Resolving Sinumerik 840D Simodrive 611D Alarm 300200 Drive Bus Fault on ODM11 Modules

After a controlled shutdown of a Sinumerik 840D PowerLine controller driving a Simodrive 611D axis/spindle rack, operators frequently encounter alarm 300200 "DRIVE BUS" hardware fault on a subset of the drive modules (for example, three ODM11 modules out of six) and a complementary "DRIVE MISSING" alarm on the remaining modules. Because the failure appears only after a power-off/power-on event and not during steady-state operation, the root cause almost always sits in the physical drive-bus layer: a missing/loose connector, a damaged fiber-optic segment, a removed bus terminator at the last module in the chain, or a wrong node address that the NCK only re-evaluates on boot.

This reference consolidates the field-proven diagnostic workflow for alarm 300200 on Sinumerik 840D PowerLine with Simodrive 611D, including ODM11 module identification, drive-bus topology, termination rules, NCK-side parameter checks, and the verification procedure required to clear the fault without a controller restart loop.

1. Alarm 300200 Definition and Symptoms

Alarm 300200 is the NCK-side representation of a drive-bus hardware fault on the Simodrive 611D system bus. It is generated when the numerical-control kernel (NCK) cannot complete a poll cycle over the drive bus, or when a drive that is configured in the axis/slot map is physically absent from the bus. Siemens publishes the alarm in the SINUMERIK 840D sl/Diagnostics Manual under the cluster 300200–300299 – Drive faults. The alarm text in the HMI is short: DRIVE BUS or DRIVE MISSING depending on the failure mode:

The fact that three modules report DRIVE BUS and three different modules report DRIVE MISSING on the same rack is the classic signature of an open fiber-optic loop between the two halves of the daisy chain. The modules downstream of the break (typically three in a 6-module Simodrive 611D line-up) cannot be polled, so the NCK raises DRIVE MISSING for each of them. The module whose receiver pin is disconnected raises DRIVE BUS because it sees an upstream interruption.

2. System Architecture: 840D PowerLine + Simodrive 611D Drive Bus

The 840D PowerLine controller is paired with a Simodrive 611D drive line-up. The drive bus is a point-to-point fiber-optic ring between the NCK's drive-bus interface and every drive module. The protocol is a Siemens proprietary, PROFIBUS-DP-based serial bus running at 12 Mbaud. Each module has two fiber ports (in / out); the cable from the NCK enters the first module, exits to the second, and so on, with the last module terminating the line.

Figure 1 — Typical Simodrive 611D drive-bus topology. The outbound fiber path (NCK → #1 → #2 → #3) is intact, but the return path is interrupted at ODM11 #6 (terminator end). Modules #4, #5, #6 cannot be polled, producing DRIVE MISSING on the NCK side, while modules #1, #2, #3 report DRIVE BUS because the ring is broken.

3. ODM11 Module Identification

ODM11 in this context refers to a Simodrive 611D drive module from the 6SN1 family – typically a feed-drive (FDD) or main-spindle-drive (MSD) module using the 6SN1118-0DM11-0AA1 control insert. Each module hosts the closed-loop regulator for one motor (or, in dual-axis variants, two motors) and contains the fiber-optic transceivers that couple it to the upstream/downstream neighbors. The relevant connectors and indicators for bus diagnosis are:

4. Root Cause Analysis: Why a Power Cycle Triggers 300200

The bus was almost certainly running correctly before the shutdown, so the question becomes what changed in the cold-start path? The most common root causes, in descending order of frequency on 840D PowerLine with 611D, are:

1. Bus terminator removed or left OFF at the last module. During maintenance, a technician may have unplugged the fiber to swap a module, then re-cabled only the outbound side. The terminator on the last module is implemented by a DIP switch on the module itself, not by an external resistor. A floating terminator produces the exact "half the modules alive, half missing" symptom on next power-up.
2. Fiber-optic connector contaminated or unseated. A fiber that was barely latched can survive vibration while the line is live (the optical budget has headroom) but loses too much power during the inrush/charging transient of the DC link. The NCK completes POST, attempts a poll, and times out – alarm 300200.
3. One drive module failed to power up. A blown DC-link fuse, a missing 24 V to the control insert, or a stuck fan on an MSD module can keep the bus transceiver in reset. The NCK sees that address as missing.
4. Module address (DIP) changed inadvertently. A module swapped during a previous intervention may have been reseated with a different S1 setting, or two modules now share an address. The NCK then sees the second copy as a collision and the third as missing.
5. NCK-side machine data corruption. Less common, but a CF-card / SRAM battery exhausted during the shutdown can reset MD13010 to defaults, mapping axes to bus addresses that no longer match the physical layout.

Because the symptom is reproducible on every cold start, a single bench session is enough to isolate the cause. The diagnostic procedure below is built for that workflow.

5. Diagnostic Procedure (Step-by-Step)

5.1 Pre-checks (controller powered OFF, locked out)

1. Lock out the main disconnect. Wait 5 minutes for DC-link discharge. Verify 0 V at the DC bus bars with a Cat IV meter.
2. Open the Simodrive 611D cabinet. Inspect the complete fiber-optic loop visually: every X461 and X462 must have a connector latched with the bayonet-style F-SMA coupling fully locked (a 1/4 turn past the click).
3. Look for kinked fibers, fibers routed across sharp sheet-metal edges, or fibers running parallel to VFD power cables for > 30 cm without separation. A fiber run within 100 mm of a 611D line reactor for any distance can pick up sufficient EMI to be marginal on cold start.
4. Unplug each fiber one at a time and inspect the ferrule with a 10× loupe. Any contamination, scratch across the core, or cracked ferrule end-face is grounds for re-terminating that fiber with a new F-SMA connector (Siemens 6FX2003-0SU07 or equivalent).

5.2 Powered-up inspection (HMI diagnostic screens)

1. Power the cabinet. Go to Commissioning → Drives/Drives on the HMI.
2. Open the drive list. The three DRIVE BUS modules will appear in red with a bus error code; the three DRIVE MISSING modules will appear with a blank/grey status.
3. Navigate to Diagnostics → Bus diagnostics. Confirm the NCK sees the first 1–2 modules but loses contact after the third. This is the canonical "break at module N+1" pattern.
4. Open the alarm log (HMI soft key ALARM → SELECT). Note any companion alarms: 300201 (axis-specific drive fault), 300500 (encoder), 25201 (axis standstill), or 380001 (PROFIBUS). Their presence narrows the cause to the addressed module rather than the bus medium itself.

5.3 Bus termination verification

The terminator is internal to the last module in the chain. For 6SN1118-0DM11-0AA1, the DIP switch block S1 is laid out as follows (verify against the sticker on the module faceplate, since Siemens has shipped at least two revisions):

Confirm with a continuity / DIP-setting check that only one module in the rack has S1-7 = ON. If two modules have the terminator on, the bus signal integrity is destroyed and you get a symptom similar to the one in this case. If zero modules have it on, the bus does not close and the NCK loses all drives after the first.

5.4 NCK parameter cross-check

From the HMI, in Commissioning → Machine data, dump the current values of:

Each axis name in MD13100 must reference a bus address that physically exists. A common field mistake is restoring an old archive after a module swap, which leaves the axis map pointing to a slot the new hardware no longer occupies. If a parameter was changed, restore the last known good backup (the .arc file on the CF card dated before the shutdown).

5.5 Optical-power budget check

Use a Simodrive fiber-optic power meter (Siemens 6FC5247-0AA02-0AA0, or a generic F-SMA 850 nm meter). The required power at each receiver X461 is in the range –24 dBm to –10 dBm. If any segment reads below –24 dBm, that fiber is the prime suspect: replace the F-SMA connectors on both ends and re-test.

6. Repair Actions

Apply the corrective actions in this order; each is independent and most cases resolve within the first two steps.

1. Re-seat and clean every fiber. Pull each connector, blow out with filtered compressed air (< 2 bar), wipe the ferrule with a lint-free swab and IPA, re-latch. Do not use general-purpose solvents – only >99 % IPA.
2. Set the bus terminator correctly. ON on the last module only. OFF on every other module. If you are unsure which module is last, follow the fiber from the NCK through the rack; the module whose X461 is connected but whose X462 is empty is the last.
3. Restore the axis map. Compare MD13100 against the physical layout; reload the matching archive.
4. Replace damaged fibers. Use only Siemens-approved 6FX2-series plastic optical fiber (POF) at 1 mm core. Standard 62.5/125 glass fiber is not compatible with the F-SMA ports on 6SN1118 modules and will permanently damage the transceivers.
5. Replace a faulty module. If a module's H1 LED stays off while its upstream neighbor's H2 LED is on, the module's receiver has failed. Replace the module, re-apply the DIP address, and re-enter its drive parameters (MD13020 / MD13030).

7. Verification Procedure

After the corrective action, run a controlled verification before returning the machine to production.

1. Power cycle the cabinet. Wait for the NCK to complete its POST. Confirm on the HMI that the drive list shows every module green – no red bus-error icons.
2. Open Diagnostics → Bus diagnostics again. The "lost contact" message must no longer be present. The bus cycle time should be in the 1–2 ms range; anything > 5 ms indicates a marginal fiber that will fail again under load.
3. Cancel the alarm with CANCEL on the HMI. The alarm 300200 must clear with the cause "reset by HMI" and must not re-appear after a follow-up NCK reset.
4. Jog each axis in JOG mode at low speed (5 % rapid). Verify that the position feedback follows the command without 25050 (contour monitoring) or 300500 (encoder) alarms.
5. Run the spindle through its full speed range, including the field-weakening range for an MSD module.
6. Run a part-program with at least one tool change and at least one G0/G1 transition per axis. Watch the alarm log for any 300xxx recurrence.

8. Related Alarm and Fault Code Matrix

9. Preventive Maintenance Recommendations

Alarm 300200 is a physical-layer fault. The right prevention program is a periodic inspection, not a parameter change.

• Annual fiber inspection. Clean every F-SMA connector with an IPA swab. Replace any fiber showing > 1 dB loss growth on a 5-year cycle, or immediately after any panel opening that involved the fiber bundle.
• Cabinet housekeeping. Verify that no cable tie has been added across a fiber bend radius, that no copper power cable has been re-routed across the fiber bundle, and that the cabinet's cooling fans are not blowing dust onto the F-SMA ports.
• Module-swap procedure. Any drive module replacement should be done with the line isolated, and the DIP switch setting of the new module should be cross-checked against the sticker on the old module before power is reapplied. Photograph the S1 block before pulling the module.
• Archive integrity. Verify that the NCK's CF-card battery is healthy at every major PM. A dead battery on shutdown is a frequent silent cause of "axis map reverted to default" symptoms that mimic a bus fault.
• Cable labeling. Label every fiber with its source and destination, written on a tag behind the bayonet coupling, so that a re-cable during a future intervention cannot accidentally swap inbound and outbound fibers.

10. Quick Field Triage Decision Tree

Figure 2 — Triage logic for alarm 300200 on Sinumerik 840D PowerLine. The mixed BUS / MISSING signature (this case) almost always points to a broken fiber segment or a missing/wrong terminator on the last module.

11. Frequently Asked Questions