-
Notifications
You must be signed in to change notification settings - Fork 14.6k
Mecanum: Seperate velocity control #24647
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
🔎 FLASH Analysispx4_fmu-v5x [Total VM Diff: 144 byte (0.01 %)]
px4_fmu-v6x [Total VM Diff: 136 byte (0.01 %)]
Updated: 2025-05-05T07:10:45 |
3e5f3cc
to
f2159b0
Compare
f2159b0
to
1e9399a
Compare
sfuhrer
reviewed
Apr 30, 2025
1e9399a
to
d9d6848
Compare
Rebased on main |
sfuhrer
approved these changes
May 5, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Solved Problem
Seperated

MecanumPosVelControl
intoMecanumVelControl
andMecanumPosControl
to bring the module into the following structure (Continuation of #24604):This introduces this new rover specific setpoint:
MecanumVelocitySetpoint
This PR also streamlines the flow of information between the different controllers: Each level of control will only publish the setpoint for one hierarchy level below (with the exception of the RoverThrottleSetpoint).
This is in preparation of exposing the rover setpoints (all orange uORB messages in the figure above) to DDS.
Test Coverage
Tested in SITL
Hardware tests: