Tektronix 2221 - STATUS BYTES AND EVENT CODES; Option 10 and Option 12 Status Reporting

Options and Accessories - 2221 Operators
STATUS BYTES AND EVENT CODES
П
П
П
П
O
It is not
necessary to
wait for an
SRQ . The
instrument
will
return the status byte code for STA ? status bytes pending
and an event code for EVE ? for events waiting to be
reported ( or a for no events to report ) .
The
various
status
events
and
errors
that
can occur are
divided into
several
categories as defined
Table 7-34 .
Table 7-35 lists the event codes that are returned as the
result
of
an
EVEnt
?
query
.
Option
12
Option
10
If there is more than one event of different priority
levels to be reported , the oscilloscope reasserts SRQ until
it reports all events of different priority . It does not issue
an SRQ for
duplicate events
pending or for more
than one
event of the same priority level . Each event is automati
cally cleared when its status byte is reported . The con
troller
option
can
clear all
events
by
repeatedly
sending the
EVEnt ? query until a zero status byte is returned . The
Device Clear ( DCL )
interface
message may be
used to
clear
all
events
,
except
the
power
-
on
event
.
If there is more than one event of different priority lev .
els to be reported , the oscilloscope has a status byte and
event code available for each one . It does not report dupli
cate events or more than one event of the same priority
level . Each event is automatically cleared when its status
byte or event code is reported . The Device Clear ( DCL )
interface message may be used to clear all events , except
the power - on event . Querying EVEnt ? until the return is
EVE clears all pending status bytes and there is no
power
-
on
event
.
1
П
П
on
П
1
With
RQS set
OFF , all
service
requests
(
except
the
power - on SRQ ) are prevented . With the service requests
turned off , the
EVEnt ?
query must be
sent to the
oscillo
scope so that the controller can determine the oscilloscope
and event status . The controller may address the oscillo
scope and send the STAtus ? or EVEnt ? query at any time .
With RQS
set OFF ,
all
service
requests are
prevented .
With the
service
requests
turned
off ,
the
EVEnt ?
query
must be sent to the oscilloscope so that the controller can
determine the oscilloscope and event status . The controller
may send the EVEnt ? query at any time , and the instru
ment will
return the
code for
an event
waiting
to
be
reported ( or a for no events to report ) . The controller can
clear all events by repeatedly sending the EVEnt ? query
until a zero status byte is returned .
Table 7-34
Status
Event and
Error
Categories
Category
Status
Byte Description
Command Error
97 or 113
The instrument received a command that it cannot understand .
Execution
Error
98 or 114
The
instrument
received a
command that it
cannot execute
.
This
is
caused by
either out - of
-
range
arguments or
settings
that conflict .
П
Internal Error
99 or 115
System
Events
65-67 and 81-83
Execution
Error
Warning
101 or
117
The instrument detected a hardware condition or a firmware
problem that prevents operation .
Events common to instruments in a system ( e.g. , Power - on
and
User
Request ) .
The
instrument
received a
command and
is
executing it ,
but a
potential problem may exist . For example , the instrument is out
of
range
,
but is
sending
a
reading anyway .
The
instrument
detected
a
problem
. It
remains
operational
, but
the problem should be corrected ( e.g. , out of calibration ) .
Device - dependent events .
Internal
Warning
102 or 118
Device Status
O or 16 ,
193-238
, and
209-254
1
П
C
7-47