-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SICK nano M1 error and lost data #150
Comments
Dear Raymond, which firmware of the nanoScan3 are you using? I guess it might be 1.92 or 1.93. There seems to be a bug on the sensor side with this firmware. If these are the firmware you are suing, please get in touch with your SICK contact, they might be able to help you. A similar problem has been seen in the ROS2 driver, see: SICKAG/sick_safetyscanners2#48 Additionally, I can't see the images and wireshark data, they don't seem to be uploaded correctly, I simply see dead links. |
Hi Puck-fzi, |
Dear Raymond, I don't quiet understand the ROS version you mean, If you have the source code, you can look in the CHANGELOG.rst in the main folder, there it should state the latest version. According to your files its the version 1.0.8 for the ROS1 driver. Could you try to resend the images from the initial issue, since I can't open them |
Hi ,
I met M1 error code 0x6307000E of nanoScan3 and can not receive any data from scanner when using nano for slam application.
I checked with SICK support and got that is due to the scanner got wrong TCP commands.
But to be honest, there is no more interaction after the 1st power on the slam ros driver, which means customer's slam contoller only activate the ros driver of nano once during the power on process as picture below.
I uploaded the normal procedure of the activation of nano data by wireshark, and also a packege with some unormal interaction between nano and controller when the issue happened.
Uploading wireshark files.zip…
would you please help to check if there is any possible reason for above issue?
thank you!
The text was updated successfully, but these errors were encountered: