Yaskawa V1000 Alarm and Fault Codes
The fault and alarm codes of the Yaskawa V1000 drive: which ones trip the drive and which only flash a warning, what each one means, the likely causes, the first checks in order, and how to log it so the same stop stops coming back.
How V1000 codes show on the drive
When the V1000 trips on a fault, the code shows on the LED operator and the ALM light stays lit without flashing until the fault is reset, and the motor coasts to a stop.
When the code and the ALM light flash, it is a minor fault or alarm: the motor keeps running (or the drive refuses to start) and the code clears by itself once the cause is gone, so watch whether the display is steady or flashing because codes like ov, oH, CE and EF can appear both ways.
An oPE code means two parameter settings conflict and the drive will not run until the setting is corrected, and pressing ENTER while it shows brings up U1-18, the parameter that caused it.
U2-02 shows the last fault and U2-03 to U2-17 show the frequency, current, voltage and status at the moment it happened, while U3-01 to U3-10 list the last ten faults and U3-11 to U3-20 the operating hours when each one occurred. To reset, fix the cause and press the RESET key on the operator, or close and open the fault reset input (terminal S4 by factory setting).
If neither clears it, switch off the main power and switch it back on after the operator display has gone dark.
The CHARGE indicator LED only goes out when the DC bus is below 50 Vdc, and Yaskawa says to wait at least five minutes after all indicators are off and then measure the DC bus voltage to confirm it is safe before touching terminals.
Safe Disable (Hbb) switches off the drive output but does not cut the drive power supply or isolate input from output, and a baseblock (bb) is not a safe stop, so always shut off the power for maintenance. Follow lockout/tagout and your site's safe-work procedures, and check the manual for your exact model before you act.
Quick lookup
Faults trip the drive and stop the motor, so in OEE they are availability losses; alarms flash while the drive keeps running or waits, and oPE setting errors block the start until a parameter is fixed.
Type a code or a word (base block, overload, overcurrent, communication) to filter the list. Some codes are a fault and a minor fault, so each has its own row; click a code for its causes and first checks.
70 codes
| Code | Type | Name |
|---|---|---|
| oC | Fault | Overcurrent |
| ov | Fault | Overvoltage (fault) |
| Uv1 | Fault | DC Bus Undervoltage |
| oL1 | Fault | Motor Overload |
| oL2 | Fault | Drive Overload |
| SC | Fault | IGBT Short Circuit |
| GF | Fault | Ground Fault |
| oH | Fault | Heatsink Overheat (fault) |
| oH1 | Fault | Heatsink Overheat 1 |
| oH3 | Fault | Motor Overheat Alarm, PTC input (fault) |
| oH4 | Fault | Motor Overheat Fault (PTC input) |
| oL3 | Fault | Overtorque Detection 1 (fault) |
| UL3 | Fault | Undertorque Detection 1 (fault) |
| PF | Fault | Input Phase Loss |
| LF | Fault | Output Phase Loss |
| LF2 | Fault | Output Current Imbalance |
| rH | Fault | Braking Resistor Overheat |
| rr | Fault | Dynamic Braking Transistor |
| Uv2 | Fault | Control Power Supply Undervoltage |
| Uv3 | Fault | Soft Charge Circuit Fault |
| CE | Fault | MEMOBUS/Modbus Communication Error (fault) |
| bUS | Fault | Option Communication Error |
| EF0 | Fault | Option Card External Fault |
| EF1 to EF7 | Fault | External Fault (input terminal S1 to S7) |
| oPr | Fault | External Digital Operator Connection Fault |
| CoF | Fault | Current Offset Fault |
| SEr | Fault | Too Many Speed Search Restarts |
| Err | Fault | EEPROM Write Error |
| CPF02 | Fault | A/D Conversion Error |
| CPF06 | Fault | EEPROM Data Error |
| CPF07 / CPF08 | Fault | Terminal Board Communication Fault / EEPROM Serial Communication Fault |
| CPF20 / CPF21 | Fault | RAM, FLASH, Watchdog or Clock Fault |
| CPF25 | Fault | Terminal Board Not Connected |
| CPF03, CPF11 to CPF19, CPF22 to CPF24 | Fault | Control Board Hardware Faults |
| FbH | Fault | Excessive PID Feedback |
| FbL | Fault | PID Feedback Loss |
| oFA00 to oFA43 | Fault | Option Card Errors |
| bb | Alarm | Baseblock |
| Hbb | Alarm | Safe Disable Signal Input |
| HbbF | Alarm | Safe Disable Signal Input (channel fault) |
| CALL | Alarm | Serial Communication Transmission Error |
| CE | Alarm | MEMOBUS/Modbus Communication Error (alarm) |
| EF | Alarm | Forward/Reverse Run Command Input Error |
| EF1 to EF7 | Alarm | External Fault, alarm only (input terminal S1 to S7) |
| oH | Alarm | Heatsink Overheat (pre-alarm) |
| oH2 | Alarm | Drive Overheat Warning |
| oH3 | Alarm | Motor Overheat (PTC alarm) |
| oL3 | Alarm | Overtorque 1 (alarm) |
| UL3 | Alarm | Undertorque Detection 1 (alarm) |
| ov | Alarm | DC Bus Overvoltage (alarm) |
| Uv | Alarm | Undervoltage (alarm) |
| PASS | Alarm | MEMOBUS/Modbus Test Mode Complete |
| SE | Alarm | MEMOBUS/Modbus Test Mode Fault |
| rUn | Alarm | Motor Switch during Run |
| CrST | Alarm | Can Not Reset |
| dnE | Alarm | Drive Disabled |
| HCA | Alarm | Current Alarm |
| LT-1 | Alarm | Cooling Fan Maintenance Time |
| LT-2 | Alarm | Capacitor Maintenance Time |
| LT-3 | Alarm | Soft Charge Bypass Relay Maintenance Time |
| LT-4 | Alarm | IGBT Maintenance Time (50%) |
| TrPC | Alarm | IGBT Maintenance Time (90%) |
| oPE01 | Setting error | Drive Capacity Setting Fault |
| oPE02 | Setting error | Parameter Range Setting Error |
| oPE03 | Setting error | Multi-Function Input Selection Error |
| oPE04 | Setting error | Initialization Required (Terminal Board Mismatch) |
| oPE05 | Setting error | Run Command / Frequency Reference Source Selection Error |
| oPE08 | Setting error | Parameter Selection Error |
| oPE10 | Setting error | V/f Data Setting Error |
| oPE11 | Setting error | Carrier Frequency Setting Error |
Each code: causes and first checks
oC: Overcurrent
Hits OEE: AvailabilityWhat it means: The drive measured output current above its overcurrent trip level and switched the output off. Usually a short or ground in the motor circuit, or the load or ramp demanding more current than the drive can give.[1][3][4]
Also on: Fault only. Same code on J1000 and Z1000.
Likely causes
- Motor insulation damaged, or a motor cable shorted or grounded
- Load too heavy, or acceleration or deceleration time too short
- Contactor between drive and motor switched while the drive was outputting
- V/f settings wrong or too much torque compensation (C4-01)
- Run command given while the motor was still coasting
First checks, in this order
- With power off and the bus discharged, check the motor cable and the motor insulation resistance to ground
- Measure motor current and compare it with the drive rated current
- Make sure no output contactor opens or closes while the drive runs
- Lengthen the acceleration time (C1-01) and check E1-04 to E1-10
- If the motor can be coasting at start, enable speed search at start (b3-01 = 1)
ov: Overvoltage (fault)
Hits OEE: AvailabilityWhat it means: DC bus voltage rose above the overvoltage trip level (about 410 V on 200 V class, about 820 V on 400 V class) and the drive tripped. Most often the motor is pushing energy back into the drive during a fast slowdown.[1][3][4]
Also on: Also a minor fault (flashing ov, see the warning row). Same code on J1000 and Z1000.
Likely causes
- Deceleration time too short, so regenerative energy flows back from the motor
- Excessive braking load, or no braking resistor where one is needed
- Supply voltage too high or surges on the input supply
- Ground fault in the output circuit charging the DC bus
- Braking transistor damaged or braking resistor wired wrong
First checks, in this order
- Lengthen the deceleration time (C1-02, C1-04, C1-06, C1-08)
- Check stall prevention during deceleration is on (L3-04 = 1, the default)
- Fit a braking resistor if fast stops are needed
- Measure the supply voltage and check the motor wiring for ground faults
- Check the braking resistor and transistor wiring
Uv1: DC Bus Undervoltage
Hits OEE: AvailabilityWhat it means: While running, the DC bus voltage fell below the undervoltage level (L2-05) and the drive tripped. It points to the supply: a lost phase, a loose terminal, a dip or an outage.[1][3][4]
Also on: Not saved in the fault history. The flashing Uv code is the minor fault version. Same code on J1000 and Z1000.
Likely causes
- Input phase loss or a loose input power terminal
- Supply voltage too low, or the power was interrupted
- Supply transformer too small, so voltage sags at switch on
- Worn DC bus capacitors or internal circuitry
First checks, in this order
- Measure the input voltage on all phases
- Tighten the input terminals to the specified torque
- Check the capacity of the supply transformer
- Check capacitor maintenance monitor U4-05 and replace the drive if it is above 90%
oL1: Motor Overload
Hits OEE: AvailabilityWhat it means: The drive's electronic motor thermal protection decided the motor has been overloaded and stopped it. The calculation is based on the motor rated current set in E2-01.[1][3][4]
Also on: Fault only. Same code on J1000 and Z1000.
Likely causes
- Load too heavy, or long running at low speed with a general purpose motor
- Acceleration and deceleration cycles too short
- Wrong motor rated current in E2-01 or base frequency in E1-06 set too low
- Several motors running off one drive
- V/f voltage too high for the motor
First checks, in this order
- Check E2-01 matches the motor nameplate current
- Measure motor current and reduce the load
- Lengthen acceleration and deceleration times (C1-01 to C1-08)
- Check L1-01 suits the motor type, and use a thermal relay per motor (L1-01 = 0) for multiple motors
- Wait until monitor U4-16 is below 100 before resetting
oL2: Drive Overload
Hits OEE: AvailabilityWhat it means: The drive's own thermal protection tripped because the drive carried too much current for too long.[1][3][4]
Also on: Same code on J1000 and Z1000.
Likely causes
- Load too heavy for the drive size
- Acceleration and deceleration cycles too short
- Overload while running at low speed
- V/f voltage too high or too much torque compensation
- Current fluctuation from an input phase loss
First checks, in this order
- Measure output current and reduce the load
- Lengthen acceleration and deceleration times
- Lower the carrier frequency (C6-02) when running at low speed
- Check the input supply for a missing phase
- Fit a larger drive if the load is correct
SC: IGBT Short Circuit
Hits OEE: AvailabilityWhat it means: The drive detected a short circuit at its output transistors (IGBTs) and shut down.[1][4]
Also on: Drive software PRG 1020 and later. Z1000 uses SC for IGBT Short Circuit or Ground Fault.
Likely causes
- Short circuit in the motor wiring
- IGBT short circuit or a fault in the detection circuit inside the drive
First checks, in this order
- Check the motor wiring for shorts
- Cycle power to the drive
- If it comes back, contact your Yaskawa representative
GF: Ground Fault
Hits OEE: AvailabilityWhat it means: Current leaking to ground on the output side went above half of the drive rated current, so the drive tripped.[1][4]
Also on: On models 2A0020 to 2A0069 and 4A0011 to 4A0038 detection is enabled with L8-09 = 1. Same code on Z1000.
Likely causes
- Motor insulation damaged
- Damaged motor cable shorting to ground
- Leakage current at the drive output too high
- Drive hardware problem
First checks, in this order
- Measure the motor insulation resistance
- Check the motor cable and its resistance to the ground terminal
- Lower the carrier frequency and reduce stray capacitance to cut leakage
- Replace the drive if motor and cable test good
oH: Heatsink Overheat (fault)
Hits OEE: AvailabilityWhat it means: The heatsink went above the oH detection temperature (L8-02) and the drive is set to stop on it.[1][4]
Also on: Trips only when L8-03 is set to a stop method (0 to 2). With the factory setting (L8-03 = 3) oH flashes as an alarm instead, see the warning row. Same code on Z1000.
Likely causes
- Surrounding temperature too high
- Load too heavy
- Internal cooling fan stopped
First checks, in this order
- Check the temperature around the drive and the airflow in the enclosure
- Measure output current and reduce the load
- Lower the carrier frequency (C6-02)
- Replace the cooling fan if stopped, then reset its maintenance monitor (o4-03 = 0)
oH1: Heatsink Overheat 1
Hits OEE: AvailabilityWhat it means: The heatsink got hotter than the oH1 level, which is 10 degrees C above the factory value of L8-02, and the drive tripped.[1][3][4]
Also on: Same code on J1000 and Z1000.
Likely causes
- Surrounding temperature too high
- Load too heavy
- Cooling fan at the end of its life or failed
- Current drawn from control terminal +V above its limit
First checks, in this order
- Check ambient temperature and enclosure ventilation
- Measure output current, then reduce the load or the carrier frequency (C6-02)
- Check fan maintenance monitor U4-04 and replace the fan, then set o4-03 = 0
- Keep the current from terminal +V at 20 mA or less
oH3: Motor Overheat Alarm, PTC input (fault)
Hits OEE: AvailabilityWhat it means: The motor PTC thermistor signal on analog input A1 or A2 reached the alarm level, and L1-03 is set to stop the drive.[1][4]
Also on: Needs H3-02 or H3-10 set to E. Trips only when L1-03 = 0 to 2; the factory setting (3) gives the flashing oH3 alarm. Same code on Z1000.
Likely causes
- Motor overheated from heavy load, short cycles or long accel and decel
- V/f pattern voltage too high (E1-08, E1-10)
- Wrong motor rated current in E2-01
- Motor cooling system not working
First checks, in this order
- Check load size, acceleration and deceleration times and cycle times
- Check E2-01 against the motor nameplate
- Check the motor cooling and repair it if needed
- Reduce E1-08 and E1-10 only moderately, too low cuts low speed torque
oH4: Motor Overheat Fault (PTC input)
Hits OEE: AvailabilityWhat it means: The motor PTC signal reached the fault level, which is above the oH3 alarm level, and the drive stops the motor.[1][4]
Also on: Needs H3-02 or H3-10 set to E. The stop method is set in L1-04. Same code on Z1000.
Likely causes
- Motor overheated from heavy load or short cycle times
- V/f pattern voltage too high (E1-08, E1-10)
- Wrong motor rated current in E2-01
- Motor cooling system not working
First checks, in this order
- Check load size, acceleration and deceleration times and cycle times
- Check E2-01 against the motor nameplate
- Check the motor cooling and repair it if needed
- Increase acceleration and deceleration times (C1-01 to C1-08)
oL3: Overtorque Detection 1 (fault)
Hits OEE: AvailabilityWhat it means: Output current (or torque in Open Loop Vector) stayed above L6-02 for longer than L6-03, and L6-01 is set to trip. Often a jammed or overloaded machine.[1][3][4]
Also on: Fault when L6-01 = 3 or 4, flashing alarm when L6-01 = 1 or 2. oL4 is the same check using L6-04 to L6-06. Same code on J1000 and Z1000.
Likely causes
- Fault on the machine side, for example the machine is locked up
- Detection level or time not suited to the load
First checks, in this order
- Check the machine for jams or binding and remove the cause
- Check the settings of L6-02 and L6-03
- Check L6-01 to confirm the drive should trip (3 or 4) rather than only warn (1 or 2)
UL3: Undertorque Detection 1 (fault)
Hits OEE: AvailabilityWhat it means: Output current fell below L6-02 for longer than L6-03, and L6-01 is set to trip. Typical of a broken part in the drive train or a load that went missing.[1][4]
Also on: Can also be set as a flashing alarm through L6-01. UL4 is the same check using L6-04 to L6-06. Same code on Z1000.
Likely causes
- Fault on the machine side, the load dropped or decreased sharply
- Detection level or time not suited to the load
First checks, in this order
- Check the load and the transmission for broken parts
- Check the settings of L6-02 and L6-03
- Check the L6-01 setting, it decides whether UL3 trips the drive or only warns
PF: Input Phase Loss
Hits OEE: AvailabilityWhat it means: The drive saw an open phase or a large voltage imbalance on its input supply. Detection is on when L8-05 = 1.[1][3][4]
Also on: Same code on J1000 and Z1000.
Likely causes
- Phase loss in the drive input power
- Loose wiring at the input power terminals
- Large fluctuation or imbalance in the supply voltage
- Main circuit capacitors worn
First checks, in this order
- Check the main circuit input wiring for errors
- Tighten the input terminals to the specified torque
- Measure the supply voltage on each phase
- Check capacitor monitor U4-05 and replace the drive if it is above 90%
LF: Output Phase Loss
Hits OEE: AvailabilityWhat it means: One output phase to the motor is open. Detection is on when L8-07 = 1 or 2.[1][3][4]
Also on: Same code on J1000 and Z1000.
Likely causes
- Output cable disconnected or output terminal loose
- Motor winding damaged
- Motor current is less than 5% of the drive rated current
- Output transistor damaged
- Single phase motor connected
First checks, in this order
- Check the output wiring and tighten the terminals
- Measure the resistance between motor lines
- Check that drive and motor capacities match
- Replace the drive if an output transistor has failed
LF2: Output Current Imbalance
Hits OEE: AvailabilityWhat it means: The three output currents are out of balance because one or more phases is lost.[1][4]
Also on: Same code on Z1000.
Likely causes
- Phase loss or poor connection on the output side
- Loose output terminal wires
- No signal from the gate driver board
- Motor phases have uneven impedance
First checks, in this order
- Check the output wiring and connections
- Tighten the output terminals to the specified torque
- Measure the line to line resistance of each motor phase, all should match
- Contact Yaskawa if the gate driver board is suspected
rH: Braking Resistor Overheat
Hits OEE: AvailabilityWhat it means: The braking resistor protection tripped because the resistor is used harder than its rating. It works on braking load, so it can trip even when the resistor surface is not very hot.[1][3][4]
Also on: Detection only when L8-01 = 1 (off by default). Same code on J1000 and Z1000.
Likely causes
- Deceleration time too short, too much regenerative energy
- Excessive braking inertia
- Braking resistor not suited to the duty
First checks, in this order
- Check the load, deceleration time and speed
- Lengthen acceleration and deceleration times (C1-01 to C1-08)
- Recalculate braking power and fit a larger braking resistor if needed
rr: Dynamic Braking Transistor
Hits OEE: AvailabilityWhat it means: The built in dynamic braking transistor has failed.[1][4]
Also on: Same code on Z1000.
Likely causes
- Braking transistor damaged
- Control circuit damaged
First checks, in this order
- Cycle power and see if the fault comes back
- Replace the drive if it continues
Uv2: Control Power Supply Undervoltage
Hits OEE: AvailabilityWhat it means: The voltage of the drive's internal control power supply is too low.[1][4]
Also on: Not saved in the fault history. Same code on Z1000.
Likely causes
- L2-02 changed from default on a 7.5 kW or smaller drive without the Momentary Power Loss Ride-Thru unit
- Control power supply wiring damaged
- Internal circuitry damaged
First checks, in this order
- Return L2-02 to its default or fit the Momentary Power Loss Ride-Thru unit
- Cycle power and see if the fault comes back
- Replace the drive if it keeps coming back
Uv3: Soft Charge Circuit Fault
Hits OEE: AvailabilityWhat it means: The inrush prevention (soft charge) circuit that charges the DC bus at power on has failed.[1][3][4]
Also on: Same code on J1000 and Z1000.
Likely causes
- Contactor in the inrush prevention circuit damaged
- Inrush circuit at the end of its expected life
First checks, in this order
- Cycle power and see if the fault comes back
- Check monitor U4-06 and replace the drive if it is above 90%
- Replace the drive if the fault continues
CE: MEMOBUS/Modbus Communication Error (fault)
Hits OEE: AvailabilityWhat it means: No valid Modbus control data arrived within the CE detection time (H5-09), and H5-04 is set to stop the drive.[1][3][4]
Also on: With the factory setting H5-04 = 3, CE is an alarm only and the drive keeps running (see the warning row). Same code on J1000 and Z1000.
Likely causes
- Faulty or shorted communication wiring
- Noise on the communication line
- Protocol settings (H5 parameters) not matching the master
- H5-09 shorter than the master's message cycle
- Communication cable disconnected or damaged
First checks, in this order
- Check the RS-485 wiring and connectors for loose wires and shorts
- Compare the H5 settings with the PLC settings
- Use shielded cable grounded at one end and keep it away from power wiring
- Set a longer CE detection time (H5-09) if the master polls slowly
bUS: Option Communication Error
Hits OEE: AvailabilityWhat it means: The fieldbus option card lost communication with the master after the link had been established.[1][4]
Also on: Only detected when the run command or frequency reference comes from the option card. Can also appear as a flashing minor fault depending on F6-01. Same code on Z1000.
Likely causes
- No signal from the PLC, or the master stopped communicating
- Communication cable faulty, loose or shorted
- Noise on the network
- Option card damaged or not properly seated
First checks, in this order
- Check the network wiring and connectors
- Check that the PLC or master is running
- Reseat the option card so its pins line up with the drive connector
- Reduce noise with shielded cable and separate routing from power lines
- Replace the option card if the wiring is good and the error continues
EF0: Option Card External Fault
Hits OEE: AvailabilityWhat it means: The PLC sent an external fault to the drive through the communication option card.[1][3][4]
Also on: Shows as a flashing alarm instead when F6-03 = 3. Same code on J1000 and Z1000.
Likely causes
- External fault sent by the PLC
- Problem in the PLC program
First checks, in this order
- Find and clear the cause of the external fault on the PLC side
- Remove the external fault command from the PLC
- Check the PLC program
EF1 to EF7: External Fault (input terminal S1 to S7)
Hits OEE: AvailabilityWhat it means: A device wired to a digital input set as external fault (H1 = 20 to 2F) signalled a problem and the drive stopped. The number is the terminal, so EF3 means terminal S3.[1][3][4]
Also on: Factory setting makes S3 an external fault input (H1-03 = 24), so EF3 is the one seen most. Some H1 settings make it alarm only (see the warning row). J1000 has EF1 to EF5, Z1000 has EF1 to EF7.
Likely causes
- An external device tripped its alarm output
- Wiring to the input is wrong
- A digital input is set as external fault by mistake
First checks, in this order
- Find the device wired to that terminal and clear its fault
- Check the signal wiring to the terminal
- Check for unused terminals set to H1 = 20 to 2F and change them
- Reset the fault
oPr: External Digital Operator Connection Fault
Hits OEE: AvailabilityWhat it means: The external operator keypad was disconnected while it was the run command source (LOCAL) and o2-06 is set to stop on disconnection.[1][3][4]
Also on: Same code on J1000 and Z1000.
Likely causes
- External operator not properly connected
- Operator cable damaged
First checks, in this order
- Check the connection between the operator and the drive
- Replace the cable if damaged
- Power off, disconnect and reconnect the operator, then power on
CoF: Current Offset Fault
Hits OEE: AvailabilityWhat it means: At start the drive could not set its current sensor offset, usually because current was still circulating in a motor that was coasting or had just stopped, or because the sensor is damaged.[1][3]
Also on: Same code on J1000.
Likely causes
- Residual induction current in the motor when the drive tried to start
- Current sensor damaged
First checks, in this order
- Give the motor enough time for its residual voltage to fade before restarting
- Enable speed search at start (b3-01 = 1)
- Use external speed search inputs (H1 = 61 or 62)
SEr: Too Many Speed Search Restarts
Hits OEE: AvailabilityWhat it means: Speed search tried to catch the spinning motor more times than b3-19 allows.[1][4]
Also on: Same code on Z1000.
Likely causes
- Speed search parameters set to the wrong values
- Motor coasting in the opposite direction to the run command
First checks, in this order
- Reduce b3-10 and increase b3-17 and b3-18
- Repeat auto-tuning
- Enable bi-directional speed search (b3-14 = 1)
Err: EEPROM Write Error
Hits OEE: AvailabilityWhat it means: Data written to the drive memory (EEPROM) did not match when it was checked.[1][3][4]
Also on: Same code on J1000 and Z1000.
Likely causes
- Yaskawa lists no specific cause, the write to EEPROM did not verify
First checks, in this order
- Press the ENTER key
- Correct the parameter settings
- Cycle power to the drive
CPF02: A/D Conversion Error
Hits OEE: AvailabilityWhat it means: The drive's analog to digital converter reported an error.[1][3][4]
Also on: Same code on J1000 and Z1000.
Likely causes
- Control circuit damaged
- Control terminals shorted (+V, AC)
- Too much current drawn from control terminal +V
First checks, in this order
- Check the control terminal wiring for errors and shorts
- Check the speed potentiometer resistance and its wiring
- Keep the current from terminal +V at 20 mA or less
- Cycle power and replace the drive if it continues
CPF06: EEPROM Data Error
Hits OEE: AvailabilityWhat it means: The data saved in the drive memory is corrupt or does not match after a board replacement.[1][3][4]
Also on: Same code on J1000 and Z1000.
Likely causes
- Control circuit damaged
- Power switched off while parameters were being written, for example from a communication option
First checks, in this order
- Cycle power and check operation
- Initialize the drive with A1-03
- Replace the drive if the problem continues
CPF07 / CPF08: Terminal Board Communication Fault / EEPROM Serial Communication Fault
Hits OEE: AvailabilityWhat it means: The control board cannot talk properly to the removable terminal board or its memory.[1][3][4]
Also on: J1000 lists CPF08, Z1000 lists CPF07 and CPF08.
Likely causes
- Bad connection between the terminal board and the control board
First checks, in this order
- Turn the power off
- Reconnect the control circuit terminal board and check its connections
- Power on and check if the fault returns
CPF20 / CPF21: RAM, FLASH, Watchdog or Clock Fault
Hits OEE: AvailabilityWhat it means: One of the control board self checks (RAM, flash memory, watchdog or clock) failed. CPF20 shows when it happens at power up, CPF21 after the drive has started.[1][3][4]
Also on: Same codes on J1000 and Z1000.
Likely causes
- Control board hardware damaged
First checks, in this order
- Note the code, drive model and software version
- Replace the drive (Yaskawa's listed fix)
CPF25: Terminal Board Not Connected
Hits OEE: AvailabilityWhat it means: The removable control terminal board is not connected correctly.[1][4]
Also on: Same code on Z1000.
Likely causes
- Terminal board not connected correctly
First checks, in this order
- Power off and reconnect the terminal board to its connector on the drive
- Cycle power to the drive
CPF03, CPF11 to CPF19, CPF22 to CPF24: Control Board Hardware Faults
Hits OEE: AvailabilityWhat it means: Internal self diagnostics found a control board problem: PWM data (CPF03), RAM (CPF11), flash (CPF12), watchdog (CPF13), CPU (CPF14, CPF18, CPF19), clock (CPF16), timing (CPF17), A/D (CPF22), PWM feedback (CPF23) or capacity signal (CPF24).[1]
Also on: The V1000 list skips CPF15. Several of these codes also exist on J1000 and Z1000.
Likely causes
- Drive hardware damaged
- CPU upset by noise (Yaskawa names noise for CPF14, CPF18 and CPF19)
First checks, in this order
- Cycle power once (Yaskawa lists this for CPF22)
- Replace the drive if the code returns (Yaskawa's listed fix for these codes)
FbH: Excessive PID Feedback
Hits OEE: AvailabilityWhat it means: The PID feedback signal stayed above b5-36 for longer than b5-37.[1][4]
Also on: Fault when b5-12 = 2 or 5, flashing alarm when b5-12 = 1 or 4. Same code on Z1000.
Likely causes
- b5-36 or b5-37 set wrong
- PID feedback wiring incorrect
- Feedback sensor faulty
First checks, in this order
- Check the settings of b5-36 and b5-37
- Check and correct the feedback wiring
- Check the sensor and replace it if damaged
FbL: PID Feedback Loss
Hits OEE: AvailabilityWhat it means: The PID feedback signal stayed below b5-13 for longer than b5-14, so the drive treats the feedback as lost.[1][4]
Also on: Fault when b5-12 = 2, flashing alarm when b5-12 = 1 or 4. Same code on Z1000.
Likely causes
- b5-13 or b5-14 set wrong
- PID feedback wiring incorrect or broken
- Feedback sensor faulty
First checks, in this order
- Check the settings of b5-13 and b5-14
- Check and correct the feedback wiring
- Check the sensor and replace it if damaged
oFA00 to oFA43: Option Card Errors
Hits OEE: AvailabilityWhat it means: The drive found a problem with the option card in port CN5: an incompatible card (oFA00), a card not connected properly (oFA01), or a card self check or memory error (oFA03 to oFA43).[1][3][4]
Also on: J1000 lists oFA01, Z1000 lists oFA codes.
Likely causes
- Option card not compatible with the drive
- Option card not connected properly
- Option card or hardware damaged
First checks, in this order
- Use an option card that is compatible with the V1000
- Turn the power off and reconnect the option card
- Replace the option card and contact Yaskawa
bb: Baseblock
Warning: act before it becomes a stopWhat it means: An external baseblock signal on a digital input has switched the drive output off, and the motor coasts. When the signal clears with a run command still on, the drive does a speed search and picks the motor up again.[1][2][3][4]
Also on: Does not close a minor fault output (H2 = 10); a digital output set to 8 (During Baseblock) shows it. Same code and meaning on J1000 and Z1000 (Z1000: set H2 = 8 or 1B to signal bb).
Likely causes
- Baseblock signal present on a digital input S1 to S7 set to H1 = 8 or 9
- With setting 8 (N.O.) the input is closed, with setting 9 (N.C.) the input is open
- External sequence or interlock timing holding the baseblock signal
First checks, in this order
- Find which terminal is set to H1 = 8 or 9
- Check that input's state against its N.O. or N.C. setting
- Check the external sequence and the timing of the baseblock signal against the run command
Hbb: Safe Disable Signal Input
Warning: act before it becomes a stopWhat it means: The Safe Disable input (H1 to HC) is open, so the drive output is switched off and the motor cannot run. This is the normal display while the safety circuit is open.[1][2][5]
Also on: Closes a minor fault output (H2 = 10). With the optional dual Safe Disable terminal board (JVOP-TBVA03) both H1 and H2 must be closed to HC. Not listed in the J1000 or Z1000 manuals checked.
Likely causes
- External safety circuit tripped and opened terminal H1
- Factory jumper between HC and H1 removed or loose on a drive that does not use Safe Disable
- Safe Disable channel broken inside the drive
First checks, in this order
- Check whether the external safety circuit has tripped and reset it
- If Safe Disable is not used, check the jumper link between HC and H1
- Remove the run command, close H1 to HC, then give a new run command
- Replace the drive if H1 has a signal and Hbb stays
HbbF: Safe Disable Signal Input (channel fault)
Warning: act before it becomes a stopWhat it means: The drive found a problem with the Safe Disable inputs, such as only one of two channels opening or faulty Safe Disable hardware, and the output stays off.[1][2][5]
Also on: Closes a minor fault output (H2 = 10). Yaskawa documents word it differently, see uncertain.
Likely causes
- Only one Safe Disable input opened (dual input terminal board)
- Safe Disable input wiring fault
- Safe Disable hardware in the drive defective
First checks, in this order
- Check the Safe Disable wiring to H1 and H2
- Make sure both Safe Disable inputs switch together
- Replace the drive if the wiring is good (Yaskawa's listed fix)
CALL: Serial Communication Transmission Error
Warning: act before it becomes a stopWhat it means: Modbus communication has not been established yet, the drive is still waiting for a valid message from the master.[1][3][4]
Also on: Same code on J1000 and Z1000.
Likely causes
- Communication wiring faulty, shorted or not connected
- Programming error on the master side
- Communication circuitry damaged
- Termination resistor switch set wrong on the last drive
First checks, in this order
- Check the wiring, remove shorts and reconnect loose wires
- Check the master's communication program at start up
- Set DIP switch S2 to ON on the drive at the end of the line
- Replace the drive if self diagnostics show a fault
CE: MEMOBUS/Modbus Communication Error (alarm)
Warning: act before it becomes a stopWhat it means: Control data from the Modbus master was not received correctly in time, and the drive is set to keep running (H5-04 = 3, the factory setting) while CE flashes.[1][2][3][4]
Also on: Becomes a fault when H5-04 = 0 to 2. Same code on J1000 and Z1000.
Likely causes
- Noise on the communication line
- Communication protocol not compatible
- CE detection time (H5-09) shorter than the communication cycle
- PLC software settings or hardware problem
- Cable disconnected or damaged
First checks, in this order
- Check the cable and connector for a signal
- Compare the H5 settings with the PLC protocol settings
- Set a longer H5-09 or change the PLC timing
- Improve shielding and separate the cable from power wiring
EF: Forward/Reverse Run Command Input Error
Warning: act before it becomes a stopWhat it means: Forward and reverse run commands were both on for more than 0.5 seconds. The motor ramps to stop.[1][2][3][4]
Also on: Minor fault output closes (H2 = 10). Same code on J1000 and Z1000.
Likely causes
- Sequence error in the run command wiring or PLC logic
First checks, in this order
- Check the forward and reverse command sequence
- Make sure only one direction command can be on at a time
EF1 to EF7: External Fault, alarm only (input terminal S1 to S7)
Warning: act before it becomes a stopWhat it means: An external fault input set to alarm only is active, so the drive keeps running and flashes EF with the terminal number.[1][3][4]
Also on: J1000 has EF1 to EF5, Z1000 has EF1 to EF7.
Likely causes
- An external device tripped its alarm output
- Wiring to the input is wrong
- Multi-function inputs set incorrectly
First checks, in this order
- Clear the cause at the external device
- Check the signal wiring to the terminal set to H1 = 20 to 2F
- Check for unused terminals set as external fault and change them
oH: Heatsink Overheat (pre-alarm)
Warning: act before it becomes a stopWhat it means: The heatsink passed the oH level (L8-02). With the factory setting L8-03 = 3 the drive keeps running and flashes oH; oH1 trips at a higher temperature.[1][3][4]
Also on: L8-03 = 4 makes the drive slow down instead (L8-19). Same code on J1000 and Z1000.
Likely causes
- Surrounding temperature too high
- Internal cooling fan stopped
- Airflow around the drive restricted or fan clogged with dust
First checks, in this order
- Check the surrounding temperature and enclosure ventilation
- Check the installation spacing around the drive
- Clear dust and debris from the cooling fan
- Replace the fan if stopped and reset its monitor (o4-03 = 0)
oH2: Drive Overheat Warning
Warning: act before it becomes a stopWhat it means: An external device sent an overheat warning to a digital input set to H1 = B.[1][4]
Also on: Same code on Z1000.
Likely causes
- External device triggered the overheat warning input
First checks, in this order
- Find the device that sent the overheat warning
- Fix that device, the warning then clears by itself
oH3: Motor Overheat (PTC alarm)
Warning: act before it becomes a stopWhat it means: The motor PTC signal reached the alarm level. With the factory setting L1-03 = 3 the drive keeps running and flashes oH3.[1][4]
Also on: Same code on Z1000.
Likely causes
- Motor thermistor (PTC) wiring fault
- Fault on the machine side, for example the machine is locked up
- Motor overheated
First checks, in this order
- Repair the PTC input wiring if faulty
- Check the machine and remove the cause
- Check load size, acceleration and deceleration times and cycle times
- Check E2-01 and the motor cooling system
oL3: Overtorque 1 (alarm)
Warning: act before it becomes a stopWhat it means: Output current (or torque in Open Loop Vector) was above L6-02 for longer than L6-03, and L6-01 is set to warn and keep running.[1][3][4]
Also on: oL4 is the same alarm using L6-05 and L6-06. Same code on J1000 and Z1000.
Likely causes
- Parameter settings not suited to the load
- Fault on the machine side, for example the machine is locked up
First checks, in this order
- Check the machine and remove the cause
- Check L6-02 and L6-03
- Set L6-01 to 3 or 4 if the machine should stop on overtorque instead of only warning
UL3: Undertorque Detection 1 (alarm)
Warning: act before it becomes a stopWhat it means: Output current (or torque in Open Loop Vector) was below L6-02 for longer than L6-03, and the drive is set to warn and keep running.[1][4]
Also on: UL4 is the same alarm using L6-05 and L6-06. Same code on Z1000.
Likely causes
- Parameter settings not suited to the load
- Load dropped or decreased significantly
First checks, in this order
- Check the transmission for broken parts
- Check L6-02 and L6-03
- Check the L6-01 setting, it decides whether UL3 trips the drive or only warns
ov: DC Bus Overvoltage (alarm)
Warning: act before it becomes a stopWhat it means: The DC bus voltage went above the overvoltage level and the drive flashes ov as a warning instead of tripping.[1][3][4]
Also on: The steady ov is the fault version. Same code on J1000 and Z1000.
Likely causes
- Surge voltage on the drive input supply
- Motor short circuited
- Ground current has over charged the main circuit capacitors
- Noise making the drive operate incorrectly
First checks, in this order
- Install an AC reactor or DC link choke against supply surges
- Check the motor cable, relay terminals and motor terminal box for shorts
- Check noise sources and fit a surge protector on contactor coils
- Set the number of fault restarts (L5-01) to a value other than 0
Uv: Undervoltage (alarm)
Warning: act before it becomes a stopWhat it means: A run command was given while the drive was stopped and the DC bus was low, the inrush contactor was open or the control supply was low. Uv also flashes while the drive rides through a momentary power loss (L2-01 = 1 or 2).[1][3][4]
Also on: Same code on J1000 and Z1000.
Likely causes
- Phase loss in the drive input power
- Loose wiring at the input terminals
- Input voltage problem
- Worn internal circuitry or capacitors
- Supply transformer too small
First checks, in this order
- Check the main circuit input wiring
- Tighten the input terminals to the specified torque
- Measure the input voltage
- Check capacitor monitor U4-05 and replace the drive if it is above 90%
PASS: MEMOBUS/Modbus Test Mode Complete
Warning: act before it becomes a stopWhat it means: Not a problem: the Modbus self test has finished normally.[1][3][4]
Also on: No minor fault output. Same code on J1000 and Z1000.
Likely causes
- The Modbus communication self test was run and passed
First checks, in this order
- No fix needed, this confirms the test was successful
SE: MEMOBUS/Modbus Test Mode Fault
Warning: act before it becomes a stopWhat it means: A digital input set to Modbus test (H1 = 67) was closed while the drive was running.[1][3][4]
Also on: Same code on J1000 and Z1000.
Likely causes
- Modbus test input closed during run
First checks, in this order
- Stop the drive
- Run the Modbus test again
rUn: Motor Switch during Run
Warning: act before it becomes a stopWhat it means: A command to switch between motor 1 and motor 2 came in while the drive was running.[1]
Also on: Minor fault output closes (H2 = 10).
Likely causes
- Motor switch command entered during run
First checks, in this order
- Change the sequence so the motor switch command only comes while the drive is stopped
CrST: Can Not Reset
Warning: act before it becomes a stopWhat it means: A fault reset was tried while a run command was on, so the reset was refused.[1][3][4]
Also on: Same code on J1000 and Z1000.
Likely causes
- Fault reset executed while a run command was entered
First checks, in this order
- Turn off the run command
- Make sure no run command can come from the terminals or option card during a reset
- Reset the fault again
dnE: Drive Disabled
Warning: act before it becomes a stopWhat it means: A digital input set to Drive Enable (H1 = 6A) is switched off, so the drive will not run.[1][4]
Also on: Same code on Z1000.
Likely causes
- Drive Enable input switched off
First checks, in this order
- Check the operation sequence and the signal to the Drive Enable input
HCA: Current Alarm
Warning: act before it becomes a stopWhat it means: Output current went above the warning level of 150% of drive rated current. The drive keeps running.[1][2][4]
Also on: Same code on Z1000.
Likely causes
- Load too heavy
- Acceleration and deceleration times too short
- Special purpose motor, or a motor larger than the drive allows
First checks, in this order
- Measure the current flowing through the motor
- Reduce the load or use a larger drive
- Lengthen acceleration and deceleration times (C1-01 to C1-08)
- Check the motor capacity suits the drive
LT-1: Cooling Fan Maintenance Time
Warning: act before it becomes a stopWhat it means: The cooling fan has reached 90% of its expected life and may need replacing.[1][2][4]
Also on: Signals on a digital output only when H2 = 2F. Same code on Z1000.
Likely causes
- Cooling fan reached 90% of its expected performance life
First checks, in this order
- Replace the cooling fan
- Reset the maintenance monitor by setting o4-03 to 0
LT-2: Capacitor Maintenance Time
Warning: act before it becomes a stopWhat it means: The main circuit and control circuit capacitors have reached 90% of their expected life.[1][2][4]
Also on: Signals on a digital output only when H2 = 2F. Same code on Z1000.
Likely causes
- Capacitors reached 90% of their expected performance life
First checks, in this order
- Plan replacement of the control board or the whole drive
- Contact Yaskawa for control board replacement
LT-3: Soft Charge Bypass Relay Maintenance Time
Warning: act before it becomes a stopWhat it means: The DC bus soft charge relay has reached 90% of its expected life.[1][4]
Also on: Signals on a digital output only when H2 = 2F. Same code on Z1000.
Likely causes
- Soft charge relay reached 90% of its expected performance life
First checks, in this order
- Plan replacement of the control board or the whole drive
- Contact Yaskawa for control board replacement
LT-4: IGBT Maintenance Time (50%)
Warning: act before it becomes a stopWhat it means: The output transistors (IGBTs) have reached 50% of their expected life.[1][4]
Also on: Signals on a digital output only when H2 = 2F. TrPC follows at 90%. Same code on Z1000.
Likely causes
- IGBTs reached 50% of their expected performance life
First checks, in this order
- Check the load, carrier frequency and output frequency
TrPC: IGBT Maintenance Time (90%)
Warning: act before it becomes a stopWhat it means: The output transistors (IGBTs) have reached 90% of their expected life.[1][4]
Also on: Minor fault output closes (H2 = 10). Same code on Z1000.
Likely causes
- IGBTs reached 90% of their expected performance life
First checks, in this order
- Replace the drive
oPE01: Drive Capacity Setting Fault
Setting error: the drive will not start until it is fixedWhat it means: The drive capacity set in o2-04 does not match the actual drive, so it will not run.[1][3]
Also on: Programming error, no fault output. Same code on J1000.
Likely causes
- o2-04 differs from the real drive capacity
First checks, in this order
- Correct the value in o2-04
oPE02: Parameter Range Setting Error
Setting error: the drive will not start until it is fixedWhat it means: A parameter is set outside its allowed range, so the drive will not run.[1][3]
Also on: Other errors take priority if several occur at once. Same code on J1000.
Likely causes
- Parameters set outside the possible setting range
First checks, in this order
- Press ENTER to show U1-18, which names the parameter
- Set that parameter to a proper value
oPE03: Multi-Function Input Selection Error
Setting error: the drive will not start until it is fixedWhat it means: The digital inputs H1-01 to H1-07 have contradictory settings, so the drive will not run.[1][3]
Also on: Same code on J1000.
Likely causes
- Same function assigned to two inputs (except Not used and External Fault)
- Up command set without Down, or the other way round
- Functions that cannot be used together set at the same time
First checks, in this order
- Press ENTER to show U1-18
- Give each digital input a different function
- Set paired functions together, for example Up with Down
oPE04: Initialization Required (Terminal Board Mismatch)
Setting error: the drive will not start until it is fixedWhat it means: The drive, control board or terminal board was replaced and the parameter sets no longer match.[1]
Also on: Programming error, no fault output.
Likely causes
- Drive, control board or terminal board replaced
First checks, in this order
- To load the settings stored in the terminal board, set A1-03 to 5550
- To start fresh after drive replacement, initialize with A1-03 = 1110 or 2220
oPE05: Run Command / Frequency Reference Source Selection Error
Setting error: the drive will not start until it is fixedWhat it means: The run command or speed reference is assigned to a source that is not there, such as a missing option card.[1][3]
Also on: Same code on J1000.
Likely causes
- Frequency reference (b1-01 = 3) or run command (b1-02 = 3) set to an option card that is not connected
- Frequency reference set to pulse train (b1-01 = 4) but terminal RP not set for it (H6-01 above 0)
First checks, in this order
- Reconnect the option card, or change b1-01 and b1-02
- For pulse train reference set H6-01 to 0
oPE08: Parameter Selection Error
Setting error: the drive will not start until it is fixedWhat it means: A function has been set that cannot be used in the selected motor control method.[1]
Also on: Programming error, no fault output.
Likely causes
- An Open Loop Vector only function used in V/f control
- Simple V/f with PG enabled while not in V/f control
- PM motor data (E5 parameters) missing or contradictory
First checks, in this order
- Press ENTER to show U1-18
- Check the control method (A1-02) and the functions it supports
- For PM motors set the correct motor code in E5-01
oPE10: V/f Data Setting Error
Setting error: the drive will not start until it is fixedWhat it means: The V/f pattern frequencies are not in the required order, so the drive will not run.[1][3]
Also on: Same code on J1000.
Likely causes
- V/f pattern setting error in E1-04, E1-06, E1-07, E1-09 or E1-11 (E3 for motor 2)
First checks, in this order
- Correct E1-04, E1-06, E1-07, E1-09 and E1-11
- For motor 2 correct E3-04, E3-06, E3-07, E3-09 and E3-11
oPE11: Carrier Frequency Setting Error
Setting error: the drive will not start until it is fixedWhat it means: The carrier frequency limits contradict each other.[1][3]
Also on: Same code on J1000.
Likely causes
- Carrier frequency lower limit set above the upper limit (C6-04 above C6-03 with C6-05 above 6)
- Limits between C6-02 and C6-05 contradict each other
First checks, in this order
- Correct the C6 carrier frequency settings
Log it, or the same alarm comes back
A drive fault stops the motor 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, and count the alarms that repeat before they become faults.
- Reason code: the code plus the drive, for example V1000 oL1, conveyor 3 drive, so an overload that trips every hot afternoon stands out.
- 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 the four Yaskawa faults that cause most trips (oC, ov, uv1, oL1), fabrico.io has the Yaskawa 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
What does bb mean on a Yaskawa V1000?
bb means baseblock: a digital input set to External Baseblock (H1 = 8 or 9) is telling the drive to switch its output off, so the motor coasts and bb flashes. It is not a fault and nothing is stored in the fault history. Find the terminal set to 8 or 9 and check what is holding that signal; when it clears with a run command on, the drive speed searches and restarts the motor.
How do I clear an Hbb alarm on a V1000?
Hbb means the Safe Disable input between HC and H1 is open, so first check whether the machine's safety circuit has tripped and reset it. If the drive does not use Safe Disable, the factory jumper between HC and H1 must be in place. Remove the run command, close the input, then give a new run command, because Yaskawa says the safety input only releases with no run command present; if H1 is closed and Hbb stays, Yaskawa says to replace the drive.
How do I read the fault history on a V1000?
Go to the monitor menu and scroll to U2-02 for the last fault, then U2-03 to U2-17 for the frequency, current, voltage and status at the moment it tripped. U3-01 to U3-10 list the last ten faults and U3-11 to U3-20 the operating hours when each one happened. Uv1 and Uv2 are not saved in the history, and initializing the drive does not clear U2 and U3 (o4-11 does).
What is the difference between a steady and a flashing code on the V1000?
A steady code with the ALM light lit is a fault: the output is off, the motor coasts and the drive stays locked until you fix the cause and reset with the RESET key, the fault reset input (S4 by default) or a power cycle. A flashing code with a flashing ALM light is a minor fault or alarm: the drive keeps running or just refuses to start, and the code clears by itself when the cause is gone. Some codes, such as ov, oH, oL3, CE and EF1 to EF7, can appear either way depending on parameter settings.
What is H66 or alarm 66 on a Yaskawa drive?
H66 and 66 are not in Yaskawa's V1000 code list. On the drive's 7 segment display a lowercase b looks very much like a 6, so H66 is most likely Hbb (Safe Disable input open) and 66 is most likely bb (baseblock). Check which one matches your display and use those rows.
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.
- YASKAWA AC Drive V1000 Compact Vector Control Drive Technical Manual, MANUAL NO. SIEP C710606 18F
- YASKAWA AC Drive V1000 Quick Start Guide, MANUAL NO. TOEP C710606 14E (read from the Internet Archive copy of this yaskawa.com URL, snapshot 2011-10-05)
- YASKAWA AC Drive J1000 Compact V/f Control Drive Technical Manual, MANUAL NO. SIEP C710606 31D
- YASKAWA AC Drive Z1000 User Manual, MANUAL NO. TOEP YAIZ1U 03C
- YASKAWA AC Drive V1000 Option Dual Safe Disable Input Installation Manual, Type JVOP-TBVA03BWA, MANUAL NO. EZZ022486
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: VFD drive troubleshooting · electric motor · ABB ACS550 fault codes · 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: 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 | 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