Status and Events
Synchronizat
ion Methods
Overview
Although most commands are completed almost immediately after being received
by the oscilloscope, some commands start a process that requires time. For
example, onc
e a single sequence acquisition command is executed, depending
upon the applied signals and trigger settings, it may take an indeterminate amount
of time b efore the acquisition is complete. Rather than remain idle while the
operation is in process, the oscilloscope will continue processing other commands.
This means that some operations will no t be completed in the order that they
were sent.
Sometimes the result of an operation depends on the result of a n earlier operation.
A first operation must complete before the next one is processed. The oscilloscope
status and event reporting system is designed to accommodate this process.
The Operation Complete (OPC) bit of the Standard Event Status Register (SESR)
can be programmed to indicate when certain oscilloscope operations have
completed and, by setting the E vent Status Enable Register (ES
ER) to report
OPC in the Event Status Bit (ESB) of the Status Byte Register (SBR) and setting
the Service Request Enable Register (SRER) to generate service request upon a
positive transition of the ESB, a service request (SRQ) interrupt can be generated
when certain operations comple te as described in this section.
The following oscilloscope operations can generate an OPC:
:ACQuire:STATE<non-zeronr1>|ON|RUNonlywheninsinglesequence
acquisition mode
:CALibrate:FACtory STARt
:CALibrate:FACtory CONTinue
:CALibrate:FACtory PREVious
:HARDCopy
:HARDCopy START
:DIAg:STATE EXECute
:SAVe:IMAGe <file as quoted string>
:SAVe:SETUp <file as quoted string>
:RECAll:SETUp <file as quoted string>
:SAVe:WAVEform <source wwfm>,(<REF1-REF4> | <file as quoted string>
:RECAll:WAVEform <ISF file as quoted string>,<REF1-REF4>
:CH<1-4>:PRObe:DEGAUss EXECute
:CH<1-4>:PRObe:AUTOZero EXECute
TEKSecure
MSO2000B, DPO2000B, MSO2000 and DPO2000 Series Oscilloscopes Programmer Manual 3-7