Filter
Top Products
Appendix A Error Messages
List of Errors
Operating and Programming Guide A-7
List of Errors
Table A-2 lists and describes the error messages
Table A-2. Error Messages
Number Error String Cause
+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-on or *CLS.
-100 Command error This is the generic syntax error used if the Receiver 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.
-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 undefined. For example, the command ":HELLO".
-120 Numeric data error This error, as well as errors -121 through -129, is generated when parsing a data
element which appears to be numeric. This particular error message is used when
the Receiver cannot detect a more specific error.
-121 Invalid character in number An invalid character for the data type being parsed was encountered. For example, a
"9" in ocatal data.
-123 Exponent too large Numeric overflow.
-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 Receiver 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 Receiver.
-134 Suffix too long The suffix contained more than 12 characters.
-138 Suffix not allowed A suffix was encountered after a numeric element that does not allow a suffix.
-141 Invalid character data The character data element contains an invalid character.
-148 Character data not allowed A legal character data element was encountered where prohibited by the Receiver.
-150 String data error This error can be generated when parsing a string data element. This particular error
message is used if the Receiver cannot detect a more specific error.
-151 Invalid string data A string data element was expected but was invalid for some reason.
-158 String data not allowed A string data element was encountered but was not allowed by the Receiver at this
point in parsing.
-170 Expression error This error can be generated when parsing an expression data element. It is used if
the Receiver cannot detect a more specific error.