Troubleshooting Sinumerik 840D NCU 611D Drive Bus Fault 300500

Problem Overview

A Sinumerik 840D-controlled lathe suddenly enters a global fault state. The HMI stays alive but reports that no drive returns READY, no DC link voltage is established on the SIMODRIVE 611D line-up, and no enable signals reach the spindle or feed axes. The active alarm list points to alarm 300500 with clearing criterion 0001BH for axis 6 ("Your axis no 6 611D drive control card has hardware fault"). The operator has already performed an NCU series commissioning file restore without success, and the spindle 611D modules (C10 and C1) have been physically swapped — the alarm follows the original slot, not the spare card. Cables and connectors have been visually checked.

This profile is the classic signature of a 611D control board / NCU drive-bus problem, not a simple drive module failure. The decision tree below separates a single bad drive module from a fault located in the NCU, the drive bus, the bus terminating resistor, or the 24 V supply that powers the 611D control electronics.

Sinumerik 840D + SIMODRIVE 611D System Architecture

For a lathe with Sinumerik 840D sl, the motion-control hardware is normally arranged as follows:

• NCU (Numerical Control Unit) — NCU 561.x, NCU 571.x, NCU 572.x, or NCU 573.x with PCU/HMI on the panel. The NCU hosts the PLC (SIMATIC S7-300-compatible) and the NCK.
• MCP / HMI — operator panel and PCU 50 / PCU 70, or a TCU/Operator Panel Front (OP 010 / OP 012 / OP 015 / OP 019).
• SIMODRIVE 611D line-up — one or more 6SN1 12-1 module slots: infeed/regenerative feedback (UE / I/R), axis modules (C1, C2, … Cn) for feed and spindle axes, and the matching 611D control boards (6SN1 11-1Ax0x-0AAx) plugged into the front of each module.
• Drive bus — proprietary Siemens drive bus (NOT standard PROFIBUS-DP), wired daisy-chain between the NCU X141 and the X131 / X132 ports of each 611D control board. Terminated by a 220 Ω resistor at the last node (or activated terminator on the last control board).
• PROFIBUS DP — used separately for distributed I/O (MCP, handheld unit, I/O stations, drives on the NC side as a fallback). The drive bus and PROFIBUS are two physically separate networks.

Because the drive bus is a closed Siemens protocol at 1.5 Mbaud / 12 Mbaud (depending on NCU and 611D generation), failure of a single node, the cable, or the NCU drive-bus master can knock out the entire line-up. The NCU's drive-bus master is on the NCU module itself (X141 connector on NCU 573.x; on older NCU 561 / 571 the drive bus originates on the NCU's left flange and goes to a distributor sub-D).

Alarm 300500 — Decoding

Alarm 300500 belongs to the Drive alarm class and is raised by the NCK when the 611D control board reports an internal hardware fault, when communication with the control board is lost, or when the drive-bus telegram is invalid. The standard decoding is:

Alarm 300500 should be cross-checked with the active HMI alarm line, the diagnostics buffer on the NCK (Display > Diagnostics > NCK Trace / Alarm Log), and — if the line-up still partially responds — with the 611D seven-segment display on the affected control board. The seven-segment "1B" or "1b" on the 611D control unit confirms an internal fault, while "0." (single dot) indicates "no drive bus communication" which points at the bus itself rather than the board.

Drive Bus Topology and Signal Path

The drive bus is a shielded 9-pin D-sub daisy chain. The path is:

1. NCU connector X141 (or NCU 561/571 left-flange D-sub) — drive bus master.
2. First 611D control board X131 (incoming from NCU side).
3. Loop through the module to X132 (outgoing to next module).
4. Continue daisy chain across all 611D control boards in the line-up.
5. Last 611D control board — drive bus terminating resistor engaged (DIP switch or fixed 220 Ω terminator plug on the cable end).

If any one node shorts or locks the bus, every downstream node is lost. If the terminator is missing, double, or open, every node becomes intermittent. If the 24 V supply that feeds the 611D control electronics is missing, every control board powers up dead even if the power section is fine. Each of those three failure modes is visually similar from the HMI ("no drive ready") but the remedy is completely different.

Root Cause Hypotheses (Ranked)

Diagnostic Procedure — NCU Side

1. Verify NCU health. The NCU should display a steady RDY (ready) state with a green or off "PWR" / "SF" LED. A red SF (System Fault) LED and a blank or rapidly-blinking RDY LED indicates a hardware-level NCU fault. The "PN" and "SF" LEDs on the X120 / X130 / X140 port group are not the same as the drive-bus status — they refer to PROFINET, not the drive bus.
2. Confirm NCU firmware / series commissioning state. Use the HMI menu Startup > Commissioning > NCK & Drive and read the active series commissioning file date. The user already restored the series file; the file itself is rarely the cause when no drive is reachable at all. If the file restore wiped PLC and drive parameters, re-load the matching archive.
3. Read the NCK diagnostics buffer. On the HMI, Display > Diagnostics > NCK Trace / Alarm Log. Look for the order of alarms: 300500 with the same clearing criterion, plus any earlier 3000xx bus-related alarms (300402, 300404, 300405, 380001) that would indicate drive-bus timeout or sign-of-life errors.
4. Check the PLC alarm / status bits. The user PLC (S7-compatible) on the NCU reads drive ready bits at DB31..DB61, DBW 96 / DBB 140 (depending on firmware). All axes returning "Axis ready = FALSE" simultaneously is a strong indicator of a bus-level or supply-level problem rather than a per-axis fault.
5. Try a controlled NCU restart. Power off, wait 30 s, power on. Watch the seven-segment on the NCU during boot. A hanging boot, a stuck display, or repeated reboots indicates the NCU module is suspect. Document the boot stage number (e.g. "6" = NCK is starting, "8" = PLC starting, "9" = drives initialising). If boot hangs before drive initialisation stage 9, the NCU itself is the prime suspect.

Diagnostic Procedure — 611D Drive Side

1. Read the 7-segment display on each 611D control board. After the NCU has finished booting, each 611D control board should show "0." (idle / no fault, bus present) or an axis number. A blank display = no 24 V to the control board. "1b" or "1B" = internal control board fault. "—" or "-.-" = drive bus missing. A continuously cycling number = firmware crash on the control board.
2. Check 24 V aux supply on the control boards. Each 611D control board has a connector (X131 on the incoming side, X132 on the outgoing side) carrying shielded twisted pairs and the 24 V supply. Measure 24 V ±10 % at the connector; this rail is fed by a dedicated 24 V DC power supply in the cabinet (often a Siemens 6EP1 SITOP or the 6SN1 145 internal supply on the UE module).
3. Inspect the DC link. Measure the DC link voltage at the UE module terminals. A healthy 611D line-up reads 600 V DC at 400 V AC line, or 270 V DC at 230 V AC line. Zero volts with the infeed powered indicates a missing line voltage, a tripped pre-charge, or a failed infeed module.
4. Verify the ready chain. The infeed "Ready" terminal (terminals 663 / 65 / 9 on the 6SN1145) must be high. The 611D axis modules each have their own ready relay chain (X121 connector on older units, X21 on newer). A broken relay in the chain disables all downstream modules — this is a frequent root cause of "no drive ready on anything" and is NOT detected as a 300500.
5. Check the line contactor and emergency stop chain. If the EMERGENCY STOP circuit or the line contactor is open, the infeed is de-energised and no DC link is built. Verify 24 V at the contactor coil and continuity of the E-stop loop through MCP, external guards, and the NCU X121 I/O.

Cable, Connector, and Termination Verification

Cable and connector faults are the most common cause of complete drive-bus loss following a period of normal operation. The drive bus carries a Siemens-proprietary protocol and is extremely sensitive to:

• Loose or oxidised D-sub thumbscrews. Re-tighten to finger-tight plus a quarter turn; do not exceed the screw torque limit.
• Broken shield continuity. The shield must be 360° bonded at every connector body — the shield pigtail must be folded back over the cable jacket and clamped under the connector housing, not soldered to a single pin.
• Terminator state. The last 611D control board on the daisy chain must have the terminator active (DIP switch "ON", or the terminator plug fitted). The terminator is a 220 Ω resistor between pins 3 and 8 of the D-sub (Siemens-spec). A missing terminator causes intermittent or no communication; a doubled terminator (two terminators active) attenuates the bus so that only the closest nodes handshake.
• Pin-to-pin continuity check with a multimeter. With the cabinet de-energised, lift the connector at the NCU end and the last 611D end, and check the loop: pin 3 ↔ pin 3, pin 8 ↔ pin 8, shield ↔ shield. Also check for shorts between pins 3 and 8, and between any signal pin and shield.
• Routing and EMC. The drive bus must not run parallel to VFD power cables within 200 mm for any length. If a recent cabinet move has shifted the harness, the bus may now be next to a 400 V power cable.

NCU Replacement Decision Matrix

Before replacing the NCU module, all of the following must be true. If any test passes, do NOT replace the NCU — fix the underlying cause first.

611D Control Card Replacement Procedure

If the 611D control board for axis 6 is the actual faulty part, the swap is a hot-swap-capable operation on most 611D modules, but only with proper precautions.

1. Identify the exact MLFB of the control board currently fitted (e.g. 6SN1118-0AA11-0AA1 for a two-axis control unit, or 6SN1118-0AD11-0AA1 for a single-axis high-resolution variant). Match the replacement exactly — Siemens does not cross-substitute freely across the A/B/D/E generations.
2. Record the drive parameters to the HMI archive before any hardware swap: Startup > Commissioning > Drive > Save / Restore. The drive parameters live in the control board's NV memory; swapping a board without backup means re-commissioning from the series file and possibly re-doing the measuring-system / encoder offset routine.
3. Open the cabinet and power down the infeed (line contactor off) AND the 24 V control electronics. Wait 5 minutes for the DC link to discharge to safe levels (verify with a meter at the UE module — below 50 V DC is acceptable).
4. Remove the four retaining screws on the front of the 611D control board, lever the board out of the slot with the integrated handles, lift it clear. Do not pry against the housing.
5. Fit the replacement board, hand-tighten the four screws, restore 24 V, then re-energise the infeed. The NCU will re-detect the new control board on the drive bus and request a parameter re-load automatically if the saved series file is consistent.
6. Run the axis-specific measuring system and referencing routine. On a lathe, also re-check the C-axis spindle encoder offset and the spindle zero-pulse position.

Commissioning and Verification Steps After Repair

1. Clear the alarm buffer and the PLC error buffer. Display > Diagnostics > Alarm Log > Clear and PLC > Diagnostic Buffer > Clear.
2. From the HMI, run Startup > Commissioning > Drive > Identify all drives. The NCU must show a green "OK" for every configured drive object (axis 1, axis 2, … axis N, spindle 1, spindle 2 if present).
3. Check the drive-ready bits in the PLC status (DB31, DBW 96 / DBB 140 area for feed axes, DB61 for the spindle). All must be 1 within 30 seconds of NCU boot completion.
4. Run a controlled axis motion test in JOG mode with reduced feed override. Monitor the following for at least one minute each: position actual value, velocity actual value, current / torque actual value, and DC link voltage.
5. Run a spindle speed test at low RPM, then at 50 %, then at full speed. Listen for abnormal harmonics, check the spindle encoder return on the HMI position display.
6. Run an automatic test program (a simple tool-change, a single-axis move, a G0 cube) and verify no alarms are raised for at least 30 minutes of continuous operation.

Preventive Recommendations

• Schedule an annual drive-bus connector re-torque and visual inspection. Even a single loose thumbscrew will produce intermittent faults that are hard to reproduce.
• Maintain a verified backup of the NCK series commissioning file and the drive parameters (the .ARC archive from Startup > Commissioning > Save). Store the archive on a USB drive that is regularly refreshed; a corrupt archive is a common reason for "restore didn't work".
• Fit a UPS on the 24 V supply that feeds the 611D control boards. A brownout on the 24 V aux rail can lock up the control boards with symptoms similar to 300500.
• Record every 300500 occurrence in a maintenance log with date, time, alarm clearing criterion, axis configuration, and any recent mechanical work. Recurrence on the same axis after the 611D card is replaced suggests a deeper drive-side issue (motor encoder, motor cable, or motor itself).
• Keep at least one spare NCU module with the correct MLFB and firmware (with the appropriate license dongle / CF card) on the shelf for a 6-12 month-old machine. The lead time on a matching NCU can be several weeks and a lathe down for that long is rarely acceptable.

When to Stop and Call Siemens Service

If after isolating the drive bus and the 24 V supply, the 611D control boards still do not respond and the NCU shows a healthy boot, the failure is either inside the NCU's drive-bus master (hardware on the NCU module) or a configuration mismatch between the NCK series file and the physical line-up. At that point:

• Cross-check the machine's series commissioning file against a verified-good backup from a sister machine of the same MLFB and the same NCU firmware version.
• Open a Siemens service request with the SINUMERIK 840D sl hardware serial number, the NCU MLFB and firmware version, the active alarm text and clearing criterion, and the last clean state of the machine.
• Do not re-load random series commissioning files from other machines — the axis configuration and encoder data are machine-unique and writing the wrong values can damage the spindle or feed motors on a real motion attempt.

Field-Engineering Notes

• The 7-segment display on the 611D control board is the single best field tool. "0." = bus OK, idle. "-." = bus error. "1B" = internal control board fault. "11" = under-voltage. "12" = over-voltage. "33" = encoder error. Always read it cold-boot, then again after the NCK has had 30 seconds to send configuration telegrams.
• Alarm 300500 with different clearing criteria point at different root causes: 0x0B = bus timeout (cable), 0x1B = control board hardware (module), 0x2B = firmware mismatch (configuration), 0x3B = encoder (motor-side). Always decode the clearing criterion, do not treat all 300500 as the same fault.
• Replacing the NCU does not require re-licensing only if the new NCU is a like-for-like MLFB and firmware version, and the CF card / CompactFlash with the SINUMERIK license is moved to the replacement NCU. A different NCU variant usually requires a re-license.