Concurrent Measurements
Table Key:
Empty cell: No concurrency considerations
A: Cannot operate concurrently. Whichever measurement is activated most recently will cause all other
conflicting measurements to be deactivated.
B: These measurements share a sampler path. If multiple measurements are initiated at same time, the
measurements will execute sequentially. If multiple measurements are configured to operate off of the same
trigger event and only a single occurrence of that event happens, only one measurement will complete (the
first measurement in the sequence of measurements).
C: The test set will not prevent the user from changing the TCH ARFCN or transmit power level while the
measurement is in progress. However, changing the TCH ARFCN or transmit power level while the
measurement is in progress will cause the measurement to start over which will cause the measurement to
take longer to execute.
The only absolute restriction regarding concurrency is that the downlink speech source cannot be used when
the FBER or BER measurements are running. These measurements take absolute control of the downlink
speech source and use it to generate the pseudo-random data. (The test set prevents the user from accessing
the downlink speech source while the FBER or BER measurements are running). Other than this restriction,
multiple measurements can always be initiated with a single program message, and the test set will manage
and report the sequence that measurement results are made available to the controlling application through
the INITiate:DONE? query.
Related Topics
*******************************************************
"Measurement Event Synchronization" on page 132
"Block Diagram" on page 504
*******************************************************
124
S:\Hp8960\E1960A GSM Mobile Test Application\A.04 Release\Reference_Manual\Chapters\prog_gen_concurrent.fm