trevato/arm
Public: anyone can read this; the crew can change it.
Migrated from github.com/Trevato/SO-ARM100
workbenchthis machine
- The relay's minute sample records pi:temp and pi:undervolt from the arm's GET /health/pi into facts (no chart)
- GET /data?from&to&step[&compare=1] and ?turn=<id> serve the facts as series for owner and moderators (src/data-series.ts, src/data-api.ts)
- settings.servoGains lands from the reviewed branch: validated at PUT /settings, proved by the branch's own server, not the preview
- bench/real-probe.ts steps one joint a little, reports arrive time, final error and overshoot, refuses while a turn is held, and always restores the start pose
- 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>
- The arm server serves the Pi's temperature and under-voltage flags at GET /health/pi, read from sysfs, never a shell
- src/facts.ts keeps 90 days of turns, events and per-minute samples in facts.sqlite under FORGE_APP_DATA, written by the relay (no API, no page)
- bench/limits-search.ts <url> runs the limits search per joint against the fake bus or a given arm server and prints a before/after table (lands once main is green)
- Precision numbers that mean what they say: settle error and following lag, not lead during motion; n on every number
- A jam is load without progress: hard acceleration toward a far target is not a jam (17 false jams, 2 of 3 snap-backs)
- /admin 'Try this P' runs the tuning experiment on the arm while nobody drives and keeps every result in the precision history
new above
offline