National Instruments NI-488.2 - Manual (Page 108)

Appendix C Error Codes and Solutions
NI-488.2 User Manual C-4 ni.com
Solutions
Possible solutions for this error are as follows:
• Make sure that the GPIB address of your device matches the GPIB
address of the device to which you want to write data.
• Use the appropriate hex code in ibcmd to address your device.
• Check your cable connections and make sure at least two-thirds of
your devices are powered on.
• Call ibconfig with the IbcPAD (or IbcSAD , if necessary) options to
match the configured address to the device switch settings.
EADR (3)
EADR occurs when the GPIB interface is CIC and is not properly
addressing itself before read and write functions. This error is usually
associated with board-level functions.
EADR is also returned by the function ibgts when the shadow-handshake
feature is requested and the GPIB ATN line is already unasserted. In this
case, the shadow handshake is not possible and the error is returned to
notify you of that fact.
Solutions
Possible solutions for this error are as follows:
• Make sure that the GPIB interface is addressed correctly before calling
ibrd , ibwrt , RcvRespMsg , or SendDataBytes .
• Avoid calling ibgts except immediately after an ibcmd call.
( ibcmd causes ATN to be asserted.)
EARG (4)
EARG results when an invalid argument is passed to a function call.
The following are some examples:
• ibconfig with the IbcTMO option called with a value not in the range
0 through 17.
• ibconfig with the IbcEOS option called with meaningless bits set in
the high byte of the second parameter.
• ibconfig with the IbcPAD or IbcSAD option called with invalid
addresses.