Revision history [back]

What do you want to do is not too much well explained. In any case:

ROS currently has only a basic and experimental support for windows: http://www.ros.org/wiki/win_ros. You will have to test the basic examples of this package. Also make sure that the ROS_MASTER_URI variable is properly set.

Of course you an alternative is interconecting processes using standar IPC mechanism: from simple sockets to complex web services. You can also use XML-RPC++. Using these mechanisms you would lose the majority of the runtime ROS benefits: introspection of topics, parameter server, services, dynamic reconfigure. Also many of the development and deployment ROS features like roslauch/topic remaping, etc.

What do you want to do is not too much well explained. In any case:

ROS currently has only a basic and experimental support for windows: http://www.ros.org/wiki/win_ros. You will have to test the basic examples of this package. Also make sure that the ROS_MASTER_URI variable is properly set.

Of course you an alternative is interconecting processes using standar IPC mechanism: from simple sockets to complex web services. You can also use XML-RPC++. Using these mechanisms you would lose the majority of the runtime ROS benefits: benefits as Distributed System: introspection of topics, parameter server, services, dynamic reconfigure. It also includes the powerful publish/subscribe that ROS provides: A ROS node/process can comunicate with other process in other machines in a decoupled way. That is, without knowing neither: the IP of the machine nor the proces PID nor the underlaying socket port.

Also many of the development and deployment ROS features like roslauch/topic remaping, etc.

What do you want to do is not too much well explained. In But in any case:case, here you are some important hints about using a heterogeneus network for robotic applications with/without ROS:

ROS currently has only a basic and experimental support for windows: http://www.ros.org/wiki/win_ros. You will have to test the basic examples of this package. Also make sure that the ROS_MASTER_URI variable is properly set.

Of course you an alternative is interconecting processes using standar IPC mechanism: from simple sockets to complex web services. You can also use XML-RPC++. Using these mechanisms you would lose the majority of the runtime ROS benefits as Distributed System: introspection of topics, parameter server, services, dynamic reconfigure. It also includes the powerful publish/subscribe that ROS provides: A ROS node/process can comunicate with other process in other machines in a decoupled way. That is, without knowing neither: the IP of the machine nor the proces PID nor the underlaying socket port.

Also many of the development and deployment ROS features like roslauch/topic remaping, etc.

What do you want to do is not too much well explained. But in any case, here you are some important hints about using a heterogeneus network for robotic applications with/without ROS:

ROS currently has only a basic and experimental support for windows: http://www.ros.org/wiki/win_ros. You will have to test the basic examples of this package. Also make sure that the ROS_MASTER_URI variable is properly set.

Of course you an alternative is interconecting processes using standar IPC mechanism: from simple sockets to complex web services. You can also use XML-RPC++. Using However, if you use these mechanisms you would will lose the majority of the runtime ROS benefits as Distributed System: introspection of topics, introspection, data standarization in the comunications, parameter server, services, dynamic reconfigure. It also includes the powerful publish/subscribe (topics) that ROS provides: A ROS node/process can comunicate with other process in other machines in a decoupled way. That is, without knowing neither: the IP of the machine nor the proces PID nor the underlaying socket port.

Also many of the development and deployment ROS features like roslauch/topic remaping, etc.