A unit arrives already minted and leaves with a different label. Authorising is a decision; the station does the minting and shows the new claim code at the bench. No secret is generated here.
Waiting for the fleet stream…
Pick a published version and an env. The
station pulls the bytes itself and checks their sha256 against the
release before writing them; it refuses while a board is on the bench.
Env rather than board: drip-r and drip-r-psram
are both board m5 and drip-r is the rollback target.
Roll offers a build to the canaries the gate names. It never writes to a fleet unit — that stays behind fleet ops, deliberately.
Addresses in the LAN address column are links to each unit’s own web UI. They open in a new tab and only work from the same network as the device — this page cannot tell whether you are on it, so the link is always shown.
Carried to the tool by hand, on purpose. Paste after the image and backup arguments. Addresses are LAN-only — this list is useful from the same network as the units and nowhere else.
Mints a one-time code for the bench page on the workshop network.
Shipping is recorded from the unit in your hand. The customer scans the code on it to claim it — that is what makes it theirs, and it works whether or not this step was done.
Loading…
No devices yet. Bring up the stack and start the simulator —
python sim/pluvio_sim.py --devices 50 --speed 20