Yaskawa Z1000 Drive

Yaskawa Z1000 Drive Fault Codes:

Fault Code and Meaning	Cause and Remedy
bAT HOA Keypad Battery Voltage Low	Cause: The HOA keypad battery is low. Remedy: Replace the HOA keypad battery.
bUS Option Communication Error	Cause: The connection was lost after establishing initial communication, or wiring/noise issues. Remedy: Check for faulty wiring or disconnected cables. Correct the wiring and repair short circuits as needed. Check options to minimize noise effects. Counteract noise in control/main circuits and ground wiring. Ensure other equipment (switches/relays) does not cause noise; use surge absorbers. Use recommended shielded cables and ground the shield. Separate communication wiring from drive power lines. Replace the option card if wiring is fine but error persists. Reinstall option card if connector pins do not line up.
CE MEMOBUS/Modbus Communication Error	Cause: Control data was not received for the CE detection time (H5-09). Faulty wiring or noise. Remedy: Check for faulty wiring or disconnected cables. Correct the wiring. Counteract noise in control/main circuits and ground wiring. Use shielded lines and ground the shield properly. Ensure other equipment does not cause noise; use surge suppressors. Separate communication wiring from drive power lines.
CoF Current Offset Fault	Cause: Residual induction current (e.g., sudden deceleration/coasting) or damaged current sensor. Remedy: Create a motor restart sequence allowing time for residual voltage to dissipate. Enable Speed Search at start (b3-01 = 1). Use multi-function terminals to execute External Speed Search 1 and 2. If problem continues, replace the control board or entire drive.
CPF00 or CPF01 Control Circuit Error	Cause: Self-diagnostic error in control circuit or connector damage. Remedy: Cycle power to the drive. If problem continues, replace the control board or entire drive. Replace the operator if connector is damaged.
CPF02 A/D Conversion Error	Cause: An A/D conversion error or control circuit error occurred. Remedy: Cycle power to the drive. If problem continues, replace the control board or entire drive.
CPF03 Control Board Connection Error	Cause: Connection error between control board and drive, or noise interference. Remedy: Turn off power and check connection between control board and drive. Counteract noise in control/main circuits and ground wiring. Use shielded lines and ground the shield properly. Separate communication wiring from drive power lines. If problem continues, replace control board or entire drive.
CPF06 EEPROM Memory Data Error	Cause: Error in data saved to EEPROM, or power switched off while saving. Remedy: Turn off power and check connection between control board and drive. If problem continues, replace the control board or entire drive. Reinitialize the drive using parameter A1-03.
CPF07 Terminal Board Connection Error	Cause: Faulty connection between the terminal board and the control board. Remedy: Turn off power and check connection between control board and drive. If problem continues, replace the control board or entire drive.
CPF08 Terminal Board Connection Error	Cause: Faulty connection between the terminal board and the control board. Remedy: Turn off power and check connection between control board and drive. If problem continues, replace the control board or entire drive.
CPF20 or CPF21 Control Circuit Error	Cause: Hardware is damaged. Remedy: Cycle power to the drive. If problem continues, replace the control board or entire drive.
CPF22 Hybrid IC Failure	Cause: Hybrid IC failure on the power board. Remedy: Cycle power to the drive. If problem continues, replace the power board or entire drive.
CPF23 Control Board Connection Error	Cause: Hardware is damaged. Remedy: Turn off power and check connection between control board and drive. If problem continues, replace the control board or entire drive.
CPF24 Drive Unit Signal Fault	Cause: Drive capacity cannot be detected correctly. Hardware damaged. Remedy: If problem continues, replace the control board or entire drive.
CPF46 Terminal Board Error	Cause: The installed terminal board is not a Z1000 terminal board. Remedy: Remove the unsupported terminal board and replace with a Z1000 terminal board.
EF0 Option Card External Fault	Cause: External fault received from PLC and F6-03 is not 3, or PLC program problem. Remedy: Remove the cause of the external fault. Remove the external fault input from the PLC. Check the PLC program and correct problems.
EF1 to EF7 External Fault (Input Terminals S1-S7)	Cause: An external device tripped an alarm function. Remedy: Remove the cause of the external fault and reset the fault. Properly connect signal lines assigned for external fault detection. Check for unused terminals set for External Fault (H1-xx = 20 to 2F) and change settings.
Err EEPROM Write Error	Cause: Noise corrupted data while writing, or hardware problem. Remedy: Press “ENTER” on the HOA keypad. Correct the parameter setting. Cycle power to the drive. If problem continues, replace control board or entire drive.
FAn Internal Fan Fault	Cause: Internal cooling fan malfunction or fault in fan power supply. Remedy: Cycle power to the drive. Check for fan operation. Verify cumulative fan time (U4-03) and maintenance timer (U4-04). Replace cooling fan if damaged or life exceeded. If fault persists, replace power board/gate drive board or entire drive.
Fn1 External Fan Fault	Cause: External cooling fan has malfunctioned. Remedy: Cycle power to the drive. Check for fan operation. Verify cumulative fan time and maintenance timer. Replace cooling fan if damaged or life exceeded.
FbH Excessive PI Feedback	Cause: PI feedback input is greater than b5-36 level for longer than b5-37 time. Remedy: Check b5-36 and b5-37 settings. Correct the wiring. Check the sensor on the control side. Replace the sensor if damaged.
FbL PI Feedback Loss	Cause: PI feedback level is below detection level (b5-13) for longer than set time (b5-14). Remedy: Check b5-13 and b5-14 settings. Correct the wiring. Check the sensor on the control side and replace if damaged.
GF Ground Fault	Cause: Current short to ground exceeded 50% of rated current. Motor insulation damaged, cable short, or leakage. Remedy: Check motor insulation resistance and replace motor if needed. Check motor cable for shorts and replace if needed. Reduce carrier frequency or stray capacitance. If starting into coasting motor: Set b3-01 to 1 (Speed Search). If problem continues, replace control board or entire drive.
LF Output Phase Loss	Cause: Phase loss on output side. Cable disconnected, winding damaged, or loose terminal. Remedy: Check for wiring errors and connect output cable. Check resistance between motor lines; replace motor if winding damaged. Apply proper tightening torque to terminals. Check drive and motor capacities (motor < 5% of drive rating). Replace control board or entire drive if transistor damaged. Note: Drive cannot operate a single-phase motor.
LF2 Output Current Imbalance	Cause: One or more phases in output current lost. Loose wires or faulty wiring. Remedy: Check for faulty wiring or poor connections on output side. Apply proper tightening torque to terminals.
The output circuit is damaged (Display may vary)	Cause: Motor impedance or motor phases are uneven. Remedy: If problem continues, replace control board or entire drive. Measure line-to-line resistance for each motor phase. Ensure values match. Replace the motor.
nSE Node Setup Error	Cause: Node setup terminal closed during run. Remedy: Stop the drive when using the node setup function.
oC Overcurrent	Cause: Output current greater than specified level. Short circuit, load too heavy, accel time too short. Remedy: Check insulation resistance and replace motor if needed. Check motor cables for shorts and replace if needed. Measure current flowing into motor; replace with larger capacity drive if needed. Reduce load or avoid sudden changes. Increase acceleration time (C1-01/C1-03) or S-curve characteristics. Check motor capacity matches drive. Set up operation sequence so magnetic contactor (MC) does not trip while drive outputs current. Check V/f settings (E1-04 to E1-10). Reduce torque compensation gain (C4-01). Check for noise interference on control lines. Reduce Overexcitation Deceleration Gain (n3-13). Enable Speed Search (b3-01 = 1) if starting on coasting motor.
oFA00 Option Card Connection Error at Option Port CN5 (Option compatibility error)	Cause: The option card installed into port CN5 is incompatible with the drive. Remedy: Check if the drive supports the option card to be installed. Contact Yaskawa for assistance.
oFA01 Option Card Fault at Option Port CN5 (Option not properly connected)	Cause: The option card connection to port CN5 is faulty. Remedy: Turn off the power and reconnect the option card. Check if the option card is properly plugged into the option port. Make sure the card is fixed properly.
oFA05, oFA06 oFA10, oFA11 oFA12 to oFA17 oFA30 to oFA43 Option Card Error Occurred at Option Port CN5	Cause: Option card or hardware is damaged. Remedy: Cycle power to the drive. If the problem continues, replace the control board or the entire drive. Contact Yaskawa or a Yaskawa representative for instructions on replacing the control board.
oH Heatsink Overheat	Cause: 1. Surrounding temperature is too high. 2. Load is too heavy. 3. External cooling fan is stopped. Remedy: Check the temperature surrounding the drive. Verify temperature is within drive specifications. Improve air circulation or install a fan/air conditioner. Remove heat sources near the drive. Measure output current and decrease the load. Lower the carrier frequency (C6-02). Replace the cooling fan. After replacing fan, set parameter o4-03 to 0.
oH1 Overheat 1 (Heatsink Overheat) Heatsink temperature exceeded drive overheat level.	Cause: Surrounding temperature is too high or Load is too heavy. Remedy: Check temperature surrounding the drive. Improve air circulation within the enclosure panel. Install a fan or air conditioner. Measure the output current and reduce the load. Lower the carrier frequency (C6-02).
oH3 Motor Overheat Alarm (PTC Input)	Cause: Motor overheat signal to analog input terminals A1 or A2 exceeded alarm detection level. (Note: Detection requires setting multi-function analog inputs H3-02 or H3-10 to E). Remedy: Check the size of the load, accel/decel times, and cycle times. Decrease the load. Check the motor rated current and E2-01 setting. Ensure motor cooling system is operating normally.
oH4 Motor Overheat Fault (PTC Input)	Cause: The motor overheat signal to analog input A1 or A2 exceeded the fault detection level. Motor has overheated. Remedy: Check the size of the load, accel/decel times, and cycle times. Decrease the load. Increase acceleration and deceleration times (C1-01 through C1-04). Adjust V/f pattern (E1-04 to E1-10) by reducing E1-08 and E1-10 (do not set too low). Check motor rated current and parameter E2-01. Repair or replace motor cooling system.
oL1 Motor Overload (Electronic motor overload protection tripped)	Cause: Load too heavy, cycle times too short, output voltage too high, wrong motor current set, or overexcitation. Remedy: Reduce the load. Increase acceleration and deceleration times (C1-01 through C1-04). If operating at low speeds with high load, increase motor capacity. Adjust user-set V/f pattern (E1-04 to E1-10). Check motor nameplate and correct parameter E2-01 (Motor Rated Current). Verify Base Frequency (E1-06). If multiple motors, set L1-01 to 0 and install thermal relays. Reduce excitation deceleration gain (n3-13).
oL2 Drive Overload (Thermal sensor triggered overload protection)	Cause: Load too heavy, Accel/Decel too short, Output voltage too high, Drive capacity too small, or excessive torque compensation. Remedy: Reduce the load. Increase acceleration and deceleration times (C1-01 through C1-04). Adjust V/f pattern (reduce E1-08 and E1-10). Replace the drive with a larger model. Lower the carrier frequency (C6-02). Reduce torque compensation gain (C4-01). Adjust Speed Search parameters (b3-02, b3-03). Check power supply for phase loss.
oL3 Overtorque Detection 1	Cause: Current exceeded value in L6-02 for longer than time in L6-03. Parameter settings incorrect or machine fault (locked up). Remedy: Check L6-02 and L6-03 settings. Check the status of the load. Remove the cause of the fault (e.g., machine lock-up).
oL7 High Slip Braking oL	Cause: Output frequency stayed constant longer than time set in n3-04. Excessive load inertia. Remedy: Reduce deceleration times (C1-02, C1-04) for applications not using High Slip Braking. Increase parameter n3-04 (High-slip Braking Overload Time). Install a thermal relay and increase n3-04 to maximum value.
oPr HOA Keypad Connection Fault	Cause: HOA keypad disconnected from drive while output is interrupted, Run command assigned to keypad, or Sequence timer active. Remedy: Check the connection between the operator and the drive. Replace the cable if damaged. Turn off drive input power, disconnect operator, reconnect, and reapply power.
ov Overvoltage (DC bus voltage exceeded detection level)	Cause: Decel time too short, regenerative energy flowing back, ground fault, noise interference, or load inertia set incorrectly. Remedy: Increase deceleration time (C1-02, C1-04). Enable stall prevention (L3-04 = 1). Install a braking resistor or unit if necessary. Check motor wiring for ground faults. Check Speed Search settings (b3-19, b3-02, b3-03). Check input power voltage is within limits. Adjust load inertia ratio (L3-25). Set gain for Hunting Prevention (n1-02).
ov2 Overvoltage 2 (Bus voltage boosted because motor cable is too long)	Cause: The motor wiring is too long. Remedy: Shorten the shielded motor cable. Lower the carrier frequency. Switch on the internal EMC filter if the power supply has a neutral ground.
PF Input Phase Loss	Cause: Phase loss in drive input power, loose wiring, excessive voltage fluctuation, or poor balance between phases. Remedy: Check for wiring errors in main circuit drive input. Ensure terminals are tightened to specified torque. Check voltage from drive input power. Check maintenance time for capacitors (U4-05) and replace if necessary.
SEr Too Many Speed Search Restarts	Cause: Number of Speed Search restarts exceeded b3-19. Parameters wrong or motor coasting in opposite direction. Remedy: Reduce detection compensation gain (b3-10). Increase current level for Speed Search (b3-17). Increase detection time (b3-18). Set b3-14 to 1 to enable Bi-Directional Speed Search.
STo Motor Pull Out or Step Out Detection	Cause: Motor exceeded pull-out torque. Load heavy, accel/decel too short, or speed response too slow. Remedy: Increase load inertia for PM motor (n8-55). Increase pull-in current (n8-51). Reduce the load or increase motor/drive capacity. Increase accel/decel times (C1-01 to C1-04).
TdE Time Data Error	Cause: Error in Real-Clock Time function of HOA keypad or communication error. Remedy: Replace the HOA keypad. Contact Yaskawa or sales representative.
TIM Time Not Set	Cause: Real-Time Clock not set (new drive or reset). Remedy: Set the time for the HOA keypad (Parameter o4-17 = 1). Cycle power and set Real Time Clock within 30 seconds of power-up.
UL3 Undertorque Detection 1	Cause: Current fell below minimum value (L6-02) for longer than allowable time (L6-03). Remedy: Check settings of parameters L6-02 and L6-03. Check the load for any problems (e.g., broken belt/coupling).
UL6 Motor Underload	Cause: Weight of load fell below underload curve defined in L6-14. Remedy: Adjust value in L6-14 so output current remains above motor underload curve during normal operation.
Uv1 DC Bus Undervoltage	Cause: Input phase loss, loose terminals, voltage problem, main circuit capacitors worn, or soft-charge bypass relay damaged. Remedy: Check input power wiring and correct errors. Tighten loose terminals. Check voltage is within range. Check magnetic contactor on main circuit. Check capacitor maintenance time (U4-05). Replace if >90%. Cycle power. If fault reoccurs, replace control board or drive.
Uv2 Control Power Supply Voltage Fault	Cause: Voltage too low for control drive input power. Internal circuitry damaged. Remedy: Cycle power to the drive. Check if fault reoccurs. If problem continues, replace control board or entire drive.
Uv3 Undervoltage 3 (Soft-Charge Circuit Fault)	Cause: The soft-charge bypass circuit failed (relay or contactor damaged). Remedy: Cycle power to the drive. Check monitor U4-06 for soft-charge bypass life. Replace control board or entire drive if U4-06 exceeds 90% or fault persists.
voF Output Voltage Detection Fault	Cause: Problem detected with voltage on output side. Hardware is damaged. Remedy: Replace the control board or the entire drive. Contact Yaskawa for assistance.
bb Baseblock	Cause: External baseblock signal was entered via one of the multi-function input terminals (S1 to S7). Remedy: Check external sequence and baseblock signal input timing.
bUS Option Communication Error	Cause: Connection is broken, master controller stopped communicating, option is damaged, option not properly connected, or data error due to noise. Remedy: Check for faulty wiring or disconnected cables. Check for short circuits and repair as needed. If wiring is good but fault persists, replace the option. Ensure connector pins on the option are properly lined up with the drive. Take steps to counteract noise in control circuit, main circuit, and ground wiring. Use surge absorbers on magnetic contactors. Use shielded lines and ground the shield properly.
CALL Serial Communication Transmission Error	Cause: Communications wiring is faulty, short circuit, programming error on master side, circuitry damaged, or termination resistor incorrect. Remedy: Check for wiring errors, disconnected cables, or short circuits. Check communications at start-up and correct programming errors. Perform a self-diagnostics check. If problem continues, replace control board or entire drive. Install termination resistor at both ends of communication line (DIP switch S2 to ON).
CE MEMOBUS/Modbus Communication Error	Cause: Control data not received correctly for two seconds. Noise, incompatible protocol, CE detection time too short, or cable disconnected. Remedy: Minimize effects of noise (check grounding, shielded lines, surge absorbers). Check H5 parameter settings and protocol settings in controller. Set a longer CE detection time using parameter H5-09. Check the PLC software settings. Check the connector to ensure cable has signal or replace cable.
CrST Cannot Reset	Cause: Fault reset was being executed when a Run command was entered. Remedy: Ensure that a Run command cannot be entered from external terminals or option during fault reset. Turn off the Run command.
dnE Drive Disabled	Cause: “Drive Enable” is set to a multi-function contact input (H1-xx = 6A) and that signal was switched off. Remedy: Check the operation sequence.
EF Forward/Reverse Run Command Input Error	Cause: Sequence error: Both forward run and reverse run closed simultaneously for longer than 0.5 s. Remedy: Check the forward and reverse command sequence and correct the problem. Note: Motor ramps to stop when detected.
EF0 Option Card External Fault	Cause: An external fault condition is present (received from PLC with F6-03 set to 3) or problem with PLC program. Remedy: Remove the cause of the external fault. Remove the external fault input from the PLC. Check the PLC program and correct problems.
EF1 to EF7 External Fault (Input Terminal S1 to S7)	Cause: An external device has tripped an alarm function, wiring is incorrect, or multi-function inputs set incorrectly. Remedy: Remove the cause of the external fault and reset the multi-function input value. Ensure signal lines are connected properly to terminals assigned for external fault detection (H1-xx = 20 to 2F). Reconnect the signal line. Check if unused terminals have been set for External Fault and change settings if needed.
FbH Excessive PI Feedback	Cause: PI feedback input is higher than level set to b5-36 for time set to b5-37. Incorrect parameters, faulty wiring, or damaged sensor/board. Remedy: Check parameters b5-36 and b5-37. Correct the wiring. Check the sensor and replace if damaged. Replace control board or entire drive if input circuit is damaged.
FbL PI Feedback Loss	Cause: PI feedback input is lower than level set to b5-13 for time set to b5-14. Incorrect parameters, faulty wiring, or damaged sensor/board. Remedy: Check parameters b5-13 and b5-14. Correct the wiring. Check the sensor and replace if damaged. Replace control board or entire drive if input circuit is damaged.
HCA Current Alarm	Cause: Drive current exceeded overcurrent warning level (150% of rated current). Load too heavy, acceleration times too short, or wrong motor capacity. Remedy: Reduce the load for applications with repetitive operations. Calculate torque required and increase acceleration/deceleration times (C1-01 to C1-04). Increase the capacity of the drive. Check motor capacity and ensure it is within allowable range.
inTLK Interlock Open	Cause: BAS Interlock multi-function input is open. Remedy: Check the cause of interlock.
LT-1 Cooling Fan Maintenance Time	Cause: The cooling fan has reached 90% of its expected performance life. Remedy: Replace the cooling fan. Set o4-03 to 0 to reset the Maintenance Monitor.
LT-2 Capacitor Maintenance Time	Cause: The main circuit and control circuit capacitors have reached 90% of their expected performance lives. Remedy: Replace either the control board or the entire drive. Contact Yaskawa or sales representative.
LT-3 Soft Charge Bypass Relay Maintenance Time	Cause: The DC bus soft charge relay has reached 90% of expected performance life. Remedy: Replace either the control board or the entire drive. Contact Yaskawa or sales representative.
LT-4 IGBT Maintenance Time (50%)	Cause: IGBTs have reached 50% of their expected performance life. Remedy: Check the load, carrier frequency, and output frequency.
oH Heatsink Overheat	Cause: Heatsink temperature exceeded L8-02 level. Surrounding temp too high, fan stopped, or airflow restricted. Remedy: Check surrounding temperature and improve air circulation. Install fan or AC to cool area. Replace cooling fan if stopped. Clear debris clogging the fan or restricting air circulation.
oH2 Drive Overheat Warning	Cause: “Drive Overheat Warning” was input to a multi-function input terminal (H1-xx = B). Remedy: Search for the device that tripped the overheat warning. Remove the cause of the problem.
oH3 Motor Overheat	Cause: Motor overheat signal (PTC input) exceeded alarm level. Wiring faulty, machine locked, load too high, or V/f pattern incorrect. Remedy: Repair the PTC input wiring. Check status of machine (e.g. if locked up). Decrease load or increase accel/decel times. Adjust preset V/f pattern (E1-04 through E1-10). Ensure motor cooling system is operating normally.
oL3 Overtorque 1	Cause: Drive output current > L6-02 for longer than L6-03. Inappropriate parameters or machine locked. Remedy: Check parameters L6-02 and L6-03. Check the status of the machine. Remove the cause of the fault.
ov DC Bus Overvoltage	Cause: DC bus voltage exceeded trip point (approx 410V for 200V class / 820V for 400V class). Surge voltage, short circuit, or noise. Remedy: Install an AC reactor. Check motor power cable and terminals for short circuits. Check grounding and handling of noise interference. Install surge protector to MC coil if magnetic contactor is source of noise.
PASS MEMOBUS/Modbus Comm. Test Mode Complete	Cause: MEMOBUS/Modbus test has finished normally. Remedy: This verifies that the test was successful.
SAFE Customer Safety	Cause: Customer Safeties multi-function input is open. Remedy: Check the cause of the open safety (external contact).
SE MEMOBUS/Modbus Communication Test Mode Error	Cause: A digital input set to 67H was closed while the drive was running. Remedy: Stop the drive and run the test again.
TrPC IGBT Maintenance Time (90%)	Cause: IGBTs have reached 90% of their expected performance life. Remedy: Replace the drive.
UL3 Undertorque Detection 1	Cause: Drive output current less than L6-02 for longer than L6-03. Load dropped or inappropriate parameters. Remedy: Check parameters L6-02 and L6-03. Check for broken parts in the transmission system.
UL6 Undertorque Detection 6	Cause: The load has dropped or decreased under the motor underload curve. Remedy: Check parameters L6-13 and L6-14.
Uv Undervoltage	Cause: DC bus voltage dropped below L2-05. Phase loss, loose wiring, voltage problem, internal circuitry worn, or CHARGE light broken. Remedy: Check for wiring errors in main circuit drive input power. Ensure terminals are properly tightened (torque spec). Check input voltage levels. Check maintenance time for capacitors (U4-05). Replace board if needed. Check capacity of drive input power transformer. Replace control board or drive if CHARGE light is broken.
voF Output Voltage Detection Fault	Cause: There is a problem with the output voltage (Hardware is damaged). Remedy: Replace either the control board or the entire drive.
WrUn Waiting for Run	Cause: Drive is waiting for the time set to b1-11 to pass before it can begin to operate the motor. Remedy: This is not an error.
oPE01 Drive Capacity Setting Fault	Cause: The drive model selection (o2-04) and the actual capacity of the drive are not the same. Remedy: Correct the value set to o2-04.
oPE02 Parameter Range Setting Error	Cause: Parameters were set outside the possible setting range. (Use U1-18 to find parameters set outside the range). Remedy: Set parameters to the proper values. Note: When multiple errors occur simultaneously, other errors are given precedence over oPE02.
oPE03 Multi-Function Input Selection Error	Cause: A contradictory setting is assigned to multi-function contact inputs H1-01 to H1-07. The same function is assigned to two multi-function inputs (Excludes “Not used” and “External Fault”). The Up command was set but the Down command was not, or vice versa (settings 10 vs. 11). Run/Stop command for a 2-wire sequence was set (H1-xx = 42), but Forward/Reverse command (H1-xx = 43) was not. “Drive Enable” is set to multi-function input S1 or S2 (H1-01 = 6A or H1-02 = 6A). Two contradictory functions set simultaneously (e.g., Up/Down, Hold Accel/Decel, Analog Sample/Hold, Offset Frequency). Up/Down command (10, 11) and PI control (b5-01) enabled simultaneously. Remedy: Ensure all multi-function inputs are assigned to different functions. Re-enter the multi-function settings to ensure contradictions do not occur. Properly set the functions required for use in combination with other functions. Set b5-01 to 0 to disable control PI or disable the Up/Down command if they are conflicting.
oPE05 Run Command/Frequency Reference Source Selection Error	Cause: Frequency reference is assigned to an option card (b1-01 = 3) and an input option card is not connected to the drive. The Run command is assigned to an option card (b1-02 = 3) and an input option card is not connected to the drive. Remedy: Reconnect the input option card to the drive.
oPE07 Multi-Function Analog Input Selection Error	Cause: A contradictory setting is assigned to multi-function analog inputs H3-02 or H3-10 and PI functions conflict. At least two analog input terminals are set to the same function. H3-02 or H3-10 = C (PI Target Value) while b5-18 = 1 (enables b5-19 as the target PI value). Remedy: Change the settings to H3-02 and H3-10 so that functions no longer conflict. Note: Both 0 (Frequency Reference Bias) and F (Not Used) can be set simultaneously. Disable one of the PI selections.
oPE08 Parameter Selection Error	Cause: A function has been set that cannot be used in the motor control method selected. In OLV/PM, parameters E5-02 to E5-07 are set to 0. Contradictory settings in OLV/PM regarding E5-03, E5-09, or E5-24. L6-02 (Torque Detection Level 1) is set lower than L6-14 (Motor Underload Protection). Remedy: When using a special-purpose motor, set E5-xx parameters in accordance with the test report provided. Set E5-09 or E5-24 to the correct value, and set the other to 0. Set the motor rated current for PM to 0 (E5-03). Adjust the parameter values so that L6-14 ≥ L6-02.
oPE09 PI Control Selection Fault	Cause: PI control function selection is incorrect (Requires b5-01 = 1 or 3). b5-15 is not set to 0.0 while stopping method is DC Injection or Coast with timer (b1-03 = 2 or 3). b5-01 set to 1, but lower limit (d2-02) not 0 while reverse output enabled (b5-11 = 1). b5-01 set to 3, but lower limit (d2-01) is not 0. Remedy: Set b5-15 to a value other than 0.0. Set the stopping method to coast to stop or ramp to stop (b1-03 = 0 or 1). Correct the parameter settings for d2-02, d2-01, or b5-xx to remove conflicts.
oPE10 V/f Data Setting Error	Cause: One of the following V/f setting errors has occurred: E1-04 ≥ E1-06 E1-06 ≥ E1-07 E1-07 ≥ E1-09 Or E1-09 ≥ E1-11 Remedy: Correct the settings for E1-04, E1-06, E1-07, E1-09, and E1-11.
oPE11 Carrier Frequency Setting Error	Cause: The following contradictory settings occurred: C6-05 > 6 and C6-04 > C6-03 (carrier frequency lower limit is greater than the upper limit). The upper and lower limits between C6-02 and C6-05 are contradictory. Remedy: Correct the setting for the carrier frequency. Ensure upper and lower limits are logically set.
oPE16 Energy Saving Constants Error	Cause: The following contradictory settings are true: A1-02 = 0, S1-01 = 1, and b8-01 = 1. Remedy: Correct the parameter settings.
oPE27 BP Program Error	Cause: Bypass mode is not correctly configured. If digital inputs A4, A5, or A7 or digital outputs A4 or A5 are programmed, then all must be programmed. Conflict between H1-0x (3-Wire), L5-01, S4-01, and Drive Enable settings relative to A6. Remedy: Correct the parameter settings.
oPE28 Sequence Timer Error	Cause: One or more of the sequence timers is not set in the correct order. S2-01 > S2-02 S2-06 > S2-07 S2-11 > S2-12 S2-16 > S2-17 Remedy: Correct the parameter settings to ensure start times are less than end times.
oPE29 Baud Rate Setting Error	Cause: The baud rate setting (H5-02) is not compatible with currently selected protocol (H5-08). H5-08 = 1 and H5-02 ≠ 3 H5-08 = 2 and H5-02 ≠ 2, 3 H5-08 = 3 and H5-02 ≠ 3, 4, 5, 7 Remedy: Correct the parameter settings.
End3 Rated Current Setting Alarm	Cause: The correct current rating printed on the motor nameplate was not entered into T1-04. Remedy: Check the setting of parameter T1-04. Check the motor data and repeat Auto-Tuning.
End4 Adjusted Slip Calculation Error	Cause: The calculated slip is outside the allowable range. Remedy: Make sure the data entered for Auto-Tuning is correct.
End5 Resistance Tuning Error	Cause: The calculated resistance value is outside the allowable range. Remedy: Double-check the data entered for the Auto-Tuning process. Check the motor and motor cable connection for faults.
End7 No-Load Current Alarm	Cause: The entered no-load current value was outside the allowable range. Auto-Tuning results were less than 5% of the motor rated current. Remedy: Check and correct faulty motor wiring. Double-check the data entered for the Auto-Tuning process.
Er-01 Motor Data Error	Cause: Motor data or data entered during Auto-Tuning was incorrect. Motor output power and motor-rated current settings (T1-02 and T1-04) do not match. Motor rated current and detected no-load current are inconsistent. Base frequency and motor rated speed (T1-05 and T1-07) do not match. Remedy: Make sure motor data entered to T1-xx match motor nameplate information. Restart Auto-Tuning and enter the correct information. Check the drive and motor capacities. Correct the settings of parameters T1-02 and T1-04. Check the motor rated current and no-load current. Correct the settings of parameters T1-04 and E2-03. Correct the settings of parameters T1-05 and T1-07. Check that the correct number of poles were entered to T1-06.
Er-02 Minor Fault	Cause: An alarm was triggered during Auto-Tuning. Remedy: Exit the Auto-Tuning menu. Check the alarm code. Remove the alarm cause and restart Auto-Tuning.
Er-03 OFF Button Input	Cause: Auto-Tuning canceled by pressing the OFF button. Remedy: Auto-Tuning did not complete properly. Restart Auto-Tuning.
Er-04 Line-to-Line Resistance Error	Cause: Motor data entered during Auto-Tuning was incorrect. Results from Auto-Tuning are outside the parameter setting range or the tuning process took too long. Faulty motor cable or cable connection. Remedy: Make sure motor data entered to T1-xx match motor nameplate information. Restart Auto-Tuning and enter the correct information. Check and correct faulty motor wiring.
Er-05 No-Load Current Error	Cause: Motor data entered during Auto-Tuning was incorrect. Results from Auto-Tuning are outside the parameter setting range or the tuning process took too long. Remedy: Make sure motor data entered to T1-xx match motor nameplate information. Restart Auto-Tuning and enter the correct information. Check and correct faulty motor wiring.
Er-08 Rated Slip Error	Cause: Motor data entered during Auto-Tuning was incorrect. Results from Auto-Tuning are outside the parameter setting range or the tuning process took too long. Remedy: Make sure motor data entered to T1-xx match motor nameplate information. Restart Auto-Tuning and enter the correct information. Check and correct faulty motor wiring.
Er-09 Acceleration Error	Cause: The motor did not accelerate for the specified acceleration time. Remedy: Increase the acceleration time (C1-01). Disconnect the machine from the motor if possible.
Er-12 Current Detection Error	Cause: One of the motor phases is missing (U/T1, V/T2, W/T3). The current exceeded the current rating of the drive. The current is too low. Attempted Auto-Tuning without motor connected to the drive. Current detection signal error. Remedy: Check motor wiring and correct any problems. Check motor wiring for a short between motor lines. Close any magnetic contactors used between motors. Replace the control board or the entire drive. Connect the motor and restart Auto-Tuning.
CoPy Writing Parameter Settings (flashing)	Cause: Parameters are being written to the drive. Remedy: This is not an error.
CPEr Control Mode Mismatch	Cause: Control mode of the parameters to be loaded onto the drive and the control mode set to the drive do not match. Remedy: Verify the control mode for the parameters to be loaded onto the drive and the control mode on the drive to which those parameters will be written. Set the same control mode using parameter A1-02 and retry.
CPyE Error Writing Data	Cause: Failed writing parameters. Remedy: Attempt to write parameters again.
CSEr Copy Unit Error	Cause: Hardware fault. Remedy: Replace the operator or the USB Copy Unit.
dFPS Drive Model Mismatch	Cause: The drives used in the copy and write process are not the same model. – The drive from which the parameters were copied is a different model. – The drive to be written to is a different model. Remedy: Verify the model number of the drive from which the parameters were copied and the model of the drive to which those parameters will be written. Make sure the two drives are the same model and have the same software version.
End Task Complete	Cause: Finished reading, writing, or verifying parameters. Remedy: This is not an error.
iFEr Communication Error	Cause: A communication error occurred between the drive and the operator or the USB copy unit. A non-compatible cable is being used to connect the USB Copy Unit and the drive. Remedy: Check the cable connection. Use the cable originally packaged with the USB Copy Unit.
ndAT Model, Voltage Class, Capacity Mismatch	Cause: The drive from which the parameters were copied and the drive to which the parameters will be written have different electrical specifications, capacities, are set to different control modes, or are different models. The device being used to write the parameters is blank and does not have any parameters saved on it. Remedy: Make sure model numbers and specifications are the same for both drives. Make sure all connections are correct, and copy the parameter settings onto the USB Copy Unit or the operator.
rdEr Error Reading Data	Cause: Failed while attempting to read parameter settings from the drive. Remedy: Press and hold the READ key on the USB Copy Unit for at least one second to have the unit read parameters from the drive.
rEAd Reading Parameter Settings (flashing)	Cause: Displayed while the parameter settings are being read onto the USB Copy Unit. Remedy: This is not an error.
vAEr Voltage Class, Capacity Mismatch	Cause: The drive from which the parameters were copied and the drive on which the Verify mode is being performed have different electrical specifications or are a different capacity. Remedy: Make sure electrical specifications and capacities are the same for both drives.
vFyE Parameter settings mismatch	Cause: Indicates that the parameter settings that have been Read and loaded onto the Copy Unit or HOA Keypad are different from the drive. Remedy: To synchronize parameters, either write the parameters saved on the USB Copy Unit or HOA keypad onto the drive, or Read the parameter settings on the drive onto the USB Copy Unit.
vrFy Comparing Parameter Settings (flashing)	Cause: The Verify mode has confirmed that parameters settings on the drive and parameters read to the copy device are identical. Remedy: This is not an error.