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 request] Add the option to change the QoS of a topic #93

Open
charlielito opened this issue Dec 9, 2021 · 4 comments
Open

Comments

@charlielito
Copy link

charlielito commented Dec 9, 2021

When QoS doesn't match, nothing is received. For that an option to set up the QoS of the topic like in rviz2 would be very helful. For example for OccupancyGrid topics for static maps, normally the QoS is Durability: TRANSIENT_LOCAL, which currently doesn't work with rosboard.

@dheera
Copy link
Owner

dheera commented Dec 17, 2021

@charlielito :Would here be any major issues if we set the policy to all topics as TRANSIENT_LOCAL by default, before such a selection exists?

Actually I wasn't even able to get TRANSIENT_LOCATION working properly even with publisher and subscriber matching:

https://answers.ros.org/question/382626/latching-doesnt-work-in-ros2/

@charlielito
Copy link
Author

I don't think that would be a proper solution, since most of topics are VOLATILE. According to this link, VOLATILE publishers are not compatible with TRANSIENT_LOCAL subscriptions.

In my case, I've been working with ROS2 foxy and galactic and it does work TRANSIENT_LOCAL publisher and subscribers.

@dheera
Copy link
Owner

dheera commented Feb 24, 2023

Hi folks,
Sorry I haven't been active on this for a while due to a new job. Let me look into this issue and try to reproduce all the combinations of QoS to see what works.

@charlielito
Copy link
Author

Hi folks, Sorry I haven't been active on this for a while due to a new job. Let me look into this issue and try to reproduce all the combinations of QoS to see what works.

This is already addressed in #104

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