BNC 1105 Universal Counter - Manual (Page 89)

89 89 89 89
type. 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 Counter. For example,
*XYZ is not defined for the Counter.
-120 Numeric data error
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.
-121 Invalid character in number
An invalid character for the data type being parsed was encountered. For
example, a “9” in octal 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 Counter does not allow
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 Counter.
-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
suffixes.