You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Salvaged from #8 (closed as stale — 26 commits behind main, wrong feetech base).
Today so101.IsMoving returns s.isMoving.Load() — an atomic flag we set/clear around our own motion calls (arm.go). That reports our intent to move, not the servos' actual state, so it can be wrong when motion is interrupted, when the arm is back-driven, or when a joint is still settling after the flag clears.
This adds a serial round-trip per call — confirm callers (motion planner polling) tolerate the latency, or keep the atomic flag as a fast-path and only hit hardware when needed.
Should apply to the gripper (servo 6) as well as the arm servos.
Salvaged from #8 (closed as stale — 26 commits behind main, wrong feetech base).
Today
so101.IsMovingreturnss.isMoving.Load()— an atomic flag we set/clear around our own motion calls (arm.go). That reports our intent to move, not the servos' actual state, so it can be wrong when motion is interrupted, when the arm is back-driven, or when a joint is still settling after the flag clears.#8 proposed asking the hardware instead:
Notes / open questions
IsServoMovingexists / has an equivalent in feetech-servo v0.6.0 (main's current version; feat: enhance servo movement detection and motor configuration #8 was on 0.4.x).