When you perform a "Device Update" via TIA Portal, you are actually swapping out the data package container. The software unpacks the new container, compares the parameter lists (old vs. new), and migrates your settings.
It is impossible to discuss the container without understanding the Drive Object. A SINAMICS drive can host multiple logical Drive Objects:
The siemens.mc.drives.acx.model.configuration data.package container is the serialized representation of these Drive Objects. When you deploy the container, you are essentially instantiating these objects into the target CU (Control Unit). When you perform a "Device Update" via TIA
When you create a drive object in a Siemens environment (e.g., TIA Portal or STARTER/SCOUT), the system generates a data.package container behind the scenes. Inside this container, you typically find:
| Component | Description |
| :--- | :--- |
| Device Configuration (.cfg) | Basic hardware identification: Order number of the drive unit, power unit, and Control Unit (CU320-2, CU310-2). |
| Parameter List (.acx) | A flattened or structured list of all drive parameters (p-numbers and r-numbers). For example, p1300 (Control mode) or p1520 (Torque limits). |
| Communication Mapping (.dft) | Defines how process data words (PZD) map between the drive and the controller. This is critical for PROFIdrive telegrams (e.g., Telegram 1, 5, 7, 9, 105). |
| Firmware and Safety (.edz) | Links to the required SINAMICS firmware and Safety Integrated configurations (STO, SS1, SLS). |
| Topology (.tpl) | In multi-axis systems (e.g., S120 with a 32-axis line-up), this describes which motor module is connected to which drive slot. | The siemens
Advanced users can access the container programmatically using the TIA Portal Openness API. For example, a C# script can:
This enables mass configuration of drive fleets from a spreadsheet or database. This enables mass configuration of drive fleets from
Standard documentation for the package.
/**
* Provides the core data model for ACX Drive Configuration.
*
* <p>This package contains classes for managing configuration containers,
* parameter blocks, and data serialization structures used within the
* Siemens Motion Control (MC) drive ecosystem.</p>
*
* @since ACX Firmware v4.2
* @author Siemens AG
*/
package siemens.mc.drives.acx.model.configuration.data.package;
First, let’s translate the gibberish into plain English:
If you export the container to an exchange format (e.g., using TIA Portal’s “Export drive as AML”), you’ll find a structured XML file. Below is a simplified representation:
<Container id="siemens.mc.drives.acx.model.configuration">
<Header>
<Vendor>siemens</Vendor>
<DriveType>Sinamics S120</DriveType>
<Firmware>V5.2</Firmware>
</Header>
<ConfigurationData>
<Parameter name="p1082" value="1500.0" unit="rpm"/>
<Parameter name="p1120" value="2.0" unit="s"/>
<Telegram type="SIEMENS_TELEGRAM_105" pzd_config="4/4"/>
<Safety submodule="F-DI" F_CRC="0x8A3F"/>
</ConfigurationData>
<Dependencies>
<Requires>siemens.mc.drives.acx.model.deviceproxy</Requires>
<Requires>siemens.mc.drives.acx.model.safety</Requires>
</Dependencies>
</Container>
Notice that the container does not store live diagnostic data (e.g., motor temperature, actual torque). It stores the blueprint—the intended configuration.