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: | initHookFunction and asynPortDriver |
From: | Zenon Szalata <[email protected]> |
To: | Mark Rivers <[email protected]>, tech-talk <[email protected]> |
Date: | Wed, 6 Mar 2013 19:53:13 -0800 |
Hi Mark,I am wondering if there is functionality in asynPortDriver or asyn as such for having a callback routine be called at various stages of the DB initialization. I would like to use something like the EPICS initHookFunction. The problem with it is that it is a static function with no mechanism that I see to pass to it a pointer to my device driver class object, so that from the callback routine the correct instance of the device driver can be called. I have a situation where I have a few identical VME ADC boards and for each of these boards I create an object of the class (derived from asynPortDriver). I have klugged this as a function which I invoke from st.cmd file after IOC initialization is done. This works fine unless I need to have a bit more control when the routine is called, like after some phase of the DB init other than after all initialization is done.
Sorry for bugging you about this, Zen