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

QoS profiles available in the plugin #134

Closed
dbarrita opened this issue Feb 15, 2024 · 6 comments
Closed

QoS profiles available in the plugin #134

dbarrita opened this issue Feb 15, 2024 · 6 comments

Comments

@dbarrita
Copy link

Hi, I'm using the plugin and I need fast communication in my publishers and subscribers. I have seen that there are different QoS profiles available in the plugin that appear in the ROS2 documentation: Default, Services, Sensor Data, Parameters and System Default. However, there are other options available such as: ClockPub, StaticBroadcaster, DynamicBroadcaster, UnknowQoS which are not defined. Could you specify what is the behavior of these profiles or point me to the documentation that describes these profiles? Thanks.

@yuokamoto
Copy link
Contributor

Hi, thanks for your question.
We haven't add those in documentation but you can find definition here in source code
https://rclue.readthedocs.io/en/devel/doxygen_generated/html/d8/d54/rclc_utilities_8h_source.html

which follows rmw definition here
http://docs.ros.org/en/humble/p/rmw/generated/file_include_rmw_qos_profiles.h.html#file-include-rmw-qos-profiles-h

@dbarrita
Copy link
Author

Hi, thanks for the quick reply! Now I have enough information to choose the best option for my problem.

@dbarrita
Copy link
Author

Hi again, I was checking the different QoS profiles in the source code (link) and I see that in this plugin there is no option for a profile with reliability "best effort". However, this policy is set in the ROS2 profiles (link) in the sensor_data profile. Is there a reason for not having a best effort option? Thanks in advance!

@dbarrita dbarrita reopened this Feb 27, 2024
@yuokamoto
Copy link
Contributor

Honestly says, I don't remember...
Maybe just a bug, we can create PR to fix to use best effort

@dbarrita
Copy link
Author

Thanks for the answer, it would be interesting if you could create the PR to have the sensor data with best effort option, because is the only profile that use best effort for this policy.

@yuokamoto
Copy link
Contributor

#135

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

2 participants