Reviewed runtime: XGO Duck AI 0.3.6 / d66192d, 19 November 2026. Use this page to update an existing Duck.
Inspect before installing: Determine the target version, then read the existing App’s actual path, version and running state. If the target version and required build are already running normally, report “Already at the target version; skipping installation” and leave it running. Investigate logs first if the same version is unhealthy. If the latest GitHub release cannot be queried, verify the version inside the ModelScope bundle and report that it has not been confirmed as the latest. Do not downgrade a working newer version.
Latest branch instructions · 19 November 2026
The current AI branch slightly adjusts the knee and ankle targets of the ordinary walking default pose. After an update, use Default pose and the reference photos to check it; do not compensate by changing servo centers. Different builds may share version 0.3.6, so installation checks must use the target package and its build manifest.
ToF still undetected after reboot: If the connected ToF is still missing after the acceptance reboot, mark it “pending retest.” Manually turn Duck’s power switch off and on once. After startup, check /api/tof/status again for state=ranging, fresh=true, an increasing seq and valid_zones > 0. Do not mark the sensor as passed before retesting.
What changed in 0.3.6
Full first-install bundle and precompiled .ard, alongside the source ZIP.
Unified calibration of all 15 servo centers, including neck ID 30, followed by IMU and Default pose on the same page.
Phone portrait/landscape driving layouts, View controls, and light controls enabled after the camera starts.
Chinese/English gamepad UI; bindings for Sit, Roller mode, both kicks and seven Duck calls.
LED display of the last IP octet and a spoken current-IP binding reminder; a first-use rear-cover reminder before remote motion.
Choose a package
| Package | When to use it |
|---|---|
| GitHub full ZIP · SHA-256 / ModelScope full ZIP · SHA-256 | Default for first installs and version upgrades, about 470 MB. Transfer to the board and follow INSTALL.txt; it does not reflash the OS. |
| Precompiled .ard · SHA-256 | About 80 MB. Explicit lightweight installation or unavailable full bundle. Requires board App CLI/daemon 0.14+; App Lab import requires 0.11+. |
| App Lab source ZIP · SHA-256 | About 35 MB. Source editing, unsupported Release installation, or source-only target. Import, prepare dependencies and compile. |
Use the full bundle by default for first installs and version upgrades. On mainland China networks, try the ModelScope ZIP and its SHA-256 first. Elsewhere, try the GitHub ZIP and its SHA-256 first. If downloading or verification fails, or the bundled version differs from the target, download both files again from the other source. Use GitHub Releases for historical versions.
Select the source using the public egress region of the computer doing the download, independently of the board’s LAN IP and voice-service region. The prompt uses a time-limited region lookup; if the result is unclear, it briefly probes both checksum URLs and selects an available source.
Fixed download URLs follow the latest Release. Use matching version files; check Releases if assets are unavailable and retain a working installation.
Back up and migrate this Duck
Support Duck and confirm torque is off. Record the old App path, version and default App. Stop it, then back up the whole App and data/ outside its directory and check that the backup is readable.
Install into a separate directory. With both Apps stopped, migrate persistent IMU/hardware-center records, identity, binding, region, voice settings and gamepad mappings. Retain ownership and permissions.
Exclude .cache/, data/native/ and runtime sockets. Keep newly generated native files. Never transfer another robot’s identity or calibration.
Current centers live in the servos; data/hardware-centers.json records acknowledgements. Retain legacy zero_pos.json as a backup; do not fill it with 2047 to bypass physical calibration.
Configure and start the new directory
For .ard or source, migrate first, then run the following from the actual new App directory. Keep the matching web, Python and STM32 firmware together.
bash tools/install-ai-support.sh &&
sudo bash tools/router-2m.sh &&
arduino-app-cli app start "$PWD"
The full bundle starts automatically. Before restoring data, stop the new App and xgoduck-ai-hardware.service. After migration, restart the service, then start the App with --no-prepare. The 0.3.6 fixed target is /var/lib/arduino-app-cli/releases/xgoduck-ai-0-3-6-unoq. An existing target requires the matching installation receipt; never overwrite it or fabricate that receipt.
Full manual procedure and AI update prompt
Verify one normal reboot
After first startup and dependencies finish, support Duck with torque off and perform one normal reboot. Reconnect over Wi-Fi SSH; verify a changed boot ID, default App autostart, /api/version, both port-80 and port-9527 pages, and retained settings. Check wired servos, IMU and ToF. Missing binding, USB audio or internet can leave voice pending; investigate crashes and dependency failures.
Then check Default pose and a short slow walk. On failure, retain logs and the old version. Rollback must restore the old hardware service, shared Router and default App together; never run both Apps at once.
Wiki