V3.2 Documentation and API Change Notes
This document applies only to A3 software version 3.2.x.
V3.2 Documentation Updates
| Date | Update | Latest AimDK Package |
|---|---|---|
| 2026-08-15 | Released the A3 Development Guide (v3.2) | AimDK-A3-V3.2-0815 |
| 2026-09-24 | 1. Corrected incorrect joint range descriptions in the Motion Control section 2. Removed obsolete alert levels from the Fault Diagnosis section 3. Corrected inaccurate resolution and frame rate descriptions and incorrect topic names in the Sensor Data section 4. The built-in microphone has a serious bug in version 3.2 and is not recommended for secondary development. External microphone data works normally. |
AimDK-A3-V3.2-0815 |
V3.2 API Change Notes
This changelog lists API changes relative to V3.1, as well as other updates that may significantly affect secondary development. Incompatible changes are highlighted in bold.
- Microphone Management
- Fixed the issue where noise-reduced audio from the built-in microphone could not be output
- Resource Management
- Added a dance playback interface
- Sensor Data
- Added radar data publication topic
- Removed the left-eye and right-eye streaming topics for the stereo camera
- Motion Control
- Corrected incorrect arm, neck, head, and waist joint range descriptions
Issue Feedback Channel
If you encounter bugs related to secondary development APIs, you can submit feedback through the following channel:
https://agirobot.feishu.cn/share/base/form/shrcnLP2tv9gzyrZ2tSDlm1Baif
Notes
This channel is only for secondary development API questions and bug reports. For robot hardware failures, after-sales repair, or related issues, please contact the delivery, operations, or after-sales teams directly. Irrelevant questions will not be answered. Please describe the issue in detail in the form, preferably with reproducible steps. Reports with clear and complete information will be prioritized, while vague or overly general reports may be deprioritized or ignored. Please fill in all fields carefully. Tickets with inconsistent or randomly entered information will be ignored. Each ticket should focus on a single issue or a single category of issues. Do not combine multiple unrelated issues into one ticket, as this will significantly delay processing.