The site is read-only. Please transition to use Robotics Stack Exchange
| ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
 | 1 | initial version |
Reading the Bouncy source, I see 2 problems:
robot_state_publisher is publishing with RMW_QOS_POLICY_DURABILITY_TRANSIENT_LOCAL, while rviz2 is listening with the default (volatile). The connection will be made as volatile (https://github.com/ros2/ros2/wiki/About-Quality-of-Service-Settings), which means that the latched message is never received.
robot_state_publisher is publishing the actual XML in a String, while rviz2 expects the String to contain a filepath to an urdf file. So, even if the message was received, it won't be interpreted correctly.
Clearly a bug (or 2) in rviz2, but I'm not sure about the design intent.
ROS Answers is licensed under Creative Commons Attribution 3.0 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.
