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
OS: ROS2 Humble
Problem description:
Whenever I try to read /testing_only/track message it shows nothing.
Message flow diagram:
FSDS -> fsds_ros2_bridge -> ros2 topic echo command/c++ subscriber.
Prior investigation conclusions:
I think that fsds_ros2_bridge is at fault.
/testing_only/track is a latched message.
Latched messages in ROS2 work by setting proper QoS profile: "The “durability” policy “transient local”, combined with any depth, provides functionality similar to that of “latching” publishers." Source
Requirement from point 3. is not met because message qos-durability is set to volatile (which means that samples don't persist on the publisher side) SOURCE.
Point 4. evidence (output of ros2 topic info --verbose /testing_only/track):
Possible solution: Change fsds_ros2_bridge QoS profile for /testing_only/track message (as described in point 3.)
Is that possible to change QoS profile in fsds_ros2_bridge?
The text was updated successfully, but these errors were encountered:
I currently do not have a ROS2 environment set up. If you'd like to have this implemented quickly and would like to contribute, feel free to open a PR. Otherwise I will have to find some time (probably next week).
OS: ROS2 Humble
Problem description:
Whenever I try to read /testing_only/track message it shows nothing.
Message flow diagram:
FSDS -> fsds_ros2_bridge -> ros2 topic echo command/c++ subscriber.
Prior investigation conclusions:
Point 4. evidence (output of
ros2 topic info --verbose /testing_only/track
):Possible solution: Change fsds_ros2_bridge QoS profile for /testing_only/track message (as described in point 3.)
Is that possible to change QoS profile in fsds_ros2_bridge?
The text was updated successfully, but these errors were encountered: