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

subscribe directly to topics to avoid timing and namespace issues. #17

Closed

Conversation

cesar-lopez-mar
Copy link

When the merger is launch together with the lasers nodes, it did not subscribe to the topics. Also not when the laser nodes were launched under a namespace. The problem was created because some checks are done if the topics exists before subscribing. That is not needed since ROS takes care of that, subscribing to the topics when they appear (even if they do later than the merger). So a simpler way is just to subscribe directly and the previous issues are solved.

@iandresolares
Copy link

Hello,
I'm having issues with the multi merger node, it isn't subscribing to the topics when it should unless I execute the node seconds after all the other nodes when the laser topics are for sure being published. I think my problem is the same as yours and even though your changes look good I can't make it to work, did someone else have this persistent issue and know have to solve it?
Thanks.

@JackFrost67
Copy link
Contributor

refs #7 we can't really trust the user

@JackFrost67 JackFrost67 closed this Aug 7, 2021
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

Successfully merging this pull request may close these issues.

None yet

3 participants