ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange
Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

Hi @Miracle,

In the tutorial you posted they used a fixed frame (namely the camera link name) that is used to produce the plugin messages. Included with the plugin param <frameName>camera_link</frameName>: this is telling the plugin to produce the camera msgs with the header frame as camera_link. If you do not have a proper tf_tree you will be only able to see its msgs in rviz with the fixed frame set up as camera_link (This option is in the right panel->Displays->Global Options->Fixed Frame).

However in general what do you want here is a full working tf_tree able to relatee very important link in space for your robot. So you can have a global frame, for instance map or odom wich are conected to the base_link and from the base_link to other important joints or your robot. This is for Rviz to be able to apply the proper transformation for every topic and properly visualize all from the global frame. So theoretically, you can use only the fixed_frame of the camera but that in the future is not a good practice to carry out.

For generating a tf_tree for your robot you can use the robot_state_publisher node. And if you want more information about ROS frames you can check its standard.

Hope this helped you.

Regards.