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  <20102011  2012  2013  2014  2015  2016  2017  2018  2019  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  <20102011  2012  2013  2014  2015  2016  2017  2018  2019 
<== Date ==> <== Thread ==>

Subject: Re: IP asyn timeout connection
From: Dominique Touchard <touchard@ganil.fr>
To: Mark Rivers <rivers@cars.uchicago.edu>
Cc: tech-talk@aps.anl.gov
Date: Thu, 11 Mar 2010 18:47:25 +0100


Mark Rivers a écrit :
Hi Dominique,

I was thinking about this some more, and realized I may have
misunderstood your question.

When you say: 
  
At each time there could be a few modbus tcp devices that 
are not available during the vme startup.
    

Do you mean that they are not available for good reason, like they are
powered off, disconnected from the network, etc.?  And that the problem
is that it takes a long time for the driver to time out trying to reach
them?  
Yes yes yes. Thanks.
If that is what you meant, then that is a separate problem, which
I confess I have not paid much attention to this in the past, because I
have assumed that the devices must be available for the IOC to function
correctly.

Let me know if this is what you meant and I will look into it and get
  
back to you.
  
Between my first mail and your answer, I read rapidly vxworks docs and modbus,asyn sources. It seems that we cannot change the timeout connection value with asyn. But it seems that we can change the TCP_CON_TIMEO_DFLT vxworks kernel parameter. I am not a specialist and I ask to our team,  (Hi Yves and Pierre), if we could test this last solution. If you have another solution, it would be very nice of you.

Thanks again for your help.

Dominique.
Mark


-----Original Message-----
From: Dominique Touchard [mailto:touchard@ganil.fr] 
Sent: Thursday, March 11, 2010 8:06 AM
To: Mark Rivers
Subject: IP asyn timeout connection

Hi Mark,

we are using the modbus tcp (thanks again for your software) to control 
a few dozen of devices from an EPICS  vme crate. We are testing now our 
configuration, and starting often the vme crate to change our test 
configuration. At each time there could be a few modbus tcp devices that

are not available during the vme startup.

There are a lot of waste time to wait for timeout connections during the

drvMobusAsynConfigure command.( I suppose) (for example, we are testing 
now 34 devices which owns 4 modbus functions, one global read and three 
discret writes. In this case, the startup could spend half one hour 
without any acces to the IOC)

I don't find where we can set the timeout for the first connection try.

Any help would be appreciated.

Thanks again.

Dominique Touchard.


  

References:
RE: IP asyn timeout connection Mark Rivers

Navigate by Date:
Prev: Re: Building StreamDevice 2-4 / SynApps / Win32 John Dobbins
Next: Re: 2 MAXv problems Steven M. Hartman
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  <20102011  2012  2013  2014  2015  2016  2017  2018  2019 
Navigate by Thread:
Prev: RE: IP asyn timeout connection Mark Rivers
Next: Building StreamDevice 2-4 / SynApps / Win32 John Dobbins
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  <20102011  2012  2013  2014  2015  2016  2017  2018  2019 
ANJ, 02 Sep 2010 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·