4263B
-221
Setting conflict
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).
-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 4263B
(see IEEE
488.2, 11.5.1.1.5).
-223
Too
much
data
A
legal
program
data
element
of
block,
expression,
or
string
type
was
received
that
contained
more
data
than
the
4263B
could
handle
due
to
memory
or related
device-specic.
-230
Data
corrupt
or
stale
P
ossibly
invalid
data;
new
reading
started
but
not
completed
since
access
.
-241
Hardware missing
A
legal
program
command
or
query
could
not
be
executed
because
of
missing
4263B
hardware;
for
example,
an
option
was
no
installed.
-310
System
error
Some
error
,
termed \system
error" by
the
4263B
,
has
occurred.
-311
Memory
error
An
error
was
detected
in
the
4263B
's
memory
.
-313
Calibration
memory
lost
The
nonvolatile
calibration
data
has
lost.
-350
Queue
overflow
A
specic
code
entered
into
the
queue
in
lieu
of
the
code
that
caused
the
error
. This
code
indicates
that
there
is
no
room
in
the
queue
and
an
error
occurred
but
was
not
recorded.
-400
Query error
This is the generic
query error that the 4263B cannot detect more specic errors
. This code
indicates only that a error
as dened in IEEE 488.2, 11.5.1.1.7 and 6.3 has occurred.
-410
Query INTERRUPTED
A condition causing an interrupted error occurred (see IEEE 488.1, 6.3.2.3); for example
,a
query followed by D
AB or GET before a response was completely sent.
-420
Query UNTERMINATED
A condition causing an unterminated query error occurred (see IEEE 488.2, 6.3.2); for example,
the 4263B was addressed to talk and an incomplete program message was received.
Messages-6