Professional Documents
Culture Documents
CMW Bluetooth UserManual V3-8-20 en 39
CMW Bluetooth UserManual V3-8-20 en 39
R&S®CMW-KS60x/-KS61x/-KS72x
Bluetooth® Firmware Applications
User Manual
(;×îÍ2)
1173966302
User Manual
Version 39
This user manual describes the following R&S®CMW options:
● R&S®CMW-KD611 (Bluetooth® LE R4.2 advertiser RX measurement with ARB generator)
● R&S®CMW-KD720 (Bluetooth® LE 5.0 direct test mode with ARB generator)
● R&S®CMW-KM610 (Bluetooth® classic R4.2, TX measurement)
● R&S®CMW-KM611 (Bluetooth® LE R4.2, TX measurement)
● R&S®CMW-KM721 (Bluetooth® LE R5, TX measurement)
● R&S®CMW-KM722 (Bluetooth® LE R5.1, direction finding, TX measurement)
● R&S®CMW-KM012 (TX measurement, multi-evaluation list mode)
● R&S®CMW-KS600 (Bluetooth® classic R4.2, signaling, connection setup)
● R&S®CMW-KS601 (Bluetooth® LE R4.2, signaling, connection setup)
● R&S®CMW-KS602 (Bluetooth® hands-free audio profile, basic signaling)
● R&S®CMW-KS603 (Bluetooth® A2DP audio profile, basic signaling)
● R&S®CMW-KS610 (Bluetooth® classic R4.2, signaling, test mode)
● R&S®CMW-KS611 (Bluetooth® LE R4.2, direct test mode via USB)
● R&S®CMW-KS720 (Bluetooth® LE R5, signaling, connection setup)
● R&S®CMW-KS721 (Bluetooth® LE R5, direct test mode via USB)
● R&S®CMW-KS722 (Bluetooth® LE R5.1, direction finding, RX measurement)
The following abbreviations are used throughout this manual: R&S®CMW is abbreviated as R&S CMW.
R&S®CMW-KM61x/-KM72x/-KDxxx R&S®CMW-KS60x/-KS61x/-KS72x Contents
Contents
1 Preface.................................................................................................... 9
1.1 Documentation Overview............................................................................................. 9
1.1.1 Getting Started Manual / Quick Start Guide....................................................................9
1.1.2 User Manual and Help.................................................................................................... 9
1.1.3 Features & Functions...................................................................................................... 9
1.1.4 Basic Safety Instructions...............................................................................................10
1.1.5 Data Sheet and Brochure..............................................................................................10
1.1.6 Release Notes and Open-Source Acknowledgment (OSA)..........................................10
1.1.7 Application Notes, Application Cards, White Papers, etc..............................................10
1.2 R&S CMW Models....................................................................................................... 10
1.3 How to Read Firmware Application Chapters.......................................................... 11
1.3.1 General Description.......................................................................................................11
1.3.2 Application Sheets.........................................................................................................11
1.3.3 GUI Reference...............................................................................................................11
1.3.4 Programming Examples................................................................................................12
1.3.5 Command Reference.................................................................................................... 12
2 Bluetooth® Signaling........................................................................... 13
2.1 What's New.................................................................................................................. 13
2.2 General Description.................................................................................................... 13
2.2.1 Overview of Options......................................................................................................14
2.2.2 Test Setup..................................................................................................................... 15
2.2.3 Initiating Signaling Tests (Classic).................................................................................19
2.2.4 Connection Test (Classic)............................................................................................. 20
2.2.5 Test Mode (Classic).......................................................................................................21
2.2.6 Audio Profiles (BR/EDR)............................................................................................... 23
2.2.7 Connection Test (LE).....................................................................................................26
2.2.8 Test Mode (LE)..............................................................................................................27
2.2.9 Direct Test Mode (LE)................................................................................................... 28
2.2.10 Bluetooth Signal Characteristics................................................................................... 30
2.2.11 Signaling States............................................................................................................ 36
2.2.12 Trigger Signals.............................................................................................................. 40
3 Rx BER Measurement........................................................................213
3.1 Performing a BER Rx Measurement........................................................................213
3.2 GUI Reference........................................................................................................... 214
3.2.1 Tab Overview.............................................................................................................. 214
3.2.2 Measurement Control..................................................................................................216
3.2.3 Measurement Results................................................................................................. 216
3.2.4 Measurement Settings................................................................................................ 218
3.3 Programming.............................................................................................................220
3.3.1 Configuring a BER Measurement............................................................................... 220
3.3.2 Setting Up the Connection.......................................................................................... 221
3.3.3 Performing a BER Measurement................................................................................ 221
3.4 Command Reference................................................................................................ 221
3.4.1 Conventions and General Information........................................................................ 222
3.4.2 Measurement Control and States............................................................................... 226
3.4.3 Measurement Settings................................................................................................ 228
3.4.4 Measurement Results................................................................................................. 230
3.5 List of Commands.....................................................................................................232
5 Rx BER/PER Search...........................................................................258
5.1 Performing BER/PER Search Rx Measurements................................................... 258
5.2 GUI Reference........................................................................................................... 259
5.2.1 Tab Overview.............................................................................................................. 259
5.2.2 Measurement Control..................................................................................................261
5.2.3 Measurement Results................................................................................................. 262
5.2.4 Measurement Settings................................................................................................ 263
5.3 Programming.............................................................................................................270
5.3.1 Configuring a BER/PER Search Measurement...........................................................270
5.3.2 Setting Up the Connection.......................................................................................... 271
5.3.3 Performing a BER/PER Search Measurement........................................................... 271
5.4 Command Reference................................................................................................ 272
5.4.1 Conventions and General Information........................................................................ 272
5.4.2 Measurement Control and States............................................................................... 272
5.4.3 Measurement Settings................................................................................................ 275
5.4.4 Measurement Results................................................................................................. 282
5.5 List of Commands.....................................................................................................287
Index....................................................................................................714
1 Preface
● Documentation Overview.......................................................................................... 9
● R&S CMW Models.................................................................................................. 10
● How to Read Firmware Application Chapters......................................................... 11
Separate user manuals are provided for the base unit and the firmware applications:
● The base unit manual describes the base software and common features of the
firmware applications. It also describes basic principles for manual operation and
remote control. The manual includes the contents of the getting started manual or
quick start guide.
● Additional documents, like this one, describe the firmware applications, including
the graphical user interface of each application and the remote control commands.
All user manuals are available on the CMW customer web.
The contents of the user manuals are also available as help in the R&S CMW. The
help offers quick, context-sensitive access to the information needed for operation and
programming. If you perform a software update, the help is also updated.
The features & functions documents list the available software options and the related
features, settings and measurement results. The documents are available on the CMW
customer web.
The data sheet contains the technical specifications of the R&S CMW. It also lists the
options and their order numbers and optional accessories.
The brochure provides an overview of the instrument and deals with the specific char-
acteristics.
For download, refer to the internet page of your instrument model, for example
www.rohde-schwarz.com/brochure-datasheet/CMW500.
The release notes list new features, improvements and known issues per software ver-
sion and installation package.
The open-source acknowledgment provides verbatim license texts of the used open-
source software.
The documents are available on the CMW customer web.
The RF ports are built into a radio test head. The test software is running on a con-
nected computer. All tests are performed as non-signaling tests.
● R&S CMW500/2xx: Stands for the R&S CMW500, 270 and 290.
The instrument provides RF ports and contains a computer where the test software
is running. Combined signal path measurements are possible.
● R&S CMW100/CMW with MUA: R&S CMW with advanced measurement board:
– Any R&S CMW100 contains an advanced measurement board.
– An R&S CMW500/270/290 can be equipped with a measurement unit
advanced (MUA, R&S CMW-B100H) and 160-MHz TX/RX modules (R&S
CMW-B570H).
● R&S CMW500/2xx with BB Meas: R&S CMW with baseband measurement unit.
An R&S CMW500/270/290 can be equipped with a baseband measurement unit
(BB Meas, R&S CMW-B100A/D).
3. GUI reference
4. Programming examples
5. Command reference
This optional chapter provides short application examples for selected issues and rela-
ted background information.
The GUI reference describes the manual operation of the firmware application via the
graphical user interface (GUI).
The description of a configuration dialog usually starts with a screenshot presenting the
preset values of the parameters. Sometimes, preset values are modified to enable hid-
den parts of a dialog. Below the screenshot, all shown parameters are described. For
each single parameter, a link to the corresponding command description in the com-
mand reference is provided. Ranges for numeric parameters and reset values are
given there.
For measurement results, links to the corresponding command descriptions are provi-
ded (commands to retrieve the results).
The programming examples show how to control and configure the firmware applica-
tion via a remote-control program and how to retrieve measurement results. The exam-
ples consist of comprehensive command sequences. You can check just a single com-
mand of a sequence to get an example for the syntax of this single command. But you
can also consider an entire sequence showing the commands in the context of a com-
mand script, under consideration of dependencies and required orders of the com-
mands.
The command sequences are written with the intention to list most commands of the
firmware application. They do not show the fastest way for a given configuration task.
The fastest way would use many reset values and omit the corresponding commands.
The examples are referenced by the command descriptions of the command refer-
ence.
The command reference provides information on the remote commands of the firm-
ware application. The commands are grouped according to their function.
Each command description indicates the syntax of the command header and of the
parameters. For input parameters, the allowed ranges, reset values and default units
are listed. Most commands have a command form and a query form. Exceptions are
marked by "Setting only", "Query only" or "Event". Furthermore, a link to the program-
ming examples is provided and the first software version supporting the command is
indicated.
2 Bluetooth® Signaling
The "Bluetooth Signaling" firmware application generates a Bluetooth signal and
attempts a connection to the equipment under test (EUT). Once a connection is estab-
lished, various properties of the connected device can be retrieved.
Three basic signaling options are available:
● R&S CMW-KS600 for Basic Rate (BR) and Enhanced Data Rate (EDR)
● R&S CMW-KS601 for Low Energy (LE) connection tests and LE test mode on
LE 1 Msymbol/s uncoded physical layer (LE 1M PHY)
● R&S CMW-KS611 for direct test mode on LE 1M PHY.
Additional options extend the basic options, see Chapter 2.2.1, "Overview of Options",
on page 14.
The "Bluetooth Signaling" application provides also Rx tests. For details, refer to:
● Chapter 3, "Rx BER Measurement", on page 213
● Chapter 4, "Rx PER Measurement", on page 233
● Chapter 5, "Rx BER/PER Search", on page 258
● Chapter 6, "Rx Direction Finding", on page 289
● The basic signaling functionality provided by R&S CMW-KS600 for basic rate (BR)
and enhanced data rate (EDR) signals can be enhanced by the following options:
– R&S CMW-KS602 "Bluetooth hands-free audio profile, basic signaling"
Extendable by R&S CMW-KS603 "Bluetooth A2DP audio profile, basic signal-
ing"
– R&S CMW-KS610 "Bluetooth classic version 4.2, signaling, test mode"
● The basic signaling option R&S CMW-KS601 "Bluetooth LE version 4.2, signaling,
connection setup". The option supports low energy (LE) 1 Msymbol/s uncoded
physical layer (LE 1M PHY).
This option provides also a proprietary test mode connection over the air (OTA).
Test mode for LE only works after the particular FW update of the DUT.
– The option can be enhanced by R&S CMW-KS720 "Bluetooth LE version 5.0,
signaling, connection setup"
A signaling unit advanced (SUA) is required.
● The basic signaling signaling option R&S CMW-KS611 "Bluetooth LE version 4.2,
direct test mode via USB". The option supports LE 1M PHY (uncoded).
– To support LE 2 Msymbol/s uncoded physical layer (LE 2M PHY) and LE
1 Msymbol/s long range physical layer (LE coded PHY), it can be enhanced by
R&S CMW-KS721 "Bluetooth LE version 5.0, direct test mode via USB"
– Extendable by R&S CMW-KS722 "Bluetooth LE version 5.1, direction finding"
Tx tests can be performed using the Bluetooth multi-evaluation measurement.
● Measurements for BR and EDR are included in the option R&S CMW-KM610.
● Option R&S CMW-KM611 provides LE multi-evaluation measurements on uncoded
LE 1M PHY for Bluetooth v 5.0 signals.
● Option R&S CMW-KM721 extends multi-evaluation measurements for uncoded
LE 2M PHY and LE coded PHY measurements.
● Option R&S CMW-KM722 provides LE multi-evaluation measurements on uncoded
LE 1M PHY and LE 2M PHY for LE with CTE signals.
The following sections provide an overview of typical test setups for the individual
tests.
● Tests without USB Interface.................................................................................... 15
● Tests with USB Interface......................................................................................... 16
● Test with Multiple EUT's Antennas (LE with CTE).................................................. 17
● Audio Tests (BR/EDR).............................................................................................18
The equipment under test (EUT) is connected to one of the bidirectional RF COM con-
nectors at the front panel of the R&S CMW. No additional cabling and no external trig-
ger are needed. The input level ranges of all RF COM connectors are identical.
The bidirectional RF connection between the tester and the EUT carries both the
downlink and the uplink signal.
● For BR and EDR, the R&S CMW implements a master or a slave device.
The master R&S CMW performs inquiry and paging, connect / connect test mode
operations, representing the piconet master.
The slave EUT must be brought to page scan mode while the master R&S CMW is
paging to make a connection possible. Inquiry scan mode is a prerequisite for
being discoverable but not required for establishing a connection.
The slave mode of R&S CMW is only possible if Operating Mode is set to "Profile",
see "Operating Mode" on page 66. The slave R&S CMW becomes discoverable
and expects the EUT to connect as a master. Some EUTs require to be connected
to the R&S CMW in advance, in order to store a pairing information before con-
necting as a master.
● For LE signaling connection (option R&S CMW-KS601/-KS720), the R&S CMW
implements a central or peripheral device.
The central R&S CMW performs inquiry, paging to make a connection possible. It
scans during the connection, looking for advertisement. The central role is required
for LE test mode.
A device in the peripheral role makes the advertisement.
● For LE in direct test mode (option R&S CMW-KS611/-KS721), the test is started
manually at the EUT. The R&S CMW sends several test packets to the EUT.
This test setup is suitable for tests with USB interface, testing BR, EDR and LE bursts.
In addition to the bidirectional RF connector as used in the Tests without USB Inter-
face, the R&S CMW uses a secondary communication channel via USB for control
commands.
The installation of a USB driver is necessary on the R&S CMW. The installation differs
for direct USB connections and connections with a USB to RS232 adapter.
For the first time, the setup file must be executed manually on the R&S CMW as fol-
lows:
1. Open the Windows Explorer (Windows sign + E).
2. Execute the hciusb.msi file stored in the default "Program Files" direc-
tory ...\Rohde-Schwarz\CMW\3.8\RS.bluetooth_sig\drivers.
Verify that the driver is properly installed on the R&S CMW as follows:
1. Open the device manager (Windows sign + D to show the desktop, Start > Control
Panel > Device Manager).
2. Find your USB to RS232 adapter under Ports (COM & LPT), for example, ATEN
USB to Serial Bridge (COM4). The COM port number depends on the connected
USB port.
Note that the "Virtual COM Port" used by the "Bluetooth Signaling" application has
different numbering than the COM port assigned during the installation of the USB-
to-serial driver.
This test setup is suitable for direct test mode for LE with constant tone extension
(CTE):
● Angle of arrival (AoA) LE measurements, where the R&S CMW simulates a receiv-
ing device with several Rx antennas (antenna array), but only one RF connector is
used.
● Angle of departure (AoD) LE measurements in combined signal path with Blue-
tooth measurement application.
An RF splitter is required to connect the antenna array of the EUT to one RF port of the
R&S CMW. The antenna array of the EUT must include one reference and one non-
reference antenna. Additional two non-reference antennas are optional.
In addition to the bidirectional RF COM connector, the R&S CMW controls direct test
mode via USB using communication protocol HCI.
The Bluetooth signaling application controls direct test mode and Bluetooth measure-
ment application performs Tx measurements in combined signal path.
This test setup is suitable for operating mode audio and profile (audio profiles hands-
free, hands-free audio gateway, and A2DP).
In addition to the bidirectional RF COM connector as used in the Tests without USB
Interface or Tests with USB Interface, the R&S CMW uses also audio connections. The
format of audio signal is configurable as digital routed to SPDIF connectors or analog
routed to AF connectors.
Connect the DUT with the audio connectors provided by the R&S CMW with an instal-
led audio board. Select the connectors according to the performed audio test. Refer to
the user manual of the "Audio Measurement" application for the test setup instructions.
The following figure shows an example of a mono speaker test using analog audio sig-
nal routed to AF1 IN connector.
As with any other R&S CMW signaling application, the "Bluetooth Signaling" applica-
tion is started using the ON|OFF key. It starts up in the standby state with no RF signal
being generated. In the standby state, initiate state changes manually.
Inquiry
Press the "Inquire" hotkey to have the R&S CMW discover the DUTs and collect their
device addresses and clocks.
The inquiry automatically stops after a configurable amount of time or if a configurable
maximum number of devices was discovered. It can also be stopped manually at any
time.
The inquiry is not required if the USB connection is established or if a default device is
used.
Default Device
To speed up the connection setup, a default device can be configured. This device can
be paged without a preceding inquiry.
Paging
Press one of the "Connect..." hotkeys to have the master (the R&S CMW) establish a
Bluetooth connection with the DUT slave device. In the intermediate page state, the
master tries to coincide with the slave's scan activity by repeatedly transmitting the
paging message. With the information stored during inquiry, the master can predict on
which hop channel the slave starts page scanning. This channel information speeds up
the completion of the connection.
If successful, the ACL link is established and the properties of the connected device
are displayed in the "Info" and "Capabilities" pane. If unsuccessful, the R&S CMW
reverts to the standby state after a configurable "Page Timeout".
Required Settings
The default settings of the R&S CMW generally ensure a master signal with suitable
characteristics for connection setup.
For connections without USB, ensure that the DUT is discoverable before pressing the
"Inquire" hotkey on the R&S CMW. Similarly, the DUT must be page scan activated
before you press one of the "Connect..." hotkeys. Before paging the default device,
make sure its device address (and page scan repetition mode) matches.
The physical properties of the RF connection and input path can be modified in the
main window and the configuration dialog with the following settings:
● The RF connectors to be used ("RF Routing") and the "External Attenuation" to be
applied
● The power of the generated signal ("TX Level (CMW)")
5. Open the "Bluetooth Signaling" firmware application and press [ON | OFF] until the
"Bluetooth Signaling" control softkey indicates the "ON" state.
8. ● For a connection to the default device, set its BD address and the page scan
repetition mode. Continue from step 11.
● Otherwise ensure that the DUT is discoverable by enabling inquiry scan mode
and then press the "Inquire" button. Wait for the DUT to be found and its BD
address to be displayed in the "BD Address" dialog that pops up on the screen.
9. Wait for the inquiry process to finish or press "Stop Inquiry" at any time to return to
the standby state.
10. Select the target device in the "For Paging" field. If the R&S CMW does not find
any device during the inquiry, you can only select the default device.
11. Press "Connect" and wait until the "Connection Status" pane indicates the signaling
state "Connected".
12. Details about the DUT can be seen in the "EUT Info" and "EUT Capabilities" pane,
see:
● Chapter 2.3.1.2, "Connection Status Tab - EUT Info", on page 44 and
● Chapter 2.3.1.3, "Connection Status Tab - EUT Capabilities", on page 45
The DUT is connected via RF cable. Optionally, the secondary communication channel
can be realized via USB interface, see Chapter 2.2.2, "Test Setup", on page 15.
BR/EDR test mode is defined in the specification for Bluetooth wireless technology,
core system package: volume 2, part C and volume 3, part D.
The following tests are possible in test mode:
5. Set the burst type to BR or EDR. See "Burst Type (classic)" on page 69.
6. Discover the EUT. See the steps 5 to 10 of the procedure for connection tests
("Executing Connection Tests" on page 20).
7. Activate test mode at the DUT. See "Enable Test Mode (Classic)" on page 71.
8. Set the test mode to loopback. See "Test Mode (classic)" on page 69.
9. Press "Connect Test Mode" and wait for status to change to "Connected Test-
mode".
11. Press "Detach" to exit test mode and disconnect from the DUT.
over, the poll period, the packet type for test packets and the length of the test
sequence can be set, see figure below.
Executing TX Tests
Proceed as follows:
1. Connect your Bluetooth device to the R&S CMW. For the test setup, refer to Chap-
ter 2.2.2, "Test Setup", on page 15.
3. Set the burst type to BR or EDR. See "Burst Type (classic)" on page 69.
4. Set the operating mode to test mode. See "Operating Mode" on page 66.
5. Discover the DUT. See the steps 5 to 10 of the procedure for connection tests
("Executing Connection Tests" on page 20).
6. Activate test mode at the DUT. See "Enable Test Mode (Classic)" on page 71.
7. Set test mode to TX test. See "Test Mode (classic)" on page 69.
8. Press "Connect Test Mode" and wait for status to change to "Connected Test-
mode".
10. Press "Detach" to exit test mode and disconnect from the DUT.
Hands-free audio profile testing is performed using the "Audio Measurement" firmware
application of the R&S CMW.
This connection allows you, to feed an audio signal into an RF connection to the DUT
or to extract an audio signal from the RF connection for audio measurements. You can,
for example, connect the R&S UPV to the audio board of the R&S CMW and perform a
speech quality analysis.
The audio board contains a speech codec board, providing an interface to the signaling
units of the R&S CMW. It decodes the signal delivered by the "Bluetooth Signaling"
application or encodes an audio signal and delivers it to the "Bluetooth Signaling"
application.
The speech codec allows the "Bluetooth Signaling" application to support the whole
transmission chain of the audio signal. In particular, from analog input into the EUT's
microphone through the RF via a Bluetooth connection link, to the output of the AF sig-
nal or vice versa. The format of audio signal is configurable as digital (SPDIF) or ana-
log (AF connectors).
Required options:
● The audio board must be enhanced with a speech codec board (R&S CMW-
B405A).
● The latest audio firmware/software package "Setup_CMW_AUDIO.exe" must be
installed on the R&S CMW. This firmware application sends audio to and receives
audio from the "Bluetooth Signaling" application and performs audio measure-
ments.
● Option R&S CMW-KS600 is required for audio mode.
● Option R&S CMW-KS602 is required for audio profiles hands-free and hands-free
AG.
● Option R&S CMW-KS603 is required for audio profile A2DP.
The supported scenarios of audio measurements are listed in the following table:
1) only mono
2) external audio analyzer like the R&S UPV required
The procedure outlined below is an example of audio measurements with the "Blue-
tooth Signaling" application. Refer to the user manual of the "Audio Measurement"
application for more detailed information. See also Chapter 2.2.2.4, "Audio Tests (BR/
EDR)", on page 18.
To set up an audio connection using profile A2DP, perform the following steps:
1. Connect the EUT with the audio connectors provided by the R&S CMW with an
installed audio board. Select the connectors according to the performed test. Refer
to the user manual of the "Audio Measurement" application for the test setup
instructions.
5. Specify speech codec. See "Voice Link > Speech Codec (BR/EDR only)"
on page 94.
If CVSD, A-law, or μ-law coding is selected, the SCO connection is used. For
mSBC codec, the eSCO connection is used.
6. Configure audio profile settings in accordance with the EUT configuration and
capabilities. See Audio Profiles Settings.
a) Configure authentication parameters "PIN Code", "Security Mode", and "Call is
Active at Startup".
b) Specify the following A2DP-specific parameters: "Sampling Frequency", "Chan-
nel Mode", "Block Bands", "Sub-Bands", "Allocation Method", and "Minimum/
Maximum Bitpool".
7. Configure any other required settings (as for a connection without the audio board)
and switch on the "Bluetooth Signaling".
8. Press the "Audio Measurement" softkey, see Chapter 2.3.3, "Using the Shortcut
Softkeys", on page 64.
10. In the "Audio Measurement", select the "Bluetooth Signaling" as a controlling mas-
ter application to which the speech codec is connected ("Controlled by" setting).
The "Audio Measurement" selects the coupled signaling application and the "Blue-
tooth Signaling" is connected to the speech codec.
11. Discover the EUT. See the steps 5 to 10 of the procedure for connection tests
("Executing Connection Tests" on page 20).
12. Connect the hands-free profile. (Press "Connect HFP, HFP AG, or A2DP" hotkey.)
Wait for status to change to connected.
13. Turn on the internal audio generator of the "Audio Measurement" application.
The "Audio Measurement" generates audio signal and sends it to the "Bluetooth
Signaling" application.
15. Analyze the audio signal, for example, using the "Audio Measurement" application.
The Bluetooth TX measurements evaluate the different characteristics of the signal
as well.
4. Open the "Bluetooth Signaling" firmware application and press [ON | OFF] until the
"Bluetooth Signaling" control softkey indicates the "ON" state.
6. ● For central LE role, configure the DUT into advertising mode (connectable).
● For peripheral LE role, configure the DUT into central mode.
7. ● For a connection with the default device, set its address. See "Default EUT
Address" on page 90. Continue from step 9.
● Otherwise ensure that the DUT is discoverable by enabling inquiry scan mode
and then press the "Inquire" button. Wait for the DUT to be found and its
address to be displayed in the "Address" dialog that pops up on the screen.
8. Wait for the inquiry process to finish or press "Stop Inquiry" at any time to return to
the standby state.
Details about the DUT can be seen in the "EUT Info" pane, see Chapter 2.3.1.2,
"Connection Status Tab - EUT Info", on page 44.
9. Select the target device in the For Paging field. If the R&S CMW does not find any
device during the inquiry, you can only select the default device.
10. Press "Connect" and wait until the "Connection Status" pane indicates the signaling
state "Connected".
11. ● To perform RX tests, press the "RX Meas." softkey, see also Chapter 4, "Rx
PER Measurement", on page 233 and Chapter 5, "Rx BER/PER Search",
on page 258.
Signaling connection for LE (option R&S CMW-KS601) requires SUA. LE test mode is
a special over-the-air (OTA) connection, that requires a firmware update of the DUT.
The R&S CMW works in central LE role.
2. Connect your Bluetooth device to the R&S CMW. For the test setup, refer to Chap-
ter 2.2.2, "Test Setup", on page 15.
3. Make the configuration parameters of the test mode visible. Refer to "Test Mode
Available" on page 90.
6. Open the "Bluetooth Signaling" firmware application and press [ON | OFF] until the
"Bluetooth Signaling" control softkey indicates the "ON" state.
8. ● For a connection with the default device, set its address. See "Default EUT
Address" on page 90. Continue from step 9.
● Otherwise ensure that the DUT is discoverable by enabling inquiry scan mode
and then press the "Inquire" button. Wait for the DUT to be found and its
address to be displayed in the "Address" dialog that pops up on the screen.
9. Wait for the inquiry process to finish or press "Stop Inquiry" at any time to return to
the standby state.
Details about the DUT can be seen in the "EUT Info" pane, see Chapter 2.3.1.2,
"Connection Status Tab - EUT Info", on page 44.
10. Select the target device in the For Paging field. If the R&S CMW does not find any
device during the inquiry, you can only select the default device.
11. Set the channel. Refer to "Channel, Frequency " on page 75.
12. Set the Test Mode PIN. The value must match with the configuration at the DUT.
13. Send the PIN to the DUT to enable LE test mode. Refer to Test Mode Send Enable
with PIN.
14. Press "Connect Test Mode" and wait until the "Connection Status" pane indicates
the signaling state "Connected".
15. ● To perform RX tests, press the "RX Meas." softkey, see also Chapter 4, "Rx
PER Measurement", on page 233 and Chapter 5, "Rx BER/PER Search",
on page 258.
● For TX tests, perform the TX measurements with the "Bluetooth TX Measure-
ment" application e.g. power or modulation measurements:
Press the multi-evaluation softkey which opens up the "Bluetooth TX Measure-
ment" application. Using softkey has the side-effect of setting the scenario to
combined signal path. The TX measurements in LE test mode are only availa-
ble with option R&S CMW-KM611.
The DUT is connected via RF cable. Optionally, the secondary communication channel
can be realized via USB interface, see Chapter 2.2.2, "Test Setup", on page 15.
Direct test mode for LE tests is defined in the specification for Bluetooth wireless tech-
nology, core system package: volume 6, part F.
Direct test mode is used to control the DUT via secondary communication channel, to
send test packets via radio interface and to retrieve the DUT measurement report. The
test specification for Bluetooth LE technology (RF PHY test specification) uses direct
test mode in all transmitter and receiver test cases for LE.
The R&S CMW supports direct test mode over HCI and through a two-wire UART inter-
face. In addition to the RF connection, the R&S CMW uses a secondary communica-
tion channel via USB for the test control commands. For the test setup, refer to Chap-
ter 2.2.2.2, "Tests with USB Interface", on page 16.
4. Select the HW interface for LE connections. See "HW Interface" on page 71.
6. If HW Interface = "None", start the test directly at the DUT and continue from
step 10.
8. Select the used COM port . Adapt the transmission parameters. See "USB to
RS232" on page 72.
9. Press the hotkey "Connection Check" to reset the DUT and to verify the USB con-
nection.
The dialog confirms, that the DUT has executed the reset command.
If there was error indication, repeat the step 4 to reconfigure the transmission
parameters (typically the baud rate for "HW Interface" = "USB to RS232")
10. Select the frequency. See "Channel, Frequency " on page 75.
11. Configure test packets. See Chapter 2.3.9.3, "Signal Characteristics Configura-
tion", on page 91 and Chapter 2.3.1.11, "Signal Characteristics", on page 53.
13. To repeat the step 4, step 7 or step 9 to reconfigure the transmission parameters,
turn off all TX and RX LE measurements.
● Operating Bands..................................................................................................... 31
● BR/EDR: ACL Packets............................................................................................31
● BR/EDR: SCO and eSCO Packets......................................................................... 32
● BR/EDR: Link Control Packets................................................................................33
The frequency band defined for Bluetooth devices is the unlicensed 2.4 GHz "Indus-
trial, Scientific and Medical" (ISM) frequency band.
Table 2-1: Operating band BR/EDR
The ACL packets are used for asymmetric links and they contain user data or control
data. The table and the figures below give an overview of the ACL packets and their
structure.
Table 2-3: ACL packet - BR
Type Header length Payload length* in byte FEC CRC Max. timeslots
in byte
DH3 2 0-183 3
DH5 0-339 5
* The payload length in the table denotes the number of user payload bytes.
Type Header length Payload length* in byte FEC CRC Max. timeslots
in byte
2-DH3 0-367 3
2-DH5 0-679 5
3-DH1 0-83 1
Type Header length Payload length* in byte FEC CRC Max. timeslots
in byte
3-DH3 0-552 3
3-DH5 0-1021 5
* The payload length in the table denotes the number of user payload bytes.
The SCO and eSCO packets are used for symmetric links. The SCO packets are used
for 64 kbit/s speech transmission and for transparent synchronous data. The eSCO
packets are also used for 64kbit/s speech transmission and transparent data at up to
288 kbit/s.
The tables and the figures below give an overview of the SCO and eSCO packets and
their structure.
Table 2-5: SCO packets
* The payload length in the table denotes the number of user payload bytes.
EV3 1-30 no 1
* The payload length in the table denotes the number of user payload bytes.
2-EV3 1-60 1
3-EV3 1-90 1
3-EV5 1-540 3
* The payload length in the table denotes the number of user payload bytes.
There are some common kinds of packet types. An overview of these packet types is
given in the table below.
Table 2-8: Common link control packets
NULL n.a. ACL, SCO, eSCO Carries link information to the source, e.g. about
successfully received signal or the state of the
receiving buffer
POLL n.a. ACL, SCO, eSCO Similar to NULL packet, used by master to poll the
slaves, must be confirmed
Packet type ID Packet types NULL and POLL Packet types FHS
LE packet formats are described in the "Air Interface Packets" section of core specifi-
cation for Bluetooth wireless technology, volume 6, part B.
Each packet consists of four mandatory fields: preamble, sync word (test and data
channel packets), PDU, and CRC. Constant tone extension (CTE) is optional.
The entire packet is transmitted at the same symbol rate.
Packets (not including the CTE) take between 44 and 2120 μs to transmit. CTE trans-
mission takes between 16 and 160 μs (CTE units x 8 μs).
Table 2-10: Packet format for LE uncoded PHY
Each packet consists of the preamble, FEC block 1, and FEC block 2. The preamble is
not coded. The FEC block 1 consists of three fields: access address (sync word for test
and data channel packets), coding indicator (CI), and TERM1. These fields use the
S=8 coding scheme. The CI field determines which coding scheme is used for FEC
block 2. The FEC block 2 consists of three fields: PDU, CRC, and TERM2. These
fields use either the S=2 or S=8 coding scheme, depending on the value of the CI field.
The entire packet is transmitted with 1 Msymbol/s modulation. The following table cap-
tures the size and duration of a packet for the LE coded PHY.
Table 2-11: Packet format for LE coded PHY
Packets (not including the CTE) take between 44 and 2120 μs to transmit.
CTE
PDU
2-20 units
Header Payload
2 octets 0-255 octets
LE test packets are described in the section 4 LE Test Packet Definition in core specifi-
cation for Bluetooth wireless technology, volume 6, part F.
The data channel PDU has a 16-bit header (2 octets), a variable size payload (0-251
octets). An empty data channel packet supported by options R&S CMW-KS601/-
KS720 is shown in the following figure.
PDU
LSB MSB
Header Payload
2 octets 0 octets
Besides the data packet type, during Rx measurements the R&S CMW supports the
following CONTROL_DATA packet types.
● LL_FEATURE_REQ (Opcode 0x08)
● LL_FEATURE_RSP (Opcode 0x09)
Both the packet types have a 9 byte payload and therefore the default PER threshold
is set to 13.4% by default for Rx measurements.
The following section describes the main signaling states and state transitions:
Figure 2-15: R&S CMW states for connection and test modes (classic)
TM = test mode
Figure 2-16: R&S CMW states for audio profiles and echo modes
"Off" The signaling is switched OFF; all other signaling states are only available if signaling is switched ON.
"Standby" Bluetooth standby state; the default and initial state after signaling is switched ON. In this state, no RF
signal is generated.
"Run EUT controller" The R&S CMW sends a reset EUT command via USB connection. If the DUT is recognized at the
USB interface, its Bluetooth address is discovered, inquiry is not necessary to be executed. The
selected operating mode is enabled at the DUT, see Operating Mode.
"Connecting" After activating the "Connect"/"Connect Testmode" hotkey, the R&S CMW transmits a signal to syn-
chronize and connect/connect test mode to a known Bluetooth device. In the intermediate page state,
the R&S CMW tries to coincide with the slave's scan activity by repeatedly transmitting the paging
message.
"Connected A2DP" An ACL link between master and slave is established. The R&S CMW acts as A2DP source, the DUT
acts as A2DP sink.
"Connected testmode" An ACL link between master and slave is established and the selected test is running.
"Connected echo mode / An ACL link between master and slave is established, SCO/eSCO link on top of ACL link is estab-
HFP / HFP AG" lished and the selected mode / audio profile is running.
"Idle" The R&S CMW is set to slave mode. It becomes discoverable and expects the DUT to connect as a
master.
Before connecting as a master, some DUTs require a pairing information to be stored during a previ-
ous successful connection to the R&S CMW.
"Connected slave" The DUT as a master is connected via an ACL link. The R&S CMW acts as a slave.
"Connected A2DP slave" The DUT as a master is connected via an ACL link. The R&S CMW acts as an A2DP source, the DUT
acts as an A2DP sink.
"Connected HFP slave / An ACL link between master and slave is established, SCO/eSCO link on top of ACL link is estab-
HFP AG slave" lished and the selected audio profile is running in slave mode.
"Detaching" An established ACL link is being disconnected and the master signal is switching off.
The "Connection status" pane indicates the current signaling state, see Chap-
ter 2.3.1.1, "Connection Status Tab - Connection Status", on page 42.
"Off" The signaling is switched OFF; all other signaling states are only available if signaling is switched ON.
"Standby" Bluetooth standby state; the default and initial state after signaling is switched ON. In this state, no RF
signal is generated.
"Inquiring" (scanning) After activating the "Inquiry" hotkey, the R&S CMW tries to discover nearby Bluetooth LE devices
sending SCAN_REQ PDUs. The DUT basic parameters are stored for the respective device (the
EUT's name, address type, LE role).
Extended inquiry responses are ignored (ADV_EXT_IND PDU).
"Connecting" (initiating) ● After activating the "Connect" hotkey in the central mode, the R&S CMW sends connect request
(CONNECT_REQ PDU) to a known Bluetooth device. The first PDU of each advertising event
must be transmitted in the used primary advertising channel with the lowest advertising channel
index.
After EUT connect request in the central LE role, the instrument responds to ADV_IND PDU.
● In the peripheral LE role, the instrument responds to ADV_DIRECT_IND PDU.
"Detaching" An established ACL link is being disconnected and the master signal is switching off.
The "Connection status" pane indicates the current signaling state, see Chap-
ter 2.3.1.1, "Connection Status Tab - Connection Status", on page 42.
Table 2-14: R&S CMW connection status for direct test mode
Off The signaling is switched OFF; all other signaling states are only available if signaling is switched ON.
Idle Initial state after the R&S CMW has recognized a DUT connected via USB interface, no RF signal is
generated.
Communication test run- The R&S CMW sends reset command to the DUT and waits for the response.
ning
This test is triggered manually, see "Connection Check (hotkey)" on page 59.
Refreshing COM port list The R&S CMW scans the USB ports to list all connected devices, see "Refresh COM Port List (hot-
key)" on page 63.
Tx/Rx test Tx/Rx test in direct test mode in progress, see Chapter 2.2.9, "Direct Test Mode (LE)", on page 28.
Current signaling state of LE in direct test mode is only displayed in the connection sta-
tus information at the bottom of PER view, PER search view and TX measurement
view.
The "Bluetooth Signaling" application provides trigger signals that can be used by can
be used by other R&S CMW applications to synchronize to the generated Bluetooth
downlink signal.
To address the trigger signals in remote commands, use the following strings, with <i>
replaced by the instance number of the signaling application:
● "Bluetooth Sig<i>: ACPTrigger"
● "Bluetooth Sig<i>: LESignallingTrigger"
● "Bluetooth Sig<i>: SignallingTrigger"
ACP Trigger
The ACP trigger event indicates the expected start of the first symbol of the Bluetooth
burst at the DUT receiver. Between two successive ACP trigger events, the R&S CMW
waits from 100 s to 125 s before the next ACP trigger is generated.
This trigger is suitable for the following Bluetooth multi-evaluation measurements:
● 79 channels ACP BR/EDR measurements, option R&S CMW-KM610 (with signal-
ing option R&S CMW-KS610)
● All channels ACP LE measurements, option R&S CMW-KM611 (with signaling
option R&S CMW-KS611)
LE Signaling Trigger
Trigger event indicating the expected start of the first symbol at the beginning of each
Bluetooth burst received by the DUT for LE connection tests.
This trigger is suitable for the following Bluetooth multi-evaluation measurements:
● Option R&S CMW-KM611 for uncoded LE 1M PHY (with signaling option
R&S CMW-KS601)
● Plus option R&S CMW-KM721 for LE 2M and LE coded PHY (with signaling option
R&S CMW-KS720)
Signaling Trigger
Trigger event indicating the expected start of the first symbol at the beginning of each
Bluetooth burst received by the DUT.
This trigger is suitable for all remaining Bluetooth multi-evaluation measurements in
combined signal path.
● Option R&S CMW-KM610 for BR/EDR (with signaling option R&S CMW-KS610)
● Option R&S CMW-KM611 for uncoded LE 1M PHY (with signaling option
R&S CMW-KS611)
● Plus option R&S CMW-KM721 for LE 2M and LE coded PHY (with signaling option
R&S CMW-KS721)
● Plus option R&S CMW-KM722 for LE with CTE (with signaling option R&S CMW-
KS722)
The signaling view displays status information about the R&S CMW and the connected
DUT. Furthermore it allows you to set the most important parameters.
Access: Bluetooth signaling main view > "Connection Status" tab > "Connection Sta-
tus" area.
The upper left pane of the main view contains connection tabs. The "Connection Sta-
tus" tab displays information dependent on the selected burst type. All settings in this
view can also be accessed via the configuration dialog.
In the connection status pane, the current connection states, information for trouble-
shooting and the most important Bluetooth device settings are shown.
CMW............................................................................................................................. 43
Signaling....................................................................................................................... 43
Rx Power.......................................................................................................................43
Bluetooth Address.........................................................................................................43
CMW
Indicates one of the following instrument roles:
● For most of connections, the connection control role of instrument: master or slave
See also CMW Role.
● Exception: for LE connection tests, LE role: central or peripheral
See also CMW Role.
The color of the antenna icon indicates the main state of the "Bluetooth Signaling"
application: gray (OFF) or green (ON).
Remote command:
SOURce:BLUetooth:SIGN<i>:STATe
Signaling
The current signaling state. For a detailed description of the available states and state
transitions, see Chapter 2.2.11, "Signaling States", on page 36.
Current signaling state in LE direct test mode is not indicated. It is only displayed in the
connection status information at the bottom of PER view, PER search view or Tx mea-
surement view.
Remote command:
FETCh:BLUetooth:SIGN<i>:CONNection:STATe?
FETCh:BLUetooth:SIGN<i>:CONNection:STATe:LESignaling?
Rx Power
Indicates whether the power currently received from the DUT is "In Range" with the
configured expected nominal power (see Tx Level (CMW)) or if the receiver is "Over-
driven" or "Underdriven".
Bluetooth Address
The Bluetooth device address used by the R&S CMW and DUT.
This setting is not relevant for LE direct test mode.
For BR and EDR, "CMW BD Address" and "EUT BD Address" settings are covered in
the GUI description, see Chapter 2.3.9.1, "Paging Configuration Classic",
on page 85.
For LE connection tests, "CMW Address" and "EUT Address" settings are covered in
Chapter 2.3.9.2, "Paging Configuration Low Energy", on page 87.
Access: Bluetooth signaling main view > select "EUT Info" in the field below the "Con-
nection Status" area
The "EUT Info" pane displays basic device information retrieved during paging (con-
nection setup).
This section is not relevant in LE direct test mode.
Device Name.................................................................................................................44
LMP Version and Subversion (BR/EDR).......................................................................44
Power Control, Power State (BR/EDR).........................................................................44
Address Type (LE)........................................................................................................ 45
GAP Mode (LE).............................................................................................................45
Device Name
Displays name of the connected device; up to 255 characters long.
Remote command:
SENSe:BLUetooth:SIGN<i>:EUT:INFormation:NAME?
SENSe:BLUetooth:SIGN<i>:EUT:INFormation:LESignaling?
Check the DUT support of power control within the Chapter 2.3.1.3, "Connection Sta-
tus Tab - EUT Capabilities", on page 45.
Remote command:
SENSe:BLUetooth:SIGN<i>:EUT:PCONtrol:STATe:LEGacy?
SENSe:BLUetooth:SIGN<i>:EUT:PCONtrol:STATe?
SENSe:BLUetooth:SIGN<i>:EUT:PCONtrol:STATe:DPSK?
SENSe:BLUetooth:SIGN<i>:EUT:PCONtrol:STATe:DQPSk?
SENSe:BLUetooth:SIGN<i>:EUT:PCONtrol:STATe:GFSK?
Access: Bluetooth signaling main view > select "EUT Capabilities" in the field below the
"Connection Status" area
The "EUT Capabilities" pane displays device information requested from the DUT after
a connection has been successfully established.
To maximize the EUT capabilities area and display all capability information, press the
button to the right.
Remote command:
SENSe:BLUetooth:SIGN<i>:EUT:CAPability:LESignaling?
Device Information
Gets basic information about the DUT collected during inquiry and connection setup.
Remote command:
SENSe:BLUetooth:SIGN<i>:EUT:INFormation:NAME?
SENSe:BLUetooth:SIGN<i>:EUT:INFormation:VERSion?
SENSe:BLUetooth:SIGN<i>:EUT:INFormation:COMPany?
SENSe:BLUetooth:SIGN<i>:EUT:INFormation:BDADdress?
SENSe:BLUetooth:SIGN<i>:EUT:INFormation:CLASs?
Remote command:
SENSe:BLUetooth:SIGN<i>:EUT:CAPability:CONNection?
SENSe:BLUetooth:SIGN<i>:EUT:CAPability:ENCRyption?
Remote command:
SENSe:BLUetooth:SIGN<i>:EUT:CAPability:PSAVing?
SENSe:BLUetooth:SIGN<i>:EUT:CAPability:PCONtrol?
Remote command:
SENSe:BLUetooth:SIGN<i>:EUT:CAPability:SCO?
SENSe:BLUetooth:SIGN<i>:EUT:CAPability:ESCO?
SENSe:BLUetooth:SIGN<i>:EUT:CAPability:ACL?
Access: Bluetooth signaling main view > "Connection Status" tab > "Test Packet Sync
Word" area.
The following pane specifies parameters for LE direct test mode. This section is not rel-
evant for the burst type LE in connection tests.
Access: Bluetooth signaling main view > select "EUT Power Control" in the field below
the "Connection Status" area
To maximize the "EUT Power Control" area, press the button to the right.
Option R&S CMW-KS601 is required.
Connection Status.........................................................................................................50
HW Interface................................................................................................................. 50
USB Info........................................................................................................................50
Connection Status
The "Connection Status" is described in detail in the previous section Chapter 2.3.1.1,
"Connection Status Tab - Connection Status", on page 42.
HW Interface
Specifies a USB control connection to the DUT. The driver of a connected DUT must
be installed, refer to Chapter 2.2.2.2, "Tests with USB Interface", on page 16.
The following settings are supported:
● "None": configures the Rx measurements without controlling the DUT via USB
interface.
● "USB to RS232 Adapter": displays the transmission parameters of the serial inter-
face realized via USB connection with USB to RS232 adapter.
If the DUT is connected to a USB port, the mapped virtual COM port can be auto-
matically detected by pressing the hotkey "Refresh COM Port List" (see "Refresh
COM Port List (hotkey)" on page 63).
The settings are the same as in the configuration dialog, see Chapter 2.3.7, "EUT
Control", on page 70.
● "USB": specifies the tested device connected directly via USB port (connection
without serial adapter). The R&S CMW lists all detected DUTs as "USB Device"
values.
The settings are the same as in the configuration dialog, see "USB" on page 72.
Also, USB Info area is displayed.
USB Info
Displays EUT information received via USB control interface. This area is visible if HW
Interface = "USB"
Remote command:
SENSe:BLUetooth:SIGN<i>:USBDevice:INFormation:DCLass?
SENSe:BLUetooth:SIGN<i>:USBDevice:INFormation:DPRotocol?
SENSe:BLUetooth:SIGN<i>:USBDevice:INFormation:DSUBclass?
SENSe:BLUetooth:SIGN<i>:USBDevice:INFormation:IDPRoduct?
SENSe:BLUetooth:SIGN<i>:USBDevice:INFormation:IDVendor?
SENSe:BLUetooth:SIGN<i>:USBDevice:INFormation:MANufacturer?
SENSe:BLUetooth:SIGN<i>:USBDevice:INFormation:PRODuct?
SENSe:BLUetooth:SIGN<i>:USBDevice:INFormation:SERial?
Connection Status
The "Connection Status" is described in detail in the previous section Chapter 2.3.1.1,
"Connection Status Tab - Connection Status", on page 42.
Link Info
Displays the most important connection parameters of an active audio link.
Option R&S CMW-KS602 is required.
Remote command:
SENSe:BLUetooth:SIGN<i>:CONNection:AUDio:LINFo?
The "Event Log" area reports events and errors such as applied system settings,
startup events, connection events and power control events.
If the Event Log Configuration is enabled, the event log displays additional information
about the protocol exchange between the DUT and R&S CMW.
Event Log
Each entry consists of a timestamp, an icon indicating the category of the event and a
short text describing the event. Meaning of the category icons: = information,
warning and error respectively.
To expand the event log area, press the button to the right.
Press the button to the right to clear the displayed event entries.
Remote command:
CLEan:BLUetooth:SIGN<i>:ELOGging
SENSe:BLUetooth:SIGN<i>:ELOGging:ALL?
SENSe:BLUetooth:SIGN<i>:ELOGging:LAST?
SENSe:BLUetooth:SIGN<i>:EUT:PCONtrol:STATe:LESignaling?
The settings are the same as in the configuration dialog, see Chapter 2.3.6, "General
Settings", on page 66 and Chapter 2.3.5, "CMW Role", on page 65.
2.3.1.10 RF Setup
The main view provides only the most important settings for fast access. The set of dis-
played parameters depends on the selection in the pane General Setup. This section is
not relevant for connection tests.
The most of the settings are the same as in the configuration dialog, see Chap-
ter 2.3.9.3, "Signal Characteristics Configuration", on page 91.
Exceptions are the configurations of CTE-specific parameters for LE with CTE and the
packet type in audio mode:
CTE Type...................................................................................................................... 54
CTE Units......................................................................................................................54
Number of Antennae, Slot Duration.............................................................................. 54
Packet Type (audio mode)............................................................................................ 55
CTE Type
Selects between the angle of arrival (AoA) and angle of departure (AoD) CTE slots.
Remote command:
CONFigure:BLUetooth:SIGN<i>:CONNection:PACKets:TYPE:CTE:LENergy:
LE1M
CONFigure:BLUetooth:SIGN<i>:CONNection:PACKets:TYPE:CTE:LENergy:
LE2M
CTE Units
Specifies the length of CTE portion of the burst in units. One CTE unit corresponds to
8 µs.
Remote command:
CONFigure:BLUetooth:SIGN<i>:CONNection:PACKets:UNITs:CTE:
LENergy:LE1M
CONFigure:BLUetooth:SIGN<i>:CONNection:PACKets:UNITs:CTE:
LENergy:LE2M
The R&S CMW uses always only one RF connector, multiple antennas are emula-
ted. For the test setup, refer to Chapter 2.2.2.3, "Test with Multiple EUT's Antennas
(LE with CTE)", on page 17.
● In the column "Slot. Dur.", specifies the duration of CTE slots. The type of the CTE
slot is set via CTE Type. The supported CTE slots are AoA 1 µs, AoA 2 µs,
AoD 1 µs, and AoD 2 µs.
Remote command:
CONFigure:BLUetooth:SIGN<i>:RFSettings:NANTenna:CTE:LENergy
CONFigure:BLUetooth:SIGN<i>:CONNection:PACKets:TYPE:CTE:LENergy:
LE1M
CONFigure:BLUetooth:SIGN<i>:CONNection:PACKets:TYPE:CTE:LENergy:
LE2M
Defines the packet type used for audio connections. The following packets are suppor-
ted:
● SCO connections for BR: HV1, HV2 and HV3
● eSCO connections for BR: EV3, EV4 and EV5
● eSCO connections for EDR: 2-EV3, 2-EV5, 3-EV3, 3-EV5
Remote command:
CONFigure:BLUetooth:SIGN<i>:CONNection:PACKets:PTYPe:SCO
CONFigure:BLUetooth:SIGN<i>:CONNection:PACKets:PTYPe:ESCO
2.3.1.12 Authentication
The settings are the same as in the configuration dialog, see Chapter 2.3.9.4, "Audio
Profiles Settings", on page 95.
Access: Bluetooth signaling main view > "Audio Link Setup" area.
This pane is only visible if operating mode is set to "Profile" and profile is set to "A2DP
Sink", see "Operating Mode" on page 66.
Option R&S CMW-KS603 is required for A2DP profiles.
The settings are the same as in the configuration dialog, see "Audio Link Setup"
on page 96.
The individual connection states are controlled via the [ON | OFF] key, via hotkeys and
via the DUT.
The available hotkeys depend on the current connection state. Below all possible hot-
keys are described.
For background information, refer to chapter Chapter 2.2.11, "Signaling States",
on page 36.
[ON | OFF] (key) / Bluetooth Signaling (softkey)........................................................... 57
Connect (hotkey)...........................................................................................................57
Connect Audio (hotkey).................................................................................................58
Connect HFP / HFP AG / Echo Mode / A2DP (hotkey).................................................58
Connect Test Mode (hotkey)......................................................................................... 58
Connection Check (hotkey)...........................................................................................59
Connection Interval (hotkey)......................................................................................... 59
Detach (hotkey).............................................................................................................59
Enter HFP / Enter HFP AG / Enter Echo Mode (hotkey)...............................................59
Exit HFP / Exit HFP AG / Exit Echo Mode (hotkey)...................................................... 60
Initialize EUT (hotkey)................................................................................................... 60
Power Control (softkey).................................................................................................60
└ Get Tx Power (hotkey).................................................................................... 60
└ Power Up / Power Down / Step Size (hotkey)................................................ 61
└ Max Power (hotkey)........................................................................................ 61
Inquire (hotkey)............................................................................................................. 62
Power Up / Power Down / Max Power (hotkey)............................................................ 62
Refresh COM Port List (hotkey).................................................................................... 63
Refresh Devices (hotkey)..............................................................................................63
Reset EUT (hotkey).......................................................................................................63
Tx Test (hotkey).............................................................................................................63
Volume Control... (softkey)............................................................................................63
Remote command:
SOURce:BLUetooth:SIGN<i>:STATe
Connect (hotkey)
This hotkey is only available in standby state and for operating mode "Connection
Test". It activates the paging state on the R&S CMW with the target selected in "For
Paging" on page 86 for BR/EDR ("For Paging" on page 90 for LE).
If paging is successful, the R&S CMW goes to the connected state.
Remote command:
CALL:BLUetooth:SIGN<i>:CONNection:ACTion
CALL:BLUetooth:SIGN<i>:CONNection:ACTion:LESignaling
This hotkey is only available if operating mode is set to "Audio", see "Operating Mode"
on page 66.
Remote command:
CALL:BLUetooth:SIGN<i>:CONNection:ACTion
These hotkeys are only available if operating mode is set to "Profile" / "Echo Mode",
see "Operating Mode" on page 66. They establish an audio link for hands-free profile
(HFP), hands-free audio gateway profile (HFP AG), echo mode, or A2DP.
Option R&S CMW-KS602 is required for audio profiles.
Option R&S CMW-KS603 is required for A2DP.
Remote command:
CALL:BLUetooth:SIGN<i>:CONNection:ACTion
This hotkey is only available in standby state and if either BR or EDR burst type is
selected. It activates the paging state on the R&S CMW with the target selected in "For
Paging" on page 86.
If paging is successful, the R&S CMW goes to the test mode connected state.
Prerequisite: the DUT with enabled test mode (typically enabled by typing a vendor-
specific key combination at the DUT, for example #123456789#).
Option R&S CMW-KS610 is required.
While the DUT is connected, the signaling application provides a trigger signal, see
Chapter 2.2.12, "Trigger Signals", on page 40.
Remote command:
CALL:BLUetooth:SIGN<i>:CONNection:ACTion
Checks whether it is possible to control the DUT connected via USB interface. The
R&S CMW sends a reset command to the DUT and waits for the DUT's response via
RF link. The result is displayed in a pop-up dialog.
If there was failure, it is necessary to adjust the HW Interface or the transmission
parameters settings, typically the baud rate, see "USB to RS232" on page 72.
This hotkey is only available if LE burst type is selected.
Option R&S CMW-KS611 is required.
Remote command:
CALL:BLUetooth:SIGN<i>:CONNection:CHECk:LENergy?
Sets the time interval between the two consecutive connection events in slots. For
information, the value in ms is indicated.
This hotkey is only available for LE connection tests and LE test mode.
The setting for LE connection tests is covered in the main configuration tree, see "Con-
nection Interval" on page 89.
The setting for LE test mode is only available via this hotkey.
Option R&S CMW-KS601 is required.
Remote command:
CONFigure:BLUetooth:SIGN<i>:TCONnection:INTerval:LESignaling
Detach (hotkey)
This hotkey is only available during an active connection. It requests the R&S CMW to
close an established connection, switch off the master signal, and revert to standby
state.
Remote command:
CALL:BLUetooth:SIGN<i>:CONNection:ACTion
CALL:BLUetooth:SIGN<i>:CONNection:ACTion:LESignaling
These hotkeys are only available if operating mode is set to "Profile" / "Echo Mode",
see "Operating Mode" on page 66. They re-establish an audio link for hands-free
profile (HFP), hands-free audio gateway profile (HFP AG) or echo mode.
These hotkeys are only available if an audio link is established. They release the audio
link and return to the connected state (ACL link). The audio connection can be re-
established via Enter HFP / Enter HFP AG / Enter Echo Mode (hotkey).
Option R&S CMW-KS602 is required for audio profiles.
Remote command:
CALL:BLUetooth:SIGN<i>:CONNection:ACTion
This hotkey sends a reset EUT command for BR/EDR via USB connection.
Option R&S CMW-KS610 is required.
Remote command:
CALL:BLUetooth:SIGN<i>:CONNection:ACTion
The "Power Control" key is used to display the following related hotkeys.
Remote command:
SENSe:BLUetooth:SIGN<i>:EUT:PCONtrol:STATe:LESignaling?
The hotkey "Step Size" sets the power step for power-up and power-down commands.
When the DUT reaches the limit it sends "Min / Max power reached" response to the
R&S CMW, but it not does not change its power anymore.
The event log pane displays the power commands and the DUT responses.
Remote command:
CONFigure:BLUetooth:SIGN<i>:CONNection:PCONtrol:SSIZe:
LESignaling
CONFigure:BLUetooth:SIGN<i>:CONNection:PCONtrol:STEP:ACTion:
LESignaling
SENSe:BLUetooth:SIGN<i>:EUT:PCONtrol:STATe:LESignaling?
Remote command:
CONFigure:BLUetooth:SIGN<i>:CONNection:PCONtrol:STEP:ACTion:
LESignaling
SENSe:BLUetooth:SIGN<i>:EUT:PCONtrol:STATe:LESignaling?
Inquire (hotkey)
This hotkey is only available in standby state and for operating mode "Connection
Test". It activates the inquiry state on the R&S CMW. The discovered devices are pre-
sented in the "BD Address" popup ("Address" popup for LE).
After the R&S CMW reverts to standby state, the popup is automatically closed and the
list of "pageable" devices (see "For Paging" on page 86) is updated.
Remote command:
CALL:BLUetooth:SIGN<i>:CONNection:ACTion
CONFigure:BLUetooth:SIGN<i>:CONNection:INQuiry:PTARgets:CATalog?
CALL:BLUetooth:SIGN<i>:CONNection:ACTion:LESignaling
CONFigure:BLUetooth:SIGN<i>:CONNection:INQuiry:PTARgets:CATalog:
LESignaling?
These hotkeys are available for BR/EDR device in the "connected in test mode" state
for the DUT capable of power control. When the DUT reaches the limit it sends "Min /
Max power reached" response to the R&S CMW, but it not does not change its power
anymore.
All three hotkeys are available only for enhanced power control. To legacy power con-
trol, only the hotkeys "Power Up" / "Power Down" are applicable. The activated power
control mode and reported state are displayed in the main view, see Chapter 2.3.1.2,
"Connection Status Tab - EUT Info", on page 44.
For the power control of LE devices, refer to Power Control (softkey).
The event log pane displays the power commands and the DUT responses.
Remote command:
CONFigure:BLUetooth:SIGN<i>:CONNection:PCONtrol:STEP:ACTion
Remote command:
CONFigure:BLUetooth:SIGN<i>:COMSettings:PORTs:CATalog?
Remote command:
CALL:BLUetooth:SIGN<i>:RDEVices
Remote command:
CALL:BLUetooth:SIGN<i>:LENergy:RESet
Tx Test (hotkey)
Starts and stops the Tx test in direct test mode.
This hotkey is only available if LE is selected, the DUT via USB interface has been dis-
covered and option R&S CMW-KM611 (Bluetooth LE, Tx measurements) is not instal-
led.
This hotkey is only available if operating mode is set to "Profile", see "Operating Mode"
on page 66.
Remote command:
CONFigure:BLUetooth:SIGN<i>:CONNection:AUDio:VOLControl:MICGain
CONFigure:BLUetooth:SIGN<i>:CONNection:AUDio:VOLControl:SPEaker
Using one of these softkeys ensures that the measurement is configured compatible
with the settings of the signaling application. When you use the softkeys to switch to
the "Bluetooth Multi Eval." measurements, the combined signal path scenario is activa-
ted automatically in the measurement.
Consequences:
● The measurement and the signaling application can be used in parallel, i.e. both
DL signal transmission and measurement can be switched on.
● The signaling RF settings are also used for the measurement.
● The Bluetooth input signal settings of the measurement are configured compatible
with the signaling application.
● Additional softkeys and hotkeys are displayed in the measurement, so that the sig-
naling application can be controlled and configured from the measurement.
The softkey "Go to..." opens a dialog box with a list of all available Bluetooth measure-
ments. If the softkey label indicates a measurement name, this measurement has been
assigned to the softkey as fixed target.
Three shortcut softkeys are available and can be set to different fixed targets.
Select Menu
Selects the target measurement you want to switch to.
Go to / Cancel
Press "Go to" softkey to switch to the selected measurement or "Cancel" to abort.
Unit
● Single-CMW setups
In a single CMW, you can equip up to four SUU or up to two SUA. You can execute
a scenario on a single CMW. But you can also use the scenario with a multi-CMW
setup.
● Multi-CMW setups
The instruments are controlled by an R&S CMWC. The test software including the
Bluetooth signaling application is installed and executed on the R&S CMWC.
The options can be distributed over several instruments. But the signaling units
(SUA) and TX modules used for Bluetooth signal must be in the same instrument.
Example: You cannot use a signaling unit of one instrument plus the TX modules of
another instrument.
The SW licenses are pooled in the R&S CMWC, so it does not matter where they
are installed.
● SUA vs. SUU
Each SUA board provides two SUA partitions. The GUI and the remote commands
select SUA partitions, not SUA boards. In one CMW, you have up to four SUA par-
titions or up to four SUU.
For the signaling unit numbering, refer to Chapter 2.5.1.2, "Values for Signal Path
Selection", on page 114.
Remote command:
ROUTe:BLUetooth:SIGN<i>:SCENario:OTRX:FLEXible
This section is only relevant for BR/EDR, operating mode = Profile, see Operating
Mode.
CMW Role
Selects either the master or slave connection control role of the R&S CMW.
Option R&S CMW-KS602 is required.
Remote command:
CONFigure:BLUetooth:SIGN<i>:CONNection:CMW:ROLE
Standard........................................................................................................................66
Operating Mode............................................................................................................ 66
Profile............................................................................................................................ 68
CMW Role.....................................................................................................................68
Burst Type (classic).......................................................................................................69
Test Mode (classic)....................................................................................................... 69
PHY (LE)....................................................................................................................... 69
Coding Scheme (LE > Long Range)............................................................................. 70
Standard
Selects either classic (BR/EDR) or LE signaling connections.
Remote command:
CONFigure:BLUetooth:SIGN<i>:STANdard
Operating Mode
Operating mode switches between certain test scenarios that require different sets of
parameters. Some parameters are only available for specific mode.
● Connection (classic):
The R&S CMW provides ACL connections.
Connection tests for BR and EDR require the basic signaling option R&S CMW-
KS600, see Chapter 2.2.4, "Connection Test (Classic)", on page 20.
● Test mode (classic):
The R&S CMW provides loopback and Tx tests for BR and EDR. ACL links are tes-
ted. See Chapter 2.2.5, "Test Mode (Classic)", on page 21.
● Profile (classic):
The R&S CMW provides an audio link for audio profile tests. An additional parame-
ter "Profile" is displayed. In addition, the CMW Role can be specified.
LE connection tests require the basic signaling option R&S CMW-KS601, see
Chapter 2.2.7, "Connection Test (LE)", on page 26.
● Direct Test Mode (LE):
The R&S CMW provides direct test mode for LE according to Bluetooth specifica-
tion, see Chapter 2.2.9, "Direct Test Mode (LE)", on page 28. ACL links are tested.
Profile
Selects hands-free, hands-free audio gateway, or A2DP sink profile of the DUT for
Operating Mode = "Profile".
Option R&S CMW-KS602 is required for audio profiles.
Option R&S CMW-KS603 is required for A2DP audio profile.
Remote command:
CONFigure:BLUetooth:SIGN<i>:AUDio:PRFRole
CMW Role
Selects either the central or peripheral LE role of the R&S CMW.
This parameter is only relevant for Standard = "LE" and Operating Mode = "Connection
Test".
Option R&S CMW-KS601 is required.
Remote command:
CONFigure:BLUetooth:SIGN<i>:CONNection:CMW:ROLE:LESignaling
PHY (LE)
Selects the physical layer used for LE signal.
● "1 Mbps": LE uncoded 1 Msymbol/s physical layer
● "2 Mbps": LE uncoded 2 Msymbol/s physical layer
● "Long Range": LE coded 1 Msymbol/s physical layer
For LE direct test mode, option R&S CMW-KS611 is required for LE 1M PHY (unco-
ded). Option R&S CMW-KS721 is also required for LE 2M PHY and LE coded PHY.
For LE with CTE tests, option R&S CMW-KS722 is also required.
For LE connection tests (normal mode) and LE test mode, option R&S CMW-KS601 is
required for LE 1M PHY (uncoded). Option R&S CMW-KS720 is also required for
LE 2M PHY and LE coded PHY.
Remote command:
For LE direct test mode:
CONFigure:BLUetooth:SIGN<i>:CONNection:PHY:LENergy
For LE connection test (normal mode):
CONFigure:BLUetooth:SIGN<i>:CONNection:PHY:NMODe:LENergy
Access: "Config" hotkey > "General Setup" > "EUT Control" section.
Configures a USB connection to the DUT.
HW Interface................................................................................................................. 71
Reset EUT (Classic)......................................................................................................71
Enable Test Mode (Classic).......................................................................................... 71
EUT Comm. Protocol (Low Energy)..............................................................................71
Use BR/EDR Settings (Low Energy).............................................................................72
HW Interface
Defines the type of USB connection used for tests.
For LE in direct test mode, the interface is used for the test control commands.
For BR/EDR connections, the interface is used as an additional control channel for
example to enable test mode automatically, or reset the DUT, see "Initialize EUT (hot-
key)" on page 60. To detect a DUT connected via USB, the driver must be installed,
refer to Chapter 2.2.2.2, "Tests with USB Interface", on page 16.
● None: tests without a USB control connection.
For BR/EDR connections, communication with the DUT is realized via RF interface
only. The DUT is controlled manually, for example enabling test mode directly at
the device.
For LE connections, the Rx measurement is supported without controlling direct
test mode. The test is started manually by the DUT. The R&S CMW sends several
test packets to the DUT. This method is applicable only to the DUT that can count
received packets.
● USB to RS232 adapter: support of the secondary communication channel via USB
connection with USB to RS232 adapter.
● USB: support of the secondary communication channel via direct USB connection.
For the test setup, refer to Chapter 2.2.2.2, "Tests with USB Interface", on page 16.
Remote command:
CONFigure:BLUetooth:SIGN<i>:HWINterface<no>
The setting is only relevant for HW Interface = "USB to RS232 adapter". Direct USB
connections always use HCI.
Remote command:
CONFigure:BLUetooth:SIGN<i>:CPRotocol
USB to RS232
Specifies the transmission parameters of the virtual serial interface used for USB con-
nection with USB to RS232 adapter.
The USB port to which the DUT is connected is mapped automatically onto the virtual
COM port.
The transmission parameters must comply with the parameters of the DUT.
● "Virtual Com Port": specifies the port, to which the used USB port has been map-
ped. The virtual COM port used by the DUT can be automatically detected by
pressing the hotkey "Refresh COM Port List", see "Refresh COM Port List (hotkey)"
on page 63.
● "Baud Rate": data transmission rate
● "Stop Bits", "Parity": number of bits used for stop indication, parity
● "Protocol": flow control
Remote command:
CONFigure:BLUetooth:SIGN<i>:COMSettings<no>:COMPort
CONFigure:BLUetooth:SIGN<i>:COMSettings<no>:BAUDrate
CONFigure:BLUetooth:SIGN<i>:COMSettings<no>:STOPbits
CONFigure:BLUetooth:SIGN<i>:COMSettings<no>:PARity
CONFigure:BLUetooth:SIGN<i>:COMSettings<no>:PROTocol
USB
Specifies the tested device connected directly via USB port. The R&S CMW lists only
the detected DUTs.
Remote command:
CONFigure:BLUetooth:SIGN<i>:USBSettings:DEVices:CATalog?
CONFigure:BLUetooth:SIGN<i>:USBSettings<no>:USBDevice
2.3.8 RF Settings
● Signal Routing.........................................................................................................73
● RF Frequency......................................................................................................... 74
● RF Power Settings.................................................................................................. 77
● Dirty Transmitter Configuration............................................................................... 78
Access: "Config" hotkey > "RF Settings" > "RF Output"/ "RF Input" sections.
The parameters in this section configure the RF input and output paths.
RF Output......................................................................................................................73
└ Connector, Converter......................................................................................74
└ External Attenuation........................................................................................74
RF Input........................................................................................................................ 74
└ Connector, Converter......................................................................................74
└ External Attenuation........................................................................................74
RF Output
The following parameters configure the RF output path of the R&S CMW.
RF Input
The following parameters configure the RF input path of the R&S CMW.
2.3.8.2 RF Frequency
Access: "Config" hotkey > "RF Settings" > "RF Frequency" section.
This section configures the hopping and channel/frequency.
Hopping (classic)...........................................................................................................75
Channel, Frequency .....................................................................................................75
Measure Mode (LE connection test)............................................................................. 76
Hopping Mode (LE connection test)..............................................................................76
Auto Configure 2nd Channel (LE connection test)........................................................76
Table Measured Channel, Hopping Channels (LE connection test)..............................76
Hopping (classic)
Enables/disables hopping for test mode. If enabled, then the R&S CMW transmits on
all possible Bluetooth channels in a pre-determined sequence.
This setting is only relevant for BR/EDR in test mode. Connection tests for BR/EDR
(option R&S CMW-KS600) always perform hopping.
Option R&S CMW-KS610 is required for BR/EDR in test mode.
Remote command:
CONFigure:BLUetooth:SIGN<i>:RFSettings:HOPPing
Channel, Frequency
Defines the channel. It also indicates the corresponding frequency.
If the hopping checkbox is selected, then the channel and frequency settings for Tx
test and loopback test are ignored.
Option R&S CMW-KS610 is required for Tx test and loopback test.
Option R&S CMW-KS611 is required for LE direct test mode.
Remote command:
BR/EDR:
CONFigure:BLUetooth:SIGN<i>:RFSettings:CHANnel:TXTest
CONFigure:BLUetooth:SIGN<i>:RFSettings:FREQuency:TXTest?
CONFigure:BLUetooth:SIGN<i>:RFSettings:CHANnel:LOOPback
CONFigure:BLUetooth:SIGN<i>:RFSettings:FREQuency:LOOPback?
LE direct test mode:
CONFigure:BLUetooth:SIGN<i>:RFSettings:CHANnel:DTMode
CONFigure:BLUetooth:SIGN<i>:RFSettings:FREQuency:DTMode?
LE test mode:
CONFigure:BLUetooth:SIGN<i>:RFSettings:CHANnel:TMODe
CONFigure:BLUetooth:SIGN<i>:RFSettings:FREQuency:TMODe?
Access: "Config" hotkey > "RF Settings" > "RF Power" section.
The parameters in this section provide the general power settings.
Tx Level (CMW)............................................................................................................ 77
Exp. Nominal Power......................................................................................................77
User Margin...................................................................................................................77
Auto Ranging................................................................................................................ 78
Tx Level (CMW)
Defines the power level transmitted by the R&S CMW
Remote command:
CONFigure:BLUetooth:SIGN<i>:RFSettings:LEVel
User Margin
Margin that the measurement adds to the expected nominal power to determine its ref-
erence power (reference level). The margin is typically used to account for the known
variations of the RF input signal power, for example, the variations due to a specific
channel configuration.
A user margin of 3 dB is appropriate for the supported packet types.
Remote command:
CONFigure:BLUetooth:SIGN<i>:RFSettings:UMARgin
Auto Ranging
Adjusts the input level expected at the R&S CMW antenna automatically, according to
the predefined values and measured signal amplitude. If enabled, the setting of Exp.
Nominal Power is ignored.
Remote command:
CONFigure:BLUetooth:SIGN<i>:RFSettings:ARANging
Access: "Config" hotkey > "RF Settings" > "Dirty Tx" section.
Configures in the R&S CMW transmitting of a non-ideal signal also known as dirty
transmitter. Dirty transmitter is defined in the test specification for Bluetooth wireless
technology.
For BR/EDR, refer to the following tests:
● RF/RCV/CA/BV-01-C
● RF/RCV/CA/BV-02-C
● RF/RCV/CA/BV-07-C
For LE, refer to the following tests:
● RF-PHY/RCV/BV-01-C (for LE 1M PHY)
● RF-PHY/RCV/BV-08-C (for LE 2M PHY)
● RF-PHY/RCV/BV-26-C (for LE coded PHY, S = 2)
● RF-PHY/RCV/BV-27-C (for LE coded PHY, S = 8)
● RF-PHY/RCV/BV-14-C (for LE 1M PHY, stable modulation)
● RF-PHY/RCV/BV-15-C (for LE 1M PHY, stable modulation)
● RF-PHY/RCV/BV-20-C (for LE 2M PHY, stable modulation)
● RF-PHY/RCV/BV-32-C (for LE coded PHY, S = 2, stable modulation)
● RF-PHY/RCV/BV-33-C (for LE coded PHY, S = 8, stable modulation)
Dirty Tx
Enables/disables dirty transmitter.
Remote command:
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX
Dirty Tx Mode
Selects one of the following schemes to configure the dirty transmitter:
Set Frequency offset in kHz Modulation index Symbol timing error in ppm
1 75 0.28 -20
2 14 0.30 -20
3 -2 0.29 20
4 1 0.32 20
Set Frequency offset in kHz Modulation index Symbol timing error in ppm
5 39 0.33 20
6 0 0.34 -20
8 74 0.31 -20
10 -75 0.35 20
If the BR dirty transmitter is enabled, the R&S CMW transmits the first 20 ms using the
first parameter set. The second 20 ms are transmitted with parameter set two, and so
forth. After the tenth set of parameters has been used, the R&S CMW continues using
the first set again.
Table 2-16: Dirty transmitter for EDR according to the test specification
1 0 0
2 65 20
3 -65 -20
If the EDR dirty transmitter is enabled, the R&S CMW transmits the first 20 packets
using the first parameter set. The second 20 packets are transmitted with parameter
set two, and so forth. After the third set of parameters has been used, the R&S CMW
continues using the first set again.
Table 2-17: Dirty transmitter for LE according to the test specification for direct test
Set Frequency offset in Standard modulation Stable modulation Symbol timing error
kHz index index in ppm
3 -3 0.46 0.496 50
4 1 0.52 0.502 50
5 52 0.53 0.503 50
If the LE dirty transmitter is enabled, the R&S CMW transmits the first 50 packets using
the first parameter set. The next 50 packets are transmitted using the second parame-
ter set, and so forth. After the tenth set of parameters has been used, the R&S CMW
continues using the first set again.
Dirty transmitter for LE connection tests is only applicable with standard modulation.
Dirty transmitter for LE connection tests differs from direct test mode only in a used
packet type. Instead of test packets, it transmits LL_FEATURE_REQ packets.
Remote command:
BR:
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:MINDex:BRATe?
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:FOFFset:BRATe?
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:STERror:BRATe?
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:FDRift:BRATe?
EDR:
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:FOFFset:EDRate?
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:STERror:EDRate?
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:FDRift:EDRate?
LE direct test mode:
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:MINDex:STANdard:
LENergy[:LE1M]? etc.
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:MINDex:STABle:
LENergy[:LE1M]? etc.
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:FDRift:LENergy[:
LE1M]? etc.
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:FOFFset:
LENergy[:LE1M]? etc.
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:STERror:
LENergy[:LE1M]? etc.
LE connection test:
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:MINDex:NMODe:
LENergy:LE1M? etc.
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:FDRift:NMODe:
LENergy:LE1M? etc.
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:FOFFset:NMODe:
LENergy:LE1M? etc.
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:STERror:NMODe:
LENergy:LE1M? etc.
LE test mode:
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:MINDex:STANdard:
TMODe:LENergy:LE1M? etc.
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:MINDex:STABle:
TMODe:LENergy:LE1M? etc.
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:FDRift:TMODe:
LENergy:LE1M? etc.
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:FOFFset:TMODe:
LENergy:LE1M? etc.
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:STERror:TMODe:
LENergy:LE1M? etc.
Single Values
The parameters take effect if dirty Tx is set to "Single Values". Exception is the addi-
tional configuration of modulation frequency for LE, that applies also in Dirty Tx Mode =
"Spec Table".
"Single Values" specify single set of dirty transmitter parameters to be applied without
periodic change.
The following parameters are configurable:
● "Modulation Index": Enable / disable modulation index and configure its value.
Two possible modulation indexes are configurable for LE direct test: standard or
stable modulation.
The checkbox for enabling/disabling modulation index in the GUI is visible in the
LE Rx measurements, hotkey "Dirty Tx" > "Modulation Index".
● "Frequency Offset": Enable / disable frequency offset and configure its value.
● "Symbol Timing Error": Disable or enable symbol timing error and configure its
value.
● "Drift": Enable / disable the drift. For BR/EDR, the time-dependent drift is gener-
ated according to the test specification for Bluetooth wireless technology. For LE,
the value is configurable via "Modulation Frequency".
Option R&S CMW-KS610 is required for BR/EDR in test mode.
For LE direct test mode, option R&S CMW-KS611 is required for LE 1M PHY (unco-
ded). Option R&S CMW-KS721 is also required for LE 2M PHY and LE coded PHY.
For LE with CTE tests, option R&S CMW-KS722 is also required.
For LE connection tests (normal mode) and LE test mode, option R&S CMW-KS601 is
required for LE 1M PHY (uncoded). Option R&S CMW-KS720 is also required for
LE 2M PHY and LE coded PHY.
Remote command:
BR:
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:MINDex:BRATe
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:FOFFset:BRATe
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:STERror:BRATe
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:FDRift:BRATe
EDR:
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:FOFFset:EDRate
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:STERror:EDRate
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:FDRift:EDRate
LE direct test mode:
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:MINDex:STANdard:
LENergy[:LE1M] etc.
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:MINDex:STABle:
LENergy[:LE1M] etc.
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:FOFFset:
LENergy[:LE1M] etc.
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:STERror:
LENergy[:LE1M] etc.
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:FDRift:LENergy[:
LE1M] etc.
LE connection test:
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:MINDex:NMODe:
LENergy:LE1M etc.
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:FOFFset:NMODe:
LENergy:LE1M etc.
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:STERror:NMODe:
LENergy:LE1M etc.
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:FDRift:NMODe:
LENergy:LE1M etc.
LE test mode:
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:MINDex:STANdard:
TMODe:LENergy:LE1M etc.
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:MINDex:STABle:
TMODe:LENergy:LE1M etc.
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:FOFFset:TMODe:
LENergy:LE1M etc.
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:STERror:TMODe:
LENergy:LE1M etc.
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:FDRift:TMODe:
LENergy:LE1M etc.
Access: "Config" hotkey > "Connection" > "Paging" > "Classic" section.
Option R&S CMW-KS600 is required.
CMW BD Address......................................................................................................... 85
For Paging.....................................................................................................................86
Default EUT...................................................................................................................86
└ BD Address.....................................................................................................86
└ Page Scan Repetition Mode........................................................................... 86
Supervision Timeout......................................................................................................86
Inquiry Length............................................................................................................... 86
Number of Inquiry Responses.......................................................................................86
Paging Timeout............................................................................................................. 87
CMW BD Address
The Bluetooth device address used by the R&S CMW when communicating with the
DUT.
Remote command:
CONFigure:BLUetooth:SIGN<i>:CONNection:BDADdress:CMW
For Paging
A drop-down list showing all the devices that the R&S CMW found during inquiry plus
the default address.
Remote command:
CONFigure:BLUetooth:SIGN<i>:CONNection:PAGing:PTARget
CONFigure:BLUetooth:SIGN<i>:CONNection:INQuiry:PTARgets:CATalog?
Default EUT
Settings of the DUT to connect with if For Paging = "Default".
Supervision Timeout
The LMP supervision timeout, i.e. number of "non-communication slots" between
R&S CMW and DUT that can occur before the two devices detach from each other. A
supervision timeout is set to ensure link control in case that the connection (tempora-
rily) breaks down.
Remote command:
CONFigure:BLUetooth:SIGN<i>:CONNection:SVTimeout
Inquiry Length
Specifies the total duration of the inquiry mode. When this timer elapses (or the maxi-
mum "Number of Inquiry Responses" is reached), inquiry is stopped.
Remote command:
CONFigure:BLUetooth:SIGN<i>:CONNection:INQuiry:ILENgth
Paging Timeout
The maximum time the local link manager waits for a baseband page response from
the DUT, defined in slots of 625 µs. If the timer expires and the remote device has not
responded to the page at baseband level, the connection attempt is considered to have
failed.
Remote command:
CONFigure:BLUetooth:SIGN<i>:CONNection:PAGing:TOUT
Access: "Config" hotkey > "Connection" > "Paging" > "Low Energy" section.
Option R&S CMW-KS601 is required.
Supervision Timeout......................................................................................................89
Connection Interval....................................................................................................... 89
CMW Address............................................................................................................... 90
CMW Address Type...................................................................................................... 90
For Paging.....................................................................................................................90
Default EUT Address.................................................................................................... 90
Test Mode Available...................................................................................................... 90
Test Mode Send Enable with PIN..................................................................................90
Test Mode PIN...............................................................................................................91
Ignore Power Control Capability................................................................................... 91
Slave Latency
Specify the latency of DUT responses for connection tests.
Remote command:
CONFigure:BLUetooth:SIGN<i>:CONNection:SLATency:LESignaling:
CPERipheral
CONFigure:BLUetooth:SIGN<i>:CONNection:SLATency:LESignaling[:
CCENtral]
Supervision Timeout
Specifies the duration of tolerated connection breaks down, to avoid immediate detach.
Remote command:
CONFigure:BLUetooth:SIGN<i>:CONNection:SVTimeout:LESignaling
Connection Interval
Sets the time interval between two consecutive connection events (CONNEC-
TION_REQ).
Remote command:
CONFigure:BLUetooth:SIGN<i>:CONNection:INTerval:LESignaling
CMW Address
Specifies the Bluetooth LE device address (random or public) used by the R&S CMW
when communicating with the DUT. The address also determines the channel hopping
sequence for the piconet.
Remote command:
CONFigure:BLUetooth:SIGN<i>:CONNection:ADDRess:CMW:LESignaling
CONFigure:BLUetooth:SIGN<i>:CONNection:RADDress:CMW:LESignaling?
For Paging
A drop-down list showing all the devices that the R&S CMW found during inquiry plus
the default EUT address.
Remote command:
CONFigure:BLUetooth:SIGN<i>:CONNection:PAGing:PTARget:
LESignaling
CONFigure:BLUetooth:SIGN<i>:CONNection:INQuiry:PTARgets:CATalog:
LESignaling?
Typically, commands ..:BRATe are used for BR physical layer (PHY), ..:EDRate for
EDR PHY, ..:LE1M for LE 1M PHY, ..:LE2M for LE 2M PHY, and ..:LRANge for
LE coded PHY.
Packet Type.................................................................................................................. 92
Payload Length............................................................................................................. 93
Pattern Type..................................................................................................................93
Voice Link > Speech Codec (BR/EDR only)..................................................................94
Poll Period (BR/EDR only)............................................................................................ 94
Whitening (BR/EDR only)..............................................................................................94
Test Packet Sync Word (LE only)..................................................................................95
Packet Type
Defines Bluetooth packet type used by connection links. See also Chapter 2.2.10,
"Bluetooth Signal Characteristics", on page 30.
The packet types for audio (SCO or eSCO connections) can only be selected in the
main view, see Chapter 2.3.1.11, "Signal Characteristics", on page 53.
Table 2-18: Selectable packet types
BR DH1 1 0 to 27
DH3 3 0 to 183
DH5 5 0 to 339
EDR 2-DH1 1 0 to 54
2-DH3 3 0 to 367
2-DH5 5 0 to 679
3-DH1 1 0 to 83
3-DH3 3 0 to 552
3-DH5 5 0 to 1021
1) The payload length in the table denotes the number of user payload bytes.
2) The transmission interval depends on the length of LE burst.
3) Only uncoded LE 1M and LE 2M PHY.
Payload Length
Defines the length of test sequence.
The payload length used for LE connection and operating mode = "Connection" is
always zero.
Option R&S CMW-KS610 is required for BR/EDR in test mode.
For LE direct test mode, option R&S CMW-KS611 is required for LE 1M PHY (unco-
ded). Option R&S CMW-KS721 is also required for LE 2M PHY and LE coded PHY.
For LE with CTE tests, option R&S CMW-KS722 is also required.
For LE connection tests (normal mode) and LE test mode, option R&S CMW-KS601 is
required for LE 1M PHY (uncoded). Option R&S CMW-KS720 is also required for
LE 2M PHY and LE coded PHY.
Remote command:
For BR/EDR in test mode:
CONFigure:BLUetooth:SIGN<i>:CONNection:PACKets:PLENgth:BRATe
CONFigure:BLUetooth:SIGN<i>:CONNection:PACKets:PLENgth:EDRate
For LE direct test mode:
CONFigure:BLUetooth:SIGN<i>:CONNection:PACKets:PLENgth:LENergy[:
LE1M]
CONFigure:BLUetooth:SIGN<i>:CONNection:PACKets:PLENgth:LENergy:
LE2M
CONFigure:BLUetooth:SIGN<i>:CONNection:PACKets:PLENgth:LENergy:
LRANge
For LE test mode:
CONFigure:BLUetooth:SIGN<i>:TCONnection:PACKets:PLENgth:LENergy:
LE1M etc.
Pattern Type
Selects the pattern.
Option R&S CMW-KS610 is required for BR/EDR in test mode.
For LE direct test mode, option R&S CMW-KS611 is required for LE 1M PHY (unco-
ded). Option R&S CMW-KS721 is also required for LE 2M PHY and LE coded PHY.
For LE with CTE tests, option R&S CMW-KS722 is also required.
For LE connection tests (normal mode) and LE test mode, option R&S CMW-KS601 is
required for LE 1M PHY (uncoded). Option R&S CMW-KS720 is also required for
LE 2M PHY and LE coded PHY.
Remote command:
For BR/EDR in test mode:
CONFigure:BLUetooth:SIGN<i>:CONNection:PACKets:PATTern:BRATe
CONFigure:BLUetooth:SIGN<i>:CONNection:PACKets:PATTern:EDRate
For LE direct test mode:
CONFigure:BLUetooth:SIGN<i>:CONNection:PACKets:PATTern:LENergy[:
LE1M]
CONFigure:BLUetooth:SIGN<i>:CONNection:PACKets:PATTern:LENergy:
LE2M
CONFigure:BLUetooth:SIGN<i>:CONNection:PACKets:PATTern:LENergy:
LRANge
For LE test mode:
CONFigure:BLUetooth:SIGN<i>:TCONnection:PACKets:PATTern:LENergy:
LE1M etc.
PIN Code.......................................................................................................................95
Security Mode............................................................................................................... 96
Call is Active at Startup................................................................................................. 96
Audio Link Setup........................................................................................................... 96
└ Codec..............................................................................................................96
└ Sampling Frequency....................................................................................... 96
└ Channel Mode.................................................................................................96
└ Block Length................................................................................................... 96
└ Subbands........................................................................................................96
└ Allocation Method........................................................................................... 97
└ Minimum / Maximum Bitload...........................................................................97
└ Bit Rate........................................................................................................... 97
Assume Acceptor Role in Slave Mode..........................................................................97
PIN Code
Specifies PIN code for an audio connection. The default PIN code 0000 is used by
most devices. Some devices require changing the code.
Remote command:
CONFigure:BLUetooth:SIGN<i>:CONNection:AUDio:PINCode
Security Mode
Specifies security mode for audio tests in master mode.
Remote command:
CONFigure:BLUetooth:SIGN<i>:CONNection:AUDio:SECMode
Remote command:
CONFigure:BLUetooth:SIGN<i>:CONNection:AUDio:A2DP:SUBBands
Mono 320
If the value exceeds the allowed maximum value, two exclamation marks are shown in
the audio link setup area.
Remote command:
CONFigure:BLUetooth:SIGN<i>:CONNection:AUDio:A2DP:BITRate?
Go to...
Selects a measurement. The shortcut softkey opens a dialog presenting this measure-
ment as default target or uses the measurement as fixed target.
● Enabled: The softkey directly opens the measurement selected via Go to....
● Disabled: The softkey opens a dialog box for selection of the target measurement.
2.4 Programming
The following sections provide programming examples for the "Bluetooth Signaling"
application. Note that the parameter values are only examples rather than recommen-
ded values.
The examples contain SCPI commands supported by the R&S CMW and the following
symbolic scripting commands:
● // <comment>:
A <comment> ignored by the used programming tool
● WHILE <query> <> <value>:
Waits until the <query> returns a certain <value>, e.g. a specific state is reached.
● WAITKEY <message>:
Displays a dialog box with a <message> and waits until the box is closed manually.
The "Bluetooth Signaling" application is programmed as follows:
● The application is controlled by SCPI commands with the following syn-
tax: ...:BLUetooth:SIGN:...
● After a *RST, the DL signal is switched off.
To activate the DL signal use SOURce:BLUetooth:SIGN:STATe ON
To query the main state, use
FETCh:BLUetooth:SIGN:CONNection:STATe:ALL?
The result ON,SBY indicates that the Bluetooth signal is available.
● To find discoverable Bluetooth devices, use
CALL:BLUetooth:SIGN:CONNection:ACTion INQuire
To connect to a discovered device, use
CALL:BLUetooth:SIGN:CONNection:ACTion CONNect
To connect in test mode to a discovered device, use
CALL:BLUetooth:SIGN:CONNection:ACTion TMConnect
To query the connection state, use
FETCh:BLUetooth:SIGN:CONNection:STATe?
Commands for LE connection tests use token ...:LESignaling
● After all configuration commands (CONFigure:BLUetooth:SIGN:...), it is rec-
ommended to execute *OPC?. This command guarantees that the configuration
command is finished before performing other actions. Alternatively you can also
execute the query form of a command (CONFigure:BLUetooth:SIGN:...?)
The following sections describe how to configure the signaling application.
The subsequent sections describe how to switch on the master signal and the DUT,
how to set up a connection or a test connection. Some examples for actions possible
after connection setup are also given.
// *****************************************************************************
// Set operating mode to connection test.
// *****************************************************************************
CONFigure:BLUetooth:SIGN:OPMode CNT; *OPC?
// *****************************************************************************
// Configure routing and external attenuation
// *****************************************************************************
ROUTe:BLUetooth:SIGN:SCENario:OTRX RF2C,RX1,RF2C,TX1; *OPC?
CONFigure:BLUetooth:SIGN:RFSettings:EATTenuation:OUTPut 4; *OPC?
CONFigure:BLUetooth:SIGN:RFSettings:EATTenuation:INPut 4; *OPC?
// *****************************************************************************
// Alternativelly configure routing using SUA
// *****************************************************************************
ROUTe:BLUetooth:SIGN:SCENario:OTRX:FLEXible SUA1,RF2C,RX1,RF2C,TX1; *OPC?
// *****************************************************************************
// Disable auto ranging, specify the expected nominal
// power (RX level), TX power level and user margin.
// *****************************************************************************
CONFigure:BLUetooth:SIGN:RFSettings:ARANging OFF; *OPC?
CONFigure:BLUetooth:SIGN:RFSettings:ENPower 7; *OPC?
CONFigure:BLUetooth:SIGN:RFSettings:LEVel -50; *OPC?
CONFigure:BLUetooth:SIGN:RFSettings:UMARgin 1; *OPC?
// *****************************************************************************
// *****************************************************************************
// Specify the burst type and activate enhanced power control.
// *****************************************************************************
CONFigure:BLUetooth:SIGN:CONNection:BTYPe EDR; *OPC?
CONFigure:BLUetooth:SIGN:CONNection:PCONtrol:EPCMode AUTO; *OPC?
Inquire BD address
// *****************************************************************************
// Configure inquiry.
// *****************************************************************************
CONFigure:BLUetooth:SIGN:CONNection:INQuiry:ILENgth 20; *OPC?
CONFigure:BLUetooth:SIGN:CONNection:INQuiry:NOResponses 10; *OPC?
// *****************************************************************************
// Run inquiry.
// *****************************************************************************
CALL:BLUetooth:SIGN:CONNection:ACTion INQuire
WHILE FETCh:BLUetooth:SIGN:CONNection:STATe? <> "SBY"
CONFigure:BLUetooth:SIGN:CONNection:INQuiry:PTARgets:CATalog?
Connect (BR/EDR)
// *****************************************************************************
// Set up the ACL link with the page target device, if necessary
// increase/decrease the DUT power via legacy power control.
// Query the current legacy power control status.
// Query enhanced power control status.
// *****************************************************************************
CALL:BLUetooth:SIGN:CONNection:ACTion CONNect
WHILE FETCh:BLUetooth:SIGN:CONNection:STATe? <> "CONN"
CONFigure:BLUetooth:SIGN:CONNection:PCONtrol:STEP:ACTion UP; *OPC?
SENSe:BLUetooth:SIGN:EUT:PCONtrol:STATe:LEGacy?
SENSe:BLUetooth:SIGN:EUT:PCONtrol:STATe:GFSK?
SENSe:BLUetooth:SIGN:EUT:PCONtrol:STATe:DQPSk?
SENSe:BLUetooth:SIGN:EUT:PCONtrol:STATe:DPSK?
SENSe:BLUetooth:SIGN:EUT:PCONtrol:STATe?
Query results
// *****************************************************************************
// Query all EUT information results (BR/EDR)
// *****************************************************************************
SENSe:BLUetooth:SIGN:EUT:INFormation:NAME?
SENSe:BLUetooth:SIGN:EUT:INFormation:VERSion?
SENSe:BLUetooth:SIGN:EUT:INFormation:COMPany?
SENSe:BLUetooth:SIGN:EUT:INFormation:BDADdress?
SENSe:BLUetooth:SIGN:EUT:INFormation:CLASs?
// *****************************************************************************
// Query all EUT capability results (BR/EDR)
// *****************************************************************************
SENSe:BLUetooth:SIGN:EUT:CAPability:CONNection?
SENSe:BLUetooth:SIGN:EUT:CAPability:ENCRyption?
SENSe:BLUetooth:SIGN:EUT:CAPability:PSAVing?
SENSe:BLUetooth:SIGN:EUT:CAPability:PCONtrol?
SENSe:BLUetooth:SIGN:EUT:CAPability:EPControl?
SENSe:BLUetooth:SIGN:EUT:CAPability:ACL?
SENSe:BLUetooth:SIGN:EUT:CAPability:SCO?
SENSe:BLUetooth:SIGN:EUT:CAPability:ESCO?
SENSe:BLUetooth:SIGN:EUT:CAPability:SCLass?
Query results
// *****************************************************************************
// Query all USB information results
// *****************************************************************************
SENSe:BLUetooth:SIGN:USBDevice:INFormation:DCLass?
SENSe:BLUetooth:SIGN:USBDevice:INFormation:DPRotocol?
SENSe:BLUetooth:SIGN:USBDevice:INFormation:DSUBclass?
SENSe:BLUetooth:SIGN:USBDevice:INFormation:IDPRoduct?
SENSe:BLUetooth:SIGN:USBDevice:INFormation:IDVendor?
SENSe:BLUetooth:SIGN:USBDevice:INFormation:MANufacturer?
SENSe:BLUetooth:SIGN:USBDevice:INFormation:PRODuct?
SENSe:BLUetooth:SIGN:USBDevice:INFormation:SERial?
// *****************************************************************************
// Configure single values of dirty transmitter for LE2M PHY:
// enable frequency drift, set frequency offset, modulation index and
// symbol time error. Specify also drift rate of 1250 Hz.
// Enable dirty transmitter.
//
// Alternatively configure dirty transmitter for LE2M PHY according
// to the test specification. Use standard modulation index and
// drift rate of 625 Hz. Enable dirty transmitter, query all parameters.
// *****************************************************************************
CONFigure:BLUetooth:SIGN:RFSettings:DTX:MODE:LENergy:LE2M SING; *OPC?
CONFigure:BLUetooth:SIGN:RFSettings:DTX:SING:FDRift:LENergy:LE2M ON; *OPC?
CONFigure:BLUetooth:SIGN:RFSettings:DTX:SING:FOFFset:LENergy:LE2M ON; *OPC?
CONFigure:BLUetooth:SIGN:RFSettings:DTX:SING:FOFFset:LENergy:LE2M 250E+3; *OPC?
CONFigure:BLUetooth:SIGN:RXQuality:SMINdex:LENergy OFF; *OPC?
CONFigure:BLUetooth:SIGN:RFSettings:DTX:SING:MINDex:STANdard:LEN:LE2M 0.5; *OPC?
CONFigure:BLUetooth:SIGN:RFSettings:DTX:SING:MINDex:STANdard:LEN:LE2M ON; *OPC?
CONFigure:BLUetooth:SIGN:RFSettings:DTX:SING:STERror:LENergy:LE2M POS50; *OPC?
// *****************************************************************************
// Configure dirty transmitter for LE1M PHY normal mode according
// to the test specification. Enable dirty transmitter, query all parameters.
// *****************************************************************************
CONFigure:BLUetooth:SIGN:RFSettings:DTX:MODE:NMODe:LENergy:LE1M SPEC; *OPC?
CONFigure:BLUetooth:SIGN:RFSettings:DTX ON; *OPC?
CONFigure:BLUetooth:SIGN:RFSettings:DTX:STAB:FDRift:NMODe:LENergy:LE1M?
CONFigure:BLUetooth:SIGN:RFSettings:DTX:STAB:FOFFset:NMODe:LENergy:LE1M?
CONFigure:BLUetooth:SIGN:RFSettings:DTX:STAB:MINDex:NMODe:LENergy:LE1M?
CONFigure:BLUetooth:SIGN:RFSettings:DTX:STAB:STERror:NMODe:LENergy:LE1M?
// *****************************************************************************
// Use only two hopping channels (1 and 11). Select the measured channel 1.
//
// Alternatively use hopping on all chennels. Select the measured channel 1.
// *****************************************************************************
CONFigure:BLUetooth:SIGN:RFSettings:NMODe:HMODe:LENergy CH2; *OPC?
CONFigure:BLUetooth:SIGN:RFSettings:NMODe:MCHannel:LENergy 1; *OPC?
// *****************************************************************************
// For peripheral LE role set slave latency, let indicate encryption support,
// accept encryption request.
// *****************************************************************************
CONFigure:BLUetooth:SIGN:CONNection:CMW:ROLE:LESignaling PERipheral; *OPC?
CONFigure:BLUetooth:SIGN:CONNection:SLATency:LESignaling:CPERipheral 10
CONFigure:BLUetooth:SIGN:CONNection:IENCryption:LESignaling:CPERipheral ON
CONFigure:BLUetooth:SIGN:CONNection:RENCryption:LESignaling:CPERipheral OFF
// *****************************************************************************
// Query random address of instrument. Set instrument address
// type and its public address.
// *****************************************************************************
CONFigure:BLUetooth:SIGN:CONNection:RADDress:CMW:LESignaling?
CONFigure:BLUetooth:SIGN:CONNection:ADDRess:TYPE:LESignaling PUBLic; *OPC?
CONFigure:BLUetooth:SIGN:CONNection:ADDRess:CMW:LESignaling #H123456789ABC; *OPC?
// *****************************************************************************
// Either configure and perform an inquiry to find the DUT,
// or manually specify the DUT by its BD address
// *****************************************************************************
Configure inquiry
CONFigure:BLUetooth:SIGN:CONNection:INQuiry:DURation:LESignaling 10240
CONFigure:BLUetooth:SIGN:CONNection:INQuiry:NOResponses:LESignaling 10; *OPC?
CONFigure:BLUetooth:SIGN:CONNection:INQuiry:SINTerval:LESignaling 48; *OPC?
CONFigure:BLUetooth:SIGN:CONNection:INQuiry:SWINdow:LESignaling 48; *OPC?
// *****************************************************************************
// Run inquiry.
// *****************************************************************************
CALL:BLUetooth:SIGN:CONNection:ACTion:LESignaling INQuire
WHILE FETCh:BLUetooth:SIGN:CONNection:STATe:LESignaling? <> "SBY"
CONFigure:BLUetooth:SIGN:CONNection:INQuiry:PTARgets:CATalog:LESignaling?
Configure paging
// *****************************************************************************
// Configure the ACL link: supervision timeout, scan interval, scan window,
// paging timeout, connection interval, use default EUT. Set the connection
// for channel map change.
// *****************************************************************************
CONFigure:BLUetooth:SIGN:CONNection:SVTimeout:LESignaling 10000; *OPC?
CONFigure:BLUetooth:SIGN:CONNection:SINTerval:LESignaling 48; *OPC?
CONFigure:BLUetooth:SIGN:CONNection:SWINdow:LESignaling 48; *OPC?
CONFigure:BLUetooth:SIGN:CONNection:PAGing:TOUT:LESignaling 10; *OPC?
CONFigure:BLUetooth:SIGN:CONNection:INTerval:LESignaling 200; *OPC?
CONFigure:BLUetooth:SIGN:CONNection:PAGing:PTARget:LESignaling 0; *OPC?
CONFigure:BLUetooth:SIGN:CONNection:WFCMap:LESignaling:CCENtral 10
// *****************************************************************************
// For peripheral role set advertiser interval.
// *****************************************************************************
CONFigure:BLUetooth:SIGN:CONNection:AINTerval:LESignaling 160
Configure dirty transmitter for LE connection tests, see Chapter 2.4.7, "Configure Dirty
Transmitter", on page 104.
Connect
// *****************************************************************************
// Set up the ACL link with the page target device. Query connection settings.
// *****************************************************************************
CALL:BLUetooth:SIGN:CONNection:ACTion:LESignaling CONNect
WHILE FETCh:BLUetooth:SIGN:CONNection:STATe:LESignaling? <> "CONN"
SENSe:BLUetooth:SIGN:EUT:CSETtings:LESignaling?
Query results
// *****************************************************************************
// Query all EUT information results (LE)
// *****************************************************************************
SENSe:BLUetooth:SIGN:EUT:INFormation:LESignaling?
SENSe:BLUetooth:SIGN:EUT:CAPability:LESignaling?
/// *****************************************************************************
// Enable hopping, enable the user defined adaptive frequency hopping.
// *****************************************************************************
CONFigure:BLUetooth:SIGN:RFSettings:HOPPing ON; *OPC?
CONFigure:BLUetooth:SIGN:RFSettings:AFHopping ON, USER; *OPC?
// *****************************************************************************
// Set packet type, packet length and pattern type for basic
// rate packets.
// Alternatively configure EDR packets.
// Alternatively configure LE packets.
// *****************************************************************************
CONFigure:BLUetooth:SIGN:CONNection:PACKets:PTYPe:BRATe DH3; *OPC?
CONFigure:BLUetooth:SIGN:CONNection:PACKets:PATTern:BRATe PRBS9; *OPC?
CONFigure:BLUetooth:SIGN:CONNection:PACKets:PLENgth:BRATe 21,183,339
*OPC?
// *****************************************************************************
// Specify delay for test mode activation.
// *****************************************************************************
CONFigure:BLUetooth:SIGN:DELay:TMODe 2
// *****************************************************************************
// Display used channels by adaptive hopping.
// *****************************************************************************
SENSe:BLUetooth:SIGN:CMAP?
// *****************************************************************************
// Perform TX or RX tests.
// TX test: perform TX measurements using Bluetooth measurement
// application in combined signal path
// RX test: perform RX measurements
// *****************************************************************************
// *****************************************************************************
// Perform Tx measurement with the Bluetooth measurement firmware application.
// Close the connection.
// *****************************************************************************
CALL:BLUetooth:SIGN:CONNection:ACTion DET
WHILE FETCh:BLUetooth:SIGN:CONNection:STATe? <> "SBY"
// *****************************************************************************
// Alternativelly specify LE coded physical layer and
// its coding.
// *****************************************************************************
CONFigure:BLUetooth:SIGN:CONNection:BTYPe LE; *OPC?
CONFigure:BLUetooth:SIGN:CONNection:PHY:LENergy LELR; *OPC?
CONFigure:BLUetooth:SIGN:CONNection:FEC:LENergy:LRANge S8
// *****************************************************************************
// Alternatively configure LE test packets with CTE: set packet type,
// number of antennas, offset of external attenuation
// for non-reference antennas. Set gain offset for LE 1M PHY.
//
// Specify CTE type AoD 2 μs and number of CTE units.
// *****************************************************************************
CONFigure:BLUetooth:SIGN:CONNection:PACKets:PTYPe:LENergy:LE1M RFCTe; *OPC?
CONFigure:BLUetooth:SIGN:RFSettings:NANTenna:CTE:LENergy 2; *OPC?
CONFigure:BLUetooth:SIGN:RFSettings:AOFFset:INPut:CTE:LENergy 1,1,1; *OPC?
CONFigure:BLUetooth:SIGN:RFSettings:AOFFset:OUTPut:CTE:LENergy 1,1,1; *OPC?
CONFigure:BLUetooth:SIGN:RFSettings:GOFFset:CTE:LENergy:LE1M -1,-1,-1; *OPC?
// *****************************************************************************
// Switch instrument to standby state.
// Reset EUT, verify the connection for direct test.
// *****************************************************************************
SOURce:BLUetooth:SIGN:STATe ON
CALL:BLUetooth:SIGN:LENergy:RESet
CALL:BLUetooth:SIGN:CONNection:CHECk:LENergy?
// *****************************************************************************
// Perform TX or RX tests.
// TX test: perform TX measurements using Bluetooth Measurement
// application in combined signal path
// RX test: perform RX measurements
// *****************************************************************************
// *****************************************************************************
// Set the RF channel for LE test mode, query the corresponding frequency.
// *****************************************************************************
CONFigure:BLUetooth:SIGN:RFSettings:CHANnel:TMODe 11; *OPC?
CONFigure:BLUetooth:SIGN:RFSettings:FREQuency:TMODe?
// *****************************************************************************
// Connection settings for LE test mode: physical layer, coding, connection
// interval, pattern, payload length and PIN code. Enable test mode at the DUT.
// *****************************************************************************
CONFigure:BLUetooth:SIGN:TCONnection:PHY:LENergy LELR; *OPC?
CONFigure:BLUetooth:SIGN:TCONnection:FEC:LENergy:LRANge S8; *OPC?
CONFigure:BLUetooth:SIGN:TCONnection:INTerval:LESignaling 6; *OPC?
CONFigure:BLUetooth:SIGN:TCONnection:PACKets:PATTern:LENergy:LRANge P11; *OPC?
CONFigure:BLUetooth:SIGN:TCONnection:PACKets:PLENgth:LENergy:LRANge 37; *OPC?
CONFigure:BLUetooth:SIGN:TCONnection:PINCode:LENergy 25,10,11,25; *OPC?
CONFigure:BLUetooth:SIGN:TCONnection:SPINenable:LENergy ON
// *****************************************************************************
// Configure dirty TX according to the specification, standard modulation
// index, high drift rate. Enable dirty transmitter.
// *****************************************************************************
CONFigure:BLUetooth:SIGN:RFSettings:DTX:MODE:TMODe:LENergy:LRANge SPEC; *OPC?
CONFigure:BLUetooth:SIGN:RFSettings:DTX:MINDex:MODE:TMODe:LENergy:LRANge STAN
CONFigure:BLUetooth:SIGN:RFSettings:DTX:MODFrequency:TMODe:LENergy:LRANge HDRF
CONFigure:BLUetooth:SIGN:RFSettings:DTX ON; *OPC?
// *****************************************************************************
// Enable LE test mode at the instrument.
// *****************************************************************************
CONFigure:BLUetooth:SIGN:TMODe ON; *OPC?
// *****************************************************************************
// Perform TX tests: perform TX measurements using Bluetooth measurement
// application in combined signal path
// *****************************************************************************
// *****************************************************************************
// Establish a connection in audio echo mode.
// *****************************************************************************
CALL:BLUetooth:SIGN:CONNection:ACTion EMConnect
WHILE FETCh:BLUetooth:SIGN:CONNection:STATe? <> "ECON"
// *****************************************************************************
// Establish an audio connection, if necessary increase/decrease
// microphone gain and speaker volume. Query the audio link parameters.
// *****************************************************************************
CALL:BLUetooth:SIGN:CONNection:ACTion HFPConnect
WHILE FETCh:BLUetooth:SIGN:CONNection:STATe? <> "HFC"
CONFigure:BLUetooth:SIGN:CONNection:AUDio:VOLControl:MICGain 8; *OPC?
CONFigure:BLUetooth:SIGN:CONNection:AUDio:VOLControl:SPEaker 6; *OPC?
SENSe:BLUetooth:SIGN:CONNection:AUDio:LINFo?
/ *****************************************************************************
// Change audio profile role to A2DP, set audio link parameters: codec,
// .
// *****************************************************************************
CONFigure:BLUetooth:SIGN:OPMode PROF; *OPC?
CONFigure:BLUetooth:SIGN:AUDio:PRFRole ASINk; *OPC?
CONFigure:BLUetooth:SIGN:CONNection:AUDio:A2DP:CODec SBC; *OPC?
CONFigure:BLUetooth:SIGN:CONNection:AUDio:A2DP:SMPFrequency SF48; *OPC?
CONFigure:BLUetooth:SIGN:CONNection:AUDio:A2DP:CHMode JST; *OPC?
CONFigure:BLUetooth:SIGN:CONNection:AUDio:A2DP:BLKLength BL12; *OPC?
// *****************************************************************************
// Establish an audio connection, if necessary increase/decrease microphone
// gain and speaker volume. Query the audio link parameters and bit rate.
// *****************************************************************************
CALL:BLUetooth:SIGN:CONNection:ACTion ADConnect
WHILE FETCh:BLUetooth:SIGN:CONNection:STATe? <> "A2Connected"
CONFigure:BLUetooth:SIGN:CONNection:AUDio:VOLControl:MICGain 8; *OPC?
CONFigure:BLUetooth:SIGN:CONNection:AUDio:VOLControl:SPEaker 6; *OPC?
SENSe:BLUetooth:SIGN:CONNection:AUDio:LINFo?
CONFigure:BLUetooth:SIGN:CONNection:AUDio:A2DP:BITRate?
The following sections describe the most important conventions and general informa-
tion concerning the command reference.
2.5.1.1 SIGN<i>
Which connectors and modules can be specified in a command, depends on the instal-
led hardware and the active subinstrument or instance <i>.
This chapter lists all values available for path selection. Depending on your configura-
tion, only a subset is relevant for you. Virtual connector names are only relevant for
setting commands. Queries return the physical connector names.
Additional information is available in the base software documentation. It describes typ-
ical instrument configurations with the allowed RF connector - TX/RX module combina-
tions and the mapping of virtual connector names to physical connectors.
Single-CMW setup
Selection values:
● Signaling unit SUU:
SUU1 | SUU2 | SUU3 | SUU4
● Signaling unit SUA:
SUA1 | SUA2 | SUA3 | SUA4 | SUA5 | SUA6
SUA partition 1, 2, 3, 4, 5, 6
● RX module:
RX1 | RX2 | RX3 | RX4
● TX module:
TX1 | TX2 | TX3 | TX4
● RX connector:
RF1C | RF2C | RF3C | RF4C | RFAC | RFBC
RF 1 COM to RF 4 COM plus virtual connector names
● TX connector:
RF1C | RF2C | RF3C | RF4C | RFAC | RFBC
RF1O | RF3O | RFAO
RF 1 COM to RF 4 COM plus virtual connector names
RF 1 OUT and RF 3 OUT plus virtual connector name
2.5.1.3 Keywords
Selected keywords used in the command description are described in the following.
● Command usage
If the usage is not explicitly stated, the command allows you to set parameters and
query parameters. Otherwise, the command usage is stated as follows:
– "Setting only": The command can only be used to set parameters.
– "Query only": The command can only be used to query parameters.
– "Event": The command initiates an event.
● Parameter usage
The parameter usage is indicated by the keyword preceding the parameters:
– "Parameters" are sent with a setting or query command and are returned as
the result of a query.
The following commands provide main signal settings for Rx and Tx signals.
CONFigure:BLUetooth:SIGN<i>:CONNection:BTYPe........................................................ 117
CONFigure:BLUetooth:SIGN<i>:CONNection:FEC:NMODe:LENergy:LRANge..................... 117
CONFigure:BLUetooth:SIGN<i>:TCONnection:FEC:LENergy:LRANge................................ 117
CONFigure:BLUetooth:SIGN<i>:CONNection:FEC:LENergy:LRANge..................................117
CONFigure:BLUetooth:SIGN<i>:CONNection:PHY:NMODe:LENergy.................................. 118
CONFigure:BLUetooth:SIGN<i>:TCONnection:PHY:LENergy............................................. 118
CONFigure:BLUetooth:SIGN<i>:CONNection:PHY:LENergy...............................................118
CONFigure:BLUetooth:SIGN<i>:STANdard.......................................................................118
CONFigure:BLUetooth:SIGN<i>:CONNection:PACKets:PATTern:BRATe.............................. 118
CONFigure:BLUetooth:SIGN<i>:CONNection:PACKets:PATTern:EDRate............................ 118
CONFigure:BLUetooth:SIGN<i>:TCONnection:PACKets:PATTern:LENergy:LRANge.............118
CONFigure:BLUetooth:SIGN<i>:TCONnection:PACKets:PATTern:LENergy:LE2M................ 118
CONFigure:BLUetooth:SIGN<i>:TCONnection:PACKets:PATTern:LENergy:LE1M................ 118
CONFigure:BLUetooth:SIGN<i>:CONNection:PACKets:PATTern:LENergy:LE2M..................119
CONFigure:BLUetooth:SIGN<i>:CONNection:PACKets:PATTern:LENergy[:LE1M]................ 119
CONFigure:BLUetooth:SIGN<i>:CONNection:PACKets:PATTern:LENergy:LRANge.............. 119
CONFigure:BLUetooth:SIGN<i>:CONNection:PACKets:PLENgth:BRATe.............................120
CONFigure:BLUetooth:SIGN<i>:CONNection:PACKets:PLENgth:EDRate........................... 120
CONFigure:BLUetooth:SIGN<i>:TCONnection:PACKets:PLENgth:LENergy:LRANge............121
CONFigure:BLUetooth:SIGN<i>:TCONnection:PACKets:PLENgth:LENergy:LE2M............... 121
CONFigure:BLUetooth:SIGN<i>:TCONnection:PACKets:PLENgth:LENergy:LE1M............... 121
CONFigure:BLUetooth:SIGN<i>:CONNection:PACKets:PLENgth:LENergy:LRANge............. 121
CONFigure:BLUetooth:SIGN<i>:CONNection:PACKets:PLENgth:LENergy:LE2M.................121
CONFigure:BLUetooth:SIGN<i>:CONNection:PACKets:PLENgth:LENergy[:LE1M]............... 121
CONFigure:BLUetooth:SIGN<i>:CONNection:PACKets:PTYPe:BRATe................................121
CONFigure:BLUetooth:SIGN<i>:CONNection:PACKets:PTYPe:EDRate.............................. 122
CONFigure:BLUetooth:SIGN<i>:CONNection:PACKets:PTYPe:ESCO................................ 123
CONFigure:BLUetooth:SIGN<i>:CONNection:PACKets:PTYPe:SCO.................................. 123
CONFigure:BLUetooth:SIGN<i>:CONNection:PACKets:PTYPe:LENergy:LE2M................... 123
CONFigure:BLUetooth:SIGN<i>:CONNection:PACKets:PTYPe:LENergy[:LE1M]..................123
CONFigure:BLUetooth:SIGN<i>:CONNection:PACKets:TYPE:CTE:LENergy:LE1M..............123
CONFigure:BLUetooth:SIGN<i>:CONNection:PACKets:TYPE:CTE:LENergy:LE2M..............123
CONFigure:BLUetooth:SIGN<i>:CONNection:PACKets:UNITs:CTE:LENergy:LE1M............. 124
CONFigure:BLUetooth:SIGN<i>:CONNection:PACKets:UNITs:CTE:LENergy:LE2M............. 124
CONFigure:BLUetooth:SIGN<i>:CONNection:FEC:NMODe:LENergy:LRANge
<CodingScheme>
CONFigure:BLUetooth:SIGN<i>:TCONnection:FEC:LENergy:LRANge
<CodingScheme>
CONFigure:BLUetooth:SIGN<i>:CONNection:FEC:LENergy:LRANge
<CodingScheme>
Defines the coding S for LE coded PHY according to the core specification version 5.0
for Bluetooth wireless technology.
● Command for LE direct test mode: ..:FEC:LENergy..
● Command for LE connection tests (normal mode): ..:FEC:NMODe:LENergy..
● Command for LE test mode: ..:TCONnection:FEC:LENergy..
Parameters:
<CodingScheme> S8 | S2
Coding S = 8 or S = 2
*RST: S8
Example: See Direct test mode
Firmware/Software: V3.5.70, V3.7.80: added command for LE connection tests
V3.7.90: added command for LE test mode
Options: R&S CMW-KS721 for LE direct test mode
R&S CMW-KS720 for LE connection tests and LE test mode
Manual operation: See "Coding Scheme (LE > Long Range)" on page 70
CONFigure:BLUetooth:SIGN<i>:CONNection:PHY:NMODe:LENergy <PHY>
CONFigure:BLUetooth:SIGN<i>:TCONnection:PHY:LENergy <PHY>
CONFigure:BLUetooth:SIGN<i>:CONNection:PHY:LENergy <PHY>
Selects the physical layer used for LE connections.
● Command for LE direct test mode: ..:PHY:LENergy
● Command for LE connection tests (normal mode): ..:PHY:NMODe:LENergy
● Command for LE test mode: ..:TCONnection:PHY:LENergy
Parameters:
<PHY> LE1M | LE2M | LELR
LE1M: LE 1 Msymbol/s uncoded PHY
LE2M: LE 2 Msymbol/s uncoded PHY
LELR: LE 1 Msymbol/s long range (LE coded PHY)
*RST: LE1M
Example: See Direct test mode
Firmware/Software: V3.5.70, V3.7.80: added command for LE connection tests
V3.7.90: added command for LE test mode
Options: R&S CMW-KS721 for LE2M and LELR direct test mode
R&S CMW-KS720 for LE2M and LELR connection tests and LE
test mode
Manual operation: See "PHY (LE)" on page 69
CONFigure:BLUetooth:SIGN<i>:STANdard <SigStd>
Selects classic (BR/EDR) or low energy (LE) bursts.
Parameters:
<SigStd> CLASsic | LESignaling
*RST: CLAS
Example: See Connect LE (Normal Mode)
Firmware/Software: V3.7.50
Manual operation: See "Standard" on page 66
CONFigure:BLUetooth:SIGN<i>:CONNection:PACKets:PATTern:BRATe <Pattern
Type>
CONFigure:BLUetooth:SIGN<i>:CONNection:PACKets:PATTern:EDRate <Pattern
Type>
CONFigure:BLUetooth:SIGN<i>:TCONnection:PACKets:PATTern:LENergy:
LRANge <Pattern Type>
CONFigure:BLUetooth:SIGN<i>:TCONnection:PACKets:PATTern:LENergy:LE2M
<Pattern Type>
CONFigure:BLUetooth:SIGN<i>:TCONnection:PACKets:PATTern:LENergy:LE1M
<Pattern Type>
CONFigure:BLUetooth:SIGN<i>:CONNection:PACKets:PATTern:LENergy:LE2M
<Pattern Type>
CONFigure:BLUetooth:SIGN<i>:CONNection:PACKets:PATTern:LENergy[:LE1M]
<Pattern Type>
Select the bit pattern to be used for tests.
● Commands for test mode classic:
For BR (...:BRATe...), EDR (...:EDRate...)
● Commands for LE direct test mode:
For LE 1M PHY (...:LE1M...), LE 2M PHY (...:LE2M...)
● Commands for LE test mode: ..:TCONnection:..
Parameters:
<Pattern Type> ALL0 | ALL1 | P11 | P44 | PRBS9 | ALT
ALL0: 00000000
ALL1: 11111111
P11: 10101010
P44: 11110000
PRBS9: pseudo-random bit sequences of a length of 9 bits
(transmission of identical packet series)
ALT: the periodical alternation of the pattern P11 and P44
*RST: P11
Example: See Configure Test Mode Classic
Firmware/Software: V3.2.30, V3.5.30: added pattern ALT, V3.2.70: added command
for LE1M, V3.5.70: added commands for LE2M,
V3.7.90: added commands for LE test mode
Options: R&S CMW-KS610 for BR/EDR
R&S CMW-KS611 for LE direct test mode
Plus R&S CMW-KS721 for LE2M
R&S CMW-KS601 for LE test mode
Plus R&S CMW-KS720 for LE2M and LRANge
Manual operation: See "Pattern Type" on page 93
CONFigure:BLUetooth:SIGN<i>:CONNection:PACKets:PATTern:LENergy:
LRANge <Pattern Type>
Select the bit pattern to be used for tests on LE coded PHY.
Parameters:
<Pattern Type> ALL1 | P11 | P44 | PRBS9
ALL1: 11111111
P11: 10101010
P44: 11110000
PRBS9: pseudo-random bit sequences of a length of 9 bits
(transmission of identical packet series)
*RST: ALL1
CONFigure:BLUetooth:SIGN<i>:CONNection:PACKets:PLENgth:BRATe
<PayloadLength>(3)
Sets the payload length for BR test mode.
Parameters:
<PayloadLength> numeric
Range: Three values, see table below
*RST: 27 byte(s)
Example: See Configure Test Mode Classic
Firmware/Software: V3.2.30
Options: R&S CMW-KS610
Manual operation: See "Payload Length" on page 93
Table 2-20: Payload length depending on packet type
CONFigure:BLUetooth:SIGN<i>:CONNection:PACKets:PLENgth:EDRate
<PayloadLength>(6)
Sets the payload length for EDR test mode.
Parameters:
<PayloadLength> numeric
Range: Six values, see table below
*RST: 54 byte(s)
Example: See Configure Test Mode Classic
Firmware/Software: V3.2.30
Options: R&S CMW-KS610
Manual operation: See "Payload Length" on page 93
Table 2-21: Payload length depending on packet type
CONFigure:BLUetooth:SIGN<i>:TCONnection:PACKets:PLENgth:LENergy:
LRANge <PayloadLength>
CONFigure:BLUetooth:SIGN<i>:TCONnection:PACKets:PLENgth:LENergy:LE2M
<PayloadLength>
CONFigure:BLUetooth:SIGN<i>:TCONnection:PACKets:PLENgth:LENergy:LE1M
<PayloadLength>
CONFigure:BLUetooth:SIGN<i>:CONNection:PACKets:PLENgth:LENergy:
LRANge <PayloadLength>
CONFigure:BLUetooth:SIGN<i>:CONNection:PACKets:PLENgth:LENergy:LE2M
<PayloadLength>
CONFigure:BLUetooth:SIGN<i>:CONNection:PACKets:PLENgth:LENergy[:LE1M]
<PayloadLength>
Specifies the payload length.
● Commands for LE direct test mode:
For LE 1M PHY (...:LE1M...), LE 2M PHY (...:LE2M...), and LE coded
PHY (...:LRANge...).
● Commands for LE test mode: ..:TCONnection:..
Parameters:
<PayloadLength> numeric
Range: 0 byte(s) to 255 byte(s)
*RST: 37 byte(s)
Default unit: byte
Example: See Configure Test Mode Classic
Firmware/Software: V3.2.70, V3.5.20: range extended, V3.5.70: added commands
for LE2M and LRANge
V3.7.90: added commands for LE test mode
Options: R&S CMW-KS611 for LE direct test mode
Plus R&S CMW-KS721 for LE2M and LRANge
R&S CMW-KS601 for LE test mode
Plus R&S CMW-KS720 for LE2M and LRANge
Manual operation: See "Payload Length" on page 93
CONFigure:BLUetooth:SIGN<i>:CONNection:PACKets:PTYPe:BRATe <Packet
Type>
Sets the BR packet type.
Parameters:
<Packet Type> DH1 | DH3 | DH5
Data – high rate packet carrying information bytes plus a 16-bit
CRC code, see table below.
*RST: DH1
Example: See Configure Test Mode Classic
Firmware/Software: V3.2.30
Options: R&S CMW-KS610
Manual operation: See "Packet Type" on page 92
DH1 27 1
DH3 183 3
DH5 339 5
CONFigure:BLUetooth:SIGN<i>:CONNection:PACKets:PTYPe:EDRate <Packet
Type>
Sets the EDR packet type.
Parameters:
<Packet Type> E21P | E23P | E25P | E31P | E33P | E35P
Data – high rate packet carrying information bytes plus a 16-bit
CRC code, see table below.
*RST: E21P
Example: See Configure Test Mode Classic
Firmware/Software: V3.2.30
Options: R&S CMW-KS610
Manual operation: See "Packet Type" on page 92
E21P: 2-DH1 54 1
E31P: 3-DH1 83 1
CONFigure:BLUetooth:SIGN<i>:CONNection:PACKets:PTYPe:ESCO
<PacketType>
CONFigure:BLUetooth:SIGN<i>:CONNection:PACKets:PTYPe:SCO <PacketType>
CONFigure:BLUetooth:SIGN<i>:CONNection:PACKets:PTYPe:LENergy:LE2M
<Packet Type>
CONFigure:BLUetooth:SIGN<i>:CONNection:PACKets:PTYPe:LENergy[:LE1M]
<Packet Type>
Specifies the type of the LE test packet.
Commands for uncoded LE 1M PHY (..:LE1M..) and LE 2M PHY (..:LE2M..) are
available.
Parameters:
<Packet Type> RFPHytest | RFCTe
"RFPHytest": test packet according to Bluetooth specification
up to version 5.0
"RFCTe": test packet with CTE according to Bluetooth specifica-
tion version 5.1
Example: See Direct test mode
Firmware/Software: V3.7.70
Options: R&S CMW-KS611
R&S CMW-KS722 for RFCTe
Manual operation: See "Packet Type" on page 92
CONFigure:BLUetooth:SIGN<i>:CONNection:PACKets:TYPE:CTE:LENergy:LE1M
<CTE_Type>
CONFigure:BLUetooth:SIGN<i>:CONNection:PACKets:TYPE:CTE:LENergy:LE2M
<CTE_Type>
Selects the CTE type.
Commands for uncoded LE 1M PHY (..:LE1M..) and LE 2M PHY (..:LE2M..) are
available.
Parameters:
<CTE_Type> AOA2us | AOD1us | AOD2us | AOA1us
AOA1us: angle of arrival 1 µs
AOA2us: angle of arrival 2 µs
AOD1us: angle of departure 1 µs
AOD2us: angle of departure 2 µs
*RST: AOA2
Example: See Configure Test Mode Classic
Firmware/Software: V3.7.70, V3.7.80: added AOAus
V3.7.90: removed AOAus, added AOA1us
Options: R&S CMW-KS722
Manual operation: See "CTE Type" on page 54
CONFigure:BLUetooth:SIGN<i>:CONNection:PACKets:UNITs:CTE:LENergy:
LE1M <CTE_Units>
CONFigure:BLUetooth:SIGN<i>:CONNection:PACKets:UNITs:CTE:LENergy:
LE2M <CTE_Units>
Sets the number of CTE units. One CTE unit corresponds to 8 μs.
Commands for uncoded LE 1M PHY (..:LE1M..) and LE 2M PHY (..:LE2M..) are
available.
Parameters:
<CTE_Units> integer
Range: 2 to 20
*RST: 20
Example: See Configure Test Mode Classic
Firmware/Software: V3.7.70
Options: R&S CMW-KS722
Manual operation: See "CTE Units" on page 54
2.5.3 RF Settings
The following commands configure the signal input and output paths.
CONFigure:BLUetooth:SIGN<i>:RFSettings:EATTenuation:INPut....................................... 124
CONFigure:BLUetooth:SIGN<i>:RFSettings:EATTenuation:OUTPut....................................125
CONFigure:BLUetooth:SIGN<i>:RFSettings:AOFFset:INPut:CTE:LENergy..........................125
CONFigure:BLUetooth:SIGN<i>:RFSettings:AOFFset:OUTPut:CTE:LENergy...................... 125
CONFigure:BLUetooth:SIGN<i>:RFSettings:GOFFset:CTE:LENergy:LE1M......................... 126
CONFigure:BLUetooth:SIGN<i>:RFSettings:GOFFset:CTE:LENergy:LE2M......................... 126
ROUTe:BLUetooth:SIGN<i>:SCENario:OTRX...................................................................126
ROUTe:BLUetooth:SIGN<i>:SCENario:OTRX:FLEXible.....................................................127
CONFigure:BLUetooth:SIGN<i>:RFSettings:EATTenuation:INPut <ExternalAtt>
Defines an external attenuation (or gain, if the value is negative), to be applied to the
input connector.
Parameters:
<ExternalAtt> numeric
Range: -50 dB to 90 dB
*RST: 0 dB
Default unit: dB
Example: See Initialization and Basic Configuration
Firmware/Software: V3.0.12
Manual operation: See "External Attenuation" on page 74
CONFigure:BLUetooth:SIGN<i>:RFSettings:EATTenuation:OUTPut <ExternalAtt>
Defines an external attenuation (or gain, if the value is negative), to be applied to the
output connector.
Parameters:
<ExternalAtt> numeric
Range: -50 dB to 90 dB
*RST: 0 dB
Default unit: dB
Example: See Initialization and Basic Configuration
Firmware/Software: V3.0.12
Manual operation: See "External Attenuation" on page 74
CONFigure:BLUetooth:SIGN<i>:RFSettings:AOFFset:INPut:CTE:LENergy
<Ant1InAttOffset>, <Ant2InAttOffset>, <Ant3InAttOffset>
CONFigure:BLUetooth:SIGN<i>:RFSettings:AOFFset:OUTPut:CTE:LENergy
<Ant1OutAtOffset>, <Ant2OutAtOffset>, <Ant3OutAtOffset>
Specifies the offset of external attenuation per EUT antenna relative to the reference
antenna. For the reference antenna, the offset is fixed and set to 0 dB.
The commands for input and output path are available.
An SUA is required.
Parameters:
<Ant1OutAtOffset> numeric
Range: -3 dB to 3 dB
*RST: 0 dB
<Ant2OutAtOffset> numeric
Range: -3 dB to 3 dB
*RST: 0 dB
<Ant3OutAtOffset> numeric
Range: -3 dB to 3 dB
*RST: 0 dB
CONFigure:BLUetooth:SIGN<i>:RFSettings:GOFFset:CTE:LENergy:LE1M
<Ant1GainOffset>, <Ant2GainOffset>, <Ant3GainOffset>
CONFigure:BLUetooth:SIGN<i>:RFSettings:GOFFset:CTE:LENergy:LE2M
<Ant1GainOffset>, <Ant2GainOffset>, <Ant3GainOffset>
Specifies the gain offset for non-reference antennas relative to the gain (or attenuation)
of reference antenna for IQ sample dynamic range measurements.
Commands for uncoded LE 1M PHY (..:LE1M..) and LE 2M PHY (..:LE2M..) are
available.
Parameters:
<Ant1GainOffset> numeric
Range: -20 dB to 6 dB
*RST: 0 dB
<Ant2GainOffset> numeric
Range: -20 dB to 6 dB
*RST: 0 dB
<Ant3GainOffset> numeric
Range: -20 dB to 6 dB
*RST: 0 dB
Example: See Direct test mode
Firmware/Software: V3.7.70
Options: R&S CMW-KS722
Manual operation: See "Gain Offset" on page 300
ROUTe:BLUetooth:SIGN<i>:SCENario:OTRX:FLEXible <BBBoard>,
<RXConnector>, <RXConverter>, <TXConnector>, <TXConverter>
Activates the scenario with one output and one input signal paths.
For possible signaling unit, connector and converter values, see Chapter 2.5.1.2, "Val-
ues for Signal Path Selection", on page 114.
Parameters:
<BBBoard> Signaling unit
<RXConnector> RF connector for the input path
<RXConverter> RX module for the input path
<TXConnector> RF connector for the output path
<TXConverter> TX module for the output path
Example: See Initialization and Basic Configuration
Manual operation: See "Unit" on page 65
CONFigure:BLUetooth:SIGN<i>:RFSettings:CHANnel:DTMode <RxTxChan>
Configures the channel number for direct test mode.
Parameters:
<RxTxChan> numeric
Range: 0 Ch to 39 Ch
*RST: 0 Ch
CONFigure:BLUetooth:SIGN<i>:RFSettings:CHANnel:LOOPback <RxChan>,
<TxChan>
Defines the channels used by the loopback test.
Parameters:
<RxChan> numeric
Range: 0 Ch to 78 Ch
*RST: 0 Ch
<TxChan> numeric
Range: 0 Ch to 78 Ch
*RST: 78 Ch
Example: See Loopback test mode
Firmware/Software: V3.2.30
Options: R&S CMW-KS610
Manual operation: See "Channel, Frequency " on page 75
CONFigure:BLUetooth:SIGN<i>:RFSettings:CHANnel:TMODe <RxTxChan>
Sets the RF channel for LE test mode. This mode supports both data and advertising
channels.
Parameters:
<RxTxChan> numeric
Channel number
Range: 0 Ch to 39 Ch
*RST: 0 Ch
Example: See Configure LE Test Mode
Firmware/Software: V3.7.90
Options: R&S CMW-KS601
Manual operation: See "Channel, Frequency " on page 75
CONFigure:BLUetooth:SIGN<i>:RFSettings:CHANnel:TXTest <RxTxChan>
Defines the channels used by the TX test.
Parameters:
<RxTxChan> numeric
Range: 0 Ch to 78 Ch
*RST: 0 Ch
Example: See Transmitter test mode
Firmware/Software: V3.2.30
Options: R&S CMW-KS610
Manual operation: See "Channel, Frequency " on page 75
CONFigure:BLUetooth:SIGN<i>:RFSettings:FREQuency:TMODe?
Queries the frequency used for LE test mode.
Return values:
<RxTxFreq> float
Range: 100E+6 Hz to 6E+9 Hz
Example: See Configure LE Test Mode
Usage: Query only
Firmware/Software: V3.7.90
Options: R&S CMW-KS601
Manual operation: See "Channel, Frequency " on page 75
CONFigure:BLUetooth:SIGN<i>:RFSettings:FREQuency:DTMode?
Queries the frequency used for direct test mode.
Return values:
<RxTxFreq> float
Range: 100E+6 Hz to 6E+9 Hz
Example: See Direct test mode
Usage: Query only
Firmware/Software: V3.2.70
Options: R&S CMW-KS611
Manual operation: See "Channel, Frequency " on page 75
CONFigure:BLUetooth:SIGN<i>:RFSettings:FREQuency:LOOPback?
Queries EUT RX and EUT TX frequencies used by the loopback test.
Return values:
<RxFreq> float
Range: 2402 MHz to 2480 MHz
Default unit: Hz
<TxFreq> float
Range: 2402 MHz to 2480 MHz
Default unit: Hz
Example: See Loopback test mode
Usage: Query only
Firmware/Software: V3.2.30
Options: R&S CMW-KS610
Manual operation: See "Channel, Frequency " on page 75
CONFigure:BLUetooth:SIGN<i>:RFSettings:FREQuency:TXTest?
Queries the frequency used by the TX test.
Return values:
<RxTxFreq> float
Range: 2402 MHz to 2480 MHz
Default unit: Hz
Example: See Transmitter test mode
Usage: Query only
Firmware/Software: V3.2.30
Options: R&S CMW-KS610
Manual operation: See "Channel, Frequency " on page 75
CONFigure:BLUetooth:SIGN<i>:RFSettings:HOPPing <Hopping>
Enables/disables frequency hopping.
Parameters:
<Hopping> OFF | ON
*RST: OFF
Example: See Configure Test Mode Classic
Firmware/Software: V3.2.30
Options: R&S CMW-KS610 for test mode classic
Manual operation: See "Hopping (classic)" on page 75
CONFigure:BLUetooth:SIGN<i>:TMODe <TestMode>
Selects the test mode that the EUT enters in a test mode connection.
Parameters:
<TestMode> LOOPback | TXTest
LOOPback: BR/EDR loopback test mode
TXTest: BR/EDR transmitter test mode
*RST: LOOP
Example: See Transmitter test mode
Firmware/Software: V3.2.30
Options: R&S CMW-KS610
Manual operation: See "Test Mode (classic)" on page 69
CONFigure:BLUetooth:SIGN<i>:RFSettings:NMODe:HMODe:LENergy
<HoppingMode>
Specifies hopping for LE connection tests.
Channels used in hopping mode "CH2" depend on the specified measured channel.
First hopping channel is identical with measured channel
(CONFigure:BLUetooth:SIGN<i>:RFSettings:NMODe:MCHannel:LENergy).
The second hopping channel is offset from the first one.
Parameters:
<HoppingMode> CH2 | ALL
"CH2": 2 data channels offset by 10 or 9 channels are used for
hopping
"ALL": 37 data channels are used for hopping
*RST: CH2
Example: See Connect LE (Normal Mode)
Firmware/Software: V3.7.61
Options: R&S CMW-KS601
Manual operation: See "Hopping Mode (LE connection test)" on page 76
CONFigure:BLUetooth:SIGN<i>:RFSettings:NMODe:MCHannel:LENergy
<MeasuredChannel>
Set the single measured channel for Rx measurements with LE connection tests.
Channels for hopping mode "CH2" depend also on this setting. See also CONFigure:
BLUetooth:SIGN<i>:RFSettings:NMODe:HMODe:LENergy.
Parameters:
<MeasuredChannel> numeric
Channel number
Range: 1 to 11, 13 to 38
*RST: 1 Ch
Example: See Connect LE (Normal Mode)
Firmware/Software: V3.7.61
Options: R&S CMW-KS601
Manual operation: See "Table Measured Channel, Hopping Channels (LE connec-
tion test)" on page 76
The following commands are only available as remote control. They have no corre-
sponding GUI parameters.
CONFigure:BLUetooth:SIGN<i>:RFSettings:AFHopping.................................................... 132
CONFigure:BLUetooth:SIGN<i>:RFSettings:AFHopping:UCHannels...................................133
SENSe:BLUetooth:SIGN<i>:CMAP?................................................................................ 133
CONFigure:BLUetooth:SIGN<i>:RFSettings:AFHopping <AdaptiveHopping>,
<Mode>
Specifies the parameters of adaptive hopping.
Parameters:
<AdaptiveHopping> OFF | ON
Disables, enables adaptive hopping.
*RST: OFF
<Mode> EUT | NORM | USER
EUT: only the EUT reports bad channels
NORM: both, the EUT and instrument report bad channels
USER: bad channels specified manually via CONFigure:
BLUetooth:SIGN<i>:RFSettings:AFHopping:
UCHannels
*RST: NORM
Example: See Configure Test Mode Classic
Firmware/Software: V3.5.50
Options: R&S CMW-KS610
CONFigure:BLUetooth:SIGN<i>:RFSettings:AFHopping:UCHannels
<ChannelList>...
Specifies user-defined channels for adaptive frequency hopping (AFH). The setting is
relevant for mode = USER, see CONFigure:BLUetooth:SIGN<i>:RFSettings:
AFHopping.
Parameters:
<ChannelList> integer
79 comma-separated values, one value per channel:
0: channel is blocked for AFH
1: channel is released for AFH
Range: 0 to 1
*RST: 1
Example: See Configure Test Mode Classic
Firmware/Software: V3.5.50
Options: R&S CMW-KS610
SENSe:BLUetooth:SIGN<i>:CMAP?
Queries channels used by adaptive frequency hopping (AFH).
Return values:
<AFHChannelMap> decimal
79 comma-separated values, one value per channel:
0: channel is blocked for AFH
1: channel is released for AFH
Range: 0 to 1
Example: See Transmitter test mode
Usage: Query only
Firmware/Software: V3.5.50
Options: R&S CMW-KS610
CONFigure:BLUetooth:SIGN<i>:RFSettings:ARANging <AutoRanging>
Adjusts the input level expected at the R&S CMW antenna automatically, according to
the predefined values and measured signal amplitude.
Parameters:
<AutoRanging> OFF | ON
*RST: OFF
Example: See Initialization and Basic Configuration
Firmware/Software: V3.2.70
Manual operation: See "Auto Ranging" on page 78
CONFigure:BLUetooth:SIGN<i>:RFSettings:ENPower <ExpNomPwr>
Sets the expected nominal power of the EUT signal
Parameters:
<ExpNomPwr> numeric
The range of the expected nominal power can be calculated as
follows:
Range (Expected Nominal Power) = Range (Input Power) +
External Attenuation - User Margin
The input power range is stated in the data sheet.
*RST: 10 dBm
Default unit: dBm
Example: See Initialization and Basic Configuration
Firmware/Software: V3.0.12
Manual operation: See "Exp. Nominal Power" on page 77
CONFigure:BLUetooth:SIGN<i>:RFSettings:LEVel <Level>
Defines the absolute TX level of the R&S CMW (master) signal.
The allowed value range can be calculated as follows:
Range (Level) = Range (Output Power) - External Attenuation
Range (Output Power) = -130 dBm to 0 dBm (RFx COM) or -120 dBm
to 8 dBm (RFx OUT); please also notice the ranges quoted in the data sheet.
Parameters:
<Level> numeric
Range: see above
*RST: -40 dBm
Default unit: dBm
Example: See Initialization and Basic Configuration
Firmware/Software: V3.0.12
V3.7.10: changed range
Manual operation: See "Tx Level (CMW)" on page 77
CONFigure:BLUetooth:SIGN<i>:RFSettings:UMARgin <Margin>
Sets the margin that the R&S CMW adds to the expected nominal power to determine
the reference level.
The reference level minus the external input attenuation must be within the power
range of the selected input connector; refer to the data sheet.
Refer also to the following commands:
● CONFigure:BLUetooth:SIGN<i>:RFSettings:ENPower
● CONFigure:BLUetooth:SIGN<i>:RFSettings:EATTenuation:INPut
Parameters:
<Margin> numeric
Range: 0 dB to (55 dB + external attenuation - expected
nominal power)
*RST: 0 dB
Example: See Initialization and Basic Configuration
Firmware/Software: V3.0.12
Manual operation: See "User Margin" on page 77
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:FDRift:EDRate............................... 140
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:FDRift:NMODe:LENergy:LRANge.... 141
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:FDRift:NMODe:LENergy:LE2M........141
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:FDRift:NMODe:LENergy:LE1M........141
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:FDRift:TMODe:LENergy:LRANge.... 141
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:FDRift:TMODe:LENergy:LE2M........ 141
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:FDRift:TMODe:LENergy:LE1M........ 141
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:FDRift:LENergy:LRANge................ 141
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:FDRift:LENergy:LE2M.................... 141
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:FDRift:LENergy[:LE1M].................. 141
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:FOFFset:BRATe.............................142
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:FOFFset:EDRate........................... 142
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:FOFFset:NMODe:LENergy:
LRANge..............................................................................................................142
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:FOFFset:NMODe:LENergy:LE2M.... 142
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:FOFFset:NMODe:LENergy:LE1M.... 142
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:FOFFset:TMODe:LENergy:LRANge.142
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:FOFFset:TMODe:LENergy:LE2M.... 142
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:FOFFset:TMODe:LENergy:LE1M.... 142
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:FOFFset:LENergy:LRANge............. 142
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:FOFFset:LENergy:LE2M.................142
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:FOFFset:LENergy[:LE1M]............... 142
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:MINDex:BRATe.............................. 143
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:MINDex:NMODe:LENergy:LRANge. 143
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:MINDex:NMODe:LENergy:LE2M..... 143
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:MINDex:NMODe:LENergy:LE1M..... 143
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:MINDex:STANdard:TMODe:
LENergy:LRANge................................................................................................ 143
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:MINDex:STANdard:TMODe:
LENergy:LE2M.................................................................................................... 143
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:MINDex:STANdard:TMODe:
LENergy:LE1M.................................................................................................... 143
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:MINDex:STANdard:LENergy:
LRANge..............................................................................................................143
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:MINDex:STANdard:LENergy:LE2M.. 144
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:MINDex:STANdard:LENergy[:
LE1M].................................................................................................................144
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:MINDex:STABle:TMODe:
LENergy:LRANge................................................................................................ 144
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:MINDex:STABle:TMODe:
LENergy:LE2M.................................................................................................... 144
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:MINDex:STABle:TMODe:
LENergy:LE1M.................................................................................................... 144
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:MINDex:STABle:LENergy:LRANge.. 144
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:MINDex:STABle:LENergy:LE2M...... 145
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:MINDex:STABle:LENergy[:LE1M].... 145
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:STERror:BRATe............................. 145
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:STERror:EDRate........................... 145
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:STERror:NMODe:LENergy:
LRANge..............................................................................................................146
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:STERror:NMODe:LENergy:LE2M.... 146
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:STERror:NMODe:LENergy:LE1M.... 146
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:STERror:TMODe:LENergy:LRANge.146
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:STERror:TMODe:LENergy:LE2M.....146
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:STERror:TMODe:LENergy:LE1M.....146
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:STERror:LENergy:LRANge............. 146
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:STERror:LENergy:LE2M.................146
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:STERror:LENergy[:LE1M]............... 146
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:FDRift:BRATe?.............................. 147
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:FDRift:EDRate?.............................147
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:FDRift:NMODe:LENergy:LRANge?..147
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:FDRift:NMODe:LENergy:LE2M?......147
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:FDRift:NMODe:LENergy:LE1M?......147
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:FDRift:TMODe:LENergy:LRANge?.. 147
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:FDRift:TMODe:LENergy:LE2M?...... 147
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:FDRift:TMODe:LENergy:LE1M?...... 147
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:FDRift:LENergy:LRANge?.............. 147
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:FDRift:LENergy:LE2M?.................. 147
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:FDRift:LENergy[:LE1M]?................ 147
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:FOFFset:BRATe?...........................148
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:FOFFset:EDRate?......................... 148
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:FOFFset:NMODe:LENergy:
LRANge?............................................................................................................ 148
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:FOFFset:NMODe:LENergy:LE2M?.. 148
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:FOFFset:NMODe:LENergy:LE1M?.. 148
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:FOFFset:TMODe:LENergy:
LRANge?............................................................................................................ 148
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:FOFFset:TMODe:LENergy:LE2M?.. 148
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:FOFFset:TMODe:LENergy:LE1M?.. 148
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:FOFFset:LENergy:LRANge?...........148
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:FOFFset:LENergy:LE2M?...............148
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:FOFFset:LENergy[:LE1M]?.............148
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:MINDex:BRATe?............................149
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:MINDex:NMODe:LENergy:
LRANge?............................................................................................................ 149
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:MINDex:NMODe:LENergy:LE2M?... 149
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:MINDex:NMODe:LENergy:LE1M?... 149
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:MINDex:STANdard:TMODe:
LENergy:LRANge?...............................................................................................149
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:MINDex:STANdard:TMODe:
LENergy:LE2M?.................................................................................................. 149
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:MINDex:STANdard:TMODe:
LENergy:LE1M?.................................................................................................. 149
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:MINDex:STANdard:LENergy:
LRANge?............................................................................................................ 149
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:MINDex:STANdard:LENergy:
LE2M?................................................................................................................149
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:MINDex:STANdard:LENergy[:
LE1M]?...............................................................................................................149
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:MINDex:STABle:TMODe:
LENergy:LRANge?...............................................................................................150
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:MINDex:STABle:TMODe:
LENergy:LE2M?.................................................................................................. 150
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:MINDex:STABle:TMODe:
LENergy:LE1M?.................................................................................................. 150
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:MINDex:STABle:LENergy:
LRANge?............................................................................................................ 150
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:MINDex:STABle:LENergy:LE2M?.... 150
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:MINDex:STABle:LENergy[:LE1M]?.. 150
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:STERror:BRATe?...........................151
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:STERror:EDRate?......................... 151
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:STERror:NMODe:LENergy:
LRANge?............................................................................................................ 151
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:STERror:NMODe:LENergy:LE2M?.. 151
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:STERror:NMODe:LENergy:LE1M?.. 151
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:STERror:TMODe:LENergy:
LRANge?............................................................................................................ 151
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:STERror:TMODe:LENergy:LE2M?...151
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:STERror:TMODe:LENergy:LE1M?...151
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:STERror:LENergy:LRANge?........... 151
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:STERror:LENergy:LE2M?...............151
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:STERror:LENergy[:LE1M]?............. 151
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX <DTXState>
Enables/disables the dirty transmitter.
Parameters:
<DTXState> OFF | ON
*RST: OFF
Example: See Configure Dirty Transmitter
Firmware/Software: V3.2.30
Options: R&S CMW-KS610 for BR/EDR
R&S CMW-KS611 for LE
Manual operation: See "Dirty Tx" on page 79
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:MODE:BRATe <DTXMode>
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:MODE:EDRate <DTXMode>
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:MODE:NMODe:LENergy:
LRANge <DTXMode>
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:MODE:NMODe:LENergy:LE2M
<DTXMode>
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:MODE:NMODe:LENergy:LE1M
<DTXMode>
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:MODE:TMODe:LENergy:
LRANge <DTXMode>
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:MODE:TMODe:LENergy:LE2M
<DTXMode>
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:MODE:TMODe:LENergy:LE1M
<DTXMode>
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:MODE:LENergy:LRANge
<DTXMode>
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:MODE:LENergy:LE2M
<DTXMode>
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:MODE:LENergy[:LE1M]
<DTXMode>
Configure the dirty transmitter.
● RF tests:
Commands for test mode classic (..:BRATe..), (..:EDRate..) and for LE direct
test mode (..:LE1M..), (..:LE2M..), (..:LRANge..) are available.
● LE connection tests (normal mode):
Commands for uncoded LE 1M PHY (..:NMODe:LENergy:LE1M..), LE 2M PHY
(..:NMODe:LENergy:LE2M..), and LE coded PHY
(..:NMODe:LENergy:LRANge..) are available.
● LE test mode:
Commands for uncoded LE 1M PHY (..:TMODe:LENergy:LE1M..), LE 2M PHY
(..:TMODe:LENergy:LE2M..), and LE coded PHY
(..:TMODe:LENergy:LRANge..) are available.
Parameters:
<DTXMode> SINGle values | SPEC table
SING: single set of dirty transmitter parameters. No periodic
change of the frequency offset, modulation index, and symbol
timing error occurs.
SPEC: settings according to the test specification for Bluetooth
wireless technology, see "Dirty Tx Mode" on page 79.
*RST: SPEC
Example: See Configure Dirty Transmitter
Firmware/Software: V3.2.30, V3.2.70: added command for ..:LE1M, V3.5.70:
added commands for ..:LE2M and ..:LRANge, V3.7.80:
added commands for ..:NMODe:..,
V3.7.90: added commands for ..:TMODe:..
Options: R&S CMW-KS610 for BR/EDR in test mode
R&S CMW-KS611 for LE direct test mode
Plus R&S CMW-KS721 for LE2M and LRANge
R&S CMW-KS601 for LE connection test and LE test mode
Plus R&S CMW-KS720 for LE2M and LRANge
Manual operation: See "Dirty Tx Mode" on page 79
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:MODFrequency:NMODe:
LENergy:LRANge <DriftRate>
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:MODFrequency:NMODe:
LENergy:LE2M <DriftRate>
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:MODFrequency:NMODe:
LENergy:LE1M <DriftRate>
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:MODFrequency:TMODe:
LENergy:LRANge <DriftRate>
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:MODFrequency:TMODe:
LENergy:LE2M <DriftRate>
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:MODFrequency:TMODe:
LENergy:LE1M <DriftRate>
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:MODFrequency:LENergy:
LRANge <DriftRate>
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:MODFrequency:LENergy:LE2M
<DriftRate>
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:MODFrequency:LENergy[:
LE1M] <DriftRate>
Specifies the drift rate for LE dirty transmitter.
● LE direct test mode:
Commands for uncoded LE 1M PHY (..:LE1M..), LE 2M PHY (..:LE2M..),
and LE coded PHY (..:LRANge..) are available.
● LE connection tests (normal mode):
Commands ..:NMODe:LENergy:.. are available.
● LE test mode:
Commands ..:TMODe:LENergy:.. are available.
Parameters:
<DriftRate> HDRF | LDRF
HDRF: 1250 Hz (high drift rate)
LDRF: 625 Hz (low drift rate)
*RST: HDRF
Example: See Configure Dirty Transmitter
Firmware/Software: V3.5.50, V3.5.70: added commands for ...:LE2M
and ...:LRANge, V3.7.50: changed reset value, V3.7.80:
added commands for ...:NMODe:...,
V3.7.90: added commands for ...:TMODe:...
Options: R&S CMW-KS611 for LE direct test mode
Plus R&S CMW-KS721 for LE2M and LRANge
R&S CMW-KS601 for LE connection test and LE test mode
Plus R&S CMW-KS720 for LE2M and LRANge
Manual operation: See "Modulation Frequency (LE)" on page 83
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:FDRift:BRATe <FreqDrift>
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:FDRift:EDRate <FreqDrift>
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:FDRift:NMODe:LENergy:
LRANge <FreqDrift>
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:FDRift:NMODe:LENergy:
LE2M <FreqDrift>
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:FDRift:NMODe:LENergy:
LE1M <FreqDrift>
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:FDRift:TMODe:LENergy:
LRANge <FreqDrift>
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:FDRift:TMODe:LENergy:
LE2M <FreqDrift>
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:FDRift:TMODe:LENergy:
LE1M <FreqDrift>
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:FDRift:LENergy:LRANge
<FreqDrift>
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:FDRift:LENergy:LE2M
<FreqDrift>
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:FDRift:LENergy[:LE1M]
<FreqDrift>
Enable/disable the periodic change of frequency offset.
● RF tests:
Commands for test mode classic (..:BRATe..), (..:EDRate..) and for LE direct
test mode (..:LE1M..), (..:LE2M..), (..:LRANge..) are available.
● LE connection tests (normal mode):
Commands for uncoded LE 1M PHY (..:NMODe:LENergy:LE1M..), LE 2M PHY
(..:NMODe:LENergy:LE2M..), and LE coded PHY
(..:NMODe:LENergy:LRANge..) are available.
● LE test mode:
Commands for uncoded LE 1M PHY (..:TMODe:LENergy:LE1M..), LE 2M PHY
(..:TMODe:LENergy:LE2M..), and LE coded PHY
(..:TMODe:LENergy:LRANge..) are available.
Parameters:
<FreqDrift> OFF | ON
*RST: OFF
Example: See Configure Dirty Transmitter
Firmware/Software: V3.2.50, V3.2.70: added command for ...:LE1M, V3.5.70:
added commands for ...:LE2M and ...:LRANge, V3.7.61:
added commands for BR/EDR ...:NMODe:..., V3.7.80:
added commands for LE ...:NMODe:...,
V3.7.90: added commands for ...:TMODe:...
Options: R&S CMW-KS610 for BR/EDR
R&S CMW-KS611 for LE direct test mode
Plus R&S CMW-KS721 for LE2M and LRANge
R&S CMW-KS601 for LE connection test and LE test mode
Plus R&S CMW-KS720 for LE2M and LRANge
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:FOFFset:BRATe
<FreqOffset>
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:FOFFset:EDRate
<FreqOffset>
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:FOFFset:NMODe:
LENergy:LRANge <FreqOffset>
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:FOFFset:NMODe:
LENergy:LE2M <FreqOffset>
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:FOFFset:NMODe:
LENergy:LE1M <FreqOffset>
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:FOFFset:TMODe:
LENergy:LRANge <FreqOffset>
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:FOFFset:TMODe:
LENergy:LE2M <FreqOffset>
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:FOFFset:TMODe:
LENergy:LE1M <FreqOffset>
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:FOFFset:LENergy:
LRANge <FreqOffset>
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:FOFFset:LENergy:LE2M
<FreqOffset>
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:FOFFset:LENergy[:LE1M]
<FreqOffset>
Specify the constant frequency offset to be added to the center frequency.
● RF tests:
Commands for test mode classic (..:BRATe..), (..:EDRate..) and for LE direct
test mode (..:LE1M..), (..:LE2M..), (..:LRANge..) are available.
● LE connection tests (normal mode):
Commands for uncoded LE 1M PHY (..:NMODe:LENergy:LE1M..), LE 2M PHY
(..:NMODe:LENergy:LE2M..), and LE coded PHY
(..:NMODe:LENergy:LRANge..) are available.
● LE test mode:
Commands for uncoded LE 1M PHY (..:TMODe:LENergy:LE1M..), LE 2M PHY
(..:TMODe:LENergy:LE2M..), and LE coded PHY
(..:TMODe:LENergy:LRANge..) are available.
Parameters:
<FreqOffset> numeric | ON | OFF
Range: -250E+3 Hz to 250E+3 Hz
*RST: 0 Hz
Additional ON/OFF enables/disables constant frequency offset
Example: See Configure Dirty Transmitter
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:MINDex:BRATe
<ModIndex>
Specifies the modulation corruption of the signal. Modulation index of 0.32 means no
corruption.
Parameters:
<ModIndex> numeric | ON | OFF
Range: 0.2 to 0.44
*RST: 0.32
Additional ON/OFF enables/disables modulation index.
Example: See Configure Dirty Transmitter
Firmware/Software: V3.2.50
Options: R&S CMW-KS610
Manual operation: See "Single Values" on page 83
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:MINDex:NMODe:LENergy:
LRANge <ModIndex>
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:MINDex:NMODe:LENergy:
LE2M <ModIndex>
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:MINDex:NMODe:LENergy:
LE1M <ModIndex>
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:MINDex:STANdard:
TMODe:LENergy:LRANge <ModIndex>
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:MINDex:STANdard:
TMODe:LENergy:LE2M <ModIndex>
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:MINDex:STANdard:
TMODe:LENergy:LE1M <ModIndex>
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:MINDex:STANdard:
LENergy:LRANge <ModIndex>
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:MINDex:STANdard:
LENergy:LE2M <ModIndex>
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:MINDex:STANdard:
LENergy[:LE1M] <ModIndex>
Specifies the modulation corruption of the signal. Modulation index of 0.5 means no
corruption.
● LE direct test mode:
Commands for test mode classic (..:BRATe..), (..:EDRate..) and for LE direct
test mode (..:LE1M..), (..:LE2M..), (..:LRANge..) are available.
● LE connection tests (normal mode):
Commands for uncoded LE 1M PHY (..:NMODe:LENergy:LE1M..), LE 2M PHY
(..:NMODe:LENergy:LE2M..), and LE coded PHY
(..:NMODe:LENergy:LRANge..) are available.
● LE test mode:
Commands for uncoded LE 1M PHY (..:TMODe:LENergy:LE1M..), LE 2M PHY
(..:TMODe:LENergy:LE2M..), and LE coded PHY
(..:TMODe:LENergy:LRANge..) are available.
Parameters:
<ModIndex> numeric | ON | OFF
Range: 0.4 to 0.6
*RST: 0.50
Additional ON/OFF enables/disables modulation index.
Example: See Configure Dirty Transmitter
Firmware/Software: V3.2.70, V3.5.60: range extended, V3.5.70: added commands
for ...:LE2M and ...:LRANge, V3.7.80: added commands
for ...:NMODe:...,
V3.7.90: added commands for ...:TMODe:...
Options: R&S CMW-KS611 for LE direct test mode
Plus R&S CMW-KS721 for LE2M and LRANge
R&S CMW-KS601 for LE connection test and LE test mode
Plus R&S CMW-KS720 for LE2M and LRANge
Manual operation: See "Single Values" on page 83
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:MINDex:STABle:TMODe:
LENergy:LRANge <ModIndex>
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:MINDex:STABle:TMODe:
LENergy:LE2M <ModIndex>
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:MINDex:STABle:TMODe:
LENergy:LE1M <ModIndex>
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:MINDex:STABle:LENergy:
LRANge <ModIndex>
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:MINDex:STABle:LENergy:
LE2M <ModIndex>
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:MINDex:STABle:
LENergy[:LE1M] <ModIndex>
Specifies the modulation corruption of the signal. Modulation index of 0.5 means no
corruption.
● LE direct test mode:
Commands for uncoded LE 1M PHY (..:LE1M..), LE 2M PHY (..:LE2M..), and LE
coded PHY (..:LRANge..) are available.
● LE test mode:
Commands for uncoded LE 1M PHY (..:TMODe:LENergy:LE1M..), LE 2M PHY
(..:TMODe:LENergy:LE2M..), and LE coded PHY
(..:TMODe:LENergy:LRANge..) are available.
Parameters:
<ModIndex> numeric | ON | OFF
Range: 0.4 to 0.6
*RST: 0.50
Additional ON/OFF enables/disables modulation index.
Example: See Configure Dirty Transmitter
Firmware/Software: V3.5.70, V3.7.90: added commands for LE test mode
Options: R&S CMW-KS611 for LE direct test mode
Plus R&S CMW-KS721 for LE2M and LRANge
R&S CMW-KS601 for LE test mode
Plus R&S CMW-KS720 for LE2M and LRANge
Manual operation: See "Single Values" on page 83
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:STERror:BRATe
<SymbolTimeErr>
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:STERror:EDRate
<SymbolTimeErr>
Specify the symbol timing error of the signal.
Parameters:
<SymbolTimeErr> OFF | NEG20 | POS20
No symbol timing error, - 20 ppm or 20 ppm
*RST: OFF
Example: See Configure Dirty Transmitter
Firmware/Software: V3.2.50
Options: R&S CMW-KS610
Manual operation: See "Single Values" on page 83
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:STERror:NMODe:
LENergy:LRANge <SymbolTimeErr>
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:STERror:NMODe:
LENergy:LE2M <SymbolTimeErr>
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:STERror:NMODe:
LENergy:LE1M <SymbolTimeErr>
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:STERror:TMODe:
LENergy:LRANge <SymbolTimeErr>
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:STERror:TMODe:
LENergy:LE2M <SymbolTimeErr>
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:STERror:TMODe:
LENergy:LE1M <SymbolTimeErr>
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:STERror:LENergy:
LRANge <SymbolTimeErr>
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:STERror:LENergy:LE2M
<SymbolTimeErr>
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:STERror:LENergy[:LE1M]
<SymbolTimeErr>
Specifies the symbol timing error of the LE signal.
● RF tests:
Commands for test mode classic (..:BRATe..), (..:EDRate..) and for LE direct
test mode (..:LE1M..), (..:LE2M..), (..:LRANge..) are available.
● LE connection tests (normal mode):
Commands for uncoded LE 1M PHY (..:NMODe:LENergy:LE1M..), LE 2M PHY
(..:NMODe:LENergy:LE2M..), and LE coded PHY
(..:NMODe:LENergy:LRANge..) are available.
● LE test mode:
Commands for uncoded LE 1M PHY (..:TMODe:LENergy:LE1M..), LE 2M PHY
(..:TMODe:LENergy:LE2M..), and LE coded PHY
(..:TMODe:LENergy:LRANge..) are available.
Parameters:
<SymbolTimeErr> OFF | NEG50 | POS50
No symbol timing error, - 50 ppm or 50 ppm
*RST: OFF
Example: See Configure Dirty Transmitter
Firmware/Software: V3.2.70, V3.5.70: added commands for ...:LE2M
and ...:LRANge, V3.7.80: added commands
for ...:NMODe:...,
V3.7.90: added commands for ...:TMODe:...
Options: R&S CMW-KS611 for LE direct test mode
Plus R&S CMW-KS721 for LE2M and LRANge
R&S CMW-KS601 for LE connection test and LE test mode
Plus R&S CMW-KS720 for LE2M and LRANge
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:FDRift:BRATe?
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:FDRift:EDRate?
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:FDRift:NMODe:LENergy:
LRANge?
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:FDRift:NMODe:LENergy:
LE2M?
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:FDRift:NMODe:LENergy:
LE1M?
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:FDRift:TMODe:LENergy:
LRANge?
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:FDRift:TMODe:LENergy:
LE2M?
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:FDRift:TMODe:LENergy:
LE1M?
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:FDRift:LENergy:LRANge?
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:FDRift:LENergy:LE2M?
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:FDRift:LENergy[:LE1M]?
Query the dirty transmitter frequency drift set according to the test specification for
Bluetooth wireless technology.
● RF tests:
Commands for test mode classic (..:BRATe..), (..:EDRate..) and for LE direct
test mode (..:LE1M..), (..:LE2M..), (..:LRANge..) are available.
● LE connection tests (normal mode):
Commands for uncoded LE 1M PHY (..:NMODe:LENergy:LE1M..), LE 2M PHY
(..:NMODe:LENergy:LE2M..), and LE coded PHY
(..:NMODe:LENergy:LRANge..) are available.
● LE test mode:
Commands for uncoded LE 1M PHY (..:TMODe:LENergy:LE1M..), LE 2M PHY
(..:TMODe:LENergy:LE2M..), and LE coded PHY
(..:TMODe:LENergy:LRANge..) are available.
Return values:
<FreqDrift> float
Frequency drift is always enabled, according to the test specifi-
cation for Bluetooth wireless technology.
Example: See Configure Dirty Transmitter
Usage: Query only
Firmware/Software: V3.2.50, V3.2.70: added command for LE1M, V3.5.70: added
commands for ...:LE2M... and ...:LRANge..., V3.7.61:
added command for LE1M ...:NMODe:..., V3.7.80: added
commands for LE2M and LRANge ...:NMODe:...,
V3.7.90: added commands for ...:TMODe:...
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:FOFFset:BRATe?
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:FOFFset:EDRate?
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:FOFFset:NMODe:
LENergy:LRANge?
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:FOFFset:NMODe:
LENergy:LE2M?
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:FOFFset:NMODe:
LENergy:LE1M?
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:FOFFset:TMODe:
LENergy:LRANge?
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:FOFFset:TMODe:
LENergy:LE2M?
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:FOFFset:TMODe:
LENergy:LE1M?
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:FOFFset:LENergy:
LRANge?
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:FOFFset:LENergy:LE2M?
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:FOFFset:LENergy[:
LE1M]?
Return the frequency offset under the periodic change according to the test specifica-
tion for Bluetooth wireless technology (10 values for BR and LE, 3 values for EDR).
● RF tests:
Commands for test mode classic (..:BRATe..), (..:EDRate..) and for LE direct
test mode (..:LE1M..), (..:LE2M..), (..:LRANge..) are available.
● LE connection tests (normal mode):
Commands for uncoded LE 1M PHY (..:NMODe:LENergy:LE1M..), LE 2M PHY
(..:NMODe:LENergy:LE2M..), and LE coded PHY
(..:NMODe:LENergy:LRANge..) are available.
● LE test mode:
Commands for uncoded LE 1M PHY (..:TMODe:LENergy:LE1M..), LE 2M PHY
(..:TMODe:LENergy:LE2M..), and LE coded PHY
(..:TMODe:LENergy:LRANge..) are available.
Return values:
<FreqOffset> decimal | ON | OFF
Range: -250E+3 Hz to 250E+3 Hz
Default unit: Hz
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:MINDex:BRATe?
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:MINDex:NMODe:
LENergy:LRANge?
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:MINDex:NMODe:
LENergy:LE2M?
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:MINDex:NMODe:
LENergy:LE1M?
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:MINDex:STANdard:
TMODe:LENergy:LRANge?
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:MINDex:STANdard:
TMODe:LENergy:LE2M?
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:MINDex:STANdard:
TMODe:LENergy:LE1M?
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:MINDex:STANdard:
LENergy:LRANge?
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:MINDex:STANdard:
LENergy:LE2M?
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:MINDex:STANdard:
LENergy[:LE1M]?
Return the modulation index under the periodic change according to the test specifica-
tion for Bluetooth wireless technology (10 values).
● RF tests:
Commands for BR (..:BRATe..), LE 1M PHY - uncoded (..:LE1M..), LE 2M PHY -
uncoded (..:LE2M..), and LE coded PHY (..:LRANge..) are available.
For dirty transmitter parameters according to the test specification for Bluetooth wire-
less technology, see also "Dirty Tx Mode" on page 79.
● LE connection tests (normal mode):
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:MINDex:STABle:TMODe:
LENergy:LRANge?
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:MINDex:STABle:TMODe:
LENergy:LE2M?
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:MINDex:STABle:TMODe:
LENergy:LE1M?
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:MINDex:STABle:LENergy:
LRANge?
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:MINDex:STABle:LENergy:
LE2M?
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:MINDex:STABle:
LENergy[:LE1M]?
Return the modulation index h under the periodic change (10 values) for stable range
h = 0.495 to 0.505.
● LE direct test mode:
Commands for uncoded LE 1M PHY (..:LE1M..), LE 2M PHY (..:LE2M..), and LE
coded PHY (..:LRANge..) are available.
For dirty transmitter parameters according to the test specification for Bluetooth wire-
less technology, see also "Dirty Tx Mode" on page 79.
● LE test mode:
Commands for uncoded LE 1M PHY (..:TMODe:LENergy:LE1M..), LE 2M PHY
(..:TMODe:LENergy:LE2M..), and LE coded PHY
(..:TMODe:LENergy:LRANge..) are available.
Return values:
<ModIndex> float | ON | OFF
Range: 0.495 to 0.505
Example: See Configure Dirty Transmitter
Usage: Query only
Firmware/Software: V3.5.70,
V3.7.90: added commands for ...:TMODe:...
Options: R&S CMW-KS611
Plus R&S CMW-KS721 for LE2M and LRANge
R&S CMW-KS601 for LE test mode
Plus R&S CMW-KS720 for LE2M and LRANge
Manual operation: See "Settings for Spec Table Mode" on page 80
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:STERror:BRATe?
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:STERror:EDRate?
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:STERror:NMODe:
LENergy:LRANge?
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:STERror:NMODe:
LENergy:LE2M?
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:STERror:NMODe:
LENergy:LE1M?
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:STERror:TMODe:
LENergy:LRANge?
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:STERror:TMODe:
LENergy:LE2M?
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:STERror:TMODe:
LENergy:LE1M?
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:STERror:LENergy:
LRANge?
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:STERror:LENergy:LE2M?
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:STERror:LENergy[:
LE1M]?
Return the symbol timing error under the periodic change according to the test specifi-
cation for Bluetooth wireless technology (10 values for BR and LE, 3 values for EDR).
● RF tests:
Commands for test mode classic (..:BRATe..), (..:EDRate..) and for LE direct
test mode (..:LE1M..), (..:LE2M..), (..:LRANge..) are available.
For dirty transmitter parameters according to the test specification for Bluetooth wire-
less technology, see also "Dirty Tx Mode" on page 79.
● LE connection tests (normal mode):
Commands for uncoded LE 1M PHY (..:NMODe:LENergy:LE1M..), LE 2M PHY
(..:NMODe:LENergy:LE2M..), and LE coded PHY
(..:NMODe:LENergy:LRANge..) are available.
● LE test mode:
Commands for uncoded LE 1M PHY (..:TMODe:LENergy:LE1M..), LE 2M PHY
(..:TMODe:LENergy:LE2M..), and LE coded PHY
(..:TMODe:LENergy:LRANge..) are available.
Return values:
<SymbolTimeErr> decimal
Range: - 50 ppm to 50 ppm, for BR/EDR: - 20 ppm to 20
ppm
Default unit: ppm
Example: See Configure Dirty Transmitter
Usage: Query only
Firmware/Software: V3.2.50, V3.2.70: added command for ...:LE1M, V3.5.70:
added commands for ...:LE2M and ...:LRANge, V3.7.61:
added command for LE1M ...:NMODe:..., V3.7.80: added
commands for LE2M and LRANge ...:NMODe:...,
V3.7.90: added commands for ...:TMODe:...
Options: R&S CMW-KS610 for BR/EDR
R&S CMW-KS611 for LE direct test mode
Plus R&S CMW-KS721 for LE2M and LRANge
R&S CMW-KS601 for LE connection test and LE test mode
Plus R&S CMW-KS720 for LE2M and LRANge
Manual operation: See "Settings for Spec Table Mode" on page 80
The following commands control the connection to the EUT and retrieve connection-
related information.
SOURce:BLUetooth:SIGN<i>:STATe................................................................................153
FETCh:BLUetooth:SIGN<i>:CONNection:STATe?............................................................. 153
FETCh:BLUetooth:SIGN<i>:CONNection:STATe:ALL?.......................................................155
FETCh:BLUetooth:SIGN<i>:CONNection:STATe:LESignaling?........................................... 157
FETCh:BLUetooth:SIGN<i>:LENergy:STATe?................................................................... 157
CALL:BLUetooth:SIGN<i>:CONNection:ACTion................................................................ 158
CALL:BLUetooth:SIGN<i>:CONNection:ACTion:LESignaling..............................................159
CALL:BLUetooth:SIGN<i>:CONNection:CHECk:LENergy?.................................................160
CALL:BLUetooth:SIGN<i>:LENergy:RESet.......................................................................160
CALL:BLUetooth:SIGN<i>:RDEVices............................................................................... 161
CONFigure:BLUetooth:SIGN<i>:CONNection:PCONtrol:EPCMode.....................................161
CONFigure:BLUetooth:SIGN<i>:CONNection:PCONtrol:STEP:ACTion................................161
SENSe:BLUetooth:SIGN<i>:EUT:PCONtrol:STATe:LEGacy?.............................................. 161
SENSe:BLUetooth:SIGN<i>:EUT:PCONtrol:STATe?.......................................................... 162
SENSe:BLUetooth:SIGN<i>:EUT:PCONtrol:STATe:DPSK?.................................................163
SENSe:BLUetooth:SIGN<i>:EUT:PCONtrol:STATe:DQPSk?...............................................163
SENSe:BLUetooth:SIGN<i>:EUT:PCONtrol:STATe:GFSK?.................................................163
SENSe:BLUetooth:SIGN<i>:CONNection:AUDio:LINFo?................................................... 163
CLEan:BLUetooth:SIGN<i>:ELOGging.............................................................................164
SENSe:BLUetooth:SIGN<i>:ELOGging:ALL?....................................................................164
SENSe:BLUetooth:SIGN<i>:ELOGging:LAST?................................................................. 165
SENSe:BLUetooth:SIGN<i>:EUT:CSETtings:LESignaling?.................................................165
SOURce:BLUetooth:SIGN<i>:STATe <MainState>
Sets/gets the main state of the "Bluetooth Signaling" application. Signaling actions
such as inquiry or paging are initiated using the CALL:BLUetooth:SIGN<i>:
CONNection:ACTion command.
Parameters:
<MainState> ON | OFF | 1 | 0
When turned ON, the R&S CMW switches to standby state (see
FETCh:BLUetooth:SIGN<i>:CONNection:STATe?
on page 153)
Firmware/Software: V3.0.12
Manual operation: See "CMW" on page 43
FETCh:BLUetooth:SIGN<i>:CONNection:STATe?
Returns the signaling state of the R&S CMW for BR/EDR. State changes are initiated
using the CALL:BLUetooth:SIGN<i>:CONNection:ACTion command.
Return values:
<State> OFF | SBY | INQuiring | SINQuiry | CNNecting | SCONnecting |
CONNected | DETaching | TCNNecting | TCONected |
ECRunning | ECNNecting | ECONected | EXEMode |
ENEMode | HFCNnecting | HFConnected | EXHFp | ENHFp |
AGCNnecting | AGConnected | EXAGmode | ENAGmode |
ENHSmode | EXHSmode | CNASmode | CHASmode |
DHASmode | EHASmode | XHASmode | SMIDle |
SMCNnecting | SMConnected | SMDetaching | HSCNnecting |
HSConnected | HSDetaching | A2CNnecting | A2Connected |
A2Detaching | A2SNnecting | A2SCnnected | A2SDetaching |
ACNNecting | ACONected | AEXMode | AENMode
OFF: not connected
SBY: standby
INQuiring: inquiring
SINQuiry: stopping inquiry
CNNecting: connecting
FETCh:BLUetooth:SIGN<i>:CONNection:STATe:ALL?
Returns detailed information about the "Bluetooth Signaling" generator state.
Return values:
<MainState> OFF | ON
OFF: Generator switched off
ON: Generator has been turned on
<SubState> OFF | SBY | INQuiring | SINQuiry | CNNecting | SCONnecting |
CONNected | DETaching | TCNNecting | TCONected |
ECRunning | ECNNecting | ECONected | EXEMode |
ENEMode | HFCNnecting | HFConnected | EXHFp | ENHFp |
AGCNnecting | AGConnected | EXAGmode | ENAGmode |
ENHSmode | EXHSmode | CNASmode | CHASmode |
DHASmode | EHASmode | XHASmode | SMIDle |
SMCNnecting | SMConnected | SMDetaching | HSCNnecting |
HSConnected | HSDetaching | A2CNnecting | A2Connected |
A2Detaching | A2SNnecting | A2SCnnected | A2SDetaching |
ACNNecting | ACONected | AEXMode | AENMode
Signaling states of the R&S CMW for BR/EDR:
OFF: not connected
SBY: standby
INQuiring: inquiring
SINQuiry: stopping inquiry
CNNecting: connecting
SCONnecting: stop connecting
CONNected: connected
DETaching: detaching
TCNNecting: test mode - connecting
TCONnected: test mode - connected
ECRunning: EUT controller running
ECNNecting: audio echo mode - connecting
FETCh:BLUetooth:SIGN<i>:CONNection:STATe:LESignaling?
Returns the signaling state of the R&S CMW for LE. State changes are initiated using
the CALL:BLUetooth:SIGN<i>:CONNection:ACTion:LESignaling command.
Return values:
<State> OFF | SBY | INQuiring | CNNecting | CONNected | DETaching |
TCONected | TCNNecting | CPOWer
OFF: not connected
SBY: standby
INQuiring: inquiring
CNNecting: connecting
CONNected: connected
DETaching: detaching
TCONected: LE test mode - connected
CPOWer: LE power control
Example: See Connect
Usage: Query only
Firmware/Software: V3.7.50, V3.7.90: added states for LE test mode
V3.8.20: added CPOWer
Options: R&S CMW-KS601
Manual operation: See "Signaling" on page 43
FETCh:BLUetooth:SIGN<i>:LENergy:STATe?
Returns the signaling state of the R&S CMW for LE direct test connections.
Return values:
<State> IDLE | OFF | SPCM | STCM | CMR | STTX | TXRunning |
SPTX | STRX | RXRunning | SPRX | RCOM
IDLE: Connected in direct test mode, no active test running
CALL:BLUetooth:SIGN<i>:CONNection:ACTion <Action>
Requests the R&S CMW to perform certain signaling actions for BR/EDR. It has no
query form: the current signaling state can be retrieved using the FETCh:BLUetooth:
SIGN<i>:CONNection:STATe? command.
Setting parameters:
<Action> INQuire | SINQuiry | SCONnecting | STMode | CONNect |
TMConnect | DETach | REController | EMConnect | EXEMode |
ENEMode | HFPConnect | EXHFp | ENHFp | AGConnect |
ENAGate | EXAGate | ADConnect | AUDConnect | ADEXit |
ADENter
INQuire: Switch on master signal and start inquiry for Bluetooth
devices within range
Inquiry stops after a configurable maximum duration (see
CONFigure:BLUetooth:SIGN<i>:CONNection:INQuiry:
ILENgth on page 177) or after a configurable number of
responses (see CONFigure:BLUetooth:SIGN<i>:
CONNection:INQuiry:NOResponses on page 177)
SINQuiry: Stop inquiry, switch off master signal and return to
standby state
SCONnecting: Stop an ongoing connection setup, switch off the
master signal and return to standby state
STMode: Stop a test mode connection, switch off the master
signal and return to standby state
CONNect: Switch on master signal, start paging the selected
Bluetooth device and establish an ACL connection
TMConnect: Switch on master signal, start paging the selected
Bluetooth device and establish a test mode connection
CALL:BLUetooth:SIGN<i>:CONNection:ACTion:LESignaling <Action>
Requests the R&S CMW to perform certain signaling actions for LE. It has no query
form: the current signaling state can be retrieved using the FETCh:BLUetooth:
SIGN<i>:CONNection:STATe:LESignaling? command.
Setting parameters:
<Action> INQuire | SINQuiry | CONNect | SCONnecting | DETach |
TMConnect
INQuire: Switch on master signal and start inquiry for Bluetooth
devices within range
Inquiry stops after a configurable maximum duration (see
CONFigure:BLUetooth:SIGN<i>:CONNection:INQuiry:
DURation:LESignaling) or after a configurable number of
responses (see CONFigure:BLUetooth:SIGN<i>:
CONNection:INQuiry:NOResponses:LESignaling)
CALL:BLUetooth:SIGN<i>:CONNection:CHECk:LENergy?
Checks the LE connection via USB.
Return values:
<ConTestResult> PASS | FAIL | TOUT | NRUN
Result: passed, failed, timeout, not running
Example: See Direct test mode
Usage: Query only
Firmware/Software: V3.2.70
Options: R&S CMW-KS611
Manual operation: See "Connection Check (hotkey)" on page 59
CALL:BLUetooth:SIGN<i>:LENergy:RESet
Sends the HCI reset command to the EUT via USB.
Example: See Direct test mode
Usage: Event
Firmware/Software: V3.5.40
Options: R&S CMW-KS611
Manual operation: See "Reset EUT (hotkey)" on page 63
CALL:BLUetooth:SIGN<i>:RDEVices
Detects the DUTs connected to USB ports directly or via a USB-to-COM adapter.
Usage: Event
Firmware/Software: V3.8.20
Manual operation: See "Refresh Devices (hotkey)" on page 63
CONFigure:BLUetooth:SIGN<i>:CONNection:PCONtrol:EPCMode <PCMode>
Activates/deactivates enhanced power control mode.
Parameters:
<PCMode> AUTO | OFF
AUTO : instrument uses enhanced power control if EUT sup-
ports it, otherwise it uses legacy power control
OFF : instrument uses legacy power control
*RST: AUTO
Example: See Initialization and Basic Configuration
Firmware/Software: V3.2.60
Manual operation: See "Enhanced Power Control Mode" on page 98
CONFigure:BLUetooth:SIGN<i>:CONNection:PCONtrol:STEP:ACTion <PControl>
Sends a command to the EUT to increase/decrease power.
Setting parameters:
<PControl> UP | DOWN | MAX
One step up, one step down, command to maximum EUT power
Example: See Retrieve EUT Information and Capabilities
Usage: Event
Firmware/Software: V3.2.30
V3.2.60: added MAX
Manual operation: See "Power Up / Power Down / Max Power (hotkey)"
on page 62
SENSe:BLUetooth:SIGN<i>:EUT:PCONtrol:STATe:LEGacy?
Displays the EUT responses to the legacy power control commands.
Return values:
<PowerChange> NNM | UP | DOWN
NNM: no new message
UP: power up command accepted
DOWN: power down command accepted
SENSe:BLUetooth:SIGN<i>:EUT:PCONtrol:STATe?
Displays the EUT responses to the enhanced power control state commands for
GFSK-modulated BR and π/4 DQPSK and 8DPSK-modulated EDR packets.
Return values:
<PowChangeGFSK> NNE | UP | DOWN | MAX
NNE: none
UP: power up command accepted
DOWN: power down command accepted
MAX: maximum power command accepted
<PowMinMaxGFSK> NOTS | CHANged | MAX | MIN | NNM
NOTS: not supported (command not accepted by the EUT)
CHANged: changed one step
MAX: max power reached
MIN: min power reached
NNM: no new message
<PowChangeDQPSK>NNE | UP | DOWN | MAX
<PowMinMaxDQPSK>NOTS | CHANged | MAX | MIN | NNM
<PowChangeDPSK> NNE | UP | DOWN | MAX
<PowMinMaxDPSK> NOTS | CHANged | MAX | MIN | NNM
Example: See Retrieve EUT Information and Capabilities
Usage: Query only
Firmware/Software: V3.2.70
Manual operation: See "Power Control, Power State (BR/EDR)" on page 44
SENSe:BLUetooth:SIGN<i>:EUT:PCONtrol:STATe:DPSK?
SENSe:BLUetooth:SIGN<i>:EUT:PCONtrol:STATe:DQPSk?
SENSe:BLUetooth:SIGN<i>:EUT:PCONtrol:STATe:GFSK?
Displays the EUT responses to the enhanced power control state commands for
GFSK-modulated BR and π/4 DQPSK or 8DPSK-modulated EDR packets. The modu-
lation is indicated by the last mnemonic.
Return values:
<PowerChange> NNE | UP | DOWN | MAX
NNE: none
UP: power up command accepted
DOWN: power down command accepted
MAX: maximum power command accepted
<PowerMinMax> NOTS | CHANged | MAX | MIN | NNM
NOTS: not supported (command not accepted by the EUT)
CHANged: changed one step
MAX: max power reached
MIN: min power reached
NNM: no new message
Example: See Retrieve EUT Information and Capabilities
Usage: Query only
Firmware/Software: V3.2.60
Manual operation: See "Power Control, Power State (BR/EDR)" on page 44
SENSe:BLUetooth:SIGN<i>:CONNection:AUDio:LINFo?
Queries the parameters of active audio connection.
Return values:
<SpeechCode> CVSD | ALAW | ULAW | MSBC
CVSD (8 kHz), A-law (8 kHz), μ-law (8 kHz), or mSBC (16 kHz)
codec
<LinkType> SCO | ESCO
Synchronous connection-oriented (SCO) or enhanced synchro-
nous connection-oriented (eSCO) link
<PacketType> HV1 | HV2 | HV3 | EV3 | EV4 | EV5 | 2EV3 | 3EV3 | 2EV5 |
3EV5
HV1: SCO packets high-quality voice, 1/3 rate FEC
HV2: SCO packets high-quality voice, 2/3 rate FEC
HV3: SCO packets high-quality voice, no FEC
EV3, EV4, EV5: eSCO packets on the top of BR ACL connection
2EV3, 3EV3, 2EV5, 3EV5: eSCO packets on the top of EDR
ACL connection (2-EV3, 3-EV3, 2-EV5, 3-EV5 packets)
<SampleRate> float
Range: 0 kHz to 999 kHz
<DataRate> decimal
Range: 0 kbit/s to 9999 kbit/s
Example: See Configure Audio Profile
Usage: Query only
Firmware/Software: V3.5.50
V3.5.60: added <SpeechCode> ALAW and ULAW
Options: R&S CMW-KS602
Manual operation: See "Link Info" on page 51
CLEan:BLUetooth:SIGN<i>:ELOGging
Clears the event log.
Example: See Query event log
Usage: Event
Firmware/Software: V3.7.30
Manual operation: See "Event Log" on page 52
SENSe:BLUetooth:SIGN<i>:ELOGging:ALL?
Queries all entries of the event log.
For each entry three parameters are returned, from oldest to latest entry: {<Time-
stamp>, <Category>, <Event>}entry 1, {<Timestamp>, <Category>, <Event>}entry 2, ...
Return values:
<Timestamp> string
Timestamp of the entry as string in the format "hh:mm:ss"
<Category> INFO | WARNing | ERRor | CONTinue
Category of the entry, as indicated in the main view by an icon
CONTinue means the continuation of previous entry.
<Event> string
Text string describing the event
Example: See Query event log
Usage: Query only
Firmware/Software: V3.7.30
Manual operation: See "Event Log" on page 52
SENSe:BLUetooth:SIGN<i>:ELOGging:LAST?
Queries the latest entry of the event log.
Return values:
<Timestamp> string
Timestamp of the entry as string in the format "hh:mm:ss"
<Category> INFO | WARNing | ERRor | CONTinue
Category of the entry, as indicated in the main view by an icon
CONTinue means the continuation of previous entry.
<Event> string
Text string describing the event
Usage: Query only
Firmware/Software: V3.7.30
Manual operation: See "Event Log" on page 52
SENSe:BLUetooth:SIGN<i>:EUT:CSETtings:LESignaling?
Queries the connection parameters for LE normal mode.
Return values:
<ConnectionInt> float
Range: 6 to 3200
<SupervisionTout> float
Supervision timeout
Range: 100 ms to 32E+3 ms
<SlaveLatency> float
Slave latency
Range: 0 to 499
Example: See Connect
Usage: Query only
Firmware/Software: V3.7.61, V3.7.80: added <SlaveLatency>
Options: R&S CMW-KS601
Manual operation: See "Connection Interval, Connection Timeout, Slave Latency"
on page 56
The following queries retrieve information about the connected EUT as shown in the
"EUT Info" section of the main view.
SENSe:BLUetooth:SIGN<i>:EUT:INFormation:BDADdress?...............................................166
SENSe:BLUetooth:SIGN<i>:EUT:INFormation:CLASs?......................................................166
SENSe:BLUetooth:SIGN<i>:EUT:INFormation:COMPany?.................................................166
SENSe:BLUetooth:SIGN<i>:EUT:INFormation:NAME?...................................................... 167
SENSe:BLUetooth:SIGN<i>:EUT:INFormation:VERSion?...................................................167
SENSe:BLUetooth:SIGN<i>:EUT:INFormation:LESignaling?.............................................. 167
SENSe:BLUetooth:SIGN<i>:EUT:INFormation:BDADdress?
Gets the address (BD_ADDR) of the connected Bluetooth device.
Return values:
<BDAddress> hex
The Bluetooth device address in hexadecimal notation.
Range: #H0 to #HFFFFFFFFFFFF (12 hexadecimal digits)
Usage: Query only
Firmware/Software: V3.0.12
Manual operation: See "Device Information" on page 46
SENSe:BLUetooth:SIGN<i>:EUT:INFormation:CLASs?
Gets the major and the minor device class of the connected EUT as specified in https://
www.bluetooth.org/Technical/AssignedNumbers/baseband.htm.
Return values:
<MajorDevClass> string
<MinorDevClass> string
Usage: Query only
Firmware/Software: V3.0.12
Manual operation: See "Device Information" on page 46
SENSe:BLUetooth:SIGN<i>:EUT:INFormation:COMPany?
Queries the company identifier (CompId) as defined in http://www.bluetooth.org/Tech-
nical/AssignedNumbers/identifiers.htm
Return values:
<Company> string
Usage: Query only
Firmware/Software: V3.0.12
Manual operation: See "Device Information" on page 46
SENSe:BLUetooth:SIGN<i>:EUT:INFormation:NAME?
Gets the name of the connected device.
Return values:
<Name> string
Up to 255 characters
Usage: Query only
Firmware/Software: V3.0.12
Manual operation: See "Device Name" on page 44
SENSe:BLUetooth:SIGN<i>:EUT:INFormation:VERSion?
Gets LMP_version_res information.
Return values:
<LMP> string
Textual representation of the LMP version (VersNr) as defined
in http://www.bluetooth.org/Technical/AssignedNumbers/
link_manager.htm
<Company> string
Textual representation of the company identifier (CompId) as
defined in http://www.bluetooth.org/Technical/AssignedNumbers/
identifiers.htm
<LMPSubversion> string
LMP subversion number (SubVersNr), a company-internal ver-
sion number
Usage: Query only
Firmware/Software: V3.0.12
Manual operation: See "LMP Version and Subversion (BR/EDR)" on page 44
SENSe:BLUetooth:SIGN<i>:EUT:INFormation:LESignaling?
Retrieves EUT information as device name, device address and GAP mode.
Return values:
<DeviceName> string
<AddressType> PUBLic | RANDom | PIDentity | RSIDentity
Public device address, random device address: random private
ID, random static ID
<GM_Discoverable> OFF | ON
GAP mode general discoverable
<GM_Limit_Disc> OFF | ON
GAP mode limited discoverable
<GM_Connectable> OFF | ON
GAP mode undirected connectable
<GM_Direct_Con> OFF | ON
GAP mode directed connectable
Example: See Query results
Usage: Query only
Firmware/Software: V3.7.50
Options: R&S CMW-KS601
Manual operation: See "Device Name" on page 44
The following queries retrieve information about the connected EUT as shown in the
"EUT Capabilities" section of the main view.
SENSe:BLUetooth:SIGN<i>:EUT:CAPability:CONNection?................................................ 168
SENSe:BLUetooth:SIGN<i>:EUT:CAPability:ENCRyption?.................................................169
SENSe:BLUetooth:SIGN<i>:EUT:CAPability:PSAVing?......................................................169
SENSe:BLUetooth:SIGN<i>:EUT:CAPability:PCONtrol?.....................................................170
SENSe:BLUetooth:SIGN<i>:EUT:CAPability:EPControl?....................................................170
SENSe:BLUetooth:SIGN<i>:EUT:CAPability:ACL?............................................................ 170
SENSe:BLUetooth:SIGN<i>:EUT:CAPability:SCO?............................................................171
SENSe:BLUetooth:SIGN<i>:EUT:CAPability:ESCO?......................................................... 171
SENSe:BLUetooth:SIGN<i>:EUT:CAPability:SCLass?....................................................... 172
SENSe:BLUetooth:SIGN<i>:EUT:CAPability:LESignaling?................................................. 172
SENSe:BLUetooth:SIGN<i>:EUT:CAPability:CONNection?
Gets the connection-related properties and capabilities of the connected EUT.
Return values:
<PageScanMode> 0X00 | 0X01 | 0X02 | 0X03
The page scan mode that is used for default page scan:
0X00: mandatory page scan mode
0X01: optional page scan mode I
0X02: optional page scan mode II
0X03: optional page scan mode III
<PgScanPrdMode> P0 | P1 | P2
Page scan period mode
<PgScanRepMode> R0 | R1 | R2
Page scan repetition mode
<PScheme> OFF | ON
"Optional paging scheme" support
<SlotOffset> OFF | ON
"Slot offset" support
<TimingAcc> OFF | ON
"Timing accuracy" support
<Switch> OFF | ON
"Switching between master and slave" support
<RSSI> OFF | ON
"Received signal strength indication" support
Usage: Query only
Firmware/Software: V3.0.12
Manual operation: See "Paging and Other Connection Capabilities (BR/EDR)"
on page 47
SENSe:BLUetooth:SIGN<i>:EUT:CAPability:ENCRyption?
Queries whether the connected EUT supports encryption (OFF|ON)
Return values:
<Encryption> OFF | ON
Usage: Query only
Firmware/Software: V3.0.12
Manual operation: See "Paging and Other Connection Capabilities (BR/EDR)"
on page 47
SENSe:BLUetooth:SIGN<i>:EUT:CAPability:PSAVing?
Gets the power saving-related capabilities of the connected EUT. For each capability,
either OFF or ON is returned
Return values:
<Hold> OFF | ON
Hold mode
<Sniff> OFF | ON
Sniff mode
<Park> OFF | ON
Park mode
Usage: Query only
Firmware/Software: V3.0.12
Manual operation: See "Power Saving and Power Control Capabilities (BR/EDR)"
on page 47
SENSe:BLUetooth:SIGN<i>:EUT:CAPability:PCONtrol?
Queries whether the connected EUT supports legacy power control (OFF|ON)
Return values:
<PowerControl> OFF | ON
Usage: Query only
Firmware/Software: V3.0.12
Manual operation: See "Power Saving and Power Control Capabilities (BR/EDR)"
on page 47
SENSe:BLUetooth:SIGN<i>:EUT:CAPability:EPControl?
Queries whether the connected EUT supports enhanced power control (OFF|ON)
Return values:
<EPowerControl> OFF | ON
Usage: Query only
Firmware/Software: V3.0.12
SENSe:BLUetooth:SIGN<i>:EUT:CAPability:ACL?
Gets the ACL-related capabilities of the connected EUT. Except for the flow control lag,
for each capability either OFF or ON is returned.
Return values:
<FCLag> decimal
Flow control lag
Range: 0 to 7
Default unit: 256 bytes
<DH3DM3> OFF | ON
Three-slot packets
<DH5DM5> OFF | ON
Five-slot packets
<EDR3Slot> OFF | ON
Three-slot EDR ACL packets
<EDR5Slot> OFF | ON
Five-slot EDR ACL packets
<EDR2Mbps> OFF | ON
EDR ACL 2 Mbit/s
<EDR3Mpbs> OFF | ON
EDR ACL 3 Mbit/s
Usage: Query only
Firmware/Software: V3.0.12
Manual operation: See "Packet Type and Data Link Type Capabilities (BR/EDR)"
on page 47
SENSe:BLUetooth:SIGN<i>:EUT:CAPability:SCO?
Gets the SCO-related capabilities of the connected EUT. For each capability, either
OFF or ON is returned
Return values:
<CQDD> OFF | ON
Channel quality driven data rate
<Link> OFF | ON
SCO link
<TSData> OFF | ON
Transparent SCO data
<HV2P> OFF | ON
HV2 packets
<HV3P> OFF | ON
HV3 packets
<ULAW> OFF | ON
μ-law log
<ALAW> OFF | ON
A-law log
<CVSD> OFF | ON
Continuous variable slope delta modulation
Example: See Query results
Usage: Query only
Firmware/Software: V3.0.12
Manual operation: See "Packet Type and Data Link Type Capabilities (BR/EDR)"
on page 47
SENSe:BLUetooth:SIGN<i>:EUT:CAPability:ESCO?
Gets the e-SCO-related capabilities of the connected EUT. For each capability, either
OFF or ON is returned
Return values:
<EV3Packets> OFF | ON
EV3 packets
<EV4Packets> OFF | ON
EV4 packets
<EV5Packets> OFF | ON
EV5 packets
<ThreeSlotEDRPck> OFF | ON
2-EV5 / 3-EV5 packets over three slots
<EDR_2MbpsMode> OFF | ON
2-EV3 / 2-EV5 packets
<EDR_3MbpsMode> OFF | ON
3-EV3 / 3-EV5 packets
Example: See Query results
Usage: Query only
Firmware/Software: V3.5.50
Manual operation: See "Packet Type and Data Link Type Capabilities (BR/EDR)"
on page 47
SENSe:BLUetooth:SIGN<i>:EUT:CAPability:SCLass?
Gets the (major) service class of the connected EUT as specified in https://www.blue-
tooth.org/Technical/AssignedNumbers/baseband.htm.
Return values:
<ServiceClass> string
Example: See Query results
Usage: Query only
Firmware/Software: V3.0.12
SENSe:BLUetooth:SIGN<i>:EUT:CAPability:LESignaling?
Queries capabilities retrieved from the EUT.
Return values:
<1_DeviceName> string
LE device name
<2_LE_Encryption> OFF | ON
Support of LE encryption
<3_ConnParamReq> OFF | ON
Support of connection parameter request procedure
<4_ExtRejectionInd> OFF | ON
Support of extended rejection indication
<5_SlaveInitFeatEx> OFF | ON
Support of slave-initiated features exchange
<6_LE_Ping> OFF | ON
Support of LE ping
<7_Data_Pk_L_Ex> OFF | ON
Support of LE data packet length extension
<8_LL_Privacy> OFF | ON
Support of LL privacy
<9_ExScanFiltPol> OFF | ON
Support of extended scanner filter policies
<10_LE_2M_PHY> OFF | ON
Support of LE 2 Mbps PHY
<11_StabModTrans> OFF | ON
Support of stable modulation index for transmitter
<12_StabModRec> OFF | ON
Support of stable modulation index for receiver
<13_Coded_PHY> OFF | ON
Support of LE coded PHY
<14_LE_Ext_Adv> OFF | ON
Support of extended advertising
<15_Periodic_Adv> OFF | ON
Support of LE periodic advertising
<16_Chan_Sel_Alg2> OFF | ON
Support of channel selection algorithm No. 2
<17_LE_PowClass1> OFF | ON
Support of LE power class 1
<18_MinNoUsedCh> OFF | ON
Support of procedure for minimum number of used channels
Example: See Query results
Usage: Query only
CONFigure:BLUetooth:SIGN<i>:CONNection:PCONtrol:PCMode:LESignaling
<OverrideCapabilites>
Specifies, whether the power commands respect the reported EUT capabilities or
ignore them.
Parameters:
<OverrideCapabilites>OFF | ON
OFF: The reported EUT capabilities are respected.
ON: The reported EUT capabilities are ignored.
*RST: OFF
Firmware/Software: V3.8.20
Options: R&S CMW-KS601
Manual operation: See "Ignore Power Control Capability" on page 91
CONFigure:BLUetooth:SIGN<i>:CONNection:PCONtrol:SSIZe:LESignaling
<stepSize>
Sets the step size for increasing / decreasing the Tx power.
Parameters:
<stepSize> numeric
Range: 0 dB to 10 dB
*RST: 3 dB
Firmware/Software: V3.8.20
Options: R&S CMW-KS601
Manual operation: See "Power Up / Power Down / Step Size (hotkey)" on page 61
CONFigure:BLUetooth:SIGN<i>:CONNection:PCONtrol:STEP:ACTion:
LESignaling <PControl>
Sends a command to the DUT to increase/decrease power.
Setting parameters:
<PControl> UP | DOWN | MAX
One step up, one step down, command to maximum DUT Tx
power
Usage: Event
Firmware/Software: V3.8.20
Options: R&S CMW-KS601
Manual operation: See "Power Up / Power Down / Step Size (hotkey)" on page 61
SENSe:BLUetooth:SIGN<i>:EUT:PCONtrol:STATe:LESignaling?
Displays the DUT's responses to the power control state commands for low energy.
Return values:
<PowFlag> NONE | MIN | MAX
NONE: no new message
MIN: minimum power command accepted
MAX: maximum power command accepted
<PowDelta> decimal
Returns the power difference before and after the command
execution
Range: -100 dB to +100 dB
<CurrentPower> decimal
Returns the actual Tx power level of the DUT
Range: -200 dBm to +100 dBm
<EutState> FAIL | OK
Checks the command execution.
Usage: Query only
Firmware/Software: V3.8.20
Options: R&S CMW-KS601
Manual operation: See "Event Log" on page 52
The following commands configure inquiry and paging for BR/EDR signals.
CONFigure:BLUetooth:SIGN<i>:CONNection:BDADdress:CMW........................................ 176
CONFigure:BLUetooth:SIGN<i>:CONNection:BDADdress:EUT.......................................... 176
CONFigure:BLUetooth:SIGN<i>:CONNection:SVTimeout.................................................. 176
CONFigure:BLUetooth:SIGN<i>:CONNection:INQuiry:ILENgth...........................................177
CONFigure:BLUetooth:SIGN<i>:CONNection:INQuiry:NOResponses................................. 177
CONFigure:BLUetooth:SIGN<i>:CONNection:PAGing:TOUT..............................................177
CONFigure:BLUetooth:SIGN<i>:CONNection:PAGing:PSRMode........................................178
CONFigure:BLUetooth:SIGN<i>:CONNection:INQuiry:PTARgets:CATalog?......................... 178
CONFigure:BLUetooth:SIGN<i>:CONNection:PAGing:PTARget..........................................179
CONFigure:BLUetooth:SIGN<i>:CONNection:BDADdress:CMW <BDAddress>
Sets/gets the Bluetooth device address (BD_ADDR) of the R&S CMW.
Parameters:
<BDAddress> hex
Range: #H0 to #HFFFFFFFFFFFF (12 hexadecimal digits)
*RST: #H123456123456
Example: See Initialization and Basic Configuration
Firmware/Software: V3.0.12
Manual operation: See "CMW BD Address" on page 85
CONFigure:BLUetooth:SIGN<i>:CONNection:BDADdress:EUT <BDAddress>
Sets/gets the Bluetooth device address (BD_ADDR) of a default device to attempt a
connection to. If no inquiry was made before, this BD_ADDR is used for paging; other-
wise, the device to page can be set via CONFigure:BLUetooth:SIGN<i>:
CONNection:PAGing:PTARget.
Parameters:
<BDAddress> hex
Range: #H0 to #HFFFFFFFFFFFF (12 hexadecimal digits)
*RST: #H123456789012
Example: See Manually specify BD address
Firmware/Software: V3.0.12
Manual operation: See "BD Address" on page 86
Parameters:
<Supervision numeric
Timeout> Range: 400 slots to 65535 slots
*RST: 8000 slots
Default unit: slots
Example: See Configure Paging for BR/EDR
Firmware/Software: V3.0.12
Manual operation: See "Supervision Timeout" on page 86
CONFigure:BLUetooth:SIGN<i>:CONNection:INQuiry:ILENgth <InquiryLength>
Sets/gets the Inquiry_Length parameter, i.e. the total duration of the inquiry mode.
Parameters:
<InquiryLength> numeric
The inquiry length in units of 1.28 s
Range: 1 to 24
*RST: 10
Default unit: 1.28 s
Example: See Inquire or Manually Specify DUT for BR/EDR
Firmware/Software: V3.0.12
Manual operation: See "Inquiry Length" on page 86
CONFigure:BLUetooth:SIGN<i>:CONNection:INQuiry:NOResponses
<NumberResponses>
Sets/gets the maximum number of responses recorded during an inquiry.
Parameters:
<NumberResponses> numeric
The maximum number of responses, where 0 means "unlimi-
ted".
Range: 0 to 12
*RST: 12
Example: See Inquire or Manually Specify DUT for BR/EDR
Firmware/Software: V3.0.12
Manual operation: See "Number of Inquiry Responses" on page 86
CONFigure:BLUetooth:SIGN<i>:CONNection:PAGing:TOUT <Timeout>
Sets/gets the Page_Timeout configuration parameter, i.e. the maximum time the local
link manager waits for a baseband page response from the EUT.
Parameters:
<Timeout> integer
Range: 22 to 65535
*RST: 8192
Default unit: slot (625 µs)
Example: See Configure Paging for BR/EDR
Firmware/Software: V3.0.12
V3.5.30: changed range
Manual operation: See "Paging Timeout" on page 87
CONFigure:BLUetooth:SIGN<i>:CONNection:PAGing:PSRMode <PSRMode>
Sets/gets the page scan repetition mode to be used for the default device (see
CONFigure:BLUetooth:SIGN<i>:CONNection:BDADdress:EUT on page 176).
Parameters:
<PSRMode> R0 | R1 | R2
Paging mode R0, R1, R2. Select the value according to the
page scan repetition mode of the default device.
*RST: R2
Example: See Configure Paging for BR/EDR
Firmware/Software: V3.0.12
Manual operation: See "Page Scan Repetition Mode" on page 86
CONFigure:BLUetooth:SIGN<i>:CONNection:INQuiry:PTARgets:CATalog?
This query returns a list of all targets available for paging.
If no inquiry was made before, this list only contains the default device (see
CONFigure:BLUetooth:SIGN<i>:CONNection:BDADdress:EUT). After inquiry, it
also contains the devices that were responding (in chronological order).
Return values:
<NoDiscoveredDev> decimal
The number of devices discovered during inquiry
{<ItemNumber>, decimal
<DiscoveredEUT>} string
A comma-separated list of Bluetooth devices, where each
device is represented by an item number and its BD_Address in
hexadecimal notation. Item number 0 always represents the
default target.
Example: See Inquire BD address
Usage: Query only
Firmware/Software: V3.0.12
CONFigure:BLUetooth:SIGN<i>:CONNection:PAGing:PTARget <Target>
Selects the device to page from the paging target catalog (see CONFigure:
BLUetooth:SIGN<i>:CONNection:INQuiry:PTARgets:CATalog?
on page 178).
After a reset, if no inquiry was made before or if no device was detected during the pre-
vious inquiry, only the default device (<Target>=0) can be selected. After a successful
inquiry, the first discovered device (<Target>=1) is pre-selected.
Parameters:
<Target> numeric
Index of the device in the paging target catalog, where 0 always
corresponds to the default device.
If an invalid index is selected, an error message is returned.
Range: Integer >= 0
*RST: 0
Example: See Configure Paging for BR/EDR
Firmware/Software: V3.0.12
Manual operation: See "For Paging" on page 86
CONFigure:BLUetooth:SIGN<i>:TCONnection:PINCode:LENergy...................................... 186
CONFigure:BLUetooth:SIGN<i>:TCONnection:SPINenable:LENergy.................................. 187
CONFigure:BLUetooth:SIGN<i>:TMODe:LENergy.............................................................187
CONFigure:BLUetooth:SIGN<i>:CONNection:ADDRess:CMW:LESignaling
<CmwAddress>
Sets the public address of R&S CMW
Parameters:
<CmwAddress> hex
Range: #H0 to #HFFFFFFFFFFFF
*RST: #H1263456123456
Example: See Connect
Firmware/Software: V3.7.50
Options: R&S CMW-KS601
Manual operation: See "CMW Address" on page 90
CONFigure:BLUetooth:SIGN<i>:CONNection:ADDRess:EUT:LESignaling
<AddressDef>
Specifies the default EUT.
Parameters:
<AddressDef> hex
Range: #H0 to #HFFFFFFFFFFFF
*RST: #H1263456789012
Example: See Connect LE (Normal Mode)
Firmware/Software: V3.7.50
Options: R&S CMW-KS601
Manual operation: See "Default EUT Address" on page 90
CONFigure:BLUetooth:SIGN<i>:CONNection:ADDRess:TYPE:LESignaling
<AddrType>
Selects public or random addressing.
Parameters:
<AddrType> PUBLic | RANDom
*RST: PUBL
Example: See Connect LE (Normal Mode)
Firmware/Software: V3.7.50
Options: R&S CMW-KS601
Manual operation: See "CMW Address Type" on page 90
CONFigure:BLUetooth:SIGN<i>:CONNection:AINTerval:LESignaling <AdvInt>
Specifies the interval between two consecutive advertisers for an instrument in periph-
eral LE role.
Parameters:
<AdvInt> numeric
Range: 32 to 16.384E+3
*RST: 160
Example: See Configure paging
Firmware/Software: V3.7.80
Options: R&S CMW-KS601
Manual operation: See "Advertiser Interval < Peripheral" on page 89
CONFigure:BLUetooth:SIGN<i>:CONNection:INQuiry:DURation:LESignaling
<InqDuration>
Specifies the total inquiry duration.
Parameters:
<InqDuration> numeric
Range: 5 ms to 30E+3 ms
*RST: 10.24E+3 ms
Example: See Configure paging
Firmware/Software: V3.7.50
Options: R&S CMW-KS601
Manual operation: See "Inquiry < Central" on page 88
CONFigure:BLUetooth:SIGN<i>:CONNection:INQuiry:NOResponses:LESignaling
<NumberResponses>
Specifies the maximum number of responses recorded during an inquiry.
Parameters:
<NumberResponses> numeric
Range: 1 to 100
*RST: 10
Example: See Configure paging
Firmware/Software: V3.7.50
Options: R&S CMW-KS601
Manual operation: See "Inquiry < Central" on page 88
CONFigure:BLUetooth:SIGN<i>:CONNection:INQuiry:PTARgets:CATalog:
LESignaling?
This query returns a list of all targets available for paging, i.e. all LE devices found.
If no inquiry was made before, this list only contains the default device (see
CONFigure:BLUetooth:SIGN<i>:CONNection:ADDRess:EUT:LESignaling).
After inquiry, it also contains the devices that were responding (in chronological order).
Return values:
<NoDiscoveredDev> decimal
The number of devices discovered during inquiry
{<ItemNumber>, decimal
<DiscoveredEUT>} string
A comma-separated list of Bluetooth devices, where each
device is represented by an item number and its Address in
hexadecimal notation. Item number 0 always represents the
default target.
Example: See Configure paging
Usage: Query only
Firmware/Software: V3.7.50
Options: R&S CMW-KS601
Manual operation: See "Inquire (hotkey)" on page 62
CONFigure:BLUetooth:SIGN<i>:CONNection:INQuiry:SINTerval:LESignaling
<InqScanInt>
Specifies the Inquiry Scan Interval between two consecutive inquiry scans. The interval
in ms is calculated as the specified value multiplied by 0.625 ms.
Parameters:
<InqScanInt> numeric
Range: 4 to 16.384E+3
*RST: 48
Example: See Configure paging
Firmware/Software: V3.7.50
Options: R&S CMW-KS601
Manual operation: See "Inquiry < Central" on page 88
CONFigure:BLUetooth:SIGN<i>:CONNection:INQuiry:SWINdow:LESignaling
<InqScanWindow>
Specifies Inquiry Scan Window - the inquiry scan duration. The duration in ms is calcu-
lated as the specified value multiplied by 0.625 ms.
Parameters:
<InqScanWindow> numeric
Range: 4 to 16.384E+3
*RST: 48
Example: See Configure paging
Firmware/Software: V3.7.50
Options: R&S CMW-KS601
Manual operation: See "Inquiry < Central" on page 88
CONFigure:BLUetooth:SIGN<i>:CONNection:INTerval:LESignaling <Connection
Interval>
Sets the time interval between the two consecutive connection events. The interval in
ms is calculated as the specified value multiplied by 1.25 ms.
Parameters:
<Connection Interval> numeric
Range: 6 to 3200
*RST: 6
Example: See Connect
Firmware/Software: V3.7.50, V3.7.61: range extended, default value changed,
V3.7.62: unit changed
Options: R&S CMW-KS601
Manual operation: See "Connection Interval" on page 89
CONFigure:BLUetooth:SIGN<i>:CONNection:PAGing:PTARget:LESignaling
<Target>
Selects the EUT for paging. The default device is 0. For the inquiry results, see
CONFigure:BLUetooth:SIGN<i>:CONNection:INQuiry:PTARgets:CATalog:
LESignaling?.
Parameters:
<Target> numeric
Sequence number of device listed in inquiry results.
*RST: 0
Example: See Configure paging
Firmware/Software: V3.7.50
Options: R&S CMW-KS601
Manual operation: See "For Paging" on page 90
CONFigure:BLUetooth:SIGN<i>:CONNection:PAGing:TOUT:LESignaling
<Timeout>
Specifies the PageTimeout configuration parameter, i.e. the maximum time the local
link manager waits for a baseband page response from the EUT.
Parameters:
<Timeout> integer
Range: 10 ms to 30E+3 ms
*RST: 10E+3 ms
Default unit: s
Example: See Configure paging
Firmware/Software: V3.7.50
Options: R&S CMW-KS601
Manual operation: See "Connect < Central" on page 88
CONFigure:BLUetooth:SIGN<i>:CONNection:RADDress:CMW:LESignaling?
Queries the randomly generated address of R&S CMW
Return values:
<CmwAddress> hex
Range: #H0 to #HFFFFFFFFFFFF
Example: See Connect LE (Normal Mode)
Usage: Query only
Firmware/Software: V3.7.50
Options: R&S CMW-KS601
Manual operation: See "CMW Address" on page 90
CONFigure:BLUetooth:SIGN<i>:CONNection:SINTerval:LESignaling
<ConnScanInt>
Specifies the interval between two consecutive page scans. The interval in ms is calcu-
lated as the specified value multiplied by 0.625 ms.
Parameters:
<ConnScanInt> numeric
Range: 4 to 16.384E+3
*RST: 48
Example: See Configure paging
Firmware/Software: V3.7.50
Options: R&S CMW-KS601
Manual operation: See "Connect < Central" on page 88
CONFigure:BLUetooth:SIGN<i>:CONNection:SLATency:LESignaling:
CPERipheral <SlaveLatency>
CONFigure:BLUetooth:SIGN<i>:CONNection:SLATency:LESignaling[:CCENtral]
<SlaveLatency>
Specify the latency of slave responses for connection tests, central ..:CCENtral and
peripheral ..:CPERipheralR&S CMW LE role.
Parameters:
<SlaveLatency> numeric
Range: 0 to 499
*RST: 0
Default unit: The number of consecutive connection events
Example: See Connect LE (Normal Mode)
Firmware/Software: V3.7.70, V3.7.80: range extended, added command for periph-
eral role
Options: R&S CMW-KM601
Manual operation: See "Slave Latency" on page 88
CONFigure:BLUetooth:SIGN<i>:CONNection:SVTimeout:LESignaling
<Supervision Timeout>
Specifies the duration of tolerated connection breaks down.
Parameters:
<Supervision numeric
Timeout> Range: 100 ms to 32E+3 ms
*RST: 5000 ms
Default unit: ms
Firmware/Software: V3.7.50, V3.7.62: unit changed
Options: R&S CMW-KS601
Manual operation: See "Supervision Timeout" on page 89
CONFigure:BLUetooth:SIGN<i>:CONNection:SWINdow:LESignaling
<ConnScanWin>
Specifies the interval between two consecutive page scans. The interval in ms is calcu-
lated as the specified value multiplied by 0.625 ms.
Parameters:
<ConnScanWin> numeric
Range: 4 to 16.384E+3
*RST: 48
Example: See Configure paging
Firmware/Software: V3.7.50
CONFigure:BLUetooth:SIGN<i>:CONNection:WFCMap:LESignaling:CCENtral
<WaitForChMap>
Specifies the number of connection events to wait before checking the channel map
change.
Parameters:
<WaitForChMap> numeric
Range: 6 to 100
*RST: 10
Example: See Configure paging
Firmware/Software: V3.7.81
Options: R&S CMW-KS601
Manual operation: See "Wait for Channel Map in Connection Intervals" on page 89
CONFigure:BLUetooth:SIGN<i>:TCONnection:INTerval:LESignaling <Connection
Interval>
Sets the time interval between the two consecutive connection events for LE test
mode. The interval in ms is calculated as the specified value multiplied by 1.25 ms.
Parameters:
<ConnectionInterval> numeric
Range: 6 to 3200
*RST: 50
Example: See Configure LE Test Mode
Firmware/Software: V3.7.90
Options: R&S CMW-KS601
Manual operation: See "Connection Interval (hotkey)" on page 59
CONFigure:BLUetooth:SIGN<i>:TCONnection:PINCode:LENergy <PIN>...
Specifies the PIN for LE test mode. The value must match with the configuration on the
DUT.
Parameters:
<PIN> integer
Comma-separated sequence of eight integers
Range: 0 to 255
*RST: 17
Example: See Configure LE Test Mode
Firmware/Software: V3.7.90
Options: R&S CMW-KS601
Manual operation: See "Test Mode PIN" on page 91
CONFigure:BLUetooth:SIGN<i>:TCONnection:SPINenable:LENergy
<SendEnablePIN>
Enables or disables LE test mode on the DUT using a PIN. The PIN to sent is specified
via:
CONFigure:BLUetooth:SIGN<i>:TCONnection:SPINenable:LENergy
Parameters:
<SendEnablePIN> OFF | ON
*RST: ON
Example: See Configure LE Test Mode
Firmware/Software: V3.7.90
Options: R&S CMW-KS601
Manual operation: See "Test Mode Send Enable with PIN" on page 90
CONFigure:BLUetooth:SIGN<i>:TMODe:LENergy <EnableTestMode>
Enables or disables LE test mode at the R&S CMW.
Parameters:
<EnableTestMode> OFF | ON
*RST: OFF
Firmware/Software: V3.7.90
Options: R&S CMW-KS601
Manual operation: See "Test Mode Available" on page 90
CONFigure:BLUetooth:SIGN<i>:CONNection:WHITening...................................................191
CONFigure:BLUetooth:SIGN<i>:CONNection:SYNWord:LENergy.......................................191
CONFigure:BLUetooth:SIGN<i>:RFSettings:NANTenna:CTE:LENergy................................ 191
CONFigure:BLUetooth:SIGN<i>:AUDio:PRFRole <ProfileRole>
Specifies the audio profile role of the EUT.
Parameters:
<ProfileRole> HNDFree | ADGate | ASINk
Hands free, hands free - audio gateway, A2DP sink
*RST: HNDF
Example: See Configure Audio Profile
Firmware/Software: V3.5.40
Options: R&S CMW-KS602
R&S CMW-KS603 for ASINk
Manual operation: See "Profile" on page 68
CONFigure:BLUetooth:SIGN<i>:CONNection:CMW:ROLE <Role>
Specifies the connection control role of the R&S CMW for audio connections.
Parameters:
<CMWRole> MASTer | SLAVe
*RST: MAST
Example: See Configure Audio Profile
Firmware/Software: V3.5.50
Manual operation: See "CMW Role" on page 66
CONFigure:BLUetooth:SIGN<i>:CONNection:CMW:ROLE:LESignaling
<SigCmwRole>
Sets the LE role of the instrument for LE connection tests.
Parameters:
<SigCmwRole> CENTral | PERipheral
*RST: CENT
Example: See Connect LE (Normal Mode)
Firmware/Software: V3.7.50, V3.7.80: added PERipheral
Options: R&S CMW-KS601
Manual operation: See "CMW Role" on page 68
CONFigure:BLUetooth:SIGN<i>:CONNection:IENCryption:LESignaling:CCENtral
<IndEncryption>
CONFigure:BLUetooth:SIGN<i>:CONNection:IENCryption:LESignaling:
CPERipheral <IndEncryption>
Indicates the R&S CMW support of encryption in central (..:CCENtral) or peripheral
(..:CPERipheral) LE role. The command is relevant for LE connection tests.
Parameters:
<IndEncryption> OFF | ON
*RST: ON
Example: See Connect LE (Normal Mode)
Firmware/Software: V3.7.80
Options: R&S CMW-KS601
Manual operation: See "Indicate Encryption Support" on page 89
CONFigure:BLUetooth:SIGN<i>:CONNection:RENCryption:LESignaling:
CCENtral <RejEncryption>
CONFigure:BLUetooth:SIGN<i>:CONNection:RENCryption:LESignaling:
CPERipheral <RejEncryption>
Specifies, whether the encryption request from the EUT is accepted or rejected by the
R&S CMW in central (..:CCENtral) or peripheral (..:CPERipheral) LE role. The
command is relevant for LE connection tests.
Parameters:
<RejEncryption> OFF | ON
OFF: accept encryption request
ON: reject encryption request
*RST: OFF
Example: See Connect LE (Normal Mode)
Firmware/Software: V3.7.80
Options: R&S CMW-KS601
Manual operation: See "Reject Encryption Support" on page 89
CONFigure:BLUetooth:SIGN<i>:OPMode <OperatingMode>
Specifies operating mode of R&S CMW.
Parameters:
<OperatingMode> CNTest | RFTest | ECMode | PROFiles | AUDio | LETMode
CNTest: connection test for BR/EDR or LE (OTA)
RFTest: test mode for BR/EDR or direct test for LE
ECMode: echo mode for BR/EDR
PROFiles: profiles for BR/EDR
AUDio: audio mode for BR/EDR
CONFigure:BLUetooth:SIGN<i>:CONNection:PPERiod <PollPeriod>
Defines how often the R&S CMW transmitts a poll packet.
If the set poll period is too small for the selected packet type (for x-DH1, x-DH3, or x-
DH5), it is automatically changed to 2, 4, or 6 slots. X = 1, 2, 3.
Parameters:
<PollPeriod> numeric
Range: x-DH1: 1 to 127, x-DH3: 2 to 127, x-DH5: 3 to 127
*RST: 1
Default unit: Unit corresponds to two slots
Example: See Transmitter test mode
Firmware/Software: V3.2.30
Options: R&S CMW-KS610
Manual operation: See "Poll Period (BR/EDR only)" on page 94
CONFigure:BLUetooth:SIGN<i>:CONNection:PPERiod:MINimum <PollPeriodMin>
Enables minimum poll period.
To prevent simultaneous master/slave transmission, the minimum poll period for an x-
DHn packet type (n = 1, 3, 5) is automatically set to n+1 slots.
Parameters:
<PollPeriodMin> OFF | ON
*RST: ON
Example: See Transmitter test mode
Firmware/Software: V3.2.30
Options: R&S CMW-KS610
Manual operation: See "Poll Period (BR/EDR only)" on page 94
CONFigure:BLUetooth:SIGN<i>:CONNection:WHITening <Whitening>
Sets whether the EUT has to transmit ACL packets scrambled with a particular data
sequence in a loopback mode.
Parameters:
<Whitening> OFF | ON
*RST: OFF
Example: See Loopback test mode
Firmware/Software: V3.2.30
Options: R&S CMW-KS610
Manual operation: See "Whitening (BR/EDR only)" on page 94
CONFigure:BLUetooth:SIGN<i>:CONNection:SYNWord:LENergy <SynchWord>
Specifies the synchronization word used for LE connection.
Parameters:
<SynchWord> hex
Range: #H0 to #HFFFFFFFF
*RST: #H71764129
Example: See Configure Test Mode Classic
Firmware/Software: V3.5.40
Options: R&S CMW-KS611
Manual operation: See "Test Packet Sync Word (LE only)" on page 95
CONFigure:BLUetooth:SIGN<i>:RFSettings:NANTenna:CTE:LENergy
<NoOfAntenna>
Specifies the number of EUT's antennas. One reference and one non-reference anten-
nas are mandatory.
Parameters:
<NoOfAntenna> numeric
Range: 2 to 4
*RST: 4
Example: See Direct test mode
Firmware/Software: V3.7.70
Options: R&S CMW-KS722
Manual operation: See "Number of Antennae, Slot Duration" on page 54
CONFigure:BLUetooth:SIGN<i>:CONNection:AUDio:HFP:CASTartup
<CallActiveatStartup>
Enables the indication of the active call to the EUT for the audio profile role hands free.
Parameters:
<CallActiveatStartup> OFF | ON
*RST: ON
Example: See Configure Audio Profile
Firmware/Software: V3.5.40
Manual operation: See "Call is Active at Startup" on page 96
CONFigure:BLUetooth:SIGN<i>:CONNection:AUDio:PINCode <PinCode>
Specifies PIN code for audio profile tests.
Parameters:
<PinCode> string
*RST: 0000
Example: See Configure Audio Profile
Firmware/Software: V3.5.40
Manual operation: See "PIN Code" on page 95
CONFigure:BLUetooth:SIGN<i>:CONNection:AUDio:SECMode <SecurityMode>
Specifies security mode for audio tests.
Parameters:
<SecurityMode> SEC2 | SEC3
*RST: SEC3
Example: See Configure Audio Profile
Firmware/Software: V3.5.40
Manual operation: See "Security Mode" on page 96
CONFigure:BLUetooth:SIGN<i>:CONNection:AUDio:VOLControl:MICGain
<MicrophoneGain>
Controls microphone gain for audio tests.
Parameters:
<MicrophoneGain> numeric
Range: 0 to 15
*RST: 7
Example: See Configure Audio Profile
Firmware/Software: V3.5.40
Manual operation: See "Volume Control... (softkey)" on page 63
CONFigure:BLUetooth:SIGN<i>:CONNection:AUDio:VOLControl:SPEaker
<SpeakerVolume>
Controls speaker volume for audio tests.
Parameters:
<SpeakerVolume> numeric
Range: 0 to 15
*RST: 7
Example: See Configure Audio Profile
Firmware/Software: V3.5.40
Manual operation: See "Volume Control... (softkey)" on page 63
CONFigure:BLUetooth:SIGN<i>:CONNection:AUDio:CODec <Codec>
Specifies the codec to be used for synchronous connection-oriented audio connec-
tions.
Parameters:
<Codec> CVSD | ALAW | ULAW | MSBC
CVSD: continuously variable slope delta codec (8 kHz - SCO
link)
ALAW: A-law coding (8 kHz - SCO link)
ULAW: μ-law coding (8 kHz - SCO link)
CONFigure:BLUetooth:SIGN<i>:CONNection:AUDio:A2DP:ACCSlave <Assume
Acceptor Role in Slave Mode>
Allows the EUT to take control of the establishment of the A2DP connection when the
R&S CMW acts as the slave.
Parameters:
<Assume Acceptor OFF | ON
Role in Slave Mode> *RST: OFF
Example: See Configure Audio Profile
Firmware/Software: V3.5.70
Options: R&S CMW-K603
Manual operation: See "Assume Acceptor Role in Slave Mode" on page 97
CONFigure:BLUetooth:SIGN<i>:CONNection:AUDio:A2DP:ALCMethod
<AllocationMethod>
Defines the algorithm used to calculate the no. of allocated bits to represent each sub-
band sample.
Parameters:
<AllocationMethod> LOUDness | SNR
*RST: LOUD
Example: See Configure Audio Profile
Firmware/Software: V3.5.70
Options: R&S CMW-K603
Manual operation: See "Allocation Method" on page 97
CONFigure:BLUetooth:SIGN<i>:CONNection:AUDio:A2DP:BITRate?
Queries the bit rate calculated from the A2DP audio link parameters.
Return values:
<BitRate> decimal
Default unit: bit/s
CONFigure:BLUetooth:SIGN<i>:CONNection:AUDio:A2DP:BLKLength
<BlockLength>
Specifies the number of blocks of audio samples that are encoded in a single SBC
frame.
Parameters:
<BlockLength> BL4 | BL8 | BL12 | BL16
4, 8, 12, 16 blocks
*RST: BL16
Example: See Configure Audio Profile
Firmware/Software: V3.5.70
Options: R&S CMW-K603
Manual operation: See "Block Length" on page 96
CONFigure:BLUetooth:SIGN<i>:CONNection:AUDio:A2DP:CHMode
<ChannelMode>
Specifies channel mode.
Parameters:
<ChannelMode> MONO | DUAL | STEReo | JSTereo
Mono, dual, stereo, joint stereo
*RST: DUAL
Example: See Configure Audio Profile
Firmware/Software: V3.5.70
Options: R&S CMW-K603
Manual operation: See "Channel Mode" on page 96
CONFigure:BLUetooth:SIGN<i>:CONNection:AUDio:A2DP:CODec <Codec>
Specifies A2DP codec.
Parameters:
<Codec> SBC
Only subband coding is supported
*RST: SBC
Example: See Configure Audio Profile
Firmware/Software: V3.5.70
Options: R&S CMW-K603
Manual operation: See "Codec" on page 96
CONFigure:BLUetooth:SIGN<i>:CONNection:AUDio:A2DP:MAXBitpool
<MaximumBitpool>
Specifies maximum bitpool value.
Parameters:
<MaximumBitpool> numeric
Range: 8 to 250
*RST: 18
Example: See Configure Audio Profile
Firmware/Software: V3.5.70
Options: R&S CMW-K603
Manual operation: See "Minimum / Maximum Bitload" on page 97
CONFigure:BLUetooth:SIGN<i>:CONNection:AUDio:A2DP:MINBitpool
<MinimumBitpool>
Specifies minimum bitpool value.
Parameters:
<MinimumBitpool> numeric
Range: 2 to 18
*RST: 8
Example: See Configure Audio Profile
Firmware/Software: V3.5.70
Options: R&S CMW-K603
Manual operation: See "Minimum / Maximum Bitload" on page 97
CONFigure:BLUetooth:SIGN<i>:CONNection:AUDio:A2DP:SMPFrequency
<SamplingFrequency>
Specifies the sampling frequency.
Parameters:
<SamplingFrequency>SF16 | SF32 | SF441 | SF48
16 kHz, 32 kHz, 44.1 kHz, 48 kHz
*RST: SF48
Example: See Configure Audio Profile
Firmware/Software: V3.5.70
Options: R&S CMW-K603
Manual operation: See "Sampling Frequency" on page 96
CONFigure:BLUetooth:SIGN<i>:CONNection:AUDio:A2DP:SUBBands
<SubBands>
Specifies the number of subbands used by generated signal.
Parameters:
<SubBands> SB4 | SB8
Subband 4 or 8
*RST: SB8
Example: See Configure Audio Profile
Firmware/Software: V3.5.70
Options: R&S CMW-K603
Manual operation: See "Subbands" on page 96
CONFigure:BLUetooth:SIGN<i>:HWINterface<no> <HwInterface>
Defines interface used for tests.
Suffix: .
<no> 1..4
1: HW interface for LE tests
2: HW interface for BR / EDR tests
Parameters:
<HwInterface> NONE | RS232 | USB
RS232: USB connection with USB to RS232 adapter
NONE: no control via USB to be used
USB: direct USB connection
*RST: NONE
Example: See Configure USB Interface
Firmware/Software: V3.2.70
V3.5.30: added suffix <no> and value USB
Manual operation: See "HW Interface" on page 71
CONFigure:BLUetooth:SIGN<i>:COMSettings<no>:ERESet <EUTReset>
Commands to reset the EUT before starting tests.
Suffix: .
<no> 1..2
1: HW interface for LE tests
2: HW interface for BR / EDR tests
Parameters:
<EUTReset> ON | OFF
*RST: ON
Example: See Configure USB Interface
Firmware/Software: V3.2.70
V3.5.30: added suffix <no>
Manual operation: See "Reset EUT (Classic)" on page 71
CONFigure:BLUetooth:SIGN<i>:COMSettings:ETMode <EnableTestMode>
Enables test mode at the EUT automatically. The command is executable only for
BR/EDR connections via USB.
Parameters:
<EnableTestMode> OFF | ON
*RST: ON
Example: See Transmitter test mode
Firmware/Software: V3.5.71
Manual operation: See "Enable Test Mode (Classic)" on page 71
CONFigure:BLUetooth:SIGN<i>:LENergy:RESet:DELay <DelayAfterReset>
Specifies a delay after EUT reset.
Parameters:
<DelayAfterReset> numeric
Range: 0 s to 0.2 s
*RST: 0s
Example: See Configure USB Interface
Firmware/Software: V3.5.41
Options: R&S CMW-KS611
Manual operation: See "Delay After Reset (Low Energy)" on page 72
CONFigure:BLUetooth:SIGN<i>:COMSettings:PORTs:CATalog?
Queries the COM ports used by an EUT. The command is relevant for the USB con-
nection with USB-to-serial converter ("HW Interface" = USB to RS232 adapter).
Results are returned for each used USB port: <NoDevices>, {1, <Discovered-
Port>}1, ..., {<NoDevices>, <DiscoveredPort>}<NoDevices>
Return values:
<NoDevices> decimal
Number of all COM ports, where a connected EUT has been
recognized
<ItemNumber> decimal
The number of a list item
<DiscoveredPort> string
Number of the virtual COM port, to which the used USB port has
been mapped
Example: See Configure USB Interface
Usage: Query only
Firmware/Software: V3.2.70
Manual operation: See "Refresh COM Port List (hotkey)" on page 63
CONFigure:BLUetooth:SIGN<i>:COMSettings<no>:COMPort <No>
Specifies the virtual COM port to be used for USB connection with USB to RS232
adapter.
Suffix: .
<no> 1..2
1: HW interface for LE tests
2: HW interface for BR / EDR tests
Parameters:
<No> numeric
The number of a virtual COM port
*RST: 0
Example: See Configure USB Interface
Firmware/Software: V3.2.70
V3.5.30: added suffix <no>
Manual operation: See "USB to RS232" on page 72
CONFigure:BLUetooth:SIGN<i>:COMSettings<no>:BAUDrate <BaudRate>
Specifies the transmission parameters of serial connection.
Suffix: .
<no> 1..2
1: HW interface for LE tests
2: HW interface for BR / EDR tests
Parameters:
<BaudRate> B110 | B300 | B600 | B12K | B24K | B48K | B96K | B14K |
B19K | B28K | B38K | B57K | B115k | B234k | B460k | B500k |
B576k | B921k | B1M | B1M5 | B2M | B3M | B3M5 | B4M
Data transmission rate in symbol: 110, 300, 600, 1200, 2400,
4800, 9600, 14400, 19200, 28800, 38400, 57600, 115200,
230400, 460800, 500000, 576000, 921600, 1000000, 1152000,
2000000, 3000000, 3500000, 4000000
*RST: B96K
Example: See Configure USB Interface
Firmware/Software: V3.2.70
V3.5.30: added suffix <no>
3.5.71: added <BaudRate> B234k, B460, B500k, B576k,
B921k, B1M, B1M5, B2M, B3M, B3M5, B4M
Manual operation: See "USB to RS232" on page 72
CONFigure:BLUetooth:SIGN<i>:COMSettings<no>:PARity <Parity>
Specifies the transmission parameters of serial connection.
Suffix: .
<no> 1..2
1: HW interface for LE tests
2: HW interface for BR / EDR tests
Parameters:
<Parity> NONE | ODD | EVEN
Number of parity bits
*RST: NONE
Example: See Configure USB Interface
Firmware/Software: V3.2.70
V3.5.30: added suffix <no>
Manual operation: See "USB to RS232" on page 72
CONFigure:BLUetooth:SIGN<i>:COMSettings<no>:PROTocol <Protocol>
Specifies the transmission parameters of serial connection.
Suffix: .
<no> 1..2
1: HW interface for LE tests
2: HW interface for BR / EDR tests
Parameters:
<Protocol> XONXoff | CTSRts | NONE
Transmit flow control X-ON/X-OFF, RFR/CTS, or none
*RST: NONE
Example: See Configure USB Interface
Firmware/Software: V3.2.70
V3.5.30: added suffix <no>
Manual operation: See "USB to RS232" on page 72
CONFigure:BLUetooth:SIGN<i>:COMSettings<no>:STOPbits <StopBits>
Specifies the transmission parameters of serial connection.
Suffix: .
<no> 1..2
1: HW interface for LE tests
2: HW interface for BR / EDR tests
Parameters:
<StopBits> S1 | S2
Number of bits used for stop indication
*RST: S1
Example: See Configure USB Interface
Firmware/Software: V3.2.70
V3.5.30: added suffix <no>
Manual operation: See "USB to RS232" on page 72
CONFigure:BLUetooth:SIGN<i>:USBSettings:DEVices:CATalog?
Displays all EUTs discovered at USB interface. The command is relevant for the direct
USB connection ("HW Interface" = USB).
Results are returned for each connected EUT: <NoDevices>, {1, <Discovered-
Port>}1, ..., {<NoDevices>, <DiscoveredPort>}<NoDevices>
Return values:
<NoDevices> decimal
Number of all USB ports, where a connected EUT has been rec-
ognized
<ItemNumber> decimal
The number of a list item
<DiscoveredPort> string
Number of the USB port
Usage: Query only
Firmware/Software: V3.5.40
Manual operation: See "USB" on page 72
CONFigure:BLUetooth:SIGN<i>:USBSettings<no>:USBDevice <No>
Specifies the USB port to be used for direct USB connection. The command is relevant
for the direct USB connection ("HW Interface" = USB).
Suffix: .
<no> 1..2
1: HW interface for LE tests
2: HW interface for BR / EDR tests
Parameters:
<No> numeric
The number of a USB port
*RST: 0
Firmware/Software: V3.5.40
Manual operation: See "USB" on page 72
CALL:BLUetooth:SIGN<i>:HCICustom:SEND <CustomHCIByte>...
Sends specified bytes in hexadecimal format as an HCI command via USB interface.
You can send multiple bytes separated by comma.
Setting parameters:
<CustomHCIByte> hex
Comma-separated hexadecimal string
Range: #H0 to #HFF
*RST: #H0
Example: See Configure USB Interface
Usage: Event
Firmware/Software: V3.5.60
The following queries retrieve information about the EUT connected via direct USB as
shown in the "EUT Control" section of the main view.
SENSe:BLUetooth:SIGN<i>:USBDevice:INFormation:DCLass?..........................................203
SENSe:BLUetooth:SIGN<i>:USBDevice:INFormation:DPRotocol?......................................204
SENSe:BLUetooth:SIGN<i>:USBDevice:INFormation:DSUBclass?.....................................204
SENSe:BLUetooth:SIGN<i>:USBDevice:INFormation:IDPRoduct?......................................204
SENSe:BLUetooth:SIGN<i>:USBDevice:INFormation:IDVendor?........................................204
SENSe:BLUetooth:SIGN<i>:USBDevice:INFormation:MANufacturer?................................. 205
SENSe:BLUetooth:SIGN<i>:USBDevice:INFormation:PRODuct?........................................205
SENSe:BLUetooth:SIGN<i>:USBDevice:INFormation:SERial?........................................... 205
SENSe:BLUetooth:SIGN<i>:USBDevice:INFormation:DCLass?
Returns the device class of the active USB device.
Return values:
<Name> string
Example: See Query results
Usage: Query only
Firmware/Software: V3.5.30
SENSe:BLUetooth:SIGN<i>:USBDevice:INFormation:DPRotocol?
Returns the supported protocol of the active USB device.
Return values:
<Name> string
Example: See Query results
Usage: Query only
Firmware/Software: V3.5.30
Manual operation: See "USB Info" on page 50
SENSe:BLUetooth:SIGN<i>:USBDevice:INFormation:DSUBclass?
Returns the device subclass of the active USB device.
Return values:
<Name> string
Example: See Query results
Usage: Query only
Firmware/Software: V3.5.30
Manual operation: See "USB Info" on page 50
SENSe:BLUetooth:SIGN<i>:USBDevice:INFormation:IDPRoduct?
Returns the product ID of the active USB device.
Return values:
<Name> string
Example: See Query results
Usage: Query only
Firmware/Software: V3.5.30
Manual operation: See "USB Info" on page 50
SENSe:BLUetooth:SIGN<i>:USBDevice:INFormation:IDVendor?
Returns the vendor ID of the active USB device.
Return values:
<Name> string
Example: See Query results
Usage: Query only
Firmware/Software: V3.5.30
Manual operation: See "USB Info" on page 50
SENSe:BLUetooth:SIGN<i>:USBDevice:INFormation:MANufacturer?
Returns the name of the manufacturer of the active USB device.
Return values:
<Name> string
Example: See Query results
Usage: Query only
Firmware/Software: V3.5.30
Manual operation: See "USB Info" on page 50
SENSe:BLUetooth:SIGN<i>:USBDevice:INFormation:PRODuct?
Returns the product name of the active USB device.
Return values:
<Name> string
Example: See Query results
Usage: Query only
Firmware/Software: V3.5.30
Manual operation: See "USB Info" on page 50
SENSe:BLUetooth:SIGN<i>:USBDevice:INFormation:SERial?
Returns the name serial of the active USB device.
Return values:
<Name> string
Example: See Query results
Usage: Query only
Firmware/Software: V3.5.30
Manual operation: See "USB Info" on page 50
The following commands are only available as remote control. They have no corre-
sponding GUI parameters.
CONFigure:BLUetooth:SIGN<i>:DELay:PTIMeout <PollTimeout>
Sets delay for the processing of HCI commands. If set to 100 ms, maximally one HCI
command is processed every 100 ms.
Parameters:
<PollTimeout> integer
Range: 1 ms to 100 ms
*RST: 1 ms
Default unit: ms
Example: See Transmitter test mode
Firmware/Software: V3.5.50
Options: R&S CMW-KS610
CONFigure:BLUetooth:SIGN<i>:DELay:TMODe <ActTestDelay>
Specifies delay for test mode activation. The delay is applied after acknowledgment
from EUT that it has received activate test mode command.
Parameters:
<ActTestDelay> integer
Range: 1 ms to 100 ms
*RST: 1 ms
Default unit: ms
Example: See Configure Test Mode Classic
Firmware/Software: V3.5.50
Options: R&S CMW-KS610
CONFigure:BLUetooth:SIGN<i>:COMSettings<no>:STOPbits..................................................................... 201
CONFigure:BLUetooth:SIGN<i>:CONNection:ADDRess:CMW:LESignaling................................................180
CONFigure:BLUetooth:SIGN<i>:CONNection:ADDRess:EUT:LESignaling.................................................. 180
CONFigure:BLUetooth:SIGN<i>:CONNection:ADDRess:TYPE:LESignaling............................................... 180
CONFigure:BLUetooth:SIGN<i>:CONNection:AINTerval:LESignaling.......................................................... 181
CONFigure:BLUetooth:SIGN<i>:CONNection:AUDio:A2DP:ACCSlave....................................................... 194
CONFigure:BLUetooth:SIGN<i>:CONNection:AUDio:A2DP:ALCMethod..................................................... 194
CONFigure:BLUetooth:SIGN<i>:CONNection:AUDio:A2DP:BITRate?.........................................................194
CONFigure:BLUetooth:SIGN<i>:CONNection:AUDio:A2DP:BLKLength...................................................... 195
CONFigure:BLUetooth:SIGN<i>:CONNection:AUDio:A2DP:CHMode..........................................................195
CONFigure:BLUetooth:SIGN<i>:CONNection:AUDio:A2DP:CODec............................................................ 195
CONFigure:BLUetooth:SIGN<i>:CONNection:AUDio:A2DP:MAXBitpool..................................................... 196
CONFigure:BLUetooth:SIGN<i>:CONNection:AUDio:A2DP:MINBitpool...................................................... 196
CONFigure:BLUetooth:SIGN<i>:CONNection:AUDio:A2DP:SMPFrequency............................................... 196
CONFigure:BLUetooth:SIGN<i>:CONNection:AUDio:A2DP:SUBBands...................................................... 197
CONFigure:BLUetooth:SIGN<i>:CONNection:AUDio:CODec.......................................................................193
CONFigure:BLUetooth:SIGN<i>:CONNection:AUDio:HFP:CASTartup.........................................................192
CONFigure:BLUetooth:SIGN<i>:CONNection:AUDio:PINCode....................................................................192
CONFigure:BLUetooth:SIGN<i>:CONNection:AUDio:SECMode.................................................................. 192
CONFigure:BLUetooth:SIGN<i>:CONNection:AUDio:VOLControl:MICGain................................................ 193
CONFigure:BLUetooth:SIGN<i>:CONNection:AUDio:VOLControl:SPEaker................................................ 193
CONFigure:BLUetooth:SIGN<i>:CONNection:BDADdress:CMW................................................................. 176
CONFigure:BLUetooth:SIGN<i>:CONNection:BDADdress:EUT...................................................................176
CONFigure:BLUetooth:SIGN<i>:CONNection:BTYPe...................................................................................117
CONFigure:BLUetooth:SIGN<i>:CONNection:CMW:ROLE.......................................................................... 188
CONFigure:BLUetooth:SIGN<i>:CONNection:CMW:ROLE:LESignaling......................................................188
CONFigure:BLUetooth:SIGN<i>:CONNection:FEC:LENergy:LRANge......................................................... 117
CONFigure:BLUetooth:SIGN<i>:CONNection:FEC:NMODe:LENergy:LRANge........................................... 117
CONFigure:BLUetooth:SIGN<i>:CONNection:IENCryption:LESignaling:CCENtral...................................... 189
CONFigure:BLUetooth:SIGN<i>:CONNection:IENCryption:LESignaling:CPERipheral................................ 189
CONFigure:BLUetooth:SIGN<i>:CONNection:INQuiry:DURation:LESignaling.............................................181
CONFigure:BLUetooth:SIGN<i>:CONNection:INQuiry:ILENgth....................................................................177
CONFigure:BLUetooth:SIGN<i>:CONNection:INQuiry:NOResponses......................................................... 177
CONFigure:BLUetooth:SIGN<i>:CONNection:INQuiry:NOResponses:LESignaling..................................... 181
CONFigure:BLUetooth:SIGN<i>:CONNection:INQuiry:PTARgets:CATalog:LESignaling?............................182
CONFigure:BLUetooth:SIGN<i>:CONNection:INQuiry:PTARgets:CATalog?................................................ 178
CONFigure:BLUetooth:SIGN<i>:CONNection:INQuiry:SINTerval:LESignaling.............................................182
CONFigure:BLUetooth:SIGN<i>:CONNection:INQuiry:SWINdow:LESignaling............................................ 182
CONFigure:BLUetooth:SIGN<i>:CONNection:INTerval:LESignaling............................................................ 183
CONFigure:BLUetooth:SIGN<i>:CONNection:PACKets:PATTern:BRATe..................................................... 118
CONFigure:BLUetooth:SIGN<i>:CONNection:PACKets:PATTern:EDRate....................................................118
CONFigure:BLUetooth:SIGN<i>:CONNection:PACKets:PATTern:LENergy:LE2M........................................119
CONFigure:BLUetooth:SIGN<i>:CONNection:PACKets:PATTern:LENergy:LRANge....................................119
CONFigure:BLUetooth:SIGN<i>:CONNection:PACKets:PATTern:LENergy[:LE1M]......................................119
CONFigure:BLUetooth:SIGN<i>:CONNection:PACKets:PLENgth:BRATe.................................................... 120
CONFigure:BLUetooth:SIGN<i>:CONNection:PACKets:PLENgth:EDRate.................................................. 120
CONFigure:BLUetooth:SIGN<i>:CONNection:PACKets:PLENgth:LENergy:LE2M.......................................121
CONFigure:BLUetooth:SIGN<i>:CONNection:PACKets:PLENgth:LENergy:LRANge.................................. 121
CONFigure:BLUetooth:SIGN<i>:CONNection:PACKets:PLENgth:LENergy[:LE1M].....................................121
CONFigure:BLUetooth:SIGN<i>:CONNection:PACKets:PTYPe:BRATe....................................................... 121
CONFigure:BLUetooth:SIGN<i>:CONNection:PACKets:PTYPe:EDRate..................................................... 122
CONFigure:BLUetooth:SIGN<i>:CONNection:PACKets:PTYPe:ESCO........................................................123
CONFigure:BLUetooth:SIGN<i>:CONNection:PACKets:PTYPe:LENergy:LE2M..........................................123
CONFigure:BLUetooth:SIGN<i>:CONNection:PACKets:PTYPe:LENergy[:LE1M]........................................123
CONFigure:BLUetooth:SIGN<i>:CONNection:PACKets:PTYPe:SCO.......................................................... 123
CONFigure:BLUetooth:SIGN<i>:CONNection:PACKets:TYPE:CTE:LENergy:LE1M................................... 123
CONFigure:BLUetooth:SIGN<i>:CONNection:PACKets:TYPE:CTE:LENergy:LE2M................................... 123
CONFigure:BLUetooth:SIGN<i>:CONNection:PACKets:UNITs:CTE:LENergy:LE1M................................... 124
CONFigure:BLUetooth:SIGN<i>:CONNection:PACKets:UNITs:CTE:LENergy:LE2M................................... 124
CONFigure:BLUetooth:SIGN<i>:CONNection:PAGing:PSRMode................................................................ 178
CONFigure:BLUetooth:SIGN<i>:CONNection:PAGing:PTARget.................................................................. 179
CONFigure:BLUetooth:SIGN<i>:CONNection:PAGing:PTARget:LESignaling.............................................. 183
CONFigure:BLUetooth:SIGN<i>:CONNection:PAGing:TOUT.......................................................................177
CONFigure:BLUetooth:SIGN<i>:CONNection:PAGing:TOUT:LESignaling................................................... 184
CONFigure:BLUetooth:SIGN<i>:CONNection:PCONtrol:EPCMode............................................................. 161
CONFigure:BLUetooth:SIGN<i>:CONNection:PCONtrol:PCMode:LESignaling........................................... 174
CONFigure:BLUetooth:SIGN<i>:CONNection:PCONtrol:SSIZe:LESignaling............................................... 174
CONFigure:BLUetooth:SIGN<i>:CONNection:PCONtrol:STEP:ACTion....................................................... 161
CONFigure:BLUetooth:SIGN<i>:CONNection:PCONtrol:STEP:ACTion:LESignaling...................................175
CONFigure:BLUetooth:SIGN<i>:CONNection:PHY:LENergy........................................................................118
CONFigure:BLUetooth:SIGN<i>:CONNection:PHY:NMODe:LENergy..........................................................118
CONFigure:BLUetooth:SIGN<i>:CONNection:PPERiod............................................................................... 190
CONFigure:BLUetooth:SIGN<i>:CONNection:PPERiod:MINimum...............................................................190
CONFigure:BLUetooth:SIGN<i>:CONNection:RADDress:CMW:LESignaling?.............................................184
CONFigure:BLUetooth:SIGN<i>:CONNection:RENCryption:LESignaling:CCENtral.................................... 189
CONFigure:BLUetooth:SIGN<i>:CONNection:RENCryption:LESignaling:CPERipheral...............................189
CONFigure:BLUetooth:SIGN<i>:CONNection:SINTerval:LESignaling.......................................................... 184
CONFigure:BLUetooth:SIGN<i>:CONNection:SLATency:LESignaling:CPERipheral....................................185
CONFigure:BLUetooth:SIGN<i>:CONNection:SLATency:LESignaling[:CCENtral]....................................... 185
CONFigure:BLUetooth:SIGN<i>:CONNection:SVTimeout............................................................................ 176
CONFigure:BLUetooth:SIGN<i>:CONNection:SVTimeout:LESignaling........................................................185
CONFigure:BLUetooth:SIGN<i>:CONNection:SWINdow:LESignaling..........................................................185
CONFigure:BLUetooth:SIGN<i>:CONNection:SYNWord:LENergy...............................................................191
CONFigure:BLUetooth:SIGN<i>:CONNection:WFCMap:LESignaling:CCENtral.......................................... 186
CONFigure:BLUetooth:SIGN<i>:CONNection:WHITening............................................................................ 191
CONFigure:BLUetooth:SIGN<i>:CPRotocol..................................................................................................202
CONFigure:BLUetooth:SIGN<i>:DELay:PTIMeout........................................................................................206
CONFigure:BLUetooth:SIGN<i>:DELay:TMODe...........................................................................................206
CONFigure:BLUetooth:SIGN<i>:HWINterface<no>...................................................................................... 198
CONFigure:BLUetooth:SIGN<i>:LENergy:RESet:DELay..............................................................................199
CONFigure:BLUetooth:SIGN<i>:OPMode.....................................................................................................189
CONFigure:BLUetooth:SIGN<i>:RFSettings:AFHopping.............................................................................. 132
CONFigure:BLUetooth:SIGN<i>:RFSettings:AFHopping:UCHannels...........................................................133
CONFigure:BLUetooth:SIGN<i>:RFSettings:AOFFset:INPut:CTE:LENergy.................................................125
CONFigure:BLUetooth:SIGN<i>:RFSettings:AOFFset:OUTPut:CTE:LENergy.............................................125
CONFigure:BLUetooth:SIGN<i>:RFSettings:ARANging............................................................................... 133
CONFigure:BLUetooth:SIGN<i>:RFSettings:CHANnel:DTMode.................................................................. 127
CONFigure:BLUetooth:SIGN<i>:RFSettings:CHANnel:LOOPback...............................................................128
CONFigure:BLUetooth:SIGN<i>:RFSettings:CHANnel:TMODe....................................................................128
CONFigure:BLUetooth:SIGN<i>:RFSettings:CHANnel:TXTest..................................................................... 128
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX......................................................................................... 138
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:MODE:BRATe................................................................. 138
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:MODE:EDRate................................................................138
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:MODE:LENergy:LE2M....................................................139
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:MODE:LENergy:LRANge................................................139
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:MODE:LENergy[:LE1M]..................................................139
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:MODE:NMODe:LENergy:LE1M......................................138
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:MODE:NMODe:LENergy:LE2M......................................138
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:MODE:NMODe:LENergy:LRANge..................................138
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:MODE:TMODe:LENergy:LE1M...................................... 139
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:MODE:TMODe:LENergy:LE2M...................................... 139
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:MODE:TMODe:LENergy:LRANge.................................. 138
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:MODFrequency:LENergy:LE2M..................................... 140
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:MODFrequency:LENergy:LRANge................................. 140
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:MODFrequency:LENergy[:LE1M]................................... 140
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:MODFrequency:NMODe:LENergy:LE1M....................... 140
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:MODFrequency:NMODe:LENergy:LE2M....................... 140
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:MODFrequency:NMODe:LENergy:LRANge................... 140
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:MODFrequency:TMODe:LENergy:LE1M........................140
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:MODFrequency:TMODe:LENergy:LE2M........................140
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:MODFrequency:TMODe:LENergy:LRANge................... 140
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:FDRift:BRATe........................................................ 140
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:FDRift:EDRate...................................................... 140
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:FDRift:LENergy:LE2M...........................................141
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:FDRift:LENergy:LRANge...................................... 141
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:FDRift:LENergy[:LE1M].........................................141
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:FDRift:NMODe:LENergy:LE1M.............................141
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:FDRift:NMODe:LENergy:LE2M.............................141
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:FDRift:NMODe:LENergy:LRANge........................ 141
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:FDRift:TMODe:LENergy:LE1M............................. 141
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:FDRift:TMODe:LENergy:LE2M............................. 141
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:FDRift:TMODe:LENergy:LRANge.........................141
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:FOFFset:BRATe.................................................... 142
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:FOFFset:EDRate.................................................. 142
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:FOFFset:LENergy:LE2M.......................................142
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:FOFFset:LENergy:LRANge.................................. 142
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:FOFFset:LENergy[:LE1M].....................................142
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:FOFFset:NMODe:LENergy:LE1M.........................142
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:FOFFset:NMODe:LENergy:LE2M.........................142
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:FOFFset:NMODe:LENergy:LRANge.................... 142
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:FOFFset:TMODe:LENergy:LE1M......................... 142
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:FOFFset:TMODe:LENergy:LE2M......................... 142
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:FOFFset:TMODe:LENergy:LRANge.....................142
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:MINDex:BRATe..................................................... 143
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:MINDex:NMODe:LENergy:LE1M..........................143
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:MINDex:NMODe:LENergy:LE2M..........................143
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:MINDex:NMODe:LENergy:LRANge......................143
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:MINDex:STABle:LENergy:LE2M...........................145
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:MINDex:STABle:LENergy:LRANge.......................144
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:MINDex:STABle:LENergy[:LE1M].........................145
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:MINDex:STABle:TMODe:LENergy:LE1M............. 144
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:MINDex:STABle:TMODe:LENergy:LE2M............. 144
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:MINDex:STABle:TMODe:LENergy:LRANge......... 144
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:MINDex:STANdard:LENergy:LE2M...................... 144
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:MINDex:STANdard:LENergy:LRANge.................. 143
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:MINDex:STANdard:LENergy[:LE1M].................... 144
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:MINDex:STANdard:TMODe:LENergy:LE1M.........143
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:MINDex:STANdard:TMODe:LENergy:LE2M.........143
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:MINDex:STANdard:TMODe:LENergy:LRANge.... 143
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:STERror:BRATe.................................................... 145
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:STERror:EDRate...................................................145
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:STERror:LENergy:LE2M.......................................146
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:STERror:LENergy:LRANge...................................146
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:STERror:LENergy[:LE1M].....................................146
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:STERror:NMODe:LENergy:LE1M.........................146
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:STERror:NMODe:LENergy:LE2M.........................146
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:STERror:NMODe:LENergy:LRANge.....................146
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:STERror:TMODe:LENergy:LE1M......................... 146
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:STERror:TMODe:LENergy:LE2M......................... 146
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:SING:STERror:TMODe:LENergy:LRANge..................... 146
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:FDRift:BRATe?......................................................147
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:FDRift:EDRate?.................................................... 147
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:FDRift:LENergy:LE2M?........................................ 147
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:FDRift:LENergy:LRANge?.................................... 147
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:FDRift:LENergy[:LE1M]?...................................... 147
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:FDRift:NMODe:LENergy:LE1M?.......................... 147
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:FDRift:NMODe:LENergy:LE2M?.......................... 147
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:FDRift:NMODe:LENergy:LRANge?...................... 147
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:FDRift:TMODe:LENergy:LE1M?...........................147
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:FDRift:TMODe:LENergy:LE2M?...........................147
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:FDRift:TMODe:LENergy:LRANge?...................... 147
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:FOFFset:BRATe?..................................................148
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:FOFFset:EDRate?................................................ 148
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:FOFFset:LENergy:LE2M?.................................... 148
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:FOFFset:LENergy:LRANge?................................ 148
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:FOFFset:LENergy[:LE1M]?.................................. 148
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:FOFFset:NMODe:LENergy:LE1M?...................... 148
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:FOFFset:NMODe:LENergy:LE2M?...................... 148
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:FOFFset:NMODe:LENergy:LRANge?.................. 148
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:FOFFset:TMODe:LENergy:LE1M?.......................148
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:FOFFset:TMODe:LENergy:LE2M?.......................148
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:FOFFset:TMODe:LENergy:LRANge?.................. 148
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:MINDex:BRATe?...................................................149
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:MINDex:NMODe:LENergy:LE1M?....................... 149
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:MINDex:NMODe:LENergy:LE2M?....................... 149
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:MINDex:NMODe:LENergy:LRANge?................... 149
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:MINDex:STABle:LENergy:LE2M?........................ 150
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:MINDex:STABle:LENergy:LRANge?.................... 150
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:MINDex:STABle:LENergy[:LE1M]?...................... 150
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:MINDex:STABle:TMODe:LENergy:LE1M?...........150
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:MINDex:STABle:TMODe:LENergy:LE2M?...........150
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:MINDex:STABle:TMODe:LENergy:LRANge?.......150
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:MINDex:STANdard:LENergy:LE2M?....................149
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:MINDex:STANdard:LENergy:LRANge?................149
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:MINDex:STANdard:LENergy[:LE1M]?..................149
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:MINDex:STANdard:TMODe:LENergy:LE1M?...... 149
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:MINDex:STANdard:TMODe:LENergy:LE2M?...... 149
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:MINDex:STANdard:TMODe:LENergy:LRANge?.. 149
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:STERror:BRATe?..................................................151
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:STERror:EDRate?................................................ 151
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:STERror:LENergy:LE2M?.................................... 151
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:STERror:LENergy:LRANge?................................ 151
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:STERror:LENergy[:LE1M]?.................................. 151
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:STERror:NMODe:LENergy:LE1M?...................... 151
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:STERror:NMODe:LENergy:LE2M?...................... 151
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:STERror:NMODe:LENergy:LRANge?.................. 151
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:STERror:TMODe:LENergy:LE1M?.......................151
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:STERror:TMODe:LENergy:LE2M?.......................151
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:STERror:TMODe:LENergy:LRANge?...................151
CONFigure:BLUetooth:SIGN<i>:RFSettings:EATTenuation:INPut................................................................124
CONFigure:BLUetooth:SIGN<i>:RFSettings:EATTenuation:OUTPut............................................................125
CONFigure:BLUetooth:SIGN<i>:RFSettings:ENPower................................................................................. 134
CONFigure:BLUetooth:SIGN<i>:RFSettings:FREQuency:DTMode?............................................................129
CONFigure:BLUetooth:SIGN<i>:RFSettings:FREQuency:LOOPback?........................................................ 129
CONFigure:BLUetooth:SIGN<i>:RFSettings:FREQuency:TMODe?............................................................. 129
CONFigure:BLUetooth:SIGN<i>:RFSettings:FREQuency:TXTest?.............................................................. 130
CONFigure:BLUetooth:SIGN<i>:RFSettings:GOFFset:CTE:LENergy:LE1M................................................126
CONFigure:BLUetooth:SIGN<i>:RFSettings:GOFFset:CTE:LENergy:LE2M................................................126
CONFigure:BLUetooth:SIGN<i>:RFSettings:HOPPing................................................................................. 130
CONFigure:BLUetooth:SIGN<i>:RFSettings:LEVel.......................................................................................134
CONFigure:BLUetooth:SIGN<i>:RFSettings:NANTenna:CTE:LENergy........................................................191
CONFigure:BLUetooth:SIGN<i>:RFSettings:NMODe:HMODe:LENergy...................................................... 131
CONFigure:BLUetooth:SIGN<i>:RFSettings:NMODe:MCHannel:LENergy.................................................. 131
CONFigure:BLUetooth:SIGN<i>:RFSettings:UMARgin.................................................................................135
CONFigure:BLUetooth:SIGN<i>:STANdard...................................................................................................118
CONFigure:BLUetooth:SIGN<i>:TCONnection:FEC:LENergy:LRANge........................................................117
CONFigure:BLUetooth:SIGN<i>:TCONnection:INTerval:LESignaling...........................................................186
CONFigure:BLUetooth:SIGN<i>:TCONnection:PACKets:PATTern:LENergy:LE1M...................................... 118
CONFigure:BLUetooth:SIGN<i>:TCONnection:PACKets:PATTern:LENergy:LE2M...................................... 118
CONFigure:BLUetooth:SIGN<i>:TCONnection:PACKets:PATTern:LENergy:LRANge.................................. 118
CONFigure:BLUetooth:SIGN<i>:TCONnection:PACKets:PLENgth:LENergy:LE1M..................................... 121
CONFigure:BLUetooth:SIGN<i>:TCONnection:PACKets:PLENgth:LENergy:LE2M..................................... 121
CONFigure:BLUetooth:SIGN<i>:TCONnection:PACKets:PLENgth:LENergy:LRANge.................................121
CONFigure:BLUetooth:SIGN<i>:TCONnection:PHY:LENergy...................................................................... 118
CONFigure:BLUetooth:SIGN<i>:TCONnection:PINCode:LENergy...............................................................186
CONFigure:BLUetooth:SIGN<i>:TCONnection:SPINenable:LENergy.......................................................... 187
CONFigure:BLUetooth:SIGN<i>:TMODe...................................................................................................... 131
CONFigure:BLUetooth:SIGN<i>:TMODe:LENergy....................................................................................... 187
CONFigure:BLUetooth:SIGN<i>:USBSettings:DEVices:CATalog?............................................................... 202
CONFigure:BLUetooth:SIGN<i>:USBSettings<no>:USBDevice................................................................... 202
FETCh:BLUetooth:SIGN<i>:CONNection:STATe:ALL?.................................................................................155
FETCh:BLUetooth:SIGN<i>:CONNection:STATe:LESignaling?.................................................................... 157
FETCh:BLUetooth:SIGN<i>:CONNection:STATe?........................................................................................ 153
FETCh:BLUetooth:SIGN<i>:LENergy:STATe?.............................................................................................. 157
ROUTe:BLUetooth:SIGN<i>:SCENario:OTRX.............................................................................................. 126
ROUTe:BLUetooth:SIGN<i>:SCENario:OTRX:FLEXible...............................................................................127
SENSe:BLUetooth:SIGN<i>:CMAP?.............................................................................................................133
SENSe:BLUetooth:SIGN<i>:CONNection:AUDio:LINFo?............................................................................. 163
SENSe:BLUetooth:SIGN<i>:ELOGging:ALL?............................................................................................... 164
SENSe:BLUetooth:SIGN<i>:ELOGging:LAST?.............................................................................................165
SENSe:BLUetooth:SIGN<i>:EUT:CAPability:ACL?....................................................................................... 170
SENSe:BLUetooth:SIGN<i>:EUT:CAPability:CONNection?..........................................................................168
SENSe:BLUetooth:SIGN<i>:EUT:CAPability:ENCRyption?.......................................................................... 169
SENSe:BLUetooth:SIGN<i>:EUT:CAPability:EPControl?..............................................................................170
SENSe:BLUetooth:SIGN<i>:EUT:CAPability:ESCO?....................................................................................171
SENSe:BLUetooth:SIGN<i>:EUT:CAPability:LESignaling?...........................................................................172
SENSe:BLUetooth:SIGN<i>:EUT:CAPability:PCONtrol?...............................................................................170
SENSe:BLUetooth:SIGN<i>:EUT:CAPability:PSAVing?................................................................................169
SENSe:BLUetooth:SIGN<i>:EUT:CAPability:SCLass?................................................................................. 172
SENSe:BLUetooth:SIGN<i>:EUT:CAPability:SCO?...................................................................................... 171
SENSe:BLUetooth:SIGN<i>:EUT:CSETtings:LESignaling?.......................................................................... 165
SENSe:BLUetooth:SIGN<i>:EUT:INFormation:BDADdress?........................................................................ 166
SENSe:BLUetooth:SIGN<i>:EUT:INFormation:CLASs?................................................................................166
SENSe:BLUetooth:SIGN<i>:EUT:INFormation:COMPany?.......................................................................... 166
SENSe:BLUetooth:SIGN<i>:EUT:INFormation:LESignaling?........................................................................167
SENSe:BLUetooth:SIGN<i>:EUT:INFormation:NAME?................................................................................ 167
SENSe:BLUetooth:SIGN<i>:EUT:INFormation:VERSion?............................................................................ 167
SENSe:BLUetooth:SIGN<i>:EUT:PCONtrol:STATe:DPSK?.......................................................................... 163
SENSe:BLUetooth:SIGN<i>:EUT:PCONtrol:STATe:DQPSk?........................................................................163
SENSe:BLUetooth:SIGN<i>:EUT:PCONtrol:STATe:GFSK?.......................................................................... 163
SENSe:BLUetooth:SIGN<i>:EUT:PCONtrol:STATe:LEGacy?....................................................................... 161
SENSe:BLUetooth:SIGN<i>:EUT:PCONtrol:STATe:LESignaling?.................................................................175
SENSe:BLUetooth:SIGN<i>:EUT:PCONtrol:STATe?.....................................................................................162
SENSe:BLUetooth:SIGN<i>:USBDevice:INFormation:DCLass?.................................................................. 203
SENSe:BLUetooth:SIGN<i>:USBDevice:INFormation:DPRotocol?.............................................................. 204
SENSe:BLUetooth:SIGN<i>:USBDevice:INFormation:DSUBclass?............................................................. 204
SENSe:BLUetooth:SIGN<i>:USBDevice:INFormation:IDPRoduct?..............................................................204
SENSe:BLUetooth:SIGN<i>:USBDevice:INFormation:IDVendor?................................................................ 204
SENSe:BLUetooth:SIGN<i>:USBDevice:INFormation:MANufacturer?......................................................... 205
SENSe:BLUetooth:SIGN<i>:USBDevice:INFormation:PRODuct?................................................................ 205
SENSe:BLUetooth:SIGN<i>:USBDevice:INFormation:SERial?.................................................................... 205
SOURce:BLUetooth:SIGN<i>:STATe.............................................................................................................153
3 Rx BER Measurement
The BER measurement is installed together with the Bluetooth signaling application. To
access the measurement, press the softkey "Bluetooth RX Meas." in the Bluetooth sig-
naling main view. Then select the tab "BER". The BER measurement is supported for
burst type "Basic Rate" or enhanced data rate ("EDR") in test mode.
For the calculation of BER results, the R&S CMW compares its transmitted packets
with the received packets to derive the measurement results.
The measurement is especially suitable to assess the characteristics and the perfor-
mance of the EUT receiver at low RF power levels. The transmission errors of the
higher signal level, produced on the way back (from the EUT to the instrument) can
usually be neglected.
Option R&S CMW-KS610 is required for BR and EDR.
1. Configure a test connection with loopback test. Refer to "Loopback Test Mode (BR/
EDR)" on page 21.
3. Configure any other required settings as for a connection without the "BER" mea-
surement (frequency, power, packet type, payload length, pattern, dirty Tx).
Acquisition Error
If the EUT does not close the loop and sends other data instead of looping back the
received data, then it results in an acquisition error (reliability indicator value 7). For the
BER measurement, an acquisition error indicates that the UL signal was decoded suc-
cessfully, but the expected bit pattern was not found.
The BER tab provides the BER loopback tests in test mode for BR and EDR.
The most important settings of the "Bluetooth Signaling" application can be accessed
via the "Signaling Parameter" softkey and the related hotkeys.
To switch to the signaling application, press the "Bluetooth Signaling" softkey two
times.
The "Config" hotkey opens either the configuration dialog of the measurement or the
configuration dialog of the signaling application, depending on which softkey is active.
The BER tab shows the measurement results to the left, settings to the right and the
connection status at the bottom.
Results
The results are displayed to the left. For the description, refer to Chapter 3.2.3, "Mea-
surement Results", on page 216.
Common Settings
The settings to the right are the same as in the configuration dialog.
● General setup: see Chapter 2.3.6, "General Settings", on page 66
● RF setup:
– For RF frequency settings, see Chapter 2.3.8.2, "RF Frequency", on page 74
– For other RF power settings, see Chapter 2.3.8.3, "RF Power Settings",
on page 77
– For the description of dirty transmitter, see Chapter 2.3.8.4, "Dirty Transmitter
Configuration", on page 78
● Signal characteristics: see Chapter 2.3.1.11, "Signal Characteristics", on page 53
Connection Status
The connection status information at the bottom of the BER tab shows the signal and
connection status and the EUT for paging. For background information, see Chap-
ter 2.2.11, "Signaling States", on page 36.
For BR/EDR tests, this information is the same as in the main view, see Chap-
ter 2.3.1.1, "Connection Status Tab - Connection Status", on page 42.
To turn the measurement on or off, select the control softkey and press [ON | OFF] or
[RESTART | STOP]. Alternatively, right-click the control softkey.
BER (Softkey)
The softkey shows the current measurement state. Additional measurement substates
can be retrieved via remote control.
Remote command:
INITiate:BLUetooth:SIGN<i>:RXQuality:BER[:BEDR]
STOP:BLUetooth:SIGN<i>:RXQuality:BER[:BEDR]
ABORt:BLUetooth:SIGN<i>:RXQuality:BER[:BEDR]
FETCh:BLUetooth:SIGN<i>:RXQuality:BER:STATe:ALL[:BEDR]?
FETCh:BLUetooth:SIGN<i>:RXQuality:BER:STATe[:BEDR]?
Access: Bluetooth signaling main view > "Bluetooth Rx Meas" softkey > "BER" tab.
The BER tab shows the measurement results to the left, settings to the right and the
connection status at the bottom.
Results
The following results apply to BR/EDR BER measurements.
● "BER": bit error rate, percentage of received erroneous data bits.
● "Bit Errors": sum of received erroneous data bits.
● "NAK Rate": percentage of packets transmitted by the R&S CMW, which were not
acknowledged by the EUT positively.
● "PER": packet error rate, percentage of bad packets received. This value is equal
to the sum of the percentages of the individual packet error types.
● "Missing Packets Rate": Difference between the number of packets sent and the
number of packets received from the EUT as percentage.
● "HEC Error Rate": header error check, percentage of received packets with the bit
errors in the header.
● "CRC Error Rate": cyclic redundancy check, percentage of received packets with
the bit errors in the payload.
● "Wrong Packet Type": percentage of received packets of a different type to that
originally transmitted ones by the R&S CMW, including poll and null packets.
● "Wrong Payload Length": percentage of received packets containing the different
payload length to that originally transmitted ones by the R&S CMW.
● "Packets Received": number of test packets with the correct CRC and the correct
packet header received by the EUT, i.e. packets that are not considered for the
BER measurement. Received bad packets (packets, that the EUT is unable to
send back and the ones that are sent back in error) do not affect this packet coun-
ter.
After the start of a single shot measurement, this value indicates the number of
received packets and the total number of packets to be measured per single shot.
Two equal numbers indicate that the first shot is complete and the statistical depth
has been reached.
A measurement in continuous mode still continues and calculates results from the
previous statistical cycle (e.g. the previous 100 packets).
Access: Bluetooth signaling main view > "Bluetooth Rx Meas" softkey > "Config" hot-
key.
The "Measurement Control" parameters configure the scope of the measurement. The
following chapter describes only the settings relevant for BER measurements.
Common Settings........................................................................................................218
Repetition.................................................................................................................... 219
Packets....................................................................................................................... 219
Limits...........................................................................................................................219
Connection.................................................................................................................. 219
Suppress "Sig Off" Message....................................................................................... 219
Related Dirty Tx Hotkeys............................................................................................ 220
Common Settings
The following settings are the same as in the configuration dialog.
● General setup: see Chapter 2.3.6, "General Settings", on page 66
● RF settings:
Repetition
Defines how often the measurement is repeated if it is not stopped explicitly or by a
failed limit check.
● Continuous: The measurement is continued until it is explicitly terminated. The
results are periodically updated.
● Single-Shot: The measurement is stopped after one measurement cycle.
Single-shot is preferable if only a single measurement result is required under fixed
conditions, which is typical for remote-controlled measurements. The continuous mode
is suitable to monitor the evolution of the measurement results and to observe how
they depend on the measurement configuration, which is typically done in manual con-
trol.
Remote command:
CONFigure:BLUetooth:SIGN<i>:RXQuality:REPetition
Packets
Defines the number of data packets to be measured per measurement cycle (statistics
cycle). The number of packets sent can be larger than the specified value because of
possible packet lost on the way to the EUT and back.
The number of payload bits is displayed for information.
Remote command:
CONFigure:BLUetooth:SIGN<i>:RXQuality:PACKets[:BEDR]
Limits
Defines and activates/deactivates the upper limit for the results of BER measurements.
Remote command:
CONFigure:BLUetooth:SIGN<i>:RXQuality:LIMit:MBER:BRATe
CONFigure:BLUetooth:SIGN<i>:RXQuality:LIMit:MBER:EDRate
Connection
The connection settings are the same as in the configuration dialog, see Chapter 2.3.9,
"Connection Configuration", on page 85.
Hotkey Description
For a description, refer to Chapter 2.3.8.4, "Dirty Transmitter Configuration", on page 78.
Remote command:
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:MINDex:BRATe? etc.
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:FOFFset:BRATe?
etc.
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:STERror:BRATe?
etc.
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:FDRift:BRATe? etc.
3.3 Programming
The BER measurements provided by the "Bluetooth Signaling" application are pro-
grammed as follows:
● The application is controlled by SCPI commands with the following syn-
tax: ...:BLUetooth:SIGN:RXQuality:...
● After a *RST, the measurement is switched off. Use
READ:BLUetooth:SIGN:RXQuality:BER? to initiate a single-shot measure-
ment and retrieve the results. You can also start the measurement using
INIT:BLUetooth:SIGN:RXQuality:BER and retrieve the results using
FETCh:BLUetooth:SIGN:RXQuality:BER?.
The examples in this section focus on commands directly related to the BER measure-
ments. For general configuration of the signaling application, refer to Chapter 2.4, "Pro-
gramming", on page 99.
*CLS; *OPC?
// *****************************************************************************
// Configure a BR/EDR BER measurement: number of transport
// blocks to be measured and limits
// *****************************************************************************
CONFigure:BLUetooth:SIGN:RXQuality:PACKets:BEDR 10000; *OPC?
CONFigure:BLUetooth:SIGN:RXQuality:LIMit:MBER:BRATe 100; *OPC?
CONFigure:BLUetooth:SIGN:RXQuality:LIMit:MBER:EDRate 100; *OPC?
To configure and set up the connection in test mode, see Configure Test Mode Classic.
// *****************************************************************************
// Start continuous measurement; wait for 5 ms and return BER results.
// Query measurement state and substates (should be "RUN,ADJ,ACT").
// *****************************************************************************
CONFigure:BLUetooth:SIGN:RXQuality:REPetition CONT; *OPC?
INIT:BLUetooth:SIGN:RXQuality:BER
Pause 5000
FETCh:BLUetooth:SIGN:RXQuality:BER?
CALCulate:BLUetooth:SIGN:RXQuality:BER?
FETCh:BLUetooth:SIGN:RXQuality:BER:STATe:ALL?
The following sections describe the most important conventions and general informa-
tion concerning the command reference.
3.4.1.1 SIGN<i>
3.4.1.3 Keywords
Selected keywords used in the command description are described in the following.
● Command usage
If the usage is not explicitly stated, the command allows you to set parameters and
query parameters. Otherwise, the command usage is stated as follows:
– "Setting only": The command can only be used to set parameters.
– "Query only": The command can only be used to query parameters.
– "Event": The command initiates an event.
● Parameter usage
The parameter usage is indicated by the keyword preceding the parameters:
– "Parameters" are sent with a setting or query command and are returned as
the result of a query.
– "Setting parameters" are sent with a setting command.
– "Query parameters" are sent with a query command, to refine the query.
– "Return values" are returned as the result of a query.
● Firmware/Software:
Indicates the lowest software version supporting the command. Command
enhancements in later software versions are also indicated.
The first value in the output arrays of FETCh...?, READ...? and CALCulate...?
queries indicates the most severe error that has occurred during the measurement.
Example for an output array: 0, 10.22, 10.15, 10.01, 10.29, 100 (reliability = 0, followed
by 5 numeric measurement values).
The reliability indicator has one of the following values:
● 0 ("No Error"):
Measurement values available, no error detected.
● 1 ("Measurement Timeout"):
The measurement has been stopped after the configured measurement timeout.
Measurement results can be available. However, at least a part of the measure-
ment provides only INValid results or has not completed the full statistic count.
● 2 ("Capture Buffer Overflow"):
The measurement configuration results in a capture length that exceeds the availa-
ble memory.
● 3 ("Input Overdriven") / 4 ("Input Underdriven"):
The accuracy of measurement results can be impaired because the input signal
level was too high / too low.
● 6 ("Trigger Timeout"):
The measurement could not be started or continued because no trigger event was
detected.
● 7 ("Acquisition Error"):
The R&S CMW could not properly decode the RF input signal.
● 8 ("Sync Error"):
The R&S CMW could not synchronize to the RF input signal.
● 9 ("Uncal"):
Due to an inappropriate configuration of resolution bandwidth, video bandwidth or
sweep time, the measurement results are not within the specified data sheet limits.
● 15 ("Reference Frequency Error"):
The instrument has been configured to use an external reference signal. But the
reference oscillator could not be phase-locked to the external signal (for example
signal level too low, frequency out of range or reference signal not available at all).
● 16 ("RF Not Available"):
The measurement could not be started because the configured RF input path was
not active.
This problem can occur if a measurement is started in combined signal path mode
and the master application has not yet activated the input path.
● 17 ("RF Level Not Settled") / 18 ("RF Frequency Not Settled"):
The measurement could not be started because the R&S CMW was not yet ready
to deliver stable results after a change of the input signal power / the input signal
frequency.
● 19 ("Call Not Established"):
For measurements: The measurement could not be started because no signaling
connection to the DUT was established.
● 20 ("Call Type Not Usable"):
For measurements: The measurement could not be started because the estab-
lished signaling connection had wrong properties.
● 21 ("Call Lost"):
For measurements: The measurement was interrupted because the signaling con-
nection to the DUT was lost.
● 23 ("Missing Option"):
An action cannot be executed due to a missing option.
For GPRF generator: The ARB file cannot be played due to a missing option.
● 24 ("Invalid RF Setting"):
The desired RF TX level or RF RX reference level could not be applied.
● 25 ("Level Overrange"):
The RF TX level is in overrange. The signal quality can be degraded.
● 26 ("Resource Conflict"):
The application could not be started or has been stopped due to a conflicting hard-
ware resource or software option that is allocated by another application.
Stop the application that has allocated the conflicting resources and try again.
● 28 ("Unexpected Parameter Change"):
One or more measurement configuration parameters were changed while the mea-
surement completed. The results were not obtained with these new parameter val-
ues. Repeat the measurement. This situation can only occur in remote single-shot
mode.
● 29 ("Invalid RF Frequency Setting"):
The desired RF TX frequency or RF RX frequency could not be applied.
● 30 ("File Not Found"):
The specified file could not be found.
● 31 ("No DTM Reply"):
The EUT did not reply to the direct test mode (DTM) command.
● 32 ("ACL Disconnected"):
The ACL connection has been disconnected or lost.
● 40 ("ARB File CRC Error"):
The cyclic redundancy check of the ARB file failed. The ARB file is corrupt and not
reliable.
● 42 ("ARB Header Tag Invalid"):
The ARB file selected in the GPRF generator contains an invalid header tag.
● 43 ("ARB Segment Overflow"):
The number of segments in the multi-segment ARB file is higher than the allowed
maximum.
● 44 ("ARB File Not Found"):
The selected ARB file could not be found.
The following commands control the measurement and return the current measure-
ment state.
INITiate:BLUetooth:SIGN<i>:RXQuality:BER[:BEDR].........................................................226
STOP:BLUetooth:SIGN<i>:RXQuality:BER[:BEDR]........................................................... 226
ABORt:BLUetooth:SIGN<i>:RXQuality:BER[:BEDR].......................................................... 226
FETCh:BLUetooth:SIGN<i>:RXQuality:BER:STATe:ALL[:BEDR]?....................................... 227
FETCh:BLUetooth:SIGN<i>:RXQuality:BER:STATe[:BEDR]?..............................................228
INITiate:BLUetooth:SIGN<i>:RXQuality:BER[:BEDR]
STOP:BLUetooth:SIGN<i>:RXQuality:BER[:BEDR]
ABORt:BLUetooth:SIGN<i>:RXQuality:BER[:BEDR]
Starts, stops, or aborts the measurement:
● INITiate... starts or restarts the measurement. The measurement enters the
"RUN" state.
● STOP... halts the measurement immediately. The measurement enters the "RDY"
state. Measurement results are kept. The resources remain allocated to the mea-
surement.
FETCh:BLUetooth:SIGN<i>:RXQuality:BER:STATe:ALL[:BEDR]?
Queries the main measurement state and the measurement substates. Both measure-
ment substates are relevant for running measurements only. Use FETCh:...:STATe?
to query the main measurement state only. Use INITiate..., STOP...,
ABORt... to change the measurement state.
Return values:
<MainState> OFF | RDY | RUN
OFF: measurement switched off, no resources allocated, no
results available (when entered after STOP...)
RDY: measurement has been terminated, valid results can be
available
RUN: measurement running (after INITiate..., READ...),
synchronization pending or adjusted, resources active or queued
*RST: OFF
<SyncState> PEND | ADJ | INV
PEND: waiting for resource allocation, adjustment, hardware
switching ("pending")
ADJ: all necessary adjustments finished, measurement running
("adjusted")
INV: not applicable because <main_state>: OFF or RDY ("inva-
lid")
<RessourceState> QUE | ACT | INV
QUE: measurement without resources, no results available
("queued")
ACT: resources allocated, acquisition of results in progress but
not complete ("active")
INV: not applicable because <main_state>: OFF or RDY ("inva-
lid")
Example: See Performing a BER Measurement
Usage: Query only
Firmware/Software: V3.2.30
FETCh:BLUetooth:SIGN<i>:RXQuality:BER:STATe[:BEDR]?
Queries the main measurement state. Use FETCh:...:STATe:ALL? to query the
measurement state including the substates. Use INITiate..., STOP...,
ABORt... to change the measurement state.
Return values:
<MeasStatus> OFF | RDY | RUN
OFF: measurement switched off, no resources allocated, no
results available (when entered after ABORt...)
RDY: measurement has been terminated, valid results can be
available
RUN: measurement running (after INITiate..., READ...),
synchronization pending or adjusted, resources active or queued
Example: See Performing a BER Measurement
Usage: Query only
Firmware/Software: V3.2.30
Options: R&S CMW-KS610
Manual operation: See "BER (Softkey)" on page 216
CONFigure:BLUetooth:SIGN<i>:RXQuality:TOUT <Timeout>
Defines a timeout for the measurement. The timer is started when the measurement is
initiated via a READ or INIT command. It is not started if the measurement is initiated
manually ([ON | OFF] key or [RESTART | STOP] key).
When the measurement has completed the first measurement cycle (first single shot),
the statistical depth is reached and the timer is reset.
If the first measurement cycle has not been completed when the timer expires, the
measurement is stopped. The measurement state changes to RDY. The reliability indi-
cator is set to 1, indicating that a measurement timeout occurred. Still running READ,
FETCh or CALCulate commands are completed, returning the available results. At
least for some results, there are no values at all or the statistical depth has not been
reached.
A timeout of 0 s corresponds to an infinite measurement timeout.
Parameters:
<Timeout> numeric
Default unit: s
Firmware/Software: V3.2.30
Options: R&S CMW-KS610
CONFigure:BLUetooth:SIGN<i>:RXQuality:REPetition <Repetition>
Specifies the repetition mode of the measurement. The repetition mode specifies
whether the measurement is stopped after a single-shot or repeated continuously. Use
CONFigure:BLUetooth:SIGN<i>:RXQuality:PACKets[:BEDR] or
CONFigure:BLUetooth:SIGN<i>:RXQuality:PACKets:LENergy[:LE1M] to
determine the number of transport blocks per single shot.
Parameters:
<Repetition> SINGleshot | CONTinuous
SINGleshot: single-shot measurement
CONTinuous: continuous measurement
*RST: SING
Example: See Performing a BER Measurement
Firmware/Software: V3.2.60
Options: R&S CMW-KS610 for BR/EDR
R&S CMW-KS611 for LE
Manual operation: See "Repetition" on page 219
CONFigure:BLUetooth:SIGN<i>:RXQuality:PACKets[:BEDR] <NumberPackets>
Defines the number of data packets to be measured per measurement cycle (statistics
cycle).
Parameters:
<NumberPackets> numeric
Range: 1 to 400E+3
*RST: 1000
Example: See Configuring a BER Measurement
Firmware/Software: V3.2.30
CONFigure:BLUetooth:SIGN<i>:RXQuality:LIMit:MBER:BRATe <Limit>
Specifies the upper BER limit for BR RX measurements.
Parameters:
<Limit> numeric | ON | OFF
Range: 0 % to 100 %
*RST: 0.1 %
Default unit: %
Additional parameters: OFF | ON (disables the limit | enables the
limit using the previous/default level)
Example: See Configuring a BER Measurement
Firmware/Software: V3.2.30
Options: R&S CMW-KS610
Manual operation: See "Limits" on page 219
CONFigure:BLUetooth:SIGN<i>:RXQuality:LIMit:MBER:EDRate <Limit>
Specifies the upper BER limit for EDR RX measurements.
Parameters:
<Limit> numeric | ON | OFF
Range: 0 % to 100 %
Increment: 0.01 %
*RST: 0.01 %
Default unit: %
Additional parameters: OFF | ON (disables the limit | enables the
limit using the previous/default level)
Example: See Configuring a BER Measurement
Firmware/Software: V3.2.30
Options: R&S CMW-KS610
Manual operation: See "Limits" on page 219
CALCulate:BLUetooth:SIGN<i>:RXQuality:BER[:BEDR]?
FETCh:BLUetooth:SIGN<i>:RXQuality:BER[:BEDR]?
READ:BLUetooth:SIGN<i>:RXQuality:BER[:BEDR]?
Return all results of the signaling BER measurement.
The values described below are returned by FETCh and READ commands. CALCulate
commands return limit check results instead, one value for each result listed below.
Return values:
<1_Reliability> decimal
See Reliability Indicator
<2_BER> float
Bit error rate
Range: 0 % to 100 %
Default unit: %
<3_PER> float
Packet error rate
Range: 0 % to 100 %
Default unit: %
<4_BitErrors> decimal
Sum of received erroneous data bits
Range: 0 to 18.4467440737096E+18
<5_MissingPackets> float
Difference between the number of packets sent and the number
of packets received in percentage
Range: 0 % to 100 %
Default unit: %
<6_NAK> float
Percentage of packets not acknowledged by the EUT positively
Range: 0 % to 100 %
Default unit: %
<7_HEC_Errors> float
Percentage of packets with the bit errors in the header
Range: 0 % to 100 %
Default unit: %
<8_CRC_Errors> float
Percentage of packets with the bit errors in the payload
Range: 0 % to 100 %
Default unit: %
<9_WrongPackType> float
Received packets of a different type to the one originally trans-
mitted
Range: 0 % to 100 %
Default unit: %
<10_WrongPaylRate> float
Received packets of a different payload length to the one origi-
nally transmitted
Range: 0 % to 100 %
Default unit: %
<11_PackReceived> decimal
Total number of packets successfully received (without bad
packets)
Range: 0 to 200E+6
Example: See Performing a BER Measurement
Usage: Query only
Firmware/Software: V3.2.30
Options: R&S CMW-KS610
4 Rx PER Measurement
The PER measurement is installed together with the Bluetooth signaling application. To
access the measurement, press the softkey "Bluetooth RX Meas." in the Bluetooth sig-
naling main view. Then select the tab "PER". The PER measurement is supported for
the burst type "Low Energy" in direct test mode, connection test, or test mode.
The R&S CMW transmits Bluetooth LE test packets with a specific payload and evalu-
ates the percentage of packets that the EUT receives in error or misses.
The measurement is especially suitable to assess the characteristics and the perfor-
mance of the EUT receiver at low RF power levels. The transmission errors of the
higher signal level, produced on the way back (from the EUT to the instrument) can
usually be neglected.
For LE direct test mode, option R&S CMW-KS611 is required for LE 1M PHY (unco-
ded). Option R&S CMW-KS721 is also required for LE 2M PHY and LE coded PHY.
For LE with CTE tests, option R&S CMW-KS722 is also required.
For LE connection tests (normal mode) and LE test mode, option R&S CMW-KS601 is
required for LE 1M PHY (uncoded). Option R&S CMW-KS720 is also required for
LE 2M PHY and LE coded PHY.
1. To measure the packet error rate (PER), connect the EUT to the R&S CMW. Select
the operation mode direct test mode, connection test or LE test mode.
● For direct test mode, refer to "Executing Tests in Direct Test Mode" on page 29.
● For a connection test (normal mode), refer to Chapter 2.2.7, "Connection Test
(LE)", on page 26.
● For LE test mode, refer to Test Mode (LE).
3. Configure any other required settings as for a connection without the "PER" mea-
surement (channels, power, PHY, payload length, pattern, dirty Tx).
● EUT receives and counts the packets. Every packet with passing CRC is counted
as a correctly received packet.
● The R&S CMW commands the EUT to end the test.
● EUT reports the correct packets to the R&S CMW.
The results are calculated as follows:
● BER (LE test mode only): the R&S CMW compares the looped-back payload bits
with the bits originally sent and calculates the BER:
BER = bit errors / total number of received payload bits * 100%
Only packets looped back with the correct CRC and the correct packet header are
considered.
NAK rate = NAK / total number of packets transmitted * 100%
NAK packets comprise:
– Packets with negative acknowledgment in the header, which would normally
require retransmission (note that data packets are not retransmitted in test
mode)
– Packets with wrong payload length
– Packets with access code error
– Packets with missing acknowledgment bit in the header, which counts either as
a header error (HEC) or missing packets
● PER: the ratio of corrupted and missing packets to the total number of transmitted
packets in percent:
Acquisition Error
If the EUT reports LE_Test_Status FAIL, it results in an acquisition error (reliability indi-
cator value 7).
Results
The results are displayed to the left. For the description, refer to Chapter 4.2.3, "Mea-
surement Results", on page 237.
Common settings
The settings to the right are the same as in the configuration dialog.
● General setup: see Chapter 2.3.6, "General Settings", on page 66
● RF setup:
– For RF frequency settings, see Chapter 2.3.8.2, "RF Frequency", on page 74
– For other RF power settings, see Chapter 2.3.8.3, "RF Power Settings",
on page 77
– For the description of dirty transmitter, see Chapter 2.3.8.4, "Dirty Transmitter
Configuration", on page 78
● Signal characteristics: see Chapter 2.3.1.11, "Signal Characteristics", on page 53
● Connection Info (connection tests only): see Chapter 2.3.1.14, "Connection Info",
on page 56
Connection Status
The connection status information at the bottom of Rx measurement tabs shows the
signal and connection status, and for connection tests and test mode also the EUT for
paging. For background information, see Chapter 2.2.11, "Signaling States",
on page 36.
Remote command:
FETCh:BLUetooth:SIGN<i>:LENergy:STATe?
To turn the measurement on or off, select the control softkey and press [ON | OFF] or
[RESTART | STOP]. Alternatively, right-click the control softkey.
PER (Softkey)
The softkey shows the current measurement state. Additional measurement substates
can be retrieved via remote control.
Remote command:
INITiate:BLUetooth:SIGN<i>:RXQuality:PER
STOP:BLUetooth:SIGN<i>:RXQuality:PER
ABORt:BLUetooth:SIGN<i>:RXQuality:PER
FETCh:BLUetooth:SIGN<i>:RXQuality:PER:STATe?
Access: Bluetooth signaling main view > "Bluetooth Rx Meas" softkey > "PER" tab.
The PER tab shows the measurement results to the left, settings to the right and the
connection status at the bottom.
Results
The following results apply to LE PER measurements.
● "BER": bit error rate, percentage of received erroneous data bits.
● "Bit Errors": sum of received erroneous data bits.
● "PER": packet error rate, percentage of corrupted data packets that the EUT
received.
● "Correct Packets Reported": total number of packets with a passed CRC check
received by the EUT.
● "Packets Received Reported": total number of packets received by the EUT and
reported to R&S CMW
● "Number of Invalid CRC Packets": total number of looped-back packets with a
failed CRC check received by the R&S CMW.
● "Number of Pattern Type Errors": total number of looped-back packets with an
unequal payload pattern comparing to the packet sent originally.
● "Number of Payload Length Errors": total number of looped-back packets with
an unequal payload length comparing to the packet sent originally.
● "Packets Transmitted": number of test packets transmitted by the R&S CMW.
After the start of a single shot measurement, this value indicates the number of
transmitted packets and the total number of packets to be measured per single
shot. Two equal numbers indicate that the first shot is complete and the statistical
depth has been reached.
A measurement in continuous mode still continues and calculates results from the
previous statistical cycle (e.g. the previous 100 packets).
● "Packets Transmitted by CMW": Total number of test packets to be transmitted
during the RX measurement.
● "Report Integrity": Report integrity adjusts the ratio of the test packets with correct
CRC transmitted by the R&S CMW.
For LE connection tests, the report integrity is not supported.
● "Correct CRC Rate in Transmitted Packets": Ratio of the test packets with cor-
rect CRC, generated by the R&S CMW. If the report integrity is ON, the ratio is set
to 50%. If the report integrity is OFF, all packets contain correct CRC.
For LE connection tests, this result is not supported.
Remote command:
For LE in direct test mode:
FETCh:BLUetooth:SIGN<i>:RXQuality:PER:LENergy[:LE1M]? etc.
FETCh:BLUetooth:SIGN<i>:RXQuality:PER:LENergy:LE2M? etc.
FETCh:BLUetooth:SIGN<i>:RXQuality:PER:LENergy:LRANge? etc.
For LE connection test (normal mode):
FETCh:BLUetooth:SIGN<i>:RXQuality:PER:NMODe:LENergy:LE1M? etc.
FETCh:BLUetooth:SIGN<i>:RXQuality:PER:NMODe:LENergy:LE2M? etc.
FETCh:BLUetooth:SIGN<i>:RXQuality:PER:NMODe:LENergy:LRANge? etc.
For LE test mode:
FETCh:BLUetooth:SIGN<i>:RXQuality:PER:TMODe:LENergy:LE1M? etc.
FETCh:BLUetooth:SIGN<i>:RXQuality:PER:TMODe:LENergy:LE2M? etc.
FETCh:BLUetooth:SIGN<i>:RXQuality:PER:TMODe:LENergy:LRANge? etc.
Access: Bluetooth signaling main view > "Bluetooth Rx Meas" softkey > "Config" hot-
key.
The "Measurement Control" parameters configure the scope of the measurement. The
following chapter describes only the settings relevant for PER measurements.
Common Settings
The following settings are the same as in the configuration dialog.
● General setup: see Chapter 2.3.6, "General Settings", on page 66
● RF settings:
– For signal routing, see Chapter 2.3.8.1, "Signal Routing", on page 73
– For RF frequency settings, see Chapter 2.3.8.2, "RF Frequency", on page 74
– For RF power settings, see Chapter 2.3.8.3, "RF Power Settings", on page 77
● Dirty Tx: see Chapter 2.3.8.4, "Dirty Transmitter Configuration", on page 78
● Connection: see Chapter 2.3.9, "Connection Configuration", on page 85
● For "Suppress "Sig Off" Message", refer to "Suppress "Sig Off" Message"
on page 219.
Repetition
Defines how often the measurement is repeated if it is not stopped explicitly or by a
failed limit check.
● Continuous: The measurement is continued until it is explicitly terminated. The
results are periodically updated.
● Single-Shot: The measurement is stopped after one measurement cycle.
Single-shot is preferable if only a single measurement result is required under fixed
conditions, which is typical for remote-controlled measurements. The continuous mode
is suitable to monitor the evolution of the measurement results and to observe how
they depend on the measurement configuration, which is typically done in manual con-
trol.
Remote command:
CONFigure:BLUetooth:SIGN<i>:RXQuality:REPetition
Packets
Defines the number of data packets to be measured per measurement cycle (statistics
cycle). The number of packets sent can be larger than the specified value because of
possible packet lost on the way to the EUT and back.
The number of payload bits is displayed for information.
Remote command:
For LE in direct test mode:
CONFigure:BLUetooth:SIGN<i>:RXQuality:PACKets:LENergy[:LE1M]
CONFigure:BLUetooth:SIGN<i>:RXQuality:PACKets:LENergy:LE2M
CONFigure:BLUetooth:SIGN<i>:RXQuality:PACKets:LENergy:LRANge
For LE connection tests (normal mode):
CONFigure:BLUetooth:SIGN<i>:RXQuality:PACKets:NMODe:LENergy:LE1M
CONFigure:BLUetooth:SIGN<i>:RXQuality:PACKets:NMODe:LENergy:LE2M
CONFigure:BLUetooth:SIGN<i>:RXQuality:PACKets:NMODe:LENergy:
LRANge
For LE test mode:
CONFigure:BLUetooth:SIGN<i>:RXQuality:PACKets:TMODe:LENergy:LE1M
CONFigure:BLUetooth:SIGN<i>:RXQuality:PACKets:TMODe:LENergy:LE2M
CONFigure:BLUetooth:SIGN<i>:RXQuality:PACKets:TMODe:LENergy:
LRANge
Limits
Defines and activates/deactivates the upper limit for the results of PER measurements.
Remote command:
For direct test mode:
CONFigure:BLUetooth:SIGN<i>:RXQuality:LIMit:MPER:LENergy[:LE1M]
CONFigure:BLUetooth:SIGN<i>:RXQuality:LIMit:MPER:LENergy:LE2M
CONFigure:BLUetooth:SIGN<i>:RXQuality:LIMit:MPER:LENergy:LRANge
For LE connection test (normal mode):
CONFigure:BLUetooth:SIGN<i>:RXQuality:LIMit:MPER:NMODe:LENergy:
LE1M
CONFigure:BLUetooth:SIGN<i>:RXQuality:LIMit:MPER:NMODe:LENergy:
LE2M
CONFigure:BLUetooth:SIGN<i>:RXQuality:LIMit:MPER:NMODe:LENergy:
LRANge
For LE test mode:
CONFigure:BLUetooth:SIGN<i>:RXQuality:LIMit:MBER:TMODe:LENergy:
LE1M
CONFigure:BLUetooth:SIGN<i>:RXQuality:LIMit:MBER:TMODe:LENergy:
LE2M
CONFigure:BLUetooth:SIGN<i>:RXQuality:LIMit:MBER:TMODe:LENergy:
LRANge
CONFigure:BLUetooth:SIGN<i>:RXQuality:LIMit:MPER:TMODe:LENergy:
LE1M
CONFigure:BLUetooth:SIGN<i>:RXQuality:LIMit:MPER:TMODe:LENergy:
LE2M
CONFigure:BLUetooth:SIGN<i>:RXQuality:LIMit:MPER:TMODe:LENergy:
LRANge
Integrity
Sets the ratio of the packets with correct CRC, generated and transmitted by the
R&S CMW within LE direct test.
The setting is not relevant for LE connection tests.
This setting is appropriate for PER report integrity tests.
Refer to the following test purposes:
● RF-PHY/RCV/BV-07-C (for LE 1M PHY)
● RF-PHY/RCV/BV-13-C (for LE 2M PHY)
● RF-PHY/RCV/BV-30-C (for LE coded PHY, S = 2)
● RF-PHY/RCV/BV-31-C (for LE coded PHY, S = 8)
● RF-PHY/RCV/BV-19-C (for LE 1M PHY, stable modulation)
● RF-PHY/RCV/BV-25-C (for LE 2M PHY, stable modulation)
● RF-PHY/RCV/BV-36-C (for LE coded PHY, S = 2, stable modulation)
● RF-PHY/RCV/BV-37-C (for LE coded PHY, S = 8, stable modulation)
Remote command:
For direct test mode:
CONFigure:BLUetooth:SIGN<i>:RXQuality:RINTegrity:LENergy[:LE1M]
CONFigure:BLUetooth:SIGN<i>:RXQuality:RINTegrity:LENergy:LE2M
CONFigure:BLUetooth:SIGN<i>:RXQuality:RINTegrity:LENergy:LRANge
For LE connection test (normal mode): no integrity check
For LE test mode:
CONFigure:BLUetooth:SIGN<i>:RXQuality:RINTegrity:TMODe:LENergy:
LE1M
CONFigure:BLUetooth:SIGN<i>:RXQuality:RINTegrity:TMODe:LENergy:
LE2M
CONFigure:BLUetooth:SIGN<i>:RXQuality:RINTegrity:TMODe:LENergy:
LRANge
In the GUI, the commands for Dirty Tx Mode = "Single Values" are configurable.
Remote commands distinguish between settings for Dirty Tx Mode = "Single Values"
and "Spec Table".
For the configuration of the modulation index for Dirty Tx Mode = "Spec Table", refer to
Settings for Spec Table Mode .
For the configuration of the modulation index for Dirty Tx Mode = "Single Values", refer
to Single Values.
Remote command:
CONFigure:BLUetooth:SIGN<i>:RXQuality:SMINdex:LENergy
Connection
The connection settings are the same as in the configuration dialog, see Chapter 2.3.9,
"Connection Configuration", on page 85.
Hotkey Description
For a description, refer to Chapter 2.3.8.4, "Dirty Transmitter Configuration", on page 78.
Remote command:
Commands for LE direct test:
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:MODFrequency:LENergy:
LRANge etc.
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:MINDex:STABle:
LENergy:LRANge? etc.
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:MINDex:STANdard:
LENergy:LRANge? etc.
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:FDRift:LENergy[:
LE1M]? etc.
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:FOFFset:
LENergy[:LE1M]? etc.
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:STERror:
LENergy[:LE1M]? etc.
Commands for LE connection test:
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:MODFrequency:NMODe:
LENergy:LE1M etc.
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:MINDex:NMODe:
LENergy:LE1M? etc.
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:FDRift:NMODe:
LENergy:LE1M? etc.
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:FOFFset:NMODe:
LENergy:LE1M? etc.
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:STERror:NMODe:
LENergy:LE1M? etc.
Commands for LE test mode:
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:MODFrequency:TMODe:
LENergy:LE1M etc.
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:MINDex:STANdard:
TMODe:LENergy:LE1M? etc.
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:MINDex:STABle:
TMODe:LENergy:LE1M? etc.
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:FDRift:TMODe:
LENergy:LE1M? etc.
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:FOFFset:TMODe:
LENergy:LE1M? etc.
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:STERror:TMODe:
LENergy:LE1M? etc.
4.3 Programming
The PER measurements provided by the "Bluetooth Signaling" application are pro-
grammed as follows:
● The application is controlled by SCPI commands with the following syn-
tax: ...:BLUetooth:SIGN:RXQuality:...
● After a *RST, the measurement is switched off. Use
READ:BLUetooth:SIGN:RXQuality:PER? to initiate a single-shot measure-
ment and retrieve the results. You can also start the measurement using
INIT:BLUetooth:SIGN:RXQuality:PER and retrieve the results using
FETCh:BLUetooth:SIGN:RXQuality:PER?.
The examples in this section focus on commands directly related to the PER measure-
ments. For general configuration of the signaling application, refer to Chapter 2.4, "Pro-
gramming", on page 99.
// *****************************************************************************
// Configure an LE measurement for LE 1M PHY: number of test packets
// to be measured, PER limit (disable BER limit), and report integrity.
// Use stable modulation index.
// *****************************************************************************
CONFigure:BLUetooth:SIGN:RXQuality:PACKets:LENergy:LE1M 1000; *OPC?
CONFigure:BLUetooth:SIGN:RXQuality:LIMit:MPER:LENergy:LE1M 20; *OPC?
CONFigure:BLUetooth:SIGN:RXQuality:LIMit:MBER:TMODe:LENergy:LE1M OFF; *OPC?
CONFigure:BLUetooth:SIGN:RXQuality:RINTegrity:LENergy:LE1M ON; *OPC?
CONFigure:BLUetooth:SIGN:RXQuality:SMINdex:LENergy ON; *OPC?
// *****************************************************************************
// Use only two hopping channels (1 and 11). Select the measured channel 1.
//
// Alternatively use hopping on all chennels. Select the measured channel 1.
// *****************************************************************************
CONFigure:BLUetooth:SIGN:RFSettings:NMODe:HMODe:LENergy CH2; *OPC?
CONFigure:BLUetooth:SIGN:RFSettings:NMODe:MCHannel:LENergy 1; *OPC?
To configure and set up the connection for direct test mode, see "Direct test mode"
on page 109; for LE connection tests, see Chapter 2.4.8, "Connect LE (Normal Mode)",
on page 105.
The following commands control the measurement and return the current measure-
ment state.
INITiate:BLUetooth:SIGN<i>:RXQuality:PER.................................................................... 247
STOP:BLUetooth:SIGN<i>:RXQuality:PER....................................................................... 247
ABORt:BLUetooth:SIGN<i>:RXQuality:PER......................................................................247
FETCh:BLUetooth:SIGN<i>:RXQuality:PER:STATe?......................................................... 248
INITiate:BLUetooth:SIGN<i>:RXQuality:PER
STOP:BLUetooth:SIGN<i>:RXQuality:PER
ABORt:BLUetooth:SIGN<i>:RXQuality:PER
Starts, stops, or aborts the measurement:
● INITiate... starts or restarts the measurement. The measurement enters the
"RUN" state.
● STOP... halts the measurement immediately. The measurement enters the "RDY"
state. Measurement results are kept. The resources remain allocated to the mea-
surement.
● ABORt... halts the measurement immediately. The measurement enters the
"OFF" state. All measurement values are set to NAV. Allocated resources are
released.
Use FETCh...STATe? to query the current measurement state.
FETCh:BLUetooth:SIGN<i>:RXQuality:PER:STATe?
Queries the main measurement state. Use FETCh:...:STATe:ALL? to query the
measurement state including the substates. Use INITiate..., STOP...,
ABORt... to change the measurement state.
Return values:
<MeasStatus> OFF | RDY | RUN
OFF: measurement switched off, no resources allocated, no
results available (when entered after ABORt...)
RDY: measurement has been terminated, valid results can be
available
RUN: measurement running (after INITiate..., READ...),
synchronization pending or adjusted, resources active or queued
Example: See Performing a PER Measurement
Usage: Query only
Firmware/Software: V3.2.70
Options: R&S CMW-KS611
Manual operation: See "PER (Softkey)" on page 237
CONFigure:BLUetooth:SIGN<i>:RXQuality:LIMit:MPER:NMODe:LENergy:LE2M................. 251
CONFigure:BLUetooth:SIGN<i>:RXQuality:LIMit:MPER:NMODe:LENergy:LE1M................. 251
CONFigure:BLUetooth:SIGN<i>:RXQuality:LIMit:MPER:TMODe:LENergy:LRANge..............251
CONFigure:BLUetooth:SIGN<i>:RXQuality:LIMit:MPER:TMODe:LENergy:LE2M..................251
CONFigure:BLUetooth:SIGN<i>:RXQuality:LIMit:MPER:TMODe:LENergy:LE1M..................251
CONFigure:BLUetooth:SIGN<i>:RXQuality:LIMit:MPER:LENergy:LRANge.......................... 251
CONFigure:BLUetooth:SIGN<i>:RXQuality:LIMit:MPER:LENergy:LE2M..............................251
CONFigure:BLUetooth:SIGN<i>:RXQuality:LIMit:MPER:LENergy[:LE1M]............................ 251
CONFigure:BLUetooth:SIGN<i>:RXQuality:RINTegrity:TMODe:LENergy:LRANge................ 252
CONFigure:BLUetooth:SIGN<i>:RXQuality:RINTegrity:TMODe:LENergy:LE2M....................252
CONFigure:BLUetooth:SIGN<i>:RXQuality:RINTegrity:TMODe:LENergy:LE1M....................252
CONFigure:BLUetooth:SIGN<i>:RXQuality:RINTegrity:LENergy:LRANge............................ 252
CONFigure:BLUetooth:SIGN<i>:RXQuality:RINTegrity:LENergy:LE2M................................ 252
CONFigure:BLUetooth:SIGN<i>:RXQuality:RINTegrity:LENergy[:LE1M].............................. 252
CONFigure:BLUetooth:SIGN<i>:RXQuality:SMINdex:LENergy........................................... 253
CONFigure:BLUetooth:SIGN<i>:RXQuality:REPetition <Repetition>
Specifies the repetition mode of the measurement. The repetition mode specifies
whether the measurement is stopped after a single-shot or repeated continuously. Use
CONFigure:BLUetooth:SIGN<i>:RXQuality:PACKets[:BEDR] or
CONFigure:BLUetooth:SIGN<i>:RXQuality:PACKets:LENergy[:LE1M] to
determine the number of transport blocks per single shot.
Parameters:
<Repetition> SINGleshot | CONTinuous
SINGleshot: single-shot measurement
CONTinuous: continuous measurement
*RST: SING
Example: See Performing a BER Measurement
Firmware/Software: V3.2.60
Options: R&S CMW-KS610 for BR/EDR
R&S CMW-KS611 for LE
Manual operation: See "Repetition" on page 219
CONFigure:BLUetooth:SIGN<i>:RXQuality:PACKets:NMODe:LENergy:LRANge
<NumberPackets>
CONFigure:BLUetooth:SIGN<i>:RXQuality:PACKets:NMODe:LENergy:LE2M
<NumberPackets>
CONFigure:BLUetooth:SIGN<i>:RXQuality:PACKets:NMODe:LENergy:LE1M
<NumberPackets>
CONFigure:BLUetooth:SIGN<i>:RXQuality:PACKets:TMODe:LENergy:LRANge
<NumberPackets>
CONFigure:BLUetooth:SIGN<i>:RXQuality:PACKets:TMODe:LENergy:LE2M
<NumberPackets>
CONFigure:BLUetooth:SIGN<i>:RXQuality:PACKets:TMODe:LENergy:LE1M
<NumberPackets>
CONFigure:BLUetooth:SIGN<i>:RXQuality:PACKets:LENergy:LRANge
<NumberPackets>
CONFigure:BLUetooth:SIGN<i>:RXQuality:PACKets:LENergy:LE2M
<NumberPackets>
CONFigure:BLUetooth:SIGN<i>:RXQuality:PACKets:LENergy[:LE1M]
<NumberPackets>
Defines the number of packets to be measured per measurement cycle (statistics
cycle).
● LE direct test mode:
Commands for uncoded LE 1M PHY (..:LE1M..), LE 2M PHY (..:LE2M..),
and LE coded PHY (..:LRANge..) are available.
● LE connection tests (normal mode):
Commands ..:NMODe:LENergy:.. are available.
● LE test mode:
Commands ..:TMODe:LENergy:.. are available.
Parameters:
<NumberPackets> numeric
Range: 1 to 30E+3
*RST: 1500
Example: See Configuring a PER Measurement
Firmware/Software: V3.2.70, V3.5.70: added commands for ...:LE2M...
and ...:LRANge..., V3.7.61: added command for
LE1M ...:NMODe:..., V3.7.80: added commands for LE2M
and LRANge ...:NMODe:...,
V3.7.90: added commands for ...:TMODe:...
Options: R&S CMW-KS611 for LE1M direct test mode
Plus R&S CMW-KS721 for LE2M and LRANge
R&S CMW-KS601 for LE connection test and LE test mode
Plus R&S CMW-KS720 for LE2M and LRANge
Manual operation: See "Packets" on page 242
CONFigure:BLUetooth:SIGN<i>:RXQuality:LIMit:MBER:TMODe:LENergy:
LRANge <Limit>
CONFigure:BLUetooth:SIGN<i>:RXQuality:LIMit:MBER:TMODe:LENergy:LE2M
<Limit>
CONFigure:BLUetooth:SIGN<i>:RXQuality:LIMit:MBER:TMODe:LENergy:LE1M
<Limit>
Specifies the upper BER limit for PER measurements in LE test mode.
Commands for uncoded LE 1M PHY (..:TMODe:LENergy:LE1M..), LE 2M PHY
(..:TMODe:LENergy:LE2M..), and LE coded PHY
(..:TMODe:LENergy:LRANge..) are available.
Parameters:
<Limit> numeric | ON | OFF
Range: 0 % to 100 %
*RST: 0.1 %
Additional parameters: OFF | ON (disables the limit | enables the
limit using the previous/default value)
Example: See Configuring a PER Measurement
Firmware/Software: V3.7.90
Options: R&S CMW-KS601 for LE1M
Plus R&S CMW-KS720 for LE2M and LRANge
Manual operation: See "Limits" on page 242
CONFigure:BLUetooth:SIGN<i>:RXQuality:LIMit:MPER:NMODe:LENergy:
LRANge <Limit>
CONFigure:BLUetooth:SIGN<i>:RXQuality:LIMit:MPER:NMODe:LENergy:LE2M
<Limit>
CONFigure:BLUetooth:SIGN<i>:RXQuality:LIMit:MPER:NMODe:LENergy:LE1M
<Limit>
CONFigure:BLUetooth:SIGN<i>:RXQuality:LIMit:MPER:TMODe:LENergy:LRANge
<Limit>
CONFigure:BLUetooth:SIGN<i>:RXQuality:LIMit:MPER:TMODe:LENergy:LE2M
<Limit>
CONFigure:BLUetooth:SIGN<i>:RXQuality:LIMit:MPER:TMODe:LENergy:LE1M
<Limit>
CONFigure:BLUetooth:SIGN<i>:RXQuality:LIMit:MPER:LENergy:LRANge <Limit>
CONFigure:BLUetooth:SIGN<i>:RXQuality:LIMit:MPER:LENergy:LE2M <Limit>
CONFigure:BLUetooth:SIGN<i>:RXQuality:LIMit:MPER:LENergy[:LE1M] <Limit>
Specifies the upper PER limit for LE RX measurements.
● LE direct test mode:
Commands for uncoded LE 1M PHY (..:LE1M..), LE 2M PHY (..:LE2M..),
and LE coded PHY (..:LRANge..) are available.
● LE connection tests (normal mode):
Commands ..:NMODe:LENergy:.. are available.
● LE test mode:
Commands ..:TMODe:LENergy:.. are available.
Parameters:
<Limit> numeric | ON | OFF
Range: 0 % to 100 %
*RST: 30.8 %; normal mode: 13.4%
Default unit: %
Additional parameters: OFF | ON (disables the limit | enables the
limit using the previous/default value)
Example: See Configuring a PER Measurement
CONFigure:BLUetooth:SIGN<i>:RXQuality:RINTegrity:TMODe:LENergy:LRANge
<ReportIntegrity>
CONFigure:BLUetooth:SIGN<i>:RXQuality:RINTegrity:TMODe:LENergy:LE2M
<ReportIntegrity>
CONFigure:BLUetooth:SIGN<i>:RXQuality:RINTegrity:TMODe:LENergy:LE1M
<ReportIntegrity>
CONFigure:BLUetooth:SIGN<i>:RXQuality:RINTegrity:LENergy:LRANge
<ReportIntegrity>
CONFigure:BLUetooth:SIGN<i>:RXQuality:RINTegrity:LENergy:LE2M
<ReportIntegrity>
CONFigure:BLUetooth:SIGN<i>:RXQuality:RINTegrity:LENergy[:LE1M]
<ReportIntegrity>
Sets the ratio of the test packets with correct CRC transmitted by the R&S CMW.
● LE RF tests (direct test mode):
Commands for LE 1M PHY - uncoded (..:LE1M..), LE 2M PHY - uncoded
(..:LE2M..), and LE coded PHY (..:LRANge..) are available.
● LE test mode:
Commands ..:TMODe:LENergy:.. are available.
Parameters:
<ReportIntegrity> OFF | ON
OFF: 100% of packets generated with correct CRC
ON: 50% of packets generated with correct CRC
*RST: OFF
Example: See Configuring a PER Measurement
Firmware/Software: V3.2.70, V3.5.70: added commands for ...:LE2M...
and ...:LRANge...
V3.7.90: added commands for ...:TMODe:...
Options: R&S CMW-KS611 for LE direct test mode
Plus R&S CMW-KS721 for LE2M and LRANge
R&S CMW-KS601 for LE test mode
Plus R&S CMW-KS720 for LE2M
Manual operation: See "Integrity" on page 243
CONFigure:BLUetooth:SIGN<i>:RXQuality:SMINdex:LENergy <ModIndexType>
Selects the standard or stable modulation index.
Parameters:
<ModIndexType> OFF | ON
OFF: standard modulation index is used
ON: stable modulation index is used
*RST: OFF
Example: See Configuring a PER Measurement
Firmware/Software: V3.7.30
Options: R&S CMW-KS611
Manual operation: See "Stable Modulation Index (enabling)" on page 243
CALCulate:BLUetooth:SIGN<i>:RXQuality:PER:NMODe:LENergy:LRANge?
CALCulate:BLUetooth:SIGN<i>:RXQuality:PER:NMODe:LENergy:LE2M?
CALCulate:BLUetooth:SIGN<i>:RXQuality:PER:NMODe:LENergy:LE1M?
CALCulate:BLUetooth:SIGN<i>:RXQuality:PER:LENergy:LRANge?
CALCulate:BLUetooth:SIGN<i>:RXQuality:PER:LENergy:LE2M?
CALCulate:BLUetooth:SIGN<i>:RXQuality:PER:LENergy[:LE1M]?
FETCh:BLUetooth:SIGN<i>:RXQuality:PER:NMODe:LENergy:LRANge?
FETCh:BLUetooth:SIGN<i>:RXQuality:PER:NMODe:LENergy:LE2M?
FETCh:BLUetooth:SIGN<i>:RXQuality:PER:NMODe:LENergy:LE1M?
FETCh:BLUetooth:SIGN<i>:RXQuality:PER:LENergy:LRANge?
FETCh:BLUetooth:SIGN<i>:RXQuality:PER:LENergy:LE2M?
FETCh:BLUetooth:SIGN<i>:RXQuality:PER:LENergy[:LE1M]?
READ:BLUetooth:SIGN<i>:RXQuality:PER:NMODe:LENergy:LRANge?
READ:BLUetooth:SIGN<i>:RXQuality:PER:NMODe:LENergy:LE2M?
READ:BLUetooth:SIGN<i>:RXQuality:PER:NMODe:LENergy:LE1M?
READ:BLUetooth:SIGN<i>:RXQuality:PER:LENergy:LRANge?
READ:BLUetooth:SIGN<i>:RXQuality:PER:LENergy:LE2M?
READ:BLUetooth:SIGN<i>:RXQuality:PER:LENergy[:LE1M]?
Return all results of the signaling LE Rx measurement for LE direct test and LE con-
nection test.
● LE direct test mode:
Commands for uncoded LE 1M PHY (..:LE1M..), LE 2M PHY (..:LE2M..),
and LE coded PHY (..:LRANge..) are available.
● LE connection tests (normal mode):
Commands for uncoded LE 1M PHY (..:NMODe:LENergy:LE1M..), LE 2M PHY
(..:NMODe:LENergy:LE2M..), and LE coded PHY
(..:NMODe:LENergy:LRANge..) are available.
Return values:
<Reliability> decimal
See Reliability Indicator
<PER> float
Packet error rate
Range: 0 % to 100 %
Default unit: %
<PacketsReceived> decimal
Number of correct packets received and reported by the EUT.
Range: 0 to 30E+3
Example: See Performing a PER Measurement
Usage: Query only
Firmware/Software: V3.2.70, V3.5.70: added commands for ...:LE2M...
and ...:LRANge..., V3.7.61: added commands for
LE1M ...:NMODe:..., V3.7.80: added commands for LE2M
and LRANge ...:NMODe:...,
CALCulate:BLUetooth:SIGN<i>:RXQuality:PER:TMODe:LENergy:LRANge?
CALCulate:BLUetooth:SIGN<i>:RXQuality:PER:TMODe:LENergy:LE2M?
CALCulate:BLUetooth:SIGN<i>:RXQuality:PER:TMODe:LENergy:LE1M?
FETCh:BLUetooth:SIGN<i>:RXQuality:PER:TMODe:LENergy:LRANge?
FETCh:BLUetooth:SIGN<i>:RXQuality:PER:TMODe:LENergy:LE2M?
FETCh:BLUetooth:SIGN<i>:RXQuality:PER:TMODe:LENergy:LE1M?
READ:BLUetooth:SIGN<i>:RXQuality:PER:TMODe:LENergy:LRANge?
READ:BLUetooth:SIGN<i>:RXQuality:PER:TMODe:LENergy:LE2M?
READ:BLUetooth:SIGN<i>:RXQuality:PER:TMODe:LENergy:LE1M?
Return all results of the signaling Rx measurement in LE test mode.
Commands for uncoded LE 1M PHY (..:TMODe:LENergy:LE1M..), LE 2M PHY
(..:TMODe:LENergy:LE2M..), and LE coded PHY
(..:TMODe:LENergy:LRANge..) are available.
Return values:
<Reliability> decimal
See Reliability Indicator
<PER> float
Packet error rate
Range: 0 % to 100 %
Default unit: %
<CorPacketsRecv> decimal
Number of correct received packets reported by the EUT
Range: 0 to 30E+3
<BER> float
Bit error rate
Range: 0 % to 100 %
<PacketsReceived> decimal
Number of received packets detected by the R&S CMW
Range: 0 to 30E+3
<NumInvalidCRC> decimal
Number of packets with detected CRC error
<NumPatternErr> decimal
Number of packets with detected pattern error
<NumPayloadErr> decimal
Number of packets with detected payload length error
<BitErrors> decimal
Number of detected bit errors
Example: See Performing a PER Measurement
Usage: Query only
Firmware/Software: V3.7.90
Options: R&S CMW-KS601 for LE1M
Plus R&S CMW-KS720 for LE2M and LRANge
CONFigure:BLUetooth:SIGN<i>:RXQuality:RINTegrity:TMODe:LENergy:LE2M.......................................... 252
CONFigure:BLUetooth:SIGN<i>:RXQuality:RINTegrity:TMODe:LENergy:LRANge......................................252
CONFigure:BLUetooth:SIGN<i>:RXQuality:SMINdex:LENergy.................................................................... 253
FETCh:BLUetooth:SIGN<i>:RXQuality:PER:LENergy:LE2M?......................................................................254
FETCh:BLUetooth:SIGN<i>:RXQuality:PER:LENergy:LRANge?..................................................................254
FETCh:BLUetooth:SIGN<i>:RXQuality:PER:LENergy[:LE1M]?....................................................................254
FETCh:BLUetooth:SIGN<i>:RXQuality:PER:NMODe:LENergy:LE1M?........................................................254
FETCh:BLUetooth:SIGN<i>:RXQuality:PER:NMODe:LENergy:LE2M?........................................................254
FETCh:BLUetooth:SIGN<i>:RXQuality:PER:NMODe:LENergy:LRANge?....................................................254
FETCh:BLUetooth:SIGN<i>:RXQuality:PER:STATe?....................................................................................248
FETCh:BLUetooth:SIGN<i>:RXQuality:PER:TMODe:LENergy:LE1M?........................................................ 255
FETCh:BLUetooth:SIGN<i>:RXQuality:PER:TMODe:LENergy:LE2M?........................................................ 255
FETCh:BLUetooth:SIGN<i>:RXQuality:PER:TMODe:LENergy:LRANge?.................................................... 255
INITiate:BLUetooth:SIGN<i>:RXQuality:PER................................................................................................ 247
READ:BLUetooth:SIGN<i>:RXQuality:PER:LENergy:LE2M?....................................................................... 254
READ:BLUetooth:SIGN<i>:RXQuality:PER:LENergy:LRANge?................................................................... 254
READ:BLUetooth:SIGN<i>:RXQuality:PER:LENergy[:LE1M]?..................................................................... 254
READ:BLUetooth:SIGN<i>:RXQuality:PER:NMODe:LENergy:LE1M?......................................................... 254
READ:BLUetooth:SIGN<i>:RXQuality:PER:NMODe:LENergy:LE2M?......................................................... 254
READ:BLUetooth:SIGN<i>:RXQuality:PER:NMODe:LENergy:LRANge?..................................................... 254
READ:BLUetooth:SIGN<i>:RXQuality:PER:TMODe:LENergy:LE1M?..........................................................255
READ:BLUetooth:SIGN<i>:RXQuality:PER:TMODe:LENergy:LE2M?..........................................................255
READ:BLUetooth:SIGN<i>:RXQuality:PER:TMODe:LENergy:LRANge?..................................................... 255
STOP:BLUetooth:SIGN<i>:RXQuality:PER...................................................................................................247
5 Rx BER/PER Search
The signaling "BER Search" and "PER Search" are installed together with the Blue-
tooth signaling application. To access the measurement, press the softkey "Bluetooth
RX Meas." in the Bluetooth signaling main view. Then select the tab "BER Search" or
"PER Search".
● The BER measurement is supported for burst type "Basic Rate" or enhanced data
rate ("EDR") in test mode.
● The PER measurement is supported for the burst type "Low Energy"in direct test
modet, LE connection test, or LE test mode.
The search measurements determine the Rx sensitivity level of the EUT for a given
BER/PER value. The search iteration is performed at decreasing Tx RF output levels
until the target BER/PER is found, or the minimum CMW output level is reached.
The measurement is especially suitable to assess the characteristics and the perfor-
mance of the EUT receiver at low RF power levels. The transmission errors of the
higher signal level, produced on the way back (from the EUT to the instrument) can
usually be neglected.
Option R&S CMW-KS610 is required for BR and EDR.
For LE direct test mode, option R&S CMW-KS611 is required for LE 1M PHY (unco-
ded). Option R&S CMW-KS721 is also required for LE 2M PHY and LE coded PHY.
For LE with CTE tests, option R&S CMW-KS722 is also required.
For LE connection tests (normal mode) and LE test mode, option R&S CMW-KS601 is
required for LE 1M PHY (uncoded). Option R&S CMW-KS720 is also required for
LE 2M PHY and LE coded PHY.
2. Configure Rx measurement settings, especially the BER limit value for search iter-
ation. See Chapter 5.2.4, "Measurement Settings", on page 263.
3. Configure any other required settings as for a connection without the "BER Search"
measurement (frequency, power, packet type, payload length, pattern, dirty Tx).
2. Configure Rx measurement settings, especially the PER limit value for search iter-
ation. See Chapter 5.2.4, "Measurement Settings", on page 263.
3. Configure any other required settings as for a connection without the "PER Search"
measurement (channels, power, PHY, payload length, pattern, dirty Tx).
The measurements start at given "Start Level". The search iteration is performed at
decreasing power steps and is stopped if the measured BER/PER exceeds the speci-
fied search limits, see Limits.
The search tabs show the measurement results to the left, settings to the right and the
connection status at the bottom.
Results
The results are displayed to the left. For the description, refer to Chapter 5.2.3, "Mea-
surement Results", on page 262.
Common settings
The settings to the right are the same as in the configuration tree. Exception: level con-
figuration for search Rx measurements.
● General setup: see Chapter 2.3.6, "General Settings", on page 66
● RF setup:
– For RF frequency settings, see Chapter 2.3.8.2, "RF Frequency", on page 74
– Start level, see "Start Level" on page 261
– Level step, see "Level Step" on page 268
– For other RF power settings, see Chapter 2.3.8.3, "RF Power Settings",
on page 77
– For the description of dirty transmitter, see Chapter 2.3.8.4, "Dirty Transmitter
Configuration", on page 78
● Signal characteristics: see Chapter 2.3.1.11, "Signal Characteristics", on page 53
Start Level
The settings to the right are the same as in the configuration dialog (see "Common set-
tings" on page 260). Exception: "Start Level" configuration for search Rx measure-
ments.
The start level is equal to Tx Level (CMW)). This setting is only displayed within the
"RF Setup" pane of Rx search tabs.
Remote command:
CONFigure:BLUetooth:SIGN<i>:RFSettings:LEVel
Connection Status
The connection status information at the bottom of Rx measurement tabs shows the
signal and connection status, and for BR and EDR also the EUT for paging. For back-
ground information, see Chapter 2.2.11, "Signaling States", on page 36.
For BR/EDR tests, this information is the same as in the main view of signaling, see
Chapter 2.3.1.1, "Connection Status Tab - Connection Status", on page 42.
For LE tests, use the remote command below.
Remote command:
FETCh:BLUetooth:SIGN<i>:LENergy:STATe?
To turn the measurement on or off, select the control softkey and press [ON | OFF] or
[RESTART | STOP]. Alternatively, right-click the control softkey.
Remote command:
INITiate:BLUetooth:SIGN<i>:RXQuality:SEARch:BER[:BEDR]
STOP:BLUetooth:SIGN<i>:RXQuality:SEARch:BER[:BEDR]
ABORt:BLUetooth:SIGN<i>:RXQuality:SEARch:BER[:BEDR]
FETCh:BLUetooth:SIGN<i>:RXQuality:SEARch:BER:STATe:ALL[:BEDR]?
FETCh:BLUetooth:SIGN<i>:RXQuality:SEARch:BER:STATe[:BEDR]?
Remote command:
INITiate:BLUetooth:SIGN<i>:RXQuality:SEARch:PER
STOP:BLUetooth:SIGN<i>:RXQuality:SEARch:PER
ABORt:BLUetooth:SIGN<i>:RXQuality:SEARch:PER
FETCh:BLUetooth:SIGN<i>:RXQuality:SEARch:PER:STATe?
Access: Bluetooth signaling main view > "Bluetooth Rx Meas" > "BER Search"/ "PER
Search" tab.
The tabs show the measurement results to the left, settings to the right and the con-
nection status at the bottom.
Search Results
Search measurements provide in addition to the results of BER/PER measurements
also search-specific results. Search-specific results are situated in the middle of the left
pane.
Access: Bluetooth signaling main view > "Bluetooth Rx Meas" softkey > "Config" hot-
key.
For BR or EDR in test mode, option R&S CMW-KS610 is required.
For LE direct test mode, option R&S CMW-KS611 is required for LE 1M PHY (unco-
ded). Option R&S CMW-KS721 is also required for LE 2M PHY and LE coded PHY.
For LE with CTE tests, option R&S CMW-KS722 is also required.
For LE connection tests (normal mode) and LE test mode, option R&S CMW-KS601 is
required for LE 1M PHY (uncoded). Option R&S CMW-KS720 is also required for
LE 2M PHY and LE coded PHY.
The "Measurement Control" parameters configure the scope of the measurement. The
following chapter describes only the settings relevant for "BER Search" (BR/EDR) and
"PER Search" (LE) measurements.
Common Settings........................................................................................................266
Packets....................................................................................................................... 266
Start Level................................................................................................................... 267
Limits...........................................................................................................................267
Level Step................................................................................................................... 268
Integrity (PER Search)................................................................................................ 268
Measure Mode (LE Connection Test)..........................................................................268
Stable Modulation Index (LE) enabling....................................................................... 268
Connection.................................................................................................................. 269
Suppress "Sig Off" Message....................................................................................... 269
Related Dirty Tx Hotkeys............................................................................................ 269
Common Settings
The following settings are the same as in the main configuration dialog of Bluetooth
signaling.
● General setup: see Chapter 2.3.6, "General Settings", on page 66
● RF settings:
– For signal routing, see Chapter 2.3.8.1, "Signal Routing", on page 73
– For RF frequency settings, see Chapter 2.3.8.2, "RF Frequency", on page 74
– For RF power settings, see Chapter 2.3.8.3, "RF Power Settings", on page 77
● Dirty Tx: see Chapter 2.3.8.4, "Dirty Transmitter Configuration", on page 78
● Connection: see Chapter 2.3.9, "Connection Configuration", on page 85
Packets
Defines the number of data packets to be measured per measurement cycle (statistics
cycle). The number of packets sent can be larger than the specified value because of
possible packet lost on the way to the EUT and back.
The number of payload bits is displayed for information.
Remote command:
BER search measurement:
CONFigure:BLUetooth:SIGN<i>:RXQuality:SEARch:PACKets[:BEDR]
PER search measurement for LE direct test mode:
CONFigure:BLUetooth:SIGN<i>:RXQuality:SEARch:PACKets:LENergy[:
LE1M]
CONFigure:BLUetooth:SIGN<i>:RXQuality:SEARch:PACKets:LENergy:
LE2M
CONFigure:BLUetooth:SIGN<i>:RXQuality:SEARch:PACKets:LENergy:
LRANge
PER search measurement for LE connection test (normal mode):
CONFigure:BLUetooth:SIGN<i>:RXQuality:SEARch:PACKets:NMODe:
LENergy:LE1M
CONFigure:BLUetooth:SIGN<i>:RXQuality:SEARch:PACKets:NMODe:
LENergy:LE2M
CONFigure:BLUetooth:SIGN<i>:RXQuality:SEARch:PACKets:NMODe:
LENergy:LRANge
PER search measurement for LE test mode:
CONFigure:BLUetooth:SIGN<i>:RXQuality:SEARch:PACKets:TMODe:
LENergy:LE1M
CONFigure:BLUetooth:SIGN<i>:RXQuality:SEARch:PACKets:TMODe:
LENergy:LE2M
CONFigure:BLUetooth:SIGN<i>:RXQuality:SEARch:LIMit:MPER:TMODe:
LENergy:LRANge
Start Level
Specifies the initial Tx Level (CMW) for the search iteration.
The setting is only displayed in the "RF Setup" pane of Rx search tabs, see Chap-
ter 5.2.1, "Tab Overview", on page 259.
Remote command:
CONFigure:BLUetooth:SIGN<i>:RFSettings:LEVel
Limits
The limits of BER search and PER search measurement define the value for which the
Rx sensitivity level is determined.
Remote command:
BER search limits:
CONFigure:BLUetooth:SIGN<i>:RXQuality:SEARch:LIMit:MBER:BRATe
CONFigure:BLUetooth:SIGN<i>:RXQuality:SEARch:LIMit:MBER:EDRate
PER search limits for LE direct test mode:
CONFigure:BLUetooth:SIGN<i>:RXQuality:SEARch:LIMit:MPER:
LENergy[:LE1M]
CONFigure:BLUetooth:SIGN<i>:RXQuality:SEARch:LIMit:MPER:LENergy:
LE2M
CONFigure:BLUetooth:SIGN<i>:RXQuality:SEARch:LIMit:MPER:LENergy:
LRANge
PER search limits for LE connection test (normal mode):
CONFigure:BLUetooth:SIGN<i>:RXQuality:SEARch:LIMit:MPER:NMODe:
LENergy:LE1M
CONFigure:BLUetooth:SIGN<i>:RXQuality:SEARch:LIMit:MPER:NMODe:
LENergy:LE2M
CONFigure:BLUetooth:SIGN<i>:RXQuality:SEARch:LIMit:MPER:NMODe:
LENergy:LRANge
PER search limits for LE test mode:
CONFigure:BLUetooth:SIGN<i>:RXQuality:SEARch:LIMit:MBER:TMODe:
LENergy:LE1M
CONFigure:BLUetooth:SIGN<i>:RXQuality:SEARch:LIMit:MBER:TMODe:
LENergy:LE2M
CONFigure:BLUetooth:SIGN<i>:RXQuality:SEARch:LIMit:MBER:TMODe:
LENergy:LRANge
CONFigure:BLUetooth:SIGN<i>:RXQuality:SEARch:LIMit:MPER:TMODe:
LENergy:LE1M
CONFigure:BLUetooth:SIGN<i>:RXQuality:SEARch:LIMit:MPER:TMODe:
LENergy:LE2M
CONFigure:BLUetooth:SIGN<i>:RXQuality:SEARch:LIMit:MPER:TMODe:
LENergy:LRANge
Level Step
Specifies the power step. The search iteration is performed at decreasing power steps.
Remote command:
Commands for LE direct test mode:
CONFigure:BLUetooth:SIGN<i>:RXQuality:SEARch:STEP:BREDr
CONFigure:BLUetooth:SIGN<i>:RXQuality:SEARch:STEP:LENergy
Command for LE connection test (normal mode):
CONFigure:BLUetooth:SIGN<i>:RXQuality:SEARch:STEP:NMODe:LENergy
Command for LE test mode:
CONFigure:BLUetooth:SIGN<i>:RXQuality:SEARch:STEP:TMODe:LENergy
Connection
The connection settings are the same as in the configuration dialog, see Chapter 2.3.9,
"Connection Configuration", on page 85.
Hotkey Description
For a description, refer to Chapter 2.3.8.4, "Dirty Transmitter Configuration", on page 78.
Remote command:
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:MINDex:BRATe? etc.
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:FOFFset:BRATe?
etc.
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:STERror:BRATe?
etc.
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:FDRift:BRATe? etc.
LE commands for direct tests:
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:MODFrequency:LENergy:
LRANge etc.
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:MINDex:STABle:
LENergy:LRANge? etc.
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:MINDex:STANdard:
LENergy:LRANge? etc.
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:FDRift:LENergy[:
LE1M]? etc.
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:FOFFset:
LENergy[:LE1M]? etc.
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:STERror:
LENergy[:LE1M]? etc.
LE commands for connection test:
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:MODFrequency:NMODe:
LENergy:LE1M etc.
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:FDRift:NMODe:
LENergy:LE1M? etc.
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:FOFFset:NMODe:
LENergy:LE1M? etc.
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX:STAB:STERror:NMODe:
LENergy:LE1M? etc.
5.3 Programming
The BER search and PER search measurements provided by the "Bluetooth Signaling"
application are programmed as follows:
● The application is controlled by SCPI commands with the following syn-
tax: ...:BLUetooth:SIGN:RXQuality:SEARch:...
● After a *RST, the measurement is switched off. Use
READ:BLUetooth:SIGN:RXQuality:SEARch:BER? or
READ:BLUetooth:SIGN:RXQuality:SEARch:PER? to initiate a single-shot
measurement and retrieve the results. You can also start the measurement using
INIT:BLUetooth:SIGN:RXQuality:SEARch:BER or
INIT:BLUetooth:SIGN:RXQuality:SEARch:PER and retrieve the results
using FETCh:BLUetooth:SIGN:RXQuality:SEARch:BER? or
FETCh:BLUetooth:SIGN:RXQuality:SEARch:PER?.
The examples in this section focus on commands directly related to the BER and PER
search measurements. For general configuration of the signaling application, refer to
Chapter 2.4, "Programming", on page 99.
// *****************************************************************************
*RST; *OPC?
*CLS; *OPC?
// *****************************************************************************
// Configure a BR/EDR BER search measurement: number of transport
// blocks to be measured, limits and level steps
// *****************************************************************************
CONFigure:BLUetooth:SIGN:RXQuality:SEARch:PACKets:BEDR 10000; *OPC?
CONFigure:BLUetooth:SIGN:RXQuality:SEARch:LIMit:MBER:BRATe 100; *OPC?
CONFigure:BLUetooth:SIGN:RXQuality:SEARch:LIMit:MBER:EDRate 100; *OPC?
CONFigure:BLUetooth:SIGN:RXQuality:SEARch:STEP:BREDr 1; *OPC?
// *****************************************************************************
// Configure an LE search measurement for LE 1M PHY: number of test
// packets to be measured, PER limit, disable BER limt. Set level
// step and report integrity.
// *****************************************************************************
CONFigure:BLUetooth:SIGN:RXQuality:SEARch:PACKets:LENergy:LE1M 1000; *OPC?
CONFigure:BLUetooth:SIGN:RXQuality:SEARch:LIMit:MPER:LENergy:LE1M 20; *OPC?
CONFigure:BLUetooth:SIGN:RXQuality:SEARch:LIMit:MBER:TMODe:LENergy:LE1M OFF
CONFigure:BLUetooth:SIGN:RXQuality:SEARch:STEP:LENergy 1; *OPC?
CONFigure:BLUetooth:SIGN:RXQuality:SEARch:RINTegrity:LENergy:LE1M ON; *OPC?
// *****************************************************************************
// Use only two hopping channels (1 and 11). Select the measured channel 1.
//
// Alternatively use hopping on all chennels. Select the measured channel 1.
// *****************************************************************************
CONFigure:BLUetooth:SIGN:RFSettings:NMODe:HMODe:LENergy CH2; *OPC?
CONFigure:BLUetooth:SIGN:RFSettings:NMODe:MCHannel:LENergy 1; *OPC?
To configure and set up the BR/EDR connection in test mode, see Configure Test
Mode Classic.
To configure and set up the connection for LE RF tests, see "Direct test mode"
on page 109; for LE connection tests, see Chapter 2.4.8, "Connect LE (Normal Mode)",
on page 105.
INIT:BLUetooth:SIGN:RXQuality:SEARch:PER
FETCh:BLUetooth:SIGN:RXQuality:SEARch:PER:LENergy:LE1M?
CALCulate:BLUetooth:SIGN:RXQuality:SEARch:PER:LENergy:LE1M?
FETCh:BLUetooth:SIGN:RXQuality:SEARch:PER:STATe?
// *****************************************************************************
// Start measurement; wait for 5 ms and return BER results.
// Query measurement state and substates (should be "RUN,ADJ,ACT").
// *****************************************************************************
INIT:BLUetooth:SIGN:RXQuality:SEARch:BER
Pause 5000
FETCh:BLUetooth:SIGN:RXQuality:SEARch:BER?
CALCulate:BLUetooth:SIGN:RXQuality:SEARch:BER?
FETCh:BLUetooth:SIGN:RXQuality:SEARch:BER:STATe:ALL?
The following commands control the measurement and return the current measure-
ment state.
INITiate:BLUetooth:SIGN<i>:RXQuality:SEARch:BER[:BEDR]............................................273
STOP:BLUetooth:SIGN<i>:RXQuality:SEARch:BER[:BEDR].............................................. 273
ABORt:BLUetooth:SIGN<i>:RXQuality:SEARch:BER[:BEDR].............................................273
INITiate:BLUetooth:SIGN<i>:RXQuality:SEARch:PER....................................................... 273
STOP:BLUetooth:SIGN<i>:RXQuality:SEARch:PER..........................................................273
ABORt:BLUetooth:SIGN<i>:RXQuality:SEARch:PER........................................................ 273
FETCh:BLUetooth:SIGN<i>:RXQuality:SEARch:BER:STATe:ALL[:BEDR]?.......................... 274
FETCh:BLUetooth:SIGN<i>:RXQuality:SEARch:BER:STATe[:BEDR]?.................................275
FETCh:BLUetooth:SIGN<i>:RXQuality:SEARch:PER:STATe?............................................ 275
INITiate:BLUetooth:SIGN<i>:RXQuality:SEARch:BER[:BEDR]
STOP:BLUetooth:SIGN<i>:RXQuality:SEARch:BER[:BEDR]
ABORt:BLUetooth:SIGN<i>:RXQuality:SEARch:BER[:BEDR]
Starts, stops, or aborts the measurement:
● INITiate... starts or restarts the measurement. The measurement enters the
"RUN" state.
● STOP... halts the measurement immediately. The measurement enters the "RDY"
state. Measurement results are kept. The resources remain allocated to the mea-
surement.
● ABORt... halts the measurement immediately. The measurement enters the
"OFF" state. All measurement values are set to NAV. Allocated resources are
released.
Use FETCh...STATe? to query the current measurement state.
Example: See Performing a BER/PER Search Measurement
Usage: Event
Firmware/Software: V3.5.50
Options: R&S CMW-KS610
Manual operation: See "BER Search (Softkey)" on page 261
INITiate:BLUetooth:SIGN<i>:RXQuality:SEARch:PER
STOP:BLUetooth:SIGN<i>:RXQuality:SEARch:PER
ABORt:BLUetooth:SIGN<i>:RXQuality:SEARch:PER
Starts, stops, or aborts the measurement:
● INITiate... starts or restarts the measurement. The measurement enters the
"RUN" state.
● STOP... halts the measurement immediately. The measurement enters the "RDY"
state. Measurement results are kept. The resources remain allocated to the mea-
surement.
● ABORt... halts the measurement immediately. The measurement enters the
"OFF" state. All measurement values are set to NAV. Allocated resources are
released.
Use FETCh...STATe? to query the current measurement state.
Example: See Performing a BER/PER Search Measurement
Usage: Event
Firmware/Software: V3.5.50
Options: R&S CMW-KS611
Manual operation: See "PER Search (Softkey)" on page 261
FETCh:BLUetooth:SIGN<i>:RXQuality:SEARch:BER:STATe:ALL[:BEDR]?
Queries the main measurement state and the measurement substates. Both measure-
ment substates are relevant for running measurements only. Use FETCh:...:STATe?
to query the main measurement state only. Use INITiate..., STOP...,
ABORt... to change the measurement state.
Return values:
<MainState> OFF | RDY | RUN
OFF: measurement switched off, no resources allocated, no
results available (when entered after STOP...)
RDY: measurement has been terminated, valid results can be
available
RUN: measurement running (after INITiate..., READ...),
synchronization pending or adjusted, resources active or queued
*RST: OFF
<SyncState> PEND | ADJ | INV
PEND: waiting for resource allocation, adjustment, hardware
switching ("pending")
ADJ: all necessary adjustments finished, measurement running
("adjusted")
INV: not applicable because <main_state>: OFF or RDY ("inva-
lid")
<RessourceState> QUE | ACT | INV
QUE: measurement without resources, no results available
("queued")
ACT: resources allocated, acquisition of results in progress but
not complete ("active")
INV: not applicable because <main_state>: OFF or RDY ("inva-
lid")
Example: See Performing a BER/PER Search Measurement
Usage: Query only
Firmware/Software: V3.5.50
Options: R&S CMW-KS610
Manual operation: See "BER Search (Softkey)" on page 261
FETCh:BLUetooth:SIGN<i>:RXQuality:SEARch:BER:STATe[:BEDR]?
Queries the main measurement state. Use FETCh:...:STATe:ALL? to query the
measurement state including the substates. Use INITiate..., STOP...,
ABORt... to change the measurement state.
Return values:
<MeasStatus> OFF | RDY | RUN
OFF: measurement switched off, no resources allocated, no
results available (when entered after ABORt...)
RDY: measurement has been terminated, valid results can be
available
RUN: measurement running (after INITiate..., READ...),
synchronization pending or adjusted, resources active or queued
Example: See Performing a BER/PER Search Measurement
Usage: Query only
Firmware/Software: V3.5.50
Options: R&S CMW-KS610
Manual operation: See "BER Search (Softkey)" on page 261
FETCh:BLUetooth:SIGN<i>:RXQuality:SEARch:PER:STATe?
Queries the main measurement state. Use FETCh:...:STATe:ALL? to query the
measurement state including the substates. Use INITiate..., STOP...,
ABORt... to change the measurement state.
Return values:
<MeasStatus> OFF | RDY | RUN
OFF: measurement switched off, no resources allocated, no
results available (when entered after ABORt...)
RDY: measurement has been terminated, valid results can be
available
RUN: measurement running (after INITiate..., READ...),
synchronization pending or adjusted, resources active or queued
Example: See Performing a BER/PER Search Measurement
Usage: Query only
Firmware/Software: V3.5.50
Options: R&S CMW-KS611
Manual operation: See "PER Search (Softkey)" on page 261
CONFigure:BLUetooth:SIGN<i>:RXQuality:SEARch:TOUT................................................ 276
CONFigure:BLUetooth:SIGN<i>:RXQuality:SEARch:PACKets[:BEDR]................................ 277
CONFigure:BLUetooth:SIGN<i>:RXQuality:SEARch:PACKets:NMODe:LENergy:LRANge.....277
CONFigure:BLUetooth:SIGN<i>:RXQuality:SEARch:PACKets:NMODe:LENergy:LE2M........ 277
CONFigure:BLUetooth:SIGN<i>:RXQuality:SEARch:PACKets:NMODe:LENergy:LE1M........ 277
CONFigure:BLUetooth:SIGN<i>:RXQuality:SEARch:PACKets:TMODe:LENergy:LRANge..... 277
CONFigure:BLUetooth:SIGN<i>:RXQuality:SEARch:PACKets:TMODe:LENergy:LE2M.........277
CONFigure:BLUetooth:SIGN<i>:RXQuality:SEARch:PACKets:TMODe:LENergy:LE1M.........277
CONFigure:BLUetooth:SIGN<i>:RXQuality:SEARch:PACKets:LENergy:LRANge................. 277
CONFigure:BLUetooth:SIGN<i>:RXQuality:SEARch:PACKets:LENergy:LE2M..................... 278
CONFigure:BLUetooth:SIGN<i>:RXQuality:SEARch:PACKets:LENergy[:LE1M]................... 278
CONFigure:BLUetooth:SIGN<i>:RXQuality:SEARch:LIMit:MBER:BRATe.............................278
CONFigure:BLUetooth:SIGN<i>:RXQuality:SEARch:LIMit:MBER:EDRate........................... 278
CONFigure:BLUetooth:SIGN<i>:RXQuality:SEARch:LIMit:MBER:TMODe:LENergy:LRANge.279
CONFigure:BLUetooth:SIGN<i>:RXQuality:SEARch:LIMit:MBER:TMODe:LENergy:LE2M.... 279
CONFigure:BLUetooth:SIGN<i>:RXQuality:SEARch:LIMit:MBER:TMODe:LENergy:LE1M.... 279
CONFigure:BLUetooth:SIGN<i>:RXQuality:SEARch:LIMit:MPER:NMODe:LENergy:
LRANge..............................................................................................................279
CONFigure:BLUetooth:SIGN<i>:RXQuality:SEARch:LIMit:MPER:NMODe:LENergy:LE2M.... 279
CONFigure:BLUetooth:SIGN<i>:RXQuality:SEARch:LIMit:MPER:NMODe:LENergy:LE1M.... 279
CONFigure:BLUetooth:SIGN<i>:RXQuality:SEARch:LIMit:MPER:TMODe:LENergy:LRANge.279
CONFigure:BLUetooth:SIGN<i>:RXQuality:SEARch:LIMit:MPER:TMODe:LENergy:LE2M.... 279
CONFigure:BLUetooth:SIGN<i>:RXQuality:SEARch:LIMit:MPER:TMODe:LENergy:LE1M.... 279
CONFigure:BLUetooth:SIGN<i>:RXQuality:SEARch:LIMit:MPER:LENergy:LRANge............. 279
CONFigure:BLUetooth:SIGN<i>:RXQuality:SEARch:LIMit:MPER:LENergy:LE2M.................280
CONFigure:BLUetooth:SIGN<i>:RXQuality:SEARch:LIMit:MPER:LENergy[:LE1M]............... 280
CONFigure:BLUetooth:SIGN<i>:RXQuality:SEARch:STEP:BREDr..................................... 280
CONFigure:BLUetooth:SIGN<i>:RXQuality:SEARch:STEP:NMODe:LENergy...................... 281
CONFigure:BLUetooth:SIGN<i>:RXQuality:SEARch:STEP:TMODe:LENergy.......................281
CONFigure:BLUetooth:SIGN<i>:RXQuality:SEARch:STEP:LENergy...................................281
CONFigure:BLUetooth:SIGN<i>:RXQuality:SEARch:RINTegrity:TMODe:LENergy:LRANge...281
CONFigure:BLUetooth:SIGN<i>:RXQuality:SEARch:RINTegrity:TMODe:LENergy:LE2M.......281
CONFigure:BLUetooth:SIGN<i>:RXQuality:SEARch:RINTegrity:TMODe:LENergy:LE1M.......281
CONFigure:BLUetooth:SIGN<i>:RXQuality:SEARch:RINTegrity:LENergy:LRANge............... 281
CONFigure:BLUetooth:SIGN<i>:RXQuality:SEARch:RINTegrity:LENergy:LE2M...................281
CONFigure:BLUetooth:SIGN<i>:RXQuality:SEARch:RINTegrity:LENergy[:LE1M]................. 281
CONFigure:BLUetooth:SIGN<i>:RXQuality:SEARch:TOUT <Timeout>
Defines a timeout for the measurement. The timer is started when the measurement is
initiated via a READ or INIT command. It is not started if the measurement is initiated
manually ([ON | OFF] key or [RESTART | STOP] key).
When the measurement has completed the first measurement cycle (first single shot),
the statistical depth is reached and the timer is reset.
If the first measurement cycle has not been completed when the timer expires, the
measurement is stopped. The measurement state changes to RDY. The reliability indi-
cator is set to 1, indicating that a measurement timeout occurred. Still running READ,
FETCh or CALCulate commands are completed, returning the available results. At
least for some results, there are no values at all or the statistical depth has not been
reached.
A timeout of 0 s corresponds to an infinite measurement timeout.
Parameters:
<Timeout> numeric
Default unit: s
Firmware/Software: V3.5.50
Options: R&S CMW-KS610
CONFigure:BLUetooth:SIGN<i>:RXQuality:SEARch:PACKets[:BEDR]
<NumberPackets>
Defines the number of data packets to be measured per measurement cycle (statistics
cycle).
Parameters:
<NumberPackets> numeric
Range: 1 to 400E+3
*RST: 200
Example: See Configuring a BER/PER Search Measurement
Firmware/Software: V3.5.50
Options: R&S CMW-KS610
Manual operation: See "Packets" on page 266
CONFigure:BLUetooth:SIGN<i>:RXQuality:SEARch:PACKets:NMODe:LENergy:
LRANge <NumberPackets>
CONFigure:BLUetooth:SIGN<i>:RXQuality:SEARch:PACKets:NMODe:LENergy:
LE2M <NumberPackets>
CONFigure:BLUetooth:SIGN<i>:RXQuality:SEARch:PACKets:NMODe:LENergy:
LE1M <NumberPackets>
CONFigure:BLUetooth:SIGN<i>:RXQuality:SEARch:PACKets:TMODe:LENergy:
LRANge <NumberPackets>
CONFigure:BLUetooth:SIGN<i>:RXQuality:SEARch:PACKets:TMODe:LENergy:
LE2M <NumberPackets>
CONFigure:BLUetooth:SIGN<i>:RXQuality:SEARch:PACKets:TMODe:LENergy:
LE1M <NumberPackets>
CONFigure:BLUetooth:SIGN<i>:RXQuality:SEARch:PACKets:LENergy:LRANge
<NumberPackets>
CONFigure:BLUetooth:SIGN<i>:RXQuality:SEARch:PACKets:LENergy:LE2M
<NumberPackets>
CONFigure:BLUetooth:SIGN<i>:RXQuality:SEARch:PACKets:LENergy[:LE1M]
<NumberPackets>
Defines the number of data packets to be measured per measurement cycle (statistics
cycle).
● LE direct test mode:
Commands for uncoded LE 1M PHY (..:LE1M..), LE 2M PHY (..:LE2M..),
and LE coded PHY (..:LRANge..) are available.
● LE connection tests (normal mode):
Commands ..:NMODe:LENergy:.. are available.
● LE test mode:
Commands ..:TMODe:LENergy:.. are available.
Parameters:
<NumberPackets> numeric
Range: 1 to 30E+3
*RST: 200
Example: See Configuring a BER/PER Search Measurement
Firmware/Software: V3.5.50, V3.5.70: added commands for ..:LE2M..
and ..:LRANge.., V3.7.61: added command for
LE1M ..:NMODe:.., V3.7.80: added commands for LE2M and
LRANge ..:NMODe:..,
V3.7.90: added commands for ..:TMODe:..
Options: R&S CMW-KS611 for LE1M direct test mode
Plus R&S CMW-KS721 for LE2M and LRANge
R&S CMW-KS601 for LE connection test and LE test mode
Plus R&S CMW-KS720 for LE2M and LRANge
Manual operation: See "Packets" on page 266
CONFigure:BLUetooth:SIGN<i>:RXQuality:SEARch:LIMit:MBER:BRATe <Limit>
CONFigure:BLUetooth:SIGN<i>:RXQuality:SEARch:LIMit:MBER:EDRate <Limit>
Specifies the upper BER limit for BR (..:BRATe) and EDR (..:EDRate) BER search
measurements.
Parameters:
<Limit> numeric | ON | OFF
Range: 0 % to 100 %
Increment: 0.01 %
*RST: 0.01 %
Default unit: %
Additional parameters: OFF | ON (disables | enables the limit
using the previous/default value)
Example: See Configuring a BER/PER Search Measurement
Firmware/Software: V3.5.50
Options: R&S CMW-KS610
Manual operation: See "Limits" on page 267
CONFigure:BLUetooth:SIGN<i>:RXQuality:SEARch:LIMit:MBER:TMODe:
LENergy:LRANge <Limit>
CONFigure:BLUetooth:SIGN<i>:RXQuality:SEARch:LIMit:MBER:TMODe:
LENergy:LE2M <Limit>
CONFigure:BLUetooth:SIGN<i>:RXQuality:SEARch:LIMit:MBER:TMODe:
LENergy:LE1M <Limit>
Specifies the upper BER limit for RX search measurements in LE test mode.
Commands for uncoded LE 1M PHY (..:TMODe:LENergy:LE1M..), LE 2M PHY
(..:TMODe:LENergy:LE2M..), and LE coded PHY
(..:TMODe:LENergy:LRANge..) are available.
Parameters:
<Limit> numeric | ON | OFF
Range: 0 % to 100 %
*RST: 0.1 %
Additional parameters: OFF | ON (disables the limit | enables the
limit using the previous/default value)
Example: See Configuring a BER/PER Search Measurement
Firmware/Software: V3.7.90
Options: R&S CMW-KS601 for LE1M
Plus R&S CMW-KS720 for LE2M and LRANge
Manual operation: See "Limits" on page 267
CONFigure:BLUetooth:SIGN<i>:RXQuality:SEARch:LIMit:MPER:NMODe:
LENergy:LRANge <Limit>
CONFigure:BLUetooth:SIGN<i>:RXQuality:SEARch:LIMit:MPER:NMODe:
LENergy:LE2M <Limit>
CONFigure:BLUetooth:SIGN<i>:RXQuality:SEARch:LIMit:MPER:NMODe:
LENergy:LE1M <Limit>
CONFigure:BLUetooth:SIGN<i>:RXQuality:SEARch:LIMit:MPER:TMODe:
LENergy:LRANge <Limit>
CONFigure:BLUetooth:SIGN<i>:RXQuality:SEARch:LIMit:MPER:TMODe:
LENergy:LE2M <Limit>
CONFigure:BLUetooth:SIGN<i>:RXQuality:SEARch:LIMit:MPER:TMODe:
LENergy:LE1M <Limit>
CONFigure:BLUetooth:SIGN<i>:RXQuality:SEARch:LIMit:MPER:LENergy:
LRANge <Limit>
CONFigure:BLUetooth:SIGN<i>:RXQuality:SEARch:LIMit:MPER:LENergy:LE2M
<Limit>
CONFigure:BLUetooth:SIGN<i>:RXQuality:SEARch:LIMit:MPER:LENergy[:LE1M]
<Limit>
Specifies the upper PER limit for LE PER search measurements.
● LE direct test mode:
Commands for uncoded LE 1M PHY (..:LE1M..), LE 2M PHY (..:LE2M..),
and LE coded PHY (..:LRANge..) are available.
● LE connection tests (normal mode):
Commands ..:NMODe:LENergy:.. are available.
● LE test mode:
Commands ..:TMODe:LENergy:.. are available.
Parameters:
<Limit> numeric | ON | OFF
Range: 0 % to 100 %
*RST: 30.8 %
Default unit: %
Additional parameters: OFF | ON (disables the limit | enables the
limit using the previous/default level)
Example: See Configuring a BER/PER Search Measurement
Firmware/Software: V3.5.50, V3.5.70: added commands for ..:LE2M..
and ..:LRANge.., V3.7.61: added command for
LE1M ..:NMODe:.., V3.7.80: added commands for LE2M and
LRANge ..:NMODe:..,
V3.7.90: added commands for LE test mode ..:TMODe:..
Options: R&S CMW-KS611 for LE1M direct test mode
Plus R&S CMW-KS721 for LE2M and LRANge
R&S CMW-KS601 for LE connection test and LE test mode
Plus R&S CMW-KS720 for LE2M and LRANge
Manual operation: See "Limits" on page 267
CONFigure:BLUetooth:SIGN<i>:RXQuality:SEARch:STEP:BREDr <LevelStep>
Specifies the power step for the BR/EDR search iteration of BER search measure-
ments.
Parameters:
<LevelStep> numeric
Range: 0.01 dBm to 5 dBm
*RST: 0.5 dBm
Default unit: dB
Example: See Configuring a BER/PER Search Measurement
Firmware/Software: V3.5.50
Options: R&S CMW-KS610
CONFigure:BLUetooth:SIGN<i>:RXQuality:SEARch:STEP:NMODe:LENergy
<LevelStep>
CONFigure:BLUetooth:SIGN<i>:RXQuality:SEARch:STEP:TMODe:LENergy
<LevelStep>
CONFigure:BLUetooth:SIGN<i>:RXQuality:SEARch:STEP:LENergy <LevelStep>
Specifies the power step for the LE search iteration of PER search measurements.
● For LE connection tests (normal mode), command for LE 1M PHY - uncoded
(..:NMODe:LENergy:LE1M..) is available.
● For LE test mode, command ..:SEARch:STEP:TMODe:LENergy.. is available.
● For LE RF tests (direct test mode), command ..:SEARch:STEP:LENergy.. is
available.
Parameters:
<LevelStep> numeric
Range: 0.01 dB to 5 dB
*RST: 0.5 dB
Default unit: dB
Example: See Configuring a BER/PER Search Measurement
Firmware/Software: V3.5.50, V3.7.61: added command for ..:NMODe:..
V3.7.90: added commands for LE test mode ..:TMODe:..
Options: R&S CMW-KS611 for LE1M direct test mode
R&S CMW-KS601 for LE connection test and LE test mode
Manual operation: See "Level Step" on page 268
CONFigure:BLUetooth:SIGN<i>:RXQuality:SEARch:RINTegrity:TMODe:LENergy:
LRANge <ReportIntegrity>
CONFigure:BLUetooth:SIGN<i>:RXQuality:SEARch:RINTegrity:TMODe:LENergy:
LE2M <ReportIntegrity>
CONFigure:BLUetooth:SIGN<i>:RXQuality:SEARch:RINTegrity:TMODe:LENergy:
LE1M <ReportIntegrity>
CONFigure:BLUetooth:SIGN<i>:RXQuality:SEARch:RINTegrity:LENergy:LRANge
<ReportIntegrity>
CONFigure:BLUetooth:SIGN<i>:RXQuality:SEARch:RINTegrity:LENergy:LE2M
<ReportIntegrity>
CONFigure:BLUetooth:SIGN<i>:RXQuality:SEARch:RINTegrity:LENergy[:LE1M]
<ReportIntegrity>
Sets the ratio of the test packets with correct CRC transmitted by the R&S CMW.
Commands for uncoded LE 1M PHY (..:LE1M..), LE 2M PHY (..:LE2M..), and LE
coded PHY (..:LRANge..) are available.
Parameters:
<ReportIntegrity> OFF | ON
OFF: 100% of packets generated with correct CRC
ON: 50% of packets generated with correct CRC
*RST: OFF
Example: See Configuring a BER/PER Search Measurement
Firmware/Software: V3.5.50, V3.5.70: added commands for ...:LE2M...
and ...:LRANge...
V3.7.90: added commands for ...:TMODe:...
Options: R&S CMW-KS611 for LE1M direct test mode
Plus R&S CMW-KS721 for LE2M and LRANge
R&S CMW-KS601 for LE test mode
Plus R&S CMW-KS720 for LE2M
Manual operation: See "Integrity (PER Search)" on page 268
READ:BLUetooth:SIGN<i>:RXQuality:SEARch:PER:TMODe:LENergy:LRANge?.................285
READ:BLUetooth:SIGN<i>:RXQuality:SEARch:PER:TMODe:LENergy:LE2M?.....................285
READ:BLUetooth:SIGN<i>:RXQuality:SEARch:PER:TMODe:LENergy:LE1M?.....................285
CALCulate:BLUetooth:SIGN<i>:RXQuality:SEARch:BER[:BEDR]?
FETCh:BLUetooth:SIGN<i>:RXQuality:SEARch:BER[:BEDR]?
READ:BLUetooth:SIGN<i>:RXQuality:SEARch:BER[:BEDR]?
Return all results of the BR/EDR BER search measurement.
The values described below are returned by FETCh and READ commands. CALCulate
commands return limit check results instead, one value for each result listed below.
Return values:
<1_Reliability> decimal
See Reliability Indicator
<2_BER> float
Bit error rate
Range: 0 % to 100 %
Default unit: %
<3_PER> float
Packet error rate
Default unit: %
<4_BitErrors> decimal
Sum of received erroneous data bits
Range: 0 to 18.4467440737096E+18
<5_MissingPackets> float
Difference between the number of packets sent and the number
of packets received in percentage
Default unit: %
<6_NAK> float
Percentage of packets not acknowledged by the EUT positively
Default unit: %
<7_HEC_Errors> float
Percentage of packets with the bit errors in the header
Default unit: %
<8_CRC_Errors> float
Percentage of packets with the bit errors in the payload
Default unit: %
<9_WrongPackType> float
Received packets of a different type to the one originally trans-
mitted
Default unit: %
<10_WrongPaylRate> float
Received packets of a different payload length to the one origi-
nally transmitted
Default unit: %
<11_PackReceived> decimal
Total number of packets successfully received (without bad
packets)
Range: 0 to 200E+6
<12_SearchResult> float
TX level of the R&S CMW resulting in the configured BER
search limit
Range: -100 dBm to 0 dBm
Example: See Performing a BER/PER Search Measurement
Usage: Query only
Firmware/Software: V3.5.50
Options: R&S CMW-KS610
CALCulate:BLUetooth:SIGN<i>:RXQuality:SEARch:PER:NMODe:LENergy:
LRANge?
CALCulate:BLUetooth:SIGN<i>:RXQuality:SEARch:PER:NMODe:LENergy:
LE2M?
CALCulate:BLUetooth:SIGN<i>:RXQuality:SEARch:PER:NMODe:LENergy:
LE1M?
CALCulate:BLUetooth:SIGN<i>:RXQuality:SEARch:PER:LENergy:LRANge?
CALCulate:BLUetooth:SIGN<i>:RXQuality:SEARch:PER:LENergy:LE2M?
CALCulate:BLUetooth:SIGN<i>:RXQuality:SEARch:PER:LENergy[:LE1M]?
FETCh:BLUetooth:SIGN<i>:RXQuality:SEARch:PER:NMODe:LENergy:LRANge?
FETCh:BLUetooth:SIGN<i>:RXQuality:SEARch:PER:NMODe:LENergy:LE2M?
FETCh:BLUetooth:SIGN<i>:RXQuality:SEARch:PER:NMODe:LENergy:LE1M?
FETCh:BLUetooth:SIGN<i>:RXQuality:SEARch:PER:LENergy:LRANge?
FETCh:BLUetooth:SIGN<i>:RXQuality:SEARch:PER:LENergy:LE2M?
FETCh:BLUetooth:SIGN<i>:RXQuality:SEARch:PER:LENergy[:LE1M]?
READ:BLUetooth:SIGN<i>:RXQuality:SEARch:PER:NMODe:LENergy:LRANge?
READ:BLUetooth:SIGN<i>:RXQuality:SEARch:PER:NMODe:LENergy:LE2M?
READ:BLUetooth:SIGN<i>:RXQuality:SEARch:PER:NMODe:LENergy:LE1M?
READ:BLUetooth:SIGN<i>:RXQuality:SEARch:PER:LENergy:LRANge?
READ:BLUetooth:SIGN<i>:RXQuality:SEARch:PER:LENergy:LE2M?
READ:BLUetooth:SIGN<i>:RXQuality:SEARch:PER:LENergy[:LE1M]?
Return the results of PER search RX measurement for LE direct test mode and LE
connection tests.
● LE direct test mode:
Commands for uncoded LE 1M PHY (..:LE1M..), LE 2M PHY (..:LE2M..),
and LE coded PHY (..:LRANge..) are available.
CALCulate:BLUetooth:SIGN<i>:RXQuality:SEARch:PER:TMODe:LENergy:
LRANge?
CALCulate:BLUetooth:SIGN<i>:RXQuality:SEARch:PER:TMODe:LENergy:LE2M?
CALCulate:BLUetooth:SIGN<i>:RXQuality:SEARch:PER:TMODe:LENergy:LE1M?
FETCh:BLUetooth:SIGN<i>:RXQuality:SEARch:PER:TMODe:LENergy:LRANge?
FETCh:BLUetooth:SIGN<i>:RXQuality:SEARch:PER:TMODe:LENergy:LE2M?
FETCh:BLUetooth:SIGN<i>:RXQuality:SEARch:PER:TMODe:LENergy:LE1M?
READ:BLUetooth:SIGN<i>:RXQuality:SEARch:PER:TMODe:LENergy:LRANge?
READ:BLUetooth:SIGN<i>:RXQuality:SEARch:PER:TMODe:LENergy:LE2M?
READ:BLUetooth:SIGN<i>:RXQuality:SEARch:PER:TMODe:LENergy:LE1M?
Return the results of PER search RX measurement in LE test mode.
FETCh:BLUetooth:SIGN<i>:RXQuality:SEARch:BER:STATe:ALL[:BEDR]?.................................................274
FETCh:BLUetooth:SIGN<i>:RXQuality:SEARch:BER:STATe[:BEDR]?........................................................ 275
FETCh:BLUetooth:SIGN<i>:RXQuality:SEARch:BER[:BEDR]?....................................................................283
FETCh:BLUetooth:SIGN<i>:RXQuality:SEARch:PER:LENergy:LE2M?....................................................... 284
FETCh:BLUetooth:SIGN<i>:RXQuality:SEARch:PER:LENergy:LRANge?................................................... 284
FETCh:BLUetooth:SIGN<i>:RXQuality:SEARch:PER:LENergy[:LE1M]?..................................................... 284
FETCh:BLUetooth:SIGN<i>:RXQuality:SEARch:PER:NMODe:LENergy:LE1M?......................................... 284
FETCh:BLUetooth:SIGN<i>:RXQuality:SEARch:PER:NMODe:LENergy:LE2M?......................................... 284
FETCh:BLUetooth:SIGN<i>:RXQuality:SEARch:PER:NMODe:LENergy:LRANge?..................................... 284
FETCh:BLUetooth:SIGN<i>:RXQuality:SEARch:PER:STATe?..................................................................... 275
FETCh:BLUetooth:SIGN<i>:RXQuality:SEARch:PER:TMODe:LENergy:LE1M?..........................................285
FETCh:BLUetooth:SIGN<i>:RXQuality:SEARch:PER:TMODe:LENergy:LE2M?..........................................285
FETCh:BLUetooth:SIGN<i>:RXQuality:SEARch:PER:TMODe:LENergy:LRANge?..................................... 285
INITiate:BLUetooth:SIGN<i>:RXQuality:SEARch:BER[:BEDR].................................................................... 273
INITiate:BLUetooth:SIGN<i>:RXQuality:SEARch:PER................................................................................. 273
READ:BLUetooth:SIGN<i>:RXQuality:SEARch:BER[:BEDR]?..................................................................... 283
READ:BLUetooth:SIGN<i>:RXQuality:SEARch:PER:LENergy:LE2M?.........................................................284
READ:BLUetooth:SIGN<i>:RXQuality:SEARch:PER:LENergy:LRANge?.................................................... 284
READ:BLUetooth:SIGN<i>:RXQuality:SEARch:PER:LENergy[:LE1M]?.......................................................284
READ:BLUetooth:SIGN<i>:RXQuality:SEARch:PER:NMODe:LENergy:LE1M?...........................................284
READ:BLUetooth:SIGN<i>:RXQuality:SEARch:PER:NMODe:LENergy:LE2M?...........................................284
READ:BLUetooth:SIGN<i>:RXQuality:SEARch:PER:NMODe:LENergy:LRANge?...................................... 284
READ:BLUetooth:SIGN<i>:RXQuality:SEARch:PER:TMODe:LENergy:LE1M?........................................... 285
READ:BLUetooth:SIGN<i>:RXQuality:SEARch:PER:TMODe:LENergy:LE2M?........................................... 285
READ:BLUetooth:SIGN<i>:RXQuality:SEARch:PER:TMODe:LENergy:LRANge?.......................................285
STOP:BLUetooth:SIGN<i>:RXQuality:SEARch:BER[:BEDR]....................................................................... 273
STOP:BLUetooth:SIGN<i>:RXQuality:SEARch:PER.................................................................................... 273
6 Rx Direction Finding
For direct test mode over HCI and if a constant tone extension (CTE) is present in a
received packet, the controller can generate events containing IQ samples of the CTE.
The R&S CMW provides IQ samples coherency and IQ samples dynamic range Rx
measurements for LE with CTE, uncoded physical layer (LE 1M PHY and LE 2M PHY).
The supported CTE types are:
● Angle of arrival (AoA) 1 µs or 2 µs
● Angle of departure (AoD) 1 µs or 2 µs
Option R&S CMW-KS722 is required for LE with CTE.
3. Select the RF test. Refer to "Operating Mode" on page 66. See also "Executing
Tests in Direct Test Mode" on page 29.
8. Configure any other required settings as for a connection without direction finding
measurements (frequency for direct test mode, power, PHY, sync word, payload
length, pattern).
9. Switch on the "IQ Samples Coherency" or "IQ Samples Dynamic Range" measure-
ment. Retrieve the results.
To turn the measurement on or off, select the control softkey and press [ON | OFF] or
[RESTART | STOP]. Alternatively, right-click the control softkey.
IQ Coherency (Softkey)
The softkey shows the current measurement state. Additional measurement substates
can be retrieved via remote control.
Option R&S CMW-KS722 is required for LE with CTE.
Remote command:
INITiate:BLUetooth:SIGN<i>:RXQuality:IQCoherency
STOP:BLUetooth:SIGN<i>:RXQuality:IQCoherency
ABORt:BLUetooth:SIGN<i>:RXQuality:IQCoherency
FETCh:BLUetooth:SIGN<i>:RXQuality:IQCoherency:STATe?
Remote command:
INITiate:BLUetooth:SIGN<i>:RXQuality:IQDRange
STOP:BLUetooth:SIGN<i>:RXQuality:IQDRange
ABORt:BLUetooth:SIGN<i>:RXQuality:IQDRange
FETCh:BLUetooth:SIGN<i>:RXQuality:IQDRange:STATe?
Access: Bluetooth signaling main view > "Bluetooth Rx Meas" softkey > "IQ Coher-
ency" or "IQ Dynamic Range" tab.
All results of the direction finding Rx measurements are displayed on the "IQ Coher-
ency" and "IQ Dynamic Range" tab. The results are described below.
IQ samples coherency results.....................................................................................291
└ Diagram........................................................................................................ 292
└ Tables............................................................................................................292
IQ samples dynamic range results..............................................................................293
● "No. of Processed with Valid CRC": No. of valid HCI reports processed by the
R&S CMW
● "No. of Possible Phase Measurements": No. of possible phase measurements
determined by CTE length, slot length and number of antennas
The second table lists results per non-reference antenna of the DUT.
● "No. of Valid Phase Measurements": No. of already reported valid measure-
ments to the required minimal number of measurements (see "Number of Mea-
surements" on page 298)
The valid measurement is defined as follows:
– For reference phase deviation (ANT0), a valid IQ sample pair is required follow-
ing the non-reference antenna (n+1), at the pair before (n-1), and also (n-2)
– For relative phase (ANT1 to ANT3), a valid IQ sample pair for the non-refer-
ence antenna is required to be measured (n), at the pair before (n-1), and also
(n-2)
● "Mean Reference Phase Difference": mean reference phase deviation (RPD) for
ANT0
● "Mean Phase Difference": mean relative phase RP(m) for ANT1 to ANT3
● "95 Mean Phase Diff. Range": 95% confidence level of mean RP(m) range
Remote command:
FETCh:BLUetooth:SIGN<i>:RXQuality:IQCoherency:LENergy:LE1M:
A0Reference?
FETCh:BLUetooth:SIGN<i>:RXQuality:IQCoherency:LENergy:LE1M:
A1NReference? etc.
The view displays the scalar results of IQ samples dynamic range Rx measurement.
The first table contains the statistics of R&S CMW
● "No. of Transmitted Packets": total number of packets transmitted by the
R&S CMW since the beginning of the measurement to the required total number of
packets to be sent by the R&S CMW (see "Packets" on page 298)
● "No. of Received Events": percentage of all reports received from the DUT
● "No. of Processed Events": percentage of all reports received from the DUT
● "No. of Received Events with Valid CRC": percentage of valid reports received
from the DUT
The second table lists calculated mean amplitude differences. The limit checks verifies,
whether the following condition is fulfilled:
MeanANT3 < MeanANT2 < MeanANT0 < MeanANT1
The third table lists results per DUT's antenna.
● "Mean Amplitude": mean IQ amplitude levels in dBFS (dB values relative to the
largest possible measured IQ amplitude at the DUT)
Mean amplitude is calculated as 10 log10√(I2+Q2)
● "No. of Possible Amplitude Measurements": No. of possible amplitude mea-
surements determined by CTE length, slot length and number of antennas
● "No. of Valid Amplitude Measurements": No. of already reported valid IQ sam-
ples to the required minimal number of measurements (see "Number of Measure-
ments" on page 298)
Remote command:
FETCh:BLUetooth:SIGN<i>:RXQuality:IQDRange:LENergy:LE1M:
A0Reference? etc.
FETCh:BLUetooth:SIGN<i>:RXQuality:IQDRange:LENergy:LE1M:
A1NReference? etc.
FETCh:BLUetooth:SIGN<i>:RXQuality:IQDRange:ANTMeanamp:LENergy:
LE1M? etc.
Access: Bluetooth signaling main view > "Bluetooth Rx Meas" softkey > "Config" hot-
key.
The "Measurement Control" parameters configure the scope of the measurement. The
following chapter describes only the settings relevant for direction finding measure-
ments.
Common Settings........................................................................................................296
Direction finding settings............................................................................................. 296
└ Inter Burst Length......................................................................................... 297
└ Ignore Test End Response............................................................................297
└ Measure on Exception.................................................................................. 298
└ Packets......................................................................................................... 298
└ Number of Measurements............................................................................ 298
└ Limits.............................................................................................................299
└ External Attenuation......................................................................................299
└ Gain Offset....................................................................................................300
Dump DF IQ Sample Pairs..........................................................................................300
Connection.................................................................................................................. 301
Suppress "Sig Off" Message....................................................................................... 301
Common Settings
The following settings are the same as in the configuration dialog.
● General setup: see Chapter 2.3.6, "General Settings", on page 66
● RF settings:
– For signal routing, see Chapter 2.3.8.1, "Signal Routing", on page 73
– For RF frequency settings, see Chapter 2.3.8.2, "RF Frequency", on page 74
– For RF power settings, see Chapter 2.3.8.3, "RF Power Settings", on page 77
● Dirty Tx: see Chapter 2.3.8.4, "Dirty Transmitter Configuration", on page 78
● Connection: see Chapter 2.3.9, "Connection Configuration", on page 85
Remote command:
CONFigure:BLUetooth:SIGN<i>:RXQuality:ITENd:LENergy:LE1M
CONFigure:BLUetooth:SIGN<i>:RXQuality:ITENd:LENergy:LE2M
0 (reference) -52
1 (non-reference) -49
2 (non-reference) -57
3 (non-reference) -62
Remote command:
CONFigure:BLUetooth:SIGN<i>:RXQuality:IQCoherency:LIMit:LENergy:
LE1M:A0Reference
CONFigure:BLUetooth:SIGN<i>:RXQuality:IQCoherency:LIMit:LENergy:
LE1M:A1NReference etc.
CONFigure:BLUetooth:SIGN<i>:RXQuality:IQCoherency:LIMit:LENergy:
LE2M:A0Reference
CONFigure:BLUetooth:SIGN<i>:RXQuality:IQCoherency:LIMit:LENergy:
LE2M:A1NReference etc.
CONFigure:BLUetooth:SIGN<i>:RXQuality:IQDRange:ANTMeanamp:LIMit:
LENergy:LE1M
CONFigure:BLUetooth:SIGN<i>:RXQuality:IQDRange:ANTMeanamp:LIMit:
LENergy:LE2M
Remote command:
CONFigure:BLUetooth:SIGN<i>:RXQuality:IQSDump
Connection
The connection settings are the same as in the configuration dialog, see Chapter 2.3.9,
"Connection Configuration", on page 85.
6.3 Programming
The direction finding Rx measurements provided by the "Bluetooth Signaling" applica-
tion contain IQ samples coherency measurement and IQ samples dynamic range mea-
surement.
● The IQ samples coherency measurement is controlled by SCPI commands with the
following syntax: ...:BLUetooth:SIGN:RXQuality:IQCoherency...
The IQ samples dynamic range measurement is controlled by SCPI commands
with the following syntax: ...:BLUetooth:SIGN:RXQuality:IQDRange...
● After a *RST, the measurement is switched off.
For the IQ samples coherency measurement, use e.g.
READ:BLUetooth:SIGN:RXQuality:IQCoherency:LENergy:LE1M:
A1NReference? to initiate a single-shot measurement and retrieve the results.
You can also start the measurement using e.g.
INIT:BLUetooth:SIGN:RXQuality:IQCoherency and retrieve the results
using
FETCh:BLUetooth:SIGN:RXQuality:IQCoherency:LENergy:LE1M:
A1NReference?.
For the IQ samples dynamic range measurement, use e.g.
READ:BLUetooth:SIGN:RXQuality:IQDRange:LENergy:LE1M:
A1NReference? to initiate a single-shot measurement and retrieve the results.
You can also start the measurement using e.g.
INIT:BLUetooth:SIGN:RXQuality:RXQuality:IQDRange and retrieve the
results using
FETCh:BLUetooth:SIGN:RXQuality:IQDRange:LENergy:LE1M:
A1NReference?.
The examples in this section focus on commands directly related to the direction find-
ing Rx measurements. For general configuration of the signaling application, refer to
Chapter 2.4, "Programming", on page 99.
// *****************************************************************************
// Set operating mode to RF test.
// *****************************************************************************
CONFigure:BLUetooth:SIGN:OPMode RFT; *OPC?
// *****************************************************************************
// Specify LE burst type, physical layer, packet type, sync word.
// *****************************************************************************
CONFigure:BLUetooth:SIGN:CONNection:BTYPe LE; *OPC?
CONFigure:BLUetooth:SIGN:CONNection:PHY:LENergy LE1M; *OPC?
CONFigure:BLUetooth:SIGN:CONNection:PACKets:PTYPe:LENergy:LE1M RFCTe; *OPC?
CONFigure:BLUetooth:SIGN:CONNection:SYNWord:LENergy #H71764129; *OPC?
// *****************************************************************************
// Specify channel number and query the frequency.
// *****************************************************************************
CONFigure:BLUetooth:SIGN:RFSettings:CHANnel:DTMode 10
CONFigure:BLUetooth:SIGN:RFSettings:FREQuency:DTMode?
// *****************************************************************************
// Select RF connectors.
// Specify the number of antennas, external attenuation for reference
// antenna and offset of external attenuation for all three
// non-reference antennas. Set gain offset for IQ dynamic range tests.
// *****************************************************************************
ROUTe:BLUetooth:SIGN:SCENario:OTRX RF2C,RX1,RF2C,TX1
CONFigure:BLUetooth:SIGN:RFSettings:NANTenna:CTE:LENergy 2
CONFigure:BLUetooth:SIGN:RFSettings:EATTenuation:INPut 4
CONFigure:BLUetooth:SIGN:RFSettings:EATTenuation:OUTPut 4
CONFigure:BLUetooth:SIGN:RFSettings:AOFFset:INPut:CTE:LENergy 1,1,1
CONFigure:BLUetooth:SIGN:RFSettings:AOFFset:OUTPut:CTE:LENergy 1,1,1
CONFigure:BLUetooth:SIGN:RFSettings:GOFFset:CTE:LENergy:LE1M -1,-1,-1
// *****************************************************************************
// Specify CTE type AoD 2 μs and number of CTE units.
// *****************************************************************************
CONFigure:BLUetooth:SIGN:CONNection:PACKets:TYPE:CTE:LENergy:LE1M AOD2us
CONFigure:BLUetooth:SIGN:CONNection:PACKets:UNITs:CTE:LENergy:LE1M 20
// *****************************************************************************
// Configure an IQ samples coherency measurements on LE 1M PHY: number of EUT
// reports, number of test packets to be measured and the limits per antenna.
// *****************************************************************************
CONF:BLU:SIGN:RXQ:IQCoherency:NOMeas:LENergy:LE1M:A0Reference 10E+3
CONF:BLU:SIGN:RXQ:IQCoherency:NOMeas:LENergy:LE1M:A1NReference 10E+3
CONF:BLU:SIGN:RXQ:IQCoherency:NOMeas:LENergy:LE1M:A2NReference 10E+3
CONF:BLU:SIGN:RXQ:IQCoherency:NOMeas:LENergy:LE1M:A3NReference 10E+3
CONF:BLU:SIGN:RXQ:IQCoherency:PACKets:LENergy:LE1M 50E+3
CONF:BLU:SIGN:RXQ:IQCoherency:LIMit:LENergy:LE1M:A0Reference 1.125,ON
CONF:BLU:SIGN:RXQ:IQCoherency:LIMit:LENergy:LE1M:A1NReference 1.125,ON
CONF:BLU:SIGN:RXQ:IQCoherency:LIMit:LENergy:LE1M:A2NReference 1.125,ON
CONF:BLU:SIGN:RXQ:IQCoherency:LIMit:LENergy:LE1M:A3NReference 1.125,ON
// *****************************************************************************
// Configure an IQ samples dynamic range measurements on LE 1M PHY: number of
// EUT reports, number of test packets to be measured and the limit.
// *****************************************************************************
CONF:BLU:SIGN:RXQ:IQDRange:NOMeas:LENergy:LE1M:A0Reference 10E+3
CONF:BLU:SIGN:RXQ:IQDRange:NOMeas:LENergy:LE1M:A1NReference 10E+3
CONF:BLU:SIGN:RXQ:IQDRange:NOMeas:LENergy:LE1M:A2NReference 10E+3
CONF:BLU:SIGN:RXQ:IQDRange:NOMeas:LENergy:LE1M:A3NReference 10E+3
CONF:BLU:SIGN:RXQ:IQDRange:PACKets:LENergy:LE1M 50E+3
CONF:BLU:SIGN:RXQ:IQDRange:LIMit:LENergy:LE1M ON,ON,ON,ON
● Connect EUT (see Chapter 2.2.2.3, "Test with Multiple EUT's Antennas (LE with
CTE)", on page 17)
● Configure USB connection parameters. Refer to Chapter 2.4.6, "Configure USB
Interface", on page 103.
// *****************************************************************************
// Switch instrument to standby state
// Reset EUT, verify the connection for direct test.
// *****************************************************************************
SOURce:BLUetooth:SIGN:STATe ON
CALL:BLUetooth:SIGN:LENergy:RESet
CALL:BLUetooth:SIGN:CONNection:CHECk:LENergy?
// *****************************************************************************
// Start IQ sample coherency measurement, return trace and statistical
// results for LE 1M PHY.
// Query the measurement state (should be "RDY").
// *****************************************************************************
INIT:BLUetooth:SIGN:RXQuality:IQCoherency
FETCh:BLUetooth:SIGN:RXQuality:TRACe:IQCoherency:A0Reference?
FETCh:BLUetooth:SIGN:RXQuality:TRACe:IQCoherency:A1NReference?
FETCh:BLUetooth:SIGN:RXQuality:TRACe:IQCoherency:A2NReference?
FETCh:BLUetooth:SIGN:RXQuality:TRACe:IQCoherency:A3NReference?
FETCh:BLUetooth:SIGN:RXQuality:IQCoherency:LENergy:LE1M:A0Reference?
FETCh:BLUetooth:SIGN:RXQuality:IQCoherency:LENergy:LE1M:A1NReference?
FETCh:BLUetooth:SIGN:RXQuality:IQCoherency:LENergy:LE1M:A2NReference?
FETCh:BLUetooth:SIGN:RXQuality:IQCoherency:LENergy:LE1M:A3NReference?
CALCulate:BLUetooth:SIGN:RXQuality:IQCoherency:LENergy:LE1M:A0Reference?
CALCulate:BLUetooth:SIGN:RXQuality:IQCoherency:LENergy:LE1M:A1NReference?
CALCulate:BLUetooth:SIGN:RXQuality:IQCoherency:LENergy:LE1M:A2NReference?
CALCulate:BLUetooth:SIGN:RXQuality:IQCoherency:LENergy:LE1M:A3NReference?
FETCh:BLUetooth:SIGN:RXQuality:IQCoherency:STATe?
// *****************************************************************************
// Start IQ sample dynamic range measurement, return results for LE 1M PHY.
// Query the measurement state (should be "RDY").
// *****************************************************************************
INIT:BLUetooth:SIGN:RXQuality:IQDRange
FETCh:BLUetooth:SIGN:RXQuality:IQDRange:LENergy:LE1M:A0Reference?
FETCh:BLUetooth:SIGN:RXQuality:IQDRange:LENergy:LE1M:A1NReference?
FETCh:BLUetooth:SIGN:RXQuality:IQDRange:LENergy:LE1M:A2NReference?
FETCh:BLUetooth:SIGN:RXQuality:IQDRange:LENergy:LE1M:A3NReference?
CALCulate:BLUetooth:SIGN:RXQuality:IQDRange:LENergy:LE1M:A0Reference?
CALCulate:BLUetooth:SIGN:RXQuality:IQDRange:LENergy:LE1M:A1NReference?
CALCulate:BLUetooth:SIGN:RXQuality:IQDRange:LENergy:LE1M:A2NReference?
CALCulate:BLUetooth:SIGN:RXQuality:IQDRange:LENergy:LE1M:A3NReference?
FETCh:BLUetooth:SIGN:RXQuality:IQDRange:STATe?
CONFigure:BLUetooth:SIGN<i>:RXQuality:IBLength:LENergy:LE2M <Enable>,
<InterBurstLen>
CONFigure:BLUetooth:SIGN<i>:RXQuality:IBLength:LENergy:LE1M <Enable>,
<InterBurstLen>
Enables and sets the number of slots to wait between transmissions for direction find-
ing tests.
Parameters:
<Enable> OFF | ON
*RST: OFF
<InterBurstLen> integer
Range: 0 slot(s) to 255 slot(s)
*RST: 10 slot(s)
Firmware/Software: V3.7.90
Options: R&S CMW-KS722
Manual operation: See "Inter Burst Length" on page 297
CONFigure:BLUetooth:SIGN<i>:RXQuality:ITENd:LENergy:LE2M
<IgnoreTestEnd>
CONFigure:BLUetooth:SIGN<i>:RXQuality:ITENd:LENergy:LE1M
<IgnoreTestEnd>
Specifies, whether the R&S CMW ignores the DUT´s response to end of direction find-
ing tests.
Parameters:
<IgnoreTestEnd> OFF | ON
*RST: OFF
Firmware/Software: V3.7.90
Options: R&S CMW-KS722
Manual operation: See "Ignore Test End Response" on page 297
CONFigure:BLUetooth:SIGN<i>:RXQuality:IQSDump <DumpIQPairs>
Enables or disables dumping of the Rx IQ events received from the EUT via HCI.
Parameters:
<DumpIQPairs> OFF | ON
*RST: OFF
Example: See Performing a Direction Finding Rx Measurement.
Firmware/Software: V3.7.81
Options: R&S CMW-KS722
Manual operation: See "Dump DF IQ Sample Pairs" on page 300
The following chapters describe the commands related to the IQ samples coherency
Rx measurements.
● Measurement Control and States......................................................................... 306
● Measurement Settings.......................................................................................... 307
● Measurement Results........................................................................................... 311
The following commands control the measurement and return the current measure-
ment state.
INITiate:BLUetooth:SIGN<i>:RXQuality:IQCoherency........................................................ 306
STOP:BLUetooth:SIGN<i>:RXQuality:IQCoherency.......................................................... 306
ABORt:BLUetooth:SIGN<i>:RXQuality:IQCoherency......................................................... 306
FETCh:BLUetooth:SIGN<i>:RXQuality:IQCoherency:STATe?............................................. 307
INITiate:BLUetooth:SIGN<i>:RXQuality:IQCoherency
STOP:BLUetooth:SIGN<i>:RXQuality:IQCoherency
ABORt:BLUetooth:SIGN<i>:RXQuality:IQCoherency
Starts, stops, or aborts the measurement:
● INITiate... starts or restarts the measurement. The measurement enters the
"RUN" state.
● STOP... halts the measurement immediately. The measurement enters the "RDY"
state. Measurement results are kept. The resources remain allocated to the mea-
surement.
● ABORt... halts the measurement immediately. The measurement enters the
"OFF" state. All measurement values are set to NAV. Allocated resources are
released.
Use FETCh...STATe? to query the current measurement state.
Example: See Performing a Direction Finding Rx Measurement
Usage: Event
Firmware/Software: V3.7.70
FETCh:BLUetooth:SIGN<i>:RXQuality:IQCoherency:STATe?
Queries the main measurement state. Use FETCh:...:STATe:ALL? to query the
measurement state including the substates. Use INITiate..., STOP...,
ABORt... to change the measurement state.
Return values:
<MeasStatus> OFF | RDY | RUN
OFF: measurement switched off, no resources allocated, no
results available (when entered after ABORt...)
RDY: measurement has been terminated, valid results can be
available
RUN: measurement running (after INITiate..., READ...),
synchronization pending or adjusted, resources active or queued
Usage: Query only
Firmware/Software: V3.7.70
Options: R&S CMW-KS722
Manual operation: See "IQ Coherency (Softkey)" on page 290
CONFigure:BLUetooth:SIGN<i>:RXQuality:IQCoherency:LIMit:LENergy:LE1M:
A0Reference....................................................................................................... 310
CONFigure:BLUetooth:SIGN<i>:RXQuality:IQCoherency:LIMit:LENergy:LE2M:
A0Reference....................................................................................................... 310
CONFigure:BLUetooth:SIGN<i>:RXQuality:IQCoherency:LIMit:LENergy:LE1M:
A1NReference.....................................................................................................310
CONFigure:BLUetooth:SIGN<i>:RXQuality:IQCoherency:LIMit:LENergy:LE1M:
A2NReference.....................................................................................................310
CONFigure:BLUetooth:SIGN<i>:RXQuality:IQCoherency:LIMit:LENergy:LE1M:
A3NReference.....................................................................................................310
CONFigure:BLUetooth:SIGN<i>:RXQuality:IQCoherency:LIMit:LENergy:LE2M:
A1NReference.....................................................................................................310
CONFigure:BLUetooth:SIGN<i>:RXQuality:IQCoherency:LIMit:LENergy:LE2M:
A2NReference.....................................................................................................310
CONFigure:BLUetooth:SIGN<i>:RXQuality:IQCoherency:LIMit:LENergy:LE2M:
A3NReference.....................................................................................................310
CONFigure:BLUetooth:SIGN<i>:RXQuality:IQCoherency:MOEXception:LENergy:
LE1M <MeasOnException>
CONFigure:BLUetooth:SIGN<i>:RXQuality:IQCoherency:MOEXception:LENergy:
LE2M <MeasOnException>
Specifies whether measurement results that the R&S CMW identifies as faulty or inac-
curate are rejected.
Commands for uncoded LE 1M PHY (..:LE1M..) and LE 2M PHY (..:LE2M..) are
available.
Parameters:
<MeasOnException> OFF | ON
OFF: Faulty results are rejected
ON: Results are never rejected
*RST: OFF
Firmware/Software: V3.7.90
Options: R&S CMW-KS722
Manual operation: See "Measure on Exception" on page 298
CONFigure:BLUetooth:SIGN<i>:RXQuality:IQCoherency:NOMeas:LENergy:
LE1M:A0Reference <NoOfMeas>
CONFigure:BLUetooth:SIGN<i>:RXQuality:IQCoherency:NOMeas:LENergy:
LE1M:A1NReference <NoOfMeas>
CONFigure:BLUetooth:SIGN<i>:RXQuality:IQCoherency:NOMeas:LENergy:
LE1M:A2NReference <NoOfMeas>
CONFigure:BLUetooth:SIGN<i>:RXQuality:IQCoherency:NOMeas:LENergy:
LE1M:A3NReference <NoOfMeas>
CONFigure:BLUetooth:SIGN<i>:RXQuality:IQCoherency:NOMeas:LENergy:
LE2M:A0Reference <NoOfMeas>
CONFigure:BLUetooth:SIGN<i>:RXQuality:IQCoherency:NOMeas:LENergy:
LE2M:A1NReference <NoOfMeas>
CONFigure:BLUetooth:SIGN<i>:RXQuality:IQCoherency:NOMeas:LENergy:
LE2M:A2NReference <NoOfMeas>
CONFigure:BLUetooth:SIGN<i>:RXQuality:IQCoherency:NOMeas:LENergy:
LE2M:A3NReference <NoOfMeas>
Specifies the minimal number of IQ samples to be reported by the EUT for the speci-
fied antenna.
Commands for uncoded LE 1M PHY (..:LE1M..) and LE 2M PHY (..:LE2M..) are
available.
Commands for reference antenna (...:A0Reference), mandatory second antenna
(...:A1NReference), and optional third and fourth antennas are available.
Parameters:
<NoOfMeas> numeric
Range: 1 to 30E+3
*RST: 10E+3
Example: See Configuring a Direction Finding Rx Measurement
Firmware/Software: V3.7.70
Options: R&S CMW-KS722
CONFigure:BLUetooth:SIGN<i>:RXQuality:IQCoherency:PACKets:LENergy:
LE1M <Packets>
CONFigure:BLUetooth:SIGN<i>:RXQuality:IQCoherency:PACKets:LENergy:
LE2M <Packets>
Defines the number of packets to be sent per measurement cycle (statistics cycle).
Commands for uncoded LE 1M PHY (..:LE1M..) and LE 2M PHY (..:LE2M..) are
available.
Parameters:
<Packets> numeric
Range: 1 to 6.4E+6
*RST: 50E+3
Example: See Configuring a Direction Finding Rx Measurement
Firmware/Software: V3.7.70, V3.7.90: range extended
Options: R&S CMW-KS722
Manual operation: See "Packets" on page 298
CONFigure:BLUetooth:SIGN<i>:RXQuality:IQCoherency:LIMit:LENergy:LE1M:
A0Reference <Limit>, <Enable>
CONFigure:BLUetooth:SIGN<i>:RXQuality:IQCoherency:LIMit:LENergy:LE2M:
A0Reference <Limit>, <Enable>
Defines the IQ samples coherency limit for mean reference phase deviation (RPD)
results for the reference antenna.
Commands for uncoded LE 1M PHY (..:LE1M..) and LE 2M PHY (..:LE2M..) are
available.
Parameters:
<Limit> numeric
Range: 0 (Rad) to 3.14 (Rad)
*RST: 1.125 (Rad)
<Enable> OFF | ON
Disables/enables the limit check
*RST: ON
Example: See Configuring a Direction Finding Rx Measurement
Firmware/Software: V3.7.70, V3.7.80: added <Enable>, V3.7.90: limits enabled per
default
Options: R&S CMW-KS722
Manual operation: See "Limits" on page 299
CONFigure:BLUetooth:SIGN<i>:RXQuality:IQCoherency:LIMit:LENergy:LE1M:
A1NReference <Limit>, <Enable>
CONFigure:BLUetooth:SIGN<i>:RXQuality:IQCoherency:LIMit:LENergy:LE1M:
A2NReference <Limit>, <Enable>
CONFigure:BLUetooth:SIGN<i>:RXQuality:IQCoherency:LIMit:LENergy:LE1M:
A3NReference <Limit>, <Enable>
CONFigure:BLUetooth:SIGN<i>:RXQuality:IQCoherency:LIMit:LENergy:LE2M:
A1NReference <Limit>, <Enable>
CONFigure:BLUetooth:SIGN<i>:RXQuality:IQCoherency:LIMit:LENergy:LE2M:
A2NReference <Limit>, <Enable>
CONFigure:BLUetooth:SIGN<i>:RXQuality:IQCoherency:LIMit:LENergy:LE2M:
A3NReference <Limit>, <Enable>
Defines the IQ samples coherency limit for 95% relative phase values RP(m) for non-
reference antennas A1NReference to A3NReference.
Commands for uncoded LE 1M PHY (..:LE1M..) and LE 2M PHY (..:LE2M..) are
available.
Parameters:
<Limit> numeric
Range: 0 (Rad) to 3.14 (Rad)
*RST: 1.125 (Rad)
<Enable> OFF | ON
Disables/enables the limit check
*RST: ON
Example: See Configuring a Direction Finding Rx Measurement
Firmware/Software: V3.7.70, V3.7.80: added <Enable>, V3.7.90: limits enabled per
default
Options: R&S CMW-KS722
CALCulate:BLUetooth:SIGN<i>:RXQuality:IQCoherency:LENergy:LE1M:
A0Reference?
CALCulate:BLUetooth:SIGN<i>:RXQuality:IQCoherency:LENergy:LE2M:
A0Reference?
FETCh:BLUetooth:SIGN<i>:RXQuality:IQCoherency:LENergy:LE1M:
A0Reference?
FETCh:BLUetooth:SIGN<i>:RXQuality:IQCoherency:LENergy:LE2M:
A0Reference?
READ:BLUetooth:SIGN<i>:RXQuality:IQCoherency:LENergy:LE1M:
A0Reference?
READ:BLUetooth:SIGN<i>:RXQuality:IQCoherency:LENergy:LE2M:
A0Reference?
Return the results of IQ samples coherency RPD measurements for the reference
antenna.
Commands for uncoded LE 1M PHY (..:LE1M..) and LE 2M PHY (..:LE2M..) are
available.
The values described below are returned by FETCh and READ commands. CALCulate
commands return limit check results instead, one value for each result listed below.
Return values:
<1_Reliability> decimal
See Reliability Indicator
<2_TransPackets> decimal
No. of transmitted packets
Range: 0 to 200E+6
<3_RecPackets> float
Percentage of received events related to transmitted packets
Range: 0 % to 100 %
Default unit: %
<4_EventsValCRC> decimal
Percentage of received events with valid CRC related to trans-
mitted packets
Range: 0 % to 100 %
Default unit: %
<5_NoValidIQPairs> decimal
No. of received valid IQ sample pairs
<6_ValidIQPairsRec> float
Percentage of received valid IQ sample pairs related to all
received IQ pairs
<7_MeanPhaseDiff> float
Mean current phase difference
Default unit: rad/π
<8_RecEventsCnt> decimal
No. of received events
<9_ProEventsCnt> decimal
No. of processed events
<10_ProEveValCrc> decimal
No. of processed events with valid CRC
<11_NofPosPha> decimal
No. of possible phase measurements determined by CTE
length, slot length and number of antennas
<12_MRPDavg> float
Mean reference phase deviation (RPD) - average value
<13_MRPDmin> float
Mean RPD - minimum value
<14_MRPDmax> float
Mean RPD - maximum value
Example: See Performing a Direction Finding Rx Measurement
Usage: Query only
Firmware/Software: V3.7.70, V3.7.90: added parameters <8_RecEventsCnt> to
<14_MRPDmax>
Options: R&S CMW-KS722
CALCulate:BLUetooth:SIGN<i>:RXQuality:IQCoherency:LENergy:LE1M:
A1NReference?
CALCulate:BLUetooth:SIGN<i>:RXQuality:IQCoherency:LENergy:LE1M:
A2NReference?
CALCulate:BLUetooth:SIGN<i>:RXQuality:IQCoherency:LENergy:LE1M:
A3NReference?
CALCulate:BLUetooth:SIGN<i>:RXQuality:IQCoherency:LENergy:LE2M:
A1NReference?
CALCulate:BLUetooth:SIGN<i>:RXQuality:IQCoherency:LENergy:LE2M:
A2NReference?
CALCulate:BLUetooth:SIGN<i>:RXQuality:IQCoherency:LENergy:LE2M:
A3NReference?
FETCh:BLUetooth:SIGN<i>:RXQuality:IQCoherency:LENergy:LE1M:
A1NReference?
FETCh:BLUetooth:SIGN<i>:RXQuality:IQCoherency:LENergy:LE1M:
A2NReference?
FETCh:BLUetooth:SIGN<i>:RXQuality:IQCoherency:LENergy:LE1M:
A3NReference?
FETCh:BLUetooth:SIGN<i>:RXQuality:IQCoherency:LENergy:LE2M:
A1NReference?
FETCh:BLUetooth:SIGN<i>:RXQuality:IQCoherency:LENergy:LE2M:
A2NReference?
FETCh:BLUetooth:SIGN<i>:RXQuality:IQCoherency:LENergy:LE2M:
A3NReference?
READ:BLUetooth:SIGN<i>:RXQuality:IQCoherency:LENergy:LE1M:
A1NReference?
READ:BLUetooth:SIGN<i>:RXQuality:IQCoherency:LENergy:LE1M:
A2NReference?
READ:BLUetooth:SIGN<i>:RXQuality:IQCoherency:LENergy:LE1M:
A3NReference?
READ:BLUetooth:SIGN<i>:RXQuality:IQCoherency:LENergy:LE2M:
A1NReference?
READ:BLUetooth:SIGN<i>:RXQuality:IQCoherency:LENergy:LE2M:
A2NReference?
READ:BLUetooth:SIGN<i>:RXQuality:IQCoherency:LENergy:LE2M:
A3NReference?
Returns the results of IQ samples coherency RP(m) measurement for the specified
non-reference antenna.
Commands for uncoded LE 1M PHY (..:LE1M..) and LE 2M PHY (..:LE2M..) are
available.
Commands for the mandatory non-reference antenna (...:A1NReference), and
optional third (...:A2NReference) and fourth (...:A3NReference) antennas are
available.
The values described below are returned by FETCh and READ commands. CALCulate
commands return limit check results instead, one value for each result listed below.
Return values:
<1_Reliability> decimal
See Reliability Indicator
<2_TransPackets> decimal
No. of transmitted packets
Range: 0 to 200E+6
<3_RecPackets> float
Percentage of received events related to transmitted packets
Range: 0 % to 100 %
Default unit: %
<4_EventsValCRC> decimal
Percentage of received events with valid CRC related to trans-
mitted packets
Range: 0 % to 100 %
Default unit: %
<5_NoValidIQPairs> decimal
No. of received valid IQ sample pairs
<6_ValidIQPairsRec> float
Percentage of received valid IQ sample pairs related to all
received IQ pairs
<7_MeanRelPhase> float
Mean current relative phase RP(m)
Default unit: rad/π
<8_P95_MPhDev> float
95% of mean RP(m) range
Default unit: rad/π
<9_RecEventsCnt> decimal
No. of received events
<10_ProEventsCnt> decimal
No. of processed events
<11_ProEveValCrc> decimal
No. of processed events with valid CRC
<12_NofPosPha> decimal
No. of possible phase measurements determined by CTE
length, slot length and number of antennas
Example: See Performing a Direction Finding Rx Measurement
Usage: Query only
Firmware/Software: V3.7.70, V3.7.90: added parameters <9_RecEventsCnt> to
<12_NofPosPha>
Options: R&S CMW-KS722
FETCh:BLUetooth:SIGN<i>:RXQuality:TRACe:IQCoherency:A0Reference?
READ:BLUetooth:SIGN<i>:RXQuality:TRACe:IQCoherency:A0Reference?
Return the trace results of reference phase deviation RPD for IQ samples coherency
measured at antenna 0.
Return values:
<1_Reliability> decimal
See Reliability Indicator
<2_RPD>... float
<721_RPD> 720 RPD results, one result per IQ sample slot.
Example: See Performing a Direction Finding Rx Measurement
Usage: Query only
Firmware/Software: V3.7.70
Options: R&S CMW-KS722
FETCh:BLUetooth:SIGN<i>:RXQuality:TRACe:IQCoherency:A1NReference?
FETCh:BLUetooth:SIGN<i>:RXQuality:TRACe:IQCoherency:A2NReference?
FETCh:BLUetooth:SIGN<i>:RXQuality:TRACe:IQCoherency:A3NReference?
READ:BLUetooth:SIGN<i>:RXQuality:TRACe:IQCoherency:A1NReference?
READ:BLUetooth:SIGN<i>:RXQuality:TRACe:IQCoherency:A2NReference?
READ:BLUetooth:SIGN<i>:RXQuality:TRACe:IQCoherency:A3NReference?
Return the trace results of relative phase values RP(m) for IQ samples coherency Rx
measurements.
Commands for mandatory second (non-reference) antenna (...:A1NReference),
and optional third and fourth non-reference antennas are available.
Return values:
<Reliability> decimal
See Reliability Indicator
<RP(1)>... <RP(720)> float
720 RP(m) results, one result per IQ sample slot.
Example: See Performing a Direction Finding Rx Measurement
Usage: Query only
Firmware/Software: V3.7.70
Options: R&S CMW-KS722
The following chapters describe the commands related to the IQ samples dynamic
range Rx measurements.
● Measurement Control and States......................................................................... 316
● Measurement Settings.......................................................................................... 318
● Measurement Results........................................................................................... 320
The following commands control the measurement and return the current measure-
ment state.
CONFigure:BLUetooth:SIGN<i>:RXQuality:IQDRange:MOEXception:LENergy:LE1M........... 317
CONFigure:BLUetooth:SIGN<i>:RXQuality:IQDRange:MOEXception:LENergy:LE2M........... 317
INITiate:BLUetooth:SIGN<i>:RXQuality:IQDRange............................................................317
STOP:BLUetooth:SIGN<i>:RXQuality:IQDRange.............................................................. 317
ABORt:BLUetooth:SIGN<i>:RXQuality:IQDRange............................................................. 317
FETCh:BLUetooth:SIGN<i>:RXQuality:IQDRange:STATe?.................................................318
CONFigure:BLUetooth:SIGN<i>:RXQuality:IQDRange:MOEXception:LENergy:
LE1M <MeasOnException>
CONFigure:BLUetooth:SIGN<i>:RXQuality:IQDRange:MOEXception:LENergy:
LE2M <MeasOnException>
Specifies whether measurement results that the R&S CMW identifies as faulty or inac-
curate are rejected.
Commands for uncoded LE 1M PHY (..:LE1M..) and LE 2M PHY (..:LE2M..) are
available.
Parameters:
<MeasOnException> OFF | ON
OFF: Faulty results are rejected
ON: Results are never rejected
*RST: OFF
Firmware/Software: V3.7.90
Options: R&S CMW-KS722
Manual operation: See "Measure on Exception" on page 298
INITiate:BLUetooth:SIGN<i>:RXQuality:IQDRange
STOP:BLUetooth:SIGN<i>:RXQuality:IQDRange
ABORt:BLUetooth:SIGN<i>:RXQuality:IQDRange
Starts, stops, or aborts the measurement:
● INITiate... starts or restarts the measurement. The measurement enters the
"RUN" state.
● STOP... halts the measurement immediately. The measurement enters the "RDY"
state. Measurement results are kept. The resources remain allocated to the mea-
surement.
● ABORt... halts the measurement immediately. The measurement enters the
"OFF" state. All measurement values are set to NAV. Allocated resources are
released.
Use FETCh...STATe? to query the current measurement state.
Example: See Performing a Direction Finding Rx Measurement
Usage: Event
Firmware/Software: V3.7.70
Options: R&S CMW-KS722
Manual operation: See "IQ Dynamic Range (Softkey)" on page 290
FETCh:BLUetooth:SIGN<i>:RXQuality:IQDRange:STATe?
Queries the main measurement state. Use FETCh:...:STATe:ALL? to query the
measurement state including the substates. Use INITiate..., STOP...,
ABORt... to change the measurement state.
Return values:
<MeasStatus> OFF | RDY | RUN
OFF: measurement switched off, no resources allocated, no
results available (when entered after ABORt...)
RDY: measurement has been terminated, valid results can be
available
RUN: measurement running (after INITiate..., READ...),
synchronization pending or adjusted, resources active or queued
Usage: Query only
Firmware/Software: V3.7.70
Options: R&S CMW-KS722
Manual operation: See "IQ Dynamic Range (Softkey)" on page 290
CONFigure:BLUetooth:SIGN<i>:RXQuality:IQDRange:NOMeas:LENergy:LE1M:
A0Reference <NoOfMeas>
CONFigure:BLUetooth:SIGN<i>:RXQuality:IQDRange:NOMeas:LENergy:LE1M:
A1NReference <NoOfMeas>
CONFigure:BLUetooth:SIGN<i>:RXQuality:IQDRange:NOMeas:LENergy:LE1M:
A2NReference <NoOfMeas>
CONFigure:BLUetooth:SIGN<i>:RXQuality:IQDRange:NOMeas:LENergy:LE1M:
A3NReference <NoOfMeas>
CONFigure:BLUetooth:SIGN<i>:RXQuality:IQDRange:NOMeas:LENergy:LE2M:
A0Reference <NoOfMeas>
CONFigure:BLUetooth:SIGN<i>:RXQuality:IQDRange:NOMeas:LENergy:LE2M:
A1NReference <NoOfMeas>
CONFigure:BLUetooth:SIGN<i>:RXQuality:IQDRange:NOMeas:LENergy:LE2M:
A2NReference <NoOfMeas>
CONFigure:BLUetooth:SIGN<i>:RXQuality:IQDRange:NOMeas:LENergy:LE2M:
A3NReference <NoOfMeas>
Defines the number of measurements per measurement cycle for the specified
antenna.
Commands for uncoded LE 1M PHY (..:LE1M..) and LE 2M PHY (..:LE2M..) are
available.
Commands for reference antenna (...:A0Reference), mandatory second antenna
(...:A1NReference), and optional third and fourth antennas are available.
Parameters:
<NoOfMeas> numeric
Range: 0 to 30E+3
*RST: 10E+3
Example: See Configuring a Direction Finding Rx Measurement
Firmware/Software: V3.7.80, V3.7.90: range extended - now from zero
Options: R&S CMW-KS722
CONFigure:BLUetooth:SIGN<i>:RXQuality:IQDRange:PACKets:LENergy:LE1M
<Packets>
CONFigure:BLUetooth:SIGN<i>:RXQuality:IQDRange:PACKets:LENergy:LE2M
<Packets>
Defines the number of packets to be sent per measurement cycle (statistics cycle).
Commands for uncoded LE 1M PHY (..:LE1M..) and LE 2M PHY (..:LE2M..) are
available.
Parameters:
<Packets> numeric
Range: 1 to 6.4E+6
*RST: 50E+3
Example: See Configuring a Direction Finding Rx Measurement
CONFigure:BLUetooth:SIGN<i>:RXQuality:IQDRange:ANTMeanamp:LIMit:
LENergy:LE1M <Ant3Minus2Enable>, <Ant2MinusRefEnable>,
<AntRefMinus1Enable>
CONFigure:BLUetooth:SIGN<i>:RXQuality:IQDRange:ANTMeanamp:LIMit:
LENergy:LE2M <Ant3Minus2Enable>, <Ant2MinusRefEnable>,
<AntRefMinus1Enable>
Disables/enables the limit check for the IQ dynamic range results to monitor the
requirement: MeanANT3 < MeanANT2 < MeanANT0 < MeanANT1
Parameters:
<Ant3-Ant2Enable> OFF | ON
Limit for (MeanAmplitudeANT3 - MeanAmplitudeANT2)
*RST: ON
<Ant2-AntRefEnable> OFF | ON
Limit for (MeanAmplitudeANT2 - MeanAmplitudeANT0)
*RST: ON
<AntRef-Ant1Enable> OFF | ON
Limit for (MeanAmplitudeANT0 - MeanAmplitudeANT1)
*RST: ON
Firmware/Software: V3.7.90
Options: R&S CMMW-KS722
Manual operation: See "Limits" on page 299
FETCh:BLUetooth:SIGN<i>:RXQuality:IQDRange:LENergy:LE2M:A1NReference?.............. 321
FETCh:BLUetooth:SIGN<i>:RXQuality:IQDRange:LENergy:LE2M:A2NReference?.............. 321
FETCh:BLUetooth:SIGN<i>:RXQuality:IQDRange:LENergy:LE2M:A3NReference?.............. 321
READ:BLUetooth:SIGN<i>:RXQuality:IQDRange:LENergy:LE1M:A1?.................................321
READ:BLUetooth:SIGN<i>:RXQuality:IQDRange:LENergy:LE1M:A1NReference?............... 321
READ:BLUetooth:SIGN<i>:RXQuality:IQDRange:LENergy:LE1M:A2?.................................322
READ:BLUetooth:SIGN<i>:RXQuality:IQDRange:LENergy:LE1M:A2NReference?............... 322
READ:BLUetooth:SIGN<i>:RXQuality:IQDRange:LENergy:LE1M:A3?.................................322
READ:BLUetooth:SIGN<i>:RXQuality:IQDRange:LENergy:LE1M:A3NReference?............... 322
READ:BLUetooth:SIGN<i>:RXQuality:IQDRange:LENergy:LE2M:A0Reference?..................322
READ:BLUetooth:SIGN<i>:RXQuality:IQDRange:LENergy:LE2M:A1?.................................322
READ:BLUetooth:SIGN<i>:RXQuality:IQDRange:LENergy:LE2M:A1NReference?............... 322
READ:BLUetooth:SIGN<i>:RXQuality:IQDRange:LENergy:LE2M:A2?.................................322
READ:BLUetooth:SIGN<i>:RXQuality:IQDRange:LENergy:LE2M:A2NReference?............... 322
READ:BLUetooth:SIGN<i>:RXQuality:IQDRange:LENergy:LE2M:A3?.................................322
READ:BLUetooth:SIGN<i>:RXQuality:IQDRange:LENergy:LE2M:A3NReference?............... 322
CALCulate:BLUetooth:SIGN<i>:RXQuality:IQDRange:ANTMeanamp:LENergy:LE1M?......... 323
CALCulate:BLUetooth:SIGN<i>:RXQuality:IQDRange:ANTMeanamp:LENergy:LE2M?......... 323
FETCh:BLUetooth:SIGN<i>:RXQuality:IQDRange:ANTMeanamp:LENergy:LE1M?.............. 323
FETCh:BLUetooth:SIGN<i>:RXQuality:IQDRange:ANTMeanamp:LENergy:LE2M?.............. 323
READ:BLUetooth:SIGN<i>:RXQuality:IQDRange:ANTMeanamp:LENergy:LE1M?................323
READ:BLUetooth:SIGN<i>:RXQuality:IQDRange:ANTMeanamp:LENergy:LE2M?................323
CALCulate:BLUetooth:SIGN<i>:RXQuality:IQDRange:LENergy:LE1M:
A0Reference?
CALCulate:BLUetooth:SIGN<i>:RXQuality:IQDRange:LENergy:LE1M:
A1NReference?
CALCulate:BLUetooth:SIGN<i>:RXQuality:IQDRange:LENergy:LE1M:
A2NReference?
CALCulate:BLUetooth:SIGN<i>:RXQuality:IQDRange:LENergy:LE1M:
A3NReference?
CALCulate:BLUetooth:SIGN<i>:RXQuality:IQDRange:LENergy:LE2M:
A0Reference?
CALCulate:BLUetooth:SIGN<i>:RXQuality:IQDRange:LENergy:LE2M:
A1NReference?
CALCulate:BLUetooth:SIGN<i>:RXQuality:IQDRange:LENergy:LE2M:
A2NReference?
CALCulate:BLUetooth:SIGN<i>:RXQuality:IQDRange:LENergy:LE2M:
A3NReference?
FETCh:BLUetooth:SIGN<i>:RXQuality:IQDRange:LENergy:LE1M:A0Reference?
FETCh:BLUetooth:SIGN<i>:RXQuality:IQDRange:LENergy:LE1M:A1NReference?
FETCh:BLUetooth:SIGN<i>:RXQuality:IQDRange:LENergy:LE1M:A2NReference?
FETCh:BLUetooth:SIGN<i>:RXQuality:IQDRange:LENergy:LE1M:A3NReference?
FETCh:BLUetooth:SIGN<i>:RXQuality:IQDRange:LENergy:LE2M:A0Reference?
FETCh:BLUetooth:SIGN<i>:RXQuality:IQDRange:LENergy:LE2M:A1NReference?
FETCh:BLUetooth:SIGN<i>:RXQuality:IQDRange:LENergy:LE2M:A2NReference?
FETCh:BLUetooth:SIGN<i>:RXQuality:IQDRange:LENergy:LE2M:A3NReference?
READ:BLUetooth:SIGN<i>:RXQuality:IQDRange:LENergy:LE1M:A1?
READ:BLUetooth:SIGN<i>:RXQuality:IQDRange:LENergy:LE1M:A1NReference?
READ:BLUetooth:SIGN<i>:RXQuality:IQDRange:LENergy:LE1M:A2?
READ:BLUetooth:SIGN<i>:RXQuality:IQDRange:LENergy:LE1M:A2NReference?
READ:BLUetooth:SIGN<i>:RXQuality:IQDRange:LENergy:LE1M:A3?
READ:BLUetooth:SIGN<i>:RXQuality:IQDRange:LENergy:LE1M:A3NReference?
READ:BLUetooth:SIGN<i>:RXQuality:IQDRange:LENergy:LE2M:A0Reference?
READ:BLUetooth:SIGN<i>:RXQuality:IQDRange:LENergy:LE2M:A1?
READ:BLUetooth:SIGN<i>:RXQuality:IQDRange:LENergy:LE2M:A1NReference?
READ:BLUetooth:SIGN<i>:RXQuality:IQDRange:LENergy:LE2M:A2?
READ:BLUetooth:SIGN<i>:RXQuality:IQDRange:LENergy:LE2M:A2NReference?
READ:BLUetooth:SIGN<i>:RXQuality:IQDRange:LENergy:LE2M:A3?
READ:BLUetooth:SIGN<i>:RXQuality:IQDRange:LENergy:LE2M:A3NReference?
Returns the results of IQ dynamic range Rx measurement for the specified antenna.
Commands for uncoded LE 1M PHY (..:LE1M..) and LE 2M PHY (..:LE2M..) are
available.
Commands for reference antenna (...:A0Reference), mandatory second non-refer-
ence antenna (...:A1NReference), and optional third and fourth non-reference
antennas are available.
The values described below are returned by FETCh and READ commands. CALCulate
commands return limit check results instead, one value for each result listed below.
Return values:
<1_Reliability> decimal
See Reliability Indicator
<2_TransPackets> decimal
No. of transmitted packets
Range: 0 to 200E+6
<3_RecPackets> float
Percentage of received events related to transmitted packets
Range: 0 % to 100 %
Default unit: %
<4_EventsValCRC> decimal
Percentage of received events with valid CRC related to trans-
mitted packets
Range: 0 % to 100 %
Default unit: %
<5_NoValidIQPairs> decimal
No. of valid measurements
Range: 0 to 100E+3
<6_ValidIQPairsRec> float
Percentage of received valid IQ sample pairs related to all
received IQ pairs
Range: 0 % to 100 %
Default unit: %
<7_MeanAmplitude> float
Mean amplitude
Range: 0 to 1
Default unit: dBFS
<8_MaxAmplitude> float
Max amplitude
Range: 0 to 1
Default unit: dBFS
<9_RecEventsCnt> decimal
No. of received events
<10_ProEventsCnt> decimal
No. of processed events
<11_ProEveValCrc> decimal
No. of received events with valid CRC
<12_NofPosAmp> decimal
No. of possible amplitude measurements determined by CTE
length, slot length and number of antennas
Example: See Performing a Direction Finding Rx Measurement
Usage: Query only
Firmware/Software: V3.7.70
V3.7.90: added parameters <9_RecEventsCnt> to
<12_NofPosAmp>
Options: R&S CMW-KS722
CALCulate:BLUetooth:SIGN<i>:RXQuality:IQDRange:ANTMeanamp:LENergy:
LE1M?
CALCulate:BLUetooth:SIGN<i>:RXQuality:IQDRange:ANTMeanamp:LENergy:
LE2M?
FETCh:BLUetooth:SIGN<i>:RXQuality:IQDRange:ANTMeanamp:LENergy:LE1M?
FETCh:BLUetooth:SIGN<i>:RXQuality:IQDRange:ANTMeanamp:LENergy:LE2M?
READ:BLUetooth:SIGN<i>:RXQuality:IQDRange:ANTMeanamp:LENergy:LE1M?
READ:BLUetooth:SIGN<i>:RXQuality:IQDRange:ANTMeanamp:LENergy:LE2M?
Returns the results of IQ dynamic range Rx measurement for the antenna mean ampli-
tude differences.
Commands for uncoded LE 1M PHY (..:LE1M..) and LE 2M PHY (..:LE2M..) are
available.
The values described below are returned by FETCh and READ commands. CALCulate
commands return limit check results instead, one value for each result listed below.
Return values:
<Reliability> decimal
See Reliability Indicator
<Ant3Minus2> float
MeanAmplitudeANT3 - MeanAmplitudeANT2
Range: -256 to 128
<Ant2MinusRef> float
MeanAmplitudeANT2 - MeanAmplitudeANT0
Range: -256 to 128
<AntRefMinus1> float
MeanAmplitudeANT0 - MeanAmplitudeANT1
Range: -256 to 128
Usage: Query only
Firmware/Software: V3.7.90
Options: R&S CMW-KS722
CONFigure:BLUetooth:SIGN<i>:RXQuality:IQCoherency:LIMit:LENergy:LE1M:A3NReference..................310
CONFigure:BLUetooth:SIGN<i>:RXQuality:IQCoherency:LIMit:LENergy:LE2M:A0Reference.................... 310
CONFigure:BLUetooth:SIGN<i>:RXQuality:IQCoherency:LIMit:LENergy:LE2M:A1NReference..................310
CONFigure:BLUetooth:SIGN<i>:RXQuality:IQCoherency:LIMit:LENergy:LE2M:A2NReference..................310
CONFigure:BLUetooth:SIGN<i>:RXQuality:IQCoherency:LIMit:LENergy:LE2M:A3NReference..................310
CONFigure:BLUetooth:SIGN<i>:RXQuality:IQCoherency:MOEXception:LENergy:LE1M............................ 308
CONFigure:BLUetooth:SIGN<i>:RXQuality:IQCoherency:MOEXception:LENergy:LE2M............................ 308
CONFigure:BLUetooth:SIGN<i>:RXQuality:IQCoherency:NOMeas:LENergy:LE1M:A0Reference.............. 308
CONFigure:BLUetooth:SIGN<i>:RXQuality:IQCoherency:NOMeas:LENergy:LE1M:A1NReference........... 308
CONFigure:BLUetooth:SIGN<i>:RXQuality:IQCoherency:NOMeas:LENergy:LE1M:A2NReference........... 308
CONFigure:BLUetooth:SIGN<i>:RXQuality:IQCoherency:NOMeas:LENergy:LE1M:A3NReference........... 308
CONFigure:BLUetooth:SIGN<i>:RXQuality:IQCoherency:NOMeas:LENergy:LE2M:A0Reference.............. 308
CONFigure:BLUetooth:SIGN<i>:RXQuality:IQCoherency:NOMeas:LENergy:LE2M:A1NReference........... 309
CONFigure:BLUetooth:SIGN<i>:RXQuality:IQCoherency:NOMeas:LENergy:LE2M:A2NReference........... 309
CONFigure:BLUetooth:SIGN<i>:RXQuality:IQCoherency:NOMeas:LENergy:LE2M:A3NReference........... 309
CONFigure:BLUetooth:SIGN<i>:RXQuality:IQCoherency:PACKets:LENergy:LE1M....................................309
CONFigure:BLUetooth:SIGN<i>:RXQuality:IQCoherency:PACKets:LENergy:LE2M....................................309
CONFigure:BLUetooth:SIGN<i>:RXQuality:IQDRange:ANTMeanamp:LIMit:LENergy:LE1M...................... 320
CONFigure:BLUetooth:SIGN<i>:RXQuality:IQDRange:ANTMeanamp:LIMit:LENergy:LE2M...................... 320
CONFigure:BLUetooth:SIGN<i>:RXQuality:IQDRange:MOEXception:LENergy:LE1M................................ 317
CONFigure:BLUetooth:SIGN<i>:RXQuality:IQDRange:MOEXception:LENergy:LE2M................................ 317
CONFigure:BLUetooth:SIGN<i>:RXQuality:IQDRange:NOMeas:LENergy:LE1M:A0Reference.................. 319
CONFigure:BLUetooth:SIGN<i>:RXQuality:IQDRange:NOMeas:LENergy:LE1M:A1NReference................319
CONFigure:BLUetooth:SIGN<i>:RXQuality:IQDRange:NOMeas:LENergy:LE1M:A2NReference................319
CONFigure:BLUetooth:SIGN<i>:RXQuality:IQDRange:NOMeas:LENergy:LE1M:A3NReference................319
CONFigure:BLUetooth:SIGN<i>:RXQuality:IQDRange:NOMeas:LENergy:LE2M:A0Reference.................. 319
CONFigure:BLUetooth:SIGN<i>:RXQuality:IQDRange:NOMeas:LENergy:LE2M:A1NReference................319
CONFigure:BLUetooth:SIGN<i>:RXQuality:IQDRange:NOMeas:LENergy:LE2M:A2NReference................319
CONFigure:BLUetooth:SIGN<i>:RXQuality:IQDRange:NOMeas:LENergy:LE2M:A3NReference................319
CONFigure:BLUetooth:SIGN<i>:RXQuality:IQDRange:PACKets:LENergy:LE1M........................................ 319
CONFigure:BLUetooth:SIGN<i>:RXQuality:IQDRange:PACKets:LENergy:LE2M........................................ 319
CONFigure:BLUetooth:SIGN<i>:RXQuality:IQSDump.................................................................................. 305
CONFigure:BLUetooth:SIGN<i>:RXQuality:ITENd:LENergy:LE1M.............................................................. 305
CONFigure:BLUetooth:SIGN<i>:RXQuality:ITENd:LENergy:LE2M.............................................................. 305
FETCh:BLUetooth:SIGN<i>:RXQuality:IQCoherency:LENergy:LE1M:A0Reference?.................................. 312
FETCh:BLUetooth:SIGN<i>:RXQuality:IQCoherency:LENergy:LE1M:A1NReference?............................... 313
FETCh:BLUetooth:SIGN<i>:RXQuality:IQCoherency:LENergy:LE1M:A2NReference?............................... 313
FETCh:BLUetooth:SIGN<i>:RXQuality:IQCoherency:LENergy:LE1M:A3NReference?............................... 313
FETCh:BLUetooth:SIGN<i>:RXQuality:IQCoherency:LENergy:LE2M:A0Reference?.................................. 312
FETCh:BLUetooth:SIGN<i>:RXQuality:IQCoherency:LENergy:LE2M:A1NReference?............................... 313
FETCh:BLUetooth:SIGN<i>:RXQuality:IQCoherency:LENergy:LE2M:A2NReference?............................... 314
FETCh:BLUetooth:SIGN<i>:RXQuality:IQCoherency:LENergy:LE2M:A3NReference?............................... 314
FETCh:BLUetooth:SIGN<i>:RXQuality:IQCoherency:STATe?...................................................................... 307
FETCh:BLUetooth:SIGN<i>:RXQuality:IQDRange:ANTMeanamp:LENergy:LE1M?.................................... 323
FETCh:BLUetooth:SIGN<i>:RXQuality:IQDRange:ANTMeanamp:LENergy:LE2M?.................................... 323
FETCh:BLUetooth:SIGN<i>:RXQuality:IQDRange:LENergy:LE1M:A0Reference?...................................... 321
FETCh:BLUetooth:SIGN<i>:RXQuality:IQDRange:LENergy:LE1M:A1NReference?....................................321
FETCh:BLUetooth:SIGN<i>:RXQuality:IQDRange:LENergy:LE1M:A2NReference?....................................321
FETCh:BLUetooth:SIGN<i>:RXQuality:IQDRange:LENergy:LE1M:A3NReference?....................................321
FETCh:BLUetooth:SIGN<i>:RXQuality:IQDRange:LENergy:LE2M:A0Reference?...................................... 321
FETCh:BLUetooth:SIGN<i>:RXQuality:IQDRange:LENergy:LE2M:A1NReference?....................................321
FETCh:BLUetooth:SIGN<i>:RXQuality:IQDRange:LENergy:LE2M:A2NReference?....................................321
FETCh:BLUetooth:SIGN<i>:RXQuality:IQDRange:LENergy:LE2M:A3NReference?....................................321
FETCh:BLUetooth:SIGN<i>:RXQuality:IQDRange:STATe?.......................................................................... 318
FETCh:BLUetooth:SIGN<i>:RXQuality:TRACe:IQCoherency:A0Reference?...............................................315
FETCh:BLUetooth:SIGN<i>:RXQuality:TRACe:IQCoherency:A1NReference?............................................ 316
FETCh:BLUetooth:SIGN<i>:RXQuality:TRACe:IQCoherency:A2NReference?............................................ 316
FETCh:BLUetooth:SIGN<i>:RXQuality:TRACe:IQCoherency:A3NReference?............................................ 316
INITiate:BLUetooth:SIGN<i>:RXQuality:IQCoherency.................................................................................. 306
INITiate:BLUetooth:SIGN<i>:RXQuality:IQDRange...................................................................................... 317
READ:BLUetooth:SIGN<i>:RXQuality:IQCoherency:LENergy:LE1M:A0Reference?................................... 312
READ:BLUetooth:SIGN<i>:RXQuality:IQCoherency:LENergy:LE1M:A1NReference?.................................314
READ:BLUetooth:SIGN<i>:RXQuality:IQCoherency:LENergy:LE1M:A2NReference?.................................314
READ:BLUetooth:SIGN<i>:RXQuality:IQCoherency:LENergy:LE1M:A3NReference?.................................314
READ:BLUetooth:SIGN<i>:RXQuality:IQCoherency:LENergy:LE2M:A0Reference?................................... 312
READ:BLUetooth:SIGN<i>:RXQuality:IQCoherency:LENergy:LE2M:A1NReference?.................................314
READ:BLUetooth:SIGN<i>:RXQuality:IQCoherency:LENergy:LE2M:A2NReference?.................................314
READ:BLUetooth:SIGN<i>:RXQuality:IQCoherency:LENergy:LE2M:A3NReference?.................................314
READ:BLUetooth:SIGN<i>:RXQuality:IQDRange:ANTMeanamp:LENergy:LE1M?..................................... 323
READ:BLUetooth:SIGN<i>:RXQuality:IQDRange:ANTMeanamp:LENergy:LE2M?..................................... 323
READ:BLUetooth:SIGN<i>:RXQuality:IQDRange:LENergy:LE1M:A1?........................................................ 321
READ:BLUetooth:SIGN<i>:RXQuality:IQDRange:LENergy:LE1M:A1NReference?..................................... 321
READ:BLUetooth:SIGN<i>:RXQuality:IQDRange:LENergy:LE1M:A2?........................................................ 322
READ:BLUetooth:SIGN<i>:RXQuality:IQDRange:LENergy:LE1M:A2NReference?..................................... 322
READ:BLUetooth:SIGN<i>:RXQuality:IQDRange:LENergy:LE1M:A3?........................................................ 322
READ:BLUetooth:SIGN<i>:RXQuality:IQDRange:LENergy:LE1M:A3NReference?..................................... 322
READ:BLUetooth:SIGN<i>:RXQuality:IQDRange:LENergy:LE2M:A0Reference?........................................322
READ:BLUetooth:SIGN<i>:RXQuality:IQDRange:LENergy:LE2M:A1?........................................................ 322
READ:BLUetooth:SIGN<i>:RXQuality:IQDRange:LENergy:LE2M:A1NReference?..................................... 322
READ:BLUetooth:SIGN<i>:RXQuality:IQDRange:LENergy:LE2M:A2?........................................................ 322
READ:BLUetooth:SIGN<i>:RXQuality:IQDRange:LENergy:LE2M:A2NReference?..................................... 322
READ:BLUetooth:SIGN<i>:RXQuality:IQDRange:LENergy:LE2M:A3?........................................................ 322
READ:BLUetooth:SIGN<i>:RXQuality:IQDRange:LENergy:LE2M:A3NReference?..................................... 322
READ:BLUetooth:SIGN<i>:RXQuality:TRACe:IQCoherency:A0Reference?................................................ 315
READ:BLUetooth:SIGN<i>:RXQuality:TRACe:IQCoherency:A1NReference?............................................. 316
READ:BLUetooth:SIGN<i>:RXQuality:TRACe:IQCoherency:A2NReference?............................................. 316
READ:BLUetooth:SIGN<i>:RXQuality:TRACe:IQCoherency:A3NReference?............................................. 316
STOP:BLUetooth:SIGN<i>:RXQuality:IQCoherency..................................................................................... 306
STOP:BLUetooth:SIGN<i>:RXQuality:IQDRange......................................................................................... 317
7 Bluetooth® Measurements
"Bluetooth Measurement" provides transmitter (Tx) tests for Bluetooth devices and
non-signaling Rx LE measurements with ARB generator. The following figure displays
provided options.
Tx measurements:
● Option R&S CMW-KM610 supports Basic Rate (BR) and Enhanced Data Rate
(EDR) packets transmitter (Tx) measurements.
● Option R&S CMW-KM611 supports Tx measurements for uncoded 1 Msymbol/s
Low Energy (LE 1M) packets.
– Supplementary option R&S CMW-KM721 adds Bluetooth version 5.0 support
for uncoded 2 Msymbol/s LE packets (LE 2M) and coded 1 Msymbol/s LE long
range packets (LE coded).
– Supplementary option R&S CMW-KM722 extends the R&S CMW-KM721 for
the support of measurements on LE packets with constant tone extension
(CTE), LE uncoded PHY.
All Tx tests are available within a multi-evaluation measurement group, refer to Chap-
ter 7.2.1, "Tx Measurements", on page 330.
"Bluetooth Signaling" option or GPRF generator with Bluetooth waveform file can be
used to generate Bluetooth signal to be sent to the EUT in parallel to the Tx measure-
ments.
GPRF generator with option R&S CMW-KV610 enables processing of Bluetooth wave-
form files.
R&S CMW supports Tx measurement of EUT signals during a signaling connection,
see Chapter 7.2.1.3, "Parallel Signaling and Measurement", on page 332.
Rx measurements:
Support of non-signaling Rx tests is available with GPRF generator. It processes pre-
defined waveform files (ARB files). The following Rx measurements are supported:
● Option R&S CMW-KD611 for non-signaling Rx advertiser tests, version 4.2. An
R&S CMW100/CMW with MUA is required.
For details, refer to Chapter 7.2.2, "Rx Measurements with ARB Generator: Adver-
tiser Tests", on page 334.
● Option R&S CMW-KD720 for direct test mode, version 5.0. PER and PER search
Rx measurements are supported. An R&S CMW100 is required.
For details, refer to Chapter 7.2.3, "Rx Measurements with ARB Generator: Direct
Test Mode", on page 336.
test mode test mode normal direct test direct test connection others
(DHx) (2-/3-DHx) mode 5,6) (test pack- (test packets test 5,6) (data (advertis-
(all pack- ets) with CTE) chan. pack- ers)
ets) ets)
"Power vs Slot" X
"DEVM" X
"Phase Difference" X
test mode test mode normal direct test direct test connection others
(DHx) (2-/3-DHx) mode 5,6) (test pack- (test packets test 5,6) (data (advertis-
(all pack- ets) with CTE) chan. pack- ers)
ets) ets)
"Spectrum 20 dB Band- X
width"
"Frequency Range" X
"PER" (tab) 8) X
7.2.1 Tx Measurements
Modula- Frequency accuracy Carrier frequency stability Frequency accuracy Frequency accuracy
tion Frequency deviation Differential error vector Frequency offset Frequency deviation
magnitude (DEVM)
Frequency drift Frequency deviation CTE frequency off-
Differential phase encod- set
Drift rate Frequency drift, ini-
ing tial drift, max. drift CTE frequency drift,
rate CTE initial drift,
CTE max. drift rate
Spec- Frequency range In-band spurious emis- Adjacent channel Adjacent channel
trum sions power power
20 dB bandwidth
Adjacent channel
power
For a definition of measured quantities and conformance requirements, refer to the fol-
lowing test specification for Bluetooth wireless technology:
● Basic rate (BR) and enhanced data rate (EDR) measurements in test mode:
RF for 5.0.0
(R&S CMW-KM610)
● Low energy (LE) measurements in direct test mode:
– RF PHY for 5.0.0 (R&S CMW-KM611, R&S CMW-KM721)
– RF PHY for 5.1.0 (R&S CMW-KM722 )
The following sections describe Bluetooth Tx measurements and show how to perform
them.
● Test Setup............................................................................................................. 331
● Measuring a Bluetooth Signal............................................................................... 331
● Parallel Signaling and Measurement.................................................................... 332
Connect the external RF signal source (mobile station, signal generator etc.) to one of
the bidirectional RF connectors on the front panel of the R&S CMW.
For measurements in combined signal path, refer to the user manual of Bluetooth sig-
naling, chapter test setup.
See Chapter 2.2.2, "Test Setup", on page 15.
After connecting your Bluetooth device to the R&S CMW as described in the section
Chapter 7.2.1.1, "Test Setup", on page 331, adjust the following analyzer settings to
the properties of the transmitted Bluetooth signal:
● The analyzer frequency
● The expected nominal power and (optionally) a user margin and external attenua-
tion.
Recommended values:
"Expected Nominal Power" = nominal power of the Bluetooth packet
"User Margin" = 3 dB
● The trigger source "Power" for stand-alone measurements
The selection of the trigger for combined signal path (CSP) is done automatically,
see Chapter 7.2.1.3, "Parallel Signaling and Measurement", on page 332 for
details.
For exact time synchronization to the received signal and proper decoding, the "Blue-
tooth Input Signal" settings in the configuration dialog must be in accordance with the
measured signal:
BD address match piconet master's match piconet master's for advertisers only
LAP1) LAP1)
1) The lower address part (LAP) consists of the last 6 hexadecimal digits of the Bluetooth device address.
In the CONNECTION state, the LAP of the piconet's master is used to generate the channel access code of
each transmitted packet.
Alternatively, for an unspecified BD address, enable automatic synchronization, see "Auto Sync (BR/EDR)"
on page 434.
With the settings described above, the R&S CMW is able to analyze the received pack-
ets. Some measurement results and some test purposes in the Bluetooth radio test
specification require a particular signal configuration; for an overview refer to Chap-
ter 7.3.1, "Basic Rate Measurements in Test Mode", on page 363, Chapter 7.3.2,
"Enhanced Data Rate Measurements in Test Mode", on page 367 and Chapter 7.3.3,
"Low Energy Measurements in Direct Test Mode", on page 370.
Default settings
The default values for the "Payload Length" correspond to the maximum allowed
length for each packet type; see "Packet Type" on page 436. If the measured Blue-
tooth signal complies with the default settings, you only have to adjust the "Burst Type"
and the "Packet Type".
tion and the resulting uplink signal can be measured using the multi-evaluation mea-
surement.
A Bluetooth combined signal path (CSP) measurement requires one of the following
option combinations:
● Signaling: Option R&S CMW-KS600/-KS602 or /-KS603 for BR/EDR (classic)
Measurement: R&S CMW-KM610 (normal mode)
● Signaling: R&S CMW-KS610 for BR/EDR test mode
Measurement: R&S CMW-KM610 (as per Bluetooth test specification)
● Signaling: R&S CMW-KS601 for signaling connection tests with uncoded LE 1M
PHY (including LE test mode)
Measurement: R&S CMW-KM611 (normal mode with LE connection tests)
● Signaling: R&S CMW-KS720 for signaling connection tests with LE 2M or LE
coded PHY (including LE test mode)
Measurement: R&S CMW-KM721 (normal mode with LE connection tests)
● Signaling: R&S CMW-KS611 for direct test with LE 1M PHY (uncoded)
Measurement: R&S CMW-KM611 (as per Bluetooth test specification)
● Signaling: R&S CMW-KS721 for direct test with LE 2M (uncoded) or LE coded
PHY
Measurement: R&S CMW-KM721 (as per Bluetooth test specification)
● Signaling: R&S CMW-KS722 for direct test on LE with CTE, uncoded LE 1M or LE
2M PHY
Measurement: R&S CMW-KM722 (as per Bluetooth test specification)
To use both applications in parallel, the combined signal path scenario must be activa-
ted (see "Scenario, Controlled by" on page 428). Most signal routing and analyzer set-
tings and some measurement control settings are then configured by the signaling
application. The multi-evaluation measurement displays the corresponding signaling
settings instead of its own settings. These signaling settings can be configured in both
measurement and signaling application GUIs. Use the commands of signaling applica-
tion to configure the settings via remote control. For a command-mapping table, see
Chapter 7.6.7, "Combined Signal Path Commands", on page 695.
For LE measurements in combined signal path, keep 20 dB difference between the "Tx
Level (CMW)" and "Exp. Nominal Power" to avoid measurement errors.
The values are configurable by the signaling application.
In the measurement GUI the most important signaling parameters can be configured
via additional hotkeys, see Chapter 7.4.12, "Additional Softkeys and Hotkeys",
on page 465.
In the combined signal path scenario, the trigger signal from the signaling application
has to be used as the measurement application trigger input. The selection of the trig-
ger is done automatically:
● "Bluetooth Sig<i>: ACPTrigger" for the 79 channels mode of BR/EDR ACP mea-
surements and for the all channels mode of LE ACP measurements.
● "Bluetooth Sig<i>: LESignallingTrigger" for LE connection tests (normal mode)
Within option R&S CMW-KD611, you can perform non-signaling over-the-air (OTA) Rx
tests on advertisers. The RX measurement only supports LE 1 Msymbol/s uncoded
physical layer (LE 1M PHY), advertiser packets. It covers all advertising channels (37,
38, 39), see Chapter 7.2.6.4, "LE: Channels", on page 346.
The RF signal of the R&S CMW is fed to the antenna port of the DUT. The R&S CMW
measures the DUT reaction. Most conveniently, a bi-directional connection with a sin-
gle coax cable can be used.
For OTA RF connection, use an RF shield box, for example R&S CMW-Z10. Connect
the shield box to one of the bidirectional RF connectors on the front panel of the
R&S CMW.
The "Bluetooth Measurement" provides a power trigger signal that can be used by
other R&S CMW applications. The trigger is useful for non-signaling Rx measurements
for the timing of SCAN_REQ sent by the GPRF generator.
Option R&S CMW-KD611 is required (only for R&S CMW100/CMW with MUA).
To address the trigger signals of the measurement in remote commands, use the fol-
lowing string, with <i> replaced by the instance number of the measurement:
● "Bluetooth Meas<i>: Power"
9. Configure output path for waveform signal transmission. See RF Routing (Output).
11. Configure any other required settings (as for a connection without Rx measure-
ments).
12. Select the softkey "Rx Meas" and switch on the signal generator and measure-
ment:
a) Press [ON | OFF], or
b) Right-click the softkey "Rx Meas" > "ON".
Within option R&S CMW-KD720, you can perform PER and PER search measure-
ments in direct test mode on LE test packets, version 5.0.
Connect the external RF signal source (mobile station, signal generator etc.) to one of
the bidirectional RF connectors on the front panel of the R&S CMW.
In addition, the R&S CMW uses also a secondary communication channel via USB for
control commands.
The installation of a USB driver is necessary on the R&S CMW100 control computer.
Verify that the driver is properly installed on the R&S CMW as follows:
1. Open the device manager (Windows sign + D to show the desktop, Start > Control
Panel > Device Manager).
2. Find your USB to RS232 adapter under Ports (COM & LPT), for example, ATEN
USB to Serial Bridge (COM4). The COM port number depends on the connected
USB port.
Note that the "Virtual COM Port" used by the "Bluetooth Measurement" application
has different numbering than the COM port assigned during the installation of the
USB-to-serial driver.
7. In the tab "EUT Control", set the HW Interface to USB to RS232 adapter
Additional tabs "PER" and "PER Search" appear.
8. Configure output path for waveform signal transmission. See RF Routing (Output).
10. In the tab "PER", configure dirty Tx. See "Stable Modulation Index" on page 422.
12. Configure any other required settings (as for a connection without Rx measure-
ments).
13. In the tab "PER", right-click the softkey "PER" > "ON" to switch on the signal gener-
ator and measurement.
per advertiser event in remote operation. The first advertiser event is used for training
phase, actual Tx-Rx tests run at the next three advertiser events.
These measurements support LE 1 Msymbol/s uncoded physical layer (LE 1M PHY)
and cover all advertising channels (37, 38, 39) within only four advertising events, see
Chapter 7.2.6.4, "LE: Channels", on page 346.
For remote control, refer to Chapter 7.6.5, "Combined Non-Signaling Tx-Rx Measure-
ment Commands", on page 673.
● For the description of Tx tests, refer to Chapter 7.2.1, "Tx Measurements",
on page 330
● For the description of spot check Rx tests, refer to Chapter 7.2.2, "Rx Measure-
ments with ARB Generator: Advertiser Tests", on page 334
The Bluetooth multi-evaluation list mode requires option R&S CMW-KM012. In this
mode, the signal is captured and processed in segments. The list mode is essentially a
single-shot remote control application. When a measurement is initiated in list mode,
all defined segments are measured once.
Each segment could be configured to measure any one or more of the following mea-
surements: Power, modulation, 20dB bandwidth (occupied bandwidth), spectrum ACP
or spectrum gated ACP. With spectrum ACP and spectrum gated ACP measurements,
full Bluetooth band measurement (79 channels for BR/EDR, and 81 MHz for LE) is not
possible. Statistic count (or the number of bursts to measure) for each of the measure-
ments listed above could be set individually for each of the segment.
A single list mode measurement could configure up to a maximum of 48 segments.
Maximum signal capture duration is 6700 Bluetooth timeslots (or ~ 4.18 s).
Initially, the capture mechanism is armed and awaits the trigger to start the capture
process. Once the trigger is detected, then all the specified segments have to be cap-
tured.
The received signal is expected to be reconfigured at the end of a segment in prepara-
tion for the capture of the next segment. If this reconfiguration is not possible, then the
capturing needs to be rearmed to await the trigger for the capture of the next segment,
as shown in the figure below.
It is possible to measure all bursts of a segment or to exclude bursts at the end of the
segment. The statistical length defines the number of bursts to be measured. The "cur-
rent" result of a segment refers to the last measured burst of the statistical length.
Additional statistical values (average, minimum, maximum and standard deviation) are
calculated for the entire statistical length. The following figure provides a summary.
Remote commands
The list mode is essentially a single-shot remote control application. When a measure-
ment is initiated in list mode, all defined segments are measured once. Afterwards, the
results can be retrieved using FETCh commands.
The following remote control commands are used for list mode settings and result
retrieval.
Table 7-3: List mode commands
The list mode can be deactivated via command (see table above) and also via the GUI:
1. Go to local using the corresponding hotkey.
The active list mode is indicated in the upper right corner of the current view by the
words "List Mode".
2. Open the configuration dialog box. Disable the list mode in section "Measurement
Control ".
For better understanding of the required settings, this section describes the following
selected topics related to Bluetooth technology.
● BR/EDR: Channels............................................................................................... 344
● BR/EDR: ACL Packet Format............................................................................... 345
● BR/EDR: Modulation Scheme...............................................................................345
● LE: Channels.........................................................................................................346
● LE: Packet Formats...............................................................................................347
● LE: Packet Types.................................................................................................. 348
● LE: Modulation Scheme........................................................................................ 351
The frequency band defined for Bluetooth devices is the unlicensed 2.4 GHz "Indus-
trial, Scientific and Medical" (ISM) frequency band.
Table 7-4: Operating band
Two modulation modes are used for Bluetooth: the mandatory basic rate (BR) and the
optional enhanced data rate (EDR). The BR mode uses binary FM modulation and pro-
vides a data rate of 1 Mbps. The EDR mode uses two types of PSK modulation, the
π/4-DQPSK or 8DPSK, and achieves data rates of 2 Mbps and 3 Mbps, respectively.
All modulations schemes have the symbol rate equal to 1 Msymbol/s.
A time division duplex (TDD) scheme for duplex transmission is defined for both
modes.
The ACL packets are used for asymmetric links and they contain user data or control
data. The table and the figures below give an overview of the ACL packets and their
structure.
Table 7-5: ACL packet - BR
DH1 1 0-27 1
DH3 2 0-183 3
DH5 0-339 5
* The payload length in the table denotes the number of user payload bytes.
2-DH1 2 0-54 1
2-DH3 0-367 3
2-DH5 0-679 5
3-DH1 0-83 1
3-DH3 0-552 3
2-DH5 0-1021 5
* The payload length in the table denotes the number of user payload bytes.
The modulation used for the basic data rate packets is Gaussian frequency shift keying
(GFSK) with a bandwidth bit period product BT=0.5. The modulation index is between
0.28 and 0.35.
The modulation scheme used for enhanced data rate packets changes within the
packet. The access code and packet header have a GFSK modulation scheme and are
transmitted with the basic rate 1 Mbps. The subsequent synchronization sequence,
payload and trailer sequence have a PSK type of modulation and are transmitted with
a data rate of 2 Mbps or optionally 3 Mbps.
The PSK modulation, namely π/4 rotated differential encoded quaternary phase shift
keying (π/4–DQPSK) is defined for the 2 Mbps transmission.
The PSK modulation, namely differential encoded 8-ary phase shift keying (8DPSK), is
defined for the 3 Mbps transmission.
Table 7-7: The modulation types and corresponding packet types
The R&S CMW provides you with the ability to generate signals in accordance with the
low energy (LE) specification for Bluetooth wireless technology. Bluetooth LE provides
data transfer from low-power devices running on the smallest of batteries to a larger
device, such as a PC, a mobile phone, or a PDA. For the first time, a Bluetooth con-
nection to a wristwatch, or a heart rate sensor, or a data transfer from a digital camera,
is possible. The generated packets do not support audio content.
A time division duplex (TDD) scheme for duplex transmission is defined. The frequency
band defined for Bluetooth devices is the unlicensed 2.4 GHz "Industrial, Scientific and
Medical" (ISM) frequency band.
Table 7-8: Operating band
0 2402 - 37
1 to 11 2404 to 2424 0 to 10 -
12 2426 - 38
13 to 38 2428 to 2478 11 to 36 -
39 2480 - 39
Sync word /
Preamble PDU CRC CTE
Access address
Packets (not including the CTE) take between 44 and 2120 μs to transmit. CTE trans-
mission takes between 16 and 160 μs (CTE units x 8 μs).
S = 8 coding S = 2 or 8
Each packet consists of the preamble, FEC block 1, and FEC block 2. The preamble is
not coded. The FEC block 1 consists of three fields: access address (or sync word for
test packets), coding indicator (CI), and TERM1. These fields use the S=8 coding
scheme. The CI field determines which coding scheme is used for FEC block 2. The
FEC block 2 consists of three fields: PDU, CRC, and TERM2. These fields use either
the S=2 or S=8 coding scheme, depending on the value of the CI field.
The entire packet is transmitted with 1 Msymbol/s modulation. The following table cap-
tures the size and duration of the packet fields.
Table 7-11: Packet format for LE coded PHY
CTE
PDU
2-20 units
Header Payload
2 octets 0-255 octets
LE test packets are described in the "Air Interface Packets" section of core specifica-
tion for Bluetooth wireless technology, volume 6, part B.
PDU
LSB MSB
Header Payload
2 octets 1-255 octets
The PDU header indicates the payload content type, the payload length expresses in
octets, and information related to the PDU type.
With option R&S CMW-KM611, the R&S CMW allows all advertising channel packet
types defined in Bluetooth specification version 4.2 to be measured in payload-inde-
pendent measurement mode. The supported PDU types, are listed in the following
table.
Table 7-12: Supported advertising channel PDU types with R&S CMW-KM611
For advertising packets, the option R&S CMW-KM611 supports only LE 1 Msymbol/s
uncoded physical layer (LE 1M PHY) and only primary advertising channels (channel
index 37, 38, and 39).
Extended advertising
Option R&S CMW-KM721 supports additionally also low energy extended advertising
as defined in Bluetooth specification version 5.0.
Table 7-13: Supported advertising channel PDU types with R&S CMW-KM721
*) extended advertising
Extended advertising uses one of the primary advertising channels (channel index 37,
38, or 39) for ADV_EXT_IND. This advertiser indicates the transmission of the next
auxiliary packet in the chain. All auxiliary packets use secondary advertising channels
(channel index 0 to 36).
PDU
LSB MSB
Header Payload
2 octets 0-251 octets
For measurements on data channel packet with LE connection test, R&S CMW sup-
ports only uncoded LE 1M PHY.
Besides the data packet type, instrument supports the following CONTROL_DATA
packet types.
Table 7-14: Control data packet types
Table 7-15: Additional control data packet types within additional option R&S CMW-KM721
The modulation is Gaussian frequency shift keying (GFSK) with a bandwidth bit period
product BT = 0.5. The modulation index has to be between 0.45 and 0.55. The manda-
tory modulation scheme is 1 Msymbol/s modulation. It uses a shaped, binary FM to
minimize transceiver complexity.
● 1 Msymbol/s modulation supports two PHYs:
– LE 1M PHY: LE physical layer with uncoded data at 1 Mbit/s
– Optional LE coded PHY: LE coded physical layer with the access address,
coding indicator, TERM1 fields of the packet coded at 125 kbit/s and the pay-
load coded at either 125 kbit/s or 500 kbit/s
● The 2 Msymbol/s modulation supports physical layer with uncoded data at 2 Mbit/s
(LE 2M PHY)
For low energy with CTE, the R&S CMW supports only uncoded PHY (LE 1M PHY and
LE 2M PHY).
Conformance requirements for Bluetooth transmitter tests are specified in the test
specification for Bluetooth wireless technology; the following sections give an overview.
● Transmit Power Requirements..............................................................................352
● Modulation Requirements..................................................................................... 352
● Spectrum Requirements....................................................................................... 354
● Differential Phase Encoding Requirements.......................................................... 355
In addition, the guard time has to be between 4.75 μs and 5.25 μs. The guard time
starts at the end of the last GFSK symbol of the header and ends at the start of the
reference symbol of the synchronization sequence.
Bluetooth Maximum output Nominal output power Min. output power Pmin Power control
device power Pmax (peak (at max. power setting)
power)
LE 10 dBm for v4.2 n/a -20 dBm the output power control can
be changed locally
20 dBm from v5.0
*) lower power limit Pmin < –30 dBm is suggested but not mandatory
BR EDR
Frequency drift -50 kHz to 50 kHz -50 kHz to 50 kHz -50 kHz to 50 kHz
Initial frequency drift -23 kHz to 23 kHz -23 kHz to 23 kHz n/a
with CTE: -13.6 kHz to 13.6 with CTE: -13.6 kHz to 13.6
kHz kHz
Maximum drift rate -20 kHz/50μs to 20 kHz/50μs -20 kHz/50μs to 20 kHz/50μs -19.2 kHz/48µs to 19.2 kHz/
48µs
(payload) (between any two 10-bit (between any two 20-bit
groups separated by 50µs) groups separated by 50µs) (between any two 16-symbol
groups separated by 48µs)
Maximum drift rate -19.2 kHz/50μs to 19.2 kHz/ -19.2 kHz/50μs to 19.2 kHz/ n/a
50μs 50μs
(CTE)
(between any two CTE units (between any two CTE units
separated by 50µs) separated by 50µs)
Average frequency deviation Δf1 avg: 225 kHz to 275 kHz *) Δf1 avg: 450 kHz to 550 kHz*) Δf1 avg: 225 kHz to 275 kHz
standard modulation character-
istics
Average frequency deviation Δf1 avg: 247.5 kHz to 252.5 Δf1 avg: 495 kHz to 505 kHz*) n/a
kHz *)
stable modulation characteris-
tics
Lower limit for at least 99.9% Δf2: 185 kHz *) Δf2: 370 kHz*) Δf1: 185 kHz
frequency deviations
The spectrum requirements depend on the packet type. For a definition of the relevant
channel powers, refer to Chapter 7.4.2.11, "EDR: Spectrum Gated ACP Results ",
on page 401.
Table 7-19: Bluetooth spectrum requirements
Spectrum 20 dB bandwidth BR RF/TRM/CA/BV-05-C 1.0 MHz for high peak emission bursts (≧ 0 dBm)
upper limit fH – fL
1.5 MHz for low peak emission bursts (< 0 dBm)
Frequency range upper and BR RF/TRM/CA/BV-04-C fL, fH within the allowed frequency band 2.4 GHz to
lower limit 2.4835 GHz
Spectrum ACP upper limit BR RF/TRM/CA/BV-06-C 1) PTX (±2 MHz) ≦ -20 dBm
PTX (n MHz) ≦ -40 dBm, |n| ≧ 3 2)
Spectrum gated ACP upper DPSK portion RF/TRM/CA/BV-13-C 1) PTX (±2 MHz) ≦ -20 dBm
limit of EDR
PTX (n MHz) ≦ -40 dBm, |n| ≧ 3 2)
PTX - 26 dB(±1 MHz) ≦ PTXref – 26
In-band emissions upper LE for RF-PHY/TRM/BV-03-C 1) PTX (±2 MHz) ≦ -20 dBm
limit LE1M PHY 1)P
TX (n MHz) ≦ -30 dBm, |n| ≧ 3 3)
These requirements are defined for EDR only. For a definition of the relevant parame-
ters, refer to Chapter 7.4.2.10, "EDR: Differential Phase Encoding Results ",
on page 400.
Table 7-20: Bluetooth EDR differential phase encoding requirements
Differential phase encoding RF/TRM/CA/BV-12-C zero errors detected in 99% of the packets
lower limit
If the measurement is performed repeatedly, the R&S CMW can evaluate the trace sta-
tistics. The number and position of the trace points is calculated as described in the fol-
lowing sections.
● PvT and Freq. Dev. Trace Points (Classic)........................................................... 355
● DEVM Trace Points for Test Mode (EDR).............................................................356
● Phase Difference Trace Points (EDR)...................................................................358
● Trace Points for IQ Constellation Diagrams (EDR)...............................................359
● PvT and Modulation Trace Points (LE)................................................................. 360
● Scope of Spectrum Measurements.......................................................................361
The number N of symbols in the burst can be read from the figure above: N = 150
+ 8*n for DH1 packets, N = 158 + 8 * n for DH3 and DH5 packets. With a fixed over-
sampling factor of 4, the number m of trace points is equal to:
m = 4*(100 + N + 100) = 800 + 4*N
For EDR, the following fields are used for power measurements:
The number of DEVM trace points depends on the packet type and the payload length.
These parameters determine the number N of 50-symbol blocks that the R&S CMW
processes for the modulation analysis.
Number N of blocks processed for floor [(56 + 8*n)/(2*50)] floor [(68 + 8*n)/(3*50)]
EDR modulation analysis
The displayed DEVM values include 132 zeros, corresponding to 126 GFSK symbols,
5 guard period symbols, and 1 Sref symbol. Thus, the number of DEVM values is 132
+ 50*N.
DEVM calculation
In the π/4-DQPSK and 8DPSK modulation schemes, the modulation vector corre-
sponds to the distance between two points in the constellation diagram, irrespective of
the axes and the origin. See figure below, part (a). The differential error vector magni-
tude (DEVM) is calculated from the magnitude of the differential error vector, in anal-
ogy to the ordinary EVM (part (b)).
In the "Differential Error Vector Magnitude" view, the DEVM is expressed as the ratio |
E| / |R'|. To obtain the DEVM results, the R&S CMW proceeds as described in Chap-
ter 7.4.2.9, "EDR: Statistical Modulation Results ", on page 398.
π/4 1/4 0 0
3π/4 3/4 0 1
–3π/4 –3/4 1 1
–π/4 –1/4 1 0
0 0 0 0 0
π/4 1/4 0 0 1
π/2 1/2 0 1 1
3π/4 31/4 0 1 0
π 1 1 1 0
–3π/4 –3/4 1 1 1
–3π/2 –1/2 1 0 1
–π/4 –1/4 1 0 0
"Phase Difference" is calculated for symbols starting from the guard symbols to the
symbol corresponding to the signal power down ramp position. All the DPSK symbols
within the burst and beyond are covered.
The IQ constellation (absolute and relative) results correspond to the normalized I/Q
vectors of the Sref symbol and of each symbol in the 50-symbol blocks processed. The
number of results is 50*N + 1 where N is the number of blocks from Symbol blocks for
EDR modulation analysis. The constellation error is based on the DEVM between con-
secutive symbols, so the number of results is 50*N.
The I/Q diagrams show the constellation points (or vector diagrams) for the DPSK
modulated portion of the EDR bursts. The diagrams start from the Sref symbol in the
EDR synchronization sequence (shown in the following figure).
tion sequence. The last symbol in each block provides the phase reference that is nec-
essary to demodulate the (differentially modulated) symbols in the next block. The Sref
symbol is used as a reference for the first block.
The I/Q values can be displayed in three different diagram types; see Chapter 7.4.2.7,
"EDR: Measurement Diagrams ", on page 395.
IQ constellation absolute
The absolute I/Q diagram shows the normalized I/Q vectors starting from Sref symbol.
The diagrams contain 50*N + 1 consecutive symbols. Normalization means that the
average magnitude of all I/Q vectors equals to 1. N is the number of blocks processed
within a packet. This value depends on packet type and number of payload bytes
("Payload Length"). For 2-DHx and 3-DHx packets, it is calculated according to
Table 7-21.
IQ constellation differential
The differential I/Q diagram shows the normalized I/Q amplitude of each symbol and
the phase difference compared to the previous symbol:
Last symbol = a · e j·⍺, current symbol = b · e j·β
Prerequisites
I/Q symbols are displayed for EDR Bluetooth bursts only.
I/Q symbols are not displayed for the following EDR Bluetooth bursts:
● Without valid EDR synchronization sequence or
● With less than 50 valid DPSK symbols (excluding the Sref).
Symbols from fractional blocks at the end of the burst are not displayed.
The number of time domain trace points for LE packets ("PvT", "Freq. Deviation")
depends on the payload length. The traces cover the whole burst plus 160 symbols
before the symbol 0 and 100 symbols after the last symbol in the burst. Exception: for
measurements with LE connection tests (R&S CMW-KS601/-KS720), the traces cover
the whole burst plus 140 symbols before the symbol 0 and 100 symbols after the last
symbol in the burst.
For LE uncoded PHY (LE 1M PHY and LE 2M PHY), the TX measurements display
four samples per symbol.
For LE coded PHY, the TX measurements display one sample per symbols. Measure-
ments for LE coded PHY are applicable to power versus time and frequency deviation
graphs only.
The Bluetooth LE transmission interval depends on LE packet length L. Core specifica-
tion defines the minimum LE test packet interval in LE direct test mode for L in μs:
I (L) = ceiling ((L + 249) / 625) x 625
For packet structure, refer to Chapter 7.2.6.5, "LE: Packet Formats", on page 347.
Adjacent channel power (ACP) is the radiated RF power in the off-carrier channels.
The R&S CMW measures the ACP in accordance with the Bluetooth RF test specifica-
tion; for details refer to the following sections:
● BR: Chapter 7.4.2.6, "BR: Spectrum ACP Results ", on page 392
● EDR: Chapter 7.4.2.11, "EDR: Spectrum Gated ACP Results ", on page 401
● LE: Chapter 7.4.2.18, "LE: Spectrum ACP Results ", on page 415
According to the test specification, the ACP measurement must cover all Bluetooth
channels, i.e. a frequency band of at least 80 MHz. To achieve this range, the received
signal is captured multiple times at different receive frequencies.
The measurement bandwidth for each single shot capture is 25 MHz. To cover all
channels, a minimum of four captures is required.
In summary, to measure in accordance with the LE RF test specification use the follow-
ing settings:
● Settings for LE 1M PHY:
– For the payload length of 37 bytes, set the statistic count to 2 ms / 376 µs ≅ 6
– For the payload length of 255 bytes, set the statistic count to 2 ms / 2120 µs ≅
1
● Settings for LE 2M PHY:
– For the payload length of 37 bytes, set the statistic count to 2 ms / 192 µs ≅ 11
– For the payload length of 255 bytes, set the statistic count to 2 ms / 1064 µs ≅
2
● Tests for LE coded PHY are not specified in the test specification for Bluetooth
wireless technology RF-PHY, version 5.0.0.
This application sheet describes the use of the "Bluetooth Measurement" firmware
application for non-signaling transmitter tests on Basic Rate (BR) packets. The mea-
surements are in line with the test specification for Bluetooth wireless technology RF,
version 4.2.3.
The power measurements are in accordance with the test specification for Bluetooth
wireless technology, see test purpose RF/TRM/CA/BV-01-C. The RF output power
results include nominal power and peak power.
To obtain the RF output power results in accordance with the test specification, pro-
ceed as follows:
● Select the wideband measurement filter ("Measurement Control > Filter > Basic
Rate Filter Bandwidth: Wide"
● Provide a signal with the following characteristics and adjust the "Bluetooth Input
Signal" settings accordingly.
Table 7-24: Power measurement settings
Maximum output power Expected nominal power Select according to the power class of the
EUT
Hopping off, three consecutive measure- Frequency Use 2402 MHz, 2441 MHz, 2480 MHz
ments at lowest, mid, and highest operat-
ing frequency.
EUT transmits the longest supported "Bluetooth Input Signal > Packet Type, Depending on EUT capabilities, e.g. DH5
packet type with full payload length Payload Length" with a 339 byte payload
EUT transmits a PRBS 9 sequence as "Bluetooth Input Signal > Basic Rate Pat- "Other" denotes any pattern except
payload tern Type": Other "11110000" and "10101010".
According to the test specification for Bluetooth wireless technology, some of the mod-
ulation results for BR packets require a particular payload pattern. The following table
gives an overview.
Table 7-25: BR payload patterns and modulation results
Payload length
Due to the different measurement procedures, some of the modulation results are valid
only if the packet contains enough payload bytes. A packet configuration according to
the test specification for Bluetooth wireless technology ensures a sufficient "Payload
Length" for all modulation results.
The modulation measurements are in accordance with the test specification for Blue-
tooth wireless technology, see test purpose RF/TRM/CA/BV-07-C and RF/TRM/CA/
BV-08-C.
To obtain the modulation characteristics in accordance with the test specification, pro-
ceed as follows:
● Use the default measurement filter ("Measurement Control > Filter > Basic Rate
Filter Bandwidth: Narrow"
● Use the default statistical settings ("Measurement Control > Modulation > Statistic
Count: 10")
● Provide a signal with the following characteristics and adjust the "Bluetooth Input
Signal" settings accordingly.
Table 7-26: Modulation measurement settings
Maximum output power Expected nominal power Select according to the power class of the
EUT
Hopping off, three consecutive measure- Frequency Use 2402 MHz, 2441 MHz, 2480 MHz
ments at lowest, mid, and highest operat-
ing frequency.
EUT transmits the longest supported "Bluetooth Input Signal > Packet Type, Depending on EUT capabilities, e.g. DH5
packet type with full payload length Payload Length" with a 339 byte payload
EUT transmits a 11110000... bit pattern "Bluetooth Input Signal > Basic Rate Pat- "Other" denotes any pattern except
(stage 1) or a 10101010... bit pattern as tern Type": "11110000" or "10101010" "11110000" and "10101010".
payload
To obtain the 20 dB bandwidth, the R&S CMW automatically uses the basic test set-
tings from the test specification for Bluetooth wireless technology: 10 kHz resolution
bandwidth (fixed), "Statistic Count": 10 (default), calculation of "Maximum" values
(fixed).
To measure in line with test purpose RF/TRM/CA/BV-05-C, provide a signal with the
following characteristics, and adjust the "Bluetooth Input Signal" settings accordingly.
Table 7-27: 20 dB bandwidth measurement settings
Maximum output power Expected nominal power Select according to the power class of the
EUT
Hopping off, three consecutive measure- Frequency Use 2402 MHz, 2441 MHz, 2480 MHz
ments at lowest, mid, and highest operat-
ing frequency.
EUT transmits the longest supported "Bluetooth Input Signal > Packet Type, Depending on EUT capabilities, e.g. DH5
packet type with full payload length Payload Length" with a 339 byte payload
EUT transmits a PRBS 9 sequence as "Bluetooth Input Signal > Basic Rate Pat- "Other" denotes any pattern except
payload tern Type": Other "11110000" and "10101010".
The measurement method of the R&S CMW does not rely on a frequency sweep as
suggested in the specification but provides equivalent results.
To obtain the frequency range bandwidth, the R&S CMW automatically uses the basic
test settings from the test specification for Bluetooth wireless technology: resolution
bandwidth of 100 kHz, a video bandwidth of 300 kHz, a peak detector, calculation of
"Average" values (trace). The R&S CMW measures one complete burst at each of 501
frequency pixels. According to the test specification, the measurement must be per-
formed in two different frequency ranges. The frequency pixels are set by the fre-
quency span shown in the table below.
Table 7-28: Measurement frequencies
Therefore the frequency between pixels would be either 20kHz for 10MHz span, or
12kHz for 6 MHz span (Δf = span / 500).
To measure in line with test purpose RF/TRM/CA/BV-04-C, it is recommended to use
the "Bluetooth Signaling" application and combined signal path scenario.
Test procedure:
1. Via "Bluetooth Signaling" application, establish the test mode connection to the
EUT (loopback or TX test) using the PRBS9 pattern. Disable frequency hopping.
3. In the "Bluetooth TX Measurement" application, set the threshold value for the
spectral power density drop.
5. Measure lowest frequency fL at which spectral power density drops below the
specified threshold value.
7. Measure highest frequency fH at which spectral power density drops below the
specified threshold value.
Maximum output power "Power Up" hotkey Via the signaling application
Hopping off, two consecutive measure- Frequency Set 2402 MHz, 2480 MHz via signaling
ments at lowest and highest operating fre- application
quency.
EUT transmits the BR "General Setup > Burst Type" Set "Basic Rate" via the signaling applica-
tion
EUT transmits a PRBS9 pattern as pay- "Bluetooth Signal Characteristics > Basic Set "PRBS9" via the signaling application
load Rate Pattern Type"
The measurement method of the R&S CMW does not rely on a frequency sweep as
suggested in the specification but provides equivalent results.
To obtain the adjacent channel power (ACP), the R&S CMW automatically uses the
basic test settings from the test specification for Bluetooth wireless technology: 100
kHz resolution bandwidth (fixed), "Statistic Count": 10 (default). The required ACP
results correspond to the "Maximum" values in the ACP diagrams.
To measure in line with test purpose RF/TRM/CA/BV-06-C, provide a signal with the
following characteristics, and adjust the "Bluetooth Input Signal" settings accordingly.
Table 7-30: ACP measurement settings
Maximum output power Expected nominal power Select according to the power class of the
EUT
Hopping off, three consecutive measure- Frequency Use 2405 MHz, 2441 MHz, 2477 MHz
ments at lowest operating frequency + 3
MHz, mid frequency, and highest operat-
ing frequency – 3 MHz.
EUT transmits DH1 packets "Bluetooth Input Signal > Packet Type: Maximum payload length for DH1 BR
DH1" packets: 27 bytes
EUT transmits a PRBS 9 sequence as "Bluetooth Input Signal > Basic Rate Pat- "Other" denotes any pattern except
payload tern Type": Other "11110000" and "10101010".
Specified sweep time: 10 * 100 ms Statistic count: 800 for DH1 packets, 267 See "Statistical settings for ACP measure-
for DH3, 160 for DH5 ments" in Chapter 7.2.8.6, "Scope of
Spectrum Measurements", on page 361.
For the 79 channels ACP measurements in the combined signal path scenario, the
ACP trigger of the "Bluetooth Signaling" application is automatically selected.
The measurement method of the R&S CMW is faster than the method suggested in the
specification but provides equivalent results.
This application sheet describes the use of the "Bluetooth TX Measurement" firmware
application for non-signaling transmitter tests on Enhanced Data Rate (EDR) packets.
The measurements are in line with the test specification for Bluetooth wireless technol-
ogy, RF, version 4.2.3.
The power measurements are in accordance with the test specification for Bluetooth
wireless technology, see test purpose RF/TRM/CA/BV-10-C. The RF output power
results include nominal power, GFSK power, DPSK power. The required results corre-
spond to the "Average" values in the "Power vs. Time" diagrams.
To obtain the RF output power results in accordance with the test specification, pro-
ceed as follows:
● Use the default measurement filter ("Measurement Control > Filter > EDR Filter
Bandwidth: Wide")
● Use the default statistical settings ("Measurement Control > Power vs. Time > Sta-
tistic Count: 10")
● Provide a signal with the following characteristics and adjust the "Bluetooth Input
Signal" settings accordingly.
Table 7-31: Power measurement settings
Maximum output power Expected nominal power Select according to the power class of the
EUT
Hopping off, three consecutive measure- Frequency Use 2402 MHz, 2441 MHz, 2480 MHz
ments at lowest, mid, and highest operat-
ing frequency.
EUT transmits the longest supported π/4 "Bluetooth Input Signal > Packet Type, Depending on EUT capabilities, e.g. 2-
DQPSK and 8DPSK packet type with full Payload Length" DH5 with a 679 byte payload and 3-DH5
payload length with a 1021 byte payload
The modulation measurements are in accordance with the test specification for Blue-
tooth wireless technology, see test purpose RF/TRM/CA/BV-11-C.
To obtain the modulation characteristics in accordance with the test specification, pro-
ceed as follows:
● Select the measurement filter ("Measurement Control > Filter > EDR Filter Band-
width: Narrow"
● Use the default statistical settings ("Measurement Control > Modulation > Statistic
Count: 10")
● Provide a signal with the following characteristics and adjust the "Bluetooth Input
Signal" settings accordingly.
Maximum output power Expected nominal power Select according to the power class of the
EUT
Hopping off, three consecutive measure- Frequency Use 2402 MHz, 2441 MHz, 2480 MHz
ments at lowest, mid, and highest operat-
ing frequency.
EUT transmits the longest supported π/4 "Bluetooth Input Signal > Packet Type, Depending on EUT capabilities, e.g. 2-
DQPSK and 8DPSK packet type with full Payload Length" DH5 with a 679 byte payload and 3-DH5
payload length with a 1021 byte payload
Payload length
Due to the different measurement procedures, some of the modulation results are valid
only if the packet contains enough payload bytes. A packet configuration according to
the test specification for Bluetooth wireless technology ensures a sufficient "Payload
Length" for all modulation results.
To obtain the adjacent channel power (ACP), the R&S CMW automatically uses the
basic test settings from the test specification for Bluetooth wireless technology: 100
kHz resolution bandwidth (fixed), "Statistic Count": 10 (default). The measurement is
gated to cover only the DPSK portion of the packet. The required ACP results corre-
spond to the "Maximum" values in the ACP diagrams.
To measure in line with test purpose RF/TRM/CA/BV-13-C, provide a signal with the
following characteristics, and adjust the "Bluetooth Input Signal" settings accordingly.
Table 7-33: ACP measurement settings
Maximum output power Expected nominal power Select according to the power class of the
EUT
Hopping off, three consecutive measure- Frequency Use 2405 MHz, 2441 MHz, 2477 MHz
ments at lowest operating frequency + 3
MHz, mid frequency, and highest operat-
ing frequency – 3 MHz.
EUT transmits the longest supported π/4 "Bluetooth Input Signal > Packet Type: 2- Depending on EUT capabilities, e.g. 2-
DQPSK packet type with maximum length DH1/3/5" DH5 with a 679 byte payload
payload
For the 79 channels gated ACP measurements in the combined signal path scenario,
the ACP trigger of the "Bluetooth Signaling" application is automatically selected.
The measurement method of the R&S CMW is faster than the method suggested in the
specification but provides equivalent results.
The phase encoding measurement is available only in combined signal path scenario
to obtain the phase encoding characteristics in accordance with the test specification
for Bluetooth wireless technology - RF/TRM/CA/BV-12-C .
Test procedure:
1. Establish the TX test mode connection with whitening turned off via "Bluetooth Sig-
naling" application. Disable frequency hopping.
3. Select 2-DH1 or 2-EV3 packets with maximum length payload containing PRBS9.
6. If the EUT supports 8DPSK modulation, repeat steps step 4 and step 5 using 3-
DH1 or 3-EV3 packets with maximum length payload containing PRBS9.
Maximum output power "Power Up" hotkey Via the signaling application
Hopping off, lowest operating frequency. Frequency Set 2402 MHz via signaling application
EUT transmits the EDR "General Setup > Burst Type" Set "Enhanced Data Rate" via the signal-
ing application
Stage one: measurement for 2-DH1 or 2- "Bluetooth Signal Characteristics > Set "2-DH1" or "2-DH3" via the signaling
EV3 packets with maximum payload Enhanced Data Packet Type" application
length
Stage two (if supported by the EUT): mea- "Bluetooth Signal Characteristics > Set "3-DH1" or "3-DH3" via the signaling
surement for 3-DH1 or 3-EV3 packets Enhanced Data Packet Type" application
with maximum payload length
EUT transmits a PRBS9 pattern as pay- "Bluetooth Signal Characteristics > Set "PRBS9" via the signaling application
load Enhanced Data Rate Pattern Type"
This application sheet describes the use of the "Bluetooth Measurement" for Low
Energy (LE) tests in line with the test specification for Bluetooth wireless technology
RF-PHY, version 5.1.0.
The LE conformance tests rely on the availability of the direct test mode at the EUT,
which is part of the core specification for Bluetooth wireless technology. In this mode,
the EUT transmits LE test packets with configurable payload size up to 256 bytes.
Even if the R&S CMW provides also measurements on advertiser packets, this appli-
cation sheet focuses on LE test packets only.
LE test packets are described in the "Air Interface Packets" section of the core specifi-
cation for Bluetooth wireless technology, volume 6, part B.
Concerning frequencies, the test specification differentiates between the profile roles
implemented.
For devices or products supporting both connectable and non-connectable roles (e.g.
peripheral and broadcaster roles), the frequencies for testing have to be as for the con-
nectable roles.
To measure in accordance with the LE test specification, set the EUT to direct TX
mode at maximum output power. Turn off whitening and frequency hopping.
At the R&S CMW, the following settings are always required:
● "Expected Nominal Power" according to the EUT's maximum output power (must
be between –20 dBm and +10 dBm)
● "Bluetooth Input Signal > Detection Mode: Manual"
● "Bluetooth Input Signal > Burst Type: Low Energy"
● "Bluetooth Input Signal > PHY"
● "Bluetooth Input Signal > Coding (only for LE coded PHY)"
● "Bluetooth Input Signal > Packet Type: RF_PHY_TestRef or RF_PHY_Tes-
tRef_CTE"
● "Bluetooth Input Signal > Payload Length: up to 256 bytes"
The power measurements are in accordance with the test specification for Bluetooth
wireless technology, refer to the transmitter test RF-PHY/TRM/BV-01-C.
The RF output power results include average power and peak power.
To obtain the RF output power results in accordance with the test specification, pro-
ceed as follows:
● Select the wideband measurement filter ("Measurement Control > Filter > LE/LE2M
Filter Bandwidth: Wide".
● Provide a signal with the following characteristics and adjust the "Bluetooth Input
Signal" settings accordingly.
Table 7-38: Power measurement settings
Three consecutive measurements at low- Set frequency to See Chapter 7.3.3.1, "Frequencies for
est, middle, and highest transmit fre- ● 2402 MHz, 2440 MHz and 2480 MHz Testing", on page 371
quency for connectable devices
● 2402 MHz, 2426 MHz and 2480 MHz
for non-connectable devices
Transmit test packages with PRBS9 "Bluetooth Input Signal > Pattern Type: "Other" denotes any payload pattern
sequence as payload Other" except "11110000" and "10101010".
The modulation measurements are in accordance with the test specification for Blue-
tooth wireless technology, refer to the following transmitter tests:
● RF-PHY/TRM/BV-05-C "Modulation characteristics" for LE 1M PHY
● RF-PHY/TRM/BV-10-C "Modulation characteristics" for LE 2M PHY
● RF-PHY/TRM/BV-09-C "Stable modulation characteristics" for LE 1M PHY
● RF-PHY/TRM/BV-11-C "Stable modulation characteristics" for LE 2M PHY
● RF-PHY/TRM/BV-06-C "Carrier frequency offset and drift" for LE 1M PHY
● RF-PHY/TRM/BV-12-C "Carrier frequency offset and drift" for LE 2M PHY
● RF-PHY/TRM/BV-16-C "Carrier frequency offset and drift" for LE 1M PHY with CTE
● RF-PHY/TRM/BV-17-C "Carrier frequency offset and drift" for LE 2M PHY with CTE
To obtain the modulation characteristics in accordance with the test specification, pro-
ceed as follows:
● Select narrowband measurement filter ("Measurement Control > Filter > LE/LE2M
Filter Bandwidth: Narrow"
● Use the statistical settings for 10 consecutive test packets ("Measurement Control
> Modulation > Statistic Count: 10")
● Provide a signal with the following characteristics and adjust the "Bluetooth Input
Signal" and "PHY" settings accordingly.
According to the test specification for Bluetooth wireless technology, certain modulation
measurements require specific payload pattern. The following table gives an overview
for LE uncoded PHY.
Table 7-39: Pattern and modulation results for LE uncoded PHY
Payload bit pattern "Bluetooth Input Signal > Pattern Type: 10101010"
Transmit a "11110000" payload bit pattern "Bluetooth Input Signal > Pattern Type: 11110000"
The modulation measurements are in accordance with the test specification for Blue-
tooth wireless technology, refer to the following transmitter tests:
● RF-PHY/TRM/BV-13-C "Modulation characteristics"
● RF-PHY/TRM/BV-14-C "Carrier frequency offset and drift"
The modulation measurements are in accordance with the test specification for Blue-
tooth wireless technology.
To obtain the modulation characteristics in accordance with the test specification, pro-
ceed as follows:
● Use the statistical settings for 10 consecutive test packets ("Measurement Control
> Modulation > Statistic Count: 10")
● Provide a signal with the following characteristics and adjust the "Bluetooth Input
Signal", "PHY", and "Coding" settings accordingly.
Tests for LE coded PHY require the payload pattern '11111111'.
● For the Δf1 modulation results, refer to RF-PHY/TRM/BV-13-C
● For the frequency offset and drift results, refer to RF-PHY/TRM/BV-14-C
To obtain the results in accordance with the test specification, provide a signal with the
following characteristics and adjust the "Bluetooth Input Signal" settings accordingly.
Table 7-42: Modulation measurement settings
To obtain the adjacent channel power (ACP), the R&S CMW automatically uses the
100 kHz resolution bandwidth required in the test specification for Bluetooth wireless
technology.
To measure in line with TX test RF-PHY/TRM/BV-03-C (In-band emissions at LE 1M
PHY) or RF-PHY/TRM/BV-08-C (In-band emissions at LE 2M PHY), proceed as fol-
lows:
● Select the wideband measurement filter ("Measurement Control > Filter > LE/LE2M
Filter Bandwidth: Wide"
● Provide a signal with the following characteristics and adjust the "Bluetooth Input
Signal" settings accordingly.
Three consecutive mea- Set "Frequency" to See Chapter 7.3.3.1, "Frequencies for Testing",
surements at lowest, ● 2406 MHz, 2440 MHz and 2476 MHz for con- on page 371
middle, and highest nectable devices
transmit frequency ● 2402 MHz, 2426 MHz and 2480 MHz for non-
connectable devices
Transmit a PRBS9 "Bluetooth Input Signal > Pattern Type: Other" "Other" denotes any pattern except "11110000"
sequence as payload and "10101010".
Measurement time: 1 s "Measurement Control > Spectrum > ACP Statistic See "Statistical settings for ACP measurements on
Count": 1 for the payload length of 255 bytes LE packets" in Chapter 7.2.8.6, "Scope of Spec-
trum Measurements", on page 361.
The power limits specified in the "in-band emissions" test cases apply to the "Maxi-
mum" statistical measurement results.
For the all channels ACP measurements in the combined signal path scenario, use the
ACP trigger of the "Bluetooth Signaling" application (option R&S CMW-KS611
required).
A Bluetooth combined signal path measurement requires one of the following option
combinations:
● Signaling: Option R&S CMW-KS600/-KS602 or /-KS603 for BR/EDR (classic)
Measurement: R&S CMW-KM610 (normal mode)
● Signaling: R&S CMW-KS610 for BR/EDR test mode
Measurement: R&S CMW-KM610 (as per Bluetooth test specification)
● Signaling: R&S CMW-KS601 for signaling connection tests LE 1M PHY (uncoded)
Measurement: R&S CMW-KM611 (normal mode with LE connection tests)
● Signaling: R&S CMW-KS720 for signaling connection tests using LE 2M PHY
(uncoded) or LE coded PHY
An established connection to the EUT is a prerequisite for all signaling tests, including
the combined signal path measurement described in this application sheet.
To set up a connection:
1. Preset your R&S CMW to ensure a definite instrument state.
3. Open the "Bluetooth Signaling" application, e.g. from the task bar (press "TASKS"
to open the task bar).
If the application is not present in the task bar, enable it in the "Generator/Signaling
Controller" dialog (press "SIGNAL GEN" to open the dialog).
5. In section "RF Settings", select a bidirectional RF connector for input and output.
This example uses RF 1 COM.
If necessary, also adjust the "External Attenuation" settings.
6. For a connection to the default device, set its BD address and the page scan repe-
tition mode in section "Connection" > "Paging" > "Classic" > "Default EUT".
8. In the main view of the signaling application, adjust the "General Setup", "RF
Setup" and "Signal Characteristics" settings to the capabilities of your EUT.
9. To reach standby status of the R&S CMW, press [ON | OFF] key.
12. Wait for the inquiry process to finish or press "Stop Inquiry" at any time to return to
the standby state.
13. Select the desired device "For Paging". If the R&S CMW has not discovered any
EUT, only the default device is available for selection.
14. Press the "Connect "or "Connect Test Mode" hotkey to set up a connection.
Note the connection states displayed in the main view and wait until the EUT state
indicates "Connected".
After the EUT has connected, the main view provides EUT information.
While an established connection is available, the uplink signal of the EUT can be moni-
tored using a "Bluetooth TX Measurement" provided by option R&S CMW-KM610 or
R&S CMW-KM611.
To ensure compatible measurement settings, the measurement must be coupled to the
"Bluetooth Signaling" application. This coupling is done by selecting the combined sig-
nal path scenario in the measurement. As a result the measurement application uses
the most important settings of the signaling application, e.g. the signal routing and ana-
lyzer settings.
The following example applies to a multi-evaluation measurement.
Proceed as follows:
1. In the "Bluetooth Signaling" application, use the "Bluetooth Multi Eval." softkey to
switch to the multi-evaluation measurement.
The measurement application is opened and the combined signal path scenario is
selected automatically. The trigger signal provided by the signaling application is
selected automatically as well.
4. To enlarge a diagram presented in the main view, perform one of the following
actions:
a) Double-click it using a connected mouse.
b) Select it by turning the rotary knob. Open it by pressing the rotary knob.
In the combined signal path, the signal routing and analyzer settings are controlled by
the signaling application. The TX measurement displays the corresponding signaling
settings instead of its own settings. The configurable signal routing and analyzer set-
tings of the signaling application can be modified both via the measurement GUI and
via the GUI of the signaling application. To configure the signal routing and analyzer
settings via remote commands, the commands of the signaling application have to be
used.
To turn the measurement on or off, select the control softkey and press [ON | OFF] or
[RESTART | STOP]. Alternatively, right-click the control softkey.
The softkey shows the current measurement state. Additional measurement substates
can be retrieved via remote control.
Remote command:
INITiate:BLUetooth:MEAS<i>:MEValuation etc.
FETCh:BLUetooth:MEAS<i>:MEValuation:STATe?
FETCh:BLUetooth:MEAS<i>:MEValuation:STATe:ALL?
Rx Meas (Softkey)
The "Rx Measurement" with ARB generator on advertisers is included in the Bluetooth
measurement application. To access the measurement, press the softkey "Rx Meas" in
the Bluetooth measurement or select the tab "Rx Meas".
Non-signaling OTA Rx tests on advertisers are only supported with an
R&S CMW100/CMW with MUA. Option R&S CMW-KD611 is required.
The softkey shows the current measurement state. Additional measurement substates
can be retrieved via remote control.
Remote command:
INITiate:BLUetooth:MEAS<i>:RXQuality etc.
FETCh:BLUetooth:MEAS<i>:RXQuality:STATe?
FETCh:BLUetooth:MEAS<i>:RXQuality:STATe:ALL?
The softkey shows the current measurement state. Additional measurement substates
can be retrieved via remote control.
Remote command:
For PER:
INITiate:BLUetooth:MEAS<i>:DTMode:RXQuality:PER etc.
FETCh:BLUetooth:MEAS<i>:DTMode:RXQuality:PER:STATe?
For PER search:
INITiate:BLUetooth:MEAS<i>:DTMode:RXQuality:SEARch:PER etc.
FETCh:BLUetooth:MEAS<i>:DTMode:RXQuality:SEARch:PER:STATe?
Tx measurement results
The Tx measurement results are displayed in a "Multi Evaluation" tab. The multi-evalu-
ation Tx measurement provides an overview dialog and a detailed view for each dia-
gram in the overview. Measurement results depend on the packet type.
Use the "Display" parameters to select the different multi-evaluation views and to
change their appearance and contents.
The results to be measured and displayed in the overview can be limited using the hot-
key "Assign Views", see "Assign Views" on page 446.
You can enlarge one of the diagrams in the overview and show a detailed view with
additional measurement results, see Chapter 7.4.2.23, "Selecting and Modifying
Views", on page 424.
Rx measurement results
The "Rx Meas" tab shows the measurement results in a table. The type of displayed
results depends on the selected measurement mode.
The "Config" hotkey opens either the configuration dialog of the Rx measurement or
the configuration dialog of the Bluetooth multi-evaluation measurement application,
depending on which softkey is active.
For a detailed description of the results, see Chapter 7.4.2.20, "LE: Rx Measurement
Results for Advertisers", on page 419.
The views and tabs are described in the following sections.
● BR: Measurement Diagrams ................................................................................383
● BR: Statistical Power vs. Time Results ................................................................ 385
● BR: Statistical Modulation Results ....................................................................... 386
● BR: Spectrum 20 dB Bandwidth Results ..............................................................390
● BR: Spectrum Frequency Range Results ............................................................ 391
● BR: Spectrum ACP Results ................................................................................. 392
● EDR: Measurement Diagrams ............................................................................. 395
● EDR: Statistical Power vs. Time Results ............................................................. 397
● EDR: Statistical Modulation Results .....................................................................398
● EDR: Differential Phase Encoding Results .......................................................... 400
● EDR: Spectrum Gated ACP Results .................................................................... 401
● Normal Mode Classic: Measurement Diagrams ...................................................403
● Normal Mode Classic: Statistical Power vs. Time Results ...................................405
● Normal Mode Classic: Statistical Modulation Results .......................................... 406
● LE: Tx Measurement Diagrams ........................................................................... 406
● LE: Statistical Power vs. Time Results .................................................................409
● LE: Statistical Modulation Results ........................................................................410
● LE: Spectrum ACP Results .................................................................................. 415
● LE with CTE: Additional Results .......................................................................... 417
● LE: Rx Measurement Results for Advertisers....................................................... 419
● LE: Rx Measurement Results for PER..................................................................421
● LE: Rx Measurement Results for PER Search..................................................... 422
● Selecting and Modifying Views............................................................................. 424
● Using Markers....................................................................................................... 424
● Common View Elements.......................................................................................425
The "Overview" dialog shows several or all the detailed views in a single diagram.
The "Power Scalars" view shows an overview of power results and the corresponding
statistics.
● "Packet Timing": Timing error between the expected and actual start of the first
symbol of the Bluetooth burst. As the expected start is defined by the signaling trig-
ger, this setting is relevant for combined signal path only (options R&S CMW-
KS600/-KS610).
For query of the results via remote control, see Chapter 7.6.3.13, "Power Results (BR,
Single Values)", on page 577.
The "TX Measurement Modulation" view shows an overview of modulation results and
the corresponding statistics.
Some of the results require a special payload "Pattern Type"; see Chapter 7.3.1.2,
"Modulation Measurements", on page 364. See also Freq. Dev. Δf2.
Δf2 99.9%
Frequency deviation value Δf2 above which 99.9% of all measured Δf2 values occur.
A Δf2 99.9% value of 115 means that 99.9% of all measured Δf2 values are above or
equal to 115 kHz.
This measurement spans over all packets with sufficient payload length.
Δf2 99.9% measurement requires a payload length of at least 2 bytes and payload pat-
tern "10101010".
See also Freq. Dev. Δf2.
Freq. accuracy
The frequency accuracy is the difference between the nominal channel frequency fTX
and the initial carrier frequency f0, measured over the packet preamble:
The preamble is a 4-bit pattern "1010" or "0101"' at the beginning of each packet. To
measure the initial carrier frequency, the R&S CMW includes by measurement also
preamble of 4 μs (bit lengths) in total. It means the R&S CMW integrates also the fre-
quency of the demodulated signal from the center of the first preamble bit to the center
of the first bit following the preamble.
No payload bits are involved in the frequency accuracy calculation.
Freq. drift
Maximum difference between the measured initial carrier frequency f0, and the carrier
frequencies fn, where n = 1 ... N, measured within the payload.
To obtain the latter, the payload is grouped into 10-bit groups as shown in the following
figure:
This measurement does not include the payload header or the CRC bits.
The first bit and incomplete 10-bit groups are not considered for the calculation.
This measurement requires payload pattern "10101010" and a minimum payload
length of 2 bytes. Otherwise this measurement result is invalid.
The first 4 bits and incomplete 8-bit groups (the last 4 bits) are not considered for the
calculation.
This measurement requires payload pattern "11110000" and a minimum payload length
of 2 bytes. Otherwise this measurement result is invalid.
The first bit and incomplete 8-bit groups (the last 7 bits) are not considered for the cal-
culation.
This measurement requires payload pattern "10101010" and a minimum payload
length of 2 bytes. Otherwise this measurement result is invalid.
Nominal power
Average burst power during the carrier-on state, measured within the "Basic Rate Filter
Bandwidth".
If automatic burst detection is active ("Input Signal > Detection Mode: Auto"), the "Mod-
ulation Scalars" view also shows the detected packet type, pattern type, and payload
length. Automatic detection mode is indicated in the upper right corner.
In "ACP 79 Channels" mode, the number of off slots has to be displayed.
The "Pattern Yield" is the percentage of detected packets with a specific payload pat-
tern type.
The modulation ratio Δf2 avg / Δf1 avg is the ratio of the smallest measured frequency
deviation min(Δf2 avg) to the largest one max(Δf1 avg). This value requires at least
one BR packet with a "11110000" and one with a "10101010" payload pattern; see defi-
nition of Δf2 and Δf1 above.
For query of the results via remote control, see Chapter 7.6.3.17, "Modulation Results
(BR, Single Values)", on page 588.
The output fields in the "Spectrum 20 dB Bandwidth" view show an overview of the 20
dB bandwidth results.
The 20 dB bandwidth (occupied bandwidth, OBW) is the width of the frequency band
around the peak of the emission where the transmit power drops by less than 20 dB. It
is measured as the difference between the two frequencies fH – fL, where:
● "fH" denotes the highest frequency at which the transmit power drops 20 dB below
the peak power.
● "fL" denotes the smallest frequency at which the transmit power drops 20 dB below
the peak power.
The 20 dB bandwidth results are based on the "Maximum" spectral trace and obtained
using a 10 kHz resolution bandwidth. A small 20 dB bandwidth means that the transmit
power is focused, and hence the off-carrier emissions are small. An example is shown
below.
For query of the results via remote control, see Chapter 7.6.3.21, "Spectrum Results
(BR, Single Values)", on page 628.
The scalar output fields view show an overview of the frequency range results.
The frequency range is the width of the frequency band around the center frequency
where the transmit power drops by less than specified threshold value. The frequen-
cies fH and fL are measured, where:
● "fH" denotes the highest frequency at which the transmit power drops below the
specified threshold.
● "fL" denotes the smallest frequency at which the transmit power drops below the
specified threshold.
● Nominal power: average burst power during the carrier-on state, measured within
the "Basic Rate Filter Bandwidth".
The frequency results are based on the "Average" spectral trace and obtained using a
100 kHz resolution bandwidth. Results fL and fH must be within the allowed frequency
band 2.4 GHz to 2.4835 GHz. An example is shown below.
Read Chapter 7.3.1.4, "Frequency Range Measurement", on page 366 to measure the
spectrum frequency range in line with the test specification for Bluetooth wireless tech-
nology.
For query of the results via remote control, see Chapter 7.6.3.21, "Spectrum Results
(BR, Single Values)", on page 628.
The "Spectrum ACP" table view for BR packets shows the adjacent channel power
results.
Switch the appearance of the results for "Spectrum ACP" measurements via "Display"
softkey > "Diagram View / Table View" hotkey.
Diagram view
For the diagram view, refer to Chapter 7.4.2.1, "BR: Measurement Diagrams ",
on page 383.
Table view
There are two possible "Spectrum ACP" table views. The view depends on the ACP
measurement mode:
● ACP 79 channels (Bluetooth frequencies only, see Chapter 7.2.6.1, "BR/EDR:
Channels", on page 344) or
● ACP +/-10 channels (any frequencies)
● "Nominal Power": Average burst power during the carrier-on state, measured in
the "Basic Rate Filter Bandwidth".
The measurement procedure of the R&S CMW is faster than the procedure described
in the test specification for Bluetooth wireless technology, but it provides equivalent
results. See also "Statistical settings for ACP measurements" in Chapter 7.2.8.6,
"Scope of Spectrum Measurements", on page 361.
Read Chapter 7.3.1.5, "Spectrum ACP Measurement", on page 367 to measure the
ACP in line with the test specification for Bluetooth wireless technology.
For query of the results via remote control, see Chapter 7.6.3.21, "Spectrum Results
(BR, Single Values)", on page 628.
The "Overview" dialog shows several or all the detailed views in a single diagram.
Figure 7-37: Bluetooth multi-evaluation: overview in combined signal path scenario (EDR)
● "Guard Period": Length of the guard band between the packet header and the
EDR synchronization sequence. The guard band is a field used for physical layer
change of modulation scheme.
● "Packet Timing": Timing error between the expected and actual start of the first
symbol of the Bluetooth burst. As the expected start is defined by the signaling trig-
ger, this setting is relevant for combined signal path only (options R&S CMW-
KS600/-KS610).
● "Nominal Power": Average burst power during the carrier-on state, measured in
the EDR filter bandwidth.
For query of the results via remote control, see Chapter 7.6.3.14, "Power Results
(EDR, Single Values)", on page 578.
To be valid the DPSK results require a minimum payload length of 6 (2-DHx packets)
or 11 (3-DHx packets), corresponding to one complete 50-symbol block.
For additional screen elements, refer to Chapter 7.4.2.25, "Common View Elements",
on page 425.
For query of the results via remote control, see Chapter 7.6.3.18, "Modulation Results
(EDR, Single Values)", on page 593.
The purpose of the EDR differential phase encoding measurement is to verify the
phase encoding of the data by the EUT.
The measurement is only available in the combined signal path scenario.
The following results of the EDR differential phase encoding measurement are provi-
ded:
● "Bit Error Rate": number of bit errors in the received burst, as a percentage of the
total number of bits received.
● "Packets With 0 Bit Errors": number of bit error free packets received, as a per-
centage of all the bursts received
● "Sync Bit Errors": number of errors on sync bit, refer to Figure 7-13
● "Trailer Bit Errors": number of errors on trailer bit, refer to Figure 7-13
● "Nominal Power": average burst power during the carrier-on state, measured
within the "Enhanced Data Rate Filter Bandwidth".
For query of the results via remote control, see Chapter 7.6.3.25, "Differential Phase
Encoding Results (EDR, Single Values)", on page 636.
The "Spectrum Gated ACP" table view shows all adjacent channel power results for
EDR packets. The measurement is similar to the ACP measurement for BR packets
(see Chapter 7.4.2.6, "BR: Spectrum ACP Results ", on page 392), the differences are
described below.
According to the test specification for Bluetooth wireless technology (test purpose
RF/TRM/CA/BV-13-C), the ACP measurement for EDR packets is gated to cover only
the DPSK portion of the packet.
The view contains the following results:
● "(Relative) Channel": Bluetooth regulatory or relative channel number.
– With "ACP +/-10 Channels" mode, the channel number corresponds to the fre-
quency spacing in MHz relative to the center channel. Channel no. 0 is the
channel defined by the selected RF frequency.
– With "ACP 79 Channels", the channel number corresponds to the channels
within the Bluetooth regulatory range (channels 0 to 78, corresponding to RF
frequencies 2402 MHz, 2403 MHz ... 2479 MHz).
See "ACP Measurement Mode" on page 444.
● "Frequency" in MHz: Center frequency of the (relative) channels.
● "Ptx" in dBm: Gated ACP results for all channels. The results correspond to the
integrated powers that the Bluetooth device transmits in the Bluetooth channels.
According to the test specification for Bluetooth wireless technology, the ACP is the
sum of the maximum powers PTXi at 10 distinct, equidistant frequencies fi distrib-
uted across the channel width:
PTX (f) = ∑(PTXi ), i = 1 ... 10
See also Figure 7-45.
● "Nominal Power": Average burst power during the carrier-on state, measured in
the "Enhanced Data Rate Filter Bandwidth".
For query of the results via remote control, see Chapter 7.6.3.22, "Spectrum Results
(EDR, Single Values)", on page 631.
The R&S CMW provides diagrams and statistical results for normal mode BR/EDR
measurements in combined signal path.
Table 7-44: Supported BR/EDR measurements in test mode and normal mode
"Power vs Time" X X X
"DEVM" X
"Phase Difference" X
"Spectrum 20 dB Bandwidth" X
"Frequency range" X
1) Only in combined signal path, refer to Chapter 7.2.1.3, "Parallel Signaling and Measurement",
on page 332
2) Only GFSK header portion (first 126 symbols) analyzed
3) Only "ACP+/-10 channel" mode supported
4) Only average power results
BR/EDR measurements in normal mode require combined signal path with a measure-
ment option R&S CMW-KM610 and a basic signaling option R&S CMW-KS600/-KS602
or /-KS603.
The "Overview" dialog shows several or all the detailed views in a single diagram.
The "Power Scalars" view shows an overview of power results and the corresponding
statistics.
The power results table contains "Average Power": Average burst power during the
carrier-on state.
For query of the results via remote control, see Chapter 7.6.3.16, "Power Results (Nor-
mal Mode, Single Values)", on page 583.
The "TX Measurement Modulation" view shows an overview of modulation results and
the corresponding statistics. The * sign indicates the results provided only with an
R&S CMW with MUA.
The "TX Measurement Modulation" table contains the same results as BR measure-
ments in test mode, see Chapter 7.4.2.3, "BR: Statistical Modulation Results ",
on page 386.
For query of the results via remote control, see Chapter 7.6.3.20, "Modulation Results
(Normal Mode, Single Values)", on page 611.
The R&S CMW provides measurement diagrams and statistical results of Tx measure-
ments (tab "Multi Evaluation").
direct test (test direct test (test connection test 1) others 4) (advertis-
packets) packets) (data chan. pack- ers)
ets)
"Power vs Time" X X X X
"Power vs Slot"5) X
"Frequency Deviation" X X X X
"Modulation Scalars" X X X X
1) Only in combined signal path, refer to Chapter 7.2.1.3, "Parallel Signaling and Measurement", on page 332
2) Only "ACP+/-5 channel" mode supported (21 half-channels)
3) Only average power results
4) Only in non-signaling stand alone operation
5) Only LE with CTE
6)All Tx measurements, only spot check Rx test, see Chapter 7.4.2.20, "LE: Rx Measurement Results for Advertisers",
on page 419
Option R&S CMW-KM611 is required for LE 1M PHY (uncoded). For LE 2M PHY and
LE coded PHY, option R&S CMW-KM721 is also required.
Measurements on LE with CTE require an option R&S CMW-KM722.
LE measurements in normal mode require combined signal path with a measurement
option R&S CMW-KM611 and a basic signaling option R&S CMW-KS601 for uncoded
LE 1M PHY. For LE 2M and LE code PHY, options R&S CMW-KM721 and R&S CMW-
KS720 are also required.
The "Overview" dialog shows several or all the detailed views in a "Multi Evaluation"
tab.
For enabled limit check, two limit lines are displayed. For limit configuration, see
"ACP (BR, LE)" on page 462.
– Red limit line "Ptx" is the upper limit for the adjacent channel power in 2 MHz
channels fTX ± 4 MHz
– Green limit line "Exc." is upper limit for the adjacent channel power in 2 MHz
channels fTX ±6 MHz, fTX ±8 MHz, ...
For scalar results, refer to Chapter 7.4.2.18, "LE: Spectrum ACP Results ",
on page 415.
For query of the diagram contents via remote control, see:
● Chapter 7.6.3.26, "Power Trace Results", on page 637
● Chapter 7.6.3.27, "Modulation Trace Results", on page 640
● Chapter 7.6.3.28, "Spectrum Trace Results", on page 642
The "TX Measurement Power vs. Time" view displays statistical power results. Mea-
surements on test packets and advertiser packets support all results. Measurements
with LE connection tests provide only average power results.
The "TX Measurement Modulation" view shows an overview of modulation results and
the corresponding statistics. For the supported results, refer to Table 7-1.
● For measurements on test packets "RF_PHY_TestRef", all modulation results are
supported. Some of the results require particular physical layer or a special pay-
load "Pattern Type". See Chapter 7.3.3.4, "Modulation Measurements LE Uncoded
PHY", on page 373 and Chapter 7.3.3.5, "Modulation Measurements LE Coded
PHY S = 8", on page 375.
See also "Additional results in automatic detection mode" on page 415.
● For measurements on test packets "RF_PHY_TestRef_CTE", additional results for
CTE slots are provided.
Refer to Chapter 7.4.2.19, "LE with CTE: Additional Results ", on page 417.
Access: "Display" softkey > "CTE Results" hotkey
The "TX Measurement Modulation" result table contains the following values:
Δf2 99.9%
Frequency deviation value Δf2 above which 99.9% of all measured Δf2 values occur.
A Δf2 99.9% value of 185 means that 99.9% of all measured Δf2 values are above or
equal to 185 kHz.
This measurement spans over all packets with sufficient payload length.
Δf2 99.9% measurement requires a payload pattern "10101010".
The results are only relevant for LE uncoded PHY (LE 1M PHY, LE 2M PHY).
See also "Freq. Dev. Δf2" on page 414.
Δf1 99.9%
Δf1 99.9% is frequency deviation value Δf1 above which 99.9% of all measured Δf1
values occur. The result is only relevant for LE coded PHY with coding S=8.
Freq. accuracy
The frequency accuracy is the difference between the nominal channel frequency fTX
and the initial carrier frequency f0, measured over the packet preamble:
Freq. offset
Maximum difference between the nominal channel frequency fTX and carrier frequen-
cies fn, n = 1 ... N measured over the packet preamble and payload:
Freq. offset = fm – fTX , where m = arg maxn ∈ {1, ..., N}(|fn – fTX |)
This measurement does not include the payload header, payload length field or the
CRC bits. The frequency offset measurement requires a payload length of at least 2
bytes.
To measure the carrier frequencies within the packet payload, the R&S CMW proceed
as follows:
● For LE 1M PHY, the R&S CMW integrates the frequency of the demodulated signal
in non-overlapping 10-bit intervals ('0101010101'), starting from the second pay-
load bit. The first bit and incomplete 10-bit groups are not considered for the calcu-
lation.
This measurement requires a payload length of at least 2 bytes and payload pat-
tern "10101010".
● For LE 2M PHY, the R&S CMW integrates the frequency of the demodulated signal
in non-overlapping 20-bit intervals, starting from the second payload bit. The first
bit and incomplete 20-bit groups are not considered for the calculation.
This measurement requires a payload length of at least 3 bytes and payload pat-
tern "10101010".
● For LE coded PHY, the R&S CMW integrates the frequency of the demodulated
signal in non-overlapping 16-symbol intervals, starting from the symbol 31. The first
30 symbols and the last 34 symbols are not considered for the calculation.
This measurement requires a payload length of 255 bytes and payload pattern
"11111111".
Freq. drift
Maximum difference between the measured initial carrier frequency f0 and the carrier
frequencies fn, n = 1 ... N, measured within the test packet payload (see Freq. offset) :
This measurement does not include the payload header, payload length field or the
CRC bits.
LE 1M PHY and LE 2M PHY measurements require a payload pattern "10101010". LE
coded PHY (S = 8) measurements require a payload pattern "11111111".
Range The first 4 bits and incomplete 8- Measures from the beginning of
bit groups are not considered for the 31st symbol in the payload.
the calculation. The last 34 symbols in the pay-
load are disregarded.
To obtain the Δf1 results in accordance with the Bluetooth LE test specification, the
R&S CMW proceeds as follows:
● Divides the payload into its "00001111" 8-bit subsequences
● Each bit of the payload is oversampled at least 32 times
● For each "00001111" 8-bit subsequence, the average frequency f1ccf is calculated
● For each of the "00001111" 8-bit subsequences, the frequency deviation of bits 2,
3, 6 and 7 from favg are calculated as Δf1max, i
The first four bits and incomplete 8-bit groups (the last 4 bits) are not considered for
the calculation.
This measurement requires a minimum payload length of 2 bytes and payload pattern
"10101010".
The results are only relevant for LE uncoded PHY (LE 1M PHY, LE 2M PHY).
If automatic burst detection is active ("Input Signal > Detection Mode: Auto"), the "Mod-
ulation Scalars" view also shows the detected pattern type, and payload length. Auto-
matic detection mode is indicated in the upper right corner.
In "LE All Channels" mode, the number of off slots has to be displayed. This mode is
not supported for advertisers and test packets with LE coded PHY.
The "Pattern Yield" is the percentage of detected packets with a specific payload pat-
tern type. This result is not provided for LE coded PHY.
The modulation ratio Δf2 avg / Δf1 avg is the ratio of the smallest measured frequency
deviation min(Δf2 avg) to the largest one max(Δf1 avg). This value requires at least
one LE packet with a "11110000" and one with a "10101010" payload pattern; see defi-
nition of Δf2 and Δf1 above. This result is not provided for LE coded PHY.
Switch the appearance of the results for "Spectrum ACP" measurements via "Display"
softkey > "Diagram View / Table View" hotkey.
Diagram view
For the diagram view, refer to Chapter 7.4.2.15, "LE: Tx Measurement Diagrams ",
on page 406.
Table view
The "Spectrum ACP" table view for LE packets shows the adjacent channel power
results.
There are two possible "Spectrum ACP" table views. The view depends on the ACP
measurement mode:
● LE all channels (LE frequencies only, see Chapter 7.2.6.4, "LE: Channels",
on page 346) or
● ACP +/-5 channels (any frequencies)
In-band emissions are analyzed in the 1 MHz half-channels (compared to the LE chan-
nel bandwidth of 2 MHz) centered at 2401 MHz, 2402 MHz, ... , 2481 MHz. Refer to
the LE test specification RF PHY for Bluetooth wireless technology.
– With "LE All Channels" mode, the channel number follows the LE scheme
(channels 0 to 39, corresponding to RF frequencies 2402 MHz, 2404 MHz ...
2480 MHz). Test specification for Bluetooth wireless technology defines in-band
emission measurements only for test packets with LE 1M PHY (uncoded) and
LE 2M PHY (uncoded). LE coded PHY and advertiser packets are not suppor-
ted in "LE All Channels" mode.
In both modes, frequencies mid way between two valid LE channels is indicated by
dashes.
See "ACP Measurement Mode" on page 444.
● "Frequency" in MHz: Center frequency of the respective half-channel.
● "Ptx" in dBm: ACP results for all half-channels.
According to the Bluetooth LE test specification, the ACP is the sum of the maxi-
mum powers PTXi at 10 distinct, equidistant frequencies fi distributed across the
half-channel width. The half-channel width is = 1 MHz.
● "No. of Exceptions": Number of half-channels in which the recorded PTX value is
greater than "ACP > Low Energy > Exceptions PTX" limit. The center channel
(defined by the selected LE RF channel or frequency) and 2 half-channels, each,
on either side of this center channel are excluded from this measurement.
● "Nominal Power": Burst power during the carrier-on state, measured in the "LE
Filter Bandwidth" / "LE 2M PHY Filter Bandwidth".
Follow Chapter 7.3.3.6, "Spectrum ACP Measurement", on page 375 to measure the
in-band emissions in line with the test specification for Bluetooth wireless technology.
The measurements on LE with CTE provide in addition to standard direct test results
also "TX Measurement Power vs. Slot" diagrams and statistical power and modulation
results for CTE slots.
Statistical results
Access: "Display" softkey > "Select View" hotkey > select "Modulation Scalars" view
"Display" softkey > "CTE Results" hotkey
In the modulation scalar view, additional statistical results are provided for LE with
CTE. The CTE results are limited to measurements of CTE slots only.
Remote command:
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:CTE:LENergy:LE1M:
CURRent? etc.
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:CTE:LENergy:LE2M:
CURRent? etc.
The result table indicates settings and statistical measurement results according to the
measurement mode:
Spot Check..................................................................................................................419
PER.............................................................................................................................420
Sensitivity Search........................................................................................................420
Spot Check
The table shows the following statistical results:
● "Detected Address": device address of EUT. Both public and random address
types are supported.
● "Level (CMW) [dBm]": Tx level of R&S CMW for SCAN_REQ transmission
● "Spot Check": pass / fail test verdict
Remote command:
FETCh:BLUetooth:MEAS<i>:RXQuality:ADETected:AADDress?
FETCh:BLUetooth:MEAS<i>:RXQuality:SPOTcheck?
PER
The table shows the following statistical results:
● "Detected Address" and "Level (CMW) [dBm]": see spot check results above
● "Number of Packets Received": number of SCAN_RSP packets received by the
R&S CMW since the start of a measurement
● "PER": packet error rate, the ratio of corrupted and missing SCAN_RSP packets to
the total number of transmitted SCAN_REQ packets in percent
● "Packets Sent": number of SCAN_REQ packets transmitted by the R&S CMW.
After the measurement start, this value indicates the number of transmitted packets
and the total number of packets to be transmitted. Two equal numbers indicate that
the measurement is finished.
Remote command:
FETCh:BLUetooth:MEAS<i>:RXQuality:ADETected:AADDress?
FETCh:BLUetooth:MEAS<i>:RXQuality:PER?
FETCh:BLUetooth:MEAS<i>:RXQuality:PER:RXPackets?
Sensitivity Search
The table shows the following statistical results:
Remote command:
FETCh:BLUetooth:MEAS<i>:RXQuality:ADETected:AADDress?
FETCh:BLUetooth:MEAS<i>:RXQuality:PER:RXPackets?
FETCh:BLUetooth:MEAS<i>:RXQuality:SENSitivity?
The R&S CMW provides non-signaling PER measurements in direct test mode with
ARB generator in an individual tab "PER". For the detailed description, refer to Chap-
ter 7.2.3, "Rx Measurements with ARB Generator: Direct Test Mode", on page 336.
The result table indicates the statistical measurement results to the left and settings to
the right:
Results........................................................................................................................ 421
Settings....................................................................................................................... 422
└ Stable Modulation Index............................................................................... 422
Results
The following results apply to LE PER measurements.
● "PER": packet error rate, percentage of corrupted data packets that the EUT
received.
● "Correct Packets Reported": total number of packets with a passed CRC check
received by the EUT.
● "Packets Transmitted": number of test packets transmitted by the R&S CMW.
After the start of a measurement, this value indicates the number of transmitted
packets and the total number of packets to be measured. Two equal numbers indi-
cate that the measurement is complete and the statistical depth has been reached.
● "Packets Transmitted by CMW": Total number of test packets to be transmitted
during the RX measurement.
● "Report Integrity": Report integrity adjusts the ratio of the test packets with correct
CRC transmitted by the R&S CMW.
● "Correct CRC Rate in Transmitted Packets": Ratio of the test packets with cor-
rect CRC, generated by the R&S CMW. If the report integrity is ON, the ratio is set
to 50%. If the report integrity is OFF, all packets contain correct CRC.
Remote command:
FETCh:BLUetooth:MEAS<i>:DTMode:RXQuality:PER:LENergy:LE1M? etc.
FETCh:BLUetooth:MEAS<i>:DTMode:RXQuality:PER:LENergy:LE2M? etc.
FETCh:BLUetooth:MEAS<i>:DTMode:RXQuality:PER:LENergy:LRANge? etc.
Settings
The parameters for fast access are displayed. They are the same as in the configura-
tion tree. Exception: Stable Modulation Index
● "General Setup": refer to Chapter 7.4.4, "Input Signal Settings", on page 432
● "RF Setup": refer to Chapter 7.4.3, "Signal Routing and Analyzer Settings",
on page 426
● "Signal Characteristics": refer to Chapter 7.4.4, "Input Signal Settings",
on page 432
The R&S CMW provides non-signaling PER search measurements in direct test mode
with ARB generator in an individual tab "PER Search". For the detailed description,
refer to Chapter 7.2.3, "Rx Measurements with ARB Generator: Direct Test Mode",
on page 336.
The result table indicates the statistical measurement results to the left and settings to
the right:
Results........................................................................................................................ 423
Settings....................................................................................................................... 424
Results
The following results apply to LE PER measurements.
● "PER": packet error rate, percentage of corrupted data packets that the EUT
received.
● "Correct Packets Reported": total number of packets with a passed CRC check
received by the EUT.
● "Packets Transmitted": number of test packets transmitted by the R&S CMW.
After the start of a measurement, this value indicates the number of transmitted
packets and the total number of packets to be measured. Two equal numbers indi-
cate that the measurement is complete and the statistical depth has been reached.
● "Current Level (CMW)": Displays the power level transmitted by the R&S CMW.
The initial level is configurable, see Tx Level (CMW) < PER
● "Search Result": the last TX sweep level of the R&S CMW for which the mea-
sured PER value is below the specified PER search limit, see "Limits "
on page 449
● "Packets Transmitted by CMW": Total number of test packets to be transmitted
during the RX measurement.
● "Report Integrity": Report integrity adjusts the ratio of the test packets with correct
CRC transmitted by the R&S CMW.
● "Correct CRC Rate in Transmitted Packets": Ratio of the test packets with cor-
rect CRC, generated by the R&S CMW. If the report integrity is ON, the ratio is set
to 50%. If the report integrity is OFF, all packets contain correct CRC.
Remote command:
FETCh:BLUetooth:MEAS<i>:DTMode:RXQuality:SEARch:PER:LENergy:
LE1M? etc.
FETCh:BLUetooth:MEAS<i>:DTMode:RXQuality:SEARch:PER:LENergy:
LE2M? etc.
FETCh:BLUetooth:MEAS<i>:DTMode:RXQuality:SEARch:PER:LENergy:
LRANge? etc.
Settings
The parameters for fast access are displayed. They are the same as in configuration
trees.
● "General Setup": refer to Chapter 7.4.4, "Input Signal Settings", on page 432
● "Channel, Frequency": refer to Chapter 7.4.3, "Signal Routing and Analyzer Set-
tings", on page 426
● "Start Level": refer to"Start Level < PER search" on page 450
● "Step Level": refer to "Level Step < PER search" on page 450
● "Signal Characteristics": refer to Chapter 7.4.4, "Input Signal Settings",
on page 432
Use the "Display" parameters to select the views and to change the appearance and
contents of the views. Depending on the selected view, the following "Display" hotkeys
are available:
Hotkey Description
"Select Trace ..." Select the trace types to be displayed in the view.
"X Scale... / Y Scale..." In views with Cartesian diagrams: Modify the ranges of the X-axis and the Y-
axis.
"Display Samples" In the "IQ Constellation Absolute" view: Plot the constellation points.
"Vector..." In the "IQ Constellation ..." views: Plot the I/Q trajectories in-between the con-
stellation points (vector diagrams).
"Scaling..." In the "IQ Constellation ..." views: Scale/zoom into the diagram and/or move the
origin.
Use the "Marker" parameters to activate markers and to modify their position. The fol-
lowing "Marker" hotkeys are available:
Hotkey Description
"Ref. Marker ..." Enable or disable the reference marker, select a trace and the marker position
on that trace
"Marker 1 /2 ..." Enable or disable marker 1 or 2 and define the marker position (absolute or rel-
ative to the reference marker)
Depending on the trace mode, a trace can also be selected.
"Select Trace Mode" Define whether all markers are collectively set to the same trace or to individual
traces
Current settings
The most important settings of measured signal are displayed at the top of the mea-
surement dialog. If enabled, the automatic detection of received packets is also indica-
ted. The displayed signal parameters depend on the type of measurements:
● Tx measurements on BR or EDR bursts: Measured channel, frequency, reference
level, burst type, and packet type are displayed.
● Tx measurements on LE test packets: Frequency, reference level, packet type, and
setup with burst type, physical layer and for LE coded PHY also coding are dis-
played.
Statistic Count
Progress bar for the measurement, displayed in all detailed views. During the first sin-
gle shot after the start of the measurement, the bar shows the number of elapsed mea-
surement intervals relative to the statistic count. A filled progress bar indicates that the
first shot is complete and the statistical depth has been reached.
Figure 7-64: Signal routing and analyzer R&S CMW100 settings (standalone scenario with ARB gen-
erator)
Figure 7-65: Signal routing and analyzer settings (combined signal path)
Scenario, Controlled by
Scenario switches between certain test situations that require different sets of parame-
ters. Some parameters are only available for a specific scenario.
● Standalone: provides you the non-signaling Bluetooth measurement, using all
Bluetooth multi-evaluation settings.
● Combined signal path: allows you to use a "Bluetooth Signaling" application
(options R&S CMW-KS60x/-KS61x/-KS721) in combination with Bluetooth multi-
evaluation measurement. The signaling application is selected by the additional
parameter "Controlled by". The signaling application settings of analyzer and signal
routing are displayed in the "Controller Settings" section.
The parameters display values determined by the signaling application. The corre-
sponding measurement settings are remembered in the background and displayed
again when switching back to the standalone scenario.
After selecting softkey "Input Signal", additional test mode hotkeys provide some
signaling parameters added to the measurement dialog for fast access.
Connection status information of the signaling application is displayed at the bot-
tom of the measurement views. Softkeys and hotkeys provide access to the set-
tings of the signaling application and allow to switch the downlink signal on or off,
see Chapter 7.4.12, "Additional Softkeys and Hotkeys", on page 465.
For additional information, see Chapter 7.2.1.3, "Parallel Signaling and Measure-
ment", on page 332.
Remote command:
ROUTe:BLUetooth:MEAS<i>:SCENario:SALone
ROUTe:BLUetooth:MEAS<i>:SCENario:CSPath
ROUTe:BLUetooth:MEAS<i>:SCENario?
ROUTe:BLUetooth:MEAS<i>?
RF Routing (Input)
Selects the input path for the measured RF signal, i.e. the input connector and the RX
module to be used.
In the standalone (SA) scenario, these parameters are controlled by the measurement.
In the combined signal path (CSP) scenario, they are controlled by the signaling appli-
cation.
Remote command:
ROUTe:BLUetooth:MEAS<i>:SCENario:SALone (SA)
ROUTe:BLUetooth:MEAS<i>:SCENario:CSPath (CSP)
Remote command:
CONFigure:BLUetooth:MEAS<i>:RFSettings:EATTenuation (SA)
CONFigure:BLUetooth:SIGN<i>:RFSettings:EATTenuation:INPut (CSP)
RF Routing (Output)
Selects the output path for the generated RF signal, i.e. the output connector and the
Tx module to be used for ARB files.
Depending on your hardware configuration, there are dependencies between both
parameters. Select the RF connector first. The "Converter" parameter offers only val-
ues compatible with the selected RF connector.
Option R&S CMW-KD611 is required (only for R&S CMW100/CMW with MUA).
Remote command:
CONFigure:BLUetooth:MEAS<i>:RXQuality:ROUTe
Connectors (Output)
Selects the Tx connectors of a connector bench to broadcast waveform ARB signal.
This node is visible if you select a connector bench with several connectors. The avail-
ability of connector benches depends on the instrument model.
Option R&S CMW-KD611 is required (only for R&S CMW100/CMW with MUA).
Remote command:
CONFigure:BLUetooth:MEAS<i>:RXQuality:ROUTe:USAGe:ALL
You can use either frequencies or channel numbers to define the analyzer frequency.
For measurements on LE advertiser packets, also the advertiser index can be speci-
fied, see Chapter 7.2.6.4, "LE: Channels", on page 346.
These settings are not relevant for measurements with LE connection tests. For set-
tings with LE connection tests, refer to "Frequency/Channel... (LE connection tests)"
on page 465.
In the standalone (SA) scenario, these parameters are controlled by the measurement.
In the combined signal path (CSP) scenario, they are controlled by the signaling appli-
cation.
Remote command:
CONFigure:BLUetooth:MEAS<i>:RFSettings:FREQuency (SA)
CONFigure:BLUetooth:MEAS<i>:RXQuality:AINDex (SA)
CONFigure:BLUetooth:SIGN<i>:RFSettings:CHANnel:DTMode (CSP)
CONFigure:BLUetooth:SIGN<i>:RFSettings:FREQuency:DTMode? (CSP)
CONFigure:BLUetooth:SIGN<i>:RFSettings:CHANnel:LOOPback (CSP)
CONFigure:BLUetooth:SIGN<i>:RFSettings:FREQuency:LOOPback? (CSP)
CONFigure:BLUetooth:SIGN<i>:RFSettings:CHANnel:TXTest (CSP)
CONFigure:BLUetooth:SIGN<i>:RFSettings:FREQuency:TXTest? (CSP)
TX Level (CMW)
For description, see "Tx Level (CMW)" on page 77.
This parameter is available in the combined signal path (CSP) scenario only. It is con-
trolled by the signaling application.
Remote command:
CONFigure:BLUetooth:SIGN<i>:RFSettings:LEVel (CSP)
User Margin
Margin that the measurement adds to the expected nominal power to determine its ref-
erence power (reference level). The margin is typically used to account for the known
variations of the RF input signal power, for example, the variations due to a specific
channel configuration.
A user margin of 3 dB is appropriate for the supported packet types.
In the standalone (SA) scenario, this parameter is controlled by the measurement. In
the combined signal path (CSP) scenario, it is controlled by the signaling application.
Remote command:
CONFigure:BLUetooth:MEAS<i>:RFSettings:UMARgin (SA)
CONFigure:BLUetooth:SIGN<i>:RFSettings:UMARgin (CSP)
Dirty Tx
For description, see Chapter 2.3.8.4, "Dirty Transmitter Configuration", on page 78.
This parameter is available in the combined signal path (CSP) scenario only. It is con-
trolled by the signaling application.
Remote command:
CONFigure:BLUetooth:SIGN<i>:RFSettings:DTX (CSP)
Detection Mode
The input signal parameters for the bursts to be measured can be either configured
manually or detected automatically, "Manual" detection and "Auto " detection mode
respectively.
● In "Manual" detection mode, the burst analysis is based on the input signal set-
tings. The R&S CMW checks the properties of the analyzed burst. Measurement
results are calculated if the properties are in accordance with the input signal set-
tings.
Manual input signal settings provide the fastest measurement. It is the recommen-
ded mode of operation in factory testing.
● In "Auto" detection mode, the R&S CMW only uses the selected "Burst Type". The
remaining signal properties are established during the burst analysis; input signal
settings are ignored. Automatic detection mode is indicated in the upper right cor-
ner of measurement views as "(auto)". The results of the burst analysis are dis-
played in the "Power Scalars" and "Modulation Scalars" views.
In this mode, you can reconfigure the Bluetooth signal during the measurement
without adjusting the input signal settings.
Automatic detection of Bluetooth bursts is not supported in list mode.
The following table lists the parameters to be configured manually in "Manual" and
"Auto" detection mode.
Table 7-48: Configurable parameters
LE: LE 1M PHY (uncoded)7) Packet type4), sync word, payload Packet type4), sync word/ access
length, pattern type, CTE slot address
type5), No. of antennas5), No. of
OFF slots2)
LE: LE 2M PHY (uncoded)7) Packet type4), sync word, payload Packet type4), sync word
length, pattern type, CTE slot
type5), No. of antennas5), No. of
OFF slots2)
LE: LE coded PHY7) Coding type, sync word, pattern Sync word
type, payload length
Option R&S CMW-KM611 is required for LE 1M PHY (uncoded). For LE 2M PHY and
LE coded PHY, option R&S CMW-KM721 is also required.
In the standalone (SA) scenario, this parameter is controlled by the measurement. In
the combined signal path (CSP) scenario, it is controlled by the signaling application.
Remote command:
CONFigure:BLUetooth:MEAS<i>:ISIGnal:DMODe (SA)
Commands FETCh:BLUetooth:MEAS:ISIGnal:ADETected:..., refer to Chap-
ter 7.6.3.12, "Detected Signal Characteristics", on page 568.
Fixed value Automatic (CSP)
Burst Type
Selects the basic burst type of the measured signal. The input signal settings, mea-
surement types and measurement algorithms are adjusted to the selected burst type.
For more information, refer to Chapter 7.2.6, "Bluetooth Signal Properties",
on page 344.
Option R&S CMW-KM610 is required for BR and EDR.
Option R&S CMW-KM611 is required for LE.
In the standalone (SA) scenario, this parameter is controlled by the measurement. In
the combined signal path (CSP) scenario, it is controlled by the signaling application.
Remote command:
CONFigure:BLUetooth:MEAS<i>:ISIGnal:BTYPe (SA)
CONFigure:BLUetooth:SIGN<i>:CONNection:BTYPe (CSP)
BD Address (BR/EDR)
For BR and EDR packets, the BD address specifies the Bluetooth device address of
the EUT's piconet. BD addresses are 48-bit (12-digit hex) numbers and consist of the
three subfields LAP (lower address part), UAP (upper address part) and NAP (non-
specific address part).
The synchronization word is derived from the LAP; it must be known to detect captured
bursts. The R&S CMW does not evaluate the other two parts of the received "BD
Address", so it is sufficient to enter a six-digit hexadecimal number.
Note: Separate address field settings. The "Input Signal > BD Address" hotkey pro-
vides another possibility to set the LAP, UAP, and NAP.
PHY (LE)
Selects the physical layer (PHY) used for LE connections.
See also Table 7-45.
Option R&S CMW-KM611 is required for LE 1M PHY (uncoded). For LE 2M PHY and
LE coded PHY, option R&S CMW-KM721 is also required.
In the standalone (SA) scenario, this parameter is controlled by the measurement. In
the combined signal path (CSP) scenario, it is controlled by the signaling application.
Remote command:
CONFigure:BLUetooth:MEAS<i>:ISIGnal:LENergy:PHY (SA)
CONFigure:BLUetooth:SIGN<i>:CONNection:PHY:LENergy (CSP)
CONFigure:BLUetooth:SIGN<i>:CONNection:PHY:NMODe:LENergy (CSP)
Packet Type
Specifies the packet type of the measured signal. The supported packet types are lis-
ted below, together with the payload length for each packet. The length of a standard
Bluetooth time slot is 625 µs.
Table 7-49: Supported packet types
BR DH1 1 0 to 27
DH3 3 0 to 183
DH5 5 0 to 339
EDR 2-DH1 1 0 to 54
2-DH3 3 0 to 367
2-DH5 5 0 to 679
3-DH1 1 0 to 83
3-DH3 3 0 to 552
3-DH5 5 0 to 1021
Advertising packet4) 1 6 to 37
1) The payload length in the table denotes the number of user payload bytes.
2) The transmission interval depends on the length of LE burst.
3) Only supported for LE with CTE uncoded PHY (LE 1M or LE 2M).
4) Only supported with automatic detection mode in non-signaling stand alone mode.
5) Only supported with automatic detection mode and CSP with LE connection test.
Option R&S CMW-KM611 is required for LE 1M PHY (uncoded). For LE 2M PHY and
LE coded PHY, option R&S CMW-KM721 is also required.
Measurements on LE with CTE require an option R&S CMW-KM722.
LE measurements in normal mode require combined signal path with a measurement
option R&S CMW-KM611 and a basic signaling option R&S CMW-KS601 for uncoded
LE 1M PHY. For LE 2M and LE code PHY, options R&S CMW-KM721 and R&S CMW-
KS720 are also required.
In the standalone (SA) scenario, these parameters are controlled by the measurement.
In the combined signal path (CSP) scenario, they are controlled by the signaling appli-
cation.
Remote command:
CONFigure:BLUetooth:MEAS<i>:ISIGnal:PTYPe:BRATe (SA)
CONFigure:BLUetooth:MEAS<i>:ISIGnal:PTYPe:EDRate (SA)
CONFigure:BLUetooth:MEAS<i>:ISIGnal:PTYPe:LENergy[:LE1M] (SA)
CONFigure:BLUetooth:MEAS<i>:ISIGnal:PTYPe:LENergy:LE2M (SA)
CONFigure:BLUetooth:MEAS<i>:ISIGnal:PTYPe:LENergy:LRANge (SA)
Auto detection mode:
FETCh:BLUetooth:MEAS<i>:ISIGnal:ADETected:PTYPe:BRATe? (SA)
FETCh:BLUetooth:MEAS<i>:ISIGnal:ADETected:PTYPe:EDRate? (SA)
FETCh:BLUetooth:MEAS<i>:ISIGnal:ADETected:PTYPe:LENergy[:LE1M]?
(SA)
FETCh:BLUetooth:MEAS<i>:ISIGnal:ADETected:PTYPe:LENergy:LE2M?
(SA)
FETCh:BLUetooth:MEAS<i>:ISIGnal:ADETected:PTYPe:LENergy:LRANge?
(SA)
CONFigure:BLUetooth:SIGN<i>:CONNection:PACKets:PTYPe:BRATe (CSP)
CONFigure:BLUetooth:SIGN<i>:CONNection:PACKets:PTYPe:EDRate (CSP)
CONFigure:BLUetooth:SIGN<i>:CONNection:PACKets:PTYPe:LENergy[:
LE1M] (CSP)
CONFigure:BLUetooth:SIGN<i>:CONNection:PACKets:PTYPe:LENergy:
LE2M (CSP)
Payload Length
Specifies the number of payload bytes (octets) in the measured packets. The value
range depends on the packet type.
Option R&S CMW-KM610 is required for BR or EDR measurements. Option
R&S CMW-KM611 is required for LE 1M PHY (uncoded). For LE 2M PHY and
LE coded PHY, option R&S CMW-KM721 is also required.
Pattern Type
Specifies the data pattern type that the EUT transmits as user payload data on its BR
or LE packets. In the standalone scenario, there is no equivalent setting for EDR pack-
ets.
Some of the modulation results for BR, LE 1M PHY and LE 2M PHY require a
'11110000' or a '10101010' pattern; see Chapter 7.3.1.2, "Modulation Measurements",
on page 364 and Chapter 7.3.3.4, "Modulation Measurements LE Uncoded PHY",
on page 373. Any other pattern type causes invalid results.
"Alternating" pattern alternates periodically a '11110000' and a '10101010' pattern.
Measurements on LE coded PHY (S = 8) require a '11111111' pattern, see Chap-
ter 7.3.3.5, "Modulation Measurements LE Coded PHY S = 8", on page 375.
CONFigure:BLUetooth:SIGN<i>:CONNection:PACKets:TYPE:CTE:LENergy:
LE1M (CSP)
CONFigure:BLUetooth:SIGN<i>:CONNection:PACKets:TYPE:CTE:LENergy:
LE2M (CSP)
CONFigure:BLUetooth:SIGN<i>:CONNection:PACKets:UNITs:CTE:
LENergy:LE1M (CSP)
CONFigure:BLUetooth:SIGN<i>:CONNection:PACKets:UNITs:CTE:
LENergy:LE2M (CSP)
The "No. of Off Slots" setting is only relevant for multi-shot ACP measurements, i.e.
ACP measurement mode: "ACP 79 Channels" for BR/EDR or "LE All Channels" in
manual detection mode. For settings, refer to "ACP Measurement Mode" on page 444.
The Bluetooth LE transmission interval depends on the number of payload bytes, see
Chapter 7.2.8.5, "PvT and Modulation Trace Points (LE)", on page 360. For "LE All
Channels" ACP measurements, it is recommended to set the number of "off" slots to
be the same as the number of "on" slots.
Option R&S CMW-KM610 is required for BR or EDR measurements. Option
R&S CMW-KM611 is required for LE 1M PHY (uncoded). For LE 2M PHY and
LE coded PHY, option R&S CMW-KM721 is also required.
In the standalone (SA) scenario, this parameter is controlled by the measurement. In
the combined signal path (CSP) scenario, it is controlled by the signaling application.
Remote command:
CONFigure:BLUetooth:MEAS<i>:ISIGnal:OSLots:BRATe (SA)
CONFigure:BLUetooth:MEAS<i>:ISIGnal:OSLots:EDRate (SA)
CONFigure:BLUetooth:MEAS<i>:ISIGnal:OSLots:LENergy[:LE1M] (SA)
CONFigure:BLUetooth:MEAS<i>:ISIGnal:OSLots:LENergy:LE2M (SA)
Auto detection mode:
FETCh:BLUetooth:MEAS<i>:ISIGnal:ADETected:NOSLots:BRATe? (SA)
FETCh:BLUetooth:MEAS<i>:ISIGnal:ADETected:NOSLots:EDRate? (SA)
Automatic configuration (CSP)
Remote command:
CONFigure:BLUetooth:SIGN<i>:CONNection:WHITening (CSP)
CONFigure:BLUetooth:SIGN<i>:CONNection:PPERiod (CSP)
CONFigure:BLUetooth:SIGN<i>:CONNection:PPERiod:MINimum (CSP)
Repetition.................................................................................................................... 442
Stop Condition.............................................................................................................443
Measure on Exception................................................................................................ 443
List Mode.....................................................................................................................443
Power vs. Time / Modulation / Phase Encoding / Spectrum > ... Statistic Count........ 443
ACP Measurement Mode............................................................................................444
Frequency Range........................................................................................................445
Filter............................................................................................................................ 445
Assign Views...............................................................................................................446
Repetition
Defines how often the measurement is repeated if it is not stopped explicitly or by a
failed limit check.
Stop Condition
Specifies the conditions for an early termination of the measurement:
● "None": The measurement is performed according to its "Repetition" mode and
"Statistic Count", irrespective of the limit check results.
● "On Limit Failure": The measurement is stopped when one of the limits is excee-
ded, irrespective of the repetition mode set. If no limit failure occurs, it is performed
according to its "Repetition" mode and "Statistic Count". Use this setting for mea-
surements that are intended for checking limits, e.g. production tests.
Remote command:
CONFigure:BLUetooth:MEAS<i>:MEValuation:SCONdition
Measure on Exception
Specifies whether results that the measurement identifies as faulty or inaccurate are
rejected. A faulty result occurs, for example, when an overload is detected. In remote
control, the cause of the error is indicated by the "reliability indicator".
● Off: Faulty results are rejected. The measurement is continued. The statistical
counters are not reset. Use this mode to ensure that a single faulty result does not
affect the entire measurement.
● On: Results are never rejected. Use this mode for development purposes, if you
want to analyze the reason for occasional wrong transmissions.
Remote command:
CONFigure:BLUetooth:MEAS<i>:MEValuation:MOEXception
List Mode
Shows whether the list mode is enabled and disables an enabled list mode. Enabling
the list mode is only possible via the remote control command below.
The list mode is essentially a remote control feature; for an introduction see Chap-
ter 7.2.5, "List Mode", on page 340.
Option R&S CMW-KM012 is required.
Remote command:
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIST
Power vs. Time / Modulation / Phase Encoding / Spectrum > ... Statistic Count
Defines the number of measurement intervals per measurement cycle. A measurement
cycle is the duration of a single-shot measurement.
Remote command:
CONFigure:BLUetooth:MEAS<i>:MEValuation:SACP:BRATe:MEASurement:
MODE
CONFigure:BLUetooth:MEAS<i>:MEValuation:SGACp:EDRate:
MEASurement:MODE
CONFigure:BLUetooth:MEAS<i>:MEValuation:SACP:LENergy[:LE1M]:
MEASurement:MODE
CONFigure:BLUetooth:MEAS<i>:MEValuation:SACP:LENergy:LE2M:
MEASurement:MODE
Frequency Range
Specifies the number of 1 MHz channels to be measured below and above the current
measured channel. The threshold is the level that needs to be crossed to search the
frequencies fL and fH.
For more details, see Chapter 7.4.2.5, "BR: Spectrum Frequency Range Results ",
on page 391.
Remote command:
CONFigure:BLUetooth:MEAS<i>:MEValuation:FRANge:BRATe:MEASurement
Filter
Selects the resolution bandwidth of the measurement filter used for power and modula-
tion measurements. For EDR measurements, the filter affects only to the GFSK portion
of the burst.
The filter setting complies with the two alternative settings stipulated in the Bluetooth
RF test specification for BR and EDR and RF-PHY test specification for LE 1M and LE
LR:
● Narrow band filter: 1.3 MHz
● Wide band filter: Approx. 2.0 MHz
The filter settings for LE 2M in line with RF-PHY test specification are as follows:
● Narrow band filter: 2.6 MHz
● Wide band filter: 4.0 MHz
Spectrum measurements (20 dB bandwidth and ACP) are performed at smaller mea-
surement bandwidths; see Chapter 7.3.1, "Basic Rate Measurements in Test Mode",
on page 363, Chapter 7.3.2, "Enhanced Data Rate Measurements in Test Mode",
on page 367 and Chapter 7.3.3, "Low Energy Measurements in Direct Test Mode",
on page 370.
Option R&S CMW-KM610 is required for BR or EDR measurements. Option
R&S CMW-KM611 is required for LE 1M PHY (uncoded). For LE 2M PHY and
LE coded PHY, option R&S CMW-KM721 is also required.
Remote command:
CONFigure:BLUetooth:MEAS<i>:MEValuation:BRATe:FILTer:BWIDth
CONFigure:BLUetooth:MEAS<i>:MEValuation:EDRate:FILTer:BWIDth
CONFigure:BLUetooth:MEAS<i>:MEValuation:LENergy[:LE1M]:FILTer:
BWIDth
CONFigure:BLUetooth:MEAS<i>:MEValuation:LENergy:LE2M:FILTer:
BWIDth
CONFigure:BLUetooth:MEAS<i>:MEValuation:LENergy:LRANge:FILTer:
BWIDth
Assign Views
Selects the view types to be displayed in the "Overview" dialog. The R&S CMW does
not evaluate the results for disabled views. Therefore, limiting the number of assigned
views can speed up the measurement.
Remote command:
CONFigure:BLUetooth:MEAS<i>:MEValuation:RESult:MSCalar etc.
CONFigure:BLUetooth:MEAS<i>:MEValuation:RESult[:ALL]
Access: "Config" hotkey > "Rx Measurement Control" > "OTA Advertiser" section.
Option R&S CMW-KD611 is required (only for R&S CMW100/CMW with MUA).
The "OTA Advertiser" parameters configure the scope of the measurement.
Mode
Selects measurement mode: spot check, PER or sensitivity search measurement, see
Chapter 7.2.2, "Rx Measurements with ARB Generator: Advertiser Tests",
on page 334.
Remote command:
CONFigure:BLUetooth:MEAS<i>:RXQuality:MMODe
Sensitivity
Specifies settings for Mode = "Sensitivity".
Retry ← Sensitivity
Specify the number of retry attempts per step for sensitivity search measurement.
Remote command:
CONFigure:BLUetooth:MEAS<i>:RXQuality:SENSitivity:RETRy
PER
Specifies settings for Mode = "PER".
Level ← PER
Sets the constant Tx level of R&S CMW for SCAN_REQ transmission.
Remote command:
CONFigure:BLUetooth:MEAS<i>:RXQuality:PER:LEVel
Access: "Config" hotkey > "Rx Measurement Control" > "Direct Test Mode (DTM)" sec-
tion.
Option R&S CMW-KD720 and an R&S CMW100 are required.
The following parameters configure the scope of PER and PER search in direct test
mode.
Packets
Defines the number of data packets to be measured. The number of packets sent can
be larger than the specified value because of possible packet lost on the way to the
DUT and back.
Limits
Defines and activates/deactivates the upper PER limit for the results of PER and PER
search measurements.
Remote command:
For PER:
CONFigure:BLUetooth:MEAS<i>:DTMode:RXQuality:LIMit:MPER:LENergy:
LE1M
CONFigure:BLUetooth:MEAS<i>:DTMode:RXQuality:LIMit:MPER:LENergy:
LE2M
CONFigure:BLUetooth:MEAS<i>:DTMode:RXQuality:LIMit:MPER:LENergy:
LRANge
For PER search:
CONFigure:BLUetooth:MEAS<i>:DTMode:RXQuality:SEARch:LIMit:MPER:
LENergy:LE1M
CONFigure:BLUetooth:MEAS<i>:DTMode:RXQuality:SEARch:LIMit:MPER:
LENergy:LE2M
CONFigure:BLUetooth:MEAS<i>:DTMode:RXQuality:SEARch:LIMit:MPER:
LENergy:LRANge
Integrity
Sets the ratio of the packets with correct CRC, generated and transmitted by the
R&S CMW within LE direct test.
Remote command:
For PER:
CONFigure:BLUetooth:MEAS<i>:DTMode:RXQuality:RINTegrity:LENergy:
LE1M
CONFigure:BLUetooth:MEAS<i>:DTMode:RXQuality:RINTegrity:LENergy:
LE2M
CONFigure:BLUetooth:MEAS<i>:DTMode:RXQuality:RINTegrity:LENergy:
LRANge
For PER search:
CONFigure:BLUetooth:MEAS<i>:DTMode:RXQuality:SEARch:RINTegrity:
LENergy:LE1M
CONFigure:BLUetooth:MEAS<i>:DTMode:RXQuality:SEARch:RINTegrity:
LENergy:LE2M
CONFigure:BLUetooth:MEAS<i>:DTMode:RXQuality:SEARch:RINTegrity:
LENergy:LRANge
HW Interface............................................................................................................... 451
EUT Comm. Protocol.................................................................................................. 452
Virtual COM Port......................................................................................................... 452
Baud Rate................................................................................................................... 452
Stop Bits, Parity...........................................................................................................452
Protocol....................................................................................................................... 452
Autoreset EUT.............................................................................................................452
Event Log.................................................................................................................... 452
Refresh Devices (hotkey)............................................................................................452
Reset EUT (hotkey).....................................................................................................453
HW Interface
Defines the type of USB connection used for tests.
The interface is used for the test control commands.
● None: tests without a USB control connection.
The Rx measurement is supported without controlling direct test mode. The test is
started manually by the DUT. The R&S CMW transmits the waveform signal. This
method is applicable only to the DUT that can count received packets.
● USB to RS232 adapter: support of the secondary communication channel via USB
connection with USB to RS232 adapter.
For the test setup, refer to Chapter 7.2.3.1, "Test Setup", on page 337.
Remote command:
CONFigure:BLUetooth:MEAS<i>:HWINterface
Baud Rate
Specifies the data transmission rate.
Remote command:
CONFigure:BLUetooth:MEAS<i>:COMSettings:BAUDrate
Protocol
Specifies the flow control protocol.
Remote command:
CONFigure:BLUetooth:MEAS<i>:COMSettings:PROTocol
Autoreset EUT
Resets the DUT at the beginning of a direct test.
Event Log
Each entry consists of a timestamp, an icon indicating the category of the event and a
short text describing the event. Meaning of the category icons: = information,
warning and error respectively.
Press the button to the right to clear the displayed event entries.
Remote command:
CLEan:BLUetooth:MEAS<i>:ELOGging
SENSe:BLUetooth:MEAS<i>:ELOGging:ALL?
SENSe:BLUetooth:MEAS<i>:ELOGging:LAST?
Remote command:
CALL:BLUetooth:MEAS<i>:DTMode:LENergy:RDEVices
Remote command:
CALL:BLUetooth:MEAS<i>:DTMode:LENergy:RESet
CALL:BLUetooth:MEAS<i>:DTMode:LENergy:RRESult?
Trigger Source
Selects the source of the trigger event.
Only the measurement-specific trigger sources are listed here. Additional trigger sour-
ces are provided by the base software and by other applications like the GPRF genera-
tor. For a description of these trigger sources, refer to the documentation of the corre-
sponding software part.
Trigger source "Power" triggers the measurement by the rising edge of the measured
Bluetooth burst. This trigger is a recommended trigger in the standalone scenario.
This parameter is only visible in the standalone (SA) scenario. In the combined signal
path (CSP) scenario, it is controlled by the signaling application. See also Chap-
ter 7.2.1.3, "Parallel Signaling and Measurement", on page 332.
Remote command:
TRIGger:BLUetooth:MEAS<i>:MEValuation:CATalog:SOURce?
TRIGger:BLUetooth:MEAS<i>:MEValuation:SOURce
Trigger Threshold
Defines the input signal power where the trigger condition is satisfied and a trigger
event is generated. The trigger threshold is valid for power trigger sources. It is a dB
value, relative to the reference level minus the external attenuation ("<Ref. Level> –
<External Attenuation (Input)> – <Frequency Dependent External Attenuation>").
The trigger threshold is referenced to the actual maximum RF input power at the
R&S CMW if:
● The reference level is set to the actual maximum output power of the EUT and
● The external attenuation settings are in accordance with the test setup.
A low threshold can be required to ensure that the R&S CMW always detects the input
signal. A higher threshold prevents unintended trigger events.
Remote command:
TRIGger:BLUetooth:MEAS<i>:MEValuation:THReshold
Trigger Timeout
Sets a time after which an initiated measurement must have received a trigger event. If
no trigger event is received, a trigger timeout is indicated in manual operation mode. In
remote control mode, the measurement is automatically stopped.
Remote command:
TRIGger:BLUetooth:MEAS<i>:MEValuation:TOUT
● Power Limits..........................................................................................................454
● Modulation Limits.................................................................................................. 456
● Spectrum Limits.................................................................................................... 461
● Phase Encoding Limits..........................................................................................463
Power Limits
Upper and lower limits for the current, average, maximum and minimum power results.
● "Packet Timing": Lower and upper limits for the packet timing defined as the time
between the expected and actual start of the first symbol of the Bluetooth burst. As
the expected start is defined by the signaling trigger, this setting is relevant for
combined signal path only (options R&S CMW-KS600/-KS610).
● "Average Power": Lower and upper limits for the average burst power during the
carrier-on state
● "Peak Power": Upper limit for the peak power measured (no lower limit specified).
● "DPSK Pow – GFSK Pow": Lower and upper limit for the difference between the
average power in the DPSK and in the GFSK-modulated portions of an EDR burst.
● "Guard Period": Lower and upper limit for the duration of the guard band between
the packet header and the synchronization sequence in an EDR burst.
● "Peak Power – Average Power": Upper limit for the difference between peak and
average power in LE bursts
● "Direction Finding > Reference Period Deviation": Upper limit for CTE power
deviation for reference antenna
● "Direction Finding > Tx Slot Deviation": Upper limit for CTE power deviation per
CTE slot
Option R&S CMW-KM611 is required for LE 1M PHY (uncoded). For LE 2M PHY and
LE coded PHY, option R&S CMW-KM721 is also required.
Measurements on LE with CTE require an option R&S CMW-KM722.
Remote command:
Packet timing:
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:PVTime
BR limits:
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:BRATe:PVTime
EDR limits:
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:EDRate:PVTime
LE limits:
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy[:LE1M]:
PVTime
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy:LE2M:
PVTime
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy:LRANge:
PVTime
LE with CTE limits:
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:CTE:LENergy:LE1M:
PDEViation
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:CTE:LENergy:LE2M:
PDEViation
BR
Upper and lower limits for the measurement results which characterize the modulation
accuracy of BR packets. For a detailed description of the results, refer to Chap-
ter 7.4.2.3, "BR: Statistical Modulation Results ", on page 386.
The limits apply to the "Current", "Average", "Max" and "Min" results, however, it is pos-
sible to enable the limit checks separately.
● "Δf2 99.9%": Lower limit for the frequency deviation Δf2 that must be exceeded by
99.9% of the measured bits
● "Δf2 avg / Δf1 avg": Lower limit for the modulation ratio
● "Freq. Accuracy / Freq. Drift / Max. Drift Rate": Limit for the carrier frequency
error, the frequency drift and the maximum drift rate. An "upper" limit of <x> kHz
means that the measurement result must be in the range between –<x> kHz and
+<x> kHz. The default value of "20.0 kHz" denotes a maximum absolute drift rate
of 20 kHz/50 μs.
The R&S CMW supports different drift limits for packet types DH1, DH3 and DH5.
● Freq. Dev. Δf...: Limit for the frequency deviation for different payload patterns.
The frequency deviations must be in a range between the lower and the upper lim-
its.
Remote command:
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:BRATe:DELTa
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:BRATe:MRATio
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:BRATe:DAVerage
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:BRATe:FACCuracy
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:BRATe:FDRift
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:BRATe:FDRift:
APACkets
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:BRATe:DMINimum
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:BRATe:DMAXimum
EDR
Upper limits for the measurement results which characterize the modulation accuracy
of EDR packets. For a detailed description of the results, refer to Chapter 7.4.2.9,
"EDR: Statistical Modulation Results ", on page 398.
A single limit is provided for each quantity, however, it is possible to enable each limit
check separately for the "Current", "Average", and "Max" results.
● "Freq. Stability ωi": Upper limit for the initial center frequency error.
● "Freq. Stability (ω0 + ωi)max": Upper limit for the overall uncompensated fre-
quency error.
● "Freq. Stability ω0max": Upper limit for the maximum compensated frequency
error.
● "RMS DEVM / Peak DEVM / 99% DEVM": Upper limit for the differential error vec-
tor magnitude results. Independent limits for the modulation schemes π/4 DQPSK
(2-DHx packets) and 8DPSK (3-DHx) are provided.
Remote command:
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:EDRate:DPSK:DEVM
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:EDRate:DQPSk:DEVM
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:EDRate:FSTability
LE
Upper and lower limits for the measurement results which characterize the modulation
accuracy of LE packets. For a detailed description of the results, refer to Chap-
ter 7.4.2.17, "LE: Statistical Modulation Results ", on page 410.
Option R&S CMW-KM611 is required for LE 1M PHY (uncoded). For LE 2M PHY and
LE coded PHY, option R&S CMW-KM721 is also required.
Measurements on LE with CTE require an option R&S CMW-KM722.
The limits apply to the "Current", "Average", "Max" and "Min" results, however, it is pos-
sible to enable the limit checks separately.
● "Δf1 99.9%": Lower limit for the frequency deviation Δf1 that must be exceeded by
99.9% of the measured bits. This limit is only relevant for LE coded PHY.
● "Δf2 99.9%": Lower limit for the frequency deviation Δf2 that must be exceeded by
99.9% of the measured bits
● "Δf2 avg / Δf1 avg": Lower limit for the modulation ratio
● "Freq. Accuracy": An upper limit of <x> kHz means that the carrier frequency
error must be in the range between –<x> kHz and +<x> kHz.
● "Freq. Offset": Carrier frequency error for preamble and payload.
● "Freq. Drift": An upper limit of <x> kHz means that the frequency drift must be in
the range between –<x> kHz and +<x> kHz.
● "Initial Freq. Drift": Frequency drift between preamble and payload start.
● "Max. Drift Rate": An upper limit of <x> kHz means that the maximum drift rate
must be in the range between –<x> kHz and +<x> kHz per stated time interval. For
uncoded PHY, for example, the default value of "20.0 kHz" denotes a maximum
absolute drift rate of 20 kHz/50 μs.
● "Freq. Dev. Δf...": Limit for the frequency deviation Δf1 or Δf2 for different payload
patterns. The frequency deviations must be in a range between the lower and the
upper limits.
● CTE : Upper modulation limits for LE with CTE.
All limits listed in the configuration dialog are relevant for LE test packet connections
(direct test mode and LE test mode). For measurements on advertiser packets, only
the limit of frequency accuracy is relevant.
Remote command:
LE 1M PHY (uncoded):
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy:DELTa
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy[:LE1M]:
MRATio
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy[:LE1M]:
FACCuracy
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy[:LE1M]:
FOFFset
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy[:LE1M]:
FDRift
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy:DAVerage
etc.
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy:DAVerage:
DF2S etc.
LE 2M PHY (uncoded):
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy:LE2M:DELTa
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy:LE2M:
MRATio
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy:LE2M:
FACCuracy
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy:LE2M:
FOFFset
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy:LE2M:
FDRift
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy:LE2M:
DAVerage etc.
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy:LE2M:
DAVerage:DF2S etc.
LE coded PHY:
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy:LRANge:
DELTa
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy:LRANge:
FACCuracy
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy:LRANge:
FOFFset
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy:LRANge:
FDRift
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy:LRANge:
DAVerage
LE with CTE:
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:CTE:LENergy:LE1M:
FDRift etc.
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:CTE:LENergy:LE1M:
FOFFset etc.
20 dB Bandwidth (BR)
The 20 dB bandwidth measurement is available for BR bursts only. The following set-
tings can be configured:
● "Peak Emission Threshold": The user-defined threshold value for "high" TX
power: if the peak emission within a burst is equal or higher than this threshold,
then the "High Pk Emission Bandwidth" limit applies, otherwise the "Low Pk Emis-
sion Bandwidth" limit applies.
● "High Pk Emission Bandwidth": 20 dB bandwidth limit for "high" peak emission
bursts
● "Low Pk Emission Bandwidth": 20 dB bandwidth limit for "low" peak emission
bursts
The default settings correspond to the values specified in the transmitter test
RF/TRM/CA/BV-05-C ("TX Output Spectrum – 20 dB Bandwidth").
Remote command:
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:SOBW
Defines and enables the following limits relative to the center frequency:
● Lower limit for the lowest frequency within the measured range
● Upper limit for the highest frequency within the measured range
Remote command:
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:FRANge
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy:LE2M:SACP
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy[:LE1M]:
SACP
Upper limits for the measurement results which characterize the in-band spurious
emissions.
The gated ACP measurement is available for EDR bursts only. The following settings
can be configured:
● "PTx, Exceptions PTx, No. of Exceptions": see ACP description for BR and LE
● "PTx–26dBm –1 (rel)": Maximum value of the relative PTx–26dBm in channel –1
● "PTx–26dBm +1 (rel)": Maximum value of the relative PTx–26dBm in channel +1
Remote command:
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:SGACp
Lower
Defines and enables the lower limit as percentage of received fault free packets.
Remote command:
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:EDRate:PENCoding
Active View
Selects the diagram type to be displayed.
Remote command:
CONFigure:BLUetooth:MEAS<i>:DISPlay
Auto Scaling
Activates the "Auto Scaling" function for the active view. No remote control is provided.
Generator Shortcut
Enables you to start the GPRF generator and use GPRF-related hotkeys and softkeys
within the measurement application.
The "Generator Shortcut" is only available in the "Standalone (Non Signaling)" mode.
When a connection to the GPRF generator instance is established, two additional soft-
keys with corresponding hotkey bars provide access to the generator configuration,
see "ARB/List Mode, GPRF<i> Generator" on page 467.
Use the appropriate softkey/hotkey combination to access the generator parameters.
For details on the available parameters, see the GPRF generator documentation.
Bluetooth Signaling
Select this softkey and press [ON | OFF] to turn the downlink signal transmission on or
off.
It is displayed only while the combined signal path scenario is active and is provided by
the "Bluetooth Signaling" application selected as master application. See also "Sce-
nario, Controlled by" on page 428.
Press the softkey two times (select it and press it again) to switch to the signaling
application.
While this softkey is selected, the "Config" hotkey opens the configuration dialog of the
signaling application, not the configuration dialog of the measurement.
7.5 Programming
The following sections provide programming examples for the "Bluetooth Tx Measure-
ment" application. The examples have been tested with the aid of a simple software
tool.
● Key Features.........................................................................................................467
● Specifying General Measurement Settings...........................................................468
● Basic Input Signal Properties: EDR Packets.........................................................469
● Basic Input Signal Properties: LE Packets............................................................469
● Limit Settings.........................................................................................................470
● Configuring Measurements................................................................................... 471
● Performing PvT and Modulation Measurements...................................................472
● Performing Spectrum Measurements................................................................... 473
● Differential Phase Encoding Measurements......................................................... 474
● Performing LE with CTE Measurements...............................................................474
● Automatic Detection Mode.................................................................................... 475
● Using Bluetooth List Mode.................................................................................... 477
● Rx Measurements on Advertisers......................................................................... 481
● Rx Measurements in Direct Test Mode................................................................. 484
● Tx-Rx Measurements............................................................................................486
// *****************************************************************************
// System-Reset
// *****************************************************************************
*RST;*OPC?
*CLS; *OPC?
// *****************************************************************************
// Define a measurement timeout of 1 s.
// Define signal routing, configure RF and analyzer settings for a Bluetooth
// signal with a nominal power of 0 dBm and low operating frequency.
// Alternatively select combined signal path and let the Bluetooth Signaling
// control RF and analyzer settings. Select channel 78 to be measured in CSP
// for normal mode classic and 36 for LE.
// *****************************************************************************
CONFigure:BLUetooth:MEAS:MEValuation:TOUT 1
ROUTe:BLUetooth:MEAS:SCENario:SALone RF1C,RX1
CONFigure:BLUetooth:MEAS:RFSettings:EATTenuation 2
CONFigure:BLUetooth:MEAS:RFSettings:ENPower 0
CONFigure:BLUetooth:MEAS:RFSettings:UMARgin 3
CONFigure:BLUetooth:MEAS:RFSettings:FREQuency 2402E+6
WAITKEY >Signal routing and analyzer settings completed, press "OK" to continue<
// *****************************************************************************
// Assume the EUT transmits the longest supported π/4-DQPSK packet
// type (2-DH5) with a PRBS9 payload bit pattern. Query the (maximum)
// payload length. Disable auto synchronization. Specify and query
// the transmitted BD Address (the response is #H565634121212).
// *****************************************************************************
CONFigure:BLUetooth:MEAS:ISIGnal:DMODe MANual
CONFigure:BLUetooth:MEAS:ISIGnal:BTYPe EDR
CONFigure:BLUetooth:MEAS:ISIGnal:PTYPe:EDRate E25P
CONFigure:BLUetooth:MEAS:ISIGnal:PATTern OTHer
CONFigure:BLUetooth:MEAS:ISIGnal:ASYNchronize OFF
CONFigure:BLUetooth:MEAS:ISIGnal:PLENgth:EDRate?
CONFigure:BLUetooth:MEAS:ISIGnal:LAP #H121212
CONFigure:BLUetooth:MEAS:ISIGnal:UAP #H34
CONFigure:BLUetooth:MEAS:ISIGnal:NAP #H5656
CONFigure:BLUetooth:MEAS:ISIGnal:BDADdress?
// *****************************************************************************
// Set the trigger source, reduce the trigger threshold and timeout
// *****************************************************************************
TRIGger:BLUetooth:MEAS:MEValuation:CATalog:SOURce?
TRIGger:BLUetooth:MEAS:MEValuation:SOURce "POWer"
TRIGger:BLUetooth:MEAS:MEValuation:THREShold -25
TRIGger:BLUetooth:MEAS:MEValuation:TOUT 1
// *****************************************************************************
// Set LE advertiser input signal. LE 1M PHY and automatic detection
// is required. Adjust access address, set pattern and packet length.
// *****************************************************************************
CONFigure:BLUetooth:MEAS:ISIGnal:BTYPe LE
CONFigure:BLUetooth:MEAS:ISIGnal:LENergy:PHY LE1M
CONFigure:BLUetooth:MEAS:ISIGnal:PTYPe:LENergy:LE1M ADV
CONFigure:BLUetooth:MEAS:ISIGnal:DMODe AUTO
CONFigure:BLUetooth:MEAS:ISIGnal:ACCaddress:LENergy #HFFFF
CONFigure:BLUetooth:MEAS:ISIGnal:PATTern:LENergy P11
CONFigure:BLUetooth:MEAS:ISIGnal:PLENgth:LENergy 37
// *****************************************************************************
// Alternativelly measure LE coded PHY, set burst type, packet type, PHY,
// coding. Adjust sync word, set pattern and packet length.
// *****************************************************************************
CONFigure:BLUetooth:MEAS:ISIGnal:BTYPe LE
CONFigure:BLUetooth:MEAS:ISIGnal:PTYPe:LENergy:LRANge RFPH
CONFigure:BLUetooth:MEAS:ISIGnal:LENergy:PHY LELR
CONFigure:BLUetooth:MEAS:ISIGnal:FEC:LENergy:LRANge S8
CONFigure:BLUetooth:MEAS:ISIGnal:LENergy:SYNWord #HFFFFFFFF
CONFigure:BLUetooth:MEAS:ISIGnal:PATTern:LENergy:LRANge ALL1
CONFigure:BLUetooth:MEAS:ISIGnal:PLENgth:LENergy:LRANge 255
// *****************************************************************************
// Define and enable common timing error limit
// *****************************************************************************
CONFigure:BLUetooth:MEAS:MEValuation:LIMit:PVTime -10,10,ON
// *****************************************************************************
// Define limits and enable limit check for BR packets
// *****************************************************************************
CONFigure:BLUetooth:MEAS:MEValuation:LIMit:BRATe:PVTime
-6.0,4.0,23.0,ON,ON,ON,ON,ON,ON,ON,ON
CONFigure:BLUetooth:MEAS:MEValuation:LIMit:BRATe:DELTa 115E+3, ON
CONFigure:BLUetooth:MEAS:MEValuation:LIMit:BRATe:MRATio 8E-1, ON
CONFigure:BLUetooth:MEAS:MEValuation:LIMit:BRATe:FACCuracy
75E+3, ON, ON, ON
CONFigure:BLUetooth:MEAS:MEValuation:LIMit:BRATe:FDRift:APACkets
25E+3,25E+3,40E+3,20E+3,ON,ON,ON,ON,ON,ON,ON,ON,ON,ON,ON,ON
CONFigure:BLUetooth:MEAS:MEValuation:LIMit:BRATe:DMINimum
115E+3, 175E+3, 115E+3, 175E+3, ON, ON, ON, ON, ON, ON, ON, ON
CONFigure:BLUetooth:MEAS:MEValuation:LIMit:BRATe:DMAXimum
115E+3, 175E+3, 115E+3, 175E+3, ON, ON, ON, ON, ON, ON, ON, ON
CONFigure:BLUetooth:MEAS:MEValuation:LIMit:BRATe:DAVerage
115E+3, 175E+3, 115E+3, 175E+3, ON, ON, ON, ON, ON, ON, ON, ON
CONFigure:BLUetooth:MEAS:MEValuation:LIMit:SOBW 0.0E+0,1.0E+6,1.5E+6,ON,OFF
CONFigure:BLUetooth:MEAS:MEValuation:LIMit:FRANge -5E+6,5E+6,ON,ON
CONFigure:BLUetooth:MEAS:MEValuation:LIMit:SACP -20.0,-30.0,3,ON,ON
// *****************************************************************************
// Define limits and enable limit check for EDR packets
// *****************************************************************************
CONFigure:BLUetooth:MEAS:MEValuation:LIMit:EDRATe:PVTime
-4.0,1.0,4.75,5.25,ON,ON,ON,ON,ON,ON,ON,ON
CONFigure:BLUetooth:MEAS:MEValuation:LIMit:EDRate:FSTability?
CONFigure:BLUetooth:MEAS:MEValuation:LIMit:EDRate:DQPSk:DEVM?
CONFigure:BLUetooth:MEAS:MEValuation:LIMit:EDRate:DPSK:DEVM?
CONFigure:BLUetooth:MEAS:MEValuation:LIMit:EDRate:FSTability
75E+3, 10E+3, 75E+3, ON, ON, ON, ON, ON, ON, ON, ON, ON
CONFigure:BLUetooth:MEAS:MEValuation:LIMit:EDRate:DQPSk:DEVM
// *****************************************************************************
// Define limits and enable limit check for LE 1M PHY
// *****************************************************************************
CONFigure:BLUetooth:MEAS:MEValuation:LIMit:LENergy:LE1M:PVTime
-20.0, 10.0, 3.0, ON, ON, ON, ON, ON, ON, ON, ON
CONFigure:BLUetooth:MEAS:MEValuation:LIMit:LENergy:DELTa 115E+3, ON
CONFigure:BLUetooth:MEAS:MEValuation:LIMit:LENergy:LE1M:MRATio 8E-1, ON
CONFigure:BLUetooth:MEAS:MEValuation:LIMit:LENergy:LE1M:FACCuracy
75E+3, ON, ON, ON
CONFigure:BLUetooth:MEAS:MEValuation:LIMit:LENergy:LE1M:FOFFset
150E+3, ON, ON, ON
CONFigure:BLUetooth:MEAS:MEValuation:LIMit:LENergy:LE1M:FDRift
50E+003,20E+3,20E+3,ON,ON,ON,ON,ON,ON,ON,ON,ON
CONFigure:BLUetooth:MEAS:MEValuation:LIMit:LENergy:DMINimum
225E+3, 275E+3, OFF, OFF, OFF, OFF
CONFigure:BLUetooth:MEAS:MEValuation:LIMit:LENergy:DMAXimum
225E+3, 275E+3, OFF, OFF, OFF, OFF
CONFigure:BLUetooth:MEAS:MEValuation:LIMit:LENergy:DAVerage
225E+3, 275E+3, ON, ON, ON, ON
CONFigure:BLUetooth:MEAS:MEValuation:LIMit:LENergy:LE1M:SACP
-20.0,-40.0,3,ON,ON
CONFigure:BLUetooth:MEAS:MEValuation:LIMit:LENergy:LE1M:DAVerage:DF2S
115E+3,175E+3,ON,ON,ON,ON
CONFigure:BLUetooth:MEAS:MEValuation:RESult:SGAcp?
CONFigure:BLUetooth:MEAS:MEValuation:RESult:ALL?
// *****************************************************************************
// Change EUT configuration and send Basic Rate (DH5) packets.
// Adjust input signal settings to the new EUT configuration.
// Stop the previous EDR measurement (READ...) and perform
// a measurement for BR packets.
// *****************************************************************************
CONFigure:BLUetooth:MEAS:ISIGnal:BTYPe BR
CONFigure:BLUetooth:MEAS:ISIGnal:PTYPe:BRATe DH5
CONFigure:BLUetooth:MEAS:ISIGnal:PLENgth:BRATe?
READ:BLUetooth:MEAS:MEValuation:MODulation:BRATe:CURRent?
FETCh:BLUetooth:MEAS:MEValuation:MODulation:BRATe:MAXimum?
// *****************************************************************************
// Change EUT configuration for LE test packets.
// Adjust sync word, set pattern and packet length.
// Perform a measurement for LE test packets.
// *****************************************************************************
CONFigure:BLUetooth:MEAS:ISIGnal:BTYPe LE
CONFigure:BLUetooth:MEAS:ISIGnal:LENergy:PHY LE1M
CONFigure:BLUetooth:MEAS:ISIGnal:LENergy:SYNWord #H71764129
CONFigure:BLUetooth:MEAS:ISIGnal:PATTern:LENergy:LE1M P11
CONFigure:BLUetooth:MEAS:ISIGnal:PLENgth:LENergy:LE1M 37
READ:BLUetooth:MEAS:MEValuation:PvTime:LENergy:LE1M:CURRent?
READ:BLUetooth:MEAS:MEValuation:MODulation:LENergy:LE1M:CURRent?
FETCh:BLUetooth:MEAS:MEValuation:MODulation:LENergy:LE1M:MAXimum?
// *****************************************************************************
// Alternatively in normal mode with CSP use the following
// commands to query the power and modulation results.
// *****************************************************************************
FETCh:BLUetooth:MEAS:MEValuation:MODulation:NMODe:CLASsic:CURRent?
FETCh:BLUetooth:MEAS:MEValuation:MODulation:NMODe:LENergy:LE1M:CURRent?
FETCh:BLUetooth:MEAS:MEValuation:PVTime:NMODe:LENergy:LE1M:CURRent?
// *****************************************************************************
// Perform a measurement
// *****************************************************************************
INITiate:BLUetooth:MEAS:MEValuation
// *****************************************************************************
// BR: Monitor the spectrum ACP view.
// Measure the ACP in all 79 Bluetooth channels
//
// Set the frequency range channels and threshold. Perform
// measurement; return frequency range and "Spectrum 20 dB Bandwidth" results.
// *****************************************************************************
CONFigure:BLUetooth:MEAS:DISPlay SACP
CONFigure:BLUetooth:MEAS:MEValuation:SACP:BRATe:MEASurement:MODE CH79
CONFigure:BLUetooth:MEAS:ISIGnal:OSLots:BRATe 3,4,5
READ:BLUetooth:MEAS:MEValuation:TRACe:SACP:PTX?
FETCh:BLUetooth:MEAS:MEValuation:TRACe:SACP:CURRent?
CONFigure:BLUetooth:MEAS:MEValuation:FRANge:BRATe:MEASurement 5,5,-30
FETCh:BLUetooth:MEAS:MEValuation:FRANge:BRATe:CURRent?
FETCh:BLUetooth:MEAS:MEValuation:TRACe:FRANge:AVERage?
FETCh:BLUetooth:MEAS:MEValuation:TRACe:SOBW:MAXimum?
FETCh:BLUetooth:MEAS:MEValuation:SOBW:BRATe:MAXimum?
// *****************************************************************************
// EDR: Measure the gated ACP in all 79 Bluetooth channels with 3 off slots
// (the other BR input signal settings defined above are still valid).
// *****************************************************************************
CONFigure:BLUetooth:MEAS:ISIGnal:BTYPe EDR
CONFigure:BLUetooth:MEAS:MEValuation:SGACp:EDRate:MEASurement:MODE CH79
CONFigure:BLUetooth:MEAS:ISIGnal:OSLots:EDRate 3, 3, 3, 3, 3, 3
INITiate:BLUetooth:MEAS:MEValuation
FETCh:BLUetooth:MEAS:MEValuation:TRACe:SGAcp:PTX?
FETCh:BLUetooth:MEAS:MEValuation:TRACe:SGAcp:CURRent?
FETCh:BLUetooth:MEAS:MEValuation:SGAcp:EDRate:PTX?
// *****************************************************************************
// LE: Measure the ACP in all 81 Bluetooth halfchannels for a signal
// with 2 off slots.
// *****************************************************************************
CONFigure:BLUetooth:MEAS:ISIGnal:BTYPe LE
CONFigure:BLUetooth:MEAS:MEValuation:SACP:LENergy:LE1M:MEASurement:MODE CH40
CONFigure:BLUetooth:MEAS:ISIGnal:OSLots:LENergy:LE1M 2
INITiate:BLUetooth:MEAS:MEValuation
FETCh:BLUetooth:MEAS:MEValuation:TRACe:SACP:PTX?
FETCh:BLUetooth:MEAS:MEValuation:TRACe:SACP:CURRent?
FETCh:BLUetooth:MEAS:MEValuation:SACP:LENergy?
// *****************************************************************************
// Perform a measurement; return all phase encoding results.
// *****************************************************************************
INITiate:BLUetooth:MEAS:MEValuation
FETCh:BLUetooth:MEAS:MEValuation:PENCoding:EDRate:CURRent:C?
FETCh:BLUetooth:MEAS:MEValuation:PENCoding:SSEQuence:EDRate:CURRent?
// *****************************************************************************
// Set CTE type and the number of CTE units.
// is required. Adjust sync word, set pattern and packet length.
// *****************************************************************************
CONFigure:BLUetooth:MEAS:ISIGnal:CTE:LENergy:LE2M:TYPE AOD2
CONFigure:BLUetooth:MEAS:ISIGnal:CTE:LENergy:LE2M:UNITs 20
// *****************************************************************************
// Enables or disables the evaluation of results of power vs slot measurements
// *****************************************************************************
CONFigure:BLUetooth:MEAS:MEValuation:RESult:PVSLot ON
// *****************************************************************************
// Set CTE limits: for power deviation, frequency drift, and frequency
// offset.
// *****************************************************************************
CONF:BLUetooth:MEAS:MEV:LIMit:CTE:LENergy:LE2M:PDEViation 0.25,0.25,ON,ON
CONFigure:BLUetooth:MEAS:MEV:LIMit:CTE:LENergy:LE2M:FDRift 50E+3,19.2E+3,
19.2E+3,ON,ON,ON,ON,ON,ON,ON,ON,ON
CONFigure:BLUetooth:MEAS:MEV:LIMit:CTE:LENergy:LE2M:FOFFset 150E+3,ON,ON,ON
// *****************************************************************************
// Query the detected packet type, CTE slot type, and number of CTE units.
// *****************************************************************************
FETCh:BLUetooth:MEAS:ISIGnal:ADETected:PTYPe:LENergy:LE2M?
FETCh:BLUetooth:MEAS:ISIGnal:ADETected:CTE:LENergy:LE2M:TYPE?
FETCh:BLUetooth:MEAS:ISIGnal:ADETected:CTE:LENergy:LE2M:UNITs?
// *****************************************************************************
// Start a CTE measurement and return average modulation results.
// Return traces for average power and max. power deviation per CTE slot.
// *****************************************************************************
INIT:BLUetooth:MEAS:MEValuation
FETCh:BLUetooth:MEAS:MEValuation:MODulation:CTE:LENergy:LE2M:AVERage?
FETCh:BLUetooth:MEAS:MEValuation:TRACe:SPOWer:AVERage?
FETCh:BLUetooth:MEAS:MEValuation:TRACe:PDEViation:MAXimum?
// *****************************************************************************
// Start a measurement and read the modulation results.
// Read the auto-detected signal properties and the yield.
// *****************************************************************************
READ:BLUetooth:MEAS:MEValuation:MODulation:BRATe:CURRent?
FETCh:BLUetooth:MEAS:ISIGnal:ADETected:PTYPe:BRATe?
FETCh:BLUetooth:MEAS:ISIGnal:ADETected:PATTern:BRATe?
FETCh:BLUetooth:MEAS:ISIGnal:ADETected:PLENgth:BRATe?
FETCh:BLUetooth:MEAS:ISIGnal:ADETected:NOSLots:BRATe?
FETCh:BLUetooth:MEAS:MEValuation:MODulation:BRATe:YIELd?
// *****************************************************************************
// Change the signal configuration and R&S CMW settings for EDR packets with the
// BD Address defined above. Start a measurement, read the auto-detected signal
// properties
// *****************************************************************************
CONFigure:BLUetooth:MEAS:ISIGnal:BTYPe EDR
READ:BLUetooth:MEAS:MEValuation:MODulation:EDRATe:CURRent?
FETCh:BLUetooth:MEAS:ISIGnal:ADETected:PTYPe:EDRate?
FETCh:BLUetooth:MEAS:ISIGnal:ADETected:PLENgth:EDRate?
FETCh:BLUetooth:MEAS:ISIGnal:ADETected:NOSLots:EDRate?
// *****************************************************************************
// Change the signal configuration and R&S CMW settings for LE packets.
// Start an LE 1M measurement, read the auto-detected signal properties
// *****************************************************************************
CONFigure:BLUetooth:MEAS:ISIGnal:BTYPe LE
CONFigure:BLUetooth:MEAS:ISIGnal:LENergy:PHY LE1M
READ:BLUetooth:MEAS:MEValuation:MODulation:LENergy:LE1M:CURRent?
FETCh:BLUetooth:MEAS:MEValuation:MODulation:LENergy:LE1M:YIELd?
FETCh:BLUetooth:MEAS:ISIGnal:ADETected:PTYPe:LENergy:LE1M?
FETCh:BLUetooth:MEAS:ISIGnal:ADETected:AADDress:LENergy:LE1M?
FETCh:BLUetooth:MEAS:ISIGnal:ADETected:PATTern:LENergy:LE1M?
FETCh:BLUetooth:MEAS:ISIGnal:ADETected:PLENgth:LENergy:LE1M?
// *****************************************************************************
// Change the signal configuration and R&S CMW settings for LE packets.
// Start a LE 2M PHY measurement, read the auto-detected signal
// properties.
// *****************************************************************************
CONFigure:BLUetooth:MEAS:ISIGnal:BTYPe LE
CONFigure:BLUetooth:MEAS:ISIGnal:LENergy:PHY LE2M
READ:BLUetooth:MEAS:MEValuation:MODulation:LENergy:LE2M:AVERage?
FETCh:BLUetooth:MEAS:MEValuation:MODulation:LENergy:LE2M:YIELd?
FETCh:BLUetooth:MEAS:ISIGnal:ADETected:PTYPe:LENergy:LRANge?
FETCh:BLUetooth:MEAS:ISIGnal:ADETected:PATTern:LENergy:LE2M?
FETCh:BLUetooth:MEAS:ISIGnal:ADETected:PLENgth:LENergy:LE2M?
FETCh:BLUetooth:MEAS:ISIGnal:ADETected:CODing:LENergy:LE2M?
// *********************************************************************************
// Reset
// *********************************************************************************
SYSTem:RESet 'Bluetooth Meas1'; *OPC?
*CLS; *OPC?
// *********************************************************************************
// Define signal routing and external attenuation
// *********************************************************************************
ROUTe:BLUetooth:MEAS:SCENario:SALone RF1C, RX1
CONFigure:BLUetooth:MEAS:RFSettings:EATTenuation 2
// *********************************************************************************
// Specify the transmitted BD address.
// *****************************************************************************
CONFigure:BLUetooth:MEAS:ISIGnal:BDADdress #H565634121212
// *********************************************************************************
// Define 2 segments with a length of 5 BR bursts each, different expected
// nominal power, pattern, and trigger and identical remaining settings.
//
// Alternatively use individual ...:SET:... commands.
// *********************************************************************************
CONF:BLUetooth:MEAS:MEV:LIST:COUNt 2
CONF:BLUetooth:MEAS:MEV:LIST:SEGM1:SET BR,DH1,P11,27,1,5,ON,7,2402E+6,NARR,OFF
CONF:BLUetooth:MEAS:MEV:LIST:SEGM2:SET BR,DH1,P44,27,1,5,ON,0,2402E+6,NARR,ON
CONF:BLUetooth:MEAS:MEV:LIST:SEGM1:SET:BTYPe BR
CONF:BLUetooth:MEAS:MEV:LIST:SEGM2:SET:BTYPe BR
CONF:BLUetooth:MEAS:MEV:LIST:SEGM1:SET:PTYPe DH1
CONF:BLUetooth:MEAS:MEV:LIST:SEGM2:SET:PTYPe DH1
CONF:BLUetooth:MEAS:MEV:LIST:SEGM1:SET:PATTern P11
CONF:BLUetooth:MEAS:MEV:LIST:SEGM2:SET:PATTern P44
CONF:BLUetooth:MEAS:MEV:LIST:SEGM1:SET:PLENgth 27
CONF:BLUetooth:MEAS:MEV:LIST:SEGM2:SET:PLENgth 27
CONF:BLUetooth:MEAS:MEV:LIST:SEGM1:SET:OSLots 1
CONF:BLUetooth:MEAS:MEV:LIST:SEGM2:SET:OSLots 1
CONF:BLUetooth:MEAS:MEV:LIST:SEGM1:SET:SLENgth 5
CONF:BLUetooth:MEAS:MEV:LIST:SEGM2:SET:SLENgth 5
CONF:BLUetooth:MEAS:MEV:LIST:SEGM1:SET:MOEXception ON
CONF:BLUetooth:MEAS:MEV:LIST:SEGM2:SET:MOEXception ON
CONF:BLUetooth:MEAS:MEV:LIST:SEGM1:SET:ENPower 7
CONF:BLUetooth:MEAS:MEV:LIST:SEGM2:SET:ENPower 0
CONF:BLUetooth:MEAS:MEV:LIST:SEGM1:SET:FREQuency 2402E+6
CONF:BLUetooth:MEAS:MEV:LIST:SEGM2:SET:FREQuency 2402E+6
CONF:BLUetooth:MEAS:MEV:LIST:SEGM1:SET:FILTer NARR
CONF:BLUetooth:MEAS:MEV:LIST:SEGM2:SET:FILTer NARR
CONF:BLUetooth:MEAS:MEV:LIST:SEGM1:SET:RTRigger OFF
CONF:BLUetooth:MEAS:MEV:LIST:SEGM2:SET:RTRigger ON
// *********************************************************************************
// Alternatively define 2 segments for LE coded
CONF:BLUetooth:MEAS:MEV:LIST:SEGM1:SET:BTYPe LE
CONF:BLUetooth:MEAS:MEV:LIST:SEGM2:SET:BTYPe LE
CONF:BLUetooth:MEAS:MEV:LIST:SEGM1:SET:PHY LELR
CONF:BLUetooth:MEAS:MEV:LIST:SEGM2:SET:PHY LELR
CONF:BLUetooth:MEAS:MEV:LIST:SEGM1:SET:CSCHeme S8
CONF:BLUetooth:MEAS:MEV:LIST:SEGM2:SET:CSCHeme S8
// *********************************************************************************
// Enable modulation and power scalar results and spectrum 20 dB bandwidth
// results for segment 1 and spectrum ACP results for segment 2.
//
// Alternatively use individual ...:RESults:... commands.
// *********************************************************************************
CONF:BLUetooth:MEAS:MEV:LIST:SEGMent1:RESults ON,ON,ON,OFF,OFF
CONF:BLUetooth:MEAS:MEV:LIST:SEGMent2:RESults OFF,OFF,OFF,ON,OFF
CONF:BLUetooth:MEAS:MEV:LIST:SEGMent1:RESults:MSCalar ON
CONF:BLUetooth:MEAS:MEV:LIST:SEGMent1:RESults:PSCalar ON
CONF:BLUetooth:MEAS:MEV:LIST:SEGMent1:RESults:SOBW ON
CONF:BLUetooth:MEAS:MEV:LIST:SEGMent2:RESults:SACP ON
// *********************************************************************************
// Set statistic count for the particular measurement type.
//
// Alternatively use individual ...:SCOunt:... commands.
// *********************************************************************************
CONFigure:BLUetooth:MEAS:MEV:LIST:SEGMent1:SCOunt 4,5,3,1,1
CONFigure:BLUetooth:MEAS:MEV:LIST:SEGMent2:SCOunt 1,1,1,5,1
CONFigure:BLUetooth:MEAS:MEV:LIST:SEGMent1:SCOunt:MSCalar 4
CONFigure:BLUetooth:MEAS:MEV:LIST:SEGMent1:SCOunt:PSCalar 5
CONFigure:BLUetooth:MEAS:MEV:LIST:SEGMent1:SCOunt:SOBW 3
CONFigure:BLUetooth:MEAS:MEV:LIST:SEGMent2:SCOunt:SACP 5
// *********************************************************************************
// Only for measurements with R&S CMWS:
// Configure the RF input connector per segment.
// *********************************************************************************
CONFigure:BLUetooth:MEAS:MEValuation:LIST:CMWS:CMODe LIST
CONFigure:BLUetooth:MEAS:MEValuation:LIST:SEGMent1:CMWS:CONNector R11
CONFigure:BLUetooth:MEAS:MEValuation:LIST:SEGMent2:CMWS:CONNector R12
// *********************************************************************************
// Enable the list mode.
// *********************************************************************************
CONFigure:BLUetooth:MEAS:MEValuation:LIST ON
// *********************************************************************************
// Start a measurement.
// Return modulation results for segment 1.
// *********************************************************************************
INIT:BLUetooth:MEAS:MEValuation
FETCh:BLUetooth:MEAS:MEValuation:LIST:SEGMent1:MODulation:CURRent?
FETCh:BLUetooth:MEAS:MEValuation:LIST:SEGMent1:MODulation:MAXimum?
FETCh:BLUetooth:MEAS:MEValuation:LIST:SEGMent1:MODulation:AVERage?
FETCh:BLUetooth:MEAS:MEValuation:LIST:SEGMent1:MODulation:MINimum?
// *********************************************************************************
// Return average and maximum statistical power results.
// *********************************************************************************
FETCh:BLUetooth:MEAS:MEValuation:LIST:SEGMent1:PVTime:CURRent?
FETCh:BLUetooth:MEAS:MEValuation:LIST:SEGMent1:PVTime:MAXimum?
// *********************************************************************************
// Return maximum 20 dB bandwidth spectrum results.
// *********************************************************************************
FETCh:BLUetooth:MEAS:MEValuation:LIST:SEGMent1:SOBW:MAXimum?
// *********************************************************************************
// Return spectrum ACP results.
// *********************************************************************************
FETCh:BLUetooth:MEAS:MEValuation:LIST:SEGMent2:SACP?
// *********************************************************************************
// Alternatively for LE coded PHY return current modulation
// results and standard deviation results
// *********************************************************************************
FETCh:BLUetooth:MEAS:MEValuation:LIST:SEGMent1:MODulation:CURRent:EXTended?
FETCh:BLUetooth:MEAS:MEValuation:LIST:SEGMent2:MODulation:CURRent:EXTended?
FETCh:BLUetooth:MEAS:MEValuation:LIST:SEGMent1:MODulation:SDEViation:EXTended?
FETCh:BLUetooth:MEAS:MEValuation:LIST:SEGMent2:MODulation:SDEViation:EXTended?
// *********************************************************************************
// System-Reset
// *********************************************************************************
*RST; *OPC?
*CLS; *OPC?
// *********************************************************************************
// Initial configuration to create temporary ARB file: set automatic
// detection, specify routing, set burst type LE, PHY LE1M, advertiser
// packet type. Specify advertiser channel frequency, or alternatively
// channel index. Set no measurement stop condition, disable
// measure on exception, enable only PvT and modulation
// views, set modulation and PvT statistic count to 1, set instrument
// address and address type. Enable ARB generation and start Tx measurement.
// *********************************************************************************
CONFigure:BLUetooth:MEAS:ISIGnal:DMODe AUTO
ROUTe:BLUetooth:MEAS:SCENario:SALone R11,RX11
CONFigure:BLUetooth:MEAS:ISIGnal:BTYPe LE
CONFigure:BLUetooth:MEAS:ISIGnal:LENergy:PHY LE1M
CONFigure:BLUetooth:MEAS:ISIGnal:PTYPe:LENergy:LE1M ADV
CONFigure:BLUetooth:MEAS:RFSettings:FREQuency 2402
CONFigure:BLUetooth:MEAS:RXQuality:AINDex 37
CONFigure:BLUetooth:MEAS:MEValuation:SCONdition NONE
CONFigure:BLUetooth:MEAS:MEValuation:MOEXception OFF
CONFigure:BLUetooth:MEAS:MEValuation:RESult:ALL OFF,OFF,ON,OFF,OFF,OFF,
OFF,OFF,ON,OFF,OFF,OFF,OFF,OFF
CONFigure:BLUetooth:MEAS:MEValuation:SCOunt:MODulation 1
CONFigure:BLUetooth:MEAS:MEValuation:SCOunt:PVTime 1
CONFigure:BLUetooth:MEAS:RXQuality:SADDress #H1234
CONFigure:BLUetooth:MEAS:RXQuality:SATYpe PUBL
CONFigure:BLUetooth:MEAS:RXQuality:GARB ON
// *********************************************************************************
// Execute training phase: Start TX Measurement, return PvT and
FETCh:BLUetooth:MEAS:MEValuation:PVTime:LENergy:LE1M:CURR?
FETCh:BLUetooth:MEAS:MEValuation:MODulation:LENergy:LE1M:CURR?
FETCh:BLUetooth:MEAS:ISIGnal:ADETected:PLENgth:LENergy:LE1M?
FETCh:BLUetooth:MEAS:ISIGnal:ADETected:AADDress:LENergy:LE1M?
FETCh:BLUetooth:MEAS:ISIGnal:ADETected:PTYPe:LENergy:LE1M?
FETCh:BLUetooth:MEAS:ISIGnal:ADETected:PATTern:LENergy:LE1M?
// *********************************************************************************
// Alternatively to measure at multiple channels, use list mode: enable
// list mode, specify the number of segments, enable only
// modulation and PvT measurements, set statistic count to 1.
// Start TX Measurement, return PvT and modulation current results.
// Disable list mode.
// *********************************************************************************
CONFigure:BLUetooth:MEAS:MEValuation:LIST:COUNTt 2
CONF:BLUetooth:MEAS:MEV:LIST:SEGM1:SET LE,ADV,OTH,27,1,1,OFF,7,2426E+6,NARR,ON
CONF:BLUetooth:MEAS:MEV:LIST:SEGM2:SET LE,ADV,OTH,27,1,1,OFF,7,2480E+6,NARR,ON
CONFigure:BLUetooth:MEAS:MEValuation:LIST:SEGM1:RESult ON,ON,OFF,OFF,OFF
CONFigure:BLUetooth:MEAS:MEValuation:LIST:SEGM2:RESult ON,ON,OFF,OFF,OFF
CONFigure:BLUetooth:MEAS:MEValuation:LIST:SEGM1:SCOunt 1,1,1,1,1
CONFigure:BLUetooth:MEAS:MEValuation:LIST:SEGM2:SCOunt 1,1,1,1,1
INITiate:BLUetooth:MEAS:MEValuation
FETCh:BLUetooth:MEAS:MEValuation:LIST:SEGM1:MODulation:CURRent?
FETCh:BLUetooth:MEAS:MEValuation:LIST:SEGM2:MODulation:CURRent?
FETCh:BLUetooth:MEAS:MEValuation:LIST:SEGM1:PVTime:CURRent?
FETCh:BLUetooth:MEAS:MEValuation:LIST:SEGM2:PVTime:CURRent?
// *********************************************************************************
// Configure Rx measurement: Select routing for RF output path,
// external attenuation and measurement mode.
// *********************************************************************************
CONFigure:BLUetooth:MEAS:RXQuality:ROUTe R11,RX11
CONFigure:BLUetooth:MEAS:RXQuality:ROUTe:USAGe:ALL R118,ON,OFF,OFF,OFF,
OFF,OFF,OFF,OFF
CONFigure:BLUetooth:MEAS:RXQuality:EATTenuation:OUTPut 5
CONFigure:BLUetooth:MEAS:RXQuality:MMODe SENS
// *********************************************************************************
// For PER measurement, set Tx level and number of SCAN_REQ advertisers,
// to be sent.
// *********************************************************************************
CONFigure:BLUetooth:MEAS:RXQuality:PER:LEVel -40
CONFigure:BLUetooth:MEAS:RXQuality:PER:RXPackets 1000
// *********************************************************************************
// For sensitivity search measurement, set number of retry attempts,
// initial Tx level and decrease power step.
// *********************************************************************************
CONFigure:BLUetooth:MEAS:RXQuality:SENSitivity:RETRy 2
CONFigure:BLUetooth:MEAS:RXQuality:SENSitivity:STARtlevel -40
CONFigure:BLUetooth:MEAS:RXQuality:SENSitivity:STEPsize 1
// *********************************************************************************
// For spot check, set Tx level.
// *********************************************************************************
CONFigure:BLUetooth:MEAS:RXQuality:SPOTcheck:LEVel -40
// *********************************************************************************
// Set trigger source to Bluetooth Meas:Power.
// *********************************************************************************
TRIGger:BLUetooth:MEAS:MEValuation:SOURce 'Bluetooth Meas:Power'
// *********************************************************************************
// Start the measurement and return the contents of the result table.
// Query the measurement state (should be "RDY").
// *********************************************************************************
INIT:BLUetooth:MEAS:RXQuality
FETCh:BLUetooth:MEAS:RXQuality?
FETCh:BLUetooth:MEAS:RXQuality:STATe?
FETCh:BLUetooth:MEAS:RXQuality:STATe:ALL?
// *********************************************************************************
// Query the PER results: detected EUT device address, PER,
// number of recieved SCAN_RSP.
// *********************************************************************************
FETCh:BLUetooth:MEAS:RXQuality:ADETected:AADDress?
FETCh:BLUetooth:MEAS:RXQuality:PER?
FETCh:BLUetooth:MEAS:RXQuality:PER:RXPackets?
// *********************************************************************************
// Query the sensitivity search measurement results.
// *********************************************************************************
FETCh:BLUetooth:MEAS:RXQuality:SENSitivity?
// *********************************************************************************
// Query the spot chec results.
// *********************************************************************************
FETCh:BLUetooth:MEAS:RXQuality:SPOTcheck?
// *********************************************************************************
// System-Reset
// *********************************************************************************
*RST; *OPC?
*CLS; *OPC?
// *********************************************************************************
// Initial configuration to create temporary ARB file: set automatic
// detection, specify routing, set burst type LE, PHY, LE test
// packet type. Specify sync word, and channel frequency.
// *********************************************************************************
CONFigure:BLUetooth:MEAS:ISIGnal:DMODe AUTO
ROUTe:BLUetooth:MEAS:SCENario:SALone R11,RX11
CONFigure:BLUetooth:MEAS:ISIGnal:BTYPe LE
CONFigure:BLUetooth:MEAS:ISIGnal:LENergy:PHY LE2M
CONFigure:BLUetooth:MEAS:ISIGnal:PTYPe:LENergy:LE2M RFPH
CONFigure:BLUetooth:MEAS:ISIGnal:LENergy:SYNWord #HFFFFFFFF
CONFigure:BLUetooth:MEAS:RFSettings:FREQuency 2402
// *********************************************************************************
// Clean old event log entries.
// *********************************************************************************
CLEan:BLUetooth:MEAS:ELOGging
// *********************************************************************************
// Select the serial interface for test control commands and HCI as
// communication protocol. Connect the DUT to a USB port and query
// the port list. Configure the further transmission settings accordingly.
// let reset the EUT before each test start command, specify
// delay after reset. Send custom HCI command to the DUT.
// Query the connected DUTs, send HCI reset and query the execution of DUT's reset.
// *********************************************************************************
CONFigure:BLUetooth:MEAS:HWINterface1 RS232
CONFigure:BLUetooth:MEAS:CPRotocol HCI
CONFigure:BLUetooth:MEAS:COMSettings:PORTs:CATalog?
CONFigure:BLUetooth:MEAS:COMSettings:BAUDrate B14K
CONFigure:BLUetooth:MEAS:COMSettings:COMPort 0
CONFigure:BLUetooth:MEAS:COMSettings:PARity EVEN
CONFigure:BLUetooth:MEAS:COMSettings:PROTocol NONE
CONFigure:BLUetooth:MEAS:COMSettings:STOPbits S1
CALL:BLUetooth:MEAS:DTMode:LENergy:RDEVices
CALL:BLUetooth:MEAS:DTMode:LENergy:RESet
CALL:BLUetooth:MEAS:DTMode:LENergy:RRESult?
// *********************************************************************************
// Monitor event log entries.
// *********************************************************************************
SENSe:BLUetooth:MEAS:ELOGging:ALL?
SENSe:BLUetooth:MEAS:ELOGging:LAST?
// *********************************************************************************
// Configure Rx measurement: Select routing for RF output path and
// external attenuation.
// *********************************************************************************
CONFigure:BLUetooth:MEAS:RXQuality:ROUTe R11,RX11
CONFigure:BLUetooth:MEAS:RXQuality:ROUTe:USAGe:ALL R118,ON,ON,ON,ON,
ON,ON,ON,ON
CONFigure:BLUetooth:MEAS:DTMode:RXQuality:EATTenuation:OUTPut 5
// *********************************************************************************
// Configure transmitted signal: payload pattern and length.
// Use standard modulation index
// *********************************************************************************
CONFigure:BLUetooth:MEAS:ISIGnal:DTMode:PATTern:LENergy:LE2M P11
CONFigure:BLUetooth:MEAS:ISIGnal:DTMode:PLENgth:LENergy:LE2M 37
CONFigure:BLUetooth:MEAS:DTMode:RXQuality:SMINdex:LENergy OFF
// *********************************************************************************
// For PER measurement, set Tx level, PER limit and integrity check.
// *********************************************************************************
CONFigure:BLUetooth:MEAS:DTMode:RXQuality:PER:LEVel -40
CONFigure:BLUetooth:MEAS:DTMode:RXQuality:LIMit:MPER:LENergy:LE2M 40
CONFigure:BLUetooth:MEAS:DTMode:RXQuality:RINTegrity:LENergy:LE2M OFF
// *********************************************************************************
// For PER search measurement, set start Tx level, level step,
// PER limit and integrity check.
// *********************************************************************************
CONFigure:BLUetooth:MEAS:DTMode:RXQuality:SEARch:STARtlevel -40
CONFigure:BLUetooth:MEAS:DTMode:RXQuality:SEARch:STEP 0.5
CONFigure:BLUetooth:MEAS:DTMode:RXQuality:SEARch:LIMit:MPER:LENergy:LE2M 40
CONFigure:BLUetooth:MEAS:DTMode:RXQuality:SEARch:RINTegrity:LENergy:LE2M OFF
// *********************************************************************************
// Start the PER measurement and return results.
// Query the measurement state (should be "RDY").
// *********************************************************************************
INIT:BLUetooth:MEAS:DTMode:RXQuality:PER
FETCh:BLUetooth:MEAS:DTMode:RXQuality:PER:LENergy:LE2M?
FETCh:BLUetooth:MEAS:DTMode:RXQuality:PER:STATe?
// *********************************************************************************
// Start the PER search measurement and return results.
// Query the measurement state (should be "RDY").
// *********************************************************************************
INIT:BLUetooth:MEAS:DTMode:RXQuality:SEARch:PER
FETCh:BLUetooth:MEAS:DTMode:RXQuality:PER:LENergy:LE2M?
FETCh:BLUetooth:MEAS:DTMode:RXQuality:SEARch:PER:STATe?
// *********************************************************************************
// System-Reset
// *********************************************************************************
*RST; *OPC?
*CLS; *OPC?
// *********************************************************************************
// Initial configuration to create temporary ARB file: set automatic
// detection, specify routing, set burst type LE, PHY LE1M, advertiser
// *********************************************************************************
// Execute training phase: Start TX Measurement, return PvT and
// modulation current results, payload length, advertiser address,
// packet and pattern type.
// *********************************************************************************
INITiate:BLUetooth:MEAS:MEValuation
FETCh:BLUetooth:MEAS:MEValuation:PVTime:LENergy:LE1M:CURR?
FETCh:BLUetooth:MEAS:MEValuation:MODulation:LENergy:LE1M:CURR?
FETCh:BLUetooth:MEAS:ISIGnal:ADETected:PLENgth:LENergy:LE1M?
FETCh:BLUetooth:MEAS:ISIGnal:ADETected:AADDress:LENergy:LE1M?
FETCh:BLUetooth:MEAS:ISIGnal:ADETected:PTYPe:LENergy:LE1M?
FETCh:BLUetooth:MEAS:ISIGnal:ADETected:PATTern:LENergy:LE1M?
// *********************************************************************************
// Configure Tx-Rx measurement: Select routing for RF output path,
// external attenuation and measurement mode.
// *********************************************************************************
CONFigure:BLUetooth:MEAS:RXQuality:ROUTe R11,RX11
CONFigure:BLUetooth:MEAS:RXQuality:ROUTe:USAGe:ALL R118,ON,OFF,OFF,OFF,
OFF,OFF,OFF,OFF
CONFigure:BLUetooth:MEAS:RXQuality:EATTenuation:OUTPut 5
CONFigure:BLUetooth:MEAS:RXQuality:MMODe SPOT
// *********************************************************************************
// Set spot check Tx level.
// *********************************************************************************
CONFigure:BLUetooth:MEAS:RXQuality:SPOTcheck:LEVel -40
// *********************************************************************************
// Set trigger source to Bluetooth Meas:Power.
// *********************************************************************************
TRIGger:BLUetooth:MEAS:MEValuation:SOURce 'Bluetooth Meas:Power'
// *********************************************************************************
// Start the measurement and return the contents of the result table.
// Query the measurement state (should be "RDY").
// *********************************************************************************
INIT:BLUetooth:MEAS:TRX
FETCh:BLUetooth:MEAS:TRX?
FETCh:BLUetooth:MEAS:TRX:STATe?
FETCh:BLUetooth:MEAS:TRX:STATe:ALL?
// *********************************************************************************
// Query all results.
// *********************************************************************************
FETCh:BLUetooth:MEAS:TRX:ACP?
FETCh:BLUetooth:MEAS:TRX:MODulation?
FETCh:BLUetooth:MEAS:TRX:POWer?
FETCh:BLUetooth:MEAS:TRX:SPOT?
The following sections describe the most important conventions and give general infor-
mation concerning the command reference.
7.6.1.1 MEAS<i>
The measurement is repeated according to the selected statistic count and repetition
mode. Consecutive measurement values are stored and used to calculate statistical
results.
Commands for result query often contain a mnemonic that indicates which results are
returned: CURRent, AVERage, EXTReme, MINimum, MAXimum or SDEViation.
To select an RF input path, you must specify an RF connector and an RX module (con-
verter).
Which connectors and modules can be specified in a command, depends on the instal-
led hardware, the test setup and the active subinstrument or instance <i>.
This chapter lists all values available for path selection. Depending on your configura-
tion, only a subset is relevant for you. Virtual connector names are only relevant for
setting commands. Queries return the physical connector names.
Additional information is available in the base software documentation. It describes typ-
ical instrument configurations with the allowed RF connector - TX/RX module combina-
tions and the mapping of virtual connector names to physical connectors.
R&S CMW100
The following values are applicable for up to four radio test heads connected to a sin-
gle PC.
RF path selection values:
● RX module:
RX11 | RX21 | RX31 | RX41
RX<a>1: radio test head <a>, RX 1
● RX connector:
R11 | R12 | R13 | R14 | R15 | R16 | R17 | R18
R21 | R22 | R23 | R24 | R25 | R26 | R27 | R28
R31 | R32 | R33 | R34 | R35 | R36 | R37 | R38
R41 | R42 | R43 | R44 | R45 | R46 | R47 | R48
RA1 | RA2 | RA3 | RA4 | RA5 | RA6 | RA7 | RA8
RB1 | RB2 | RB3 | RB4 | RB5 | RB6 | RB7 | RB8
RC1 | RC2 | RC3 | RC4 | RC5 | RC6 | RC7 | RC8
RD1 | RD2 | RD3 | RD4 | RD5 | RD6 | RD7 | RD8
R<a><n>: radio test head <a>, connector RF <n>
RA<n>: first radio test head of the subinstrument, <n>th connector of the subinstru-
ment
RB<n> / RC<n> / RD<n>: second / third / fourth radio test head of the subinstru-
ment, connector RF <n>
● TX module:
TX11 | TX21 | TX31 | TX41
TX<a>1: radio test head <a>, TX 1
● TX connector:
R118 | R218 | R318 | R418 | RA18 | RB18 | RC18 | RD18
R11O | R21O | R31O | R41O
R<a>18: radio test head <a>, connector RF 1 to RF 8 (connector bench)
RA18 / RB18 / RC18 / RD18: first / second / third / fourth radio test head of the
subinstrument, connector RF 1 to RF 8
R<a>1O: radio test head <a>, connector TX AUX
● Connector usage:
R11 | R12 | R13 | R14 | R15 | R16 | R17 | R18
R21 | R22 | R23 | R24 | R25 | R26 | R27 | R28
R31 | R32 | R33 | R34 | R35 | R36 | R37 | R38
R41 | R42 | R43 | R44 | R45 | R46 | R47 | R48
RA1 | RA2 | RA3 | RA4 | RA5 | RA6 | RA7 | RA8
RB1 | RB2 | RB3 | RB4 | RB5 | RB6 | RB7 | RB8
RC1 | RC2 | RC3 | RC4 | RC5 | RC6 | RC7 | RC8
RD1 | RD2 | RD3 | RD4 | RD5 | RD6 | RD7 | RD8
R<a><n>: radio test head <a>, connector RF <n>
RA<n>: first radio test head of the subinstrument, <n>th connector of the subinstru-
ment
RB<n> / RC<n> / RD<n>: second / third / fourth radio test head of the subinstru-
ment, connector RF <n>
7.6.1.5 Keywords
Selected keywords used in the command description are described in the following.
● Command usage
If the usage is not explicitly stated, the command allows you to set parameters and
query parameters. Otherwise, the command usage is stated as follows:
– "Setting only": The command can only be used to set parameters.
– "Query only": The command can only be used to query parameters.
– "Event": The command initiates an event.
● Parameter usage
The parameter usage is indicated by the keyword preceding the parameters:
– "Parameters" are sent with a setting or query command and are returned as
the result of a query.
– "Setting parameters" are sent with a setting command.
– "Query parameters" are sent with a query command, to refine the query.
– "Return values" are returned as the result of a query.
● Firmware/Software:
The first value in the output arrays of FETCh...?, READ...? and CALCulate...?
queries indicates the most severe error that has occurred during the measurement.
Example for an output array: 0, 10.22, 10.15, 10.01, 10.29, 100 (reliability = 0, followed
by 5 numeric measurement values).
The reliability indicator has one of the following values:
● 0 ("No Error"):
Measurement values available, no error detected.
● 1 ("Measurement Timeout"):
The measurement has been stopped after the configured measurement timeout.
Measurement results can be available. However, at least a part of the measure-
ment provides only INValid results or has not completed the full statistic count.
● 2 ("Capture Buffer Overflow"):
The measurement configuration results in a capture length that exceeds the availa-
ble memory.
● 3 ("Input Overdriven") / 4 ("Input Underdriven"):
The accuracy of measurement results can be impaired because the input signal
level was too high / too low.
● 6 ("Trigger Timeout"):
The measurement could not be started or continued because no trigger event was
detected.
● 7 ("Acquisition Error"):
The R&S CMW could not properly decode the RF input signal.
● 8 ("Sync Error"):
The R&S CMW could not synchronize to the RF input signal.
● 9 ("Uncal"):
Due to an inappropriate configuration of resolution bandwidth, video bandwidth or
sweep time, the measurement results are not within the specified data sheet limits.
● 15 ("Reference Frequency Error"):
The instrument has been configured to use an external reference signal. But the
reference oscillator could not be phase-locked to the external signal (for example
signal level too low, frequency out of range or reference signal not available at all).
● 16 ("RF Not Available"):
The measurement could not be started because the configured RF input path was
not active.
This problem can occur if a measurement is started in combined signal path mode
and the master application has not yet activated the input path.
● 17 ("RF Level Not Settled") / 18 ("RF Frequency Not Settled"):
The measurement could not be started because the R&S CMW was not yet ready
to deliver stable results after a change of the input signal power / the input signal
frequency.
The clock rate of the ARB file is either too high or too low.
● 47 ("ARB Cycles Out of Range"):
The repetition mode equals "Single Shot" and the playback length is too long.
Reduce the playback length or set the repetition mode to "Continuous".
<Length> = (<Cycles> * <Samples> + <Additional Samples>) / <Clock Rate>
● 52 ("Connection Error")
A connection setup failed or a connection was lost.
For Bluetooth: The EUT has been disconnected from the R&S CMW.
● 60 ("Invalid RF-Connector Setting")
The individual segments of a list mode measurement with R&S CMWS use differ-
ent connector benches. All segments must use the same bench.
Check the "Info" dialog for the relevant segment numbers.
● 70 ("Wrong Standard")
The standard of the measured signal does not match the configured standard.
● 71 ("Wrong Bandwidth")
The bandwidth of the measured signal does not match the configured bandwidth.
● 72 ("Wrong Burst Type")
The burst type of the measured signal does not match the configured burst type.
● 73 ("MIMO Signal Detected")
The measurement expects a SISO signal and detected a MIMO signal. Use a
MIMO receive mode to measure this signal.
● 74 ("More Streams than Antennas")
The measured signal has more streams than expected due to the configured num-
ber of antennas. Increase the configured number of antennas to measure this sig-
nal.
● 75 ("Matrix Inversion Failed")
The inversion of the channel matrix failed for a MIMO measurement. Check that
the antennas are connected correctly to the instrument.
● 76 ("SIG CRC Failed")
The cyclic redundancy check of a SIGNAL field failed.
● 77 ("Parity Check Failed")
The parity check of a SIGNAL field failed.
● 78 ("Bursts Not Identical")
In training mode for composite MIMO measurements, at least some symbols of
sequential bursts need to be identical to be used as training data. Setting a fix
scrambler initialization can solve this problem.
● 79 ("Wrong Modulation")
The modulation type of the measured signal does not match the configured modu-
lation type.
● 93 ("OCXO Oven Temperature Too Low"):
The accuracy of measurement results can be impaired because the oven-control-
led crystal oscillator has a too low temperature. After switching-on the instrument,
the OCXO requires a warm-up phase to reach its operating temperature.
● 101 ("Firmware Error"):
Indicates a firmware or software error. If you encounter this error for the first time,
restart the instrument.
The commands of "Bluetooth TX Measurement" are divided into the groups listed
below.
● Signal Routing.......................................................................................................496
● Analyzer Settings.................................................................................................. 499
● Input Signal Settings............................................................................................. 502
The following commands select the connector and define an external attenuation
value.
ROUTe:BLUetooth:MEAS<i>:SCENario:SALone............................................................... 497
ROUTe:BLUetooth:MEAS<i>:SCENario:CSPath............................................................... 497
ROUTe:BLUetooth:MEAS<i>?......................................................................................... 497
ROUTe:BLUetooth:MEAS<i>:SCENario?..........................................................................498
CONFigure:BLUetooth:MEAS<i>:RFSettings:EATTenuation............................................... 498
CONFigure:BLUetooth:MEAS<i>:RFSettings:CTE:LENergy:AOFFset................................. 498
CONFigure:BLUetooth:MEAS<i>:RFSettings:CTE:LENergy:NANTenna...............................499
ROUTe:BLUetooth:MEAS<i>:SCENario:CSPath <Master>
Activates the combined signal path scenario and selects a master. The master controls
the signal routing settings, analyzer settings and UE signal info settings while the com-
bined signal path scenario is active.
Parameters:
<Master> string
String parameter selecting the master application
Example: 'Bluetooth Sig1' or 'Bluetooth Sig2'
See Specifying General Measurement Settings
Firmware/Software: V3.2.30
Manual operation: See "Scenario, Controlled by" on page 428
ROUTe:BLUetooth:MEAS<i>?
Returns the configured routing settings.
For possible connector and converter values, see Chapter 7.6.1.4, "Values for RF Path
Selection", on page 489.
Return values:
<Scenario> SALone | CSPath
SALone: standalone (non-signaling)
CSPath: combined signal path
<Master> string
Master application for scenario CSPath
<RF Connector> RF connector for the input path
<RF Converter> RX module for the input path
Example: See Specifying General Measurement Settings
ROUTe:BLUetooth:MEAS<i>:SCENario?
Queries the active test scenario.
Return values:
<Scenario> SALone | CSPath
SALone: standalone (non-signaling)
CSPath: combined signal path
Example: See Specifying General Measurement Settings
Usage: Query only
Firmware/Software: V2.0.10
V3.2.30: "CSPath" added
Manual operation: See "Scenario, Controlled by" on page 428
CONFigure:BLUetooth:MEAS<i>:RFSettings:EATTenuation <ExternalAtt>
Defines an external attenuation (or gain, if the value is negative), to be applied to the
input connector.
For the combined signal path scenario, useCONFigure:BLUetooth:SIGN<i>:
RFSettings:EATTenuation:INPut.
Parameters:
<ExternalAtt> numeric
Range: -50 dB to 90 dB
*RST: 0 dB
Example: See Specifying General Measurement Settings
Firmware/Software: V1.0.10.1
Manual operation: See "External Attenuation (Input)" on page 428
CONFigure:BLUetooth:MEAS<i>:RFSettings:CTE:LENergy:AOFFset <AntRef1>,
<AntRef2>, <AntRef3>
Specifies the offset of external attenuation per input antenna relative to the reference
antenna. For the reference antenna, the offset is fixed and set to 0 dB.
Parameters:
<AntRef1> numeric
Range: -3 dB to 3 dB
*RST: 0 dB
<AntRef2> numeric
Range: -3 dB to 3 dB
*RST: 0 dB
<AntRef3> numeric
Range: -3 dB to 3 dB
*RST: 0 dB
Firmware/Software: V3.7.70
Options: R&S CMW-KM722
Manual operation: See "Antenna Attenuation (LE with CTE)" on page 440
CONFigure:BLUetooth:MEAS<i>:RFSettings:CTE:LENergy:NANTenna
<nofAntennas>
Specifies the number of DUT's antennas. One reference and one non-reference anten-
nas are mandatory.
Parameters:
<nofAntennas> numeric
Range: 2 to 4
*RST: 4
Firmware/Software: V3.7.70
Options: R&S CMW-KM722
Manual operation: See "No. of Antennas (LE with CTE)" on page 440
The following commands configure the RF input path and measured channel.
CONFigure:BLUetooth:MEAS<i>:RFSettings:ENPower......................................................499
CONFigure:BLUetooth:MEAS<i>:RFSettings:UMARgin..................................................... 500
CONFigure:BLUetooth:MEAS<i>:RFSettings:FREQuency..................................................500
CONFigure:BLUetooth:MEAS<i>:RFSettings:MMODe....................................................... 501
CONFigure:BLUetooth:MEAS<i>:RFSettings:MMODe:NMODe:LENergy............................. 501
CONFigure:BLUetooth:MEAS<i>:RFSettings:MCHannel[:CLASsic].....................................502
CONFigure:BLUetooth:MEAS<i>:RFSettings:MCHannel:LENergy...................................... 502
CONFigure:BLUetooth:MEAS<i>:RFSettings:ENPower <ExpNomPwr>
Sets the expected nominal power of the measured RF signal.
For the combined signal path scenario, useCONFigure:BLUetooth:SIGN<i>:
RFSettings:ENPower.
Parameters:
<ExpNomPwr> numeric
The range of the expected nominal power can be calculated as
follows:
Range (Expected Nominal Power) = Range (Input Power) +
External Attenuation - User Margin
The input power range is stated in the data sheet.
*RST: 0 dBm
Example: See Specifying General Measurement Settings
Firmware/Software: V1.0.10.1
Manual operation: See "Expected Nominal Power, Auto Ranging" on page 431
CONFigure:BLUetooth:MEAS<i>:RFSettings:UMARgin <UserMargin>
Sets the margin that the R&S CMW adds to the expected nominal power to determine
the reference level.
The reference level minus the external input attenuation must be within the power
range of the selected input connector; refer to the data sheet.
For the combined signal path scenario, useCONFigure:BLUetooth:SIGN<i>:
RFSettings:UMARgin.
Parameters:
<UserMargin> numeric
Range: 0 dB to (55 dB + external attenuation - expected
nominal power)
*RST: 0 dB
Example: See Specifying General Measurement Settings
Firmware/Software: V1.0.10.1
Manual operation: See "User Margin" on page 431
CONFigure:BLUetooth:MEAS<i>:RFSettings:FREQuency <AnalyzerFreq>
Selects the center frequency of the RF analyzer.
For the combined signal path scenario, use:
● CONFigure:BLUetooth:SIGN<i>:RFSettings:CHANnel:LOOPback
● CONFigure:BLUetooth:SIGN<i>:RFSettings:CHANnel:TXTest
● CONFigure:BLUetooth:SIGN<i>:RFSettings:FREQuency:LOOPback?
● CONFigure:BLUetooth:SIGN<i>:RFSettings:FREQuency:TXTest?
● CONFigure:BLUetooth:SIGN<i>:RFSettings:HOPPing
● CONFigure:BLUetooth:MEAS<i>:RFSettings:MMODe
● CONFigure:BLUetooth:MEAS<i>:RFSettings:MCHannel[:CLASsic]
Parameters:
<AnalyzerFreq> numeric
Range: 100E+6 Hz to 6E+9 Hz
Increment: 0.1 Hz
*RST: 2.402E+9 Hz
Default unit: Hz
Example: See Specifying General Measurement Settings
Firmware/Software: V1.0.10.1
Manual operation: See "Frequency, Channel, Advertising Index" on page 429
CONFigure:BLUetooth:MEAS<i>:RFSettings:MMODe <MeasureMode>
Sets measure mode for BR/EDR test mode in combined signal path scenario during
hopping enabled.
Parameters:
<MeasureMode> ALL | SINGle
ALL: multi-evaluation TX measurements on all channels
SINGle: multi-evaluation TX measurements on specified chan-
nel, see CONFigure:BLUetooth:MEAS<i>:RFSettings:
MCHannel[:CLASsic]
*RST: ALL
Example: See Specifying General Measurement Settings
Firmware/Software: V3.2.30
Manual operation: See "Hopping, Measure Mode" on page 430
CONFigure:BLUetooth:MEAS<i>:RFSettings:MMODe:NMODe:LENergy
<MeasureMode>
Specifies measurement mode for LE connection tests in combined signal path sce-
nario.
● All 37 data channels can only be measured if signaling application uses all channel
hopping mode.
● Single channel mode enables Tx measurements at the specified RF channel
For the combined signal path scenario, use CONFigure:BLUetooth:SIGN<i>:
RFSettings:NMODe:HMODe:LENergy
Parameters:
<MeasureMode> ALL | SINGle
*RST: SING
Firmware/Software: V3.7.61
Manual operation: See "Measure Mode" on page 466
CONFigure:BLUetooth:MEAS<i>:RFSettings:MCHannel[:CLASsic]
<MeasuredChannel>
Specifies the channel to be measured in CSP single channel mode for classic, see
CONFigure:BLUetooth:MEAS<i>:RFSettings:MMODe
Parameters:
<MeasuredChannel> numeric
Range: 0 to 78
Example: See Specifying General Measurement Settings
Firmware/Software: V3.2.30, V3.7.51: added token [:CLASsic]
Manual operation: See "Hopping, Measure Mode" on page 430
CONFigure:BLUetooth:MEAS<i>:RFSettings:MCHannel:LENergy
<MeasuredChannel>
Specifies the channel to be measured in CSP single channel mode with LE connection
tests, see CONFigure:BLUetooth:MEAS<i>:RFSettings:MMODe:NMODe:
LENergy
Parameters:
<MeasuredChannel> numeric
Channel number
Range: 1 to 11, 13 to 38
Example: See Specifying General Measurement Settings
Firmware/Software: V3.7.61
Options: R&S CMW-KM611
Manual operation: See "Measured Channel, Hopping Channels (CSP)"
on page 466
The following commands define the basic properties of the measured Bluetooth signal.
CONFigure:BLUetooth:MEAS<i>:ISIGnal:DMODe.............................................................503
CONFigure:BLUetooth:MEAS<i>:ISIGnal:BTYPe.............................................................. 503
CONFigure:BLUetooth:MEAS<i>:ISIGnal:ASYNchronize................................................... 504
CONFigure:BLUetooth:MEAS<i>:ISIGnal:BDADdress........................................................504
CONFigure:BLUetooth:MEAS<i>:ISIGnal:LAP.................................................................. 504
CONFigure:BLUetooth:MEAS<i>:ISIGnal:UAP..................................................................505
CONFigure:BLUetooth:MEAS<i>:ISIGnal:NAP..................................................................505
CONFigure:BLUetooth:MEAS<i>:ISIGnal:PTYPe:BRATe................................................... 505
CONFigure:BLUetooth:MEAS<i>:ISIGnal:PTYPe:EDRate.................................................. 506
CONFigure:BLUetooth:MEAS<i>:ISIGnal:PTYPe:LENergy:LE2M....................................... 506
CONFigure:BLUetooth:MEAS<i>:ISIGnal:PTYPe:LENergy[:LE1M]......................................506
CONFigure:BLUetooth:MEAS<i>:ISIGnal:PTYPe:LENergy:LRANge....................................506
CONFigure:BLUetooth:MEAS<i>:ISIGnal:LENergy:PHY.................................................... 507
CONFigure:BLUetooth:MEAS<i>:ISIGnal:LENergy:SYNWord.............................................507
CONFigure:BLUetooth:MEAS<i>:ISIGnal:ACCaddress:LENergy.........................................508
CONFigure:BLUetooth:MEAS<i>:ISIGnal:PATTern............................................................ 508
CONFigure:BLUetooth:MEAS<i>:ISIGnal:PATTern:LENergy:LE2M..................................... 508
CONFigure:BLUetooth:MEAS<i>:ISIGnal:PATTern:LENergy[:LE1M]....................................508
CONFigure:BLUetooth:MEAS<i>:ISIGnal:PATTern:LENergy:LRANge..................................509
CONFigure:BLUetooth:MEAS<i>:ISIGnal:FEC:LENergy:LRANge....................................... 509
CONFigure:BLUetooth:MEAS<i>:ISIGnal:PLENgth:BRATe.................................................510
CONFigure:BLUetooth:MEAS<i>:ISIGnal:PLENgth:EDRate............................................... 510
CONFigure:BLUetooth:MEAS<i>:ISIGnal:PLENgth:LENergy:LRANge................................. 511
CONFigure:BLUetooth:MEAS<i>:ISIGnal:PLENgth:LENergy:LE2M..................................... 511
CONFigure:BLUetooth:MEAS<i>:ISIGnal:PLENgth:LENergy[:LE1M]................................... 511
CONFigure:BLUetooth:MEAS<i>:ISIGnal:CTE:LENergy:LE1M:TYPE..................................512
CONFigure:BLUetooth:MEAS<i>:ISIGnal:CTE:LENergy:LE2M:TYPE..................................512
CONFigure:BLUetooth:MEAS<i>:ISIGnal:CTE:LENergy:LE1M:UNITs................................. 512
CONFigure:BLUetooth:MEAS<i>:ISIGnal:CTE:LENergy:LE2M:UNITs................................. 512
CONFigure:BLUetooth:MEAS<i>:ISIGnal:OSLots:BRATe................................................... 512
CONFigure:BLUetooth:MEAS<i>:ISIGnal:OSLots:EDRate................................................. 512
CONFigure:BLUetooth:MEAS<i>:ISIGnal:OSLots:LENergy:LE2M.......................................513
CONFigure:BLUetooth:MEAS<i>:ISIGnal:OSLots:LENergy[:LE1M]..................................... 513
Firmware/Software: V1.0.10.1
V2.1.20: added LE
Options: R&S CMW-KM610 for BR and EDR
R&S CMW-KM611 for LE
Manual operation: See "Burst Type" on page 434
CONFigure:BLUetooth:MEAS<i>:ISIGnal:ASYNchronize <AutoSynch>
Disables / enables automatic synchronization to the captured signal for an unspecified
Bluetooth device address.
Parameters:
<AutoSynch> OFF | ON
*RST: OFF
Example: See Basic Input Signal Properties: EDR Packets
Firmware/Software: V3.5.40
Manual operation: See "Auto Sync (BR/EDR)" on page 434
CONFigure:BLUetooth:MEAS<i>:ISIGnal:BDADdress <BDAddress>
Specifies the Bluetooth device address that the R&S CMW expects the EUT to use to
generate its access code.
Parameters:
<BDAddress> hex
12-digit hex number
Range: #H0 to #HFFFFFFFFFFFF
*RST: #H000000123456
Example: See Basic Input Signal Properties: EDR Packets
Firmware/Software: V1.0.10.1
Manual operation: See "BD Address (BR/EDR)" on page 434
CONFigure:BLUetooth:MEAS<i>:ISIGnal:LAP <BDAddressLAP>
Specifies the lower address part of the DUT's Bluetooth device address.
Parameters:
<BDAddressLAP> hex
Six-digit hex number
Range: #H0 to #HFFFFFF
*RST: #H123456
Example: See Basic Input Signal Properties: EDR Packets
Firmware/Software: V1.0.10.1
CONFigure:BLUetooth:MEAS<i>:ISIGnal:UAP <BDAddressUAP>
Specifies the upper address part of the DUT's Bluetooth device address.
Parameters:
<BDAddressUAP> hex
Two-digit hex number
Range: #H0 to #HFF
*RST: #H00
Example: See Basic Input Signal Properties: EDR Packets
Firmware/Software: V1.0.10.1
Manual operation: See "BD Address (BR/EDR)" on page 434
CONFigure:BLUetooth:MEAS<i>:ISIGnal:NAP <BDAddressNAP>
Specifies the non-specific address part of the EUT's Bluetooth device address.
Parameters:
<BDAddressNAP> hex
Four-digit hex number
Range: #H0 to #HFFFF
*RST: #H0000
Example: See Basic Input Signal Properties: EDR Packets
Firmware/Software: V1.0.10.1
Manual operation: See "BD Address (BR/EDR)" on page 434
CONFigure:BLUetooth:MEAS<i>:ISIGnal:PTYPe:LENergy:LE2M
<ELE_Packet_Type>
CONFigure:BLUetooth:MEAS<i>:ISIGnal:PTYPe:LENergy[:LE1M] <LE Packet
Type>
Specifies the packet type of the measured signal for LE uncoded PHY (LE 1M and LE
2M).
Data channel packet cannot be selected. It is only automatically selected in combined
signal path with LE connection tests.
Parameters:
<LE Packet Type> RFPHytest | ADVertiser | RFCTe
RFPHytest: LE test packet
ADVertiser: air interface packet with advertising channel PDU
RFCTe: LE with CTE test packet
*RST: RFPH
Example: See Basic Input Signal Properties: LE Packets
Firmware/Software: V3.5.60, V3.7.61: added command LE2M, V3.7.70: added RFCT
V3.7.90: ADVertiser supported also with LE2M command
Options: R&S CMW-KM611
R&S CMW-KM721 for LE2M
R&S CMW-KM722 for RFCTe
Manual operation: See "Packet Type" on page 436
CONFigure:BLUetooth:MEAS<i>:ISIGnal:PTYPe:LENergy:LRANge
<LELRPacketType>
Specifies the packet type of the measured signal for LE coded PHY.
Data channel packet cannot be selected. It is only automatically selected in combined
signal path with LE connection tests.
Parameters:
<LELRPacketType> RFPHytest | ADVertiser
RFPHytest: LE test packet
ADVertiser: air interface packet with advertising channel PDU
*RST: RFPH
Example: See Basic Input Signal Properties: LE Packets
Firmware/Software: V3.7.90
Options: R&S CMW-KM721
Manual operation: See "Packet Type" on page 436
CONFigure:BLUetooth:MEAS<i>:ISIGnal:LENergy:PHY <PHY>
Selects the physical layer used for LE measurements.
For the combined signal path scenario, use CONFigure:BLUetooth:SIGN<i>:
CONNection:PHY:LENergy
Parameters:
<PHY> LE1M | LE2M | LELR
LE1M: LE 1 Msymbol/s uncoded PHY
LE2M: LE 2 Msymbol/s uncoded PHY
LELR: LE 1 Msymbol/s long range (LE coded PHY)
*RST: LE1M
Example: See Basic Input Signal Properties: LE Packets
Firmware/Software: V3.5.70
Options: R&S CMW-KM611
Plus R&S CMW-KM721 for LE2M and LELR
Manual operation: See "PHY (LE)" on page 435
CONFigure:BLUetooth:MEAS<i>:ISIGnal:LENergy:SYNWord <SynchWord>
Specifies the synchronization word used during direct test mode.
For the combined signal path scenario, use CONFigure:BLUetooth:SIGN<i>:
CONNection:SYNWord:LENergy
Parameters:
<SynchWord> hex
Range: #H0 to #HFFFFFFFF
*RST: #H71764129
Example: See Performing PvT and Modulation Measurements
Firmware/Software: V3.5.70
Options: R&S CMW-KM611
Manual operation: See "Test Packet Sync Word (LE)" on page 437
CONFigure:BLUetooth:MEAS<i>:ISIGnal:ACCaddress:LENergy <AccessAddress>
Specifies the access address of advertiser for standalone LE measurements.
Parameters:
<AccessAddress> hex
Range: #H0 to #HFFFFFFFF
*RST: #H8E89BED6
Example: See Basic Input Signal Properties: LE Packets
Firmware/Software: V3.5.60
Options: R&S CMW-KM611
Manual operation: See "Access Address (LE)" on page 437
CONFigure:BLUetooth:MEAS<i>:ISIGnal:PATTern:LENergy:LRANge <Pattern
Type>
Specifies the data pattern type for LE coded PHY, that the EUT transmits as user pay-
load data.
For the combined signal path scenario, use CONFigure:BLUetooth:SIGN<i>:
CONNection:PACKets:PATTern:LENergy:LRANge
Parameters:
<Pattern Type> ALL1 | OTHer
ALL1: '11111111'
OTHer: any pattern except ALL1
*RST: ALL1
Example: See Basic Input Signal Properties: LE Packets
Firmware/Software: V3.5.70
Options: R&S CMW-KM721
Manual operation: See "Pattern Type" on page 438
CONFigure:BLUetooth:MEAS<i>:ISIGnal:FEC:LENergy:LRANge <CodingScheme>
Defines S coding for LE coded PHY according to the core specification version 5.0 for
Bluetooth wireless technology.
CONFigure:BLUetooth:MEAS<i>:ISIGnal:PLENgth:BRATe <PayloadLength>(3)
Specifies the number of bytes (octets) in the payload data of the measured BR signal.
The range of values depends on the packet type (CONFigure:BLUetooth:
MEAS<i>:ISIGnal:PTYPe:BRATe).
The command requires 3 comma-separated parameters, one for each BR packet type
(order: DH1, DH3, DH5).
For the combined signal path scenario, useCONFigure:BLUetooth:SIGN<i>:
CONNection:PACKets:PLENgth:BRATe.
Parameters:
<PayloadLength> numeric
3 payload lengths for BR packets
Range: 0 to 27 (DH1), 0 to 183 (DH3), 0 to 339 (DH5)
*RST: Maximum value for each packet type
Example: See Performing PvT and Modulation Measurements
Firmware/Software: V1.0.10.1
Manual operation: See "Payload Length" on page 437
CONFigure:BLUetooth:MEAS<i>:ISIGnal:PLENgth:EDRate <PayloadLength>(6)
Specifies the number of bytes (octets) in the payload data of the measured EDR sig-
nal. The range of values depends on the packet type (CONFigure:BLUetooth:
MEAS<i>:ISIGnal:PTYPe:EDRate).
The command requires 6 comma-separated parameters, one for each EDR packet
type (order: 2-DH1, 2-DH3, 2-DH5, 3-DH1, 3-DH3, 3-DH5).
For the combined signal path scenario, useCONFigure:BLUetooth:SIGN<i>:
CONNection:PACKets:PLENgth:EDRate.
Parameters:
<PayloadLength> numeric
6 payload lengths for EDR packets
Range: 0 to 54 (2-DH1), 0 to 367 (2-DH3), 0 to 679 (2-
DH5), 0 to 83 (3-DH1), 0 to 552 (3-DH3), 0 to 1021
(3-DH5)
*RST: Maximum value for each packet type
Example: See Basic Input Signal Properties: EDR Packets
Firmware/Software: V1.0.10.1
Manual operation: See "Payload Length" on page 437
CONFigure:BLUetooth:MEAS<i>:ISIGnal:PLENgth:LENergy:LRANge
<PayloadLength>
CONFigure:BLUetooth:MEAS<i>:ISIGnal:PLENgth:LENergy:LE2M
<PayloadLength>
CONFigure:BLUetooth:MEAS<i>:ISIGnal:PLENgth:LENergy[:LE1M]
<PayloadLength>
Specifies the number of bytes (octets) in the payload data of the measured LE test
packets.
Commands for uncoded LE 1M PHY (..:LE1M..), LE 2M PHY (..:LE2M..), and LE
coded PHY (..:LRANge..) are available.
For the combined signal path scenario, use:
● CONFigure:BLUetooth:SIGN<i>:CONNection:PACKets:PLENgth:
LENergy[:LE1M]
● CONFigure:BLUetooth:SIGN<i>:CONNection:PACKets:PLENgth:
LENergy:LE2M
● CONFigure:BLUetooth:SIGN<i>:CONNection:PACKets:PLENgth:
LENergy:LRANge
Parameters:
<PayloadLength> numeric
Payload lengths for LE packets
Range: 0 Byte(s) to 255 Byte(s)
*RST: 37 Byte(s)
Default unit: byte
Example: See Performing PvT and Modulation Measurements
Firmware/Software: V2.1.20
V3.5.20: range extended
V3.5.70: added commands for LE2M and LRANge
Options: R&S CMW-KM611
Plus R&S CMW-KM721 for LE2M and LRANge
Manual operation: See "Payload Length" on page 437
CONFigure:BLUetooth:MEAS<i>:ISIGnal:CTE:LENergy:LE1M:TYPE <CteType>
CONFigure:BLUetooth:MEAS<i>:ISIGnal:CTE:LENergy:LE2M:TYPE <CteType>
Specifies the CTE slot type for LE with CTE.
Commands for uncoded LE 1M PHY (..:LE1M..) and LE 2M PHY (..:LE2M..) are
available.
Parameters:
<CteType> AOAus | AOD1us | AOD2us | AOA2us | AOA1us
AOD1us, AOD2us: CTE type angle of departure, 1 µs or 2 µs
slot
AOAus, AOA2us: CTE type angle of arrival, 2 µs slot
AOA1us: CTE type angle of arrival, 1 µs slot
*RST: AOA
Example: See Performing LE with CTE Measurements
Firmware/Software: V3.7.70
V3.7.90: added AOA1us
Options: R&S CMW-KM722
Manual operation: See "CTE Slot Type (LE with CTE)" on page 439
CONFigure:BLUetooth:MEAS<i>:ISIGnal:CTE:LENergy:LE1M:UNITs <CteUnits>
CONFigure:BLUetooth:MEAS<i>:ISIGnal:CTE:LENergy:LE2M:UNITs <CteUnits>
Specifies the number of CTE units for LE with CTE.
Commands for uncoded LE 1M PHY (..:LE1M..) and LE 2M PHY (..:LE2M..) are
available.
Parameters:
<CteUnits> numeric
Range: 2 to 20
*RST: 2
Example: See Performing LE with CTE Measurements
Firmware/Software: V3.7.70
Options: R&S CMW-KM722
Manual operation: See "CTE Units (LE with CTE)" on page 440
CONFigure:BLUetooth:MEAS<i>:ISIGnal:OSLots:BRATe <NoOfOffSlots>(3)
CONFigure:BLUetooth:MEAS<i>:ISIGnal:OSLots:EDRate <NoOfOffSlots>(6)
Specifies the number of unused slots between any two occupied slots or slot sequen-
ces.
Parameters:
<NoOfOffSlots> numeric
Number of off slots for the different packet types:
3 values for BR packets (DH1, DH3, DH5)
6 values for EDR packets (2-DH1, 2-DH3, 2-DH5, 3-DH1, 3-
DH3, 3-DH5)
Range: 1 to 9
*RST: 1
Example: See Performing Spectrum Measurements
Firmware/Software: V2.0.20
Manual operation: See "No. of Off Slots " on page 441
CONFigure:BLUetooth:MEAS<i>:ISIGnal:OSLots:LENergy:LE2M <NoOfOffSlots>
CONFigure:BLUetooth:MEAS<i>:ISIGnal:OSLots:LENergy[:LE1M] <NoOfOffSlots>
Specifies the number of unused slots between any two occupied slots or slot sequen-
ces.
Commands for LE 1M PHY (...:LE1M...) and LE 2M PHY (...:LE2M...) are
available.
Parameters:
<NoOfOffSlots> numeric
Range: 1 to 9
*RST: 1
Default unit: Multiplies of 625 µs
Example: See Performing Spectrum Measurements
Firmware/Software: V3.5.20
V3.5.70: added command for LE2M
Options: R&S CMW-KM611
Plus R&S CMW-KM721 for LE2M
Manual operation: See "No. of Off Slots " on page 441
The commands valid for the Bluetooth multi-evaluation Tx measurement are divided
into the groups listed below.
● Measurement Control and States......................................................................... 514
● Measurement Parameters.....................................................................................517
● Enabling Results and Views..................................................................................523
● List Mode Settings.................................................................................................526
● Trigger Settings.....................................................................................................541
● Limits (Power vs. Time).........................................................................................543
● Limits (Modulation BR)..........................................................................................547
● Limits (Modulation EDR)....................................................................................... 551
The following commands control the measurement and return the current measure-
ment state.
INITiate:BLUetooth:MEAS<i>:MEValuation....................................................................... 514
STOP:BLUetooth:MEAS<i>:MEValuation..........................................................................514
ABORt:BLUetooth:MEAS<i>:MEValuation........................................................................ 514
FETCh:BLUetooth:MEAS<i>:MEValuation:STATe?............................................................ 515
FETCh:BLUetooth:MEAS<i>:MEValuation:STATe:ALL?......................................................515
CONFigure:BLUetooth:MEAS<i>:DISPlay........................................................................ 516
INITiate:BLUetooth:MEAS<i>:MEValuation
STOP:BLUetooth:MEAS<i>:MEValuation
ABORt:BLUetooth:MEAS<i>:MEValuation
Starts, stops, or aborts the measurement:
● INITiate... starts or restarts the measurement. The measurement enters the
"RUN" state.
● STOP... halts the measurement immediately. The measurement enters the "RDY"
state. Measurement results are kept. The resources remain allocated to the mea-
surement.
● ABORt... halts the measurement immediately. The measurement enters the
"OFF" state. All measurement values are set to NAV. Allocated resources are
released.
Use FETCh...STATe? to query the current measurement state.
FETCh:BLUetooth:MEAS<i>:MEValuation:STATe?
Queries the main measurement state. Use FETCh:...:STATe:ALL? to query the
measurement state including the substates. Use INITiate..., STOP...,
ABORt... to change the measurement state.
Return values:
<MeasState> OFF | RUN | RDY
OFF: Measurement switched off, no resources allocated, no
results available (when entered after ABORt...)
RUN: Measurement running (after INITiate..., READ...),
synchronization pending or adjusted, resources active or queued
RDY: Measurement has been terminated, valid results are avail-
able
*RST: OFF
Usage: Query only
Firmware/Software: V1.0.10.1
Manual operation: See "Multi Evaluation (Softkey)" on page 381
FETCh:BLUetooth:MEAS<i>:MEValuation:STATe:ALL?
Queries the main measurement state and the measurement substates. Both measure-
ment substates are relevant for running measurements only. Use FETCh:...:STATe?
to query the main measurement state only. Use INITiate..., STOP...,
ABORt... to change the measurement state.
Return values:
<MainState> OFF | RDY | RUN
OFF: Measurement switched off, no resources allocated, no
results available (when entered after STOP...)
RDY: Measurement has been terminated, valid results are avail-
able
RUN: Measurement running (after INITiate..., READ...),
synchronization pending or adjusted, resources active or queued
*RST: OFF
Firmware/Software: V3.2.50
Manual operation: See "Active View" on page 464
CONFigure:BLUetooth:MEAS<i>:MEValuation:TOUT <Timeout>
Defines a timeout for the measurement. The timer is started when the measurement is
initiated via a READ or INIT command. It is not started if the measurement is initiated
manually ([ON | OFF] key or [RESTART | STOP] key).
When the measurement has completed the first measurement cycle (first single shot),
the statistical depth is reached and the timer is reset.
If the first measurement cycle has not been completed when the timer expires, the
measurement is stopped. The measurement state changes to RDY. The reliability indi-
cator is set to 1, indicating that a measurement timeout occurred. Still running READ,
FETCh or CALCulate commands are completed, returning the available results. At
least for some results, there are no values at all or the statistical depth has not been
reached.
A timeout of 0 s corresponds to an infinite measurement timeout.
Parameters:
<Timeout> numeric
Default unit: s
Example: See Specifying General Measurement Settings
Firmware/Software: V2.0.10
CONFigure:BLUetooth:MEAS<i>:MEValuation:REPetition <Repetition>
Specifies the repetition mode of the measurement. The repetition mode specifies
whether the measurement is stopped after a single shot or repeated continuously. Use
CONFigure:..:MEAS<i>:...:SCOunt to determine the number of measurement
intervals per single shot.
Parameters:
<Repetition> SINGleshot | CONTinuous
SINGleshot: Single-shot measurement
CONTinuous: Continuous measurement
*RST: SINGleshot
Firmware/Software: V1.0.10.1
Manual operation: See "Repetition" on page 442
CONFigure:BLUetooth:MEAS<i>:MEValuation:MOEXception <MeasOnException>
Specifies whether measurement results that are identified as faulty or inaccurate are
rejected.
Parameters:
<MeasOnException> OFF | ON
ON: Results are never rejected
OFF: Faulty results are rejected
*RST: OFF
Example: See Configuring Measurements
Firmware/Software: V1.0.10.1
Manual operation: See "Measure on Exception" on page 443
CONFigure:BLUetooth:MEAS<i>:MEValuation:SCOunt:MODulation
<StatisticCount>
CONFigure:BLUetooth:MEAS<i>:MEValuation:SCOunt:PENCoding
<StatisticCount>
CONFigure:BLUetooth:MEAS<i>:MEValuation:SCOunt:PVTime <StatisticCount>
CONFigure:BLUetooth:MEAS<i>:MEValuation:SCOunt:SOBW <StatisticCount>
Specifies the statistic count of the measurement. The statistic count is equal to the
number of measurement intervals per single shot.
The last mnemonic denotes the measurement type: statistical modulation, statistical
power and spectrum 20 dB bandwidth (occupied bandwidth) measurement.
Parameters:
<StatisticCount> numeric
Number of measurement intervals
Range: 1 to 1000
*RST: 10
Example: See Configuring Measurements
Firmware/Software: V1.0.10.1
V1.0.15.20: added command for spectrum 20 dB bandwidth
measurement
Manual operation: See "Power vs. Time / Modulation / Phase Encoding / Spectrum
> ... Statistic Count" on page 443
CONFigure:BLUetooth:MEAS<i>:MEValuation:SCOunt:FRANge <StatisticCount>
CONFigure:BLUetooth:MEAS<i>:MEValuation:SCOunt:SACP <StatisticCount>
CONFigure:BLUetooth:MEAS<i>:MEValuation:SCOunt:SGACp <StatisticCount>
Specifies the statistic count of the measurement. The statistic count is equal to the
number of measurement intervals per single shot.
The last mnemonic denotes the measurement type: spectrum frequency range, spec-
trum ACP and spectrum gated ACP.
Parameters:
<StatisticCount> numeric
Statistic count for the measurement
Range: 1 to 1000
*RST: 6
Example: See Configuring Measurements
Firmware/Software: V1.0.15.20
V2.0.20: added command for gated ACP
V3.2.50: added command for frequency range
Manual operation: See "Power vs. Time / Modulation / Phase Encoding / Spectrum
> ... Statistic Count" on page 443
CONFigure:BLUetooth:MEAS<i>:MEValuation:SACP:BRATe:MEASurement:
MODE <Meas Mode>
CONFigure:BLUetooth:MEAS<i>:MEValuation:SGACp:EDRate:MEASurement:
MODE <Meas Mode>
Selects the measured ACP channel range for BR or EDR packets. The ACP can be
measured over the expected transmit channel +/- 10 channels (21 channels in total) or
over the entire Bluetooth regulatory range (79 channels).
Parameters:
<Meas Mode> CH79 | CH21
Measure 79 or 21 channels
*RST: CH21
Example: See Performing Spectrum Measurements
Firmware/Software: V2.0.20
Manual operation: See "ACP Measurement Mode" on page 444
CONFigure:BLUetooth:MEAS<i>:MEValuation:SACP:LENergy:LE2M:
MEASurement:MODE <Meas Mode>
CONFigure:BLUetooth:MEAS<i>:MEValuation:SACP:LENergy[:LE1M]:
MEASurement:MODE <Meas Mode>
Specifies the channel range for ACP measurements. Can be selected to cover either
the full LE frequency band (forty 2 MHz channels) or only the adjacency of the current
LE channel (ten 2 MHz channels).
The commands for LE 1M PHY (...:LE1M...) and LE 2M PHY (...:LE2M...) are
available.
Note: Although LE channels are 2 MHz wide, the channel width in ACP measurements
is always 1 MHz ("half-channel").
Parameters:
<Meas Mode> CH40 | CH10
CH10: Covers the current and its 10 adjacent 2 MHz LE chan-
nels (5 to the left, 5 to the right). The R&S CMW measures the 1
MHz channels centered at fTX – 10 MHz, ..., fTX + 10 MHz.
CH40: Covers all 40 LE channels. The R&S CMW measures the
81 half-channels centered at 2401 MHz, 2402 MHz, ..., 2481
MHz.
*RST: CH10
Example: See Performing Spectrum Measurements
Firmware/Software: V2.1.20
V3.5.70: added commands for LE2M
Options: R&S CMW-KM611
Plus R&S CMW-KM721 for LE2M
Manual operation: See "ACP Measurement Mode" on page 444
CONFigure:BLUetooth:MEAS<i>:MEValuation:FRANge:BRATe:MEASurement
<LeftChannel>, <RightChannel>, <Threshold>
Specifies the number of 1 MHz channels to be measured below and above the current
measured channel. The threshold is the level that needs to be crossed to search the
frequencies fL and fH.
Parameters:
<LeftChannel> numeric
Left adjacent channel relative to the EUT center TX channel
Range: 1 to 5
*RST: 5
<RightChannel> numeric
Right adjacent channel relative to the EUT center TX channel
Range: 1 to 5
*RST: 5
<Threshold> numeric
Threshold for the spectral power density drop to search the fre-
quencies fL and fH
Specification defines - 80 dBm/Hz for equivalent isotropically
radiated power or - 30 dBm if measured in a 100 kHz bandwidth.
Range: -80 dBm to 40 dBm
*RST: -30 dBm
Example: See Performing Spectrum Measurements
Firmware/Software: V3.2.50
Manual operation: See "Frequency Range" on page 445
CONFigure:BLUetooth:MEAS<i>:MEValuation:BRATe:FILTer:BWIDth
<FilterBandWidth>
Selects the filter bandwidth for BR measurements.
Parameters:
<FilterBandWidth> NARRow | WIDE
NARRow: Narrow-band filter
WIDE: Wide-band filter
*RST: NARR
Example: See Configuring Measurements
Firmware/Software: V1.0.10.1
Manual operation: See "Filter" on page 445
CONFigure:BLUetooth:MEAS<i>:MEValuation:EDRate:FILTer:BWIDth
<FilterBandWidth>
Selects the filter bandwidth for EDR measurements. The filter is applied only to the
GFSK portion of the bursts.
Parameters:
<FilterBandWidth> NARRow | WIDE
NARRow: Narrow-band filter
WIDE: Wide-band filter
*RST: WIDE
Example: See Configuring Measurements
Firmware/Software: V1.0.10.1
V3.5.50: filter limited to GFSK portion
Manual operation: See "Filter" on page 445
CONFigure:BLUetooth:MEAS<i>:MEValuation:LENergy:LRANge:FILTer:BWIDth
<FilterBandWidth>
CONFigure:BLUetooth:MEAS<i>:MEValuation:LENergy:LE2M:FILTer:BWIDth
<FilterBandWidth>
CONFigure:BLUetooth:MEAS<i>:MEValuation:LENergy[:LE1M]:FILTer:BWIDth
<FilterBandWidth>
Selects the filter bandwidth.
Commands for uncoded LE 1M PHY (..:LE1M..), LE 2M PHY (..:LE2M..), and LE
coded PHY (..:LRANge..) are available.
Parameters:
<FilterBandWidth> NARRow | WIDE
NARRow: Narrow-band filter
WIDE: Wide-band filter
*RST: NARR
The following commands select the evaluated results and the displayed views.
CONFigure:BLUetooth:MEAS<i>:MEValuation:RESult:MSCalar..........................................523
CONFigure:BLUetooth:MEAS<i>:MEValuation:RESult:PSCalar.......................................... 523
CONFigure:BLUetooth:MEAS<i>:MEValuation:RESult:PENCoding..................................... 523
CONFigure:BLUetooth:MEAS<i>:MEValuation:RESult:PVTime...........................................523
CONFigure:BLUetooth:MEAS<i>:MEValuation:RESult:PVSLot........................................... 523
CONFigure:BLUetooth:MEAS<i>:MEValuation:RESult:DEVMagnitude................................ 523
CONFigure:BLUetooth:MEAS<i>:MEValuation:RESult:PDIFference.................................... 523
CONFigure:BLUetooth:MEAS<i>:MEValuation:RESult:IQABsolute......................................523
CONFigure:BLUetooth:MEAS<i>:MEValuation:RESult:IQDiff.............................................. 523
CONFigure:BLUetooth:MEAS<i>:MEValuation:RESult:IQERror.......................................... 523
CONFigure:BLUetooth:MEAS<i>:MEValuation:RESult:FDEViation......................................523
CONFigure:BLUetooth:MEAS<i>:MEValuation:RESult:FRANge..........................................523
CONFigure:BLUetooth:MEAS<i>:MEValuation:RESult:SOBW............................................ 523
CONFigure:BLUetooth:MEAS<i>:MEValuation:RESult:SACP............................................. 524
CONFigure:BLUetooth:MEAS<i>:MEValuation:RESult:SGACp........................................... 524
CONFigure:BLUetooth:MEAS<i>:MEValuation:RESult[:ALL]...............................................524
CONFigure:BLUetooth:MEAS<i>:MEValuation:RESult:MSCalar <Enable>
CONFigure:BLUetooth:MEAS<i>:MEValuation:RESult:PSCalar <Enable>
CONFigure:BLUetooth:MEAS<i>:MEValuation:RESult:PENCoding <Enable>
CONFigure:BLUetooth:MEAS<i>:MEValuation:RESult:PVTime <Enable>
CONFigure:BLUetooth:MEAS<i>:MEValuation:RESult:PVSLot <Enable>
CONFigure:BLUetooth:MEAS<i>:MEValuation:RESult:DEVMagnitude <Enable>
CONFigure:BLUetooth:MEAS<i>:MEValuation:RESult:PDIFference <Enable>
CONFigure:BLUetooth:MEAS<i>:MEValuation:RESult:IQABsolute <Enable>
CONFigure:BLUetooth:MEAS<i>:MEValuation:RESult:IQDiff <Enable>
CONFigure:BLUetooth:MEAS<i>:MEValuation:RESult:IQERror <Enable>
CONFigure:BLUetooth:MEAS<i>:MEValuation:RESult:FDEViation <Enable>
CONFigure:BLUetooth:MEAS<i>:MEValuation:RESult:FRANge <Enable>
CONFigure:BLUetooth:MEAS<i>:MEValuation:RESult:SOBW <Enable>
CONFigure:BLUetooth:MEAS<i>:MEValuation:RESult:SACP <Enable>
CONFigure:BLUetooth:MEAS<i>:MEValuation:RESult:SGACp <Enable>
Enables or disables the evaluation of results and shows or hides the views in the multi-
evaluation measurement. The last mnemonic denotes the view type: statistical modula-
tion results , statistical power results, statistical differential phase encoding results
(EDR in CSP), power vs. time results, power vs. slot results (LE with CTE), DEVM
(EDR), phase difference (EDR), IQ constellation absolute (EDR), IQ constellation dif-
ferential (EDR), IQ constellation error (EDR), frequency deviation (BR, LE), frequency
range results (BR), spectrum 20 dB bandwidth (BR), spectrum ACP (BR, LE), spec-
trum gated ACP (EDR). Use CONFigure:BLUetooth:MEAS<i>:MEValuation:
RESult[:ALL] to enable/disable all result types.
Tip: Use READ...? queries to retrieve results for disabled views.
Parameters:
<Enable> OFF | ON
ON: Evaluate results and show view
OFF: Do not evaluate results, hide view
*RST: ON (most measurement results)
Example: See Configuring Measurements
Firmware/Software: V1.0.10.50, V1.0.15.20: added commands for SOBW, SAPC,
V2.0.20: for SGAPC, V2.0.20: for FRANge, PENCoding,
V3.7.70: added command for PVSLot (power vs. slot diagram)
CONFigure:BLUetooth:MEAS<i>:MEValuation:RESult[:ALL] <DEVM>,
<PhaseDiff>, <ModScalars>, <IQAbsolute>, <IQDifferential>, <IQError>,
<FreqDev>, <PvT>, <PowerScalars>, <SpectrumOBW>, <SpectrumACP>,
<SpectrumGACP>[, <SpecFreqRange>, <PhaseEncoding>, <PowerVsSlot>]
Enables or disables the evaluation of results and shows or hides the views in the multi-
evaluation measurement. This command combines all other
CONFigure:BLUetooth:MEAS<i>:MEValuation:RESult... commands.
Tip: Use READ...? queries to retrieve results for disabled views.
Parameters:
<DEVM> OFF | ON
Differential error vector magnitude (only for EDR)
ON: Evaluate results and show the view
OFF: Do not evaluate results, hide the view (if applicable)
*RST: ON
<PhaseDiff> OFF | ON
Phase difference (only for EDR)
*RST: ON
<ModScalars> OFF | ON
Statistical modulation results
*RST: ON
<IQAbsolute> OFF | ON
IQ constellation absolute (only for EDR)
*RST: ON
<IQDifferential> OFF | ON
IQ constellation differential (only for EDR)
*RST: ON
<IQError> OFF | ON
IQ constellation error (only for EDR)
*RST: ON
<FreqDev> OFF | ON
Frequency deviation (only for BR and LE)
*RST: ON
<PvT> OFF | ON
Power vs. time
*RST: ON
<PowerScalars> OFF | ON
Statistical power results
*RST: ON
<SpectrumOBW> OFF | ON
Spectrum 20 dB bandwidth (only for BR)
*RST: ON
<SpectrumACP> OFF | ON
Spectrum ACP (only for BR and LE)
*RST: ON
<SpectrumGACP> OFF | ON
Spectrum gated ACP (only for EDR)
*RST: ON
<SpecFreqRange> OFF | ON
Spectrum frequency range (only for BR)
*RST: ON
<PhaseEncoding> OFF | ON
Statistical differential phase encoding results (only for EDR in
combined signal path)
<PowerVsSlot> OFF | ON
Power versus slot (only for LE with CE)
*RST: ON
Example: See Configuring Measurements
The following commands configure the list mode. For retrieving list mode results, see
Chapter 7.6.3.29, "List Mode Results (One Segment)", on page 647.
For a description of the list mode, see Chapter 7.2.5, "List Mode", on page 340.
The segment number <no> in the following commands refers to the complete range of
configured segments (1..48).
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIST.......................................................... 527
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIST:COUNt............................................... 527
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>:RESults........................527
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>:RESults:MSCalar.......... 528
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>:RESults:PSCalar...........528
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>:RESults:SACP.............. 528
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>:RESults:SGACp............528
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>:RESults:SOBW............. 528
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>:SCOunt........................ 529
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>:SCOunt:MSCalar.......... 529
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>:SCOunt:PSCalar........... 529
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>:SCOunt:SACP.............. 529
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>:SCOunt:SGACp............ 530
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>:SCOunt:SOBW............. 530
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIST:CMWS:CMODe................................... 530
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>[:SETup]:CSCHeme....... 531
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>[:SETup]:CMWS:
CONNector......................................................................................................... 531
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>[:SETup]........................532
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>[:SETup]:BTYPe.............534
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>[:SETup]:ENPower......... 534
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>[:SETup]:EXTended........ 535
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>[:SETup]:FILTer.............. 537
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>[:SETup]:FREQuency..... 537
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>[:SETup]:MOEXception... 538
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>[:SETup]:OSLots............ 538
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>[:SETup]:PATTern...........538
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>[:SETup]:PHY................ 539
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>[:SETup]:PLENgth.......... 539
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>[:SETup]:PTYPe.............540
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>[:SETup]:RTRigger......... 540
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>[:SETup]:SLENgth.......... 541
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIST <Enable>
Enables or disables the list mode.
Parameters:
<Enable> OFF | ON
OFF: disable list mode
ON: enable list mode
*RST: OFF
Example: See Specifying List Mode Settings
Firmware/Software: V3.2.50
Options: R&S CMW-KM012
Manual operation: See "List Mode" on page 443
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIST:COUNt <Segments>
Defines the number of segments in the entire measurement interval.
Parameters:
<Segments> numeric
Range: 1 to 48
*RST: 3
Example: See Specifying List Mode Settings
Firmware/Software: V3.2.50
Options: R&S CMW-KM012
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>:RESults
<EnableModScalar>, <EnablePowScalar>, <EnableSpecOBW>,
<EnableSpecACP>, <EnableSpecGACP>
Enables or disables the evaluation of the particular measurement type in the segment.
Suffix: .
<no> 1..48
Segment number
Parameters:
<EnableModScalar> OFF | ON
Enable/disable statistical modulation results
*RST: OFF
<EnablePowScalar> OFF | ON
Enable/disable statistical power results
*RST: OFF
<EnableSpecOBW> OFF | ON
Enable/disable the spectrum 20 dB bandwidth results (BR)
*RST: OFF
<EnableSpecACP> OFF | ON
Enable/disable the spectrum ACP results (BR, LE)
*RST: OFF
<EnableSpecGACP> OFF | ON
Enable/disable the spectrum gated ACP results (EDR)
*RST: OFF
Example: See Specifying List Mode Settings
Firmware/Software: V3.2.50
Options: R&S CMW-KM012
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>:RESults:
MSCalar <EnableModScalar>
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>:RESults:
PSCalar <EnablePowScalar>
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>:RESults:SACP
<EnableSpecACP>
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>:RESults:
SGACp <EnableSpecGACP>
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>:RESults:
SOBW <EnableSpecOBW>
Enables or disables the evaluation of results for the segment<no> in list mode. The last
mnemonic denotes the measurement type: statistical modulation results, statistical
power results, spectrum ACP (BR, LE), spectrum gated ACP (EDR), occupied band-
width (BR).
Suffix: .
<no> 1..48
Segment number
Parameters:
<Enable> OFF | ON
*RST: OFF
Example: See Specifying List Mode Settings
Firmware/Software: V3.2.50
Options: R&S CMW-KM012
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>:SCOunt
<ModStatCount>, <PowerStatCount>, <SpecOBWStatCnt>,
<SpecACPStatCnt>, <SpecGACPStatCnt>
Defines the statistic count for the particular measurement type in the segment.
Suffix: .
<no> 1..48
Segment number
Parameters:
<ModStatCount> numeric
Statistic count for the statistical modulation measurement
Range: 1 to 1000
*RST: 10
<PowerStatCount> numeric
Statistic count for the statistical power measurement
Range: 1 to 1000
*RST: 10
<SpecOBWStatCnt> numeric
Statistic count for the spectrum 20 dB bandwidth measurement
(BR)
Range: 1 to 1000
*RST: 10
<SpecACPStatCnt> numeric
Statistic count for the spectrum ACP measurement (BR, LE)
Range: 1 to 1000
*RST: 10
<SpecGACPStatCnt> numeric
Statistic count for the spectrum gated ACP measurement (EDR)
Range: 1 to 1000
*RST: 10
Example: See Specifying List Mode Settings
Firmware/Software: V3.2.50
Options: R&S CMW-KM012
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>:SCOunt:
MSCalar <ModStatCount>
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>:SCOunt:
PSCalar <PowerStatCount>
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>:SCOunt:SACP
<SpecACPStatCnt>
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>:SCOunt:
SGACp <SpecGACPStatCnt>
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>:SCOunt:
SOBW <SpecOBWStatCnt>
Defines the statistic count in the segment. The last mnemonic denotes the measure-
ment type: statistical modulation measurement, statistical power measurement, spec-
trum ACP measurement (BR, LE), spectrum gated ACP measurement (EDR), spec-
trum 20 dB bandwidth (occupied bandwidth) measurement (BR).
Suffix: .
<no> 1..48
Segment number
Parameters:
<SpecOBWStatCnt> numeric
Statistic count
Range: 1 to 1000
*RST: 10
Example: See Specifying List Mode Settings
Firmware/Software: V3.2.50
Options: R&S CMW-KM012
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIST:CMWS:CMODe
<ConnectorMode>
Specifies how the input connector is selected for Bluetooth list mode measurements
with the R&S CMWS.
Parameters:
<ConnectorMode> GLOBal | LIST
GLOBal: The same input connector is used for all segments. It
is selected in the same way as without list mode, for example via
ROUTe:BLUetooth:MEAS<i>:SCENario:SALone.
LIST: The input connector is configured individually for each
segment. See CONFigure:BLUetooth:MEAS<i>:
MEValuation:LIST:SEGMent<no>[:SETup]:CMWS:
CONNector.
*RST: GLOB
Example: See Specifying List Mode Settings
Firmware/Software: V3.2.50
Options: R&S CMW-KM012
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>[:SETup]:
CSCHeme <LeLrCoding>
Defines coding scheme S for LE coded PHY according to the core specification version
5.0 for Bluetooth wireless technology.
Suffix: .
<no> 1..48
Segment number
Parameters:
<LeLrCoding> S8 | S2
Coding S = 8 or S = 2
*RST: S2
Example: See Specifying List Mode Settings
Firmware/Software: V3.7.20
Options: R&S CMW-KM012
R&S CMW-KM721
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>[:SETup]:
CMWS:CONNector <CMWSConnector>
Selects the RF input connector for segment <no> for Bluetooth list mode measure-
ments with the R&S CMWS. This setting is only relevant for connector mode LIST,
see CONFigure:BLUetooth:MEAS<i>:MEValuation:LIST:CMWS:CMODe.
All segments of a list mode measurement must use connectors of the same bench.
For possible connector values, see Chapter 7.6.1.4, "Values for RF Path Selection",
on page 489.
Suffix: .
<no> 1..2000
Segment number
Parameters:
<CMWSConnector> Selects the input connector of the R&S CMWS
*RST: R11
Example: See Specifying List Mode Settings
Firmware/Software: V3.2.50
Options: R&S CMW-KM012
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>[:SETup]
<BurstType>, <PacketType>, <PatternType>, <PayloadLength>,
<NoOfOffSlots>, <SegmentLength>, <MeasOnException>, <Level>,
<Frequency>, <MeasFilter>[, <ReTrigger>]
Defines the segment length, the signal properties and the analyzer settings for a
selected segment. In general, this command must be sent for all segments to be mea-
sured.
Suffix: .
<no> 1..48
Segment number
Parameters:
<BurstType> BR | EDR | LE
Burst type expected in the segment
*RST: Basic Rate
<PacketType> DH1 | DH3 | DH5 | E21P | E23P | E25P | E31P | E33P | E35P |
RFPHytest | ADVertiser
Packet type expected in the segment
DH1, DH3, DH5: BR packet
E21P, E23P, E25P, E31P, E33P, E35P: 2-DH1, 2-DH3, 2-DH5, 3-
DH1, 3-DH3, 3-DH5 EDR packet
RFPHytest: LE test packet
ADVertiser: LE advertiser
*RST: DH1
<PatternType> ALL1 | P11 | OTHer | ALTernating | P44
Payload pattern type expected in the segment
ALL1: 11111111
P11: 10101010
OTHer: any pattern except P11, P44 and ALL1
ALTernating: the periodical change of the pattern P11, P44
P44: 11110000
*RST: OTH
<PayloadLength> numeric
Payload length expected in the segment
Range: 0 Byte(s) to 1021 Byte(s)
*RST: 27 Byte(s)
<NoOfOffSlots> numeric
Number of unused slots between any two occupied slots or slot
sequences expected in the segment
Range: 1 to 9
*RST: 1
<SegmentLength> numeric
Number of measured bursts in the segment. The sum of the
length of all active segments must not exceed 6700 timeslots (1
timeslot = 625 μs duration).
Range: 1 to 1000
*RST: 10
<MeasOnException> OFF | ON
Specifies whether the segment results that the R&S CMW identi-
fies as faulty or inaccurate are rejected.
ON: include the erroneous bursts
OFF: exclude the erroneous bursts
*RST: OFF
<Level> numeric
Expected nominal power in the segment. The range of the
expected nominal power can be calculated as follows:
Range (Expected Nominal Power) = Range (Input Power) +
External Attenuation - User Margin
The input power range is stated in the data sheet.
*RST: 0 dBm
Default unit: dBm
<Frequency> numeric
Center frequency for the segment
Range: 100E+6 Hz to 6E+9 Hz
*RST: 2.402E+9 Hz
Default unit: Hz
<MeasFilter> NARRow | WIDE
Filter bandwidth for the segment
NARRow: narrow-band filter
WIDE: wide-band filter
*RST: NARR
<ReTrigger> OFF | ON
Specifies whether a trigger event is required for the segment or
not. The setting is ignored for the first segment of a measure-
ment.
OFF: measure the segment without retrigger
ON: trigger event required
*RST: OFF
Example: See Specifying List Mode Settings
Firmware/Software: V3.2.50
V3.5.30: added <PatternType> ALTernating
V3.7.20: added <PacketType> ADVertiser,
<PatternType> ALL1
Options: R&S CMW-KM012
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>[:SETup]:
BTYPe <BurstType>
Specifies the burst type of the signal expected in the segment.
Suffix: .
<no> 1..48
Segment number
Parameters:
<BurstType> BR | EDR | LE
Burst type expected in the segment.
*RST: Basic Rate
Example: See Specifying List Mode Settings
Firmware/Software: V3.2.50
Options: R&S CMW-KM012
R&S CMW-KM610 for BR and EDR
R&S CMW-KM611 for LE
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>[:SETup]:
ENPower <Level>
Specifies the expected nominal power in the segment. The range of the expected nom-
inal power can be calculated as follows:
Range (Expected Nominal Power) = Range (Input Power) + External Attenuation -
User Margin
Suffix: .
<no> 1..48
Segment number
Parameters:
<Level> numeric
The input power range is stated in the data sheet.
*RST: 0 dBm
Default unit: dBm
Example: See Specifying List Mode Settings
Firmware/Software: V3.2.50
Options: R&S CMW-KM012
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>[:SETup]:
EXTended <BurstType>, <Phy>, <Coding>, <PacketType>, <PatternType>,
<PayloadLength>, <NoOfOffSlots>, <SegmentLength>, <MeasOnException>,
<Level>, <Frequency>, <MeasFilter>, <ReTrigger>
Defines the segment length, the signal properties including Bluetooth version 5 and the
analyzer settings for a selected segment. In general, this command must be sent for all
segments to be measured.
Suffix: .
<no> 1..48
Segment number
Parameters:
<1_BurstType> BR | EDR | LE
Burst type expected in the segment
*RST: Basic Rate
<2_PHY> LE1M | LE2M | LELR
Relevant only for LE. Set dummy value for other burst types.
LE1M: LE 1 Msymbol/s PHY
LE2M: LE 2 Msymbol/s PHY
LELR: Long range (LE coded PHY)
*RST: LE1M
<3_Coding> S8 | S2
Coding S = 8 or S = 2 relevant only for LELR PHY
Set dummy value for other physical layers.
<4_PacketType> DH1 | DH3 | DH5 | E21P | E23P | E25P | E31P | E33P | E35P |
RFPHytest | ADVertiser
Packet type expected in the segment
DH1, DH3, DH5: BR packet
E21P, E23P, E25P, E31P, E33P, E35P: 2-DH1, 2-DH3, 2-DH5, 3-
DH1, 3-DH3, 3-DH5 EDR packet
RFPHytest: LE test packet
ADVertiser: LE advertiser
*RST: DH1
<5_PatternType> ALL1 | P11 | OTHer | ALTernating | P44
Payload pattern type expected in the segment
ALL1: 11111111
P11: 10101010
OTHer: any pattern except P11, P44 and ALL1
ALTernating: the periodical change of the pattern P11, P44
P44: 11110000
*RST: OTH
<6_PayloadLength> numeric
Payload length expected in the segment
Range: 0 Byte(s) to 1021 Byte(s)
*RST: 27 Byte(s)
<7_NoOfOffSlots> numeric
Number of unused slots between any two occupied slots or slot
sequences expected in the segment
Range: 1 to 9
*RST: 1
<8_SegmentLength> numeric
Number of measured bursts in the segment. The sum of the
length of all active segments must not exceed 6700 timeslots (1
timeslot = 625 μs duration).
Range: 1 to 1000
*RST: 10
<10_MeasOnExcept> OFF | ON
Specifies whether the segment results that the R&S CMW identi-
fies as faulty or inaccurate are rejected.
ON: include the erroneous bursts
OFF: exclude the erroneous bursts
*RST: OFF
<11_Level> numeric
Expected nominal power in the segment. The range of the
expected nominal power can be calculated as follows:
Range (Expected Nominal Power) = Range (Input Power) +
External Attenuation - User Margin
The input power range is stated in the data sheet.
*RST: 0 dBm
<12_Frequency> numeric
Center frequency for the segment
Range: 100E+6 Hz to 6E+9 Hz
*RST: 2.402E+9 Hz
<13_MeasFilter> NARRow | WIDE
Filter bandwidth for the segment
NARRow: narrow-band filter
WIDE: wide-band filter
*RST: NARR
<14_ReTrigger> OFF | ON
Specifies whether a trigger event is required for the segment or
not. The setting is ignored for the first segment of a measure-
ment.
OFF: measure the segment without retrigger
ON: trigger event required
*RST: OFF
Example: See Specifying List Mode Settings
Firmware/Software: V3.7.20
Options: R&S CMW-KM012
R&S CMW-KM611 <BurstType> LE
R&S CMW-KM721 for <Phy> LE2M and LELR
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>[:SETup]:
FILTer <MeasFilter>
Specifies the measurement filter bandwidth for the segment.
Suffix: .
<no> 1..48
Segment number
Parameters:
<MeasFilter> NARRow | WIDE
NARRow: narrow-band filter
WIDE: wide-band filter
*RST: NARR
Example: See Specifying List Mode Settings
Firmware/Software: V3.2.50
Options: R&S CMW-KM012
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>[:SETup]:
FREQuency <Frequency>
Specifies the center frequency of the signal expected in the segment.
Suffix: .
<no> 1..48
Segment number
Parameters:
<Frequency> numeric
Range: 100E+6 Hz to 6E+9 Hz
*RST: 2.402E+9 Hz
Default unit: Hz
Example: See Specifying List Mode Settings
Firmware/Software: V3.2.50
Options: R&S CMW-KM012
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>[:SETup]:
MOEXception <MeasOnException>
Specifies whether the segment results that the R&S CMW identifies as faulty or inaccu-
rate are rejected.
Suffix: .
<no> 1..48
Segment number
Parameters:
<MeasOnException> OFF | ON
ON: include the erroneous bursts
OFF: exclude the erroneous bursts
*RST: OFF
Example: See Specifying List Mode Settings
Firmware/Software: V3.2.50
Options: R&S CMW-KM012
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>[:SETup]:
OSLots <NoOfOffSlots>
Specifies the number of unused slots between any two occupied slots or slot sequen-
ces expected in the segment.
Suffix: .
<no> 1..48
Segment number
Parameters:
<NoOfOffSlots> numeric
Range: 1 to 9
*RST: 1
Example: See Specifying List Mode Settings
Firmware/Software: V3.2.50
Options: R&S CMW-KM012
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>[:SETup]:
PATTern <PatternType>
Specifies the payload pattern type expected in the segment.
Suffix: .
<no> 1..48
Segment number
Parameters:
<PatternType> ALL1 | P11 | OTHer | ALTernating | P44
ALL1: 11111111
P11: 10101010
OTHer: any pattern except P11, P44, ALL1
ALTernating: the periodical change of the pattern P11 and P44
P44: 11110000
*RST: OTH
Example: See Specifying List Mode Settings
Firmware/Software: V3.2.50
V3.5.30: added pattern ALTernating
V3.7.20: added ALL1
Options: R&S CMW-KM012
R&S CMW100/CMW with MUA for <PatternType> ALL1
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>[:SETup]:PHY
<LePhyType>
Defines physical layer ( PHY) for segment according to the core specification version
5.0 for Bluetooth wireless technology.
Suffix: .
<no> 1..48
Segment number
Parameters:
<LePhyType> LE1M | LE2M | LELR
LE1M: LE 1 Msymbol/s uncoded PHY
LE2M: LE 2 Msymbol/s uncoded PHY
LELR: LE 1 Msymbol/s long range (LE coded PHY)
*RST: LE1M
Example: See Specifying List Mode Settings
Firmware/Software: V3.7.20
Options: R&S CMW-KM012
R&S CMW-KM611
R&S CMW-KM721 for LE2M and LELR
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>[:SETup]:
PLENgth <PayloadLength>
Specifies the payload length expected in the segment.
Suffix: .
<no> 1..48
Segment number
Parameters:
<PayloadLength> numeric
Range: 0 Byte(s) to 1021 Byte(s)
*RST: 27 Byte(s)
Example: See Specifying List Mode Settings
Firmware/Software: V3.2.50
Options: R&S CMW-KM012
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>[:SETup]:
PTYPe <PacketType>
Specifies the packet type expected in the segment.
Suffix: .
<no> 1..48
Segment number
Parameters:
<PacketType> DH1 | DH3 | DH5 | E21P | E23P | E25P | E31P | E33P | E35P |
RFPHytest | ADVertiser
DH1, DH3, DH5: BR packet
E21P, E23P, E25P, E31P, E33P, E35P: 2-DH1, 2-DH3, 2-DH5, 3-
DH1, 3-DH3, 3-DH5 EDR packet
RFPHytest: LE test packet
ADVertiser: LE advertiser
*RST: DH1
Example: See Specifying List Mode Settings
Firmware/Software: V3.2.50
V3.7.20: added <PacketType> ADVertiser
Options: R&S CMW-KM012
R&S CMW-KM611 for <PacketType> RFPHytest and ADVertiser
R&S CMW100/CMW with MUA for <PacketType> ADVertiser
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>[:SETup]:
RTRigger <ReTrigger>
Specifies whether a trigger event is required for the segment or not. The setting is
ignored for the first segment of a measurement.
Suffix: .
<no> 1..48
Segment number
Parameters:
<ReTrigger> OFF | ON
OFF: measure the segment without retrigger
ON: trigger event required
*RST: OFF
Example: See Specifying List Mode Settings
Firmware/Software: V3.2.50
Options: R&S CMW-KM012
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>[:SETup]:
SLENgth <SegmentLength>
Defines the number of measured bursts in the segment
Suffix: .
<no> 1..48
Segment number
Parameters:
<SegmentLength> numeric
The sum of the length of all active segments must not exceed
6700 timeslots (1 timeslot = 625 μs duration).
Range: 1 to 1000
*RST: 10
Example: See Specifying List Mode Settings
Firmware/Software: V3.2.50
Options: R&S CMW-KM012
TRIGger:BLUetooth:MEAS<i>:MEValuation:CATalog:SOURce?
Lists all trigger source values that can be set using TRIGger:BLUetooth:MEAS<i>:
MEValuation:SOURce.
Return values:
<Sourcelist> string
Comma-separated list of all supported values. Each value is rep-
resented as a string.
TRIGger:BLUetooth:MEAS<i>:MEValuation:SOURce <Source>
Selects the source of the trigger events. Some values are always available. They are
listed below. Depending on the installed options, additional values are available. You
can query a list of all supported values via TRIGger:...:CATalog:SOURce?.
Parameters:
<Source> string
'Power': power trigger (received RF power)
*RST: 'Power'
Example: See Basic Input Signal Properties: EDR Packets
Firmware/Software: V3.5.10
Manual operation: See "Trigger Source" on page 453
TRIGger:BLUetooth:MEAS<i>:MEValuation:THReshold <Power>
Defines the trigger threshold for the power trigger.
Parameters:
<Power> numeric
Range: -50 dB to 0 dB
Increment: 0.1 dB
*RST: -30 dB
Default unit: dB (full scale, i.e. relative to reference level minus
external attenuation)
Example: See Basic Input Signal Properties: EDR Packets
Firmware/Software: V1.0.10.1
Manual operation: See "Trigger Threshold" on page 454
TRIGger:BLUetooth:MEAS<i>:MEValuation:TOUT <TriggerTimeout>
Selects the maximum time that the measurement waits for a trigger event before it
stops in remote control mode or indicates a trigger timeout in manual operation mode.
Parameters:
<TriggerTimeout> numeric | ON | OFF
Range: 0.01 s to 167772.15 s
Increment: 0.001 s
*RST: 1s
Additional parameters: OFF | ON (disables timeout | enables
timeout using the previous/default values)
Example: See Basic Input Signal Properties: EDR Packets
Firmware/Software: V1.0.10.1
Manual operation: See "Trigger Timeout" on page 454
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:PVTime <PackTimeLower>,
<PackTimeUpper>, <PackTimeEnable>(4)
Sets and enables/disables a lower and upper timing error limit for PVT measurements.
Parameters:
<PackTimeLower> numeric
Range: -15 µs to 15 µs
*RST: -5 µs
<PackTimeUpper> numeric
Range: -15 µs to 15 µs
*RST: 5 µs
<PackTimeEnable> OFF | ON
*RST: OFF
Example: See Limit Settings
Firmware/Software: V3.2.30
Manual operation: See "Power Limits" on page 455
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:BRATe:PVTime
<NomPowLower>, <NomPowUpper>, <PeakPowUpper>,
<NomPowEnabled>(4), <PeakPowEnabled>(4)
Defines the power limits for BR: lower and upper average power limits, upper peak
power limit, limit check enabling.
Parameters:
<NomPowLower> numeric
Range: -99.99 dBm to 99.99 dBm
*RST: -6 dBm
<NomPowUpper> numeric
Range: -99.99 dBm to 99.99 dBm
*RST: 4 dBm
<PeakPowUpper> numeric
Range: -99.99 dBm to 99.99 dBm
*RST: 23 dBm
<NomPowEnabled> OFF | ON
Disables or enables the limit check for the average power, 4 val-
ues, corresponding to the current, average, maximum and mini-
mum results.
*RST: ON
<PeakPowEnabled> OFF | ON
Disables or enables the limit check for the peak power, 4 values,
corresponding to the current, average, maximum and minimum
results.
*RST: ON
Example: See Limit Settings
Firmware/Software: V1.0.10.1
Manual operation: See "Power Limits" on page 455
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:EDRate:PVTime
<DPSKmGFSKLow>, <DPSKmGFSKUpp>, <GuardPeriodLow>,
<GuardPeriodUpp>, <DPSKmGFSKEnab>(4), <GuardPeriodEnab>(4)
Defines the power limits for EDR: lower and upper limits for DPSK minus GFSK power
and for guard period, limit check enabling.
Parameters:
<DPSKmGFSKLow> numeric
Range: -99.99 dB to 99.99 dB
*RST: -4 dB
<DPSKmGFSKUpp> numeric
Range: -99.99 dB to 99.99 dB
*RST: 1 dB
<GuardPeriodLow> numeric
Range: -9.99 µs to 9.99 µs
*RST: 4.75 µs
<GuardPeriodUpp> numeric
Range: -9.99 µs to 9.99 µs
*RST: 5.25 µs
<DPSKmGFSKEnab> OFF | ON
Disables or enables the limit check for the DPSK minus GFSK
power, 4 values, corresponding to the current, average, maxi-
mum and minimum results.
*RST: ON
<GuardPeriodEnab> OFF | ON
Disables or enables the limit check for the guard period, 4 val-
ues, corresponding to the current, average, maximum and mini-
mum results.
*RST: ON
Example: See Limit Settings
Firmware/Software: V1.0.10.1
Manual operation: See "Power Limits" on page 455
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy:LRANge:PVTime
<AvgPowLower>, <AvgPowUpper>, <PkmAvgPowUpper>,
<AvgPowEnabled>(4), <PkmAvgPowEnable>(4)
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy:LE2M:PVTime
<AvgPowLower>, <AvgPowUpper>, <PkmAvgPowUpper>,
<AvgPowEnabled>(4), <PkmAvgPowEnable>(4)
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy[:LE1M]:PVTime
<AvgPowLower>, <AvgPowUpper>, <PkmAvgPowUpper>,
<AvgPowEnabled>(4), <PkmAvgPowEnable>(4)
Defines the power limits: lower and upper average power limits, upper limit for "peak
minus average power", limit check enabling.
Commands for uncoded LE 1M PHY (..:LE1M..), LE 2M PHY (..:LE2M..), and LE
coded PHY (..:LRANge..) are available.
Parameters:
<AvgPowLower> numeric
Range: -99.99 dBm to 99.99 dBm
*RST: -20 dBm
<AvgPowUpper> numeric
Range: -99.99 dBm to 99.99 dBm
*RST: 10 dBm
<PkmAvgPowUpper> numeric
Range: -99.99 dBm to 99.99 dBm
*RST: 3 dBm
<AvgPowEnabled> OFF | ON
Disables or enables the limit check for the average power, 4 val-
ues, corresponding to the current, average, maximum and mini-
mum results.
*RST: ON
<PkmAvgPowEnable>OFF | ON
Disables or enables the limit check for the "peak minus average
power", 4 values, corresponding to the current, average, maxi-
mum and minimum results.
*RST: ON
Example: See Limit Settings
Firmware/Software: V2.1.20
V3.5.70: added commands for LE2M and LRANge
Options: R&S CMW-KM611
Plus R&S CMW-KM721 for LE2M and LRANge
Manual operation: See "Power Limits" on page 455
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:CTE:LENergy:LE1M:
PDEViation <RefDev>, <TxDev>, <RefDevEnable>, <TxDevEnable>
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:CTE:LENergy:LE2M:
PDEViation <RefDev>, <TxDev>, <RefDevEnable>, <TxDevEnable>
Defines the upper CTE power limits and enables/disables the limit check.
Commands for uncoded LE 1M PHY (..:LE1M..) and LE 2M PHY (..:LE2M..) are
available.
Parameters:
<RefDev> numeric
Upper CTE power limit for reference antenna.
Range: 0.01 to 1
*RST: 0.25
<TxDev> numeric
Upper limit for power deviation in a slot.
Range: 0.01 to 1
*RST: 0.25
<RefDevEnable> OFF | ON
Enables/disables the CTE power limit check for reference
antenna.
*RST: ON
<TxDevEnable> OFF | ON
Enables/disables the limit check for power deviation in a slot.
*RST: ON
Example: See Performing LE with CTE Measurements
Firmware/Software: V3.7.70
Options: R&S CMW-KM722
Manual operation: See "Power Limits" on page 455
The following commands define limits for results which characterize the modulation
accuracy of BR packets.
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:BRATe:DELTa..................................... 547
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:BRATe:FACCuracy.............................. 548
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:BRATe:FDRift:APACkets...................... 548
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:BRATe:FDRift..................................... 549
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:BRATe:DAVerage................................ 550
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:BRATe:DMINimum.............................. 550
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:BRATe:DMAXimum............................. 550
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:BRATe:MRATio................................... 551
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:BRATe:DELTa
<DeltaF2P99p9>, <DeltaF2P99Enabl>
Defines the lower limit for the frequency deviation Δf2 that must be exceeded by 99.9%
of the measured bits.
Parameters:
<DeltaF2P99p9> numeric
Range: 100E+3 Hz to 200E+3 Hz
*RST: 115E+3 Hz
<DeltaF2P99Enabl> OFF | ON
*RST: ON
Example: See Limit Settings
Firmware/Software: V1.0.10.1
Manual operation: See "BR" on page 457
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:BRATe:FACCuracy
<FreqAccuracy>, <FreqAccEnabled>(3)
Defines the limit for the frequency accuracy.
Parameters:
<FreqAccuracy> numeric
Range: 0 Hz to 250E+3 Hz
*RST: 75E+3 Hz
<FreqAccEnabled> OFF | ON
Disable or enable limit check for current, average, and maximum
results (3 values)
*RST: ON
Example: See Limit Settings
Firmware/Software: V1.0.10.1
Manual operation: See "BR" on page 457
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:BRATe:FDRift:APACkets
<FreqDriftDH1>, <FreqDriftDH3>, <FreqDriftDH5>, <MaxDriftRate>,
<FreqDriftDH1Enb>(3), <FreqDriftDH3Enb>(3), <FreqDriftDH5Enb>(3),
<MaxDriftRateEnb>(3)
Defines the limits for the frequency drift and the maximum drift rate for BR. For each
packet type (DH1, DH3, DH5) a different frequency drift limit can be specified.
Parameters:
<FreqDriftDH1> numeric
Range: 0 Hz to 250E+3 Hz
*RST: 25E+3 Hz
<FreqDriftDH3> numeric
Range: 0 Hz to 250E+3 Hz
*RST: 40E+3 Hz
<FreqDriftDH5> numeric
Range: 0 Hz to 250E+3 Hz
*RST: 40E+3 Hz
<MaxDriftRate> numeric
Range: 0 Hz to 250E+3 Hz
*RST: 20E+3 Hz
<FreqDriftDH1Enb> OFF | ON
Disable or enable limit check for current, average, and maximum
results (3 values).
*RST: ON
<FreqDriftDH3Enb> OFF | ON
Disable or enable limit check for current, average, and maximum
results (3 values).
*RST: ON
<FreqDriftDH5Enb> OFF | ON
Disable or enable limit check for current, average, and maximum
results (3 values).
*RST: ON
<MaxDriftRateEnb> OFF | ON
Disable or enable limit check for current, average, and maximum
results (3 values).
*RST: ON
Example: See Limit Settings
Firmware/Software: V2.1.20
Manual operation: See "BR" on page 457
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:BRATe:FDRift
<FrequencyDrift>, <MaxDriftRate>, <FreqDriftEnable>(3),
<MaxDriftRateEnb>(3)
Defines the frequency drift limit for DH1 packets and the maximum drift rate limit for all
BR packets.
Since V2.1.20, this command is superseded by the command CONFigure:
BLUetooth:MEAS<i>:MEValuation:LIMit:BRATe:FDRift:APACkets that
allows to set different limits for different packet types.
Parameters:
<FrequencyDrift> numeric
Range: 0 Hz to 250E+3 Hz
*RST: 25E+3 Hz
<MaxDriftRate> numeric
Range: 0 Hz to 250E+3 Hz
*RST: 20E+3 Hz
<FreqDriftEnable> OFF | ON
Disable or enable limit check for current, average, and maximum
results (3 values).
*RST: ON
<MaxDriftRateEnb> OFF | ON
Disable or enable limit check for current, average, and maximum
results (3 values).
*RST: ON
Firmware/Software: V1.0.10.1
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:BRATe:DAVerage
<FreqDevF1Lower>, <FreqDevF1Upper>, <FreqDevF2Lower>,
<FreqDevF2Upper>, <FreqDevF1Enable>(4), <FreqDevF2Enable>(4)
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:BRATe:DMINimum
<FreqDevF1Lower>, <FreqDevF1Upper>, <FreqDevF2Lower>,
<FreqDevF2Upper>, <FreqDevF1Enable>(4), <FreqDevF2Enable>(4)
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:BRATe:DMAXimum
<FreqDevF1Lower>, <FreqDevF1Upper>, <FreqDevF2Lower>,
<FreqDevF2Upper>, <FreqDevF1Enable>(4), <FreqDevF2Enable>(4)
Defines the lower and upper frequency deviation limits for BR bursts. The mnemonics
DAVerage, DMAXimum, DMINimum distinguish average, maximum, and minimum fre-
quency deviations.
Parameters:
<FreqDevF1Lower> numeric
Range: 0 Hz to 500E+3 Hz
*RST: 140E+3 Hz
<FreqDevF1Upper> numeric
Range: 0 Hz to 500E+3 Hz
*RST: 175E+3 Hz
<FreqDevF2Lower> numeric
Range: 0 Hz to 500E+3 Hz
*RST: 115E+3 Hz
<FreqDevF2Upper> numeric
Range: 0 Hz to 500E+3 Hz
*RST: 175E+3 Hz
<FreqDevF1Enable> OFF | ON
Disable or enable limits for current, average, maximum, and
minimum results (4 values)
*RST: ON for all Δf1avg limits, OFF otherwise
<FreqDevF2Enable> OFF | ON
Disable or enable limits for current, average, maximum, and
minimum results (4 values)
*RST: OFF (all values)
Example: See Limit Settings
Firmware/Software: V1.0.10.1
Manual operation: See "BR" on page 457
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:BRATe:MRATio <ModRatio>,
<ModRatioEnabled>
Specifies the modulation ratio limit Δf2 avg / Δf1 avg for BR bursts.
Parameters:
<ModRatio> numeric
Range: 0 to 2
*RST: 0.8
<ModRatioEnabled> OFF | ON
Disable/enable limit checking
*RST: ON
Example: See Limit Settings
Firmware/Software: V2.1.20, V3.7.50: range extended
Manual operation: See "BR" on page 457
The following commands define limits for results which characterize the modulation
accuracy of EDR packets.
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:EDRate:FSTability............................... 551
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:EDRate:DQPSk:DEVM........................ 552
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:EDRate:DPSK:DEVM.......................... 553
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:EDRate:FSTability <Wi>,
<WiplusW0max>, <W0max>, <WiEnabled>(3), <WiW0maxEnabled>(3),
<W0maxEnabled>(3)
Defines and activates upper limits for the frequency stability.
Parameters:
<Wi> numeric
Limit for the initial center frequency error
Range: 0 Hz to 250E+3 Hz
*RST: 75E+3 Hz
<WiplusW0max> numeric
Limit for the overall uncompensated frequency error
Range: 0 Hz to 250E+3 Hz
*RST: 75E+3 Hz
<W0max> numeric
Limit for the maximum compensated frequency error in the
DPSK portion of the packet
Range: 0 Hz to 250E+3 Hz
*RST: 10E+3 Hz
<WiEnabled> OFF | ON
Enable limits for current, average, and maximum results (3 val-
ues)
*RST: ON
<WiW0maxEnabled> OFF | ON
Enable limits for current, average, and maximum results (3 val-
ues)
*RST: ON
<W0maxEnabled> OFF | ON
Enable limits for current, average, and maximum results (3 val-
ues)
*RST: ON
Example: See Limit Settings
Firmware/Software: V1.0.10.1
Manual operation: See "EDR" on page 458
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:EDRate:DQPSk:DEVM
<RMS>, <Peak>, <P99>, <RMSEnabled>(3), <PeakEnabled>(3),
<P99Enabled>
Defines and activates upper limits for the differential error vector magnitude for π/4
DQPSK modulated packets (2-DHx).
Parameters:
<RMS> numeric
Limit for RMS DEVM (π/4 DQPSK)
Range: 0 to 1
*RST: 0.2
<Peak> numeric
Limit for peak DEVM (π/4 DQPSK)
Range: 0 to 1
*RST: 0.35
<P99> numeric
Limit for 99% DEVM (π/4 DQPSK)
Range: 0 to 1
*RST: 0.3
<RMSEnabled> OFF | ON
Disable or enable limit check for current, average, and maximum
results (3 values)
*RST: ON
<PeakEnabled> OFF | ON
Disable or enable limit check for current, average, and maximum
results (3 values)
*RST: ON
<P99Enabled> OFF | ON
Disable or enable limit check for current result (1 value)
*RST: ON
Example: See Limit Settings
Firmware/Software: V1.0.10.1
Manual operation: See "EDR" on page 458
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:EDRate:DPSK:DEVM <RMS>,
<Peak>, <P99>, <RMSEnabled>(3), <PeakEnabled>(3), <P99Enabled>
Defines and activates upper limits for the differential error vector magnitude for 8DPSK
modulated packets (3-DHx).
Parameters:
<RMS> numeric
Limit for RMS DEVM (8DPSK)
Range: 0 to 1
*RST: 0.13
<Peak> numeric
Limit for peak DEVM (8DPSK)
Range: 0 to 1
*RST: 0.25
<P99> numeric
Limit for 99% DEVM (8DPSK)
Range: 0 to 1
*RST: 0.2
<RMSEnabled> OFF | ON
Disable or enable limit check for current, average, and maximum
results (3 values)
*RST: ON
<PeakEnabled> OFF | ON
Disable or enable limit check for current, average, and maximum
results (3 values)
*RST: ON
<P99Enabled> OFF | ON
Disable or enable limit check for current result (1 value)
*RST: ON
The following commands define limits for results which characterize the modulation
accuracy of LE packets.
Commands for uncoded LE 1M PHY (..:LE1M..), LE 2M PHY (..:LE2M..), and LE
coded PHY (..:LRANge..) are available.
Commands for LE (..:LIMit:LENergy..), and for LE with CTE
(..:LIMit:CTE:LENergy..) are available.
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy:DELTa.................................. 555
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy:LE2M:DELTa......................... 555
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy:LRANge:DELTa..................... 555
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy:LRANge:FACCuracy.............. 556
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy:LE2M:FACCuracy..................556
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy[:LE1M]:FACCuracy................ 556
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy:LRANge:FOFFset..................557
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy:LE2M:FOFFset......................557
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy[:LE1M]:FOFFset....................557
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:CTE:LENergy:LE1M:FOFFset.............. 557
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:CTE:LENergy:LE2M:FOFFset.............. 557
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy:LRANge:FDRift..................... 558
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy:LE2M:FDRift......................... 558
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy[:LE1M]:FDRift....................... 558
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:CTE:LENergy:LE1M:FDRift..................559
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:CTE:LENergy:LE2M:FDRift..................559
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy:DAVerage............................. 560
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy:DMINimum............................560
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy:DMAXimum.......................... 560
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy:LE2M:DAVerage....................560
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy:LE2M:DMINimum.................. 560
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy:LE2M:DMAXimum................. 560
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy:LRANge:DAVerage................ 561
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy:LRANge:DMINimum.............. 561
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy:LRANge:DMAXimum............. 561
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy:DAVerage:DF2S.................... 562
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy:DMINimum:DF2S.................. 562
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy:DMAXimum:DF2S................. 562
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy:LE2M:DAVerage:DF2S...........562
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy:LE2M:DMINimum:DF2S......... 562
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy:LE2M:DMAXimum:DF2S........ 562
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy:LE2M:MRATio....................... 563
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy[:LE1M]:MRATio..................... 563
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy:DELTa
<DeltaF2P99p9>, <DeltaF2P99Enabl>
Sets/gets the limit for the frequency deviation Δf2 for LE 1M PHY that must be excee-
ded by 99.9% of the measured samples.
Parameters:
<DeltaF2P99p9> numeric
Range: 150E+3 Hz to 250E+3 Hz
*RST: 185E+3 Hz
<DeltaF2P99Enabl> OFF | ON
Disable/enable limit checking
*RST: ON
Example: See Limit Settings
Firmware/Software: V2.1.20
Options: R&S CMW-KM611
Manual operation: See "LE" on page 459
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy:LE2M:DELTa
<DeltaF2P99p9>, <DeltaF2P99Enabl>
Sets/gets the limit for the frequency deviation Δf2 for LE 2M PHY that must be excee-
ded by 99.9% of the measured samples.
Parameters:
<DeltaF2P99p9> numeric
Range: 150E+3 Hz to 500E+3 Hz
*RST: 370E+3 Hz
<DeltaF2P99Enabl> OFF | ON
Disable/enable limit checking
*RST: ON
Firmware/Software: V3.5.70
Options: R&S CMW-KM721
Manual operation: See "LE" on page 459
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy:LRANge:DELTa
<DeltaF1P99p9>, <DeltaF1P99Enabl>
Sets/gets the limit for the frequency deviation Δf1 that must be exceeded by 99.9% of
the measured samples for LE coded PHY.
Parameters:
<DeltaF1P99p9> numeric
Range: 150E+3 Hz to 250E+3 Hz
*RST: 185E+3 Hz
<DeltaF1P99Enabl> OFF | ON
Disable/enable limit checking
*RST: ON
Firmware/Software: V3.5.70
Options: R&S CMW-KM721
Manual operation: See "LE" on page 459
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy:LRANge:
FACCuracy <FreqAccuracy>, <FreqAccEnabled>(3)
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy:LE2M:FACCuracy
<FreqAccuracy>, <FreqAccEnabled>(3)
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy[:LE1M]:FACCuracy
<FreqAccuracy>, <FreqAccEnabled>(3)
Defines the limit for the frequency accuracy.
Commands for uncoded LE 1M PHY (..:LE1M..), LE 2M PHY (..:LE2M..), and LE
coded PHY (..:LRANge..) are available.
Parameters:
<FreqAccuracy> numeric
Range: 0 Hz to 250E+3 Hz
*RST: 150E+3 Hz
<FreqAccEnabled> OFF | ON
Disable or enable limit check for current, average, and maximum
results (3 values)
*RST: ON
Example: See Limit Settings
Firmware/Software: V3.2.30
V3.5.70: added commands for LE2M and LRANge
Options: R&S CMW-KM611
Plus R&S CMW-KM721 for LE2M and LRANge
Manual operation: See "LE" on page 459
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy:LRANge:FOFFset
<FreqOffset>, <FreqOffsetEnab>(3)
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy:LE2M:FOFFset
<FreqOffset>, <FreqOffsetEnab>(3)
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy[:LE1M]:FOFFset
<FreqOffset>, <FreqOffsetEnab>(3)
Sets/gets the frequency offset limit.
Commands for uncoded LE 1M PHY (..:LE1M..), LE 2M PHY (..:LE2M..), and LE
coded PHY (..:LRANge..) are available.
Parameters:
<FreqOffset> numeric
Range: 0 Hz to 250E+3 Hz
*RST: 150E+3 Hz
<FreqOffsetEnab> OFF | ON
Disable or enable limit checking for current, average, and maxi-
mum results (3 values)
*RST: ON
Example: See Limit Settings
Firmware/Software: V2.1.20, V3.5.70: added commands for LE2M and LRANge
Options: R&S CMW-KM611
Plus R&S CMW-KM721 for LE2M and LRANge
Manual operation: See "LE" on page 459
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:CTE:LENergy:LE1M:FOFFset
<FreqOffset>, <FreqOffsetEnab>(3)
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:CTE:LENergy:LE2M:FOFFset
<FreqOffset>, <FreqOffsetEnab>(3)
Sets/gets the frequency offset limit for the CTE portion.
Commands for uncoded LE 1M PHY (..:LE1M..) and LE 2M PHY (..:LE2M..) are
available.
Parameters:
<FreqOffset> numeric
Range: 0 Hz to 500E+3 Hz
*RST: 150E+3 Hz
<FreqOffsetEnab> OFF | ON
Disable or enable limit checking for current, average, and maxi-
mum results (3 values)
*RST: ON
Example: See Performing LE with CTE Measurements
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy:LRANge:FDRift
<FrequencyDrift>, <MaxDriftRate>, <InitlFreqDrift>, <FreqDriftEnable>(3),
<MaxDriftRateEnb>(3), <InitFreqDriftEn>(3)
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy:LE2M:FDRift
<FrequencyDrift>, <MaxDriftRate>, <InitlFreqDrift>, <FreqDriftEnable>(3),
<MaxDriftRateEnb>(3), <InitFreqDriftEn>(3)
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy[:LE1M]:FDRift
<FrequencyDrift>, <MaxDriftRate>, <InitlFreqDrift>, <FreqDriftEnable>(3),
<MaxDriftRateEnb>(3), <InitFreqDriftEn>(3)
Sets and enables limits for frequency drift, maximum drift rate and initial frequency
drift.
Commands for uncoded LE 1M PHY (..:LE1M..), LE 2M PHY (..:LE2M..), and LE
coded PHY (..:LRANge..) are available.
Parameters:
<FrequencyDrift> numeric
Range: 0 Hz to 250E+3 Hz
*RST: 50E+3 Hz
<MaxDriftRate> numeric
Range: 0 Hz to 250E+3 Hz
*RST: 20E+3 Hz
<InitlFreqDrift> numeric
Range: 0 Hz to 250E+3 Hz
*RST: 23E+3 Hz
<FreqDriftEnable> OFF | ON
Disable or enable limit checking for current, average, and maxi-
mum results (3 values).
*RST: ON
<MaxDriftRateEnb> OFF | ON
Disable or enable limit checking for current, average, and maxi-
mum results (3 values).
*RST: ON
<InitFreqDriftEn> OFF | ON
Disable or enable limit checking for current, average, and maxi-
mum results (3 values).
*RST: ON
Example: See Limit Settings
Firmware/Software: V2.1.20
V3.5.60: changed reset value of <InitlFreqDrift>, V3.5.70: added
commands for LE2M, V3.7.20: added commands for LRANge
Options: R&S CMW-KM611
Plus R&S CMW-KM721 for LE2M and LELR
Manual operation: See "LE" on page 459
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:CTE:LENergy:LE1M:FDRift
<FrequencyDrift>, <MaxDriftRate>, <InitlFreqDrift>, <FreqDriftEnable>(3),
<MaxDriftRateEnb>(3), <InitFreqDriftEn>(3)
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:CTE:LENergy:LE2M:FDRift
<FrequencyDrift>, <MaxDriftRate>, <InitlFreqDrift>, <FreqDriftEnable>(3),
<MaxDriftRateEnb>(3), <InitFreqDriftEn>(3)
Sets and enables limits for frequency drift, maximum drift rate and initial frequency drift
for the CTE portion.
Commands for uncoded LE 1M PHY (..:LE1M..) and LE 2M PHY (..:LE2M..) are
available.
Parameters:
<FrequencyDrift> numeric
Range: 0 Hz to 500E+3 Hz
*RST: 50E+3 Hz
<MaxDriftRate> numeric
Range: 0 Hz to 500E+3 Hz
*RST: 19.2E+3 Hz
<InitlFreqDrift> numeric
Range: 0 Hz to 500E+3 Hz
*RST: 13.6E+3 Hz
<FreqDriftEnable> OFF | ON
Disable or enable limit checking for current, average, and maxi-
mum results (3 values).
*RST: ON
<MaxDriftRateEnb> OFF | ON
Disable or enable limit checking for current, average, and maxi-
mum results (3 values).
*RST: ON
<InitFreqDriftEn> OFF | ON
Disable or enable limit checking for current, average, and maxi-
mum results (3 values).
*RST: ON
Example: See Performing LE with CTE Measurements
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy:DAVerage
<FreqDevF1Lower>, <FreqDevF1Upper>, <FreqDevF1Enable>(4)
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy:DMINimum
<FreqDevF1Lower>, <FreqDevF1Upper>, <FreqDevF1Enable>(4)
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy:DMAXimum
<FreqDevF1Lower>, <FreqDevF1Upper>, <FreqDevF1Enable>(4)
Defines the lower and upper Δf1 frequency deviation limits for LE 1M PHY. The mne-
monics DAVerage, DMINimum, DMAXimum distinguish average, minimum and maxi-
mum frequency deviations.
Parameters:
<FreqDevF1Lower> numeric
Range: 0 Hz to 500E+3 Hz
*RST: 225E+3 Hz
<FreqDevF1Upper> numeric
Range: 0 Hz to 500E+3 Hz
*RST: 275E+3 Hz
<FreqDevF1Enable> OFF | ON
Disable or enable limits for current, average, maximum, and
minimum results (4 values)
*RST: ON for all Δf1avg limits, OFF otherwise
Example: See Limit Settings
Firmware/Software: V2.1.20
Options: R&S CMW-KM611
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy:LE2M:DAVerage
<FreqDevF1Lower>, <FreqDevF1Upper>, <FreqDevF1Enable>(4)
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy:LE2M:DMINimum
<FreqDevF1Lower>, <FreqDevF1Upper>, <FreqDevF1Enable>(4)
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy:LE2M:DMAXimum
<FreqDevF1Lower>, <FreqDevF1Upper>, <FreqDevF1Enable>(4)
Defines the lower and upper Δf1 frequency deviation limits for LE 2M PHY. The mne-
monics DAVerage, DMINimum, DMAXimum distinguish average, minimum and maxi-
mum frequency deviations.
Parameters:
<FreqDevF1Lower> numeric
Range: 0 Hz to 900E+3 Hz
*RST: 450E+3 Hz
<FreqDevF1Upper> numeric
Range: 0 Hz to 900E+3 Hz
*RST: 550E+3 Hz
<FreqDevF1Enable> OFF | ON
Disable or enable limits for current, average, maximum, and
minimum results (4 values)
*RST: OFF, for all Δf1avg limits: ON
Firmware/Software: V3.5.70
Options: R&S CMW-KM721
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy:LRANge:DAVerage
<FreqDevF1Lower>, <FreqDevF1Upper>, <FreqDevF1Enable>(4)
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy:LRANge:
DMINimum <FreqDevF1Lower>, <FreqDevF1Upper>, <FreqDevF1Enable>(4)
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy:LRANge:
DMAXimum <FreqDevF1Lower>, <FreqDevF1Upper>, <FreqDevF1Enable>(4)
Defines the lower and upper Δf1 frequency deviation limits for LE coded PHY. The
mnemonics DAVerage, DMINimum, DMAXimum distinguish average, minimum and
maximum frequency deviations.
Parameters:
<FreqDevF1Lower> numeric
Range: 0 Hz to 500E+3 Hz
*RST: 225E+3 Hz
<FreqDevF1Upper> numeric
Range: 0 Hz to 500E+3 Hz
*RST: 275E+3 Hz
<FreqDevF1Enable> OFF | ON
Disable or enable limits for current, average, maximum, and
minimum results (4 values)
*RST: OFF (all values)
Firmware/Software: V3.5.70
Options: R&S CMW-KM721
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy:DAVerage:DF2S
<FreqDevF2Lower>, <FreqDevF2Upper>, <FreqDevF2Enable>(4)
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy:DMINimum:DF2S
<FreqDevF2Lower>, <FreqDevF2Upper>, <FreqDevF2Enable>(4)
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy:DMAXimum:DF2S
<FreqDevF2Lower>, <FreqDevF2Upper>, <FreqDevF2Enable>(4)
Defines the lower and upper Δf2 frequency deviation limits for uncoded LE 1M PHY.
The mnemonics DAVerage, DMINimum, DMAXimum distinguish average, minimum and
maximum frequency deviations.
Parameters:
<FreqDevF2Lower> numeric
Range: 0 Hz to 500E+3 Hz
*RST: 115E+3 Hz
<FreqDevF2Upper> numeric
Range: 0 Hz to 500E+3 Hz
*RST: 175E+3 Hz
<FreqDevF2Enable> OFF | ON
Disable or enable limits for current, average, maximum, and
minimum results (4 values)
*RST: OFF
Example: See Limit Settings
Firmware/Software: V3.7.80
Options: R&S CMW-KM611
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy:LE2M:DAVerage:
DF2S <FreqDevF2Lower>, <FreqDevF2Upper>, <FreqDevF2Enable>(4)
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy:LE2M:DMINimum:
DF2S <FreqDevF2Lower>, <FreqDevF2Upper>, <FreqDevF2Enable>(4)
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy:LE2M:DMAXimum:
DF2S <FreqDevF2Lower>, <FreqDevF2Upper>, <FreqDevF2Enable>(4)
Defines the lower and upper Δf2 frequency deviation limits for LE 2M PHY. The mne-
monics DAVerage, DMINimum, DMAXimum distinguish average, minimum and maxi-
mum frequency deviations.
Parameters:
<FreqDevF2Lower> numeric
Range: 0 Hz to 900E+3 Hz
*RST: 115E+3 Hz
<FreqDevF2Upper> numeric
Range: 0 Hz to 900E+3 Hz
*RST: 175E+3 Hz
<FreqDevF2Enable> OFF | ON
Disable or enable limits for current, average, maximum, and
minimum results (4 values)
*RST: OFF
Example: See Limit Settings
Firmware/Software: V3.7.80, V3.7.81: range of <FreqDevF2Lower> and <Freq-
DevF2Upper> extended
Options: R&S CMW-KM721
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy:LE2M:MRATio
<ModRatio>, <ModRatioEnabled>
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy[:LE1M]:MRATio
<ModRatio>, <ModRatioEnabled>
Sets or queries the modulation ratio limit Δf2 avg / Δf1 avg for LE 1M PHY
(...:LE1M...) and LE 2M PHY (...:LE2M...).
Parameters:
<ModRatio> numeric
Range: 0 to 2
*RST: 0.8
<ModRatioEnabled> OFF | ON
Disable/enable limit checking
*RST: ON
Example: See Limit Settings
Firmware/Software: V2.1.20, V3.5.70: added commands for LE2M, V3.7.50: range
extended
Options: R&S CMW-KM611
Plus R&S CMW-KM721 for LE2M
Manual operation: See "LE" on page 459
The following commands define limits for the spectrum measurement results.
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:SOBW............................................... 564
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:FRANge.............................................564
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:SACP................................................ 565
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy:LRANge:SACP......................565
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy:LE2M:SACP..........................565
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy[:LE1M]:SACP........................565
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:SGACp.............................................. 566
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:SOBW <LimitThreshold>,
<EqHighPeakUpper>, <LowPeakUpper>, <EqHighPeakEnab>,
<LowPeakEnab>
Defines and enables the limits for the 20 dB bandwidth measurement (BR only).
Parameters:
<LimitThreshold> numeric
Threshold value for "high" vs "low" peak emission bursts
Range: -80 dBm to 40 dBm
*RST: 0 dBm
<EqHighPeakUpper> numeric
20 dB bandwidth limit for "high" peak emission bursts
(≥LimitThreshold)
Range: 1E-3 MHz to 4 MHz
*RST: 1 MHz
<LowPeakUpper> numeric
20 dB bandwidth limit for "low" peak emission bursts (<
LimitThreshold)
Range: 1E-3 MHz to 4 MHz
*RST: 1.5 MHz
<EqHighPeakEnab> OFF | ON
Disable or enable the 20 dB bandwidth limit for "high" peak
emission bursts
*RST: ON
<LowPeakEnab> OFF | ON
Disable or enable the 20 dB bandwidth limit for "low" peak emis-
sion bursts
*RST: ON
Example: See Limit Settings
Firmware/Software: V1.0.15.20
V2.1.20: removed <BandwidthUpper>, <BandwidthEnab>,
added <LimitThreshold>, <EqHighPeakUpper>,
<LowPeakUpper>, <EqHighPeakEnab>, <LowPeakEnab>
Manual operation: See "20 dB Bandwidth (BR)" on page 461
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:FRANge <FLx_Lower>,
<FHx_Upper>, <FLx_LowerEnable>, <FHx_UpperEnable>
Defines the limit for the frequency range measurement.
Parameters:
<FLx_Lower> numeric
Lower limit for the lowest frequency fL relative to center fre-
quency
Range: -5 MHz to 0 MHz
*RST: -2 MHz
Default unit: Hz
<FHx_Upper> numeric
Upper limit for the highest frequency fH relative to center fre-
quency
Range: 0 MHz to 5 MHz
*RST: 3.5 MHz
Default unit: Hz
<FLx_LowerEnable> OFF | ON
Disable or enable limit check for the lowest frequency fL
*RST: ON
<FHx_UpperEnable> OFF | ON
Disable or enable limit check for the highest frequency fH
*RST: ON
Example: See Limit Settings
Firmware/Software: V3.2.50
Manual operation: See "Frequency Range (BR)" on page 462
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:SACP <PTxLimit>,
<ExcPTxLimit>, <NoOfExLimit>, <PTxEnable>, <NoOfExcEnable>
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy:LRANge:SACP
<PTxLimit>, <ExcPTxLimit>, <NoOfExLimit>, <PTxEnable>, <NoOfExcEnable>
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy:LE2M:SACP
<PTxLimit>, <ExcPTxLimit>, <NoOfExLimit>, <PTxEnable>, <NoOfExcEnable>
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy[:LE1M]:SACP
<PTxLimit>, <ExcPTxLimit>, <NoOfExLimit>, <PTxEnable>, <NoOfExcEnable>
These commands define and enable the "Spectrum ACP" limits for BR
(...:LIMit:SACP), LE 1M PHY ( ...:LE1M...), LE 2M PHY (...:LE2M...), and
LE coded PHY (...:LRANge...), respectively.
Parameters:
<PTxLimit> numeric
Power limit for 1 MHz channels fTX± 2 MHz
Range: -80 dBm to -10 dBm
*RST: -20 dBm
<ExcPTxLimit> numeric
Power limit for 1 MHz channels fTX±3 MHz, fTX±4 MHz, ...
Range: -80 dBm to -10 dBm
*RST: -40 dBm for BR, -30 dBm for LE
<NoOfExLimit> numeric
Maximum number of tolerable exceptions, i.e. 1 MHz channels
fTX±3 MHz, fTX±4 MHz, ... whose power is above ExcPTxLimit,
but below PTxLimit
Range: 0 to 16
*RST: 3
<PTxEnable> OFF | ON
Disables | enables the PTxLimit limit for 1 MHz channels fTX
± 2 MHz
*RST: ON
<NoOfExcEnable> OFF | ON
Disables | enables the ExcPTxLimit limit for 1 MHz channels
fTX±3 MHz, fTX±4 MHz, ... with NoOfExLimit tolerable excep-
tions (per statistic cycle).
*RST: ON
Example: See Limit Settings
Firmware/Software: V1.0.15.20
V2.1.20: added command for LE
V3.5.70: added commands for LE2M and LRANge
Options: R&S CMW-KM610 for BR and EDR
R&S CMW-KM611 for LE
Plus R&S CMW-KM721 for LE2M and LRANge
Manual operation: See "ACP (BR, LE)" on page 462
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:SGACp <PTxLimit>,
<ExcPTxLimit>, <NoOfExLimit>, <Ptxm26N1relLim>, <Ptxm26P1relLim>,
<PTxEnable>, <NoOfExcEnable>, <Ptxm26N1relEnab>, <Ptxm26P1relEnab>
Defines and enables the upper limits for the "Spectrum Gated ACP" measurement for
EDR packets: "PTx", "Exceptions PTx", "No. of Exceptions", PTx–26 dB–1 (rel), PTx–26 dB
+1 (rel), and limit check enabling.
Parameters:
<PTxLimit> numeric
Range: -80 dBm to -10 dBm
*RST: -20 dBm
<ExcPTxLimit> numeric
Range: -80 dBm to -10 dBm
*RST: -40 dBm
<NoOfExLimit> numeric
Range: 0 to 16
*RST: 3
<Ptxm26N1relLim> numeric
Range: -80 dB to 0 dB
*RST: -26 dB
<Ptxm26P1relLim> numeric
Range: -80 dB to 0 dB
*RST: -26 dB
<PTxEnable> OFF | ON
*RST: ON
<NoOfExcEnable> OFF | ON
*RST: ON
<Ptxm26N1relEnab> OFF | ON
*RST: ON
<Ptxm26P1relEnab> OFF | ON
*RST: ON
Example: See Limit Settings
Firmware/Software: V2.0.20
Manual operation: See "Gated ACP (EDR)" on page 463
The following command defines limits for the differential phase encoding measurement
results.
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:EDRate:PENCoding
<PhaseEncoding>, <PhaseEncodEnab>
Defines the limit for the phase encoding measurement.
Parameters:
<PhaseEncoding> numeric
Lower limit as percentage of received fault free packets.
Range: 0 to 1
*RST: .99
<PhaseEncodEnab> OFF | ON
Disable or enable limit check for the phase encoding.
*RST: ON
Example: See Limit Settings
Firmware/Software: V3.2.50
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:EDRate:PENCoding:
SSEQuence <SyncBitErrors>, <TrailerBitErrs>, <SyncBitEnable>,
<TrailerBitEnab>
Defines the limit for the differential phase encoding measurement in combined signal
path.
Parameters:
<SyncBitErrors> numeric
Upper limit for sync bit errors.
Range: 0 to 1000
*RST: 0
<TrailerBitErrs> numeric
Upper limit for trailer bit errors.
Range: 0 to 1000
*RST: 1
<SyncBitEnable> OFF | ON
Disable or enable the limit check.
*RST: ON
<TrailerBitEnab> OFF | ON
Disable or enable the limit check.
*RST: ON
Example: See Limit Settings
Firmware/Software: V3.7.81
Manual operation: See "Sync/ Trailer Bit Errors" on page 464
The following commands query the signal characteristics in automatic detection mode.
The manual settings are ignored.
FETCh:BLUetooth:MEAS<i>:ISIGnal:ADETected:AADDress:LENergy[:LE1M]?.................... 569
FETCh:BLUetooth:MEAS<i>:ISIGnal:ADETected:PTYPe:BRATe?.......................................569
FETCh:BLUetooth:MEAS<i>:ISIGnal:ADETected:PTYPe:EDRate?..................................... 570
FETCh:BLUetooth:MEAS<i>:ISIGnal:ADETected:PTYPe:LENergy[:LE1M]?.........................570
FETCh:BLUetooth:MEAS<i>:ISIGnal:ADETected:PTYPe:LENergy:LE2M?...........................570
FETCh:BLUetooth:MEAS<i>:ISIGnal:ADETected:PTYPe:LENergy:LRANge?.......................571
FETCh:BLUetooth:MEAS<i>:ISIGnal:ADETected:PATTern[:BRATe]?................................... 571
FETCh:BLUetooth:MEAS<i>:ISIGnal:ADETected:PATTern:LENergy:LE2M?.........................572
FETCh:BLUetooth:MEAS<i>:ISIGnal:ADETected:PATTern:LENergy[:LE1M]?....................... 572
FETCh:BLUetooth:MEAS<i>:ISIGnal:ADETected:PATTern:LENergy:LRANge?..................... 573
FETCh:BLUetooth:MEAS<i>:ISIGnal:ADETected:CODing:LENergy:LRANge?......................573
FETCh:BLUetooth:MEAS<i>:ISIGnal:ADETected:PLENgth:BRATe?.................................... 573
FETCh:BLUetooth:MEAS<i>:ISIGnal:ADETected:PLENgth:EDRate?.................................. 574
FETCh:BLUetooth:MEAS<i>:ISIGnal:ADETected:PLENgth:LENergy:LRANge?.................... 574
FETCh:BLUetooth:MEAS<i>:ISIGnal:ADETected:PLENgth:LENergy:LE2M?........................574
FETCh:BLUetooth:MEAS<i>:ISIGnal:ADETected:PLENgth:LENergy[:LE1M]?...................... 574
FETCh:BLUetooth:MEAS<i>:ISIGnal:ADETected:CTE:LENergy:LE1M:TYPE?..................... 575
FETCh:BLUetooth:MEAS<i>:ISIGnal:ADETected:CTE:LENergy:LE2M:TYPE?..................... 575
FETCh:BLUetooth:MEAS<i>:ISIGnal:ADETected:CTE:LENergy:LE1M:UNITs?.....................575
FETCh:BLUetooth:MEAS<i>:ISIGnal:ADETected:CTE:LENergy:LE2M:UNITs?.....................575
FETCh:BLUetooth:MEAS<i>:ISIGnal:ADETected:NOSLots:BRATe?....................................576
FETCh:BLUetooth:MEAS<i>:ISIGnal:ADETected:NOSLots:EDRate?.................................. 576
FETCh:BLUetooth:MEAS<i>:ISIGnal:ADETected:AADDress:LENergy[:LE1M]?
Returns the detected access address of advertiser for LE 1M PHY. A result is available
after the R&S CMW has auto-detected a packet (CONFigure:BLUetooth:MEAS<i>:
ISIGnal:DMODe AUTO).
Return values:
<Reliability> decimal
Reliability Indicator
<AdvAddress> string
Example: See Automatic Detection Mode
Usage: Query only
Firmware/Software: V3.5.70
Options: R&S CMW-KM611
Manual operation: See "Access Address (LE)" on page 437
FETCh:BLUetooth:MEAS<i>:ISIGnal:ADETected:PTYPe:BRATe?
Returns the detected BR packet type. A result is available after the R&S CMW has
auto-detected a packet (CONFigure:BLUetooth:MEAS<i>:ISIGnal:DMODe
AUTO).
Return values:
<Reliability> decimal
Reliability Indicator
<Packet Type> DH1 | DH3 | DH5
Example: See Automatic Detection Mode
Usage: Query only
Firmware/Software: V2.0.20
Manual operation: See "Packet Type" on page 436
FETCh:BLUetooth:MEAS<i>:ISIGnal:ADETected:PTYPe:EDRate?
Returns the detected EDR packet type. A result is available after the R&S CMW has
auto-detected a packet (CONFigure:BLUetooth:MEAS<i>:ISIGnal:DMODe
AUTO).
Return values:
<Reliability> decimal
Reliability Indicator
<Packet Type> E21P | E23P | E25P | E31P | E33P | E35P
2-DH1, 2-DH3, 2-DH5, 3-DH1, 3-DH3, or 3-DH5 packets
Example: See Automatic Detection Mode
Usage: Query only
Firmware/Software: V2.0.20
Manual operation: See "Packet Type" on page 436
FETCh:BLUetooth:MEAS<i>:ISIGnal:ADETected:PTYPe:LENergy[:LE1M]?
Returns the detected packet type for LE 1M PHY (uncoded).
A result is available after the R&S CMW has auto-detected a packet (CONFigure:
BLUetooth:MEAS<i>:ISIGnal:DMODe AUTO).
Return values:
<Reliability> decimal
Reliability Indicator
<Packet Type> RFPHytest | ADVertiser | RFCTe
RFPHytest: LE test packet (direct test mode)
ADVertiser: air interface packet with advertising channel PDU
RFCTe: LE test packet with CTE
Example: See Automatic Detection Mode
Usage: Query only
Firmware/Software: V2.1.20, V3.5.60: added ADVertiser,
V3.7.70: added RFCTe
Options: R&S CMW-KM611
R&S CMW-KM722 for RFCTe
Manual operation: See "Packet Type" on page 436
FETCh:BLUetooth:MEAS<i>:ISIGnal:ADETected:PTYPe:LENergy:LE2M?
Returns the detected packet type for LE 2M PHY.
A result is available after the R&S CMW has auto-detected a packet (CONFigure:
BLUetooth:MEAS<i>:ISIGnal:DMODe AUTO).
Return values:
<Reliability> decimal
Reliability Indicator
<Packet Type> RFPHytest | ADVertiser | RFCTe
RFPHytest: LE test packet (direct test mode)
ADVertiser: air interface packet with advertising channel PDU
RFCTe: LE test packet with CTE
Example: See Performing LE with CTE Measurements
Usage: Query only
Firmware/Software: V3.5.70, V3.7.70: added RFCT, V3.7.90: added ADVertiser
Options: R&S CMW-KM721
R&S CMW-KM722 for RFCTe
Manual operation: See "Packet Type" on page 436
FETCh:BLUetooth:MEAS<i>:ISIGnal:ADETected:PTYPe:LENergy:LRANge?
Returns the detected packet type for LE coded PHY.
A result is available after the R&S CMW has auto-detected a packet (CONFigure:
BLUetooth:MEAS<i>:ISIGnal:DMODe AUTO).
Return values:
<Reliability> decimal
Reliability Indicator
<Packet Type> RFPHytest | ADVertiser
RFPHytest: LE test packet (direct test mode)
ADVertiser: air interface packet with advertising channel PDU
Usage: Query only
Firmware/Software: V3.5.70, V3.7.90: added ADVertiser
Options: R&S CMW-KM721
Manual operation: See "Packet Type" on page 436
FETCh:BLUetooth:MEAS<i>:ISIGnal:ADETected:PATTern[:BRATe]?
Returns the detected payload pattern type. A result is available after the R&S CMW
has auto-detected a packet (CONFigure:BLUetooth:MEAS<i>:ISIGnal:DMODe
AUTO).
Return values:
<Reliability> decimal
Reliability Indicator
<Pattern Type> P44 | P11 | OTHer | ALTernating
P11: 10101010
P44: 11110000
OTHer: any pattern except P11, P44
ALTernating: the periodical change of the pattern P11 and P44
*RST: OTH
Example: See Automatic Detection Mode
Usage: Query only
Firmware/Software: V2.0.20
V2.1.20: optional mnemonic BRATe appended
V3.5.30: added pattern ALTernating
Manual operation: See "Pattern Type" on page 438
FETCh:BLUetooth:MEAS<i>:ISIGnal:ADETected:PATTern:LENergy:LE2M?
FETCh:BLUetooth:MEAS<i>:ISIGnal:ADETected:PATTern:LENergy[:LE1M]?
Returns the detected payload pattern type.
Commands for LE 1M PHY (...:LE1M...) and LE 2M PHY (...:LE2M...) are
available.
A result is available after the R&S CMW has auto-detected a packet (CONFigure:
BLUetooth:MEAS<i>:ISIGnal:DMODe AUTO).
Return values:
<Reliability> decimal
Reliability Indicator
<Pattern Type> P44 | P11 | OTHer | ALTernating
P11: 10101010
P44: 11110000
OTHer: any pattern except P11, P44
ALTernating: the periodical change of the pattern P11 and P44
*RST: OTH
Example: See Automatic Detection Mode
Usage: Query only
Firmware/Software: V2.1.20
V3.5.30: added pattern ALTernating
V3.5.70: added command for LE2M
Options: R&S CMW-KM611
Plus R&S CMW-KM721 for LE2M
Manual operation: See "Payload Length" on page 437
FETCh:BLUetooth:MEAS<i>:ISIGnal:ADETected:PATTern:LENergy:LRANge?
Returns the detected payload pattern type for LE coded PHY. A result is available after
the R&S CMW has auto-detected a packet (CONFigure:BLUetooth:MEAS<i>:
ISIGnal:DMODe AUTO).
Return values:
<Reliability> decimal
Reliability Indicator
<Pattern Type> ALL1 | OTHer | P44 | P11 | ALL0 | PRBS9
P11: '10101010'
P44: '11110000'
OTHer: any pattern except P11, P44
ALTernating: the periodical change of the pattern P11 and P44
*RST: OTH
Example: See Automatic Detection Mode
Usage: Query only
Firmware/Software: V3.5.70
Options: R&S CMW-KM721
Manual operation: See "Payload Length" on page 437
FETCh:BLUetooth:MEAS<i>:ISIGnal:ADETected:CODing:LENergy:LRANge?
Returns the detected forward error correction coding for LE coded PHY.
Return values:
<Reliability> decimal
Reliability Indicator
<Coding> S8 | S2
Coding S = 8 or S = 2
Example: See Automatic Detection Mode
Usage: Query only
Firmware/Software: V3.5.70
Options: R&S CMW-KM721
Manual operation: See "Coding (LE coded PHY)" on page 435
FETCh:BLUetooth:MEAS<i>:ISIGnal:ADETected:PLENgth:BRATe?
Returns the detected BR payload length. A result is available after the R&S CMW has
auto-detected a packet (CONFigure:BLUetooth:MEAS<i>:ISIGnal:DMODe
AUTO).
Return values:
<Reliability> decimal
Reliability Indicator
<PayloadLength> decimal
Range: 0 Byte(s) to 339 Byte(s)
Example: See Automatic Detection Mode
Usage: Query only
Firmware/Software: V2.0.20
Manual operation: See "Payload Length" on page 437
FETCh:BLUetooth:MEAS<i>:ISIGnal:ADETected:PLENgth:EDRate?
Returns the detected EDR payload length. A result is available after the R&S CMW
has auto-detected a packet (CONFigure:BLUetooth:MEAS<i>:ISIGnal:DMODe
AUTO).
Return values:
<Reliability> decimal
Reliability Indicator
<PayloadLength> decimal
Range: 0 Byte(s) to 1021 Byte(s)
Example: See Automatic Detection Mode
Usage: Query only
Firmware/Software: V2.0.20
Manual operation: See "Payload Length" on page 437
FETCh:BLUetooth:MEAS<i>:ISIGnal:ADETected:PLENgth:LENergy:LRANge?
FETCh:BLUetooth:MEAS<i>:ISIGnal:ADETected:PLENgth:LENergy:LE2M?
FETCh:BLUetooth:MEAS<i>:ISIGnal:ADETected:PLENgth:LENergy[:LE1M]?
Returns the detected payload length.
Commands for uncoded LE 1M PHY (..:LE1M..), LE 2M PHY (..:LE2M..), and LE
coded PHY (..:LRANge..) are available.
A result is available after the R&S CMW has auto-detected a packet (CONFigure:
BLUetooth:MEAS<i>:ISIGnal:DMODe AUTO).
Return values:
<Reliability> decimal
Reliability Indicator
<PayloadLength> decimal
Range: 0 to 255
Default unit: byte
FETCh:BLUetooth:MEAS<i>:ISIGnal:ADETected:CTE:LENergy:LE1M:TYPE?
FETCh:BLUetooth:MEAS<i>:ISIGnal:ADETected:CTE:LENergy:LE2M:TYPE?
Returns the detected CTE type. A result is available after the R&S CMW has auto-
detected a packet (CONFigure:BLUetooth:MEAS<i>:ISIGnal:DMODeAUTO).
Commands for uncoded LE 1M PHY (..:LE1M..) and LE 2M PHY (..:LE2M..) are
available.
Return values:
<Reliability> decimal
Reliability Indicator
<CTE Type> AOAus | AOD1us | AOD2us | AOA2us | AOA1us
AOD1us, AOD2us: CTE type angle of departure, 1 µs or 2 µs
slot
AOAus, AOA2us: CTE type angle of arrival, 2 µs slot
AOA1us: CTE type angle of arrival, 1 µs slot
Example: See Performing LE with CTE Measurements
Usage: Query only
Firmware/Software: V3.7.70, V3.7.80: added AOAus
V3.7.90: added AOA1us
Options: R&S CMW-KM722
Manual operation: See "CTE Slot Type (LE with CTE)" on page 439
FETCh:BLUetooth:MEAS<i>:ISIGnal:ADETected:CTE:LENergy:LE1M:UNITs?
FETCh:BLUetooth:MEAS<i>:ISIGnal:ADETected:CTE:LENergy:LE2M:UNITs?
Returns the detected number of CTE units. A result is available after the R&S CMW
has auto-detected a packet (CONFigure:BLUetooth:MEAS<i>:ISIGnal:DMODe
AUTO).
Commands for uncoded LE 1M PHY (..:LE1M..) and LE 2M PHY (..:LE2M..) are
available.
Return values:
<Reliability> decimal
Reliability Indicator
<No_of_CTE_Units> decimal
Range: 2 to 20
Example: See Performing LE with CTE Measurements
Usage: Query only
Firmware/Software: V3.7.70
Options: R&S CMW-KM722
Manual operation: See "CTE Units (LE with CTE)" on page 440
FETCh:BLUetooth:MEAS<i>:ISIGnal:ADETected:NOSLots:BRATe?
Returns the detected BR number of off slots. A result is available after the R&S CMW
has auto-detected a packet (CONFigure:BLUetooth:MEAS<i>:ISIGnal:DMODe
AUTO).
Return values:
<Reliability> decimal
Reliability Indicator
<NoOfOffSlots> decimal
Range: 0 to 9
Example: See Automatic Detection Mode
Usage: Query only
Firmware/Software: V2.0.20
Manual operation: See "No. of Off Slots " on page 441
FETCh:BLUetooth:MEAS<i>:ISIGnal:ADETected:NOSLots:EDRate?
Returns the detected EDR number of off slots. A result is available after the R&S CMW
has auto-detected a packet (CONFigure:BLUetooth:MEAS<i>:ISIGnal:DMODe
AUTO).
Return values:
<Reliability> decimal
Reliability Indicator
<NoOfOffSlots> decimal
Range: 0 to 9
Example: See Automatic Detection Mode
Usage: Query only
Firmware/Software: V2.0.20
Manual operation: See "No. of Off Slots " on page 441
The following commands return the power results (single values) for BR packets.
CALCulate:BLUetooth:MEAS<i>:MEValuation:PVTime:BRATe:CURRent?
CALCulate:BLUetooth:MEAS<i>:MEValuation:PVTime:BRATe:AVERage?
CALCulate:BLUetooth:MEAS<i>:MEValuation:PVTime:BRATe:MINimum?
CALCulate:BLUetooth:MEAS<i>:MEValuation:PVTime:BRATe:MAXimum?
FETCh:BLUetooth:MEAS<i>:MEValuation:PVTime:BRATe:CURRent?
FETCh:BLUetooth:MEAS<i>:MEValuation:PVTime:BRATe:AVERage?
FETCh:BLUetooth:MEAS<i>:MEValuation:PVTime:BRATe:MINimum?
FETCh:BLUetooth:MEAS<i>:MEValuation:PVTime:BRATe:MAXimum?
READ:BLUetooth:MEAS<i>:MEValuation:PVTime:BRATe:CURRent?
READ:BLUetooth:MEAS<i>:MEValuation:PVTime:BRATe:AVERage?
READ:BLUetooth:MEAS<i>:MEValuation:PVTime:BRATe:MINimum?
READ:BLUetooth:MEAS<i>:MEValuation:PVTime:BRATe:MAXimum?
Returns the power results for BR packets.
The values described below are returned by FETCh and READ commands. CALCulate
commands return limit check results instead, one value for each result listed below.
Return values:
<1_Reliability> decimal
Reliability Indicator
<2_Out of Tol> float | ON | OFF
Out of tolerance result, i.e. percentage of measurement intervals
of the statistic count (CONFigure:BLUetooth:MEAS<i>:
MEValuation:SCOunt:PVTime) exceeding the specified lim-
its.
Range: 0 % to 100 %
Default unit: %
<3_Nominal Pow> float
Average power during the carrier-on state
Range: -99.99 dBm to 99.99 dBm
Default unit: dBm
<4_Peak Pow> float
Peak power during the carrier-on state
Range: -99.99 dBm to 99.99 dBm
Default unit: dBm
<5_Leakage Pow> float
Average power during the carrier-off state
Range: -99.99 dBm to 99.99 dBm
Default unit: dBm
<6_PacketTiming> float
Time between the expected and actual start of the first symbol of
the Bluetooth burst
Range: -99.99 µs to 99.99 µs
Default unit: s
<7_GFSK_Pow> float
Average power within the access code and header portion of the
BR burst (first 126 symbols).
Range: -99.99 dBm to 99.99 dBm
Default unit: dBm
Example: See Performing PvT and Modulation Measurements
Usage: Query only
Firmware/Software: V1.0.10.50
V3.2.30: <PacketTiming> added
V3.2.60: <GFSK_Power> added
The following commands return the power results (single values) for EDR packets.
CALCulate:BLUetooth:MEAS<i>:MEValuation:PVTime:EDRate:CURRent?
CALCulate:BLUetooth:MEAS<i>:MEValuation:PVTime:EDRate:AVERage?
CALCulate:BLUetooth:MEAS<i>:MEValuation:PVTime:EDRate:MINimum?
CALCulate:BLUetooth:MEAS<i>:MEValuation:PVTime:EDRate:MAXimum?
FETCh:BLUetooth:MEAS<i>:MEValuation:PVTime:EDRate:CURRent?
FETCh:BLUetooth:MEAS<i>:MEValuation:PVTime:EDRate:AVERage?
FETCh:BLUetooth:MEAS<i>:MEValuation:PVTime:EDRate:MINimum?
FETCh:BLUetooth:MEAS<i>:MEValuation:PVTime:EDRate:MAXimum?
READ:BLUetooth:MEAS<i>:MEValuation:PVTime:EDRate:CURRent?
READ:BLUetooth:MEAS<i>:MEValuation:PVTime:EDRate:AVERage?
READ:BLUetooth:MEAS<i>:MEValuation:PVTime:EDRate:MINimum?
READ:BLUetooth:MEAS<i>:MEValuation:PVTime:EDRate:MAXimum?
Returns the power results for EDR packets.
The values described below are returned by FETCh and READ commands. CALCulate
commands return limit check results instead, one value for each result listed below.
Return values:
<1_Reliability> decimal
Reliability Indicator
Firmware/Software: V1.0.10.50
V3.2.30: <8_PacketTiming> added
V3.5.60: <9_PeakPower> added
CALCulate:BLUetooth:MEAS<i>:MEValuation:PVTime:LENergy[:LE1M]:
CURRent?
CALCulate:BLUetooth:MEAS<i>:MEValuation:PVTime:LENergy[:LE1M]:
AVERage?
CALCulate:BLUetooth:MEAS<i>:MEValuation:PVTime:LENergy[:LE1M]:
MINimum?
CALCulate:BLUetooth:MEAS<i>:MEValuation:PVTime:LENergy[:LE1M]:
MAXimum?
FETCh:BLUetooth:MEAS<i>:MEValuation:PVTime:LENergy[:LE1M]:CURRent?
FETCh:BLUetooth:MEAS<i>:MEValuation:PVTime:LENergy[:LE1M]:AVERage?
FETCh:BLUetooth:MEAS<i>:MEValuation:PVTime:LENergy[:LE1M]:MINimum?
FETCh:BLUetooth:MEAS<i>:MEValuation:PVTime:LENergy[:LE1M]:MAXimum?
READ:BLUetooth:MEAS<i>:MEValuation:PVTime:LENergy[:LE1M]:CURRent?
READ:BLUetooth:MEAS<i>:MEValuation:PVTime:LENergy[:LE1M]:AVERage?
READ:BLUetooth:MEAS<i>:MEValuation:PVTime:LENergy[:LE1M]:MINimum?
READ:BLUetooth:MEAS<i>:MEValuation:PVTime:LENergy[:LE1M]:MAXimum?
Returns the power results for LE 1M PHY (uncoded).
The values described below are returned by FETCh and READ commands. CALCulate
commands return limit check results instead, one value for each result listed below.
Return values:
<Reliability> decimal
Reliability Indicator
<BurstOutOfTol> float
Out of tolerance result, i.e. percentage of measurement intervals
of the statistic count (CONFigure:BLUetooth:MEAS<i>:
MEValuation:SCOunt:PVTime) exceeding the specified lim-
its, see CONFigure:BLUetooth:MEAS<i>:MEValuation:
LIMit:LENergy[:LE1M]:PVTime.
Range: 0 % to 100 %
Default unit: %
<NominalPower> float
Average power during the carrier-on state
Range: -99.99 dBm to 99.99 dBm
Default unit: dBm
<PeakPower> float
Peak power during the carrier-on state
Range: -99.99 dBm to 99.99 dBm
Default unit: dBm
<LeakagePower> float
Average power during the carrier-off state
Range: -99.99 dBm to 99.99 dBm
Default unit: dBm
<PeakMinAvgPow> float
Peak power minus average power
Range: -99.99 dBm to 99.99 dBm
Default unit: dBm
Example: See Performing PvT and Modulation Measurements
Usage: Query only
Firmware/Software: V2.1.20
Options: R&S CMW-KM611
CALCulate:BLUetooth:MEAS<i>:MEValuation:PVTime:LENergy:LRANge:
CURRent?
CALCulate:BLUetooth:MEAS<i>:MEValuation:PVTime:LENergy:LRANge:
AVERage?
CALCulate:BLUetooth:MEAS<i>:MEValuation:PVTime:LENergy:LRANge:
MINimum?
CALCulate:BLUetooth:MEAS<i>:MEValuation:PVTime:LENergy:LRANge:
MAXimum?
FETCh:BLUetooth:MEAS<i>:MEValuation:PVTime:LENergy:LRANge:CURRent?
FETCh:BLUetooth:MEAS<i>:MEValuation:PVTime:LENergy:LRANge:AVERage?
FETCh:BLUetooth:MEAS<i>:MEValuation:PVTime:LENergy:LRANge:MINimum?
FETCh:BLUetooth:MEAS<i>:MEValuation:PVTime:LENergy:LRANge:MAXimum?
READ:BLUetooth:MEAS<i>:MEValuation:PVTime:LENergy:LRANge:CURRent?
READ:BLUetooth:MEAS<i>:MEValuation:PVTime:LENergy:LRANge:AVERage?
READ:BLUetooth:MEAS<i>:MEValuation:PVTime:LENergy:LRANge:MINimum?
READ:BLUetooth:MEAS<i>:MEValuation:PVTime:LENergy:LRANge:MAXimum?
CALCulate:BLUetooth:MEAS<i>:MEValuation:PVTime:LENergy:LE2M:CURRent?
CALCulate:BLUetooth:MEAS<i>:MEValuation:PVTime:LENergy:LE2M:AVERage?
CALCulate:BLUetooth:MEAS<i>:MEValuation:PVTime:LENergy:LE2M:MINimum?
CALCulate:BLUetooth:MEAS<i>:MEValuation:PVTime:LENergy:LE2M:
MAXimum?
FETCh:BLUetooth:MEAS<i>:MEValuation:PVTime:LENergy:LE2M:CURRent?
FETCh:BLUetooth:MEAS<i>:MEValuation:PVTime:LENergy:LE2M:AVERage?
FETCh:BLUetooth:MEAS<i>:MEValuation:PVTime:LENergy:LE2M:MINimum?
FETCh:BLUetooth:MEAS<i>:MEValuation:PVTime:LENergy:LE2M:MAXimum?
READ:BLUetooth:MEAS<i>:MEValuation:PVTime:LENergy:LE2M:CURRent?
READ:BLUetooth:MEAS<i>:MEValuation:PVTime:LENergy:LE2M:AVERage?
READ:BLUetooth:MEAS<i>:MEValuation:PVTime:LENergy:LE2M:MINimum?
READ:BLUetooth:MEAS<i>:MEValuation:PVTime:LENergy:LE2M:MAXimum?
Returns the power results for LE 2M PHY (...:LE2M...) and LE coded PHY
(...:LRANge...).
The values described below are returned by FETCh and READ commands. CALCulate
commands return limit check results instead, one value for each result listed below.
Return values:
<Reliability> decimal
Reliability Indicator
The following commands return the power results (single values) in normal mode.
Commands for normal mode with BR/EDR (..:NMODe:CLASsic..) and LE
(..:NMODe:LENenergy..) are available.
LE commands support uncoded LE 1M PHY (..:NMODe:LEN:LE1M:..), LE 2M PHY
(..:NMODe:LEN:LE2M:..), and LE coded PHY (..:NMODe:LEN:LRANge..).
Measurements in normal mode are only supported in combined signal path, see Chap-
ter 7.2.1.3, "Parallel Signaling and Measurement", on page 332.
CALCulate:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:CLASsic:CURRent?............ 585
CALCulate:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:CLASsic:AVERage?............585
CALCulate:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:CLASsic:MINimum?............ 585
CALCulate:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:CLASsic:MAXimum?........... 585
FETCh:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:CLASsic:CURRent?................. 585
FETCh:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:CLASsic:AVERage?................. 585
FETCh:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:CLASsic:MINimum?................. 585
FETCh:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:CLASsic:MAXimum?................ 585
READ:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:CLASsic:CURRent?...................585
READ:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:CLASsic:AVERage?...................585
READ:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:CLASsic:MINimum?...................585
READ:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:CLASsic:MAXimum?..................585
CALCulate:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:LENergy:LE2M:
CURRent?.......................................................................................................... 586
CALCulate:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:LENergy:LE2M:
AVERage?.......................................................................................................... 586
CALCulate:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:LENergy:LE2M:
MINimum?.......................................................................................................... 586
CALCulate:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:LENergy:LE2M:
MAXimum?......................................................................................................... 586
CALCulate:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:LENergy:LRANge:
CURRent?.......................................................................................................... 586
CALCulate:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:LENergy:LRANge:
AVERage?.......................................................................................................... 586
CALCulate:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:LENergy:LRANge:
MINimum?.......................................................................................................... 586
CALCulate:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:LENergy:LRANge:
MAXimum?......................................................................................................... 586
CALCulate:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:LENergy[:LE1M]:
CURRent?.......................................................................................................... 586
CALCulate:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:LENergy[:LE1M]:
AVERage?.......................................................................................................... 586
CALCulate:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:LENergy[:LE1M]:
MINimum?.......................................................................................................... 586
CALCulate:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:LENergy[:LE1M]:
MAXimum?......................................................................................................... 586
FETCh:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:LENergy:LE2M:CURRent?........586
FETCh:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:LENergy:LE2M:AVERage?........586
FETCh:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:LENergy:LE2M:MINimum?........586
FETCh:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:LENergy:LE2M:MAXimum?.......586
FETCh:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:LENergy:LRANge:CURRent?.... 586
FETCh:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:LENergy:LRANge:AVERage?.... 586
FETCh:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:LENergy:LRANge:MINimum?.... 586
FETCh:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:LENergy:LRANge:MAXimum?... 586
FETCh:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:LENergy[:LE1M]:CURRent?...... 587
FETCh:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:LENergy[:LE1M]:AVERage?...... 587
FETCh:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:LENergy[:LE1M]:MINimum?...... 587
FETCh:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:LENergy[:LE1M]:MAXimum?..... 587
READ:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:LENergy:LE2M:CURRent?......... 587
READ:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:LENergy:LE2M:AVERage?......... 587
READ:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:LENergy:LE2M:MINimum?......... 587
READ:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:LENergy:LE2M:MAXimum?........ 587
READ:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:LENergy:LRANge:CURRent?..... 587
READ:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:LENergy:LRANge:AVERage?..... 587
READ:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:LENergy:LRANge:MINimum?..... 587
READ:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:LENergy:LRANge:MAXimum?.... 587
READ:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:LENergy[:LE1M]:CURRent?....... 587
READ:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:LENergy[:LE1M]:AVERage?....... 587
READ:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:LENergy[:LE1M]:MINimum?....... 587
READ:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:LENergy[:LE1M]:MAXimum?...... 587
CALCulate:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:CLASsic:
CURRent?
CALCulate:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:CLASsic:
AVERage?
CALCulate:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:CLASsic:
MINimum?
CALCulate:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:CLASsic:
MAXimum?
FETCh:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:CLASsic:CURRent?
FETCh:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:CLASsic:AVERage?
FETCh:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:CLASsic:MINimum?
FETCh:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:CLASsic:MAXimum?
READ:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:CLASsic:CURRent?
READ:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:CLASsic:AVERage?
READ:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:CLASsic:MINimum?
READ:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:CLASsic:MAXimum?
Returns the current, average, min, and max power results for BR/EDR, normal mode.
The values described below are returned by FETCh and READ commands. CALCulate
commands return limit check results instead, one value for each result listed below.
Return values:
<Reliability> decimal
See Reliability Indicator
<BurstOutOfTol> float | ON | OFF
Out of tolerance result, i.e. percentage of measurement intervals
of the statistic count (CONFigure:BLUetooth:MEAS<i>:
MEValuation:SCOunt:PVTime) exceeding the specified lim-
its, see CONFigure:BLUetooth:MEAS<i>:MEValuation:
LIMit:BRATe:PVTime and CONFigure:BLUetooth:
MEAS<i>:MEValuation:LIMit:EDRate:PVTime.
Range: 0 % to 100 %
Default unit: %
<NominalPower> float
Average power during the carrier-on state
Range: -99.99 dBm to 99.99 dBm
Default unit: dBm
Usage: Query only
Firmware/Software: V3.7.40
CALCulate:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:LENergy:LE2M:
CURRent?
CALCulate:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:LENergy:LE2M:
AVERage?
CALCulate:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:LENergy:LE2M:
MINimum?
CALCulate:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:LENergy:LE2M:
MAXimum?
CALCulate:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:LENergy:LRANge:
CURRent?
CALCulate:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:LENergy:LRANge:
AVERage?
CALCulate:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:LENergy:LRANge:
MINimum?
CALCulate:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:LENergy:LRANge:
MAXimum?
CALCulate:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:LENergy[:LE1M]:
CURRent?
CALCulate:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:LENergy[:LE1M]:
AVERage?
CALCulate:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:LENergy[:LE1M]:
MINimum?
CALCulate:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:LENergy[:LE1M]:
MAXimum?
FETCh:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:LENergy:LE2M:
CURRent?
FETCh:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:LENergy:LE2M:
AVERage?
FETCh:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:LENergy:LE2M:
MINimum?
FETCh:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:LENergy:LE2M:
MAXimum?
FETCh:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:LENergy:LRANge:
CURRent?
FETCh:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:LENergy:LRANge:
AVERage?
FETCh:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:LENergy:LRANge:
MINimum?
FETCh:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:LENergy:LRANge:
MAXimum?
FETCh:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:LENergy[:LE1M]:
CURRent?
FETCh:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:LENergy[:LE1M]:
AVERage?
FETCh:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:LENergy[:LE1M]:
MINimum?
FETCh:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:LENergy[:LE1M]:
MAXimum?
READ:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:LENergy:LE2M:
CURRent?
READ:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:LENergy:LE2M:
AVERage?
READ:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:LENergy:LE2M:
MINimum?
READ:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:LENergy:LE2M:
MAXimum?
READ:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:LENergy:LRANge:
CURRent?
READ:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:LENergy:LRANge:
AVERage?
READ:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:LENergy:LRANge:
MINimum?
READ:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:LENergy:LRANge:
MAXimum?
READ:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:LENergy[:LE1M]:
CURRent?
READ:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:LENergy[:LE1M]:
AVERage?
READ:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:LENergy[:LE1M]:
MINimum?
READ:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:LENergy[:LE1M]:
MAXimum?
Returns the current, average, min, and max power results for LE normal mode.
Commands for uncoded LE 1M PHY (..:LE1M..), LE 2M PHY (..:LE2M..), and LE
coded PHY (..:LRANge..) are available.
The values described below are returned by FETCh and READ commands. CALCulate
commands return limit check results instead, one value for each result listed below.
Return values:
<Reliability> decimal
See Reliability Indicator
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:BRATe:AVERage?...........................589
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:BRATe:XMINimum?.........................589
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:BRATe:XMAXimum?........................589
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:BRATe:MAXimum?..........................589
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:BRATe:CURRent?............................ 589
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:BRATe:AVERage?............................ 589
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:BRATe:XMINimum?.......................... 589
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:BRATe:XMAXimum?......................... 589
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:BRATe:MAXimum?........................... 589
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:BRATe:MINimum?..................... 591
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:BRATe:MINimum?...........................591
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:BRATe:MINimum?............................ 591
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:BRATe:SDEViation?...................592
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:BRATe:SDEViation?........................ 592
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:BRATe:SDEViation?......................... 592
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:BRATe:YIELd?................................ 593
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:BRATe:CURRent?
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:BRATe:AVERage?
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:BRATe:XMINimum?
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:BRATe:XMAXimum?
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:BRATe:MAXimum?
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:BRATe:CURRent?
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:BRATe:AVERage?
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:BRATe:XMINimum?
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:BRATe:XMAXimum?
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:BRATe:MAXimum?
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:BRATe:CURRent?
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:BRATe:AVERage?
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:BRATe:XMINimum?
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:BRATe:XMAXimum?
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:BRATe:MAXimum?
Returns the current, average, absolute min (xmin), absolute max (xmax), and max
modulation results for BR packets.
The values described below are returned by FETCh and READ commands. CALCulate
commands return limit check results instead, one value for each result listed below.
Return values:
<1_Reliability> decimal
See Reliability Indicator
<2_Out of Tol> float
Out of tolerance result, i.e. percentage of measurement intervals
of the statistic count (CONFigure:BLUetooth:MEAS<i>:
MEValuation:SCOunt:MODulation) exceeding the specified
limits.
Range: 0 % to 100 %
Default unit: %
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:BRATe:MINimum?
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:BRATe:MINimum?
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:BRATe:MINimum?
Returns the minimum modulation results for BR packets.
The values described below are returned by FETCh and READ commands. CALCulate
commands return limit check results instead, one value for each result listed below.
Return values:
<1_Reliability> decimal
Reliability Indicator
<2_Out of Tol> float
Out of tolerance result, i.e. percentage of measurement intervals
of the statistic count (CONFigure:BLUetooth:MEAS<i>:
MEValuation:SCOunt:MODulation) exceeding the specified
limits.
Range: 0 % to 100 %
Default unit: %
<3_Δf2 99.9%> float
Range: -0.99999E+6 Hz to 0.99999E+6 Hz
Default unit: Hz
<4_Δf1 avg> float
Frequency deviation results
Range: -0.99999E+6 Hz to 0.99999E+6 Hz
Default unit: Hz
<5_Δf1 min> float
Range: -0.99999E+6 Hz to 0.99999E+6 Hz
Default unit: Hz
<6_Δf1 max> float
Range: -0.99999E+6 Hz to 0.99999E+6 Hz
Default unit: Hz
<7_Δf2 avg> float
Range: -0.99999E+6 Hz to 0.99999E+6 Hz
Default unit: Hz
<8_Δf2 min> float
Range: -0.99999E+6 Hz to 0.99999E+6 Hz
Default unit: Hz
<9_Δf2 max> float
Range: -0.99999E+6 Hz to 0.99999E+6 Hz
Default unit: Hz
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:BRATe:SDEViation?
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:BRATe:SDEViation?
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:BRATe:SDEViation?
Returns the standard deviation of the modulation results for BR packets.
The values described below are returned by FETCh and READ commands. CALCulate
commands return limit check results instead, one value for each result listed below.
Return values:
<1_Reliability> decimal
Reliability Indicator
<2_Out of Tol> float
Out of tolerance result, i.e. percentage of measurement intervals
of the statistic count (CONFigure:BLUetooth:MEAS<i>:
MEValuation:SCOunt:MODulation) exceeding the specified
limits.
Range: 0 % to 100 %
Default unit: %
<3_Δf2 99.9%> float
Range: -0.99999E+6 Hz to 0.99999E+6 Hz
Default unit: Hz
<4_Freq. Accuracy> float
Range: -0.99999E+6 Hz to 0.99999E+6 Hz
Default unit: Hz
<5_Freq. Drift> float
Range: -0.99999E+6 Hz to 0.99999E+6 Hz
Default unit: Hz
<6_Max. Drift Rate> float
Range: -0.99999E+6 Hz/50 μs to 0.99999E+6 Hz/50 μs
Default unit: Hz/50 μs
<7_NominalPower> float
Average power during the carrier-on state
Range: 0 dB to 79 dB
Default unit: dB
<8_ModRatio> float
Modulation ratio Δf2 avg / Δf1 avg
Range: 0 to 1
Example: See Performing PvT and Modulation Measurements
Usage: Query only
Firmware/Software: V1.0.10.1 (modulation ratio added in V2.0.20)
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:BRATe:YIELd?
Returns the percentages of auto-detected BR packets with a particular pattern type. A
result is available after the R&S CMW has auto-detected a packet (CONFigure:
BLUetooth:MEAS<i>:ISIGnal:DMODeAUTO).
Return values:
<Reliability> decimal
Reliability Indicator
<PatternYield> float
Pattern yield for 11110000 patterns, 10101010 patterns, and any
other patterns (3 values)
Range: 0 to 100
Default unit: %
Example: See Automatic Detection Mode
Usage: Query only
Firmware/Software: V2.0.10
The following commands return the modulation results for EDR packets.
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:EDRate:CURRent?.................... 594
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:EDRate:AVERage?....................594
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:EDRate:MAXimum?................... 594
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:EDRate:CURRent?......................... 594
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:EDRate:AVERage?......................... 594
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:EDRate:MAXimum?........................ 594
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:EDRate:CURRent?...........................594
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:EDRate:AVERage?...........................594
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:EDRate:MAXimum?..........................594
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:EDRate:SDEViation?................. 595
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:EDRate:SDEViation?.......................595
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:EDRate:SDEViation?........................ 595
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:EDRate:CURRent?
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:EDRate:AVERage?
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:EDRate:MAXimum?
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:EDRate:CURRent?
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:EDRate:AVERage?
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:EDRate:MAXimum?
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:EDRate:CURRent?
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:EDRate:AVERage?
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:EDRate:MAXimum?
Returns the modulation results for EDR packets.
The values described below are returned by FETCh and READ commands. CALCulate
commands return limit check results instead, one value for each result listed below.
Return values:
<1_Reliability> decimal
Reliability Indicator
<2_Out of Tol> float
Out of tolerance result, i.e. percentage of measurement intervals
of the statistic count (CONFigure:BLUetooth:MEAS<i>:
MEValuation:SCOunt:MODulation) exceeding the specified
limits.
Range: 0 % to 100 %
Default unit: %
<3_ωi> float
Initial center frequency error
Range: -0.99999E+6 Hz to 0.99999E+6 Hz
Default unit: Hz
<4_ω0 + ωi> float
Overall uncompensated frequency error
Range: -0.99999E+6 Hz to 0.99999E+6 Hz
Default unit: Hz
<5_ω0max> float
Maximum compensated frequency error
Range: -0.99999E+6 Hz to 0.99999E+6 Hz
Default unit: Hz
<6_RMS DEVM> float
Differential EVM results
Range: 0 to 1
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:EDRate:SDEViation?
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:EDRate:SDEViation?
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:EDRate:SDEViation?
Returns the standard deviation of the modulation results for EDR packets.
The values described below are returned by FETCh and READ commands. CALCulate
commands return limit check results instead, one value for each result listed below.
Return values:
<1_Reliability> decimal
Reliability Indicator
<2_Out of Tol> float
Out of tolerance result, i.e. percentage of measurement intervals
of the statistic count (CONFigure:BLUetooth:MEAS<i>:
MEValuation:SCOunt:MODulation) exceeding the specified
limits.
Range: 0 % to 100 %
Default unit: %
<3_ωi> float
Standard deviation of the initial center frequency error
Range: -0.99999E+6 Hz to 0.99999E+6 Hz
Default unit: Hz
<4_ω0 + ωi> float
Standard deviation of the overall uncompensated frequency
error
Range: -0.99999E+6 Hz to 0.99999E+6 Hz
Default unit: Hz
<5_ω0max> float
Standard deviation of the maximum compensated frequency
error
Range: -0.99999E+6 Hz to 0.99999E+6 Hz
Default unit: Hz
<6_RMS DEVM> float
Standard deviation of the differential EVM results
Range: 0 to 1
<7_Peak DEVM> float
Range: 0 to 1
<8_P99 DEVM> float
Range: 0 to 1
<9_Nominal Pow> float
Standard deviation of the average power during the carrier-on
state
Range: -99.99 dBm to 99.99 dBm
Example: See Performing PvT and Modulation Measurements.
Usage: Query only
Firmware/Software: V1.0.10.1
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:CTE:LENergy:LE2M:
AVERage?.......................................................................................................... 599
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:CTE:LENergy:LE2M:
SDEViation?........................................................................................................599
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:CTE:LENergy:LE2M:
XMINimum?........................................................................................................ 599
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:CTE:LENergy:LE2M:
XMAXimum?....................................................................................................... 599
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:CTE:LENergy:LE2M:
MAXimum?......................................................................................................... 599
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:CTE:LENergy:LE1M:CURRent?....... 599
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:CTE:LENergy:LE1M:AVERage?....... 599
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:CTE:LENergy:LE1M:SDEViation?.....599
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:CTE:LENergy:LE1M:XMINimum?..... 599
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:CTE:LENergy:LE1M:XMAXimum?.... 599
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:CTE:LENergy:LE1M:MAXimum?...... 599
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:CTE:LENergy:LE2M:CURRent?....... 599
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:CTE:LENergy:LE2M:AVERage?....... 599
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:CTE:LENergy:LE2M:SDEViation?.....599
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:CTE:LENergy:LE2M:XMINimum?..... 599
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:CTE:LENergy:LE2M:XMAXimum?.... 599
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:CTE:LENergy:LE2M:MAXimum?...... 599
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:CTE:LENergy:LE1M:CURRent?.........600
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:CTE:LENergy:LE1M:AVERage?........ 600
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:CTE:LENergy:LE1M:SDEViation?...... 600
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:CTE:LENergy:LE1M:XMINimum?...... 600
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:CTE:LENergy:LE1M:XMAXimum?..... 600
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:CTE:LENergy:LE1M:MAXimum?........600
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:CTE:LENergy:LE2M:CURRent?.........600
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:CTE:LENergy:LE2M:AVERage?........ 600
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:CTE:LENergy:LE2M:SDEViation?...... 600
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:CTE:LENergy:LE2M:XMINimum?...... 600
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:CTE:LENergy:LE2M:XMAXimum?..... 600
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:CTE:LENergy:LE2M:MAXimum?........600
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy[:LE1M]:CURRent?........601
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy[:LE1M]:AVERage?....... 601
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy[:LE1M]:XMINimum?..... 601
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy[:LE1M]:XMAXimum?.... 601
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy[:LE1M]:MAXimum?...... 601
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy[:LE1M]:CURRent?............. 601
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy[:LE1M]:AVERage?.............601
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy[:LE1M]:XMINimum?...........601
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy[:LE1M]:XMAXimum?..........601
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy[:LE1M]:MAXimum?............601
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy[:LE1M]:CURRent?.............. 601
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy[:LE1M]:AVERage?.............. 601
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy[:LE1M]:XMINimum?............ 601
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy[:LE1M]:XMAXimum?........... 601
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy[:LE1M]:MAXimum?............. 601
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LE2M:CURRent?......... 601
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LE2M:AVERage?......... 601
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LE2M:XMINimum?....... 602
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LE2M:XMAXimum?...... 602
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LE2M:MAXimum?........ 602
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LE2M:CURRent?...............602
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LE2M:AVERage?...............602
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LE2M:XMINimum?.............602
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LE2M:XMAXimum?............602
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LE2M:MAXimum?..............602
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LE2M:CURRent?................ 602
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LE2M:AVERage?................ 602
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LE2M:XMINimum?..............602
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LE2M:XMAXimum?.............602
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LE2M:MAXimum?............... 602
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LRANge:CURRent?......604
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LRANge:AVERage?..... 604
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LRANge:XMINimum?... 604
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LRANge:
XMAXimum?....................................................................................................... 604
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LRANge:MAXimum?.... 604
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LRANge:CURRent?........... 604
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LRANge:AVERage?...........604
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LRANge:XMINimum?.........604
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LRANge:XMAXimum?........604
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LRANge:MAXimum?.......... 604
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LRANge:CURRent?............ 604
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LRANge:AVERage?............ 604
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LRANge:XMINimum?.......... 604
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LRANge:XMAXimum?......... 604
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LRANge:MAXimum?........... 604
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy[:LE1M]:MINimum?........605
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy[:LE1M]:MINimum?............. 605
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy[:LE1M]:MINimum?.............. 605
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LE2M:MINimum?......... 605
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LE2M:MINimum?...............606
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LE2M:MINimum?................ 606
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LRANge:MINimum?......607
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LRANge:MINimum?........... 607
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LRANge:MINimum?............ 607
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy[:LE1M]:SDEViation?..... 608
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy[:LE1M]:SDEViation?.......... 608
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy[:LE1M]:SDEViation?............608
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LE2M:SDEViation?.......608
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LE2M:SDEViation?............ 608
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LE2M:SDEViation?............. 608
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LRANge:SDEViation?... 609
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LRANge:SDEViation?........ 609
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LRANge:SDEViation?..........609
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LE2M:YIELd?....................610
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy[:LE1M]:YIELd?.................. 610
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:CTE:LENergy:LE1M:
CURRent?
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:CTE:LENergy:LE1M:
AVERage?
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:CTE:LENergy:LE1M:
SDEViation?
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:CTE:LENergy:LE1M:
XMINimum?
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:CTE:LENergy:LE1M:
XMAXimum?
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:CTE:LENergy:LE1M:
MAXimum?
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:CTE:LENergy:LE2M:
CURRent?
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:CTE:LENergy:LE2M:
AVERage?
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:CTE:LENergy:LE2M:
SDEViation?
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:CTE:LENergy:LE2M:
XMINimum?
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:CTE:LENergy:LE2M:
XMAXimum?
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:CTE:LENergy:LE2M:
MAXimum?
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:CTE:LENergy:LE1M:
CURRent?
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:CTE:LENergy:LE1M:
AVERage?
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:CTE:LENergy:LE1M:
SDEViation?
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:CTE:LENergy:LE1M:
XMINimum?
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:CTE:LENergy:LE1M:
XMAXimum?
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:CTE:LENergy:LE1M:
MAXimum?
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:CTE:LENergy:LE2M:
CURRent?
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:CTE:LENergy:LE2M:
AVERage?
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:CTE:LENergy:LE2M:
SDEViation?
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:CTE:LENergy:LE2M:
XMINimum?
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:CTE:LENergy:LE2M:
XMAXimum?
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:CTE:LENergy:LE2M:
MAXimum?
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:CTE:LENergy:LE1M:
CURRent?
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:CTE:LENergy:LE1M:
AVERage?
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:CTE:LENergy:LE1M:
SDEViation?
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:CTE:LENergy:LE1M:
XMINimum?
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:CTE:LENergy:LE1M:
XMAXimum?
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:CTE:LENergy:LE1M:
MAXimum?
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:CTE:LENergy:LE2M:
CURRent?
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:CTE:LENergy:LE2M:
AVERage?
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:CTE:LENergy:LE2M:
SDEViation?
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:CTE:LENergy:LE2M:
XMINimum?
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:CTE:LENergy:LE2M:
XMAXimum?
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:CTE:LENergy:LE2M:
MAXimum?
Returns current, average, standard deviation, absolute min (xmin), absolute max
(xmax), and max CTE modulation results for LE uncoded PHY (LE 1M PHY, LE 2M
PHY).
The values described below are returned by FETCh and READ commands. CALCulate
commands return limit check results instead, one value for each result listed below.
Return values:
<1_Reliability> decimal
See Reliability Indicator
<2_Out_of_Tol> float
Out of tolerance result, i.e. percentage of measurement intervals
of the statistic count (CONFigure:BLUetooth:MEAS<i>:
MEValuation:SCOunt:MODulation) exceeding the specified
limits, see Limits (Modulation LE).
Range: 0 % to 100 %
<3_Freq_Drift> float
Range: -0.99999E+6 Hz to 0.99999E+6 Hz
Default unit: Hz
<4_Max_Drift_Rate> float
Range: -0.99999E+6 Hz to 0.99999E+6 Hz
Default unit: Hz/50 μs
<5_Freq_Offset> float
Range: -0.99999E+6 Hz to 0.99999E+6 Hz
Default unit: Hz
<6_Initial_Freq_Drift> float
Range: -0.99999E+6 Hz to 0.99999E+6 Hz
Default unit: Hz
Example: See Performing LE with CTE Measurements
Usage: Query only
Firmware/Software: V3.7.70
Options: R&S CMW-KM722
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy[:LE1M]:
CURRent?
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy[:LE1M]:
AVERage?
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy[:LE1M]:
XMINimum?
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy[:LE1M]:
XMAXimum?
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy[:LE1M]:
MAXimum?
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy[:LE1M]:
CURRent?
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy[:LE1M]:
AVERage?
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy[:LE1M]:
XMINimum?
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy[:LE1M]:
XMAXimum?
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy[:LE1M]:
MAXimum?
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy[:LE1M]:
CURRent?
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy[:LE1M]:
AVERage?
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy[:LE1M]:
XMINimum?
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy[:LE1M]:
XMAXimum?
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy[:LE1M]:
MAXimum?
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LE2M:
CURRent?
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LE2M:
AVERage?
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LE2M:
XMINimum?
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LE2M:
XMAXimum?
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LE2M:
MAXimum?
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LE2M:CURRent?
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LE2M:AVERage?
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LE2M:
XMINimum?
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LE2M:
XMAXimum?
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LE2M:
MAXimum?
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LE2M:CURRent?
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LE2M:AVERage?
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LE2M:
XMINimum?
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LE2M:
XMAXimum?
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LE2M:MAXimum?
Returns current, average, absolute min (xmin), absolute max (xmax), and max modula-
tion results for LE uncoded PHY (LE 1M PHY, LE 2M PHY), see Chapter 7.4.2.17, "LE:
Statistical Modulation Results ", on page 410.
The values described below are returned by FETCh and READ commands. CALCulate
commands return limit check results instead, one value for each result listed below.
Return values:
<1_Reliability> decimal
See Reliability Indicator
<2_Out of Tol> float
Out of tolerance result, i.e. percentage of measurement intervals
of the statistic count (CONFigure:BLUetooth:MEAS<i>:
MEValuation:SCOunt:MODulation) exceeding the specified
limits, see Limits (Modulation LE).
Range: 0 % to 100 %
<3_Δf2 99.9%> float
Range: -0.99999E+6 Hz to 0.99999E+6 Hz
Default unit: Hz
<4_Freq. Accuracy> float
Range: -0.99999E+6 Hz to 0.99999E+6 Hz
Default unit: Hz
<5_Freq. Drift> float
Range: -0.99999E+6 Hz to 0.99999E+6 Hz
Default unit: Hz
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LRANge:
CURRent?
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LRANge:
AVERage?
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LRANge:
XMINimum?
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LRANge:
XMAXimum?
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LRANge:
MAXimum?
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LRANge:
CURRent?
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LRANge:
AVERage?
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LRANge:
XMINimum?
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LRANge:
XMAXimum?
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LRANge:
MAXimum?
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LRANge:
CURRent?
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LRANge:
AVERage?
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LRANge:
XMINimum?
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LRANge:
XMAXimum?
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LRANge:
MAXimum?
Returns the current, average, absolute min (xmin), absolute max (xmax), and max
modulation results for LE coded PHY, see Chapter 7.4.2.17, "LE: Statistical Modulation
Results ", on page 410.
The values described below are returned by FETCh and READ commands. CALCulate
commands return limit check results instead, one value for each result listed below.
Return values:
<1_Reliability> decimal
See Reliability Indicator
<2_Out of Tol> float
Out of tolerance result, i.e. percentage of measurement intervals
of the statistic count (CONFigure:BLUetooth:MEAS<i>:
MEValuation:SCOunt:MODulation) exceeding the specified
limits, see Limits (Modulation LE).
Range: 0 % to 100 %
Default unit: %
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy[:LE1M]:
MINimum?
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy[:LE1M]:
MINimum?
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy[:LE1M]:
MINimum?
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LE2M:
MINimum?
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LE2M:MINimum?
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LE2M:MINimum?
Returns the minimum modulation results for LE uncoded PHY (LE 1M PHY, LE 2M
PHY), see Chapter 7.4.2.17, "LE: Statistical Modulation Results ", on page 410.
The values described below are returned by FETCh and READ commands. CALCulate
commands return limit check results instead, one value for each result listed below.
Return values:
<1_Reliability> decimal
Reliability Indicator
<2_Out of Tol> float
Out of tolerance result, i.e. percentage of measurement intervals
of the statistic count (CONFigure:BLUetooth:MEAS<i>:
MEValuation:SCOunt:MODulation) exceeding the specified
limits, see Limits (Modulation LE).
Range: 0 % to 100 %
Default unit: %
<3_Δf2 99.9%> float
Range: -0.99999E+6 Hz to 0.99999E+6 Hz
Default unit: Hz
<4_Δf1 avg> float
Frequency deviation results
Range: -0.99999E+6 Hz to 0.99999E+6 Hz
Default unit: Hz
<5_Δf1 min> float
Range: -0.99999E+6 Hz to 0.99999E+6 Hz
Default unit: Hz
<6_Δf1 max> float
Range: -0.99999E+6 Hz to 0.99999E+6 Hz
Default unit: Hz
<7_Δf2 avg> float
Range: -0.99999E+6 Hz to 0.99999E+6 Hz
Default unit: Hz
<8_Δf2 min> float
Range: -0.99999E+6 Hz to 0.99999E+6 Hz
Default unit: Hz
<9_Δf2 max> float
Range: -0.99999E+6 Hz to 0.99999E+6 Hz
Default unit: dBm
<10_Nominal Pow> float
Range: -99.99 dBm to 99.99 dBm
Default unit: dBm
<11_ModRatio> float
Range: 0 to 1
Usage: Query only
Firmware/Software: V3.5.70
Options: R&S CMW-KM611
R&S CMW-KM721 for LE2M
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LRANge:
MINimum?
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LRANge:
MINimum?
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LRANge:
MINimum?
Returns current, average and maximum modulation results for LE coded PHY, see
Chapter 7.4.2.17, "LE: Statistical Modulation Results ", on page 410.
The values described below are returned by FETCh and READ commands. CALCulate
commands return limit check results instead, one value for each result listed below.
Return values:
<1_Reliability> decimal
Reliability Indicator
<2_Out of Tol> float
Out of tolerance result, i.e. percentage of measurement intervals
of the statistic count (CONFigure:BLUetooth:MEAS<i>:
MEValuation:SCOunt:MODulation) exceeding the specified
limits, see Limits (Modulation LE).
Range: 0 % to 100 %
Default unit: %
<3_Δf1 99.9%> float
Range: -0.99999E+6 Hz to 0.99999E+6 Hz
Default unit: Hz
<4_Δf1 avg> float
Range: -0.99999E+6 Hz to 0.99999E+6 Hz
Default unit: Hz
<5_Δf1 min> float
Range: -0.99999E+6 Hz to 0.99999E+6 Hz
Default unit: Hz
<6_Δf1 max> float
Range: -0.99999E+6 Hz to 0.99999E+6 Hz
Default unit: Hz
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy[:LE1M]:
SDEViation?
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy[:LE1M]:
SDEViation?
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy[:LE1M]:
SDEViation?
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LE2M:
SDEViation?
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LE2M:
SDEViation?
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LE2M:
SDEViation?
Returns the standard deviation of the modulation results for LE uncoded PHY (LE 1M
PHY, LE 2M PHY), see Chapter 7.4.2.17, "LE: Statistical Modulation Results ",
on page 410.
The values described below are returned by FETCh and READ commands. CALCulate
commands return limit check results instead, one value for each result listed below.
Return values:
<1_Reliability> decimal
Reliability Indicator
<2_Out of Tol> float
Out of tolerance result, i.e. percentage of measurement intervals
of the statistic count (CONFigure:BLUetooth:MEAS<i>:
MEValuation:SCOunt:MODulation) exceeding the specified
limits, see Limits (Modulation LE).
Range: 0 % to 100 %
Default unit: %
<3_Δf2 99.9%> float
Range: -0.99999E+6 Hz to 0.99999E+6 Hz
Default unit: Hz
<4_Freq. Accuracy> float
Range: -0.99999E+6 Hz to 0.99999E+6 Hz
Default unit: Hz
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LRANge:
SDEViation?
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LRANge:
SDEViation?
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LRANge:
SDEViation?
Returns the standard deviation of the modulation results for LE coded PHY, see Chap-
ter 7.4.2.17, "LE: Statistical Modulation Results ", on page 410.
The values described below are returned by FETCh and READ commands. CALCulate
commands return limit check results instead, one value for each result listed below.
Return values:
<1_Reliability> decimal
Reliability Indicator
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LE2M:YIELd?
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy[:LE1M]:YIELd?
Returns the percentages of auto-detected LE packets with a particular pattern type.
Commands for uncoded LE 1M PHY (..:LE1M..) and LE 2M PHY (..:LE2M..) are
available.
A result is available after the R&S CMW has auto-detected a packet (CONFigure:
BLUetooth:MEAS<i>:ISIGnal:DMODeAUTO).
Return values:
<Reliability> decimal
Reliability Indicator
<PatternYield> float
Pattern yield for 11110000 patterns, 10101010 patterns, and any
other patterns (3 values)
Range: 0 to 100
Default unit: %
Example: See Automatic Detection Mode
Usage: Query only
Firmware/Software: V2.1.20
V3.5.70: added commands for LE2M
Options: R&S CMW-KM611
Plus R&S CMW-KM721 for LE2M
Measurements in normal mode are only supported in combined signal path, see Chap-
ter 7.2.1.3, "Parallel Signaling and Measurement", on page 332.
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:CLASsic:CURRent?...... 614
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:CLASsic:AVERage?...... 614
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:CLASsic:XMINimum?.... 614
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:CLASsic:XMAXimum?... 614
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:CLASsic:MAXimum?..... 614
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:CLASsic:CURRent?............614
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:CLASsic:AVERage?............614
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:CLASsic:XMINimum?..........614
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:CLASsic:XMAXimum?........ 614
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:CLASsic:MAXimum?...........614
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:CLASsic:CURRent?............. 614
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:CLASsic:AVERage?.............614
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:CLASsic:XMINimum?...........614
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:CLASsic:XMAXimum?..........614
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:CLASsic:MAXimum?............ 614
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:CLASsic:SDEViation?....616
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:CLASsic:SDEViation?......... 616
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:CLASsic:SDEViation?.......... 616
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy[:LE1M]:
CURRent?.......................................................................................................... 616
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy[:LE1M]:
AVERage?.......................................................................................................... 616
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy[:LE1M]:
XMINimum?........................................................................................................ 616
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy[:LE1M]:
XMAXimum?....................................................................................................... 617
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy[:LE1M]:
MAXimum?......................................................................................................... 617
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy[:LE1M]:
CURRent?.......................................................................................................... 617
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy[:LE1M]:
AVERage?.......................................................................................................... 617
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy[:LE1M]:
XMINimum?........................................................................................................ 617
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy[:LE1M]:
XMAXimum?....................................................................................................... 617
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy[:LE1M]:
MAXimum?......................................................................................................... 617
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:LE2M:CURRent?... 617
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy[:LE1M]:
CURRent?.......................................................................................................... 617
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy[:LE1M]:
AVERage?.......................................................................................................... 617
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy[:LE1M]:
XMINimum?........................................................................................................ 617
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy[:LE1M]:
XMAXimum?....................................................................................................... 617
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy[:LE1M]:
MAXimum?......................................................................................................... 617
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:LE2M:
CURRent?.......................................................................................................... 618
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:LE2M:
AVERage?.......................................................................................................... 618
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:LE2M:
XMINimum?........................................................................................................ 618
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:LE2M:
XMAXimum?....................................................................................................... 618
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:LE2M:
MAXimum?......................................................................................................... 618
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:LE2M:CURRent?.. 618
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:LE2M:AVERage?.. 618
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:LE2M:
XMINimum?........................................................................................................ 618
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:LE2M:
XMAXimum?....................................................................................................... 619
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:LE2M:
MAXimum?......................................................................................................... 619
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:LE2M:AVERage?... 619
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:LE2M:
XMINimum?........................................................................................................ 619
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:LE2M:
XMAXimum?....................................................................................................... 619
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:LE2M:MAXimum?.. 619
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:LRANge:
CURRent?.......................................................................................................... 620
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:LRANge:
AVERage?.......................................................................................................... 620
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:LRANge:
XMINimum?........................................................................................................ 620
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:LRANge:
XMAXimum?....................................................................................................... 620
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:LRANge:
MAXimum?......................................................................................................... 620
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:LRANge:
CURRent?.......................................................................................................... 620
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:LRANge:
AVERage?.......................................................................................................... 620
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:LRANge:
XMINimum?........................................................................................................ 620
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:LRANge:
XMAXimum?....................................................................................................... 620
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:LRANge:
MAXimum?......................................................................................................... 620
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:LRANge:
CURRent?.......................................................................................................... 620
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:LRANge:
AVERage?.......................................................................................................... 621
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:LRANge:
XMINimum?........................................................................................................ 621
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:LRANge:
XMAXimum?....................................................................................................... 621
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:LRANge:
MAXimum?......................................................................................................... 621
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy[:LE1M]:
MINimum?.......................................................................................................... 622
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy[:LE1M]:
MINimum?.......................................................................................................... 622
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy[:LE1M]:
MINimum?.......................................................................................................... 622
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:LE2M:
MINimum?.......................................................................................................... 623
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:LE2M:MINimum?.. 623
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:LE2M:MINimum?... 623
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:LRANge:
MINimum?.......................................................................................................... 624
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:LRANge:
MINimum?.......................................................................................................... 624
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:LRANge:
MINimum?.......................................................................................................... 624
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy[:LE1M]:
SDEViation?........................................................................................................625
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy[:LE1M]:
SDEViation?........................................................................................................625
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy[:LE1M]:
SDEViation?........................................................................................................625
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:LE2M:
SDEViation?........................................................................................................626
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:LE2M:
SDEViation?........................................................................................................626
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:LE2M:
SDEViation?........................................................................................................626
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:LRANge:
SDEViation?........................................................................................................627
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:LRANge:
SDEViation?........................................................................................................627
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:LRANge:
SDEViation?........................................................................................................627
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:CLASsic:
CURRent?
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:CLASsic:
AVERage?
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:CLASsic:
XMINimum?
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:CLASsic:
XMAXimum?
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:CLASsic:
MAXimum?
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:CLASsic:
CURRent?
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:CLASsic:
AVERage?
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:CLASsic:
XMINimum?
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:CLASsic:
XMAXimum?
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:CLASsic:
MAXimum?
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:CLASsic:
CURRent?
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:CLASsic:
AVERage?
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:CLASsic:
XMINimum?
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:CLASsic:
XMAXimum?
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:CLASsic:
MAXimum?
Returns the current, average, xmin, xmax, and max modulation results for BR/EDR,
normal mode, see Chapter 7.4.2.17, "LE: Statistical Modulation Results ", on page 410.
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:CLASsic:
SDEViation?
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:CLASsic:
SDEViation?
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:CLASsic:
SDEViation?
Returns standard deviation modulation results for BR/EDR, normal mode, see Chap-
ter 7.4.2.17, "LE: Statistical Modulation Results ", on page 410.
An R&S CMW100/CMW with MUA returns all results.
An R&S CMW500/2xx with BB Meas returns only three values: results 1 to 3.
The values described below are returned by FETCh and READ commands. CALCulate
commands return limit check results instead, one value for each result listed below.
Return values:
<1_Reliability> decimal
See Reliability Indicator
<2_OutOfTol> float
Out of tolerance result, i.e. percentage of measurement intervals
of the statistic count (CONFigure:BLUetooth:MEAS<i>:
MEValuation:SCOunt:MODulation) exceeding the specified
limits, see Limits (Modulation BR) and Limits (Modulation EDR).
Range: 0 % to 100 %
<3_FreqAccuracy> float
Range: -0.99999E+6 Hz to 0.99999E+6 Hz
<4_FreqDrift> float
Range: -0.99999E+6 Hz to 0.99999E+6 Hz
<5_MaxDriftRate> float
Range: -0.99999E+6 Hz to 0.99999E+6 Hz
Default unit: Hz/50 μs
Example: See Performing PvT and Modulation Measurements
Usage: Query only
Firmware/Software: V3.7.40
Options: R&S CMW-KM610
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy[:
LE1M]:CURRent?
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy[:
LE1M]:AVERage?
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy[:
LE1M]:XMINimum?
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy[:
LE1M]:XMAXimum?
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy[:
LE1M]:MAXimum?
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy[:LE1M]:
CURRent?
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy[:LE1M]:
AVERage?
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy[:LE1M]:
XMINimum?
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy[:LE1M]:
XMAXimum?
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy[:LE1M]:
MAXimum?
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:LE2M:
CURRent?
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy[:LE1M]:
CURRent?
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy[:LE1M]:
AVERage?
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy[:LE1M]:
XMINimum?
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy[:LE1M]:
XMAXimum?
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy[:LE1M]:
MAXimum?
Returns the current, average, xmin, xmax, and maximum modulation results for LE 1M
PHY in normal mode, see Chapter 7.4.2.17, "LE: Statistical Modulation Results ",
on page 410.
The values described below are returned by FETCh and READ commands. CALCulate
commands return limit check results instead, one value for each result listed below.
Return values:
<1_Reliability> decimal
See Reliability Indicator
<2_OutOfTol> float
Out of tolerance result, i.e. percentage of measurement intervals
of the statistic count (CONFigure:BLUetooth:MEAS<i>:
MEValuation:SCOunt:MODulation) exceeding the specified
limits, see Limits (Modulation LE).
Range: 0 % to 100 %
<3_FreqAccuracy> float
Default unit: Hz
<4_FreqOffset> float
Default unit: Hz
<5_FreqDrift> float
Default unit: Hz
<6_InitialFreqDrift> float
Default unit: Hz
<7_MaxDriftRate> float
Default unit: Hz/50 μs
<8_Δf1 Avg> float
Frequency deviation results
Default unit: Hz
<9_Δf1 Min> float
Default unit: Hz
<10_Δf1 Max> float
Default unit: Hz
<11_Δf2 Avg> float
Default unit: Hz
<12_Δf2 Min> float
Default unit: Hz
<13_Δf2 Max> float
Default unit: Hz
Example: See Performing PvT and Modulation Measurements
Usage: Query only
Firmware/Software: V3.7.61
Options: R&S CMW-KM611
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:
LE2M:CURRent?
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:
LE2M:AVERage?
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:
LE2M:XMINimum?
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:
LE2M:XMAXimum?
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:
LE2M:MAXimum?
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:LE2M:
CURRent?
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:LE2M:
AVERage?
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:LE2M:
XMINimum?
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:LE2M:
XMAXimum?
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:LE2M:
MAXimum?
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:LE2M:
AVERage?
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:LE2M:
XMINimum?
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:LE2M:
XMAXimum?
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:LE2M:
MAXimum?
Returns the current, average, xmin, xmax, and maximum modulation results for LE 2M
PHY in normal mode, see Chapter 7.4.2.17, "LE: Statistical Modulation Results ",
on page 410.
The values described below are returned by FETCh and READ commands. CALCulate
commands return limit check results instead, one value for each result listed below.
Return values:
<1_Reliability> decimal
See Reliability Indicator
<2_OutOfTol> float
Out of tolerance result, i.e. percentage of measurement intervals
of the statistic count (CONFigure:BLUetooth:MEAS<i>:
MEValuation:SCOunt:MODulation) exceeding the specified
limits, see Limits (Modulation LE).
Range: 0 % to 100 %
<3_Δf2 99.9%> float
Range: -4E+6 Hz to 4E+6 Hz
<4_FreqAccuracy> float
Default unit: Hz
<5_FreqDrift> float
Default unit: Hz
<6_MaxDriftRate> float
Default unit: Hz/50 μs
<7_Δf1 Avg> Frequency deviation results
Default unit: Hz
<8_Δf1 Min> float
Default unit: Hz
<9_Δf1 Max> float
Default unit: Hz
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:
LRANge:CURRent?
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:
LRANge:AVERage?
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:
LRANge:XMINimum?
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:
LRANge:XMAXimum?
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:
LRANge:MAXimum?
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:
LRANge:CURRent?
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:
LRANge:AVERage?
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:
LRANge:XMINimum?
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:
LRANge:XMAXimum?
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:
LRANge:MAXimum?
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:LRANge:
CURRent?
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:LRANge:
AVERage?
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:LRANge:
XMINimum?
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:LRANge:
XMAXimum?
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:LRANge:
MAXimum?
Returns the current, average, xmin, xmax, and maximum modulation results for LE
coded PHY in normal mode, see Chapter 7.4.2.17, "LE: Statistical Modulation Results
", on page 410.
The values described below are returned by FETCh and READ commands. CALCulate
commands return limit check results instead, one value for each result listed below.
Return values:
<1_Reliability> decimal
See Reliability Indicator
<2_OutOfTol> float
Out of tolerance result, i.e. percentage of measurement intervals
of the statistic count (CONFigure:BLUetooth:MEAS<i>:
MEValuation:SCOunt:MODulation) exceeding the specified
limits, see Limits (Modulation LE).
Range: 0 % to 100 %
<3_Δf1 99.9%> float
Range: -4E+6 Hz to 4E+6 Hz
<4_FreqAccuracy> float
Default unit: Hz
<5_FreqDrift> float
Default unit: Hz
<6_MaxDriftRate> float
Default unit: Hz/50 μs
<7_Δf1 Avg> Frequency deviation results
Default unit: Hz
<8_Δf1 Min> float
Default unit: Hz
<9_Δf1 Max> float
Default unit: Hz
<10_Nominal Pow> float
Range: -99.99 dBm to 99.99 dBm
<11_Freq. Offset> float
Range: -0.99999E+6 Hz to 0.99999E+6 Hz
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy[:
LE1M]:MINimum?
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy[:LE1M]:
MINimum?
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy[:LE1M]:
MINimum?
Returns the minimum modulation results for LE 1M PHY in normal mode, see Chap-
ter 7.4.2.17, "LE: Statistical Modulation Results ", on page 410.
The values described below are returned by FETCh and READ commands. CALCulate
commands return limit check results instead, one value for each result listed below.
Return values:
<1_Reliability> decimal
See Reliability Indicator
<2_OutOfTol> float
Out of tolerance result, i.e. percentage of measurement intervals
of the statistic count (CONFigure:BLUetooth:MEAS<i>:
MEValuation:SCOunt:MODulation) exceeding the specified
limits, see Limits (Modulation LE).
Range: 0 % to 100 %
<3_Δf1 Avg> float
Frequency deviation results
Default unit: Hz
<4_Δf1 Min> float
Default unit: Hz
<5_Δf1 Max> float
Default unit: Hz
<6_Δf2 Avg> float
Default unit: Hz
<7_Δf2 Min> float
Default unit: Hz
<8_Δf2 Max> float
Default unit: Hz
Example: See Performing PvT and Modulation Measurements
Usage: Query only
Firmware/Software: V3.7.61
Options: R&S CMW-KM611
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:
LE2M:MINimum?
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:LE2M:
MINimum?
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:LE2M:
MINimum?
Returns the minimum modulation results for LE 2M PHY in normal mode, see Chap-
ter 7.4.2.17, "LE: Statistical Modulation Results ", on page 410.
The values described below are returned by FETCh and READ commands. CALCulate
commands return limit check results instead, one value for each result listed below.
Return values:
<1_Reliability> decimal
See Reliability Indicator
<2_OutOfTol> float
Out of tolerance result, i.e. percentage of measurement intervals
of the statistic count (CONFigure:BLUetooth:MEAS<i>:
MEValuation:SCOunt:MODulation) exceeding the specified
limits, see Limits (Modulation LE).
Range: 0 % to 100 %
<3_Δf2 99.9%> float
Range: -0.99999E+6 Hz to 0.99999E+6 Hz
<4_Δf1 Avg> Frequency deviation results
Default unit: Hz
<5_Δf1 Min> float
Default unit: Hz
<6_Δf1 Max> float
Default unit: Hz
<7_Δf2 Avg> float
Default unit: Hz
<8_Δf2 Min> float
Default unit: Hz
<9_Δf2 Max> float
Default unit: Hz
<10_Nominal Pow> float
Range: -99.99 dBm to 99.99 dBm
<11_ModRatio> float
Range: 0 to 1
Example: See Performing PvT and Modulation Measurements
Usage: Query only
Firmware/Software: V3.7.80
Options: R&S CMW-KM721
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:
LRANge:MINimum?
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:
LRANge:MINimum?
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:LRANge:
MINimum?
Returns the minimum modulation results for LE coded PHY in normal mode, see Chap-
ter 7.4.2.17, "LE: Statistical Modulation Results ", on page 410.
The values described below are returned by FETCh and READ commands. CALCulate
commands return limit check results instead, one value for each result listed below.
Return values:
<1_Reliability> decimal
See Reliability Indicator
<2_OutOfTol> float
Out of tolerance result, i.e. percentage of measurement intervals
of the statistic count (CONFigure:BLUetooth:MEAS<i>:
MEValuation:SCOunt:MODulation) exceeding the specified
limits, see Limits (Modulation LE).
Range: 0 % to 100 %
<3_Δf1 99.9%> float
Range: -0.99999E+6 Hz to 0.99999E+6 Hz
<4_Δf1 Avg> float
Frequency deviation results
Default unit: Hz
<5_Δf1 Min> float
Default unit: Hz
<6_Δf1 Max> float
Default unit: Hz
<7_Nominal Pow> float
Range: -99.99 dBm to 99.99 dBm
Example: See Performing PvT and Modulation Measurements
Usage: Query only
Firmware/Software: V3.7.80
Options: R&S CMW-KM721
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy[:
LE1M]:SDEViation?
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy[:LE1M]:
SDEViation?
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy[:LE1M]:
SDEViation?
Returns the standard deviation modulation results for LE 1M PHY in normal mode, see
Chapter 7.4.2.17, "LE: Statistical Modulation Results ", on page 410.
The values described below are returned by FETCh and READ commands. CALCulate
commands return limit check results instead, one value for each result listed below.
Return values:
<1_Reliability> decimal
See Reliability Indicator
<2_OutOfTol> float
Out of tolerance result, i.e. percentage of measurement intervals
of the statistic count (CONFigure:BLUetooth:MEAS<i>:
MEValuation:SCOunt:MODulation) exceeding the specified
limits, see Limits (Modulation LE).
Range: 0 % to 100 %
Default unit: %
<3_FreqAccuracy> float
Range: -0.99999E+6 Hz to 0.99999E+6 Hz
Default unit: Hz
<4_FreqDrift> float
Range: -0.99999E+6 Hz to 0.99999E+6 Hz
<5_MaxDriftRate> float
Range: -0.99999E+6 Hz to 0.99999E+6 Hz
Default unit: Hz/50 μs
Example: See Performing PvT and Modulation Measurements
Usage: Query only
Firmware/Software: V3.7.61
Options: R&S CMW-KM611
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:
LE2M:SDEViation?
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:LE2M:
SDEViation?
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:LE2M:
SDEViation?
Returns the standard deviation modulation results for LE 2M PHY in normal mode, see
Chapter 7.4.2.17, "LE: Statistical Modulation Results ", on page 410.
The values described below are returned by FETCh and READ commands. CALCulate
commands return limit check results instead, one value for each result listed below.
Return values:
<1_Reliability> decimal
See Reliability Indicator
<2_OutOfTol> float
Out of tolerance result, i.e. percentage of measurement intervals
of the statistic count (CONFigure:BLUetooth:MEAS<i>:
MEValuation:SCOunt:MODulation) exceeding the specified
limits, see Limits (Modulation LE).
Range: 0 % to 100 %
Default unit: %
<3_Δf2 99.9%> float
Range: -0.99999E+6 Hz to 0.99999E+6 Hz
<4_Freq.Accuracy> float
Range: -0.99999E+6 Hz to 0.99999E+6 Hz
Default unit: Hz
<5_FreqDrift> float
Range: -0.99999E+6 Hz to 0.99999E+6 Hz
<6_MaxDriftRate> float
Range: -0.99999E+6 Hz to 0.99999E+6 Hz
Default unit: Hz/50 μs
<7_NominalPower> float
Range: -99.99 dBm to 99.99 dBm
<8_ModRatio> float
Range: 0 to 1
<9_Freq. Offset> float
Range: -0.99999E+6 Hz to 0.99999E+6 Hz
<10_Initial Freq.Drift> float
Range: -0.99999E+6 Hz to 0.99999E+6 Hz
Example: See Performing PvT and Modulation Measurements
Usage: Query only
Firmware/Software: V3.7.80
Options: R&S CMW-KM721
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:
LRANge:SDEViation?
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:
LRANge:SDEViation?
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:LRANge:
SDEViation?
Returns the standard deviation modulation results for LE coded PHY in normal mode,
see Chapter 7.4.2.17, "LE: Statistical Modulation Results ", on page 410.
The values described below are returned by FETCh and READ commands. CALCulate
commands return limit check results instead, one value for each result listed below.
Return values:
<1_Reliability> decimal
See Reliability Indicator
<2_OutOfTol> float
Out of tolerance result, i.e. percentage of measurement intervals
of the statistic count (CONFigure:BLUetooth:MEAS<i>:
MEValuation:SCOunt:MODulation) exceeding the specified
limits, see Limits (Modulation LE).
Range: 0 % to 100 %
Default unit: %
<3_Δf1 99.9%> float
Range: -0.99999E+6 Hz to 0.99999E+6 Hz
<4_Freq.Accuracy> float
Range: -0.99999E+6 Hz to 0.99999E+6 Hz
Default unit: Hz
<5_FreqDrift> float
Range: -0.99999E+6 Hz to 0.99999E+6 Hz
<6_MaxDriftRate> float
Range: -0.99999E+6 Hz to 0.99999E+6 Hz
Default unit: Hz/50 μs
<7_NominalPower> float
Range: -99.99 dBm to 99.99 dBm
<8_Freq. Offset> float
Range: -0.99999E+6 Hz to 0.99999E+6 Hz
Example: See Performing PvT and Modulation Measurements
Usage: Query only
Firmware/Software: V3.7.80
The following commands return the spectrum results (single values) for BR packets.
CALCulate:BLUetooth:MEAS<i>:MEValuation:SOBW:BRATe:MAXimum?............................628
FETCh:BLUetooth:MEAS<i>:MEValuation:SOBW:BRATe:MAXimum?................................. 628
READ:BLUetooth:MEAS<i>:MEValuation:SOBW:BRATe:MAXimum?.................................. 628
CALCulate:BLUetooth:MEAS<i>:MEValuation:SACP:BRATe[:PTX]?....................................629
FETCh:BLUetooth:MEAS<i>:MEValuation:SACP:BRATe[:PTX]?......................................... 629
READ:BLUetooth:MEAS<i>:MEValuation:SACP:BRATe[:PTX]?.......................................... 629
CALCulate:BLUetooth:MEAS<i>:MEValuation:FRANge:BRATe:CURRent?.......................... 630
FETCh:BLUetooth:MEAS<i>:MEValuation:FRANge:BRATe:CURRent?................................630
READ:BLUetooth:MEAS<i>:MEValuation:FRANge:BRATe:CURRent?.................................630
CALCulate:BLUetooth:MEAS<i>:MEValuation:SOBW:BRATe:MAXimum?
FETCh:BLUetooth:MEAS<i>:MEValuation:SOBW:BRATe:MAXimum?
READ:BLUetooth:MEAS<i>:MEValuation:SOBW:BRATe:MAXimum?
Returns the "Spectrum 20 dB Bandwidth" results.
The values described below are returned by FETCh and READ commands. CALCulate
commands return limit check results instead, one value for each result listed below.
Return values:
<1_Reliability> decimal
Reliability Indicator
<2_Out of Tol> float | ON | OFF
Out of tolerance result, i.e. percentage of measurement intervals
of the statistic count (CONFigure:BLUetooth:MEAS<i>:
MEValuation:LIMit:SOBW) exceeding the specified limits.
Range: 0 % to 100 %
Default unit: %
<3_Nominal Pow> float
Average power during the carrier-on state
Range: -99.99 dBm to 99.99 dBm
Default unit: dBm
<4_Peak Emission> float
Peak power in the measured spectral range
Range: -99.99 dBm to 99.99 dBm
Default unit: dBm
<5_fL> float
Lower frequency where the transmit power drops 20 dB below
the peak emission
Range: -0.99999E+6 MHz to 0.99999E+6 MHz
Default unit: Hz
<6_fH> float
Higher frequency where the transmit power drops 20 dB below
the peak emission
Range: -0.99999E+6 MHz to 0.99999E+6 MHz
<7_fH - fL> float
20 dB bandwidth; difference between fH – fL.
Range: -0.99999E+6 MHz to 0.99999E+6 MHz
Default unit: Hz
Example: See Performing Spectrum Measurements
Usage: Query only
Firmware/Software: V1.0.15.20
CALCulate:BLUetooth:MEAS<i>:MEValuation:SACP:BRATe[:PTX]?
FETCh:BLUetooth:MEAS<i>:MEValuation:SACP:BRATe[:PTX]?
READ:BLUetooth:MEAS<i>:MEValuation:SACP:BRATe[:PTX]?
Returns the "Spectrum ACP" results for BR packets.
The values described below are returned by FETCh and READ commands. CALCulate
commands return limit check results instead, one value for each result listed below.
The number of valid ACP results depends on the ACP measurement mode
(CONFigure:BLUetooth:MEAS<i>:MEValuation:SACP:BRATe:MEASurement:
MODE CH21 | CH79):
● If "ACP +/- 10 Channels" is selected, the first 21 ACP values contain the results for
the relative channels –10, ..., 0, ..., +10; the remaining 58 values are not displayed.
● If "ACP 79 Channels" is selected, valid ACP values are available for all channels in
the Bluetooth regulatory range.
Return values:
<1_Reliability> decimal
Reliability Indicator
<2_Out of Tol> float
Out of tolerance result, i.e. percentage of measurement intervals
of the statistic count (CONFigure:BLUetooth:MEAS<i>:
MEValuation:SCOunt:SACP) exceeding the specified limits.
Range: 0 % to 100 %
Default unit: %
<3_Nominal Pow> float
Average power during the carrier-on state
Range: -99.99 dBm to 99.99 dBm
Default unit: dBm
CALCulate:BLUetooth:MEAS<i>:MEValuation:FRANge:BRATe:CURRent?
FETCh:BLUetooth:MEAS<i>:MEValuation:FRANge:BRATe:CURRent?
READ:BLUetooth:MEAS<i>:MEValuation:FRANge:BRATe:CURRent?
Returns the "Frequency Range" results for BR.
The values described below are returned by FETCh and READ commands. CALCulate
commands return limit check results instead, one value for each result listed below.
Return values:
<Reliability> decimal
Reliability Indicator
<BurstOutOfTol> float | ON | OFF
Out of tolerance result, i.e. percentage of measurement intervals
of the statistic count (CONFigure:BLUetooth:MEAS<i>:
MEValuation:SCOunt:FRANge) exceeding the specified lim-
its, see CONFigure:BLUetooth:MEAS<i>:MEValuation:
LIMit:FRANge.
Additional ON/OFF enables/disables the out of tolerance evalua-
tion.
Range: 0 % to 100 %
<NominalPower> float
Average power during the carrier-on state
Range: -128 dBm to 30 dBm
<fL> float
Lowest frequency at which spectral power density drops below
specified threshold
Range: -1 MHz to +1 MHz
<fH> float
Highest frequency at which spectral power density drops below
specified threshold
Range: -1 MHz to +1 MHz
Example: See Performing Spectrum Measurements
Usage: Query only
Firmware/Software: V3.2.50
The following commands return the spectrum results (single values) for EDR packets.
CALCulate:BLUetooth:MEAS<i>:MEValuation:SGACp:EDRate[:PTX]?
FETCh:BLUetooth:MEAS<i>:MEValuation:SGACp:EDRate[:PTX]?
READ:BLUetooth:MEAS<i>:MEValuation:SGACp:EDRate[:PTX]?
Returns the "Spectrum Gated ACP" results for EDR packets (single values).
The values described below are returned by FETCh and READ commands. CALCulate
commands return limit check results instead, one value for each result listed below.
Return values:
<1_Reliability> decimal
Reliability Indicator
<2_Out of Tol> float
Out of tolerance result, i.e. percentage of measurement intervals
of the statistic count (CONFigure:BLUetooth:MEAS<i>:
MEValuation:SCOunt:SGACp) exceeding the specified limits.
Range: 0 % to 100 %
Default unit: %
<3_Nominal Pow> float
Average power during the carrier-on state
Range: -99.99 dBm to 99.99 dBm
Default unit: dBm
<4_No of Except> decimal
Number of exceptions (channels ±3, ±4 ... with an ACP above
the "Exception PTx" threshold )
Range: 0 to 99
<5_PTxRef> float
Reference power PTXref, measured in the center channel
Range: -99.99 dBm to 99.99 dBm
Default unit: dBm
<6_N26ChN1Abs> float
Absolute PTX – 26 dB value for channel –1, maximum value
Range: -99.99 dBm to 99.99 dBm
Default unit: dBm
<7_N26ChP1Abs> float
Absolute PTX – 26 dB value for channel +1, maximum value
Range: -99.99 dBm to 99.99 dBm
Default unit: dBm
<8_N26ChN1Rel> float
Relative PTX – 26 dB value for channel –1, maximum value
Range: -99.99 dBW to 99.99 dBW
Default unit: dBW
<9_N26ChP1Rel> float
Relative PTX – 26 dB value for channel +1, maximum value
Range: -99.99 dBW to 99.99 dBW
Default unit: dBW
Example: See Performing Spectrum Measurements
Usage: Query only
Firmware/Software: V2.0.20, V3.7.51: added token [:PTX]
CALCulate:BLUetooth:MEAS<i>:MEValuation:SACP:LENergy[:LE1M]?
FETCh:BLUetooth:MEAS<i>:MEValuation:SACP:LENergy[:LE1M]?
READ:BLUetooth:MEAS<i>:MEValuation:SACP:LENergy[:LE1M]?
Returns the "Spectrum ACP" results for LE1M, see Chapter 7.4.2.18, "LE: Spectrum
ACP Results ", on page 415.
The values described below are returned by FETCh and READ commands. CALCulate
commands return limit check results instead, one value for each result listed below.
Return values:
<Reliability> decimal
Reliability Indicator
<NominalPower> float
Average power during the carrier-on state
Range: -99.99 dBm to 99.99 dBm
<NoOfExceptions> decimal
Number of exceptions (channels ±3, ±4 ... with an ACP above
the "Exception PTx" threshold )
Range: 0 to 99
Usage: Query only
Firmware/Software: V2.1.20
Options: R&S CMW-KM611
CALCulate:BLUetooth:MEAS<i>:MEValuation:SACP:LENergy:LRANge?
FETCh:BLUetooth:MEAS<i>:MEValuation:SACP:LENergy:LRANge?
READ:BLUetooth:MEAS<i>:MEValuation:SACP:LENergy:LRANge?
CALCulate:BLUetooth:MEAS<i>:MEValuation:SACP:LENergy:LE2M?
FETCh:BLUetooth:MEAS<i>:MEValuation:SACP:LENergy:LE2M?
READ:BLUetooth:MEAS<i>:MEValuation:SACP:LENergy:LE2M?
Returns the "Spectrum ACP" results for LE 2M PHY (...:LE2M...) and LE coded
PHY (...:LRANge...), see Chapter 7.4.2.18, "LE: Spectrum ACP Results ",
on page 415.
The values described below are returned by FETCh and READ commands. CALCulate
commands return limit check results instead, one value for each result listed below.
Return values:
<Reliability> decimal
Reliability Indicator
<NominalPower> float
Average power during the carrier-on state
Range: -99.99 dBm to 99.99 dBm
<NoOfExceptions> decimal
Number of exceptions (channels ±3, ±4 ... with an ACP above
the "Exception PTx" threshold )
Range: 0 to 99
Usage: Query only
Firmware/Software: V3.5.70
Options: R&S CMW-KM721
The following commands return the spectrum results (single values) in normal mode.
Commands for normal mode with BR/EDR (..:NMODe:CLASsic..) and LE
(..:NMODe:LENenergy..) are available.
LE commands support uncoded LE 1M PHY (..:NMODe:LEN:LE1M:..), LE 2M PHY
(..:NMODe:LEN:LE2M:..), and LE coded PHY (..:NMODe:LEN:LRANge..).
Measurements in normal mode are only supported in combined signal path, see Chap-
ter 7.2.1.3, "Parallel Signaling and Measurement", on page 332.
CALCulate:BLUetooth:MEAS<i>:MEValuation:SACP:NMODe:CLASsic?............................. 634
FETCh:BLUetooth:MEAS<i>:MEValuation:SACP:NMODe:CLASsic?...................................634
READ:BLUetooth:MEAS<i>:MEValuation:SACP:NMODe:CLASsic?.................................... 634
CALCulate:BLUetooth:MEAS<i>:MEValuation:SACP:NMODe:LENergy:LE2M?....................635
CALCulate:BLUetooth:MEAS<i>:MEValuation:SACP:NMODe:LENergy:LRANge?................ 635
CALCulate:BLUetooth:MEAS<i>:MEValuation:SACP:NMODe:LENergy[:LE1M]?.................. 635
FETCh:BLUetooth:MEAS<i>:MEValuation:SACP:NMODe:LENergy:LE2M?......................... 635
FETCh:BLUetooth:MEAS<i>:MEValuation:SACP:NMODe:LENergy:LRANge?..................... 635
FETCh:BLUetooth:MEAS<i>:MEValuation:SACP:NMODe:LENergy[:LE1M]?....................... 635
READ:BLUetooth:MEAS<i>:MEValuation:SACP:NMODe:LENergy:LE2M?.......................... 635
READ:BLUetooth:MEAS<i>:MEValuation:SACP:NMODe:LENergy:LRANge?.......................635
READ:BLUetooth:MEAS<i>:MEValuation:SACP:NMODe:LENergy[:LE1M]?.........................635
CALCulate:BLUetooth:MEAS<i>:MEValuation:SACP:NMODe:CLASsic?
FETCh:BLUetooth:MEAS<i>:MEValuation:SACP:NMODe:CLASsic?
READ:BLUetooth:MEAS<i>:MEValuation:SACP:NMODe:CLASsic?
Returns the "Spectrum ACP" results for normal mode classic.
The values described below are returned by FETCh and READ commands. CALCulate
commands return limit check results instead, one value for each result listed below.
Return values:
<1_Reliability> decimal
Reliability Indicator
<2_Out of Tol> float
Out of tolerance result, i.e. percentage of measurement intervals
of the statistic count (CONFigure:BLUetooth:MEAS<i>:
MEValuation:SCOunt:SACP) exceeding the specified BR lim-
its, see "ACP (BR, LE)" on page 462.
Range: 0 % to 100 %
<3_Nominal Pow> float
Average power during the carrier-on state
Range: -99.99 dBm to 99.99 dBm
CALCulate:BLUetooth:MEAS<i>:MEValuation:SACP:NMODe:LENergy:LE2M?
CALCulate:BLUetooth:MEAS<i>:MEValuation:SACP:NMODe:LENergy:LRANge?
CALCulate:BLUetooth:MEAS<i>:MEValuation:SACP:NMODe:LENergy[:LE1M]?
FETCh:BLUetooth:MEAS<i>:MEValuation:SACP:NMODe:LENergy:LE2M?
FETCh:BLUetooth:MEAS<i>:MEValuation:SACP:NMODe:LENergy:LRANge?
FETCh:BLUetooth:MEAS<i>:MEValuation:SACP:NMODe:LENergy[:LE1M]?
READ:BLUetooth:MEAS<i>:MEValuation:SACP:NMODe:LENergy:LE2M?
READ:BLUetooth:MEAS<i>:MEValuation:SACP:NMODe:LENergy:LRANge?
READ:BLUetooth:MEAS<i>:MEValuation:SACP:NMODe:LENergy[:LE1M]?
Returns the "Spectrum ACP" results for LE normal mode, see Chapter 7.4.2.18, "LE:
Spectrum ACP Results ", on page 415.
Commands for uncoded LE 1M PHY (..:LE1M..), LE 2M PHY (..:LE2M..), and LE
coded PHY (..:LRANge..) are available.
The values described below are returned by FETCh and READ commands. CALCulate
commands return limit check results instead, one value for each result listed below.
Return values:
<Reliability> decimal
Reliability Indicator
<NominalPower> float
Average power during the carrier-on state
Range: -128.0 dBm to +30.0 dBm
Default unit: dBm
<NoOfExceptions> decimal
Number of exceptions (channels ±3, ±4 ... with an ACP above
the "Exception PTx" threshold )
Range: 0 to 99
Usage: Query only
Firmware/Software: V3.7.61, V3.7.80: added LE2M and LRANge commands
Options: R&S CMW-KM611
Plus R&S CMW-KM721 for LE2M and LRANge
The following commands return the phase encoding results (single values) for EDR
packets.
CALCulate:BLUetooth:MEAS<i>:MEValuation:PENCoding:EDRate:CURRent?.................... 636
FETCh:BLUetooth:MEAS<i>:MEValuation:PENCoding:EDRate:CURRent:C?...................... 636
READ:BLUetooth:MEAS<i>:MEValuation:PENCoding:EDRate:CURRent?...........................636
CALCulate:BLUetooth:MEAS<i>:MEValuation:PENCoding:SSEQuence:EDRate:
CURRent?.......................................................................................................... 637
FETCh:BLUetooth:MEAS<i>:MEValuation:PENCoding:SSEQuence:EDRate:CURRent?.......637
READ:BLUetooth:MEAS<i>:MEValuation:PENCoding:SSEQuence:EDRate:CURRent?........ 637
CALCulate:BLUetooth:MEAS<i>:MEValuation:PENCoding:EDRate:CURRent?
FETCh:BLUetooth:MEAS<i>:MEValuation:PENCoding:EDRate:CURRent:C?
READ:BLUetooth:MEAS<i>:MEValuation:PENCoding:EDRate:CURRent?
Returns the "Differential Phase Encoding" results for EDR packets (single values).
The values described below are returned by FETCh and READ commands. CALCulate
commands return limit check results instead, one value for each result listed below.
Return values:
<Reliability> float
Reliability Indicator
<NominalPower> float
Average power during the carrier-on state
Range: -128 dBm to 30 dBm
Default unit: dBm
<BitErrorRate> float
Number of bit errors in the received burst, as a percentage of
the total number of bits received
Range: 0 % to 100 %
Default unit: %
<Packets0Errors> float
Number of bit error free packets received, as a percentage of all
the bursts received
Range: 0 % to 100 %
Default unit: %
Example: See Differential Phase Encoding Measurements
Usage: Query only
Firmware/Software: V3.2.50
V3.2.81: added command FETCh:...:CURRent:C
CALCulate:BLUetooth:MEAS<i>:MEValuation:PENCoding:SSEQuence:EDRate:
CURRent?
FETCh:BLUetooth:MEAS<i>:MEValuation:PENCoding:SSEQuence:EDRate:
CURRent?
READ:BLUetooth:MEAS<i>:MEValuation:PENCoding:SSEQuence:EDRate:
CURRent?
Returns the "Differential Phase Encoding" results for EDR packets in combined signal
path.
The values described below are returned by FETCh and READ commands. CALCulate
commands return limit check results instead, one value for each result listed below.
Return values:
<Reliability> decimal
Reliability Indicator
<NominalPower> float
Average burst power during the carrier-on state
Range: -99.99 dBm to 99.99 dBm
<SyncBitErrors> decimal
Sync bit errors
Range: 0 to 10E+3
<TrailerBitErrs> decimal
Trailer bit errors
Range: 0 to 10E+3
Example: See Differential Phase Encoding Measurements
Usage: Query only
Firmware/Software: V3.7.81
The following commands return the power trace results of the multi-evaluation mea-
surement. See also Calculation of Results.
Commands for power vs. time diagram (...:TRACe:PVTime:...), average power
vs. slot diagram (...:TRACe:SPOWer:...), and power vs. slot deviation diagram
(...:TRACe:PDEViation:...) are available.
FETCh:BLUetooth:MEAS<i>:MEValuation:TRACe:PVTime:CURRent?................................638
FETCh:BLUetooth:MEAS<i>:MEValuation:TRACe:PVTime:AVERage?................................638
FETCh:BLUetooth:MEAS<i>:MEValuation:TRACe:PVTime:MINimum?................................638
FETCh:BLUetooth:MEAS<i>:MEValuation:TRACe:PVTime:MAXimum?...............................638
READ:BLUetooth:MEAS<i>:MEValuation:TRACe:PVTime:CURRent?................................. 638
READ:BLUetooth:MEAS<i>:MEValuation:TRACe:PVTime:AVERage?................................. 638
READ:BLUetooth:MEAS<i>:MEValuation:TRACe:PVTime:MINimum?................................. 638
READ:BLUetooth:MEAS<i>:MEValuation:TRACe:PVTime:MAXimum?................................ 638
FETCh:BLUetooth:MEAS<i>:MEValuation:TRACe:SPOWer:CURRent?.............................. 638
FETCh:BLUetooth:MEAS<i>:MEValuation:TRACe:SPOWer:AVERage?.............................. 638
FETCh:BLUetooth:MEAS<i>:MEValuation:TRACe:SPOWer:MINimum?.............................. 638
FETCh:BLUetooth:MEAS<i>:MEValuation:TRACe:SPOWer:MAXimum?............................. 638
READ:BLUetooth:MEAS<i>:MEValuation:TRACe:SPOWer:CURRent?................................638
READ:BLUetooth:MEAS<i>:MEValuation:TRACe:SPOWer:AVERage?................................638
READ:BLUetooth:MEAS<i>:MEValuation:TRACe:SPOWer:MINimum?................................639
READ:BLUetooth:MEAS<i>:MEValuation:TRACe:SPOWer:MAXimum?...............................639
CALCulate:BLUetooth:MEAS<i>:MEValuation:TRACe:PDEViation:MINimum?..................... 639
CALCulate:BLUetooth:MEAS<i>:MEValuation:TRACe:PDEViation:MAXimum?.................... 639
FETCh:BLUetooth:MEAS<i>:MEValuation:TRACe:PDEViation:MINimum?...........................639
FETCh:BLUetooth:MEAS<i>:MEValuation:TRACe:PDEViation:MAXimum?..........................639
READ:BLUetooth:MEAS<i>:MEValuation:TRACe:PDEViation:MINimum?............................ 639
READ:BLUetooth:MEAS<i>:MEValuation:TRACe:PDEViation:MAXimum?...........................639
FETCh:BLUetooth:MEAS<i>:MEValuation:TRACe:PVTime:CURRent?
FETCh:BLUetooth:MEAS<i>:MEValuation:TRACe:PVTime:AVERage?
FETCh:BLUetooth:MEAS<i>:MEValuation:TRACe:PVTime:MINimum?
FETCh:BLUetooth:MEAS<i>:MEValuation:TRACe:PVTime:MAXimum?
READ:BLUetooth:MEAS<i>:MEValuation:TRACe:PVTime:CURRent?
READ:BLUetooth:MEAS<i>:MEValuation:TRACe:PVTime:AVERage?
READ:BLUetooth:MEAS<i>:MEValuation:TRACe:PVTime:MINimum?
READ:BLUetooth:MEAS<i>:MEValuation:TRACe:PVTime:MAXimum?
Returns the values of the power vs. time traces. The results of the current, average
minimum and maximum traces can be retrieved.
Return values:
<Reliability> decimal
Reliability Indicator
<PvT_1> ... <PvT_M> float
M power results, depending on the packet type and payload
length; see PvT and Freq. Dev. Trace Points (Classic), DEVM
Trace Points for Test Mode (EDR) and PvT and Modulation
Trace Points (LE).
Range: –128.0 dBm to 30.0 dBm
Default unit: dBm
Usage: Query only
Firmware/Software: V1.0.10.50
V2.1.20: support for LE bursts added
FETCh:BLUetooth:MEAS<i>:MEValuation:TRACe:SPOWer:CURRent?
FETCh:BLUetooth:MEAS<i>:MEValuation:TRACe:SPOWer:AVERage?
FETCh:BLUetooth:MEAS<i>:MEValuation:TRACe:SPOWer:MINimum?
FETCh:BLUetooth:MEAS<i>:MEValuation:TRACe:SPOWer:MAXimum?
READ:BLUetooth:MEAS<i>:MEValuation:TRACe:SPOWer:CURRent?
READ:BLUetooth:MEAS<i>:MEValuation:TRACe:SPOWer:AVERage?
READ:BLUetooth:MEAS<i>:MEValuation:TRACe:SPOWer:MINimum?
READ:BLUetooth:MEAS<i>:MEValuation:TRACe:SPOWer:MAXimum?
Returns the results of the power per CTE slot for LE CTE traces. The results of the cur-
rent, average, minimum and maximum traces can be retrieved.
Return values:
<Reliability> decimal
Reliability Indicator
<Power_S_1> float
<Power_S_149> 149 CTE slot power results for one reference slot (PDev_S_1)
and 148 switch / sample CTE slots. For unused CTE slots,
NCAP values are returned.
Range: -99.99 dBm to 99.99 dBm
Default unit: dBm
Usage: Query only
Firmware/Software: V3.7.70
Options: R&S CMW-KM722
CALCulate:BLUetooth:MEAS<i>:MEValuation:TRACe:PDEViation:MINimum?
CALCulate:BLUetooth:MEAS<i>:MEValuation:TRACe:PDEViation:MAXimum?
FETCh:BLUetooth:MEAS<i>:MEValuation:TRACe:PDEViation:MINimum?
FETCh:BLUetooth:MEAS<i>:MEValuation:TRACe:PDEViation:MAXimum?
READ:BLUetooth:MEAS<i>:MEValuation:TRACe:PDEViation:MINimum?
READ:BLUetooth:MEAS<i>:MEValuation:TRACe:PDEViation:MAXimum?
Returns the results of power deviation per slot for LE CTE traces. Deviation value is
calculated as peak to average power ratio. The results of the minimum and maximum
traces can be retrieved.
The values described below are returned by FETCh and READ commands. CALCulate
commands return limit check results instead, one value for each result listed below.
Return values:
<Reliability> decimal
Reliability Indicator
<PDev_S_1> float
<PDev_S_149> 149 slot power deviation results for one reference slot
(PDev_S_1) and 148 switch / sample CTE slots. For unused
CTE slots, NCAP values are returned.
Range: 0.01 to 1
Usage: Query only
Firmware/Software: V3.7.70, V3.7.81: added CALC commands
Options: R&S CMW-KM722
The following commands return the modulation trace results of the multi-evaluation
measurement. See also Calculation of Results.
FETCh:BLUetooth:MEAS<i>:MEValuation:TRACe:FDEViation:CURRent?...........................640
FETCh:BLUetooth:MEAS<i>:MEValuation:TRACe:FDEViation:AVERage?...........................640
FETCh:BLUetooth:MEAS<i>:MEValuation:TRACe:FDEViation:MINimum?...........................640
FETCh:BLUetooth:MEAS<i>:MEValuation:TRACe:FDEViation:MAXimum?..........................640
READ:BLUetooth:MEAS<i>:MEValuation:TRACe:FDEViation:CURRent?............................ 640
READ:BLUetooth:MEAS<i>:MEValuation:TRACe:FDEViation:AVERage?............................ 640
READ:BLUetooth:MEAS<i>:MEValuation:TRACe:FDEViation:MINimum?............................ 640
READ:BLUetooth:MEAS<i>:MEValuation:TRACe:FDEViation:MAXimum?........................... 640
FETCh:BLUetooth:MEAS<i>:MEValuation:TRACe:DEVMagnitude:CURRent?..................... 641
FETCh:BLUetooth:MEAS<i>:MEValuation:TRACe:DEVMagnitude:AVERage?..................... 641
FETCh:BLUetooth:MEAS<i>:MEValuation:TRACe:DEVMagnitude:MAXimum?.................... 641
READ:BLUetooth:MEAS<i>:MEValuation:TRACe:DEVMagnitude:CURRent?.......................641
READ:BLUetooth:MEAS<i>:MEValuation:TRACe:DEVMagnitude:AVERage?.......................641
READ:BLUetooth:MEAS<i>:MEValuation:TRACe:DEVMagnitude:MAXimum?......................641
FETCh:BLUetooth:MEAS<i>:MEValuation:TRACe:PDIFference:CURRent?......................... 641
FETCh:BLUetooth:MEAS<i>:MEValuation:TRACe:PDIFference:AVERage?......................... 641
FETCh:BLUetooth:MEAS<i>:MEValuation:TRACe:PDIFference:MAXimum?........................ 641
READ:BLUetooth:MEAS<i>:MEValuation:TRACe:PDIFference:CURRent?.......................... 641
READ:BLUetooth:MEAS<i>:MEValuation:TRACe:PDIFference:AVERage?.......................... 641
READ:BLUetooth:MEAS<i>:MEValuation:TRACe:PDIFference:MAXimum?......................... 641
FETCh:BLUetooth:MEAS<i>:MEValuation:TRACe:IQABs?.................................................642
FETCh:BLUetooth:MEAS<i>:MEValuation:TRACe:IQDiff?..................................................642
FETCh:BLUetooth:MEAS<i>:MEValuation:TRACe:IQERr?................................................. 642
READ:BLUetooth:MEAS<i>:MEValuation:TRACe:IQABs?..................................................642
READ:BLUetooth:MEAS<i>:MEValuation:TRACe:IQDiff?................................................... 642
READ:BLUetooth:MEAS<i>:MEValuation:TRACe:IQERr?.................................................. 642
FETCh:BLUetooth:MEAS<i>:MEValuation:TRACe:FDEViation:CURRent?
FETCh:BLUetooth:MEAS<i>:MEValuation:TRACe:FDEViation:AVERage?
FETCh:BLUetooth:MEAS<i>:MEValuation:TRACe:FDEViation:MINimum?
FETCh:BLUetooth:MEAS<i>:MEValuation:TRACe:FDEViation:MAXimum?
READ:BLUetooth:MEAS<i>:MEValuation:TRACe:FDEViation:CURRent?
READ:BLUetooth:MEAS<i>:MEValuation:TRACe:FDEViation:AVERage?
READ:BLUetooth:MEAS<i>:MEValuation:TRACe:FDEViation:MINimum?
READ:BLUetooth:MEAS<i>:MEValuation:TRACe:FDEViation:MAXimum?
Returns the values of the frequency deviation traces. The results of the current, aver-
age minimum and maximum traces can be retrieved. The frequency deviation traces
are available for BR and LE bursts (see CONFigure:BLUetooth:MEAS<i>:
ISIGnal:BTYPe).
Return values:
<Reliability> decimal
Reliability Indicator
FETCh:BLUetooth:MEAS<i>:MEValuation:TRACe:DEVMagnitude:CURRent?
FETCh:BLUetooth:MEAS<i>:MEValuation:TRACe:DEVMagnitude:AVERage?
FETCh:BLUetooth:MEAS<i>:MEValuation:TRACe:DEVMagnitude:MAXimum?
READ:BLUetooth:MEAS<i>:MEValuation:TRACe:DEVMagnitude:CURRent?
READ:BLUetooth:MEAS<i>:MEValuation:TRACe:DEVMagnitude:AVERage?
READ:BLUetooth:MEAS<i>:MEValuation:TRACe:DEVMagnitude:MAXimum?
Returns the values of the DEVM traces. The results of the current, average minimum
and maximum traces can be retrieved. The DEVM traces are available for EDR bursts
(CONFigure:BLUetooth:MEAS<i>:ISIGnal:BTYPe EDR).
Return values:
<Reliability> decimal
Reliability Indicator
<DEVM_1> ... float
<DEVM_m> m DEVM results, depending on the packet type and payload
length; see DEVM Trace Points for Test Mode (EDR).
Range: 0 % to 100 %
Default unit: %
Usage: Query only
Firmware/Software: V1.0.10.50
FETCh:BLUetooth:MEAS<i>:MEValuation:TRACe:PDIFference:CURRent?
FETCh:BLUetooth:MEAS<i>:MEValuation:TRACe:PDIFference:AVERage?
FETCh:BLUetooth:MEAS<i>:MEValuation:TRACe:PDIFference:MAXimum?
READ:BLUetooth:MEAS<i>:MEValuation:TRACe:PDIFference:CURRent?
READ:BLUetooth:MEAS<i>:MEValuation:TRACe:PDIFference:AVERage?
READ:BLUetooth:MEAS<i>:MEValuation:TRACe:PDIFference:MAXimum?
Returns the values of the phase difference traces. The results of the current, average
minimum and maximum traces can be retrieved. The phase difference traces are avail-
able for EDR bursts (CONFigure:BLUetooth:MEAS<i>:ISIGnal:BTYPe EDR).
Return values:
<Reliability> decimal
Reliability Indicator
FETCh:BLUetooth:MEAS<i>:MEValuation:TRACe:IQABs?
FETCh:BLUetooth:MEAS<i>:MEValuation:TRACe:IQDiff?
FETCh:BLUetooth:MEAS<i>:MEValuation:TRACe:IQERr?
READ:BLUetooth:MEAS<i>:MEValuation:TRACe:IQABs?
READ:BLUetooth:MEAS<i>:MEValuation:TRACe:IQDiff?
READ:BLUetooth:MEAS<i>:MEValuation:TRACe:IQERr?
Returns the values of the traces in the I/Q constellation diagrams. The mnemonics
IQABs, IQDiff, and IQERr denote the absolute, differential and I/Q constellation
error results. The I/Q traces are available for EDR packets (CONFigure:BLUetooth:
MEAS<i>:ISIGnal:BTYPe EDR).
Return values:
<Reliability> decimal
Reliability Indicator
<IPhase_1> float
<QPhase_1> ... m in-phase amplitudes (IPhase) and m quadrature-phase
(QPhase) amplitudes, where m is equal to the number of pro-
cessed 50-symbol blocks; see Trace Points for IQ Constellation
Diagrams (EDR).
Range: -2 to 2
*RST: 1
<IPhase_m> float
<QPhase_m>
Usage: Query only
Firmware/Software: V1.0.10.50
The following commands return the spectrum trace results of the multi-evaluation mea-
surement. See also Calculation of Results.
FETCh:BLUetooth:MEAS<i>:MEValuation:TRACe:SOBW:CURRent?................................. 643
FETCh:BLUetooth:MEAS<i>:MEValuation:TRACe:SOBW:AVERage?................................. 643
FETCh:BLUetooth:MEAS<i>:MEValuation:TRACe:SOBW:MAXimum?................................ 643
READ:BLUetooth:MEAS<i>:MEValuation:TRACe:SOBW:CURRent?...................................643
READ:BLUetooth:MEAS<i>:MEValuation:TRACe:SOBW:AVERage?.................................. 643
READ:BLUetooth:MEAS<i>:MEValuation:TRACe:SOBW:MAXimum?..................................643
FETCh:BLUetooth:MEAS<i>:MEValuation:TRACe:FRANge:AVERage?...............................644
READ:BLUetooth:MEAS<i>:MEValuation:TRACe:FRANge:AVERage?................................ 644
FETCh:BLUetooth:MEAS<i>:MEValuation:TRACe:SACP[:PTX]?........................................ 644
READ:BLUetooth:MEAS<i>:MEValuation:TRACe:SACP[:PTX]?......................................... 644
FETCh:BLUetooth:MEAS<i>:MEValuation:TRACe:SGACp[:PTX]?...................................... 645
READ:BLUetooth:MEAS<i>:MEValuation:TRACe:SGACp[:PTX]?....................................... 645
FETCh:BLUetooth:MEAS<i>:MEValuation:TRACe:SACP:CURRent?.................................. 645
FETCh:BLUetooth:MEAS<i>:MEValuation:TRACe:SACP:AVERage?.................................. 645
FETCh:BLUetooth:MEAS<i>:MEValuation:TRACe:SACP:MAXimum?................................. 645
READ:BLUetooth:MEAS<i>:MEValuation:TRACe:SACP:CURRent?....................................645
READ:BLUetooth:MEAS<i>:MEValuation:TRACe:SACP:AVERage?....................................646
READ:BLUetooth:MEAS<i>:MEValuation:TRACe:SACP:MAXimum?...................................646
FETCh:BLUetooth:MEAS<i>:MEValuation:TRACe:SGACp:CURRent?................................ 646
FETCh:BLUetooth:MEAS<i>:MEValuation:TRACe:SGACp:AVERage?................................ 646
FETCh:BLUetooth:MEAS<i>:MEValuation:TRACe:SGACp:MAXimum?............................... 646
READ:BLUetooth:MEAS<i>:MEValuation:TRACe:SGACp:CURRent?................................. 646
READ:BLUetooth:MEAS<i>:MEValuation:TRACe:SGACp:AVERage?................................. 647
READ:BLUetooth:MEAS<i>:MEValuation:TRACe:SGACp:MAXimum?................................ 647
FETCh:BLUetooth:MEAS<i>:MEValuation:TRACe:SOBW:CURRent?
FETCh:BLUetooth:MEAS<i>:MEValuation:TRACe:SOBW:AVERage?
FETCh:BLUetooth:MEAS<i>:MEValuation:TRACe:SOBW:MAXimum?
READ:BLUetooth:MEAS<i>:MEValuation:TRACe:SOBW:CURRent?
READ:BLUetooth:MEAS<i>:MEValuation:TRACe:SOBW:AVERage?
READ:BLUetooth:MEAS<i>:MEValuation:TRACe:SOBW:MAXimum?
Returns current, average and maximum results of the "Spectrum 20 dB Bandwidth"
trace. The 20 dB bandwidth values are available for BR bursts (CONFigure:
BLUetooth:MEAS<i>:ISIGnal:BTYPe).
Return values:
<Reliability> decimal
Reliability Indicator
<OBW_1> ... float
<OBW_769> 769 bandwidth results, covering a frequency range [–1.5 MHz,
+1.5 MHz], relative to the peak emission within the measured
Bluetooth channel. The spacing between adjacent trace points is
3.906 kHz (≅4 MHz/1024).
Range: -99.99 dB to 99.99 dB
Default unit: dB
Usage: Query only
Firmware/Software: V1.0.15.20
V3.7.40: added commands for current and average results
FETCh:BLUetooth:MEAS<i>:MEValuation:TRACe:FRANge:AVERage?
READ:BLUetooth:MEAS<i>:MEValuation:TRACe:FRANge:AVERage?
Returns the average values of the "Frequency Range" trace. The values are available
for BR packets.
Return values:
<Reliability> decimal
Reliability Indicator
<FrequencyRange> float
RX signal level measured at the frequencies between 501 pixels
(502 values)
Range: -100 dBm to 42 dBm
Default unit: dBm
Example: See Performing Spectrum Measurements
Usage: Query only
Firmware/Software: V3.2.50
FETCh:BLUetooth:MEAS<i>:MEValuation:TRACe:SACP[:PTX]?
READ:BLUetooth:MEAS<i>:MEValuation:TRACe:SACP[:PTX]?
Returns the values of the "Spectrum ACP" table for BR and LE packets in line with
Bluetooth test specification.
Note that the number of returned values depends on the current burst type.
● For BR bursts, the trace returns 79 values.
The number of valid ACP results depends on the ACP measurement mode
(CONFigure:BLUetooth:MEAS<i>:MEValuation:SACP:BRATe:
MEASurement:MODE):
– In CH21 mode, the first 21 ACP values contain results for the relative channels
–10, ..., 0, ..., +10; the remaining 58 values are not displayed.
– In CH79 mode, valid ACP values are available for all 79 Bluetooth channels
(2402 MHz, 2403 MHz, ..., 2480 MHz)
● For LE bursts, the trace returns 81 values.
The number of valid ACP results depends on the ACP measurement mode
(CONFigure:BLUetooth:MEAS<i>:MEValuation:SACP:LENergy:LE2M:
MEASurement:MODE):
– In CH10 ("ACP +/- 5 Channels") mode, the first 21 ACP values contain results
for the 1 MHz channels centered at fTX – 10 MHz, fTX – 9 MHz, ..., fTX + 10
MHz. The remaining 58 values are invalid (NAV).
This mode is applicable to all types of LE bursts.
– In CH40 mode ("LE All Channels"), ACP values 1 to 81 contain results for the 1
MHz channels centered at 2401 MHz, 2402 MHz, ..., 2481 MHz
This mode is only applicable to test packets using LE 1M PHY or LE 2M PHY.
Return values:
<Reliability> float
Reliability Indicator
<ACP_1> ... float
<ACP_N> As explained above, for BR bursts the trace returns N=79, and
for LE bursts it returns N=81 values.
Range: -99.99 dBm to 99.99 dBm
Default unit: dBm
Example: See Performing Spectrum Measurements
Usage: Query only
Firmware/Software: V2.0.10
FETCh:BLUetooth:MEAS<i>:MEValuation:TRACe:SGACp[:PTX]?
READ:BLUetooth:MEAS<i>:MEValuation:TRACe:SGACp[:PTX]?
Returns the values of the "Spectrum Gated ACP" tables for EDR packets. The
R&S CMW measures the adjacent channel power values PTX(f) in line with Bluetooth
test specification.
The number of valid results depends on the ACP measurement mode (CONFigure:
BLUetooth:MEAS<i>:MEValuation:SACP:BRATe:MEASurement:MODE CH21 |
CH79):
● If "ACP +/- 10 Channels" is selected, the first 21 values contain the results for the
relative channels –10, ..., 0, ..., +10; the remaining 58 values are not displayed.
● If "ACP 79 Channels" is selected, valid ACP values are available for all channels in
the Bluetooth regulatory range.
Return values:
<Reliability> float
Reliability Indicator
<ACP_1> ... float
<ACP_79> 79 ACP results
Range: -99.99 dBm to 99.99 dBm
Default unit: dBm
Example: See Performing Spectrum Measurements
Usage: Query only
Firmware/Software: V2.0.20
FETCh:BLUetooth:MEAS<i>:MEValuation:TRACe:SACP:CURRent?
FETCh:BLUetooth:MEAS<i>:MEValuation:TRACe:SACP:AVERage?
FETCh:BLUetooth:MEAS<i>:MEValuation:TRACe:SACP:MAXimum?
READ:BLUetooth:MEAS<i>:MEValuation:TRACe:SACP:CURRent?
READ:BLUetooth:MEAS<i>:MEValuation:TRACe:SACP:AVERage?
READ:BLUetooth:MEAS<i>:MEValuation:TRACe:SACP:MAXimum?
Returns the current, average and maximum values of the "Spectrum ACP" traces for
BR and LE packets.
The number of returned values depends on the current burst type.
● For BR bursts, the trace returns 79 values.
The number of valid ACP results depends on the ACP measurement mode
(CONFigure:BLUetooth:MEAS<i>:MEValuation:SACP:BRATe:
MEASurement:MODE):
– In CH21 mode ("ACP +/- 10 Channels"), the first 21 ACP values contain results
for the relative channels –10, ..., 0, ..., +10; the remaining 58 values are not dis-
played.
– In CH79 mode ("ACP 79 Channels"), valid ACP values are available for all 79
Bluetooth channels (2402 MHz, 2403 MHz, ..., 2480 MHz)
● For LE bursts, the trace returns 81 values.
The number of valid ACP results depends on the ACP measurement mode
(CONFigure:BLUetooth:MEAS<i>:MEValuation:SACP:LENergy:LE2M:
MEASurement:MODE):
– In CH10 mode ("ACP +/- 5 Channels"), the first 21 ACP values contain results
for the 1 MHz channels centered at fTX – 10 MHz, fTX – 9 MHz, ..., fTX + 10
MHz. The remaining 58 values are invalid (NAV).
This mode is applicable to all types of LE bursts.
– In CH40 mode ("LE All Channels"), ACP values 1 to 81 contain results for the 1
MHz channels centered at 2401 MHz, 2402 MHz, ..., 2481 MHz
This mode is only applicable to test packets using LE 1M PHY or LE 2M PHY.
Return values:
<Reliability> float
Reliability Indicator
<ACP> float
79 ACP values for BR, 81 ACP values for LE
Range: -99.99 dBm to 99.99 dBm
Example: See Performing Spectrum Measurements
Usage: Query only
Firmware/Software: V3.7.40
FETCh:BLUetooth:MEAS<i>:MEValuation:TRACe:SGACp:CURRent?
FETCh:BLUetooth:MEAS<i>:MEValuation:TRACe:SGACp:AVERage?
FETCh:BLUetooth:MEAS<i>:MEValuation:TRACe:SGACp:MAXimum?
READ:BLUetooth:MEAS<i>:MEValuation:TRACe:SGACp:CURRent?
READ:BLUetooth:MEAS<i>:MEValuation:TRACe:SGACp:AVERage?
READ:BLUetooth:MEAS<i>:MEValuation:TRACe:SGACp:MAXimum?
Returns the results of the "Spectrum Gated ACP" traces for EDR packets. The
R&S CMW measures the current, average and maximum adjacent channel power val-
ues.
The number of valid results depends on the ACP measurement mode (CONFigure:
BLUetooth:MEAS<i>:MEValuation:SGACp:EDRate:MEASurement:MODECH21
| CH79):
● If CH21 mode ("ACP +/- 10 Channels") is selected, the first 21 values contain the
results for the relative channels –10, ..., 0, ..., +10; the remaining 58 values are not
displayed.
● If CH79 mode ("ACP 79 Channels") is selected, valid ACP values are available for
all channels in the Bluetooth regulatory range.
Return values:
<Reliability> float
Reliability Indicator
<ACP> float
79 ACP results
Range: -99.99 dBm to 99.99 dBm
Example: See Performing Spectrum Measurements
Usage: Query only
Firmware/Software: V3.7.40
The following commands return the list mode results for a selected segment.
To configure the list mode, use the commands described in Chapter 7.6.3.4, "List Mode
Settings", on page 526.
For a description of the list mode, see Chapter 7.2.5, "List Mode", on page 340.
The indicated ranges apply to all statistical results except standard deviation results.
The minimum for standard deviation results equals 0. The maximum equals the width
of the indicated range divided by two. Exceptions are explicitly stated.
FETCh:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>:MODulation:CURRent?........ 648
FETCh:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>:MODulation:CURRent:
EXTended?......................................................................................................... 650
FETCh:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>:MODulation:AVERage?........652
FETCh:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>:MODulation:MAXimum?.......652
FETCh:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>:MODulation:MINimum?........ 654
FETCh:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>:MODulation:SDEViation?..... 655
FETCh:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>:MODulation:SDEViation:
EXTended?......................................................................................................... 656
FETCh:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>:PVTime:CURRent?..............659
FETCh:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>:PVTime:AVERage?............. 659
FETCh:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>:PVTime:MAXimum?.............659
FETCh:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>:PVTime:MINimum?..............659
FETCh:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>:SACP[:PTX]?...................... 660
FETCh:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>:SOBW:MAXimum?.............. 662
FETCh:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>:MODulation:
CURRent?
Returns modulation single value results for segment<no> in list mode.
The command returns all parameters listed below, independent of the selected list
mode setup. However, only for some of the parameters measured values are available.
For the other parameters, only an indicator is returned (e.g. NAV).
Suffix: .
<no> 1..48
Segment number
Return values:
<01_Reliability> decimal
Reliability Indicator
<02_SegReliability> decimal
Reliability indicator for the segment. The meaning of the
returned values is the same as for the common reliability indica-
tor, see previous parameter.
<03_Out of Tol> float
Percentage of measured bursts with failed limit check
Range: 0 % to 100 %
Default unit: %
<04_NominalPower> float
Average power during the carrier-on state
Range: -99.99 dBm to 99.99 dBm
Default unit: dBm
<05_FreqAcc or ωi> float
Frequency accuracy (BR, LE) or initial center frequency error ωi
(EDR)
Range: -0.99999E+6 Hz to 0.99999E+6 Hz
Default unit: Hz
<06_FreqDrift> float
Frequency drift (BR, LE)
Range: -0.99999E+6 Hz to 0.99999E+6 Hz
Default unit: Hz
<07_MaxDriftRate> float
Maximal drift rate (BR, LE)
Range: -0.99999E+6 Hz/50 μs to 0.99999E+6 Hz/50 μs
Default unit: Hz/50 μs
<08_Δf1 avg> float
<09_Δf1 min> Frequency deviation results (BR, LE)
<10_Δf1 max>
Range: 0 Hz to 250E+3 Hz
<11_Δf2 avg>
Default unit: Hz
<12_Δf2 min>
<13_Δf2 max>
<14_Δf2 99.9%> float
Frequency deviation value Δf2 above which 99.9% of all mea-
sured Δf2 values occur (BR, LE)
<15_ω0 + ωi> float
Overall uncompensated frequency error (EDR)
Range: -0.99999E+6 Hz to 0.99999E+6 Hz
Default unit: Hz
<16_ω0max> float
Maximum compensated frequency error (EDR)
Range: -0.99999E+6 Hz to 0.99999E+6 Hz
Default unit: Hz
<17_RMS DEVM> float
RMS DEVM (EDR)
Range: 0 to 1
<18_Peak DEVM> float
Peak DEVM (EDR)
Range: 0 to 1
<19_P99 DEVM> float
DEVM value below which 99% of all measured DEVM values
occur (EDR)
Range: 0 to 1
<20_FreqOffset> float
Frequency offset (LE)
Range: -0.99999E+6 Hz to 0.99999E+6 Hz
Default unit: Hz
<21_InitialFreqDrift> float
Initial frequency drift (LE)
Range: -0.99999E+6 Hz to 0.99999E+6 Hz
Default unit: Hz
Example: See Performing Measurements
FETCh:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>:MODulation:
CURRent:EXTended?
Returns modulation single value results for segment<no> in list mode including Blue-
tooth version 5.0.
The command returns all parameters listed below, independent of the selected list
mode setup. However, only for some of the parameters measured values are available.
For the other parameters, only an indicator is returned (e.g. NAV).
Suffix: .
<no> 1..48
Segment number
Return values:
<01_Reliability> decimal
Reliability Indicator
<02_SegReliability> decimal
Reliability indicator for the segment. The meaning of the
returned values is the same as for the common reliability indica-
tor, see previous parameter.
<03_Out of Tol> float
Percentage of measured bursts with failed limit check
Range: 0 % to 100 %
Default unit: %
<04_NominalPower> float
Average power during the carrier-on state
Range: -99.99 dBm to 99.99 dBm
Default unit: dBm
<05_FreqAcc or ωi> float
Frequency accuracy (BR, LE) or initial center frequency error ωi
(EDR)
Range: -0.99999E+6 Hz to 0.99999E+6 Hz
Default unit: Hz
<06_FreqDrift> float
Frequency drift (BR, LE)
Range: -0.99999E+6 Hz to 0.99999E+6 Hz
Default unit: Hz
<07_MaxDriftRate> float
Maximal drift rate (BR, LE)
Range: -0.99999E+6 Hz/50 μs to 0.99999E+6 Hz/50 μs
Default unit: Hz/50 μs
<08_Δf1 avg> float
<09_Δf1 min> Frequency deviation results (BR, LE)
<10_Δf1 max>
Range: 0 Hz to 250E+3 Hz
<11_Δf2 avg>
Default unit: Hz
<12_Δf2 min>
<13_Δf2 max>
<14_Δf2 99.9%> float
Frequency deviation value Δf2 above which 99.9% of all mea-
sured Δf2 values occur (BR, LE)
Range: -0.99999E+6 Hz to 0.99999E+6 Hz
Default unit: Hz
<15_ω0 + ωi> float
Overall uncompensated frequency error (EDR)
Range: -0.99999E+6 Hz to 0.99999E+6 Hz
Default unit: Hz
<16_ω0max> float
Maximum compensated frequency error (EDR)
Range: -0.99999E+6 Hz to 0.99999E+6 Hz
Default unit: Hz
<17_RMS DEVM> RMS DEVM (EDR)
Range: 0 to 1
<18_Peak DEVM> float
Peak DEVM (EDR)
Range: 0 to 1
<19_P99 DEVM> float
DEVM value below which 99% of all measured DEVM values
occur (EDR)
Range: 0 to 1
<20_FreqOffset> float
Frequency offset (LE)
Range: -0.99999E+6 Hz to 0.99999E+6 Hz
Default unit: Hz
<21_InitialFreqDrift> float
Initial frequency drift (LE)
Range: -0.99999E+6 Hz to 0.99999E+6 Hz
Default unit: Hz
FETCh:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>:MODulation:
AVERage?
FETCh:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>:MODulation:
MAXimum?
Returns modulation single value results for segment<no> in list mode.
The command returns all parameters listed below, independent of the selected list
mode setup. However, only for some of the parameters measured values are available.
For the other parameters, only an indicator is returned (e.g. NAV).
Suffix: .
<no> 1..48
Segment number
Return values:
<01_Reliability> decimal
Reliability Indicator
<02_SegReliability> decimal
Reliability indicator for the segment. The meaning of the
returned values is the same as for the common reliability indica-
tor, see previous parameter.
<03_Out of Tol> float
Percentage of measured bursts with failed limit check
Range: 0 % to 100 %
Default unit: %
<04_NominalPower> float
Average power during the carrier-on state
Range: -99.99 dBm to 99.99 dBm
Default unit: dBm
FETCh:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>:MODulation:
MINimum?
Returns modulation single value results for segment<no> in list mode.
The command returns all parameters listed below, independent of the selected list
mode setup. However, only for some of the parameters measured values are available.
For the other parameters, only an indicator is returned (e.g. NAV).
Suffix: .
<no> 1..48
Segment number
Return values:
<01_Reliability> decimal
Reliability Indicator
<02_SegReliability> decimal
Reliability indicator for the segment. The meaning of the
returned values is the same as for the common reliability indica-
tor, see previous parameter.
<03_Out of Tol> float
Percentage of measured bursts with failed limit check
Range: 0 % to 100 %
Default unit: %
<04_NominalPower> float
Average power during the carrier-on state
Range: -99.99 dBm to 99.99 dBm
Default unit: dBm
<05_Δf1 avg> float
<06_Δf1 min> Frequency deviation results (BR, LE)
<07_Δf1 max>
Range: 0 Hz to 250E+3 Hz
<08_Δf2 avg>
Default unit: Hz
<09_Δf2 min>
<10_Δf2 max>
Example: See Performing Measurements
Usage: Query only
Firmware/Software: V3.2.50
Options: R&S CMW-KM012
FETCh:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>:MODulation:
SDEViation?
Returns modulation single value results for segment<no> in list mode.
The command returns all parameters listed below, independent of the selected list
mode setup. However, only for some of the parameters measured values are available.
For the other parameters, only an indicator is returned (e.g. NAV).
Suffix: .
<no> 1..48
Segment number
Return values:
<1_Reliability> decimal
Reliability Indicator
<2_SegReliability> decimal
Reliability indicator for the segment. The meaning of the
returned values is the same as for the common reliability indica-
tor, see previous parameter.
<3_Out of Tol> float
Percentage of measured bursts with failed limit check
Range: 0 % to 100 %
Default unit: %
<4_NominalPower> float
Average power during the carrier-on state
Range: -99.99 dBm to 99.99 dBm
Default unit: dBm
<5_FreqAcc or ωi> float
Frequency accuracy (BR, LE) or initial center frequency error ωi
(EDR)
Range: -0.99999E+6 Hz to 0.99999E+6 Hz
Default unit: Hz
<6_FreqDrift> float
Frequency drift (BR, LE)
Range: -0.99999E+6 Hz to 0.99999E+6 Hz
Default unit: Hz
<7_MaxDriftRate> float
Maximal drift rate (BR, LE)
Range: -0.99999E+6 Hz/50 μs to 0.99999E+6 Hz/50 μs
Default unit: Hz/50 μs
FETCh:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>:MODulation:
SDEViation:EXTended?
Returns modulation single value results for segment<no> in list mode including Blue-
tooth version 5.0.
The command returns all parameters listed below, independent of the selected list
mode setup. However, only for some of the parameters measured values are available.
For the other parameters, only an indicator is returned (e.g. NAV).
Suffix: .
<no> 1..48
Segment number
Return values:
<1_Reliability> decimal
Reliability Indicator
<2_SegReliability> decimal
Reliability indicator for the segment. The meaning of the
returned values is the same as for the common reliability indica-
tor, see previous parameter.
<3_Out of Tol> float
Percentage of measured bursts with failed limit check
Range: 0 % to 100 %
Default unit: %
<4_NominalPower> float
Average power during the carrier-on state
Range: -99.99 dBm to 99.99 dBm
Default unit: dBm
<5_FreqAcc or ωi> float
Frequency accuracy (BR, LE) or initial center frequency error ωi
(EDR)
Range: -0.99999E+6 Hz to 0.99999E+6 Hz
Default unit: Hz
<6_FreqDrift> float
Frequency drift (BR, LE)
Range: -0.99999E+6 Hz to 0.99999E+6 Hz
Default unit: Hz
<7_MaxDriftRate> float
Maximal drift rate (BR, LE)
Range: -0.99999E+6 Hz to 0.99999E+6 Hz
Default unit: Hz
<8_Δf2 99.9%> float
Frequency deviation value Δf2 above which 99.9% of all mea-
sured Δf2 values occur (BR, LE)
Range: -0.99999E+6 Hz to 0.99999E+6 Hz
Default unit: Hz
FETCh:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>:PVTime:CURRent?
FETCh:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>:PVTime:AVERage?
FETCh:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>:PVTime:
MAXimum?
FETCh:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>:PVTime:
MINimum?
Returns statistical power vs. time single value results for segment<no> in list mode.
The command returns all parameters listed below, independent of the selected list
mode setup. However, only for some of the parameters measured values are available.
For the other parameters, only an indicator is returned (e.g. NAV).
Suffix: .
<no> 1..48
Segment number
Return values:
<1_Reliability> decimal
Reliability Indicator
<2_SegReliability> decimal
Reliability indicator for the segment. The meaning of the
returned values is the same as for the common reliability indica-
tor, see previous parameter.
<3_OutOfTol> float
Percentage of measured bursts with failed limit check
Range: 0 % to 100 %
<4_NominalPower> float
Average power during the carrier-on state
Range: -99.99 dBm to 99.99 dBm
Default unit: dBm
<5_PeakPower> float
Peak power
Range: -99.99 dBm to 99.99 dBm
Default unit: dBm
<6_LeakagePower> float
Leakage power (BR, LE)
Range: -99.99 dBm to 99.99 dBm
Default unit: dBm
<7_GFSKPower> float
Average power within the GFSK modulated part of the burst
(EDR)
Range: -99.99 dBm to 99.99 dBm
Default unit: dBm
<8_DPSKPower> float
Average power within the DPSK modulated part of the burst
(EDR)
Range: -99.99 dBm to 99.99 dBm
Default unit: dBm
<9_DPSK_–_GFSK> float
Difference between the <8_DPSKPower> and <7_GFSKPower>
(EDR)
Range: -99.99 dBm to 99.99 dBm
Default unit: dBm
<10_GuardPeriod> float
Length of the guard band between the packet header and the
EDR synchronization sequence (EDR)
Range: 0 µs to 9.99 µs
Default unit: s
<11_Peak_–_Avg> float
Difference between the peak power and the average power in
the burst (LE)
Range: -99.99 dBm to 99.99 dBm
Default unit: dBm
Example: See Performing Measurements
Usage: Query only
Firmware/Software: V3.2.50
V3.5.60: results <5_PeakPower> available also for EDR
Options: R&S CMW-KM012
FETCh:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>:SACP[:PTX]?
Returns spectrum ACP single value results for segment<no> in list mode.
The command returns all parameters listed below, independent of the selected list
mode setup. However, only for some of the parameters measured values are available.
For the other parameters, only an indicator is returned (e.g. NAV).
Suffix: .
<no> 1..48
Segment number
Return values:
<1_Reliability> decimal
Reliability Indicator
<2_SegReliability> decimal
Reliability indicator for the segment. The meaning of the
returned values is the same as for the common reliability indica-
tor, see previous parameter.
<3_OutOfTol> float
Percentage of measured bursts with failed limit check
Range: 0 % to 100 %
Default unit: %
<4_NominalPower> float
Average power during the carrier-on state
Range: -99.99 dBm to 99.99 dBm
Default unit: dBm
<5_NoOfExceptions> decimal
Number of exceptions, whose power is above "Exception PTX"
Range: 0 to 99
<6_PTxRef> float
Reference power obtained within the center channel (EDR)
Range: -99.99 dBm to 99.99 dBm
Default unit: dBm
<7_PTx26ChN1Abs> float
The absolute PTX - 26 dB (-1) result (EDR)
Range: -99.99 dBm to 99.99 dBm
Default unit: dBm
<8_PTx26ChP1Abs> float
The absolute PTX - 26 dB (+1) result (EDR)
Range: -99.99 dBm to 99.99 dBm
Default unit: dBm
<9_PTx26ChN1Rel> float
The PTX - 26 dB (-1) result relative to the reference power (EDR)
Range: -99.99 dBW to 99.99 dBW
<10_PTx26ChP1Rel> float
The PTX - 26 dB (+1) result relative to the reference power (EDR)
Range: -99.99 dBW to 99.99 dBW
Default unit: dBW
<11_ACP> ... float
The PTX results for all channels
21 values for ACP +/-10 channels mode (BR, EDR)
11 values for ACP +/-5 channels mode (LE)
Range: -99.99 dBm to 99.99 dBm
Default unit: dBm
FETCh:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>:SOBW:MAXimum?
Returns spectrum occupied bandwidth (20 dB bandwidth) single value results for seg-
ment<no> in list mode. The 20 dB bandwidth measurement is available for BR bursts
only.
Suffix: .
<no> 1..48
Segment number
Return values:
<1_Reliability> decimal
Reliability Indicator
<2_SegReliability> decimal
Reliability indicator for the segment. The meaning of the
returned values is the same as for the common reliability indica-
tor, see previous parameter.
<3_BurstOutOfTol> float
Percentage of measured bursts with failed limit check
Range: 0 % to 100 %
Default unit: %
<4_NominalPower> float
Average power during the carrier-on state
Range: -99.99 dBm to 99.99 dBm
Default unit: dBm
<5_PeakEmission> float
Peak power within the maximum spectral trace
Range: -99.99 dBm to 99.99 dBm
Default unit: dBm
<6_fL> float
The smallest frequency at which the transmit power drops 20 dB
below the peak power
Range: -0.99999E+6 MHz to 0.99999E+6 MHz
Default unit: Hz
<7_fH> float
The highest frequency at which the transmit power drops 20 dB
below the peak power
Range: -0.99999E+6 MHz to 0.99999E+6 MHz
Default unit: Hz
<8_fH_–_fL> float
Difference between the <7_fH> and <6_fL>
Range: -0.99999E+6 MHz to 0.99999E+6 MHz
Default unit: Hz
Example: See Performing Measurements
Usage: Query only
Firmware/Software: V3.2.50
Options: R&S CMW-KM012
The following sections describe the commands related to the non-signaling LE adver-
tiser Rx measurement with ARB generator.
The following commands control the measurement and return the current measure-
ment state.
INITiate:BLUetooth:MEAS<i>:RXQuality...........................................................................663
STOP:BLUetooth:MEAS<i>:RXQuality............................................................................. 663
ABORt:BLUetooth:MEAS<i>:RXQuality............................................................................663
FETCh:BLUetooth:MEAS<i>:RXQuality:STATe?................................................................664
FETCh:BLUetooth:MEAS<i>:RXQuality:STATe:ALL?......................................................... 664
INITiate:BLUetooth:MEAS<i>:RXQuality
STOP:BLUetooth:MEAS<i>:RXQuality
ABORt:BLUetooth:MEAS<i>:RXQuality
Starts, stops, or aborts the measurement:
● INITiate... starts or restarts the measurement. The measurement enters the
"RUN" state.
● STOP... halts the measurement immediately. The measurement enters the "RDY"
state. Measurement results are kept. The resources remain allocated to the mea-
surement.
● ABORt... halts the measurement immediately. The measurement enters the
"OFF" state. All measurement values are set to NAV. Allocated resources are
released.
Use FETCh...STATe? to query the current measurement state.
Example: See Performing an Rx Measurement
Usage: Event
Firmware/Software: V3.7.20
Options: R&S CMW-KD611
FETCh:BLUetooth:MEAS<i>:RXQuality:STATe?
Queries the main measurement state. Use FETCh:...:STATe:ALL? to query the
measurement state including the substates. Use INITiate..., STOP...,
ABORt... to change the measurement state.
Return values:
<MeasState> OFF | RDY | RUN
OFF: measurement switched off, no resources allocated, no
results available (when entered after ABORt...)
RDY: measurement has been terminated, valid results are avail-
able
RUN: measurement running (after INITiate..., READ...),
synchronization pending or adjusted, resources active or queued
*RST: OFF
Example: See Performing an Rx Measurement
Usage: Query only
Firmware/Software: V3.7.20
Options: R&S CMW-KD611
Manual operation: See "Rx Meas (Softkey)" on page 381
FETCh:BLUetooth:MEAS<i>:RXQuality:STATe:ALL?
Queries the main measurement state and the measurement substates. Both measure-
ment substates are relevant for running measurements only. Use FETCh:...:STATe?
to query the main measurement state only. Use INITiate..., STOP...,
ABORt... to change the measurement state.
Return values:
<MainState> OFF | RDY | RUN
OFF: measurement switched off, no resources allocated, no
results available (when entered after STOP...)
RDY: measurement has been terminated, valid results are avail-
able
RUN: measurement running (after INITiate..., READ...),
synchronization pending or adjusted, resources active or queued
*RST: OFF
<SyncState> PEND | ADJ | INV
PEND: waiting for resource allocation, adjustment, hardware
switching ("pending")
ADJ: all necessary adjustments finished, measurement running
("adjusted")
INV: not applicable because <main_state>: OFF or RDY ("inva-
lid")
<ResourceState> QUE | ACT | INV
QUE: measurement without resources, no results available
("queued")
ACT: resources allocated, acquisition of results in progress but
not complete ("active")
INV: not applicable because <main_state>: OFF or RDY ("inva-
lid")
Example: See Performing an Rx Measurement
Usage: Query only
Firmware/Software: V3.7.20
Options: R&S CMW-KD611
Manual operation: See "Rx Meas (Softkey)" on page 381
CONFigure:BLUetooth:MEAS<i>:RXQuality:SENSitivity:STARtlevel....................................669
CONFigure:BLUetooth:MEAS<i>:RXQuality:SENSitivity:STEPsize......................................670
CONFigure:BLUetooth:MEAS<i>:RXQuality:SPOTcheck:LEVel.......................................... 670
CONFigure:BLUetooth:MEAS<i>:RXQuality:AINDex <AdvChanIndex>
Specifies the advertiser channel index to be measured.
See also Figure 7-14.
Parameters:
<AdvChanIndex> numeric
Range: 37 to 39
*RST: 37
Example: See Configuring an Rx Measurement
Firmware/Software: V3.7.20
Options: R&S CMW-KM611
Manual operation: See "Frequency, Channel, Advertising Index" on page 429
CONFigure:BLUetooth:MEAS<i>:RXQuality:EATTenuation:OUTPut <Atten>
Defines an external attenuation (or gain, if the value is negative), to be applied to the
output connector.
Parameters:
<Atten> numeric
Range: -50 dB to 90 dB
*RST: 0 dB
Example: See Configuring an Rx Measurement
Firmware/Software: V3.7.20
Options: R&S CMW-KD611
Manual operation: See "External Attenuation (Output)" on page 429
CONFigure:BLUetooth:MEAS<i>:RXQuality:ROUTe:USAGe:ALL
<TXConnectorBENCH>, <Usage>...
CONFigure:BLUetooth:MEAS<i>:RXQuality:ROUTe:USAGe:ALL?
<TXConnectorBENCH>
Activates or deactivates the individual RF connectors of a connector bench. The set-
ting is relevant for non-signaling Rx measurements.
For possible bench values, see Chapter 7.6.1.4, "Values for RF Path Selection",
on page 489.
Parameters:
<Usage> OFF | ON
Comma-separated list of 4 or 8 values, one for each connector
of the bench.
*RST: ON, OFF, OFF, OFF, OFF, OFF, OFF, OFF
Parameters for setting and query:
<TXConnectorBENCH> Selects a bench with 4 or 8 connectors.
*RST: R118
Example: See Configuring an Rx Measurement
Options: R&S CMW-KD611
Manual operation: See "Connectors (Output)" on page 429
CONFigure:BLUetooth:MEAS<i>:RXQuality:GARB <ArbDuringTx>
Enables / disables the processing of ARB file during measurements.
Parameters:
<ArbDuringTx> OFF | ON
*RST: OFF
Example: See Configuring an Rx Measurement
Firmware/Software: V3.7.20
Options: R&S CMW-KD611
Manual operation: See "Generate ARB during Tx Measurements" on page 447
CONFigure:BLUetooth:MEAS<i>:RXQuality:MMODe <MeasMode>
Sets measurement mode for non-signaling Rx measurements.
Parameters:
<MeasMode> SPOT | SENS | PER
Spot check, sensitivity search, PER measurement
*RST: SPOT
Example: See Configuring an Rx Measurement
Firmware/Software: V3.7.20
Options: R&S CMW-KD611
Manual operation: See "Mode" on page 447
CONFigure:BLUetooth:MEAS<i>:RXQuality:PER:LEVel <Level>
Sets the Tx level of R&S CMW for PER measurements.
The allowed value range can be calculated as follows:
Range (Level) = Range (Output Power) - External Attenuation
Range (Output Power) = -130 dBm to 0 dBm (RFx COM) or -120 dBm
to 8 dBm (RFx OUT); please also notice the ranges quoted in the data sheet.
Parameters:
<Level> numeric
Range: see above
*RST: -40 dBm
Example: See Configuring an Rx Measurement
Firmware/Software: V3.7.20
Options: R&S CMW-KD611
Manual operation: See "Level" on page 448
CONFigure:BLUetooth:MEAS<i>:RXQuality:PER:TXPackets <PacketsToSend>
Sets number of packets for PER measurements.
Parameters:
<PacketsToSend> numeric
Range: 1 to 100E+3
*RST: 10
Example: See Configuring an Rx Measurement
Firmware/Software: V3.7.20
Options: R&S CMW-KD611
Manual operation: See "Packets to Send" on page 448
CONFigure:BLUetooth:MEAS<i>:RXQuality:SADDress <ScannerAddress>
Sets the scanner's device address of R&S CMW.
Parameters:
<ScannerAddress> hex
12-digit hexadecimal number
Range: #H0 to #HFFFFFFFFFFFF
*RST: #H123456789ABC
Example: See Configuring an Rx Measurement
Firmware/Software: V3.7.20
Options: R&S CMW-KD611
Manual operation: See "CMW Scanner Address" on page 447
CONFigure:BLUetooth:MEAS<i>:RXQuality:SATYpe <ScannerAddressType>
Sets the address type of R&S CMW scanner device address.
Parameters:
<ScannerAddrType> PUBLic | RANDom
*RST: PUBL
Example: See Configuring an Rx Measurement
Firmware/Software: V3.7.20
Options: R&S CMW-KD611
Manual operation: See "CMW Address Type" on page 448
CONFigure:BLUetooth:MEAS<i>:RXQuality:SENSitivity:RETRy <RetryCount>
Specify the number of retry attempts per step for sensitivity search measurement.
Parameters:
<RetryCount> numeric
Range: 0 to 7
*RST: 0
Example: See Configuring an Rx Measurement
Firmware/Software: V3.7.20, V3.7.30: range extended, reset value changed
Options: R&S CMW-KD611
Manual operation: See "Retry" on page 448
CONFigure:BLUetooth:MEAS<i>:RXQuality:SENSitivity:STARtlevel <StartLevel>
Sets Tx start level of R&S CMW for sensitivity search measurement.
CONFigure:BLUetooth:MEAS<i>:RXQuality:SENSitivity:STEPsize <StepSize>
Sets the step size for decreasing Tx level of R&S CMW for sensitivity search measure-
ment.
Parameters:
<StepSize> numeric
Range: 0.01 dB to 5 dB
*RST: 1 dB
Example: See Configuring an Rx Measurement
Firmware/Software: V3.7.20
Options: R&S CMW-KD611
Manual operation: See "Step Size" on page 448
CONFigure:BLUetooth:MEAS<i>:RXQuality:SPOTcheck:LEVel <Level>
Sets the Tx level of R&S CMW for spot check.
The allowed value range can be calculated as follows:
Range (Level) = Range (Output Power) - External Attenuation
Range (Output Power) = -130 dBm to 0 dBm (RFx COM) or -120 dBm
to 8 dBm (RFx OUT); please also notice the ranges quoted in the data sheet.
Parameters:
<Level> numeric
Range: see above
*RST: -40 dBm
Example: See Configuring an Rx Measurement
Firmware/Software: V3.7.20
Options: R&S CMW-KD611
Manual operation: See "Spot Check > Level" on page 448
FETCh:BLUetooth:MEAS<i>:RXQuality:ADETected:AADDress?
Queries the automatically detected advertiser address of EUT.
Return values:
<Reliability> decimal
See Reliability Indicator
<AdvAddress> string
12-digit hexadecimal number
Range: #H0 to #HFFFFFFFFFFFF
Example: See Performing an Rx Measurement
Usage: Query only
Firmware/Software: V3.7.20
Options: R&S CMW-KD611
Manual operation: See "Spot Check" on page 419
FETCh:BLUetooth:MEAS<i>:RXQuality:PER?
Queries the PER results for the specified Tx level of R&S CMW.
Return values:
<Reliability> decimal
See Reliability Indicator
<Result> float
Packet error rate
Example: See Performing an Rx Measurement
Usage: Query only
Firmware/Software: V3.7.20
Options: R&S CMW-KD611
FETCh:BLUetooth:MEAS<i>:RXQuality:PER:RXPackets?
Queries the number of packets received during PER measurement.
Return values:
<Reliability> decimal
See Reliability Indicator
<PacketsReceived> decimal
Packets detected by the R&S CMW
Range: 0 to 100E+3
Example: See Performing an Rx Measurement
Usage: Query only
Firmware/Software: V3.7.20
Options: R&S CMW-KD611
Manual operation: See "PER" on page 420
FETCh:BLUetooth:MEAS<i>:RXQuality:SENSitivity?
Queries the results of sensitivity search measurements for a target PER.
Return values:
<Reliability> decimal
See Reliability Indicator
<SensitivitySearch> float
Determined Tx level of R&S CMW for the specified PER value.
Range: -120 dBm to 0 dBm
Example: See Performing an Rx Measurement
Usage: Query only
Firmware/Software: V3.7.20
Options: R&S CMW-KD611
Manual operation: See "Sensitivity Search" on page 420
FETCh:BLUetooth:MEAS<i>:RXQuality:SPOTcheck?
Queries the verdict of spot check.
Return values:
<Reliability> decimal
See Reliability Indicator
The following sections describe the commands related to the non-signaling LE adver-
tiser Tx-Rx measurement.
The following commands control the measurement and return the current measure-
ment state.
INITiate:BLUetooth:MEAS<i>:TRX...................................................................................673
STOP:BLUetooth:MEAS<i>:TRX..................................................................................... 673
ABORt:BLUetooth:MEAS<i>:TRX.................................................................................... 673
FETCh:BLUetooth:MEAS<i>:TRX:STATe?........................................................................674
FETCh:BLUetooth:MEAS<i>:TRX:STATe:ALL?................................................................. 674
INITiate:BLUetooth:MEAS<i>:TRX
STOP:BLUetooth:MEAS<i>:TRX
ABORt:BLUetooth:MEAS<i>:TRX
Starts, stops, or aborts the measurement:
● INITiate... starts or restarts the measurement. The measurement enters the
"RUN" state.
● STOP... halts the measurement immediately. The measurement enters the "RDY"
state. Measurement results are kept. The resources remain allocated to the mea-
surement.
FETCh:BLUetooth:MEAS<i>:TRX:STATe?
Queries the main measurement state. Use FETCh:...:STATe:ALL? to query the
measurement state including the substates. Use INITiate..., STOP...,
ABORt... to change the measurement state.
Return values:
<MeasState> OFF | RDY | RUN
OFF: measurement switched off, no resources allocated, no
results available (when entered after ABORt...)
RDY: measurement has been terminated, valid results are avail-
able
RUN: measurement running (after INITiate..., READ...),
synchronization pending or adjusted, resources active or queued
*RST: OFF
Example: See Performing a Tx-Rx Measurement
Usage: Query only
Firmware/Software: V3.7.62
Options: R&S CMW-KD611
FETCh:BLUetooth:MEAS<i>:TRX:STATe:ALL?
Queries the main measurement state and the measurement substates. Both measure-
ment substates are relevant for running measurements only. Use FETCh:...:STATe?
to query the main measurement state only. Use INITiate..., STOP...,
ABORt... to change the measurement state.
Return values:
<MainState> OFF | RDY | RUN
OFF: measurement switched off, no resources allocated, no
results available (when entered after STOP...)
RDY: measurement has been terminated, valid results are avail-
able
RUN: measurement running (after INITiate..., READ...),
synchronization pending or adjusted, resources active or queued
*RST: OFF
<SyncState> PEND | ADJ | INV
PEND: waiting for resource allocation, adjustment, hardware
switching ("pending")
ADJ: all necessary adjustments finished, measurement running
("adjusted")
INV: not applicable because <main_state>: OFF or RDY ("inva-
lid")
<ResourceState> QUE | ACT | INV
QUE: measurement without resources, no results available
("queued")
ACT: resources allocated, acquisition of results in progress but
not complete ("active")
INV: not applicable because <main_state>: OFF or RDY ("inva-
lid")
Example: See Performing a Tx-Rx Measurement
Usage: Query only
Firmware/Software: V3.7.62
Options: R&S CMW-KD611
<Power> OFF | ON
Statistical power results
*RST: ON
<Modulation> OFF | ON
Statistical modulation results
*RST: ON
<SpectrumACP> OFF | ON
Spectrum ACP results
Only ACP+/-5 channel mode supported (21 half-channels)
*RST: ON
Example: See Configuring a Tx-Rx Measurement
Firmware/Software: V3.7.62
Options: R&S CMW-KD611
FETCh:BLUetooth:MEAS<i>:TRX:ACP?
Returns the "Spectrum ACP" results for Tx-Rx tests on advertiser packets (LE 1M
PHY). Only "ACP+/-5 channel" mode is supported (21 half-channels).
See also Chapter 7.4.2.18, "LE: Spectrum ACP Results ", on page 415.
Return values:
<Reliability> decimal
Reliability Indicator
<NominalPower> float
Average power during the carrier-on state
Default unit: dBm
<NoOfExceptions> decimal
Number of exceptions (channels ±3, ±4 ... with an ACP above
the "Exception PTx" threshold )
Example: See Performing a Tx-Rx Measurement
Usage: Query only
Firmware/Software: V3.7.62
Options: R&S CMW-KD611
FETCh:BLUetooth:MEAS<i>:TRX:MODulation?
Returns current modulation results for TRx tests on advertiser packets (LE 1M PHY).
See also Chapter 7.4.2.17, "LE: Statistical Modulation Results ", on page 410.
Return values:
<1_Reliability> decimal
See Reliability Indicator
<2_Out of Tol> float
Out of tolerance result, i.e. percentage of measurement intervals
of the statistic count (CONFigure:BLUetooth:MEAS<i>:
MEValuation:SCOunt:MODulation) exceeding the specified
limits, see Limits (Modulation LE).
<3_Δf2 99.9%> float
Default unit: %
<4_Freq. Accuracy> float
Default unit: Hz
<5_Freq. Drift> float
Default unit: Hz
<6_Max. Drift_Rate> float
<7_Δf1 avg> float
Default unit: Hz
<8_Δf1 min> float
Default unit: Hz
<9_Δf1 max> float
Default unit: Hz
<10_Δf2 avg> float
Default unit: Hz
<11_Δf2 min> float
Default unit: Hz
<12_Δf2 max> float
Range: -0.99999E+6 Hz to 0.99999E+6 Hz
Default unit: Hz
<13_Nominal Pow> float
Default unit: dBm
<14_ModRatio> float
Range: 0 to >1
<15_Freq. Offset> float
<16_Initial FreqDrift> float
FETCh:BLUetooth:MEAS<i>:TRX:POWer?
Returns the power results for Tx-Rx measurements on advertiser packets LE 1M PHY
(uncoded).
Return values:
<Reliability> decimal
Reliability Indicator
<OutOfTol> float
Out of tolerance result, i.e. percentage of measurement intervals
of the statistic count (CONFigure:BLUetooth:MEAS<i>:
MEValuation:SCOunt:PVTime) exceeding the specified lim-
its, see CONFigure:BLUetooth:MEAS<i>:MEValuation:
LIMit:LENergy[:LE1M]:PVTime.
<NominalPower> float
Average power during the carrier-on state
Range: -128.0 dBm to 130.0 dBm
Default unit: dBm
<PeakPower> float
Peak power during the carrier-on state
Range: -128.0 dBm to 130.0 dBm
Default unit: dBm
<LeakagePower> float
Average power during the carrier-off state
Range: -128.0 dBm to 130.0 dBm
Default unit: dBm
<PeakMinAvgPow> float
Peak power minus average power
Range: 0 dB to 158 dB
Default unit: dB
Example: See Performing a Tx-Rx Measurement
Usage: Query only
Firmware/Software: V3.7.62
Options: R&S CMW-KD611
FETCh:BLUetooth:MEAS<i>:TRX:SPOT?
Queries the verdict of spot check.
Return values:
<Reliability> decimal
See Reliability Indicator
<SpotCheckResult> FAIL | PASS
FAIL: no expected response from the EUT detected within
advertising event
PASS: SCAN_RSP detected
Example: See Performing a Tx-Rx Measurement
Usage: Query only
Firmware/Software: V3.7.62
Options: R&S CMW-KD611
The following sections describe the commands related to the non-signaling direct test
mode with ARB generator.
Direct test mode with ARB generator is only supported by R&S CMW100.
CONFigure:BLUetooth:MEAS<i>:COMSettings:PROTocol................................................. 682
CONFigure:BLUetooth:MEAS<i>:COMSettings:STOPbits.................................................. 682
CONFigure:BLUetooth:MEAS<i>:CPRotocol.....................................................................683
CONFigure:BLUetooth:MEAS<i>:HWINterface..................................................................683
CLEan:BLUetooth:MEAS<i>:ELOGging............................................................................683
SENSe:BLUetooth:MEAS<i>:ELOGging:ALL?.................................................................. 684
SENSe:BLUetooth:MEAS<i>:ELOGging:LAST?................................................................ 684
CALL:BLUetooth:MEAS<i>:DTMode:LENergy:RDEVices
Discovers the DUTs connected to USB ports via a USB-to-RS232 adapter.
Example: See Configuring an Rx Measurement
Usage: Event
Firmware/Software: V3.8.10
Options: R&S CMW-KD720
Manual operation: See "Refresh Devices (hotkey)" on page 452
CALL:BLUetooth:MEAS<i>:DTMode:LENergy:RESet
Sends the HCI reset command to the EUT via USB.
Check the execution via CALL:BLUetooth:MEAS<i>:DTMode:LENergy:RRESult?
.
Example: See Configuring an Rx Measurement
Usage: Event
Firmware/Software: V3.8.10
Options: R&S CMW-KD720
Manual operation: See "Reset EUT (hotkey)" on page 453
CALL:BLUetooth:MEAS<i>:DTMode:LENergy:RRESult?
Returns the result of reset DUT command. Refer toCALL:BLUetooth:MEAS<i>:
DTMode:LENergy:RESet.
Return values:
<Result> FAIL | PASS
Example: See Configuring an Rx Measurement
Usage: Query only
Firmware/Software: V3.8.10
Options: R&S CMW-KD720
Manual operation: See "Reset EUT (hotkey)" on page 453
CONFigure:BLUetooth:MEAS<i>:COMSettings:BAUDrate <BaudRate>
Specifies the transmission parameters of serial connection.
Parameters:
<BaudRate> B110 | B300 | B600 | B12K | B24K | B48K | B96K | B14K |
B19K | B28K | B38K | B57K | B115k | B234k | B460k | B500k |
B576k | B921k | B1M | B1M5 | B2M | B3M | B3M5 | B4M
Data transmission rate in symbol: 110, 300, 600, 1200, 2400,
4800, 9600, 14400, 19200, 28800, 38400, 57600, 115200,
230400, 460800, 500000, 576000, 921600, 1000000, 1152000,
2000000, 3000000, 3500000, 4000000
*RST: B96K
Example: See Configuring an Rx Measurement
Firmware/Software: V3.8.10
Options: R&S CMW-KD720
Manual operation: See "Baud Rate" on page 452
CONFigure:BLUetooth:MEAS<i>:COMSettings:COMPort <No>
Specifies the virtual COM port of the R&S CMW100 control computer to be used for
USB connection with USB to RS232 adapter.
Parameters:
<No> integer
The number of a virtual COM port
*RST: 0
Example: See Configuring an Rx Measurement
Firmware/Software: V3.8.10
Options: R&S CMW-KD720
Manual operation: See "Virtual COM Port" on page 452
CONFigure:BLUetooth:MEAS<i>:COMSettings:PARity <Parity>
Specifies the transmission parameters of serial connection.
Parameters:
<Parity> NONE | ODD | EVEN
Number of parity bits
*RST: NONE
Example: See Configuring an Rx Measurement
Firmware/Software: V3.8.10
Options: R&S CMW-KD720
CONFigure:BLUetooth:MEAS<i>:COMSettings:PORTs:CATalog?
Queries the COM ports of the R&S CMW100 control computer used by a DUT. The
command is relevant for the USB connection with USB-to-serial converter ("HW Inter-
face" = USB to RS232 adapter).
Results are returned for each used USB port: <NoDevices>, {1, <Discovered-
Port>}1, ..., {<NoDevices>, <DiscoveredPort>}<NoDevices>
Return values:
<NoDevices> decimal
Number of all COM ports, where a connected DUT has been
recognized
<ItemNumber> decimal
The number of a list item
<DiscoveredPort> string
Number of the virtual COM port, to which the used USB port has
been mapped
Example: See Configuring an Rx Measurement
Usage: Query only
Firmware/Software: V3.8.10
Options: R&S CMW-KD720
CONFigure:BLUetooth:MEAS<i>:COMSettings:PROTocol <Protocol>
Specifies the transmission parameters of serial connection.
Parameters:
<Protocol> XONXoff | CTSRts | NONE
Transmit flow control X-ON/X-OFF, RFR/CTS, or none
*RST: NONE
Example: See Configuring an Rx Measurement
Firmware/Software: V3.8.10
Options: R&S CMW-KD720
Manual operation: See "Protocol" on page 452
CONFigure:BLUetooth:MEAS<i>:COMSettings:STOPbits <StopBits>
Specifies the transmission parameters of serial connection.
Parameters:
<StopBits> S1 | S2
Number of bits used for stop indication
*RST: S1
Example: See Configuring an Rx Measurement
Firmware/Software: V3.8.10
Options: R&S CMW-KD720
Manual operation: See "Stop Bits, Parity" on page 452
CONFigure:BLUetooth:MEAS<i>:HWINterface <HwInterface>
Defines the interface used for the control connection between the DUT and the control
computer of the R&S CMW100.
Parameters:
<HwInterface> NONE | RS232 | USB
RS232: USB connection with USB to RS232 adapter
NONE: no control via USB to be used
USB: direct USB connection
Example: See Configuring an Rx Measurement
Firmware/Software: V3.8.10
Options: R&S CMW-KD720
Manual operation: See "HW Interface" on page 451
CLEan:BLUetooth:MEAS<i>:ELOGging
Clears the event log.
Example: See Configuring an Rx Measurement
Usage: Event
Firmware/Software: V3.8.10
Options: R&S CMW-KD720
Manual operation: See "Event Log" on page 452
SENSe:BLUetooth:MEAS<i>:ELOGging:ALL?
Queries all entries of the event log.
For each entry three parameters are returned, from oldest to latest entry: {<Time-
stamp>, <Category>, <Event>}entry 1, {<Timestamp>, <Category>, <Event>}entry 2, ...
Return values:
<Timestamp> string
Timestamp of the entry as string in the format "hh:mm:ss"
<Category> INFO | WARNing | ERRor | CONTinue
Category of the entry, as indicated in the main view by an icon
CONTinue means the continuation of previous entry.
<Event> string
Text string describing the event
Example: See Configuring an Rx Measurement
Usage: Query only
Firmware/Software: V3.8.10
Options: R&S CMW-KD720
Manual operation: See "Event Log" on page 452
SENSe:BLUetooth:MEAS<i>:ELOGging:LAST?
Queries the latest entry of the event log.
Return values:
<Timestamp> string
Timestamp of the entry as string in the format "hh:mm:ss"
<Category> INFO | WARNing | ERRor | CONTinue
Category of the entry, as indicated in the main view by an icon
CONTinue means the continuation of previous entry.
<Event> string
Text string describing the event
Example: See Configuring an Rx Measurement
Usage: Query only
Firmware/Software: V3.8.10
The following commands define the basic properties of the Bluetooth signal for non-
signaling direct test mode.
CONFigure:BLUetooth:MEAS<i>:ISIGnal:DTMode:PATTern:LENergy:LRANge.................... 685
CONFigure:BLUetooth:MEAS<i>:ISIGnal:DTMode:PATTern:LENergy:LE2M........................ 685
CONFigure:BLUetooth:MEAS<i>:ISIGnal:DTMode:PATTern:LENergy:LE1M........................ 685
CONFigure:BLUetooth:MEAS<i>:ISIGnal:DTMode:PLENgth:LENergy:LRANge....................686
CONFigure:BLUetooth:MEAS<i>:ISIGnal:DTMode:PLENgth:LENergy:LE2M....................... 686
CONFigure:BLUetooth:MEAS<i>:ISIGnal:DTMode:PLENgth:LENergy:LE1M....................... 686
CONFigure:BLUetooth:MEAS<i>:DTMode:RXQuality:EATTenuation:OUTPut.......................686
CONFigure:BLUetooth:MEAS<i>:DTMode:RXQuality:SMINdex:LENergy.............................686
CONFigure:BLUetooth:MEAS<i>:ISIGnal:DTMode:PATTern:LENergy:LRANge
<Pattern Type>
CONFigure:BLUetooth:MEAS<i>:ISIGnal:DTMode:PATTern:LENergy:LE2M
<Pattern Type>
CONFigure:BLUetooth:MEAS<i>:ISIGnal:DTMode:PATTern:LENergy:LE1M
<Pattern Type>
Specifies the data pattern type that the EUT transmits as user payload data in its LE
packets.
Commands for uncoded LE 1M PHY (..:LE1M..), LE 2M PHY (..:LE2M..), and LE
coded PHY (..:LRANge..) are available.
Parameters:
<Pattern Type> ALL0 | ALL1 | P11 | P44 | PRBS9
ALL0: '00000000'
P11: '10101010' in transmission order (LSB first)
P44: '11110000' in transmission order (LSB first)
ALL1: '11111111'
PRBS9: pseudorandom binary sequence of length 9
*RST: P11
Example: See Configuring an Rx Measurement
Firmware/Software: V3.8.10
Options: R&S CMW-KD720
Manual operation: See "Pattern Type" on page 438
CONFigure:BLUetooth:MEAS<i>:ISIGnal:DTMode:PLENgth:LENergy:LRANge
<PayloadLength>
CONFigure:BLUetooth:MEAS<i>:ISIGnal:DTMode:PLENgth:LENergy:LE2M
<PayloadLength>
CONFigure:BLUetooth:MEAS<i>:ISIGnal:DTMode:PLENgth:LENergy:LE1M
<PayloadLength>
Specifies the number of bytes (octets) in the payload data of the measured LE test
packets.
Commands for uncoded LE 1M PHY (..:LE1M..), LE 2M PHY (..:LE2M..), and LE
coded PHY (..:LRANge..) are available.
Parameters:
<PayloadLength> numeric
Payload lengths of LE packets
Range: 0 Byte(s) to 255 Byte(s)
*RST: 37 Byte(s)
Example: See Configuring an Rx Measurement
Firmware/Software: V3.8.10
Options: R&S CMW-KD720
Manual operation: See "Payload Length" on page 437
CONFigure:BLUetooth:MEAS<i>:DTMode:RXQuality:EATTenuation:OUTPut
<Atten>
Defines an external attenuation (or gain, if the value is negative), to be applied to the
output connector.
Parameters:
<Atten> numeric
Range: -50 dB to 90 dB
*RST: 0 dB
Example: See Configuring an Rx Measurement
Firmware/Software: V3.8.10
Options: R&S CMW-KD720
Manual operation: See "External Attenuation (Output)" on page 429
CONFigure:BLUetooth:MEAS<i>:DTMode:RXQuality:SMINdex:LENergy
<ModIndexType>
Selects the standard or stable modulation index used by a dirty transmitter.
Parameters:
<ModIndexType> OFF | ON
OFF: standard modulation index is used
ON: stable modulation index is used
*RST: OFF
Example: See Configuring an Rx Measurement
Firmware/Software: V3.8.10
Options: R&S CMW-KD720
Manual operation: See "Stable Modulation Index" on page 422
The following commands control the measurement and return the current measure-
ment state.
INITiate:BLUetooth:MEAS<i>:DTMode:RXQuality:PER......................................................687
STOP:BLUetooth:MEAS<i>:DTMode:RXQuality:PER........................................................ 687
ABORt:BLUetooth:MEAS<i>:DTMode:RXQuality:PER....................................................... 687
FETCh:BLUetooth:MEAS<i>:DTMode:RXQuality:PER:STATe?........................................... 688
INITiate:BLUetooth:MEAS<i>:DTMode:RXQuality:PER
STOP:BLUetooth:MEAS<i>:DTMode:RXQuality:PER
ABORt:BLUetooth:MEAS<i>:DTMode:RXQuality:PER
Starts, stops, or aborts the measurement:
● INITiate... starts or restarts the measurement. The measurement enters the
"RUN" state.
● STOP... halts the measurement immediately. The measurement enters the "RDY"
state. Measurement results are kept. The resources remain allocated to the mea-
surement.
● ABORt... halts the measurement immediately. The measurement enters the
"OFF" state. All measurement values are set to NAV. Allocated resources are
released.
Use FETCh...STATe? to query the current measurement state.
Example: See Performing an Rx Measurement
Usage: Event
Firmware/Software: V3.8.10
Options: R&S CMW-KD720
FETCh:BLUetooth:MEAS<i>:DTMode:RXQuality:PER:STATe?
Queries the main measurement state. Use FETCh:...:STATe:ALL? to query the
measurement state including the substates. Use INITiate..., STOP...,
ABORt... to change the measurement state.
Return values:
<MeasStatus> OFF | RDY | RUN
OFF: measurement switched off, no resources allocated, no
results available (when entered after ABORt...)
RDY: measurement has been terminated, valid results can be
available
RUN: measurement running (after INITiate..., READ...),
synchronization pending or adjusted, resources active or queued
Example: See Performing an Rx Measurement
Usage: Query only
Firmware/Software: V3.8.10
Options: R&S CMW-KD720
Manual operation: See "PER, PER Search (Softkeys)" on page 382
CONFigure:BLUetooth:MEAS<i>:DTMode:RXQuality:LIMit:MPER:LENergy:
LRANge <Limit>
CONFigure:BLUetooth:MEAS<i>:DTMode:RXQuality:LIMit:MPER:LENergy:LE2M
<Limit>
CONFigure:BLUetooth:MEAS<i>:DTMode:RXQuality:LIMit:MPER:LENergy:LE1M
<Limit>
Specifies the upper PER limit for direct test mode with ARB generator.
Commands for uncoded LE 1M PHY (..:LE1M..), LE 2M PHY (..:LE2M..), and LE
coded PHY (..:LRANge..) are available.
Parameters:
<Limit> numeric | ON | OFF
Range: 0 % to 100 %
*RST: 30.8 %
Default unit: %
Additional parameters: OFF | ON (disables the limit | enables the
limit using the previous/default value)
Example: See Configuring an Rx Measurement
Firmware/Software: V3.8.10
Options: R&S CMW-KD720
Manual operation: See "Limits " on page 449
CONFigure:BLUetooth:MEAS<i>:DTMode:RXQuality:RINTegrity:LENergy:
LRANge <ReportIntegrity>
CONFigure:BLUetooth:MEAS<i>:DTMode:RXQuality:RINTegrity:LENergy:LE2M
<ReportIntegrity>
CONFigure:BLUetooth:MEAS<i>:DTMode:RXQuality:RINTegrity:LENergy:LE1M
<ReportIntegrity>
Sets the ratio of the test packets with correct CRC transmitted by the R&S CMW.
Commands for uncoded LE 1M PHY (..:LE1M..), LE 2M PHY (..:LE2M..), and LE
coded PHY (..:LRANge..) are available.
Parameters:
<ReportIntegrity> OFF | ON
OFF: 100% of packets generated with correct CRC
ON: 50% of packets generated with correct CRC
*RST: OFF
Example: See Configuring an Rx Measurement
Firmware/Software: V3.8.10
Options: R&S CMW-KD720
Manual operation: See "Integrity" on page 450
CONFigure:BLUetooth:MEAS<i>:DTMode:RXQuality:PER:LEVel <Level>
Sets the Tx level of ARB generator.
Parameters:
<Level> numeric
*RST: -40 dBm
Example: See Configuring an Rx Measurement
Firmware/Software: V3.8.10
Options: R&S CMW-KD720
Manual operation: See "Tx Level (CMW) < PER" on page 449
CALCulate:BLUetooth:MEAS<i>:DTMode:RXQuality:PER:LENergy:LRANge?
CALCulate:BLUetooth:MEAS<i>:DTMode:RXQuality:PER:LENergy:LE2M?
CALCulate:BLUetooth:MEAS<i>:DTMode:RXQuality:PER:LENergy:LE1M?
FETCh:BLUetooth:MEAS<i>:DTMode:RXQuality:PER:LENergy:LRANge?
FETCh:BLUetooth:MEAS<i>:DTMode:RXQuality:PER:LENergy:LE2M?
FETCh:BLUetooth:MEAS<i>:DTMode:RXQuality:PER:LENergy:LE1M?
READ:BLUetooth:MEAS<i>:DTMode:RXQuality:PER:LENergy:LRANge?
READ:BLUetooth:MEAS<i>:DTMode:RXQuality:PER:LENergy:LE2M?
READ:BLUetooth:MEAS<i>:DTMode:RXQuality:PER:LENergy:LE1M?
Return all results of the non-signaling LE Rx measurement for LE direct test.
Commands for uncoded LE 1M PHY (..:LE1M..), LE 2M PHY (..:LE2M..), and LE
coded PHY (..:LRANge..) are available.
Return values:
<Reliability> decimal
Reliability Indicator
<PER> float
Packet error rate
Range: 0 % to 100 %
Default unit: %
<PacketsReceived> decimal
Number of correct packets received and reported by the DUT.
Range: 0 to 30E+3
Example: See Performing an Rx Measurement
Usage: Query only
Firmware/Software: V3.8.10
Options: R&S CMW-KD720
The following commands control the measurement and return the current measure-
ment state.
INITiate:BLUetooth:MEAS<i>:DTMode:RXQuality:SEARch:PER.........................................691
STOP:BLUetooth:MEAS<i>:DTMode:RXQuality:SEARch:PER........................................... 691
ABORt:BLUetooth:MEAS<i>:DTMode:RXQuality:SEARch:PER..........................................691
FETCh:BLUetooth:MEAS<i>:DTMode:RXQuality:SEARch:PER:STATe?..............................691
INITiate:BLUetooth:MEAS<i>:DTMode:RXQuality:SEARch:PER
STOP:BLUetooth:MEAS<i>:DTMode:RXQuality:SEARch:PER
ABORt:BLUetooth:MEAS<i>:DTMode:RXQuality:SEARch:PER
Starts, stops, or aborts the measurement:
● INITiate... starts or restarts the measurement. The measurement enters the
"RUN" state.
● STOP... halts the measurement immediately. The measurement enters the "RDY"
state. Measurement results are kept. The resources remain allocated to the mea-
surement.
● ABORt... halts the measurement immediately. The measurement enters the
"OFF" state. All measurement values are set to NAV. Allocated resources are
released.
Use FETCh...STATe? to query the current measurement state.
Example: See Performing an Rx Measurement
Usage: Event
Firmware/Software: V3.8.10
Options: R&S CMW-KD720
FETCh:BLUetooth:MEAS<i>:DTMode:RXQuality:SEARch:PER:STATe?
Queries the main measurement state. Use FETCh:...:STATe:ALL? to query the
measurement state including the substates. Use INITiate..., STOP...,
ABORt... to change the measurement state.
Return values:
<MeasStatus> OFF | RDY | RUN
OFF: measurement switched off, no resources allocated, no
results available (when entered after ABORt...)
RDY: measurement has been terminated, valid results can be
available
RUN: measurement running (after INITiate..., READ...),
synchronization pending or adjusted, resources active or queued
Example: See Performing an Rx Measurement
Usage: Query only
Firmware/Software: V3.8.10
Options: R&S CMW-KD720
Manual operation: See "PER, PER Search (Softkeys)" on page 382
CONFigure:BLUetooth:MEAS<i>:DTMode:RXQuality:SEARch:LIMit:MPER:
LENergy:LRANge <Limit>
CONFigure:BLUetooth:MEAS<i>:DTMode:RXQuality:SEARch:LIMit:MPER:
LENergy:LE2M <Limit>
CONFigure:BLUetooth:MEAS<i>:DTMode:RXQuality:SEARch:LIMit:MPER:
LENergy:LE1M <Limit>
Specifies the upper PER limit for PER search measurements with ARB generator.
Commands for uncoded LE 1M PHY (..:LE1M..), LE 2M PHY (..:LE2M..), and LE
coded PHY (..:LRANge..) are available.
Parameters:
<Limit> numeric | ON | OFF
Range: 0 % to 100 %
*RST: 30.8 %
Default unit: %
Additional parameters: OFF | ON (disables the limit | enables the
limit using the previous/default level)
Example: See Configuring an Rx Measurement
Firmware/Software: V3.8.10
Options: R&S CMW-KD720
Manual operation: See "Limits " on page 449
CONFigure:BLUetooth:MEAS<i>:DTMode:RXQuality:SEARch:STARtlevel
<StartLevel>
Specifies the initial Tx power for the LE search iteration of PER search measurements
with ARB generator.
Parameters:
<StartLevel> numeric
Range: -100 dBm to 0 dBm
*RST: -70 dBm
Example: See Configuring an Rx Measurement
Firmware/Software: V3.8.10
Options: R&S CMW-KD720
Manual operation: See "Start Level < PER search" on page 450
CONFigure:BLUetooth:MEAS<i>:DTMode:RXQuality:SEARch:STEP <LevelStep>
Specifies the power step for the LE search iteration of PER search measurements with
ARB generator.
Parameters:
<LevelStep> numeric
Range: 0.01 dB to 5 dB
*RST: 0.5 dB
Example: See Configuring an Rx Measurement
Firmware/Software: V3.8.10
Options: R&S CMW-KD720
Manual operation: See "Level Step < PER search" on page 450
CONFigure:BLUetooth:MEAS<i>:DTMode:RXQuality:SEARch:RINTegrity:
LENergy:LRANge <ReportIntegrity>
CONFigure:BLUetooth:MEAS<i>:DTMode:RXQuality:SEARch:RINTegrity:
LENergy:LE2M <ReportIntegrity>
CONFigure:BLUetooth:MEAS<i>:DTMode:RXQuality:SEARch:RINTegrity:
LENergy:LE1M <ReportIntegrity>
Sets the ratio of the test packets with correct CRC transmitted by the R&S CMW for
direct test mode with ARB generator.
Commands for uncoded LE 1M PHY (..:LE1M..), LE 2M PHY (..:LE2M..), and LE
coded PHY (..:LRANge..) are available.
Parameters:
<ReportIntegrity> OFF | ON
OFF: 100% of packets generated with correct CRC
ON: 50% of packets generated with correct CRC
*RST: OFF
Example: See Configuring an Rx Measurement
Firmware/Software: V3.8.10
Options: R&S CMW-KD720
Manual operation: See "Integrity" on page 450
CALCulate:BLUetooth:MEAS<i>:DTMode:RXQuality:SEARch:PER:LENergy:
LRANge?
CALCulate:BLUetooth:MEAS<i>:DTMode:RXQuality:SEARch:PER:LENergy:
LE2M?
CALCulate:BLUetooth:MEAS<i>:DTMode:RXQuality:SEARch:PER:LENergy:
LE1M?
FETCh:BLUetooth:MEAS<i>:DTMode:RXQuality:SEARch:PER:LENergy:
LRANge?
FETCh:BLUetooth:MEAS<i>:DTMode:RXQuality:SEARch:PER:LENergy:LE2M?
FETCh:BLUetooth:MEAS<i>:DTMode:RXQuality:SEARch:PER:LENergy:LE1M?
READ:BLUetooth:MEAS<i>:DTMode:RXQuality:SEARch:PER:LENergy:LRANge?
READ:BLUetooth:MEAS<i>:DTMode:RXQuality:SEARch:PER:LENergy:LE2M?
READ:BLUetooth:MEAS<i>:DTMode:RXQuality:SEARch:PER:LENergy:LE1M?
Return the results of PER search RX measurement for LE direct test mode.
Commands for uncoded LE 1M PHY (..:LE1M..), LE 2M PHY (..:LE2M..), and LE
coded PHY (..:LRANge..) are available.
Return values:
<Reliability> decimal
Reliability Indicator
<PER> float
Packet error rate
Range: 0 % to 100 %
Default unit: %
<PacketsReceived> decimal
Number of correct packets received and reported by the DUT
Range: 0 to 30E+3
<SearchResult> float
TX level of the R&S CMW resulting in the configured PER
search limit
Range: -999 dBm to 0 dBm
Default unit: dBm
Example: See Performing an Rx Measurement
Usage: Query only
Firmware/Software: V3.8.10
Options: R&S CMW-KD720
For some settings, the command to be used depends on the active scenario. While the
combined signal path (CSP) scenario is active, these settings are configured via com-
mands of the signaling application. While the stand-alone (SA) scenario is active, they
are configured via measurement commands.
The following mapping tables provide an overview for measurement settings and for
multi-evaluation measurement commands.
Table 7-50: Mapping for measurement settings
CONFigure:BLUetooth:MEAS<i>:ISIGnal: CONFigure:BLUetooth:SIGN<i>:
PTYPe:EDRate CONNection:PACKets:PTYPe:EDRate
CONFigure:BLUetooth:MEAS<i>:ISIGnal: CONFigure:BLUetooth:SIGN<i>:
PTYPe:LENergy[:LE1M] CONNection:PACKets:PTYPe:LENergy[:
LE1M]
CONFigure:BLUetooth:MEAS<i>:ISIGnal: CONFigure:BLUetooth:SIGN<i>:
PTYPe:LENergy:LE2M CONNection:PACKets:PTYPe:LENergy:LE2M
CONFigure:BLUetooth:MEAS<i>:ISIGnal: CONFigure:BLUetooth:SIGN<i>:
PATTern:LENergy[:LE1M] CONNection:PACKets:PATTern:LENergy[:
LE1M]
CONFigure:BLUetooth:MEAS<i>:ISIGnal: CONFigure:BLUetooth:SIGN<i>:
PATTern:LENergy:LE2M CONNection:PACKets:PATTern:LENergy:
LE2M
CONFigure:BLUetooth:MEAS<i>:ISIGnal: CONFigure:BLUetooth:SIGN<i>:
PATTern:LENergy:LRANge CONNection:PACKets:PATTern:LENergy:
LRANge
CONFigure:BLUetooth:MEAS<i>:ISIGnal: CONFigure:BLUetooth:SIGN<i>:
PLENgth:EDRate CONNection:PACKets:PLENgth:EDRate
CONFigure:BLUetooth:MEAS<i>:ISIGnal: CONFigure:BLUetooth:SIGN<i>:
PLENgth:LENergy[:LE1M] CONNection:PACKets:PLENgth:LENergy[:
LE1M]
CONFigure:BLUetooth:MEAS<i>:ISIGnal: CONFigure:BLUetooth:SIGN<i>:
PLENgth:LENergy:LE2M CONNection:PACKets:PLENgth:LENergy:
LE2M
CONFigure:BLUetooth:MEAS<i>:ISIGnal: CONFigure:BLUetooth:SIGN<i>:
PLENgth:LENergy:LRANge CONNection:PACKets:PLENgth:LENergy:
LRANge
CALCulate:BLUetooth:MEAS<i>:DTMode:RXQuality:PER:LENergy:LRANge?........................................... 690
CALCulate:BLUetooth:MEAS<i>:DTMode:RXQuality:SEARch:PER:LENergy:LE1M?................................. 694
CALCulate:BLUetooth:MEAS<i>:DTMode:RXQuality:SEARch:PER:LENergy:LE2M?................................. 694
CALCulate:BLUetooth:MEAS<i>:DTMode:RXQuality:SEARch:PER:LENergy:LRANge?.............................694
CALCulate:BLUetooth:MEAS<i>:MEValuation:FRANge:BRATe:CURRent?................................................. 630
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:BRATe:AVERage?............................................589
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:BRATe:CURRent?............................................589
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:BRATe:MAXimum?...........................................589
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:BRATe:MINimum?............................................591
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:BRATe:SDEViation?......................................... 592
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:BRATe:XMAXimum?........................................ 589
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:BRATe:XMINimum?......................................... 589
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:CTE:LENergy:LE1M:AVERage?...................... 599
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:CTE:LENergy:LE1M:CURRent?...................... 599
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:CTE:LENergy:LE1M:MAXimum?..................... 599
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:CTE:LENergy:LE1M:SDEViation?................... 599
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:CTE:LENergy:LE1M:XMAXimum?...................599
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:CTE:LENergy:LE1M:XMINimum?....................599
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:CTE:LENergy:LE2M:AVERage?...................... 599
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:CTE:LENergy:LE2M:CURRent?...................... 599
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:CTE:LENergy:LE2M:MAXimum?..................... 599
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:CTE:LENergy:LE2M:SDEViation?................... 599
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:CTE:LENergy:LE2M:XMAXimum?...................599
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:CTE:LENergy:LE2M:XMINimum?....................599
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:EDRate:AVERage?.......................................... 594
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:EDRate:CURRent?.......................................... 594
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:EDRate:MAXimum?......................................... 594
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:EDRate:SDEViation?....................................... 595
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LE2M:AVERage?.............................. 601
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LE2M:CURRent?.............................. 601
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LE2M:MAXimum?............................. 602
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LE2M:MINimum?.............................. 605
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LE2M:SDEViation?........................... 608
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LE2M:XMAXimum?...........................602
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LE2M:XMINimum?............................ 602
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LRANge:AVERage?.......................... 604
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LRANge:CURRent?.......................... 604
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LRANge:MAXimum?......................... 604
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LRANge:MINimum?.......................... 607
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LRANge:SDEViation?....................... 609
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LRANge:XMAXimum?.......................604
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LRANge:XMINimum?........................604
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy[:LE1M]:AVERage?............................ 601
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy[:LE1M]:CURRent?............................ 601
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy[:LE1M]:MAXimum?........................... 601
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy[:LE1M]:MINimum?............................ 605
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy[:LE1M]:SDEViation?......................... 608
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy[:LE1M]:XMAXimum?.........................601
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy[:LE1M]:XMINimum?.......................... 601
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:CLASsic:AVERage?...........................614
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:CLASsic:CURRent?........................... 614
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:CLASsic:MAXimum?..........................614
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:CLASsic:SDEViation?........................ 616
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:CLASsic:XMAXimum?....................... 614
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:CLASsic:XMINimum?.........................614
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:LE2M:AVERage?................ 618
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:LE2M:CURRent?................ 618
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:LE2M:MAXimum?............... 618
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:LE2M:MINimum?................ 623
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:LE2M:SDEViation?............. 626
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:LE2M:XMAXimum?.............618
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:LE2M:XMINimum?.............. 618
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:LRANge:AVERage?............ 620
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:LRANge:CURRent?............ 620
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:LRANge:MAXimum?........... 620
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:LRANge:MINimum?............ 624
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:LRANge:SDEViation?......... 627
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:LRANge:XMAXimum?.........620
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:LRANge:XMINimum?..........620
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy[:LE1M]:AVERage?.............. 616
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy[:LE1M]:CURRent?.............. 616
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy[:LE1M]:MAXimum?............. 617
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy[:LE1M]:MINimum?.............. 622
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy[:LE1M]:SDEViation?........... 625
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy[:LE1M]:XMAXimum?...........617
CALCulate:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy[:LE1M]:XMINimum?............ 616
CALCulate:BLUetooth:MEAS<i>:MEValuation:PENCoding:EDRate:CURRent?.......................................... 636
CALCulate:BLUetooth:MEAS<i>:MEValuation:PENCoding:SSEQuence:EDRate:CURRent?......................637
CALCulate:BLUetooth:MEAS<i>:MEValuation:PVTime:BRATe:AVERage?.................................................. 577
CALCulate:BLUetooth:MEAS<i>:MEValuation:PVTime:BRATe:CURRent?.................................................. 577
CALCulate:BLUetooth:MEAS<i>:MEValuation:PVTime:BRATe:MAXimum?................................................. 577
CALCulate:BLUetooth:MEAS<i>:MEValuation:PVTime:BRATe:MINimum?.................................................. 577
CALCulate:BLUetooth:MEAS<i>:MEValuation:PVTime:EDRate:AVERage?................................................ 578
CALCulate:BLUetooth:MEAS<i>:MEValuation:PVTime:EDRate:CURRent?.................................................578
CALCulate:BLUetooth:MEAS<i>:MEValuation:PVTime:EDRate:MAXimum?............................................... 578
CALCulate:BLUetooth:MEAS<i>:MEValuation:PVTime:EDRate:MINimum?.................................................578
CALCulate:BLUetooth:MEAS<i>:MEValuation:PVTime:LENergy:LE2M:AVERage?.....................................582
CALCulate:BLUetooth:MEAS<i>:MEValuation:PVTime:LENergy:LE2M:CURRent?.....................................582
CALCulate:BLUetooth:MEAS<i>:MEValuation:PVTime:LENergy:LE2M:MAXimum?....................................582
CALCulate:BLUetooth:MEAS<i>:MEValuation:PVTime:LENergy:LE2M:MINimum?.....................................582
CALCulate:BLUetooth:MEAS<i>:MEValuation:PVTime:LENergy:LRANge:AVERage?................................ 582
CALCulate:BLUetooth:MEAS<i>:MEValuation:PVTime:LENergy:LRANge:CURRent?.................................582
CALCulate:BLUetooth:MEAS<i>:MEValuation:PVTime:LENergy:LRANge:MAXimum?............................... 582
CALCulate:BLUetooth:MEAS<i>:MEValuation:PVTime:LENergy:LRANge:MINimum?.................................582
CALCulate:BLUetooth:MEAS<i>:MEValuation:PVTime:LENergy[:LE1M]:AVERage?...................................581
CALCulate:BLUetooth:MEAS<i>:MEValuation:PVTime:LENergy[:LE1M]:CURRent?...................................581
CALCulate:BLUetooth:MEAS<i>:MEValuation:PVTime:LENergy[:LE1M]:MAXimum?..................................581
CALCulate:BLUetooth:MEAS<i>:MEValuation:PVTime:LENergy[:LE1M]:MINimum?...................................581
CALCulate:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:CLASsic:AVERage?................................. 585
CALCulate:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:CLASsic:CURRent?................................. 585
CALCulate:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:CLASsic:MAXimum?................................ 585
CALCulate:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:CLASsic:MINimum?................................. 585
CALCulate:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:LENergy:LE2M:AVERage?.......................586
CALCulate:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:LENergy:LE2M:CURRent?.......................586
CALCulate:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:LENergy:LE2M:MAXimum?......................586
CALCulate:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:LENergy:LE2M:MINimum?.......................586
CALCulate:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:LENergy:LRANge:AVERage?.................. 586
CALCulate:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:LENergy:LRANge:CURRent?...................586
CALCulate:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:LENergy:LRANge:MAXimum?................. 586
CALCulate:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:LENergy:LRANge:MINimum?...................586
CALCulate:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:LENergy[:LE1M]:AVERage?.....................586
CALCulate:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:LENergy[:LE1M]:CURRent?.....................586
CALCulate:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:LENergy[:LE1M]:MAXimum?....................586
CALCulate:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:LENergy[:LE1M]:MINimum?.....................586
CALCulate:BLUetooth:MEAS<i>:MEValuation:SACP:BRATe[:PTX]?........................................................... 629
CALCulate:BLUetooth:MEAS<i>:MEValuation:SACP:LENergy:LE2M?........................................................ 633
CALCulate:BLUetooth:MEAS<i>:MEValuation:SACP:LENergy:LRANge?....................................................633
CALCulate:BLUetooth:MEAS<i>:MEValuation:SACP:LENergy[:LE1M]?...................................................... 632
CALCulate:BLUetooth:MEAS<i>:MEValuation:SACP:NMODe:CLASsic?.....................................................634
CALCulate:BLUetooth:MEAS<i>:MEValuation:SACP:NMODe:LENergy:LE2M?.......................................... 635
CALCulate:BLUetooth:MEAS<i>:MEValuation:SACP:NMODe:LENergy:LRANge?......................................635
CALCulate:BLUetooth:MEAS<i>:MEValuation:SACP:NMODe:LENergy[:LE1M]?........................................ 635
CALCulate:BLUetooth:MEAS<i>:MEValuation:SGACp:EDRate[:PTX]?....................................................... 631
CALCulate:BLUetooth:MEAS<i>:MEValuation:SOBW:BRATe:MAXimum?...................................................628
CALCulate:BLUetooth:MEAS<i>:MEValuation:TRACe:PDEViation:MAXimum?.......................................... 639
CALCulate:BLUetooth:MEAS<i>:MEValuation:TRACe:PDEViation:MINimum?............................................639
CALL:BLUetooth:MEAS<i>:DTMode:LENergy:RDEVices.............................................................................680
CALL:BLUetooth:MEAS<i>:DTMode:LENergy:RESet...................................................................................680
CALL:BLUetooth:MEAS<i>:DTMode:LENergy:RRESult?............................................................................. 680
CLEan:BLUetooth:MEAS<i>:ELOGging........................................................................................................683
CONFigure:BLUetooth:MEAS<i>:COMSettings:BAUDrate........................................................................... 681
CONFigure:BLUetooth:MEAS<i>:COMSettings:COMPort............................................................................ 681
CONFigure:BLUetooth:MEAS<i>:COMSettings:PARity................................................................................ 681
CONFigure:BLUetooth:MEAS<i>:COMSettings:PORTs:CATalog?............................................................... 682
CONFigure:BLUetooth:MEAS<i>:COMSettings:PROTocol........................................................................... 682
CONFigure:BLUetooth:MEAS<i>:COMSettings:STOPbits............................................................................682
CONFigure:BLUetooth:MEAS<i>:CPRotocol................................................................................................ 683
CONFigure:BLUetooth:MEAS<i>:DISPlay.....................................................................................................516
CONFigure:BLUetooth:MEAS<i>:DTMode:RXQuality:EATTenuation:OUTPut............................................. 686
CONFigure:BLUetooth:MEAS<i>:DTMode:RXQuality:LIMit:MPER:LENergy:LE1M..................................... 688
CONFigure:BLUetooth:MEAS<i>:DTMode:RXQuality:LIMit:MPER:LENergy:LE2M..................................... 688
CONFigure:BLUetooth:MEAS<i>:DTMode:RXQuality:LIMit:MPER:LENergy:LRANge.................................688
CONFigure:BLUetooth:MEAS<i>:DTMode:RXQuality:PER:LEVel................................................................689
CONFigure:BLUetooth:MEAS<i>:DTMode:RXQuality:RINTegrity:LENergy:LE1M....................................... 689
CONFigure:BLUetooth:MEAS<i>:DTMode:RXQuality:RINTegrity:LENergy:LE2M....................................... 689
CONFigure:BLUetooth:MEAS<i>:DTMode:RXQuality:RINTegrity:LENergy:LRANge................................... 689
CONFigure:BLUetooth:MEAS<i>:DTMode:RXQuality:SEARch:LIMit:MPER:LENergy:LE1M...................... 692
CONFigure:BLUetooth:MEAS<i>:DTMode:RXQuality:SEARch:LIMit:MPER:LENergy:LE2M...................... 692
CONFigure:BLUetooth:MEAS<i>:DTMode:RXQuality:SEARch:LIMit:MPER:LENergy:LRANge.................. 692
CONFigure:BLUetooth:MEAS<i>:DTMode:RXQuality:SEARch:RINTegrity:LENergy:LE1M.........................693
CONFigure:BLUetooth:MEAS<i>:DTMode:RXQuality:SEARch:RINTegrity:LENergy:LE2M.........................693
CONFigure:BLUetooth:MEAS<i>:DTMode:RXQuality:SEARch:RINTegrity:LENergy:LRANge.....................693
CONFigure:BLUetooth:MEAS<i>:DTMode:RXQuality:SEARch:STARtlevel................................................. 693
CONFigure:BLUetooth:MEAS<i>:DTMode:RXQuality:SEARch:STEP..........................................................693
CONFigure:BLUetooth:MEAS<i>:DTMode:RXQuality:SMINdex:LENergy....................................................686
CONFigure:BLUetooth:MEAS<i>:HWINterface............................................................................................. 683
CONFigure:BLUetooth:MEAS<i>:ISIGnal:ACCaddress:LENergy................................................................. 508
CONFigure:BLUetooth:MEAS<i>:ISIGnal:ASYNchronize............................................................................. 504
CONFigure:BLUetooth:MEAS<i>:ISIGnal:BDADdress..................................................................................504
CONFigure:BLUetooth:MEAS<i>:ISIGnal:BTYPe......................................................................................... 503
CONFigure:BLUetooth:MEAS<i>:ISIGnal:CTE:LENergy:LE1M:TYPE..........................................................512
CONFigure:BLUetooth:MEAS<i>:ISIGnal:CTE:LENergy:LE1M:UNITs......................................................... 512
CONFigure:BLUetooth:MEAS<i>:ISIGnal:CTE:LENergy:LE2M:TYPE..........................................................512
CONFigure:BLUetooth:MEAS<i>:ISIGnal:CTE:LENergy:LE2M:UNITs......................................................... 512
CONFigure:BLUetooth:MEAS<i>:ISIGnal:DMODe........................................................................................503
CONFigure:BLUetooth:MEAS<i>:ISIGnal:DTMode:PATTern:LENergy:LE1M...............................................685
CONFigure:BLUetooth:MEAS<i>:ISIGnal:DTMode:PATTern:LENergy:LE2M...............................................685
CONFigure:BLUetooth:MEAS<i>:ISIGnal:DTMode:PATTern:LENergy:LRANge...........................................685
CONFigure:BLUetooth:MEAS<i>:ISIGnal:DTMode:PLENgth:LENergy:LE1M.............................................. 686
CONFigure:BLUetooth:MEAS<i>:ISIGnal:DTMode:PLENgth:LENergy:LE2M.............................................. 686
CONFigure:BLUetooth:MEAS<i>:ISIGnal:DTMode:PLENgth:LENergy:LRANge..........................................686
CONFigure:BLUetooth:MEAS<i>:ISIGnal:FEC:LENergy:LRANge................................................................509
CONFigure:BLUetooth:MEAS<i>:ISIGnal:LAP..............................................................................................504
CONFigure:BLUetooth:MEAS<i>:ISIGnal:LENergy:PHY.............................................................................. 507
CONFigure:BLUetooth:MEAS<i>:ISIGnal:LENergy:SYNWord......................................................................507
CONFigure:BLUetooth:MEAS<i>:ISIGnal:NAP............................................................................................. 505
CONFigure:BLUetooth:MEAS<i>:ISIGnal:OSLots:BRATe.............................................................................512
CONFigure:BLUetooth:MEAS<i>:ISIGnal:OSLots:EDRate........................................................................... 512
CONFigure:BLUetooth:MEAS<i>:ISIGnal:OSLots:LENergy:LE2M............................................................... 513
CONFigure:BLUetooth:MEAS<i>:ISIGnal:OSLots:LENergy[:LE1M]............................................................. 513
CONFigure:BLUetooth:MEAS<i>:ISIGnal:PATTern....................................................................................... 508
CONFigure:BLUetooth:MEAS<i>:ISIGnal:PATTern:LENergy:LE2M..............................................................508
CONFigure:BLUetooth:MEAS<i>:ISIGnal:PATTern:LENergy:LRANge......................................................... 509
CONFigure:BLUetooth:MEAS<i>:ISIGnal:PATTern:LENergy[:LE1M]............................................................508
CONFigure:BLUetooth:MEAS<i>:ISIGnal:PLENgth:BRATe.......................................................................... 510
CONFigure:BLUetooth:MEAS<i>:ISIGnal:PLENgth:EDRate.........................................................................510
CONFigure:BLUetooth:MEAS<i>:ISIGnal:PLENgth:LENergy:LE2M............................................................. 511
CONFigure:BLUetooth:MEAS<i>:ISIGnal:PLENgth:LENergy:LRANge.........................................................511
CONFigure:BLUetooth:MEAS<i>:ISIGnal:PLENgth:LENergy[:LE1M]........................................................... 511
CONFigure:BLUetooth:MEAS<i>:ISIGnal:PTYPe:BRATe............................................................................. 505
CONFigure:BLUetooth:MEAS<i>:ISIGnal:PTYPe:EDRate............................................................................506
CONFigure:BLUetooth:MEAS<i>:ISIGnal:PTYPe:LENergy:LE2M................................................................506
CONFigure:BLUetooth:MEAS<i>:ISIGnal:PTYPe:LENergy:LRANge............................................................506
CONFigure:BLUetooth:MEAS<i>:ISIGnal:PTYPe:LENergy[:LE1M]..............................................................506
CONFigure:BLUetooth:MEAS<i>:ISIGnal:UAP............................................................................................. 505
CONFigure:BLUetooth:MEAS<i>:MEValuation:BRATe:FILTer:BWIDth......................................................... 522
CONFigure:BLUetooth:MEAS<i>:MEValuation:EDRate:FILTer:BWIDth....................................................... 522
CONFigure:BLUetooth:MEAS<i>:MEValuation:FRANge:BRATe:MEASurement.......................................... 521
CONFigure:BLUetooth:MEAS<i>:MEValuation:LENergy:LE2M:FILTer:BWIDth............................................522
CONFigure:BLUetooth:MEAS<i>:MEValuation:LENergy:LRANge:FILTer:BWIDth....................................... 522
CONFigure:BLUetooth:MEAS<i>:MEValuation:LENergy[:LE1M]:FILTer:BWIDth..........................................522
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:BRATe:DAVerage........................................................550
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:BRATe:DELTa............................................................. 547
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:BRATe:DMAXimum.................................................... 550
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:BRATe:DMINimum......................................................550
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:BRATe:FACCuracy..................................................... 548
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:BRATe:FDRift............................................................. 549
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:BRATe:FDRift:APACkets............................................ 548
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:BRATe:MRATio........................................................... 551
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:BRATe:PVTime........................................................... 544
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:CTE:LENergy:LE1M:FDRift........................................559
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:CTE:LENergy:LE1M:FOFFset....................................557
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:CTE:LENergy:LE1M:PDEViation................................546
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:CTE:LENergy:LE2M:FDRift........................................559
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:CTE:LENergy:LE2M:FOFFset....................................557
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:CTE:LENergy:LE2M:PDEViation................................546
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:EDRate:DPSK:DEVM.................................................553
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:EDRate:DQPSk:DEVM...............................................552
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:EDRate:FSTability...................................................... 551
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:EDRate:PENCoding................................................... 567
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:EDRate:PENCoding:SSEQuence.............................. 568
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:EDRate:PVTime......................................................... 544
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:FRANge......................................................................564
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy:DAVerage.................................................... 560
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy:DAVerage:DF2S.......................................... 562
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy:DELTa.......................................................... 555
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy:DMAXimum................................................. 560
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy:DMAXimum:DF2S....................................... 562
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy:DMINimum...................................................560
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy:DMINimum:DF2S........................................ 562
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy:LE2M:DAVerage.......................................... 560
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy:LE2M:DAVerage:DF2S................................562
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy:LE2M:DELTa................................................555
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy:LE2M:DMAXimum....................................... 560
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy:LE2M:DMAXimum:DF2S.............................562
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy:LE2M:DMINimum........................................ 560
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy:LE2M:DMINimum:DF2S.............................. 562
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy:LE2M:FACCuracy........................................556
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy:LE2M:FDRift................................................ 558
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy:LE2M:FOFFset............................................ 557
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy:LE2M:MRATio..............................................563
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy:LE2M:PVTime..............................................545
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy:LE2M:SACP................................................ 565
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy:LRANge:DAVerage......................................561
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy:LRANge:DELTa........................................... 555
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy:LRANge:DMAXimum...................................561
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy:LRANge:DMINimum.................................... 561
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy:LRANge:FACCuracy....................................556
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy:LRANge:FDRift............................................558
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy:LRANge:FOFFset........................................557
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy:LRANge:PVTime......................................... 545
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy:LRANge:SACP............................................ 565
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy[:LE1M]:FACCuracy......................................556
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy[:LE1M]:FDRift.............................................. 558
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy[:LE1M]:FOFFset.......................................... 557
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy[:LE1M]:MRATio............................................563
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy[:LE1M]:PVTime............................................545
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:LENergy[:LE1M]:SACP.............................................. 565
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:PVTime....................................................................... 543
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:SACP..........................................................................565
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:SGACp....................................................................... 566
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIMit:SOBW.........................................................................564
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIST.....................................................................................527
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIST:CMWS:CMODe...........................................................530
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIST:COUNt.........................................................................527
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>:RESults.............................................. 527
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>:RESults:MSCalar............................... 528
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>:RESults:PSCalar................................ 528
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>:RESults:SACP....................................528
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>:RESults:SGACp................................. 528
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>:RESults:SOBW.................................. 528
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>:SCOunt...............................................529
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>:SCOunt:MSCalar................................529
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>:SCOunt:PSCalar................................ 529
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>:SCOunt:SACP....................................529
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>:SCOunt:SGACp................................. 530
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>:SCOunt:SOBW...................................530
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>[:SETup]...............................................532
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>[:SETup]:BTYPe.................................. 534
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>[:SETup]:CMWS:CONNector...............531
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>[:SETup]:CSCHeme............................ 531
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>[:SETup]:ENPower.............................. 534
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>[:SETup]:EXTended............................. 535
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>[:SETup]:FILTer....................................537
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>[:SETup]:FREQuency.......................... 537
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>[:SETup]:MOEXception....................... 538
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>[:SETup]:OSLots..................................538
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>[:SETup]:PATTern................................ 538
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>[:SETup]:PHY...................................... 539
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>[:SETup]:PLENgth............................... 539
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>[:SETup]:PTYPe.................................. 540
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>[:SETup]:RTRigger.............................. 540
CONFigure:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>[:SETup]:SLENgth............................... 541
CONFigure:BLUetooth:MEAS<i>:MEValuation:MOEXception...................................................................... 518
CONFigure:BLUetooth:MEAS<i>:MEValuation:REPetition........................................................................... 518
CONFigure:BLUetooth:MEAS<i>:MEValuation:RESult:DEVMagnitude........................................................ 523
CONFigure:BLUetooth:MEAS<i>:MEValuation:RESult:FDEViation.............................................................. 523
CONFigure:BLUetooth:MEAS<i>:MEValuation:RESult:FRANge.................................................................. 523
CONFigure:BLUetooth:MEAS<i>:MEValuation:RESult:IQABsolute.............................................................. 523
CONFigure:BLUetooth:MEAS<i>:MEValuation:RESult:IQDiff....................................................................... 523
CONFigure:BLUetooth:MEAS<i>:MEValuation:RESult:IQERror................................................................... 523
CONFigure:BLUetooth:MEAS<i>:MEValuation:RESult:MSCalar.................................................................. 523
CONFigure:BLUetooth:MEAS<i>:MEValuation:RESult:PDIFference............................................................ 523
CONFigure:BLUetooth:MEAS<i>:MEValuation:RESult:PENCoding............................................................. 523
CONFigure:BLUetooth:MEAS<i>:MEValuation:RESult:PSCalar...................................................................523
CONFigure:BLUetooth:MEAS<i>:MEValuation:RESult:PVSLot.................................................................... 523
CONFigure:BLUetooth:MEAS<i>:MEValuation:RESult:PVTime....................................................................523
CONFigure:BLUetooth:MEAS<i>:MEValuation:RESult:SACP...................................................................... 524
CONFigure:BLUetooth:MEAS<i>:MEValuation:RESult:SGACp.................................................................... 524
CONFigure:BLUetooth:MEAS<i>:MEValuation:RESult:SOBW..................................................................... 523
CONFigure:BLUetooth:MEAS<i>:MEValuation:RESult[:ALL]........................................................................524
CONFigure:BLUetooth:MEAS<i>:MEValuation:SACP:BRATe:MEASurement:MODE.................................. 520
CONFigure:BLUetooth:MEAS<i>:MEValuation:SACP:LENergy:LE2M:MEASurement:MODE..................... 520
CONFigure:BLUetooth:MEAS<i>:MEValuation:SACP:LENergy[:LE1M]:MEASurement:MODE................... 520
CONFigure:BLUetooth:MEAS<i>:MEValuation:SCONdition......................................................................... 518
CONFigure:BLUetooth:MEAS<i>:MEValuation:SCOunt:FRANge.................................................................519
CONFigure:BLUetooth:MEAS<i>:MEValuation:SCOunt:MODulation............................................................519
CONFigure:BLUetooth:MEAS<i>:MEValuation:SCOunt:PENCoding............................................................519
CONFigure:BLUetooth:MEAS<i>:MEValuation:SCOunt:PVTime.................................................................. 519
CONFigure:BLUetooth:MEAS<i>:MEValuation:SCOunt:SACP.....................................................................519
CONFigure:BLUetooth:MEAS<i>:MEValuation:SCOunt:SGACp.................................................................. 519
CONFigure:BLUetooth:MEAS<i>:MEValuation:SCOunt:SOBW....................................................................519
CONFigure:BLUetooth:MEAS<i>:MEValuation:SGACp:EDRate:MEASurement:MODE.............................. 520
CONFigure:BLUetooth:MEAS<i>:MEValuation:TOUT...................................................................................517
CONFigure:BLUetooth:MEAS<i>:RFSettings:CTE:LENergy:AOFFset......................................................... 498
CONFigure:BLUetooth:MEAS<i>:RFSettings:CTE:LENergy:NANTenna...................................................... 499
CONFigure:BLUetooth:MEAS<i>:RFSettings:EATTenuation........................................................................ 498
CONFigure:BLUetooth:MEAS<i>:RFSettings:ENPower................................................................................499
CONFigure:BLUetooth:MEAS<i>:RFSettings:FREQuency........................................................................... 500
CONFigure:BLUetooth:MEAS<i>:RFSettings:MCHannel:LENergy...............................................................502
CONFigure:BLUetooth:MEAS<i>:RFSettings:MCHannel[:CLASsic]............................................................. 502
CONFigure:BLUetooth:MEAS<i>:RFSettings:MMODe................................................................................. 501
CONFigure:BLUetooth:MEAS<i>:RFSettings:MMODe:NMODe:LENergy.................................................... 501
CONFigure:BLUetooth:MEAS<i>:RFSettings:UMARgin............................................................................... 500
CONFigure:BLUetooth:MEAS<i>:RXQuality:AINDex.................................................................................... 666
CONFigure:BLUetooth:MEAS<i>:RXQuality:EATTenuation:OUTPut............................................................ 666
CONFigure:BLUetooth:MEAS<i>:RXQuality:GARB...................................................................................... 667
CONFigure:BLUetooth:MEAS<i>:RXQuality:MMODe................................................................................... 667
CONFigure:BLUetooth:MEAS<i>:RXQuality:PER:LEVel...............................................................................668
CONFigure:BLUetooth:MEAS<i>:RXQuality:PER:TXPackets.......................................................................668
CONFigure:BLUetooth:MEAS<i>:RXQuality:ROUTe.....................................................................................666
CONFigure:BLUetooth:MEAS<i>:RXQuality:ROUTe:USAGe:ALL................................................................ 667
CONFigure:BLUetooth:MEAS<i>:RXQuality:SADDress................................................................................669
CONFigure:BLUetooth:MEAS<i>:RXQuality:SATYpe................................................................................... 669
CONFigure:BLUetooth:MEAS<i>:RXQuality:SENSitivity:RETRy.................................................................. 669
CONFigure:BLUetooth:MEAS<i>:RXQuality:SENSitivity:STARtlevel............................................................669
CONFigure:BLUetooth:MEAS<i>:RXQuality:SENSitivity:STEPsize..............................................................670
CONFigure:BLUetooth:MEAS<i>:RXQuality:SPOTcheck:LEVel................................................................... 670
CONFigure:BLUetooth:MEAS<i>:TRX:RESult[:ALL].....................................................................................675
FETCh:BLUetooth:MEAS<i>:DTMode:RXQuality:PER:LENergy:LE1M?......................................................690
FETCh:BLUetooth:MEAS<i>:DTMode:RXQuality:PER:LENergy:LE2M?......................................................690
FETCh:BLUetooth:MEAS<i>:DTMode:RXQuality:PER:LENergy:LRANge?................................................. 690
FETCh:BLUetooth:MEAS<i>:DTMode:RXQuality:PER:STATe?....................................................................688
FETCh:BLUetooth:MEAS<i>:DTMode:RXQuality:SEARch:PER:LENergy:LE1M?....................................... 694
FETCh:BLUetooth:MEAS<i>:DTMode:RXQuality:SEARch:PER:LENergy:LE2M?....................................... 694
FETCh:BLUetooth:MEAS<i>:DTMode:RXQuality:SEARch:PER:LENergy:LRANge?...................................694
FETCh:BLUetooth:MEAS<i>:DTMode:RXQuality:SEARch:PER:STATe?..................................................... 691
FETCh:BLUetooth:MEAS<i>:ISIGnal:ADETected:AADDress:LENergy[:LE1M]?.......................................... 569
FETCh:BLUetooth:MEAS<i>:ISIGnal:ADETected:CODing:LENergy:LRANge?............................................ 573
FETCh:BLUetooth:MEAS<i>:ISIGnal:ADETected:CTE:LENergy:LE1M:TYPE?........................................... 575
FETCh:BLUetooth:MEAS<i>:ISIGnal:ADETected:CTE:LENergy:LE1M:UNITs?........................................... 575
FETCh:BLUetooth:MEAS<i>:ISIGnal:ADETected:CTE:LENergy:LE2M:TYPE?........................................... 575
FETCh:BLUetooth:MEAS<i>:ISIGnal:ADETected:CTE:LENergy:LE2M:UNITs?........................................... 575
FETCh:BLUetooth:MEAS<i>:ISIGnal:ADETected:NOSLots:BRATe?............................................................576
FETCh:BLUetooth:MEAS<i>:ISIGnal:ADETected:NOSLots:EDRate?.......................................................... 576
FETCh:BLUetooth:MEAS<i>:ISIGnal:ADETected:PATTern:LENergy:LE2M?............................................... 572
FETCh:BLUetooth:MEAS<i>:ISIGnal:ADETected:PATTern:LENergy:LRANge?........................................... 573
FETCh:BLUetooth:MEAS<i>:ISIGnal:ADETected:PATTern:LENergy[:LE1M]?............................................. 572
FETCh:BLUetooth:MEAS<i>:ISIGnal:ADETected:PATTern[:BRATe]?........................................................... 571
FETCh:BLUetooth:MEAS<i>:ISIGnal:ADETected:PLENgth:BRATe?............................................................ 573
FETCh:BLUetooth:MEAS<i>:ISIGnal:ADETected:PLENgth:EDRate?.......................................................... 574
FETCh:BLUetooth:MEAS<i>:ISIGnal:ADETected:PLENgth:LENergy:LE2M?...............................................574
FETCh:BLUetooth:MEAS<i>:ISIGnal:ADETected:PLENgth:LENergy:LRANge?.......................................... 574
FETCh:BLUetooth:MEAS<i>:ISIGnal:ADETected:PLENgth:LENergy[:LE1M]?.............................................574
FETCh:BLUetooth:MEAS<i>:ISIGnal:ADETected:PTYPe:BRATe?............................................................... 569
FETCh:BLUetooth:MEAS<i>:ISIGnal:ADETected:PTYPe:EDRate?............................................................. 570
FETCh:BLUetooth:MEAS<i>:ISIGnal:ADETected:PTYPe:LENergy:LE2M?..................................................570
FETCh:BLUetooth:MEAS<i>:ISIGnal:ADETected:PTYPe:LENergy:LRANge?............................................. 571
FETCh:BLUetooth:MEAS<i>:ISIGnal:ADETected:PTYPe:LENergy[:LE1M]?................................................570
FETCh:BLUetooth:MEAS<i>:MEValuation:FRANge:BRATe:CURRent?....................................................... 630
FETCh:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>:MODulation:AVERage?.............................652
FETCh:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>:MODulation:CURRent:EXTended?........... 650
FETCh:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>:MODulation:CURRent?.............................648
FETCh:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>:MODulation:MAXimum?............................652
FETCh:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>:MODulation:MINimum?.............................654
FETCh:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>:MODulation:SDEViation:EXTended?........ 656
FETCh:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>:MODulation:SDEViation?..........................655
FETCh:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>:PVTime:AVERage?................................... 659
FETCh:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>:PVTime:CURRent?................................... 659
FETCh:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>:PVTime:MAXimum?.................................. 659
FETCh:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>:PVTime:MINimum?................................... 659
FETCh:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>:SACP[:PTX]?............................................ 660
FETCh:BLUetooth:MEAS<i>:MEValuation:LIST:SEGMent<no>:SOBW:MAXimum?....................................662
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:BRATe:AVERage?..................................................589
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:BRATe:CURRent?..................................................589
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:BRATe:MAXimum?.................................................589
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:BRATe:MINimum?..................................................591
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:BRATe:SDEViation?............................................... 592
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:BRATe:XMAXimum?.............................................. 589
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:BRATe:XMINimum?............................................... 589
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:BRATe:YIELd?....................................................... 593
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:CTE:LENergy:LE1M:AVERage?............................ 599
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:CTE:LENergy:LE1M:CURRent?............................ 599
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:CTE:LENergy:LE1M:MAXimum?........................... 599
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:CTE:LENergy:LE1M:SDEViation?......................... 599
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:CTE:LENergy:LE1M:XMAXimum?.........................599
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:CTE:LENergy:LE1M:XMINimum?..........................599
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:CTE:LENergy:LE2M:AVERage?............................ 599
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:CTE:LENergy:LE2M:CURRent?............................ 599
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:CTE:LENergy:LE2M:MAXimum?........................... 599
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:CTE:LENergy:LE2M:SDEViation?......................... 599
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:CTE:LENergy:LE2M:XMAXimum?.........................599
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:CTE:LENergy:LE2M:XMINimum?..........................599
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:EDRate:AVERage?................................................ 594
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:EDRate:CURRent?................................................ 594
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:EDRate:MAXimum?............................................... 594
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:EDRate:SDEViation?............................................. 595
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LE2M:AVERage?.................................... 602
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LE2M:CURRent?.................................... 602
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LE2M:MAXimum?................................... 602
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LE2M:MINimum?.................................... 606
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LE2M:SDEViation?................................. 608
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LE2M:XMAXimum?.................................602
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LE2M:XMINimum?.................................. 602
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LE2M:YIELd?.......................................... 610
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LRANge:AVERage?................................ 604
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LRANge:CURRent?................................ 604
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LRANge:MAXimum?............................... 604
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LRANge:MINimum?................................ 607
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LRANge:SDEViation?............................. 609
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LRANge:XMAXimum?.............................604
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LRANge:XMINimum?..............................604
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy[:LE1M]:AVERage?.................................. 601
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy[:LE1M]:CURRent?.................................. 601
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy[:LE1M]:MAXimum?................................. 601
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy[:LE1M]:MINimum?.................................. 605
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy[:LE1M]:SDEViation?............................... 608
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy[:LE1M]:XMAXimum?...............................601
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy[:LE1M]:XMINimum?................................ 601
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy[:LE1M]:YIELd?........................................ 610
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:CLASsic:AVERage?.................................614
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:CLASsic:CURRent?................................. 614
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:CLASsic:MAXimum?................................614
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:CLASsic:SDEViation?.............................. 616
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:CLASsic:XMAXimum?............................. 614
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:CLASsic:XMINimum?...............................614
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:LE2M:AVERage?...................... 618
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:LE2M:CURRent?...................... 618
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:LE2M:MAXimum?..................... 619
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:LE2M:MINimum?...................... 623
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:LE2M:SDEViation?................... 626
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:LE2M:XMAXimum?...................619
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:LE2M:XMINimum?.................... 618
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:LRANge:AVERage?.................. 620
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:LRANge:CURRent?.................. 620
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:LRANge:MAXimum?................. 620
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:LRANge:MINimum?.................. 624
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:LRANge:SDEViation?............... 627
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:LRANge:XMAXimum?...............620
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:LRANge:XMINimum?................620
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy[:LE1M]:AVERage?.................... 617
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy[:LE1M]:CURRent?.................... 617
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy[:LE1M]:MAXimum?................... 617
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy[:LE1M]:MINimum?.................... 622
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy[:LE1M]:SDEViation?................. 625
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy[:LE1M]:XMAXimum?.................617
FETCh:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy[:LE1M]:XMINimum?.................. 617
FETCh:BLUetooth:MEAS<i>:MEValuation:PENCoding:EDRate:CURRent:C?.............................................636
FETCh:BLUetooth:MEAS<i>:MEValuation:PENCoding:SSEQuence:EDRate:CURRent?............................637
FETCh:BLUetooth:MEAS<i>:MEValuation:PVTime:BRATe:AVERage?........................................................ 577
FETCh:BLUetooth:MEAS<i>:MEValuation:PVTime:BRATe:CURRent?........................................................ 577
FETCh:BLUetooth:MEAS<i>:MEValuation:PVTime:BRATe:MAXimum?....................................................... 577
FETCh:BLUetooth:MEAS<i>:MEValuation:PVTime:BRATe:MINimum?........................................................ 577
FETCh:BLUetooth:MEAS<i>:MEValuation:PVTime:EDRate:AVERage?...................................................... 578
FETCh:BLUetooth:MEAS<i>:MEValuation:PVTime:EDRate:CURRent?.......................................................578
FETCh:BLUetooth:MEAS<i>:MEValuation:PVTime:EDRate:MAXimum?..................................................... 578
FETCh:BLUetooth:MEAS<i>:MEValuation:PVTime:EDRate:MINimum?.......................................................578
FETCh:BLUetooth:MEAS<i>:MEValuation:PVTime:LENergy:LE2M:AVERage?...........................................582
FETCh:BLUetooth:MEAS<i>:MEValuation:PVTime:LENergy:LE2M:CURRent?...........................................582
FETCh:BLUetooth:MEAS<i>:MEValuation:PVTime:LENergy:LE2M:MAXimum?..........................................582
FETCh:BLUetooth:MEAS<i>:MEValuation:PVTime:LENergy:LE2M:MINimum?...........................................582
FETCh:BLUetooth:MEAS<i>:MEValuation:PVTime:LENergy:LRANge:AVERage?...................................... 582
FETCh:BLUetooth:MEAS<i>:MEValuation:PVTime:LENergy:LRANge:CURRent?.......................................582
FETCh:BLUetooth:MEAS<i>:MEValuation:PVTime:LENergy:LRANge:MAXimum?..................................... 582
FETCh:BLUetooth:MEAS<i>:MEValuation:PVTime:LENergy:LRANge:MINimum?.......................................582
FETCh:BLUetooth:MEAS<i>:MEValuation:PVTime:LENergy[:LE1M]:AVERage?.........................................581
FETCh:BLUetooth:MEAS<i>:MEValuation:PVTime:LENergy[:LE1M]:CURRent?.........................................581
FETCh:BLUetooth:MEAS<i>:MEValuation:PVTime:LENergy[:LE1M]:MAXimum?........................................581
FETCh:BLUetooth:MEAS<i>:MEValuation:PVTime:LENergy[:LE1M]:MINimum?.........................................581
FETCh:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:CLASsic:AVERage?....................................... 585
FETCh:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:CLASsic:CURRent?....................................... 585
FETCh:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:CLASsic:MAXimum?...................................... 585
FETCh:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:CLASsic:MINimum?....................................... 585
FETCh:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:LENergy:LE2M:AVERage?.............................586
FETCh:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:LENergy:LE2M:CURRent?.............................586
FETCh:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:LENergy:LE2M:MAXimum?............................586
FETCh:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:LENergy:LE2M:MINimum?.............................586
FETCh:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:LENergy:LRANge:AVERage?........................ 586
FETCh:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:LENergy:LRANge:CURRent?.........................586
FETCh:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:LENergy:LRANge:MAXimum?....................... 586
FETCh:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:LENergy:LRANge:MINimum?.........................586
FETCh:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:LENergy[:LE1M]:AVERage?...........................587
FETCh:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:LENergy[:LE1M]:CURRent?...........................587
FETCh:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:LENergy[:LE1M]:MAXimum?..........................587
FETCh:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:LENergy[:LE1M]:MINimum?...........................587
FETCh:BLUetooth:MEAS<i>:MEValuation:SACP:BRATe[:PTX]?................................................................. 629
FETCh:BLUetooth:MEAS<i>:MEValuation:SACP:LENergy:LE2M?.............................................................. 633
FETCh:BLUetooth:MEAS<i>:MEValuation:SACP:LENergy:LRANge?..........................................................633
FETCh:BLUetooth:MEAS<i>:MEValuation:SACP:LENergy[:LE1M]?............................................................ 632
FETCh:BLUetooth:MEAS<i>:MEValuation:SACP:NMODe:CLASsic?...........................................................634
FETCh:BLUetooth:MEAS<i>:MEValuation:SACP:NMODe:LENergy:LE2M?................................................ 635
FETCh:BLUetooth:MEAS<i>:MEValuation:SACP:NMODe:LENergy:LRANge?............................................635
FETCh:BLUetooth:MEAS<i>:MEValuation:SACP:NMODe:LENergy[:LE1M]?.............................................. 635
FETCh:BLUetooth:MEAS<i>:MEValuation:SGACp:EDRate[:PTX]?............................................................. 631
FETCh:BLUetooth:MEAS<i>:MEValuation:SOBW:BRATe:MAXimum?.........................................................628
FETCh:BLUetooth:MEAS<i>:MEValuation:STATe:ALL?................................................................................515
FETCh:BLUetooth:MEAS<i>:MEValuation:STATe?....................................................................................... 515
FETCh:BLUetooth:MEAS<i>:MEValuation:TRACe:DEVMagnitude:AVERage?............................................641
FETCh:BLUetooth:MEAS<i>:MEValuation:TRACe:DEVMagnitude:CURRent?............................................641
FETCh:BLUetooth:MEAS<i>:MEValuation:TRACe:DEVMagnitude:MAXimum?...........................................641
FETCh:BLUetooth:MEAS<i>:MEValuation:TRACe:FDEViation:AVERage?..................................................640
FETCh:BLUetooth:MEAS<i>:MEValuation:TRACe:FDEViation:CURRent?..................................................640
FETCh:BLUetooth:MEAS<i>:MEValuation:TRACe:FDEViation:MAXimum?.................................................640
FETCh:BLUetooth:MEAS<i>:MEValuation:TRACe:FDEViation:MINimum?..................................................640
FETCh:BLUetooth:MEAS<i>:MEValuation:TRACe:FRANge:AVERage?...................................................... 644
FETCh:BLUetooth:MEAS<i>:MEValuation:TRACe:IQABs?.......................................................................... 642
FETCh:BLUetooth:MEAS<i>:MEValuation:TRACe:IQDiff?........................................................................... 642
FETCh:BLUetooth:MEAS<i>:MEValuation:TRACe:IQERr?.......................................................................... 642
FETCh:BLUetooth:MEAS<i>:MEValuation:TRACe:PDEViation:MAXimum?................................................ 639
FETCh:BLUetooth:MEAS<i>:MEValuation:TRACe:PDEViation:MINimum?..................................................639
FETCh:BLUetooth:MEAS<i>:MEValuation:TRACe:PDIFference:AVERage?................................................641
FETCh:BLUetooth:MEAS<i>:MEValuation:TRACe:PDIFference:CURRent?................................................641
FETCh:BLUetooth:MEAS<i>:MEValuation:TRACe:PDIFference:MAXimum?...............................................641
FETCh:BLUetooth:MEAS<i>:MEValuation:TRACe:PVTime:AVERage?....................................................... 638
FETCh:BLUetooth:MEAS<i>:MEValuation:TRACe:PVTime:CURRent?....................................................... 638
FETCh:BLUetooth:MEAS<i>:MEValuation:TRACe:PVTime:MAXimum?...................................................... 638
FETCh:BLUetooth:MEAS<i>:MEValuation:TRACe:PVTime:MINimum?....................................................... 638
FETCh:BLUetooth:MEAS<i>:MEValuation:TRACe:SACP:AVERage?.......................................................... 645
FETCh:BLUetooth:MEAS<i>:MEValuation:TRACe:SACP:CURRent?.......................................................... 645
FETCh:BLUetooth:MEAS<i>:MEValuation:TRACe:SACP:MAXimum?......................................................... 645
FETCh:BLUetooth:MEAS<i>:MEValuation:TRACe:SACP[:PTX]?.................................................................644
FETCh:BLUetooth:MEAS<i>:MEValuation:TRACe:SGACp:AVERage?........................................................646
FETCh:BLUetooth:MEAS<i>:MEValuation:TRACe:SGACp:CURRent?........................................................646
FETCh:BLUetooth:MEAS<i>:MEValuation:TRACe:SGACp:MAXimum?.......................................................646
FETCh:BLUetooth:MEAS<i>:MEValuation:TRACe:SGACp[:PTX]?.............................................................. 645
FETCh:BLUetooth:MEAS<i>:MEValuation:TRACe:SOBW:AVERage?......................................................... 643
FETCh:BLUetooth:MEAS<i>:MEValuation:TRACe:SOBW:CURRent?......................................................... 643
FETCh:BLUetooth:MEAS<i>:MEValuation:TRACe:SOBW:MAXimum?........................................................643
FETCh:BLUetooth:MEAS<i>:MEValuation:TRACe:SPOWer:AVERage?......................................................638
FETCh:BLUetooth:MEAS<i>:MEValuation:TRACe:SPOWer:CURRent?......................................................638
FETCh:BLUetooth:MEAS<i>:MEValuation:TRACe:SPOWer:MAXimum?.....................................................638
FETCh:BLUetooth:MEAS<i>:MEValuation:TRACe:SPOWer:MINimum?......................................................638
FETCh:BLUetooth:MEAS<i>:RXQuality:ADETected:AADDress?................................................................. 671
FETCh:BLUetooth:MEAS<i>:RXQuality:PER:RXPackets?........................................................................... 672
FETCh:BLUetooth:MEAS<i>:RXQuality:PER?..............................................................................................671
FETCh:BLUetooth:MEAS<i>:RXQuality:SENSitivity?................................................................................... 672
FETCh:BLUetooth:MEAS<i>:RXQuality:SPOTcheck?.................................................................................. 672
FETCh:BLUetooth:MEAS<i>:RXQuality:STATe:ALL?................................................................................... 664
FETCh:BLUetooth:MEAS<i>:RXQuality:STATe?...........................................................................................664
FETCh:BLUetooth:MEAS<i>:TRX:ACP?.......................................................................................................676
FETCh:BLUetooth:MEAS<i>:TRX:MODulation?........................................................................................... 677
FETCh:BLUetooth:MEAS<i>:TRX:POWer?.................................................................................................. 678
FETCh:BLUetooth:MEAS<i>:TRX:SPOT?.................................................................................................... 679
FETCh:BLUetooth:MEAS<i>:TRX:STATe:ALL?............................................................................................ 674
FETCh:BLUetooth:MEAS<i>:TRX:STATe?....................................................................................................674
INITiate:BLUetooth:MEAS<i>:DTMode:RXQuality:PER................................................................................687
INITiate:BLUetooth:MEAS<i>:DTMode:RXQuality:SEARch:PER................................................................. 691
INITiate:BLUetooth:MEAS<i>:MEValuation................................................................................................... 514
INITiate:BLUetooth:MEAS<i>:RXQuality....................................................................................................... 663
INITiate:BLUetooth:MEAS<i>:TRX................................................................................................................ 673
READ:BLUetooth:MEAS<i>:DTMode:RXQuality:PER:LENergy:LE1M?....................................................... 690
READ:BLUetooth:MEAS<i>:DTMode:RXQuality:PER:LENergy:LE2M?....................................................... 690
READ:BLUetooth:MEAS<i>:DTMode:RXQuality:PER:LENergy:LRANge?...................................................690
READ:BLUetooth:MEAS<i>:DTMode:RXQuality:SEARch:PER:LENergy:LE1M?........................................ 694
READ:BLUetooth:MEAS<i>:DTMode:RXQuality:SEARch:PER:LENergy:LE2M?........................................ 694
READ:BLUetooth:MEAS<i>:DTMode:RXQuality:SEARch:PER:LENergy:LRANge?.................................... 694
READ:BLUetooth:MEAS<i>:MEValuation:FRANge:BRATe:CURRent?........................................................ 630
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:BRATe:AVERage?................................................... 589
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:BRATe:CURRent?................................................... 589
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:BRATe:MAXimum?.................................................. 589
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:BRATe:MINimum?................................................... 591
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:BRATe:SDEViation?................................................ 592
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:BRATe:XMAXimum?................................................589
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:BRATe:XMINimum?.................................................589
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:CTE:LENergy:LE1M:AVERage?............................. 600
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:CTE:LENergy:LE1M:CURRent?..............................600
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:CTE:LENergy:LE1M:MAXimum?............................ 600
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:CTE:LENergy:LE1M:SDEViation?...........................600
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:CTE:LENergy:LE1M:XMAXimum?.......................... 600
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:CTE:LENergy:LE1M:XMINimum?........................... 600
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:CTE:LENergy:LE2M:AVERage?............................. 600
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:CTE:LENergy:LE2M:CURRent?..............................600
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:CTE:LENergy:LE2M:MAXimum?............................ 600
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:CTE:LENergy:LE2M:SDEViation?...........................600
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:CTE:LENergy:LE2M:XMAXimum?.......................... 600
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:CTE:LENergy:LE2M:XMINimum?........................... 600
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:EDRate:AVERage?................................................. 594
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:EDRate:CURRent?..................................................594
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:EDRate:MAXimum?................................................ 594
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:EDRate:SDEViation?...............................................595
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LE2M:AVERage?......................................602
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LE2M:CURRent?......................................602
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LE2M:MAXimum?.....................................602
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LE2M:MINimum?......................................606
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LE2M:SDEViation?...................................608
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LE2M:XMAXimum?.................................. 602
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LE2M:XMINimum?................................... 602
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LRANge:AVERage?................................. 604
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LRANge:CURRent?..................................604
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LRANge:MAXimum?................................ 604
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LRANge:MINimum?..................................607
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LRANge:SDEViation?...............................609
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LRANge:XMAXimum?.............................. 604
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy:LRANge:XMINimum?............................... 604
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy[:LE1M]:AVERage?....................................601
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy[:LE1M]:CURRent?....................................601
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy[:LE1M]:MAXimum?...................................601
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy[:LE1M]:MINimum?....................................605
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy[:LE1M]:SDEViation?.................................608
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy[:LE1M]:XMAXimum?................................ 601
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:LENergy[:LE1M]:XMINimum?................................. 601
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:CLASsic:AVERage?.................................. 614
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:CLASsic:CURRent?.................................. 614
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:CLASsic:MAXimum?................................. 614
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:CLASsic:SDEViation?............................... 616
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:CLASsic:XMAXimum?...............................614
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:CLASsic:XMINimum?................................ 614
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:LE2M:AVERage?........................619
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:LE2M:CURRent?........................617
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:LE2M:MAXimum?.......................619
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:LE2M:MINimum?........................623
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:LE2M:SDEViation?.....................626
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:LE2M:XMAXimum?.................... 619
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:LE2M:XMINimum?..................... 619
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:LRANge:AVERage?................... 621
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:LRANge:CURRent?....................620
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:LRANge:MAXimum?.................. 621
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:LRANge:MINimum?....................624
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:LRANge:SDEViation?.................627
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:LRANge:XMAXimum?................ 621
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy:LRANge:XMINimum?................. 621
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy[:LE1M]:AVERage?......................617
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy[:LE1M]:CURRent?......................617
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy[:LE1M]:MAXimum?.....................617
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy[:LE1M]:MINimum?......................622
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy[:LE1M]:SDEViation?...................625
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy[:LE1M]:XMAXimum?.................. 617
READ:BLUetooth:MEAS<i>:MEValuation:MODulation:NMODe:LENergy[:LE1M]:XMINimum?................... 617
READ:BLUetooth:MEAS<i>:MEValuation:PENCoding:EDRate:CURRent?..................................................636
READ:BLUetooth:MEAS<i>:MEValuation:PENCoding:SSEQuence:EDRate:CURRent?............................. 637
READ:BLUetooth:MEAS<i>:MEValuation:PVTime:BRATe:AVERage?......................................................... 577
READ:BLUetooth:MEAS<i>:MEValuation:PVTime:BRATe:CURRent?..........................................................577
READ:BLUetooth:MEAS<i>:MEValuation:PVTime:BRATe:MAXimum?........................................................ 577
READ:BLUetooth:MEAS<i>:MEValuation:PVTime:BRATe:MINimum?..........................................................577
READ:BLUetooth:MEAS<i>:MEValuation:PVTime:EDRate:AVERage?........................................................578
READ:BLUetooth:MEAS<i>:MEValuation:PVTime:EDRate:CURRent?........................................................ 578
READ:BLUetooth:MEAS<i>:MEValuation:PVTime:EDRate:MAXimum?.......................................................578
READ:BLUetooth:MEAS<i>:MEValuation:PVTime:EDRate:MINimum?........................................................ 578
READ:BLUetooth:MEAS<i>:MEValuation:PVTime:LENergy:LE2M:AVERage?............................................ 582
READ:BLUetooth:MEAS<i>:MEValuation:PVTime:LENergy:LE2M:CURRent?............................................ 582
READ:BLUetooth:MEAS<i>:MEValuation:PVTime:LENergy:LE2M:MAXimum?........................................... 582
READ:BLUetooth:MEAS<i>:MEValuation:PVTime:LENergy:LE2M:MINimum?............................................ 582
READ:BLUetooth:MEAS<i>:MEValuation:PVTime:LENergy:LRANge:AVERage?........................................582
READ:BLUetooth:MEAS<i>:MEValuation:PVTime:LENergy:LRANge:CURRent?........................................ 582
READ:BLUetooth:MEAS<i>:MEValuation:PVTime:LENergy:LRANge:MAXimum?.......................................582
READ:BLUetooth:MEAS<i>:MEValuation:PVTime:LENergy:LRANge:MINimum?........................................ 582
READ:BLUetooth:MEAS<i>:MEValuation:PVTime:LENergy[:LE1M]:AVERage?.......................................... 581
READ:BLUetooth:MEAS<i>:MEValuation:PVTime:LENergy[:LE1M]:CURRent?.......................................... 581
READ:BLUetooth:MEAS<i>:MEValuation:PVTime:LENergy[:LE1M]:MAXimum?......................................... 581
READ:BLUetooth:MEAS<i>:MEValuation:PVTime:LENergy[:LE1M]:MINimum?.......................................... 581
READ:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:CLASsic:AVERage?.........................................585
READ:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:CLASsic:CURRent?.........................................585
READ:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:CLASsic:MAXimum?........................................585
READ:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:CLASsic:MINimum?.........................................585
READ:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:LENergy:LE2M:AVERage?.............................. 587
READ:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:LENergy:LE2M:CURRent?.............................. 587
READ:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:LENergy:LE2M:MAXimum?............................. 587
READ:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:LENergy:LE2M:MINimum?.............................. 587
READ:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:LENergy:LRANge:AVERage?..........................587
READ:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:LENergy:LRANge:CURRent?.......................... 587
READ:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:LENergy:LRANge:MAXimum?.........................587
READ:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:LENergy:LRANge:MINimum?.......................... 587
READ:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:LENergy[:LE1M]:AVERage?............................ 587
READ:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:LENergy[:LE1M]:CURRent?............................ 587
READ:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:LENergy[:LE1M]:MAXimum?........................... 587
READ:BLUetooth:MEAS<i>:MEValuation:PVTime:NMODe:LENergy[:LE1M]:MINimum?............................ 587
READ:BLUetooth:MEAS<i>:MEValuation:SACP:BRATe[:PTX]?...................................................................629
READ:BLUetooth:MEAS<i>:MEValuation:SACP:LENergy:LE2M?............................................................... 633
READ:BLUetooth:MEAS<i>:MEValuation:SACP:LENergy:LRANge?........................................................... 633
READ:BLUetooth:MEAS<i>:MEValuation:SACP:LENergy[:LE1M]?............................................................. 632
READ:BLUetooth:MEAS<i>:MEValuation:SACP:NMODe:CLASsic?............................................................ 634
READ:BLUetooth:MEAS<i>:MEValuation:SACP:NMODe:LENergy:LE2M?................................................. 635
READ:BLUetooth:MEAS<i>:MEValuation:SACP:NMODe:LENergy:LRANge?............................................. 635
READ:BLUetooth:MEAS<i>:MEValuation:SACP:NMODe:LENergy[:LE1M]?............................................... 635
READ:BLUetooth:MEAS<i>:MEValuation:SGACp:EDRate[:PTX]?...............................................................631
READ:BLUetooth:MEAS<i>:MEValuation:SOBW:BRATe:MAXimum?.......................................................... 628
READ:BLUetooth:MEAS<i>:MEValuation:TRACe:DEVMagnitude:AVERage?............................................. 641
READ:BLUetooth:MEAS<i>:MEValuation:TRACe:DEVMagnitude:CURRent?............................................. 641
READ:BLUetooth:MEAS<i>:MEValuation:TRACe:DEVMagnitude:MAXimum?............................................ 641
READ:BLUetooth:MEAS<i>:MEValuation:TRACe:FDEViation:AVERage?................................................... 640
READ:BLUetooth:MEAS<i>:MEValuation:TRACe:FDEViation:CURRent?................................................... 640
READ:BLUetooth:MEAS<i>:MEValuation:TRACe:FDEViation:MAXimum?.................................................. 640
READ:BLUetooth:MEAS<i>:MEValuation:TRACe:FDEViation:MINimum?................................................... 640
READ:BLUetooth:MEAS<i>:MEValuation:TRACe:FRANge:AVERage?....................................................... 644
READ:BLUetooth:MEAS<i>:MEValuation:TRACe:IQABs?........................................................................... 642
READ:BLUetooth:MEAS<i>:MEValuation:TRACe:IQDiff?.............................................................................642
READ:BLUetooth:MEAS<i>:MEValuation:TRACe:IQERr?............................................................................642
READ:BLUetooth:MEAS<i>:MEValuation:TRACe:PDEViation:MAXimum?..................................................639
READ:BLUetooth:MEAS<i>:MEValuation:TRACe:PDEViation:MINimum?................................................... 639
READ:BLUetooth:MEAS<i>:MEValuation:TRACe:PDIFference:AVERage?................................................. 641
READ:BLUetooth:MEAS<i>:MEValuation:TRACe:PDIFference:CURRent?................................................. 641
READ:BLUetooth:MEAS<i>:MEValuation:TRACe:PDIFference:MAXimum?................................................ 641
READ:BLUetooth:MEAS<i>:MEValuation:TRACe:PVTime:AVERage?.........................................................638
READ:BLUetooth:MEAS<i>:MEValuation:TRACe:PVTime:CURRent?.........................................................638
READ:BLUetooth:MEAS<i>:MEValuation:TRACe:PVTime:MAXimum?........................................................638
READ:BLUetooth:MEAS<i>:MEValuation:TRACe:PVTime:MINimum?.........................................................638
READ:BLUetooth:MEAS<i>:MEValuation:TRACe:SACP:AVERage?........................................................... 646
READ:BLUetooth:MEAS<i>:MEValuation:TRACe:SACP:CURRent?............................................................645
READ:BLUetooth:MEAS<i>:MEValuation:TRACe:SACP:MAXimum?.......................................................... 646
READ:BLUetooth:MEAS<i>:MEValuation:TRACe:SACP[:PTX]?.................................................................. 644
READ:BLUetooth:MEAS<i>:MEValuation:TRACe:SGACp:AVERage?......................................................... 647
READ:BLUetooth:MEAS<i>:MEValuation:TRACe:SGACp:CURRent?......................................................... 646
READ:BLUetooth:MEAS<i>:MEValuation:TRACe:SGACp:MAXimum?........................................................ 647
READ:BLUetooth:MEAS<i>:MEValuation:TRACe:SGACp[:PTX]?................................................................645
READ:BLUetooth:MEAS<i>:MEValuation:TRACe:SOBW:AVERage?.......................................................... 643
READ:BLUetooth:MEAS<i>:MEValuation:TRACe:SOBW:CURRent?.......................................................... 643
READ:BLUetooth:MEAS<i>:MEValuation:TRACe:SOBW:MAXimum?......................................................... 643
READ:BLUetooth:MEAS<i>:MEValuation:TRACe:SPOWer:AVERage?....................................................... 638
READ:BLUetooth:MEAS<i>:MEValuation:TRACe:SPOWer:CURRent?....................................................... 638
READ:BLUetooth:MEAS<i>:MEValuation:TRACe:SPOWer:MAXimum?...................................................... 639
READ:BLUetooth:MEAS<i>:MEValuation:TRACe:SPOWer:MINimum?....................................................... 639
ROUTe:BLUetooth:MEAS<i>:SCENario:CSPath...........................................................................................497
ROUTe:BLUetooth:MEAS<i>:SCENario:SALone.......................................................................................... 497
ROUTe:BLUetooth:MEAS<i>:SCENario?...................................................................................................... 498
ROUTe:BLUetooth:MEAS<i>?.......................................................................................................................497
SENSe:BLUetooth:MEAS<i>:ELOGging:ALL?..............................................................................................684
SENSe:BLUetooth:MEAS<i>:ELOGging:LAST?........................................................................................... 684
STOP:BLUetooth:MEAS<i>:DTMode:RXQuality:PER...................................................................................687
STOP:BLUetooth:MEAS<i>:DTMode:RXQuality:SEARch:PER.................................................................... 691
STOP:BLUetooth:MEAS<i>:MEValuation......................................................................................................514
STOP:BLUetooth:MEAS<i>:RXQuality..........................................................................................................663
STOP:BLUetooth:MEAS<i>:TRX...................................................................................................................673
TRIGger:BLUetooth:MEAS<i>:MEValuation:CATalog:SOURce?.................................................................. 541
TRIGger:BLUetooth:MEAS<i>:MEValuation:SOURce...................................................................................542
TRIGger:BLUetooth:MEAS<i>:MEValuation:THReshold...............................................................................542
TRIGger:BLUetooth:MEAS<i>:MEValuation:TOUT....................................................................................... 542
Index
Symbols D
(ωo + ωi)max ...................................................................399 Data sheet ......................................................................... 10
20 dB bandwidth ............................................................. 390 Detaching .......................................................................... 37
99% DEVM ...................................................................... 399 Detection mode ............................................................... 433
Δf2 99.9% ................................................................ 387, 411 DEVM .............................................................................. 396
Δf2 avg / Δf1 avg ..................................................... 387, 411 Calculation ................................................................ 357
ωi .....................................................................................399 Differential error vector magnitude (DEVM) .................... 396
ωomax .............................................................................399 Direct test mode ................................................................ 28
LE ............................................................................... 28
A Dirty transmitter
Bluetooth signaling ..................................................... 78
Access address Display settings
Bluetooth measurements .......................................... 437 Bluetooth measurements .......................................... 464
ACP Documentation overview ..................................................... 9
BR ............................................................................. 392 DPSK power .................................................................... 397
EDR .......................................................................... 401 DPSK power – GFSK power ........................................... 397
LE ............................................................................. 415
ACP measurement mode ................................................ 444 E
Application cards ............................................................... 10
Application notes ............................................................... 10 EDR
Application sheet Bluetooth signaling ..................................................... 91
Bluetooth combined signal path measurement ......... 376 EDR differential phase encoding .................................... 400
BR measurements .................................................... 363 Enhanced power control mode
EDR measurements ................................................. 367 Bluetooth signaling ..................................................... 98
LE measurements ..................................................... 370 EUT control
Assign views Bluetooth signaling ..................................................... 49
Bluetooth ................................................................... 446 Expected nominal power ................................................. 431
Audio profiles Bluetooth signaling ..................................................... 77
Bluetooth signaling ..................................................... 23 External attenuation (input)
Auto synchronization ....................................................... 434 Bluetooth measurements .......................................... 428
Average power ................................................ 385, 406, 409 Bluetooth signaling ..................................................... 74
External attenuation (output)
B Bluetooth signaling ..................................................... 74
Help ..................................................................................... 9 P
Hopping
Bluetooth measurements .......................................... 430 Packet type ..................................................................... 436
Bluetooth signaling ..................................................... 92
I Packets
Bluetooth measurement PER ................................... 449
Idle .................................................................................... 40 Bluetooth signaling BER ................................... 219, 266
Initial frequency drift ........................................................ 413 Bluetooth signaling PER ................................... 242, 266
Input signal settings ........................................................ 432 Paging ............................................................................... 37
Inquiring ............................................................................ 37 Paging settings
Integrity Bluetooth signaling ..................................................... 85
Bluetooth measurement PER ................................... 450 Pattern type
Bluetooth measurement PER search ....................... 450 Bluetooth measurements .......................................... 438
Integrity LE Bluetooth signaling ..................................................... 93
Bluetooth signaling PER ................................... 243, 268 Payload length
IQ constellation diagrams Bluetooth measurements .......................................... 437
Calculation ................................................................ 359 Bluetooth signaling ..................................................... 93
Peak DEVM ..................................................................... 399
L Peak emission ................................................................. 391
Peak power ............................................................. 385, 409
LAP ................................................................................. 434 Phase difference ............................................................. 396
Leakage power ........................................................385, 409 Calculation ................................................................ 358
Level step Mapping tables ......................................................... 358
Bluetooth measurement PER search ....................... 450 Poll period
Bluetooth signaling BER search/ PER search .......... 268 Bluetooth signaling ..................................................... 94
Limit Power control
Bluetooth measurement PER ................................... 449 Softkey ........................................................................ 60
Bluetooth signaling BER ................................... 219, 267 Programming
Bluetooth signaling PER ........................................... 242 Bluetooth signaling ..................................................... 99
Limits
Bluetooth measurements .......................................... 454 Q
Link info
Bluetooth signaling ..................................................... 51 Quick start guide ................................................................. 9
List mode
Bluetooth measurements .......................................... 340 R
Loopback test .................................................................... 21
Release notes ................................................................... 10
M Repetition
Bluetooth measurements .......................................... 442
Maximum BER Bluetooth signaling BER ........................................... 219
Bluetooth signaling BER ................................... 219, 267 Bluetooth signaling PER ........................................... 241
Maximum drift rate .................................................. 388, 413 RF output
Maximum PER Bluetooth signaling ..................................................... 73
Bluetooth measurement PER ................................... 449 RF power
Bluetooth signaling PER ................................... 242, 267 Bluetooth signaling ..................................................... 77
Measure mode RF routing ....................................................................... 428
Bluetooth measurements .......................................... 430 RMS DEVM ..................................................................... 399
Bluetooth signaling PER ................................... 243, 268 Rx measurement
Measure on exception Bluetooth measurement .................................... 334, 339
Bluetooth measurements .......................................... 443
Measurement control S
Bluetooth signaling BER ................................... 216, 261
Bluetooth signaling PER ........................................... 237 Safety instructions ............................................................. 10
Scenario
N Bluetooth measurement ............................................ 428
Select as fixed target
NAP ................................................................................. 434 Bluetooth signaling ..................................................... 65
No. of exceptions ............................................ 394, 402, 416 Select menu
No. of off slots Bluetooth signaling ..................................................... 64
Bluetooth measurements .......................................... 441 Selected as fixed target
Bluetooth signaling ..................................................... 98
O Signal characteristics
Bluetooth signaling ..................................................... 91
Occupied bandwidth (OBW) ............................................ 390 Signal routing
Off ......................................................................................37 Bluetooth signaling ..................................................... 73
T
Test mode
classic ......................................................................... 21
LE ............................................................................... 27
Trigger
Bluetooth measurements .......................................... 453
Trigger signal
Bluetooth measurements .......................................... 336
Trigger threshold ............................................................. 454
Trigger timeout ................................................................ 454
TX test ............................................................................... 22
U
UAP ................................................................................. 434
USB info
Bluetooth signaling ..................................................... 50
User manual ........................................................................ 9
User margin ..................................................................... 431
Bluetooth signaling ..................................................... 77
W
White papers ..................................................................... 10
Whitening
Bluetooth signaling ..................................................... 94