Instruction manual

Chapter 5 Errors
Error Types
Programming Guide 5-7
5
Table 5-2. Errors
Number Error String Cause
+0
-100
-101
-102
-103
-104
-105
-108
-109
-110
-111
No error
Command error
Invalid character
Syntax error
Invalid separator
Data type error
GET not allowed
Parameter not allowed
Missing parameter
Command header error
Header separator 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.
An unspecified error was detected in the header.
A character that is not a legal header separator was encountered while
parsing the header.
-112
-113
-114
-120
-121
-123
-124
-128
-130
Program mnemonic too
long
Undefined header
Header suffix out of range
Numeric data error
Invalid character in
number
Exponent too large
Too many digits
Numeric data not allowed
Suffix error
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.
The value of a numeric suffix attached to a program mnemonic makes
the header invalid.
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.
This error can be generated when parsing a suffix. This particular error
message is used if the Counter cannot detect a more specific error
(errors -131 through -139).