Subject: |
Re: output record initialization |
From: |
[email protected] (Gordon Uchenick) |
To: |
[email protected], uupsi5!keck.hawaii.edu!wlupton |
Date: |
Thu, 31 Aug 95 16:47:03 EDT |
This is a subject that is guaranteed to start heated debate, if not
fist fights (at least on the East Coast). First of all, initialization
of outputs may be hardware specific because some types of I/O are affected
by a reset and other types are not. Not all types of I/O will allow you to
read back a value. The "suitable" thing to do may also depend on how long
the IOC has been down (a few seconds? a few minutes? a week? How do you
know for sure?).
IMHO, it make sense for a database designer to be able to specify whether
or not he wants a certain value to be output on restart. What do you do
when he hasn't? The general practice that I've seen is that, during
initialization, an output block should write ABSOLUTELY NOTHING to the
hardware unless it has been commanded by either an operator or an upstream
block. Aside from safety's sake, we must realize that we are just restarting
an IOC. We are not necessarily restarting the process!
Gordon
- Navigate by Date:
- Prev:
output record initialization William Lupton
- Next:
Re: Q: NI-1014 GPIB board with Force CPU40. Noboru Yamamoto
- 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:
output record initialization William Lupton
- Next:
Re: output record initialization watson
- 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
|