Table of Contents
Advertisement
3.5 Synchronization with the
Controller
The TA720 does not support overlap commands,
which allows the execution of the next command to
start before the execution of the previous command is
completed. If multiple sequential commands are sent
consecutively, the execution of the next command is
held until the execution of the previous command is
completed.
Achieving Synchronization
Synchronization is sometimes required for reasons
other than communications-related reasons, such as
the activation of a trigger, even if a sequential
command is used.
For example, if a "next program" message is
transmitted to make an inquiry about the waveform
data which has been acquired using single mode as
the trigger mode, the "MEMory:SEND?" command is
sometimes executed whether acquisition has been
completed or not, causing a command execution error.
:SSTart;:MEMory:SEND?<PMT>
In this case, the following method must be used to
synchronize with the end of the acquisition.
• Using the STATus:CONDition? query
The "STATus:CONDition?" query is used to query
the contents of the condition register (page 5-4). It
is possible to judge whether acquisition is in
progress or not by reading bit 0 of the condition
register. Bit 0 is "1" if acquisition is in progress, and
"0" if acquisition is stopped.
Example
:SSTart<PMT>
:STATus:CONDition?<PMT>
(Read the response. If bit 0 is 0, repeat
this command until it becomes 1.)
:MEMory:SEND?<PMT>
The :MEMory:SEND? command will not be
executed until bit 0 of the condition register is set to
"1."
IM 704510-17E
3.5 Synchronization with the Controller
• Using the extended event register
The changes in the condition register can be
reflected in the extended event register (page 5-4).
:STATus:FILTer1 RISE;:STATus:
Example
EESE 1;EESR?;*SRE8;SSTart<PMT>
(Wait for a service request occurrence)
:MEMory:SEND?<PMT>
The "STATus:FILTer1 RISE" command sets the
transition filter so that bit 0 (FILTer1) of the
extended event register is set to "1" when bit 0 of
the condition register changes from "0" to "1."
The ":STATus:EESE 1" command is used to
reflect only bit 0 of the extended event register to
the status byte.
The "STATus:EESR?" command is used to clear
the extended event register.
The "*SRE" command is used to generate a service
request solely on the cause of the extended event
register.
The ":MEMory:SEND?" command will not be
executed until a service request is generated.
• Using the COMMunicate:WAIT command
The "COMMunicate:WAIT" command halts
communications until a specific event is generated.
Example
:STATus:FILTer1 RISE;:STATus:
EESR?;:SSTart<PMT>
(Read the response to STATus:EESR?)
:COMMunicate:WAIT 1;:MEMory:
SEND?<PMT>
For a description of "STATus:FILTer1 RISE" and
"STATus:EESR?" see the previous section
regarding the extended event register.
The "COMMunicate:WAIT 1" command indicates
that the program will wait for bit 0 of the extended
event register to be set to "1."
The :MEMory:SEND? command will not be
executed until bit 0 of the extended event register is
set to "1."
3
3-7
Advertisement
Table of Contents
