Debug output within a launch file

debug
launch

asked 2011-03-31 06:38:12 -0600

JediHamster
995 ●42 ●53 ●59 http://sluggish.dyndns.org/

How do I enable debugging output (ROS_DEBUG) for a node within a launch file?

edit retag flag offensive close merge delete

add a comment

15

answered 2011-03-31 15:04:36 -0600

joq
25443 ●181 ●256 ●408

updated 2011-04-01 03:16:05 -0600

The previous answer is incomplete. Setting output="screen" in the launch file will show INFO messages and above, not DEBUG output.

For that, you can set the ROS console configuration.

The rxconsole package allows dynamic setting and resetting of DEBUG output. The "Levels" button near the lower right corner can set each C++ logger to any level. (It has no effect on Python loggers.)

edit flag offensive delete link

Comments

Yes. rxconsole is really what I was looking for. Screen output seems to display everything except debug information.

JediHamster ( 2011-03-31 21:27:18 -0600 )edit

Can the debug information be pushed to the console or do we have to view it in rqt?

2ROS0 ( 2016-11-01 22:41:44 -0600 )edit

Just set output="screen" in the launch file as mentioned below. I prefer rqt_console over the screen. It's much easier to filter and even pause the output.

roboticom314 ( 2016-11-09 09:09:09 -0600 )edit

I think the ros console wiki had confusing language until I edited it just now- but to be clear there is no way to have a node launch with a specific logger level, if you want debug on to catch node start debug messages you have to go outside the launch file and edit this conf file (without going to extremes to have a launch file write DEBUG or INFO to a conf file and then load that with env, and the order of execution would probably be wrong without going to even further extremes of nested launch files)- is that right?

And there is no per-node log level capability in the conf file, just per-package?

lucasw ( 2021-11-25 10:13:48 -0600 )edit

add a comment

3

answered 2011-03-31 07:29:04 -0600

Murph
1033 ●33 ●41 ●55 http://localhost/

In the node definition, you can set the output to screen: <node pkg="amcl" type="amcl" name="amcl" output="screen"> for example. That will get the output pushed to your console.

You can also often find the information you're looking for through the rxconsole program. It's nice for separating the output from the many nodes that are launched, as well as displaying based on severity (warnings, errors, debugs).

edit flag offensive delete link

add a comment

Debug output within a launch file

2 Answers

Comments

Question Tools

Stats

Related questions

Debug output within a launch file edit

2 Answers

Comments

Question Tools

Stats

Related questions

Debug output within a launch file