The site is read-only. Please transition to use Robotics Stack Exchange
| ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
 | 1 | initial version |
The solution was based on this answer to a similar problem: Adding a u-dev rule for the device
touch /etc/udev/rules.d/orbbec-usb.rules
echo "SUBSYSTEM==\"usb\", ATTR{idProduct}==\"0401\", ATTR{idVendor}==\"2bc5\", MODE:=\"0666\", OWNER:=\"root\", GROUP:=\"video\"\nSUBSYSTEM==\"usb\", ATTR{idProduct}==\"0402\", ATTR{idVendor}==\"2bc5\", MODE:=\"0666\", OWNER:=\"root\", GROUP:=\"video\"\nSUBSYSTEM==\"usb\", ATTR{idProduct}==\"0403\", ATTR{idVendor}==\"2bc5\", MODE:=\"0666\", OWNER:=\"root\", GROUP:=\"video\"\nSUBSYSTEM==\"usb\", ATTR{idProduct}==\"0404\", ATTR{idVendor}==\"2bc5\", MODE:=\"0666\", OWNER:=\"root\", GROUP:=\"video\"\nSUBSYSTEM==\"usb\", ATTR{idProduct}==\"0405\", ATTR{idVendor}==\"2bc5\", MODE:=\"0666\", OWNER:=\"root\", GROUP:=\"video\" " >> /etc/udev/rules.d/orbbec-usb.rules
udevadm control --reload-rules
Unplugging and plugging the device again, and running the launch file, now works.
ROS Answers is licensed under Creative Commons Attribution 3.0 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.