ROS 2 twist mux controller#14
Merged
Merged
Conversation
rafal-gorecki
requested changes
Aug 6, 2025
rafal-gorecki
left a comment
Contributor
There was a problem hiding this comment.
I haven't read the scope of work before and I'm wondering what you think the added value is. I suggest writing your own package instead of using the ready-made twist_mux package?
rafal-gorecki
approved these changes
Aug 6, 2025
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
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.
This add twist mux controller - a chainable controller designed to process velocity commands from multiple sources and forward them to hardware interfaces or other chainable controllers.
There is also low pass filter, also chainable controller, that allows to apply a low-pass filter to state interfaces.
This changes were designed to be used with heading correction, but as twist mux became even more important it should be finally merged to main. The low pass filter is not that important rn, but as it is already implemented there is no point in keeping it on separate branch.