4263B
-151
Invalid string
data
A string
data element
was expected,
but was
invalid for
some reason
(see IEEE
488.2,
7.7.5.2);
for example
,an
END
message
was received
before the
terminal
quote
character
.
-158
String
data not
allowed
A
string
data
element
was
encountered
but
was not
allowed by
the 4263B
at this
point
in
the
syntax
analysis
process
.
-160
Block
data
error
This
error
as
well
as
errors
-161
through
-168,
are
generated
when
analyzing
the
syntax of
a
block
data
element.
This
particular
error
message
is
used
if
the 4263B
cannot detect
a more
specic
error
.
-161
Invalid
block
data
A
block
data
element
was
expected,
but
was
invalid
for
some
reason
(see
IEEE
488.2,
7.7.6.2);
for
example,
an
END
message
was
received
before
the
length
was
satised.
-168
Block
data not
allowed
A
legal
block
data
element
was
encountered
but
was
not
allowed
by
the 4263B
at this
point in
the
syntax
analysis
process
.
-170
Expression
error
This
error
as
well
as
errors -171
through
-178,
are
generated
when
analyzing
the
syntax
of
an
expression
data
element.
This
particular
error
message is
used
if
the
4263B
cannot
detect
a
more
specic
error
.
-171
Invalid expression
The
expression
data
element
was
invalid
(see
IEEE
488.2,
7.7.7.2);
for
example
,
unmatched
parentheses
or
an
illegal
character
.
-178
Expression
data
not
allowed
A
legal
expression data
was encountered
but was
not allowed
by
the
4263B
at
this
point
in
the
syntax analysis
process
.
-200
Execution
error
This is the generic syntax error that the 4263B 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.
-211
Trigger ignored
A GET
,
*TRG
, or triggering signal was received and recognized by the 4263B but was ignored
because of
4263B timing considerations
,
n
; for example
, the 4263B was not ready to respond.
-213
Init ignored
A request for a measurement initiation was ignored as another measurement was already in
progress.
Messages-5
To Next Page
Loading...
Need help?
General
