Inovance Drive Fault Codes (MD290, MD200, MD500)

How faults show

When a fault occurs the drive stops output at once, the fault relay contact acts, and the operating panel shows the fault code, for example Err07. On the MD290, MD310 and MD500 panels the TUNE/TC indicator flashes fast to signal a fault (four times a second on the MD500); slow flashing means auto-tuning.

The MD310 can also show alarms such as A08, during which the drive keeps running, and it shows an undervoltage in the stop state as A09.

The last three faults are stored as numbers in F9-14 (1st), F9-15 (2nd) and F9-16 (3rd, the latest), where 2 means Err02; the parameters after them record the frequency, current, bus voltage, DI and DO state, power-on time and running time at each fault. The MD290 also shows the active fault number in U0-62.

The MD290 User Guide B06 prints codes in its fault list as E002.0, E003.0 and so on, while its other chapters, like the MD200, MD310 and MD500 manuals, use Err02 style.

To reset: find and remove the cause, then press STOP/RES (works in any control mode when F7-02 = 1, the default), or activate a DI set to function 9 (fault reset), or write 7 (fault reset) to communication address 2000H when F0-02 = 2, or switch the power off, wait until the display goes out, and switch it on again. Err09 resets by itself when the bus voltage recovers.

Err23 cannot be reset automatically or manually, only by switching power off and on (MD290, MD500). F9-09 sets how many automatic resets are allowed, and F9-47 to F9-50 let you choose coast to stop, stop by stop mode, or keep running for some faults (for example Err11, Err12, Err13, Err15, Err16).

The panel can also show HC at power-on: Inovance lists it as a symptom, not a fault code (see the FAQ).

Safety first.

Inovance: equipment installation, wiring, maintenance, inspection or parts replacement must be performed only by professionals, and troubleshooting and repair only by professionals following the repair instructions, with repair records kept. Do not repair or retrofit the drive yourself; for faults you cannot clear, contact the agent or Inovance.

Never work on the drive or remove its cover with power on.

Before wiring, maintenance or inspection, cut off all power supplies and wait at least the time on the drive warning label, because residual voltage stays after power-off: the MD200 label says do not touch terminals or remove the cover within 10 minutes after power-off, the MD310 and MD500 guides say wait at least 10 minutes (MD310: until the CHARGE indicator is off), and the MD290 guide says wait at least 10 minutes until the bus voltage is below 36 V and the power indicator is off (T1 to T12 models).

Then measure the main circuit DC voltage to confirm it is in the safe range. With a permanent magnet motor, do not touch the motor terminals right after power-off: a rotating motor generates voltage even with the drive off. Do not run the motor until a short circuit to ground (Err23) has been fixed.

Sources: MD290 User Guide B06 safety instructions and 5.6.2 (PDF pages 26, 27, 146, 384). MD200 User Guide C06 safety precautions and labels (PDF pages 20, 22, 23). MD310 User Guide A00 (PDF pages 11, 29). MD500 User Guide 19010374 A06 (PDF pages 8, 13). Follow lockout/tagout and your site's safe-work procedures, and check the manual for your exact model before you act.

Quick lookup

Faults trip the drive and stop the machine, so in OEE they are availability losses.

Type a code or a word (overcurrent, overvoltage, overheat, ground) to filter the list. Click a code for its causes and first checks. Each code's details name the drives that print it; the MD290 fault table also writes codes as E002.0 for Err02.

Find a code or a word

41 codes

Code	Name
Err02	Overcurrent during acceleration
Err03	Overcurrent during deceleration
Err04	Overcurrent during operation at constant speed
Err05	Overvoltage during acceleration
Err06	Overvoltage during deceleration
Err07	Overvoltage during operation at constant speed
Err08	Control power supply fault (MD200)
Err08	Pre-charge resistor fault (MD290, MD500, MD310)
Err09	Undervoltage
Err10	AC drive overload
Err11	Motor overload
Err12	Input phase loss
Err13	Output phase loss
Err14	Drive overtemperature
Err15	External device fault
Err16	Communication fault
Err17	Contactor fault
Err18	Current detection fault
Err19	Motor parameter auto-tuning fault
Err20	Encoder fault
Err21	EEPROM read-write fault
Err23	AC drive output short-circuited to ground
Err25	Motor over-temperature
Err26	Accumulative running time reached
Err27	User-defined fault 1
Err28	User-defined fault 2
Err29	Accumulative power-on time reached
Err30	Load loss
Err31	PID feedback loss during operation
Err33	Internal communication reception timeout of the driver board
Err40	Pulse-by-pulse current limit fault
Err41	Motor switchover fault during running
Err42	Excessive speed deviation
Err43	Motor overspeed
Err45	Motor temperature fault
Err49	Analog limit violation
Err55	Slave fault during speed synchronization (MD200)
Err55	Master-slave control fault (MD290, MD310)
Err61	Braking transistor overload
Err62	Braking transistor short-circuited
Err96	Control board internal communication timeout

Each code: causes and first checks

Err02: Overcurrent during acceleration

Hits OEE: Availability

What it means: The output current went above the drive's overcurrent limit while the motor was speeding up, so the drive cut its output. The MD290 manual gives the trip point as a transient current above 2.5 x 1.414 x the drive's rated current.^[1]^[2]^[3]^[4]^[5]^[6]

Also on: Drives: MD290, MD200, MD500, MD310. MD290 User Guide B06 fault list prints this code as E002.0 (Overcurrent during acceleration).

Drive response: Output stops at once and the fault relay acts; fix the cause, then reset

Likely causes

Output circuit grounded or short circuited (motor, motor cable or output contactor)
Acceleration time too short
SVC (or FVC on the MD500) selected but motor auto-tuning not done
Overcurrent stall prevention set wrongly: F3-19 off, F3-18 too high or F3-20 too low
Manual torque boost or V/f curve not suitable
Motor started while it was still spinning
Supply voltage too low, a sudden load during acceleration, a drive power rating too low, or a braking resistor whose value is too low or shorted (MD200, MD310)
External interference, or a faulty driver board or Hall device

First checks, in this order

Check the motor, motor cable and contactor for a short circuit: measure U, V and W with a multimeter and the insulation to ground with a megger.
Increase the acceleration time (F0-17).
In SVC, enter the motor nameplate data and run motor auto-tuning.
Make sure current limit is on (F3-19 = 1), keep F3-18 between 120% and 150% (MD290 manual: up to 160% for this fault) and F3-20 between 20 and 40.
Adjust the manual torque boost (F3-01) or the V/f curve.
Use flying start, or start only after the motor has stopped.
Read the current stored with the fault: if it is far below the overcurrent level, look for an interference source; if there is none, the driver board or Hall device may be faulty, so contact the agent or Inovance.

Err03: Overcurrent during deceleration

Hits OEE: Availability

What it means: The output current went above the drive's overcurrent limit while the motor was slowing down. The MD290 manual gives the trip point as a transient current above 2.5 x 1.414 x the drive's rated current.^[1]^[2]^[3]^[4]^[5]^[6]

Also on: Drives: MD290, MD200, MD500, MD310. MD290 User Guide B06 fault list prints this code as E003.0 (Overcurrent during deceleration).

Drive response: Output stops at once and the fault relay acts; fix the cause, then reset

Likely causes

Output circuit grounded or short circuited
Deceleration time too short
SVC (or FVC on the MD500) selected but motor auto-tuning not done
Overcurrent stall prevention set wrongly (F3-19, F3-18, F3-20)
No braking unit or braking resistor installed
Supply voltage too low, a sudden load during deceleration, or a braking resistor whose value is too low or shorted (MD200, MD310)
External interference, or a faulty driver board or Hall device

First checks, in this order

Check the motor, motor cable and contactor for a short circuit or ground fault.
Increase the deceleration time (F0-18).
Enter the motor nameplate data and run motor auto-tuning.
Make sure current limit is on (F3-19 = 1), F3-18 is between 120% and 150% and F3-20 between 20 and 40.
Install a braking unit and braking resistor, or replace a damaged braking resistor.
Compare the fault record current with the overcurrent level to rule out interference; if no source is found, contact the agent or Inovance.

Err04: Overcurrent during operation at constant speed

Hits OEE: Availability

What it means: The output current went above the drive's overcurrent limit while the motor was running at a steady speed. The MD290 manual gives the trip point as a transient current above 2.5 x 1.414 x the drive's rated current.^[1]^[2]^[3]^[4]^[5]^[6]

Also on: Drives: MD290, MD200, MD500, MD310. MD500 manuals name it Overcurrent at constant speed. MD290 User Guide B06 fault list prints this code as E004.0 (Overcurrent during operation at constant speed).

Drive response: Output stops at once and the fault relay acts; fix the cause, then reset

Likely causes

Output circuit grounded or short circuited, or the motor disconnected
SVC (or FVC on the MD500) selected but motor auto-tuning not done
Overcurrent stall prevention set wrongly (F3-19, F3-18, F3-20)
Drive power rating too low for the load
Supply voltage too low, a sudden load during running, or a braking resistor whose value is too low or shorted (MD200, MD310)
External interference, or a faulty driver board or Hall device

First checks, in this order

Check whether the motor or motor cable is short circuited or disconnected.
Enter the motor nameplate data and run motor auto-tuning.
Make sure current limit is on (F3-19 = 1), F3-18 is between 120% and 150% and F3-20 between 20 and 40.
If the steady running current is above the motor rated current or the drive rated output current, fit a drive with a higher power rating.
Check for sudden load changes on the machine.
Compare the fault record current with the overcurrent level to rule out interference.

Err05: Overvoltage during acceleration

Hits OEE: Availability

What it means: The DC bus voltage rose above the overvoltage threshold while the motor was speeding up (on the MD290 the threshold is set by A5-09).^[1]^[2]^[3]^[4]^[5]^[6]

Also on: Drives: MD290, MD200, MD500, MD310. MD290 User Guide B06 fault list prints this code as E005.0 (Overvoltage during acceleration).

Drive response: Output stops at once and the fault relay acts; fix the cause, then reset

Likely causes

Input supply voltage too high
An external force drives the motor during acceleration
Overvoltage stall prevention set wrongly: F3-23 off, F3-22 too high or F3-24 too low
No braking unit or braking resistor installed
Acceleration time too short

First checks, in this order

Measure the input voltage. MD290 normal range: 342 to 418 VAC on three phase 380 V models, 198 to 235.4 VAC on three phase 220 V models.
Remove the external force or install a braking resistor; on the MD290 set F3-26 between 5 Hz and 15 Hz when an external force is present.
Turn on voltage limit (F3-23 = 1), set F3-22 between 700 V and 770 V and F3-24 between 30 and 50.
Install a braking unit and braking resistor.
Increase the acceleration time (F0-17).

Err06: Overvoltage during deceleration

Hits OEE: Availability

What it means: The DC bus voltage rose above the overvoltage threshold while the motor was slowing down, usually because the motor sends energy back into the drive (on the MD290 the threshold is set by A5-09).^[1]^[2]^[3]^[4]^[5]^[6]

Also on: Drives: MD290, MD200, MD500, MD310. MD290 User Guide B06 fault list prints this code as E006.0 (Overvoltage during deceleration).

Drive response: Output stops at once and the fault relay acts; fix the cause, then reset

Likely causes

Overvoltage stall prevention set wrongly: F3-23 off, F3-22 too high or F3-24 too low
An external force or a high inertia load drives the motor during deceleration
Deceleration time too short
No braking unit or braking resistor installed
Input supply voltage too high (MD200, MD310)

First checks, in this order

Turn on voltage limit (F3-23 = 1), set F3-22 between 700 V and 770 V and F3-24 between 30 and 50.
Remove the external force or install a braking resistor.
Increase the deceleration time (F0-18).
Install a braking unit and braking resistor.
Measure the input voltage and bring it back into the normal range.

Err07: Overvoltage during operation at constant speed

Hits OEE: Availability

What it means: The DC bus voltage rose above the overvoltage threshold while the motor was running at a steady speed (on the MD290 the threshold is set by A5-09).^[1]^[2]^[3]^[4]^[5]^[6]

Also on: Drives: MD290, MD200, MD500, MD310. MD500 manuals name it Overvoltage at constant speed. MD290 User Guide B06 fault list prints this code as E007.0 (Overvoltage at a constant speed).

Drive response: Output stops at once and the fault relay acts; fix the cause, then reset

Likely causes

Overvoltage stall prevention set wrongly: F3-23 off, F3-22 too high, F3-24 too low or F3-26 too low
An external force drives the motor while it runs
Input supply voltage too high (MD200, MD310)

First checks, in this order

Turn on voltage limit (F3-23 = 1), set F3-22 between 700 V and 770 V, F3-24 between 30 and 50 and F3-26 between 5 Hz and 20 Hz.
Remove the external force or install a braking resistor.
Measure the input voltage and bring it back into the normal range.

Err08: Control power supply fault (MD200)

Hits OEE: Availability

What it means: On the MD200 this code is a control power supply fault. The only cause Inovance lists is an input voltage outside the specified range.^[2]^[3]

Also on: Drives: MD200. MD200 parameter F9-14 lists fault value 8 as Pre-charge resistor overload (Err08).

Drive response: Output stops at once and the fault relay acts; fix the cause, then reset

Likely causes

Input voltage outside the range in the drive specifications

First checks, in this order

Measure the input supply and bring it back into the range given in the specifications and on the nameplate.
If the voltage is correct and the fault stays, contact the agent or Inovance.

Err08: Pre-charge resistor fault (MD290, MD500, MD310)

Hits OEE: Availability

What it means: A fault in the pre-charge (soft charge) circuit of the DC bus. The MD290 manual says it trips when the pre-charge relay closes many times in a short period with power on; the MD500 manual says the bus voltage keeps fluctuating around the undervoltage threshold.^[1]^[4]^[5]^[6]

Also on: Drives: MD290, MD500, MD310. MD500 User Guide 19010374 A06 names it Pre-charge power fault; MD500 advanced guide 19010355 B04 names it Pre-charge resistor fault. MD290 User Guide B06 fault list prints this code as E008.0 (Pre-charge resistor fault).

Drive response: Output stops at once and the fault relay acts; fix the cause, then reset

Likely causes

Input voltage outside the permitted range, so the pre-charge contactor opens and closes again and again
Input supply switching on and off repeatedly, or large grid voltage fluctuation (MD290)
Bus voltage fluctuating around the undervoltage threshold (MD500)

First checks, in this order

Measure the input voltage; on the MD290 it should be between 342 and 418 VAC for 380 V models.
Check that the supply is not powering on and off repeatedly and that the grid voltage is stable.
If the supply is correct and the fault stays, contact the agent or Inovance.

Err09: Undervoltage

Hits OEE: Availability

What it means: The DC bus voltage fell below the undervoltage threshold (on the MD290 and MD310 set by A5-06).^[1]^[2]^[3]^[4]^[5]^[6]

Also on: Drives: MD290, MD200, MD500, MD310. MD200 fault table names it Undervoltage fault. MD310: shown as A09 instead of Err09 when the drive is stopped (A5-06 description). MD290 User Guide B06 fault list prints this code as E009.0 (Undervoltage).

Drive response: Resets by itself when the bus voltage returns to normal and is not counted as an automatic reset (MD200, MD290, MD500)

Likely causes

Momentary power failure or voltage dip
Input voltage outside the permitted range
Abnormal DC bus voltage
Faulty rectifier bridge, pre-charge resistor, driver board or control board

First checks, in this order

Measure the input voltage; on the MD290 it should be between 342 and 418 VAC for 380 V models.
For short supply dips, enable power dip ride-through (F9-59).
Measure the DC bus voltage with a multimeter: it should be about 1.414 x the input voltage, and the drive's own bus reading should match it (MD290 check).
If the bus voltage or the hardware is abnormal, contact the agent or Inovance.

Err10: AC drive overload

Hits OEE: Availability

What it means: The drive's own overload curve was exceeded: too much current for too long for the drive's rating.^[1]^[2]^[3]^[4]^[5]^[6]

Also on: Drives: MD290, MD200, MD500, MD310. MD310 names it Drive overload. MD290 User Guide B06 fault list prints this code as E010.0 (AC drive overload).

Drive response: Output stops at once and the fault relay acts; fix the cause, then reset

Likely causes

Load too heavy, or the motor is stalled or locked
Drive power rating too low for the application
Carrier frequency set above the default (MD290)
Cracked or damaged output cable (MD290)

First checks, in this order

Reduce the load and check the motor and machine for binding or a locked rotor.
Check whether the motor actually turns when the fault occurs.
If F0-15 (carrier frequency) was raised, lower it.
Inspect the output cable for cracks, short circuits or poor contact, then repeat motor auto-tuning (MD290).
If the load is genuine, fit a drive with a higher power rating.

Err11: Motor overload

Hits OEE: Availability

What it means: The motor overload curve was exceeded. With F9-01 = 1.00 the MD310 and MD500 manuals say the fault trips after 2 minutes at 175% of rated motor current, or after 80 minutes at 115%.^[1]^[2]^[3]^[4]^[5]^[6]

Also on: Drives: MD290, MD200, MD500, MD310. MD290 User Guide B06 fault list prints this code as E011.0 (Motor overload).

Drive response: Action selectable in F9-47 (ones digit): coast to stop, stop by stop mode, or keep running

Likely causes

F9-01 (motor overload protection gain) set wrongly
Load too heavy, or the motor is stalled or locked
Drive power rating too low (MD200, MD310)

First checks, in this order

Check that the motor rated current is entered correctly and that F9-01 is set properly (default 1.0; a higher value lengthens the time to trip).
Reduce the load and check the motor and machine for binding or a locked rotor.
If the load is genuine and the drive power rating is too low, select a drive with a higher power rating (MD200, MD310).

Err12: Input phase loss

Hits OEE: Availability

What it means: The drive detected a missing or abnormal phase on its three phase input.^[1]^[2]^[3]^[4]^[5]^[6]

Also on: Drives: MD290, MD200, MD500, MD310. MD290 User Guide B06 fault list prints this code as E012.0 (Input phase loss exists.).

Drive response: Action selectable in F9-47 (tens digit): coast to stop, stop by stop mode, or keep running

Likely causes

Three phase input supply abnormal: a missing phase or an unbalanced grid
Faulty driver board, lightning protection board, main control board or rectifier bridge

First checks, in this order

Measure all three input phases (MD290: 342 to 418 VAC on 380 V models) and check the R, S, T cables, fuses and breaker.
Check the grid for voltage imbalance; fix the cause or derate the drive.
If the supply is correct and the fault stays, contact the agent or Inovance.

Err13: Output phase loss

Hits OEE: Availability

What it means: One output phase to the motor is missing or the three output currents are badly unbalanced. The MD290 checks this above 0.8 Hz and trips when the highest phase current is more than 7 times the lowest.^[1]^[2]^[3]^[4]^[5]^[6]

Also on: Drives: MD290, MD200, MD500, MD310. MD290 User Guide B06 fault list prints this code as E013.0 (Output phase loss occurs.).

Drive response: Action selectable in F9-47 (hundreds digit): coast to stop, stop by stop mode, or keep running

Likely causes

Motor faulty, for example an open winding
Cable between drive and motor faulty or disconnected
Three phase output unbalanced while the motor runs
Faulty driver board or IGBT module (or lightning protection board on the MD310)

First checks, in this order

Check the motor U, V and W windings and connections for an open circuit.
Check the cable and terminals between the drive and the motor.
Compare the three output currents; check the motor winding resistance.
If the fault stays with a good motor and cable, contact the agent or Inovance.

Err14: Drive overtemperature

Hits OEE: Availability

What it means: The heatsink or power module temperature went above the drive's overtemperature threshold.^[1]^[2]^[3]^[4]^[5]^[6]

Also on: Drives: MD290, MD200, MD500, MD310. MD500 names it IGBT overheat; parameter F9-14 lists it as Module overtemperature. MD290 User Guide B06 fault list prints this code as E014.0 (Drive overtemperature).

Drive response: Output stops at once and the fault relay acts; fix the cause, then reset

Likely causes

Ambient temperature too high (MD290: above 40 C)
Air duct or air filter blocked
Cooling fan damaged or stopped
Carrier frequency set too high (when the fault repeats often)
Temperature sensor (thermistor) damaged
Power module or other internal parts damaged

First checks, in this order

Bring the ambient temperature below 40 C; on the MD290 derate by 1.5% for every 1 C between 40 C and 50 C.
Clean the air duct and air filter.
Check that the fan runs and replace it if it does not.
If the fault comes back often, reduce F0-15 (carrier frequency).
MD290: stop the drive for more than 1 hour; if the reported temperature does not fall, the thermistor is suspect, so contact Inovance.

Err15: External device fault

Hits OEE: Availability

What it means: An external fault signal was received through a digital input or a virtual I/O terminal. On the MD290 a DI set to function 11 has closed, or a DI set to function 33 has opened.^[1]^[2]^[3]^[4]^[5]^[6]

Also on: Drives: MD290, MD200, MD500, MD310. MD500 names it External fault. MD290 User Guide B06 fault list prints this code as E015.0 (The external device is faulty.).

Drive response: Action selectable in F9-47 (thousands digit): coast to stop, stop by stop mode, or keep running

Likely causes

External fault signal from other equipment through a multi-function DI
External fault signal through a virtual I/O terminal (group A1)

First checks, in this order

Check group F4 to find the DI set to function 11 or 33 and check the device and wiring connected to it.
Check the virtual I/O settings in group A1.
Clear the external fault, confirm the machine is safe to restart, then reset the drive.

Err16: Communication fault

Hits OEE: Availability

What it means: Communication between the drive and its host controller or fieldbus network was lost or invalid. On the MD290 the fault trips when the gap between messages exceeds FD-04 (Modbus) or FD-08 (expansion card), or when a master loses its slave.^[1]^[2]^[3]^[4]^[5]^[6]

Also on: Drives: MD290, MD200, MD500, MD310. MD200 names it Communication error. MD290 User Guide B06 fault list prints this code as E016.0 (Communication fault.).

Drive response: Action selectable in F9-47 (ten thousands digit): coast to stop, stop by stop mode, or keep running; MD290 default is stop by stop mode

Likely causes

Host controller program, configuration or wiring not correct
Communication cable damaged or not connected properly
F0-28 (communication protocol selection) set wrongly for the expansion card (MD290, MD500)
Group FD settings (baud rate FD-00, data format FD-01, address FD-02) not matching the host
MD310: Modbus or CANopen timeout, CANopen PDO mapping not matching (groups FE and AF), CANlink heartbeat timeout or station number conflict, or PROFIBUS DP timeout

First checks, in this order

Check the host controller program, configuration file and wiring.
Check the network or RS485 cable and connectors.
Set F0-28 to match the expansion card protocol.
Make FD-00, FD-01 and FD-02 match the host controller settings; check FD-04 against the PLC communication cycle.
MD310 on CAN: read Fd-15 to Fd-17 for interference and fix duplicate station numbers in Fd-13.
MD500: if the fault stays after these checks, restore default settings.

Err17: Contactor fault

Hits OEE: Availability

What it means: The pre-charge (soft start) contactor is not working correctly. The MD290 trips when the contactor fault signal is present for 1 second.^[1]^[4]^[5]^[6]

Also on: Drives: MD290, MD500, MD310. MD290 User Guide B06 fault list prints this code as E017.0 (Contactor fault).

Drive response: Output stops at once and the fault relay acts; fix the cause, then reset

Likely causes

Pre-charge contactor not closing: loose contactor cable, faulty contactor, or faulty 24 V contactor supply
Driver board or power supply board abnormal
Lightning protection board abnormal

First checks, in this order

Check that the input voltage is normal.
Listen at power-on for the contactor closing.
Check the contactor cable and its 24 V supply (MD500).
If these are good, the contactor, driver board, power board or lightning protection board needs replacing: contact the agent or Inovance.

Err18: Current detection fault

Hits OEE: Availability

What it means: The drive's current measurement is abnormal. The MD290 checks the current sensor zero offset at stop and trips if it is more than 10% of rated current.^[1]^[2]^[3]^[4]^[5]^[6]

Also on: Drives: MD290, MD200, MD500, MD310. MD290 and MD310 name it Current detection circuit fault. MD290 User Guide B06 fault list prints this code as E018.0 (Current detection circuit fault).

Drive response: Output stops at once and the fault relay acts; fix the cause, then reset

Likely causes

Driver board abnormal
Hall element (current sensor) abnormal (MD500)
Main circuit not powered while the control part is (MD290)

First checks, in this order

Check that the R, S, T input terminals have voltage.
At stop, check the U, V, W current reading; if it fluctuates by more than 10% of rated current, the Hall sensor or current sampling circuit is damaged.
Contact the agent or Inovance for the driver board or Hall element replacement (MD200: replace the drive).

Err19: Motor parameter auto-tuning fault

Hits OEE: Availability

What it means: Motor auto-tuning did not finish. The MD290 manual says the current was too low during stator resistance tuning.^[1]^[2]^[3]^[4]^[5]^[6]

Also on: Drives: MD290, MD200, MD500, MD310. MD500 names it Motor auto-tuning fault. MD290 User Guide B06 fault list prints this code as E019.0 (Motor parameter auto-tuning fault).

Drive response: Output stops at once and the fault relay acts; fix the cause, then reset

Likely causes

Motor parameters not entered from the nameplate
Auto-tuning timed out: motor not connected or a contactor between drive and motor open
Encoder abnormal or encoder pulses (F1-27) wrong (MD500)

First checks, in this order

Enter the motor nameplate data (F1-00 to F1-06) correctly.
Check that the motor is connected and any output contactor is closed during tuning.
MD500 with encoder: check F1-27 and the encoder signal wiring.

Err20: Encoder fault

Hits OEE: Availability

What it means: The encoder or PG card signal is wrong or lost. With F1-36 (encoder wire-break detection time) above 0.0 s, a wire break lasting longer than F1-36 also trips this fault.^[5]^[6]

Also on: Drives: MD500.

Drive response: Output stops at once and the fault relay acts; fix the cause, then reset

Likely causes

Encoder type not matching the setting
Encoder wiring incorrect
Encoder damaged
PG card abnormal

First checks, in this order

Set the encoder type correctly.
Check the PG card power supply and the encoder phase sequence.
Replace the encoder or the PG card if they are faulty.

Err21: EEPROM read-write fault

Hits OEE: Availability

What it means: The drive could not read or write its parameter memory (EEPROM). The MD290 manual adds that it trips when EEPROM operations run too long or when writes per second exceed F8-58.^[1]^[2]^[3]^[4]^[5]^[6]

Also on: Drives: MD290, MD200, MD500, MD310. MD200 names it Error in read/write operations on EEPROM. MD290 User Guide B06 fault list prints this code as E021.0 (EEPROM read/write fault).

Drive response: Output stops at once and the fault relay acts; fix the cause, then reset

Likely causes

EEPROM chip damaged
Parameters written too often over communication (MD290)

First checks, in this order

If a host controller writes parameters over communication, check that it does not write too often and that it uses the RAM addresses given in the parameter list (MD290).
Otherwise contact the agent or Inovance: the main control board needs replacing (MD200: replace the drive).

Err23: AC drive output short-circuited to ground

Hits OEE: Availability

What it means: Current from an output phase to ground went above the design threshold, so the drive treats the output as shorted to ground. It can also appear right at power-on.^[1]^[2]^[3]^[4]^[5]^[6]

Also on: Drives: MD290, MD200, MD500, MD310. MD200 names it The AC drive output is short-circuited to ground; MD500 names it Short circuit to ground. MD290 User Guide B06 fault list prints this code as E023.0 (Output short-circuited to ground).

Drive response: Cannot be reset automatically or manually; switch power off and on after fixing (MD290, MD500)

Likely causes

Motor or motor cable short circuited to ground
IGBT short circuit found in the self-check, or a damaged inverter transistor

First checks, in this order

Do not run the motor until the ground fault is fixed.
Measure the insulation to ground of the motor and output cable with a megger and check each connection; replace the cable or motor if needed.
If the motor and cable are good and the fault repeats in static self-check, replace the drive or contact the agent or Inovance.

Err25: Motor over-temperature

Hits OEE: Availability

What it means: The sampled motor temperature reached the overheat temperature.^[1]

Also on: Drives: MD290. Fault description section names it Motor overheat; MD290 revision B04 added this code. MD290 User Guide B06 fault list prints this code as E025.0 (Motor over-temperature).

Drive response: Output stops at once and the fault relay acts; fix the cause, then reset

Likely causes

Motor temperature too high

First checks, in this order

Check whether the motor temperature exceeds its upper limit.
Reduce the carrier frequency or improve motor cooling, or replace the motor.
If unresolved, contact Inovance technical support.

Err26: Accumulative running time reached

Hits OEE: Availability

What it means: The total running time has reached the value set for this alarm (on the MD290: F8-17 hours plus F8-75).^[1]^[2]^[3]^[4]^[5]^[6]

Also on: Drives: MD290, MD200, MD500, MD310. MD200 names it Cumulative running time reach; MD310 Accumulative operating time reached. MD290 User Guide B06 fault list prints this code as E026.0 (Cumulative operating time reached).

Drive response: Output stops at once and the fault relay acts; fix the cause, then reset

Likely causes

Set accumulative running time reached

First checks, in this order

Check the running time setting (F8-17) if the fault is not wanted.
Clear the record by parameter initialization (MD290: FP-01 = 2).

Err27: User-defined fault 1

Hits OEE: Availability

What it means: A digital input or virtual I/O terminal set to function 44 (user-defined fault 1) became active.^[1]^[2]^[3]^[4]^[5]^[6]

Also on: Drives: MD290, MD200, MD500, MD310. MD290 User Guide B06 fault list prints this code as E027.0 (User-defined fault 1).

Drive response: Output stops at once and the fault relay acts; fix the cause, then reset

Likely causes

User-defined fault 1 signal on a multi-function DI
User-defined fault 1 signal on a virtual I/O terminal

First checks, in this order

Find the DI or virtual I/O set to function 44 (group F4 or A1) and check the device that drives it.
Clear the condition, then reset the drive.

Err28: User-defined fault 2

Hits OEE: Availability

What it means: A digital input or virtual I/O terminal set to function 45 (user-defined fault 2) became active.^[1]^[2]^[3]^[4]^[5]^[6]

Also on: Drives: MD290, MD200, MD500, MD310. MD290 User Guide B06 fault list prints this code as E028.0 (User-defined fault 2).

Drive response: Output stops at once and the fault relay acts; fix the cause, then reset

Likely causes

User-defined fault 2 signal on a multi-function DI
User-defined fault 2 signal on a virtual I/O terminal

First checks, in this order

Find the DI or virtual I/O set to function 45 (group F4 or A1) and check the device that drives it.
Clear the condition, then reset the drive.

Err29: Accumulative power-on time reached

Hits OEE: Availability

What it means: The total powered-on time has reached the value set for this alarm (on the MD290: F8-16 hours plus F8-74).^[1]^[2]^[3]^[4]^[5]^[6]

Also on: Drives: MD290, MD200, MD500, MD310. MD200 names it Cumulative power-on time reach. MD290 User Guide B06 fault list prints this code as E029.0 (Cumulative power-on time reached).

Drive response: Output stops at once and the fault relay acts; fix the cause, then reset

Likely causes

Set accumulative power-on time reached

First checks, in this order

Check the power-on time setting (F8-16) if the fault is not wanted.
Clear the record by parameter initialization (MD290: FP-01 = 2).

Err30: Load loss

Hits OEE: Availability

What it means: While running, the output current stayed below F9-64 (load loss detection level) for longer than F9-65 (load loss detection time).^[1]^[2]^[3]^[4]^[5]^[6]

Also on: Drives: MD290, MD200, MD500, MD310. MD290 User Guide B06 fault list prints this code as E030.0 (Load loss).

Drive response: Output stops at once and the fault relay acts; fix the cause, then reset

Likely causes

Load disconnected from the motor during operation
Output cables not connected properly
F9-64 or F9-65 not set for the real operating conditions

First checks, in this order

Check whether the load is actually disconnected and whether the cables, such as the output cables, are connected properly.
Set F9-64 and F9-65 to match the real operating conditions.

Err31: PID feedback loss during operation

Hits OEE: Availability

What it means: The PID feedback signal stayed below FA-26 (PID feedback loss detection level) for longer than FA-27.^[1]^[2]^[3]^[4]^[5]^[6]

Also on: Drives: MD290, MD200, MD500, MD310. MD200 names it PID feedback loss during running; MD500 PID Feedback loss. MD290 User Guide B06 fault list prints this code as E031.0 (PID feedback loss during operation).

Drive response: Output stops at once and the fault relay acts; fix the cause, then reset

Likely causes

PID feedback signal lower than FA-26: sensor, wiring or analog input problem
FA-26 set wrongly

First checks, in this order

Check the feedback sensor, its wiring and the analog input value (the MD290 manual suggests monitoring the feedback channel in InoDriverShop).
Set FA-26 to a suitable value.

Err33: Internal communication reception timeout of the driver board

Hits OEE: Availability

What it means: Communication inside the drive between the control board and the driver board timed out.^[4]

Also on: Drives: MD310.

Drive response: Output stops at once and the fault relay acts; fix the cause, then reset

Likely causes

Loose internal cables in the drive
Driver board abnormal
Control board abnormal

First checks, in this order

Check whether the internal cable between the control board and the driver board is loose.
If it is secure, contact the agent or Inovance.

Err40: Pulse-by-pulse current limit fault

Hits OEE: Availability

What it means: The fast (pulse-by-pulse) current limit stayed active too long. On the MD290 it applies only in V/f control and trips after 500 ms of continuous current limiting.^[1]^[2]^[3]^[4]^[5]^[6]

Also on: Drives: MD290, MD200, MD500, MD310. Parameter F9-14 lists it as Fast current limit timeout. MD290 User Guide B06 fault list prints this code as E040.0 (Pulse-by-pulse current limit fault).

Drive response: Output stops at once and the fault relay acts; fix the cause, then reset

Likely causes

Load too heavy, or the motor is stalled or locked
Drive power rating too low

First checks, in this order

Reduce the load and check the motor and machine for binding or a locked rotor.
Fit a drive with a higher power rating if the drive is smaller than the motor.

Err41: Motor switchover fault during running

Hits OEE: Availability

What it means: The motor (parameter set) was switched through a terminal while the drive was running.^[1]^[4]^[5]^[6]

Also on: Drives: MD290, MD500, MD310. MD310 names it Motor switchover fault during operating. MD290 User Guide B06 fault list prints this code as E041.0 (Motor switchover fault during running).

Drive response: Output stops at once and the fault relay acts; fix the cause, then reset

Likely causes

DI assigned to motor switchover (function 41) changed during operation

First checks, in this order

Switch motors only after the drive has stopped.

Err42: Excessive speed deviation

Hits OEE: Availability

What it means: The difference between commanded and actual speed stayed above F9-69 for longer than F9-70.^[2]^[3]^[4]^[5]^[6]

Also on: Drives: MD200, MD500, MD310. MD310 names it Excessively high speed deviation; MD500 Speed error.

Drive response: Output stops at once and the fault relay acts; fix the cause, then reset

Likely causes

Motor stalled or locked
F9-69 and F9-70 set wrongly
Cable between the drive output (U, V, W) and the motor faulty (MD200, MD310)
Encoder parameters wrong, or motor auto-tuning not done (MD500)

First checks, in this order

Check the machine for binding, check that motor auto-tuning was done and that F2-10 is not set too low (MD200, MD310).
Set F9-69 and F9-70 for the real operating conditions.
Check the cable between the drive and the motor.
MD500: set the encoder parameters correctly and run motor auto-tuning.

Err43: Motor overspeed

Hits OEE: Availability

What it means: Motor speed stayed above F9-67 (overspeed detection level) for longer than F9-68.^[5]^[6]

Also on: Drives: MD500.

Drive response: Output stops at once and the fault relay acts; fix the cause, then reset

Likely causes

Encoder parameters set wrongly
Motor auto-tuning not done
F9-67 and F9-68 set wrongly

First checks, in this order

Set the encoder parameters correctly.
Run motor auto-tuning.
Set F9-67 and F9-68 for the real conditions.

Err45: Motor temperature fault

Hits OEE: Availability

What it means: The motor temperature read through the temperature sensor input is above the protection threshold (F9-57).^[1]^[4]^[5]^[6]

Also on: Drives: MD290, MD500, MD310. MD500 names it Motor overheat. MD290 User Guide B06 fault list prints this code as E045.0 (Motor temperature fault).

Drive response: Output stops at once and the fault relay acts; fix the cause, then reset

Likely causes

Temperature sensor cable loose
Motor temperature too high
F9-57 (motor overtemperature protection threshold) set too low (MD290, MD310)

First checks, in this order

Check and reconnect the temperature sensor wiring.
Compare U0-34 (motor temperature) with F9-57 (MD290).
Increase the carrier frequency or take other measures to cool the motor.
Set F9-57 to a suitable value: 90 C to 100 C for normal motors.

Err49: Analog limit violation

Hits OEE: Availability

What it means: The voltage on AI1 to AI3 is outside the range set in A6-16 to A6-21.^[1]

Also on: Drives: MD290. Fault description section names it Voltage overlimit. MD290 User Guide B06 fault list prints this code as E049.0 (Analog limit violation).

Drive response: Output stops at once and the fault relay acts; fix the cause, then reset

Likely causes

Analog input voltage on AI1 to AI3 out of the range set by A6-16 to A6-21

First checks, in this order

Check the signal source and bring the AI1 to AI3 input voltage back into range.
Correct A6-16 to A6-21, or disable this fault report if it is not needed.

Err55: Slave fault during speed synchronization (MD200)

Hits OEE: Availability

What it means: With speed synchronization over CAN enabled, the master receives CAN data but cannot detect the slave, so it reports a point-to-point slave fault.^[2]^[3]

Also on: Drives: MD200.

Drive response: Output stops at once and the fault relay acts; fix the cause, then reset

Likely causes

Slave CAN communication cable disconnected
Slave CAN communication not working

First checks, in this order

Check that the slave's CAN communication cable is connected.
Check that the slave's CAN communication is working.

Err55: Master-slave control fault (MD290, MD310)

Hits OEE: Availability

What it means: In master/slave control, a fault on the slave drive is sent to the master over the CAN bus and the master reports it.^[1]^[4]

Also on: Drives: MD290, MD310. MD290 names it Slave fault under master/slave control. MD290 User Guide B06 fault list prints this code as E055.0 (Slave fault under master/slave control).

Drive response: Output stops at once and the fault relay acts; fix the cause, then reset

Likely causes

The slave drive has a fault

First checks, in this order

Go to the slave drive, read its fault code and fix that fault.

Err61: Braking transistor overload

Hits OEE: Availability

What it means: The braking transistor exceeded its overload curve.^[1]^[4]^[5]^[6]

Also on: Drives: MD290, MD500, MD310. MD500 names it Braking unit overload. MD290 User Guide B06 fault list prints this code as E061.0 (Braking transistor overload).

Drive response: Output stops at once and the fault relay acts; fix the cause, then reset

Likely causes

Braking resistor resistance too low (power too high)

First checks, in this order

Check that the braking resistor model matches the braking component selection in the user guide.
Use a braking resistor with a higher resistance.

Err62: Braking transistor short-circuited

Hits OEE: Availability

What it means: The braking circuit is abnormal. The MD290 manual says it trips when braking current flows for 4 seconds while the transistor is off (above 0.375 x its rated current), or when braking current exceeds 2 x the transistor maximum several times.^[1]^[4]^[5]^[6]

Also on: Drives: MD290, MD500, MD310. MD500 names it Short-circuit of braking circuit; MD290 fault description section names it Braking transistor shoot through. MD290 User Guide B06 fault list prints this code as E062.0 (The braking transistor is short-circuited.).

Drive response: Output stops at once and the fault relay acts; fix the cause, then reset

Likely causes

Braking unit or braking transistor short circuited
Braking resistor damaged or connected wrongly

First checks, in this order

Measure the braking resistor with a multimeter and compare it with its nominal value; replace it if it differs too much.
Check whether an external braking resistor is used and whether it is connected properly, and whether the braking unit works.
Check the bus voltage (U0-02) to see whether braking is active, then contact the agent or Inovance.

Err96: Control board internal communication timeout

Hits OEE: Availability

What it means: Communication inside the drive timed out on the control board side.^[4]

Also on: Drives: MD310.

Drive response: Output stops at once and the fault relay acts; fix the cause, then reset

Likely causes

Loose internal cables
Driver board abnormal
Control board abnormal

First checks, in this order

Check that all internal cables are connected properly.
If they are, contact the agent or Inovance.

Log it, or the same alarm comes back

A fault trips the drive and stops the motor, so in OEE terms it is a breakdown. Log the code, the machine and the minutes lost, every time, even when a reset clears it in seconds.

Reason code: the code plus the drive, for example Inovance MD290 Err02, extruder screw drive, so an overcurrent that comes back after every start-up shows up as a pattern.
Loss bucket: a stop that needs a reset, a part or a technician is an availability loss (breakdown). Stops shorter than your micro-stop threshold go to performance (minor stops). The six big losses page shows where each one belongs.
What to count: how often each code fires per week and the minutes it costs. Two numbers a week turn "that alarm comes up sometimes" into a ranked list. The MTBF and MTTR calculator and the downtime cost calculator do the math.

The free OEE tracker logs each stop with its reason and turns the week into a downtime Pareto, so the code that costs the most rises to the top.

fabrico.io has a guide to VFD fault codes. A fault code tells you what the drive measured, not what happened at the machine in the seconds before. Fabrico's camera-based OEE software syncs line camera video with machine data, so you can replay the moment the line stopped next to the trip.

Frequently asked questions

What does Err02 mean on an Inovance drive?

Err02 is overcurrent during acceleration on the MD200, MD310, MD500 and MD290: the output current went above the overcurrent limit while the motor was speeding up. Inovance lists a short circuit or ground fault on the output, an acceleration time that is too short, missing motor auto-tuning in SVC, wrong current limit settings (F3-18, F3-19, F3-20), an unsuitable torque boost or V/f curve, starting a spinning motor and external interference. Check the motor and cable with a multimeter and megger first, then increase the acceleration time (F0-17) and check the current limit settings. Err03 and Err04 are the same fault during deceleration and at constant speed.

How do I reset a fault on an Inovance MD290 or MD200 drive?

Fix the cause first. Then press STOP/RES on the panel (it works in any control mode when F7-02 = 1, the default), or activate a digital input set to function 9 (fault reset), or write 7 to communication address 2000H when the drive is under communication control (F0-02 = 2), or switch the power off and on. Err09 (undervoltage) clears itself when the bus voltage returns. Err23 (short circuit to ground) cannot be reset automatically or manually on the MD290 and MD500; only a power cycle clears it, after the ground fault is fixed.

What does Err14 mean on an Inovance drive?

Err14 means drive overtemperature (the MD500 calls it IGBT overheat): the heatsink or module temperature is above the limit. Inovance lists high ambient temperature, a blocked air duct or filter, a damaged fan, a damaged thermistor and damaged internal parts. Keep the ambient below 40 C (the MD290 must be derated 1.5% per degree between 40 C and 50 C), clean the air path and check that the fan runs. If Err14 comes back often, reduce the carrier frequency F0-15.

What does HC on the display mean on an Inovance MD200, MD290, MD310 or MD500?

Inovance lists HC as a symptom, not a numbered fault. HC at power-on can come from a poor contact on the flat cable between the driver board and the control board, damaged control board parts, a motor or motor cable shorted to ground, a faulty Hall sensor (MD290, MD500) or a very low grid voltage; Inovance says reconnect the flat cables and otherwise contact the agent or Inovance. If the display is normal at power-on but HC appears as soon as the drive runs and it stops, check for a damaged or stopped fan and for a short circuit on the external control terminals.

What does Err23 mean and why does it show at power-on?

Err23 means the drive output is short circuited to ground: current from an output phase to ground went above the threshold. When it is shown right at power-on, Inovance points to a motor or motor cable shorted to ground, or a damaged drive. Do not run the motor until it is fixed. Check the insulation of the motor and output cable with a megger and replace the cable or motor if needed. If the fault stays with a good motor and cable, contact the agent or Inovance.

Where can I see the fault history on an Inovance MD series drive?

The last three faults are stored in F9-14 (1st fault), F9-15 (2nd fault) and F9-16 (3rd, the latest fault) as numbers, where for example 2 means Err02 and 23 means Err23. The parameters that follow record the frequency, current, bus voltage, input and output terminal state, power-on time and running time when each fault happened, which helps tell a real overcurrent from interference. On the MD290, U0-62 shows the current fault number.

Sources

Codes and meanings follow the manufacturer documentation below. Wording is ours, simplified for the shop floor; the manual for your exact model and software version wins if it differs.

See the moment the drive tripped

Fabrico, a light MES with computer vision, syncs camera footage with machine and timeline data, so you can replay the exact moment the line stopped and review the cause next to the drive's fault. Cameras also catch short stops and a line that is switched on but not producing, the losses nobody writes down. Machines connect through a PLC, a Fabrico IoT device or an AI camera.

Book a Fabrico demo

The lookup stays free.

Other alarm code lookups: FANUC: servo amplifier · spindle amplifier | Siemens: MICROMASTER 440 · MASTERDRIVES · SINAMICS G120 · SINAMICS V90 servo · SINAMICS V20 · SINAMICS G110 | ABB: ACS550 drive · ACS800 drive · robot IRC5 · DCS800 DC drive | Okuma: OSP alarms | Haas: alarm lookup | Mitsubishi: MELSERVO servo · FR-D700 and FR-E700 inverters · FX PLC | Allen-Bradley: Kinetix and Ultra3000 · MicroLogix · PowerFlex 753 and 755 · PowerFlex 70 and 700 · 1336 and 1305 | Yaskawa: V1000 drive · SERVOPACK servo · Motoman robot | Delta: VFD drives · ASDA servo | Eaton: DC1 and SVX9000 drives | Control Techniques: Commander SK and M200 | Kollmorgen: AKD servo | Lenze: SMVector, 8200, 8400, i500 | Magnetek: IMPULSE and DSD 412 | Omron: MX2 and RX inverters · G5 and 1S servo · CP1 and CJ2 PLC | WEG: CFW500, CFW300, CFW11, CFW08 | Hitachi: WJ200 inverter · SJ700 and SJ-P1 | Toshiba: E3, Q9, P9, S15, nC3, AS3 | AutomationDirect: GS10, GS20, GS4, GS1 to GS3 | Festo: CMMT servo drives | Videojet: 1000 Line CIJ printers | Lincoln Electric: Power Wave welders | Fronius: TPS and TPS/i welders | Beckhoff: TwinCAT ADS, NC and BK1120 | Universal Robots: CB3 and e-Series cobots | Pilz: PNOZ safety relays | SICK: S3000, S300, microScan3 | SANYO DENKI: SANMOTION servo | Parker: SSD 590+, 690+, AC10 | KEB: COMBIVERT F5 | Epson: robot RC700, RC90 | B&R: ACOPOS servo | Schneider Electric: Lexium 32 servo | Bosch Rexroth: IndraDrive | Vacon: NX, VACON 100 and 20 | Fuji Electric: FRENIC-Mini, Multi, Ace, MEGA | LS Electric: S100, G100, iG5A | Panasonic: MINAS A6 and A5 servo | Invertek: Optidrive E3, P2, Eco | SEW-Eurodrive: MOVITRAC B and MOVIDRIVE B | HEIDENHAIN: iTNC 530 and TNC | NORD: NORDAC SK 200E and SK 500E | Baldor: Series 15H and 18H drives | Atlas Copco: Elektronikon compressors and VSD | INVT: Goodrive GD20, GD200A, GD350