Resolving SINAMICS DCM F60062 and F60068 Faults Compensation

Overview of F60062 and F60068 on SINAMICS DCM

The SINAMICS DCM (DC Master) converter family, built around the 6RA80 control module and the Basic Operator Panel BOP20, reports two related power-unit faults that consistently surface during commissioning and after power-section replacement: F60062 (power unit fault during operation/identification) and F60068 (incorrect compensation values for the power unit). Both faults share a single underlying root cause chain — the converter cannot reconcile the analog feedback of armature voltage, armature current, and field current against the compensation map stored in the power unit EEPROM.

F60062 most commonly appears on the first ON command after power-up, immediately after the electronics initialize but before the firing pulses are released. F60068 surfaces during the identification run (p50051 = automatic identification routine) when the firmware tries to write fresh compensation coefficients into the power section and finds the values either out of range, inconsistent with the connected power stack, or unreadable from the power unit's internal memory. Field experience on the 6RA8085-6FV62 chassis and equivalent 6RA80 frames shows that a single misconfigured parameter (typically P50076[0] or P50076[1]) can trigger both faults sequentially — F60068 on identification, then F60062 the next time the operator issues the ON command.

Fault Code Definitions and Sub-Values (r0949)

Both faults carry additional diagnostic information in parameter r0949. The decoder must be read while the drive is in the fault state because the value is overwritten on the next fault or on a successful power-on reset.

Always capture r0949 the moment the fault becomes active and store it in the project documentation. If the drive has been power-cycled and the fault buffer cleared, the value is unrecoverable.

Hardware Context: SINAMICS DCM 6RA80 Series

The 6RA8085-6FV62 is a representative 6RA80-series unit rated for armature currents up to roughly 1200 A DC at 575 V AC line-side. The 6RA80 series separates the open-loop control module (CUD — Control Unit DC) from the power section. The CUD contains the firmware, BOP, parameter memory, and the DRIVE-CLiQ port that links to the power-section Interface Module (IFM) on the firing board. Compensation values for firing-angle advance, commutation overlap, and current-zero correction are written into a non-volatile memory on the IFM during commissioning.

When the CUD is replaced without transferring the power section's identification data, or when the IFM EEPROM has aged past its write-cycle limit (~100,000 cycles), the read-back fails and the firmware raises F60068. F60062 then manifests on the next run enable because the compensation map needed for stable current-loop behavior is incomplete.

The r50038 Phantom Voltage Symptom

One of the clearest field signatures of a F60062 / F60068 condition is the appearance of a non-zero armature voltage actual value (r50038) while only the 24 V DC electronics supply is on, with the line contactor open and the armature AC supply de-energized. A reading of r50038 = 1036.2 V under this condition is impossible from a real physical voltage — the maximum the bus can deliver is the peak of the 440 V AC line, which is roughly 622 V DC at no load. Values substantially above the theoretical peak indicate that the armature voltage sense path is open and the analog input is floating into a saturated range.

The root cause is one of:

1. Broken sense wire between the power section and the CUD voltage input.
2. Open shunt in the voltage divider on the Interface Module.
3. CUD mainboard analog input damaged by a previous over-voltage event on the armature.
4. Firmware corruption on the IFM EEPROM causing corrupted compensation lookup values that drive the sense-path calibration constant into an invalid range.

If r50038 does not return to a small offset value (typically < 5 V) when the line contactor is open, do not attempt to run the drive — first repair the sense path.

Root Cause Chain: How Compensation Failure Drives Both Faults

The SINAMICS DCM regulates armature current through a closed loop that uses firing-angle pre-calculation. Each firing angle is offset by a compensation value loaded from a 3-D lookup table indexed by actual current, actual voltage, and the power-unit serial number. When this table is corrupt or unreadable:

• The regulator commands firing angles outside the safe commutation window — commutation fails, DC-link current collapses, and the firmware detects the event as F60062.
• The identification routine detects that the read-back compensation coefficients do not match the power-unit serial number reported on the DRIVE-CLiQ handshake — the firmware raises F60068 before the run is enabled.

Because both faults share the same underlying compensation table, fixing one without addressing the other simply defers the problem. The complete repair must validate the compensation chain end-to-end.

P50076 — The Compensation Selection Parameters

The most common commissioning error is leaving P50076[0] at the factory default after a CUD swap. The default reflects the CUD's factory bench power unit, not the installed frame. After any CUD or IFM replacement, manually set both indices to match the actual armature and field current class of the connected power section before saving to ROM with P0977 = 1.

Step-by-Step Commissioning Procedure After Fault Occurrence

1. Capture the fault buffer. Read r0949, r0948, r0947, and r50038 for every entry. Export the trace buffer if a Starter / Startdrive project is online.
2. Verify hardware. With 24 V DC electronics on and line contactor open, confirm r50038 is below 5 V. If not, repair the armature voltage sense path before proceeding.
3. Confirm rating data. Open the converter data dialog or compare the loaded parameters against the nameplate. Verify P50071 (rated armature current), P50072 (rated armature voltage), P50073 (rated field current), and P50074 (rated field voltage).
4. Set P50076 explicitly. Set P50076[0] to the armature power-unit class and P50076[1] to the field power-unit class. These indices do not auto-populate from the DRIVE-CLiQ handshake alone.
5. Disable the run command. Ensure p0840 = 0 and the safety relay chain is open so the drive cannot pulse during the next step.
6. Trigger field identification. Set P50051 = 2 (field ID only) and pulse the field ON bit. Monitor r50038 for smooth ramp and the fault buffer for any new entries.
7. Trigger armature identification. Set P50051 = 1, then issue the run command. The identification routine rotates the motor through a controlled speed and current sweep and writes fresh compensation coefficients to the IFM EEPROM.
8. Save to ROM. Set P0977 = 1 and wait for the parameter save to complete (the BOP20 shows a busy indicator for 10–60 s depending on memory size).
9. Power-cycle. Remove the 24 V DC supply for at least 30 s, restore it, then re-attempt the run command.

Reading r0949 Sub-Fault Values in the Field

The fault value at r0949 is the single fastest diagnostic indicator. Operators familiar with the BOP20 menu structure should drill into r0949 on the fault screen and record the integer value before clearing. Common values seen on SINAMICS DCM and the corresponding corrective action:

Field Sensing vs Armature Sensing — Differentiating the Failure Point

Operators frequently see the fault "move" between the two paths on identical units. The distinguishing factor is the sub-fault value at r0949. If r0949 = 2, the failure is on the field side — investigate the field winding, the field fuse, and the Hall-effect sensor on the field stack. If r0949 = 21, the failure is on the armature sense side. If r0949 = 15, the failure is in the identification logic itself rather than a hardware path; this is the value most commonly associated with a swapped CUD or a corrupted IFM EEPROM.

Field reports show that on multi-drive installations, drives running the same load with identical firmware can present different r0949 values. This points to power-section variation, not a global firmware defect — a key reason why simply downgrading firmware rarely resolves the fault.

Firmware Considerations

Several operators have reported the fault appearing only after a firmware upgrade. SINAMICS DCM firmware versions in the V2.x and later HF series changed how P50051 interacts with the IFM EEPROM write cycle counter. If the EEPROM has been written near its cycle limit, newer firmware can detect the impending write failure and raise F60068 preventively, where older firmware would have allowed a marginal write.

Downgrading firmware is a documented workaround but is not a permanent fix — the underlying EEPROM write-cycle limit must be addressed by replacing the Interface Module. If downgrade is required for production continuity, capture the current parameters, downgrade to the last known-good version, run the identification, and schedule the IFM replacement.

Hardware Verification and Replacement Criteria

Replacement of the CUD or IFM is warranted when:

• F60068 returns within one hour of a clean identification cycle.
• The IFM EEPROM read test reports a checksum error in the diagnostic menu.
• Voltage sensing shows phantom readings above the line peak with the contactor open.
• The same r0949 sub-fault value persists across two different CUDs.

Replacement of the entire power section (CUD + IFM + thyristor stack) is warranted only when both the armature and the field sub-faults persist, indicating damage to the firing boards or to the sense wiring loom inside the stack.

Prevention and Best Practices

1. Document P50076[0] and [1] for every drive in the asset register and re-verify after every CUD replacement.
2. Avoid EEPROM write cycles — never run identification more than necessary; each identification writes several blocks to the IFM.
3. Maintain spare CUDs that have been pre-loaded with the latest project and saved to ROM with P0977 = 1 to minimize commissioning time during a swap.
4. Establish a baseline of r50038 with the contactor open during commissioning; a value above 5 V on a healthy unit indicates drift.
5. Use the trace function in Starter / Startdrive to capture r50038, r50039 (armature current), and r50040 (field current) at 2 ms resolution around every fault to capture the pre-fault trajectory.

Troubleshooting Matrix

Field-Proven Recovery Sequence Summary

The fastest path to a clean running drive when both faults appear together:

1. Read r0949 and record every fault buffer entry.
2. Confirm r50038 is near zero with contactor open.
3. Set P50076[0] and P50076[1] explicitly to match the power section nameplate.
4. Run P50051 = 3 (full identification), then P0977 = 1 (ROM save).
5. Power-cycle the electronics supply for at least 30 s.
6. Issue the run command and monitor r50038 for smooth ramp to reference.

If the fault reappears on the same drive after this sequence, escalate to hardware replacement of the Interface Module rather than repeated firmware cycles.