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: Base 3.15 and record initialization |
From: | Andreas Lüdeke <[email protected]> |
To: | <[email protected]>, <[email protected]>, <[email protected]> |
Date: | Sat, 2 Sep 2017 10:39:26 +0200 |
Hi Michael, > Notice the "MS" in the calc record's INPA. We don't yet know why the original developer did this, > and it seems that it would just cause the record to get stuck in an alarm state if any input went into an alarm state. Instead you should change to record(calc, "TEST123:CalcTest") {
field(INPA, "TEST123:CalcTest NPP
MS")
field(INPB, "TEST123:AoTest NPP MS")
field(CALC, "B<100?(A+1):A")
field(FLNK, "TEST123:AiTest")
field(SEVR, "NO_ALARM")
field(UDF, "0")
}
But it might even be that your problem has nothing to do with the upgrade to 3.15. If the developer wanted to latch all alarms of the inputs, then he probably provided a mechanism to reset the alarm. Once you do that, you don't want to have it reset just because you've rebooted. Therefore you put the SEVR and UDF fields of the calc record into autoSR / bumpless reboot configuration. If those configuration was not there for a single reboot (that might happen when you upgrade), then you'll end up with INVALID / UDF alarms in the calc record. If that was the case then do not change the DB, just set once SEVR=NO_ALARM manually and it'll work as before. I hope that helped a little? Cheers Andreas |