EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  <20152016  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  <20152016  2017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: RE: Problems with asyn read calls at driver exit
From: Sergio Esquembri <[email protected]>
To: Mark Rivers <[email protected]>
Cc: [email protected]
Date: Wed, 03 Jun 2015 10:50:47 +0100
Thanks Mark.

I have applied that and its working for the moment.

Sergio Esquembri
Technical University of Madrid

El 2015-05-28 14:46, Mark Rivers escribió:
One way that this is commonly done is to have your epicsAtExit handler
set a flag epicsExiting=true.  Then at the top of your I/O functions
you just return immediately if epicsExiting==true.

Mark

________________________________________
From: [email protected] [[email protected]] on
behalf of Sergio Esquembri [[email protected]]
Sent: Thursday, May 28, 2015 8:39 AM
To: [email protected]
Subject: Problems with asyn read calls at driver exit

Hi,

I'm developing an EPICS driver using asynDriver and I'm having problems
with the finalization of the driver. The function that frees all the
resources allocated and closes the session with the hardware driver is
registered with epicsAtExit. The problem here is that some PVs have
timed scans and the driver is receiving calls to the registered read
methods after the ioc exit call.

What is the best way to avoid read calls when closing the driver?
Should I unregister manually my driver from the asyn interfaces?

Any help or hint about this will be appreciated.

Thanks,
Sergio.

--
-----------------------------

References:
Problems with asyn read calls at driver exit Sergio Esquembri
RE: Problems with asyn read calls at driver exit Mark Rivers

Navigate by Date:
Prev: RE: Rotating or deleting procServ log files Mark Rivers
Next: in 3.15.2 the file aSubRecord.h is not properly generated by dbdToRecordtypeH.pl Yves Lussignol
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  <20152016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: RE: Problems with asyn read calls at driver exit Mark Rivers
Next: MAXv controller limits Phil Brown
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  <20152016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 16 Dec 2015 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·