On Dienstag, 14. Juli 2009, Szalata, Zenon M. wrote:
> I am running a test soft IOC, which performs a few simple functions on a
> GPIB instrument. The instrument is connected to Agilent E2050 gateway.
> The IOC is periodically reading the Status Byte. After a few hours the
> communication between the IOC and the device is broken. This is what I
> get:
>
> --------------------
> 02009/07/14 08:50:24.312 L0 vxi11 clientIoCall errno Connection reset by
> peer clnt_stat 4 2009/07/14 08:50:24.312 L0 vxiDestroyDevLink RPC error :
> RPC: Unable to send; errno = Broken pipe
>
> 2009/07/14 08:50:24.312 L0 vxiDisconnectPort : RPC: Unable to send; errno
> = Broken pipe
>
> 2009/07/14 08:50:26.314 L0 vxiDestroyDevLink RPC error : RPC: Unable to
> send; errno = Broken pipe
>
> L0 port not connected
> 2009/07/14 08:50:26.314 L0 asynGpib:pollAddr srqEnable
> 2009/07/14 08:50:26.314 MAGS:ASYN:IO: Write error, nout=0, L0 RPC failed
>
> 2009/07/14 08:50:26.314 L0 port not connected
> 2009/07/14 08:50:26.314 MAGS:ASYN:IO: Error L0 port is not connected
>
> 2009/07/14 08:50:26.314 MAGS:ASYN:IO: error nread 162331380 L0 port is
> not connected
>
> 2009/07/14 08:50:26.314 MAGS:ASYN:IO: Overflow nread 162331380 L0 port is
> not connected --------------------
>
> I have two E2050 devices and both exhibits the same behavior. The length
> of time until the communication falls apart varies. It could be as short
> as an hour or so, or as long as 10 hours.
>
> Here is the E2050 configuration:
>
> Configuration Parameters
> hostname: E2050-esalangpib2 # Internet domain name
> hardware-addr: 0800091B1EEB # Ethernet station address
> ip: 134.79.59.12 # Internet Protocol address
> default-gw: 134.79.59.1 # Default subnet gateway IP address
> subnet-mask: 255.255.252.0 # Network subnet mask
> syslog-svr: 0.0.0.0 # Syslog server IP address
> bootp: OFF # Obtain config via BOOTP/TFTP
> lan-timeout: 0 # LAN connect timeout in seconds
> io-timeout: 120 # Server I/O timeout in seconds
> allow: * # IP allow list
>
> hpib-address: 0 # HP-IB System Controller Address
> hpib-name: gpib0 # HP-IB interface symbolic name
> hpib-unit: 7 # HP-IB logical unit number
>
>
> Is this problem due to improper use of the gateway or are these devices
> malfunctioning?
Since you get "Connection reset by peer" error, I bet this is either a bug
in the E2050 firmware or a network problem (or both). Try to update the
firmware. If that doesn't help or it is already the newest version, try to
analyse the network traffic, especially between IOC and gateway. Sometimes
devices have problems with auto-negotiation of low-level ethernet protocol
(10 or 100 Mbit/s, half or full duplex). If there are conspiciously many
erroneous packages you might want to experiment with fixed settings, such
as 100 Mbit/half duplex.
Just my 2 cents.
Cheers
Ben
- References:
- Agilent E2050 Szalata, Zenon M.
- Navigate by Date:
- Prev:
RE: When an external device does not provide termination on TCP ASCIIstream replies Mark Rivers
- Next:
Re: DB CA link to PROC field Tim Mooney
- 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
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
Agilent E2050 Szalata, Zenon M.
- Next:
When an external device does not provide termination on TCP ASCII stream replies Allison, Stephanie
- 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
2019
2020
2021
2022
2023
2024
|