Skip to content

Real-time trajectory tracking #689

Answered by jpreiss
sadlim asked this question in Q&A
Sep 20, 2022 · 1 comments · 1 reply
Discussion options

You must be logged in to vote

The idea of goTo with nonzero final velocity raises some questions about how the commander should behave after the trajectory has ended.

Should the commander continue to maintain the same velocity forever? Or should there be some kind of timeout period?

When maintaining velocity after a goTo trajectory has ended, should the controller still attempt to track the position final_velocity * time_since_trajectory_ended? Or should we switch to a velocity-only controller?

So far, nobody has needed this feature enough to try to resolve these design decisions and do the implementation work.

You can certainly achieve your goal with low-level streaming modes like cmdFullState, cmdVelocityWorld, and c…

Replies: 1 comment 1 reply

Comment options

You must be logged in to vote
1 reply
@sadlim
Comment options

Answer selected by sadlim
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants