Obtaining SINAMICS S120 Firmware 02.06.02.10: Official Methods

Overview

The SINAMICS S120 is a modular, high-performance drive system designed for precise motion control in advanced industrial machinery. As with any firmware-controlled automation platform, obtaining a specific firmware version such as 02.06.02.10 requires navigating Siemens' official distribution channels. Unlike consumer software, drive firmware is typically delivered only to authenticated partners and end customers with valid service agreements, and is supplied as a CompactFlash (CF) card image rather than a direct file download.

This article details the official pathways to obtain firmware version 02.06.02.10, the prerequisites for each method, and the verification steps required after installation. For users seeking a specific older build, the procedural constraints are identical to those for any current version, but the available download entry in the Siemens support portal may differ.

Firmware Version Architecture

SINAMICS S120 firmware uses a four-segment version number of the form MM.mm.bb.hh where each segment carries specific meaning within the Siemens release schema:

For version 02.06.02.10, the interpretation is:

• Major 02 – Second-generation S120 firmware (CU320, CU320-2, CU310 control units)
• Minor 06 – Sixth functional release on that platform
• Bugfix 02 – Second bugfix level on top of 02.06
• Build 10 – Tenth build of bugfix 02

Identifying the Installed Firmware Version

Before requesting firmware, confirm the version currently installed on the Control Unit. Use one of the following methods:

1. Operator panel AOP30 / BOP20: Navigate to Menu > Commissioning > Drive diagnostics > FW version. The full string V02.06.02.10 is displayed.
2. STARTER / Startdrive (TIA Portal): Go online with the drive, right-click the Control Unit, and select Properties > Diagnostics > Firmware Version.
3. Web server (CU320-2 with Ethernet): Open https://<CU_IP>/index.htm, then Diagnostics > Version.

Official Distribution Channels

Siemens delivers SINAMICS firmware exclusively through three controlled channels. Public, direct downloads are not provided to anonymous users.

Channel 1: Siemens Industry Online Support Portal

The official firmware catalog entry for SINAMICS S120 is published as Entry ID 33124038. The portal exposes only certain published versions for direct download; builds that are out of general distribution must be requested through Siemens support.

1. Navigate to the SINAMICS S120 firmware entry in Siemens Industry Online Support.
2. Sign in with a registered account. Anonymous access cannot trigger the download.
3. Open the "Download" tab and verify the version shown matches 02.06.02.10.
4. Select the package appropriate for your Control Unit (CU320 / CU320-2 / CU310 / CU310-2). The package contains a CF card image file (typically SINAMICS_S120_V02060210.bin) along with release notes and a hash manifest.
5. Accept the end-user license agreement and start the download.

Channel 2: Local Siemens Office or Siemens Partner

For versions not exposed in the public portal, or for users without portal privileges, the official recommendation is to contact the regional Siemens office or an authorized Siemens Partner. The partner can:

• Verify the legitimate need for the specific build 02.06.02.10 (e.g., to match a fleet of identically commissioned machines).
• Order a CF card pre-imaged with the requested firmware from Siemens spare-parts logistics.
• Provide the firmware image on secured media for in-house flashing.

Request the following minimum information when contacting Siemens:

• MLFB (order number) of the Control Unit, e.g., 6SL3040-1MA00-0AA0 (CU320) or 6SL3040-1MA01-0AA0 (CU320-2 DP)
• Current installed firmware version (read from AOP30 or STARTER)
• Project reference, machine serial number, and end-customer ID
• Reason for the specific build (compatibility with existing project, OEM requirement, regression bug)

Channel 3: Copy from an Existing CompactFlash Card

If another machine in the fleet has the required firmware installed on its CF card, the image can be duplicated using a standard CF card reader and a tool such as dd (Linux), Win32 Disk Imager, or HDD Raw Copy Tool on Windows. The source card must be a Siemens S120 CF card (standard 1 GB or 2 GB) and must not be write-protected by the application.

1. Power down the Control Unit and remove the CF card from its slot.
2. Insert the source CF card into a PC-mounted or USB CF reader.
3. Create a sector-by-sector image:

   sudo dd if=/dev/sdc of=sinamics_s120_V02060210.img bs=4M status=progress conv=noerror,sync

4. Insert the target CF card (same capacity, Siemens-approved type) and write the image back:

   sudo dd if=sinamics_s120_V02060210.img of=/dev/sdc bs=4M status=progress conv=noerror,sync

5. Reinsert the cloned card into the Control Unit, power up, and verify the firmware version on the AOP30.

Prerequisites for a Successful Firmware Update

Before any firmware is loaded onto a running S120 system, the following preconditions must be met:

• Complete project backup using STARTER / Startdrive: Project > Save and Archive (creates a .zip archive with all parameters, scripts, and DCC charts).
• Project consistency check: Online > Target system > Check consistency. Resolve any reported inconsistencies before loading.
• Verify license keys are present and valid: Online > Licenses. Some firmware versions require a CF card with a valid license (CFL — Card Function License).
• Confirm drive is in a safe state — the enable signal must be removed; the drive must be in o0000 (operation disabled).
• For DRIVE-CLiQ components (Sensor Modules, Terminal Modules, Motor Modules), record their individual firmware versions, since these are managed separately and may need to be updated in a coordinated step.

Loading Firmware onto the Control Unit

Two official methods exist for loading firmware onto the Control Unit:

Method A: Pre-imaged CF Card Swap

1. Insert the CF card (already imaged with V02.06.02.10) into the powered-off Control Unit.
2. Power up the Control Unit. The bootloader reads /siemens/sinamics/ on the card and validates the firmware package.
3. On the AOP30, the system prompts: New firmware detected. Perform update? Select Yes and enter the access level (manufacturer / service).
4. Wait for the update to complete. Do not interrupt power during the update; interruption can brick the Control Unit and require return-to-factory service.

Method B: Firmware Update via STARTER / Startdrive

1. In STARTER, connect to the drive online and select the Control Unit in the project tree.
2. Right-click and select Target device > Firmware update.
3. Browse to the firmware file (typically *.bin) extracted from the CF card image.
4. Confirm the version displayed matches 02.06.02.10.
5. Click Update. The tool erases the current flash, writes the new firmware, and reboots the Control Unit.

Post-Installation Verification

After the firmware is loaded, run a structured verification sequence to confirm a clean installation.

1. Version check: Confirm V02.06.02.10 is reported on the AOP30 and in STARTER.
2. Parameter integrity check: Compare current parameter set against the archived project. Most parameters are retained; some new parameters introduced in 02.06 default to factory values.
3. DRIVE-CLiQ topology check: STARTER > Topology should show all components in green; yellow indicates a version mismatch (often fixable by a component-specific firmware update).
4. Fault buffer review: Check the fault buffer for any post-update faults (typical candidates: F01018, A01019, F08501). Acknowledge and clear after analysis.
5. Commissioning test: Run a low-speed commissioning motion. Verify encoder feedback, current limit, and basic safety functions (STO / SS1) before returning the drive to production.

Troubleshooting Matrix

Field-Proven Notes

• Build 02.06.02.10 is typically a service-pack build targeted at specific customer escalations. In many fleets, public catalog versions such as HF11 of the 02.06 branch are functionally equivalent for general use; the specific build is usually required only to match the original commissioning version.
• Always cross-check the firmware version printed on the CF card label against the version read by the AOP30. A mismatch indicates a card swap that was not reflected in the drive's parameter set.
• When commissioning multiple machines from a single project, use the Series commissioning feature in STARTER to apply the project to each Control Unit after confirming the firmware version is identical.
• For long-term fleet stability, document the installed firmware version in the machine's maintenance record and in the project's version header block.

References and Documentation

• SINAMICS S120 AC Drive Manual (function manual GH6) – canonical reference for commissioning and firmware handling
• SINAMICS S120 product page – platform overview and configuration tools
• Siemens Industry Online Support Entry ID 33124038 – SINAMICS S120 firmware catalog (active support contract required for download)

FAQ