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  2015  2016  2017  2018  <20192020  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  <20192020 
<== Date ==> <== Thread ==>

Subject: Re: Weird stream device behavior when using the IOC shell's exit function
From: Dirk Zimoch via Tech-talk <tech-talk@aps.anl.gov>
To: <tech-talk@aps.anl.gov>
Date: Wed, 6 Feb 2019 13:50:38 +0100
Can it be that several records have queued up on the asyn port when the ioc exits? In that case scanning would already have been stopped, but still records may be scheduled to access the port when the ioc is already shutting down. Maybe I need to check the ioc run state and discard all queued records when the ioc is shutting down. Also this behavior may be a side effect of the new cases in that the @init handler is supposed to run, namely after asyn port re-connect and after ioc resume (iocRun). I need to check...

Dirk

On 04.02.19 08:41, Abdalla Ahmad via Tech-talk wrote:
Hi

We are using the following setup to test control of the agilent XGS gauge controllers and Gamma ion pump controllers:

1.EPICS Base 3.15.6

2.Asyn R4-33

3.Stream R2-7-7c

For agilent controllers we get the following error:

asynError in write. Asyn driver says: device:port disconnected.

But eventually the IOC exits. For the gamma controllers we get something really strange. There a point in the database where the IOC never exits, the exit command just freezes and Ctrl-C is the only way to shut down the IOC. For now I can see that this behavior occurs because more DB substitutions are configured which means more PVs and more controllers. But that was not the case when we had:

1.EPICS Base 3.14.12.3

2.Asyn R4-18

3.Stream R2-5-1

Where the IOC exits with no errors or freezing. Should we upgrade our support modules or change the EPICS base?

Another problem we are facing with this new setup is that I can't find some asyn IOC shell function like asynTraceMask for example. The IOC is configured properly in RELEASE and src/Makefile. Is there anything we miss in the new setup?

Best Regards,

Abdalla Ahmad

Control Engineer

SESAME

Allan, Jordan.

Tel: (+962-5) 3511348 , ext. 265

Fax: (+962-5) 3511423

Mob: (+962-7)88183296

www.sesame.org.jo <http://www.sesame.org.jo/>


Replies:
RE: Weird stream device behavior when using the IOC shell's exit function Mark Rivers via Tech-talk
References:
Weird stream device behavior when using the IOC shell's exit function Abdalla Ahmad via Tech-talk

Navigate by Date:
Prev: RE: Weird stream device behavior when using the IOC shell's exit function Abdalla Ahmad via Tech-talk
Next: RE: Weird stream device behavior when using the IOC shell's exit function Mark Rivers via Tech-talk
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  <20192020 
Navigate by Thread:
Prev: RE: Weird stream device behavior when using the IOC shell's exit function Abdalla Ahmad via Tech-talk
Next: RE: Weird stream device behavior when using the IOC shell's exit function Mark Rivers via Tech-talk
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  <20192020 
ANJ, 06 Feb 2019 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·