trevato/arm
Public: anyone can read this; the crew can change it.
Migrated from github.com/Trevato/SO-ARM100
- Grow cameras see the plants: a saved camera profile per station (exposure, white balance), full-res stills cropped to the box, colour correction under grow light
- Grow box: a still every 10 min, a scrubbable timelapse, a grow log and a canopy chart
- Grow light schedule: a switch driver (smart plug, GPIO relay, or uhubctl only when it switches the light alone) with a photoperiod that runs on the Pi
- The workshop: one Pi, several stations (the arm and the grow box), each with cameras and controls; works with the arm unplugged
- Sign out, and every page shows who you are, even when the arm is off
- Closing the arm locks its owner out: keep sign-in and /admin working while closed, an Open now button on the resting card, and so101 open/close P0 Trust
- setup: find LeRobot calibration in its nested folders (calibration/robots/so_follower/*.json) P0 Trust
- `so101 setup` finds both arms, asks you to wiggle the leader, reuses existing calibration, then starts teleop
- `so101 teleop` drives the follower from the leader in one process at 60 Hz, with a joint table, lag and space to STOP
- The so101 CLI runs under Node: `node bin/so101 --help` and `ports` no longer reach bun:sqlite
- The story page: an engaging write-up of the arm for anyone, with the Hugging Face SO-101 docs and the public repo P0 Trust
- Open / Closed: the owner can close the arm, and a resting card tells visitors why (and when it is back) P0 Trust
- stack streams on larger view
- jam-stream.test.ts judges 'jams within 500 ms' on the readings' own clock, not the test machine's wall clock, so a loaded full run no longer fails it
- A session in /admin/data shows its joint traces, intent against actual, with jam, block, STOP and release marks on the same axis
- /admin/data's Health section charts Pi temperature, with under-voltage minutes marked on the same axis
- The relay's minute sample records pi:temp and pi:undervolt from the arm's GET /health/pi into facts (no chart)
- settings.servoGains lands from the reviewed branch: validated at PUT /settings, proved by the branch's own server, not the preview
- bench/jam-rate.ts <url> reports jams per hour from the arm's /metrics, so #509's before-and-after can be measured on the real arm
- The arm keeps a 5 Hz intent-and-read-back trace per joint for its last 20 drive sessions and serves it at GET /precision/trace?session=<id>
new above
offline