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: How to tag soft channels as undefined/disconnected |
From: | Kellee Summers <[email protected]> |
To: | "Andrew C. Starritt" <[email protected]>, "Lionberger, Carl A." <[email protected]>, "[email protected]" <[email protected]> |
Date: | Thu, 14 Aug 2014 08:41:31 -0700 |
Thanks Andrew, I must have something wrong in my record definition or I am doing something incorrectly, because that does not work for me from my C++ program. I cannot even set the UDF to 1 with a caput. $ caget lbc:side0:dewarTemp.UDFVery simple record definition: record(ao, "lbc:side0:dewarTemp") ... Kellee On 08/13/2014 05:45 PM, Andrew C.
Starritt wrote:
Hi Kellee, I did something like what you are doing. The PV values are written to by a bash script. If/when the source data did not exist or was stale I did I wrote 1 to the record's UDF field which set it invalid. # Set undefined. # caput ${pvname:?}.UDF 1 where worked for me, i.e. set SEVR to INVALID and STAT to UDF (using base-3.14.12.3) Regards Andrew C. Starritt | Principal Controls Engineer | Australian Synchrotron p: (03) 8540 4164 | f: (03) 8540 4200 [email protected] | www.synchrotron.org.au 800 Blackburn Road, Clayton, Victoria 3168 -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Kellee Summers Sent: Thursday, 14 August 2014 12:50 AM To: Lionberger, Carl A.; [email protected] Subject: Re: How to tag soft channels as undefined/disconnected This sounds pretty simple and what I'm trying to do. The problem is I don't know how to do this part: "sets the PV invalid" How do you do that? Is that just some kind of timeout on the processing? Thanks for your help, Kellee On 08/13/2014 06:47 AM, Lionberger, Carl A. wrote:For a project where I had a python program updating soft PVs, I wrote a timeout device support to use instead of the soft channel device support. It times out and sets the PV invalid if a new value was not put to it within the timeout period since the last put. The C++ application just wouldn't put the value to the PV if the instrument data was invalid, and then the PV would go invalid without further action. When valid data became available, the application would put it to the PV and the PV status would go normal again. Carl Carl Lionberger Instrument Data Acquisition and Controls Spallation Neutron Source ________________________________________ From: [email protected] <[email protected]> on behalf of Kellee Summers <[email protected]> Sent: Tuesday, August 12, 2014 7: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 |