Agilent Technologies 4395A - Page 556

Error
Messages
in
Numerical Order
0
160 Block
data error
This error
,as
well as
errors 0
161 and
0 168,
are generated
when
analyzing
the
syntax
of
a
block data
element. This
particular error
message is
used if
the
analyzer
cannot
detect
a
more
specic error
.
0 161
Invalid block
data
A
block
data
element
was
expected,
but
was invalid
for some
reason (see
IEEE 488.2,
7.7.6.2).
F
or
example
,
an
END
message
was received
before the
length was
satised.
0
168
Block
data not
allowed
A
legal
block
data
element
was
encountered
but
was
not
allowed by
the analyzer
at this
point
in
parsing.
0
200
Execution
error
This
is
the
generic
syntax
error
that
the
analyzer
cannot
detect
more
specic
errors
.
This
code
indicates
only that
an
execution
error
as
dened
in
IEEE
488.2,
11.5.1.1.5
has
occurred.
0 201
- 0
300
0
210
Trigger
error
A trigger
related
error
occurred.
This
error
message
is
used
when
the
analyzer
cannot
detect
the more
specic
errors
described
for
errors
0
211
through
0
219.
0
211
Trigger
ignored
A
GET
,
*TRG
,
or
triggering
signal
was received
and
recognized
by
the
analyzer
but
was
ignored
because
of
analyzer
timing
considerations
.
F
or
example,
the analyzer
was
not
ready
to
respond.
0
213
Init
ignored
A
request for
a
measurement
initiation
was
ignored
as
another
measurement
was
already
in
progress
.
0
220
P
arameter
error
Indicates
that a
program data
element related
error occurred.
This error
message is
used when
the
analyzer cannot
detect
the
more
specic
errors
described
for
errors
0
221
through 0
229.
0
221 Settings conict
A legal program data element was
parsed but could not be executed due to the current device
state (see IEEE 488.2, 6.4.5.3 and
11.5.1.1.5).
0 222 Data out of range
A legal program data element was parsed but could not be executed because the interpreted
value was outside the legal range as dened by the analyzer (see IEEE 488.2, 11.5.1.1.5).
Messages-24