The site is read-only. Please transition to use Robotics Stack Exchange
| ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
 | 1 | initial version |
If you simply want two robots and one worksstation PC to communicate via network, and you can guarantee full network connectivity at all times between all involved PCs, you don't need multimaster. Instead, you can just use the built-in ROS functionality. There's a tutorial here.
| | 2 | No.2 Revision |
If you simply want two robots and one worksstation PC to communicate via network, and you can guarantee full network connectivity at all times between all involved PCs, you don't need multimaster. Instead, you can just use the built-in ROS functionality. There's a tutorial here.
UPDATE1: To avoid name conflicts, you need to remap everything related to a specific robot into a namespace. So robot1 would receive commands on the topic /robot1/cmd_vel, robot2 likewise on the topic /robot2/cmd_vel, and both could exchange messages via some topic, say /shared_topic. The master needs to run on one of those robots (or on an entirely different PC), it doesn't really matter where it runs. The only important thing is that there is exactly one master, and all other PCs connect to it.
ROS Answers is licensed under Creative Commons Attribution 3.0 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.
