Built in VXIpc GPIB under Windows 3.1 has address conflict

["david garavaglia" david.garavaglia]

TROUBLE ADDRESSING VXIpc GPIB using Windows 3.1

David Garavaglia

david.garavaglia@aai-us.com
Voice: (918) 662-7260
FAX: (918) 662-7482




I have a VXIpc-486 Model 200 mother board with a built in GPIB running
Windows 3.1
It seems that the GPIB port has never been used. I need to use this port

now so that I calibrate my VXI instruments using a Fluke 5700.

I got from your web site the GPIB DRIVER ATWIN271.zip and successfully
installed it. Now however, running the GPIB Hardware Diagnostics Program
I keep getting an address conflict error but I can't find what device is
conflicting with GPIB0. I notice the board has a GPIO port and three other
communication ports.

com 1 address is 3F8H
com 2 address is 2F8H
LPT 1 address is 378H

What else do I need to look at? Do I need to upgrade my VXIpc?



BELOW ARE THE PRINTOUTS OF THE DIAGNOSTIC REPORTS FROM THE NI-488.2 ROUTINES.


===================================================================

GPIB Information (Mar 30 1995)
Copyright 1993-1995 National Instruments Corp. All rights reserved.

Software Information:
The NI-488.2 Software for Windows 3 is loaded.
You are running Version 2.7.1.
It supports both the NI-488 functions and NI-488.2 routines.
It supports the HS488 high-speed protocol.

Hardware Information:
GPIB0: AT-GPIB interface using the NAT4882 chip.
It supports both the NI-488 functions and NI-488.2 routines.
It does not support the HS488 high-speed protocol.
It uses base I/O address 0x180.
It uses interrupt level 11.
It uses DMA channel 5 (Demand Mode DMA).






=================================================================


National Instruments GPIB Hardware Diagnostics Program
AT-GPIB, AT-GPIB/TNT, AT-GPIB/TNT+
AT-GPIB/TNT (Plug and Play) and EISA-GPIB
Rev 1.0


The following GPIB board(s) were found in this system:
GPIB0: - AT-GPIB
GPIB1: - AT-GPIB
GPIB2: - AT-GPIB
GPIB3: - AT-GPIB

- test all boards listed above
T - test a single board listed above
O - test a board other than the ones listed above
Q - Quit

Enter selection (T,O,Q,) ->

Testing GPIB0
Base Address: 0x180 IRQ: 11 DMA: 5
..................................................
..................................................
....
<<< Base I/O Address Conflict >>>
ERROR! The board under test failed its verification test.
The most probable causes of failure are:
1. Check if any GPIB cables are connected to the board under
test. If so, remove the cable and run the hardware diagnostics
again.
2. The base address in the 'ni-pnp.ini' file does not match the
switch setting of your board. Check the switch setting again.
3. Another board or built-in device in your computer is using
the same address space. Try a different base I/O address
and run the hardware diagnostics program again.
If you have not fixed the failure with the preceding steps,
refer to the troubleshooting section in the Getting Started manual.

Board failed the hardware diagnostics tests.
R - Run more tests on this board
N - Test the Next Board (if any boards are untested)
M - Return to Main Menu
Q - Quit

Enter choice (Q,M,N,R) ->



==============================================================================




National Instruments NI-488.2 Software Diagnostic Test
Copyright 1994 National Instruments Corporation.
All rights reserved.

This test:
- checks the installation and operation of the NI-488.2 Handler.

- requires no interaction with the user.

- takes approximately 5 seconds per GPIB interface.

DISCONNECT ALL GPIB CABLES FROM ALL GPIB BOARDS


Press return to continue:


<<< Will test GPIB0 >>>
......................................................
NI-488.2 Test on GPIB0 completed successfully.


<<< No interface present for gpib1. >>>

<<< No interface present for gpib2. >>>

<<< No interface present for gpib3. >>>



=======================================================================

[System Info]
NiPnpDocRevisionLevel = 0x0100
IsaPnpSystemType = None
IsaPnpIsolationMethod = IsolationSequence
NiPnpConfiguredIsaPnpCards = Yes
EisaInfoFoundForNiInterfaces = No

[Configure NI-488 GPIB0]
ProductDescription = 0xc00
AddressSpaceType = IO
IoAddresses = 0x0180-0x019f
IRQlevels = 0x0b
DMAchannels = 0x05

[Configure NI-488 GPIB1]
ProductDescription = 0xc00
AddressSpaceType = IO
IoAddresses = 0x0100-0x011f
IRQlevels = 0x09
DMAchannels = 0x06

[Configure NI-488 GPIB2]
ProductDescription = 0xc00
AddressSpaceType = IO
IoAddresses = 0x0280-0x029f

[Configure NI-488 GPIB3]
ProductDescription = 0xc00
AddressSpaceType = IO
IoAddresses = 0x02c0-0x02df

[Current NI-488 GPIB0]
ProductDescription = 0xc00
AddressSpaceType = IO
IoAddresses = 0x0180-0x019f
IRQlevels = 0x0b
DMAchannels = 0x05

[Current NI-488 GPIB1]
ProductDescription = 0xc00
AddressSpaceType = IO
IoAddresses = 0x0100-0x011f
IRQlevels = 0x09
DMAchannels = 0x06

[Current NI-488 GPIB2]
ProductDescription = 0xc00
AddressSpaceType = IO
IoAddresses = 0x0280-0x029f

[Current NI-488 GPIB3]
ProductDescription = 0xc00
AddressSpaceType = IO
IoAddresses = 0x02c0-0x02df

[Randy Solomonson]

I think there's an ibconf utility can be used to configure the GPIB's. The following information was found in the manual for this controller:
I/O Port: 180-19F
IRQ: 11
DMA: 5

So, it looks like the settings for GPIB0 are good, but there are too many GPIB interfaces setup in the driver. Thus this conflict is appearing

Randy Solomonson
Application Engineer
National Instruments