Gazebo: Add WildThumper with Lidar #101
Merged
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.
Add a variant of the wild thumper rover with a RP A1 Lidar, reusing the mesh files from the existing
wildthumper
model.Comments
Ideally we would use model nesting to compose the lidar link with the existing
willdthumper
model. Unfortunately because of limitations in thesdformat_urdf
plugin (see: ros/sdformat_urdf#20) Gazebo and ROS cannot handle different resource prefixes consistently. There is a work-around that allows us to display the SDFormat robot model in both Gazebo and rviz provided the model is not nested. The required prefix is substituted at launch time in the ROS 2 Python launch file. The approach requires that all resources are specified a single SDF file.When the upstream issues are addressed the lidar variant of the wild thumper model can be simplified.
See also