Commands Used For Synchronization - Agilent Technologies 8960 Series Reference Manual

Hide thumbs Also See for 8960 Series:
Table of Contents

Advertisement

Methods for synchronization
The test set's GPIB command set supports the following methods to achieve synchronization for overlapped commands.
In some cases, combinations of these methods will provide the best results:
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.
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.
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.
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 or data connection processing state.
6.
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" on page 293
This command queries the test set's current call processing state. This command supports synchronization
method five. See
"Call Processing State Synchronization" on page
"CALL:STATus" on page 293
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
• :WAIT
This specialized command can be appended to call processing overlapped commands to support
synchronization method two.
See
"Call Processing Subsystem Overlapped Command Synchronization Commands" on page
• :SEQ
This specialized command can be appended to call processing overlapped commands to support
synchronization method one.
See
"Call Processing Subsystem Overlapped Command Synchronization Commands" on page
"INITiate:DONE?" on page 378
This specialized command causes the test set to return a mnemonic indicating if a measurement is done. If
not, the returned mnemonic will indicate if the measurement is still executing. This command supports
synchronization method three.
See
"INITiate:DONE?" on page
• STATUS:<register>
Status bits in the register are provided to indicate the test set's call processing state. These bits support
synchronization methods five and six.
Status bits in the
"STATus:OPERation:NMRReady Register Bit Assignments" on page 460
indicate when a measurement is ready to be fetched. These bits support synchronization method three and
"Call Processing Subsystem Overlapped Command Synchronization
2.
378.
1. This command supports synchronization method five.
S:\Hp8960\E1963A WCDMA\4.0 release\Reference Guide\Chapters\wcdma_prog_sync_gen.fm
Test System Synchronization Overview
1.
2.
2.
are provided to
199

Advertisement

Table of Contents
loading

Table of Contents