VSE NB-IoT Measurement Application · PDF file5.5 Remote Commands to Read Trace Data ... The LTE NB-IoT measurement application measures and analyzes various aspects of an LTE NB-IoT

R&S®VSE-K106LTE NB-IoT Measurement Application(Uplink)User Manual

User

Man

ual

1178.4230.02 ─ 02(;ÜZN2)

This manual describes functionality of the following R&S®VSE options:

● R&S®VSE-K106 LTE NB-IoT Uplink Measurement Application (1320.7900.02)

© 2017 Rohde & Schwarz GmbH & Co. KGMühldorfstr. 15, 81671 München, GermanyPhone: +49 89 41 29 - 0Fax: +49 89 41 29 12 164Email: [email protected]: www.rohde-schwarz.comSubject to change – Data without tolerance limits is not binding.R&S® is a registered trademark of Rohde & Schwarz GmbH & Co. KG.Trade names are trademarks of their owners.

Throughout this manual, products from Rohde & Schwarz are indicated without the ® symbol , e.g. R&S®VSE is indicated asR&S VSE.

mailto:[email protected]

http://www.rohde-schwarz.com

ContentsR&S®VSE-K106

3User Manual 1178.4230.02 ─ 02

Contents1 Welcome to the LTE NB-IoT measurement application......................5

1.1 Starting the LTE NB-IoT measurement application................................................... 5

1.2 Understanding the Display Information......................................................................6

2 Measurements and Result Displays.....................................................82.1 Selecting Measurements.............................................................................................. 8

2.2 Selecting Result Displays............................................................................................ 9

2.3 Performing Measurements...........................................................................................9

2.4 I/Q Measurements......................................................................................................... 9

2.5 Frequency Sweep Measurements............................................................................. 20

3 Configuration........................................................................................223.1 Configuration Overview..............................................................................................22

3.2 Configuring I/Q Measurements..................................................................................24

3.3 Configuring Frequency Sweep Measurements........................................................ 44

4 Analysis................................................................................................ 464.1 Configuring Tables / Numerical Results................................................................... 46

4.2 Exporting Measurement Results............................................................................... 46

4.3 Evaluation Range........................................................................................................ 47

4.4 Scale.............................................................................................................................48

4.5 Result Settings............................................................................................................ 49

4.6 Markers........................................................................................................................ 50

5 Remote Control.................................................................................... 525.1 Common Suffixes........................................................................................................52

5.2 Introduction................................................................................................................. 53

5.3 Remote Commands to Select the LTE Application..................................................58

5.4 Configuring the Screen Layout..................................................................................58

5.5 Remote Commands to Read Trace Data...................................................................68

5.6 Remote Commands to Read Numeric Results.........................................................79

5.7 Remote Commands to Configure the Application................................................... 87

5.8 Analysis..................................................................................................................... 118

Annex.................................................................................................. 125

ContentsR&S®VSE-K106

4User Manual 1178.4230.02 ─ 02

A Annex: Reference...............................................................................125A.1 Menu Reference........................................................................................................ 125

A.2 Reference of Toolbar Functions.............................................................................. 129

List of Commands..............................................................................133

Index....................................................................................................137

Welcome to the LTE NB-IoT measurement applicationR&S®VSE-K106

5User Manual 1178.4230.02 ─ 02

1 Welcome to the LTE NB-IoT measurementapplicationThe LTE NB-IoT measurement application is a firmware application that adds function-ality to perform measurements on LTE NB-IoT signals according to the 3GPP standardto the R&S VSE.

This user manual contains a description of the functionality that the application pro-vides, including remote control operation. Functions that are not discussed in this man-ual are the same as in the Spectrum application and are described in the R&S VSEUser Manual. The latest versions of the manuals are available for download at theproduct homepage.

http://www2.rohde-schwarz.com/product/vse.html.

● Starting the LTE NB-IoT measurement application...................................................5● Understanding the Display Information.....................................................................6

1.1 Starting the LTE NB-IoT measurement application

The LTE NB-IoT measurement application adds a new application to the R&S VSE.

To open the LTE NB-IoT application

1.

Select the "Add Channel" function in the Sequence tool window.

A dialog box opens that contains all operating modes and applications currentlyavailable in your R&S VSE.

2. Select the "NB-IoT" item.

The R&S VSE opens a new measurement channel for the NB-IoT application.

The application is started with the default settings. It can be configured in the "Over-view" dialog box, which is displayed when you select the "Overview" softkey from the"Meas Setup" menu.

For more information see Chapter 3, "Configuration", on page 22.

Starting the LTE NB-IoT measurement application

http://www2.rohde-schwarz.com/product/VSE.html


6User Manual 1178.4230.02 ─ 02

1.2 Understanding the Display Information

The following figure shows a measurement diagram during analyzer operation. All dif-ferent information areas are labeled. They are explained in more detail in the followingsections.

1 2 3 4 5

1 = Window title bar with information about the diagram and its traces2 = Channel bar with measurement settings3 = Diagram area4 = Diagram footer with information about the contents of the diagram5 = Color code for windows of the same channel (here: yellow)

Channel bar information

In the LTE NB-IoT measurement application, the R&S VSE shows the following set-tings:

Table 1-1: Information displayed in the channel bar in the LTE measurement application

Ref Level Reference level

Att Mechanical and electronic RF attenuation

Offset Reference level offset

Freq Center frequency

Mode NB-IoT standard

MIMO Number of Tx and Rx antennas in the measurement setup

Capture Time Length of the signal that has been captured

Slot Count Number of slots that have been captured

NPUSCH NPUSCH considered in the signal analysis

Slot Slot considered in the signal analysis

Understanding the Display Information


7User Manual 1178.4230.02 ─ 02

In addition, the channel bar also displays information on instrument settings that affectthe measurement results even though this is not immediately apparent from the displayof the measured values (for example trigger settings). This information is displayedonly when applicable for the current measurement. For details see the R&S VSE Get-ting Started manual.

Window title bar information

The information in the window title bar depends on the result display.

The "Constellation Diagram", for example, shows the number of points that have beenmeasured.

Status bar information

Global instrument settings, the instrument status and any irregularities are indicated inthe status bar beneath the diagram. Furthermore, the progress of the current operationis displayed in the status bar.

Regarding the synchronization state, the application shows the following labels.● Sync OK

The synchronization was successful. The status bar is green.● Sync Failed

The synchronization was not successful. The status bar is red.There can be three different synchronization errors.– Sync Failed (Cyclic Prefix): The cyclic prefix correlation failed.– Sync Failed NPSS): The NPSS correlation failed.– Sync Failed (NSSS): The NSSS correlation failed.

Understanding the Display Information

Measurements and Result DisplaysR&S®VSE-K106

8User Manual 1178.4230.02 ─ 02

2 Measurements and Result DisplaysThe LTE NB-IoT measurement application measures and analyzes various aspects ofan LTE NB-IoT signal.

It features several measurements and result displays. Measurements represent differ-ent ways of processing the captured data during the digital signal processing. Resultdisplays are different representations of the measurement results. They can be dia-grams that show the results as a graph or tables that show the results as numbers.

● Selecting Measurements...........................................................................................8● Selecting Result Displays..........................................................................................9● Performing Measurements........................................................................................9● I/Q Measurements.....................................................................................................9● Frequency Sweep Measurements.......................................................................... 20

2.1 Selecting Measurements

► Select the "Select Meas" menu item from the "Meas Setup" menu.

The application opens a dialog box that contains several buttons.Each button represents a set of result displays that thematically belong togetherand that have a particular display configuration. If these predefined display configu-rations do not suit your requirements, you can add or remove result displays asyou like. For more information about selecting result displays, see Chapter 2.2,"Selecting Result Displays", on page 9.

Depending on the button you select, the application changes the way the R&S VSEcaptures and processes the raw signal data.

● When you select "EVM", the application processes the I/Q data of the signal. Formore information on available I/Q result displays, see Chapter 2.4, "I/Q Measure-ments", on page 9.When you select one of the result displays available for I/Q measurements, youcan combine the result displays available for I/Q measurements in any way.

● When you select "Channel Power ACLR" or "Spectrum Emission Mask", the appli-cation performs a frequency sweep. For more information, see Chapter 2.5, "Fre-quency Sweep Measurements", on page 20.When you select one of the frequency sweep measurements, you can combine theresult displays available for the frequency sweep measurements in any way.Note that you cannot display the ACLR and SEM at the same time.

Remote command:

CONFigure[:LTE]:MEASurement on page 88

Selecting Measurements


9User Manual 1178.4230.02 ─ 02

2.2 Selecting Result Displays

► Select the "New Window" menu item from the "Window" menu or select a new win-dow with the icon in the toolbar. Depending on the number of LTE channels youare currently using, there is a submenu that contains all available result displays foreach LTE channel.

In the default state of the application, it shows several conventional result displays.● Capture Buffer● Power vs Symbol X Carrier● Constellation Diagram● Power Spectrum● Result Summary

From that predefined state, add and remove result displays to the channels as you likefrom the "Window" menu.

Remote command:

LAYout:ADD[:WINDow]? on page 63

Note that you can customize the contents of some numerical result displays. For moreinformation, see Chapter 4.1, "Configuring Tables / Numerical Results", on page 46.

2.3 Performing Measurements

By default, the application measures the signal continuously. In "Continuous Sweep"mode, the application captures and analyzes the data again and again. The amount ofdata depends on the capture time (I/Q measurements) or the sweep time (frequencysweep measurements). In "Single Sweep" mode, the application stops measuring afterit has captured the data once. The amount of data again depends on the capture timeor the sweep time.

You can also repeat a measurement based on the data that has already been capturedwith the "Refresh" function. This is useful if you want to apply different modulation set-tings to the same I/Q data, for example.

For more information see the documentation of the R&S VSE.

2.4 I/Q Measurements

Access: "Overview" > "Select Measurement" > "EVM/Frequency Err/Power"

You can select the result displays from the evaluation bar and arrange them as you likewith the SmartGrid functionality.

I/Q Measurements


10User Manual 1178.4230.02 ─ 02

Capture Buffer...............................................................................................................10EVM vs Carrier..............................................................................................................11EVM vs Symbol.............................................................................................................11Power Spectrum............................................................................................................12Spectrum Flatness........................................................................................................ 13Channel Group Delay....................................................................................................13Spectrum Flatness Difference.......................................................................................13Constellation Diagram...................................................................................................14CCDF............................................................................................................................ 14Allocation Summary...................................................................................................... 15Bit Stream..................................................................................................................... 16EVM vs Sym x Carr.......................................................................................................16Power vs Symbol x Carrier............................................................................................17Result Summary............................................................................................................17Marker Table ................................................................................................................ 20

Capture BufferThe Capture Buffer result display shows the complete range of captured data for thelast data capture. The x-axis represents time. The maximum value of the x-axis isequal to the Capture Time. The y-axis represents the amplitude of the captured I/Qdata in dBm (for RF input).

Figure 2-1: Capture buffer without zoom

A green vertical line at the beginning of the green bar in the Capture Buffer displaymarks the NPUSCH start. Additionally, the diagram contains the "Start Offset" value.This value is the time difference between the NPUSCH start and capture buffer start.

When you zoom into the diagram, you will see that the bar may be interrupted at cer-tain positions. Each small bar indicates the useful parts of the OFDM symbol.

Figure 2-2: Capture buffer after a zoom has been applied

I/Q Measurements


11User Manual 1178.4230.02 ─ 02

Remote command: Selecting the result display: LAY:ADD ? '1',LEFT,CBUFQuerying results: TRACe:DATA?

EVM vs CarrierStarts the EVM vs Carrier result display.

This result display shows the Error Vector Magnitude (EVM) of the subcarriers. Withthe help of a marker, you can use it as a debugging technique to identify any subcarri-ers whose EVM is too high.

The results are based on an average EVM that is calculated over the resource ele-ments for each subcarrier. This average subcarrier EVM is determined for each ana-lyzed slot in the capture buffer.

If you analyze all slots, the result display contains three traces.● Average EVM

This trace shows the subcarrier EVM, averaged over all slots.● Minimum EVM

This trace shows the lowest (average) subcarrier EVM that has been found overthe analyzed slots.

● Maximum EVMThis trace shows the highest (average) subcarrier EVM that has been found overthe analyzed slots.

If you select and analyze one slot only, the result display contains one trace that showsthe subcarrier EVM for that slot only. Average, minimum and maximum values in thatcase are the same. For more information, see "Slot Selection" on page 47

The x-axis represents the center frequencies of the subcarriers. On the y-axis, theEVM is plotted either in % or in dB, depending on the EVM Unit.

Remote command: Selecting the result display: LAY:ADD ? '1',LEFT,EVCAQuerying results: TRACe:DATA?

EVM vs SymbolStarts the EVM vs Symbol result display.

This result display shows the Error Vector Magnitude (EVM) of the OFDM symbols.You can use it as a debugging technique to identify any symbols whose EVM is toohigh.

The results are based on an average EVM that is calculated over all subcarriers thatare part of a particular OFDM symbol. This average OFDM symbol EVM is determinedfor all OFDM symbols in each analyzed slot.

I/Q Measurements


12User Manual 1178.4230.02 ─ 02

If you analyze all subframes, the result display contains three traces.● Average EVM

This trace shows the OFDM symbol EVM, averaged over all slots.● Minimum EVM

This trace shows the lowest (average) OFDM symbol EVM that has been foundover the analyzed slots.

● Maximum EVMThis trace shows the highest (average) OFDM symbol EVM that has been foundover the analyzed slots.

If you select and analyze one slot only, the result display contains one trace that showsthe OFDM symbol EVM for that slot only. Average, minimum and maximum values inthat case are the same. For more information, see "Slot Selection" on page 47

The x-axis represents the OFDM symbols, with each symbol represented by a dot onthe line. The number of displayed symbols depends on the Subframe Selection and thelength of the cyclic prefix. Any missing connections from one dot to another mean thatthe R&S VSE could not determine the EVM for that symbol.

On the y-axis, the EVM is plotted either in % or in dB, depending on the EVM Unit.

Remote command: Selecting the result display: LAY:ADD ? '1',LEFT,EVSYQuerying results: TRACe:DATA?

Power SpectrumStarts the Power Spectrum result display.

This result display shows the power density of the complete capture buffer in dBm/Hz.The displayed bandwidth depends on bandwidth or number of resource blocks youhave set.

For more information, see "Subcarrier Spacing" on page 26.

The x-axis represents the frequency. On the y-axis, the power level is plotted.

I/Q Measurements


13User Manual 1178.4230.02 ─ 02

Remote command: Selecting the result display: LAY:ADD ? '1',LEFT,PSPEQuerying results: TRACe:DATA?

Spectrum FlatnessStarts the Spectrum Flatness result display.

This result display shows the relative power offset caused by the transmit channel.

The measurement is evaluated over the currently selected slot.

The x-axis represents the frequency. On the y-axis, the channel flatness is plotted indB.

Note that the limit lines are only displayed if you match the Operating Band to the cen-ter frequency. Limits are defined for each operating band in the standard.

Remote command: Selecting the result display: LAY:ADD ? '1',LEFT,SFLQuerying results: TRACe:DATA?

Channel Group DelayStarts the Channel Group Delay result display.

This result display shows the group delay of each subcarrier.

(Note that the evaluation is only possible for signals with 12 subcarriers. If you evaluatea signal with 1, 3 or 6 subcarriers, no results are displayed.)


The x-axis represents the frequency. On the y-axis, the group delay is plotted in ns.

Remote command: Selecting the result display: LAY:ADD ? '1',LEFT,GDELQuerying results: TRACe:DATA?

Spectrum Flatness DifferenceStarts the Spectrum Flatness Difference result display.

I/Q Measurements


14User Manual 1178.4230.02 ─ 02

This result display shows the level difference in the spectrum flatness result betweentwo adjacent physical subcarriers.


The x-axis represents the frequency. On the y-axis, the power is plotted in dB.

Remote command: Selecting the result display: LAY:ADD ? '1',LEFT,SFDQuerying results: TRACe:DATA?

Constellation DiagramStarts the Constellation Diagram result display.

This result display shows the in-phase and quadrature phase results and is an indica-tor of the quality of the modulation of the signal.

In the default state, the result display evaluates the full range of the measured inputdata. You can filter the results by changing the evaluation range.

The constellation diagram also contains information about the current evaluationrange. In addition, it shows the number of points that are displayed in the diagram.

Remote command: Selecting the result display: LAY:ADD ? '1',LEFT,CONSQuerying results: TRACe:DATA?

CCDFStarts the Complementary Cumulative Distribution Function (CCDF) result display.

This result display shows the probability of an amplitude exceeding the mean power.For the measurement, the complete capture buffer is used.

The x-axis represents the power relative to the measured mean power. On the y-axis,the probability is plotted in %.

I/Q Measurements


15User Manual 1178.4230.02 ─ 02

In addition to the diagram, the results for the CCDF measurement are summarized inthe CCDF table.

Mean Mean power

Peak Peak power

Crest Crest factor (peak power – mean power)

10 % Level values over 10 % above mean power

1 % Level values over 1 % above mean power

0.1 % Level values over 0.1 % above mean power

0.01 % Level values over 0.01 % above mean power

Remote command: Selecting the result display: LAY:ADD ? '1',LEFT,CCDFQuerying results: TRACe:DATA?

Allocation SummaryStarts the Allocation Summary result display.

This result display shows the results of the measured allocations in tabular form.

The rows in the table represent the allocations. The columns of the table contain thefollowing information:● Idx

Shows an index number of the channel.● Allocation ID

Shows the type of the allocation.● Start Slot

Shows the number of the first slot used by the corresponding allocation.● Allocated Slots

Shows the number of slots used by the corresponding allocation.● Modulation

Shows the modulation type.● Power

Shows the power of the allocation in dBm.● EVM

Shows the EVM of the allocation. The unit depends on your selection.Note: Contents of the Allocation Summary

I/Q Measurements


16User Manual 1178.4230.02 ─ 02

The number of columns shown in the Allocation Summary is variable. To add orremove a column, click on the header row of the table once. The application opens adialog box to select the columns which you'd like to display.

Remote command: Selecting the result display: LAY:ADD ? '1',LEFT,ASUMQuerying results: TRACe:DATA?

Bit StreamStarts the Bit Stream result display.

This result display shows the demodulated data stream for each data allocation.Depending on the Bit Stream Format, the numbers represent either bits (bit order) orsymbols (symbol order).

Selecting symbol format shows the bit stream as symbols. In that case, the bits belong-ing to one symbol are shown as hexadecimal numbers with two digits. In the case of bitformat, each number represents one raw bit.

Symbols or bits that are not transmitted are represented by a "-".

If a symbol could not be decoded because the number of layers exceeds the numberof receive antennas, the application shows a "#" sign.

The table contains the following information:● Subframe

Number of the subframe the bits belong to.● Allocation ID

Channel the bits belong to.● Modulation

Modulation type of the channels.● Symbol Index or Bit Index

Shows the position of the table row's first bit or symbol within the complete stream.● Bit Stream

The actual bit stream.

Remote command: Selecting the result display: LAY:ADD ? '1',LEFT,BSTRQuerying results: TRACe:DATA?

EVM vs Sym x CarrThe EVM vs Symbol x Carrier shows the EVM for each carrier in each symbol.

The horizontal axis represents the symbols. The vertical axis represents the carriers.Different colors in the diagram area represent the EVM. The color map for the powerlevels is provided above the diagram area.

I/Q Measurements


17User Manual 1178.4230.02 ─ 02

Remote command: Selecting the result display: LAY:ADD ? '1',LEFT,EVSCQuerying results: TRACe:DATA?

Power vs Symbol x CarrierThe Power vs Symbol x Carrier shows the power for each carrier in each symbol.

The horizontal axis represents the symbols. The vertical axis represents the carriers.Different colors in the diagram area represent the power. The color map for the powerlevels is provided above the diagram area.

Remote command: Selecting the result display: LAY:ADD ? '1',LEFT,PVSCQuerying results: TRACe:DATA?

Result SummaryThe Result Summary shows all relevant measurement results in numerical form, com-bined in one table.

Remote command:

LAY:ADD ? '1',LEFT,RSUM

Contents of the result summaryThe contents of the result summary depend on the analysis mode you have selected.The first screenshot shows the results for "NPUSCH/NPUCCH" analysis mode, thesecond one those for "NPRACH" analysis mode.

I/Q Measurements


18User Manual 1178.4230.02 ─ 02

Figure 2-3: Result summary in NPUSCH/NPUCCH analysis mode

Figure 2-4: Result summary in NPRACH analysis mode

The table is split in two parts. The first part shows results that over a slot as defined by3GPP. It also indicates limit values as defined in the NB-IoT standard and limit checkresults where available. The font of 'Pass' results is green and that of 'Fail' results isred.

In addition to the red font, the application also puts a red star ( ) in front offailed results.

The second part of the table shows results that refer to a specific selection (NPUSCHand slot). The header row of the table contains information about the selection youhave made (like the subframe). Note: The EVM results on a frame level (first part of the table) are calculated asdefined by 3GPP at the edges of the cyclic prefix.The other EVM results (lower part of the table) are calculated at the optimal timingposition in the middle of the cyclic prefix.Because of inter-symbol interference, the EVM calculated at the edges of the cyclicprefix is higher than the EVM calculated in the middle of the cyclic prefix.By default, all EVM results are in %. To view the EVM results in dB, change the EVMUnit. Note: When you perform single carrier measurements, Gain Imbalance and Quadra-ture Error are not calculated.

I/Q Measurements


19User Manual 1178.4230.02 ─ 02

Table 2-1: Result summary: part containing results as defined by 3GPP (NPUSCH/NPUCCH analysis)

EVM NPUSCH QPSK Shows the EVM for all QPSK-modulated resource elements of the NPUSCHchannel in the analyzed frame. This EVM is calculated according to 3GPP.

FETCh[:CC<cc>]:SUMMary:EVM:UNSQ[:AVERage]? on page 80

EVM NPUSCH BPSK Shows the EVM for all BPSK-modulated resource elements of the NPUSCHchannel in the analyzed frame. This EVM is calculated according to 3GPP.

FETCh[:CC<cc>]:SUMMary:EVM:UNSB[:AVERage]? on page 80

EVM NDRMS NPUSCHQPSK

Shows the EVM of all NDMRS resource elements with QPSK modulation ofthe NPUSCH in the analyzed frame. This EVM is calculated according to3GPP.

FETCh[:CC<cc>]:SUMMary:EVM:UNDQ[:AVERage]? on page 79

EVM NDRMS NPUSCHBPSK

Shows the EVM of all NDMRS resource elements with BPSK modulation ofthe NPUSCH in the analyzed frame. This EVM is calculated according to3GPP.

FETCh[:CC<cc>]:SUMMary:EVM:UNDB[:AVERage]? on page 79

Frequency Error (3GPP) Shows the frequency error as defined by 3GPP.

FETCh[:CC<cc>]:SUMMary:FE3G[:AVERage]? on page 83

Table 2-2: Result summary: part containing results as defined by 3GPP (NPRACH analysis)

EVM NPRACH Shows the EVM of all resource elements of the NPRACH channel in the ana-lyzed frame.

FETCh[:CC<cc>]:SUMMary:EVM:UPRA[:AVERage]? on page 80

Table 2-3: Result summary: part containing results for a specific selection

EVM All Shows the EVM for all resource elements in the analyzed frame.

FETCh[:CC<cc>]:SUMMary:EVM[:ALL][:AVERage]? on page 82

EVM Phys Channel Shows the EVM for all physical channel resource elements in the analyzedframe.

A physical channel corresponds to a set of resource elements carrying infor-mation from higher layers. NPUSCH and NPUCCH are physical channels. Formore information, see 3GPP 36.211.

FETCh[:CC<cc>]:SUMMary:EVM:PCHannel[:AVERage]? on page 82

("NPUSCH/NPUCCH" analysis mode only.)

EVM Phys Signal Shows the EVM for all physical signal resource elements in the analyzedframe.

The reference signal is a physical signal. For more information, see 3GPP36.211.

FETCh[:CC<cc>]:SUMMary:EVM:PSIGnal[:AVERage]? on page 82


Frequency Error Shows the difference in the measured center frequency and the referencecenter frequency.

FETCh[:CC<cc>]:SUMMary:FERRor[:AVERage]? on page 83

I/Q Offset Shows the power at spectral line 0 normalized to the total transmitted power.

FETCh[:CC<cc>]:SUMMary:IQOFfset[:AVERage]? on page 84

I/Q Measurements


20User Manual 1178.4230.02 ─ 02

I/Q Gain Imbalance Shows the logarithm of the gain ratio of the Q-channel to the I-channel.

FETCh[:CC<cc>]:SUMMary:GIMBalance[:AVERage]? on page 84


I/Q Quadrature Error Shows the measure of the phase angle between Q-channel and I-channeldeviating from the ideal 90 degrees.

FETCh[:CC<cc>]:SUMMary:QUADerror[:AVERage]? on page 85


Power Shows the average time domain power of the allocated resource blocks of theanalyzed signal.

FETCh[:CC<cc>]:SUMMary:POWer[:AVERage]? on page 84

Crest Factor Shows the peak-to-average power ratio of captured signal.

FETCh[:CC<cc>]:SUMMary:CRESt[:AVERage]? on page 81

Marker TableDisplays a table with the current marker values for the active markers.

Remote command: LAY:ADD? '1',RIGH, MTAB, see LAYout:ADD[:WINDow]? on page 63Results:CALCulate<n>:MARKer<m>:X on page 86CALCulate<n>:MARKer<m>:Y? on page 87

2.5 Frequency Sweep Measurements

Access (ACLR): "Meas Setup" > "Select Measurement" > "Channel Power ACLR"

The Spectrum Emission Mask (SEM) and Adjacent Channel Leakage Ratio (ACLR)measurements are frequency sweep measurements available for the NB-IoT measure-ment application. They do not use the I/Q data all other measurements use. Insteadthose measurements sweep the frequency spectrum every time you run a new mea-surement. Therefore it is not possible to to run an I/Q measurement and then view theresults in the frequency sweep measurements and vice-versa. Also because each ofthe frequency sweep measurements uses different settings to obtain signal data it isnot possible to run a frequency sweep measurement and view the results in anotherfrequency sweep measurement.

Frequency sweep measurements are available if RF input is selected.

Frequency Sweep Measurements


21User Manual 1178.4230.02 ─ 02

In addition to the frequency sweep result displays (graphical and numerical, see thedescription below), the following result displays are also supported.● Marker Table● Marker Peak List

Both result displays have the same contents as the Spectrum application.

ACLR.............................................................................................................................21

ACLRStarts the Adjacent Channel Leakage Ratio (ACLR) measurement.

The ACLR measurement analyzes the power of the transmission (TX) channel and thepower of the two neighboring channels (adjacent channels) to the left and right of theTX channel. Thus, the ACLR measurement provides information about the power inthe adjacent channels as well as the leakage into these adjacent channels.

The x-axis represents the frequency with a frequency span that relates to the specifiedEUTRA/LTE channel and adjacent channel bandwidths. On the y-axis, the power isplotted in dBm.

By default the ACLR settings are based on the selected LTE channel bandwidth. Youcan change the assumed adjacent channel carrier type and, if necessary, customizethe channel setup to your needs. For more information, see the documentation of theR&S VSE.

The power for the TX channel is an absolute value in dBm. The power of the adjacentchannels is relative to the power of the TX channel.

In addition, the ACLR measurement results are also tested against the limits definedby 3GPP. In the diagram, the limits are represented by horizontal red lines. Result SummaryThe result summary contains information about the measurement in numerical form:● Channel

Shows the channel type (Tx, Adjacent or Alternate Channel).● Bandwidth

Shows the bandwidth of the channel.● Spacing

Shows the channel spacing.● Power

Shows the power of the transmission channel.● Lower / Upper

Shows the relative power of the lower and upper adjacent and alternate channels

Remote command: Selecting the result display:CONF:MEAS ACLRQuerying results:CALCulate<n>:MARKer<m>:FUNCtion:POWer:RESult[:CURRent]?TRACe:DATA?

Frequency Sweep Measurements

ConfigurationR&S®VSE-K106

22User Manual 1178.4230.02 ─ 02

3 ConfigurationLTE NB-IoT measurements require a special application on the R&S VSE, which youcan select by adding a new measurement channel or replacing an existing one.

For more information on controlling measurement applications, refer to the documenta-tion of the R&S VSE base software.

When you start the LTE NB-IoT application, the R&S VSE starts to measure the inputsignal with the default configuration or the configuration of the last measurement (if youhaven't performed a preset since then).

Automatic refresh of preview and visualization in dialog boxes after configura-tion changesThe R&S VSE supports you in finding the correct measurement settings quickly andeasily - after each change in settings in dialog boxes, the preview and visualizationareas are updated immediately and automatically to reflect the changes. Thus, you cansee if the setting is appropriate or not before accepting the changes.

Unavailable menusNote that the "Trace" and "Lines" menus have no contents and no function in the LTENB-IoT application.

● Configuration Overview...........................................................................................22● Configuring I/Q Measurements............................................................................... 24● Configuring Frequency Sweep Measurements.......................................................44

3.1 Configuration Overview

Throughout the measurement channel configuration, an overview of the most importantcurrently defined settings is provided in the "Overview". The "Overview" is displayedwhen you select the "Overview" menu item from the "Meas Setup" menu.

Configuration Overview


23User Manual 1178.4230.02 ─ 02

In addition to the main measurement settings, the "Overview" provides quick access tothe main settings dialog boxes. The individual configuration steps are displayed in theorder of the data flow. Thus, you can easily configure an entire measurement channelfrom input over processing to output and analysis by stepping through the dialog boxesas indicated in the "Overview".

In particular, the "Overview" provides quick access to the following configuration dialogboxes (listed in the recommended order of processing):

1. Signal DescriptionSee Chapter 3.2.1, "Defining Signal Characteristics", on page 25.

2. Input / FrontendSee Chapter 3.2.7, "Selecting the Input and Output Source", on page 36.

3. Trigger / Signal CaptureSee Chapter 3.2.10, "Triggering Measurements", on page 41See Chapter 3.2.11, "Configuring the Data Capture", on page 42

4. Trackingn/a

5. DemodulationSee Chapter 3.2.12, "Signal Demodulation", on page 43.

6. Evaluation RangeSee Chapter 4.3, "Evaluation Range", on page 47.

7. AnalysisSee Chapter 4, "Analysis", on page 46.

8. Display ConfigurationSee Chapter 2, "Measurements and Result Displays", on page 8.

Configuration Overview


24User Manual 1178.4230.02 ─ 02

In addition, the dialog box provides the "Select Measurement" button that serves as ashortcut to select the measurement type.

To configure settings

► Select any button in the "Overview" to open the corresponding dialog box.Select a setting in the channel bar (at the top of the measurement channel tab) tochange a specific setting.

Preset Channel............................................................................................................. 24Select Measurement..................................................................................................... 24Specifics for ..................................................................................................................24

Preset ChannelSelect the "Preset Channel" button in the lower left-hand corner of the "Overview" torestore all measurement settings in the current channel to their default values.

Remote command: SYSTem:PRESet:CHANnel[:EXEC] on page 88

Select MeasurementOpens a dialog box to select the type of measurement.

Using this button has the same effect as selecting the "Select Measurement" menuitem in the "Meas Setup" menu.

For more information, see Chapter 2.1, "Selecting Measurements", on page 8.

Remote command: CONFigure[:LTE]:MEASurement on page 88

Specifics forThe channel may contain several windows for different results. Thus, the settings indi-cated in the "Overview" and configured in the dialog boxes vary depending on theselected window.

Select an active window from the "Specifics for" selection list that is displayed in the"Overview" and in all window-specific configuration dialog boxes.

The "Overview" and dialog boxes are updated to indicate the settings for the selectedwindow.

3.2 Configuring I/Q Measurements

● Defining Signal Characteristics............................................................................... 25● Configuring the NPUSCH........................................................................................27● Defining Global Signal Characteristics....................................................................30● Configuring the Demodulation Reference Signal....................................................31● Configuring the Sounding Reference Signal...........................................................33● Configuring the NPRACH........................................................................................34● Selecting the Input and Output Source................................................................... 36● Defining the Frequency...........................................................................................38

Configuring I/Q Measurements


25User Manual 1178.4230.02 ─ 02

● Defining Level Characteristics.................................................................................39● Triggering Measurements....................................................................................... 41● Configuring the Data Capture................................................................................. 42● Signal Demodulation...............................................................................................43

3.2.1 Defining Signal Characteristics

Access: "Overview" > "Signal Description" > "Signal Description"

The general signal characteristics contain settings to describe the general physicalattributes of the signal. They are part of the "Signal Description" tab of the "SignalDescription" dialog box.

Selecting the LTE mode................................................................................................25Analysis Mode...............................................................................................................25Subcarrier Spacing........................................................................................................26Configuring the Physical Layer Cell Identity..................................................................26Operating Band Index................................................................................................... 26

Selecting the LTE modeThe standard selects the NB-IoT link direction you are testing.

FDD and TDD are duplexing methods.● FDD mode uses different frequencies for the uplink and the downlink.● TDD mode uses the same frequency for the uplink and the downlink.

Note that the NB-IoT standard only supports FDD mode.Downlink (DL) and Uplink (UL) describe the transmission path.● Downlink is the transmission path from the base station to the user equipment. The

physical layer mode for the downlink is always OFDMA.● Uplink is the transmission path from the user equipment to the base station. The

physical layer mode for the uplink is always SC-FDMA.

Remote command: Link direction: CONFigure[:LTE]:LDIRection on page 89

Analysis ModeSelects the channel analysis mode.

You can select from "NPUSCH/NPUCCH" mode and "NPRACH" mode.



26User Manual 1178.4230.02 ─ 02

"NPUSCH/NPUCCH" mode analyzes the NPUSCH and NPUCCH. This is the default.

NPRACH mode analyzes the NPRACH only. In NPRACH analysis mode no subframeor slot selection is available. Instead you can select a particular preamble that theresults are shown for. Note that NPRACH analysis mode does not support all resultdisplays.

Note that the subcarrier spacing is fixed to 3.75 kHz when you analyze the NPRACH,because the NPRACH always has that bandwidth.

Remote command: [SENSe:][LTE:]UL:DEMod:MODE on page 91

Subcarrier SpacingSelects the bandwidth of the subcarriers in the signal you are measuring.

The total system bandwidth (carrier) in both cases is 180 kHz.

According to 3GPP, each subcarrier is either 15 kHz or 3.75 kHz wide.

The application also calculates the sampling rate from the subcarrier bandwidth. Thoseare read only.

Remote command: CONFigure[:LTE]:UL[:CC<cc]:SSPacing on page 89

Configuring the Physical Layer Cell IdentityThe "NCell ID", "NCell Identity Group" and physical layer "Identity" are interdependentparameters. In combination, they are responsible for synchronization between networkand user equipment.

The physical layer cell ID identifies a particular radio cell in the NB-IoT network. Thecell identities are divided into 168 unique cell identity groups. Each group consists of 3physical layer identities. According to:

)2()1(3 IDIDcellID NNN

N(1) = cell identity group, {0...167}N(2) = physical layer identity, {0...2}

there is a total of 504 different cell IDs.

If you change one of these three parameters, the application automatically updates theother two.

The cell ID determines:● The reference signal grouping hopping pattern● The NPUSCH demodulation reference signal pseudo-random sequence● The pseudo-random sequence used for scrambling

Remote command: Cell ID: CONFigure[:LTE]:UL[:CC<cc>]:PLC:CID on page 90Cell Identity Group: CONFigure[:LTE]:UL[:CC<cc>]:PLC:CIDGroupon page 90Identity: CONFigure[:LTE]:UL[:CC<cc>]:PLC:PLID on page 90

Operating Band IndexSelects one of the 40 operating bands for spectrum flatness measurements as definedin TS 36.101.



27User Manual 1178.4230.02 ─ 02

The operating band defines the frequency band and the dedicated duplex mode.

Remote command: [SENSe:][LTE:]SFLatness:OBANd on page 91

3.2.2 Configuring the NPUSCH

Access: "Overview" > "Signal Description" > "NPUSCH Configuration"

Each LTE NB-IoT uplink slot is represented by a resource grid, which in turn consistsof several resource elements. The size of the resource grid depends on the number ofsubcarriers and thus the subcarrier spacing. Each resource element can be mapped toone of the physical channels.

The NPUSCH (Narrowband Physical Uplink Shared Channel) primarily carries userdata. Each slot can carry one or more NPUSCHs, whose size and usage depends onyour configuration. A group of resource elements mapped to a specific NPUSCH iscalled resource unit. Resource units are a group of consecutive subcarriers (frequencydomain) and SC-FDMA symbols (time domain). The number of resource elementsforming a resource unit depends on the subcarrier spacing and the NPUSCH format.

The configuration for each NPUSCH in the system is shown in the "NPUSCH Configu-ration Table".

● General NPUSCH Configuration.............................................................................27● Individual NPUSCH Configuration.......................................................................... 28

3.2.2.1 General NPUSCH Configuration

Automatic detection of NPUSCH characteristics.......................................................... 27

Automatic detection of NPUSCH characteristicsThe application provides functionality that allows you to automatically detect severalNPUSCH characteristics, instead of defining them manually.● "Auto Number Of Subcarriers"



28User Manual 1178.4230.02 ─ 02

Automatically detects the number of subcarriers that the corresponding NPUSCHoccupies.In case of "Manual" definition, you can define the number of subcarriers in theNPUSCH table.

● "Auto Start Subcarrier"Automatically detects the first subcarrier that the corresponding NPUSCH occu-pies.In case of "Manual" definition, you can define the start subcarrier in the NPUSCHtable.

● "Auto Modulation Type"Automatically detects the modulation type that the corresponding NPUSCH uses.In case of "Manual" definition, you can define the modulation type in the NPUSCHtable.

Remote command: Number of subcarriers: CONFigure:[:LTE]:UL:AUTO:NPUSch:NSUBcarrieron page 92Start subcarrier: CONFigure:[:LTE]:UL:AUTO:NPUSch:SSUBcarrieron page 92Modulation: CONFigure:[:LTE]:UL:AUTO:NPUSch:MTYPe on page 91

3.2.2.2 Individual NPUSCH Configuration

The "NPUSCH Configuration Table" contains the characteristics for each NPUSCHyou are using. The size of the table depends on the "Number of NPUSCH Transmis-sions" that you have defined or that have been detected in case of automatic demodu-lation. Each row in the table defines the characteristics of one NPUSCH.

Remote command:

CONFigure[:LTE]:UL:NONPusch on page 93

When you configure several NPUSCH, you can encounter several allocation conflicts.

Conflicts● "Overlapped with <x>"

This is a message you get when one or more NPUSCH use the same slots.You can solve this conflict when you change the "Start Slot" value of the affectedslot. The number of slots that a NPUSCH uses depends on the NPUSCH format,the subcarrier spacing, the number of resource units it occupies ("N_RU") and thenumber of repeated transmissions ("M_rep_NPUSCH"). For more informationabout how to calculate the NPUSCH length, refer to the 3GPP standard.

● "Start Subcarrier"



29User Manual 1178.4230.02 ─ 02

This is a message you get when you have selected a "Start Subcarrier" that is notallows for the "Number of Subcarriers" you have selected for the correspondingNPUSCH.Usually, the start subcarrier must be a multiple of the number of subcarriers. Forexample, if you have selected 3 subcarriers, the start subcarrier must be "0", "3","6", "9" etc.

NPUSCH Number......................................................................................................... 29NPUSCH Format...........................................................................................................29Number of Subcarriers.................................................................................................. 29Start Slot....................................................................................................................... 29Starting Subcarrier........................................................................................................ 29Resource Units..............................................................................................................30Repetitions.................................................................................................................... 30Modulation.....................................................................................................................30

NPUSCH NumberShows the index number of the row of the corresponding NPUSCH.

NPUSCH FormatSelects the NPUSCH format.● Format 1: Carries the uplink data.● Format 2: Carries uplink control information.

Remote command: CONFigure[:LTE]:UL:NPUSch<np>:FORMat on page 93

Number of SubcarriersSelects the number of subcarriers that the NPUSCH uses.

This in turn defines the duration of the NPUSCH, or how many slots it requires. Moresubcarriers requires less slots, so the transmission gets faster.

The number of subcarriers that the NPUSCH may use depends on the subcarrier spac-ing and the NPUSCH Format.

Remote command: CONFigure[:LTE]:UL:NPUSch<np>:NOSubcarrier on page 94

Start SlotDefines the first slot that the corresponding NPUSCH uses.

When you use more than one NPUSCH, make sure to enter a valid value. Otherwiseyou can get a conflict of overlapping NPUSCH. For more information about calculatingthe NPUSCH length, refer to the 3GPP standard.

Remote command: CONFigure[:LTE]:UL:NPUSch<np>:SSLot on page 95

Starting SubcarrierDefines the first subcarrier that the corresponding NPUSCH uses.

Make sure to define a valid start subcarrier for the corresponding NPUSCH. Otherwiseyou can get a conflict of subcarriers that are occupied by several NPUSCH.



30User Manual 1178.4230.02 ─ 02

Remote command: CONFigure[:LTE]:UL:NPUSch<np>:SSUBcarrier on page 95

Resource UnitsDefines the number of resource units reserved for the corresponding NPUSCH.

A resource unit describes the mapping of the NPUSCH to individual resource elementsin a consecutive order. When you increase the number of resource units, the NPUSCHcan carry more data.

Remote command: CONFigure[:LTE]:UL:NPUSch<np>:NORu on page 94

RepetitionsDefines the number of times the NPUSCH is transmitted with the same information andbefore the resource elements used by NPUSCH get new assignments.

Increasing the number of repetitions increases the reliabilty of the transmission in favorof speed (because more slots are required in the time domain).

Remote command: CONFigure[:LTE]:UL:NPUSch<np>:MREP on page 94

ModulationSelects the modulation scheme for the corresponding allocation.

Availability of modulation schemes for the NPUSCH is as follows.● BPSK and QPSK

NPUSCH format 1 with one subcarrier.● QPSK

NPUSCH format 1 with more than one subcarrier.● BPSK

NPUSCH format 2.

Remote command: CONFigure[:LTE]:UL:NPUSch<np>:MODulation on page 93

3.2.3 Defining Global Signal Characteristics

Access: "Overview" > "Signal Description" > "Advanced Settings" > "Global Settings"

The global settings contain settings that apply to the complete signal.



31User Manual 1178.4230.02 ─ 02

UE ID/n_RNTI............................................................................................................... 31

UE ID/n_RNTISets the radio network temporary identifier (RNTI) of the UE.

Remote command: CONFigure[:LTE]:UL[:CC<cc>]:UEID on page 96

3.2.4 Configuring the Demodulation Reference Signal

Access: "Overview" > "Signal Description" > "Advanced Settings" > "DemodulationReference Signal"

The global settings contain settings that apply to the complete signal.



32User Manual 1178.4230.02 ─ 02

Base Sequence Source................................................................................................ 32Base Sequence.............................................................................................................32Cyclic Shift.................................................................................................................... 32Delta Sequence Shift.................................................................................................... 33Group Hopping..............................................................................................................33

Base Sequence SourceSelects the origin of the reference signal sequence.● "ID Cell"

The base sequence index is derived from the cell ID.● "Higher Layer"

The base sequence index is derived from higher layer parameters.The base sequence source is relevant in the following cases.● Select NPUSCH format 1.● Turn off group hopping for the NDMRS.● Number of resource units occupied by the NPUSCH is > 1.

Remote command: CONFigure[:LTE]:UL[:CC<cc>]:DRS:BSOurce on page 96

Base Sequence"Three Tone Base Sequence", "Six Tone Base Sequence" and "Twelve Tone BaseSequence" are higher layer parameters that define the base sequence index withwhich the demodulation reference signal (NDMRS) is transmitted.● "Three Tone Base Sequence": base sequence index in case the signal is modula-

ted onto three subcarriers.● "Six Tone Base Sequence": base sequence index in case the signal is modulated

onto six subcarriers.● "Twelve Tone Base Sequence": base sequence index in case the signal is modula-

ted onto twelve subcarriers.The base sequence tone is relevant in the following cases.● Select NPUSCH format 1.● Turn off group hopping for the NDMRS.● Select "Higher Layer" base sequence source.● Number of resource units occupied by the NPUSCH is 3 (three tone), 6 (six tone)

or 12 (twelve tone).In all other cases, the NDMRS sequence is defined by other parameters.

For more information on the NDMRS sequence, refer to 3GPP 36.211, chapter 10.1.4.

Remote command: Three tone: CONFigure[:LTE]:UL[:CC<cc>]:DRS:BTHRee on page 97Six tone: CONFigure[:LTE]:UL[:CC<cc>]:DRS:BSIX on page 96Twelve tone: CONFigure[:LTE]:UL[:CC<cc>]:DRS:BSTWelve on page 97

Cyclic Shift"Three Tone Cyclic Shift" and "Six Tone Cyclic Shift" are higher layer parameters that,in combination with the base sequence, define the sequence with which the demodula-tion reference signal (NDMRS) is transmitted.



33User Manual 1178.4230.02 ─ 02

The base sequence tone is relevant in the following cases.● Select NPUSCH format 1.● Turn off group hopping for the NDMRS.● Select "Higher Layer" base sequence source.● Number of resource units occupied by the NPUSCH is 3 (three tone) or 6 (six

tone).In all other cases, the NDMRS sequence is defined by other parameters.

For more information on the NDMRS sequence, refer to 3GPP 36.211, chapter 10.1.4.

Remote command: Three tone: CONFigure[:LTE]:UL[:CC<cc>]:DRS:CSTHree on page 98Six tone: CONFigure[:LTE]:UL[:CC<cc>]:DRS:CSSix on page 98

Delta Sequence ShiftDefines the delta sequence shift ΔSS.

This value is given by the higher layer parameter groupAssignmentNPUSCH.

The "Delta Sequence Shift" has an effect when you turn on group hopping and thus forNPUSCH format 1.

For more information refer to 3GPP TS 36.211, chapter 10.1.4.1.3 "Group Hopping".

Remote command: CONFigure[:LTE]:UL[:CC<cc>]:DRS:DSSHift on page 99

Group HoppingTurns group hopping for the demodulation reference signal on and off.

Group hopping is only supported by NPUSCH format 1.

Remote command: CONFigure[:LTE]:UL[:CC<cc>]:DRS:GRPHopping on page 99

3.2.5 Configuring the Sounding Reference Signal

Access: "Overview" > "Signal Description" > "Advanced Settings" > "Sounding Refer-ence Signal"

The sounding reference signal (SRS) settings contain settings that define the physicalattributes and structure of the sounding reference signal.



34User Manual 1178.4230.02 ─ 02

Present..........................................................................................................................34SRS Subframe Configuration........................................................................................34

PresentIncludes or excludes the sounding reference signal (SRS) from the test setup.

Remote command: CONFigure[:LTE]:UL[:CC<cc>]:SRS:STAT on page 99

SRS Subframe ConfigurationDefines the subframe configuration of the SRS.

Remote command: CONFigure[:LTE]:UL[:CC<cc>]:SRS:SUConfig on page 100

3.2.6 Configuring the NPRACH

Access: "Overview" > "Signal Description" > "Advanced Settings" > "NPRACH Struc-ture"



35User Manual 1178.4230.02 ─ 02

The NPRACH transmits the physical layer random access preamble. The preambleconists of four symbol groups. Each symbol group consists of a cyclic prefix and fiveidentical symbols.

CP* Symbol Symbol Symbol Symbol Symbol

Figure 3-1: Random access symbol group

CP = Cyclic prefix (variable length)Symbol = Sequence of five identical symbols

NPRACH FormatSelects the format of the NPRACH.

3GPP defines different "Formats" of the preamble: format "0" and format "1". The dif-ference lies in the length of the cyclic prefix.

Remote command: CONFigure[:LTE]:UL[:CC<cc>]:NPRach:FORMat on page 100

Number of RepetitionsDefines the number of times the NPRACH is transmitted.

You can set up the preamble for repeated transmission, for example to make up forbad transmission quality. To control the number of times the preamble is transmitted,change the value of the "Number Of Repetitions" parameter.

Remote command: CONFigure[:LTE]:UL[:CC<cc>]:NPRach:NREP on page 102

Subcarrier ConfigurationDefines the subcarrier configuration of the NPRACH.

The NPRACH can use several subcarriers. The "Number Of Subcarriers" parameterselects the number of subcarriers allocated to the NPRACH.

You can define the location of the of the first subcarrier that is allocated to theNPRACH with the "Subcarrier Offset" property.



36User Manual 1178.4230.02 ─ 02

Remote command: Number of subcarriers: CONFigure[:LTE]:UL[:CC<cc>]:NPRach:NOSCon page 101Offset: CONFigure[:LTE]:UL[:CC<cc>]:NPRach:NSCoffset on page 102

N_initThe parameter Ninit defines the subcarrier selected by the MAC layer for the NPRACHtransmission.

The "N_Init Mode" setting selects the way the Ninit value is determined.● "Auto"

The application automatically determines the Ninit value.Note that all NPRACH parameters have to set correctly. Otherwise, the applicationis not able to determine Ninit automatically.

● "Manual"You can define the Ninit value manually in the "N_Init" field.

Remote command: Mode: CONFigure[:LTE]:UL[:CC<cc>]:NPRach:NIMode on page 100Value: CONFigure[:LTE]:UL[:CC<cc>]:NPRach:NINit on page 101

3.2.7 Selecting the Input and Output Source

The application supports several input sources and outputs.

The supported input sources depend on the connected instrument. Refer to the docu-mentation of the instrument in use for a comprehensive description of input sources.

● RF Input.................................................................................................................. 36● I/Q File Input............................................................................................................37

3.2.7.1 RF Input

Functions to configure the RF input described elsewhere:● " Input Coupling " on page 40● " Impedance " on page 40

Note that the actual functions to configure the RF input depend on the configuration ofthe connected instrument.

High Pass Filter 1 to 3 GHz ..........................................................................................36YIG-Preselector ............................................................................................................37

High Pass Filter 1 to 3 GHzActivates an additional internal high-pass filter for RF input signals from 1 GHz to3 GHz. This filter is used to remove the harmonics of the analyzer to measure the har-monics for a DUT, for example.

This function may require an additional hardware option on the connected instrument.

Remote command: INPut:FILTer:HPASs[:STATe] on page 109



37User Manual 1178.4230.02 ─ 02

YIG-PreselectorActivates or deactivates the YIG-preselector, if available on the connected instrument.

An internal YIG-preselector at the input of the connected instrument ensures thatimage frequencies are rejected. However, this is only possible for a restricted band-width. To use the maximum bandwidth for signal analysis you can deactivate the YIG-preselector at the input of the connected instrument, which can lead to image-fre-quency display.

Remote command: INPut:FILTer:YIG[:STATe] on page 110

3.2.7.2 I/Q File Input

Or: "Input & Output" > "Input Source" > "IQ File"

Alternatively to "live" data input from a connected instrument, measurement data to beanalyzed by the R&S VSE software can also be provided "offline" by a stored data file.This allows you to perform a measurement on any instrument, store the results to afile, and analyze the stored data partially or as a whole at any time using the R&S VSEsoftware.

The "Input Source" settings defined in the "Input" dialog box are identical to those con-figured for a specific channel in the "Measurement Group Setup" window.(See "Controlling Instruments and Capturing Data" in the R&S VSE User Manual).

Input Type..................................................................................................................... 38Input File....................................................................................................................... 38



38User Manual 1178.4230.02 ─ 02

Input TypeSelects an instrument or a file as the type of input provided to the channel.

Remote command: INSTrument:BLOCk:CHANnel[:SETTings]:SOURce on page 110INPut:SELect on page 110

Input FileSpecifies the I/Q data file to be used for input.

Select "Select File" to open the "Load I/Q File" dialog box.

(See "Data Management - Loading the I/Q Data File" in the R&S VSE User Manual).

3.2.8 Defining the Frequency

Access: "Overview" > "Input / Frontend" > "Frequency"

Frequency settings define the frequency characteristics of the signal at the RF input.They are part of the "Frequency" tab of the "Signal Characteristics" dialog box.

Defining the Signal Frequency...................................................................................... 38

Defining the Signal FrequencyFor measurements with an RF input source, you have to match the center frequencyof the analyzer to the frequency of the signal.

The available frequency range depends on the hardware configuration of the analyzeryou are using.

In addition to the frequency itself, you can also define a frequency stepsize. The fre-quency stepsize defines the extent of a frequency change if you change it for examplewith the rotary knob. Define the stepsize in two ways.● = Center

One frequency step corresponds to the current center frequency.● Manual

Define any stepsize you need.

Remote command: Center frequency: [SENSe:]FREQuency:CENTer[:CC<cc>] on page 111Frequency stepsize: [SENSe:]FREQuency:CENTer:STEP on page 112Frequency offset: [SENSe]:FREQuency:CENTer[:CC<cc>]:OFFSet on page 111



39User Manual 1178.4230.02 ─ 02

3.2.9 Defining Level Characteristics

Access: "Overview" > "Input / Frontend" > "Amplitude"

Amplitude settings define the expected level characteristics of the signal at the RFinput.

Level characteristics are available when you capture data with an instrument. In addi-tion, the functions that are available depend on the configuration of the connectedinstrument.

Defining a Reference Level...........................................................................................39Attenuating the Signal................................................................................................... 40Input Coupling .............................................................................................................. 40Impedance ................................................................................................................... 40

Defining a Reference LevelThe reference level is the power level the analyzer expects at the RF input. Keep inmind that the power level at the RF input is the peak envelope power in case of signalswith a high crest factor like LTE.

To get the best dynamic range, you have to set the reference level as low as possible.At the same time, make sure that the maximum signal level does not exceed the refer-ence level. If it does, it will overload the A/D converter, regardless of the signal power.Measurement results may deteriorate (e.g. EVM). This applies especially for measure-ments with more than one active channel near the one you are trying to measure (± 6MHz).

Note that the signal level at the A/D converter may be stronger than the level the appli-cation displays, depending on the current resolution bandwidth. This is because theresolution bandwidths are implemented digitally after the A/D converter.

You can define an arithmetic level offset. A level offset is useful if the signal is attenu-ated or amplified before it is fed into the analyzer. All displayed power level results willbe shifted by this value. Note however, that the reference value ignores the level offset.Thus, it is still mandatory to define the actual power level that the analyzer has to han-dle as the reference level.

You can also use automatic detection of the reference level with the "Auto Level"function.



40User Manual 1178.4230.02 ─ 02

If active, the application measures and sets the reference level to its ideal value.

Automatic level detection also optimizes RF attenuation.

Remote command: Manual: DISPlay[:WINDow<n>]:TRACe<t>:Y[:SCALe]:RLEVel on page 113Automatic: [SENSe:]ADJust:LEVel on page 117Offset: DISPlay[:WINDow<n>]:TRACe<t>:Y[:SCALe]:RLEVel:OFFSeton page 114

Attenuating the SignalAttenuation of the signal may become necessary if you have to reduce the power ofthe signal that you have applied. Power reduction is necessary, for example, to preventan overload of the input mixer.

The LTE measurement application provides several attenuation modes.● Mechanical (or RF) attenuation is always available. The mechanical attenuator

controls attenuation at the RF input.● Electronic attenuation is available when the connected instrument is equipped

with the corresponding option. Note that the frequency range may not exceed thespecification of the electronic attenuator for it to work.For both methods, the application provides automatic detection of the ideal attenu-ation level. Alternatively, you can define the attenuation level manually. The rangeis from 0 dB to 79 dB (RF attenuation) or 30 dB (electronic attenuation) in 1 dBsteps.

For more information on attenuating the signal, see the manual of the connectedinstrument.

Remote command: RF attenuation: INPut:ATTenuation on page 114Electronic attenuation: INPut<n>:EATT:STATe on page 116Electronic attenuation: INPut<n>:EATT:AUTO on page 116Electronic attenuation: INPut<n>:EATT on page 116

Input CouplingThe RF input of the connected instrument can be coupled by alternating current (AC)or direct current (DC).

AC coupling blocks any DC voltage from the input signal. This is the default setting toprevent damage to the instrument. Very low frequencies in the input signal may be dis-torted.

However, some specifications require DC coupling. In this case, you must protect theinstrument from damaging DC input voltages manually. For details, refer to the datasheet.

Remote command: INPut:COUPling on page 114

ImpedanceFor some measurements, the reference impedance for the measured levels of the con-nected instrument can be set to 50 Ω or 75 Ω.



41User Manual 1178.4230.02 ─ 02

Select 75 Ω if the 50 Ω input impedance is transformed to a higher impedance using a75 Ω adapter of the RAZ type. (That corresponds to 25Ω in series to the input impe-dance of the instrument.) The correction value in this case is 1.76 dB = 10 log (75Ω/50Ω).

Remote command: INPut:IMPedance on page 115

3.2.10 Triggering Measurements

Access: "Overview" > "Trig / Sig Capture" > "Trigger"

Configuring the Trigger................................................................................................. 41

Configuring the TriggerA trigger allows you to capture those parts of the signal that you are really interestedin.

While the application runs freely and analyzes all signal data in its default state, nomatter if the signal contains information or not, a trigger initiates a measurement onlyunder certain circumstances (the trigger event).

The application supports several trigger modes or sources.● Free Run

Starts the measurement immediately and measures continuously.● External <x>

The trigger event is the level of an external trigger signal. The measurement startswhen this signal meets or exceeds a specified trigger level at the trigger input.Some measurement devices have several trigger ports. When you use one ofthese, several external trigger sources are available.

For external trigger, you can define the trigger level. This is the level that the signalmust meet or exceed to start a measurement.

The measurement starts as soon as the trigger event happens. It may become neces-sary to start the measurement some time after the trigger event. In that case, define atrigger offset (or trigger delay). The trigger offset is the time that should pass betweenthe trigger event and the start of the measurement.



42User Manual 1178.4230.02 ─ 02

When you select an external trigger, you can also select the trigger position. The trig-ger position selects a point in the signal structure where a measurement should begin.● "Start of frame 0" (available in "NPUSCH/NPUCCH" analysis mode).

The trigger is sent at the start of frame 0.● "Frame start of first NPUSCH" (available in "NPUSCH/NPUCCH" analysis mode).

The trigger is sent at the start of the frame in which the first NPUSCH is found.● "Start of NPUSCH" (available in "NPUSCH/NPUCCH" analysis mode).

The trigger is sent at the start of the first NPUSCH.● "Start of NPRACH" (available in "NPRACH" analysis mode).

The trigger is sent at the start of the first NPRACH.When you analyze a signal from an I/Q file, then the trigger source is always to "FreeRun". In this case, the parameter describes the start of the I/Q file. If the position of theNPUSCH in unknown, select the "Unknown" trigger source. In that case, the applica-tion searches the I/Q data until it finds an NPUSCH and starts the measurement.

Remote command: TRIGger[:SEQuence]:POSition on page 106

3.2.11 Configuring the Data Capture

Access: "Overview" > "Trig / Sig Capture" > "Signal Capture"

Capture Time................................................................................................................ 42Swap I/Q....................................................................................................................... 43Overall Slot Count......................................................................................................... 43Auto According to Standard.......................................................................................... 43Number of Slots to Analyze...........................................................................................43

Capture TimeDefines the capture time.

The capture time corresponds to the time of one measurement. Hence, it defines theamount of data the application captures during a single measurement (or sweep).

By default, the application captures 20.1 ms of data to make sure that at least onecomplete NB-IoT frame is captured in the measurement.



43User Manual 1178.4230.02 ─ 02

Remote command: [SENSe:]SWEep:TIME on page 104

Swap I/QSwaps the real (I branch) and the imaginary (Q branch) parts of the signal.

Remote command: [SENSe:]SWAPiq on page 103

Overall Slot CountTurns the manual selection of the number of slots to capture (and analyze) on and off.

If the overall slot count is active, you can define a particular number of slots to captureand analyze. The measurement runs until all required slots have been analyzed, evenif it takes more than one sweep. The results are an average of the captured slot.

If the overall slot count is inactive, the application analyzes all complete slots currentlyin the capture buffer.

Remote command: [SENSe:][LTE:]SLOT:COUNt:STATe on page 103

Auto According to StandardTurns automatic selection of the number of slots to capture and analyze on and off.

If active, the application evaluates the number of slots as defined for EVM tests in theNB-IoT standard.

If inactive, you can define the number of slots you want to analyze.

This parameter is not available if the overall slot count is inactive.

Remote command: [SENSe:][LTE:]SLOT:COUNt:AUTO on page 103

Number of Slots to AnalyzeSelects the number of slots that you want to capture and analyze.

If the number of slots you have set last longer than a single measurement, the applica-tion continues the measurement until all slots have been captured.

The parameter is read only in the following cases:● The overall slot count is inactive.● The data is captured according to the standard.

Remote command: [SENSe:][LTE:]SLOT:COUNt on page 102

3.2.12 Signal Demodulation

Access: "Overview" > "Demodulation"



44User Manual 1178.4230.02 ─ 02

Channel Estimation Range........................................................................................... 44Compensate DC Offset................................................................................................. 44Scrambling of Coded Bits..............................................................................................44

Channel Estimation RangeSelects the method for channel estimation.

You can select if only the pilot symbols are used to perform channel estimation or ifboth pilot and payload carriers are used.

Remote command: [SENSe:][LTE:]UL:DEMod:CESTimation on page 109

Compensate DC OffsetTurns DC offset compensation when calculating measurement results on and off.

According to 3GPP TS 36.101 (Annex F.4), the R&S VSE removes the carrier leakage(I/Q origin offset) from the evaluated signal before it calculates the EVM and in-bandemissions.

Remote command: [SENSe:][LTE:]UL:DEMod:CDCoffset on page 109

Scrambling of Coded BitsTurns the scrambling of coded bits for the NPUSCH on and off.

The scrambling of coded bits affects the bitstream results.

Remote command: [SENSe:][LTE:]UL:DEMod:CBSCrambling on page 108

3.3 Configuring Frequency Sweep Measurements

After starting one of the frequency sweep measurements, the application automaticallyloads the configuration required by measurements according to the 3GPP standard.

● The channel configuration defined in the standard for the ACLR measurement.● The spectral mask as defined in the 3GPP standard for SEM measurements.

If you need a different measurement configuration, you can change all parameters asrequired. Except for the dialog box described below, the measurement configurationmenus for the frequency sweep measurements are the same as in the Spectrum appli-cation.

Configuring Frequency Sweep Measurements


45User Manual 1178.4230.02 ─ 02

Refer to the User Manual of the R&S VSE for a detailed description on how to config-ure ACLR measurements.

● Channel Power ACLR Measurement......................................................................45● SEM Measurement Configuration...........................................................................45

3.3.1 Channel Power ACLR Measurement

Access: "Meas Setup" > "Overview"

Access: "Meas Setup" > "CP / ACLR Config"

The ACLR measurement and its settings are basically the same as in the spectrumapplication of the connected instrument. For a comprehensive description, see the con-nected instrument user manual.

In addition, the ACLR measurement in the NB-IoT application has several exclusivesettings not available in the spectrum application.

The signal description for ACLR measurements contains settings to describe generalphysical characteristics of the signal you are measuring.

Access: "Meas Setup" > "Signal Description"

● NB-IoT "Mode": The NB-IoT mode is always "FDD Uplink".● "Analysis Mode": The analysis mode selects whether the PUSCH and PUCCH or

the PRACH are analyzed.● "Subcarrier Spacing": The subcarrier spacing selects the bandwidth of the carrier.● "Adjacent Channels": Selects the adjacent channel configuration as specified by

3GPP 36.104 chapter 6.6.2.

3.3.2 SEM Measurement Configuration

Access: "Meas Setup" > "Overview"

Access: "Meas Setup" > "Overview" > "SEM Setup"

The SEM measurement and its settings are basically the same as in the spectrumapplication of the connected instrument. For a comprehensive description, see the con-nected instrument user manual.

In addition, the SEM measurement in the NB-IoT application has several exclusive set-tings not available in the spectrum application.

The signal description for SEM measurements contains settings to describe generalphysical characteristics of the signal you are measuring.

Access: "Meas Setup" > "Signal Description"

● NB-IoT "Mode": The NB-IoT mode is always "FDD Uplink".● "Analysis Mode": The SEM measurement only supports the PUSCH/PUCCH analy-

sis mode.

Note that SEM measurements are not possible if you measure with an R&S FSL.

Configuring Frequency Sweep Measurements

AnalysisR&S®VSE-K106

46User Manual 1178.4230.02 ─ 02

4 AnalysisThe application provides several tools to analyze the measurement results in moredetail.

● Configuring Tables / Numerical Results..................................................................46● Exporting Measurement Results.............................................................................46● Evaluation Range....................................................................................................47● Scale....................................................................................................................... 48● Result Settings........................................................................................................49● Markers................................................................................................................... 50

4.1 Configuring Tables / Numerical Results

The application allows you to customize the number of columns for some numericresult displays, for example the Allocation Summary.

► Click somewhere in the header row of the table.

The application opens a dialog box to add or remove columns.

4.2 Exporting Measurement Results

Access: "Edit" > "Trace Export"

In case you want to evaluate the data with external applications (for example in an MSExcel spreadsheet), you can export the measurement data to an ASCII file. The dataexport is available for I/Q measurements - EVM / Frequency Error / Power measure-ments and Time Alignment Error.

1. Select the "Trace Export Config" dialog box via the "Edit" menu.

2. Select the data you would like to export.

3. Select the results you would like to export from the "Specifics For" dropdown menu.

4. Export the data with the "Export Trace to ASCII File" feature.

Exporting Measurement Results


47User Manual 1178.4230.02 ─ 02

5. Select the location where you would like to save the data (as a .dat file).

Note that the measurement data stored in the file depend on the selected result display("Specifics For" selection).

As the basic principle is the same as in the I/Q Analyzer, refer to the R&S VSE UserManual for more information.

4.3 Evaluation Range

The evaluation range defines the signal parts that are considered during signal analy-sis.

NPUSCH Selection....................................................................................................... 47Slot Selection................................................................................................................ 47Evaluation range for the constellation diagram............................................................. 48

NPUSCH SelectionSelects a particular NPUSCH whose results the application displays.

Selecting "All" either displays the results of all NPUSCHs or calculates a statistic overall NPUSCHs that have been analyzed.

Remote command: [SENSe:][LTE:][CC<cc>:]NPUSch:SELect on page 119

Slot SelectionSelects the slots that the application evaluates. You can select that the results areevaluated over "All" slots, or a "Single" slot. If you select a single slot, you can definethe "Slot Nr" (number of the slot) that the results are displayed for.

You can select a single slot for the following measurements.● Result Summary● EVM vs Carrier / EVM vs Symbol / EVM vs Symbol X Carrier● Inband Emission● Spectrum Flatness / Spectrum Flatness Difference● Group Delay● Power vs Symbol X Carrier● Constellation Diagram

Evaluation Range


48User Manual 1178.4230.02 ─ 02

Remote command: [SENSe:][LTE:][CC<cc>:]SLOT:SELect on page 120

Evaluation range for the constellation diagramThe "Evaluation Range" dialog box defines the type of constellation points that are dis-played in the "Constellation Diagram".

By default the application displays all constellation points of the data that have beenevaluated. However, you can filter the results by several aspects.● Modulation

Filters the results to include only the selected type of modulation.● Allocation

Filters the results to include only a particular type of allocation.● Symbol (OFDM)

Filters the results to include only a particular OFDM symbol.● Carrier

Filters the results to include only a particular subcarrier.The result display is updated as soon as you make the changes.

Note that the constellation selection is applied to all windows in split screen mode if thewindows contain constellation diagrams.

Remote command: Modulation: [SENSe:][LTE:][CC<cc>:]MODulation:SELect on page 119Allocation: [SENSe:][LTE:][CC<cc>:]ALLocation:SELect on page 118Symbol: [SENSe:][LTE:][CC<cc>:]SYMBol:SELect on page 120Carrier: [SENSe:][LTE:][CC<cc>:]CARRier:SELect on page 118

4.4 Scale

Access: "Overview" > "Analysis" > "Scale"

Scaling settings define the diagram scale.

Y-Axis Scale..................................................................................................................48

Y-Axis ScaleThe y-axis scaling determines the vertical resolution of the measurement results. Thescaling you select always applies to the currently active screen and the correspondingresult display.

Usually, the best way to view the results is if they fit ideally in the diagram area in orderto view the complete trace. This is the way the application scales the y-axis if you areusing the automatic scale function.

But it may become necessary to see a more detailed version of the results. In thatcase, turn on fixed scaling for the y-axis by defining the minimum and maximum val-ues displayed on the vertical axis. Possible values and units depend on the result dis-play you want to adjust the scale of.

You can restore the default scale at any time with "Restore Scale".

Scale


49User Manual 1178.4230.02 ─ 02

Alternatively, you can scale the windows in the "Auto Set" menu. In addition to scalingthe window currently in focus ("Auto Scale Window"), there you can scale all windowsat the same time ("Auto Scale All").

Remote command: DISPlay[:WINDow<n>]:TRACe<t>:Y[:SCALe]:AUTO ONCE on page 121DISPlay[:WINDow<n>]:TRACe<t>:Y[:SCALe]:MAXimum on page 121DISPlay[:WINDow<n>]:TRACe<t>:Y[:SCALe]:MINimum on page 121

4.5 Result Settings

Access: "Overview" > "Analysis" > "Result Settings"

Result settings define the way certain measurement results are displayed.

EVM Unit....................................................................................................................... 49Bit Stream Format......................................................................................................... 49Carrier Axes.................................................................................................................. 50Marker Coupling............................................................................................................50

EVM UnitSelects the unit for graphic and numerical EVM measurement results.

Possible units are dB and %.

Remote command: UNIT:EVM on page 123

Bit Stream FormatSelects the way the bit stream is displayed.

The bit stream is either a stream of raw bits or of symbols. In case of the symbol for-mat, the bits that belong to a symbol are shown as hexadecimal numbers with two dig-its.

Examples:

Figure 4-1: Bit stream display in uplink application if the bit stream format is set to "symbols"

Result Settings


50User Manual 1178.4230.02 ─ 02

Figure 4-2: Bit stream display in uplink application if the bit stream format is set to "bits"

Remote command: UNIT:BSTR on page 122

Carrier AxesSelects the scale of the x-axis for result displays that show results of OFDM subcarri-ers.● X-axis shows the frequency of the subcarrier

● X-axis shows the number of the subcarrier

Remote command: UNIT:CAXes on page 123

Marker CouplingCouples or decouples markers that are active in multiple result displays.

When you turn on this feature, the application moves the marker to its new position inall active result displays.

When you turn it off, you can move the markers in different result displays independentfrom each other.

Remote command: CALCulate:MARKer:COUPling on page 122

4.6 Markers

Access: "Overview" > "Analysis" > "Marker"

Markers are available for most of the I/Q measurement result displays. The functional-ity (setting and positioning) is the same as in the base software.

Markers


51User Manual 1178.4230.02 ─ 02

Markers in result displays with a third aspectIn result displays that have a third dimension (EVM vs Symbol x Carrier etc.), you canposition a marker on a particular symbol in a particular carrier.When you activate a marker, you can select the symbol and carrier you want to posi-tion the marker on. Alternatively, you can define the marker position in the "MarkerConfiguration" dialog box, which is expanded accordingly.

Figure 4-3: Marker Configuration dialog, the "Carrier" field is only available for result displays with athird dimension.

For a comprehensive description of the marker functionality, see the correspondingchapters in the documentation of the connected instrument.

Markers

Remote ControlR&S®VSE-K106

52User Manual 1178.4230.02 ─ 02

5 Remote ControlThe following remote control commands are required to configure and perform LTENB-IoT measurements in a remote environment. The R&S VSE must already be set upfor remote operation in a network as described in the base unit manual.

Universal functionalityNote that basic tasks that are also performed in the base unit in the same way are notdescribed here. For a description of such tasks, see the R&S VSE User Manual.In particular, this includes:● Managing Settings and Results, i.e. storing and loading settings and result data.● Basic instrument configuration, e.g. checking the system configuration, customizing

the screen layout, or configuring networks and remote operation.● Using the common status registers (specific status registers for Pulse measure-

ments are not used).

● Common Suffixes....................................................................................................52● Introduction............................................................................................................. 53● Remote Commands to Select the LTE Application.................................................58● Configuring the Screen Layout................................................................................58● Remote Commands to Read Trace Data................................................................68● Remote Commands to Read Numeric Results....................................................... 79● Remote Commands to Configure the Application...................................................87● Analysis.................................................................................................................118

5.1 Common Suffixes

In the LTE NB-IoT measurement application, the following common suffixes are usedin remote commands:

Table 5-1: Common suffixes used in remote commands in the LTE NB-IoT measurement application

Suffix Value range Description

<m> 1..4 Marker

<n> 1..16 Window (in the currently selected channel)

<t> 1..6 Trace

<k> irrelevant Limit line

<ant> 1..2 Selects an antenna for MIMO measurements.

<cc> 1..5 Selects a component carrier.

Irrelevant for the NB-IoT application.

Common Suffixes


53User Manual 1178.4230.02 ─ 02

Suffix Value range Description

<k> --- Selects a limit line.

Irrelevant for the NB-IoT application.

<np> 0...20 Selects a NPUSCH (NB-IoT uplink only)

5.2 Introduction

Commands are program messages that a controller (e.g. a PC) sends to the instru-ment or software. They operate its functions ('setting commands' or 'events') andrequest information ('query commands'). Some commands can only be used in oneway, others work in two ways (setting and query). If not indicated otherwise, the com-mands can be used for settings and queries.

The syntax of a SCPI command consists of a header and, in most cases, one or moreparameters. To use a command as a query, you have to append a question mark afterthe last header element, even if the command contains a parameter.

A header contains one or more keywords, separated by a colon. Header and parame-ters are separated by a "white space" (ASCII code 0 to 9, 11 to 32 decimal, e.g. blank).If there is more than one parameter for a command, these are separated by a commafrom one another.

Only the most important characteristics that you need to know when working with SCPIcommands are described here. For a more complete description, refer to the UserManual of the R&S VSE.

Remote command examplesNote that some remote command examples mentioned in this general introduction maynot be supported by this particular application.

5.2.1 Conventions used in Descriptions

Note the following conventions used in the remote command descriptions:● Command usage

If not specified otherwise, commands can be used both for setting and for queryingparameters.If a command can be used for setting or querying only, or if it initiates an event, theusage is stated explicitly.

● Parameter usageIf not specified otherwise, a parameter can be used to set a value and it is theresult of a query.Parameters required only for setting are indicated as Setting parameters.Parameters required only to refine a query are indicated as Query parameters.Parameters that are only returned as the result of a query are indicated as Returnvalues.

Introduction


54User Manual 1178.4230.02 ─ 02

● ConformityCommands that are taken from the SCPI standard are indicated as SCPI con-firmed. All commands used by the R&S VSE follow the SCPI syntax rules.

● Asynchronous commandsA command which does not automatically finish executing before the next com-mand starts executing (overlapping command) is indicated as an Asynchronouscommand.

● Reset values (*RST)Default parameter values that are used directly after resetting the instrument (*RSTcommand) are indicated as *RST values, if available.

● Default unitThis is the unit used for numeric values if no other unit is provided with the parame-ter.

● Manual operationIf the result of a remote command can also be achieved in manual operation, a linkto the description is inserted.

5.2.2 Long and Short Form

The keywords have a long and a short form. You can use either the long or the shortform, but no other abbreviations of the keywords.

The short form is emphasized in upper case letters. Note however, that this emphasisonly serves the purpose to distinguish the short from the long form in the manual. Forthe instrument, the case does not matter.

Example: SENSe:FREQuency:CENTer is the same as SENS:FREQ:CENT.

5.2.3 Numeric Suffixes

Some keywords have a numeric suffix if the command can be applied to multipleinstances of an object. In that case, the suffix selects a particular instance (e.g. a mea-surement window).

Numeric suffixes are indicated by angular brackets (<n>) next to the keyword.

If you don't quote a suffix for keywords that support one, a 1 is assumed.

Example: DISPlay[:WINDow<1...4>]:ZOOM:STATe enables the zoom in a particular mea-surement window, selected by the suffix at WINDow.

DISPlay:WINDow4:ZOOM:STATe ON refers to window 4.

Introduction


55User Manual 1178.4230.02 ─ 02

5.2.4 Optional Keywords

Some keywords are optional and are only part of the syntax because of SCPI compli-ance. You can include them in the header or not.

Note that if an optional keyword has a numeric suffix and you need to use the suffix,you have to include the optional keyword. Otherwise, the suffix of the missing keywordis assumed to be the value 1.

Optional keywords are emphasized with square brackets.

Example: Without a numeric suffix in the optional keyword:[SENSe:]FREQuency:CENTer is the same as FREQuency:CENTerWith a numeric suffix in the optional keyword:DISPlay[:WINDow<1...4>]:ZOOM:STATeDISPlay:ZOOM:STATe ON enables the zoom in window 1 (no suffix).

DISPlay:WINDow4:ZOOM:STATe ON enables the zoom in window 4.

5.2.5 Alternative Keywords

A vertical stroke indicates alternatives for a specific keyword. You can use both key-words to the same effect.

Example: [SENSe:]BANDwidth|BWIDth[:RESolution]In the short form without optional keywords, BAND 1MHZ would have the same effectas BWID 1MHZ.

5.2.6 SCPI Parameters

Many commands feature one or more parameters.

If a command supports more than one parameter, these are separated by a comma.

Example: LAYout:ADD:WINDow Spectrum,LEFT,MTABle

Parameters may have different forms of values.

● Numeric Values.......................................................................................................56● Boolean...................................................................................................................56● Character Data........................................................................................................57● Character Strings.................................................................................................... 57● Block Data...............................................................................................................57

Introduction


56User Manual 1178.4230.02 ─ 02

5.2.6.1 Numeric Values

Numeric values can be entered in any form, i.e. with sign, decimal point or exponent. Incase of physical quantities, you can also add the unit. If the unit is missing, the com-mand uses the basic unit.

Example: With unit: SENSe:FREQuency:CENTer 1GHZWithout unit: SENSe:FREQuency:CENTer 1E9 would also set a frequency of 1 GHz.

Values exceeding the resolution of the instrument are rounded up or down.

If the number you have entered is not supported (e.g. in case of discrete steps), thecommand returns an error.

Instead of a number, you can also set numeric values with a text parameter in specialcases.

● MIN/MAXDefines the minimum or maximum numeric value that is supported.

● DEFDefines the default value.

● UP/DOWNIncreases or decreases the numeric value by one step. The step size depends onthe setting. In some cases you can customize the step size with a correspondingcommand.

Querying numeric values

When you query numeric values, the system returns a number. In case of physicalquantities, it applies the basic unit (e.g. Hz in case of frequencies). The number of dig-its after the decimal point depends on the type of numeric value.

Example: Setting: SENSe:FREQuency:CENTer 1GHZQuery: SENSe:FREQuency:CENTer? would return 1E9

In some cases, numeric values may be returned as text.

● INF/NINFInfinity or negative infinity. Represents the numeric values 9.9E37 or -9.9E37.

● NANNot a number. Represents the numeric value 9.91E37. NAN is returned in case oferrors.

5.2.6.2 Boolean

Boolean parameters represent two states. The "ON" state (logically true) is represen-ted by "ON" or a numeric value 1. The "OFF" state (logically untrue) is represented by"OFF" or the numeric value 0.

Introduction


57User Manual 1178.4230.02 ─ 02

Querying Boolean parameters

When you query Boolean parameters, the system returns either the value 1 ("ON") orthe value 0 ("OFF").

Example: Setting: DISPlay:WINDow:ZOOM:STATe ONQuery: DISPlay:WINDow:ZOOM:STATe? would return 1

5.2.6.3 Character Data

Character data follows the syntactic rules of keywords. You can enter text using a shortor a long form. For more information see Chapter 5.2.2, "Long and Short Form",on page 54.

Querying text parameters

When you query text parameters, the system returns its short form.

Example: Setting: SENSe:BANDwidth:RESolution:TYPE NORMalQuery: SENSe:BANDwidth:RESolution:TYPE? would return NORM

5.2.6.4 Character Strings

Strings are alphanumeric characters. They have to be in straight quotation marks. Youcan use a single quotation mark ( ' ) or a double quotation mark ( " ).

Example: INSTRument:DELete 'Spectrum'

5.2.6.5 Block Data

Block data is a format which is suitable for the transmission of large amounts of data.

The ASCII character # introduces the data block. The next number indicates how manyof the following digits describe the length of the data block. In the example the 4 follow-ing digits indicate the length to be 5168 bytes. The data bytes follow. During the trans-mission of these data bytes all end or other control signs are ignored until all bytes aretransmitted. #0 specifies a data block of indefinite length. The use of the indefinite for-mat requires an NL^END message to terminate the data block. This format is usefulwhen the length of the transmission is not known or if speed or other considerationsprevent segmentation of the data into blocks of definite length.

Introduction


58User Manual 1178.4230.02 ─ 02

5.3 Remote Commands to Select the LTE Application

INSTrument[:SELect]........................................................................................................58

INSTrument[:SELect] <ChannelType>

This command selects a new measurement channel with the defined channel type.

Parameters:<ChannelType> NIOT

LTE NB-IoT measurement channel

Example: //Select LTE NB-IoT applicationINST NIOT

5.4 Configuring the Screen Layout

● General Layout........................................................................................................58● Configuring the Layout over all Channels............................................................... 59● Configuring the Layout of a Channel.......................................................................63

5.4.1 General Layout

The following commands are required to configure general window layout, independentof the application.

Note that the suffix <n> always refers to the window in the currently selected measure-ment channel.

DISPlay[:WINDow<n>][:SUBWindow<sub>]:SELect............................................................ 58

DISPlay[:WINDow<n>][:SUBWindow<sub>]:SELect

This command sets the focus on the selected result display window.

This window is then the active window.

For measurements with multiple results in subwindows, the command also selects thesubwindow. Use this command to select the (sub)window before querying trace data.

Suffix: <n>

.Window

<sub> 1 | 2 | 3 | 4Selects a subwindow (e.g. for MIMO data stream results)

Example: //Put the focus on window 1DISP:WIND1:SEL

Example: //Put the focus on subwindow 2 in window 1DISP:WIND1:SUBW2:SEL

Configuring the Screen Layout


59User Manual 1178.4230.02 ─ 02

Usage: Event

5.4.2 Configuring the Layout over all Channels

The following commands are required to change the evaluation type and rearrange thescreen layout across measurement channels as you do in manual operation.

For compatibility with other Rohde & Schwarz Signal and Spectrum Analyzers, the lay-out commands described in Chapter 5.4.3, "Configuring the Layout of a Channel",on page 63 are also supported. Note, however, that the commands described thereonly allow you to configure the layout within the active measurement channel.

LAYout:GLOBal:ADD[:WINDow]?...................................................................................... 59LAYout:GLOBal:CATalog[:WINDow]?................................................................................ 61LAYout:GLOBal:IDENtify[:WINDow]?................................................................................. 61LAYout:GLOBal:REMove[:WINDow].................................................................................. 62LAYout:GLOBal:REPLace[:WINDow]................................................................................. 62

LAYout:GLOBal:ADD[:WINDow]?<ExChanName>,<ExWinName>,<Direction>,<NewChanName>,<NewWinType>

This command adds a window to the display next to an existing window. The new win-dow may belong to a different channel than the existing window.

To replace an existing window, use the LAYout:GLOBal:REPLace[:WINDow] com-mand.

Parameters:<ExChanName> string

Name of an existing channel

<ExWinName> stringName of the existing window within the <ExChanName> chan-nel the new window is inserted next to.By default, the name of a window is the same as its index. Todetermine the name and index of all active windows use theLAYout:GLOBal:IDENtify[:WINDow]? query.

<Direction> LEFT | RIGHt | ABOVe | BELow | TABDirection the new window is added relative to the existing win-dow.TABThe new window is added as a new tab in the specified existingwindow.

<NewChanName> stringName of the channel for which a new window is to be added.



60User Manual 1178.4230.02 ─ 02

<NewWinType> stringType of result display (evaluation method) you want to add.See the table below for available parameter values.

Return values: <NewWindowName> When adding a new window, the command returns its name (by

default the same as its number) as a result.

Example: LAYout:GLOBal:ADD:WINDow? 'IQAnalyzer','1',RIGH,'IQ Analyzer2','FREQ'Adds a new window named 'Spectrum' with a Spectrum displayto the right of window 1 in the channel 'IQ Analyzer'.

Usage: Query only

Table 5-2: <WindowType> parameter values for NB-IoT Uplink Measurement application

Parameter value Window type

ASUM Allocation Summary

BSTR Bitstream

CBUF Capture Buffer

CCDF CCDF

CONS Constellation Diagram

EVCA EVM vs Carrier

EVSY EVM vs Symbol

EVSC EVM vs Symbol X Carrier

GDEL Group Delay

IE Inband Emission

IEA Inband Emission All

MTAB Marker Table

PSPE Power Spectrum

PVSC Power vs Symbol X Carrier

RSUM Result Summary

SFD Spectrum Flatness Difference

SFL Spectrum Flatness

ACLR measurements

DIAG Diagram

PEAK Peak List

MTAB Marker Table

RSUM Result Summary



61User Manual 1178.4230.02 ─ 02

LAYout:GLOBal:CATalog[:WINDow]?

This command queries the name and index of all active windows from top left to bot-tom right for each active channel. The result is a comma-separated list of values foreach window, with the syntax:

<ChannelName_1>: <WindowName_1>,<WindowIndex_1>..<WindowName_n>,<Win-dowIndex_n>

..

<ChannelName_m>: <WindowName_1>,<WindowIndex_1>..<WindowName_n>,<Win-dowIndex_n>

Return values: <ChannelName> String containing the name of the channel. The channel name is

displayed as the tab label for the measurement channel.

<WindowName> stringName of the window.In the default state, the name of the window is its index.

<WindowIndex> numeric valueIndex of the window.

Example: LAY:GLOB:CAT?Result:IQ Analyzer: '1',1,'2',2Analog Demod: '1',1,'4',4For the I/Q Analyzer channel, two windows are displayed,named '2' (at the top or left), and '1' (at the bottom or right).For the Analog Demodulation channel, two windows are dis-played, named '1' (at the top or left), and '4' (at the bottom orright).

Usage: Query only

LAYout:GLOBal:IDENtify[:WINDow]? <ChannelName>,<WindowName>

This command queries the index of a particular display window in the specified chan-nel.

Note: to query the name of a particular window, use the LAYout:WINDow<n>:IDENtify? query.

Parameters:<ChannelName> String containing the name of the channel. The channel name is

displayed as the tab label for the measurement channel.

Query parameters: <WindowName> String containing the name of a window.

Return values: <WindowIndex> Index number of the window.



62User Manual 1178.4230.02 ─ 02

Example: LAYout:GLOBal:ADD:WINDow? IQ,'1',RIGH,'Spectrum',FREQAdds a new window named 'Spectrum' with a Spectrum displayto the right of window 1.

Example: LAYout:GLOBal:IDENtify? 'IQ Analyzer','Spectrum'Result:2Window index is: 2.

Usage: Query only

LAYout:GLOBal:REMove[:WINDow] <ChannelName>,<WindowName>

This command removes a window from the display.

Parameters:<ChannelName> String containing the name of the channel.

<WindowName> String containing the name of the window.

Usage: Event

LAYout:GLOBal:REPLace[:WINDow]<ExChannelName>,<WindowName>,<NewChannelName>,<WindowType>

This command replaces the window type (for example from "Diagram" to "Result Sum-mary") of an already existing window while keeping its position, index and windowname.

To add a new window, use the LAYout:GLOBal:ADD[:WINDow]? command.

Parameters:<ExChannelName> String containing the name of the channel in which a window is

to be replaced. The channel name is displayed as the tab labelfor the measurement channel.

<WindowName> String containing the name of the existing window.To determine the name and index of all active windows, use theLAYout:GLOBal:CATalog[:WINDow]? query.

<NewChannelName> String containing the name of the channel for which a new win-dow will be created.

<WindowType> Type of result display you want to use in the existing window.Note that the window type must be valid for the specified chan-nel (<NewChannelName>).See LAYout:ADD[:WINDow]? on page 63 for a list of availa-ble window types.



63User Manual 1178.4230.02 ─ 02

Example: LAY:GLOB:REPL:WIND 'IQ Analyzer','1','AnalogDemod',MTABReplaces the I/Q Analyzer result display in window 1 by amarker table for the AnalogDemod channel.

5.4.3 Configuring the Layout of a Channel

The following commands are required to change the evaluation type and rearrange thescreen layout for a measurement channel as you do using the SmartGrid in manualoperation. Since the available evaluation types depend on the selected application,some parameters for the following commands also depend on the selected measure-ment channel.

Note that the suffix <n> always refers to the window in the currently selected measure-ment channel.

LAYout:ADD[:WINDow]?...................................................................................................63LAYout:CATalog[:WINDow]?.............................................................................................65LAYout:IDENtify[:WINDow]?..............................................................................................65LAYout:REMove[:WINDow]...............................................................................................66LAYout:REPLace[:WINDow]..............................................................................................66LAYout:WINDow<n>:ADD?...............................................................................................66LAYout:WINDow<n>:IDENtify?..........................................................................................67LAYout:WINDow<n>:REMove........................................................................................... 68LAYout:WINDow<n>:REPLace..........................................................................................68

LAYout:ADD[:WINDow]? <WindowName>,<Direction>,<WindowType>

This command adds a window to the display in the active channel.

This command is always used as a query so that you immediately obtain the name ofthe new window as a result.

To replace an existing window, use the LAYout:REPLace[:WINDow] command.

Query parameters: <WindowName> String containing the name of the existing window the new win-

dow is inserted next to.By default, the name of a window is the same as its index. Todetermine the name and index of all active windows, use theLAYout:CATalog[:WINDow]? query.

<Direction> LEFT | RIGHt | ABOVe | BELowDirection the new window is added relative to the existing win-dow.

<WindowType> text valueType of result display (evaluation method) you want to add.See the table below for available parameter values.Note that the window type must be valid for the active channel.To create a window for a different channel use the LAYout:GLOBal:REPLace[:WINDow] command.



64User Manual 1178.4230.02 ─ 02



Usage: Query only

Manual operation: See "Capture Buffer" on page 10See "EVM vs Carrier" on page 11See "EVM vs Symbol" on page 11See "Power Spectrum" on page 12See "Spectrum Flatness" on page 13See "Channel Group Delay" on page 13See "Spectrum Flatness Difference" on page 13See "Constellation Diagram" on page 14See "CCDF" on page 14See "Allocation Summary" on page 15See "Bit Stream" on page 16See "EVM vs Sym x Carr" on page 16See "Power vs Symbol x Carrier" on page 17See "Result Summary" on page 17See " Marker Table " on page 20

Table 5-3: <WindowType> parameter values for NB-IoT Uplink Measurement application


I/Q Measurements

ASUM Allocation Summary

BSTR Bitstream

CBUF Capture Buffer

CCDF CCDF

CONS Constellation Diagram

EVCA EVM vs. Carrier

EVSY EVM vs. Symbol

EVSC EVM vs. Symbol X Carrier

GDEL Group Delay

IE Inband Emission

IEA Inband Emission All

MTAB Marker Table

PSPE Power Spectrum

PVSC Power vs. Symbol X Carrier

RSUM Result Summary

SFD Spectrum Flatness Difference

SFL Spectrum Flatness



65User Manual 1178.4230.02 ─ 02


ACLR measurements

DIAG Diagram

PEAK Peak List

MTAB Marker Table

RSUM Result Summary

LAYout:CATalog[:WINDow]?

This command queries the name and index of all active windows in the active channelfrom top left to bottom right. The result is a comma-separated list of values for eachwindow, with the syntax:

<WindowName_1>,<WindowIndex_1>..<WindowName_n>,<WindowIndex_n>

To query the name and index of all windows in all channels use the LAYout:GLOBal:CATalog[:WINDow]? command.

Return values: <WindowName> string

Name of the window.In the default state, the name of the window is its index.

<WindowIndex> numeric valueIndex of the window.

Example: LAY:CAT?Result:'2',2,'1',1Two windows are displayed, named '2' (at the top or left), and '1'(at the bottom or right).

Usage: Query only

LAYout:IDENtify[:WINDow]? <WindowName>

This command queries the index of a particular display window in the active channel.

Note: to query the name of a particular window, use the LAYout:WINDow<n>:IDENtify? query.

To query the index of a window in a different channel use the LAYout:GLOBal:IDENtify[:WINDow]? command.

Query parameters: <WindowName> String containing the name of a window.

Return values: <WindowIndex> Index number of the window.



66User Manual 1178.4230.02 ─ 02

Example: LAY:WIND:IDEN? '2'Queries the index of the result display named '2'.Response:2

Usage: Query only

LAYout:REMove[:WINDow] <WindowName>

This command removes a window from the display in the active channel.

To remove a window for a different channel use the LAYout:GLOBal:REMove[:WINDow] command.

Setting parameters: <WindowName> String containing the name of the window.

In the default state, the name of the window is its index.

Example: LAY:REM '2'Removes the result display in the window named '2'.

Usage: Event

LAYout:REPLace[:WINDow] <WindowName>,<WindowType>

This command replaces the window type (for example from "Diagram" to "Result Sum-mary") of an already existing window in the active channel while keeping its position,index and window name.

To add a new window, use the LAYout:ADD[:WINDow]? command.

Parameters:<WindowName> String containing the name of the existing window.

By default, the name of a window is the same as its index. Todetermine the name and index of all active windows in the activechannel, use the LAYout:CATalog[:WINDow]? query.

<WindowType> Type of result display you want to use in the existing window.See LAYout:ADD[:WINDow]? on page 63 for a list of availablewindow types.Note that the window type must be valid for the active channel.To create a window for a different channel use the LAYout:GLOBal:REPLace[:WINDow] command.

Example: LAY:REPL:WIND '1',MTABReplaces the result display in window 1 with a marker table.

LAYout:WINDow<n>:ADD? <Direction>,<WindowType>

This command adds a measurement window to the display. Note that with this com-mand, the suffix <n> determines the existing window next to which the new window isadded, as opposed to LAYout:ADD[:WINDow]?, for which the existing window isdefined by a parameter.



67User Manual 1178.4230.02 ─ 02

To replace an existing window, use the LAYout:WINDow<n>:REPLace command.

This command is always used as a query so that you immediately obtain the name ofthe new window as a result.

Suffix: <n>

.Window

Parameters:<Direction> LEFT | RIGHt | ABOVe | BELow

<WindowType> Type of measurement window you want to add.See LAYout:ADD[:WINDow]? on page 63 for a list of availablewindow types.Note that the window type must be valid for the active channel.To create a window for a different channel use the LAYout:GLOBal:ADD[:WINDow]? command.



Example: LAY:WIND1:ADD? LEFT,MTABResult:'2'Adds a new window named '2' with a marker table to the left ofwindow 1.

Usage: Query only

LAYout:WINDow<n>:IDENtify?

This command queries the name of a particular display window (indicated by the <n>suffix) in the active channel.

Note: to query the index of a particular window, use the LAYout:IDENtify[:WINDow]? command.

Suffix: <n>

.Window

Return values: <WindowName> String containing the name of a window.

In the default state, the name of the window is its index.

Example: LAY:WIND2:IDEN?Queries the name of the result display in window 2.Response:'2'

Usage: Query only



68User Manual 1178.4230.02 ─ 02

LAYout:WINDow<n>:REMove

This command removes the window specified by the suffix <n> from the display in theactive channel.

The result of this command is identical to the LAYout:REMove[:WINDow] command.

To remove a window in a different channel use the LAYout:GLOBal:REMove[:WINDow] command.

Suffix: <n>

.Window

Example: LAY:WIND2:REMRemoves the result display in window 2.

Usage: Event

LAYout:WINDow<n>:REPLace <WindowType>

This command changes the window type of an existing window (specified by the suffix<n>) in the active channel.

The result of this command is identical to the LAYout:REPLace[:WINDow] com-mand.

To add a new window, use the LAYout:WINDow<n>:ADD? command.

Suffix: <n>

.Window

Setting parameters: <WindowType> Type of measurement window you want to replace another one

with.See LAYout:ADD[:WINDow]? on page 63 for a list of availablewindow types.Note that the window type must be valid for the active channel.To create a window for a different channel use the LAYout:GLOBal:REPLace[:WINDow] command.

Example: LAY:WIND2:REPL MTABReplaces the result display in window 2 with a marker table.

5.5 Remote Commands to Read Trace Data

● Using the TRACe[:DATA] Command......................................................................69● Remote Commands to Read Measurement Results...............................................77

Remote Commands to Read Trace Data


69User Manual 1178.4230.02 ─ 02

5.5.1 Using the TRACe[:DATA] Command

This chapter contains information on the TRACe:DATA command and a detaileddescription of the characteristics of that command.

The TRACe:DATA command queries the trace data or results of the currently activemeasurement or result display. The type, number and structure of the return values arespecific for each result display. In case of results that have any kind of unit, the com-mand returns the results in the unit you have currently set for that result display.

Note also that return values for results that are available for both downlink and uplinkmay be different.

For several result displays, the command also supports various SCPI parameters incombination with the query. If available, each SCPI parameter returns a differentaspect of the results. If SCPI parameters are supported, you have to quote one in thequery.

Example: TRAC2:DATA? TRACE1

The format of the return values is either in ASCII or binary characters and depends onthe format you have set with FORMat[:DATA].

Following this detailed description, you will find a short summary of the most importantfunctions of the command (TRACe<n>[:DATA]?).

Selecting a measurement windowBefore querying results, you have to select the measurement window with the suffix<n> at TRACe. The range of <n> depends on the number of active measurement win-dows.

● Adjacent Channel Leakage Ratio............................................................................70● Allocation Summary................................................................................................ 70● Bit Stream............................................................................................................... 71● Capture Buffer.........................................................................................................71● CCDF...................................................................................................................... 71● Channel and Spectrum Flatness.............................................................................72● Channel and Spectrum Flatness Difference........................................................... 72● Channel Group Delay..............................................................................................73● Constellation Diagram.............................................................................................73● EVM vs Carrier........................................................................................................73● EVM vs Symbol.......................................................................................................74● EVM vs Symbol x Carrier........................................................................................74● Frequency Error vs Symbol.....................................................................................74● Power Spectrum......................................................................................................75● Power vs Symbol x Carrier......................................................................................75● Spectrum Emission Mask........................................................................................75● Return Value Codes................................................................................................76



70User Manual 1178.4230.02 ─ 02

5.5.1.1 Adjacent Channel Leakage Ratio

For the ACLR result display, the number and type of returns values depend on theparameter.

● TRACE1Returns one value for each trace point.

● LISTReturns the contents of the ACLR table.For each channel, it returns six values.<channel type>, <bandwidth>, <spacing offset>, <power oflower channel>, <power of upper channel>, <limit>, ...The unit of the <bandwidth> and <spacing offset> is Hz.The unit of the power values is either dBm for the TX channel or dB for the neigh-boring channels.The unit of the limit is dB.The <channel type> is encoded. For the code assignment see Chap-ter 5.5.1.17, "Return Value Codes", on page 76.Note that the TX channel does not have a <spacing offset>, <power oflower channel> and <limit>. NaN is returned instead.

5.5.1.2 Allocation Summary

For the Allocation Summary, the command returns seven values for each line of thetable.

<subframe>, <allocation ID>, <number of RB>, <offset RB>,<modulation>, <absolute power>, <EVM>, ...The unit for <absolute power> is always dBm. The unit for <EVM> depends onUNIT:EVM. All other values have no unit.

The <allocation ID> and <modulation> are encoded. For the code assignmentsee Chapter 5.5.1.17, "Return Value Codes", on page 76.

Note that the data format of the return values is always ASCII.

Example:

TRAC:DATA? TRACE1 would return:0, -40, 10, 2, 2, -84.7431947342849, 2.68723483754626E-06,0, -41, 0, 0, 6, -84.7431432845264, 2.37549449584568E-06,0, -42, 0, 0, 6, -80.9404231343884, 3.97834623871343E-06,...



71User Manual 1178.4230.02 ─ 02

5.5.1.3 Bit Stream

For the Bit Stream result display, the command returns five values and the bitstreamfor each line of the table.

<subframe>, <allocation ID>, <codeword>, <modulation>, <# ofsymbols/bits>, <hexadecimal/binary numbers>,...All values have no unit. The format of the bitstream depends on Bit Stream Format.

The <allocation ID>, <codeword> and <modulation> are encoded. For thecode assignment see Chapter 5.5.1.17, "Return Value Codes", on page 76.

For symbols or bits that are not transmitted, the command returns● "FFF" if the bit stream format is "Symbols"● "9" if the bit stream format is "Bits".

For symbols or bits that could not be decoded because the number of layer exceedsthe number of receive antennas, the command returns● "FFE" if the bit stream format is "Symbols"● "8" if the bit stream format is "Bits".

Note that the data format of the return values is always ASCII.

Example:

TRAC:DATA? TRACE1 would return:0, -40, 0, 2, 0, 03, 01, 02, 03, 03, 00, 00, 00, 01, 02, 02, ...<continues like this until the next data block starts or the end of data is reached>0, -40, 0, 2, 32, 03, 03, 00, 00, 03, 01, 02, 00, 01, 00, ...

5.5.1.4 Capture Buffer

For the Capture Buffer result display, the command returns one value for each I/Qsample in the capture buffer.

<absolute power>, ...The unit is always dBm.

The following parameters are supported.● TRACE1

5.5.1.5 CCDF

For the CCDF result display, the type of return values depends on the parameter.

● TRACE1



72User Manual 1178.4230.02 ─ 02

Returns the probability values (y-axis).<# of values>, <probability>, ...The unit is always %.The first value that is returned is the number of the following values.

● TRACE2Returns the corresponding power levels (x-axis).<# of values>, <relative power>, ...The unit is always dB.The first value that is returned is the number of the following values.

5.5.1.6 Channel and Spectrum Flatness

For the Channel Flatness result display, the command returns one value for each tracepoint.

<relative power>, ...The unit is always dB.


Returns the average power over all subframes.● TRACE2

Returns the minimum power found over all subframes. If you are analyzing a partic-ular subframe, it returns nothing.

● TRACE3Returns the maximum power found over all subframes. If you are analyzing a par-ticular subframe, it returns nothing.

5.5.1.7 Channel and Spectrum Flatness Difference

For the Channel Flatness Difference result display, the command returns one value foreach trace point.

<relative power>, ...The unit is always dB. The number of values depends on the selected LTE bandwidth.


Returns the average power over all subframes.● TRACE2

Returns the minimum power found over all subframes. If you are analyzing a partic-ular subframe, it returns nothing.

● TRACE3Returns the maximum power found over all subframes. If you are analyzing a par-ticular subframe, it returns nothing.



73User Manual 1178.4230.02 ─ 02

5.5.1.8 Channel Group Delay

For the Channel Group Delay result display, the command returns one value for eachtrace point.

<group delay>, ...The unit is always ns. The number of values depends on the selected LTE bandwidth.


Returns the group delay.

5.5.1.9 Constellation Diagram

For the Constellation Diagram, the command returns two values for each constellationpoint.

<I[Slot0][Sym0][Carrier1]>, <Q[Slot0][Sym0][Carrier1]>, ..., <I[Slot0][Sym0][Carrier(n)]>, <Q[Slot0][Sym0][Carrier(n)]>,


<I[Slot0][Sym(n)][Carrier1]>, <Q[Slot0][Sym(n)][Carrier1]>, ..., <I[Slot0][Sym(n)][Carrier(n)]>, <Q[Slot0][Sym(n)][Carrier(n)]>,



<I[Slot(n)][Sym(n)][Carrier1]>, <Q[Slot(n)][Sym(n)][Carrier1]>, ..., <I[Slot(n)][Sym(n)][Carrier(n)]>,<Q[Slot(n)][Sym(n)][Carrier(n)]>

With Slot = slot number and Sym = symbol of that slot.

The I and Q values have no unit.

The number of return values depends on the constellation selection. By default, itreturns all resource elements including the DC carrier.


Returns all constellation points included in the selection.

5.5.1.10 EVM vs Carrier

For the EVM vs Carrier result display, the command returns one value for each subcar-rier that has been analyzed.

<EVM>, ...The unit depends on UNIT:EVM.




74User Manual 1178.4230.02 ─ 02

Returns the average EVM over all subframes● TRACE2

Returns the minimum EVM found over all subframes. If you are analyzing a particu-lar subframe, it returns nothing.

● TRACE3Returns the maximum EVM found over all subframes. If you are analyzing a partic-ular subframe, it returns nothing.

5.5.1.11 EVM vs Symbol

For the EVM vs Symbol result display, the command returns one value for each OFDMsymbol that has been analyzed.

<EVM>, ...For measurements on a single subframe, the command returns the symbols of thatsubframe only.

The unit depends on UNIT:EVM.


5.5.1.12 EVM vs Symbol x Carrier

For the EVM vs Symbol x Carrier, the command returns one value for each resourceelement.

<EVM[Symbol(0),Carrier(1)]>, ..., <EVM[Symbol(0),Carrier(n)]>,<EVM[Symbol(1),Carrier(1)]>, ..., <EVM[Symbol(1),Carrier(n)]>,...<EVM[Symbol(n),Carrier(1)]>, ..., <EVM[Symbol(n),Carrier(n)]>,The unit depends on UNIT:EVM.

Resource elements that are unused return NAN.


5.5.1.13 Frequency Error vs Symbol

For the Frequency Error vs Symbol result display, the command returns one value foreach OFDM symbol that has been analyzed.

<frequency error>,...The unit is always Hz.



75User Manual 1178.4230.02 ─ 02


5.5.1.14 Power Spectrum

For the Power Spectrum result display, the command returns one value for each tracepoint.

<power>,...The unit is always dBm/Hz.


5.5.1.15 Power vs Symbol x Carrier

For the Power vs Symbol x Carrier, the command returns one value for each resourceelement.

<P[Symbol(0),Carrier(1)]>, ..., <P[Symbol(0),Carrier(n)]>,<P[Symbol(1),Carrier(1)]>, ..., <P[Symbol(1),Carrier(n)]>,...<P[Symbol(n),Carrier(1)]>, ..., <P[Symbol(n),Carrier(n)]>,with P = Power of a resource element.

The unit is always dBm.

Resource elements that are unused return NAN.


5.5.1.16 Spectrum Emission Mask

For the SEM measurement, the number and type of returns values depend on theparameter.

● TRACE1Returns one value for each trace point.<absolute power>, ...The unit is always dBm.

● LISTReturns the contents of the SEM table. For every frequency in the spectrum emis-sion mask, it returns 11 values.<index>, <start frequency in Hz>, <stop frequency in Hz>,<RBW in Hz>, <limit fail frequency in Hz>, <absolute power indBm>, <relative power in dBc>, <limit distance in dB>, <limitcheck result>, <reserved>, <reserved>...



76User Manual 1178.4230.02 ─ 02

The <limit check result> is either a 0 (for PASS) or a 1 (for FAIL).

5.5.1.17 Return Value Codes

This chapter contains a list for encoded return values.

<allocation ID>

Represents the allocation ID. The value is a number in the range {1...-70}.● 1 = Reference symbol● 0 = Data symbol● -1 = Invalid● -40 = NPUSCH● -41 = NDMRS NPUSCH● -70 = NPRACH

<channel type>

● 0 = TX channel● 1 = adjacent channel● 2 = alternate channel

<modulation>

Represents the modulation scheme. The range is {0...14}.● 0 = unrecognized● 1 = RBPSK● 2 = QPSK● 7 = mixed modulation● 8 = BPSK

<number of symbols or bits>

In hexadecimal mode, this represents the number of symbols to be transmitted. Inbinary mode, it represents the number of bits to be transmitted.

TRACe<n>[:DATA]? <Result>

This command returns the trace data for the current measurement or result display.

For more information see Chapter 5.5.1, "Using the TRACe[:DATA] Command",on page 69.

Suffix: <n>

.Window

Query parameters: <TraceNumber> TRACE1 | TRACE2 | TRACE3

LIST



77User Manual 1178.4230.02 ─ 02

Example: TRAC2? TRACE1Queries results of the second measurement window. The type ofdata that is returned by the parameter (TRACE1) depends on theresult display shown in measurement window 2.

Usage: Query only

5.5.2 Remote Commands to Read Measurement Results

CALCulate<n>:MARKer<m>:FUNCtion:POWer:RESult[:CURRent]?..................................... 77FORMat[:DATA]...............................................................................................................78

CALCulate<n>:MARKer<m>:FUNCtion:POWer:RESult[:CURRent]? <ResultType>

This command queries the current results of the ACLR measurement or the total signalpower level of the SEM measurement.

To get a valid result, you have to perform a complete measurement with synchroniza-tion to the end of the measurement before reading out the result. This is only possiblefor single sweeps.

Suffix: <m>

.Marker

<n> Window

Query parameters: <ResultType> CPOW

This parameter queries the channel power of the referencerange.MCACQueries the channel powers of the ACLR, MC ACLR and Cumu-lative ACLR measurements as shown in the ACLR table.Where available, this parameter also queries the power of theadjacent channels (for example in the ACLR measurement).GACLrQueries the ACLR values for each gap channel in the MC ACLRmeasurement.



78User Manual 1178.4230.02 ─ 02

Return values: <Result> Results for the Spectrum Emission Mask measurement:

Power level in dBm.Results for the ACLR measurements:Relative power levels of the ACLR channels. The number ofreturn values depends on the number of transmission and adja-cent channels. The order of return values is:• <TXChannelPower> is the power of the transmission channelin dBm• <LowerAdjChannelPower> is the relative power of the loweradjacent channel in dB• <UpperAdjChannelPower> is the relative power of the upperadjacent channel in dB• <1stLowerAltChannelPower> is the relative power of the firstlower alternate channel in dB• <1stUpperAltChannelPower> is the relative power of the firstlower alternate channel in dB(...)• <nthLowerAltChannelPower> is the relative power of a subse-quent lower alternate channel in dB• <nthUpperAltChannelPower> is the relative power of a subse-quent lower alternate channel in dB

Example: CALC1:MARK:FUNC:POW:RES? MCACReturns the current ACLR measurement results.

Usage: Query only

Manual operation: See "ACLR" on page 21

FORMat[:DATA] <Format>

This command specifies the data format for the data transmission between the LTEmeasurement application and the remote client. Supported formats are ASCII orREAL32.

Note that the following result displays do not support the REAL32 format. The returnvalues for those are always in ASCII format.● Allocation summary● Bitstream

Parameters:<Format> ASCii | REAL

*RST: ASCii

Example: FORM REALThe software will send binary data in Real32 data format.



79User Manual 1178.4230.02 ─ 02

5.6 Remote Commands to Read Numeric Results

● Frame Results.........................................................................................................79● Result for Selection.................................................................................................81● Marker Table...........................................................................................................85

5.6.1 Frame Results

FETCh[:CC<cc>]:SUMMary:EVM:UNDB[:AVERage]?..........................................................79FETCh[:CC<cc>]:SUMMary:EVM:UNDQ[:AVERage]?......................................................... 79FETCh[:CC<cc>]:SUMMary:EVM:UNSB[:AVERage]?..........................................................80FETCh[:CC<cc>]:SUMMary:EVM:UNSQ[:AVERage]?......................................................... 80FETCh[:CC<cc>]:SUMMary:EVM:UPRA[:AVERage]?..........................................................80

FETCh[:CC<cc>]:SUMMary:EVM:UNDB[:AVERage]?

This command queries the EVM of all NDMRS NPUSCH resource elements with aBPSK modulation.

Suffix: <cc>

.irrelevant

Return values: <EVM> <numeric value>

EVM in % or dB, depending on the unit you have set.

Example: //Query EVMFETC:SUMM:EVM:UNDB?

Usage: Query only

Manual operation: See "Result Summary" on page 17

FETCh[:CC<cc>]:SUMMary:EVM:UNDQ[:AVERage]?

This command queries the EVM of all NDMRS NPUSCH resource elements with aQPSK modulation.

Suffix: <cc>

.irrelevant



Example: //Query EVMFETC:SUMM:EVM:UNDQ?

Usage: Query only


Remote Commands to Read Numeric Results


80User Manual 1178.4230.02 ─ 02

FETCh[:CC<cc>]:SUMMary:EVM:UNSB[:AVERage]?

This command queries the EVM of all NPUSCH resource elements with a BPSK mod-ulation.

Suffix: <cc>

.irrelevant



Example: //Query EVMFETC:SUMM:EVM:UNSB?

Usage: Query only


FETCh[:CC<cc>]:SUMMary:EVM:UNSQ[:AVERage]?

This command queries the EVM of all NPUSCH resource elements with a QPSK mod-ulation.

Suffix: <cc>

.irrelevant



Example: //Query EVMFETC:SUMM:EVM:UNSQ?

Usage: Query only


FETCh[:CC<cc>]:SUMMary:EVM:UPRA[:AVERage]?

This command queries the EVM of all NPRACH resource elements.

Suffix: <cc>

.irrelevant

Return values: <EVM> EVM in % or dB, depending on the unit you have set.

Example: //Query EVMFETC:SUMM:EVM:UPRA?

Usage: Query only




81User Manual 1178.4230.02 ─ 02

5.6.2 Result for Selection

FETCh[:CC<cc>]:SUMMary:CRESt[:AVERage]?.................................................................81FETCh[:CC<cc>]:SUMMary:EVM[:ALL]:MAXimum?............................................................ 82FETCh[:CC<cc>]:SUMMary:EVM[:ALL]:MINimum?............................................................. 82FETCh[:CC<cc>]:SUMMary:EVM[:ALL][:AVERage]?........................................................... 82FETCh[:CC<cc>]:SUMMary:EVM:PCHannel:MAXimum?..................................................... 82FETCh[:CC<cc>]:SUMMary:EVM:PCHannel:MINimum?...................................................... 82FETCh[:CC<cc>]:SUMMary:EVM:PCHannel[:AVERage]?.................................................... 82FETCh[:CC<cc>]:SUMMary:EVM:PSIGnal:MAXimum?........................................................82FETCh[:CC<cc>]:SUMMary:EVM:PSIGnal:MINimum?.........................................................82FETCh[:CC<cc>]:SUMMary:EVM:PSIGnal[:AVERage]?.......................................................82FETCh[:CC<cc>]:SUMMary:FE3G:MAXimum?................................................................... 83FETCh[:CC<cc>]:SUMMary:FE3G:MINimum?.................................................................... 83FETCh[:CC<cc>]:SUMMary:FE3G[:AVERage]?.................................................................. 83FETCh[:CC<cc>]:SUMMary:FERRor:MAXimum?................................................................ 83FETCh[:CC<cc>]:SUMMary:FERRor:MINimum?................................................................. 83FETCh[:CC<cc>]:SUMMary:FERRor[:AVERage]?...............................................................83FETCh[:CC<cc>]:SUMMary:GIMBalance:MAXimum?..........................................................84FETCh[:CC<cc>]:SUMMary:GIMBalance:MINimum?........................................................... 84FETCh[:CC<cc>]:SUMMary:GIMBalance[:AVERage]?.........................................................84FETCh[:CC<cc>]:SUMMary:IQOFfset:MAXimum?...............................................................84FETCh[:CC<cc>]:SUMMary:IQOFfset:MINimum?................................................................84FETCh[:CC<cc>]:SUMMary:IQOFfset[:AVERage]?..............................................................84FETCh[:CC<cc>]:SUMMary:POWer:MAXimum?................................................................. 84FETCh[:CC<cc>]:SUMMary:POWer:MINimum?.................................................................. 84FETCh[:CC<cc>]:SUMMary:POWer[:AVERage]?................................................................ 84FETCh[:CC<cc>]:SUMMary:QUADerror:MAXimum?............................................................85FETCh[:CC<cc>]:SUMMary:QUADerror:MINimum?.............................................................85FETCh[:CC<cc>]:SUMMary:QUADerror[:AVERage]?.......................................................... 85

FETCh[:CC<cc>]:SUMMary:CRESt[:AVERage]?

This command queries the average crest factor as shown in the result summary.

Suffix: <cc>

.irrelevant

Return values: <CrestFactor> <numeric value>

Crest Factor in dB.

Example: //Query crest factorFETC:SUMM:CRES?

Usage: Query only




82User Manual 1178.4230.02 ─ 02

FETCh[:CC<cc>]:SUMMary:EVM[:ALL]:MAXimum?FETCh[:CC<cc>]:SUMMary:EVM[:ALL]:MINimum?FETCh[:CC<cc>]:SUMMary:EVM[:ALL][:AVERage]?This command queries the EVM of all resource elements.

Suffix: <cc>

.irrelevant


Minimum, maximum or average EVM, depending on the lastcommand syntax element.The unit is % or dB, depending on your selection.

Example: //Query EVMFETC:SUMM:EVM?

Usage: Query only


FETCh[:CC<cc>]:SUMMary:EVM:PCHannel:MAXimum?FETCh[:CC<cc>]:SUMMary:EVM:PCHannel:MINimum?FETCh[:CC<cc>]:SUMMary:EVM:PCHannel[:AVERage]?This command queries the EVM of all physical channel resource elements.

Suffix: <cc>

.irrelevant



Example: //Query EVMFETC:SUMM:EVM:PCH?

Usage: Query only


FETCh[:CC<cc>]:SUMMary:EVM:PSIGnal:MAXimum?FETCh[:CC<cc>]:SUMMary:EVM:PSIGnal:MINimum?FETCh[:CC<cc>]:SUMMary:EVM:PSIGnal[:AVERage]?This command queries the EVM of all physical signal resource elements.

Suffix: <cc>

.irrelevant



83User Manual 1178.4230.02 ─ 02


Minimum, maximum or average EVM, depending on the lastcommand syntax element.The unit is % or dB, depending on your selection.

Example: //Query EVMFETC:SUMM:EVM:PSIG?

Usage: Query only


FETCh[:CC<cc>]:SUMMary:FE3G:MAXimum?FETCh[:CC<cc>]:SUMMary:FE3G:MINimum?FETCh[:CC<cc>]:SUMMary:FE3G[:AVERage]?This command queries the frequency error as defined by 3GPP.

Return values: <FreqError> <numeric value>

Minimum, maximum or average frequency error, depending onthe last command syntax element.Default unit: Hz

Example: //Query average frequency errorFETC:SUMM:FE3G?

Usage: Query only


FETCh[:CC<cc>]:SUMMary:FERRor:MAXimum?FETCh[:CC<cc>]:SUMMary:FERRor:MINimum?FETCh[:CC<cc>]:SUMMary:FERRor[:AVERage]?This command queries the frequency error.

Suffix: <cc>

.irrelevant

Return values: <FreqError> <numeric value>

Minimum, maximum or average frequency error, depending onthe last command syntax element.Default unit: Hz

Example: //Query average frequency errorFETC:SUMM:FERR?

Usage: Query only




84User Manual 1178.4230.02 ─ 02

FETCh[:CC<cc>]:SUMMary:GIMBalance:MAXimum?FETCh[:CC<cc>]:SUMMary:GIMBalance:MINimum?FETCh[:CC<cc>]:SUMMary:GIMBalance[:AVERage]?This command queries the I/Q gain imbalance.

Suffix: <cc>

.irrelevant

Return values: <GainImbalance> <numeric value>

Minimum, maximum or average I/Q imbalance, depending onthe last command syntax element.Default unit: dB

Example: //Query average gain imbalanceFETC:SUMM:GIMB?

Usage: Query only


FETCh[:CC<cc>]:SUMMary:IQOFfset:MAXimum?FETCh[:CC<cc>]:SUMMary:IQOFfset:MINimum?FETCh[:CC<cc>]:SUMMary:IQOFfset[:AVERage]?This command queries the I/Q offset.

Suffix: <cc>

.irrelevant

Return values: <IQOffset> <numeric value>

Minimum, maximum or average I/Q offset, depending on the lastcommand syntax element.Default unit: dB

Example: //Query average IQ offsetFETC:SUMM:IQOF?

Usage: Query only


FETCh[:CC<cc>]:SUMMary:POWer:MAXimum?FETCh[:CC<cc>]:SUMMary:POWer:MINimum?FETCh[:CC<cc>]:SUMMary:POWer[:AVERage]?This command queries the total power.

Suffix: <cc>

.irrelevant



85User Manual 1178.4230.02 ─ 02

Return values: <Power> <numeric value>

Minimum, maximum or average power, depending on the lastcommand syntax element.Default unit: dBm

Example: //Query average total powerFETC:SUMM:POW?

Usage: Query only


FETCh[:CC<cc>]:SUMMary:QUADerror:MAXimum?FETCh[:CC<cc>]:SUMMary:QUADerror:MINimum?FETCh[:CC<cc>]:SUMMary:QUADerror[:AVERage]?This command queries the quadrature error.

Suffix: <cc>

.irrelevant

Return values: <QuadError> <numeric value>

Minimum, maximum or average quadrature error, depending onthe last command syntax element.Default unit: deg

Example: //Query average quadrature errorFETC:SUMM:QUAD?

Usage: Query only


5.6.3 Marker Table

CALCulate<n>:DELTamarker<m>:X.................................................................................. 85CALCulate<n>:DELTamarker<m>:Y?.................................................................................86CALCulate<n>:MARKer<m>:X.......................................................................................... 86CALCulate<n>:MARKer<m>:Y?.........................................................................................87

CALCulate<n>:DELTamarker<m>:X <Position>

This command moves a delta marker to a particular coordinate on the x-axis.

If necessary, the command activates the delta marker and positions a referencemarker to the peak power.

Suffix: <m>

.Marker

<n> Window



86User Manual 1178.4230.02 ─ 02

Example: CALC:DELT:X?Outputs the absolute x-value of delta marker 1.

CALCulate<n>:DELTamarker<m>:Y?

This command queries the relative position of a delta marker on the y-axis.

If necessary, the command activates the delta marker first.

To get a valid result, you have to perform a complete measurement with synchroniza-tion to the end of the measurement before reading out the result. This is only possiblefor single measurement mode.

The unit depends on the application of the command.

Suffix: <m>

.Marker

<n> Window

Return values: <Result> Result at the position of the delta marker.

The unit is variable and depends on the one you have currentlyset.

Example: INIT:CONT OFFSwitches to single sweep mode.INIT;*WAIStarts a sweep and waits for its end.CALC:DELT2 ONSwitches on delta marker 2.CALC:DELT2:Y?Outputs measurement value of delta marker 2.

Usage: Query only

CALCulate<n>:MARKer<m>:X <Position>

This command moves a marker to a particular coordinate on the x-axis.

If necessary, the command activates the marker.

If the marker has been used as a delta marker, the command turns it into a normalmarker.

Suffix: <m>

.Marker (query: 1 to 16)

<n> Window

Parameters:<Position> Numeric value that defines the marker position on the x-axis.

Range: The range depends on the current x-axis range.

Example: CALC:MARK2:X 1.7MHzPositions marker 2 to frequency 1.7 MHz.



87User Manual 1178.4230.02 ─ 02

Manual operation: See " Marker Table " on page 20

CALCulate<n>:MARKer<m>:Y?

This command queries the position of a marker on the y-axis.

If necessary, the command activates the marker first.

To get a valid result, you have to perform a complete measurement with synchroniza-tion to the end of the measurement before reading out the result. This is only possiblefor single measurement mode.

Suffix: <n>

.Window

<m> Marker

Return values: <Result> Result at the marker position.

Example: INIT:CONT OFFSwitches to single measurement mode.CALC:MARK2 ONSwitches marker 2.INIT;*WAIStarts a measurement and waits for the end.CALC:MARK2:Y?Outputs the measured value of marker 2.

Usage: Query only

Manual operation: See " Marker Table " on page 20

5.7 Remote Commands to Configure the Application

● General Configuration.............................................................................................87● Configuring I/Q Measurements............................................................................... 88● Configuring Frequency Sweep Measurements.....................................................117

5.7.1 General Configuration

The following remote control command control general configuration of the application.

The remote control commands to select the result displays for I/Q measurements aredescribed in Chapter 5.4, "Configuring the Screen Layout", on page 58.

CONFigure[:LTE]:MEASurement....................................................................................... 88MMEMory:LOAD:IQ:STATe.............................................................................................. 88SYSTem:PRESet:CHANnel[:EXEC]...................................................................................88

Remote Commands to Configure the Application


88User Manual 1178.4230.02 ─ 02

CONFigure[:LTE]:MEASurement <Measurement>

This command selects the measurement.

Parameters:<Measurement> ACLR

Selects the Adjacent Channel Leakage Ratio measurement.ESPectrumSelects the Spectrum Emission Mask measurement.EVMSelects I/Q measurements.

Example: CONF:MEAS ACLRSelects the ACLR measurement.

Manual operation: See "ACLR" on page 21See "Select Measurement" on page 24

MMEMory:LOAD:IQ:STATe <Path>

This command restores I/Q data from a file.

Setting parameters: <Path> String containing the path and name of the source file.

Example: //Load IQ dataMMEM:LOAD:IQ:STAT 'C:\R_S\Instr\user\data.iq.tar'

Usage: Setting only

SYSTem:PRESet:CHANnel[:EXEC]

This command restores the default software settings in the current channel.

Use INST:SEL to select the channel.

Example: INST:SEL 'Spectrum2'Selects the channel for "Spectrum2".SYST:PRES:CHAN:EXECRestores the factory default settings to the "Spectrum2" channel.

Usage: Event

Manual operation: See "Preset Channel" on page 24

5.7.2 Configuring I/Q Measurements

● Signal Characteristics............................................................................................. 89● Signal Capture...................................................................................................... 102● Demodulation........................................................................................................108



89User Manual 1178.4230.02 ─ 02

● Configuring Inputs and Outputs............................................................................ 109● Defining the Frequency.........................................................................................111● Configuring Amplitude Characteristics..................................................................113

5.7.2.1 Signal Characteristics

● Physical Settings.....................................................................................................89● NPUSCH Configuration...........................................................................................91● Global Settings........................................................................................................95● Demodulation Reference Signal............................................................................. 96● Sounding Reference Signal.................................................................................... 99● NPRACH Structure............................................................................................... 100

Physical Settings

CONFigure[:LTE]:LDIRection............................................................................................ 89CONFigure[:LTE]:UL[:CC<cc]:SSPacing.............................................................................89CONFigure[:LTE]:UL[:CC<cc>]:PLC:CID............................................................................ 90CONFigure[:LTE]:UL[:CC<cc>]:PLC:CIDGroup................................................................... 90CONFigure[:LTE]:UL[:CC<cc>]:PLC:PLID.......................................................................... 90[SENSe:][LTE:]SFLatness:OBANd.....................................................................................91[SENSe:][LTE:]UL:DEMod:MODE......................................................................................91

CONFigure[:LTE]:LDIRection <Direction>

This command selects the link direction.

Parameters:<Direction> DL

Selects the mode to analyze downlink signals.ULSelects the mode to analyze uplink signals.

Example: //Select downlink modeCONF:LDIR DL

Manual operation: See "Selecting the LTE mode" on page 25

CONFigure[:LTE]:UL[:CC<cc]:SSPacing <Bandwidth>

This command selects the subcarrier spacing of the signal.

Suffix: <cc>

.Component Carrier

Parameters:<Bandwidth> SS_15

Selects 15 kHz subcarrier bandwidth.SS_3_75Selects a 3.75 kHz subcarrier bandwidth.*RST: SS_15



90User Manual 1178.4230.02 ─ 02

Example: //Select 15 kHz subcarrier spacingCONF:UL:SSP SS_15

Manual operation: See "Subcarrier Spacing" on page 26

CONFigure[:LTE]:UL[:CC<cc>]:PLC:CID <Cell_ID>

This command defines the cell ID.

Suffix: <cc>

.Component Carrier

Parameters:<Cell_ID> AUTO

Automatically determines the cell ID.<numeric value> (integer only)Number of the cell ID.Range: 0 to 503

Example: //Select automatic detection of the cell IDCONF:UL:PLC:CID AUTO

Manual operation: See "Configuring the Physical Layer Cell Identity" on page 26

CONFigure[:LTE]:UL[:CC<cc>]:PLC:CIDGroup <GroupNumber>

This command selects the cell identity group.

Suffix: <cc>

.Component Carrier

Parameters:<GroupNumber> <numeric value> (integer only)

Range: 1 to 167*RST: 0

Example: //Select cell identity group 12CONF:UL:PLCI:CIDG 12


CONFigure[:LTE]:UL[:CC<cc>]:PLC:PLID <Identity>

This command selects the physical layer identity.

Suffix: <cc>

.Component Carrier

Parameters:<Identity> 0 | 1 | 2

Example: //Select physical layer identity 2CONF:DL:PLC:PLID 2



91User Manual 1178.4230.02 ─ 02


[SENSe:][LTE:]SFLatness:OBANd <Subbands>

This command selects the operating band for spectrum flatness measurements.

Parameters:<Subbands> <numeric value> (integer only)


Example: //Select operating band 10SFL:OBAN 10

Manual operation: See "Operating Band Index" on page 26

[SENSe:][LTE:]UL:DEMod:MODE <Reference>

This command selects the uplink analysis mode.

Parameters:<Reference> NPUSch

Analyzes the NPUSCH and NPUCCH.NPRachAnalyzes the NPRACH.*RST: NPUSch

Example: UL:DEM:MODE PRACSelects NPRACH analysis mode.

Manual operation: See "Analysis Mode" on page 25

NPUSCH Configuration

CONFigure:[:LTE]:UL:AUTO:NPUSch:MTYPe.................................................................... 91CONFigure:[:LTE]:UL:AUTO:NPUSch:NSUBcarrier............................................................. 92CONFigure:[:LTE]:UL:AUTO:NPUSch:SSUBcarrier............................................................. 92CONFigure[:LTE]:UL:NONPusch....................................................................................... 93CONFigure[:LTE]:UL:NPUSch<np>:FORMat...................................................................... 93CONFigure[:LTE]:UL:NPUSch<np>:MODulation................................................................. 93CONFigure[:LTE]:UL:NPUSch<np>:MREP......................................................................... 94CONFigure[:LTE]:UL:NPUSch<np>:NORu..........................................................................94CONFigure[:LTE]:UL:NPUSch<np>:NOSubcarrier...............................................................94CONFigure[:LTE]:UL:NPUSch<np>:SSLot..........................................................................95CONFigure[:LTE]:UL:NPUSch<np>:SSUBcarrier.................................................................95

CONFigure:[:LTE]:UL:AUTO:NPUSch:MTYPe <State>

This command turn automatic detection of the modulation type that an NPUSCH useson and off.



92User Manual 1178.4230.02 ─ 02

Parameters:<State> ON

Automatically detects the modulation type of an NPUSCH.OFFYou can define the modulation type manually withCONFigure[:LTE]:UL:NPUSch<np>:MODulation.

*RST: ON

Example: //Detect modulation type of NPUSCHCONF:UL:AUTO:NPUS:MTYP ON

Manual operation: See "Automatic detection of NPUSCH characteristics"on page 27

CONFigure:[:LTE]:UL:AUTO:NPUSch:NSUBcarrier <State>

This command turn automatic detection of the number of subcarriers that an NPUSCHoccupies on and off.


Automatically detects the number of subcarriers occupied by anNPUSCH.OFFYou can define the number of subcarriers manually withCONFigure[:LTE]:UL:NPUSch<np>:NOSubcarrier.

*RST: ON

Example: //Detect number of subcarriers occupied by an NPUSCHCONF:UL:AUTO:NPUS:NSUB ON


CONFigure:[:LTE]:UL:AUTO:NPUSch:SSUBcarrier <State>

This command turn automatic detection of the first subcarrier that an NPUSCH occu-pies on and off.


Automatically detects the start subcarrier of an NPUSCH.OFFYou can define the start subcarrier manually with CONFigure[:LTE]:UL:NPUSch<np>:SSUBcarrier.

*RST: ON

Example: //Detect start subcarrier of NPUSCHCONF:UL:AUTO:NPUS:SSUB ON



93User Manual 1178.4230.02 ─ 02


CONFigure[:LTE]:UL:NONPusch <NPUSCHs>

This command defines the number of NPUSCH channels in the system.

Commands to customize each NPUSCH separately.● NPUSCH format: CONFigure[:LTE]:UL:NPUSch<np>:FORMat● Subcarriers: CONFigure[:LTE]:UL:NPUSch<np>:NOSubcarrier● Start slot: CONFigure[:LTE]:UL:NPUSch<np>:SSLot● Start subcarrier: CONFigure[:LTE]:UL:NPUSch<np>:SSUBcarrier● Resource units: CONFigure[:LTE]:UL:NPUSch<np>:NORu● Repetitions: CONFigure[:LTE]:UL:NPUSch<np>:MREP● Modulation: CONFigure[:LTE]:UL:NPUSch<np>:MODulationParameters:<NPUSCHs> <numeric value> (integer only)


Example: //Select 5 NPUSCHsCONF:UL:NONP 5

CONFigure[:LTE]:UL:NPUSch<np>:FORMat <Format>

This command selects the format of the corresponding NPUSCH.

Suffix: <np>

.NPUSCH

Parameters:<Format> F1 | F2

*RST: F1

Example: //Select format F1 for the second NPUSCHCONF:UL:NPUS2:FORM F1

Manual operation: See "NPUSCH Format" on page 29

CONFigure[:LTE]:UL:NPUSch<np>:MODulation <Modulation>

This command selects the modulation type for the corresponding NPUSCH.

Suffix: <np>

.NPUSCH



94User Manual 1178.4230.02 ─ 02

Parameters:<Modulation> BPSK | QPSK

Note: Availability of modulation types depend on NPUSCH for-mat and number of subcarriers reserved for the NPUSCH.• NPUSCH format 1 with one subcarrier: BPSK and QPSK• NPUSCH format 1 with more than one subcarrier: QPSK• NPUSCH format 2: BPSK*RST: QPSK (F1 is default for any NPUSCH)

Example: //Configure the second NPUSCH for QPSK modulationCONF:UL:NPUS2:MOD QPSK

Manual operation: See "Modulation" on page 30

CONFigure[:LTE]:UL:NPUSch<np>:MREP <Repetitions>

This command defines how often the NPUSCH is transmitted with the same informa-tion.

Suffix: <np>

.NPUSCH

Parameters:<Repetitions> 1 | 2 | 4 | 8 | 16 | 32 | 64 | 128

*RST: 1

Example: //Configure the second NPUSCH to be repeated 16 timesCONF:UL:NPUS2:MREP 16

Manual operation: See "Repetitions" on page 30

CONFigure[:LTE]:UL:NPUSch<np>:NORu <ResourceUnits>

This command defines the number of resource units the NPUSCH is mapped to.

Suffix: <np>

.NPUSCH

Parameters:<ResourceUnits> 1 | 2 | 3 | 4 | 5 | 6 | 8 | 10

*RST: 1

Example: //Map the second NPUSCH to 5 resource unitsCONF:UL:NPUS2:NOR 5

Manual operation: See "Resource Units" on page 30

CONFigure[:LTE]:UL:NPUSch<np>:NOSubcarrier <Subcarrier>

This command defines the number of subcarriers used by the correspondingNPUSCH.



95User Manual 1178.4230.02 ─ 02

Suffix: <np>

.NPUSCH

Parameters:<Subcarrier> 1 | 3 | 6 | 12

Note: Values other than "1" are only availble for a subcarrierspacing of 15 kHz and NPUSCHs configured as format 1.*RST: 1

Example: //Assign 4 subcarriers to the second NPUSCH.CONF:UL:NPUS2:NOS 4

Manual operation: See "Number of Subcarriers" on page 29

CONFigure[:LTE]:UL:NPUSch<np>:SSLot <Slot>

This command defines the start slot of the corresponding NPUSCH.

Suffix: <np>

.NPUSCH

Parameters:<Slot> <numeric value> (integer only)


Example: //Configure the second NPUSCH to start on slot number 10.CONF:UL:NPUS2:SSL 10

Manual operation: See "Start Slot" on page 29

CONFigure[:LTE]:UL:NPUSch<np>:SSUBcarrier <Subcarrier>

This command defines the start subcarrier for the corresponding NPUSCH.

Suffix: <np>

.NPUSCH

Parameters:<Subcarrier> <numeric value> (integer only)


Example: //Configure the second NPUSCH to start on subcarrier number10.CONF:UL:NPUS2:SSUB 10

Manual operation: See "Starting Subcarrier" on page 29

Global Settings

CONFigure[:LTE]:UL[:CC<cc>]:UEID................................................................................. 96



96User Manual 1178.4230.02 ─ 02

CONFigure[:LTE]:UL[:CC<cc>]:UEID <ID>

This command defines the radio network temporary identifier (RNTI) of the UE.

Suffix: <cc>

.Component Carrier

Parameters:<ID> <numeric value> (integer only)


Example: //Define a RNTI of 2CONF:UL:UEID 2

Manual operation: See "UE ID/n_RNTI" on page 31

Demodulation Reference Signal

CONFigure[:LTE]:UL[:CC<cc>]:DRS:BSOurce.................................................................... 96CONFigure[:LTE]:UL[:CC<cc>]:DRS:BSIX..........................................................................96CONFigure[:LTE]:UL[:CC<cc>]:DRS:BTHRee.....................................................................97CONFigure[:LTE]:UL[:CC<cc>]:DRS:BSTWelve..................................................................97CONFigure[:LTE]:UL[:CC<cc>]:DRS:CSSix........................................................................ 98CONFigure[:LTE]:UL[:CC<cc>]:DRS:CSTHree....................................................................98CONFigure[:LTE]:UL[:CC<cc>]:DRS:DSSHift......................................................................99CONFigure[:LTE]:UL[:CC<cc>]:DRS:GRPHopping.............................................................. 99

CONFigure[:LTE]:UL[:CC<cc>]:DRS:BSOurce <Source>

This command selects the source of the demodulation reference signal.

Suffix: <cc>

.Component Carrier

Parameters:<Source> HLAYer

Source of the NDMRS is a higher layer.IDCellSource of the NDMRS is the cell ID.*RST: IDCell

Example: //Select the higher layer as the source of the NDMRSCONF:UL:DRS:BSO HLAY

Manual operation: See "Base Sequence Source" on page 32

CONFigure[:LTE]:UL[:CC<cc>]:DRS:BSIX <BaseSequence>

This command defines the base sequence for the demodulation reference signal incase it is based on a six tone.



97User Manual 1178.4230.02 ─ 02

Prerequisites for this command● Group hopping is off, see CONFigure[:LTE]:UL[:CC<cc>]:DRS:GRPHopping● Source of the reference signal is a higher layer, see CONFigure[:LTE]:UL[:

CC<cc>]:DRS:BSOurce.

Suffix: <cc>

.Component Carrier

Parameters:<BaseSequence> Range: 0 to 13

*RST: 0

Example: //Select base sequenceCONF:UL:DRS:BSIX 4

Manual operation: See "Base Sequence" on page 32

CONFigure[:LTE]:UL[:CC<cc>]:DRS:BTHRee <BaseSequence>

This command defines the base sequence for the demodulation reference signal incase it is based on a three tone.



Suffix: <cc>

.Component Carrier


*RST: 0

Example: //Select base sequenceCONF:UL:DRS:BTHR 4


CONFigure[:LTE]:UL[:CC<cc>]:DRS:BSTWelve <BaseSequence>

This command defines the base sequence for the demodulation reference signal incase it is based on a twelve tone.



Suffix: <cc>

.Component Carrier



98User Manual 1178.4230.02 ─ 02


*RST: 0

Example: //Select base sequenceCONF:UL:DRS:BSTW 4


CONFigure[:LTE]:UL[:CC<cc>]:DRS:CSSix <CyclicShift>

This command defines the cyclic shift for the demodulation reference signal in case itis based on a six tone.



Suffix: <cc>

.Component Carrier

Parameters:<CyclicShift> 0 | 1 | 2 | 3

*RST: 0

Example: //Select six tone cyclic shift 2CONF:UL:DRS:CSS 2

Manual operation: See "Cyclic Shift" on page 32

CONFigure[:LTE]:UL[:CC<cc>]:DRS:CSTHree <CyclicShift>

This command defines the cyclic shift for the demodulation reference signal in case itis based on a three tone.

Prerequisites for this command● Group hopping is off, see CONFigure[:LTE]:UL[:CC<cc>]:DRS:GRPHopping

.● Source of the reference signal is a higher layer, see CONFigure[:LTE]:UL[:


Suffix: <cc>

.Component Carrier

Parameters:<CyclicShift> 0 | 1 | 2

*RST: 0

Example: //Select three tone cyclic shift 2CONF:UL:DRS:CSTH

Manual operation: See "Cyclic Shift" on page 32



99User Manual 1178.4230.02 ─ 02

CONFigure[:LTE]:UL[:CC<cc>]:DRS:DSSHift <Shift>

This command selects the delta sequence shift of the uplink signal.

Prerequisites for this command● Turn on group hopping (CONFigure[:LTE]:UL[:CC<cc>]:DRS:GRPHopping

on page 99).

Suffix: <cc>

.Component Carrier

Parameters:<Shift> <numeric value> (integer only)

*RST: 0

Example: //Select delta sequence shiftCONF:UL:DRS:DSSH 3

Manual operation: See " Delta Sequence Shift" on page 33

CONFigure[:LTE]:UL[:CC<cc>]:DRS:GRPHopping <State>

This command turns group hopping for uplink signals on and off.

Suffix: <cc>

.Component Carrier

Parameters:<State> ON | OFF | 1 | 0

*RST: OFF

Example: //Turn on group hoppingCONF:UL:DRS:GRPH ON

Manual operation: See " Group Hopping" on page 33

Sounding Reference Signal

CONFigure[:LTE]:UL[:CC<cc>]:SRS:STAT......................................................................... 99CONFigure[:LTE]:UL[:CC<cc>]:SRS:SUConfig................................................................. 100

CONFigure[:LTE]:UL[:CC<cc>]:SRS:STAT <State>

Turns the sounding reference signal on and off.

Suffix: <cc>

.Component Carrier


*RST: OFF

Example: //Turn on the sounding reference signalCONF:UL:SRS:STAT ON



100User Manual 1178.4230.02 ─ 02

Manual operation: See " Present" on page 34

CONFigure[:LTE]:UL[:CC<cc>]:SRS:SUConfig <Configuration>

This command defines the SRS subframe configuration.

Prerequisites for this command● Turn on the sounding reference signal with CONFigure[:LTE]:UL[:CC<cc>]:

SRS:STAT.

Suffix: <cc>

.Component Carrier

Parameters:<Configuration> <numeric value> (integer only)


Example: //Select SRS subframe configuration 4CONF:UL:SRS:SUC 4

Manual operation: See " SRS Subframe Configuration" on page 34

NPRACH Structure

CONFigure[:LTE]:UL[:CC<cc>]:NPRach:FORMat..............................................................100CONFigure[:LTE]:UL[:CC<cc>]:NPRach:NIMode...............................................................100CONFigure[:LTE]:UL[:CC<cc>]:NPRach:NINit...................................................................101CONFigure[:LTE]:UL[:CC<cc>]:NPRach:NOSC.................................................................101CONFigure[:LTE]:UL[:CC<cc>]:NPRach:NREP.................................................................102CONFigure[:LTE]:UL[:CC<cc>]:NPRach:NSCoffset........................................................... 102

CONFigure[:LTE]:UL[:CC<cc>]:NPRach:FORMat <Format>

This command selects the NPRACH format.

Suffix: <cc>

.Component Carrier

Parameters:<Format> F0 | F1

*RST: F1

Example: //Select NPRACH format F1CONF:UL:NPR:FORM F1

Manual operation: See "NPRACH Format" on page 35

CONFigure[:LTE]:UL[:CC<cc>]:NPRach:NIMode <Mode>

This command selects the way that the NInit is determined (location of the NPRACH).



101User Manual 1178.4230.02 ─ 02

Suffix: <cc>

.Component Carrier

Parameters:<Mode> AUTO

Automatically determines the NInit.

MANualYou can define the NInit manually with CONFigure[:LTE]:UL[:CC<cc>]:NPRach:NINit.

*RST: AUTO

Example: //Select mode to determine N_initCONF:UL:NPR:NIM AUTO

Manual operation: See "N_init" on page 36

CONFigure[:LTE]:UL[:CC<cc>]:NPRach:NINit <Value>

This command defines the NInit value.

Prerequisites for this command● Select manual NInit mode (CONFigure[:LTE]:UL[:CC<cc>]:NPRach:NIMode).

Suffix: <cc>

.Component Carrier

Parameters:<Value> <numeric value> (integer only)


Example: //Select n_initCONF:UL:NPR:NIM MANCONF:UL:NPR:NIN 10

Manual operation: See "N_init" on page 36

CONFigure[:LTE]:UL[:CC<cc>]:NPRach:NOSC <Subcarriers>

This command defines the number of subcarriers allocated to the NPRACH.

Suffix: <cc>

.Component Carrier

Parameters:<Subcarriers> 12 | 24 | 36 | 48

*RST: 12

Example: //Allocate 24 subcarriers to the NPRACHCONF:UL:NPR:NOSC 24

Manual operation: See "Subcarrier Configuration" on page 35



102User Manual 1178.4230.02 ─ 02

CONFigure[:LTE]:UL[:CC<cc>]:NPRach:NREP <Repetitions>

This command defines how often identical NPRACH information is transmitted.

Suffix: <cc>

.Component Carrier

Parameters:<Repetitions> 1 | 2 | 4 | 8 | 16 | 32 | 64 | 128

*RST: 0

Example: //Transmit the NPRACH information 16 timesCONF:UL:NPR:NREP 16

Manual operation: See "Number of Repetitions" on page 35

CONFigure[:LTE]:UL[:CC<cc>]:NPRach:NSCoffset <Offset>

This command defines the first subcarrier allocated to the NPRACH.

Suffix: <cc>

.Component Carrier

Parameters:<Offset> 0 | 2 | 12 | 18 | 24 | 34 | 36

*RST: 0

Example: //Select an offset of 2CONF:UL:NPR:NSC 2

Manual operation: See "Subcarrier Configuration" on page 35

5.7.2.2 Signal Capture

● Data Capture.........................................................................................................102● Trigger...................................................................................................................104

Data Capture

[SENSe:][LTE:]SLOT:COUNt.......................................................................................... 102[SENSe:][LTE:]SLOT:COUNt:STATe................................................................................103[SENSe:][LTE:]SLOT:COUNt:AUTO.................................................................................103[SENSe:]SWAPiq...........................................................................................................103[SENSe:]SWEep:TIME................................................................................................... 104

[SENSe:][LTE:]SLOT:COUNt <Slots>

This command defines the number of slots you want to analyze.

Prerequisites for this command● Turn off automatics evaluation of slots ([SENSe:][LTE:]SLOT:COUNt:AUTO).



103User Manual 1178.4230.02 ─ 02

Parameters:<Slots> <numeric value> (integer only)

*RST: 1

Example: //Analyze 4 slotsSLOT:COUN:AUTO OFFSLOT:COUN 4

Manual operation: See "Number of Slots to Analyze" on page 43

[SENSe:][LTE:]SLOT:COUNt:STATe <State>

This command turns manual selection of the number of frames you want to analyze onand off.


Define the number of slots to analyze manually.OFFThe R&S VSE analyzes the slots contained in a single sweep.*RST: ON

Example: //Analyze all captured slotsSLOT:COUN:STAT OFF

Manual operation: See "Overall Slot Count" on page 43

[SENSe:][LTE:]SLOT:COUNt:AUTO <State>

This command turns automatic selection of the number of slots to analyze on and off.


Selects the number of slots to analyze according to the NB-IoTstandard.OFFTurns manual selection of the slots number on.In case of manual selection, you can select the number of slotswith [SENSe:][LTE:]SLOT:COUNt*RST: ON

Example: //Analyze slots according to standardSLOT:COUN:AUTO ON

Manual operation: See "Auto According to Standard" on page 43

[SENSe:]SWAPiq <State>

This command turns a swap of the I and Q branches on and off.



104User Manual 1178.4230.02 ─ 02


*RST: OFF

Example: //Swap I and Q branchesSWAP ON

Manual operation: See "Swap I/Q" on page 43

[SENSe:]SWEep:TIME <CaptLength>

This command defines the capture time.

Parameters:<CaptLength> <numeric value>

*RST: 40.1 msDefault unit: s

Example: //Define capture timeSWE:TIME 40ms

Manual operation: See "Capture Time" on page 42

Trigger

The trigger functionality of the LTE measurement application is the same as that of theR&S VSE.

For a comprehensive description of the available remote control commands for triggerconfiguration, see the documentation of the R&S VSE.

TRIGger[:SEQuence]:HOLDoff<instrument>..................................................................... 104TRIGger[:SEQuence]:LEVel<instrument>[:EXTernal].........................................................105TRIGger[:SEQuence]:LEVel:MAPower.............................................................................105TRIGger[:SEQuence]:MAPower:HOLDoff......................................................................... 105TRIGger[:SEQuence]:MAPower:HYSTeresis.................................................................... 105TRIGger[:SEQuence]:PORT<instrument>.........................................................................106TRIGger[:SEQuence]:POSition........................................................................................106TRIGger[:SEQuence]:SLOPe.......................................................................................... 107TRIGger[:SEQuence]:SOURce........................................................................................107

TRIGger[:SEQuence]:HOLDoff<instrument> <Offset>

This command defines the trigger offset.

Parameters:<Offset> <numeric value>

*RST: 0 sDefault unit: s

Example: //Define trigger offsetTRIG:HOLD 5MS



105User Manual 1178.4230.02 ─ 02

TRIGger[:SEQuence]:LEVel<instrument>[:EXTernal] <Level>

This command defines the level for an external trigger.

Parameters:<Level> Range: 0.5 V to 3.5 V

*RST: 1.4 VDefault unit: V

Example: //Define trigger levelTRIG:LEV 2V

TRIGger[:SEQuence]:LEVel:MAPower <TriggerLevel>

This command defines the power level that must be exceeded to cause a trigger eventfor (offline) input from a file.

Parameters:<TriggerLevel> For details on available trigger levels and trigger bandwidths see

the data sheet.

Example: TRIG:LEV:MAP -30DBM

TRIGger[:SEQuence]:MAPower:HOLDoff <Period>

This command defines the holding time before the next trigger event for (offline) inputfrom a file.

Parameters:<Period> Range: 0 s to 10 s

*RST: 0 s

Example: TRIG:SOUR MAGNSets an offline magnitude trigger source.TRIG:MAP:HOLD 200 nsSets the holding time to 200 ns.

TRIGger[:SEQuence]:MAPower:HYSTeresis <Hysteresis>

This command defines the trigger hysteresis for the (offline) magnitude trigger source(used for input from a file).

Parameters:<Hysteresis> Range: 3 dB to 50 dB

*RST: 3 dB

Example: TRIG:SOUR MAPSets the (offline) magnitude trigger source.TRIG:MAP:HYST 10DBSets the hysteresis limit value.



106User Manual 1178.4230.02 ─ 02

TRIGger[:SEQuence]:PORT<instrument> <Port>

This command selects the trigger port for measurements with devices that have sev-eral trigger ports.

Parameters:<Port> PORT1

PORT2PORT3

Example: //Select trigger port 1TRIG:PORT PORT1

TRIGger[:SEQuence]:POSition <Position>

This command selects the position in an NB-IoT signal where the trigger conditionmust be met.

Parameters:<Position> FRAMe

The trigger is sent at the start of frame 0.FNPuschThe trigger is sent at the start of the frame in which the firstNPUSCH is found.NPRachThe trigger is sent at the start of the first NPRACH.NPUSchThe trigger is sent at the start of the first NPUSCH.UNKNownThe measurement starts when the first NPUSCH has beenfound.Prerequisites for this parameter:• Data source is an I/Q file.• Trigger source is "Free Run" (this is always the case when youanalyze an I/Q file).*RST: FRAMe

Example: //Select triggering on the first occurence of the NPUSCHTRIG:POS NPUS

Manual operation: See "Configuring the Trigger" on page 41



107User Manual 1178.4230.02 ─ 02

TRIGger[:SEQuence]:SLOPe <Type>

Parameters:<Type> POSitive | NEGative

POSitiveTriggers when the signal rises to the trigger level (rising edge).NEGativeTriggers when the signal drops to the trigger level (falling edge).*RST: POSitive

Example: TRIG:SLOP NEG

TRIGger[:SEQuence]:SOURce <Source>

This command selects the trigger source.

Note that the availability of trigger sources depends on the connected instrument.

Note on external triggers:

If a measurement is configured to wait for an external trigger signal in a remote controlprogram, remote control is blocked until the trigger is received and the program cancontinue. Make sure this situation is avoided in your remote control programs.



108User Manual 1178.4230.02 ─ 02

Parameters:<Source> IMMediate

Free RunEXTernalTrigger signal from the TRIGGER INPUT connector.EXT | EXT2 | EXT3 | EXT4Trigger signal from the corresponding TRIGGER INPUT/OUTPUT connector on the connected instrument, or the oscillo-scope's corresponding input channel.For details on the connectors see the instrument's Getting Star-ted manual.RFPowerFirst intermediate frequencyIFPowerSecond intermediate frequencyIQPowerMagnitude of sampled I/Q dataFor applications that process I/Q data, such as the I/Q Analyzeror optional applications.TIMETime intervalMAGNitudeFor (offline) input from a file, rather than an instrument.The trigger level is specified by TRIGger[:SEQuence]:LEVel:MAPower.

*RST: IMMediate

Example: TRIG:SOUR EXTSelects the external trigger input as source of the trigger signal

5.7.2.3 Demodulation

[SENSe:][LTE:]UL:DEMod:CBSCrambling........................................................................ 108[SENSe:][LTE:]UL:DEMod:CESTimation.......................................................................... 109[SENSe:][LTE:]UL:DEMod:CDCoffset...............................................................................109

[SENSe:][LTE:]UL:DEMod:CBSCrambling <State>

This command turns scrambling of coded bits on and off.


*RST: ON

Example: //Turn off descrambling of coded bitsUL:DEM:CBSC OFF

Manual operation: See "Scrambling of Coded Bits" on page 44



109User Manual 1178.4230.02 ─ 02

[SENSe:][LTE:]UL:DEMod:CESTimation <Type>

This command selects the channel estimation type.

Parameters:<Type> PIL

Pilot onlyPILPPilot and payload*RST: PILP

Example: //Use the pilot signal for channel estimationUL:DEM:CEST PIL

Manual operation: See "Channel Estimation Range" on page 44

[SENSe:][LTE:]UL:DEMod:CDCoffset <State>

This command turns DC offset compensation on and off.


*RST: ON

Example: //Turn off DC offset compensationUL:DEM:CDC OFF

Manual operation: See "Compensate DC Offset" on page 44

5.7.2.4 Configuring Inputs and Outputs

Useful commands to perform measurements described elsewhere:● INPut:COUPling on page 114● INPut:IMPedance on page 115

INPut:FILTer:HPASs[:STATe]..........................................................................................109INPut:FILTer:YIG[:STATe].............................................................................................. 110INPut:SELect.................................................................................................................110INSTrument:BLOCk:CHANnel[:SETTings]:SOURce.......................................................... 110

INPut:FILTer:HPASs[:STATe] <State>

Activates an additional internal high-pass filter for RF input signals from 1 GHz to3 GHz. This filter is used to remove the harmonics of the connected instrument in orderto measure the harmonics for a DUT, for example.

This function requires an additional high-pass filter hardware option.

(Note: for RF input signals outside the specified range, the high-pass filter has noeffect. For signals with a frequency of approximately 4 GHz upwards, the harmonicsare suppressed sufficiently by the YIG-preselector, if available.)



110User Manual 1178.4230.02 ─ 02


*RST: 0

Example: INP:FILT:HPAS ONTurns on the filter.

Manual operation: See " High Pass Filter 1 to 3 GHz " on page 36

INPut:FILTer:YIG[:STATe] <State>

This command turns the YIG-preselector on and off.

Note the special conditions and restrictions for the YIG-preselector described in " YIG-Preselector " on page 37.

Example: INP:FILT:YIG OFFDeactivates the YIG-preselector.

Manual operation: See " YIG-Preselector " on page 37

INPut:SELect <Source>

This command selects the signal source for measurements, i.e. it defines which con-nector is used to input data to the R&S VSE.

Parameters:<Source> RF

Radio Frequency ("RF INPUT" connector)FIQI/Q data file*RST: RF

Manual operation: See "Input Type" on page 38

INSTrument:BLOCk:CHANnel[:SETTings]:SOURce <Type>

Selects an instrument or a file as the source of input provided to the channel.

Parameters:<Type> FILE | DEVice | NONE

FILEA loaded file is used for input.DEViceA configured device provides input for the measurementNONENo input source defined.

Manual operation: See "Input Type" on page 38



111User Manual 1178.4230.02 ─ 02

5.7.2.5 Defining the Frequency

[SENSe:]FREQuency:CENTer[:CC<cc>].......................................................................... 111[SENSe]:FREQuency:CENTer[:CC<cc>]:OFFSet.............................................................. 111[SENSe:]FREQuency:CENTer:STEP............................................................................... 112[SENSe:]FREQuency:CENTer:STEP:LINK....................................................................... 112[SENSe:]FREQuency:CENTer:STEP:LINK:FACTor........................................................... 113

[SENSe:]FREQuency:CENTer[:CC<cc>] <Frequency>

This command sets the center frequency for RF measurements.

Note that the [:CC<cci>] part of the syntax is not supported.

Suffix: <cc>

.irrelevant

Parameters:<Frequency> <numeric value>

Range: fmin to fmax*RST: 1 GHzDefault unit: Hz

Example: //Define frequency for measurement on one carrier:FREQ:CENT 1GHZ

Example: //Define frequency for measurement on aggregated carriers:FREQ:CENT:CC1 850MHZ

Manual operation: See "Defining the Signal Frequency" on page 38

[SENSe]:FREQuency:CENTer[:CC<cc>]:OFFSet <Frequency>

This command defines the general frequency offset or the frequency offset for a com-ponent carrier.

The effect of the command depends on the syntax:● When you omit the [CC<cci>] syntax element, the command defines the overall

frequency offset.In that case, the value is added to the measurement frequency and, in case ofmeasurements with component carriers, the center frequency of the componentcarriers.

● When you include the [CC<cci>] syntax element, the command defines the offsetof the component carrier relative the first component carrier.In that case, the command is not available for the first component carrier -thus, ...:CC1:... is not possible.

Suffix: <cc>

.irrelevant



112User Manual 1178.4230.02 ─ 02

Parameters:<Frequency> • General frequency offset: frequency offset in Hz.

• Component carrier offset: frequency offset relative to the firstcomponent carrier in Hz.

Example: //Add a frequency offset of 50 Hz to the measurement fre-quency.//If you are measuring component carriers, the value is alsoadded to the center frequencies of those carriers.FREQ:CENT:OFFS 50HZ//Define a frequency offset of 15 MHz for the second componentcarrier relative to the first component carrier.FREQ:CENT:CC2:OFFS 15MHZ


[SENSe:]FREQuency:CENTer:STEP <StepSize>

This command defines the center frequency step size.

You can increase or decrease the center frequency quickly in fixed steps using theSENS:FREQ UP and SENS:FREQ DOWN commands, see [SENSe:]FREQuency:CENTer[:CC<cc>] on page 111.

Parameters:<StepSize> fmax is specified in the data sheet.

Range: 1 to fMAX*RST: 0.1 x spanDefault unit: Hz

Example: //Set the center frequency to 110 MHz.FREQ:CENT 100 MHzFREQ:CENT:STEP 10 MHzFREQ:CENT UP


[SENSe:]FREQuency:CENTer:STEP:LINK <CouplingType>

This command couples and decouples the center frequency step size to the span orthe resolution bandwidth.

Parameters:<CouplingType> SPAN

Couples the step size to the span. Available for measurementsin the frequency domain.OFFDecouples the step size.*RST: SPAN

Example: //Couple step size to spanFREQ:CENT:STEP:LINK SPAN



113User Manual 1178.4230.02 ─ 02

[SENSe:]FREQuency:CENTer:STEP:LINK:FACTor <Factor>

This command defines a step size factor if the center frequency step size is coupled tothe span or the resolution bandwidth.

Parameters:<Factor> 1 to 100 PCT

*RST: 10

Example: //Couple frequency step size to span and define a step size fac-torFREQ:CENT:STEP:LINK SPANFREQ:CENT:STEP:LINK:FACT 20PCT

5.7.2.6 Configuring Amplitude Characteristics

The commands are available when you capture data with an instrument. In addition,the commands that are available depend on the configuration of the connected instru-ment.

DISPlay[:WINDow<n>]:TRACe<t>:Y[:SCALe]:RLEVel....................................................... 113DISPlay[:WINDow<n>]:TRACe<t>:Y[:SCALe]:RLEVel:OFFSet........................................... 114INPut:ATTenuation.........................................................................................................114INPut:ATTenuation:AUTO...............................................................................................114INPut:COUPling.............................................................................................................114INPut:GAIN[:VALue].......................................................................................................115INPut:GAIN:STATe........................................................................................................ 115INPut:IMPedance...........................................................................................................115INPut<n>:EATT............................................................................................................. 116INPut<n>:EATT:AUTO................................................................................................... 116INPut<n>:EATT:STATe.................................................................................................. 116[SENSe:]ADJust:LEVel...................................................................................................117

DISPlay[:WINDow<n>]:TRACe<t>:Y[:SCALe]:RLEVel <ReferenceLevel>

This command defines the reference level (for all traces in all windows).

With a reference level offset ≠ 0, the value range of the reference level is modified bythe offset.

Suffix: <n>, <t>

.irrelevant

Parameters:<ReferenceLevel> The unit is variable.

Range: see datasheet*RST: 0 dBm

Example: DISP:TRAC:Y:RLEV -60dBmManual operation: See "Defining a Reference Level" on page 39



114User Manual 1178.4230.02 ─ 02

DISPlay[:WINDow<n>]:TRACe<t>:Y[:SCALe]:RLEVel:OFFSet <Offset>

This command defines a reference level offset (for all traces in all windows).

Suffix: <n>, <t>

.irrelevant

Parameters:<Offset> Range: -200 dB to 200 dB

*RST: 0dB

Example: DISP:TRAC:Y:RLEV:OFFS -10dBManual operation: See "Defining a Reference Level" on page 39

INPut:ATTenuation <Attenuation>

This command defines the total attenuation for RF input.

If you set the attenuation manually, it is no longer coupled to the reference level, butthe reference level is coupled to the attenuation. Thus, if the current reference level isnot compatible with an attenuation that has been set manually, the command alsoadjusts the reference level.

Parameters:<Attenuation> Range: see data sheet

Increment: 5 dB*RST: 10 dB (AUTO is set to ON)

Example: INP:ATT 30dBDefines a 30 dB attenuation and decouples the attenuation fromthe reference level.

Manual operation: See "Attenuating the Signal" on page 40

INPut:ATTenuation:AUTO <State>

This command couples or decouples the attenuation to the reference level. Thus, whenthe reference level is changed, the R&S VSE determines the signal level for optimalinternal data processing and sets the required attenuation accordingly.


*RST: 1

Example: INP:ATT:AUTO ONCouples the attenuation to the reference level.

INPut:COUPling <CouplingType>

This command selects the coupling type of the RF input.



115User Manual 1178.4230.02 ─ 02

Parameters:<CouplingType> AC

AC couplingDCDC coupling*RST: AC

Example: INP:COUP DCManual operation: See " Input Coupling " on page 40

INPut:GAIN[:VALue] <Gain>

This command selects the gain if the preamplifier is activated (INP:GAIN:STAT ON,see INPut:GAIN:STATe on page 115).

The command requires the additional preamplifier hardware option.

Parameters:<Gain> 15 dB | 30 dB

The availability of gain levels depends on the model of the con-nected instrument.*RST: OFF

Example: INP:GAIN:STAT ONINP:GAIN:VAL 30Switches on 30 dB preamplification.

INPut:GAIN:STATe <State>

This command turns the preamplifier on the connected instrument on and off. Itrequires the additional preamplifier hardware option on the connected instrument.


*RST: 0

Example: INP:GAIN:STAT ONSwitches on 30 dB preamplification.

INPut:IMPedance <Impedance>

This command selects the nominal input impedance of the RF input. In some applica-tions, only 50 Ω are supported.

Parameters:<Impedance> 50 | 75

*RST: 50 Ω

Example: INP:IMP 75Manual operation: See " Impedance " on page 40



116User Manual 1178.4230.02 ─ 02

INPut<n>:EATT <Attenuation>

This command defines the electronic attenuation level.

If the current reference level is not compatible with an attenuation that has been setmanually, the command also adjusts the reference level.

Suffix: <n>

.Window

Parameters:<Attenuation> Attenuation level in dB.

Default unit: dB

Example: INP:EATT 10Defines an attenuation level of 10 dB.


INPut<n>:EATT:AUTO <State>

This command turns automatic selection of the electronic attenuation on and off.

If on, electronic attenuation reduces the mechanical attenuation whenever possible.

Suffix: <n>

.Window

Parameters:<State> ON | OFF

*RST: OFF

Example: INP:EATT:AUTO ONTurns automatic selection of electronic attenuation level on.


INPut<n>:EATT:STATe <State>

This command turns the electronic attenuator on and off.

Suffix: <n>

.Window


*RST: OFF

Example: INP:EATT:STAT ONTurns on the electronic attenuator.




117User Manual 1178.4230.02 ─ 02

[SENSe:]ADJust:LEVel

This command initiates a single (internal) measurement that evaluates and sets theideal reference level for the current input data and measurement settings. This ensuresthat the settings of the RF attenuation and the reference level are optimally adjusted tothe signal level without overloading the R&S VSE or limiting the dynamic range by anS/N ratio that is too small.

Example: ADJ:LEVUsage: Event

Manual operation: See "Defining a Reference Level" on page 39

5.7.3 Configuring Frequency Sweep Measurements

The remote commands to configure the ACLR and SEM measurements are the sameas in the spectrum application.

For a comprehensive description, see the R&S VSE user manual.

In addition, the SEM measurement in the NB-IoT application has several exclusive set-tings not available in the spectrum application.

Commands to configure exclusive ACLR settings described elsewhere.● NB-IoT mode: CONFigure[:LTE]:LDIRection on page 89● Analysis mode: [SENSe:][LTE:]UL:DEMod:MODE on page 91● Subcarrier spacing: CONFigure[:LTE]:UL[:CC<cc]:SSPacing on page 89

Commands to configure exclusive SEM settings described elsewhere.● NB-IoT mode: CONFigure[:LTE]:LDIRection on page 89● SEM measurements are only possible in PUSCH/PUCCH analysis mode.

[SENSe:]POWer:ACHannel:AACHannel...........................................................................117

[SENSe:]POWer:ACHannel:AACHannel <Channel>

This command selects the bandwidth of the adjacent channel for ACLR measure-ments.

Parameters:<Channel> N1GSm

Selects a GSM signal as assumed adjacent channel carrier.N1UTraSelects an UTRA signal as assumed adjacent channel carrier.*RST: EUTRA

Example: //Select assumed adjacent channelPOW:ACH:AACH N1GS



118User Manual 1178.4230.02 ─ 02

5.8 Analysis

● Evaluation Range..................................................................................................118● Y-Axis Scale..........................................................................................................120● Result Settings......................................................................................................122● Marker...................................................................................................................123

5.8.1 Evaluation Range

[SENSe:][LTE:][CC<cc>:]ALLocation:SELect.................................................................... 118[SENSe:][LTE:][CC<cc>:]CARRier:SELect........................................................................118[SENSe:][LTE:][CC<cc>:]MODulation:SELect................................................................... 119[SENSe:][LTE:][CC<cc>:]NPUSch:SELect........................................................................ 119[SENSe:][LTE:][CC<cc>:]SLOT:SELect............................................................................ 120[SENSe:][LTE:][CC<cc>:]SYMBol:SELect.........................................................................120

[SENSe:][LTE:][CC<cc>:]ALLocation:SELect <Allocation>

This command filters the displayed results in the constellation diagram by a particulartype of allocation.

Suffix: <cc>

.Component Carrier

Parameters:<Allocation> ALL

Shows the results for all allocations.<numeric_value>Shows the results for a single allocation type.Allocation types are mapped to numeric values. For the codeassignment, see Chapter 5.5.1.17, "Return Value Codes",on page 76.*RST: ALL

Example: //Display results for allocation 2ALL:SEL 2

Manual operation: See "Evaluation range for the constellation diagram" on page 48

[SENSe:][LTE:][CC<cc>:]CARRier:SELect <Carrier>

This command filters the displayed results in the constellation diagram by a particularsubcarrier.

Suffix: <cc>

.Component Carrier

Analysis


119User Manual 1178.4230.02 ─ 02

Parameters:<Carrier> ALL

Shows the results for all subcarriers.<numeric_value>Shows the results for a single subcarrier.*RST: ALL

Example: //Display results for subcarrier 1CARR:SEL 1


[SENSe:][LTE:][CC<cc>:]MODulation:SELect <Modulation>

This command filters the displayed results in the constellation diagram by a particulartype of modulation.

Suffix: <cc>

.Component Carrier

Parameters:<Modulation> ALL

Shows the results for all modulation types.<numeric_value>Shows the results for a single modulation type.Modulation types are mapped to numeric values. For the codeassignment, see Chapter 5.5.1.17, "Return Value Codes",on page 76.*RST: ALL

Example: //Display results for all elements with a QPSK modulationMOD:SEL 2


[SENSe:][LTE:][CC<cc>:]NPUSch:SELect <NPUSCH>

This command filters the displayed results by a specific NPUSCH.

Suffix: <cc>

.irrelevant

Parameters:<NPUSCH> ALL

Shows the results for all slots.<numeric_value>Shows the results for a single slot.*RST: ALL

Example: //Display results for all NPUSCHNPUS:SEL ALL

Analysis


120User Manual 1178.4230.02 ─ 02

Manual operation: See "NPUSCH Selection" on page 47

[SENSe:][LTE:][CC<cc>:]SLOT:SELect <Slot>

This command filters the displayed results in the constellation diagram by a particularslot.

Suffix: <cc>

.Component Carrier

Parameters:<Slot> ALL

Shows the results for all slots.<numeric_value>Shows the results for a single slot.*RST: ALL

Example: //Display results for all slotsSLOT:SEL ALL

Manual operation: See "Slot Selection" on page 47

[SENSe:][LTE:][CC<cc>:]SYMBol:SELect <Symbol>

This command filters the displayed results in the constellation diagram by a particularOFDM symbol.

Suffix: <cc>

.Component Carrier

Parameters:<Symbol> ALL

Shows the results for all subcarriers.<numeric_value>Shows the results for a single OFDM symbol.*RST: ALL

Example: //Display result for OFDM symbol 2SYMB:SEL 2


5.8.2 Y-Axis Scale

DISPlay[:WINDow<n>]:TRACe<t>:Y[:SCALe]:AUTO ONCE............................................... 121DISPlay[:WINDow<n>]:TRACe<t>:Y[:SCALe]:MAXimum................................................... 121DISPlay[:WINDow<n>]:TRACe<t>:Y[:SCALe]:MINimum.....................................................121

Analysis


121User Manual 1178.4230.02 ─ 02

DISPlay[:WINDow<n>]:TRACe<t>:Y[:SCALe]:AUTO ONCE

Automatic scaling of the y-axis is performed once, then switched off again (for alltraces).

Suffix: <n>

.Window

<t> irrelevant

Manual operation: See "Y-Axis Scale" on page 48

DISPlay[:WINDow<n>]:TRACe<t>:Y[:SCALe]:MAXimum <Value>

This command defines the maximum value of the y-axis for all traces in the selectedresult display.

Suffix: <n>

.Window

<t> irrelevant

Parameters:<Value> <numeric value>

*RST: depends on the result displayThe unit and range depend on the result display.

Example: DISP:TRAC:Y:MIN -60DISP:TRAC:Y:MAX 0Defines the y-axis with a minimum value of -60 and maximumvalue of 0.


DISPlay[:WINDow<n>]:TRACe<t>:Y[:SCALe]:MINimum <Value>

This command defines the minimum value of the y-axis for all traces in the selectedresult display.

Suffix: <n>

.Window

<t> irrelevant

Parameters:<Value> <numeric value>

*RST: depends on the result displayThe unit and range depend on the result display.

Example: DISP:TRAC:Y:MIN -60DISP:TRAC:Y:MAX 0Defines the y-axis with a minimum value of -60 and maximumvalue of 0.


Analysis


122User Manual 1178.4230.02 ─ 02

5.8.3 Result Settings

CALCulate:MARKer:COUPling........................................................................................ 122DISPlay[:WINDow]:SUBWindow:COUPling.......................................................................122UNIT:BSTR................................................................................................................... 122UNIT:CAXes..................................................................................................................123UNIT:EVM.....................................................................................................................123

CALCulate:MARKer:COUPling <State>

This command couples or decouples markers in different result displays to each other.


*RST: OFF

Example: //Couple markers to each other.CALC:MARK:COUP ON

Manual operation: See "Marker Coupling" on page 50

DISPlay[:WINDow]:SUBWindow:COUPling <State>

This command couples or decouples result display tabs (subwindows).

Subwindow coupling is available for measurements with multiple data streams (MIMO).


*RST: OFF

Example: DISP:SUBW:COUP ONTurns on subwindow coupling.

UNIT:BSTR <Unit>

This command selects the way the bit stream is displayed.

Parameters:<Unit> SYMbols

Displays the bit stream using symbolsBITsDisplays the bit stream using bits*RST: SYMbols

Example: //Display bit stream as bitsUNIT:BSTR BIT

Manual operation: See "Bit Stream Format" on page 49

Analysis


123User Manual 1178.4230.02 ─ 02

UNIT:CAXes <Unit>

This command selects the scale of the x-axis for result displays that show subcarrierresults.

Parameters:<Unit> CARR

Shows the number of the subcarriers on the x-axis.HZShows the frequency of the subcarriers on the x-axis.

Example: //Display frequency on the x-axisUNIT:CAX HZ

Manual operation: See "Carrier Axes" on page 50

UNIT:EVM <Unit>

This command selects the EVM unit.

Parameters:<Unit> DB

EVM results returned in dBPCTEVM results returned in %*RST: PCT

Example: //Display EVM results in %UNIT:EVM PCT

Manual operation: See "EVM Unit" on page 49

5.8.4 Marker

Commands to position markers and query marker positions are the same as in thebase unit.

For three-dimensional result diagrams, the application supports a couple of additionalcommands.

CALCulate<n>:MARKer<m>:Z?.......................................................................................123CALCulate<n>:MARKer<m>:Z:ALL?................................................................................ 124

CALCulate<n>:MARKer<m>:Z?

This command queries the marker position on the z-axis of three-dimensional resultdisplays.

This command returns the type of value displayed in the selected result display (EVMor Power).

Suffix: <m>

.Marker

Analysis


124User Manual 1178.4230.02 ─ 02

<n> Window

Return values: <Position> <numeric value>

Default unit: Depends on result display

Example: //Query marker positionCALC:MARK:Z?

Usage: Query only

CALCulate<n>:MARKer<m>:Z:ALL?

This command queries the marker position on the z-axis of three-dimensional resultdisplays.

Instead of returning a certain type of value (EVM or Power), which is possible withCALCulate<n>:MARKer<m>:Z?, this command returns all types of values (EVM andPower), regardless of the result display type.

Suffix: <m>

.irrelevant

<n> Window

Parameters:<Position> EVM

EVM at the marker position.PowerPower at the marker position.

Example: CALC:MARK:Z:ALL?Usage: Query only

Analysis

Annex: ReferenceR&S®VSE-K106

125User Manual 1178.4230.02 ─ 02

AnnexA Annex: Reference

● Menu Reference....................................................................................................125● Reference of Toolbar Functions............................................................................129

A.1 Menu Reference

Most functions in the R&S VSE are available from the menus.

● Common R&S VSE Menus................................................................................... 125● LTE Measurement Menus.....................................................................................127

A.1.1 Common R&S VSE Menus

The following menus provide basic functions for all applications:

● File Menu.............................................................................................................. 125● Window Menu....................................................................................................... 126● Help Menu.............................................................................................................127

A.1.1.1 File Menu

The "File" menu includes all functionality directly related to any file operations, printingor setting up general parameters.

Menu item Correspond-ing icon intoolbar

Description

Save Saves the current software configuration to a file

Recall Recalls a saved software configuration from a file

Save IQ Recording - Saves the recorded I/Q data from a measurement channel to afile

Recall IQ Recording - Loads the recorded I/Q data from a file

Measurement Group > - Configures measurement channels and groups

> New Group - Inserts a new group in the measurement sequence

> Rename Group - Changes the name of the selected group

> New MeasurementChannel

- Inserts a new channel in the selected group

Menu Reference


126User Manual 1178.4230.02 ─ 02


Description

> Replace Measure-ment Channel

- Replaces the currently selected channel by the selected applica-tion.

> Rename Measure-ment Channel

- Changes the name of the selected channel.

> Delete Current Mea-surement Channel

- Deletes the currently selected channel.

> Measurement GroupSetup

- Displays the "Measurement Group Setup" tool window.

Instruments > - Configures instruments to be used for input to the R&S VSE soft-ware

> New - Creates a new instrument configuration

> Search - Searches for connected instruments in the network

> Delete All - Deletes all current instrument configurations

> Setup - Hides or displays the "Instrument" tool window

Preset > - Restores stored settings

> Selected Channel - Restores the default software configuration for an individualchannel

> All - Restores the default software configuration globally for the entiresoftware

> All & Delete Instru-ments

Restores the default software configuration globally for the entiresoftware and deletes all instrument configurations

> Reset VSE Layout - Restores the default layout of windows, toolbars etc. in theR&S VSE software

Preferences > - Configures global software settings

> General -

> Displayed Items - Hides or shows individual screen elements

> Theme & Color - Configures the style of individual screen elements

> Network & Remote - Configures the network settings and remote access to or fromother devices

> Recording - Configures general recording parameters

Print - Opens "Print" dialog to print selected measurement results

Exit - Closes the R&S VSE software

A.1.1.2 Window Menu

The "Window" menu allows you to hide or show individual windows.

Menu Reference


127User Manual 1178.4230.02 ─ 02


Description

Player - Displays the "Player" tool window to recall I/Q data recordings

Instruments - Displays the "Instruments" window to configure input instruments

Measurement GroupSetup

- Displays the "Measurement Group Setup" window to configure ameasurement sequence

New Window > Inserts a new result display window for the selected measure-ment channel

Channel Information > - Displays the channel bar with global channel information for theselected measurement channel

Active Windows > - Selects a result display as the active window; the correspondingchannel is also activated

A.1.1.3 Help Menu

The "Help" menu provides access to help, support and licensing functions.


Description

Help Opens the Online help window

License - Licensing, version and options information

Support - Support functions

Register VSE - Attempts to create an email with the default mail program (ifavailable) to the Rohde & Schwarz support address for registra-tion.

Online Support - Opens the default web browser and attempts to establish anInternet connection to the Rohde & Schwarz product site.

About - Software version information

A.1.2 LTE Measurement Menus

● Input & Output Menu.............................................................................................127● Meas Setup Menu.................................................................................................128● Trace Menu...........................................................................................................128● Marker Menu.........................................................................................................128● Limits Menu...........................................................................................................129

A.1.2.1 Input & Output Menu

The "Input & Output" menu provides functions to configure the input source, frontendparameters and output settings for the measurement.

Menu Reference


128User Manual 1178.4230.02 ─ 02

This menu is application-specific.

Table A-1: "Input" menu items for LTE measurements

Menu item Description

Amplitude Chapter 3.2.9, "Defining Level Characteristics", on page 39

Scale Chapter 4.4, "Scale", on page 48

Frequency Chapter 3.2.8, "Defining the Frequency", on page 38

Trigger Chapter 3.2.10, "Triggering Measurements", on page 41

Input Source Chapter 3.2.7, "Selecting the Input and Output Source", on page 36

Output Source

A.1.2.2 Meas Setup Menu

The "Meas Setup" menu provides access to most measurement-specific settings, aswell as bandwidth, sweep and auto configuration settings, and the configuration "Over-view" window.


Table A-2: "Meas Setup" menu items for LTE measurements

Menu item Description

Select Measurement Chapter 2, "Measurements and Result Displays", on page 8

Signal Description Chapter 3.2.1, "Defining Signal Characteristics", on page 25

NPUSCH Configuration Chapter 3.2.2, "Configuring the NPUSCH", on page 27

Signal Capture Chapter 3.2.11, "Configuring the Data Capture", on page 42

Trigger Chapter 3.2.10, "Triggering Measurements", on page 41

Demod Chapter 3.2.12, "Signal Demodulation", on page 43

Evaluation Range Chapter 4.3, "Evaluation Range", on page 47

Result Settings Chapter 4.5, "Result Settings", on page 49

Overview Chapter 3.1, "Configuration Overview", on page 22

A.1.2.3 Trace Menu

The "Trace" does not contain any functions for LTE measurements, traces are gener-ally not configurable.

A.1.2.4 Marker Menu

The "Marker" menu provides access to marker-specific functions.


Menu Reference


129User Manual 1178.4230.02 ─ 02

Table A-3: "Marker" menu items for LTE measurements


Description

Select marker <x> Chapter 4.6, "Markers", on page 50

Marker to Trace - Chapter 4.6, "Markers", on page 50

All Markers Off Chapter 4.6, "Markers", on page 50

Marker... Chapter 4.6, "Markers", on page 50

Search - Chapter 4.6, "Markers", on page 50

A.1.2.5 Limits Menu

The "Limits" menu does not contain any functions for LTE measurements.

A.2 Reference of Toolbar Functions

Common functions can be performed via the icons in the toolbars.

Individual toolbars can be hidden or displayed.

Hiding and displaying a toolbar

1. Right-click any toolbar or the menu bar.

A context menu with a list of all available toolbars is displayed.

2. Select the toolbar you want to hide or display.

A checkmark indicates that the toolbar is currently displayed.

The toolbar is toggled on or off.

Note that some icons are only available for specific applications. Those functions aredescribed in the individual application's User Manual.

General toolbars

The following functions are generally available for all applications:

Reference of Toolbar Functions


130User Manual 1178.4230.02 ─ 02

"Main" toolbar

Table A-4: Functions in the "Main" toolbar

Icon Description

Overview: Displays the configuration overview for the current measurement channel

Save: Saves the current software configuration to a file

Recall: Recalls a saved software configuration from a file

Save I/Q recording: Stores the recorded I/Q data to a file

Recall I/Q recording: Loads recorded I/Q data from a file

Print immediately: prints the current display (screenshot) as configured

Add Window: Inserts a new result display window for the selected measurement channel

MultiView mode: displays windows for all active measurement channels (disabled: only windowsfor currently selected channel are displayed)

"Control" toolbar

Table A-5: Functions in the "Control" toolbar

Icon Description

Selects the currently active channel

Capture: performs the selected measurement

Pause: temporarily stops the current measurement

Continuous: toggles to continuous measurement mode for next capture

Single: toggles to single measurement mode for next capture

Record: performs the selected measurement and records the captured data andresults

Refresh: Repeats the evaluation of the data currently in the capture buffer withoutcapturing new data (VSA application only).



131User Manual 1178.4230.02 ─ 02

"Help" toolbar

Table A-6: Functions in the "Help" toolbar

Icon Description

Help (+ Select): allows you to select an object for which context-specific help is displayed

(not available in standard Windows dialog boxes or measurement result windows)

Help: displays context-sensitive help topic for currently selected element

Application-specific toolbars

The following toolbars are application-specific; not all functions shown here may beavailable in each application:

"Zoom" toolbar

Table A-7: Functions in the "Zoom" toolbar

Icon Description

Normal mouse mode: the cursor can be used to select (and move) markers in a zoomed display

Zoom mode: displays a dotted rectangle in the diagram that can be expanded to define thezoom area

Multiple zoom mode: multiple zoom areas can be defined for the same diagram

Zoom off: displays the diagram in its original size

Table A-8: Functions in the "Marker" toolbar

Icon Description

Place new marker

%Percent Marker (CCDF only)

Select marker

Marker type "normal"

Marker type "delta"

Global peak

Absolute peak

(Currently only for GSM application)

Next peak to the left

Next peak to the right



132User Manual 1178.4230.02 ─ 02

Icon Description

Next peak up (for spectrograms only: search in more recent frames)

Next peak down (for spectrograms only: search in previous frames)

Global minimum

Next minimum left

Next minimum right

Next min up (for spectrograms only: search in more recent frames)

Next min down (for spectrograms only: search in previous frames)

Set marker value to center frequency

Set reference level to marker value

All markers off

Marker search configuration

Marker configuration

Table A-9: Functions in the "AutoSet" toolbar

Icon Description

Auto level

Auto frequency

Auto trigger (R&S VSE GSM application only)

Auto frame (R&S VSE GSM application only)

Auto search (R&S VSE 3GPP FDD application only)

Auto scale (R&S VSE 3GPP FDD + Pulse applications only)

Auto scale all (R&S VSE 3GPP FDD + Pulse applications only)

Auto all

Configure auto settings


List of CommandsR&S®VSE-K106

133User Manual 1178.4230.02 ─ 02

List of Commands[SENSe:][LTE:][CC<cc>:]ALLocation:SELect................................................................................................118[SENSe:][LTE:][CC<cc>:]CARRier:SELect....................................................................................................118[SENSe:][LTE:][CC<cc>:]MODulation:SELect...............................................................................................119[SENSe:][LTE:][CC<cc>:]NPUSch:SELect.................................................................................................... 119[SENSe:][LTE:][CC<cc>:]SLOT:SELect.........................................................................................................120[SENSe:][LTE:][CC<cc>:]SYMBol:SELect.....................................................................................................120[SENSe:][LTE:]SFLatness:OBANd.................................................................................................................. 91[SENSe:][LTE:]SLOT:COUNt.........................................................................................................................102[SENSe:][LTE:]SLOT:COUNt:AUTO..............................................................................................................103[SENSe:][LTE:]SLOT:COUNt:STATe............................................................................................................ 103[SENSe:][LTE:]UL:DEMod:CBSCrambling.................................................................................................... 108[SENSe:][LTE:]UL:DEMod:CDCoffset........................................................................................................... 109[SENSe:][LTE:]UL:DEMod:CESTimation.......................................................................................................109[SENSe:][LTE:]UL:DEMod:MODE................................................................................................................... 91[SENSe:]ADJust:LEVel..................................................................................................................................117[SENSe:]FREQuency:CENTer:STEP............................................................................................................ 112[SENSe:]FREQuency:CENTer:STEP:LINK................................................................................................... 112[SENSe:]FREQuency:CENTer:STEP:LINK:FACTor......................................................................................113[SENSe:]FREQuency:CENTer[:CC<cc>].......................................................................................................111[SENSe:]POWer:ACHannel:AACHannel....................................................................................................... 117[SENSe:]SWAPiq...........................................................................................................................................103[SENSe:]SWEep:TIME.................................................................................................................................. 104[SENSe]:FREQuency:CENTer[:CC<cc>]:OFFSet.........................................................................................111CALCulate:MARKer:COUPling......................................................................................................................122CALCulate<n>:DELTamarker<m>:X............................................................................................................... 85CALCulate<n>:DELTamarker<m>:Y?............................................................................................................. 86CALCulate<n>:MARKer<m>:FUNCtion:POWer:RESult[:CURRent]?............................................................. 77CALCulate<n>:MARKer<m>:X........................................................................................................................ 86CALCulate<n>:MARKer<m>:Y?...................................................................................................................... 87CALCulate<n>:MARKer<m>:Z:ALL?.............................................................................................................124CALCulate<n>:MARKer<m>:Z?.................................................................................................................... 123CONFigure:[:LTE]:UL:AUTO:NPUSch:MTYPe................................................................................................91CONFigure:[:LTE]:UL:AUTO:NPUSch:NSUBcarrier........................................................................................92CONFigure:[:LTE]:UL:AUTO:NPUSch:SSUBcarrier........................................................................................92CONFigure[:LTE]:LDIRection.......................................................................................................................... 89CONFigure[:LTE]:MEASurement.....................................................................................................................88CONFigure[:LTE]:UL:NONPusch.....................................................................................................................93CONFigure[:LTE]:UL:NPUSch<np>:FORMat..................................................................................................93CONFigure[:LTE]:UL:NPUSch<np>:MODulation.............................................................................................93CONFigure[:LTE]:UL:NPUSch<np>:MREP..................................................................................................... 94CONFigure[:LTE]:UL:NPUSch<np>:NORu......................................................................................................94CONFigure[:LTE]:UL:NPUSch<np>:NOSubcarrier..........................................................................................94CONFigure[:LTE]:UL:NPUSch<np>:SSLot......................................................................................................95CONFigure[:LTE]:UL:NPUSch<np>:SSUBcarrier............................................................................................95CONFigure[:LTE]:UL[:CC<cc]:SSPacing.........................................................................................................89CONFigure[:LTE]:UL[:CC<cc>]:DRS:BSIX......................................................................................................96CONFigure[:LTE]:UL[:CC<cc>]:DRS:BSOurce............................................................................................... 96


134User Manual 1178.4230.02 ─ 02

CONFigure[:LTE]:UL[:CC<cc>]:DRS:BSTWelve.............................................................................................97CONFigure[:LTE]:UL[:CC<cc>]:DRS:BTHRee................................................................................................ 97CONFigure[:LTE]:UL[:CC<cc>]:DRS:CSSix....................................................................................................98CONFigure[:LTE]:UL[:CC<cc>]:DRS:CSTHree...............................................................................................98CONFigure[:LTE]:UL[:CC<cc>]:DRS:DSSHift................................................................................................. 99CONFigure[:LTE]:UL[:CC<cc>]:DRS:GRPHopping.........................................................................................99CONFigure[:LTE]:UL[:CC<cc>]:NPRach:FORMat.........................................................................................100CONFigure[:LTE]:UL[:CC<cc>]:NPRach:NIMode..........................................................................................100CONFigure[:LTE]:UL[:CC<cc>]:NPRach:NINit.............................................................................................. 101CONFigure[:LTE]:UL[:CC<cc>]:NPRach:NOSC............................................................................................101CONFigure[:LTE]:UL[:CC<cc>]:NPRach:NREP............................................................................................ 102CONFigure[:LTE]:UL[:CC<cc>]:NPRach:NSCoffset......................................................................................102CONFigure[:LTE]:UL[:CC<cc>]:PLC:CID........................................................................................................ 90CONFigure[:LTE]:UL[:CC<cc>]:PLC:CIDGroup.............................................................................................. 90CONFigure[:LTE]:UL[:CC<cc>]:PLC:PLID.......................................................................................................90CONFigure[:LTE]:UL[:CC<cc>]:SRS:STAT.....................................................................................................99CONFigure[:LTE]:UL[:CC<cc>]:SRS:SUConfig.............................................................................................100CONFigure[:LTE]:UL[:CC<cc>]:UEID..............................................................................................................96DISPlay[:WINDow]:SUBWindow:COUPling...................................................................................................122DISPlay[:WINDow<n>]:TRACe<t>:Y[:SCALe]:AUTO ONCE........................................................................ 121DISPlay[:WINDow<n>]:TRACe<t>:Y[:SCALe]:MAXimum............................................................................. 121DISPlay[:WINDow<n>]:TRACe<t>:Y[:SCALe]:MINimum.............................................................................. 121DISPlay[:WINDow<n>]:TRACe<t>:Y[:SCALe]:RLEVel..................................................................................113DISPlay[:WINDow<n>]:TRACe<t>:Y[:SCALe]:RLEVel:OFFSet....................................................................114DISPlay[:WINDow<n>][:SUBWindow<sub>]:SELect.......................................................................................58FETCh[:CC<cc>]:SUMMary:CRESt[:AVERage]?............................................................................................81FETCh[:CC<cc>]:SUMMary:EVM:PCHannel:MAXimum?...............................................................................82FETCh[:CC<cc>]:SUMMary:EVM:PCHannel:MINimum?................................................................................82FETCh[:CC<cc>]:SUMMary:EVM:PCHannel[:AVERage]?..............................................................................82FETCh[:CC<cc>]:SUMMary:EVM:PSIGnal:MAXimum?..................................................................................82FETCh[:CC<cc>]:SUMMary:EVM:PSIGnal:MINimum?...................................................................................82FETCh[:CC<cc>]:SUMMary:EVM:PSIGnal[:AVERage]?.................................................................................82FETCh[:CC<cc>]:SUMMary:EVM:UNDB[:AVERage]?....................................................................................79FETCh[:CC<cc>]:SUMMary:EVM:UNDQ[:AVERage]?................................................................................... 79FETCh[:CC<cc>]:SUMMary:EVM:UNSB[:AVERage]?....................................................................................80FETCh[:CC<cc>]:SUMMary:EVM:UNSQ[:AVERage]?....................................................................................80FETCh[:CC<cc>]:SUMMary:EVM:UPRA[:AVERage]?....................................................................................80FETCh[:CC<cc>]:SUMMary:EVM[:ALL]:MAXimum?.......................................................................................82FETCh[:CC<cc>]:SUMMary:EVM[:ALL]:MINimum?........................................................................................82FETCh[:CC<cc>]:SUMMary:EVM[:ALL][:AVERage]?......................................................................................82FETCh[:CC<cc>]:SUMMary:FE3G:MAXimum?...............................................................................................83FETCh[:CC<cc>]:SUMMary:FE3G:MINimum?................................................................................................83FETCh[:CC<cc>]:SUMMary:FE3G[:AVERage]?............................................................................................. 83FETCh[:CC<cc>]:SUMMary:FERRor:MAXimum?...........................................................................................83FETCh[:CC<cc>]:SUMMary:FERRor:MINimum?............................................................................................ 83FETCh[:CC<cc>]:SUMMary:FERRor[:AVERage]?..........................................................................................83FETCh[:CC<cc>]:SUMMary:GIMBalance:MAXimum?.................................................................................... 84FETCh[:CC<cc>]:SUMMary:GIMBalance:MINimum?..................................................................................... 84FETCh[:CC<cc>]:SUMMary:GIMBalance[:AVERage]?...................................................................................84FETCh[:CC<cc>]:SUMMary:IQOFfset:MAXimum?......................................................................................... 84


135User Manual 1178.4230.02 ─ 02

FETCh[:CC<cc>]:SUMMary:IQOFfset:MINimum?...........................................................................................84FETCh[:CC<cc>]:SUMMary:IQOFfset[:AVERage]?........................................................................................ 84FETCh[:CC<cc>]:SUMMary:POWer:MAXimum?............................................................................................ 84FETCh[:CC<cc>]:SUMMary:POWer:MINimum?............................................................................................. 84FETCh[:CC<cc>]:SUMMary:POWer[:AVERage]?...........................................................................................84FETCh[:CC<cc>]:SUMMary:QUADerror:MAXimum?......................................................................................85FETCh[:CC<cc>]:SUMMary:QUADerror:MINimum?....................................................................................... 85FETCh[:CC<cc>]:SUMMary:QUADerror[:AVERage]?.....................................................................................85FORMat[:DATA]...............................................................................................................................................78INPut:ATTenuation........................................................................................................................................ 114INPut:ATTenuation:AUTO............................................................................................................................. 114INPut:COUPling.............................................................................................................................................114INPut:FILTer:HPASs[:STATe]........................................................................................................................109INPut:FILTer:YIG[:STATe].............................................................................................................................110INPut:GAIN:STATe........................................................................................................................................115INPut:GAIN[:VALue]...................................................................................................................................... 115INPut:IMPedance...........................................................................................................................................115INPut:SELect................................................................................................................................................. 110INPut<n>:EATT..............................................................................................................................................116INPut<n>:EATT:AUTO...................................................................................................................................116INPut<n>:EATT:STATe................................................................................................................................. 116INSTrument:BLOCk:CHANnel[:SETTings]:SOURce.....................................................................................110INSTrument[:SELect].......................................................................................................................................58LAYout:ADD[:WINDow]?................................................................................................................................. 63LAYout:CATalog[:WINDow]?...........................................................................................................................65LAYout:GLOBal:ADD[:WINDow]?....................................................................................................................59LAYout:GLOBal:CATalog[:WINDow]?............................................................................................................. 61LAYout:GLOBal:IDENtify[:WINDow]?..............................................................................................................61LAYout:GLOBal:REMove[:WINDow]............................................................................................................... 62LAYout:GLOBal:REPLace[:WINDow]..............................................................................................................62LAYout:IDENtify[:WINDow]?............................................................................................................................65LAYout:REMove[:WINDow]............................................................................................................................. 66LAYout:REPLace[:WINDow]............................................................................................................................66LAYout:WINDow<n>:ADD?............................................................................................................................. 66LAYout:WINDow<n>:IDENtify?........................................................................................................................67LAYout:WINDow<n>:REMove.........................................................................................................................68LAYout:WINDow<n>:REPLace........................................................................................................................68MMEMory:LOAD:IQ:STATe.............................................................................................................................88SYSTem:PRESet:CHANnel[:EXEC]................................................................................................................88TRACe<n>[:DATA]?........................................................................................................................................ 76TRIGger[:SEQuence]:HOLDoff<instrument>.................................................................................................104TRIGger[:SEQuence]:LEVel:MAPower..........................................................................................................105TRIGger[:SEQuence]:LEVel<instrument>[:EXTernal]................................................................................... 105TRIGger[:SEQuence]:MAPower:HOLDoff..................................................................................................... 105TRIGger[:SEQuence]:MAPower:HYSTeresis................................................................................................105TRIGger[:SEQuence]:PORT<instrument>.....................................................................................................106TRIGger[:SEQuence]:POSition......................................................................................................................106TRIGger[:SEQuence]:SLOPe........................................................................................................................ 107TRIGger[:SEQuence]:SOURce......................................................................................................................107UNIT:BSTR....................................................................................................................................................122


136User Manual 1178.4230.02 ─ 02

UNIT:CAXes.................................................................................................................................................. 123UNIT:EVM......................................................................................................................................................123

IndexR&S®VSE-K106

137User Manual 1178.4230.02 ─ 02

Index

A

AC/DC coupling .................................................................40ACLR ...........................................................................20, 21Add channel ........................................................................ 5Allocation

Filter by ....................................................................... 48Allocation summary ........................................................... 15Amplitude .......................................................................... 39ASCII export ...................................................................... 46Attenuation ........................................................................ 40Auto Detection (Cell Identity) ............................................ 26Auto level .......................................................................... 39Auto scale y-axis ............................................................... 48

B

Bandwidth ......................................................................... 26Base sequence source ......................................................32Base sequence tone ......................................................... 32Bit stream .......................................................................... 16Bitstream format ................................................................ 49

C

Capture buffer ................................................................... 10Capture time ......................................................................42Carrier

Filter by ....................................................................... 48Carrier axis scale .............................................................. 50CCDF ................................................................................ 14Cell ID ............................................................................... 26Cell Identity Group ............................................................ 26Center frequency ...............................................................38Channel bandwidth ........................................................... 26Channel bar .........................................................................6Channel estimation range ................................................. 44Channel flatness group delay ............................................13Closing

Windows (remote) ...........................................62, 66, 68Compensate DC offset ...................................................... 44Configuration overview ......................................................22Configuration Table ........................................................... 27Constellation diagram ....................................................... 14

Configuration .............................................................. 48Constellation selection ...................................................... 48Conventions

SCPI commands ......................................................... 53Coupling

Input (remote) ........................................................... 114Cyclic shift tone ................................................................. 32

D

Data capture ......................................................................42Data input .......................................................................... 36DC offset ........................................................................... 44Delta sequence shift ..........................................................33Demodulation .................................................................... 43Demodulation reference signal

Delta sequence shift ................................................... 33Group hopping ............................................................ 33

Demodulation reference signal configuration .................... 31Display information ..............................................................6

Duplexing .......................................................................... 25

E

Evaluation methodsRemote ................................................................. 59, 63

Evaluation range ............................................................... 47EVM unit ............................................................................49EVM vs Carrier .................................................................. 11EVM vs symbol ................................................................. 11EVM vs symbol x carrier ................................................... 16Export ................................................................................ 46External Attenuation .......................................................... 40External trigger .................................................................. 41

F

FiltersHigh-pass (remote) ................................................... 109High-pass (RF input) ...................................................36YIG (remote) ............................................................. 110

Free run .............................................................................41Frequency

Configuration .............................................................. 38Frequency sweep measurement ....................................... 20

G

Global signal characteristics ............................................. 30Group hopping .................................................................. 33

H

Hardware settings ............................................................... 6High-pass filter

Remote ..................................................................... 109RF input ...................................................................... 36

I

I/Q measurement ................................................................ 9Identity (Physical Layer) .................................................... 26Impedance

Remote ..................................................................... 115Setting .........................................................................40

InputCoupling ......................................................................40Coupling (remote) ..................................................... 114

Input source ...................................................................... 36Input sources

Channels .....................................................................38

L

Level configuration ............................................................ 39Link direction ..................................................................... 25

M

Marker coupling .................................................................50Marker table

Evaluation method ...................................................... 20

IndexR&S®VSE-K106

138User Manual 1178.4230.02 ─ 02

MarkersQuerying position (remote) ......................................... 87Table (evaluation method) .......................................... 20

MeasurementACLR .................................................................... 20, 21allocation summary ..................................................... 15bit stream .................................................................... 16Capture buffer ............................................................. 10CCDF .......................................................................... 14channel flatness group delay ...................................... 13constellation ................................................................ 14Continuous ....................................................................9EVM vs carrier ............................................................ 11EVM vs sym x carr ...................................................... 16EVM vs symbol ........................................................... 11Export data ................................................................. 46Frequency sweep ....................................................... 20I/Q ................................................................................. 9numerical .................................................................... 17power spectrum .......................................................... 12power vs sym x carr .................................................... 17Refresh ......................................................................... 9Result displays ..............................................................9result summary ........................................................... 17Selecting ....................................................................... 8Single ............................................................................ 9spectrum flatness ........................................................13spectrum flatness difference ....................................... 13

Measurement channelsInput source ................................................................ 38

Measurement time ............................................................ 42Modulation .........................................................................30

Filter by ....................................................................... 48Modulation detection ......................................................... 27

N

N_init ................................................................................. 36n_RNTI .............................................................................. 31NB-IoT application ...............................................................5NPUSCH

Auto configuration ....................................................... 27Configuration .............................................................. 27detection ..................................................................... 27Manual configuration .................................................. 28Modulation .................................................................. 30Repetitions .................................................................. 30Resource units ............................................................ 30Selection ..................................................................... 47Starting subcarrier ...................................................... 29table ............................................................................ 28Table conflicts ............................................................. 28Trigger ........................................................................ 41

NPUSCH format ................................................................ 29NPUSCH start slot ............................................................ 29Number of slots to analyze ................................................43Number of subcarriers .......................................................29Numerical result configuration ...........................................46Numerical results .............................................................. 17

O

OffsetFrequency ................................................................... 38Reference level ........................................................... 39

Operating band index ........................................................ 26

OptionsHigh-pass filter .................................................... 36, 109

Overall slot count .............................................................. 43Overview ........................................................................... 22

P

Physical signal .................................................................. 25Power spectrum ................................................................ 12Power vs symbol x carrier ................................................. 17Presetting

Channels .....................................................................24

R

Reference Level ................................................................ 39Remote commands

Basics on syntax ......................................................... 53Boolean values ........................................................... 56Capitalization .............................................................. 54Character data ............................................................ 57Data blocks ................................................................. 57Numeric values ........................................................... 56Optional keywords ...................................................... 55Parameters ................................................................. 55Strings .........................................................................57Suffixes ....................................................................... 54

Resource units .................................................................. 30Restoring

Channel settings ......................................................... 24Result displays .................................................................... 9

Marker table ................................................................ 20Result settings ...................................................................49Result summary ................................................................ 17RF input .............................................................................36

Remote ..................................................................... 110

S

Scale y-axis ....................................................................... 48Scrambling of coded bits ................................................... 44Screen layout ...................................................................... 6Settings

Auto ............................................................................ 26Auto modulation type .................................................. 27Auto number of subcarriers ........................................ 27Auto start subcarrier ................................................... 27Base sequence source ............................................... 32Base sequence tone ................................................... 32Bitstream format ......................................................... 49Capture time ............................................................... 42Carrier axes ................................................................ 50Channel estimation range ........................................... 44Compensate DC offset ............................................... 44Constellation selection ................................................ 48Cyclic shift tone ...........................................................32Delta sequence shift ................................................... 33EVM unit ..................................................................... 49Ext Att ......................................................................... 40Frequency ................................................................... 38Group hopping ............................................................ 33Identity ........................................................................ 26M_rep_NPUSCH ........................................................ 30Marker coupling .......................................................... 50Modulation .................................................................. 30n_RNTI ....................................................................... 31N_RU .......................................................................... 30

IndexR&S®VSE-K106

139User Manual 1178.4230.02 ─ 02

NCell ID ...................................................................... 26NCell Identity Group ................................................... 26NPUSCH format ......................................................... 29NPUSCH selection ..................................................... 47Number of slots to analyze ......................................... 43Number of subcarriers ................................................ 29Operating band index ................................................. 26Overall slot count ........................................................ 43Present ....................................................................... 34Ref Level .....................................................................39Scrambling of coded bits ............................................ 44Slot selection .............................................................. 47SRS subframe configuration ....................................... 34Standard ..................................................................... 25Start slot ......................................................................29Starting subcarrier ...................................................... 29Swap I/Q ..................................................................... 43UE_ID ......................................................................... 31

Signal capture ................................................................... 42Signal characteristics ........................................................ 25Signal source

Remote ..................................................................... 110Slope

Trigger ...................................................................... 107Slot capture ....................................................................... 43Slot count .......................................................................... 43Slot selection ..................................................................... 47Sounding reference signal

Present ....................................................................... 34SRS subframe configuration ....................................... 34

Sounding reference signal configuration ........................... 33Specifics for

Configuration .............................................................. 24Spectrum flatness ....................................................... 13, 26Spectrum flatness difference .............................................13Standard selection ............................................................ 25Start slot ............................................................................ 29Start subcarrier detection .................................................. 27Starting subcarrier ............................................................. 29Status bar ............................................................................ 7Step size ........................................................................... 38Subcarrier ..........................................................................29Subcarrier detection .......................................................... 27Subcarrier spacing ............................................................ 26Subcarriers ........................................................................ 29Suffixes

Common ..................................................................... 52Remote commands .....................................................54

Swap I/Q ........................................................................... 43Symbol

Filter by ....................................................................... 48

T

Table layout .......................................................................46Toolbars

AutoSet ..................................................................... 132Control ...................................................................... 130Functions .................................................................. 129Help .......................................................................... 131Main .......................................................................... 130Marker .......................................................................131Overview ................................................................... 129Zoom .........................................................................131

Trace export ...................................................................... 46Transmission path ............................................................. 25

TriggerExternal (remote) ...................................................... 107Slope .........................................................................107

Trigger configuration ......................................................... 41Trigger position ................................................................. 41

U

UE_ID ................................................................................31

W

Window title bar ...................................................................7Windows

Adding (remote) .................................................... 59, 63Closing (remote) ............................................. 62, 66, 68Configuring ................................................................. 24Querying (remote) .................................................61, 65Replacing (remote) ............................................... 62, 66Types (remote) ..................................................... 59, 63

Y

Y-axis scale ....................................................................... 48YIG-preselector

Activating/Deactivating ............................................... 37Activating/Deactivating (remote) ............................... 110

Z

ZoomCapture buffer ............................................................. 10

Documents

VSE NB-IoT Measurement Application · PDF file5.5 Remote Commands to Read Trace Data ... The LTE NB-IoT measurement application measures and analyzes various aspects of an LTE NB-IoT