Start with the product architecture diagram for the overall layout. This chapter maps the running software to its interfaces so you can extend the complete audio/video robot without bypassing its motion checks.
Runtime responsibilities
| Layer | Responsibility | Interface |
|---|---|---|
| UNO Q Linux main App | State, browser controls and ONNX policy inference | Python application and HTTP/WebSocket endpoints |
| Audio/video support process | USB camera, audio, light, binding and voice integration | Local hardware-service interface |
| UNO Q STM32U585 | Servo communication and sensor acquisition | Arduino Bridge at 2 Mbps |
| Servo bus | Commands and feedback for joints | Serial bus at 1 Mbps |
| IMU and ToF | Attitude and distance acquisition | Separate Wire / Wire1 I²C buses |
Find the source
| Location | Use |
|---|---|
| python/main.py | Main Python entry and runtime coordination |
| sketch/ | MCU program and its Bridge / peripheral implementation |
| assets/ | Browser interface and static resources |
| tools/ | Installation, hardware checks and maintenance utilities |
| data/ | This robot’s persistent settings, binding and calibration records |
Use the reviewed audio/video runtime branch and inspect its current file layout before changing an interface. Keep Python, MCU code, protocol and hardware services at compatible versions.
Read status before adding controls
This Python example only reads the running App. Replace the address with your robot’s current IP; it does not enable motion.
import json
from urllib.request import urlopen
board = "192.168.1.123"
with urlopen(f"http://{board}:9527/api/status", timeout=5) as response:
status = json.load(response)
print(status)For camera, audio and ToF use their documented service endpoints and check the response fields, freshness and device state. Avoid polling loops without a delay or launching duplicate processes that compete for USB/I²C devices.
Extend motion carefully
Keep the declared observation order, units, joint order, action scaling, control period and servo limits consistent with the selected policy.
Retain the application’s mode, calibration, gain/protection and input-loss checks when adding a controller.
The motion policy covers 14 body joints; mouth ID 34 is controlled separately for interaction.
Test with the robot supported, then use short low-speed checks on a clear floor. Log stale feedback and rejected commands instead of silently overriding them.
Hardware and research sources
Hardware repository: PCB and BOM · Policy training and export. Printing downloads are listed only through the MakerWorld entries in step 01.
0.3.6 installation paths and firmware
Use app list and installation output to find the actual directory. Precompiled releases may live under /var/lib/arduino-app-cli/releases rather than ~/ArduinoApps. Normal .ard installation uses bundled firmware and Python dependencies. Changes to sketch inputs or damaged firmware trigger a rebuild; use the project release_firmware.py recovery instructions with network available for missing dependencies. Keep this Duck’s persistent data separate from native build artifacts.
Wiki