Here’s how to debug this by turning on all asynTrace debugging on that port driver:
vxi11Configure("L0", "172.20.92.3", 0, 0.0, "inst0", 0)
asynSetTraceIOMask(“L0”,0,2)
asynSetTraceMask(“L0”,0,255)
Mark
From: [email protected] [mailto:[email protected]]
On Behalf Of Pavel Masloff
Sent: Tuesday, March 20, 2012 9:12 AM
To: EPICS Tech Talk
Subject: Re: [ASYN-vxi11] can't connect to Tektronix scope on Fedora 16
UPDATE:
i can talk to the scope more or less. but what do these error messages mean and where do they come from?? I haven't had such on RHEL...
On Tue, Mar 20, 2012 at 5:47 PM, Pavel Masloff <[email protected]> wrote:
Hello all,
The Tektronix TDS3000/5000 support worked perfectly well on Red Hat Linux 5.5.
Now I have decided to run an IOC on Fedora 16 and here's what I have got:
############################################################################
## EPICS R3.14.12.2 $Date: Mon 2011-12-12 14:09:32 -0600$
## EPICS Base built Mar 14 2012
############################################################################
2012/03/20 17:34:57.555 scopeTest:: queueRequest failed
2012/03/20 17:34:57.556 scopeTest:: queueRequest failed
2012/03/20 17:34:58.057 scopeTest:clearMenuBO queueRequest failed port L0 not connected
2012/03/20 17:34:58.057 scopeTest:initBO queueRequest failed port L0 not connected
2012/03/20 17:34:58.057 scopeTest:frontPanelLockBO queueRequest failed port L0 not connected
2012/03/20 17:34:58.057 scopeTest:ethernetNameSI queueRequest failed port L0 not connected
iocRun: All initialization complete
## Start any sequence programs
epics> 2012/03/20 17:34:58.557 scopeTest:scopeBusyBI queueRequest failed port L0 not connected
2012/03/20 17:34:59.057 scopeTest:scopeBusyBI queueRequest failed port L0 not connected
2012/03/20 17:34:59.557 scopeTest:scopeBusyBI queueRequest failed port L0 not connected
2012/03/20 17:35:00.057 scopeTest:scopeBusyBI queueRequest failed port L0 not connected
2012/03/20 17:35:00.557 scopeTest:scopeBusyBI queueRequest failed port L0 not connected
2012/03/20 17:35:01.057 scopeTest:scopeBusyBI queueRequest failed port L0 not connected
2012/03/20 17:35:01.065 L0 vxi11 clientCall errno Success clnt_stat 5
2012/03/20 17:35:01.065 L0 vxiCreateIrqChannel (create_intr_chan): RPC: Timed out
2012/03/20 17:35:01.065 L0 Warning -- SRQ not operational.
############################################################################
I have double-checked it works on RHEL with version of ASYN, BASE, SNC, etc! What can be the problem with Fedora? I am using epics base 3-14-12-2, ASYN 4-18. And connect to the scope via direct Ethernet connection:
vxi11Configure("L0", "172.20.92.3", 0, 0.0, "inst0", 0)
--
Best regards,
Pavel Maslov, MS
Controls Engineer at Pulsed power Lab
Efremov Institute for Electro-Physical Apparatus
St. Petersburg, Russia
Mobile: +7 (951) 672 22 19
Phone: +7 (812) 461 01 01
--
Best regards,
Pavel Maslov, MS
Controls Engineer at Pulsed power Lab
Efremov Institute for Electro-Physical Apparatus
St. Petersburg, Russia
Mobile: +7 (951) 672 22 19
Phone: +7 (812) 461 01 01