Delta CP2000 Series drive

Delta CP2000 Series drive Fault Codes:

Fault Code and MeaningCause and Remedy

CE1



Communication error 1

(RS-485 Modbus illegal function code)

Cause:

  • Incorrect communication command from upper unit.

  • Malfunction caused by interference.

  • Different communication setting from the upper unit.

  • Disconnection or bad connection of the cable.




Remedy:

  • Check if the communication command is correct.

  • Verify the wiring and grounding of the communication circuit. Separate communication circuit from main circuit or wire at 90 degrees.

  • Check if the setting for Pr.09-02 is the same as the setting for the upper unit.

  • Check the cable and replace it if necessary.

CK1



Communication command error 1

(Keypad communication data, illegal function code)

Cause:

  • Incorrect communication command from keypad.

  • Malfunction caused by interference.

  • Different communication setting from keypad.

  • Disconnection or bad connection of the cable.




Remedy:

  • Remove the keypad and then reconnect it to the motor drive.

  • Verify the wiring and grounding. Separate communication circuit from main circuit.

  • Check if the Baud rate = 19200 bps, Format = RTU8, N, 2.

  • Check the cable and replace it if necessary.

CE2



Communication error 2

(RS-485 Modbus illegal data address)

Cause:

  • Incorrect communication command from upper unit.

  • Malfunction caused by interference.

  • Different communication setting from the upper unit.

  • Disconnection or bad connection of the cable.




Remedy:

  • Check if the communication command is correct.

  • Verify wiring and grounding. Separate communication circuit from main circuit.

  • Check if Pr.09-02 setting matches the upper unit.

  • Check the cable and replace it if necessary.

CK2



Communication address error

(Keypad communication data, illegal data address)

Cause:

  • Incorrect communication command from keypad.

  • Malfunction caused by interference.

  • Different communication setting from keypad.

  • Disconnection or bad connection of the cable.




Remedy:

  • Remove the keypad and then reconnect it to the motor drive.

  • Verify wiring and grounding. Separate communication circuit from main circuit.

  • Check if the Baud rate = 19200 bps, Format = RTU8, N, 2.

  • Check the cable and replace it if necessary.

CE3



Communication error 3

(RS-485 Modbus illegal data value)

Cause:

  • Incorrect communication command from upper unit.

  • Malfunction caused by interference.

  • Different communication setting from upper unit.

  • Disconnection or bad connection of the cable.




Remedy:

  • Check if the communication command is correct.

  • Verify wiring and grounding. Separate communication circuit from main circuit.

  • Check if Pr.09-02 setting matches the upper unit.

  • Check the cable and replace it if necessary.

CK3



Communication data error

(Keypad communication data, illegal data value)

Cause:

  • Incorrect communication command from keypad.

  • Malfunction caused by interference.

  • Different communication setting from keypad.

  • Disconnection or bad connection of the cable.




Remedy:

  • Remove the keypad and then reconnect it to the motor drive.

  • Verify wiring and grounding. Separate communication circuit from main circuit.

  • Check if the Baud rate = 19200 bps, Format = RTU8, N, 2.

  • Check the cable and replace it if necessary.

CE4



Communication error 4

(RS-485 Modbus data is written to read-only address)

Cause:

  • Incorrect communication command from upper unit.

  • Malfunction caused by interference.

  • Different communication setting from the upper unit.

  • Disconnection or bad connection of the cable.




Remedy:

  • Check if the communication command is correct.

  • Verify wiring and grounding. Separate communication circuit from main circuit.

  • Check if Pr.09-02 setting matches the upper unit.

  • Check the cable and replace it if is necessary.

CK4



Communication slave error

(Keypad communication data is written to read-only address)

Cause:

  • Incorrect communication command from keypad.

  • Malfunction caused by interference.

  • Different communication setting from keypad.

  • Disconnection or bad connection of the cable.




Remedy:

  • Remove the keypad and then reconnect it to the motor drive. If problem persists, check drive status (e.g. PLC function enablement).

  • Verify wiring and grounding. Separate communication circuit from main circuit.

  • Check if the Baud rate = 19200 bps, Format = RTU8, N, 2.

  • Check the cable and replace it if is necessary.

CE10



Communication error 10

(RS-485 Modbus transmission time-out)

Cause:

  • The upper unit does not transmit the communication command within Pr.09-03 setting time.

  • Malfunction caused by interference.

  • Different communication setting from the upper unit.

  • Disconnection or bad connection of the cable.




Remedy:

  • Check if the upper unit transmits the command within the setting time.

  • Verify wiring and grounding. Separate communication circuit from main circuit.

  • Check if Pr.09-02 setting matches the upper unit.

  • Check the cable and replace it if necessary.

CK10



Keypad communication time out

(Keypad communication data, transmission time-out)

Cause:

  • Incorrect communication command from keypad.

  • Malfunction caused by interference.

  • Different communication setting from keypad.

  • Disconnection or bad connection of the cable.




Remedy:

  • Remove the keypad and then reconnect it to the motor drive.

  • Verify wiring and grounding. Separate communication circuit from main circuit.

  • Check if the Baud rate = 19200 bps, Format = RTU8, N, 2.

  • Check the cable and replace it if necessary.

SE1



Save error 1

(Keypad COPY error 1: Keypad copy time-out)

Cause:

  • Communication connection error (interference, unacceptable command).

  • Keypad error.

  • Control board error.




Remedy:

  • Check if error occurs randomly or only when copying certain parameters.

  • If you cannot clear the error, please contact Delta.

SE2



Save error 2

(Keypad COPY error 2: parameter writing error)

Cause:

  • Attempting to copy new firmware version parameters to a drive with old firmware version.

  • Data error during copy process or failure to save to EEPROM.

  • Malfunction caused by interference.




Remedy:

  • Check the status of Data ROM and remove error causes first.

  • Verify wiring and grounding of the main circuit, control circuit, and encoder.

  • If you cannot clear the error, please contact Delta.

oH1



IGBT over-heating warning

(AC motor drive detects over-heating of IGBT)

Cause:

  • Ambient temperature or cabinet temperature too high.

  • Obstruction in ventilation hole or heat sink.

  • Cooling fan not running.

  • Insufficient ventilation space.

  • Drive overload or high carrier frequency.




Remedy:

  • Check ambient temperature and inspect ventilation holes.

  • Remove obstructions or replace cooling fan.

  • Install/add cooling fan or air conditioner to lower cabinet temperature.

  • Increase ventilation space.

  • Decrease loading, decrease carrier frequency, or replace with a larger capacity drive.

oH2



Board-level component overheating warning

(Detected over heat of board-level component)

Cause:

  • Ambient temperature or cabinet temperature too high.

  • Obstruction in ventilation hole or heat sink.

  • Cooling fan not running.

  • Insufficient ventilation space.

  • Drive overloaded.




Remedy:

  • Check ambient temperature and inspect ventilation holes.

  • Remove obstructions or replace cooling fan.

  • Install/add cooling fan or air conditioner.

  • Increase ventilation space.

  • Decrease loading, decrease carrier frequency, or replace with a larger capacity drive.

PID



PID feedback error

(PID feedback loss; analog signal < 4 mA)

Cause:

  • Loose or broken PID feedback wiring.

  • Feedback device malfunction.

  • Hardware error.




Remedy:

  • Tighten the terminals again or replace with a new cable.

  • Replace with a new feedback device.

  • If error persists after checking wiring, return to factory for repair.

AnL



ACI analog signal loss

(Analog input current loss < 4 mA)

Cause:

  • Loose or broken ACI wiring.

  • External device error.

  • Hardware error.




Remedy:

  • Tighten the terminals again or replace with a new cable.

  • Replace new device.

  • If error persists after checking wiring, return to factory for repair.

uC



Under current

(Low current detection)

Cause:

  • Broken motor cable.

  • Improper setting for the low current protection (Pr.06-71, Pr.06-72, Pr.06-73).

  • Low load.




Remedy:

  • Exclude the connection issue of the motor and its load.

  • Set the proper settings for Pr.06-71, Pr.06-72, and Pr.06-73.

  • Check the loading status and ensure it matches motor capacity.
oSPD
Over speed warning
Cause:

  • Improper setting for Pr.10-25 (FOC bandwidth).

  • Improper bandwidth setting for ASR speed controller.

  • Incorrect motor parameter setting.

  • Malfunction caused by interference.




Remedy:

  • Decrease setting value for Pr.10-25.

  • Increase the bandwidth setting for ASR speed controller.

  • Reset motor parameter and run parameter tuning.

  • Verify wiring of the control circuit and grounding to prevent interference.
dAvE
Deviation Warning
Cause:

  • Improper parameter setting for the slip error.

  • Improper setting for ASR parameter and acceleration/deceleration.

  • Accel./Decel. time is too short.

  • Motor locked.

  • Mechanical brake is not released.

  • Incorrect parameter setting of torque limit (Pr.06-12, Pr.11-17~20).

  • Malfunction caused by interference.




Remedy:

  • Reset proper value for Pr.10-13 and Pr.10-14.

  • Reset ASR parameters and set proper Accel./Decel. time.

  • Remove the causes of motor lock.

  • Check the active timing of the system.

  • Adjust to proper torque limit setting value.

  • Verify wiring of the control/main circuit to prevent interference.
PHL
Phase loss (Input phase loss)
Cause:

  • Phase loss of the input power.

  • Single phase power input on a three-phase model.

  • The power voltage has changed.

  • Loose wiring terminal of input power.

  • Input cable of 3-phase power is broken.

  • Unbalance in three-phase input power.




Remedy:

  • Verify wiring of the main circuit.

  • Use a model with voltage that matches the power.

  • Check if the MC of the main circuit is broken. Cycle power. If PHL persists, return to factory.

  • Tighten the terminal screws.

  • Replace the broken part of the cable.

  • Check settings for Pr.06-50 and Pr.06-52.

  • Check the status of three-phase power.
ot1
Over-torque 1
Cause:

  • Incorrect parameter setting (Pr.06-07, Pr.06-08).

  • Mechanical error (e.g., lock due to over-torque).

  • The load is too large.

  • Accel./Decel. time and working cycle is too short.

  • V/F voltage is too high.

  • Motor capacity is too small.

  • Over-load during low-speed operation.

  • Torque compensation is too large.

  • Improper speed tracking settings.




Remedy:

  • Configure settings for Pr.06-07 and Pr.06-08 again.

  • Remove causes of malfunction/lock.

  • Decrease loading or replace with larger capacity motor.

  • Increase setting values for Pr.01-12~01-19.

  • Adjust V/F curve (Pr.01-01~01-08), especially mid-point voltage.

  • Adjust torque compensation (Pr.07-26).

  • Correct parameter settings for speed tracking (Pr.07-09).
ot2
Over-torque 2
Cause:

  • Incorrect parameter setting (Pr.06-10, Pr.06-11).

  • Mechanical error / Load too large.

  • Accel./Decel. time too short.

  • V/F voltage is too high.

  • Motor capacity too small.

  • Torque compensation too large.

  • Improper speed tracking settings.




Remedy:

  • Configure settings for Pr.06-10 and Pr.06-11 again.

  • Remove mechanical lock / Decrease loading.

  • Increase Accel./Decel. time (Pr.01-12~01-19).

  • Adjust V/F curve (Motor 2, Pr.01-35~01-42).

  • Replace with larger capacity motor.

  • Adjust torque compensation (Pr.07-26).

  • Correct speed tracking settings (Pr.07-09).
oH3 (PTC)
Motor over-heating
Cause:

  • Motor locked or load too large.

  • Ambient temperature is too high.

  • Motor cooling system/fan error.

  • Operates at low-speed too long.

  • V/F voltage too high.

  • Incorrect motor rated current setting.

  • PTC improper setting/wiring.

  • Harmonics too high.




Remedy:

  • Clear motor lock / Decrease loading.

  • Install cooling fan/AC or change installation place.

  • Replace fan or check cooling system.

  • Decrease low-speed operation time or use dedicated motor.

  • Adjust V/F curve settings.

  • Configure correct rated current value.

  • Check connection between PTC thermistor and heat protection.

  • Use remedies to reduce harmonics.
oH3 (PT100)
Motor over-heating
Cause:

  • Motor locked or load too large.

  • Ambient temperature is too high.

  • Motor cooling system error.

  • Operates at low-speed too long.

  • V/F voltage too high.

  • Incorrect motor rated current setting.

  • PT100 improper setting/wiring.




Remedy:

  • Clear motor lock / Decrease loading.

  • Improve ambient cooling.

  • Check cooling system / Replace fan.

  • Decrease low-speed operation time or upgrade motor.

  • Adjust V/F curve settings.

  • Configure correct rated current.

  • Check connection between PT100 thermistor and heat protection.
oSL
Over slip warning
Cause:

  • Incorrect motor parameter.

  • Load is too large.

  • Improper settings for Pr.07-29, Pr.07-30, and Pr.10-29.




Remedy:

  • Check the motor parameter.

  • Decrease the loading.

  • Check the parameter settings for oSL protection.
tUn
Auto tuning
Cause:

  • The motor parameter is running auto-tuning.




Remedy:

  • When the auto-tuning is finished, the warning automatically clears.
OPHL
Output phase loss
Cause:

  • Unbalanced three-phase impedance of the motor.

  • Wiring is incorrect or cable broken.

  • Motor is single-phase (Drive requires three-phase).

  • Current sensor broken or loose control board cable.

  • Capacity of drive is larger than motor.




Remedy:

  • Replace the motor.

  • Check and replace the cable.

  • Choose a three-phase motor.

  • Reconnect control board cable. Check 3-phase current balance. Return to factory if error persists.

  • Choose matched capacity for drive and motor.
SE3
Copy model error 3
Cause:

  • Keypad copy between different power range drives.




Remedy:

  • It is mainly to prevent parameter copies between different HP/models. Perform Manual Reset.
CGdn
CANopen guarding time-out
Cause:

  • The guarding time is too short, or less detection times.

  • Malfunction caused by interference.




Remedy:

  • Increase the guarding time (Index 100C) and detection times.

  • Verify wiring/grounding. Separate communication circuit from main circuit (90 degrees).

  • Ensure communication circuit is wired in series.

  • Use CANopen cable or add terminating resistance.
CHbn
CANopen heartbeat error
Cause:

  • The heartbeat time is too short.

  • Malfunction caused by interference.

  • Communication cable is broken or bad connection.




Remedy:

  • Increase heartbeat time (Index 1016).

  • Verify wiring/grounding and separation from main circuit.

  • Ensure series wiring and terminating resistance.

  • Check or replace the communication cable.
CbFn
CANopen bus off error
Cause:

  • CANopen card is not installed (Hardware).

  • Master received wrong package (Software).

  • Too much interference on BUS.

  • CAN_H and CAN_L shorted.

  • Communication cable broken/bad connection.




Remedy:

  • Make sure the CANopen card is installed.

  • Reset CANopen speed (Pr.09-37).

  • Verify wiring, grounding, and separation from main circuit.

  • Use terminating resistance.

  • Check or replace communication cable.
CIdn
CANopen index error
Cause:

  • Incorrect setting of CANopen index.




Remedy:

  • Reset CANopen Index (Pr.00-02 = 7).
CAdn
CANopen station address error
Cause:

  • Incorrect setting of CANopen station address (Only supports 1-127).




Remedy:

  • Disable CANopen (Pr.09-36 = 0).

  • Reset CANopen (Pr.00-02 = 7).

  • Reset CANopen station address (Pr.09-36).
CFrn
CANopen memory error
Cause:

  • CANopen internal memory error (often after firmware update).




Remedy:

  • Disable CANopen (Pr.09-36 = 0).

  • Reset CANopen (Pr.00-20 = 7).

  • Reset CANopen station address (Pr.09-36).
CSdn (ID 43)
CANopen SDO time-out
Cause:

  • Slave is not connected.

  • The synchronize cycle is set too short.

  • Malfunction caused by interference.

  • Disconnection or bad connection of the communication cable.




Remedy:

  • Connect slave and CANopen BUS.

  • Increase the synchronization time (Index 1006).

  • Verify wiring and grounding. Separate communication circuit from main circuit (or wire at 90 degrees). Ensure series wiring. Use CANopen cable or add terminating resistance.

  • Check the status of the cable, or replace the cable.
CSbn (ID 44)
CANopen SDO receives register overflow
Cause:

  • Too much SDO from the upper unit (causes buffer overflow).




Remedy:

  • Check if the master sends too much SDO command.

  • Make sure the master sends SDO command according to the command format.
CPtn (ID 46)
CANopen format error
Cause:

  • The upper unit sends incorrect communication packet (slave cannot recognize data).




Remedy:

  • Make sure the master sends the packet based on CANopen DS301 standard command format.
PLrA (ID 47)
RTC adjust
Cause:

  • RTC time different after drive powered off > 7 days.

  • KPC-CC01 disconnected for a long time.

  • KPC-CC01 does not adjust the RTC time.

  • PLC detects unreasonable RTC time.




Remedy:

  • Stop the PLC program and restart it.

  • Adjust the RTC time and cycle the power.

  • If necessary, replace with a new KPC-CC01.
PLiC (ID 48)
InnerCOM error
Cause:

  • Communication cable is loose.

  • Malfunction caused by interference.




Remedy:

  • Check the connection of the communication cable.

  • Verify wiring and grounding. Separate communication circuit from main circuit.

  • Install terminal resistor(s) on the first and last unit of the communication circuit.
PLrt (ID 49)
Keypad RTC time-out
Cause:

  • KPC-CC01 is not connected to the control board while using the RTC function.




Remedy:

  • Do not remove the KPC-CC01 keypad while using RTC function.
PLod (ID 50)
PLC opposite defect (Download error)
Cause:

  • Incorrect component number is found when downloading the PLC program.

  • Source code detects incorrect address (e.g. exceeds range).




Remedy:

  • Use the correct component number.

  • Check if the program is correct and re-download.
PLSv (ID 51)
PLC save memory error
Cause:

  • An incorrect written address is detected during PLC operation (e.g. address exceeds range).




Remedy:

  • Make sure the write-in address is correct and re-download the program.
PLdA (ID 52)
Data defect
Cause:

  • External Modbus has written/read incorrect data to internal PLC program.

  • Program detects incorrect write-in address when decoding/downloading.




Remedy:

  • Check if the upper unit transmits the correct command.

  • Check if the program is correct and re-download the program.
PLFn (ID 53)
Function defect
Cause:

  • Unsupported command has used while downloading the program.




Remedy:

  • Check if the firmware of the drive is the old version. If yes, contact Delta.

  • Check if the program is correct and re-download.
PLor (ID 54)
PLC buffer overflow
Cause:

  • The program detects source code error during PLC operation (command exceeds maximum capacity).




Remedy:

  • Disable PLC.

  • Delete PLC program (Pr.00-02 = 6).

  • Enable PLC.

  • Re-download PLC program.
PLFF (ID 55)
Function defect (Code error)
Cause:

  • The PLC runs an incorrect command during operation.

  • There is no program in the PLC (normal warning in this state).




Remedy:

  • Check if the program is correct and re-download the program.
PLSn (ID 56)
Checksum error
Cause:

  • The program detects checksum error during PLC operation (after power on).




Remedy:

  • Disable PLC.

  • Remove PLC program (Pr.00-02 = 6).

  • Enable PLC.

  • Re-download PLC program.
PLEd (ID 57)
No end command
Cause:

  • There is no “END” command during PLC operation.




Remedy:

  • Disable PLC.

  • Remove PLC program (Pr.00-02 = 6).

  • Enable PLC.

  • Re-download PLC program.
PLCr (ID 58)
PLC MCR error
Cause:

  • The MC command is continuously used for more than 9 times.

  • No corresponded MCR command detected.




Remedy:

  • The MC command cannot be used continuously for 9 times. Check and reset the program.

  • Re-download the program.
PLdF (ID 59)
PLC download fail
Cause:

  • PLC download is forced to stop, so the program write-in is incomplete.

  • Momentary power loss during downloading.




Remedy:

  • Check if there is any error in the program and re-download the PLC program.
PLSF (ID 60)
PLC scan time fail
Cause:

  • The PLC scan time exceeds the maximum allowable time (400ms).




Remedy:

  • Check if the source code is correct and re-download the program.
PCGd (ID 61)
CAN/M guarding error
Cause:

  • Slave is not connected or CANopen BUS cable is not connected.

  • Malfunction caused by interference.

  • Communication cable is broken or bad connected.




Remedy:

  • Connect the Slave and CANopen BUS.

  • Verify wiring/grounding of communication circuit (separate from main circuit/wire 90 deg).

  • Make sure communication circuit is wired in series.

  • Use CANopen cable or add terminating resistance.

  • Check or replace the communication cable.
PCbF (ID 62)
CAN/M BUS off
Cause:

  • Malfunction caused by interference (error packets > 255).

  • Communication cable is broken or bad connected.




Remedy:

  • Verify wiring/grounding of communication circuit.

  • Make sure communication circuit is wired in series.

  • Use CANopen cable or add terminating resistance.

  • Check or replace the communication cable.
PCnL (ID 63)
CAN/M node lack
Cause:

  • The configured node quantity is different from the actual nodes.

  • Communication cable is broken or bad connected.




Remedy:

  • Connect BUS to the original slave, or change the configured node numbers to meet the actual node quantity.

  • Check or replace the communication cable.
PCCt
CANopen Master cycle time-out
Cause:

When the transmitted packet from CANopen master exceeds the maximum allowable quantity in a certain time.



Remedy:

Increase the time setting of D1090 synchronization cycle.
PCSF
CANopen Master SDO overflow
Cause:

Internal PLC transmits too much SDO at once.



Remedy:

The PLC program needs to confirm receiving the SDO feedback data before sending another SDO command.
PCSd
CANopen Master SDO time-out
Cause:

When the CANopen master transmits a SDO command, and does not receive feedback from the Slave within 1 sec.



Remedy:

Check if the Slave responds within 1 second.
PCAd
CANopen Master station address error
Cause:

When the CANopen master detects an incorrect or repeated station address from the Slave.



Remedy:

Set the correct slave station address.
PCTo
CAN/M time-out
Cause:

Malfunction caused by interference OR The command from the upper unit does not meet the CANopen format.



Remedy:

  • Verify wiring/grounding of the communication circuit (separate from main circuit or wire 90 degrees).

  • Make sure the communication circuit is wired in series.

  • Use CANopen cable or add terminating resistance.

  • Contact Delta for further confirmation.
ECid
ExCom ID fail (Duplicate MAC ID error)
Cause:

  • The setting address exceeds the range (0–63).

  • The speed setting exceeds the range.

  • The address is duplicated with other nodes on the BUS.




Remedy:

  • Check the address setting of the communication card (Pr.09-70).

  • Standard: 0–2, non-standard: 0–7.

  • Reset the address.
ECLv
ExCom power loss (Low voltage of communication card)
Cause:

The 5V power that drive provides to communication card is too low OR The card is loose.



Remedy:

  • Switch the communication card to other CP2000 drives. If error persists, replace card; if not, replace drive.

  • Use another communication card to test. If error persists, replace drive; if not, replace card.

  • Make sure the communication card is well inserted.
ECtt
ExCom test mode
Cause:

Communication command error.



Remedy:

Cycle the power.
ECbF
ExCom Bus off
Cause:

Poor connection of the cable OR Bad quality of the cable.



Remedy:

Re-connect the cable OR Replace the cable.
ECnP
ExCom no power (No power on DeviceNet)
Cause:

The drive detects that DeviceNet has no power.



Remedy:

Check if the cable and power is normal. If yes, return to the factory for repair.
ECFF
ExCom factory defect
Cause:

Factory default setting error.



Remedy:

Use DCISoft to reset to the default value.
ECiF
ExCom inner error
Cause:

Noise interference OR The memory is broken.



Remedy:

  • Verify wiring of the control circuit and wiring/grounding of the main circuit.

  • Cycle the power.

  • Reset to the default value. If error exists, replace communication card.
ECio
ExCom IO Net break
Cause:

The cable is loose OR Incorrect parameter setting for master communication.



Remedy:

Re-install the cable OR Check the setting for master communication parameter.
ECPP
ExCom Parameter data error
Cause:

The GSD file is incorrect.



Remedy:

Get the correct GSD file from the software.
ECPi
ExCom configuration data error
Cause:

The GSD file is incorrect.



Remedy:

Get the correct GSD file from the software.
ECEF
Ethernet link fail
Cause:

Ethernet cable is loose OR Bad quality of Ethernet cable.



Remedy:

Re-connect the cable OR Replace the cable.
ECto
Communication time-out
Cause:

Communication card is not connected with the upper unit OR Communication error of the upper unit.



Remedy:

Check if the connection of the communication cable is correct OR Check if the communication of the upper unit is normal.
ECCS
Checksum error
Cause:

Noise interference.



Remedy:

Verify wiring of the control circuit, and wiring/grounding of the main circuit to prevent interference.
ECrF
Return defect
Cause:

Communication card is returning to default setting.



Remedy:

No actions.
Eco0
Modbus TCP over
Cause:

  • Master communication value > allowable quantity.

  • Upper unit is online without communicating/does not break off link.

  • New Modbus TCP connection built every time upper unit connects.




Remedy:

  • Reduce Master communication value.

  • Revise program of upper unit (break off communication when not used).

  • Revise program of upper unit (use same Modbus TCP connection).
ECo1
EtherNet/IP over
Cause:

  • Master communication value > allowable quantity.

  • Upper unit is online without communicating/does not break off link.

  • New Modbus TCP connection built every time upper unit connects.




Remedy:

  • Reduce Master communication value.

  • Revise program of upper unit (break off communication when not used).

  • Revise program of upper unit (use same Modbus TCP connection).
ECiP
IP fail (IP setting error)
Cause:

IP conflict OR DHCP IP configuration error.



Remedy:

Reset IP OR MIS check if DHCP Server works normally.
EC3F
Mail fail
Cause:

Communication card establishes alarm conditions.



Remedy:

No actions.
ECbY
ExCom busy
Cause:

Communication packets are too much for the communication card to process.



Remedy:

Reduce communication packets.
ECCb
ExCom card break
Cause:

Communication card break off.



Remedy:

Re-install communication card.
CPLP (90)

Copy PLC: password error
Cause: PLC password is incorrect (during PLC copy process).



Remedy:

  • Reset and enter correct PLC password.
CPL0 (91)

Copy PLC: Read mode error
Cause: When copy PLC read mode and the process is incorrect.



Remedy:

  • Cycle the power and copy PLC read mode again.
CPL1 (92)

Copy PLC: Write mode error
Cause: When copy PLC write mode and the process is incorrect.



Remedy:

  • Cycle the power and copy PLC read mode again.
CPLv (93)

Copy PLC: version error
Cause: Non-CP2000 PLC program is copied to CP2000.



Remedy:

  • Check if the copied PLC program is for CP2000.

  • Use the correct CP2000 PLC program.
CPLS (94)

Copy PLC: size error
Cause: The PLC copied to CP2000 exceeds the allowable capacity.



Remedy:

  • Check if the copied PLC program is for CP2000.

  • Use CP2000 PLC program with correct capacity.
CPLF (95)

Copy PLC: PLC function
Cause: PLC function is enabled when KPC-CC01 is running copy PLC.



Remedy:

  • Disable PLC function first, then run the PLC copy function again.
CPLt (96)

Copy PLC: time-out
Cause: KPC-CC01 is removed while copying PLC program.



Remedy:

  • The KPC-CC01 cannot be removed during the PLC copy process.
ictn (101)

InrCOM time-out
Cause:

  • Malfunction caused by interference.

  • Different communication conditions with the upper unit.

  • Communication cable break off or not connected well.




Remedy:

  • Verify wiring/grounding of communication circuit (separate from main circuit or wire 90 degrees).

  • Check if Pr.09-02 setting matches the upper unit.

  • Check cable status or replace the cable.
SpdR (105)

Estimated speed reverse
Cause:

  • The motor runs in reverse direction at start.

  • Difference between measured Rr and Rs value is too large.

  • Insufficient output torque is dragged to reverse direction by load.




Remedy:

  • Check if motor is held when started, or start motor with speed source.

  • Proceed with motor parameter auto-tuning again.

  • Increase current limit (Pr.06-12) to increase output torque.
dEb (123)

Deceleration energy backup
Cause: Instantaneous power off or low voltage and unstable/sudden heavy load causing voltage drop.



Remedy:

  • Check the power consumption.
ocA (1)

Over-current during acceleration
Cause:

  • Acceleration time is too short.

  • Short circuit at motor output (poor insulation/wiring).

  • Motor burnout or aging insulation.

  • Load is too large.

  • Impulsive change of load.

  • Torque compensation too large.




Remedy:

  • Increase acceleration time (or S-curve time).

  • Check motor cable and remove short circuits.

  • Check motor insulation with megger.

  • Replace drive with larger capacity model if load exceeds rating.

  • Check contactor timing at output (U/V/W).

  • Adjust V/F curve setting (reduce voltage if too high).

  • Adjust torque compensation (Pr.07-26).

  • Perform speed tracking if motor starts in free run.
ocd (2)

Over-current during deceleration
Cause:

  • Deceleration time too short.

  • Mechanical brake activates too early.

  • Short-circuit or ground fault at output.

  • Load too large or impulsive change.

  • Hardware error.




Remedy:

  • Increase deceleration time.

  • Check action timing of mechanical brake.

  • Check motor cable and insulation (megger).

  • Install AC reactor on output side if cable is too long.

  • Check for short circuits between terminals (U, V, W) and ground.
ocn (3)

Over-current during steady operation
Cause:

  • Short-circuit at motor output.

  • Motor shaft lock / burnout.

  • Impulsive load change.

  • Over-torque offset value too high.




Remedy:

  • Check motor cable and remove short circuits.

  • Troubleshoot motor shaft lock or insulation.

  • Check motor capacity vs drive rating.

  • Adjust Over-torque offset and Torque compensation (Pr.07-26).

  • Install AC reactor if motor cable is too long.
GFF (4)

Ground fault
Cause:

  • Motor burnout or aging insulation.

  • Short circuit due to broken cable.

  • Large stray capacitance (long cable).

  • Hardware failure.




Remedy:

  • Check motor insulation with megger.

  • Replace broken cables.

  • Decrease carrier frequency if cable length > 100m.

  • Return to factory if hardware failure persists after checking external factors.
occ (5)

IGBT short circuit
Cause: IGBT error or Short-circuit detecting circuit error.



Remedy:

  • Check motor wiring.

  • Cycle power; if error persists, return to factory.
ocS (6)

Over-current at stop
Cause: Over-current or hardware failure in current detection at stop.



Remedy:

  • Verify wiring/grounding to prevent interference.

  • Cycle power. If hardware failure (cd1, cd2, cd3) shows, return to factory.
ovA (7)

Over-voltage during acceleration
Cause:

  • Acceleration is too slow (regenerative energy).

  • Power voltage too high or surge from phase-in capacitor.

  • Regenerative voltage of motor inertia.

  • Motor ground fault.




Remedy:

  • Decrease acceleration time or use brake unit/DC bus.

  • Check input voltage range.

  • Install AC reactor if power system causes surges.

  • Use over-voltage stall prevention (Pr.06-01).

  • Check wiring of brake resistor/unit.
ovd (8)

Over-voltage during deceleration
Cause:

  • Deceleration time too short (large regenerative energy).

  • Stall prevention level too small.

  • Power voltage too high.

  • Motor ground fault.




Remedy:

  • Increase deceleration time.

  • Connect brake resistor, brake unit, or DC bus.

  • Use S-curve acceleration/deceleration.

  • Adjust braking level.

  • Install AC reactor for power surges.

  • Troubleshoot ground faults on motor cable/terminals.

ovn


Over-voltage at constant speed

Cause:




  • Impulsive change of the load.

  • The setting for stall prevention level is smaller than no-load current.

  • Regenerative voltage of motor inertia.

  • Power voltage is too high.

  • ON/OFF switch action of phase-in capacitor in the same power system.

  • Motor ground fault.

  • Incorrect wiring of brake resistor or brake unit.

  • Malfunction caused by interference.



Remedy:




  • Connect brake resistor, brake unit or DC bus to the drive; Reduce load; Replace with larger capacity model.

  • Ensure stall prevention level is larger than no-load current.

  • Use over-voltage stall prevention function (Pr.06-01) or a brake unit.

  • Check if input voltage is within rated range and check for voltage spikes.

  • Install an AC reactor if power supply surges occur.

  • Check for ground faults on motor cable, wiring box, and terminals.

  • Verify wiring of brake resistor/unit.

  • Verify control circuit wiring and grounding to prevent interference.

ovS


Over-voltage at stop

Cause:




  • Power voltage is too high.

  • ON/OFF switch action of phase-in capacitor in the same power system.

  • Incorrect wiring of brake resistor or brake unit.

  • Malfunction caused by interference.

  • Hardware failure in voltage detection.

  • Motor ground fault.



Remedy:




  • Check if input voltage is within rated range.

  • Install an AC reactor.

  • Check wiring of brake resistor/unit.

  • Verify wiring and grounding.

  • Check if error codes cd1–cd3 occur after cycling power; return to factory if yes.

  • Check for ground faults on motor cable and terminals.

LvA


Low-voltage during acceleration

Cause:




  • Power-off or poor power supply condition.

  • Power voltage changes.

  • Starting up a motor with large capacity.

  • The load is too large.

  • DC bus issues.

  • Missing short-circuit plate or DC reactor between terminals +1 and +2.



Remedy:




  • Improve power supply condition.

  • Adjust voltage to the power range of the drive.

  • Check power system and increase capacity of power equipment.

  • Reduce load, increase drive capacity, or increase acceleration time.

  • Install DC reactor(s).

  • Connect short circuit plate or DC reactor between terminal +1 and +2.

Lvd


Low-voltage during deceleration

Cause:




  • Power-off or poor power supply condition.

  • Power voltage changes.

  • Starting up a motor with large capacity.

  • Sudden load.



Remedy:




  • Improve power supply condition.

  • Adjust voltage to the power range of the drive.

  • Check power system and increase capacity of power equipment.

  • Reduce the load or increase the drive capacity.

  • Install DC reactor(s).

Lvn


Low-voltage at constant speed

Cause:




  • Power-off or poor power supply condition.

  • Power voltage changes.

  • Starting up a motor with large capacity.

  • Sudden load.



Remedy:




  • Improve power supply condition.

  • Adjust voltage to the power range of the drive.

  • Check power system and increase capacity of power equipment.

  • Reduce the load or increase the drive capacity.

  • Install DC reactor(s).

LvS


Low-voltage at stop

Cause:




  • Power-off or poor power supply condition.

  • Incorrect drive models (power spec mismatch).

  • Power voltage changes.

  • Starting up a motor with large capacity.



Remedy:




  • Improve power supply condition.

  • Check if the power specification matches the drive.

  • Adjust voltage to power range. Cycle power; if error exists, return to factory.

  • Check power system and increase capacity of power equipment.

  • Install DC reactor(s).

OrP


Phase loss protection (Input)

Cause:




  • Phase loss of input power.

  • Single phase power input to three-phase model.

  • Power voltage changes.

  • Loose wiring terminal of input power.

  • The input cable of three-phase power is cut off.

  • Input power voltage changes too much.

  • Unbalanced three-phase input power.



Remedy:




  • Correctly install the wiring of the main circuit power.

  • Choose the model whose power matches the voltage.

  • Verify main circuit; cycle power. Return to factory if error persists.

  • Tighten terminal screws according to torque manual.

  • Wire correctly and replace cut cables.

  • Verify settings for Pr.06-50 (Time for Input Phase Loss) and Pr.06-52.

  • Check the power three-phase status.

oH1


IGBT overheating

Cause:




  • Ambient temperature/cabinet temperature too high or obstruction in ventilation.

  • Obstruction on heat sink or fan not running.

  • Insufficient ventilation space.

  • Drive does not match the load.

  • Drive has run at >100% rated output for a long time.



Remedy:




  • Check ambient temp, inspect ventilation holes, remove heating objects, or install cooling fan/AC.

  • Remove obstruction or replace cooling fan.

  • Increase ventilation space of the drive.

  • Reduce load, reduce carrier frequency, or replace with larger capacity drive.

  • Replace the drive with a larger capacity model.

oH2


Board level component overheating

Cause:




  • Ambient temperature/cabinet temperature too high or obstruction in ventilation.

  • Obstruction on heat sink or fan not running.

  • Insufficient ventilation space.

  • Drive does not match the load.

  • Unstable power.

  • Load changes frequently.



Remedy:




  • Check ambient temp, inspect ventilation holes, remove heating objects, or install cooling fan/AC.

  • Remove obstruction or replace cooling fan.

  • Increase ventilation space of the drive.

  • Reduce load, reduce carrier frequency, or replace with larger capacity drive.

  • Install reactor(s).

  • Reduce load changes.

tH1o


IGBT temperature detection failure

Cause:




  • Hardware failure (NTC broken or wiring failure).



Remedy:




  • Wait for 10 minutes, then cycle power. Check if protection still exists. If yes, return to factory.

tH2o


Capacitor hardware error

Cause:




  • Hardware failure (NTC broken or wiring failure).



Remedy:




  • Wait for 10 minutes, then cycle power. Check if protection still exists. If yes, return to factory.

oL


Over load

Cause:




  • The load is too large.

  • Accel./Decel. time or working cycle too short.

  • V/F voltage is too high.

  • The capacity of the drive is too small.

  • Overload during low-speed operation.

  • Torque compensation is too large.

  • Incorrect stall prevention setting.

  • Output phase loss.

  • Improper parameter settings for speed tracking function.



Remedy:




  • Reduce the load.

  • Increase setting for Pr.01-12~01-19 (accel/decel time).

  • Adjust V/F curve settings (Pr.01-01~01-08); check mid-point voltage.

  • Replace the drive with a larger capacity model.

  • Reduce load at low speed, increase drive capacity, or decrease carrier frequency (Pr.00-17).

  • Adjust torque compensation (Pr.07-26) until current reduces.

  • Set stall prevention to proper value.

  • Check three-phase motor status and cables.

  • Correct speed tracking parameters and adjust maximum current (Pr.07-09).

EoL1


Electronic thermal relay 1 protection

Cause:




  • The load is too large.

  • Accel./Decel. time or working cycle too short.

  • V/F voltage is too high.

  • Overload during low-speed operation (General motor vs VFD motor).

  • Incorrect setting for motor type (Pr.06-13).

  • Incorrect value of electronic thermal relay or max motor frequency.

  • One drive connected to multiple motors.

  • Incorrect stall prevention setting.

  • Torque compensation is too large.

  • Motor fan error or unbalanced three-phase impedance.



Remedy:




  • Reduce the load.

  • Increase Accel/Decel time.

  • Adjust V/F curve settings.

  • Decrease low-speed operation time or replace with dedicated VFD motor/increase capacity.

  • Set Pr.06-13 correctly (0 for inverter motor, 1 for standard motor).

  • Reset to correct motor rated current and frequency.

  • Set Pr.06-13 = 2 (disable) and install external thermal relays on each motor.

  • Set stall prevention to proper value.

  • Adjust torque compensation gain.

  • Check/replace fan or replace motor.
EoL2

Electronic thermal relay 2 protection
Cause: The load is too large.


Remedy:
Reduce the load.


Cause: Accel./Decel. time or the working cycle are too short.


Remedy:
Increase the setting values for Pr.01-12–01-19 (accel./decel. time).


Cause: V/F voltage is too high.


Remedy:
Adjust the settings for Pr.01-01–01-08 (V/F curve), especially the setting value for the mid-point voltage. Refer to Pr.01-43.


Cause: Overload during low-speed operation.


Remedy:


  • Decrease low-speed operation time.

  • Replace the drive with a dedicated to VFD model.

  • Increase the motor capacity.




Cause: Incorrect setting for VFD dedicated motors (Pr.06-27).


Remedy:
Set Pr.06-27 = 1 (Electronic thermal relay selection motor 2 = standard motor with fan on shaft).


Cause: Incorrect value of electronic thermal relay.


Remedy:
Reset to the correct motor rated current.


Cause: The maximum motor frequency is set too low.


Remedy:
Reset to the correct motor rated frequency.


Cause: One drive to multiple motors.


Remedy:
Set Pr.06-27 = 2 (Disable) and install thermal relay on each motor.


Cause: Torque compensation is too large.


Remedy:
Adjust torque compensation (Pr.07-26) until current reduces and motor does not stall.


Cause: Motor fan error.


Remedy:
Check the status of the fan, or replace the fan.


Cause: Unbalanced three-phase impedance of the motor.


Remedy:
Replace the motor.
oH3 (PTC)

Motor overheating (PTC)
Cause: Motor shaft lock.


Remedy:
Remove the shaft lock.


Cause: The load is too large.


Remedy:
Reduce the load or increase motor capacity.


Cause: Ambient temperature is too high.


Remedy:
Change installation place, add cooling fan or air conditioner.


Cause: Motor cooling system error or Fan error.


Remedy:
Check cooling system or replace fan.


Cause: Operate at low-speed too long.


Remedy:
Decrease low-speed time, replace with VFD dedicated motor, or increase capacity.


Cause: V/F voltage is too high.


Remedy:
Adjust settings for Pr.01-01–01-08.


Cause: Motor rated current mismatch.


Remedy:
Reset to the correct motor rated current.


Cause: Check if the PTC is properly set and wired.


Remedy:
Check the connection between PTC thermistor and the heat protection.


Cause: Unbalanced three-phase impedance or High Harmonics.


Remedy:
Replace motor or use remedies to reduce harmonics.
oH3 (PT100)

Motor overheating (PT100)
Cause: PT100 input value > Pr.06-57 setting.


Remedy:


  • Check for motor shaft lock or overload.

  • Check ambient temperature.

  • Check cooling system and fan.

  • Check connection of PT100 thermistor.
ot1

Over torque 1
Cause: Incorrect parameter setting.


Remedy:
Reset Pr.06-07 and Pr.06-08.


Cause: Mechanical failure (e.g. over-torque, mechanical lock).


Remedy:
Remove the causes of malfunction.


Cause: The load is too large or Motor capacity too small.


Remedy:
Reduce load or replace with larger capacity motor.


Cause: Accel./Decel. time too short.


Remedy:
Increase setting values for Pr.01-12–Pr.01-19.


Cause: V/F voltage is too high.


Remedy:
Adjust settings for Pr.01-01–01-08.


Cause: Torque compensation is too large.


Remedy:
Adjust torque compensation (Pr.07-26).


Cause: Improper parameter settings for speed tracking function.


Remedy:
Correct settings for speed tracking (Start function, adjust Pr.07-09).
ot2

Over torque 2
Cause: Output current exceeds Pr.06-10 for time Pr.06-11.


Remedy:


  • Reset Pr.06-07 and Pr.06-08.

  • Check for mechanical failure/lock.

  • Reduce load or increase motor capacity.

  • Increase Accel./Decel. time.

  • Adjust V/F curve settings.

  • Adjust torque compensation.
uC

Under current
Cause: Motor cable disconnection.


Remedy:
Troubleshoot the connection between the motor and the load.


Cause: Improper setting of low-current protection.


Remedy:
Reset Pr.06-71, Pr.06-72 and Pr.06-73 to proper settings.


Cause: The load is too low.


Remedy:
Check the load status and if motor capacity matches the load.
LiT

Limit Error
Cause: The limit ON/OFF switch is on incorrect position.


Remedy:
Install the limit ON/OFF switch to correct position.


Cause: Deceleration time is too long (motor cannot stop at limited position).


Remedy:
Reduce deceleration time. Adjust brake level (Pr.07-01).


Cause: The motor cannot stop due to over-voltage stall prevention.


Remedy:
Reset the over-voltage stall prevention.


Cause: Malfunction caused by interference.


Remedy:
Verify wiring of the control circuit and wiring/grounding of the main circuit.
cF1

EEPROM write error
Cause: Internal EEPROM cannot be programmed.


Remedy:
Press “RESET” key or reset parameters to default. Cycle power. If error persists, return to factory for repair.
cF2

EEPROM read error
Cause: Internal EEPROM cannot be read.


Remedy:
Press “RESET” key or reset parameters to default. Cycle power. If error persists, return to factory for repair.
cd1

U-phase error
Cause: Hardware failure (U-phase current detection error).


Remedy:
Cycle the power. If cd1 still exists, return to the factory for repair.
cd2

V-phase error
Cause: Hardware failure (V-phase current detection error).


Remedy:
Cycle the power. If cd2 still exists, return to the factory for repair.
cd3

W-phase error
Cause: Hardware failure (W-phase current detection error).


Remedy:
Cycle the power. If cd3 still exists, return to the factory for repair.
Hd0

cc hardware failure
Cause: Hardware failure (current clamp protection error).


Remedy:
Cycle the power. If Hd0 still exists, return to the factory for repair.
Hd1

oc hardware error
Cause: Hardware failure (oc protection error).


Remedy:
Cycle the power. If Hd1 still exists, return to the factory for repair.
Hd2

ov hardware error
Cause: Hardware failure (ov protection error).


Remedy:
Cycle the power. If Hd2 still exists, return to the factory for repair.
Hd3

occ hardware error
Cause: Hardware failure (occ IGBT short-circuit detection).


Remedy:
Cycle the power. If Hd3 still exists, return to the factory for repair.
AUE

Auto-tuning error
Cause: Press “STOP” key during auto-tuning.


Remedy:
Re-execute auto-tuning.


Cause: Incorrect motor capacity or parameters.


Remedy:
Check motor capacity. Set correct parameters (Pr.01-01–Pr.01-02). Set Pr.01-00 larger than motor rated frequency.


Cause: Incorrect motor wiring.


Remedy:
Check the wiring.


Cause: Motor shaft lock.


Remedy:
Remove the cause of motor shaft lock.


Cause: Electromagnetic contactor is ON at output side.


Remedy:
Make sure the electromagnetic valve is OFF.


Cause: The load is too large.


Remedy:
Reduce the load or replace with larger capacity motor.
AFE

PID loss ACI
Cause: PID feedback cable is loose or cut off.


Remedy:
Tighten the terminal or replace the cable.


Cause: Feedback device failure.


Remedy:
Replace the device with a new one.


Cause: Hardware failure.


Remedy:
Check all wiring. If AFE fault still exists, return to factory for repair.
42 (PGF1)

PG feedback error
Cause:



  • Incorrect parameter setting of encoder.

  • Check wiring of the encoder.

  • PG card or PG encoder failure.

  • Malfunction caused by interference.




Remedy:



  • Reset encoder parameter (Pr.10-02).

  • Re-wire the encoder.

  • Replace PG card or encoder with a new one.

  • Verify wiring of the control circuit and wiring/grounding of the main circuit to prevent interference.
43 (PGF2)

PG feedback loss
Cause:



  • Incorrect setting of encoder parameter.

  • Incorrect selection of the control mode.




Remedy:



  • Reset encoder parameters (Pr.10-00 and Pr.10-02).

  • Choose the correct control mode.
44 (PGF3)

PG feedback stall
Cause:



  • Incorrect setting of encoder parameter.

  • Pr. 01-00 is set too small.

  • Incorrect setting for ASR parameters and accel./decel. time.

  • Incorrect setting for PG feedback stall.




Remedy:



  • Reset encoder parameter (Pr.10-01).

  • Set proper value for Pr.01-00.

  • Reset ASR parameters. Set correct accel./decel. time.

  • Reset proper values for Pr.10-10 and Pr.10-11.
45 (PGF4)

PG slip error
Cause:



  • Incorrect settings for PG feedback parameters.

  • Incorrect settings for ASR parameters and accel./decel. time.

  • Incorrect settings of encoder parameters.

  • Accel./Decel. time is too short.

  • Incorrect settings of torque limit parameters (Pr.06-12, Pr.11-17–20).

  • Motor shaft lock.

  • Mechanical brake is not released.




Remedy:



  • Reset correct values for Pr.10-13 and Pr.10-14.

  • Reset ASR parameters. Set correct accel./decel time.

  • Reset encoder parameters (Pr.10-01).

  • Reset proper accel./decel. time.

  • Reset proper setting values for Pr.06-12 and Pr.11-17–Pr. 17-20.

  • Remove causes of motor shaft lock.

  • Check the action sequence of the system.
48 (ACE)

ACI loss (Analog Input Loss)
Cause:



  • ACI cable is loose or cut off.

  • External device failure.

  • Hardware failure.




Remedy:



  • Tighten the terminal. Replace the cable with a new one.

  • Replace the device with a new one.

  • Check all the wiring. If ACE still exists, return to the factory for repair.
49 (EF)

External fault
Cause:



  • External fault (MIx = EF triggered).




Remedy:



  • Press RESET key after the fault is cleared.
50 (EF1)

Emergency stop
Cause:



  • When MIx = EF1 activates.




Remedy:



  • Verify if the system is back to normal condition, and then press “RESET” key to go back to the default.
51 (bb)

External base block
Cause:



  • When MIx = bb activates.




Remedy:



  • Verify if the system is back to normal condition, and then press “RESET” key to go back to the default.
52 (Pcod)

Password is locked
Cause:



  • Incorrect password input through Pr.00-07.




Remedy:



  • Input the correct password after rebooting the motor drive.

  • If you forget the password:

    • Step 1: Input 9999 and press ENTER.

    • Step 2: Repeat step 1. Input 9999 and press ENTER. (Finish within 10 seconds).



  • Parameter settings return to default when the “Input 9999” process is finished.
54 (CE1)

Illegal command
Cause:



  • Incorrect communication command from the upper unit.

  • Malfunction caused by interference.

  • Different communication setting from the upper unit.

  • Disconnection or bad connection of the cable.




Remedy:



  • Check if the communication command is correct.

  • Verify wiring/grounding. Use twisted pair/shielded cable or wire in 90 degrees.

  • Check if the setting for Pr.09-02 is the same as the setting for the upper unit.

  • Check the cable and replace it if necessary.
55 (CE2)

Illegal data address
Cause:



  • Incorrect communication command from the upper unit.

  • Malfunction caused by interference.

  • Different communication setting from the upper unit.

  • Disconnection or bad connection of the cable.




Remedy:



  • Check if the communication command is correct.

  • Verify wiring/grounding.

  • Check if the setting for Pr.09-02 is the same as the setting for the upper unit.

  • Check the cable and replace it if necessary.
56 (CE3)

Illegal data value
Cause:



  • Incorrect communication command from the upper unit.

  • Malfunction caused by interference.

  • Different communication setting from the upper unit.

  • Disconnection or bad connection of the cable.




Remedy:



  • Check if the communication command is correct.

  • Verify wiring/grounding.

  • Check if the setting for Pr.09-02 is the same as the setting for the upper unit.

  • Check the cable and replace it if necessary.
57 (CE4)

Data is written to read-only address
Cause:



  • Incorrect communication command from the upper unit.

  • Malfunction caused by interference.

  • Different communication setting from the upper unit.

  • Disconnection or bad connection of the cable.




Remedy:



  • Check if the communication command is correct.

  • Verify wiring/grounding.

  • Check if the setting for Pr.09-02 is the same as the setting for the upper unit.

  • Check the cable and replace it if necessary.
58 (CE10)

Modbus transmission time-out
Cause:



  • The upper unit does not transmit the communication command within Pr.09-03 setting time.

  • Malfunction caused by interference.

  • Different communication setting from the upper unit.

  • Disconnection or bad connection of the cable.




Remedy:



  • Check if the upper unit transmits the communication command within the setting time for Pr.09-03.

  • Verify wiring/grounding.

  • Check if the setting for Pr.09-02 is the same as the setting for the upper unit.

  • Check the cable and replace it if necessary.
60 (bF)

Brake transistor error
Cause:



  • Hardware error.

  • Malfunction caused by interference.

  • Using the incorrect brake resistor.

  • Incorrect wiring of the brake resistor.




Remedy:



  • Press “RESET”. If bF still exists, return to factory.

  • Power off and check if B2 to DC- is short-circuited. If yes, return to factory.

  • Verify wiring/grounding to prevent interference.

  • Check if the resistance value matches the drive.

  • Verify the wiring (Refer to optional accessories instruction).
61 (ydc)

Y-connection / Δ-connection switch error
Cause:



  • The electromagnetic valve operates incorrectly during Y-Δ switch.

  • Incorrect parameter setting.

  • The wiring of Y-Δ switch function is incorrect.




Remedy:



  • Check if the electromagnetic valve works normally. If not, replace it.

  • Check if related parameters are all set up and set correctly.

  • Check the wiring.
62 (dEb)

Deceleration energy backup error
Cause:



  • Unstable power source or the power is off.

  • There is any other large load operates in the power system.




Remedy:



  • Check the power system.

  • Replace power system with a larger capacity.

  • Use a different power system from the large load system.
63 (oSL)

Over slip error
Cause:



  • Any of the motor parameters in parameter group 5 may be incorrect.

  • Overload.

  • Any of the setting value of Pr.07-29, 07-30, and 10-29 is improper.




Remedy:



  • Check the motor parameters.

  • Decrease the load.

  • Check the setting of oSL protection function related parameters.
64 (ryF)

Electric valve switch error
Cause:



  • The input power is abnormal.

  • Malfunction caused by interference.

  • Hardware failure.




Remedy:



  • Check if the power is shut down during the drive operation. Check if three-phase input is normal.

  • Verify the wiring/grounding of the main circuit.

  • Cycle the power after checking the power. If ryF error still exists, return to the factory for repair.
65 (PGF5)

PG hardware error
Cause:



  • Wiring Error or No U,V, W Input Signal.

  • Encoder error.

  • Incorrect setting of encoder parameter.

  • Verify if the motor selecting switch on the PG card is on the right side.

  • Wrong PG card.




Remedy:



  • Re-wire correctly.

  • Verify if it is a UVW signal encoder.

  • Reset correct values for Pr.10-00.

  • Verify if using a UVW signal encoder or a Delta wire-saving encoder.

  • Verify if using a wrong PG card then choose a right one.
SdRv (ID 68)
Reverse direction of the speed feedback
Cause:

  • The setting of Pr.10-25 FOC bandwidth of speed observer is improper.

  • The setting of motor parameter is incorrect.

  • The motor cable is abnormal or broken.

  • A reverse force is exerted, or the motor runs in a reverse direction at start.

  • Malfunction caused by interference.




Remedy:

  • Decrease the setting of Pr.10-25.

  • Reset the motor parameter and execute parameter tuning.

  • Check if the cable is well functioned or replace the cable.

  • Start speed tracking function (Pr.07-12).

  • Verify the wiring of the control circuit and wiring/grounding of the main circuit to prevent interference.
SdOr (ID 69)
Over speed rotation feedback
Cause:

  • The setting of Pr.10-25 FOC bandwidth of speed observer is improper.

  • The setting of ASR bandwidth of speed controller is improper.

  • The setting of motor parameter is incorrect.

  • Malfunction caused by interference.




Remedy:

  • Decrease the setting of Pr.10-25.

  • Increase the bandwidth of ASR speed controller.

  • Reset motor parameter and execute parameter tuning.

  • Verify the wiring of the control circuit and wiring/grounding of the main circuit to prevent interference.
SdDe (ID 70)
Large deviation of speed feedback
Cause:

  • Improper parameter setting for abnormal rotating slip function.

  • Improper parameter setting for ASR and acceleration/deceleration.

  • The acceleration/deceleration time is too short.

  • Motor shaft lock.

  • The mechanical brake is not released.

  • Incorrect parameter setting for torque limit (Pr.06-12, Pr.11-17~20).

  • Malfunction caused by interference.




Remedy:

  • Reset proper setting for Pr.10-13 and Pr.10-14.

  • Reset ASR parameters. Set proper acceleration/deceleration time.

  • Reset proper acceleration/deceleration time.

  • Remove the cause of motor shaft lock.

  • Verify the system action timeline.

  • Adjust the setting to proper value.

  • Verify the wiring of the control circuit and wiring/grounding of the main circuit to prevent interference.
WDTT (ID 71)
Watchdog error
Cause: Hardware interference.



Remedy:

  • Verify the wiring of the control circuit and wiring/grounding of the main circuit to prevent interference.

  • If the WDTT fault still exists, return to the factory for repair.
STL1 (ID 72)
STO Loss 1 (STO1–SCM1 internal loop detection error)
Cause:

  • STO1 and SCM1 short circuit lines are not connected.

  • Hardware failure.

  • Bad connection of the IO card.

  • The IO card does not match the version of the control board.




Remedy:

  • Connect the short circuit line.

  • After you make sure all the wiring is correct, if STOL fault still exists after cycling the power, please return to the factory for repair.

  • Check if the PIN of IO card is broken. Check if the IO card connects to the control board correctly, and if the screws are tightened well.

  • Contact local agent or Delta.
S1 (ID 73)
Emergency stop for external safety
Cause:

  • The switch action of S1 and SCM (OPEN).

  • S1 and SCM short circuit lines are not connected.

  • Malfunction caused by interference.

  • Hardware failure.

  • Poor connection of the IO card.

  • The IO card does not match the version of the control board.




Remedy:

  • Reset the switch and cycle the power.

  • Re-connect the short circuit lines.

  • Verify the wiring/grounding of the main circuit, control circuit and encoder to prevent interference.

  • If S1 fault still exists after cycling the power, please return to the factory for repair.

  • Check if the PIN of IO card is broken or loose. Tighten screws.

  • Contact local agent or Delta.
Brk (ID 75)
External brake error
Cause:

  • Mechanical brake error.

  • Incorrect parameter setting (If there is no brake-confirming signal).

  • Signal cable is loose or cut off.

  • The time of Pr.02-56 is set too short.

  • Malfunction caused by interference.




Remedy:

  • Verify if the mechanical brake can work correctly. Replace mechanical brake.

  • Set Pr.02-56 = 0.

  • Tighten the screws or replace the signal cable with a new one.

  • Increase the time setting of Pr.02-56.

  • Verify the wiring/grounding of the main circuit, control circuit and encoder to prevent interference.
STO (ID 76)
Safety Torque Off function active
Cause:

  • The switch action of STO1/SCM1 and STO2/SCM2 (OPEN).

  • Poor connection of the IO card.

  • The IO card does not match the version of the control board.




Remedy:

  • Reset the switch (ON) and cycle the power.

  • Check if the PIN of IO card is broken. Check connection and screws.

  • Contact local agent or Delta.
STL2 (ID 77)
STO Loss 2 (STO2–SCM2 internal loop detection error)
Cause:

  • STO2 and SCM2 short circuit lines are not connected.

  • Hardware failure.

  • Poor connection of the IO card.

  • The IO card does not match the version of the control board.




Remedy:

  • Connect the short circuit lines.

  • If STL2 fault still exists after cycling the power, return to the factory for repair.

  • Check PINs and screws of IO card.

  • Contact local agent or Delta.
STL3 (ID 78)
STO Loss 3 (STO1–SCM1 and STO2–SCM2 internal loop error)
Cause:

  • STO1 and SCM1, or STO2 and SCM2 short circuit lines are not connected.

  • Hardware failure.

  • Poor connection of the IO card.

  • The IO card does not match the version of the control board.




Remedy:

  • Re-connect the short circuit lines.

  • If STL3 fault still exists after cycling the power, return to the factory for repair.

  • Check PINs and screws of IO card.

  • Contact local agent or Delta.
OPHL (ID 82)
Output phase loss U phase
Cause:

  • The three-phase impedance of motor is unbalanced.

  • The motor is wired incorrectly.

  • Using a single-phase motor.

  • The current sensor is damaged.

  • The drive capacity is much larger than the motor capacity.




Remedy:

  • Replace the motor.

  • Check the cable condition. Replace the cable.

  • Choose a three-phase motor.

  • Check the flat cable of the control board. If fault exists, return to factory. Verify three-phase current balance.

  • Make sure the capacity of the drive and motor match to each other.
OPHL (ID 83)
Output phase loss V phase
Cause:

  • Unbalanced three-phase impedance of the motor.

  • Check if the wiring is incorrect.

  • Check if the motor is a single-phase motor.

  • Check if the current sensor is broken.

  • Check if the drive capacity is larger than the motor capacity.




Remedy:

  • Replace the motor.

  • Check the cable and replace it if necessary.

  • Choose a three-phase motor.

  • Check control board cable. Return to factory if fault persists.

  • Choose the drive that matches the motor capacity.
OPHL (ID 84)
Output phase loss W phase
Cause:

  • Unbalanced three-phase impedance of the motor.

  • Check if the wiring is incorrect.

  • Check if the motor is a single-phase motor.

  • Check if the current sensor is broken.

  • Check if the drive capacity is larger than the motor capacity.




Remedy:

  • Replace the motor.

  • Check the cable and replace it if necessary.

  • Choose a three-phase motor.

  • Check control board cable. Return to factory if fault persists.

  • Choose the drive that matches the motor capacity.
AboF (ID 85)
PG ABZ loss protection
Cause:

  • PG card signal cable is not wired or is broken.

  • PG card screws are loose.

  • Malfunction caused by interference.

  • Hardware failure (PG card VP power issue or Encoder broken).

  • Cable between encoder and PG card is too long (VP voltage drop).




Remedy:

  • Re-wire the PG card.

  • Tighten all PG card screws.

  • Verify wiring/grounding to prevent interference.

  • Cycle power. If fault persists, return to factory.

  • Reduce cable length or use external power source for encoder.
UvoF (ID 86)
PG UVW loss protection
Cause:

  • PG card signal cable is not wired or is broken.

  • PG card screws are loose.

  • Malfunction caused by interference.

  • Hardware failure.

  • Cable between encoder and PG card is too long.




Remedy:

  • Re-wire the PG card.

  • Tighten all PG card screws.

  • Verify wiring/grounding to prevent interference.

  • Cycle power. If fault persists, return to factory.

  • Reduce cable length or supply power from another source.
oL3

Overload protection at low frequency
(Low frequency and high current protection)
Cause: The drive operates at a frequency below 15 Hz, and output current is too large.



Remedy:

  • Enhance the heat dissipation capacity for the cabinet.

  • Lower the carrier frequency (Pr.00-17).

  • Decrease the voltage settings that correspond to frequency below 15 Hz in the V/F curve.

  • Change Pr.00-11 to general control mode.

  • Replace the drive with a larger power model.
RoPd

Rotor position detection error
(Rotor position detection error protection)
Cause:

  • Motor cable abnormal or broken.

  • Motor coil error.

  • Hardware failure.

  • Drive’s current feedback line error.




Remedy:

  • Check or replace the cable.

  • Replace the motor.

  • IGBT broken. Return to the factory for repair.

  • Cycle the power. If RoPd still occurs during operation, return to the factory for repair.
FStp

Force to stop
(Keypad forces PLC to Stop)
Cause:

  • Pr.00-32 = 1: keypad STOP button is valid.

  • Press STOP button during PLC operation.




Remedy:

  • Check if it is necessary to set Pr.00-32 = 0, so the keypad STOP button is invalid.

  • Verify the timing of STOP function.
TRAP

CPU error 0
(CPU crash)
Cause:

  • Hardware interference.

  • Hardware failure.

  • CPU is in an infinite loop.




Remedy:

  • Verify the wiring of control circuit, and the wiring/grounding of the main circuit to prevent interference.

  • If TRAP fault still exists, return to the factory for repair.

  • Cycle the power. If the TRAP fault still exists, return to the factory for repair.
CGdE

CANopen guarding error
Cause:

  • The guarding time is too short, or less detection times.

  • Malfunction caused by interference.

  • Communication cable is broken or bad connected.




Remedy:

  • Increase the guarding time (Index 100C) and detection times.

  • Verify the wiring and grounding of the communication circuit. (Recommended to separate from main circuit or wire in 90 degrees).

  • Make sure the communication circuit is wired in series.

  • Use CANopen cable or add terminating resistance.

  • Check or replace the communication cable.
CHbE

CANopen heartbeat error
Cause:

  • The heartbeat time is too short.

  • Malfunction caused by interference.

  • Communication cable is broken or bad connected.




Remedy:

  • Increase heartbeat time (Index 100C).

  • Verify the wiring and grounding of the communication circuit.

  • Make sure the communication circuit is wired in series.

  • Use CANopen cable or add terminating resistance.

  • Check or replace the communication cable.
CbFE

CANopen bus off error
Cause:

  • CANopen card not installed.

  • Check if the CANopen speed is correct.

  • Malfunction caused by interference.

  • Communication cable is broken or bad connected.




Remedy:

  • Make sure the CANopen card is installed.

  • Reset CANopen speed (Pr.09-37).

  • Verify wiring/grounding of communication circuit.

  • Use CANopen cable or add terminating resistance.

  • Check or replace the communication cable.
CIdE

CANopen index error
Cause: Incorrect setting of CANopen index.



Remedy: Reset CANopen Index (Pr.00-02 = 7).
CAdE

CANopen station address error
(only supports 1–127)
Cause: Incorrect setting of CANopen station address.



Remedy:

  • Disable CANopen (Pr.09-36 = 0).

  • Reset CANopen (Pr.00-02 = 7).

  • Reset CANopen station address (Pr.09-36).
CFrE

CANopen memory error
Cause: CANopen internal memory error (Data change during firmware update).



Remedy:

  • Disable CANopen (Pr.09-36 = 0).

  • Reset CANopen (Pr.00-02 = 7).

  • Reset CANopen station address (Pr.09-36).
ictE

InrCOM time-out error
(Internal communication time-out)
Cause:

  • Malfunction caused by interference.

  • The communication condition is different with the upper unit.

  • Communication cable is broken or bad connected.




Remedy:

  • Verify wiring and grounding of communication circuit (separate from main circuit).

  • Verify the setting of Pr.09-02 is the same as the setting of upper unit.

  • Check or replace the communication cable.
SfLK

PMLess shaft lock
(Drive has RUN command but PM motor does not turn)
Cause:

  • Improper setting of the speed observer bandwidth.

  • Motor shaft lock.

  • Motor error (e.g. demagnetization).




Remedy:

  • Increase the setting value.

  • Remove causes of the motor shaft lock.

  • Replace the motor with a new one.
AUE1

Auto-tune error 1
(No feedback current error)
Cause:

  • Motor is not wired.

  • The electromagnetic contactor is used as an open state on the output side (U/V/W).




Remedy:

  • Wire the motor correctly.

  • Verify that the electromagnetic valve is closed.
AUE2

Auto-tune error 2
(Motor phase loss error)
Cause:

  • Incorrect motor wiring or wire error.

  • Motor error.

  • The electromagnetic contactor is open on the output side (U/V/W).




Remedy:

  • Wire the motor correctly.

  • Check if the motor works normally.

  • Verify that the three-phases of the electromagnetic valve are all closed.

  • Check if the wires are broken.
AUE3

Auto-tune error 3
(No load current I0 measurement error)
Cause:

  • Incorrect settings for the motor parameter (rated current).

  • Motor error.




Remedy:

  • Check the settings for Pr.05-01 / Pr.05-13 / Pr.05-34.

  • Check if the motor works normally.
AUE4

Auto-tune error 4
(Leakage inductance Lsigma measurement error)
Cause:

  • Motor error.

  • Incorrect setting of motor parameters (base frequency).




Remedy:

  • Check if the motor works normally.

  • Check the setting of Pr.01-01.
CBM

C/B mismatch
(Control board matching error)
Cause: Incorrect control board.



Remedy: Replace with the correct control board. If the CBM still exists, contact Delta for further confirmation.