IIDC Camera Control Library

Hello,

I just wondered if anyone could recommend a low profile firewire PCI card for (ubuntu oneiric) linux and/or windows. The main purpose is to drive some 400/800 Point Grey cameras with libdc1394. I have only had experience with built in firewire on mac so far and my understanding is that for PCs not all firewire cards are created equal. Furthermore a bit of searching suggests that low profile cards are quite rare. 

With many thanks for any suggestions,

Greg.

PS To be more specific the PC is a small form factor Optiplex 760 with a regular PCI and a PCI express x16 (currently housing the graphics card) – nothing special but space is tight and we have a few of them kicking around.

--
Gregory Jefferis, PhD                      
Division of Neurobiology                   
MRC Laboratory of Molecular Biology,       
Hills Road,                                
Cambridge, CB2 0QH, UK.                    

http://www2.mrc-lmb.cam.ac.uk/group-leaders/h-to-m/g-jefferis
http://www.neuroscience.cam.ac.uk/directory/profile.php?gsxej2
http://flybrain.stanford.edu

Hi Damien, hi everyone...

I'm currently trying to get my Point Grey FireflyMV FFMV-03M2M to work on a Mac Book Pro running OSX 10.6 in combination with reactiVISion.
I was able to configure and build reactivision using XCode. 
After that, when I run the application, I get the following message:


> Last login: Tue Feb 28 17:19:55 on ttys000
> /Users/jh/_UNI/D/software/reactivision/reacTIVision-1.4-src/macosx/build/Development/reacTIVision.app/Contents/MacOS/reacTIVision ; exit;
> greyhound:~ jh$ /Users/jh/_UNI/D/software/reactivision/reacTIVision-1.4-src/macosx/build/Development/reacTIVision.app/Contents/MacOS/reacTIVision ; exit;
> reacTIVision 1.4 (Feb 28 2012)
> libdc1394 error: Format_7 Error_flag_1 is set: in _dc1394_v130_handshake (format7.c, line 122): invalid image position, size, color coding or ISO speed
> 
> libdc1394 error: Format_7 Error_flag_1 is set: in dc1394_format7_set_roi (format7.c, line 803): Handshaking failed after setting color_coding
> 
> camera: Point Grey Research, Firefly MV FFMV-03M2M
> format: 752x480
> 
> display:
>    n - no image
>    s - source image
>    t - target image
>    h - toggle help text
> 
> commands:
>    ESC - quit reacTIVision
>    v - verbose output
>    o - camera options
>    p - pause processing
> debug options:
>    b - save buffer as PGM
>    m - save buffer sequence
> 
> FrameEqualizer:
>    e - toggle frame equalizer
>    SPACE - activate frame equalizer
> 
> FrameThresholder:
>    g - adjust gradient gate
> 
> FiducialFinder:
>    i - invert x-axis, y-axis or angle
> FidtrackFinder:
>    f - adjust finger size & sensitivity
> 
> CalibrationEngine:
>    c - toggle calibration mode
>    j - reset calibration grid
>    k - reset selected point
>    l - revert to saved grid
>    r - show calibration result
>    a,d,w,x - move within grid
>    cursor keys - adjust grid point


Can you (or someone) provide any help and point out what the errors are about and on how to avoid them in order to get reactivision to work with the firefly cam?
(at the moment i get a scrambled image, the size sometimes is correct and true to the aspect ratio of the cam, but sometimes it isn't)

Thanks for your help

joachim

Hi all,

The windows code is now working fine so I have merged the windows branch
in the git repo. If there's no outstanding problems we can make a new
release, I guess 2.2.0 would be a good number given the big addition.

Would it also be a good time to add support for 32 F7 video modes?
(see commits of 2009-4-12 and 2009-6-11) This breaks the API but AFAICT
we would keep backward compatibility.

Damien


On Thu, 2012-01-26 at 15:38 +0900, Damien Douxchamps wrote:
> Hi all,
> 
> The list has been a bit quiet lately, so let's stir things up with a big
> news: there's a new Windows stack! To keep a long story short, my
> company needed it so we put a few bucks on the table and Satofumi-san
> did the job. All thanks to him ( ^^)v
> 
> As we had limited time and ressources, we decided to use the CMU 1394
> camera library as a base. The CMU software is LPGL, stable and goes
> around numerous quirks of the Windows platform (32/64bit versions, API
> differences, etc). Also, one can link the library binaries easily,
> without code duplication.
> 
> At this point most things should work, although it's hard to actually
> test everything. If you have a windows computer lying around, please
> give it a try!
> 
> Known limitations:
> - lack of valid time stamps in the dc1394video_frame_t structure. The
> CMU team has problems getting this information from the Windows kernel,
> so the buffer fill time cannot reach us.
> - compilation is only for MinGW/Msys at this time. Let us know if you
> can make libdc1394 compile on MS products (VC?)
> - untested: multi-camera/multi-card capture, hubs, hotplug (is this
> supposed to work anyway?), weird topologies (loops), multi-unit devices
> 
> The source code is located in a new "windows" branch of the GIT
> repository. Temporarily, a tarball is also available on the SF website
> (libdc1394-2.1.4-win.tar.gz) Installation instructions are in the
> dc1394/windows/INSTALL.txt file.
> 
> Have fun!
> 
> Cheers,
> 
> Damien
> 

-- 
Damien Douxchamps
Cyberdyne Inc, Japan