Experimental Physics and
Industrial Control System

"Russ Berg" <[email protected]> · Thu, 5 Apr 2007 10:39:15 -0600

Hi John, 
We are currently using the Flea's and Flea2 on our IOC's (Scientific
Linux w/ 2.6.9 kernel), the SLS software required a few "site"
reconfigurations but essentially it compiled and ran out of the box.
Previously we had been running RH 7.2 with 2.4.7 kernel which required
a kernel upgrade to 2.4.27 (as well as the 1394 libs/modules) in order
to add the 1394 support to talk to firewire camera's , but we have since
standardized to 2.6.9. If possible you should move to 2.6.9 and save the
headaches.

Our current 1394 configuration:
Epics ver: 3.14.6
Linux (2.6.9): Scientific Linux https://www.scientificlinux.org/
SLS SW:  ccd1394-1.2.tar.gz
1394 card: Not sure exactly, we have a variety but I believe they are
all generic OHCI compliant.
1394 Cameras used: Sony DFW-SX-900, Flea, Flea2

-Russ
~~~~~~~~~~~~~~~~~~~~~~~~~~
Russ Berg
Control Systems
Canadian Light Source Inc.
www.lightsource.ca
Ph: 306.657.3572
~~~~~~~~~~~~~~~~~~~~~~~~~~

-----Original Message-----
From: John Dobbins [mailto:[email protected]] 
Sent: Wednesday, April 04, 2007 2:47 PM
To: EPICS Tech-Talk
Subject: Point Grey Flea2

Dear All,

I am trying to reproduce the SLS Firewire Camera video server described
here:

http://epics.web.psi.ch/software/firewire/

which was originally based on the Point Grey Flea camera model. I ended
up purchasing a Flea2 model. I haven't been able to get the Flea2 to
work on Linux (details below). I am wondering if other folks are using
the Flea2 on Linux and if so with what configuration?

Thanks and regards,

John Dobbins
Lab for Elementary Particle Physics
Cornell University

Details:

We have been able to get the Flea2 to work on Windows with the Carnegie
Melon DCAM driver for windows (http://www.cs.cmu.edu/~iwan/1394/)
however the Flea2 doesn't seem to be recognized on our Linux box.

We are not able to detect our Flea2 when it's connected to an Adaptec
FireConnect 8300 card on a computer running Redhat Enterprise Linux 3,
kernel 2.4.21.

Here is what we see in syslog when connecting the camera:
------
ohci1394: $Rev: 896 $ Ben Collins <[email protected]>
ohci1394_0: OHCI-1394 1.1 (PCI): IRQ=[20]  MMIO=[d0014000-d00147ff]  Max
Packet=[4096]
raw1394: /dev/raw1394 device initialized
ieee1394: ConfigROM quadlet transaction error for node 00:1023
ieee1394: Host added: Node[01:1023]  GUID[080028640000212c]  [Linux
OHCI-1394]
video1394: Installed video1394 module
------

And here is the output of testlibraw:
------
successfully got handle
current generation number: 1
1 card(s) found
   nodes on bus:  2, card name: ohci1394 using first card found: 2 nodes
on bus, local ID is 1, IRM is 1

doing transactions with custom tag handler trying to send read request
to node 0... failed with error: Resource temporarily unavailable trying
to send read request to node 1... completed with value 0x51e49ac1

using standard tag handler and synchronous calls trying to read from
node 0... failed with error: Resource temporarily unavailable trying to
read from node 1... completed with value 0xbbf39ac1

testing FCP monitoring on local node
got fcp command from node 1 of 8 bytes: 01 23 45 67 89 ab cd ef got fcp
response from node 1 of 8 bytes: 01 23 45 67 89 ab cd ef

polling for leftover messages
------

Accordingly, both dc1394_vloopback and coriander are unable to see the
camera.

We have two other types of firewire cameras that are working properly on
this system.

We see the same behavior when using libdc1394-2.0 (and coriander-2.0) or
libdc1394-1.2.1 (and coriander-1.0.1).

Any suggestions or help would be greatly appreciated. Point Grey does
not support Linux for this model.

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System