YOKOGAWA wt1600 User Manual page 33

4.5 Synchronization with the Controller
Using the COMMunicate:OVERlap command
The "COMMunicate:OVERlap" command is used to
enable or disable overlap operation.
Example
:COMMunicate:OVERlap #HFFBF;:FILE:LOAD:
SETup "FILE1";:INPut:VOLTage:RANGe:
ELEMent1?<PMT>
The "COMMunicate:OVERlap #HFFBF" command
disables overlapped operation of the medium access
command, while enabling all other overlap-type
operations. The oscilloscope will therefore handle
"FILE:LOAD:SETup" s a sequential command,
ensuring that the ":INPut:VOLTage:RANGe:
ELEMent1?" command (in the above example) will not
execute until file loading is completed.
Using the *OPC command
The *OPC command causes the OPC bit (bit 0) of the
standard event register (page 6-3) to be set to "1"
when an overlap operation has been completed.
Example
:COMMunicate:OPSE #H0040;*ESE 1;
*ESR?;*SRE 32;:FILE:LOAD:SETup "FILE1";
*OPC<PMT>
(Response to *ESR? is decoded.)
(Service request is awaited.)
:INPut:VOLTage:RANGe:ELEMent1?<PMT>
The "COMMunicate:OPSE" command is used to
designate which commands are to be subject to the
*OPC command. In the above example, only medium
access commands are designated.
*ESE 1 and *SRE 32 stipulate that a service request
is generated only when the OPC bit is set to "1".
*ESR? is used to clear the standard event register.
In the above example,
":INPut:VOLTage:RANGe:ELEMent1?" will not be
executed until a service request is generated.
4-8
Using the *OPC? query
The *OPC? query generates a response when an
overlap operation has been completed.
Example
:COMMunicate:OPSE #H0040;:FILE:LOAD:
SETup "FILE1";*OPC?<PMT>
(Response to *OPC? is decoded.)
:INPut:VOLTage:RANGe:ELEMent?<PMT>
The "COMMunicate:OPSE" command is used to
designate which commands are to be subject to the
*OPC? command. In the above example, only medium
access commands are designated.
Since *OPC? does not generate a response until an
overlap operation is completed, file loading will have
been completed when a response to *OPC? is read.
Note
Most commands are sequential commands. Commands used in
Chapter 5 are sequential commands unless otherwise specified.
Synchronization with Non-Overlap Commands
Even for sequential commands, synchronization is
sometimes required to correctly query the measured
data.
If you wish to query the newest numerical data on
every time measured data is updated, for example,
sending the ":NUMeric[:NORMal]:VALue?"
command at an arbitrary timing can cause data that is
the same as the previous data to be received. This is
because the WT1600 returns the current measured
data regardless of whether the measured data has
been updated since the previous query.
In this case, the following method must be used to
synchronize with the end of the updating of the
measured data.
Using STATus:CONDition? query
The "STATus:CONDition?" query is used to query
the contents of the condition register (page 6-4). You
can determine whether the measured data is being
updated by reading bit 0 of the condition register. If bit
0 of the condition register is "1," the measured data is
being updated. If it is "0," the measured data can be
queried.
IM 760101-11E