INVT DA300 Drive Fault Codes:
| Fault Code and Meaning | Cause and Remedy |
|---|---|
| Er01-0 IGBT fault | Cause: The drive actual output current exceeds the specified value. 1. Drive fault (such as drive circuit or IGBT fault). 2. Drive cables U, V, and W are short connected, or drive cables are grounded or contacted improperly. 3. The motor breaks down. 4. Drive cables U, V, and W are connected in reverse phases. 5. Improper parameter settings cause system divergence. 6. The ACC/DEC time in the start or stop process is too short. 7. Instantaneous load is too heavy. Remedy:
|
| Er01-1 Brake pipe fault (models 7.5kW or above) | Cause: Brake unit fault. Remedy:
|
| Er01-5 IPM fault | Cause: The drive actual output current exceeds the specified value. 1. Drive fault (such as drive circuit or IGBT fault). 2. Drive cables U, V, and W are short connected/grounded. 3. The motor breaks down. 4. Drive cables U, V, and W are connected in reverse phases. 5. Improper parameter settings cause system divergence. 6. ACC/DEC time is too short. 7. Instantaneous load is too heavy. Remedy:
|
| Er02-0 Encoder fault–Encoder offline | Cause: 1. The encoder is not connected. 2. The encoder plug contact is loose. 3. One of encoder signal cables U, V, W, A, B, and Z is disconnected. 4. Encoder phases A and B are reverse. 5. Noise causes communication interruption or data exceptions. 6. Encoder communicates properly but with data exceptions. 7. The FPGA that communicates with the encoder reports timeout. 8. The drive does not support the encoder type. Remedy:
|
| Er02-8 Encoder fault–Encoder battery low-voltage alarm | Cause: When the multiturn absolute encoder is used, the external battery voltage of the encoder is between 3.0V–3.2V. Remedy:
|
| Er02-9 Encoder fault–Encoder battery undervoltage | Cause: When the multiturn absolute encoder is used, the external battery voltage of the encoder is between 2.5V–3.0V. Remedy:
|
| Er02-a Encoder fault–Encoder overheating | Cause: The encoder feedback temperature is higher than the temperature threshold for protection against overheating. Remedy:
|
| Er02-b Encoder fault–Encoder EEPROM writing error | Cause: If the motor is used with a communication encoder, a communication transmission or data check error occurs when the drive updates data to the encoder EEPROM. Remedy:
|
| Er02-c Encoder fault–No data in encoder EEPROM | Cause: If the motor is used with a communication encoder, no data is found in the encoder EEPROM when the motor attempts to read data from it during power-on. Remedy:
|
| Er02-d Encoder fault–Encoder EEPROM data check error | Cause: If the motor is used with a communication encoder, a data check error occurs when the motor attempts to read data from the encoder EEPROM during power-on. Remedy:
|
| Er03-0 Current sensor fault–Phase-U current sensor | Cause: 1. The current sensor or detection circuit is abnormal. 2. The motor shaft is powered on in non-static state. 3. The IPM module of ≤1kW drivers cannot work properly. Remedy:
|
| Er03-1 Current sensor fault–Phase-V current sensor fault | Cause: Same as Er03-0 (Current sensor or detection circuit abnormal). Remedy:
|
| Er03-2 Current sensor fault–Phase-W current sensor fault | Cause: Same as Er03-0 (Current sensor or detection circuit abnormal). Remedy:
|
| Er04-0 System initialization fault | Cause: There are failed self-check items after power-on initialization is complete. Remedy:
|
| Er05-1 Setting fault–Motor model not exist | Cause: P0.00 is set incorrectly. Remedy:
|
| Er05-2 Setting fault–Motor and drive model not match | Cause: P0.00 is set incorrectly. Remedy:
|
| Er05-3 Setting fault–Incorrect software limits | Cause: Software limits are set incorrectly. The setting of P0.35 is equal to or less than that of P0.36. Remedy:
|
| Er05-4 Setting fault–Incorrect homing mode | Cause: The setting of P5.10 is incorrect. Remedy:
|
| Er05-5 Setting fault–PTP-control travel overflow | Cause: The single increment of a PTP idle travel exceeds (2^31 – 1). Remedy:
|
| Er07-0 Regenerative brake over-discharge | Cause: 1. The brake resistor power is low. 2. The motor speed is too high or the deceleration is too quick, which causes the failure to absorb the regenerate energy within specified time. 3. The action limit of the external brake resistor is restricted to the duty ratio 10%. Remedy:
|
| Er08-0 AI overvoltage fault–AI 1 | Cause: The voltage input to the port of analog input 1 exceeds the setting of P3.22. Remedy:
|
| Er08-1 AI overvoltage fault–AI 2 | Cause: The voltage input to the port of analog input 2 exceeds the setting of P3.25. Remedy:
|
| Er08-2 AI overvoltage fault–AI 3 | Cause: The voltage input to the port of analog input 3 exceeds the setting of P3.75. Remedy:
|
| Er09-0 EEPROM fault–Read/write error | Cause: 1. Data is damaged in the data storage area when the drive reads data from the EEPROM. 2. Writing data to the EEPROM is disturbed. Remedy:
|
| Er09-1 EEPROM fault–Data check error | Cause: 1. The data read from EEPROM during power-on is different from the data that is written. 2. The driver DSP version is updated. Remedy:
|
| Er10-0 Hardware fault–FPGA fault | Cause: The FPGA on the control board reports a fault. Remedy:
|
| Er10-1 Hardware fault–Communication card fault | Cause: The external communication card is faulty. Remedy:
|
| Er10-2 Hardware fault–Ground short-connection fault | Cause: One of the motor cables V and W is short connected to the ground, which is found in ground short-connection detection during drive power-on. Remedy:
|
| Er10-3 Hardware fault–External input fault | Cause: This fault occurs when the digital terminal configured with the external fault input function acts. Remedy:
|
| Er10-4 Hardware fault–Emergency stop fault | Cause: This fault occurs when the digital terminal configured with the emergency stop function acts. Remedy:
|
| Er10-5 Hardware fault–RS485 communication fault | Cause: Strong EMI on RS485 communication circuit causes a drive serial communication alarm. Remedy:
|
| Er10-6 Hardware fault–AC power phase loss | Cause: One of the phases R, S, and T is lost. Remedy:
|
| Er10-7 Hardware fault–Fan fault | Cause: The fan built in the servo stops running. Remedy:
|
| Er10-8 Hardware fault–Regenerative transistor fault | Cause: The external regenerative brake resistor is connected improperly or disconnected. Remedy:
|
| Er10-9 Hardware fault–STO phase loss | Cause: There is a phase loss in safety terminal input. Remedy:
|
| Er11-0 Software fault–Motor control task re-entry | Cause: 1. The DSP CPU utilization is too high. 2. The DSP has bugs. Remedy:
|
| Er12-0 I/O fault–Duplicate digital input assignment | Cause: Two or more digital inputs are configured with the same function. Remedy:
|
| Er12-1 I/O fault–Duplicate AI assignment | Cause: When the drive is a standard, analog input 3 is configured as a speed command. Remedy:
|
| Er12-2 I/O fault–Pulse input frequency too high | Cause: 1. External input pulse signal frequency is too high. 2. There is damage to the internal pulse frequency detection circuit of the drive. Remedy:
|
| Er13-0 Main circuit overvoltage | Cause: The DC voltage of the drive main circuit is higher than the specified voltage. 1. The grid voltage is too high. 2. No brake resistor or pipe is connected during braking or the brake resistor is damaged. 3. The DEC time in the stop process is too short. 4. The internal DC voltage detection circuit of the drive is damaged. Remedy:
|
| Er13-1 Main circuit undervoltage | Cause: The DC voltage of the drive main circuit is abnormal. 1. The grid voltage is too low. 2. The buffer relay is not closed. 3. The drive output power is too high. 4. The internal DC voltage detection circuit of the drive is damaged. Remedy:
|
| Er14-0 Control power undervoltage | Cause: The DC voltage of the drive control circuit is abnormal. 1. The grid voltage is too low. Remedy:
|
| Er17-0 Drive overload | Cause: The short-time load on the drive is too heavy. Remedy:
|
| Er17-1 Drive overload 2 | Cause: The drive load is too heavy. Remedy:
|
| Er18-0 Motor overload | Cause: 1. Long-term overload running. 2. Short-time overload. Remedy:
|
| Er18-1 Motor overtemperature | Cause: The motor temperature is higher than the temperature threshold for protection against overheating. Remedy:
|
| Er19-0 Speed fault–Overspeed | Cause: The motor speed absolute value exceeds the setting of P4.32. 1. The motor stalls or motor phases U, V, and W are in reverse sequence. 2. The electronic gear ratio or motor speed loop control parameters are set improperly. 3. The setting of P4.32 is less than that of P4.31. 4. The encoder feedback signal is interfered. Remedy:
|
| Er19-1 Speed fault–CCW overspeed | Cause: The speed feedback exceeds the setting of P4.40 by more than 20ms. Remedy:
|
| Er19-2 Speed fault–CW overspeed | Cause: The speed feedback exceeds the setting of P4.41 by more than 20ms. Remedy:
|
| Er19-3 Speed fault–Overspeed parameter set incorrectly | Cause: The setting of P4.40 is less than 0 or that of P4.41 is greater than 0. Remedy:
|
| Er20-0 Speed deviation fault | Cause: In non-torque mode, the deviation between the motor speed and speed command exceeds the setting of P4.39. 1. The motor phases U, V, and W are in reverse sequence or motor cables are not connected. 2. The motor load is too heavy, which causes motor stalling. 3. The drive force is insufficient, which causes motor stalling. 4. The speed loop control parameters are set improperly. 5. The setting of P4.39 is too low. Remedy:
|
| Er21-0 Position overtravel–CCW | Cause: In position mode, the CCW limit switch is touched or the accumulated feedback pulse exceeds the setting of P0.35. Remedy:
|
| Er21-1 Position overtravel–CW | Cause: In position mode, the CW limit switch is touched or the accumulated feedback pulse exceeds the setting of P0.36. Remedy:
|
| Er22-0 Position deviation fault | Cause: 1. Server response time is too slow. Therefore the residual pulses exceed the setting of P4.33. 2. The motor load is too heavy, which causes motor stalling. 3. Pulse input frequency is too high, exceeding the maximum motor speed. 4. The step variable in the position command input exceeds the setting of P4.33. Remedy:
|
| Er22-1 Hybrid control deviation too large | Cause: In fully-closed loop control, the feedback position deviation between the grating ruler and encoder exceeds the setting of P4.64. Remedy:
|
| Er22-2 Position increment overflow | Cause: The single-variation position command after electronic gear ratio conversion exceeds (2^31 – 1). Remedy:
|
| Er23-0 Drive overtemperature | Cause: 1. The ambient temperature of the drive exceeds the specified temperature. 2. The drive is overloaded. Remedy:
|
| Er25-4 Application fault–Encoder offset angle test timeout | Cause: An exception occurred in the encoder offset angle test. Remedy:
|
| Er25-5 Application fault–Encoder offset angle test failed | Cause: There is great fluctuation in current feedback in the encoder offset angle test. Remedy:
|
| Er25-6 Application fault–Homing offside | Cause: The limit switch or software limit is enabled during homing. Remedy:
|
| Er25-7 Application fault–Inertia identifying failed | Cause: 1. During inertia identifying, the motor stops rotating with vibration of longer than 3.5s. 2. The actual ACC time for inertia identifying is too short. 3. The inertia identifying speed is lower than 150r/min. Remedy:
|
| Er25-8 Application fault–Magnetic pole check failed | Cause: 1. The power cable phase sequence is incorrect. 2. The encoder direction conflicts with the power cable phase sequence. 3. External force or overload occurs in the check. Remedy:
|
| Er25-9 Application fault–Overtravel/overspeed in confirmation of magnetic pole check | Cause: The motor motion range is too large or speed is too fast in the confirmation of magnetic pole. Remedy:
|
| Er25-a Application fault–Out-of-range in magnetic pole check | Cause: The motor motion range exceeds the specified range in the magnetic pole check. Remedy:
|
| Er22-3 Synchronization signal timeout | Cause: In Interpolation position mode, the time interval between two adjacent synchronization frame signals is more than twice the communication cycle. Remedy:
|
| Er22-4 Full position command buffer | Cause: CANopen PTP position command buffer is full. Remedy:
|
| Er26-0 CANopen offline | Cause: The master node does not receive heartbeat packets from a slave node within a period of time. Remedy:
|
| Er26-1 SDO index not exist | Cause: When the SDO reads or writes parameters, the index does not exist in the object dictionary or is not supported by the servo drive. Remedy:
|
| Er26-2 SDO sub-index not exist | Cause: When the SDO reads or writes parameters, the index exists in the object dictionary, but the sub-index does not exist in the dictionary or is not supported by the servo drive. Remedy:
|
| Er26-3 Incorrect SDO data length | Cause: The length information in SDO read or write commands does not match the data length in the servo drive object dictionary. Remedy:
|
| Er26-4 SDOCANopen fault–SDO data out of range | Cause: The data that the SDO writes exceeds the data range in the servo drive object dictionary. Remedy:
|
| Er26-5 Modification not allowed for read-only | Cause: There are attempts to modify read-only parameters. Remedy:
|
| Er26-6 Incorrect PDO mapping length | Cause: The total length of data mapped from the PDO exceeds 64 bits. Remedy:
|
| Er26-7 PDO mapping data not exist | Cause: The parameters associated with the data mapped from the PDO are not found in the object dictionary. Remedy:
|
| Er26-8 PDO modification not allowed in operational state | Cause: There are attempts to modify PDO mappings. Remedy:
|
| Er26-9 PDO mapping not allowed | Cause: There are attempts to map parameters that disallow mapping to the PDO. Remedy:
|
| Er26-a Synchronization signal too fast | Cause: In synchronization working mode, the number of frames received by a slave node exceeds the range supported by the baud rate. Remedy:
|
| Er26-b Receiving fault | Cause: CAN communication is offline or the error receiving counter exceeds 128. Remedy:
|
| Er26-c Sending fault | Cause: CAN communication is offline or the error receiving counter exceeds 128. Remedy:
|
| Er26-d Duplicate synchronization signal | Cause: In the case where a slave node is configured to generate synchronization signals, external synchronization signals are received. Remedy:
|
| Er26-e Bus load ratio too high | Cause: In asynchronous working mode, the number of frames received by a slave node exceeds the range supported by the baud rate. Remedy:
|
| Er26-f Incorrect parameter modification status | Cause: The SDO attempts to modify parameters in a state that disallows modification. Remedy:
|
| Er24-8 Initialization fault | Cause: The EtherCAT chip contact is abnormal. Remedy:
|
| Er24-9 EEPROM fault | Cause: No data is found in the EtherCAT EEPROM or data reading failed. Remedy:
|
| Er24-a DC Sync0 signal exception | Cause: In DC synchronization working mode, DC Sync0 signal interruption is not detected within a period of time. Remedy:
|
| Er24-b Disconnection | Cause: After the drive is enabled, the network cable contact is improper or the master node of EtherCAT communication works abnormally. Remedy:
|
| Er24-c PDO data lost | Cause: After the drive is enabled, the drive does not receive PDO data within a period of time. Remedy:
|