MicroDuck 0.17.9: Camera Recovery & Endurance Logs

What changed in the official release

Tag daemon-v0.17.9 and main resolve to 96b89d8613; the release was published October 26 at 11:19:51 UTC. Merged changes are PR467, PR468 and PR469. Duckctl on PyPI is also 0.17.9; the reviewed HF policy set remains v8.

After an initial decoded video frame, the official console detects a one-second decoding freeze and opens a new session after a 300 ms reconnect delay. Bytes arriving alone do not count as a working picture. Beta GC2093 exposure belongs to rkaiq; IMX219 keeps the mediad loop. Idle glances blend toward a straight head instead of orbiting a pose left by the pad; this is not servo zero calibration.

• Official stable release
• Fixed release comparison
• Camera and console implementation

Inspect the endurance tool before starting it

The commands below inspect help, status and the existing service log. Starting with sudo robotctl endurance is a different action: it schedules walking, standing and sitting, runs as robotctl-endurance in the background, and continues after SSH closes. The source asks for clear floor and no gamepad competing with its commands.

The default sample interval is ten seconds. samples.csv, events.csv and meta.json persist under /var/lib/endurance/<hostname>-<UTC time>/; the plotting script reads that run directory. The default 0.45 m odometry fence is not a physical boundary. At or below 2% the tool stops driving and leaves empty-battery handling to robotd. sudo robotctl endurance stop ends the run but leaves the robot standing; --dry-run logs without commanding motion and still creates a run. These are software behaviors, not a measured battery-life result.

robotctl endurance --help
robotctl endurance status
journalctl -u robotctl-endurance -n 60 --no-pager

• Fixed command reference and run files
• Endurance implementation
• Plotting source

Keep official updates and personal images separate

Record the robot model, current software version, configuration and a known working recovery route before using the project’s update procedure. After updating, check decoded frames rather than only a connected indicator; investigate a missing first frame separately. This site reviewed sources without running a daemon, camera, battery test or hardware update.

fanhao375 reports a local isolated 0.17.9 integration, but explicitly says the runtime branch was not pushed and no new image was delivered. Its current published image remains 20261023c. KISS’s public route still names Robot Console R17 V167/control.43. Do not install official binaries over an HD1910 stack because the version number is newer; the consoles, IMU/servo paths and acceptance scopes differ.

• Author’s public migration scope
• Choose a DIY route