Ask Your Question
0

How to get PointGrey camera acquiring image data in Python on Raspberry Pi?

asked 2019-11-08 15:34:54 -0500

Py_J gravatar image

Hi all,

I have 2 Point Grey cameras with code FL3-U3-88S2C-C on their labels. I've had these cameras for some time and have never been able to get them working. I was hoping to get some guidance as I have had no luck with the online support.

Basically, I would like to use these cameras as part of an OpenCV based Python program running on Raspbian or Ubuntu on a single board computer. Right now I'm using a Raspberry Pi 4.

Currently, I can see that my camera is recognised when running the lsusb command in terminal but I get the following error when using the OpenCV VideoCapture(1) function in Python.

[ WARN:0] global /home/pi/opencv/modules/videoio/src/cap_v4l.cpp (802) open VIDEOIO ERROR: V4L: can't open camera by index 1
libdc1394 warning: usb: Failed to open device for config ROM
libdc1394 warning: Failed to get config ROM from usb device

Is there anything you could suggest to help me start acquiring image data?

Thanks!

edit retag flag offensive close merge delete

2 answers

Sort by » oldest newest most voted
0

answered 2019-11-10 04:08:33 -0500

kbarni gravatar image

Did you manage to make the camera work with another program? (to see if you have all the necessary rights to access it) Point Grey has ARMHF SDK that should work on the Raspberry Pi, with some testing code.

Anyway, I never used industrial cameras with the OpenCV API; I prefer to use the official SDK which is more stable and offers complete control. I think it's a pity to use high-end cameras with a limited control. After, you can easily create an OpenCV Mat from the captured buffer.

edit flag offensive delete link more
0

answered 2019-11-08 20:53:47 -0500

supra56 gravatar image

updated 2019-11-09 05:48:44 -0500

Try this:

sudo gedit /etc/udev/rules.d/10-pointgrey.rules

And enter this:

# udev rules file for Point Grey Firefly-MV
BUS=="usb", SYSFS{idVendor}=="1e10", SYSFS{idProduct}=="3300", GROUP="plugdev"

Save it and reboot it. Update: I change 2000 to 3300.

edit flag offensive delete link more

Comments

Thanks for the suggestion. I gave it a try and it seemed to have no effect. I wondered if I just need to tune the parameters to suit my system but I was unsure how to find them.

Here’s what I get when I run the lsusb command:

Bus 002 Device 002: ID 1e10:3300 Point Grey Research, Inc.

Do you think I need to take some info from this and put it in the .rules file?

Py_J gravatar imagePy_J ( 2019-11-09 04:03:55 -0500 )edit

See my answer as above. I changed to 3300.

supra56 gravatar imagesupra56 ( 2019-11-09 04:42:08 -0500 )edit

Just tried and had no luck. I've just noticed that when I run VideoCapture(0) or VideoCapture(1) I get this error:

[ WARN:0] global /home/pi/opencv/modules/videoio/src/cap_v4l.cpp (802) open VIDEOIO ERROR: V4L: can't open camera by index 1
libdc1394 warning: usb: Failed to open device for config ROM
libdc1394 warning: Failed to get config ROM from usb device

However, when I run VideoCapture(-1), I get this error. Don't suppose that tells you anything?

VIDEOIO ERROR: V4L: can't find camera device
libdc1394 warning: usb: Failed to open device for config ROM
libdc1394 warning: Failed to get config ROM from usb device
Py_J gravatar imagePy_J ( 2019-11-09 06:27:29 -0500 )edit

Didn't you install libdc1394-22-dev?

supra56 gravatar imagesupra56 ( 2019-11-09 06:57:19 -0500 )edit

Yes that's installed:

libdc1394-22-dev is already the newest version (2.2.5-1).
Py_J gravatar imagePy_J ( 2019-11-09 09:26:54 -0500 )edit

Did you plugged usb3 on middle side (colour blue) of RPI 4?

supra56 gravatar imagesupra56 ( 2019-11-09 10:36:34 -0500 )edit

You may have to order pdf from packit; OpenCV 3 Blueprints

I maybe off for weekend.

supra56 gravatar imagesupra56 ( 2019-11-09 10:41:39 -0500 )edit
Login/Signup to Answer

Question Tools

1 follower

Stats

Asked: 2019-11-08 15:34:54 -0500

Seen: 56 times

Last updated: Nov 10