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  2015  2016  2017  <20182019  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  2015  2016  2017  <20182019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: RE: Asyn not automatically reconnecting
From: Mark Rivers <[email protected]>
To: "'Daykin, Evan'" <[email protected]>, "[email protected]" <[email protected]>
Date: Thu, 22 Feb 2018 23:19:58 +0000

Hi Evan,

 

Ø  We have client devices that, when remotely updated and rebooted, the IOC does not attempt to reconnect automatically

Ø  TEST-RF-DCU-N0001 multiDevice:No canBlock:Yes autoConnect:Yes

Ø  enabled:Yes connected:No numberConnects 1

Ø  nDevices 0 nQueued 114 blocked:No

 

The above information says that indeed autoConnect is set to Yes, and it is currently not connected.  The 114 entries in the queue seems strange.

 

What version of asyn and what version of StreamDevice are you using?  What you are observing does not seem correct.

 

What timeouts if any have you specified in your protocol file?

 

Mark

 

 

 

 

From: [email protected] [mailto:[email protected]] On Behalf Of Daykin, Evan
Sent: Thursday, February 22, 2018 4:32 PM
To: [email protected]
Subject: Asyn not automatically reconnecting

 

Hello,

 

Apologies if this has already been asked and answered. We have client devices that, when remotely updated and rebooted, the IOC does not attempt to reconnect automatically. Any records tied to it simply enter a TIMEOUT_ALARM state, and no asyn or StreamDevice error messages are printed.  autoConnect is not specified in drvAsynIPPortconfigure, which, according to the documentation, implicitly enables autoConnect/attempting to reconnect every 20 seconds.  Does anything else need to be done?

 

The devices are configured to communicate using Stream Device.

Relevant asyn configuration in the startup script:

-drvAsynIPPortConfigure("TEST-RF-DCU-N0001",  "test-rf-dcu-n0001.cts:5001”)

 

asynReport after client is disconnected and brought back up:

TEST-RF-DCU-N0001 multiDevice:No canBlock:Yes autoConnect:Yes

    enabled:Yes connected:No numberConnects 1

    nDevices 0 nQueued 114 blocked:No

    asynManagerLock:No synchronousLock:Yes

    exceptionActive:No exceptionUsers 2 exceptionNotifys 0

    traceMask:0x1 traceIOMask:0x0 traceInfoMask:0x1

    interposeInterfaceList

        asynOctet pinterface 0x7f0a07506900 drvPvt 0x6c3720

    interfaceList

        asynCommon pinterface 0x7f0a07502650 drvPvt 0x6bfe30

        asynOption pinterface 0x7f0a07502670 drvPvt 0x6bfe30

        asynOctet pinterface 0x6bff50 drvPvt 0x6bfe30

    Port test-rf-dcu-n0001.cts:5001: Disconnected

                    fd: -1

    Characters written: 127036

       Characters read: 138000

 

-Evan


References:
Asyn not automatically reconnecting Daykin, Evan

Navigate by Date:
Prev: Asyn not automatically reconnecting Daykin, Evan
Next: Looking for areaDetector driver Jörn Dreyer
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  <20182019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: Asyn not automatically reconnecting Daykin, Evan
Next: RE: Asyn not automatically reconnecting Daykin, Evan
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  <20182019  2020  2021  2022  2023  2024 
ANJ, 23 Feb 2018 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·