Agilent Technologies ESA-E Series Programmer's Manual page 343

Error Messages
Error Message Types
Error Message Types
Events do not generate more than one type of error. For example, an
event that generates a query error will not generate a device-specific ,
execution, or command error .
- 499 to
-400 : These errors indicate that the instrument output queue control ha s
Query Errors detected a problem with the message exchange protocol described i n
IEEE 488 .2, Chapter 6. Errors in this class set the query error bit (bi t
2) in the event status register (IEEE 488 .2, section 11 .5 .1). These errors
correspond to message exchange protocol errors described in IEE E
488 .2, 6.5. In this case :
• Either an attempt is being made to read data from the output queu e
when no output is either present or pending, or
• data in the output queue has been lost .
-399 to -300: These errors indicate that the instrument output queue control ha s
Device-Specific
detected a problem with the message exchange protocol described i n
Error Messages IEEE 488 .2, Chapter 6 . Errors in this class set the query error bit (bi t
2) in the event status register (IEEE 488 .2, section 11 .5 .1). These errors
correspond to message exchange protocol errors described in IEE E
488.2, 6.5. In this case :
• Either an attempt is being made to read data from the output queue
when no output is either present or pending, o r
• data in the output queue has been lost .
-299 to -200 :
These errors indicate that an error has been detected during
Execution Error
instrument execution .
Message s
- 199 to -100 :
These errors indicate that the instrument parser detected an IEE E
Command Errors 488.2 syntax error. Errors in this class set the command error bit (bit 5)
in the event status register (IEEE 488 .2, section 11 .5.1) . In this case :
• Either an IEEE 488 .2 syntax error has been detected by the parse r
(a control-to-device message was received that is in violation of the
IEEE 488 .2 standard . Possible violations include a data element
which violates device listening formats or whose type i s
unacceptable to the device .), or
• an unrecognized header was received . These include incorrect
device-specific headers and incorrect or unimplemented IEEE 488 .2
common commands .
Chapter 7 7-15