ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
1 | initial version |
What people normally do in this situation is:
1) send the log messages to stdout. Messages are displayed immediately, without any buffering. This can be configured in your launch file (per node), or on the roslaunch
command line. Be aware that just because roslaunch told you the filename at node start doesn't mean the node wrote anything.
2) Install the tools rqt_console
and rqt_logger_level
to get access to more detailed messages. These are GUI tools, so it is more complicated because they require a machine with a screen, and the machine must be part of your ros network.
2 | No.2 Revision |
What people normally do in this situation is:
1) send the log messages to stdout. Messages are displayed immediately, without any buffering. This can be configured in your launch file (per node), or on the roslaunch
command line. Be aware that just because roslaunch told you the filename at when the node start started doesn't mean the node actually wrote anything.
2) Install the tools rqt_console
and rqt_logger_level
to get access to more detailed messages. These are GUI tools, so it is more complicated because they require a machine with a screen, and the machine must be part of your ros network.