Appendix B. RF Test Cases of the TC-3000C
224
5.2.7 Modulation Characteristics (TRM/CA/07/C)
Goal
Verification of the modulation index
Parameters
1. Test mode: Transmitter test, Loop back.
Note. The test case cannot be executed in Null packets Test mode.
2. BT channels are the TX frequency channels of the DUT, which are selected to test. The
frequency for each channel is calculated as (2402+ch) MHz, where ch is the frequency
channel. The frequency channel is the value from 0 to 78. Any quantity of the frequency
channels can be selected in the TC-3000C. The list of selected channels must be
separated by “-“. For instance, the record “0-20-40-60” means that the test case must be
executed for four frequency channels: 0, 20, 40 and 60, that is for the frequencies
2402MHz, 2422MHz, 2442MHz and 2462MHz.
3. Packet type parameter specifies which packet type will be used for the test case. If the
parameter is equal to ‘longest’ then the tester will read LMP features of the DUT and the
longest supported packet will be chosen for the test case.
4. Number of packets parameter specifies how many packets will be used to calculate
modulation characteristics.
5. Hopping mode parameter specifies which hopping sequence will be used for the test.
Allowed values of the parameter are:
1 - single frequency (hopping is off)
79 - hopping is on
If the flag “Use Default” is selected then all of displayed values of parameters are ignored and
the listed above values will be assigned automatically:
Test/Normal mode: Transmitter
BT channels: 0-39-78
Packet type: longest
Number of packets: 10
Hopping mode: 1 (Hopping is off)
Additional test conditions
Whitening is disabled.
Test Procedure
1. If the DUT is not connected then the tester creates connection via access procedures
(paging and inquiry if necessary).
2. The tester will activate test mode (if the test mode is not activated yet) and will set all
necessary parameters of the test mode depending on the Test Mode, Packet type and
Hopping mode parameters.
3. The tester checks whether the DUT transmits at maximum power. If not and the DUT
supports power control, then the tester will consecutively send LMP_incr_power_req
requests until the LMP_max_power response would be received from the DUT. The time
delay between two consequential LMP_incr_power_req requests depends on the
Pow.SetTime parameter (to modify the value use: Menu Configuration DUT
More3/5 Pow.SetTime, default value is equal to 1 second).