Problem Overview
SINAMICS S120 drives configured with a CU320-2 PN control unit, a Smart Line Module, and a Double Motor Module driving two 1FT7042-5AF70-1BG2 servo motors (DRIVE-CLiQ, integrated encoder) report fault F07900 — "Drive: Motor locked / speed controller at its limit" immediately after the standstill (stationary) measurement completes, both from the STARTER control panel and from the S7-300 CPU via EPOS basic positioner. The fault appears the first time a non-zero speed setpoint (for example, 100 rpm) is commanded, regardless of which SERVO drive object (SERVO_02 or SERVO_03) is active.
This behavior is reproducible after a full project download, after a factory reset + automatic device configuration, and after switching the active drive object in the STARTER control panel. A short, sluggish shaft rotation is typically observed before the drive pulses are inhibited and F07900 is latched.
Affected Components and Topology
The fault typically surfaces in the following configuration, which is the reference scenario for the procedure below:
| Component | Order number / designation | Role |
|---|---|---|
| Control Unit | CU320-2 PN (6SL3040-1MA01-0AA0 family) | Central DRIVE-CLiQ coordinator, PROFINET I/O to S7-300 |
| Line Module | Smart Line Module 6SL3130-6AE15-0ABx | DC-link supply, regenerative |
| Motor Module | Double Motor Module 6SL3120-2TE13-0AAx class | Two-axis servo output stage |
| Motor X1 (SERVO_02) | 1FT7042-5AF70-1BG2 (SIMOTICS S) | DRIVE-CLiQ motor, integrated absolute encoder |
| Motor X2 (SERVO_03) | 1FT7042-5AF70-1BG2 (SIMOTICS S) | DRIVE-CLiQ motor, integrated absolute encoder |
| Controller | SIMATIC S7-315-2 PN/DP | Higher-level PLC, EPOS setpoint source |
| Engineering | STARTER (or Startdrive, depending on firmware) | Drive configuration and online diagnostics |
The 1FT7042-5AF70-1BG2 is a SIMOTICS S servo motor with a built-in DRIVE-CLiQ encoder. The motor has only two physical connections: an orange power cable with a pre-fitted connector on the motor side, and a green DRIVE-CLiQ signal cable. The power cable reaches the Motor Module as a free-end lead that the user must connect to the U2/V2/W2 (or U/V/W depending on module family) terminal block of the corresponding axis.
Root Cause: Power Phase Sequence vs. Encoder Direction
F07900 is raised by the SINAMICS closed-loop control when it detects a contradiction between the speed setpoint issued by the higher-level controller, the speed controller output (torque demand), and the measured encoder velocity. The drive concludes the motor must be mechanically blocked and trips to protect the system.
For an unloaded 1FT7 motor that has just passed the standstill measurement, the three most probable causes in this topology are:
- Power phase sequence reversed on the Motor Module terminal block. The magnetic field in the stator rotates in the opposite direction to the direction expected by the encoder-based field-orientation model. The speed controller saturates trying to close the gap and the "motor locked" detection trips. This is the most common cause when a non-prefabricated (free-end) cable is used or when the cable was ordered separately from the motor and crossed in the field.
- Encoder physically paired with the wrong motor. On a Double Motor Module, axis X1 and axis X2 share a common housing. The DRIVE-CLiQ topology wizard validates that the encoder type matches, but it does not verify that encoder X1 is mechanically mounted on the same shaft as power X1. If the green DRIVE-CLiQ leads were inadvertently swapped at the Motor Module end, the field-orientation model rotates correctly but on the wrong physical shaft, so the controlled shaft reports near-zero speed while the controller commands a positive speed.
- Torque limit / current limit too low relative to friction + load. The standstill measurement typically sets p1400/p1520/p1521 based on motor data. If the load-side friction or any external torque is significant, the speed controller may saturate against the torque limit and the "motor locked" time threshold expires.
The DRIVE-CLiQ encoder interface communicates the absolute position, commutation angle, and pole-pair information to the control unit over a digital link. Because the commutation is computed in the drive from the encoder feedback, swapping power phases U ↔ V (or V ↔ W, or U ↔ W) on the Motor Module terminal is a real, physical phase sequence change and is not auto-corrected by DRIVE-CLiQ. DRIVE-CLiQ only resolves the logical direction (positive/negative setpoint) via parameter p0410[p].bit / p1821 (direction of rotation reversal), not the electrical phase wiring.
Relevant SINAMICS Parameters
Before touching wiring, capture the current state of the parameters below. They are visible in STARTER under Drive → Commissioning → Motor/Encoder and Drive → Messages/monitoring → Speed messages.
| Parameter | Name | Default (S120) | Function in F07900 path |
|---|---|---|---|
| p1082 | Maximum speed (rpm) | Motor-dependent | Upper speed clamp; verify the requested 100 rpm is well below. |
| p1520 | Upper torque limit (Nm) | From standstill measurement | If too low, the speed controller saturates against this limit. |
| p1521 | Lower torque limit (Nm) | From standstill measurement | Same as p1520 for negative direction. |
| p1530 | Power limit motoring (kW) | From standstill measurement | Power clamp; relevant if the motor is over-rated for the output stage. |
| p1531 | Power limit regenerating (kW) | From standstill measurement | Regenerative clamp. |
| p2162 | Speed threshold hysteresis (rpm) | — | Used to qualify the speed deviation message. |
| p2175 | Motor locked speed threshold (rpm) | 6.00 | If |n_act| stays below this while |n_set − n_act| > p2162 for longer than p2177, F07900 trips. |
| p2177 | Motor locked delay time (s) | 3.0 | How long the speed deviation must persist before F07900. |
| p2198 | Monitoring configuration bits | — | Bit 0 enables motor locked monitoring; clear to disable. |
| p1821 | Direction of rotation reversal (per encoder) | 0 (off) | Logical direction; does NOT fix power phase sequence. |
| p0410[p] | Encoder inversion (per encoder) | 0 | Same as p1821 — encoder-side only. |
p2175 = 0 deactivates the motor-locked detection for that drive. Use this only as a temporary diagnostic — never as a permanent fix. The fault is a protection function; suppressing it will not correct the underlying wiring or mechanical problem, and the drive will still saturate the speed controller, lose the ability to follow a setpoint, and potentially flag other faults (F07901, F08501, F30002, etc.). Siemens support forums confirm that disabling the locked detection alone typically does not clear F07900 in this scenario.Solution A — Verify and Correct Power Phase Sequence
This is the field-proven fix for the reference case and is the first action to take whenever F07900 is raised on a DRIVE-CLiQ motor right after the standstill measurement on an unloaded shaft.
Prerequisites
- Drive is safely de-energized, DC-link discharged (≥ 5 min wait after line contactor OFF, verify with a suitable DC-link meter at the Smart Line Module test points).
- All safety circuits (STO via terminals EP at the Motor Module) are in the safe state.
- Documentation of which orange power cable belongs to which physical motor and which axis socket on the Double Motor Module.
Step-by-step
- Power down the Line Module, lock the main disconnect, and confirm zero voltage at the Motor Module input. Discharge the DC link per the S120 Equipment Manual instructions.
- Trace each power lead from the motor connector back to the Motor Module terminal block. The 1FT7042 power cable has three phase cores plus protective earth. Color coding on Siemens prefabricated cables: U = black, V = black with white stripe, W = black (the printed sleeve near each lug identifies the phase). Confirm the assignment against the schematic in the S120 List Manual (search for "Motor connection").
- Connect U → U2, V → V2, W → W2 on the Motor Module terminals. The terminal layout for the 6SL3120-2TE13-0AAx class Double Motor Module is: axis X1: U2 V2 W2, axis X2: U2 V2 W2 on the lower terminal block, with PE (ground) on the dedicated grounding bar.
- Re-torque the terminal screws to the value specified on the module label (typically 2.5 Nm for the 6SL3120 double motor module family).
-
Verify DRIVE-CLiQ topology: in STARTER online, expand the device tree and confirm that the encoder of motor X1 is on DRIVE-CLiQ port X1 of the Double Motor Module and the encoder of motor X2 is on port X2. If the topology wizard in HW Config / TIA Portal was used, the project topology must match the physical topology — if it does not, the wrong
p0141/p0142encoder assignment is in effect. - Power up the Line Module, wait for DC-link ready, and bring the drive back online in STARTER.
- Run a directional test using the STARTER control panel: command a small positive speed (e.g. 30 rpm) on SERVO_02 with the motor uncoupled. Verify the shaft physically rotates in the direction defined as "positive" by your mechanical convention. If it rotates the wrong way, swap two phases and leave the encoder wiring as-is — do not change p1821. If it rotates correctly, no further wiring change is needed; proceed to the optimization measurement.
Solution B — Confirm Encoder-to-Motor Pairing
When phase sequence is correct but F07900 still trips on a particular drive object, the most likely remaining cause is that the green DRIVE-CLiQ cable of motor X1 has been plugged into port X2 of the Double Motor Module (or vice versa). The drive is then closing the loop on the wrong physical shaft.
- With both motors mechanically accessible and uncoupled, command a slow speed (10 rpm) on SERVO_02 from the STARTER control panel.
- Visually confirm that the physical motor attached to power X1 (not power X2) is the one rotating. If the motor on X2 rotates, the green DRIVE-CLiQ cables are swapped at the Motor Module.
- Power down, swap the two DRIVE-CLiQ connectors between X1 and X2 on the Motor Module, and repeat the test.
- Once the rotation matches the active drive object, re-run the standstill measurement on both axes to update the commutation offset in
p0431and the torque/current limit inp1520/p1521.
Solution C — Relax the Motor-Locked Detection (Diagnostic Only)
Use this only to confirm the protection path is the source of the trip, never as a permanent workaround.
- In STARTER, open Drive → Messages/monitoring → Speed messages.
- Set
p2175 = 0.00rpm to disable the motor-locked speed threshold. - Set
p2198.0 = 0if you also want to disable the monitoring flag entirely. - Download to the drive and run the same 100 rpm test from the control panel.
- If F07900 still trips, the fault is in the torque/current loop, not the speed monitoring — return to Solutions A and B.
- Revert
p2175to the recommended 6.00 rpm (or the calculated value for your application) before commissioning the machine.
Solution D — Check Torque and Current Limits
If both wiring paths are correct and F07900 still appears at higher speeds, verify the following with the drive online:
-
r0027(actual speed smoothed) versusr0062(speed setpoint) — if the gap is sustained and the torque setpoint r0079 saturates against r1520, the speed controller is in current limit. -
r0067(actual current) versusr0068(current limit) — saturation here confirms torque limit too low. - Mechanical load: free the shaft completely. Even a sticky bearing or misaligned coupling at standstill can hold n_act below p2175 long enough for F07900 to trip after p2177 (3.0 s) elapses.
- If the standstill measurement ran with load attached, re-run it with the motor uncoupled and re-accept the values. The measurement writes new limits for p1520/p1521.
EPOS Integration with S7-300
Once the F07900 path is resolved, the same S7-300 application code (FB 1 / FB 2 / FB 3 EPOS blocks, or a manual telegram 111 setpoint) will follow the position setpoint without raising the fault. Two notes specific to PROFINET IRT between an S7-300 (315-2 PN/DP) and a CU320-2 PN:
- The PROFINET send/receive cycle must match the drive-side clock (p2048 / p0922 = 100). The default STARTER telegram for EPOS on a CU320-2 PN with the 1FT7 motor is telegram 111 (positioning, with 32-bit position, velocity override, and control/status words). The 315-2 PN/DP supports this, but the IRT slot must be configured topologically in HW Config.
- Bit 0 of the EPOS control word (
STW1.0— ON/OFF1) must be set on each axis. The S7 application must also clearSTW1.1(no OFF2) andSTW1.2(no OFF3), and setSTW1.3(enable operation) andSTW2.4(interpolate). If any of these bits are false the drive will not open the speed controller and the next setpoint will trip F07900 because the controller is disabled.
Verification Procedure
After implementing any of the solutions above, perform the full verification before returning the machine to production:
- Clear the fault buffer in STARTER (Drive → Diagnostics → Fault buffer → Acknowledge all) and run a power-on reset (line contactor OFF, then ON, after the DC-link discharge time).
- Run the commutation-angle test via the control panel: Commissioning → Motor/Encoder → Commutation. The drive should report SUCCESS with the new angle stored in
p0431. - Run the rotating measurement on each axis separately, with the motor uncoupled. Accept the new controller gains (p1460 / p1470 / p1472 — speed controller Kp and Tn).
- From the STARTER control panel, ramp each axis through −1500 → 0 → +1500 → 0 rpm in steps of 250 rpm. Capture
r0027,r0062, andr0079in the trace. Confirm no F07900 / F07901 / F08501 appears in the fault buffer. - From the S7-300, issue a relative positioning command of 10 revolutions at 200 rpm on SERVO_02, then SERVO_03, then both simultaneously. Confirm position following error
r2561stays within the configured window (p2546) and that no F011 / F07900 is raised. - Re-enable the motor-locked detection (
p2175 = 6.00) and confirm the protection is operational by blocking the shaft mechanically for ≥ 4 s during a 100 rpm command. F07900 should re-appear — this confirms the protection path is alive and the production configuration is safe.
Parameter Cross-Reference Table
| Function | Parameter | Read/Write | Reference |
|---|---|---|---|
| Motor-locked speed threshold | p2175 | R/W online | S120 List Manual |
| Motor-locked delay time | p2177 | R/W online | Same as above |
| Torque limit upper | p1520 | R/W online | Same as above |
| Torque limit lower | p1521 | R/W online | Same as above |
| Direction of rotation reversal (logical) | p1821 | R/W online | Same as above |
| Encoder inversion | p0410[0..n].bit | R/W online | Same as above |
| DRIVE-CLiQ port assignment | p0141, p0142 | Auto from topology | S120 Equipment Manual |
| Commutation angle offset | p0431 | R/W online (set by measurement) | S120 List Manual |
| PROFINET send clock | p2048 | R/W | PROFINET Commissioning Manual |
| EPOS following error window | p2546 | R/W | EPOS function manual |
| Telegram selection | p0922 / p2079 | R/W | S120 List Manual |
Fault Code Family Reference
F07900 belongs to a small group of closely related faults that the speed and current monitoring channels can raise. Knowing the siblings helps disambiguate in the field.
| Fault | Meaning | Typical cause in a fresh commissioning |
|---|---|---|
| F07900 | Motor locked / speed controller at limit | Phase sequence reversed, wrong encoder pairing, or torque limit too low |
| F07901 | Motor overspeed | Encoder direction inverted, wrong motor data, mechanical overdrive |
| F08501 | PROFINET communication fault | Watchdog timeout, IRT slot mis-configured, telegram mismatch |
| F30002 | DC-link overvoltage | Regenerative energy with no absorber / wrong line module |
| F30611 | Line phase failure | Smart Line Module input phase missing |
| F08501 / F01910 | Fieldbus timeout | PN cable break, controller in STOP |
Safety Notes for Working on the SINAMICS S120
After the line contactor is opened, the DC-link remains at hazardous voltage (typ. 540–600 V DC for a 400 V class Smart Line Module) for the time specified on the module label (typically 5 min). Verify with a properly rated meter at the DC-link test points before touching any motor terminal.
If you removed or reseated the EP terminal jumper on the Motor Module to de-energize the outputs, the Safe Torque Off function is engaged. Re-install the jumper only after the safety relay circuit is re-validated. Any STO event resets the
Safety Integrated checksum and the drive will not run until the safety configuration is acknowledged.F07900 is a drive-side speed monitoring fault, not a safety fault. The safety-integrated parameters are unrelated to this code.
Documentation References
- SINAMICS S120 Equipment Manual — DC-link discharge time, terminal layouts, wiring
- SINAMICS S120/S150 List Manual — full parameter list including p2175, p2177, p1520, p1821, p0431
- SINAMICS S120 Commissioning Manual — STARTER control panel procedure and standstill/rotating measurement
- SINAMICS S120 Communication Manual (PROFINET) — telegram 111, IRT configuration
- SIMOTICS 1FT7 Configuration Manual — 1FT7042 connector pin-out, prefabricated cable part numbers
- SINAMICS S120 EPOS Function Manual — basic positioner control words, p2546 following error window
FAQ
Does DRIVE-CLiQ auto-correct a reversed power phase sequence on a 1FT7 motor?
No. DRIVE-CLiQ only delivers the encoder signal, absolute position, and motor nameplate data to the control unit. The electrical phase sequence on the Motor Module terminal block is a physical wiring concern; if U, V, W are not in the correct order the rotating field goes the wrong way and the drive will trip F07900 on the first movement. Use p1821 only for logical direction reversal after the physical phase sequence is verified correct.
Can I just set p2175 = 0 to make F07900 go away?
You can disable the motor-locked detection by setting p2175 to 0 rpm, but this is a diagnostic step only. F07900 is a protection function. Disabling it does not fix the underlying cause (phase sequence, encoder pairing, or torque limit) and exposes the drive and mechanism to undetected stall conditions.
The standstill measurement completed successfully, so why does F07900 trip on the next run?
The standstill measurement only sets the commutation angle, controller gains, and torque limits — it does not verify the direction of rotation. If the power phase sequence is reversed, the standstill measurement still succeeds because the motor is not asked to rotate. The fault trips the moment a non-zero speed setpoint is applied, because the encoder feedback direction contradicts the commanded field direction.
F07900 appears only on one of the two axes. What is the quickest diagnostic?
Swap the two green DRIVE-CLiQ cables between X1 and X2 on the Double Motor Module and re-test. If the fault follows the DRIVE-CLiQ cable (i.e., the axis that was previously good now trips), the encoder of one motor is plugged into the wrong port. If the fault stays on the same drive object, the issue is power-side on that axis (phase sequence or torque limit).
What telegram should I use between an S7-300 and a CU320-2 PN for EPOS on a 1FT7 motor?
Use standard telegram 111 (positioning mode, 32-bit position, velocity override, and EPOS control/status words). The 315-2 PN/DP supports it via PROFINET IRT. Make sure p0922 = 111 on the drive side, p2048 matches the controller send clock (typically 1 ms), and p2079 holds the correct number of extension words if you add additional process data.