Experimental Physics and Industrial Control System
|
I thought this STAT==UDF alarm stuff was the reason some records were
changed to allow their UDF field to be specified at DCT time. But we've
also seen a record with UDF==0 specified in the database *still* come
up with STAT==UDF. I can't think of a use for this behavior. How about
if init_record() were to set STAT/SEVR="NO_ALARM" if it saw that UDF==0?
And why not setting PINI=Yes to say this record is processed and ready
to use and keep the one thing for all records in mind that: a record is
undefined and invalid until it is processed! This behaviour is
neccessary for all records with hardware access and to start all records
this way keeps from beeing puzzled about what state any particular
record should be have after the start of an ioc because it is UDF INVALID.
- References:
- Initial STAT and SEVR for soft ai and ao records Mark Rivers
- Re: Initial STAT and SEVR for soft ai and ao records Marty Kraimer
- Re: Initial STAT and SEVR for soft ai and ao records Tim Mooney
- Navigate by Date:
- Prev:
Re: Initial STAT and SEVR for soft ai and ao records Tim Mooney
- Next:
RE: Initial STAT and SEVR for soft ai and ao records Mark Rivers
- 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: Initial STAT and SEVR for soft ai and ao records Tim Mooney
- Next:
RE: Initial STAT and SEVR for soft ai and ao records Mark Rivers
- 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
|
ANJ, 02 Sep 2010 |
·
Home
·
News
·
About
·
Base
·
Modules
·
Extensions
·
Distributions
·
Download
·
·
Search
·
EPICS V4
·
IRMIS
·
Talk
·
Bugs
·
Documents
·
Links
·
Licensing
·
|