The error message you're seeing:
2009/07/23 13:28:10.304 L0 vxiCreateIrqChannel VXI: channel not
established (create_intr_chan)
is coming from vxiCreateIrqChannel(). The error status is being
reported by the ICS 8065. The 8065 is reporting a failure of the
create_intr_chan remote procedure call. Here's the code from the asyn
VXI-11 driver.
clntStat = clientCall(pvxiPort, create_intr_chan,
(const xdrproc_t) xdr_Device_RemoteFunc, (void *) &devRemF,
(const xdrproc_t) xdr_Device_Error, (void *) &devErr);
if(clntStat != RPC_SUCCESS) {
asynPrint(pasynUser,ASYN_TRACE_ERROR,
"%s vxiCreateIrqChannel (create_intr_chan)%s\n",
pvxiPort->portName,clnt_sperror(pvxiPort->rpcClient,""));
xdr_free((const xdrproc_t) xdr_Device_Error, (char *) &devErr);
clnt_destroy(pvxiPort->rpcClient);
} else if(devErr.error != VXI_OK) {
asynPrint(pasynUser,ASYN_TRACE_ERROR,
"%s vxiCreateIrqChannel %s (create_intr_chan)\n",
pvxiPort->portName, vxiError(devErr.error));
xdr_free((const xdrproc_t) xdr_Device_Error, (char *) &devErr);
clnt_destroy(pvxiPort->rpcClient);
} else {
vxiSrqEnable(pvxiPort,1);
xdr_free((const xdrproc_t) xdr_Device_Error, (char *) &devErr);
return;
}
The error message indicates that the remote procedure call itself
succeeded (i.e. that clntStat == RPC_SUCCESS) but that the remote
device (the ICS 8065) reported a failure. My guess is that it has a
limited number of channels available and you've run out after four
restarts.
Have you tried issuing a reset to the ICS 8065 before starting the
IOC? The asyn VXI-11 driver provides reboot commands for the Agilent
E2050 and E5810 devices. Perhaps something similar could be done for
the ICS 8065?
On Jul 23, 2009, at 4:50 PM, Szalata, Zenon M. wrote:
I put these two commands in my st.cmd file:
asynSetTraceMask( "L0",10,0xff)
asynSetTraceIOMask( "L0",10,0x2)
I assume that I did what you suggested. I am not sure what is
traceIOMask=255?
This is what I did:
1. Reboot the gateway,
2. Start IOC. I get many trace messages.
3. Restart the IOC until it fails. It failed on the fourth
restart. This time I got not one trace message.
4. I repeated the above and again on the fourth restart it failed.
Seems that some resource is being exhausted.
Thanks,
Zen
-----Original Message-----
From: Mark Rivers [mailto:[email protected]]
Sent: Thursday, July 23, 2009 2:06 PM
To: Szalata, Zenon M.; [email protected]
Subject: RE: Vxi11
One suggestion would be to set asynTraceIOMask=2 and traceIOMask=255
for that asynPort in your startup script. Then reboot the IOC until
it fails and see if you can what is different in the traffic.
Mark
-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Szalata, Zenon M.
Sent: Thursday, July 23, 2009 4:03 PM
To: [email protected]
Subject: Vxi11
I am using ICS 8065 Ethernet - GPIB gateway. The soft IOC is built
with EPICS R3.14.9, asyn version 4.11, streamdevice version 2.4.
Sometime when I restart the IOC it dies with the following error:
########################################################################
####
## EPICS R3.14.9-ilc3 $R3-14-9$ $2007/02/05 16:31:45$ ## EPICS Base
built Mar 2 2009
########################################################################
####
2009/07/23 13:28:10.304 L0 vxiCreateIrqChannel VXI: channel not
established (create_intr_chan)
2009/07/23 13:28:10.304 L0 Warning -- SRQ not operational.
@@@ @@@ @@@ @@@ @@@
@@@ Received a sigChild for process 29220. The process was killed by
signal 11 @@@ Current time: Thu Jul 23 13:28:10 2009
I don't understand these error messages. I need to understand in
what way the gateway is failing so that I can explain my problem
more intelligently to the tech support at ICS. So, my question is
how to interpret the messages listed above?
Are there other users of the ICS 8065 gateway? Has anyone seen this
problem? If so what is the solution?
Thanks,
Zen
--
Eric Norum <[email protected]>
Advanced Photon Source
Argonne National Laboratory
(630) 252-4793
- References:
- Vxi11 Szalata, Zenon M.
- RE: Vxi11 Mark Rivers
- RE: Vxi11 Szalata, Zenon M.
- Navigate by Date:
- Prev:
RE: Vxi11 Szalata, Zenon M.
- Next:
Re: Waveform record updating problem Prachi Chitnis
- 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:
RE: Vxi11 Szalata, Zenon M.
- Next:
Re: --more-- Waveform record updating problem Prachi Chitnis
- 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
|