Experimental Physics and
Industrial Control System

Eric Norum <[email protected]> · Wed, 30 May 2012 08:23:32 -0700

On May 30, 2012, at 8:07 AM, Ernest L. Williams Jr. wrote:

>> 
> 
> Hi Mark,
> I apologize for the late response.
> Here at the LCLS we are indeed interested in this.
> 
> We rely on our pulseID or "beam flavor" for correlation on a pulse by pulse basis.
> This will be useful for any piece of data acquisition hardware which has an asyn driver.
> For example, if I wanted to use your ip330-asyn driver for beam synchronous acquisition (BSA)
> 
> I hope to encourage more asyn-based drivers here at LCLS but we do need the capability to grab the pulseID
> with the "TSE = -2" technique.  :)
> 
> At this time, there are 2 waveform digitizer VME boards that we have started to work on:
> (1) Struck SIS3350
> (2) Struck SIS3302
> Can we make these asyn drivers and still integrate with GTR?  Eric any comments?

I don't see how GTR and ASYN would go together very easily.    Also, I don't think that TSE=-2 is the right choice for this setup -- the digitizers don't supply the time stamp.  I think that you'd be better off setting the waveform record TSE=<the number of some event in your timing system event receiver associated with the pulse>.  The waveform record would then get its time stamp from the event receiver.  If other records associated with the pulse use the same TSE field then they and the waveform record will have exactly the same time stamp for each pulse.

> If the driver is indeed asyn, we like the proposal for getting the pulseID that you mention above. :)
> 
> I wonder how Jeff Hill (LANL) will correlate his data at LANSCE?
> 

-- 
Eric Norum
[email protected]

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System