ALTERIOMESP32 Farm
A rig is a Raspberry Pi, a powered hub and a handful of ESP32 boards. Two pieces of software make it a rig: an agent that takes work from the farm and reports what happened, and a health check that proves a board is wired, reachable and alive before a run trusts it.
Both are open: the rig software at Alteriom/esp32-rig (with its guide) and the health check firmware at Alteriom/esp32-hil-firmware. The versions below are what this farm's rigs are told to run.
WHAT THE RIGS RUN
Read live from the farm: which release its rigs are told to run.
Loading…
PROJECTS ON THE FARM
The built-ins every rig has, and the projects whose owners made them public. Any of them can be added to a rig of your own from its repository.
Loading…
THE RIG'S OWN DASHBOARD
A rig serves its own dashboard, with or without this farm: its boards, its runs and their evidence, how it has been doing.
Pictures of a demo rig. A tour of the dashboard has every page.
WHAT EACH PIECE DOES
It talks outward only: hello, then a heartbeat with what the rig has and what it is still running; a long poll for the next job it was granted; the stages, the log and the evidence as the job goes. A rig never listens for the farm, so a rig needs no address, no port and no inbound rule.
The end of a run is written to disk before it is sent, so a farm that is unreachable, or a rig that restarts, loses no verdict.
Firmware that answers. It says which board it is, proves the serial path both ways, and drives the pins a wiring check reads from the other end, so a board that is present but miswired is found before a suite blames the firmware under test.
It lives in its own repository and has its own releases; each rig release pins one version of it, and a rig installs that one with the rig software.
A rig runs on hardware you own, in a room you control, and it reports to a farm you may not. That is a reasonable thing to want to read before you run it. The agent and the health check are public; the portal that schedules them stays ours.
DOCS AND SUPPORT
Building a rig, from parts to first run: the hardware blueprint and the bring-up checklist. What the farm does with a rig once it has joined: the farm service.
These links want a GitHub account with access today. They open with the package.
Something wrong with a rig, or a question about running one: write to espfarm@alteriom.net.
If a rig of yours has gone quiet, its page in the dashboard shows what it last said and when. Start there.
A rig joins a farm with one command and a token that works once. It is private until you say otherwise: nothing about it appears on the public site unless its owner shows it.
Adding one is the farm's to do today: write to espfarm@alteriom.net and the command and the token come back. Sign in first: the rig is handed to the account you signed in with, and from then on the rig, its runs and who may see it are yours.