6: Troubleshooting - Grantham00/rplidar_detection GitHub Wiki
Starting the robopeak/rplidar_ros node
Can not start scan: 80008000!
This is a general error in launching the node. I have found that it tends to be due to power limitation on the rplidar. While the rplidar is capable of being powered by solely the microUSB connection, it requires a fair amount of current in order to start. This is why the rplidar is supplied with an additional USB to barrel jack cable. If you're trying to power the rplidar with only the microUSB cable, your PC may not be supplying enough current. Try a different USB port, or through a powered USB Hub. Try restarting the computer.
Error, cannot bind to the specified serial port
This happens if either the device is not found or the correct permissions are not set. First, see if the device ttyUSB exists. ttyUSB is a USB serial device, similar to a COM port on Windows. Hardware devices on Linux are found in the /dev directory. Use the command
ls /dev | grep ttyUSB
ls lists every file in the specified directory. The | Pipe sends the output of one command into the input of the next. grep searches the input for the given string. So, this command searches the /dev directory for any filenames containing the string "ttyUSB". The output should be
If nothing at all is listed, the hardware is not detected. If only ttyUSB1 is detected, the device may be on the wrong port. This happens when the device is unplugged and plugged into a different port. This may also happen if you have more than one USB serial device installed. Try replugging the device or rebooting to get it on ttyUSB0. Alternatively, the robopeak/rplidar_ros driver can be pointed to a different ttyUSB port number by modifying the .launch file under ~/catkin_ws/src/rplidar_ros/launch and rebuilding by running catkin_make from ~/catkin_ws.
If ttyUSB0 is the only device listed from the ls command above, there may be a permissions issue. Try
sudo chmod 666 /dev/ttyUSB0