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

Node naming limitations #63

Closed
gstavrinos opened this issue May 31, 2017 · 4 comments
Closed

Node naming limitations #63

gstavrinos opened this issue May 31, 2017 · 4 comments

Comments

@gstavrinos
Copy link
Contributor

@gstavrinos gstavrinos commented May 31, 2017

We are using the multimaster package in a system with two machines. One machine is a Turtlebot and the other one is a Raspberry Pi 3.

For our application, we use, among many others, two nodes that are called "radio_node_manager" and "radio_node_manager_main_controller". While using rosnode list we could only detect the second node from the remote machine. After a lot of hours of frustration, it turns out that the problem lies here.

I would suggest either removing this limitation and finding another way to exclude the multimaster-specific node_manager, or at the very least, mention this limitation on github and the ROS wiki.

If you are interested in the nodes, you can check the RADIO project github page.

Thanks for this great package and your time.

@atiderko

This comment has been minimized.

Copy link
Member

@atiderko atiderko commented May 31, 2017

i'm sorry for this trouble and thank you for report this problem!
Perhaps it would help to remove '*' from filter for multimaster specific nodes?

@gstavrinos

This comment has been minimized.

Copy link
Contributor Author

@gstavrinos gstavrinos commented May 31, 2017

Removing the "*" would definitely help. I am not really sure if you use any prefixes to the "node_manager" string, and that's why I did not make a pull request.

@atiderko

This comment has been minimized.

Copy link
Member

@atiderko atiderko commented May 31, 2017

It was designed to use also namespaces, but in the practice we do not really need it. I will test it in our group before I commit this change.

@gstavrinos

This comment has been minimized.

Copy link
Contributor Author

@gstavrinos gstavrinos commented May 31, 2017

Ok! Thank you for your fast response! Happy coding!

@gstavrinos gstavrinos closed this Oct 31, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
2 participants
You can’t perform that action at this time.