Skip to content
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

[Feature] Use DDS Liveliness Qos instead of periodic messages #88

Open
Aposhian opened this issue Jul 25, 2022 · 0 comments
Open

[Feature] Use DDS Liveliness Qos instead of periodic messages #88

Aposhian opened this issue Jul 25, 2022 · 0 comments

Comments

@Aposhian
Copy link

Currently, bond relies on sending ReliabilityPolicy::Reliable messages periodically, with managed timers, timeouts, etc. In ROS2 over DDS, these sorts of features are actually built into the RMW in a more efficient way, by using Liveliness QoS, and liveliness event callbacks.

That way, if you just want a heartbeat, it is possible even to simply renew your lease duration periodically, and not even actually publish a message at all, if no data needs to be transmitted.

Motivation

bond uses quite a lot of DDS bandwidth for the task of keeping multiple nodes alive together.

Implementation concerns

Since advanced QoS is not used by most ROS2 users, the common middlewares (FastDDS, CycloneDDS) are inconsistent in their implementation of liveliness qos events at the rclcpp level, from my experience.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant