Filter
Top Products
Common Errors and Their Solutions Appendix B
GPIB-PC User Manual B-8 ©National Instruments Corp.
• All device functions require the board to be Controller-In-
Charge. If it is not, either because it is not System Controller
or because it has passed control away, the function will not
return until control is passed back to the board. If this never
happens, the function will never return. To check the board's
System Controller status, either run IBCONF and verify that the
board is configured to be System Controller, or run IBIC and
execute the function IBRSC with an argument of 1. The
previous value is reported as 1 if the board was System
Controller before your function call. To check that the board
has not passed control, confirm that you never call IBPCT, nor
IBCMD with the Take Control command (9 hex) as an
argument.
Error Condition: The computer crashes.
Solutions:
• Run IBCONF and confirm that the board's DMA channel and
interrupt line match the hardware settings. Also check that the
DMA channel and interrupt line do not conflict with other
devices in the computer.
• Configure the hardware and software to not use DMA and/or
interrupts. You may have a PC compatible that is not totally
compatible.
• Check that none of your device names is the same as any of
your file or directory names, not including the file or directory
name suffix.
Error Condition: IBDIAG reports a DMA or interrupt problem.
Solutions:
• Reconfigure the hardware and software for another DMA
channel and/or interrupt line. You might have a conflict with
another device.
• With the GPIB-PCIIA and GPIB-PCIII, which have shareable
interrupt capability, check that another device on the same line
really has the shareable interrupt capability. Many do not.
• If an interrupt problem persists, configure the hardware and
software for non-DMA or non-interrupt operation. You may
have a PC compatible that is not totally compatible.