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 2025 | 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 2025 |
<== Date ==> | <== Thread ==> |
---|
Subject: | Re: aSub debug output |
From: | "Johnson, Andrew N. via Tech-talk" <tech-talk at aps.anl.gov> |
To: | Michael Davidsaver <mdavidsaver at gmail.com> |
Cc: | EPICS tech-talk <tech-talk at aps.anl.gov>, "Daykin, Evan" <daykin at frib.msu.edu> |
Date: | Wed, 2 Dec 2020 23:19:21 +0000 |
On Dec 2, 2020, at 2:39 PM, Michael Davidsaver <mdavidsaver at gmail.com> wrote:
I don’t think Evan needs to set MSI for the record to go into an INVALID/LINK alarm state if one or more of the links isn’t connected, that should be happening anyway. This example uses a subRecord but the same rules apply, the subroutine isn’t
called if any of the input links aren’t connected:
Note that in the second dbpr output SEVR: INVALID STAT: LINK show that the record is in alarm
state because the INPA field wasn’t connected. How you might flag that to a human when it happens is a different question though, records go into alarm state all the time and never announce that on the IOC console. Maybe some other parts of the database or
its clients need to monitor the record’s alarm state if this situation can arise and needs to be known about?
Note that there is an iocsh command which tells you about any unconnected CA links in the database:
If you have devIocStats loaded that has PVs that report the connected and disconnected counts.
- Andrew
--
Complexity comes for free, simplicity you have to work for.
|