Inovance SV670P Servo Drive Fault Codes:
| Fault Code and Meaning | Cause 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:
|
| 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:
|
| 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:
|
| 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:
|
| 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:
|
| 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:
|
| 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:
|
| E834.1 AI1 overvoltage | Cause: Input voltage is too high (>11.5 V), wiring error, or interference. Remedy:
|
| E834.2 AI2 overcurrent | Cause: Input current too large, wiring error, or interference. Remedy:
|
| 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:
|
| 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:
|
| 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:
|
| E952.0 Reverse overtravel warning | Cause: DI function 15 (N-OT, negative limit switch) triggered or software limit reached. Remedy:
|
| 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:
|
| E101.1 Parameter error in group H00/H01 | Cause: Parameter values in groups H00 or H01 exceed the limit (often after software update). Remedy:
|
| E101.2 System parameter error | Cause: Address error in read/write operation after the number of parameters changes. Remedy:
|
| E101.9 Parameter attribute initialization check error | Cause: Parameter attribute initialization check failed. Remedy:
|
| E102.0 FPGA communication establishment error | Cause: Communication between MCU and FPGA cannot be established. Remedy:
|
| E102.1 FPGA initialization start error | Cause: FPGA failed to start. Remedy:
|
| E102.8 FPGA and MCU version mismatch | Cause: Software versions of FPGA and MCU are inconsistent. Remedy:
|
| E104.1 MCU running timeout (MCU break down) | Cause: MCU Access timeout or Real-time communication error between MCU and FPGA. Remedy:
|
| E104.2 FPGA running timeout (FPGA break down) | Cause: FPGA running timeout, failure, or handshaking error. Remedy:
|
| E104.4 MCU command update timeout | Cause: Command calculation time is too long or encoder communication time set improperly. Remedy:
|
| E120.0 Unknown encoder model | Cause: Detected encoder model does not comply with requirement or drive/motor code mismatch. Remedy:
|
| E120.1 Unknown motor model | Cause: Motor model defined by H00.00 does not exist. Remedy:
|
| E120.2 Unknown drive model | Cause: Servo drive model defined by H01.10 does not exist. Remedy:
|
| E120.5 Motor and drive current mismatch | Cause: Drive rated output is far higher than motor rated current (internal scale value abnormal). Remedy:
|
| E120.6 FPGA and motor model mismatch | Cause: Motor model set improperly or encoder not supported by drive. Remedy:
|
| E120.7 Model check error | Cause: Model parameter CRC check failed; parameter not identified. Remedy:
|
| E120.8 Junction temperature parameter check error | Cause: Junction temperature parameter CRC check failed. Remedy:
|
| E122.1 Different DIs allocated with the same function | Cause: Multiple DIs assigned same function or DI function No. exceeds limit. Remedy:
|
| E122.2 Different DOs assigned with the same function | Cause: DO function No. exceeds maximum allowed. Remedy:
|
| 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:
|
| E122.4 Different VDIs assigned with the same function | Cause: Duplicate functions on VDIs or VDI function No. exceeds limit. Remedy:
|
| E122.5 DI and VDI assigned with the same function | Cause: Same function assigned to both a DI and a VDI. Remedy:
|
| E122.7 Fully closed-loop parameter setting error | Cause: Incorrect setting when fully closed-loop is used. Remedy:
|
| E122.9 Fully closed-loop function pin conflict | Cause: Frequency division output pin conflicts with fully closed loop second encoder pin. Remedy:
|
| E126.0 Process segment number error | Cause: Process segment number (H22.00) is not 0-15 or 1000. Remedy:
|
| E126.1 Process segment internal operation mode error | Cause: Technology segment operation mode is not 0, 1, 2, 3, 7, or 8. Remedy:
|
| E126.2 Position reference type error | Cause: Position reference type is not 00 (Absolute) or 10 (Incremental). Remedy:
|
| E136.0 Encoder ROM motor parameter check error | Cause: ROM parameters missing or inconsistent. Cable issues. Remedy:
|
| E136.1 Encoder ROM motor parameter read error | Cause: Cable disconnected or communication interference. Remedy:
|
| E150.0 STO safety state | Cause: STO input protection applies (Safety state active). Remedy:
|
| E150.1 STO input abnormal | Cause: Single-channel input of STO ineffective, or power supply abnormal. Remedy:
|
| E150.2 Buffer 5V voltage detection error | Cause: 5V supply to STO Buffer is abnormal (under/over voltage). Remedy:
|
| E150.3 STO input circuit hardware diagnosis failure | Cause: Short circuit on optocoupler of STO hardware. Remedy:
|
| E150.4 PWM buffer hardware diagnosis failure | Cause: Error on PWM Buffer IC during initialization. Remedy:
|
| 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:
|
| E201.1 Phase-U overcurrent | Cause: High current in Phase-U. Loose cables, short to ground, short between phases. Remedy:
|
| E201.2 Phase-V overcurrent | Cause: High current in Phase-V. Remedy:
|
| E201.4 Phase-N overcurrent | Cause: High current in DC-AC negative pole. Improper gains, encoder issues, braking current superposition. Remedy:
|
| E208.2 Encoder communication timeout | Cause: Drive fails to receive encoder data (3 cycles). Cable issues, interference, or faulty hardware. Remedy:
|
| E208.4 FPGA current loop operation timeout | Cause: Current loop time exceeds threshold. Remedy:
|
| E210.0 Short-to-ground detection error | Cause: Abnormal phase current or bus voltage during self-test. Cables or motor shorted to ground. Remedy:
|
| E234.0 Runaway | Cause: Feedback direction opposite to reference. Wrong phase sequence or encoder error. Remedy:
|
| E320.0 Resistor fault | Cause: Regenerative resistor overloaded. Remedy:
|
| 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:
|
| 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:
|
| E410.1 Main circuit de-energized | Cause: The power supply is disconnected during operation. Remedy:
|
| E420.0 Main circuit phase loss | Cause: Phase loss occurs on the three-phase servo drive. Remedy:
|
| E420.1 Main circuit PL signal detection error | Cause: Signal detection error related to phase loss. Remedy:
|
| E430.0 Control circuit power supply undervoltage | Cause: Control circuit voltage is below threshold (190V for 220V drive; 350V for 380V drive). Remedy:
|
| E500.0 Motor overspeed | Cause: The actual speed of the motor exceeds the overspeed threshold. Remedy:
|
| E500.1 Speed feedback overflow | Cause: The FPGA speed measurement overflows. Remedy:
|
| E500.2 Velocity feedback error 2 | Cause: Communication error occurred between boards of the drive. Remedy:
|
| E602.0 Angle auto-tuning error | Cause: Unusual jitter occurs on the encoder feedback during angle auto-tuning. Remedy:
|
| 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:
|
| E605.0 Bootstrap overspeed | Cause: The motor speed exceeds the rated speed when the servo drive (size A/B) is switched on. Remedy:
|
| E620.0 Motor overload | Cause: The accumulative heat of the motor reaches the fault threshold. Remedy:
|
| E625.0 Brake abnormality enabled | Cause: The brake fails when it is released (Motor shaft held while release signal active). Remedy:
|
| E626.0 Brake abnormality enabled | Cause: The brake fails when it closes (Motor shaft not held tightly). Remedy:
|
| E630.0 Motor stall | Cause: Actual speed < 10rpm but torque reference reaches limit for time defined in H0A.32. Remedy:
|
| E631.1 Motor brake fault | Cause: The brake circuit is faulty; 24V power or brake not connected. Remedy:
|
| E631.2 P-MOS open circuit | Cause: P-MOS open circuit occurred on the brake circuit. Remedy:
|
| E631.3 N-MOS open circuit | Cause: N-MOS open circuit occurred on the brake circuit. Remedy:
|
| E631.4 P-Mos short-circuited | Cause: The P-Mos in the brake circuit is short-circuited. Remedy:
|
| E631.5 N-Mos short-circuited | Cause: The N-Mos in the brake circuit is short-circuited. Remedy:
|
| E640.0 IGBT junction temperature too high | Cause: IGBT junction temperature reaches threshold defined by H0A.18. Remedy:
|
| E640.1 Diode overtemperature | Cause: Temperature of flywheel diode reaches threshold defined by H0A.18. Remedy:
|
| E650.0 Servo drive overtemperature | Cause: Temperature of servo drive power module is higher than overtemperature threshold. Remedy:
|
| E660.0 Motor overtemperature | Cause: The temperature of the air-cooled motor is too high. Remedy:
|
| E660.0 Motor overtemperature | Cause: The temperature of the air-cooled motor is too high. Remedy:
|
| E661.0 STune failure | Cause: During STune operation, the gain drops to the lower limit, stiffness <= 10. Remedy:
Cause: Check whether resonance that occurred during ITune operation cannot be suppressed. Remedy:
|
| 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:
Cause: Check whether resonance that occurred during ETune operation cannot be suppressed. Remedy:
|
| E663.0 ITune failure | Cause: Check whether resonance that occurred during ITune operation cannot be suppressed. Remedy:
|
| 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:
|
| E731.0 Encoder battery failure | Cause: The battery is not connected during power-off. Remedy:
Cause: The encoder battery voltage is too low (< 2.9V). Remedy:
|
| E733.0 Encoder multi-turn counting error | Cause: The encoder is faulty. Remedy:
|
| 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:
|
| 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:
|
| E740.2 Absolute encoder communication error | Cause: The encoder is wired improperly. Remedy:
Cause: The encoder cable is loosened. Remedy:
Cause: The encoder Z signal is being disturbed. Remedy:
Cause: The encoder is faulty. Remedy:
Cause: An error occurs on communication between servo drive and encoder. Remedy:
|
| E740.3 Absolute encoder single-turn calculation error | Cause: An encoder fault occurs. Remedy:
|
| E740.6 Encoder data write error | Cause: An error occurs when writing the position offset after angle auto-tuning. Remedy:
|
| E760.0 Encoder overtemperature | Cause: The temperature of the absolute encoder is too high. Remedy:
|
| E765.0 Nikon encoder over-temperature or overspeed | Cause: The temperature of the absolute encoder is too high. Remedy:
|
| 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:
|
| 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:
|
| 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:
|
| E770.3 BISS communication protocol timeout | Cause: BISS encoder communication data is not transmitted back to the drive. Remedy:
|
| E770.4 BISS communication CRC check error | Cause: BISS encoder communication data CRC check error (Interference). Remedy:
|
| E770.6 Fully closed-loop 2nd encoder initialization communication error | Cause: The encoder cable connections are incorrect or loosened. Remedy:
Cause: The servo drive is faulty. Remedy:
|
| E770.7 Fully closed-loop Inovance 2nd encoder communication error | Cause: The encoder is wired improperly. Remedy:
Cause: The encoder cable is loosened. Remedy:
Cause: The encoder Z signal is being disturbed. Remedy:
Cause: The encoder is faulty. Remedy:
|
| E939.0 Motor power cable failure | Cause: Motor power cables are broken or not connected. Remedy:
|
| E939.1 Phase-U power cable disconnected | Cause: Motor power cables disconnected (Phase U). Remedy:
|
| E939.2 Phase-V power cable disconnected | Cause: Motor power cables disconnected (Phase V). Remedy:
|
| E939.3 Phase-W power cable disconnected | Cause: Motor power cables disconnected (Phase W). Remedy:
|
| E994.0 Station number conflict | Cause: CANlink station No. conflict. Remedy:
|
| EA33.0 Internal encoder read/write check error | Cause: The serial incremental encoder cable is disconnected or loose. Remedy:
Cause: An error occurs when reading/writing the serial incremental encoder parameters. Remedy:
|
| EA33.1 Fully closed-loop Inovance 2nd encoder data read/write error | Cause: Encoder parameters are abnormal. Remedy:
|
| EB00.0 Position deviation too large | Cause: U/V/W output phase loss or incorrect phase sequence on the servo drive. Remedy:
Cause: The servo drive U/V/W cables or the encoder cable is disconnected. Remedy:
Cause: The motor is stalled due to mechanical factors. Remedy:
Cause: The gain values are too low. Remedy:
Cause: The position reference increment is too large. Remedy:
Cause: The value of 6065h (H0A.10) is insufficient for the operating conditions. Remedy:
Cause: The servo drive/motor is faulty. Remedy:
|
| EB00.1 Position deviation overflow | Cause: U/V/W output phase loss or incorrect phase sequence. Remedy:
Cause: Servo drive U/V/W cables or encoder cable disconnected. Remedy:
Cause: Motor stalled due to mechanical factors. Remedy:
Cause: Gain values are too low. Remedy:
Cause: Position reference increment too large. Remedy:
Cause: Value of 6065h is insufficient. Remedy:
Cause: Servo drive/motor faulty. Remedy:
|
| EB01.0 Position reference increment too large | Cause: The pulse reference increment exceeds the excessive reference threshold three times consecutively. Remedy:
|
| EB01.1 Individual position reference increment too large | Cause: The target position increment is too large. Remedy:
|
| 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:
|
| 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:
|
| EB02.1 Fully closed-loop position deviation overflow | Cause: The absolute value of the fully closed-loop position deviation is greater than 231. Remedy:
|
| EB03.0 Electronic gear ratio overrun | Cause: The electronic gear ratio exceeds the limit: (0.001–4000 x Encoder resolution/10000). Remedy:
|
| 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:
|
| 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:
|
| ED02.0 Modbus communication timeout | Cause: Modbus communication timeout occurred. Remedy:
|
| ED03.0 CANLink communication failure | Cause: The master is offline. Remedy:
|
| ED04.0 CANopen communication timeout | Cause: The slave reaches the time configured by the consumer or the node guarding time. Remedy:
|
| ED05.0 CANopen communication initialized | Cause: Errors (slave offline, heartbeat abnormal, etc.) occurred when NMT changes to initialization state. Remedy:
|
| ED08.0 CANopen bus PDO transmission length error | Cause: The length of content transmitted by PDO is inconsistent with configured mapping length. Remedy:
|
| ED11.0 CANopen sync period error too large | Cause: The SYNC period error exceeds the setpoint. Remedy:
|
| EE08.0 Synchronization lost | Cause: Slave receiving abnormally, Master transmitting abnormally, or Network switch failure. Remedy:
|
| EE08.1 Network status switchover error | Cause: The network switches from OP to non-OP when the servo drive is enabled. Remedy:
|
| EE08.3 Link is missing | Cause: Physical connection unstable, process data lost, or cable unplugged. Remedy:
|
| 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:
|
| EE09.1 Home setting error | Cause: The home offset is outside the software position limit or mechanical single-turn limit. Remedy:
|
| EE09.2 Gear ratio beyond the limit | Cause: Electronic gear ratio exceeds range or numerator/denominator is 0. Remedy:
|
| EE09.3 No synchronization signal | Cause: Improper clock config, inverse cable connection, or hardware damage. Remedy:
|
| EE09.5 PDO mapping beyond the limit | Cause: The mapping objects in TPDO or RPDO exceeds 40 bytes. Remedy:
|
| EE10.0 Protection against MailBox setting error | Cause: Master station configured incorrectly or Slave XML file incorrect. Remedy:
|
| EE10.1 SM2 setting error | Cause: Master station configured incorrectly or Slave XML file incorrect. Remedy:
|
| EE10.2 SM3 setting error | Cause: Master station configured incorrectly or Slave XML file incorrect. Remedy:
|
| EE10.3 PDO watchdog setting error | Cause: The master station is configured incorrectly. Remedy:
|
| EE10.4 Protection against incomplete PLL (no sync signal) | Cause: The master station is configured incorrectly. Remedy:
|
| EE11.0 ESI check error | Cause: XML file load failed during EtherCAT communication. Remedy:
|
| EE11.1 Failed to read e2prom by bus | Cause: The e2prom communication fails. Remedy:
|
| EE11.2 Failed to update e2prom by bus | Cause: Communication is normal but information in e2prom is wrong or lost. Remedy:
|
| EE11.3 ESI and drive mismatch | Cause: Downloaded XML file not compatible or modified unexpectedly. Remedy:
|
| EE16.0 MCU and ESC communication error | Cause: MCU and ESC communication timeout. Remedy:
|
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:
|