Conversation
Note that I decided to publish the robot model (instead of write it as a parameter) for a few reasons:
I also chose to duplicate the robot_model::initFile function so that I did not also have to make changes to two the robot_model repo. An improved solution would be to modify that function instead of having the separate copy (additionally, that would keep the file from being read twice). |
Updated the robot state publisher to publish the robot model URDF as a std_msgs/String. This is to allow rviz, or other nodes, to access the robot model.
dd0826b
to
a2bde60
Compare
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
I made a few fix ups and improved one of the error messages.
Sorry @bponsler that it took so long to add this. I was going back and forth on whether or not to add this and finally when we implemented it in the ros2/rviz repository, we added support of topic or parameter, so I opted to go ahead and include this for now.
Thanks for the contribution and sorry it sat so long.
Awesome! Thanks for pushing it over the finish line - glad it ended up being useful. |
Simple changes to the robot state publisher to publish the robot model URDF as a std_msgs/String. This is to allow rviz, or other nodes, to access the robot model.