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: | Way to know when streamReload has been completed |
From: | "Zimoch Dirk \(PSI\) via Tech-talk" <tech-talk at aps.anl.gov> |
To: | "Wang, Andrew" <wang126 at llnl.gov> |
Cc: | EPICS tech-talk <tech-talk at aps.anl.gov> |
Date: | Wed, 3 Aug 2022 17:02:26 +0000 |
Hi Andy,
When the function returns it has finished its work, i.e. all currently running protocols have beeb aborted and all records have re-read their protocol files. At that time, the sub record finishes processing. Thus, you can write using a caput with callback.
When it returns, all work is done.
If you (i.e. the CA client you are using) have no callback option, then you can FLNK some records together to set some record to 1, then call streamReload and from there FLNK to a record that writes 0.
Maybe you can use the busyRecord somehow, but I have never tried that.
Dirk
Am 02.08.2022 um 19:08 schrieb Wang, Andrew via Tech-talk <tech-talk at aps.anl.gov>:
|