Resolving SINAMICS S120 Speed Controller Inhibited OFF1 Fault

David Krause19 min read
SiemensTroubleshootingVFD / Drives
Licensed PE Working through this on a live machine? A Maine-licensed engineer can take it from here — included with IMD hardware, by the hour for everything else. Book an engineer

Problem Definition

When commissioning a SINAMICS S120 multi-axis drive system with the Starter or Startdrive commissioning tool, an asymmetric configuration state can develop between drives that are otherwise identical at the topology level. A common symptom is one axis returning to operation normally after automatic configuration while a second axis reports the simultaneous conditions Speed controller inhibited and OFF1 enable missing in the diagnostic buffer and online status panel. The drive continues to acknowledge parameter writes, but several expert-list parameters that are normally populated by the auto-configuration routine remain at zero. Manual attempts to exit commissioning by writing p10 = 0 are rejected with the diagnostic message Value rejected, and a request to end quick commissioning via p3900 = 3 reverts to p3900 = 0 after a few seconds. Together, these behaviors indicate that the automatic commissioning sequence never reached the calculation phase on the affected drive, leaving the drive object in a half-configured state.

Symptom versus expected behavior on a healthy axis
Observed symptom Expected on a properly commissioned axis
"Speed controller inhibited" status r0052 bit 4 = 1 (speed controller active)
"OFF1 enable missing" status r0046 bit 0 = 0 (OFF1 present)
p10 accepts writes only to 1 p10 accepts 0 once commissioning data is consistent
p3900 = 3 reverts immediately to 0 p3900 = 3 calculates, accepts to ROM, returns to 0
Expert list parameters at 0 p0300 family, p0341, p2000 family populated from motor code

Affected Hardware Topology

The reported configuration consists of a SINAMICS S120 booksize line-up controlled by a CU320-2 PN control unit. The infeed is a Smart Line Module and the two motor axes are served by a Double Motor Module. Both motors come from the 1FK7 synchronous servo family. Identifying the DRIVE-CLiQ capability of each component is the foundation of the root-cause analysis.

Components referenced in the failure scenario
Component Article number / designation Role DRIVE-CLiQ capability
Control Unit CU320-2 PN (e.g., 6SL3040-1MA01-0AA0) Central control / PROFINET coupling 4 DRIVE-CLiQ ports
Smart Line Module 6SL3130-6AE15-0AB1 (5 kW, 400 V booksize) Non-regenerative DC link supply 1 DRIVE-CLiQ port
Double Motor Module 6SL3120-2TE13-0AA4 (2 × 3 A) Two-axis inverter 1 DRIVE-CLiQ port (per axis internal)
Motor axis 1 (working) 1FK7022-5AK71-1LG0 Synchronous servo, with DQ Integrated DQ interface (L-suffix)
Motor axis 2 (failing) 1FK7022-5AK71-1AG0 Synchronous servo, no DQ No DQ; resolver / incremental via SMC
Encoder axis 2 IC2048S/R L22 (incremental, 2048 S/R) Position feedback on axis 2 Requires SMC20 or SMC30 module

The article-number suffix in the 1FK7 family encodes the integrated electronics options. The letter in the 11th position is the deciding field for DRIVE-CLiQ:

  • 1FK7022-5AK71-1AG0 – 11th character A: no DRIVE-CLiQ interface; resolver / incremental feedback only, terminal box connection.
  • 1FK7022-5AK71-1LG0 – 11th character L: with DRIVE-CLiQ; encoder and electronic nameplate are transferred over the digital interface.

This is the central distinction in the failure scenario. The "L" variant carries an electronic nameplate that the auto-configuration routine reads to populate motor and encoder parameters. The "A" variant carries no electronic nameplate; the auto-configuration routine finds no DRIVE-CLiQ node on that axis and skips parameter population. To complete the topology, an external Sensor Module Cabinet-Mounted (SMC20 for resolvers, SMC30 for incremental encoders such as the IC2048S/R) must be wired into the DRIVE-CLiQ ring of the CU320-2 PN.

Identification shortcut: On a 1FK7 motor the 11th character of the article number is the DRIVE-CLiQ designator. A = no DQ, L = DQ. Cross-check against the encoder cable routing – DQ motors have a single M12 connector carrying power and signals; non-DQ motors have a separate power connector and a separate signal connector routed to an SMC module.

Root Cause: Non-DQ Motor Configuration Gap

Auto-configuration in SINAMICS Starter / Startdrive depends on the topology it can read. When Starter performs automatic configuration (drive object creation based on the DRIVE-CLiQ topology), it walks the DRIVE-CLiQ ring and discovers Line Modules, Motor Modules, motors with electronic nameplates, and Sensor Modules. A motor without an integrated DRIVE-CLiQ interface and without an external SMC module wired into the topology is invisible to the auto-configuration routine. The Motor Module creates a drive object, but the motor code, motor equivalent-circuit parameters, and encoder parameters remain at zero.

Consequences on the affected axis:

  1. p10 cannot be set to 0. The drive object has not finished the parameter consistency check required to leave commissioning state. Writing p10 = 0 is rejected with "Value rejected" because motor data (p0300 family), encoder data (p0400 family), and the closed-loop control structure reference (p1300) are inconsistent or zero.
  2. p3900 = 3 reverts to 0. The end-of-quick-commissioning sequence needs a valid p0300 (motor code selection) and a consistent motor data set. With p0300 = 0 the calculation routine has nothing to compute, the command is accepted briefly, the calculation aborts, and p3900 is written back to 0 by the firmware within a few seconds.
  3. "OFF1 enable missing" and "speed controller inhibited" persist. These are status bits driven by the enable logic. The drive stays in state S1 (Ready for switching on) or S2.1 (Ready for operation with controller inhibit) because the missing motor identification means the closed-loop controller cannot be released; the OFF1 signal cannot latch without a configured power unit and motor model.

In short, the automatic configuration successfully wrote a topology into the project for the DQ motor, then encountered the non-DQ motor whose nameplate data could not be read and silently left the drive object incomplete. The user-visible symptom is asymmetric between two otherwise mechanically identical axes.

Diagnostic Procedure and Parameter State Inspection

Before changing any project data, perform the following read-only checks in Starter or Startdrive to confirm the hypothesis.

Read the enable status word

Open the affected drive's Diagnostics > Status / Control panel or read the following parameters online:

  • r0046 – Missing enables (bit field). On a faulted axis, bit 0 (OFF1 enable) and bit 21 (speed controller inhibited) are typically set to 1.
  • r0047 – Drive status word 1 (state machine S0 / S1 / S2 ...).
  • r0052 – Status word 2 (bit 4 = speed controller active).
  • r0002 – Current drive state (numeric code from the state machine).
Key bits of r0046 (Missing enables)
Bit Name Implication
0 OFF1 enable missing Drive cannot close output stage; OFF1 command has no effect
1 OFF2 enable missing Coast-stop command missing (often EP terminal open)
2 OFF3 enable missing Quick-stop command missing
3 Inverter enable missing Pulse-enable bit not set; check p0852 source
10 Pulse inhibit active Drive is hard-inhibited (commissioning state, fault, EP)
21 Speed controller inhibited Closed-loop controller is held in commissioning state
22 Open-loop operation active Drive runs in open-loop (encoderless) mode

Compare parameter populations between drives

Open the expert list for both drives and look at the parameter groups below. On a successfully auto-configured DQ axis the parameters are populated; on the failing non-DQ axis they are zero.

Parameters to compare between the working axis and the failing axis
Parameter group Key parameters Function
Motor data p0300, p0301, p0304, p0305, p0307, p0310, p0311 Motor code, voltage, current, power, frequency, pole pair count
Motor equivalent circuit p0350, p0352, p0354, p0356, p0358, p0360 Stator / rotor resistance, leakage reactance, main inductance
Encoder data p0400, p0401, p0404, p0408, p0420 Encoder type, resolution, inversion, signal level
Speed controller p1460, p1462, p1470, p1472 Gain, integral time, encoderless switchover
Reference values p2000, p2001, p2002, p2003 Reference speed, voltage, current, torque

If the working axis shows e.g. p0300 = 203 (1FK7 DQ family) or p0300 = 207 (third-party synchronous) and the failing axis shows p0300 = 0, the missing parameter set is the smoking gun. The same check on p0400 confirms the encoder side.

Read the drive state and control word

Read r0002 (drive state) and r0898 (control word 1, BICO view). The failing axis will be in S1 (Ready for switching on) rather than S4 (Operation) because no OFF1 has latched. Confirm also that r0050 (active command data set CDS) is 0 or 1 as expected; some multi-axis projects use two CDS to switch motor data between gear stages, and the active CDS can mask which parameter set is actually loaded.

Key Parameter Reference

The following parameters form the minimum surface area that must be valid before the drive can leave commissioning state. They are read from the SINAMICS S120 List Manual.

SINAMICS S120 commissioning parameters
Parameter Name Values Notes
p10 Drive commissioning parameter filter 0 = ready
1 = quick commissioning
5 = safety commissioning
6 = basic commissioning
Must return to 0 before p3900 / p0340 / commissioning wizard exit
p3900 End quick commissioning 0 = ready
1 = calculate motor equivalent circuit only
2 = calculate and accept
3 = calculate, accept, factory reset I/O
Reverts to 0 after calculation completes; on failure reverts immediately
p0010 / p0011 Commissioning / BICO filter Mirror p10 values Filtering prevents writes to certain parameter groups
p864 Signal source for control word 1, bit 0 (OFF1) Default 0 (no source) Setting p864 to a fixed source (e.g., r0899.0) latches OFF1; required for direct digital control
p8641 Signal source for control word 1, bit 1 (OFF2 / coast stop) Default 1 (inverter enables OFF2) If changed accidentally, OFF2 is permanently missing
p0852 Signal source for inverter enable Default r0899.3 Drives OFF1 transition into pulse enable
p0300 Motor type selection 0 = no motor
1 = induction
2 = synchronous
203 = 1FK7 synchronous DQ family
207 = third-party / non-DQ synchronous
p0300 = 0 blocks motor identification and controller release
p0400 Encoder type selection 0 = none
2001 / 2002 = DRIVE-CLiQ encoder
1002-1011 = SMC20 resolver series
3001-3011 = SMC30 incremental series
9999 = user-defined
For non-DQ motors, configure to match the SMC channel in use
p1300 Open-loop / closed-loop control mode 0 / 1 = V/f
2 / 20 = speed enc
21 = speed enc (with encoder)
22 = torque
For servos with IC2048S/R encoder, p1300 = 21 is the default
p1910 / p1960 Motor identification / speed controller optimization 1 = start routine Static measurement (p1910) and rotating travel profile (p1960)
p0977 Save all parameters 1 = save to ROM Required after commissioning to persist values across power cycles
r0046 Missing enables Bit field (read-only) Diagnostic for OFF1 / OFF2 / OFF3 / pulse enable status
Important: The value p10 = 0 is a gate condition, not a fix. If the underlying motor and encoder data are invalid, the drive firmware continues to hold p10 at 1 or rejects the write. Confirm p0300 / p0400 / p1300 are valid before retrying p10 = 0.

Resolution Procedure: Manual Offline Commissioning

The successful resolution on a non-DQ axis is to upload the existing drive data into the project, take the project offline, and re-enter the configuration deliberately in the project's configuration tab for that drive object. Auto-configuration is then effectively replaced by manual configuration for that axis.

Prerequisites

  • Starter or Startdrive with the project that matches the CU320-2 PN.
  • Online connection (PROFINET or PROFIBUS) to the CU320-2 PN.
  • Article numbers of the motor, encoder, Sensor Module (if used), and Motor Module.
  • Motor data sheet (resistance, inductance, EMF constant, rated current, rated torque).

Step-by-step procedure

  1. Upload drive data to the project. Right-click the CU320-2 PN in the project tree and choose Target device > Upload device to PG/PC. The existing on-line configuration is mirrored into the offline project. This step ensures the project reflects what the drive actually has, including the parameters that auto-configuration set to zero.
  2. Go offline. Right-click the CU320-2 PN and select Go offline. All further edits must happen offline so the configuration can be compiled and downloaded as a complete package.
  3. Open the configuration of the affected SERVO drive object. In the project tree, double-click SERVO_03 (or whatever index the affected axis has). Select the Configuration tab.
  4. Configure the power unit. Confirm the Motor Module selection matches the installed hardware (e.g., 6SL3120-2TE13-0AA4). An incorrect power-unit selection changes the current limit, DC link voltage scaling, and overload capability and re-triggers the commissioning filter.
  5. Select the motor. In the motor configuration, open the motor catalog. For a 1FK7022-5AK71-1AG0 (non-DQ), the catalog entry is the same motor family but the DRIVE-CLiQ column must be set to "without DQ" or the article number must be entered with the "A" suffix explicitly. If the entry is not in the catalog, switch to Third-party motor or Motor with DRIVE-CLiQ → data entered manually and populate p0300, p0301, p0304, p0305, p0307, p0310, p0311, p0314 from the motor data sheet.
  6. Select the encoder. The IC2048S/R L22 incremental encoder is not a DRIVE-CLiQ encoder. Select the SMC channel that the encoder is wired into. For a resolver, configure SMC20 (p0400 in the 1002-1011 series); for an incremental encoder such as the IC2048S/R, configure SMC30 (p0400 in the 3001-3011 series). Set the resolution to 2048 S/R, set inversion (p0410) if the rotation direction is reversed, and set p0421 if the encoder has a commutation track.
  7. Set the control mode. Select Speed control with encoder (p1300 = 21) for the affected axis. Encoderless operation is not appropriate here because the IC2048S/R is the position feedback and the motor identification sequence requires it.
  8. Save and recompile the project. Press Save and compile. Any inconsistency in the configuration (e.g., a missing motor code for the selected control mode) appears as a compile error and prevents the download.
  9. Download to the target. Right-click the CU320-2 PN and select Download to target device. Confirm that the drive object SERVO_03 is included in the download. The download writes the configured motor and encoder data into the affected drive object.
  10. End quick commissioning. On the affected drive, set p3900 = 3 (calculate motor equivalent circuit, accept, factory reset I/O). The parameter should return to 0 after a few seconds. If it does not, the motor code is still inconsistent – re-check p0300 and the encoder configuration.
  11. Set p10 = 0. The drive should now accept the write and leave commissioning state.
  12. Save to ROM. Issue p0977 = 1 to copy the parameter set from RAM to ROM so the values persist across a power cycle.
  13. Run motor identification (strongly recommended). For a non-DQ motor that was not identified by auto-configuration, run p1910 = 1 (static motor identification) followed by p1960 = 1 (speed controller optimization). These routines measure the stator resistance, leakage inductance, and main inductance, then run a speed-controller optimization travel profile. Allow the motor shaft to rotate freely during p1960.

Validation checkpoints

  • After step 9, the affected drive's r0046 should show all enable bits cleared (OFF1, OFF2, OFF3, inverter enable).
  • After step 10, p0300 and p0400 should be non-zero and reflect the configured motor / encoder.
  • After step 13, r0052 bit 4 (speed controller active) should set to 1 once a motion command is issued.

Verification and Status Bit Checks

Once the project is downloaded, verify that the affected axis behaves identically to the working axis. Use the Starter control panel or Startdrive trace to check the items in the table below.

Verification checklist after manual commissioning
Check Method Pass criterion
Commissioning filter closed Read p10 p10 = 0
Quick commissioning ended Read p3900 p3900 = 0 after write of 3
Motor data accepted Read p0300, p0301, p0307 Non-zero values matching the data sheet
Encoder data accepted Read p0400, p0408 Encoder type matches SMC module, 2048 S/R
OFF1 enable present Read r0046 bit 0 r0046.0 = 0
Speed controller released Read r0046 bit 21, r0052 bit 4 r0046.21 = 0, r0052.4 = 1 during motion
Drive state machine advanced Read r0002 S4 (Operation) when motion is commanded
Speed setpoint reaches motor Trace r0062 and r0021 Setpoint and actual speed track within controller bandwidth
Torque saturation absent Trace r0079 Torque setpoint < p1520 / p1521 current limit

Run the drive through a small jogging profile in the control panel (e.g., 100 rpm for 2 s, then -100 rpm for 2 s). Capture r0021 (actual speed smoothed), r0062 (speed setpoint filtered), and r0079 (torque setpoint). On a properly configured axis, all three signals track within the controller bandwidth (default p1460 ≈ 0.7 Nm·s/rad, p1472 ≈ 20 ms after p1960 optimization). Persistent oscillation or torque saturation indicates that the motor identification must be re-run.

Supplementary Troubleshooting Matrix

The "Speed controller inhibited" / "OFF1 enable missing" pair can have causes beyond the auto-configuration gap. The matrix below maps the most common variants to the underlying cause and the appropriate action.

Troubleshooting matrix for "OFF1 enable missing" / "Speed controller inhibited"
Symptom combination Underlying cause Action
r0046.0 = 1, OFF1 source missing on p864 p864 was changed to an invalid BICO source Reset p864 to r0899.0 (drive-internal OFF1)
r0046.1 = 1, motor cannot coast OFF2 missing, EP terminal open, or safety STO active Check STO wiring, EP terminals X121/X131 on the Motor Module, F-CPU signals
r0046.3 = 1, pulse enable missing Inverter enable bit in control word not set, or p0852 not configured Set p0852 to r0899.3 (inverter enable)
r0046.10 = 1, pulse inhibit hard-set Drive is in commissioning state, fault, or EP terminal asserted Acknowledge faults, set p10 = 0, check EP terminal
p0300 = 0 and p10 cannot be set to 0 Motor code not selected (non-DQ motor or auto-configuration gap) Manual configuration of motor and encoder as in this article
p3900 = 3 reverts to 0 immediately Calculation aborted because p0300 = 0 or inconsistent Set motor code and encoder type first, then re-run p3900
Motor identification fails with F7011 Motor cannot move safely, encoder missing, or wrong motor code Check encoder wiring, ensure motor shaft is free to move for p1960
"Speed controller inhibited" only on the second drive Topology mismatch on the second axis (this article's scenario) Offline configuration and download as described
Drive in state S2 (Ready for operation) but not S4 Missing OFF1 signal from PLC Check PLC telegram (e.g., telegram 1/2/3/5/102); verify STW1 bit 0 from PROFINET
r0046.21 = 1 after p1960 with overshoot Speed controller gain too high (p1460) Reduce p1460 by 30 % and re-test; verify p1472 > 10 ms

Related SINAMICS faults

Common faults that co-occur with controller-inhibit conditions
Fault / alarm Meaning Remedy
F7011 Motor identification fault Re-run with motor free to rotate; check encoder data
F07802 Drive object does not exist (configuration gap) Re-run configuration; check topology
F07412 Encoder error – bad signal Check encoder cable, shielding, SMC module
F31117 / F31118 Encoder signal level out of tolerance Check encoder supply, cable length, encoder replacement
F08501 PROFINET sign-of-life failure Check PLC cycle, cable, watchdog time
A07929 Drive object not configured Run automatic configuration or manual configuration
F30002 DC link overvoltage Verify Line Module capacity vs. regen load
F30003 DC link undervoltage Verify Line Module mains, check precharge
F30600 Line Module identification failure Check DRIVE-CLiQ wiring to SLM

Preventive Configuration Best Practices

To avoid this asymmetry on multi-axis projects with mixed DQ / non-DQ motors:

  1. Document the DRIVE-CLiQ topology before commissioning. List each axis's motor article number with the 11th character identified. Label every DQ cable, every SMC, and every resolver cable. The article-number-vs-capability table above should be printed and stored with the project.
  2. Insert SMC modules into the topology before auto-configuration. If a non-DQ motor is intended, the SMC20 or SMC30 must be physically wired and visible to the CU320-2 PN's DRIVE-CLiQ ring before Starter auto-configuration runs. Auto-configuration will then create the encoder DO and accept the encoder topology.
  3. Use manual configuration for mixed axes. In the project's drive configuration, mark DQ axes for auto-configuration and non-DQ axes for manual configuration. This is a project-level decision, not a drive-level one – the configuration tab of each drive object controls it.
  4. After every auto-configuration, verify p10 and p3900. Add a commissioning checklist step that reads p10 = 0 and p3900 = 0 on every axis. If either drive reports otherwise, the commissioning is incomplete.
  5. Run the motor identification sequence. For every non-DQ axis, run p1910 = 1 (static motor data identification) and p1960 = 1 (speed controller optimization) once the project is downloaded. These routines populate p0350 / p0352 / p0354 / p0356 with measured values and tune p1460 / p1472.
  6. Save the project to ROM. After successful commissioning, copy RAM to ROM (p0977 = 1) on each drive object so the parameters survive a power cycle.
  7. Use telegram 1/2/3/5 for PLC-driven axes. Standard telegrams pre-wire the control and status word bits; custom telegrams introduce BICO sources that must be reviewed for OFF1 / OFF2 / OFF3 / inverter enable.
  8. Check F-CPU and STO wiring. Safety-integrated applications route STO through the F-CPU and the EP terminal strip on the Motor Module. Missing STO ack is one of the most common reasons r0046.1 (OFF2) sets after a mechanical intervention.

Reference documents

Frequently Asked Questions

Why does only the second axis show "Speed controller inhibited" while the first one works?

The first axis is a 1FK7022-5AK71-1LG0 with an integrated DRIVE-CLiQ interface, so auto-configuration read its electronic nameplate and populated p0300, p0400, and the equivalent-circuit parameters automatically. The second axis is a 1FK7022-5AK71-1AG0 without DRIVE-CLiQ; auto-configuration found no electronic nameplate, left those parameters at zero, and never exited commissioning state. The drive therefore reports OFF1 enable missing and speed controller inhibited because the motor and encoder data are inconsistent.

Why does p3900 = 3 immediately revert to 0?

p3900 = 3 triggers the end-of-quick-commissioning calculation. The calculation requires a valid motor code in p0300 and a consistent motor data set. If p0300 = 0 because the motor was not selected, the calculation aborts and the firmware writes p3900 back to 0. Set the motor code and encoder type first, then re-run p3900 = 3.

Why is writing p10 = 0 rejected with "Value rejected"?

p10 is the commissioning parameter filter. The drive firmware only accepts p10 = 0 when the underlying motor, encoder, and control-mode data are mutually consistent. With p0300 = 0 (no motor selected) the filter rejects the write. Resolve the motor and encoder configuration first and p10 = 0 will be accepted.

What is the difference between the 1FK7022-5AK71-1AG0 and the -1LG0?

The 11th character of the 1FK7 article number encodes the DRIVE-CLiQ designator. "A" means without DRIVE-CLiQ (terminal box connection, resolver via SMC20 or incremental via SMC30). "L" means with DRIVE-CLiQ (integrated encoder interface and electronic nameplate). The mechanical and electrical ratings are otherwise identical for the same shaft height and length.

What does r0046.21 (Speed controller inhibited) actually mean?

Bit 21 of r0046 indicates that the closed-loop speed controller is held in an inactive state because the drive object has not satisfied the enable preconditions. Typical causes are missing motor identification (p1910 / p1960 not run), missing encoder data (p0400 = 0), or a hard pulse inhibit (r0046.10 = 1). Clearing the underlying preconditions clears bit 21.

Can p864 be left at default and still get OFF1?

Yes. When the drive is controlled from a PROFINET master through a standard telegram (1 / 2 / 3 / 5 / 102 ...), OFF1 is sourced from the telegram's bit 0 in the control word and is internally routed to the control-word processing. Changing p864 is only needed if you want a fixed, non-PLC-controlled OFF1 source. An accidental write to p864 with an invalid BICO source is one of the reasons r0046.0 can be set even on a fully configured axis.

Do I have to run p1960 (rotating identification) on a non-DQ motor?

Yes, for any non-DQ motor that was not identified by auto-configuration. p1910 measures the equivalent-circuit parameters (resistance, leakage inductance) statically; p1960 then runs a short travel profile to tune the speed controller gain p1460 and integral time p1472. Skipping p1960 leaves the controller on conservative defaults and shows up as overshoot or sluggish response in the first motion tests.

Back to blog