FAQ
Issue | Common Cause | Solution |
|---|---|---|
| Robot not fully started yet, or timeout too short | Wait for the robot to fully start (typically 30–60 seconds after boot) before connecting; or retry after increasing the |
Non-battery | Data did not arrive within | First try increasing |
| Incorrect number of joints passed |
① Control all joints (see T1/K1 manual for joint count of each model) ② Control only 10 upper body joints (head 2 + arms 8). Use |
Robot does not move after | Velocity value too small, or robot is not in motion mode | Check if velocity value is too small (recommended to start from |
Head does not move after | Angle value exceeds joint limits, or value too small | Use |
| Speech capability unavailable, audio service abnormal, or microphone stream unavailable | ① Check whether the audio service has started normally. ② Check whether the microphone and speakers in the current operating environment are working properly. ③ If the issue persists, restart the robot or the simulation environment and try again. |
|
| Try again after installing |
Cannot import | Vision optional dependencies not installed | Run |
| Model path does not exist, optional dependencies missing, ONNX Runtime / CUDA / TensorRT environment unavailable | First use |
Hand-guiding recording/playback function abnormal | Hand-guiding function of dual-board models (e.g., T1) is only available on the motion control board | Deploy hand-guiding related code to the motion control board for execution |