I have encountered a situation in which spurious (i.e. unexpected) link
alarms are being generated following the reboot of an IOC. The record
connectivity is:
Record A has a scan rate of one second
Record A has a forward link to record B
Record B has an input link in its INP field that references record A with
"NPP"
and "MS" specified.
When record A is processed for the first time, record B registers an
"INVALID" alarm severity with a "LINK" alarm status. The second time that A
is processed, the "INVALID" alarm severity is cleared.
I believe that, when record B retrieves the value from record A during the
initial process cycle, the alarm severity that is propagated by the "MS"
specification is "INVALID" because record A must, somehow, retain the
original "INVALID" severity and the "UDF" status even though it has already
processed. During subsequent process cycles, record B does not generate an
"LINK" alarm status because record A no longer has "UDF" alarm status.
This behavior is counter-intuitive. The "Application Developer's Guide"
states that the forward link is not executed until the originating record
has completed processing. If this is the case, why does an input link to
that record transfer the prior (or initial) alarm state?
Finally, we are still using release 3.13.4.
Fritz
- Replies:
- Re: Spurious link alarms generated? Marty Kraimer
- Navigate by Date:
- Prev:
RE: Novice EPICS questions re yet another port David Kelly
- Next:
Software listing Ian Lenzen
- 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: "assert (this->exitWait ( DBL_MAX ))" failed Jeff Hill
- Next:
Re: Spurious link alarms generated? 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
|