Operate the Real Arm · xArm 6 · Step 6 of 9
Respond to an Abnormal Condition
Something will go wrong sooner or later. What matters is the order: make it safe first, then find the cause, then recover, with lab staff. Never create a fault on purpose to practice this: use the simulator.
The Rule for Every Error
- When an error occurs, the arm stops at once and discards its queued commands, and the error must be cleared by hand before normal work goes on1.
- Stop the arm and ask for help whenever its condition is uncertain2.
- Before any restart after an emergency stop, make sure the restart motions will not hit anything3.
Warning
Common Conditions
| Condition | How it is detected | Immediate safe response | Likely cause | Recovery procedure |
|---|---|---|---|---|
| The control box's emergency stop is pressed | Studio shows error code C1: the emergency stop button on the control box is pushed in6 | Keep clear. The arm loses power, brakes slightly and falls, and a part it holds can drop789 | Someone pressed the button: in an emergency, or by accident7 | With lab staff, find out why it was pressed and make sure the restart motions will not hit anything. Turn the button in the direction of its arrow to release it, then click Enable Robot3106 |
| A collision stop | The arm stops, and Studio shows error code C31, abnormal current in the arm, with the joint, its torque, the collision sensitivity, the payload and the mounting setting11. With collision rebound on, the arm first moves back a little12 | Click STOP and keep clear. Press the emergency stop if anyone is hurt or at risk137 | The arm hit something, or the mounting setting does not match the real arm, which causes frequent collision stops1114 | Check whether the arm really collided, and clear the obstacle11. Lab staff decide what else to check, such as the payload and mounting settings; then the error is cleared2141 |
| Loss of communication between the computer and the arm | With Network Monitoring on, Studio checks whether the connection is interrupted while you hold a motion button in Live Control15. A Python program gets code -1, the arm not connected16 | If the arm is moving and Studio does not respond, press the emergency stop7 | The network cable is out or damaged, the computer's address is wrong, or a wireless link is in use1718 | Reconnect the cable directly to the control box, check your computer's address1718, then in Studio enter the arm's address in the IP search field and click Connect Server again19. Read the arm's state before any move20 |
| The suction does not hold, or the part drops | The part does not lift, or falls while carried. In a Blockly program with object detection on, the program stops when the part is not held21 | Click STOP. Do not reach for the part until the arm has stopped1322 | The cups were not on the part, the part is misplaced, suction was not switched on, or the tool is loose. Unstable clamping can drop a part21923 | With the arm stopped, pick up the part and check it. Check the tool is installed properly, test the suction again, and restart only with lab staff's approval232124 |
| A joint past its limit, or a poor starting position | Studio shows error code C23: a joint angle beyond its limit25 | Stop and keep clear1 | The arm started from, or was moved to, a pose outside a joint's range25 | Make sure the path is clear, then press Initial Position in Live Control to bring the arm back263 |
Anything Else
Printed from https://www.anotherplace.com/learn/en/xarm-6/operate/abnormal. Every line cites its source on that page.