Description of Fault Codes
‑33‑
The communication between MCU and FPGA cannot be established.
Cause
Confirming Method
Solution
The communication
between MCU and FPGA
cannot be established.
The fault persists after the
servo drive is powered off
and on repeatedly.
Replace the servo drive.
● E102.1: FPGA initialization start error
Cause:
FPGA failed.
Cause
Confirming Method
Solution
FPGA cannot start.
The fault persists after the
servo drive is powered off
and on repeatedly.
Replace the servo drive.
● E102.8: FPGA and MCU version mismatch
Cause:
FPGA and MCU version mismatch.
Cause
Confirming Method
Solution
FPGA and MCU version
mismatch
View the FPGA software
version (H01.01), MCU
software version (H01.03)
and CPU1 software version
(H01.00) through the keypad
or Inovance software tool.
Check whether the non‑zero
values of the most
significant bit of these
software version numbers
are consistent.
Contact Inovance for
technical support. Update
the FPGA or MCU software.
● E104.1: MCU running timeout (MCU break down)
Cause:
MCU Access timeout (MCU break down).
Cause
Confirming Method
Solution
1. The MCU failed.
The fault persists after the
servo drive is powered off
and on repeatedly.
Replace the servo drive.
2. Real‑time communication
error between MCU and
FPGA.
● E104.2: FPGA running timeout (FPGA break down)
Cause:
FPGA running timeout (FPGA break down).