EPICS Home

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: Abdalla Ahmad via Tech-talk <tech-talk@aps.anl.gov>
To: Mark Rivers <rivers@cars.uchicago.edu>
Cc: "tech-talk@aps.anl.gov" <tech-talk@aps.anl.gov>
Date: Mon, 4 Feb 2019 14:43:41 +0000
Hello Mark

I will apply the gdb tip and get back to you. For the asyn commands, I don't see any asyn command when I type exit.

Get Outlook for Android




On Mon, Feb 4, 2019 at 4:33 PM +0200, "Mark Rivers" <rivers@cars.uchicago.edu> wrote:

Hi Abdalla,
 
> asynError in write. Asyn driver says: device:port disconnected.

During IOC shutdown asyn does close all TCP ports.  However, record processing should have already been shut down, so I don't understand why you are getting that message from Stream.

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?

> 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.

I don't think I have seen that with Stream on any version of Stream/asyn/base that I have used.  That includes base 3.14.12, 3.15.5, 7.0.2.

If you run the IOC with gdb then when you type exit and it hangs do the following:

- Type Ctrl-C
- Enter the gdb command
thread apply all bt

That will show you the current stack trace for all threads.  You can then see what is blocking the threads.

> 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?

The command is not "asynTraceMask" it is "asynSetTraceMask" or "asynSetTraceIOMask".  

What asyn commands do you see if you type "help" at the iocsh prompt?

Mark

________________________________________
From: tech-talk-bounces@aps.anl.gov  on behalf of Abdalla Ahmad via Tech-talk 
Sent: Monday, February 4, 2019 1:41 AM
To: tech-talk@aps.anl.gov
Subject: Weird stream device behavior when using the IOC shell's exit function 
 
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
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
Re: Weird stream device behavior when using the IOC shell's exit function Mark Rivers via Tech-talk

Navigate by Date:
Prev: Re: Weird stream device behavior when using the IOC shell's exit function Mark Rivers 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 Mark Rivers 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