|
|
|
|
Programming a Power versus Time Measurement
Last updated: May 8, 2002
This section contains two programming examples:
Programming a Power versus Time Measurement for GSM
This section provides an example of how to make the power versus time (PvT) measurement via GPIB.
The following procedure assumes that an active link is established between the test set and the mobile station. See
Establishing an Active GSM Link with the Mobile Station
.
-
Configure PvT measurement parameters using the SETup subsystem.
-
Start the PvT measurement using the INITiate subsystem.
-
Use the FETCh? command to obtain PvT measurement results.
Programming Example
10 OUTPUT 714;"SETUP:PVTIME:CONTINUOUS OFF" !Configures a PvT measurement to
20 !single trigger mode.
30 OUTPUT 714;"SETUP:PVTIME:COUNT:NUMBER 100 !Configures a multi-measurment
40 !of 100.
50 OUTPUT 714;"SETUP:PVTIME:TRIGGER:SOURCE AUTO" !Configure trigger source
60 !to auto.
70 OUTPUT 714;"SETUP:PVTIME:SYNC MIDAMBLE" !Configures a PvT measurement so
80 !that burst synchronization, which
90 !will synchronize the time of the
100 !measurement algorithm relative to
110 !the data sample, will be set
120 !to midamble.
130 OUTPUT 714;"SETUP:PVTIME:TIME:OFFSET -28US,-18US" !Turns on time markers
140 !-28 and -18 microseconds.
150 OUTPUT 714;"INITIATE:PVTIME" !Start PvT measurement.
160 OUTPUT 714;"FETCH:PVTIME:ALL?" !PvT results for time measurements.
170 ENTER 714;Integrity,Pvt_mask, Pvt_power, Max_offset1, Max_offset2
180 END
Returned values
The measurements returned by this program are:
Programming a Power versus Time Measurement for GPRS
This section provides an example of how to make the power versus time (PvT) measurement via GPIB.
The following procedure assumes that the Operating Mode has been set to Active Cell (using
CALL:OPERating:MODE
) and the data connection type has been set to ETSI Type B (using
CALL:FUNCtion:DATA:TYPE
). In addition, it is assumed that a data connection has been established between the test set and the mobile station (connection status is Transferring). See
Step 4: Make a connection
.
Note that you can also make power versus time measurements in active cell mode using the BLER and ETSI Type B data connection types (see
CALL:FUNCtion:DATA:TYPE
). Power versus time measurements can also be made when the test set's operating mode is set to GPRS BCH+PDTCH test mode (see
CALL:OPERating:MODE
).
-
Set the multislot configuration to two downlinks, two uplinks (D2U2) and set the uplink power control level for each of the two bursts using the CALL subsystem.
-
Configure PvT measurement parameters using the SETup subsystem.
-
Set the trigger type to single using the SETup subsystem.
-
Start the PvT measurement using the INITiate subsystem.
-
Use the FETCh? commands to obtain PvT measurement results.
Programming Example
10 OUTPUT 714;"CALL:PDTCH:MSLOT:CONFIG D2U2" ! Configures the multislot
20 ! configuration to be
30 ! 2 downlink, 2 uplink.
40 OUTPUT 714;"CALL:PDTCH:MS:TXLEVEL:BURST1 10" ! Sets the uplink power for
50 ! the first burst to 23 dBm.
60 OUTPUT 714;"CALL:PDTCH:MS:TXLEVEL:BURST2 5" ! Sets the uplink power for
70 ! the second burst to 33 dBm.
80 OUTPUT 714;"SETUP:PVTIME:CONTINUOUS OFF" !Configures a PvT measurement to
90 !single trigger mode.
100 OUTPUT 714;"SETUP:PVTIME:COUNT:NUMBER 100" !Configures a multi-measurement
110 !of 100.
120 OUTPUT 714;"SETUP:PVTIME:TRIGGER:SOURCE AUTO" !Configure trigger source
130 !to auto.
140 OUTPUT 714;"SETUP:PVTIME:SYNC MIDAMBLE" !Configures a PvT measurement so
150 !that burst synchronization, which
160 !will synchronize the time of the
170 !measurement algorithm relative to
180 !the data sample, will be set
190 !to midamble.
200 OUTPUT 714;"INITIATE:PVTIME" !Start PvT measurement.
210 ! Fetch all the required PvT results.
220 OUTPUT 714;"FETCH:PVTIME:BURST1:INTEGRITY?" ! Always check integrity values.
230 ENTER 714;Integ_burst1
240 OUTPUT 714;"FETCH:PVTIME:BURST2:INTEGRITY?"
250 ENTER 714;Integ_burst2
260 IF (Integ_burst1=0) AND (Integ_burst2=0) THEN
270 OUTPUT 714;"FETCH:PVTIME:MASK?" !PvT pass/fail result for entire mask
280 ENTER 714;Mask_result
290 OUTPUT 714;"FETCH:PVTIME:MASK:SEGMENT?" ! PvT mask error code. This will
300 ! tell us which parts of the
310 ! uplink has failed the mask.
320 ENTER 714;Mask_error_code
330 OUTPUT 714;"FETCH:PVTIME:BURST1:POWER:AVERAGE?" ! PvT Carrier Power result
340 ! for the first burst.
350 ENTER 714;Pvt_pwr_burst1
360 OUTPUT 714;"FETCH:PVTIME:BURST2:POWER:AVERAGE?" ! PvT Carrier Power result
370 ! for the second burst.
380 ENTER 714;Pvt_pwr_burst2
390 ELSE
400 PRINT "Measurement error: "&Meas_complete$
410 PRINT "Measurement Integrity value for burst 1 = ";Integ_burst1
420 PRINT "Measurement Integrity value for burst 2 = ";Integ_burst2
430 END IF
440 END
Returned values
The measurements returned by this program are:
-
Integ_burst1
and
Integ_burst2
return the measurement integrity values for each of the two adjacent uplink bursts in the multislot configuration (0 means a successful measurement with no errors). See
Integrity Indicator
.
-
Mask_result
returns the mask pass/fail indicator for the entire mask, not an individual burst. When the multi-measurement count is greater than 1, the PvT mask pass/fail result will return Fail (1) if any single measurement fails.
-
Mask_error_code
returns the mask error code for the entire multislot configuration. For more details on how to interpret the value returned by this result, see
FETCh:PVTime:MASK[:FAIL]:SEGment?
.
-
Pvt_pwr_burst1
and
Pvt_pwr_burst2
return the PvT carrier power results in dBm for each of the bursts in the multislot configuration.
Back to Top
|