Troubleshooting SINAMICS CU320 Download Error WWBS:896

1. Problem Overview

A SINAMICS S120 control unit CU320-2 connected to SIMOTION SCOUT V4.3 / V4.4 over PROFIBUS DP (or PROFINET) refuses the first commissioning download. SCOUT reports "Waiting for first commissioning" on connect, briefly prints download complete, then aborts with the dialog:

Download (WWBS:896)
An error has occurred while downloading.
Possible causes:
- Illegal parameter set
- The quantity structure is not permitted
Return code: 0xbe0b0018 or 0xbe0bffff

Only the green RDY LED on the CU320-2 is lit. No other fault LEDs are active. The condition is reproducible at every download attempt, and the online/offline handshake collapses after parameter transfer completes, even though SCOUT believes the transfer succeeded.

This document walks through the root causes, the diagnostic buffer interpretation, and the field-proven recovery sequence for a CU320-2 first-commissioning failure on a partially populated S120 line-up (i.e. the control unit is online but one or more Motor Modules / encoders are physically absent).

2. Affected Components, Firmware and Tooling

Refer to the SINAMICS S120/S150 List Manual (LH1) and the CU320-2 Control Unit Operating Instructions for the parameter references cited below.

3. Decoding the Return Codes

The two error values observed in this scenario are decoded against the SINAMICS commissioning and SCOUT WWBS error catalogs as follows.

3.1 SCOUT-side error: Download (WWBS:896)

WWBS:896 is the SCOUT commissioning channel error for "Illegal parameter set / quantity structure not permitted". It is raised by the SIMOTION DCC / SCOUT loader when the SINAMICS parameter image it has just written back from the device (RAM-to-RAM compare) does not match the offline image. The most common triggers are:

• Offline topology contains drive objects that are not present in the connected CU320-2 (and vice versa).
• Offline p0108 / p0121 (drive object configuration) disagrees with the firmware on the CF card.
• Project was created under a different SINAMICS firmware / SSP combination (for example SSP V2.6.0 against device V2.6.2).
• One of the configured Drive Objects is in the deactivated state (p105 = 0) but SCOUT still expects a parameter record for it.

3.2 Return code 0xbe0b0018

The 32-bit return value 0xBE0B0018 is composed as:

• BE0B = SCOUT WWBS function class "parameter download / RAM compare".
• 0018 = sub-error "quantity structure inadmissible / object type missing in the device".

It tells you the offline image references a Drive Object (DO) number (typically DO2 .. DO16) that the running firmware on the CU320-2 has not instantiated. The classic case is: offline project has 6 drives, online device has 1 drive.

3.3 Return code 0xbe0bffff

The variant 0xBE0BFFFF is the "generic / unspecified" form of the same WWBS:896 class. SCOUT receives a negative acknowledgement from the device that does not carry a specific sub-error. In practice, the underlying cause is the same: a mismatch between offline DO list and online DO list, or a corrupted parameter set on the CF card.

4. Root Cause Analysis

Five failure modes produce this exact symptom tree. They are listed in order of frequency observed in the field.

4.1 Topology mismatch (most common)

Offline DRIVE-CLiQ topology in the SCOUT project includes Motor Modules, Line Modules or TM modules that are not physically wired to the CU320-2. On first commissioning the device raises a top-level fault F01300 / F08501 indicating missing components. The download complete message is reported by the RAM writer, but the verification compare (which reads the p0108 / p0107 / r0108 image back) cannot complete because the device has already gone into topology fault state and is no longer accepting acyclic parameter services from SCOUT.

4.2 SSP / firmware mismatch

The CF card carries SINAMICS firmware V2.6.2 but the project was built against SSP V2.6.0 or V2.5.x. Each firmware release adds, removes, or re-numbers parameters; a load from an older SSP into a newer firmware can pass the write step and fail the read-back compare because the device-side parameter set has new defaults the project does not know about.

4.3 DO number conflict

Drive Objects are pre-assigned DO numbers 2..16 by the offline topology. If the user has edited DO numbers (right-click Drive Object → Properties → Number) and the running firmware has already instantiated the same DO for a different function, the load fails with 0xBE0B0018.

4.4 Deactivated DO with active parameter set

The user has set p0105 = 0 (deactivate component) on a Drive Object, but the offline project still contains a parameter image for it. The CU320-2 will not return a parameter record for the deactivated DO, breaking the compare.

4.5 Corrupted / non-bootable CF card

If the CF card image is incomplete (for example a partial unzip, or a card programmed with the wrong order: license first, then firmware), the control unit boots into fallback firmware and the wrong firmware version is reported online. SCOUT then downloads against the wrong baseline.

5. Diagnostic Procedure

Run the following checks in the listed order. Each step produces a binary signal (go / no-go) that decides the next branch.

Step 1 - LED status inventory

If RDY is red or flashing, the problem is on the CF card (Section 7.4) and SCOUT will not be able to write a parameter set at all. Resolve the boot state first.

Step 2 - Online diagnostic buffer

1. Select the SINAMICS device in the SCOUT project tree.
2. Press Ctrl+D (or right-click → Diagnostics → Diagnostic buffer).
3. Read the most recent faults and warnings, with timestamps.

Typical fault set seen on this error:

• F01300 — topology: missing component on DRIVE-CLiQ.
• F08501 — PROFINET/PROFIBUS communication error during parameter download.
• A08502 — warning, drive object not ready.

Record every F-code. The combination of F01300 plus F08501 is the smoking gun for a topology mismatch (Section 4.1).

Step 3 - Online compare of drive objects

1. Right-click the SINAMICS device → Target system → Device trace.
2. Open Commissioning → Drive objects and read r0107 / r0108 on the live device.
3. Compare the DO list to the offline project. Any DO that exists offline but not online is a candidate for deactivation (Section 6.1).

Step 4 - Firmware / SSP cross-check

1. On the live device, read r0018 (Control Unit firmware version). Confirm it is V2.6.2.
2. In SCOUT, open Options → Support Packages. Confirm an SSP with the same version (V2.6.2) is installed and assigned to the device.
3. If the SSP is older or newer, install the matching SSP, recompile, and re-attempt the load.

Step 5 - Reconnect test

After the failed download, disconnect the online connection in SCOUT, wait 5 s, and re-establish it. If the device comes back online, the firmware image is healthy and the issue is purely a parameter compare failure (the recoverable path). If the device is unreachable for > 30 s, the control unit is in a topology fault state and must be cleared from the diagnostic buffer before any further downloads.

6. Solution Path A — Deactivate Drive Objects (Topology Mismatch)

Use this path when the diagnosis (Section 5) shows missing Motor Modules, Line Modules, Terminal Modules, encoder modules, or sensors that are referenced in the offline project but not present on the real line-up.

6.1 Deactivate a missing DO offline

1. In the SCOUT project navigator, expand the SINAMICS device.
2. Open the Topology view (DRIVE-CLiQ topology).
3. Right-click the missing component (Motor Module, Line Module, TM, etc.).
4. Choose Status → Deactivated.

The component is grayed out and excluded from the offline parameter set. Repeat for every component that is not physically wired to the CU320-2.

6.2 Deactivate via parameter p105

Equivalent to 6.1 but at the parameter level. Useful when the component is referenced indirectly (for example by a safety Integrated channel):

1. Open the expert list of the affected Drive Object.
2. Set p0105[DO] = 0 (component deactivated).
3. If the parameter write is rejected because the device is in fault state, do this offline and reload.

6.3 Re-attempt the download

1. Compile the project (Ctrl+B).
2. Go online to the CU320-2.
3. Right-click the SINAMICS device → Download to target.
4. Accept the prompt "Download will overwrite the offline image".
5. Monitor the target system output. The download should now terminate with "Download (completed)" and the diagnostic buffer should be clear of F01300.

7. Solution Path B — Automatic Commissioning (Drive Objects Present)

Use this path when the Motor Modules and encoders ARE wired to the CU320-2 but the offline project does not reflect the actual topology, or the user wants the device to discover its own DO list.

7.1 Procedure

1. Go online to the CU320-2.
2. Right-click the SINAMICS device in the project tree.
3. Select Commissioning → Automatic commissioning.
4. SCOUT will read the live topology, instantiate the drive objects, and propose an offline project that matches.
5. Apply, save, compile, and reload.

7.2 When to use this path instead of Section 6

• The user has access to the drives and the wiring has been completed.
• The project is being built from scratch (no DO list yet).
• The first commissioning has never been executed on this CF card.

8. Firmware and SSP Verification

Firmware and Support Package alignment is the second most common cause of this error and is frequently misdiagnosed as a parameter problem.

8.1 Read the live firmware version

Online → SINAMICS device → Properties → Version overview. The Control Unit firmware field must match the CF card label. For the reported case, this is V2.6.2.

8.2 Match the SSP in SCOUT

1. Options → Support Packages.
2. Confirm an entry for SSP SINAMICS V2.6.2 is installed.
3. Open the project → SINAMICS device → Properties → Support Package. The assigned SSP must equal the live firmware.

8.3 Recover a corrupted CF card

1. Power down the CU320-2.
2. Remove the CF card.
3. Re-image the card using a PC with SIMOTION SCOUT Card Reader/Writer or a Siemens CF card programmer, with the correct image (license, then firmware, then project if required).
4. Reinsert, power up, and re-check the RDY LED.

Refer to the SINAMICS S120 Commissioning Manual for the recommended CF card write procedure.

9. Verification

Use the following checks to confirm the recovery is complete.

9.1 Parameter compare

1. Online → SINAMICS device → Target system → Compare offline / online.
2. The result must be identical. Any persistent difference is a hidden topology or DO conflict.

9.2 Diagnostic buffer clean state

1. Open the diagnostic buffer (Ctrl+D).
2. Press the Acknowledge button.
3. Re-trigger a download. The buffer must stay empty of F01300, F08501, A08502.

9.3 LED status

• RDY = steady green.
• COM = steady or flickering on bus traffic.
• OUT1, OUT2 = off (no output configured at first commissioning).

9.4 Project tree drive state

The previously grayed-out drive objects with the "?" indicator must be solid and reachable. If a DO is still whited-out, repeat Section 6.1 (deactivate) or Section 7.1 (automatic commissioning) until the offline and online DO lists match exactly.

10. Common Pitfalls and Edge Cases

11. Prevention and Best Practices

• One firmware, one SSP, one project. Freeze the SINAMICS firmware on the CF card and use the matching SSP in SCOUT. Do not mix V2.6.x projects with V2.5.x firmware on the bench.
• Build the project from the actual topology. When the line-up is fully wired, run Automatic commissioning first; only then write the application (DCC, SIMOTION axes, etc.).
• Deactivate before you build. If the bench is incomplete, deactivate every missing component in the offline topology before the first download. This avoids the WWBS:896 compare failure on the first attempt.
• Keep the diagnostic buffer discipline. Acknowledge faults before each download. A residual F01300 will be re-raised after a successful download, hiding any new fault.
• Document the DO list. Keep a printout or PDF of the offline drive object list (with DO numbers and article numbers) inside the cabinet. When the line-up changes, the list is the reference for the next engineer.

12. Related Siemens Documentation

• CU320-2 Control Unit Operating Instructions (CompactFlash, LED, diagnostics)
• SINAMICS S120 Commissioning Manual
• SINAMICS S120/S150 List Manual (LH1, parameter r0107/r0108/p0108/p0121/p105)
• SIMOTION SCOUT V4.3 / V4.4 Configuration and Programming Manual
• SIMOTION D4x5 Commissioning and Hardware Installation Manual