Inovance MD520 Drive Fault Codes List

A comprehensive guide to Inovance MD520 universal drive fault codes. Learn to interpret Err codes, use the advanced LCD keypad, and resolve STO and vector control issues.

Inovance MD520 Fault Codes Reference Table

Below is the complete list of fault codes, STO warnings, and troubleshooting actions associated with the MD520 series.

  Inovance MD520 Drive Fault Codes List

Inovance MD520 Drive Fault Codes List

Fault Code and Meaning Cause and Remedy
E002.1
Hardware overcurrent
Cause: The instantaneous output current exceeds 2.5*1.414 times the rated current.

Remedy: Connect to mobile App via Wi-Fi for self-diagnosis.
Cause: Output grounding.

Remedy: Check for output ground points and measure the ground impedance by segment using a megohmmeter.
Cause: Inter-phase short-circuit.

Remedy:
  • Check whether the output side is short circuited.
  • Check whether the power cable is short circuited.
  • Check whether motor resistance is symmetrical.
Cause: No parameter auto-tuning in vector control mode.

Remedy: Set motor parameters correctly and perform auto-tuning again.
Cause: Encoder interference or wire breakage.

Remedy:
  • Check if encoder cable is connected securely.
  • Check if encoder cable is grounded at the AC drive side.
  • Ground the motor enclosure.
  • Replace the encoder and the encoder cable.
Cause: Output phase loss.

Remedy:
  • Check if cables are properly connected.
  • Check contactor opening logic and contacts if present at output.
Cause: Current detection exception.

Remedy: Contact after-sales service.
Cause: V/f control acceleration/deceleration time too short.

Remedy:
  • Enable the overcurrent suppression function.
  • Increase the acceleration/deceleration time.
Cause: Encoder phase sequence error.

Remedy: If encoder direction and motor running direction are opposite, change the encoder direction.
Cause: Model setting error.

Remedy: Set the AC drive model correctly (FF-01).
E002.2
Software overcurrent
Cause: Software overcurrent threshold (FF-18) triggered. Default is 100% (indicating threshold does not take effect).

Remedy: Refer to remedies for E002.1 (Hardware overcurrent) as causes are identical.
Cause: Output grounding.

Remedy: Check for output short-to-ground and measure ground impedance.
Cause: Inter-phase short-circuit.

Remedy: Check output side, power cable, and motor resistance symmetry.
Cause: No parameter auto-tuning in vector control mode.

Remedy: Set motor parameters correctly and perform auto-tuning.
Cause: Encoder interference, wire breakage, or phase sequence error.

Remedy: Check connections, grounding, or change encoder direction.
Cause: V/f control accel/decel time too short.

Remedy: Enable overcurrent suppression; Increase accel/decel time.
E005.1
Bus overvoltage
Cause: Output grounding.

Remedy: Check output side/power cable for shorts; check motor resistance symmetry.
Cause: Encoder interference/wire breakage.

Remedy: Check connections, grounding, or replace encoder/cable.
Cause: Power generation during motor deceleration.

Remedy:
  • Enable overvoltage suppression if there is no active load.
  • Connect a braking resistor if possible.
  • Set F3-19 (V/f) or AB-25 bit1 (Vector) settings.
Cause: Fault reaction upon runaway of synchronous motor.

Remedy: Shorten overspeed protection time (F9-67 and F9-68).
Cause: Braking resistor selection error.

Remedy: Ensure braking module power is sufficient (Continuous load 0.8x motor power, Short-term 1.5x).
Cause: Braking resistor phase loss.

Remedy: Check that the braking resistor is properly connected.
Cause: Overshoot upon speed reach in vector control mode.

Remedy: Configure RFG with rounding time and acceleration feedforward.
Cause: V/f oscillation.

Remedy: Enable oscillation suppression function and optimize the coefficient.
Cause: AC drive model setting error.

Remedy: Set the AC drive model correctly.
E008.1
Frequent pre-charge		 Cause: Pre-charge circuit exception (action of the pre-charge contactor can be heard frequently).

Remedy: Contact after-sales service (frequent pre-charge can cause overload of the circuit).
E009.1
Undervoltage
Cause: Instantaneous power failure.

Remedy: Enable overvoltage suppression if no active load. Set F9-59 (V/f) or AB-25 bit0 (Vector).
Cause: AC drive input voltage out of range.

Remedy: Adjust the input voltage to the normal range.
Cause: Input phase loss and large output power.

Remedy: Make sure the input grid is normal.
Cause: High undervoltage threshold.

Remedy: Lower the undervoltage threshold as appropriate.
Cause: AC drive model setting error.

Remedy: Set the AC drive model correctly.
Cause: Rectifier bridge, pre-charge resistor, drive board, or control board exception.

Remedy: Contact the technical support personnel.
E009.3
Pre-charge fault		 Cause: Failure to power on the bus long after the motor is started in the state of undervoltage.

Remedy: Start the motor after the bus becomes stable after power-on.
E010.1
AC drive overload
Cause: Excessive load or locked-rotor.

Remedy: Reduce the load and check the motor and mechanical conditions.
Cause: High carrier frequency.

Remedy: Decrease the carrier frequency.
Cause: Low bus voltage during high speed running with heavy load.

Remedy:
  • Increase the input voltage of the grid.
  • Enable the overmodulation function.
Cause: Derating at low frequency due to long-term running below 5 Hz.

Remedy: Avoid running motor with heavy load at low speed for long time, or select higher power AC drive.
Cause: Output grounding or Output phase loss.

Remedy: Check for output ground points and output phase loss.
Cause: Motor parameter error.

Remedy: Check nameplate parameters and perform auto-tuning correctly.
Cause: Flying start not applied when the motor is started during rotation.

Remedy: Enable flying start by setting F6-00.
Cause: Encoder direction error.

Remedy: Change the A/B phase sequence of the encoder (F1-30).
Cause: Inadequate power rating of the AC drive.

Remedy: Replace the AC drive with one of higher power rating.
E010.3
AC drive pre-overload		 Cause: AC drive overload ratio reaching 80%.

Remedy:
  • Same countermeasures as E010.1 (see above).
  • Change the pre-overload response level by setting parameters in group H1 (pre-overload is not reported by default).
E011.1

Motor overload		 Cause:
Inappropriate F9-01 (motor overload protection) setting; Inadequate power rating of the motor; Brake error; Excessive load or locked-rotor.

Remedy:
  • Set F9-01 correctly.
  • Select an appropriate motor.
  • Check that the brake can be opened properly.
  • Reduce the load and check the motor and mechanical conditions.
E011.2

Motor pre-overload		 Cause:
Motor overload ratio reaching the value of F9-02.

Remedy:
  • Same as E011.1.
  • Change the motor pre-overload coefficient (F9-02).
  • Change the exception response level by setting parameters in group H1 because motor pre-overload is not reported by default.
E012.1

Input phase loss		 Cause:
Three-phase input power input phase loss; Three-phase grid imbalance; Drive board, surge protector, main control board, or rectifier bridge exception.

Remedy:
  • Check that the power input is normal.
  • Make sure the input grid is symmetrical (unbalanced grid causes bus voltage fluctuation).
  • Contact the technical support personnel.
E013.1

Output phase loss		 Cause:
Motor phase loss.

Remedy:
Check whether open circuit occurs on the motor.
E013.2

Output phase loss (Cable)		 Cause:
Exception of the cable connecting the AC drive and the motor.

Remedy:
Check that the wiring is secure.
E013.3

Output phase loss (Unbalance)		 Cause:
Unbalanced three-phase output of the AC drive during motor running.

Remedy:
Check whether the motor three-phase winding is normal. If not, eliminate the fault.
E013.4

Output phase loss (Hardware)		 Cause:
Drive board or IGBT exception.

Remedy:
Contact the technical support personnel.
E014.1

IGBT overheat		 Cause:
Over-high ambient temperature; Air filter blocked; Fan damage; IGBT thermistor damage; IGBT damage.

Remedy:
  • Reduce the ambient temperature.
  • Clean the air filter.
  • Replace the fan.
  • Replace the thermistor.
  • Replace the IGBT.
E014.2

Module pre-overtemperature		 Cause:
Module temperature exceeding the pre-overtemperature threshold.

Remedy:
  • Same as E014.1.
  • Change the exception response level by setting parameters in group H1 because module pre-overtemperature is not reported by default.
E015.1

External device fault (NO)		 Cause:
External fault input through the multi-function DI (NO).

Remedy:
Eliminate the external fault, ensure that the mechanical condition allows restart (F8-18), and reset the operation.
E015.2

External device fault (NC)		 Cause:
External fault input through the multi-functional DI (NC).

Remedy:
Eliminate the external fault, ensure that the mechanical condition allows restart (F8-18), and reset the operation.
E017.1

Contactor fault		 Cause:
Drive board and power supply exception; Contactor exception; Surge protector exception.

Remedy:
  • Replace the drive board or power supply board.
  • Replace the contactor.
  • Replace the surge protector.
E018.1

Current detection fault		 Cause:
Hall component exception; AC drive stopped while synchronous motor is rotating at high speed; Drive board exception.

Remedy:
  • Replace the hall component.
  • Disable zero drift detection by setting bit07 of BF-07.
  • Replace the drive board.
E019.1

Auto-tuning timeout		 Cause:
Motor parameter setting exception or AC drive model setting exception.

Remedy:
Set the motor and AC drive parameters correctly.
E019.2

Auto-tuning interruption		 Cause:
Auto-tuning interrupted by a stop command.

Remedy:
Wait until auto-tuning is completed. The motor will stop automatically.
E019.3

Overcurrent during auto-tuning		 Cause:
Current out-of-control during auto-tuning.

Remedy:
  • Set the motor parameters and AC drive model correctly.
  • Contact the technical support personnel.
E019.4

Auto-tuning back EMF exception		 Cause:
Basic motor parameter setting error; Oscillation suppression failure during auto-tuning of back EMF.

Remedy:
  • Set the motor nameplate parameters and AC drive model correctly.
  • Adjust the oscillation suppression parameter.
E019.5

Motor type setting error		 Cause:
Incorrect motor type.

Remedy:
Set the motor type correctly.
E019.7

No-load current auto-tuning error		 Cause:
No-load current out-of-range during motor auto-tuning.

Remedy:
Set the motor nameplate parameters and AC drive model correctly.
E020.1

Encoder hardware wire breakage detection		 Cause:
Encoder hardware feedback signal exception.

Remedy:
  • Check whether the correct PG card is selected.
  • Check whether the wiring is normal.
  • Check whether the encoder is normal.
  • Check whether the encoder DIP switch is appropriate.
  • Check whether the encoder parameters are set correctly.
  • Set F1-36 to a non-zero value, and set bit02 of AA-30 to enable PG fault detection. (Fault reported only in FVC mode).
E020.2

Encoder PPR error		 Cause:
Inconsistency between encoder feedback speed and actual motor speed.

Remedy:
Check whether the ABZ encoder PPR or number of pole pairs of resolver is incorrect.
E020.3

No encoder feedback		 Cause:
No encoder feedback speed.

Remedy:
  • Check whether the correct PG card is selected.
  • Check whether the wiring is normal.
  • Check whether the encoder is normal.
  • Check whether the encoder DIP switch is appropriate.
  • Check whether the encoder parameters are set correctly.
E020.4

Encoder direction fault		 Cause:
Encoder direction opposite to motor rotation direction.

Remedy:
Set F1-30 to switch the encoder direction.
E020.5

Large encoder feedback speed fluctuation		 Cause:
Sudden change of the encoder feedback speed (introduces control fluctuations/divergence). Detection disabled by default.

Remedy:
  • Check whether the correct PG card is selected.
  • Check whether the wiring is normal.
  • Check whether the encoder is normal.
  • Check whether the encoder DIP switch is appropriate.
  • Check whether the encoder parameters are set correctly.
  • Check whether the encoder shield layer is grounded at the AC drive side.
  • Check whether the motor enclosure is grounded.
  • Check whether the encoder cable is far away from the power cables.
  • Install a magnetic ring on the encoder cable.
  • Use twisted pair cable with dense metal mesh shield layer.
  • Use as few adapters as possible.
  • Set bit01 of A9-09 to enable software detection of wire breakage, set A9-08 to specify coefficient, set bit02 of A9-09 to remove glitches.
E020.8

ABZ encoder Z signal loss		 Cause:
ABZ encoder Z signal loss.

Remedy:
This fault is reported only during self-check when the synchronous motor uses the ABZ encoder in FVC mode.
E020.9

Encoder pulse interference		 Cause:
Encoder feedback speed fluctuation exception.

Remedy:
This fault is reported only during self-check of the encoder.
E021.1
E021.2
E021.3
E021.4

EEPROM read-write fault		 Cause:
EEPROM read-write exception.

Remedy:
  • For parameters written through communication, check the RAM addresses and address mapping (Section 1.2 "Parameter Communication Addresses").
  • If the EEPROM chip is damaged, contact the manufacturer to replace the main control board.
E021.5

EEPROM internal cache overrun		 Cause:
EEPROM internal cache overrun.

Remedy:
For parameters written through communication, check for frequent writes.
E023.1

Short-to-ground		 Cause:
Motor short-to-ground; Self-check during motor running; IGBT short circuit.

Remedy:
  • Check the connector adapters and measure the ground impedance by using a megohmmeter. If the problem persists, replace the cable or motor.
  • Do not run the motor until the cause of the fault is located.
  • Replace the motor and perform static self-check again.
E026.1

Accumulative running duration reach		 Cause:
Accumulative running duration reaching setpoint.

Remedy:
Clear the record through parameter initialization.
E027.1
E027.2

User-defined fault		 Cause:
Signal of user-defined fault input through the multi-function DI terminal, virtual I/O, or connector.

Remedy:
Eliminate the external fault, ensure that the mechanical condition allows restart (F8-18), and reset the operation.
E027.3
E027.4

User-defined fault (Connector)		 Cause:
Signal of user-defined fault input through the connector.

Remedy:
  • Check settings of connector parameters (H2-06 to H2-07).
  • Eliminate the external fault, ensure that the mechanical condition allows restart (F8-18), and reset the operation.
L028.1
L028.2
L028.3
L028.4

User-defined alarm		 Cause:
Signal of user-defined fault input through the connector.

Remedy:
Check settings of connector parameters (H2-08 to H2-11).
E029.1

Accumulative power-on duration reach		 Cause:
Accumulative power-on duration reaching the setpoint.

Remedy:
Clear the record through parameter initialization.
E031.1

PID feedback loss during running		 Cause:
PID feedback less than the value of FA-26.

Remedy:
Check the PID feedback signal or set FA-26 properly.
E032.1

Parameter exception (Reset)		 Cause:
Parameter reset exception.

Remedy:
Reset FP-01. If the fault persists, contact the technical support personnel.
E032.2

Parameter exception (Backup)		 Cause:
Parameter backup exception.

Remedy:
Back up all parameters again. If the fault cannot be reset, contact the technical support personnel.
E032.3

Parameter power-off exception		 Cause:
Parameter power-off exception.

Remedy:
Check whether the power is off and whether the bus capacitor discharges too fast.
E032.4

Parameter setting exception		 Cause:
Parameter setting exception.

Remedy:
Check whether the related parameters are set as required, especially parameters with setting limits that are associated with other parameters.
E032.6

Parameter power-on check exception		 Cause:
Parameter power-on check exception.

Remedy:
Check the value of U2-09. If the value is normal, contact the technical support personnel.
E040.1

Pulse-by-pulse current limit fault		 Cause:
  • Excessive load or locked-rotor.
  • Output short-to-ground.
  • Motor turn-to-turn short circuit.
  • Motor nameplate parameter error.
  • Output phase loss.
  • V/f oscillation.
  • Inadequate power rating of the AC drive.

Remedy:
  • Reduce the load and check the motor and mechanical conditions.
  • Perform self-check to check for the short-to-ground point.
  • Perform self-check, measure whether the resistance of the output terminal is symmetrical with a multimeter; replace motor if short circuit confirmed.
  • Set the motor parameters correctly.
  • Perform self-check and connect the motor properly.
  • Enable V/f oscillation suppression and adjust the oscillation suppression coefficient.
  • Replace the AC drive with one of higher power rating.
E042.1

Excessive speed deviation		 Cause:
  • Incorrect setting of encoder parameters.
  • Motor auto-tuning not performed.
  • Excessive load.
  • Encoder direction fault.
  • Inappropriate setting of F9-69 and F9-70.

Remedy:
  • Set encoder parameters correctly.
  • Perform motor auto-tuning.
  • Ensure that a proper load is connected.
  • Set the encoder direction correctly.
  • Set the parameters correctly based on actual conditions.
E043.1

Motor overspeed		 Cause:
  • Incorrect setting of encoder parameters.
  • Motor auto-tuning not performed.
  • Runaway caused by incorrect encoder zero point angle of synchronous motor.
  • Inappropriate setting of F9-67 and F9-68.

Remedy:
  • Set encoder parameters correctly.
  • Perform motor auto-tuning.
  • Check whether the encoder zero point angle obtained by auto-tuning is accurate and whether the connection is loose.
  • Set the parameters correctly based on actual conditions.
E045.1

Motor overtemperature		 Cause:
  • Loose connection of temperature sensor.
  • Overhigh motor temperature.
  • Excessively low motor overtemperature protection threshold (F9-57 or F9-76).

Remedy:
  • Check the wiring of the temperature sensor.
  • Decrease the carrier frequency or take other measures to cool the motor.
  • Raise the motor overtemperature protection threshold to between 90°C to 100°C.
E045.2

Motor pre-overtemperature		 Cause:
  • Loose connection of temperature sensor.
  • Overhigh motor temperature.
  • Excessively low motor pre-overtemperature protection threshold (F9-58 or F9-77).

Remedy:
  • Check the wiring of the temperature sensor.
  • Decrease the carrier frequency or take other measures to cool the motor.
  • Raise the motor pre-overtemperature protection threshold.
E047.2

STO fault		 Cause: STO1 and STO2 signal disconnection.

Remedy: Check the wiring of STO1 and STO2.
E047.3

STO circuit undervoltage or overvoltage		 Cause: STO circuit voltage exception.

Remedy: Contact the technical support personnel.
E047.4

STO circuit input subsystem exception		 Cause: Input subsystem exception.

Remedy: Contact the technical support personnel.
E047.5

STO blocking output chip exception		 Cause: Chip exception.

Remedy: Contact the technical support personnel.
E051.1

Pole position auto-tuning error		 Cause: Check the motor for output phase loss.

Remedy: Connect the motor output correctly and ensure that the output contactor is closed.
E055.1

Slave error in master-slave control		 Cause: Slave fault.

Remedy: Troubleshoot the problem based on the slave fault code.
E056.2

IGBT U- short circuit		 Cause: IGBT monitoring VCE signal exception.

Remedy: Contact after-sales service.
E056.3

IGBT U+ short circuit		 Cause: IGBT monitoring VCE signal exception.

Remedy: Contact after-sales service.
E056.4

IGBT V- short circuit		 Cause: IGBT monitoring VCE signal exception.

Remedy: Contact after-sales service.
E056.5

IGBT V+ short circuit		 Cause: IGBT monitoring VCE signal exception.

Remedy: Contact after-sales service.
E056.9

Output phase loss		 Cause: Motor output phase loss.

Remedy: Make sure the motor is connected properly and the output contactor is normal.
E057.1

U phase upper bridge or V phase lower bridge IGBT continuity failure		 Cause: IGBT open circuit.

Remedy: Contact after-sales service.
E057.2

U phase lower bridge or V phase upper bridge IGBT continuity failure		 Cause: IGBT open circuit.

Remedy: Contact after-sales service.
E057.3

V phase upper bridge or W phase lower bridge IGBT continuity failure		 Cause: IGBT open circuit.

Remedy: Contact after-sales service.
E057.4

V phase lower bridge or W phase upper bridge IGBT continuity failure		 Cause: IGBT open circuit.

Remedy: Contact after-sales service.
E057.5

W phase upper bridge or U phase lower bridge IGBT continuity failure		 Cause: IGBT open circuit.

Remedy: Contact after-sales service.
E057.6

W phase lower bridge or U phase upper bridge IGBT continuity failure		 Cause: IGBT open circuit.

Remedy: Contact after-sales service.
E057.7

UV output end short circuit		 Cause: Inter-phase output short circuit.

Remedy: Check for inter-phase short circuit.
E057.8

VW output end short circuit		 Cause: Inter-phase output short circuit.

Remedy: Check for inter-phase short circuit.
E057.9

WU output end short circuit		 Cause: Inter-phase output short circuit.

Remedy: Check for inter-phase short circuit.
E058.1

Module U phase current sensor inversely installed		 Cause: Current sampling sensor exception.

Remedy: Contact after-sales service.
E058.2

Module V phase current sensor inversely installed		 Cause: Current sampling sensor exception.

Remedy: Contact after-sales service.
E058.3

Module W phase current sensor inversely installed		 Cause: Current sampling sensor exception.

Remedy: Contact after-sales service.
E058.4

Module UV phase sensor incorrectly inserted		 Cause: Current sampling sensor exception.

Remedy: Contact after-sales service.
E058.5

Module VW phase sensor incorrectly inserted		 Cause: Current sampling sensor exception.

Remedy: Contact after-sales service.
E058.6

Module WU phase sensor incorrectly inserted		 Cause: Current sampling sensor exception.

Remedy: Contact after-sales service.
E059.1

UV phase imbalance		 Cause: Motor turn-to-turn short circuit.

Remedy: Replace the motor and then perform self-check to confirm the cause.
E059.2

VW phase imbalance		 Cause: Motor turn-to-turn short circuit.

Remedy: Replace the motor and then perform self-check to confirm the cause.
E059.3

WU phase imbalance		 Cause: Motor turn-to-turn short circuit.

Remedy: Replace the motor and then perform self-check to confirm the cause.
E061.1

Braking unit overload		 Cause: Overhigh power of braking resistor (resistance too small).

Remedy: Use a braking resistor with higher resistance.
E062.2

Braking transistor shoot-through		 Cause:
  • Braking module exception.
  • Braking resistor short circuit.

Remedy:
  • Contact the technical support personnel.
  • Check whether the braking resistor is short circuited or damaged. If yes, replace it.
E062.3

Braking transistor overcurrent		 Cause: Incorrect connection of braking resistor.

Remedy: Check whether the braking resistor is properly connected and whether the braking unit is normal.
E093.1

Motor rotor locked		 Cause:
  • Excessive load or brake exception.
  • Low torque limit/current limit.
  • Auto-tuning not performed.
  • AC drive model setting error.

Remedy:
  • Ensure that the motor load is within a reasonable range.
  • Set the torque limit as appropriate.
  • Perform auto-tuning before running.
  • Set the AC drive model correctly.
E093.2

Motor stall		 Cause:
  • Encoder interference/wire breakage.
  • Encoder PPR error or loose connection.
  • Auto-tuning not performed.
  • AC drive model error.

Remedy:
  • Check the encoder for interference.
  • Check whether the encoder is connected reliably.
  • Set the rated parameters of the motor correctly, and perform dynamic auto-tuning if possible.
  • Set the AC drive model correctly.
E093.4

Current control exception		 Cause:
  • Output phase loss.
  • Encoder interference or encoder wire breakage.
  • Sudden and large drop in bus voltage.
  • Auto-tuning not performed.

Remedy:
  • Check the motor for phase loss.
  • Check whether the encoder is normal.
  • Keep the grid voltage stable.
  • Input motor parameters correctly and perform auto-tuning.
E094.1
Inconsistency between calculated and set numbers of pole pairs		 Cause:
Incorrect setting of the number of motor pole pairs.

Remedy:
  • Set A9-02 only when the number of motor pole pairs exceeds 12.
E094.2
Motor power, voltage, and current matching error		 Cause:
Motor power, voltage, and current mismatch.

Remedy:
  • Set the motor parameters correctly.
E094.3
No-load current range error		 Cause:
Incorrect motor no-load current range.

Remedy:
  • Check the motor nameplate parameters and ensure correct model setting of the AC drive.
E094.4
Inconsistency between Lm, I0 and rated voltage		 Cause:
Inconsistency with rated voltage caused by separate modification of no-load current or mutual inductance.

Remedy:
  • Set motor nameplate parameters correctly and perform auto-tuning.
E094.5
Rotor resistance range exception		 Cause:
Rotor resistance range out-of-range.

Remedy:
  • Check whether the motor is rotating during auto-tuning.
  • Check whether the motor nameplate parameters and AC drive model setting are correct.
E094.7
Mismatch between the numbers of pole pairs of the resolver and synchronous motor		 Cause:
Incorrect number of resolver pole pairs of synchronous motor.

Remedy:
  • Ensure that the number of pole pairs of the synchronous motor is divisible by the number of resolver pole pairs.
E159.1
Auto reset failure		 Cause:
Auto reset disabled.

Remedy:
  • Check H2-20 to H2-39 to see whether auto reset is disabled.
E160.1
Modbus communication fault		 Cause:
Modbus communication timeout.

Remedy:
  • Check whether the RS-485 communication cable is correctly connected.
  • Check whether the setting of FD-04 and the PLC communication cycle are proper.
E161.1
CANopen communication fault		 Cause:
CANopen communication timeout.

Remedy:
  • Check whether the CAN communication cable is correctly connected.
  • Check parameters FD-15 to FD-17 for further action.
E161.2
CANopen PDO mapping inconsistency		 Cause:
Inconsistency between PDO mapping configured for CANopen and the actual mapping.

Remedy:
  • Check the PDO mapping of parameters in group AF.
E162.1
CANlink communication fault		 Cause:
CANlink heartbeat timeout.

Remedy:
  • Check whether the CAN communication cable is correctly connected.
  • Check parameters FD-15 to FD-17 for further action.
E162.2
CANlink station number conflict		 Cause:
CANlink station number conflict.

Remedy:
  • Modify the CAN station numbers by using FD-13.
E164.1
Expansion card fault		 Cause:
Expansion card fault.

Remedy:
  • Check communication of the expansion card.
E174.1
Wire breakage (HDI1)		 Cause:
HDI1 wire breakage.

Remedy:
  • Check HDI wiring.
E174.3
Wire breakage (AI1)		 Cause:
AI1 wire breakage.

Remedy:
  • Check AI1 wiring.
E174.4
Wire breakage (AI2)		 Cause:
AI2 wire breakage.

Remedy:
  • Check AI2 wiring.
E174.5
Wire breakage (AI3)		 Cause:
AI3 wire breakage.

Remedy:
  • Check AI3 wiring.

How to Read MD520 Faults via LCD Keypad & Software

The MD520 offers superior diagnostic capabilities compared to older models. In 2026, utilizing the advanced interface options is key to rapid troubleshooting.

  • LCD Keypad Descriptions: If your MD520 is equipped with the advanced LCD keypad, it will often display a short text description alongside the “Err” code. This allows you to immediately identify issues like “Output Phase Loss” or “STO Request” without needing a manual.
  • InoDriveShop Analysis: For complex issues, connecting to the InoDriveShop PC software allows you to view the “Fault Snapshot.” This feature captures the drive’s exact state (Bus Voltage, Output Current, I/O Status) at the millisecond the error occurred.
  • STO Diagnostics: Since the MD520 supports Safe Torque Off, specific faults relate to safety circuits (e.g., channel mismatch). Viewing internal monitoring parameters allows you to verify if the safety inputs (H1/H2) are synchronized.

Frequently Asked Questions (FAQ)

Q: What is the difference between a Warning and a Fault?

A: A Warning (often displayed as ‘A’ or ‘ALm’ codes) alerts you to a condition that requires attention—such as high heatsink temperature—but permits operation. A Fault (displayed as ‘Err’ codes) triggers the protection mechanism, immediately stopping the output and engaging the brake (if configured).

Q: How do I reset an Inovance MD520 fault?

A: You can reset the drive using the following methods:

  1. Pressing the STOP/RESET button on the keypad.
  2. Toggling a Digital Input (DI) programmed for the “Reset” function.
  3. Sending a reset command via Fieldbus (EtherCAT, PROFINET, or Modbus) or via the InoDriveShop software.

Q: Where is the fault history stored?

A: The MD520 retains a detailed history of the last 3 faults in parameters U0-00 through U0-02. Detailed snapshot data (frequency, current, voltage at the time of the fault) is stored in the subsequent U0 group parameters.

Comments

Post a Comment

Popular posts from this blog

Allen Bradley Kinetix 5500 Drive Fault Codes List

Complete guide to Allen Bradley Kinetix 5500 fault codes. Troubleshoot FLT codes, Single-Cable (DSL) feedback errors, shared bus faults, and perform diagnostics via Studio 5000. Kinetix 5500 Fault Codes Reference Table Kinetix 5500 Fault Codes Reference Table Kinetix 5500 Fault Codes Reference Table Fault Code and Meaning Cause and Remedy FLT S03 – MTR OVERSPEED FL Motor Overspeed Factory Limit Fault Cause: Motor speed has exceeded 125% of its maximum speed. Remedy: Check control loop tuning. FLT S04 – MTR OVERSPEED UL Motor Overspeed User Limit Fault Cause: Motor speed has exceeded motor overspeed user limit. Remedy: Check control loop tuning. Increase the Motor Overspeed UL attribute value. FLT S05 – MTR OVERTEMP FL Motor Overtemperature Factory Limit Fault Cause: Calculations based ...
Read more

Danfoss VACON 100 FLOW Drive Fault Codes List

Access the complete reference guide for Danfoss VACON 100 FLOW drive fault codes. Learn to diagnose Multipump communication errors, dry run faults, and use Vacon Live software. VACON 100 FLOW Fault Codes Reference Table VACON 100 FLOW Faults and Alarms VACON 100 FLOW - Fault Tracing Fault Code and Meaning Cause and Remedy Fault Code 1, ID 1 Overcurrent (Hardware Fault) Cause: There is too high a current (> 4 × IH) in the motor cable. a sudden heavy load increase a short circuit in the motor cables the motor is not the correct type the parameter settings are not properly made Remedy: Check the loading. Check the motor. Check the cables and connections. Make an identification run. Set the acceleration time longer (P3.4.1.2 and P3.4.2.2). Fault Code 1, ID 2 Overcurrent (Software Fault...
Read more

ABB ACH580 Drive Fault Codes List

Access the complete reference guide for ABB ACH580 HVAC drive fault codes. Learn to diagnose issues via the Hand-Off-Auto panel, BACnet integration, and Fireman’s Override. The ABB ACH580 is the industry-standard flagship drive for HVACR applications. Designed to control air handling units, cooling towers, and chillers, it ensures critical comfort and safety in buildings. When a malfunction occurs, the dedicated Hand-Off-Auto (HOA) control panel displays a 4-digit code alongside plain-text diagnostics, often integrated directly into the Building Management System (BMS). This guide provides the most updated reference to help you interpret these codes and maintain building environmental standards. ACH580 Fault Codes Reference Table Use the search bar below or browse the table to identify your specific error code: ABB ACH580 Drive Fault Codes List ABB ACH580 Drive Fault Codes List Fault Code and Meaning Cause and Remedy A2B1...
Read more