Yaskawa HV600 Drive – Drivefault

Yaskawa HV600 Drive Fault Codes:

Fault Code and Meaning	Cause and Remedy
AUXFB PI Aux Feedback Level Loss	Cause: The analog input from the terminal set for PI Auxiliary Control Feedback Level [H3-xx = 27] is more than 21 mA or less than 3 mA for longer than 1 s. Remedy: Repair transducer or wiring. Note: Do a Fault Reset to clear the fault.
bAT Keypad Battery Low Voltage	Cause: The keypad battery voltage is low. Remedy: Replace the keypad battery. Note: Use o4-24 [bAT Detection Selection] to enable/disable bAT detection.
bCE Bluetooth Communication Fault	Cause: The smartphone or tablet with DriveWizard Mobile or DriveWizard installed is too far from the keypad. Radio waves from a different device are causing interference with communications between the smartphone or tablet and keypad. Remedy: Use the smartphone or tablet 10 m (32.8 ft) or nearer to the keypad. Make sure that no device around the keypad uses the same radio bandwidth (2400 MHz to 2480 MHz), and prevent radio interference. Note: Do a Fault Reset to clear the fault. Set stopping method in o2-27.
bUS Option Communication Error	Cause: The drive did not receive a signal from the controller. The communications cable wiring is incorrect. There is a short-circuit in the communications cable or the cable is not connected. Electrical interference caused a communication data error. The option is incorrectly installed to the drive. The option is damaged. Remedy: Correct wiring errors. Repair short circuits and connect cables. Replace the defective communications cable. Examine control circuit lines, main circuit lines, and ground wiring to decrease interference. Ensure magnetic contactor is not source of interference (use Surge Protective Device). Use recommended shielded cables. Ground the shield. Separate communication wiring from power lines; install noise filter. Correctly install the option to the drive. If fault continues and wiring is correct, replace the option.
CE Modbus Communication Error	Cause: The communications cable wiring is incorrect. There is a short circuit in the communications cable or the cable is not connected. Electrical interference caused a communication data error. Remedy: Correct wiring errors. Repair short circuits and connect cables. Replace the defective communications cable. Examine lines and ground wiring to decrease interference. Use Surge Protective Device on magnetic contactors if necessary. Use shielded lines and ground the shield correctly. Note: The drive detects this error based on CE detection time set in H5-09.
CoF Current Offset Fault	Cause: The drive starts operation while the induced voltage stays in the motor (during coasting to a stop or after fast deceleration). A drive hardware problem occurred. Remedy: Make a sequence that does not restart operation when induced voltage stays in the motor. Set b3-01 = 1 [Speed Search at Start Selection = Enabled]. Use Speed Search from Fmax or Fref [H1-xx = 61, 62]. Do a Fault Reset to clear the fault or de-energize the drive. If the fault stays, replace the drive.
CPF00 Control Circuit Error	Cause: A drive hardware problem occurred. Remedy: Re-energize the drive. If the fault stays, replace the control board or the drive. Contact Yaskawa or sales representative.
CPF01 Control Circuit Error	Cause: A drive hardware problem occurred. Remedy: Re-energize the drive. If the fault stays, replace the control board or the drive.
CPF02 Control Circuit Error	Cause: A drive hardware problem occurred. Remedy: Re-energize the drive. If the fault stays, replace the control board or the drive.
CPF03 Control Circuit Error	Cause: A drive hardware problem occurred. Remedy: Re-energize the drive. If the fault stays, replace the control board or the drive.
CPF06 Control Circuit Error (EEPROM memory Data Error)	Cause: The drive power supply was de-energized while a communication option entered a parameter Write command. An EEPROM peripheral circuit error occurred. Remedy: Set A1-03 = 2220 or 3330 (Initialize Parameters) and initialize the drive. Re-energize the drive. If the fault stays, replace the control board or the drive.
CPF07 Control Circuit Error	Cause: A drive hardware problem occurred. Remedy: Re-energize the drive. If the fault stays, replace the control board or the drive.
CPF08 Control Circuit Error	Cause: A drive hardware problem occurred. Remedy: Re-energize the drive. If the fault stays, replace the control board or the drive.
CPF11 Control Circuit Error	Cause: A drive hardware problem occurred. Remedy: Re-energize the drive. If the fault stays, replace the control board or the drive.
CPF12 Control Circuit Error	Cause: A drive hardware problem occurred. Remedy: Re-energize the drive. If the fault stays, replace the control board or the drive.
CPF13 Control Circuit Error	Cause: A drive hardware problem occurred. Remedy: Re-energize the drive. If the fault stays, replace the control board or the drive.
CPF14 Control Circuit Error	Cause: A drive hardware problem occurred. Remedy: Re-energize the drive. If the fault stays, replace the control board or the drive.
CPF16 Control Circuit Error	Cause: A drive hardware problem occurred. Remedy: Re-energize the drive. If the fault stays, replace the control board or the drive.
CPF17 Control Circuit Error	Cause: A drive hardware problem occurred. Remedy: Re-energize the drive. If the fault stays, replace the control board or the drive.
CPF18 Control Circuit Error	Cause: A drive hardware problem occurred. Remedy: Re-energize the drive. If the fault stays, replace the control board or the drive.
CPF19 Control Circuit Error	Cause: A drive hardware problem occurred. Remedy: Re-energize the drive. If the fault stays, replace the control board or the drive.
CPF20 Control Circuit Error	Cause: A drive hardware problem occurred. Remedy: Re-energize the drive. If the fault stays, replace the control board or the drive.
CPF21 Control Circuit Error	Cause: A drive hardware problem occurred. Remedy: Re-energize the drive. If the fault stays, replace the control board or the drive.
CPF22 Control Circuit Error	Cause: A drive hardware problem occurred. Remedy: Re-energize the drive. If the fault stays, replace the control board or the drive.
CPF23 Control Circuit Error	Cause: A drive hardware problem occurred. Remedy: Re-energize the drive. If the fault stays, replace the control board or the drive.
CPF24 Control Circuit Error (Drive Unit Signal Fault)	Cause: A drive hardware problem occurred. Remedy: Re-energize the drive. If the fault stays, replace the control board or the drive.
CPF26 Control Circuit Error	Cause: A drive hardware problem occurred. Remedy: Re-energize the drive. If the fault stays, replace the control board or the drive.
CPF27 Control Circuit Error	Cause: A drive hardware problem occurred. Remedy: Re-energize the drive. If the fault stays, replace the control board or the drive.
CPF28 Control Circuit Error	Cause: A drive hardware problem occurred. Remedy: Re-energize the drive. If the fault stays, replace the control board or the drive.
CPF29 Control Circuit Error	Cause: A drive hardware problem occurred. Remedy: Re-energize the drive. If the fault stays, replace the control board or the drive.
CPF30 Control Circuit Error	Cause: A drive hardware problem occurred. Remedy: Re-energize the drive. If the fault stays, replace the control board or the drive.
CPF31 Control Circuit Error	Cause: A drive hardware problem occurred. Remedy: Re-energize the drive. If the fault stays, replace the control board or the drive.
CPF32 Control Circuit Error	Cause: A drive hardware problem occurred. Remedy: Re-energize the drive. If the fault stays, replace the control board or the drive.
CPF33 Control Circuit Error	Cause: A drive hardware problem occurred. Remedy: Re-energize the drive. If the fault stays, replace the control board or the drive. Contact Yaskawa or your nearest sales representative.
CPF34 Control Circuit Error	Cause: A drive hardware problem occurred. Remedy: Re-energize the drive. If the fault stays, replace the control board or the drive.
CPF35 – CPF39 Control Circuit Error	Cause: A drive hardware problem occurred. Remedy: Re-energize the drive. If the fault stays, replace the control board or the drive.
dEv Speed Deviation	Cause: The load is too heavy. Acceleration and deceleration times are set too short. The dEv detection level settings are incorrect. The load is locked up. Remedy: Decrease the load. Increase the values set in C1-01 to C1-04 [Acceleration/Deceleration Time]. Adjust F1-10 [Speed Deviation Detection Level] and F1-11. Examine the machine. Release the holding brake.
DIFF Differential Feedback Exceeded	Cause: The difference between the PID Feedback and Differential Level Source is more than the level set in Y4-18 for the time set in Y4-19. Remedy: Replace the feedback transducer or transducers. Make sure that the settings of Y4-18 to Y4-20 are correct.
dv7 Polarity Judge Timeout	Cause: There is a disconnection in the motor coil winding. The screws on the drive output terminals are loose. Remedy: Measure the motor line-to-line resistance and replace the motor if a coil is disconnected. Tighten the terminal screws to the correct tightening torque.
dWF1 EEPROM Memory DWEZ Data Error	Cause: There is an error in the EEPROM peripheral circuit. There is a problem with the EEPROM data. Remedy: Re-energize the drive. If fault stays, replace control board/drive. Set A1-03 = 2220 or 3330 to initialize the drive, then upload the DriveWorksEZ project again.
dWF2 / dWF3 / dWFL DriveWorksEZ Fault	Cause: There was a fault in the DriveWorksEZ program. Remedy: Examine the DriveWorksEZ program and remove the cause of the fault. Note: This is not a drive fault, but a program logic issue.
EF0 Option Card External Fault	Cause: The communication option received an external fault from the controller. A programming error occurred on the controller side. Remedy: Find the device that caused the external fault and remove the cause. Clear the external fault input from the controller. Examine the operation of the controller program.
EF1 External Fault (Terminal S1)	Cause: MFDI terminal S1 caused an external fault through an external device. The wiring is incorrect. Remedy: Find the device that caused the external fault and remove the cause. Clear the external fault input in the MFDI. Correctly connect the signal line to MFDI terminal S1.
EF2 External Fault (Terminal S2)	Cause: MFDI terminal S2 caused an external fault; or wiring incorrect. Remedy: Find device causing fault and remove cause. Correctly connect signal line to MFDI terminal S2. Ensure External Fault parameter [H1-02] is set correctly.
EF3 External Fault (Terminal S3)	Cause: MFDI terminal S3 caused an external fault; or wiring incorrect. Remedy: Find device causing fault and remove cause. Correctly connect signal line to MFDI terminal S3.
EF4 External Fault (Terminal S4)	Cause: MFDI terminal S4 caused an external fault; or wiring incorrect. Remedy: Find device causing fault and remove cause. Correctly connect signal line to MFDI terminal S4.
EF5 External Fault (Terminal S5)	Cause: MFDI terminal S5 caused an external fault; or wiring incorrect. Remedy: Find device causing fault and remove cause. Correctly connect signal line to MFDI terminal S5.
EF6 External Fault (Terminal S6)	Cause: MFDI terminal S6 caused an external fault; or wiring incorrect. Remedy: Find device causing fault and remove cause. Correctly connect signal line to MFDI terminal S6.
EF7 External Fault (Terminal S7)	Cause: MFDI terminal S7 caused an external fault; or wiring incorrect. Remedy: Find device causing fault and remove cause. Correctly connect signal line to MFDI terminal S7.
Err EEPROM Write Error	Cause: There was a problem with the EEPROM hardware. Electrical interference corrupted data while writing to EEPROM. Remedy: Re-energize the drive. If fault stays, replace control board/drive. Push ENTER Key and set parameters again.
FAn1 Drive Cooling Fan Fault	Cause: The cooling fan stopped operating correctly. The circulation fan is damaged. Remedy: Examine cooling/circulation fan operation. Re-energize the drive. Replace fan if U4-03/U4-04 indicate expired life or damage.
FDBKL WIRE Break	Cause: The analog input for PID Feedback is more than 21mA or less than 3mA (loss of signal). Remedy: Make sure that you install the PID feedback source and it operates correctly. Check wiring continuity.
GF Ground Fault	Cause: Overheating caused damage to motor insulation. Motor main circuit cable is contacting ground (short circuit). Stray capacitance of cable/ground is too high (leakage current). Drive hardware problem. Remedy: Measure motor insulation resistance; replace motor if needed. Examine/Replace main circuit cable. If cable length > 100m, decrease carrier frequency. Replace control board or drive if hardware is faulty.
HFB High Feedback Sensed	Cause: The feedback level is higher than the level set in Y1-11 for the time set in Y1-12. Remedy: Decrease the feedback level less than Y1-11. Set Y1-11 and Y1-12 correctly.
HIAUX High PI Aux Feedback Level	Cause: PI Auxiliary Feedback is more than level set in YF-12 for time set in YF-13. Remedy: Decrease the PI Auxiliary Feedback level. Set YF-12 and YF-13 correctly.
HLCE High Level Communication Errors	Cause: Communication data error between option and master drive (Gateway function). Remedy: Examine the wiring between the option and the master drive. Remove the cause of the fault (interference/connections).
LF Output Phase Loss	Cause: Motor main circuit cable disconnected. Disconnection in motor coil winding. Loose drive output terminal screws. Rated output current < 5% of drive rated current. Trying to use a single-phase motor. Output transistor damaged. Remedy: Connect/Correct motor main circuit wiring. Measure Line-to-Line resistance; replace motor if disconnected. Tighten terminal screws. Examine drive capacity vs motor output. Re-energize drive. If fault stays, replace board/drive.
LF2 Output Current Imbalance	Cause: Phase loss in wiring on output side. Loose output terminal screws. Imbalance in PM motor impedance. Drive output circuit broken. Remedy: Examine wiring for errors/disconnections. Tighten terminal screws. Measure Line-to-Line resistance; ensure balance. Re-energize drive. If fault stays, replace board/drive.
LFB Low Feedback Sensed	Cause: Feedback level is less than level set in Y1-08 for time set in Y1-09. Remedy: Increase the feedback level to more than Y1-08. Set Y1-08 and Y1-09 correctly.
LOAUX Low PI Aux Feedback Level	Cause: When the drive operates in AUTO Mode or HAND Mode, PI Auxiliary Feedback is less than the level set in YF-09 [PI Aux Control Low Lvl Detection] for the time set in YF-10 [PI Aux Control Low Lvl Det Time] and the drive is running. Remedy: Increase the PI Auxiliary Feedback level to be more than YF-09. Set YF-09 and YF-10 correctly. Note: Do a Fault Reset to clear the fault.
LOP Loss of Prime	Cause: The drive used the Y1-18 [Prime Loss Detection Method] setting and measured a pump load that is less than the level set in Y1-19 [Prime Loss Level] for the time set in Y1-20 [Prime Loss Time], and the output frequency is Y1-21 [Prime Loss Activation Freq] or more. Remedy: Examine for a dry well, air in the system, or no water in the system. Use preferred priming method suggested by the pump manufacturer to restart the pump. When there is resistance in the pump, let the system pump water again. Set Y1-18 to Y1-21 correctly.
MSL Net Master Lost	Cause: When Y9-27 = 3 [Network Recovery = Fault MSL] and the drive does not receive message from the master within the time set in Y9-26 [Master Time-out]. Remedy: Increase Y9-26 to account for network latency. Make sure that there is a drive on the network with parameters set to Y1-01 = 3 and Y9-27 = 0. Examine network connections and the settings of H5-01 and Y9-25 for all drives on the network.
NMS Setpoint Not Met	Cause: The feedback deviates from the setpoint at a level more than Y1-15 [Maximum Setpoint Difference] for the time set in Y1-16 [Not Maintaining Setpoint Time]. Remedy: Examine for a blocked impeller, over cycling, or broken pipe. Set Y1-15 and Y1-16 correctly.
nSE Node Setup Error	Cause: The drive received a Run command while the Node Setup function was active. Remedy: Stop the drive when the Node Setup function is in use.
oC Overcurrent	Cause: The load is too large. Remedy: Measure the current flowing into the motor. Replace the drive with a larger capacity model if the current value is more than the drive rated current. Decrease the load or replace with a larger drive to prevent sudden changes in the current level. Cause: Overheating caused damage to the motor or the motor insulation is not satisfactory. Remedy: Measure the motor insulation resistance, and replace the motor if there is electrical conduction or unserviceable insulation. Cause: The motor main circuit cable is contacting ground to make a short circuit. Remedy: Examine the motor main circuit cable for damage, and repair short circuits. Measure the resistance between the motor main circuit cable and the ground terminal. If there is electrical conduction, replace the cable. Cause: A short circuit or ground fault on the drive output side caused damage to the output transistor of the drive. Remedy: Make sure that there is not a short circuit in terminals – and terminals U/T1, V/T2, and W/T3. If there is a short circuit, contact Yaskawa or your nearest sales representative. Cause: The acceleration time is too short. Remedy: Calculate the torque necessary during acceleration related to the load inertia and the specified acceleration time. Increase the values set in C1-01 or C1-03 [Acceleration Times] to get the necessary torque. Increase the values set in C2-01 to C2-04 [S-Curve Characteristics] to get the necessary torque. Replace the drive with a larger capacity model. Cause: The drive is trying to operate a specialized motor or a motor that is larger than the maximum applicable motor output of the drive. Remedy: Examine the motor nameplate, the motor, and the drive to make sure that the drive rated current is larger than the motor rated current. Replace the drive with a larger capacity model. Cause: A magnetic contactor was switched at the output. Remedy: Set the operation sequence to not turn ON or OFF the magnetic contactor while the drive is outputting voltage. Cause: The V/f pattern settings are incorrect. Remedy: Examine the ratios between the V/f pattern frequency and voltage. Decrease the voltage if it is too high compared to the frequency. Adjust E1-04 to E1-10 [V/f Pattern Parameters]. For motor 2, adjust E3-04 to E3-10. Cause: The torque compensation gain is too large. Remedy: Decrease the value set in C4-01 [Torque Compensation Gain] to make sure that the motor does not stall. Cause: The gain during overexcitation operation is too large. Remedy: Find the time when the fault occurs. If the fault occurs at the same time as overexcitation operation, decrease the value set in n3-13 [OverexcitationBraking (OEB) Gain] and consider the motor flux saturation. Cause: The drive received a Run command while the motor was coasting. Remedy: Examine the sequence and input the Run command after the motor fully stops. Set b3-01 = 1 or set H1-xx = 61, 62 to input speed search commands from the MFDI terminals.
OD Output Disconnect	Cause: The output circuit between the drive and the motor is open, and the drive output current is less than 5% of E2-01 [Motor Rated Current (FLA)]. Remedy: Close the disconnected output circuit between the drive and the motor.
oFA00 Option Not Compatible with Port	Cause: The option connected to connector CN5-A is not compatible, DIP switches on JOHB-SMP3 are at factory default, or DIP switches are not set to a valid protocol. Remedy: Connect the option to the correct connector. Remove power, wait for charge light to go out, then set DIP switches on JOHB-SMP3 to desired protocol. Replace the option if it has failed.
oFA01 Option Fault/Connection Error	Cause: The option card connected to connector CN5 is not compatible. Remedy: De-energize the drive. Refer to the option card manual and correctly connect the option card to the connector on the drive.
oFA05 Option A/D Error	Cause: A fault occurred in the option card. Remedy: De-energize the drive. Make sure that the option card is correctly connected to the connector. If the problem continues, replace the option card.
oFA06 Option Communication Error	Cause: A fault occurred in the option card. Remedy: De-energize the drive. Make sure that the option card is correctly connected to the connector. If the problem continues, replace the option card.
oFA10 Option RAM Error	Cause: A fault occurred in the option card. Remedy: De-energize the drive. Make sure that the option card is correctly connected to the connector. If the problem continues, replace the option card.
oFA11 Option Ope Mode Error	Cause: A fault occurred in the option card. Remedy: De-energize the drive. Make sure that the option card is correctly connected to the connector. If the problem continues, replace the option card.
oFA12 Drive Receive CRC Error	Cause: A fault occurred in the option card. Remedy: De-energize the drive. Make sure that the option card is correctly connected to the connector. If the problem continues, replace the option card.
oFA13 Drive Receive Frame Error	Cause: A fault occurred in the option card. Remedy: De-energize the drive. Make sure that the option card is correctly connected to the connector. If the problem continues, replace the option card.
oFA14 Drive Receive Abort Error	Cause: A fault occurred in the option card. Remedy: De-energize the drive. Make sure that the option card is correctly connected to the connector. If the problem continues, replace the option card.
oFA15 Option Receive CRC Error	Cause: A fault occurred in the option card. Remedy: De-energize the drive. Make sure that the option card is correctly connected to the connector. If the problem continues, replace the option card.
oFA16 Option Receive Frame Error	Cause: A fault occurred in the option card. Remedy: De-energize the drive. Make sure that the option card is correctly connected to the connector. If the problem continues, replace the option card.
oFA17 Option Receive Abort Error	Cause: A fault occurred in the option card. Remedy: De-energize the drive. Make sure that the option card is correctly connected to the connector. If the problem continues, replace the option card.
oFA30 COM ID Error	Cause: A fault occurred in the option card. Remedy: De-energize the drive. Make sure that the option card is correctly connected to the connector. If the problem continues, replace the option card.
oFA31 Type Code Error	Cause: A fault occurred in the option card. Remedy: De-energize the drive. Make sure that the option card is correctly connected to the connector. If the problem continues, replace the option card.
oFA32 SUM Check Error	Cause: A fault occurred in the option card. Remedy: De-energize the drive. Make sure that the option card is correctly connected to the connector. If the problem continues, replace the option card.
oFA33 Option Receive Time Over	Cause: A fault occurred in the option card. Remedy: De-energize the drive. Make sure that the option card is correctly connected to the connector. If the problem continues, replace the option card.
oFA34 Memobus Time Over	Cause: A fault occurred in the option card. Remedy: De-energize the drive. Make sure that the option card is correctly connected to the connector. If the problem continues, replace the option card.
oFA35 Drive Receive Time Over 1	Cause: A fault occurred in the option card. Remedy: De-energize the drive. Make sure that the option card is correctly connected to the connector. If the problem continues, replace the option card.
oFA36 CI Check Error	Cause: A fault occurred in the option card. Remedy: De-energize the drive. Make sure that the option card is correctly connected to the connector. If the problem continues, replace the option card.
oFA37 Drive Receive Time Over 2	Cause: A fault occurred in the option card. Remedy: De-energize the drive. Make sure that the option card is correctly connected to the connector. If the problem continues, replace the option card.
oFA38 Control Reference Error	Cause: A fault occurred in the option card. Remedy: De-energize the drive. Make sure that the option card is correctly connected to the connector. If the problem continues, replace the option card.
oFA39 Drive Receive Time Over 3	Cause: A fault occurred in the option card. Remedy: De-energize the drive. Make sure that the option card is correctly connected to the connector. If the problem continues, replace the option card.
oFA40 CtrlResSel 1Err	Cause: A fault occurred in the option card. Remedy: De-energize the drive. Make sure that the option card is correctly connected to the connector. If the problem continues, replace the option card.
oFA41 Drive Receive Time Over 4	Cause: A fault occurred in the option card. Remedy: De-energize the drive. Make sure that the option card is correctly connected to the connector. If the problem continues, replace the option card. Note: Do a Fault Reset to clear the fault.
oFA42 CtrlResSel 2Err	Cause: A fault occurred in the option card. Remedy: De-energize the drive. Make sure that the option card is correctly connected to the connector. If the problem continues, replace the option card. Note: Do a Fault Reset to clear the fault.
oFA43 Drive Receive Time Over 5	Cause: A fault occurred in the option card. Remedy: De-energize the drive. Make sure that the option card is correctly connected to the connector. If the problem continues, replace the option card. Note: Do a Fault Reset to clear the fault.
oH Heatsink Overheat	Cause: The ambient temperature is high and the heatsink temperature of the drive is more than the value set in L8-02 [Overheat Alarm Level]. The load is too heavy. The internal cooling fan of the drive stopped. Remedy: Measure the ambient temperature. Increase the airflow in the control panel. Install a cooling device (cooling fan or air conditioner) to lower the ambient temperature. Remove objects near the drive that are producing too much heat. Measure the output current and decrease the load. Decrease the value set in C6-02 [Carrier Frequency Selection]. Use the procedures in the manual to replace the cooling fan. Set o4-03 = 0 [Fan Operation Time Setting = 0 h].
oH1 Heatsink Overheat	Cause: The ambient temperature is high and the heatsink temperature of the drive is more than the oH1 detection level. The load is too heavy. Remedy: Measure the ambient temperature. Increase the airflow in the control panel. Install a cooling device (cooling fan or air conditioner). Remove objects near the drive that are producing too much heat. Measure the output current and decrease the load. Decrease the value set in C6-02 [Carrier Frequency Selection].
oH3 Motor Overheat (PTC Input)	Cause: The thermistor wiring that detects motor temperature is defective. A fault occurred on the machine (e.g., machine is locked). Remedy: Correct wiring errors. Examine the machine and remove the cause of the fault.
oH4 Motor Overheat Fault (PTC Input)	Cause: The motor has overheated. Remedy: Check the load level, acceleration/deceleration time, and motor start/stop frequency (cycle time). Decrease the load. Increase the values set in C1-01 to C1-04 [Acceleration/Deceleration Times]. Set E2-01 [Motor Rated Current (FLA)] correctly to the value specified by the motor nameplate. Make sure that the motor cooling system is operating correctly, and repair or replace it if it is damaged. Adjust E1-04 to E1-10 [V/f Pattern Parameters]. For motor 2, adjust E3-04 to E3-10.
oL1 Motor Overload	Cause: The load is too heavy. The acceleration/deceleration times or cycle times are too short. Overload occurred while running at low speed. L1-01 [Motor Overload (oL1) Protection] is set incorrectly. The V/f pattern does not fit the motor qualities. E1-06 [Base Frequency] is set incorrectly. One drive is operating more than one motor. Remedy: Decrease the load. Examine the acceleration/deceleration times and the motor start/stop frequencies. Increase C1-01 to C1-04. Decrease the load when running at low speed or increase motor speed. If running frequently at low speeds, replace with a larger motor or drive-dedicated motor. Set L1-01 as specified by the motor qualities. Examine V/f pattern frequency and voltage. Decrease voltage if too high. Adjust E1-04 to E1-10. Set E1-06 to the rated frequency shown on the motor nameplate. If operating multiple motors: Set L1-01 = 0 and connect thermal overload relays to each motor.
oL2 Drive Overload	Cause: The load is too large. The acceleration/deceleration times or cycle times are too short. The V/f pattern does not fit the motor qualities. The drive capacity is too small. Overload occurred while running at low speed. The torque compensation gain is too large. The speed search-related parameters are set incorrectly. Phase loss in the input power supply. Overload occurred during overexcitation deceleration. Remedy: Decrease the load. Increase the values set in C1-01 to C1-04. Adjust E1-04 to E1-10 [V/f Pattern Parameters]. Decrease voltage if too high. Replace the drive with a larger capacity model. Decrease C6-02 [Carrier Frequency Selection]. Decrease the value set in C4-01 [Torque Compensation Gain]. Adjust b3-03 [Speed Search Deceleration Time] or set b3-24 = 1 after Auto-Tuning. Correct errors with the wiring for main circuit drive input power. Decrease n3-13 [OverexcitationBraking (OEB) Gain] or n3-21 [HSB Current Suppression Level].
oL3 Overtorque Detection 1	Cause: A fault occurred on the machine (e.g., machine is locked). The parameters are incorrect for the load. Remedy: Examine the machine and remove the cause of the fault. Adjust L6-02 [Torque Detection Level 1] and L6-03 [Torque Detection Time 1] settings.
oL4 Overtorque Detection 2	Cause: A fault occurred on the machine (e.g., machine is locked). The parameters are incorrect for the load. Remedy: Examine the machine and remove the cause of the fault. Adjust L6-05 [Torque Detection Level 2] and L6-06 [Torque Detection Time 2] settings.
oL7 High Slip Braking Overload	Cause: The load inertia is too large. An external force on the load side rotated the motor. Something is preventing deceleration on the load side. The value set in n3-04 [HSB Overload Time] is too small. Remedy: Decrease deceleration times in C1-02 and C1-04 for applications that do not use High Slip Braking. Increase the value set in n3-04. Connect a thermal overload relay to the motor and set n3-04 = 1200 s.
oPr Keypad Connection Fault	Cause: The keypad is not securely connected to the connector on the drive. The connection cable between the drive and the keypad is disconnected. Remedy: Examine the connection between the keypad and the drive. Remove the keypad and connect it again. If the cable is damaged, replace it.
oS Overspeed	Cause: There is overshoot. Remedy: Decrease C5-01 [ASR Proportional Gain 1] and increase C5-02 [ASR Integral Time 1].
ov Overvoltage	Cause: Deceleration time is too short and regenerative energy is flowing from the motor into the drive. The acceleration time is too short. The drive output cable or motor is shorted to ground. Speed search-related parameters are incorrect (during speed search, power loss recovery, etc.). The power supply voltage is too high. Electrical interference caused a drive malfunction. The load inertia is set incorrectly. There is motor hunting. Speed search does not complete at start. Remedy: Set L3-04 = 1 [Stall Prevention during Decel = General Purpose]. Increase C1-02 or C1-04 [Deceleration Times]. Increase C1-01 or C1-03 [Acceleration Times] or C2-02 [S-Curve]. Set L3-11 = 1 [Overvoltage Suppression Select = Enabled]. Examine motor main circuit cable and terminals for ground faults. Adjust speed search parameters (b3-03, b3-24, b3-19) or V/f Recovery Ramp (L2-04). Decrease power supply voltage to align with drive rated voltage. Examine control/main circuit lines for interference; use Surge Protective Device if necessary. Adjust L3-25 [Load Inertia Ratio]. Adjust n1-02 [Hunting Prevention] and n8-45 [Speed Feedback Detection Gain].
ov2 DC Bus Overvoltage 2	Cause: The wiring is too long and DC bus voltage is too large. Remedy: Shorten the shielded motor cable. Decrease the carrier frequency. If the power supply has a neutral ground, switch on the internal EMC filter.
PE1 PLC Fault 1	Cause: The communication option detected a fault. Remedy: Refer to the manual for the communication option card.
PE2 PLC Fault 2	Cause: The communication option detected a fault. Remedy: Refer to the manual for the communication option card.
PF Input Phase Loss	Cause: There is a phase loss in the drive input power. There is loose wiring in the drive input power terminals. The drive input power voltage is changing too much. There is unsatisfactory balance between voltage phases. Remedy: Correct errors with the wiring for main circuit drive input power. Tighten the terminal screws to the correct tightening torque. Examine the input power for problems and make it stable. If input power is good, examine the magnetic contactor. Set L8-05 = 0 [Input Phase Loss Protection Sel = Disabled] (Use with caution).
PSE JOHB-SMP3 Protocol Set Error	Cause: The DIP switches on the JOHB-SMP3 Multi-Protocol Ethernet Card are at factory default settings. The DIP switches on the JOHB-SMP3 are not set to a valid protocol. Remedy: Remove power from the drive, wait for the charge light to go out, then set the DIP switches on the JOHB-SMP3 to the desired protocol. Note: “PSE” error occurs only for PRG: 01018 and later. Do a Fault Reset to clear.
SC Short Circuit/IGBT Failure	Cause: Overheating caused damage to the motor or the motor insulation is not satisfactory. The motor main circuit cable is contacting ground to make a short circuit. A short circuit or ground fault on the drive output side caused damage to the output transistor. When A1-02 = 5 [Control Method Selection = OLV/PM], output current > L8-27. Remedy: Measure the motor insulation resistance; replace motor if conduction/unserviceable insulation found. Examine motor main circuit cable for damage and repair short circuits. Measure resistance between motor main circuit cable and ground terminal. Check for short circuits in terminals +1, -, U/T1, V/T2, W/T3. Set L8-27 correctly.
SCF Safety Circuit Fault	Cause: The safety circuit is broken. Remedy: Replace the control board or the drive. Contact Yaskawa or your nearest sales representative.
SEr Speed Search Retries Exceeded	Cause: The speed search-related parameters are set incorrectly. The motor is coasting in the opposite direction of the Run command. Remedy: Decrease b3-10 [Speed Estimation Detection Gain]. Increase b3-17 [Speed Est Retry Current Level]. Increase b3-18 [Speed Est Retry Detection Time]. Do Auto-Tuning again. Set b3-14 = 1 [Bi-directional Speed Search = Enabled].
STPo Motor Step-Out Detected	Cause: The motor code is set incorrectly for PM Control Methods. The load is too large. The load inertia is too large. The acceleration/deceleration times are too short. Speed response is too slow. Remedy: Set E5-01 [PM Motor Code Selection] correctly as specified by the motor. Increase n8-55 [Motor to Load Inertia Ratio]. Increase n8-51 [Pull-in Current @ Acceleration]. Decrease the load. Increase C1-01 to C1-04 [Accel/Decel Times]. Increase C2-01 [S-Curve Time @ Start of Accel].
TiM Keypad Time Not Set	Cause: There is a battery in the keypad, but the date and time are not set. Remedy: Use the keypad to set the date and time.
UL3 Undertorque Detection 1	Cause: A fault occurred on the machine (e.g., broken pulley belt). The parameters are incorrect for the load. Remedy: Examine the machine and remove the cause of the fault. Adjust L6-02 [Torque Detection Level 1] and L6-03 [Torque Detection Time 1] settings.
UL4 Undertorque Detection 2	Cause: A fault occurred on the machine (e.g., broken pulley belt). The parameters are incorrect for the load. Remedy: Examine the machine and remove the cause of the fault. Adjust L6-05 [Torque Detection Level 2] and L6-06 [Torque Detection Time 2] settings.
UL6 Underload or Belt Break Detected	Cause: The output current decreased less than the motor underload curve set in L6-14 for longer than the time set in L6-03. Remedy: Adjust the L6-14 setting to set the output current to stay the level more than the motor underload curve during usual operations.
Uv1 DC Bus Undervoltage	Cause: There is a phase loss in the drive input power. There is loose wiring in the drive input power terminals. The drive input power voltage is changing too much. There was a loss of power. The main circuit capacitors have become unserviceable. Remedy: Correct errors with the wiring for main circuit drive input power. Tighten the terminal screws to the correct tightening torque. Examine the input power for problems and make it stable. Examine the capacitor maintenance time in monitor U4-05. Replace the control board or drive if required.
Uv2 Control Power Undervoltage	Cause: The value set in L2-02 [Power Loss Ride Through Time] increased and the momentary power loss recovery unit is not connected. There was a problem with the drive hardware. Remedy: Connect the momentary power loss recovery unit to the drive. Re-energize the drive. If fault stays, replace the control board or the drive.
Uv3 Soft Charge Answerback Fault	Cause: The relay or contactor on the soft-charge bypass relay is damaged. Air inside the drive is too hot. Remedy: Re-energize the drive. Check monitor U4-06 [PreChargeRelayMainte]. If > 90%, replace board/drive. Check the ambient temperature of the drive.
VLTS Thermostat Fault	Cause: The digital input from the terminal set for Thermostat Fault [H1-xx = 88] is active. Remedy: Examine the wiring or wait for the motor to cool.
AFBL Analog Fbk Lost, Switched to Net	Cause: The analog input source is defective or broken. Remedy: Make sure that you install the PID Feedback source and it operates correctly. If the drive does not have an analog PID Feedback source, set Y9-02 = 3 [System Feedback Source = Network Only]. Cause: The parameter setting is H3-xx ≠ B [MFAI Function Selection ≠ PID Feedback]. Remedy: Set H3-xx = B to use the analog input source for PID Feedback. If the drive does not have an analog PID Feedback source, set Y9-02 = 3.
AuDis Low PI Aux Fdbk Drive Disabled	Cause: Parameter setting of Y9-51 = 1 [PI Aux Control Turn-Off Method = Enabled] does not let the drive operate in Memobus Multiplex. PI Auxiliary Feedback is less than the YF-06 [PI Aux Control Wake-up Level] setting. Remedy: Make sure that the YF-06 setting is correct. Wait for the PI Auxiliary Feedback to recover.
AUXFB PI Aux Feedback Level Loss	Cause: The analog input from the terminal set to H3-xx = 27 is more than 21 mA or less than 3 mA for longer than 1 s. Remedy: Repair transducer or wiring.
AuFbl PI Aux Fdbk Lost Switched to Net	Cause: The analog input source is defective or broken. Remedy: Make sure that you install the Auxiliary PI Feedback source and it operates correctly. Make sure that the YF-19 [PI Aux Ctrl Feedback WireBreak] setting is correct. If there is no analog feedback, set Y9-50 = 3.
bAT Keypad Battery Low Voltage	Cause: The keypad battery voltage is low. Remedy: Replace the keypad battery.
bb Baseblock	Cause: An external baseblock command was entered through one of the MFDI terminals Sx. Remedy: Examine the external sequence and timing of the baseblock command input.
bCE Bluetooth Communication Error	Cause: The smartphone or tablet is too far from the keypad. Remedy: Move to 10 m (32.8 ft) or less from the keypad. Cause: Radio waves from a different device are causing interference. Remedy: Make sure that no device around the keypad uses the same radio bandwidth (2400 MHz to 2480 MHz).
BuDif Main Fdbk Lost, Using Diff Fdbk	Cause: Parameter Y4-41 = 1 and drive detected wire-break on PID Feedback [H3-xx = B]. Remedy: Examine the connection of the Main PID Feedback Transducer. Cause: Main PID Feedback Transducer is broken. Remedy: Replace Main PID Feedback Transducer.
Bu-Fb Main Fdbk Lost Using Backup Fdbk	Cause: The drive detected wire-break on the analog input terminal set to H3-xx = B. Remedy: Examine the connection of the Main PID Feedback Transducer. Cause: Main PID Feedback Transducer is broken. Remedy: Replace Main PID Feedback Transducer.
BuFbl Backup Fdbk Lost Chk/Repl Xducer	Cause: Wire-break on input set for PID Feedback Backup [H3-xx = 24] or Backup Transducer broken. Remedy: Examine the connection of the Differential PID Feedback transducer. Replace Backup PID Feedback Transducer. Cause: Y4-41 = 1 and wire-break detected on Differential Level Source [H3-xx = 2D] or Differential Transducer broken. Remedy: Examine the connection of the Differential PID Feedback transducer. Replace the Differential PID Feedback Transducer. Set Y4-41 = 0 [Disabled].
bUS Option Communication Error	Cause: The communications cable wiring is incorrect. Remedy: Correct wiring errors. Cause: Short-circuit in cable or cable not connected. Remedy: Repair short circuits and connect cables. Replace the defective communications cable. Cause: Electrical interference caused a communication data error. Remedy: Examine control/main circuit lines and grounding. Decrease electrical interference. Ensure magnetic contactor is not the source of interference (use Surge Protective Device). Use recommended shielded cables. Ground shield correctly. Separate communication wiring from drive power lines; install noise filter. Cause: Option card incorrectly installed or damaged. Remedy: Correctly install the option card or replace it.
bUSy Busy	Cause: You set the drive to use MEMOBUS/Modbus to change parameters, but you used the keypad. Remedy: Use MEMOBUS/Modbus communications to enter the enter command, then use the keypad to change the parameter. Cause: You tried to change a parameter while the drive was changing setting. Remedy: Wait until the process is complete.
CALL Serial Comm Transmission Error	Cause: Communications cable wiring incorrect, short circuit, or disconnected. Remedy: Correct wiring errors, repair short-circuits, or replace cables. Cause: A programming error occurred on the controller side. Remedy: Examine communications at start-up and correct programming errors. Cause: Damage to communications circuitry. Remedy: Do a self-diagnostics check. Replace control board or drive if problem continues. Cause: Termination resistor setting incorrect. Remedy: Set DIP switch S2 to the ON position on the last drive in the network.
CE Modbus Communication Error	Cause: Communications cable wiring incorrect, short circuit, or disconnected. Remedy: Correct wiring errors, repair cables, or replace defective cables. Cause: Electrical interference caused a communication data error. Remedy: Check grounding, shielding, and noise filters. Decrease electrical interference. Cause: The communication protocol is not compatible. Remedy: Examine values in H5-xx and settings on the controller side. Cause: H5-09 [CE Detection Time] is too small. Remedy: Change controller software settings or increase H5-09. Cause: Controller software/hardware communication problem. Remedy: Examine the controller and remove the cause.
CE Run at H5-34 (CE Go-To-Freq)	Cause: Communications cable wiring incorrect, short circuit, or disconnected. Remedy: Correct wiring errors, repair cables, or replace defective cables. Cause: Electrical interference caused a communication data error. Remedy: Check grounding, shielding, and noise filters. Decrease electrical interference. Cause: The communication protocol is not compatible. Remedy: Examine values in H5-xx and settings on the controller side. Cause: H5-09 [CE Detection Time] is too small. Remedy: Make sure settings are compatible. Change PLC software or increase H5-09. Cause: Controller software/hardware communication problem. Remedy: Examine the controller and remove the cause.
CrST Cannot Reset	Cause: The drive received a fault reset command when a Run command was active. Remedy: Turn off the Run command then de-energize and re-energize the drive.
CyPo Cycle Power to Accept Changes	Cause: Although F6-15 = 1, the drive does not update the communication option parameters. Remedy: Re-energize the drive to update the communication option parameters.
dEv Speed Deviation	Cause: The load is too heavy. Acceleration and deceleration times are set too short. The dEv detection level settings are incorrect. The load is locked up. The holding brake is stopping the motor. Remedy: Decrease the load. Increase the values set in C1-01 to C1-04. Adjust F1-10 and F1-11. Examine the machine. Release the holding brake.
DIFF Differential Feedback Exceeded	Cause: The difference between PID Feedback and Differential Level Source [H3-xx = 2D] is more than level Y4-18 for time Y4-19. Remedy: Replace the feedback transducer or transducers. Set Y4-18 and Y4-19 correctly.
dnE Drive Disabled	Cause: A terminal set for H1-xx = 6A [MFDI Function Selection = Drive Enable] deactivated. Remedy: Examine the operation sequence.
dWA2 DriveWorksEZ Alarm 2	Cause: The DriveWorksEZ program output a minor fault. Remedy: Examine the DriveWorksEZ program and remove the cause of the fault. This is not a drive fault.
dWA3 DriveWorksEZ Alarm 3	Cause: The DriveWorksEZ program output a minor fault. Remedy: Examine the DriveWorksEZ program and remove the cause of the fault. This is not a drive fault.
dWAL DriveWorksEZ Alarm	Cause: There was an error in the DriveWorksEZ program. Remedy: Examine the DriveWorksEZ program and remove the cause of the error. This is not a drive fault.
EF FWD/REV Run Command Input Error	Cause: The drive received a forward command and a reverse command at the same time for longer than 0.5 s. Remedy: Examine the forward and reverse command sequence and correct the problem.
EF0 Option Card External Fault	Cause: The communication option card received an external fault from the controller. Remedy: Find the device that caused the external fault and remove the cause. Clear the external fault input from the controller. Cause: Programming error occurred on the controller side. Remedy: Examine the operation of the controller program.
EF1 External Fault (Terminal S1)	Cause: MFDI terminal S1 caused an external fault through an external device. Remedy: Find the device that caused the external fault and remove the cause. Clear the external fault input in the MFDI. Cause: The wiring is incorrect. Remedy: Correctly connect the signal line to MFDI terminal S1. Cause: External Fault [H1-01] is set to MFDI terminal S1, but the terminal is not in use. Remedy: Correctly set the MFDI.
EF2 External Fault (Terminal S2)	Cause: MFDI terminal S2 caused an external fault through an external device. Remedy: Find/remove cause and clear input. Cause: The wiring is incorrect. Remedy: Correctly connect the signal line to MFDI terminal S2. Cause: External Fault [H1-02] is set to MFDI terminal S2, but the terminal is not in use. Remedy: Correctly set the MFDI.
EF3 External Fault (Terminal S3)	Cause: MFDI terminal S3 caused an external fault through an external device. Remedy: Find/remove cause and clear input. Cause: The wiring is incorrect. Remedy: Correctly connect the signal line to MFDI terminal S3. Cause: External Fault [H1-03] is set to MFDI terminal S3, but the terminal is not in use. Remedy: Correctly set the MFDI.
EF4 External Fault (Terminal S4)	Cause: MFDI terminal S4 caused an external fault through an external device. Remedy: Find/remove cause and clear input. Cause: The wiring is incorrect. Remedy: Correctly connect the signal line to MFDI terminal S4. Cause: External Fault [H1-04] is set to MFDI terminal S4, but the terminal is not in use. Remedy: Correctly set the MFDI.
EF5 External Fault (Terminal S5)	Cause: MFDI terminal S5 caused an external fault through an external device. Remedy: Find/remove cause and clear input. Cause: The wiring is incorrect. Remedy: Correctly connect the signal line to MFDI terminal S5. Cause: External Fault [H1-05] is set to MFDI terminal S5, but the terminal is not in use. Remedy: Correctly set the MFDI.
EF6 External Fault (Terminal S6)	Cause: MFDI terminal S6 caused an external fault through an external device. Remedy: Find/remove cause and clear input. Cause: The wiring is incorrect. Remedy: Correctly connect the signal line to MFDI terminal S6.
EF7 External Fault (Terminal S7)	Cause: MFDI terminal S7 caused an external fault through an external device OR Wiring is incorrect. Remedy: Find the device that caused the external fault and remove the cause. Clear the external fault input in the MFDI. Correctly connect the signal line to MFDI terminal S7. Correctly set the MFDI.
EOF Emergency Override FWD	Cause: The digital input terminal set to H1-xx = AF [Emergency Override FWD] activated. Remedy: When the emergency condition is gone, deactivate the digital input set to Emergency Override FWD.
EOR Emergency Override REV	Cause: The digital input terminal set to H1-xx = B0 [Emergency Override REV] activated. Remedy: When the emergency condition is gone, deactivate the digital input set to Emergency Override REV.
EP24v External Power 24V Supply	Cause: The voltage of the main circuit power supply decreased, and the 24 V power supply is supplying power to the drive. Remedy: Examine the main circuit power supply. Turn ON the main circuit power supply to run the drive.
FDBKL Feedback Loss Wire Break	Cause: The PID Feedback analog input is > 21 mA or < 3 mA for longer than 1s (under specific b5-82/b5-01 settings). Remedy: Make sure that you install the PID feedback source and it operates correctly.
FLGT Feedback Loss, Go To Freq b5-83	Cause: PID Feedback input error detected while “Run At b5-83” is selected. Remedy: Make sure that you install the PID feedback source and it operates correctly.
FR Freq Ref < Minimum Speed (Y1-06)	Cause: The drive frequency reference setting is less than the value set in Y1-06 [Minimum Speed]. Remedy: Increase the frequency reference to a value more than Y1-06.
FR Freq. Reference < Thrust (Y4-12)	Cause: The drive frequency reference setting is less than the value set in Y4-12 [Thrust Frequency]. Remedy: Increase the frequency reference to a value more than Y4-12.
HCA High Current Alarm	Cause: Load is too heavy; Accel time too short; Specialized motor used; or Current level temporarily increased due to speed search. Remedy: Decrease the load for applications with repetitive starts/stops. Replace the drive with a larger capacity model. Increase Acceleration Times (C1-01/C1-03) or S-Curve (C2-01 to C2-04). Examine motor nameplate and ensure drive rated current > motor rated current. If caused by Speed Search/Auto Restart: No steps necessary (alarm is temporary).
HIAUX High PI Aux Feedback Level	Cause: PI Auxiliary Feedback is more than the level set in YF-12 for the time set in YF-13. Remedy: Decrease the PI Auxiliary Feedback level to less than YF-12. Set YF-12 and YF-13 correctly.
HIFB High Feedback Sensed	Cause: The feedback level is more than the level set in Y1-11 [High Feedback Level]. Remedy: Decrease the feedback level to less than Y1-11 – Y1-14 [Hysteresis Level]. Set Y1-11 and Y1-12 correctly.
INTLK BAS Interlock	Cause: The digital input terminal set to H1-xx = B2 [BAS Interlock] deactivated. Remedy: Make sure the cause of interlock is resolved.
L24v Loss of External Power 24 Supply	Cause: The voltage of the backup 24 V power supply has decreased. Remedy: Examine the external 24 V power supply for disconnected wires and wiring errors. Examine the external 24 V power supply for problems.
LCP Low City Pressure	Cause: Insufficient pressure present on the inlet to the pump. Remedy: Examine the pressure switch contact for correct operation. Examine control wiring to drive terminal strip. Make sure suction pressure is present with an isolated measuring device. Set Y4-22 (On-Delay) and Y4-23 (Off-Delay) correctly. Deactivate digital input terminals set to B8 or 1B8.
LOAUX Low PI Aux Feedback Level	Cause: PI Auxiliary Feedback is less than the level set in YF-09 for the time set in YF-10. Remedy: Increase the PI Auxiliary Feedback level more than YF-09. Set YF-09 and YF-10 correctly.
LOFB Low Feedback Sensed	Cause: The feedback level is less than the level set in Y1-08 for the time set in Y1-09. Remedy: Increase the feedback level to more than Y1-08 + Y1-14. Set Y1-08 and Y1-09 correctly.
LoG Com Error / Abnormal SD Card	Cause: No micro SD card; Card communication > 1000 files; Card full; Line number data changed; or Comms error. Remedy: Put a micro SD card in the keypad. Set o5-01 = 0 [Log Start/Stop Selection = OFF].
LOP Loss of Prime	Cause: The drive detected pump load is less than Y1-19 (Prime Loss Level) for time Y1-20. Remedy: Examine a dry well, air in the system, or no water. Use priming method suggested by pump manufacturer. When there is resistance in the pump, allow system to pump water again. Set Y1-18 to Y1-21 correctly.
LSP Low Suction Pressure	Cause: An external input indicated insufficient suction pressure. Remedy: Examine the pressure switch contact and control wiring. Make sure suction pressure is present. Increase the system pressure. Set Y4-22 (On-Delay) and Y4-23 (Off-Delay) correctly.
LT-1 Cooling Fan Maintenance Time	Cause: The cooling fan is at 90% of its performance life estimate. Remedy: Replace the cooling fan. Set o4-03 = 0 to reset the cooling fan operation time.
LT-2 Capacitor Maintenance Time	Cause: The capacitors for the main circuit and control circuit are at 90% of their performance life estimate. Remedy: Replace the control board or the drive. Contact Yaskawa.
LT-3 SoftChargeBypassRelay MainteTime	Cause: The soft charge bypass relay is at 90% of its performance life estimate. Remedy: Replace the control board or the drive. Contact Yaskawa.
LT-4 IGBT Maintenance Time (50%)	Cause: The IGBT is at 50% of its performance life estimate. Remedy: Check the load, carrier frequency, and output frequency.
LWT Low Water In Tank	Cause: An external input has indicated that the water level in the tank is too low. Remedy: Examine the pressure switch contact and control wiring. Make sure suction pressure is present. Increase the water level. Set Y4-22 and Y4-23 correctly.
NETSC NETSCAN Waiting for Master	Cause: The drive does not receive message from the master in the time set in Y9-28. Remedy: Increase Y9-28 to account for network latency. Make sure there is a drive on the network with Y1-01=3 and Y9-27=0. Examine network connections and settings of H5-01 and Y9-25.
NMS Setpoint Not Met	Cause: Feedback deviates from setpoint > Y1-15 for time set in Y1-16. Remedy: Examine for a blocked impeller, over cycling, or broken pipe. Set Y1-15 and Y1-16 correctly.
OD Output Disconnect	Cause: Output circuit between drive and motor is open, and current < 5% of E2-01. Remedy: Close the disconnected output circuit between the drive and the motor. If you do not use a motor disconnect, set Y4-42 = 0 [Disabled].
oH Heatsink Overheat	Cause: Ambient temp too high; Insufficient airflow; Internal cooling fan stopped. Remedy: Measure and decrease ambient temperature (install cooling device). Ensure correct installation space and sufficient circulation. Clean dust/materials clogging the fan. Replace cooling fan and reset o4-03 to 0.
oH2 External Overheat (H1-XX=B)	Cause: An external device sent an oH2 alarm. Remedy: Find the external device that output the overheat alarm. Remove the cause of the problem. Clear the Overheat Alarm input in MFDI.
oH3 Motor Overheat (PTC Input)	Cause: Thermistor wiring defective; Machine locked; Motor overheated due to load/accel settings; or Cooling system failure. Remedy: Correct wiring errors. Examine the machine and remove cause of fault (e.g. unlock machine). Check load level and cycle time. Increase C1-01 to C1-04 times. Set E2-01 [Motor Rated Current] correctly. Repair motor cooling system. Adjust V/f Pattern (E1/E3 parameters).
oL3 Overtorque 1	Cause: A fault occurred on the machine (e.g., machine is locked) or parameters are incorrect for the load. Remedy: Examine the machine and remove the cause of the fault. Adjust L6-02 [Torque Detection Level 1] and L6-03 [Torque Detection Time 1] settings.
oL4 Overtorque 2	Cause: A fault occurred on the machine (e.g., machine is locked) or parameters are incorrect for the load. Remedy: Examine the machine and remove the cause of the fault. Adjust L6-05 [Torque Detection Level 2] and L6-06 [Torque Detection Time 2] settings.
oS Overspeed	Cause: There is overshoot. Remedy: Decrease C5-01 [ASR Proportional Gain 1]. Increase C5-02 [ASR Integral Time 1].
ov DC Bus Overvoltage	Cause: Drive output cable or motor shorted to ground (charging main circuit capacitor). Power supply voltage is too high. Electrical interference causing drive malfunction. Remedy: Examine motor main circuit cable, terminals, and motor terminal box; remove ground faults. Re-energize drive. Decrease power supply voltage to align with drive rated voltage. Check control/main circuit lines and ground wiring to minimize noise. Install Surge Protective Device if a magnetic contactor is the noise source.
ovEr Too Many Parameters Changed	Cause: You tried to change more than 150 parameters. Remedy: Make sure that parameters that do not have an effect on drive operation are at their default settings. Note: Return non-essential parameters to default to reduce the count below 150.
PASS Modbus Communication Test	Cause: The MEMOBUS/Modbus communications test is complete. Remedy: The PASS display will turn off after communications test mode is cleared.
PF Input Phase Loss	Cause: Phase loss in drive input power. Loose wiring in input power terminals. Drive input power voltage fluctuation or unsatisfactory balance between phases. Remedy: Correct errors with the wiring for main circuit drive input power. Tighten the terminal screws to the correct tightening torque. Examine input power for stability and balance. Check the magnetic contactor on the main circuit side.
rUn Motor Switch during Run	Cause: The drive received a Motor 2 Selection [H1-xx = 16] during run. Remedy: Make sure that the drive receives the Motor 2 Selection while the drive is stopped.
SAFE Customer Safeties	Cause: External contact from customer wiring is open. Remedy: Examine the cause of the open safety contact.
SE Modbus Test Mode Error	Cause: MEMOBUS/Modbus communications self-diagnostics [H1-xx = 67] was done while the drive was running. Remedy: Stop the drive and do MEMOBUS/Modbus communications self-diagnostics.
STo Safe Torque OFF	Cause: Safe Disable inputs H1-HC and H2-HC are open. Internal damage to the two Safe Disable channels. Remedy: Make sure Safe Disable signal is input from external source to H1-HC and H2-HC. If Safe Disable is not in use, use a jumper to connect terminals H1-HC and H2-HC. If board/drive is damaged, contact Yaskawa or sales representative.
SToF Safe Torque OFF Hardware	Cause: One of two terminals H1-HC or H2-HC received Safe Disable input (signal mismatch). Safe Disable input signal wired incorrectly. Internal damage to one Safe Disable channel. Remedy: Check external source signals to H1-HC and H2-HC. If function not in use, jumper terminals H1-HC and H2-HC. Replace board or drive if damage is suspected.
TiM Keypad Time Not Set	Cause: There is a battery in the keypad, but you have not set the date and time. Remedy: Use the keypad to set the date and time.
TrPC IGBT Maintenance Time (90%)	Cause: The IGBT is at 90% of its performance life estimate. Remedy: Replace the IGBT or the drive. Contact Yaskawa or sales representative.
UL3 Undertorque Detection 1	Cause: A fault occurred on the machine (e.g., broken pulley belt) or parameters are incorrect for the load. Remedy: Examine the machine and remove the cause of the fault. Adjust L6-02 [Torque Detection Level 1] and L6-03 [Torque Detection Time 1] settings.
UL4 Undertorque Detection 2	Cause: A fault occurred on the machine (e.g., broken pulley belt) or parameters are incorrect for the load. Remedy: Examine the machine and remove the cause of the fault. Adjust L6-05 [Torque Detection Level 2] and L6-06 [Torque Detection Time 2] settings.
UL6 Underload or Belt Break Detected	Cause: Output current decreased less than motor underload curve for longer than set time. Belt has broken disconnecting motor from load. Remedy: Examine parameters L6-13 [Motor Underload Curve Select] and L6-14. Check for broken belts or mechanical disconnections.
Uv Undervoltage	Cause: Drive input power voltage fluctuating or unstable. Phase loss or loose wiring in drive input power. Main circuit capacitors unserviceable. Input power transformer too small. Air inside drive is too hot. Charge LED is broken. Remedy: Examine input power for problems and stability. Tighten terminal screws; correct wiring errors. Check capacitor maintenance time (U4-05). Replace if >90%. Check capacity of power supply transformer. Check ambient temperature of the drive. Replace control board or drive if Charge LED is broken.
oPE01 Drive Capacity Setting Error	Cause: The value set in o2-04 [Drive Model (KVA) Selection] does not agree with the drive model. Remedy: Set o2-04 to the correct value.
oPE02 Parameter Range Setting Error	Cause: Parameters settings are not in the applicable setting range or conflict with other parameters. Specific conflicts include: Motor Rated Current (E2-01) ≤ No-Load Current (E2-03). Ambient Temp (L8-12) vs Installation Method (L8-35) conflicts. Multiplex Mode (Y1-01=3) vs Gateway Mode (F6-16). DriveWorksEZ (A1-07) enabled with Slave Address (q7-01) or MFDI conflicts. PI2 Control limits: S3-09 < S3-10 or S3-13 > S3-15. Relay Operator Control conflicts (o1-17 vs H2-xx). Remedy: Push UP/DOWN arrow to show U1-18 [oPE Fault Parameter] to find the specific parameter. Make sure E2-01 > E2-03. Set L8-35 = 0 or 2 (IP20/UL Open Type) if required. When Y1-01 = 3, set F6-16 = 0 or disable DriveWorksEZ. Ensure S3-09 > S3-10 and S3-13 < S3-15 at all times. Correct MFDO settings regarding H2-xx and o1-17.
oPE03 Multi-Function Input Setting Err	Cause: Conflicting or overlapping settings for Multi-Function Digital Inputs (H1-01 to H1-07, H7-xx). Common conflicts: Duplicate functions assigned to different terminals. Up Command (10) and Down Command (11) not set together. PID Mode (b5-01) enabled while Up/Down commands set. KEB Ride-Thru or Speed Search settings overlap. Run Command 2-Wire/3-Wire conflicts. Fast Stop N.O. (15) and N.C. (17) set simultaneously. Drive Enable (6A) or Drive Enable 2 (70) set on multiple terminals. Remedy: Check U1-18 to identify the conflicting parameters. Ensure Up/Down commands are set as a pair (10 and 11). Remove unused function settings. If b5-01 (PID) is enabled, remove Up/Down command settings. Set H1-xx correctly to prevent function overlap. Check 3-wire vs 2-wire sequence settings.
oPE05 Run Cmd/Freq Ref Source Sel Err	Cause: The setting to assign the Run command or frequency reference to an option card is incorrect. b1-01 or b1-02 = 3 (Option PCB) but no card connected. HAND-OFF-AUTO Behavior (S5-04) conflicts with b1-02. Remedy: Connect an option card to the drive. If S5-04 = 0 (Legacy), set b1-02 = 7, 8, or 9. If S5-10 = 2 (AUTO Key Memory), change b1-02 or S5-10 setting.
oPE07 Analog Input Selection Error	Cause: The settings for H3-02, H3-10 [MFAI Function Selection] and H7-30 [Virtual Analog Input Selection] overlap. Remedy: Set H3-02, H3-10, and H7-30 correctly to prevent overlap. Note: Multiple inputs can be set to 0 [Frequency Reference], F [Not Used], or 1F [Not Used] without error.
oPE08 Parameter Selection Error	Cause: A function is set that is not compatible with the control method (A1-02). Dynamic Noise Control (S1-01) enabled in V/f mode. PM Motor parameters (E5-xx) not set while in OLV/PM mode (A1-02 = 5). EZOLV mode (A1-02=8) conflicts with Motor Type (E9-01) or Speed Search (b3-24). Torque Detection Level (L6-02) < Motor Underload Level (L6-14). Remedy: Push UP/DOWN arrow to show U1-18 and find the specific parameter. If V/f mode, set S1-01 = 0 or Y4-42 = 0. If OLV/PM mode, set E5-01 correctly based on motor, or input E5-xx data from test report. If EZOLV mode, ensure E9-01 settings match b3-24 settings. Ensure L6-02 ≥ L6-14.
oPE09 PID Control Selection Fault	Cause: PID parameters set incorrectly. b5-01 (PID Mode) = 1 or 3, but other parameters like d2-02, Y1-06, Y4-12, Y1-01, or YF-01 are set to conflicting values. Remedy: Check settings for b5-01 vs d2-02, Y1-06, Y4-12, Y1-01, and YF-01. Correct the parameter settings to enable PID mode properly.
oPE10 V/f Data Setting Error	Cause: The parameters that set the V/f pattern do not satisfy logic conditions (e.g., Output Frequency ≤ Mid Point A ≤ Base Frequency, etc.). Remedy: Ensure E1-09 ≤ E1-07 < E1-06 ≤ E1-11 ≤ E1-04 for Motor 1. Ensure E3-09 ≤ E3-07 < E3-06 ≤ E3-11 ≤ E3-04 for Motor 2.
oPE11 Carrier Frequency Setting Error	Cause: Carrier Frequency parameters (C6-xx) are set incorrectly. C6-05 > 6 while C6-04 > C6-03. C6-02 to C6-05 are not in applicable range. Remedy: Set C6-02 to C6-05 correctly. Note: When C6-05 < 7, C6-04 becomes disabled.
oPE16 Energy Saving Constants Error	Cause: Energy Saving parameters (b8-01, S1-01) enabled but motor constants (E5-xx) are not set correctly. Remedy: Make sure E5-xx is set correctly as specified by motor nameplate. Disable Energy Saving Control (b8-01 = 0) or Dynamic Noise Control (S1-01 = 0).
oPE33 Digital Output Selection Error	Cause: Conflicting settings for Digital Outputs (Terminals M1-M2, M3-M4, M5-M6). Setting H2-xx to “Inverse output” (1xx) while the secondary function is also set. Remedy: Clear the H2-01 to H2-03 = 1xx [Inverse output] settings. It is not possible to use inverse output when using output functions for logic operations (H2-60/63/66 ≠ F).
oPE34 HAND/OFF/AUTO Input Setting	Cause: Conflict between S5-04 (HOA Behavior) and H1-xx (MFDI). AUTO Command (6D) and HAND Command (6E) set simultaneously. S5-04 = 1 but run command selection (b1-02) is not Digital Input. Remedy: Set only one of the two functions H1-xx = 6D or 6E. If S5-04 = 1 and b1-02 = 1, remove H1-xx = 6D setting.
oPE35 Network PI Aux Operation Mode	Cause: These parameter settings are not compatible: Y9-50 ≠ 0 [PI Auxiliary Control Source ≠ Analog Only]. Y9-51 = 1 [PI Aux Control Turn-Off Method = Enabled]. Remedy: Examine and correct the settings for Y9-50 and Y9-51.
End1 Excessive Rated Voltage Setting	Cause: The torque reference was more than 20% during Auto-Tuning or the no-load current that was measured after Auto-Tuning is more than 80%. Remedy: Make sure that the input motor nameplate data is correct. Do Auto-Tuning again and correctly set the motor nameplate data. If you can uncouple the motor and load, remove the motor from the machine and do Rotational Auto-Tuning again. If you cannot uncouple the motor and load, use the results from Auto-Tuning.
End2 Iron Core Saturation Coefficient	Cause: The motor nameplate data entered during Auto-Tuning is incorrect. Remedy: Make sure that the input motor nameplate data is correct. Do Auto-Tuning again and correctly set the motor nameplate data.
End3 Rated Current Setting Alarm	Cause: The rated current value is incorrect. Remedy: Do Auto-Tuning again and set the correct rated current shown on the motor nameplate.
End4 Adjusted Slip Calculation Error	Cause: The Auto-Tuning results were not in the applicable parameter setting range. The motor rated slip that was measured after Stationary Auto-Tuning was 0.2 Hz or lower. The secondary resistor measurement results were not in the applicable range. Remedy: Make sure the input motor nameplate data is correct. Do Rotational Auto-Tuning again and correctly set the motor nameplate data. If you cannot uncouple the motor and load, do Stationary Auto-Tuning 2.
End5 Resistance Tuning Error	Cause: The Auto-Tuning results of the Line-to-Line Resistance were not in the applicable range. Remedy: Make sure that the input motor nameplate data is correct. Examine and repair damaged motor wiring.
End6 Leakage Inductance Alarm	Cause: The Auto-Tuning results were not in the applicable parameter setting range. A1-02 [Control Method Selection] setting is not applicable. Remedy: Make sure that the input motor nameplate data is correct, and do Auto-Tuning again. Examine the value set in A1-02.
End7 No-Load Current Alarm	Cause: The Auto-Tuning results of the motor no-load current value were not in the applicable range. Auto-Tuning results were less than 5% of the motor rated current. Remedy: Examine and repair damaged motor wiring. Make sure that the input motor nameplate data is correct, and do Auto-Tuning again.
End8 HFI Alarm	Cause: Inductance saliency ratio (E5-07/E5-06) is too small. The drive cannot find the n8-36 [HFI Frequency Level for L Tuning] value. Remedy: Set the correct value on the motor nameplate to E5-xx [PM Motor Settings] or do rotational/stationary Auto-Tuning. When it is necessary to set n8-35 = 1, make sure that there is no unusual noise in the low speed range (10% or less) and that the motor does not rotate in reverse at start. Note: If the drive detects End8, it will automatically set n8-35 = 0. Do not change settings unless necessary.
End9 Initial Pole Detection Alarm	Cause: The drive cannot calculate the correct value for n8-84 [Polarity Detection Current] during High Frequency Injection Tuning. Remedy: When n8-35 = 1 [Initial Pole Detection Method = High Frequency Injection], make sure that the motor does not rotate in reverse at start. Note: If the drive detects End9, it will automatically set n8-35 = 0. Do not change settings unless necessary.
Er-01 Motor Data Error	Cause: The motor nameplate data entered during Auto-Tuning is incorrect. The combination of the motor rated power and motor rated current do not match. The combination of the motor rated current entered and E2-03 [Motor No-Load Current] do not match. The combination of Motor Base Frequency and Motor Base Speed do not match. Remedy: Make sure that the motor nameplate data is correct. Do Auto-Tuning again and correctly set the motor nameplate data. Examine the combination of drive capacity and motor output. Examine the motor rated current and the no-load current (Set E2-03 correctly). Do Auto-Tuning again, and correctly set the Motor Base Frequency and Motor Base Speed.
Er-02 Drive in an Alarm State	Cause: The motor nameplate data entered during Auto-Tuning is incorrect. You did Auto-Tuning while the drive had a minor fault or alarm. There is a defective motor cable or cable connection. The load is too large. The drive detected a minor fault during Auto-Tuning. Remedy: Make sure that the motor nameplate data entered in Auto-Tuning is correct. Clear the minor fault or alarm and do Auto-Tuning again. Examine and repair motor wiring. Decrease the load. Examine the machine area to see if the motor shaft is locked. Stop Auto-Tuning, remove the cause of the minor fault, and do Auto-Tuning again.
Er-03 OFF Button was Pressed	Cause: You pushed OFF during Auto-Tuning. Remedy: Auto-Tuning did not complete correctly. Do Auto-Tuning again.
Er-04 Line-to-Line Resistance Error	Cause: The Auto-Tuning results were not in the applicable parameter setting range. Auto-Tuning did not complete in a pre-set length of time. There is a defective motor cable or cable connection. The motor nameplate data entered during Auto-Tuning is incorrect. Remedy: Examine and repair motor wiring. Disconnect the machine from the motor and do Rotational Auto-Tuning again. Make sure that the input motor nameplate data is correct.
Er-05 No-Load Current Error	Cause: The Auto-Tuning results were not in the applicable parameter setting range. Auto-Tuning did not complete in a pre-set length of time. The motor nameplate data entered during Auto-Tuning is incorrect. Rotational Auto-Tuning was done with a load that was more than 30% of the rating connected to the motor. Remedy: Examine and repair motor wiring. Disconnect the machine from the motor and do Rotational Auto-Tuning again. Make sure that the input motor nameplate data is correct. If you cannot uncouple the motor/load, make sure load is < 30%. Release mechanical brakes if installed.
Er-08 Rated Slip Error	Cause: The motor nameplate data entered during Auto-Tuning is incorrect. Auto-Tuning did not complete in a pre-set length of time. The Auto-Tuning results were not in the applicable parameter setting range. Rotational Auto-Tuning was done with a load that was more than 30% of the rating connected to the motor. Remedy: Make sure that the input motor nameplate data is correct. Examine and repair the motor wiring. If the motor and machine are connected during Rotational Auto-Tuning, decouple the motor from the machinery. If you cannot uncouple, ensure load is < 30% and release brakes.
Er-09 Acceleration Error	Cause: The motor did not accelerate for the specified acceleration time. Rotational Auto-Tuning was done with a load that was more than 30% of the rating connected to the motor. Remedy: Increase the value set in C1-01 [Acceleration Time 1]. Disconnect the machine from the motor and do Rotational Auto-Tuning again. If you cannot uncouple, ensure load is < 30% and release brakes.
Er-12 Current Detection Error	Cause: There is a phase loss in the drive input power. (U/T1, V/T2, W/T3). The current exceeded the current rating of the drive. The output current is too low. You tried Auto-Tuning without a motor connected to the drive. There was a current detection signal error. Remedy: Examine and repair motor wiring. Check for short circuits between wires. Check and turn ON any magnetic contactors used between motors. Replace the control board or the drive. Connect the motor and do Auto-Tuning.
Er-13 Leakage Inductance Error	Cause: The motor rated current value is incorrect. The drive could not complete tuning for leakage inductance in fewer than 300 s. Remedy: Correctly set the rated current indicated on the motor nameplate and do Auto-Tuning again. Examine and repair motor wiring.
Er-18 Back EMF Error	Cause: The result of the induced voltage tuning was not in the applicable range. Remedy: Make sure that the input motor nameplate data is correct. Do Auto-Tuning again and correctly set the motor nameplate data.
Er-19 PM Inductance Error	Cause: The Auto-Tuning results of the PM motor inductance were not in the applicable range. Remedy: Make sure that the input motor nameplate data is correct. Do Auto-Tuning again and correctly set the motor nameplate data.
Er-20 Stator Resistance Error	Cause: The Auto-Tuning results of the PM Motor Stator Resistance were not in the applicable range. Remedy: Make sure that the input motor nameplate data is correct. Do Auto-Tuning again and correctly set the motor nameplate data.
Er-25 HighFreq Inject Param Tuning Err	Cause: The motor data is incorrect. Remedy: Do Stationary Auto-Tuning again. Note: If the drive detects Er-25 after you do Stationary Auto-Tuning, it is possible that the motor cannot use high frequency injection.
CPEr Control Mode Mismatch	Cause: The keypad setting and drive setting for A1-02 [Control Method Selection] do not agree. Remedy: Set A1-02 on the drive to the same value that is on the keypad. Restore the parameters.
CPyE Error Writing Data	Cause: Parameter restore did not end correctly. Remedy: Restore the parameters.
CSEr Control Mode Mismatch	Cause: The keypad is broken. Remedy: Replace the keypad.
dFPS Drive Model Mismatch	Cause: You tried to restore parameters to a different drive model than the one that you backed up. Remedy: Examine the drive model that you used to back up the parameters. Restore the parameters.
iFEr Keypad Communication Error	Cause: There was a communications error between the keypad and the drive. Remedy: Examine the connector or cable connection.
ndAT Error Received Data	Cause: The parameter settings for model and specifications (power supply voltage and capacity) are different between the keypad and the drive. Remedy: Make sure that drive model and the value set in o2-04 [Drive Model (KVA) Selection] agree. Restore the parameters. Cause: The parameters are not stored in the keypad. Remedy: Connect a keypad that has the correct parameters. Restore the parameters.
PWEr DWEZ Password Mismatch	Cause: The password set in the backup operation with qx-xx [DriveWorksEZ Parameters] and rx-xx [DriveWorksEZ Connections] is incorrect. Remedy: Set the DWEZ PC software password supplied by Yaskawa for the DWEZ program user ID downloaded to the drive.
rdEr Error Reading Data	Cause: You tried to back up the data when o3-02 = 0 [Copy Allowed Selection = Disabled]. Remedy: Set o3-02 = 1 [Enabled] and back up again.
vAEr Voltage Class, Capacity Mismatch	Cause: The power supply specifications or drive capacity parameter settings are different between the keypad and the drive. Remedy: Make sure that drive model and the value set in o2-04 [Drive Model (KVA) Selection] agree. Restore the parameters.
vFyE Parameters do not Match	Cause: The parameters that are backed up in the keypad and the parameters in the drive are not the same. Remedy: Restore or backup the parameter again. Verify the parameters.