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
You will need two machines with ROS 2: one mobile and one stationary.
# User input in terminal 1
ros2 run topic_monitor topic_monitor --display
Run the ros2 launch topic_monitor reliability_demo_launch.py executable on the stationary machine. This will start two nodes: one publishing in “reliable” mode, and one in “best effort”.
# User input in terminal 1
ros2 launch topic_monitor reliability_demo_launch.py
Start the monitor on a mobile machine such as a laptop. Use ros2 run topic_monitor topic_monitor --display --allowed-latency 5 to account for any latency that may occur re-sending the reliable messages.
# User input in terminal 1
ros2 run topic_monitor topic_monitor --display --allowed-latency 5
Take the mobile machine out of range of the monitor, and observe how the reception rates differ for the different topics.
Expect
You should see that the "reliable" topic has a reception rate that is almost always either 0 or 100%, while the "best effort" topic has a reception rate that fluctuates based on the strength of the connection.
You can find the code used to generate this test case here
Setup
Links
Checks
Comparing reliability QoS settings
details
Try
You will need two machines with ROS 2: one mobile and one stationary.
# User input in terminal 1 ros2 run topic_monitor topic_monitor --displayRun the
ros2 launch topic_monitor reliability_demo_launch.pyexecutable on the stationary machine. This will start two nodes: one publishing in “reliable” mode, and one in “best effort”.# User input in terminal 1 ros2 launch topic_monitor reliability_demo_launch.pyStart the monitor on a mobile machine such as a laptop. Use
ros2 run topic_monitor topic_monitor --display --allowed-latency 5to account for any latency that may occur re-sending the reliable messages.# User input in terminal 1 ros2 run topic_monitor topic_monitor --display --allowed-latency 5Take the mobile machine out of range of the monitor, and observe how the reception rates differ for the different topics.
Expect
You should see that the "reliable" topic has a reception rate that is almost always either 0 or 100%, while the "best effort" topic has a reception rate that fluctuates based on the strength of the connection.
You can find the code used to generate this test case here