> I don't like to have to process the output records and cause any resulting
> processing just to get the current value of an output record after a reboot,
I agree. As all our fieldbus directed outputs are terminal, i.e. there is
no resulting processing, we just didn't care.
> 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
- References:
- Re: VxWorks global variable device support Deb Kerstiens
- Navigate by Date:
- Prev:
Re: VxWorks global variable device support (capfast can default DOL to not set) Rozelle Wright
- Next:
Re: VxWorks global variable device support Deb Kerstiens
- 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: VxWorks global variable device support Deb Kerstiens
- Next:
Re: VxWorks global variable device support Nick Rees
- 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
|