Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Multiple RobotModel cannot listen to different transform topics #1507

Closed
raphaeldeimel opened this issue May 26, 2020 · 1 comment
Closed

Comments

@raphaeldeimel
Copy link

Due to ros/robot_state_publisher#125 robot_state publisher in noetic no longer supports prefixing transforms.

If one publishes more than one robot state using the same robot_description (say, for visualizing multiple poses of the same robot), those now need to be published on separate topics to distinguish them. But RobotModel does not have a parameter for specifying the topic to listen to.

This is a regression / API breakage in robot_state_publisher between melodic and noetic, but it was supposedly introduced to bring noetic in line with how ROS2 works.

Example use case: publish current and expected pose of a robot:

<launch>

  <param  name="robot_description" command="$(find robot_models)/urdf/robot.urdf />

  <node name="tf_publisher" pkg="robot_state_publisher" type="robot_state_publisher" >
    <remap from="/tf" to="tf" />
  </node>

  <node name="tf_publisher2" pkg="robot_state_publisher" type="robot_state_publisher">
    <remap from="/tf" to="tf_expected" />
    <remap from="joint_states" to="joint_states_expected"/>
  </node>
 
</launch>

One way to resolve this breakage could be to add a "topic" parameter to RobotModel (defaulting to /tf)

Your environment

  • OS Version: e.g. Ubuntu 20.04
  • ROS Distro: [Noetic]
  • RViz, Qt, OGRE, OpenGl version as printed by rviz:
compiled against Qt version 5.12.8
compiled against OGRE version 1.9.0 (Ghadamon)
Forcing OpenGl version 0.
Stereo is NOT SUPPORTED
OpenGl version: 4.6 (GLSL 4.6).```
@rhaschke
Copy link
Contributor

This is not related to rviz, but to robot_state_publisher. I filed a PR to fix the issue there: ros/robot_state_publisher#139.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants