ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange
Ask Your Question

nonnoc's profile - activity

2017-11-03 13:28:10 -0500 received badge  Taxonomist
2012-12-02 23:42:02 -0500 received badge  Popular Question (source)
2012-12-02 23:42:02 -0500 received badge  Notable Question (source)
2012-12-02 23:42:02 -0500 received badge  Famous Question (source)
2011-12-08 02:35:01 -0500 received badge  Student (source)
2011-12-07 10:03:06 -0500 asked a question Unknown exception errors in sick_ldmrs "offset must be non-negative"

Currently working on an autonomous vehicle project where the majority of software is written in ROS and I am using the ibeo LUX lidar for object detection along with the sick_ldmrs lidar driver code (as a part of the csiro-asl-ros-pkg). I recently came across some strange exceptions and was wondering if anyone recognized them, or had any inkling as to their origin and (hopefully) how to fix them. Both errors were exceptions caught by sickldmrs.py on line 394

   rospy.logwarn('Caught unknown exception: %s...restarting transport.' % e)

The first said "index out of bounds" and was most likely triggered within dataproc.py around lines 153-155

if any(["scan" in topic and num_subs > 0 for topic, num_subs in subscribers.iteritems()]):
  self.make_scans()
  self.publish_scans()

The second error said "offset must be non-negative and smaller than buffer lenth (44)", and I do not have any idea where it was triggered.

On a related note, I noticed that there was a large pool of water near the sensor when these errors were triggered. Has anyone ever experienced issues with water and the sick_ldmrs driver? Thanks for any help. I would appreciate even a rough guess of the origin for either error.

For reference I am using Diamondback with Ubuntu 11.04