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

S2 - Error, RPLidar internal error detected. Please reboot the device to retry #152

Open
CycleMark opened this issue Feb 3, 2024 · 2 comments

Comments

@CycleMark
Copy link

Re the S2 - There seems to be various "ideas" on how to solve this. Including SLAMTec's very own "Unplug it and plug it back in again nonsense.

This sensor has never worked. Latest drivers, good PSUs and UBS cables.

@Slamtec - what gives?

Mark

@oguzhankose
Copy link

oguzhankose commented May 27, 2024

Hello Mark
i agree that unplugging and plugging it back in is not a way for solving a problem. But when we talk to slamtech about this problem, they couldn't give any other recommendation to us. So i think there is no solution for this problem for now. If you find a solution, please let me know.

@3bdul1ah
Copy link

I'm currently facing same issue with my RPLidar S2 on the Jetson Nano. The lidar works perfectly fine on my laptop, but when I use it with the Jetson Nano, I consistently get the following error:

Error: rplidar internal error detected. Please reboot the device to retry.

I've tried the following solutions:

  • Granted proper permissions (chmod for /dev/ttyUSB0)
  • Ensured proper wiring, including separate power supply
  • Rebooting the device and reconnecting multiple times
  • Running sudo apt update && sudo apt upgrade
  • Plugging and unplugging the device
    When I unplug and reconnect, it works for about 2 seconds and then fails with the same internal error.

This seems to be a common problem with the S2 lidar, as many users have reported similar issues. Has anyone managed to figure out the exact reason for this behavior or found a reliable solution?

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

3 participants