Errors when using ocean_battery_driver

Error: Cannot open /dev/ttyUSB0

  •  user@prX: rosrun ocean_battery_driver monitor 
     sh: cannot open /dev/ttyUSB0: No such file
     cannot open port [/dev/ttyUSB0]


  • Is the battery system connected?
    • No device is connected.
  • You can run battery_check to try to get more information.

rosrun ocean_battery_driver battery_check -v /dev/ttyUSB0

Error: Battery status gui comes up empty

Screenshot-PR2 Power State.png


  • Is the battery monitor running on your robot?
    • On the robot
      •    $~/ros/ros-pkg/drivers/robot/pr2/ocean_battery_driver/ ./scripts/view_batteries
    • Off the robot
      •    $ ssh prX2 rosrun ocean_battery_driver view_batteries
  • Is your ROS_MASTER_URI pointing at the right place?

Error: Batteries report "No Good"

The "No Good" message means the batteries are in a lockout/error state. When a battery is drained too low, it can disable itself to prevent further damage, and enable the "No Good" state.

In order to reset this message, the ocean battery server needs to be completely power cycled.

If you see this message on a PR2, contact Willow Garage Support.

Error: Battery Report "Stale updates" or "No updates"

The batteries periodically publish their status to the ocean battery driver. If they go too long before publishing status, the battery driver will report a warning or error. The timeouts for these warnings and errors can be adjusted with the ~lag_timeout and ~stale_timeout parameters to the battery driver.

If a battery reports this message, and the timeout is sufficiently long (over 60 seconds, for most purposes), this probably means a connection problem with the battery.

At the end of the diagnostic message for each battery, they report "Time since update (s)". If this value is "N/A", this means the battery has not updated, and is probably disconnected.

Wiki: ocean_battery_driver/Troubleshooting (last edited 2010-09-10 20:55:06 by KevinWatts)