Revision history [back]

After much poking and prodding, I was able to get camera_drivers, image_pipeline, vision_opencv, et. al to compile. I haven't tested whether or not they function correctly, but I wanted to let everyone know. Here's what I did:

export ROS_OS_OVERRIDE=ubuntu:11.04

This fixes the issue with rosdep being unable to detect os. I then found a base ROS installation that contained all of the stacks I needed, the perception install, available here:

http://packages.ros.org/cgi-bin/gen_rosinstall.py?rosdistro=diamondback&variant=perception&overlay=no

I edited out some packages I didn't need, but you can just as easily keep them all. I then used rosinstall to download everything:

rosinstall ~/ros "http://packages.ros.org/cgi-bin/gen_rosinstall.py?rosdistro=diamondback&variant=perception&overlay=no"

Next, I compiled ros:

rosmake -i ros

Then, I compiled the camera_drivers package and others:

rosmake --rosdep-install camera1394 camera_calibration image_proc

Which, after many hours, compiled successfully.

At this point, I need to test getting the camera up and running. For now, I'm going to bed, I'll update tomorrow (assuming everything works).

I don't know if this belongs as an additional update to the question or not. I'd like Eric to get the karma for answering, because his was incredibly helpful, so I'll likely mark his as correct and move this into the question. Let me know if you disagree with this course of action. For now, bedtime.

export ROS_OS_OVERRIDE=ubuntu:11.04

This fixes the issue with rosdep being unable to detect os. I then found a base ROS installation that contained all of the stacks I needed, the perception install, available here:

http://packages.ros.org/cgi-bin/gen_rosinstall.py?rosdistro=diamondback&variant=perception&overlay=no

I edited out some packages I didn't need, but you can just as easily keep them all. I then used rosinstall to download everything:

rosinstall ~/ros "http://packages.ros.org/cgi-bin/gen_rosinstall.py?rosdistro=diamondback&variant=perception&overlay=no"

Next, I compiled ros:

rosmake -i ros

Then, I compiled the camera_drivers package and others:

rosmake --rosdep-install camera1394 camera_calibration image_proc

Which, after many hours, compiled successfully.

At this point, I need to test getting

Update:

I now have the camera up and ~~running. For now,~~ running, publishing to a number of image topics quite happily. After getting the various bits of code required compiled, it was fairly straightforward.

In essence, you have to create a udev rule. With your favorite text editor, create a file in:

/etc/udev/rules.d/10-descriptivename.rules

Add the following:

# udev rules file for CAMERA_NAME_HERE BUS=="usb", SYSFS{idVendor}=="XXXX", SYSFS{idProduct}=="YYYY", GROUP="admin"

Where CAMERA_NAME_HERE is the name for your camera (mine was Point Grey FireflyMV), XXXX is your Vendor ID, and YYYY is your Product ID. Both Vendor and Product IDs can be found using

lsusb

With your camera plugged in.

One thing to note is that the group I'm ~~going to bed, I'll update tomorrow (assuming everything works).~~

I don't know if using here is admin instead of plugdev. Normally for security reasons, you would use plugdev, but on this belongs as an additional update to the question or not. I'd like Eric to get the karma for answering, because his was incredibly helpful, so I'll likely mark his as correct and move this into the question. Let me know particular Linaro build, there is no plugdev group, and setting it up is somewhat of a chore. Admin works just fine, if you ~~disagree with this course of action. For now, bedtime.~~
don't mind the small security threat it poses.

After that, you can just rosrun your camera driver, and you're off to the races. I did find that the publishing rate for the image was about half that of the frame rate of the camera. I'm looking in to why the camera1394 node is running so slowly.

Thanks for all the help!

-Bradley Powers