| 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: base R7.0.3.1-1.0 db field DOL="" different behavior then in R3.14.12 |
| From: | Michael Davidsaver via Tech-talk <tech-talk at aps.anl.gov> |
| To: | "Luchini, Kristi L." <luchini at slac.stanford.edu> |
| Cc: | "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov> |
| Date: | Mon, 6 Mar 2023 16:13:55 +0000 |
On 3/3/23 23:38, Luchini, Kristi L. via Tech-talk wrote:
Hello, I’m upgrading an EPICS IOC Application from epics base R3.14.12 to R7.0.3.1-1.0, and I’ve noticed a different behavior on boot regarding the DOL field of an output record. For example for an aoRecord, in R3.14.12 if you set DOL=”” on boot the VAL field will be restored. If, DOL is a link then the value of that PV will be restored in the ao. However, in R7.0.3.1-1.0 , if DOL=”” a 0 is restored, independent of the VAL field. Only if I don’t specify the DOL field in the db, will the VAL field be restored on boot.
Is there a reason this behavior has changed? To me the R3.14.12 behavior seems to be correct.
If I have correctly understand the situation you describe, then this change was not intentional. Can you see if this change results in the behavior you expect? https://github.com/epics-base/epics-base/pull/335