Changed constrained velocity to match motor max better #322
Conversation
This file contains 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.
Fixes ROBOTIS-GIT/turtlebot3#765. In short, commanded velocities were ignored for the turtlebot3 burger if they were higher than 0.22m/s.
This was because the constant
LIMIT_X_MAX_VELOCITYwas set specifically for the Dynamixel XM430-W210-T (i.e for the Turtlebot3 Waffle) but the Dynamixel XM430-W250-T (Burger) has a lower attainable velocity. Here, I set the constant to the lower value to match the Burger, but I read the max velocity for the constraint from the motor's control table itself so that the Waffle does not lose its higher wheel RPM.