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: CA monitoring weirdness for status/severity |
From: | "Hogben, Colin H" <[email protected]> |
To: | "Johnson, Andrew N." <[email protected]> |
Cc: | "[email protected]" <[email protected]> |
Date: | Tue, 08 Aug 2017 15:03:16 +0100 |
On 07/08/17 19:22, Johnson, Andrew N. wrote:
* If the PV represents the VAL field. then the status & severity in updates may be used; in effect, this is effectively a short-cut to getting the VAL, STAT and SEVR fields at the same time. * If the PV represents any other field, the status and severity in an update are meaningless noise and should be disregarded. Is that a reasonable approximation?Yes. You could also use the presence of a '.' in the PV name to switch behaviors since .VAL is the default field if none is specified. Note that IOC PVs are likely to behave differently from those from other kinds of servers (CAS-based), and these rules only apply to IOCs.
OK, the test I am now using is: if the name ends with '.' and up to four uppercase letters which are not 'VAL' then ignore the status/severity. It seems to be working OK. As for non-IOC PVs, I'll cross that bridge when I come to it.
Thanks to all for your help. -- Colin Hogben Professional Software/Control Engineer CODAS & IT Department United Kingdom Atomic Energy Authority Culham Science Centre Abingdon Oxfordshire OX14 3DB Tel : 01235 464948 Web: www.gov.uk/ukaea