Inovance SV670P Servo Drive

Fault Code and MeaningCause and Remedy
E108.0
Parameter write error

Cause: Parameter values cannot be written to e2prom (error during parameter-writing).


Remedy: Modify a certain parameter, power off and on the servo drive again and check whether the modification is saved. If the modification is not saved and the fault persists after repeated power cycling, replace the servo drive.
E108.1
Parameter read error

Cause: Parameter values cannot be read from e2prom (read operation abnormal).


Remedy: Modify a certain parameter, power off and on the servo drive again and check whether the modification is saved. If the modification is not saved and the fault persists, replace the servo drive.
E108.2
Check on data written in e2prom failed

Cause: The check on the data written in e2prom fails.


Remedy: Modify a certain parameter, power off and on the servo drive again and check whether the modification is saved. If not saved and fault persists, replace the servo drive.
E108.3
Check on data read in e2prom failed

Cause: The check on the data read in e2prom fails (error during reading).


Remedy: Modify a certain parameter, power off and on the servo drive again and check whether the modification is saved. If not saved and fault persists, replace the servo drive.
E108.4
Single data stored too many times

Cause: Single data is stored too frequently, which may damage e2prom over time.


Remedy:

  • If caused by manually modifying a parameter/object dictionary, reset the fault (stop frequent manual modification).

  • Check H0b.90 (parameter address) and H0b.91 (internal variable if = 15).

  • If the host controller program frequently writes parameters via SDO, modify the program to stop this behavior.


E110.0
Frequency-division pulse output setting error

Cause: The number of frequency divisions (quadrupled) exceeds the motor revolutions.


Remedy: Adjust the value of H05.17 on the basis of the motor revolutions.
E120.3
The motor and drive do not match in the power

Cause: The motor and drive do not match in the rated power.


Remedy:

  • Replace the motor or drive.

  • If they can work properly despite mismatch, set bit4 of H0A.71 to 1 to shield the alarm.


E121.0
Invalid S-ON command

Cause: A redundant S-ON signal is sent when some auxiliary functions are used (Communication S-ON active while drive enabled internally).


Remedy: Deactivate the DI assigned with FunIN.1 (both hardware DI and virtual DI). Check DI functions H0d.02, H0d.03, H0d.12.
E122.0
Multi-turn absolute encoder setting error

Cause: The motor does not match the absolute position mode or the motor code is set improperly.


Remedy:

  • Check motor nameplate to see if configured with multi-turn absolute encoder.

  • Reset H00.00 (motor code) according to nameplate or use a suitable motor.


E122.6
Absolute function setting error of 2nd encoder

Cause: The motor does not match the absolute position mode.


Remedy: Set H0F.02 to 0.
E510.0
Frequency division pulse output overspeed

Cause: Single-channel output pulse frequency exceeds hardware limit (4 MHz) or MCU detects excessive pulse increment from FPGA.


Remedy:

  • Decrease H05.17 (encoder frequency-division pulses) to drop below the frequency upper limit.

  • If input pulse frequency exceeds 2 MHz or there is interference: Decrease input frequency or take anti-interference measures (STP cable, filter parameters H0A.24/H0A.30).


E600.0
Inertia auto-tuning failure

Cause: Vibration cannot be suppressed, auto-tuned values fluctuate, mechanical couplings are loose, or load inertia is too large.


Remedy:

  • Rectify mechanical faults (loose couplings) and perform inertia auto-tuning again.

  • Enable vibration suppression.

  • Increase maximum operating speed, reduce acceleration/deceleration time, and shorten stroke of lead screw during ETune.


E601.0
Homing timeout

Cause: The homing time exceeds the time set by H05.35.


Remedy: Increase the value of H05.35 (Time limit for homing).
E601.1
Homing switch error

Cause: The homing switch is set improperly (limit signals, deceleration point, or Z signal issues).


Remedy:

  • Check if hardware DI wiring matches H03 group settings.

  • Check condition of Z signal if used.

  • Set the position of the physical switch properly.

  • Increase H05.35 or adjust 6099-01h if speed is too low.


E601.2
Homing method setting error

Cause: The homing method value is too large/invalid.


Remedy: Change the value of H22.70 (technology segment homing) to a valid mode.
E730.0
Encoder battery voltage low

Cause: The voltage of the absolute encoder battery is lower than 3.0 V.


Remedy: Measure the battery voltage and use a new battery with the matching voltage.
E730.1
Inovance 2nd encoder battery voltage low

Cause: Inovance 2nd encoder battery voltage is lower than 3.0 V.


Remedy: Measure the battery voltage and use a new battery with the matching voltage.
E831.0
AI2 zero offset too large

Cause: Wiring incorrect, interference, or servo drive faulty.


Remedy:

  • Use shielded twisted pairs, shorten circuit length, increase AI2 input filter time.

  • Disconnect AI1/AI2 and measure voltage. If actual voltage < 0.5V but fault persists, replace drive.


E834.1
AI1 overvoltage

Cause: Input voltage is too high (>11.5 V), wiring error, or interference.


Remedy:

  • Use shielded twisted pairs, increase filter time.

  • Adjust the input voltage to a value lower than 11.5 V.


E834.2
AI2 overcurrent

Cause: Input current too large, wiring error, or interference.


Remedy:

  • Use shielded twisted pairs, increase filter time.

  • Adjust the input current to a value lower than 21 mA.


E900.0
Emergency braking

Cause: The DI function 34 (EmergencyStop) is triggered.


Remedy: Check the operation mode and clear the active DI braking signal without affecting safety performance.
E902.0
DI function disabled

Cause: DI function parameters (H03 group) are set to invalid values.


Remedy: Set DI function parameters to valid values.
E902.1
DO function disabled

Cause: DO function parameters (H04 group) are set to invalid values.


Remedy: Set DO function parameters to valid values.
E902.2
Invalid setting for torque reach

Cause: DO parameters set for torque reach in torque control mode are invalid (H07.22 <= H07.23).


Remedy: Set H07.22 to a value higher than that of H07.23.
E908.0
Model identification failure

Cause: Model ID check word incorrect or parameters not written before delivery.


Remedy: Set H01-72 to 1 to disable model identification temporarily.
E909.0
Motor overload warning

Cause: Accumulative heat of motor reaches warning threshold (90%). Causes include wiring, heavy load, gain settings, or stalled motor.


Remedy:

  • Check wiring (use proper cables).

  • Reduce load, increase accel/decel time, or use higher capacity drive/motor.

  • Check H0b.12 (average load rate).

  • Adjust gains if vibration occurs.

  • Set motor/drive model properly (H00.05, H01.10).

  • Eliminate mechanical factors causing stall.


E910.0
Control circuit overvoltage

Cause: Input voltage in control circuit cable is out of range.


Remedy: Check input voltage (220V drive: 198-264V; 380V drive: 342-484V). Re-connect or replace cables.
E920.0
Regenerative resistor overload

Cause: Accumulative heat of regenerative resistor exceeds set value.


Remedy:

  • If external resistor used: Check connection P⊕ and C. Ensure resistance is not infinite.

  • If built-in resistor used: Ensure jumper between P⊕ and D is connected.

  • Check H02.25 setting (1=natural cooling, 2=forced air).

  • Select proper resistor size. Set H02.27 correctly.

  • Check main circuit input voltage.


E922.0
Resistance of external regenerative resistor too small

Cause: H02.27 is lower than H02.21 (permissible min resistance).


Remedy: Replace with resistor matching the drive specifications, or set H02.27 to a value consistent with the actual resistor used.
E924.0
Braking junction temperature too high

Cause: Regenerative transistor temperature exceeds threshold (H0A.49).


Remedy: Control the working conditions and usage of the regenerative transistor.
E941.0
Parameter modifications activated at next power-on

Cause: Parameters with “Effective time” = “Next power-on” were modified.


Remedy: Power off and on the servo drive again.
E942.0
Parameter saved frequently

Cause: Number of parameters modified exceeds 200 at a brief interval.


Remedy: Check host controller program. For parameters not needing e2prom save, set H0C.13 to 0.
E950.0
Forward overtravel warning

Cause: DI function 14 (P-OT, positive limit switch) triggered or software limit reached.


Remedy:

  • Send reverse run command or rotate motor to deactivate P-OT.

  • Adjust forward soft limit value (H0A.40/41) or adjust motor stroke.


E952.0
Reverse overtravel warning

Cause: DI function 15 (N-OT, negative limit switch) triggered or software limit reached.


Remedy:

  • Send forward run command or rotate motor to deactivate N-OT.

  • Adjust reverse soft limit value or adjust motor stroke.


E954.0
Position command overflow

Cause: In PR mode, position command is beyond the limit.


Remedy: Change the value of the position command and the limit.
E956.0
Forward position reference overtravel in process segment

Cause: Position reference > H22.04 in process segment position mode.


Remedy: Reduce the position reference to a value lower than the setpoint of H22.06.
E958.0
Reverse position reference overtravel in process segment

Cause: Position reference < H22.06 (when running reversely) in process segment mode.


Remedy: Increase the position reference to a value greater than the setpoint of H22.06.
E971.0
Undervoltage warning for voltage drop protection

Cause: The bus voltage is lower than the undervoltage threshold.


Remedy: Check the power supply.
E980.0
Encoder algorithm error

Cause: An encoder algorithm error occurs.


Remedy: Check wiring. If fault persists after power cycling, replace the servo motor.
EA41.0
Torque fluctuation compensation failure

Cause: Auto-tuning torque fluctuation compensation failure.


Remedy: Turn off the torque fluctuation compensation function.
E101.0
System parameter error

Cause: Parameters in group H02 and above exceed the limit, or total number of parameters changed (often after software update).



Remedy:

  • Restore system parameters to default settings (H02.31 = 1) and write parameters again.

  • Check for instantaneous power failure during parameter save.

  • Increase power supply capacity if voltage drops (220V drive: 198V-264V range; 380V drive: 342V-484V range).

  • If caused by frequent host controller updates, change write mode.

  • If servo drive is faulty, replace it.


E101.1
Parameter error in group H00/H01

Cause: Parameter values in groups H00 or H01 exceed the limit (often after software update).



Remedy:

  • Set the servo drive model (H01.10) to a wrong value first, perform a power cycle.

  • Set the servo drive model back to the correct value and perform a power cycle.


E101.2
System parameter error

Cause: Address error in read/write operation after the number of parameters changes.



Remedy:

  • Read H0b.90 and H0b.91 to obtain abnormal parameter group.

  • Rectify the wrong values or restore factory settings.


E101.9
Parameter attribute initialization check error

Cause: Parameter attribute initialization check failed.



Remedy:

  • Check that H0A.99 = AA5C.

  • Power off and on several times.

  • If problem persists, replace the servo drive.


E102.0
FPGA communication establishment error

Cause: Communication between MCU and FPGA cannot be established.



Remedy:

  • Power off and on repeatedly.

  • If fault persists, replace the servo drive.


E102.1
FPGA initialization start error

Cause: FPGA failed to start.



Remedy:

  • Power off and on repeatedly.

  • If fault persists, replace the servo drive.


E102.8
FPGA and MCU version mismatch

Cause: Software versions of FPGA and MCU are inconsistent.



Remedy:

  • View versions via H01.01 (FPGA), H01.03 (MCU), H01.00 (CPU1).

  • Contact Inovance for technical support.

  • Update the FPGA or MCU software.


E104.1
MCU running timeout (MCU break down)

Cause: MCU Access timeout or Real-time communication error between MCU and FPGA.



Remedy:

  • Power off and on repeatedly.

  • If fault persists, replace the servo drive.


E104.2
FPGA running timeout (FPGA break down)

Cause: FPGA running timeout, failure, or handshaking error.



Remedy:

  • Power off and on repeatedly.

  • If fault persists, replace the servo drive.


E104.4
MCU command update timeout

Cause: Command calculation time is too long or encoder communication time set improperly.



Remedy:

  • Hide/disable unnecessary functions.

  • Replace the servo drive.


E120.0
Unknown encoder model

Cause: Detected encoder model does not comply with requirement or drive/motor code mismatch.



Remedy:

  • If using SV670P drive and 23-bit motor, set H00.00 to 14101.

  • Check servo drive code (H01.02) matches nameplate.

  • Check if motor power rating matches drive.

  • Replace unmatched products or rectify motor code.


E120.1
Unknown motor model

Cause: Motor model defined by H00.00 does not exist.



Remedy:

  • Check if H00.00 matches the used motor.

  • Rectify the value of H00.00.


E120.2
Unknown drive model

Cause: Servo drive model defined by H01.10 does not exist.



Remedy:

  • Disable servo drive model auto detection.

  • Set H01.10 to a proper value manually.


E120.5
Motor and drive current mismatch

Cause: Drive rated output is far higher than motor rated current (internal scale value abnormal).



Remedy:

  • Check if servo drive model is correct.

  • Replace the servo drive.


E120.6
FPGA and motor model mismatch

Cause: Motor model set improperly or encoder not supported by drive.



Remedy:

  • Check if FPGA software (H01.01) supports the motor model (H00.00).

  • Update FPGA software to support the motor.


E120.7
Model check error

Cause: Model parameter CRC check failed; parameter not identified.



Remedy:

  • Write the model parameter again.


E120.8
Junction temperature parameter check error

Cause: Junction temperature parameter CRC check failed.



Remedy:

  • Rewrite the junction temperature parameter.


E122.1
Different DIs allocated with the same function

Cause: Multiple DIs assigned same function or DI function No. exceeds limit.



Remedy:

  • Check group H03 for repetitive numbers and change them.

  • Restore system parameters to default (H02.31 = 1) and restart drive.


E122.2
Different DOs assigned with the same function

Cause: DO function No. exceeds maximum allowed.



Remedy:

  • Check H04.00, H04.02, H04.04.

  • Set the correct DO function No.


E122.3
Upper limit in the rotation mode invalid

Cause: Upper limit of mechanical single-turn position exceeds 2^31 in absolute rotation mode.



Remedy:

  • Check mechanical gear ratio and limits.

  • Reset mechanical gear ratio to ensure limit does not exceed 2^31 (when H02.01=2).


E122.4
Different VDIs assigned with the same function

Cause: Duplicate functions on VDIs or VDI function No. exceeds limit.



Remedy:

  • Check group H17 for repetitive numbers and change them.

  • Restore system parameters to default (H02.31=1) and restart.


E122.5
DI and VDI assigned with the same function

Cause: Same function assigned to both a DI and a VDI.



Remedy:

  • Check groups H03 and H17. Assign different function numbers.

  • Re-energize control circuit or send “RESET” signal to activate.


E122.7
Fully closed-loop parameter setting error

Cause: Incorrect setting when fully closed-loop is used.



Remedy:

  • If H0F.00 is not 0, set H02.01 to 2 (absolute position rotation mode).


E122.9
Fully closed-loop function pin conflict

Cause: Frequency division output pin conflicts with fully closed loop second encoder pin.



Remedy:

  • Check H05.38 and H0F.03.

  • Disable frequency-division output.


E126.0
Process segment number error

Cause: Process segment number (H22.00) is not 0-15 or 1000.



Remedy:

  • Write value 0…15 to H22.00 in the technology segment mode.


E126.1
Process segment internal operation mode error

Cause: Technology segment operation mode is not 0, 1, 2, 3, 7, or 8.



Remedy:

  • Set the technology segment operation mode to 0, 1, 2, 3, 7, or 8.


E126.2
Position reference type error

Cause: Position reference type is not 00 (Absolute) or 10 (Incremental).



Remedy:

  • Set the position reference type to 00 or 10.


E136.0
Encoder ROM motor parameter check error

Cause: ROM parameters missing or inconsistent. Cable issues.



Remedy:

  • Check if drive and motor models match (SV670P series).

  • Use Inovance encoder cable; ensure secure connection.

  • Route encoder cables separately from power cables (R/S/T, U/V/W).

  • If fault persists after restart, replace servo drive.


E136.1
Encoder ROM motor parameter read error

Cause: Cable disconnected or communication interference.



Remedy:

  • Check encoder cable connection and looseness due to vibration.

  • Connect cables securely.

  • If fault persists after restart, replace servo drive.


E150.0
STO safety state

Cause: STO input protection applies (Safety state active).



Remedy:

  • No corrective action needed if STO is intentional. Clear fault when STO terminal is normal.

  • Check 24V power supply for STO.

  • Tighten loose cables.

  • If fault persists, replace servo drive.


E150.1
STO input abnormal

Cause: Single-channel input of STO ineffective, or power supply abnormal.



Remedy:

  • Check 24V STO power supply stability.

  • Check for loose cables.

  • If input resistor is abnormal (drift), replace servo drive.


E150.2
Buffer 5V voltage detection error

Cause: 5V supply to STO Buffer is abnormal (under/over voltage).



Remedy:

  • Restart drive. If fault persists, replace servo drive.


E150.3
STO input circuit hardware diagnosis failure

Cause: Short circuit on optocoupler of STO hardware.



Remedy:

  • Power cycle 24V supply. If E150.3 persists, replace servo drive.


E150.4
PWM buffer hardware diagnosis failure

Cause: Error on PWM Buffer IC during initialization.



Remedy:

  • Power cycle 24V supply. If E150.4 persists, replace servo drive.


E201.0
Phase-P overcurrent

Cause: High current in DC-AC positive pole. Caused by improper gains, encoder wiring, regen resistor short, or faulty drive.



Remedy:

  • Modify motor/current loop/speed loop parameters to stop oscillation.

  • Re-solder, tighten, or replace encoder cable.

  • Check external regenerative resistor wiring (Terminals P and C).

  • Disconnect motor cable; if fault persists on power-up, replace servo drive.


E201.1
Phase-U overcurrent

Cause: High current in Phase-U. Loose cables, short to ground, short between phases.



Remedy:

  • Tighten loose cables on U/V/W.

  • Measure insulation resistance (U/V/W to PE). Replace motor if insulation poor.

  • Check for short circuits or burrs in wiring.

  • Measure resistance balance among UVW phases. Replace motor if unbalanced.


E201.2
Phase-V overcurrent

Cause: High current in Phase-V.



Remedy:

  • Tighten loose cables.

  • Check insulation resistance (U/V/W to PE).

  • Check for wiring shorts/burrs.

  • Replace motor if resistance unbalanced.


E201.4
Phase-N overcurrent

Cause: High current in DC-AC negative pole. Improper gains, encoder issues, braking current superposition.



Remedy:

  • Adjust gains.

  • Re-solder or replace encoder cable.

  • Check regenerative resistor wiring.

  • Increase acceleration/deceleration time.

  • If fault persists with motor disconnected, replace servo drive.


E208.2
Encoder communication timeout

Cause: Drive fails to receive encoder data (3 cycles). Cable issues, interference, or faulty hardware.



Remedy:

  • Check if motor model is correct.

  • Check encoder cable connection, length, and specification.

  • Check if encoder version (H00.04) is set properly.

  • If servo drive is faulty, replace it.


E208.4
FPGA current loop operation timeout

Cause: Current loop time exceeds threshold.



Remedy:

  • Disable unnecessary functions to reduce operating load of the current loop.


E210.0
Short-to-ground detection error

Cause: Abnormal phase current or bus voltage during self-test. Cables or motor shorted to ground.



Remedy:

  • Check power cables (U/V/W) for short to ground. Replace cables.

  • Measure motor insulation resistance. Replace motor if faulty.

  • If fault persists with cables disconnected, replace servo drive.

  • Reduce motor speed if “generating status” is detected during power-on.


E234.0
Runaway

Cause: Feedback direction opposite to reference. Wrong phase sequence or encoder error.



Remedy:

  • Connect U/V/W cables in the correct phase sequence.

  • Power cycle the drive.

  • Check encoder model, type, and cable connection. Match drive and motor correctly.


E320.0
Resistor fault

Cause: Regenerative resistor overloaded.



Remedy:

  • Check if large regenerative current is present due to high bus voltage.

  • Ensure motor is not driven reversely.

  • Replace the servo drive.


E400.0
Main circuit overvoltage

Cause:

The DC bus voltage between P⊕ and N⊖ exceeds the overvoltage threshold.

(220V Drive Threshold: 420V | 380V Drive Threshold: 760V)



Remedy:

  • Check if input voltage is too high. Replace or adjust the power supply to specified range.

  • If power supply is unstable or affected by lightning, connect a surge protection device.

  • If using built-in regenerative resistor, check jumper between P⊕ and D. If external, check resistance.

  • If resistance of external regenerative resistor is too large, replace with recommended value and set H02.26/H02.27 correctly.

  • If motor is in abrupt accel/decel, increase the acceleration/deceleration time.

  • If bus voltage sampling deviates greatly (H0b.26), contact Inovance technical support.

  • If fault persists after power cycling, replace the servo drive.


E410.0
Main circuit undervoltage

Cause:

The DC bus voltage between P⊕ and N⊖ is lower than the undervoltage threshold.

(220V Drive Threshold: 200V | 380V Drive Threshold: 380V)



Remedy:

  • Check if power supply is unstable or power failure occurs; increase capacity of power supply.

  • If instantaneous power failure occurs, increase power supply capacity.

  • If power supply voltage drops during operation due to other devices, increase power capacity.

  • Check if 3-phase drive is connected to single-phase (leading to phase loss). Replace/connect cables correctly (R, S, T).

  • If fault persists after repeated power cycling, replace the servo drive.


E410.1
Main circuit de-energized

Cause:

The power supply is disconnected during operation.



Remedy:

  • Check power input specifications and measure voltage; Increase capacity of the power supply.

  • Check if main circuit wired correctly (phase loss detection); Replace cables and connect R, S, T correctly.

  • Check if bus voltage (H0b.26) is too low; If fault persists, replace the servo drive.


E420.0
Main circuit phase loss

Cause:

Phase loss occurs on the three-phase servo drive.



Remedy:

  • Check if 3-phase input cables are connected improperly; Connect main circuit cables correctly.

  • If single-phase supply used for 3-phase drive (allowed for 0.75kW if H01.02=5): If voltage is within range, set H0A.00 to 2 (Inhibit phase loss fault). If not, adjust power supply.

  • Check if 3-phase supply is unbalanced or voltages too low.

  • If fault persists after power cycling, replace the servo drive.


E420.1
Main circuit PL signal detection error

Cause:

Signal detection error related to phase loss.



Remedy:

  • Check cable connections between power supply and R/S/T terminals.

  • Verify power supply balance and voltage levels.

  • If single-phase is used intentionally, verify parameter H0A.00 settings.

  • If fault persists, replace the servo drive.


E430.0
Control circuit power supply undervoltage

Cause:

Control circuit voltage is below threshold (190V for 220V drive; 350V for 380V drive).



Remedy:

  • Power off and on again. If unexpected failure occurs, ensure stable power supply.

  • Check input voltage of control circuit (L1C, L2C); Increase power supply capacity.

  • Check for poor contact in cables; Re-connect or replace cables.


E500.0
Motor overspeed

Cause:

The actual speed of the motor exceeds the overspeed threshold.



Remedy:

  • Check phase sequence (U/V/W); Connect cables in correct sequence.

  • Check if H0A.08 (Overspeed threshold) is set improperly; Reset according to mechanical requirements.

  • If input reference causes overspeed: Reduce position reference increment, increase accel/decel ramp, or lower speed limit.

  • If motor speed overshoots: Adjust gains or mechanical operating conditions.

  • If fault persists after power cycling, replace the servo drive.


E500.1
Speed feedback overflow

Cause:

The FPGA speed measurement overflows.



Remedy:

  • Check U/V/W sequence; Connect cables correctly.

  • If motor speed overshoots, adjust gains.

  • If speed measurement abnormal: Check encoder version (H00.04), replace encoder cable, or install magnetic ring/shielding for interference.


E500.2
Velocity feedback error 2

Cause:

Communication error occurred between boards of the drive.



Remedy:

  • If alarm persists after repeated power off and on, replace the servo drive.


E602.0
Angle auto-tuning error

Cause:

Unusual jitter occurs on the encoder feedback during angle auto-tuning.



Remedy:

  • Check if encoder communication is being disturbed.

  • Check the wiring of the encoder.


E602.2
Wrong phase sequence detected during angle auto-tuning

Cause:

A wrong U/V/W phase sequence is detected during angle auto-tuning.



Remedy:

  • Exchange cables of any two phases among U/V/W and perform auto-tuning again.


E605.0
Bootstrap overspeed

Cause:

The motor speed exceeds the rated speed when the servo drive (size A/B) is switched on.



Remedy:

  • Check if drive is enabled when motor is being driven.

  • Switch on the drive when the motor is at a standstill.


E620.0
Motor overload

Cause:

The accumulative heat of the motor reaches the fault threshold.



Remedy:

  • Check motor/encoder wiring. Connect according to diagram.

  • If load is too heavy (H0b.12 > 100%): Use higher capacity drive/motor or reduce load.

  • If accel/decel too frequent (High Load Inertia H08.00): Increase accel/decel time.

  • If gains improper (vibration/noise): Adjust gains.

  • Check servo/motor model settings (H00.05, H01.10).

  • If motor stalled due to mechanical factors: Eliminate mechanical jam.

  • If fault persists after cooling (30s) and restart, replace servo drive.


E625.0
Brake abnormality enabled

Cause:

The brake fails when it is released (Motor shaft held while release signal active).



Remedy:

  • Check the brake wiring.

  • Replace the Brake motor.


E626.0
Brake abnormality enabled

Cause:

The brake fails when it closes (Motor shaft not held tightly).



Remedy:

  • Check the brake wiring.

  • Replace the Brake motor.


E630.0
Motor stall

Cause:

Actual speed < 10rpm but torque reference reaches limit for time defined in H0A.32.



Remedy:

  • Check U/V/W for phase loss/wire break. Re-connect cables.

  • Check number of pole pairs and angle auto-tuning (H00.28). Modify parameters.

  • Check if communication commands (EtherCAT) are disturbed/jittery. Check comms lines.

  • Check if motor is stalled due to mechanical factors (stuck/eccentric).


E631.1
Motor brake fault

Cause:

The brake circuit is faulty; 24V power or brake not connected.



Remedy:

  • Turn off the brake switch H02.16.

  • Connect the brake cable and 24 V power supply cable.

  • Replace the motor.


E631.2
P-MOS open circuit

Cause:

P-MOS open circuit occurred on the brake circuit.



Remedy:

  • Turn off the brake switch H02.16.

  • Replace the motor.


E631.3
N-MOS open circuit

Cause:

N-MOS open circuit occurred on the brake circuit.



Remedy:

  • Turn off the brake switch H02.16.

  • Replace the motor.


E631.4
P-Mos short-circuited

Cause:

The P-Mos in the brake circuit is short-circuited.



Remedy:

  • Replace the servo drive.


E631.5
N-Mos short-circuited

Cause:

The N-Mos in the brake circuit is short-circuited.



Remedy:

  • Replace the servo drive.


E640.0
IGBT junction temperature too high

Cause:

IGBT junction temperature reaches threshold defined by H0A.18.



Remedy:

  • Measure ambient temperature; Improve cooling conditions.

  • If drive restarted repeatedly after overload: Wait 30s before reset, increase drive/motor capacity, or reduce load.

  • Check if fan works properly; Replace servo drive if damaged.

  • Check installation direction and clearance.

  • If fault persists 5 mins after power-off, replace servo drive.


E640.1
Diode overtemperature

Cause:

Temperature of flywheel diode reaches threshold defined by H0A.18.



Remedy:

  • Measure ambient temperature; Improve cooling conditions.

  • Avoid repeated restarts after overload; Reduce load or increase capacity.

  • Check fan operation.

  • Check installation clearance.

  • If fault persists, replace servo drive.


E650.0
Servo drive overtemperature

Cause:

Temperature of servo drive power module is higher than overtemperature threshold.



Remedy:

  • Improve cooling conditions.

  • Check fault records; Change reset method (wait 30s); Reduce load.

  • Check fan operation; Replace drive if faulty.

  • Check installation direction/clearance.

  • If fault persists, replace servo drive.


E660.0
Motor overtemperature

Cause:

The temperature of the air-cooled motor is too high.



Remedy:

  • Cool the motor down.


E660.0
Motor overtemperature

Cause: The temperature of the air-cooled motor is too high.



Remedy:

  • Measure whether the temperature of the air-cooled motor is too high.

  • Cool the motor down.

  • Stop the servo drive for at least 30s before further operations.


E661.0
STune failure


Cause: During STune operation, the gain drops to the lower limit, stiffness <= 10.



Remedy:

  • Set the notch manually when vibration cannot be suppressed automatically.

  • Modify the electronic gear ratio to improve the command resolution.

  • Increase the command filter time constant in the “Parameter configuration” interface.

  • Check the machine for cyclic fluctuation.




Cause: Check whether resonance that occurred during ITune operation cannot be suppressed.



Remedy:

  • Set the notch manually.

  • Modify the electronic gear ratio to improve command resolution or increase filter time constant.

  • Check whether the machine suffers from periodic fluctuation.

  • Set H09.58 to 1 to clear resonance suppression parameters, and perform STune again.



E662.0
ETune failure


Cause: During ETtune operation, the gain drops to the lower limit (Position loop < 5, Speed loop < 5, Model loop < 10).



Remedy:

  • Set the notch manually when vibration cannot be suppressed automatically.

  • Modify the electronic gear ratio to improve command resolution or increase filter time constant.

  • Increase the value of H09.11 as appropriate.

  • Check whether the machine suffers from periodic fluctuation.

  • Check whether the positioning threshold is too low. Increase the reference acceleration/deceleration time.




Cause: Check whether resonance that occurred during ETune operation cannot be suppressed.



Remedy:

  • Set the notch manually.

  • Modify the electronic gear ratio to improve command resolution or increase filter time constant.

  • Check whether the current of the machine fluctuates periodically.



E663.0
ITune failure

Cause: Check whether resonance that occurred during ITune operation cannot be suppressed.



Remedy:

  • Set the notch manually when vibration cannot be suppressed automatically.

  • Modify the electronic gear ratio to improve command resolution or increase filter time constant.

  • Check whether the machine suffers from periodic fluctuation.

  • Increase the value of H09.11 as appropriate.


E664.0
Excessive system resonance

Cause: Resonance occurs on the servo system and the torque fluctuation amplitude is higher than the value of H09.54.



Remedy:

  • Check whether the inertia ratio or loop gain parameters are set properly.

  • Check whether resonance parameters are set properly.

  • Increase the value of H09.54 or set H09.54 to 0 to disable this function.


E731.0
Encoder battery failure


Cause: The battery is not connected during power-off.



Remedy:

  • Set H0d.20 to 1 to clear the fault.




Cause: The encoder battery voltage is too low (< 2.9V).



Remedy:

  • Use a new battery with the matching voltage.



E733.0
Encoder multi-turn counting error

Cause: The encoder is faulty.



Remedy:

  • Set H0d.20 to 2 to clear the fault.

  • If E733.0 persists after restart, replace the motor.


E735.0
Encoder multi-turn counting overflow

Cause: A multi-turn counting overflow occurs on the absolute encoder (Forward revs > 32767 or Reverse revs > 32768).



Remedy:

  • This fault can be hidden if multi-turn position isn’t needed but position recording is required.

  • Check if rotation mode applies to occasions where only single-turn absolute position needs to be recorded.

  • Set H0d.20 to 2 to power on again. Perform homing if necessary.


E740.0
Encoder communication timeout

Cause: The encoder cable is not connected reliably. The communication between the servo drive and the encoder times out.



Remedy:

  • Check the encoder cable connections.

  • Check whether vibration on site is too strong, causing loose or damaged cables.

  • Replace with a new encoder cable. If fault persists, the original cable was likely damaged.

  • Check whether the encoder version (H00.04) is set properly.

  • Check whether the servo drive software version (H01.00) is correct.

  • Replace the servo motor.


E740.2
Absolute encoder communication error


Cause: The encoder is wired improperly.



Remedy:
  • Connect the encoder cables according to the correct wiring diagram.



Cause: The encoder cable is loosened.



Remedy:
  • Re-connect encoder cables and ensure encoder terminals are connected securely.



Cause: The encoder Z signal is being disturbed.



Remedy:

  • Use cables provided by Inovance or shielded twisted pair cables.

  • Route motor cables and encoder cables through different routes.

  • Ensure proper grounding of servo motor and drive.

  • Check connectors for good contact.




Cause: The encoder is faulty.



Remedy:

  • Replace with a new encoder cable.

  • If fault persists after cable replacement, replace the servo motor.




Cause: An error occurs on communication between servo drive and encoder.



Remedy:

  • Check whether H00.00 (Motor code) is set properly.

  • Check whether the encoder cable is connected properly.

  • Ensure proper grounding; wind a magnetic ring on the encoder cable to reduce interference.



E740.3
Absolute encoder single-turn calculation error

Cause: An encoder fault occurs.



Remedy:

  • Check whether the encoder version (H00.04) is proper.

  • Check whether the encoder cable is proper.

  • Replace the motor.


E740.6
Encoder data write error

Cause: An error occurs when writing the position offset after angle auto-tuning.



Remedy:

  • Replace with a new encoder cable.

  • If the fault persists after the encoder cable is replaced, the encoder may be faulty. Replace the servo motor.


E760.0
Encoder overtemperature

Cause: The temperature of the absolute encoder is too high.



Remedy:

  • Switch off the S-ON signal to wait for the encoder to cool down.


E765.0
Nikon encoder over-temperature or overspeed

Cause: The temperature of the absolute encoder is too high.



Remedy:

  • Switch off the S-ON signal to wait for the encoder to cool down.


E770.0
Pulse closed-loop scale fault – Phase-A

Cause: Fully-closed loop phase A input differential voltage is too low (< 2.5 V).



Remedy:

  • Adjust the fully-closed loop phase A input voltage.

  • Replace the external encoder or cable.


E770.1
Fully-closed loop input phase B wire breakage

Cause: Fully-closed loop phase B input differential voltage is too low (< 2.5 V).



Remedy:

  • Adjust the fully-closed loop phase B input voltage.

  • Replace the external encoder or cable.


E770.2
Fully-closed loop input phase Z wire breakage

Cause: Fully-closed loop phase Z input differential voltage is too low (< 2.5 V).



Remedy:

  • Adjust the fully-closed loop phase Z input voltage.

  • Replace the external encoder or cable.


E770.3
BISS communication protocol timeout

Cause: BISS encoder communication data is not transmitted back to the drive.



Remedy:

  • Check the wiring.

  • Set H0F.28, H0F.29 and H0F.30 according to the specifications of the BISS encoder.


E770.4
BISS communication CRC check error

Cause: BISS encoder communication data CRC check error (Interference).



Remedy:

  • Replace the cable with shielded twisted pairs.


E770.6
Fully closed-loop 2nd encoder initialization communication error


Cause: The encoder cable connections are incorrect or loosened.



Remedy:

  • Connect the encoder cables according to the correct wiring diagram.

  • Re-connect encoder cables and ensure encoder terminals are connected securely.




Cause: The servo drive is faulty.



Remedy:
  • Replace the servo drive.


E770.7
Fully closed-loop Inovance 2nd encoder communication error


Cause: The encoder is wired improperly.



Remedy:
  • Connect the encoder cables according to the correct wiring diagram.



Cause: The encoder cable is loosened.



Remedy:
  • Re-connect encoder cables and ensure encoder terminals are connected securely.



Cause: The encoder Z signal is being disturbed.



Remedy:

  • Use Inovance cables or shielded twisted pair.

  • Route cables properly.

  • Ensure grounding.




Cause: The encoder is faulty.



Remedy:
  • Replace with a new encoder cable. If fault persists, replace the servo motor.


E939.0
Motor power cable failure

Cause: Motor power cables are broken or not connected.



Remedy:

  • Check whether the power cables are disconnected or in poor contact. Re-connect the power cables.

  • Replace the servo motor.


E939.1
Phase-U power cable disconnected

Cause: Motor power cables disconnected (Phase U).



Remedy:

  • Check whether the power cables are disconnected or in poor contact. Re-connect the power cables.

  • Replace the servo motor.


E939.2
Phase-V power cable disconnected

Cause: Motor power cables disconnected (Phase V).



Remedy:

  • Check whether the power cables are disconnected or in poor contact. Re-connect the power cables.

  • Replace the servo motor.


E939.3
Phase-W power cable disconnected

Cause: Motor power cables disconnected (Phase W).



Remedy:

  • Check whether the power cables are disconnected or in poor contact. Re-connect the power cables.

  • Replace the servo motor.


E994.0
Station number conflict

Cause: CANlink station No. conflict.



Remedy:

  • Rectify the value of H0E.00.


EA33.0
Internal encoder read/write check error


Cause: The serial incremental encoder cable is disconnected or loose.



Remedy:

  • Check for wrong connection, disconnection and poor contact of the encoder cable.

  • Route the motor cable and encoder cable through different routes.




Cause: An error occurs when reading/writing the serial incremental encoder parameters.



Remedy:
  • If the fault persists after the servo drive is powered off and on repeatedly, the encoder is faulty. Replace the servo motor.


EA33.1
Fully closed-loop Inovance 2nd encoder data read/write error

Cause: Encoder parameters are abnormal.



Remedy:

  • Check for wrong connection, disconnection and poor contact of the encoder cable.

  • Route the motor cable and encoder cable through different routes.

  • If fault persists after power cycling, replace the servo motor. (Same solution as EA33.0).


EB00.0
Position deviation too large


Cause: U/V/W output phase loss or incorrect phase sequence on the servo drive.



Remedy:
  • Connect cables again according to the correct wiring diagram or replace the cables.



Cause: The servo drive U/V/W cables or the encoder cable is disconnected.



Remedy:
  • Connect the cables again. Ensure correct order at both ends. Replace with new cables if necessary.



Cause: The motor is stalled due to mechanical factors.



Remedy:
  • Eliminate the mechanical factors.



Cause: The gain values are too low.



Remedy:
  • Adjust the gain values manually or perform gain auto-tuning.



Cause: The position reference increment is too large.



Remedy:

  • CSP: Decrease position reference increment.

  • PP: Decrease value 6081h or increase acceleration/deceleration ramp.

  • HM: Decrease 6099.01h/6099.02h or increase acceleration/deceleration ramp.

  • Decrease the gear ratio.




Cause: The value of 6065h (H0A.10) is insufficient for the operating conditions.



Remedy:
  • Increase the setpoint of 6065h.



Cause: The servo drive/motor is faulty.



Remedy:
  • If the position reference is not 0 but the position feedback is always 0, replace the servo drive or motor.


EB00.1
Position deviation overflow


Cause: U/V/W output phase loss or incorrect phase sequence.



Remedy:
  • Connect cables again according to correct wiring diagram.



Cause: Servo drive U/V/W cables or encoder cable disconnected.



Remedy:
  • Connect cables again in correct order.



Cause: Motor stalled due to mechanical factors.



Remedy:
  • Eliminate mechanical factors.



Cause: Gain values are too low.



Remedy:
  • Adjust gain values manually or perform auto-tuning.



Cause: Position reference increment too large.



Remedy:
  • Decrease position reference increment or gear ratio.



Cause: Value of 6065h is insufficient.



Remedy:
  • Increase the setpoint of 6065h.



Cause: Servo drive/motor faulty.



Remedy:
  • If position feedback is 0 while reference is not, replace drive or motor.


EB01.0
Position reference increment too large

Cause: The pulse reference increment exceeds the excessive reference threshold three times consecutively.



Remedy:

  • Increase the value of H0A.09.

  • Reduce the baud rate of pulse input.


EB01.1
Individual position reference increment too large

Cause: The target position increment is too large.



Remedy:

  • Check whether max speed of motor fulfills application requirement. If yes, reduce target position reference increment. If not, replace servo motor.

  • Check whether target position is aligned with current position feedback before switching mode.

  • Check the communication sequence of the host controller.


EB01.3
Command overflow

Cause: The target position is still in the process of transmission when the servo limit or software position limit signal is activated and the 32-bit upper/lower limit is reached.



Remedy:

  • Detect the servo limit signal (bit0 and bit1 of 60FD is recommended) through the host controller.

  • Stop sending limit direction commands when an active servo limit signal is detected by the host controller.


EB02.0
Excessive position deviation in fully closed-loop mode

Cause: The absolute value of position deviation in fully closed-loop mode exceeds the value of H0F.08.



Remedy:

  • Connect cables again according to the correct wiring diagram or replace the cables (check for U/V/W phase loss).

  • Ensure servo drive power cables are connected in the correct order at both ends.

  • Eliminate mechanical factors causing the motor to stall.

  • Adjust the gain values manually or use gain auto-tuning (H08.00…H08.05).

  • Reduce the position reference frequency or the electronic gear ratio.

  • Increase the setpoint of H0F.08 (Threshold of excessive position deviation).

  • If the position reference is not 0 but feedback is always 0, replace the servo drive or motor.


EB02.1
Fully closed-loop position deviation overflow

Cause: The absolute value of the fully closed-loop position deviation is greater than 231.



Remedy:

  • Check wiring for U/V/W output phase loss or incorrect phase sequence.

  • Reconnect drive power cables in the correct order or replace cables if disconnected.


EB03.0
Electronic gear ratio overrun

Cause: The electronic gear ratio exceeds the limit: (0.001–4000 x Encoder resolution/10000).



Remedy:

  • Change the value of H05.02 so the ratio is within range.


EB03.1
Electronic gear ratio overrun (Group 1)

Cause: The group 1 electronic gear ratio exceeds the limit: (0.001–4000 x Encoder resolution/10000).



Remedy:

  • Change the values of H05.07/H05.09.


EB03.2
Electronic gear ratio overrun (Group 2)

Cause: The group 2 electronic gear ratio exceeds the limit: (0.001–4000 x Encoder resolution/10000).



Remedy:

  • Change the values of H05.11/H05.13.


ED02.0
Modbus communication timeout

Cause: Modbus communication timeout occurred.



Remedy:

  • Determine the Modbus access cycle by frame grab.

  • Increase the value of H0E.83.


ED03.0
CANLink communication failure

Cause: The master is offline.



Remedy:

  • Capture frames to ensure that the master station is online.

  • Increase the heartbeat threshold of the master station.

  • Check the wiring.


ED04.0
CANopen communication timeout

Cause: The slave reaches the time configured by the consumer or the node guarding time.



Remedy:

  • Check whether all CAN nodes are online.

  • Check the CANopen configuration.

  • Reset the node or communication.


ED05.0
CANopen communication initialized

Cause: Errors (slave offline, heartbeat abnormal, etc.) occurred when NMT changes to initialization state.



Remedy:

  • Reset the NMT node. (Disable output stage when changing NMT).

  • Use shielded cables to prevent interference.

  • Ground the servo drive properly.

  • Ensure the termination resistor is installed.

  • Ensure no false reset frame is triggered by the host controller.


ED08.0
CANopen bus PDO transmission length error

Cause: The length of content transmitted by PDO is inconsistent with configured mapping length.



Remedy:

  • Re-configure the PDO settings.

  • Reset the node or communication.


ED11.0
CANopen sync period error too large

Cause: The SYNC period error exceeds the setpoint.



Remedy:

  • Check settings of 60C2.01h and 60C2.02h to ensure sync period is set properly.

  • Ensure host controller sync period is correct.

  • Check wiring between the slave and the master.


EE08.0
Synchronization lost

Cause: Slave receiving abnormally, Master transmitting abnormally, or Network switch failure.



Remedy:

  • Use shielded twisted pair cables and ensure drive is grounded.

  • Check network connection status (LED).

  • If synchronization cycle is 0, activate the host controller synchronous clock.

  • Ensure network cables connect IN to OUT correctly.

  • Increase synchronization loss threshold of the slave (H0E.32).


EE08.1
Network status switchover error

Cause: The network switches from OP to non-OP when the servo drive is enabled.



Remedy:

  • Check the network status switchover program of the host controller.


EE08.3
Link is missing

Cause: Physical connection unstable, process data lost, or cable unplugged.



Remedy:

  • Check whether the network cable is connected securely.

  • Check whether strong vibration occurs on site.


EE09.0
Software position limit setting error

Cause: The lower limit of the software position limit is equal to or larger than the upper limit.



Remedy:

  • Reset the values (607D.01h and 607D.02h) ensuring the former is smaller than the latter.


EE09.1
Home setting error

Cause: The home offset is outside the software position limit or mechanical single-turn limit.



Remedy:

  • Set the home offset to a value within the software position limit.

  • Set the home offset to a value within the mechanical single-turn upper/lower limit.


EE09.2
Gear ratio beyond the limit

Cause: Electronic gear ratio exceeds range or numerator/denominator is 0.



Remedy:

  • Set the gear ratio according to the preceding range.


EE09.3
No synchronization signal

Cause: Improper clock config, inverse cable connection, or hardware damage.



Remedy:

  • Rectify improper master configurations.

  • Connect the IN and OUT ports in the correct sequence.

  • Contact Inovance if slave controller IC or MCU pins are damaged.


EE09.5
PDO mapping beyond the limit

Cause: The mapping objects in TPDO or RPDO exceeds 40 bytes.



Remedy:

  • Ensure mapping objects in TPDO or RPDO do not exceed 40 bytes.


EE10.0
Protection against MailBox setting error

Cause: Master station configured incorrectly or Slave XML file incorrect.



Remedy:

  • Check the configuration of SM0 and SM1 channels for errors.


EE10.1
SM2 setting error

Cause: Master station configured incorrectly or Slave XML file incorrect.



Remedy:

  • Check the configuration of SM2 for errors.

  • Check whether the index of the RxPDO mapping object dictionary is out of bounds (max 0x0A).


EE10.2
SM3 setting error

Cause: Master station configured incorrectly or Slave XML file incorrect.



Remedy:

  • Check the configuration of SM3 for errors.

  • Check whether the index of the TxPDO mapping object dictionary is out of bounds (max 0x1A).


EE10.3
PDO watchdog setting error

Cause: The master station is configured incorrectly.



Remedy:

  • Check the settings of the watchdog.


EE10.4
Protection against incomplete PLL (no sync signal)

Cause: The master station is configured incorrectly.



Remedy:

  • Check whether a sync0 signal is generated.


EE11.0
ESI check error

Cause: XML file load failed during EtherCAT communication.



Remedy:

  • Download the XML file.

  • Set H0E.37 to 1 and power on and off again.


EE11.1
Failed to read e2prom by bus

Cause: The e2prom communication fails.



Remedy:

  • Replace the servo drive.


EE11.2
Failed to update e2prom by bus

Cause: Communication is normal but information in e2prom is wrong or lost.



Remedy:

  • Replace the servo drive.


EE11.3
ESI and drive mismatch

Cause: Downloaded XML file not compatible or modified unexpectedly.



Remedy:

  • Download the correct XML file.


EE16.0
MCU and ESC communication error

Cause: MCU and ESC communication timeout.



Remedy:

  • Replace the servo drive.



E602.0
Angle auto-tuning failure


E220.0
Phase sequence incorrect


EA40.0
Parameter auto-tuning failure


E111.0
Internal parameter error

Cause: Internal system fault.



Remedy:

  • Contact Inovance for technical support.