Received: from [134.79.72.91] (134.79.72.91) by email.slac.stanford.edu (134.79.106.208) with Microsoft SMTP Server (TLS) id 8.1.436.0; Thu, 30 Sep 2010 16:25:12 -0700 From: "Hill, Bruce" To: "Chaiken, Alison" Date: Thu, 30 Sep 2010 16:25:12 -0700 Subject: Re: PCDS "event" module and BSA hardware Thread-Topic: PCDS "event" module and BSA hardware Thread-Index: Actg9rtWemAcWDmqRPm20iTFgQUKXg== Message-ID: <4CA51C58.70104@slac.stanford.edu> References: <4CA3C6F4.7020306@slac.stanford.edu> In-Reply-To: <4CA3C6F4.7020306@slac.stanford.edu> Accept-Language: en-US Content-Language: en-US X-MS-Exchange-Organization-AuthAs: Internal X-MS-Exchange-Organization-AuthMechanism: 0a X-MS-Exchange-Organization-AuthSource: EXCH-CLIENT1.win.slac.stanford.edu X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Thunderbird 2.0.0.24 (X11/20100903) Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Hi Alison, I'm not clear on what you're asking. Have you used the eBeam version=20 of the event module with MRF EVR's? If so, there's not really anything different=20 about our event module other than running on a linux box. We're using PMC EVR230 modules, so we use a Technobox PCIe carrier card to mount them in the PCIe slots on our linux boxes. They get a fiber from our MRF timing=20 fanout board and the event module gets the fiducial from the EVR hardware and uses it=20 to set the EPICS timestamp. When our camera module timestamps it's image, it get= s the current EPICS timestamp. Since the shutter duration is much=20 longer than a fiducial interval, the fiducial in the timestamp is not the same as=20 the fiducial when the camera was triggered, but that has not been an issue for us as these=20 camera images are used for viewing and don't go into data aquisition. - Bruce Alison Chaiken wrote: > Bruce, thanks again for the source code and advice you provided me with=20 > before. I'm starting to think about what EVR hardware I might need= =20 > for BSA correlation of camera images with other data in FACET. It's my= =20 > understanding from your previous message that the "event" module that=20 > you pointed me to provides this correlation. Can you please point me=20 > to any diagram or documentation that explains how the hardware portion=20 > of the system (the signal propagation) is hooked up? Thanks for your=20 > assistance. > > =20 --=20 Bruce Hill Member Technical Staff SLAC National Accelerator Lab 2575 Sand Hill Road M/S 10 Menlo Park, CA 94025