Programmer’s Guide
13-15
SCPI Error Messages
Device-Specific Errors
Device-Specific Errors
An error/event number in the range
−
399 to
−
300 or 1 to 32767 indicates
that the instrument has detected an error which is not a command error,
a query error, or an execution error. It indicates that some device
operations did not properly complete, possibly due to an abnormal
hardware or firmware condition. These codes are also used for self-test
response errors. The occurrence of any error in this class should cause
the device-specific error bit (bit 3) in the event status register to be set.
The meaning of positive error codes is device-dependent and may be
enumerated or bit mapped; the error message string for positive error
codes is not defined by SCPI and available to the device designer. Note
that the string is not optional; if the designer does not wish to implement
a string for a particular error, the null string should be sent (for example,
42). The occurrence of any error in this class should cause the
device-specific error bit (bit 3) in the event status register to be set.
Events that generate device-specific errors shall not generate command
errors, execution errors, or query errors; see the other error definitions in
this section.
Summary of Contents for 8712ES
Page 11: ...1 1 1 Introduction to GPIB Programming ...
Page 27: ...2 1 2 Synchronizing the Analyzer and a Controller ...
Page 36: ...3 1 3 Passing Control ...
Page 39: ...4 1 4 Data Types and Encoding ...
Page 46: ...5 1 5 Using Status Registers ...
Page 71: ...6 1 6 Trace Data Transfers ...
Page 98: ...6 28 Programmer sGuide Trace Data Transfers Internal Measurement Arrays ...
Page 99: ...7 1 7 Using Graphics ...
Page 105: ...8 1 8 Front Panel Keycodes ...
Page 111: ...9 1 9 Introduction to SCPI ...
Page 129: ...10 1 10 Menu Map with SCPI Commands ...
Page 268: ...12 1 12 SCPI Conformance Information ...
Page 290: ...13 1 13 SCPI Error Messages ...