Skip to content

FAQ lists#

This page compiles common issues and solutions for the Airbot Play robotic arm. Whether you're a beginner or an experienced developer, you'll find useful information here to help you quickly resolve technical problems and optimize the use and development experience of the robotic arm.

1. Errors When Starting the Robotic Arm Control Service#

### 1.1 Error: Motor 1 in mode SINGLE not calibrated Gravity compensation calibration has not been performed，contact after-sales support for remote gravity compensation calibration.

### 1.2 OD motor × encoder bias too large，Base recorded position is nan,please set zero first The robotic arm needs to be zero-calibrated.

## 2. Error: Motor × is not sync - Scenario 1: Unable to read parameters for a specific motor. - Solution: Contact after-sales support for further inspection. - Scenario 2: Parameters can be read, but the issue is with Motor 7. - Cause: Likely due to a damaged end-effector cable. - Solution: Try replacing the cable. - Scenario 3: Parameters can be read, but the issue is with Motor 1 or 7. - Cause: Likely due to a disconnected USB data cable caused by pulling. - Solution: Reconnect the USB data cable.

3. End-Effector Buttons Unresponsive After SDK Control#

If you want to use the end-effector buttons to control the robotic arm after controlling it via the SDK, you need to switch to online mode in the SDK.

4. Discrepancy Between Actual and Target Arm Positions#

  • Step 1: Perform zero-calibration and check if the actual position matches the target position.
  • Step 2: If the discrepancy persists, contact after-sales support for remote absolute zero-calibration.