RpLidar s2 Error, rplidar internal error detected. Please reboot the device to retry.

[vivekmange56]

Hello

I am using the new Rplidar s2 on jetson nx, I frequently face this below issue, what should i do to overcome this

roslaunch rplidar_ros rplidar_s2.launch
... logging to /home/nvidia/.ros/log/e8398694-dc20-11ec-a98c-00181af28bd5/roslaunch-tegra-ubuntu-19279.log
Checking log directory for disk usage. This may take a while.
Press Ctrl-C to interrupt
Done checking log file disk usage. Usage is <1GB.

started roslaunch server http://192.168.1.104:36973/

SUMMARY

PARAMETERS

• /rosdistro: melodic
• /rosversion: 1.14.13
• /rplidarNode/angle_compensate: True
• /rplidarNode/frame_id: laser
• /rplidarNode/inverted: False
• /rplidarNode/serial_baudrate: 1000000
• /rplidarNode/serial_port: /dev/rplidar

NODES
/
rplidarNode (rplidar_ros/rplidarNode)

auto-starting new master
process[master]: started with pid [19345]
ROS_MASTER_URI=http://192.168.1.104:11311

setting /run_id to e8398694-dc20-11ec-a98c-00181af28bd5
process[rosout-1]: started with pid [19374]
started core service [/rosout]
process[rplidarNode-2]: started with pid [19382]
[ INFO] [1653479445.408398218]: RPLIDAR running on ROS package rplidar_ros, SDK Version:2.0.0
[ INFO] [1653479445.464188214]: RPLIDAR S/N: 5AACECF8C4E699D5B8EB99F9D6734715
[ INFO] [1653479445.464808939]: Firmware Ver: 1.01
[ INFO] [1653479445.464974537]: Hardware Rev: 18
[ERROR] [1653479445.517251953]: Error, rplidar internal error detected. Please reboot the device to retry.
[rplidarNode-2] process has died [pid 19382, exit code 255, cmd /home/nvidia/aurus_ws/install/rplidar_ros/lib/rplidar_ros/rplidarNode __name:=rplidarNode __log:=/home/nvidia/.ros/log/e8398694-dc20-11ec-a98c-00181af28bd5/rplidarNode-2.log].
log file: /home/nvidia/.ros/log/e8398694-dc20-11ec-a98c-00181af28bd5/rplidarNode-2*.log
^C[rosout-1] killing on exit
[master] killing on exit
shutting down processing monitor...
... shutting down processing monitor complete
done

[Sudharsan10]

I'm facing the same error and only difference is that I used a raspberry Pi 4B

[jcrupi]

Any resolutions?

[vivekmange56]

The system worked for me. I connected the same device with different s2 adapter and cabel and it worked. After that i used the same old wires and cables and it worked fine. I haven't faced issue after that.

…

On Fri, Jul 15, 2022, 4:26 AM John Crupi ***@***.***> wrote: Any resolutions? — Reply to this email directly, view it on GitHub <#87 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AKD3SZ73OTHTTUT6XKEXSUDVUCLIHANCNFSM5W43VMQQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[astumpf]

I'm experiencing the same error message with 2 brand-new devices. Cannot get them to work at all using a regular PC. I appreciate any ideas how to solve this issue.

[vivekmange56]

Hey I bought a new Lidar and fortunately, both the S2 lidar worked after connecting the old lidar with the new cable. I also tried multiple configurations with cables, adapters and lidar and all the configurations worked. So I am not sure what was the reason but now both Lidars are working fine.

…

On Mon, 22 Aug 2022 at 14:45, Alexander Stumpf ***@***.***> wrote: I'm experiencing the same error message with 2 brand-new devices. Cannot get them to work at all. I appreciate any ideas how to solve this issue. — Reply to this email directly, view it on GitHub <#87 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AKD3SZ3NOHAKIAQPO3WJQU3V2NAJ7ANCNFSM5W43VMQQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[CycleMark]

Has this been solved at all. I get this issue on any board I try. My A3 and A1 SLAMTec sensors work just fine. I can't be having a sensor which may or may not work on a whim (well tbf it mostly doesn't work)

Thanks

Mark

[j953302]

Hello, I use S2 and face the same problem randomly. Sometimes it work fine but sometimes it doesn't. I have give it independent 5V power but it doesn't figure it out. Is there any other advice? Thank.

[SyJarvis]

Try providing additional power supply

[CycleMark]

Unfortunately external PSU makes no difference. Having to remove and reboot the sensor makes is somewhat useless

[SyJarvis]

21软件7班-你的邮箱已收到

[3bdul1ah]

I'm currently facing an 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?

[SyJarvis]

24计科(专升本)2班-你的邮箱已收到

[CycleMark]

@3bdul1ah - sadly not. My sensor has spent 2 years in a box. Not heard anything from SLAMTEC. Like you I've tried everything

[SyJarvis]

24计科(专升本)2班-你的邮箱已收到

[3bdul1ah]

@3bdul1ah - sadly not. My sensor has spent 2 years in a box. Not heard anything from SLAMTEC. Like you I've tried everything

@CycleMark - 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.