CR User Manual Error Code en
CR User Manual Error Code en
Algorithm error
Error ID Description Solution Level
37 The Joint angle is changed over 180° Reselect the movement points 5
41 Collision backoff in the first axis Please contact technical support engineer 5
42 Collision backoff in the second axis Please contact technical support engineer 5
43 Collision backoff in the third axis Please contact technical support engineer 5
44 Collision backoff in the fourth axis Please contact technical support engineer 5
45 Collision backoff in the fifth axis Please contact technical support engineer 5
46 Collision backoff in the sixth axis Please contact technical support engineer 5
Position deviation of joint is too large Check whether the load parameters and
134 0
when enabled mounting angle are correct
144 The selected points are wrong Enter the correct parameters 5
The target point is out of workspace Check whether the target point is in the
146 5
when stepping the robot workspace of the robot
The current motion command does not The current motion command does not
160 5
support pause support pause
Error ID Description Solution Level
Error in setting the minimum value of Reset the value or contact technical
168 5
feedback voltage support engineer
Error in setting the maximum value of Reset the value or contact technical
169 5
feedback voltage support engineer
174 Abnormal energy-feedback time Check if the input power supply and load 5
detection are standardized, or contact technical
Error ID Description Solution Level
support engineer
178 ForceControl sensor data is abnormal Check the force control sensor 5
179 ForceControl sensor is not enabled Enable the force control sensor 5
182 Tool 24V output overcurrent Check whether the hardware is working 5
properly, restart the controller, or contact
technical support engineer
210 Wrong parameters for linear weaving Enter the correct parameters 5
211 Wrong parameters for arc weaving Enter the correct parameters 5
224 Tool TCP/elbow crossing the safety wall Jog the robot back to the safety wall 5
The tracking difference of Joint 1 is too System error, restart controller or contact
225 5
large technical support engineer
The tracking difference of Joint 2 is too System error, restart controller or contact
226 5
large technical support engineer
227 The tracking difference of Joint 3 is too System error, restart controller or contact 5
Error ID Description Solution Level
The tracking difference of Joint 4 is too System error, restart controller or contact
228 5
large technical support engineer
The tracking difference of Joint 5 is too System error, restart controller or contact
229 5
large technical support engineer
The tracking difference of Joint 6 is too System error, restart controller or contact
230 5
large technical support engineer
240 Robot end exceeds pressure threshold Please contact technical support engineer 5
241 Robot end reach distance exceeds limit Please contact technical support engineer 5
The following error of the first axis is too System error, restart controller or contact
242 5
large technical support engineer
The following error of the second axis is System error, restart controller or contact
243 5
too large technical support engineer
The following error of the third axis is System error, restart controller or contact
244 5
too large technical support engineer
The following error of the fourth axis is System error, restart controller or contact
245 5
too large technical support engineer
The following error of the fifth axis is too System error, restart controller or contact
246 5
large technical support engineer
The following error of the sixth axis is System error, restart controller or contact
247 5
too large technical support engineer
The steady-state error of the first axis is System error, restart controller or contact
248 5
too large technical support engineer
The steady-state error of the second axis System error, restart controller or contact
249 5
is too large technical support engineer
The steady-state error of the third axis is System error, restart controller or contact
250 5
too large technical support engineer
The steady-state error of the fourth axis is System error, restart controller or contact
251 5
too large technical support engineer
Error ID Description Solution Level
The steady-state error of the fifth axis is System error, restart controller or contact
252 5
too large technical support engineer
The steady-state error of the sixth axis is System error, restart controller or contact
253 5
too large technical support engineer
The current command does not support Please adjust the command to avoid
254 5
resuming operation after collision obstacles
Failed to open the mechanical parameter Check the file path and restart the
4096 | 0x1000 5
file controller
32770 | 0x8002 Parameters of DO command are wrong Enter the correct parameters 5
32771 | 0x8003 Parameters of DI command are wrong Enter the correct parameters 5
Error ID Description Solution Level
32777 | 0x8009 Index out of range in DOGroup parameter Enter the correct parameters 5
32785 | 0x8011 Parameters of AI command are wrong Enter the correct parameters 5
33024 | 0x8100 CP command has no input parameters Enter the correct parameters 5
Error ID Description Solution Level
33280 | 0x8200 Arch command has no input parameters Enter the correct parameters 5
33536 | 0x8300 LimZ command has no input parameters Enter the correct parameters 5
33792 | 0x8400 Speed command has no input parameters Enter the correct parameters 5
Ratio parameter of Speed command is out Enter the correct parameters, range:
33793 | 0x8401 5
of range [1,100]
34048 | 0x8500 Accel command has no input parameters Enter the correct parameters 5
Ratio parameter of Accel command is out Enter the correct parameters, range:
34049 | 0x8501 5
of range [1,100]
34304 | 0x8600 Jerk command has no input parameters Enter the correct parameters 5
Ratio parameter of Jerk command is out Enter the correct parameters, range:
34305 | 0x8601 5
of range [1,100]
35328 | 0x8A00 AccelR command has no input Enter the correct parameters 5
Error ID Description Solution Level
parameters
35584 | 0x8B00 JerkS command has no input parameters Enter the correct parameters 5
Ratio parameter of JerkS icommand is out Enter the correct parameters, range:
35585 | 0x8B01 5
of range [1,100]
35840 | 0x8C00 JerkR command has no input parameters Enter the correct parameters 5
Ratio parameter of JerkR command is out Enter the correct parameters, range:
35841 | 0x8C01 5
of range [1,100]
36096 | 0x8D00 Go command has no input parameters Enter the correct parameters 5
36097 | 0x8D01 Go command has no point parameter Enter the correct parameters 5
36098 | 0x8D02 Point parameter of Go command is wrong Enter the correct parameters 5
36100 | 0x8D04 MoveJ command has no input parameters Enter the correct parameters 5
36101 | 0x8D05 MoveJ command has no point parameters Enter the correct parameters 5
36102 | 0x8D06 MoveJ command has no point parameters Enter the correct parameters 5
36103 | 0x8D07 Point parameter of RP command is wrong Enter the correct parameters 5
36105 | 0x8D09 Point parameter of RJ command is wrong Enter the correct parameters 5
36107 | 0x8D0B GoR command has no input parameters Enter the correct parameters 5
36111 | 0x8D0F GoIO command has no input parameters Enter the correct parameters 5
36120 | 0x8D18 MoveJ command has no point parameters Enter the correct parameters 5
36352 | 0x8E00 Move command has no input parameters Enter the correct parameters 5
36353 | 0x8E01 Move command has no point parameters Enter the correct parameters 5
36608 | 0x8F00 Arch3 command has no input parameters Enter the correct parameters 5
36609 | 0x8F01 Arch3 command has no point parameters Enter the correct parameters 5
36864 | 0x9000 Jump command has no input parameters Enter the correct parameters 5
36865 | 0x9001 Jump command has no point parameters Enter the correct parameters 5
40960 | 0xA000 Circle3 command has no input parameters Enter the correct parameters 5
40961 | 0xA001 Circle3 command has no point parameters Enter the correct parameters 5
41216 | 0xA100 Spiral command has no input parameters Enter the correct parameters 5
41217 | 0xA101 Spiral command has no point parameters Enter the correct parameters 5
41728 | 0xA300 Liner command has no input parameters Enter the correct parameters 5
41984 | 0xA400 The parameter of Jack direction is wrong Enter the correct parameters 5
41985 | 0xA401 The parameter of Jack speed is wrong Enter the correct parameters 5
41986 | 0xA402 The parameter of Jack force is wrong Enter the correct parameters 5
41988 | 0xA404 The parameter of Jack mode is wrong Enter the correct parameters 5
42497 | 0xA601 FCAct command has no input parameters Enter the correct parameters 5
Error ID Description Solution Level
42498 | 0xA602 FCAct parameter out of range 0/1 Enter the correct parameters 5
42505 | 0xA609 FCCalib has no input parameters Enter the correct parameters 5
42507 | 0xA60B FCCalib optional parameter error Enter the correct parameters 5
42508 | 0xA60C Optional parameter “IsInside” error Enter the correct parameters 5
42509 | 0xA60D Optional parameter “timeout” error Enter the correct parameters 5
42510 | 0xA60E Optional parameter “IsAlarm” error Enter the correct parameters 5
42511 | 0xA60F FCCond parameter “Force” not exist Enter the correct parameters 5
42512 | 0xA610 FCCond parameter “Force” error Enter the correct parameters 5
42513 | 0xA611 FCCond optional parameter “Force” error Enter the correct parameters 5
42514 | 0xA612 FCCond TCP speed parameter not exist Enter the correct parameters 5
42515 | 0xA613 FCCond TCP speed parameter error Enter the correct parameters 5
42517 | 0xA615 FCCond parameter “Torque” not exist Enter the correct parameters 5
42518 | 0xA616 FCCond parameter “Torque” error Enter the correct parameters 5
42520 | 0xA618 FCCond Displac not exit Enter the correct parameters 5
Error ID Description Solution Level
42521 | 0xA619 FCCond parameter Displac error Enter the correct parameters 5
42523 | 0xA61B FCRef optional parameter “SpeedF” error Enter the correct parameters 5
42527 | 0xA61F FCRef optional parameter “SpeedL” error Enter the correct parameters 5
42544 | 0xA630 FCRefForce parameter not exist Enter the correct parameters 5
42545 | 0xA631 FCRefForce optional parameter error Enter the correct parameters 5
42547 | 0xA633 FCRefTorque parameter not exist Enter the correct parameters 5
42548 | 0xA634 FCRefTorque optional parameter error Enter the correct parameters 5
42550 | 0xA636 FCRefline has no input parameters Enter the correct parameters 5
42551 | 0xA637 FCRefline optional parameter error Enter the correct parameters 5
42553 | 0xA639 FCRefRot parameter not exist Enter the correct parameters 5
42554 | 0xA63A FCRefrotate optional parameter error Enter the correct parameters 5
42555 | 0xA63B FCRef parameter “rotate” error Enter the correct parameters 5
42556 | 0xA63C FCRefSpiral parameter not exist Enter the correct parameters 5
42557 | 0xA63D FCRefSpiral optional parameter error Enter the correct parameters 5
42752 | 0x7000 SetSafeSkin parameter not exist Enter the correct parameters 5
42754 | 0x7002 SetSafeSkin parameter out of range Enter the correct parameters 5
45079 | 0xB017 Optional parameter “CP” is wrong Enter the correct parameters 5
45080 | 0xB018 Optional parameter "TooL” is wrong Enter the correct parameters 5
45081 | 0xB019 Optional parameter "user” is wrong Enter the correct parameters 5
45082 | 0xB01A Optional parameter “Speed” is wrong Enter the correct parameters 5
45083 | 0xB01B Optional parameter “SpeedS” is wrong Enter the correct parameters 5
45084 | 0xB01C Optional parameter “Accel” is wrong Enter the correct parameters 5
Error ID Description Solution Level
45085 | 0xB01D Optional parameter “AccelS” is wrong Enter the correct parameters 5
45086 | 0xB01E Optional parameter “Arch” is wrong Enter the correct parameters 5
45087 | 0xB01F Optional parameter “start” is wrong Enter the correct parameters 5
45088 | 0xB020 Optional parameter “zlimit” is wrong Enter the correct parameters 5
45089 | 0xB021 Optional parameter “end” is wrong Enter the correct parameters 5
45090 | 0xB022 Optional parameter “sync” is wrong Enter the correct parameters 5
45091 | 0xB023 Optional parameter “arm” is wrong Enter the correct parameters 5
45095 | 0xB027 “tool” list in setTool params is wrong Enter the correct parameters 5
45096 | 0xB028 “user” list in setUser params is wrong Enter the correct parameters 5
45135 | 0xB04F MoveR command type error Enter the correct parameters 5
It is not allowed to set the installation Disable the robot, then set the installation
46098 | 0xB412 0
angle when the robot is in enabled status angle
46080 | 0xB400 The parameter of ExcitMode() is wrong Enter the correct parameters 5
Error ID Description Solution Level
SendCam("CAMn","string") param
49457 | 0xC131 number error, need two parameters, one Enter the correct parameters 5
camera name, one string
SendCam("CAMn","string") param 1
49458 | 0xC132 Enter the correct parameters 5
type error, string only
SendCam("CAMn","string") param 2
49459 | 0xC133 Enter the correct parameters 5
type error, string only
SendCam("CAMn","string") param 1
49460 | 0xC134 Enter the correct parameters 5
content error, can not find this camera!
49473 | 0xC141 RecvCam("CAMn") param number error Enter the correct parameters 5
Not in OP status, in PREOP status, the Check whether the hardware is working
49674 | 0xC20A system will try to switch from station to properly, restart the controller, or contact 5
OP technical support engineer
49666 | 0xC202 ModbusCreate input param error Enter the correct parameters 5
49669 | 0xC205 GetInRegs input param error Enter the correct parameters 5
49670 | 0xC206 SetHoldRegs input param error Enter the correct parameters 5
49671 | 0xC207 GetHoldRegs input param error Enter the correct parameters 5
49672 | 0xC208 GetCoils input param error Enter the correct parameters 5
49673 | 0xC209 SetCoils input param error Enter the correct parameters 5
Parameter 1 of InverseSolution() is of
49793 | 0xC281 Enter the correct parameters 5
wrong type
Parameter 2 of InverseSolution() is of
49794 | 0xC282 Enter the correct parameters 5
wrong type
Parameter 3 of InverseSolution() is of
49795 | 0xC283 Enter the correct parameters 5
wrong type
Parameter 4 of InverseSolution() is of
49796 | 0xC284 Enter the correct parameters 5
wrong type
Parameter 5 of InverseSolution() is of
49797 | 0xC285 Enter the correct parameters 5
wrong type
60949 | 0xEE15 ModbusClose input param error Enter the correct parameters 0
{x,y,z,a,b,c}
Parameter 3 of MoveToolR() or
49750 | 0xC256 Enter the correct parameters 5
MoveUserR() has wrong content
50193 | 0xC411 Wrong number of tcpspeed () parameters Enter the correct parameters 5
50195 | 0xC413 Tcpspeed() internal execution error Enter the correct parameters 5
50227 | 0xC433 Servoj() optional parameter does not exist Enter the correct parameters 5
Cause:
Check if the hardware E-Stop button is
Failed to exit the drag mode and disable pressed.
1000 | 0x03E8 0
the robot Hardware:
Release the hardware E-Stop button, and
restart the controller.
Cause:
Check if the hardware E-Stop button is
pressed.
1004 | 0x03Ec Failed to exit the drag mode 0
Hardware:
Release the hardware E-Stop button, and
restart the controller.
Cause:
The modbus configuration is abnormal.
Check whether the modbus enabled coil
address and the disabled coil address are
occupied.
1005 | 0x03Ed Abnormal remote modbus configuration 0
Software:
1. The enabled coil address must be set to
100.
2. The disabled coil address must be set to
101.
Cause:
There is a null-valued variable in the Lua
code.
1006 | 0x03EE Attempt to compare number with nil. 0
Software:
Check if there are any null-valued
variables in the Lua code.
Cause:
Check if the hardware E-Stop button is
pressed.
1007 | 0x03EF Power-on failure, controller internal error. 0
Hardware:
Release the hardware E-Stop button, and
restart the controller.
Cause:
Check if the hardware E-Stop button is
Power-on failure, emergency stop pressed.
1008 | 0x03F0 0
triggered during power-on. Hardware:
Release the hardware E-Stop button, and
restart the controller.
Error ID Description Solution Level
...
8197 | 0x2005 Failed to parse the project file Check the file, or rerun the debugger 0
8198 | 0x2006 Project file content is empty Check the file, or rerun the debugger 0
8199 | 0x2007 Project file does not exist Check the file, or rerun the debugger 0
...
Cause:
There are obstacles in the area.
16384 | 0x4000 Obstacle detected in the area Environment: 5
Clear the obstacles and continue to run the
robot.
16386 | 0x4002 Inverse kinematics failed, wrong points Clear the alarm and re-teach points. 5
Cause:
1. SafeSkin is not installed.
2. SafeSkin is damaged.
49920 | 0xC300 SafeSkin not installed 5
Hardware:
1. Check if the SafeSkin is damaged.
2. Install SafeSkin before using this API.
Cause:
Codesys detected that the PDO variable
“OnlineStatus” for the tool IO has not
Tool IO is disconnected, please check the changed for a period of time.
60968 | 0xEE28 EtherCAT link between the controller and Software: 0
the robot body. Use Codesys to check whether the
heartbeat of the tool IO changes. Track the
heartbeat value curve and observe if
changes are continuous without pauses.
Error ID Description Solution Level
No power-on signal
Check whether the hardware is working properly, restart
1773 | 0x06ED feedback from the energy- 0
the controller, or contact technical support engineer
feedback board
...
Cause:
The controller has detected no change in the heartbeat
value of the energy-feedback board.
Software:
Modbus of energy- Use Codesys to check whether the voltage data of the
20480 | 0x5000 feedback board is energy-feedback board (V2.3.1 and above, check Rsv0) is 0
disconnected normal and changing.
Hardware:
Check whether the 485 wiring between the energy-
feedback board and safety I/O inside the controller is
normal.
Cause:
The CR controller routes 220V AC through an AC
contactor to a 48V switch-mode power supply, then to a
48V regulated power supply, and finally to the 48V input
of the energy-feedback board. When powering on the
robot body, the energy-feedback board checks the 48V
Voltage above 49.5V
20481 | 0x5001 input and triggers an alarm when it detects a voltage value 0
before powering
above 49.5V.
Hardware:
1. Check if the power supply and voltage are normal.
2. If the alarm persists after multiple restarts, it might be
the controller power failure, please contact the hardware
engineer for further assistance.
Cause:
The current-limiting chip monitors the current on the bus.
If the current is excessively high, it emits an abnormal
signal. Upon detecting this signal, the software triggers an
alarm and powers off the robot body to prevent damage
due to excessive current.
Hardware:
The hardware circuit
1. Check if the robot body has experienced any serious
20483 | 0x5003 related to the current- 0
collisions.
limiting chip is abnormal
2. Check if there is a short circuit in the robot body. You
can turn off the power, unplug the heavy-duty cable, and
restart the controller to see if the alarm persists.
3. If there is no alarm after restarting, it may be a problem
with the robot body, and the body needs to be replaced. If
the alarm persists after multiple restarts, the hardware may
be damaged and the board needs to be replaced.
Cause:
After the robot body is powered on, the bus voltage is
continuously monitored. An alarm is triggered if the bus
voltage exceeds 56V.
Hardware:
Voltage above 56V after
20484 | 0x5004 1. Check if the robot body has experienced any serious 0
powering
collisions.
2. If the alarm occurs during operation, it is possible that
the energy-feedback resistor is damaged and fails to
function properly, leading to a continuous increase in
voltage that triggers the alarm.
Cause:
It may be that the power supply is abnormal and exceeds
the operating voltage range of the regulator chip.
Hardware:
Internal first stabilized 1. Check if the power supply and voltage are normal.
20486 | 0x5006 0
voltage is abnormal 2. Check if the power supply is sufficient.
3. If the power supply is normal and the alarm persists
after multiple restarts, it might be the hardware failure,
please contact the hardware engineer for further
assistance.
Cause:
It may be that the power supply is abnormal and exceeds
the operating voltage range of the regulator chip.
Hardware:
Internal second stabilized 1. Check if the power supply and voltage are normal.
20487 | 0x5007 0
voltage is abnormal 2. Check if the power supply is sufficient.
3. If the power supply is normal and the alarm persists
after multiple restarts, it might be the hardware failure,
please contact the hardware engineer for further
assistance.
Cause:
After the controller is powered on, it will not immediately
output 48V to the robot body. There will be a slow-start
process first (pre-charging of the body). Once the body
voltage rises to 44V, the slow-start is discontinued, and the
48V power supply is activated. This process is designed to
prevent damage to the body caused by powering on too
quickly. Before the slow-start, the output voltage is
Abnormal output voltage
checked, and an alarm is triggered if the voltage exceeds
20488 | 0x5008 before the robot is slow- 0
49.5V for more than 3 seconds to prevent the circuit from
starting
directly burning out the MOSFET.
Hardware:
1. Ensure the robot body is powered on in a stationary
status.
2. Check if the power supply and voltage are normal.
3. If the alarm persists after multiple restarts, it might be
the hardware failure, please contact the hardware engineer
for further assistance.
Cause:
During deceleration, energy is dissipated through heat
generated by the energy-feedback resistor, reducing the
bus voltage. The software monitors the current through the
resistor, triggering an alarm if the current exceeds 2.55A
Power protection for
20490 | 0x500A for more than 5 seconds to prevent the resistor from 0
cement resistor
burning out.
Hardware:
Potential abnormalities in the circuit of the energy-
feedback board, contact the development team or
hardware engineer for assistance.
Cause:
The software continuously monitors the bus current and
triggers an alarm when it detects that the bus current
exceeds the limit values (CR3: 10A, CR5/7: 26A,
CR10/12: 47.5A, CR16: 47.5A).
The bus current is higher Operation:
20491 | 0x500B 0
than 26A Generally, this alarm does not appear. If it is running at
full load and speed, or bad operating conditions, this alarm
may appear. You can reduce the speed or decrease the
load. If it is necessary to operate under current conditions,
contact the development team to discuss adjusting the
current limit.
Cause:
After the controller is powered on, it will not immediately
output 48V to the robot body. There will be a slow-start
process first (pre-charging of the body). Once the body
voltage rises to 44V, the slow-start is discontinued, and the
48V power supply is activated. This process is designed to
prevent damage to the body caused by powering on too
The energy-feedback quickly. Throughout the slow-start process, the system checks for
20492 | 0x500C board alarms when the energy feedback, triggering an alarm if detected to prevent the 0
robot is slow-starting circuit from directly burning out the MOSFET.
Hardware:
1. Ensure the robot body is powered on in a stationary
status.
2. Check if the power supply and voltage are normal.
3. If the alarm persists after multiple restarts, it might be
the hardware failure, please contact the hardware engineer
for further assistance.
Cause:
Communication between the safety I/O board and the
energy-feedback board uses the 485-bus Modbus protocol.
The safety I/O board periodically reads data from the
energy-feedback board. If communication fails or the
energy-feedback board’s heartbeat remains unchanged for
The communication of
more than 2 seconds, an alarm is triggered.
24584 | 0x6008 energy-feedback board 0
Software:
Modbus is interrupted
Update the firmware to match the version of the controller.
Hardware:
After updating, if the alarm persists after multiple restarts,
it may be caused by bad wiring of the 485 bus in the
controller or hardware failure, please contact the hardware
engineer for further assistance.
...
Hardware:
1. Power off the controller and restart it. At the same time,
observe the controller to see if there is clicking noise of
the AC contactor.
2. If there is clicking noise of the contactor but the
software still reports an error, check if there is poor wiring
inside the controller.
3. If there is no clicking noise of the contactor and the
error persists after multiple restarts, the AC contactor may
be damaged.
Cause:
AC detection is used to monitor the power status. For AC
controller, the AC power goes through waveform shaping
before sending a detection signal to the software. The
software checks the waveform frequency, if the detected
frequency is less than 20Hz or continuously zero, an alarm
is triggered. For DC controller, the detection signal will be
a high-level signal. The software monitors the signal level,
AC detection board status if a low level is detected for more than 100ms, an alarm is
1775 | 0x06EF 0
error triggered.
Hardware:
1. Check if the rocker switch is off or if the power cable
has been unplugged.
2. Check if the power supply is normal.
3. If the alarm persists after multiple restarts, it may be
caused by bad wiring of the detection cables inside the
controller or hardware failure, please contact the hardware
engineer for further assistance.
Cause:
The E-Stop button is pressed.
12288 | 0x3000 Emergency stop detected Hardware: 0
Release the E-Stop button, clear the alarm and power on
again.
body.
Software:
Refer to the solutions for the related alarms, clear the
alarms, and power on the body again.
Cause:
After the robot body is powered on, the AC contactor is
closed. The software continuously monitors the status of
the contactor, where a closed status is indicated by a low
level signal. If a high level signal is detected continuously
for 1 seconds, it is determined that there is a contactor
anomaly.
Hardware:
The contactor did not
24578 | 0x6002 1. Power off the controller and restart it. At the same time, 0
close as required
observe the controller to see if there is clicking noise of
the AC contactor.
2. If there is clicking noise of the contactor but the
software still reports an error, check if there is poor wiring
inside the controller.
3. If there is no clicking noise of the contactor and the
error persists after multiple restarts, the AC contactor may
be damaged.
triggered.
Hardware:
1. Check if the rocker switch is off or if the power cable
has been unplugged.
2. Check if the power supply is normal.
3. If the alarm persists after multiple restarts, it may be
caused by bad wiring of the detection cables inside the
controller or hardware failure, please contact the hardware
engineer for further assistance.
Cause:
The safety I/O board checks the bus communication status
5 minutes after the controller is powered on to ensure it is
After 5 minutes of power-
functioning correctly.
on, the data of the energy-
24582 | 0x6006 Software: 0
feedback board did not
1. Use Codesys to check the communication status of each
update for 1 minute
slave.
2. Check if the PDO variable “ControlSource” on the
safety I/O is set to 1.
Cause:
This alarm occurs when the switch on the controller is
The switch on the
24583 | 0x6007 pressed to shut down. 0
controller is pressed
Operation:
Turn the switch on.
Cause:
There is a 24V super capacitor on the AC detection board
of the CR controller. After the controller is powered on, it
charges the capacitor. The software monitors the charging
status. When the voltage is higher than 16.4V, the software
detects a high level signal. When the voltage is lower than
16.4V, the software detects a low level signal. An alarm is
Abnormal charging
triggered if a low level signal is detected continuously for
24588 | 0x600C detection of 24V super 0
200ms.
capacitor (modbus)
Hardware:
1. Restart the controller.
2. If the alarm persists after restart, it is possible that the
fuse in the charging circuit of the energy-feedback board is
damaged (the energy-feedback board may need to be
replaced), contact the hardware engineer for further
assistance.
Cause:
The hardware E-Stop The hardware E-Stop button is pressed.
49153 | 0xC001 5
button is pressed Hardware:
Release the hardware E-Stop button.
Cause:
The software E-Stop The software E-Stop button is pressed.
49154 | 0xC002 5
button is pressed Software:
Release the software E-Stop button.
Cause:
The user emergency stop The user emergency stop is triggered.
49155 | 0xC003 5
is triggered Hardware:
Recover the user emergency stop wiring.
Cause:
Safety I/O is Codesys detected that the PDO variable “OnlineStatus”
disconnected, please for the safety I/O has not changed for a period of time.
60960 | 0xEE20 check the EtherCAT link Software: 0
between the controller Use Codesys to check whether the heartbeat of the safety
and the safety I/O board. I/O changes. Track the heartbeat value curve and observe
if changes are continuous without pauses.
Servo error
Error ID Description Solution Level
Difference between the set position Check whether the motor and circuit are
16 and current position exceeds the working properly, and adjust the servo 0
range parameters
35 The servo drive is abnormal when System error, please contact technical 0
Error ID Description Solution Level
Working speed is higher than the System error, please contact technical
40 0
expected speed support engineer
The SoftMotion axis is not in the Switch the SoftMotion axis to the
81 0
required status corresponding status
The function does not support System error, please contact technical
85 0
virtual or logical mode support engineer
86 The bit width is invalid Reset the bit width, range: [8, 32] 0
93 The pulse value of modulus period System error, please contact technical 0
Error ID Description Solution Level
Servo has no response to the reset System error, please contact technical
121 0
command support engineer
is abnormal.
Structure:
1. Check whether the brake can be switched
on normally.
2. Switch on the brake and check whether
the joint rotation is normal.
3. Check whether the load exceeds the
nominal value of the load curve in the user
guide.
Cause:
One phase of the collected UVW three-phase
current significantly deviates from its zero-
point current, exceeding the protection
The current offset of the zero point
9088 | 0x2380 threshold. 0
is too high
Hardware:
1. Check whether the sampling resistor value
is normal.
2. Check whether the bus voltage is normal.
Cause:
The output speed is higher than the
maximum speed of motor.
33920 | 0x8480 Motor overspeed 0
Software:
Check whether the controller and servo
versions are compatible.
Cause:
1. Check if the robot has collided and caused
Difference between the set speed
the alarm to appear on the corresponding
33921 | 0x8481 and current speed exceeds the 0
joint motor.
range
2. Check if the servo parameters are
configured properly.
Cause:
1. Check if the robot has collided and caused
Difference between the set position
the alarm to appear on the corresponding
34321 | 0x8611 and current position exceeds the 0
joint motor.
range
2. Check if the servo parameters are
configured properly.
Cause:
The planned command of the controller is
abnormal.
34322 | 0x8612 Position is out of range 0
Software:
Check whether the controller and servo
versions are compatible.
Cause:
The bus voltage detected exceeds the
threshold for each model.
12816 | 0x3210 Voltage between PN is too high 0
Hardware:
1. Check if the voltage output from the
switch, adapter, or AGV battery is normal.
Cause:
The MCU detects that the temperature
register is higher than 90°C.
Environment:
Check whether the robot has been operating
in high-temperature conditions for an
extended period or running under excessive
17168 | 0x4310 Driver temperature is too high load. 0
Hardware:
Check if the servo driver has short-circuited
or burnt out.
Solution:
1. Disable the robot, power off the robot
body and cool it down for a period of time.
2. Replace the servo power board.
Cause:
Incorrect UVW wiring.
13184 | 0x3380(不对
Driver output phase sequence error Hardware: 0
外)
Check the wiring sequence of the UVW
three-phase cables.
12592 | 0x3130(不对
Driver input phase lost Check if the power input terminal is normal. 0
外)
Troubleshooting:
1. Check if the connection between the servo
control board and the servo power board is
loose.
21008 | 0x5210(不对 Driver board identification is 2. Check if the servo power board is
0
外) abnormal damaged.
Solution:
Ensure that the connection between the servo
control board and the servo power board is
secure.
Hardware:
1. Check if the motor is jammed due to a
mechanical failure.
2. Check if the motor brake is functioning
properly or is damaged.
28961 | 0x7121 Motor is in Locked-Rotor status 0
Solution:
If the motor shaft can rotate normally with
the brake on and the motor is disabled, you
can enable the motor and carry out the
operation of the whole unit.
Hardware:
1. Check the drive circuit for shorts.
2. Check whether the sampling resistor value
is abnormal.
Structure:
1. Check whether the brake can be switched
on normally.
2. Switch on the brake and check whether
the joint rotation is normal.
3. Check whether the load exceeds the
nominal value of the load curve in the user
guide.
Hardware:
1. Check if the motor is jammed due to a
mechanical failure.
2. Check if the motor brake is functioning
29059 | 0x7183 Failed to enable 0
properly or is damaged.
3. Check if the direction of the first swing of
the motor is the direction of getting rid of the
teeth.
Not in OP status, in Init status, the Check whether the hardware is working
60945 system will try to switch from properly, restart the controller, or contact 0
station to OP technical support engineer
Cause:
Codesys detected that the PDO variable
“OnlineStatus” for the universal IO has not
Universal IO is disconnected,
changed for a period of time.
please check the EtherCAT link
60961 | 0xEE21 Software: 0
between the robot body and the
Use Codesys to check whether the heartbeat
universal IO board.
of the universal IO changes. Track the
heartbeat value curve and observe if changes
are continuous without pauses.
12290 | 0x3002 Axis 1 not in Bus mode Check if Axis 1 cable is damaged or 0
disconnected, or contact technical support
Error ID Description Solution Level
engineer.
Cause:
The servo 1 MCU detects that the
temperature register is higher than 90°C.
Environment:
Check whether the robot has been operating
Servo 1 MCU temperature exceeds
12298 | 0x300A in high-temperature conditions for an 0
alarm threshold
extended period or running under excessive
load.
Hardware:
Check if the servo driver has short-circuited
or burnt out.
Cause:
The servo 3 MCU detects that the
temperature register is higher than 90°C.
Environment:
Check whether the robot has been operating
Servo 3 MCU temperature exceeds
12300 | 0x300C in high-temperature conditions for an 0
alarm threshold
extended period or running under excessive
load.
Hardware:
Check if the servo driver has short-circuited
or burnt out.
Cause:
The servo 4 MCU detects that the
temperature register is higher than 90°C.
Environment:
Check whether the robot has been operating
Servo 4 MCU temperature exceeds
12301 | 0x300D in high-temperature conditions for an 0
alarm threshold
extended period or running under excessive
load.
Hardware:
Check if the servo driver has short-circuited
or burnt out.
Cause:
The servo 5 MCU detects that the
temperature register is higher than 90°C.
Environment:
Check whether the robot has been operating
Servo 5 MCU temperature exceeds
12302 | 0x300E in high-temperature conditions for an 0
alarm threshold
extended period or running under excessive
load.
Hardware:
Check if the servo driver has short-circuited
or burnt out.