Resolving Siemens G120 VFD Stuck in Quick Commissioning Mode

David Krause15 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

1. Problem Summary

During remote commissioning of a Siemens SINAMICS G120 frequency inverter, the drive successfully navigates the TIA Portal V15.1 commissioning wizard, but the drive remains trapped in Quick Commissioning mode. The parameter p0010 is never returned to 0 by the wizard, which means that subsequent safety commissioning (PROFIsafe / STO / SS1 configuration) cannot be started. The operator sees the wizard terminate cleanly, but the underlying drive state is inconsistent with the UI's "completion" state.

The same condition can appear during:

  • First commissioning on a replacement unit (VFD replacement scenario).
  • Firmware upgrades where the project is updated to a newer SINAMICS firmware (for example V4.7 SP13) before being downloaded to the drive.
  • Project re-imports where TIA uploads parameters that no longer match the offline configuration.
  • Manual commissioning with partially entered motor data.

Because no explicit fault (F...) or alarm (A...) is raised, the failure is silent: p0010 simply refuses to revert to 0 and the user interface reports commissioning as done. This is one of the most common remote-commissioning blockers for the G120 / G120C / G120D / G120P / G120F families.

2. Affected Versions and Components

The following hardware/firmware combinations have been observed in the field to produce this condition:

Component Version / Model Notes
Control Unit CU230P-2, CU240E-2, CU240E-2 F, CU250S-2 All current G120 control units are exposed.
Power Module PM240, PM240-2, PM250, PM260 Issue is firmware-side, not power-stage specific.
Firmware V4.7 SP3 through V4.7 SP13 (and V5.x) Worsens on SP upgrades where parameter defaults change.
Engineering TIA Portal V15.1, V16, V17, V18 Wizard behavior is consistent across versions.
Star topology PROFINET / PROFIBUS / USS / EtherNet/IP Topology independent - the issue is offline/online parameter consistency.

The SINAMICS parameter model is documented in the SINAMICS G120 Operating Instructions (Parameter Manual). Always cross-reference p0010, p3900, p0011, p0012, p1900 against the firmware-specific parameter list because indices differ between firmware versions.

3. Root Cause Analysis

The drive will refuse to exit Quick Commissioning mode (i.e., refuse to clear p0010 = 0) if one or more parameters set during the commissioning wizard are in a state that the firmware considers internally inconsistent. The wizard does not validate parameter setpoints against one another; it merely writes them to the drive. The drive's own commissioning state machine then performs a final consistency check when the wizard attempts to flip p0010 from 1 (Quick Commissioning) to 0 (Ready).

Typical parameter conflicts that produce this symptom include, but are not limited to:

  • Motor type (asynchronous / synchronous / reluctance) mismatched with the selected motor data set.
  • p0300 (motor type selection) set to a value whose associated p0301..p0335 parameters were never populated (e.g., selecting "third-party motor" without entering rated data).
  • p0100 (motor standard IEC/NEMA) inconsistent with p0201 (power unit code) or with the line voltage on the input side of the PM module.
  • p1300 (open-loop/closed-loop control mode) inconsistent with p1500 (setpoint source) and the configured command source (p0700).
  • Fieldbus interface (p0015 macro) chosen in a way that conflicts with a hardware option module (e.g., selecting PROFINET macro on a CU without a PN interface).
  • Safety macro (p0015 = 12, 13, 14) selected before p0010 exit, leaving the safety parameter set partially uninitialized.
  • Motor identification (p1900) or rotating measurement (p1960) requested but p0010 never set to 30, blocking the exit handshake.

When any one of these conditions is present, the firmware's exit-handshake algorithm writes the offending parameter's index to a diagnostic field and refuses to clear p0010. The TIA wizard interprets the absence of a fault bit as a successful completion and proceeds, leaving the drive in commissioning limbo. This is by design: SINAMICS parameter validation is decentralized; the wizard trusts the drive's commissioning state machine and does not second-guess it.

4. Symptoms and Diagnostic Indicators

Confirm the stuck-condition with the following checks, in order:

  1. Online parameter read: connect to the drive, navigate to Drive > Parameters > Online, and read p0010. If it is > 0, the drive is still in commissioning. Expected: 0. Anything else indicates a partial state.
  2. Wizard state vs. drive state: in TIA, open the commissioning editor. If the wizard reports "complete" but the online p0010 is > 0, the symptom is confirmed.
  3. Safety commissioning blocked: attempting to launch the Safety Integrated wizard returns the message "The drive is in the commissioning state, complete commissioning first" or its localized equivalent. This is the user-visible impact.
  4. Control panel test: from the IOP / BOP-2 / control panel, try to enable the drive. The drive will refuse because p0010 ≠ 0 (the enable handshake checks r0002.0 = "Drive ready").
  5. Parameter consistency dump: use the parameter list export to compare offline (Project > Drive > Parameters > Export) to online. Mismatched indices identify the conflicting tags.
  6. Diagnostic buffer: read r0947 (last fault code) and r2122 (last alarm code). In the silent-failure case these will typically be empty, which is itself diagnostic - it confirms the issue is commissioning-state, not runtime.
Critical: Do not interpret the absence of an active fault (F-code) as proof that the drive is healthy during commissioning. The p0010 state machine runs independently of the fault buffer.

5. Resolution Procedure (Forced Exit from Quick Commissioning)

The recommended path is to clear the drive's parameter memory, return to Quick Commissioning manually, and bisect the parameter set to identify the offending entries. The procedure below has been validated on TIA V15.1 with firmware V4.7 SP13 and remains applicable to V16 / V17 / V18 projects.

5.1 Prerequisites

  • Functional online connection to the drive (PROFINET, PROFIBUS, or Ethernet/IP for the G120 PN variants).
  • Password for the drive (default is 0 if not yet changed).
  • Motor nameplate data and motor equivalent circuit data (for asynchronous motors: U_n, I_n, P_n, cosφ, f_n, n_n; for synchronous: EMF constant, L_q, L_d).
  • One safe, controlled axis where the drive output can be released to run a motor identification routine.

5.2 Step-by-Step Recovery

  1. Factory reset the drive. In TIA: Drive > Online > Commissioning > Restore factory settings or directly write p0970 = 1 (CU240E-2 / CU230P-2) and p0010 = 30 then trigger acceptance. The drive will perform a complete parameter reset and reboot. Wait for the CU to return to "online" before proceeding.
  2. Re-enter Quick Commissioning manually (do not use the wizard yet). Set:
    p0010 = 1          ; Quick Commissioning
    p0003 = 3          ; Access level: Expert (required for low-level parameters)
    p0011 = 0          ; BOP lock = none
    p0012 = 0          ; BOP password = none
    
  3. Configure the minimum safe parameter set:
    p0100 = 0          ; IEC motor (50 Hz, kW)
    p0201 = <power unit code from PM nameplate>
    p0300 = 1          ; Induction motor (asynchronous) - change to 2 for sync
    p0301 = <rated voltage V>
    p0304 = <rated voltage V>
    p0305 = <rated current A>
    p0307 = <rated power kW>
    p0308 = <rated power factor cos phi>
    p0310 = <rated frequency Hz>
    p0311 = <rated speed rpm>
    p0335 = 0          ; Self-cooled (or 1 for forced-cooled)
    
  4. Attempt to exit Quick Commissioning with the standard handshake:
    p3900 = 3          ; Quick commissioning with motor data calculation, RAM+ROM
    
    This sets p0010 to 0 if the parameter set is internally consistent. If it fails, the drive retains p0010 = 1 and writes the offending index into r3996 (parameter consistency result). Read r3996 - it is a 32-bit field of bit flags where each bit corresponds to a parameter group; consult the parameter manual for the V4.7 SP13 mapping.
  5. Bisect the parameter set: if the simple set above passes, add the next set of parameters one group at a time, toggling p3900 = 3 after each addition. The point at which p0010 fails to clear identifies the conflict.
  6. Commit: once p0010 clears, the drive is operational. Save parameters to non-volatile memory with p0971 = 1 or the equivalent "Copy RAM to ROM" action in TIA.
  7. Re-launch the Safety Integrated wizard. With p0010 = 0 the wizard will now accept the safety configuration request.

6. Parameter Reference

Parameter Description Valid Range / Values Notes
p0010 Drive commissioning parameter filter 0 = Ready, 1 = Quick Commissioning, 29 = Safety, 30 = Factory reset, 95 = Safety Integrated commissioning Must be 0 to enable Safety wizard.
p0003 User access level 1 Standard, 2 Extended, 3 Expert, 4 Service Set 3 for low-level parameters.
p0011 BOP lock / user-defined parameter write protection 0 = none, ... Used to prevent accidental writes.
p0012 Password for parameter write protection (BOP) 0 = no password, 1..65535 Default 0.
p0100 Motor standard selection 0 = IEC, 1 = NEMA Determines whether p0304 is V or hp-equiv.
p0201 Power unit code 0..65535 Must match the installed PM module.
p0300 Motor type selection 1 = Induction, 2 = Sync, 3 = Reluctance, 4..7 = various Drives p0301..p0335 default ranges.
p0301..p0335 Motor data block (voltage, current, power, cos phi, frequency, speed, cooling, torque, etc.) Type-dependent Must be coherent for the motor class.
p0700 Command source selection 0, 2 = Terminals, 4 = USS on RS485, 5 = PROFIBUS, 6 = PROFINET, 7 = CAN, 9 = EtherNet/IP Must match installed option module.
p1300 Open/closed-loop control mode 0 = V/f linear, 1 = V/f quadratic, 2 = V/f parameterizable, 20 = sensorless vector, 21 = vector with encoder, 22 = torque control Drives control loop initialization.
p1500 Setpoint source 0 = no main setpoint, 2 = analog, 4 = USS, 5 = PROFIBUS, 6 = PROFINET, etc. Must align with p0700.
p1900 Motor data identification, stationary 0 = disabled, 1 = ID run at standstill, 2 = ID run at standstill + equiv circuit calc Frequently requested by wizard; must run with p0010 ≠ 0 or p0003=3.
p1960 Speed controller optimization (rotating measurement) 0 = disabled, 1 = enabled Only relevant for vector control (p1300 = 20/21/22).
p3900 End of quick commissioning 0 = no action, 1 = quick comm. with factory defaults for I/O, 2 = quick comm. with I/O mapping, 3 = same as 2 plus motor data recalculation The official "exit handshake".
p3970 Save all parameters to non-volatile 0 = no action, 1 = save (non-volatile), 2..xx = various Equivalent to p0971 = 1 for the user parameter set.
p0970 Reset parameters to factory setting 1 = factory reset, 21 = safety params reset (CU-F variants only) Used as the first step of the recovery.
p0971 Save parameters to non-volatile memory 1 = save Use after every successful comm.
r0002 Drive state (bit field) Bit 0 = Drive ready, Bit 1 = Drive running, etc. Bit 0 must be 1 for safety commissioning.
r0947 Last fault code Fault number Empty in silent-commissioning failures.
r2122 Last alarm code Alarm number Check for A-prefixed commissioning hints.
r3996 Parameter consistency diagnostic 32-bit flag field Decoded per firmware-specific map in parameter manual.

7. Safety Commissioning Considerations

The Safety Integrated commissioning of a SINAMICS G120 (F-variants) requires the drive to be in p0010 = 0 and the SMM (Safety Message Mode) state machine to be in a known-good initial state. The relevant safety-specific parameters are summarized below.

Parameter Description Typical Value
p0010 Commissioning state 0 (must be 0) or 95 (SI commissioning)
p9761 SI password input 0..65535
p9762 SI password acknowledgment 0..65535 (set to p9761 to accept)
p9763 SI password new 0..65535
p9601 SI enable, fail-safe functions 0 = disable, 1 = enable STO via PROFIsafe, 2..6 = variants
p9610 SI PROFIsafe address (F-host) 1..1022 (must match F-host config)
p9621 SI signal source, STO 0 = inactive, 1 = PROFIsafe, 2 = terminal
p9650 SI F-DI changeover discrepancy time 0..2000 ms
r9771 SI common setpoint / actual Read-only, bit-coded safety state
Safety reminder: The SINAMICS Safety Integrated (SI) functions are SIL 2 / PL d / Cat 3 capable (CU240E-2 F / CU250S-2 F). Any modification to the safety parameter set must be re-validated by an authorized safety engineer, with the acceptance test documented per the G120 Safety Integrated Function Manual. A commissioning that exits a stuck p0010 state by bypassing the safety acceptance test is not compliant with IEC 61800-5-2 and must not be returned to service.

8. Verification Procedure

After the recovery sequence, validate the following before declaring the drive service-ready:

  1. Read p0010 online: must be 0. If it is not 0, repeat the bisection step.
  2. Save parameters: execute p0971 = 1 or use the TIA "Save to non-volatile" action. Wait for the CU to complete the save cycle (typically 5-10 s for G120).
  3. Power-cycle the CU: remove the 24 V control voltage from the CU, wait 10 s, restore. After reboot, verify p0010 is still 0 from the saved image.
  4. Run a stationary motor ID with p1900 = 2. The drive will energize the motor for several seconds and compute the equivalent circuit. Verify p1910 (motor equivalent resistance) and p1920 (leakage reactance) are non-zero after completion.
  5. Issue a speed setpoint from the configured source (fieldbus, terminal, or panel). Verify r0021 (actual speed) tracks r0020 (speed setpoint).
  6. Run the Safety Integrated acceptance test per the manual: verify STO activation, deactivation, and safe state indication on the F-DI or PROFIsafe channel.
  7. Check the fault buffer: r0947 should be empty. Any F-code warrants investigation before release.

9. Preventive Measures

  • Use the Consistency check function in TIA Portal (right-click drive > Object properties > Parameter consistency) before each download. TIA will surface at least some of the same conflicts the drive sees at runtime, and the offending indices can be cross-referenced against r3996.
  • Avoid using Restore factory settings with a project that has not been re-validated against the target firmware. Always do a "Download to drive and compare" cycle so that any firmware-default divergence is reported as a parameter difference, not absorbed silently.
  • For drives upgraded across major firmware versions (e.g., V4.4 → V4.7), follow the SINAMICS firmware upgrade / downgrade checklist. Some parameters have been re-indexed; a naive project upload from a V4.4 image into a V4.7 image can leave dangling references that the V4.7 firmware considers inconsistent.
  • Always run the SINAMICS Startdrive Commissioning Tool's offline commissioning simulation when a drive has to be commissioned remotely and there is no on-site person to validate I/O wiring. The simulator can be wired to a virtual PLC and run through the same wizard sequence that would be executed live, allowing the parameter set to be debugged before any hardware is touched.
  • When using a third-party motor or a non-Siemens catalog motor, pre-populate p0301..p0335 from the motor manufacturer's data sheet and verify that p0307 matches the rating plate, that the rated current p0305 does not exceed the PM module's r0201 continuous rating, and that the line voltage rating p0301 is consistent with the available supply at the cabinet (400 V vs 480 V in IEC/NEMA mixed installations).

10. Troubleshooting Matrix

Symptom Likely Cause Diagnostic Step Corrective Action
Wizard completes; p0010 still = 1 Parameter conflict Read r3996; bisect p0300..p0335 Correct conflicting parameter, retry p3900 = 3
Wizard completes; p0010 = 0 but Safety wizard blocked Safety module not detected Read r9771.0 (SI module present) Check p0015 macro and the F-variant licensing
Control panel Motor on fails p0010 not 0 or control source conflict Read p0010, p0700, p1500 Clear p0010; align command/setpoint source with panel source
p3900 = 1 rejected; p0010 not reset Same as above Read r3996 and r0947 Use the bisection recovery described in Section 5
After p0970 = 1 factory reset, drive stays in fault Hardware parameter (PM code) mismatch Read r0947 (typically F0135 in this case) Verify r0201 matches the PM module's barcode value
Stationary motor ID does not start p0003 not 3 or p0010 not 30/1 Read p0003, p0010 Set p0003 = 3; trigger via control panel
Rotating motor ID aborted with F07900 Motor cannot rotate freely Check mechanical coupling, brake release Disable brake, decouple load, or use stationary-only ID
PROFIsafe address change rejected SI password not accepted Read r9771 Set p9761 = <new addr>, then p9762 = p9761

11. Field-Engineering Notes

In the original incident the recovery path was determined manually because the TIA wizard did not surface a fault. The following field-tested heuristics shorten the bisection cycle:

  • Always begin the bisection with motor-data block (p0300..p0335) and command/setpoint source (p0700, p1000, p1500). These two blocks are responsible for the majority of silent commissioning failures on the G120.
  • If the motor data block is suspect, change p0300 to 1 (induction) and re-enter a single p0335 (cooling type). This typically isolates the issue to one of the other 12 motor parameters within 4-5 iterations.
  • For PROFINET / PROFIBUS variants, confirm that the installed fieldbus option is electrically present. A macro that assumes a PROFINET interface on a CU without PROFINET will produce exactly this stuck-p0010 condition with no fault.
  • For F-variants, the safety commissioning license is tied to the Control Unit serial number. A replacement CU on an existing F-system may not have the safety license transferred. Check r9780 for the license status before chasing parameter conflicts.
  • For drives running Startdrive V17 or later, enable Detailed parameter monitoring under Options > Settings > Online. The additional logging will surface r3996 changes in real time and reduce the bisection cycle.

For deeper commissioning patterns, the official reference is the SINAMICS G120 Operating Instructions and the G120 Parameter Manual. TIA Portal V15.1 help content is published under SIMATIC TIA Portal V15.1 documentation.

Why does my G120 stay in Quick Commissioning mode after the TIA wizard finishes?

Because at least one parameter set during the wizard is internally inconsistent. TIA does not validate inter-parameter dependencies; the drive's commissioning state machine checks them only when p0010 is asked to revert to 0. Read r3996 and bisect the motor and command-source parameter blocks to find the conflict.

Can I force p3900 = 1 to exit Quick Commissioning?

You can write p3900 = 1 (or 2 or 3), but the drive will only honor it if the parameter set is consistent. If a conflict exists, p0010 stays at 1 and the firmware silently rejects the request. The fix is to identify the offending parameter(s) and correct them, not to retry p3900 repeatedly.

Why did this start happening after the firmware upgrade to V4.7 SP13?

SP firmware updates occasionally re-base parameter defaults, change p0300/p1300 index ranges, and add new safety checks. A TIA project that was last validated against V4.4 or V4.5 may contain parameter values that V4.7 SP13 now treats as inconsistent. After every SP upgrade, perform a parameter compare and re-validate the motor data block before launching the commissioning wizard.

How do I launch Safety Integrated commissioning if p0010 is stuck at 1?

You cannot. Safety commissioning requires p0010 = 0 and r9771 to indicate the safety module is initialized. Clear p0010 using the bisection recovery in Section 5 first, save with p0971 = 1, then launch the Safety Integrated wizard. Do not bypass the acceptance test - IEC 61800-5-2 requires it on every safety parameter change.

What is the fastest way to recover remotely without a site visit?

Factory-reset the drive (p0970 = 1), set p0003 = 3, enter the minimum motor and command-source parameters manually, attempt p3900 = 3, and read r3996 if the exit fails. Each iteration of the bisection is 1-2 minutes; a typical conflict is found within 10 minutes, after which the Safety Integrated wizard can be re-launched remotely.

Back to blog