Inovance MD500 Plus Drive Fault Codes List
A comprehensive guide to Inovance MD500-Plus fault codes. Troubleshoot this enhanced vector drive, interpret Err codes, and access diagnostic data via InoDriveShop.
Inovance MD500-Plus Fault Codes Reference Table
Below is the complete list of fault codes, definitions, and troubleshooting steps associated with the MD500-Plus series.
Inovance MD500 Plus Drive Fault Codes List
| Fault Code and Meaning | Cause and Remedy |
|---|---|
| E02.00 Overcurrent during acceleration |
Cause: Grounded or short-circuited output circuit of the AC drive.
Remedy:
Cause: Auto-tuning is not performed in SVC or FVC control mode.
Remedy:
Cause: Excessively short acceleration time.
Remedy:
Cause: Inappropriate overcurrent stall suppression.
Remedy:
Cause: Inappropriate customized torque boost or V/f curve.
Remedy:
Cause: Startup of a running motor.
Remedy:
Cause: External interference to the AC drive.
Remedy:
|
| E03.00 Overcurrent during deceleration |
Cause: Grounded or short-circuited output circuit of the AC drive.
Remedy:
Cause: Auto-tuning is not performed in SVC or FVC control mode.
Remedy:
Cause: Excessively short deceleration time.
Remedy:
Cause: Inappropriate overcurrent stall suppression.
Remedy:
Cause: The braking unit and braking resistor are not installed.
Remedy:
Cause: External interference to the AC drive.
Remedy:
|
| E04.00 Overcurrent during operation at constant speed |
Cause: Grounded or short-circuited output circuit of the AC drive.
Remedy:
Cause: Auto-tuning is not performed in SVC or FVC control mode.
Remedy:
Cause: Inappropriate overcurrent stall suppression.
Remedy:
Cause: Inadequate power rating of the AC drive.
Remedy:
Cause: External interference to the AC drive.
Remedy:
|
| E05.00 Overvoltage during acceleration |
Cause: High input grid voltage.
Remedy:
Cause: External force driving the motor during acceleration.
Remedy:
Cause: Inappropriate overvoltage suppression.
Remedy:
Cause: The braking unit and braking resistor are not installed.
Remedy:
Cause: Excessively short acceleration time.
Remedy:
|
| E06.00 Overvoltage during deceleration |
Cause: Inappropriate overvoltage suppression.
Remedy:
Cause: External force driving the motor during deceleration.
Remedy:
Cause: Excessively short deceleration time.
Remedy:
Cause: The braking unit and braking resistor are not installed.
Remedy:
|
| E07.00 Overvoltage during operation at constant speed |
Cause: Inappropriate overvoltage suppression.
Remedy:
Cause: External force driving the motor during operation.
Remedy:
|
| E09.00 Undervoltage |
Cause: Instantaneous power failure.
Remedy:
Cause: AC drive input voltage out of range.
Remedy:
Cause: Abnormal bus voltage.
Remedy:
Cause: Abnormal rectifier, IGBT driver board, or IGBT control board.
Remedy:
|
| E10.00 AC drive overload |
Cause: Excessively heavy load or stalled motor.
Remedy:
Cause: Inadequate power rating of the AC drive.
Remedy:
Cause: Auto-tuning is not performed in SVC or FVC control mode.
Remedy:
Cause: Excessively high torque boost (F3-01) in V/f control mode.
Remedy:
Cause: Output phase loss on the AC drive.
Remedy:
|
| E11.00 Motor overload |
Cause: Inappropriate F9-01 (motor overload protection gain) setting.
Remedy:
Cause: Excessively heavy load or stalled motor.
Remedy:
|
| E12.00 Input phase loss |
Cause: Input phase loss.
Remedy:
|
| E13.00 Output phase loss |
Cause: Motor fault.
Remedy:
Cause: Abnormal lead wire connecting the AC drive to the motor.
Remedy:
Cause: Unbalanced three-phase output of the AC drive during motor operation.
Remedy:
Cause: Abnormal driver board or IGBT.
Remedy:
|
| E14.00 IGBT overtemperature |
Cause: High ambient temperature; Blocked air filter; Damaged fan; Damaged thermistor of the IGBT; Damaged IGBT. Remedy:
|
| E15.01 External fault |
Cause: External fault signal input to the multi-function DI terminal (normally open). Remedy: Rectify the external fault, and ensure that the mechanical condition allows restart (F8-18). |
| E15.02 External fault |
Cause: External fault signal input to the multi-function DI terminal (normally closed). Remedy: Rectify the external fault, and ensure that the mechanical condition allows restart (F8-18). |
| E16.01 Communication fault (Modbus) |
Cause: Modbus communication timeout. Remedy:
|
| E16.11 Communication fault (CANopen) |
Cause: CANopen communication timeout. Remedy:
|
| E16.12 Communication fault (CANopen PDO) |
Cause: Inconsistency between the configured CANopen-based PDO mapping and the actual mapping. Remedy: Check the PDO mapping of parameters in group AF. |
| E16.21 Communication fault (CANlink) |
Cause: CANlink heartbeat timeout. Remedy:
|
| E16.22 Communication fault (CANlink Conflict) |
Cause: CANlink station number conflict. Remedy: Change the value of FD-13 to make CANlink station numbers different from each other. |
| E17.00 Contactor fault |
Cause: Abnormal driver board and power supply; Abnormal contactor; Abnormal lightning protection board. Remedy:
|
| E18.00 Damaged current sampling circuit |
Cause: Abnormal AC drive current sampling. Remedy:
|
| E19.02 Motor auto-tuning fault |
Cause: Fault in auto-tuning on the magnetic pole position angle of the synchronous motor. Remedy: Ensure that the motor is connected and there is no output phase loss. |
| E19.06 E19.07 E19.08 Motor auto-tuning fault |
Cause: Fault in auto-tuning on the stator resistance. Remedy:
|
| E19.09 E19.10 Motor auto-tuning fault |
Cause: Fault in auto-tuning on the transient leakage inductance of the asynchronous motor. Remedy:
|
| E19.11 Motor auto-tuning fault |
Cause: Inertia auto-tuning fault. Remedy:
|
| E19.20 Motor auto-tuning fault |
Cause: Timeout of auto-tuning on the no-load zero position angle of the synchronous motor. Remedy: Check the Z feedback signal. |
| E19.23 Motor auto-tuning fault |
Cause: Fault in auto-tuning on the magnetic pole position of the synchronous motor. Remedy:
|
| E19.24 Motor auto-tuning fault |
Cause: Errors in auto-tuning on the transient leakage inductance of the asynchronous motor. Remedy: Check whether the power rating of the AC drive is low. If yes, use an AC drive with a proper power rating matching the motor power. |
| E20.00 Encoder fault |
Cause: Encoder disconnected. Remedy: Restore the connection. |
| E20.01 E20.02 E20.03...E20.08 Encoder fault / Disconnected / Tuning fault |
Cause: General encoder faults, disconnections, or faults during no-load/with-load auto-tuning. Remedy:
|
| E20.09 Encoder fault |
Cause: Encoder fault during auto-tuning of the synchronous motor. Remedy: Check the encoder Z signal and wiring of the PG card. |
| E20.10 Encoder fault |
Cause: Synchronous motor encoder fault. Remedy: See general encoder remedies (Connection, F1-27 consistency). |
| E20.11 Encoder fault |
Cause: The encoder is faulty during FVC no-load auto-tuning of the asynchronous motor. Remedy:
|
| E20.12 Encoder fault |
Cause: Excessive deviation between the encoder feedback speed and the speed estimated by SVC. Remedy:
|
| E20.13 Encoder fault |
Cause: Resolver encoder disconnected. Remedy: Check the wiring of the encoder. |
| E20.17 Encoder fault |
Cause: 23-bit encoder disconnected. Remedy: Check the wiring of the 23-bit encoder. |
| E21.01 E21.02 E21.03 E21.04 EEPROM read/write fault |
Cause: EEPROM read/write abnormality. Remedy:
|
| E22.00 Motor auto-tuning error |
Cause: Auto-tuned stator resistance out of range. Remedy:
|
| E22.01 Motor auto-tuning error |
Cause: Auto-tuned rotor resistance of the asynchronous motor out of range. Remedy:
|
| E22.02 Motor auto-tuning error |
Cause: The no-load current and mutual inductance of the asynchronous motor obtained through auto-tuning exceed the allowed range. (Note: If this alarm is reported, the AC drive calculates values based on known parameters which may not be optimal). Remedy:
|
| E22.03 Motor auto-tuning error |
Cause: Auto-tuned back EMF of the synchronous motor out of range. Remedy:
|
| E22.04 Motor auto-tuning error |
Cause: Inertia auto-tuning fault. Remedy:
|
| E23.00 Short circuit to ground |
Cause: Motor shorted to the ground. Remedy:
|
| E24.00 Motor inter-phase short circuit |
Cause: Motor inter-phase short circuit. Remedy:
|
| E25.00 Rectifier fault |
Cause: Rectifier fault (e.g., input phase loss, overtemperature). Remedy: Rectify corresponding faults based on feedback signals:
|
| E26.00 Accumulative running time reach |
Cause: The accumulative running time has reached the reference value. Remedy:
|
| E27.00 User-defined fault 1 |
Cause: The user-defined fault 1 signal is input via the DI OR input through the virtual I/O function. Remedy:
|
| E28.00 User-defined fault 2 |
Cause: The user-defined fault 2 signal is input via the DI OR input through the virtual I/O function. Remedy:
|
| E29.00 Accumulative power-on time reach |
Cause: The accumulative power-on time has reached the reference value. Remedy:
|
| E30.00 Load lost |
Cause: Running current of the AC drive less than the value of F9-64. Remedy:
|
| E31.00 PID feedback loss during operation |
Cause: PID feedback less than the value of FA-26. Remedy:
|
| E40.00 Pulse-by-pulse current limit fault |
Cause: 1. Excessively heavy load or stalled motor. 2. Inadequate power rating of the AC drive. Remedy:
|
| E42.00 Excessive speed deviation |
Cause: 1. Incorrect setting of encoder parameters. 2. Auto-tuning is not performed on parameters. 3. Inappropriate setting of F9-69 and F9-70. Remedy:
|
| E43.00 Motor overspeed |
Cause: 1. Incorrect setting of encoder parameters. 2. Auto-tuning is not performed on parameters. 3. Inappropriate setting of F9-67 and F9-68. Remedy:
|
| E45.00 Motor overtemperature |
Cause: 1. Temperature sensor loosely connected. 2. High motor temperature. 3. Excessively low value of F9-57 (motor overtemperature protection threshold). Remedy:
|
| E60.00 AC drive overtemperature |
Cause: High internal temperature of the AC drive. Remedy:
|
| E61.00 Braking transistor overload |
Cause: Excessively low resistance of the braking resistor. Remedy:
|
| E62.00 Braking transistor short circuit |
Cause: Braking transistor short circuit. Remedy:
|
| E63.00 Low liquid level alarm |
Cause: Low liquid level of the water tank. Remedy:
|
| E64.00 Water cooling system fault |
Cause: Water-cooling system control unit fault. Remedy:
|
How to Read MD500-Plus Faults via InoDriveShop
The MD500-Plus is often installed in critical or difficult environments (textiles, stone processing, etc.). Accurate diagnosis is vital to prevent repeat failures. In 2026, using the InoDriveShop PC software is the standard for troubleshooting.
- Environmental Context: Since the “Plus” series is designed for harsher environments, pay close attention to thermal faults (like Err14). Use the software to check the “Module Temperature” history to see if the drive is suffering from blocked airflow or ambient heat spikes.
- Detailed Fault Snapshot: The drive stores detailed electrical data (Bus Voltage, Current, I/O State) at the exact moment of the trip. This is accessible via parameter group U0 or the “Fault Diagnosis” window in InoDriveShop.
- Waveform Recording: For intermittent issues, use the oscilloscope function to trigger a recording on a specific fault code. This helps verify if power supply instability or instantaneous load shocks are triggering the protection mechanisms.
Frequently Asked Questions (FAQ)
Q: What is the difference between an Alarm and a Fault?
A: An Alarm (displayed as ‘A’ or ‘ALm’ codes) is a warning that operational limits are being reached, but the drive continues to output power. A Fault (displayed as ‘Err’ codes) is a hard stop condition where the drive immediately disables the output to protect internal components.
Q: How do I reset an Inovance MD500-Plus fault?
A: You can reset the drive using the following methods:
- Pressing the STOP/RESET button on the keypad.
- Activating a Digital Input (DI) programmed for the “Reset” function (Function 9).
- Cycling the main power (ensure the display turns off completely before powering back on).
Q: Where is the fault history stored?
A: The MD500-Plus stores the last 3 fault codes in parameters U0-00 (most recent), U0-01, and U0-02. The specific running data (Amps, Volts, Hz) for the most recent fault is preserved in parameters U0-03 through U0-17.
Comments
Post a Comment