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  <20102011  2012  2013  2014  2015  2016  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  <20102011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Re: asyn re-connect problem
From: Benjamin Franksen <[email protected]>
To: [email protected]
Date: Thu, 16 Dec 2010 14:03:47 +0100
An here is the fix: in asyn/vxi11/drvVxi11.c, procedure vxiConnectPort, line 
906, vxiCreateDeviceLink gets called. Before this is done, the member 
abortPort must be cleared (set to 0). Thus I added

    pvxiPort->abortPort = 0;

at line 905 and now re-connects work as expected.

Cheers
Ben

On Thursday, December 16, 2010, Benjamin Franksen wrote:
> The reconnect feature in asyn is still buggy. I am using it with a
> gpib/lan gateway (Agilent E5810A). Any time I reboot the gpib box I get
> these messages:
> 
> -------------------------------------------------
> epics> 2010/12/16 13:07:44.150 L3 PAHRP:NRVD:cmdTrg: asynError in read:
> L3 RPC failed
> 
> 2010/12/16 13:07:44.150 L3 PAHRP:NRVD:cmdTrg: I/O error after reading 0
> bytes: ""
> 2010/12/16 13:07:44.150 L3 PAHRP:NRVD:cmdTrg: Protocol aborted
> 2010/12/16 13:07:45.747 L3 vxiDestroyDevLink RPC error : RPC: Unable to
> send; errno = Broken pipe
> 
> 2010/12/16 13:07:45.747 L3 vxiDisconnectPort : RPC: Unable to send; errno
> = Broken pipe
> 
> 2010/12/16 13:07:47.750 L3 vxiDestroyDevLink RPC error : RPC: Unable to
> send; errno = Broken pipe
> 
> L3 port not connected
> 2010/12/16 13:07:47.750 L3 asynGpib:pollAddr srqEnable
> 2010/12/16 13:07:47.750 L3 PAHRP:NRVD:rdPow1: asynError in write: L3 RPC
> failed
> 
> 2010/12/16 13:07:47.750 cbLow PAHRP:NRVD:rdPow2 lockRequest:
> pasynManager-
> 
> >queueRequest() failed: port L3 not connected
> 
> 2010/12/16 13:07:47.766 gpib0 vxiCreateDeviceLink abort channel TCP port
> changed from 1004 to 1005
> 2010/12/16 13:07:47.772 gpib0,20 vxiCreateDeviceLink abort channel TCP
> port changed from 1004 to 1005
> -------------------------------------------------
> 
> Afterwards there are no further communication attempts; rebooting the IOC
> correctly establishes a new connection.
> 
> The IOC runs on a GNU/linux system. Version info:
> 
> kernel 2.6.18-6-686
> EPICS base-3.14.8.2
> asyn-4.15
> streamDevice-2-snapshot20100615
> 
> Cheers
> Ben


References:
asyn re-connect problem Benjamin Franksen

Navigate by Date:
Prev: asyn re-connect problem Benjamin Franksen
Next: Re: About PCAS Access Control William Lu
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  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: asyn re-connect problem Benjamin Franksen
Next: 24-bit DAC Eric Berryman
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  2020  2021  2022  2023  2024 
ANJ, 16 Dec 2010 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·