Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  <20122013  2014  2015  2016  2017  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  <20122013  2014  2015  2016  2017 
<== Date ==> <== Thread ==>

Subject: Re: Proposed change in asyn - request for comments
From: Eric Norum <eric@norum.ca>
To: "Ernest L. Williams Jr." <ernesto@slac.stanford.edu>
Cc: EPICS Techtalk <tech-talk@aps.anl.gov>
Date: 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
eric@norum.ca






Replies:
Re: Proposed change in asyn - request for comments Michael Davidsaver
RE: Proposed change in asyn - request for comments Mark Rivers
References:
Proposed change in asyn - request for comments Mark Rivers
Re: Proposed change in asyn - request for comments Ernest L. Williams Jr.

Navigate by Date:
Prev: Re: Proposed change in asyn - request for comments Ernest L. Williams Jr.
Next: Re: calc VAL field not updating from bi VAL field J. Lewis Muir
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  <20122013  2014  2015  2016  2017 
Navigate by Thread:
Prev: Re: Proposed change in asyn - request for comments Ernest L. Williams Jr.
Next: Re: Proposed change in asyn - request for comments Michael Davidsaver
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  <20122013  2014  2015  2016  2017 
ANJ, 18 Nov 2013 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·