ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
1 | initial version |
You could try to set a logging level for all your environment to debug
by adding the following configuration file:
# Override my package to output everything
log4j.logger.ros.YOUR_PACKAGE_NAME=DEBUG
You can load this set of parameters from a launch file simple adding:
2 | No.2 Revision |
You could try to set a logging level for all your environment to debug
by adding the following configuration file:
# Override my package to output everything
log4j.logger.ros.YOUR_PACKAGE_NAME=DEBUG
You can load this set of parameters from a launch file simple adding:
<env name="ROSCONSOLE_CONFIG_FILE" value="$(find mypackage)/custom_rosconsole.conf"/>
This will work for C++. There is a different method for python nodes it seems.
This answer has been pretty much taken from here.
3 | No.3 Revision |
You could try to set a logging level for all your environment package to debug
by adding the following configuration file:file (don't forget to change the package name):
# Override my package to output everything
log4j.logger.ros.YOUR_PACKAGE_NAME=DEBUG
You can load this set of parameters from a launch file simple simply adding:
<env name="ROSCONSOLE_CONFIG_FILE" value="$(find mypackage)/custom_rosconsole.conf"/>
YOUR_PACKAGE_NAME)/custom_rosconsole.conf"/>
This will should work for C++. There is a different method for python nodes it seems.
This answer has been pretty much taken from here.