UFactory xArm - Page 223

223
A9
xArm is not ready.
Please check whether the errors have been cleared, whether the robot
arm has been enabled, and whether the robot arm status is set correctly.
A11
Other error.
Please contact technical support.
A12
Parameter error.
A20
Tool IO ID error.
A22
The end tool Modbus baud rate is incorrect.
A23
The end tool Modbus reply length error.
A31
Trajectory read/write failed.
A32
Trajectory read/write timeout.
A33
Playback trajectory timeout.
A41
Vacuum gripper wait timeout.
A100
Waiting for completion timeout.
A101
Too many failures to detect the status of the end effector.
A102
There are errors in the end effector
A103
The end effector is not enabled
For alarm codes that are not listed in the above table: enable the robotic arm and gripper. If
the problem remains unsolved after power on/off for multiple times, please contact technical
support.
xArm-Python-SDK Error Handling:
When designing the robotic arm motion path with the Python library, if
the robotic arm error (see Appendix for Alarm information) occurs, then
it needs to be cleared manually. After clearing the error, the robotic arm
should be motion enabled.
Python library error clearing steps: (Please check GitHub for details on
the following interfaces)
a. error clearing: clean_error()
b. Re-enable the robotic arm: motion_enable(true)