Skip to content
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

Open
Raymond601 opened this issue Sep 24, 2024 · 5 comments
Open

SICK nano M1 error and lost data #150

Raymond601 opened this issue Sep 24, 2024 · 5 comments

Comments

@Raymond601
Copy link

Raymond601 commented Sep 24, 2024

Hi ,
I met M1 error code 0x6307000E of nanoScan3 and can not receive any data from scanner when using nano for slam application.
M1 error code

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.
Only once activate udp data for nano

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.
[
tcpdump(0).zip
](url)

would you please help to check if there is any possible reason for above issue?
thank you!

@lenpuc
Copy link
Collaborator

lenpuc commented Sep 25, 2024

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.
Best regards

@Raymond601
Copy link
Author

Hi Puck-fzi,
Thank you for your information, I forward your recommendation to SICK AG, and I think they may get in touch with you these days.
one more quesion is that another engineer shared the ros driver document with me, but I cannot find the version inside it.
would you please help to check how can I find the ros revision?

@Raymond601
Copy link
Author

SICK ROS.zip

@lenpuc
Copy link
Collaborator

lenpuc commented Sep 27, 2024

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

@Raymond601
Copy link
Author

Raymond601 commented Dec 12, 2024

Hi Puck-fzi,
Sorry for lately reply, I've uploaded the images and wireshark files in initial chatbox.
Would you please help to check if it's related to the firmware of nano 1.92 /.93 or other reasons?

One more question is that is there any reconnection method between laser scanner and host in the ros driver 1.0.9?
as several customers mentioned, once there is an issue on the safety laser scanner or network connection, their controller cannot got the data from laser scanner.
thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants