[Example 13] Multi-robot system with lifecycle management (backport #417) #606
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 is a rewrite of #187 including StoglRobotics-forks#7.
Open questions for me:
The problems discussed in the latter PR are summarized in Ressource manager hangs up on lifecycle changes ros2_control#1103. I'd say we can add this example even if the problem is not fixed yet.It uses the rrbot URDF from example_4 and example_5. Should I generate new ones inside example 15? Currently, there is also the FTS broadcaster etc in Rviz, but maybe this wouldn't be necessary and we could just use the same Rrbot instead.-> we decided in the WG meeting to reuse descriptions for the multi-robot examples./joint_states
topic and it seemed to work (better than now, without the necessity of reloading the JSB). The only difference is that with the global one, all joints are within one message. Why would someone need this for multiple robots?This is an automatic backport of pull request [Example 13] Multi-robot system with lifecycle management #417 done by Mergify.