Fix joint trajectory action topic in ros_client.cpp #522
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
The old one was using pr2_controllers msgs
|
thank you for your contribution! please let me know if you checked with real NEXTAGE robot. I also understand this 'should' work, but sometimes it will not working..... |
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.
The old version of ros_client.cpp was using the pr2_controller messages and did not connect to either the simulation or the real robot. This PR changes it to the newer control_msgs topic that is currently used, so the interface connects properly.
We tested the change with a HIRONX and the simulation environment and found no issue. It should work the same way with a NEXTAGE.