# MicroDuck 0.17.2 Separates Brief Controller Stalls From a Lost Network Session

Source: TechNewsList (https://technewslist.com)
Canonical URL: https://technewslist.com/en/article/microduck-daemon-0172-udp-stall-recovery-2026-10-13-night
Section: Drones & Robots (https://technewslist.com/en/drones-robotics)
Author: TechNewsList
Language: en
Published: 2026-10-13T18:53:31.589+00:00
Updated: 2026-10-13T18:53:31.774962+00:00

> Pollen’s new daemon release preserves a UDP controller session during brief input loss, rejects late packets and exposes timing diagnostics. Its software safeguards are not a physical emergency-stop guarantee.

## TL;DR
- MicroDuck daemon 0.17.2 was released October 13 with configurable axes and UDP control-loss changes.
- Default stale-input and client-loss thresholds are 300 ms and 1000 ms respectively.
- UDP control is an opt-in trusted-LAN tool; software timing is not a certified physical stopping distance.

## Key points
- The official 0.17.2 release was published October 13 at 09:46 UTC.
- The release adds configurable gamepad axes and command limits.
- Pinned documentation defaults stale_ms to 300 and timeout_ms to 1000.
- A short input stall zeros walking while retaining the sender lock; a longer timeout clears the session.
- UDP control is disabled by default, unauthenticated, and intended only for a trusted LAN.
- Daemon updates, running services and separately installed learned policies must be checked independently.

## What happened

Pollen Robotics released MicroDuck daemon 0.17.2 on October 13 at 09:46 UTC. The release notes identify configurable gamepad axes and command limits, late-datagram handling, latency logging and a change that stops the robot when a controller stalls while retaining its session. This is a concrete control-software update for the small biped, not a new claim about its maximum physical speed or learned movement quality.

![Actual MicroDuck beside a coding laptop illustrates the control-development context, not an update test.](https://rkhynbcsbnkkcwgexzwg.supabase.co/storage/v1/object/public/media/api/1791917605335-n722s6-microduck-daemon-0172-udp-stall-recovery-2026-10-13-night-inside-1-8769e819c2.webp)
*Actual MicroDuck beside a coding laptop illustrates the control-development context, not an update test.. Credit: Pollen Robotics, reproduced by MicroDuck Robot Community.*

The change follows yesterday’s introduction and refinement of optional UDP gamepad control. An independent October 13 review of 0.17.1 describes that earlier version, including its older timeout behavior. It does not test the new release on hardware. The authoritative timing for this story therefore comes from Pollen’s documentation pinned to the 0.17.2 commit, rather than copying a number from the previous review.

## Why it matters

A network-controlled robot needs to distinguish a brief interruption from a vanished controller. If it continues applying an old movement command during a stall, the operator has lost effective control. If every small interruption destroys the session, recovery becomes unnecessarily disruptive. The new implementation separates the decision to stop walking from the decision to release the sender’s session, giving those states different thresholds and diagnostics.

That separation is useful only when its limits are understood. A software stale-input timer is not an instantaneous hardware emergency stop, nor does its value establish how far a robot moves before physically settling. Network delay, control-loop behavior, mechanics and the current action can all matter. A developer should treat the published values as part of a control contract to verify, not as a safety certification for unsupervised operation.

## Technical details

The pinned UDP guide defaults stale_ms to 300 milliseconds and timeout_ms to 1000 milliseconds. A stale input period stops walking while preserving the sender lock and held-button state. Longer silence counts the client as gone and clears the session; a sit request follows later when appropriate. The stale threshold must remain below the separate deadman setting, and configuration validation rejects inconsistent limits.

![Official close-up shows the real robot’s joints and body, keeping software timing distinct from physical certification.](https://rkhynbcsbnkkcwgexzwg.supabase.co/storage/v1/object/public/media/api/1791917606896-sjtgm1-microduck-daemon-0172-udp-stall-recovery-2026-10-13-night-inside-2-2a71c54715.webp)
*Official close-up shows the real robot’s joints and body, keeping software timing distinct from physical certification.. Credit: Pollen Robotics, reproduced by MicroDuck Robot Community.*

The release also drops sufficiently delayed datagrams and reports their arrival timing. That matters because receiving a packet is not the same as receiving a current instruction. A delayed command can be syntactically correct but wrong for the present moment. Link diagnostics give developers a way to investigate stale arrivals and stalls instead of assuming that every problem lies in a walking policy or gamepad mapping.

The UDP service is disabled by default and intended for a trusted local network. Pollen’s guide explicitly says it is unauthenticated and that reachable clients can control the robot. It is not the recommended internet-control path. Enabling it changes which pad daemon owns input: the Bluetooth and UDP services must agree on the configuration. A service that remains on an old setting can resemble a controller failure even when the network is healthy.

## Market / industry impact

The configurable-axis work makes the robot’s input contract more adaptable, but it should not be confused with a new learned capability. Changing a source axis, inversion or gain changes what the controller requests. It does not demonstrate that the physical robot can safely execute a wider motion range. The release’s contribution is better control and observability, with the movement policy and hardware still needing their own validation.

For open robotics projects, this kind of operational detail can be more valuable than a polished demonstration. Users need to know which version is running, why a requested action was clamped and whether input actually reached the controller. Pollen’s command reference provides version, health, configuration and policy inspection. The independent earlier review also stresses that daemon and policy updates are separate decisions rather than one automatic upgrade to every behavior.

## What to watch next

Before an intentional update, an owner should record the running version, local overrides, actual bindings and installed policies. Support the robot and verify the control path in a suitable supervised setup. Afterward, compare the same evidence again. A downloaded release does not prove the service restarted into it, and a new daemon does not prove that a separately installed policy changed or that a local override disappeared.

The most useful validation would deliberately distinguish short input loss, long silence, delayed packets and a changed controller layout, with logs showing the resulting state. That is a test plan, not a claim that TechPulse performed it. Physical measurements would still be needed to characterize stopping behavior. The published software update gives operators better evidence to collect; it does not remove the need to collect it.

Finally, the right recovery action depends on the observed state. A preserved session after a short stall is different from a client timeout, and neither automatically means the robot needs a firmware reinstall. Version and health reports should come before broad changes. Keeping the controller, daemon, policy and physical outcome distinct makes a small robotics platform easier to debug without overstating what a single release can guarantee.

## Sources

- [Pollen 0.17.2 release](https://github.com/pollen-robotics/microduck/releases/tag/daemon-v0.17.2) — October 13 timestamp and merged axis, datagram latency, late-packet and stalled-client changes.
- [Pinned UDP control documentation](https://github.com/pollen-robotics/microduck/blob/35b71a2a4499eb22216b3417e19e97db602561d4/docs/robot/udp-pad.md) — Exact version defaults: 300 ms stale input, 1000 ms timeout, trusted LAN limitation, service selection and diagnostics.
- [Pinned robot control command reference](https://github.com/pollen-robotics/microduck/blob/35b71a2a4499eb22216b3417e19e97db602561d4/docs/robot/cheatsheet.md) — Running version, health, configuration overrides, policy separation and controller inspection.
- [Independent 0.17.1 source review](https://microduckrobot.org/news/daemon-0-17-1/) — October 13 review of the previous release provides context and 250 ms old timeout, explicitly not physical testing or 0.17.2 verification.

Mentions: Pollen Robotics, MicroDuck

## Sources
- [Pollen 0.17.2 release](https://github.com/pollen-robotics/microduck/releases/tag/daemon-v0.17.2)
- [Pinned UDP control documentation](https://github.com/pollen-robotics/microduck/blob/35b71a2a4499eb22216b3417e19e97db602561d4/docs/robot/udp-pad.md)
- [Pinned robot control command reference](https://github.com/pollen-robotics/microduck/blob/35b71a2a4499eb22216b3417e19e97db602561d4/docs/robot/cheatsheet.md)
- [Independent 0.17.1 source review](https://microduckrobot.org/news/daemon-0-17-1/)