Skip to content

Lower trans_stopped_velocity below the robot's real top speed#30

Open
MJohnson459 wants to merge 1 commit into
mainfrom
trans-stopped-velocity
Open

Lower trans_stopped_velocity below the robot's real top speed#30
MJohnson459 wants to merge 1 commit into
mainfrom
trans-stopped-velocity

Conversation

@MJohnson459

@MJohnson459 MJohnson459 commented Jul 6, 2026

Copy link
Copy Markdown
Contributor

Summary

FollowPath.trans_stopped_velocity was 0.25 m/s — above the ~0.218 m/s surface-speed ceiling the servos actually sustain at the 5 V supply (measured from recorded odometry). The controller therefore treats the robot as "stopped translating" even at full cruise, which skews the RotateToGoal critic's "have we stopped yet" check. Lower it to 0.1, clearly below cruising speed.

Context

Surfaced while reviewing the real-robot nav bags (the same investigation behind the WheelSpeedLimit critic, #28): the robot's linear speed is hard-walled at ~0.218 m/s, so any threshold above that is never crossed.

Test plan

  • One-line value change; nav2_params.yaml still parses.
  • Live: confirm rotate-to-goal transitions behave sensibly on the Pi / in sim-nav.

Note

Touches the same FollowPath block as #28, so whichever lands second will need a trivial conflict resolution.

🤖 Generated with Claude Code

trans_stopped_velocity was 0.25 m/s, above the ~0.218 m/s ceiling the
servos actually sustain, so the controller treated the robot as stopped
even at full cruise — skewing the RotateToGoal "have we stopped
translating yet" check. Drop it to 0.1, clearly below cruising speed.

Claude-Session: https://claude.ai/code/session_01C1uzkSYe5pzhPvamaoaHcW
@MJohnson459 MJohnson459 marked this pull request as ready for review July 8, 2026 09:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant