Agilent Technologies 86100A, Programmer'S Manual, Page: 52 / 366

1-48
Introduction
Error Messages
Table 1-10. Error Messages Returned by Instrument Parser (1 of 3)
Error Returned String Description
0 No error The error queue is empty. Every error in the queue has been read (SYSTEM:ERROR?
query) or the queue was cleared by power-up or *CLS.
-100 Command error This is the generic syntax error used if the instrument cannot detect more specific
errors.
-101 Invalid character A syntactic element contains a character that is invalid for that type.
-102 Syntax error An unrecognized command or data type was encountered.
-103 Invalid separator The parser was expecting a separator and encountered an illegal character.
-104 Data type error The parser recognized a data element different than one allowed. For example, numeric
or string data was expected but block data was received.
-105 GET not allowed A Group Execute Trigger was received within a program message.
-108 Parameter not allowed More parameters were received than expected for the header.
-109 Missing parameter Fewer parameters were received than required for the header.
-112 Program mnemonic too long The header or character data element contains more than twelve characters.
-113 Undefined header The header is syntactically correct, but it is undefined for the instrument. For example,
*XYZ is not defined for the instrument.
-121 Invalid character in number An invalid character for the data type being parsed was encountered. For example, a “9”
in octal data.
-123 Numeric overflow Number is too large or too small to be represented internally.
-124 Too many digits The mantissa of a decimal numeric data element contained more than 255 digits
excluding leading zeros.
-128 Numeric data not allowed A legal numeric data element was received, but the instrument does not accept one in
this position for the header.
-131 Invalid suffix The suffix does not follow the syntax described in IEEE 488.2 or the suffix is
inappropriate for the instrument.
-138 Suffix not allowed A suffix was encountered after a numeric element that does not allow suffixes.
-141 Invalid character data Either the character data element contains an invalid character or the particular element
received is not valid for the header.
-144 Character data too long
-148 Character data not allowed A legal character data element was encountered where prohibited by the instrument.
-150 String data error This error can be generated when parsing a string data element. This particular error
message is used if the instrument cannot detect a more specific error.
-151 Invalid string data A string data element was expected, but was invalid for some reason. For example, an
END message was received before the terminal quote character.
-158 String data not allowed A string data element was encountered but was not allowed by the instrument at this
point in parsing.