Step 1 – Download
Get the .acx or .zip container (extract if zipped).
Step 2 – Import into STARTER / SCOUT
Step 3 – Verify
Check the drive’s r0145 (firmware version) matches the container’s version.
Step 4 – Configure
Now you can:
System integrators downloaded configuration containers to drives via VPN + web server. No on-site presence required. Error rate dropped by 92%.
A poor download process leads to:
A better download means:
For advanced users, write a script that:
# TIA Openness PowerShell snippet
$drive = Get-SiemensDrive -ProfinetName "Drive_01"
$drive | Export-AcxContainer -ConfigOnly -Compression Fastest -Path ".\configs\"
A "better" download is useless if corrupted. Use the SHA-256 checksum included in modern ACX headers:
certutil -hashfile drive_config.acx SHA256
# Compare with Siemens reference hash
Using SCOUT or STARTER:
Siemens MC drives utilizing the ACX (Advanced Control X) firmware environment rely on hierarchical model configuration data packages. These packages are often encapsulated in container formats (e.g., SIMOTION SCOUT TIA Portal containers, .acx, .zip, or Siemens-specific archive types). This paper analyzes common bottlenecks in downloading such containers and proposes improved workflows, validation methods, and version control practices to enhance reliability and speed.
An ACX (Drive Configuration) data package is essentially a container—a zip-like archive that holds:
The default method (using STARTER or Startdrive) often downloads unnecessary diagnostic logs and redundant data blocks, leading to: Step 1 – Download Get the