Simodrive 611D X141/X341 Drive Bus Wiring and NCU Configuration

Overview

The Siemens Simodrive 611D is a modular digital drive system designed for high-performance machine tool applications. It operates as the power and servo control stage for Sinumerik 840D and 810D CNC controllers. The system is split between the power modules (line infeed / I/R module, motor-side power stages) and the digital control boards that plug onto the front of each power module. The NCU (Numerical Control Unit) communicates with each control board over the proprietary Siemens drive bus, a high-speed serial link that carries setpoints, actual values, parameterization, and diagnostics in real time. Field engineers maintaining or commissioning these systems must understand the drive bus topology, the X141/X341 connector roles, the cable specification, the termination rules, and the LED indicators on the control board to keep the machine reliable.

This reference covers the wiring and topology of the 611D drive bus, the role of X141 and X341 on 1-axis and 2-axis control boards, the bus termination rules, and the standard commissioning procedure for a daisy-chain of drives connected to a Sinumerik 840D NCU. It targets engineers maintaining older 840D-based machines still in production, retrofit projects where the 611D platform must be kept on a verified NCU, and bench-rebuild shops that stage spare 611D cabinets before delivery.

System Architecture

The Sinumerik 840D NCU generates the motion commands for each axis. For every axis, the NCU computes position setpoints, velocity feedforward, and torque commands from the part program and the interpolator. The NCU packages these setpoints into serial telegrams on the drive bus. Each 611D control board on the bus receives the telegrams addressed to its axes, runs the current and velocity control loops locally, and commands the IGBT power stage mounted beneath it. The motor's resolver or encoder returns feedback through the same control board, closing the loop locally while forwarding actual values back to the NCU for display, monitoring, and follow-up interpolation.

The drive bus is electrically isolated from the NCU and uses differential signaling on a shielded twisted-pair cable. Up to six axes (three 2-axis boards, or a mix of 1-axis and 2-axis boards) typically share one drive bus segment. The exact maximum depends on the NCU firmware revision and the total cable length. The NCU is the only bus master; every control board is a slave and only transmits when polled.

Component Identification

Each 611D control board carries a Siemens MLFB (Machine-Readable Product Code, the Siemens order number) printed on the front label. Knowing the exact MLFB is essential when sourcing spares and when reviewing Siemens compatibility matrices, because firmware revisions and the supported power stages vary across the 6SN1118 family. The MLFB suffixes in particular encode the firmware version, performance class, and connector options.

The reference machine uses NCU MLFB 6FC5110-1BB01-0AA1, which is a Sinumerik 840D NCU. Confirm the firmware version on the NCU before any commissioning step, because drive bus timing, supported axis counts, and alarm number assignments are firmware-dependent. Firmware version is visible on the HMI boot screen and via the NCU service menu.

X141 and X341 Connector Roles

The 611D control board exposes two 9-pin D-sub connectors for the drive bus. Their roles depend on the board variant and on the board's position in the daisy chain. On the 1-axis (6SN1118-0DG23-0AA0) and 2-axis (6SN1118-0AE11-0AA1) boards used with the 840D, the connectors are designated as follows:

The 9-pin shell carries the cable shield through a metal backshell with 360-degree shield termination. The mating cable must use a metallized plastic or metal hood with a strain relief that bonds the cable shield to the connector shell at both ends. Improper shield termination is the single most common source of EMC-related drive bus faults and surfaces as intermittent CRC alarms rather than a hard wiring fault.

Drive Bus Topology

The drive bus is a linear, daisy-chained bus. The NCU is the master. The first 611D control board taps the bus from the NCU. Each subsequent control board takes the bus from the upstream board and forwards it to the next. The last physical node on the chain must terminate the bus with a Siemens terminator plug or with the integrated termination jumper on the final board.

Key topology rules from Siemens commissioning manuals:

1. The bus must be a single linear segment. Star, tree, or stub branches are not permitted.
2. Cable stubs from the bus to a control board are not allowed. The cable enters the connector, and the bus exits the second connector of that board.
3. The total cable length is limited per Siemens documentation. For a 1.5 Mbaud segment the practical maximum is in the tens of meters. Refer to the NCU hardware manual for the exact figure applicable to the installed firmware revision.
4. The shield must be continuous across the segment and bonded to the connector shell at every node, with 360-degree backshells at both ends of every cable.
5. The terminator is a Siemens part matched to the bus impedance. Third-party 120-ohm terminators must not be used.

Pin Configuration

The 9-pin D-sub cable carries the drive bus as a single differential pair plus the shield. Per Siemens 611D documentation, the pinout follows the company's standard drive bus assignment. Verify the exact assignment against the wiring diagram shipped with the control board before wiring, because Siemens has shipped variants with reserved pins reassigned in earlier hardware revisions.

Communication Protocol

The drive bus carries cyclic and acyclic telegrams. Cyclic telegrams repeat every position controller cycle (typically 2 ms or 4 ms depending on the NCU configuration) and include setpoint and actual values for every axis. Acyclic telegrams carry parameter read/write, firmware upload, and diagnostic data, and run in the interstices between cyclic frames.

The bus is driven by the NCU as the master. Each control board listens continuously and only transmits when the NCU polls its address. Address assignment on most 611D boards is automatic and follows the physical order on the bus, but explicit addressing can be forced by DIP switches on the board or by parameterization in the NCU. Refer to the Siemens commissioning manual for the specific board variant to confirm.

Setpoint data exchanged per cycle includes:

• Position command (increments, 32-bit signed)
• Velocity feedforward (per NCU scaling)
• Torque/force command (per drive scaling)
• Digital outputs to the drive (controller enable, drive inhibit, ramp-stop)

Actual value data returned per cycle includes:

• Position actual (encoder feedback, 32-bit signed)
• Velocity actual (computed from position increment)
• Current actual (per drive scaling)
• Status word, warnings, and alarm bits
• Diagnostic counters (CRC errors, telegram failures, lost telegrams)

Cable Specification

Use only Siemens 6FX2 series drive bus cable or its equivalent. The cable must be shielded twisted pair with a characteristic impedance matched to the Siemens terminator. Field substitutes (Cat 5, Profibus cable, generic shielded twisted pair) frequently work at short distances during bench tests but fail under production conditions because of impedance mismatch, shield construction, or capacitance.

Strip the outer jacket only as far as required for the backshell. Do not fold the shield back over the jacket; let the backshell clamp directly on the braid for a 360-degree bond. Pull-test every connector after assembly; a loose backshell is a guaranteed intermittent fault.

Termination

The last node on the bus segment must terminate the line. Siemens supplies dedicated terminator plugs for the 611D drive bus that match the cable impedance. The terminator plugs into X341 of the last control board, leaving X141 unused at that node.

If the last control board has onboard termination jumpers (varies by board variant), the jumper must be engaged on the last board and the external terminator plug omitted. Engage exactly one terminator per segment.

LED Indicators and Status Diagnostics

The front of the 611D control board carries a small array of LEDs that report bus and drive status. While exact LED labels vary by board variant, the typical mapping is:

Read the LED combination together with the alarm buffer on the HMI. A green LED without alarm buffer entries and a non-responsive axis typically indicates an NCU parameterization issue rather than a bus wiring issue; a green LED with persistent alarm entries points to a soft fault in the firmware configuration. A red blinking LED with or without alarms is almost always physical layer: cable, terminator, or board.

Commissioning Procedure

Commissioning follows the Siemens standard sequence. Use this procedure when installing a new control board or when tracing a drive bus fault on an existing machine.

1. Lock out and tag out. Open the main disconnect and verify zero energy at the line side. Wait for the line module's DC link to discharge below 50 V before touching any drive module hardware.
2. Confirm MLFBs. Verify each control board MLFB against the machine's parts list. Confirm the NCU MLFB matches the machine's documentation. Record the firmware version visible on the NCU boot screen.
3. Inspect the wiring. With power locked out, visually verify each X141 and X341 connection. Confirm the cable is the Siemens drive bus type, that the shield is bonded 360 degrees at both ends, and that no strain is on the connector.
4. Verify the topology. Walk the bus from the NCU. Each board's X141 must come from the upstream node; each board's X341 must go to the next board's X141. The last board's X341 must hold the terminator.
5. Power up the line module. Close the main disconnect and apply 24 VDC control power. Confirm the line module charges (typically signaled by a green charging LED on the I/R module).
6. Power up the NCU. Boot the NCU. Read the drive bus topology from the NCU diagnostics or HMI screen. Confirm every expected axis appears and the address order matches the physical bus order.
7. Check the alarm buffer. Note any alarm numbers that appear. Common bus-related alarms at first commissioning are 380001 (drive bus CRC), 380500 (drive bus connection failed), and 380501 (drive bus timeout).
8. Enable each axis individually. Use the NCU's axis commissioning screen to enable one axis at a time. Verify that the green LED on the corresponding control board lights steady.
9. Run an axis test. Use the HMI's axis test screen to command a small motion (typically +/- 1 mm at low velocity). Verify position feedback follows the command and that no new alarms appear.
10. Document and back up. Save the NCU commissioning archive to a service PC. Label the terminator location on the cabinet door wiring diagram so the next engineer sees the topology at a glance.

Troubleshooting Matrix

Specifications

Safety and Lockout Considerations

All commissioning and troubleshooting work on the 611D drive system must be performed with the cabinet locked out per local electrical safety procedure. The DC link on the line module stores lethal energy for several minutes after the line voltage is removed; verify the DC link voltage is below 50 V before touching any power module. Use a properly rated measurement instrument and a known-good test point before assuming the link is discharged.

Confirm any external 24 VDC supplies feeding the control boards are also locked out. Many field engineers forget the control supply and receive drive bus alarms that resolve themselves only when the 24 V is removed, leading to misdiagnosis as a wiring fault. Verify that the line module, the 24 V control supply, and any external axis enable circuits are all de-energized before opening the cabinet.

Keep one hand in a pocket when probing the DC link or any high-voltage section. Wear the PPE required for the cabinet's arc-flash label. Never assume that a green LED on a control board means the drive is safe; a board can have bus communication and still hold a motor in a torque-producing state.

Migration and Replacement Considerations

The 611D platform is legacy and Siemens has shifted new production to the Sinamics S120 drive family. Existing machines in service can be kept running on the 611D platform, but field engineers planning multi-year support should weigh three points:

1. Spares availability. MLFBs in the 6SN1118 family remain orderable through Siemens spare-parts channels, but lead times for older revisions can extend. Confirm the active MLFB on stock before committing to a repair timeline.
2. NCU compatibility. The 840D NCU and the 611D control boards are paired through firmware. Mixing newer NCU firmware with older control board firmware, or vice versa, can produce alarms that look like wiring faults. Verify the firmware compatibility matrix in the NCU documentation before updating either side.
3. Migration path. If a full migration to Sinamics S120 is in scope, drive bus topology translates to DRIVE-CLiQ on the new platform. The cable plant and connector discipline can be reused in spirit (linear daisy-chain, single terminator, 360-degree shield bonding) but the connectors, cable type, and protocol all change. Treat any migration as a new commissioning, not a wire swap.

For existing 611D installations, the highest-value maintenance investments are periodic cable inspection, terminator replacement on a fixed schedule, and archiving of the NCU commissioning data after every parameter change. The drive bus is robust to wiring faults only when the topology rules are followed exactly.

FAQ