Experimental Physics and Industrial Control System
Hello all,
I just observed a passive analog output record that after rec init had
STAT=UDF_ALARM, SEVR=INVALID_ALARM, and UDF=0. My device support
successfully read the initial value out of the device (and
indirectly set UDF to false). Once this record is processed for the
first time then the UDF alarm condition goes away.
This appears to be a flaw in the AO record. The ascii rec def initializes
stat=UDF and sevr=INVALID. When the record inits if we get the value from the
device and the udf field becomes zero then we dont reset stat and sevr.
Most likely we need to call alarm() from within AO rec support just after
calling devRecInit()? Since recGblSetSevr() maximizes the alarm condition
we would need to init stat/sevr to no alarm?
It is hard to believe that this has gone undetected for this long.
Has anyone else noticed a passive AO rec in alarm state UDF that
successfully read its initial value from the IO but hasnt been processed
for the first time?
Jeff
______________________________________________________________________
Jeffrey O. Hill Internet [email protected]
LANL MS H820 Voice 505 665 1831
Los Alamos, NM 87545 USA FAX 505 665 5107
- Navigate by Date:
- Prev:
Re: Free GDCT and Alpha/Digital Unix Tim Mooney
- Next:
Re: AO rec flaw Marty Kraimer
- 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: Free GDCT and Alpha/Digital Unix Tim Mooney
- Next:
Re: AO rec flaw Marty Kraimer
- 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