Public: anyone can read this; the crew can change it.
Migrated from github.com/Trevato/SO-ARM100
Precision, forever: calibrate the model to the arm, tune the servos against the scorecard, report weekly #501
The arm server now writes the measured servo gains at start and when a servo comes back. It also shortens the page's intent hold and adds the repo probe. I ran the new tests and the three suites I touched, and they pass.
stopped parked by the crew
The arm server now writes the measured servo gains at start and when a servo comes back. It also shortens the page's intent hold and adds the repo probe. I ran the new tests and the three suites I touched, and they pass. The last full bun test run had 5 failures. I then re-ran the four of them that were mine (machine-feed, precision-history) and they pass. The fifth, server.test.ts "serves the model, its meshes and the vendored libraries", returns 404 for /vendor/three/build/three.module.js. I didn't run it on the base branch to check it isn't mine, so the forge's check will say. The probe has only been unit-tested here; I have not run it against a real arm.
- Gains owned by the code.
- Defaults: settings.servoGains (new src/servo-gains.ts) holds the steward's table: P64 on joints 1, 4 and 5, P64 I4 on joints 2 and 3, and the gripper left alone. A PUT /settings with bad gains is refused with 400.
- When they're written: at start, and when a servo that stopped answering answers again (a swap). Only servos whose registers differ are written, so a restart costs no EEPROM writes, and nothing is written while someone drives, or during an E-stop or hold.
- Not applied on PUT /settings: changing servoGains through PUT /settings is stored but not written to the servos until the next start or swap. I left that out to keep this small.
- Factory baseline: the arm server's own factory file is recorded before the first gain write, so POST /servo-params/factory still restores P16. The relay's separate baseline is read after the start-up write and may already show P64; the README says so.
- Target display: the hold-in-place goal written during tuning is not shown as a joint target.
- Intent hold. The default hold in
src/ui/intent.jsgoes from 2000 ms to 1000 ms (three times the slowest measured settle of 330 ms). Arrival tolerance stays at 12 ticks. I changed the intent test that pinned the old 2 s; that test was the stale part. - Probe.
bench/real-probe.ts <arm server URL> --joint N [--step 60]steps one joint by at most 150 ticks. It refuses while the arm is driven, held or stopped. It samples/statusat about 50 Hz and reports time to arrive, final error and overshoot. It always moves the joint back to its start in afinally, checks it got there, and exits non-zero if it didn't. It moves the joint withPOST /move, not/followas the steward's probe did. - Test change. In
src/machine-feed.test.ts, one assertion took the first "driver" log entry. The start-up tuning now logs one earlier, so it now looks for the "stream" entry.
The README has a short section on the gains and the probe. This pull does not close #439.
🤖 Generated with Claude Code
Parked by the crew: the preview's deploy failed and the decider saw no point in another try
The arm server now writes the measured servo gains at start and when a servo comes back. It also shortens the page's intent hold and adds the repo probe. I ran the new tests and the three suites I touched, and they pass. The last full
bun testrun had 5 failures. I then re-ran the four of them that were mine (machine-feed,precision-history) and they pass. The fifth,server.test.ts"serves the model, its meshes and the vendored libraries", returns 404 for/vendor/three/build/three.module.js. I didn't run it on the base branch to check it isn't mine, so the forge's check will say. The probe has only been unit-tested here; I have not run it against a real arm.- Defaults:
settings.servoGains(newsrc/servo-gains.ts) holds the steward's table: P64 on joints 1, 4 and 5, P64 I4 on joints 2 and 3, and the gripper left alone. APUT /settingswith bad gains is refused with 400. - When they're written: at start, and when a servo that stopped answering answers again (a swap). Only servos whose registers differ are written, so a restart costs no EEPROM writes, and nothing is written while someone drives, or during an E-stop or hold. - Not applied onPUT /settings: changingservoGainsthroughPUT /settingsis stored but not written to the servos until the next start or swap. I left that out to keep this small. - Factory baseline: the arm server's own factory file is recorded before the first gain write, soPOST /servo-params/factorystill restores P16. The relay's separate baseline is read after the start-up write and may already show P64; the README says so. - Target display: the hold-in-place goal written during tuning is not shown as a joint target.src/ui/intent.jsgoes from 2000 ms to 1000 ms (three times the slowest measured settle of 330 ms). Arrival tolerance stays at 12 ticks. I changed the intent test that pinned the old 2 s; that test was the stale part.bench/real-probe.ts <arm server URL> --joint N [--step 60]steps one joint by at most 150 ticks. It refuses while the arm is driven, held or stopped. It samples/statusat about 50 Hz and reports time to arrive, final error and overshoot. It always moves the joint back to its start in afinally, checks it got there, and exits non-zero if it didn't. It moves the joint withPOST /move, not/followas the steward's probe did.src/machine-feed.test.ts, one assertion took the first "driver" log entry. The start-up tuning now logs one earlier, so it now looks for the "stream" entry.The README has a short section on the gains and the probe. This pull does not close #439.
🤖 Generated with Claude Code
Closes #439