Skip to content

SANDER release notes

Subscribe to updates

SANDER v1.0.0

Released on September 2026

This note describes the firmware as it ships today, including features introduced in earlier releases that are still part of the product. You do not need to read back through older notes to know what the current firmware does.

New Features and Improvements

  • Each unit now identifies itself to the host — SANDER reports a serial number derived from its own MAC address, a USB device version that tracks the firmware version, and named USB interfaces. A host can tell two dongles apart, and Device Manager shows which firmware a unit is running. Please note: this changes the USB device descriptor, so the first time a host sees an updated unit it treats it as new hardware and enumerates it again.

  • Touch, pen and eraser input over one USB connection — up to 10 simultaneous touch contacts, and three pen transducers reporting 10-bit pressure (0–1023). Fiducial markers are reported as erasers, so annotation tools behave as expected without extra software on the host.

  • Eraser contact size is configurable — set the eraser's reported contact area as a circle (radius) or a rectangle (width × height). Windows Ink applications size the eraser from what the device reports, so this is what makes a marker erase a believable area rather than a point. Host support varies.

  • Source resolution is detected automatically — SANDER reads the resolution the NetBridge source advertises and scales touches to your screen without anyone entering it by hand. A manual value still overrides the detected one where a source reports nothing useful.

  • Ethernet as well as Wi-Fi — an Ethernet board variant connects over W5500 wired networking. The web interface switches transport, shows Ethernet status, and configures a static IP for the wired interface. Receive is interrupt-driven, which keeps latency steady under load.

  • Static IP on either transport — optional static addressing (address, gateway, subnet mask) with DHCP as the default. If a static address cannot be applied at boot, the device falls back to DHCP rather than dropping off the network, and a factory reset clears the setting.

  • Over-the-air firmware updates — the device pulls firmware from the flasher site itself, so updating a deployed dongle does not require USB access to it.

  • Web flasher with three board variants — Standard, Ethernet and DevKitC-1 (16 MB), each with its own manifest. Every Install button shows the version it will flash, and a touch diagnostic tracer is published alongside the firmware for checking a suspect installation.

  • Remote access to device logs — GET /api/logs returns recent logs from the device's capture buffer, so a unit can be diagnosed without physical access to its console. This matters on a dongle whose single USB port is doing the touch injection.

  • NetBridge source handling — the data connection can be bound to a chosen source IP so traffic leaves the interface you intend, and the device can be re-pointed at a different source while running, without a reboot.

Bug Fixes

  • Web-based firmware upload no longer fails at 100% — uploads through the web interface were rejected during the final step because the upload framing was not parsed correctly.

  • The device no longer boot-loops after a logging change — a log-capture hook overflowed a system task's stack, leaving affected units restarting continuously.

  • Ethernet receive latency corrected — the Ethernet controller was polled rather than interrupt-driven, adding avoidable delay to every touch event on wired units.

  • The configuration page no longer shows controls that do nothing — seven settings that had no effect on the firmware were removed from the web form.

  • Re-pointing at a new NetBridge source no longer leaves two clients running — stopping the previous connection now completes before the new one starts.