Troubleshooting / INVT VFD faults

INVT VFD Fault Codes

Every drive trip is downtime on the line, and in OEE it is lost availability. These are the fault codes of INVT Goodrive inverters (GD20, GD200A, GD300, GD350, GD10 and the CHF100A): what each code means, the likely causes, the first checks, and how to log it so it stops coming back.

How faults show

When an INVT Goodrive drive detects a fault it goes into the fault alarm state at once: the TRIP light on the keypad comes on and the keypad shows the fault code (on the GD20 the code blinks, and it stays on the display while the fault persists). A blinking TRIP light means a pre-alarm: the drive is still running but will trip soon if nothing is corrected.

The GD200A LCD keypad spells the fault out, for example 'Fault code: 23, 23: Braking unit fault (bCE)'. The number in square brackets in INVT's fault table (for example [4] for OC1) is the fault type number read over communication and stored in the fault record.

On GD20, GD200A, GD300, GD350 and GD10, P07.27 holds the present fault and P07.28 to P07.32 the five before it (six in total). P07.33 to P07.40, P07.41 to P07.48 and P07.49 to P07.56 hold the running data at the last three faults (running frequency, ramp reference frequency, output voltage, output current, bus voltage, temperature, input and output terminal state).

On the CHF100A, P7.17 to P7.19 hold the last three faults and P7.20 to P7.24 the output frequency, output current, DC bus voltage and terminal states at the latest one. To reset: remove the cause, then press STOP/RST, use a digital input set to function 7 in group P05 (GD20: Fault reset, GD200A: Reset faults), send a reset over communication, or switch the power off.

Automatic reset is set with P08.28 (number of resets, 0 to 10) and P08.29 (interval, 0.1 to 3600.0 s) on GD20 and GD200A, and with P8.16 (0 to 3) and P8.17 on the CHF100A. A CHF100A that is not reset stays in protection and cannot run.

Safety first.
INVT: only trained, qualified electricians may install, wire, inspect or maintain the drive. Do not wire, inspect or replace parts with power applied. Disconnect all input power and wait at least the time marked on the drive, or until the DC bus voltage is below 36 V: 5 minutes for GD20 (all models up to 110 kW) and GD10.

On GD200A 5 minutes up to 110G/132P, 15 minutes for 132/160P to 315G/355P and 25 minutes for 355G/400P and larger. On GD300 and GD350 380 V drives 5 minutes up to 110 kW, 15 minutes from 132 to 315 kW and 25 minutes for the largest units.

On the CHF100A wait 10 minutes after switching off, until the CHARGE light is off, and never run insulation or voltage withstand tests on cables connected to it. The heatsink can be hot during running. Do not modify the drive without authorization.

The GD350 manual adds that the drive is not an emergency stop device and cannot act as an emergency brake, so a mechanical brake must be installed. Sources: GD20 manual V2.1 section 1.3 (PDF page 7). GD200A manual V3.1 section 1.4 (PDF page 9). GD300 manual V3.6 (PDF page 7). GD350 manual V2.1 (PDF page 12). GD10 manual V2.9 (PDF page 7).

CHF100A manual chapters 3 and 4 (PDF pages 10 to 12). 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 inverter and stop the machine, so in OEE they are availability losses; warnings are early signs.

Type a code or a word (overcurrent, overvoltage, phase, overheat) to filter the list. Click a code for its causes and first checks. Each code's details name the INVT drives whose manual prints it; where a drive words the name differently, that wording is there too.

42 codes

CodeName
OUt1Inverter unit U phase protection
OUt2Inverter unit V phase protection
OUt3Inverter unit W phase protection
OC1Overcurrent during acceleration
OC2Overcurrent during deceleration
OC3Overcurrent during constant speed running
OV1Overvoltage during acceleration
OV2Overvoltage during deceleration
OV3Overvoltage during constant speed running
UVBus undervoltage
OL1Motor overload
OL2VFD overload
SPIPhase loss on input side
SPOPhase loss on output side
OH1Rectifier module overheat
OH2Inverter module overheat
EFExternal fault
CERS485 communication fault
ItECurrent detection fault
tEMotor autotuning fault
EEPEEPROM operation fault
PIDEPID feedback offline fault
bCEBraking unit fault
ENDRunning time reached
OL3Electronic overload (GD20, GD200A, GD300, GD350, GD10)
PCEKeypad communication error
UPEParameter upload error
DNEParameter download error
ETH1To-ground short-circuit fault 1
ETH2To-ground short-circuit fault 2
dEuSpeed deviation fault
SToMaladjustment fault
LLElectronic underload fault
PoFFSystem power off
E-DPPROFIBUS card communication timeout fault
E-NETEthernet card communication timeout fault
E-CANCANopen card communication timeout fault
STOSafe torque off
STL1Exception occurred to safe circuit of channel 1
STL2Exception occurred to safe circuit of channel 2
STL3Exception occurred to both channel 1 and channel 2
OL3Overtorque (CHF100A)

Each code: causes and first checks

OUt1: Inverter unit U phase protection

Hits OEE: Availability

What it means: The protection of the U phase of the inverter unit (the IGBT output stage) has tripped, so the drive stops and shows OUt1. CHF100A calls the same code an IGBT Ph-U fault.[1][2][3][4][6]

Also on: Drives: GD20, GD200A, GD300, GD350, CHF100A. GD200A and GD350 print 'Inverter unit U-phase protection'; GD300 prints 'Inverter unit U phase protection'; CHF100A prints 'IGBT Ph-U fault'. Fault type number [1] when read over communication.

Drive response: Drive trips and the TRIP light is on; fix the cause, then reset with STOP/RST, a fault reset input or a power cycle

Likely causes

  • Acceleration too fast (ACC time too short); GD350 also names deceleration
  • IGBT module fault or damage
  • False trip caused by electrical interference
  • Drive wires inside the drive poorly connected
  • Improper grounding, or a short circuit to ground on the output (GD200A, GD300, GD350)
  • Sparks inside the drive because of a poor environment, such as dust or oil (GD350)

First checks, in this order

  1. Increase the ACC time (GD350: ACC and DEC time).
  2. Check the drive wires for loose connections.
  3. Check for strong interference from external equipment and remove it.
  4. Check the motor wiring and look for a motor to ground short; check that the drive and system are reliably grounded (GD350).
  5. Remove dust or oil inside the drive regularly (GD350).
  6. If the IGBT module is damaged, the power unit (inverter unit) has to be replaced; INVT says to ask for support.

OUt2: Inverter unit V phase protection

Hits OEE: Availability

What it means: The protection of the V phase of the inverter unit (the IGBT output stage) has tripped, so the drive stops and shows OUt2. CHF100A calls the same code an IGBT Ph-V fault.[1][2][3][4][6]

Also on: Drives: GD20, GD200A, GD300, GD350, CHF100A. GD200A and GD350 print 'Inverter unit V-phase protection'; GD300 prints 'Inverter unit V phase protection'; CHF100A prints 'IGBT Ph-V fault'. Fault type number [2] when read over communication.

Drive response: Drive trips and the TRIP light is on; fix the cause, then reset with STOP/RST, a fault reset input or a power cycle

Likely causes

  • Acceleration too fast (ACC time too short); GD350 also names deceleration
  • IGBT module fault or damage
  • False trip caused by electrical interference
  • Drive wires inside the drive poorly connected
  • Improper grounding, or a short circuit to ground on the output (GD200A, GD300, GD350)
  • Sparks inside the drive because of a poor environment, such as dust or oil (GD350)

First checks, in this order

  1. Increase the ACC time (GD350: ACC and DEC time).
  2. Check the drive wires for loose connections.
  3. Check for strong interference from external equipment and remove it.
  4. Check the motor wiring and look for a motor to ground short; check that the drive and system are reliably grounded (GD350).
  5. Remove dust or oil inside the drive regularly (GD350).
  6. If the IGBT module is damaged, the power unit (inverter unit) has to be replaced; INVT says to ask for support.

OUt3: Inverter unit W phase protection

Hits OEE: Availability

What it means: The protection of the W phase of the inverter unit (the IGBT output stage) has tripped, so the drive stops and shows OUt3. CHF100A calls the same code an IGBT Ph-W fault.[1][2][3][4][6]

Also on: Drives: GD20, GD200A, GD300, GD350, CHF100A. GD200A and GD350 print 'Inverter unit W-phase protection'; GD300 prints 'Inverter unit W phase protection'; CHF100A prints 'IGBT Ph-W fault'. Fault type number [3] when read over communication.

Drive response: Drive trips and the TRIP light is on; fix the cause, then reset with STOP/RST, a fault reset input or a power cycle

Likely causes

  • Acceleration too fast (ACC time too short); GD350 also names deceleration
  • IGBT module fault or damage
  • False trip caused by electrical interference
  • Drive wires inside the drive poorly connected
  • Improper grounding, or a short circuit to ground on the output (GD200A, GD300, GD350)
  • Sparks inside the drive because of a poor environment, such as dust or oil (GD350)

First checks, in this order

  1. Increase the ACC time (GD350: ACC and DEC time).
  2. Check the drive wires for loose connections.
  3. Check for strong interference from external equipment and remove it.
  4. Check the motor wiring and look for a motor to ground short; check that the drive and system are reliably grounded (GD350).
  5. Remove dust or oil inside the drive regularly (GD350).
  6. If the IGBT module is damaged, the power unit (inverter unit) has to be replaced; INVT says to ask for support.

OC1: Overcurrent during acceleration

Hits OEE: Availability

What it means: The drive tripped on overcurrent while the motor was accelerating.[1][2][3][4][5][6]

Also on: Drives: GD20, GD200A, GD300, GD350, GD10, CHF100A. GD200A and GD350: 'Overcurrent during ACC'; GD300: 'Accelerating overcurrent'; GD10: 'Overcurrent during acceleration'; CHF100A: 'Over-current when acceleration'. Fault type [4].

Drive response: Drive trips and the TRIP light is on; fix the cause, then reset with STOP/RST, a fault reset input or a power cycle

Likely causes

  • Acceleration too fast (ACC time too short)
  • Grid (supply) voltage too low
  • Drive power rating too small for the load
  • Sudden load change or abnormal load
  • Short circuit to ground or output phase loss
  • Strong external interference (GD350 names contactor switching and improper grounding)
  • Overvoltage stall protection not enabled (as printed by INVT)
  • Three phase output current imbalance (GD350)

First checks, in this order

  1. Increase the ACC time.
  2. Check the input power supply voltage.
  3. Check whether the load or the output wiring is short circuited (to ground or line to line) and whether the machine turns smoothly.
  4. Check the output wiring and configuration.
  5. Check for strong interference; keep the motor cable away from contactors and make sure the system is reliably grounded (GD350).
  6. Check the related function code settings.
  7. If the drive is too small, select a drive with a larger power rating.

OC2: Overcurrent during deceleration

Hits OEE: Availability

What it means: The drive tripped on overcurrent while the motor was decelerating.[1][2][3][4][5][6]

Also on: Drives: GD20, GD200A, GD300, GD350, GD10, CHF100A. GD200A and GD350: 'Overcurrent during DEC'; GD300: 'Decelerating overcurrent'; GD10: 'Overcurrent during deceleration'; CHF100A: 'Over-current when deceleration'. Fault type [5].

Drive response: Drive trips and the TRIP light is on; fix the cause, then reset with STOP/RST, a fault reset input or a power cycle

Likely causes

  • Deceleration too fast (DEC time too short)
  • Large load inertia (CHF100A)
  • Grid (supply) voltage too low
  • Drive power rating too small for the load
  • Sudden load change or abnormal load
  • Short circuit to ground or output phase loss
  • Strong external interference
  • Overvoltage stall protection not enabled (as printed by INVT)

First checks, in this order

  1. Increase the DEC time.
  2. Fit suitable energy consumption braking components (CHF100A).
  3. Check the input power supply voltage.
  4. Check whether the load or the output wiring is short circuited (to ground or line to line) and whether the machine turns smoothly.
  5. Check the output wiring and check for strong interference.
  6. Check the related function code settings.
  7. If the drive is too small, select a drive with a larger power rating.

OC3: Overcurrent during constant speed running

Hits OEE: Availability

What it means: The drive tripped on overcurrent while running at a steady speed.[1][2][3][4][5][6]

Also on: Drives: GD20, GD200A, GD300, GD350, GD10, CHF100A. GD200A and GD350: 'Overcurrent during constant speed running'; GD300: 'Constant overcurrent'; GD10: 'Overcurrent during constant speed running'; CHF100A: 'Over-current when constant speed running'. Fault type [6].

Drive response: Drive trips and the TRIP light is on; fix the cause, then reset with STOP/RST, a fault reset input or a power cycle

Likely causes

  • Sudden load change or abnormal load
  • Grid (supply) voltage too low
  • Drive power rating too small for the load
  • Short circuit to ground or output phase loss
  • Strong external interference
  • Overvoltage stall protection not enabled (as printed by INVT)
  • Three phase output current imbalance (GD350)

First checks, in this order

  1. Check the load and reduce sudden load changes (CHF100A).
  2. Check the input power supply voltage.
  3. Check for motor stalling and whether the load or the output wiring is short circuited (to ground or line to line).
  4. Check the output wiring and check for strong interference.
  5. Check the three phase output voltage and the motor three phase resistance for imbalance (GD350).
  6. Check the related function code settings.
  7. If the drive is too small, select a drive with a larger power rating.

OV1: Overvoltage during acceleration

Hits OEE: Availability

What it means: The DC bus voltage went too high while the motor was accelerating, so the drive tripped.[1][2][3][4][5][6]

Also on: Drives: GD20, GD200A, GD300, GD350, GD10, CHF100A. GD200A and GD350: 'Overvoltage during ACC'; GD300: 'Accelerating overvoltage'; CHF100A: 'Over-voltage when acceleration'. Fault type [7].

Drive response: Drive trips and the TRIP light is on; fix the cause, then reset with STOP/RST, a fault reset input or a power cycle

Likely causes

  • Input supply voltage abnormal
  • Large energy fed back from the motor and load
  • No braking components fitted, or dynamic braking not enabled
  • Motor restarted while still rotating, for example after a sudden power loss (CHF100A, GD350)

First checks, in this order

  1. Check the input power supply.
  2. Check whether the motor is started while it is still rotating; avoid restarting a coasting motor, or use the speed tracking start function (GD350).
  3. Install dynamic braking components (braking unit or braking resistor) and check the related function codes.

OV2: Overvoltage during deceleration

Hits OEE: Availability

What it means: The DC bus voltage went too high while the motor was decelerating, so the drive tripped.[1][2][3][4][5][6]

Also on: Drives: GD20, GD200A, GD300, GD350, GD10, CHF100A. GD200A and GD350: 'Overvoltage during DEC'; GD300: 'Decelerating overvoltage'; CHF100A: 'Over-voltage when deceleration'. Fault type [8].

Drive response: Drive trips and the TRIP light is on; fix the cause, then reset with STOP/RST, a fault reset input or a power cycle

Likely causes

  • Deceleration time too short for the load
  • Large load inertia, so a lot of energy is fed back
  • Input supply voltage abnormal
  • No braking components fitted, or dynamic braking not enabled

First checks, in this order

  1. Increase the DEC time.
  2. Install or increase energy consumption (dynamic braking) components, or regenerative units (GD350), and set the dynamic braking parameters.
  3. Check the input power supply.

OV3: Overvoltage during constant speed running

Hits OEE: Availability

What it means: The DC bus voltage went too high while the drive was running at a steady speed, so it tripped.[1][2][3][4][5][6]

Also on: Drives: GD20, GD200A, GD300, GD350, GD10, CHF100A. GD200A and GD350: 'Overvoltage during constant speed running'; GD300: 'Constant overvoltage'; CHF100A: 'Over-voltage when constant speed running'. Fault type [9].

Drive response: Drive trips and the TRIP light is on; fix the cause, then reset with STOP/RST, a fault reset input or a power cycle

Likely causes

  • Input supply voltage changes abnormally
  • Large load inertia or large regenerated energy
  • No braking components fitted, or dynamic braking not enabled

First checks, in this order

  1. Check the input power supply; CHF100A advises installing an input reactor.
  2. Install suitable energy consumption (dynamic braking) components and check the related function codes.

UV: Bus undervoltage

Hits OEE: Availability

What it means: The DC bus voltage has dropped too low, usually because the supply voltage is too low.[1][2][3][4][5][6]

Also on: Drives: GD20, GD200A, GD300, GD350, GD10, CHF100A. GD300: 'Bus undervoltage fault'; CHF100A: 'DC bus Under-voltage'. Fault type [10]. See also PoFF.

Drive response: Drive trips and the TRIP light is on; fix the cause, then reset with STOP/RST, a fault reset input or a power cycle

Likely causes

  • Supply (grid) voltage too low
  • Overvoltage stall protection not enabled (GD200A, GD300, as printed by INVT)
  • Abnormal bus voltage display or abnormal precharge contactor closing (GD350)

First checks, in this order

  1. Check the input power of the supply line.
  2. Check the setting of the related function codes (GD200A, GD300).
  3. On a GD350, if the bus voltage display or the precharge contactor is abnormal, contact INVT.

OL1: Motor overload

Hits OEE: Availability

What it means: The drive's motor overload protection has tripped.[1][2][3][4][5][6]

Also on: Drives: GD20, GD200A, GD300, GD350, GD10, CHF100A. Same name on all six families. Fault type [11].

Drive response: Drive trips and the TRIP light is on; fix the cause, then reset with STOP/RST, a fault reset input or a power cycle

Likely causes

  • Supply voltage too low
  • Motor rated current set incorrectly in the drive
  • Motor stall or violent load changes
  • Motor power too big (CHF100A)

First checks, in this order

  1. Check the supply line voltage.
  2. Set the motor rated current correctly (GD350: in the motor parameter group).
  3. Check the load and adjust the torque boost.
  4. Select a proper motor (CHF100A).

OL2: VFD overload

Hits OEE: Availability

What it means: The drive's own overload protection (VFD overload, as opposed to motor overload OL1) has tripped.[1][2][3][4][5][6]

Also on: Drives: GD20, GD200A, GD300, GD350, GD10, CHF100A. CHF100A: 'Inverter overload'. Fault type [12].

Drive response: Drive trips and the TRIP light is on; fix the cause, then reset with STOP/RST, a fault reset input or a power cycle

Likely causes

  • Acceleration too fast
  • Motor restarted while it is still rotating
  • Supply voltage too low
  • Load too heavy
  • Drive power too small for the motor (GD20: motor power too large for the drive)

First checks, in this order

  1. Increase the ACC time.
  2. Avoid restarting after stop while the motor still turns, or enable speed tracking start (GD350).
  3. Check the supply line voltage.
  4. Select a drive with a larger power rating, or a proper motor.

SPI: Phase loss on input side

Hits OEE: Availability

What it means: The drive has detected a missing phase, or violent fluctuation, on its R, S, T supply input.[1][2][3][4][6]

Also on: Drives: GD20, GD200A, GD300, GD350, CHF100A. GD300 and CHF100A: 'Input phase loss'. Fault type [13]. On GD20 the P11.00 default depends on size (input phase loss hardware detection is on by default from 4 kW); GD200A notes input phase loss detection is ineffective on -4 models from 0.75 to 2.2 kW.

Drive response: Drive trips and the TRIP light is on; fix the cause, then reset with STOP/RST, a fault reset input or a power cycle

Likely causes

  • Phase loss or violent fluctuation on input R, S, T
  • Loose input side screws or input cables (GD350)

First checks, in this order

  1. Check the input power on all three phases.
  2. Check the installation wiring and tighten loose input cables.
  3. Input phase loss protection is set in P11.00 (GD20, GD200A, GD350); GD350 notes P11.00 can screen out the fault.

SPO: Phase loss on output side

Hits OEE: Availability

What it means: The drive has detected a missing phase on its U, V, W output, or the three motor phases are badly unbalanced.[1][2][3][4][6]

Also on: Drives: GD20, GD200A, GD300, GD350, CHF100A. GD300 and CHF100A: 'Output phase loss'. Fault type [14].

Drive response: Drive trips and the TRIP light is on; fix the cause, then reset with STOP/RST, a fault reset input or a power cycle

Likely causes

  • Phase loss on U, V or W output
  • The three phases of the motor or load are seriously asymmetrical
  • Output cables broken or shorted to ground (GD350)

First checks, in this order

  1. Check the output wiring for loose or broken cables.
  2. Check the motor and the motor cable.
  3. Check for sharp load fluctuation and for motor three phase resistance imbalance (GD350).

OH1: Rectifier module overheat

Hits OEE: Availability

What it means: The rectifier (input) module of the drive is too hot, so the drive tripped.[1][2][3][4][5][6]

Also on: Drives: GD20, GD200A, GD300, GD350, GD10, CHF100A. GD200A and GD350: 'Rectifier module overheating'; GD300: 'Rectifier module overheated'; CHF100A: 'Rectify overheat'. Fault type [15].

Drive response: Drive trips and the TRIP light is on; fix the cause, then reset with STOP/RST, a fault reset input or a power cycle

Likely causes

  • Air duct blocked or cooling fan damaged
  • Ambient temperature too high
  • Overload running for too long
  • Sudden overcurrent, or a direct or indirect short circuit between the output phases (CHF100A)
  • Loose control board wiring or plug-ins, damaged auxiliary power supply, or a control board fault (CHF100A)

First checks, in this order

  1. Clear the air duct and replace the fan if it is damaged.
  2. Lower the ambient temperature and keep good ventilation.
  3. Select a drive with a larger power rating (GD350).
  4. On a CHF100A, follow the overcurrent checks, check and reconnect loose wiring, and ask INVT for service for power supply or board faults.

OH2: Inverter module overheat

Hits OEE: Availability

What it means: The inverter (IGBT output) module of the drive is too hot, so the drive tripped.[1][2][3][4][5][6]

Also on: Drives: GD20, GD200A, GD300, GD350, GD10, CHF100A. GD350: 'Inverter module overheating'; GD300: 'Inverter module overheated'; CHF100A: 'IGBT overheat'. Fault type [16].

Drive response: Drive trips and the TRIP light is on; fix the cause, then reset with STOP/RST, a fault reset input or a power cycle

Likely causes

  • Air duct blocked or cooling fan damaged
  • Ambient temperature too high
  • Overload running for too long
  • Sudden overcurrent, or a direct or indirect short circuit between the output phases (CHF100A)
  • Loose control board wiring or plug-ins, damaged auxiliary power supply, or a control board fault (CHF100A)

First checks, in this order

  1. Clear the air duct and replace the fan if it is damaged.
  2. Lower the ambient temperature and keep good ventilation.
  3. Select a drive with a larger power rating (GD350).
  4. On a CHF100A, follow the overcurrent checks, check and reconnect loose wiring, and ask INVT for service for power supply or board faults.

EF: External fault

Hits OEE: Availability

What it means: A digital input (S terminal) set as an external fault input has switched, so the drive tripped. INVT points to the external device connected to that input.[1][2][3][4][5][6]

Also on: Drives: GD20, GD200A, GD300, GD350, GD10, CHF100A. Same name on all six families. Fault type [17].

Drive response: Drive trips and the TRIP light is on; fix the cause, then reset with STOP/RST, a fault reset input or a power cycle

Likely causes

  • The external fault input terminal has acted

First checks, in this order

  1. Check the external device wired to that input and its signal.

CE: RS485 communication fault

Hits OEE: Availability

What it means: Serial (RS485 Modbus) communication with the drive has failed or timed out.[1][2][3][4][5][6]

Also on: Drives: GD20, GD200A, GD300, GD350, GD10, CHF100A. GD300: '485 communication fault'; GD350 parameter list: 'Modbus/Modbus TCP communication fault'; CHF100A: 'Communication fault'. Fault type [18].

Drive response: Drive trips and the TRIP light is on; fix the cause, then reset with STOP/RST, a fault reset input or a power cycle

Likely causes

  • Baud rate set incorrectly
  • Fault in the communication wiring
  • Wrong communication address
  • Strong interference on the communication line
  • Communication off for a long time (CHF100A)

First checks, in this order

  1. Set the correct baud rate.
  2. Check the communication wiring and connections.
  3. Set the correct communication address.
  4. Re-route or replace the wiring to improve noise immunity; GD350 recommends shielded cable.
  5. Check the timeout setting: P14.04 on GD20 and GD200A (0.0 s disables the timeout) and the action on error in P14.05 (default: report the alarm and coast to stop); PC.05 on CHF100A.

ItE: Current detection fault

Hits OEE: Availability

What it means: The drive's current measurement circuit is reporting an error.[1][2][3][4][6]

Also on: Drives: GD20, GD200A, GD300, GD350, CHF100A. GD300: 'Current-detecting fault'. Fault type [19].

Drive response: Drive trips and the TRIP light is on; fix the cause, then reset with STOP/RST, a fault reset input or a power cycle

Likely causes

  • Poor contact of the control board connector
  • Hall component damaged (GD200A, GD300, GD350; CHF100A writes 'Hoare components')
  • Exception in the amplifier (signal) circuit
  • Abnormal motor cable or motor insulation, Hall cable in poor contact, or current sampling optocoupler damaged (GD350)
  • Auxiliary power supply damaged (CHF100A)

First checks, in this order

  1. Check the control board connector and plug it in again.
  2. Remove the motor cables to check whether the fault stays (GD350).
  3. Replace the Hall component or the main control board, through INVT service.

tE: Motor autotuning fault

Hits OEE: Availability

What it means: Motor parameter autotuning failed.[1][2][3][4][6]

Also on: Drives: GD20, GD200A, GD300, GD350, CHF100A. GD300: 'Motor-autotuning fault'; CHF100A: 'Autotuning fault'. Fault type [20].

Drive response: Drive trips and the TRIP light is on; fix the cause, then reset with STOP/RST, a fault reset input or a power cycle

Likely causes

  • Motor capacity does not match the drive capacity (GD350: can occur if they differ by more than five power classes)
  • Motor rated parameters set incorrectly
  • Parameters from autotuning deviate sharply from the standard parameters
  • Autotuning timed out
  • Pulse current setting too large (GD350)

First checks, in this order

  1. Use a drive model that matches the motor, or use V/F control (GD350).
  2. Set the motor type and rated parameters from the motor nameplate.
  3. Remove the motor load and run autotuning again.
  4. Check the motor wiring and the parameter settings.
  5. Check that the upper limit frequency is above 2/3 of the rated frequency.
  6. Reduce the pulse current setting (GD350).

EEP: EEPROM operation fault

Hits OEE: Availability

What it means: The drive could not read or write its stored parameters (EEPROM).[1][2][3][4][5][6]

Also on: Drives: GD20, GD200A, GD300, GD350, GD10, CHF100A. GD200A parameter list: 'EEPROM operation error'; CHF100A: 'EEPROM fault'. Fault type [21].

Drive response: Drive trips and the TRIP light is on; fix the cause, then reset with STOP/RST, a fault reset input or a power cycle

Likely causes

  • Error reading or writing the control parameters
  • EEPROM damaged

First checks, in this order

  1. Press STOP/RST to reset.
  2. If it returns, the main control board has to be replaced (INVT service).

PIDE: PID feedback offline fault

Hits OEE: Availability

What it means: The PID feedback signal has been lost.[1][2][3][4][5][6]

Also on: Drives: GD20, GD200A, GD300, GD350, GD10, CHF100A. GD300: 'PID feedback outline fault'; CHF100A: 'PID feedback fault'. Fault type [22].

Drive response: Drive trips and the TRIP light is on; fix the cause, then reset with STOP/RST, a fault reset input or a power cycle

Likely causes

  • PID feedback signal offline
  • PID feedback source disappears

First checks, in this order

  1. Check the PID feedback signal wires.
  2. Check the PID feedback source (sensor).

bCE: Braking unit fault

Hits OEE: Availability

What it means: The drive has detected a fault in its braking circuit.[1][2][3][4][6]

Also on: Drives: GD20, GD200A, GD300, GD350, CHF100A. Same name on GD20, GD200A, GD300, GD350 and CHF100A. Fault type [23].

Drive response: Drive trips and the TRIP light is on; fix the cause, then reset with STOP/RST, a fault reset input or a power cycle

Likely causes

  • Fault in the braking circuit, or the braking pipe (INVT's wording) is damaged
  • External braking resistor value too small

First checks, in this order

  1. Check the braking unit and replace the braking pipe.
  2. Increase the braking resistance.

END: Running time reached

Hits OEE: Availability

What it means: The drive's actual running time has passed the running time set internally (CHF100A: trial time arrival), so it stops.[1][2][3][4][5][6]

Also on: Drives: GD20, GD200A, GD300, GD350, GD10, CHF100A. GD300: 'Running time arrival'; CHF100A: 'Time reach of factory setting'. Fault type [24].

Drive response: Drive trips and the TRIP light is on; fix the cause, then reset with STOP/RST, a fault reset input or a power cycle

Likely causes

  • The actual running time of the drive is longer than the internally set running time

First checks, in this order

  1. Ask the supplier to adjust the set running time (GD350: contact INVT).

OL3: Electronic overload (GD20, GD200A, GD300, GD350, GD10)

Warning: act before it becomes a stop

What it means: Overload pre-alarm: the output current of the drive or motor (or the motor torque, depending on P11.08) has stayed above the overload pre-alarm level (P11.09) for longer than the detection time (P11.10).[1][2][3][4][5]

Also on: Drives: GD20, GD200A, GD300, GD350, GD10. GD200A, GD350 and GD10: 'Electronic overload fault'; GD300: 'Electrical overload'. Fault type [25]. On CHF100A, OL3 means Overtorque (separate row).

Drive response: Set by P11.08 tens place on GD20 and GD200A: 0 (default) keeps running after the alarm, 1 or 3 stops on an overload fault; the TRIP light blinks during a pre-alarm

Likely causes

  • The load is above the overload pre-alarm threshold set in the drive

First checks, in this order

  1. Check the load.
  2. Check that the overload pre-alarm threshold and time (P11.09, P11.10) and the reference set in P11.08 are right for the application.

PCE: Keypad communication error

Hits OEE: Availability

What it means: The drive's main board has lost communication with the keypad.[1][2][3][4]

Also on: Drives: GD20, GD200A, GD300, GD350. GD200A, GD300 and GD350: 'Keypad communication fault'. Fault type [26].

Drive response: Drive trips and the TRIP light is on; fix the cause, then reset with STOP/RST, a fault reset input or a power cycle

Likely causes

  • Keypad cable loose, poorly connected or disconnected
  • Keypad cable too long, picking up strong interference
  • Fault in the communication circuit of the keypad or main board

First checks, in this order

  1. Check the keypad cable and plug it in again.
  2. Check the surroundings and remove the interference source.
  3. If it persists, replace the hardware through INVT maintenance service.

UPE: Parameter upload error

Hits OEE: Availability

What it means: Copying parameters from the drive up to the keypad failed.[1][2][3][4]

Also on: Drives: GD20, GD200A, GD300, GD350. GD300: 'Parameters uploading fault'. Fault type [27].

Drive response: Drive trips and the TRIP light is on; fix the cause, then reset with STOP/RST, a fault reset input or a power cycle

Likely causes

  • Keypad cable loose, poorly connected or disconnected
  • Keypad cable too long, picking up strong interference
  • Fault in the communication circuit of the keypad or main board

First checks, in this order

  1. Check the keypad cable and plug it in again.
  2. Check the surroundings and remove the interference source.
  3. If it persists, replace the hardware through INVT maintenance service.

DNE: Parameter download error

Hits OEE: Availability

What it means: Copying parameters from the keypad down to the drive failed.[1][2][3][4]

Also on: Drives: GD20, GD200A, GD300, GD350. GD300: 'Parameters downloading fault'. Fault type [28].

Drive response: Drive trips and the TRIP light is on; fix the cause, then reset with STOP/RST, a fault reset input or a power cycle

Likely causes

  • Keypad cable loose, poorly connected or disconnected
  • Keypad cable too long, picking up strong interference
  • Data storage error in the keypad

First checks, in this order

  1. Check the surroundings and remove the interference source.
  2. Back up the data into the keypad again, then retry the download.
  3. Check that the control board software version of the copied parameters matches the drive you download to (GD350).
  4. If it persists, replace the hardware through INVT maintenance service.

ETH1: To-ground short-circuit fault 1

Hits OEE: Availability

What it means: The drive has detected a short circuit from its output to ground. INVT gives ETH1 and ETH2 the same causes and solutions.[1][2][3][4]

Also on: Drives: GD20, GD200A, GD300, GD350. GD300: 'Grounding shortcut fault 1'. Fault type [32].

Drive response: Drive trips and the TRIP light is on; fix the cause, then reset with STOP/RST, a fault reset input or a power cycle

Likely causes

  • The drive output is short circuited to ground
  • Fault in the current detection circuit
  • The motor power set in the drive differs sharply from the drive power

First checks, in this order

  1. Check the motor and motor wiring for a short to ground.
  2. Check that the motor power parameters (P02 group on GD20) match the motor actually used, and set the motor parameters correctly.
  3. If the wiring is good, the Hall component or the main control board may need replacing (INVT service).

ETH2: To-ground short-circuit fault 2

Hits OEE: Availability

What it means: The drive has detected a short circuit from its output to ground. INVT gives ETH1 and ETH2 the same causes and solutions.[1][2][3][4]

Also on: Drives: GD20, GD200A, GD300, GD350. GD300: 'Grounding shortcut fault 2'. Fault type [33].

Drive response: Drive trips and the TRIP light is on; fix the cause, then reset with STOP/RST, a fault reset input or a power cycle

Likely causes

  • The drive output is short circuited to ground
  • Fault in the current detection circuit
  • The motor power set in the drive differs sharply from the drive power

First checks, in this order

  1. Check the motor and motor wiring for a short to ground.
  2. Check that the motor power parameters (P02 group on GD20) match the motor actually used, and set the motor parameters correctly.
  3. If the wiring is good, the Hall component or the main control board may need replacing (INVT service).

dEu: Speed deviation fault

Hits OEE: Availability

What it means: The speed deviation has stayed above the detection value for longer than the detection time (GD350: P11.14, default 10.0 %, and P11.15, default 2.0 s; 0.0 s turns the protection off).[1][3][4]

Also on: Drives: GD20, GD300, GD350. Fault type [34]. Not in the GD200A V3.1 fault table.

Drive response: Drive trips and the TRIP light is on; fix the cause, then reset with STOP/RST, a fault reset input or a power cycle

Likely causes

  • Load too heavy, or the motor stalled

First checks, in this order

  1. Check that the load is normal and not stalled.
  2. Increase the speed deviation detection time, or lengthen the ACC and DEC time (GD350).
  3. Check the control parameters; GD350 adds: check the motor parameters, re-run autotuning and check the speed loop settings.

STo: Maladjustment fault

Hits OEE: Availability

What it means: The drive has detected maladjustment while controlling a synchronous motor. Not the same code as STO (Safe torque off) on the GD350.[1][3][4]

Also on: Drives: GD20, GD300, GD350. GD350: 'Mal-adjustment fault'. Fault type [35]. Not in the GD200A V3.1 fault table.

Drive response: Drive trips and the TRIP light is on; fix the cause, then reset with STOP/RST, a fault reset input or a power cycle

Likely causes

  • Synchronous motor control parameters set wrongly
  • Parameters from autotuning are inaccurate
  • The drive is not connected to the motor
  • Load exception or flux weakening application (GD350)

First checks, in this order

  1. Check that the load is normal.
  2. Check that the control parameters are set correctly; GD350 adds the motor parameters and counter EMF settings.
  3. Run motor parameter autotuning again (GD350).
  4. Increase the maladjustment detection time (P13.11 on GD300 and GD350, default 0.5 s on GD350; INVT says to raise it when load inertia is large, at the cost of slower response).
  5. On a GD350 with flux weakening, adjust the flux weakening coefficient and current loop parameters.

LL: Electronic underload fault

Warning: act before it becomes a stop

What it means: Underload pre-alarm: the output current has stayed below the underload pre-alarm level (P11.11) for longer than the detection time (P11.12).[1][2][3][4][5]

Also on: Drives: GD20, GD200A, GD300, GD350, GD10. Fault type [36]. The GD300 parameter list prints 'Undervoltage fault (LL)' for type 36, while its fault table says 'Electronic underload fault'.

Drive response: Set by P11.08 tens place on GD20 and GD200A: 0 (default) keeps running after the alarm, 2 or 3 stops on an underload fault

Likely causes

  • The load is below the underload pre-alarm threshold set in the drive

First checks, in this order

  1. Check the load.
  2. Check the underload pre-alarm threshold and time (P11.11, P11.12).

PoFF: System power off

Warning: act before it becomes a stop

What it means: Status display, listed by INVT under other states and not in the fault type list: the system is powered off or the DC bus voltage is too low.[1][2][3][4][5]

Also on: Drives: GD20, GD200A, GD300, GD350, GD10. GD200A, GD300, GD350 and GD10: 'System power failure'. See also UV.

Drive response: Shown as a state, not logged as a fault type

Likely causes

  • System power switched off, or DC bus voltage too low

First checks, in this order

  1. Check the grid (supply) conditions.

E-DP: PROFIBUS card communication timeout fault

Hits OEE: Availability

What it means: The PROFIBUS communication card is not exchanging data with the master (host controller or PLC).[3][4]

Also on: Drives: GD300, GD350. GD300: 'PROFIBUS communication fault'. Fault type [29]; reserved on GD20.

Drive response: Drive trips and the TRIP light is on; fix the cause, then reset with STOP/RST, a fault reset input or a power cycle

Likely causes

  • No data transmission between the communication card and the host controller or PLC (GD350)
  • Wrong communication address (GD300)
  • Terminal resistor on the card not switched in (INVT: 'corresponding resistor is not dialed') (GD300)
  • GSD file not set up properly on the master (GD300)
  • Too much interference from the surroundings (GD300)

First checks, in this order

  1. Check whether the communication card wiring is loose or disconnected.
  2. Check the related settings (address, terminal resistor, master GSD file).
  3. Check the surroundings and remove interference.

E-NET: Ethernet card communication timeout fault

Hits OEE: Availability

What it means: The Ethernet communication card is not exchanging data with the host controller.[3][4]

Also on: Drives: GD300, GD350. GD300: 'Ethernet communication fault'. Fault type [30]; reserved on GD20.

Drive response: Drive trips and the TRIP light is on; fix the cause, then reset with STOP/RST, a fault reset input or a power cycle

Likely causes

  • No data transmission between the communication card and the host controller (GD350)
  • Ethernet address not set correctly (GD300)
  • Ethernet communication not selected correctly (GD300)
  • Too much interference from the surroundings (GD300)

First checks, in this order

  1. Check whether the communication card wiring is loose or disconnected.
  2. Check the address setting and the communication method selection.
  3. Check the surroundings and remove interference.

E-CAN: CANopen card communication timeout fault

Hits OEE: Availability

What it means: The CANopen communication card is not exchanging data with the host controller or PLC.[3][4]

Also on: Drives: GD300, GD350. GD300: 'CANopen communication fault'. Fault type [31]; reserved on GD20.

Drive response: Drive trips and the TRIP light is on; fix the cause, then reset with STOP/RST, a fault reset input or a power cycle

Likely causes

  • No data transmission between the communication card and the host controller or PLC (GD350)
  • Poor connection (GD300)
  • Terminal resistor not switched in (GD300)
  • Communication baud rate not matched (GD300)
  • Too much interference from the surroundings (GD300)

First checks, in this order

  1. Check whether the communication card wiring is loose or disconnected.
  2. Check the terminal resistor setting and set the same baud rate on all nodes.
  3. Check the surroundings and remove interference.

STO: Safe torque off

Hits OEE: Availability

What it means: The safe torque off function has been triggered from outside: both STO inputs H1 and H2 opened, so the drive switched off its output and stopped. Not the same code as STo (Maladjustment fault).[4]

Also on: Drives: GD350. Fault type [40].

Drive response: Drive stops output at once; reset needed after the STO inputs close unless P08.52 = 1

Likely causes

  • The external NC safety contact wired to H1 and H2 opened (INVT: STO enabled by external forces)

First checks, in this order

  1. STO acts when the external NC contact wired to H1 and H2 opens; the drive runs again only when both inputs are closed.
  2. H1 and H2 are linked to +24V by a jumper from the factory; if the jumper was removed for STO use, check the safety wiring (shielded, within 25 m).
  3. With P08.52 = 0 (default, lock upon STO alarm) a reset is needed after the inputs close; with P08.52 = 1 the alarm clears by itself.

STL1: Exception occurred to safe circuit of channel 1

Hits OEE: Availability

What it means: The two STO inputs disagree: the drive found an exception in safety channel 1 (H1).[4]

Also on: Drives: GD350. Fault type [41].

Drive response: Drive trips and the TRIP light is on; fix the cause, then reset with STOP/RST, a fault reset input or a power cycle

Likely causes

  • One STO channel open and the other closed: H1 channel exception
  • Improper STO wiring, or a fault in the external STO switch
  • Hardware fault in the channel safety circuit

First checks, in this order

  1. Check that the STO terminal wiring is correct and firm.
  2. Check that the external STO switch works properly.
  3. If wiring and switch are good, the control board has to be replaced.

STL2: Exception occurred to safe circuit of channel 2

Hits OEE: Availability

What it means: The two STO inputs disagree: the drive found an exception in safety channel 2 (H2).[4]

Also on: Drives: GD350. Fault type [42].

Drive response: Drive trips and the TRIP light is on; fix the cause, then reset with STOP/RST, a fault reset input or a power cycle

Likely causes

  • One STO channel open and the other closed: H2 channel exception
  • Improper STO wiring, or a fault in the external STO switch
  • Hardware fault in the channel safety circuit

First checks, in this order

  1. Check that the STO terminal wiring is correct and firm.
  2. Check that the external STO switch works properly.
  3. If wiring and switch are good, the control board has to be replaced.

STL3: Exception occurred to both channel 1 and channel 2

Hits OEE: Availability

What it means: The drive found an exception in both STO safety channels (H1 and H2).[4]

Also on: Drives: GD350. Fault type [43].

Drive response: Drive trips and the TRIP light is on; fix the cause, then reset with STOP/RST, a fault reset input or a power cycle

Likely causes

  • Hardware fault in the STO circuit

First checks, in this order

  1. Replace the control board (INVT service).

OL3: Overtorque (CHF100A)

Warning: act before it becomes a stop

What it means: On the CHF100A, OL3 is the overtorque signal: the output torque reached the overtorque detection level (Pb.12) for longer than the detection time (Pb.13).[6]

Also on: Drives: CHF100A. Different meaning from OL3 'Electronic overload' on GD20, GD200A, GD300, GD350 and GD10.

Drive response: Pb.11 = 1 (default) or 3: drive keeps running and the TRIP light flashes; Pb.11 = 2 or 4: warning OL3 and the drive stops output

Likely causes

  • Acceleration too fast
  • Motor restarted while still rotating
  • Supply voltage too low
  • Load too heavy

First checks, in this order

  1. Increase the ACC time.
  2. Avoid restarting after stop while the motor still turns.
  3. Check the supply line voltage.
  4. Select a drive with a larger power rating.
  5. Set Pb.11 (overtorque selection) to a value that suits the application.

Log it, or the same alarm comes back

A fault trips the inverter and stops the motor, so in OEE terms it is a breakdown. Log the code, the machine and the minutes lost, every time; a pre-alarm (blinking TRIP light) is an early sign worth logging too.

  • Reason code: the code plus the drive, for example INVT GD20 OC1, mixer motor, so an overcurrent on every acceleration 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 OC1 mean on an INVT VFD?

OC1 is Overcurrent during acceleration: the drive tripped on overcurrent while the motor was speeding up. INVT lists the acceleration time being too short, low supply voltage, a drive too small for the load, a sudden load change, a short to ground or output phase loss, and strong interference. Increase the ACC time, check the supply, check the motor and cable for shorts, and check the output wiring. OC2 is the same fault during deceleration and OC3 at constant speed.

What is the difference between OUt1, OUt2 and OUt3 on an INVT drive?

They are the same protection on the three output phases of the inverter unit: OUt1 is the U phase, OUt2 the V phase and OUt3 the W phase (the CHF100A calls them IGBT Ph-U, Ph-V and Ph-W faults). INVT names too fast acceleration, a damaged IGBT module, interference, poorly connected drive wires and grounding problems as causes. Increase the ACC time, check the drive wires and remove interference; if the IGBT module is damaged the power unit has to be replaced.

How do I reset a fault on an INVT GD20 or GD200A?

First remove the cause. Then press STOP/RST on the keypad, use a digital input set to function 7 (Fault reset on GD20, Reset faults on GD200A), send a reset over communication, or switch the power off. Automatic reset can be set with P08.28 (number of resets) and P08.29 (interval). If the fault is still present the code stays on the display.

Where do I find the fault history on an INVT inverter?

On GD20, GD200A, GD300, GD350 and GD10, P07.27 is the present fault and P07.28 to P07.32 the five before it. P07.33 to P07.56 store the running frequency, output voltage and current, bus voltage, temperature and terminal states at the last three faults. On the CHF100A the last three faults are in P7.17 to P7.19.

Is STo the same as STO on an INVT drive?

No. STo is the Maladjustment fault on GD20, GD300 and GD350: control of a synchronous motor has lost step, from wrong motor parameters, inaccurate autotuning or no motor connected. STO, printed only in the GD350 manual here, is Safe torque off: both safety inputs H1 and H2 opened and the drive switched off its output.

What does PoFF mean on an INVT inverter display?

PoFF is System power off (System power failure on GD200A, GD300, GD350 and GD10). INVT lists it as a state, not a fault: the system is powered off or the DC bus voltage is too low. Check the supply. A supply voltage that is too low also gives UV, Bus undervoltage, which is a fault.

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.

  1. Goodrive20 Series VFD Manual (GD20 VFD Manual), V2.1, uploaded 2025-09-02, hosted by INVT (www.invt.com)
  2. Goodrive200A Series VFD Manual, V3.1 (English), uploaded 2026-08-05, hosted by INVT (www.invt.com)
  3. Goodrive300 Series VFD Manual, V3.6 (202110), uploaded 2022-04-21, hosted by INVT (www.invt.com)
  4. Goodrive350 Series High-Performance Multifunction VFD Manual, V2.1 (202601), uploaded 2026-03-27, hosted by INVT (www.invt.com)
  5. Goodrive10 Series Mini VFD Manual (GD10 VFD Manual), V2.9, uploaded 2025-09-02, hosted by INVT (www.invt.com)
  6. CHF100A Series High Performance Universal Inverter Manual (no version printed), uploaded 2020-07-06, hosted by INVT (www.invt.com)

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.

Related: Inovance drive fault codes · Delta VFD fault codes · LS Electric trip codes · VFD drive troubleshooting · electric motor

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 | Inovance: MD290, MD200, MD500, MD310

Related tools: full troubleshooting directory · OEE calculator · downtime cost · MTBF / MTTR · glossary

OEE essentials: OEE calculator · What is OEE · How to improve OEE · Six big losses · Availability · TEEP · Cost of downtime · OEE benchmark · Free OEE tracker · Free OEE software · How to track downtime · How to implement OEE · Light MES vs full MES