The standard way to handle error returns from the device was to place the
record into INVALID alarm severity and then place the reason in the STAT
field. THe typical STAT was just READ or WRITE. You may want to extend the
alarm status menu to add some new choices if there are only a few.
Otherwise, the alternatives mentioned in earlier email may be useful. I tend
to keep error status available from the driver through pseudo channels.
These are addresses that are not used by the hardware. THey return things
like number of data timeout errors, crc errors, etc..
- References:
- RE: Status return from EPICS device support Jeff Hill
- Navigate by Date:
- Prev:
Re: Status return from EPICS device support Steve Lewis
- Next:
Building dm2k problem... Leonard J. Reder
- 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: Status return from EPICS device support Jeff Hill
- Next:
Re: Status return from EPICS device support Steve Lewis
- 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
|