Siemens.mc.drives.acx.model.configuration Data.package Container -
When upgrading Sinamics drives from an older firmware (e.g., V4.7 to V5.2), the ACX model container is converted by Startdrive. The tool reads the existing container structure, validates compatibility, and rewrites the internal schema—without losing parameter values. This process is far more reliable than manual parameter comparison.
Refers to the specific drive technology or extension (commonly associated with (url) drive macros and configurations). Package Container:
The identifier refers to a specific software component or "Hardware Support Package" (HSP) required for the TIA Portal (Totally Integrated Automation) ecosystem. This package is specifically tied to the Startdrive commissioning tool, which integrates Siemens drive hardware into the TIA Portal engineering environment. Core Identity and Role
The data.package container serves as the software object that holds all this information — whether from automatic detection or user-defined files — within a structured, programmable format. Engineering tools like CMC, TIA Portal, and custom .NET applications use this container to manipulate, transfer, and apply drive configurations. When upgrading Sinamics drives from an older firmware (e
Open the or the Totally Integrated Automation UPDATER .
In this mode, the CMC package uses a user-defined offline topology file, typically with a .utz2 extension, which describes the maximum machine configuration. This topology file defines not only the physical arrangement of components but also DO names, component numbers, article numbers, component types, and generalized drive data structures. When the package is executed, SINAMICS checks this offline topology against the currently available hardware and customizes the configuration accordingly, creating target topologies and DOs for the specified components.
The is far more than a cryptic internal identifier—it is a powerful, standardized encapsulation of drive intelligence. For the motion control engineer, mastering this container means: Refers to the specific drive technology or extension
Therefore, the term as a whole most likely refers to a , allowing it to be managed and deployed by custom automation code.
The container separates application parameters (e.g., positioning speed) from engineering parameters (e.g., current limits). This separation allows for modular engineering.
Within the DRV (drive) subsystem, the package interacts intimately with the data.package container . The package contains drive data in the form of parameter backup files ( PSxxxyyy.ACX ), topology definitions, and component properties. The process within the package can follow one of two paths: Core Identity and Role The data
In “automatic configuration” mode, SINAMICS determines the actual hardware topology online and saves it as the target topology ( p9903 ). The system creates drive objects (DO) automatically and assigns them names, numbers, and folder structures based on bus and slave numbers. Each DO is represented as a PSxxxxxx.ACX or *.TEA file. The PS000000.ACX file monitors consistency, and PS000099.ACX stores internal PROFIBUS configuration data. This entire structure is captured and can be stored as a drive archive for later import.
: Likely refers to the internal model architecture used for drive configuration data in TIA Portal.
