Subject: |
Re: APS Event Hardware |
From: |
[email protected] (Bob Dalesio) |
Date: |
Wed, 24 Aug 94 08:30:13 MDT |
The software latency will be the sum of the interrupt latency (was 3us on a 68020) a context switch (was 30 usec on a 68020) and record processing (about
80 usec each on the 68040). Minimum latency is acheived by running the record from this on an event scan list at high priority. This is the highest priority
in the system. Only several vxWorks tasks run higher. The most devious one
being the shell task. If someone is logged in and invoking diagnostic routines,
then all bets are off.
The LANL timing hardware would also handle this problem. It has a 5 Mhz clock
and ~500 nansecond jitter. It is a much simpler design that the ANL timing as
it only has three types of events: no sequence RAM, no programmed events.
This proved adequate for our LINAC which was pulsed at 10 Hz. These boards
are relatively inexpensive, but not appropriate if you want to be generating
events at greater than 100 Hz. The limitation is in the software, not the
clock generator.
Bob
- Navigate by Date:
- Prev:
RE: a friend in need Gabor Csuka, DESY - Germany
- Next:
RE: APS Event Hardware Frank Lenkszus
- Index:
<1994>
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
Re: APS Event Hardware watson
- Next:
RE: APS Event Hardware Frank Lenkszus
- Index:
<1994>
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
|