Variable Speed Drive Fault Code Lookup

Use this tool to look up variable speed drive fault codes and get immediate guidance on causes and corrective actions. Select your drive manufacturer, then search by fault code or symptom. Coverage includes ABB, Siemens, Danfoss, Schneider Altivar, Mitsubishi FR-series, Yaskawa, Allen-Bradley PowerFlex, WEG CFW-series, and Invertek Optidrive.

Always isolate the drive before inspecting internal components. If a fault code is not listed or fault recurs after reset, contact a qualified drive engineer before further restart attempts.

86 faults found

ABBF001OvercurrentDo Not Restart
Likely Causes

Motor short circuit, earth fault, motor overload, output cable fault, drive output phase loss.

Immediate Action

Check motor and output cable insulation resistance. Verify motor is not mechanically seized. Check output terminals for earth fault. Reset and test at low speed.

When to Escalate

If fault repeats within minutes or insulation resistance is below 1 MΩ, isolate and call an engineer.

Get engineer support for this fault →
ABBF002DC overvoltageMonitor
Likely Causes

Deceleration ramp too fast for load inertia, supply voltage too high, regenerative load braking without braking chopper.

Immediate Action

Increase deceleration ramp time. Verify supply voltage is within drive rating. Check braking resistor connection if fitted.

When to Escalate

If supply voltage is within spec and fault persists, internal capacitor or IGBT fault suspected — do not reset repeatedly.

Get engineer support for this fault →
ABBF003Earth faultAction Required
Likely Causes

Earth fault on output cable or motor winding. High leakage current through cable screen.

Immediate Action

Measure insulation resistance motor-to-earth with drive disconnected. Check cable screen termination at both ends. Check motor terminal box for moisture.

When to Escalate

Insulation below 1 MΩ — motor requires rewinding or replacement before restart.

Get engineer support for this fault →
ABBF005DC undervoltageMonitor
Likely Causes

Supply voltage too low, supply phase loss, internal DC bus fault, incoming fuse blown.

Immediate Action

Check incoming supply voltage on all three phases. Check incoming fuses or MCB. Verify supply is stable under load.

When to Escalate

If supply is correct and fault persists, internal power supply or rectifier fault — requires engineer.

Get engineer support for this fault →
ABBF007Motor overtemperatureMonitor
Likely Causes

Motor overloaded, ambient temperature too high, motor cooling blocked, motor fan failed.

Immediate Action

Reduce load. Check motor cooling fins and fan. Measure motor current vs nameplate rating. Check ambient temperature in motor enclosure.

When to Escalate

If motor is hot to touch and overloaded, allow to cool fully before restart. Repeated overtemperature shortens winding life significantly.

Get engineer support for this fault →
ABBF009Drive overtemperatureAction Required
Likely Causes

Panel ambient too hot, drive cooling fan blocked or failed, drive vents blocked with dust.

Immediate Action

Check drive cooling fan is running. Clean drive vents. Measure panel ambient temperature — should be below drive rating (typically 40–50°C).

When to Escalate

If cooling fan has failed, replace before restarting. Fan part numbers available from ABB distributor.

Get engineer support for this fault →
ABBF010Input phase lossDo Not Restart
Likely Causes

Incoming supply phase missing, loose terminal on input contactor or fuse, blown input fuse.

Immediate Action

Measure voltage on all three input phases at drive terminals L1, L2, L3. Check incoming fuses and contactor terminals.

When to Escalate

Do not run single-phase — drive will sustain internal damage. Isolate until supply is restored.

Get engineer support for this fault →
ABBF011Output phase lossAction Required
Likely Causes

Open circuit on one output phase: broken cable, loose terminal, tripped output contactor, motor winding open.

Immediate Action

Check output cable connections at drive terminals U, V, W and at motor terminal box. Measure motor winding resistance across each phase pair.

When to Escalate

Winding imbalance >5% — motor fault, requires replacement or rewind.

Get engineer support for this fault →
ABBF014Identification run failedMonitor
Likely Causes

Motor data incorrectly entered, motor cable too long, motor not connected.

Immediate Action

Re-check all motor nameplate parameters entered into drive: kW, voltage, current, frequency, speed. Ensure motor is connected and not mechanically loaded during ID run.

When to Escalate

Repeat after correcting parameters. If fault persists with correct data, check for output wiring fault.

Get engineer support for this fault →
ABBF023Brake resistor overtemperatureAction Required
Likely Causes

Braking resistor overloaded — duty cycle too high, resistor undersized for application.

Immediate Action

Increase deceleration ramp time to reduce braking load. Verify resistor size matches drive specification.

When to Escalate

If brake resistor is physically damaged or discoloured, replace before resuming operation.

Get engineer support for this fault →
SiemensF00001Overcurrent / short circuitMonitor
Likely Causes

Output short circuit, earth fault, motor cable fault, motor winding fault.

Immediate Action

Disconnect motor cable at drive output terminals. Measure insulation motor-to-earth and phase-to-phase. Check cable route for physical damage.

When to Escalate

If drive IGBT is suspected (no external fault found), requires specialist workshop testing.

Get engineer support for this fault →
SiemensF00002DC link overvoltageAction Required
Likely Causes

Regen load, deceleration too fast, supply voltage high.

Immediate Action

Extend deceleration ramp time. Check supply voltage. Verify braking chopper/resistor if fitted.

When to Escalate

Repeated DC bus faults without clear cause — internal capacitor degradation possible, contact engineer.

Get engineer support for this fault →
SiemensF00003DC link undervoltageDo Not Restart
Likely Causes

Low supply voltage, phase loss, internal pre-charge fault.

Immediate Action

Check all three supply phases and incoming fuses.

When to Escalate

Phase loss confirmed — do not restart until supply rectified.

Get engineer support for this fault →
SiemensF00011Drive overtemperatureAction Required
Likely Causes

Cooling fan fault, blocked vents, high ambient.

Immediate Action

Check internal cooling fan. Clean vents. Reduce ambient if possible.

When to Escalate

Fan replacement required if failed — operate with fan failed risks permanent IGBT damage.

Get engineer support for this fault →
SiemensF00012Motor overtemperature (PTC/KTY)Monitor
Likely Causes

Motor temperature sensor tripped. Motor overloaded or cooling restricted.

Immediate Action

Allow motor to cool. Verify PTC/KTY sensor wiring to drive terminals. Check motor load.

When to Escalate

If sensor circuit is open/short, verify sensor continuity before assuming motor fault.

Get engineer support for this fault →
SiemensF00022I²t motor overloadMonitor
Likely Causes

Persistent overload — motor running above rated current for extended period.

Immediate Action

Check driven load for mechanical obstruction or overload. Verify motor current against nameplate rating.

When to Escalate

If motor has been in sustained overload, inspect motor and bearings before restart.

Get engineer support for this fault →
SiemensF00070EEPROM faultMonitor
Likely Causes

Parameter memory corruption, drive firmware issue.

Immediate Action

Restore factory parameters and re-commission. Back up parameters before reset if possible.

When to Escalate

Repeated EEPROM faults may indicate control board failure — contact Siemens service.

Get engineer support for this fault →
SiemensF00085Power board faultMonitor
Likely Causes

Internal power supply fault, gate driver fault.

Immediate Action

Cycle power (wait 5 minutes after isolating). Check for external causes (voltage spikes, earthing).

When to Escalate

If fault persists after clean power cycle, internal hardware fault — do not continue operating.

Get engineer support for this fault →
DanfossTRIP 110 Volts lowAction Required
Likely Causes

Internal 10V supply fault or short circuit on external circuit connected to drive 10V terminal.

Immediate Action

Disconnect any external equipment from the drive 10V terminal. Check for wiring faults on analogue inputs.

When to Escalate

If fault clears with external wiring disconnected, trace and repair short circuit in control wiring.

Get engineer support for this fault →
DanfossTRIP 2Live zero faultMonitor
Likely Causes

Analogue input reference signal lost — e.g. 4–20 mA signal dropped to below 2 mA.

Immediate Action

Check reference signal cable from PLC, sensor, or potentiometer. Verify signal source is powered and outputting correct range.

When to Escalate

If signal source is healthy and fault persists, analogue input card fault possible.

Get engineer support for this fault →
DanfossTRIP 4Mains phase lossMonitor
Likely Causes

One or more input phases missing at drive terminals.

Immediate Action

Check all three incoming phases. Check upstream fuses and contactors.

When to Escalate

Do not run on phase loss — proceed only after supply confirmed healthy on all three phases.

Get engineer support for this fault →
DanfossTRIP 5DC link overvoltageMonitor
Likely Causes

Regen braking, fast deceleration, high supply voltage.

Immediate Action

Extend deceleration ramp time. Confirm supply voltage within spec.

When to Escalate

If braking resistor fitted, check connection and continuity of resistor.

Get engineer support for this fault →
DanfossTRIP 6DC link undervoltageAction Required
Likely Causes

Low supply voltage, phase loss, internal DC bus fault.

Immediate Action

Check incoming supply. Verify all fuses.

When to Escalate

Persistent DC undervoltage on healthy supply — internal fault, contact engineer.

Get engineer support for this fault →
DanfossTRIP 7DC link overvoltage (alt)Monitor
Likely Causes

As TRIP 5 — DC bus voltage exceeded during operation.

Immediate Action

As TRIP 5.

When to Escalate

As TRIP 5.

Get engineer support for this fault →
DanfossTRIP 8DC link undervoltage (alt)Monitor
Likely Causes

As TRIP 6.

Immediate Action

As TRIP 6.

When to Escalate

As TRIP 6.

Get engineer support for this fault →
DanfossTRIP 9Inverter overloadedAction Required
Likely Causes

Drive has been overloaded beyond rated current continuously.

Immediate Action

Check motor load for mechanical issues. Verify drive is correctly sized for motor.

When to Escalate

If drive is undersized, replacement with correctly rated unit required.

Get engineer support for this fault →
DanfossTRIP 11Motor thermistor tripMonitor
Likely Causes

Motor PTC thermistor tripped — motor overtemperature.

Immediate Action

Allow motor to cool. Check motor load and ambient temperature.

When to Escalate

Confirm thermistor circuit is intact before restart.

Get engineer support for this fault →
DanfossTRIP 13OvercurrentMonitor
Likely Causes

Output short circuit, earth fault, rapid acceleration, load spike.

Immediate Action

Disconnect output and check insulation resistance. Increase acceleration ramp time.

When to Escalate

Repeated overcurrent trips with no external fault — IGBT fault possible.

Get engineer support for this fault →
DanfossTRIP 14Earth faultAction Required
Likely Causes

Earth fault detected on output. Motor or cable insulation breakdown.

Immediate Action

Measure insulation motor and cable to earth with drive isolated.

When to Escalate

Insulation below 1 MΩ — motor or cable must be repaired before restart.

Get engineer support for this fault →
DanfossTRIP 29Heat sink overtemperatureAction Required
Likely Causes

Drive cooling fan blocked or failed, ambient too high.

Immediate Action

Check cooling fan. Clean heat sink fins. Reduce ambient temperature.

When to Escalate

Fan replacement required if failed.

Get engineer support for this fault →
DanfossTRIP 34Fieldbus communication faultMonitor
Likely Causes

Loss of communication from PLC or BMS. Fieldbus cable fault.

Immediate Action

Check Profibus/Modbus/DeviceNet cable. Check PLC programme and communications settings.

When to Escalate

If cable and PLC are healthy, drive fieldbus card may have failed.

Get engineer support for this fault →
SchneiderOCFOvercurrent faultMonitor
Likely Causes

Output short circuit, earth fault, inertia too high for ramp setting, motor cable too long.

Immediate Action

Check output cable and motor insulation. Increase acceleration ramp time. Check motor sizing.

When to Escalate

If no external fault found after insulation check, suspect IGBT fault.

Get engineer support for this fault →
SchneiderOHFDrive overheatingMonitor
Likely Causes

Cooling fan failed, blocked vents, high ambient.

Immediate Action

Check internal cooling fan. Clean air vents.

When to Escalate

Fan part numbers from Schneider distributor. Do not operate with failed fan.

Get engineer support for this fault →
SchneiderOLFMotor overload faultMonitor
Likely Causes

Motor current exceeded rated value persistently. Mechanical overload or incorrect motor parameters.

Immediate Action

Check motor rated current entered in drive parameters. Check driven load for obstruction.

When to Escalate

If motor current is correct and fault persists, motor may have winding damage — check winding resistance.

Get engineer support for this fault →
SchneiderPHFInput phase lossDo Not Restart
Likely Causes

Supply phase missing at drive input.

Immediate Action

Check all three input phases and fuses.

When to Escalate

Do not restart on single-phase supply.

Get engineer support for this fault →
SchneiderUSFSupply undervoltageMonitor
Likely Causes

Low supply voltage, phase loss.

Immediate Action

Measure all three input phase voltages at drive terminals.

When to Escalate

Persistent on healthy supply — internal fault.

Get engineer support for this fault →
SchneiderOSFSupply overvoltageMonitor
Likely Causes

Supply voltage too high. Check supply with meter.

Immediate Action

Measure incoming supply. If above drive rated voltage, investigate supply issue.

When to Escalate

Do not operate if supply consistently above upper limit.

Get engineer support for this fault →
SchneiderSCF1Motor short circuit (phase 1)Action Required
Likely Causes

Short circuit between U output and earth or between phases.

Immediate Action

Disconnect motor cable. Measure insulation phase-to-earth and phase-to-phase.

When to Escalate

Confirmed short — motor or cable replacement required.

Get engineer support for this fault →
SchneiderSCF3Motor earth faultDo Not Restart
Likely Causes

Earth fault on motor winding or output cable.

Immediate Action

Measure insulation motor and cable to earth.

When to Escalate

Below 1 MΩ — isolate and repair before restart.

Get engineer support for this fault →
SchneiderCFFIncorrect configurationAction Required
Likely Causes

Parameter configuration incorrect or incompatible settings combination.

Immediate Action

Review parameter settings. Factory reset and re-commission if required.

When to Escalate

Contact engineer if unsure which parameters are causing conflict.

Get engineer support for this fault →
SchneiderEEFEEPROM faultAction Required
Likely Causes

Memory corruption. Possible after power interruption during parameter save.

Immediate Action

Factory reset and re-enter all parameters.

When to Escalate

Repeated EEPROM faults — control card replacement may be required.

Get engineer support for this fault →
MitsubishiE.OC1Overcurrent during accelerationMonitor
Likely Causes

Acceleration time too short, load inertia too high, motor fault.

Immediate Action

Increase acceleration time (Pr.7). Check motor for mechanical seizure.

When to Escalate

If fault persists with longer ramp, check motor winding and cable insulation.

Get engineer support for this fault →
MitsubishiE.OC2Overcurrent during constant speedDo Not Restart
Likely Causes

Sudden load spike, output short, earth fault.

Immediate Action

Measure output cable and motor insulation. Check process for load spikes.

When to Escalate

IGBT damage possible if overcurrent was severe — do not restart without insulation check.

Get engineer support for this fault →
MitsubishiE.OC3Overcurrent during decelerationMonitor
Likely Causes

Deceleration too fast, regenerative load.

Immediate Action

Increase deceleration time (Pr.8). Consider braking resistor if load has high inertia.

When to Escalate

Repeated OC3 without change — braking resistor selection and connection check required.

Get engineer support for this fault →
MitsubishiE.OV1Overvoltage during accelerationMonitor
Likely Causes

Supply voltage high, regen from load during acceleration.

Immediate Action

Check supply voltage. Reduce acceleration rate.

When to Escalate

Consistent OV1 — check supply quality and consider line reactor.

Get engineer support for this fault →
MitsubishiE.OV2Overvoltage during constant speedMonitor
Likely Causes

Supply voltage spike, regen load.

Immediate Action

Check supply quality with power analyser.

When to Escalate

If supply is clean, braking resistor may be required.

Get engineer support for this fault →
MitsubishiE.OV3Overvoltage during decelerationAction Required
Likely Causes

Deceleration too fast for load inertia, no braking resistor.

Immediate Action

Increase deceleration time. Verify braking resistor connection and resistance value.

When to Escalate

If braking resistor has failed open, replace before restart.

Get engineer support for this fault →
MitsubishiE.THTDrive overtemperatureAction Required
Likely Causes

Cooling fan fault, blocked vents, ambient too high.

Immediate Action

Check cooling fan. Clean heat sink. Reduce panel ambient.

When to Escalate

Fan failure — replace fan before resuming operation.

Get engineer support for this fault →
MitsubishiE.THMMotor overtemperature (electronic)Monitor
Likely Causes

Motor running above rated current, motor thermal model tripped.

Immediate Action

Check motor load. Verify motor rated current (Pr.9) set correctly.

When to Escalate

If motor is physically hot, allow full cooldown before restart.

Get engineer support for this fault →
MitsubishiE.FINHeat sink overtemperature (thermistor)Action Required
Likely Causes

Drive heatsink exceeded temperature limit.

Immediate Action

As E.THT — check cooling fan and ambient.

When to Escalate

Fan replacement required.

Get engineer support for this fault →
MitsubishiE.GFEarth fault (output)Action Required
Likely Causes

Earth fault on output cable or motor winding.

Immediate Action

Measure insulation resistance all output phases to earth.

When to Escalate

Below 1 MΩ — motor or cable repair required before restart.

Get engineer support for this fault →
MitsubishiE.ILFInput phase lossDo Not Restart
Likely Causes

One input phase missing.

Immediate Action

Check all three input phases, fuses, and upstream contactor.

When to Escalate

Do not restart on single-phase supply.

Get engineer support for this fault →
YaskawaoCOvercurrentMonitor
Likely Causes

Output short circuit, ground fault, acceleration too fast, motor cable fault.

Immediate Action

Check output insulation. Increase accel time (C1-01). Check motor and cable.

When to Escalate

Repeated oC with no external fault — IGBT suspect.

Get engineer support for this fault →
YaskawaovDC bus overvoltageMonitor
Likely Causes

Decel too fast, supply overvoltage, regenerative load.

Immediate Action

Increase decel time (C1-02). Check supply voltage. Verify braking resistor.

When to Escalate

Braking resistor selection review required if regen load is frequent.

Get engineer support for this fault →
Yaskawauv1DC bus undervoltageMonitor
Likely Causes

Low supply voltage, phase loss, momentary supply interruption.

Immediate Action

Check three-phase supply and incoming fuses.

When to Escalate

Persistent uv1 on good supply — internal fault.

Get engineer support for this fault →
Yaskawauv2Control power supply faultAction Required
Likely Causes

Internal control power supply fault.

Immediate Action

Cycle power. Check for external causes (earthing issues, voltage spikes).

When to Escalate

Persistent fault — control board failure, contact engineer.

Get engineer support for this fault →
YaskawaoH1Drive overtemperature (heatsink)Action Required
Likely Causes

Cooling fan failed, blocked vents, ambient too high.

Immediate Action

Check cooling fan. Clean vents. Reduce ambient.

When to Escalate

Fan replacement required if failed.

Get engineer support for this fault →
YaskawaoL1Motor overloadMonitor
Likely Causes

Motor current exceeded motor overload protection threshold.

Immediate Action

Verify E2-01 (motor rated current) is set correctly. Check driven load for mechanical issue.

When to Escalate

If motor is running hot and overloaded, investigate load and motor sizing.

Get engineer support for this fault →
YaskawaoL2Drive overloadMonitor
Likely Causes

Drive current exceeded 110% for one minute (ND) or 150% instantaneous.

Immediate Action

Check actual output current vs drive rating. Check for load spikes.

When to Escalate

Drive may be undersized for application — review with engineer.

Get engineer support for this fault →
YaskawaGFGround faultDo Not Restart
Likely Causes

Ground fault on output phases. Motor or cable insulation breakdown.

Immediate Action

Measure insulation resistance motor and cable to earth.

When to Escalate

Insulation below 1 MΩ — do not restart.

Get engineer support for this fault →
YaskawaCPF00Control circuit faultAction Required
Likely Causes

Internal control circuit hardware fault.

Immediate Action

Cycle power. Check earthing quality.

When to Escalate

Persistent CPF fault — control board failure, contact engineer.

Get engineer support for this fault →
Allen-BradleyF2Auxiliary input faultMonitor
Likely Causes

External fault input active — interlock opened.

Immediate Action

Check external fault input wiring (TB3 terminals). Identify which interlock is open (E-stop, thermal switch, door switch).

When to Escalate

Do not bypass interlocks without identifying cause.

Get engineer support for this fault →
Allen-BradleyF3Power loss faultDo Not Restart
Likely Causes

DC bus voltage dropped below minimum — supply phase loss, supply interruption.

Immediate Action

Check all three incoming phases and fuses.

When to Escalate

Do not restart until supply confirmed healthy.

Get engineer support for this fault →
Allen-BradleyF4Undervoltage faultMonitor
Likely Causes

DC bus below minimum threshold.

Immediate Action

Check incoming supply voltage.

When to Escalate

If supply is in spec, internal capacitor or rectifier fault possible.

Get engineer support for this fault →
Allen-BradleyF5Overvoltage faultMonitor
Likely Causes

DC bus above maximum — decel too fast, regen load, high supply voltage.

Immediate Action

Increase decel time. Check supply voltage. Verify braking resistor.

When to Escalate

Review braking resistor sizing if application is regen-heavy.

Get engineer support for this fault →
Allen-BradleyF6Motor stall faultMonitor
Likely Causes

Motor stalled or speed not reached within timeout period.

Immediate Action

Check driven load for mechanical seizure or excessive load. Verify motor is not running against closed valve/damper.

When to Escalate

Mechanical investigation required if load is seized.

Get engineer support for this fault →
Allen-BradleyF7Motor overloadMonitor
Likely Causes

Motor I²t overload tripped.

Immediate Action

Check motor rated FLA entered in drive parameters. Verify driven load.

When to Escalate

Investigate load and motor sizing if fault repeats.

Get engineer support for this fault →
Allen-BradleyF8Heatsink overtemperatureAction Required
Likely Causes

Drive overheating — cooling fan fault, blocked vents, high ambient.

Immediate Action

Check cooling fan. Clean heatsink vents.

When to Escalate

Replace fan if failed.

Get engineer support for this fault →
Allen-BradleyF12HW overcurrentDo Not Restart
Likely Causes

Hardware overcurrent detected — typically output short or earth fault.

Immediate Action

Disconnect motor. Measure insulation resistance. Check output cable.

When to Escalate

If IGBT damage suspected (no external cause), do not restart — contact engineer.

Get engineer support for this fault →
Allen-BradleyF13Ground faultAction Required
Likely Causes

Ground fault on output or motor.

Immediate Action

Measure insulation resistance motor and cable to earth.

When to Escalate

Below 1 MΩ — repair required before restart.

Get engineer support for this fault →
Allen-BradleyF29Analog input lossMonitor
Likely Causes

4–20 mA reference signal lost (dropped below 2 mA).

Immediate Action

Check reference signal source. Check cable from PLC or sensor.

When to Escalate

If source is healthy, check drive analogue input setting and wiring.

Get engineer support for this fault →
WEGF001Overcurrent (instantaneous)Monitor
Likely Causes

Output short circuit, earth fault, aggressive acceleration.

Immediate Action

Check output cable and motor insulation. Increase acceleration ramp.

When to Escalate

Persistent fault with no external cause — IGBT inspection required.

Get engineer support for this fault →
WEGF002Drive overtemperatureAction Required
Likely Causes

Cooling fan blocked or failed. High ambient.

Immediate Action

Check cooling fan. Clean vents.

When to Escalate

Fan replacement required if failed.

Get engineer support for this fault →
WEGF003DC bus overvoltageAction Required
Likely Causes

Decel too fast, regen load, high supply.

Immediate Action

Increase decel ramp. Check supply voltage. Check braking resistor.

When to Escalate

If braking resistor is open circuit, replace before restart.

Get engineer support for this fault →
WEGF004DC bus undervoltageMonitor
Likely Causes

Low supply voltage, phase loss.

Immediate Action

Check all three input phases and fuses.

When to Escalate

Persistent on good supply — internal fault.

Get engineer support for this fault →
WEGF005Motor overload (I²t)Monitor
Likely Causes

Motor running above rated current. Mechanical overload.

Immediate Action

Verify motor rated current in P0401. Check driven load.

When to Escalate

Repeated trips under normal load — investigate motor and load sizing.

Get engineer support for this fault →
WEGF011Input phase lossDo Not Restart
Likely Causes

One phase missing at drive input.

Immediate Action

Check three-phase supply and upstream protection.

When to Escalate

Do not restart until all three phases confirmed.

Get engineer support for this fault →
WEGF033Ground faultDo Not Restart
Likely Causes

Earth fault on output cable or motor.

Immediate Action

Measure insulation resistance to earth.

When to Escalate

Below 1 MΩ — do not restart.

Get engineer support for this fault →
InvertekE-01DC bus overvoltageMonitor
Likely Causes

Supply overvoltage, deceleration too fast, regenerative load.

Immediate Action

Check supply voltage. Increase deceleration ramp time (P1-04).

When to Escalate

Braking resistor required if load is regenerative.

Get engineer support for this fault →
InvertekE-02DC bus undervoltageMonitor
Likely Causes

Low supply voltage, phase loss.

Immediate Action

Check all supply phases and fuses.

When to Escalate

Persistent on healthy supply — internal fault.

Get engineer support for this fault →
InvertekE-03Drive overtemperatureAction Required
Likely Causes

Cooling fan blocked or failed, high ambient.

Immediate Action

Check cooling fan. Clean heatsink vents.

When to Escalate

Fan replacement required.

Get engineer support for this fault →
InvertekE-05Overcurrent / short circuitMonitor
Likely Causes

Output short circuit, earth fault, aggressive acceleration.

Immediate Action

Check motor and cable insulation. Increase acceleration ramp (P1-03).

When to Escalate

No external fault found — internal IGBT suspect.

Get engineer support for this fault →
InvertekE-07Motor overloadMonitor
Likely Causes

Motor current exceeds overload threshold. Mechanical overload.

Immediate Action

Verify motor rated current in P1-08. Check load.

When to Escalate

Motor or drive undersized — review specification.

Get engineer support for this fault →
InvertekE-09External fault / interlockMonitor
Likely Causes

External fault input has been activated.

Immediate Action

Check wiring on digital input configured as external fault. Identify which device triggered it.

When to Escalate

Do not bypass — identify cause of interlock trip.

Get engineer support for this fault →
InvertekE-10Loss of load / undercurrentAction Required
Likely Causes

Motor has lost its load (e.g. broken belt, pump cavitation, coupling failed).

Immediate Action

Check mechanical connection between motor and load. Check for pump cavitation.

When to Escalate

If belt or coupling is broken, mechanical repair required before restart.

Get engineer support for this fault →
InvertekE-14Control signal loss (4–20 mA)Monitor
Likely Causes

Analogue reference signal below 2 mA — cable fault or source failure.

Immediate Action

Check signal source and cable. Confirm PLC output is active.

When to Escalate

If source is healthy, check drive analogue input wiring.

Get engineer support for this fault →

Common VSD Faults Without a Fault Code

Not all drive problems raise a fault code. These operational symptoms frequently require engineer attendance:

SymptomLikely CauseFirst Check
Drive powers up but won't runNo run command, interlock open, control signal missingCheck digital input status on drive display. Confirm 24V run signal present.
Motor runs but at wrong speedReference signal fault, parameter incorrect, PID setpoint issueCheck analogue input value on drive display. Confirm 4–20 mA signal from sensor/PLC.
Motor runs in wrong directionOutput phases U/V/W swapped, motor wiring reversedSwap any two output phases (U↔V) at drive output terminals — do not swap at motor.
Drive trips intermittently under loadThermal overload, loose connection, supply quality issueMonitor drive output current display under load. Check all power terminal torques.
Drive display blank, no powerIncoming fuse or MCB blown, control supply fuse failed, SMPS faultCheck incoming fuses. Measure voltage at drive input terminals L1/L2/L3.
Motor vibrates or makes noise at certain speedsSkip frequency not set, resonance in mechanical systemProgramme skip frequency bands in drive parameters to avoid resonant speeds.
PLC loses comms with driveFieldbus cable fault, address mismatch, termination resistor missingCheck Profibus/Modbus cable. Verify drive node address matches PLC configuration. Check termination.

Need an Engineer On-Site?

Ashmit Engineering Ltd provides VSD fault diagnosis, repair, and recommissioning across UK industrial and marine sites. We work with all major drive manufacturers.