Description of Fault Codes
‑34‑
Cause
Confirming Method
Solution
1.FPGA failure
The fault persists after the
servo drive is powered off
and on repeatedly.
Replace the servo drive.
2.FPGA and MCU
communication
handshaking error
● E104.4: MCU command update timeout
Cause:
Take the moment when interrupt starts as the starting time, if the time when
commands are written to MCU is larger than the time when position and speed
regulators are started by FPGA, a warning will be reported.
Cause
Confirming Method
Solution
The system reports that the
encoder communication
time is set improperly or the
command calculation time
is too long.
The fault persists after the
servo drive is powered off
and on repeatedly.
1. Hide unnecessary
functions.
2. Replace the servo drive.
● E120.0: Unknown encoder model
Cause:
The servo drive detects the encoder model during initialization upon power‑on. If
the encoder model does not comply with the requirement, E120.0 occurs.
Cause
Confirming Method
Solution
1. The product (motor or
servo drive) code does not
exist.
Read the nameplates of the
servo drive and motor to
check whether SV670P series
servo drive and 23‑bit servo
motor are used. Meanwhile,
check whether H00.00
(motor code) is set to 14101.
If the motor code is
unknown, set H00.00 to
14101 when the SV670P
series servo drive and 23‑bit
servo motor are used.
Check the servo drive code
(H01.02) to see whether this
servo drive code exists.
If the drive code is absent,
set the servo drive model
correctly according to the
nameplate.
2. The power rating of the
motor does not match that
of the servo drive.
Check whether the servo
drive code (H01.02) matches
the serial‑type motor code
(H00.05).
Replace the unmatched
products.
The encoder type does not
match the servo drive.
Check whether the encoder
model is correct.
Rectify the motor code.
● E120.1: Unknown motor model
Cause:
The servo drive detects the motor model defined by H00.00 during initialization
upon power‑on. If the motor model does not exist, E120.1 occurs.