HP 53150A Series Programming Manual page 170

Chapter 5 Errors
Error Types
Table 5-2. Errors
Number Error String
+0 No error
-100 Command error
-101 Invalid character
-102 Syntax error
-103 Invalid separator
-104 Data type error
-105 GET not allowed
-108 Parameter not allowed
-109 Missing parameter
-110 Command header error
-111 Header separator error
-112 Program mnemonic too
long
-113 Undefined header
-114 Header suffix out of range
-120 Numeric data error
-121 Invalid character in number
-123 Exponent too large
-124 Too many digits
-128 Numeric data not allowed
-130 Suffix error
5-8
Cause
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.
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).
Programming Guide