search

SICKAG / sick_scan_xd

Based on the sick_scan drivers for ROS1, sick_scan_xd merges sick_scan, sick_scan2 and sick_scan_base repositories. The driver supports both Linux (native, ROS1, ROS2) and Windows (native and ROS2).
Apache License 2.0
89 stars 81 forks source link

Question: Multiscan seems to shut off after a while #350

Closed Navsea closed 2 weeks ago

Navsea commented 2 weeks ago

Hi,

Is this the right place to ask these kind of questions? Seems it might not be really driver related, but I have gotten knowledgeable responses here before, so that's why i post it here.

We have a multiscan lidar running in the field, and it seems that from time to time (every x days), we stop getting lidar data. We currently suspect that the callback of the lidar ROS driver no longer gets called, when spinning the node. Probably because the sensor is off.

When the machine shuts off, and later on again (and the ROS driver gets restarted) we get data again.

Would anyone have an idea of what the reasons for a shutdown could be. I know we've previously experienced that the multiscan can shut down when overheating (at 50deg, it was in direct sunlight...). Now we have a cover shielding it from the sun, but maybe it's not enough to prevent it from overheating. Are there any other situations that you could think of?

How would you go about debugging these kinds of things? I saw the C++ driver has a diagnostic message, but I don't think there are diagnostic messages available for the ROS driver right? Do we have to start using the proprietary protocol so that we can access additional information?

Best regards, Kenneth

rostest commented 2 weeks ago

Thanks for your feedback. We recommend to contact the SICK support for issues with overheating.

The diagnostic messages of the C-API provides the informational logmessages, warnings and error from the ROS driver. They do not provide further informations than the ROS messages.