Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

This is expected behavior: from http://www.ros.org/wiki/roslaunch/Architecture,

"Remote processes do not forward their stderr/stdout to your local console. In general, nodes should be reporting important information using ROS' builtin logging mechanisms (i.e. rosconsole for roscpp, logout/logerr for rospy, etc...). This allows you to view this important information via the rosout tools."

On your local machine where you do have an X-server, start up a terminal, set the ROS_MASTER_URI environment variable to point to the master on computer A, then run rxconsole.

This is expected behavior: from http://www.ros.org/wiki/roslaunch/Architecture,

"Remote processes do not forward their stderr/stdout to your local console. In general, nodes should be reporting important information using ROS' builtin logging mechanisms (i.e. rosconsole for roscpp, logout/logerr for rospy, etc...). This allows you to view this important information via the rosout tools."

On your local machine where you do have an X-server, start up a terminal, set the ROS_MASTER_URI environment variable to point to the master on computer A, then run rxconsole.rqt_console.