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 |
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.
| | 2 | No.2 Revision |
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.
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.
