Filter
Top Products
Chapter 5 Errors
Error Queue
Programming Guide 5-7
Table 5-2. Errors
Number Error String Cause
+0
-100
-101
-102
-103
-104
-105
-108
-109
-112
-113
-120
-121
-123
-124
-128
-131
-134
-138
-141
-148
-150
No error
Command error
Invalid character
Syntax error
Invalid separator
Data type error
GET not allowed
Parameter not allowed
Missing parameter
Program mnemonic too long
Undefined header
Numeric data error
Invalid character in number
Exponent too large
Too many digits
Numeric data not allowed
Invalid suffix
Suffix too long
Suffix not allowed
Invalid character data
Character data not allowed
String data 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.
This is the generic syntax error used if the Counter cannot detect more
specific errors.
A syntactic element contains a character that is invalid for that type.
For example, a header containing an ampersand, :INP:COUP& AC.
An unrecognized command or data type was encountered.
The parser was expecting a separator and encountered an illegal
character.
The parser recognized a data element different than one allowed.
For example, numeric or string data was expected, but block data was
received.
A Group Execute Trigger was received within a program message.
More parameters were received than expected for the header.
Fewer parameters were received than required for the header.
The header or character data element contains more than twelve
characters.
The header is syntactically correct, but it is undefined for the Counter.
For example, *XYZ is not defined for the Counter.
This error, as well as errors -121 through -129, are generated when
parsing a data element which appears to be numeric, including the
non-decimal numeric types. This particular error message is used when
the Counter cannot detect a more specific error.
An invalid character for the data type being parsed was encountered.
For example, a “9” in octal data.
Numeric overflow.
The mantissa of a decimal numeric data element contained more than
255 digits excluding leading zeros.
A legal numeric data element was received, but the Counter does not
accept one in this position for the header.
The suffix does not follow the syntax described in IEEE 488.2 or the suffix
is inappropriate for the Counter.
The suffix contained more than 12 characters.
A suffix was encountered after a numeric element that does not allow
suffixes.
The character data element contains an invalid character.
A legal character data element was encountered where prohibited by the
Counter.
This error can be generated when parsing a string data element.
This particular error message is used if the Counter cannot detect a more
specific error.