Re: [libdc] point grey chameleon
Capture and control API for IIDC compliant cameras
Brought to you by:
ddouxchamps,
gordp
From: Aryeh W. <ar...@cc...> - 2013-07-10 18:41:58
|
On 7/10/13 8:36 PM, Rodolphe Pineau wrote: > > On Wed 7/10/13, at 10:04, Aryeh Weiss <ar...@cc...> wrote: >> >> From lsusb -v : >> idVendor 0x1e10 Point Grey Research, Inc. >> idProduct 0x2005 >> > > These are the right one so no funky firmware that would have messed up the VID/PID. > >> There is a bunch of other output from lsusb -v. >> >> I will try running with DC1394_DEBUG=1 when I am next in that lab. >> Meanwhile, I received the following output to stderr when i tried to run >> Coriander: >> libdc1394 warning: usb: Failed to open device for config ROM >> libdc1394 warning: Failed to get config ROM from usb device >> >> I tried running as root to see if there was a privileges problem. >> >> --aryeh > > > This error looks like the device is already in use by something else and when the library call libusb_open it gets an error. > So you have other video related application running at the same time ? Does it do the same thing if you run your code as root (directly as root or via sudo) ? > > Rodolphe > Thank you again for your replies. I decided to set it up on my home Suse system to see what happens. Indeed, it runs when I do it as root (so I must have done something else wrong the last time I tried). There is no other video device, but that error which I reported last time will occur when I am not root. However, there is a different problem. Coriander finds the camera , but cannot control it. Here is the debug output: (coriander:8581): GConf-WARNING **: Client failed to connect to the D-BUS daemon: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. ...many times libdc1394 debug: Initializing platform 0: linux libdc1394 debug: linux: Failed to open RAW1394DEV or /dev/raw1394 libdc1394 debug: Failed to initialize platform 0 libdc1394 debug: Initializing platform 1: juju libdc1394 debug: Juju: Found /dev/fw0 libdc1394 debug: Initialized platform 1 libdc1394 debug: Initializing platform 2: usb libdc1394 debug: Initialized platform 2 libdc1394 debug: Enumerating cameras... libdc1394 debug: Enumerating platform juju libdc1394 debug: Juju: Opened /dev/fw0 successfully libdc1394 debug: Platform juju has 1 device(s) libdc1394 debug: Got 256 quads of config ROM libdc1394 debug: Enumerating platform usb libdc1394 debug: usb: Found vendor:prod 1e10:2005 at address 2:4 libdc1394 debug: Platform usb has 1 device(s) libdc1394 debug: Got 37 quads of config ROM libdc1394 debug: Adding camera b09d0100c7f03f:0 b09d:1 (Point Grey Research:Chameleon CMLN-13S2M) (coriander:8581): GConf-WARNING **: Client failed to connect to the D-BUS daemon: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. ...many times. --aryeb -- Aryeh Weiss Faculty of Engineering Bar Ilan University Ramat Gan 52900 Israel Ph: 972-3-5317638 FAX: 972-3-7384051 |