Inovance IS810N Servo Drive Fault Codes List

A comprehensive guide to Inovance IS810N multi-axis servo fault codes. Troubleshoot common DC bus errors, EtherCAT synchronization, and module failures via InoDriverShop.

Inovance IS810N Fault Codes Reference Table

Below is the complete list of fault codes, sub-codes, and troubleshooting actions associated with the IS810N multi-axis series.

Inovance IS810N Servo Drive Fault Codes List

Inovance IS810N Servo Drive Fault Codes List

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.
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.
 

How to Read IS810N Faults via InoDriverShop

Because the IS810N operates as a cohesive multi-axis system, a fault in one axis (like an overload) can be caused by issues in the power supply module. In 2026, using the InoDriverShop PC software is the standard for system-level diagnosis.

  • Sub-Code Precision: The LED display on the IS810N modules allows you to toggle between the main fault code (e.g., E108) and the sub-code (e.g., .1). InoDriverShop displays the full text description immediately (e.g., “E108.1: Parameter Storage Failure”), saving you from cross-referencing manuals.
  • Synchronization Analysis: For EtherCAT applications, “Sync Lost” (E1.E08) is a common stop condition. The software allows you to monitor the “Distributed Clock (DC)” jitter and sync signals to determine if the issue stems from the cable, the Master PLC cycle time, or electromagnetic interference.
  • Common DC Bus Monitoring: Since all axes share one rectifier, a “Main Circuit Undervoltage” (E12.00) on one drive might mean the shared Power Supply Unit (PSU) is failing or overloaded. The software lets you trend the DC bus voltage of the entire system to pinpoint the root cause.

Frequently Asked Questions (FAQ)

Q: What is the difference between an Alarm and a Fault?

A: An Alarm (typically displayed with ‘A’ codes or specific warnings like “Battery Low”) indicates a condition that requires maintenance but allows the axis to finish its motion profile. A Fault (displayed as ‘E’ codes) immediately disables the power stage (STO) of the affected axis (and often linked axes) to prevent mechanical collision.

Q: How do I reset an Inovance IS810N fault?

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

  1. Sending a Fault Reset Command (Control Word Bit 7) via the EtherCAT/PROFINET master.
  2. Pressing the SET button on the specific axis module’s keypad.
  3. Cycling the 24V Control Power (required for critical internal errors like E130 FPGA Faults).

Q: Where is the fault history stored?

A: The IS810N stores the last 10 fault records in parameter group H02 (H02-00 to H02-09). The history includes not just the code, but the timestamp and critical drive states (current, position, speed) at the moment of failure.

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