Updating on Device

Updating on device

A Klipper change reaches a real printer through NebulaOS-firmware's component-update path — Moonraker's Update Manager, backed by a health-check-and-rollback supervisor. See Developer Update for the full mechanism.

During earlier live testing against the real device's config, we found and fixed a few compatibility gaps between this fork and the printer's actual printer.cfg (in the prtouch_v2, custom_macro, temp_offset_flag, and z_compensate sections). /opt/klipper on the device is writable, so testing a config change or MCU handshake doesn't require a full image rebuild.

See also: Integration with NebulaOS-firmware.