-
Notifications
You must be signed in to change notification settings - Fork 552
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
Comments
Hello Mark |
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:
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? |
How often did you get the problem? I've got the problem too |
I managed to solve the issue. I was using a Jetson Nano with Ubuntu 20.04, which isn’t natively supported as the Jetson Nano is optimized for Ubuntu 18.04. This mismatch likely caused some limitations, such as the USB port not supplying enough voltage to power the LiDAR, which could be why we kept seeing the error. After downgrading to Ubuntu 18.04 and testing it, everything surprisingly worked without any issues. This explains why it worked fine on both my laptop and the Jetson Orin running Ubuntu 20.04 but not on the Jetson Nano with the same version. The laptop and Orin are natively supported by Ubuntu 20.04, whereas the Jetson Nano has native support only for Ubuntu 18.04. Based on my experience, this seems to be a reasonable explanation. However, the error is quite general and could arise from different causes, making it difficult to pinpoint the exact issue. While it’s working fine on the Jetson Nano with Ubuntu 18.04, I did notice that the error could also stem from changes in the device path, like /dev/ttyUSB*, which keeps switching between 1 and 2. This doesn’t seem like an issue that can be permanently fixed by assigning it to a single port. So, even after downgrading (which worked for me), you might still encounter the error, but likely due to the port switching. In that case, it should get back to working fine once you adjust it. |
Seems to be like the device is still broken. 18.04 is very old. All the other SLAMTEC Lidars that I have A3 - work fine on 22 etc |
I found that by quickly inserting the microUSB cable and power cord within 2-3 seconds, it works. |
Unfortunately not a solution. The device cannot have manual intervention to make it "work" |
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
The text was updated successfully, but these errors were encountered: