Resolving Sinamics DCM F60069: Control Unit Power Module Fault

1. Problem Overview

The Sinamics DCM (DC Master, MLFB family 6RA80) is a fully digital, modular DC drive used for armature and field control of DC motors in metals, paper, hoist, and test-stand applications. The drive is split into two functional sub-assemblies:

• Power Module (PM) – the thyristor bridge, snubbers, current transformers, and heatsink; identified in Siemens ordering data as the Lxx option (e.g. L10 = without integrated field power module).
• Control Unit (CUD) – the digital controller board; supplied as Basic or Advanced. The CUD carries the firmware, the parameter image, and the backplane link to the power unit.

During commissioning or after a hardware change-out, the drive raises alarm F60069 and the CUD reports that it cannot establish a logical link to the power module. Typical operator-panel text reads: "Communication failure to the power module" or "Power module not identified." Until the link is restored, the drive will not close the contactor and will refuse the ON command; the starter is held in "Ready without power module" state.

2. Sinamics DCM Hardware Architecture

Understanding the architecture is required before interpreting F60069. The DCM is a two-board system with an optional operator panel (BOP20 / AOP30) and optional communication modules mounted on the CUD.

2.1 Power Module Options (L-codes)

An L10 machine therefore arrives from the factory without the field-power PCB. When the application requires an internal field module, the customer either changes the MLFB or installs the field-power kit. The Control Unit does not change for L10 vs L00 – only the power stack changes.

2.2 Control Unit Basic vs Advanced

If the application needs PROFINET IO for setpoint, encoder, or diagnostics – particularly reading an absolute encoder position over PROFINET as in the field case described here – the CUD must be Advanced. A Basic CUD cannot host a CBE20 with PROFINET IO controller capability.

2.3 Operator Panel and EPROM

The DCM uses either an AOP30 (Advanced Operator Panel) or a BOP20 (Basic Operator Panel). The AOP30 contains an EEPROM that stores drive-identifying information: MLFB, serial number, factory parameter set, and CUD firmware checksum. If this EEPROM is damaged, missing, or mismatched to the rest of the drive, the CUD cannot complete its identification handshake with the power module and raises F60069.

3. Alarm F60069 – Code Definition and Behavior

3.1 Where the Code Comes From

F60069 belongs to the Sinamics fault-numbering block 60000-60099, which is reserved for hardware identification and module-acknowledgment faults. Within this block:

3.2 Fault Value (r0949) Interpretation

The numerical fault value in r0949 differentiates the underlying cause:

Always read r0949 before clearing the alarm. The value tells you whether to focus on the operator panel EEPROM, the backplane ribbon, or the firmware.

4. Root Cause in This Application

The application that produced the original F60069 had three converging factors:

1. L10 power module – ordered without integrated field. The CUD powers up expecting to handshake with an L00 (full armature + field) power stack. When the field-power section is absent the CUD sees an incomplete type-ID register on the SPI bus and stops identification.
2. CUD swapped from Basic to Advanced – the drive was shipped with a Basic CUD (the L10 option normally ships Basic) but the application required PROFINET to read an encoder. The Basic CUD was field-replaced with an Advanced CUD without re-flashing the operator-panel EEPROM that holds the previous unit's serial/MLFB.
3. AOP30 EEPROM carries the CUD's identity – when the CUD was changed, the panel still advertised the old MLFB/serial. The CUD's startup routine detects that the announced identity does not match its own hardware key and refuses to claim the power module.

Together these three factors generate r0949 = 2 (serial number missing / mismatched). Replacing the panel board resolved the alarm because the new board carried an EEPROM correctly cloned to the new CUD identity – or because the freshly imaged EEPROM revalidated the handshake on the very next boot.

5. Diagnostic Procedure

Execute the following steps in order. Each step is non-destructive and can be performed with the drive de-energized except where noted.

5.1 Read the Fault Buffer

1. On the AOP30, navigate to Menu → Diagnostics → Fault buffer, or use STARTER / Startdrive connected via USB or PROFINET.
2. Record r0949[0] (current fault value), r0947[0] (fault number), and the time stamp r2131[0].
3. If r0949 = 0 → problem is mechanical (ribbon cable, power module absent). If r0949 = 2 or 3 → problem is the operator panel / EEPROM. If r0949 = 4 → firmware mismatch.

5.2 Inspect the Backplane

1. Power down and lock-out the drive. Wait 5 minutes for DC bus capacitors to discharge – measure at the DC-link test points with a 1000 V meter to confirm < 50 V.
2. Open the CUD compartment. Inspect ribbon cable X100 between the CUD and the power module; also inspect X101 if present.
3. Look for bent pins, oxidation on the connector, or a half-inserted socket. Reseat both ends.

5.3 Verify Power Module Type ID

1. In STARTER, navigate to Drive → Configuration → Power Module and read r0207 (rated armature current) and r0208 (rated armature voltage) from the identified PM.
2. If both read zero or "??", the CUD cannot read the PM type ID at all → ribbon or PM EEPROM fault.

5.4 Compare the Operator Panel EEPROM to the CUD Identity

1. On the AOP30, navigate to Menu → Commissioning → Drive identification and read the displayed MLFB and serial number.
2. Compare against the rating-plate label on the CUD.
3. If the AOP30 shows the MLFB of the previous CUD, the panel was not re-cloned. This is the r0949 = 2 case.

6. Solutions

6.1 Solution A – Replace or Re-clone the Operator Panel Board

1. Order the AOP30 board compatible with the Advanced CUD (Siemens part reference 6RA80xxx-0Axxx depending on the specific model).
2. Swap the AOP30. The new panel's EEPROM ships blank – the CUD will write its identity into the panel on the first successful boot.
3. Power the drive (DC 24 V only is sufficient for the CUD, the line may remain off).
4. Clear the fault via p3981 = 0 (factory reset of the fault buffer) or by acknowledging on the AOP30.
5. Verify F60069 is gone and the power module is now identified: r0207 and r0208 should show non-zero values.

6.2 Solution B – Manual EEPROM Repair on the AOP30

If a replacement panel is not on hand, attempt EEPROM recovery using STARTER:

1. Connect STARTER online to the CUD over the USB service port.
2. Open Drive → Parameters → Expert list and filter for the operator-panel identification parameters.
3. Set p9908 = 1 to force a re-identification of the panel EEPROM.
4. Wait for the CUD to power-cycle internally; observe r0949 value after the cycle.

If the EEPROM is physically damaged (write errors during p9908), replacement is unavoidable.

6.3 Solution C – Reseat the Ribbon and Clear the Topology

1. With the drive off and locked out, reseat X100/X101.
2. Apply power and execute p9906 = 1 (topology check) then p9907 = 0 (accept current topology).
3. Re-read r0949.

6.4 Solution D – CUD / Power Module Firmware Match

If r0949 = 4, the CUD firmware (read via r0018) is incompatible with the PM hardware revision (read via r0203).

1. Identify the current firmware from the SD card label or r0018.
2. Download the matching firmware from Siemens Support (search "6RA80 firmware") and load it to the SD card.
3. Insert the SD card into the CUD and cycle 24 V control power; the CUD will auto-flash from the SD card on the next boot.

7. Adding PROFINET with CBE20 on an Advanced CUD

Once F60069 is cleared, the application requires PROFINET to read encoder position. The Advanced CUD has an integrated PROFINET interface but adding the CBE20 Communication Board Ethernet provides a second channel for redundancy or for connecting PROFINET IO devices (encoders, valve islands, I/O).

7.1 Hardware Insertion

1. Power down and lock-out.
2. Open the CUD compartment; the CBE20 slot is on the right side of the CUD, behind a blank cover.
3. Insert the CBE20 board; torque the two captive screws.
4. Wire the PROFINET cables to the CBE20's two RJ45 ports (P1, P2) using the standard PROFINET color coding.

7.2 Configuration in TIA Portal / STARTER

1. Install the Sinamics DCM HSP (Hardware Support Package) for the active TIA Portal version. Locate it via "Siemens Support → HSP download → Sinamics DCM".
2. Add the DCM to the device view; select the Advanced CUD variant.
3. Add the CBE20 from the catalog and drop it on slot 3 of the CUD.
4. Configure the PROFINET device name on the CBE20 – this must match the device name set in HW Config. Use the "Assign PROFINET device name" function from the PLC's online menu.
5. If the encoder is a PROFINET IO device, drag it into the topology; the DCM will exchange cyclic data with the encoder when telegrams are configured in p0922 / p2079.

7.3 Reading Encoder Position

PROFINET encoder position from a CBE20-attached encoder is mirrored into drive parameters through the standard SINAMICS free-function-block linkage. Typical mapping:

• Encoder cyclic word 1 → drive connector CI: p2050[0] on the CBE20.
• Position value displayed in r0479[0] (position actual value, normalized).

For the encoder telegram configuration, set:

p0922 = 999   ; free telegram configuration
p2079 = 3     ; encoder telegram length = 3 words
p2051[0] = r0479[0]   ; send actual position to PROFINET

7.4 IP Address and Device Name

8. Verification

After the corrective action, perform the following checks before returning the drive to production:

1. No active alarms. AOP30 should show no F-codes and no A-codes; STARTER fault buffer should be empty after a clear.
2. Power module identified. r0207, r0208, r0209 show non-zero armature rating values.
3. Field path verified (if L00/L05 was the target). Field current r0027 responds to field setpoint p2571; with armature off, the field can be turned on via p2571 = rated field current and the motor field should hold.
4. PROFINET IO is up. The CBE20 port LEDs (Link/Activity) show steady green; TIA Portal diagnostics show no PROFINET diagnosis events.
5. Encoder cyclic data. In STARTER trace, record r0479[0]; rotate the encoder by hand and confirm the value changes monotonically.
6. No-trip test. Issue ON with 0 setpoint and confirm the contactor closes; ramp to 5% speed and back to 0 with no F-code events.
7. Save parameters. Copy RAM→ROM with p0977 = 1; save to SD card with the AOP30 "Copy RAM to ROM and save to card" menu item.

9. Related Faults and Their Overlap with F60069

10. Preventive Measures

• Whenever a CUD is swapped, always verify that the AOP30 / BOP20 EEPROM has been cloned or replaced. Siemens supplies new CUDs with an empty EEPROM that the panel detects and self-programs on first boot – but a panel from another drive will keep the old identity.
• Maintain firmware parity across the fleet. Use the same CUD firmware version on all DCMs at a site to avoid r0949 = 4 mismatches after a board swap from spares.
• Document the L-code option on every drive in the asset register so that a future engineer does not misdiagnose the missing field-power section as a hardware fault.
• When commissioning a brand-new L10 unit, perform a quick r0207 / r0208 check before closing the cabinet – if the values are zero, the CUD has not yet identified the power module, and an F60069 is imminent.
• Store the project STARTER archive on the SD card and on a network share so that a CUD replacement can be commissioned offline in 30 minutes rather than in 4 hours.

11. Spares and Field Notes

12. Frequently Asked Questions