Agilent Technologies 86140B Series, User Manual

Page: 212 / 290

5-13
Status Listings
SCPI-Defined Errors
Device-specific errors
An <error/event number> in the range [–399, –300] or [1, 32767] indicates the
instrument has detected an error which is not a command error, a query error,
or an execution error; some device operations did not properly complete, pos-
sibly 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 reg-
ister (IEEE 488.2, section 11.5.1) 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 (IEEE
–273 desc = “Illegal macro label”
help = ““
[Indicates that the macro label defined in the *DMC command was a legal string
syntax, but could not be accepted by the device (see IEEE 488.2, 10.7.3 and
10.7.6.2); for example, the label was too long, the same as a common command
header, or contained invalid header
–276 desc = “Macro recursion error”
help = ““
[Indicates that a syntactically legal macro program data sequence could not be
executed because the device found it to be recursive (see IEEE 488.2, 10.7.6.6).]
–277 desc = “Macro redefinition not allowed”
help = ““
[Indicates that a syntactically legal macro label in the *DMC command could not
be executed because the macro label was already defined (see IEEE 488.2,
10.7.6.4).]
–278 desc = “Macro header not found”
help = ““
[Indicates that a syntactically legal macro label in the *GMC? query could not be
executed because the header was not previously defined.]
Table 5-2. Execution Errors (3 of 3)
Error Number Error Description [description/explanation/examples]