Agilent Technologies 4349B, Руководство пользователя

Страница: 224 / 233

4349B
-105 GET not allowed
A Group Execute Trigger (GET) was received within a program message (see IEEE 488.2, 7.7).
-108 P arameter not allowed
More parameters were received than expected for the header; for example , the AVER command
only accepts one parameter , so receiving AVER is not allowed.
-109 Missing parameter
F ewer parameters were received than required for the header; for example , the AVER command
requires one parameter , so receiving only AVER is not allowed.
-112 Program mnemonic too long
The header contains more than twelve characters (see IEEE 488.2, 7.6.1.4.1).
-113 Undened header
The header is syntactically correct, but it is undened for the 4349B; for example , *XYZ is not
dened for the 4349B.
-121 Invalid character in number
An invalid character for the data type being parsed was encountered; for example , an alpha
character in a decimal numeric or a \9" in octal data.
-123 Exponent too large
The magnitude of the exponent was larger than 32000 (see IEEE 488.2, 7.7.2.4.1).
-124 T oo 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).
-128 Numeric data not allowed
Legal numeric data element was received, but the 4349B does not accept it in this position for
a header .
-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 4349B.
-138 Sux not allowed
A sux was encountered after a numeric element which does not allow suxes .
-140 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 4349B cannot detect a
more specic error .
Messages-4