Yaskawa FP605 Drive

Fault Code and MeaningCause 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.

  • 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.




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).

  • Do a Fault Reset to clear the fault.


bUS
Option Communication Error

Cause:

  • The drive did not receive a signal from the controller.

  • Communications cable wiring is incorrect, disconnected, or short-circuited.

  • Electrical interference caused a communication data error.

  • The option is incorrectly installed or damaged.




Remedy:

  • Correct wiring errors and repair short circuits.

  • Replace defective cables.

  • Examine control/main circuit lines and ground wiring to decrease interference.

  • Install a noise filter on the input side.

  • Correctly install the option to the drive.

  • If fault continues, replace the option.


CE
Modbus Communication Error

Cause:

  • Communications cable wiring is incorrect, short-circuited, or not connected.

  • Electrical interference caused a communication data error.




Remedy:

  • Correct wiring errors and repair short circuits.

  • Replace defective communications cables.

  • Check magnetic contactors for interference; use Surge Protective Device if necessary.

  • Use recommended shielded lines and ground the shield properly.

  • Separate communication wiring from drive power lines.


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].

  • 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.


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, 3330 to 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. For information about replacing the control board, 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
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.


CPF36
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.


CPF37
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.


CPF38
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.


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/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 [Acceleration/Deceleration Time].

  • Adjust F1-10 [Speed Deviation Detection Level] and F1-11 [Speed Deviation Detect Delay Time].

  • 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 [Differential Level] to Y4-20 [Differential Level Detection Sel] 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.


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; External Fault parameters set incorrectly.


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.

  • Correctly set the MFDI (H1-01).


EF2
External Fault (Terminal S2)

Cause:
MFDI terminal S2 caused an external fault through an external device; The wiring is incorrect; External Fault parameters set incorrectly.


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 S2.

  • Correctly set the MFDI (H1-02).


EF3
External Fault (Terminal S3)

Cause:
MFDI terminal S3 caused an external fault through an external device; The wiring is incorrect; External Fault parameters set incorrectly.


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 S3.

  • Correctly set the MFDI (H1-03).


EF4
External Fault (Terminal S4)

Cause:
MFDI terminal S4 caused an external fault through an external device; The wiring is incorrect; External Fault parameters set incorrectly.


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 S4.

  • Correctly set the MFDI (H1-04).


EF5
External Fault (Terminal S5)

Cause:
MFDI terminal S5 caused an external fault through an external device; The wiring is incorrect; External Fault parameters set incorrectly.


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 S5.

  • Correctly set the MFDI (H1-05).


EF6
External Fault (Terminal S6)

Cause:
MFDI terminal S6 caused an external fault through an external device; The wiring is incorrect; External Fault parameters set incorrectly.


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 S6.

  • Correctly set the MFDI (H1-06).


EF7
External Fault (Terminal S7)

Cause:
MFDI terminal S7 caused an external fault through an external device; The wiring is incorrect; External Fault parameters set incorrectly.


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 (H1-07).


EF8
External Fault (Terminal S8)

Cause:
MFDI terminal S8 caused an external fault through an external device; The wiring is incorrect; External Fault parameters set incorrectly.


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 S8.

  • Correctly set the MFDI (H1-08).


Err
EEPROM Write Error

Cause:
There was a problem with the EEPROM hardware; Electrical interference corrupted the data while it was writing to the EEPROM.


Remedy:

  • Re-energize the drive.

  • If the fault stays, replace the control board or the drive.

  • Push ENTER Key.

  • Set the parameters again.


FAn1
Drive Cooling Fan Fault

Cause:
The cooling fan stopped operating correctly; The circulation fan is damaged.


Remedy:

  • Examine cooling fan operation.

  • Re-energize the drive.

  • Examine U4-03 and U4-04. If performance life expired or fan damaged, replace fan.

  • Examine circulation fan operation.


FDBKL
WIRE Break

Cause:
The analog input from the terminal set for PID Feedback is more than 21mA or less than 3mA for longer than 1s.


Remedy:

  • Make sure that you install the PID feedback source and it operates correctly.


GF
Ground Fault

Cause:
Overheating caused damage to the motor/insulation; Main circuit cable contacting ground; Increase in stray capacitance; Problem with drive hardware.


Remedy:

  • Measure motor insulation resistance and replace motor if necessary.

  • Examine motor main circuit cable for damage and repair.

  • If wiring length > 100m, decrease carrier frequency.

  • Decrease stray capacitance.

  • Replace the control board or the drive.


HFB
High Feedback Sensed

Cause:
The feedback level is more 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 the level set in YF-12 for the time set in YF-13.


Remedy:

  • Decrease the PI Auxiliary Feedback level less than YF-12.

  • Set YF-12 and YF-13 correctly.


HLCE
High Level Communication Errors

Cause:
Communication data error occurred between the option and the master drive when using Gateway function.


Remedy:

  • Examine the wiring between the option and the master drive and remove the cause of the fault.


HWL
High Water Level

Cause:
The digital input terminal set to High Water Level is activated, deactivated, or defective (depending on setting).


Remedy:

  • Decrease the water level.

  • Adjust the terminal set to H1-xx = BC or 1BC.


LF
Output Phase Loss

Cause:
Motor main circuit cable disconnected; Disconnection in motor coil; Loose output terminal screws; Drive capacity mismatch; Using single-phase motor; Output transistor damaged.


Remedy:

  • Connect motor main circuit cable wiring. Correct wiring errors.

  • Measure motor Line-to-Line Resistance and replace motor if coil is disconnected.

  • Tighten terminal screws to correct torque.

  • Examine drive capacity vs motor output.

  • (Drive cannot operate single-phase motor).

  • Re-energize drive. If fault stays, replace control board or drive.


LF2
Output Current Imbalance

Cause:
Phase loss in wiring on output side; Loose terminal screws; Imbalance between three phases of PM motor impedance; Drive output circuit broken.


Remedy:

  • Examine for wiring errors or disconnected wires and repair.

  • Tighten terminal screws to correct torque.

  • Measure Line-to-Line Resistance and replace motor if necessary.

  • Re-energize drive. If fault stays, replace control board or drive.


LFB
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.

  • Set Y1-08 and Y1-09 correctly.


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 to be more than YF-09.

  • Set YF-09 and YF-10 correctly.


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 for the time set in Y1-20, and the output frequency is Y1-21 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.

  • Note: Do a Fault Reset to clear the fault.


LWL
Low Water Level

Cause: The digital input terminal set to H1-xx = BB [Low Water Level] is activated/defective, or the terminal set to H1-xx = 1BB [!Low Water Level] is deactivated/defective.



Remedy:

  • Increase the water level.

  • Adjust the terminal set to H1-xx = BB or 1BB.


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.



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.

  • Overheating caused damage to the motor or motor insulation is not satisfactory.

  • Short circuit or ground fault on the output side (cables or motor).

  • Acceleration time is too short.

  • The drive is operating a specialized motor or a motor larger than the drive’s rating.

  • A magnetic contactor was switched at the output.




Remedy:

  • Measure current flowing into the motor. Replace drive with larger capacity if necessary.

  • Measure motor insulation resistance; replace motor if insulation is unserviceable.

  • Check motor main circuit cable for short circuits or ground faults. Repair or replace cable.

  • Increase Acceleration Times (C1-01/C1-03) or S-Curve Characteristics (C2-01 to C2-04).

  • Ensure motor nameplate rating does not exceed drive rating.

  • Set operation sequence to not switch the magnetic contactor while the drive is outputting voltage.


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.



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. This may occur if DIP switches on JOHB-SMP3 are not set to a valid protocol.



Remedy:

  • Connect the option to the correct connector.

  • Remove power, wait for charge light to go off, then set DIP switches on the JOHB-SMP3 to the desired protocol.


oFA01
Option Fault/Connection Error

Cause: The option card connected to connector CN5-A 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.


oFA02
Duplicate Options

Cause: The same option cards or the same type of option cards are connected to connectors CN5-A and B.



Remedy:
Connect the option card to the correct connector.
oFA03
Diagnostic 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.


oFA04
Flash Write Mode

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.


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.


Note: Do a Fault Reset to clear the fault.
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.
oFb00

Option Not Compatible with Port

Cause:
The option connected to connector CN5-B is not compatible.


Remedy:

  • Connect the option to the correct connector.


Note: The communication options cannot connect to connector CN5-B.

Do a Fault Reset to clear the fault.

oFb01

Option Fault/Connection Error

Cause:
The option card connected to connector CN5-B was changed during operation.


Remedy:

  • De-energize the drive.

  • Refer to the option card manual and correctly connect the option card to the connector on the drive.


Note: Do a Fault Reset to clear the fault.
oFb02

Duplicate Options

Cause:
The same option cards or the same type of option cards are connected to connectors CN5-A and B.


Remedy:

  • Connect the option card to the correct connector.


Note: Do a Fault Reset to clear the fault.
oFb03

Diagnostic 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.


Note: Do a Fault Reset to clear the fault.
oFb04

Flash Write Mode

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.
oFb05

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.


Note: Do a Fault Reset to clear the fault.
oFb06

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.


Note: Do a Fault Reset to clear the fault.
oFb10

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.


Note: Do a Fault Reset to clear the fault.
oFb11

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.


Note: Do a Fault Reset to clear the fault.
oFb12

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.


Note: Do a Fault Reset to clear the fault.
oFb13

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.


Note: Do a Fault Reset to clear the fault.
oFb14

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.


Note: Do a Fault Reset to clear the fault.
oFb15

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.


Note: Do a Fault Reset to clear the fault.
oFb16

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.


Note: Do a Fault Reset to clear the fault.
oFb17

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.


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].


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.




Cause:
The load is too heavy.


Remedy:

  • Measure the output current.

  • Decrease the load.

  • Decrease the value set in C6-02 [Carrier Frequency Selection].




Cause:
The internal cooling fan of the drive stopped.


Remedy:

  • Use the procedures in this 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.


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.




Cause:
The load is too heavy.


Remedy:

  • Measure the output current.

  • 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.


Remedy:

  • Correct wiring errors.




Cause:
A fault occurred on the machine. Example: The machine is locked.


Remedy:

  • Examine the machine and remove the cause of the fault.





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.

  • Set E2-01 [Motor Rated Current (FLA)] correctly.

  • 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. Decrease values in E1-08 and E1-10.


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.

  • Set E2-01 [Motor Rated Current (FLA)] correctly.

  • Make sure that the motor cooling system is operating correctly.

  • Adjust E1-04 to E1-10 [V/f Pattern Parameters]. For motor 2, adjust E3-04 to E3-10.


Note: If E1-08 and E1-10 are set too low, the overload tolerance will decrease at low speeds.
oL1

Motor Overload

Cause:
The load is too heavy.


Remedy:

  • Decrease the load.

  • Reset oL1 when U4-16 < 100.




Cause:
The acceleration/deceleration times or cycle times are too short.


Remedy:

  • Examine the acceleration/deceleration times and the motor start/stop frequencies.

  • Increase the values set in C1-01 to C1-04.




Cause:
Overload occurred while running at low speed.


Remedy:

  • Decrease the load when running at low speed.

  • Increase the motor speed.

  • If the motor is run frequently at low speeds, replace the motor with a larger motor or use a drive-dedicated motor.




Cause:
L1-01 [Motor Overload (oL1) Protection] is set incorrectly.


Remedy:

  • Set L1-01 in as specified by the motor qualities for a drive-dedicated motor.




Cause:
The V/f pattern does not fit the motor qualities.


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. For motor 2, adjust E3-04 to E3-10. Decrease values in E1-08 and E1-10.




Cause:
E1-06 [Base Frequency] is set incorrectly.


Remedy:

  • Set E1-06 to the rated frequency shown on the motor nameplate.




Cause:
One drive is operating more than one motor.


Remedy:

  • Set L1-01 = 0 [Disabled], connect thermal overload relay to each motor to prevent damage to the motor.





Cause:
The electronic thermal protector qualities and the motor overload properties do not align.


Remedy:

  • Examine the motor qualities and set L1-01 correctly.

  • Connect a thermal overload relay to the motor.




Cause:
The electronic thermal protector is operating at an incorrect level.


Remedy:

  • Set E2-01 [Motor Rated Current (FLA)] correctly to the value specified by the motor nameplate.




Cause:
There is increased motor loss from overexcitation operation.


Remedy:

  • Lower the value set in n3-13 [OverexcitationBraking (OEB) Gain].

  • Set L3-04 ≠ 4.

  • Set n3-23 = 0.




Cause:
The speed search-related parameters are set incorrectly.


Remedy:

  • Examine the settings for all speed search related parameters.

  • Adjust b3-03.

  • Set b3-24 = 1 after Auto-Tuning.




Cause:
Phase loss in the input power supply is causing the output current to change.


Remedy:

  • Make sure that there is no phase loss, and repair problems.




Cause:
Overload occurred during overexcitation deceleration.


Remedy:

  • Decrease the value set in n3-13.

  • Decrease the value set in n3-21.


oL2

Drive Overload

Cause:
The load is too large.


Remedy:

  • Decrease the load.




Cause:
The acceleration/deceleration times or cycle times are too short.


Remedy:

  • Examine the acceleration/deceleration times and the motor start/stop frequencies.

  • Increase the values set in C1-01 to C1-04.




Cause:
The V/f pattern does not fit the motor qualities.


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. Decrease values in E1-08 and E1-10. For motor 2, adjust E3-04 to E3-10.




Cause:
The drive capacity is too small.


Remedy:

  • Replace the drive with a larger capacity model.




Cause:
Overload occurred while running at low speed.


Remedy:

  • Decrease the load when running at low speed.

  • Replace the drive with a larger capacity model.

  • Decrease the value set in C6-02 [Carrier Frequency Selection].




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 speed search-related parameters are set incorrectly.


Remedy:

  • Examine the settings for all speed search-related parameters.

  • Adjust b3-03.

  • Set b3-24 = 1 after Auto-Tuning.




Cause:
Phase loss in the input power supply is causing the output current to change.


Remedy:

  • Correct errors with the wiring for main circuit drive input power.

  • Make sure that there is no phase loss, and repair problems.




Cause:
Overload occurred during overexcitation deceleration.


Remedy:

  • Decrease the value set in n3-13.

  • Decrease the value set in n3-21.


oL3
Overtorque Detection 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 Detection 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.


oL7
High Slip Braking Overload

Cause: Load inertia too large, external force rotated motor, or HSB Overload Time (n3-04) is too small.



Remedy:

  • Decrease deceleration times in C1-02 and C1-04 for applications not using 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: Keypad not securely connected or connection cable 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 too short (regenerative energy flowing to drive).



Remedy:

  • Set L3-04 = 1 [Stall Prevention during Decel = General Purpose].

  • Increase C1-02 or C1-04 [Deceleration Times].

  • Perform Deceleration Rate Auto-Tuning.




Cause: Acceleration time too short.



Remedy:

  • Increase C1-01 or C1-03 [Acceleration Times].

  • Increase C2-02 [S-Curve Time @ End of Accel].

  • Set L3-11 = 1 [Overvoltage Suppression Select = Enabled].




Cause: Output cable/motor shorted to ground (charging main circuit capacitor).



Remedy:

  • Examine motor main circuit cable, terminals, and terminal box; remove ground faults.

  • Re-energize the drive.




Cause: Speed search parameters incorrect (during speed search, power loss recovery, or premium efficiency motor usage).



Remedy:

  • Set b3-19 ≠ 0 [Speed Search Restart Attempts].

  • Adjust b3-03 [Speed Search Deceleration Time].

  • Do Stationary Auto-Tuning for Line-to-Line Resistance, then set b3-24 = 1.

  • Increase L2-04 [Powerloss V/f Recovery Ramp Time].




Cause: Power supply voltage too high.



Remedy:

  • Decrease power supply voltage to align with drive rated voltage.




Cause: Electrical interference.



Remedy:

  • Examine control/main circuit lines and ground wiring.

  • Ensure magnetic contactor is not the source of interference; use Surge Protective Device.




Cause: Load inertia set incorrectly or Motor hunting.



Remedy:

  • Adjust L3-25 [Load Inertia Ratio].

  • Adjust n1-02 [Hunting Prevention Gain] and n8-45/n8-47.


ov2
DC Bus Overvoltage 2

Cause: Wiring is too long and DC bus voltage is too large.



Remedy:

  • Shorten the shielded motor cable.

  • Decrease the carrier frequency.

  • Switch on internal EMC filter (if power supply has neutral ground).


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: Input phase loss, loose wiring, or voltage changing too much.



Remedy:

  • Correct errors with wiring for main circuit drive input power.

  • Tighten terminal screws to correct torque.

  • Examine input power stability and magnetic contactor.

  • Set L8-05 = 0 [Input Phase Loss Protection Sel = Disabled] (if balance unsatisfactory).




Cause: Main circuit capacitors unserviceable.



Remedy:

  • Examine capacitor maintenance time (U4-05). If >90%, replace control board or drive.

  • If input power is correct but fault stays, replace control board or drive.


PSE
JOHB-SMP3 Protocol Set Error

Cause: DIP switches on JOHB-SMP3 card are at factory default or invalid.



Remedy:

  • Remove power, wait for charge light to go out, then set DIP switches to desired protocol.


SC
Short Circuit/IGBT Failure

Cause: Overheating damaged motor/insulation, motor main circuit cable grounding, or output short circuit.



Remedy:

  • Measure motor insulation resistance; replace motor if unserviceable.

  • Examine motor main circuit cable for damage/repair short circuits.

  • Check for short circuits in terminals +1, U/T1, V/T2, W/T3.

  • If short circuit exists, contact Yaskawa or sales representative.

  • When A1-02=5 (OLV/PM), set L8-27 correctly.


SCF
Safety Circuit Fault

Cause: The safety circuit is broken.



Remedy:

  • Make sure you ground the drive correctly and re-energize.

  • If fault stays, replace control board or drive.


SEr
Speed Search Retries Exceeded

Cause: Speed search-related parameters incorrect OR motor coasting in opposite direction.



Remedy:

  • Decrease b3-10 [Speed Estimation Detection Gain].

  • Increase b3-17 and b3-18 (Retry Current/Time).

  • Do Auto-Tuning again.

  • Set b3-14 = 1 [Bi-directional Speed Search = Enabled].


SPCNR
Single Phase Converter Not Ready

Cause: Digital input for Single Phase Converter deactivated (faulted or not ready).



Remedy:

  • Examine wiring between drive and converter.

  • Examine error code on converter.


STPo
Motor Step-Out Detected

Cause: Incorrect motor code, load too large/inertia too large, or acceleration/deceleration times too short.



Remedy:

  • Set E5-01 correctly.

  • Increase n8-55 [Motor to Load Inertia Ratio].

  • Increase n8-51 [Pull-in Current] (or adjust n8-79 if during decel).

  • Increase C1-01 to C1-04 times or C2-01 S-Curve.

  • Replace drive/motor with larger capacity.


TiM
Keypad Time Not Set

Cause: Battery is in keypad, but date and time are not set.



Remedy:

  • Use the keypad to set the date and time.


UL3
Undertorque Detection 1

Cause: Fault on machine (e.g., broken belt) or incorrect parameters.



Remedy:

  • Examine machine and remove cause.

  • Adjust L6-02 and L6-03 settings.


UL4
Undertorque Detection 2

Cause: Fault on machine (e.g., broken belt) or incorrect parameters.



Remedy:

  • Examine machine and remove cause.

  • Adjust L6-05 and L6-06 settings.


UL6
Underload or Belt Break Detected

Cause: Output current decreased less than motor underload curve (L6-14) for longer than L6-03.



Remedy:

  • Adjust L6-14 setting to set output current to stay above underload curve during normal operation.


Uv1
DC Bus Undervoltage

Cause: Phase loss, loose wiring, unstable input power, or magnetic contactor issue.



Remedy:

  • Correct wiring errors and tighten terminals.

  • Examine input power stability and magnetic contactor on main circuit side.




Cause: Loss of power or Capacitors unserviceable.



Remedy:

  • Use better power supply.

  • Examine U4-05 [Capacitor Maintenance]; replace board/drive if >90%.




Cause: Soft-charge bypass relay damaged.



Remedy:

  • Check U4-06; replace board or drive if >90%.


Uv2
Control Power Undervoltage

Cause: L2-02 [Power Loss Ride Through] increased but momentary power loss unit not connected OR hardware problem.



Remedy:

  • Connect the momentary power loss recovery unit to the drive.

  • Re-energize the drive.

  • If fault stays, replace control board or drive.


Uv3
Soft Charge Answerback Fault

Cause: Relay/contactor on soft-charge bypass is damaged OR air inside drive is too hot.



Remedy:

  • Re-energize the drive.

  • Check monitor U4-06; if >90%, replace board/drive.

  • Check the ambient temperature of the drive.


VLTS
Thermostat Fault

Cause: Digital input set for Thermostat Fault (H1-xx = 88) is active.



Remedy:

  • Examine the wiring or wait for the motor to cool.


AEr
Station Address Setting Error

Cause:

The node address for the communication option is not in the permitted setting range.



Remedy:

For CANopen communication, set F6-35 [CANopen Node ID Selection] correctly.
AUXFB
PI Aux Feedback Level Loss

Cause:

The analog input from the terminal set to H3-xx = 27 [MFAI Function Selection = PI Auxiliary Control Feedback Level] is more than 21 mA or less than 3 mA for longer than 1 s.



Remedy:

Repair transducer or wiring.
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, and the drive output stopped as shown by an external baseblock command.



Remedy:

Examine the external sequence and timing of the baseblock command input.
bCE
Bluetooth Communication Error

Cause:


  • The smartphone or tablet with DriveWizard Mobile or DriveWizard is too far from the keypad.

  • Radio waves from a different device are causing interference.




Remedy:

  • Move to 10 m (32.8 ft) or less from the keypad.

  • 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:

The drive detected a wire-break on the analog input terminal set for PID Feedback (or Main PID Feedback Transducer is broken).



Remedy:

  • Examine the connection of the Main PID Feedback Transducer.

  • 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 [PID Feedback] (or Transducer is broken).



Remedy:

  • Examine the connection of the Main PID Feedback Transducer.

  • Replace Main PID Feedback Transducer.


BuFbl
Backup Fdbk Lost Chk/Repl Xducer

Cause:

The drive detected wire-break on the analog input terminal set for PID Feedback Backup [H3-xx = 24].



Remedy:

  • Examine the connection of the Differential PID Feedback transducer.

  • Replace Backup PID Feedback Transducer.


bUS
Option Communication Error

Cause:


  • Communication cable wiring is incorrect or disconnected.

  • Short-circuit in communications cable.

  • Electrical interference.

  • Option card is incorrectly installed or damaged.




Remedy:

  • Correct wiring errors and repair short circuits.

  • Examine control/main circuit lines and ground wiring to decrease interference.

  • Use a Surge Protective Device on magnetic contactors if necessary.

  • Use shielded lines and separate communication wiring from drive power lines.

  • Correctly install or replace the option card.


bUSy
Busy

Cause:


  • You set the drive to use MEMOBUS/Modbus communications to change parameters, but you used the keypad.

  • You tried to change a parameter while the drive was changing setting.




Remedy:

  • Use MEMOBUS/Modbus communications to enter the command, then use the keypad.

  • Wait until the process is complete.


CALL
Serial Comm Transmission Error

Cause:


  • Communications cable wiring is incorrect, disconnected, or shorted.

  • Programming error on the controller side.

  • Damage to communications circuitry.

  • Termination resistor setting incorrect.




Remedy:

  • Correct wiring errors and replace defective cables.

  • Examine communications at start-up and correct programming errors.

  • Do a self-diagnostics check; replace control board if needed.

  • On the last drive in network, set DIP switch S2 to ON.


CE
Modbus Communication Error

Cause:


  • Communications cable wiring is incorrect, shorted, or disconnected.

  • Electrical interference.

  • Communication protocol is not compatible.

  • H5-09 [CE Detection Time] is too small.

  • Controller software/hardware issue.




Remedy:

  • Correct wiring errors and use shielded lines.

  • Examine controller settings and correct communication conditions (H5-xx).

  • Increase the value set in H5-09.

  • Examine the controller and remove the cause of the problem.


CE
Run at H5-34 (CE Go-To-Freq)

Cause:

(Same as standard CE Error)

Wiring incorrect, interference, protocol incompatibility, or timeout.



Remedy:

  • Repair short circuits and connect cables.

  • Examine control circuit lines and decrease electrical interference.

  • Check H5-xx settings and increase H5-09.

  • Examine the controller.


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 [Reload Now], 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.

  • dEv detection level settings (F1-10, F1-11) are incorrect.

  • The load is locked up or holding brake is stopping motor.




Remedy:

  • Decrease the load.

  • Increase values in C1-01 to C1-04.

  • Adjust F1-10 and F1-11.

  • Examine machine and release holding brake.


DIFF
Differential Feedback Exceeded

Cause:

The difference between the PID Feedback and Differential Level Source [H3-xx = 2D] is more than the level set in Y4-18.



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.
DS
De-Scale/De-Rag Active

Cause:

The terminal is set to H2-xx = C5 or 1C5 and the set length of run time elapsed.



Remedy:

  • If you do not want to De-Scale, set Y8-01 = 0.

  • Adjust the Y8-08 [Run Time before De-Scale] setting.


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, or programming error occurred.



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, or wiring is incorrect.



Remedy:

  • Find the device that caused the external fault and remove the cause.

  • Correctly connect the signal line to MFDI terminal S1.

  • Correctly set the MFDI parameters.


EF2
External Fault (Terminal S2)

Cause:

MFDI terminal S2 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.

  • Correctly connect the signal line to MFDI terminal S2.

  • Correctly set the MFDI parameters.


EF3
External Fault (Terminal S3)

Cause:

MFDI terminal S3 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.

  • Correctly connect the signal line to MFDI terminal S3.

  • Correctly set the MFDI parameters.


EF4
External Fault (Terminal S4)

Cause:

MFDI terminal S4 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.

  • Correctly connect the signal line to MFDI terminal S4.

  • Correctly set the MFDI parameters.


EF5
External Fault (Terminal S5)

Cause:

MFDI terminal S5 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.

  • Correctly connect the signal line to MFDI terminal S5.

  • Correctly set the MFDI parameters.


EF6
External Fault (Terminal S6)

Cause:

MFDI terminal S6 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.

  • Correctly connect the signal line to MFDI terminal S6.

  • Correctly set the MFDI parameters.


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.

  • Correctly connect the signal line to MFDI terminal S7.

  • Correctly set the MFDI parameters.


EF8
External Fault (Terminal S8)

Cause:

MFDI terminal S8 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.

  • Correctly connect the signal line to MFDI terminal S8.

  • Correctly set the MFDI parameters.


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: PID Feedback analog input is > 21 mA or < 3 mA for longer than 1s (Signal selection 4-20mA).


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 analog input is > 21 mA or < 3 mA for longer than 1s (Signal selection 4-20mA).


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:

  • The load is too heavy.

  • The acceleration time is too short.

  • The drive is trying to operate a specialized motor or a motor larger than the drive rating.




Remedy:



  • Decrease the load for applications with repetitive starts/stops or replace with larger drive.

  • Calculate necessary torque, increase acceleration times (C1-01/03), or adjust S-Curves (C2-01 to C2-04).

  • Examine motor nameplate and ensure drive rating matches motor rating.


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.

  • Set Y1-11 and Y1-12 correctly.


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/wiring errors.

  • Examine the external 24 V power supply for problems.


LCP

Low City Pressure

Cause: Insufficient pressure is present on the inlet to the pump.


Remedy:



  • Examine the pressure switch contact and control wiring.

  • Make sure suction pressure is present.

  • Set Y4-22 and Y4-23 correctly.

  • Deactivate the digital input set to Low City Pressure.


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:

  • Drive connected to USB.

  • Too many log files (>1000) or no memory space.

  • Communication error between keypad and drive.

  • Keypad does not support short-term data logs.




Remedy:



  • Put a micro SD card in the keypad.

  • Set o5-01 = 0 [Log Start/Stop Selection = OFF].

  • Connect a keypad that supports short-term data logs (REV: H or later).


LOP

Loss of Prime

Cause: Pump load is less than the level set in Y1-19 for the time set in Y1-20.


Remedy:



  • Examine a dry well, air in the system, or no water. Use priming method.

  • Allow system to pump water again if there is resistance.

  • Set Y1-18 to Y1-21 correctly.


LSP

Low Suction Pressure

Cause: An external input (Low Suction Pressure) has indicated insufficient suction pressure.


Remedy:



  • Examine pressure switch and wiring.

  • Make sure suction pressure is present.

  • Increase system pressure.

  • Set Y4-22 and Y4-23 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 or sales representative.
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.
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 pressure switch and wiring.

  • Make sure suction pressure is present.

  • Increase the water level.

  • Set Y4-22 and Y4-23 correctly.


NMS

Setpoint Not Met

Cause: The feedback deviates from the setpoint at a level more than Y1-15 for the 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: The output circuit between the drive and motor is open (current < 5% of FLA).


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:

  • High ambient temperature.

  • Not sufficient airflow around the drive / Dust clogging fan.

  • Internal cooling fan stopped.




Remedy:



  • Measure ambient temperature, increase airflow, install cooling device.

  • Check installation space and circulation.

  • Clean dust/debris.

  • Replace cooling fan and reset o4-03.


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 (oH2) by MFDI terminal.


oH3

Motor Overheat (PTC Input)

Cause:

  • Defective thermistor wiring.

  • Machine locked/Fault on machine.

  • Motor overheated (Load, Accel time, E2-01 setting, V/f pattern).




Remedy:



  • Correct wiring errors.

  • Examine machine and remove fault.

  • Decrease load, Increase C1-01 to C1-04, Check E2-01.

  • Check cooling system. Adjust V/f pattern (E1-04 to E1-10).


oL3

Overtorque 1

Cause:

  • A fault occurred on the machine (e.g., locked).

  • Parameters are incorrect for the load.




Remedy:



  • Examine the machine and remove the cause of the fault.

  • Adjust L6-02 and L6-03 settings.


oL4

Overtorque 2

Cause:

  • A fault occurred on the machine (e.g., locked).

  • Parameters are incorrect for the load.




Remedy:



  • Examine the machine and remove the cause of the fault.

  • Adjust L6-05 and L6-06 settings.


oS

Overspeed

Cause: There is overshoot.


Remedy:


Decrease C5-01 [ASR Proportional Gain 1] and increase C5-02 [ASR Integral Time 1].
ov

DC Bus Overvoltage

Cause:

  • Drive output cable/motor shorted to ground.

  • Power supply voltage too high.

  • Electrical interference (noise).




Remedy:



  • Examine motor main circuit cable, terminals, and motor box for ground faults.

  • Decrease power supply voltage to align with drive rated voltage.

  • Examine control/main circuit lines, grounding, and install Surge Protective Device if necessary.


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:

• You can change 150 parameters maximum.

• If you change parameters that have dependencies, the drive can detect ovEr when the number of changed parameters is fewer than 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:

  • There is a phase loss in the drive input power.

  • Loose wiring in the input power terminals.

  • The drive input power voltage is changing too much.

  • Unsatisfactory balance between voltage phases.

  • The main circuit capacitors are 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 the drive input power stable.

  • If the input power supply is good, examine the magnetic contactor on the main circuit side for problems.

  • Examine the capacitor maintenance time in monitor U4-05 [CapacitorMaintenance]. If U4-05 is more than 90%, replace the capacitor.

  • Re-energize the drive. If the alarm stays, replace the circuit board or the drive.



Note: The drive detects this error if the DC bus voltage changes irregularly without regeneration. Use L8-05 to enable/disable detection.

R-DNE

Remote Drive Disable

Cause:

  • The digital input set to H1-xx = BD [Remote Drive Disable] activated.

  • The digital input set to H1-xx = 1BD [!Remote Drive Disable] deactivated.




Remedy:

  • Examine the statuses of the digital input terminals set to H1-xx = BD or 1BD.


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.


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.


SPCNR

Single Phase Converter Not Ready

Cause: When YC-14 = 1, the digital input set to H1-xx = BE [Single Phase Converter Ready NC] deactivated to show that the attached converter is faulted or not ready.



Remedy:

  • Examine the wiring between the drive and converter.

  • Examine the error code on converter.


STo

Safe Torque OFF

Cause:

  • Safe Disable inputs H1-HC and H2-HC are open.

  • There is internal damage to the two Safe Disable channels.




Remedy:

  • Make sure that the Safe Disable signal is input from an external source to terminal H1-HC and H2-HC.

  • When the Safe Disable function is not in use, use a jumper to connect terminals H1-HC and H2-HC.

  • Replace the board or the drive (Contact Yaskawa).


SToF

Safe Torque OFF Hardware

Cause:

  • One of the two terminals H1-HC or H2-HC received the Safe Disable input signal.

  • The Safe Disable input signal is wired incorrectly.

  • There is internal damage to one Safe Disable channel.




Remedy:

  • Make sure that the Safe Disable signal is input from an external source to terminals H1-HC or H2-HC.

  • When the Safe Disable function is not in use, use a jumper to connect terminals H1-HC and H2-HC.

  • Replace the board or the drive.


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.



Note: Parameter o4-24 [bAT Detection selection] enables and disables TiM detection.

TrPC

IGBT Maintenance Time (90%)

Cause: The IGBT is at 90% of its performance life estimate.



Remedy:

  • Replace the IGBT or the drive. For more information, contact Yaskawa or your nearest sales representative.


UL3

Undertorque Detection 1

Cause:

  • A fault occurred on the machine. Example: There is a 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. Example: There is a 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.

  • The belt has broken disconnecting the motor from the load.




Remedy:

  • Examine parameters L6-13 [Motor Underload Curve Select] and L6-14.


Uv

Undervoltage

Cause:

  • The drive input power voltage is changing too much.

  • There is a phase loss in the drive input power.

  • There is loose wiring in the drive input power terminals.

  • There was a loss of power.

  • The main circuit capacitors have become unserviceable.

  • The drive input power transformer is too small and voltage drops when the power is switched on.

  • Air inside the drive is too hot.

  • The Charge LED is broken.




Remedy:

  • Examine the input power for problems and make stable.

  • Correct errors with the wiring for main circuit drive input power.

  • Tighten the terminal screws to the correct tightening torque.

  • Use a better power supply.

  • Examine capacitor maintenance time (U4-05). If > 90%, replace control board/drive.

  • Check for alarm when MCCB/ELCB/Magnetic Contactor is ON.

  • Check the capacity of the drive power supply transformer.

  • Check the ambient temperature of the drive.

  • Replace the control board or the entire drive.



Note: The drive detects this error if one of these conditions is correct when the Run command has not been input (while the drive is stopped):

– The DC bus voltage < L2-05

– The Contactor that prevents inrush current in the drive was opened.

– There is low voltage in the control drive input power.


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:

Parameter settings are not in the applicable setting range, or relationships between parameters are incorrect (e.g., Motor Rated Current E2-01 ≤ No-Load Current E2-03).



Remedy:

  • Push the enter key to show U1-18 [oPE Fault Parameter] to find the specific parameter causing the error.

  • Make sure E2-01 > E2-03.

  • Check Logical conflicts between L8-12 and L8-35 (Installation method vs Temperature).

  • Ensure PI2 Control limits are correct (S3-09 > S3-10 and S3-13 < S3-15).

  • Correct parameter settings as indicated by U1-18.



oPE03


Multi-Function Input Setting Err

Cause:

The settings for these parameters do not agree or overlap:

  • F3-10 to F3-25 [Terminal D1 to DF Function Selection]

  • H1-01 to H1-08 [Terminals S1 to S8 Function Selection]

  • H7-01 to H7-04 [Virtual Multi-Function Inputs]

  • MFDI pairs set incorrectly (e.g., Up/Down command set simultaneously).





Remedy:

  • Set the parameters correctly to prevent MFDI function overlap.

  • If using Up/Down or Run/FWD wire sequences, ensure pairs are set correctly.

  • Remove function settings that are not in use.



oPE05


Run Cmd/Freq Ref Source Sel Err

Cause:

The setting to assign the Run command or frequency reference to an option card or the pulse train input is incorrect.

  • Option PCB selected (b1-01=3 or b1-02=3) but no card connected.

  • Pulse Train Input selected (b1-01=4) but H6-01 is not 0.

  • Digital Input Data Length conflicts (F3-01 vs F3-03).





Remedy:

  • Connect an option card to the drive if Option PCB is selected.

  • Set H6-01 = 0 if using Pulse Train Input.

  • Set F3-03 = 2 [16-bit] if required.

  • Correct the parameter settings.



oPE07


Analog Input Selection Error

Cause:

The settings for H3-02, H3-06, H3-10 [MFAI Function Selection] and H7-30 [Virtual Analog Input Selection] overlap or conflict with PID settings.



Remedy:

  • Set H3-02, H3-06, H3-10, and H7-30 correctly to prevent overlap.

  • Set values to F or 1F [Not Used] for unused terminals.

  • If using Differential Level Source (H3-xx = 2D), ensure Y4-41 is set correctly for backup PID feedback.



oPE08


Parameter Selection Error

Cause:

You set a function that is not compatible with the control method set in A1-02.

  • V/f Control conflicts with Dynamic Noise Control (S1-01) or Output Disconnect (Y4-42).

  • PM Motor settings (E5-xx) incorrect for OLV/PM (A1-02=5).

  • Drive capacity/Motor mismatch for specific control modes.





Remedy:

  • Push the enter key to show U1-18 [oPE Fault Parameter].

  • Set S1-01 = 0 or Y4-42 = 0 if in V/f mode.

  • Set E5-01 correctly based on the motor nameplate.

  • Set E5-09 and E5-24 to 0 if required by the control mode.



oPE09


PID Control Selection Fault

Cause:

PID Control is enabled (b5-01=1) but conflicts with other parameters:

  • Frequency Reference Lower Limits (d2-02).

  • Sleep Level Type (Y2-01).

  • Thrust Frequency (Y4-12) or Minimum Speed (Y1-06).





Remedy:

  • Correct the parameter settings causing the conflict.

  • Verify b5-01 setting.



oPE10


V/f Data Setting Error

Cause:

The parameters that set the V/f pattern do not satisfy the required frequency conditions (Min ≤ Mid Point A ≤ Base ≤ Mid Point B ≤ Max).



Remedy:

  • Set parameters (E1-09 through E1-04 for Motor 1) correctly to satisfy the logical frequency order.



oPE11


Carrier Frequency Setting Error

Cause:

These parameters are set at the same time incorrectly:

  • C6-05 > 6 [Carrier Freq Proportional Gain].

  • C6-04 > C6-03 [Carrier Frequency Lower Limit > Upper Limit].





Remedy:

  • Set C6-02 to C6-05 correctly.



oPE16


Energy Saving Constants Error

Cause:

The Energy Saving parameters are not set in the applicable setting range, or Energy Saving Control overlaps with Dynamic Noise Control (S1-01=1).



Remedy:

  • Make sure E5-xx is set correctly as specified by motor nameplate data.

  • Disable Energy Saving Control or Dynamic Noise Control.



oPE33


Digital Output Selection Error

Cause:

Inverse output functions (H2-01 to H2-03 = 1xx) are selected while secondary functions (H2-60, H2-63, H2-66) are used.



Remedy:

  • Clear the H2-01 to H2-03 = 1xx [Inverse output of xx] settings.

  • Note: It is not possible to use inverse output when using output functions for logic operations.


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 [Pull-in]. Do not change the 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 [Pull-in]. Do not change the 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 that was entered and E2-03 [Motor No-Load Current] do not match.

– The combination of the setting values 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.


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, for example, the motor shaft is locked.

  • Examine the minor fault code and remove the cause of the problem.


Er-03
STOP Button was Pressed

Cause: During Auto-Tuning, STOP was pushed.



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.

  • Do Auto-Tuning again and correctly set the motor nameplate data.


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 and load, make sure that the load is less than 30% of the motor rating. If a mechanical brake is installed, release the brake during Rotational Auto-Tuning.


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.

  • Disconnect the machine from the motor and do Rotational Auto-Tuning again.

  • If you cannot uncouple the motor and load, make sure that the load is less than 30% of the motor rating and release any mechanical brake.


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 the motor and load, make sure that the load is less than 30% of the motor rating and release any mechanical brake.


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 the motor wiring for any short circuits between the 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. For more information, contact Yaskawa or your nearest sales representative.

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.


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.