search

SICKAG / sick_safetyscanners

ROS driver for SICK safety laser scanners
https://www.sick.com/de/en/opto-electronic-protective-devices/safety-laser-scanners/c/g187225
Apache License 2.0
61 stars 59 forks source link

ros driver stop #84

Closed Raymond-601-cmd closed 3 years ago

Raymond-601-cmd commented 3 years ago

Dear, We are using SICK nanoScan3 core IO on our AGVs, and we just use the ros driver from github for navigation system. But the ros driver stopped suddenly durign the running of AGV recently as below picture: 01 02 03 Could you help to analyze this issue? Thanks.

lenpuc commented 3 years ago

Hi there,

from the provides screenshot I can not tell what happened. Except that there was a crash with a SIGABRT. So most likely some internal signal triggered the abort through an assert or something similar. However, I can not deduct from the provided info why this was happening.

Is this a reoccurring issue? Or did this happen only once so far? If this happens frequently please make sure you have the latest version of the driver and for debugging purposes best build it from source with debug flags enabled. Then you can get a trace with gdb, which might help to analyze the issue.

Raymond-601-cmd commented 3 years ago

Hi there,

from the provides screenshot I can not tell what happened. Except that there was a crash with a SIGABRT. So most likely some internal signal triggered the abort through an assert or something similar. However, I can not deduct from the provided info why this was happening.

Is this a reoccurring issue? Or did this happen only once so far? If this happens frequently please make sure you have the latest version of the driver and for debugging purposes best build it from source with debug flags enabled. Then you can get a trace with gdb, which might help to analyze the issue.

Thank you for your support. Yes, It happened several times but not regular. You mean we need to tranck the log for this issue,right?

lenpuc commented 3 years ago

Sorry for the late reply.

Yes you need to have debug flags enabled and provide a stack trace. Otherwise it will be impossible for me to pinpoint where the error resides.

so best build the driver from source using CMAKE_BUILD_TYPE=Debug

and start the driver with gdb

lenpuc commented 3 years ago

Closing this, if there are further problems please reopen