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: EPICS R3.15 and menuScan.dbd |
From: | "Johnson, Andrew N. via Tech-talk" <[email protected]> |
To: | "[email protected]" <[email protected]> |
Date: | Mon, 6 Jan 2020 21:25:46 +0000 |
Ah, don't do that last bit, see below. You probably didn't actually do that with 3.14 either...In the past (using EPICS R3.14.12.x) when we wanted to use custom scan rates, we included a customized version of menuScan.dbd in the source code directory of the IOC project and added 'project_DBD += menuScan.dbd' to the Makefile.
No, just put the menuScan.dbd file in the iocApp/src directory where you compile the IOC, but do not add it to the Makefile at all. When the IOC's DBD file gets expanded it will pull in base.dbd, which includes menuScan.dbd, and the search order for the file expansion will find your new file before it sees the one in Base. You could also install a menuScan.dbd file into a support module's dbd directory if you want to override the Base version for all IOCs that use that support module (as long as the RELEASE files list the support module before their EPICS_BASE entry).However, under EPICSS R3.15 the compilation now fails with multiple errors that say dbdExpand.pl: A different menu named 'menuScan' already exists
It seems we get one of these error messages for each support module that is included in the project.
Is there a new way of defining custom scan rates on a per project basis in EPICS R3.15?
-- Complexity comes for free, Simplicity you have to work for.