News

Siemens Inverter Closed-Loop Control Motor Won’t Start: Complete Troubleshooting Guide

Siemens Inverter Closed-Loop Control Motor Won’t Start: Complete Troubleshooting Guide

Comprehensive Diagnostic & Solution Manual for Industrial Automation Engineers


Introduction

When a Siemens inverter (Variable Frequency Drive, VFD) fails to start a motor in closed-loop control mode, the consequences can halt an entire production line. Unlike open-loop systems, closed-loop configurations rely on real-time feedback from encoders or sensors to precisely regulate motor speed and torque. When something goes wrong in this feedback chain, the motor may refuse to start entirely — or worse, behave unpredictably.

This guide provides a systematic, step-by-step troubleshooting methodology covering power issues, parameter misconfiguration, hardware faults, sensor failures, and mechanical binding. Whether you’re a plant maintenance technician, a PLC programmer, or an automation engineer, you’ll find actionable diagnosis procedures backed by Siemens official documentation and field experience.

Keywords covered: Siemens VFD troubleshooting, closed-loop motor control, inverter fault diagnosis, Siemens inverter F0001 F0003, encoder feedback issues, PLC-integrated drive systems.


Table of Contents

  1. Understanding Siemens Closed-Loop Inverter Control
  2. Power System Inspection
  3. Parameter Configuration Audit
  4. Hardware Fault Diagnosis
  5. Encoder & Feedback Sensor Testing
  6. PLC & Control Signal Verification
  7. Mechanical Load Assessment
  8. Advanced Drive Parameter Optimization
  9. Siemens-Specific Fault Code Reference
  10. Preventive Maintenance Checklist

1. Understanding Siemens Closed-Loop Inverter Control

1.1 How Closed-Loop Control Works in Siemens VFDs

In a closed-loop configuration, the Siemens inverter continuously compares a setpoint (target speed/torque) from the PLC or HMI against the actual value measured by a feedback device — typically a rotary encoder mounted on the motor shaft. The inverter’s internal PID controller calculates the error and adjusts the output frequency and voltage to minimize the error in real time.

Key components in the loop:

  • PLC or Controller — Issues the setpoint via analog signal (0-10V / 4-20mA) or fieldbus (Profibus, Profinet, EtherNet/IP)
  • Siemens VFD (e.g., SINAMICS G120, S120, or Micromaster series) — Receives setpoint, runs PID, outputs power to motor
  • Encoder / Feedback Sensor — Provides actual speed/position data back to the drive
  • Motor — Receives regulated power, drives the mechanical load

1.2 Why Closed-Loop Failures Cause Motor Stalling

A motor won’t start — or will start then stall — when:

  • The feedback signal is absent, causing the drive to “chase” an unreachable target
  • The setpoint is contradictory to the feedback (e.g., reverse setpoint with forward encoder)
  • The PID output is saturated due to excessive error, triggering internal protective shutdown
  • Hardware protection (OVP, OCP, OTP) trips before the motor can reach operating speed

1.3 Preliminary Safety Notice

⚠️ WARNING: Before any electrical inspection, ensure the drive is in a safe, de-energized state. Wait at least 5 minutes after disconnecting power to allow DC link capacitors to discharge. Use appropriate PPE (insulated gloves, arc-flash face shield). Failure to do so may result in serious injury or death.


2. Power System Inspection

2.1 Verify Supply VoltagePresence

Symptoms: Motor does not respond at all; no display on the inverter panel.

Procedure:

Step 1: Measure the three-phase supply voltage at the drive’s input terminals (L1, L2, L3) using a digital multimeter (DMM).

Voltage LevelExpected RangeAction if Out of Range
380V systems342V – 418V ACInvestigate supply transformer, check for phase loss
220V systems198V – 242V ACCheck single-phase supply quality
DC Bus voltage1.35 × Line-to-Line AC voltageBelow spec indicates power stage failure

Step 2: Check for phase sequence correctness. Some Siemens drives require correct phase rotation; reversed phases can prevent startup or trigger Fault F0003 (DC Overvoltage).

Step 3: Inspect all fuses and circuit breakers upstream of the drive. A single blown fuse causes phase imbalance → motor won’t start.

Recommended tools: Fluke 87 DMM, Fluke 375 FC clamp meter, Fluke 1FC2 phase rotation meter.

2.2 Analyze F0003 DC Link Overvoltage

The F0003 fault is one of the most common causes of motor stalling in Siemens inverters. It triggers when the DC bus voltage exceeds 1.25× the rated value.

Common causes:

  • Regenerative braking from a decelerating load exceeding the drive’s braking resistor capacity
  • Supply voltage spikes from nearby heavy machinery switching
  • Incorrect parameter P0210 (supply voltage) set lower than actual, causing false overvoltage detection
  • Braking resistor (BR) failure — open circuit eliminates the regenerative path

Resolution steps:

  1. Verify P0210 matches actual supply voltage (e.g., set to 380V for 380V systems)
  2. Check the braking resistor wiring and resistance value (compare against datasheet)
  3. If load has high inertia, extend deceleration ramp time (P1121 for G120)
  4. Consider adding an external braking module or increasing resistor power rating

2.3 Inspect Grounding & EMC Compliance

Poor grounding can cause:

  • Intermittent operation — motor starts sometimes, fails other times
  • Erratic encoder feedback, resulting in PID instability
  • False overcurrent and overvoltage faults

Checklist:

  • ✅ Drive chassis ground strap connected to main ground bus (≤10Ω continuity)
  • ✅ Motor ground wire separate from signal cable (no shared ground loops)
  • ✅ Encoder shield grounded at drive end only (not both ends — double grounding creates ground loops)
  • ✅ EMC filter installed within 1m of the drive input

3. Parameter Configuration Audit

3.1 Critical Parameters for Closed-Loop Operation (Siemens G120 / SINAMICS)

Below are the parameters that most frequently cause motor startup failures when misconfigured:

ParameterDescriptionTypical Error Causing Motor Stall
P0210Supply voltageSet too low → false OV fault
P0300Motor type selection1=异步, 2=同步 — wrong setting causes unstable control
P0304Motor rated voltageMust match nameplate exactly
P0305Motor rated currentUsed for motor model — wrong value causes thermal O/C
P0307Motor rated power (kW/HP)Incorrect setting affects torque calculation
P0310Motor rated frequency50Hz or 60Hz per motor nameplate
P0311Motor rated speedUsed in encoderless operation and slip compensation
P1080Minimum frequencySet too high → motor can’t reach required speed
P1082Maximum frequencySet too low → motor speed capped below requirement
P1120Ramp-up timeToo long → motor doesn’t reach operating speed in expected time
P1121Ramp-down timeToo short → overvoltage fault during deceleration
P1310Boost — starting torqueToo low → insufficient starting torque in heavy load
P1500Motor control modeMust be set correctly for encoder feedback (p1500=1 for encoder)

3.2 Encoder Configuration for Closed-Loop

P1500 = 1 is the key parameter: it tells the drive to use an encoder for speed feedback.

Additional encoder parameters:

  • P0400 — Encoder type (incremental/absolute)
  • P0408 — Encoder pulses per revolution (PPR). E.g., 1024 PPR, 2048 PPR, 4096 PPR
  • P0430 — Encoder filter time (reduces noise but adds lag)
  • P0440 — Encoder evaluation (e.g., 1 = A/B track evaluation)

Warning: If P1500 is set to 0 (sensorless / open-loop), the drive operates without encoder feedback. A motor may struggle to start if the load demands more torque than the open-loop torque boost can provide.

3.3 PLC Setpoint Signal Verification

Check the analog input configuration:

For 4-20mA current signal:

  • Measure the current with a DMM in series with the signal loop (should be 4-20mA, not 0mA)
  • Verify that P2015 (analog input filter) isn’t set too high, which can cause sluggish response
  • Check that P0756 (analog input scaling) correctly maps 4mA = 0Hz and 20mA = max frequency

For Profibus / Profinet fieldbus:

  • Verify node address (PA) matches PLC configuration
  • Check that the cyclic data exchange is active (LED indicators on the drive)
  • Confirm the setpoint word (STW1) contains valid run command + speed setpoint

3.4 PID Controller Tuning

If the motor starts but oscillates or hunts around the setpoint, the PID gains need adjustment:

  • P1650 — Speed controller Kp (proportional gain). Too high → oscillations. Too low → sluggish response.
  • P1651 — Speed controllerTn (integral time). Too low → overshoot. Too high → steady-state error.
  • P1652 — Speed controller Tv (derivative). Use for anticipatory action on load changes.

Basic tuning procedure:

  1. Set P1650 to a conservative value (e.g., 0.5× default)
  2. Gradually increase Kp until slight oscillation appears
  3. Back off by ~20%
  4. Adjust Tn to eliminate steady-state error without causing overshoot

4. Hardware Fault Diagnosis

4.1 Drive Output Stage Testing

Using a megohmmeter (Megger):

Step 1: Disconnect motor leads from the drive output (U, V, W terminals).

Step 2: Measure insulation resistance between each phase and ground:

  • Acceptable: > 1MΩ (motors in good condition)
  • Warning: 100kΩ–1MΩ — motor humidity contamination, monitor closely
  • Failure: < 100kΩ — motor winding must be dried or rewound

Step 3: Measure winding continuity (resistance between U-V, V-W, W-U):

  • Values should be nearly equal (within 5%). Large imbalance indicates winding fault.
  • Infinity reading = open winding → motor must be replaced.

Using a clamp meter for operating current:

Step 1: Clamp around one output phase conductor while the drive is running.

Step 2: Compare measured current against the motor nameplate rated current.

  • No current flow → drive is not conducting (check output stage, trigger pulses from control board)
  • Current way below nameplate → motor not receiving full voltage, check PWM outputs with oscilloscope

4.2 IGBT & Power Module Testing

Warning: This test requires knowledge of power electronics. Proceed only if qualified.

The IGBT (Insulated Gate Bipolar Transistor) modules are the primary switching elements in modern Siemens VFDs. A failed IGBT will:

  • Trigger F0001 (Overcurrent) fault
  • Cause random trips during acceleration
  • Produce a characteristic “buzzing” sound from the drive

Basic in-circuit testing (drive de-energized):

  1. Use a digital transistor tester or curve tracer
  2. Test each IGBT’s body diode forward/reverse characteristics
  3. Check gate-emitter resistance (should be > 10MΩ with gate shorted to emitter)
  4. Any short between collector-emitter indicates failed IGBT — replacement of power module required

4.3 Control Board Self-Diagnosis

Siemens G120 and Micromaster drives feature a parameter-based self-diagnosis:

  • r0002 — Drive operational status (Running / Stopped / Fault)
  • r0947 — Fault history (last 8 faults with fault codes)
  • r0948 — Fault time stamps (in hours of operation)
  • r0949 — Fault additional value (provides manufacturer-specific fault detail)

If the fault history shows repeated F0001 (overcurrent) faults at startup:

  • The power module may be degrading
  • Motor cable may have insulation damage (check with megger at the cable end)
  • Motor may be drawing excess starting current due to winding short

4.4 Cooling & Thermal Management

Overheating causes protective shutdown that mimics a motor stalling symptom:

  • Check the heatsink temperature via parameter r0037
  • Verify that cooling fans are operational (audible, directional airflow)
  • Clean heatsink fins of dust and debris (compressed air blow-out)
  • For cabinet-mounted drives, ensure ventilation openings are unobstructed
  • Confirm that ambient temperature is within drive specification (typically -10°C to +50°C for industrial drives)

5. Encoder & Feedback Sensor Testing

5.1 Incremental Encoder Signal Verification

Tools required: Oscilloscope (2-channel), Encoder signal cable.

Signal checks:

Channel 1 → Encoder A output
Channel 2 → Encoder B output (90° phase-shifted from A)

TestExpected ResultFailure Indicator
Signal amplitude0.5V to 1.0V peak-to-peak (verify against encoder datasheet)Flat-line = open circuit
A/B phase relationship90° phase shift (Quad-A/B mode)In-phase = wiring error
Index pulse (Z)One pulse per revolutionMissing Z = encoder failure

Procedure:

  1. Spin the motor shaft manually at ~1 revolution per second
  2. Observe oscilloscope for clean, rectangular A/B pulse trains
  3. If signals are noisy or attenuated, check cable shielding and routing
  4. If signals are absent, swap encoder channels to isolate whether cable or encoder is at fault

5.2 Absolute Encoder Configuration

For absolute encoders (EnDat, Hiperface, SSI), verify:

  • Correct protocol selected in P0400 and drive parameter set for the specific interface type
  • Wiring pinout matches the drive’s encoder interface (typically Sub-D or circular connector)
  • Baud rate and resolution parameters correctly entered
  • For EnDat encoders: verify that the drive’s encoder interface card is compatible with the encoder protocol

EnDat specific troubleshooting:

  • Use the drive’s built-in encoder diagnostic parameter r0451 to view raw position data
  • If data is garbled or stuck, suspect communication line noise or incorrect termination
  • Add a 120Ω termination resistor at the drive end of the cable if the encoder requires it

5.3 PLC Closed-Loop Tuning: PID Fundamentals

The PID loop in a PLC-PID configuration operates differently than in the drive’s internal speed control. Two scenarios exist:

Scenario A: Drive handles PID (drive-based closed-loop)

  • Drive receives speed setpoint from PLC
  • Drive’s internal PID uses encoder feedback to regulate speed
  • PLC is “hands-off” once setpoint is sent

Scenario B: PLC handles PID (PLC-based closed-loop)

  • Encoder feeds back to PLC (via high-speed counter card)
  • PLC calculates PID output and sends as analog setpoint to drive
  • Drive operates in open-loop (speed mode) following the PLC’s 4-20mA command

For Scenario B, ensure:

  • PLC analog output is calibrated (0% = 4mA, 100% = 20mA)
  • PLC scan time is fast enough for the control loop (PID rate > 10× the system’s natural frequency)
  • Encoder count direction matches motor rotation direction (invert if needed in PLC software)

6. PLC & Control Signal Verification

6.1 Digital Control Word (STW1) Decode

For drives connected via Profibus/Profinet, the control word (STW1) is a 16-bit binary value that commands the drive’s state. A motor won’t run if the wrong bit pattern is sent.

Key bits in STW1:

  • Bit 0 (ON/OFF1) — Must be set to 1 to enable the drive
  • Bit 1 (OFF2) — Must be 0 (0 = no emergency stop)
  • Bit 2 (OFF3) — Must be 0 (0 = no fast stop)
  • Bit 3 (Enable Operation) — Must be 1 to allow inverter to output power
  • Bit 4 (Enable Ramp Generator) — Set 1 to allow speed to change
  • Bit 6 (Master Control) — Valid command, must be 1

Troubleshooting: Use a PLC watch table to monitor the actual control word value being sent. If any of bits 1, 2, or 6 are incorrectly configured, the drive won’t start.

6.2 Speed Setpoint Processing

For analog (4-20mA) setpoint:

  • Confirm the PLC analog output card is scaled correctly
  • Test with a calibrated current meter in series
  • Try injecting a manual signal (use a calibrator to output 12mA = 50% speed) to isolate whether the issue is in the PLC program

For Profinet/PROFINET setpoint:

  • Check that the cycletime (update rate) is adequate for the application
  • Increase the process data width to include a status word (ZSW) in addition to the setpoint for full diagnostic visibility
  • Use Wireshark or a network sniffer to verify telegram traffic if communication appears dead

6.3 Emergency Stop Circuit Integrity

An improperly wired emergency stop circuit is a common cause of intermittent motor stalling — the drive may run for minutes or hours before the fault condition is accidentally triggered.

Checkpoints:

  • Emergency stop button NC contacts must wire into the drive’s safety enable circuit (or via safety relay)
  • Test all emergency stop buttons manually (bypass PLC logic, test at the hardwired circuit level)
  • Verify that the drive’s STO (Safe Torque Off) or SS1 (Safe Stop 1) function is not incorrectly activated
  • Check the safety relay LED indicators — a de-energized relay indicates the STO circuit is open

7. Mechanical Load Assessment

7.1 Manual Shaft Rotation Test

Objective: Determine whether the motor can physically turn the load.

Procedure:

  1. De-energize the entire system (drive OFF, motor disconnected from VFD output)
  2. Manually rotate the motor shaft or driven equipment (coupling, belt, chain)
  3. Feel for resistance, grinding, binding, or unexpected resistance

Interpretation:

  • Smooth rotation with consistent resistance — load is mechanically normal
  • Cogging or stepping — gear damage, bearing failure, or foreign object in mechanism
  • Excessive resistance — seized bearing, seized pump impeller, jammed gearbox, or dried-out lubricant
  • Free rotation but drive still won’t start — electrical/control issue confirmed

Note: On large motors (>10kW), manual rotation may be impossible. Use a torque wrench or rotate via the motor’s own power at very low frequency (0.5Hz with controlled torque) to test.

7.2 Coupling & Alignment检查

Misalignment symptoms:

  • Motor runs but draws higher than rated current
  • Vibration increases over time
  • Coupling wear accelerates dramatically

Acceptable alignment tolerance (motor-to-driven equipment):

TypeParallel offsetAngular gap
Flexible coupling< 0.05mm< 0.05mm
Rigid coupling< 0.02mm< 0.02mm

Check procedure:

  1. Use a dial indicator or laser alignment tool
  2. Check both angular and parallel misalignment
  3. Realign if offset exceeds tolerance values above
  4. Inspect coupling elastomer/element for wear, hardening, or cracking — replace if deteriorated

7.3 Load Inertia vs. Drive Capacity

High-inertia loads can exceed a drive’s ability to accelerate within the allowed current limits, causing an F0001 overcurrent fault during the acceleration ramp.

Quick calculation:

  • If the load inertia exceeds 5× the motor rotor inertia, a standard VFD may not be able to accelerate it reliably without extended ramp times or a heavier-rated drive.
  • Extended acceleration ramps (P1120) can compensate for moderate inertia mismatch
  • For extreme inertia loads, a DC bus choke or dynamic braking resistor may be required

7.4 Hydraulic System Back Pressure

For pump and fan applications, verify:

  • No obstruction in the discharge line (check valves, filters, blockages)
  • Back pressure readings are within design range
  • Relief valves are not stuck in partially open position
  • Variable displacement pumps are not commanded to zero displacement (which creates a locked load condition)

8. Advanced Drive Parameter Optimization

8.1 Start-Up Mode Selection

Siemens G120 drives support multiple start-up modes:

  • OFF1 (Standard) — Ramp to setpoint, standard ramp-out on stop
  • OFF2 (Free format) — Immediate output cutoff, coast to stop
  • OFF3 (Fast stop) — Controlled fast ramp stop with preset deceleration time
  • ON/REV — Start in forward/reverse direction

For a motor that will not start at all, the parameter P0840 (ON/OFF1 command source) must be correctly configured to receive a digital signal from the PLC or a local control panel.

8.2 Motor Data Autotuning

Siemens drives include an automatic motor tuning function (P1900). Running this procedure significantly improves motor performance in closed-loop mode.

Procedure:

  1. Ensure motor is disconnected from any mechanical load (or load is decoupled)
  2. Set P1900 = 2 (full motor identification, including encoder alignment)
  3. Press the START button (or send the enable command via fieldbus)
  4. The drive will inject test signals and measure motor parameters over ~30-60 seconds
  5. Monitor r0052 for status (bit 0 = identification active)
  6. After completion, verify P0340 (motor data in derived units) has been populated

⚠️ Warning: Motor must be able to rotate freely during tuning. Any mechanical blocking will cause the process to fail or produce incorrect parameters.

8.3 Speed Controller Adaptation

After autotuning, the drive calculates default speed controller settings. For heavy loads or dynamic applications, manual refinement may be needed:

Parameters to adjust:

  • P1460 — Speed controller Kp (proportional gain, reduces response time)
  • P1462 — Speed controller integral time Tn (eliminates steady-state error)
  • P1470 — Encoderless speed controller Kp (for sensorless mode)
  • P1472 — Encoderless speed controller Tn

Tuning for stiff, precise positioning applications:

  • Increase Kp (reduce P1460 value) for faster response — but watch for overshoot
  • Reduce Tn (reduce P1462 value) for less integral lag — but watch for oscillation

Tuning for soft, inertial loads:

  • Decrease Kp (increase P1460 value) to smooth out torque fluctuations
  • Increase Tn (increase P1462 value) to reduce overshoot

8.4 Flying Restart Function

For motors that need to restart while the driven equipment is still coasting (e.g., fans, large pumps), the flying restart (P1200) function allows the drive to match motor speed to the coasting load before taking control.

P1200 settings:

  • P1200 = 0: Flying restart disabled
  • P1200 = 1: Flying restart enabled — search from max frequency downward
  • P1200 = 2: Flying restart enabled — search from setpoint frequency upward

⚠️ Caution: Flying restart is not suitable for loads where the motor must stop fully before restarting (safety-critical circuits).


9. Siemens-Specific Fault Code Reference

9.1 F0001 — Overcurrent

Root causes:

  • Motor winding short or ground fault
  • Motor cable damage or incorrect wiring
  • Drive output stage (IGBT) failure
  • Motor rated current parameter (P0305) set incorrectly
  • Load too heavy for drive rating
  • Short circuit between motor phases

Diagnostic steps:

  1. Measure motor winding resistance — any value < 1Ω between phases indicates winding fault
  2. Megger test motor cable and motor windings
  3. Swap drive output phases to see if fault code changes (isolates cable vs. drive)
  4. Check P0305 matches motor nameplate current

9.2 F0002 — Overvoltage

Root causes:

  • Deceleration ramp time too short
  • Supply voltage too high
  • Excessive regenerative energy from load

Diagnostic steps:

  1. Measure actual supply voltage at drive terminals
  2. Increase P1121 (ramp-down time) by 50% increments
  3. Check if a braking resistor is installed and functional
  4. Verify P0210 (supply voltage) parameter matches actual

9.3 F0003 — DC Link Overvoltage

Root causes and fixes:

  • Same as F0002 — see above
  • Braking resistor open circuit (check with ohmmeter — should read a few ohms, not open)
  • DC bus capacitor aging (drive operates for years then suddenly fails with repeated F0003)

9.4 F0004 — Drive Overtemperature

Root causes:

  • Heatsink temperature > 100°C (r0037 shows actual value)
  • Fan failure
  • Ambient temperature too high
  • Dust accumulation on heatsink fins
  • Drive load cycle exceeded thermal capacity

Diagnostic steps:

  1. Read r0037 — actual heatsink temperature
  2. Check fan rotation and airflow direction
  3. Clean heatsink with dry compressed air
  4. For cabinet-mounted drives, verify enclosure ventilation fans and ambient temperature
  5. If r0037 approaches 100°C, reduce load or replace with higher-power-rated drive

9.5 F0011 — Motor Overtemperature

Root causes:

  • Motor running above rated current (check with clamp meter)
  • Motor fan (if externally ventilated) malfunctioning
  • Motor thermal model parameters (P0625 through P0628) incorrect
  • Ambient temperature around motor too high

Diagnostic steps:

  1. Compare operating current to P0305 (rated motor current)
  2. If current is at or above rated value, motor is overloaded — reduce load or replace with larger motor
  3. Verify motor fan is operational and airflow is not obstructed
  4. Check motor nameplate thermal class — if motor is rated Class F (155°C) but running at elevated temperature, derating may be needed

9.6 F0070 — Fieldbus Communication Failure

Root causes:

  • Profibus/Profinet cable disconnected or damaged
  • Node address conflict
  • PLC not running or not sending data
  • Incorrect telegram configuration (P0927 wrong)

Diagnostic steps:

  1. Check cable connectors at both drive and PLC ends
  2. Use PLC online diagnostic to confirm cyclic data exchange
  3. Verify node address (PA) in drive (P0918 for Profibus) matches hardware address switch
  4. Check diagnostic LEDs on the drive’s fieldbus interface card
  5. Try replacing the fieldbus cable with a known-good cable

9.7 F0072 — Encoder Signal Loss

Root causes:

  • Encoder cable disconnected or broken
  • Encoder signal level too low (long cable, insufficient shielding)
  • Encoder power supply (5V or 24V) missing
  • Encoder mechanically damaged (no signal on A/B channels)

Diagnostic steps:

  1. Visually inspect encoder cable for damage, crushing, or connector loosening
  2. Use oscilloscope to verify A/B signal presence and amplitude at the drive’s encoder terminals
  3. Measure encoder supply voltage — if 0V, check the drive’s encoder output voltage setting
  4. Swap encoder channel connections (A ↔ A, B ↔ B) to check for cable polarity issues
  5. Replace encoder if signals cannot be detected

9.8 F07220 — Motor Stall Detection

Root causes:

  • Load torque exceeds drive’s available torque at the set speed
  • Motor mechanically blocked
  • Encoder feedback indicates speed is zero while setpoint is applied

Diagnostic steps:

  1. Check if motor shaft can be rotated manually (mechanical binding)
  2. Verify encoder signals are present and clean (use oscilloscope)
  3. Reduce setpoint to see if motor begins turning at low speed
  4. Confirm motor thermal overload parameters (P0610) are not set too conservatively
  5. If load is a pump or fan, check for blockage or closed valves creating excessive back pressure

10. Preventive Maintenance Checklist

Use this checklist monthly or quarterly (adjust interval based on operating environment):

Electrical Testing

  • [ ] Megger test motor windings (record values in maintenance log)
  • [ ] Measure and record operating current under normal load conditions (compare to baseline)
  • [ ] Verify all ground connections are tight (< 10Ω continuity test)
  • [ ] Inspect and retighten all power terminal connections (loose terminals cause overheating and arcing)
  • [ ] Test all safety circuits (emergency stop, safety relay logic, STO function)

Mechanical Inspection

  • [ ] Listen for abnormal bearing noise during motor operation (grinding, screeching)
  • [ ] Check coupling condition — replace elastomer if hardened or cracked
  • [ ] Verify alignment (laser alignment tool) — realign if offset > 0.05mm
  • [ ] Check motor fan screen and cooling fins for dust accumulation
  • [ ] Inspect mounting bolts for tightness

Parameter & Software Checks

  • [ ] Review fault history (r0947) — any new fault codes since last inspection?
  • [ ] Verify key parameters (P0210, P0304, P0305, P0311) haven’t drifted
  • [ ] Confirm control word (STW1) bit configuration is correct in PLC program
  • [ ] Review trending data for motor current — any upward trend indicating developing issue?
  • [ ] Verify PID controller performance is still satisfactory (no hunting or oscillation)

Environmental

  • [ ] Cabinet ambient temperature within drive specification (< 45°C recommended)
  • [ ] Humidity levels within normal range (< 85% RH, non-condensing)
  • [ ] No corrosive atmosphere (no chemical vapors, salt air, dust storm exposure)
  • [ ] Ventilation openings clear and unobstructed

Conclusion & Next Steps

A Siemens inverter motor not starting in closed-loop mode is a multi-causal problem. The most effective diagnostic strategy is systematic elimination — work from simple causes (power, parameters) to complex ones (hardware failure, encoder breakdown). Document every step, keep a maintenance log, and compare today’s readings against the baseline you establish during initial commissioning.

When to escalate to Siemens support:

  • Repeated F0001 overcurrent at startup with no motor/cable fault found (possible IGBT failure)
  • F0072 encoder loss with confirmed good encoder hardware (possible drive encoder interface board failure)
  • Drive trips on multiple faults simultaneously (possible control board or firmware issue)
  • Safety functions (STO, SS1) triggering with no obvious cause (possible safety relay or wiring fault)

For firmware updates, drive configuration backups, or parameter restoration, contact Siemens technical support with your drive’s MLFB serial number (found on the drive nameplate). Keep a backup of all drive parameters on an SD card or in your CMMS system at every major configuration change.


About this guide: This article is intended for industrial automation professionals working with Siemens SINAMICS G120, S120, Micromaster 440, and Micromaster 420 series drives in closed-loop motor control applications. Always refer to the official Siemens technical documentation for your specific drive model before performing any diagnostic or repair procedures.

Leave a Reply

Your email address will not be published. Required fields are marked *