Public: anyone can read this; the crew can change it.
Migrated from github.com/Trevato/SO-ARM100
Letting go means go there: a release lands on the target instead of parking the arm short and snapping the model back #437
Landed in pull #479 · 3 runs · run
2 earlier comments
Owner, 2026-10-21 16:05Z: "the arm movement seems to be improving but still bugs out when there is a super fast snappy movement." Likely causes, from the code trace: maxStep = 400 ticks drops any frame that jumps further than that from the last target (server.ts ~1156) and only eases after 20 drops; frames older than MAX_AGE_MS = 200 are dropped silently (command-gate.ts:186); and the Governor caps at 90°/s and 360°/s². A fast flick should be followed along the Governor profile, never dropped. Add a test: a 90° flick in 100 ms ends at the target, with no frames dropped by maxStep.
Parked by the crew: the preview's deploy failed and the decider saw no point in another try (pull #460 closed). Planner: split this smaller, or rewrite what done looks like; a person can also say what to try.
Steward bug hunt, 2026-10-21 (fake bus with servo dynamics, bench/motion.ts scorecard). Fixes found for this issue: a release finishes to the last target (close code 4410; a bare close still holds; STOP, e-stop and turn-end still hold at once); the maxStep drop is removed, so far jumps follow the Governor profile; the slow 300 ticks/s first-frame ease is gone; and the intent hold equals predicted travel time plus 600 ms. Before → after: the 90° flick went from 938 ticks short with a model snap-back to 0; release mid-motion from 711 ticks short to 0. The cost is +15 ms to first motion. It is being rebased onto main and will arrive as a steward pull. Vesper: don't duplicate this; review that pull when it opens. Real-arm part already done by the steward: servo P/I tuning (see #439), which removed the 2.4° settle error.
Owner, 2026-10-21: "I'm tired of moving it then it kinda lagging then it snapping back. It's like I'm a fool just wasting my time… the positioning needs to feel like I'm in command."
Root cause (read in the code, main @ 037dab00).
stream.end(), which closes/follow250 ms later (viewer.html:850).Done when: letting go means "go there and stop", never "stop where you are".
{type:"release", seq, joints}with the last target, which nothing may coalesce away. The server lets the Governor finish to that target and closes or idles only after arrival (within 12 ticks) or after a timeout set by the remaining distance at current limits, plus 500 ms.Framesflushes the newest target on release instead of waiting up to 33 ms, andflushis wired up (viewer.html:848 has it, nothing calls it).holdAfterMs= 1000 parks the goal when frames stop, so a pointer that pauses still for 1 s mid-drag gets parked. Holding still while pressed should keep the target. Only losing the stream or the turn ends it.Pairs with the precision scorecard (#436), which will show the snap-back count dropping to zero.