Lenze Drive Fault Codes
The fault codes of the Lenze drives people search most, SMVector (AC Tech), 8200 vector, 8400 and i500: what each one means, the likely causes, the first checks with the parameters to look at, and how to log it so it stops coming back.
How faults show on each drive
SMVector (AC Tech): when the drive trips, the display shows F. plus the fault code, for example F.OF, and the motor stops. Status and warning messages such as LC (fault lockout) or CL (current limit) show without the F. prefix. P500 lists the last 8 faults as n.xxx, where 1 is the newest and the F. is left off.
P550 to P552 give the same 8 faults with the hour each one happened and a counter for repeats. P197 = 1 clears the history. Fix the cause, then reset: a digital input set to Clear Fault (P121 to P124 = 20) resets the fault when it closes, and F.cFT clears by pressing the M (Mode) key twice. The drive only runs again after the fault is reset.
With P110 = 3 to 6 the drive tries 5 automatic restarts and then shows LC, which needs a manual reset. 8400 (StateLine C, HighLine C, TopLine C): the red DRV-ERR LED lights or blinks when a warning, trouble or fault is active. With the keypad plugged into diagnostic interface X6, status icons show Fault, Trouble, TroubleQSP or Warning.
The current error is shown as text plus a number in the form [type].[subject area].[ID], for example oC1 = xx.0123.00016, in C00165 and C00166, and the status-determining error in C00168.
The logbook (keypad menu Diagnostics > Logbook, or the Logbook button in EASY Starter or Engineer) keeps 15 entries on StateLine and 50 on HighLine and TopLine, with power-on time and a repeat counter, and it survives power loss.
Fault, Trouble, TroubleQSP and WarningLocked must be reset after the cause is fixed: device command C00002/19 = 1, the Reset error button in EASY Starter or Engineer, the FailReset bit in the control word, or a HIGH to LOW edge on terminal RFR in the Lenze preset terminal setup.
AutoFailReset (C00184 to C00189) can reset automatically. i500 (i510, i550): when an event is active the keypad shows the error text, the type letter (F = fault, T = trouble, W = warning) and the error code in hexadecimal. Faults and trouble stay on screen; warnings flash up every 2 seconds.
The error history buffer is parameter P155.00 in group 1 (Diagnostics): the last 32 events with text, type letter, error code, time and a repeat counter, entry 01 being the newest. Reset with the keypad STOP key once the cause is gone; the motor then stays stopped with KSTOP on the display until you press the RUN key.
You can also reset with the trigger assigned to Reset fault (P400.04), the EASY Starter Diagnostics tab, or the reset bit of the network control word. Some events (earth fault, short circuit) have a 1 to 2 s blocking time before a reset is accepted, and a few need mains switching.
Trouble clears by itself when the condition goes away. 8200 vector: a slowly blinking red LED means a fault is active; read it in C0161. The E82ZBC keypad shows the code, for example OC1, with the fault symbol. LU and OU show as messages. The history buffer is C0161 (active fault), C0162 (last fault), C0163 and C0164.
A TRIP needs a TRIP reset; with the Lenze setting C0170 = 0 that is mains switching, the keypad controller inhibit (stop) key, a LOW edge on terminal X3/28, or C0043 = 0 through a module. C0170 = 1 adds automatic TRIP reset after the delay in C0171; more than 8 automatic resets in 10 minutes trips rST. 9300 vector: a slowly blinking red LED means an active fault.
The history buffer C0168/1 to C0168/8 holds the fault numbers, C0169 the time and C0170 how often each happened. C0167 = 1 clears it. The first digit of the fault number is the response: 0 = TRIP, 1 = message, 2 = warning.
A TRIP switches off the outputs (the motor coasts) and needs a TRIP reset: the keypad XT EMZ9371 BC key sequence shown in the manual, C0043 = 0, bit 11 of control word C0135, or the AIF or CAN control word. The drive stays stopped after the reset. A message such as OU or LU clears by itself and the drive restarts automatically.
On 8400 the wait is 3 to 20 minutes depending on the unit, and on i500 the time is printed next to the warning symbol on the device label. Then measure to confirm the terminals are dead before you touch anything. The power terminals are also live whenever mains is on, even with the motor stopped or the drive inhibited.
On 8200 vector the relay outputs K11, K12 and K14 can still carry dangerous voltage. Do not cycle SMVector input power more than once every two minutes; on 8400, after 3 mains switchings within one minute, wait 9 minutes.
Sources: SMVector Operating Instructions EDBSV01 v22.0, Safety Information pp. 3 to 5; 8400 StateLine Operating Instructions DMS 1.2, 2.3 Residual hazards p. 8, and Reference manual DMS 16.1, Su03 p. 468; 8200 vector System Manual EDS82EV903, safety instructions pp. 23 and 98; 9300 vector System Manual EDSVF9333V, safety instructions p. 31.
I550 cabinet online documentation, Residual hazards. Follow lockout/tagout and your site's safe-work procedures, and check the manual for your exact model before you act.
Quick lookup
Faults stop the inverter and the machine it drives, so in OEE they are availability losses.
Type a code or a word (overcurrent, overvoltage, earth fault, overload) to filter the list. Click a code for its causes and first checks.
80 codes
| Code | Drive | Name |
|---|---|---|
| F.OF | SMVector | Output fault: Transistor fault |
| F.OF1 | SMVector | Output fault: Ground fault |
| F.HF | SMVector | High DC Bus Voltage fault |
| F.LF | SMVector | Low DC Bus Voltage fault |
| F.SF | SMVector | Single-Phase fault |
| F.PF | SMVector | Motor Overload fault |
| F.AF | SMVector | High Temperature fault |
| F.EF | SMVector | External fault |
| F.dbF | SMVector | Dynamic Braking fault |
| F.UF | SMVector | Start fault |
| F.rF | SMVector | Flying Restart fault |
| F.ntF | SMVector | Module communication fault |
| F.nF1 to F.nF9 | SMVector | Network Faults |
| F.JF | SMVector | Remote keypad fault |
| F.Fnr | SMVector | Control Configuration Fault |
| F.FoL | SMVector | TB25 (4-20 mA signal) Threshold fault |
| F.FAU | SMVector | TB5 (0-10V signal) Threshold fault |
| F.AL | SMVector | Assertion Level fault |
| F.IL | SMVector | Digital Input Configuration fault (P121...P124) |
| F.nId | SMVector | No Motor ID fault |
| F.F1 | SMVector | EPM fault |
| F.F2 to F.F13 | SMVector | Internal faults |
| F.CF | SMVector | Control fault |
| F.cF | SMVector | Incompatible EPM fault |
| F.cFT | SMVector | Forced Translation fault |
| F.bF | SMVector | Personality fault |
| LC | SMVector | Fault Lockout |
| oC1 | 8400 | Power section - short circuit |
| oC2 | 8400 | Power section - earth fault |
| oC7 | 8400 | Motor overcurrent |
| oC5 | 8400 | Ixt overload |
| oC6 | 8400 | I2xt motor overload |
| oC11 | 8400 | Clamp operation active |
| OU | 8400 | DC bus overvoltage |
| LU | 8400 | DC bus undervoltage |
| oH1 | 8400 | Heatsink overtemperature |
| oH3 | 8400 | Motor temperature (X106) triggered |
| LP1 | 8400 | Motor phase failure |
| Su02 | 8400 | One mains phase is missing |
| Su03 | 8400 | Too frequent mains switching |
| Su06 | 8400 | Power input overload |
| PS01 | 8400 | No memory module |
| PS02 | 8400 | Par. set invalid |
| PS03 | 8400 | Par. set device invalid |
| CE4 | 8400 | CAN Bus Off |
| CA0F | 8400 | CAN control word |
| CI01 | 8400 | Module missing/incompatible |
| An01 | 8400 | AIN1_I < 4 mA |
| dH10 | 8400 | Fan failure |
| Id1 | 8400 | Motor data identification error |
| oS2 | 8400 | Max. motor speed |
| dF10 | 8400 | AutoTrip reset |
| Sd3 | 8400 | Open circuit HTL 2-fold or 4-fold |
| Sd2 | 8400 | Resolver open circuit |
| Sd7 | 8400 | Error encoder communication |
| Ck01 | 8400 | Pos. HW limit switch |
| OC1 | 8200 vector | Short circuit |
| OC2 | 8200 vector | Earth fault |
| OC3 | 8200 vector | Controller overload during acceleration or short circuit |
| OC4 | 8200 vector | Controller overload during deceleration |
| OC6 | 8200 vector | Motor overload (I2 x t overload) |
| OUE | 8200 vector | DC-bus overvoltage |
| LU | 8200 vector | DC-bus undervoltage |
| OH | 8200 vector | Heatsink temperature > +85 °C |
| EEr | 8200 vector | External fault (TRIP-SET) |
| 0x2250 | i500 | CiA: Continuous over current (internal) |
| 0x2320 | i500 | Short circuit or earth leakage at the motor end |
| 0x2340 | i500 | Short circuit at the motor end |
| 0x2350 | i500 | CiA: i²xt overload (thermal state) |
| 0x3120 | i500 | Mains phase fault |
| 0x3210 | i500 | Fault - DC bus overvoltage |
| 0x3220 | i500 | Fault - DC bus undervoltage |
| 0x4210 | i500 | Fault - Power unit overtemperature |
| 0x4310 | i500 | Motor overtemperature |
| 0x7180 | i500 | Motor overcurrent |
| OC1 | 9300 | Overcurrent in motor cable |
| OC2 | 9300 | Motor cable earth fault |
| OU | 9300 | Overvoltage in the DC bus |
| LU | 9300 | Undervoltage in the DC bus |
| OH | 9300 | Heatsink temperature > +90 °C |
Each code: causes and first checks
F.OF: Output fault: Transistor fault
Hits OEE: AvailabilityWhat it means: The drive tripped because of a fault on its output stage, usually a short on the output or a severe overload that pulled too much current.[1]
Likely causes
- Short circuit on the drive output or in the motor cable
- Acceleration time too short
- Severe motor overload from a mechanical problem, or drive and motor too small for the application
- Boost values set too high
- Too much capacitive charging current from the motor cable
- Failed output transistor
First checks, in this order
- Check the motor and motor cable for shorts.
- Increase the acceleration time (P104, P125).
- Check the machine for jams and confirm the drive and motor are sized for the load.
- Lower the boost values (P168, P169).
- Use shorter or low-capacitance motor cable, or install a reactor between drive and motor.
- With flying restart (P110 = 5 or 6), try P110 = 7 or 8 if the drive trips on F.OF.
- If the output transistor has failed, contact Lenze technical support.
F.OF1: Output fault: Ground fault
Hits OEE: AvailabilityWhat it means: The drive sees current flowing to ground on the output side, from a grounded motor phase or from cable leakage.[1]
Likely causes
- Grounded motor phase
- Excessive capacitive charging current of the motor cable
First checks, in this order
- Check the motor and motor cable for a phase shorted to ground.
- Use a shorter motor cable with lower charging current.
F.HF: High DC Bus Voltage fault
Hits OEE: AvailabilityWhat it means: DC bus voltage went too high, usually from high mains voltage or from the motor feeding energy back while slowing down.[1]
Likely causes
- Mains voltage too high
- Deceleration time too short, or too much regenerated energy from the motor
First checks, in this order
- Check the mains voltage and the line voltage selection P107.
- Increase the active deceleration time (P105, P126, P127).
- Install the dynamic braking option.
- If you see deC (Decel Override) before the trip, the drive was already holding off deceleration to avoid this fault.
F.LF: Low DC Bus Voltage fault
Hits OEE: AvailabilityWhat it means: DC bus voltage dropped too low because the incoming mains voltage is too low.[1]
Likely causes
- Mains voltage too low
First checks, in this order
- Check the mains voltage at the drive input terminals, also while the motor is under load.
F.SF: Single-Phase fault
Hits OEE: AvailabilityWhat it means: One phase of the three-phase mains supply has been lost.[1]
Likely causes
- A mains phase is missing (blown fuse, open breaker pole, loose connection)
First checks, in this order
- Check the mains voltage on all three input phases.
F.PF: Motor Overload fault
Hits OEE: AvailabilityWhat it means: The drive's motor overload protection tripped because the motor carried too much load for too long.[1]
Likely causes
- Excessive motor load for too long
- P108 set wrong for the motor
- Drive or motor too small for the application
First checks, in this order
- Check P108 (Motor Overload): P108 = motor current rating x 100 / SMV output rating, and never above the motor nameplate current.
- Verify the drive and motor are sized for the application.
- Check the machine for jams or extra friction.
F.AF: High Temperature fault
Hits OEE: AvailabilityWhat it means: The drive is too hot inside.[1]
Likely causes
- Drive load too high
- Poor cooling (hot cabinet, blocked airflow)
First checks, in this order
- Reduce the drive load.
- Improve cooling around the drive.
- Read the heatsink temperature in P512.
F.EF: External fault
Hits OEE: AvailabilityWhat it means: A digital input set up as an external fault input has tripped the drive.[1]
Likely causes
- An input set to External Fault (P121 to P124 = 21, normally closed) has opened
- An input set to Inverse External Fault (P121 to P124 = 22, normally open) has closed
First checks, in this order
- Find and correct the external fault condition (the device wired to that input).
- Make sure the input is set correctly for a normally closed or normally open circuit.
F.dbF: Dynamic Braking fault
Hits OEE: AvailabilityWhat it means: The dynamic braking resistors are overheating.[1]
Likely causes
- Deceleration too fast for the braking resistor
- Mains voltage too high
First checks, in this order
- Increase the active deceleration time (P105, P126, P127).
- Check the mains voltage and P107.
F.UF: Start fault
Hits OEE: AvailabilityWhat it means: A start command was already present when power was applied, and the start method does not allow that.[1]
Likely causes
- Start command present at power-up with P110 = 0 or 2
First checks, in this order
- Wait at least 2 seconds after power-up before applying the start command.
- Consider a different start method in P110.
F.rF: Flying Restart fault
Hits OEE: AvailabilityWhat it means: During a flying restart the drive could not lock onto the spinning motor.[1]
Likely causes
- Drive unable to synchronize with the motor during a restart attempt (P110 = 5 or 6)
First checks, in this order
- Check the motor and the load.
- For 2-pole motors that need a flying restart, P110 = 7 or 8 (Type 2) is available.
F.ntF: Module communication fault
Hits OEE: AvailabilityWhat it means: Communication between the drive and its plug-in network module has failed.[1][2]
Likely causes
- Network module not seated or poorly connected
- Connection between module and drive not made
First checks, in this order
- Check the module connection to the drive.
- Power down, reseat the module, and power up again.
F.nF1 to F.nF9: Network Faults
Hits OEE: AvailabilityWhat it means: The installed network module reported a network fault; the exact meaning of each number depends on the module.[1][2]
Likely causes
- Network communication lost while the drive is under network control
- Fault reported by the network module (see the module's manual)
First checks, in this order
- Look up the code in the manual for the installed network module.
- For the Modbus module, a network time-out fault means communication was lost under network control; check the time-out settings P425 and P426.
F.JF: Remote keypad fault
Hits OEE: AvailabilityWhat it means: The remote keypad has been disconnected.[1]
Likely causes
- Remote keypad cable unplugged or damaged
First checks, in this order
- Check the remote keypad connections.
F.Fnr: Control Configuration Fault
Hits OEE: AvailabilityWhat it means: The start control source is set to remote keypad or network, but the matching communication is not set up.[1]
Likely causes
- P100 = 2 or 5 (remote keypad control) but remote keypad communication not enabled
- P100 = 3 (network only) but network communication not set up
First checks, in this order
- For remote keypad control, set P400 = 1 or P600 = 1.
- For network control, set P400 or P600 to a valid network protocol.
F.FoL: TB25 (4-20 mA signal) Threshold fault
Hits OEE: AvailabilityWhat it means: The 4 to 20 mA signal on terminal TB-25 dropped below the level set in P164.[1]
Likely causes
- Broken or loose 4 to 20 mA signal wire
- Signal source failed or below its minimum
First checks, in this order
- Check the signal and the signal wire at TB-25 (actual value in P521).
- Check parameters P163 and P164.
F.FAU: TB5 (0-10V signal) Threshold fault
Hits OEE: AvailabilityWhat it means: The 0 to 10 V signal on terminal TB5 dropped below the level set in P158.[1]
Likely causes
- Broken or loose 0 to 10 V signal wire
- Signal source failed or below its minimum
First checks, in this order
- Check the signal and the signal wire at TB5 (actual value in P520).
- Check parameters P157 and P158.
F.AL: Assertion Level fault
Hits OEE: AvailabilityWhat it means: The input assertion level setting (switch and P120) does not match, or was changed while the drive was running.[1]
Likely causes
- Assertion Level switch changed during operation
- P120 changed during operation
- P100 or P121 to P124 set to a non-zero value while P120 does not match the Assertion Level switch
- Reset to 50 or 60 Hz defaults, which sets P120 to 2 (High)
First checks, in this order
- Set the Assertion Level switch and P120 for the type of input devices used, before setting P100 or P121 to P124.
- After a reset to defaults (P199), check P120 again.
F.IL: Digital Input Configuration fault (P121...P124)
Hits OEE: AvailabilityWhat it means: The digital inputs TB-13A to TB-13D are programmed with settings that conflict with each other.[1]
Likely causes
- More than one digital input set to the same function
- Only one input set for the MOP function (Up or Down)
- PID mode with setpoint and feedback on the same analog signal
- One input set to 10 and another to 11 to 14, or one set to 11 or 12 and another to 13 or 14
- PID enabled in Vector Torque mode (P200 = 1 or 2 with P300 = 5)
First checks, in this order
- Use each input function only once (settings 0 and 3 are the exceptions).
- Set one input to MOP Up and another to MOP Down.
- Change the PID setpoint reference (P121 to P124) or the feedback source (P201).
- Reconfigure the digital inputs so the settings do not conflict.
- Do not use PID in Vector Torque mode.
F.nId: No Motor ID fault
Hits OEE: AvailabilityWhat it means: A start was attempted in Vector or Enhanced V/Hz mode before the motor auto-calibration was done.[1]
Likely causes
- Drive mode P300 set to a vector or enhanced V/Hz mode without motor auto-calibration
First checks, in this order
- Enter the motor data and run the motor auto-calibration (P300 to P399, auto-calibration in P399).
- Check the drive mode setting in P300.
F.F1: EPM fault
Hits OEE: AvailabilityWhat it means: The EPM memory module is missing or defective.[1]
Likely causes
- EPM not installed
- EPM defective
First checks, in this order
- Power down and replace the EPM.
F.F2 to F.F13: Internal faults
Hits OEE: AvailabilityWhat it means: The drive detected an internal fault.[1]
Likely causes
- Internal drive fault
First checks, in this order
- Note the code and the fault history in P500.
- Contact Lenze technical support.
F.CF: Control fault
Hits OEE: AvailabilityWhat it means: The installed EPM memory module is blank or its data is corrupted.[1]
Likely causes
- Blank EPM installed
- Corrupted EPM data
First checks, in this order
- Cycle power.
- Power down and install an EPM with valid data.
- Reset the drive to defaults (P199 = 3 or 4) and reprogram it.
- If the problem persists, contact Lenze technical support.
F.cF: Incompatible EPM fault
Hits OEE: AvailabilityWhat it means: The installed EPM holds data from an incompatible parameter version.[1]
Likely causes
- EPM taken from a drive with an incompatible parameter version
First checks, in this order
- Power down and install an EPM with valid data.
- Reset the drive to defaults (P199 = 3 or 4) and reprogram it.
- If the EPM holds valid data from an older software version (status cE), convert it with P199 = 5.
- If the problem persists, contact Lenze technical support.
F.cFT: Forced Translation fault
Hits OEE: AvailabilityWhat it means: An EPM from an older drive was put into a newer drive.[1]
Likely causes
- EPM moved from an old drive to a new drive
First checks, in this order
- Press the M (Mode) button twice to reset.
- Check the parameter settings afterwards.
F.bF: Personality fault
Hits OEE: AvailabilityWhat it means: The drive found a problem with its hardware identity (personality).[1]
Likely causes
- Drive hardware fault
- EPM data does not suit the drive
First checks, in this order
- Cycle power.
- Power down and install an EPM with valid data.
- Reset the drive to defaults (P199 = 3 or 4) and reprogram it.
- If the problem persists, contact Lenze technical support.
LC: Fault Lockout
Warning: act before it becomes a stopWhat it means: The drive tried 5 automatic restarts after a fault and all of them failed, so it locked out.[1]
Drive response: Warning
Likely causes
- Auto-restart enabled (P110 = 3 to 6) and the original fault keeps coming back
First checks, in this order
- Reset the drive manually.
- Check the fault history (P500) and correct the fault that caused the restarts.
oC1: Power section - short circuit
Hits OEE: AvailabilityWhat it means: The drive detected a short circuit between motor phases and switched off its output to protect itself (error number xx.0123.00016).[3][5][6]
Also on: 8400 HighLine C and TopLine C (same code, number and text)
Likely causes
- Incorrect motor connection (the most common cause)
- Drive too small for the motor load with the current limit (Imax) controller set wrong
- Current limit controller dynamics set too high
First checks, in this order
- Check the motor connections and the plug connector on the drive.
- Use only permitted combinations of drive power and motor power.
- Do not set the dynamics of the current limit controller too high.
oC2: Power section - earth fault
Hits OEE: AvailabilityWhat it means: The drive detected an earth fault on a motor phase and switched off its output (error number xx.0123.00017).[3][5][6]
Also on: 8400 HighLine C and TopLine C (same code, number and text)
Likely causes
- Incorrect motor connection (the most common cause)
- Leakage current to PE from a wrong motor filter, cable length or cable type
- Motor filter with extra +UG and -UG terminals on drives of 3 kW and up
- Shielded motor cable longer than 50 m
First checks, in this order
- Check the motor connections and the plug connector on the drive.
- Use motor filters, cable lengths and cable types recommended by Lenze.
- With motor filters that have +UG and -UG terminals on drives of 3 kW and up (firmware V05.01.00 and later), set the earth fault filter time C01770 to 250 ms, which turns off earth fault detection during operation.
- With motor cables longer than 50 m (firmware V05.01.00 and later), increase the filter time in C01770.
oC7: Motor overcurrent
Hits OEE: AvailabilityWhat it means: The instantaneous motor current went above the limit set in C00939.[3][5][6]
Also on: 8400 HighLine C and TopLine C (same code, number and text)
Likely causes
- Load too high for the installed drive power
- Limit in C00939 set too low
First checks, in this order
- Check the load against the installed drive power.
- Check the limit value in C00939.
oC5: Ixt overload
Warning: act before it becomes a stopWhat it means: The drive's own Ixt overload check reached its threshold (100% by default, set in C00123); the response is set in C00604.[3][5][6]
Also on: 8400 HighLine C and TopLine C (same code, number and text)
Drive response: Warning
Likely causes
- Drive undersized for the motor load
- Load cycles exceed what the drive is rated for
First checks, in this order
- Check the drive sizing against the motor load and technical data.
- Reduce the motor load cycles.
- Watch device utilization in C00064.
oC6: I2xt motor overload
Warning: act before it becomes a stopWhat it means: The motor thermal model says the motor is overloaded; the threshold is C00120 and the response is set in C00606.[3][4][5][6]
Also on: 8400 HighLine C and TopLine C (same code, number and text)
Drive response: Warning
Likely causes
- Motor load too high or too long
- Motor with a separate cooling fan (only self-ventilated motors can be modeled)
- Vmin boost too high with VFCplus control
First checks, in this order
- If the motor is not self-ventilated, set C00606 to 0: No Reaction.
- Check the load requirements and the drive sizing.
- With VFCplus control, check the Vmin boost in C00016.
oC11: Clamp operation active
Hits OEE: AvailabilityWhat it means: The fast CLAMP current limit kept switching the output off; constant clamping ends in an overload trip.[3][5][6]
Also on: 8400 HighLine C and TopLine C (same code, number and text)
Likely causes
- Setpoint changes too fast (ramps too short)
- Motor load too high
First checks, in this order
- Make the setpoint changes less aggressive (longer ramps).
- Reduce the motor load.
OU: DC bus overvoltage
Hits OEE: AvailabilityWhat it means: DC bus voltage is too high, so the drive switches off its output; if it lasts longer than the time in C00601 it becomes a Fault.[3][5][6]
Also on: 8400 HighLine C and TopLine C (same code, number and text)
Drive response: Trouble
Likely causes
- Too much regenerative energy from the load (braking, overhauling load)
- Deceleration too fast for the braking setup
- Brake resistor missing or too small
First checks, in this order
- Reduce the regenerative load or lengthen the deceleration.
- Use a brake resistor, a regenerative power supply or a DC bus connection.
- Select a braking method in C00175 that holds the ramp at the brake chopper threshold.
- Use C00142 if the drive should only restart after a controller inhibit.
LU: DC bus undervoltage
Hits OEE: AvailabilityWhat it means: DC bus voltage is too low for the motor control, so the drive switches off its output.[3][5][6]
Also on: 8400 HighLine C and TopLine C (same code, number and text)
Drive response: Trouble
Likely causes
- Mains supply off or too low
- Insufficient supply through the DC bus connection
First checks, in this order
- Switch on the mains or make sure the DC bus supply is adequate.
- Check the auto-start setting in C00142 if the drive restarts unexpectedly.
oH1: Heatsink overtemperature
Hits OEE: AvailabilityWhat it means: The heatsink is hotter than the fixed limit of 90 °C.[3][5][6]
Also on: 8400 HighLine C and TopLine C (same code, number and text)
Likely causes
- Cabinet or ambient temperature too high
- Dirty fan or blocked ventilation slots
First checks, in this order
- Check the control cabinet temperature.
- Clean the filter and the drive.
- Clean or replace the fan.
- Read the heatsink temperature in C00061.
oH3: Motor temperature (X106) triggered
Hits OEE: AvailabilityWhat it means: The motor temperature input at connector X106 (terminals T1 and T2) tripped; the response is set in C00585.[3][5][6]
Also on: 8400 HighLine C and TopLine C (same code, number and text)
Likely causes
- Motor overheated so its thermal contact opened
- Open circuit or loose contact on the T1 and T2 wiring
First checks, in this order
- Check the motor temperature monitoring circuit.
- Check the motor cooling.
- Check the T1 and T2 terminals for an open circuit or loose contact.
LP1: Motor phase failure
Logged only by default: act before it becomes a stopWhat it means: A motor phase carried less current during one half-wave than the threshold in C00599. The Lenze default response is No Reaction; set the response in C00597.[3][5][6]
Also on: 8400 HighLine C and TopLine C (same code, number and text)
Drive response: No reaction (Lenze default; can be changed)
Likely causes
- Open or loose motor phase connection
- Threshold in C00599 set too high for a small motor
First checks, in this order
- Check the motor connections, the plug connector on the drive and the motor terminal box.
- Check the trigger threshold in C00599.
Su02: One mains phase is missing
Warning: act before it becomes a stopWhat it means: One phase of the three-phase supply has failed; the response is set in C00565.[3][5][6]
Also on: 8400 HighLine C and TopLine C (same code, number and text)
Drive response: Warning
Likely causes
- Blown fuse, open breaker pole or loose mains connection
First checks, in this order
- Check the mains connection at terminal X100.
Su03: Too frequent mains switching
Hits OEE: AvailabilityWhat it means: The power section was switched on and off too often, so the drive blocks enable to protect its charging circuit.[3][5][6]
Also on: 8400 HighLine C and TopLine C (same code, number and text)
Likely causes
- Mains switched on and off too often (for example by a contactor each cycle)
- Power supply module in a DC bus connection wired after the charging circuit
First checks, in this order
- Acknowledge this error by switching the mains.
- After 3 mains switchings within one minute, wait 9 minutes; switching every 3 minutes is allowed.
- Leave the mains off long enough for the charging circuit to cool.
Su06: Power input overload
Hits OEE: AvailabilityWhat it means: The hardware overload detection in the mains input tripped (fitted on 7.5, 11, 15, 30, 37 and 45 kW units).[3][5][6]
Also on: 8400 HighLine C and TopLine C (same code, number and text)
Likely causes
- Running on 2 phases because one mains phase is missing
- Insufficient cooling of the drive
First checks, in this order
- Check that all mains phases are connected.
- Make sure the drive is cooled properly.
PS01: No memory module
Warning: act before it becomes a stopWhat it means: The memory module is missing or not snapped in place.[3][5][6]
Also on: 8400 HighLine C and TopLine C (same code, number and text)
Drive response: Warning
Likely causes
- Memory module not plugged in
- Memory module not seated correctly
First checks, in this order
- Plug the memory module into its slot on the drive.
- Check that it is seated correctly.
PS02: Par. set invalid
Hits OEE: AvailabilityWhat it means: The parameter set stored in the memory module is invalid.[3][5][6]
Also on: 8400 HighLine C and TopLine C (same code, number and text)
Likely causes
- Power lost while the parameter set was being saved
- Memory module from a drive with newer firmware (compare C00099) or from another device type, for example 8400 BaseLine
First checks, in this order
- Clear the error by loading the Lenze setting with device command C00002/1 = 1, then reload or re-enter your parameters.
- Do not switch off power while parameters are being saved.
- To move a parameter set to a drive with lower firmware, use the keypad copy parameter set function.
PS03: Par. set device invalid
Hits OEE: AvailabilityWhat it means: The parameter set in the memory module does not fit this drive.[3][5][6]
Also on: 8400 HighLine C and TopLine C (same code, number and text)
Likely causes
- Memory module from an 8400 HighLine plugged into an 8400 StateLine
- Parameter set saved by a higher firmware version than this drive
First checks, in this order
- Check memory module compatibility: StateLine V2.0 to V3.0 and StateLine V2.0 to HighLine V2.0 work; HighLine to StateLine and StateLine V3.0 to an older StateLine do not.
- If the set is from a lower version, it only shows as information; save the parameter set again to clear it.
CE4: CAN Bus Off
Logged only by default: act before it becomes a stopWhat it means: The onboard CAN interface went to bus-off. The Lenze default response is No Reaction; set it in C00592/2.[3][5][6]
Also on: 8400 HighLine C and TopLine C (same code, number and text)
Drive response: No reaction (Lenze default; can be changed)
Likely causes
- Too many faulty telegrams received
- Damaged cable or loose contact
- Two nodes with the same ID
- Electrical interference (EMC)
First checks, in this order
- Check the wiring and the bus terminating resistors.
- Set the same baud rate on every node.
- Give every node a different ID.
- Remove sources of electrical interference.
CA0F: CAN control word
Hits OEE: AvailabilityWhat it means: The controller on the CAN bus set bit 14 (SetFail) in the CAN control word, which trips the drive on purpose.[3][5][6]
Also on: 8400 HighLine C and TopLine C (same code, number and text)
Likely causes
- PLC or master on the CAN bus commanded a fault through bit 14 of the control word
First checks, in this order
- Trace which signal on the CAN bus sets bit 14 (SetFail) and why.
- For fieldbus modules the same function shows as CE0F (MCI control word).
CI01: Module missing/incompatible
Logged only by default: act before it becomes a stopWhat it means: The optional communication module was removed, has a connection problem, or does not match the drive. The response is set in C01501/2.[3][5][6]
Also on: 8400 HighLine C and TopLine C (same code, number and text)
Drive response: No reaction (Lenze default; can be changed)
Likely causes
- Communication module removed or not plugged in correctly
- Module or drive firmware out of date (incompatible)
First checks, in this order
- Check the connection between the communication module and the drive.
- Check that the module is plugged in correctly.
- If they are incompatible, contact Lenze about the module or drive firmware.
An01: AIN1_I < 4 mA
Hits OEE: AvailabilityWhat it means: Open-circuit monitoring on analog input 1 tripped while it is set as a 4 to 20 mA current loop (C00034/1 = 2); the response is set in C00598/1.[3][5][6]
Also on: 8400 HighLine C and TopLine C (same code, number and text)
Drive response: Trouble, quick stop
Likely causes
- Broken wire on analog input terminal X3/A1I
- Signal source below its minimum current
First checks, in this order
- Check the wiring of analog input X3/A1I for an open circuit.
- Check the minimum current of the signal source.
dH10: Fan failure
Warning: act before it becomes a stopWhat it means: The drive fan has failed: either its short-circuit check or its speed monitoring tripped. The response is set in C00566.[3][5][6]
Also on: 8400 HighLine C and TopLine C (same code, number and text)
Drive response: Warning
Likely causes
- Short circuit in the fan connection
- Fan blocked, dirty or worn out
First checks, in this order
- Check the fan for a short circuit.
- Clean the fan.
- Check fan running time in C00180/2.
Id1: Motor data identification error
Hits OEE: AvailabilityWhat it means: An error happened during the motor parameter identification.[3][5][6]
Also on: 8400 HighLine C and TopLine C (same code, number and text)
Likely causes
- Interrupted motor cable
- Power section switched off during the identification
- Implausible start parameters (motor nameplate data)
First checks, in this order
- Check the motor connections, the plug connector on the drive and the motor terminal box.
- Correct the motor nameplate data used for the identification.
- Make sure the drive has a stable power supply during identification.
oS2: Max. motor speed
Hits OEE: AvailabilityWhat it means: The motor reached its maximum permitted speed.[3][5][6]
Also on: 8400 HighLine C and TopLine C (same code, number and text)
Likely causes
- Setpoint above the permitted motor speed
- Overhauling load driving the motor too fast
First checks, in this order
- Limit the setpoint to the maximum permitted motor speed.
- If needed, adjust the maximum motor speed in C00965.
dF10: AutoTrip reset
Hits OEE: AvailabilityWhat it means: The automatic fault reset (AutoFailReset) ran too many times without success; the limit is C00186 and this response is set in C00189.[3][5][6]
Also on: 8400 HighLine C and TopLine C (same code, number and text)
Likely causes
- A recurring fault that the automatic reset keeps clearing
First checks, in this order
- Check the logbook for the fault that triggered the automatic resets.
- Fix that cause, then reset the error manually (C00002/19 = 1).
Sd3: Open circuit HTL 2-fold or 4-fold
Hits OEE: AvailabilityWhat it means: The HTL encoder signal is missing; the response is set in C00586.[3][5][6]
Also on: 8400 HighLine C and TopLine C (same code, number and text)
Likely causes
- HTL encoder cable broken
- HTL encoder defective
- Very hard acceleration or starting against a blocked shaft, for example a closed holding brake
First checks, in this order
- Check the HTL encoder cable and terminals.
- Check the HTL encoder.
- If no HTL encoder is used, set C00586 to 0: No Reaction.
Sd2: Resolver open circuit
Hits OEE: AvailabilityWhat it means: TopLine only: the resolver signal is missing; the response is set in C00603/2.[6]
Likely causes
- Electrical interference on the encoder signals (EMC)
- Resolver cable broken
- Resolver defective
First checks, in this order
- Check the resolver cable.
- Check the resolver.
- If no resolver is used, set C00603/2 to 0: No Reaction.
Sd7: Error encoder communication
Hits OEE: AvailabilityWhat it means: TopLine only: communication with the encoder failed; the response is set in C00603/4.[6]
Likely causes
- Encoder cable broken
- Encoder defective
- Wrong encoder parameter settings
First checks, in this order
- Check the encoder cable.
- Check the encoder.
- Check the encoder parameter settings.
Ck01: Pos. HW limit switch
Hits OEE: AvailabilityWhat it means: HighLine and TopLine: the hardware limit switch in the positive travel direction tripped (input bLimitSwitchPos went FALSE); the response is set in C00595/1.[5][6]
Also on: 8400 HighLine C (same code, number and text)
Drive response: Trouble, quick stop
Likely causes
- Axis ran onto the positive limit switch
- Limit switch or its wiring faulty (the input is fail-safe, so an open wire also trips)
First checks, in this order
- Reset the error and move the axis back off the limit switch.
- Check the limit switch and its wiring.
OC1: Short circuit
Hits OEE: AvailabilityWhat it means: TRIP on a short circuit at the output (LECOM error number 11). The outputs switch off and the motor coasts until the TRIP is reset.[9]
Drive response: TRIP
Likely causes
- Short circuit in the motor cable or motor
- Short in the brake resistor or its cable
- Capacitive charging current of the motor cable too high
First checks, in this order
- Find the cause of the short circuit; check the motor cable.
- Check the brake resistor and the cable to it.
- Use a shorter or low-capacitance motor cable.
OC2: Earth fault
Hits OEE: AvailabilityWhat it means: TRIP because a motor phase has contact to earth (LECOM error number 12).[9]
Drive response: TRIP
Likely causes
- A motor phase shorted to earth
- Capacitive charging current of the motor cable too high
First checks, in this order
- Check the motor and the motor cable.
- Use a shorter or low-capacitance motor cable.
- For test purposes only, the manual allows switching off earth fault detection.
OC3: Controller overload during acceleration or short circuit
Hits OEE: AvailabilityWhat it means: TRIP because the drive was overloaded while accelerating, or because of a short circuit (LECOM error number 13).[9]
Drive response: TRIP
Likely causes
- Acceleration time (C0012) too short
- Defective motor cable
- Interturn fault in the motor
First checks, in this order
- Increase the acceleration time (C0012).
- Check the drive sizing.
- Check the wiring.
- Check the motor.
OC4: Controller overload during deceleration
Hits OEE: AvailabilityWhat it means: TRIP because the drive was overloaded while decelerating (LECOM error number 14).[9]
Drive response: TRIP
Likely causes
- Deceleration time (C0013) too short
- External brake resistor too small
First checks, in this order
- Increase the deceleration time (C0013).
- Check the sizing of the external brake resistor.
OC6: Motor overload (I2 x t overload)
Hits OEE: AvailabilityWhat it means: TRIP because the motor thermal model says the motor is overloaded (LECOM error number 16).[9]
Drive response: TRIP
Likely causes
- Continuous current above what the motor allows
- Frequent or too long acceleration
First checks, in this order
- Check the drive and motor sizing.
- Check the setting of C0120.
OUE: DC-bus overvoltage
Hits OEE: AvailabilityWhat it means: TRIP on DC bus overvoltage (LECOM error number 22), usually from braking energy. OU with the message symbol is the non-trip version, caused by high mains voltage; C0310 chooses message or TRIP.[9]
Drive response: TRIP
Likely causes
- Braking (regenerative) energy too high for the deceleration time
- External brake resistor too small, badly connected or with a bad supply cable
- Earth leakage at the motor end
- Mains voltage too high (shows as OU)
First checks, in this order
- Increase the deceleration times.
- With an external brake resistor, check its sizing, connection and supply cable.
- Disconnect the motor from the drive and check the motor cable and motor for an earth fault.
- Check the supply voltage.
LU: DC-bus undervoltage
Hits OEE: AvailabilityWhat it means: Message (not a TRIP): DC bus voltage is too low, so the outputs are inhibited until the voltage recovers. The red LED blinks fast.[9]
Drive response: Message
Likely causes
- Mains voltage too low
- DC bus supply too low (power supply module)
- 400 V drive connected to a 240 V mains
First checks, in this order
- Check the mains voltage.
- Check the power supply module if the drive runs on a DC bus.
- Connect the drive to the correct mains voltage.
OH: Heatsink temperature > +85 °C
Hits OEE: AvailabilityWhat it means: TRIP because the heatsink passed +85 °C (LECOM error number 50). Above +80 °C the same OH code shows first as a warning.[9]
Drive response: TRIP
Likely causes
- Ambient temperature too high
- Heatsink very dirty
- High currents or frequent, long accelerations
First checks, in this order
- Let the drive cool down and improve ventilation.
- Clean the heatsink.
- Check the drive sizing and the load; replace rough-running or worn bearings if needed.
EEr: External fault (TRIP-SET)
Hits OEE: AvailabilityWhat it means: TRIP because a digital signal assigned to the TRIP-Set function became active (LECOM error number 91).[9]
Drive response: TRIP
Likely causes
- External device wired to the TRIP-Set input reported a fault
First checks, in this order
- Check the external device or sensor wired to the TRIP-Set input.
- Check which signal source is assigned to TRIP-Set in C0410.
0x2250: CiA: Continuous over current (internal)
Hits OEE: AvailabilityWhat it means: Keypad text: PU over current (event ID 8784). Continuous overcurrent on the inverter or motor side; the inverter is disabled at once and the motor coasts. Reset is accepted only after a 2 s blocking time.[7][8]
Also on: i510 cabinet (same code, text and keypad display)
Likely causes
- Continuous overcurrent on the inverter or motor side
- Overcurrent at the brake chopper (brake transistor)
- DC bus relay did not close because of a malfunction
First checks, in this order
- Check the motor and wiring for short circuits.
- Check the brake resistor and its wiring.
- Check any switching in the motor circuit.
- Check the motor data settings.
0x2320: Short circuit or earth leakage at the motor end
Hits OEE: AvailabilityWhat it means: Keypad text: Earth leak (event ID 8992). The inverter is disabled at once and the motor coasts. Reset is accepted only after a 2 s blocking time.[7][8]
Also on: i510 cabinet (same code, text and keypad display)
Likely causes
- Short circuit or earth fault in the motor cable
- Capacitive charging current of the motor cable too high
First checks, in this order
- Check the motor cable.
- Check the length of the motor cable.
- Use a shorter or lower-capacitance motor cable.
0x2340: Short circuit at the motor end
Hits OEE: AvailabilityWhat it means: Keypad text: Motor shorted (event ID 9024). The inverter is disabled at once and the motor coasts. Reset is accepted only after a 2 s blocking time.[7][8]
Also on: i510 cabinet (same code, text and keypad display)
Likely causes
- Short circuit in the motor cable
First checks, in this order
- Check the motor cable for a short circuit.
- Check the motor windings.
0x2350: CiA: i²xt overload (thermal state)
Hits OEE: AvailabilityWhat it means: Keypad text: i2t motor (event ID 9040). The motor thermal model says the motor is overloaded; the response is set in P308.03. Reset after a 2 s blocking time.[7][8]
Also on: i510 cabinet (same code, text and keypad display)
Likely causes
- Continuous current above what the motor allows
- Frequent or too long accelerations
- Too much load from the machine or driven mechanics
- Wrong motor data
First checks, in this order
- Check the drive sizing.
- Check the machine and driven mechanics for excess load.
- Check the motor data settings.
- Reduce slip compensation (P315.01, P315.02) and oscillation damping (P318.01, P318.02).
0x3120: Mains phase fault
Hits OEE: AvailabilityWhat it means: Keypad text: Mains Phase fail (event ID 12576). A mains phase has failed.[7][8]
Also on: i510 cabinet (same code, text and keypad display)
Likely causes
- Mains phase missing (blown fuse, loose terminal, open breaker pole)
First checks, in this order
- Check the wiring of the mains connection.
- Check the fuses.
0x3210: Fault - DC bus overvoltage
Hits OEE: AvailabilityWhat it means: Keypad text: DC Bus OV (event ID 12816). DC bus voltage passed the overvoltage error threshold, which follows the rated mains voltage set in P208.01 (threshold shown in P208.06).[7][8]
Also on: i510 cabinet (same code, text and keypad display)
Likely causes
- Too much braking energy (deceleration too fast for the load)
- Mains voltage too high
- Brake resistor or brake chopper not set up
First checks, in this order
- Make the load profile less aggressive (longer deceleration).
- Check the mains voltage and P208.01.
- Check the brake energy management settings.
- With P706.01 = 0, connect a brake resistor to the power unit and activate the integrated brake chopper.
0x3220: Fault - DC bus undervoltage
Hits OEE: AvailabilityWhat it means: Keypad text: DC Bus UV (event ID 12832). DC bus voltage fell below the undervoltage threshold (shown in P208.03). As trouble, it clears by itself when the voltage returns.[7][8]
Also on: i510 cabinet (same code, text and keypad display)
Drive response: Trouble
Likely causes
- Mains voltage too low or interrupted
- Blown fuse
- Rated mains voltage setting (P208.01) does not match the supply
First checks, in this order
- Check the mains voltage.
- Check the DC bus voltage in P105.00.
- Check the mains settings (P208.01).
- Check the fuses.
0x4210: Fault - Power unit overtemperature
Hits OEE: AvailabilityWhat it means: Keypad text: PU Overtemp. (event ID 16912). The power unit heatsink passed its fixed limit of 100 °C (actual value in P117.01).[7][8]
Also on: i510 cabinet (same code, text and keypad display)
Likely causes
- Ambient temperature too high
- Fan or ventilation slots dirty
- Fan defective
First checks, in this order
- Make sure the drive is cooled properly; 60 to 70 °C is normal at 100% load (P117.01).
- Clean the fan and ventilation slots; replace the fan if needed.
- Reduce the switching frequency (P305.00).
- Check the mains voltage.
0x4310: Motor overtemperature
Hits OEE: AvailabilityWhat it means: Keypad text: Overtemp. motor (event ID 17168). The motor temperature sensor on terminals X109/T1 and X109/T2 reads too hot; the response is set in P309.02. Reset after a 2 s blocking time.[7]
Likely causes
- Motor too hot from excessive current
- Motor too hot from frequent, long accelerations
- Fault in the temperature sensor or its wiring
First checks, in this order
- Check the drive and motor sizing.
- Check the motor temperature sensor and its wiring at X109/T1 and T2.
0x7180: Motor overcurrent
Hits OEE: AvailabilityWhat it means: Keypad text: Mot max current (event ID 29056). Motor current passed the threshold set in P353.01; the response is set in P353.02. Reset after a 1 s blocking time.[7][8]
Also on: i510 cabinet (same code, text and keypad display)
Likely causes
- Motor load too high
- Drive or motor undersized
- Threshold in P353.01 set too low
First checks, in this order
- Check the motor load.
- Check the drive sizing.
- Check the threshold set in P353.01.
OC1: Overcurrent in motor cable
Hits OEE: AvailabilityWhat it means: TRIP (fault number 0011): motor cable current above 2.25 x rated current, caught by hardware monitoring. The outputs switch off and the motor coasts.[10]
Drive response: TRIP
Likely causes
- Short circuit
- Capacitive charging current of the motor cable too high
- Acceleration or deceleration too short for the load (C0012, C0013, C0105)
- Encoder fault or swapped encoder tracks
- DC injection braking at high speed
- Missing mains phase
First checks, in this order
- Find the cause of the short circuit; check the motor cable.
- Use a shorter or lower-capacitance motor cable.
- Increase the gain of the Imax controller (C0075) and reduce its integral time (C0076).
- Check the encoder wiring.
- Check the mains connections, supply cable and mains voltage.
OC2: Motor cable earth fault
Hits OEE: AvailabilityWhat it means: TRIP (fault number 0012): one of the motor phases has contact to earth.[10]
Drive response: TRIP
Likely causes
- Motor phase shorted to earth in the motor or motor cable
First checks, in this order
- Find the cause of the short circuit.
- Check the motor cable.
OU: Overvoltage in the DC bus
Hits OEE: AvailabilityWhat it means: Message: DC bus voltage passed the switch-off threshold for the mains setting in C0173 (770 V, or 800 V at 480 V with brake chopper), so the outputs are inhibited until it drops and the C0912 delay has passed.[10]
Drive response: Message
Likely causes
- Braking energy too high
- Brake resistor too small
First checks, in this order
- Use a braking unit or regenerative module.
- Check the brake resistor sizing.
- Check that C0173 matches the mains voltage and braking setup.
LU: Undervoltage in the DC bus
Hits OEE: AvailabilityWhat it means: Message (fault number 1030): DC bus voltage is below the level set by C0173; the drive restarts by itself when the voltage returns.[10]
Drive response: Message
Likely causes
- Mains voltage too low or missing
- Supply cable problem
First checks, in this order
- Check the mains voltage.
- Check the supply cable.
OH: Heatsink temperature > +90 °C
Hits OEE: AvailabilityWhat it means: TRIP (fault number 0050): the heatsink passed +90 °C.[10]
Drive response: TRIP
Likely causes
- Ambient temperature above +40 °C or +50 °C
- Heatsink very dirty
- Wrong mounting position
First checks, in this order
- Let the drive cool and improve ventilation.
- Check the temperature inside the control cabinet.
- Clean the heatsink.
- Correct the mounting position.
Log it, or the same alarm comes back
A fault stops the inverter and with it the conveyor, pump or fan the line depends on, so in OEE terms it is a breakdown. Log the code, the drive and the minutes lost.
- Reason code: the code plus the drive, for example 8400 OC1, filler infeed conveyor, so an overcurrent that trips on every heavy start 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.
For drive faults across brands, fabrico.io has a VFD fault codes guide. 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
How do I reset a fault on a Lenze SMVector (AC Tech) drive?
Read the code first: the display shows F. plus the fault, for example F.OF, and P500 lists the last 8 faults. Fix the cause, then reset. The SMVector operating instructions describe a digital input set to Clear Fault (P121 to P124 = 20), which resets the fault when it closes; F.cFT clears by pressing the M (Mode) key twice. If the drive shows LC, it has used up its 5 automatic restarts (P110 = 3 to 6) and needs a manual reset after you correct the fault. The drive only runs again once the fault is reset, and the manual warns that cycling power after a motor overload fault can shorten motor life.
What does fault OC1 mean on a Lenze 8200 vector?
OC1 is Short circuit (LECOM error 11). It is a TRIP: the outputs switch off and the motor coasts until you reset it. Look for a short in the motor cable or motor, check the brake resistor and its cable, and check for too much charging current from a long motor cable (use a shorter or low-capacitance cable). On the 8400, oC1 means Power section - short circuit, most often a wrong motor connection. On the 9300 vector, OC1 means Overcurrent in motor cable, above 2.25 x rated current.
Where do I find the fault history on a Lenze 8400 (StateLine, HighLine, TopLine)?
Use the logbook. On the keypad open Diagnostics > Logbook; in EASY Starter or Engineer go online and click Logbook on the Diagnostics tab. StateLine keeps the last 15 entries and HighLine and TopLine keep 50. Each entry has the error type, the error such as oC1 or OU, the power-on time and a counter for repeats, and the logbook survives power loss. The current error is also shown in C00165 and C00166, and the status-determining error in C00168.
How do I reset a fault on a Lenze 8400?
Fix the cause first. Then run device command C00002/19 = 1, click Reset error on the Diagnostics tab in EASY Starter or Engineer, set the FailReset bit in the control word, or, with the Lenze preset terminal setup, take terminal RFR from HIGH to LOW. Fault, Trouble, TroubleQSP and WarningLocked all need this reset. Su03 (too frequent mains switching) can only be cleared by switching the mains. Automatic resets can be set up with AutoFailReset (C00184 to C00189); too many in a row trip dF10.
Where is the Lenze i550 fault code list, and how do I read a code on the keypad?
Lenze publishes the i510 and i550 event list online at docs.lenze.com, in the Diagnostics and fault elimination chapter (Event ID overview, then Causes and remedies). The keypad shows the error text, a letter for the type (F fault, T trouble, W warning) and the hexadecimal error code, for example Earth leak for 0x2320. Older events are in the error history buffer, P155.00 in group 1 (Diagnostics), which holds the last 32. To reset, clear the cause and press the keypad STOP key; the drive stays stopped (KSTOP) until you press RUN.
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.
- SMVector Frequency Inverter Operating Instructions, EDBSV01 EN v22.0 (Lenze no. 13632304), PDF dated 2023-02-22, served by Lenze's Documentation Finder (lenze.com, Services > Product-related documentation > SMVector > Operating instructions)
- SMVector ESVZAR0 RS-485 Modbus Communication Module, CMVMB401C, served by Lenze's Documentation Finder (lenze.com)
- Inverter Drives 8400 StateLine C (E84AVSCxxxxx) Reference manual, DMS 16.1 EN, 10/2019 (Lenze no. 13572910), served by Lenze's Documentation Finder (lenze.com)
- Inverter Drives 8400 StateLine C Operating Instructions, from firmware V06.00, DMS 1.2 EN, 12/2012 (Lenze no. 13390878), served by Lenze's Documentation Finder (lenze.com)
- Inverter Drives 8400 HighLine C (E84AVHCxxxxx) Reference manual, DMS 14.1 EN, 10/2019 (Lenze no. 13572908), served by Lenze's Documentation Finder (lenze.com)
- Inverter Drives 8400 TopLine C (E84AVTCxxxxx) Reference manual, DMS 11.1 EN, 10/2019 (Lenze no. 13572906), served by Lenze's Documentation Finder (lenze.com)
- Lenze online documentation, i550 cabinet frequency inverter Commissioning, Diagnostics and fault elimination (docs.lenze.com, build of 22 June 2026)
- Lenze online documentation, i510 cabinet frequency inverter Commissioning, Causes and remedies (docs.lenze.com, build of 22 June 2026)
- 8200 vector 0.25 to 90 kW frequency inverter System Manual, EDS82EV903 EN 3.0, served by Lenze's Documentation Finder (lenze.com, 8200 vector > Commissioning)
- 9300 vector 0.37 to 90 kW frequency inverter System Manual, EDSVF9333V EN 6.2, 04/2012 (bundled with EDSVF9383V EN 7.1 for the larger frames), served by Lenze's Documentation Finder (lenze.com, 9300 vector > Commissioning)
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 demoRelated: SEW-Eurodrive fault codes · Siemens SINAMICS G120 codes · VFD drive troubleshooting · electric motor · conveyor
Other alarm code lookups: FANUC: servo amplifier · spindle amplifier · robot SRVO | Siemens: MICROMASTER 440 · MASTERDRIVES · SINAMICS G120 · SINAMICS V90 servo · SINAMICS V20 | ABB: ACS550 drive · ACS800 drive · robot IRC5 | 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 | Magnetek: IMPULSE and DSD 412 | Omron: MX2 and RX inverters · G5 and 1S servo | WEG: CFW500, CFW300, CFW11, CFW08 | Hitachi: WJ200 inverter | Toshiba: E3, Q9, P9, S15, nC3, AS3 | AutomationDirect: GS10, GS20, GS4, GS1 to GS3 | 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
Related tools: full troubleshooting directory · OEE calculator · downtime cost · MTBF / MTTR · glossary