Debugging Your Application
Chapter 4
NI-488.2M UM for Windows NT
4-4
© National Instruments Corp.
Debugging with ibic
If your application does not automatically check for and display errors, you can locate an
error by using
ibic
. Simply issue the same functions or routines, one at a time as they
appear in your application program. Because
ibic
returns the status values and error
codes after each call, you should be able to determine which GPIB call is failing. For
more information about
ibic
, refer to Chapter 5, ibic–Interface Bus Interactive Control
Utility .
After you determine which GPIB call is failing and note the corresponding values of the
global variables, refer to Appendix A, Status Word Conditions , and Appendix B, Error
Codes and Solutions. These appendixes can help you interpret the state of the driver.
GPIB Error Codes
Table 4-1 lists the GPIB error codes. Remember that the error variable is meaningful
only when the ERR bit in the status variable is set. For a detailed description of each
error and possible solutions, refer to Appendix B, Error Codes and Solutions.
Table 4-1. GPIB Error Codes
Error
Mnemonic
iberr
Value
Meaning
EDVR
0
System error
ECIC
1
Function requires GPIB board to be CIC
ENOL
2
No Listeners on the GPIB
EADR
3
GPIB board not addressed correctly
EARG
4
Invalid argument to function call
ESAC
5
GPIB board not System Controller as required
EABO
6
I/O operation aborted (timeout)
ENEB
7
Nonexistent GPIB board
EOIP
10
Asynchronous I/O in progress
ECAP
11
No capability for operation
EFSO
12
File system error
EBUS
14
GPIB bus error
ESTB
15
Serial poll status byte queue overflow
ESRQ
16
SRQ stuck in ON position
ETAB
20
Table problem
