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: | Smoothing and alarm filtering on the analog input record - a proposal |
From: | "Dalesio, Leo" <[email protected]> |
To: | <[email protected]> |
Date: | Mon, 30 Mar 2009 16:43:07 -0400 |
DESY would like to see the following changes: SMOO applies to all values returned from device support - weather or not they need to be converted. This should have no impact - as device support that returns engineering numbers likely does not have SMOO set to anything. Same thing for returning values from database links that are inputs. Any objections? Add the following fields MSEV - measured alarm severity MSTA - measured alarm status CFIL - number of scans this status must be true before it is applied ACNT - number of scans this status and alarm severity have been detected Two questions: does the count get reset every time the alarm condition changes? Does it need to be more intelligent? We are accepting input for 24 hours. Thanks, Bob