Commands Used For Synchronization - Agilent Technologies 8960 10 Series Reference Manual

Test System Synchronization Overview
to because subsequent commands are not executed until the previous sequential command is finished. Once
the test set has begun execution of an overlapped command, however, another command or commands may
begin executing, allowing the test set to use its internal resources as efficiently as possible. Overlapped
commands are more difficult to synchronize to because an overlapped operation that started several
commands earlier may still be executing as subsequent commands are being parsed out from the input buffer
and executed. This can present a problem unless the external controller is properly synchronized to the test
set's execution of commands.
The test set's GPIB command set supports the following methods to achieve synchronization. In some cases,
combinations of these methods will provide the best results:
Methods for synchronization
Methods one and two do not require the external controller to query the test set, nor to perform any branching
or decision-making associated with information acquired from the test set.
1. Force the test set to execute overlapped commands sequentially.
2. Force the test set to wait until an overlapped command is done executing before executing any more
commands.
Methods three through six rely on responses from the test set to an external controller, indicating that some
event has occurred. The external controller can then make decisions based on these responses to control the
flow of commands to the test set and other devices in the test system.
3. Query the test set to determine when a command has finished executing.
4. Query the test set to determine when all commands sent to it have at least begun executing.
5. Query the test set to determine the current call processing state.
3. Program the test set to generate a service request when an operation has completed or the test set is in a
certain state

Commands used for synchronization:

• "CALL:STATus[:STATe]?" on page 283
This command queries the test set's current call processing state. This command supports synchronization
method five. (See "Call Processing State Query" on page
• "CALL:CONNected[:STATe]?" on page 240
This command determines the connected/idle state of a call. A feature called the change detector provides
the user with a way to hold off the response to this query until a call processing state transition has taken
place. (See "Connected/Idle Query" on page
• :DONE? and :OPC?
These specialized commands can be appended to call processing overlapped commands to support
synchronization method three. (See
Commands" on page
40
S:\Hp8960\E1960A GSM Mobile Test Application\A.04 Release\Reference_Manual\Chapters\prog_synch_gen.fm
"Call Processing Subsystem Overlapped Command Synchronization
31.)
35).
35). This command supports synchronization method five.