Subject: |
Re: camac crate initialization |
From: |
[email protected] |
Date: |
Mon, 09 May 94 17:07:32 -0400 |
CEBAF's strategy for CAMAC in EPICS is to have all CAMAC device
support sit directly above the CAMAC IEEE/ESONE standard routines.
I.e., they use nothing except the standard routines.
The advantage of this is that then EPICS can run against ANY
CAMAC interface, since all CAMAC interfaces have the IEEE routines
available, or can easily have these routines added. At CEBAF, we
use 2 different hardware interfaces, and the standard routines hide
the differences from EPICS.
I will grant that this could cost slightly in performance in principle,
however, with good coding this is not the case, and the portability
is worth the extra effort.
Device initialization, therefore, becomes the domain of the device
support layer, using standard routine calls. We are considering
adding LAM callbacks in device support to detect crate power-up so
that we can automatically re-initialize a crate without restarting EPICS.
The CAMAC device support will support (coming in a month) an initialization
function as part of the hardware address "parm" field, and this function
will be repeated when the power interrupt occurs. This is consistent
of our strategy of having most CAMAC modules supported by a single,
generic, CAMAC device support (less code to maintain).
Chip
- Navigate by Date:
- Prev:
camac crate initialization Rozelle Wright
- Next:
applications that use channel access Jeff Hill
- 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:
camac crate initialization Rozelle Wright
- Next:
AR docs greene%denali . UUCP
- 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
|