Closed maracuya-robotics closed 2 months ago
Thank you very much for your feedback. We will correct range_min
in thesensor_msgs/LaserScan
messages in the next release. In the meantime please replace line 846 in driver/src/sick_scansegment_xd/ros_msgpack_publisher.cpp by 0.05f for multiScan and picoScan:
laser_scan_msg.range_min = std::max(0.05f, laser_scan_msg.range_min); // min range of multiScan and picoScan: 0.05 [m]
While using
sick_scan_xd
with a SICK picoScan150, I noticed that therange_min
field of thesensor_msgs/LaserScan
message is always set to0.0
. At the same time, invalid range measurements are set to zero. According to the definition of the message invalid measurements should not be included within this range:The documentation says that the picoScan150 has a design limitation of
range_min = 0.05
, thereforerange_min
should be set to this value in the message. Alternatively define invalid scans asNaN
or+infinity
.