EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  <20142015  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  <20142015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: RE: How to tag soft channels as undefined/disconnected
From: "Allison, Stephanie" <[email protected]>
To: "'Kellee Summers'" <[email protected]>, "[email protected]" <[email protected]>
Date: Tue, 12 Aug 2014 16:26:59 -0700
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 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. 

Stephanie Allison

> -----Original Message-----
> From: [email protected] [mailto:[email protected]] On Behalf
> Of Kellee Summers
> Sent: Tuesday, August 12, 2014 4:02 PM
> To: [email protected]
> Subject: How to tag soft channels as undefined/disconnected
> 
> Hi All,
> 
> We have set up an EPICS R3.14.12.4 database of pure software channels
> (on a Linux system) so that we can use the alarm handler. The channel
> values are being driven by a C++ software application that reads our
> instrument data.   When the instrument data is stale (determined by an
> out-of-date timestamp), I would like to
> set the channels to UDF so that the alarm state is INVALID.
> 
> The SEVR and STAT alarm fields are non-modifiable.  I tried setting the
> UDF field but it didn't give me a disconnected channel.
> 
> Do I need to modify the record processing?
> 
> Suggestions?
> 
> Thanks


Replies:
Re: How to tag soft channels as undefined/disconnected Maren Purves
References:
How to tag soft channels as undefined/disconnected Kellee Summers

Navigate by Date:
Prev: How to tag soft channels as undefined/disconnected Kellee Summers
Next: Re: How to tag soft channels as undefined/disconnected Maren Purves
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  <20142015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: How to tag soft channels as undefined/disconnected Kellee Summers
Next: Re: How to tag soft channels as undefined/disconnected Maren Purves
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  <20142015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 17 Dec 2015 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·