Troubleshooting
About 679 wordsAbout 2 min
This section describes common issues encountered during robot operation, along with their possible causes and recommended corrective actions. If the problem cannot be resolved using the table below, please contact Cross‑Dimensional Intelligence technical support personnel.
| Problem | Possible Cause | Solution |
|---|---|---|
| Clicking sound from motors during arm movement | CPU load is too high, leaving insufficient computational resources for motion control tasks; or CPU temperature is too high, triggering thermal protection that reduces the clock frequency and leads to insufficient computing power. | Immediately press the emergency stop button on the back of the robot to halt operation. Allow the motors to cool down for 10–30 minutes, then release the emergency stop button and re‑execute the original motion. Observe for 30 minutes. If the issue persists, contact our company promptly. |
| Abnormal simulation model loading | If the model does not stand up properly (e.g., floating, tilted, sunken into the ground, or incorrect posture), the issue may be caused by abnormal data on the corresponding topics. | Check whether the following topics are publishing data: - Real robot: /feedback/joint - Simulation: /feedback/joint_sim |
| System restart takes too long | System‑related causes. | After rebooting via PC1/PC2, the system restart may take approximately 5–7 minutes. For a proper restart, follow Section 4.2 to shut down the robot, then press the rocker switch to power on again. |
| Multiple control cursors appear in teleoperation interface | Abnormal VR headset or controller behavior. | Immediately exit teleoperation to avoid potential arm collisions. |
| Hand gestures remain controllable after exiting teleoperation | After exiting the teleoperation interface, the actual exit process still takes some time due to data transmission latency. | Wait approximately 10 seconds after exiting the teleoperation interface. During this period, avoid performing hand gestures or controlling the arms to prevent anomalies. |
| Abnormal noise from robot joints | Under‑voltage: Charger display shows voltage below 45V and current below 5A. Over‑voltage: Charger display shows voltage above 54V and still rising. | Under‑voltage: Adjust the charger knob clockwise to set the charging voltage to ≥10A. Over‑voltage: Disconnect the charger immediately. |
| VR headset does not detect the controllers or displays low battery warning | Controller batteries are depleted. | Replace the AA batteries in the VR controllers. |
| Chassis control handle receiver is inserted but cannot control the chassis | The handle receiver has been unused for an extended period and is unresponsive. | Re‑initialize the handle receiver, then attempt to control the chassis again. |
| OP status drops (OP lost) | EtherCAT slave is offline, possibly due to loose connection between the cable plug and the joint module socket. | 1. Check that all slave cables are securely connected; reconnect any loose cables. 2. Monitor whether the OP loss occurs repeatedly. If the issue persists, contact Cross‑Dimensional Intelligence technical support for further troubleshooting. |
| No image or data from the wrist camera | The wrist camera was plugged or unplugged while the robot was running.
|
|