Ask Your Question
0

TurtleBot Calibration -- continuous stream of warnings and errors

asked 2011-09-01 04:14:27 -0500

Aroarus gravatar image

updated 2011-09-02 10:16:43 -0500

mmwise gravatar image

I am running the turtlebot calibration procedure for my turtlebot and I am getting a long list of scrolling errors and process restarts when I run the command:

roslaunch turtlebot_calibration calibrate.launch

I have run this before and it has worked, but now I am getting a long stream of the following. I also have a weird error that when I run any ros packages the green power light on the create turns off... but it runs anyway (such as teleop or calibrate). Namely the light turns off, the diagnostic pane says power system error, but the breaker is lit up green and the dashboard shows it to be in full mode and it responds to keyboard commands. The error I get when running calibrate.launch is below:

... logging to /home/turtlebot/.ros/log/4dd2b4ee-d4b2-11e0-89cd-485d607f80f5/roslaunch-turtlebot-laptop-600.log
Checking log directory for disk usage. This may take awhile.
Press Ctrl-C to interrupt
Done checking log file disk usage. Usage is <1GB.

started roslaunch server http://192.168.11.59:33068/

SUMMARY
========

PARAMETERS
 * /openni_camera/depth_time_offset
 * /openni_camera/image_mode
 * /kinect_laser/output_frame_id
 * /openni_camera/depth_rgb_translation
 * /pointcloud_throttle/max_rate
 * /openni_camera/depth_mode
 * /openni_camera/shift_offset
 * /scan_to_angle/min_angle
 * /kinect_laser/min_height
 * /openni_camera/depth_rgb_rotation
 * /kinect_laser_narrow/max_height
 * /scan_to_angle/max_angle
 * /kinect_laser/max_height
 * /rosdistro
 * /openni_camera/projector_depth_baseline
 * /kinect_laser_narrow/output_frame_id
 * /rosversion
 * /openni_camera/debayering
 * /openni_camera/depth_frame_id
 * /openni_camera/image_time_offset
 * /openni_camera/depth_registration
 * /kinect_laser_narrow/min_height
 * /openni_camera/rgb_frame_id

NODES
  /
    kinect_breaker_enabler (turtlebot_node/kinect_breaker_enabler.py)
    openni_manager (nodelet/nodelet)
    openni_camera (nodelet/nodelet)
    pointcloud_throttle (nodelet/nodelet)
    kinect_laser (nodelet/nodelet)
    kinect_laser_narrow (nodelet/nodelet)
    scan_to_angle (turtlebot_calibration/scan_to_angle.py)
    turtlebot_calibration (turtlebot_calibration/calibrate.py)

ROS_MASTER_URI=http://192.168.11.59:11311

core service [/rosout] found
process[kinect_breaker_enabler-1]: started with pid [745]
process[openni_manager-2]: started with pid [752]
process[openni_camera-3]: started with pid [760]
process[pointcloud_throttle-4]: started with pid [767]
process[kinect_laser-5]: started with pid [773]
process[kinect_laser_narrow-6]: started with pid [785]
process[scan_to_angle-7]: started with pid [802]
process[turtlebot_calibration-8]: started with pid [810]
Caught exception while logging: [Cannot use ros::Time::now() before the first NodeHandle has been created or ros::start() has been called.  If this is a standalone app or test that just uses ros::Time and does not communicate over ROS, you may also call ros::Time::init()]
Caught exception while logging: [Cannot use ros::Time::now() before the first NodeHandle has been created or ros::start() has been called.  If this is a standalone app or test that just uses ros::Time and does not communicate over ROS, you may also call ros::Time::init()]
[pointcloud_throttle-4] process has finished cleanly.
log file: /home/turtlebot/.ros/log/4dd2b4ee-d4b2-11e0-89cd-485d607f80f5/pointcloud_throttle-4*.log
respawning...
[pointcloud_throttle-4] restarting process
process[pointcloud_throttle-4]: started with pid [1057]
[ INFO] [1314893216.963954647]: [/openni_camera] No devices connected.... waiting for devices to be connected
[INFO] [WallTime: 1314893217.065955] Estimating imu drift
[INFO] [WallTime: 1314893217.367307] Still waiting for imu
[pointcloud_throttle-4] process has finished cleanly.
log file: /home/turtlebot/.ros/log/4dd2b4ee-d4b2-11e0-89cd-485d607f80f5/pointcloud_throttle-4*.log
respawning...
[pointcloud_throttle-4] restarting process
process[pointcloud_throttle-4]: started with pid [1165]
[INFO] [WallTime: 1314893217.669826] Still waiting for imu
[INFO] [WallTime: 1314893217.971408] Still waiting for imu
[ INFO] [1314893217.972921728]: [/openni_camera] No devices connected.... waiting for devices ...
(more)
edit retag flag offensive close merge delete

Comments

are you running diamondback or electric?
mmwise gravatar image mmwise  ( 2011-09-01 06:57:22 -0500 )edit
I am running diamondback
Aroarus gravatar image Aroarus  ( 2011-09-01 07:30:41 -0500 )edit
did the calibration finish properly? sometimes the ROS openni driver has problems starting up and you will see some errors but I haven't seen this before. Did you have the kinect.launch running before running the calibration?
mmwise gravatar image mmwise  ( 2011-09-01 08:04:15 -0500 )edit
I did not have anything else running before I ran the calibration. The calibration ran correctly, but did not stop the stream of errors when it finished. I had to kill the process to get to the numbers it printed out (the changes to the parameters) before they went off of the top of my terminal.
Aroarus gravatar image Aroarus  ( 2011-09-01 08:28:24 -0500 )edit
I think this requires a ticket..
mmwise gravatar image mmwise  ( 2011-09-01 08:49:08 -0500 )edit

1 Answer

Sort by ยป oldest newest most voted
0

answered 2011-09-01 08:50:58 -0500

mmwise gravatar image

I have files a ticket to look into what is causing the errors: https://kforge.ros.org/turtlebot/trac/ticket/57

edit flag offensive delete link more

Comments

Thank you very much! I really appreciate all of your help!
Aroarus gravatar image Aroarus  ( 2011-09-02 04:17:33 -0500 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

Stats

Asked: 2011-09-01 04:14:27 -0500

Seen: 748 times

Last updated: Sep 02 '11