EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  <20072008  2009  2010  2011  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  <20072008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Re: VXI11 ASYN problem on VxWorks
From: Eric Norum <[email protected]>
To: [email protected]
Cc: tech-talk talk <[email protected]>
Date: Fri, 15 Jun 2007 11:17:23 -0500
We use quite a few E5810s here. Most with systems other than vxWorks, though.

The error you're seeing is coming from clnttcp_create when it is trying to map the VXI-11 RPC program and version number to a TCP port number on the E5810. Do you have any network gateways between the IOC and the E5810 that could be blocking the UDP request to the portmapper in the E55810? Is your 55810 set to its factory defaults?


On Jun 15, 2007, at 10:29 AM, Matthew Pearson wrote:



Hi,


I'm trying to use a GPIB device via the VXI11 Agilent E5810A, by using the ASYN support for the E5810A. So in my IOC start up file I have:

iocshCmd("vxi11Configure L0 172.23.116.185 0 0.0 gpib0 0 0")

but at start up I get:

2007/06/15 15:17:53.852 L0 vxiConnectPort error 172.23.116.185: RPC: Program not registered

2007/06/15 15:17:53.852 asynManager::asynConnectCallback, port L0 error calling asynCommon->connect
2007/06/15 15:17:53.852 L0 vxiConnectPort error 172.23.116.185: RPC: Program not registered


2007/06/15 15:17:53.852 asynManager::asynConnectCallback, port L0 error calling asynCommon->connect
2007/06/15 15:17:53.852 L0 vxiConnectPort error 172.23.116.185: RPC: Program not registered


2007/06/15 15:17:53.852 L0 -1 autoConnect could not connect
2007/06/15 15:17:53.885 L0 vxiConnectPort error 172.23.116.185: RPC: Program not registered


2007/06/15 15:17:53.968 asynManager::asynConnectCallback, port L0 error calling asynCommon->connect
2007/06/15 15:17:54.868 L0 port not connected


2007/06/15 15:17:58.618 L0 vxi11 clientCall errno 3997698 clnt_stat 0
L0 port not connected
2007/06/15 15:17:58.618 L0 vxiConnectPort vxiBusStatus error initialization aborted
0x1ea12bc0 (L0): memPartFree: invalid block 0x1e247e80 in partition 0x265d1c.



Have people seen something like this before? I'm not sure if the E5810A is widely used or not.


The device itself is fine. The above works OK if I am using a linux IOC. Also, the VxWorks IOC can see the E5810A because it send a reboot command successfully.

Cheers,
Matthew

-- Eric Norum <[email protected]> Advanced Photon Source Argonne National Laboratory (630) 252-4793



Replies:
Re: VXI11 ASYN problem on VxWorks Matthew Pearson
References:
VXI11 ASYN problem on VxWorks Matthew Pearson

Navigate by Date:
Prev: VXI11 ASYN problem on VxWorks Matthew Pearson
Next: RE: EPICS channels via the Internet Elder Matias
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  <20072008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: VXI11 ASYN problem on VxWorks Matthew Pearson
Next: Re: VXI11 ASYN problem on VxWorks Matthew Pearson
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  <20072008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 10 Nov 2011 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·