Home > Blog > Mitsubishi servo motor repair and maintenance > Siemens SINAMICS V90 Servo Drive Alarm & Fault Codes, Step-by-Step Repair & Maintenance Guide

Siemens SINAMICS V90 Servo Drive Alarm & Fault Codes, Step-by-Step Repair & Maintenance Guide

By Jennifer Zhang November 7th, 2026 2 views

By Jennifer Zhang

The SINAMICS V90 is Siemens’ entry-level servo drive for motion control tasks from 50 W up to 7 kW, in V90 PTI (pulse train) and V90 PN (PROFINET) versions. Because it shares diagnostic architecture with the larger SINAMICS family, its display codes follow a strict pattern any technician can learn in one afternoon. This guide covers the codes that actually stop production on V90 drives — verified against Siemens’ official fault and alarm documentation — with the checks and repairs we use on the bench every day. Need replacement hardware? Our Siemens servo drive spare parts collection is a good starting point.

Siemens servo motors from our tested stock

First: Fault (F) vs Alarm (A) on the V90

Codes that start with F are faults: the drive trips, pulses are disabled, and the code must be acknowledged before the drive can run again. Codes that start with A are alarms: they inform but do not trip the drive, and they clear themselves once the cause disappears. The active fault number sits in parameter r0945 with its fault value in r0949; the alarm history sits in r2122 and r2124. On the drive itself, the BOP display shows the live code, and the V-ASSISTANT commissioning software shows the same information on the “Alarms” tab with plain-language explanations.

Repair steps (universal): photograph the code, reset via the BOP or digital input, and re-power if the fault latches. If a fault returns immediately on enable, do not keep resetting — find the root cause below.

Power-Stage Faults (F30001–F30050)

Fault manifestations: the drive trips at power-up, at enable, or during deceleration. Typical codes: F30001 (power unit overcurrent), F30002 (DC bus overvoltage), F30003 (DC bus undervoltage), F30004 (heatsink overtemperature), F30005 (power unit overload I2t), F30011 (phase failure in the main circuit), F30015 (power cable phase failure), F30021 (ground fault), F30027 (DC bus pre-charging time monitoring), F30036 (power unit internal space overtemperature), F30050 (24 V supply overvoltage).

Root causes: shorted motor cable or motor winding and damaged output IGBTs drive F30001 and F30021; too-short deceleration ramps or a missing/incorrect braking resistor drive F30002; a weak supply, blown line fuse, or loose input terminal drives F30003 and F30011; blocked cooling, high ambient temperature, and dust-clogged fins drive F30004 and F30036; sustained mechanical overload drives F30005; excessive load on the 24 V control supply drives F30050.

Repair steps: disconnect the motor cable and re-test — if F30001/F30021 persists with the motor disconnected, the power stage itself is damaged and the unit needs repair or replacement. Measure line-to-line resistance of the motor and cable. Verify the braking resistor value and wiring for F30002. Check all three line phases and input terminals for F30003/F30011. Clean the heatsink, verify the fan, and confirm ambient temperature for F30004/F30036. Give the V90 its own 24 V DC supply sized with headroom — Siemens explicitly warns against sharing it with inductive loads such as relays and solenoids.

Siemens PLC control box components inspected in our workshop

Motor, Motion and Positioning Faults (F7xxx)

Fault manifestations: the drive trips on enable or during motion with F7900 (motor blocked / stalled at maximum torque), F7901 (motor overspeed), F7450–F7453 (static monitoring, positioning monitoring, following error, position actual-value processing), F7403/F7404 (DC bus lower/upper limit), F7011 (motor overtemperature), F7412 (commutation angle error), F7491/F7492 (negative/positive stop cam reached), F7481/F7482 (soft limits exceeded), F7995 (motor identification failed), F7815 (power unit changed).

Root causes: a mechanically jammed axis, undersized motor, torque limits set too low, a brake that never releases, or a failing encoder cable cause F7900 and the F7450-family. Position loop gains that are too high or too low, acceleration set too aggressively, and P2546 tolerance set too small also trigger F7452. F7995 appears when pole-position identification for an incremental-encoder motor runs while the shaft is moving or under external force. F7491/F7492 and F7481/F7482 are limit switches and software limits doing their job.

Repair steps: jog the axis by hand (power off) to confirm it moves freely; check the brake, coupling, and load. Verify torque limits, encoder and power cable connections, and position loop gain. On bench tests without wired limit switches, set P29300 = 6 to force the CWL/CCWL limit signals high; on real machines, clear F7491/F7492 by backing the axis off the cam. For F7995, ensure the shaft is stationary at enable and repeat identification. For F7815, confirm the power unit matches the drive configuration.

Encoder Faults (F31100–F31130)

Fault manifestations: F31100 (zero-mark distance error), F31101 (zero-mark fault), F31110 (serial communication fault with the encoder), F31112 (fault bit in the serial data record), F31117 (A/B/R signal inversion error), F31130 (coarse-sync zero-mark and position error). These often appear intermittently and randomly — a classic EMC signature.

Root causes: encoder cable shielding not bonded at both ends, power and signal cables in the same trunk, loose X2 encoder connector, or a failing encoder. On 200 V V90 drives Siemens has documented random F31100/F31117/F7452/F7453 alarms caused purely by poor grounding.

Repair steps: re-route encoder cable away from motor power cable, verify shield grounding at the drive and motor, re-seat the encoder connector (fastening torque at the drive is 0.4 N·m — do not overtighten), and replace the encoder cable or encoder if the fault persists. Where drives feed larger SINAMICS architectures, a failing upstream feed such as a SINAMICS Smart Line Module 6SL3130-6AE21-0AB1 can mimic supply-side symptoms, so isolate the drive before condemning the encoder.

Siemens servo motor checked before shipment

Communication and Software Faults

Fault manifestations: F1030 (communication fault with the higher-level controller), F8501 (PROFINET: setpoint reception interrupted — connection dropped, controller in STOP, or V90 PN device name/IP does not match the project), A1932 (DSC: Drive Bus clock cycles missing — the PLC telegram does not match the drive’s default telegram 105), plus internal software codes F1000–F1003, F1015, F1018 and F1611.

Root causes: for PROFINET codes, wiring, switch configuration, or a telegram mismatch. For F1xxx codes, firmware exceptions or corrupted parameter sets.

Repair steps: check cable and connectors, confirm the controller is RUN, and make sure the device name and IP address in TIA Portal match the drive. Use the same telegram number in the PLC and the drive. For internal software faults, save the parameter set, update the firmware to the current release, and perform a factory reset followed by re-commissioning if the code persists. Machines integrating V90 with higher-end control hardware — for example a SINAMICS CU320-2 PN control unit 6SL3040-1MA00-0AA0 — should be diagnosed from the top down: confirm the controller is healthy before blaming the V90 axis.

Alarms That Warn Before They Trip (A-codes)

A1009 (control unit overtemperature), A5000 (heatsink overtemperature), A7012 (motor thermal model), and A7805 (power unit I2t overload) are thermal early warnings — act before they become F-codes. A1032 means parameters changed and must be saved; A7971/A7991 indicate commutation-offset measurement or motor data detection in progress; A7441 saves the absolute-encoder position offset; A7478–A7480 flag EPOS soft-limit approaches; A7576 means encoder-less running after a fault; A31411/A31412 warn of absolute-encoder data issues; A52901 signals a braking resistor at its alarm threshold. None trip the drive, but each is free diagnostic information — log them.

Preventive Maintenance for V90 Drives

  1. Give each V90 a dedicated 24 V DC supply with headroom; never share it with relays or solenoids.
  2. Ground the motor power cable earth and both ends of the encoder cable shield; separate power and signal routing.
  3. Re-torque encoder and power connectors annually (0.4 N·m at the encoder connector).
  4. Save parameters after every change (clears A1032) and keep a V-ASSISTANT backup.
  5. Keep the heatsink and fan clean; verify braking resistor value and wiring yearly.
  6. Use V-ASSISTANT Trace to trend speed, current and DC bus voltage — drift often precedes F30002/F30005 trips by months.

When a power stage or control board is beyond repair, replacement is usually faster. Our stock includes SINAMICS-family hardware such as the SINAMICS S120 Double Motor Module 6SL3120-1TE21-0AA3 and the control unit listed above, all tested before shipment.

FAQ

Q1: How do I reset a V90 fault? Acknowledge it via the BOP, the V-ASSISTANT “clear all” button, or the reset digital input. Alarms clear themselves; faults require the cause to be gone first.

Q2: The drive shows F07995 on every enable. Is it broken? Usually not. Pole-position identification fails when the shaft is moving or loaded at enable. Keep the shaft still, check the brake and load, and retry.

Q3: F31100 appears randomly every few days. What should I check first? Grounding and EMC: encoder shield bonding, cable separation, and the 0.4 N·m connector torque. Siemens documents this exact random pattern on 200 V drives.

Q4: Why does my V90 PN show A1932 after I changed the PLC project? The default V90 PN telegram is 105. If the PLC uses a different telegram, clock sync mismatches and A1932 appears. Align telegrams on both sides and it clears automatically.

Q5: Can I run the V90 without limit switches during commissioning? Yes — set P29300 = 6 to force the CWL/CCWL signals high, bench tests only; restore hardware limits on the machine.

Q6: Where can I get a tested replacement for a failed V90 or SINAMICS component? Test Well Electronics supplies tested Siemens servo drives, control units and Siemens PLC modules with warranty — send us the MLFB number for a quote.

Mitsubishi FX5U / FX3U PLC Error & Diagnostic Codes, Step-by-Step Troubleshooting Guide
Previous
Mitsubishi FX5U / FX3U PLC Error & Diagnostic Codes, Step-by-Step Troubleshooting Guide
Read More
PROFINET Communication Failure: Step-by-Step Diagnosis & Fix Guide
Next
PROFINET Communication Failure: Step-by-Step Diagnosis & Fix Guide
Read More