Agilent Technologies 4395A, Service Manual

Page: 337 / 343

Error Messages in Numerical Order
0130 Sux error
This error, as w ell as errors 0131 through 0139, are generated when parsing a sux. This
particular error message is used if the analyzer cannot detect a more sp ecic error.
0131 In v alid sux
The sux do es not follow the syn tax describ ed in IEEE 488.2, 7.7.3.2, or the sux is
inappropriate for the analyzer.
0134 Sux to o long
The sux con tained more than 12 c haracters (see IEEE 488.2, 7.7.3.4).
0138 Sux not allow ed
A sux w as encoun tered after a n umeric elemen t that do es not allo w suxes.
0140 Character data error
This error, as w ell as errors 0141 through 0148, are generated when analyzing the syn tax of a
c haracter data elemen t. This particular error message is used if the analyzer cannot detect a
more sp ecic error.
0141 In v alid c haracter data
Either the c haracter data elemen t con tains an in v alid c haracter or the particular elemen t
receiv ed is not v alid for the header.
0144 Character data to o long
The c haracter data elemen t con tains more than t w elv e c haracters (see IEEE 488.2, 7.7.1.4).
0148 Character data not allow ed
A legal c haracter data elemen t w as encoun tered where prohibited b y the analyzer.
0150 String data error
This error, as w ell as errors 0151 and 0158, are generated when analyzing the syn tax of a
string data elemen t. This particular error message is used if the analyzer cannot detect a more
sp ecic error.
0151 In v alid string data
A string data elemen t w as exp ected, but w as in v alid for some reason (see IEEE 488.2, 7.7.5.2).
F or example, an END message w as receiv ed b efore the terminal quote c haracter.
0158 String data not allow ed
A string data elemen t w as encoun tered but w as not allo w ed b y the analyzer at this p oint in
parsing.
Messages-25