Slamtec / rplidar_sdk

Open source SDK for Slamtec RPLIDAR series products
BSD 2-Clause "Simplified" License
425 stars 253 forks source link

Error, cannot bind to the specified serial port /dev/ttyUSB0 #45

Open VbsmRobotic opened 3 years ago

VbsmRobotic commented 3 years ago

Hi, I am using ubuntu 18.04. I have already root privilege to access tty device as below : $ cd /etc/udev/rules.d/ \ $ sudo touch 50-usb-serial.rules \ $ sudo gedit 50-usb-serial.rules \ In the file that is opened by the GEdit, wrote these words: KERNEL=="ttyUSB0", GROUP="vahid", MODE="0666" Also run $ sudo chmod 0666 /dev/ttyUSB0

When I run ultra_simple, face issue as follow : ~/rplidar_sdk/sdk/output/Linux/Release$ sudo ./ultra_simple /dev/ttyUSB0 115200

Ultra simple LIDAR data grabber for RPLIDAR. Version: 1.12.0 Error, cannot bind to the specified serial port /dev/ttyUSB0.

Anyone has face this issue. Please advise

pirate999 commented 3 years ago

I have the same issue, have you solved ?

VbsmRobotic commented 3 years ago

Please change buad rate to 256000. It should work.

PauloSilva98 commented 3 years ago

Did you manage to solve this issue? Same thing is happening to me...

VbsmRobotic commented 3 years ago

Did you manage to solve this issue? Same thing is happening to me...

Have changed buad rate to 256000 ?

PauloSilva98 commented 3 years ago

Yes I have, both in the RP Lidar itself and the when running it

VbsmRobotic commented 3 years ago

Yes I have, both in the RP Lidar itself and the when running it

How about ttyUSB permission ?

PauloSilva98 commented 3 years ago

Yes I have, both in the RP Lidar itself and the when running it

How about ttyUSB permission ?

KERNEL=="ttyUSB0", GROUP="vahid", MODE="0666"

I have added this into a new rules file in the udev

VbsmRobotic commented 3 years ago

Yes I have, both in the RP Lidar itself and the when running it

How about ttyUSB permission ?

KERNEL=="ttyUSB0", GROUP="vahid", MODE="0666"

I have added this into a new rules file in the udev

Please remove GROUP= "vahid" after that from terminal run $ sudo chmod 666 /dev/ttyUSB0 based on your usb port select ttyUSB0 or ttyUSB1 ...

PauloSilva98 commented 3 years ago

Yes I have, both in the RP Lidar itself and the when running it

How about ttyUSB permission ?

KERNEL=="ttyUSB0", GROUP="vahid", MODE="0666" I have added this into a new rules file in the udev

Please remove GROUP= "vahid" after that from terminal run $ sudo chmod 666 /dev/ttyUSB0 based on your usb port select ttyUSB0 or ttyUSB1 ...

Tried it still doesn't work. This is what pops up with this command: $ ls -l /dev |grep ttyUSB crw-rw-rw- 1 root root 188, 0 dez 23 10:57 ttyUSB0

So i see that it is in ttyUSB0 (and it has never changed). I don't understand why i still don't have permission. Is this "crw-rw-rw" not enough?

J0ANMM commented 3 years ago

I had a similar issue and the following command solved it for me: sudo adduser $USER dialout I found this solution here.

KianRK commented 1 year ago

I have the same issue, but none of the proposed solutions worked for me. I am using ubuntu 20.04. I have tried it with all the different baud rates, with and without sudo or root. I checked the installation of the divers.

I added my user to dialout etc. I have a dual boot on the same laptop and with robostudio on windows it works but not on my ubuntu, but since I will use ubuntu to work with ros I need it to work on here.

Any suggestions beyond the previous ones?

kadenslater95 commented 11 months ago

Hello everyone, I ran into this problem and it was a pain trying everything they mentioned above. Finally I figured it out. First, you do need to get the permissions set up right so do follow at least one of those suggestions above. Now with that out of the way, what was causing the issue is that the default Baudrate, and the suggested above Baudrate of 265000 were incorrect for my particular device. I have the model A1M8. It turns out that if you just type ./ultra_simple on the latest version of the sdk from github it will print out the usage which includes a list of baud rates. I had to use the A1 baudrate of 115200 and voila, it works now.

For reference here is the list that spits out in the terminal A1(115200),A2M7(256000),A2M8(115200),A2M12(256000),A3(256000),S1(256000),S2(1000000),S3(1000000)

kadenslater95 commented 11 months ago

One final note, you should update the README with this little tricky configuration issue and mark this issue as closed

mattiadutto commented 6 months ago

In my case the problem was resolved by sudo chmod 0666 /dev/ttyUSB0 Thanks!