Agilent Technologies 4395A - Page 554

Error
Messages
in
Numerical Order
0
105 GET
not allowed
AGroup
Execute Trigger
(GET) was
received within
a program
message (see
IEEE 488.2,
7.7).
0 108
Parameter
not allowed
More
parameters
were
received than
expected for
the header
.F
or example
,the
*SRE command
only
accepts
one
parameter
,
so
receiving
*SRE 4,16
is not
allowed.
0
109
Missing
parameter
F
ewer
parameters
were
received
than
required
for
the
header
.
F
or
example
,the
*SRE
command
requires
one
parameter
,
so
receiving
only
*SRE
is
not
allowed.
0
110
Command
header
error
An
error
was
detected
in
the
header
.
This
error
message
is
used
when
the
analyzer
cannot
detect
the
more
specic
errors
described
for
errors
0
111
through
0
119.
0
111 Header
separator
error
A
character
that
is
not
a
legal
header
separator
was
encountered
while
parsing
the
header
.
F
or
example
,no
white
space
followed
the
header
,
thus
*SRE4
is
an
error
.
0
112
Program
mnemonic
too
long
The
header
contains
more than
twelve characters
(see
IEEE
488.2,
7.6.1.4.1).
0
113
Undened
header
The
header
is
syntactically
correct,
but
it
is
undened
for
the
analyzer
.
F
or
example
,
*XYZ
is
not
dened
for
the
analyzer
.
0
114
Header
Sux
out
of
range
The
value
of a
numeric sux
attached
to
a
program
mnemonic
makes
the
header
invalid.
0
120
Numeric data
error
This
error
,
as
well
as
errors
0
121
through
0
129,
are
generated
when
parsing
adata
element
that
appears
to
be
numeric
,
including
the
nondecimal
numeric
types
.
This
particular
error
message
is used
if
the
analyzer
cannot
detect
a
more
specic
error
.
0 121 Invalid character in number
An invalid character for the data type being parsed was encountered. F
or example
,
an alpha
character in a decimal numeric or a \9" in octal data.
0 123 Exponent too large
The magnitude of the exponent was larger than 32000 (see IEEE 488.2, 7.7.2.4.1).
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).
Messages-22