Error Message Types - Agilent Technologies ESA-E Series User Manual

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.
These errors indicate that the instrument output queue control has
–499 to –400:
Query Errors detected a problem with the message exchange protocol described in
IEEE 488.2, Chapter 6. Errors in this class set the query error bit (bit
2) in the event status register (IEEE 488.2, section 11.5.1). These errors
correspond to message exchange protocol errors described in IEEE
488.2, 6.5. In this case:
• Either an attempt is being made to read data from the output queue
• data in the output queue has been lost.
–399 to –300: These errors indicate that the instrument output queue control has
Device-Specific detected a problem with the message exchange protocol described in
Error Messages IEEE 488.2, Chapter 6. Errors in this class set the query error bit (bit
2) in the event status register (IEEE 488.2, section 11.5.1). These errors
correspond to message exchange protocol errors described in IEEE
488.2, 6.5. In this case:
• Either an attempt is being made to read data from the output queue
• data in the output queue has been lost.
–299 to –200: These errors indicate that an error has been detected during
instrument execution.
Execution Error
Messages
–199 to –100: These errors indicate that the instrument parser detected an IEEE
488.2 syntax error. Errors in this class set the command error bit (bit 5)
Command Errors
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 parser
• an unrecognized header was received. These include incorrect
Chapter 4
when no output is either present or pending, or
when no output is either present or pending, or
(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 is
unacceptable to the device.), or
device-specific headers and incorrect or unimplemented IEEE 488.2
common commands.
Troubleshooting
Error Message Types
4-23