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
Currently, the ros2 topic hz verb does not allow the user to specify qos settings.
We had a case where ros2 topic hz did not report the expected frequency. In this case, 12 messages was published at a burst at 10 Hz (resulting in an expected frequency of 120 Hz). The hz verb uses the sensor_data qos profile, which has a queue depth of 5. This caused messags to be dropped, and ros2 topic hz only reporting about 70-80 Hz. Setting up a separate subscriber with a queue depth > 12 we received all the messages.
It would be very nice to be able to specify the qos settings in a similar way as e.g. ros2 topic echo.
Implementation considerations
This could probably be implemented in a similar way as for the other ros2 topic verbs?
The text was updated successfully, but these errors were encountered:
Feature description
Currently, the
ros2 topic hz
verb does not allow the user to specify qos settings.We had a case where
ros2 topic hz
did not report the expected frequency. In this case, 12 messages was published at a burst at 10 Hz (resulting in an expected frequency of 120 Hz). Thehz
verb uses thesensor_data
qos profile, which has a queue depth of 5. This caused messags to be dropped, andros2 topic hz
only reporting about 70-80 Hz. Setting up a separate subscriber with a queue depth > 12 we received all the messages.It would be very nice to be able to specify the qos settings in a similar way as e.g.
ros2 topic echo
.Implementation considerations
This could probably be implemented in a similar way as for the other
ros2 topic
verbs?The text was updated successfully, but these errors were encountered: