Hello everybody,
I am trying to set-up a GPIB link using the NI-1014-1 VME card. My IOC is
a Motorola MVME147 and my EPICS release is R3.12.2. After configuring the
obvious things as base address and others and "play" a lot with the GPIB driver
in order to produce printouts that can help to solve our problems, we have not
gone any further. We are using the generic GPIB record to communicate with
our multimeter (a Keithley 2010) to start with. We get the following output
messages:
0x3af360 (tShell): Gpib NI1014 driver initializing
0x3af360 (tShell): short_base 0xFFFF0000
0x3af360 (tShell): NIGPIB_SHORT_OFF 0x00005000
0x3af360 (tShell): NIGPIB_NUM_LINKS 0x00000001
0x3af360 (tShell): GPIB card found at address 0xFFFF5000
0x3af360 (tShell): ibLinkInit(00296D28): entered, type 5, link 0, bug -1
0x3af360 (tShell): JAP: GPIB IRQ level: 5
0x3af360 (tShell): JAP: GPIB IVEC base: 00000064
0x3af360 (tShell): JAP: GPIB STD Address Mode: 00000004
0x3af360 (tShell): ibLinkStart(00296D28): entered for linkType 5, link 0
0x3af360 (tShell): JAP: Before calling ioctlIb for IFC...
0x3af360 (tShell): niGpibIoctl(0, 4, -1, 00000000)
0x3af360 (tShell): JAP: After calling ioctlIb for IFC...
0x3af360 (tShell): JAP: Before calling ioctlIb for REN...
0x3af360 (tShell): niGpibIoctl(0, 5, 1, 00000000)
0x3af360 (tShell): JAP: After calling ioctlIb for REN...
0x3af360 (tShell): writeIbCmd(00296D28, 00367710, 1)
0x3af360 (tShell): niGpibCmd(0, 0x00367710, 1): command string ><
0x3af360 (tShell): JAP: Polling GPIB address 1...
0x3af360 (tShell): pollIb(0x00296D28, 1, 1, 5)
0x3af360 (tShell): readIb(00296D28, 1, 0x003AF000, 3)
0x3af360 (tShell): writeIbCmd(00296D28, 003AEFAA, 4)
0x3af360 (tShell): niGpibCmd(0, 0x003AEFAA, 4): command string ><
0x3af360 (tShell): niGpibRead(0, 0x003AF000, 3, 5)
0x3af360 (tShell): Got a bouncer at 0x002943F4
0x3af360 (tShell): PhysIO: readying to xlate cc pointers at 00296C60 and
002943F6
0x3af360 (tShell): PhysIO: &cc_byte=00A96C60,
&pNiLink[link]->A24BounceBuffer[cnt-1]=00A943F6, 0x3af360 (tShell):
&cc_array=00A96C54, 0x3af360 (tShell): pNiLink[link]->A24BounceBuffer=00A943F4
0x3af360 (tShell): PhysIO: JAP: After niWrLong...
0x3af360 (tShell): PhysIO: JAP: After wdStart...
0x3af360 (tShell): PhysIO: JAP: After enabling interrupts...
interrupt: GPIB error interrupt generated on link 0
interrupt: ch0: ccr=10 csr=01 cer=00 mtc=0002 mar=00A943F4 btc=FDFF bar=00000000
interrupt: ch1: ccr=08 csr=93 cer=0B mtc=FFFF mar=FFFFFFFF btc=0002 bar=00000000
logTask: 3 log messages lost.
0x3af360 (tShell): PhysIO: JAP: Before vxMemProbe...
0x3af360 (tShell): PhysIO: JAP: After vxMemProbe...
0x3af360 (tShell): DMA timing: error = 0, total = 0, max = 0
0x3af360 (tShell): PhysIO: JAP: After b->ch0.ccr...
0x3af360 (tShell): DMA timing: error = 0, total = 0, max = 0
0x3af360 (tShell): PhysIO: JAP: After b->imr2...
0x3af360 (tShell): DMAC error initialization on link 0.
0x3af360 (tShell): writeIbCmd(00296D28, 003AEFAA, 2)
0x3af360 (tShell): niGpibCmd(0, 0x003AEFAA, 2): command string >_?C <
0x3af360 (tShell): pollIb(0, 1): data read error
0x3af360 (tShell): JAP: Polling GPIB address 2...
0x3af360 (tShell): pollIb(0x00296D28, 2, 1, 5)
0x3af360 (tShell): readIb(00296D28, 2, 0x003AF000, 3)
0x3af360 (tShell): writeIbCmd(00296D28, 003AEFAA, 4)
0x3af360 (tShell): niGpibCmd(0, 0x003AEFAA, 4): command string ><
0x3af360 (tShell): niGpibRead(0, 0x003AF000, 3, 5)
0x3af360 (tShell): PhysIO: readying to xlate cc pointers at 00296C60 and
002943F6
0x3af360 (tShell): PhysIO: &cc_byte=00A96C60,
&pNiLink[link]->A24BounceBuffer[cnt-1]=00A943F6, 0x3af360 (tShell):
&cc_array=00A96C54, 0x3af360 (tShell): pNiLink[link]->A24BounceBuffer=00A943F4
0x3af360 (tShell): PhysIO: JAP: After niWrLong...
0x3af360 (tShell): PhysIO: JAP: After wdStart...
00x3af360 (tShell): PhysIO: JAP: After enabling interrupts...
interrupt: GPIB error interrupt generated on link 0
interrupt: ch0: ccr=00 csr=01 cer=00 mtc=0002 mar=00A943F4 btc=FDFF bar=00000003
interrupt: ch1: ccr=08 csr=93 cer=0B mtc=FFFF mar=FFFFFFFF btc=0002 bar=00000003
0x3af360 (tShell): PhysIO: JAP: Before vxMemProbe...
0x3af360 (tShell): PhysIO: JAP: After vxMemProbe...
0x3af360 (tShell): DMA timing: error = 0, total = 0, max = 0
0x3af360 (tShell): PhysIO: JAP: After b->ch0.ccr...
0x3af360 (tShell): DMA timing: error = 0, total = 0, max = 0
0x3af360 (tShell): PhysIO: JAP: After b->imr2...
0x3af360 (tShell): DMAC error initialization on link 0.
0x3af360 (tShell): writeIbCmd(00296D28, 003AEFAA, 2)
0x3af360 (tShell): niGpibCmd(0, 0x003AEFAA, 2): command string ><
0x3af360 (tShell): pollIb(0, 2): data read error
0x3af360 (tShell): JAP: Polling GPIB address 3...
0x3af360 (tShell): pollIb(0x00296D28, 3, 1, 5)
0x3af360 (tShell): readIb(00296D28, 3, 0x003AF000, 3)
0x3af360 (tShell): writeIbCmd(00296D28, 003AEFAA, 4)
0x3af360 (tShell): niGpibCmd(0, 0x003AEFAA, 4): command string
>me/epics/appSA/ioc/lsbvme2/st_gpib.cmdmv147<
0x3af360 (tShell): niGpibRead(0, 0x003AF000, 3, 5)
0x3af360 (tShell): PhysIO: readying to xlate cc pointers at 00296C60 and
002943F6
0x3af360 (tShell): PhysIO: &cc_byte=00A96C60,
&pNiLink[link]->A24BounceBuffer[cnt-1]=00A943F6, 0x3af360 (tShell):
&cc_array=00A96C54, 0x3af360 (tShell): pNiLink[link]->A24BounceBuffer=00A943F4
0x3af360 (tShell): PhysIO: JAP: After niWrLong...
0x3af360 (tShell): PhysIO: JAP: After wdStart...
0x3af360 (tShell): PhysIO: JAP: After enabling interrupts...
0x3af360 (tShell): PhysIO: JAP: Before vxMemProbe...
0x3af360 (tShell): PhysIO: JAP: After vxMemProbe...
0x3af360 (tShell): DMA timing: error = 0, total = 0, max = 0
0x3af360 (tShell): PhysIO: JAP: After b->ch0.ccr...
0x3af360 (tShell): DMA timing: error = 0, total = 0, max = 0
0x3af360 (tShell): PhysIO: JAP: After b->imr2...
0x3af360 (tShell): DMAC error initialization on link 0.
0x3af360 (tShell): writeIbCmd(00296D28, 003AEFAA, 2)
0x3af360 (tShell): niGpibCmd(0, 0x003AEFAA, 2): command string ><
0x3af360 (tShell): pollIb(0, 3): data read error
0x3af360 (tShell): writeIbCmd(00296D28, 00367712, 1)
0x3af360 (tShell): niGpibCmd(0, 0x00367712, 1): command string ><
0x3af360 (tShell): JAP: After polling all available addresses...
0x3af360 (tShell): JAP: Before spawing task to manage link...
0x294264 (ib-00): ibLinkTask started for link type 5, link 0
0x294264 (ib-00): writeIbCmd(00296D28, 003674A8, 2)
0x294264 (ib-00): niGpibCmd(0, 0x003674A8, 2): command string >?_<
0x294264 (ib-00): niSrqIntEnable(0): ch0.csr = 0x09, gsr=0xFFFFFFFF
00x3af360 (tShell): JAP: After spawing task to manage link. ibLinkStart
exiting...
0x3af360 (tShell): niGpibIoctl(0, 8, 0, 00000000)
0x3af360 (tShell): niGpibIoctl(0, 9, 0, 00291648)
0x3af360 (tShell): iocInit: All initialization complete
value = 0 = 0x0
Done executing startup script
/export/home/epics/appSA/ioc/lsbvme2/st_gpib.cmdmv147
->
(messages containing the string JAP are our own debugging)
Our instruments is in address 3.
Any idea why I get the error messages:
interrupt: GPIB error interrupt generated on link 0
and also
DMAC error initialization on link 0 ?
Do I need to setup the NI-1014 DMA AM jumpers?
Has anyone used successfully the NI-1014 card such that I can know where
my problem comes from?
Any help is more than welcome.
Josep Perlas
--
_________________________________________________________________
Dr. Josep A. Perlas - Head of Control System and Power Technology
Lab. Sincrotro Barcelona - IFAE -------- Tel: (+34 3)581.28.38
Edifici Cn, Campus UAB ------------ Fax: (+34 3)581.19.38
E-08193 Bellaterra (Barcelona) SPAIN ---- email: [email protected]
_________________________________________________________________
- Navigate by Date:
- Prev:
Re: EPICS Channel Access in Python. Noboru Yamamoto
- Next:
Re: NI-1014 help needed Ned Arnold
- 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:
DB initialization ? Marian ZUREK
- Next:
Re: NI-1014 help needed Ned Arnold
- 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
|