ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
1 | initial version |
I would like to extend jaco answer as this is an easy solution to a struggle lot of people, including myself run into when starting rosrun --debug rviz rviz
(debug for verbose)
The solution is having a publisher for the fixed frame attached to the grid that describes your frame relative to it. This means using the quaternion/euler-angles rviz can transform the coordinate system from the fixed one into your frame. This is sets up a publisher that tells rviz where to put the fixed world frame.
rosrun tf static_transform_publisher 0 0 0 0 0 0 1 map my_frame 10
The one is necessary as its the quaternion identity 0 0 0 1.
The doc says this:
static_transform_publisher x y z qx qy qz qw frame_id child_frame_id period_in_ms
or in eulers as jaco did
static_transform_publisher x y z yaw pitch roll frame_id child_frame_id period_in_ms
having this publisher running the global status of the fixed frame is known and the Fixed Frame
No tf data. Actual error: Fixed Frame [map] does not exist
disappears.
2 | No.2 Revision |
I would like to extend jaco answer as this is an easy solution to a struggle lot of people, including myself run into when starting rosrun --debug rviz rviz
(debug for verbose)
The solution is having a publisher for the fixed frame attached to the grid that describes your frame relative to it. This means using the quaternion/euler-angles rviz can transform the coordinate system from the fixed one into your frame. This is sets up a publisher that tells rviz where to put the fixed world frame.
rosrun tf static_transform_publisher 0 0 0 0 0 0 1 map my_frame 10
The one is necessary as its the quaternion identity 0 0 0 1.
The doc says this:
static_transform_publisher x y z qx qy qz qw frame_id child_frame_id period_in_ms
or in eulers as jaco did
static_transform_publisher x y z yaw pitch roll frame_id child_frame_id period_in_ms
having this publisher running the global status of the fixed frame is known and the Fixed Frame
No tf data. Actual error: Fixed Frame [map] does not exist
disappears.
Update:
Quicker: After $ rosrun rviz rviz
change the option Fixed Frame on the left hand side under Global Options ( in the Display Panel) from map (default) to base_link
in the dropdown menu.
3 | No.3 Revision |
I would like to extend jaco answer as this is an easy solution to a struggle lot of people, including myself run into when starting rosrun --debug rviz rviz
(debug for verbose)
The solution is having a publisher for the fixed frame attached to the grid that describes your frame relative to it. This means using the quaternion/euler-angles rviz can transform the coordinate system from the fixed one into your frame. This is sets up a publisher that tells rviz where to put the fixed world frame.
rosrun tf static_transform_publisher 0 0 0 0 0 0 1 map my_frame 10
The one is necessary as its the quaternion identity 0 0 0 1.
The doc says this:
static_transform_publisher x y z qx qy qz qw frame_id child_frame_id period_in_ms
or in eulers as jaco did
static_transform_publisher x y z yaw pitch roll frame_id child_frame_id period_in_ms
having this publisher running the global status of the fixed frame is known and the Fixed Frame
No tf data. Actual error: Fixed Frame [map] does not exist
disappears.
Update:
Quicker: After $ rosrun rviz rviz
change the option Fixed Frame on the left hand side under Global Options ( in the Display Panel) from map (default) to base_link
in the dropdown menu.