Received: from nospam2.slac.stanford.edu (134.79.18.82) by
 exch-hub1.win.slac.stanford.edu (134.79.164.111) with Microsoft SMTP Server
 (TLS) id 8.1.436.0; Wed, 4 Aug 2010 08:33:21 -0700
Received: from qmta09.emeryville.ca.mail.comcast.net
 (qmta09.emeryville.ca.mail.comcast.net [76.96.30.96])	by
 nospam2.slac.stanford.edu (8.14.4/8.14.4) with ESMTP id o74FXKo2016130	for
 <alison@slac.stanford.edu>; Wed, 4 Aug 2010 08:33:20 -0700	(envelope-from
 murad.karmali@cookecorp.com)
Received: from omta05.emeryville.ca.mail.comcast.net ([76.96.30.43])	by
 qmta09.emeryville.ca.mail.comcast.net with comcast	id qDto1e00A0vp7WLA9FZLSn;
 Wed, 04 Aug 2010 15:33:20 +0000
Received: from muradk ([63.227.218.204])	by
 omta05.emeryville.ca.mail.comcast.net with comcast	id qFZB1e00B4RBZe78RFZD5j;
 Wed, 04 Aug 2010 15:33:18 +0000
From: Murad Karmali <murad.karmali@cookecorp.com>
To: "Chaiken, Alison" <alison@slac.stanford.edu>
Date: Wed, 4 Aug 2010 08:33:11 -0700
Subject: RE: questions about pco.edge-compatible framegrabber
Thread-Topic: questions about pco.edge-compatible framegrabber
Thread-Index: AcszNEig3yM4/jjSSDed1wL7ntITngAtUVsA
Message-ID: <00f001cb33ea$5cf58830$16e09890$@karmali@cookecorp.com>
References: <4C5856BF.5040001@slac.stanford.edu>
In-Reply-To: <4C5856BF.5040001@slac.stanford.edu>
Reply-To: "murad.karmali@cookecorp.com" <murad.karmali@cookecorp.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Exchange-Organization-AuthAs: Anonymous
X-MS-Exchange-Organization-AuthSource: exch-hub1.win.slac.stanford.edu
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-pmx-version: 5.5.9.395186, Antispam-Engine: 2.7.2.376379, Antispam-Data:
 2010.8.4.152114
x-pmx-spam: Gauge=IIIIIIII, Probability=8%, Report='
 BODYTEXTP_SIZE_3000_LESS 0, BODY_SIZE_2000_2999 0, BODY_SIZE_5000_LESS 0,
 BODY_SIZE_7000_LESS 0, DATE_TZ_NA 0, ECARD_WORD 0, FORGED_MUA_OUTLOOK 0,
 __BOUNCE_CHALLENGE_SUBJ 0, __BOUNCE_NDR_SUBJ_EXEMPT 0, __C230066_P5 0,
 __CP_URI_IN_BODY 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0,
 __HAS_X_MAILER 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __OEM_PHRASE 0,
 __OUTLOOK_MUA 0, __OUTLOOK_MUA_1 0, __SANE_MSGID 0, __TO_MALFORMED_2 0,
 __URI_NO_WWW 0, __URI_NS , __USER_AGENT_MS_GENERIC 0'
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Hello Alison:

Regarding the camera link card, we will be including a camera link card
(which is an OEM version of the microEnable IV) with the camera and also th=
e
cables will be included so you may not need to purchase another one.  The
reason for an OEM version of the board for us is that we have to use specia=
l
firmware on the board to provide lossless compression in order to meet the
bandwidth limitation of the PCIe bus as you've indicated below.  So, this
will be included with the board we provide and you should be able to use th=
e
Linux driver they provide.  With the board we provide, you will be able to
realize full frame rate (in 12-bit mode) through the bus.

We will also have camera control commands that you can use to address the
camera in your application which will be communicated serially through the
camera link interface to the camera.

Hopefully this helps.

Regards,

Murad

-----Original Message-----
From: Alison Chaiken [mailto:alison@slac.stanford.edu]=20
Sent: Tuesday, August 03, 2010 10:50 AM
To: murad.karmali@cookecorp.com
Subject: questions about pco.edge-compatible framegrabber

Greetings Murad, I would like to order the CameraLink PCI card for the=20
pco.edge this week before I leave on vacation.    Two candidates would=20
seem to be the microEnable IV from Silicon Software and the PCIe-CPL64=20
from Adlink.        I take it power-over-CameraLink (PoCL) and 2xMDR-26=20
cables are what the pco.edge needs?   With the Silicon Software=20
microEnable IV AD4-CL we can get 760 MB/s with PCIe x 4 and a 256 MB=20
on-board buffer plus FPGA and a Linux driver.   With the Adlink=20
PCIe-CML64F we can get 680 MB/s with PCIe x4 and a 128 MB on-board=20
buffer plus FPGA but no Linux driver.    Is the microEnable IV AD4-CL=20
the product you'd recommend?  Presumably we'd need two microEnable IV=20
AD4-CL units to support one camera at maximum data rate (not that I=20
think we'd be operating full-frame at full data rate most of the=20
time).   Thanks for your support, and sorry once again to miss you next=20
week.

--=20
Alison Chaiken				alison@slac.stanford.edu
(650) 926-2755 [checked nearly never]	http://exerciseforthereader.org/
I've got stacks in my structs, I've got arrays in my queues,
I've got the segmentation-violation, core-dumped blues.
-- Rick Moen



