Revision history [back]

It looks like it's undocumented, and it even gives a warning if you try to use it, but! You can, in fuerte, at least, add a "machine" attribute to an "include" tag in a launchfile.

See here for setting up machine tags: http://www.ros.org/wiki/roslaunch/XML/machine

And then just simply do (with appropriate values) something like:

<launch>
  <machine name="other-pc" address="192.168.13.37" env-loader="/opt/ros/fuerte/env.sh"/>
  <include file="/path/to/file/on/remote/machine.launch" machine="other-pc"/>
</launch>

It looks like it's undocumented, and it even gives a warning if you try to use it, but! You can, in fuerte, at least, add a "machine" attribute to an "include" tag in a launchfile.

See here for setting up machine tags: http://www.ros.org/wiki/roslaunch/XML/machine

And then just simply do (with appropriate values) something like:

<launch>
  <machine name="other-pc" address="192.168.13.37" env-loader="/opt/ros/fuerte/env.sh"/>
  <include file="/path/to/file/on/remote/machine.launch" file="/path/to/file/on/local/machine.launch" machine="other-pc"/>
</launch>

It looks like it's undocumented, and it even gives a warning if you try to use it, but! You can, in fuerte, at least, add a "machine" attribute to an "include" tag in a launchfile.launchfile and get it to launch everything in that included launchfile to come up on another machine.

See here for setting up machine tags: http://www.ros.org/wiki/roslaunch/XML/machine

And then just simply do (with appropriate values) something like:

<launch>
  <machine name="other-pc" address="192.168.13.37" env-loader="/opt/ros/fuerte/env.sh"/>
  <include file="/path/to/file/on/local/machine.launch" machine="other-pc"/>
</launch>

It looks like what this is doing is actually reading a launchfile on the local machine, and then bringing up its nodes on the other machine!