>
> I don't know enough about how Bob's archiver handles these bumpless
> reboot situations. (I guess it is by IOC, not by record.) Most of our
> outputs are read back during IOC initialisation (the inherent luxury of
> a fieldbus based design) --- this is handled record-wise by device
> support looking at the PINI field.
>
> Specifying "readback wanted" in the OUT link seems absolutely
> appropriate in your case.
>
> Maybe all output records should have a menu-type field that specifies if
> readback at init time should be performed.
>
> Should they?
>
> Ralph
>
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,
so it would be great to add the selectable readback to all output records
or add something like RINI (read at initialization) to read but not process.
We might consider one additional subtlety 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.
- Replies:
- Re: VxWorks global variable device support Ralph . Lange
- Re: VxWorks global variable device support Nick Rees
- Navigate by Date:
- Prev:
RE: Python/CA Jeff Hill
- Next:
Re: VxWorks global variable device support (capfast can default DOL to not set) Rozelle Wright
- 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 Ralph . Lange
- Next:
Re: VxWorks global variable device support Ralph . Lange
- 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
|