Bug solution multi-vehicles in wamv_gazebo.urdf.xacro #644
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.
When trying to launch a second vessel with the name wamv2, the following error message was shown
[ERROR] [launch]: Caught exception in launch (see debug for traceback): Error Code 20: Msg: Child frame with name[wamv/base_link] specified by joint with name[wamv_external_pivot_joint] not found in model with name[WAM-V]
When inspecting the problem (also see problem #638), I found the problem in line 103 of the
wamv_gazebo.urdf.xacro
file, in which the namespace was not properly referenced to the namespace but only to the standard topic namespace ofwamv/base_link
. As a result without changing the child to$(arg namespace)/base_link
, it is not possible to spawn a second vehicle with a different namespace. Therefore, without the change, it would not be possible to control the vessels independent of each other, as both subscribe to the same topic.Tested the changes for ROS2