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.
|
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] to Fd-17 (Bus disconnection times) 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 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 and Fd-17 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 bridge 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 bridge 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 Profibus-DP-to-CANopen bridge configuration are incorrectly set.
Remedy:
- Check that the value of the “NO. n” parameter of PLC is consistent with the setting of AF-66 (Valid RPDOs) and AF-67 (Valid TPDOs).
|
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 Profibus-DP-to-CANopen bridge configuration are incorrectly set.
Remedy:
- Check that the value of the “NO. 1” parameter of PLC is consistent with the setting of AF-66 and AF-67 of the bridge 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. Ensure data length of PLC configuration is consistent with 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 and power of the braking resistor are 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:
- Lower the ambient temperature.
- Check whether the cooling fan runs properly.
- Clean the ventilation.
- Check whether the temperature sensor is damaged.
|
-H-C-
HC Displayed |
Cause:
– Related components on control board are damaged.
– Motor or motor cable short circuited to ground.
– The hall is damaged.
– Mains voltage is too low.
Remedy:
- Contact the agent or Inovance.
|
E23.00
Motor short circuit |
Cause:
– The motor or motor cable is short circuited to the ground.
– The power supply unit is damaged.
Remedy:
- Use a megger to measure the insulation resistance of the motor and motor cable.
- Contact the agent or Inovance.
|