Inovance SV660F Drive

Inovance SV660F Drive Fault Codes:

Fault Code and Meaning	Cause and Remedy
E108.0 Parameter write error Parameter values cannot be written to EEPROM.	Cause: An error occurs 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 Parameter values cannot be read from EEPROM.	Cause: The parameter-read operation is abnormal, and the system indicates an EEPROM read failure. 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.2 EEPROM write check error The check on the data written in EEPROM failed.	Cause: An error occurs 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.3 EEPROM read check error The check on the data read in EEPROM failed.	Cause: An error occurs during parameter-reading. 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.
E110.0 Frequency-division pulse output setting error The frequency-division output setpoint (H05.17) exceeds the encoder resolution.	Cause: The number of frequency divisions (quadrupled) exceeds the motor revolutions. Remedy: Check the value of H05.17. Adjust the value of H05.17 on the basis of the motor revolutions.
E121.0 Duplicate S-ON command A redundant S-ON signal is sent when some auxiliary functions are used.	Cause: The external S-ON signal is active when servo drive is enabled internally. Remedy: Check whether DI functions (H0d.02, H0d.03, and H0d.12) are used and whether FunIN.1 (S-ON signal) is active. Deactivate the DI assigned with FunIN.1 (both hardware DI and virtual DI).
E122.0 Multi-turn absolute encoder setting error The motor does not match the absolute position mode or the motor code is set improperly.	Cause: The motor does not match the absolute position mode or the motor code is set incorrectly. Remedy: Check the motor nameplate to see whether the motor is configured with a multi-turn absolute encoder. Check whether H00.00 (motor code) is set properly. Reset H00.00 (motor code) according to the motor nameplate or use a suitable motor.
E510.0 Frequency division output overspeed The single-channel output pulse frequency exceeds the frequency upper limit allowed by the hardware (4 MHz).	Cause: H05.38 is set to 0 or 2: Output pulse frequency exceeds limit based on motor speed. H05.38 is set to 1: Input pulse frequency exceeds 2 MHz or interference exists. Remedy: If H05.38=0 or 2: Decrease the value of H05.17 to allow output frequency to drop below the limit. If H05.38=1: Decrease the input pulse frequency to a value within the upper limit. Take anti-interference measures (use STP cable for pulse input and set pin filter H0A.24 or H0A.30).
E550.2 External switchover wait warning Incorrect task block switching.	Cause: The external warning must be kept to allow current block to continue operating. Remedy: Check bit4–7 of the task mode (H28.16–H28.31) of current operation block. The warning will be cleared automatically when the next block is triggered by the external signal.
E600.0 Inertia auto-tuning failure Vibration cannot be suppressed, values fluctuate, or load issues.	Cause: Continuous vibration occurs during auto-tuning. Auto-tuned values fluctuate dramatically. Mechanical couplings are loose/eccentric. Load carries large inertia. Remedy: Rectify the fault and perform inertia auto-tuning again. For vibration that cannot be suppressed, enable vibration suppression or set notch parameters manually. Ensure mechanical couplings are connected securely. Increase maximum operating speed, reduce acceleration/deceleration time, and shorten stroke during ETune.
E601.0 Homing warning Homing time exceeds the setpoint.	Cause: The home switch is faulty (high speed search but no low speed). The homing time limit (H05.35h) is too short. The speed in high-speed searching is too low (long homing process). The setting of the home switch is improper. Remedy: Check wiring/logic of DI. Monitor H0b.03. If Z signal is used, check Z signal condition. Increase the value of H05.35 (time limit). Increase the value of 6099.01h (high-speed search speed). Set the position of the physical switch properly.
E601.1 Homing switch error The homing switch is set improperly.	Cause: The home switch is set improperly (e.g., limit signals at both sides activated simultaneously with home signal). Remedy: Check whether limit signals at both sides are activated. Check if limit signal and home signal are both activated. Set the position of the physical switch properly.
E601.2 Homing method setting error The homing method value is too large.	Cause: The homing method value is too large. Remedy: Check the homing method value (object dictionary 6098h). Change the value of 6098h.
E730.0 Encoder battery warning The voltage of the absolute encoder battery is lower than 3.0 V.	Cause: The voltage of the absolute encoder battery is lower than 3.0 V. Remedy: Measure the battery voltage. Use a new battery with the matching voltage.
E900.0 DI emergency braking The DI terminal allocated with DI function 34 (Emergency Stop) is active.	Cause: The DI function 34 (EmergencyStop) is triggered. Remedy: Check whether the logic of the DI allocated with FunIN.34 is valid. Check the operation mode and clear the active DI braking signal.
E902.0 DI setting invalid DI function parameters are set to invalid values.	Cause: DI (DI1…DI5) function parameters are set to invalid values. Remedy: Check whether H03.02, H03.04, H03.06, H03.08, and H03.10 are set to invalid values. Set DI function parameters to valid values.
E902.1 DO setting invalid DO function parameters are set to invalid values.	Cause: DO (DO1…DO3) function parameters are set to invalid values. Remedy: Check whether H04.00, H04.02, and H04.04 are set to invalid values. Set DO function parameters to valid values.
E902.2 Invalid setting for torque reach DO parameters set for torque reach are invalid.	Cause: The value of H07.22 is lower than or equal to the value of H07.23. Remedy: Set H07.22 to a value higher than that of H07.23.
E908.0 Model identification failure Model identification check code error.	Cause: The model identification check word stored in EEPROM is incorrect. Model parameters not written before delivery. Remedy: Check whether the warning persists after restart. Set H01-72 to 1 to disable model identification temporarily. Check whether parameters can be saved to EEPROM.
E908.1 Inverter model setting mismatch The inverter model is set improperly.	Cause: The model identification check word stored in EEPROM is incorrect. Model parameters not written before delivery. Remedy: Check whether the warning persists after restart. Set H01-72 to 1 to disable model identification temporarily. Check whether parameters can be saved to EEPROM.
E920.0 Regenerative resistor overload The accumulative heat of the regenerative resistor exceeds the set value.	Cause: External resistor disconnected or improper connection. Jumper between P⊕ and D is shorted/disconnected improperly. H02.25 (Resistor type) set improperly. Resistance is too large. Input voltage of main circuit beyond specified range. Load moment of inertia too large. Remedy: Replace/Connect resistor properly between P⊕ and C. Ensure terminals P⊕ and D are jumpered for built-in resistor usage. Set H02.25 correctly (1=External natural, 2=External forced air). Select proper regenerative resistor according to specifications. Adjust power supply to specified range (220V or 380V ranges). Select larger resistor/drive, reduce load, or increase accel/decel time.
E922.0 Resistance of external regenerative resistor too small H02.27 is lower than H02.21 (permissible min. resistance).	Cause: When an external resistor is used, its resistance is lower than the minimum allowed. Remedy: Measure resistance between P⊕ and C. If too low: Replace with a resistor that matches the drive, then set H02.27 accordingly. If not too low: Set H02.27 to a value consistent with the actual resistance used.
E924.0 Regenerative transistor overtemperature Estimated temperature is higher than H0A.18.	Cause: The regenerative transistor temperature exceeds the threshold defined by H0A.49. Remedy: Control the working conditions and usage of the regenerative transistor.
E941.0 Parameter modifications activated at next power-on Parameters modified require a restart.	Cause: The parameters modified are those whose “Effective time” is “Next power-on”. Remedy: Check modified parameters. Power off and on the servo drive again.
E942.0 Parameter saved frequently The number of parameters modified at a time exceeds 200.	Cause: Too many parameters are modified and saved to EEPROM (H0C.13 = 1) at a brief interval. Remedy: Check the operation mode. For parameters that need not be saved to EEPROM, set H0C.13 to 0.
E950.0 Forward overtravel warning DI function 14 (P-OT) effective or software limit reached.	Cause: Logic of DI assigned with FunIN.14 is effective. Servo position feedback reaches positive software position limit. Remedy: Send a reverse command or rotate motor to deactivate DI logic. Ensure servo drive references are proper, allowing load travel within software position limit.
E952.0 Reverse overtravel warning DI function 15 (N-OT) effective or software limit reached.	Cause: Logic of DI assigned with FunIN.15 is effective. Servo position feedback reaches negative software position limit. Remedy: Send a forward command or rotate motor to deactivate DI logic. Ensure servo drive references are proper, allowing load travel within software position limit.
E958.0 Reverse position reference overtravel in process segment position mode Reverse direction position reference overtravel.	Cause: Position reference is less than the value of H22.06 when motor runs reversely in process segment mode. Remedy: Increase the position reference to a value greater than the setpoint of H22.06.
E980.0 Encoder algorithm error An encoder algorithm error occurs.	Cause: An internal fault occurs on the encoder. Remedy: If the servo drive is powered off and on several times but the warning is still reported, replace the servo motor.
EA41.0 Torque fluctuation compensation failure The torque compensation fails.	Cause: The torque compensation fails. Remedy: Turn off the torque fluctuation compensation function.
E101.0 Parameter error in H02 and above	Cause: 1. Control circuit power supply voltage drops instantaneously. 2. Instantaneous power failure while saving parameters. 3. Excessive write operations within a certain period. 4. Software update caused parameter limit overflow. 5. Servo drive is faulty. Remedy: Restore default settings (H02.31 = 1) and write parameters again. Check input voltage (L1C, L2C). Increase power capacity if needed. Check for power failures during storage. If write operations exceeded limit: Change parameter writing method or replace servo drive. Reset servo drive/motor model and restore default settings. If fault persists after power cycle and reset, replace the servo drive.
E101.1 Parameter error in group H00/H01	Cause: Parameter values in H00/H01 exceed the upper/lower limit (often after software update or initialization). Remedy: Check groups H00 and H01 to find the parameter with abnormal range. Confirm whether the parameter range is abnormal. Replace the motor or servo drive.
E101.2 Address error in read/write operation	Cause: Total number of parameters changed after software update, leading to address error. Remedy: Read H0b.90 and H0b.91 to obtain the abnormal parameter group number. Rectify the wrong values. Restore default settings.
E102.0 FPGA communication establishment error	Cause: Communication between MCU and FPGA cannot be established. Remedy: Power the servo drive off and on repeatedly. If fault persists, replace the servo drive.
E102.1 FPGA initialization start error	Cause: FPGA cannot start / FPGA failed. Remedy: Power the servo drive off and on repeatedly. If fault persists, replace the servo drive.
E102.8 FPGA and MCU version mismatch	Cause: The software versions of MCU and FPGA are inconsistent. Remedy: Check MCU version (H01.00) and FPGA version (H01.01). Contact Inovance for technical support. Update the FPGA or MCU software.
E104.1 MCU running timeout (MCU break down)	Cause: Access to MCU timed out due to FPGA failure, communication handshaking error, or coprocessor access timeout. Remedy: Power the servo drive off and on repeatedly. If fault persists, replace the servo drive.
E104.2 Current loop operation timeout (FPGA break down)	Cause: MCU torque interrupt scheduling time is abnormal (FPGA failure or handshaking error). Remedy: Power the servo drive off and on repeatedly. If fault persists, replace the servo drive.
E104.4 MCU command update timeout	Cause: Encoder communication time set improperly or command calculation time is too long. Remedy: Hide unnecessary functions. Replace the servo drive.
E120.0 Unknown encoder model	Cause: 1. Motor or drive code does not exist. 2. Power rating of motor does not match servo drive. Remedy: If using SV660F/23-bit motor, ensure H00.00 is set to 14101. Check servo drive code (H01.02) matches nameplate. Check if H01.02 matches serial-type motor code (H00.05). Replace the unmatched products.
E120.1 Unknown motor model	Cause: The motor model defined by H00.00 is abnormal or does not exist. Remedy: Check whether the value of H00.00 matches the used motor. Rectify the value of H00.00.
E120.2 Unknown drive model	Cause: H01.10 is incorrect (drive model detection failed). Remedy: Check the value of H01.10. Disable servo drive model auto detection. Set H01-10 to a proper value manually.
E120.5 Motor and drive current mismatch	Cause: The internal scale value is abnormal (rated output of drive is far higher than motor). Remedy: Check whether the servo drive model is correct. If calculation overflow occurs due to sampling coefficient, replace the servo drive.
E120.6 FPGA and motor model mismatch	Cause: FPGA software version and H00.00 mismatch, or encoder not supported. Remedy: Check if FPGA version (H01.01) supports the motor model (H00.00). Update the FPGA software to support the motor model. Replace the motor.
E120.7 Model check error	Cause: Model parameter CRC check failed. Remedy: Check that the model parameter is present. Write the model parameter again.
E120.8 Junction temperature parameter check error	Cause: Junction temperature parameter CRC check failed. Remedy: Check that the junction temperature parameter is present. Rewrite the junction temperature parameter.
E122.1 Different DIs assigned with the same function	Cause: 1. Multiple DIs assigned with same function. 2. DI function No. exceeds maximum allowed. Remedy: Check H03.02-H03.20 and H17.xx. Assign different DI function numbers. Re-energize control circuit or send “RESET” signal. If function No. exceeds limit: Restore system parameters (H02.31=1) and restart drive.
E122.2 Different DOs assigned with the same function	Cause: The DO function No. exceeds the maximum number allowed. Remedy: Check H04.00 and H04.02. Set the correct DO function No.
E122.3 Upper limit in the rotation mode invalid	Cause: The upper limit of the mechanical single-turn position exceeds 2^31 in absolute position rotation mode. Remedy: Check mechanical gear ratio and electronic gear ratio (H02.01 = 2). Reset ratios to ensure upper limit does not exceed 2^31.
E122.4 Different VDIs assigned with the same function	Cause: 1. The same function is assigned to different VDIs. 2. VDI function No. exceeds maximum allowed. Remedy: Check H03/H17 groups. Assign different numbers. Restart control circuit or send “RESET” signal. Restore system parameters (H02.31=1) and restart drive.
E122.5 DI and VDI assigned with the same function	Cause: Two or more DIs and VDIs are assigned with the same function No. Remedy: Check DI function numbers in groups H03 and H17. Change any repetitive number.
E122.8 Small lower limit of the rotation mode	Cause: The lower limit of the mechanical single-turn position (modal axis modulus) is less than 1. Remedy: Check mechanical and electronic gear ratios (H02.01 = 2 or 5). Reset ratios to ensure lower limit is not below 1.
E126.0 Process segment number error	Cause: The process segment number is not 1000 or any value from 0 to 15. Remedy: Check if H22.00 exceeds range (0-15 or 1000). Write 0…15 to H22.00 in the technology segment mode.
E126.1 Process segment internal operation mode error	Cause: The technology segment operation mode is not 0, 1, 2, 3, 7, or 8. Remedy: Check values of bit0 to bit3 of the parameter defined by the faulty segment. Set operation mode to 0, 1, 2, 3, 7, or 8.
E126.2 Position reference type error in process segment	Cause: The position reference type is not 00 (Absolute) or 10 (Incremental). Remedy: Check bit6 or bit7 of the faulty technology segment parameter. Set position reference type to 00 (Absolute) or 10 (Incremental).
E136.0 Encoder ROM motor parameter check error	Cause: 1. Servo drive/motor model mismatch. 2. Encoder ROM parameter check error or no parameters saved. 3. Servo drive is faulty. Remedy: Check nameplates (SV660F series + Servo Motor). Replace if unmatched. Use Inovance encoder cable. Ensure secure connection. Route encoder cables and power cables separately to avoid interference. Replace the servo drive if fault persists after restart.
E136.1 Encoder ROM motor parameter read error	Cause: 1. Encoder cable connections incorrect or loosened. 2. Ambient vibration causing looseness. 3. Servo drive is faulty. Remedy: Connect encoder cables according to correct wiring diagram. Re-connect and ensure terminals are secure. Replace the servo drive if fault persists after restart.
E136.2 Torque ripple compensation data check error	Cause: Data check error. Remedy: Check the encoder type. Power on the servo drive again.
E150.0 STO safety state applied	Cause: Two 24V inputs are disconnected simultaneously, triggering STO function. Remedy: Check if STO function is activated. Clear fault when STO terminal is normal. Check 24V power supply stability. Tighten loose or disconnected cables. Replace servo drive if fault persists.
E150.1 STO input state abnormal	Cause: The single-channel input of STO is ineffective. Remedy: Check STO input wiring. Ensure both channels operate correctly.
E150.2 Buffer 5 V voltage detection error. The MCU monitors the 5 V power supply of the PWM Buffer.	Cause: The 5 V voltage supplied to the STO Buffer is abnormal due to undervoltage or overvoltage. Remedy: Check whether the fault can be removed by a restart. If the fault persists, the 5V voltage supplied to the Buffer is abnormal. Replace the servo drive.
E150.3 STO input circuit hardware diagnosis failure. Short circuit on upstream optocoupler of STO.	Cause: Short circuit occurs on the upstream optocoupler of STO1 or STO2. Remedy: Restart the drive. If the keypad displays E150.3 after restart, replace the servo drive.
E150.4 PWM buffer hardware detection failure. Error on PWM Buffer IC during initialization.	Cause: STO Buffer power-on test error. Remedy: Restart the drive. If the keypad displays E150.4 after restart, replace the servo drive.
E201.0 Phase-P overcurrent. Excessively high current flows through the positive pole of the DC-AC circuit.	Cause: 1. Gains set improperly (oscillation). 2. Encoder wired improperly, aging, or loose. 3. Servo drive is faulty. 4. Overcurrent on regenerative resistor. Remedy: Modify motor parameter values or current/speed loop parameters. Re-solder, tighten or replace the encoder cable. Disconnect motor cable and power on; if fault persists, replace servo drive. Check if external regenerative resistor resistance is too small or short-circuited. Use a matching regenerative resistor and perform wiring again.
E201.1 Phase-U overcurrent. Current higher than threshold collected in phase-U.	Cause: 1. Motor cables in poor contact, grounded, or short-circuited. 2. The motor is damaged. Remedy: Check U, V, W cables for looseness and tighten them. Measure insulation resistance (U/V/W to PE) to ensure it is at MΩ level. Check for short circuits or burrs in wiring. Replace the motor if insulation is poor or resistance is unbalanced.
E201.2 Phase-V overcurrent. Current higher than threshold collected in phase-V.	Cause: 1. Motor cables in poor contact, grounded, or short-circuited. 2. The motor is damaged. Remedy: Tighten loose cables. Check insulation resistance and for short circuits between phases. Connect motor cables correctly. Replace the motor if resistance is unbalanced.
E201.4 Phase-N overcurrent. Excessively high current flows through the negative pole of the DC-AC circuit.	Cause: 1. Gains set improperly (oscillation). 2. Encoder wired improperly or aging. 3. Regen resistor resistance too small or shorted. 4. Abrupt acceleration during braking. 5. Servo drive is faulty. Remedy: Adjust the gains. Re-solder, tighten, or replace the encoder cable. Replace with a matching regenerative resistor. Increase the acceleration/deceleration time. Disconnect motor cable; if fault persists after power cycle, replace servo drive.
E206.0 Switching frequency abnormal.	Cause: 1. Motor control malfunction. 2. Switch-on times of inverting circuit is abnormal. Remedy: Power the servo drive off and on. If fault persists, replace the servo drive.
E208.2 Encoder communication timeout. FPGA detected communication timeout with encoder.	Cause: 1. Drive fails to receive data for 3 consecutive cycles. 2. Cable loose, too long, or interference. 3. Faulty encoder. Remedy: Check if motor model is correct (Check bit12 of H0b.30). Check condition of encoder cable (reconnect or replace). Check encoder version (H00.04). If drive operates improperly, replace it.
E208.4 FPGA current loop operation timeout. Operating time exceeds interval threshold.	Cause: FPGA operation timeout / Internal fault code H0b.45 = 4208. Remedy: Disable unnecessary functions to reduce the operating load of the current loop.
E210.0 Output short-circuited to ground. Abnormal phase current or bus voltage during power-on self-test.	Cause: 1. Power cables (U/V/W) shorted to ground. 2. Motor shorted to ground. 3. Servo drive faulty. 4. Motor speed too high during detection. Remedy: Disconnect motor cables and measure for short to PE; replace cables if needed. Measure motor insulation resistance; replace motor if needed. Disconnect cables; if fault persists on power-up, replace servo drive. Reduce the motor speed during power-on.
E234.0 Runaway. Torque/Speed reference direction is reverse to feedback direction.	Cause: 1. Phase sequence of U/V/W incorrect. 2. Interference signal causes error in initial phase detection. 3. Encoder model wrong or wired improperly. 4. Gravity load too large (vertical axis). 5. Improper stiffness settings (vibration). Remedy: Connect U, V, W cables according to correct phase sequence. Power off and on again (check interference). Check servo motor nameplates (SV660F/23-bit). Re-solder or replace encoder cable. Reduce load, increase stiffness level, or adjust brake parameters (H02.09…H02.12). Set a proper stiffness level to avoid excessive vibration.
E320.0 Regenerative resistor overload.	Cause: Accumulative heat of regenerative resistor exceeds thermal capacity. Remedy: Check whether value of H0b.67 exceeds 100%. Check if large discharge current is present due to high bus voltage. Ensure the motor cannot be driven reversely. Replace the servo drive.
E320.1 Braking resistor surface temperature too high.	Cause: The braking resistor surface temperature is too high. Remedy: Check whether value of H0b.67 exceeds 100%. Check if large discharge current is present due to high bus voltage. Ensure the motor cannot be driven reversely. Replace the servo drive.
E400.0 Main circuit overvoltage. DC bus voltage exceeds threshold.	Cause: DC bus voltage between P⊕ and N⊖ is too high. (220V drive threshold: 420V / 380V drive threshold: 760V). Remedy: Check input power supply voltage. Check if the drive is decelerating too quickly (regenerative energy). Check braking resistor wiring and value.
E410.0 Main circuit undervoltage	Cause: 1. The power supply of the main circuit is unstable or power failure occurs. Remedy: Check input voltage at main circuit cables (R/S/T). Increase the capacity of the power supply. Cause: 2. Instantaneous power failure occurs. Remedy: Measure voltages of all three phases. Increase the capacity of the power supply. Cause: 3. The power voltage drops during running. Remedy: Check if power is applied to other devices causing drops. Increase power capacity. Cause: 4. A three-phase servo drive is connected to a single-phase power supply (Phase Loss). Remedy: Check wiring. Replace cables and wire correctly (Three-phase: R, S, T). Cause: 5. The servo drive is faulty (Bus voltage reading error). Remedy: Check if H0b.26 is below threshold (<200V for 220V drive; <380V for 380V drive). Replace the servo drive.
E410.1 Main circuit de-energized (Phase Loss)	Cause: 1. The power supply is disconnected during operation. Remedy: Check input voltage at main circuit cables (R/S/T). Increase the capacity of the power supply. Cause: 2. Drive faulty (Internal voltage check). Remedy: Check if 200B.1Bh (Bus voltage) is within range. Replace the servo drive. Cause: 3. Wiring issue. Remedy: Check wiring of the main circuit. Replace cables and wire correctly (Three-phase: R, S, T/L1, L2, L3).
E420.0 Main circuit phase loss	Cause: 1. The three-phase input cables are connected improperly. Remedy: Check RST cables on drive and non-drive side. Replace cables and connect properly. Cause: 2. A single-phase power supply is used for a three-phase servo drive. Remedy: 0.75 kW drives (H01.10=5) can use single-phase. Set H0A.00 to 2 (Inhibit phase loss faults) if input complies with specs. Otherwise, replace or adjust power supply. Cause: 3. Power supply unbalanced or voltage too low. Remedy: Measure voltages of all three phases. Replace or adjust the power supply.
E420.1 Main circuit PL signal detection error	Cause: 1. Three-phase input cables connected improperly. Remedy: Power off and on again. Ensure power supply is stable. Cause: 2. Single-phase used / Unbalanced supply. Remedy: Check specifications and voltage range. Replace or adjust power supply.
E430.0 Control circuit power supply undervoltage	Cause: 1. The control power supply of servo drives (size C/D/E) is unstable or fails. Remedy: Check specifications and measure voltage input. Increase the capacity of the power supply. Cause: 2. Control power supply cables in poor contact. Remedy: Check if L1C, L2C cables are connected properly. Re-connect or replace the cables.
E500.0 Motor overspeed	Cause: 1. The phase sequence of motor cables is wrong. Remedy: Connect U, V, and W cables according to correct phase sequence. Cause: 2. H0A.08 (Overspeed threshold) is set improperly. Remedy: Re-set the overspeed threshold according to mechanical requirements. Cause: 3. The input reference exceeds the overspeed threshold. Remedy: Position Mode: Decrease position reference increment; check gear ratios (6091h). Speed Mode: Decrease target velocity, speed limit, or gear ratio. Torque Mode: Set speed limit (H07.17) lower than overspeed threshold. Cause: 4. The motor speed overshoots. Remedy: Adjust the gain or mechanical running conditions. Cause: 5. The servo drive is faulty. Remedy: Replace the servo drive.
E500.1 Speed feedback overflow	Cause: 1. FPGA internal speed overflows. Remedy: Connect U, V, W cables according to correct phase sequence. Cause: 2. The motor speed overshoots. Remedy: Adjust the gain or mechanical running conditions.
E500.2 FPGA position feedback pulse overspeed	Cause: Communication error occurred between boards of the drive. Remedy: If alarm persists after repeated power off/on, replace the servo drive.
E550.0 Initial operation block number not exist	Cause: The block number designated by PLC is outside range (0-15) or set to “Invisible”. Remedy: Rectify the operation block number. Change the attribute to “Visible”.
E550.1 Relative/absolute attribute set improperly	Cause: The relative/absolute attribute of positioning or fixed stopper commands set improperly (bit8–bit11 of task mode is 0 or 1). Remedy: Set bit4–bit7 of the corresponding task mode to 0 or 1.
E550.9 Fixed stopper beyond the window	Cause: The position feedback fluctuation exceeds the monitoring window (H28.64) after the fixed stopper is found. Remedy: Check whether H28.64 is set properly. Set a proper monitoring window value.
E551.1 Program block stop exception	Cause: The switchover condition for the last block is not “stop”. Remedy: Check whether bit4–7 of the task mode (H18.16–28.31) of the last block in operation is 0. Set the switchover condition for the last block to “stop”.
E551.3 Jump block not exist	Cause: The block number designated by the jump task does not exist. Remedy: Check whether the setting range of corresponding task parameters (H28.32–H28.62) of the jump block is 0–15. Set task parameters for the jump block properly.
E602.0 Angle auto-tuning failure	Cause: The data fed back by the encoder is abnormal (unusual jitter). Remedy: Check if the encoder communication is being disturbed. Check the wiring of the encoder.
E602.2 U/V/W phase sequence reversed	Cause: Incorrect UVW wiring is detected during angle auto-tuning. Remedy: Exchange cables of any two phases among U/V/W and perform auto-tuning again.
E605.0 Motor speed too high upon S-ON	Cause: The motor speed exceeds the rated speed when the servo drive is switched on. Remedy: Check if the drive is enabled when the motor has been 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. Possible causes: Motor/Encoder cables connected incorrectly or poor contact. Load is too heavy; effective torque exceeds rated torque. Acceleration/deceleration too frequent or load inertia too large. Gain adjustment improper or stiffness too high. Servo drive or motor model set improperly. Motor stalled due to mechanical factors. Servo drive is faulty. Remedy: Connect cables according to the wiring diagram (use Inovance cables if possible). Use a servo drive of higher capacity, reduce load, or increase accel/decel time. Check H0b.12 (average load rate). Readjust the gain if the motor vibrates. Check drive model (H01.10) and motor model (H00.00). Rectify mechanical-related problems if motor speed is 0 but reference is not 0. If fault persists after power off/on, replace the servo drive. Note: Stop drive for at least 30s before further operations.
E625.0 Brake abnormality enabled	Cause: The brake fails when it is released. Remedy: Check if the motor shaft end is held by the brake when the brake release signal is active. Check the brake wiring. Replace the Brake motor.
E626.0 Brake abnormality disabled	Cause: The brake fails when it closes. Remedy: Check if the motor shaft end is not held tightly by the brake when the braking signal is active. Check the brake wiring. Replace the Brake motor.
E630.0 Motor rotor locked over-temperature	Cause: Motor speed is lower than 10rpm but torque reference reaches limit for time defined by H0A.32. Remedy: If U/V/W phase loss/breakage: Check cable connections and phase sequence; connect cables again or replace them. If motor parameters set improperly: View Group H00 (especially pole pairs H00.28). Perform angle auto-tuning. If communication disturbed: Check communication lines between host and drive. If mechanically stalled: Check if any mechanical part is stuck or eccentric.
E640.0 IGBT over-temperature	Cause: The IGBT temperature reaches the fault threshold defined by H0A.18. Remedy: Ambient temp too high: Improve cooling conditions to lower ambient temperature. Repeated restarts: Wait 30s before reset. Increase capacity of drive/motor. Increase accel/decel time. Reduce load. Fan damaged: Check fan operation. Replace servo drive if needed. Installation issue: Ensure proper direction and clearance according to requirements. Drive faulty: If fault persists 5 mins after power-off/on, replace the servo drive.
E640.1 Flywheel diode overtemperature	Cause: The temperature of the flywheel diode reaches the fault threshold defined by H0A.18. Remedy: Improve cooling conditions. Wait 30s before reset; increase drive capacity or accel/decel time. Check fan operation. Check installation clearance. Replace servo drive if fault persists.
E650.0 Heatsink overtemperature	Cause: The temperature of the servo drive power module is higher than the overtemperature threshold. Remedy: Improve cooling conditions. Wait 30s before reset; increase drive capacity or accel/decel time. Check fan operation. Check installation clearance. Replace servo drive if fault persists.
E660.0 Motor overtemperature	Cause: The temperature of the air-cooled motor is too high. Remedy: Measure the temperature of the air-cooled motor. Cool the motor down.
E661.0 STune failure	Cause: During STune operation, the gain drops to the lower limit (Position/Speed loop gain < 5, Model loop gain < 10). Remedy: Set the notch manually. Modify the electronic gear ratio to improve command resolution. Increase the command filter time constant. Check if 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: Resonance occurred during ETune operation cannot be suppressed. Remedy: Set the notch manually when vibration cannot be suppressed automatically. Modify the electronic gear ratio to improve command resolution. Increase H09.11 as appropriate. Check if the machine suffers from periodic fluctuation. Check if positioning threshold is too low; increase reference accel/decel time.
E663.0 ITune failure	Cause: Resonance occurred during ITune operation cannot be suppressed. Remedy: Check whether there is abnormal noise or torque fluctuation during operation. (Refer to resonance suppression methods similar to ETune/STune if applicable).
E664.0 Resonance too strong	Cause: Resonance occurs on the servo system and the torque fluctuation amplitude is higher than the value of H09.54. Remedy: Check whether there is abnormal noise or torque fluctuation during operation. Set the notch manually when vibration cannot be suppressed automatically. Modify the electronic gear ratio to improve command resolution. Increase the command filter time constant. Check if the machine suffers from periodic fluctuation. Check inertia ratio and loop gain parameters. Increase the value of H09.54 or set to 0 to disable function.
E731.0 Encoder battery failure	Cause: The voltage of the absolute encoder battery is lower than 2.9V. Remedy: Check if battery is connected (if not, Set H0d.20 to 1 to clear fault). Measure battery voltage. If too low, use a new battery with matching voltage.
E733.0 Encoder multi-turn counting error	Cause: An encoder multi-turn counting error occurs (Encoder 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 revolutions > 32767 or Reverse > 32768). Remedy: Check value of H0b.70 (Number of absolute encoder revolutions). Set H0d.20 to 2 to power on again. Perform homing if necessary.
E740.0 Absolute encoder communication timeout	Cause: Communication timeout occurs on the absolute encoder. Remedy: Check the wiring of the encoder and power on the servo drive again. Check whether the encoder version (H00.04) is set properly. Check whether the servo drive software version is correct (H01.00). Check encoder cable connections. Replace the servo motor.
E740.2 Absolute encoder error	Cause: A communication error occurs on the RX side of the encoder. Remedy: Check if H0b.28 is not 0. Check whether H00.00 (Motor code) is set properly. Check encoder cable connection. Ensure servo drive and motor are grounded properly (wind a magnetic ring on encoder cable).
E740.3 Absolute encoder single-turn calculation error	Cause: An internal fault occurs on the encoder (Encoder is faulty). Remedy: Check whether bit7 of H0b.28 is set to 1. 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 fault persists after cable replacement, the encoder may be faulty; replace the servo motor. Observe change of H0b.17 (Electrical angle); deviation should be within ±30°.
E760.0 Encoder overtemperature	Cause: The temperature of the absolute encoder is too high. Remedy: Measure the encoder or motor temperature. Switch off the S-ON signal to wait for the encoder to cool down.
E765.0 Nikon encoder over-temperature or overspeed	Cause: Motor overtemperature. Remedy: Check if the ambient temperature or the average load rate is too high. Switch off the S-ON signal to wait for the encoder to cool down.
E770.0 Fully-closed input phase A wire breakage	Cause: Fully-closed phase A input differential voltage wire breakage. Remedy: Measure the phase AB differential voltage to check if it is below 2.5 V. Adjust the fully-closed loop phase A input voltage.
E770.1 Fully-closed input phase B wire breakage	Cause: Fully-closed phase B input differential voltage wire breakage. Remedy: Measure the phase B differential voltage to check if it is below 2.5 V. Adjust the fully-closed loop phase B input voltage.
E770.2 Fully-closed input phase Z wire breakage	Cause: Fully-closed phase Z input differential voltage wire breakage. Remedy: Measure the phase Z differential voltage to check if it is below 2.5 V. Adjust the fully-closed loop phase Z input voltage.
EA33.0 Encoder read/write check error	Cause: Internal parameters of the encoder are abnormal (or cable disconnected/loose). Remedy: Check wiring. Separate motor cables and encoder cables. If fault persists after repeated power cycling, the encoder is faulty. Replace servo motor.
EB00.0 Position deviation too large	Cause: Position deviation is larger than setpoint of 6065h. Potential causes: Phase loss, disconnected cables, mechanical stall, low gain, or reference increment too large. Remedy: Phase Loss/Sequence: Re-connect cables according to wiring diagram. Disconnected Cables: Check U/V/W and encoder wiring. Replace if necessary. Stalled Motor: Check reference/motor speed (H0b.00). Rectify mechanical problem. Gain too low: Adjust gain values manually or perform auto-tuning (H08.00…H08.05). Reference too large: Decrease position reference increment (CSP/PP/HM modes). Decrease gear ratios. 6065h Value: Increase value of 6065h. Hardware Fault: If position reference is not 0 but feedback is 0, replace drive or motor.
EB00.1 Position deviation overflow	Cause: The position deviation is too large. Remedy: Perform no-load trial run; check wiring. Re-connect cables. Check U/V/W and encoder cables. Replace if necessary.
EB01.0 Position reference increment too large	Cause: Pulse reference increment exceeds threshold three times consecutively. Remedy: Check whether baud rate of pulse reference input exceeds H0A.09. 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 if max speed fulfills application requirement. Reduce target position reference increment (lower profile reference speed). Before switching mode/enabling, check if target position aligns with current feedback. Check communication sequence of host controller.
EB01.2 Position reference increment too large continuously	Cause: The target position increment is too large (Continuous). Remedy: See remedies for EB01.1. Check variation between two adjacent target positions using software tool.
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: Check whether the host controller continues sending commands after overtravel warning is reported. 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.
EB01.4 Target position beyond upper/lower limit	Cause: The target position exceeds the upper/lower limit of the unit position in the single turn absolute mode. Remedy: Check whether the set target position is within the single-turn upper/lower limit. Set the target position to a value within the upper/lower limit.
EB02.0 Position deviation exceeding threshold in fully closed-loop	Cause: The absolute value of position deviation in fully closed-loop mode exceeds the value of H0F.08. Causes include phase loss, disconnected cables, mechanical stalling, low drive gain, high input pulse frequency, or hardware faults. Remedy: Perform a no-load trial run; check wiring. Re-connect cables (U, V, W) or replace them. Check reference/motor speed and torque modes. Rectify mechanical-related problems if motor is stalled. Adjust gain values manually or use gain auto-tuning. Reduce position reference frequency or electronic gear ratio if input pulse frequency is too high. Increase the setpoint of H0F.08 if it is too low. Monitor operation waveform. If position reference is not 0 but feedback is 0, replace the servo drive or motor.
EB03.0 Electronic gear ratio beyond the limit – H05.02	Cause: The electronic gear ratio exceeds the limit: (0.001–4000 x Encoder resolution/10000). Remedy: Check if the electronic gear ratio is within the range. Change the value of H05.02.
EB03.1 Electronic gear ratio beyond the limit – Electronic gear ratio 1	Cause: The group 1 electronic gear ratio exceeds the limit: (0.001–4000 x Encoder resolution/10000). Remedy: Check if the group 1 electronic gear ratio is within the range. Change the group 1 electronic gear ratio.
EB03.2 Electronic gear ratio beyond the limit – Electronic gear ratio 2	Cause: The group 2 electronic gear ratio exceeds the limit: (0.001–4000 x Encoder resolution/10000). Remedy: Check if the group 2 electronic gear ratio is within the range. Change the group 2 electronic gear ratio.
EE03.0 Communication timeout	Cause: Communication timeout occurred after switching to the running state. Communication frame present, but drive is waiting. Remedy: Switch the PLC to normal operation state. Use the STP cable and ensure the drive is well grounded. Connect the cable according to wiring instructions. Verify that the topology of the host controller is consistent with the actual connection (IRT mode). Increase the watchdog time if PLC has too many axes.
EE03.1 Communication abnormal	Cause: The communication chip is not functioning properly (faulty), and the check times out. Remedy: Check if PLC is in normal operation state and STP cable is used. Check grounding and cable connections. If fault persists after repeated restarts, replace the servo drive.
EE08.0 PLC synchronization lost	Cause: The SYNC signal is turned off when the PROFINET network is in the OP state. Bit10 of control word changes. Remedy: Check whether STW1.bit10 (Encoder feedback mode) is set to 0. If STW1.bit10 is 0, set bit10 to 1.
EE08.1 PLC stopped	Cause: The PLC stopped during synchronous communication. Remedy: Switch the PLC to normal operation state. Use STP cable and ensure drive is grounded. Connect the cable according to wiring instructions. Check if the Ethernet port of the servo drive is damaged.
EE08.7 Abnormal heartbeat	Cause: The heartbeat is abnormal during synchronous communication. Remedy: Use the STP cable. Connect the cable according to the wiring instructions. Check the value of H29.01.
EE08.8 No network connection during synchronous communication	Cause: The network is not connected during synchronous communication. Remedy: Use the STP cable. Connect the cable according to the wiring instructions. Check whether the servo drive is well grounded.
EE08.9 LAN cable disconnected	Cause: The LAN cable is disconnected during synchronous communication. Remedy: Use the STP cable. Connect the cable according to the wiring instructions. Check whether the servo drive is well grounded.
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: Check the values of 607D.01h and 607D.02h. Reset the values and ensure the former is smaller than the latter.
EE09.1 Home setting error	Cause: The home offset exceeds the upper/lower limit of the software position limit or mechanical limit. Remedy: Set the home offset to a value within the software position limit (incremental/absolute linear/single-turn absolute modes). Set the home offset to a value within the mechanical single-turn upper/lower limit (rotation mode).
EE09.2 Gear ratio beyond the limit	Cause: The electronic gear ratio exceeds the limit. Remedy: Check if gear ratio 6091.01h/6091.02h exceeds the range. Set the gear ratio within the required range.
EE09.3 Homing mode setting error	Cause: MCU does not receive synchronization signal. Causes include improper sync clock config, inverse IN/OUT connection, damaged slave IC, or damaged MCU pins. Remedy: Rectify improper configurations (test with another master like Beckhoff/Omron). Connect the IN and OUT ports in the correct sequence. Measure synchronization signal with oscilloscope; if no signal, contact Inovance to replace slave controller IC. If signal exists but fault persists, contact Inovance to replace MCU chip.
EE09.5 PDO mapping beyond the limit	Cause: The mapping objects in TPDO or RPDO exceeds 40 bytes. Remedy: Check the number of self-indexes configured in 1600h or 1A00h. Ensure mapping objects in TPDO or RPDO do not exceed 40 bytes.
EE11.0 ESI check error	Cause: PROFINET communication failed to load the XML file. XML not downloaded or drive faulty. Remedy: Check whether XML version displayed in H0E.96 is normal. Download the XML file. If XML version is not empty, set H0E.37 to 1 and power on/off again.
EE11.1 EEPROM read failure	Cause: Communication with external EEPROM failed. Remedy: If fault persists after powering off and on several times, replace the servo drive.
EE11.2 EEPROM update failure	Cause: Communication is normal but message in EEPROM is wrong or lost. Remedy: If fault persists after powering off and on several times, replace the servo drive.
EE11.3 ESI and drive mismatch	Cause: The XML file does not match the drive model. Remedy: Check whether the XML version displayed in H0E.96 is normal. Download the correct XML file.
EE12.0 Parallel port detection error	Cause: The internal chip is faulty. Remedy: If fault persists after powering off and on repeatedly, replace the servo drive.
EE15.0 Synchronization cycle error too large	Cause: The synchronization cycle error of the controller exceeds the threshold. Remedy: Measure the synchronization cycle of the controller (digital oscilloscope or software tool). Increase the value of H0E.32.
EE16.0 MCU and ESC communication error	Cause: MCU and ESC communication timed out. Remedy: If fault persists after powering off and on repeatedly, replace the servo drive.
EE18.0 PN device name missing	Cause: The communication is faulty, leading to device name loss. Remedy: Check whether the device name is present through the software tool network. Re-assign a device name.
EE20.0 Continuous position reference not supported	Cause: Continuous position reference is set for telegram 111 relative positioning. Remedy: Check whether bit12 of POS_STW1 is 1. Set bit12 of POS-STW1 to 0.
Internal Faults (E602.0, E220.0, EA40.0, E111.0)	Cause: Internal errors (Angle auto-tuning, Phase sequence, Parameter auto-tuning, Internal parameter). Remedy: Contact Inovance for technical support.