-
Notifications
You must be signed in to change notification settings - Fork 299
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
Expose throughput and heartbeat settings #62
Comments
This is unfortunately not possible on a per node / per topic basis at the moment. This is on the wishlist though. Hope this helps |
That could get us working, as we do not use ROS2 directly (we are working on a Java RTPS implementation with support for ROS2 message format). Is it a possibility to make these settings user changeable after compilation so we don't have to recompile but can just set ENV variables or edit a config file? That way it might also be possible to set them on a per process basis. |
Follow-up of this discussion on rmw_fastrtps ros2/rmw_fastrtps#95 |
@jespersmith FYI since ros2/rmw_fastrtps#153 it is possible to override vendor's default QoS settings using xml files |
That sounds like a good solution to us. I'm closing this issue. |
We use the ros1 to ros2 bridge to send large point clouds around over WiFi. Because of the data size, the flood of UDP packets results in dropped packets. With the default heartbeat settings, this results in quite a big delay using RELIABLE and using BEST_EFFORT we would lose a large number of packets.
Is it possible to set the maximum throughput and configure the hearbeat settings?
The text was updated successfully, but these errors were encountered: