Agilent Technologies 4395A, Service Manual

Page: 336 / 343

Error Messages in Numerical Order
0109 Missing parameter
F ew er parameters w ere receiv ed than required for the header. F or example, the *SRE
command requires one parameter, so receiving only *SRE is not allo w ed.
0110 Command header error
An error w as detected in the header. This error message is used when the analyzer cannot
detect the more sp ecic errors describ ed for errors 0111 through 0119.
0111 Header separator error
A c haracter that is not a legal header separator w as encoun tered while parsing the header.
F or example, no white space follow ed the header, th us *SRE4 is an error.
0112 Program mnemonic to o long
The header con tains more than t w elv e c haracters (see IEEE 488.2, 7.6.1.4.1).
0113 Undened header
The header is syn tactically correct, but it is undened for the analyzer. F or example, *XYZ is
not dened for the analyzer.
0114 Header Sux out of range
The v alue of a n umeric sux attached to a program mnemonic makes the header in v alid.
0120 Numeric data error
This error, as w ell as errors 0121 through 0129, are generated when parsing a data elemen t
that app ears to b e n umeric, including the nondecimal n umeric t yp es. This particular error
message is used if the analyzer cannot detect a more sp ecic error.
0121 In v alid c haracter in n um b er
An in v alid c haracter for the data t yp e b eing parsed w as encoun tered. F or example, an alpha
c haracter in a decimal n umeric or a \9" in o ctal data.
0123 Exp onen t to o large
The magnitude of the exp onent w as larger than 32000 (see IEEE 488.2, 7.7.2.4.1).
0124 T o o man y digits
The man tissa of a decimal n umeric data elemen t con tains more than 255 digits excluding
leading zeros (see IEEE 488.2, 7.7.2.4.1).
0128 Numeric data not allo w ed
A legal n umeric data elemen t w as receiv ed, but the analyzer do es not accept it in this p osition
for a header.
Messages-24