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 |
There is a multi_robot_test.launch that works with trunk of simulator_gazebo. It starts up 3 robots under separate ros namespaces.
The image_proc and stereo_image_proc nodes are commented out for now, just requires some accounting to put back in if anyone is interested.
| | 2 | No.2 Revision |
There is a multi_robot_test.launch that works with trunk of simulator_gazebo. It starts up 3 robots under separate ros namespaces.
I basically started with standard pr2_empty_world.launch and namespaced nodes / added tf_prefixes.
The image_proc and stereo_image_proc nodes are commented out for now, just requires some accounting to put back in if anyone is interested.
| | 3 | No.3 Revision |
There is a multi_robot_test.launch that works with trunk of simulator_gazebo. It starts up 3 robots under separate ros namespaces.
I basically started with standard pr2_empty_world.launch and namespaced nodes / added tf_prefixes.
The image_proc and stereo_image_proc nodes are commented out for now, just requires some accounting to put back in if anyone is interested.
| | 4 | No.4 Revision |
There is a multi_robot_test.launch that works with trunk of simulator_gazebo. It starts up 3 robots under separate ros namespaces.
I basically started with standard pr2_empty_world.launch and namespaced nodes / added tf_prefixes.
robots spawn and pieces of it are controllable if you configure your teleop to work under a namespace, but otherwise much of this is untested.
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.
