-
Notifications
You must be signed in to change notification settings - Fork 4
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
Multicast in docker #208
Comments
Original comment by Vinayak Jagtap (Bitbucket: vinayak_jagtap).
|
Original comment by Nate Koenig (Bitbucket: Nathan Koenig). Can you offer some insight as to why you need multimaster? Normally, multimaster is used when there are multiple robots. |
Original comment by Vinayak Jagtap (Bitbucket: vinayak_jagtap). That's right, we are using multimaster for forwarding data on topics to OCU. |
Original comment by Akihiko Honda (Bitbucket: akiHonda). Our team are also planning to use multimaster method. We work hard to realize it and got some advance, however it is not completed. I think the problem is a location of ROS master and communication blocking. Is there any chance to get new option to choose the location of ROS master ? (If we predict the real mars mission, ROS master will be located in FC, not mars environment.) |
Original comment by Rud Merriam (Bitbucket: rmerriam). I had some luck locally using the NMap ncat to do a bidirectional transfer of ROS topics. That was local docker to my desktop. I stumbled on getting it to work with CouldSim. |
Original report (archived issue) by Vinayak Jagtap (Bitbucket: vinayak_jagtap).
The multimaster options in ROS need multicast to be enabled on the system otherwise the connection breaks every few minutes. Is that possible in Docker? Has anyone successfully configured multimaster that is running for something like 30minutes or more?
The text was updated successfully, but these errors were encountered: