Debugging Your Application
Chapter 4
NI-488.2M UM for Windows NT
4-2
© National Instruments Corp.
You should also see one or more lines similar to the following:
Device
Status
Started
GPIB Port Driver (AT-GPIB)
****
System
GPIB Port Driver (MC-GPIB)
****
System
The
GPIB Board Class Driver
and the
GPIB Device Class Driver
should both have a status of
Started
. If not, refer to the next section, Examining the
NT System Log Using the Event Viewer .
At least one of the GPIB Port Drivers listed by the Devices applet should have a status of
Started
. If not, refer to the next section, Examining the NT System Log Using the
Event Viewer .
If the GPIB Class Driver lines are not present or at least one GPIB Port Driver line is not
present, the NI-488.2M software is not installed properly. You must reinstall the
NI -488.2M software.
Examining the NT System Log Using the Event Viewer
Windows NT maintains a system log. If the NI-488.2M driver is unable to start, it
records entries in the system log explaining why it failed to start. You can examine the
system log by running the Event Viewer utility in the Administrative Tools window of
the Program Manager . Events that might appear in the system log include the
following:
•
The system is unable to locate the device file f or one or more of the devices that
make up the NI-488.2M driver and an event is logged that
The system cannot
find the file specified
. In this case, the NI-488.2M software is
incorrectly installed. You should reinstall the software.
•
A conflict exists between the GPIB hardware and the other hardware in the system.
If this is the case, an event is logged that indicates the nature of the resource conflict.
To correct this conflict, reconfigure the GPIB hardware and NI-488.2M software.
Refer to the getting started manual that came with your GPIB board.
GPIB Cables Connected
The following error messages appear if a GPIB cable is connected to the board when you
run
ibtest
.
Call(25) 'ibcmd " "' failed, ibsta (0x134) not what was expected
(0x8130)
Call(25) 'ibcmd " "' failed, expected ibsta (0x100) to have the
ERR bit set.
Disconnect all GPIB cables before trying the test again.
