v0.13.1

v0.13.1

Interface contract: carbon-interface v1.3.3 (required — earlier versions lack signed register/RAM access)
Firmware compatibility: unchanged from v0.13.0

A patch release. The headline is a change to how the sensor delivers its point stream by default, fixing a multicast regression on multi-homed hosts (Windows in particular).

Behavior Changes

• The push stream is now delivered by unicast by default. On connect, the primary client tells the sensor to reply straight back to it (reply-to-last-sender) instead of streaming to a multicast group. This arrives reliably even when the host has several network connections active at once — e.g. wired plus Wi-Fi — which is where the previous multicast default could silently fail to deliver frames. Multicast is now opt-in via the multicast stream-transport setting (CLI --stream-transport multicast, or the equivalent config/Python/C++ field); use it when you want several clients to share one sensor and your network is set up to route the group correctly. Observer-only clients still require the primary to use multicast.
• SDL bandwidth/parameter changes no longer report a false outcome while still being applied. The host-written "queued for MCU" marker (MessageReadyForMcu) is now treated as in-flight: the client keeps polling — without burning a retry — until the firmware finishes verifying and applying the command. A bandwidth change in particular can sit queued for several heartbeats. This removes spurious early success/failure reports on SDL commands.

Other Changes

• API reference docs (Python & C++) are now built in CI.
• Example tweaks to align the bundled examples with the SDK comments.