-
Notifications
You must be signed in to change notification settings - Fork 200
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
tf2_ros::StaticTransformBroadcaster does not keep last msg for later subscription #183
Comments
It is kept, but the naming in DDS (and hence ROS 2) is different. In ROS 2, a "latched" topic is called "transient local". If the publisher is a "transient local", then it will hold a copy for any subscriber that comes in later. However, the subscriber must also be "transient local" for this to work. If you use the stock TF2 clients, they have the appropriate QoS settings for this to work. If you are subscribing to I'm going to close this out assuming that is what is going on here, but feel free to keep commenting or re-open if this doesn't work for you. |
@sharronliu I noticed you're using |
added one known issue ros2/geometry2#183 Signed-off-by: Sharron LIU <sharron.liu@intel.com>
Transient local durability will be supported in Eloquent. This patch workaround this issue till adaption to Eloquent. ros2/geometry2#183 Signed-off-by: Sharron LIU <sharron.liu@intel.com>
Bug report
Required Info:
Steps to reproduce issue
In rclcpp node, send static TF using
tf2_ros::StaticTransformBroadcaster::sendTransform()
. The function was invoked only once, since the TF is unchanged. The observation is the msg was not received by a later subscription. This behavior differs from ROS1.Try to instanciate the rclcpp node with below QoS profile, problem still observed.
Please can you suggest any other parameters may lead to the problematic result?
Expected behavior
The static msg was kept for later subscription
Actual behavior
The static msg was not received in later subscription
The text was updated successfully, but these errors were encountered: