ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
1 | initial version |
You could check the permissions of ttyUSB0
ls -la /dev/
If the perms are not 666 or a+rw then you need to boot with usb that has permission to access. Basically you need to create a new rule in /etc/udev/rules.d:
Create a new file with your specific permissions (higher numbers override existing rules):
cd /etc/udev/rules.d/
touch 80-turtlebot.rules
sudo pico 80-turtlebot.rules
Add the following lines for every usb device:
#serial usb
SUBSYSTEM=="usb", ATTRS{idProduct}=="6001", ATTRS{idVendor}=="0403", MODE="0666", GROUP="turtlebot"
To find the product id and vendor id, do lsusb -v, I think if you just do regular lsusb its vendor:product. Shift + PgUp to view previous parts of the cli.
finally reboot
sudo reboot
2 | No.2 Revision |
You could check the permissions of ttyUSB0
ls -la /dev/
If the perms are not 666 or a+rw then you need to boot with usb that has permission to access. Basically you need to create a new rule in /etc/udev/rules.d:
Create a new file with your specific permissions (higher numbers override existing rules):
cd /etc/udev/rules.d/
touch 80-turtlebot.rules
sudo pico 80-turtlebot.rules
Add the following lines for every usb device:
#serial usb
SUBSYSTEM=="usb", ATTRS{idProduct}=="6001", ATTRS{idVendor}=="0403", MODE="0666", GROUP="turtlebot"
To find the product id and vendor id, do do:
lsusb -v, -v
I think if you just do regular lsusb its vendor:product. Shift + PgUp to view previous parts of the cli.
finally reboot
sudo reboot