Troubleshooting Simodrive 611 Fault 607 and Cascading Servo Module Failures on SINUMERIK 802D

The Siemens SIMODRIVE 611 drive family remains in active service on thousands of milling, turning, and grinding machines, particularly those controlled by SINUMERIK 802D, 810D, and 840D CNCs that shipped between the late 1990s and mid-2000s. One of the most confusing failure modes operators encounter is a "cascading" servo-module failure: a single LT (Leistungs-Teil / power) module fails, and within hours or days a servo module on a neighbouring axis — or even on a parallel drive bus — also fails. This article walks through the field-diagnosed root causes, the meaning of alarm 607, the role of the DC bus link, the Profibus DP coupling between modules, and the verification procedure that isolates a thermally stressed LT module from a defective servo control card.

1. Symptom Description

The reported machine presents a recurring, low-cycle failure with the following observable behaviour:

• Drive population: Two SIMODRIVE 611 LT modules ganged through a common DC bus.
  • LT module #1 (failing): Siemens MLFB 6SN1123-1AB00-0CA1 — 2-axis, 2 × 50 A peak output.
  • LT module #2 (stable): Siemens MLFB 6SN1123-1AB00-0BA1 — 2-axis, 2 × 15 A peak output.
• Servo control module: 6SN1118-0NH11-0AA0 (SIMODRIVE 611 universal servo / spindle module).
• Motor assignment:
  • Failing LT module #1 (50 A) drives the Z feed axis and the spindle (Siemens 11 Nm feed motor + 7.5 kW spindle motor).
  • Stable LT module #2 (15 A) drives the X and Y feed axes.
• Failure timing: New servo modules last approximately 20 hours of milling before failing. The machine runs only 2–3 hours per day.
• Alarm at failure: Alarm 607 (current controller at its limit) precedes the failure; alarm 609 is reported on the surviving axis (typically X) immediately afterwards.
• DC bus voltage anomaly: Standstill DC-link voltage measures ~0.1 V (effectively zero) when healthy, but rises to ~100 V when a servo module begins to misbehave. Jogging any axis triggers an alarm.
• Cabinet environment: 25–30 °C ambient with verified fan operation. Top spindle temperature during cutting: 44 °C.

2. SIMODRIVE 611 System Architecture

The SIMODRIVE 611 modular drive system separates power conversion (LT module), closed-loop control (611-D servo module), and protective / monitoring functions (ER module). Modules mount side-by-side on a shared backplane and share a common DC bus formed by the rectifier output.

Two LT modules sharing a DC bus is a standard topology used to mix current ratings (e.g. a 2 × 50 A module for spindle + Z, and a 2 × 15 A module for X + Y). Both LT modules are fed from the same unregulated DC link (~600 V DC nominal from a 3-phase 400 V supply after rectification). The 24 V and 5 V rails used by the 6SN1118 control cards are generated by an NE (Netz-Einspeisung / power supply) module and distributed across the backplane ribbon cable.

2.1 Decoding the LT Module MLFB

The order code 6SN1123-1AB00-0CA1 breaks down as follows:

Compare with 6SN1123-1AB00-0BA1: the same family at the 2 × 15 A / 30 A peak rating. Both modules share a single DC bus bar and the same NE module for logic power.

3. Alarm Reference: 607 and 609

SIMODRIVE 611 alarms are four-digit numbers reported by the 6SN1118 module back to the SINUMERIK NC and displayed on the HMI.

3.1 Alarm 607 — Current Controller at Limit

Alarm 607 means that the torque-producing current command (Md setpoint) has saturated the current controller. In SIMODRIVE 611, this alarm is generated when the actual current reaches the parameterized current limit (MD 1105 / MD 1107 family or drive-parameter equivalents) for more than the configured time window. It is always a downstream symptom — the drive is asking for more torque than either the motor or the LT module can deliver.

Common root causes:

1. Mechanical overload on the axis (binding slides, ballscrew preload, gib adjustment, lubrication starvation, chip pack in the way).
2. Motor-side problem: failed encoder, demagnetized rotor, winding turn-to-turn short, brake not releasing.
3. Wrong machine data: torque limit, current limit, or motor code set incorrectly for the connected motor.
4. Drive-side current measurement drift: defective current sensor on the LT module (failure mode: gradual thermal drift → false-high Iq reading → controller saturates at lower mechanical load).

3.2 Alarm 609 — DC Link Undervoltage / Communication Loss

Alarm 609 in the SIMODRIVE 611D alarm set indicates DC link undervoltage or, in some firmware revisions, communication monitoring error between the NCK and the drive. The 100 V DC-link reading observed at standstill — when it should be ~600 V — indicates the bus is collapsing because an inverter stage is being driven into a short or an over-current shutdown.

4. Cascading-Failure Root-Cause Tree

Because the failure migrates from one 6SN1118 module to another, the root cause is almost certainly shared rather than axis-specific. The candidate root causes, ranked by field frequency, are:

1. Failing LT module (6SN1123-1AB00-0CA1) — most likely. A 2 × 50 A LT module produces ~3 kW of dissipation at full load. Even at low mechanical load (~10 % of rated Iq), thermal stress on aged IGBT modules, dry joints on the bus-bar solder joints, or failed current-sense Hall sensors can cause intermittent short-circuit events that pull the entire DC bus down.
2. NE module / 24 V rail instability. The 6SN1122 NE module generates the 5 V and 24 V rails that power every 6SN1118 control card. If the NE module's electrolytic capacitors are aged (typical service life 8–12 years at 40 °C ambient), the 24 V rail will dip under transient load, causing 6SN1118 modules to reset or latch false alarms.
3. Profibus DP termination / address conflict. All 611-D modules participate in the same Profibus segment as the 802D NCK. A failing module can corrupt the bus, which then trips other modules' communication-watchdog timers.
4. DC bus capacitor degradation. The bulk capacitors in the LT module lose ~20 % of capacitance over 10–15 years. Under pulsed load they ring, causing over-voltage trips on the bleeder module.
5. Backplane ribbon cable / connector. The 6SN1118 module plugs into the LT module via a 50-pin ribbon cable carrying the gate-drive signals and 24 V / 5 V. Oxidation or fractured pins on this connector cause both modules on the LT to misbehave simultaneously and can also leak noise into the DC bus measurement.

5. Mechanical Inspection Checklist (Motor-Side)

Before replacing any electronics, rule out mechanical-side causes of alarm 607. Even when the failure looks electronic, the drive is reacting to a torque demand — and that demand has a physical origin.

6. Electrical Measurements (Drive-Side)

Perform the following with the cabinet powered and the drive enabled. Use a true-RMS multimeter with a 1 MHz bandwidth for the DC bus measurement.

6.1 DC Bus Voltage

Measure between the DC+ and DC− bus bars at each LT module. Nominal value with the line at 400 V 3-phase:

V_DC ≈ √2 × V_LL × 0.95 ≈ 537 V DC (lightly loaded)
V_DC ≈ 600–620 V DC (regulated by NE / ER module under load)

Recorded behaviour:

• Healthy: ~600 V at idle, briefly 580–620 V during accel/decel.
• Suspicious: ~100 V at idle when servo module begins to fail → indicates LT module short or current-sensor-induced controller saturation pulling bus down.

6.2 24 V Logic Rail

Measure at the 6SN1118 X141 connector, pins 1 (+) and 2 (−). Tolerance: 24 V ±10 % (21.6–26.4 V). A sag below 22 V under load points to a failing NE module. Replace the NE module before replacing any 6SN1118.

6.3 Phase Current Balance

With the axis jogging at a constant velocity, read MD 1719 (absolute current actual value) on each axis. Compare phase currents U, V, W via the SINUMERIK trace function:

% Slow jog axis X at 1000 mm/min
% Trace MD 1719 (I_actual) and MD 1720 (I_setpoint)
% Expected: I_setpoint ≈ I_actual within ±5 %
% If I_actual oscillates or shows saturation: mechanical or sensor issue
% If I_setpoint is at limit but I_actual tracks: parameter issue or genuine load

7. Communication Path Diagnostics

SINUMERIK 802D and 611-D communicate over Profibus DP at 12 Mbit/s (default) using the DP-V0 protocol. Every 6SN1118 module is a slave on the bus. The 802D NCK is the master.

7.1 Verify Profibus Topology

Confirm the physical layout — Profibus is a linear bus with termination, not a ring. The cable must run from the NCK out to module #1, on to module #2, and end at a termination resistor (typically switched ON at the last slave's Profibus connector, OFF on all intermediate slaves).

If a module is failing electrically, it can drag the Profibus RS-485 differential voltage below the 0.8 V threshold and cause the other slaves to lose communication. Confirm:

1. Profibus connector pins are screwed, not loose.
2. Shield is terminated at the backshell, not floating.
3. Termination switches are set correctly per the table above.

7.2 Read Bus Diagnostics from the NCK

On the 802D HMI, navigate to:

Commissioning > Bus diagnostics > Profibus DP

Look for:

• Slave diagnostic: all slaves cycling through "OK" state.
• Frame-error counter: non-zero on the failing module is expected; non-zero on healthy modules indicates bus contention.
• Cycle-time overflow: if the configured DP cycle is exceeded, the NCK will reset the affected slave.

8. Identifying the Failing LT Module

The fastest field test is to swap the 2 × 15 A LT module (spare) in place of the 2 × 50 A LT module and re-run the test program. This was offered as an option in the field report and is the correct diagnostic move.

8.1 Swap Procedure

1. Lock out and tag out the cabinet. Wait 5 minutes for DC bus capacitors to discharge to < 50 V (verify with meter at the bus bars).
2. Remove the 6SN1123-1AB00-0CA1 (2 × 50 A) LT module from the backplane.
3. Install the 6SN1123-1AB00-0BA1 (2 × 15 A) spare. Both modules are pin-compatible on the backplane, but the 15 A module will limit the spindle to ~15 A continuous — adequate for low-load milling.
4. Reconnect the DC bus bars, ribbon cables, and motor power leads.
5. Power up and verify machine data loads without 611-D alarm.
6. Run the failing program for 4+ hours.

8.2 Interpreting the Result

9. Repair vs. Replace Decision for the LT Module

SIMODRIVE 611 LT modules are repairable. The two repair paths are:

10. Repairing an LT Module Internally

If you elect bench-repair, the following subassemblies fail in this order of frequency:

1. Current sensors (Hall-effect LEM modules) on each axis. Symptoms: false-high Iq, false torque limit, alarm 607 at low load. Replace in pairs if one has failed.
2. IGBT modules. Use an ESR tester to confirm before replacement; a shorted IGBT pulls the bus down even with the gate driver inhibited.
3. Gate-driver optocouplers / gate-drive boards. Symptoms: axis runs for a few minutes then trips; thermal stress cracks the optocoupler.
4. DC bus electrolytic capacitors. Replace all with 105 °C, 5000 h or longer-life parts.
5. Cooling fans. The 2 × 50 A LT module has internal fans; bearing failure causes thermal shutdown that appears intermittent.

11. Firmware and Machine Data Verification

Confirm the firmware versions on all 6SN1118 modules match the SINUMERIK 802D compatibility matrix. Mixing firmware revisions across modules in the same drive cluster is a documented source of intermittent communication failures.

Commissioning > Drive diagnostics > Module info
→ Note firmware version of each 6SN1118
→ Cross-check with 802D commissioning manual compatibility list
→ Re-flash mismatched modules to the lowest common version

Confirm the current limit parameters for the X and Y axes are identical (the field report mentions a shared 7.9 A limit). If one axis is parameterized higher than the other, a stall on the lower-limited axis will manifest as alarm 607 — but the alarm will then propagate across the bus.

12. Verification Procedure After Repair

Run the following sequence after any LT module repair or replacement. Document each result.

1. Power up. Confirm no start-up alarms on the 802D HMI.
2. Jog X, Y, Z individually at slow speed (10 % rapid). Verify no 607.
3. Run spindle at 1000 RPM unloaded for 5 minutes. Verify motor temperature < 60 °C.
4. Run a full 4-hour milling program with representative cutting loads. Log MD 1719 for all axes and the DC bus voltage continuously.
5. After 4 hours: LT module heatsink temperature should be < 70 °C; 24 V rail should remain at 24.0–24.5 V; no 607 or 609 should occur.
6. Repeat for 5 consecutive working days. If no alarms occur, the failure root cause has been addressed.

13. Long-Term Prevention Checklist

The SIMODRIVE 611 platform typically reaches its capacitor end-of-life between years 10 and 15. Once an LT module begins to fail intermittently, the NE module is almost always a co-conspirator. Replace both at the same time.

14. Frequently Asked Questions