Error Messages in Numerical Order
0
124
Too many digits
The mantissa of a decimal numeric data element contains more than 255 digits excluding
leading zeros (see IEEE 488.2, 7.7.2.4.1).
0
128
Numeric data not allowed
A legal numeric data element was received, but the analyzer does not accept it in this position
for a header.
0
130
Sux error
This error, as well as errors
0
131 through
0
139, are generated when parsing a sux. This
particular error message is used if the analyzer cannot detect a more specic error.
0
131
Invalid sux
The sux does not follow the syntax described in IEEE 488.2, 7.7.3.2, or the sux is
inappropriate for the analyzer.
0
134
Sux too long
The sux contained more than 12 characters (see IEEE 488.2, 7.7.3.4).
0
138
Sux not allowed
A sux was encountered after a numeric element that does not allow suxes
.
0
140
Character data error
This error, as well as errors
0
141 through
0
148, are generated when analyzing the syntax of a
character data element. This particular error message is used if the analyzer cannot detect a
more specic error.
0
141
Invalid character data
Either the character data element contains an invalid character or the particular element
received is not valid for the header.
0
144
Character data too long
The character data element contains more than twelve characters (see IEEE 488.2, 7.7.1.4).
0
148
Character data not allowed
A legal character data element was encountered where prohibited by the analyzer
.
0
150
String data error
This error, as well as errors
0
151 and
0
158, are generated when analyzing the syntax of a
string data element. This particular error message is used if the analyzer cannot detect a more
specic error.
0
151
Invalid string data
A string data element was expected, but was invalid for some reason (see IEEE 488.2, 7.7.5.2).
For example,an
END
message was received before the terminal quote character.
Messages-23