Inovance MD810 Drive

Inovance MD810 Drive Fault Codes:

Fault Code and Meaning	Cause and Remedy
E12.01 Input voltage abnormal	Cause: R phase loss occurs on input voltage. Remedy: Check the three-phase power. Check whether the input power cable is broken. Check that the input terminal is correctly connected. Check the hardware voltage detection circuit.
E12.02 Input voltage abnormal	Cause: S phase loss occurs on input voltage. Remedy: Check the three-phase power. Check whether the input power cable is broken. Check that the input terminal is correctly connected. Check the hardware voltage detection circuit.
E12.03 Input voltage abnormal	Cause: T phase loss occurs on input voltage. Remedy: Check the three-phase power. Check whether the input power cable is broken. Check that the input terminal is correctly connected. Check the hardware voltage detection circuit.
E12.04 Input voltage abnormal	Cause: The input three-phase voltage is too high. Remedy: Adjust three-phase voltage to normal range.
E12.05 Input voltage abnormal	Cause: Three-phase input voltage unbalance occurs. Remedy: Check the three-phase power. Check the hardware voltage detection circuit.
E12.07 Input voltage abnormal	Cause: Three-phase input voltage low. Remedy: Check the three-phase power. Check the hardware voltage detection circuit.
E14.00 SCR overheat	Cause: The ambient temperature is too high. The ventilation is clogged. The fan is damaged. The thermally sensitive resistor of SCR is damaged. The SCR is damaged. Remedy: Lower the ambient temperature. Clean the ventilation. Replace the cooling fan. Contact the agent or Inovance.
E16.01 Communication fault	Cause: Modbus communication times out. Remedy: Check that the RS-485 communication cable is correctly connected. Check that the setting of Fd-04 (Modbus communication timeout time) and PLC communication cycle are proper.
E16.11 Communication fault	Cause: CANopen communication times out. Remedy: Check that the CAN communication cable is correctly connected. Check the setting of Fd-15 [Maximum value of node reception error count (real-time)] to Fd-17 (Bus disconnection times per unit of time) and confirm interference.
E16.12 Communication fault	Cause: The PDO mapping configured for CANopen is not consistent with the actual mapping. Remedy: Check the PDO mapping of parameters in group AF.
E16.13 Communication fault	Cause: Data exchange times out when the drive units receive data from the power supply unit. Remedy: Check that the power supply unit is running. Check whether the network cables of the power supply unit and drive units are connected. Check that the terminal build-out resistor is correctly connected. Check Fd-12 (CAN baud rate) and confirm that the CAN baud rate setting is consistent.
E16.14 Communication fault	Cause: Data exchange is abnormal when the drive units receive data from the power supply unit. Remedy: Rectify the fault of the power supply unit.
E16.21 Communication fault	Cause: The CANlink heartbeat times out. Remedy: Check that the CAN communication cable is correctly connected. Check the setting of Fd-15 [Maximum value of node reception error count (real-time)] to Fd-17 (Bus disconnection times per unit of time) and confirm interference.
E16.22 Communication fault	Cause: CANlink station numbers conflict. Remedy: Change the value of Fd-13 (CAN station number) to make CANlink station numbers different.
E16.31 Communication fault	Cause: PROFIBUS-DP communication times out (specific to PROFIBUS-DP-to-CANopen gateway mode). Remedy: Check that the PROFIBUS-DP communication cable is correctly connected.
E16.34 Communication fault	Cause: A CAN slave is offline during PROFIBUS-DP-to-CANopen gateway configuration. Remedy: Check whether the value of the “The number of devices” parameter of PLC is consistent with the actual number of stations. Check that the slave station number is correctly set.
E16.35 Communication fault	Cause: Parameters of stations except the power supply unit are incorrectly set on the PROFIBUS-DP-to-CANopen gateway. Remedy: Check that the value of the “NO. n” parameter of PLC is consistent with the setting of AF-66 (Number of valid RPDOs) and AF-67 (Number of valid TPDOs) according to the PLC diagnosis report.
E16.41 Communication fault	Cause: PROFIBUS-DP communication times out. Remedy: Check that the PROFIBUS-DP communication cable is correctly connected.
E16.42 Communication fault	Cause: Parameters of the power supply unit are incorrectly set on the PROFIBUS-DP-to-CANopen gateway. Remedy: Check that the value of the “NO. 1” parameter of PLC is consistent with the setting of AF-66 (Number of valid RPDOs) and AF-67 (Number of valid TPDOs) of the gateway unit.
E16.71 Communication fault	Cause: PROFINET communication times out. Remedy: Check the Ethernet wiring. Increase the PROFINET timeout interval.
E16.72 Communication fault	Cause: The CANopen slave communication times out. Remedy: Check the wiring. Check whether the termination resistor is configured correctly.
E16.74 Communication fault	Cause: The configured CANopen slave is missing. Remedy: Modify the AC drive site number or modify the PLC configuration to ensure consistent configuration.
E16.75 Communication fault	Cause: CANopen mapping data does not match. Remedy: Check the process data mapping of parameter configuration. Ensure that the data length of the PLC configuration is consistent with the process data length of the corresponding slave.
E16.76 Communication fault	Cause: The process data of the power supply unit does not match the configuration. Remedy: Check the process data mapping of parameter configuration. Ensure that the data length of the PLC configuration is consistent with the process data length of the power supply unit.
E16.77 Communication fault	Cause: An internal serial communication fault occurs. Remedy: Check that Fd-10 (Communication protocol selection) is set to 5. Re-power on the power supply unit. Contact the agent or Inovance.
E16.78 Communication fault	Cause: An internal SPI communication fault occurs. Remedy: Check that Fd-10 (Communication protocol selection) is set to 5. Re-power on the power supply unit. Contact the agent or Inovance.
E61.01 Braking unit fault	Cause: The braking unit is directly connected. Remedy: Check whether the braking resistor is short circuited. Check whether the brake transistor is directly connected.
E61.02 Braking unit fault	Cause: Overcurrent occurs on the braking unit. Remedy: Check whether the resistance of the braking resistor is too low. Check for interference. Check whether an error occurs during hardware circuit detection.
E61.03 Braking unit fault	Cause: Overload occurs on the braking unit. Remedy: Check whether the resistance and power of the braking resistor are too small.
E61.04 Braking unit fault	Cause: An overheat warning is detected on the braking unit. Remedy: Lower the ambient temperature. Check whether the cooling fan runs properly. Clean the ventilation. Check whether the temperature sensor is damaged.
E61.05 Braking unit fault	Cause: The braking unit overheats. Remedy: Clean the ventilation. Check whether the temperature sensor is damaged.
E01.01 Abnormal current sampling	Cause: The current sampling circuit is faulty. Remedy: Check whether mains power supply is on. Contact the agent or Inovance.
E01.02 Contactor fault	Cause: The driver board or power supply is faulty. The contactor is faulty. The surge protection device is faulty. Remedy: Contact the agent or Inovance.
E01.05 Product model setup error	Cause: Product model and hardware do not match. Remedy: Check whether the equipment model is wrong.
E01.06 STO product model setup error	Cause: Product hardware does not support STO. Remedy: Check whether there is no STO product model, and contact the manufacturer if so.
E02.00 Overcurrent during acceleration	Cause: A grounding fault or short circuit exists in the output circuit. The control mode is SVC or FVC but motor auto-tuning is not performed. The acceleration time is too short. The overcurrent stall prevention parameters are set improperly. Customized torque boost or V/F curve is not appropriate. The spinning motor is started. The drive suffers external interference. Remedy: Check whether short-circuit occurs on the motor, motor cable, or contactor. Set motor parameters according to motor nameplate and perform motor auto-tuning. Increase the acceleration time. Ensure that current limit is enabled (F3-19 = 1). The setting of F3-18 (Current limit level) is too large. Adjust it between 120% and 160%. The setting of F3-20 (Current limit gain) is too small. Adjust it between 20 and 40. Adjust the customized torque boost or V/F curve. Enable the flying start function or start the motor after it stops. View historical fault records. If the current value is far from the overcurrent level, find the interference source. If an external interference does not exist, the driver board or hall device may be faulty.
E03.00 Overcurrent during deceleration	Cause: A grounding fault or short circuit exists in the output circuit. The control mode is SVC or FVC but motor auto-tuning is not performed. The deceleration time is too short. The overcurrent stall prevention parameters are set improperly. The braking unit and braking resistor are not installed. The drive suffers external interference. Remedy: Check whether short-circuit occurs on the motor, motor cable, or contactor. Set the motor parameters according to the motor nameplate and perform motor auto-tuning. Increase the deceleration time. Ensure current limit is enabled (F3-19=1). Adjust F3-18 (120%-150%) and F3-20 (20-40). Install the braking unit and braking resistor. View historical fault records. Find interference source or check driver board/hall device.
E04.00 Overcurrent at constant speed	Cause: A grounding fault or short circuit exists in the output circuit. The control mode is SVC or FVC but motor auto-tuning is not performed. The overcurrent stall prevention parameters are set improperly. The drive power class is small. The drive suffers external interference. Remedy: Check whether short-circuit occurs on the motor, motor cable, or contactor. Set motor parameters according to nameplate and perform auto-tuning. Ensure current limit is enabled (F3-19=1). Adjust F3-18 (120%-150%) and F3-20 (20-40). Replace with a drive of larger power class. View historical records. Check for interference or faulty driver board/hall device.
E05.00 Overvoltage during acceleration	Cause: Input voltage is too high. An external force drives the motor during acceleration. The overvoltage stall prevention parameters are set improperly. The braking unit and braking resistor are not installed. The acceleration time is too short. Remedy: Adjust input voltage to normal range. Cancel external force or install braking resistor. Adjust F3-26 (5Hz-15Hz). Ensure voltage limit enabled (F3-23=1). Adjust F3-22 (700V-770V) and F3-24 (30-50). Install the braking unit and braking resistor. Increase the acceleration time.
E06.00 Overvoltage during deceleration	Cause: The overvoltage stall prevention parameters are set improperly. An external force drives the motor during acceleration. The deceleration time is too short. The braking unit and braking resistor are not installed. Remedy: Ensure voltage limit enabled (F3-23=1). Adjust F3-22 (700V-770V) and F3-24 (30-50). Cancel external force or install braking resistor. Adjust F3-26 (5Hz-15Hz). Increase the deceleration time. Install the braking unit and braking resistor.
E07.00 Overvoltage at constant speed	Cause: The overvoltage stall prevention parameters are set improperly. An external force drives the motor during acceleration. Remedy: Ensure voltage limit enabled (F3-23=1). Adjust F3-22 (700V-770V) and F3-24 (30-50). Cancel external force or install braking resistor. Adjust F3-26 (5Hz-15Hz).
E09.00 Undervoltage	Cause: Instantaneous power failure occurs. The drive’s input voltage is not within the permissible range. The bus voltage is abnormal. The rectifier bridge, driver board, or control board are abnormal. Remedy: Enable the power dip ride through function (F9-59 ≠ 0). Adjust the voltage to the normal range. Contact the agent or Inovance. Contact the agent or Inovance.
E10.00 Drive overload	Cause: The load is too heavy or locked-rotor occurs on the motor. The drive power class is small. Control mode is SVC/FVC but auto-tuning not performed. V/F mode: Torque boost (F3-01) is too large. Output phase loss occurs on the AC drive. Remedy: Reduce the load or check motor and mechanical conditions. Replace a drive of larger power class. Set parameters according to nameplate and perform auto-tuning. Decrease F3-01 gradually or set to 0 (Automatic torque boost). Check the output wiring of the AC drive.
E10.01 Pulse-by-pulse current limit fault	Cause: The load is too heavy or locked-rotor occurs on the motor. The AC drive power class is small. Remedy: Reduce the load or check motor and mechanical conditions. Replace a drive of larger power class.
E11.00 Motor overload	Cause: F9-01 (Motor overload protection gain) is set improperly. The load is too heavy or locked-rotor occurs on the motor. Remedy: Set F9-01 correctly. Increase value to prolong overload time. Reduce the load or check motor and mechanical conditions.
E13.00 Output phase loss	Cause: The motor is faulty. The cable connecting the drive and the motor is abnormal. The drive’s three-phase outputs are unbalanced while running. The driver board or the IGBT is abnormal. Remedy: Check and ensure that the motor is without open circuit. Eliminate external faults. Check whether the motor three-phase winding is normal. Contact the agent or Inovance.
E14.00 IGBT overheat	Cause: The ambient temperature is too high. The ventilation is clogged. The fan is damaged. The thermistor of IGBT is damaged. The IGBT is damaged. Remedy: Lower the ambient temperature. Clean the ventilation. Replace the cooling fan. Contact the agent or Inovance.
E15.01 / E15.02 External fault	Cause: E15.01: An external fault signal is input using DI (NO). E15.02: An external fault signal is input using DI (NC). Remedy: Eliminate external faults. Confirm that the mechanical condition allows restart (F8-18, Startup protection) and reset the operation.
E16.01 Communication fault (Modbus)	Cause: Modbus communication times out. Remedy: Check whether the RS485 communication cable is correctly connected. Check whether Fd-04 (Timeout) and PLC communication cycle are properly set.
E16.11 Communication fault (CANopen)	Cause: CANopen communication times out. Remedy: Check whether CAN communication cable is correctly connected. Check parameters Fd-15 and Fd-17 for further action.
E16.12 Communication fault (CANopen PDO)	Cause: PDO mapping configured by CANopen does not match the actual communication mapping. Remedy: Check the PDO mapping in group AF.
E16.13 Communication fault (Power Supply Unit)	Cause: Timeout occurs on transmitting interactive data from the power supply unit to the drive unit. Remedy: Check whether the power supply unit is in operation. Check communication cable connection between power supply and drive. Check matching termination resistor. Check Fd-12 (CAN baud rate).
E16.14 Communication fault (Interactive Data)	Cause: The interactive data from the power supply unit to the drive unit is abnormal. Remedy: The power supply unit is faulty. Eliminate the faults.
E16.15 Communication fault (Synchronous)	Cause: Synchronous control communication times out. Remedy: Check group A8 parameters for correct master station number. Check whether the CAN2 cable is connected normally.
E16.21 Communication fault (CANlink Heartbeat)	Cause: CANlink heartbeat times out. Remedy: Check whether CAN communication cable is correctly connected. Check parameters Fd-15 and Fd-17.
E16.22 Communication fault (Station Conflict)	Cause: Conflicts are caused by the same CANlink station number. Remedy: Modify the CAN station numbers by using Fd-13 (CAN station No.).
E16.31 Communication fault (PROFIBUS-DP)	Cause: PROFIBUS-DP communication times out (PROFIBUS-DP to CANopen gateway mode). Remedy: Check whether PROFIBUS-DP communication cable is correctly connected.
E16.34 Communication fault	Cause: Slaves are offline (PROFIBUS-DP to CANopen gateway). Remedy: Check whether the number displayed in “The number of devices” of PLC matches the actual quantity of stations. Check whether the station numbers of slaves are correctly set.
E16.35 Communication fault	Cause: PROFIBUS-DP to CANopen gateway configuration parameters are set incorrectly. Remedy: Check whether the value of “NO. n” of PLC is consistent with that of AF-66/67 (Number of valid RPDOs/Number of valid TPDOs).
E16.41 Communication fault	Cause: PROFIBUS-DP communication times out. Remedy: Check whether the PROFIBUS-DP communication cable is correctly connected.
E16.42 Communication fault	Cause: PROFIBUS-DP to CANopen gateway configuration parameters are set incorrectly. Remedy: Check whether the value of “NO. 1” of PLC is consistent with that of AF-66/67 (Number of valid RPDOs/Number of valid TPDOs).
E16.51 Communication fault	Cause: The EtherCAT synchronization frame is lost. Remedy: Check whether the EtherCAT network cable is normal and whether the connection is loose.
E16.52 Communication fault	Cause: Wiring EEPROM with EtherCAT is faulty. Remedy: Contact Inovance or the agent for technical support.
E16.53 Communication fault	Cause: EtherCAT initialization failed. Remedy: Contact Inovance or the agent for technical support.
E16.54 Communication fault	Cause: EtherCAT state switchover failed (switching the EtherCAT state during running enabling). Remedy: Stop enabling and then switch the EtherCAT state.
E16.81 Communication fault	Cause: The SPI communication of the EtherCAT module is interfered with or interrupted, or the SPI communication stops when the EtherCAT module is running. Remedy: Contact Inovance or the agent for technical support.
E16.83 Communication fault	Cause: Bus synchronization is lost in the AC drive. Remedy: Contact Inovance or the agent for technical support.
E17.05 External DC soft charge unit error	Cause: The external DC soft charge unit is not connected or fails. Remedy: Check whether the external DC soft charge unit is faulty and properly connected. If the DC soft charge unit is not required, restore the tens position of F9-49 (Fault protection action selection 2) to the default value 5 (Cancelled).
E19.02 / E19.04 Motor auto-tuning fault	Cause: Synchronous motor magnetic pole angle auto-tuning is faulty. Remedy: The motor is not connected or output phase loss occurs.
E19.05 Motor auto-tuning fault	Cause: Synchronous motor initial magnetic pole angle auto-tuning is faulty. Remedy: Increase the setting of F2-29 (Synchronous motor initial angle detection current).
E19.06 / E19.07 / E19.08 Motor auto-tuning fault	Cause: Stator resistance auto-tuning is faulty. Remedy: The motor is not connected. Set F1-03 (Rated motor current) according to the motor nameplate.
E19.09 / E19.10 Motor auto-tuning fault	Cause: Asynchronous motor instantaneous leakage inductive reactance auto-tuning is faulty. Remedy: The motor is not connected or output phase loss occurs.
E19.11 Motor auto-tuning fault	Cause: Inertia auto-tuning is faulty. Remedy: Set F1-03 (Rated motor current) according to the motor nameplate. Increase the setting of F2-43 (Inertia auto-tuning and dynamic speed reference).
E19.12 – E19.19 Motor auto-tuning fault	Cause: Timeout occurs on auto-tuning. Remedy: The motor is not connected or output phase loss occurs. Confirm the load is disconnected from the motor.
E19.20 Motor auto-tuning fault	Cause: Timeout occurs on synchronous motor no-load zero position angle auto-tuning. Remedy: Check feedback signal Z.
E19.22 / E19.23 Motor auto-tuning fault	Cause: Synchronous motor magnetic pole angle auto-tuning is faulty. Remedy: Set F1-03 (Rated motor current) according to the motor nameplate. Decrease the setting of F2-29 (Synchronous motor initial angle detection current).
E19.24 Motor auto-tuning fault	Cause: Asynchronous motor instantaneous leakage inductive reactance auto-tuning is faulty. Remedy: The drive power class is small. Select the proper drive according to the power of motor.
E20.00 / E20.02 Encoder fault	Cause: Encoder wire-break occurs. Remedy: Repair the wire-break. Confirm the wiring of PG card is correct. Confirm the actual encoder pulses per revolution matches the setting value of F1-27 (Encoder pulses per revolution). Confirm the wiring of signal AB is correct.
E20.01 Encoder fault	Cause: The encoder is faulty. Remedy: Refer to remedy for E20.00 (Check wiring, settings, and connections).
E20.03 – E20.08 Encoder fault	Cause: The synchronous motor no-load auto-tuning encoder is faulty. Remedy: Refer to remedy for E20.00 (Check wiring, settings, and connections).
E20.09 Encoder fault	Cause: The synchronous motor with-load auto-tuning encoder is faulty. Remedy: Check feedback signal Z and the wiring of PG card.
E20.10 / E20.11 Encoder fault	Cause: The synchronous motor encoder is faulty (E20.10) OR The asynchronous motor FVC no-load auto-tuning encoder is faulty (E20.11). Remedy: Confirm the encoder is correctly connected. Confirm the actual encoder pulses per revolution matches the setting value of F1-27 (Encoder pulses per revolution).
E20.12 Encoder fault	Cause: Error between encoder feedback speed and speed estimated by SVC is too large. Remedy: Confirm the encoder is correctly connected. Confirm the motor parameters are correctly set. Confirm motor auto-tuning is performed.
E20.13 Encoder fault	Cause: The resolver encoder wire-break occurs. Remedy: Confirm the encoder is correctly connected.
E20.17 Encoder fault	Cause: The wiring of the 23-bit encoder is faulty. Remedy: Check the wiring of the 23-bit encoder.
E21.01 – E21.04 EEPROM read-write fault	Cause: EEPROM read/write is abnormal. Remedy: If the writing is done through communication, ensure that you use the RAM address of the parameter. For the mapping rules of all RAM addresses to parameters, see section 6.2.4. The EEROM chip is damaged. Contact the manufacturer to replace the control board.
E22.00 Motor auto-tuning warning	Cause: The asynchronous motor stator resistance after auto-tuning is over range. Remedy: Set Group F1 (1st Motor Parameters) according to the motor nameplate. Perform auto-tuning when the motor is stopped.
E22.01 Motor auto-tuning warning	Cause: The asynchronous motor rotor resistance after auto-tuning is over range. Remedy: Perform auto-tuning when the motor is stopped.
E22.02 Motor auto-tuning warning	Cause: The asynchronous motor no-load current and mutual inductive reactance is over range. (Note: This may be slightly inaccurate). Remedy: Set Group F1 (1st Motor Parameters) according to the motor nameplate. Confirm the motor is disconnected from the load.
E22.03 Motor auto-tuning warning	Cause: The synchronous motor back EMF after auto-tuning is over range. Remedy: Set F1-02 (Rated motor voltage) according to the motor nameplate. Confirm the motor is disconnected from the load.
E22.04 Motor auto-tuning warning	Cause: Inertia auto-tuning is faulty. Remedy: Set F1-03 (Rated motor current) according to the motor nameplate.
E23.00 Short circuit to ground	Cause: The motor is short circuited to the ground. Remedy: Replace the cable or motor.
E24.00 Phase to phase short circuit	Cause: Phase to phase short circuit occurs on the motor. Remedy: Check whether short-circuit occurs on the output UVW.
E25.00 Power supply unit fault	Cause: The power supply unit is faulty. Remedy: Eliminate the fault, such as input phase loss and overheat. 1: Operation enable 2: Incoming breaker feedback 3: Auxiliary breaker feedback 4: Leakage breaker feedback 6: Drive unit operation forbidden 7: Drive unit coast-to-stop 8: Drive unit shutdown by setting
E25.12 Power supply unit fault	Cause: The grid voltage is abnormal. Remedy: Check whether the three-phase power supply is normal. Check whether the input cables break. Check whether input terminals are connected properly. Check the hardware voltage detection circuit. Adjust the three-phase voltage to the allowable range. Check whether the three-phase power supply is normal. Check the hardware voltage detection circuit.
E25.14 Power supply unit fault (IGBT overheating)	Cause: The IGBT is overheating. Remedy: Lower the ambient temperature. Clean the air duct. Replace the fan. Contact Inovance or the agent for technical support.
E25.16 Power supply unit fault (Communication fault)	Cause: A communication fault occurs. Remedy: Check whether the RS485 communication cable is connected properly. Check whether the setting of Fd-04 (Modbus communication timeout) and PLC communication period are reasonable. Check whether the CAN communication cable is connected properly. Check Fd-15 (Maximum value of node receiving error counter) to Fd-17 (CANopen/CANlink bus disconnection times in a period) to obtain the interference information. Check the PDO mapping of parameters in group AF. Check whether the power supply unit is working. Check whether the network cables are connected for the power supply unit and drive unit. Check whether the termination resistor is connected properly. Check Fd-12 (CAN baud rate) to see whether the CAN baud rate is consistent. If the power supply unit is faulty, rectify the fault. Modify the CAN station numbers by using Fd-13 (CAN station No.). Check whether the PROFIBUS-DP cable is connected properly. Check whether the number displayed in “The number of devices” of PLC matches the actual quantity of stations. Check whether the station numbers of slaves are correctly set. Check whether the value of “NO.n” of PLC is consistent with that of AF-66/AF-67.
E25.21 Power supply unit fault (EEPROM faulty)	Cause: The EEPROM is faulty. Remedy: Contact Inovance or the agent for technical support.
E25.61 Power supply unit fault (Braking unit faulty)	Cause: The braking unit is faulty. Remedy: Check whether the braking resistor is short circuited. Check whether the braking transistor is short circuited. Check whether the braking resistance and power class of the AC drive are too small. Check whether external interference exists. Check whether the hardware circuit detection is normal. Lower the ambient temperature. Check whether the cooling fan works properly. Clean the air duct. Check whether the temperature sensor is damaged.
E26.00 Accumulative running time reached	Cause: The accumulative running time reached the set value. Remedy: Clear the record by parameter initialization.
E27.00 User-defined fault 1	Cause: The signal of user-defined fault 1 is input through the multi-functional terminal DI or virtual I/O. Remedy: Perform the reset operation.
E28.00 User-defined fault 2	Cause: The signal of user-defined fault 2 is input through the multi-functional terminal DI or virtual I/O. Remedy: Perform the reset operation.
E29.00 Accumulative power-on time reached	Cause: The accumulative power-on time reached the set value. Remedy: Clear the record by parameter initialization.
E30.00 Load loss	Cause: The operation current of the drive is smaller than F9-64 (Load loss detection level). Remedy: Check whether the load is disconnected. Ensure that F9-64 (Load loss detection level) and F9-65 (Load loss detection time) are set based on the actual conditions.
E31.00 PID Feedback loss	Cause: PID feedback is smaller than FA-26 (Detection level of PID feedback loss). Remedy: Check the PID feedback signal. Set FA-26 (Detection level of PID feedback loss) correctly.
E42.00 Speed error	Cause: 1. Encoder parameters are set improperly. 2. Motor auto-tuning is not performed. 3. F9-69 (Detection level of speed deviation excessive) and F9-70 are set incorrectly. Remedy: Set encoder parameters properly. Perform motor auto-tuning. Set F9-69 and F9-70 correctly based on actual condition.
E43.00 Motor overspeed	Cause: 1. Encoder parameters are set improperly. 2. Motor auto-tuning is not performed. 3. F9-67 (Overspeed detection level) and F9-68 are set incorrectly. Remedy: Set encoder parameters properly. Perform motor auto-tuning. Set F9-67 and F9-68 correctly based on the actual situation.
E45.00 Motor overheat	Cause: 1. Cable connection of the temperature sensor becomes loose. 2. The motor temperature is too high. 3. The setting of F9-57 (Motor overheat protection threshold) is too small. Remedy: Check cable connection of the temperature sensor. Increase the carrier frequency or take other measures to cool the motor. Adjust the setting of motor overheat protection threshold between 90°C to 100°C.
E46.01 Improper master/slave setting	Cause: The setting of A8-10, A8-50, and A8-70 is different. Remedy: Set A8-10 (Master/Slave selection in speed and position control), A8-50 (Load allocation), and A8-70 (Droop control) to Slave.
E47.00 STO fault/triggering	Cause: STO fault occurred. Remedy: Check whether F8-54 (STO function) is set to 1 (Enabled). If an error is displayed and STO is enabled, check whether drive unit terminals STO1 and STO2 have 24 V input.
E54.01 Home abnormal (Timeout/No data)	Cause: The AC drive does not receive valid home data after the time set by B4-18. Remedy: Check whether the home signal is connected properly. Check whether B4-05 (Position control home signal source) is set properly. Check whether the home searching timeout is set too short. Check whether the home searching speed is too low. When home data is received through the DI, check whether terminal function (68) is set properly. When encoder Z signal is used as home, check whether Z signal exists.
E54.02 Home abnormal (Z signal deviation)	Cause: When the Z signal is used as the home, the position deviation between adjacent Z signals exceeds B4-19. Remedy: Check the field wiring and check whether the shielded cable of the encoder is connected properly (Interference). The encoder Z signal is abnormal. Manually rotate the motor and check U2-75 and U2-76. If abnormal, the encoder may be faulty.
E54.03 Home abnormal (Home loss)	Cause: In absolute/fixed length mode, times drive does not receive normal home signal > B4-67. Remedy: Check whether the home signal is connected properly. The home signal suffers from interference. The DI filter time is too large; reduce the DI home filter time properly. The DI home time is too short, so the home signal cannot be collected.
E55.00 Position deviation large	Cause: In position synchronization mode, the pulse deviation is too large and the slave cannot follow the host. Remedy: Set A8-32 (Detection threshold of excessive deviation) and A8-33 (Detection time of excessive deviation).