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 |
Ok, problem solved! The issue was that my device needed a udev rule. I created one, and the camera works great now. Here was what I did:
First, I used lsusb with the camera plugged in to determine the USB Vendor and Product IDs for my camera:
bradpowers@bp-rosdev:~$ lsusb
Bus 002 Device 009: ID 1e10:2000 Point Grey Research, Inc.
Bus 002 Device 008: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse
Bus 002 Device 007: ID 05ac:0220 Apple, Inc. Aluminum Keyboard (ANSI)
Bus 002 Device 006: ID 05ac:1006 Apple, Inc. Hub in Aluminum Keyboard
Bus 002 Device 005: ID 05ac:921c Apple, Inc.
Bus 002 Device 004: ID 0cf3:3002 Atheros Communications, Inc.
Bus 002 Device 003: ID 05ac:911c Apple, Inc.
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
The device I'm concerned with is the Point Grey Research device at the top. I copied down the ID number, 1e10:2000.
From there, I needed to create a udev rule to add the device to the plugdev group when plugged in:
bradpowers@bp-rosdev:~$ sudo gedit /etc/udev/rules.d/10-pointgrey.rules
In this file, I entered the following:
# udev rules file for Point Grey Firefly-MV
BUS=="usb", SYSFS{idVendor}=="1e10", SYSFS{idProduct}=="2000", GROUP="plugdev"
After saving, and a reboot, launching my roslaunch file worked great. Thanks to Andy Barry for a phone call and solution so quickly.
| | 2 | No.2 Revision |
Ok, problem solved! The issue was that my device needed a udev rule. I created one, and the camera works great now. Here was what I did:
First, I used lsusb with the camera plugged in to determine the USB Vendor and Product IDs for my camera:
bradpowers@bp-rosdev:~$ lsusb
Bus 002 Device 009: ID 1e10:2000 Point Grey Research, Inc.
Bus 002 Device 008: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse
Bus 002 Device 007: ID 05ac:0220 Apple, Inc. Aluminum Keyboard (ANSI)
Bus 002 Device 006: ID 05ac:1006 Apple, Inc. Hub in Aluminum Keyboard
Bus 002 Device 005: ID 05ac:921c Apple, Inc.
Bus 002 Device 004: ID 0cf3:3002 Atheros Communications, Inc.
Bus 002 Device 003: ID 05ac:911c Apple, Inc.
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
The device I'm concerned with is the Point Grey Research device at the top. I copied down the ID number, 1e10:2000.
From there, I needed to create a udev rule to add the device to the plugdev group when plugged in:
bradpowers@bp-rosdev:~$ sudo gedit /etc/udev/rules.d/10-pointgrey.rules
In this file, I entered the following:
# udev rules file for Point Grey Firefly-MV
BUS=="usb", SYSFS{idVendor}=="1e10", SYSFS{idProduct}=="2000", GROUP="plugdev"
After saving, and a reboot, launching my roslaunch file worked great. Thanks to Andy Barry Barry for a phone call and solution so quickly.
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.