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: Mark Rivers <[email protected]>
To: Sergio Esquembri <[email protected]>, "[email protected]" <[email protected]>
Date: Thu, 28 May 2015 13:46:29 +0000
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.

--
-----------------------------
Sergio Esquembri
Technical University of Madrid
Instrumentation and Applied Acoustic Research Group
Crta Valencia Km-7
Madrid 28031
Phone(R&D Lab): 913364696 Ext: 29400
email: [email protected]
-----------------------------
Disclaimer:
This e-mail message may contain confidential information and/or legally
privileged and is intended only for the use of the addressed person. Any
disclosure, copying, distribution or the taking of any action in reliance
on the contents of this e-mail by any other person is strictly prohibited.
If you believe that it has been sent to you in error, please reply to the
sender that you have received the message in error, then delete this
message from your system. Thank you for your cooperation.



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

Navigate by Date:
Prev: Problems with asyn read calls at driver exit Sergio Esquembri
Next: Re: Draft requirements document for enhanced EPICS motor support Pearson, Matthew R.
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: Problems with asyn read calls at driver exit Sergio Esquembri
Next: RE: Problems with asyn read calls at driver exit Sergio Esquembri
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 ·