EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  <20002001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024  Index 1994  1995  1996  1997  1998  1999  <20002001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Re: VxWorks global variable device support
From: [email protected] (Deb Kerstiens)
To: [email protected], [email protected]
Cc: [email protected]
Date: Thu, 3 Feb 2000 11:20:41 -0700
> 
>   > We might consider one additional subtlety
> 
> Just one?
> 
>   > for those of us who use STAT and/or
>   > SEVR, particularly to display value with a color rule that indicates these
>   > values.  If an output record had readback but was not processed, would it affect
>   > STAT and/or SEVR values.  Right now I think these are usually UDF and INVALID
>   > respectively until the record is processed. 
> 
> Good point. As the record is defined after reading back the value,
> UDF/INVALID is inappropriate. Would you think we need to have another
> status that announces that the value has been read back and is valid, but
> the record hasn't been processed yet? Or would that be too subtle a
> difference to be signalled?
> 
> Ralph
> 

>From my own perspective, the distinction would not generally be an important 
one.  It might be an important one, though, if you're accustomed to using the 
UDF and INVALID as indications that a record hasn't been processed when 
debugging applications at the IOC level as I often do.  You'd have to look at
the "read but don't process" choice if the record used DOL to understand why 
VAL was different from DOL and why nothing else in the chain had been processed.So it might be nice to have the distinction reflected in STAT and SEVR (if it's not too much trouble :-), but I can live without it if no one else cares.
 
deb


Navigate by Date:
Prev: Re: VxWorks global variable device support Ralph . Lange
Next: Re: VxWorks global variable device support Nick Rees
Index: 1994  1995  1996  1997  1998  1999  <20002001  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: support for output records Bernd Schoeneburg
Next: Re: VxWorks global variable device support William Lupton
Index: 1994  1995  1996  1997  1998  1999  <20002001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 10 Aug 2010 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·