Problem: Connecting a DRIVE-CLiQ Motor to a Simodrive 611 (DB25) Input
A common retrofit scenario in brownfield Siemens installations: a spare or replacement motor is on hand, but its encoder terminates in a DRIVE-CLiQ RJ45 connector (8-pin, gigabit physical layer, proprietary Siemens protocol), while the installed drive is a Simodrive 611U or 611A with a 25-pin D-Sub (DB25) encoder input. The field attempt to solve this with a passive DB25-to-RJ45 breakout or pin-to-pin wiring harness fails: the drive posts an encoder fault (F31110 / F31111 / F31117 on the 611D family, or "encoder initialization error" on the 611U), the motor shaft is invisible to the controller, and the question becomes whether any physical or protocol converter exists in the Siemens catalog that can make the new encoder visible to the legacy drive.
The short answer: a direct cable will never work because DRIVE-CLiQ is not a pin-compatible alternative to sin/cos, EnDat, SSI, or Hiperface. It is a digital, deterministic, real-time protocol that carries the encoder's raw data, type plate, nameplate, and diagnostic telemetry inside Ethernet frames. A DB25 connector on a Simodrive 611U/611A carries raw analog or RS-485 signals. Bridging the two requires either a Siemens drive or sensor module on the DRIVE-CLiQ side, or an encoder swap on the motor side.
Simodrive 611 Family: Which Variant You Have Determines the Path
Before touching any cable, identify the Simodrive variant. The three sub-families have radically different encoder interfaces.
| Variant | Encoder Interface | Native DRIVE-CLiQ? | Connector Type |
|---|---|---|---|
| SIMODRIVE 611A (analog) | Resolver or sin/cos incremental | No | DB25 or Siemens flange connector |
| SIMODRIVE 611U (universal) | Resolver, sin/cos, EnDat 2.1, SSI, Hiperface (configurable per firmware) | No | DB25 (X411 / X412 depending on axis) |
| SIMODRIVE 611D (digital) | DRIVE-CLiQ, sin/cos, EnDat, SSI via Sensor Modules | Yes (X202 / X203) | RJ45 (DRIVE-CLiQ) on chassis; DB25 only via SME |
Reference: SIMODRIVE 611 digital Function Manual (Siemens), SIMODRIVE 611 universal / analog Function Manual. The 611D is the only sub-family that accepts DRIVE-CLiQ natively. On 611D, port X202 is a DRIVE-CLiQ RJ45 jack; the motor with a built-in DRIVE-CLiQ interface plugs directly into X202 with a 6FX8002 series cable — no adapter required. If the drive in the cabinet is a 611D and the motor already has DRIVE-CLiQ, the field problem described in the source post does not exist.
Why a Direct DB25 ↔ RJ45 Cable Adapter Cannot Work
Mapping the physical connector pin-for-pin is necessary but not sufficient. The deeper incompatibility is the signal protocol, summarized below.
| Property | DB25 on 611U/611A | DRIVE-CLiQ (RJ45) |
|---|---|---|
| Signal type | Analog differential (sin/cos, resolver) or RS-485 (EnDat, SSI, Hiperface) | 1000BASE-T / 100BASE-TX Ethernet physical layer with Siemens proprietary upper layers |
| Data direction | Bidirectional for absolute protocols; one-way clock + data | Bidirectional, full-duplex, real-time cycle 31.25 µs |
| Power on cable | Typically 5 V or 11 V supplied by drive to encoder | 24 V supplied by drive to encoder/Sensor Module |
| Nameplate / type-plate | Read once at power-on (EnDat 2.1 / Hiperface) | Stored electronically in the encoder, transferred to drive on every power-up |
| Latency | Asynchronous to drive cycle | Synchronized to drive sampling clock (P1150 / position controller cycle) |
| Fault telemetry | Bit in serial protocol | Detailed alarm structures, temperature, vibration |
Because the drive's encoder port expects raw waveforms or EnDat/SSI/Hiperface frames, it has no Ethernet PHY, no MAC, and no TCP/IP or PROFINET stack on that DB25. Even if the 8 RJ45 pins are perfectly soldered to the right DB25 pins, the drive will read DC or noise on the analog inputs and flag "encoder signal too small" or "encoder communication error." The cable adapter fails for the same reason an HDMI-to-VGA passive cable does not work: the link layer is different.
DB25 Encoder Pinout Reference (Simodrive 611U/611A, X411 / X412)
Pinout varies by configured encoder type. The table below shows the most common 611U assignment when configured for sin/cos 1 Vpp incremental with TTL/HTL reference marks. Always cross-check with the drive's parameter p0400 (encoder type selection) and the project documentation, because Siemens supports multiple modes per port.
| DB25 Pin | Signal (sin/cos 1 Vpp + reference) | Function |
|---|---|---|
| 1 | A+ (cos+) | Incremental track A, positive |
| 2 | A- (cos-) | Incremental track A, negative |
| 3 | +5 V / +11 V sense | Encoder power return / sense |
| 4 | R+ (ref+) | Reference mark, positive |
| 5 | R- (ref-) | Reference mark, negative |
| 6 | B+ (sin+) | Incremental track B, positive |
| 7 | B- (sin-) | Incremental track B, negative |
| 8 | Reserved | — |
| 9 | Reserved | — |
| 10 | P encoder (5 V / 11 V) | Encoder power supply output |
| 11-15 | Reserved / shield | — |
| 16 | Data+ (EnDat / SSI / Hiperface) | Serial data, positive |
| 17 | Data- (EnDat / SSI / Hiperface) | Serial data, negative |
| 18 | Clock+ (EnDat 2.1 / SSI) | Serial clock, positive |
| 19 | Clock- (EnDat 2.1 / SSI) | Serial clock, negative |
| 20 | Shield | Cable shield, chassis GND |
| 21-25 | Reserved | — |
Reference: Siemens SIMODRIVE 611U Function Manual section "X411/X412 encoder connection," support.industry.siemens.com 108140719.
DRIVE-CLiQ RJ45 Pinout and Cable Specification
DRIVE-CLiQ uses a standard 8P8C (RJ45) jack but the cable is not Ethernet. Siemens specifies 6FX8002-2DCxx (pre-fabricated, length-encoded in the part number suffix) or 6FX2008-1DCxx for hybrid cables that include 24 V power cores. Standard CAT5e is allowed only for very short cabinet hops when a Siemens DRIVE-CLiQ patch cable is used; never for motor pigtails that carry power.
| RJ45 Pin | Signal (per Siemens 6FX8002 spec) | Wire color (Siemens pre-fab) |
|---|---|---|
| 1 | TX+ (DRIVE-CLiQ data out) | Yellow |
| 2 | TX- (DRIVE-CLiQ data out) | Orange |
| 3 | RX+ (DRIVE-CLiQ data in) | White |
| 4 | Reserved / P24 (in hybrid cable) | — |
| 5 | Reserved / M (in hybrid cable) | — |
| 6 | RX- (DRIVE-CLiQ data in) | Blue |
| 7 | M (0 V) (in hybrid cable) | White/Green |
| 8 | P24 (+24 V) (in hybrid cable) | Brown |
The shield terminates to the RJ45 shell and must be bonded to chassis at both ends via the metalized connector housing. Pinout reference: SINAMICS S120 Function Manual — DRIVE-CLiQ topology.
Signal Architecture: From Analog Sin/Cos to Digital DRIVE-CLiQ
A block-diagram view clarifies why a passive adapter cannot bridge the gap. The DB25 side ends in an FPGA that samples analog waveforms (or a UART that decodes EnDat/SSI/Hiperface). The DRIVE-CLiQ side terminates in a 1000BASE-T PHY feeding a real-time protocol stack on the encoder's microcontroller.
Correct Solution Path 1: Replace the Motor's Integrated DRIVE-CLiQ Encoder
This is the path Siemens service recommends and the only one with a defined catalog solution. The motor's integrated DRIVE-CLiQ encoder is replaced with a sin/cos or EnDat encoder compatible with the Simodrive 611U/611A DB25 port. The replacement encoder must be mechanically identical (shaft, flange, coupling) to preserve the bearing and balancing class.
- Identify the motor: read the nameplate, then cross-reference the order number (MLFB) in the Siemens MOTION-CONNECT catalog. Typical frame sizes: 1FT6, 1FK6, 1FT7, 1FK7.
- Order a like-for-like encoder module. Common catalog numbers (verify against current Siemens Product Configurator before ordering):
- Sin/cos 1 Vpp incremental + C/D track: 6FX2001-2xxxx series (suffix depends on pole count and resolution).
- EnDat 2.1 absolute singleturn: 6FX2001-3xxxx series.
- EnDat 2.1 absolute multiturn: 6FX2001-4xxxx series.
- Replace the encoder in the motor housing per the motor's service manual. The motor must be partially disassembled; only qualified service personnel should do this because the rotor and stator alignment is critical.
- Connect the new encoder directly to the DB25 port with a Siemens MOTION-CONNECT 800plus cable (6FX8002 series, length code after the dash).
- Configure p0400 in the drive to match the new encoder type and run the auto-configuration (p340 / p341 in SimoCom U or SimoPro).
Correct Solution Path 2: Use a SINAMICS Drive as a Bridge
If the existing cabinet must keep the Simodrive 611U/611A controller but the motor is locked to DRIVE-CLiQ, install a SINAMICS drive (S120 Booksize or Chassis size, or a CU320-2 control unit with an SMC/SME) in the cabinet. The SINAMICS drive is placed between the controller and the motor. The 611 becomes a "current/voltage command" master; the SINAMICS handles commutation, encoder feedback, and DRIVE-CLiQ.
- Select a SINAMICS line module (Active Line Module for regenerative applications, Smart Line Module for cost-sensitive, Basic Line Module for unidirectional).
- Select a Motor Module sized for the motor's rated current (verify I_rated > motor nameplate I_0).
- Connect the motor's DRIVE-CLiQ cable directly to the Motor Module's X202 port.
- Connect the SINAMICS analog setpoint input (±10 V velocity/torque command) to the Simodrive 611's analog output, or use PROFIBUS/PROFINET to command the SINAMICS from the 611's host PLC.
- Power on in the order: line module → control unit → motor module. SINAMICS STARTER or TIA Portal V15+ commissioning tool downloads the DRIVE-CLiQ topology and binds the encoder.
Correct Solution Path 3: Sensor Module External (SME) — When and Why It Still Fails
The Sensor Module External (SME) is often suggested in this context. Common catalog numbers include SME 20 (6SL3055-0AA00-5BA0 family) and SME 25 (6SL3055-0AA00-5CA0 family) for EnDat/sin/cos input, and SME 120/SME 125 (6SL3055-0AA00-5DA0 / 5EA0 family) for resolvers. The SME converts a standard encoder's analog/RS-485 signals into a DRIVE-CLiQ uplink.
Critical point: the SME converts into DRIVE-CLiQ, not out of DRIVE-CLiQ. There is no Siemens Sensor Module that takes a DRIVE-CLiQ signal and outputs sin/cos or EnDat for a 611U/611A DB25 port. The 6FX2001-2xxx and 6FX2001-3xxx SME variants are all uplink-only. The SME can be used in Path 2 (to attach a legacy encoder to a SINAMICS), but it does not solve the original problem in this article's source.
Commissioning and Verification Procedure (Path 1, Encoder Replacement)
After a successful encoder swap, follow this sequence to bring the axis back into service. Tools required: Siemens SimoCom U (611U) or SimoPro (611A) commissioning tool, a PC with RS-232 or PROFIBUS connection, and a calibrated hand tachometer for the verification step.
- Connect the PC to the drive via the X471 RS-232 port (611U) or PROFIBUS address 0 (611U/611A). Open SimoCom U.
- Read out the existing project file. Save a backup of p0001 through p1999 as the baseline.
- Set p0010 = 4 (commissioning reset) and p0970 = 1 to factory-reset only the encoder parameters if a clean slate is required.
- Set p0400 to the encoder type. For sin/cos 1 Vpp with EnDat 2.1 absolute singleturn: p0400 = 2. For sin/cos 1 Vpp incremental: p0400 = 1. For EnDat 2.1 multiturn: p0400 = 8 (verify on firmware version).
- Set p0408 to the encoder's line count (ppr) from the encoder data sheet, e.g. 2048, 4096, 8192, 16384.
- Set p0410 to the encoder's pole count for resolvers. For sin/cos, set p0411 = 0 (rotary, no commutation offset learning required at first power-up).
- Power-cycle the drive. The encoder must initialize without alarm. Confirm the green "Encoder OK" LED on the drive front panel.
- Run a referencing pass. For absolute encoders, set p171.0 = 1 then p971.0 = 1 to accept the mechanical home position. For incremental encoders, the drive requires a full mechanical reference run to define the zero point.
- Verify by jogging the motor at 50 rpm and confirming in r0021 that the speed readout tracks within ±2%. Confirm in r0026 that the direction is correct (positive command → positive speed).
- Confirm at 1500 rpm that the encoder is not dropping counts. Read r377 in SimoCom U; it should remain constant over a 60-second run at constant speed.
Troubleshooting Matrix
| Symptom | Probable Cause | Drive Alarm (611U/611A) | Remedy |
|---|---|---|---|
| Encoder LED off, drive reports "encoder broken wire" | Cable shield not bonded, twisted pair polarity reversed on +5 V supply | F31110 (encoder error), F31111 (encoder signal level) | Re-terminate DB25 per pinout table; verify 5 V present on pin 10 with multimeter (unloaded) and 4.75 V – 5.25 V under load |
| Encoder LED on, drive reports "encoder comm error" | EnDat clock/data swapped (pins 18/19 and 16/17 cross-wired) | F31117 (encoder protocol error) | Swap clock pair with data pair at the DB25 end |
| Motor commutation takes off in wrong direction at first motion command | A/B tracks swapped (cos vs sin to wrong DB25 pins) | F31118 (encoder direction reverse), F7990 (motor stalled) | Swap A+/A- (pins 1/2) with B+/B- (pins 6/7) on the DB25 only, or use p0410 to invert direction without rewiring |
| Drive reports "encoder signal too small" after cabling | Cable length > 50 m without line driver, or 5 V supply droop | F31111 | Use a Siemens 6FX8002-1 cable rated to 100 m, or install an external line driver. Verify 5 V at the encoder end under load |
| Drive repeatedly loses the encoder after 30 s – 5 min | EMC interference; cable routed next to VFD power output | F31110, F31117 intermittent | Re-route cable > 200 mm from power conductors; ground both ends of cable shield |
| Multiturn absolute position wrong after power cycle | Multiturn battery missing or exhausted; p0410 set to "no multiturn" | F31170, F31171 (encoder battery warning/fault) | Check battery in encoder housing (if buffered); for non-buffered encoders, run a referencing pass after each power-up |
| Drive accepts encoder but controller reports position drift > 1° over 1 hour | Shield ground loop; resolver sin/cos not terminated | No alarm, silent drift | Verify single-point shield ground at the drive end; check resolver termination resistor (120 Ω on each of sin/cos pairs if not internal) |
| After Sin/cos → DRIVE-CLiQ conversion (via SME 25), drive rejects encoder | SMx firmware version too old to recognize the SME firmware | F01320 (topology fault) | Upgrade drive firmware (e.g., 611D to 3.4.x or SINAMICS to 5.2+) via SimoCom U / STARTER |
Engineering Field Notes and Caveats
- DRIVE-CLiQ cables are polarity-sensitive. Both ends are RJ45, but the wiring is not Ethernet crossover. The two color-coded ends (one yellow-striped, one green-striped in the Siemens pre-fab cable) identify the direction: yellow is the line side, green is the motor side. Reversing them does not damage anything but the topology detection fails.
- Maximum DRIVE-CLiQ cable length is 100 m for the standard 6FX8002 series. For lengths above 30 m, ensure the cabinet ground is referenced to the same potential as the motor's grounding brush.
- If the cabinet must stay on Simodrive 611 hardware for legacy reasons (e.g., the project is locked to FM-NC on a SINUMERIK 840D and the drive firmware is not upgradeable to SINAMICS), Path 1 (encoder swap) is the only sustainable solution. Path 2 introduces a dual-drive architecture that complicates Safety Integrated and PROFIsafe.
- The "SMC 20" (Sensor Module Cabinet) is a daughterboard that slots into a SINAMICS power module. It is not a standalone product and cannot be used with a Simodrive 611U/611A. The "SME" (External) is the standalone IP67 variant used outside the cabinet.
- After any encoder replacement, the drive's mechanical home position must be re-referenced. For 611U with EnDat 2.1 singleturn, the absolute position is lost across power cycles and a new home run is required every time. Multiturn EnDat 2.1 retains position across power cycles only if the encoder's backup battery is healthy.
- Whenever an encoder cable is replaced, perform an insulation test (500 V DC for 5 s) and a continuity test on all 8 RJ45 wires plus the shield. A shorted DRIVE-CLiQ cable typically takes down the encoder port and posts a "topology fault" rather than a "cable fault" — confusing at first diagnosis.
FAQ
Can I connect a motor with a DRIVE-CLiQ encoder directly to a Simodrive 611U (DB25) using only a cable adapter?
No. DRIVE-CLiQ is a digital Ethernet-based protocol with 24 V power; a DB25 on the 611U accepts analog sin/cos, resolver, EnDat, SSI, or Hiperface signals. A passive RJ45-to-DB25 cable cannot bridge the protocol mismatch and the drive will report F31110 / F31117. Use a Siemens Sensor Module (SME 20/25/120/125) only if the drive is SINAMICS, or replace the motor's encoder with one that matches the 611U's DB25 port type.
My Simodrive is a 611D. Do I need any adapter to connect a DRIVE-CLiQ motor?
No. The Simodrive 611D has a native DRIVE-CLiQ port (X202 / X203) and accepts a motor with an integrated DRIVE-CLiQ encoder using a 6FX8002-2DCxx cable. Configure the encoder in p0400 and run an automatic topology detection by powering on the drive. No third-party hardware is required.
Does Siemens sell a DRIVE-CLiQ-to-analog (sin/cos or EnDat) converter?
No. Siemens' SME and SMC product families only convert standard encoders into DRIVE-CLiQ, not out of it. For a reverse conversion, replace the motor's DRIVE-CLiQ encoder with a sin/cos or EnDat module, or use a SINAMICS drive as a bridge to the 611U/611A.
What DRIVE-CLiQ cable length is allowed between the motor and the drive?
Up to 100 m using the Siemens MOTION-CONNECT 800plus 6FX8002-2DCxx cable family. For runs longer than 30 m, route the cable at least 200 mm from any VFD power conductors and ground the shield at both ends. The maximum length is set by IEEE 802.3 gigabit Ethernet signal-integrity limits, not by Siemens policy.
After an encoder replacement on a 611U, do I need to re-reference the axis?
Yes. For a new absolute encoder (EnDat 2.1 singleturn), execute a referencing run via p171 / p971 in SimoCom U. For multiturn EnDat with a healthy battery, the drive will retain absolute position across power cycles; for a swapped encoder, always run one full referencing pass before resuming production motion. Incremental encoders (sin/cos without EnDat) require a mechanical reference run at every power-up.