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 | 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 |
<== Date ==> | <== Thread ==> |
---|
Subject: | Re: How to tag soft channels as undefined/disconnected |
From: | Maren Purves <[email protected]> |
To: | [email protected] |
Date: | Tue, 12 Aug 2014 13:37:56 -1000 |
On 08/12/14 13:26, Allison, Stephanie wrote:
Hi Kellee, You may want to read the tech-talk thread on back-propagating error states starting with this message: http://www.aps.anl.gov/epics/tech-talk/2009/msg00689.php I assume you want to invalidate your data, not show it as "disconnected". Basically, you set a record (ie, a bo record) to indicate the validity of your data - you will set it up so that record has either a NO_ALARM or INVALID severity. Then you use that record in the SDIS
I think I would just use the VAL field here. You can send out alarms or make decisions on the basis of the VAL field - what you call it is up to you. I realize that's not the exact same thing ...
field of the record with the data and use "CP MS" to maximize the severity (make sure DISV is set so it will never actually disable). If you don't want to use the disable feature of the record for the purpose of invalidating your data (it is a real kluge after all), then you can always FLNK your data record to a calc record that has as input both your data record and your validity record and maximizes the severity of both. All your clients then use the calc record instead of the data record for display and alarming.
HTH, Maren