You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Remove the deprecated 'use_tf_static' parameter. Now fixed transforms
will always be published to the topic /tf_static.
This change also avoid repeatedly publishing the same transforms.
This restores the behavior from ROS 1; now a single "latched" message
is published over /tf_static.
Signed-off-by: Jacob Perron <[email protected]>
Copy file name to clipboardExpand all lines: README.md
+8-4Lines changed: 8 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,8 +2,13 @@ Robot State Publisher
2
2
=====================
3
3
4
4
This package contains the Robot State Publisher, a node and a class to publish the state of a robot to tf2.
5
-
Once the state gets published, it is available to all components in the system that also use tf2.
6
-
The package takes the joint angles of the robot as input and publishes the 3D poses of the robot links, using a kinematic tree model of the robot.
5
+
At startup time, Robot State Publisher is supplied with a kinematic tree model (URDF) of the robot.
6
+
It then subscribes to the `joint_states` message (of type `sensor_msgs/msg/JointState`) to get individual joint states.
7
+
These joint states are used to update the kinematic tree model, and the resulting 3D poses are then published to tf2.
8
+
9
+
Robot State Publisher deals with two different "classes" of joint types: fixed and movable.
10
+
Fixed joints (with the type "fixed") are published to the transient_local `/tf_static` topic once on startup (transient_local topics keep a history of what they published, so a later subscription can always get the latest state of the world).
11
+
Movable joints are published to the regular `/tf` topic any time the appropriate joint is updated in the `joint_states` message.
7
12
8
13
Examples showing how to pass the `robot_description` parameter using a launch file are available in the 'launch' subdirectory.
9
14
@@ -20,7 +25,6 @@ Subscribed Topics
20
25
Parameters
21
26
----------
22
27
*`robot_description` (string) - The original description of the robot in URDF form. This *must* be set at robot_state_publisher startup time, or the node will fail to start. Updates to this parameter will be reflected in the `robot_description` topic.
23
-
*`publish_frequency` (double) - The frequency at which fixed transforms will be republished to the network. Defaults to 20.0 Hz.
24
-
*`use_tf_static` (bool) - Whether to publish fixed joints on the static broadcaster (`/tf_static` topic) or on the dynamic one (`/tf` topic). Defaults to true, so it publishes on the `/tf_static` topic.
28
+
*`publish_frequency` (double) - The maximum frequency at which non-static transforms (e.g. joint states) will be published to `/tf`. Defaults to 20.0 Hz.
25
29
*`ignore_timestamp` (bool) - Whether to accept all joint states no matter what the timestamp (true), or to only publish joint state updates if they are newer than the last publish_frequency (false). Defaults to false.
26
30
*`frame_prefix` (string) - An arbitrary prefix to add to the published tf2 frames. Defaults to the empty string.
0 commit comments