Agilent Technologies 4395A, Manual Change

Page: 555 / 575

Error Messages in Numerical Order
0128 Numeric data not allowed
A legal numeric data element was received, but the analyzer does not accept it in this position
for a header .
0130 Sux error
This error , as well as errors 0131 through 0139, are generated when parsing a sux. This
particular error message is used if the analyzer cannot detect a more specic error .
0131 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 .
0134 Sux too long
The sux contained more than 12 characters (see IEEE 488.2, 7.7.3.4).
0138 Sux not allowed
A sux was encountered after a numeric element that does not allow suxes .
0140 Character data error
This error , as well as errors 0141 through 0148, 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 .
0141 Invalid character data
Either the character data element contains an invalid character or the particular element
received is not valid for the header .
0144 Character data too long
The character data element contains more than twelve characters (see IEEE 488.2, 7.7.1.4).
0148 Character data not allowed
A legal character data element was encountered where prohibited by the analyzer .
0150 String data error
This error , as well as errors 0151 and 0158, 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 .
0151 Invalid string data
A string data element was expected, but was invalid for some reason (see IEEE 488.2, 7.7.5.2).
F or example , an END message was received before the terminal quote character .
0158 String data not allowed
A string data element was encountered but was not allowed by the analyzer at this point in
parsing.
Messages-23