-
Notifications
You must be signed in to change notification settings - Fork 197
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
Update all demos using the description from topic rather than the parameter #456
Update all demos using the description from topic rather than the parameter #456
Conversation
Since activation of the "hardware" takes some time, the resource manager might try to write the initial NaN value to the hardware. This commit adds a check to the write method for that.
Co-authored-by: Sai Kishor Kothakota <[email protected]>
Migrated all demos and manually tested them. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The changes look good to me!
Let's merge once ros-controls/ros2_control#1358 is merged!
I don't see any specific reason to wait for that, as this PR removes long-deprecated mechanisms and is in line with the docs again, but sure, it's not necessarily required before ros-controls/ros2_control#1358 is merged. |
Sure, we can merge it. You have a point 👍🏽 Let's wait for one more approval for merging it :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thank you for thinking of this!
should we backport this? this should work even with humble?
No, this will not work on humble because we subscribe to robot_description and not ~/robot_description on rolling. |
ah you are right. should we backport the rest? |
…ameter (#456) * Use correct remapping for iron/humble * Updated demos * Example 14: Check for NaN in write method Since activation of the "hardware" takes some time, the resource manager might try to write the initial NaN value to the hardware. This commit adds a check to the write method for that. --------- Co-authored-by: Sai Kishor Kothakota <[email protected]>
…ameter (#456) * Use correct remapping for iron/humble * Updated demos * Example 14: Check for NaN in write method Since activation of the "hardware" takes some time, the resource manager might try to write the initial NaN value to the hardware. This commit adds a check to the write method for that. --------- Co-authored-by: Sai Kishor Kothakota <[email protected]> Co-authored-by: Felix Exner (fexner) <[email protected]>
…ameter (#456) (#472) * Use correct remapping for iron/humble * Updated demos * Example 14: Check for NaN in write method Since activation of the "hardware" takes some time, the resource manager might try to write the initial NaN value to the hardware. This commit adds a check to the write method for that. --------- Co-authored-by: Sai Kishor Kothakota <[email protected]> Co-authored-by: Felix Exner (fexner) <[email protected]>
…ameter (#456) (#472) * Use correct remapping for iron/humble * Updated demos * Example 14: Check for NaN in write method Since activation of the "hardware" takes some time, the resource manager might try to write the initial NaN value to the hardware. This commit adds a check to the write method for that. --------- Co-authored-by: Sai Kishor Kothakota <[email protected]> Co-authored-by: Felix Exner (fexner) <[email protected]> (cherry picked from commit 11d699b)
…ameter (#456) (#472) (#473) * Use correct remapping for iron/humble * Updated demos * Example 14: Check for NaN in write method Since activation of the "hardware" takes some time, the resource manager might try to write the initial NaN value to the hardware. This commit adds a check to the write method for that. --------- Co-authored-by: Sai Kishor Kothakota <[email protected]> Co-authored-by: Felix Exner (fexner) <[email protected]> (cherry picked from commit 11d699b) Co-authored-by: Christoph Fröhlich <[email protected]>
This will make sure things work after ros-controls/ros2_control#1358 is merged.
I'll update this demo by demo whenever I find the time and check the demos according to their docs after modifying them.