Configure SINAMICS SIZER for CU320-2 PN Firmware V4.4 and CF

Configure SINAMICS SIZER for CU320-2 PN: Firmware V4.4 and CF Card Reference

Applies to: SINAMICS SIZER for Siemens Drives V3.4 HF1, V3.5 HF1, and V3.6; SINAMICS S120 stand-alone systems built on the CU320-2 PN Control Unit (6SL3040-1MA01-0AA0); CompactFlash cards ordered as 6SL3054-xEExx-1BA0 with firmware baseline V4.4 or higher. Use this guide whenever a SIZER-generated parts list feeds a S120 cabinet build, a retrofit, or a SINUMERIK / SIMOTION migration that carries an existing CU320-2 PN.

What SIZER Does and When It Applies

SIZER for Siemens Drives is the central sizing and selection tool for the SINAMICS, MICROMASTER, and DYNAVERT T drive families, SIRIUS motor starters, SINUMERIK 840D sl, and SIMOTION motion controllers. It accepts line, motor, mechanical load, and regulatory inputs and returns a topology-validated drive configuration that includes:

• Selected Control Units, Line Modules, Motor Modules, line filters, and braking choppers
• Calculated motor current, converter overload, torque margin, and switching-frequency derating
• A BOM-ready parts list with order numbers, quantities, and dependencies
• Cable schedules (DRIVE-CLiQ, motor, line), cabinet heat-loss estimates, and dimensional drawings
• Topology export to STARTER, SIMOTION Scout, TIA Portal (Startdrive), or SINUMERIK Integrate Create MyHMI

SIZER is officially distributed and version-maintained through Siemens Industry Online Support. The release-history entry for the current and historical SIZER service packs is maintained under delivery release ID 47040218 (Delivery release for SINAMICS MICROMASTER SIZER V3.4 HF1). Out-of-cycle hotfix notes for later SIZER builds are posted as separate entry IDs (49972151 for V3.5 HF1 and 54992004 for the SIZER for Siemens Drives V3.6 update news).

Supported Drive Families and Product Scope

SIZER accepts project data in three forms: a fully manual entry through the GUI, a CSV import from upstream mechanical sizing tools, and a STARTER / Scout topology import for revision management. Every output can be regenerated against a new SIZER service pack while preserving the CU320-2 PN MLFB if the firmware baseline is matched.

SIZER Release History and CU320-2 PN Compatibility

The SIZER service-pack chain follows the Siemens firmware release cadence. Each hotfix adds MLFBs that may not have shipped when the original build was cut and removes obsolete variants. CU320-2 PN compatibility is governed by a hard rule: SIZER V3.5 or higher requires CU320-2 PN firmware V4.4 or higher. Back-porting older firmware against newer SIZER is not supported and triggers a downgrade event at first commissioning.

Selecting the wrong matrix cell triggers one of three commissioning faults: FW mismatch alarm F0130 (firmware downgrade not supported), parameter load fault F06010 (signed / unsigned parameter set mismatch), or CF card license fault F01000 (license certificate absent). All three are user-recoverable but extend the cold-commissioning time from minutes to hours.

CU320-2 PN Firmware Baseline Requirements

The CU320-2 PN (order number 6SL3040-1MA01-0AA0) ships at a firmware release that depends on the CF card fitted at delivery. Siemens stores firmware (FW), parameter descriptions (PD), and license keys (LOCK) on three partitions of the CF card. The first two are version-pinned and must match the firmware in the surrounding S120 system. The third is keyed to the CF card serial number and is project-independent.

Field-tested warning: Downgrading the firmware on a CU320-2 PN that was built against SIZER V3.6 to a V4.4 image using a V3.5 SIZER parts list will clear the project-specific license keys if the CF card is left in the slot during the downgrade. Always remove the CF card before flashing a lower baseline.

CompactFlash Card Specifications and Order Numbers

The CU320-2 and CU320-2 PN Control Units use a Type I CompactFlash card seated under the front cover. The card carries the firmware (FW), parameter descriptions (PD), and the signed license certificate (LOCK) that grants the project's commissioning entitlement. The order-code family 6SL3054-xEExx-1BA0 is the official substitute group; anything outside this family is treated as obsolete by SIZER parsers.

The substitute rule reads: when ordering a CompactFlash card, any part number collapsed into the 6SL3054-xEExx-1BA0 pattern can be used in place of the originally specified variant without reburning the project. The card's .bin file must match the project's firmware baseline exactly. Mismatched baselines produce fault F01000 on first POWER ON of the Control Unit.

Reference Parts List for Standalone SINAMICS S120

The parts list below is the worked example from a CU320-2 PN stand-alone S120 build. The BOM is one Control Unit plus its firmware-bearing CF card. It assumes a single-line supply topologically, so add Line Modules, Motor Modules, line reactors, and filters separately using SIZER's drag-and-drop designer.

For V3.5 projects that have already been issued to procurement, the same position 2 may also carry 6SL3054-0EAxx-1BA0 substitutes or the SIZER V3.5 HF1 build ordered through entry 49972151.

Step-by-Step Configuration Workflow

1. Verify prerequisites. Confirm 64-bit Windows engineering host (Windows 10 21H2 or later, or Windows Server 2019+); 8 GB RAM minimum, 16 GB for S120 cabinet builds; Internet access to support.industry.siemens.com; existing SIZER license (single-user or multi-user) activated on the dongle or in the floating-license pool.
2. Install SIZER. Run the installer as Administrator. The installer unpacks the FW database and SIZER MLFB catalogue side-by-side, so version alignment is automatic on a clean install. Overwriting an older SIZER build requires uninstalling the prior version first; otherwise registry keys collide and the BOM export silently drops Control Unit MLFBs.
3. Create a new project. Select File > New > Drive System, name the project, and pick the supply system topology. For a CU320-2 PN stand-alone S120, choose Stand-alone S120.
4. Configure supply and infeed. Enter line-to-line voltage, frequency, fault level (Isc), required line harmonics class (THDi), and any regenerative mode. SIZER returns the smallest Line Module that meets the application's peak current and overload conditions.
5. Select Control Unit. Pick CU320-2 PN when the application needs PROFINET I/O for the higher-level PLC. SIZER imposes the V4.4 minimum firmware rule and locks the BOM accordingly.
6. Add drive axes. For each axis, pick Motor Module form factor (booksize, booksize compact, chassis), Motor Module current rating, motor, encoder, and any DRIVE-CLiQ encoder interface. SIZER validates the topology and warns if a Motor Module exceeds its thermal budget on the cycle profile.
7. Run compliance checks. SIZER performs EMC compliance, harmonic-load, and overload checks. Resolve all warnings before exporting the BOM or the cabinet will not pass factory acceptance without rework.
8. Export BOM. Use File > Export > Parts List (CSV) or the direct RTF export. Hand the CSV to the procurement team and quote the 6SL3054-xEExx-1BA0 substitute string for the CF card line.
9. Transfer to STARTER / Scout / TIA Portal. SIZER writes a topology export that STARTER or Scout reads as the offline project base. TIA Portal uses the Startdrive plugin to import. Confirm at import that the firmware baseline matches the CU320-2 PN's CF card BIN version exactly.

Verification and Commissioning Checks

Before powering the converter on for the first time, complete the following checks. A failed check does not necessarily block the cabinet but introduces rework time during cold commissioning.

1. CF card firmware level. Insert the CF card in any Windows host and read FWCHECK.LOG from the \FW\ partition. The BIN file SINAMICS_V04.04.nn.bin must show a version equal to or above V4.4. SIZER V3.6 projects require V4.5 or higher.
2. Project license. Read the LOCK partition in SIZER's License Overview; the certificate's CU320-2 PN serial must match the Control Unit label.
3. DRIVE-CLiQ topology matches SIZER. Power the cabinet, navigate to parameter r0098[0..9] (Control Unit topology index) and confirm the component sequence read by STARTER online matches the sequence in the SIZER export.
4. PROFINET name and IP. Using PRONETA or TIA Portal topology editor, assign the CU320-2 PN's PROFINET device name and IP address from the SIZER project. The PLC connection must be cyclic (Watchdog = 1 ms typical).
5. First safe stop. Trigger STO from the higher-level PLC and observe r9773.0 to confirm the safe torque off path clears. This must succeed before drive enable.

Troubleshooting Matrix

Field Proven Caveats and Edge Cases

• License-card vs. CF card confusion. Older SIZER installs distinguish the engineering license (SIZER dongle / license pool) from the CF card (project license). They are different artifacts. Slipping the project license card into a CU310-2 instead of a CU320-2 PN triggers F01000.
• Hotfix vs. full release. V3.5 HF1 sits between V3.5 and V3.6. Some procurement databases only accept full release MLFBs; quote 6SL3070-0AA00-0AG0 for V3.6 and the previous release media MLFB for V3.5 HF1.
• Cross-version backup restore. Restoring a STARTER backup taken against SIZER V3.6 onto a CU320-2 PN firmware V4.4 CF card works for parameter data but fails for any safety or Drive-CLiQ topology changes that landed between versions.
• TIA Portal migration path. SIZER exports remain readable from TIA Portal V15 onward. Pre-V13 projects must be re-exported from SIZER into the new topology format before they import cleanly.
• CompactFlash read/write endurance. CU320-2 CF cards are rated for a defined erase-cycle count; using the card as a fault log target rather than just FW + license holding is the most common way to wear out a card before firmware rev obsolescence.

Standards and Compliance References

For harmonic and EMC verification when configuring the line side via SIZER, consult the relevant section of the SIZER report against the working standard cited in the line harmonics-class parameter. SIZER's reports use the public IEC TR 61800-6 harmonic methodology for converters, and pull EN 61800-5-1 safety-clearance criteria when computing cabinet creepage distances. Always re-verify the standard revision against your country's national annex because IEC publications are typically adopted with national deviations. Background on the underlying PROFINET infrastructure that the CU320-2 PN enforces is in PROFIsafe / PROFINET installations guides maintained by PI (PROFIBUS / PROFINET International).