FSW UserManual
FSW UserManual
(;×ì;2)
1173941102
Version 55
This manual applies to the following FSW models with firmware version 6.20 and later:
● R&S®FSW8 (1331.5003K08 / 1312.8000K08)
● R&S®FSW13 (1331.5003K13 / 1312.8000K13)
● R&S®FSW26 (1331.5003K26 / 1312.8000K26)
● R&S®FSW43 (1331.5003K43 / 1312.8000K43)
● R&S®FSW50 (1331.5003K50 / 1312.8000K50)
● R&S®FSW67 (1331.5003K67 / 1312.8000K67)
● R&S®FSW85 (1331.5003K85 / 1312.8000K85)
Contents
1 Safety and regulatory information......................................................17
1.1 Safety instructions......................................................................................................17
1.2 Warning messages in the documentation................................................................ 20
1.3 Korea certification class B......................................................................................... 21
2 Documentation overview.....................................................................22
2.1 Getting started manual............................................................................................... 22
2.2 User manuals and help...............................................................................................22
2.3 Service manual............................................................................................................22
2.4 Instrument security procedures................................................................................ 23
2.5 Printed safety instructions.........................................................................................23
2.6 Specifications and brochures....................................................................................23
2.7 Release notes and open-source acknowledgment (OSA).......................................23
2.8 Application notes, application cards, white papers, etc......................................... 24
2.9 Videos...........................................................................................................................24
4 Getting Started..................................................................................... 26
4.1 Key features.................................................................................................................26
4.2 Preparing for use........................................................................................................ 27
4.2.1 Lifting and carrying........................................................................................................27
4.2.2 Unpacking and checking............................................................................................... 27
4.2.3 Choosing the operating site.......................................................................................... 27
4.2.4 Setting up the product................................................................................................... 28
4.2.5 Connecting the AC power............................................................................................. 30
4.2.6 Switching the instrument on and off.............................................................................. 30
4.2.7 Connecting to RF coaxial connectors........................................................................... 32
4.2.8 Connecting to LAN........................................................................................................ 33
4.2.9 Connecting a keyboard................................................................................................. 34
4.2.10 Connecting an external monitor.................................................................................... 34
4.2.11 Considerations for test setup........................................................................................ 36
4.2.12 Windows operating system........................................................................................... 37
14 Troubleshooting............................................................................... 1548
14.1 Error information.....................................................................................................1548
14.2 Error messages in remote control mode.............................................................. 1550
14.3 Troubleshooting remote operation........................................................................1551
14.4 Miscellaneous troubleshooting hints....................................................................1553
14.5 System recovery..................................................................................................... 1555
14.6 Collecting information for support........................................................................1555
14.7 Contacting customer support................................................................................1558
Index..................................................................................................1589
Intended use
The product is intended for the development, production and verification of electronic
components and devices in industrial, administrative, and laboratory environments.
Use the product only for its designated purpose. Observe the operating conditions and
performance limits stated in the specifications document.
Target audience
The target audience of this document includes developers and technicians, administra-
tors and maintenance personnel performing RF signal measurements. The required
skills and experience of the users depend on the test setup and application of the prod-
uct.
Connecting to power
The product is an overvoltage category II product. Connect the product to a fixed
installation used to supply energy-consuming equipment such as household applian-
ces and similar loads. Keep in mind that electrically powered products have risks, such
as electric shock, fire, personal injury or even death. Replace parts that are relevant to
safety only by original parts, e.g. power cables or fuses.
Take the following measures for your safety:
● Before switching on the product, ensure that the voltage and frequency indicated
on the product match the available power source. If the power adapter does not
adjust automatically, set the correct value and check the rating of the fuse.
● Only use the power cable delivered with the product. It complies with country-spe-
cific safety requirements. Only insert the plug into an outlet with protective conduc-
tor terminal.
● Only use intact cables and route them carefully so that they cannot be damaged.
Check the power cables regularly to ensure that they are undamaged. Also ensure
that nobody can trip over loose cables.
● Only connect the product to a power source with a fuse protection of maximum
20 A.
● Ensure that you can disconnect the product from the power source at any time.
Pull the power plug to disconnect the product. The power plug must be easily
accessible. If the product is integrated into a system that does not meet these
requirements, provide an easily accessible circuit breaker at the system level.
Using headphones
Take the following measures to prevent hearing damage. Before using headphones,
check the volume and reduce it if necessary. If you monitor varying signal levels, take
off the headphones and wait until the signal has settled. Then adjust the volume.
Potential hazard
Read the product documentation to avoid personal injury or product damage.
Heavy product
Be careful when lifting, moving or carrying the product. Carrying the product requires a suffi-
cient number of persons or transport equipment.
Electrical hazard
Indicates live parts. Risk of electric shock, fire, personal injury or even death.
Hot surface
Do not touch. Risk of skin burns. Risk of fire.
WARNING
Potentially hazardous situation. Could result in death or serious injury if not avoided.
CAUTION
Potentially hazardous situation. Could result in minor or moderate injury if not avoided.
NOTICE
Potential risks of damage. Could result in damage to the supported product or to other
property.
2 Documentation overview
This section provides an overview of the FSW user documentation. Unless specified
otherwise, you find the documents at:
www.rohde-schwarz.com/manual/FSW
Further documents are available at:
www.rohde-schwarz.com/product/FSW
The service manual is available for registered users on the global Rohde & Schwarz
information system (GLORIS):
https://gloris.rohde-schwarz.com
2.9 Videos
Find various videos on Rohde & Schwarz products and test and measurement topics
on YouTube: https://www.youtube.com/@RohdeundSchwarz
4 Getting Started
Note: the following sections are identical to those in the printed FSW Getting Started
manual.
● Key features............................................................................................................ 26
● Preparing for use.....................................................................................................27
● Instrument tour........................................................................................................ 43
● Trying out the instrument........................................................................................ 63
● Operating the instrument.........................................................................................81
The carrying handles are designed to lift or carry the instrument. Do not apply exces-
sive external force to the handles.
See "Lifting and carrying the product" on page 18.
2. Retain the original packing material. Use it when transporting or shipping the FSW
later.
Specific operating conditions ensure proper operation and avoid damage to the prod-
uct and connected devices. For information on environmental conditions such as ambi-
ent temperature and humidity, see the specifications document.
For safety information, see "Choosing the operating site" on page 18.
See also:
● "Setting up the product" on page 18
● "Intended use" on page 17
2. WARNING! A stack of products can fall over and cause injury. Never stack more
than two products. Otherwise, mount them in a rack.
Stack as follows:
● All products must have the same dimensions (width and length).
● Do not exceed a total load of 50 kg placed on the product at the bottom of the
stack.
2. NOTICE! Insufficient airflow can cause overheating and damage the product.
Design and implement an efficient ventilation concept for the rack.
3. Grab the handles and push the FSW onto the shelf until the rack brackets fit
closely to the rack.
4. Tighten all screws in the rack brackets with a tightening torque of 1.2 Nm to secure
the FSW in the rack.
3. If placing the FSW on a bench top again, unmount the adapter kit from the FSW.
Follow the instructions provided with the adapter kit.
In the standard version, the FSW is equipped with an AC power supply connector.
The FSW can be used with different AC power voltages and adapts itself automatically
to it. Refer to the specifications document for the requirements of voltage and fre-
quency.
For safety information, see "Connecting to power" on page 19.
2. Plug the AC power cable into a power outlet with ground contact.
The required ratings are listed next to the AC power connector and in the specifica-
tions document.
For details on the connector, refer to Section 4.3.2.2, "AC power supply connection and
main power switch", on page 56.
If the instrument temperature exceeds the limit specified in the specifications docu-
ment, the FSW automatically shuts down to protect the instrument from damage.
The most common interface used to provide signal input to the FSW is the RF input 50
ohm connector.
The RF input can be coupled to the DUT by alternating current (AC) or direct current
(DC). AC coupling blocks any DC voltage from the input signal. This is the default set-
ting to prevent damage to the instrument. However, some specifications require DC
coupling.
In this case, protect the instrument from damaging DC input voltages manually, e.g. by
inserting a DC blocker or using a bias tee to bias your DUT and supply the DC input to
the instrument. For details, refer to the specifications document.
2. Use a high-quality RF cable that matches the RF connector type. See also "Cable
selection to minimize electromagnetic interference (EMI)" on page 36.
2. Mate the connectors along the common axis until the male pin of the inner connec-
tor engages with the female socket of the outer connector.
3. Turn the nut of the outer connector until the connectors are firmly coupled.
2. Mate the connectors along the common axis until the male pin of the connector of
the cable engages with the female socket of the BNC connector.
You can connect the instrument to a LAN for remote operation via a PC.
For details on the connector, see Section 4.3.2.4, "LAN", on page 56.
Provided the network administrator has assigned you the appropriate rights and adap-
ted the Windows firewall configuration, you can use the interface, for example:
● To transfer data between a controlling device and the test device, e.g. to run a
remote control program
● To access or control the measurement from a remote computer using the "Remote
Desktop" application (or a similar tool)
● To connect external network devices (e.g. printers)
● To transfer data from a remote computer and back, e.g. using network folders
Network environment
Before connecting the product to a local area network (LAN), consider the following:
● Install the latest firmware to reduce security risks.
● For internet or remote access, use secured connections, if applicable.
● Ensure that the network settings comply with the security policies of your company.
Contact your local system administrator or IT department before connecting your
product to your company LAN.
● When connected to the LAN, the product may potentially be accessed from the
internet, which may be a security risk. For example, attackers might misuse or
damage the product. For more information about IT security and how to operate
the product in a secure LAN environment, see the Rohde & Schwarz white paper
1EF96: Malware Protection Windows 10.
For more information on LAN configuration, see Section 12.6.4, "LAN settings",
on page 864.
The keyboard is detected automatically when it is connected. The default input lan-
guage is English – US.
However, you can also connect foreign language keyboards; currently the following
languages are supported for the FSW:
● German
● Swiss
● French
● Russian
2. Select "Start > Settings > Time & language > Region & language > Add a lan-
guage" .
You can connect an external monitor (or projector) to the "DVI" or "Display port" con-
nector on the rear panel of the FSW (see also Section 4.3.2.5, "Display port and DVI",
on page 57).
2. Press [Setup].
3. Press "Display".
6. Tap "Apply" to try out the settings before they are accepted permanently, then you
can easily return to the previous settings, if necessary.
An unsuitable test setup can damage the instrument and connected devices.
Electrostatically discharge the DUT with a short or match before connecting it to the
instrument. Even residual charges on cables can cause damage when discharged by
the instrument.
The instrument contains the Windows 10 operating system which has been configured
according to the instrument's features and needs. Changes in the system setup are
only required when peripherals like a keyboard or a printer are installed or if the net-
work configuration does not comply with the default settings. After the FSW is started,
the operating system boots and the instrument firmware is started automatically.
Tested software
The drivers and programs used on the instrument under Windows 10 are adapted to
the instrument. Only install update software released by Rohde & Schwarz to modify
existing instrument software.
You can install additional software on the instrument; however, additional software can
impair instrument function. Thus, run only programs that Rohde & Schwarz has tested
for compatibility with the instrument software.
The following program packages have been tested:
● R&S Power Viewer Plus - virtual power meter for displaying results of the power
sensor R&S NRPxx (install only this component!)
● Symantec Endpoint Security – virus-protection software
● FileShredder - for reliable deletion of files on the hard disk
Firewall settings
A firewall protects an instrument by preventing unauthorized users from gaining access
to it through a network. Rohde & Schwarz highly recommends using the firewall on
your instrument. Rohde & Schwarz instruments are shipped with the Windows firewall
enabled. All ports and connections for remote control are enabled.
Note that changing firewall settings requires administrator rights.
Virus protection
Take appropriate steps to protect your instruments from infection. Use strong firewall
settings and scan any removable storage device used with a Rohde & Schwarz instru-
ment regularly. It is also recommended that you install anti-virus software on the instru-
ment. Rohde & Schwarz does NOT recommend running anti-virus software in the
background ("on-access" mode) on Windows-based instruments, due to potentially
degrading instrument performance. However, Rohde & Schwarz does recommend run-
ning it during non-critical hours.
For details and recommendations, see the following Rohde & Schwarz white paper:
● 1EF96: Malware Protection Windows 10
The Windows taskbar also provides quick access to commonly used programs, for
example Paint or WordPad. IECWIN, the auxiliary remote control tool provided free of
charge and installed by Rohde & Schwarz, is also available from the taskbar or "Start"
menu.
For details on the IECWIN tool, see Section 12.4, "The IECWIN tool", on page 840.
All necessary system settings can be defined in the "Start > Settings" menu.
For required settings, refer to the Windows 10 documentation and to the hardware
description.
4.2.13 Logging on
Windows 10 requires that users identify themselves by entering a user name and pass-
word in a login window. By default, the FSW provides the following user accounts:
● "Instrument": an administrator account with unrestricted access to the computer/
domain
● "NormalUser": a standard user account with limited access
Some administrative tasks require administrator rights (e.g. the configuration of a LAN
network). Refer to the description of the basic instrument Setup ([Setup] menu) to find
out which functions are affected.
Passwords
For all default user accounts, the initial password is 894129. Note that this password is
very weak, and it is recommended that you change the password for all users after ini-
tial login. An administrator can change the password in Windows 10 for any user at any
time via "Start > Settings > Account > SignIn Options > Password > Change".
Auto-login
When shipped, the instrument automatically logs on the default "Instrument" user to
Windows 10 (with full access) using the default password. This function is active until
an administrator explicitly deactivates it or changes the password.
1. Select the "Windows" icon in the toolbar to access the operating system of the
FSW (see also "To access the "Start" menu" on page 38).
For information on deactivating and reactivating the auto-login function, see "Deactivat-
ing the auto-login function" on page 883.
The instrument can be equipped with both hardware and firmware options. To check
whether the installed options correspond to the options indicated on the delivery note,
proceed as follows.
1. Press [SETUP].
3. Switch to the "Versions + Options" tab in the "System Configuration" dialog box.
A list with hardware and firmware information is displayed.
4. Check the availability of the hardware options as indicated in the delivery note.
When temperature changes occur in the environment of the FSW, or after updating the
firmware, you have to perform a self-alignment to align the data to a reference source.
During self-alignment, do not connect a signal to the RF input connector. Running a
self-alignment with a signal connected to the RF input can lead to false measurement
results.
Performing a self-alignment
Before performing this alignment, make sure that the instrument has reached its oper-
ating temperature (for details, refer to the specifications document).
A message in the status bar ("Instrument warming up...") indicates that the operating
temperature has not yet been reached.
2. Press "Alignment".
During normal operation, the FSW uses a solid-state drive to store its operating sys-
tem, instrument firmware, instrument self-alignment data, and any user data created
during operation.
If necessary, the solid-state drive can be removed from the FSW and locked in a
secure place to protect any classified data it may contain.
Self-alignment data
Note that self-alignment data becomes invalid with time and due to temperature
changes. Therefore, to achieve optimal accuracy, it can be preferable to perform a new
self-alignment at the start of each new session on the FSW.
Windows updates
In secure user mode, in rare cases, Windows updates trigger a reboot. We recommend
using secure user mode on R&S FSW-K33 only in private LAN without access to the
internet or disconnected to LAN to avoid unwanted Windows updates. In preparation
for Windows updates, disable secure user mode temporarily.
Restricted operation
Since permanent storage is not possible, the following functions are not available in
secure user mode:
● Firmware update
● Activating a new option key
Furthermore, since the "SecureUser" used in secure user mode does not have admin-
istrator rights, administrative tasks such as LAN configuration and some general
instrument settings are not available. Refer to the description of the basic instrument
setup ([SETUP] menu) to find out which functions are affected.
Secure passwords
By default, the initial password for both the administrator account and the "Secure-
User" account is "894129". When the secure user mode is activated the first time after
installation, you are prompted to change the passwords for all user accounts to
improve system security. Although it is possible to continue without changing the pass-
words, it is strongly recommended that you do so.
You can change the password in Windows 10 for any user at any time via:
"Start > Settings > Account > SignIn Options > Password > Change"
To deactivate the secure user mode, the "SecureUser" must log off and a user with
administrator rights must log on.
The secure user mode setting and auto-login is automatically deactivated when
another user logs on. The "SecureUser" is no longer available.
For users with administrator rights, the secure user mode setting is available in the
general system configuration settings (see "SecureUser Mode" on page 794).
Remote control
Initially after installation of the R&S FSW-K33 option, secure user mode must be
enabled manually once before remote control is possible.
(See SYSTem:SECurity[:STATe].)
Manual activation is necessary to prompt for a change of passwords.
This section describes the front panel, including all function keys and connectors.
(Note: the graphic shows a 26 GHz model of the FSW. Some connectors on the
85 GHz model differ slightly; differences are indicated for the individual connectors.)
2 3 4
7
1
16 15 14 13 12 11 10 9 8
1 = POWER key
2 = Touchscreen
3 = Function keys
4 = Keypad
5 = Navigation controls
6 = TRIGGER INPUT/OUTPUT connectors
7 = RF Input 50 Ω connector
8 = EXT MIXER connector (optional)
9 = (Analog) Baseband Input 50Ω connectors for I/Q signal or Rohde & Schwarz active probes (optional)
10 = (Analog) Baseband Input 50Ω connectors for inverse part of differential I/Q signal (optional, not for
FSW85)
11 = NOISE SOURCE CONTROL
12 = PROBE connector
13 = POWER SENSOR connector
14 = USB connectors
15 = Headphones connector and volume control
16 = SYSTEM keys
The power key is on the lower left corner of the front panel. It starts up and shuts down
the instrument.
See also "Connecting to power" on page 19.
4.3.1.2 Touchscreen
All measurement results are displayed on the screen on the front panel. Additionally,
the screen display provides status and setting information and allows you to switch
between various measurement tasks. The screen is touch-sensitive, offering an alter-
native means of user interaction for quick and easy handling of the instrument.
1 2 3 4
5
7
1 = Toolbar with standard application functions, e.g. print, save/open file etc.
2 = Tabs for individual measurement channels
3 = Channel bar for firmware and measurement settings
4 = Measurement results area
5 = Softkeys for function access
6 = Instrument status bar with error messages, progress bar and date/time display
7 = Diagram footer with diagram-specific information, depending on application
8 = Window title bar with diagram-specific (trace) information
Any user interface elements that react to a click by a mouse pointer also react to a tap
on the screen, and vice versa. Using touchscreen gestures, you can perform the fol-
lowing tasks (among others, see also Section 4.4, "Trying out the instrument",
on page 63):
● Changing a setting
● Changing the display
● Moving a marker
● Zooming into a diagram
● Selecting a new evaluation method
● Scrolling through a result list or table
● Saving or printing results and settings
To imitate a right-click by mouse using the touchscreen, for example to open a context-
sensitive menu for a specific item, press the screen for about 1 second.
For details on touchscreen gestures, see Section 4.5.5, "Touchscreen gestures",
on page 99.
Function keys provide access to the most common measurement settings and func-
tions.
A detailed description of the corresponding functions is provided in the User Manual.
Table 4-2: Function keys
[FREQ] Sets the center frequency and the start and stop frequencies for the fre-
quency range under consideration. This key is also used to set the fre-
quency offset and the signal track function.
[AMPT] Sets the reference level, the displayed dynamic range, the RF attenua-
tion and the unit for the level display.
Sets the level offset and the input impedance.
Activates the preamplifier (option RF Preamplifier, R&S FSW-B24).
[AUTO SET] Enables automatic settings for level, frequency or sweep type mode.
[SWEEP] Sets the sweep time and the number of measurement points.
Selects continuous measurement or single measurement.
[TRACE] Configures the measured data acquisition and the analysis of the mea-
surement data.
[TRIG] Sets the trigger mode, the trigger threshold, the trigger delay, and the
gate configuration in the case of gated sweep.
Marker functions
[MKR] Sets and positions the absolute and relative measurement markers
(markers and delta markers).
[PEAK SEARCH] Performs a peak search for active marker. If no marker is active, normal
marker 1 is activated and the peak search is performed for it.
The navigation controls include a rotary knob, navigation keys, and Undo / Redo keys.
They allow you to navigate within the display or within dialog boxes.
Navigating in tables
The easiest way to navigate within tables (both in result tables and configuration
tables) is to scroll through the entries with your finger on the touchscreen.
Rotary knob
Navigation keys
You can use the navigation keys as an alternative to the rotary knob to navigate
through dialog boxes, diagrams or tables.
Undo/redo keys
● [Undo] reverts the previous action, i.e. the state before the previous action is
retrieved.
The undo function is useful, for example, if you accidentally select a different mea-
surement. In this case, many settings are lost. However, if you press [Undo] imme-
diately afterwards, the previous state is retrieved, i.e. the previous measurement
and all settings.
● [Redo] repeats the previously reverted action, i.e. the most recent action is repea-
ted.
The [Undo] function is not available after a [Preset] or "Recall" operation. When you
use these functions, the history of previous actions is deleted.
4.3.1.5 Keypad
Alphanumeric keys Enter numbers and (special) characters in edit dialog boxes.
Sign key Changes the sign of a numeric parameter. For an alphanumeric parame-
ter, inserts a "-" at the cursor position.
Unit keys (GHz/-dBm MHz/ Adds the selected unit to the entered numeric value and complete the
dBm, kHz/dB and Hz/dB) entry.
For level entries (e.g. in dB) or dimensionless values, all units have the
value "1" as multiplying factor. Thus, they have the same function as an
Enter key.
[Esc] key Closes all kinds of dialog boxes, if the edit Mode is not active. Quits the
edit mode, if the edit mode is active. In dialog boxes that contain a "Can-
cel" button it activates that button.
For "Edit" dialog boxes the following mechanism is used:
● If data entry has been started, it retains the original value and
closes the dialog box.
● If data entry has not been started or has been completed, it closes
the dialog box.
Backspace key If an alphanumeric entry has already been started, this key deletes the
character to the left of the cursor.
Enter key ● Concludes the entry of dimensionless entries. The new value is
accepted.
● With other entries, this key can be used instead of the "Hz/dB" unit
key.
● In a dialog box, selects the default or focused element.
Use the female "TRIGGER INPUT" connector to input an external trigger or gate data.
Thus, you can control the measurement using an external signal. The voltage levels
can range from 0.5 V to 3.5 V. The default value is 1.4 V. The typical input impedance
is 10 kΩ.
Use the female BNC "TRIGGER INPUT / OUTPUT" connector to receive a second
external signal or to provide a signal to another device. The signal is TTL compatible
(0 V / 5 V). You control the connector usage in the "Trigger" settings ([TRIG] key).
The trigger output also controls signals by the frequency mask trigger available in
Real-Time mode.
The rear panel provides a third "TRIGGER INPUT / OUTPUT" connector, see Sec-
tion 4.3.2.12, "TRIGGER 3 INPUT/ OUTPUT", on page 59. (Not models
1312.8000Kxx)
For FSW85 models, the second trigger (female BNC "TRIGGER INPUT / OUTPUT"
connector) on the front panel is not available due to the second RF input connector
(see Section 4.3.1.7, "RF input 50 ohm", on page 50).
Provides RF input from a connected device under test (DUT) to the FSW, which is then
analyzed in an RF measurement. Connect the DUT to the "RF Input" connector on the
FSW after switching on the instrument. Disconnect the RF input before switching off
the instrument. Do not overload the input. For maximum allowed values, see the speci-
fications document.
The specific connector type depends on the instrument model:
● FSW26: APC 3.5 mm male (compatible with R&S SMA)
● FSW43: 2.92 mm male (compatible with R&S SMA)
● FSW50/67: 1.85 mm male (compatible with 2.4 mm)
● FSW85:
– Input 1: 1.00 mm RF input connector for frequencies up to 85 GHz (90 GHz
with option R&S FSW-B90G)
– Input 2: 1.85 mm RF input connector for frequencies up to 67 GHz
For models 1312.8000Kxx:
1.00 mm RF input connector for frequencies up to 85 GHz (90 GHz with option
R&S FSW-B90G)
For more information on connecting devices to this input, see Section 4.2.7, "Connect-
ing to RF coaxial connectors", on page 32.
See also Section 4.2.11, "Considerations for test setup", on page 36.
For FSW85 models, which have two input connectors, you must define which input
source is used for each measurement channel.
(See Section 7.2.2.1, "Radio frequency input", on page 364).
Connect external mixers to the "EXT MIXER LO OUT/IF IN" and "IF IN" female con-
nectors to increase the available frequency range. These connectors are optional and
only available with R&S FSW-B21.
If no external mixers are connected to the FSW, cover the two front connectors "LO
OUT / IF IN" and "IF IN" with the supplied SMA caps.
The "Analog Baseband" interface option provides four "Baseband input" BNC connec-
tors on the front panel of the FSW for analog I and Q signals.
(FSW85: two connectors)
The upper BNC connectors BASEBAND INPUT I and BASEBAND INPUT Q are used
to input:
● Single-ended signals
● The positive signal input for differential signals
● Input from active Rohde & Schwarz probes (see specifications document)
The lower BNC connectors Ī and Ǭ are used to input the negative signal for differential
signals.
FSW85
The FSW85 provides only two connectors; differential input is not supported.
All connectors have a fixed impedance of 50 Ω. Do not overload the input. For maxi-
mum allowed values, see the specifications document.
Since the Digital I/Q input and the Analog Baseband input use the same digital signal
path, both cannot be used simultaneously. When one is activated, established connec-
tions for the other are disconnected. When the second input is deactivated, connec-
tions to the first are re-established. This can cause a short delay in data transfer after
switching the input source.
Input via the "Analog Baseband" interface can be enabled in the I/Q Analyzer or in one
of the optional applications that process I/Q data (where available).
The noise source control female connector is used to provide the supply voltage for an
external noise source. For example, use it to measure the noise figure and gain of
amplifiers and frequency converting devices.
Conventional noise sources require a voltage of +28 V to be switched on and 0 V to be
switched off. The output supports a maximum load of 100 mA.
For smart noise sources, use the Lemosa Power sensor connector.
For details on noise source control, see "Noise Source Control" on page 470.
4.3.1.11 Probe
The FSW provides a connector for supply voltages of +15 V to -12 V and ground for
active probes and preamplifiers. A maximum current of 140 mA is available. This con-
nector is suitable as a power supply for high-impedance probes.
For details on configuring and using power sensors, see Section 7.2.3, "Power sen-
sors", on page 369.
The "Lemosa" female connector is used to connect Rohde & Schwarz power sensors,
but also smart noise sources. For a detailed list of supported sensors and smart noise
sources, see the specifications document.
For details on configuring and using power sensors, see Section 7.2.3, "Power sen-
sors", on page 369. For details on noise source control, see "Noise Source Control"
on page 470.
A smart noise source (SNS) provides its own ENR and uncertainty tables and a tem-
perature value from an internal measurement. Thus, accuracy is improved and less
configuration efforts are required compared to common noise sources.
Connect the smart noise source to the Lemosa "Power Sensor" connector on the FSW.
Then connect the SNS output to the DUT or the "RF Input" connector on the FSW.
When you connect a smart noise source, the FSW automatically loads its ENR table
and stores it for future measurements. The ENR table remains stored on the instru-
ment even after the noise source is disconnected. If the table already exists on the
FSW, the contents are updated, if necessary. The identification and setup procedure
after connecting the R&S FS-SNS can take up to 10 seconds.
For details on Rohde & Schwarz smart noise sources, see the product documentation.
4.3.1.13 USB
The front panel provides three female "USB" connectors ("USB-A") to connect devices
like a keyboard or a mouse. In addition, a memory stick can be connected to store and
reload instrument settings and measurement data.
The rear panel provides further "USB" connectors, including a male ("USB-B") connec-
tor. See Section 4.3.2.3, "USB", on page 56.
All USB connectors support standard 2.0.
You can use headphones to monitor demodulated audio frequencies in time domain
measurements acoustically.
Connect headphones equipped with a miniature jack plug to the "PHONES" female
connector. Set the output voltage using the "Volume" control to the right of the female
connector. The maximum output voltage (volume) is 1 V. If a headphone is plugged
into the instrument, the internal loudspeaker is automatically switched off.
The output provided to the "PHONES" connector is the same as the (video) output at
the IF/VIDEO/DEMOD OUTPUT connector.
See also "Using headphones" on page 19.
[SYSTEM] keys set the instrument to a predefined state, change basic settings, and
provide print and display functions.
A detailed description of the corresponding functions is provided in the User Manual.
Table 4-4: SYSTEM keys
This figure shows the rear panel view of the FSW. The individual elements are descri-
bed in more detail in the subsequent sections.
3
6
1 2
6 5 4 3
7 6 5 4 3 2
1 = Bandwidth extension options, with "IF WIDE OUTPUT" connector (option -B160/-B320-B512) and Digital
I/Q 40G Streaming Output QSFP+ connector (option B517/B1017)
2 = GPIB interface
3 = AUX PORT
4 = SYNC TRIGGER OUTPUT/INPUT
5 = DIGITAL BASEBAND INPUT/OUTPUT connectors (option B17)
6 = TRIGGER 3 INPUT/OUTPUT connector
7 = IF/VIDEO/DEMOD connector
1 2 3
1 2
The removable system hard drive contains all measurement data from the FSW, allow-
ing you to store the data securely in an external location.
An AC power supply connector and main power switch are located in a unit on the rear
panel of the instrument.
Main power switch function:
Position 1: The instrument can be started via the Power key on the front panel.
The (optional) OCXO reference frequency is warmed up.
Position O: The entire instrument is disconnected from the AC power supply.
For details, refer to "Connecting to power" on page 19 and Section 4.2.5, "Connecting
the AC power", on page 30.
4.3.2.3 USB
The rear panel provides four additional female "USB (USB-A)" connectors to connect
devices like a keyboard, a mouse or a memory stick (see also Section 4.3.1.13, "USB",
on page 53).
Furthermore, a male "USB DEVICE" connector ("USB-B") is provided, for example to
connect the FSW to a PC for remote control. (Not available for instruments with CPU
board 1206.3874.00 or higher.)
All USB connectors support standard 2.0.
4.3.2.4 LAN
The FSW is equipped with a 1 GBit Ethernet IEEE 802.3u network interface with Auto-
MDI(X) functionality. The assignment of the RJ-45 connector supports twisted-pair cat-
egory 5 UTP/STP cables in a star configuration (UTP stands for unshielded twisted
pair, and STP for shielded twisted pair).
For details, see Section 12, "Network operation and remote control", on page 819.
You can connect an external monitor or other display device to the FSW to provide an
enlarged display. Two different types of connectors are provided for this purpose:
● Display Port
● DVI (digital visual interface)
For details, see Section 4.2.10, "Connecting an external monitor", on page 34.
You can extend the signal analysis bandwidth of the FSW by a hardware option
(R&S FSW-B160/-B320/-B512/-B1200/-B2001/-B4001/-B8001 or R&S FSW-Uxxx).
The bandwidth extension allows for an output sample rate of up to 10 GHz and a linear
bandwidth up to:
● 160 MHz (with option B160/U160)
● 320 MHz (with option B320/U320)
● 512 MHz (with option B512/U512)
● 1200 MHz (with option B1200/U1200)
● 2001 MHz (with option B2001/U2001)
● 4001 MHz (with option B4001/U4001)
● 6001 MHz (with option B6001/U6001)
● 8001 MHz (with option B8001/U8001)
While the extension can be activated or deactivated manually in the FSW base unit
(I/Q Analyzer application), it is activated automatically in some applications that also
support I/Q data analysis. See the application-specific documentation for details.
The Digital I/Q 40G Streaming Output (QSFP+) connector is provided by the hardware
of any bandwidth extension option for 512 MHz or more.
If necessary, remove the metal cover from the connector on the rear panel of the FSW.
The output connector provides I/Q data streams with a sample rate of up to 600 MHz, if
the R&S FSW-B517 option is installed and active. With R&S FSW-B1017 installed, out-
put rates up to 1200 MHz are available.
Output is activated in the software ([INPUT/OUTPUT] key).
See the FSW I/Q Analyzer and I/Q Input User Manual for details.
The GPIB interface is in compliance with IEEE488 and SCPI. A computer for remote
control can be connected via this interface. To set up the connection, a shielded cable
is recommended.
For more details, refer to Section 12, "Network operation and remote control",
on page 819.
A 9-pole SUB-D male connector used to provide low-voltage TTL control signals (max.
5 V). The output signals can be used to control external devices.
The optional "DIGITAL BASEBAND" connectors allow you to provide digital I/Q data for
measurements with the FSW. Using the output connector you can provide RF input
from the FSW to a connected device as digital I/Q data. The digital input and output
connectors cannot be used simultaneously.
It is recommended that you use the R&S®SMU-Z6 (1415.0201.02) cable to connect
other devices to the Digital Baseband Interface of the FSW.
For high output rates, use the Digital I/Q 40G Streaming Output option (R&S FSW-
B517), see Section 4.3.2.7, "Digital I/Q 40G streaming output connector (R&S FSW-
B517/-B1017)", on page 57.
The additional female BNC "TRIGGER INPUT / OUTPUT" connector can be used to
receive a third external signal or to provide a signal to another device. The signal is
TTL compatible (0 V / 5 V). You can control the connector usage in the "Trigger" set-
tings ([TRIG] key).
The "Analog Baseband" interface option provides four "Baseband input" BNC connec-
tors on the front panel of the FSW for analog I and Q signals.
(FSW85: two connectors)
The upper BNC connectors BASEBAND INPUT I and BASEBAND INPUT Q are used
to input:
● Single-ended signals
● The positive signal input for differential signals
● Input from active Rohde & Schwarz probes (see specifications document)
The lower BNC connectors Ī and Ǭ are used to input the negative signal for differential
signals.
FSW85
The FSW85 provides only two connectors; differential input is not supported.
All connectors have a fixed impedance of 50 Ω. Do not overload the input. For maxi-
mum allowed values, see the specifications document.
Since the Digital I/Q input and the Analog Baseband input use the same digital signal
path, both cannot be used simultaneously. When one is activated, established connec-
tions for the other are disconnected. When the second input is deactivated, connec-
tions to the first are re-established. This can cause a short delay in data transfer after
switching the input source.
Input via the "Analog Baseband" interface can be enabled in the I/Q Analyzer or in one
of the optional applications that process I/Q data (where available).
The external generator control option provides an additional GPIB and an "AUX con-
trol" connector.
The GPIB connector can be used to connect the external generator to the FSW.
The 9-pole SUB-D female "AUX control" connector is required for TTL synchronization,
if supported by the generator.
For details on connecting an external generator, see "External generator connections"
on page 378.
The alignment signal source is required to align the connected oscilloscope and the
oscilloscope ADC for the optional 2 GHz bandwidth extension (R&S FSW-B2000).
For details, see the FSW I/Q Analyzer and I/Q Input User Manual.
The "REF INPUT" connectors are used to provide an external reference signal to the
FSW.
The "REF OUTPUT" connectors can be used to provide an external reference signal
(or the optional OCXO reference signal) from the FSW to other devices that are con-
nected to this instrument.
Various connectors are provided for different reference signals:
"REF INPUT" 1...50 MHz To provide an external reference signal on the FSW.
0...10 dBm
"REF OUTPUT" 1...50 MHz To provide the same external reference signal received by
the "REF INPUT 1...50 MHz" connector to another device,
0...10 dBm
when available.
"REF OUTPUT" 10 MHz To provide the internal reference signal from the FSW to
another device continuously.
10 dBm
Also used to provide OCXO reference signal to another
device.
"REF INPUT" 100 MHz / 1 GHz To provide an external reference signal on the FSW.
0...10 dBm
"REF OUTPUT" 100 MHz To provide a 100 MHz reference signal from the FSW to
another device.
6 dBm
"REF OUTPUT" 640 MHz To provide a 640 MHz reference signal from the FSW to
another device.
16 dBm
SYNC TRIGGER
The "SYNC TRIGGER" connector can also be used to synchronize the reference fre-
quency on several devices (see Section 4.3.2.10, "SYNC TRIGGER OUTPUT/INPUT",
on page 59).
This option generates a 10 MHz reference signal with a very precise frequency. If
installed, and if no external signal is used, this signal is used as an internal reference.
It can also be used to synchronize other connected devices via the "REF OUTPUT 10
MHz" connector.
Labeling in line with EN 50419 for disposal of electrical and electronic equipment after the prod-
uct has come to the end of its service life.
For more information, see "Disposing of electrical and electronic equipment" on page 1560.
4.3.2.21 Device ID
The unique device identifier is provided as a barcode sticker on the rear panel of the
FSW.
It consists of the device order number and a serial number.
The serial number is used to define the default instrument name, which is:
<Type><variant>-<serial_number>
For example, FSW8-123456.
The instrument name is required to establish a connection to the instrument in a LAN.
Prerequisites
● The instrument is set up, connected to the mains system, and started up as descri-
bed in Section 4.2, "Preparing for use", on page 27.
For these first measurements, you use the internal calibration signal, so you do not
need any additional signal source or instruments. Try out the following:
● Measuring a basic signal.........................................................................................64
● Displaying a spectrogram........................................................................................65
● Activating additional measurement channels..........................................................67
● Performing sequential measurements.................................................................... 70
● Setting and moving a marker.................................................................................. 71
● Displaying a marker peak list.................................................................................. 72
● Zooming into the display......................................................................................... 73
● Zooming into the display permanently.................................................................... 76
● Saving settings........................................................................................................79
● Printing and saving results...................................................................................... 80
We will start out by measuring a basic signal, using the internal calibration signal as
the input.
5. Tap the "Calibration Frequency RF" option. Leave the frequency at the default
64 MHz, with a narrowband spectrum.
The calibration signal is now sent to the RF input of the FSW. By default, a continu-
ous frequency sweep is performed, so that the spectrum of the calibration signal is
now displayed in the standard level versus frequency diagram.
In addition to the standard "level versus frequency" spectrum display, the FSW also
provides a spectrogram display of the measured data. A spectrogram shows how the
spectral density of a signal varies over time. The x-axis shows the frequency, the y-axis
shows the time. A third dimension, the power level, is indicated by different colors.
Thus you can see how the strength of the signal varies over time for different frequen-
cies.
3.
Drag the "Spectrogram" icon from the evaluation bar to the diagram area. The blue
area indicates that the new diagram would replace the previous spectrum display.
Since we do not want to replace the spectrum, drag the icon to the lower half of the
display to add an additional window instead.
4. Close the SmartGrid mode by tapping the "Close" icon at the top right corner of the
toolbar.
You see the spectrogram compared to the standard spectrum display. Since the
calibration signal does not change over time, the color of the frequency levels does
not change over time, i.e. vertically. The legend at the top of the spectrogram win-
dow describes the power levels the colors represent.
The FSW features multiple measurement channels, i.e. you can define several mea-
surement configurations in parallel and then switch between the channels automati-
cally to perform the measurements sequentially. We will demonstrate this feature by
activating additional measurement channels for a different frequency range, a zero
span measurement, and an I/Q analysis.
2. On the "New Channel" tab of the "Signal + Spectrum Mode" dialog box, tap "Spec-
trum".
Figure 4-13: Frequency spectrum of the calibration signal with a larger span
As the calibration signal does not vary over time, the level versus time diagram dis-
plays a straight line.
The "IQ Analyzer" channel displays the real and imaginary signal parts in separate
windows.
Although only one measurement can be performed at any one time, the measurements
configured in the active channels can be performed sequentially, that means: one after
the other, automatically, either once or continuously.
In Figure 4-17, the "Spectrum 2" measurement is currently active (indicated by the
"channel active" icon in the tab label).
Markers are useful to determine the position of particular effects in the trace. The most
common use is to determine a peak, which is the default setting when you activate a
marker. We will set a marker on the peak in our first Spectrum measurement.
1. In the "MultiView" tab, double-tap the "Spectrum" window (frequency sweep with
spectrogram display) to return to the "Spectrum" channel.
4. Press "RUN SINGLE" on the front panel to perform a single sweep so we have a
fixed trace to set a marker on.
6. Now you can move the marker by tapping and dragging it to a different position.
The current position is indicated by a dotted blue line. Notice how the position and
value change in the marker area of the diagram.
The marker peak list determines the frequencies and levels of peaks in the spectrum
automatically. We will display a marker peak list for the Spectrum 2 channel.
2. Press "RUN SINGLE" on the front panel to perform a single sweep for which we
will determine the peaks.
4. Drag the "Marker Peak List" icon from the evaluation bar to the lower half of the
display to add a new window for the peak list.
6. To obtain a more conclusive peak list that does not contain noise peaks, for exam-
ple, define a threshold that is higher than the noise floor:
a) Press [MKR] on the front panel.
b) Tap "Marker Config" in the "Marker" menu.
c) Tap the "Search" tab in the "Marker" dialog box.
d) In the "Threshold" field, enter -68 dBm.
e) Tap the "State" box for "Threshold" to activate its use.
Only peaks that are larger than -68 dBm will be included in the peak list.
The marker peak list displays the determined peaks that are above the defined
threshold.
To analyze the areas around the peak levels in more detail, we will zoom into the top 3
peaks.
2. Tap the diagram near the first peak and drag your finger to the opposite corner of
the zoom area. A white rectangle is displayed from the point where you tapped to
the current position.
When you remove your finger, the zoom area is enlarged in a second (sub-)win-
dow.
3. In Figure 4-20, the enlarged peak is represented by a very thick trace. This is due
to the insufficient number of sweep points. The missing sweep points for the
zoomed display are interpolated, which provides poor results. To optimize the
results, we will increase the number of sweep points from the default 1001 to
32001.
a) Press [Sweep] on the front panel.
b) Tap "Sweep Config" in the "Sweep" menu.
c) In the "Sweep Points" field, enter 32001.
d) Press RUN SINGLE on the front panel to perform a new sweep with the
increased number of sweep points.
4. Tap the "Multiple Zoom" icon in the toolbar again and define a zoom area around
markers M4, M5 and M6.
5. Tap the "Multiple Zoom" icon in the toolbar again and define a zoom area around
marker M8.
6. To increase the size of the third zoom window, drag the "splitter" between the win-
dows to the left or right or up or down.
The zoomed results from Section 4.4.7, "Zooming into the display", on page 73 were
only graphical changes to the display. Now we would like to change the measurement
settings such that the zoomed result is maintained permanently. We will demonstrate
this in the Spectrum channel.
4. Place two fingers on the diagram, to the left and right of the marker, and stretch
them apart.
5. When the area has the size you require, remove your fingers from the display.
The displayed span and the number of displayed sweep points is smaller than
before, all other measurement settings remain unchanged.
6. Tap the "Measurement Zoom" icon on the toolbar for a second or so.
A context menu with further options is displayed.
To restore the results of our measurements later, we will store the instrument settings
to a file.
2. Press the keyboard key on the front panel to display the on-screen keyboard, as
you will have to enter text in the next step.
3. In the "Save" dialog box, tap the "File Name" field and enter MyMultiViewSetup
using the external or onscreen keyboard.
Keep the default "File Type" setting "Instrument with all Channels" to store the con-
figuration of all channels.
4. Tap "Save".
The file MyMultiViewSetup.dfl is stored in the default directory C:/R_S/
instr/user.
3. In the "Load" dialog box, select the MyMultiViewSetup.dfl file in the default
directory C:/R_S/instr/user.
Finally, after a successful measurement, we will document our results. First we will
export the numeric trace data, then we will create a screenshot of the graphical display.
5. Enter the file name MyPeakResults using the external or onscreen keyboard.
The trace data is stored to MyPeakResults.DAT
2. In the "Save Hardcopy as Portable Network Graphics (PNG)" dialog box, enter a
file name, e.g. MyPeakDisplay.
The screenshot is stored to MyPeakDisplay.png.
Remote control
In addition to working with the FSW interactively, located directly at the instrument, it is
also possible to operate and control it from a remote PC. Various methods for remote
control are supported:
● Connecting the instrument to a (LAN) network
● Using the web browser interface in a LAN network
● Using the Windows Remote Desktop application in a LAN network
● Connecting a PC via the GPIB interface
How to configure the remote control interfaces is described in the FSW user manual.
The following figure shows a measurement diagram in Spectrum mode. All different
information areas are labeled. They are explained in more detail in the following sec-
tions.
1 2 3
5 4
● Channel bar.............................................................................................................83
● Window title bar.......................................................................................................87
● Marker information.................................................................................................. 88
● Frequency and span information in diagram footer.................................................89
● Instrument and status information...........................................................................89
● Error information..................................................................................................... 90
Using the FSW you can handle several different measurement tasks (channels) at the
same time, although they can only be performed asynchronously. For each channel, a
separate tab is displayed on the screen. To switch from one channel display to another,
simply select the corresponding tab.
If many tabs are displayed, select the tab selection list icon at the right end of the chan-
nel bar. Select the channel you want to switch to from the list.
MultiView tab
An additional tab labeled "MultiView" provides an overview of all active channels at a
glance. In the "MultiView" tab, each individual window contains its own channel bar
with an additional button. Tap this button, or double-tap in any window, to switch to the
corresponding channel display quickly.
"IQ" in the channel tab indicates that the results for the channel no longer match the
data currently in the capture buffer.
In MSRA mode, the results in an MSRA secondary application no longer match the
data captured by the MSRA primary application. The "IQ" disappears after you refresh
the results in the outdated application.
For applications using a long capture buffer, this icon appears if you switch channels.
The icon disappears after you switch back to the application and perform a new mea-
surement.
The icon indicates the currently active channel during an automatic measurement
sequence ("Sequencer" functionality).
Channel-specific settings
Beneath the channel name, information on channel-specific settings for the measure-
ment is displayed in the "channel bar". Channel information varies depending on the
active application.
In the Spectrum application, the FSW shows the following settings:
Table 4-6: Channel settings displayed in the channel bar in the Spectrum application
"ExtFE: Att" External frontend attenuation when measuring external frontend input.
"Meas Time"/"AQT" Measurement (acquisition) time, calculated from analysis bandwidth and
number of samples (for statistics measurements)
"Compatible" Compatible device mode (FSP, FSU, default; default not displayed)
Common settings
The channel bar above the diagram not only displays the channel-specific settings. It
also displays information on instrument settings that affect the measurement results
even though it is not immediately apparent from the display of the measured values.
This information is displayed in gray font and only when applicable for the current mea-
surement, as opposed to the channel-specific settings that are always displayed.
"Sweep Count" The current signal count for measurement tasks that involve a specific number of subse-
quent sweeps
(see "Sweep Count" setting in "Sweep settings" in the User Manual)
"PA"/"Ext PA" The preamplifier is activated. / Data compensation is performed using data from the
(optional) external preamplifier.
"GAT" The frequency sweep is controlled via the TRIGGER INPUT connector.
"ExtMix" An external mixer is activated for input (requires option R&S FSW-B21); the used band is
<band> also indicated
"Ext. Gen" The FSW is controlling an external generator (requires option R&S FSW-B10).
<"NOR" | "NOR": the measurements are normalized with the results of the external generator cali-
"APX"> bration
"APX" (approximation): the measurements are normalized with the results of the external
generator calibration; however, the measurement settings have been changed since cali-
bration
If neither label is displayed, no calibration has been performed yet or normalization is not
active.
For details, see Section 7.2.4, "Optional external generator control", on page 377.
"Inp:ExtFe" An external frontend is active (requires option R&S FSW-K553); the used frequency
"IF High" / "IF band configuration is indicated for reference.
Low" / "Spur See "Frequency Band Configuration" on page 454.
optimized" /
"EVM opti-
mized" / <IF
frequency
range> /
"Shared LO"
"IFCorr" IF cable correction for an active external frontend is enabled and a valid correction file is
available.
"LVL" A level offset is applied to the external generator signal (only if external generator control
is active).
"Inp: Input 2" For FSW85 models with two RF input connectors only: the second input connector "RF2"
is the current input source for the channel
"B2000" A connected oscilloscope is being used to acquire data with up to 2 GHz bandwidth
(requires bandwidth extension option R&S FSW-B2000)
"B5000" A connected oscilloscope is being used to acquire data with up to 5 GHz bandwidth
(requires bandwidth extension option R&S FSW-B5000)
Remote command:
INSTrument:REName on page 905
Each channel in the FSW display can contain several windows. Each window can dis-
play either a graph or a table as a result of the channel measurement. Which type of
result evaluation is displayed in which window is defined in the display configuration
(see Section 4.5.6, "Displaying results", on page 102). The window title bar indicates
which type of evaluation is displayed.
Double-tap the window title bar to enlarge the window temporarily. Double-tap it again
to restore the original size.
See also Section 4.5.6.4, "Switching between a split and maximized window display",
on page 108.
1 2 3 4 5
AP AUTOPEAK detector
Sa SAMPLE detector
Av AVERAGE detector
Rm RMS detector
QP QUASIPEAK detector
Clrw CLEAR/WRITE
View VIEW
Marker information is provided either in the diagram grid or in a separate marker table,
depending on the configuration.
Type Marker type: N (normal), D (delta), T (temporary, internal), PWR (power sensor)
The information in the diagram footer (beneath the diagram) depends on the current
application, measurement, and result display.
For a default measurement in the "Spectrum" mode, the "Diagram" result display con-
tains the following information, for example:
Table 4-8: Frequency domain display
Label Information
Pts Number of sweep points or (rounded) number of currently displayed points in zoom
mode
Label Information
CF Center frequency
Pts Number of sweep points or (rounded) number of currently displayed points in zoom
mode
Global instrument settings and functions, the instrument status and any irregularities
are indicated in the status bar beneath the diagram.
In the MultiView tab, the status bar always displays the information for the currently
selected measurement.
The following information is displayed:
Instrument status
The optional Digital Baseband Interface (R&S FSW-B17) is being used for digital
input
For details on the Digital Baseband Interface (R&S FSW-B17), see the FSW I/Q Ana-
lyzer User Manual.
The optional Digital Baseband Interface (R&S FSW-B17) is being used to provide
digital output.
For details on the Digital Baseband Interface (R&S FSW-B17), see the FSW I/Q Ana-
lyzer User Manual.
The optional Digital I/Q 40G Streaming Output Connector (R&S FSW-B517) is being
IQ 40G
used to provide digital output.
For details on the Digital I/Q 40G Streaming Output Connector, see the FSW I/Q
Analyzer User Manual.
Progress
The progress of the current operation is displayed in the status bar.
In the MultiView tab, the progress bar indicates the status of the currently selected
measurement, not the measurement a Sequencer is currently performing, for example.
Depending on the type of message, the status message is indicated in varying colors.
Table 4-10: Status bar information - color coding
Red Error An error occurred at the start or during a measurement, e.g. due to missing
data or wrong settings, so that the measurement cannot be started or com-
pleted correctly.
Orange Warning An irregular situation occurred during measurement, e.g. the settings no lon-
ger match the displayed results, or the connection to an external device was
interrupted temporarily.
Green Measurement Some applications visualize that the measurement was successful by show-
successful ing a message.
You can operate all instrument functions using this user interface.
For most tasks, there are at least 2 alternative methods to perform them:
● Using the touchscreen
● Using other elements provided by the front panel, e.g. the keypad, rotary knob, or
arrow and position keys.
The measurement and instrument functions and settings can be accessed by selecting
one of the following elements:
● System and function keys on the front panel of the instrument
● Softkeys on the touchscreen
● Context menus for specific elements on the touchscreen
● Icons on the tool bar in the touchscreen
● Displayed setting on the touchscreen
4.5.2.1 Toolbar
Standard functions can be performed via the icons in the toolbar at thetop of the
screen.
You can hide the toolbar display, e.g. when using remote control, to enlarge the display
area for the measurement results ("Setup > Display > Displayed Items"). See the FSW
User Manual for details.
Icon Description
Icon Description
Report Menu:
Displays the "Report" menu to configure a report.
See Section 10.6, "Working with test reports", on page 712.
Selection mode: the cursor can be used to select (and move) markers in a zoomed display
(This function is only available and required for older instruments that do not support multi-touch
gestures.)
Multiple (graphical) zoom mode: applies to the next display you select;
Allows you to enlarge several different areas of the trace simultaneously.
Displays a dotted rectangle in the diagram that can be expanded to define the zoom area; a
subwindow is added to display an enlarged extract of the trace
This function changes the behavior of finger gestures such as dragging or stretching a finger
(see also "Touch gestures in diagrams change measurement settings" on page 101)
Icon Description
Data shift: Shifts the data to be evaluated in the result display and re-evaluates the new data.
Currently, this function is only available in the Transient Analysis application.
Data zoom: Decreases the amount of data to be evaluated in the result display and re-evaluates
the new data, thus enlarging the display of the remaining data.
Currently, this function is only available in the Transient Analysis application.
Event based actions manager: opens a dialog to configure actions based on specific events
For details see Section 8.7, "Event-based actions", on page 662.
Application starter: opens a dialog to start an external application directly from the FSW firm-
ware.
For details see Section 11.3, "Application starter", on page 751.
To return to the FSW window, use the [Alt]+[Tab] keys.
Help (+ Select): allows you to select an object for which context-specific help is displayed
Report New: Deletes all currently stored datasets and creates a new one.
See Section 10.6, "Working with test reports", on page 712.
Report Append: Adds a new dataset to the existing ones for the next test report.
See Section 10.6, "Working with test reports", on page 712.
4.5.2.2 Softkeys
Softkeys are virtual keys provided by the software. Thus, more functions can be provi-
ded than those that can be accessed directly via the function keys on the instrument.
Softkeys are dynamic, i.e. depending on the selected function key, a different list of
softkeys is displayed on the right side of the screen.
A list of softkeys for a certain function key is also called a menu. Softkeys can either
perform a specific function or open a dialog box.
The "More" softkey indicates that the menu contains more softkeys than can be dis-
played at once on the screen. When pressed, it displays the next set of softkeys.
Color Meaning
Blue Associated function is active; for toggle keys: currently active state
Gray Instrument function is temporarily not available due to a specific setting or missing option
You can hide the softkey display, e.g. when using remote control, to enlarge the display
area for the measurement results ("Setup > Display > Displayed Items"). See the User
Manual for details.
Several items in the diagram area have context menus, such as traces, markers, soft-
keys, or settings in the channel bar. If you right-click on one of these items (or tap it for
about 1 second), a menu is displayed with context-specific menu items for the selected
item.
If SCPI Recording is available, the context menu contains a link to the SCPI recorder
functions and a link to a help topic for the specific item.
For details, see Section 12.5.1, "The context-sensitive SCPI command menu",
on page 842.
Figure 4-26: Context menu for a result display with SCPI Recorder functions
If SCPI Recorder functions are not available, for example for channel bar settings or in
some applications, the context menu contains functions for the selected item. These
functions correspond to the functions also provided for the item in softkey menus. This
is useful, for example, when the softkey display is hidden.
The on-screen keyboard is an additional means of interacting with the instrument with-
out having to connect an external keyboard.
The on-screen keyboard display can be switched on and off as desired using the "On-
Screen Keyboard" function key beneath the screen.
When you press this key, the display switches between the following options:
● Keyboard displayed at the top of the screen
● Keyboard displayed at the bottom of the screen
● No keyboard displayed
You can use the TAB key on the on-screen keyboard to move the focus from one field
to another in dialog boxes.
Any interaction using the keypad, scrollbar or knobs always affects the currently
focused element in the display, e.g. a dialog field, diagram, or table row. The currently
focused element is indicated by a blue frame (diagram, window, table) or is otherwise
highlighted (softkey, marker etc.). To move the focus, select the element on the touch-
screen.
To move the focus between any displayed diagrams or tables in a window, press
"Change focus" on the front panel. The focus moves from the diagram to the first table
to the next table etc. and then back to the diagram, within the same window.
In fullscreen mode, where a single window is displayed in full size on the screen, this
key switches the focus (and the display) from one active window to the next.
You can enter data in dialog boxes using any of the following methods:
● Using the touchscreen, via the on-screen keyboard
● Using other elements provided by the front panel, e.g. the keypad, rotary knob, or
navigation keys
The rotary knob acts like the [ENTER] key when it is pressed.
● Using a connected external keyboard
(The title bar of the dialog box is always slightly transparent and is not affected by the
slider.)
1. Enter the parameter value using the keypad, or change the currently used parame-
ter value by using the rotary knob (small steps) or the [UP] or [DOWN] keys (large
steps).
2. After entering the numeric value via keypad, press the corresponding unit key.
The unit is added to the entry.
3. If the parameter does not require a unit, confirm the entered value by pressing
[ENTER] or any of the unit keys.
The editing line is highlighted to confirm the entry.
1. In the input field for a numeric value, select the pencil icon to switch to extended
data entry mode.
2. Use the left and right arrow keys to scroll through the individual digits of the indica-
ted value.
3. Change the required digit using the up and down arrow keys or the rotary knob to
scroll through the values 0 to 9.
The new value is applied immediately, without further confirmation.
Note:
● If you enter a digit using the keypad, the entire value is overwritten, as in nor-
mal data entry mode.
● To add a digit to the existing value, you must return to normal data entry mode.
Select the pencil icon to toggle between entry modes.
4. To change the unit:
a) Press the right arrow key and scroll past the last digit to select the unit list.
b) Use the up and down arrow keys to scroll through the available units.
c) Press the left arrow key to return to the last digit of the numeric value.
The new unit is applied immediately, without further confirmation.
If a field requires alphanumeric input, you can use the on-screen keyboard to enter
numbers and (special) characters (see Section 4.5.2.4, "On-screen keyboard",
on page 95).
Alternatively, you can use the keypad. Every alphanumeric key represents several
characters and one number. The decimal point key (.) represents special characters,
and the sign key (-) toggles between capital and small letters. For the assignment,
refer to Table 4-12.
You can change the default behavior of the keypad for text input. This is useful if you
frequently enter numeric values in text fields, for example to define file names consist-
ing of numbers.
For details, see "Number block behavior" on page 795.
3. To choose another value provided by this key, press the key again, until your
desired value is displayed.
4. With every key stroke, the next possible value of this key is displayed. If all possi-
ble values have been displayed, the series starts with the first value again. For
information on the series, refer to Table 4-12.
5. To change from capital to small letters and vice versa, press the sign key (-).
6. When you have chosen the desired value, wait for 2 seconds (to use the same key
again), or start the next entry by pressing another key.
To enter a blank
► Press the "Space" bar, or press "0" and wait 2 seconds.
To correct an entry
1. Using the arrow keys, move the cursor to the right of the entry you want to delete.
2. Press [BACKSPACE].
The entry to the left of the cursor is deleted.
7 7µΩ°€¥$¢
8 A B C 8 Ä ÆÅ Ç
9 DEF9É
4 GHI4
5 JKL5
6 MNO6ŇÖ
1 PQRS1
2 TUV2Ü
3 WXYZ3
. .*:_,;"'?()#
A touchscreen allows you to interact with the software using various finger gestures on
the screen. The basic gestures supported by the software and most applications are
described here. Further actions using the same gestures may be possible.
Tapping
Touch the screen quickly, usually on a specific element.
You can tap most elements on the screen; in particular, any elements you can also
click on with a mouse pointer.
Double-tapping
Tap the screen twice, in quick succession.
Double-tap a diagram or the window title bar to maximize a window in the display, or to
restore the original size.
Dragging
Move your finger from one position to another on the display, keeping your finger on
the display the whole time.
By dragging your finger over a table or diagram you can pan the displayed area of the
table or diagram to show results that were previously out of view.
For example:
● Dragging horizontally in a spectrum display changes the center frequency.
● Dragging vertically in a power vs frequency (spectrum) or power vs. time display
changes the reference level (for absolute scaling) or the min and max power val-
ues (for relative scaling).
● Dragging horizontally in a time domain display changes the trigger offset value (if
available, not in free run).
● Spreading or pinching a spectrum display changes the center frequency and span
(horizontal) or reference level and range (vertical), or a combination of these set-
tings (diagonal).
● Spreading or pinching a time domain display changes the sweep time and trigger
offset (horizontal) or reference level position and range (vertical), or a combination
of these settings (diagonal).
You can prevent the firmware from changing specific settings using the options in the
context menu for the measurement zoom icon. By default, the reference level is locked
and thus not changed automatically due to touch gestures.
(See "Measurement Zoom" on page 545).
Click Tap
Double-click Double-tap
Drag-&-drop (= click and hold, then drag and Touch, then drag and release
release)
In (graphical) Zoom mode only: dragging the bor- Touch, then drag and release
ders of the displayed rectangle to change its size
Example:
You can scroll through a long table in conventional mouse operation by clicking in the
table's scrollbar repeatedly. In touch operation, you would scroll through the table by
dragging the table up and down with your finger.
The FSW provides several instrument applications for different analysis tasks and dif-
ferent types of signals, e.g. 3G FDD, I/Q analysis or basic spectrum analysis. For each
application, a new measurement channel is created and displayed in a separate tab on
the screen.
The results of a measurement channel can be evaluated in many different ways, both
graphically and numerically. For each evaluation method the results are displayed in a
separate window in the tab.
The FSW allows you to configure the display to suit your specific requirements and
optimize analysis.
When you activate an application, a new measurement channel is created which deter-
mines the measurement settings for that application. The same application can be acti-
vated with different measurement settings by creating several channels for the same
2. In the "Mode" dialog box, select the required application on the "New Channel" tab.
A new tab is displayed for the new channel.
Remote command:
INSTrument:CREate[:NEW] on page 901/ INSTrument:CREate:DUPLicate
on page 901
2. Select [Mode].
3. In the "Mode" dialog box, select the new application to be displayed on the
"Replace Current Channel" tab.
The selected application is displayed in the current channel.
Remote command:
INSTrument:CREate:REPLace on page 902
Remote command:
INSTrument:DELete on page 902
Measurement results can be evaluated in many different ways, for example graphically,
as summary tables, statistical evaluations etc. Each type of evaluation is displayed in a
separate window in the channel tab. Up to 16 individual windows can be displayed per
channel (i.e. per tab). To arrange the diagrams and tables on the screen, the Rohde &
Schwarz SmartGrid function helps you find the target position simply and quickly.
Principally, the layout of the windows on the screen is based on an underlying grid, the
SmartGrid. However, the SmartGrid is dynamic and flexible, allowing for many different
layout possibilities. The SmartGrid functionality provides the following basic features:
● Windows can be arranged in columns or in rows, or in a combination of both.
● Windows can be arranged in up to four rows and four columns.
● Windows are moved simply by dragging them to a new position on the screen, pos-
sibly changing the layout of the other windows, as well.
● All evaluation methods available for the currently selected measurement are dis-
played as icons in the evaluation bar. If the evaluation bar contains more icons
than can be displayed at once on the screen, it can be scrolled vertically. The same
evaluation method can be displayed in multiple windows simultaneously.
● New windows are added by dragging an evaluation icon from the evaluation bar to
the screen. The position of each new window depends on where you drop the eval-
uation icon in relation to the existing windows.
● All display configuration actions are only possible in SmartGrid mode. When Smart-
Grid mode is activated, the evaluation bar replaces the current softkey menu dis-
play. When the SmartGrid mode is deactivated again, the previous softkey menu
display is restored.
● Background information: the smartgrid principle...................................................105
● How to activate smartgrid mode............................................................................106
● How to add a new result window...........................................................................106
● How to close a result window................................................................................107
● How to arrange the result windows....................................................................... 107
SmartGrid display
During any positioning action, the underlying SmartGrid is displayed. Different colors
and frames indicate the possible new positions. The position in the SmartGrid where
you drop the window determines its position on the screen.
The brown area indicates the possible "drop area" for the window, i.e. the area in which
the window can be placed. A blue area indicates the (approximate) layout of the win-
dow as it would be if the icon were dropped at the current position. The frames indicate
the possible destinations of the new window with respect to the existing windows:
above/below, right/left or replacement (as illustrated in Figure 4-33). If an existing win-
dow would be replaced, the drop area is highlighted in a darker color shade.
1
A
B 2 3 2 3 2
C
1
SmartGrid functions
Once the evaluation icon has been dropped, icons in each window provide delete and
move functions.
The "Move" icon allows you to move the position of the window, possibly changing the
size and position of the other displayed windows.
The "Delete" icon allows you to close the window, enlarging the display of the remain-
ing windows.
To close the SmartGrid mode and restore the previous softkey menu, select the
"Close" icon, or press any key.
2. Select the icon for the required evaluation method from the evaluation bar.
If the evaluation bar contains more icons than can be displayed at once on the
screen, it can be scrolled vertically. Touch the evaluation bar between the icons
and move it up or down until the required icon appears.
3. Drag the required icon from the evaluation bar to the SmartGrid, which is displayed
in the diagram area, and drop it at the required position. (See "How to arrange the
result windows" on page 107 for more information on positioning the window).
Remote command:
LAYout:ADD[:WINDow]? on page 1103 / LAYout:WINDow<n>:ADD? on page 1107
► To close a window, activate SmartGrid mode and select the "Delete" icon for the
window.
Remote command:
LAYout:REMove[:WINDow] on page 1105 / LAYout:WINDow<n>:REMove
on page 1108
1. Select an icon from the evaluation bar or the "Move" icon for an existing evaluation
window.
Remote command:
LAYout:REPLace[:WINDow] on page 1105 / LAYout:WINDow<n>:REPLace
on page 1108
LAYout:MOVE[:WINDow] on page 1105
Each channel tab may contain several windows to evaluate the measurement results
using different methods. A "splitter" allows you to change the size of neighboring win-
dows.
► To change the size of two neighboring windows, drag the splitter between the win-
dows in either direction.
To get an overview of the results, displaying several windows at the same time may be
helpful. However, the individual windows may become rather small. In this case it is
useful to maximize an individual window to the entire screen temporarily in order to
analyze the results in more detail.
To switch between a split and a maximized display without having to close and re-open
windows, press [SPLIT/MAXIMIZE] on the front panel. In maximized display, the cur-
rently focused window is maximized. In split display, all active windows are displayed.
Alternatively, double-tap the title bar of a window to maximize it.
The display can be optimized for your individual needs. The following display functions
are available and are described in detail in Section 11.2, "Display settings",
on page 736 and Section 8, "Common analysis and display functions", on page 536.
● Displaying a simulation of the entire front panel of the instrument on the screen
("Front Panel")
● Displaying the main function hardkeys in a separate window on the screen ("Mini
Front Panel")
● Hiding or showing various screen elements
● Selecting a display theme and colors
● Changing the display update rate
● Activating or deactivating the touch-sensitivity of the screen
● Zooming into the diagram
If any questions or problems concerning the FSW arise, an extensive online help sys-
tem is provided on the instrument and can be consulted at any time. The help system
is context-sensitive and provides information specifically for the current operation or
setting to be performed. In addition, general topics provide an overview on complete
tasks or function groups as well as background information.
The online help can be opened at any time by selecting one of the "Help" icons on the
toolbar or by pressing [F1] on an external or the on-screen keyboard.
The "Help" dialog box "View" tab is displayed. A topic containing information about
the focused screen element is displayed.
If no context-specific help topic is available, a more general topic or the "Content"
tab is displayed.
For standard Windows dialog boxes (e.g. File Properties, Print dialog etc.), no context-
sensitive help is available.
Measurements
Depending on the task, the application can provide different measurement functions.
The measurement function determines which settings, functions and evaluation meth-
ods are available in the FSW. Only one measurement can be performed at the same
time within the same application instance. You select the measurement for an applica-
tion via the [MEAS] key.
In the Spectrum application, for example, the FSW provides a variety of different mea-
surement functions, including:
● Frequency sweep or zero span measurement
● Basic measurements - measure the spectrum of your signal or watch your signal
in time domain
● Power measurements - calculate the powers involved in modulated carrier signals
● Emission measurements - detect unwanted signal emission
● Statistic measurements - evaluate the spectral distribution of the signal
● Further measurements - provide characteristic values of the signal
● EMI measurements - detect electromagnetic interference in the signal
The individual functions are described in detail in Section 6, "Measurements and
results", on page 129.
The individual functions are described in detail in the FSW User Manual.
Operating modes
By default, each application operates independently of the others, measuring and ana-
lyzing its own distinct data. However, the FSW also provides other operating modes, in
which the individual applications are correlated and analyze the same set of data.
Remote command:
INST:MODE SAN, see INSTrument:MODE on page 904
Spectrogram application
Spectrogram measurements are not a separate application, but rather a trace evalua-
tion method, thus they are available as an evaluation method for the Display Configu-
ration, not by creating a new channel. Spectrograms are configured and activated in
the "Trace" settings. See Section 8.5.2.1, "Working with spectrograms", on page 631
for details.
Trial licenses
The trial license allows you to use further optional applications that require a separate
license from Rohde & Schwarz. It is pre-installed at the factory on request. If enabled,
you can use additional applications for a limited period of time (90 days from factory
installation).
Applications with trial licenses are indicated by a special tag:
Spectrum..................................................................................................................... 115
1xEV-DO BTS..............................................................................................................115
1xEV-DO MS............................................................................................................... 115
3G FDD BTS............................................................................................................... 116
3G FDD UE................................................................................................................. 116
5G NR..........................................................................................................................116
802.11ad......................................................................................................................116
802.11ay...................................................................................................................... 116
Amplifier.......................................................................................................................117
AM/FM/PM Modulation Analysis..................................................................................117
Avionics....................................................................................................................... 117
Bluetooth..................................................................................................................... 117
cdma2000 BTS............................................................................................................117
cdma2000 MS............................................................................................................. 118
Fast Spur Search.........................................................................................................118
(Multi-Carrier) Group Delay......................................................................................... 118
GSM............................................................................................................................ 118
HRP UWB....................................................................................................................118
I/Q Analyzer.................................................................................................................118
LTE.............................................................................................................................. 119
NB-IoT......................................................................................................................... 119
Noise Figure................................................................................................................ 119
OFDM Vector Signal Analysis (OFDM VSA)............................................................... 119
OneWeb...................................................................................................................... 119
Phase Noise................................................................................................................ 119
Pulse Measurements.................................................................................................. 120
Real-Time Spectrum................................................................................................... 120
TD-SCDMA BTS......................................................................................................... 120
TD-SCDMA UE........................................................................................................... 120
Transient Analysis....................................................................................................... 120
Verizon 5GTF Measurement Application (V5GTF)..................................................... 121
Vector Signal Analysis (VSA)...................................................................................... 121
WLAN..........................................................................................................................121
DOCSIS 3.1................................................................................................................ 121
Spectrum
In the Spectrum application the provided functions correspond to those of a conven-
tional spectrum analyzer. The analyzer measures the frequency spectrum of the RF
input signal over the selected frequency range with the selected resolution and sweep
time, or, for a fixed frequency, displays the waveform of the video signal. This applica-
tion is used in the initial configuration.
For details see Section 6, "Measurements and results", on page 129.
Remote command:
INST:SEL SAN, see INSTrument[:SELect] on page 905
1xEV-DO BTS
The 1xEV-DO BTS application requires an instrument equipped with the 1xEV-DO BTS
Measurements option, R&S FSW-K84. This application provides test measurements
for 1xEV-DO BTS downlink signals (base station signals) according to the test specifi-
cation.
For details see the R&S FSW-K84/-K85 User Manual.
For details see the R&S FSW-K84 User Manual.
Remote command:
INST:SEL BDO, see INSTrument[:SELect] on page 905
1xEV-DO MS
The 1xEV-DO MS application requires an instrument equipped with the 1xEV-DO MS
Measurements option, R&S FSW-K85. This application provides test measurements
for 1xEV-DO MS uplink signals (mobile signals) according to the test specification.
For details see the R&S FSW-K84/-K85 User Manual.
Remote command:
INST:SEL MDO, see INSTrument[:SELect] on page 905
3G FDD BTS
The 3G FDD BTS application requires an instrument equipped with the 3GPP Base
Station Measurements option, R&S FSW-K72. This application provides test measure-
ments for W-CDMA downlink signals (base station signals) according to the test speci-
fication.
For details see the R&S FSW-K72/-K73 User Manual.
For details see the R&S FSW-K72 User Manual.
Remote command:
INST:SEL BWCD, see INSTrument[:SELect] on page 905
3G FDD UE
The 3G FDD UE application requires an instrument equipped with the 3GPP User
Equipment Measurements option, R&S FSW-K73. This application provides test mea-
surements for W-CDMA uplink signals (mobile signals) according to the test specifica-
tion.
For details see the R&S FSW-K72/-K73 User Manual.
Remote command:
INST:SEL MWCD, see INSTrument[:SELect] on page 905
5G NR
The 5G NR application requires an instrument equipped with one of the 5G NR Mea-
surements options.
The R&S FSW-K144 application provides 5G NR measurements on the downlink.
The R&S FSW-K145 application provides 5G NR measurements on the uplink.
For details see the user manuals for the 5G NR downlink and uplink measurement
application.
Remote command:
INST:SEL NR5G, see INSTrument[:SELect] on page 905
802.11ad
The 802.11ad application requires an instrument equipped with the 802.11ad option,
R&S FSW-K95. This application provides measurements and evaluations according to
the IEEE 802.11 ad standard.
For details see the R&S FSW-K95/-K97 User Manual.
Remote command:
INST:SEL WIGIG, see INSTrument[:SELect] on page 905
802.11ay
The 802.11ay application requires an instrument equipped with the 802.11ay option,
R&S FSW-K97. This application provides measurements and evaluations according to
the IEEE 802.11 ay standard.
For details see the R&S FSW-K95/-K97 User Manual.
Remote command:
INST:SEL EDMG, see INSTrument[:SELect] on page 905
Amplifier
The Amplifier Measurement application requires an instrument equipped with the
Amplifier Measurement option R&S FSW-K18. This application provides measure-
ments to measure the efficiency of traditional amplifiers and amplifiers that support
envelope tracking with the FSW.
Also available is option R&S FSW-K18D, which provides direct DPD functionality.
For details see the R&S FSW-K18 User Manual (also contains information about
R&S FSW-K18D.
Remote command:
INST:SEL AMPL, see INSTrument[:SELect] on page 905
Avionics
The Avionics application requires an instrument equipped with the corresponding
optional software. This application provides measurement functions for measuring
avionics (ILS/VOR) signals.
For details see the R&S FSW-K15 User Manual.
Remote command:
INST:SEL AVIONICS, see INSTrument[:SELect] on page 905
Bluetooth
The Bluetooth application requires an instrument equipped with the Bluettooth Mea-
surements option R&S FSW-K8. This application provides Bluetooth measurements.
For details see the R&S FSW-K8 User Manual.
Remote command:
INST:SEL BTO, see INSTrument[:SELect] on page 905
cdma2000 BTS
The cdma2000 BTS application requires an instrument equipped with the cdma2000
BTS Measurements option, R&S FSW-K82. This application provides test measure-
ments for cdma2000 BTS downlink signals (base station signals) according to the test
specification.
For details see the R&S FSW-K82/-K83 User Manual.
For details see the R&S FSW-K82 User Manual.
Remote command:
INST:SEL BC2K, see INSTrument[:SELect] on page 905
cdma2000 MS
The cdma2000 MS application requires an instrument equipped with the cdma2000
MS Measurements option, R&S FSW-K83. This application provides test measure-
ments for cdma2000 MS uplink signals (mobile signals) according to the test specifica-
tion.
For details see the R&S FSW-K82/-K83 User Manual.
Remote command:
INST:SEL MC2K, see INSTrument[:SELect] on page 905
GSM
The GSM application requires an instrument equipped with the GSM Measurements
option R&S FSW-K10. This application provides GSM measurements.
For details see the R&S FSW-K10 User Manual.
Remote command:
INST:SEL GSM, see INSTrument[:SELect] on page 905
HRP UWB
The HRP UWB application requires an instrument equipped with the HRP UWB Mea-
surements option R&S FSW-K149. This application provides HRP UWB measure-
ments.
For details see the R&S FSW-K149 User Manual.
Remote command:
INST:SEL UWB, see INSTrument[:SELect] on page 905
I/Q Analyzer
The I/Q Analyzer application provides measurement and display functions for I/Q data.
For details see the R&S FSW I/Q Analyzer User Manual.
Remote command:
INST:SEL IQ, see INSTrument[:SELect] on page 905
LTE
The LTE application requires an instrument equipped with the LTE Measurements
option R&S FSW-K10x. This application provides LTE measurements.
For details see the user manuals for the LTE downlink and uplink measurement appli-
cation.
Remote command:
INST:SEL LTE, see INSTrument[:SELect] on page 905
NB-IoT
The NB-IoT application requires an instrument equipped with the NB-IoT measure-
ments option R&S FSW-K106. This application provides NB-IoT measurements in the
downlink.
For details see the R&S FSW-K106 (NB-IoT Downlink) User Manual.
Remote command:
INST:SEL NIOT, see INSTrument[:SELect] on page 905
Noise Figure
The Noise Figure application requires an instrument equipped with the Noise Figure
Measurements option R&S FSW-K30. This application provides noise figure measure-
ments.
For details see the R&S FSW-K30 User Manual.
Remote command:
INST:SEL NOISE, see INSTrument[:SELect] on page 905
OneWeb
The OneWeb application requires an instrument equipped with the OneWeb measure-
ments option R&S FSW-K201. This application provides OneWeb reverse link mea-
surements.
For details see the R&S FSW-K201 (OneWeb Reverse Link Measurements) User Man-
ual.
Remote command:
INST:SEL OWEB, see INSTrument[:SELect] on page 905
Phase Noise
The Phase Noise application requires an instrument equipped with the Phase Noise
Measurements option, R&S FSW-K40. This application provides measurements for
phase noise tests.
For details see the R&S FSW-K40 User Manual.
Remote command:
INST:SEL PNOISE, see INSTrument[:SELect] on page 905
Pulse Measurements
The Pulse application requires an instrument equipped with the Pulse Measurements
option, R&S FSW-K6. This application provides measurement functions for pulsed sig-
nals.
For details see the R&S FSW-K6 User Manual.
Remote command:
INST:SEL PULSE, see INSTrument[:SELect] on page 905
Real-Time Spectrum
The Real-Time Spectrum application requires an instrument equipped with the Real-
Time Spectrum option (R&S FSW-B160R/-K160RE/-U160R). This application provides
real-time measurement functions.
For details see the R&S FSW Real-Time User Manual.
Remote command:
INST:SEL RTIM, see INSTrument[:SELect] on page 905
TD-SCDMA BTS
The TD-SCDMA BTS application requires an instrument equipped with the TD-SCDMA
Base Station Measurements option, R&S FSW-K76. This application provides test
measurements for TD-SCDMA downlink signals (base station signals) according to the
test specification.
For details see the R&S FSW-K76/-K77 User Manual.
For details see the R&S FSW-K76 User Manual.
Remote command:
INST:SEL BTDS, see INSTrument[:SELect] on page 905
TD-SCDMA UE
The TD-SCDMA UE application requires an instrument equipped with the TD-SCDMA
User Equipment Measurements option, R&S FSW-K77. This application provides test
measurements for TD-SCDMA uplink signals (mobile signals) according to the test
specification.
For details see the R&S FSW-K76/-K77 User Manual.
Remote command:
INST:SEL MTDS, see INSTrument[:SELect] on page 905
Transient Analysis
The Transient Analysis application requires an instrument equipped with the Transient
Analysis option, R&S FSW-K60. This application provides measurements and evalua-
tions for Transient Analysis.
For details see the R&S FSW-K60 User Manual.
Remote command:
INST:SEL TA, see INSTrument[:SELect] on page 905
WLAN
The WLAN application requires an instrument equipped with the WLAN option,
R&S FSW-K91/91n. This application provides measurements and evaluations accord-
ing to the WLAN IEEE 802.11 standards.
For details see the R&S FSW-K91 User Manual.
Remote command:
INST:SEL WLAN, see INSTrument[:SELect] on page 905
DOCSIS 3.1
The DOCSIS 3.1 application requires an instrument equipped with the DOCSIS 3.1
option, R&S FSW-K192. This application provides measurements and evaluations
according to the DOCSIS 3.1 standard.
For details see the R&S FSW-K192 User Manual.
Remote command:
INST:SEL DOCS, see INSTrument[:SELect] on page 905
Remote command:
DISPlay:FORMat on page 1102
The default application in Signal and Spectrum Analyzer mode is a Spectrum measure-
ment.
Selecting an application
To start a new or replace an existing application, select the corresponding button in the
correct tab.
Note: The measurement channels are labeled with their default name. If that name
already exists, a sequential number is added. You can change the name of the mea-
surement channel by double-tapping the name in the channel bar and entering a new
name.
For an overview of default names see INSTrument:LIST? on page 902.
Remote command:
INSTrument[:SELect] on page 905
Remote command:
INSTrument:CREate[:NEW] on page 901
INSTrument[:SELect] on page 905
Closing an application
To close an application, simply close the corresponding tab by selecting the "x" next to
the channel name.
Remote command:
INSTrument:DELete on page 902
The Sequencer function is slightly different in MSRA or MSRT operating mode. For
details see the FSW MSRA User Manual or the FSW Real-Time Spectrum Application
and MSRT Operating Mode User Manual.
The instrument can only activate one specific channel at any time. Thus, only one
measurement can be performed at any time, namely the one in the currently active
channel. However, in order to perform the configured measurements consecutively, a
Sequencer function is provided, which changes the channel of the instrument as
Sequencer modes
Three different Sequencer modes are available:
● Single Sequence
Similar to single sweep mode; each measurement is performed once, until all mea-
surements in all defined "Channel"s have been performed.
● Continuous Sequence
Similar to continuous sweep mode; the measurements in each defined "Channel"
are performed one after the other, repeatedly, in the same order, until sequential
operation is stopped. This is the default Sequencer mode.
● Channel-defined Sequence
First, a single sequence is performed. Then, only "Channel"s in continuous sweep
mode are repeated continuously.
The "Single Sweep" and "Continuous Sweep"softkeys control the sweep mode for the
currently selected channel only; the sweep mode only has an effect the next time the
Sequencer activates that channel, and only for a channel-defined sequence. In this
case, a channel in single sweep mode is swept only once by the Sequencer. A channel
in continuous sweep mode is swept repeatedly.
Sequencer State
Activates or deactivates the Sequencer. If activated, sequential operation according to
the selected Sequencer mode is started immediately.
Remote command:
SYSTem:SEQuencer on page 908
INITiate:SEQuencer:IMMediate on page 907
INITiate:SEQuencer:ABORt on page 907
Sequencer Mode
Defines how often which measurements are performed. The currently selected mode
softkey is highlighted blue. During an active Sequencer process, the selected mode
softkey is highlighted orange.
"Single Sequence"
Each measurement is performed once, until all measurements in all
active channels have been performed.
"Continuous Sequence"
The measurements in each active channel are performed one after
the other, repeatedly, in the same order, until sequential operation is
stopped.
This is the default Sequencer mode.
"Channel Defined Sequence"
First, a single sequence is performed. Then, only channels in continu-
ous sweep mode are repeated.
Channel-defined sequence is not available in Multi-Standard Real-
Time (MSRT) operating mode.
Remote command:
INITiate:SEQuencer:MODE on page 907
4. To change the Sequencer mode and start a new sequence immediately, select the
corresponding mode softkey, or press the [Run Single] or [Run Cont] key.
The measurements configured in the currently active channels are performed one
after the other in the order of the tabs until the Sequencer is stopped.
The result displays in the individual channels are updated as the measurements
are performed.
Trial licenses
The trial license allows you to use further optional measurements that require a sepa-
rate license from Rohde & Schwarz. It is pre-installed at the factory on request. If
enabled, you can use additional measurements for a limited period of time (90 days
from factory installation).
Measurements with trial licenses are indicated by a special tag:
The measurement function determines which settings, functions and evaluation meth-
ods are available in the FSW. The various measurement functions are described in
detail here.
When you select a measurement function, the measurement is started with its default
settings immediately and the corresponding measurement configuration menu is dis-
played. The measurement configuration menu can be displayed at any time by press-
ing [MEAS CONFIG].
The easiest way to configure measurements is using the configuration "Overview", see
Section 7.1, "Configuration overview", on page 359.
In addition to the measurement-specific parameters, the general parameters can be
configured as usual, see Section 7, "Common measurement settings", on page 359.
● Basic measurements.............................................................................................130
● Channel power and adjacent-channel power (ACLR) measurement....................151
● Carrier-to-noise measurements............................................................................ 208
● Occupied bandwidth measurement (OBW)...........................................................212
● Noise power ratio (NPR) measurement................................................................ 218
● Spectrum emission mask (SEM) measurement....................................................235
● Spurious emissions measurement........................................................................ 281
● Statistical measurements (APD, CCDF)............................................................... 295
● Time domain power measurement........................................................................310
● Harmonic distortion measurement........................................................................ 315
● Third order intercept (TOI) measurement............................................................. 321
● AM modulation depth measurement..................................................................... 331
● Electromagnetic interference (EMI) measurement................................................334
Frequency Sweep
A common frequency sweep of the input signal over a specified span. Can be used for
general purposes to obtain basic measurement results such as peak levels and spec-
trum traces. The "Frequency" menu is displayed. This is the default measurement if no
other function is selected.
Various other measurements are based on the common frequency sweep, but require
additional configuration of sweep spans or amplitude limits, for example.
Examples for frequency sweep measurements are:
● Adjacent channel power (ACP)
● Carrier-to-noise (C/N)
● Occupied bandwidth (OBW)
● Noise power ratio (NPR)
● Spectrum emission mask (SEM)
● Spurious emissions
● Third order intercept (TOI)
● AM modulation depth
● Electromagnetic interference (EMI)
Use the general measurement settings to configure the measurement, e.g. via the
"Overview" (see Section 7, "Common measurement settings", on page 359).
Remote command:
[SENSe:]FREQuency:STARt on page 1198, [SENSe:]FREQuency:STOP
on page 1199
INITiate<n>[:IMMediate] on page 913
INITiate<n>:CONTinuous on page 912
Zero Span
A sweep in the time domain at the specified (center) frequency, i.e. the frequency span
is set to zero. The display shows the time on the x-axis and the signal level on the y-
axis, as on an oscilloscope. On the time axis, the grid lines correspond to 1/10 of the
current sweep time.
Use the general measurement settings to configure the measurement, e.g. via the
"Overview" (see Section 7, "Common measurement settings", on page 359).
Most result evaluations can also be used for zero span measurements, although some
functions (e.g. markers) may work slightly differently and some may not be available. If
so, this will be indicated in the function descriptions (see Section 8, "Common analysis
and display functions", on page 536).
Remote command:
[SENSe:]FREQuency:SPAN on page 1198
INITiate<n>[:IMMediate] on page 913
INITiate<n>:CONTinuous on page 912
The following step-by-step instructions demonstrate how to perform basic sweep mea-
surements.
For remote operation, see Section 13.16.1, "Programming example: performing a basic
frequency sweep", on page 1536.
4. If necessary, configure a trigger for the measurement ("Trigger/ Gate Config" dialog
box.
See Section 7.6, "Trigger and gate configuration", on page 510
5. Define how the results are evaluated for display ("Trace" dialog box, see Sec-
tion 8.5.1.2, "Trace settings", on page 624).
6. If necessary, configure the vertical axis of the display ("Amplitude" dialog box, see
Section 7.4, "Amplitude and vertical axis configuration", on page 481).
8. To repeat the same number of sweeps without deleting the last trace, select "Con-
tinue Single Sweep" in the "Sweep" menu.
One of the most common measurement tasks that can be handled using a signal ana-
lyzer is determining the level and frequency of a signal. When measuring an unknown
signal, you can usually start with the presettings.
Test setup
1. Configure the signal generator (e.g. R&S SMW):
● Frequency: 128 MHz
● Level: -30 dBm
2. NOTICE! Signal levels exceeding 30 dBm can damage the RF attenuator or the
input mixer. When calculating the expected power level, consider the total power of
all occuring signals.
If you measure signals higher than +30 dBm (=1 W), insert a power attenuator
before the RF input of the analyzer.
3. Connect the RF output of the signal generator to the RF input of the FSW.
The level and frequency of a sinusoidal signal can be measured easily using the
marker function. The FSW always displays its amplitude and frequency at the marker
position. The frequency measurement uncertainty is determined by the reference fre-
quency of the FSW, the resolution of the marker frequency display and the number of
sweep points.
2. Connect the signal to be measured to the "RF INPUT" connector on the FSW.
Note: Coupled settings. When the frequency span is defined, the resolution band-
width, the video bandwidth and the sweep time are automatically adjusted,
because these functions are defined as coupled functions in the presettings.
5. Select [MKR] to activate marker 1 and automatically set it to the maximum of the
trace.
The level and frequency values measured by the marker are displayed in the
marker information at the top of the display.
Note: Performing a peak search. When a marker is initially activated, it automati-
cally performs the peak search function (as shown in the example).
If a marker was already active, select [Peak Search] or the "Peak" softkey in the
[MKR >] menu in order to set the currently active marker to the maximum of the
displayed signal.
In the presettings, the value of the reference level is 0 dBm. If the input signal is
-30 dBm, the reference level can be reduced by 30 dB without causing the signal path
to be overloaded.
The built-in signal counter allows you to measure the frequency more accurately than
measuring it with the marker. The frequency sweep is stopped at the marker, and the
FSW measures the frequency of the signal at the marker position (see also Sec-
tion 8.3.4.1, "Precise frequency (signal count) marker", on page 568).
In the following example, the frequency of the generator at 128 MHz is shown using
the marker.
Prerequisite
Precise frequency measurements require a precise reference frequency. Therefore, an
external reference frequency from the signal generator is used. Connect the signal
generator's "Ref OUT" connector to the analyzer's "Ref IN" connector.
4. Select "Setup" > "Reference" > "External Reference 10 MHz" to activate the exter-
nal reference frequency.
5. Select [MKR] to activate marker 1 and automatically set it to the maximum of the
trace.
The level and the frequency of the marker are displayed in the marker results in the
diagram or the marker table.
6. Select [MKR FUNC] > "Signal Count" to activate the signal counter.
The result of the signal counter is displayed in the marker results.
The minimum signal level a signal analyzer can measure is limited by its intrinsic noise.
Small signals can be swamped by noise and therefore cannot be measured. For sig-
nals that are just above the intrinsic noise, the accuracy of the level measurement is
influenced by the intrinsic noise of the FSW.
The displayed noise level of a signal analyzer depends on its noise figure, the selected
RF attenuation, the selected reference level, the selected resolution and video band-
width and the detector.
For details see:
● Section 7.4.1.2, "RF attenuation", on page 482
● Section 7.4.1.1, "Reference level", on page 481
● Section 7.5.1.1, "Separating signals by selecting an appropriate resolution band-
width", on page 494
● Section 7.5.1.2, "Smoothing the trace using the video bandwidth", on page 495
● "Mapping samples to sweep points with the trace detector" on page 611
This measurement example shows the different factors influencing the S/N ratio.
Table 6-1: Signal generator settings (e.g. R&S SMW)
5. To suppress noise spikes, average the trace. In the "Traces" configuration dialog,
set the "Trace Mode" to "Average" (see "Trace Mode" on page 625).
The traces of consecutive sweeps are averaged. To perform averaging, the FSW
automatically switches on the sample detector. The RF signal, therefore, can be
more clearly distinguished from noise.
Figure 6-2: RF sine wave signal with low S/N ratio with an averaged trace
6. Instead of trace averaging, you can select a video filter that is narrower than the
resolution bandwidth. Set the trace mode back to "Clear/ Write", then set the VBW
to 10 kHz manually in the "Bandwidth" configuration dialog.
The RF signal can be distinguished from noise more clearly.
Figure 6-3: RF sine wave signal with low S/N ratio with a smaller video bandwidth
A basic feature of a Signal and Spectrum Analyzer is the ability to separate the spec-
tral components of a mixture of signals. The resolution at which the individual compo-
nents can be separated is determined by the resolution bandwidth. Selecting a resolu-
tion bandwidth that is too large may make it impossible to distinguish between spectral
components, i.e. they are displayed as a single component (see also Section 7.5.1.1,
"Separating signals by selecting an appropriate resolution bandwidth", on page 494).
Two signals with the same amplitude can be resolved if the resolution bandwidth is
smaller than or equal to the frequency spacing of the signal. If the resolution bandwidth
is equal to the frequency spacing, the spectrum display shows a level drop of 3 dB pre-
cisely in the center of the two signals. Decreasing the resolution bandwidth makes the
level drop larger, which thus makes the individual signals clearer.
In this measurement example we will analyze two signals with a level of -30 dBm each
and a frequency spacing of 30 kHz.
Level Frequency
4. Set the resolution bandwidth to 30 kHz and the video bandwidth to 1 kHz.
Note: Larger video bandwidths. The video bandwidth is set to 1 kHz in order to
make the level drop in the center of the two signals clearly visible. At larger video
bandwidths, the video voltage that results from envelope detection is not suffi-
ciently suppressed. This produces additional voltages, which are visible in the
trace, in the transition area between the two signals.
Figure 6-6: Measurement of two equally-leveled RF sinusoidal signals with the resolution band-
width which corresponds to the frequency spacing of the signals
Figure 6-7: Measurement of two equally-leveled RF sinusoidal signals with a resolution band-
width which is larger than their frequency spacing
Figure 6-8: Measurement of two equally-leveled RF sinusoidal signals with a resolution band-
width (1 kHz) which is significantly smaller than their frequency spacing
In the frequency range display, the AM side bands can be resolved with a narrow
bandwidth and measured separately. The modulation depth of a carrier modulated with
a sinusoidal signal can then be measured. Since the dynamic range of a signal ana-
lyzer is very large, extremely small modulation depths can also be measured precisely.
For this purpose, the FSW provides measurement routines that output the modulation
depth numerically in percent directly.
4. Select [MEAS] > "AM Modulation Depth" to activate the modulation depth mea-
surement.
The FSW automatically sets a marker to the carrier signal in the center of the dia-
gram and one delta marker each to the upper and lower AM sidebands. The FSW
calculates the AM modulation depth from the level differences of the delta markers
to the main marker and outputs the numeric value in the marker information.
The modulation depth is displayed as "MDepth". The frequency of the AF signal can be
obtained from the frequency display of the delta marker.
The FSW rectifies the RF input signal (that is, removes the negative parts) and dis-
plays it as a magnitude spectrum. The rectification also demodulates AM-modulated
signals. The AF voltage can be displayed in zero span if the modulation sidebands fall
within the resolution bandwidth.
Displaying the AF of an AM-modulated signal (Zero Span)
6. Set the reference level to -24 dBm and the display range to linear ([AMPT] > "Scale
Config" > "Scaling": "Linear Percent").
7. Set the scaling unit to Volt ([AMPT] > "Amplitude Config" > "Unit": "V").
8. Define triggering in response to the AF signal using the video trigger to produce a
static image.
a) Press [TRIG].
b) Select "Video".
c) Set the "Trg/Gate Level" to 50%.
The trigger level is displayed as a horizontal line across the entire measurement
diagram. The FSW displays the 1 kHz AF signal as a static image in zero span.
Figure 6-12: Measurement of the AF signal of a carrier that is AM-modulated with 1 kHz
For radio transmission systems that use the TDMA method (for example, GSM), trans-
mission quality is determined not only by spectral characteristics but also by character-
istics in zero span. A timeslot is assigned to each user since several users share the
same frequency. Smooth operation is ensured only if all users adhere exactly to their
assigned timeslots.
Both the power during the send phase as well as the timing and duration of the TDMA
burst, and rise and fall times of the burst, are important.
● Measuring the power characteristic of burst signals............................................. 145
● Measuring the signal-to-noise ratio of burst signals..............................................149
To measure power in zero span, the FSW offers easy-to-use functions that measure
the power over a predefined time.
Level 0 dBm
4. Set the reference level to 10 dBm (= level of the signal generator +10 dB) (AMPT).
8. Using the video trigger, set triggering on the rising edge of the burst.
a) Press [TRIG].
b) Set the "Trg Source" to "Video".
c) Set the "Trg/Gate Level" to 70%.
The FSW shows a static image with the GSM burst at the start of the trace. The
trigger level is displayed as a horizontal line labeled with the absolute level for the
trigger threshold in the measurement diagram.
9. Activate power measurement within the activation phase of the burst in zero span.
a) Press [MEAS].
b) Select "Time Domain Power".
c) Select "Time Dom Power Config".
d) Set the "Limits" state to "On".
e) Select the "Left Limit" input field.
f) By turning the rotary knob clockwise, move the vertical line "S1" to the start of
the burst.
g) Select the "Right Limit" input field.
h) By turning the rotary knob clockwise, move the vertical line "S2" to the end of
the burst.
The FSW displays the average (mean) power during the activation phase of the
burst.
Figure 6-14: Measurement of the average power during the burst of a GSM signal
Level 0 dBm
The measurement is based on the example "Measuring the power of a GSM burst dur-
ing the activation phase" on page 146.
1. Switch off the power measurement.
a) Press [MEAS].
2. Increase the time resolution by setting the sweep time to 100 µs ([SWEEP] >
"Sweep Time Manual").
3. Shift the rising edge of the GSM burst to the center of the display by defining a trig-
ger offset.
a) Press [TRIG].
b) Select "Trigger Offset".
c) By turning the rotary knob counterclockwise, reduce the trigger offset until the
burst edge is displayed in the center of the display, or enter -50 µs.
The FSW displays the rising edge of the GSM burst.
Figure 6-16: Rising edge of the GSM burst displayed with high time resolution
4. Move the falling edge of the burst to the center of the display. To do so, switch the
trigger "Slope" to "Falling" ([TRIG] > "Trigger/ Gate Config").
The FSW displays the falling edge of the GSM burst.
Figure 6-17: Falling edge of the GSM burst displayed with high time resolution
When TDMA transmission methods are used, the signal-to-noise ratio or the dynamic
range for deactivation can be measured by comparing the power values during the
activation phase and the deactivation phase of the transmission burst. Therefore, the
FSW provides a measurement for absolute and relative power in zero span. In the fol-
lowing example, the measurement is performed using a GSM burst.
Signal-to-Noise Ratio of a GSM Signal
Level 0 dBm
7. Use the trigger source "Video" and the trigger slope "Rising" to trigger on the rising
edge of the burst and shift the start of the burst to the center of the display (see
step 3 in "Measuring the edges of a GSM burst with high time resolution"
on page 147).
8. Activate power measurement within the activation phase of the burst in zero span.
a) Press [MEAS].
b) Select "Time Domain Power".
c) Select "Time Dom Power Config".
d) Set the "Limits" state to "On".
e) Select the "Left Limit" input field.
f) By turning the rotary knob clockwise, move the vertical line "S1" to the start of
the burst.
g) Select the "Right Limit" input field.
h) By turning the rotary knob clockwise, move the vertical line "S2" to the end of
the burst.
i) Note down the power result for the burst, indicated by the "TD Pow RMS" result
in the marker table.
9. Measure the power during the deactivation phase of the burst by switching the trig-
ger slope to "Falling" ([TRIG] > "Trigger/ Gate Config").
The FSW initiates triggering in response to the falling edge of the burst. This shifts
the burst to the left-hand side of the measurement diagram. The power is mea-
sured in the deactivation phase.
Figure 6-19: Measurement of the signal-to-noise ratio of a GSM burst signal in zero span
10. Note down the power result for the measured noise, indicated by the "TD Pow
RMS" result in the marker table.
Subtract the measured noise power from the burst power to obtain the signal-to-
noise ratio of the burst signal.
Measuring channel power and adjacent channel power is one of the most important
tasks during signal analysis with the necessary test routines in the field of digital trans-
mission. Theoretically, a power meter could be used to measure channel power at
highest accuracy. However, its low selectivity means that it is not suitable for measur-
ing adjacent channel power as an absolute value or relative to the transmit channel
power. Only a selective power meter can measure the power in the adjacent channels.
A signal analyzer cannot be classified as a true power meter, because it displays the IF
envelope voltage. However, it is calibrated such as to display the power of a pure sine
wave signal correctly, irrespective of the selected detector. This calibration cannot be
applied for non-sinusoidal signals. Assuming that the digitally modulated signal has a
Gaussian amplitude distribution, the signal power within the selected resolution band-
width can be obtained using correction factors. The internal power measurement rou-
tines in a signal analyzer normally use these correction factors to determine the signal
power from IF envelope measurements. These factors apply if and only if the assump-
tion of a Gaussian amplitude distribution is correct.
Apart from this common method, the FSW also has a true power detector, i.e. an RMS
detector. It displays the power of the test signal within the selected resolution band-
width correctly, irrespective of the amplitude distribution, without additional correction
factors being required.
The FSW software allows you to perform ACLR measurements on input containing
multiple signals for different communication standards. A measurement standard is
provided that allows you to define multiple discontiguous transmit channels at specified
frequencies, independent from the selected center frequency. The ACLR measurement
determines the power levels of the individual transmit, adjacent, and gap channels, as
well as the total power for each sub block of transmit channels.
A detailed measurement example is provided in Section 6.2.7, "Measurement exam-
ples", on page 199.
Results are provided for the TX channel and the number of defined adjacent channels
above and below the TX channel. If more than one TX channel is defined, you must
specify the channel to which the relative adjacent-channel power values refer. By
default, it is the TX channel with the maximum power.
0 Channel powers
1 ● Channel powers
● Power of the upper and lower adjacent channel
2 ● Channel powers
● Power of the upper and lower adjacent channel
● Power of the next higher and lower channel (alternate channel 1)
3 ● Channel powers
● Power of the upper and lower adjacent channel
● Power of the next higher and lower channel (alternate channel 1)
● Power of the second next higher and lower adjacent channel (alternate channel 2)
… …
12 ● Channel powers
● Power of the upper and lower adjacent channel
● Power of all the higher and lower channels (alternate channels 1 to 11)
In the FSW display, only the first neighboring channel of the carrier (TX) channel is
labeled "Adj" (adjacent) channel; all others are labeled "Alt" (alternate) channels. In this
manual, "Adjacent" refers to both adjacent and alternate channels.
The measured power values for the TX and adjacent channels are also output as a
table in the Result Summary window. Which powers are measured depends on the
number of configured channels.
For each channel, the following values are displayed:
Label Description
Channel Channel name as specified in the "Channel Settings" (see "Channel Names"
on page 177).
Offset Offset of the channel to the TX channel (configured channel spacing, see "Channel
Bandwidth" on page 174)
Power The measured power values for the TX and lower and upper adjacent channels. The
powers of the transmission channels are output in dBm or dBm/Hz, or in dBc, relative
(Lower/Upper)
to the specified reference TX channel.
this case, the measured power value for each sweep point (by default 1001) is
returned.
For a full list of remote commands for ACLR measurements, see Section 13.5.3.10,
"Retrieving and analyzing measurement results", on page 971.
Some background knowledge on basic terms and principles used in channel power
measurements is provided here for a better understanding of the required configuration
settings.
● Measurement methods......................................................................................... 154
● Measurement repeatability....................................................................................156
● Recommended common measurement parameters.............................................157
● Measurement on multi-standard radio (MSR) signals...........................................161
The channel power is defined as the integration of the power across the channel band-
width.
The Adjacent Channel Leakage Power Ratio (ACLR) is also known as the Adjacent
Channel Power Ratio (ACPR). It is defined as the ratio between the total power of the
adjacent channel to the power of the carrier channel. An ACLR measurement with sev-
eral carrier channels (also known as transmission or TX channels) is also possible and
is referred to as a multicarrier ACLR measurement.
There are two possible methods for measuring channel and adjacent channel power
with a signal analyzer:
● IBW method (Integration BandWidth method)
● Fast ACLR (Zero-span method ), i.e. using a channel filter
IBW method
When measuring the channel power, the FSW integrates the linear power which corre-
sponds to the levels of the measurement points within the selected channel. The signal
analyzer uses a resolution bandwidth which is far smaller than the channel bandwidth.
When sweeping over the channel, the channel filter is formed by the passband charac-
teristics of the resolution bandwidth.
Figure 6-20: Approximating the channel filter by sweeping with a small resolution bandwidth
1. The linear power of all the trace points within the channel is calculated.
Pi = 10(Li/10)
Where Pi = power of the trace pixel i
Li = displayed level of trace point i
2. The powers of all trace points within the channel are summed up and the sum is
divided by the number of trace points in the channel.
3. The result is multiplied by the quotient of the selected channel bandwidth and the
noise bandwidth of the resolution filter (RBW).
Since the power calculation is performed by integrating the trace within the channel
bandwidth, this method is called the IBW method (Integration Bandwidth method).
Fast ACLR
The integrated bandwidth method (IBW) calculates channel power and ACLR from the
trace data obtained during a continuous sweep over the selected span. Most parts of
this sweep are not part of the channel itself or the defined adjacent channels. There-
fore, most of the samples taken during the sweep time cannot be used for channel
power or ACLR calculation.
To decrease the measurement times, the FSW offers a "Fast ACLR" mode. In Fast
ACLR mode, the power of the frequency range between the channels of interest is not
measured, because it is not required for channel power or ACLR calculation. The mea-
surement time per channel is set with the sweep time. It is equal to the selected mea-
surement time divided by the selected number of channels.
In the "Fast ACLR" mode, the FSW measures the power of each channel in the time
domain, with the defined channel bandwidth, at the center frequency of the channel in
question. The digital implementation of the resolution bandwidths makes it possible to
select filter characteristics that are precisely tailored to the signal. For CDMA2000, for
example, the power in the useful channel is measured with a bandwidth of 1.23 MHz.
The power of the adjacent channels is measured with a bandwidth of 30 kHz. There-
fore the FSW changes from one channel to the other and measures the power at a
bandwidth of 1.23 MHz or 30 kHz using the RMS detector.
Figure 6-21: Measuring the channel power and adjacent channel power ratio for CDMA2000 signals
with zero span (Fast ACLR)
The repeatability of the results, especially in the narrow adjacent channels, strongly
depends on the measurement time for a given resolution bandwidth. A longer sweep
time can increase the probability that the measured value converges to the true value
of the adjacent channel power, but obviously increases measurement time.
Assume a measurement with five channels (1 channel plus 2 lower and 2 upper adja-
cent channels) and a sweep time of 100 ms. This measurement requires a measure-
ment time per channel of 20 ms. To calculate the power in one channel, the analyzer
considers the following number of effective samples:
<sweep time in channel> * <selected resolution bandwidth>
For example, for a sweep time of 100 ms the analyzer considers
(30 kHz / 4.19 MHz) * 100 ms * 10 kHz ≈ 7 samples. Whereas in Fast ACLR mode, it
considers (100 ms / 5) * 30 kHz ≈ 600 samples. If you compare these numbers, you
understand the increase of repeatability with a 95 % confidence level (2δ). It rises from
± 2.8 dB in normal mode to ± 0.34 dB in Fast ACLR mode for a sweep time of 100 ms.
For the same repeatability, the integration method requires a sweep time of 8.5 s. The
Figure 6-22 shows the standard deviation of the results as a function of the sweep
time.
Figure 6-22: Repeatability of adjacent channel power measurement on CDMA2000 standard signals if
the integration bandwidth method is used
The Figure 6-23 shows the repeatability of power measurements in the transmit chan-
nel and of relative power measurements in the adjacent channels as a function of
sweep time. The standard deviation of measurement results is calculated from 100
consecutive measurements. Consider the scaling when you compare power values.
Figure 6-23: Repeatability of adjacent channel power measurements on CDMA2000 signals in the fast
ACLR mode
All instrument settings for the selected channel setup (channel bandwidth, channel
spacing) can be optimized automatically using the "Adjust Settings" function (see "Opti-
mized Settings (Adjust Settings)" on page 172).
The easiest way to configure a measurement is using the configuration "Overview",
see Section 7.1, "Configuration overview", on page 359.
Sweep Time
The "Sweep Time" is selected depending on the desired reproducibility of results.
Reproducibility increases with "Sweep Time" since power measurement is then per-
formed over a longer time period. As a general approach, approximately 500 non-cor-
related measured values are required for a reproducibility of 0.5 dB. (That means: 95
% of the measurements are within 0.5 dB of the true measured value). Approximately
5000 measured values are required for a reproducibility of 0.1 dB (99 %). These values
are valid for white noise. The measured values are considered as non-correlated if
their time interval corresponds to the reciprocal of the measured bandwidth.
The number of A/D converter values, N, used to calculate the power, is defined by the
"Sweep Time". The time per trace pixel for power measurements is directly propor-
tional to the selected "Sweep Time".
If the sample detector is used, it is best to select the smallest "Sweep Time" possible
for a given span and resolution bandwidth. The minimum time is obtained if the setting
is coupled, that is: the time per measurement is minimal. Extending the measurement
time does not have any advantages. The number of samples for calculating the power
is defined by the number of trace points in the channel.
If the RMS detector is used, the selection of "Sweep Time"s can affect the repeatability
of the measurement results. Repeatability is increased at longer "Sweep Time"s.
If the RMS detector is used, the number of samples can be estimated as follows:
Since only uncorrelated samples contribute to the RMS value, the number of samples
can be calculated from the "Sweep Time" and the resolution bandwidth.
Samples can be assumed to be uncorrelated if sampling is performed at intervals of 1/
RBW. The number of uncorrelated samples is calculated as follows:
Ndecorr = SWT * RBW
The number of uncorrelated samples per trace pixel is obtained by dividing Ndecorr by
1001 (= pixels per trace).
The "Sweep Time" can be defined using the softkey in the "Ch Power" menu or in the
"Sweep" configuration dialog box (see "Sweep Time" on page 172).
Frequency span
The frequency span must cover at least the channels to be measured plus a measure-
ment margin of approximately 10 %.
If the frequency span is large in comparison to the channel bandwidth (or the adjacent-
channel bandwidths) being analyzed, only a few points on the trace are available per
channel. The calculated waveform for the used channel filter is less accurate, which
has a negative effect on the measurement accuracy. It is therefore strongly recommen-
ded that you consider the described formulas when you select the frequency span.
The frequency span for the defined channel settings can be optimized. Use the "Adjust
Settings" function in the "Ch Power" menu or the "General Settings" tab of the "ACLR
Setup" dialog box (see "Optimized Settings (Adjust Settings)" on page 172). You can
set the frequency span manually in the "Frequency" configuration dialog box.
(See Section 7.3.4, "How to define the frequency range", on page 480.)
For channel power measurements the "Adjust Settings" function sets the frequency
span as follows:
(No. of transmission channels – 1) x transmission channel spacing + 2 x transmission
channel bandwidth + measurement margin
For adjacent-channel power measurements, the "Adjust Settings" function sets the fre-
quency span as a function of the following parameters:
● Number of transmission channels
● Transmission channel spacing
● Adjacent-channel spacing
● Bandwidth of one of adjacent-channels ADJ, ALT1 or ALT2, whichever is furthest
away from the transmission channels
(No. of transmission channels – 1) * (transmission channel spacing + 2) * (adjacent-
channel spacing + adjacent-channel bandwidth) + measurement margin
The measurement margin is approximately 10 % of the value obtained by adding the
channel spacing and the channel bandwidth.
You can optimize the resolution bandwidth for the defined channel settings. Use the
"Adjust Settings" function in the "Ch Power" menu or the "General Settings" tab of the
"ACLR Setup" dialog box (see "Optimized Settings (Adjust Settings)" on page 172).
You can set the RBW manually in the "Bandwidth" configuration dialog box, see "RBW"
on page 349.
Except for the IS95 CDMA standards, the "Adjust Settings" function sets the resolution
bandwidth (RBW) as a function of the channel bandwidth:
"RBW" ≤ 1/40 of "Channel Bandwidth"
The maximum resolution bandwidth (concerning the requirement RBW ≤ 1/40) result-
ing from the available RBW steps (1, 3) is selected.
Detector
The RMS detector correctly indicates the power irrespective of the characteristics of
the signal to be measured.
For details, see "RMS average detector" on page 618.
In principle, the sample detector is also possible. However, due to the limited number
of measurement points used to calculate the power in the channel, the sample detector
yields less stable results.
You can set the RMS detector for the defined channel settings automatically. Use the
"Adjust Settings" function in the "Ch Power" menu or the "General Settings" tab of the
"ACLR Setup" dialog box (see "Optimized Settings (Adjust Settings)" on page 172).
You can set the detector manually in the "Traces" configuration dialog box, see "Detec-
tor" on page 626.
Trace averaging
Avoid averaging, which is often performed to stabilize the measurement results but
leads to a level indication that is too low. The reduction in the displayed power depends
on the number of averages and the signal characteristics in the channel to be mea-
sured.
The "Adjust Settings" function switches off trace averaging. You can deactivate the
trace averaging manually in the "Traces" configuration dialog box, see "Average Mode"
on page 627.
Reference level
To achieve an optimum dynamic range, set the reference level so that the signal is as
close to the reference level as possible without forcing an overload message. However,
if the signal-to-noise ratio becomes too small, the dynamic range is also limited. The
measurement bandwidth for channel power measurements is significantly smaller than
the signal bandwidth. Thus, the signal path can be overloaded although the trace is still
significantly below the reference level.
Selecting a predefined standard or automatically adjusting settings does not affect the
reference level. The reference level can be set automatically using the "Auto Level"
function in the [Auto Set] menu, or manually in the "Amplitude" menu.
Modern base stations can contain multiple signals for different communication stand-
ards. A new measurement standard is provided for the FSW ACLR measurement that
allows you to measure such MSR signals, including non-contiguous setups. Multiple
(also non-) contiguous transmit channels can be specified at absolute frequencies,
independent from the common center frequency selected for display.
Signal structure
Up to 18 transmit channels can be grouped in a maximum of 8sub blocks. Between
two sub blocks, two gaps are defined: a lower gap and an upper gap. Each gap in turn
contains two channels (gap channels). The channels in the upper gap are identical to
those in the lower gap, but inverted. To either side of the outermost transmit channels,
lower and upper adjacent channels can be defined as in common ACLR measurement
setups.
If the gap channels are not symmetrical, you must configure up to four channels indi-
vidually. The formula indicated above applies for the lower channels. For the upper
channels, the spacing is defined as:
Spacing = [right sub block CF]- [CF of gap channel] - ([RF bandwidth of right sub
block] /2)
According to the MSR standard, the Cumulative Adjacent Channel Leakage Ratio
(CACLR) power must be determined for the gap channels. The CACLR power is mea-
sured in the two gap channels for the upper and lower gap. The power in the gap chan-
nels is then set in relation to the power of the two closest transmission channels to
either side of the gap. The CACLR power for the gap channels is indicated in the
Result Summary.
In addition, the ACLR power for the individual gap channels is indicated in the Result
Summary. The ACLR power of the lower gap channels refers to the TX channel to the
left of the gap. The ACLR power of the upper gap channels refers to the TX channel to
the right of the gap. A separate relative limit value can be defined for the ACLR power.
Adjacent channels
Adjacent channels are defined as in common ACLR measurements using bandwidths
and spacings, relative to the uppermost or lowermost transmit channels in the sub
blocks (see also Figure 6-24):
● The spacing of the lower adjacent channels refers to the CF of the first TX channel
in the first sub block.
● The spacing of the upper adjacent channels refers to the CF of the last TX channel
in the last sub block.
The upper and lower adjacent channels can also be defined asymmetrically (see "Sym-
metrical Adjacent Setup" on page 182). This is particularly useful if the lowest TX chan-
nel and highest TX channel use different standards and thus require different band-
widths for adjacent channel power measurement.
For symmetrical configuration, gap channels can be hidden if they do not reach a mini-
mum size.
For asymmetrical configuration, you can define the number of upper or lower gap
channels to be displayed.
In both cases, you can deactivate all gap channels. This enhances the result display,
as fewer lines and bars are displayed. If gap channels are deactivated, the power
results are not calculated and thus are not shown in the Result Summary table.
Furthermore, channel names for all TX, adjacent, and alternate channels are user-
definable (not gap channels).
of a total TX channel power. Instead of the individual channel frequency offsets, the
absolute center frequencies are indicated for the transmit channels.
The CACLR and ACLR power results for each gap channel are appended at the end of
the table. The CACLR results are calculated as the power in the gap channel divided
by the power sum of the two closest transmission channels to either side of it.
Remote command:
CALCulate:MARKer:FUNCtion:POWer<sb>:RESult? GACLr or
CALCulate:MARKer:FUNCtion:POWer<sb>:RESult? MACM, see
CALCulate<n>:MARKer<m>:FUNCtion:POWer<sb>:RESult? on page 915
Access: "Overview" > "Select Measurement" > "Channel Power ACLR" > "CP / ACLR
Config"
Both Channel Power (CP) and Adjacent-Channel Power (ACLR) measurements are
available.
If the "Multi-Standard Radio" standard is selected (see "Standard" on page 168), the
"ACLR Setup" dialog box is replaced by the "MSR ACLR Setup" dialog box. See Sec-
tion 6.2.5, "MSR ACLR configuration", on page 177 for a description of these settings.
The remote commands required to perform these tasks are described in Sec-
tion 13.5.3, "Measuring the channel power and ACLR", on page 918.
● General CP/ACLR measurement settings............................................................ 167
● Channel setup.......................................................................................................173
General measurement settings are defined in the "ACLR Setup" dialog, in the "General
Settings" tab.
Standard......................................................................................................................168
└ Predefined Standards................................................................................... 168
└ User Standards............................................................................................. 168
Standard
The main measurement settings can be stored as a standard file. When such a stan-
dard is loaded, the required channel and general measurement settings are automati-
cally set on the FSW. However, the settings can be changed. Predefined standards are
available for standard measurements, but standard files with user-defined configura-
tions can also be created.
Note: If the "Multi-Standard Radio" standard is selected, the "ACLR Setup" dialog box
is replaced by the "MSR ACLR Setup" dialog box (see Section 6.2.5, "MSR ACLR con-
figuration", on page 177).
If any other predefined standard (or "NONE") is selected, the "ACLR Setup" dialog box
is restored (see Section 6.2.4, "Channel power configuration", on page 167).
Note that changes in the configuration are not stored when the dialog boxes are
exchanged.
In addition to the predefined standards, you can save your own standards with your
specific measurement settings in an XML file so you can use them again later. User-
defined standards are stored on the instrument in the
C:\Program Files (x86)\Rohde-Schwarz\FSW\<version>\acp_std direc-
tory.
A sample file is provided for an MSR ACLR measurement (MSR_ACLRExample.xml).
It sets up the measurement for the MSR signal generator waveform described in the
file C:\R_S\INSTR\USER\waveform\MSRA_GSM_WCDMA_LTE_GSM.wv.
Note that ACLR user standards are not supported for Fast ACLR measurements.
Note: User standards created on an analyzer of the R&S FSP family are compatible to
the FSW. User standards created on an FSW, however, are not necessarily compatible
to the analyzers of the R&S FSP family and may not work there.
The following parameter definitions are saved in a user-defined standard:
● Number of adjacent channels
● Channel bandwidth of transmission (Tx), adjacent (Adj) and alternate (Alt) chan-
nels
● Channel spacings
● Weighting filters
● Resolution bandwidth
● Video bandwidth
● Detector
● ACLR limits and their state
● "Sweep Time" and "Sweep Time" coupling
● Trace and power mode
● (MSR only: sub block and gap channel definition)
Save the current measurement settings as a user-defined standard, load a stored mea-
surement configuration, or delete an existing configuration file.
For details see Section 6.2.6.4, "How to manage user-defined configurations",
on page 198.
Remote command:
To query all available standards:
CALCulate<n>:MARKer<m>:FUNCtion:POWer<sb>:STANdard:CATalog?
on page 919
To load a standard:
CALCulate<n>:MARKer<m>:FUNCtion:POWer<sb>:PRESet on page 919
To save a standard:
CALCulate<n>:MARKer<m>:FUNCtion:POWer<sb>:STANdard:SAVE
on page 920
To delete a standard:
CALCulate<n>:MARKer<m>:FUNCtion:POWer<sb>:STANdard:DELete
on page 920
Results are provided for the Tx channel and the number of defined adjacent channels
above and below the Tx channel. If more than one Tx channel is defined, the carrier
channel to which the relative adjacent-channel power values should be referenced
must be defined (see "Reference Channel" on page 170).
Note: If several carriers (Tx channels) are activated for the measurement, the number
of sweep points is increased to ensure that adjacent-channel powers are measured
with adequate accuracy.
For more information on how the number of channels affects the measured powers,
see Section 6.2.2, "Channel power results", on page 152.
Remote command:
Number of Tx channels:
[SENSe:]POWer:ACHannel:TXCHannel:COUNt on page 925
Number of Adjacent channels:
[SENSe:]POWer:ACHannel:ACPairs on page 921
Reference Channel
The measured power values in the adjacent channels can be displayed relative to the
transmission channel. If more than one Tx channel is defined, define which one is used
as a reference channel.
Min Power Tx Channel The transmission channel with the lowest power is used as a reference channel.
Max Power Tx Chan- The transmission channel with the highest power is used as a reference channel
nel (Default).
Lowest & Highest The outer left-hand transmission channel is the reference channel for the lower
Channel adjacent channels, the outer right-hand transmission channel that for the upper
adjacent channels.
Remote command:
[SENSe:]POWer:ACHannel:REFerence:TXCHannel:MANual on page 928
[SENSe:]POWer:ACHannel:REFerence:TXCHannel:AUTO on page 928
Noise Cancellation
The FSW can correct the results by removing the inherent noise of the analyzer, which
increases the dynamic range.
In this case, a reference measurement of the inherent noise of the analyzer is carried
out. The measured noise power is then subtracted from the power in the channel that
is being analyzed (first active trace only).
The inherent noise of the instrument depends on the selected center frequency, resolu-
tion bandwidth and level setting. Therefore, the correction function is disabled when-
ever one of these parameters is changed. A disable message is displayed on the
screen. To enable the correction function after changing one of these settings, activate
it again. A new reference measurement is carried out.
Noise cancellation is also available in zero span.
For an active external frontend, noise cancellation is not available. See "External Fron-
tend Connection State" on page 453.
Currently, noise cancellation is only available for the following trace detectors (see
"Detector" on page 626):
● RMS
● Average
● Sample
● Positive peak
Remote command:
[SENSe:]POWer:NCORrection on page 1212
Fast ACLR
If activated, instead of using the IBW method, the FSW sets the center frequency to
the different channel center frequencies consecutively and measures the power with
the selected measurement time (= sweep time/number of channels).
Remote command:
[SENSe:]POWer:HSPeed on page 940
Selected Trace
The CP/ACLR measurement can be performed on any active trace.
Remote command:
[SENSe:]POWer:TRACe on page 918
Power Mode
The measured power values can be displayed directly for each trace ("Clear/ Write"),
or only the maximum values over a series of measurements can be displayed ("Max
Hold"). In the latter case, the power values are calculated from the current trace and
compared with the previous power value using a maximum algorithm. The higher value
is retained. If "Max Hold" mode is activated, "Pwr Max" is indicated in the table header.
Note that the trace mode remains unaffected by this setting.
Remote command:
CALCulate<n>:MARKer<m>:FUNCtion:POWer<sb>:MODE on page 914
Sweep Time
With the RMS detector, a longer "Sweep Time" increases the stability of the measure-
ment results. For recommendations on setting this parameter, see "Sweep Time"
on page 158.
The "Sweep Time" can be set via the softkey in the "Ch Power" menu and is identical
to the general setting in the "Sweep" configuration dialog box.
Remote command:
[SENSe:]SWEep:TIME on page 1208
The "Channel Settings" tab in the "ACLR Setup" dialog box provides all the channel
settings to configure the channel power or ACLR measurement. You can define the
channel settings for all channels, independent of the defined number of used TX or
adjacent channels (see "Number of channels: Tx, Adj" on page 169).
For details on setting up channels, see Section 6.2.6.2, "How to set up the channels",
on page 195.
The following settings are available in individual subtabs of the "Channel Settings" tab.
Channel Bandwidth..................................................................................................... 174
Channel Spacings....................................................................................................... 174
Limit Check................................................................................................................. 175
Total Limit Pass Mode................................................................................................. 176
Weighting Filters..........................................................................................................177
Channel Names.......................................................................................................... 177
Channel Bandwidth
Channel Spacings
Channel spacings are normally defined by the transmission standard but can be
changed.
If the spacings are not equal, the channel distribution in relation to the center frequency
is as follows:
Even number of Tx channels The two Tx channels in the middle are used to calculate the fre-
quency between those two channels. This frequency is aligned to
the center frequency.
The spacings between all Tx channels can be defined individually. When you change
the spacing for one channel, the value is automatically also defined for all subsequent
Tx channels. This allows you to set up a system with equal Tx channel spacing quickly.
For different spacings, set up the channels from top to bottom.
… …
If you change the adjacent-channel spacing (ADJ), all higher adjacent channel spac-
ings (ALT1, ALT2, …) are multiplied by the same factor (new spacing value/old spacing
value). Again, only enter one value for equal channel spacing. For different spacing,
configure the spacings from top to bottom.
For details, see Section 6.2.6.2, "How to set up the channels", on page 195
Remote command:
[SENSe:]POWer:ACHannel:SPACing:CHANnel<ch> on page 924
[SENSe:]POWer:ACHannel:SPACing[:ACHannel] on page 923
[SENSe:]POWer:ACHannel:SPACing:ALTernate<ch> on page 924
Limit Check
During an ACLR measurement, the power values can be checked whether they
exceed user-defined or standard-defined limits. A relative or absolute limit can be
defined, or both. Both limit types are considered, regardless whether the measured lev-
els are absolute or relative values. The check of both limit values can be activated
independently. If any active limit value is exceeded, the measured value is displayed in
red and marked by a preceding asterisk in the result table.
The results of the power limit checks are also indicated in the STAT:QUES:ACPL sta-
tus registry (see Section 12.2.2.6, "STATus:QUEStionable:ACPLimit register",
on page 832).
Remote command:
CALCulate<n>:LIMit<li>:ACPower[:STATe] on page 935
CALCulate<n>:LIMit<li>:ACPower:ACHannel:ABSolute:STATe on page 929
If you define only relative or absolute limits, the FSW only evaluates the corresponding
limits.
If you change the limit evaluation method after the measurement, you have to refresh
the measurement.
The selected method adjusts the contents of the following result displays.
● ACLR result summary
The default value is according to 3GPP 36.141 and 38.141-x.
"Absolute" Checks the absolute limits defined for the ACLR. The limit check
passes when the signal level is within the absolute limits.
"Relative" Checks the relative limits defined for the ACLR. The limit check
passes when the signal level is within the relative limits.
"Absolute and The limit check for both, the absolute and the relative limits, must
Relative" pass to get an overall pass.
"Absolute or The limit check for either the absolute or the relative limits must pass
Relative" to get an overall pass.
Remote command:
CALCulate<n>:LIMit<li>:ACPower:PMODe on page 934
Weighting Filters
Weighting filters allow you to determine the influence of individual channels on the total
measurement result. For each channel you can activate or deactivate the use of the
weighting filter and define an individual weighting factor ("Alpha:" value).
Weighting filters are not available for all supported standards and cannot always be
defined manually where they are available.
Remote command:
Activating/Deactivating:
[SENSe:]POWer:ACHannel:FILTer[:STATe]:CHANnel<ch> on page 927
[SENSe:]POWer:ACHannel:FILTer[:STATe]:ACHannel on page 926
[SENSe:]POWer:ACHannel:FILTer[:STATe]:ALTernate<ch> on page 927
Alpha value:
[SENSe:]POWer:ACHannel:FILTer:ALPHa:CHANnel<ch> on page 926
[SENSe:]POWer:ACHannel:FILTer:ALPHa:ACHannel on page 925
[SENSe:]POWer:ACHannel:FILTer:ALPHa:ALTernate<ch> on page 925
Channel Names
In the FSW's display, carrier channels are labeled "Tx" by default; the first neighboring
channel is labeled "Adj" (adjacent) channel; all others are labeled "Alt" (alternate)
channels. You can define user-specific channel names for each channel which are dis-
played in the result diagram and result table.
Remote command:
[SENSe:]POWer:ACHannel:NAME:ACHannel on page 922
[SENSe:]POWer:ACHannel:NAME:ALTernate<ch> on page 923
[SENSe:]POWer:ACHannel:NAME:CHANnel<ch> on page 923
Access: "Overview" > "Select Measurement" > "Channel Power ACLR" > "CP / ACLR
Standard" > "Standard": "Multi-Standard Radio" > "CP / ACLR Config"
ACLR measurements can also be performed on input containing multiple signals for
different communication standards. A new measurement standard is provided that
allows you to define multiple discontiguous transmit channels at specified frequencies,
independent from the selected center frequency. If the "Multi-Standard Radio" standard
is selected (see "Standard" on page 168), the "ACLR Setup" dialog box is replaced by
the "MSR ACLR Setup" dialog box.
Access: "Overview" > "Select Measurement" > "Channel Power ACLR" > "CP / ACLR
Standard" > "Standard": "Multi-Standard Radio" > "CP / ACLR Config" > "MSR General
Settings" tab
Standard......................................................................................................................179
└ Predefined Standards................................................................................... 179
└ User Standards............................................................................................. 179
Number of Sub Blocks................................................................................................ 180
Reference Channel..................................................................................................... 180
Noise Cancellation...................................................................................................... 181
Selected Trace............................................................................................................ 181
Absolute and Relative Values (ACLR Mode).............................................................. 181
Channel power level and density (Power Unit)........................................................... 182
Power Mode................................................................................................................ 182
Optimized Settings (Adjust Settings)...........................................................................182
Symmetrical Adjacent Setup....................................................................................... 182
Limit Checking.............................................................................................................183
Standard
The main measurement settings can be stored as a standard file. When such a stan-
dard is loaded, the required channel and general measurement settings are automati-
cally set on the FSW. However, the settings can be changed. Predefined standards are
available for standard measurements, but standard files with user-defined configura-
tions can also be created.
Note: If the "Multi-Standard Radio" standard is selected, the "ACLR Setup" dialog box
is replaced by the "MSR ACLR Setup" dialog box (see Section 6.2.5, "MSR ACLR con-
figuration", on page 177).
If any other predefined standard (or "NONE") is selected, the "ACLR Setup" dialog box
is restored (see Section 6.2.4, "Channel power configuration", on page 167).
Note that changes in the configuration are not stored when the dialog boxes are
exchanged.
● Channel bandwidth of transmission (Tx), adjacent (Adj) and alternate (Alt) chan-
nels
● Channel spacings
● Weighting filters
● Resolution bandwidth
● Video bandwidth
● Detector
● ACLR limits and their state
● "Sweep Time" and "Sweep Time" coupling
● Trace and power mode
● (MSR only: sub block and gap channel definition)
Save the current measurement settings as a user-defined standard, load a stored mea-
surement configuration, or delete an existing configuration file.
For details see Section 6.2.6.4, "How to manage user-defined configurations",
on page 198.
Remote command:
To query all available standards:
CALCulate<n>:MARKer<m>:FUNCtion:POWer<sb>:STANdard:CATalog?
on page 919
To load a standard:
CALCulate<n>:MARKer<m>:FUNCtion:POWer<sb>:PRESet on page 919
To save a standard:
CALCulate<n>:MARKer<m>:FUNCtion:POWer<sb>:STANdard:SAVE
on page 920
To delete a standard:
CALCulate<n>:MARKer<m>:FUNCtion:POWer<sb>:STANdard:DELete
on page 920
Reference Channel
The measured power values in the adjacent channels can be displayed relative to the
transmission channel. If more than one Tx channel is defined, define which one is used
as a reference channel.
Min Power Tx Channel The transmission channel with the lowest power is used as a reference channel.
Max Power Tx Chan- The transmission channel with the highest power is used as a reference channel
nel (Default).
Lowest & Highest The outer left-hand transmission channel is the reference channel for the lower
Channel adjacent channels, the outer right-hand transmission channel that for the upper
adjacent channels.
Remote command:
[SENSe:]POWer:ACHannel:REFerence:TXCHannel:MANual on page 928
[SENSe:]POWer:ACHannel:REFerence:TXCHannel:AUTO on page 928
Noise Cancellation
The FSW can correct the results by removing the inherent noise of the analyzer, which
increases the dynamic range.
In this case, a reference measurement of the inherent noise of the analyzer is carried
out. The measured noise power is then subtracted from the power in the channel that
is being analyzed (first active trace only).
The inherent noise of the instrument depends on the selected center frequency, resolu-
tion bandwidth and level setting. Therefore, the correction function is disabled when-
ever one of these parameters is changed. A disable message is displayed on the
screen. To enable the correction function after changing one of these settings, activate
it again. A new reference measurement is carried out.
Noise cancellation is also available in zero span.
For an active external frontend, noise cancellation is not available. See "External Fron-
tend Connection State" on page 453.
Currently, noise cancellation is only available for the following trace detectors (see
"Detector" on page 626):
● RMS
● Average
● Sample
● Positive peak
Remote command:
[SENSe:]POWer:NCORrection on page 1212
Selected Trace
The CP/ACLR measurement can be performed on any active trace.
Remote command:
[SENSe:]POWer:TRACe on page 918
Remote command:
[SENSe:]POWer:ACHannel:MODE on page 974
Power Mode
The measured power values can be displayed directly for each trace ("Clear/ Write"),
or only the maximum values over a series of measurements can be displayed ("Max
Hold"). In the latter case, the power values are calculated from the current trace and
compared with the previous power value using a maximum algorithm. The higher value
is retained. If "Max Hold" mode is activated, "Pwr Max" is indicated in the table header.
Note that the trace mode remains unaffected by this setting.
Remote command:
CALCulate<n>:MARKer<m>:FUNCtion:POWer<sb>:MODE on page 914
If disabled, the upper and lower channels can be configured differently. This is particu-
larly useful if the lowest TX channel and highest TX channel use different standards
and thus require different bandwidths for adjacent channel power measurement.
Remote command:
[SENSe:]POWer:ACHannel:SSETup on page 946
Limit Checking
Activates or deactivates limit checks globally for all adjacent and gap channels. In addi-
tion to this setting, limits must be defined and activated individually for each channel.
The results of the power limit checks are also indicated in the STAT:QUES:ACPL sta-
tus registry (see Section 12.2.2.6, "STATus:QUEStionable:ACPLimit register",
on page 832).
Remote command:
CALCulate<n>:LIMit<li>:ACPower[:STATe] on page 935
Access: "Overview" > "Select Measurement" > "Channel Power ACLR" > "CP / ACLR
Standard" > "Standard": "Multi-Standard Radio" > "CP / ACLR Config" > "Tx Channels"
tab
The "Tx Channels" tab provides all the channel settings to configure sub blocks and TX
channels in MSR ACLR measurements.
Tx Channel Definition
As opposed to common ACLR channel definitions, the TX channels are defined at
absolute frequencies, rather than by a spacing relative to the (common) center fre-
quency. Each transmit channel can be assigned a different technology, used to prede-
fine the required bandwidth.
The TX channel settings for the individual sub blocks are configured in individual sub-
tabs of the "Tx Channel Settings" tab.
For details on configuring MSR TX channels, see Section 6.2.6.3, "How to configure an
MSR ACLR measurement", on page 196.
Remote command:
[SENSe:]POWer:ACHannel:SBLock<sb>:NAME[:CHANnel<ch>] on page 970
Remote command:
Activating/Deactivating:
[SENSe:]POWer:ACHannel:FILTer[:STATe]:SBLock<sb>:CHANnel<ch>
on page 942
Alpha value:
[SENSe:]POWer:ACHannel:FILTer:ALPHa:SBLock<sb>:CHANnel<ch>
on page 942
Access: "Overview" > "Select Measurement" > "Channel Power ACLR" > "CP / ACLR
Standard" > "Standard": "Multi-Standard Radio" > "CP / ACLR Config" > "Adjacent
Channels" tab
The "Adjacent Channels" tab provides all the channel settings to configure adjacent
and gap channels in MSR ACLR measurements.
For symmetrical channel definition (see "Symmetrical Adjacent Setup" on page 182),
the dialog box is reduced as the upper and lower channels are identical.
For details on setting up channels, see Section 6.2.6.3, "How to configure an MSR
ACLR measurement", on page 196.
Remote command:
[SENSe:]POWer:ACHannel:BANDwidth:ACHannel on page 921
[SENSe:]POWer:ACHannel:BANDwidth:ALTernate<ch> on page 922
[SENSe:]POWer:ACHannel:BANDwidth:UACHannel on page 947
[SENSe:]POWer:ACHannel:BANDwidth:UALTernate<ch> on page 947
Remote command:
CALCulate<n>:LIMit<li>:ACPower[:STATe] on page 935
CALCulate<n>:LIMit<li>:ACPower:ACHannel:ABSolute:STATe on page 929
CALCulate<n>:LIMit<li>:ACPower:ACHannel:ABSolute on page 929
CALCulate<n>:LIMit<li>:ACPower:ACHannel[:RELative]:STATe
on page 931
CALCulate<n>:LIMit<li>:ACPower:ACHannel[:RELative] on page 930
CALCulate<n>:LIMit<li>:ACPower:ALTernate<ch>:ABSolute:STATe
on page 932
CALCulate<n>:LIMit<li>:ACPower:ALTernate<ch>:ABSolute on page 932
CALCulate<n>:LIMit<li>:ACPower:ALTernate<ch>[:RELative]:STATe
on page 934
CALCulate<n>:LIMit<li>:ACPower:ALTernate<ch>[:RELative]
on page 933
CALCulate<n>:LIMit<li>:ACPower:ACHannel:RESult? on page 930
Access: "Overview" > "Select Measurement" > "Channel Power ACLR" > "CP / ACLR
Standard" > "Standard": "Multi-Standard Radio" > "CP / ACLR Config" > "Gap Chan-
nels" tab
The "Gap Channels" tab provides all the channel settings to configure gap channels in
MSR ACLR measurements.
Activate Gaps
If enabled, the gap channels are displayed and channel power results are calculated
and displayed in the Result Summary.
Remote command:
[SENSe:]POWer:ACHannel:AGCHannels on page 949
Gap Mode
In "Auto" mode, upper and lower gap channels are configured identically, so only two
channels need to be configured (gap 1, gap 2). Gap channels are configured identically
for all gaps, if more than two sub blocks are defined. Depending on the defined mini-
mum gap size, the actual number of evaluated gap channels is determined automati-
cally.
In "Manual" mode, up to four channels can be configured individually for each gap. If
enabled, the configured gap channels are always evaluated, regardless of the gap
size.
Remote command:
[SENSe:]POWer:ACHannel:GAP<gap>:MODE on page 949
Minimum gap size to show Gap 1/ Minimum gap size to show Gap 2 ← Gap
Channel Definition
If the gap between the sub blocks does not exceed the specified bandwidth, the gap
channels are not displayed in the diagram. The gap channel results are not calculated
in the result summary.
This command is only available for symmetrical gap channels in "Auto" gap mode (see
"Gap Mode" on page 190).
Remote command:
[SENSe:]POWer:ACHannel:GAP<gap>[:AUTO]:MSIZe on page 954
The required spacing can be determined according to the following formula (indicated
for lower channels):
Spacing = [CF of gap channel] - [left sub block CF] + ([RF band-
width of left sub block] /2)
For details, see Section 6.2.6.3, "How to configure an MSR ACLR measurement",
on page 196.
Remote command:
[SENSe:]POWer:ACHannel:SPACing:GAP<gap>[:AUTO] on page 954
For manual (asymmetrical) configuration:
[SENSe:]POWer:ACHannel:SPACing:GAP<gap>:MANual:LOWer on page 968
[SENSe:]POWer:ACHannel:SPACing:GAP<gap>:MANual:UPPer on page 968
Access: "Overview" > "Select Measurement" > "Channel Power ACLR" > "CP / ACLR
Standard" > "Standard": "Multi-Standard Radio" > "CP / ACLR Config" > "Names" tab
Channel names for all TX, adjacent, and alternate channels are user-definable.
In the "Names" tab, you can define a customized name for each channel in each sub
block. Note that the names are not checked for uniqueness.
Remote command:
[SENSe:]POWer:ACHannel:SBLock<sb>:NAME[:CHANnel<ch>] on page 970
[SENSe:]POWer:ACHannel:NAME:ACHannel on page 922
[SENSe:]POWer:ACHannel:NAME:ALTernate<ch> on page 923
[SENSe:]POWer:ACHannel:NAME:UACHannel on page 969
[SENSe:]POWer:ACHannel:NAME:UALTernate<ch> on page 970
The following step-by-step instructions demonstrate the most common tasks when per-
forming channel power measurements.
For remote operation, see Section 13.5.3.11, "Programming examples for channel
power measurements", on page 974.
5. If necessary, edit the settings for your specific measurement as described in Sec-
tion 6.2.6.2, "How to set up the channels", on page 195, or load a user-defined
configuration (see "To load a user-defined configuration" on page 198).
Channel definition is the basis for measuring power levels in certain frequency ranges.
Usually, the power levels in one or more carrier (TX) channels and possibly the adja-
cent channels are of interest. Up to 18 carrier channels and up to 12 adjacent channels
can be defined.
When a measurement standard is selected, all settings including the channel band-
widths and channel spacings are set according to the selected standard. Select a stan-
dard in the "Ch Power" menu or the "ACLR Setup" dialog box. You can adjust the set-
tings afterwards.
Channel setup consists of the following settings:
● The number of transmission (TX) and adjacent channels
● The bandwidth of each channel
● For multicarrier ACLR measurements: which TX channel is used as a reference
● The spacing between the individual channels
● Optionally: the names of the channels displayed in the diagram and result table
● Optionally: the influence of individual channels on the total measurement result
("Weighting Filter")
● Optionally: limits for a limit check on the measured power levels
► To configure the channels in the "Ch Power" dialog box, select "Ch Power" > "CP /
ACLR Config" > "Channel Settings" tab.
In the "Channel Setup" dialog box, you can define the channel settings for all channels,
independent of the defined number of used TX or adjacent channels.
5. Select "CP / ACLR Config" to configure general MSR settings, including the num-
ber of sub blocks (up to 8).
To configure asymmetric adjacent channels, deactivate the "Symmetrical" option in
the general MSR settings.
6. Select the "Tx Channels" tab to configure the sub blocks and transmission chan-
nels.
For each sub block:
a) Define the (center frequency) position and bandwidth of the sub block, as well
as the number of transmission channels it contains.
b) For each transmission channel in the sub block:
● Define the center frequency.
● Select the technology used for transmission.
● Check the bandwidth.
● If necessary, define the use of a weighting filter for the channel.
8. Define the number of adjacent channels and the settings for each channel:
● The spacing, defined as the distance of the center frequency from the center
frequency of the first transmission channel in the first sub block.
For asymmetrical channels, define the upper adjacent channel spacing as the
distance from the center frequency of the last transmission channel in the last
sub block.
● The bandwidth
● If necessary, a weighting filter
● Optionally, define and activate relative or absolute limits, or both, against which
the power levels of the channel are to be checked.
10. Define the following settings for the two (upper or lower) gap channels. Since the
upper and lower channels are identical, it is only necessary to configure two chan-
nels.
● The spacing, defined as the distance of the center frequency from the outer
edge of the sub block to the left or right of the gap. You can determine the
required spacing as follows:
Spacing = [CF of the gap channel] - [left sub block center] + ([RF bandwidth of
left sub block] /2)
● The bandwidth
● If necessary, a weighting filter
● Optionally, define and activate relative or absolute limits, or both, against which
the power levels of the channel are to be checked.
11. If power limits are defined and activated, activate global limit checking for the mea-
surement on the "MSR General Settings" tab.
12. Optionally, store the settings for the MSR ACLR measurement as a user-defined
standard as described in "To store a user-defined configuration" on page 198. Oth-
erwise the configuration is lost when you select a different measurement standard.
2. Configure the measurement as required (see also Section 6.2.6.2, "How to set up
the channels", on page 195).
3. In the "General Settings" tab, select "Manage User Standards" to display the "Man-
age" dialog box.
5. Select "Save".
3. Select "Load".
The stored settings are automatically set on the FSW and the measurement is
restarted with the new parameters.
For power measurements with only one TX channel and no adjacent channels, you
can define a fixed reference power and compare subsequent measurement results to
the stored reference power.
5. To start a new measurement without the fixed reference, temporarily define a sec-
ond channel or preset the instrument.
The FSW has test routines for simple channel and adjacent channel power measure-
ments. These routines give quick results without any complex or tedious setting proce-
dures.
Test setup:
Level: 0 dBm
Modulation: CDMA2000
Procedure:
7. Set the "CDMA2000" standard for adjacent channel power measurement in the
"ACLR Setup" dialog box.
The FSW sets the channel configuration according to the 2000 standard with two
adjacent channels above and 2 below the transmit channel. The spectrum is dis-
played in the upper part of the screen, the numeric values of the results and the
channel configuration in the lower part of the screen. The various channels are rep-
resented by vertical lines on the graph.
The frequency span, resolution bandwidth, video bandwidth and detector are
selected automatically to give correct results. To obtain stable results – especially
in the adjacent channels (30 kHz bandwidth) which are narrow in comparison with
the transmission channel bandwidth (1.23 MHz) – the RMS detector is used.
8. Set the optimal reference level and RF attenuation for the applied signal level using
the "Auto Level" function in the [Auto Set] menu.
The FSW sets the optimal RF attenuation and the reference level based on the
transmission channel power to obtain the maximum dynamic range.
The Figure 6-37 shows the result of the measurement.
Test setup:
Level: 4 dBm
Procedure:
4. Select the "Channel Power ACLR" measurement function from the "Select Mea-
surement" dialog box.
5. Set the "W-CDMA 3GPP REV" standard for adjacent channel power measurement
in the "ACLR Setup" dialog box.
The FSW sets the channel configuration to the W-CDMA standard for mobiles with
two adjacent channels above and below the transmit channel. The frequency span,
the resolution and video bandwidth and the detector are automatically set to the
correct values. The spectrum is displayed in the upper window and the channel
power, the level ratios of the adjacent channel powers and the channel configura-
tion in the lower window. The individual channels are displayed as bars in the
graph.
6. Set the optimal reference level and RF attenuation for the applied signal level using
the "Auto Level" function.
The FSW sets the optimum RF attenuation and the reference level for the power in
the transmission channel to obtain the maximum dynamic range. The following fig-
ure shows the result of the measurement.
Figure 6-38: Measuring the relative adjacent channel power on a W-CDMA uplink signal
The FSW measures the power of the individual channels. A root raised cosine filter
with the parameters α = 0.22 and chip rate 3.84 Mcps (= receive filter for W-CDMA)
is used as channel filter.
Figure 6-39: Dynamic range for ACLR measurements on W-CDMA uplink signals as a function of the
mixer level
The level of the W-CDMA signal at the input mixer is shown on the horizontal axis, i.e.
the measured signal level minus the selected RF attenuation. The individual compo-
nents which contribute to the power in the adjacent channel and the resulting relative
level (total ACPR) in the adjacent channel are displayed on the vertical axis. The opti-
mum mixer level is -12 dBm. The relative adjacent channel power (ACPR) at an opti-
mum mixer level is -77 dBc. At a given signal level, the mixer level is set in 1 dB steps
with the 1 dB RF attenuator. Thus, the optimum range spreads from -10 dBm to
-14 dBm.
To set the attenuation parameter manually, the following method is recommended:
► Set the RF attenuation so that the mixer level (= measured channel power – RF
attenuation) is between -10 dBm and -14 dBm.
This method is automated with the "Auto Level" function. Especially in remote control
mode, e.g. in production environments, set the attenuation parameters correctly before
the measurement. That saves the time required for automatic setting.
To measure the FSW's intrinsic dynamic range for W-CDMA adjacent channel power
measurements, a filter which suppresses the adjacent channel power is required at the
output of the transmitter. A SAW filter with a bandwidth of 4 MHz, for example, can be
used.
6.2.7.3 Measurement example 3 – measuring the intrinsic noise of the FSW with the
channel power function
Noise in any bandwidth can be measured with the channel power measurement func-
tions. Thus the noise power in a communication channel can be determined, for exam-
ple.
If the noise spectrum within the channel bandwidth is flat, the noise marker can be
used to determine the noise power in the channel by considering the channel band-
width. However, in the following cases, the channel power measurement method must
be used to obtain correct measurement results:
● If phase noise and noise that normally increases towards the carrier is dominant in
the channel to be measured
● If there are discrete spurious signals in the channel
Test setup:
Procedure:
4. Select the "Channel Power ACLR" measurement function from the "Select Mea-
surement" dialog box.
5. In the "ACLR Setup" dialog box, set up a single TX channel with the channel band-
width 1.23 MHz.
Figure 6-40: Measurement of the FSW's intrinsic noise power in a 1.23 MHz channel bandwidth.
If the results do not meet your expectations, or if you want to minimize the measure-
ment duration, try the following methods to optimize the measurement:
● Only activate as many adjacent channels as necessary to minimize the required
span and thus the required measurement time for the measurement.
● Increase the RBW to minimize the measurement time; however, consider the
requirements of the standard if you need to measure according to standard! The
automatic settings are always according to standard.
● Take advantage of the speed optimization mode in the "Sweep" settings if you do
not require the larger dynamic range (see "Optimization" on page 506).
● Reduce the "Sweep Time" and thus the amount of data to be captured and calcu-
lated; however, consider the requirements regarding the standard deviation.
● To improve the stability of the measured results, increase the "Sweep Time",
which also leads to more averaging steps.
● Instead of trace averaging, use an RMS detector with a higher "Sweep Time" to
obtain better average power results in less time.
● To determine a channel power level quickly, use the Time domain power mea-
surement (TDP) rather than a Channel Power measurement. The TDP measure-
ment is a zero span measurement where the sweep time determines the measure-
ment time. Due to the FFT measurement, duplicate averaging is performed, provid-
ing very stable results very quickly.
Note, however, that for TDP measurements, channel filters are not available and a
fixed RBW is used. Thus, the measurement may not be according to standard for
some test cases.
When using predefined standards for ACLR measurement, the test parameters for the
channel and adjacent-channel measurements are configured automatically.
You can select a predefined standard via "CP / ACLR Standard" in the "Ch Power"
menu or the selection list in the "General Settings" tab of the "ACLR Setup" dialog box
(see "Standard" on page 168).
Table 6-9: Predefined CP / ACLR standards with remote command parameters
None NONE
CDMA2000 S2CDma
WIMAX WIMax
WIBRO WIBRo
GSM GSM
TETRA TETRa
PDC PDC
PHS PHS
CDPD CDPD
APCO-25 P2 PAPCo25
For the FSW, the channel spacing is defined as the distance between the center fre-
quency of the adjacent channel and the center frequency of the transmission channel.
The definition of the adjacent-channel spacing in standards IS95C and CDMA 2000 is
different. These standards define the adjacent-channel spacing from the center of the
transmission channel to the closest border of the adjacent channel. This definition is
also used by the FSW for the standards marked with an asterisk *).
In addition to the predefined standards, some user standards with specific measure-
ment settings for common ACLR measurements are provided in XML files on the
instrument in the
C:\Program Files (x86)\Rohde-Schwarz\FSW\<version>\acp_std direc-
tory.
In particular, a sample file (MSR_ACLRExample.xml) is provided for an MSR ACLR
measurement. It sets up the measurement for the MSR signal generator waveform
described in the file
C:\R_S\INSTR\USER\waveform\MSRA_GSM_WCDMA_LTE_GSM.wv.
Furthermore, the following XML files are provided:
5GNR\DL
● 5GNR\DL\5GNR_DL_FR1_20MHz
● 5GNR\DL\5GNR_DL_FR1_100MHz
● 5GNR\DL\5GNR_DL_FR2_100MHz
● 5GNR\DL\5GNR_DL_FR2_200MHz
5GNR\UL
● 5GNR\UL\5GNR_UL_FR1_20MHz
● 5GNR\UL\5GNR_UL_FR1_100MHz
● 5GNR\UL\5GNR_UL_FR2_100MHz
● 5GNR\UL\5GNR_UL_FR2_200MHz
LTE\DL
● LTE\DL\LTE_DL_5MHZ.XML
● LTE\DL\LTE_DL_10MHZ.XML
● LTE\DL\LTE_DL_15MHZ.XML
● LTE\DL\LTE_DL_20MHZ.XML
LTE\UL
● LTE\UL\LTE_UL_5MHZ.XML
● LTE\UL\LTE_UL_10MHZ.XML
● LTE\UL\LTE_UL_15MHZ.XML
● LTE\UL\LTE_UL_20MHZ.XML
WLAN
● WLAN\802_11ac\802_11ac_20MHZ.XML
● WLAN\802_11ac\802_11ac_40MHZ.XML
● WLAN\802_11ac\802_11ac_80MHZ.XML
● WLAN\802_11ac\802_11ac_160MHZ.XML
The largest signal in the frequency span is the carrier. When you activate the C/N or
C/N0 function, the FSW searches the (unmodulated) carrier using a peak detector. The
carrier is marked using a fixed reference marker ("FXD").
To determine the noise power, the FSW analyzes a channel with a defined bandwidth
at the defined center frequency. The FSW integrates the power within this channel to
obtain the noise power level. If the carrier is within this channel, you have to switch off
the carrier to determine the correct noise power level. To determine the noise power,
the FSW requires an RMS detector. To switch detectors, you must adjust the settings
between the two measurements (see "Adjust Settings" on page 211).
The FSW subtracts the noise power of the channel from the maximum carrier signal
level. For a C/N0 measurement, the FSW normalizes the result to a 1 Hz bandwidth.
The carrier-to-noise measurements are only available in the frequency domain (span
>0).
Frequency Span
To measure the carrier-to-noise ratio correctly, set the frequency span to approximately
twice the channel bandwidth. The "Adjust Settings" function automatically uses that
value.
As a result of the carrier-to-noise measurement, the evaluated bandwidth and the cal-
culated C/N ratio are displayed in the result window. The fixed reference marker for the
(unmodulated) carrier is indicated in the diagram.
Remote command:
CALC:MARK:FUNC:POW:RES? CN
CALC:MARK:FUNC:POW:RES? CN0
See CALCulate<n>:MARKer<m>:FUNCtion:POWer<sb>:RESult? on page 915.
Access: "Overview" > "Select Measurement" > "C/N"/"C/N0" > "Carrier Noise Config"
Both a carrier-to-noise ratio (C/N) and a carrier-to-noise ratio in relation to the band-
width (C/N0) measurement are available.
The remote commands required to perform these tasks are described in Sec-
tion 13.5.4, "Measuring the carrier-to-noise ratio", on page 982.
C/N.............................................................................................................................. 210
C/N0............................................................................................................................ 211
Channel Bandwidth..................................................................................................... 211
Adjust Settings.............................................................................................................211
C/N
Switches the measurement of the carrier/noise ratio on or off. If no marker is active,
marker 1 is activated.
The measurement is performed on the trace that marker 1 is assigned to. To shift
marker 1 and measure another trace, use "Marker To Trace" in the "Marker" menu (see
"Assigning the Marker to a Trace" on page 346).
Remote command:
CALCulate<n>:MARKer<m>:FUNCtion:POWer<sb>:SELect on page 916
CALCulate<n>:MARKer<m>:FUNCtion:POWer<sb>:RESult? on page 915
CALCulate<n>:MARKer<m>:FUNCtion:POWer<sb>[:STATe] on page 917
C/N0
Switches the measurement of the carrier/noise ratio with reference to a 1 Hz bandwidth
on or off. If no marker is active, marker 1 is activated.
The measurement is performed on the trace that marker 1 is assigned to. To shift
marker 1 and measure another trace, use "Marker To Trace" in the "Marker" menu (see
"Assigning the Marker to a Trace" on page 346).
Remote command:
CALCulate<n>:MARKer<m>:FUNCtion:POWer<sb>:SELect on page 916
CALCulate<n>:MARKer<m>:FUNCtion:POWer<sb>:RESult? on page 915
CALCulate<n>:MARKer<m>:FUNCtion:POWer<sb>[:STATe] on page 917
Channel Bandwidth
Defines the channel bandwidth.
The default setting is 14 kHz.
Remote command:
[SENSe:]POWer:ACHannel:BANDwidth[:CHANnel<ch>] on page 922
Adjust Settings
Enables the RMS detector and adjusts the span to the selected channel bandwidth
according to:
2 * channel bandwidth
The adjustment is performed once. If necessary, you can change the setting later.
Remote command:
[SENSe:]POWer:ACHannel:PRESet on page 917
1. Select [MEAS].
The fixed reference marker for the (unmodulated) carrier is indicated in the dia-
gram.
5. If the carrier signal is located within the analyzed channel bandwidth, switch off the
carrier signal so that only the noise is displayed in the channel.
6. To optimize the settings for the selected channel configuration and use the RMS
detector, select "Adjust Settings".
Measurement principle
The bandwidth containing 99% of the signal power is to be determined, for example.
The algorithm first calculates the total power of all displayed points of the trace. In the
next step, the points from the right edge of the trace are summed up until 0.5 % of the
total power is reached. Auxiliary marker 1 is positioned at the corresponding frequency.
Then the points from the left edge of the trace are summed up until 0.5 % of the power
is reached. Auxiliary marker 2 is positioned at this point. 99 % of the power is now
between the two markers. The distance between the two frequency markers is the
occupied bandwidth which is displayed in the marker field.
OBW within defined search limits - multicarrier OBW measurement in one sweep
The occupied bandwidth of the signal can also be determined within defined search
limits instead of for the entire signal. Thus, only a single sweep is required to determine
the OBW for a multicarrier signal. To do so, search limits are defined for an individual
carrier and the OBW measurement is restricted to the frequency range contained
within those limits. Then the search limits are adapted for the next carrier and the OBW
is automatically recalculated for the new range.
For step-by-step instructions, see "How to determine the OBW for a multicarrier signal
using search limits" on page 217.
Prerequisites
To ensure correct power measurement, especially for noise signals, and to obtain the
correct occupied bandwidth, the following prerequisites and settings are necessary:
● Only the signal to be measured is displayed in the window, or search limits are
defined to include only one (carrier) signal. An additional signal would falsify the
measurement.
● RBW << occupied bandwidth (approx. 1/20 of occupied bandwidth, for voice com-
munication type: 300 Hz or 1 kHz)
● VBW ≥ 3 x RBW
● RMS detector
● Span ≥ 2 to 3 x occupied bandwidth
Some of the measurement specifications (e.g. PDC, RCR STD-27B) require measure-
ment of the occupied bandwidth using a peak detector. The detector setting of the
FSW has to be changed accordingly then.
As a result of the OBW measurement the occupied bandwidth ("Occ Bw") is indicated
in the marker results. Furthermore, the marker at the center frequency and the tempo-
rary markers are indicated.
The measurement is performed on the trace with marker 1. In order to evaluate
another trace, marker 1 must be placed on another trace (see Assigning the Marker to
a Trace).
The OBW calculation is repeated if the Search Limits are changed, without performing
a new sweep. Thus, the OBW for a multicarrier signal can be determined using only
one sweep.
Centroid frequency
The centroid frequency is defined as the point in the center of the occupied bandwidth,
calculated using the temporary OBW markers T1 and T2. This frequency is indicated
as a function result ("Occ Bw Centroid") in the marker table.
Frequency offset
The offset of the calculated centroid frequency to the defined center frequency of the
FSW is indicated as a function result ("Occ Bw Freq Offset") in the marker table.
Remote command:
The determined occupied bandwidth can also be queried using the remote command
CALC:MARK:FUNC:POW:RES? OBW or CALC:MARK:FUNC:POW:RES? AOBW. While
the OBW parameter returns only the occupied bandwidth, the AOBW parameter also
returns the position and level of the temporary markers T1 and T2 used to calculate the
occupied bandwidth.
CALC:MARK:FUNC:POW:SEL OBW, see CALCulate<n>:MARKer<m>:FUNCtion:
POWer<sb>:SELect on page 916
CALCulate<n>:MARKer<m>:FUNCtion:POWer<sb>[:STATe] on page 917
CALC:MARK:FUNC:POW:RES? OBW, see CALCulate<n>:MARKer<m>:FUNCtion:
POWer<sb>:RESult? on page 915
CALC:MARK:FUNC:POW:RES? COBW, see CALCulate<n>:MARKer<m>:FUNCtion:
POWer<sb>:RESult? on page 915
Access: "Overview" > "Select Measurement" > "OBW" > "OBW Config"
The remote commands required to perform these tasks are described in Sec-
tion 13.5.5, "Measuring the occupied bandwidth", on page 983.
% Power Bandwidth.................................................................................................... 215
Channel Bandwidth..................................................................................................... 216
Adjust Settings............................................................................................................ 216
Search Limits (Left / Right)..........................................................................................216
Search Limits Off.........................................................................................................216
% Power Bandwidth
Defines the percentage of total power in the displayed frequency range which defines
the occupied bandwidth. Values from 10 % to 99.9 % are allowed.
Remote command:
[SENSe:]POWer:BANDwidth on page 984
Channel Bandwidth
Defines the channel bandwidth for the transmission channel in single-carrier measure-
ments. This bandwidth is used to optimize the test parameters (for details see "Adjust
Settings" on page 216). The default setting is 14 kHz.
For measurements according to a specific transmission standard, define the bandwidth
specified by the standard for the transmission channel.
For multicarrier measurements, this setting is irrelevant.
Remote command:
[SENSe:]POWer:ACHannel:BANDwidth[:CHANnel<ch>] on page 922
Adjust Settings
Optimizes the instrument settings for the measurement of the occupied bandwidth
according to the specified channel bandwidth.
This function is only useful for single carrier measurements.
All instrument settings relevant for power measurement within a specific frequency
range are optimized:
● Frequency span: 3 × channel bandwidth
● RBW ≤ 1/40 of channel bandwidth
● VBW ≥ 3 × RBW
● Detector: RMS
The reference level is not affected by "Adjust Settings". For an optimum dynamic
range,select the reference level such that the signal maximum is close to the reference
level.
(See "Setting the Reference Level Automatically (Auto Level)" on page 488).
The adjustment is carried out only once. If necessary, the instrument settings can be
changed later.
Remote command:
[SENSe:]POWer:ACHannel:PRESet on page 917
For remote operation, see Section 13.5.5.2, "Programming example: OBW measure-
ment", on page 984.
4. Define the percentage of power ("% Power Bandwidth") that defines the bandwidth
to be determined.
6. To optimize the settings for the selected channel configuration, select "Adjust Set-
tings".
7. Start a sweep.
The result is displayed as OBW in the marker results.
How to determine the OBW for a multicarrier signal using search limits
1. Press [MEAS] or select "Select Measurement" in the "Overview".
4. Define the percentage of power ("% Power Bandwidth") that defines the bandwidth
to be determined.
5. Define search limits so the search area contains only the first carrier signal:
a) Enter values for the left or right limits, or both.
b) Enable the use of the required limits.
6. Start a sweep.
The result for the first carrier is displayed as OBW in the marker results.
7. Change the search limits so the search area contains the next carrier signal as
described in step 5.
The OBW is recalculated and the result for the next carrier is displayed. A new
sweep is not necessary!
In the following example, the bandwidth that occupies 99 % of the total power of a PDC
signal at 800 MHz, level 0 dBm is measured.
9. Optimize the settings for the selected channel configuration by selecting "Adjust
Settings".
10. Adjust the reference level to the measured total power by selecting "Auto Level" in
the [Auto set] menu.
11. The PDC standard requires the peak detector for OBW measurement. In the
"Traces" configuration dialog, set the trace detector to "PositivePeak".
The noise power ratio is defined as the relationship between the total power density in
a channel and the noise power density. The noise power ratio is commonly used to
describe the distortion caused by in-band multi-carrier intermodulation in a wideband
satellite channel. A satellite can be considered to be a "transparent transponder". It
receives the uplink signal, amplifies it, translates the frequency, amplifies it more, and
finally retransmits it. Typically, the signal contains a large number of carriers. To mea-
sure the in-band distortions of specific carriers in a satellite DUT, notch filters are inser-
ted inside the channel. Notch filters remove the effects of the underlying subcarriers
from the signal. Thus, the distortion of these carriers caused by the others can be
determined.
The FSW noise power ratio measurement allows you to specify your satellite channel
and up to 25 notch filters in your measurement setup. For a more general measure-
ment, the bandwidth on which the total power density is based can be selected freely.
As a result, the channel power density, the notch power density, and the noise power
ratio are calculated.
Some background knowledge on basic terms and principles used in noise power ratio
measurements is provided here for a better understanding of the required configuration
settings.
Channel Bandwidth
Integration Bandwidth
Notch 1 Notch 2
Figure 6-41: Auto mode: Integration bandwidth = channel bandwidth (notches deducted)
In manual measurement, however, the notch power is not deducted. In manual mode,
the application simply integrates all measured powered levels over the integration
bandwidth, including the power levels measured within the notches.
Channel Bandwidth
Integration Bandwidth
Notch 1 Notch 2
Figure 6-42: Manual mode: Integration bandwidth ≠ channel bandwidth (notches not deducted)
The FSW shows the measurement results in a diagram and a table in numerical form.
The diagram consists of several elements.
● A horizontal blue bar at the bottom of the diagram indicates the channel bandwidth.
● Two vertical blue lines indicate the integration range or integration bandwidth. It is
the same as the channel bandwidth by default (it is labeled "channel bandwidth" in
that case).
● Vertical green lines indicate notches and their bandwidth. The number of displayed
notches is variable.
In the result summary, the following results are provided for the specified channel and
individual notches:
Table 6-10: Noise Power Ratio result summary parameters
Parameter Description
"Channel BW" (auto Specified channel bandwidth or manually defined integration bandwidth used
mode) / "Integration BW" as basis for power density calculation in total channel or notch
Parameter Description
"Channel Power" / "Power Power measured in channel or notch - absolute value or density (= power
density" divided by the "Channel BW"/"Integration BW" in dBm/Hz)
"NPR" (Notches only:) Ratio of total channel power density to notch power density in
dB
Remote command:
Channel power (density), notch power density, power ratio:
CALCulate<n>:NPRatio:RESult? on page 999
Measured power values for each sweep point (by default 1001):
TRAC:DATA? TRACe1 (see TRACe<n>[:DATA] on page 1262).
Access: "Overview" > "Select Measurement" > "Noise Power Measurement" > "NPR
Config" > "Noise Power Ratio" tab
The FSW noise power ratio measurement allows you to specify your satellite channel
and up to 25 notch filters in your measurement setup. For a more general measure-
ment, the bandwidth on which the total power density is based can be selected freely.
Figure 6-43: Noise Power Ratio configuration dialog with a signal generator connected
An LED next to a setting indicates whether the setting was adjusted on the connected
generator successfully. They are only available if a valid generator IP address is detec-
ted (see "IP Address" on page 228).
The LED indicates the following states:
● green: setting on the FSW is valid and was successfully applied on the signal gen-
erator
● red: control error, for example because the specified value cannot be applied on
the signal generator
● gray: signal generator control off
Note that if you change the setting on the generator manually, the analyzer does not
adapt the setting automatically. The green LED for a previous successful transmission
does not change.
Channel Bandwidth
Defines the channel bandwidth on which the total power density is based. The band-
width is positioned around the currently defined Center Frequency.
To specify a different bandwidth for total power density calculation, or to shift the band-
width, define an Integration Bandwidth manually.
Remote command:
[SENSe:]NPRatio:CHANnel:BWIDth on page 985
Integration Bandwidth
Defines a bandwidth other than the channel bandwidth to be used for total power den-
sity calculation. Select the "Manual" option and define the bandwidth manually.
In auto mode, the integration bandwidth is the same as the channel bandwidth.
Notches are deducted from the results.
In manual mode, you can customize the integration bandwidth. The results include the
power levels measured within notches, however.
A "Frequency Offset" shifts the bandwidth away from the currently defined Center Fre-
quency.
Remote command:
[SENSe:]NPRatio:CHANnel:INTegration:BWIDth on page 986
[SENSe:]NPRatio:CHANnel:INTegration:AUTO on page 986
[SENSe:]NPRatio:CHANnel:INTegration:FREQuency:OFFSet on page 987
Number of Notches
Defines the number of notches for which results are determined. A maximum of 25
notches can be defined. Note that even if bandwidths for further notches are defined,
only the number specified here are actually calculated and displayed.
If Generator Control State is enabled in the generator settings, the specified number of
notches is sent to the generator on upload. An LED next to the setting indicates
whether the setting was adjusted on the connected instrument successfully.
See Section 6.5.3, "NPR results", on page 221 for more information about how notches
are treated in the measurement.
Remote command:
[SENSe:]NPRatio:NOTCh<notch>:COUNt on page 988
CONFigure:GENerator:NPRatio:NOTCh<notch>:COUNt:CSTate? on page 995
If a variable frequency definition is used (see Section 6.5.6, "Generator frequency cou-
pling", on page 231), the defined factor (Numerator / Denominator) is also applied to
the absolute notch bandwidth.
Notch_BWGen = Numerator / Denominator * Notch_BWAnalyzer
Remote command:
[SENSe:]NPRatio:NOTCh<notch>:BWIDth[:ABSolute] on page 988
[SENSe:]NPRatio:NOTCh<notch>:BWIDth:RELative on page 987
CONFigure:GENerator:NPRatio:NOTCh<notch>:BWIDth:ABSolute:CSTate?
on page 993
Access: "Overview" > "Select Measurement" > "Noise Power Measurement" > "NPR
Config" > "Generator Setup" tab
The general settings required to control a connected signal generator by the FSW are
defined here. The control settings are only available if a connection to a signal genera-
tor has been established.
The individual settings are only available if generator control is enabled.
For each setting, an LED indicates whether the setting was adjusted on the connected
generator successfully. Thus, you can quickly detect the cause of possible errors.
The LED indicates the following states:
● green: connection established and all settings valid
● red: control error, for example because a specified value cannot be applied on the
signal generator
● gray: signal generator control off
If you change the setting on the generator manually after an automatic setting, the LED
might not indicate the correct state.
Remote command:
CONFigure:GENerator:NPRatio:STATe:CSTate? on page 997
IP Address...................................................................................................................228
└ IP Address / Computer Name....................................................................... 228
└ Connect/Disconnect......................................................................................228
Generator Control State.............................................................................................. 229
Path RF/ Path BB........................................................................................................229
RF Output State.......................................................................................................... 229
Frequency................................................................................................................... 230
Level (RMS)................................................................................................................ 230
Level Offset................................................................................................................. 230
Reference Frequency..................................................................................................230
Standard......................................................................................................................230
IP Address
Indicates the state and address of a connected signal generator.
The LED indicates the following connection states:
● green: connection established to compatible generator
● red: connection could not be established, possibly due to an incompatible instru-
ment
● gray: no signal generator connected
Select the TCPIP address or "Configure" to define the connection information for the
connected signal generator.
Remote command:
CONFigure:GENerator:CONNection:CSTate? on page 1459
Connect/Disconnect ← IP Address
The FSW attempts to establish a connection to the signal generator, or disconnects it.
RF Output State
To protect the instrument from possibly erroneous or damaging settings, you must
manually activate the RF output on the signal generator to start providing a signal.
Check all settings on the signal generator, in particular the level settings, before acti-
vating the RF output.
A red LED on the "Generator Control" tab indicates a setting error on the generator.
Remote command:
CONFigure:GENerator:RFOutput[:STATe] on page 998
CONFigure:GENerator:NPRatio:RFOutput:STATe:CSTate? on page 996
Frequency
Defines the frequency of the signal provided by the signal generator.
If the Generator Frequency Coupling State is active, this value is read-only and indi-
cates the resulting frequency setting on the generator.
Remote command:
CONFigure:GENerator:FREQuency:CENTer on page 990
CONFigure:GENerator:NPRatio:FREQuency:CENTer:CSTate? on page 991
Level (RMS)
(Default:) The specified power level is used for the output power by the connected sig-
nal generator.
Remote command:
CONFigure:GENerator:POWer:LEVel on page 998
CONFigure:GENerator:NPRatio:POWer:LEVel:CSTate? on page 995
Level Offset
Defines a fixed offset in the power level used by the generator, for example due to a
gain from the DUT.
Remote command:
CONFigure:GENerator:POWer:LEVel:OFFSet on page 998
CONFigure:GENerator:NPRatio:POWer:LEVel:OFFSet:CSTate? on page 996
Reference Frequency
Selects the source of the generator reference frequency.
The internal reference is that of the signal generator itself.
An external reference is provided via the EXT connectors on the generator, for exam-
ple by the FSW.
Remote command:
CONFigure:GENerator:EXTernal:ROSCillator on page 989
CONFigure:GENerator:NPRatio:EXTernal:ROSCillator:CSTate?
on page 991
Standard
For reference only: the standard currently used by the signal generator. If no standard
is defined on the generator, notched signals are not available (see "Generator Notch
Filter State" on page 224).
Remote command:
CONFigure:GENerator:NPRatio:BB:STANdard? on page 990
Access: "Overview" > "Select Measurement" > "Noise Power Measurement" > "NPR
Config" > "Generator Freq Coupling" tab
These settings are only available if generator control is enabled (see "Generator Con-
trol State" on page 229).
Instead of defining a fixed frequency to be used by the signal generator, you can cou-
ple the frequency of the generator to the analyzer using a variable frequency definition.
Note that the frequency definition also affects the (absolute) Notch Bandwidth (Abso-
lute / Relative to Channel BW) and the "Frequency Offset per Notch" on page 224.
The overall status of the frequency coupling is indicated by an LED next to the fre-
quency definition.
The LED indicates the following states:
● green: frequency setting valid
● red: frequency value cannot be applied on the signal generator
● gray: signal generator control or coupling off
fGen
Indicates the resulting frequency setting on the generator, depending on the other fre-
quency parameters.
The generator frequency is defined as:
fGen = [fAnalyzer * Numerator / Denominator] + Frequency Offset
Any changes to one of the interdependent parameters automatically affect the calcula-
ted signal levels on the connected generator.
If Generator Frequency Coupling State is disabled, define a fixed frequency to be used
by the generator.
Remote command:
CONFigure:GENerator:FREQuency:CENTer on page 990
CONFigure:GENerator:NPRatio:FREQuency:CENTer:CSTate? on page 991
fAnalyzer
Sets the analyzer (center) frequency, which is used as a basis for the variable fre-
quency definition.
Remote command:
[SENSe:]FREQuency:CENTer on page 1195
Numerator
Defines the numerator of the frequency-defining factor.
Note that this factor also affects the (absolute) Notch Bandwidth (Absolute / Relative to
Channel BW) and the "Frequency Offset per Notch" on page 224.
Remote command:
CONFigure:GENerator:NPRatio:FREQuency[:FACTor]:NUMerator
on page 993
Denominator
Defines the denominator of the frequency-defining factor.
Note that this factor also affects the (absolute) Notch Bandwidth (Absolute / Relative to
Channel BW) and the "Frequency Offset per Notch" on page 224.
Remote command:
CONFigure:GENerator:NPRatio:FREQuency[:FACTor]:DENominator
on page 992
Frequency Offset
Defines a fixed offset to be applied to the generator frequency.
Remote command:
CONFigure:GENerator:NPRatio:FREQuency:OFFSet on page 992
Measuring the noise power ratio is a very easy and straightforward task with the FSW.
9. For each notch, define the bandwidth (absolute or relative to the channel band-
width) and its position (relative to the center frequency).
The channel and notches are indicated in the spectrum diagram, and the power
results are indicated in the result summary.
The Spectrum Emission Mask (SEM) measurement defines a measurement that moni-
tors compliance with a spectral mask. The mask is defined with reference to the input
signal power. The FSW allows for a flexible definition of all parameters in the SEM
measurement. The analyzer performs measurements in predefined frequency ranges
with settings that can be specified individually for each of these ranges.
In the basic Spectrum application, spectrum emissions can be measured for multiple
sub blocks of channels, where the sub blocks can include gaps or overlap, and define
separate masks. Radio signals using multiple standards can also be analyzed.
SEM measurement configurations can be saved to an XML file which can then be
exported to another application or loaded on the FSW again later. Some predefined
XML files are provided that contain ranges and parameters according to the selected
standard.
To improve the performance of the FSW for spectrum emission mask measurements, a
"Fast SEM" mode is available.
A special limit check for SEM measurements allows for monitoring compliance of the
spectrum.
Spectrum Emission Mask measurements are typically performed to ensure that modu-
lated signals remain within the valid signal level ranges. These ranges are defined by a
particular transmission standard, both in the transmission channel and neighboring
channels. Any violations of the mask can interfere with other transmissions.
The 3GPP TS 34.122 standard, for example, defines a mask for emissions outside the
transmission channel. This mask is defined relative to the input signal power. Three
frequency ranges to each side of the transmission channel are defined.
As a result of the Spectrum Emission Mask measurement, the following results are dis-
played in a diagram (see also Section 6.6.4.2, "Limit lines in SEM measurements",
on page 242):
● The measured signal levels
● The result of the limit check (mask monitoring)
● The defined limit lines
● TX channel power "P"
● The used power class
Multi-SEM measurements
Multi-SEM measurements are SEM measurements with more than one sub block. In
these measurements, each sub block has its own power class definitions. In this case,
the power class is not indicated in the graphical result displays.
Example:
For example, in Figure 6-44, "31 < P < 39" is indicated as the used power class is
defined from 31 to 39.
In addition to the graphical results of the SEM measurement displayed in the diagram,
a result summary is displayed to evaluate the limit check results (see also Sec-
tion 6.6.4.2, "Limit lines in SEM measurements", on page 242).
The following information is provided in the result summary:
Label Description
General information
Range results
"Range Low" Start of the frequency range the peak value was found in
"Range Up" Frequency range end the peak value was found in
Label Description
"Power Rel" Peak power level within the range, relative to the "Tx Power"
"ΔLimit" Deviation of the peak power level from the limit line
You can define in which detail the data is displayed in the result summary in the "List
Evaluation" settings (see Section 6.6.5.7, "List evaluation (results configuration)",
on page 266). By default, one peak per range is displayed. However, you can change
the settings to display only peaks that exceed a threshold ("Margin").
Detected peaks are not only listed in the Result Summary, they are also indicated by
colored squares in the diagram (optionally, see Show Peaks in the "List Evaluation"
settings).
Furthermore, you can export the results of the result summary to a file which can be
exported to another application for further analysis.
Some background knowledge on basic terms and principles used in SEM measure-
ments is provided here for a better understanding of the required configuration set-
tings.
● Ranges and range settings................................................................................... 240
● Limit lines in SEM measurements.........................................................................242
● Fast SEM measurements......................................................................................244
● Multi-standard radio (MSR) SEM measurements................................................. 245
● SEM with multiple sub blocks ("Multi-SEM")......................................................... 246
In the Spectrum Emission Mask measurements, a range defines a segment for which
you can define the following parameters separately:
● Start and stop frequency
● RBW
● VBW
● "Sweep Time"
● "Sweep Points"
● Reference level
● Attenuator settings
● Preamplifier settings
● Transducer settings
● Limit values
Via the sweep list, you define the ranges and their settings. For details on settings,
refer to Section 6.6.5.1, "Sweep List", on page 250.
For details on defining the limits (masks), see Section 6.6.4.2, "Limit lines in SEM mea-
surements", on page 242.
Range definition
After a preset, the sweep list contains a set of default ranges and parameters. For
each range, you can change the parameters listed above. You can insert or delete
ranges.
The changes of the sweep list are only kept until you load another parameter set (by
pressing [PRESET] or by loading an XML file). If you want a parameter set to be avail-
able permanently, create an XML file for this configuration (for details refer to "How to
save a user-defined SEM settings file" on page 271).
If you load one of the provided XML files, the sweep list contains ranges and parame-
ters according to the selected standard.
Reference range
The range containing the center frequency is defined as the reference range for all
other ranges in the sweep list. All range limits are defined in relation to the reference
range. The TX power used as a reference for all power level results in the result sum-
mary is also calculated for this reference range. You can define whether the power
used for reference is the peak power level or the integrated power of the reference
range. In the "Sweep List", the reference range is highlighted in blue and cannot be
deleted.
Rules
The following rules apply to ranges:
● The minimum span of a range is 20 Hz.
● The individual ranges must not overlap (but can have gaps).
Sweep points
You can define a minimum number of sweep points for each range. The total number
of available sweep points is then distributed among the ranges in consideration of the
minimum values. If the total number of sweep points is not enough to satisfy the mini-
mum sweep point requirements in all ranges, the FSW adjusts the global number of
Sweep Points accordingly. By default, each range has a minimum of one sweep point.
This allows you to increase the resolution within a specific range for detailed analysis.
You do not have to increase the overall number of sweep points and thus the measure-
ment time for the SEM measurement.
Symmetrical ranges
You can easily define a sweep list with symmetrical range settings, i.e. the ranges to
the left and right of the reference range are defined symmetrically. When symmetrical
setup is activated, the current sweep list configuration is changed to define a symmetri-
cal setup regarding the reference range. The number of ranges to the left of the refer-
ence range is reflected to the right, i.e. any missing ranges on the right are inserted,
while superfluous ranges are removed. The values in the ranges to the right of the ref-
erence range are adapted symmetrically to those in the left ranges.
Symmetrical ranges fulfill the conditions required for "Fast SEM" mode (see Sec-
tion 6.6.4.3, "Fast SEM measurements", on page 244).
Power classes
If the signal power level to be monitored varies and the limits vary accordingly, you can
define power classes, which can then be assigned to the frequency ranges. Thus, the
limits for the signal levels can be defined differently for varying input levels. For
instance, for higher input levels a transmission standard can allow for higher power lev-
els in adjacent channels, whereas for lower input levels the allowed deviation can be
stricter. Up to four different power classes can be defined.
For the FSW, the spectrum emission mask is defined using limit lines. Limit lines allow
you to check the measured data (that is, the trace results) against specified limit val-
ues. Generally, it is possible to define limit lines for any measurement in the Spectrum
application application using the [Lines] function. For SEM measurements, however,
special limit lines are available via the "Sweep List", and it is strongly recommended
that you use only these limit line definitions.
In the "Sweep List", you can define a limit line for each power class that varies its level
according to the specified frequency ranges. Special limit lines are automatically
defined for each power class according to the current "Sweep List" settings every time
the settings change. These limit lines are labeled "_SEM_LINE_<xxx>_ABS<0...3>"
and "_SEM_LINE_<xxx>_REL<0...3>", where <xxx> is an index to distinguish limit
lines between different channels.
The limit line defined for the currently used power class is indicated by a red line in the
display. The result of the limit check is indicated at the top of the diagram. Note that
only "Pass" or "Fail" is indicated; a "Margin" function as for general limit lines is not
available.
The indicated limit line depends on the settings in the "Sweep List". Several types of
limit checks are possible:
Table 6-11: Limit check types
"Absolute" Absolute power levels must not Defined by the "Abs Limit Start"/ "Abs Limit
exceed limit line Stop" values for each range
"Relative" Power deviations relative to the TX Defined by the "Rel Limit Start"/ "Rel Limit
channel power must not exceed limit Stop" values (relative to the TX channel
line power), fixed for each range.
"Relative with If the power exceeds both the abso- Defined by the maximum of the absolute or
function f(x)" lute and the relative limits, the check relative start and stop limit values for each
fails (see Relative limit line functions range. Thus, the start or stop point of the limit
below) range, or both, are variable (since the maxi-
mum can vary).
"Abs and Rel" If the power exceeds both the abso- The less strict (higher) limit line is displayed
lute and the relative limits, the check for each range.
fails. If you use a function to define the relative limit
start or stop value, the signal is checked
against an additional condition: the power
must exceed the absolute limit, as well as the
absolute and relative function values.
"Abs or Rel" If the power exceeds either the The stricter (lower) limit line is displayed for
absolute or the relative limits, the each range.
check fails. If you use a function to define the relative limit
start or stop value, the signal is checked
against an additional condition: if the power
exceeds the absolute limit, or the higher of the
absolute and relative function values, the
check fails.
Although a margin functionality is not available for the limit check, a margin (threshold)
for the peak values to be displayed in the Result Summary can be defined. (In the "List
Evaluation" settings, see Section 6.6.5.7, "List evaluation (results configuration)",
on page 266).
To improve the performance of the FSW for spectrum emission mask measurements, a
"Fast SEM" mode is available. If this mode is activated, several consecutive ranges
with identical sweep settings are combined to one sweep internally, which makes the
measurement considerably faster. The displayed results remain unchanged and still
consist of several ranges. Thus, measurement settings that apply only to the results,
such as limits, can nevertheless be defined individually for each range.
Prerequisites
"Fast SEM" mode is available if the following criteria apply:
● The frequency ranges are consecutive, without frequency gaps
● The following sweep settings are identical (for details see Section 6.6.5.1, "Sweep
List", on page 250):
– "Filter Type"
– "RBW"
– "VBW"
– "Sweep Time Mode"
– "Reference Level"
– "RF Attenuation Mode"
– "RF Attenuation"
– "Preamplifier"
Consequences
When the "Fast SEM" mode is activated, the ranges for which these criteria apply are
displayed as one single range. The sweep time is defined as the sum of the individual
sweep times, initially, but can be changed.
If "Symmetrical Setup" mode is active when "Fast SEM" mode is activated, not all
sweep list settings can be configured symmetrically automatically (see also "Symmetri-
cal Setup" on page 256).
Any other changes to the sweep settings of the combined range are applied to each
included range and remain changed even after deactivating "Fast SEM" mode.
Example
In Figure 6-47, a sweep list is shown for which Fast SEM is activated. The formerly five
separately defined ranges are combined to two sweep ranges internally.
Multi-standard radio (MSR) measurements allow you to perform SEM tests on signals
with multiple carriers using different digital standards. MSR measurements are descri-
bed in the specification 3GPP TS 37.141. Various typical combinations of standards for
base station tests are described, e.g. LTE FDD and W-CDMA carriers. By performing
an MSR SEM measurement you can determine if or how the different carriers affect
each other, i.e. if unwanted emissions occur. On the FSW, the MSR SEM measure-
ment is a standard measurement as for single carriers. The MSR settings merely pro-
vide a convenient way of configuring the sweep list for all required ranges according to
the specification quickly.
Refined settings allow the FSW to calculate the SEM limits according to standard
3GPP 37.141 V12.2.0, which distinguishes between base station configurations and
power values.
In the Spectrum application application only, spectrum emissions can be measured for
multiple sub blocks of channels (also referred to as a "Multi-SEM" measurement). Sub
blocks are a set of multiple ranges around a defined center frequency (carrier). Multiple
sub blocks can include gaps or overlap, and each sub block defines a separate mask.
In the overlapping masks, multi-limit lines are calculated. Up to 8 sub blocks (with 7
gaps) can be defined. For each sub block, the familiar configuration settings concern-
ing ranges, limit lines etc. can be defined individually.
For setups with more than one sub block, frequencies are defined relative to the center
frequency of the reference ranges for the individual sub blocks. However, in the result
summary, frequencies are indicated as absolute values. Relative frequencies that refer
to different reference ranges would be inconvenient and difficult to analyze.
● For the ranges in which multiple limit lines are significant, a range-specific function
determines the behavior of the limit check
Initial situation: overlapping ranges Result: Subranges 4a and 5a are created left and right of the
mid-frequency;
Range 4 ("None") + Range 5 ("None") overlap and cross the
mid-frequency between sub blocks 1 and 2 For subrange 4a: limit line and parameters of range 4 apply
For subrange 5a: limit line and parameters of range 5 apply
Multi-SEM configuration
In the Spectrum application application only, spectrum emissions can be measured for
multiple sub blocks of channels (see Section 6.6.4.5, "SEM with multiple sub blocks
("Multi-SEM")", on page 246). Up to 8 sub blocks (with 7 gaps) can be defined. For
each sub block, the familiar configuration settings concerning ranges, limit lines etc.
can be defined in individual tabs. In addition, settings on the sub blocks themselves
must be configured in the "Sub Block" tab of the "Spectrum Emission Mask" configura-
tion dialog box (see Section 6.6.5.2, "Multi-SEM (sub block) settings", on page 257).
The following settings are available in individual tabs of the "Spectrum Emission Mask"
configuration dialog box.
● Sweep List.............................................................................................................250
● Multi-SEM (sub block) settings..............................................................................257
● Reference range................................................................................................... 258
● Power classes....................................................................................................... 259
● MSR settings.........................................................................................................261
● Standard files........................................................................................................ 264
● List evaluation (results configuration)....................................................................266
Access: "Overview" > "Select Measurement" > "Spectrum Emission Mask" > "Sweep
List"
For SEM measurements, the input signal is split into several frequency ranges which
are swept individually and for which different limitations apply. You configure the indi-
vidual frequency ranges and mask limits in the "Sweep List".
If you edit the sweep list, always follow the rules and consider the limitations described
in Section 6.6.4.1, "Ranges and range settings", on page 240.
To change the start/stop frequency of the first or last range, respectively, select the
appropriate span in the [SPAN] configuration dialog. You can set a span that is smaller
than the overall span of the ranges. In this case, the measurement includes only the
ranges that lie within the defined span and have a minimum span of 20 Hz. The first
and last ranges are adapted to the given span as long as the minimum span of 20 Hz
is not violated.
Define frequency values for each range relative to the center frequency. Center the ref-
erence range on the center frequency. The current "Tx Bandwidth" defines the mini-
mum span of the reference range (see "Channel Power Settings" on page 259).
Remote command:
[SENSe:]ESPectrum<sb>:RANGe<ri>[:FREQuency]:STARt on page 1008
[SENSe:]ESPectrum<sb>:RANGe<ri>[:FREQuency]:STOP on page 1009
Fast SEM
Activates "Fast SEM" mode for all ranges in the sweep list. For details, see Sec-
tion 6.6.4.3, "Fast SEM measurements", on page 244.
Note: If you deactivate "Fast SEM" mode while "Symmetrical Setup" mode is on,
"Symmetrical Setup" mode is automatically also deactivated.
If you activate "Fast SEM" mode while "Symmetrical Setup" mode is on, not all range
settings can be configured symmetrically automatically.
Remote command:
[SENSe:]ESPectrum<sb>:HSPeed on page 1005
Filter Type
Sets the filter type for this range.
For details on filter types, see Section 7.5.1.6, "Which data may pass: filter types",
on page 498.
Remote command:
[SENSe:]ESPectrum<sb>:RANGe<ri>:FILTer:TYPE on page 1007
RBW
Sets the resolution bandwidth for this range.
For details on the RBW, see Section 7.5.1.1, "Separating signals by selecting an
appropriate resolution bandwidth", on page 494.
Remote command:
[SENSe:]ESPectrum<sb>:RANGe<ri>:BANDwidth:RESolution on page 1006
VBW
Sets the video bandwidth for this range.
For details on the VBW, see Section 7.5.1.2, "Smoothing the trace using the video
bandwidth", on page 495.
Remote command:
[SENSe:]ESPectrum<sb>:RANGe<ri>:BANDwidth:VIDeo on page 1006
For details on the sweep time mode, see Section 7.5.1.7, "How long the data is mea-
sured: Sweep Time", on page 499
Remote command:
[SENSe:]ESPectrum<sb>:RANGe<ri>:SWEep:TIME:AUTO on page 1019
Sweep Time
Sets the sweep time value for the range.
For details on the sweep time, see Section 7.5.1.7, "How long the data is measured:
Sweep Time", on page 499
Remote command:
[SENSe:]ESPectrum<sb>:RANGe<ri>:SWEep:TIME on page 1019
Ref Level
Sets the reference level for the range.
For details on the reference level, see Section 7.4.1.1, "Reference level", on page 481.
Remote command:
[SENSe:]ESPectrum<sb>:RANGe<ri>:RLEVel on page 1018
RF Att Mode
Activates or deactivates the auto mode for RF attenuation.
For details on attenuation, see Section 7.4.1.2, "RF attenuation", on page 482.
Note: If an external frontend is active (see External frontend settings), the required
attenuation is applied to the input of the external frontend, not the FSW. However, you
can configure additional attenuation for the analyzer (see SPA: RF Attenuation Mode /
SPA: RF Attenuation). When using an external frontend, only mechanical attenuation is
available.
For more information, see "External frontend attenuation vs. analyzer attenuation"
on page 448.
For more information, see the FSW User Manual.
Remote command:
[SENSe:]ESPectrum<sb>:RANGe<ri>:INPut:ATTenuation:AUTO on page 1009
RF Attenuation
Sets the attenuation value for the range.
For details on attenuation, see Section 7.4.1.2, "RF attenuation", on page 482.
Remote command:
[SENSe:]ESPectrum<sb>:RANGe<ri>:INPut:ATTenuation on page 1009
Preamp
Switches the preamplifier on or off.
For details on the preamplifier, see "Preamplifier" on page 490.
Remote command:
[SENSe:]ESPectrum<sb>:RANGe<ri>:INPut:GAIN:STATe on page 1010
Transducer Factor
Sets a transducer for the specified range. You can only choose a transducer that fulfills
the following conditions:
● The transducer overlaps or equals the span of the range.
● The x-axis is linear.
● The unit is dB.
For details on transducers, see Section 11.4.1, "Basics on transducer factors",
on page 756.
Remote command:
[SENSe:]ESPectrum<sb>:RANGe<ri>:TRANsducer on page 1020
If the function is set to "Max", you can define a relative and an absolute limit level. In
this case, the maximum of the two values is used as the limit level.
For more information, see "Relative limit line functions" on page 243.
Remote command:
[SENSe:]ESPectrum<sb>:RANGe<ri>:LIMit<li>:RELative:STARt
on page 1013
[SENSe:]ESPectrum<sb>:RANGe<ri>:LIMit<li>:RELative:STOP
on page 1015
[SENSe:]ESPectrum<sb>:RANGe<ri>:LIMit<li>:RELative:STARt:
FUNCtion on page 1014
[SENSe:]ESPectrum<sb>:RANGe<ri>:LIMit<li>:RELative:STOP:FUNCtion
on page 1016
[SENSe:]ESPectrum<sb>:RANGe<ri>:LIMit<li>:RELative:STARt:ABS
on page 1014
[SENSe:]ESPectrum<sb>:RANGe<ri>:LIMit<li>:RELative:STOP:ABS
on page 1016
"NONE" (reference ranges only:) the limit of the reference range is used
"SUM" Sum of the two limit lines (calculated for linear powers) is used
"MAX" Maximum of the two limit lines is used
Remote command:
[SENSe:]ESPectrum<sb>:RANGe<ri>:MLCalc on page 1018
Delete Range
Deletes the currently focused range, if possible. (The reference range cannot be
deleted. A minimum of three ranges is required.) The range numbers are updated
accordingly.
Remote command:
[SENSe:]ESPectrum<sb>:RANGe<ri>:DELete on page 1007
Symmetrical Setup
Any changes to the range settings in active "Symmetrical Setup" mode lead to sym-
metrical changes in the other ranges (where possible). In particular, this means:
● Inserting ranges: a symmetrical range is inserted on the other side of the reference
range
● Deleting ranges: the symmetrical range on the other side of the reference range is
also deleted
● Editing range settings: the settings in the symmetrical range are adapted accord-
ingly
Note: If "Fast SEM" mode is deactivated while "Symmetrical Setup" mode is on, "Sym
Setup" mode is automatically also deactivated.
If "Fast SEM" mode is activated while "Symmetrical Setup" mode is on, not all range
settings can be set automatically.
Remote command:
[SENSe:]ESPectrum<sb>:SSETup on page 1020
Access: "Overview" > "Select Measurement" > "Spectrum Emission Mask" > "Sub
Blocks"
In the Spectrum application application only, spectrum emissions can be measured for
multiple sub blocks of channels (see Section 6.6.4.5, "SEM with multiple sub blocks
("Multi-SEM")", on page 246). Sub blocks are a set of multiple ranges around a defined
center frequency (carrier).
By default, a single sub block is assumed. If more than one sub blocks are defined,
additional tabs are inserted for each sub block in the individual tabs of the "Spectrum
Emission Mask" configuration dialog box.
Note that either a standard or an MSR setting can be selected; if one is selected, the
other is disabled.
Remote command:
[SENSe:]ESPectrum<sb>:PRESet[:STANdard] on page 1002
Section 13.5.7.3, "Configuring a multi-sem measurement", on page 1003
Access: "Overview" > "Select Measurement" > "Spectrum Emission Mask" > "Refer-
ence Range"
The range around the center frequency is defined as the reference range for all other
ranges in the sweep list.
"Channel Power"
Measures the channel power within the reference range using the
integration bandwidth method. Additional settings can be configured
for this method.
(See also "IBW method" on page 154)
"Peak Power"
Determines the peak power within the reference range.
Remote command:
[SENSe:]ESPectrum<sb>:RTYPe on page 1022
Access: "Overview" > "Select Measurement" > "Spectrum Emission Mask" > "Power
Classes"
You can configure power classes which you can then assign to sweep list ranges. For
details, see "Power classes" on page 241.
PMin/ PMax
Defines the power limits for each power class. The first range always starts at -200
dBm (-INF) and the last range always stops at 200 dBm (+INF). These fields cannot be
modified. If more than one power class is defined, the value of "PMin" must be equal to
the value of "PMax" of the previous power class and vice versa.
Note that the power level can be equal to the lower limit(s), but must be lower than the
upper limit(s):
Pmin≦P<Pmax
Otherwise the ranges are corrected automatically.
Remote command:
CALCulate<n>:LIMit<li>:ESPectrum<sb>:PCLass<pc>:MINimum
on page 1027
CALCulate<n>:LIMit<li>:ESPectrum<sb>:PCLass<pc>:MAXimum
on page 1026
Sweep List
Switches to the "Sweep List" tab of the "Spectrum Emission Mask" dialog box and
focuses the "Limit Check" setting for the corresponding power class (1-4) in the refer-
ence range (see "Limit Check <n>" on page 254).
Access: "Overview" > "Select Measurement" > "Spectrum Emission Mask" > "MSR
Settings"
Multi-standard radio (MSR) measurements allow you to perform SEM tests on multiple
carriers using different digital standards.
For details, see Section 6.6.4.4, "Multi-standard radio (MSR) SEM measurements",
on page 245.
Band Category
Defines the band category for MSR measurements, i.e. the combination of available
carriers to measure.
"BC1" LTE FDD and W-CDMA
"BC2" LTE FDD, W-CDMA and GSM/EDGE
"BC3" LTE TDD and TD-SCDMA
Remote command:
[SENSe:]ESPectrum<sb>:MSR:BCATegory on page 1029
Remote command:
[SENSe:]ESPectrum<sb>:MSR:CLASs on page 1030
Bands
Defines the frequency range of the bands used by the base station.
This setting is only available for Band Category 1 or 3.
This setting is required to calculate the SEM limits according to standard 3GPP 37.141
V12.2.0.
Remote command:
[SENSe:]ESPectrum<sb>:MSR:BAND on page 1028
This setting is required to calculate the SEM limits according to standard 3GPP 37.141
V12.2.0.
Remote command:
[SENSe:]ESPectrum<sb>:MSR:GSM:CARRier on page 1030
Apply to SEM
Configures the SEM sweep list according to the specified MSR settings.
Remote command:
[SENSe:]ESPectrum<sb>:MSR:APPLy on page 1028
Access: "Overview" > "Select Measurement" > "Spectrum Emission Mask" > "Stan-
dard Files"
You can save the current measurement settings as a user-defined standard (XML file),
or load stored measurement settings. Furthermore, you can delete an existing settings
file.
For details, see Section 6.6.6.1, "How to manage SEM settings files", on page 271.
File Name
Contains the name of the data file without the path or extension.
By default, the name of a user file consists of a base name followed by an underscore.
Multiple files with the same base name are extended by three numbers, e.g.
limit_lines_005.
File names must be compatible with the Windows conventions for file names. In partic-
ular, they must not contain special characters such as ":", "*", "?".
For details on the filename and location, see Section 10.3.2.2, "Storage location and
filename", on page 684.
Load Standard
Loads the selected measurement settings file.
Remote command:
[SENSe:]ESPectrum<sb>:PRESet[:STANdard] on page 1002
File Explorer
Opens the Microsoft Windows File Explorer.
Remote command:
not supported
Save Standard
Saves the current measurement settings for a specific standard as a file with the
defined name.
Remote command:
[SENSe:]ESPectrum<sb>:PRESet:STORe on page 1002
Delete Standard
Deletes the selected standard. Standards predefined by Rohde & Schwarz can also be
deleted. A confirmation query is displayed to avoid unintentional deletion of the stan-
dard.
Note: Restoring predefined standard files. The standards predefined by Rohde &
Schwarz available at the time of delivery can be restored using the "Restore Standard
Files" function (see "Restore Standard Files" on page 266).
Access: "Overview" > "Select Measurement" > "Spectrum Emission Mask" > "List
Evaluation"
In the "List Evaluation" dialog box, you configure the contents and display of the SEM
results.
Show Peaks
If activated, all peaks that have been detected during an active SEM measurement are
marked with blue squares in the Spectrum diagram.
Remote command:
CALCulate<n>:ESPectrum:PEAKsearch:PSHow on page 1035
Margin
Although a margin functionality is not available for the limit check, you can define a
margin (or: threshold) for the peak values to be displayed in the result summary. Only
peaks that exceed the margin value are displayed (also in the diagram, if activated).
Remote command:
CALCulate<n>:ESPectrum:PEAKsearch:MARGin on page 1034
2. Split the frequency span of the measurement into ranges for signal parts with simi-
lar characteristics.
Starting from the center frequency, determine which sections of the signal to the
left and right can be swept and monitored using the same parameters. Criteria for
such a range definition may be, for example:
● The signal power level
● The required resolution bandwidth or sweep time
● Transducer factors
● Permitted deviation from the defined signal level, i.e. the required limit values
for monitoring
If the signal consists of a transmission channel and adjacent channels, the channel
ranges can usually be used for the range definition.
3. If the signal power level to be monitored varies and the limits vary, define power
classes. For each range of levels that can be monitored in the same way, define a
power class.
a) Select "Overview".
b) Select "SEM Setup".
c) Switch to the "Power Classes" tab.
d) To add a power class, select "Add".
e) Enter the start and stop power levels to define the class.
f) Select the power classes to be used for the current measurement:
● a specific class
● all classes, to have the required class selected automatically according to
the input level measured in the reference range
4. Select the "Sweep List" tab of the "Spectrum Emission Mask" dialog box.
5. Insert the required ranges using "Insert before Range" and "Insert after Range",
which refer to the currently selected range (the reference range by default).
If the signal trace is symmetric to the center frequency, activate the "Sym Setup"
option to make setup easier and quicker.
7. If the sweep list settings - other than the limit and transducer values - are identical
for several adjacent ranges, activate "Fast SEM" mode to speed up the measure-
ment. You only have to activate the mode for one range, the others are adapted
automatically.
8. If necessary, change the settings for the reference power to which all SEM results
refer in the "Reference Range" tab.
10. To save the current SEM measurement settings to a file to re-use them later, save
a settings file as described in "How to save a user-defined SEM settings file"
on page 271.
12. To save the Result Summary, export the results to a file as described in Sec-
tion 6.6.6.2, "How to save SEM result files", on page 272.
2. Select the band category that determines the digital standards used in the mea-
surement setup (see "Band Category" on page 262).
3. Define the bandwidth that contains all relevant carrier signals to be measured.
4. For measurements with GSM/EDGE, LTE FDD and W-CDMA carriers (BC2),
define whether a GSM/EDGE or an LTE FDD carrier, or both, are located at the
edge of the bandwidth.
6. Start a sweep.
The determined powers and limit deviations for each range are indicated in the
Result Summary. If activated, the peak power levels for each range are also indica-
ted in the Spectrum diagram.
7. To save the Result Summary, export the results to a file as described in Sec-
tion 6.6.6.2, "How to save SEM result files", on page 272.
3. Define the number of sub blocks (up to 8) that contain the relevant carriers.
4. For each sub block, define the center frequency, that is, the frequency of the TX
carrier or a frequency in the dedicated reference range.
● Select "MSR Settings" and define the MSR configuration as described in "To
perform an MSR SEM measurement" on page 270.
● Select "Edit" and configure the sweep list manually as defined in "To configure
a user-defined SEM measurement" on page 268. Be sure to select the correct
vertical tab for the corresponding sub block within each subtab of the "Spec-
trum Emission Mask" configuration dialog.
Define a function to be used for overlapping ranges in the "Multi-Limit Calc"
field of the sweep list.
6. Start a sweep.
The determined powers and limit deviations for each sub block, each gap, and
each range are indicated in the Result Summary. If activated, the peak power lev-
els for each range are also indicated in the Spectrum diagram.
7. To save the Result Summary, export the results to a file as described in Sec-
tion 6.6.6.2, "How to save SEM result files", on page 272.
SEM measurement settings can be saved to an XML file which can then be exported to
another application or loaded on the FSW again later. Some predefined XML files are
provided that contain ranges and parameters according to the selected standard. All
XML files are stored under
C:\Program Files (x86)\Rohde-Schwarz\FSW\<version>\sem_std.
For details on the file format of the SEM settings file, see Section 6.6.8.1, "Format
description of SEM XML files", on page 274.
SEM settings or standard files are managed in the "Standard" tab of the "Spectrum
Emission Mask" dialog box. To display this dialog box, select "Overview" and then
"SEM Setup".
2. Select "Load".
The settings from the selected file are restored to the FSW and you can repeat the
SEM measurement with the stored settings.
2. In the "Standard Files" tab of the "Spectrum Emission Mask" dialog box, define a
filename and storage location for the settings file.
3. Select "Save".
The settings are stored to a file with the extension .xml as specified.
2. Select "Delete".
The Result Summary from an SEM measurement can be saved to a file, which can be
exported to another application for further analysis, for example.
For details on the file format of the SEM export file, see Section 6.6.8.2, "ASCII file
export format (spectrum emission mask)", on page 280.
4. Select "Save".
5. In the file selection dialog box, select a storage location and filename for the result
file.
6. Select "Save".
The file with the specified name and the extension .dat is stored in the defined
storage location.
Test setup:
7. For "Sub Block A", define the settings for the 3GPP/FDD signal:
● Set the "Center Frequency" to 900 MHz
● Select "MSR Settings".
● Set the "Base Station RF Bandwidth" to 5 MHz.
● Select "Apply to SEM".
8. For "Sub Block B", define the settings for the EUTRA/LTE signal:
● Set the "Center Frequency" to 906.5 MHz
● Select "MSR Settings".
● Set the "Base Station RF Bandwidth" to 5 MHz.
● Select "Apply to SEM".
Figure 6-50: Multi-SEM measurement: results of the measurement for each sub block
This reference provides details on the format of the SEM settings and result files.
● Format description of SEM XML files....................................................................274
● ASCII file export format (spectrum emission mask).............................................. 280
The SEM XML files offer a quick way to change the measurement settings. A set of
predefined XML files for different standards is already provided. You can also create
and use your own XML files. Alternatively, edit the settings directly in the "Spectrum
Emission Mask" dialog box and save the XML file afterwards. This way, you do not
have to modify the XML file itself.
In addition to saving the current settings to a file, settings files can also be created
independently of the FSW, in an external application. When creating your own XML
files, be sure to comply with the following conventions because the FSW can only inter-
pret XML files of a known structure. For sample files, see the
C:\Program Files (x86)\Rohde-Schwarz\FSW\<version>\sem_std direc-
tory of the FSW.
To load a settings file, use the "Load" function in the "Standard Files" tab of the "Spec-
trum Emission Mask" dialog box (see "How to load an SEM settings file" on page 271).
Be sure to follow the structure exactly as shown below or else the FSW is not able to
interpret the XML file and error messages are shown on the screen. It is recommended
that you make a copy of an existing file and edit the copy of the file.
Example:
In the sample file PowerClass_39_43.xml under
C:\Program Files (x86)\Rohde-Schwarz\FSW\<version>\sem_std\
WCDMA\3GPP, these attributes are defined as follows:
● Standard="W-CDMA 3GPP"
● LinkDirection="DL"
● PowerClass="(39,43)dBm"
two limit nodes: one that defines the limit in absolute values and one in relative values.
Make sure units for the Start and Stop nodes are identical for each Limit node.
For details, refer to Section 6.6.5.1, "Sweep List", on page 250. The child nodes and
attributes of this element are shown in Table 6-15.
The following tables show the child nodes and attributes of each element and show if a
child node or attribute is mandatory for the FSW to interpret the file or not. The hierar-
chy of the XML cannot be seen in the tables. View one of the predefined files already
stored on the FSW in the "C:\Program Files
(x86)\Rohde-Schwarz\FSW\<version>\sem_std" directory, or check the struc-
ture as shown below.
Below, a basic example of the structure of the file is shown, containing all mandatory
attributes and child nodes. Note that the PowerClass element and the Range element
are themselves elements of the BaseFormat element. They must be inserted where
noted. They are separated here simply to provide a better overview. Also, no example
values are given here to allow a quick reference to the tables above. Italic font shows
the placeholders for the values.
● The BaseFormat element is structured as follows:
– <RS_SEM_ACP_FileFormat Version="1.0.0.0">
<Name>"Standard"</Name>
<Instrument>
<Type>"Instrument Type"</Type>
<Application>"Application"</Application>
</Instrument>
<LinkDirection Name="Name">
<ReferencePower>
<Method>"Method"</Method>
</ReferencePower>
<PowerClass Index="n">
<!-- For contents of the PowerClass node, see Table 6-14 -->
<!-- Define up to four PowerClass nodes -->
</PowerClass>
</LinkDirection>
</RS_SEM_ACP_File>
● The "PowerClass" element is structured as follows:
– <PowerClass Index="n">
<StartPower Unit="dBm" InclusiveFlag="true" Value="StartPowerValue"/>
<StopPower Unit="dBm" InclusiveFlag="false" Value="StopPowerValue"/>
<DefaultLimitFailMode>"Limit Fail Mode"</DefaultLimitFailMode>
<Range Index="n">
<!-- For contents of the Range node, see Table 6-15 -->
<!-- Define up to twenty Range nodes -->
</Range>
…
</PowerClass>
● The "Range" element is structured as follows:
– <Range Index="n">
<Name="Name">
<ChannelType>"Channel Type"</Channel Type>
<WeightingFilter>
<Type>"FilterType"</Type>
<RollOffFactor>"Factor"</RollOffFactor>
<Bandwith>"Bandwidth"</Bandwidth>
</WeightingFilter>
<FrequencyRange>
<Start>"RangeStart"</Start>
<Stop>"RangeStop"</Stop>
</FrequencyRange>
<Limit>
<Start Unit="Unit" Value="Value"/>
<Stop Unit="Unit" Value="Value"/>
</Limit>
<Limit>
<Start Unit="Unit" Value="Value"/>
<Stop Unit="Unit" Value="Value"/>
</Limit>
<RBW Bandwidth="Bandwidth" Type="FilterType"/>
<VBW Bandwidth="Bandwidth"/>
<Detector>"Detector"</Detector>
<Sweep Mode="SweepMode" Time="SweepTime"/>
<Amplitude>
<ReferenceLevel Unit="dBm" Value="Value"/>
<RFAttenuation Mode="Auto" Unit="dB" Value="Value"/>
<Preamplifier State="State"/>
</Amplitude>
<MeasPointsMin>1</MeasPointsMin>
<CalcRuleMulti>Sum</CalcRuleMulti>
</Range>
Table 6-13: Attributes and child nodes of the BaseFormat element
ShortName DL | UL No
Reference- Yes
Power
Reference- <string> No
Channel
StartPower Value <power in dBm> The start power must be equal Yes
to the stop power of the previ-
ous power class. The Start-
Power value of the first range
is -200
StopPower Value <power in dBm> The stop power must be equal Yes
to the start power of the next
power class. The StopPower
value of the last range is 200
Unit dBm
Table 6-15: Attributes and child nodes of the Range element (normal ranges)
Roll Off Factor 0…1 Excess bandwidth of the fil- Only if the filter
ter type is RRC
FrequencyRange Yes
Amplitude No
ReferenceLevel Value <power in dBm> "Ref Level" on page 253 Yes, if the Refer-
enceLevel child
node is used
RFAttenuation Mode Manual | Auto "RF Att Mode" on page 253 Yes, if the Refer-
enceLevel child
node is used
When trace data from an SEM measurement is exported, the data is stored in ASCII
format as described below. The first part of the file lists information about the signal
analyzer and the general setup.
File header
Type;FSW-26; Model
Freq Offset;0.000000;Hz
Span;25500000.000000;Hz
x-Axis;LIN;
Start;13237250000.000000;Hz
Stop;13262750000.000000;Hz
Ref Position;100.000000;%
y-Axis;LOG;
Level Range;100.000000;dB
Trace settings
Trace Mode;CLR/WRITE;
Detector;RMS;
Sweep Count;0;
Trace 1:;
x-Unit;Hz;
y-Unit;dBm;
Alpha;0.22;
The measured signal, including any spurious emissions, and optionally the detected
peaks are displayed in the Spurious Emissions measurement diagram. If defined, the
limit lines and the limit check results are also indicated. In addition to the graphical
results, a result table can be displayed to evaluate the measured powers and limit
check results (see also Section 6.7.3.2, "Limit lines in spurious measurements",
on page 284). The details of the evaluation list can be configured.
The following information is provided in the evaluation list for each range:
Column Description
Range Low Frequency range start for the range the peak value belongs to
Range Up Frequency range end for the range the peak value belongs to
ΔLimit Deviation of the absolute power level from the defined limit for the peak
value
By default, one peak per range is displayed. However, you can change the settings to:
● Display all peaks
● Display a certain number of peaks per range
● Display only peaks that exceed a threshold ("Margin")
● Display detected peaks as blue squares in the diagram, as well as in the peak list
Some background knowledge on basic terms and principles used in Spurious Emis-
sions measurements is provided here for a better understanding of the required config-
uration settings.
● Ranges and range settings................................................................................... 283
● Limit lines in spurious measurements................................................................... 284
Limit lines allow you to check the measured data against specified limit values. Gener-
ally, it is possible to define limit lines for any measurement in the Spectrum application
using [Lines]. For Spurious measurements, however, a special limit line is available via
the "Sweep List", and it is strongly recommended that you use only this limit line defini-
tion.
In the "Sweep List", you can define a limit line that varies its level according to the
specified frequency ranges. A distinguished limit line is automatically defined according
to the current "Sweep List" settings every time the settings change. This limit line is
labeled "_SPURIOUS_LINE_ABS_<xxx>", where <xxx> is an index to distinguish limit
lines between different channels.
If a limit check is activated in the "Sweep List", the "_SPURIOUS_LINE_ABS_<xxx>"
limit line is indicated by a red line in the display. The result of the limit check is indica-
ted at the top of the diagram. Note that only "Pass" or "Fail" is indicated; a margin func-
tion as for general limit lines is not available. Also, only absolute limits can be checked,
not relative ones.
As for general limit lines, the results of each limit line check are displayed (here:
"_SPURIOUS_LINE_ABS_<xxx>"), as well as the combined result for all defined limit
lines ("Limit Check").
The limit check is considered to be "' failed!" if any signal level outside the absolute lim-
its is measured.
If the limit check is activated, the limit line values for each range are displayed in the
evaluation list. Furthermore, the largest deviations of the absolute power from the limit
line for each range are displayed. Values that exceed the limit are indicated in red and
by an asterisk (*).
Although a margin functionality is not available for the limit check, a margin (threshold)
for the peak values to be displayed in the evaluation list can be defined. Furthermore,
you can define how many peaks per range are listed. For details, see Section 6.7.4.3,
"List evaluation", on page 290.
Access: "Overview" > "Select Measurement" > "Spurious Emissions" > "Sweep List"
For Spurious Emissions measurements, the input signal is split into several frequency
ranges which are swept individually and for which different limitations apply.
If you edit the sweep list, always follow the rules and consider the limitations described
in Section 6.7.3.1, "Ranges and range settings", on page 283.
Remote command:
[SENSe:]LIST:RANGe<ri>[:FREQuency]:STARt on page 1042
[SENSe:]LIST:RANGe<ri>[:FREQuency]:STOP on page 1042
Filter Type
Sets the filter type for this range.
For details on filter types, see Section 7.5.1.6, "Which data may pass: filter types",
on page 498.
Remote command:
[SENSe:]LIST:RANGe<ri>:FILTer:TYPE on page 1043
RBW
Sets the RBW value for this range.
For details on the RBW, see Section 7.5.1.1, "Separating signals by selecting an
appropriate resolution bandwidth", on page 494.
Remote command:
[SENSe:]LIST:RANGe<ri>:BANDwidth:RESolution on page 1040
VBW
Sets the VBW value for this range.
For details on the VBW, see Section 7.5.1.2, "Smoothing the trace using the video
bandwidth", on page 495.
Remote command:
[SENSe:]LIST:RANGe<ri>:BANDwidth:VIDeo on page 1040
Sweep Time
Sets the sweep time value for the range.
For details on the sweep time, see Section 7.5.1.7, "How long the data is measured:
Sweep Time", on page 499
Remote command:
[SENSe:]LIST:RANGe<ri>:SWEep:TIME on page 1048
Detector
Sets the detector for the range.
For details, refer to "Mapping samples to sweep points with the trace detector"
on page 611.
Remote command:
[SENSe:]LIST:RANGe<ri>:DETector on page 1041
Reference Level
Sets the reference level for the range.
For details on the reference level, see Section 7.4.1.1, "Reference level", on page 481.
Remote command:
[SENSe:]LIST:RANGe<ri>:RLEVel on page 1047
RF Attenuation Mode
Activates or deactivates the auto mode for RF attenuation.
For details on attenuation, see Section 7.4.1.2, "RF attenuation", on page 482.
Note: If an external frontend is active (see External frontend settings), you can config-
ure attenuation settings for the external frontend and the analyzer separately. This set-
ting defines the attenuation for the external frontend.
When using an external frontend, only mechanical attenuation is available.
For more information, see "External frontend attenuation vs. analyzer attenuation"
on page 448.
For more information, see the FSW User Manual.
Remote command:
[SENSe:]LIST:RANGe<ri>:INPut:ATTenuation:AUTO on page 1044
RF Attenuation
Sets the attenuation value for that range.
For details on attenuation, see Section 7.4.1.2, "RF attenuation", on page 482.
Remote command:
[SENSe:]LIST:RANGe<ri>:INPut:ATTenuation on page 1044
Remote command:
[SENSe:]LIST:RANGe<ri>:INPut:SANalyzer:ATTenuation on page 1045
[SENSe:]LIST:RANGe<ri>:INPut:SANalyzer:ATTenuation:AUTO
on page 1045
Preamp
Switches the preamplifier on or off.
For details on the preamplifier, see "Preamplifier" on page 490.
Remote command:
[SENSe:]LIST:RANGe<ri>:INPut:GAIN:STATe on page 1044
Sweep Points
Sets the number of sweep points for the specified range.
For details on sweep points, see Section 7.5.1.8, "How much data is measured: sweep
points and sweep count", on page 499.
Remote command:
[SENSe:]LIST:RANGe<ri>:POINts[:VALue] on page 1047
Transducer
Sets a transducer for the specified range. You can only choose a transducer that fulfills
the following conditions:
● The transducer overlaps or equals the span of the range.
● The x-axis is linear.
● The unit is dB.
For details on transducers, see Section 11.4.1, "Basics on transducer factors",
on page 756.
Remote command:
[SENSe:]LIST:RANGe<ri>:TRANsducer on page 1048
Limit Check
Activates or deactivates the limit check for all ranges.
For details on limit checks, see Section 6.7.3.2, "Limit lines in spurious measure-
ments", on page 284.
"ABSOLUTE" Signal is checked against absolute limit values
"NONE" No limit check is performed.
Remote command:
[SENSe:]LIST:RANGe<ri>:LIMit:STATe on page 1046
CALCulate<n>:LIMit<li>:FAIL? on page 1348
Delete Range
Deletes the currently focused range. The range numbers are updated accordingly.
Access: "Overview" > "Select Measurement" > "Spurious Emissions" > "Adjust X-Axis"
The frequency axis of the measurement diagram can be adjusted automatically so that
the span of all sweep list ranges corresponds to the displayed span. Thus, the x-axis
range is set from the start frequency of the first sweep range to the stop frequency of
the last sweep range.
Remote command:
[SENSe:]LIST:XADJust on page 1051
Access: "Overview" > "Select Measurement" > "Spurious Emissions" > "List Evalua-
tion"
Configure the contents and display of the result list.
Show Peaks
If activated, all peaks that have been detected during an active list evaluation are
marked with blue squares in the diagram.
Remote command:
CALCulate<n>:PEAKsearch:PSHow on page 1050
Margin
A margin functionality is not available for the limit check. However, you can define a
margin (=threshold) for the peak values to be displayed in the evaluation list. Only
peaks that exceed the margin value are displayed (also in the diagram, if activated).
Remote command:
CALCulate<n>:PEAKsearch:MARGin on page 1050
Details
Configures how detailed the list in the Result Summary is.
On Includes all detected peaks (up to a maximum defined by "Peaks per Range").
Remote command:
CALCulate<n>:ESPectrum:PEAKsearch:DETails on page 1049
For remote operation, see Section 13.5.8.7, "Programming example: spurious emis-
sions measurement", on page 1051.
2. Define the span of the signal to be monitored in the general span settings.
4. Split the frequency span of the measurement into ranges for signal parts with simi-
lar characteristics.
Define the required ranges in the "Sweep List" using "Insert before Range" and
"Insert after Range", which refer to the currently selected range.
8. Start a sweep.
The determined powers and limit deviations for each range are indicated in the
evaluation list. If activated, the peak power levels for each range are also indicated
in the diagram.
9. To save the evaluation list, export the results to a file as described in "How to Save
the Spurious Emissions Evaluation List" on page 293.
4. Select "Save".
5. In the file selection dialog box, select a storage location and file name for the result
file.
6. Select "Save".
The file with the specified name and the extension .dat is stored in the defined
storage location.
The file has a header containing important parameters for scaling, several data sec-
tions containing the sweep settings per range, and a data section containing the peak
list.
The header data is made up of three columns, separated by ';', with the syntax:
Parameter name; numeric value; basic unit
File header
Type;FSW-26 Model
Freq Offset;0.000000;Hz
Span;26499982000.000000;Hz
x-Axis;LIN;
Start;9000.000000;Hz
Stop;8000000000.000000;Hz
Ref Position;100.000000;%
y-Axis;LOG;
Level Range;100.000000;dB
Trace settings
Trace Mode;CLR/WRITE;
Sweep Count;1;
TRACE 1:
Trace Mode;CLR/WRITE;
x-Unit;Hz;
y-Unit;dBm;
The probability of amplitude values can be measured with the Amplitude Probability
Distribution function (APD). During a selectable measurement time all occurring ampli-
tude values are assigned to an amplitude range. The number of amplitude values in
the individual ranges is counted and the result is displayed as a histogram.
Alternatively, the Complementary Cumulative Distribution Function (CCDF) can be dis-
played. It shows the probability that the mean signal power amplitude will be exceeded
in percent.
Only one of the signal statistic functions can be switched on at a time. When a statistic
function is switched on, the FSW is set into zero span mode automatically. The FSW
measures the statistics of the signal applied to the RF input with the defined analysis
bandwidth. To avoid affecting the peak amplitudes the video bandwidth is automatically
set to 10 times the analysis bandwidth. The sample detector is used for detecting the
video voltage.
Statistic measurements on pulsed signals can be performed using a gated trigger. For
details see Section 6.8.4, "APD and CCDF basics - gated triggering", on page 298.
Digital modulated signals are similar to white noise within the transmit channel, but are
different in their amplitude distribution. In order to transmit the modulated signal without
distortion, all amplitudes of the signal have to be transmitted linearly from the output
power amplifier. Most critical are the peak amplitude values. Degradation in transmit
quality caused by a transmitter two port network is dependent on the amplitude of the
peak values as well as on their probability.
If modulation types are used that do not have a constant envelope in zero span, the
transmitter has to handle peak amplitudes that are greater than the average power.
This includes all modulation types that involve amplitude modulation, QPSK for exam-
ple. CDMA transmission modes in particular may have power peaks that are large
compared to the average power.
For signals of this kind, the transmitter must provide large reserves for the peak power
to prevent signal compression and thus an increase of the bit error rate at the receiver.
The peak power or the crest factor of a signal is therefore an important transmitter
design criterion. The crest factor is defined as the peak power to mean power ratio or,
logarithmically, as the peak level minus the average level of the signal. To reduce
power consumption and cut costs, transmitters are not designed for the largest power
that could ever occur, but for a power that has a specified probability of being excee-
ded (e.g. 0.01 %).
The statistical functions provide information on such signal criteria.
The size of each amplitude range (bin) determines the resolution of the histogram and
is indicated in the channel bar, for example / 0.10 dB. In this case, a single bar in the
histogram represents an amplitude range of 0.10 dB.
In addition to the histogram, a result table is displayed containing the following informa-
tion:
● Number of samples used for calculation
● For each displayed trace:
– Mean amplitude
– Peak amplitude
– Crest factor
The crest factor is defined as the peak power to mean power ratio or, logarith-
mically, as the peak level minus the average level of the signal.
A red line indicates the ideal Gaussian (normal) distribution for the measured ampli-
tude range.
0,1 % 0,1 % probability that the level exceeds mean power + [x] dB
0,01 % 0,01 % probability that the level exceeds mean power + [x] dB
Percent marker
In addition to the results for specific percentages in the table, a percent marker can be
activated for a freely selectable percentage. This marker indicates how many level val-
ues are over <x> % above the mean power.
Percent marker
As all markers, the percent marker can be moved simply by selecting it with a finger or
mouse cursor and dragging it to the desired position.
Diagram Scaling
The scaling for both the x-axis and y-axis of the statistics diagram can be configured.
In particular, you can restrict the range of amplitudes to be evaluated and the probabili-
ties to be displayed.
Remote commands:
CALCulate<n>:STATistics:CCDF:X<t>? on page 1062
CALCulate<n>:STATistics:RESult<res>? on page 1062
Access: "Overview" > "Select Measurement" > "APD"/"CCDF" > "APD Config"/ "CCDF
Config"
The remote commands required to perform these tasks are described in Sec-
tion 13.5.9, "Analyzing statistics (APD, CCDF)", on page 1054.
Both dialog boxes are identical except for the "Percent Marker" setting, which is only
available for CCDF measurements.
Percent Marker (CCDF only).......................................................................................300
Analysis Bandwidth..................................................................................................... 300
Number of Samples.................................................................................................... 301
Gated Trigger.............................................................................................................. 301
Normal Distribution......................................................................................................301
Edit Gate Ranges........................................................................................................301
Adjust Settings............................................................................................................ 301
Analysis Bandwidth
Defines the analysis bandwidth.
For correct measurement of the signal statistics, the analysis bandwidth has to be
wider than the signal bandwidth in order to measure the peaks of the signal amplitude
correctly. To avoid influencing the peak amplitudes, the video bandwidth is automati-
cally set to 10 MHz. The sample detector is used for detecting the video voltage.
Number of Samples
Defines the number of power measurements that are taken into account for the statis-
tics.
For statistics measurements with the FSW, the number of samples to be measured is
defined instead of the sweep time. Since only statistically independent samples con-
tribute to statistics, the sweep or measurement time is calculated automatically and
displayed in the channel bar ("Meas Time"). The samples are statistically independent
if the time difference is at least 1/RBW. The measurement time is, therefore, expressed
as follows:
Meas Time = NSamples/RBW
The maximum number of samples is limited by the hardware capability. For gated trig-
gered APD or CCDF measurements, the maximum number is limited further, if neces-
sary, to accommodate for very small ranges within a relatively long period. In this case,
the smallest gate/period ratio is considered, and the number is adapted to capture full
periods of data. If the defined number of samples exceeds the limit, it is automatically
reduced to the maximum value.
Remote command:
CALCulate<n>:STATistics:NSAMples on page 1056
Gated Trigger
Activates and deactivates gating for statistics functions for the ACP and the CCDF
measurements. The gate ranges are defined using the Edit Gate Ranges function.
Remote command:
[SENSe:]SWEep:EGATe on page 1228
Normal Distribution
Enables or disables the red trace in the CCDF display indicating the normal distribu-
tion.
Remote command:
DISPlay[:WINDow<n>]:STATistics:CCDF:GAUSs on page 1056
Adjust Settings
Adjusts the level settings according to the measured difference between peak and min-
imum power for APD measurement or peak and mean power for CCDF measurement
in order to obtain maximum power resolution. Adjusts the reference level to the current
input signal.
Note this function is not available when using an external frontend.
Remote command:
CALCulate<n>:STATistics:SCALe:AUTO ONCE on page 1059
Access: "Overview" > "Select Measurement" > "APD"/"CCDF" > "APD Config"/ "CCDF
Config" > "Edit Gate Ranges"
You can configure gate ranges for gated triggering in statistical measurements.
For background information on defining gate ranges see Section 6.8.4, "APD and
CCDF basics - gated triggering", on page 298.
The remote commands required to perform these tasks are described in Sec-
tion 13.5.9.3, "Using gate ranges for statistical measurements", on page 1056.
Up to three ranges can be defined for each of the six available traces.
Comment.....................................................................................................................302
Period..........................................................................................................................302
Range <x> Use........................................................................................................... 303
Range <x> Start/Stop..................................................................................................303
Comment
An optional comment can be defined for the gate range settings of each trace.
Remote command:
[SENSe:]SWEep:EGATe:TRACe<t>:COMMent on page 1056
Period
Length of the period to be traced. The period is the same for all traces. If you change
the period for one trace, it is automatically changed for all traces.
Make sure the defined period is not longer than the total measurement time of the cur-
rent measurement. Keep in mind that the measurement time depends on the band-
width and the number of samples (see "Number of Samples" on page 301). The cur-
rent measurement time is indicated as "Meas Time" in the channel bar.
Remote command:
[SENSe:]SWEep:EGATe:TRACe<t>:PERiod on page 1057
In statistical diagrams, the x-axis displays the signal level values (= y-axis in standard
display), while the y-axis displays the probability of the values.
X-Axis..........................................................................................................................304
└ Ref Level.......................................................................................................304
└ Range........................................................................................................... 304
└ Shifting the Display (Offset).......................................................................... 305
Y-Axis.......................................................................................................................... 305
└ Y-Unit............................................................................................................ 305
└ Y-Max/ Y-Min.................................................................................................305
Default Settings...........................................................................................................305
Adjust Settings............................................................................................................ 306
X-Axis
Defines the scaling settings for signal level values.
Range ← X-Axis
Defines the level range in dB to be evaluated by the statistics measurement.
Remote command:
CALCulate<n>:STATistics:SCALe:X:RANGe on page 1060
Y-Axis
Defines the scaling settings for the probability distribution.
Y-Unit ← Y-Axis
Defines the scaling type of the y-axis as either percentage or absolute. The default
value is absolute scaling.
Remote command:
CALCulate<n>:STATistics:SCALe:Y:UNIT on page 1061
Default Settings
Resets the x- and y-axis scalings to their preset values.
Remote command:
CALCulate<n>:STATistics:PRESet on page 1059
Adjust Settings
Adjusts the level settings according to the measured difference between peak and min-
imum power for APD measurement or peak and mean power for CCDF measurement
in order to obtain maximum power resolution. Adjusts the reference level to the current
input signal.
Note this function is not available when using an external frontend.
Remote command:
CALCulate<n>:STATistics:SCALe:AUTO ONCE on page 1059
For remote operation, see Section 13.5.9.7, "Programming example: measuring statis-
tics", on page 1063.
2. Start a sweep.
As soon as the defined number of samples have been measured, the statistical
evaluation is displayed.
3. Define the time period for which the input signal is to be analyzed, for example the
duration of 3 signal pulses.
4. For each active trace, define up to three ranges within the time period to be mea-
sured. In the example covering 3 pulses, you could define one range for each
pulse.
a) Assuming the external trigger determines T=0 as the start of the first pulse,
define the start time of range 1 at 0 s.
b) Define the stop time of range 1 at the duration of the first pulse.
c) Activate range 1 by setting "Range 1 Use" to On.
d) Define the start time of range 2 as (duration of pulse 1 + duration of interval)
e) Define the stop time of range 2 as (start time of range 2 + duration of pulse 2)
f) Activate range 2 by setting "Range 2 Use" to On.
5. Start a sweep.
As soon as the defined number of samples have been measured, the statistical
evaluation is displayed. Only the signal levels within the pulse periods are consid-
ered.
6.8.7 Examples
A statistics evaluation has to be done over the useful part of the signal between t3 and
t4. The period of the GSM signal is 4.61536 ms.
6.8.7.2 Measurement example – measuring the APD and CCDF of white noise generated
by the FSW
3. Select the "APD" measurement function from the "Select Measurement" dialog
box.
The FSW sets the frequency span to 0 Hz and measures the amplitude probability
distribution (APD). The number of uncorrelated level measurements used for the
measurement is 100000. The mean power and the peak power are displayed in
dBm. The crest factor (peak power – mean power) is output as well.
4. Now select the "CCDF" measurement function from the "Select Measurement" dia-
log box.
The CCDF trace indicates the probability that a level will exceed the mean power.
The level above the mean power is plotted along the x-axis of the graph. The origin
of the axis corresponds to the mean power level. The probability that a level will be
exceeded is plotted along the y-axis.
If the results do not meet your expectations, try the following methods to optimize the
measurement:
● Make sure the defined bandwidth is wide enough for the signal bandwidth of the
device under test to be fully analyzed (see "Analysis Bandwidth" on page 300).
● If the complete signal is be measured, increase the number of samples so that the
resulting measurement time is longer than one period of a bursted signal.
● If only parts of the signal are to be examined, define a trigger source and a gate.
Using the Time Domain Power measurement function, the FSW determines the power
of the signal in zero span by summing up the power at the individual measurement
points and dividing the result by the number of measurement points. Thus it is possible
to measure the power of TDMA signals during transmission, for example, or during the
muting phase. Both the mean power and the RMS power can be measured.
For this measurement, the sample detector is recommended. The sample detector is
activated automatically if the detector is in auto mode.
Mode Description
Peak Peak value from the points of the displayed trace or a segment
thereof.
RMS RMS value from the points of the displayed trace or a segment
thereof.
Mean Mean value from the points of the displayed trace or a segment
thereof. The linear mean value of the equivalent voltages is calcula-
ted.
For example to measure the mean power during a GSM burst
Std Dev The standard deviation of the measurement points from the mean
value.
The result is displayed in the marker results, indicated by "Power" and the selected
power mode, e.g. "RMS". The measured values are updated after each sweep or aver-
aged over a user-defined number of sweeps (trace averaging).
The results can also be queried using the remote commands described in Sec-
tion 13.5.10, "Measuring the time domain power", on page 1064.
6.9.3 Time domain power basics - range definition using limit lines
The range of the measured signal to be evaluated for the power measurement can be
restricted using limit lines. The left and right limit lines (S1, S2) define the evaluation
range and are indicated by vertical red lines in the diagram. If activated, the power
results are only calculated from the levels within the limit lines.
For example, if both the on and off phase of a burst signal are displayed, the measure-
ment range can be limited to the transmission or to the muting phase. The ratio
between signal and noise power of a TDMA signal for instance can be measured by
using a measurement as a reference value and then varying the measurement range.
In order to get stable measurement results for a limited evaluation range, usually a trig-
ger is required.
Access: "Overview" > "Select Measurement" > "Time Domain Power" > "Time Dom
Power Config"
The remote commands required to perform these tasks are described in Sec-
tion 13.5.10, "Measuring the time domain power", on page 1064.
Results........................................................................................................................ 313
Limit State................................................................................................................... 313
Left Limit / Right Limit..................................................................................................313
Results
Activates the power results to be evaluated from the displayed trace or a limited area
of the trace.
"Peak" Peak power over several measurements (uses trace averaging, Max
Hold)
"RMS" RMS value from the points of the displayed trace or a segment
thereof.
"Mean" Mean value from the points of the displayed trace or a segment
thereof. The linear mean value of the equivalent voltages is calcula-
ted.
"Std Dev" The standard deviation of the measurement points from the mean
value.
The measurement of the mean power is automatically switched on at
the same time.
Remote command:
CALCulate<n>:MARKer<m>:FUNCtion:SUMMary:PPEak[:STATe] on page 1067
CALCulate<n>:MARKer<m>:FUNCtion:SUMMary:PPEak:RESult? on page 1070
CALCulate<n>:MARKer<m>:FUNCtion:SUMMary:RMS[:STATe] on page 1067
CALCulate<n>:MARKer<m>:FUNCtion:SUMMary:RMS:RESult? on page 1071
CALCulate<n>:MARKer<m>:FUNCtion:SUMMary:MEAN[:STATe] on page 1066
CALCulate<n>:MARKer<m>:FUNCtion:SUMMary:MEAN:RESult? on page 1069
Limit State
Switches the limitation of the evaluation range on or off. Default setting is off.
If deactivated, the entire sweep time is evaluated. If switched on, the evaluation range
is defined by the left and right limit. If only one limit is set, it corresponds to the left limit
and the right limit is defined by the stop frequency. If the second limit is also set, it
defines the right limit.
Remote command:
CALCulate<n>:MARKer<m>:X:SLIMits[:STATe] on page 1282
The step-by-step procedure to measure powers in the time domain is described here in
detail.
2. From the "Select Measurement" dialog box, select the "Time Domain Power" mea-
surement function.
5. Start a sweep.
The measured powers are displayed in the marker results.
This measurement example demonstrates the time domain power calculation for a
GSM burst.
For remote operation, see Section 13.5.10.4, "Programming example: time domain
power", on page 1073.
Test setup:
Modulation: GSM/EDGE
Procedure:
1. Preset the FSW.
7. Select the "Time Domain Power" measurement function from the "Select Measure-
ment" dialog box.
8. In the Time Domain Power configuration dialog box, set all four results to "On".
10. Define the left limit at 326 μs and the right limit at 538 μs.
This range corresponds to the useful part of the GSM burst.
The mean power of the useful part of the GSM burst is calculated to be -13 dBm.
With this measurement it is possible to measure the harmonics easily, for example
from a VCO. In addition, the total harmonic distortion (THD) is calculated.
For measurements in the frequency domain, the Harmonic Distortion measurement
starts with an automatic search for the first harmonic (= peak) within the set frequency
range. The center frequency is set to this frequency and the reference level is adjusted
accordingly.
For measurements in zero span, the center frequency remains unchanged.
The Harmonic Distortion measurement then performs zero span sweeps at the center
frequency and at each harmonic, i.e. at frequencies that are a multiple of the center
frequency.
As a result, the zero span sweeps on all harmonics are shown, as well as the RMS
values and the total harmonic distortion (THD).
An application note discussing harmonics measurement is available from the Rohde &
Schwarz website:
1EF78: Measurement of Harmonics using Spectrum Analyzers
Measuring the harmonics of a signal is a frequent problem which can be solved best
using a signal analyzer. In general, every signal contains harmonics. Harmonics are
generated by nonlinear characteristics, which add frequencies to a pure sinewave.
They can often be reduced by low pass filters. Since the signal analyzer itself has a
nonlinear characteristic, for example in its first mixer, measures must be taken to
ensure that harmonics produced in the signal analyzer do not cause spurious results. If
necessary, the fundamental wave must be attenuated selectively with respect to the
other harmonics with a high pass filter. Harmonics are particularly critical regarding
high-power transmitters such as transceivers because large harmonics can interfere
with other radio services.
Harmonic distortion can be determined as the level of the individual components, or as
the root mean square of all components together, the total harmonic distortion (THD).
The THD is set in relation to the power of the fundamental frequency (= center fre-
quency).
As shown in Figure 6-54, the level of the 2nd harmonic drops by 20 dB if the level of the
fundamental wave is reduced by 10 dB.
Figure 6-54: Extrapolation of the 1st and 2nd harmonics to the 2nd harmonic intercept at 40 dBm
The following formula for the obtainable harmonic distortion d2 in dB is derived from the
straight-line equations and the given intercept point:
d2 = S.H.I – PI (1)
where:
d2 = harmonic distortion
PI = mixer level/dBm
The mixer level is the RF level applied to the RF input minus the set RF attenuation.
The formula for the internally generated level P1 at the 2nd harmonic in dBm is:
P1 = 2 * PI – S.H.I. (2)
The lower measurement limit for the harmonic is the noise floor of the signal analyzer.
The harmonic of the measured DUT should – if sufficiently averaged by means of a
video filter – be at least 4 dB above the noise floor so that the measurement error due
to the input noise is less than 1 dB.
● Select an RF attenuation which is high enough to measure the harmonic ratio only.
The maximum harmonic distortion is obtained if the level of the harmonic equals the
intrinsic noise level of the receiver. The level applied to the mixer, according to (2), is:
At a resolution bandwidth of 10 Hz (noise level -143 dBm, S.H.I. = 40 dBm), the opti-
mum mixer level is – 51.5 dBm. According to (1) a maximum measurable harmonic dis-
tortion of 91.5 dB minus a minimum S/N ratio of 4 dB is obtained.
As a result of the harmonics distortion measurement, the zero span sweeps of all
detected harmonics are shown in the diagram, separated by red display lines. This pro-
vides a very good overview of the measurement.
Remote commands
The results can also be queried using remote commands.
The first harmonic frequency can be read out via the general center frequency com-
mand [SENSe:]FREQuency:CENTer on page 1195.
THD: CALCulate<n>:MARKer<m>:FUNCtion:HARMonics:DISTortion?
on page 1076
List of harmonics: CALCulate<n>:MARKer<m>:FUNCtion:HARMonics:LIST
on page 1077
Access: "Overview" > "Select Measurement" > "Harmonic Distortion" > "Harmonic Dis-
tortion Config"
The remote commands required to perform these tasks are described in Sec-
tion 13.5.11, "Measuring the harmonic distortion", on page 1074.
Number of Harmonics................................................................................................. 320
Harmonic Sweep Time................................................................................................ 320
Harmonic RBW Auto................................................................................................... 320
Adjust Settings............................................................................................................ 320
Number of Harmonics
Defines the number of harmonics to be measured. The range is from 1 to 26. Default is
10.
Remote command:
CALCulate<n>:MARKer<m>:FUNCtion:HARMonics:NHARmonics on page 1075
Adjust Settings
If harmonic measurement was performed in the frequency domain, a new peak search
is started in the frequency range that was set before starting the harmonic measure-
ment. The center frequency is set to this frequency and the reference level is adjusted
accordingly.
If harmonic measurement was performed in the time domain, this function adjusts the
reference level only.
Remote command:
CALCulate<n>:MARKer<m>:FUNCtion:HARMonics:PRESet on page 1076
1. Select the "Harmonic Distortion" measurement function from the "Select Measure-
ment" dialog box.
3. Perform a sweep.
The trace for the determined harmonics are displayed in the diagram, separated by
red display lines. The measured power for each harmonic in relation to the funda-
mental is indicated in the result table.
4. If the signal changes significantly during or after the harmonics measurement, use
the "Adjust Settings" function to adjust the settings automatically and restart the
measurement.
If several signals are applied to a two-port transmission device with nonlinear charac-
teristic, intermodulation products appear at its output at the sums and differences of
the signals. The nonlinear characteristic produces harmonics of the useful signals,
which intermodulate at the characteristic. The intermodulation products of lower order
have a special effect, since their level is largest and they are near the useful signals.
The intermodulation product of third order causes the highest interference. It is the
intermodulation product generated from one of the useful signals and the 2nd harmonic
of the second useful signal for two-tone modulation.
To measure the third order intercept point (TOI), a two-tone signal with equal carrier
levels is expected at the FSW input. Marker 1 and marker 2 (both normal markers) are
set to the maximum of the two signals. Marker 3 and marker 4 are placed on the inter-
modulation products.
The FSW calculates the third order intercept point from the level difference between
the first 2 markers and the markers 3 and 4, and displays it in the marker table.
If several signals are applied to a two-port transmission device with nonlinear charac-
teristic, intermodulation products appear at its output at the sums and differences of
the signals. The nonlinear characteristic produces harmonics of the useful signals,
which intermodulate at the characteristic.
The frequencies of the intermodulation products are above and below the useful sig-
nals. Figure 6-55 shows intermodulation products PS1 and PS2, generated by the two
useful signals PU1 and PU2.
The intermodulation product at fi2 is generated by mixing the 2nd harmonic of useful
signal PU2 and useful signal PU1.
The intermodulation product at fi1 is generated by mixing the 2nd harmonic of useful
signal PU1 and useful signal PU2.
The useful signals at the two-port output increase proportionally with the input level as
long as the two-port is in the linear range. A level change of 1 dB at the input causes a
level change of 1 dB at the output. Beyond a certain input level, the two-port goes into
compression and the output level stops increasing. The intermodulation products of the
third order increase three times as quickly as the useful signals. The intercept point is
the fictitious level where the two lines intersect. It cannot be measured directly, since
the useful level is limited by the maximum two-port output power.
Calculation method
However, the intercept point can be calculated from the known line slopes and the
measured spacing aD3 between intermodulation signals and useful signals at a given
level Pu according to the following formula:
aD 3
IP3 PN
2
Example:
Assume that the measured spacing between intermodulation and useful signal is 60 dB
at the input level PU= -20 dBm. Then the third order intercept point (TOI) is calculated
according to the following formula:
60
IP3 (20dBm) 10dBm
2
For typical values for your instrument, see the specifications document.
Figure 6-57: Intermodulation-free range as a function of level at the input mixer and the set resolution
bandwidth
The optimum mixer level, i.e. the level at which the intermodulation distance is at its
maximum, depends on the bandwidth. At a resolution bandwidth of 10 Hz, it is approx.
‑35 dBm. At 1 kHz, it increases to approx. ‑30 dBm.
Phase noise has a considerable influence on the intermodulation-free range at carrier
offsets between 10 kHz and 100 kHz ( see Figure 6-58). At greater bandwidths, the
influence of the phase noise is greater than it would be with small bandwidths. The
optimum mixer level at the bandwidths under consideration becomes almost independ-
ent of bandwidth and is approx. -40 dBm.
Figure 6-58: Intermodulation-free dynamic range as a function of level at the input mixer and of the
selected resolution bandwidth
When you measure the intermodulation products of a DUT with a very high dynamic
range, the used resolution bandwidth is usually very small. In this case, it is best to
measure the levels of the useful signals and those of the intermodulation products sep-
arately, using a small span. The measurement time is reduced, in particular if the offset
of the useful signals is large. To find signals reliably when the frequency span is small,
it is best to synchronize the signal sources and the FSW.
As a result of the TOI measurement, the following values are displayed in the marker
area of the diagram:
Label Description
TOI Third-order intercept point for averaged levels (see also Section 6.11.3, "TOI results",
on page 326 and Figure 6-55):
PU-AVG+ (PU-AVG-PS-AVG)/2
Remote command
The TOI can also be queried using the remote commands:
CALCulate<n>:MARKer<m>:FUNCtion:TOI:RESult? on page 1079.
CALCulate<n>:MARKer<m>:FUNCtion:TOI:RESult:MAXimum? on page 1079
CALCulate<n>:MARKer<m>:FUNCtion:TOI:RESult:MINimum? on page 1080
Access: "Overview" > "Select Measurement" > "Third Order Intercept" > "TOI Config"
The remote commands required to perform these tasks are described in Sec-
tion 13.5.12, "Measuring the third order intercept point", on page 1078.
Marker 1/Marker 2/Marker 3/Marker 4........................................................................ 328
Search Signals............................................................................................................ 328
Search Signals
Performs a new search on the input signals and recalculates the TOI according to the
measured values.
Remote command:
CALCulate<n>:MARKer<m>:FUNCtion:TOI:SEARchsignal ONCE on page 1079
The precise TOI for the FSW in relation to the input signals is provided in the specifica-
tions document.
For remote operation, see Section 13.5.12.2, "Programming example: measuring the
TOI", on page 1081.
1. Apply a two-tone signal with equal carrier levels to the FSW input.
3. Select the "Third Order Intercept" measurement function from the "Select Measure-
ment" dialog box.
The calculated TOI is indicated in the marker information. The markers required for
calculation are displayed in the marker table.
4. If the signal changes significantly during or after the TOI measurement, use the
"Search Signals" function to start a new signal search automatically and restart the
calculation of the TOI.
Test setup:
2. Set the center frequency to 800 MHz and the frequency span to 3 MHz.
The noise is reduced, the trace is smoothed further and the intermodulation prod-
ucts can be seen clearly.
The AM modulation depth, also known as a modulation index, indicates how much the
modulated signal varies around the carrier amplitude. It is defined as:
MDepth = peak signal amplitude / unmodulated carrier amplitude
So for MDepth = 0.5, for example, the carrier amplitude varies by 50% above and below
its unmodulated level, and for MDepth = 1.0 it varies by 100%.
When this measurement is activated, marker 1 is set to the peak level, which is consid-
ered to be the carrier level. Delta markers 2 and 3 are automatically set symmetrically
to the carrier on the adjacent peak values of the trace. The markers can be adjusted
manually, if necessary.
The FSW calculates the power at the marker positions from the measured levels. The
AM modulation depth is calculated as the ratio between the power values at the refer-
ence marker and at the delta markers. If the powers of the two AM side bands are
unequal, the mean value of the two power values is used for AM modulation depth cal-
culation.
As a result of the AM Modulation Depth measurement, the following values are dis-
played in the marker area of the diagram:
Label Description
Remote command:
The AM modulation depth can also be queried using the remote command
CALCulate<n>:MARKer<m>:FUNCtion:MDEPth:RESult<t>? on page 1082.
Access: "Overview" > "Select Measurement" > "AM Modulation Depth" > "AM Mod
Depth Config"
The remote commands required to perform these tasks are described in Sec-
tion 13.5.13, "Measuring the AM modulation depth", on page 1081.
Marker 1/Marker 2/Marker 3........................................................................................333
Search Signals............................................................................................................ 333
Marker Description
The marker positions can be edited; the modulation depth is then recalculated accord-
ing to the new marker values.
To reset all marker positions automatically, use the Search Signals function.
Note: Moving the marker positions manually. When the position of delta marker 2 is
changed, delta marker 3 is moved symmetrically with respect to the reference marker
1.
Delta marker 3, on the other hand, can be moved for fine adjustment independently of
marker 2.
Marker 1 can also be moved manually for re-adjustment without affecting the position
of the delta markers.
Remote command:
CALCulate<n>:MARKer<m>:X on page 1279
CALCulate<n>:DELTamarker<m>:X on page 1276
CALCulate<n>:DELTamarker<m>:X:RELative? on page 1292
Search Signals
Performs a new search on the input signal and recalculates the AM Modulation Depth
according to the measured values.
Remote command:
CALCulate<n>:MARKer<m>:FUNCtion:MDEPth:SEARchsignal ONCE
on page 1082
If the results do not meet your expectations, try the following methods to optimize the
measurement:
● Set the center frequency to the frequency of the device under test.
● Adjust the span so the peaks to the left and right of the carrier, produced by the AM
modulated signal, are clearly visible.
If the span is too wide, these signals may fall together with the carrier and the mea-
surement can not be performed.
If the span is too narrow, theses signals are outside of the measured span and the
delta markers can not find these peaks.
The rule of thumb is to set the span to three times the value of the AM modulation
frequency.
For remote operation, see Section 13.5.13.2, "Example: measuring the AM modulation
depth", on page 1082.
3. Select the "AM Modulation Depth" measurement function from the "Select Mea-
surement" dialog box.
The calculated AM Modulation Depth is indicated in the marker information. The
markers required for calculation are displayed in the marker table.
4. If the signal changes significantly during or after the AM Modulation Depth mea-
surement, use the "Search Signals" function to start a new peak search automati-
cally and restart the calculation of the AM Modulation Depth.
As the result of an EMI measurement, the measured signal levels and active markers
are displayed in a Spectrum diagram.
The marker results are also displayed in the Result Summary; in addition, the Marker
Table contains the marker results for those markers for which no final EMI test is per-
formed.
Label Description
Label Description
Δ Limit Delta between measured level and limit line (if active)
The value is colored to indicate the following states:
● green: does not exceed limit
● yellow: within margin
● red: exceeds limit
Final Result Value measured during final EMI test using specified detector at marker frequency
Some background knowledge on basic terms and principles used in EMI measure-
ments is provided here for a better understanding of the required configuration set-
tings.
● Resolution bandwidth and filter types................................................................... 337
● Detectors and dwell time.......................................................................................338
● Frequency resolution - sweep points and scaling................................................. 339
● Controlling V-Networks (LISN).............................................................................. 340
● Using transducer factors....................................................................................... 340
● Initial measurement - peak search........................................................................ 341
● Final measurement at the marker position............................................................342
● Limit checks.......................................................................................................... 342
EMI testing requires resolution filters with a 6 dB bandwidth. The EMI measurement
adds the following bandwidths, which comply to commercial and military standards, to
those already available with the base unit:
Commercial (CISPR, FFC etc.)
● 200 Hz
● 9 kHz
● 120 kHz
● 1 MHz (not with quasi-peak detector, see "Quasi-peak detector (CISPR filter only)"
on page 338)
Military (MIL Std)
● 10 Hz
● 100 Hz
● 1 kHz
● 10 kHz
● 100 kHz
● 1 MHz
If you select a CISPR or MIL filter type, the corresponding RBW that is closest to the
currently selected RBW value is used. In this case, the channel bar indicates "RBW
(CISPR)".
For the quasi-peak, CISPR Average, or RMS Average detector, the bandwidth is fixed
depending on the frequency. For more information, see Section 6.13.3.2, "Detectors
and dwell time", on page 338.
The EMI measurement adds new detectors to those already available with the base
unit. The additional detectors are especially designed for and required by EMI applica-
tions.
The additional detectors are available only if the EMI (R&S FSW-K54) measurement
option is installed. However, the EMI measurement need not be active.
See:
● "Quasipeak detector" on page 616
● "CISPR average detector" on page 617
● "RMS average detector" on page 618
The detector to be used for the initial peak search is configured in the trace settings
(see Section 8.5.1.2, "Trace settings", on page 624). The detector for the final test is
configured in the EMI marker settings, see Section 6.13.4.1, "EMI marker configura-
tion", on page 343.
Dwell time
EMC tests often require a specific dwell time for an EMI measurement. The dwell time
defines how long the FSW measures the signal at the individual frequencies. Each
detector needs a different period of time to fully charge and discharge. For details on
defining the dwell time for an EMI measurement, see "Defining a dwell time for the final
measurement" on page 342.
RMS detector
The RMS detector displays the root mean square (RMS) value over the specified dwell
time. The integration time is the specified dwell time.
See "RMS detector" on page 614
Sample detector
The sample detector displays the last value from the samples allocated to a pixel.
The sample detector is used for noise or phase noise marker calculation. However, it is
unreliable if the displayed span is much greater then the resolution bandwidth or if the
tuning steps of the local oscillator are too large. The sample detector is not recommen-
ded for EMI tests.
See "Sample detector" on page 616
The number of sweep points defines the number of measurement values collected dur-
ing one sweep. Thus, increasing the sweep points also increases the accuracy of the
results regarding the frequency resolution.
Because EMI measurements often cover a large frequency range, be sure to define an
adequate number of sweep points, especially when performing the measurement on a
logarithmic axis. As on a linear axis, the distance from one sweep point to the next is
calculated graphically on a logarithmic axis, and is not based on the frequency itself.
Thus, the frequency resolution between two sweep points deteriorates with higher fre-
quencies.
The resolution bandwidth should cover at least one sweep point (more is better). If this
condition is not met, signals or interferences can be missed during refined measure-
ment of narrowband interferers. If the distance between two sweep points is larger than
RBW/2, a warning is displayed in the status bar ("Increase Sweep Points"). If possible
for the selected RBW and span, the minimum required number of sweep points to fulfill
this condition is indicated. If the number of sweep points exceeds the limit, reduce the
span or increase the RBW.
The FSW supports a maximum of 200001 sweep points for EMI measurements.
Example:
Linear axis:
With a linear axis, the distance between the sweep points is equal, e.g. 200 kHz.
Logarithmic axis:
With a logarithmic axis, the distance between sweep points is variable. In the spectrum
from 10 Hz to 100 Hz, the distance is a few Hz. Between 100 MHz and 1 GHz, the dis-
tance is several MHz.
This number is based on typical bands measured with a single resolution bandwidth.
There are sufficient sweep points to make sure that a signal is found during the refined
measurement, even when covering 30 MHz to 1 GHz with logarithmic scaling and
120 kHz RBW.
Two-line V-networks
ESH3-Z5 N, L1
ENV216 / AMN6500 N, L1
Four-line V-networks
For the ENV216 / AMN6500 network, a 150 kHz highpass filter is available to protect
the input of the FSW.
The FSW EMI measurement provides functionality to include transducer factors in the
test setup. Transducers are devices like antennas, probes or current probes that are
connected to the FSW to measure interferences or wanted signals. The transducer
converts the measured value such as field strength, current or RFI voltage into a volt-
age across 50 Ω. During the measurement, the transducer is considered a part of the
instrument.
A transducer usually has a frequency-dependent transducer factor that includes the
frequency response of the corresponding device. During level measurement, the trans-
ducer factor automatically converts the results into the correct unit and magnitude. A
transducer factor consists of a maximum of 1001 reference values. Each reference
value includes frequency, unit and level.
The FSW EMI measurement adds several predefined transducer factors. In addition,
you can also create new and edit existing transducer factors.
For more information, see Section 11.4.1, "Basics on transducer factors",
on page 756 .
The purpose of an initial peak search is to find signals with a high interference level
quickly. The peak search is performed with a fast detector like the peak or average
detector. The initial peak search is the basis for a possible refined measurement of
interferences with the detectors specific to EMI measurements.
The results of the initial peak search are shown in the Marker Table (see Sec-
tion 6.13.2, "EMI measurement results", on page 335).
Peak searches can be performed automatically or manually.
Example:
● In the initial measurement, determine the peak on one trace using the average
detector by assigning a marker to that trace. For the marker frequency, perform a
refined measurement using the CISPR or RMS average detector.
● In the initial measurement, determine the peak on another trace using the peak
detector by assigning another marker to that trace. For this marker frequency, per-
form a refined measurement using the quasi-peak detector.
Finding peaks with the help of an initial marker peak search reduces data to be evalu-
ated and thus measurement time. A final measurement with a special EMI detector can
then refine the initial results.
The R&S FSW EMI measurement performs the final measurement automatically as
soon as a detector for the final test is defined for an EMI marker and the marker is acti-
vated. The final measurement starts immediately after the marker has been set. The
advantage of an immediate final measurement is that it eliminates the risk of measure-
ment errors based on frequency drifts of the disturbance signal.
The final measurement at the marker frequency can have a different detector than dur-
ing the initial peak search. Thus, the final measurement consumes much less time
because detectors with a long measurement time are needed only at the critical fre-
quency.
The R&S FSW EMI measurement also allows you to use multiple detectors for the final
measurement. The advantage of multiple detections is that you only need one test run
to see if the results comply with the limits specified in a standard. The detectors for the
final EMI tests are defined in the marker configuration, as opposed to the trace detec-
tor which is used for the initial peak search.
The results of the final measurement are shown in the Result Summary (see Sec-
tion 6.13.2, "EMI measurement results", on page 335).
General limit line functionality is provided by the FSW base unit. The base unit also
provides various predefined limit lines that you can use for various applications.
The EMI measurement adds further predefined limit lines designed in compliance with
several EMC standards.
When using limit lines in combination with EMI measurements, the marker levels from
the initial measurement are compared to the limit line values. The result of the limit line
check is displayed in the diagram as usual.
In the EMI Result Summary, the limit check is based on the results of the final test.
Since the marker can be determined using a different detector than the final test
results, the two limit check results can differ. The difference between the limit line and
the measured value is colored to indicate the following states:
● green: does not exceed limit
● yellow: within margin
● red: exceeds limit
For more information on using limit lines, see Section 8.4.2.1, "Basics on limit lines",
on page 595.
Access: "Overview" > "Select Measurement" > "EMI" > "EMI Config"
On the FSW, EMI measurement configuration consists of the following settings.
In addition, some common settings are also relevant for EMI measurements:
● Section 11.4.2, "Transducer settings", on page 758
● "Reference Level" on page 486
● Section 8.4.2.2, "Limit line settings and functions", on page 599
● EMI marker configuration...................................................................................... 343
● EMI final measurement configuration....................................................................347
● LISN control settings............................................................................................. 351
Selected Marker
Marker name. The marker which is currently selected for editing is highlighted orange.
Remote command:
Marker selected via suffix <m> in remote commands.
Marker State
Activates or deactivates the marker in the diagram.
Remote command:
CALCulate<n>:MARKer<m>[:STATe] on page 1278
CALCulate<n>:DELTamarker<m>[:STATe] on page 1275
Remote command:
CALCulate<n>:MARKer<m>:X on page 1279
CALCulate<n>:DELTamarker<m>:X on page 1276
Marker Type
Toggles the marker type.
The type for marker 1 is always "Normal", the type for delta marker 1 is always "Delta".
These types cannot be changed.
Note: If normal marker 1 is the active marker, switching the "Mkr Type" activates an
additional delta marker 1. For any other marker, switching the marker type does not
activate an additional marker, it only switches the type of the selected marker.
"Normal" A normal marker indicates the absolute value at the defined position
in the diagram.
"Delta" A delta marker defines the value of the marker relative to the speci-
fied reference marker (marker 1 by default).
Remote command:
CALCulate<n>:MARKer<m>[:STATe] on page 1278
CALCulate<n>:DELTamarker<m>[:STATe] on page 1275
Reference Marker
Defines a marker as the reference marker which is used to determine relative analysis
results (delta marker values).
If the reference marker is deactivated, the delta marker referring to it is also deactiva-
ted.
If a fixed reference point is configured (see "Defining a Fixed Reference" on page 558),
the reference point ("FXD") can also be selected instead of another marker.
Remote command:
CALCulate<n>:DELTamarker<m>:MREFerence on page 1275
Select Marker
The "Select Marker" function opens a dialog box to select and activate or deactivate
one or more markers quickly.
Remote command:
CALCulate<n>:MARKer<m>[:STATe] on page 1278
CALCulate<n>:DELTamarker<m>[:STATe] on page 1275
The final EMI measurement can be performed with different settings than the initial
peak search. These settings are described here.
The detector to be used for the final EMI test can be defined differently for each fre-
quency, thus the detector is configured in the EMI marker settings, see "Final Test
Detector" on page 346.
Filter Type
Defines the filter type.
The following filter types are available:
● Normal (3dB)
● Channel
● RRC (not available for sweep type "FFT")
● 5-Pole (not available for sweep type "FFT")
● CISPR (6 dB) - requires EMI (R&S FSW-K54) option
● MIL Std (6 dB) - requires EMI (R&S FSW-K54) option
For more information, see Section 7.5.1.6, "Which data may pass: filter types",
on page 498.
Note: The EMI-specific filter types are available if the EMI (R&S FSW-K54) measure-
ment option is installed, even if EMI measurement is not active. If you select a CISPR
trace detector, the filter type is automatically also set to CISPR. An active CISPR filter
is indicated in the channel info, next to the RBW information. For details, see Sec-
tion 6.13.3.1, "Resolution bandwidth and filter types", on page 337.
The RBW filter configured in the bandwidth settings is identical to the filter configured
in the EMI configuration.
Remote command:
[SENSe:]BANDwidth[:RESolution]:TYPE on page 1203
RBW
Defines the resolution bandwidth. The available resolution bandwidths are specified in
the specifications document. Numeric input is always rounded to the nearest possible
bandwidth.
If "Auto" is selected, the resolution bandwidth is coupled to the selected span (for span
> 0). If the span is changed, the resolution bandwidth is automatically adjusted.
If the resolution bandwidth is defined manually, a green bullet is displayed next to the
"RBW" display in the channel bar.
For a list of supported filters, see the specifications document.
For more information see Section 7.5.1.1, "Separating signals by selecting an appropri-
ate resolution bandwidth", on page 494.
Note: Restrictions.
● For measurements on I/Q data in the frequency domain, the maximum RBW is
1 MHz.
● Some additional Gaussian filters are provided for special measurements, such as
5G NR spurious emissions measurements. They are only available if you enter the
value manually, not using the rotary knob or stepping through the filter values. They
are not supported by all applications. For these particular filters, gating is also pos-
sible. The following values indicate the 3-dB filter width:
– 51 kHz
– 150 kHz
– 250 kHz
– 400 kHz
– 450 kHz
– 6 MHz
– 8 MHz
● For EMI measurements using the quasipeak detector, the 1 MHz RBW filter is not
available (see Section 6.13.3.1, "Resolution bandwidth and filter types",
on page 337).
Remote command:
[SENSe:]BANDwidth[:RESolution] on page 1201
[SENSe:]BANDwidth[:RESolution]:AUTO on page 1202
If Auto peak search and limit lines are active, the active markers are set to the peak
delta values between the measured signal and the limit lines.
Note: The general search functions Auto Max Peak Search / Auto Min Peak Search
are not available for EMI measurements.
Remote command:
CALCulate<n>:MARKer<m>:FUNCtion:FMEasurement:PEAKsearch:AUTO
on page 1085
Dwell Time
Sets the dwell time for the EMI marker measurement.
For more information see Section 6.13.3.2, "Detectors and dwell time", on page 338.
Remote command:
CALCulate<n>:MARKer<m>:FUNCtion:FMEasurement:DWELl on page 1086
Remote command:
CALCulate<n>:MARKer<m>:FUNCtion:FMEasurement:DETector on page 1084
CALCulate<n>:DELTamarker<m>:FUNCtion:FMEasurement:DETector
on page 1084
Res BW CISPR
Automatically sets the measurement bandwidth for commercial EMC standards
according to CISPR.
For more information, see Section 6.13.3.1, "Resolution bandwidth and filter types",
on page 337.
Remote command:
Filter type:
[SENSe:]BANDwidth[:RESolution]:TYPE on page 1203
Filter bandwidth:
[SENSe:]BANDwidth[:RESolution] on page 1201
Res BW MIL
Automatically sets the measurement bandwidth for military EMC standards.
For more information, see Section 6.13.3.1, "Resolution bandwidth and filter types",
on page 337.
Remote command:
Filter type:
[SENSe:]BANDwidth[:RESolution]:TYPE on page 1203
Filter bandwidth:
[SENSe:]BANDwidth[:RESolution] on page 1201
LISN Type
Selects the network type and activates output to the network via the user port of the
FSW. The network type determines the supported phases (see Table 6-16).
"Off" disables LISN control and output.
Remote command:
INPut:LISN[:TYPE] on page 1087
Phase
Selects the phase to be measured. Phase N and L1 are included in all four LISN.
Phase L2 and L3 are only included in four-line networks.
You can select one phase only for each measurement.
Remote command:
INPut:LISN:PHASe on page 1087
Marker demodulation
The FSW is able to demodulate AM and FM signals for acoustic tests and monitoring
purposes.
When the demodulator function is active, the EMI measurement demodulates the sig-
nal continuously (regardless of the "Continuous Demodulation" setting in the marker
function configuration). The demodulation begins as soon as a marker is activated.
During the initial measurement, demodulation is performed for the entire measurement
span; during the final measurement only the detected peak marker positions are
demodulated (for the defined dwell time). You can listen to the results during the mea-
surement using headphones or the internal speaker.
For more information, see Section 8.3.4.7, "Demodulating marker values and providing
audio output (marker demodulation)", on page 581.
Limit lines
General limit line functionality is provided by the FSW base unit. The base unit also
provides various predefined limit lines that you can use for various applications.
The EMI measurement adds further predefined limit lines designed in compliance with
several EMC standards.
Limit line configuration is described in Section 8.4.2.2, "Limit line settings and func-
tions", on page 599.
Test reports
The FSW features a test report generator. A test report is a document that summarizes
the results and configuration of measurements.
Test reports are based on a general template, and are completed with user-defined,
measurement-specific contents. You can create multiple templates for different applica-
tions.
Test reports are described in Section 10.6, "Working with test reports", on page 712.
For remote operation, see Section 13.5.14.8, "Programming example: EMI measure-
ment", on page 1090.
1. Select [MODE] on the front panel and select the "Spectrum" application.
4. Select [MEAS] on the front panel and select the "EMI" measurement.
The EMI main menu is displayed.
6. Define the resolution bandwidth and filter type to be used for the measurement.
By default, the FSW uses a filter with a 3-db bandwidth. EMI measurements usu-
ally require a filter with a 6 dB bandwidth.
7. Define the dwell time for which each marker position is measured during the final
measurement.
8. To obtain an overview of peak values in the input signal during the initial measure-
ment, activate the "Auto Peak Search".
As soon as a sweep is started, the FSW looks for the strongest peaks in the fre-
quency range you are measuring and positions one of the active markers on those
peaks. The number of active markers determines the number of detected peaks;
no additional markers are activated.
9. Define the type of scaling for the frequency axis according to the definition of the
limit lines in the standard.
12. Optionally, select the "Marker Demod Config" to configure continuous marker
demodulation.
Demodulation begins immediately with the next measurement. During the initial
measurement, demodulation is performed for the entire measurement span; during
the final measurement only the detected peak marker positions are demodulated
(for the defined dwell time).
13. Increase the number of sweep points for the EMI measurement.
a) Select [SWEEP] on the front panel.
14. Optionally, select or configure limit lines to check the marker results against.
a) Select [Lines] and then the "Lines Config" , then select the "Lines Config" tab.
b) In the "Line Config" dialog box, select the "View Filter" option: "Show Compati-
ble".
All limit lines that comply with the following conditions are displayed in the over-
view:
● Stored in the limits subfolder of the main installation folder of the instru-
ment
● File extension .LIN
● Compatible to the current EMI measurement settings
c) Select the "Check Traces" setting for a limit line in the overview.
d) Select the trace numbers to be included in the limit check. You can assign the
same limit line to several traces.
15. The default unit dBm is not suitable for EMI measurements. Define a suitable unit
for the measured values, or select a transducer.
To change the unit:
Select [AMPT] > "Amplitude Config" > "Unit".
To select a transducer:
a) Select [SETUP].
b) Select "Transducer".
c) In the "Transducer" dialog box, set the "View Filter" to "Show Compatible" to
determine the available transducers for the current EMI measurement setup.
d) In the overview, select the "Active" setting for a transducer line.
A common measurement task that you can do with the EMI measurement is to detect
radio frequency interference (RFI) or electromagnetic interferences (EMI).
The measurement shows signal levels over a particular frequency range. A typical fre-
quency range for EMI measurements is 150 kHz to 1 GHz. Usually, the captured signal
characteristics are unknown. Thus, the best way to start the measurement is to preset
the FSW and perform a peak search to obtain a general overview.
1. Select [PRESET] .
The FSW restores the default settings.
3. Select [MEAS] on the front panel and select the "EMI" measurement.
The EMI main menu is displayed.
5. Define the resolution bandwidth and filter type for the measurement.
By default, the FSW uses a filter with a 3-db bandwidth. EMI measurements usu-
ally require a filter with a 6-dB bandwidth.
6. Define the dwell time for which each marker position is measured during the final
measurement.
7. To obtain an overview of exceptional values in the input signal during the initial
measurement, activate the "Auto Peak Search".
c) Define the detectors to use for the initial measurement. Select the peak detec-
tor for trace 1 and the average detector for trace 2.
The peak detector ensures that the detected peak levels in the frequency range
covered by one pixel are displayed.
The FSW now displays two traces. Trace 1 shows the peak values, trace 2 shows
the average values.
10. Increase the number of sweep points for the EMI measurement.
a) Select [SWEEP] on the front panel.
b) Select the "Sweep Config" .
c) Set the number of "Sweep Points" to 200000.
11. Select [AMPT] , then select the "Amplitude Config" and, in the "Amplitude" dialog
box, select V as the "Unit".
If the results do not meet your expectations, try the following methods to optimize the
measurement:
Dwell time
Consider the following when defining the dwell time:
● Unknown signals: select a dwell time of at least 1 second to ensure that pulses
down to a frequency of 5 Hz are weighted correctly
● Pulsed signals or signals that fluctuate slowly: the dwell time must cover at
least the time until the first signal peak is measured; can require long dwell time
● Unmodulated signals or signals with a high modulation frequency: the dwell
time must cover at least the time until the first signal peak is measured; usually
shorter than for pulsed signals
Using this overview, you can easily configure an entire channel from input over pro-
cessing to output and analysis by stepping through the dialog boxes as indicated.
In particular, the "Overview" provides quick access to the following configuration dialog
boxes (listed in the recommended order of processing):
1. "Select Measurement"
See Section 6, "Measurements and results", on page 129
2. Input
Section 7.2, "Data input and output", on page 361
3. Amplitude
See Section 7.4, "Amplitude and vertical axis configuration", on page 481
4. Frequency
See Section 7.3, "Frequency and span configuration", on page 473
5. (Optionally:) Trigger/Gate
See Section 7.6, "Trigger and gate configuration", on page 510
6. Bandwidth
See Section 7.5.2, "Bandwidth, filter and sweep settings", on page 500
(For SEM measurements: SEM Setup, see Section 6.6.5, "SEM configuration",
on page 249)
(For Spurious measurements: Spurious Setup, see Section 6.7.4, "Spurious emis-
sions measurement configuration", on page 285)
7. (Optionally:) Outputs
See Section 7.2.8, "Output settings", on page 468
8. Analysis
See Section 8, "Common analysis and display functions", on page 536
9. Display
See Section 8.1, "Result display configuration", on page 536
To configure settings
► Select any button to open the corresponding dialog box.
Select a setting in the channel bar (at the top of the channel tab) to change a spe-
cific setting.
Preset Channel
Select "Preset Channel" in the lower left-hand corner of the "Overview" to restore all
measurement settings in the current channel to their default values.
Note: Do not confuse "Preset Channel" with the [Preset] key, which restores the entire
instrument to its default values and thus closes all channels on the FSW (except for the
default channel)!
Remote command:
SYSTem:PRESet:CHANnel[:EXEC] on page 1366
The FSW can analyze signals from different input sources and provide various types of
output (such as noise or trigger signals).
Using one of the "TRIGGER INPUT / OUTPUT" connectors of the FSW, the FSW can
use a signal from an external device as a trigger to capture data. Alternatively, the
internal trigger signal used by the FSW can be output for use by other connected devi-
ces. Using the same trigger on several devices is useful to synchronize the transmitted
and received signals within a measurement.
For details on the connectors see the FSW "Getting Started" manual.
Trigger output
The FSW can provide output to another device either to pass on the internal trigger
signal, or to indicate that the FSW itself is ready to trigger.
The trigger signal can be output by the FSW automatically, or manually by the user. If it
is provided automatically, a high signal is output when the FSW has triggered due to a
sweep start ("Device Triggered"), or when the FSW is ready to receive a trigger signal
after a sweep start ("Trigger Armed").
Manual triggering
If the trigger output signal is initiated manually, the length and level (high/low) of the
trigger pulse is also user-definable. Note, however, that the trigger pulse level is always
opposite to the constant signal level defined by the output "Level" setting, e.g. for
"Level" = "High", a constant high signal is output to the connector until "Send Trigger"
is selected. Then, a low pulse is provided.
The measured IF signal or displayed video signal (i.e. the filtered and detected IF sig-
nal) can be provided at the IF/VIDEO/DEMOD or "IF OUT 2 GHz/ IF OUT 5 GHz" out-
put connector.
The video output is a signal of 1 V. It can be used, for example, to control demodula-
ted audio frequencies.
The IF output is a signal of the measured level at a specified frequency.
The "2ND IF" output is a signal with a bandwidth of 2 GHz at the frequency 2 GHz.
This output is only available if the "IF OUT 2 GHz/ IF OUT 5 GHz" output connector is
installed. (The availability of this connector depends on the instrument model.)
If the optional 2 GHz / 5 GHz bandwidth extension (R&S FSW-B2000/B5000) is active,
the "IF OUT 2 GHz/ IF OUT 5 GHz" output connector is used to transfer the measured
data from the FSW to the connected oscilloscope. In this case, the "2ND IF" output is
automatically deactivated. It is not reactivated when the B2000/B5000 option is
switched off.
The frequency at which the active B5000 option transmits data to the oscilloscope via
the "IF 5 GHz OUT" connector depends on the analysis bandwidth.
Restrictions
Note the following restrictions for data output:
● IF and video output is only available in the time domain (zero span).
● For I/Q data, only IF output is available.
● IF output is not available if any of the following conditions apply:
– The optional "Digital Baseband" interface is active (for input or output)
IF WIDE OUTPUT
For bandwidths > 80 MHz, but less than 512 MHz, the IF output is provided at the "IF
WIDE OUTPUT" connector.
For bandwidths larger than 512 MHz, IF output is not available.
In this case, the IF output frequency cannot be defined manually, but is determined
automatically depending on the center frequency. The currently used output frequency
is indicated in the "IF Wide Out Frequency" field of the "Output" dialog box. For details
on the used frequencies see the specifications document.
2ND IF Output
For instrument models FSW26/43/50/67/85, the IF output can also be provided at the
optional "IF OUT 2 GHz" output connector at a frequency of 2 GHz and with a band-
width of 2 GHz. The IF output can then be analyzed by a different instrument, for
example an R&S®RTO oscilloscope.
For instrument model FSW85, the IF output can also be provided at the optional "IF
OUT 2 GHz" output connector at a frequency of 2 GHz and with a bandwidth of
2 GHz. The IF output can then be analyzed by a different instrument. However, con-
sider the note on the 2 GHz / 5 GHz bandwidth extension option below.
If "2ND IF" output is activated, the measured values are no longer available on the dis-
play; thus, the trace data currently displayed on the FSW becomes invalid. A message
in the status bar indicates this situation. The message also indicates whether the side-
bands of the IF spectrum output are in normal or inverted order compared to the RF
signal, which depends on the used center frequency.
Prerequisites
Note the following prerequisites for output to the "IF OUT 2 GHz" connector ("2ND
IF"):
● Instrument model FSW26/43/50/67/85; external mixers can be used
● Zero span mode, I/Q Analyzer, or optional application supporting B2000
(See the FSW I/Q Analyzer and I/Q Input User Manual)
● Center frequency ≥ 5.5 GHz
● Optional 2 GHz bandwidth extension (R&S FSW-B2000) is not active
Prerequisites for output to the "IF OUT 5 GHz" connector ("2ND IF"):
● Instrument model FSW43/85; external mixers can be used
● Zero span mode, I/Q Analyzer, or optional application supporting B5000
● Center frequency ≥ 9.5 GHz
● Optional 5 GHz bandwidth extension (R&S FSW-B5000) is not active
Access: "Overview" > "Input/Frontend" > "Input Source" > "Radio Frequency"
RF Input Protection
The RF input connector of the FSW must be protected against signal levels that
exceed the ranges specified in the specifications document. Therefore, the FSW is
equipped with an overload protection mechanism for DC and signal frequencies up to
30 MHz. This mechanism becomes active as soon as the power at the input mixer
exceeds the specified limit. It ensures that the connection between RF input and input
mixer is cut off.
When the overload protection is activated, an error message is displayed in the status
bar ("INPUT OVLD"), and a message box informs you that the RF input was discon-
nected. Furthermore, a status bit (bit 3) in the STAT:QUES:POW status register is set.
In this case, you must decrease the level at the RF input connector and then close the
message box. Then measurement is possible again. Reactivating the RF input is also
possible via the remote command INPut:ATTenuation:PROTection:RESet.
If an external frontend is active, select the connector the external frontend is connected
to. You cannot use the other RF input connector simultaneously for the same channel.
However, you can configure the use of the other RF input connector for another active
channel at the same time.
"Input 1" 1.00 mm RF input connector for frequencies up to 85 GHz (90 GHz
with option R&S FSW-B90G)
"Input 2" 1.85 mm RF input connector for frequencies up to 67 GHz
Remote command:
INPut:SELect on page 1116
INPut:TYPE on page 1117
Input Coupling
The RF input of the FSW can be coupled by alternating current (AC) or direct current
(DC).
For an active external frontend, input coupling is always AC.
Not available for input from the optional "Analog Baseband" interface.
Not available for input from the optional "Digital Baseband" interface.
AC coupling blocks any DC voltage from the input signal. AC coupling is activated by
default to prevent damage to the instrument. Very low frequencies in the input signal
can be distorted.
However, some specifications require DC coupling. In this case, you must protect the
instrument from damaging DC input voltages manually. For details, refer to the specifi-
cations document.
Remote command:
INPut:COUPling on page 1113
Impedance
The FSW has an internal impedance of 50 Ω. However, some applications use other
impedance values. To match the impedance of an external application to the impe-
dance of the FSW, an impedance matching pad can be inserted at the input. If the type
and impedance value of the used matching pad is known to the FSW, it can convert
the measured units accordingly so that the results are calculated correctly.
(See "Reference Level" on page 486).
For an active external frontend, impedance is always 50 Ω.
This function is not available for input from the optional "Digital Baseband" interface.
Not all settings are supported by all FSW applications.
The impedance conversion does not affect the level of the output signals (such as IF,
video, demod, digital I/Q output).
"50Ω" (Default:) no conversion takes place
Direct Path
Enables or disables the use of the direct path for small frequencies.
In spectrum analyzers, passive analog mixers are used for the first conversion of the
input signal. In such mixers, the LO signal is coupled into the IF path due to its limited
isolation. The coupled LO signal becomes visible at the RF frequency 0 Hz. This effect
is referred to as LO feedthrough.
To avoid the LO feedthrough the spectrum analyzer provides an alternative signal path
to the A/D converter, referred to as the direct path. By default, the direct path is
selected automatically for RF frequencies close to zero. However, this behavior can be
disabled. If "Direct Path" is set to "Off", the spectrum analyzer always uses the analog
mixer path.
For an active external frontend, the direct path is always used automatically for fre-
quencies close to zero.
"Auto" (Default) The direct path is used automatically for frequencies close
to zero.
"Off" The analog mixer path is always used.
Remote command:
INPut:DPATh on page 1114
YIG-Preselector
Enables or disables the YIG-preselector.
An internal YIG-preselector at the input of the FSW ensures that image frequencies are
rejected. However, image rejection is only possible for a restricted bandwidth. To use
the maximum bandwidth for signal analysis you can disable the YIG-preselector at the
input of the FSW, which can lead to image-frequency display.
Note: Note that the YIG-preselector is active only on frequencies greater than 8 GHz.
Therefore, switching the YIG-preselector on or off has no effect if the frequency is
below that value.
To use the optional 90 GHz frequency extension (R&S FSW-B90G), the YIG-preselec-
tor must be disabled.
The "YIG-Preselector" is off by default.
Note:
For the following measurements, the "YIG-Preselector" is off by default (if available).
● I/Q Analyzer
● All secondary applications in MSRA operating mode
● Real-time (and thus in all secondary applications in MSRT operating mode)
Remote command:
INPut:FILTer:YIG[:STATe] on page 1115
Preselector Adjust
Activates or deactivates the preselector adjustment.
This function is only available for instrument modelsFSW43/50/67/85, for frequency
sweeps in the Spectrum application.
Generally, sweeps exceeding a certain span use different signal paths to measure the
required spectrum. To minimize the hysteresis impact of the YIG preselector at the
transition frequencies, you can activate this function. It is applied only when the YIG-
preselector is active.
If activated, the FSW automatically performs a short internal adjustment. If you change
the frequency or span settings, the adjustment is repeated.
If activated, "PRADJ" is indicated in the window title bar.
Remote command:
CALibration:PADJust[:STATe] on page 1113
Input Connector
Determines which connector the input data for the measurement is taken from.
For more information on the optional "Analog Baseband" interface, see the FSW I/Q
Analyzer and I/Q Input user manual.
"RF" (Default:) The "RF Input" connector
"RF Probe" The "RF Input" connector with an adapter for a modular probe
This setting is only available if a probe is connected to the "RF Input"
connector.
It is not available for an active external frontend.
The FSW can also analyze data from a connected power sensor.
● Basics on power sensors...................................................................................... 369
● Power sensor settings...........................................................................................370
● How to work with a power sensor......................................................................... 375
Power sensors can also be used to trigger a measurement at a specified power level,
e.g. from a signal generator (see "Using a power sensor as an external power trigger"
on page 370).
Result display
The results of the power sensor measurements are displayed in the marker table. For
each power sensor, a row is inserted. The sensor index is indicated in the "Type" col-
umn.
Figure 7-2: Connecting a power sensor using the POWER SENSOR interface
The FSW receives an external trigger signal when the defined trigger level is measured
by the power sensor. Power measurement results are provided as usual.
The "Gate Mode" Level is not supported for R&S power sensors. The signal sent by
these sensors merely reflects the instant the level is first exceeded, rather than a time
period. However, only time periods can be used for gating in level mode. Thus, the trig-
ger impulse from the sensors is not long enough for a fully gated measurement; the
measurement cannot be completed. For details on gating see Section 7.6.2.1, "Gated
measurements", on page 523.
For details see "How to configure a power sensor as an external (PSE) trigger"
on page 377.
State............................................................................................................................371
Continuous Value Update........................................................................................... 372
Select.......................................................................................................................... 372
Zeroing Power Sensor................................................................................................ 372
Frequency Manual...................................................................................................... 372
Frequency Coupling.................................................................................................... 373
Unit/Scale....................................................................................................................373
Meas Time/Average.................................................................................................... 373
Setting the Reference Level from the Measurement Meas -> Ref.............................. 373
Reference Value..........................................................................................................373
Use Ref Level Offset................................................................................................... 373
Sensor Level Offset.....................................................................................................374
Average Count (Number of Readings)........................................................................374
Duty Cycle...................................................................................................................374
Using the power sensor as an external trigger............................................................374
└ External Trigger Level...................................................................................374
└ Hysteresis..................................................................................................... 375
└ Trigger Holdoff.............................................................................................. 375
└ Drop-Out Time.............................................................................................. 375
└ Slope.............................................................................................................375
State
Switches the power measurement for all power sensors on or off. Note that in addition
to this general setting, each power sensor can be activated or deactivated individually
by the Select setting on each tab. However, the general setting overrides the individual
settings.
Select
Selects the individual power sensor for usage if power measurement is generally acti-
vated (State function).
The detected serial numbers of the power sensors connected to the instrument are
provided in a selection list. For each of the four available power sensor indexes
("Power Sensor 1"..."Power Sensor 4"), which correspond to the tabs in the configura-
tion dialog, one of the detected serial numbers can be assigned. The physical sensor is
thus assigned to the configuration setting for the selected power sensor index.
By default, serial numbers not yet assigned are automatically assigned to the next free
power sensor index for which "Auto Assignment" is selected.
Alternatively, you can assign the sensors manually by deactivating the "Auto" option
and selecting a serial number from the list.
Remote command:
[SENSe:]PMETer<p>[:STATe] on page 1186
SYSTem:COMMunicate:RDEVice:PMETer<p>:DEFine on page 1180
SYSTem:COMMunicate:RDEVice:PMETer<p>:CONFigure:AUTO[:STATe]
on page 1180
SYSTem:COMMunicate:RDEVice:PMETer<p>:COUNt? on page 1180
Frequency Manual
Defines the frequency of the signal to be measured. The power sensor has a memory
with frequency-dependent correction factors. This allows extreme accuracy for signals
of a known frequency.
Remote command:
[SENSe:]PMETer<p>:FREQuency on page 1184
Frequency Coupling
Selects the coupling option. The frequency can be coupled automatically to the center
frequency of the instrument or to the frequency of marker 1.
Remote command:
[SENSe:]PMETer<p>:FREQuency:LINK on page 1184
Unit/Scale
Selects the unit with which the measured power is to be displayed. Available units are
dBm, dB, W and %.
If dB or % is selected, the display is relative to the reference value that is defined with
either the "Meas -> Ref" setting or the "Reference Value" setting.
Remote command:
UNIT<n>:PMETer<p>:POWer on page 1187
UNIT<n>:PMETer<p>:POWer:RATio on page 1188
Meas Time/Average
Selects the measurement time or switches to manual averaging mode. In general,
results are more precise with longer measurement times. The following settings are
recommended for different signal types to obtain stable and precise results:
"Short" Stationary signals with high power (> -40dBm), because they require
only a short measurement time and short measurement time provides
the highest repetition rates.
"Normal" Signals with lower power or modulated signals
"Long" Signals at the lower end of the measurement range (<-50 dBm) or
Signals with lower power to minimize the influence of noise
"Manual" Manual averaging mode. The average count is set with the Average
Count (Number of Readings) setting.
Remote command:
[SENSe:]PMETer<p>:MTIMe on page 1185
[SENSe:]PMETer<p>:MTIMe:AVERage[:STATe] on page 1185
Setting the Reference Level from the Measurement Meas -> Ref
Sets the currently measured power as a reference value for the relative display. The
reference value can also be set manually via the Reference Value setting.
Remote command:
CALCulate<n>:PMETer<p>:RELative[:MAGNitude]:AUTO ONCE on page 1182
Reference Value
Defines the reference value in dBm used for relative power meter measurements.
Remote command:
CALCulate<n>:PMETer<p>:RELative[:MAGNitude] on page 1182
Remote command:
[SENSe:]PMETer<p>:ROFFset[:STATe] on page 1186
Duty Cycle
Sets the duty cycle to a percent value for the correction of pulse-modulated signals and
activates the duty cycle correction. With the correction activated, the sensor calculates
the signal pulse power from this value and the mean power.
Remote command:
[SENSe:]PMETer<p>:DCYCle[:STATe] on page 1183
[SENSe:]PMETer<p>:DCYCle:VALue on page 1183
The following step-by-step instructions demonstrate how to set up a power sensor. For
details on individual functions and settings see Section 7.2.3.2, "Power sensor set-
tings", on page 370.
The remote commands required to perform these tasks are described in Sec-
tion 13.7.1.8, "Working with power sensors", on page 1179.
Power sensors can also be used to trigger a measurement at a specified power level,
e.g. from a signal generator.
This is described in "How to configure a power sensor as an external (PSE) trigger"
on page 377.
1. To display the "Power Sensor" tab of the "Input" dialog box, do one of the following:
● Select "Input" from the "Overview".
● Select [INPUT/OUTPUT] and then "Power Sensor Config".
2. Select the tab for the power sensor index you want to configure, e.g. "Power Sen-
sor 1".
3. Press "Select" to analyze the power sensor data according to the current configura-
tion when power measurement is activated.
4. From the selection list with serial numbers of connected power sensors, select the
sensor you want to configure.
To have newly connected power sensors assigned to a tab automatically (default),
select "Auto".
5. Define the frequency of the signal whose power you want to measure.
a) To define the frequency manually, select "Frequency Manual" and enter a fre-
quency.
b) To determine the frequency automatically, select "Frequency Coupling" and
then either "Center", to use the center frequency, or "Marker", to use the fre-
quency defined by marker 1.
7. Select the measurement time for which the average is calculated, or define the
number of readings to average. To define the number of readings to be taken into
account manually, select "Manual" and enter the number in the "Number of Read-
ings" field.
8. To activate the duty cycle correction, select "DutyCycle" and enter a percentage as
the correction value.
9. If you selected "dB" or "%" as units (relative display), define a reference value:
a) To set the currently measured power as a reference value, press "Meas ->
Ref".
b) Alternatively, enter a value manually in the "Reference Value" field.
c) Optionally, select the "Use Ref Level Offset" option to take the reference level
offset set for the analyzer into account for the measured power.
10. To use the power sensor as an external power trigger, select the "External Power
Trigger" option and define the trigger settings.
For details see "How to configure a power sensor as an external (PSE) trigger"
on page 377.
12. Set the "Power Sensor State" at the top of the "Power Sensor" tab to "On" to acti-
vate power measurement for the selected power sensors.
The results of the power measurement are displayed in the marker table (Function:
"Sensor <1...4>").
1. To display the "Power Sensor" tab of the "Input" dialog box, do one of the following:
2. Select the tab that is assigned to the power sensor you want to zero.
4. Disconnect all signals sending input to the power sensor and press [ENTER] to
continue.
3. In the "Power Sensor" tab of the "Input" dialog box, select the "External Power Trig-
ger" option.
4. Enter the power level at which a trigger signal is to be generated ("External Trigger
Level") and the other trigger settings for the power sensor trigger.
6. In the "Trigger And Gate" dialog box, select "Signal Source" = "PSE".
The FSW is configured to trigger when the defined conditions for the power sensor
occur. Power measurement results are provided as usual.
If the FSW optional External Generator Control is installed, you can operate various
commercially available generators as an external generator with the FSW. Thus, scalar
network analysis with the FSW is possible.
● About external generator control...........................................................................378
● Basics on external generator control.....................................................................378
● External generator control settings....................................................................... 387
● How to work with external generator control......................................................... 395
● Measurement example: calibration with an external generator............................ 398
A common measurement setup includes a signal generator, a device under test (DUT),
and a signal and spectrum analyzer, for example the FSW. In this setup, the signal
analyzer can control which signal the generator is to send, which is in turn measured
by the analyzer. This process is referred to as external generator control. The genera-
tor in this setup is referred to as a tracking generator.
A measurement with a tracking generator is useful to measure any effects on the
power level caused by the cables and connectors from the signal generator and the
signal analyzer in advance. The known effects can then be removed from the mea-
surement results to obtain accurate information on the DUT.
Some background knowledge on basic terms and principles used for external genera-
tor control is provided here for a better understanding of the required configuration set-
tings.
TTL synchronization
In addition, TTL synchronization can be used with some Rohde & Schwarz generators
connected via GPIB. The TTL interface is included in the AUX control connector of the
External Generator Control option.
Using the TTL interface allows for considerably higher measurement rates than pure
GPIB control, because the frequency stepping of the FSW is directly coupled with the
frequency stepping of the generator. For details see "Coupling the frequencies"
on page 384.
In Figure 7-3 the TTL connection is illustrated using an R&S SMA100B generator, for
example.
BNC Trigger
BNC Blank
In Figure 7-4 the TTL connection is illustrated using an R&S SMU generator, for exam-
ple.
Analyzer rear
BNC Blank
BNC Trigger
BNC Trigger
BNC Blank
The external generator can be used to calibrate the data source by performing either
transmission or reflection measurements.
Transmission Measurement
This measurement yields the transmission characteristics of a two-port network. The
external generator is used as a signal source. It is connected to the input connector of
the DUT. The input of the FSW is fed from the output of the DUT. A calibration can be
carried out to compensate for the effects of the test setup (e.g. frequency response of
connecting cables).
Reflection Measurement
Scalar reflection measurements can be carried out using a reflection-coefficient mea-
surement bridge.
Connection errors
If no external generator is connected, if the connection address is not correct, or the
generator is not ready for operation, an error message is displayed (e.g."Ext. Genera-
tor TCPIP Handshake Error!", see "Displayed information and errors" on page 386).
Calibration mechanism
A common measurement setup includes a signal generator, a device under test (DUT),
and a signal and spectrum analyzer. Therefore, it is useful to measure the attenuation
or gain caused by the cables and connectors from the signal generator and the signal
analyzer in advance. The known level offsets can then be removed from the measure-
ment results to obtain accurate information on the DUT.
Calculating the difference between the currently measured power and a reference
trace is referred to as calibration. Thus, the measurement results from the controlled
external generator - including the inherent distortions - can be used as a reference
trace to calibrate the measurement setup.
The inherent frequency and power level distortions can be determined by connecting
the FSW to the signal generator. The FSW sends a predefined list of frequencies to the
signal generator (see also "Coupling the frequencies" on page 384). The signal gener-
ator then sends a signal with the specified level at each frequency in the predefined
list. The FSW measures the signal and determines the level offsets to the expected
values.
Normalization
Once the measurement setup has been calibrated and the reference trace is available,
subsequent measurement results can be corrected according to the calibration factors,
if necessary. Results are corrected by subtracting the reference trace from the mea-
surement results. This process is referred to as normalization and can be activated or
deactivated as required. If normalization is activated, "NOR" is displayed in the channel
bar, next to the indication that an external generator is being used ("Ext.Gen"). The
normalized trace from the calibration sweep is a constant 0 dB line, as <calibration
trace> - <reference trace> = 0.
As long as the same settings are used for measurement as for calibration, the normal-
ized measurement results should not contain any inherent frequency or power distor-
tions. Thus, the measured DUT values are very accurate.
Approximate normalization
As soon as any of the calibration measurement settings are changed, the stored refer-
ence trace is longer identical to the new measurement results. However, if the mea-
surement settings do not deviate too much, the measurement results can still be nor-
malized approximately using the stored reference trace. An "APX" label in the channel
bar (instead of "NOR") indicates the approximated normalization.
Approximation is necessary if one or more of the following values deviate from the cali-
bration settings:
● Coupling (RBW, VBW, SWT)
● Reference level, RF attenuation
● Start or stop frequency
● Output level of external generator
● Detector (max. peak, min. peak, sample, etc.)
● Frequency deviation at a maximum of 1001 points within the set sweep limits (cor-
responds to a doubling of the span)
Differences in level settings between the reference trace and the current instrument
settings are considered automatically. If the span is reduced, a linear interpolation of
the intermediate values is applied. If the span increases, the values at the left or right
border of the reference dataset are extrapolated to the current start or stop frequency.
The reference dataset is extended by constant values.
Thus, you can change various instrument settings without giving up normalization. The
necessity to carry out a new normalization is reduced to a minimum.
Note that the normalized measurement data is stored, not the original reference trace.
Thus, if you store the normalized trace directly after calibration, without changing any
settings, the transducer factor is 0 dB for the entire span (by definition of the normal-
ized trace).
Reference trace
The calibration results are stored internally on the FSW as a reference trace. For each
measured sweep point, the offset to the expected values is determined. If normaliza-
tion is activated, the offsets in the reference trace are removed from the current mea-
surement results to compensate for the inherent distortions.
Reference line
The reference line is defined by the Reference Value and Reference Position in the
"External Generator" > "Source Calibration" settings. It is similar to the Reference
Level defined in the "Amplitude" settings. However, as opposed to the reference level,
this reference line only affects the y-axis scaling in the diagram. It has no effect on the
expected input power level or the hardware settings.
The reference line determines the range and the scaling of the y-axis, just as the refer-
ence level does.
The normalized reference trace (0 dB directly after calibration) is displayed on this ref-
erence line, indicated by a red line in the diagram. By default, the reference line is dis-
played at the top of the diagram. If you shift the reference line, the normalized trace is
shifted, as well.
Automatic coupling
If automatic coupling is used, the output frequency of the generator (source frequency)
is calculated as follows:
Numerator
FGenerator FAnalyzer FOffset
Deno min ator
Equation 7-1: Output frequency of the generator
Where:
FGenerator = output frequency of the generator
FOffset = frequency offset for FAnalyzer, for example for frequency-converting measure-
ments or harmonics measurements
The value range for the offset depends on the selected generator. The default setting is
0 Hz. Offsets other than 0 Hz are indicated by the "FRQ" label in the channel bar (see
also "Displayed information and errors" on page 386).
The calibration sweep nevertheless covers the entire span defined by the FSW. How-
ever, no input is received from the generator outside the generator's defined limits.
TTL synchronization
Some Rohde & Schwarz signal generators support TTL synchronization when connec-
ted via GPIB. The TTL interface is included in the AUX control connector of the Exter-
nal Generator Control option.
When pure GPIB connections are used between the FSW and the signal generator, the
FSW sets the generator frequency for each frequency point individually via GPIB. Only
when the setting procedure is finished, the FSW can measure the next sweep point.
For generators with a TTL interface, the FSW sends a list of the frequencies to be set
to the generator before the beginning of the first sweep. Then the FSW starts the
sweep and the next frequency point is selected by both the FSW and the generator
using the TTL handshake line "TRIGGER". The FSW can only measure a value when
the generator signals the end of the setting procedure via the "BLANK" signal.
Using the TTL interface allows for considerably higher measurement rates, because
the frequency stepping of the FSW is directly coupled with the frequency stepping of
the generator.
Reverse sweep
The frequency offset for automatic coupling can be used to sweep in the reverse direc-
tion. To do so, define a negative offset in the external generator measurement configu-
ration. (Note that the frequency is defined as the unsigned value of the equation, thus a
negative frequency is not possible.)
If the offset is adjusted so that the sweep of the generator crosses the minimum gener-
ator frequency, a message is displayed in the status bar ("Reverse Sweep via min. Ext.
Generator Frequency!").
Channel bar
If external generator control is active, some additional information is displayed in the
channel bar.
Label Description
EXT TG: <source power> External generator active; signal sent with <source power> level
Label Description
Message Description
"Ext. Generator GPIB Handshake Error!" / Connection to the generator is not possible, e.g. due to a
cable damage or loose connection or wrong address.
"Ext. Generator TCPIP Handshake Error!" /
"Ext. Generator TTL Handshake Error!"
"Ext. Generator Limits Exceeded!" The allowed frequency or power ranges for the generator
were exceeded.
"Reverse Sweep via min. Ext. Generator Fre- Reverse sweep is performed; frequencies are reduced to
quency!" the minimum frequency, then increased again; see
"Reverse sweep" on page 386.
"Ext. Generator File Syntax Error!" Syntax error in the generator setup file (see "Generator
setup files" on page 381
"Ext. Generator Command Error!" Missing or wrong command in the generator setup file
(see "Generator setup files" on page 381
"Ext. Generator Visa Error!" Error with Visa driver provided with installation (very
unlikely)
Overloading
At a reference level of -10 dBm and at an external generator output level of the same
value, the FSW operates without overrange reserve. That means the FSW is in danger
of being overloaded if a signal is applied whose amplitude is higher than the reference
line. In this case, either the message "RF OVLD" for overload or "OVLD" for exceeded
display range (clipping of the trace at the upper diagram border = overrange) is dis-
played in the status line.
Overloading can be avoided as follows:
● Reducing the output level of the external generator ("Source Power" on page 389
in "External Generator > Measurement Configuration")
● Increasing the reference level (Reference Level in the "Amplitude" menu)
For more information on external generator control, see Section 7.2.4.2, "Basics on
external generator control", on page 378.
● Measurement settings...........................................................................................388
● Interface configuration settings............................................................................. 390
● Source calibration functions.................................................................................. 392
Measurement settings
Access: [INPUT/OUPUT] > "External Generator Config" > "Measurement Configura-
tion" tab
Source State
Activates or deactivates control of an external generator.
Remote command:
SOURce<si>:EXTernal<gen>[:STATe] on page 1172
Source Power
The output power of the external generator. The default output power is -20 dBm. The
range is specified in the specifications document.
Remote command:
SOURce<si>:EXTernal<gen>:POWer[:LEVel] on page 1171
Source Offset
Constant level offset for the external generator. Values from -200 dB to +200 dB in 1
dB steps are allowed. The default setting is 0 dB. Offsets are indicated by the "LVL"
label in the channel bar (see also "Displayed information and errors" on page 386).
Using this offset, attenuators or amplifiers at the output connector of the external gen-
erator can be considered. This is useful, for example, for the displayed output power
values on screen or during data entry. Positive offsets apply to an amplifier, while nega-
tive offsets apply to an attenuator after the external generator.
Remote command:
SOURce<si>:POWer[:LEVel][:IMMediate]:OFFSet on page 1172
message is displayed on the FSW. The values for Result Frequency Start and Result
Frequency Stop are corrected to comply with the range limits.
The value range for the offset depends on the selected generator. The default setting is
0 Hz. Offsets <> 0 Hz are indicated by the "FRQ" label in the channel bar. Negative
offsets can be used to define reverse sweeps.
For more information on coupling frequencies and reverse sweeps, see "Coupling the
frequencies" on page 384. For more information on error messages and the channel
bar, see "Displayed information and errors" on page 386.
Remote command:
SOURce<si>:EXTernal<gen>:FREQuency[:FACTor]:DENominator
on page 1170
SOURce<si>:EXTernal<gen>:FREQuency[:FACTor]:NUMerator on page 1170
SOURce<si>:EXTernal<gen>:FREQuency:OFFSet on page 1171
For more information on configuring interfaces, see Section 12.1, "Remote control
interfaces and protocols", on page 819.
Generator Type........................................................................................................... 391
Interface...................................................................................................................... 391
TTL Handshake...........................................................................................................391
GPIB Address/TCPIP Address / Computer Name...................................................... 391
Reference....................................................................................................................391
Generator Type
Selects the generator type and thus defines the generator setup file to use.
For an overview of supported generators, see the specifications document. For infor-
mation on generator setup files, see "Generator setup files" on page 381.
Remote command:
SYSTem:COMMunicate:RDEVice:GENerator<gen>:TYPE on page 1174
Interface
Type of interface connection used.
For details on which signal generators support which interfaces, see the documenta-
tion of the corresponding signal generator.
● GPIB
● TCP/IP
Remote command:
SYSTem:COMMunicate:RDEVice:GENerator<gen>:INTerface on page 1173
TTL Handshake
If available for the specified generator type, this option activates TTL synchronization
via handshake.
Using the TTL interface allows for considerably higher measurement rates, because
the frequency stepping of the FSW is directly coupled with the frequency stepping of
the generator.
For more information on TTL synchronization, see "TTL synchronization" on page 385.
Remote command:
SYSTem:COMMunicate:RDEVice:GENerator<gen>:LINK on page 1173
Reference
Selects the internal FSW or an external frequency reference to synchronize the FSW
with the generator (default: internal).
Remote command:
SOURce<si>:EXTernal<gen>:ROSCillator[:SOURce] on page 1172
Calibrate Transmission................................................................................................393
Calibrate Reflection Short........................................................................................... 393
Calibrate Reflection Open........................................................................................... 393
Normalization state..................................................................................................... 393
Calibrate Transmission
Starts a transmission type measurement to determine a reference trace. This trace is
used to calculate the difference for the normalized values.
Remote command:
[SENSe:]CORRection:METHod on page 1176
Normalization state
Switches the normalization of measurement results on or off. This function is only
available if the memory contains a reference trace, that is, after a calibration has been
performed.
For details on normalization, see "Normalization" on page 382.
Remote command:
[SENSe:]CORRection[:STATe] on page 1177
Remote command:
[SENSe:]CORRection:RECall on page 1177
Reference Position
Defines the position of the reference line in percent of the total y-axis range.
The top of the diagram is 100%, the bottom is 0%. By default, the 0 dB line is displayed
at the top of the diagram (100%).
This setting is only available if normalization is on (see "Normalization state"
on page 393).
The reference line defined by the reference value and reference position is similar to
the Reference Level defined in the "Amplitude" settings. However, this reference line
only affects the y-axis scaling in the diagram, it has no effect on the expected input
power level or the hardware settings.
The normalized trace (0 dB directly after calibration) is displayed on this reference line,
indicated by a red line in the diagram. If you shift the reference line, the normalized
trace is shifted, as well.
Remote command:
DISPlay[:WINDow<n>][:SUBWindow<w>]:TRACe<t>:Y[:SCALe]:RPOSition
on page 1219
Reference Value
Defines an offset for the position of the reference line.
This setting can be used to shift the reference line and thus the normalized trace, simi-
lar to the Shifting the Display (Offset) defined in the "Amplitude" settings shifts the ref-
erence level in the display.
Shifting the normalized trace is useful, for example, to reflect an attenuation or gain
caused by the measured DUT. If you then zoom into the diagram around the normal-
ized trace, the measured trace still remains fully visible.
Remote command:
DISPlay[:WINDow<n>][:SUBWindow<w>]:TRACe<t>:Y[:SCALe]:RVALue
on page 1175
The following step-by-step instructions demonstrate how to work with the optional
external generator control.
For remote operation, see "Programming example for external generator control"
on page 1178.
1. Connect the signal generator's GPIB interface connector to the "Ext. Gen.Control
GPIB" connector on the rear panel of the FSW.
2. If the signal generator supports TTL synchronization, connect the signal generator
to the optional"Aux.Control" port.
5. Select the type of interface and the address used to connect the generator to the
FSW.
2. In the "Interface Configuration" subtab, select a generator type that has similar
characteristics (frequency and power ranges).
4. Edit the configuration values according to your generator. Be sure not to change
the syntax of the file - only change the values of the parameters.
Errors are only detected and displayed when you try to use the new generator (see
also "Displayed information and errors" on page 386).
5. Save the file under a different name with the extension .gen:
a) In the editor, select "File > SaveAs".
b) Select "Save as type: All Files (*.*)".
c) Specify a name with the extension .gen.
6. In the FSW firmware, close the "External Generator Config" dialog and re-open it.
Now you can select the new generator type from the selection list on the "Interface
Configuration" tab.
1. Connect the signal generator output to the "RF input" connector of the FSW.
2. If the measurement setup does not require the full span of the FSW, change the
"Frequency Start" and "Frequency Stop" values ([FREQ] > "Frequency Config").
8. Optionally, to define a constant level offset for the external generator, define a
"Source Offset".
9. The default frequency list for the calibration sweep contains 1001 values, divided in
equidistant frequencies between the FSW's start and stop frequency. Usually, this
automatic coupling is correct. Check the "Result Frequency Start" and "Result Fre-
quency Stop" values to make sure that the required measurement span is covered.
If necessary, change the frequency settings on the FSW ([FREQ] > "Frequency
Config"), or use a different generator type.
13. Optionally, shift the reference line further down in the result display by decreasing
the "Reference": "Position".
The measurement setup is now calibrated. Subsequent measurement results are
normalized, so that any unwanted effects from the cables and connectors are
removed.
2. After setting "Source Calibration Normalize": "On", select "Save as Trd Factor" to
store the normalized reference trace as a transducer factor.
5. Select the stored transducer in the list of available transducers and select the
"Active" setting for it.
6. Perform any measurement with the setup that contains the calibrated component.
The measurement results do not include the effects from the component.
Prerequisite: a calibration has been performed for the original measurement setup,
except for the component causing an additional gain or attenuation (as described in
"How to calibrate a measurement setup using an external generator" on page 396)
1. Insert the additional component in the calibrated measurement setup and perform
a new measurement.
4. With active normalization, set the "Reference": "Value" to the same value as the
gain or attenuation the inserted component causes.
5. Optionally, shift the reference line further down in the result display by decreasing
the "Reference": "Position".
The normalized reference trace moves to the position of the measured trace.
6. Optionally, zoom into the measured trace by changing the y-axis scaling (or the
range: "AMPT > Scale Config > Range").
The measured trace is still fully visible, and the absolute values are still valid.
The following measurement example demonstrates the most common functions using
an external generator. This example requires the External Generator Control option.
The example assumes an SMW100A generator is connected to the FSW. A band elim-
ination filter is the device under test. After calibration, an additional attenuator is inser-
ted between the DUT and the FSW.
The following procedures are described:
● "Calibrating the measurement setup" on page 398
● "Measuring the effects of the DUT" on page 400
● "Compensating the effects of additional attenuation after calibration" on page 402
2. Connect the signal generator output to the [RF input] connector of the FSW.
3. Adapt the measurement range of the FSW to the filter to be tested. In this mea-
surement, define the following settings:
a) Press [FREQ], select "Frequency Config" and enter "Frequency Start":
100 MHz.
b) Enter "Frequency Stop": 300 MHz
9. Define the generator output level as the "Source Power": -20 dBm.
Figure 7-8: Measurement results from generator, analyzer and connecting cables
13. Select "Source Calibration Normalize": "On" to set the measurement results for the
current setup to 0, thus eliminating all effects from the generator, the analyzer and
the connecting cables from subsequent measurements with the band elimination
filter.
The reference line is displayed at 0 dB at the top of the diagram (100%).
2. Connect the band elimination filter output to the [RF input] connector of the FSW.
3. Shift the reference line from the top of the diagram to the middle of the diagram by
changing the position of the reference point 0.0 dB to 50 %.
In the "Source Calibration" tab, enter "Position": 50 %.
At the same time, the range of the displayed y-axis moves from [-100.0 dB to 0 dB]
to [-50 dB to +50 dB].
Figure 7-13: Reference line with an offset of -3 dB and shifted to middle of diagram (50%)
3. After the reference trace has been shifted, you can zoom into the measured trace
to determine the offsets to the reference line, which represent the effects of the
band elimination filter in the measurement setup.
Change the y-axis scaling to 1 dB/div (or the range to 10 dB).
a) Press [AMPT], then select "Scale Config" > "Range".
b) Enter 10 dB.
Figure 7-14: Reference line with measurement results using larger scale
7.2.5 Probes
Probes allow you to perform voltage measurements very flexibly and precisely on all
sorts of devices to be tested, without interfering with the signal. The FSW base unit
and some (optional) applications support input from probes. For information on which
probes are supported, see the FSW specifications document.
Probe connectors
Probes can be connected to the following connectors on the FSW:
● BASEBAND INPUT connectors, if the optional "Analog Baseband" interface is
installed;
Allows you to perform I/Q analysis or frequency sweeps on data from all active
probes up to a frequency of 5 GHz. The power supply for the probe is integrated in
the connector.
Supported only by applications that can process I/Q data.
● "RF Input" connector using an R&S RT-ZA9 adapter;
Allows you to perform I/Q analysis or frequency sweeps on data from active modu-
lar probes directly on the RF input up to the maximum frequency of the probe and
analyzer. Does not require the optional "Analog Baseband" interface.
Supported by all FSW applications, in particular the Spectrum application.
The R&S RT-ZA9 provides an interface between the probe's BNC socket and the
analyzer's N-socket. The USB connection provides the necessary supply voltages
for the probe.
Active probes
When using active probes from the R&S RT family, consider the following:
● Active probes require operating power from the instrument and have a proprietary
interface to the instrument.
● The probe is automatically recognized by the instrument, no adjustment is
required.
● Connections should be as short as possible to keep the usable bandwidth high.
● Observe the operating voltage range.
Microbutton action
You can define an action to be performed by the FSW when the probe's microbutton (if
available) is pressed. Currently, a single data acquisition via the probe can be per-
formed simply by pressing the microbutton.
To determine whether the probe has been connected properly and recognized by the
FSW, use the [SENSe:]PROBe<pb>:SETup:STATe? remote control command.
Analog baseband input from connected probes can only be analyzed in applications
that support I/Q data processing and the optional "Analog Baseband" interface, such
as the I/Q Analyzer or one of the optional applications.
However, probes can also provide RF input to the FSW via the BASEBAND INPUT I
connector. In this case, the input is redirected to the RF input path. Then the probe
data can also be analyzed in the Spectrum application, allowing you to perform mea-
surements in the time or frequency domain on the input from a probe.
For details see the FSW I/Q Analyzer and I/Q Input User Manual.
As opposed to common RF input processing, a transducer is activated before the com-
mon process to compensate for the additional path of the redirected signal.
Additional information
An application note discussing differential measurements with spectrum analyzers is
available from the Rohde & Schwarz website:
1EF84: Differential measurements with Spectrum Analyzers and Probes
Figure 7-15: Common mode (CM) offset compensation for a differential measurement
If the input signals fit into the operating voltage window of the R&S®RT-ZD10/20/30, it
is not necessary to set a common mode offset compensation.
RF probes
Generally, you can perform frequency sweeps on active probes connected to the
BASEBAND INPUT connectors by redirecting the input to the RF Input path (see "Ana-
log baseband probes" on page 406). However, this measurement setup is restricted to
a maximum frequency of 5 GHz by the BASEBAND INPUT connectors. Furthermore,
this setup is restricted to applications that can process I/Q data.
Connecting probes directly to the RF Input connector allows you to make use of the
maximum frequency range provided by the probe and the FSW, which can be much
higher than 5 GHz.
Furthermore, input from probes at the RF Input connector can be analyzed in all FSW
applications, including applications that do not process I/Q data, and do not support the
optional "Analog Baseband" interface.
Only active modular probes can be connected to the RF Input connector via the
optional R&S RT-ZA9 adapter.
2. Connect the R&S RT-ZA9 adapter's USB cable to a USB connector on the FSW.
4. In the "Input source" settings, select the "Input connector": "RF Probe".
Probes are automatically detected when you plug them into the FSW. The detected
information on the probe is displayed in the "Probes" tab of the "Input" dialog box.
To determine whether the probe has been connected properly and recognized by the
FSW, use the [SENSe:]PROBe<pb>:SETup:STATe? remote control command.
Offset compensation
The R&S RT-ZM probes feature a comprehensive offset compensation function. The
compensation of DC components directly at the probe tip even in front of the active
probe amplifier is possible with an extremely wide compensation range of ±16 V (±24 V
for P and N modes).
The offset compensation feature is available for every MultiMode setting:
CM-Mode Common mode DC volt- ±16 V Measurements of signals with high common
age mode levels, e.g. current measurements
with a shunt resistor.
If the offset for DM-mode or CM-mode is changed, the offsets for the P-mode and N-
mode are adapted accordingly, and vice versa.
For each possible probe connector (Baseband Input I, Baseband Input Q, RF), the
detected type of probe, if any, is displayed.
For more information on using probes with an FSW, see Section 7.2.5.1, "Using
probes", on page 405.
For general information on the R&S®RT probes, see the device manuals.
Name...........................................................................................................................411
Serial Number..............................................................................................................411
Part Number................................................................................................................ 411
Type............................................................................................................................ 412
Mode........................................................................................................................... 412
Common Mode Offset / Diff. Mode Offset / P Offset / N Offset /................................. 412
Attenuation.................................................................................................................. 412
Microbutton Action...................................................................................................... 413
Name
Probe name
Remote command:
[SENSe:]PROBe<pb>:SETup:NAME? on page 1165
Serial Number
Serial number of the probe
Remote command:
[SENSe:]PROBe<pb>:ID:SRNumber? on page 1163
Part Number
Rohde & Schwarz part number
Remote command:
[SENSe:]PROBe<pb>:ID:PARTnumber? on page 1162
Type
Type of probe:
● Single-ended
● Differential
● Active Modular
Remote command:
[SENSe:]PROBe<pb>:SETup:TYPE? on page 1168
Mode
Mode for multi-mode modular probes. Determines which voltage is measured.
"DM-mode" Voltage between the positive and negative input terminal
"CM-mode" Mean voltage between the positive and negative input terminal vs.
ground
"P-mode" Voltage between the positive input terminal and ground
"N-mode" Voltage between the negative input terminal and ground
Remote command:
[SENSe:]PROBe<pb>:SETup:PMODe on page 1166
Attenuation
Defines the attenuation applied to the input at the probe. This setting is only available
for modular probes.
"10:1" Attenuation by 20 dB
"2:1" Attenuation by 6 dB
Remote command:
[SENSe:]PROBe<pb>:SETup:ATTRatio on page 1163
Microbutton Action
Active Rohde & Schwarz probes (except for R&S RT-ZS10E) have a configurable
microbutton on the probe head. By pressing this button, you can perform an action on
the instrument directly from the probe.
Select the action that you want to start from the probe:
"Run Single" Starts one data acquisition.
"No Action" Prevents unwanted actions due to unintended usage of the microbut-
ton.
Remote command:
[SENSe:]PROBe<pb>:SETup:MODE on page 1165
If the FSW External Mixer option is installed, an external mixer can be connected to the
FSW to increase the available frequency range. In this case, the input to measure is
not taken from the RF input connector, but from the "Ext Mixer" connector(s).
For an active external frontend, external mixers are not available. See "External Fron-
tend Connection State" on page 453.
● Basics on external mixers..................................................................................... 413
● External mixer settings..........................................................................................425
● How to work with external mixers..........................................................................436
● Measurement examples: using an external mixer.................................................439
Some background knowledge on basic terms and principles used with external mixers
is provided here for a better understanding of the required configuration settings.
● Frequency ranges................................................................................................. 413
● Two-port and three-port mixers............................................................................. 414
● Bias current........................................................................................................... 415
● Conversion loss tables.......................................................................................... 416
● External mixers and large bandwidth extension options....................................... 418
● Automatic signal identification...............................................................................420
Frequency ranges
In a common spectrum analyzer, rather than providing one large (and thus inaccurate)
filter, or providing several filters to cover the required frequency range of the input sig-
nal (at a high cost), a single, very accurate filter is used. Therefore, the input signal
must be converted to the frequencies covered by the single accurate filter. This is done
by a mixer, which converts and multiplies the frequency of the input signal with the help
of the local oscillator (LO). The result is a higher and lower intermediate frequency (IF).
The local oscillator can be tuned within the supported frequency range of the input sig-
nal.
In order to extend the supported frequency range of the input signal, an external mixer
can be used. In this case, the LO frequency is output to the external mixer, where it is
mixed with the RF input from the original input signal. In addition, the harmonics of the
LO are mixed with the input signal, and converted to new intermediate frequencies.
Thus, a wider range of frequencies can be obtained. The IF from the external mixer is
then returned to the spectrum analyzer.
The frequency of the input signal can be expressed as a function of the LO frequency
and the selected harmonic of the first LO as follows:
fin = n * fLO + fIF
Where:
fin: Frequency of input signal
fIF: Intermediate frequency (variable; defined internally depending on RBW, span and
optional bandwidth extensions)
Thus, depending on the required frequency band, the appropriate order of harmonic
must be selected. For commonly required frequency ranges, predefined bands with the
appropriate harmonic order setting are provided. By default, the lowest harmonic order
is selected that allows conversion of input signals in the whole band.
For the "USER" band, the order of harmonic is defined by the user. The order of har-
monic can be between 2 and 128, the lowest usable frequency being 16.88 GHz.
The frequency ranges for pre-defined bands are described in Table 13-4.
Changes to the band and mixer settings are maintained even after using the [PRESET]
function. A "Preset band" function allows you to restore the original band settings.
Additional ranges
If due to the LO frequency the conversion of the input signal is not possible using one
harmonic, the band must be split. An adjacent, partially overlapping frequency range
can be defined using different harmonics. In this case, the sweep begins using the har-
monic defined for the first range, and at a specified frequency in the overlapping range
("handover frequency"), switches to the harmonic for the second range.
Which harmonics are supported depends on the mixer type.
When using three-port mixers, the LO signal output from the FSW and the IF input
from the mixer are transmitted on separate connectors, whereas for two-port mixers,
both signals are exchanged via the same connector (LO OUT/IF IN). Because of the
diplexer contained in the FSW, the IF signal can be tapped from the line which is used
to feed the LO signal to the mixer.
For measurements with a bandwidth larger than 2 GHz and an external mixer, only 3-
port mixers are supported.
For more information see "External mixers and large bandwidth extension options"
on page 418.
Bias current
Single-diode mixers generally require a DC voltage which is applied via the LO line.
This DC voltage is to be tuned to the minimum conversion loss versus frequency. Such
a DC voltage can be set via the "BIAS" function using the D/A converter of the FSW.
The value to be entered is not the voltage but the short-circuit current. The current is
defined in the "Bias Settings" or set to the value of the conversion loss table.
See "Bias Value" on page 431 and "Bias" on page 435.
The voltage U0 at the output of the operational amplifier can be set in the range –2.0 V
to +2.0 V. An open-circuit voltage Ubias of –0.5 V to +0.5 V is obtained accordingly at
the output of the voltage divider. A short-circuit current of Ishort = U0 / 200 Ω = 10 mA to
+10 mA is obtained for a short circuit at the output of the voltage divider. In order to use
biasing it is not important to know the exact current flowing through the diode since the
conversion loss must be set to a minimum with the frequency. Therefore, it makes no
difference whether the setting is performed by an open-circuit voltage or by a short-cir-
cuit current. A DC return path is ensured via the 66 Ω resistor, which is an advantage
in some mixers.
Predefined conversion loss tables are often provided with the external mixer and can
be imported to the FSW.
Alternatively, you can define your own conversion loss tables. Conversion loss tables
are configured and managed in the "Conversion loss Table Settings" tab of the "Exter-
nal Mixer Configuration" dialog box.
See "Managing conversion loss tables" on page 431 for more information about con-
version loss tables.
When using external mixers with optional bandwidth extensions larger than 512 MHz,
special conversion loss tables are required, see "External mixers and large bandwidth
extension options" on page 418.
Before copying any files to the C:\R_S\INSTR\USER\cvl\ directory, the FSW firm-
ware moves any existing user-defined cvl tables to a backup subdirectory. To use a
user-defined cvl table later, select the file in the C:\R_S\INSTR\USER\cvl\backup
directory.
A validation check is then performed on the selected table to ensure that it complies
with the settings. In particular, the following is checked:
● The assigned band name
● The harmonic order
● The mixer type
● The table must contain at least one frequency that lies within the frequency range
for the band
Reference level
The maximum possible reference level depends on the maximum used conversion loss
value. Thus, the reference level can be adjusted for each range according to the used
conversion loss table or average conversion loss value. If a conversion loss value is
used which exceeds the maximum reference level, the reference level is adjusted to
the maximum value permitted by the firmware.
BW extension option Used meas bandwidth Required conversion loss table format
BW extension option Used meas bandwidth Required conversion loss table format
While the common .acl files can be used, data acquisition with larger bandwidths
using such conversion loss tables leads to substantial inaccuracy. Using an average
conversion loss for the entire range (instead of a conversion loss table) during data
acquisition with the large bandwidth extension options causes even more inaccuracy.
In both cases, the UNCAL status message indicates that the measurement can have
inaccurate results.
Special conversion loss tables (in .b2g or .b5g files) cannot be edited within the FSW
firmware; they can only be imported and deleted.
Example:
For example, for the level measured at the frequency 50 GHz, 43 correction levels are
defined:
● 21 for the frequencies 48.075 GHz, 49.125 GHz, 49.175 GHz, ..., 49.975 GHz
● 1 for the frequency 50 GHz
● 21 for the frequencies 50.025 GHz, 50.075 GHz, 50.125 GHz, ..., 51.025 GHz
B2000-specific conversion loss tables are provided in files according to the following
syntax:
<serial_no.>_MAG_<harmonic>_B2000.b2g
The "Auto ID" function is now also available for Spectrum emission mask (SEM) mea-
surement and Spurious emissions measurement using an external mixer.
Signal ID function
Two sweeps are performed alternately. Trace 1 shows the trace measured on the
upper side band (USB) of the LO (the test sweep), trace 2 shows the trace measured
on the lower side band (LSB), i.e. the reference sweep.
Figure 7-18: Signal identification function (Signal ID) with optional external mixer
Auto ID function
The Auto ID function basically functions like Signal ID function. However, the test and
reference sweeps are converted into a single trace by a comparison of maximum peak
values of each sweep point. The result of this comparison is displayed in trace 3 if "Sig-
nal ID" is active at the same time. If "Signal ID" is not active, the result can be dis-
played in any of the traces 1 to 3. Unwanted mixer products are suppressed in this cal-
culated trace.
Auto ID Auto ID - -
Time-constant spectrum
The automatic comparison of the test sweep and reference sweep with the Auto ID
function can only be applied usefully for signals with a time-constant spectrum since
the two sweeps are always required to determine the actual spectrum.
Figure 7-19: Different mixer products displayed at the same frequency in the test sweep and refer-
ence sweep (large span)
Example:
The external mixer is set to use the 2nd order harmonic. The signal recorded in the test
sweep is displayed by trace 1. The IF filter of the FSW is represented at a 3 dB band-
width of 20 kHz, the real IF bandwidth being 30 kHz. If, however, the 3 dB bandwidth of
the signal recorded in the reference sweep is examined (trace 2), it will be found to be
larger exactly by a factor of 2. This shows that the two products were generated by
mixing with LO harmonics of different orders. The signal recorded in the test sweep
was generated by mixing with the 3rd order harmonic. Since the frequency axis scaling
is based on the 2nd order, the mixer product or the resulting diagram of the IF filter is
compressed by a factor of 2/3. The signal recorded in the reference sweep was gener-
ated by mixing with the fundamental of the LO signal. Since the frequency axis scaling
is based on the 2nd order, the mixer product or the resulting diagram of the IF filter is
expanded by a factor of 2.
Automatic identification with a large span is not possible since the two mixer products
are displayed at the same frequency. The diagram shown in Figure 7-20 is obtained
when examining products with a narrow span using the Auto ID function. You can
easily recognize unwanted mixer products in the diagram obtained using one of the
automatic detection functions.
Mixer settings
Access: [INPUT/OUTPUT] > "External Mixer Config" > "Mixer Settings"
RF Start / RF Stop
Displays the start and stop frequency of the selected band (read-only).
The frequency range for the user-defined band is defined via the harmonics configura-
tion (see "Range 1/Range 2" on page 428).
For details on available frequency ranges, see table 13-4 on page 1151.
Remote command:
[SENSe:]MIXer<x>:FREQuency:STARt on page 1150
[SENSe:]MIXer<x>:FREQuency:STOP on page 1150
Handover Freq
If due to the LO frequency the conversion of the input signal is not possible using one
harmonic, the band must be split. An adjacent, partially overlapping frequency range
can be defined using different harmonics. In this case, the sweep begins using the har-
monic defined for the first range. At the specified "handover frequency" in the overlap-
ping range, it switches to the harmonic for the second range.
The handover frequency can be selected freely within the overlapping frequency
range.
Remote command:
[SENSe:]MIXer<x>:FREQuency:HANDover on page 1150
Band
Defines the waveguide frequency band or user-defined frequency band to be used by
the mixer.
The start and stop frequencies of the selected band are displayed in the "RF Start" and
"RF Stop" fields.
For a definition of the frequency range for the pre-defined bands, see table 13-4 on
page 1151.
The mixer settings for the user-defined band can be selected freely. The frequency
range for the user-defined band is defined via the harmonics configuration (see "Range
1/Range 2" on page 428).
Remote command:
[SENSe:]MIXer<x>:HARMonic:BAND on page 1151
RF Overrange
Sometimes, the harmonics defined for a specific band allow for an even larger fre-
quency range than the band requires. By default, the pre-defined range is used. How-
ever, you can take advantage of the extended frequency range by overriding the
defined "RF Start" and "RF Stop" frequencies by the maximum values.
If "RF Overrange" is enabled, the frequency range is not restricted by the band limits
("RF Start" and "RF Stop"). In this case, the full frequency range that can be reached
using the selected harmonics is used.
Remote command:
[SENSe:]MIXer<x>:RFOVerrange[:STATe] on page 1155
Preset Band
Restores the presettings for the selected band.
Note: changes to the band and mixer settings are maintained even after using the
[PRESET] function. This function allows you to restore the original band settings.
Remote command:
[SENSe:]MIXer<x>:HARMonic:BAND:PRESet on page 1151
IF
Displays the intermediate frequency currently used by the external mixer (for reference
and in the I/Q Analyzer only).
Remote command:
[SENSe:]MIXer<x>:IF? on page 1153
Mixer Type
The External Mixer option supports the following external mixer types:
Note: For measurements with a bandwidth larger than 2 GHz and an external mixer,
only 3-port mixers are supported.
For more information, see "External mixers and large bandwidth extension options"
on page 418.
"2 Port" LO and IF data use the same port
"3 Port" LO and IF data use separate ports
Remote command:
[SENSe:]MIXer<x>:PORTs on page 1155
Remote command:
[SENSe:]MIXer<x>:HARMonic[:LOW] on page 1153
[SENSe:]MIXer<x>:HARMonic:HIGH[:VALue] on page 1152
Basic settings
Access: [INPUT/OUTPUT] > "External Mixer Config" > "Basic Settings"
The basic settings concern general use of an external mixer. They are only available if
the External Mixer (State) is "On".
LO Level......................................................................................................................430
Signal ID......................................................................................................................430
Auto ID........................................................................................................................ 430
Auto ID Threshold....................................................................................................... 431
Bias Value................................................................................................................... 431
└ Write to CVL table.........................................................................................431
LO Level
Defines the LO level of the external mixer's LO port. Possible values are from
13.0 dBm to 17.0 dBm in 0.1 dB steps. Default value is 15.5 dB.
Remote command:
[SENSe:]MIXer<x>:LOPower on page 1148
Signal ID
Activates or deactivates visual signal identification. Two sweeps are performed alter-
nately. Trace 1 shows the trace measured on the upper side band (USB) of the LO (the
test sweep). Trace 2 shows the trace measured on the lower side band (LSB), i.e. the
reference sweep.
Note that automatic signal identification is only available for measurements that per-
form frequency sweeps (not in the VSA or the I/Q Analyzer, for instance).
(See also "Automatic signal identification" on page 420).
Mathematical functions with traces and trace copy cannot be used with the Signal ID
function.
Remote command:
[SENSe:]MIXer<x>:SIGNal on page 1148
Auto ID
Activates or deactivates automatic signal identification.
Auto ID basically functions like Signal ID. However, the test and reference sweeps are
converted into a single trace by a comparison of maximum peak values of each sweep
point. The result of this comparison is displayed in trace 3 if "Signal ID" is active at the
same time. If "Signal ID" is not active, the result can be displayed in any of the traces 1
to 3. Unwanted mixer products are suppressed in this calculated trace.
Note that automatic signal identification is only available for measurements that per-
form frequency sweeps (not in vector signal analysis or the I/Q Analyzer, for instance).
Note: The "Auto ID" function is now also available for Spectrum emission mask (SEM)
measurement and Spurious emissions measurement using an external mixer.
(See also "Automatic signal identification" on page 420).
Remote command:
[SENSe:]MIXer<x>:SIGNal on page 1148
Auto ID Threshold
Defines the maximum permissible level difference between test sweep and reference
sweep to be corrected during automatic comparison ("Auto ID" on page 430 function).
The input range is between 0.1 dB and 100 dB. Values of about 10 dB (i.e. default set-
ting) generally yield satisfactory results.
(See also "Automatic signal identification" on page 420).
Remote command:
[SENSe:]MIXer<x>:THReshold on page 1149
Bias Value
Define the bias current for each range, which is required to set the mixer to its optimum
operating point. It corresponds to the short-circuit current. The bias current can range
from -10 mA to 10 mA. The actual bias current is lower because of the forward voltage
of the mixer diode(s).
Tip: The trace in the currently active result display (if applicable) is adapted to the set-
tings immediately so you can check the results.
To store the bias setting in the currently selected conversion loss table, select Write to
CVL table.
Remote command:
[SENSe:]MIXer<x>:BIAS[:LOW] on page 1148
[SENSe:]MIXer<x>:BIAS:HIGH on page 1147
In this tab, you configure and manage conversion loss tables. Conversion loss tables
consist of value pairs that describe the correction values for conversion loss at certain
frequencies. The correction values for frequencies between the reference points are
obtained via interpolation.
The currently selected table for each range is displayed at the top of the dialog box. All
conversion loss tables found in the instrument's C:\R_S\INSTR\USER\cvl\ direc-
tory are listed in the "Modify Tables" list.
New Table
Opens the "Edit conversion loss table" dialog box to configure a new conversion loss
table.
For details on table configuration, see "Creating and editing conversion loss tables"
on page 433.
Remote command:
[SENSe:]CORRection:CVL:SELect on page 1159
Edit Table
Opens the "Edit conversion loss table" dialog box to edit the selected conversion loss
table.
For details on table configuration, see "Creating and editing conversion loss tables"
on page 433.
Remote command:
[SENSe:]CORRection:CVL:SELect on page 1159
Delete Table
Deletes the currently selected conversion loss table after you confirm the action.
Remote command:
[SENSe:]CORRection:CVL:CLEar on page 1157
Import Table
Imports one or more stored conversion loss tables from any directory and copies them
to the instrument's C:\R_S\INSTR\USER\cvl\ directory. They can then be assigned
for use for a specific frequency range (see "Conversion Loss" on page 429).
Note:
Before copying any files to the C:\R_S\INSTR\USER\cvl\ directory, the FSW firm-
ware moves any existing user-defined cvl tables to a backup subdirectory. To use a
user-defined cvl table later, select the file in the C:\R_S\INSTR\USER\cvl\backup
directory.
Note: If the bandwidth extension options R&S FSW-B6001/-B8001 are active, external
mixers are supported for an analysis bandwidth up to 4 GHz.
Measurements using bandwidth extension options over 512 MHz require special con-
version loss tables, see Table 7-1.
Supported tables have the file extension .b2g or .b5g, as opposed to .acl for com-
mon tables. While .acl files can be used, data acquisition with larger bandwidths
using such conversion loss tables leads to substantial inaccuracy. Using no conversion
loss tables at all during data acquisition with the larger bandwidth options causes even
more inaccuracy.
Note that only common conversion loss tables (in .acl files) can be edited. Special
conversion loss tables (in .b2g or .b5g files) can only be imported and deleted.
For more details, see "External mixers and large bandwidth extension options"
on page 418.
Remote command:
MMEM:COPY '<conversionlosstable>',C:\R_S\INSTR\USER\cvl\
See MMEMory:COPY on page 1354
See FSW base unit user manual.
Note that only common conversion loss tables (in .acl files) can be edited. Special
conversion loss tables (in .b2g or .b5g files) can only be imported and deleted.
For details see "External mixers and large bandwidth extension options" on page 418.
A preview pane displays the current configuration of the conversion loss function as
described by the position/value entries.
File Name....................................................................................................................434
Comment.....................................................................................................................435
Band............................................................................................................................435
Harmonic Order...........................................................................................................435
Bias............................................................................................................................. 435
Mixer Name.................................................................................................................435
Mixer S/N.................................................................................................................... 435
Mixer Type...................................................................................................................436
Position/Value..............................................................................................................436
Insert Value................................................................................................................. 436
Delete Value................................................................................................................436
Shift x.......................................................................................................................... 436
Shift y.......................................................................................................................... 436
Save............................................................................................................................ 436
File Name
Defines the name under which the table is stored in the C:\R_S\INSTR\USER\cvl\
directory on the instrument. The name of the table is identical to the name of the file
(without extension) in which the table is stored. This setting is mandatory. The .ACL
extension is automatically appended during storage.
Remote command:
[SENSe:]CORRection:CVL:SELect on page 1159
Comment
An optional comment that describes the conversion loss table. The comment is user-
definable.
Remote command:
[SENSe:]CORRection:CVL:COMMent on page 1157
Band
The waveguide or user-defined band to which the table applies. This setting is checked
against the current mixer setting before the table can be assigned to the range.
For a definition of the frequency range for the pre-defined bands, see table 13-4 on
page 1151.
Remote command:
[SENSe:]CORRection:CVL:BAND on page 1156
Harmonic Order
The harmonic order of the range to which the table applies. This setting is checked
against the current mixer setting before the table can be assigned to the range.
Remote command:
[SENSe:]CORRection:CVL:HARMonic on page 1158
Bias
The bias current which is required to set the mixer to its optimum operating point. It
corresponds to the short-circuit current. The bias current can range from -10 mA to
10 mA. The actual bias current is lower because of the forward voltage of the mixer
diode(s).
Tip: You can also define the bias interactively while a preview of the trace with the
changed setting is displayed, see "Bias Value" on page 431.
Remote command:
[SENSe:]CORRection:CVL:BIAS on page 1156
Mixer Name
Specifies the name of the external mixer to which the table applies. This setting is
checked against the current mixer setting before the table can be assigned to the
range.
Remote command:
[SENSe:]CORRection:CVL:MIXer on page 1158
Mixer S/N
Specifies the serial number of the external mixer to which the table applies.
The specified number is checked against the currently connected mixer number before
the table can be assigned to the range.
Remote command:
[SENSe:]CORRection:CVL:SNUMber on page 1160
Mixer Type
Specifies whether the external mixer to which the table applies is a two-port or three-
port type. This setting is checked against the current mixer setting before the table can
be assigned to the range.
Remote command:
[SENSe:]CORRection:CVL:PORTs on page 1159
Position/Value
Each position/value pair defines the conversion loss value in dB for a specific fre-
quency. Enter the reference values in order of increasing frequencies. You can define a
maximum of 500 reference values. To enter a new value pair, select an empty space in
the "Position"/"Value" table, or select Insert Value.
Correction values for frequencies between the reference values are interpolated. Lin-
ear interpolation is performed if the table contains only two values. If it contains more
than two reference values, spline interpolation is carried out. Outside the frequency
range covered by the table, the conversion loss is assumed to be the same as for the
first and last reference value.
The current configuration of the conversion loss function as described by the position/
value entries is displayed in the preview pane to the right of the table.
Remote command:
[SENSe:]CORRection:CVL:DATA on page 1158
Insert Value
Inserts a new position/value entry in the table.
If the table is empty, a new entry at 0 Hz is inserted.
If entries already exist, a new entry is inserted above the selected entry. The position of
the new entry is selected such that it divides the span to the previous entry in half.
Delete Value
Deletes the currently selected position/value entry.
Shift x
Shifts all positions in the table by a specific value. The value can be entered in the edit
dialog box. The conversion loss function in the preview pane is shifted along the x-axis.
Shift y
Shifts all conversion loss values by a specific value. The value can be entered in the
edit dialog box. The conversion loss function in the preview pane is shifted along the y-
axis.
Save
The conversion loss table is stored under the specified file name in the
C:\R_S\INSTR\USER\cvl\ directory of the instrument.
The required tasks to work with external mixers are described step-by-step:
For remote operation, see "Programming example: working with an external mixer"
on page 1160.
Use the supplied coaxial cable to feed in the LO signal. If no external mixers are con-
nected to the FSW, cover the two front connectors [LO OUT / IF IN] and [IF IN] with the
SMA caps supplied.
1. Connect the LO OUT / IF IN output of the FSW to the LO port of the external mixer.
2. Connect the IF IN input of the FSW to the IF port of the external mixer.
1. 1. Connect the LO OUT / IF IN output of the FSW to the LO/IF port of the external
mixer. The nominal LO level is 15.5 dBm.
Because of the diplexer contained in the FSW, the IF signal can be tapped from the
line which is used to feed the LO signal to the mixer.
2. Select "Mixer Settings > Band" to define the required frequency range.
4. In the Mixer Settings, select "Conversion Loss: Table" for Range 1 to define fre-
quency-dependent level correction.
5. From the selection list, select a conversion loss table stored on the instrument. No
further settings are necessary since the selected file contains all required parame-
ters. If the selected table is not valid for the selected band, an error message is dis-
played.
If no conversion loss table is available yet, create a new table first (as described in
"To define a new conversion loss table" on page 439).
6. Optionally, select "Basic Settings> Auto ID: On" to activate automatic signal identifi-
cation.
3. Define a file name and, optionally, a comment for the new table.
4. Define the band and mixer settings for which the conversion loss table is to be
used. These settings will be compared to the current mixer settings during the vali-
dation check when the table is imported.
6. Select "Save".
The table is stored and is then available for import and assignment to a specific fre-
quency range.
1. Select "INPUT > Input Source Config > External Mixer > Conversion Loss Table".
4. Select "Shift y" and enter the constant value <a0> to shift all y-values in the table by
this value.
Or:
Select "Shift x" and enter the constant value <a0> to shift all x-values in the table by
this value.
5. Select "Save".
of 52 GHz to 60 GHz using a 2-port mixer for the V band. The mixer used is a double-
diode mixer. The example of operation is described in the following steps:
● "To set up the measurement" on page 440
● "To activate and configure the external mixer" on page 440
● "To take into account the cable loss in the IF path" on page 441
IF IN
LO OUT/IF IN
LO/IF
External
Mixer
RF
Multiplier
RF
INPUT
1. Connect the [LO OUT / IF IN] output of the FSW to the [LO/IF] port of the external
mixer.
3. Apply a sine wave signal with f = 14.5 GHz to the input of the multiplier.
2. Select "Mixer Settings > Band" to define the required frequency range.
4. In the Mixer Settings, select "Conversion Loss: Table" for Range 1 to define fre-
quency-dependent level correction.
5. From the selection list, select a conversion loss table stored on the instrument. No
further settings are necessary since the selected file contains all required parame-
ters. If the selected table is not valid for the selected band, an error message is dis-
played.
If no conversion loss table is available yet, create a new table first (as described in
"To define a new conversion loss table" on page 439).
6. A span is automatically set which covers the whole V band (50 GHz to 75 GHz).
7. Reduce the video bandwidth by selecting "BW > Video Bandwidth Manual": 1
MHz. This allows for correct signal identification using the Auto ID function (see
also "Automatic signal identification" on page 420).
8. Select "Basic Settings> Auto ID: On" to activate automatic signal identification.
9. Adapt the tolerance limit by selecting "Basic Settings> Auto ID Threshold". The tol-
erance limit is set to 5 dB in this example.
2. Increase each reference value in the conversion-loss table by the insertion loss
(a0).
a) Select "INPUT > Input Source Config > External Mixer > Conversion Loss
Table".
b) Select the assigned conversion loss table.
c) Select "Edit Table".
d) Select "Shift y" and enter the insertion loss value <a0> to shift all y-values in the
table by this value.
3. Select "Save".
IF IN
LO OUT/IF IN
LO IF
External
Mixer RF
RF
INPUT
1. Connect the [LO] port of the external mixer to the [LO OUT / IF IN] connector of the
FSW.
2. Connect the [IF] port of the external mixer to the [IF IN] connector of the FSW.
6. If necessary, start an alignment for the measurement setup with the R&S FSW-
B5000.
2. Import the conversion loss table for the RPG FS-Z75 mixer, which is provided with
the device.
a) Select the "Conversion Loss Table" tab.
b) Select "Import Table".
5. Select "Mixer Settings > Band" to define the required frequency range.
7. A span is automatically set which covers the whole V band (50 GHz to 75 GHz).
8. In the "Mixer Settings", select "Conversion Loss: Table" for Range 1 to define fre-
quency-dependent level correction.
If the External Frontend Control option (R&S FSW-K553) is installed, you can control
measurements with the FSW using a connected external frontend.
● External frontend basics........................................................................................443
● External frontend settings..................................................................................... 451
● How to use an external frontend........................................................................... 462
● Troubleshooting external frontend control.............................................................465
Prerequisites
To use an external frontend, the external frontend control option (R&S FSW-K553)
must be installed.
Only measurements that support FFT sweeps or I/Q-based measurements, such as
the I/Q Analyzer application, can process input from an external frontend.
● Test setup..............................................................................................................444
● Multiple connections to a single frontend.............................................................. 445
● Mismatched settings on multiple connected instruments......................................446
● Using external frontends for FFT sweep measurements...................................... 446
● Activation...............................................................................................................447
● Configuration.........................................................................................................448
● External frontend attenuation vs. analyzer attenuation......................................... 448
● External frontends and FSW85 with two input connectors....................................449
● LO signal input and output.................................................................................... 449
● Calibration and alignment..................................................................................... 450
● Diagnostics............................................................................................................450
● Adding external devices to the test setup............................................................. 450
Test setup
Currently, the FSW supports the following external frontend types:
● R&S FE44S
● R&S FE50DTR
● R&S FE110SR
● R&S FE170SR
For details on which FSWs support external frontends, see the instrument's specifica-
tions document.
The external frontend is controlled by the FSW via a LAN connection. Up to 2 LAN/SSL
connections are supported by the frontend. The data is transferred using an IF cable.
In addition, a reference signal is provided from the FSW to the frontend.
RF shield box
RF IF Out RF
DUT
Signal Analyzer REF Ref Frontend
LAN FE control
For details on setting up the external frontend, see the documentation of the used
device.
RF
Figure 7-24: Typical setup for multiple instruments connected to one external frontend
When using R&S FE170SR and R&S FE110SR type frontends, make sure you insert
the correct waveguide filter for the frequency range you intend to measure. See "Add-
ing external devices to the test setup" on page 450 and the specifications document for
details. Particularly when performing FFT sweeps with these external frontends, fre-
quencies outside the filter range can cause mixer products that produce unexpected
signals.
Spectrum measurements that use FFT sweeps also support external frontends.
Activation
Activation is a two-step process. First, global activation allows for the general use of an
external frontend for the application. The application adapts the available measure-
ment settings to the connected frontend, for example the available frequency range,
reference level and attenuation.
If a measurement is active that does not support an FFT sweep, the basic frequency
sweep measurement is automatically selected. For all frequency sweep measure-
ments, the "Sweep type" is set to "FFT".
If a measurement is active that does not support external frontends when you activate
the frontend, the basic zero span measurement is automatically selected.
If no frontend is configured yet, the configuration settings become available. The chan-
nel bar indicates "Inp: ExtFe".
In a second step, the configured frontend is connected. Due to the two-step process,
the frontend can be deactivated temporarily for use by another connected instrument,
for example if the frontend has two signal paths. The measurement settings on the
FSW remain untouched.
If global activation is stopped, the application adapts the measurement settings to the
common settings supported by the FSW.
If an external frontend is configured in the active channel and you start a new applica-
tion that supports its use, the external frontend settings are automatically copied. How-
ever, you can deactivate the frontend or change the settings for individual applications.
Only one application can use the frontend at the same time.
Configuration
You can configure external frontends individually for each measurement application.
The settings are preserved after presetting the instrument, and are included in save-
sets. The frontend is controlled and configured by the FSW using the common mea-
surement settings.
There are some minor differences in the measurement settings if an external frontend
is active:
● The available frequency range, reference level and attenuation are adapted to the
values supported by the configured frontend.
● Amplitude settings refer to the RF input at the external frontend, not the levels at
the RF input of the FSW (which is the downconverted IF data from the frontend).
However, you can also configure attenuation for the analyzer, see "External fron-
tend attenuation vs. analyzer attenuation" on page 448.
● Only mechanical attenuation is available.
Electronic attenuation, preamplifier, and noise cancellation are not available.
● Auto settings are not available for active external frontends.
● Input coupling is always AC.
● Impedance is always 50 Ω.
● Only external triggers, I/Q power triggers, and (periodic) time triggers are suppor-
ted as trigger sources.
For spectrum measurements, only external triggers and video triggers are suppor-
ted.
● Depending on the bandwidth extension options available on the FSW, the maxi-
mum I/Q bandwidth is 1 GHz.
● If global activation of the external frontend is on, but the connection state of the
configured frontend is off, the FSW application is temporarily "on hold". It is set up
for and awaiting input from the external frontend, but the connection is aborted.
Thus, further measurement configuration is not possible until the frontend is recon-
nected, or global activation is stopped.
● The hardware of the FSW is adjusted to the defined reference level for the RF
input at the external frontend. It is adjusted optimally for input signals with a crest
factor of 10 dB. Thus, the required reference level for an optimal measurement can
differ depending on the crest factor of the input signal.
● Input from external frontends cannot be used simultaneously with:
– External generator control
– I/Q file input
– External mixers
– Analog baseband input
Defining attenuation at the analyzer can avoid frequent switching at the mechanical
attenuator when you switch between applications with different input settings.
Note, however, that in "Auto" mode, the FSW determines the required attenuation at
the external frontend for an optimal EVM automatically. If you adapt the attenuation at
the frontend and the analyzer manually, the EVM can decrease.
LO OUT LO IN
Signal Generator DUT Signal Analyzer
Ext. FE1 Ext. FE2
Coupling multiple devices by their used LO signals is useful, for example, in setups
with multiple input streams to reduce the phase noise.
To use the same LO signal on coupled external frontends, both devices have to
use the same LO frequency for upconversion and downconversion. For coupled
frontends of the same type, make sure to select the same frequency band configu-
ration for all frontends. (See "Frequency Band Configuration" on page 454.)
You can also couple an R&S FE170SR and an R&S FE170ST, or an
R&S FE110SR and an R&S FE110ST. However, since they are different types of
frontend, they can use different LO signals for the same frequency band setting. In
this case, use the "Shared LO" setting, which ensures that both devices use the
same LO frequency according to a frequency plan.
LO input and output is not available for FFT sweep measurements. In this case, the
external frontend always uses its internal LO.
Diagnostics
The FSW allows you to obtain information on the performance of the connected fron-
tend and to perform a self-test on the frontend. The results can be stored as an XML
log file.
When using R&S FE170SR and R&S FE110SR type frontends, make sure you insert
the correct waveguide filter for the frequency range you intend to measure. See the
specifications document for details.
Test setup
Figure 7-26 illustrates a test setup with an external frontend connected to a FSW and
an antenna, which is mounted inside an RF shield box. An additional band filter is
inserted between the DUT and the external frontend.
RF shield box
RF In IF Out RF In RF out in RF
Ref R&S Band- DUT
Signal Analyzer REF
FE110SR filter
LAN IX IX
LAN
IX
Access: "Overview" > "Input" > "Input Source Config" > "Input Source" > "External
Frontend"
The following settings are only available if the external frontend control option
(R&S FSW-K553) is installed on the FSW.
They are only available for measurements that support FFT sweeps or I/Q-based mea-
surements, such as in the I/Q Analyzer application.
For details see the FSW user manual.
● Global configuration settings.................................................................................452
● Frontend configuration settings.............................................................................453
● Diagnostics............................................................................................................457
● Network configuration........................................................................................... 458
● External Devices................................................................................................... 460
Global activation..........................................................................................................452
External Frontend Connection State........................................................................... 453
Frontend Type............................................................................................................. 453
IP Address/ Computer Name...................................................................................... 453
FW Update.................................................................................................................. 453
Global activation
If enabled, the FSW allows you to configure and connect an external frontend. The
application adapts the available measurement settings to the connected frontend, for
example the available frequency range, reference level and attenuation.
If a measurement is active that does not support an FFT sweep, the basic frequency
sweep measurement is automatically selected. For all measurements, the "Sweep
type" is set to "FFT".
If no frontend is configured yet, the configuration settings become available. The chan-
nel bar indicates "Inp: ExtFe".
If disabled, the frontend is disconnected. The application adapts the measurement set-
tings to the common settings supported by the FSW.
Remote command:
[SENSe:]EFRontend[:STATe] on page 1127
Frontend Type
Defines the type of frontend to be connected.
Currently, the FSW supports the following external frontend types:
● R&S FE44S
● R&S FE50DTR
● R&S FE110SR
● R&S FE170SR
Remote command:
[SENSe:]EFRontend:CONNection:CONFig on page 1119
FW Update
When the FSW establishes a connection to the frontend, it checks the firmware version
of the frontend. If the FSW does not support the firmware installed on the frontend, you
are asked to update the frontend firmware. You can either start the firmware update
immediately, or abort the connection process and update the firmware on the frontend
later. In this case, the frontend is not available for use with the FSW until you perform
the update.
Remote command:
[SENSe:]EFRontend:FWUPdate on page 1129
The used Intermediate Frequency and the resulting Frequency Band sideband that can
be analyzed on the FSW are indicated for reference.
The selected frequency band configuration is also indicated in the channel bar.
R&S FE50DTR-type frontends can be used by an analyzer and a signal generator
simultaneously. In this case, both channels use the same internal LO and thus both
signal paths operate on the same frequency. Therefore, if you want to analyze the sig-
nal from the generator using the same frontend, make sure that the configured fre-
quency bands are identical on both instruments.
You can select the required IF output range manually, or it can be determined automat-
ically, according to the other frequency settings.
Currently, auto mode always applies the "IF Low" range for R&S FE44S and
R&S FE50DTR-type frontends. For R&S FE170SR and R&S FE110SR frontends, the
"Spur Optimized" range is used.
In manual mode, select one of the following IF output ranges:
"IF High" (R&S FE44S/ R&S FE50DTR)
A higher intermediate frequency is used on the external frontend,
resulting in a higher input frequency at the FSW.
"IF Low" (R&S FE44S/ R&S FE50DTR)
A lower intermediate frequency is used on the external frontend,
resulting in a lower input frequency at the FSW.
"Spur Optimized"
(R&S FE170SR/R&S FE110SR only)
The selected IF range avoids unwanted spurious effects.
"EVM Optimized"
(R&S FE170SR only)
The selected IF range provides an optimal EVM result.
"Shared LO" (R&S FE170SR/R&S FE110SR only)
Ensures that multiple external frontends of a different type
(R&S FE170SR/ R&S FE170ST or R&S FE110SR/R&S FE110ST)
use the same LO frequencies for upconversion and downconversion.
Remote command:
[SENSe:]EFRontend:FREQuency:BCONfig:AUTO on page 1121
[SENSe:]EFRontend:FREQuency:BCONfig:LIST? on page 1122
[SENSe:]EFRontend:FREQuency:BCONfig:SELect on page 1122
Frequency Band
Displays the range of the frequency band supported by the connected frontend (for ref-
erence only).
Remote command:
[SENSe:]EFRontend:FREQuency:BAND:COUNt? on page 1120
[SENSe:]EFRontend:FREQuency:BAND<b>:LOWer? on page 1120
[SENSe:]EFRontend:FREQuency:BAND<b>:UPPer? on page 1121
Reference Frequency
Sets the reference frequency that is used for frequency conversion on the frontend.
Depending on the connected type of frontend, different values are available.
Remote command:
[SENSe:]EFRontend:FREQuency:REFerence on page 1126
[SENSe:]EFRontend:FREQuency:REFerence:LIST? on page 1126
Intermediate Frequency
Indicates the currently used intermediate frequency (IF) and sideband (upper/lower) for
frequency conversion (for reference only).
This value depends on the "Frequency Band Configuration" on page 454.
For FFT sweep measurements, the LO is adapted during the measurement to cover
the entire sweep range. The resulting IF range is indicated.
For FE50DTR-type frontends that are used by an analyzer and a signal generator
simultaneously, make sure that the used intermediate frequency is identical on both
instruments.
Make sure the IF frequency required by the external frontend lies within the IF fre-
quency range of the FSW.
"USB" Upper sideband
"LSB" Lower sideband
Remote command:
For I/Q measurements:
[SENSe:]EFRontend:FREQuency:IFRequency[:VALue]? on page 1124
[SENSe:]EFRontend:FREQuency:IFRequency:SIDeband? on page 1123
For FFT sweep measurements:
[SENSe:]EFRontend:FREQuency:IFRequency:MAXimum? on page 1123
[SENSe:]EFRontend:FREQuency:IFRequency:MINimum? on page 1123
LO Mode
Determines whether the external frontend uses its internal LO or an external LO.
The LO configuration settings are not available for FFT sweep measurements. The
external frontend always uses its internal LO.
See also "LO signal input and output" on page 449.
For details, see the FSW base unit user manual.
"External" Uses the external signal provided at the "LO Input" connector of the
external frontend. The frequency at which the LO must be input to the
external frontend is indicated as "Mandatory LO IN Frequency"
on page 457.
If enabled, "LO EXT" is displayed in the channel bar.
"Internal" Uses the internal LO
Remote command:
[SENSe:]EFRontend:FREQuency:LOSCillator:MODE on page 1124
LO Out State
Enables or disables output of the LO at the "LO OUT" connector of the external fron-
tend. Which LO is provided depends on LO Mode. The frequency at which the LO is
provided to the connector is indicated as LO OUT Frequency.
Remote command:
[SENSe:]EFRontend:FREQuency:LOSCillator:OUTPut:STATe on page 1125
Mandatory LO IN Frequency
Indicates the required frequency of the LO input at the external frontend when using an
external LO. If the coupled device does not provide the external LO at this frequency,
the results of the external frontend are inaccurate.
Remote command:
[SENSe:]EFRontend:FREQuency:LOSCillator:INPut:FREQuency?
on page 1124
LO OUT Frequency
Indicates the frequency of the LO output, if LO Out State is "ON".
Remote command:
[SENSe:]EFRontend:FREQuency:LOSCillator:OUTPut:FREQuency?
on page 1125
Correction State
Activates correction of the IF signal due to cable loss from the frontend to the analyzer.
Remote command:
[SENSe:]EFRontend:ALIGnment<ch>:STATe on page 1128
Diagnostics
Access: "Overview" > "Input" > "Input Source Config" > "Input Source" > "External
Frontend" > "Diagnostics"
The "Diagnostics" tab provides information on the performance of the connected fron-
tend and allows you to perform a self-test on the frontend.
Start Selftest................................................................................................................458
Abort Selftest...............................................................................................................458
Selftest Results........................................................................................................... 458
Start Selftest
Performs a self-test on the frontend to compare the current performance and charac-
teristic values with the specified values for the frontend.
Remote command:
[SENSe:]EFRontend<fe>:SELFtest? on page 1129
Abort Selftest
Aborts a running self-test.
Remote command:
not supported
Selftest Results
Indicates the results of a selftest performed on the connected frontend.
Remote command:
[SENSe:]EFRontend<fe>:SELFtest:RESult? on page 1129
Network configuration
Access: "Overview" > "Input" > "Input Source Config" > "Input Source" > "External
Frontend" > "Network Config"
After connection, you can assign a static IP address or switch to a dynamic IP address
for the external frontend directly from the FSW.
IP Address...................................................................................................................459
Subnet Mask............................................................................................................... 459
DHCP.......................................................................................................................... 459
Apply Network Settings............................................................................................... 459
IP Address
Defines the IP address of the external frontend. If the DHCP server is used ("DHCP
On"), the setting is read-only.
Remote command:
[SENSe:]EFRontend:NETWork on page 1126
Subnet Mask
Defines the subnet mask of the external frontend. If the DHCP server is used ("DHCP
On"), this setting is read-only.
Remote command:
[SENSe:]EFRontend:NETWork on page 1126
DHCP
Switches between DHCP server available (""On) or not available ("Off"). If a DHCP
server is available in the network, the IP address and subnet mask of the external fron-
tend are obtained automatically from the DHCP server.
Remote command:
[SENSe:]EFRontend:NETWork on page 1126
Beware that if you change the network information, the connection is aborted and you
must re-establish a connection to the frontend (see "External Frontend Connection
State" on page 453).
Remote command:
[SENSe:]EFRontend:NETWork on page 1126
External Devices
Access: "Overview" > "Input" > "Input Source Config" > "Input Source" > "External
Frontend" > "External Devices"
You can insert additional external devices in the signal path between the DUT and the
external frontend, such as preamplifiers or filters. The external frontend must then con-
sider the additional gain or correction values.
When the FSW initially connects to the external frontend, the instrument automatically
detects any devices connected to the external frontend. The FSW displays information
on detected devices in the "External Devices" tab of the dialog.
Name...........................................................................................................................460
Type............................................................................................................................ 461
Frequency Range........................................................................................................461
Gain.............................................................................................................................461
Refresh External Devices............................................................................................461
Correction State.......................................................................................................... 461
Load S2P File..............................................................................................................461
Name
Name of the external device for reference.
Remote command:
[SENSe:]EFRontend[:CHANnel<ch>]:EXTDevice<di>:NAME? on page 1133
[SENSe:]EFRontend[:CHANnel<ch>]:EXTDevice<di>:LIST? on page 1131
Type
Type of the detected device for reference.
Currently, the following device types are supported:
● Filter
● Amplifier (R&S FE170SR only)
Remote command:
[SENSe:]EFRontend[:CHANnel<ch>]:EXTDevice<di>:TYPE? on page 1134
Frequency Range
The supported frequency range of the connected device.
Remote command:
[SENSe:]EFRontend[:CHANnel<ch>]:EXTDevice<di>:FREQuency:MINimum?
on page 1133
[SENSe:]EFRontend[:CHANnel<ch>]:EXTDevice<di>:FREQuency:MAXimum?
on page 1132
Gain
For connected external amplifiers only: provided gain.
Remote command:
[SENSe:]EFRontend[:CHANnel<ch>]:EXTDevice<di>:GAIN? on page 1133
Correction State
Enables or disables the use of an additional correction file for the connected external
devices. Additional correction is useful, for example, if you do not use the IX cable to
connect the external device to the external frontend. In this case, automatic compensa-
tion cannot be applied.
See also "Correcting the signal path" on page 451.
Remote command:
[SENSe:]EFRontend[:CHANnel<ch>]:EXTDevice<di>:CORRection:STATe
on page 1130
Remote command:
[SENSe:]EFRontend[:CHANnel<ch>]:EXTDevice<di>:CORRection:FILE
on page 1130
[SENSe:]EFRontend[:CHANnel<ch>]:EXTDevice<di>:CORRection:VALid?
on page 1131
3. Select [Input / Output] > "Input Source Config" > "Input Source" > "External Fron-
tend".
4. On the "Global Config" tab, enable general use of the external frontend for the
application ("On").
The connection settings become available.
6. Enter the IP address or computer name of the connected frontend. The information
is indicated on the electronic label on the side panel of the frontend.
After you enter the IP address, the "Connection State" setting becomes available.
It can take up to 10 seconds until the FSW sets up the control connection to the
frontend. The displayed status of the control connection in the dialog box switches
from "Not Connected" (white) to "Connected" (green). The LAN LED on the front
panel of the frontend switches from green to orange.
The frequency band supported by the connected frontend is displayed on the
"Frontend Config" tab.
10. Optionally, enable compensation for the frequency response of the IF cable from
the FSW to the frontend.
a) Select "Load Cable Correction S2P File".
b) Select an .s2p file that contains the frequency response for the used IF cable.
To provide valid results, the frequency response file must provide the S21
parameter for the used frequency range of the external frontend.
Frequency response files are usually provided with the IF cable. The calibration
data for the IF cable provided with the FSW is installed on the instrument at the
factory.
The .s2p files are stored on the instrument under
C:\R_S\INSTR\USER\external_frontends\<frontend_type>\
touchstonefiles\. For example, the files for the IF cable are stored under
C:\R_S\Instr\user\external_frontends\FE44S\
touchstonefiles\if_default_cable_1347_7552_00.s2p.
c) Set the "Correction State" to "On" to enable the use of the correction file.
The FSW automatically adapts the measured values from the external frontend to
the known cable loss.
12. Optionally, if you need to change the network settings, proceed as follows:
a) Disable DHCP ("DHCP" > "Off").
b) Adjust the network settings according to your test setup.
c) Click "Apply Network Settings".
Note: If you change the network configuration to "DHCP" > "On", the connection to
the FSW is aborted. You must re-establish a connection to the frontend as descri-
bed in step step 4).
If you have connection issues, see .
13. Configure the measurement as usual. The amplitude and frequency settings are
adapted to the supported values of the external frontend. The reference value
refers to the RF input of the external frontend.
2. Connect the external frontend to the FSW as described in the frontend manual.
3. Configure the external frontend as described in "To configure the use of an external
frontend" on page 462.
4. Select [Input / Output] > "Input Source Config" > "Input Source" > "External Fron-
tend" > "External Devices".
5. If the external frontend was already connected to the analyzer when you connected
the external device, select "Refresh External Devices" to update the information.
6. Optionally, if you do not connect the external device to the frontend using the IX
cable, enable additional compensation for the external device.
a) Select "Load S2P File".
b) Select an .s2p file that contains the frequency response for the used devices
and cables.
To provide valid results, the frequency response file must provide the S21
parameter for the used frequency range of the external devices.
The dialog indicates whether the selected file is valid or not.
c) Set the "Correction State" to "On" to enable the use of the correction file.
The external frontend automatically adapts the signal values from the external
devices to the known loss.
If problems arise during external frontend control, try the following measures to opti-
mize the connection or setup.
For additional information, see the external frontend documentation.
Error messages
If errors occur, status messages in the external frontend configuration dialog box and in
the status bar of the display inform you about them.
Query the error message queue using the remote command SYST:ERR? to determine
if any or which errors occurred during operation. For details, see Section 14.2, "Error
messages in remote control mode", on page 1550.
If any errors occur that are not described here, contact the Rohde & Schwarz customer
support, see Section 14.7, "Contacting customer support", on page 1558.
Table 7-2: Status and error messages
Status bar message Dialog status SYST:ERR? result Description/ Possible solution
External Frontend [x]: Connecting... Connection to the external frontend is being estab-
Connecting... lished.
It can take up to 10 seconds to determine that LAN
connection failed.
External Frontend [x]: Invalid Host IP 300, "Invalid Host Verify the specified IP address of the external fron-
Invalid Host IP IP" tend.
External Frontend [x]: Not connected 301, "LAN Connection Verify that the external frontend is connected to the
LAN Connection Failed Failed" same network as the FSW.
Verify the specified IP address of the external fron-
tend.
External Frontend [x]: Incompatible Ana- 302, "Incompatible The frontend hardware is not compatible with the
Incompatible Analyzer lyzer Firmware Analyzer Firmware" installed analyzer firmware.
Firmware Update your analyzer firmware.
See Section 11.7.4, "Firmware updates",
on page 792.
External Frontend [x]: Incompatible Fron- 303, "Incompatible The firmware of the external frontend is not up-to-
Incompatible Frontend tend Firmware Frontend Firmware" date.
Firmware Perform a firmware update.
See "FW Update" on page 453.
External Frontend [x]: Device Locked 304, "Device Locked" External frontend is accessible via ping, but no
Device Locked SSL-connection could be established.
Disconnect another device that is currently access-
ing the external frontend and try reconnecting.
A single frontend supports up to 2 LAN/SSL con-
nections.
External Frontend [x]: Wrong Device Type 306, "Wrong Device The connected external frontend is not of the
Wrong Device Type Type" specified type.
Disconnect the device, select the correct external
frontend type in the configuration dialog box, and
reconnect.
External Frontend [x]: LAN Connection Lost 314, "LAN Connection The connection to the external frontend has been
LAN Connection Lost Lost" lost.
The analyzer attempts to reconnect periodically.
Wait for the "Connecting…" message.
External Frontend [x]: Firmware Update 315, "Firmware The firmware of the external frontend was not
Firmware Update Failed Failed Update Failed" updated successfully.
Status bar message Dialog status SYST:ERR? result Description/ Possible solution
External Frontend [x]: Connected 316, "External The FSW does not support any IF frequencies
<Frontend_Name> is Frontend Not required by the external frontend.
not allowed, RF input Allowed"
frequency of at least
<Max_RF> GHz is
required.
External Frontend [x]: Connected 317, “RF frequency The selected measurement (RF) frequency is not
Current RF frequency is is out of valid supported by the selected frequency band of the
out of valid range. range.” external frontend. Select a different frequency on
Please check Frontend the FSW, or a different frequency band for the fron-
Config dialog for more tend.
information
External Frontend [x]: Connected 332, "Settings The conversion settings on the external frontend
Settings Mismatch - Mismatch" were changed by another instrument during the
reinitiate frontend by measurement on the FSW. The measurement
changing a measure- results no longer match the original measurement
ment parameter settings. To restore the original measurement set-
tings on the frontend, change a frontend setting in
the FSW dialog.
External Frontend [x]: Device busy 333, "Device Busy" The external frontend is currently blocked by
Not Connected – Device another instrument, e.g. for initial connection or a
Busy firmware update. After the other instrument finishes
its task, try reconnecting the FSW. (Switch the
"Connection" state off and on again.)
External Frontend [x]: Connected 333, "Device Busy" During a running measurement, the external fron-
Device Busy tend is blocked by another instrument, e.g. for ini-
tial connection or a firmware update. The current
measurement is aborted. After the other instrument
finishes its task, start a new measurement on the
FSW.
External Frontend [x]: 350, "Touchstone The .s2p file does not cover the used frequency.
Touchstone file insuffi- file frequency range
Correct the file or select a different correction file.
cient frequency range insufficient"
"<filename>.s2p has -150, "String data The .s2p file does not have the correct syntax.
wrong file format" error"
Correct the file.
(Result for [SENSe:
]EFRontend:
ALIGnment<ch>:FILE
on page 1128)
-256, "File name not The specified .s2p file does not exist.
found"
Correct the path and filename and make sure that
(Result for [SENSe: the file is stored on the instrument under
]EFRontend: C:\R_S\INSTR\USER\external_frontends\
ALIGnment<ch>:FILE <frontend_type>\touchstonefiles.
on page 1128)
Problem: The analyzer does not show the signal sent by a signal generator using
the same external frontend
Possible Solution: Although the generator and the analyzer are set to the same fre-
quency, possibly they are not using the same IF for conversion.
Make sure that both instruments are set to the same Frequency Band Configuration in
the Frontend configuration settings.
Problem: My FSW85 does not show the signal measured with an external fron-
tend
Possible Solution:
Select the other RF Input connector in the Radio frequency input (see "Radio Fre-
quency State" on page 365). The external frontend settings apply to both RF input con-
nectors on the FSW85, so you must select the connector you use.
Data Output.................................................................................................................469
Noise Source Control.................................................................................................. 470
Data Output
Defines the type of signal available at one of the output connectors of the FSW.
For restrictions and additional information, see Section 7.2.1.2, "IF and video signal
output", on page 362.
"IF" The measured IF value is provided at the IF/VIDEO/DEMOD output
connector.
For bandwidths up to 80 MHZ, the IF output is provided at the speci-
fied "IF Out Frequency".
If an optional bandwidth extension FSW-B160/-B320/-B512 is used,
the measured IF value is available at the "IF WIDE OUTPUT" con-
nector. The frequency at which this value is output is determined
automatically. It is displayed as the "IF Wide Out Frequency". For
details on the used frequencies, see the specifications document.
This setting is not available for bandwidths larger than 512 MHz.
"2ND IF" The measured IF value is provided at the "IF OUT 2 GHz/ IF OUT
5 GHz" output connector, if available, at a frequency of 2 GHz and
with a bandwidth of 2 GHz. The availability of this connector depends
on the instrument model.
This setting is not available if the optional 2 GHz / 5 GHz bandwidth
extension (FSW-B2000/B5000) is active.
"Video" The displayed video signal (i.e. the filtered and detected IF signal) is
available at the IF/VIDEO/DEMOD output connector. This setting is
required to provide demodulated audio frequencies at the output. It is
not available for frequency sweeps or I/Q measurements.
Remote command:
OUTPut:IF[:SOURce] on page 1191
OUTPut:IF:IFFRequency on page 1192
SYSTem:SPEaker:VOLume on page 1193
Trigger 2/3
The trigger input and output functionality depends on how the variable "Trigger Input/
Output" connectors are used.
"Trigger 1" "Trigger 1" is input only.
"Trigger 2" Defines the usage of the variable "Trigger Input/Output" connector on
the front panel
(not available for FSW85 models with 2 RF input connectors)
"Trigger 3" Defines the usage of the variable "Trigger 3 Input/Output" connector
on the rear panel
"Input" The signal at the connector is used as an external trigger source by
the FSW. Trigger input parameters are available in the "Trigger" dia-
log box.
"Output" The FSW sends a trigger signal to the output connector to be used by
connected devices.
Further trigger parameters are available for the connector.
Remote command:
OUTPut:TRIGger<tp>:DIRection on page 1233
Remote command:
OUTPut:TRIGger<tp>:LEVel on page 1234
Using the variable Trigger 2/3 connector of the FSW, the internal trigger signal can be
output for use by other connected devices.
For details on the connectors see the FSW "Getting Started" manual.
5. For manual output: Specify the constant signal level and the length of the trigger
pulse to be output. Note that the level of the trigger pulse is opposite to the con-
stant output "Level" setting (compare the graphic on "Send Trigger").
6. Connect a device that will receive the trigger signal to the configured Trigger 2/3
connector.
7. Start a measurement and wait for an internal trigger, or select "Send Trigger".
The configured trigger is output to the connector.
Some background knowledge on the impact of the described settings is provided here
for a better understanding of the required configuration.
● Defining the scope of the measurement - frequency range.................................. 473
● Stepping through the frequency range - center frequency stepsize..................... 473
● Coping with large frequency ranges - logarithmic scaling.....................................474
The frequency range defines the scope of the signal and spectrum to be analyzed. It
can either be defined as a span around a center frequency, or as a range from a start
to a stop frequency. Furthermore, the full span comprising the entire possible fre-
quency range can be selected, or a zero span. The full span option allows you to per-
form an overview measurement over the entire span. Using the "Last Span" function
you can easily switch back to the detailed measurement of a specific frequency range.
For sinusoidal signals, the center frequency can be defined automatically by the FSW
as the highest frequency level in the frequency span (see "Adjusting the Center Fre-
quency Automatically (Auto Frequency)" on page 533).
Using the arrow keys you can move the center frequency in discrete steps through the
available frequency range. The step size by which the center frequency is increased or
decreased is defined by the "Center Frequency Stepsize".
The "Center Frequency Stepsize" also defines the step size by which the value is
increased or decreased when you use the rotary knob to change the center frequency;
however, the rotary knob moves in steps of only 1/10 of the "Center Frequency
Stepsize" to allow for a more precise setting.
By default, the step size is set in relation to the selected span or resolution bandwidth
(for zero span measurements). In some cases, however, it may be useful to set the
step size to other values.
For example, to analyze signal harmonics, you can define the step size to be equal to
the center frequency. In this case, each stroke of the arrow key selects the center fre-
quency of another harmonic. Similarly, you can define the step size to be equal to the
current marker frequency.
In a linear display, the frequencies are distributed linearly across the x-axis. That
means the entire frequency range is divided by the number of sweep points, and the
distance between sweep points is equal. Linear scaling is useful to determine precise
frequencies within a small range.
1 MHz 10 MHz
Figure 7-27: Linear x-axis scaling: the distance between the sweep points is equal, e.g. 200 kHz
However, if high and low frequencies appear in the same display, it is difficult to deter-
mine individual frequencies precisely or to distinguish frequencies that are close
together.
In a logarithmic display, lower frequencies are distributed among a much larger area of
the display, while high frequencies are condensed to a smaller area. Now it is much
easier to distinguish several lower frequencies, as they are spread over a wider area.
Logarithmic scaling is useful for overview measurements when a large frequency
range must be displayed in one diagram.
Note that logarithmic scaling is only available if R&S FSW-K54 is installed.
However, with logarithmic scaling, the frequency resolution between two sweep points
deteriorates with higher frequencies.
1 Hz 1 MHz 1 GHz
Figure 7-28: Logarithmic x-axis scaling: the distance between sweep points is variable
In the spectrum from 10 Hz to 100 Hz, the distance is a few Hz. Between 100 MHz and
1 GHz, the distance is several MHz.
Thus, for logarithmic x-axis scaling, the number of sweep points must be sufficiently
high in order to distinguish high frequencies precisely. The resolution bandwidth should
cover at least one sweep point (that means: the distance between two sweep points
should not exceed the RBW). If this condition is not met, signals or interferers could be
missed, especially narrowband interferers.
Insufficient measurement points - Resolution filter bandwidth Resolution filter bandwidth covers
Filter may miss a signal covers one measurement point several measurement points
Center Frequency
Defines the center frequency of the signal in Hertz.
The allowed range of values for the center frequency depends on the frequency span.
span > 0: spanmin/2 ≤ fcenter ≤ fmax – spanmin/2
zero span: 0 Hz ≤ fcenter ≤ fmax
fmax and spanmin depend on the instrument and are specified in the specifications docu-
ment.
Remote command:
[SENSe:]FREQuency:CENTer on page 1195
Span
Defines the frequency span. The center frequency is kept constant. The following
range is allowed:
span = 0: 0 Hz
span >0:
spanmin ≤ f span ≤ f max
fmax and spanmin are specified in the specifications document.
For more information, see Section 7.3.1.1, "Defining the scope of the measurement -
frequency range", on page 473.
Remote command:
[SENSe:]FREQuency:SPAN on page 1198
Start / Stop
Defines the start and stop frequencies.
The following range of values is allowed:
fmin ≤ fstart ≤ fmax – spanmin
fmin + spanmin ≤ fstop ≤ fmax
fmin, fmax and spanmin are specified in the specifications document.
Remote command:
[SENSe:]FREQuency:STARt on page 1198
[SENSe:]FREQuency:STOP on page 1199
Full Span
Sets the span to the full frequency range of the FSW specified in the specifications
document. This setting is useful for overview measurements.
Remote command:
[SENSe:]FREQuency:SPAN:FULL on page 1198
Zero Span
Sets the span to 0 Hz (zero span). The x-axis becomes the time axis with the grid lines
corresponding to 1/10 of the current sweep time ("SWT").
For details see Section 6.1, "Basic measurements", on page 130.
Remote command:
FREQ:SPAN 0Hz, see [SENSe:]FREQuency:SPAN on page 1198
Last Span
Sets the span to the previous value. With this function you can switch between an
overview measurement and a detailed measurement quickly.
Remote command:
[SENSe:]FREQuency:SPAN on page 1198
Frequency Offset
Shifts the displayed frequency range along the x-axis by the defined offset.
This parameter has no effect on the instrument's hardware, on the captured data, or on
data processing. It is simply a manipulation of the final results in which absolute fre-
quency values are displayed. Thus, the x-axis of a spectrum display is shifted by a
constant offset if it shows absolute frequencies. However, if it shows frequencies rela-
tive to the signal's center frequency, it is not shifted.
A frequency offset can be used to correct the display of a signal that is slightly distorted
by the measurement setup, for example.
The allowed values range from -1 THz to 1 THz. The default setting is 0 Hz.
Remote command:
[SENSe:]FREQuency:OFFSet on page 1198
If the signal drifts on the display but you want to keep the center frequency on the sig-
nal peak, the center frequency can be adjusted automatically using signal tracking. In
this case, the signal trace is surveyed in a specified bandwidth around the expected
center frequency. After each sweep, the center frequency is set to the maximum signal
found within the searched bandwidth. If no maximum signal above a defined threshold
value is found in the searched bandwidth, the center frequency remains unchanged.
The search bandwidth and the threshold value are shown in the diagram by red lines
which are labeled as "TRK".
Signal Tracking
Access: "Overview" > "Frequency" > "Signal Tracking" tab
Defines the settings for signal tracking. These settings are only available for spans > 0.
For more details see Section 7.3.3, "Keeping the center frequency stable - signal track-
ing", on page 479.
If activated, after each sweep, the center frequency is set to the maximum level of the
specified "Signal Track Trace" found within the searched "Tracking Bandwidth".
If the signal level does not pass the "Tracking Threshold", the center frequency is not
changed.
Remote command:
CALCulate<n>:MARKer<m>:FUNCtion:STRack[:STATe] on page 1199
CALCulate<n>:MARKer<m>:FUNCtion:STRack:BANDwidth on page 1200
7.3.5 How to move the center frequency through the frequency range
In some cases it may be useful to move the center frequency through a larger fre-
quency range, for example from one harmonic to another.
1. In the "Frequency" dialog box, define the "Center Frequency Stepsize". This is the
size by which the center frequency is to be increased or decreased in each step.
Enter a manual or relative value, or set the step size to the current center fre-
quency or marker value. To move from one harmonic to the next, use the center
frequency or marker value.
3. Use the arrow keys to move the center frequency in discrete steps through the
available frequency range.
Some background knowledge on the impact of the described settings is provided here
for a better understanding of the required configuration.
● Reference level..................................................................................................... 481
● RF attenuation.......................................................................................................482
● Scaling.................................................................................................................. 483
The reference level value is the maximum value the AD converter can handle without
distortion of the measured value. Signal levels above this value will not be measured
correctly, which is indicated by the "IF Overload" status display.
Internally, the reference level is also used to determine the optimum hardware settings
for the FSW. The defined reference level should correspond with the maximum expec-
ted RF input level.
When determining the expected input level, consider that the power from all input sig-
nals contribute to the total power. The reference level must be higher than the total
power from all signals.
The optimum reference level for the current measurement settings can be set automat-
ically by the FSW (see "Reference Level" on page 486).
The reference level determines the amplitude represented by the topmost grid line in
the display. When you change the reference level, the measurement is not restarted;
the results are merely shifted in the display. Only if the reference level changes due to
a coupled RF attenuation (see "Attenuation Mode / Value" on page 488), the measure-
ment is restarted.
In general, the FSW measures the signal voltage at the RF input. The level display is
calibrated in RMS values of an unmodulated sine wave signal. In the default state, the
level is displayed at a power of 1 mW (= dBm). Via the known input impedance, con-
version to other units is possible.
See "Impedance" on page 366.
Example
1. The initial reference level is 2 dBm with no offset.
Both the displayed reference level and the internal reference level are 2 dBm.
2. An offset of 3 dB is defined.
The displayed reference level is adjusted to 5 dBm.
The internal reference level remains at 2 dBm.
(5 dBm (displayed ref level) - 3 dB (offset) = 2 dBm)
7.4.1.2 RF attenuation
The attenuation is meant to protect the input mixer from high RF input levels. The level
at the input mixer is determined by the set RF attenuation according to the formula:
"levelmixer = levelinput – RF attenuation"
attenuation values cause the inherent noise (i.e the noise floor) to rise and the sensitiv-
ity of the analyzer decreases.
The sensitivity of a signal analyzer is directly influenced by the selected RF attenua-
tion. The highest sensitivity is obtained at an RF attenuation of 0 dB. Each additional
10 dB step reduces the sensitivity by 10 dB, i.e. the displayed noise is increased by 10
dB. To measure a signal with an improved signal-to-noise ratio, decrease the RF
attenuation.
For ideal sinusoidal signals, the displayed signal level is independent of the RF attenu-
ation.
Depending on the type of measurement you must find a compromise between a low
noise floor and high intermodulation levels, and protecting the instrument from high
input levels. You achieve this best by letting the FSW determine the optimum level
automatically (see "Attenuation Mode / Value" on page 488).
Electronic attenuation
If the optional electronic attenuation hardware is installed on the FSW, you can also
activate an electronic attenuator. For details, see "Using Electronic Attenuation"
on page 489.
7.4.1.3 Scaling
In a linear display, the measurement values are distributed linearly throughout the grid.
That means the entire range of measured values is divided by the number of rows in
the grid (10) and each row corresponds to 1/10 of the total range. Linear scaling is use-
ful to determine precise levels for a small range of values. However, if large and small
values appear in the same display, it is difficult to determine individual values precisely
or to distinguish values that are close together.
In a logarithmic display, smaller values are distributed among a much larger area of the
display, while large values are condensed to a smaller area. Now it is much easier to
distinguish several lower values, as they are spread over a wider area. Logarithmic
scaling is useful when large ranges of values must be combined in one display. Loga-
rithmic scaling is best applied to measurement values in logarithmic units (dB, dBm
etc.).
In addition to linear or logarithmic scaling, the vertical axis can be set to display either
absolute or relative values. Absolute values show the measured levels, while relative
values show the difference between the measured level and the defined reference
level. Relative values are indicated in percent for linear scaling, and in dB for logarith-
mic scaling.
Amplitude settings determine how the FSW must process or display the expected input
power levels.
Configuring amplitude settings allows you to:
● Adapt the instrument hardware to the expected maximum signal level by setting
the Reference Level to this maximum
● Consider an external attenuator or preamplifier (using the "Offset").
● Optimize the SNR of the measurement for low signal levels by configuring the Ref-
erence Level as high as possible without introducing compression, clipping or over-
load. Use early amplification by the preamplifier and a low attenuation.
● Optimize the SNR for high signal levels and ensure that the instrument hardware is
not damaged, using high attenuation and AC coupling (for DC input voltage).
● Adapt the reference impedance for power results when measuring in a 75-Ohm
system by connecting an external matching pad to the RF input.
Amplitude settings for input from the optional "Analog Baseband" interface are descri-
bed in the FSW I/Q Analyzer and I/Q Input User Manual.
The remote commands required to define these settings are described in Sec-
tion 13.7.4.1, "Amplitude settings", on page 1210.
Reference Level
Defines the expected maximum reference level. Signal levels above this value are pos-
sibly not measured correctly. Signals above the reference level are indicated by an "IF
Overload" or "OVLD" status display.
The reference level can also be used to scale power diagrams; the reference level is
then used for the calculation of the maximum on the y-axis.
Since the hardware of the FSW is adapted according to this value, it is recommended
that you set the reference level close above the expected maximum signal level. Thus
you ensure an optimal measurement (no compression, good signal-to-noise ratio).
For details, see Section 7.4.1.1, "Reference level", on page 481.
Note that for input from the External Mixer (R&S FSW-B21) the maximum reference
level also depends on the conversion loss, see "Reference level" on page 418.
Note that for input from the External Mixer (R&S FSW-B21) the maximum reference
level also depends on the conversion loss; see the FSW base unit user manual for
details.
For an active external frontend, the reference level refers to the RF input at the exter-
nal frontend, not the levels at the RF input of the FSW. The hardware is adjusted to the
defined reference level optimally for input signals with a crest factor of 10 dB. Thus, the
required reference level for an optimal measurement can differ depending on the crest
factor of the input signal.
See "External Frontend Connection State" on page 453.
Remote command:
DISPlay[:WINDow<n>][:SUBWindow<w>]:TRACe<t>:Y[:SCALe]:RLEVel
on page 1211
Remote command:
INPut:IMPedance on page 1115
CALCulate<n>:UNIT:POWer on page 1211
If the defined reference level cannot be set for the given attenuation, the reference
level is adjusted accordingly and the warning "limit reached" is displayed in the status
bar.
Remote command:
INPut:EATT:STATe on page 1214
INPut:EATT:AUTO on page 1214
INPut:EATT on page 1214
Input Settings
Some input settings affect the measured amplitude of the signal, as well.
The parameters "Input Coupling" and "Impedance" are identical to those in the "Input"
settings.
See Section 7.2.2, "Input source settings", on page 364.
When enabled, the FSW automatically compensates the magnitude and phase charac-
teristics of the external preamplifier in the measurement results. Any internal preampli-
fier, if available, is disabled.
An active external preamplifier is also included in the calculation of the combined user-
defined frequency response correction filter and displayed in the preview for SnP files
(see "Preview" on page 778).
For FSW85 models with two RF inputs, you can enable correction from the external
preamplifier for each input individually, but not for both at the same time.
When disabled, no compensation is performed even if an external preamplifier remains
connected.
Remote command:
INPut:EGAin[:STATe] on page 1216
Noise Cancellation
The FSW can correct the results by removing the inherent noise of the analyzer, which
increases the dynamic range.
In this case, a reference measurement of the inherent noise of the analyzer is carried
out. The measured noise power is then subtracted from the power in the channel that
is being analyzed (first active trace only).
The inherent noise of the instrument depends on the selected center frequency, resolu-
tion bandwidth and level setting. Therefore, the correction function is disabled when-
ever one of these parameters is changed. A disable message is displayed on the
screen. To enable the correction function after changing one of these settings, activate
it again. A new reference measurement is carried out.
Noise cancellation is also available in zero span.
For an active external frontend, noise cancellation is not available. See "External Fron-
tend Connection State" on page 453.
Currently, noise cancellation is only available for the following trace detectors (see
"Detector" on page 626):
● RMS
● Average
● Sample
● Positive peak
Remote command:
[SENSe:]POWer:NCORrection on page 1212
The individual scaling settings that affect the vertical axis are described here.
Access: "Overview" > "Amplitude" > "Scale" tab
Or: [AMPT] > "Scale Config"
The remote commands required to define these settings are described in Sec-
tion 13.7.4, "Configuring the vertical axis (amplitude, scaling)", on page 1210.
Range..........................................................................................................................492
Ref Level Position....................................................................................................... 492
Auto Scale Once......................................................................................................... 492
Scaling........................................................................................................................ 493
Range
Defines the displayed y-axis range in dB.
The default value is 100 dB.
Remote command:
DISPlay[:WINDow<n>][:SUBWindow<w>]:TRACe<t>:Y[:SCALe] on page 1218
Remote command:
DISPlay[:WINDow<n>][:SUBWindow<w>]:TRACe<t>:Y[:SCALe]:AUTO ONCE
on page 1218
Scaling
Defines the scaling method for the y-axis.
For more information, see Section 7.4.1.3, "Scaling", on page 483.
"Logarithmic" Logarithmic scaling (only available for logarithmic units - dB..., and A,
V, Watt)
"Linear with Linear scaling in the unit of the measured signal
Unit"
"Linear Per- Linear scaling in percentages from 0 to 100
cent"
"Absolute" The labeling of the level lines refers to the absolute value of the refer-
ence level (not available for "Linear Percent")
"Relative" The scaling is in dB, relative to the reference level (only available for
logarithmic units - dB...). The upper line of the grid (reference level) is
always at 0 dB.
Remote command:
DISPlay[:WINDow<n>][:SUBWindow<w>]:TRACe<t>:Y:SPACing on page 1220
DISPlay[:WINDow<n>][:SUBWindow<w>]:TRACe<t>:Y[:SCALe]:MODE
on page 1218
This section gives you some advice on how to optimize the display of the measured
signal amplitudes depending on the required evaluation.
1. Perform a measurement with the default settings to get an impression of the values
to be expected.
2. Use the "Auto Level" function ([AUTO] menu) to optimize the reference level.
3. Use the "Auto Scale Once" function ([AUTO] menu) to optimize the scaling.
Now you can determine if any spurious levels of a certain size are visible.
The bandwidth, filter and sweep settings are closely related and interdependent. The
values available for resolution bandwidth and video bandwidth depend on the selected
filter type. In addition, these settings have an impact on other measurement parame-
ters. The following equation shows the interdependency of these settings:
TMIN = K*Span/RBW2
When defining the bandwidth and filter settings, consider the impact of the individual
settings on the other settings and the measurement result, as described in more detail
in the following sections.
● Separating signals by selecting an appropriate resolution bandwidth.................. 494
● Smoothing the trace using the video bandwidth................................................... 495
● Coupling VBW and RBW...................................................................................... 496
● Coupling span and RBW.......................................................................................496
● How data is measured: the sweep type................................................................ 497
● Which data may pass: filter types......................................................................... 498
● How long the data is measured: Sweep Time.......................................................499
● How much data is measured: sweep points and sweep count............................. 499
● How often data is measured: sweep mode........................................................... 500
The resolution bandwidth defines the 3 dB bandwidth of the resolution filter to be used.
An RF sinusoidal signal is displayed according to the passband characteristic of the
resolution filter (RBW), i.e. the signal display reflects the shape of the filter.
A basic feature of a signal analyzer is being able to separate the spectral components
of a mixture of signals. The resolution at which the individual components can be sepa-
rated is determined by the resolution bandwidth. Selecting a resolution bandwidth that
is too large may make it impossible to distinguish between spectral components, i.e.
they are displayed as a single component. Smaller resolution bandwidths, however,
increase the required "Sweep Time".
Two signals with the same amplitude can be resolved if the resolution bandwidth is
smaller than or equal to the frequency spacing of the signal. If the resolution bandwidth
is equal to the frequency spacing, the spectrum display screen shows a level drop of 3
dB precisely in the center of the two signals. Decreasing the resolution bandwidth
makes the level drop larger, which thus makes the individual signals clearer.
The highest sensitivity is obtained at the smallest bandwidth (1 Hz). If the bandwidth is
increased, the reduction in sensitivity is proportional to the change in bandwidth.
Increasing the bandwidth by a factor of 3 increases the displayed noise by approx. 5
dB (4.77 dB precisely). If the bandwidth is increased by a factor of 10, the displayed
noise increases by a factor of 10, i.e. 10 dB.
If there are large level differences between signals, the resolution is determined by
selectivity as well as by the resolution bandwidth that has been selected. The measure
of selectivity used for signal analyzers is the ratio of the 60 dB bandwidth to the 3 dB
bandwidth (= shape factor).
For the FSW, the shape factor for bandwidths is < 5, i.e. the 60 dB bandwidth of the 30
kHz filter is <150 kHz.
The higher spectral resolution with smaller bandwidths is won by longer sweep times
for the same span. The sweep time has to allow the resolution filters to settle during a
sweep at all signal levels and frequencies to be displayed.
If the RBW is too large, signal parts that are very far away (e.g. from a different signal)
are considered in the measurement and distort the results. The noise increases.
If the RBW is too small, parts of the signal are lost. As the displayed signal always
reflects the shape of the filter, select a bandwidth large enough so the displayed signal
reflects the entire shape of the filter.
The video filters are responsible for smoothing the displayed trace. Using video band-
widths that are small compared to the resolution bandwidth, only the signal average is
displayed and noise peaks and pulsed signals are repressed. If pulsed signals are to
be measured, it is advisable to use a video bandwidth that is large compared to the
resolution bandwidth (VBW = 10 x RBW) for the amplitudes of pulses to be measured
correctly.
The level of a sine wave signal is not influenced by the video bandwidth. A sine wave
signal can therefore be freed from noise by using a video bandwidth that is small com-
pared with the resolution bandwidth, and thus be measured more accurately.
The video bandwidth can be coupled to the resolution bandwidth automatically. In this
case, if the resolution bandwidth is changed, the video bandwidth is automatically
adjusted.
Coupling is recommended if a minimum "Sweep Time" is required for a selected reso-
lution bandwidth. Narrow video bandwidths require longer "Sweep Time"s due to the
longer settling time. Wide bandwidths reduce the signal/noise ratio.
Table 7-3: Overview of RBW/VBW ratios and recommendations for use
The resolution bandwidth can be coupled to the span setting, either by a manually
defined factor or automatically. If the span is changed, the resolution bandwidth is
automatically adjusted. The automatic coupling adapts the resolution bandwidth to the
currently set frequency span/100.
The 6 dB bandwidths 200 Hz, 9 kHz and 120 kHz and the available channel filters are
not changed by the coupling.
With a span/RBW ratio of 100 and a screen resolution of 1000 pixels, each frequency
in the spectrum is displayed by 10 pixels. A span/RBW ratio of 1000 provides the high-
est resolution.
In a standard analog frequency sweep, the local oscillator of the analyzer sweeps the
applied signal quasi analog from the start to the stop frequency to determine the fre-
quency spectrum.
Alternatively, the analyzer can sample signal levels over time at a defined frequency
and transform the data to a spectrum by Fast Fourier Transformation (FFT). Although
this measurement method requires additional calculations, it can provide results much
faster than the frequency sweep, in particular for small RBWs.
Which sweep mode is appropriate for the current measurement depends on the span,
RBW, VBW and "Sweep Time" settings. By default ("Auto" sweep type), the FSW auto-
matically uses the sweep type with the highest sweep rate depending on these mea-
surement settings.
For EMI measurements, the FSW automatically selects sweep mode for auto sweep
type. You can also select sweep mode manually.
Optimization
In FFT mode, FFT analysis is performed to determine a spectrum of frequencies. Sev-
eral analysis steps are required to cover the entire span. The subspan which is cov-
ered by one FFT analysis depends on the RBW. The subspan cannot be defined
directly, but it can be optimized according to measurement requirements.
Narrow subspans provide a higher dynamic range, and also allow you to perform mea-
surements near a carrier with a reduced reference level. With a wide subspan, the car-
rier and the useful signal are likely to be measured at the same time, in which case the
powers of both signals are summarized, so the reference level must be high enough to
consider this factor. With a narrow subspan, this is less likely to happen, so the refer-
ence level can be reduced.
For an optimal dynamic range, the narrowest possible subspan (depending on the
RBW) is used. Furthermore, the autorange function for the internal IF gain calculation
is activated to obtain the best control range of the A/D converter.
On the other hand, the narrower the subspan, the more steps are required to cover the
entire span, thus increasing analysis and calculation time. To optimize the sweep
rate, the widest possible subspan (depending on the RBW) is used.
For an optimal sweep rate, it is recommended that you set the "Sweep Time" to "Auto",
as well.
Number of subspans
Several analysis steps are required to cover the entire span, in particular if the span
exceeds the maximum I/Q bandwidth for a single measurement. In this case, each FFT
analysis covers a subspan. The subspan cannot be defined directly, but it can be opti-
mized according to measurement requirements, as described above. The number of
required subspans is indicated in the sweep settings dialog box. Thus, you can deter-
mine the required measurement time for an individual span (and thus sweep point) as:
<Meas time subspan> = <sweep time> / <no. of subspans>
While the filter is irrelevant when measuring individual narrowband signals (as long as
the signal remains within the RBW), the measurement result for broadband signals is
very dependant on the selected filter type and its shape. If the filter is too narrow, the
signal is distorted by the filter. If the filter is too wide, multiple signals can no longer be
distinguished. Generally, the smaller the filter width and the steeper its edges, the lon-
ger the settling time and thus the longer the "Sweep Time" must be.
All resolution bandwidths are realized with digital filters. Normal (3dB) Gaussian filters
are set by default. Some communication standards require different filters.
For a list of available filter types, see the specifications document.
Channel filters
Channel filters are fairly steep but require a long settling time; they are useful for pulse
measurements in the time domain.
RRC filters
Root raised cosine filters are similar in shape to channel filters and are required by
some measurement standards.
5-Pole filters
5-Pole filters are very broad and allow for a large bandwidth to pass.
Each filter has a settling time that must be awaited in order to obtain correct results.
Since the resolution bandwidth and video bandwidth define the filter, the smaller of the
two determines the minimum "Sweep Time" required for the measurement. Allowed
values depend on the ratio of span to RBW and RBW to VBW.
If the selected "Sweep Time" is too short for the selected bandwidth and span, level
measurement errors will occur. In this case, the FSW displays the error message
"Sweep time too low" and marks the indicated "Sweep Time" with a red bullet. Further-
more, a status bit indicates an error.
(For more information see Section 12.2.2.14, "STATus:QUEStionable:TIMe register",
on page 837.)
The "Sweep Time" can be coupled to the span (not zero span), video bandwidth (VBW)
and resolution bandwidth (RBW) automatically. If the span, resolution bandwidth or
video bandwidth is changed, the "Sweep Time" is automatically adjusted.
Note that the "Sweep Time" only indicates how long data is captured; the time required
to process the captured data may be considerably longer, in particular for FFT mode.
For FFT mode, an estimated duration is indicated behind the "Sweep Time" in the
channel bar (for RF measurements only).
7.5.1.8 How much data is measured: sweep points and sweep count
By default, 1001 data points are determined in a single sweep. During the next sweep,
1001 new data points are collected, and so on. The number of sweep points defines
how much of the entire span is covered by a single data point. By increasing the num-
ber of sweep points you can increase the reliability of the individual data points and
thus the accuracy of the analyzed results. However, these data points are all stored on
the instrument, occupying a large amount of memory, and each sweep point increases
the overall measurement time.
The number of sweeps to be performed in single sweep mode is defined by the
"Sweep Count". Values from 0 to 200000 are allowed. If the values 0 or 1 are set, one
sweep is performed. The sweep count is applied to all the traces in a diagram.
If the trace configurations "Average", "Max Hold" or "Min Hold" are set, the "Sweep/
Average Count" also determines the number of averaging or maximum search proce-
dures (see "Analyzing several traces - trace mode" on page 620).
For details on how the number of sweep points and the sweep count affect the trace
results on the screen, see "Mapping samples to sweep points with the trace detector"
on page 611.
How often the spectrum is swept depends on the sweep mode. Either a certain number
of sweeps can be defined ("Sweep Count") which are performed in "Single Sweep"
mode, or the sweep is repeated continuously ("Continuous Sweep" mode).
By default, the data is collected for the specified number of sweeps and the corre-
sponding trace is displayed. When the next sweep is started, the previous trace is
deleted.
However, the data from a single sweep run can also be retained and displayed
together with the new data ("Continue Single Sweep" mode). This is particularly of
interest when using the trace configurations "Average" or "Max Hold" to take previously
recorded measurements into account for averaging/maximum search (see "Analyzing
several traces - trace mode" on page 620).
RBW............................................................................................................................503
VBW............................................................................................................................ 503
Sweep Time................................................................................................................ 504
Span/RBW.................................................................................................................. 504
RBW/VBW...................................................................................................................504
Filter Type................................................................................................................... 505
Default Coupling..........................................................................................................505
Sweep/Average Count................................................................................................ 506
Sweep Points.............................................................................................................. 506
Optimization................................................................................................................ 506
Sweep Type................................................................................................................ 507
FFT Subspans.............................................................................................................508
Single Sweep / Run Single..........................................................................................508
Continuous Sweep / Run Cont....................................................................................508
Continue Single Sweep...............................................................................................509
Spectrogram Frames.................................................................................................. 509
└ Select Frame.................................................................................................509
└ Continue Frame............................................................................................ 509
└ Frame Count................................................................................................. 510
└ Clear Spectrogram........................................................................................510
RBW
Defines the resolution bandwidth. The available resolution bandwidths are specified in
the specifications document. Numeric input is always rounded to the nearest possible
bandwidth.
If "Auto" is selected, the resolution bandwidth is coupled to the selected span (for span
> 0). If the span is changed, the resolution bandwidth is automatically adjusted.
If the resolution bandwidth is defined manually, a green bullet is displayed next to the
"RBW" display in the channel bar.
For a list of supported filters, see the specifications document.
For more information see Section 7.5.1.1, "Separating signals by selecting an appropri-
ate resolution bandwidth", on page 494.
Note: Restrictions.
● For measurements on I/Q data in the frequency domain, the maximum RBW is
1 MHz.
● Some additional Gaussian filters are provided for special measurements, such as
5G NR spurious emissions measurements. They are only available if you enter the
value manually, not using the rotary knob or stepping through the filter values. They
are not supported by all applications. For these particular filters, gating is also pos-
sible. The following values indicate the 3-dB filter width:
– 51 kHz
– 150 kHz
– 250 kHz
– 400 kHz
– 450 kHz
– 6 MHz
– 8 MHz
● For EMI measurements using the quasipeak detector, the 1 MHz RBW filter is not
available (see Section 6.13.3.1, "Resolution bandwidth and filter types",
on page 337).
Remote command:
[SENSe:]BANDwidth[:RESolution] on page 1201
[SENSe:]BANDwidth[:RESolution]:AUTO on page 1202
VBW
Defines the video bandwidth automatically or manually.
For more information see Section 7.5.1.2, "Smoothing the trace using the video band-
width", on page 495.
"Auto" The video bandwidth is coupled to the resolution bandwidth. If the
resolution bandwidth is changed, the video bandwidth is automatically
adjusted.
"Manual" For manual mode, define the bandwidth value. The available video
bandwidths are specified in the specifications document. Numeric
input is always rounded to the nearest possible bandwidth.
If the video bandwidth is defined manually, a green bullet is displayed
next to the "VBW" display in the channel bar.
Remote command:
[SENSe:]BANDwidth:VIDeo:AUTO on page 1204
[SENSe:]BANDwidth:VIDeo on page 1203
[SENSe:]BANDwidth:VIDeo:TYPE on page 1204
Sweep Time
Defines the duration of a single sweep, during which the defined number of sweep
points are measured. The "Sweep Time" can be defined automatically or manually.
The allowed "Sweep Time" depends on the device model; refer to the specifications
document.
For more information see Section 7.5.1.7, "How long the data is measured: Sweep
Time", on page 499.
Note: The "Sweep Time" only indicates how long data is captured; the time required to
process the captured data may be considerably longer, in particular for FFT mode. For
FFT mode, an estimated duration is indicated behind the "Sweep Time" in the channel
bar (for RF measurements only).
"Auto" The "Sweep Time" is coupled to the span (not zero span), video
bandwidth (VBW) and resolution bandwidth (RBW). If the span, reso-
lution bandwidth or video bandwidth is changed, the "Sweep Time" is
automatically adjusted.
"Manual" For manual mode, define the "Sweep Time". Allowed values depend
on the ratio of span to RBW and RBW to VBW. For details refer to the
specifications document. Numeric input is always rounded to the
nearest possible "Sweep Time".
Remote command:
[SENSe:]SWEep:TIME:AUTO on page 1208
[SENSe:]SWEep:TIME on page 1208
[SENSe:]SWEep:DURation? on page 1206
Span/RBW
Sets the coupling ratio if RBW is set to auto mode.
For more information see Section 7.5.1.4, "Coupling span and RBW", on page 496.
"Auto[100]" "Resolution Bandwidth" = "Span/100"
This coupling ratio is the default setting of the FSW.
"Manual" The coupling ratio is defined manually.
The span/resolution bandwidth ratio can be set in the range from 1 to
10000.
Remote command:
[SENSe:]BANDwidth[:RESolution]:RATio on page 1202
RBW/VBW
Sets the coupling ratio between the resolution bandwidth and the video bandwidth.
This setting is only effective if VBW is set to auto mode.
For more information see Section 7.5.1.3, "Coupling VBW and RBW", on page 496.
Filter Type
Defines the filter type.
The following filter types are available:
● Normal (3dB)
● Channel
● RRC (not available for sweep type "FFT")
● 5-Pole (not available for sweep type "FFT")
● CISPR (6 dB) - requires EMI (R&S FSW-K54) option
● MIL Std (6 dB) - requires EMI (R&S FSW-K54) option
For more information, see Section 7.5.1.6, "Which data may pass: filter types",
on page 498.
Note: The EMI-specific filter types are available if the EMI (R&S FSW-K54) measure-
ment option is installed, even if EMI measurement is not active. If you select a CISPR
trace detector, the filter type is automatically also set to CISPR. An active CISPR filter
is indicated in the channel info, next to the RBW information. For details, see Sec-
tion 6.13.3.1, "Resolution bandwidth and filter types", on page 337.
The RBW filter configured in the bandwidth settings is identical to the filter configured
in the EMI configuration.
Remote command:
[SENSe:]BANDwidth[:RESolution]:TYPE on page 1203
Default Coupling
Sets all coupled functions to the default state ("Auto"). In addition, the ratio "RBW/
VBW" is set to "Sine[1/1]" and the ratio "Span/RBW" to 100.
For more information see Section 7.5.1.3, "Coupling VBW and RBW", on page 496.
Remote command:
[SENSe:]BANDwidth[:RESolution]:AUTO on page 1202
[SENSe:]BANDwidth:VIDeo:AUTO on page 1204
[SENSe:]SWEep:TIME:AUTO on page 1208
Sweep/Average Count
Defines the number of sweeps to be performed in the single sweep mode. Values from
0 to 200000 are allowed. If the values 0 or 1 are set, one sweep is performed.
The sweep count is applied to all the traces in all diagrams.
If the trace modes "Average", "Max Hold" or "Min Hold" are set, this value also deter-
mines the number of averaging or maximum search procedures.
In continuous sweep mode, if "Sweep Count" = 0 (default), averaging is performed
over 10 sweeps. For "Sweep Count" =1, no averaging, maxhold or minhold operations
are performed.
For more information, see Section 7.5.1.8, "How much data is measured: sweep points
and sweep count", on page 499.
For spectrogram displays, the sweep count determines how many sweeps are com-
bined in one frame in the spectrogram; that is: how many sweeps the FSW performs to
plot one trace in the spectrogram result display. For more details, see "Time frames"
on page 632.
Remote command:
[SENSe:]SWEep:COUNt on page 1205
[SENSe:]AVERage<n>:COUNt on page 1249
Sweep Points
Defines the number of measured values to be collected during one sweep.
For details see Section 7.5.1.8, "How much data is measured: sweep points and
sweep count", on page 499.
All values from 101 to 100001 can be set. The default value is 1001 sweep points.
For EMI measurements, 200001 sweep points are available.
Remote command:
[SENSe:]SWEep[:WINDow<n>]:POINts on page 1208
Optimization
In FFT mode, several FFT analysis steps are required to cover the entire measurement
span. The span which is covered by one FFT analysis step is called subspan. The sub-
span cannot be defined directly, but it can be optimized according to measurement
requirements.
Note: To determine the number of required subspans for the measurement, see "FFT
Subspans" on page 508.
"Dynamic" Optimizes the dynamic range by using the narrowest possible subspan (depending
on the RBW).
The autorange function for the internal IF gain calculation is activated to obtain the
best control range for the A/D converter.
"Speed" Optimizes the sweep rate by using the widest possible subspan (depending on the
RBW).
The autorange function for the internal IF gain calculation is deactivated. (Note: set
the reference level accordingly to optimize the control range for the A/D converter).
It is recommended that you set the Sweep Time to "Auto" to optimize the sweep
rate.
Sweep Type
Defines the sweep type.
"Sweep" In the standard sweep mode, the local oscillator is set to provide the
spectrum quasi analog from the start to the stop frequency.
"Auto" Automatically sets the fastest available sweep type for the current
measurement (Frequency or FFT). Auto mode is set by default.
"FFT" The FFT sweep samples on a defined frequency value and trans-
forms it to the spectrum by fast Fourier transform (FFT) (see also
Section 7.5.1.5, "How data is measured: the sweep type",
on page 497).
FFT is not available in the following cases:
● When using 5-Pole filters or RRC filters
● When using one of the CISPR detectors
● When an external generator is active (via hardware option)
In these cases, frequency sweep is used.
Remote command:
[SENSe:]SWEep:TYPE on page 1209
FFT Subspans
Indicates the number of FFT subspans required to cover the entire measurement
range (read-only).
See also "Number of subspans" on page 498.
Only available in FFT sweep mode in the Spectrum application, and not for SEM,
ACLR, or Spurious emissions measurements.
Remote command:
[SENSe:]SWEep:FFTSubspan? on page 1206
While the measurement is running, "Continuous Sweep" and [RUN CONT] are high-
lighted. The running measurement can be aborted by selecting the highlighted softkey
or key again. The results are not deleted until a new measurement is started.
Note: Sequencer. If the Sequencer is active, "Continuous Sweep" only controls the
sweep mode for the currently selected channel. However, the sweep mode only takes
effect the next time the Sequencer activates that channel, and only for a channel-
defined sequence. In this case, a channel in continuous sweep mode is swept repeat-
edly.
Furthermore, [RUN CONT] controls the Sequencer, not individual sweeps. [RUN
CONT] starts the Sequencer in continuous mode.
For details on the Sequencer, see Section 5.4.1, "The sequencer concept",
on page 124.
For details on the Sequencer, see the FSW base unit user manual.
Remote command:
INITiate<n>:CONTinuous on page 912
Spectrogram Frames
These settings are only available if spectrogram display is active.
For more information see Section 8.5.2.3, "How to display and configure a spectro-
gram", on page 644.
● On
When the average or peak values are determined for the new sweep, the results of
the previous sweeps in the spectrogram are also considered.
● Off
The average or peak values are determined from the results of the newly swept
frames only.
Remote command:
CALCulate<n>:SPECtrogram:CONTinuous on page 1253
7.6.1 Triggering
In a basic measurement with default settings, the sweep is started immediately. How-
ever, sometimes you want the measurement to start only when a specific condition is
fulfilled, for example a signal level is exceeded, or in certain time intervals. For these
cases, you can define a trigger for the measurement. In FFT sweep mode, the trigger
defines when the data acquisition starts for the FFT conversion.
An "Offset" can be defined to delay the measurement after the trigger event, or to
include data before the actual trigger event in time domain measurements (pre-trigger
offset).
For complex tasks, advanced trigger settings are available:
● Hysteresis to avoid unwanted trigger events caused by noise
● Holdoff to define exactly which trigger event causes the trigger in a jittering signal
● Trigger source....................................................................................................... 511
● Trigger offset......................................................................................................... 511
● Trigger hysteresis.................................................................................................. 511
● Trigger drop-out time.............................................................................................512
● Trigger holdoff....................................................................................................... 513
Trigger source
The trigger source defines which source must fulfill the condition that triggers the mea-
surement. Basically, the source can be:
● Time: the measurement is repeated in a regular interval
● Power: an input signal is checked for a defined power level
The trigger signal can be any of the following:
– The input signal at one of various stages in the signal analysis process - before
or after the input mixer, after the video filter etc.
– A signal from an external device via one of the TRIGGER INPUT / OUTPUT
connectors on the instrument
– A signal from a power sensor, see "Using a power sensor as an external power
trigger" on page 370.
For details on the available trigger sources, see "Trigger Source" on page 516.
Trigger offset
An offset can be defined to delay the measurement after the trigger event, or to include
data before the actual trigger event in time domain measurements (pre-trigger offset).
Pre-trigger offsets are possible because the FSW captures data continuously in the
time domain, even before the trigger occurs.
See "Trigger Offset" on page 520.
Trigger hysteresis
Setting a hysteresis for the trigger helps avoid unwanted trigger events caused by
noise, for example. The hysteresis is a threshold to the trigger level that the signal
must fall below on a rising slope or rise above on a falling slope before another trigger
event occurs.
Example:
In the following example, the signal does not drop below the hysteresis (threshold)
before it reaches the trigger level again. Thus, the second possible trigger event on the
rising edge is ignored. On the falling edge, however, two trigger events occur. The sig-
nal exceeds the hysteresis before it falls to the trigger level the second time.
Trigger
hysteresis
Trigger level
T T
T T
T T T
Drop-Out
Drop-Out
For gated measurements, a combination of a falling edge trigger and a drop-out time is
generally not allowed.
Trigger holdoff
The trigger holdoff defines a waiting period before the next trigger after the current one
will be recognized.
Frame 1 Frame 2
T T T T
Holdoff
External triggers from one of the TRIGGER INPUT / OUTPUT connectors on the FSW
are configured in a separate tab of the dialog box.
See Section 7.2.9, "Trigger input/output settings", on page 470
└ RF Power...................................................................................................... 518
└ Power Sensor............................................................................................... 519
└ Time.............................................................................................................. 519
Trigger Level............................................................................................................... 519
Repetition Interval....................................................................................................... 520
Drop-Out Time.............................................................................................................520
Trigger Offset.............................................................................................................. 520
Hysteresis................................................................................................................... 520
Trigger Holdoff.............................................................................................................521
Slope........................................................................................................................... 521
Preview
The preview mode allows you to try out trigger and gate settings before actually apply-
ing them to the current measurement.
The preview diagram displays a zero span measurement at the center frequency with
the defined RBW and sweep time. This is useful when analyzing bursts, for example,
to determine the required gate settings.
The trigger and gate settings are applied to the measurement when the dialog box is
closed.
Note: The zero span settings refer only to the preview diagram. The main diagram
remains unchanged.
If preview mode is switched off, any changes to the settings in this dialog box are
applied to the measurement diagram directly. In this case, the zero span settings for
the preview diagram are not displayed.
For information on the zero span settings, see:
● "Center Frequency" on page 476
● "RBW" on page 349
● "Sweep Time" on page 504
Frequency ← Preview
Defines the center frequency for the preview diagram.
Remote command:
[SENSe:]FREQuency:CENTer on page 1195
RBW ← Preview
Defines the resolution bandwidth for the preview diagram. The available resolution
bandwidths are specified in the specifications document. Numeric input is always roun-
ded to the nearest possible bandwidth.
Remote command:
[SENSe:]BANDwidth[:RESolution] on page 1201
Trigger Source
Selects the trigger source. If a trigger source other than "Free Run" is set, "TRG" is dis-
played in the channel bar and the trigger source is indicated.
For gated measurements, this setting also selects the gating source.
For more information, see "Trigger source" on page 511.
Note: When triggering or gating is activated, the squelch function is automatically dis-
abled.
(See "Squelch" on page 583).
For an active external frontend, only external triggers, I/Q power triggers and (periodic)
time triggers are supported as trigger sources.
See "External Frontend Connection State" on page 453.
Note: If the 1.2 GHz bandwidth extension option (B1200) or the internal 2 GHz option
(B2001) is active, only an external trigger, IF power trigger, or no trigger is available.
If a B4001/B6001/B8001 bandwidth extension option is active, only an external trigger,
power trigger, or no trigger is available for bandwidths ≥80 MHz. If any trigger other
than an external trigger or power trigger is active and the analysis bandwidth is
increased above 80 MHz (thus activating the B4001/B6001/B8001 option), the trigger
is automatically deactivated.
Remote command:
TRIGger[:SEQuence]:SOURce on page 1225
[SENSe:]SWEep:EGATe:SOURce on page 1232
Remote command:
TRIG:SOUR IFP, see TRIGger[:SEQuence]:SOURce on page 1225
SWE:EGAT:SOUR IFP for gated triggering, see [SENSe:]SWEep:EGATe:SOURce
on page 1232
Trigger Level
Defines the trigger level for the specified trigger source.
For gated measurements, this setting also defines the gate level.
For details on supported trigger levels, see the instrument specifications document.
For time triggers, the repetition interval is defined. See "Repetition Interval"
on page 520.
Remote command:
TRIGger[:SEQuence]:LEVel:IFPower on page 1224
TRIGger[:SEQuence]:LEVel:IQPower on page 1224
TRIGger[:SEQuence]:LEVel[:EXTernal<port>] on page 1223
TRIGger[:SEQuence]:LEVel:VIDeo on page 1225
TRIGger[:SEQuence]:LEVel:RFPower on page 1224
For baseband input only:
TRIGger[:SEQuence]:LEVel:BBPower on page 1223
Repetition Interval
Defines the repetition interval for a time trigger.
The shortest interval is 2 ms.
Set the repetition interval to the exact pulse period, burst length, frame length or other
repetitive signal characteristic. If the required interval cannot be set with the available
granularity, configure a multiple of the interval that can be set. Thus, the trigger
remains synchronized to the signal.
Remote command:
TRIGger[:SEQuence]:TIME:RINTerval on page 1227
Drop-Out Time
Defines the time that the input signal must stay below the trigger level before triggering
again.
For more information on the drop-out time, see "Trigger drop-out time" on page 512.
Note: For input from the optional "Analog Baseband" interface using the baseband
power trigger (BBP), the default drop out time is set to 100 ns. This avoids uninten-
tional trigger events (as no hysteresis can be configured in this case).
Remote command:
TRIGger[:SEQuence]:DTIMe on page 1221
Trigger Offset
Defines the time offset between the trigger event and the start of the sweep.
For more information, see "Trigger offset" on page 511.
For the "Time" trigger source in swept measurements, this function is not available.
Remote command:
TRIGger[:SEQuence]:HOLDoff[:TIME] on page 1222
Hysteresis
Defines the distance in dB to the trigger level that the trigger source must exceed
before a trigger event occurs. Setting a hysteresis avoids unwanted trigger events
caused by noise oscillation around the trigger level.
This setting is only available for "IF Power" trigger sources. The range of the value is
between 3 dB and 50 dB with a step width of 1 dB.
For more information, see "Trigger hysteresis" on page 511.
Remote command:
TRIGger[:SEQuence]:IFPower:HYSTeresis on page 1223
Trigger Holdoff
Defines the minimum time (in seconds) that must pass between two trigger events.
Trigger events that occur during the holdoff time are ignored.
For more information, see "Trigger holdoff" on page 513.
Remote command:
TRIGger[:SEQuence]:IFPower:HOLDoff on page 1222
Slope
For all trigger sources except time, you can define whether triggering occurs when the
signal rises to the trigger level or falls down to it.
For gated measurements in "Edge" mode, the slope also defines whether the gate
starts on a falling or rising edge.
Remote command:
TRIGger[:SEQuence]:SLOPe on page 1225
[SENSe:]SWEep:EGATe:POLarity on page 1232
2. Set the "Frequency", "RBW" and "Sweep Time" such that the relevant part of the
signal is displayed, for example a complete burst.
3. Determine the parameters you want to use to define the trigger and gate conditions
from the preview diagram, for example:
● the length of a burst or slot
● the upper or lower power level of a pulse
● the maximum noise level
● the power level or time at which a certain incident occurs
4. Try out different trigger and gate settings as described in How to configure a trig-
gered measurement and How to configure a gated measurement, then select
"Update Main Diagram" to see the effect of the current settings on the main mea-
surement in the background.
5. If the results are as expected, close the dialog box to keep the changes perma-
nently. Otherwise, correct the settings as necessary.
2. Define the "Repetition Interval": the time after which a new measurement is started.
2. In the "Trigger And Gate" dialog box, define the "Trigger Source" = "External".
3. If you are using the variable TRIGGER 2 INPUT / OUTPUT connector, you must
define its use as an input connector. In the "Trigger In/Out" tab of the "Trigger And
Gate" dialog box, set the corresponding trigger to "Input".
(Note: Trigger 2 is on the front panel, Trigger 3 is on the rear panel.)
4. Configure the external trigger as described for the other power triggers.
2. Define the "Trigger Level": the power level at which the measurement will start.
For a "Video" trigger source you can move the level line graphically to define the
level. If you define the value numerically, you must enter a percentage of the full
diagram height as the level.
3. Define whether the signal must cross the trigger level on a falling or on a rising
edge ("Slope") to trigger the measurement.
5. To reject triggers due to noise or jittering in the signal, define a "Hysteresis" that is
larger than the expected noise or jittering. After the previous trigger, the signal
must exceed this threshold before the next level crossing triggers a new measure-
ment.
6. To skip multiple triggers in a burst, define a "Holdoff" time that must pass between
two triggers. The holdoff time should be slightly larger than the burst.
7.6.2 Gating
● Gated measurements............................................................................................523
● Gate settings......................................................................................................... 526
● Continuous gate settings.......................................................................................528
● Gate source settings............................................................................................. 529
● How to configure a gated measurement............................................................... 530
Like a gate provides an opening in a fence, a gated measurement lets data from the
input signal pass in defined areas only. The gate controls exactly when data is included
in the measurement results and when not. The gate is opened by the trigger source,
which is also the gate source.
Gates can be used in two different modes:
● Level: The gate opens and the measurement starts when a defined level in the
gate source is exceeded and stops when the gate source drops below the "Gate
Level".
Using a pulsed gate signal in level mode, the following behavior can be achieved:
When the gate source signal is active, the input signal data is collected; when the
gate signal is inactive, the input signal is ignored.
● Edge: The gate opens and the measurement starts when a defined level in the
gate source is exceeded and stops when the defined "Gate Length" is reached.
Restrictions
● The "Gate Mode" Level is not supported for Rohde & Schwarz power sensors. The
signal sent by these sensors merely reflects the instant the level is first exceeded,
rather than a time period. However, only time periods can be used for gating in
level mode. Thus, the trigger impulse from the sensors is not long enough for a
fully gated measurement; the measurement cannot be completed.
For details on power sensors, see "Using a power sensor as an external power trigger"
on page 370.
Additionally, a delay time can be defined so that the first few measurement points after
the gate opening are ignored.
Figure 7-36: Effects of Gate mode, Gate delay and Gate length
Example:
By using a gate in sweep mode and stopping the measurement while the gate signal is
inactive, the spectrum for pulsed RF carriers can be displayed without the superposi-
tion of frequency components generated during switching. Similarly, the spectrum can
also be analyzed for an inactive carrier. The sweep can be controlled by an external
gate or by the internal power trigger.
Gated sweep operation is also possible for zero span measurements. This allows you
to display level variations of individual slots, for instance in burst signals, versus time.
To indicate that a gate is used for the sweep, "GAT" and the gate source is displayed in
the channel bar.
Continuous gating
With common gating, a measurement is performed each time the trigger event occurs.
However, when using an external trigger, the measurement time for a single gate is
restricted by the repetition rate of the external trigger.
Now, a new function in the FSW allows you to perform a number of measurements
periodically after each external trigger event. This function can speed up the measure-
ment significantly. After the first external trigger event, a specified number of gate peri-
ods are generated internally, in a specified interval, without requiring additional trigger
events. Only after the specified number of measurements have been performed, the
FSW waits for the next external trigger event.
Example:
Continuous gating is useful, for example, if you want to measure a periodic signal
which occurs after a specific trigger event. Using gate periods, you can average the
individual periods of the signal for several trigger events.
Continuous gating can also improve the measurement speed, as you no longer have to
wait for the next external trigger events, but can measure several periodic bursts after
a single trigger event.
Settings for continuous gate periods are defined in a separate tab of the "Trigger / Gate
Config" dialog box (see Section 7.6.2.3, "Continuous gate settings", on page 528).
Example:
A rotating antenna can be used as a general (external) trigger source, for example.
Only when the antenna reaches a specified position, measurement is possible. A sec-
ond external trigger can then be used to control the gating periods to measure a burs-
ted signal.
RF Signal ...
Frame trigger
(Ext. Trigger2) ...
Measured 1 2 3 4 5 6 7 8 1 2 3 4 5 6
Gates
...
Access: "Overview" > "Trigger" > "Trigger / Gate Config." > "Gate Settings"
Gated Trigger
Switches gated triggering on or off.
If the gate is switched on, a gate signal applied to one of the TRIGGER INPUT connec-
tors or the internal IF power trigger controls the sweep.
Remote command:
[SENSe:]SWEep:EGATe on page 1228
Gate Mode
Sets the gate mode.
For more information, see Section 7.6.2.1, "Gated measurements", on page 523
"Edge" The trigger event for the gate to open is the detection of the signal
edge.
After the gate signal has been detected, the gate remains open until
the gate length is over.
"Level" The trigger event for the gate to open is a particular power level.
After the gate signal has been detected, the gate remains open until
the signal disappears.
Note: If you perform gated measurements in combination with the IF
Power trigger, the FSW ignores the holding time for frequency sweep,
FFT sweep, zero span and I/Q mode measurements.
This mode is not supported when using R&S Power Sensors as
power triggers ("Trg/Gate Source" = Power Sensor or External).
Remote command:
[SENSe:]SWEep:EGATe:TYPE on page 1233
Gate Delay
Defines the delay time between the gate signal and the continuation of the measure-
ment.
The delay position on the time axis in relation to the sweep is indicated by a line
labeled "GD".
For more information, see Section 7.6.2.1, "Gated measurements", on page 523
Remote command:
[SENSe:]SWEep:EGATe:HOLDoff on page 1230
Gate Length
Defines how long the gate is open when it is triggered.
The gate length can only be set in the edge-triggered gate mode. In the level-triggered
mode the gate length depends on the level of the gate signal.
The gate length in relation to the sweep is indicated by a line labeled "GL".
For more information, see Section 7.6.2.1, "Gated measurements", on page 523
Remote command:
[SENSe:]SWEep:EGATe:LENGth on page 1230
Access: "Overview" > "Trigger" > "Trigger / Gate Config." > "Cont. Gate" tab
Continuous gating allows you to perform a continuous gated sweep after a single
external trigger is received.
Continuous Gate
Activates or deactivates continuous gating.
Access: "Overview" > "Trigger" > "Gate Settings" > "Source" tab
By default, the gate is opened by the trigger source, which is also the gate source.
However, you can also use different sources for a general trigger and the beginnning of
the individual gates. In this case, the trigger source defines when measurement is gen-
erally possible, and the gate source determines which data is actually measured.
Triggered gated measurements are only available in applications based on frequency
sweeps (not I/Q-data based), such as the Spectrum application.
For more information see "Triggered gated measurements" on page 526.
For more information see the FSW User Manual.
Source
Selects the gating trigger source which determines when the gate is opened. For Gate
Source Mode "AUTO", the trigger defined by Trigger Source is used both for the gen-
eral measurement trigger and the gating trigger.
The following gate trigger sources are supported:
● External Trigger 1/2/3
● Power Sensor
Remote command:
[SENSe:]SWEep:EGATe:SOURce on page 1232
Level
Defines the gate level for which the gate is open.
Remote command:
[SENSe:]SWEep:EGATe:LEVel[:EXTernal<tp>] on page 1230
[SENSe:]SWEep:EGATe:LEVel:RFPower on page 1231
Polarity
Defines whether the gate is opened when the signal rises to the trigger level or falls
down to it. For gated measurements in "Edge" mode, the slope defines whether the
gate starts on a falling or rising edge.
Remote command:
[SENSe:]SWEep:EGATe:POLarity on page 1232
A gated measurement records data only while the gate conditions are fulfilled. These
step-by-step instructions demonstrate how to configure a gated measurement man-
ually.
2. The gate is opened by a trigger event, which must be based on a power source.
Define the trigger as described in Section 7.6.1.4, "How to configure a triggered
measurement", on page 521.
As the "Trigger Source", use "IF Power", "Video" or "External".
4. To open the gate with a time delay, for example to ignore an overshoot, define a
"Gate Delay".
2. In the "Gate Settings" of the "Trigger and Gate" dialog box, select "Gated Trigger":
"On".
3. Define the gate settings as described in "To configure a common gated measure-
ment" on page 531.
6. Define the length in seconds from the beginning of one gate measurement to the
beginning of the next one ("Gate Period Length").
7. Define how many gate measurements are to be performed after a single trigger
event ("Gate Period Count").
8. Run a measurement and wait for the external trigger event to occur.
2. In order to trigger the initial gate, define a trigger event based on a power source.
Define the trigger as described in Section 7.6.1.4, "How to configure a triggered
measurement", on page 521. As the "Trigger Source", use "External" or "Power
Sensor" (if available).
3. Each individual gate is also opened by a trigger event. To use a different trigger
source for the individual gates than for general measurement:
a) Switch to the "Source" tab for gate settings.
b) As the "Source", select "External" or "Power Sensor" (if available).
c) Configure the power trigger as defined in Section 7.6.1.4, "How to configure a
triggered measurement", on page 521.
6. To open the gate with a time delay, for example to ignore an overshoot, define a
"Gate Delay".
Measurement results can be displayed and evaluated using various different methods,
also at the same time. Depending on the currently selected measurement, in particular
when using optional firmware applications, not all evaluation methods are available.
The evaluation methods described here are available for most measurements in the
Spectrum application.
Diagram.......................................................................................................................537
Marker Table............................................................................................................... 537
Marker Peak List......................................................................................................... 538
Result Summary..........................................................................................................538
Spectrogram................................................................................................................538
Diagram
Displays a basic level vs. frequency or level vs. time diagram of the measured data to
evaluate the results graphically. This is the default evaluation method. Which data is
displayed in the diagram depends on the "Trace" settings. Scaling for the y-axis can be
configured.
See Section 8.5, "Trace configuration", on page 611 and Section 7.4.3, "Scaling the
y-axis", on page 491.
Remote command:
LAY:ADD? '1',RIGH, DIAG, see LAYout:ADD[:WINDow]? on page 1103
Results:
TRACe<n>[:DATA] on page 1262
Marker Table
Displays a table with the current marker values for the active markers.
This table is displayed automatically if configured accordingly.
(See "Marker Table Display" on page 557).
Tip: To navigate within long marker tables, simply scroll through the entries with your
finger on the touchscreen.
Remote command:
LAY:ADD? '1',RIGH, MTAB, see LAYout:ADD[:WINDow]? on page 1103
Results:
CALCulate<n>:MARKer<m>:X on page 1279
CALCulate<n>:MARKer<m>:Y? on page 1292
Tip: To navigate within long marker peak lists, simply scroll through the entries with
your finger on the touchscreen.
Remote command:
LAY:ADD? '1',RIGH, PEAK, see LAYout:ADD[:WINDow]? on page 1103
Results:
CALCulate<n>:MARKer<m>:X on page 1279
CALCulate<n>:MARKer<m>:Y? on page 1292
Result Summary
Result summaries provide the results of specific measurement functions in a table for
numerical evaluation. The contents of the result summary vary depending on the
selected measurement function. See the description of the individual measurement
functions for details.
Tip: To navigate within long marker tables, simply scroll through the entries with your
finger on the touchscreen.
Remote command:
LAY:ADD? '1',RIGH, RSUM, see LAYout:ADD[:WINDow]? on page 1103
Spectrogram
A spectrogram shows how the spectral density of a signal varies over time. The x-axis
shows the frequency or sweep time, the y-axis shows the measurement time. A third
dimension, the power level, is indicated by different colors. Thus you can see how the
strength of the signal varies over time for different frequencies.
The spectrogram display consists of two diagrams: the standard spectrum result dis-
play (upper diagram) and the spectrogram result display (lower diagram).
For details see Section 8.5.2.1, "Working with spectrograms", on page 631.
Remote command:
LAY:ADD? '1',RIGH, SGR, see LAYout:ADD[:WINDow]? on page 1103
Measurement results can be evaluated in many different ways, for example graphically,
as summary tables, statistical evaluations etc. Each type of evaluation is displayed in a
separate window in the channel tab. Up to 16 individual windows can be displayed per
channel (i.e. per tab). To arrange the diagrams and tables on the screen, the Rohde &
Schwarz SmartGrid function helps you find the target position simply and quickly.
Principally, the layout of the windows on the screen is based on an underlying grid, the
SmartGrid. However, the SmartGrid is dynamic and flexible, allowing for many different
layout possibilities. The SmartGrid functionality provides the following basic features:
● Windows can be arranged in columns or in rows, or in a combination of both.
● Windows can be arranged in up to four rows and four columns.
● Windows are moved simply by dragging them to a new position on the screen, pos-
sibly changing the layout of the other windows, as well.
● All evaluation methods available for the currently selected measurement are dis-
played as icons in the evaluation bar. If the evaluation bar contains more icons
than can be displayed at once on the screen, it can be scrolled vertically. The same
evaluation method can be displayed in multiple windows simultaneously.
● New windows are added by dragging an evaluation icon from the evaluation bar to
the screen. The position of each new window depends on where you drop the eval-
uation icon in relation to the existing windows.
● All display configuration actions are only possible in SmartGrid mode. When Smart-
Grid mode is activated, the evaluation bar replaces the current softkey menu dis-
play. When the SmartGrid mode is deactivated again, the previous softkey menu
display is restored.
● Background information: the smartgrid principle...................................................539
● How to activate smartgrid mode............................................................................541
● How to add a new result window...........................................................................541
● How to close a result window................................................................................542
● How to arrange the result windows....................................................................... 542
SmartGrid display
During any positioning action, the underlying SmartGrid is displayed. Different colors
and frames indicate the possible new positions. The position in the SmartGrid where
you drop the window determines its position on the screen.
The brown area indicates the possible "drop area" for the window, i.e. the area in which
the window can be placed. A blue area indicates the (approximate) layout of the win-
dow as it would be if the icon were dropped at the current position. The frames indicate
the possible destinations of the new window with respect to the existing windows:
above/below, right/left or replacement (as illustrated in Figure 4-33). If an existing win-
dow would be replaced, the drop area is highlighted in a darker color shade.
1
A
B 2 3 2 3 2
C
1
SmartGrid functions
Once the evaluation icon has been dropped, icons in each window provide delete and
move functions.
The "Move" icon allows you to move the position of the window, possibly changing the
size and position of the other displayed windows.
The "Delete" icon allows you to close the window, enlarging the display of the remain-
ing windows.
All display configuration actions are only possible in SmartGrid mode. In SmartGrid
mode the evaluation bar replaces the current softkey menu display. When the Smart-
Grid mode is deactivated again, the previous softkey menu display is restored.
To close the SmartGrid mode and restore the previous softkey menu, select the
"Close" icon, or press any key.
2. Select the icon for the required evaluation method from the evaluation bar.
If the evaluation bar contains more icons than can be displayed at once on the
screen, it can be scrolled vertically. Touch the evaluation bar between the icons
and move it up or down until the required icon appears.
3. Drag the required icon from the evaluation bar to the SmartGrid, which is displayed
in the diagram area, and drop it at the required position. (See "How to arrange the
result windows" on page 107 for more information on positioning the window).
Remote command:
LAYout:ADD[:WINDow]? on page 1103 / LAYout:WINDow<n>:ADD? on page 1107
► To close a window, activate SmartGrid mode and select the "Delete" icon for the
window.
Remote command:
LAYout:REMove[:WINDow] on page 1105 / LAYout:WINDow<n>:REMove
on page 1108
1. Select an icon from the evaluation bar or the "Move" icon for an existing evaluation
window.
Remote command:
LAYout:REPLace[:WINDow] on page 1105 / LAYout:WINDow<n>:REPLace
on page 1108
LAYout:MOVE[:WINDow] on page 1105
When you change the display using touch gestures, however, the corresponding mea-
surement settings are adapted. For example, dragging horizontally in a spectrum dis-
play changes the center frequency. Dragging vertically in a spectrum display changes
the reference level (for absolute scaling). These changes are permanent for the mea-
surement. This behavior is also referred to as measurement zoom, and is active by
default in the new FSW.However, you can also activate it manually for a display that
has already been zoomed graphically. In this case, the temporary changes to the dis-
play are replaced by permanent changes to the measurement settings with the same
effect.
Example:
Assume you have a spectrum display from a spurious emission measurement. You
graphically zoom into the area around a detected spur. If you now activate a measure-
ment zoom, the reference level, the center frequency, the frequency span, and the
scaling settings are adapted so that the results of the measurement now indicate only
the formerly zoomed area around the detected spur.
Two different (graphical) zoom modes are available: single zoom and multiple zoom. A
single zoom replaces the current diagram by a new diagram which displays an
enlarged extract of the trace. This function can be used repetitively until the required
details are visible. In multiple zoom mode, you can enlarge up to four different areas of
the trace simultaneously. An overview window indicates the zoom areas in the original
trace, while the zoomed trace areas are displayed in individual windows. The zoom
areas can be moved and resized any time. The zoom area that corresponds to the indi-
vidual zoom display is indicated in the lower right corner, between the scrollbars.
Single Zoom
A single zoom replaces the current diagram by a new diagram which displays an
enlarged extract of the trace. This function can be used repetitively until the required
details are visible.
Remote command:
DISPlay[:WINDow<n>][:SUBWindow<w>]:ZOOM[:STATe] on page 1241
DISPlay[:WINDow<n>][:SUBWindow<w>]:ZOOM:AREA on page 1240
Multi-Zoom
In multiple zoom mode, you can enlarge several different areas of the trace simultane-
ously. An overview window indicates the zoom areas in the original trace, while the
zoomed trace areas are displayed in individual windows. The zoom area that corre-
sponds to the individual zoom display is indicated in the lower right corner, between the
scrollbars.
Remote command:
DISPlay[:WINDow<n>][:SUBWindow<w>]:ZOOM:MULTiple<zn>[:STATe]
on page 1243
DISPlay[:WINDow<n>][:SUBWindow<w>]:ZOOM:MULTiple<zn>:AREA
on page 1242
Measurement Zoom
As opposed to the graphical zoom, which is merely a visual tool, the measurement
zoom adapts the measurement settings such that the data you are interested in is dis-
played in the required detail. In measurement zoom mode, you can change the display
using touch gestures. This is the default operating mode of the FSW.
For details on touch gestures see "Operating Basics" in the FSW Getting Started man-
ual.
Note: The measurement settings are adapted to practical values based on a suitable
grid for the current settings, rather than to unwieldy values that reflect precisely the
pixel you happen to tap.
If the measurement zoom leads to undesirable results, you can easily return to the
original measurement settings using the "UNDO" function.
When you select the "Measurement Zoom" icon, then tap in a diagram, a dotted rect-
angle is displayed which you can drag to define the zoom area. This allows you to
define the zoom area more precisely than by spreading two fingers in the display.
The measurement zoom function provides further options in a context-sensitive menu,
which is displayed when you tap the icon for about a second (or right-click it). These
options concern the behavior of the firmware for subsequent touch gestures on the
screen. Note that these settings remain unchanged after a channel preset.
Restores the original display, that is, the originally calculated displays for the entire
capture buffer, and closes all zoom windows.
Note: This function only restores graphically zoomed displays. Measurement zooms,
for which measurement settings were adapted, are recalculated based on the adapted
measurement settings. In this case, the zoomed display is maintained.
Remote command:
Single zoom:
DISPlay[:WINDow<n>][:SUBWindow<w>]:ZOOM[:STATe] on page 1241
Multiple zoom:
DISPlay[:WINDow<n>][:SUBWindow<w>]:ZOOM:MULTiple<zn>[:STATe]
on page 1243 (for each multiple zoom window)
Data Zoom
Decreases the amount of data to be evaluated in the result display (analysis region or
hop/chirp) and re-evaluates the new data, thus enlarging the display of the remaining
data.
ALL result displays based on the same data (analysis region or hop/chirp) are updated.
Currently, this function is only available in the Transient Analysis application.
Tip: result tables are also re-evaluated for each data zoom, which can take some time.
Close the result tables during a data shift/zoom to improve the screen update speed.
The remote commands required to zoom into a display are described in Section 13.8.1,
"Zooming into the display", on page 1240.
The following tasks are described here:
● "To zoom into the diagram at one position" on page 547
● "To return to original display" on page 548
● "To zoom into multiple positions in the diagram" on page 548
● "To maintain a zoomed display permanently" on page 549
For information on how to zoom into a diagram using touch gestures and change the
display permanently, see Section 4.5.5, "Touchscreen gestures", on page 99.
2. Tap and drag your finger in the diagram to select the area to be enlarged. The
selected area is indicated by a dotted rectangle.
When you leave the touchscreen, the diagram is replaced by the zoomed trace
area.
2. Select the first area in the diagram to be enlarged as described in "To zoom into
the diagram at one position" on page 547. The selected area is indicated by a dot-
ted rectangle.
When you have completed your selection, the original trace is shown in an over-
view diagram with the selected area indicated by a dotted rectangle. The zoomed
trace area is displayed in a separate window (see Figure 8-4.
3.
5. Repeat these steps, if necessary, to zoom into further trace areas (up to four).
● Tap and drag one finger in the diagram to select the area to be enlarged. The
selected area is indicated by a dotted rectangle.
The measurement settings are adapted as required to obtain the zoomed result
display.
● Basics on markers.................................................................................................550
● Marker settings......................................................................................................553
● Marker search settings and positioning functions................................................. 559
● Marker (measurement) functions.......................................................................... 567
● How to work with markers..................................................................................... 588
● Measurement example: measuring harmonics using marker functions................ 591
Some background knowledge on marker settings and functions is provided here for a
better understanding of the required configuration settings.
Markers are used to mark points on traces, to read out measurement results and to
select a display section quickly. FSW provides 17 markers per display window. In the
Spectrum application, the same markers are displayed in all windows.
● To set individual markers very quickly, use the softkeys in the "Marker" menu.
● To set up several markers at once, use the "Marker" dialog box.
● To position the selected marker to a special value, use the softkeys in the "Marker
To" menu.
● The easiest way to work with markers is using a mouse. Simply drag the marker
and drop it at the required position.
● When you select a marker in a diagram, a vertical line is displayed which indicates
the marker's current x-value.
● Alternatively, change the position of the selected marker using the rotary knob. By
default, the marker is moved from one pixel to the next. If you need to position the
marker more precisely, change the step size to move from one sweep point to the
next (General Marker Setting).
● You can also set an active marker to a new position by defining its x-position
numerically. When you select the softkey for a marker, an edit dialog box is dis-
played.
● The most commonly required marker settings and functions are also available as
softkeys or via the context menu. Tap the marker on the touch screen and hold
your finger for about 2 seconds until the context menu is opened, then select the
required entry.
● Softkeys for active markers (displayed on the screen) are highlighted blue. The
softkey for the currently selected marker (for which functions are performed) is
highlighted orange.
● To determine more sophisticated marker results, use the special functions in the
"Marker Function" dialog box.
● Marker types......................................................................................................... 551
● Activating markers.................................................................................................552
● Marker results....................................................................................................... 552
All markers can be used either as normal markers or delta markers. A normal marker
indicates the absolute signal value at the defined position in the diagram. A delta
marker indicates the value of the marker relative to the specified reference marker (by
default marker 1).
In addition, special functions can be assigned to the individual markers. The availability
of special marker functions depends on whether the measurement is performed in the
frequency or time domain, and on the type of measurement.
Temporary markers are used in addition to the markers and delta markers to analyze
the measurement results for special marker functions. They disappear when the asso-
ciated function is deactivated.
Only active markers are displayed in the diagram and in the marker table.
Active markers are indicated by a highlighted softkey.
By default, marker 1 is active and positioned on the maximum value (peak) of trace 1
as a normal marker. If several traces are displayed, the marker is set to the maximum
value of the trace which has the lowest number and is not frozen (View mode). The
next marker to be activated is set to the frequency of the next lower level (next peak)
as a delta marker; its value is indicated as an offset to marker 1.
A marker can only be activated when at least one trace in the corresponding window is
visible. If a trace is switched off, the corresponding markers and marker functions are
also deactivated. If the trace is switched on again, the markers along with coupled
functions are restored to their original positions, provided the markers have not been
used on another trace.
Normal markers point to a trace point on the x-axis and display the associated numeric
value for that trace point. Delta markers indicate an offset between the level at the
delta marker position and the level at the position of the assigned reference marker, in
dB.
Note that markers placed on the start and stop values of the x-axis indicate the y-val-
ues of the first and last trace point, respectively. For details see "X-value of the sweep
point" on page 619.
Signal count markers determine the frequency of a signal at the marker position very
accurately.
The results can be displayed directly within the diagram area or in a separate table. By
default, the first two active markers are displayed in the diagram area. If more markers
are activated, the results are displayed in a marker table.
Frame Spectrogram frame the marker is positioned in. Displayed only when the Spectro-
gram is displayed.
The markers are distributed among 3 tabs for a better overview. By default, the first
marker is defined as a normal marker, whereas all others are defined as delta markers
with reference to the first marker. All markers are assigned to trace 1, but only the first
marker is active.
Selected Marker.......................................................................................................... 554
Marker State................................................................................................................554
Marker Position X-value.............................................................................................. 555
Frame (Spectrogram only).......................................................................................... 555
Marker Type................................................................................................................ 555
Reference Marker....................................................................................................... 555
Linking to Another Marker........................................................................................... 556
Assigning the Marker to a Trace................................................................................. 556
Select Marker.............................................................................................................. 556
All Markers Off.............................................................................................................557
Selected Marker
Marker name. The marker which is currently selected for editing is highlighted orange.
Remote command:
Marker selected via suffix <m> in remote commands.
Marker State
Activates or deactivates the marker in the diagram.
Remote command:
CALCulate<n>:MARKer<m>[:STATe] on page 1278
CALCulate<n>:DELTamarker<m>[:STATe] on page 1275
Marker Type
Toggles the marker type.
The type for marker 1 is always "Normal", the type for delta marker 1 is always "Delta".
These types cannot be changed.
Note: If normal marker 1 is the active marker, switching the "Mkr Type" activates an
additional delta marker 1. For any other marker, switching the marker type does not
activate an additional marker, it only switches the type of the selected marker.
"Normal" A normal marker indicates the absolute value at the defined position
in the diagram.
"Delta" A delta marker defines the value of the marker relative to the speci-
fied reference marker (marker 1 by default).
Remote command:
CALCulate<n>:MARKer<m>[:STATe] on page 1278
CALCulate<n>:DELTamarker<m>[:STATe] on page 1275
Reference Marker
Defines a marker as the reference marker which is used to determine relative analysis
results (delta marker values).
If the reference marker is deactivated, the delta marker referring to it is also deactiva-
ted.
If a fixed reference point is configured (see "Defining a Fixed Reference"
on page 558), the reference point ("FXD") can also be selected instead of another
marker.
Remote command:
CALCulate<n>:DELTamarker<m>:MREFerence on page 1275
Select Marker
The "Select Marker" function opens a dialog box to select and activate or deactivate
one or more markers quickly.
Remote command:
CALCulate<n>:MARKer<m>[:STATe] on page 1278
CALCulate<n>:DELTamarker<m>[:STATe] on page 1275
Some general marker settings allow you to influence the marker behavior for all mark-
ers.
"Auto" (Default) If more than two markers are active, the marker table is dis-
played automatically.
If Marker Info is active, the marker information for up to two markers
is displayed in the diagram area.
Remote command:
DISPlay[:WINDow<n>]:MTABle on page 1280
Marker Info
Turns the marker information displayed in the diagram on and off.
Remote command:
DISPlay[:WINDow<n>]:MINFo[:STATe] on page 1280
Marker Stepsize
Defines the size of the steps that the marker position is moved using the rotary knob.
"Standard" The marker position is moved in steps of (Span/1000), which corre-
sponds approximately to the number of pixels for the default display
of 1001 sweep points. This setting is most suitable to move the
marker over a larger distance.
"Sweep The marker position is moved from one sweep point to the next. This
Points" setting is required for a very precise positioning if more sweep points
are collected than the number of pixels that can be displayed on the
screen. It is the default mode.
Remote command:
CALCulate<n>:MARKer<m>:X:SSIZe on page 1280
Peak Search sets the fixed reference marker to the current maximum value of the
trace assigned to marker 1.
If activated, the fixed reference marker ("FXD") can also be selected as a Reference
Marker instead of another marker.
Remote command:
CALCulate<n>:DELTamarker<m>:FUNCtion:FIXed[:STATe] on page 1303
CALCulate<n>:DELTamarker<m>:FUNCtion:FIXed:RPOint:Y on page 1303
CALCulate<n>:DELTamarker<m>:FUNCtion:FIXed:RPOint:X on page 1302
CALCulate<n>:DELTamarker<m>:FUNCtion:FIXed:RPOint:MAXimum[:PEAK]
on page 1302
For Spectrograms, special marker settings are available, see Section 8.3.3.2, "Marker
search settings for spectrograms", on page 562.
Exclude LO
If activated, restricts the frequency range for the marker search functions.
"On" The minimum frequency included in the peak search range is ≥ 5 ×
resolution bandwidth (RBW).
Due to the interference by the first local oscillator to the first inter-
mediate frequency at the input mixer, the LO is represented as a sig-
nal at 0 Hz. To avoid the peak marker jumping to the LO signal at 0
Hz, this frequency is excluded from the peak search.
"Off" No restriction to the search range. The frequency 0 Hz is included in
the marker search functions.
Remote command:
CALCulate<n>:MARKer<m>:LOEXclude on page 1281
Peak Excursion
Defines the minimum level value by which a signal must rise or fall so that it is identi-
fied as a maximum or a minimum by the search functions.
Entries from 0 dB to 80 dB are allowed; the resolution is 0.1 dB. The default setting for
the peak excursion is 6 dB.
For Analog Modulation Analysis, the unit and value range depend on the selected
result display type.
For more information, see Section 8.3.4.8, "Marker peak list", on page 584.
Remote command:
CALCulate<n>:MARKer<m>:PEXCursion on page 1281
Search Limits
The search results can be restricted by limiting the search area or adding search con-
ditions.
Exclude LO
If activated, restricts the frequency range for the marker search functions.
"On" The minimum frequency included in the peak search range is ≥ 5 ×
resolution bandwidth (RBW).
Due to the interference by the first local oscillator to the first inter-
mediate frequency at the input mixer, the LO is represented as a sig-
nal at 0 Hz. To avoid the peak marker jumping to the LO signal at 0
Hz, this frequency is excluded from the peak search.
"Off" No restriction to the search range. The frequency 0 Hz is included in
the marker search functions.
Remote command:
CALCulate<n>:MARKer<m>:LOEXclude on page 1281
Peak Excursion
Defines the minimum level value by which a signal must rise or fall so that it is identi-
fied as a maximum or a minimum by the search functions.
Entries from 0 dB to 80 dB are allowed; the resolution is 0.1 dB. The default setting for
the peak excursion is 6 dB.
For Analog Modulation Analysis, the unit and value range depend on the selected
result display type.
For more information, see Section 8.3.4.8, "Marker peak list", on page 584.
Remote command:
CALCulate<n>:MARKer<m>:PEXCursion on page 1281
For EMI measurements, these functions are not available; use Automatic Peak Search
instead (see Section 6.13.4.2, "EMI final measurement configuration", on page 347).
Remote command:
CALCulate<n>:MARKer<m>:MAXimum:AUTO on page 1285
CALCulate<n>:MARKer<m>:MINimum:AUTO on page 1287
Search Limits
The search results can be restricted by limiting the search area or adding search con-
ditions.
Peak Search
Sets the selected marker/delta marker to the maximum of the trace. If no marker is
active, marker 1 is activated.
For spectrogram displays, define which frame the peak is to be searched in.
Remote command:
CALCulate<n>:MARKer<m>:MAXimum[:PEAK] on page 1286
CALCulate<n>:DELTamarker<m>:MAXimum[:PEAK] on page 1289
Search Minimum
Sets the selected marker/delta marker to the minimum of the trace. If no marker is
active, marker 1 is activated.
For spectrogram displays, define which frame the minimum is to be searched in.
Remote command:
CALCulate<n>:MARKer<m>:MINimum[:PEAK] on page 1288
CALCulate<n>:DELTamarker<m>:MINimum[:PEAK] on page 1290
The remote commands required to define these settings are described in Sec-
tion 13.8.3, "Working with markers", on page 1272.
● Precise frequency (signal count) marker...............................................................568
● Measuring noise density (noise meas marker)..................................................... 569
● Phase noise measurement marker....................................................................... 572
● Measuring characteristic bandwidths (n db down marker)....................................575
● Fixed reference marker......................................................................................... 577
● Measuring the power in a channel (band power marker)......................................578
Access: "Overview" > "Analysis" > "Marker Functions" > "Select Marker Function" >
"Signal Count" > "Signal Count Config"
Or: [MKR FUNC] > "Select Marker Function" > "Signal Count" > "Signal Count Config"
A normal marker determines the position of the point on the trace and indicates the sig-
nal frequency at this position. The trace, however, contains only a limited number of
points. Depending on the selected span, each trace point can contain many measure-
ment values. Thus, the frequency resolution of each trace point is limited.
(See also Section 7.5.1.8, "How much data is measured: sweep points and sweep
count", on page 499).
Frequency resolution is further restricted by the RBW and sweep time settings.
To determine the frequency of a signal point accurately without changing the sweep
settings, the FSW is equipped with a signal counter. The signal counter sets the RF to
the current marker position, then counts the zero crossings of the IF (thus the term sig-
nal counter) and derives the precise frequency value.
To determine the frequency accurately using the signal counter function, the marker
must be sufficiently close to the actual signal (for a 3-dB Gauss filter, the delta must be
less than 2*RBW). Usually, the marker peak function detects a trace point that is close
enough. However, for a large span or a small number of sweep points, the result can
be inaccurate.
Signal counting can be performed explicitly at the current marker position ("Signal
Count" marker function), or implicitly by the FSW for certain functions.
Signal counting is only possible while the instrument is not sweeping. Thus, to perform
a signal count for a marker, the sweep is stopped at the marker position. The fre-
quency is determined with the desired resolution and then the sweep is allowed to con-
tinue.
Remote commands:
"Example: performing a highly accurate frequency measurement using the signal count
marker" on page 1331
CALCulate<n>:MARKer<m>:COUNt on page 1319
CALCulate<n>:MARKer<m>:COUNt:RESolution on page 1320
Signal Count Marker State.......................................................................................... 569
Resolution................................................................................................................... 569
Resolution
Defines the resolution with which the signal is analyzed around the reference marker 1.
Remote command:
CALCulate<n>:MARKer<m>:COUNt:RESolution on page 1320
Access: "Overview" > "Analysis" > "Marker Functions" > "Select Marker Function" >
"Noise Measurement" > "Noise Meas Config"
Or: [MKR FUNC] > "Select Marker Function" > "Noise Measurement" > "Noise Meas
Config"
Using the noise measurement marker function, the noise power density is measured at
the position of the marker. In the time domain mode, all points of the trace are used to
determine the noise power density. When measurements are performed in the fre-
quency domain, eight points to the right and left of the marker (if available) are used for
the measurement to obtain a stable result.
Result display
Noise density is the noise referred to a bandwidth of 1 Hz. With logarithmic amplitude
units (dBm, dBmV, dBmµV, dBµA), the noise power density is output in dBm/Hz, i.e. as
the level in 1 Hz bandwidth with reference to 1 mW. With linear amplitude units (V, A,
W), the noise voltage density is analyzed in µV/√Hz; the noise current density in µA/
√Hz; the noise power density in µW/√Hz.
The result is indicated as the function result in the Marker Table.
Prerequisite settings
The following settings are required to obtain correct values:
● Detector: Sample or RMS
● Video bandwidth:
≤ 0.1 resolution bandwidth with sample detector
≥ 3 x resolution bandwidth with RMS detector
● Trace averaging:
In the default setting, the FSW uses the sample detector for the noise function.
With the sample detector, you can set the trace to "Average" mode to stabilize the
measured values. When the RMS detector is used, trace averaging produces noise
levels that are too low and cannot be corrected. Instead, increase the sweep time
to obtain stable measurement results.
Correction factors
The FSW uses the following correction factors to analyze the noise density from the
marker level:
● Since the noise power is indicated with reference to 1 Hz bandwidth, the bandwidth
correction value is deducted from the marker level. It is 10 x lg (1 Hz/BWNoise),
where BWNoise is the noise or power bandwidth of the set resolution filter (RBW).
● RMS detector: With the exception of bandwidth correction, no further corrections
are required since this detector already indicates the power for each point of the
trace.
● Sample detector: As a result of video filter averaging and trace averaging, 1.05 dB
is added to the marker level. This is the difference between the average value and
the RMS value of white noise. With a logarithmic level axis, 1.45 dB is added addi-
tionally. Logarithmic averaging is thus fully taken into account, which yields a value
that is 1.45 dB lower than that of linear averaging.
● To allow for a more stable noise display, eight trace points on each side of the mea-
surement frequency are averaged.
● For span > 0, the measured values are averaged versus time (after a sweep).
The FSW noise figure can be calculated from the measured power density level. It is
calculated by deducting the set RF attenuation (RF Att) from the displayed noise level
and adding 174 to the result.
The individual marker settings correspond to those defined in the "Marker" dialog box
(see Section 8.3.2.1, "Individual marker setup", on page 553). Any settings to the
marker state or type changed in the "Marker Function" dialog box are also changed in
the "Marker" dialog box and vice versa.
Remote commands:
"Example: measuring noise density" on page 1327
CALCulate<n>:MARKer<m>:FUNCtion:NOISe[:STATe] on page 1308
CALCulate<n>:MARKer<m>:FUNCtion:NOISe:RESult? on page 1308
Marker State................................................................................................................571
Marker Type................................................................................................................ 571
Noise Measurement State...........................................................................................572
Switching All Noise Measurement Off......................................................................... 572
Marker State
Activates or deactivates the marker in the diagram.
Remote command:
CALCulate<n>:MARKer<m>[:STATe] on page 1278
CALCulate<n>:DELTamarker<m>[:STATe] on page 1275
Marker Type
Toggles the marker type.
The type for marker 1 is always "Normal", the type for delta marker 1 is always "Delta".
These types cannot be changed.
Note: If normal marker 1 is the active marker, switching the "Mkr Type" activates an
additional delta marker 1. For any other marker, switching the marker type does not
activate an additional marker, it only switches the type of the selected marker.
"Normal" A normal marker indicates the absolute value at the defined position
in the diagram.
"Delta" A delta marker defines the value of the marker relative to the speci-
fied reference marker (marker 1 by default).
Remote command:
CALCulate<n>:MARKer<m>[:STATe] on page 1278
CALCulate<n>:DELTamarker<m>[:STATe] on page 1275
Access: "Overview" > "Analysis" > "Marker Functions" > "Phase Noise" > "Phase
Noise Config"
Or: [MKR FUNC] > "Select Marker Function" > "Phase Noise" > "Phase Noise Config"
For each of the 16 markers, you can activate a phase noise measurement.
Phase noise is unintentional modulation of a carrier; it creates frequencies next to the
carrier frequency. A phase noise measurement consists of noise density measure-
ments at defined offsets from the carrier; the results are given in relation to the carrier
level (dBc). The phase noise marker function measures the noise power at the delta
markers referred to 1 Hz bandwidth. Marker 1 is used as the reference for the phase
noise measurement. By default, the current frequency and level of marker 1 are used
as the fixed reference marker. However, you can start a peak search to use the current
signal peak as the reference point, or you can define a reference point manually.
The reference point for the phase noise measurement is fixed. After phase noise mea-
surement is started, you can set the reference level or the center frequency so that the
carrier is outside the displayed frequency range. You can also activate a notch filter to
suppress the carrier.
Remote commands:
CALCulate<n>:MARKer<m>:FUNCtion:PNOise[:STATe] on page 1311
CALCulate<n>:MARKer<m>:FUNCtion:PNOise:RESult? on page 1311
Phase Noise Measurement State............................................................................... 574
Defining Reference Point............................................................................................ 575
Switching All Phase Noise Measurements Off............................................................ 575
If activated, the delta markers display the phase noise measured at defined offsets
from the reference position.
Remote command:
CALCulate<n>:DELTamarker<m>:FUNCtion:PNOise[:STATe] on page 1310
CALCulate<n>:DELTamarker<m>:FUNCtion:PNOise:RESult? on page 1309
Access: "Overview" > "Analysis" > "Marker Functions" > "n dB down" > "n dB Down
Config"
Or: [MKR FUNC] > "Select Marker Function" > "n dB down" > "n dB Down Config"
When characterizing the shape of a signal, the bandwidth at a specified offset from its
peak level is often of interest. The offset is specified as a relative decrease in ampli-
tude of n dB. To measure this bandwidth, you could use several markers and delta
markers and determine the bandwidth manually. However, using the n dB down marker
function makes the task very simple and quick.
The n dB down marker function uses the current value of marker 1 as the reference
point. It activates two temporary markers T1 and T2 located on the signal, whose level
is n dB below the level of the reference point. Marker T1 is placed to the left and
marker T2 to the right of the reference marker. The default setting for n is 3 dB, but it
can be changed.
If a positive offset is entered, the markers T1 and T2 are placed below the active refer-
ence point. If a negative value is entered (for example for notch filter measurements),
the markers T1 and T2 are placed above the active reference point.
Label Description
ndB down Bw / Determined bandwidth or pulse width (zero span) at the offset
PWid
If the required position for the temporary markers cannot be determined uniquely, for
example due to noise, dashes are displayed as a result.
Remote commands:
CALCulate<n>:MARKer<m>:FUNCtion:NDBDown:STATe on page 1318
n dB down Value
Defines the delta level from the reference marker 1 used to determine the bandwidth or
time span.
Remote command:
CALCulate<n>:MARKer<m>:FUNCtion:NDBDown:FREQuency? on page 1316
CALCulate<n>:MARKer<m>:FUNCtion:NDBDown:TIME? on page 1318
Access: "Overview" > "Analysis" > "Marker Functions" > "Reference Fixed"
Or: [MKR FUNC] > "Select Marker Function" > "Reference Fixed"
Instead of using a reference marker that may vary its position depending on the mea-
surement results, a fixed reference marker can be defined for trace analysis. Once
positioned, the reference marker does not move during subsequent sweeps unless you
explicitely move it manually.
When you select this marker function, a vertical and a horizontal red display line are
displayed, marked as "FXD". A normal marker is activated and set to the peak value
and a delta marker to the next peak. The fixed reference marker is set to the position of
the normal marker at the peak value. The delta marker refers to the fixed reference
marker.
You can move the position of the fixed reference marker graphically by dragging the
display lines, or numerically by entering values for the marker position and level.
Remote commands:
"Example: using a fixed reference marker" on page 1326
CALCulate<n>:DELTamarker<m>:FUNCtion:FIXed[:STATe] on page 1303
CALCulate<n>:DELTamarker<m>:FUNCtion:FIXed:RPOint:X on page 1302
CALCulate<n>:DELTamarker<m>:FUNCtion:FIXed:RPOint:Y on page 1303
Access: "Overview" > "Analysis" > "Marker Functions" > "Band Power" > "Band Power
Config"
or: [MKR FUNC] > "Select Marker Function" > "Band Power"
To determine the noise power in a transmission channel, you can use a noise marker
and multiply the result with the channel bandwidth. However, the results are only accu-
rate for flat noise.
Band power markers allow you to measure the integrated power for a defined span
(band) around a marker (similar to ACP measurements). By default, 5 % of the current
span is used. The span is indicated by limit lines in the diagram. You can easily change
the span by moving the limit lines in the diagram. They are automatically aligned sym-
metrically to the marker frequency. They are also moved automatically if you move the
marker on the screen.
The results can be displayed either as a power (dBm) or density (dBm/Hz) value and
are indicated in the "marker table" for each band power marker.
Band power markers are only available for standard frequency measurements (not
zero span) in the Spectrum and Spectrum application. In Analog Modulation Analysis
with AM, FM, or PM spectrum results, this marker function does not determine a power
value, but rather the deviation within the specified span.
For the I/Q Analyzer application, band power markers are only available for Spectrum
displays.
The entire band must lie within the display. If it is moved out of the display, the result
cannot be calculated (indicated by "- - -" as the "Function Result"). However, the width
of the band is maintained so that the band power can be calculated again when it
returns to the display.
All markers can be defined as band power markers, each with a different span. When a
band power marker is activated, if no marker is active yet, marker 1 is activated. Other-
wise, the currently active marker is used as a band power marker (all other marker
functions for this marker are deactivated).
If the detector mode for the marker trace is set to "Auto", the RMS detector is used.
The individual marker settings correspond to those defined in the "Marker" dialog box
(see Section 8.3.2.1, "Individual marker setup", on page 553). Any settings to the
marker state or type changed in the "Marker Function" dialog box are also changed in
the "Marker" dialog box and vice versa.
Remote commands:
"Example: measuring the power in a channel using band power markers"
on page 1329
CALCulate<n>:MARKer<m>:FUNCtion:BPOWer[:STATe] on page 1313
CALCulate<n>:MARKer<m>:FUNCtion:BPOWer:RESult? on page 1312
Band Power Measurement State................................................................................ 580
Span............................................................................................................................581
Power Mode................................................................................................................ 581
Switching All Band Power Measurements Off.............................................................581
Remote command:
CALCulate<n>:MARKer<m>:FUNCtion:BPOWer[:STATe] on page 1313
CALCulate<n>:DELTamarker<m>:FUNCtion:BPOWer[:STATe] on page 1315
Span
Defines the span (band) around the marker for which the power is measured.
The span is indicated by lines in the diagram. You can easily change the span by mov-
ing the limit lines in the diagram. They are automatically aligned symmetrically to the
marker frequency. They are also moved automatically if you move the marker on the
screen.
Remote command:
CALCulate<n>:MARKer<m>:FUNCtion:BPOWer:SPAN on page 1313
CALCulate<n>:DELTamarker<m>:FUNCtion:BPOWer:SPAN on page 1315
Power Mode
Defines the mode of the power measurement result.
For Analog Modulation Analysis, the power mode is not editable for AM, FM, or PM
spectrum results. In this case, the marker function does not determine a power value,
but rather the deviation within the specified span.
"Power" The result is an absolute power level.
The power unit depends on the Unit setting.
"Relative This setting is only available for a delta band power marker.
Power" The result is the difference between the absolute power in the band
around the delta marker and the absolute power for the reference
marker (see "Reference Marker" on page 345). The powers are sub-
tracted logarithmically, so the result is a dB value.
[Relative band power (Delta2) in dB] = [absolute band power (Delta2)
in dBm] - [absolute (band) power of reference marker in dBm]
For details see "Relative band power markers" on page 579
"Density" The result is a power level in relation to the bandwidth, displayed in
dBm/Hz.
Remote command:
CALCulate<n>:MARKer<m>:FUNCtion:BPOWer:MODE on page 1312
CALCulate<n>:DELTamarker<m>:FUNCtion:BPOWer:MODE on page 1314
8.3.4.7 Demodulating marker values and providing audio output (marker demodulation)
Access: "Overview" > "Analysis" > "Marker Functions" > "Select Marker Function" >
"Marker Demodulation" > "Marker Demod Config"
Or: [MKR FUNC] > "Select Marker Function" > "Marker Demodulation" > "Marker
Demod Config"
The FSW provides demodulators for AM, FM and PM signals. The demodulation
marker function sends the demodulated data at the current marker frequency to the
audio output. Thus, a displayed signal can be identified acoustically with the help of the
internal loudspeaker or with headphones.
This function is not available for Spectrum Emission Mask measurements or measure-
ments on I/Q-based data.
The sweep stops at the frequency determined by marker 1 for the selected time and
the RF signal is demodulated in a bandwidth that corresponds to the RBW. Alterna-
tively, demodulation can be activated continuously, i.e. audio output occurs regardless
of the marker position and the marker stop time. For measurements in the time domain
(zero span), demodulation is always continuous.
Optionally, a minimum level ("Squelch Level") can be defined so that the signal is only
demodulated when it exceeds the set level. This is useful during continuous demodula-
tion to avoid listening to noise.
The squelch function activates the video trigger function (see "Video" on page 517) and
deactivates any other trigger or gating settings. The squelch level and trigger level are
set to the same value. The trigger source in the channel bar is indicated as "SQL" for
squelch. The squelch level is indicated by a red line in the diagram.
Remote commands:
Section 13.8.3.15, "Programming examples for using markers and marker functions",
on page 1323
Marker Demodulation State........................................................................................ 583
Continuous Demodulation...........................................................................................583
Marker Stop Time........................................................................................................583
Modulation...................................................................................................................583
Squelch....................................................................................................................... 583
Squelch Level..............................................................................................................584
Continuous Demodulation
If activated, the signal is demodulated continuously and sent to the audio output,
instead of stopping the sweep at the marker frequency of marker 1 and demodulating
there for the configured marker stop time. This allows you to monitor the frequency
range acoustically (assuming the sweep time is long enough).
In FFT mode, "Continuous Demodulation" is not available. The sweep always stops at
the frequency of marker 1.
For EMI measurements, during the initial peak search, demodulation is not stopped at
the determined markers, even if "Continuous Demodulation" is disabled.
During the final measurement, demodulation is always performed at the detected peak
marker positions only (for the defined dwell time), regardless of the "Continuous
Demodulation" setting.
Remote command:
CALCulate<n>:MARKer<m>:FUNCtion:DEModulation:CONTinuous
on page 1321
Modulation
Defines the demodulation mode for output. The default setting is AM.
Remote command:
CALCulate<n>:MARKer<m>:FUNCtion:DEModulation:SELect on page 1322
Squelch
Activates or deactivates the squelch function. If activated, the audible AF is cut off
below a defined threshold level. Thus, you avoid hearing noise at the audio output
when no signal is available.
The squelch function activates the video trigger function (see "Video" on page 517) and
deactivates any other trigger or gating settings. The squelch level and trigger level are
set to the same value. The trigger source in the channel bar is indicated as "SQL" for
squelch. The squelch level is indicated by a red line in the diagram.
The trigger source in the channel bar is indicated as "SQL" for squelch. The squelch
level is indicated by a red line in the diagram.
Remote command:
[SENSe:]DEMod:SQUelch[:STATe] on page 1323
Squelch Level
Defines the level threshold below which the audible AF is cut off if squelching is
enabled. The video trigger level is set to the same value.
The squelch level is indicated by a red line in the diagram.
Remote command:
[SENSe:]DEMod:SQUelch:LEVel on page 1322
Access: "Overview" > "Analysis" > "Marker Functions" > "Marker Peak List"
Or: [MKR FUNC] > "Marker Peak List"
A common measurement task is to determine peak values, i.e. maximum or minimum
signal levels. The FSW provides various peak search functions and applications:
● Setting a marker to a peak value once (Peak Search)
● Searching for a peak value within a restricted search area (Search Limits)
● Creating a "marker table" with all or a defined number of peak values for one
sweep ("Marker Peak List")
● Updating the marker position to the current peak value automatically after each
sweep (Auto Peak Search)
● Creating a fixed reference marker at the current peak value of a trace (Fixed Refer-
ence)
The following table lists the peaks as indicated by the marker numbers in the diagram
above, as well as the minimum decrease in amplitude to either side of the peak:
1 80 dB
2 80 dB
3 55 dB
4 39 dB
5 32 dB
To eliminate the smaller peaks M3, M4 and M5 in the example above, a peak excur-
sion of at least 60 dB is required. In this case, the amplitude must rise at least 60 dB
before falling again before a peak is detected.
measurement result, keeps the delta frequency value. Therefore, the phase noise
measurement leads to reliable results in a certain offset although the source is drifting.
Remote commands:
"Example: obtaining a marker peak list" on page 1327
CALCulate<n>:MARKer<m>:FUNCtion:FPEaks:STATe on page 1306
TRAC? LIST,
See TRACe<n>[:DATA] on page 1262
Peak List State............................................................................................................ 587
Sort Mode....................................................................................................................587
Maximum Number of Peaks........................................................................................587
Peak Excursion........................................................................................................... 587
Display Marker Numbers.............................................................................................587
Export Peak List.......................................................................................................... 587
Sort Mode
Defines whether the peak list is sorted according to the x-values or y-values. In either
case, the values are sorted in ascending order.
Remote command:
CALCulate<n>:MARKer<m>:FUNCtion:FPEaks:SORT on page 1306
Peak Excursion
Defines the minimum level value by which a signal must rise or fall so that it is identi-
fied as a maximum or a minimum by the search functions.
Entries from 0 dB to 80 dB are allowed; the resolution is 0.1 dB. The default setting for
the peak excursion is 6 dB.
For Analog Modulation Analysis, the unit and value range depend on the selected
result display type.
For more information, see Section 8.3.4.8, "Marker peak list", on page 584.
Remote command:
CALCulate<n>:MARKer<m>:PEXCursion on page 1281
Access: "Overview" > "Analysis" > "Marker Functions" > "All Functions Off"
Or: [MKR FUNC] > "All Functions Off"
All special marker functions can be deactivated in one step.
Remote command:
CALCulate<n>:MARKer<m>:FUNCtion:BPOWer:AOFF on page 1312
CALCulate<n>:MARKer<m>:FUNCtion:NOISe:AOFF on page 1307
CALCulate<n>:MARKer<m>:FUNCtion:PNOise:AOFF on page 1310
The following step-by-step instructions demonstrate in detail how to work with markers.
● How to analyze a signal point in detail.................................................................. 588
● How to use a fixed reference marker.................................................................... 589
● How to output the demodulated signal accoustically............................................ 589
● How to export a peak list.......................................................................................590
Step-by-step instructions on working with markers are provided here. For details on
individual functions and settings see Section 8.3.2, "Marker settings", on page 553.
The remote commands required to perform these tasks are described in Sec-
tion 13.8.3, "Working with markers", on page 1272.
When you need to analyze a characteristic point in the signal in more detail, the follow-
ing procedure can be helpful:
2. If the required signal point is not the maximum, continue the peak search to one of
the subsequent maxima or minima:
a) Press [Mkr ->].
b) Select "Next Peak" or "Next Min".
c) If necessary, change the search settings by selecting "Search Config".
3. Center the display around the determined signal point by setting the marker value
to the center frequency. Select "Center = Mkr Freq".
By default, delta markers refer to marker 1. However, they can also refer to a fixed ref-
erence marker.
2. For the active delta marker that is to refer to the fixed reference marker, select
"FXD" from the "Reference Marker" list.
The delta marker indicates the offset of the current trace value at the marker posi-
tion from the fixed reference value.
For long sweep times you may wish to monitor a measurement accoustically rather
than visually to determine when a certain signal level is reached.
6. Define how long you want to hear the output signal when the marker value is
reached by entering the duration in the "Marker Stop Time" field.
Alternatively, the audio signal can be output continuously, regardless of the marker
value; in this case, set "Continuous Demodulation" to "On".
8. To avoid listening to noise during continuous output, set "Squelch" to "On" and
define the signal level below which the signal is ignored ("Squelch").
10. CAUTION! Risk of hearing damage. To protect your hearing, make sure that the
volume setting is not too high before putting on the headphones.
Plug your headphones into the PHONES connector on the front panel of the FSW.
11. Adjust the volume using the rotary knob next to the PHONES connector.
During the next or currently running measurement, when the sweep reaches the
marker position, the demodulated signal is output as an audio signal via the head-
phones for the given duration. Or, depending on the configuration, the demodula-
ted signal is continuously output via the headphones, if the signal level exceeds the
squelch level.
You can save the results of a marker peak list to an ASCII file.
3. Configure the peak search and list settings as described in Section 8.3.4.8,
"Marker peak list", on page 584.
5. Press [RUN SINGLE] to perform a single sweep measurement and create a marker
peak list.
6. Select "Marker Peak List" to display the "Marker Peak List" dialog box again.
7. If necessary, change the decimal separator to be used for the ASCII export file.
9. In the file selection dialog box, select the storage location and file name for the
export file.
10. Select "Save" to close the dialog box and export the peak list data to the file.
This measurement example describes how to measure harmonics using the provided
marker functions. Note that this task can be performed much simpler using the Har-
monic Distortion measurement (see Section 6.10, "Harmonic distortion measurement",
on page 315).
Procedure:
6. Set the measured signal frequency and the measured level as reference values:
a) Press [MKR FUNC]
b) Press "Reference Fixed".
The position of the marker becomes the reference point. The reference point level
is indicated by a horizontal line, the reference point frequency with a vertical line.
At the same time, the delta marker 2 is switched on.
Figure 8-7: Fundamental wave and the frequency and level reference point
7. Make the step size for the center frequency correspond to the signal frequency: in
the "Frequency" configuration dialog box, select "Center Frequency Stepsize" =
"Marker".
The step size for the center frequency is now equal to the marker frequency.
8. Move the center frequency to the 2nd harmonic of the signal by pressing [UP] ( ).
The center frequency is set to the 2nd harmonic.
9. Select "Auto Level" to ensure the FSW measures the harmonics with a high sensi-
tivity.
10. Place the delta marker on the 2nd harmonic: in the "Marker To" menu, select
"Peak".
The delta marker moves to the maximum of the 2nd harmonic. The displayed level
result is relative to the reference point level (= fundamental wave level).
The other harmonics are measured by repeating steps step 8 to step 10, with the cen-
ter frequency being incremented or decremented in steps of 128 MHz using the [UP] or
[DOWN] keys.
Display lines are only available in the Spectrum and (optional) Analog Demodulation
applications.
In the I/Q Analyzer application, lines are only available for measurements in the fre-
quency domain.
Display lines help you analyze a trace – as do markers. The function of a display line is
comparable to that of a ruler that can be shifted on the trace in order to mark absolute
values. They are used exclusively to visually mark relevant frequencies or points in
time (zero span), as well as constant level values. It is not possible to check automati-
cally whether the points are below or above the marked level values - use limit lines for
that task (see Section 8.4.2.1, "Basics on limit lines", on page 595).
Two different types of display lines are provided:
● Two horizontal lines: "Horizontal Line 1" and "Horizontal Line 2".
These lines are continuous horizontal lines across the entire width of a diagram
and can be shifted up and down.
● Four vertical lines: "Vertical Line 1" to "Vertical Line 4".
These lines are continuous vertical lines across the entire height of the diagram
and can be shifted left and right.
Lables
Each line is identified by one of the following abbreviations in the diagrams:
● H1: "Horizontal Line 1"
● H2: "Horizontal Line 2"
● V1: "Vertical Line 1"
● V2: "Vertical Line 2"
● V3: "Vertical Line 3"
● V4: "Vertical Line 4"
1. Display lines are configured in the "Lines Config" dialog box. To display this dialog
box, press [Lines] and then "Lines Config".
Limit lines allow you to check automatically whether the measured points are below or
above specified values.
● Basics on limit lines...............................................................................................595
● Limit line settings and functions............................................................................ 599
● How to define limit lines........................................................................................ 606
● Reference: limit line file format..............................................................................610
Limit lines are used to define amplitude curves or spectral distribution boundaries in
the result diagram which are not to be exceeded. They indicate, for example, the upper
limits for interference radiation or spurious waves which are allowed from a device
under test (DUT). When transmitting information in TDMA systems (e.g. GSM), the
amplitude of the bursts in a time slot must adhere to a curve that falls within a specified
tolerance band. The lower and upper limits may each be specified by a limit line. Then,
the amplitude curve can be controlled either visually or automatically for any violations
of the upper or lower limits (GO/NOGO test).
The FSW supports limit lines with a maximum of 200 data points. Eight of the limit lines
stored in the instrument can be activated simultaneously. The number of limit lines
stored in the instrument is only limited by the capacity of the storage device used.
Limit line data can also be exported to a file in ASCII (CSV) format for further evalua-
tion in other applications. Limit lines stored in the specified ASCII (CSV) format can
also be imported to the FSW for other measurements.
Compatibility
Limit lines are compatible with the current measurement settings, if the following
applies:
● The x unit of the limit line has to be identical to the current setting.
● The y unit of the limit line has to be identical to the current setting with the excep-
tion of dB based units; all dB based units are compatible with each other.
Validity
Only limit lines that fulfill the following conditions can be activated:
● Each limit line must consist of a minimum of 2 and a maximum of 200 data points.
● The frequencies/times for each data point must be defined in ascending order;
however, for any single frequency or time, two data points may be entered (to
define a vertical segment of a limit line).
● Gaps in frequency or time are not allowed. If gaps are desired, two separate limit
lines must be defined and then both enabled.
Thresholds
If the y-axis for the limit line data points uses relative scaling, an additional absolute
threshold can be defined for the limit check. In this case, both the threshold value and
the relative limit line must be exceeded before a violation occurs.
For the limit line overview, the FSW searches for all stored limit lines with the file exten-
sion .LIN in the limits subfolder of the main installation folder. The overview allows
you to determine which limit lines are available and can be used for the current mea-
surement.
For details on settings for individual lines see "Limit line details" on page 602.
For more basic information on limit lines see Section 8.4.2.1, "Basics on limit lines",
on page 595.
Name...........................................................................................................................600
Unit..............................................................................................................................601
Compatibility................................................................................................................601
Visibility....................................................................................................................... 601
Traces to be Checked................................................................................................. 601
Comment.....................................................................................................................601
Included Lines in Overview (View Filter)..................................................................... 601
└ Show Lines for all Modes..............................................................................601
X-Offset....................................................................................................................... 601
Y-Offset....................................................................................................................... 602
Create New Line......................................................................................................... 602
Edit Line...................................................................................................................... 602
Copy Line.................................................................................................................... 602
Delete Line.................................................................................................................. 602
Disable All Lines..........................................................................................................602
Name
The name of the stored limit line.
Unit
The unit in which the y-values of the data points of the limit line are defined.
Compatibility
Indicates whether the limit line definition is compatible with the current measurement
settings.
For more information on which conditions a limit line must fulfill to be compatible, see
"Compatibility" on page 595.
Visibility
Displays or hides the limit line in the diagram. Up to 8 limit lines can be visible at the
same time. Inactive limit lines can also be displayed in the diagram.
Remote command:
CALCulate<n>:LIMit<li>:LOWer:STATe on page 1340
CALCulate<n>:LIMit<li>:UPPer:STATe on page 1344
CALCulate<n>:LIMit<li>:ACTive? on page 1345
Traces to be Checked
Defines which traces are automatically checked for conformance with the limit lines. As
soon as a trace to be checked is defined, the assigned limit line is active. One limit line
can be activated for several traces simultaneously. If any of the "Traces to be
Checked" violate any of the active limit lines, a message is indicated in the diagram.
Remote command:
CALCulate<n>:LIMit<li>:TRACe<t>:CHECk on page 1346
Comment
An optional description of the limit line.
Show Lines for all Modes ← Included Lines in Overview (View Filter)
If activated (default), limit lines from all applications are displayed. Otherwise, only
lines that were created in the Spectrum application are displayed.
Note that limit lines from some applications may include additional properties that are
lost when the limit lines are edited in the Spectrum application. In this case a warning
is displayed when you try to store the limit line.
X-Offset
Shifts a limit line that has been specified for relative frequencies or times (x-axis) hori-
zontally.
This setting does not have any effect on limit lines that are defined by absolute values
for the x-axis.
Remote command:
CALCulate<n>:LIMit<li>:CONTrol:OFFSet on page 1337
Y-Offset
Shifts a limit line that has relative values for the y-axis (levels or linear units such as
volt) vertically.
This setting does not have any effect on limit lines that are defined by absolute values
for the y-axis.
Remote command:
CALCulate<n>:LIMit<li>:LOWer:OFFSet on page 1339
CALCulate<n>:LIMit<li>:UPPer:OFFSet on page 1343
Edit Line
Edit an existing limit line configuration.
Copy Line
Copy the selected limit line configuration to create a new line.
Remote command:
CALCulate<n>:LIMit<li>:COPY on page 1345
Delete Line
Delete the selected limit line configuration.
Remote command:
CALCulate<n>:LIMit<li>:DELete on page 1345
Name...........................................................................................................................603
Comment.....................................................................................................................603
Threshold.................................................................................................................... 603
Margin......................................................................................................................... 604
X-Axis..........................................................................................................................604
Y-Axis.......................................................................................................................... 604
Data Points..................................................................................................................604
Insert Value................................................................................................................. 605
Delete Value................................................................................................................605
Shift x.......................................................................................................................... 605
Shift y.......................................................................................................................... 605
Save............................................................................................................................ 605
Import.......................................................................................................................... 605
└ File Explorer..................................................................................................605
Export..........................................................................................................................605
└ File Explorer..................................................................................................606
Name
Defines the limit line name. All names must be compatible with Windows conventions
for file names. The limit line data is stored under this name (with a .LIN extension).
Remote command:
CALCulate<n>:LIMit<li>:NAME on page 1341
Comment
Defines an optional comment for the limit line.
Remote command:
CALCulate<n>:LIMit<li>:COMMent on page 1335
Threshold
Defines an absolute threshold value (only for relative scaling of the y-axis).
Margin
Defines a margin for the limit line. The default setting is 0 dB (i.e. no margin).
For details on margins see "Limits and Margins" on page 596.
Remote command:
CALCulate<n>:LIMit<li>:LOWer:MARGin on page 1338
CALCulate<n>:LIMit<li>:UPPer:MARGin on page 1342
X-Axis
Describes the horizontal axis on which the data points of the limit line are defined.
Includes the following settings:
● Unit:
– "Hz": for frequency domain
– "s": for time domain
● Scaling mode: absolute or relative values
For relative values, the frequencies are referred to the currently set center fre-
quency. In the time domain, the left boundary of the diagram is used as the refer-
ence.
● Scaling: linear or logarithmic
Remote command:
CALCulate<n>:LIMit<li>:CONTrol:MODE on page 1336
CALCulate<n>:LIMit<li>:CONTrol:DOMain on page 1336
CALCulate<n>:LIMit<li>:CONTrol:SPACing on page 1337
Y-Axis
Describes the vertical axis on which the data points of the limit line are defined.
Includes the following settings:
● Level unit
● Scaling mode: absolute or relative (dB/%) values
Relative limit values refer to the reference level.
● Limit type: upper or lower limit; values must stay above the lower limit and below
the upper limit to pass the limit check
Remote command:
CALCulate<n>:LIMit<li>:UNIT on page 1341
CALCulate<n>:LIMit<li>:LOWer:MODE on page 1338
CALCulate<n>:LIMit<li>:UPPer:MODE on page 1342
CALCulate<n>:LIMit<li>:LOWer:SPACing on page 1340
CALCulate<n>:LIMit<li>:UPPer:SPACing on page 1343
Data Points
Each limit line is defined by a minimum of 2 and a maximum of 200 data points. Each
data point is defined by its position (x-axis) and value (y-value). Data points must be
defined in ascending order. The same position can have two different values.
Remote command:
CALCulate<n>:LIMit<li>:CONTrol[:DATA] on page 1335
CALCulate<n>:LIMit<li>:LOWer[:DATA] on page 1338
CALCulate<n>:LIMit<li>:UPPer[:DATA] on page 1341
Insert Value
Inserts a data point in the limit line above the selected one in the "Edit Limit Line" dia-
log box.
Delete Value
Deletes the selected data point in the "Edit Limit Line" dialog box.
Shift x
Shifts the x-value of each data point horizontally by the defined shift width (as opposed
to an additive offset defined for the entire limit line, see "X-Offset" on page 601).
Remote command:
CALCulate<n>:LIMit<li>:CONTrol:SHIFt on page 1337
Shift y
Shifts the y-value of each data point vertically by the defined shift width (as opposed to
an additive offset defined for the entire limit line, see "Y-Offset" on page 602).
Remote command:
CALCulate<n>:LIMit<li>:LOWer:SHIFt on page 1339
CALCulate<n>:LIMit<li>:UPPer:SHIFt on page 1343
Save
Saves the currently edited limit line under the name defined in the "Name" field.
Import
Opens a file selection dialog box and loads the limit line from the selected file in .CSV
format.
Note that a valid import file must contain a minimum of required information for the
FSW.
For details on the file format see Section 8.4.2.4, "Reference: limit line file format",
on page 610.
Remote command:
MMEMory:LOAD<n>:LIMit on page 1347
Export
Opens a file selection dialog box and stores the currently displayed limit line to the
defined file in .CSV format.
For details on the file format see Section 8.4.2.4, "Reference: limit line file format",
on page 610.
The limit line can be imported again later by the FSW for use in other measurements.
Remote command:
MMEMory:STORe<n>:LIMit on page 1347
2. Select "Edit".
3. Edit the line configuration as described in "How to configure a new limit line"
on page 608.
3. Define a new name to create a new limit with the same configuration as the source
line.
4. Edit the line configuration as described in "How to configure a new limit line"
on page 608.
2. Select "Delete".
2. Define a "Name" and, optionally, a "Comment" for the new limit line.
6. Check the current line configuration in the preview area of the dialog box. If neces-
sary, correct individual data points or add or delete some.
If necessary, shift the entire line vertically or horizontally by selecting "Shift x" or
"Shift y" and defining the shift width.
2. To shift the complete limit line parallel in the horizontal direction, select "X-Offset"
and enter an offset value.
To shift the complete limit line parallel in the vertical direction, select "Y-Offset" and
enter an offset value.
3. To shift the individual data points of a limit line by a fixed value (all at once):
a) Select "Edit".
b) In the "Edit Limit Line" dialog box, select "Shift x" or "Shift y" and define the
shift width.
c) Save the shifted data points by selecting "Save".
If activated, the limit line is shifted in the diagram.
3. Define the limit line as described in "How to configure a new limit line"
on page 608.
7. Select "Save".
The limit line is stored to a file with the specified name and the extension .CSV.
For details on the file format see Section 8.4.2.4, "Reference: limit line file format",
on page 610.
6. Select "Select".
The limit line is loaded from the specified file and displayed in the "Edit Limit Line"
dialog box.
7. Activate the limit line as described in "How to activate and deactivate a limit check"
on page 607.
Limit line data can be exported to a file in ASCII (CSV) format for further evaluation in
other applications. Limit lines stored in the specified ASCII (CSV) format can also be
imported to the FSW for other measurements (see "How to import a limit line"
on page 609). This reference describes in detail the format of the export/import files for
limit lines. Note that the bold data is mandatory, all other data is optional.
Different language versions of evaluation programs may require a different handling of
the decimal point. Thus, you can define the decimal separator to be used (see "Deci-
mal Separator" on page 654).
Table 8-2: ASCII file format for limit line files
Header data
-2000000000;-30
-1000000000;0
0;-30
2500000000;-50
Example:
Assume the following measurement parameters:
● Sample rate: 32 MSamples / s
● Measurement points: 1000
● Measurement time: 100 ms
● Span: 5 GHz
During a single measurement, 3.2 * 106 samples are collected and distributed to 1000
measurement points, i.e. 3200 samples are collected per measurement point. For each
measurement point, the measured data for a frequency span of 5 MHz (span/<mea-
surement points>) is analyzed.
Note that if you increase the number of measurement points, the frequency span ana-
lyzed for each point in the trace decreases, making the trace more reliable. The ana-
lyzed results become more accurate. On the other hand, for detectors that average the
samples within the span, the trace becomes less stable because fewer samples are
averaged.
See also Section 7.5.1.8, "How much data is measured: sweep points and sweep
count", on page 499.
Obviously, the data must be reduced to determine which of the samples are displayed
for each measurement point. This is the trace detector's task. The trace detector can
analyze the measured data using various methods.
The result obtained from the selected detector for a measurement point is displayed as
the value at this frequency point in the trace.
Measurement point n Meas. point n+1
Video video
Signal signal
SAMPLE
AVG s1 s2 s3 s4 s5 s6 s8 s1
RMS
MAX PEAK
AUTO PEAK
MIN PEAK
You can define the trace detector to be used for the individual traces manually, or the
FSW can select the appropriate detector automatically.
The detectors of the FSW are implemented as pure digital devices. All detectors work
in parallel in the background, which means that the measurement speed is independ-
ent of the detector combination used for different traces.
However, you should select a measurement time that is sufficient for the detector that
requires the longest measurement time.
Auto detector
If the FSW is set to define the appropriate detector automatically, the detector is set
depending on the selected trace mode and average mode:
"View" –
"Blank" –
The detector activated for the specific trace is indicated in the corresponding trace
information by an abbreviation. Not all detector types are supported by all applications
available for the FSW.
Detector Abbrev.
RMS "Rm"
Average "Av"
Detector Abbrev.
Measurement time
The measurement time defines how long the FSW measures the signal at the individ-
ual frequencies. Each detector needs a different period of time to fully charge and dis-
charge; the individual requirements on the measurement time are described for each
detector.
● Positive peak (max peak) and negative peak (min peak) detector....................... 614
● Auto peak detector................................................................................................ 614
● RMS detector........................................................................................................ 614
● Average detector...................................................................................................615
● Sample detector.................................................................................................... 616
● Quasipeak detector............................................................................................... 616
● CISPR average detector....................................................................................... 617
● RMS average detector.......................................................................................... 618
Positive peak (max peak) and negative peak (min peak) detector
The positive (maximum) detector determines the largest of all positive peak values
measured at the individual measurement points which are combined in one sample
point.
The negative (minimum) peak detector determines the smallest of all negative peak
values measured at the individual measurement points which are combined in one
sample point.
Tips regarding measurement time:
● For unmodulated signals, you can use the shortest possible measurement time.
● For pulsed signals, measurement time must be longer than the expected pulse
length, that is: it must cover at least one pulse.
RMS detector
The RMS detector calculates the root mean square of all samples combined in a
sweep point. The whole IF envelope is used to calculate the power for each measure-
ment point. The IF envelope is digitized using a sample rate which is at least five times
the selected resolution bandwidth. Based on the sample values, the power is calcula-
ted for each measurement point using the following formula:
Where:
● PRMS = power represented by a measurement point
● N = number of A/D converter values (samples) per measurement point
● R = electrical impedance
● si = linear digitized video voltage at the output of the A/D converter
For logarithmic scaling, after the power has been calculated, the power units are con-
verted into decibels and the value is displayed as a measurement point.
Where:
● P (dB) = logarithmic power represented by a measurement point
Each sweep point thus corresponds to the root mean square of the measured values
combined in the sweep point.
The RMS detector supplies the power of the signal irrespective of the waveform (CW
carrier, modulated carrier, white noise or impulsive signal). Correction factors as nee-
ded for other detectors to measure the power of the different signal classes are not
required.
Tips regarding measurement time:
● For unmodulated signals, you can use the shortest possible measurement time.
● For modulated signals, the measurement time must be long enough to make sure
the averaging considers all variations due to the modulation characteristics of the
signal.
● For pulsed signals, the measurement time must be long enough to capture a suffi-
cient number of pulses. For averaging, a sufficient number of pulses is greater than
10.
Average detector
The average detector calculates the linear average of all samples combined in a
sweep point.
For average detection, the video voltage (envelope of IF signal) is averaged over the
measurement time. Averaging is digital, i.e. the digitized values of the video voltage
are summed up and divided by the number of samples at the end of the measurement
time. This corresponds to a filtering with a rectangular window in the time domain and
a filtering with sin x/x characteristic in the frequency domain.
To this effect, FSW uses the linear voltage after envelope detection. The sampled lin-
ear values are summed up and the sum is divided by the number of samples (= linear
average value). For linear display, the average value is displayed.
Where:
● PAVG = power represented by a measurement point
● N = number of A/D converter values per measurement point
● R = electrical impedance
● si = linear digitized video voltage at the output of the A/D converter
For logarithmic scaling, after the power has been calculated, the power units are con-
verted into decibels, and the value is displayed as a measurement point.
Where:
● P (dBm) = logarithmic power represented by a measurement point
Each measurement point thus corresponds to the average of the measured values
combined in the measurement point.
The average detector supplies the average value of the signal irrespective of the wave-
form (CW carrier, modulated carrier, white noise or impulsive signal).
Tips regarding measurement time:
● For unmodulated signals, you can use the shortest possible measurement time.
● For modulated signals, the measurement time must be long enough to make sure
the averaging considers all variations due to the modulation characteristics of the
signal.
● For pulsed signals, the measurement time must be long enough to capture a suffi-
cient number of pulses. For averaging, a sufficient number of pulses is greater than
10.
Sample detector
The sample detector selects and displays a single sample (always the first or always
the last) from all samples that are combined in the sweep point. All other measured
values for the sample point are ignored.
Quasipeak detector
The quasipeak detector resembles the behavior of an analog voltmeter by analyzing
the measured values for a sample point. The quasipeak detector is especially designed
for the requirements of EMI measurements and is used to analyze pulse-shaped spurs.
This detector is only available for the CISPR filter.
It requires the R&S FSW EMI measurement option (K54) to be installed.
The quasipeak detector is not available for an RBW of 1 MHz.
The quasipeak detector displays the weighted maximum signal level according to
CISPR 16-1-1 that was detected during the specified measurement time.
The filter bandwidth and time parameters of the detector depend on the measured fre-
quency. The time lag of the simulated pointer instrument reflects the weighting factor of
the signal depending on its form, modulation, etc.
Table 8-5: Required parameters depending on frequency for CISPR quasi-peak detector
Frequency range < 150 kHz 150 kHz to 30 MHz > 30 MHz
Frequency range <150 kHz 150 kHz to 30 MHz 30 MHz to 1 GHz >1 GHz
Frequency range <150 kHz 150 kHz to 30 MHz 30 MHz to 1 GHz >1 GHz
When you change the frequency or the attenuation, the FSW waits until the lowpass
filter has settled before starting the measurement. In this case, the measurement time
depends on the resolution bandwidth and the characteristics of the signal.
Start/stop
This is the default (legacy) method for trace values in the frequency domain. The x-
value of the first sweep point corresponds to the starting point of the full measurement
span. The x-value of the last sweep point corresponds to the end point of the full mea-
surement span. All other sweep points are divided evenly between the first and last
points. The distance between two sweep points is span/(<no_sweep_points> -1).
Bin-centered
This is the default method for all marker values. The full measurement span is divided
by the number of sweep points. The result is the span that is evaluated for an individ-
ual sweep point, also referred to as a bin. The x-value of the sweep point is then
defined as the x-value at the center of the bin (bin/2).
Measurement point n Meas. point n+1
Video video
Signal signal
s1 s2 s3 s4 s5 s6 s8 s1
x
xn xn+1
Using the bin-centered method, the first and last x-values of the trace are not identical
to the exact starting and end point of the measurement span. The distance between
two sweep points corresponds to the width of the bin, or span/(<no_sweep_points>).
Marker values are always determined using the bin-centered method. Markers placed
on the first and last x-values of the measured span indicate the same results as the
first and last trace point.
Example:
Assume the following measurement parameters:
● Start frequency: 1.000 GHz
● Stop frequency: 6.000 GHz
● => Span: 5 GHz
● sweep points: 1000
● =>bin: 5 MHz (span/<sweep points>)
The first trace point is displayed at (<fstart> + bin/2) = 1.0025 GHz.
The last trace point is displayed at (<fstop> - bin/2) = 5.9975 GHz.
A marker placed at 1.000 GHz indicates the same result as a marker placed at 1.0025
GHz, since no other value is available.
For trace values in the frequency domain, you can select which method is used to
determine the x-values in the frequency domain, that is:
● In the result displays
● When exporting traces
● For the TRACe<n>[:DATA]:X? command
See "X-Value Distribution" on page 654.
Note the possible minor discrepancy between marker values and trace values using
the start/stop method.
Each time you change the trace mode, the selected trace memory is cleared.
The trace mode also determines the detector type if the detector is set automatically,
see "Mapping samples to sweep points with the trace detector" on page 611.
Clear Write Overwrite mode: the trace is overwritten by each sweep. This is the default setting.
All available detectors can be selected.
Max Hold The maximum value is determined over several measurements and displayed. The
FSW saves the sweep result in the trace memory only if the new value is greater than
the previous one.
This mode is especially useful with modulated or pulsed signals. The signal spectrum
is filled up upon each sweep until all signal components are detected in a kind of
envelope.
This mode is not available for statistics measurements.
Min Hold The minimum value is determined from several measurements and displayed. The
FSW saves the sweep result in the trace memory only if the new value is lower than
the previous one.
This mode is useful for example for making an unmodulated carrier in a composite
signal visible. Noise, interference signals or modulated signals are suppressed,
whereas a CW signal is recognized by its constant level.
This mode is not available for statistics measurements.
View The current contents of the trace memory are frozen and displayed.
If a trace is frozen ("View" mode), you can change the measurement settings, apart
from scaling settings, without impact on the displayed trace. The fact that the displayed
trace no longer matches the current measurement settings is indicated by a yellow
asterisk on the tab label.
If you change any parameters that affect the scaling of the diagram axes, the FSW
automatically adapts the trace data to the changed display range. Thus, you can zoom
into the diagram after the measurement to show details of the trace.
Due to the weighting between the current trace and the average trace, past val-
ues have practically no influence on the displayed trace after about ten
sweeps. With this setting, signal noise is effectively reduced without need for
restarting the averaging process after a change of the signal.
– In "Single" sweep mode, the current trace is averaged with the previously
stored averaged trace. No averaging is carried out for the first sweep but the
measured value is stored in the trace memory. The next time a sweep is per-
formed, the trace average is calculated according to the following formula:
Traceold MeasValue
Trace
2
For stationary signals, the two methods yield the same result.
Logarithmic averaging is recommended if sinewave signals are to be clearly visible
against noise since with this type of averaging noise suppression is improved while the
sinewave signals remain unchanged.
For noise or pseudo-noise signals, the positive peak amplitudes are decreased in loga-
rithmic averaging due to the characteristic involved. The negative peak values are
increased relative to the average value. If the distorted amplitude distribution is aver-
aged, a value is obtained that is smaller than the actual average value. The difference
is -2.5 dB.
This low average value is usually corrected in noise power measurements by a 2.5 dB
factor. Therefore the FSW offers the selection of linear averaging. The trace data is lin-
earized before averaging, then averaged and logarithmized again for display on the
screen. The average value is always displayed correctly irrespective of the signal char-
acteristic.
Trace smoothing
A video bandwidth filter (VBW) is a hardware-based method of smoothing the trace
(see also Section 7.5.1.2, "Smoothing the trace using the video bandwidth",
on page 495). However, other sweep and bandwidth settings can be coupled to the
VBW. For some signals, a VBW may not be freely selectable to obtain the required
smoothing effect. Therefore, a software-based trace smoothing function is also availa-
ble.
(Software-based) smoothing is a way to remove anomalies visually in the trace that
can distort the results. The smoothing process is based on a moving average over the
complete measurement range. The number of samples included in the averaging proc-
ess (the aperture size) is variable and is a percentage of all samples that the trace con-
sists of.
You can turn trace smoothing on and off for all traces individually and compare, for
example, the raw and the smooth trace.
Linear smoothing is based on the following algorithm:
x s n1
1 2
y ' s y x
n
x s n1
2
Equation 8-1: Linear trace smoothing
With:
s = sample number
x = sample offset from s
n = aperture size
Trace data can also be exported to an ASCII file for further analysis. For details see
Section 8.6.2, "Trace/data ex/import", on page 652.
Trace Mode
Defines the update mode for subsequent traces.
For details, see "Analyzing several traces - trace mode" on page 620.
"Clear/ Write" Overwrite mode (default): the trace is overwritten by each sweep.
All available detectors can be selected.
In Spectrum mode, the "Detector" is automatically set to "Auto Peak".
"Max Hold" The maximum value is determined over several measurements and
displayed. The FSW saves the sweep result in the trace memory only
if the new value is greater than the previous one.
This mode is especially useful with modulated or pulsed signals. The
signal spectrum is filled up upon each sweep until all signal compo-
nents are detected in a kind of envelope.
The "Detector" is automatically set to "PositivePeak".
This mode is not available for statistics measurements.
"Min Hold" The minimum value is determined from several measurements and
displayed. The FSW saves the sweep result in the trace memory only
if the new value is lower than the previous one.
This mode is useful for example for making an unmodulated carrier in
a composite signal visible. Noise, interference signals or modulated
signals are suppressed, whereas a CW signal is recognized by its
constant level.
The "Detector" is automatically set to "Negative Peak".
This mode is not available for statistics measurements.
"Average" The average is formed over several sweeps.
The Sweep/Average Count determines the number of averaging pro-
cedures.
The "Detector" is automatically set to "Sample".
This mode is not available for statistics measurements.
"View" The current contents of the trace memory are frozen and displayed.
Note: If a trace is frozen, you can change the measurement settings,
apart from scaling settings, without impact on the displayed trace.
The fact that the displayed trace no longer matches the current mea-
surement settings is indicated by a yellow asterisk on the tab label.
If you change any parameters that affect the scaling of the diagram
axes, the FSW automatically adapts the trace data to the changed
display range. Thus, you can zoom into the diagram after the mea-
surement to show details of the trace.
"Blank" Removes the selected trace from the display.
Remote command:
DISPlay[:WINDow<n>][:SUBWindow<w>]:TRACe<t>:MODE on page 1245
Detector
Defines the trace detector to be used for trace analysis.
For details see "Mapping samples to sweep points with the trace detector"
on page 611.
Note: For EMI measurements, the trace detector is used for the initial peak search
only, not for the final test. The detector for the final test is configured in the EMI marker
settings, see Section 6.13.4.1, "EMI marker configuration", on page 343.
"Auto" (default:) Selects the optimum detector for the selected trace and fil-
ter mode
"Type" Defines the selected detector type.
Note: If the EMI (R&S FSW-K54) measurement option is installed,
additional detectors are available, even if EMI measurement is not
active. If you select a CISPR trace detector, the RBW filter type is
automatically also set to CISPR.
CISPR detectors are only available under the following conditions:
● Time domain measurements and frequency measurements in
sweep mode (not FFT mode, not power measurements, emission
measurements, or statistics measurements)
For details and further restrictions, see Section 6.13.3.2, "Detectors
and dwell time", on page 338.
Remote command:
[SENSe:][WINDow<n>:]DETector<t>[:FUNCtion] on page 1250
[SENSe:][WINDow<n>:]DETector<t>[:FUNCtion]:AUTO on page 1251
Hold
If activated, traces in "Min Hold", "Max Hold" and "Average" mode are not reset after
specific parameter changes have been made.
Normally, the measurement is started again after parameter changes, before the mea-
surement results are analyzed (e.g. using a marker). In all cases that require a new
measurement after parameter changes, the trace is reset automatically to avoid false
results (e.g. with span changes). For applications that require no reset after parameter
changes, the automatic reset can be switched off.
The default setting is off.
Remote command:
DISPlay[:WINDow<n>][:SUBWindow<w>]:TRACe<t>:MODE:HCONtinuous
on page 1246
Smoothing
If enabled, the trace is smoothed by the specified value (between 1 % and 50 %). The
smoothing value is defined as a percentage of the display width. The larger the
smoothing value, the greater the smoothing effect.
Note: Effects of smoothing on post-processing functions. Note that in Spectrum mode,
all functions performed after the sweep, such as limit checks, markers, or channel
power measurements, are based on the smoothed trace data. Thus, the results differ
from results based on the original trace.
For more information, see "Trace smoothing" on page 623.
Remote command:
DISPlay[:WINDow<n>][:SUBWindow<w>]:TRACe<t>:SMOothing[:STATe]
on page 1248
DISPlay[:WINDow<n>][:SUBWindow<w>]:TRACe<t>:SMOothing:APERture
on page 1248
Average Mode
Defines the mode with which the trace is averaged over several sweeps.
This setting is generally applicable if trace mode "Average" is selected.
For FFT sweeps, the setting also affects the VBW (regardless of whether the trace is
averaged).
(See also "Video bandwidth (VBW)" on page 160).
How many sweeps are averaged is defined by the "Sweep/Average Count"
on page 506.
For details see "How trace data is averaged - the averaging mode" on page 622.
"Linear" The power level values are converted into linear units before averag-
ing. After the averaging, the data is converted back into its original
unit.
"Logarithmic" For logarithmic scaling, the values are averaged in dBm. For linear
scaling, the behavior is the same as with linear averaging.
"Power" Activates linear power averaging.
The power level values are converted into unit Watt before averaging.
After the averaging, the data is converted back into its original unit.
Use this mode to average power values in Volts or Amperes correctly.
In particular, for small VBW values (smaller than the RBW), use
power averaging mode for correct power measurements in FFT
sweep mode.
Remote command:
[SENSe:]AVERage<n>:TYPE on page 1249
Average Count
Determines the number of averaging or maximum search procedures If the trace
modes "Average", "Max Hold" or "Min Hold" are set.
Trace 2: Average
Auto Detector (Sample)
Remote command:
DISPlay[:WINDow<n>][:SUBWindow<w>]:TRACe<t>:PRESet on page 1247
Copy Trace
Access: "Overview" > "Analysis" > "Traces" > "Copy Trace"
Or: [TRACE] > "Copy Trace"
Copies trace data to another trace.
The first group of buttons (labeled "Trace 1" to "Trace 6") selects the source trace. The
second group of buttons (labeled "Copy to Trace 1" to "Copy to Tace 6") selects the
destination.
Remote command:
TRACe<n>:COPY on page 1251
Trace Labels
Access: "Overview" > "Analysis" > "Traces" > "Trace Label" tab
You can define a descriptive label to active traces instead of the default "Trace <x>"
label.
Note: This function is not available in all applications.
The labels are displayed in the diagram area. The font color corresponds to the color of
the particular trace (for example, yellow trace: yellow font).
Figure 8-14: Example: the yellow and blue traces have a label
You can move the trace label to any position on the display by dragging it to the new
position.
You can only configure labels for active traces and for traces whose "State" is enabled.
1. For each trace, select the "Trace Mode" and "Trace Detector". Traces with the
trace mode "Blank" are not displayed.
2. To configure several traces to predefined display modes in one step, press the but-
ton for the required function:
● "Preset All Traces"
● "Set Trace Mode Max | Avg | Min"
● "Set Trace Mode Max | ClrWrite | Min"
For details see Section 8.5.1.2, "Trace settings", on page 624.
3. For "Average" trace mode, define the number of sweeps to be averaged in the
"Count:" field.
5. To improve the trace stability, increase the number of "Sweep Points" or the
"Sweep Time" (in the "Sweep" settings).
All configured traces (not set to "Blank") are displayed after the next sweep.
3. Select "Copy to Trace" for the trace to which the settings are to be applied.
The settings from the source trace are applied to the destination trace. The newly
configured trace (if not set to "Blank") is displayed after the next sweep.
8.5.2 Spectrograms
In addition to the standard "level versus frequency" or "level versus time" traces, the
FSW also provides a spectrogram display of the measured data.
A spectrogram shows how the spectral density of a signal varies over time. The x-axis
shows the frequency, the y-axis shows the time. A third dimension, the power level, is
indicated by different colors. Thus you can see how the strength of the signal varies
over time for different frequencies.
Example:
In this example, you see the spectrogram for the calibration signal of the FSW, com-
pared to the standard spectrum display. Since the signal does not change over time,
the color of the frequency levels does not change over time, i.e. vertically. The legend
above the spectrogram display describes the power levels the colors represent.
Result display
The spectrogram result can consist of the following elements:
2
4
8 5 8
7
3
For more information about spectrogram configuration, see Section 8.5.2.2, "Spectro-
gram settings", on page 639.
Remote commands:
Activating and configuring spectrograms:
Section 13.8.2.2, "Configuring spectrograms", on page 1252
Storing results:
MMEMory:STORe<n>:SPECtrogram on page 1379
● Time frames.......................................................................................................... 632
● Markers in the spectrogram.................................................................................. 634
● Three-dimensional spectrograms..........................................................................635
● Color maps............................................................................................................636
Time frames
The time information in the spectrogram is displayed vertically, along the y-axis. Each
line (or trace) of the y-axis represents one or more captured sweep and is called a
time frame or simply "frame". As with standard spectrum traces, several measured
values are combined in one sweep point using the selected detector.
(See "Mapping samples to sweep points with the trace detector" on page 611).
Frames are sorted in chronological order, beginning with the most recently recorded
frame at the top of the diagram (frame number 0). With the next sweep, the previous
frame is moved further down in the diagram, until the maximum number of captured
frames is reached. The display is updated continuously during the measurement, and
the measured trace data is stored. Spectrogram displays are continued even after sin-
gle measurements unless they are cleared manually.
The maximum number of frames that you can capture is summarized in Table 8-9.
Table 8-9: Correlation between number of sweep points and number of frames stored in the history
buffer
≤1250 20000
2001 12488
4001 6247
8.001 3124
16.001 1562
32.001 781
The scaling of the time axis (y-axis) is not configurable. However, you can enlarge the
spectrogram display by maximizing the window using "Split/Maximize".
Especially for "Average" or "Min Hold" and "Max Hold" trace modes, the number of
sweeps that are analyzed to create a single trace has an effect on the accuracy of the
results. Thus, you can also define whether the results from frames in previous traces
are considered in the analysis for each new trace ("Continue Frame").
In the spectrum result display, the markers and their frequency and level values (1) are
displayed as usual. Additionally, the frame number is displayed to indicate the position
of the marker in time (2).
In the spectrogram result display, you can activate up to 16 markers or delta markers
at the same time. Each marker can be assigned to a different frame. Therefore, in
addition to the frequency you also define the frame number when activating a new
marker. If no frame number is specified, the marker is positioned on the currently
selected frame. All markers are visible that are positioned on a visible frame. Special
search functions are provided for spectrogram markers.
In the spectrum result display, only the markers positioned on the currently selected
frame are visible. In "Continuous Sweep" mode, this means that only markers posi-
tioned on frame 0 are visible. To view markers that are positioned on a frame other
than frame 0 in the spectrum result display, you must stop the measurement and select
the corresponding frame.
Three-dimensional spectrograms
A common spectrogram shows the frequency on the x-axis, while the y-axis shows the
time (in frames). The power level is indicated by different colors of the 2-dimensional
points.
In the 3-dimensional spectrogram, the power is indicated by a value in a third dimen-
sion, the z-axis. The color mapping is maintained for the point in the 3-dimensional
result display.
This new display provides an even better overview of how the strength of the signal
varies over time for different frequencies.
The number of frames displayed on the time (y-)axis is user-definable, whereas for 2-
dimensional spectrograms, the number of frames is determined automatically accord-
ing to the size of the window. All other spectrogram settings are identical for 3-dimen-
sional and 2-dimensional spectrograms.
When the measurement is stopped or completed, the currently selected frame is indi-
cated by a gray vertical plane. (As opposed to the small white arrows at the borders of
the 2-dimensional display.) The spectrum diagram always displays the spectrum for the
currently selected frame.
By default, the most recently recorded frame (frame 0) is selected, and added at the
front of the diagram.
Rotation to the left > focus on Rotation down > focus on fre- Rotation to the right > focus on
frame quency and frame frequency
Color maps
Spectrograms assign power levels to different colors to visualize them. The legend
above the spectrogram display describes the power levels the colors represent.
The color display is highly configurable to adapt the spectrograms to your needs. You
can define:
● Which colors to use (Color scheme)
● Which value range to apply the color scheme to
● How the colors are distributed within the value range, i.e where the focus of the vis-
ualization lies (shape of the color curve)
The individual colors are assigned to the power levels automatically by the FSW.
Uses a color range from blue to red. Blue colors indicate low levels, red colors indi-
cate high ones.
● Cold
Uses a color range from red to blue. Red colors indicate low levels, blue colors
indicate high ones.
The "Cold" color scheme is the inverse "Hot" color scheme.
● Radar
Uses a color range from black over green to light turquoise with shades of green in
between. Dark colors indicate low levels, light colors indicate high ones.
● Grayscale
Shows the results in shades of gray. Dark gray indicates low levels, light gray indi-
cates high ones.
Example:
In the color map based on the linear color curve, the range from -100 dBm to -60 dBm
is covered by blue and a few shades of green only. The range from -60 dBm to
-20 dBm is covered by red, yellow and a few shades of green.
The sample spectrogram is dominated by blue and green colors. After shifting the color
curve to the left (negative value), more colors cover the range from -100 dBm to
-60 dBm (blue, green and yellow). This range occurs more often in the example. The
range from -60 dBm to -20 dBm, on the other hand, is dominated by various shades of
red only.
State............................................................................................................................640
3D Spectrogram State.................................................................................................641
Select Frame...............................................................................................................641
History Depth.............................................................................................................. 641
3-D Display Depth....................................................................................................... 641
Time Stamp................................................................................................................. 641
Color Mapping.............................................................................................................641
Continuous Sweep / Run Cont....................................................................................642
Single Sweep / Run Single..........................................................................................642
Clear Spectrogram...................................................................................................... 642
State
Activates and deactivates a Spectrogram subwindow.
"Split" Displays the Spectrogram as a subwindow in the original result dis-
play.
"Full" Displays the Spectrogram in a subwindow in the full size of the origi-
nal result display.
"Off" Closes the Spectrogram subwindow.
Remote command:
CALCulate<n>:SPECtrogram:LAYout on page 1255
3D Spectrogram State
Activates and deactivates a 3-dimensional spectrogram. As opposed to the common 2-
dimensional spectrogram, the power is not only indicated by a color mapping, but also
in a third dimension, the z-axis.
For details see "Three-dimensional spectrograms" on page 635.
Remote command:
CALCulate<n>:SPECtrogram:THReedim[:STATe] on page 1255
Select Frame
Selects a specific frame, loads the corresponding trace from the memory, and displays
it in the Spectrum window.
Note that activating a marker or changing the position of the active marker automati-
cally selects the frame that belongs to that marker.
This function is only available in single sweep mode or if the sweep is stopped, and
only if a spectrogram is selected.
The most recent frame is number 0, all previous frames have a negative number.
For more details, see "Time frames" on page 632.
Remote command:
CALCulate<n>:SPECtrogram:FRAMe:SELect on page 1254
History Depth
Sets the number of frames that the FSW stores in its memory.
The maximum number of frames depends on the Sweep Points.
If the memory is full, the FSW deletes the oldest frames stored in the memory and
replaces them with the new data.
Remote command:
CALCulate<n>:SPECtrogram:HDEPth on page 1254
Time Stamp
Activates and deactivates the timestamp. The timestamp shows the system time while
the measurement is running. In single sweep mode or if the sweep is stopped, the
timestamp shows the time and date of the end of the sweep.
When active, the timestamp replaces the display of the frame number.
Remote command:
CALCulate<n>:SPECtrogram:TSTamp[:STATe] on page 1257
CALCulate<n>:SPECtrogram:TSTamp:DATA? on page 1256
Color Mapping
Opens the "Color Mapping" dialog.
For details see "Color maps" on page 636.
Clear Spectrogram
Resets the spectrogram result display and clears the history buffer.
This function is only available if a spectrogram is selected.
Remote command:
CALCulate<n>:SPECtrogram:CLEar[:IMMediate] on page 1252
Start / Stop
Defines the lower and upper boundaries of the value range of the spectrogram.
Remote command:
DISPlay[:WINDow<n>]:SPECtrogram:COLor:LOWer on page 1258
DISPlay[:WINDow<n>]:SPECtrogram:COLor:UPPer on page 1258
Shape
Defines the shape and focus of the color curve for the spectrogram result display.
"-1 to <0" More colors are distributed among the lower values
"0" Colors are distributed linearly among the values
">0 to 1" More colors are distributed among the higher values
Remote command:
DISPlay[:WINDow<n>]:SPECtrogram:COLor:SHAPe on page 1258
Hot/Cold/Radar/Grayscale
Sets the color scheme for the spectrogram.
Remote command:
DISPlay[:WINDow<n>]:SPECtrogram:COLor[:STYLe] on page 1259
Auto
Defines the color range automatically according to the existing measured values for
optimized display.
Set to Default
Sets the color mapping to the default settings.
Remote command:
DISPlay[:WINDow<n>]:SPECtrogram:COLor:DEFault on page 1258
Close
Saves the changes and closes the dialog box.
● "To set the color curve shape graphically using the slider" on page 648
● "To set the color curve shape numerically" on page 648
To display a spectrogram
1. In the "Overview", select "Display", then drag the evaluation type "Spectrogram" to
the diagram area.
Alternatively:
a) Select [TRACE] and then "Spectrogram Config".
b) Toggle "Spectrogram" to "On".
4. Enter the frame number for which the marker is to be set, for example 0 for the cur-
rent frame, or -2 for the second to last frame. Note that the frame number is always
0 or a negative value!
The marker is only visible in the spectrum diagram if it is defined for the currently
selected frame. In the spectrogram result display all markers are visible that are
positioned on a visible frame.
To configure a spectrogram
1. Configure the spectrogram frames:
a) Select [SWEEP].
b) Select "Sweep Config".
c) In the "Sweep/Average Count" field, define how many sweeps are to be ana-
lyzed to create a single frame.
d) In the "Frame Count" field, define how many frames are to be plotted during a
single sweep measurement.
e) To include frames from previous sweeps in the analysis of the new frame (for
"Max Hold", "Min Hold" and "Average" trace modes only), select "Continue
Frame" = "On".
3. Optionally, replace the frame number by a time stamp by toggling "Time Stamp" to
"On".
4. If necessary, adapt the color mapping for the spectrogram to a different value
range or color scheme as described in "How to configure the color mapping"
on page 646.
The value range of the color map must cover at least 10% of the value range on the
horizontal axis of the diagram, that means, the difference between the start and stop
values must be at least 10%.
The value range of the color map can be set numerically or graphically.
To set the value range graphically using the color range sliders
1. Select and drag the bottom color curve slider (indicated by a gray box at the left of
the color curve pane) to the lowest value you want to include in the color mapping.
2. Select and drag the top color curve slider (indicated by a gray box at the right of
the color curve pane) to the highest value you want to include in the color mapping.
2. In the "Stop" field, enter the percentage from the right border of the histogram that
marks the end of the value range.
Example:
The color map starts at -110 dBm and ends at -10 dBm (that is: a range of 100 dB). In
order to suppress the noise, you only want the color map to start at -90 dBm. Thus,
you enter 10% in the "Start" field. The FSW shifts the start point 10% to the right, to
-90 dBm.
To switch off the trace math, use the Trace Math Off button.
Remote command:
CALCulate<n>:MATH<t>[:EXPRession][:DEFine] on page 1259
CALCulate<n>:MATH<t>:STATe on page 1261
I/Q data can only be imported and exported in applications that process I/Q data, such
as the I/Q Analyzer or optional applications.
See the corresponding user manuals for those applications for details.
Trace data that was stored during a previous measurement can be imported to the
Spectrum application, for example as a reference trace.
The data in the import file must have a specified format (see Section 8.6.6, "Reference:
ASCII file export format", on page 659), and can be stored in .CSV or .DAT format.
Trace Mode
The trace mode for the imported traces is set to "View" so that the data is not overwrit-
ten immediately during the next sweep. Other trace settings remain unchanged. Thus,
the displayed trace may not comply with the displayed trace settings in the
channel bar.
Units
If the unit of the y-axis values in the file does not correspond to the active result dis-
play, the imported values are converted. If no unit is defined in the file, it is assumed to
be dBm.
Alternatively, you can import a single trace only, which is displayed for the trace num-
ber specified in "Import to Trace". This list contains all currently active traces in the
result display. If a trace with the specified number exists in the import file, that trace is
imported. Otherwise, the first trace in the file is imported (indicated by a message in
the status bar).
Example:
The import file contains trace 1, trace 2, and trace 4. The current result display has 4
active traces.
"Import to Trace" = 2: trace 2 of the import file is displayed as trace 2 in the result dis-
play.
"Import to Trace" = 3: trace 3 is not available in the import file, thus trace 1 is imported
and displayed as trace 3 in the result display
"Import all Traces" is enabled: Trace 1 is imported from the file and replaces trace 1 in
the result display.
Trace 2 is imported from the file and replaces trace 2 in the result display.
Trace 4 is imported from the file and replaces trace 4 in the result display.
Trace 3 in the result display remains unchanged.
The standard data management functions (e.g. saving or loading instrument settings)
that are available for all FSW applications are not described here.
Trace to Export
Defines an individual trace to be exported to a file.
This setting is not available if Export all Traces and all Table Results is selected.
Decimal Separator
Defines the decimal separator for floating-point numerals for the data export/import
files. Evaluation programs require different separators in different languages.
Remote command:
FORMat:DEXPort:DSEParator on page 1352
X-Value Distribution
Defines how the x-values of the trace are determined in the frequency domain.
See "X-value of the sweep point" on page 619.
"Bin-Centered" The full measurement span is divided by the number of sweep points
to obtain bins. The x-value of the sweep point is defined as the x-
value at the center of the bin (bin/2).
"Start/Stop" (Default): The x-value of the first sweep point corresponds to the
starting point of the full measurement span. The x-value of the last
sweep point corresponds to the end point of the full measurement
span. All other sweep points are divided evenly between the first and
last points.
Remote command:
FORMat:DEXPort:XDIStrib on page 1267
If the spectrogram display is selected when you perform this function, the entire histo-
gram buffer with all frames is exported to a file. The data for a particular frame begins
with information about the frame number and the time that frame was recorded. For
large history buffers the export operation can take some time.
For details on the file format in the Spectrum application, see Section 8.6.6, "Refer-
ence: ASCII file export format", on page 659.
Note: Secure user mode.
In secure user mode, settings that are stored on the instrument are stored to volatile
memory, which is restricted to 256 MB. Thus, a "memory limit reached" error can occur
although the hard disk indicates that storage space is still available.
To store data permanently, select an external storage location such as a USB memory
device.
For details, see Section 4.2.16, "Protecting data using the secure user mode",
on page 41.
For details, see "Protecting Data Using the Secure User Mode" in the "Data Manage-
ment" section of the FSW base unit user manual.
Remote command:
MMEMory:STORe<n>:TRACe on page 1269
MMEMory:STORe<n>:SPECtrogram on page 1379
Example for tabulator (tab after the last column is not visible):
Type FSW13
Version 1.00
Date 01.Jan 3000
The selected column separator setting remains the same, even after a preset.
Remote command:
FORMat:DEXPort:CSEParator on page 1266
Importing Traces
Trace data that was stored during a previous measurement can be imported to the
Spectrum application, for example as a reference trace.
Trace data that was stored during a previous measurement can be imported to the
Spectrum application, for example as a reference trace.
3. Select "Import All Traces" to import traces for all the currently active traces, or
select a specific trace to be imported in "Import to Trace".
7. Select "Select" to close the dialog box and start the import.
The measured trace data and numerical measurement results in tables can be expor-
ted to an ASCII file. For each sweep point, the measured trace position and value are
output.
The file is stored with a .DAT or .CSV extension. For details on the storage format, see
Section 8.6.6, "Reference: ASCII file export format", on page 659.
For the results of a Spectrum Emission Mask (SEM) or Spurious Emissions measure-
ment, special file export functions are available, see Section 6.6.6.2, "How to save
SEM result files", on page 272(SEM) and "Save Evaluation List" on page 292 (Spuri-
ous).
2. Select "Export all Traces and all Table Results" to export all available measurement
result data for the current application, or select a specific "Trace to Export".
5. In the file selection dialog box, select the storage location and file name for the
export file.
6. If necessary, change the decimal separator for the ASCII export file.
8. Select "Save" to close the dialog box and export the data to the file.
You can save the results of a marker peak list to an ASCII file.
3. Configure the peak search and list settings as described in Section 8.3.4.8,
"Marker peak list", on page 584.
5. Press [RUN SINGLE] to perform a single sweep measurement and create a marker
peak list.
6. Select "Marker Peak List" to display the "Marker Peak List" dialog box again.
7. If necessary, change the decimal separator to be used for the ASCII export file.
9. In the file selection dialog box, select the storage location and file name for the
export file.
10. Select "Save" to close the dialog box and export the peak list data to the file.
Trace data can be exported to a file in ASCII format for further evaluation in other appli-
cations. This reference describes in detail the format of the export files for result data.
(For details see Section 8.6.4, "How to export trace data and numerical results",
on page 658)
For a description of the file formats for spectrum emission mask (SEM) measurement
settings and results, see Section 6.6.8, "Reference: SEM file descriptions",
on page 274.
The file format for Spurious Emissions measurement results is described in Sec-
tion 6.7.6, "Reference: ASCII export file format (spurious)", on page 294.
The file consists of the header containing important scaling parameters and a data sec-
tion containing the trace data. Optionally, the header can be excluded from the file (see
"Include Instrument & Measurement Settings" on page 653).
The data of the file header consist of three columns, each separated by a semicolon:
parameter name; numeric value; basic unit. The data section starts with the keyword
"Trace <n>" (<n> = number of stored trace). The measured data follows in one or sev-
eral columns (depending on the measurement), which are also separated by a semico-
lon.
The results are output in the same order as they are displayed on the screen: window
by window, trace by trace, and table row by table row.
Generally, the format of this ASCII file can be processed by spreadsheet calculation
programs, e.g. MS-Excel. Different language versions of evaluation programs can
require a different handling of the decimal point. Thus, you can define the decimal sep-
arator to use (decimal point or comma, see "Decimal Separator" on page 654).
If the spectrogram display is selected when you select "ASCII Trace Export", the entire
histogram buffer with all frames is exported to a file. The data corresponding to a par-
ticular frame begins with information about the frame number and the time that frame
was recorded.
Table 8-11: ASCII file format for trace export in the Spectrum application
Header data
Level Range;100;dB Display range in y direction. Unit: dB with x-axis LOG, % with x-
axis LIN
10000;-10.3;-15.7 Measured values: <x value>, <y1>, <y2>; <y2> being available
10130;-11.5;-16.9 only with detector AUTOPEAK and containing in this case the
smallest of the two measured values for a measurement point.
10360;-12.0;-17.4
...;...;
...
...
Header
Level Range;100;dB Display range in y direction. Unit: dB with x-axis LOG, % with x-
axis LIN
Data section
...
● Managing rules......................................................................................................663
● Defining rules........................................................................................................ 664
● Debugging rules with the EBA-Journal................................................................. 671
● Reference: overview of available result-events and state-events......................... 672
Access: toolbar
The event-based actions manager allows you to configure actions to be performed
when specific events occur in the measurement.
Rule state
Enables/disables processing of the defined rule for the currently active channel only.
Note that the application does not perform a validity check on the rules. For example, if
you change or delete the required command file for a rule, the rule becomes invalid.
However, the application still attempts to process the rule as far as possible. An easy
way to detect such a situation is using the log information, see Section 8.7.3, "Debug-
ging rules with the EBA-Journal", on page 671.
Rule
Name of the rule
Events
Specified trigger events for the rule
Actions
Specified actions to be performed by the rule.
Triggered
Number of trigger events for the rule that occurred since the last instrument preset or
restart.
New Rule
Opens the "Event Based Actions: Add Rule" dialog box to define a new rule as descri-
bed in Section 8.7.2, "Defining rules", on page 664.
Edit Rule
Opens the "Event Based Actions: Modify Rule" dialog box to edit the selected rule as
described in Section 8.7.2, "Defining rules", on page 664.
Copy Rule
Creates a copy of the selected rule and opens the "Event Based Actions: Modify Rule"
dialog box to edit it, as described in Section 8.7.2, "Defining rules", on page 664.
Delete Rule
Deletes the selected event-based action rule.
Show Journal
Shows the logging information for the rules defined in the EBA rule manager. This
information is useful to debug rules when expected actions are not performed. For
details, see Section 8.7.3, "Debugging rules with the EBA-Journal", on page 671.
Access: "Event-based actions" > "New Rule" / "Edit Rule" / "Copy Rule"
Rules are defined individually for each measurement channel. You must activate each
rule for each application individually, and only the currently active channel processes
the rules.
A maximum of 5 rules can be defined for each application. The base unit applications
(Spectrum, I/Q analyzer, Analog Demodulation) are counted together and thus support
a total of 5 rules over all three applications. Rules defined in one application are visible,
but cannot be edited or enabled, in the other two applications. The same applies to dif-
ferent measurements within a single application (e.g. SEM and ACLR).
Rule Name
Defines the unique name for the actions to be taken under specific conditions.
Without a name, the rule cannot be stored.
Event
Defines the event that triggers the action.
Depending on the selected event, further parameters are available.
Action
Defines the actions to be taken when the specified events occur.
Depending on the selected action, further settings are available.
Example:
The definition ScreenShot_[Date]_[Time] creates file names such as
ScreenShot_2018-12-14_12-49-51.PNG,
ScreenShot_2018-12-14_12-50-01.PNG.
Combining an I/Q data export and the "Auto Level" function for the same event stops a
continuous sweep.
Define the path and (generic) file name. The default directory is C:\R_S\INSTR\USER.
If necessary, a consecutive number is added to the specified file name to create unique
file names. Placeholders can be inserted in square brackets to create generic file
names. The placeholders are replaced by current values at the time the data is expor-
ted.
The following placeholders are supported:
● [Date] = [Year]-[Month]-[Day]
● [Time]: =[Hour]-[Minute]-[Second]
Select "Browse" to select the directory for exported data from a file-selection dialog
box.
Add Action
Adds another action to be taken when the specified events occur. You can define up to
3 different actions. The order in which the actions are defined is irrelevant.
If several actions are scheduled due to one or more rules, the actions are performed in
the following order (if specified):
● 1. Store Screenshot
● 2. Auto Level
● 3. Start Program/Script
Any other actions are performed in parallel.
Remove Action
Removes the corresponding action from the rule.
Save
Saves the rule definition. Saving is only available if the rule definition is valid. Invalid
parts of the definition are indicated by red font, for example if the specified command
name, result, or limit line does not exist. Other validity checks are not performed.
Refresh
Updates the journal display to include the latest information (since journal was opened
or last updated).
Clear
Clears all currently stored information in the journal
Debug Logging
If enabled, additional debug information is logged in the journal. Since this information
requires large amounts of storage space and can slow down the performance of the
firmware, use this mode carefully and only when necessary for troubleshooting. Debug
mode is automatically disabled when you close the "EBA Journal" dialog.
Using the event-based actions, you can define actions to be performed depending on
the values or states of specific results (see Result Value and "State Value"
on page 667). The following overview shows you which results and states are available
for which measurements.
Table 8-13: Available result and state events
Channel power ACLR Channel Power ACLR Tx Total Channel Power ACLR
Carrier-to-Noise C/N
C/N0
Spectrum Emission Mask Spectrum Emission Mask Tx Power Spectrum Emission Mask Limit
Check
9 Optimizing measurements
Additional information
An application note discussing measurement speed optimization is available from the
Rohde & Schwarz website:
1EF90: Speeding up Spectrum Analyzer Measurements
Generally, a higher sweep time leads to more data to be averaged and thus stabilizes
the results. In FFT mode, a higher sweep time means more FFTs are calculated and
combined per bin.
Thus, in the same capture time, the FFT mode with an RMS detector can provide bet-
ter results than an averaged trace.
10 Data management
The FSW allows you to store and load instrument settings, as well as import and
export measurement data for analysis later. Finally, you can store or print the measure-
ment results displayed on the screen.
General storage and import/export functions are available via the toolbar. Some special
storage functions are (also) available via softkeys or dialog boxes in the corresponding
menus, for example trace data export.
See Section 8.6, "Importing and exporting measurement results for evaluation",
on page 650 for RF measurements in the Spectrum mode, or the description of the
specific applications.
● Restoring the default instrument configuration (preset)........................................ 676
● Protecting data using the secure user mode.........................................................677
● Storing and recalling instrument settings and measurement data........................ 679
● Import/export functions..........................................................................................691
● Creating screenshots of current measurement results and settings..................... 696
● Working with test reports.......................................................................................712
After you use the [PRESET] function, the history of previous actions is deleted, i.e. any
actions performed previously cannot be undone or redone using the [UNDO/REDO]
keys.
Remote command:
*RST or SYSTem:PRESet
Remote command:
SYSTem:PRESet:CHANnel[:EXEC] on page 1366
Self-alignment data
Note that self-alignment data becomes invalid with time and due to temperature
changes. Therefore, to achieve optimal accuracy, it can be preferable to perform a new
self-alignment at the start of each new session on the FSW.
Windows updates
In secure user mode, in rare cases, Windows updates trigger a reboot. We recommend
using secure user mode on R&S FSW-K33 only in private LAN without access to the
internet or disconnected to LAN to avoid unwanted Windows updates. In preparation
for Windows updates, disable secure user mode temporarily.
Restricted operation
Since permanent storage is not possible, the following functions are not available in
secure user mode:
● Firmware update
● Activating a new option key
Furthermore, since the "SecureUser" used in secure user mode does not have admin-
istrator rights, administrative tasks such as LAN configuration and some general
instrument settings are not available. Refer to the description of the basic instrument
setup ([SETUP] menu) to find out which functions are affected.
Secure passwords
By default, the initial password for both the administrator account and the "Secure-
User" account is "894129". When the secure user mode is activated the first time after
installation, you are prompted to change the passwords for all user accounts to
improve system security. Although it is possible to continue without changing the pass-
words, it is strongly recommended that you do so.
You can change the password in Windows 10 for any user at any time via:
"Start > Settings > Account > SignIn Options > Password > Change"
To deactivate the secure user mode, the "SecureUser" must log off and a user with
administrator rights must log on.
The secure user mode setting and auto-login is automatically deactivated when
another user logs on. The "SecureUser" is no longer available.
For users with administrator rights, the secure user mode setting is available in the
general system configuration settings (see "SecureUser Mode" on page 794).
Remote control
Initially after installation of the R&S FSW-K33 option, secure user mode must be
enabled manually once before remote control is possible.
(See SYSTem:SECurity[:STATe].)
Manual activation is necessary to prompt for a change of passwords.
The "Quick Save" and "Quick Recall" functions allow you to store instrument settings or
channels very easily and quickly in one step. Up to ten different sets of settings can be
stored to or recalled from "save sets". Each save set is identified by its storage date
and type (instrument or specific "Channel") in the display. The save sets are stored in
the C:\R_S\INSTR\QuickSave directory, in files named QuickSave1.dfl to
QuickSave10.dfl. Only the current measurement settings are stored, not any addi-
tional data such as traces, limit line or transducer files (see Section 10.3.2.1, "Stored
data types", on page 683).
Source calibration files for an optional external generator, if available, are included.
During recall, save sets of type "Instrument" replace the settings of the entire instru-
ment. All other save sets start a new channel with the stored settings.
If a channel with the same name as the "Channel" to be restored is already active, the
name for the new channel is extended by a consecutive number:
Access: "Save"/ "Open" icon in the toolbar > "Quick Save" / "Quick Recall"
Both dialog boxes are very similar and closely related.
During recall, save sets of type "Instrument" replace the settings of the entire instru-
ment. All other save sets start a new channel with the stored settings.
Recall
Restores the instrument settings as saved in the selected settings file. If the settings
file contains settings for a specific "Channel" only, a new channel with the stored set-
tings is activated, otherwise all "Channel"s and instrument settings are overwritten with
the stored settings.
Note: After you use the "Recall" function, the history of previous actions is deleted, i.e.
any actions performed previously cannot be undone or redone using the [UNDO/
REDO] keys.
Remote command:
MMEMory:LOAD:STATe on page 1362
The more sophisticated storage and recall functions allow you to define which settings
are stored, and where the settings file is stored to. Any settings file can be selected for
recall.
● Stored data types..................................................................................................683
● Storage location and filename...............................................................................684
● Save and recall dialog boxes................................................................................ 685
● Startup recall settings............................................................................................687
The following types of data can be stored to and loaded from files via the "Save" dialog
box on the FSW:
Item Description
Source Cal Data Source calibration data for an optional external generator
(If available, see "Saving calibration results" on page 382).
The data is stored on the internal flash disk or, if selected, on a memory stick or net-
work drive. The operating system, firmware and stored instrument settings are located
on drive C.
The storage location and filename are selected in a file selection dialog box which is
displayed when you perform a storage function.
By default, the name of a settings file consists of a base name followed by an under-
score and three numbers, e.g. limit_lines_005. In the example, the base name is
limit_lines. The base name can contain characters, numbers and underscores.
The file extension dfl is added automatically. The default folder for settings files is
C:\R_S\INSTR\Save.
To store data permanently, select an external storage location such as a USB memory
device.
For details, see Section 4.2.16, "Protecting data using the secure user mode",
on page 41.
For details, see "Protecting Data Using the Secure User Mode" in the "Data Manage-
ment" section of the FSW base unit user manual.
Remote command:
MMEMory:CATalog on page 1353
File Name
Contains the name of the data file without the path or extension.
By default, the name of a user file consists of a base name followed by an underscore.
Multiple files with the same base name are extended by three numbers, e.g.
limit_lines_005.
File names must be compatible with the Windows conventions for file names. In partic-
ular, they must not contain special characters such as ":", "*", "?".
For details on the filename and location, see Section 10.3.2.2, "Storage location and
filename", on page 684.
Comment
An optional description for the data file. A maximum of 60 characters can be displayed.
Remote command:
MMEMory:COMMent on page 1354
File Explorer
Opens the Microsoft Windows File Explorer.
Remote command:
not supported
File Type
Determines whether the global instrument settings with all "Channel"s are stored or
recalled, or the current "Channel" settings only.
Items:
Defines which data and settings are stored or are recalled. Depending on the "File
Type", either channels only, or global settings are available. Which items are available
also depends on the installed options (see also Section 10.3.2.1, "Stored data types",
on page 683).
Remote command:
MMEMory:SELect[:ITEM]:ALL on page 1358
MMEMory:SELect[:ITEM]:DEFault on page 1359
MMEMory:SELect[:ITEM]:NONE on page 1360
MMEMory:SELect[:ITEM]:HWSettings on page 1359
MMEMory:SELect[:ITEM]:LINes:ALL on page 1359
MMEMory:SELect[:ITEM]:SCData on page 1360
MMEMory:SELect[:ITEM]:SGRam on page 1360
Save File
Saves the settings file with the defined filename.
Note: Secure user mode. In secure user mode, settings that are stored on the instru-
ment are stored to volatile memory, which is restricted to 256 MB. Thus, a "memory
limit reached" error can occur although the hard disk indicates that storage space is
still available.
For details, see Section 4.2.16, "Protecting data using the secure user mode",
on page 41.
Remote command:
MMEMory:STORe<1|2>:STATe on page 1364
MMEMory:STORe<1|2>:STATe:NEXT on page 1364
Startup Recall..............................................................................................................688
Selecting Storage Location - Drive/ Path/ Files...........................................................688
File Name....................................................................................................................689
Comment.....................................................................................................................689
Startup Recall
Activates or deactivates the startup recall function. If activated, the settings stored in
the selected file are loaded each time the instrument is started or preset. If deactivated,
the default settings are loaded.
Note that only instrument settings files can be selected for the startup recall function,
not "Channel" files.
Remote command:
MMEMory:LOAD:AUTO on page 1362
To store data permanently, select an external storage location such as a USB memory
device.
For details, see Section 4.2.16, "Protecting data using the secure user mode",
on page 41.
For details, see "Protecting Data Using the Secure User Mode" in the "Data Manage-
ment" section of the FSW base unit user manual.
Remote command:
MMEMory:CATalog on page 1353
File Name
Contains the name of the data file without the path or extension.
By default, the name of a user file consists of a base name followed by an underscore.
Multiple files with the same base name are extended by three numbers, e.g.
limit_lines_005.
File names must be compatible with the Windows conventions for file names. In partic-
ular, they must not contain special characters such as ":", "*", "?".
For details on the filename and location, see Section 10.3.2.2, "Storage location and
filename", on page 684.
Comment
An optional description for the data file. A maximum of 60 characters can be displayed.
Remote command:
MMEMory:COMMent on page 1354
Instrument settings can be saved to a file and loaded again later, so that you can
repeat the measurement with the same settings. Optionally, user-defined measurement
settings can automatically be restored each time you start or preset the instrument.
To save and recall instrument settings using the Quick Save function
1. Select the "Save" icon from the toolbar.
2. Select whether the instrument settings for all"Channel"s are stored, or only those
for the current"Channel".
3. Select one of the save sets in which the settings are stored ("QuickSaveX").
The selected settings are stored to the file
C:\R_S\INSTR\QuickSave\QuickSaveX.dfl.
Note: If you make any changes to the settings after storing the configuration file,
remember to save the settings again. Otherwise those settings cannot be restored
and will be overwritten by the stored values when the configuration file is recalled.
4. To restore the settings, select the "Open" icon from the toolbar.
5. Select the save set in which the settings were stored ("QuickSaveX").
The selected settings are restored to the instrument or channel.
3. In the file selection dialog box, select a filename and storage location for the set-
tings file.
5. Select whether the instrument settings for all"Channel"s are stored, or only those
for the current"Channel".
6. Select the items to be saved with the settings. Either the settings for the currently
selected "Channel" only, or the settings for all "Channel"s can be stored. Various
other items, such as lines or traces etc., can be stored as well (see Sec-
tion 10.3.2.1, "Stored data types", on page 683).
7. Select "Save".
A file with the defined name and path and the extension .dfl is created.
If you make any changes to the settings after storing the configuration file, remember
to save the settings again. Otherwise those settings cannot be restored and will be
overwritten by the stored values when the configuration file is recalled.
3. In the file selection dialog box, select the filename and storage location of the set-
tings file.
Note: The "File Type" indicates whether the file contains instrument settings for
all"Channel"s, or only those for the current "Channel".
4. If several items were saved, select which items are restored.
5. If a "Channel" was saved, select whether the settings will replace the settings in the
current "Channel", or whether a new channel with the saved settings will be
opened.
6. Select "Recall".
The settings and selected items from the saved measurement are restored and
you can repeat the measurement with the same settings.
Note that any changes made to the settings after storing the configuration file will
be overwritten by the stored values when the configuration file is recalled.
3. From the file selection dialog box, select the recall settings to restore.
I/Q data can only be imported and exported in applications that process I/Q data, such
as the I/Q Analyzer or optional applications.
See the corresponding user manuals for those applications for details.
Import.......................................................................................................................... 692
Export..........................................................................................................................692
└ Export Trace to ASCII File............................................................................ 692
└ File Type............................................................................................. 694
└ Decimal Separator.............................................................................. 694
└ Column Separator...............................................................................694
└ File Explorer........................................................................................694
└ Export Configuration..................................................................................... 694
└ I/Q Export......................................................................................................695
└ File Type............................................................................................. 695
└ File Explorer........................................................................................695
Import
Access: "Save/Recall" > Import
Provides functions to import data.
Importing trace data is only available via the "Trace Config" dialog box, see Sec-
tion 8.6.2, "Trace/data ex/import", on page 652.
I/Q data can only be imported by applications that process I/Q data.
Importing I/Q data is not possible in MSRA operating mode.
See the FSW I/Q Analyzer user manual for more information.
Export
Access: "Save/Recall" > Export
Opens a submenu to configure data export.
If the spectrogram display is selected when you perform this function, the entire histo-
gram buffer with all frames is exported to a file. The data for a particular frame begins
with information about the frame number and the time that frame was recorded. For
large history buffers the export operation can take some time.
For details on the file format in the Spectrum application, see Section 8.6.6, "Refer-
ence: ASCII file export format", on page 659.
Note: Secure user mode.
In secure user mode, settings that are stored on the instrument are stored to volatile
memory, which is restricted to 256 MB. Thus, a "memory limit reached" error can occur
although the hard disk indicates that storage space is still available.
To store data permanently, select an external storage location such as a USB memory
device.
For details, see Section 4.2.16, "Protecting data using the secure user mode",
on page 41.
For details, see "Protecting Data Using the Secure User Mode" in the "Data Manage-
ment" section of the FSW base unit user manual.
Remote command:
MMEMory:STORe<n>:TRACe on page 1269
MMEMory:STORe<n>:SPECtrogram on page 1379
Example for tabulator (tab after the last column is not visible):
Type FSW13
Version 1.00
Date 01.Jan 3000
The selected column separator setting remains the same, even after a preset.
Remote command:
FORMat:DEXPort:CSEParator on page 1266
To print a screenshot of the current display with the current settings immediately, with-
out switching to the "Print" menu, use the "SnapShot" icon in the toolbar.
Print Screenshot..........................................................................................................697
Print Multiple Windows................................................................................................698
Comment.....................................................................................................................698
Print Logo....................................................................................................................698
Print Page Count.........................................................................................................698
Select Device 1/2........................................................................................................ 698
Print Dialog..................................................................................................................699
Print Date and Time.................................................................................................... 699
Print Screenshot
Selects all measurement results displayed on the screen for the current channel (or
"MultiView"): diagrams, traces, markers, marker lists, limit lines, etc., including the
channel bar and status bar, for printout on a single page. Displayed items belonging to
the software user interface (e.g. softkeys) are not included. The position and size of the
elements in the printout is identical to the display.
This setting is independent of the printing device.
Remote command:
HCOPy:CONTent on page 1367
Comment
Defines an optional comment to be included in the printout of the display. Maximum
120 characters are allowed. Up to 60 characters fit in one line. In the first line, a man-
ual line-feed can be forced at any point by entering "@".
The comment is printed in the top left corner of each printout page. If a comment
should not be printed, it must be deleted.
This setting is independent of the printing device.
Tip: The current date and time can be inserted automatically, see "Print Date and
Time" on page 699.
Remote command:
HCOPy:ITEM:WINDow:TEXT on page 1372
Print Logo
Activates/deactivates the printout of the Rohde & Schwarz company logo in the upper
right corner.
This setting is independent of the printing device.
Remote command:
DISPlay:LOGO on page 1367
Two different printout devices can be configured, for example one for printing and one
for storage to a file. When you execute the "SnapShot" function, the selected printing
device and its settings determine the behavior of the FSW.
Print Dialog
Includes any currently displayed dialog in the screenshot printout.
This setting is (printing) device-specific and only available if Print Screenshot is
selected.
Access: "Print"
The "Print Preview" of the printout according to the current configuration is available in
all "Print Settings" dialog tabs.
The preview display (not the functions) is device-specific (see "Select Device 1/2"
on page 698).
Fit Page
Adapts the preview display zoom factor so that one complete page is visible as large
as possible in the available display space. Note that the zoom functions affect only the
preview, not the printout itself.
Zoom 1:1
Displays the printout in its original size, as it will be printed.
Print
Starts to print or store the selected screen contents to a file (see Section 10.5.1.1,
"Print content settings", on page 696).
Whether the output is sent to the printer or stored in a file or the clipboard depends on
the selected printing device and the printing device settings (see Section 10.5.1.3,
"Printer settings", on page 701).
If the output is stored to a file, a file selection dialog box is opened to select the file-
name and location. The default path is C:\R_S\INSTR\USER.
Remote command:
HCOPy[:IMMediate] on page 1372
HCOPy[:IMMediate]:NEXT on page 1372
Printer settings are (printing) device-specific. That means you can configure two differ-
ent printing devices (for example, a printer and a file) and switch between configura-
tions easily simply by selecting the appropriate device before printing.
Two different printout devices can be configured, for example one for printing and one
for storage to a file. When you execute the "SnapShot" function, the selected printing
device and its settings determine the behavior of the FSW.
Destination
Defines the medium to which the printout is output.
Printer Name
Defines the printer to print to if a printer is selected as the Destination.
Any printers detected in the network are listed for selection.
Tip: the printout can also be stored in a print file using the selected printer driver, see
"Print to file" on page 704.
Remote command:
SYSTem:COMMunicate:PRINter:ENUMerate[:NEXT] on page 1376
SYSTem:COMMunicate:PRINter:ENUMerate:FIRSt on page 1376
SYSTem:COMMunicate:PRINter:SELect<di> on page 1377
Print to file
If a printer is selected as the Destination, use this option to store the data in a .prn file
using the selected printer driver.
Remote command:
To enable: HCOP:DEST1 'MMEM'
To disable: HCOP:DEST1 'SYSTem:COMMunicate:PRINter'
Install Printer
This softkey opens the standard Windows dialog box to install a new printer. All print-
ers that are already installed are displayed.
Only user accounts with administrator rights can install a printer.
For further information, refer to the Microsoft Windows documentation.
Page settings are (printing) device-specific. That means you can configure two differ-
ent printing devices (for example, a printer and a file) and switch between configura-
tions easily simply by selecting the appropriate device before printing.
Page settings are only available when printing on a printer or to a PDF file (see "Desti-
nation" on page 703).
Select Device 1/2........................................................................................................ 705
Orientation...................................................................................................................706
Windows Per Page......................................................................................................706
Scaling........................................................................................................................ 706
Margins....................................................................................................................... 706
Orientation
Selects the page orientation of the printout: portrait or landscape.
Remote command:
HCOPy:PAGE:ORIentation on page 1374
Scaling
Determines the scaling of the windows in the printout if Print Multiple Windows is active
(see Section 10.5.1.1, "Print content settings", on page 696).
If more than one window is printed on one page (see Windows Per Page), each win-
dow is printed in equal size.
"Maintain Each window is printed as large as possible while maintaining the
aspect ratio" aspect ratio of the original display.
"Size to fit" Each window is scaled to fit the page size optimally, not regarding the
aspect ratio of the original display.
Remote command:
HCOPy:PAGE:WINDow:SCALe on page 1375
Margins
Defines margins for the printout page on which no elements are printed. The margins
are defined according to the selected unit.
Remote command:
HCOPy:PAGE:MARGin:BOTTom on page 1373
HCOPy:PAGE:MARGin:LEFT on page 1373
HCOPy:PAGE:MARGin:RIGHt on page 1373
HCOPy:PAGE:MARGin:TOP on page 1373
HCOPy:PAGE:MARGin:UNIT on page 1374
The settings provided here are identical to those in the "Print Colors" section of the
"Display" > "Theme + Color" dialog box.
See "Print Colors" on page 743.
See the FSW User Manual.
The measurement results displayed on the screen can be printed or stored to a file
very easily.
Two different scenarios can be configured in parallel, assigned to different printing
devices. You can then perform one or the other simply by selecting the corresponding
printing device and the "Print" function.
To print a screenshot
This configuration assumes a printer has already been installed. To install a new
printer, use the Install Printer function (common Microsoft Windows procedure).
1. Select the "Printer" tool in the toolbar.
The "Print Settings" dialog box is displayed.
2. Select "Device 1" or "Device 2" to define which printing device you want to config-
ure.
(Note: Some settings are independent of the printing-device.)
3. In the "Content" tab, define the elements of the screen and additional information to
be included in the printout.
a) Select "Print Screenshot" to include all elements displayed on the screen in a
single-page printout.
b) Optionally, add a comment to be printed at the top of the printout.
c) Optionally, activate the date and time or the logo so they are added to the print-
out.
d) Optionally, activate "Print Dialog" to include any dialog boxes currently dis-
played on the screen in the printout. This is useful, for example, to document
the used settings for a particular result.
e) Check the "Print Preview" to make sure all relevant elements of the display are
visible.
5. Select the "Printer Name" to print to from the list of installed printers.
6. In the "Page Setup" tab, configure the layout of the printout page.
a) Select the page orientation.
b) Define the page margins.
c) Check the "Print Preview" to make sure all relevant elements of the display are
visible.
7. In the "Color" tab, define the colors to be used for the printout.
a) By default, "Optimized Colors" are used to improve the visibility of the colors.
The background is always printed in white and the grid in black.
For a printout that reflects exactly what you see on the screen, select "Screen
Colors (Screenshot)".
b) Check the "Print Preview" to find out if the setting is appropriate.
9. To print another screenshot using the same configuration any other time, simply
press the "SnapShot" icon on the toolbar.
If you use different printing scenarios alternately, perform the following steps to
print another screenshot:
a) Select the "Printer" tool in the toolbar.
b) Select "Device 1" or "Device 2" to select the configured printing device.
c) Select "Print" to execute the print function.
2. Select "Device 1" or "Device 2" to define which printing device you want to config-
ure.
3. In the "Content" tab, define the elements of the screen and additional information to
be included in the printout.
a) Select "Print Selected Windows" to include the selected windows in the print-
out, possibly on multiple pages.
b) Select the result displays in the currently selected channel to be included in the
printout.
Tip: Select the "MultiView" before configuring the printout to include result dis-
plays from any active channel.
c) Optionally, add a comment to be printed at the top of each page of the printout.
d) Optionally, activate the date and time or the logo so they are added to the print-
out pages.
4. Check the "Print Preview" to make sure all required result displays are included.
a) Scroll through the individual pages of the printout using "Page Up" and "Page
Down".
b) Use the zoom functions to make sure all relevant parts of the result display are
visible.
7. By default, you define the filename individually for each print operation. To avoid
having the "File Selection" dialog box being displayed for each print operation,
select "Suppress File Name Dialog". In this case, the previously used or default
storage location and filename are used.
(C:\R_S\INSTR\USER\FSW_ScreenShot_<date and time>).
8. In the "Page Setup" tab, configure the layout of the printout page.
a) Select the page orientation.
b) Define the page margins.
c) Check the "Print Preview" to make sure all relevant elements of the display are
visible.
9. In the "Color" tab, define the colors to be used for the printout.
a) By default, "Optimized Colors" are used to improve the visibility of the colors.
The background is always printed in white and the grid in black.
For a printout that reflects the colors you see on the screen, but with a white
background, select "Screen Colors (Print)".
b) Check the "Print Preview" to find out if the setting is appropriate.
11. If you did not select the option to suppress the dialog, enter a filename in the file
selection dialog box.
The selected data elements are stored to the file as configured.
12. To store another file using the same configuration any other time, simply select the
"Print immediate" icon on the toolbar.
If you use different printing scenarios alternately, perform the following steps to
store another file:
a) Select the "Printer" tool in the toolbar.
b) Select "Device 1" or "Device 2" to select the configured printing device.
c) Select "Print" to execute the print function.
The following example describes the procedure to store results from measurements in
the Spectrum application and the I/Q Analyzer to a single PDF file.
1. Configure and perform the measurements in the Spectrum application and I/Q
Analyzer as required. Configure at least the following result displays:
● Frequency Sweep, Spectrogram (Spectrum)
● Magnitude, Spectrum (I/Q Analyzer)
2. Switch to the "MultiView" tab to display an overview of the result displays in all
active channels.
4. Select "Device 1" to configure the settings for this printing device.
7. Enter the comment Measurement Test Report to be inserted at the top of each
page.
14. Select "Windows Per Page": 1 to print a single result display on each page.
15. Select the "Scaling" option "Size to fit" to maximize the result display on each page.
16. In the "Color" tab, select "Screen Colors (Print)" for a printout that reflects the col-
ors you see on the screen, but with a white background.
17. Check the "Print Preview" to make sure all required result displays are included
and all relevant data elements are visible.
a) Scroll through the individual pages of the printout using "Page Up" and "Page
Down".
b) Use the zoom functions to make sure all relevant parts of the result display are
visible.
The FSW features a test report generator. A test report is a document that summarizes
the results and configuration of measurements.
A test report is made up of one or more datasets. Each dataset contains the results
and configuration of one measurement.
Test reports are based on a general template, and are completed with user-defined,
measurement-specific contents. You can create multiple templates for different applica-
tions.
Currently, test reports are only supported in the Spectrum application, for all measure-
ment types.
Test reports require the R&S FSW-K54 option to be installed on the FSW.
1
2
3
To see the result of your template configuration, use the Show Preview function.
● General contents...................................................................................................715
● Title page.............................................................................................................. 716
● Measurement information..................................................................................... 719
● Application-specific contents.................................................................................721
Access: > "Report menu" > "Templates" > "General" > "▽" > "General"
The "General" area defines general properties of the report document.
Page format.................................................................................................................715
File type.......................................................................................................................715
Use Screen Colors...................................................................................................... 715
Date.............................................................................................................................716
Page Count................................................................................................................. 716
Report Path................................................................................................................. 716
└ Suppress Dialog............................................................................................716
Raw Data Storage.......................................................................................................716
Page format
Selects the format of the document (A4 or "Letter" format).
Remote command:
HCOPy:TREPort:PAGesize on page 1388
File type
Selects the file type (*.pdf or *.doc).
Remote command:
HCOPy:DEVice:LANGuage on page 1371
Date
Adds the current date to each page of the report.
Remote command:
HCOPy:TREPort:TDSTamp:STATe on page 1388
Page Count
Adds page numbers to each page of the report.
Remote command:
HCOPy:TREPort:PAGecount:STATe on page 1387
Report Path
Defines the location where the report file is saved.
Enter the path in the input field, or select the directory using the "..." button.
If you omit the path, the report is saved in the default directory (C:\R_S\INSTR\USER).
Note: This path defines the location of the actual test report. Templates are stored in a
different location (see "Save" on page 723).
Remote command:
MMEMory:NAME on page 1356
Access: > "Report menu" > "Templates" > "General" > "▽" > "Title Page"
You can define an optional title page for the test report with a title and a short descrip-
tion of the report contents. It is only included in the report if you enable it.
Access: > "Report menu" > "Templates" > "General" > "▽" > "Measurement Informa-
tion"
The "Measurement Information" area allows you to add user-defined information on the
measurement to the report.
You can add up to six lines to the report, plus one picture, for example a company logo.
The first line is a heading. Each of the following five lines consists of a title and a value,
which is displayed next to the title. The information can be global, that is: valid for the
entire report, or specific to an individual measurement. In this case, you define the
actual value when you store the measurement data.
Figure 10-4: Dialog box for measurement information when appending data to a report
State............................................................................................................................720
Title..............................................................................................................................720
Value........................................................................................................................... 720
Visibility....................................................................................................................... 720
Logo............................................................................................................................ 721
State
Enables or disables the user-defined measurement information on the test report.
Remote command:
HCOPy:TREPort:ITEM:HEADer:STATe on page 1383
Title
Defines a title for the type of information, for example "Test equipment" for the name of
the device under test. Default titles are provided, but you can change and customize
each title, except for the initial "heading". A maximum of 17 characters are available.
For data that is specific to an individual measurement, this title is used in the dialog
box asking you to provide the information when you append the measurement results
to the report.
Remote command:
HCOPy:TREPort:ITEM:HEADer:LINE<li>:TITLe on page 1383
Value
Defines the actual text for the content defined by the title. A maximum of 25 characters
are available.
For data that is specific to an individual measurement, you are asked to provide this
information when you append the measurement results to the report.
Remote command:
HCOPy:TREPort:ITEM:HEADer:LINE<li>:TEXT on page 1382
Visibility
Determines the validity of the content and thus when the contents are configured and
where the line is displayed in the report.
"Never" (Default): Contents are ignored.
"Global" Contents are valid globally for the entire report. They are configured
in the template and included on each page.
"Subreport" Contents are valid for an individual measurement only. They are con-
figured when you append the measurement results to the report, and
included once for each subreport (measurement).
Remote command:
HCOPy:TREPort:ITEM:HEADer:LINE<li>:CONTrol on page 1381
HCOPy:TREPort:ITEM:LOGO:CONTrol on page 1384
Logo
Includes a picture or logo in the report. Enter the path and filename in the input field, or
select the directory using the "..." button.
The following formats are supported:
● .bmp
● .jpg
● .png
● .gif
● .emf
● .wmf
Remote command:
HCOPy:TREPort:ITEM:LOGO on page 1384
For each application, you can select which graphical results, numerical results, or infor-
mation on the measurement setup to include in the report. Information that is to be
included in the test report is represented by a blue button. Information not included is
represented by a gray button. Some information is only included if it is also displayed
for the measurement, indicated by an asterisk (*).
For the FSW, test reports are only available in Spectrum mode, and only if the
R&S FSW-K54 is installed.
Template name............................................................................................................722
Save............................................................................................................................ 723
Load............................................................................................................................ 723
Default.........................................................................................................................723
Template name
Enter the path and filename of the template in the input field, or select the directory
using the "..." button.
If you omit the path, the template is saved in the default directory (C:\R_S\INSTR
\USER).
Remote command:
Query available templates: HCOPy:TREPort:ITEM:TEMPlate:CATalog?
on page 1386
Save
Saves the current test report configuration as a template to the specified Template
name.
Remote command:
HCOPy:TREPort:ITEM:TEMPlate:SAVE on page 1387
Load
Restores the selected test report configuration.
Remote command:
HCOPy:TREPort:ITEM:TEMPlate:LOAD on page 1386
Default
Restores the default template configuration.
Remote command:
HCOPy:TREPort:ITEM:DEFault on page 1381
Access: Toolbar:
Before you can print a test report, you have to create report data.
Test report data is organized in datasets. Each dataset contains the information for one
measurement. A dataset can contain several subsets for different kinds of data for a
single measurement, for example settings and a result summary.
You create new datasets manually after a measurement.
Datasets are stored in the directory specified in "Raw Data Storage" on page 716.
After creating a dataset, you can view the details in the "Preview" dialog box (see
"Show Preview" on page 726).
Report New............................................................................................................. 723
Report Append........................................................................................................724
Report New
Deletes all currently stored datasets and creates a new one. Note that the dataset is
only written to an actual report when you select Save.
Remote command:
HCOPy:TREPort:NEW on page 1387
Report Append
Adds a new dataset to the existing ones for the next test report. If measurement-spe-
cific data is configured in the report template, a dialog box prompts you to provide the
information for the appended dataset. Note that the dataset is only written to an actual
report when you select Save.
Remote command:
HCOPy:TREPort:APPend on page 1381
File type.......................................................................................................................724
Save............................................................................................................................ 725
Selecting items to include in the report....................................................................... 725
└ Remove All....................................................................................................725
Show Preview............................................................................................................. 726
File type
Selects the file type of the report (*.pdf or *.doc).
Remote command:
HCOPy:DEVice:LANGuage on page 1371
Save
Access: > "Report menu" > "Save"
Saves the test report with the selected items to the selected Report Path with the
selected File type. If the option Suppress Dialog is enabled, the report is saved to the
directory specified in the general contents area (see Report Path).
Tip: before saving the report, check the contents using the Show Preview function.
Remote command:
Print mode: HCOPy:MODE on page 1381
Report name and directory: MMEMory:NAME on page 1356
Print report: HCOPy[:IMMediate] on page 1372
Show Preview
If enabled, a preview of the current test report configuration and contents is displayed.
Note that it can take a short time until the preview has been created.
The preview area provides typical viewing functions as in common PDF viewers.
Using a test report you can summarize the results and configuration of measurements
in a document directly from the Spectrum application.
3. Optionally, in the "Title Page" area, configure a separate title page with a title and
description of the report.
7. If you want to create multiple test report configurations, save the configuration as a
template.
a) Enter a name for the test report template.
b) Select "Save" to save the template.
2. If you want to use one of multiple predefined test report configurations, load the
required template.
a) Select the "..." button at the bottom of the "Templates" tab to select the precon-
figured template for your report.
b) Select "Load".
The preconfigured report template is loaded to the dialog box.
4. When the measurement is finished, save the results for your report:
From the toolbar, select > "Report new" to delete any existing report data and
start a new report.
6. When you are ready to create the report, from the toolbar, select > "Report
menu" > "Preview".
7. Optionally, remove any datasets you do not want to include in the report, for exam-
ple due to false measurement settings.
In the "Select items to include in the report" area, select the "X" to remove an item.
8. Optionally, use the browser functions to view the report preview in more detail.
9. Select "Save".
A file selection dialog box is displayed, unless you enabled the "Suppress dialog"
option in the general template settings.
10. Select the file name and path for the report.
2. When the measurement is finished, save the results for your report:
From the toolbar, select "Report New".
4. When you are ready to create the report, from the toolbar, select > "Report
menu" > "Save".
A file selection dialog box is displayed, unless you enabled the "Suppress dialog"
option in the general template settings.
6. Select "OK".
The test report is saved to the selected location.
● Alignment.............................................................................................................. 728
● Display settings..................................................................................................... 736
● Application starter................................................................................................. 751
● Transducers.......................................................................................................... 756
● Frequency response correction (R&S FSW-K544)............................................... 769
● Reference frequency settings............................................................................... 781
● System configuration settings............................................................................... 785
● Service functions...................................................................................................798
● Synchronizing measurement channel configuration............................................. 805
11.1 Alignment
When you put the instrument into operation for the first time or when strong tempera-
ture changes occur, align the data to a reference source (see "Temperature check"
on page 729).
The firmware determines the correction data and characteristics required for the align-
ment. It compares the results at different settings with the known characteristics of the
high-precision calibration signal source at 64 MHz.
Basic operation of the FSW can be affected before or after a self-alignment in the fol-
lowing ways:
● Depending on the installation settings, an automatic self-alignment is performed
directly after installation, and a dialog is displayed indicating how much warm-up
time is still required before self-alignment can be performed.
● During instrument start, the firmware checks whether the installed hardware is sup-
ported. If not, an error message is displayed ("Wrong Firmware Version") and you
are asked to update the firmware. Until the firmware version is updated, self-align-
ment fails.
● When you start self-alignment, a self-test is automatically performed first.
For details on the self-test, see Section 11.8.2, "Self-test settings and results",
on page 800.
● By default, a reminder is shown in the status bar of the instrument 30 days after the
last self-alignment took place. You can enable or disable the reminder, and change
the timing for it.
Tip: To check for a self-alignment reminder message in the status history, use the
SYStem:ERRor:EXTended? command and search for messages that start with
Self alignment older than. In addition, you can check bit 12 in the
STATus:OPERation register.
● A reminder is shown in the status bar of the instrument if the temperature changes
by more than 10 degrees compared to the last self-alignment took place.
Tip: To check if the temperature has changed, check bit 0 in the
STATus:QUEStionable:TEMPerature register.
● If you start a self-alignment remotely and then select "Local" while the alignment is
still running, the instrument only returns to the manual operation state after the
alignment is completed.
● During self-alignment, do not connect a signal to the RF input connector. Running
a self-alignment with a signal connected to the RF input can lead to false measure-
ment results.
Alignment results
The alignment results are displayed and contain the following information:
● Date and time of last correction data record
● Overall results of correction data record
● List of performed alignment steps
The results are classified as follows:
CHECK Deviation of correction value larger than expected, correction could however be per-
formed
FAILED Deviations of correction value too large, no correction was possible. The found cor-
rection data is not applicable.
The results are available until the next self-alignment process is started or the instru-
ment is switched off.
Temperature check
During self-alignment, the instrument's frontend temperature is measured (if activated,
only after the instrument has warmed up completely, see "Await Warm-Up Operation
before Self Alignment" on page 733). This temperature is used as a reference for a
continuous temperature check during operation. If the current temperature deviates
from the stored self-alignment temperature by a certain degree, a warning is displayed
in the status bar. The warning indicates the resulting deviation in the measured power
levels. A status bit in the STATUs:QUEStionable:TEMPerature register indicates a
possible deviation. The current temperature of the frontend can be queried using a
remote command (see SOURce<si>:TEMPerature:FRONtend on page 1406).
Touchscreen alignment
When the device is delivered, the touchscreen is initially calibrated. However, to ensure
that the touchscreen responds to the finger contact correctly, a touchscreen alignment
is required.
Alignment of the touchscreen is useful:
● At first use
● After an image update or after exchanging a hard disk
● If you notice that touching a specific point on the screen does not achieve the cor-
rect response
● If the position of the instrument has been changed and you cannot look straight on
the screen
● If another person operates the instrument
Automatic self-alignment
During installation of the FSW firmware, you can configure an automatic self-alignment
to be performed directly after installation. In addition, you can activate a preceding
warmup time before self-alignment, which is strongly recommended. If you do not acti-
vate this option, make sure the instrument has reached its operating temperature
before installing the firmware. Furthermore, you can force the instrument to shut down
after self-alignment. Note, however, that you cannot switch the instrument back on
remotely afterwards.
The additional settings for self-alignment can also be activated or deactivated during
operation in the "Alignment" settings dialog (see Await Warm-Up Operation before Self
Alignment and Shut down Device after Self Alignment.)
Schedule
If enabled, a self-alignment is performed regularly at specific days and time.
Remote command:
CALibration:DUE:SCHedule on page 1400
CALibration:DUE:DAYS on page 1399
CALibration:DUE:TIME on page 1401
Align all
Performs an extended self-alignment as performed in the factory. Any previous self-
alignment results are deleted.
Note that this process takes longer than the common self-alignment.
Remote command:
CALibration[:ALL] ACLear
Regular Reminder
Schedules a regular reminder for self-alignment. By default, a reminder is shown in the
status bar of the instrument 30 days after the last self-alignment took place.
Enable or disable the reminder as required.
If enabled, define the number of days after the last self-alignment that the reminder
appears.
Remote command:
To query whether a reminder is being displayed (self-alignment overdue):
CALibration:INFO:OLD? on page 1402
Alignment Results:
Information on whether the alignment was performed successfully and on the applied
correction data is displayed. The results are available until the next self-alignment
process is started or the instrument is switched off.
Remote command:
CALibration:RESult? on page 1403
You do not have to repeat the self-test every time you switch on the instrument. It is
only necessary when instrument malfunction is suspected.
Operating temperature
Before performing this alignment, make sure that the instrument has reached its oper-
ating temperature.
For details, refer to the specifications document.
1. Select [SETUP].
2. Select "Service".
3. Select "Selftest".
Once the instrument modules have been checked successfully, a message is dis-
played.
Operating temperature
Before performing this alignment, make sure that the instrument has reached its oper-
ating temperature.
For details, refer to the specifications document.
To perform a self-alignment
Make sure no signal is connected to the RF input connector. Running a self-alignment
with a signal connected to the RF input can lead to false measurement results.
1. Select [SETUP].
2. Select "Alignment".
2. Select "Alignment".
Select "Set Date and Time" in the "Display" dialog box, or select the date and time dis-
play in the status bar to open the Windows dialog box.
Remote command:
SYSTem:DATE on page 1433
SYSTem:TIME on page 1433
Toolbar........................................................................................................................ 739
Status Bar................................................................................................................... 739
Softkey Bar..................................................................................................................739
Channel Bar................................................................................................................ 739
Diagram Footer (Annotation).......................................................................................739
Date and Time.............................................................................................................739
Front Panel..................................................................................................................740
Mini Front Panel.......................................................................................................... 740
Toolbar
The toolbar provides access to frequently used functions via icons at the top of the
screen. Some functions, such as zooming, finding help, printing screenshots or storing
and loading files are not accessible at all without the toolbar.
Remote command:
DISPlay:TBAR[:STATe] on page 1431
Status Bar
The status bar beneath the diagram indicates the global instrument settings, the instru-
ment status and any irregularities during measurement or display.
Some of the information displayed in the status bar can be queried from the status reg-
istry via remote commands, see Section 13.11, "Using the status register",
on page 1483.
We recommend displaying the status bar at all times. If you hide the status bar, you
can miss important error messages.
Remote command:
DISPlay:SBAR[:STATe] on page 1431
Softkey Bar
Softkeys are virtual keys provided by the software. Thus, more functions can be provi-
ded than can be accessed directly via the function keys on the device.
The functions provided by the softkeys are often also available via dialog boxes. How-
ever, some functions are not accessible at all without the softkey bar.
Note: The softkey bar is hidden while the SmartGrid is displayed and restored auto-
matically when the SmartGrid is closed.
Remote command:
DISPlay:SKEYs[:STATe] on page 1431
Channel Bar
The channel bar provides information on firmware and measurement settings for a
specific channel.
Remote command:
DISPlay:ANNotation:CBAR on page 1430
You can set the current date and time and configure the display format in the "General"
tab of the "Display" dialog box.
Remote command:
DISPlay[:WINDow<n>]:TIME on page 1432
Front Panel
The "Front Panel" display simulates the entire front panel of the device (except for the
external connectors) on the screen. Thus, you can interact with the FSW without the
keypad and keys on the front panel of the device. That is useful, for example, when
working with an external monitor or operating via remote control from a computer.
To hide or show the front panel temporarily, press [F6] on the external keyboard (if
available) or the remote computer.
For more information, see Section 11.2.3, "How to work with the soft front panels",
on page 748.
Remote command:
SYSTem:DISPlay:FPANel[:STATe] on page 1433
For more information, see Section 11.2.3, "How to work with the soft front panels",
on page 748.
Note:
You can also show the mini front panel using the key combination [ALT + m] (be aware
of the keyboard language defined in the operating system!). That is useful when you
are working from a remote PC and the front panel function is not active.
Remote command:
SYSTem:DISPlay:FPANel[:STATe] on page 1433
For step-by-step instructions see Section 11.2.2, "How to configure the colors for dis-
play and printing", on page 747.
Theme......................................................................................................................... 742
Screen Colors............................................................................................................. 742
Print Colors................................................................................................................. 743
Showing Print Colors on Display.................................................................................743
Modifying User-Defined Color Assignments............................................................... 743
└ Selecting the Object......................................................................................744
└ Predefined Colors......................................................................................... 744
└ Preview......................................................................................................... 744
Defining User-specific Colors......................................................................................745
Restoring the User Settings to Default Colors............................................................ 745
Theme
The theme defines the colors and style used to display softkeys and other screen
objects.
The default theme is "IndustrialDark".
Remote command:
DISPlay:THEMe:SELect on page 1435
Screen Colors
Two different color sets are provided by the instrument, a third user-defined set can be
configured.
The default color schemes provide optimum visibility of all screen objects when regard-
ing the screen from above or below. Default setting is "Default Colors 1".
If "User Defined Colors" is selected, a user-defined color set can be defined (see
"Defining User-specific Colors" on page 745).
Remote command:
DISPlay:CMAP<it>:DEFault<ci> on page 1434
Print Colors
Defines the color settings used for printout.
In addition to the predefined settings, a user-defined color set can be configured (see
"Defining User-specific Colors" on page 745).
If "Show Print Colors on Display" is activated, the currently selected print colors are
displayed as a preview for your selection.
"Screen Colors (Print)" Selects the current screen colors for the HCOP:CMAP:DEF1
printout. The background is always printed in
white and the grid in black.
"Screen Colors Selects the current screen colors without any HCOP:CMAP:DEF4
(Screenshot)" changes for a screenshot.
Remote command:
HCOPy:CMAP<it>:DEFault<ci> on page 1368
The color palette allows you to select the color directly. The color settings allow you to
define values for tint, saturation and brightness.
Remote command:
HCOPy:CMAP<it>:HSL on page 1369
Setup...........................................................................................................................746
Screen Resolution: Restore to Default........................................................................746
Setup
Opens the standard Windows configuration dialog box to configure the used display
devices.
Level Lock
If activated (default), the reference level (and thus the attenuation) is locked, that is:
remains unchanged during touch gestures on the screen.
X-Lock
If activated, the x-axis of the diagram is not changed during subsequent touch ges-
tures.
Y-Lock
If activated, the y-axis of the diagram is not changed during subsequent touch ges-
tures.
You can configure the style and colors with which various screen objects are displayed
or printed.
5. Activate the "Show Print Colors on Display" option to see a preview of the print col-
ors.
3. From the "Selected Object:" list, select the object to which you want to assign a
color.
6. Select the next object to which you want to assign a color from the "Selected
Object:" list.
7. Repeat these steps until you have assigned a color to all objects you want to con-
figure.
Basic operation with the soft front panels is identical to normal operation, except for the
following aspects:
● To activate a key, select the key on the touchscreen.
● To simulate the use of the rotary knob, use the additional keys displayed between
the keypad and the arrow keys:
Icon Function
Turn left
Enter
Turn right
To hide or show the front panel, press [F6] on the external keyboard (if available) or on
the remote computer.
To hide or show the "Mini Front Panel", double-click the title of the softkey menu. As an
alternative, press [ALT + m] (be aware of the keyboard language defined in the operat-
ing system!) on the external keyboard (if available) or on the remote computer.
The mini front panel provides an alternative way to access the functionality of the hard-
keys when you are operating the instrument remotely. You can access the keys either
using a mouse or using keyboard shortcuts on the remote computer. The follow table
provides an overview of the assigned keyboard shortcuts for a German keyboard lay-
out. Be aware of the keyboard language defined in the operating system!
To hide or show the "Mini Front Panel", double-click the title of the softkey menu. As an
alternative, press [ALT + m].
[Freq.] [Alt+Shift+J]
[Span] [Alt+Shift+K]
[Ampt./Scale] [Alt+Shift+C]
[BW] [Alt+Shift+L]
[Sweep] [Alt+Shift+M]
[Trace] [Alt+Shift+F]
[Trigger] [Alt+Shift+S]
[Meas] [Alt+Shift+A]
[Lines] [Alt+Shift+B]
[Input/Output] [Alt+Shift+I]
[Marker] [Alt+Shift+G]
[Undo] [CTRL+Shift+U]
[Redo] [CTRL+Shift+R]
[Setup] [Alt+Shift+T]
[Print] [Alt+CTRL+P]
[File] [CTRL+S]
[Mode] [Alt+Shift+P]
[CTRL+M]
[CTRL+N]
[Preset] [Alt+Shift+U]
Access: Toolbar
The "Application Starter" dialog box provides different tabs for different types of appli-
cations:
● "External Applications": contains applications that are provided with, but are not
part of the FSW, such as auxiliary tools
● "User Applications": contains any user-defined applications that can be accessed
from the FSW, such as command scripts
● "R&S Applications": contains applications predefined by Rohde & Schwarz to
enhance the functionality of your FSW
You can add further applications to the "User Applications" and "External Applications"
tabs as you like. They are separated only to improve usability if you have a large num-
ber of applications. You cannot edit the "R&S Applications" tab.
Application buttons
Start the selected application directly on the FSW. Any application windows, outputs, or
results are displayed on the FSW screen.
Remote command:
SYSTem:PLUGin:APPStarter:EXECute on page 1480
This function is not available for applications on the "R&S Applications" tab.
Remote command:
For data security reasons, executable applications cannot be added to the Application
Starter remotely.
Edit Properties
Access: Application button context menu
Tip:
For .inp files, the IECWIN tool provided by Rohde & Schwarz to execute scripts is
preselected as the application to start. The script is defined as the parameter for the
application. The file name without the extension is used as the application name. The
IECWIN icon is selected as the application icon.
Remote command:
SYSTem:PLUGin:APPStarter:SELect on page 1482
Delete Link
Access: Application button context menu
Removes the application from the "Application Starter" dialog box and the toolbar.
This function is not available for applications on the "R&S Applications" tab.
Remote command:
SYSTem:PLUGin:APPStarter:DELete on page 1480
Add to Toolbar
Access: Application button context menu
Inserts the specified application icon in the FSW toolbar.
To start an application
1. Select the Application Starter icon from the toolbar.
The "Application Starter" dialog box is displayed.
2. Press [Alt]+[Tab].
3. Select the file type of the application to filter the file selection in the dialog box.
5. Select "Select".
The "Edit Properties" dialog box is displayed.
8. Define the name to be displayed on the button in the "Application Starter" dialog
box.
9. Select an icon to be displayed on the button in the "Application Starter" dialog box
and optionally in the toolbar.
11.4 Transducers
The transducer allows you to manipulate the trace at discrete trace points to correct
the signal coming from an input device. Transducers are often used to correct the fre-
quency response for antennas, for example. The transducer is configured by defining
transducer factors for specific trace points. A set of transducer factors defines an inter-
polated transducer line and can be stored on the instrument.
In the Spectrum application, the correction factor from all active transducers is calcula-
ted for each displayed trace point once in advance and is added to the result of the
level measurement during the sweep. If the sweep range changes, the correction val-
ues are calculated again. If several measured values are combined in one point, only
one value is taken into consideration. If the active transducer line is not defined for the
entire sweep range, the missing values are replaced by zeroes.
When a transducer is used, the trace is shifted by a calculated factor. However, an
upward shift reduces the dynamic range for the displayed values. Thus, the reference
level can be adapted automatically to restore the original dynamic range. The refer-
ence level is shifted by the maximum transducer factor. By default, if transducers are
active the reference level function is adapted automatically to obtain the best dynamic
performance.
If a transducer factor is active, "TDF" is displayed in the channel bar.
Transducers can also be defined when an optional external mixer is used (R&S FSW-
B21).
When using probes for RF input, transducers are automatically created according to
the probe's detected characteristics as soon as the probe is connected.
(See the FSW I/Q Analyzer and I/Q Input User Manual.)
Input from I/Q data files is imported as it was stored, including any correction factors,
for example from transducers. Any currently configured correction factors at the time of
import, however, are not applied.
Y-Axis Unit
The individual transducer factors can be defined as absolute values or relative (dB)
values. However, all factors for one transducer line use the same unit. As soon as a
transducer is activated, the unit of the transducer is automatically used for all the level
settings and outputs. The unit cannot be changed in the amplitude settings since the
FSW and the active transducer are regarded as one measuring instrument. Only for
relative transducer factors (unit dB), the unit originally set on the instrument is main-
tained and can be changed.
When all transducers have been switched off, the FSW returns to the unit that was
used before a transducer was activated.
Configuration
The FSW supports transducer lines with a maximum of 1001 data points. Eight of the
transducer lines stored in the instrument can be activated simultaneously. The number
of transducer lines stored in the instrument is only limited by the capacity of the storage
device used.
A transducer line consists of the following data:
● A maximum of 1001 data points with a position and value
Validity
The transducer factors must comply with the following rules to ensure correct opera-
tion:
● The frequencies for the data points must always be defined in ascending order.
Otherwise the entry will not be accepted and an error message is displayed.
● The frequencies of the data points may exceed the valid frequency range of the
FSW since only the set frequency range is taken into account for measurements.
The minimum frequency of a data point is 0 Hz, the maximum frequency 200 GHz.
● The value range for the transducer factor is ±200 dB.
● Gain has to be entered as a negative value, and attenuation as a positive value.
Transducers can also be defined when an optional external mixer is used (R&S FSW-
B21).
For the transducer line overview, the FSW searches for all stored transducer lines with
the file extension .TDF in the
C:\Program Files (x86)\Rohde-Schwarz\FSW\<version>\trd directory.
The overview allows you to determine which transducer lines are available and can be
used for the current measurement.
For details on settings for individual lines see Section 11.4.2.2, "Transducer factors",
on page 761.
For instructions on configuring and working with transducers see Section 11.4.4, "How
to configure the transducer", on page 765.
Name...........................................................................................................................760
Unit..............................................................................................................................760
Compatibility................................................................................................................760
Activating / Deactivating..............................................................................................760
Comment.....................................................................................................................760
Included Transducer Lines in Overview (View Filter).................................................. 760
Adjust Ref Level.......................................................................................................... 761
Create New Line......................................................................................................... 761
Edit Line...................................................................................................................... 761
Copy Line.................................................................................................................... 761
Delete Line.................................................................................................................. 761
Name
The name of the stored transducer line.
Unit
The unit in which the y-values of the data points of the transducer line are defined.
The following units are available:
● dB
● dBm
● dBmV
● dBμV
● dBμV/m
● dBμA
● dBμA/m
● dBpW
● dBpT
Additional units available only for installed FSW-K54 (EMI measurements) option:
● dBmV/MHz (normalized to 1 MHz)
● dBµV/MHz (normalized to 1 MHz)
● dBµA/MHz (normalized to 1 MHz)
Compatibility
Indicates whether the transducer factors are compatible with the current measurement
settings.
For more information on which conditions a transducer line must fulfill to be compati-
ble, see Section 11.4.1, "Basics on transducer factors", on page 756.
Activating / Deactivating
Activates/deactivates the transducer line. Up to 8 transducer lines can be active at the
same time.
Remote command:
[SENSe:]CORRection:TRANsducer:SELect on page 1409
[SENSe:]CORRection:TRANsducer[:STATe] on page 1410
Comment
An optional description of the transducer line.
Edit Line
Edit an existing transducer line configuration.
Copy Line
Copy the selected transducer line configuration to create a new line.
Delete Line
Delete the selected transducer line.
Remote command:
[SENSe:]CORRection:TRANsducer:DELete on page 1409
Access: [Setup] > "Transducer" > "Edit Line" / "Copy Line" / "New Line"
The settings and functions available for individual transducer lines are described here.
For instructions on creating and editing transducer lines see Section 11.4.4, "How to
configure the transducer", on page 765.
Name...........................................................................................................................762
Comment.....................................................................................................................762
Unit..............................................................................................................................763
X-Axis Scaling............................................................................................................. 763
Data Points..................................................................................................................763
Insert Value................................................................................................................. 763
Delete Value................................................................................................................763
Shift x.......................................................................................................................... 763
Shift y.......................................................................................................................... 763
Save............................................................................................................................ 763
Import.......................................................................................................................... 764
└ File Explorer..................................................................................................764
Export..........................................................................................................................764
└ File Explorer..................................................................................................764
Name
Defines the transducer line name. All names must be compatible with the Windows 10
conventions for file names. The transducer data is stored under this name (with a .TDF
extension) in the
C:\Program Files (x86)\Rohde-Schwarz\FSW\<version>\trd directory.
Remote command:
[SENSe:]CORRection:TRANsducer:SELect on page 1409
Comment
Defines an optional comment for the transducer line. The text may contain up to 40
characters.
Remote command:
[SENSe:]CORRection:TRANsducer:COMMent on page 1408
Unit
The unit in which the y-values of the data points of the transducer line are defined.
As soon as a transducer is activated, the unit of the transducer is automatically used
for all the level settings and outputs. The unit cannot be changed in the amplitude set-
tings unless dB is used.
Remote command:
[SENSe:]CORRection:TRANsducer:UNIT on page 1410
X-Axis Scaling
Describes the scaling of the horizontal axis on which the data points of the transducer
line are defined. Scaling can be linear or logarithmic.
Remote command:
[SENSe:]CORRection:TRANsducer:SCALing on page 1409
Data Points
Each transducer line is defined by a minimum of 2 and a maximum of 1001 data
points. Each data point is defined by its position (x-axis) and value (y-value).
The data points must comply with the following rules to ensure correct operation:
● The frequencies for the data points must always be defined in ascending order.
Otherwise the entry will not be accepted and the an error message is displayed.
● The frequencies of the data points may exceed the valid frequency range of the
FSW since only the set frequency range is taken into account for measurements.
The minimum frequency of a data point is 0 Hz, the maximum frequency 200 GHz.
● The value range for the transducer factor is ±200 dB.
● Gain has to be entered as a negative value, and attenuation as a positive value.
Remote command:
[SENSe:]CORRection:TRANsducer:DATA on page 1408
Insert Value
Inserts a data point in the transducer line above the selected one in the "Edit Trans-
ducer" dialog box.
Delete Value
Deletes the selected data point in the "Edit Transducer" dialog box.
Shift x
Shifts the x-value of each data point horizontally by the defined shift width.
Shift y
Shifts the y-value of each data point vertically by the defined shift width.
Save
Saves the currently edited transducer line under the name defined in the "Name" field.
Remote command:
MMEMory:SELect[:ITEM]:TRANsducer:ALL on page 1361
MMEMory:STORe<1|2>:STATe on page 1364
Import
Opens a file selection dialog box and loads the transducer factor from the selected file
in .CSV format.
Note that a valid import file must contain a minimum of required information for the
FSW. For details on the file format see Section 11.4.3, "Reference: transducer factor
file format", on page 764.
Remote command:
MMEMory:LOAD<n>:TFACtor on page 1410
Export
Opens a file selection dialog box and stores the currently displayed transducer factor to
the defined file in .CSV format.
For details on the file format see Section 11.4.3, "Reference: transducer factor file for-
mat", on page 764.
The transducer factor can be imported again later by the FSW for use in other mea-
surements.
Remote command:
MMEMory:STORe<n>:TFACtor on page 1411
Transducer factor data can be exported to a file in ASCII (CSV) format for further eval-
uation in other applications. Transducer factors stored in the specified ASCII (CSV) for-
mat can also be imported to the FSW for other measurements.
For more information about transducer factors, see "Import" on page 764.
This reference describes in detail the format of the export/import files for transducer
factors. Note that the bold data is mandatory, all other data is optional.
Different language versions of evaluation programs may require a different handling of
the decimal point. Thus, you can define the decimal separator to be used (see "Deci-
mal Separator" on page 654).
Header data
500000000;-30.000000
1000000000;0.000000
1500000000;-30.000000
2500000000;-50.000000
2. Select "Edit".
3. Edit the line configuration as described in "How to configure a new transducer line"
on page 767.
In order to store the changes to the transducer lines in a settings file, select the
"Save" icon in the toolbar.
(See Section 10.3, "Storing and recalling instrument settings and measurement data",
on page 679).
2. Select "Copy".
The "Edit Transducer" dialog box is opened with the configuration of the selected
transducer.
3. Define a new name to create a new transducer with the same configuration as the
source line.
4. Edit the line configuration as described in "How to configure a new transducer line"
on page 767.
2. Select "Delete".
2. Define a "Name" and, optionally, a "Comment" for the new transducer line.
5. Check the current line configuration in the preview area of the dialog box. If neces-
sary, correct individual data points or add or delete some.
If necessary, shift the entire line vertically or horizontally by selecting "Shift x" or
"Shift y" and defining the shift width.
2. Select "Edit".
3. In the "Edit Transducer Line" dialog box, select "Shift x" or "Shift y" and define the
shift width.
7. Select "Save".
The transducer factor is stored to a file with the specified name and the exten-
sion .CSV.
For details on the file format see Section 11.4.3, "Reference: transducer factor file
format", on page 764.
You are asked whether you would like to save the current configuration on the
FSW first.
6. Select "Select".
The transducer factor is loaded from the specified file and displayed in the "Edit
Transducer" dialog box.
.fres files
Additional frequency response correction files in .fres format allow you to correct
effects from components for which no Touchstone files are available.
Files in .fres format correspond to an S1P file. They contain exactly three values for
each frequency:
● The frequency
● The magnitude correction value
● The phase correction value
Instead of the magnitude and phase correction values, the I and Q values can be provi-
ded.
These values are applied to the input data. If the file contains any other data, it cannot
be loaded.
For .fres files, magnitude and phase correction can be activated separately.
Color Meaning
Red Correction settings active, but not in use, e.g. due to invalid settings
(see "Correction filters for I/Q data" on page 771)
Remote command:
[SENSe:]CORRection:FRESponse<si>:USER:VALid? on page 1429
Since multiple correction settings can be active at the same time, the channel bar
merely indicates that frequency response correction is being applied, but not which
files are being used. To find out which correction files are being used for the active
application, open the "User-Defined Frequency Response Correction" dialog box (see
Section 11.5.2, "User-defined frequency response correction settings", on page 772).
An LED-like symbol indicates whether each file is active and user correction or the
external preamplifier in general is switched on (symbol "lights up") or not (symbol is
dark). A purple symbol represents a Touchstone file. A green symbol represents a fre-
quency response (.fres) file.
Restrictions
Currently, the FSW has the following restrictions for Touchstone file support:
● Trace data containing corrections from Touchstone files cannot be returned in I/Q
block format
(See TRAC:IQ:DATA:FORM, described in the FSW I/Q Analyzer and I/Q Input
User Manual).
Frequency response correction can be configured individually for all available input
types (RF, baseband). The settings in the "User-defined Frequency Response Correc-
tion" dialog box apply to the currently selected input type.
State............................................................................................................................774
Refresh........................................................................................................................774
Ext. PA Correction.......................................................................................................774
Adjust Ref Level.......................................................................................................... 775
Apply to....................................................................................................................... 775
Load Settings.............................................................................................................. 775
Save Settings.............................................................................................................. 776
Clear Settings..............................................................................................................776
Touchstone File Information........................................................................................ 776
└ ID.................................................................................................................. 776
└ Filename....................................................................................................... 776
└ Active............................................................................................................ 776
└ To - From.......................................................................................................776
Add Touchstone File....................................................................................................777
Remove File................................................................................................................ 777
Move File Up or Down.................................................................................................777
Frequency Response active........................................................................................777
Frequency Response File Information........................................................................ 777
└ ID.................................................................................................................. 777
└ Filename....................................................................................................... 778
└ Magnitude..................................................................................................... 778
└ Phase............................................................................................................778
Add Freq Resp File..................................................................................................... 778
Remove Frequency Response File.............................................................................778
Preview....................................................................................................................... 778
State
Enables or disables the general usage of user-defined frequency response correction
settings. If activated, the data in the active correction files is combined to create a filter.
This filter is applied to the measurement results of subsequent sweeps.
TPIS correction is not supported if user frequency response correction is active. If you
activate frequency response correction, TPIS correction is automatically deactivated in
all channels.
For details see the FSW I/Q Analyzer and I/Q Input User Manual.
Remote command:
[SENSe:]CORRection:FRESponse<si>:USER:STATe on page 1428
Testing the validity of the correction setting:
[SENSe:]CORRection:FRESponse<si>:USER:VALid? on page 1429
Refresh
Retrieves the specified files again and creates a new combined filter. If enabled, the
filter is applied immediately.
Remote command:
[SENSe:]CORRection:FRESponse<si>:INPut<ip>:USER:REFResh
on page 1420
Ext. PA Correction
This function is only available if an external preamplifier is connected to the FSW, and
only for frequencies above 1 GHz. For details on connection, see the preamplifier's
documentation.
Using an external preamplifier, you can measure signals from devices under test with
low output power, using measurement devices which feature a low sensitivity and do
not have a built-in RF preamplifier.
When you connect the external preamplifier, the FSW reads out the touchdown (.S2P)
file from the EEPROM of the preamplifier. This file contains the s-parameters of the
preamplifier. As soon as you connect the preamplifier to the FSW, the preamplifier is
permanently on and ready to use. However, you must enable data correction based on
the stored data explicitly on the FSW using this setting.
When enabled, the FSW automatically compensates the magnitude and phase charac-
teristics of the external preamplifier in the measurement results. Any internal preampli-
fier, if available, is disabled.
An active external preamplifier is also included in the calculation of the combined user-
defined frequency response correction filter and displayed in the preview for SnP files
(see "Preview" on page 778).
For FSW85 models with two RF inputs, you can enable correction from the external
preamplifier for each input individually, but not for both at the same time.
When disabled, no compensation is performed even if an external preamplifier remains
connected.
Remote command:
INPut:EGAin[:STATe] on page 1216
Apply to
Determines which channels the correction settings are applied to.
Note: In MSRA mode, the settings are always applied to all active measurement chan-
nels.
"All Input Src" The frequency response correction settings are applied to all active
measurement channels with the same input source. A new filter is
calculated for each measurement channel as soon as you switch to it,
or when a measurement is performed (e.g. by the Sequencer).
"Channel" The frequency response correction settings are applied to the cur-
rently selected channel only.
Remote command:
[SENSe:]CORRection:FRESponse<si>:USER:SCOPe on page 1420
Load Settings
Loads a stored saveset for a user-defined frequency response correction scenario.
Existing settings in the dialog box are overwritten. The settings apply to the currently
selected channel or all channels, depending on the Apply to setting.
Only .dfl files can be loaded. The default storage directory for correction files is
C:\R_S\INSTR\USER\FResponse.
Remote command:
[SENSe:]CORRection:FRESponse<si>:USER:LOAD on page 1419
Save Settings
Stores a saveset for a user-defined frequency response correction scenario. As for all
instrument settings, a .dfl file is created for the correction data. Note that only the
settings defined in this dialog box are stored, not the contents of the files themselves.
Whether the settings for the currently selected channel only or for all channels are
stored depends on the Apply to setting.
The default storage directory is C:\R_S\INSTR\USER\FResponse.
Remote command:
[SENSe:]CORRection:FRESponse<si>:USER:STORe on page 1428
Clear Settings
Clears all current user-defined frequency response correction settings, either for the
currently selected channel only or for all channels, depending on the Apply to setting.
Merely files specific to the FSW itself remain in the list of Touchstone files.
Remote command:
[SENSe:]CORRection:FRESponse<si>:USER:PRESet on page 1420
Remove File
Removes the selected Touchstone file from the current configuration.
Remote command:
[SENSe:]CORRection:FRESponse<si>:USER:SLISt<sli>:REMove
on page 1425
[SENSe:]CORRection:FRESponse<si>:USER:SLISt<sli>:CLEar
on page 1422
Preview
The preview of the (combined) user correction files shows the correction values.
Remote command:
[SENSe:]CORRection:FRESponse<si>:USER:PSTate on page 1425
[SENSe:]CORRection:FRESponse<si>:USER:SCOVered? on page 1421
Remote command:
[SENSe:]CORRection:FRESponse<si>:USER:FLISt<fli>:DATA:FREQuency?
on page 1415
[SENSe:]CORRection:FRESponse<si>:USER:FLISt<fli>:DATA:MAGNitude?
on page 1415
[SENSe:]CORRection:FRESponse<si>:USER:FLISt<fli>:DATA:PHASe?
on page 1415
[SENSe:]CORRection:FRESponse<si>:USER:SLISt<sli>:DATA:
FREQuency<spi>? on page 1422
[SENSe:]CORRection:FRESponse<si>:USER:SLISt<sli>:DATA:
MAGNitude<spi>? on page 1422
[SENSe:]CORRection:FRESponse<si>:USER:SLISt<sli>:DATA:
PHASe<spi>? on page 1422
IQ Mode ← Preview
The preview in IQ Mode indicates the frequency ranges covered by the individual cor-
rection files. The blue bar indicates the valid frequency range for which all files contain
values.
An LED-like symbol indicates whether each file is active and user correction in general
is switched on (symbol "lights up") or not (symbol is dark). A purple symbol represents
a Touchstone file. A green symbol represents a frequency response (.fres) file.
The lower part shows the combined correction values for the valid frequency range.
Remote command:
[SENSe:]CORRection:FRESponse<si>:USER:IQ:DATA:FREQuency?
on page 1419
[SENSe:]CORRection:FRESponse<si>:USER:IQ:DATA:MAGNitude?
on page 1419
[SENSe:]CORRection:FRESponse<si>:USER:IQ:DATA:PHASe? on page 1419
Remote command:
[SENSe:]CORRection:FRESponse<si>:USER:SPECtrum:DATA:FREQuency?
on page 1427
[SENSe:]CORRection:FRESponse<si>:USER:SPECtrum:DATA:MAGNitude?
on page 1427
[SENSe:]CORRection:FRESponse<si>:USER:SPECtrum:DATA:PHASe?
on page 1427
The default setting is the internal reference. When an external reference is used, EXT
REF is displayed in the status bar.
The following reference inputs are available:
Table 11-2: Available Reference Frequency Input
External Reference REF INPUT 10 MHz +/- 6 ppm 1-100 Hz Fixed external 10 MHZ reference fre-
10 MHz 1..50 MHz quency
Good phase noise performance
External Reference REF INPUT 1..50 MHz +/- 0.5 ppm 0.1 Hz (fixed) Variable external reference frequency
1..50MHz 1..50 MHz in 1 Hz in 1 Hz steps
steps Good external phase noise suppres-
sion. Small tuning range.
External Reference REF INPUT 100 MHz +/- 6 ppm 1-300 Hz External reference
100 MHz 100 MHz / 1 GHz Good phase noise performance
External Reference REF INPUT 1 GHz +/- 6 ppm 1-300 Hz External reference
1 GHz 100 MHz / 1 GHz
Sync Trigger SYNC TRIGGER 100 MHz +/- 6 ppm 1-300 Hz External reference
INPUT
Remote command:
[SENSe:]ROSCillator:SOURce on page 1396
SOURce<si>:EXTernal<ext>:ROSCillator:EXTernal:FREQuency
on page 1395
Set to Default
The values for the "Tuning Range", "Frequency" and "Loop Bandwidth" are stored for
each source of "Reference Frequency Input".
When you switch the input source, the previously defined settings are restored. You
can restore the default values for all input sources using the "Set to Default" function.
Remote command:
DIAGnostic:SERVice:HWINfo? on page 1452
Remote commands:
SYSTem:FORMat:IDENt on page 1455
DIAGnostic:SERVice:BIOSinfo? on page 1452
DIAGnostic:SERVice:VERSinfo? on page 1453
● Obtaining copyright information on used third-party sources................................786
● License management............................................................................................786
After installing optional firmware, you must install or enable its license.
Trial license
The trial option (R&S FSW-K0) allows you to use further optional applications that
require a separate license from Rohde & Schwarz. It is pre-installed at the factory on
request. If enabled, you can use additional applications for a limited period of time (90
days from factory installation). They are accessible from the common "Mode" dialog
box (see Section 5.3, "Selecting the operating mode and applications", on page 122).
If the trial option has already expired, a message box appears for you to confirm. In
this case, all instrument functions are unavailable (including remote control) until the
FSW is rebooted. To continue to use the optional applications, you must acquire a
commercial license. Then use the "Install Option" function to enter the new license key
or activate a floating license as described in Section 11.7.2, "Licensing, versions and
options", on page 786.
The license is retrieved from the license server only when you select the application in
the "Mode" dialog box. Only one license per option is retrieved, but the option can be
used in multiple channels. It is returned shortly after you close the (last) application
channel. The license is blocked for other users only while at least one application
channel is in use.
If the connection to the license server is lost for longer than approximately 10 minutes,
the FSW assumes no license is available and closes the application.
Occupied license
An occupied license is retrieved once from the license server and stored locally for up
to 7 days, depending on the selected time period. During the occupied period, the
license is blocked for other users. After this time, the license automatically expires and
becomes available on the license server again. During the occupied period, no further
access to the license server is required. The license cannot be returned or disabled
manually before it expires, but it can be extended.
When the license expires, you must retrieve a new license from the license server. If
the connection to the license server is not available or no more licenses are available,
the FSW closes the application.
Occupied licenses are only available for instruments using a Windows 10 operating
system.
Install Option............................................................................................................... 788
Install Option by XML.................................................................................................. 788
License state ( ).................................................................................................... 789
└ Enabling/disabling floating licenses.............................................................. 789
Setup Floating License Server.................................................................................... 790
└ IP / Host name.............................................................................................. 790
└ Port............................................................................................................... 790
└ Description.................................................................................................... 790
└ Add Server.................................................................................................... 791
└ Remove Server............................................................................................. 791
└ Refresh List...................................................................................................791
Install Option
Opens an edit dialog box to enter the (permanently assigned) license key for an option.
Only user accounts with administrator rights are able to install options and enable
licenses.
License state ( )
Provides functions to enable or disable a floating license for an installed option. These
functions are only available if a floating license server is configured (see "Setup Float-
ing License Server" on page 790).
Note: Trial license. If the trial option (R&S FSW-K0) is installed, the "State" column
indicates whether an individual trial license is enabled or disabled.
Remote command:
SYSTem:OPTion:LICense[:LIST]? on page 1456
Enable/disable trial option: SYSTem:OPTion:TRIal[:STATe] on page 1458
Determine available trial applications: SYSTem:OPTion:TRIal:LIST? on page 1457
"Enabled" If enabled, the license is retrieved from the license server when you
select the application in the "Mode" dialog box.
Some options are available for multiple applications, such as power
sensor support. In this case, the license is retrieved if you select any
application that supports the option.
For options with suboptions, e.g. K91 with suboptions K91AC, K91N,
all suboptions are automatically activated together with the main
option by default.
"Disabled" If the license is disabled, it is not retrieved from the server when you
open the main application. The option is grayed out in the "Versions +
Options" dialog box. Disabling licenses is useful for suboptions (e.g.
K91N) or options that are available for multiple applications.
Indicates the currently configured floating license servers. All enabled servers are
searched for floating licenses when the FSW software starts. Note that changes to the
list of servers only take effect after the FSW software and the local License Manager
are restarted. To abort any changes, simply close the dialog box.
If the number of error messages exceeds the capacity of the error buffer, "Message
Buffer Overflow" is displayed. To clear the message buffer, use "Clear All Messages".
The following information is available:
Remote command:
SYSTem:ERRor:LIST? on page 1454
Before updating the firmware on your instrument, read the release notes delivered with
the firmware version.
Administrator rights are no longer required to perform a firmware update.
For detailed instructions on installing the firmware, see the product release notes.
Remote command:
SYSTem:FIRMware:UPDate on page 1455
Preset Mode................................................................................................................793
Out-of-range value behavior....................................................................................... 794
SecureUser Mode....................................................................................................... 794
└ Changing the password................................................................................ 794
Number block behavior............................................................................................... 795
Preset Mode
The presettings can be defined in the "Config" tab of the "System Configuration" dialog
box.
SecureUser Mode
If activated, the FSW requires a reboot and then automatically logs in using the
"SecureUser" account.
Data that the FSW normally stores on the solid-state drive is redirected to volatile
memory instead. Data that is stored in volatile memory can be accessed by the user
during the current instrument session. However, when the instrument’s power is
removed, all data in volatile memory is erased.
The Secure User Mode can only be activated or deactivated by a user with administra-
tor rights.
Note: Storing instrument settings permanently. Before you activate secure user mode,
store any instrument settings that are required beyond the current session, such as
predefined instrument settings, transducer files, or self-alignment data.
For details on the secure user mode, see Section 4.2.16, "Protecting data using the
secure user mode", on page 41.
Remote command:
SYSTem:SECurity[:STATe] on page 1458
Note: Initially after installation of the R&S FSW-K33 option, secure user mode must be
enabled manually once before remote control is possible.
To save the new password, select "Save". The password dialog for the next user is dis-
played, until you have been prompted to change the password all user accounts.
If you cancel the dialog without changing the password, the password dialog for the
next user is displayed, until you have been prompted to change the password for all
user accounts. It is possible to continue in secure user mode without changing the
passwords, and you will not be prompted to do so again. However, we strongly recom-
mend that you do define a more secure password for all users.
By default, the password characters are not displayed to ensure confidentiality during
input. To display the characters, select "Show password".
To display the onscreen keyboard, select "Keyboard".
Test Connection
The FSW attempts to establish a connection to the signal generator.
Connect/Disconnect
The FSW attempts to establish a connection to the signal generator, or disconnects it.
If an instrument is connected, the following information is displayed:
● Device type
● Name and serial number
● Connection state
Remote command:
CONFigure:GENerator:CONNection[:STATe] on page 1460
CONFigure:GENerator:CONNection:CSTate? on page 1459
Access: BIOS
Using a specific configuration setting in the BIOS of the FSW, you can define how the
instrument behaves after the AC power supply is interrupted. The setting applies
regardless whether the interruption occurs due to an irregular power outage in the
mains supply, by removing the power cable, or by switching the instrument power sup-
ply off.
The setting supports the following values:
● "Power Off": Instrument remains switched off.
● "Power On": Instrument automatically switches on as soon as power supply is
restored.
● "Last State": (Default) Instrument restores the state that it was in before the outage
occurred.
2. Watch for the prompt on the display, then press [DEL] on the keyboard to enter the
BIOS setup.
3. In the BIOS menu, select "Chipset" > "PCH-IO Configuration" > "Restore AC Power
Loss".
5. In the BIOS menu, select "Save & Exit" > "Save Changes and Exit".
Once the self-test is started, all modules are checked consecutively and the test result
is displayed. You can abort a running test.
In case of failure a short description of the failed test, the defective module, the associ-
ated value range and the corresponding test results are indicated.
Remote command:
*TST? on page 899
DIAGnostic:SERVice:STESt:RESult? on page 1406
NONE..........................................................................................................................801
Calibration Frequency RF........................................................................................... 801
└ Spectrum.......................................................................................................801
└ Frequency..................................................................................................... 802
Calibration Frequency MW..........................................................................................802
Calibration Analog Baseband......................................................................................802
└ Calibration Signal Type................................................................................. 802
NONE
Uses the current RF signal at the input, i.e. no calibration signal (default).
Remote command:
DIAGnostic:SERVice:INPut[:SELect] on page 1406
Calibration Frequency RF
Uses the internal calibration signal as the RF input signal.
Remote command:
DIAGnostic:SERVice:INPut[:SELect] on page 1406
DIAGnostic:SERVice:INPut:PULSed:CFRequency on page 1404
Calibration Frequency MW
Uses the microwave calibration signal as the RF input (for frequencies higher than 8
GHz). This function is used to calibrate the YIG-filter on the microwave converter. The
microwave calibration signal is pulsed.
You can define whether the distance between input pulses is small or wide.
Note: For FSW85 models, you can use a microwave calibration signal with a spectrum
of 43.5 GHz, or a wideband signal that covers the complete 85 GHz bandwidth. You
can define the frequency of the microwave calibration signal. The firmware adapts the
defined value to the next possible valid value.
Remote command:
DIAGnostic:SERVice:INPut[:SELect] on page 1406
DIAGnostic:SERVice:INPut:MC[:DISTance] on page 1403
DIAGnostic:SERVice:INPut:MC:CFRequency on page 1403
DIAGnostic:SERVice:INPut:MC:RANGe on page 1404
Service Function
Selects the service function by its numeric code or textual name.
The selection list includes all functions previously selected (since the last "Clear His-
tory" action).
Remote command:
DIAGnostic:SERVice:SFUNction on page 1461
Send
Starts the selected service function.
Remote command:
DIAGnostic:SERVice:SFUNction on page 1461
Numeric Mode
If activated, the service function is selected by its numeric code. Otherwise, the func-
tion is selected by its textual name.
Clear History
Deletes the list of previously selected service functions.
Password
Most service functions require a special password as they may disrupt normal opera-
tion of the FSW. There are different levels of service functions, depending on how
restrictive their use is handled. Each service level has a different password.
"Reset Password" clears any previously entered password and returns to the most
restrictive service level.
Remote command:
SYSTem:PASSword[:CENable] on page 1462
SYSTem:PASSword:RESet on page 1463
Clear Results
Clears the result display for all previously performed service functions.
Remote command:
DIAGnostic:SERVice:SFUNction:RESults:DELete on page 1461
Save Results
Saves the results of all previously performed service functions to a file stored as
C:\R_S\INSTR\results\Servicelog.txt.
Remote command:
DIAGnostic:SERVice:SFUNction:RESults:SAVE on page 1461
Result List
The Results List indicates the status and results of the executed service functions.
In case problems occur with the instrument hardware, some diagnostic tools provide
information that may support troubleshooting.
The hardware diagnostics tools are available in the "Hardware Diagnostics" tab of the
"Service" dialog box.
When you couple a parameter across all active measurement channels, a change in
the currently selected application is passed on to all other active measurement chan-
nels.
In MSRA mode, the data is captured by the MSRA primary only. Thus, parameter cou-
pling is not available for data acquisition parameters. However, it can be useful to cou-
ple time or frequency markers between applications. Thus, you can easily determine
effects that occur at the same time or frequency in different measurement views.
Note that the accuracy of time marker couplings is ±1 sample.
"Center Frequency"
Synchronizes the center frequency
Remote command:
INSTrument:COUPle:CENTer on page 1465
"Start / Stop Frequency"
Synchronizes the start and stop frequencies for measurements in the
frequency domain
Note: The start and stop frequencies can automatically change when
you change another frequency parameter (such as center frequency
or span).
Remote command:
INSTrument:COUPle:SPAN on page 1468
"Reference Synchronizes the reference level
Level" Remote command:
INSTrument:COUPle:RLEVel on page 1468
"Attenuation"
Synchronizes the attenuation
Remote command:
INSTrument:COUPle:ATTen on page 1464
"Preamplifier"
Synchronizes the gain of the optional preamplifier
Remote command:
INSTrument:COUPle:GAIN on page 1466
"Amplitude Unit"
Synchronizes the unit of the level axis
Remote command:
INSTrument:COUPle:AUNit on page 1465
"Video Bandwidth"
Synchronizes the video bandwidth
Note: You cannot synchronize the video bandwidth and the resolution
bandwidth is not possible.
Remote command:
INSTrument:COUPle:VBW on page 1469
"Resolution Bandwidth"
Synchronizes the measurement bandwidth
Note: You cannot synchronize the video bandwidth and the resolution
bandwidth simultaneously.
Remote command:
INSTrument:COUPle:BANDwidth on page 1465
"Limit Lines"
Activates the limit line over all channels
Note: Limit lines are only synchronized over channels if the limit line
is compatible to the channel configuration (especially units of the x-
and y-axis).
Remote command:
INSTrument:COUPle:LIMit on page 1467
"AC DC Coupling"
Synchronizes the Input Coupling
Remote command:
INSTrument:COUPle:ACDC on page 1464
"Impedance"
Synchronizes the impedance for RF input
Remote command:
INSTrument:COUPle:IMPedance on page 1466
"Analog Baseband Impedance"
Synchronizes the impedance for analog baseband input
Remote command:
INSTrument:COUPle:ABIMpedance on page 1463
Example:
You currently run two instances of the Spectrum application, two instances of the VSA
application, and one instance of the AM/FM/PM Analog Demod application.
You can synchronize only the first instance of the Spectrum application with the first
instance of the VSA application, while the other three channels remain independent.
Alternatively, you can synchronize all instances of the VSA application, while the Spec-
trum and AM/FM/PM Analog Demod applications remain independent.
Index
Index of the user-defined parameter coupling, used to identify the definition in remote
operation.
Remote command:
INSTrument:COUPle:USER<uc>:NUMBers:LIST? on page 1475
Parameter 1 / Parameter 2
The coupled parameters, markers, or lines.
Remote command:
INSTrument:COUPle:USER<uc>:NEW? on page 1473
State
Enables or disables the coupling.
Remote command:
INSTrument:COUPle:USER<uc>:STATe on page 1476
Direction
Determines which parameter controls the other.
"<-" Parameter 2 controls parameter 1. If parameter 2 is changed, param-
eter 1 is adapted. If parameter 1 is changed, parameter 2 remains
unchanged.
Remote command:
INST:COUP:USER:REL RTOL
"->" Parameter 1 controls parameter 2. If parameter 1 is changed, param-
eter 2 is adapted. If parameter 2 is changed, parameter 1 remains
unchanged.
Remote command:
INST:COUP:USER:REL LTOR
"<->" Both parameters are equal. If one parameter is changed, the other
parameter is adapted and vice versa.
Remote command:
INST:COUP:USER:REL BID
Info
Shows information for the selected coupling, for example, restrictions regarding the
coupling.
Note that usually, no information is displayed.
Remote command:
INSTrument:COUPle:USER<uc>:INFO on page 1472
Delete All
Deletes all current coupling definitions. Parameters are no longer coupled.
Remote command:
INSTrument:COUPle:USER<uc>:REMove on page 1476
Remote command:
INSTrument:COUPle:USER<uc>:NEW? on page 1473
Remote command:
INSTrument:COUPle:USER<uc>:ELEMent:LIST? on page 1471
You cannot only couple parameters between FSW applications, but also between the
FSW and a connected signal generator. Coupling parameters is especially useful when
you use the SCPI recorder and need to include generator commands (see "Combined
Recording of Spectrum Analyzer and R&S Signal Generator" on page 850).
Connect/Disconnect
The FSW attempts to establish a connection to the signal generator, or disconnects it.
If an instrument is connected, the following information is displayed:
● Device type
● Name and serial number
● Connection state
Remote command:
CONFigure:GENerator:CONNection[:STATe] on page 1460
CONFigure:GENerator:CONNection:CSTate? on page 1459
Coupling State
Enables or disables coupling between the FSW and a connected signal generator.
Note that only one channel can control a generator at any time. If a measurement
channel already has control of the connected generator and you enable parameter
coupling, the control is disabled in the other channel.
Remote command:
INSTrument:COUPle:GENerator:STATe on page 1479
Center Frequency
Couples the center frequency of the connected signal generator to the FSW.
This setting requires the Coupling State to be enabled.
Remote command:
INSTrument:COUPle:GENerator:CENTer[:STATe] on page 1478
Reference level
Couples the reference level of the connected signal generator to the FSW.
This setting requires the Coupling State to be enabled.
Remote command:
INSTrument:COUPle:GENerator:RLEVel[:STATe] on page 1479
3. In the "General" tab, set the parameter you want to synchronize over all measure-
ment channels to "On".
5. From the "Channel 1" list, select the channels or type of channel to couple.
6. From the "Coupling Element 1" list, select the parameter or marker to couple for
the selected measurement channels.
To shorten the list and restrict it to a certain type of parameters, select a "Category"
first.
7. For AM/FM/PM Analog Demod channels and frequency markers only, select the
individual windows (in the frequency domain) to couple.
10. If specific channels are coupled, select the "Direction" to define which channel con-
trols the other, that is: in which channel the parameter is adapted if the other is
changed.
4. Select the "Edit" icon for the parameter coupling you want to edit.
Currently two Spectrum application channels are active, one I/Q analyzer channel, and
two AM/FM/PM Analog Demod channels.
3. From the "Coupling Element 1" list, select "Frequency Marker 1".
4. From the "Specifics for Window" list, select window "1" (which is the FM Spectrum
window).
6. From the "Coupling Element 2" list, select "Frequency Marker 1".
7. From the "Specifics for Window" list, select window "1" (which is the RF Spectrum
window).
9. In the "Parameter Coupling" dialog box, for the coupling definition for the frequency
markers in the AM/FM/PM Analog Demod channels, select the "Direction": "->"
11. In the first AnaDemod channel, set the frequency marker in the FM Spectrum to
900 MHz.
In the second AnaDemod channel, the frequency marker in the RF Spectrum is
also at 900 MHz.
12. In the second AnaDemod channel, set the frequency marker in the RF Spectrum to
1100 MHz.
In the first AnaDemod channel, the frequency marker in the FM Spectrum is still at
900 MHz.
For additional information on remote control of spectrum analyzers see the following
documents available from the Rohde & Schwarz website:
● Remote control via SCPI
● 1EF62: Hints and Tricks for Remote Control of Spectrum and Network Analyzers
● 1MA171: How to use Rohde & Schwarz Instruments in MATLAB
● 1MA208: Fast Remote Instrument Control with HiSLIP
How to configure the remote control interfaces is described in Section 12.7, "How to
set up a network and remote control", on page 873.
● Remote control interfaces and protocols...............................................................819
● Status reporting system........................................................................................ 825
● GPIB languages.................................................................................................... 838
● The IECWIN tool................................................................................................... 840
● Automating tasks with remote command scripts...................................................841
● Network and remote control settings.....................................................................854
● How to set up a network and remote control.........................................................873
Local HiSLIP High-Speed LAN Instrument Protocol (IVI-6.1) TCP port: 4880 A LAN connector is located
Area TCPIP::host address::hislip0[::INSTR] on the rear panel of the
Net- instrument.
work VXI-11 TCP or UDP port: 111
(LAN)
TCPIP::host address::inst0[::INSTR] TCP port: well-known ports (600
- 1023) for Linux or registered
Library: VISA
ports (1024 - 49151) for Windows
socket communication (Raw Ethernet, simple Telnet) SCPI raw, TCP port: 5025, 5125
TCPIP::host address[::LAN device name]:: SCPI telnet, TCP port: 5024,
<port>::SOCKET 5124
Library: VISA or socket controller
*) VISA is a standardized software interface library providing input and output functions to communicate with instruments. A VISA
installation on the controller is a prerequisite for remote control using the indicated interfaces.
**) By default, FSW use these ports for communication via LAN control interface. If necessary, adapt your firewall to allow for use of
these ports.
Within this interface description, the term GPIB is used as a synonym for the IEC/IEEE
bus interface.
TCP/IP network protocol and the associated network services are preconfigured on the
instrument. Software for instrument control and the VISA program library must be
installed on the controller.
IP address
Only the IP address or a valid DNS host name is required to set up the connection.
The host address is part of the "VISA resource string" used by the programs to identify
and control the instrument.
The VISA resource string has the form:
TCPIP::host address[::LAN device name][::INSTR]
or
TCPIP::host address::port::SOCKET
where:
● TCPIP designates the network protocol used
● host address is the IP address or host name of the device
● LAN device name defines the protocol and the instance number of a subinstru-
ment;
– inst0 selects the VXI-11 protocol (default)
– hislip0 selects the HiSLIP protocol
● INSTR indicates the instrument resource class (optional)
● port determines the used port number
● SOCKET indicates the raw network socket resource class
Example:
● Instrument has the IP address 192.1.2.3; the valid resource string using VXI-11
protocol is:
TCPIP::192.1.2.3::INSTR
● The DNS host name is FSW13-123456; the valid resource string using HiSLIP is:
TCPIP::FSW13-123456::hislip0
● A raw socket connection can be established using:
TCPIP::192.1.2.3::5025::SOCKET
For details on configuring the LAN connection, see Section 12.7, "How to set up a net-
work and remote control", on page 873.
● LAN web browser interface................................................................................... 822
The LAN web browser interface allows for easy configuration of the LAN and remote
control of the FSW without additional installation requirements.
The instrument's LAN web browser interface works correctly with all W3C compliant
browsers.
Via the web browser interface to the FSW you can control the instrument remotely from
another PC. Manual instrument controls are available via the front panel simulation.
File upload and download between the instrument and the remote PC is also available.
Using this feature, several users can access and operate the FSW simultaneously.
This is useful for troubleshooting or training purposes.
For details, see Section 12.7.1.4, "How to configure the LAN using the web browser
interface", on page 878 and Section 12.7.5, "How to control the FSW via the web
browser interface", on page 884.
If you do not want other users in the LAN to be able to access and operate the FSW
you can deactivate this function.
See Section 12.7.6, "How to deactivate the web browser interface", on page 885.
Restrictions
Only user accounts with administrator rights can use the LAN web browser functional-
ity.
The navigation pane of the browser interface contains the following elements:
● "LAN"
– "Home" opens the instrument home page.
The home page displays device information, including the VISA resource string
in read-only format.
"Device Indicator" allows you to physically identify the instrument. This is useful
if you have several instruments and want to know which instrument the LAN
home page belongs to. To identify the instrument, activate the "Device Indica-
tor". Then check the "LAN Status" indicator of the instruments.
– "LAN Configuration" allows you to configure LAN parameters and to initiate a
ping.
(See "LAN configuration" on page 879.)
– "Utilities" provides access to an event log.
● "Instrument Control"
– "Web Control" provides remote access to the instrument via VNC (no installa-
tion required). Manual instrument controls are available via the front panel sim-
ulation.
– "File Download" downloads files from the instrument.
– "File Upload" uploads files to the instrument.
(See step 4.)
● "License Manager"
– "License Manager" allows you to install or uninstall license keys and to acti-
vate, register or unregister licenses.
● "Help"
"www.rohde-schwarz.com" opens the Rohde & Schwarz home page.
For remote control via the USB connection, the PC and the instrument must be con-
nected via the USB type B interface.
(Note: the USB type B interface is not available for instruments with CPU board
1206.3874.00 or higher.)
A USB connection requires the VISA library to be installed. VISA detects and config-
ures the R&S instrument automatically when the USB connection is established. You
do not have to enter an address string or install a separate driver.
USB address
The used USB address string is:
USB::<vendor ID>::<product ID>::<serial number>[::INSTR]
where:
● <vendor ID> is the vendor ID for Rohde & Schwarz (0x0AAD)
● <product ID> is the product ID for the Rohde & Schwarz instrument
● <serial number> is the individual serial number on the rear of the instrument
Table 12-2: Product IDs for FSW
FSW8 C6
FSW13 C7
FSW26 C8
FSW43 CA
FSW50 CB
FSW67 CC
FSW85 CD
Example:
USB::0x0AAD::0x00C7::100001::INSTR
0x0AAD is the vendor ID for Rohde & Schwarz
0x00C7 is the product ID for the FSW13
100001 is the serial number of the particular instrument
& logic AND 15 not used 15 not used 15 not used 15 not used
of all bits
logic OR 14 14 14 14
one register for 13 13 13 13
*)
each channel
12 Self-alignment info 12 12 12
11 11 11 11
10 Range completed 10 10 10
Multi-Standard Capture
9 9 9 9
Finish
8 HCOPy in progress 8 GAP ACLR FAIL 8 8
7 7 CACLR FAIL 7 LMARgin 8 FAIL 7 LIMit 8 FAIL
6 6 ALT3...11 LOWer/UPPer FAIL 6 LMARgin 7 FAIL 6 LIMit 7 FAIL
5 Waiting for TRIGger 5 ALT2 LOWer FAIL 5 LMARgin 6 FAIL 5 LIMit 6 FAIL
4 MEASuring 4 ALT2 UPPer FAIL 4 LMARgin 5 FAIL 4 LIMit 5 FAIL
3 SWEeping 3 ALT1 LOWer FAIL 3 LMARgin 4 FAIL 3 LIMit 4 FAIL
2 2 ALT1 UPPer FAIL 2 LMARgin 3 FAIL 2 LIMit 3 FAIL
1 1 ADJ LOWer FAIL 1 LMARgin 2 FAIL 1 LIMit 2 FAIL
SRQ
0 CALibrating 0 ADJ UPPer FAIL 0 LMARgin 1 FAIL 0 LIMit 1 FAIL
STATus:OPERation STAT:QUES:ACPLimit *) STAT:QUES:LMARgin<n> *) STAT:QUES:LIMit<n> *)
& 7
6 RQS/MSS
& 5 ESB 15 not used
& 4 MAV 15 not used
15 not used ...
& 3 ...
15 not used
... 9
& 2 14 DIQ 9
9 8
1 13 8
8 NO REF 7
0 12 ACPLimit 7
7 6
SRE STB 11 SYNC 6
6 5
10 LMARGin 5
5 4
9 LIMit 4
4 3 INPUT OVLD
8 CALibration (=UNCAL) 3
3 2 OVLD
& 7 2
2 1
& 6 1
1 LO UNLocked 0 OVERload
& 5 FREQuency 0 Frontend temp. error
0 OVEN COLD STAT:QUES:POWer *)
& 4 TEMPerature STAT:QUES:TEMPerature *)
STAT:QUES:FREQuency *)
& 3 POWer
& 2 TIME
1
0 EXTended 15 not used 15 not used
15 not used
PPE ... ... ...
STATus:QUEStionable
5 5 5
ISTflag 4 4 4 FATal
& 7 Power On 3
3 3 ERRor
& 6 User Request 2
2 2 WARNing
& 5 Command Error 1 INFO
1 Sweep time too low 1 INFO
& 4 Execution Error 0
0 0 MESSage
Device Dependent
& 3
Error STAT:QUES:TIME *) STAT:QUES:EXTended *) STAT:QUES:EXTended:INFO *)
& 2 Query Error
& 1
Error/ Event Output & 0 Operation Complete
Queue Buffer
ESE ESR
In the following sections, the contents of the status registers are described in more
detail.
STATus:QUEStionable:DIQ register
The STATus:QUEStionable:DIQ register is used for digital I/Q data from the
optional Digital Baseband Interface and is described in the FSW I/Q Analyzer and I/Q
Input User Manual.
STATus:QUEStionable:SYNC register
The STATus:QUEStionable:SYNC register is used by the FSW applications and is
described in the individual sections (manuals) for each application.
12.2.2.1 Status byte (STB) and service request enable register (SRE)
The STatus Byte (STB) is already defined in IEEE 488.2. It provides a rough over-
view of the instrument status by collecting the pieces of information of the lower regis-
ters. A special feature is that bit 6 acts as the sum bit of the remaining bits of the status
byte.
The STB can thus be compared with the CONDition part of an SCPI register and
assumes the highest level within the SCPI hierarchy.
The STB is read using the command *STB? or a serial poll.
The STatus Byte (STB) is linked to the Service Request Enable (SRE) register.
Each bit of the STB is assigned a bit in the SRE. Bit 6 of the SRE is ignored. If a bit is
set in the SRE and the associated bit in the STB changes from 0 to 1, a service
request (SRQ) is generated. The SRE can be set using the command *SRE and read
using the command *SRE?.
5 ESB bit
Sum bit of the event status register. It is set if one of the bits in the event status register is set
and enabled in the event status enable register. Setting of this bit indicates a serious error which
can be specified in greater detail by polling the event status register.
As with the SRQ, the IST flag combines the entire status information in a single bit. It
can be read by means of a parallel poll or using the command *IST?.
The parallel poll enable register (PPE) determines which bits of the STB contribute to
the IST flag. The bits of the STB are "ANDed" with the corresponding bits of the PPE,
with bit 6 being used as well in contrast to the SRE. The IST flag results from the
"ORing" of all results. The PPE can be set using commands *PRE and read using com-
mand *PRE?.
12.2.2.3 Event status register (ESR) and event status enable register (ESE)
The ESR is defined in IEEE 488.2. It can be compared with the EVENt part of a SCPI
register. The event status register can be read out using command *ESR?.
The ESE corresponds to the ENABle part of a SCPI register. If a bit is set in the ESE
and the associated bit in the ESR changes from 0 to 1, the ESB bit in the STB is set.
The ESE register can be set using the command *ESE and read using the command
*ESE?.
Table 12-4: Meaning of the bits used in the event status register
0 Operation Complete
This bit is set on receipt of the command *OPC exactly when all previous commands have been
executed.
1 Not used
2 Query Error
This bit is set if either the controller wants to read data from the instrument without having sent a
query, or if it does not fetch requested data and sends new instructions to the instrument
instead. The cause is often a query which is faulty and hence cannot be executed.
3 Device-dependent Error
This bit is set if a device-dependent error occurs. An error message with a number between
-300 and -399 or a positive error number, which denotes the error in greater detail, is entered
into the error queue.
4 Execution Error
This bit is set if a received command is syntactically correct but cannot be performed for other
reasons. An error message with a number between -200 and -300, which denotes the error in
greater detail, is entered into the error queue.
5 Command Error
This bit is set if a command is received, which is undefined or syntactically incorrect. An error
message with a number between -100 and -200, which denotes the error in greater detail, is
entered into the error queue.
6 User Request
This bit is set when the instrument is switched over to manual control.
0 CALibrating
This bit is set as long as the instrument is performing a self-alignment.
3 SWEeping
Sweep is being performed in base unit (applications are not considered); identical to bit 4
In applications, this bit is not used.
4 MEASuring
Measurement is being performed in base unit (applications are not considered); identical to bit 3
In applications, this bit is not used.
8 HardCOPy in progress
This bit is set while the instrument is printing a hardcopy.
10 Range completed
This bit is set when a range in the sweep list is completed if "Stop after Sweep" is enabled (see
"Stop After Sweep" on page 289).
11 Not used
12 Self-alignment overdue
The STAT:QUES:SYNC register is used by the applications and is thus described in the
individual applications' User Manuals.
The STATus:QUEStionable register "sums up" the information from all subregisters
(e.g. bit 2 sums up the information for all STATus:QUEStionable:TIMe registers).
For some subregisters, there may be separate registers for each active channel. Thus,
if a status bit in the STATus:QUEStionable register indicates an error, the error may
have occurred in any of the channel-specific subregisters. In this case, you must check
the subregister of each channel to determine which channel caused the error. By
default, querying the status of a subregister always returns the result for the currently
selected channel.
0 "EXTended"
This bit indicates further status information not covered by the other status registers in any of
the active channels.
1 Unused
2 "TIMe"
This bit is set if a time error occurs in any of the active channels.
The STATus:QUEStionable:TIMe register provides more information on the error type.
3 "POWer"
This bit is set if the measured power level in any of the active channels is questionable.
The STATus:QUEStionable:POWer register provides more information on the error type.
4 "TEMPerature"
This bit is set if the temperature is questionable.
5 "FREQuency"
This bit is set if there is anything wrong with the frequency of the local oscillator or the reference
frequency in any of the active channels.
The STATus:QUEStionable:FREQuency register provides more information on the error type.
6-7 Unused
8 "CALibration"
This bit is set if the FSW is unaligned ("UNCAL" display)
9 "LIMit" (device-specific)
This bit is set if a limit value is violated in any of the active channels in any window.
The STATus:QUEStionable:LIMit register provides more information on the error type.
10 "LMARgin" (device-specific)
This bit is set if a margin is violated in any of the active channels in any window.
The STATus:QUEStionable:LMARgin register provides more information on the error type.
11 "SYNC" (device-specific)
This bit is set if the FSW is not synchronized to the signal that is applied.
The FSW is not synchronized if:
● it cannot synchronize to midamble during a measurement or premeasurement
● it cannot find a burst during a measurement or premeasurement
● the results deviate too much from the expected value during premeasurements
12 "ACPLimit" (device-specific)
This bit is set if a limit during ACLR measurements is violated in any of the active channels.
The STATus:QUEStionable:ACPLimit register provides more information on the error type.
13 Unused
7 CACLR FAIL
This bit is set if the CACLR limit is exceeded in one of the gap channels.
9 to 14 Unused
0 not used
1 INFO
This bit is set if a status message is available for the application.
Which type of message occurred is indicated in the STATus:QUEStionable:EXTended:INFO reg-
ister.
2 to 14 Unused
0 MESSage
This bit is set if event or state has occurred that may lead to an error during further operation.
1 INFO
This bit is set if an informational status message is available for the application.
2 WARNing
This bit is set if an irregular situation occurs during measurement, e.g. the settings no longer
match the displayed results, or the connection to an external device was interrupted temporarily.
3 ERRor
This bit is set if an error occurs during a measurement, e.g. due to missing data or wrong set-
tings, so that the measurement cannot be completed correctly.
4 FATal
This bit is set if a serious error occurs in the application and regular operation is no longer possi-
ble.
5 to 14 Unused
0 OVEN COLD
This bit is set if the reference oscillator has not yet attained its operating temperature. "OCXO"
is displayed.
1 LO UNLocked
This bit is set if the local oscillator no longer locks. "LOUNL" is displayed.
2 to 7 Not used
8 EXTernalREFerence
This bit is set if you have selected an external reference oscillator but did not connect a useable
external reference source.
In that case the synthesizer can not lock. The frequency in all probability is not accurate.
9 to 14 Not used
0 LIMit 1 FAIL
This bit is set if limit line 1 is violated.
1 LIMit 2 FAIL
This bit is set if limit line 2 is violated.
2 LIMit 3 FAIL
This bit is set if limit line 3 is violated.
3 LIMit 4 FAIL
This bit is set if limit line 4 is violated.
4 LIMit 5 FAIL
This bit is set if limit line 5 is violated.
5 LIMit 6 FAIL
This bit is set if limit line 6 is violated.
6 LIMit 7 FAIL
This bit is set if limit line 7 is violated.
7 LIMit 8 FAIL
This bit is set if limit line 8 is violated.
8 to 14 Unused
0 LMARgin 1 FAIL
This bit is set if limit margin 1 is violated.
1 LMARgin 2 FAIL
This bit is set if limit margin 2 is violated.
2 LMARgin 3 FAIL
This bit is set if limit margin 3 is violated.
3 LMARgin 4 FAIL
This bit is set if limit margin 4 is violated.
4 LMARgin 5 FAIL
This bit is set if limit margin 5 is violated.
5 LMARgin 6 FAIL
This bit is set if limit margin 6 is violated.
6 LMARgin 7 FAIL
This bit is set if limit margin 7 is violated.
7 LMARgin 8 FAIL
This bit is set if limit margin 8 is violated.
8 to 14 Not used
0 OVERload
This bit is set if an overload occurs at the RF input, causing signal distortion but not yet causing
damage to the device.
The FSW displays the keyword "RF OVLD".
1 Unused
2 IF_OVerload
This bit is set if an overload occurs in the IF path.
The FSW displays the keyword "OVLD".
3 Input Overload
This bit is set if the signal level at the RF input connector exceeds the maximum.
The RF input is disconnected from the input mixer to protect the device. In order to re-enable
measurement, decrease the level at the RF input connector and reconnect the RF input to the
mixer input.
For details on the protection mechanism see "RF Input Protection" on page 365 or INPut:
ATTenuation:PROTection:RESet on page 1113.
The FSW displays the keyword "INPUT OVLD".
4 to 14 Unused
0 This bit is set if the frontend temperature sensor deviates by a certain degree from the self-
alignment temperature.
During warmup, this bit is always 1.
For details see "Temperature check" on page 729.
1 to 14 Unused
0 not used
2 to 14 Unused
The following table contains the different commands and events causing the status
reporting system to be reset. None of the commands, except *RST and
SYSTem:PRESet, influence the functional instrument settings. In particular, DCL does
not change the instrument settings.
Table 12-16: Resetting the status reporting system
1) The first command in a command line that immediately follows a <PROGRAM MESSAGE TERMINA-
TOR> clears the output buffer.
Supported languages
Language Comment
SCPI
8560E
8561E
8562E
8563E
8564E
8565E
8566A Command sets A and B are available. Command sets A and B differ in the rules
regarding the command structure.
Language Comment
8566B
8568A Command sets A and B are available. Command sets A and B differ in the rules
regarding the command structure.
8568B Command sets A and B are available. Command sets A and B differ in the rules
regarding the command structure.
8594E Command sets A and B are available. Command sets A and B differ in the rules
regarding the command structure.
PSA89600
PSA
PXA
R&S FSEA
R&S FSEB
R&S FSEM
R&S FSEK
R&S FSP
R&S FSQ
R&S FSU
R&S FSV
Notes:
● If you select a language other than "SCPI", the GPIB address is set to 18 if it was
20 before.
● The Start/stop frequency, reference level and number of sweep points are adapted
to the selected instrument model.
● For R&S FSP/FSQ/FSU emulation, HP commands are not automatically also
allowed. In this case, set HP Additional to ON.
● When you switch between remote control languages, the following settings or
changes are made:
SCPI:
The instrument performs a PRESET.
8566A/B, 8568A/B, 8594E; FSEA, FSEB, FSEM; FSEK:
– The instrument performs a PRESET.
– The following instrument settings are changed:
Table 12-17: Instrument settings for emulation of 8566A/B, 8568A/B, 8594E; FSEA, FSEB, FSEM;
FSEK instruments
Model # of Trace Start Freq. Stop Freq. Ref Level Input Coupling
Points
Note: The stop frequency indicated in the table may be limited to the corresponding
frequency of the FSW, if required.
The R&S IECWIN32 tool is provided free of charge. The functionality may change in a
future version without notice.
You can use the IECWIN to try out the programming examples provided in the FSW
User Manuals.
Starting IECWIN
IECWIN is available from the Windows "Start" menu on the FSW, or by executing the
following file:
C:\Program Files (x86)\Rohde-Schwarz\FSW\<version>\iecwin32.exe
You can also copy the program to any Windows PC or laptop. Simply copy the
iecwin32.exe, iecwin.chm and rsib32.dll files from the location above to the
same folder on the target computer.
When the tool is started, a "Connection settings" dialog box is displayed. Define the
connection from the computer the IECWIN tool is installed on to the FSW you want to
control. If you are using the tool directly on the FSW, you can use an NT Pipe (COM
Parser) connection, which requires no further configuration. For help on setting up
other connection types, check the tool's online help (by clicking the "Help" button in the
dialog box).
The IECWIN offers an online help with extensive information on how to work with the
tool.
instrument supports you by showing the corresponding command syntax for the cur-
rent setting value.
You can create a SCPI script directly on the instrument at any time of operation, in the
following ways:
● Recording individual steps manually
In manual recording mode, you can record an individual SCPI command using the
"Add SCPI Command to Recording" function, see "How to record SCPI commands
manually" on page 852.
● Recording all performed steps automatically
The instrument records the SCPI command and settings value of each step you
perform, and then writes the commands to the file system, see "How to record
SCPI commands automatically" on page 851. You can start, stop and resume
automatic recording, and also record individual commands manually.
● Copying commands from the context-sensitive SCPI Recorder menu and pasting
them into an editor
The SCPI Recorder enables you to copy the SCPI command and the current set-
ting shown in the context-sensitive menu and paste them into any suitable editor,
see "To edit a SCPI command list" on page 852.
The SCPI Recorder provides information on the required SCPI command for the avail-
able measurement settings, functions, and results in a context-sensitive menu. The
SCPI command menu is displayed when you tap and hold (right-click) any interface
element that allows you to define a setting, perform a function, or displays results, for
example:
● Softkeys
● Buttons or input fields in dialog boxes
● Traces or markers in a diagram
Figure 12-2: Context-sensitive SCPI command menu for a trace in a result display
The menu provides the syntax of the remote command with the current setting, and
some functions to help you create your script.
Show SCPI result query commands........................................................................... 843
Show SCPI command................................................................................................. 843
└ Copy SCPI Command to Clipboard.............................................................. 843
└ Help...............................................................................................................843
└ Add SCPI Command to Recording............................................................... 843
Help.............................................................................................................................843
Help
Provides help on the selected setting, function, or result display, as opposed to the
SCPI command itself. This function is identical to selecting the context-sensitive help
icon in the toolbar and then the interface element.
Access: Toolbar
The SCPI Recorder displays a list of the currently recorded commands and provides
functions to create and export a script of SCPI commands. Some additional settings for
recording are provided on a separate tab in the dialog box.
● Recording..............................................................................................................844
● Managing recordings.............................................................................................847
● Recording settings................................................................................................ 849
12.5.2.1 Recording
Auto Recording
If enabled, the SCPI Recorder automatically records the required SCPI commands and
parameter values for the settings and functions you use while operating the FSW.
To view the list of currently recorded SCPI commands at any time, select the SCPI
Recorder icon in the toolbar.
Remove Last
Deletes the last recorded SCPI command from the list.
Load Recording
Loads an existing script in ASCII format (*.inp) from a file to the script editor. If the
editor contains recorded commands, you must confirm a message to overwrite them. A
file selection dialog box is displayed.
Save
Saves the current SCPI command list to the currently loaded or most recently
saved .inp recording file.
Save As
Saves the current SCPI command list to a new file in the
C:\R_S\INSTR\ScpiRecordings directory in ASCII format with the file exten-
sion .inp.
Tip: You can execute the command list in an .inp file without further editing using the
IECWIN tool provided with the FSW, see Section 12.4, "The IECWIN tool",
on page 840. You can also reload .inp files to the script editor later.
Export
Exports the current SCPI command list to the specified file and directory in the
selected format. By default, the file is stored in the
C:\R_S\INSTR\ScpiRecordings directory. Besides the recorded commands them-
selves, the exported script includes all format-specific header data required to execute
the script using an external program on the controller.
Before storing the file, you can display a "Preview" of the file in the selected format.
Currently, the following file formats are supported:
"C#" A commonly used general programming language for various applica-
tions (*.cs)
"C++" A commonly used general programming language for various applica-
tions (*.cpp)
"MATLAB A programming environment, frequently used in signal processing
(Instrument and test and measurement applications (*.m)
Control Tool- You can use this format directly with the MATLAB© Instrument Con-
box)" trol Toolbox.
"MATLAB You can use this format directly with the MATLAB© Toolkit.
(R&S Toolkit)"
"NICVI" An ANSI C programming environment designed for measurements
and tests (*.cvi)
You can use this format directly with National Instruments LabWind-
ows CVI.
"Plain SCPI" Represents SCPI base format, that is ASCII format, saved as a text
file (*.inp); contains no additional header data
Use this format to load a recorded script back to the editor later.
"Python" A commonly used general programming language for various applica-
tions (.py)
Remote command:
SYSTem:SRECorder:EXPort on page 1490
Clear All
Removes all recorded commands from the current SCPI command list.
Remote command:
SYSTem:SRECorder:CLEar on page 1488
Load Recording
Loads an existing script in ASCII format (*.inp) from a file to the script editor. If the
editor contains recorded commands, you must confirm a message to overwrite them. A
file selection dialog box is displayed.
Export
Exports the current SCPI command list to the specified file and directory in the
selected format. By default, the file is stored in the
C:\R_S\INSTR\ScpiRecordings directory. Besides the recorded commands them-
selves, the exported script includes all format-specific header data required to execute
the script using an external program on the controller.
Before storing the file, you can display a "Preview" of the file in the selected format.
Currently, the following file formats are supported:
"C#" A commonly used general programming language for various applica-
tions (*.cs)
"C++" A commonly used general programming language for various applica-
tions (*.cpp)
"MATLAB A programming environment, frequently used in signal processing
(Instrument and test and measurement applications (*.m)
Control Tool- You can use this format directly with the MATLAB© Instrument Con-
box)" trol Toolbox.
"MATLAB You can use this format directly with the MATLAB© Toolkit.
(R&S Toolkit)"
"NICVI" An ANSI C programming environment designed for measurements
and tests (*.cvi)
You can use this format directly with National Instruments LabWind-
ows CVI.
"Plain SCPI" Represents SCPI base format, that is ASCII format, saved as a text
file (*.inp); contains no additional header data
Use this format to load a recorded script back to the editor later.
"Python" A commonly used general programming language for various applica-
tions (.py)
Remote command:
SYSTem:SRECorder:EXPort on page 1490
Delete Recording
Deletes the selected recording file.
Import Recording
Imports the specified file to the script editor.
Some additional settings are available to configure the exported SCPI command files.
Add Synchronization Commands................................................................................849
Recording Format....................................................................................................... 849
Combined Recording of Spectrum Analyzer and R&S Signal Generator................... 850
IP Address or Computer name of Signal Generator................................................... 850
└ 123/ABC........................................................................................................850
└ Password...................................................................................................... 850
Test Connection.......................................................................................................... 850
Recording Format
Defines whether the commands are recorded using the short or long SCPI notation.
"Short" The shortform of the keyword is used.
Example: FREQ:CENT
"Long" The entire keyword is used.
Example: FREQuency:CENTer
Remote command:
SYSTem:SRECorder:FORMat on page 1491
Test Connection
The FSW attempts to establish a connection to the signal generator.
If an instrument is connected, the following information is displayed:
● Device type
● Name and serial number
● Connection state
Remote command:
CONFigure:GENerator:CONNection:CSTate? on page 1459
CONFigure:GENerator:CONNection[:STATe] on page 1460
The SCPI Recorder provides information on the required SCPI command for the avail-
able measurement settings, functions, and results in a context-sensitive menu.
1. Define the setting or navigate to the function you need the SCPI command for.
To find the query command for trace or marker results, select the result diagram.
2. On the screen, tap and hold, or right-click the measurement setting, function, or
result display.
The context-sensitive menu for that particular setting, function, or result is dis-
played.
Tip: If the SCPI command menu is not displayed, you probably tapped outside of a
softkey or input field, for example in a block diagram. Tap within the corresponding
softkey, button or input field, or in a result display, to display the context-sensitive
SCPI command menu.
3. Select "Show SCPI result query commands" or "Show SCPI command", depending
on which item you selected.
A dialog box with the required command and some functions is displayed.
If multiple commands are possible, for example to query different measurement
results, all possible commands are displayed.
4. To display the SCPI command dialog box for a query command, select the query
command you are interested in from the list.
Using the SCPI Recorder functions, you can create a SCPI script directly on the instru-
ment and then export the script for use on the controller. The SCPI Recorder allows
you to record SCPI command lists either automatically or manually.
2. From the SCPI command dialog box, select "Add SCPI Command to Recording".
The command is added to the SCPI Recorder command list.
3. Repeat these steps for any settings, functions, or results you want to record.
4. To check the progress of the recording, select the SCPI Recorder icon in the tool-
bar.
The SCPI Recorder dialog box with the currently recorded command list is dis-
played.
3. To remove the most recently recorded command, select "Remove Last" in the SCPI
Recorder dialog box.
2. Select "Export".
3. Define a file name and storage location for the script file.
4. Select the "File Type" which defines the format of the script.
5. Select "Save".
A script with the required header data for the selected format is stored to a file.
The following example shows a recorded SCPI script in python format. The script con-
figures the ACLR measurement example described in Section 6.2.7.1, "Measurement
example 1 – ACPR measurement on a CDMA2000 signal", on page 199.
# python script created by FSW: 29:11:2017 09:08:53
import visa
# Display update ON
FSW.write("SYST:DISP:UPD ON")
FSW.write("*RST")
FSW.write("INIT:CONT OFF")
FSW.write("SENS:FREQ:CENT 850000000")
FSW.write("SENS:FREQ:SPAN 4000000")
FSW.write("DISP:WIND:SUBW:TRAC:Y:SCAL:RLEV 10")
FSW.write("CALC:MARK:FUNC:POW:SEL ACP")
FSW.write("CALC:MARK:FUNC:POW:PRES S2CD")
FSW.write("SENS:ADJ:LEV;*WAI")
FSW.write("SENS:POW:HSP ON")
FSW.write("TRAC1:DATA? TRACE1")
FSW.query("CALC1:MARK:Y?")
FSW.write("CALC1:MARK:FUNC:POW:RES? CPOW")
The remote commands required to define these settings are described in Sec-
tion 13.10.7, "Configuring the network and remote control", on page 1438.
Step-by-step instructions are provided in Section 12.7, "How to set up a network and
remote control", on page 873.
● General network settings...................................................................................... 855
● GPIB settings........................................................................................................ 857
● Compatibility settings............................................................................................ 860
● LAN settings..........................................................................................................864
● HUMS settings...................................................................................................... 865
● Remote errors....................................................................................................... 871
● Returning to manual mode ("local")...................................................................... 873
Network settings can only be edited in the firmware if a LAN cable is connected to the
FSW.
Computer Name..........................................................................................................856
IP Address...................................................................................................................857
Subnet Mask............................................................................................................... 857
DHCP.......................................................................................................................... 857
Network Configuration.................................................................................................857
Computer Name
Each instrument is delivered with an assigned computer name, but this name can be
changed. The naming conventions of Windows apply. If too many characters and/or
numbers are entered, an error message is displayed in the status line.
The default instrument name is a non-case-sensitive string with the following syntax:
<Type><variant>-<serial_number>
For example FSW13-123456
The serial number can be found on the rear panel of the instrument. It is the third part
of the device ID printed on the bar code sticker:
IP Address
Defines the IP address. The TCP/IP protocol is preinstalled with the IP address
10.0.0.10. If the DHCP server is available ("DHCP On"), the setting is read-only.
The IP address consists of four number blocks separated by dots. Each block contains
3 numbers in maximum (e.g. 100.100.100.100), but also one or two numbers are
allowed in a block (as an example see the preinstalled address).
Subnet Mask
Defines the subnet mask. The TCP/IP protocol is preinstalled with the subnet mask
255.255.255.0. If the DHCP server is available ("DHCP On"), this setting is read-only.
The subnet mask consists of four number blocks separated by dots. Each block con-
tains 3 numbers in maximum (e.g. 100.100.100.100), but also one or two numbers are
allowed in a block (as an example see the preinstalled address).
DHCP
Switches between DHCP server available (On) or not available (Off). If a DHCP server
is available in the network, the IP address and subnet mask of the instrument are
obtained automatically from the DHCP server.
Network Configuration
Opens the standard Windows "Network Configuration" dialog box for further configura-
tion.
GPIB Address
Defines the GPIB address. Values from 0 to 30 are allowed. The default address is 20.
Remote command:
SYSTem:COMMunicate:GPIB[:SELF]:ADDRess on page 1438
Identification String
Defines the identification string for the FSW which is provided as a response to the
*IDN? query. Maximum 36 characters are allowed.
Remote command:
SYSTem:IDENtify[:STRing] on page 1440
Remote command:
SYSTem:IDENtify:FACTory on page 1440
GPIB Terminator
Changes the GPIB receive terminator.
"LFEOI" According to the standard, the terminator in ASCII is <LF> and/or
<EOI>.
"EOI" For binary data transfers (e.g. trace data) from the control computer
to the instrument, the binary code used for <LF> might be included in
the binary data block, and therefore should not be interpreted as a
terminator in this particular case. This can be avoided by using only
the receive terminator EOI.
Remote command:
SYSTem:COMMunicate:GPIB[:SELF]:RTERminator on page 1438
*IDN Format
Defines the response format to the remote command *IDN? (see *IDN?
on page 897). This function is intended for re-use of existing control programs
together with the FSW.
"Leg" Legacy format, as in the R&S FSP/FSU/FSQ family.
"New" FSW format.
Remote command:
SYSTem:FORMat:IDENt on page 1455
I/O Logging
Activates or deactivates the SCPI error log function. All remote control commands
received by the FSW are recorded in a log file. The files are named according to the
following syntax:
C:\R_S\INSTR\ScpiLogging\ScpiLog.<no.>
where <no.> is a sequential number
A new log file is started each time logging was stopped and is restarted.
Logging the commands may be extremely useful for debug purposes, e.g. in order to
find misspelled keywords in control programs.
Remote command:
SYSTem:CLOGging on page 1487
The error message remains in place when you switch to "Local" mode. To close the
message box, select the "Close" icon.
Only the most recent error is displayed in remote mode. However, in local mode, all
errors that occurred during remote operation are listed in a separate tab of the "Net-
work + Remote" dialog box (see Section 12.6.6, "Remote errors", on page 871).
Remote command:
SYSTem:ERRor:DISPlay on page 1440
SYSTem:ERRor:CLEar:REMote on page 1454
The FSW can emulate the GPIB interface of other signal and spectrum analyzers, e.g.
in order to use existing control applications.
The required settings are configured in the "Compatibility" tab of the "Network
+Remote" dialog box.
Language.................................................................................................................... 861
IF Gain........................................................................................................................ 862
Sweep Repeat.............................................................................................................862
Coupling...................................................................................................................... 862
Wideband.................................................................................................................... 863
FSU/FSQ Preamplifier................................................................................................ 863
HP Additional.............................................................................................................. 863
Revision String............................................................................................................ 863
Resetting the Factory Revision................................................................................... 863
Language
Defines the system language used to control the instrument.
For details on the available GPIB languages, see Section 13.14.2, "Reference: GPIB
commands of emulated HP models", on page 1496.
Note: This function is also used to emulate previous R&S signal and spectrum ana-
lyzers.
As a rule, the FSW supports most commands from previous R&S signal and spectrum
analyzers such as the FSQ, FSP, FSU, or FSV. However, the default values, in particu-
lar the number of sweep points or particular bandwidths, may vary. Therefore, the FSW
can emulate these other devices, including their default values, in order to repeat previ-
ous measurements or support existing control applications as in legacy systems.
For R&S FSP/FSQ/FSU emulation, HP commands are not automatically also allowed.
In this case, set SYSTem:HPADditional to ON.
Note: For PSA89600 emulation, the option is indicated as "B7J" for the *OPT? query
("B7J, 140" or "B7J, 122" if Wideband is activated, see SYSTem:PSA:WIDeband
on page 1495).
Remote command:
SYSTem:LANGuage on page 1494
IF Gain
Configures the internal IF gain settings in HP emulation mode due to the application
needs. This setting is only taken into account for resolution bandwidth < 300 kHz.
NORM Optimized for high dynamic range, overload limit is close to reference level.
PULS Optimized for pulsed signals, overload limit up to 10 dB above reference level.
Sweep Repeat
Controls a repeated sweep of the E1 and MKPK HI HP model commands (for details
on the commands refer to Section 13.14.2, "Reference: GPIB commands of emulated
HP models", on page 1496). If the repeated sweep is OFF, the marker is set without
sweeping before.
Note: In single sweep mode, switch off this setting before you set the marker via the
E1 and MKPK HI commands in order to avoid sweeping again.
This setting is only available if a HP language is selected (see "Language"
on page 861).
Remote command:
SYSTem:RSWeep on page 1496
Coupling
Controls the default coupling ratios in the HP emulation mode for:
● span and resolution bandwidth (Span/RBW)
● resolution bandwidth and video bandwidth (RBW/VBW)
For FSx, the standard parameter coupling of the instrument is used. As a result, in
most cases a shorter sweep time is used than in case of HP.
This setting is only available if a HP language is selected (see "Language"
on page 861).
Remote command:
SYSTem:HPCoupling on page 1493
Wideband
This setting defines which option is returned when the *OPT? query is executed,
depending on the state of the wideband option.
It is only available for PSA89600 emulation.
"Off" No wideband is used.
The option is indicated as "B7J".
"40 MHz" The 40 MHz wideband is used.
The option is indicated as "B7J, 140".
"80 MHz" The 80 MHz wideband is used.
The option is indicated as "B7J, 122".
Remote command:
SYSTem:PSA:WIDeband on page 1495
FSU/FSQ Preamplifier
This setting defines which option is returned when the *OPT? query is executed,
depending on the used preamplifier.
It is only available for FSU/FSQ emulation, and only if a preamplifier is used by the
FSW (-B24/-B25 option).
Remote command:
SYSTem:PREamp on page 1495
HP Additional
Allows the use of HP commands in addition to SCPI commands for R&S
FSP/FSQ/FSU emulation (see Language).
Remote command:
SYSTem:HPADditional on page 1494
Revision String
Defines the response to the REV? query for the revision number.
(HP emulation only, see "Language" on page 861).
Max. 36 characters are allowed.
Remote command:
SYSTem:REVision[:STRing] on page 1496
"IP address" IP address of the FSW as defined in the operating system (see also
"IP Address" on page 857).
LAN Password
Password for LAN configuration. The default password is LxiWebIfc.
Remote command:
SYSTem:LXI:PASSword on page 1441
LAN Reset
Resets the "LAN" configuration to its default settings (LCI function).
Parameter Value
The LAN settings are configured in the "Network" tab of the "Network + Remote" dialog
box or using the instrument's "LAN" web browser interface.
Remote command:
SYSTem:LXI:LANReset on page 1441
For <interface> = snmp, you get a ZIP file containing the MIB files for SNMP. For
<interface> = rest, you get a YAML file with the OpenAPI specification of the REST
API.
Address example: http://fsw8-123456/api/hums/v1/documents?name=snmp.
The following table lists the REST endpoints and the SNMP MIB filenames.
For further information about the HUMS service itself, see R&S HUMS user manual.
You can download or view the manual on the internet.
● Basic settings........................................................................................................ 866
● Protocol settings....................................................................................................867
● Device tags........................................................................................................... 870
The remote commands to configure HUMS are described in Section 13.10.8, "Config-
uring HUMS", on page 1443.
State............................................................................................................................866
Enhanced Settings...................................................................................................... 867
View Tracked Information............................................................................................867
Delete HUMS History.................................................................................................. 867
State
Turns HUMS on or off.
If you want to track HUMS data, turn on this function.
If HUMS has been used before, turning on restores the previous protocol settings.
Remote command:
DIAGnostic:HUMS:STATe on page 1444
Enhanced Settings
Opens the dialog to configure the protocol settings and device tags.
Access: [SETUP] > "Network + Remote" > "HUMS" > "Enhanced Settings" > "Config-
ure" > "Protocol"
The "Protocol" tab of the "Enhanced Settings" dialog provides protocol settings for
SNMP or REST protocol.
SNMP..........................................................................................................................868
REST...........................................................................................................................868
SNMPv2c Configuration..............................................................................................868
└ Access.......................................................................................................... 868
└ Community....................................................................................................868
SNMPv3 Configuration................................................................................................869
└ User Name....................................................................................................869
└ Access.......................................................................................................... 869
└ Security Level............................................................................................... 869
└ Passwords.................................................................................................... 869
SNMP Location........................................................................................................... 870
SNMP Contact............................................................................................................ 870
SNMP
Selects the SNMP version to communicate with the service.
"None" Do not use SNMP.
"v2c" Select SNMP version v2c, which also activates v1.
Unlocks the settings available for SNMP v2c.
"v3" Select SNMP version v3.
Unlocks the settings available for SNMP v3.
"v2c + v3" Select both SNMP versions v2c and v3.
Unlocks the settings for both SNMP v2c and v3.
Remote command:
SYSTem:COMMunicate:SNMP:VERSion on page 1448
REST
Turns communication via REST API on or off.
Remote command:
SYSTem:COMMunicate:REST:ENABle on page 1445
SNMPv2c Configuration
For SNMPv2c/v1 authentication, you can define the "Access" and "Community".
SNMPv3 Configuration
For SNMPv3 authentication, you can define user profiles. You can manage them via a
table.
To add a new user, select "Add" and enter the data.
To delete all user profiles, select "Delete All".
To delete a single user profile, select the "x" in the appropriate user line of the table.
Remote command:
Create user: SYSTem:COMMunicate:SNMP:USM:USER on page 1447
Query all users: SYSTem:COMMunicate:SNMP:USM:USER:ALL? on page 1447
Delete a single user: SYSTem:COMMunicate:SNMP:USM:USER:DELete
on page 1448
Delete all users: SYSTem:COMMunicate:SNMP:USM:USER:DELete:ALL
on page 1448
SNMP Location
"SNMP Location" defines the SNMP location information. This information complies
with the server's physical location and is used for identification of the SNMP server. By
default, this input field is empty.
Remote command:
SYSTem:COMMunicate:SNMP:LOCation on page 1447
SNMP Contact
"SNMP Contact" defines the SNMP contact information. This information complies with
the person who manages the SNMP server and is used for identification of the SNMP
server. By default, this input field is empty.
Remote command:
SYSTem:COMMunicate:SNMP:CONTact on page 1446
Access: [SETUP] > "Network + Remote" > "HUMS" > "Enhanced Settings" > "Config-
ure" > "Device Tags"
The "Device Tags" tab of the "Enhanced Settings" dialogs displays the defined device
tags. You can also add or delete device tags here.
A device tag is a label to assign to your instrument. You can create any device tag for
your instrument and define it by a specific key and value.
Add..............................................................................................................................871
Index........................................................................................................................... 871
Key.............................................................................................................................. 871
Value........................................................................................................................... 871
Delete All.....................................................................................................................871
Add
Adds a new device tag.
Remote command:
DIAGnostic:HUMS:TAGS[:VALue] on page 1445
Index
Index (ID) of the created device tag. You can change the ID if necessary.
Key
Defines a key for your device tag. A device tag key represents the type of tag.
Value
Defines the actual value of the device tag or key.
Example:
● "Key" = Location
● "Value" = Building 1
Remote command:
DIAGnostic:HUMS:TAGS:ALL? on page 1444
Delete All
Deletes all defined device tags.
Remote command:
Delete all device tags:DIAGnostic:HUMS:TAGS:DELete:ALL on page 1444
Delete a single device tag:DIAGnostic:HUMS:TAGS:DELete on page 1445
The most recent error message during remote operation can be displayed on the
screen, see "Display Remote Errors" on page 860.
If the number of error messages exceeds the capacity of the error buffer, the oldest
error message is removed before the newest one is inserted. To clear the message
buffer use "Clear Error List". It is automatically cleared when the FSW is shut down.
The following information is available:
Remote command:
SYSTem:ERRor:LIST? on page 1454
When switched on, the instrument is always in the manual measurement mode and
can be operated via the front panel. As soon as the instrument receives a remote com-
mand, it is switched to the remote control mode.
In remote control mode, all keys of the instrument are disabled. The "LOCAL" softkey
and the Remote Display Update softkey are displayed.
Local
The instrument switches from remote to manual operation.
Note:
● If the local lockout function (LLO or SYST:KLOC ON) is activated in the remote con-
trol mode, manual operation is no longer available until GTL (or SYST:KLOC OFF)
is executed.
● Before you switch back to manual operation, all remote command processing must
be completed. Otherwise, the instrument will switch back to remote control immedi-
ately.
● If you select "Local" while a self-alignment or a self-test is still running (which was
started remotely), the instrument only returns to the manual operation state when
the alignment or test is completed.
Furthermore, when you return to manual operation, the following happens:
● All front panel keys are enabled.
● The main softkey menu of the current mode is displayed.
● The measurement diagrams, traces and display fields are displayed again.
● If, at the time of pressing "LOCAL", the synchronization mechanism via *OPC,
*OPC? or *WAI is active, the currently running measurement procedure is aborted
and synchronization is achieved by setting the corresponding bits in the registers of
the status reporting system.
● Bit 6 (User Request) of the Event status register is set.
If the status reporting system is configured accordingly, this bit immediately causes
the generation of a service request (SRQ) to inform the control software that the
user wishes to return to front panel control. For example, this can be used to inter-
rupt the control program and to correct instrument settings manually. This bit is set
each time you select "LOCAL".
Remote command:
SYST:COMM:INT:REM OFF, see SYSTem:COMMunicate:INTernal:REMote
on page 1439
Remote operation
You can operate the instrument remotely from a connected computer using SCPI com-
mands. Before you send remote commands, configure the instrument in a LAN net-
work or connect it to a PC via the GPIB interface as described in Section 12.7.1, "How
to configure a network", on page 874.
Remote Desktop
In production test and measurement, a common requirement is central monitoring of
the T&M instruments for remote maintenance and remote diagnostics. Equipped with
the Remote Desktop software of Windows, the FSW ideally meets requirements for
use in production. The computer that is used for remote operation is called "controller"
here.
The following tasks can be performed using Remote Desktop:
● Access to the control functions via a virtual front panel (soft front panel)
● Printout of measurement results directly from the controller
● Storage of measured data on the controller's hard disk
This documentation provides basic instructions on setting up the Remote Desktop for
the FSW. For details refer to the Windows 10 operating system documentation.
If the instrument is connected to the LAN, Windows automatically detects the network
connection and activates the required drivers.
The network card can be operated with a 1 GBit Ethernet IEEE 802.3u interface.
Depending on the network capacities, the TCP/IP address information for the instru-
ment can be obtained in different ways.
● If the network supports dynamic TCP/IP configuration using the Dynamic Host
Configuration Protocol (DHCP), all address information can be assigned automati-
cally.
● If the network does not support DHCP, or if the instrument is set to use alternate
TCP/IP configuration, the addresses must be set manually.
By default, the instrument is configured to use dynamic TCP/IP configuration and
obtain all address information automatically. Thus, it is safe to establish a physical con-
nection to the LAN without any previous instrument configuration.
When a DHCP server is used, a new IP address can be assigned each time the PC is
restarted. You have to determine this address on the PC itself. Thus, when using a
DHCP server, we recommend using the permanent computer name, which determines
the address via the DNS server (see "Using a DNS server to determine the IP address"
on page 876).
4. In the "Network + Remote" dialog, toggle the "DHCP On/Off" setting to the required
mode.
If DHCP is "Off", you must enter the IP address manually, as described in the fol-
lowing steps.
Note: When you switch DHCP from "On" to "Off", the previously set IP address
and subnet mask are retrieved.
If DHCP is "On", the instrument obtains the IP address of the DHCP server auto-
matically. The configuration is saved, and the FSW prompts you to restart the
instrument. You can skip the remaining steps.
Note: When a DHCP server is used, a new IP address can be assigned each time
you restart the instrument. You have to determine this address on the instrument
itself. Thus, when using a DHCP server, we recommend using the permanent com-
puter name. Then the address is determined via the DNS server.
(See "Using a DNS server to determine the IP address" on page 876 and Sec-
tion 12.7.1.3, "How to change the instrument name", on page 877).
5. Enter the "IP Address", for example 192.0.2.0. The IP address consists of four
number blocks separated by dots. Every block contains a maximum of 3 numbers.
6. Enter the "Subnet Mask", for example 255.255.255.0. The subnet mask consists of
four number blocks separated by dots. Every block contains a maximum of 3 num-
bers.
4. Double-tap "Ethernet".
6. Tap the entry named "Internet Protocol Version 4 (TCP/IPv4)" to highlight it.
7. Select "Properties".
8. On the "General" tab, select "Use the following DNS server addresses".
In a LAN that uses a DNS server, each PC or instrument connected in the LAN can be
accessed via an unambiguous computer name instead of the IP address. The DNS
server translates the host name to the IP address. Using the computer name is espe-
cially useful when a DHCP server is used, as a new IP address can be assigned each
time the instrument is restarted.
Each instrument is delivered with an assigned computer name, but you can change
this name.
12.7.1.4 How to configure the LAN using the web browser interface
The instrument's "LAN" web browser interface works correctly with all W3C compliant
browsers.
The instrument home page displays device information, including the VISA resource
string, in read-only format.
► On the "Instrument Home Page", select "Device Indicator" to activate or deactivate
the "LAN" status icon on the status bar of the FSW. The "Device Indicator" setting
is not password-protected.
A green "LAN" status symbol indicates that a LAN connection is established.
A red symbol indicates an error, for example, that no LAN cable is connected.
When a device is connecting to the instrument, the "LAN" icon blinks.
The most important control elements in the navigation pane of the browser interface
are the following:
LAN configuration
The LAN configuration consists of three parts:
● "IP configuration" provides all mandatory LAN parameters.
● "Advanced LAN Configuration" provides further LAN settings.
● "Ping Client" provides the ping utility to verify the connection between the instru-
ment and other devices.
IP configuration
The "LAN Configuration > IP configuration" web page displays all mandatory LAN
parameters and allows their modification.
The "TCP/IP Mode" configuration field controls how the IP address for the instrument
gets assigned (see also Section 12.7.1.2, "How to assign the IP address",
on page 875).
For the manual configuration mode, the static IP address, subnet mask, and default
gateway are used to configure the LAN. The automatic configuration mode uses DHCP
server or Dynamic Link Local Addressing (Automatic IP) to obtain the instrument IP
address.
Ping client
Ping is a utility that verifies the connection between the instrument and another device.
The ping command uses the ICMP echo request and echo reply packets to determine
whether the LAN connection is functional. Ping is useful for diagnosing IP network or
router failures. The ping utility is not password-protected.
To initiate a ping between the instrument and a second connected device:
2. Enter the IP address of the second device without the ping command and with-
out any further parameters into the "Destination Address" field (e.g.
10.113.10.203).
3. Select "Submit".
To operate the instrument via remote control, it must be addressed using the GPIB
address. The remote control address is factory-set to 20, but it can be changed if it
does not fit in the network environment. For remote control, addresses 0 through 30
are allowed. The GPIB address is maintained after a reset of the instrument settings.
Remote command:
SYST:COMM:GPIB:ADDR 18
Windows 10 requires that users identify themselves by entering a user name and pass-
word in a login window. You can set up two types of user accounts, either an adminis-
trator account with unrestricted access to the computer/domain or a standard user
account with limited access.
The instrument provides an auto-login function for the administrator account, i.e. login
with unrestricted access is carried out automatically in the background. By default, the
user name for the administrator account is "Instrument", and the user name for the
standard user account is "NormalUser".
In both cases the initial password is "894129". You can change the password in Win-
dows 10 for any user at any time. Some administrative tasks require administrator
rights (e.g. firmware updates or the configuration of a LAN network). If so, it is men-
tioned in the function descriptions.
At the same time you log on to the operating system, you are automatically logged on
to the network. As a prerequisite, the user name and the password must be identical
on the instrument and on the network.
After the software for the network has been installed, the instrument issues an error
message the next time it is switched on because there is no user named "instrument"
(= default user ID for Windows auto-login) in the network. Thus, a matching user must
be created in the FSW and in the network, the password must be adapted to the net-
work password, and the auto-login mechanism must then be deactivated.
The network administrator is responsible for creating new users in the network.
1.
Select the "Windows" icon in the toolbar to access the operating system.
4. In the "Microsoft account" dialog box, enter the new user name and password.
5. Select "OK".
6. Select "Finish".
The new user is created.
After the new user has been created on the instrument, the password must be adapted
to the network password.
1.
Select the "Windows" icon in the toolbar to access the operating system.
6. Press [Enter].
The new password is now active.
1. Select the "Windows" icon in the toolbar to access the operating system of the
FSW (see also "To access the "Start" menu" on page 38).
Sharing directories makes data available for other users. Sharing directories is only
possible in Microsoft networks. Sharing is a property of a file or directory.
1. In the "Start" menu, select "Programs" > "Accessories" > "Windows Explorer".
5. Select "Add"
6. Select "Share".
12.7.5 How to control the FSW via the web browser interface
Via the LAN web browser interface to the FSW, one or more users can control the
instrument remotely from another PC without additional installation. Most instrument
controls are available via the front panel simulation. File upload and download between
the instrument and the remote PC is also available.
4. Use the mouse cursor to access the functionality in the software front panel or in
the display as you would directly on the instrument's front panel.
2. In the navigation pane, select "Instrument Control" > "File Upload" or "File Down-
load".
The most commonly used folders on the instrument are displayed. For example,
folders that contain user data. From the top-most folder, My Computer, you can
access all other folders on the instrument.
If you want to prevent other users in the LAN from accessing or operating the FSW via
its LAN web browser interface, you must deactivate this function. Note that after a
firmware update the function is automatically active again until you deactivate it
manually.
Select the "Windows" icon in the toolbar to access the operating system.
7. Select "Stop".
8. Select "Apply".
The next time a user enters the IP address of the instrument in a web browser, an
error message is displayed:
Failed to connect to server (code. 1006)
Remote Desktop is a Windows application which can be used to access and control
the instrument from a remote computer through a LAN connection. While the instru-
ment is in operation, the instrument screen contents are displayed on the remote com-
puter, and Remote Desktop provides access to all of the applications, files, and net-
work resources of the instrument. Thus, remote operation of the FSW is possible.
With Windows 10, Remote Desktop Client is part of the operating system. For other
versions of Windows, Microsoft offers the Remote Desktop Client as an add-on. For
details refer to the Windows 10 operating system documentation.
With the factory settings, the default "instrument" user can connect to the FSW with the
Remote Desktop program of the controller immediately. No further configuration is
required. However, if the connection fails or other users need to connect, this section
provides basic instructions on setting up the Remote Desktop for the FSW.
12.7.7.1 How to configure the FSW for remote operation via remote desktop
1. Create a fixed IP address for the TCP/IP protocol as described in Section 12.7.1.2,
"How to assign the IP address", on page 875.
Note: To avoid problems, use a fixed IP address.
When a DHCP server is used, a new IP address is assigned each time the instru-
ment is restarted. This address must first be determined on the instrument itself.
Thus, using a DHCP server is not suitable for remote operation of the FSW via
Remote Desktop.
2.
Select the "Windows" icon in the toolbar to access the operating system.
6. Define which users can access the FSW via Remote Desktop.
Note: The currently used user account is automatically enabled for Remote Desk-
top.
7. The FSW is now ready for connection setup with the Remote Desktop program of
the controller.
1.
Select the "Windows" icon in the toolbar to access the operating system.
2. From the "Start" menu, select "All Programs" > "Accessories" > "Remote Desktop
Connection".
The "Remote Desktop Connection" dialog box is displayed.
5. In the list, select the appropriate connection (for example: "LAN (10 Mbps or
higher)").
Depending on your selection (and how powerful the connection is), the options are
activated or deactivated.
6. To improve the performance, you can deactivate the "Desktop background", "Show
contents of window while dragging" and "Menu and window animation" options.
7. Open the "Local Resources" tab to enable printers, local drives and serial interfa-
ces.
8. To access drives of the controller from the FSW, e.g. to store settings or to copy
files from the controller to the FSW:
a) Select "More".
9. To use printers connected to the controller while accessing them from the FSW,
activate the "Printers" option. Do not change the remaining settings.
11. Under "Remote desktop size", you can set the size of the FSW window on the
desktop of the controller.
13. Set the "Display the connection bar when I use the full screen" option:
● If activated, a bar showing the network address of the FSW appears at the top
edge of the screen. You can use this bar to reduce, minimize or close the win-
dow.
● If deactivated, the only way you can return to the controller desktop from the
FSW screen in full screen mode is to select "Disconnect" from the "Start"
menu.
5. Select "Connect".
The connection is set up.
6. If the "Disk drives" option is enabled on the "Local Resources" tab, a warning is
displayed indicating that the drives are enabled for access from the FSW.
Select "OK" to confirm the warning.
After a few moments, the FSW screen is displayed.
7. If a dark screen appears or a dark square appears in the upper left-hand corner of
the screen, restart the FSW to see the modified screen resolution.
a) Press the key combination [ALT] + [F4].
The FSW firmware is shut down, which can take a few seconds.
b)
The firmware restarts and then automatically opens the "Softfrontpanel", i.e. the
user interface on which all front panel controls and the rotary knob are mapped to
buttons.
For more information, see Section 11.2.3, "How to work with the soft front panels",
on page 748.
To access the Windows "Start" menu, expand the "Remote Desktop" window to full
size.
During the connection with the controller, the login dialog box is displayed on the
FSW screen.
When you switch on the FSW, it is always in manual operation state ("local" state) and
can be operated via the front panel.
4. To prevent unintentional return to manual operation, disable the keys of the instru-
ment using the universal command LLO.
Switching to manual mode is only possible via remote control then. This function is
only available for the GPIB interface.
5. To enable the keys of the FSW again, switch the instrument to local mode (GTL -
Go to Local), i.e. deactivate the REN line of the remote control interface.
Before you switch back to manual operation, all remote command processing must be
completed. Otherwise, the instrument switches back to remote control immediately.
If you select "Local" while a self-alignment or a self-test is still running (which was star-
ted remotely), the instrument only returns to the manual operation state when the align-
ment or test is completed.
13 Remote commands
The commands required to perform measurements in the Spectrum application in a
remote environment are described here.
It is assumed that the FSW has already been set up for remote operation in a network
as described in Section 12.7, "How to set up a network and remote control",
on page 873.
Parameters that are only returned as the result of a query are indicated as "Return
values".
● Conformity
Commands that are taken from the SCPI standard are indicated as "SCPI con-
firmed". All commands used by the FSW follow the SCPI syntax rules.
● Asynchronous commands
A command which does not automatically finish executing before the next com-
mand starts executing (overlapping command) is indicated as an "Asynchronous
command".
● Reset values (*RST)
Default parameter values that are used directly after resetting the instrument (*RST
command) are indicated as "*RST" values, if available.
● Default unit
The default unit is used for numeric values if no other unit is provided with the
parameter.
● Manual operation
If the result of a remote command can also be achieved in manual operation, a link
to the description is inserted.
<m> 1 to 16 Marker
<t> 1 to 6 Trace
*IDN?............................................................................................................................897
*IST?............................................................................................................................ 897
*OPC............................................................................................................................ 897
*OPT?...........................................................................................................................897
*PCB............................................................................................................................ 898
*PRE............................................................................................................................ 898
*PSC............................................................................................................................ 898
*RST.............................................................................................................................899
*SRE............................................................................................................................ 899
*STB?...........................................................................................................................899
*TRG............................................................................................................................ 899
*TST?........................................................................................................................... 899
*WAI............................................................................................................................. 900
*CAL?
Calibration query
Initiates a calibration of the instrument and then queries the calibration status. Respon-
ses > 0 indicate errors.
Note: If you start a self-alignment remotely, then select the "Local" softkey while the
alignment is still running, the instrument only returns to the manual operation state
after the alignment is completed.
Usage: Query only
Manual operation: See "Start Self Alignment" on page 732
*CLS
Clear status
Sets the status byte (STB), the standard event register (ESR) and the EVENt part of
the QUEStionable and the OPERation registers to zero. The command does not
alter the mask and transition parts of the registers. It clears the output buffer.
Usage: Setting only
*ESE <Value>
Event status enable
Sets the event status enable register to the specified value. The query returns the con-
tents of the event status enable register in decimal form.
Parameters:
<Value> Range: 0 to 255
*ESR?
Event status read
Returns the contents of the event status register in decimal form and then sets the reg-
ister to zero.
Return values:
<Contents> Range: 0 to 255
Usage: Query only
*IDN?
Identification
Returns the instrument identification.
Return values:
<ID> "Rohde&Schwarz,<device type>,<part number>/<serial num-
ber>,<firmware version>"
Example: Rohde&Schwarz,FSW-26,1312.8000K26/100005,1.30
Usage: Query only
*IST?
Individual status query
Returns the contents of the IST flag in decimal form. The IST flag is the status bit
which is sent during a parallel poll.
Return values:
<ISTflag> 0|1
Usage: Query only
*OPC
Operation complete
Sets bit 0 in the event status register when all preceding commands have been execu-
ted. This bit can be used to initiate a service request. The query writes a "1" into the
output buffer when all preceding commands have been executed, which is useful for
command synchronization.
*OPT?
Option identification query
Queries the options included in the instrument. For a list of all available options and
their description, refer to the specifications document.
Return values:
<Options> The query returns a list of all installed and activated options,
separated by commas, where:
B<number> describes hardware options.
*PCB <Address>
Pass control back
Indicates the controller address to which remote control is returned after termination of
the triggered action.
Setting parameters:
<Address> Range: 0 to 30
Usage: Setting only
*PRE <Value>
Parallel poll register enable
Sets parallel poll enable register to the indicated value. The query returns the contents
of the parallel poll enable register in decimal form.
Parameters:
<Value> Range: 0 to 255
*PSC <Action>
Power on status clear
Determines whether the contents of the ENABle registers are preserved or reset when
the instrument is switched on. Thus a service request can be triggered when the instru-
ment is switched on, if the status registers ESE and SRE are suitably configured. The
query reads out the contents of the "power-on-status-clear" flag.
Parameters:
<Action> 0|1
0
The contents of the status registers are preserved.
1
Resets the status registers.
*RST
Reset
Sets the instrument to a defined default status. The default settings are indicated in the
description of commands.
The command is equivalent to SYSTem:PRESet.
Note that the factory set default values can be modified to user-defined settings (see
MMEMory:LOAD:STATe on page 1362). For more details on default values, see Sec-
tion 10.1, "Restoring the default instrument configuration (preset)", on page 676.
Usage: Setting only
*SRE <Contents>
Service request enable
Sets the service request enable register to the indicated value. This command deter-
mines under which conditions a service request is triggered.
Parameters:
<Contents> Contents of the service request enable register in decimal form.
Bit 6 (MSS mask bit) is always 0.
Range: 0 to 255
*STB?
Status byte query
Reads the contents of the status byte in decimal form.
Usage: Query only
*TRG
Trigger
Triggers all actions waiting for a trigger event. In particular, *TRG generates a manual
trigger signal. This common command complements the commands of the TRIGger
subsystem.
*TRG corresponds to the INITiate:IMMediate command.
See INITiate<n>[:IMMediate] on page 913.
Usage: Event
*TST?
Self-test query
Initiates self-tests of the instrument and returns an error code.
Note: If you start a self-test remotely, then select the "Local" softkey while the test is
still running, the instrument only returns to the manual operation state after the test is
completed. In this case, you cannot abort the self-test.
Return values:
<ErrorCode> integer > 0 (in decimal format)
An error occurred.
For details, see the Service Manual supplied with the instrument.
0
No errors occurred.
Usage: Query only
*WAI
Wait to continue
Prevents servicing of the subsequent commands until all preceding commands have
been executed and all signals have settled (see also command synchronization and
*OPC).
Usage: Event
DISPlay:ATAB................................................................................................................901
INSTrument:CREate:DUPLicate...................................................................................... 901
INSTrument:CREate[:NEW]............................................................................................ 901
INSTrument:CREate:REPLace........................................................................................ 902
INSTrument:DELete....................................................................................................... 902
INSTrument:LIST?......................................................................................................... 902
INSTrument:MODE........................................................................................................ 904
INSTrument:REName.....................................................................................................905
INSTrument[:SELect]......................................................................................................905
DISPlay:ATAB <State>
This command switches between the MultiView tab and the most recently displayed
channel. If only one channel is active, this command has no effect.
Parameters:
<State> ON | OFF | 0 | 1
OFF | 0
Switches off the function.
ON | 1
Switches on the function.
INSTrument:CREate:DUPLicate
Duplicates the currently selected channel, i.e creates a new channel of the same type
and with the identical measurement settings. The name of the new channel is the
same as the copied channel, extended by a consecutive number (e.g. "IQAnalyzer" ->
"IQAnalyzer 2").
The channel to be duplicated must be selected first using the INST:SEL command.
Is not available if the MSRA/MSRT primary channel is selected.
Example: INST:SEL 'IQAnalyzer'
INST:CRE:DUPL
Duplicates the channel named 'IQAnalyzer' and creates a new
channel named 'IQAnalyzer2'.
Usage: Event
Manual operation: See "Duplicate Current Channel" on page 124
INSTrument:DELete <ChannelName>
Deletes a channel.
If you delete the last channel, the default "Spectrum" channel is activated.
Setting parameters:
<ChannelName> String containing the name of the channel you want to delete.
A channel must exist to delete it.
Example: INST:DEL 'IQAnalyzer4'
Deletes the channel with the name 'IQAnalyzer4'.
Usage: Setting only
Manual operation: See "Closing an application" on page 124
INSTrument:LIST?
Queries all active channels. The query is useful to obtain the names of the existing
channels, which are required to replace or delete the channels.
Return values:
<ChannelType>, For each channel, the command returns the channel type and
<ChannelName> channel name (see tables below).
Tip: to change the channel name, use the INSTrument:
REName command.
Example: INST:LIST?
Result for 3 channels:
'ADEM','Analog Demod','IQ','IQ
Analyzer','IQ','IQ Analyzer2'
Usage: Query only
Table 13-2: Available channel types and default channel names in Signal and Spectrum Analyzer
mode
*) If the specified name for a new channel already exists, the default name, extended by a sequential num-
ber, is used for the new channel.
*) If the specified name for a new channel already exists, the default name, extended by a sequential num-
ber, is used for the new channel.
INSTrument:MODE <OpMode>
The operating mode of the FSW determines which applications are available and
active. Whenever you change the operating mode, the currently active channels are
closed. The default operating mode is Signal and Spectrum Analyzer mode, however,
the presetting can be changed.
(See the "Instrument Setup" section in the FSW User Manual).
For details on operating modes and applications see Section 5, "Applications, mea-
surement channels, and operating modes", on page 111.
Parameters:
<OpMode> SANalyzer
Signal and Spectrum Analyzer mode
MSRanalyzer
Multi-Standard Radio Analysis (MSRA) mode
RTMStandard
Multi-Standard Real-Time (MSRT) mode
Only available if one of the real-time options is installed.
*RST: SAN
Example: INST:MODE MSR
Switches to Multi-Standard Radio Analysis (MSRA) mode.
Manual operation: See "Switching the operating mode" on page 123
INITiate:SEQuencer:ABORt
Stops the currently active sequence of measurements.
You can start a new sequence any time using INITiate:SEQuencer:IMMediate
on page 907.
Usage: Event
Manual operation: See "Sequencer State" on page 127
INITiate:SEQuencer:IMMediate
Starts a new sequence of measurements by the Sequencer.
Its effect is similar to the INITiate<n>[:IMMediate] command used for a single
measurement.
Before this command can be executed, the Sequencer must be activated (see
SYSTem:SEQuencer on page 908).
Example: SYST:SEQ ON
Activates the Sequencer.
INIT:SEQ:MODE SING
Sets single sequence mode so each active measurement is per-
formed once.
INIT:SEQ:IMM
Starts the sequential measurements.
Manual operation: See "Sequencer State" on page 127
INITiate:SEQuencer:MODE <Mode>
Defines the capture mode for the entire measurement sequence and all measurement
groups and channels it contains.
Note: To synchronize to the end of a measurement sequence using *OPC, *OPC? or
*WAI, use SINGle Sequencer mode.
Parameters:
<Mode> SINGle
Each measurement group is started one after the other in the
order of definition. All measurement channels in a group are
started simultaneously and performed once. After all measure-
ments are completed, the next group is started. After the last
group, the measurement sequence is finished.
CONTinuous
Each measurement group is started one after the other in the
order of definition. All measurement channels in a group are
started simultaneously and performed once. After all measure-
ments are completed, the next group is started. After the last
group, the measurement sequence restarts with the first one and
continues until it is stopped explicitly.
*RST: CONTinuous
Manual operation: See "Sequencer Mode" on page 127
SYSTem:SEQuencer <State>
Turns the Sequencer on and off. The Sequencer must be active before any other
Sequencer commands (INIT:SEQ...) are executed, otherwise an error occurs.
A detailed programming example is provided in Section 13.4.3, "Programming exam-
ple: performing a sequence of measurements", on page 908.
Parameters:
<State> ON | OFF | 0 | 1
ON | 1
The Sequencer is activated and a sequential measurement is
started immediately.
OFF | 0
The Sequencer is deactivated. Any running sequential measure-
ments are stopped. Further Sequencer commands
(INIT:SEQ...) are not available.
*RST: 0
Example: SYST:SEQ ON
Activates the Sequencer.
INIT:SEQ:MODE SING
Sets single Sequencer mode so each active measurement is
performed once.
INIT:SEQ:IMM
Starts the sequential measurements.
SYST:SEQ OFF
Manual operation: See "Sequencer State" on page 127
DISP:TRAC1:MODE BLANK
DISP:TRAC2:MODE MAXH
DISP:TRAC3:MODE MINH
//Switch to single sweep mode
INIT:CONT OFF
//switch back to first (default) analyzer channel
INST:SEL 'Spectrum';*WAI
//Switch into SEM
SENSe:SWEep:MODE ESPectrum
//Load Sem standard file for W-CDMA
SENSe:ESPectrum:PRESet:STANdard 'WCDMA\3GPP\DL\3GPP_DL.xml'
//Set sweep count in Spectrum channel
SENS:SWEEP:COUNT 5
SYSTem:SEQuencer ON
//Start sweep in Sequencer
INITiate:SEQuencer:IMMediate;*OPC?
//Switch into first IQ channel to get results
INST:SEL 'IQ 1';*WAI
CALCulate:MARKer:MAXimum
CALC:MARK:Y?
//Change sweep time in IQ
SENS:SWE:TIME 300us
//Switch to single Sequencer mode
INITiate:SEQuencer:MODE SINGle
//Sweep all channels once, taking the sweep count in each channel into account
INITiate:SEQuencer:IMMediate;*OPC?
//Set marker to maximum in IQ1 and query result
CALCulate:MARKer:MAXimum
CALC:MARK:Y?
//Switch to second IQ channel and retrieve results
INST:SEL 'IQ 2';*WAI
CALCulate:MARKer:MIN
CALC:MARK:Y?
//Switch to first Spectrum channel
INST:SEL 'Spectrum';*WAI
//Query one of the SEM results
CALCulate:MARKer:FUNCtion:POWer:RESult? CPOWer
//Switch to second Spectrum channel
INST:SEL 'Spectrum 2';*WAI
//Query channel power result
CALCulate:MARKer:FUNCtion:POWer:RESult? ACPower
ABORt
Aborts the measurement in the current channel and resets the trigger system.
To prevent overlapping execution of the subsequent command before the measure-
ment has been aborted successfully, use the *OPC? or *WAI command after ABOR and
before the next command.
For details on overlapping execution see Remote control via SCPI.
Note on blocked remote control programs:
If a sequential command cannot be completed, for example because a triggered sweep
never receives a trigger, the remote control program will never finish and the remote
channel to the FSW is blocked for further commands. In this case, you must interrupt
processing on the remote channel first in order to abort the measurement.
To do so, send a "Device Clear" command from the control instrument to the FSW on a
parallel channel to clear all currently active remote channels. Depending on the used
interface and protocol, send the following commands:
● Visa: viClear()
● GPIB: ibclr()
● RSIB: RSDLLibclr()
Now you can send the ABORt command on the remote channel performing the mea-
surement.
Example: ABOR;:INIT:IMM
Aborts the current measurement and immediately starts a new
one.
Example: ABOR;*WAI
INIT:IMM
Aborts the current measurement and starts a new one once
abortion has been completed.
Usage: Event
INITiate<n>:CONMeas
Restarts a (single) measurement that has been stopped (using ABORt) or finished in
single sweep mode.
The measurement is restarted at the beginning, not where the previous measurement
was stopped.
As opposed to INITiate<n>[:IMMediate], this command does not reset traces in
maxhold, minhold or average mode. Therefore it can be used to continue measure-
ments using maxhold or averaging functions.
Suffix: .
<n> irrelevant
Example: INIT:CONT OFF
Switches to single sweep mode.
DISP:WIND:TRAC:MODE AVER
Switches on trace averaging.
SWE:COUN 20
Setting the sweep counter to 20 sweeps.
INIT;*WAI
Starts the measurement and waits for the end of the 20 sweeps.
INIT:CONM;*WAI
Continues the measurement (next 20 sweeps) and waits for the
end.
Result: Averaging is performed over 40 sweeps.
Usage: Asynchronous command
Manual operation: See "Continue Single Sweep" on page 509
INITiate<n>:CONTinuous <State>
Controls the sweep mode for an individual channel.
Note that in single sweep mode, you can synchronize to the end of the measurement
with *OPC, *OPC? or *WAI. In continuous sweep mode, synchronization to the end of
the measurement is not possible. Thus, it is not recommended that you use continuous
sweep mode in remote control, as results like trace data or markers are only valid after
a single sweep end synchronization.
For details on synchronization see Remote control via SCPI.
Suffix: .
<n> irrelevant
Parameters:
<State> ON | OFF | 0 | 1
ON | 1
Continuous sweep
OFF | 0
Single sweep
*RST: 1 (some applications can differ)
Example: INIT:CONT OFF
Switches the sweep mode to single sweep.
INIT:CONT ON
Switches the sweep mode to continuous sweep.
Manual operation: See "Frequency Sweep" on page 131
See "Zero Span" on page 131
See "Continuous Sweep / Run Cont" on page 508
INITiate<n>[:IMMediate]
Starts a (single) new measurement.
With sweep count or average count > 0, this means a restart of the corresponding
number of measurements. With trace mode MAXHold, MINHold and AVERage, the
previous results are reset on restarting the measurement.
You can synchronize to the end of the measurement with *OPC, *OPC? or *WAI.
For details on synchronization see Remote control via SCPI.
Suffix: .
<n> irrelevant
Example: INIT:CONT OFF
Switches to single sweep mode.
DISP:WIND:TRAC:MODE AVER
Switches on trace averaging.
SWE:COUN 20
Sets the sweep counter to 20 sweeps.
INIT;*WAI
Starts the measurement and waits for the end of the 20 sweeps.
Usage: Asynchronous command
Manual operation: See "Frequency Sweep" on page 131
See "Zero Span" on page 131
See "Single Sweep / Run Single" on page 508
[SENSe:]SWEep:COUNt:CURRent?
This query returns the current number of started sweeps or measurements. This com-
mand is only available if a sweep count value is defined and the instrument is in single
sweep mode.
Return values:
<CurrentCount>
Example: SWE:COUNt 64
Sets sweep count to 64
INIT:CONT OFF
Switches to single sweep mode
INIT
Starts a sweep (without waiting for the sweep end!)
SWE:COUN:CURR?
Queries the number of started sweeps
Usage: Query only
CALCulate<n>:MARKer<m>:FUNCtion:POWer<sb>:MODE <Mode>
Selects the trace display mode for power measurements.
Suffix: .
<n> Window
<m> Marker
<sb> irrelevant
Parameters:
<Mode> WRITe | MAXHold
WRITe
The power is calculated from the current trace.
MAXHold
The power is calculated from the current trace and compared
with the previous power value using a maximum algorithm.
Manual operation: See "Power Mode" on page 172
CALCulate<n>:MARKer<m>:FUNCtion:POWer<sb>:RESult? <Measurement>
Queries the results of power measurements.
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 possible
for single sweep mode.
See also INITiate<n>:CONTinuous on page 912.
Suffix: .
<n> irrelevant
<m> irrelevant
<sb> Sub block in a Multi-standard radio measurement;
MSR ACLR: 1 to 8
Multi-SEM: 1 to 8
for all other measurements: irrelevant
Parameters:
<Measurement> ACPower | MCACpower
ACLR measurements (also known as adjacent channel power or
multicarrier adjacent channel measurements).
Returns the power for every active transmission and adjacent
channel. The order is:
• power of the transmission channels
• power of adjacent channel (lower,upper)
• power of alternate channels (lower,upper)
MSR ACLR results:
For MSR ACLR measurements, the order of the returned results
is slightly different:
• power of the transmission channels
• total power of the transmission channels for each sub block
• power of adjacent channels (lower, upper)
• power of alternate channels (lower, upper)
• power of gap channels (lower1, upper1, lower2, upper2)
The unit of the return values depends on the scaling of the y-
axis:
• logarithmic scaling returns the power in the current unit
• linear scaling returns the power in W
GACLr
For MSR ACLR measurements only: returns a list of ACLR val-
ues for each gap channel (lower1, upper1, lower2, upper2)
MACM
For MSR ACLR measurements only: returns a list of CACLR val-
ues for each gap channel (lower1, upper1, lower2, upper2)
CN
Carrier-to-noise measurements.
Returns the C/N ratio in dB.
CN0
Carrier-to-noise measurements.
Returns the C/N ratio referenced to a 1 Hz bandwidth in
dBm/Hz.
CPOWer
Channel power measurements.
Returns the channel power. The unit of the return values
depends on the scaling of the y-axis:
• logarithmic scaling returns the power in the current unit
• linear scaling returns the power in W
For SEM measurements, the return value is the channel power
of the reference range (in the specified sub block).
PPOWer
Peak power measurements.
Returns the peak power. The unit of the return values depends
on the scaling of the y-axis:
• logarithmic scaling returns the power in the current unit
• linear scaling returns the power in W
For SEM measurements, the return value is the peak power of
the reference range (in the specified sub block).
Note that this result is only available if the power reference type
is set to peak power (see [SENSe:]ESPectrum<sb>:RTYPe
on page 1022).
OBANdwidth | OBWidth
Occupied bandwidth.
Returns the occupied bandwidth in Hz.
COBandwidth | COBWidth
<Centroid frequency>,<Frequency offset>
See Section 6.4.2, "OBW results", on page 214
Manual operation: See "C/N" on page 210
See "C/N0" on page 211
CALCulate<n>:MARKer<m>:FUNCtion:POWer<sb>:SELect <MeasType>
Selects a power measurement and turns the measurement on.
Suffix: .
<n> Window
<m> Marker
<sb> irrelevant
Parameters:
<MeasType> ACPower | MCACpower
Adjacent channel leakage ratio (ACLR), also known as adjacent
channel power or multicarrier adjacent channel.
The FSW performs the measurement on the trace selected with
[SENSe:]POWer:TRACe.
CPOWer
Channel power measurement with a single carrier.
The FSW performs the measurement on the trace selected with
[SENSe:]POWer:TRACe.
OBANdwidth | OBWidth
Occupied bandwidth measurement.
The FSW performs the measurement on the trace that marker 1
is positioned on.
CN
Carrier-to-noise ratio measurement.
CN0
Carrier-to-noise ratio measurement referenced to 1 Hz band-
width
Manual operation: See "C/N" on page 210
See "C/N0" on page 211
CALCulate<n>:MARKer<m>:FUNCtion:POWer<sb>[:STATe] <State>
Turns a power measurement off. To switch on the power measurement again, use
CALCulate<n>:MARKer<m>:FUNCtion:POWer<sb>:SELect on page 916.
A standard frequency sweep is activated.
Suffix: .
<n> irrelevant
<m> irrelevant
<sb> irrelevant
Parameters:
<State> OFF
Manual operation: See "C/N" on page 210
See "C/N0" on page 211
[SENSe:]POWer:ACHannel:PRESet <Measurement>
Determines the ideal span, bandwidths and detector for the current power measure-
ment.
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 possible
for single sweep mode.
See also INITiate<n>:CONTinuous on page 912.
Parameters:
<Measurement> ACPower | MCACpower
ACLR measurement
CPOWer
channel power measurement
OBANdwidth | OBWidth
Occupied bandwidth measurement
CN
Carrier to noise ratio
CN0
Carrier to noise ration referenced to a 1 Hz bandwidth
Manual operation: See "Optimized Settings (Adjust Settings)" on page 172
See "Adjust Settings" on page 211
See "Adjust Settings" on page 216
[SENSe:]POWer:ACHannel:PRESet:RLEVel
This command determines the ideal reference level for the current measurement.
This automatic routine makes sure that the that the signal power level does not over-
load the FSW or limit the dynamic range by too small a S/N ratio.
To determine the best reference level, the FSW aborts current measurements and per-
forms a series of test sweeps. After it has finished the test, it continues with the actual
measurement.
To get a valid result, you have to perform a complete sweep with synchronization to the
sweep end. This is only possible in single sweep mode.
[SENSe:]POWer:TRACe <TraceNumber>
Selects the trace channel power measurements are performed on.
For the measurement to work, the corresponding trace has to be active.
Parameters:
<TraceNumber> Range: 1 to 6
*RST: 1
Example: POW:TRAC 2
Assigns the measurement to trace 2.
Manual operation: See "Selected Trace" on page 171
All remote control commands specific to channel power or ACLR measurements are
described here.
CALCulate<n>:MARKer<m>:FUNCtion:POWer<sb>:PRESet <Standard>
Loads a measurement configuration.
The measurement configuration for power measurements consists of weighting filter,
channel bandwidth and spacing, resolution and video bandwidth, detector and sweep
time.
If the "Multi-Standard Radio" standard is selected (see "Standard" on page 168), differ-
ent commands are required to configure ACLR measurements (see Section 13.5.3.8,
"Configuring MSR ACLR measurements", on page 941).
Suffix: .
<n> Window
<m> Marker
<sb> irrelevant
Parameters:
<Standard> For more information see Section 6.2.9, "Reference: predefined
CP/ACLR standards", on page 206.
If you want to load a customized configuration, the parameter is
a string containing the file name.
Manual operation: See "Predefined Standards" on page 168
See "User Standards" on page 168
CALCulate<n>:MARKer<m>:FUNCtion:POWer<sb>:STANdard:CATalog?
Queries all xml files containing ACLR standards in the
C:\Program Files (x86)\Rohde-Schwarz\FSW\<version>\acp_std direc-
tory. Note that subdirectories are not searched.
Suffix: .
<n> Window
<m> Marker
<sb> Sub block in a Multi-standard radio measurement;
MSR ACLR: 1 to 8
Multi-SEM: 1 to 8
for all other measurements: irrelevant
Return values:
<Standards> List of standard files.
Usage: Query only
Manual operation: See "User Standards" on page 168
CALCulate<n>:MARKer<m>:FUNCtion:POWer<sb>:STANdard:DELete
<Standard>
Deletes a file containing an ACLR standard.
Suffix: .
<n> Window
<m> Marker
<sb> irrelevant
Parameters:
<Standard> String containing the file name of the standard.
Manual operation: See "User Standards" on page 168
CALCulate<n>:MARKer<m>:FUNCtion:POWer<sb>:STANdard:SAVE <Standard>
Saves the current ACLR measurement configuration as a new ACLR standard.
The measurement configuration for power measurements consists of weighting filter,
channel bandwidth and spacing, resolution and video bandwidth, detector and sweep
time.
Suffix: .
<n> Window
<m> Marker
<sb> irrelevant
Parameters:
<Standard> String containing the file name. The file format is xml.
Manual operation: See "User Standards" on page 168
The following commands configure channels for channel power and ACLR measure-
ments.
[SENSe:]POWer:ACHannel:ACPairs................................................................................ 921
[SENSe:]POWer:ACHannel:BWIDth:ACHannel................................................................. 921
[SENSe:]POWer:ACHannel:BANDwidth:ACHannel............................................................921
[SENSe:]POWer:ACHannel:BWIDth:ALTernate<ch>.......................................................... 922
[SENSe:]POWer:ACHannel:BANDwidth:ALTernate<ch>.....................................................922
[SENSe:]POWer:ACHannel:BWIDth[:CHANnel<ch>]......................................................... 922
[SENSe:]POWer:ACHannel:BANDwidth[:CHANnel<ch>]....................................................922
[SENSe:]POWer:ACHannel:NAME:ACHannel...................................................................922
[SENSe:]POWer:ACHannel:NAME:ALTernate<ch>............................................................923
[SENSe:]POWer:ACHannel:NAME:CHANnel<ch>.............................................................923
[SENSe:]POWer:ACHannel:SPACing[:ACHannel]............................................................. 923
[SENSe:]POWer:ACHannel:SPACing:ALTernate<ch>........................................................ 924
[SENSe:]POWer:ACHannel:SPACing:CHANnel<ch>......................................................... 924
[SENSe:]POWer:ACHannel:TXCHannel:COUNt................................................................925
[SENSe:]POWer:ACHannel:ACPairs <ChannelPairs>
Defines the number of pairs of adjacent and alternate channels.
Parameters:
<ChannelPairs> Range: 0 to 12
*RST: 1
Manual operation: See "Number of channels: Tx, Adj" on page 169
See "Number of Adjacent Channels (Adj Count)" on page 187
[SENSe:]POWer:ACHannel:BWIDth:ACHannel <Bandwidth>
[SENSe:]POWer:ACHannel:BANDwidth:ACHannel <Bandwidth>
Defines the channel bandwidth of the adjacent channels.
The adjacent channels are the first channels to the left and right of the transmission
channels. If you set the channel bandwidth for these channels, the FSW sets the band-
width of the alternate channels to the same value (not for MSR signals).
For asymmetrical MSR signals, this command defines the bandwidth of the lower adja-
cent channel. To configure the bandwidth for the upper adjacent channel, use the
[SENSe:]POWer:ACHannel:BANDwidth:UACHannel command.
Steep-edged channel filters are available for fast ACLR measurements.
Parameters:
<Bandwidth> Range: 100 Hz to 1000 MHz
*RST: 14 kHz
Default unit: Hz
Manual operation: See "Channel Bandwidth" on page 174
See "Adjacent Channel Bandwidths" on page 187
[SENSe:]POWer:ACHannel:BWIDth:ALTernate<ch> <Bandwidth>
[SENSe:]POWer:ACHannel:BANDwidth:ALTernate<ch> <Bandwidth>
Defines the channel bandwidth of the alternate channels.
For MSR signals, this command defines the bandwidth of the lower alternate channels
in asymmetrical configurations. To configure the bandwidth for the upper alternate
channel, use the [SENSe:]POWer:ACHannel:BANDwidth:UALTernate<ch> com-
mand.
If you set the channel bandwidth for the first alternate channel, the FSW sets the band-
width of the other alternate channels to the same value, but not the other way round
(not for MSR signals). The command works hierarchically: to set a bandwidth of the 3rd
and 4th channel, you have to set the bandwidth of the 3rd channel first.
Steep-edged channel filters are available for fast ACLR measurements.
Suffix: .
<ch> 1..n
Alternate channel number
Parameters:
<Bandwidth> Range: 100 Hz to 1000 MHz
*RST: 14 kHz
Default unit: Hz
Manual operation: See "Channel Bandwidth" on page 174
See "Adjacent Channel Bandwidths" on page 187
[SENSe:]POWer:ACHannel:BWIDth[:CHANnel<ch>] <Bandwidth>
[SENSe:]POWer:ACHannel:BANDwidth[:CHANnel<ch>] <Bandwidth>
Defines the channel bandwidth of the transmission channels.
Steep-edged channel filters are available for fast ACLR measurements.
Suffix: .
<ch> 1..n
Tx channel number
Parameters:
<Bandwidth> Range: 100 Hz to 1000 MHz
*RST: 14 kHz
Default unit: Hz
Manual operation: See "Channel Bandwidth" on page 174
See "Channel Bandwidth" on page 211
See "Channel Bandwidth" on page 216
[SENSe:]POWer:ACHannel:NAME:ACHannel <Name>
Defines a name for the adjacent channel.
For MSR ACLR measurements, this command defines the name for the lower adjacent
channel in asymmetric channel definitions. To define the name for the upper adjacent
channel use the [SENSe:]POWer:ACHannel:NAME:UACHannel command.
Parameters:
<Name> String containing the name of the channel
*RST: ADJ
Manual operation: See "Channel Names" on page 177
[SENSe:]POWer:ACHannel:NAME:ALTernate<ch> <Name>
Defines a name for an alternate channel.
For MSR ACLR measurements, this command defines the name for the lower alternate
channel in asymmetric channel definitions. To define the name for the upper alternate
channels use the [SENSe:]POWer:ACHannel:NAME:UALTernate<ch> command.
Suffix: .
<ch> 1..n
Alternate channel number
Parameters:
<Name> String containing the name of the channel
*RST: ALT<1...11>
Manual operation: See "Channel Names" on page 177
[SENSe:]POWer:ACHannel:NAME:CHANnel<ch> <Name>
Defines a name for a transmission channel.
Suffix: .
<ch> 1..n
Tx channel number
Parameters:
<Name> String containing the name of the channel
*RST: TX<1...12>
Manual operation: See "Channel Names" on page 177
[SENSe:]POWer:ACHannel:SPACing[:ACHannel] <Spacing>
Defines the distance from transmission channel to adjacent channel.
For MSR signals, this command defines the distance from the CF of the first Tx chan-
nel in the first sub block to the lower adjacent channel. To configure the spacing for the
upper adjacent channel in asymmetrical configurations, use the [SENSe:]POWer:
ACHannel:SPACing:UACHannel command.
A change of the adjacent channel spacing causes a change in the spacing of all alter-
nate channels below the adjacent channel (not for MSR signals).
Parameters:
<Spacing> Range: 100 Hz to 2000 MHz
*RST: 14 kHz
Default unit: Hz
Manual operation: See "Channel Spacings" on page 174
See "Adjacent Channel Spacings" on page 187
[SENSe:]POWer:ACHannel:SPACing:ALTernate<ch> <Spacing>
Defines the distance from transmission channel to alternate channels.
For MSR signals, this command defines the distance from the CF of the first Tx chan-
nel in the first sub block to the lower alternate channel. To configure the spacing for the
upper alternate channel in asymmetrical configurations, use the [SENSe:]POWer:
ACHannel:SPACing:UALTernate<ch> command.
If you set the channel spacing for the first alternate channel, the FSW adjusts the spac-
ing of alternate channels of a lower order, but not the other way round (not for MSR
signals). The command works hierarchically: to set a distance from the transmission
channel to the 2nd and 3rd alternate channel, you have to define a spacing for the 2nd
alternate channel first.
Suffix: .
<ch> 1..n
Alternate channel number
Parameters:
<Spacing> Range: 100 Hz to 2000 MHz
*RST: 40 kHz (ALT1), 60 kHz (ALT2), 80 kHz (ALT3), ...
Default unit: Hz
Manual operation: See "Channel Spacings" on page 174
See "Adjacent Channel Spacings" on page 187
[SENSe:]POWer:ACHannel:SPACing:CHANnel<ch> <Spacing>
Defines the distance between transmission channels.
If you set the channel spacing for a transmission channel, the FSW sets the spacing of
the lower transmission channels to the same value, but not the other way round. The
command works hierarchically: to set a distance between the 2nd and 3rd and 3rd and
4th channel, you have to set the spacing between the 2nd and 3rd channel first.
Suffix: .
<ch> 1..n
Tx channel number
Parameters:
<Spacing> Range: 14 kHz to 2000 MHz
*RST: 20 kHz
Default unit: Hz
Manual operation: See "Channel Spacings" on page 174
[SENSe:]POWer:ACHannel:TXCHannel:COUNt <Number>
Defines the number of transmission channels.
The command works for measurements in the frequency domain.
Parameters:
<Number> Range: 1 to 18
*RST: 1
Manual operation: See "Number of channels: Tx, Adj" on page 169
[SENSe:]POWer:ACHannel:FILTer:ALPHa:ACHannel <Alpha>
Defines the roll-off factor for the adjacent channel weighting filter.
For asymmetrical MSR signals, this command defines the roll-off factor for the lower
adjacent channel. To configure the factor for the upper adjacent channel, use the
[SENSe:]POWer:ACHannel:FILTer:ALPHa:UACHannel command.
Parameters:
<Alpha> Roll-off factor
Range: 0 to 1
*RST: 0.22
Manual operation: See "Weighting Filters" on page 177
See "Weighting Filters" on page 188
[SENSe:]POWer:ACHannel:FILTer:ALPHa[:ALL] <Value>
Defines the alpha value for the weighting filter for all channels.
Parameters:
<Value> *RST: 0.22
Example: POW:ACH:FILT:ALPH:ALL 0.35
[SENSe:]POWer:ACHannel:FILTer:ALPHa:ALTernate<ch> <Alpha>
Defines the roll-off factor for the alternate channel weighting filter.
For asymmetrical MSR signals, this command defines the roll-off factor for the lower
alternate channels. To configure the factor for the upper alterante channels, use the
[SENSe:]POWer:ACHannel:FILTer:ALPHa:UALTernate<ch> command.
Suffix: .
<ch> 1..n
Alternate channel number
Parameters:
<Alpha> Roll-off factor
Range: 0 to 1
*RST: 0.22
Manual operation: See "Weighting Filters" on page 177
See "Weighting Filters" on page 188
[SENSe:]POWer:ACHannel:FILTer:ALPHa:CHANnel<ch> <Alpha>
Defines the roll-off factor for the transmission channel weighting filter.
Suffix: .
<ch> 1..n
Tx channel number
Parameters:
<Alpha> Roll-off factor
Range: 0 to 1
*RST: 0.22
Manual operation: See "Weighting Filters" on page 177
[SENSe:]POWer:ACHannel:FILTer[:STATe]:ACHannel <State>
Turns the weighting filter for the adjacent channel on and off.
For asymmetrical MSR signals, this command turns the weighting filter for the lower
adjacent channel on and off. To configure the filter state for the upper adjacent chan-
nel, use the [SENSe:]POWer:ACHannel:FILTer[:STATe]:UACHannel com-
mand.
Parameters:
<State> ON | OFF | 1 | 0
*RST: 0
Manual operation: See "Weighting Filters" on page 177
See "Weighting Filters" on page 188
[SENSe:]POWer:ACHannel:FILTer[:STATe][:ALL] <State>
Turns the weighting filters for all channels on and off.
Parameters:
<State> ON | OFF | 1 | 0
*RST: 0
[SENSe:]POWer:ACHannel:FILTer[:STATe]:ALTernate<ch> <State>
Turns the weighting filter for an alternate channel on and off.
For asymmetrical MSR signals, this command turns the weighting filter for the lower
alternate channels on and off. To configure the filter state for the upper alternate chan-
nels, use the [SENSe:]POWer:ACHannel:FILTer[:STATe]:UALTernate<ch>
command.
Suffix: .
<ch> 1..n
Alternate channel number
Parameters:
<State> ON | OFF | 1 | 0
*RST: 0
Manual operation: See "Weighting Filters" on page 177
See "Weighting Filters" on page 188
[SENSe:]POWer:ACHannel:FILTer[:STATe]:CHANnel<ch> <State>
Turns the weighting filter for a transmission channel on and off.
Suffix: .
<ch> 1..n
Tx channel number
Parameters:
<State> ON | OFF | 1 | 0
*RST: 0
Manual operation: See "Weighting Filters" on page 177
The following commands define the reference channel for relative ACLR measure-
ments.
[SENSe:]POWer:ACHannel:REFerence:AUTO ONCE....................................................... 927
[SENSe:]POWer:ACHannel:REFerence:TXCHannel:AUTO................................................ 928
[SENSe:]POWer:ACHannel:REFerence:TXCHannel:MANual............................................. 928
[SENSe:]POWer:ACHannel:REFerence:AUTO ONCE
This command sets the channel power as the reference for relative ACLR measure-
ments.
[SENSe:]POWer:ACHannel:REFerence:TXCHannel:AUTO <RefChannel>
Selects the reference channel for relative measurements.
You need at least one channel for the command to work.
Parameters:
<RefChannel> MINimum | MAXimum | LHIGhest
MINimum
Transmission channel with the lowest power
MAXimum
Transmission channel with the highest power
LHIGhest
Lowest transmission channel for lower adjacent channels and
highest transmission channel for upper adjacent channels
Example: POW:ACH:REF:TXCH:AUTO MAX
Selects the channel with the peak power as reference channel.
Manual operation: See "Reference Channel" on page 170
[SENSe:]POWer:ACHannel:REFerence:TXCHannel:MANual <ChannelNumber>
Defines a reference channel for relative ACLR measurements.
You need at least one channel for the command to work.
Note that this command is not available for MSR ACLR measurements (see
CALCulate<n>:MARKer<m>:FUNCtion:POWer<sb>:PRESet on page 919).
Parameters:
<ChannelNumber> Range: 1 to 18
*RST: 1
Manual operation: See "Reference Channel" on page 170
The following commands configure and query limit checks for channel power and
ACLR measurements.
The results of the power limit checks are also indicated in the STAT:QUES:ACPL sta-
tus registry (see Section 12.2.2.6, "STATus:QUEStionable:ACPLimit register",
on page 832).
CALCulate<n>:LIMit<li>:ACPower:ACHannel:ABSolute..................................................... 929
CALCulate<n>:LIMit<li>:ACPower:ACHannel:ABSolute:STATe........................................... 929
CALCulate<n>:LIMit<li>:ACPower:ACHannel[:RELative]....................................................930
CALCulate<n>:LIMit<li>:ACPower:ACHannel:RESult?.......................................................930
CALCulate<n>:LIMit<li>:ACPower:ACHannel[:RELative]:STATe..........................................931
CALCulate<n>:LIMit<li>:ACPower:ALTernate<ch>:ABSolute.............................................. 932
CALCulate<n>:LIMit<li>:ACPower:ALTernate<ch>:ABSolute:STATe.................................... 932
CALCulate<n>:LIMit<li>:ACPower:ALTernate<ch>[:RELative].............................................933
CALCulate<n>:LIMit<li>:ACPower:ALTernate<ch>:RESult?................................................933
CALCulate<n>:LIMit<li>:ACPower:ALTernate<ch>[:RELative]:STATe...................................934
CALCulate<n>:LIMit<li>:ACPower:PMODe.......................................................................934
CALCulate<n>:LIMit<li>:ACPower[:STATe]....................................................................... 935
CALCulate<n>:LIMit<li>:ACPower:ACHannel:ABSolute <LowerLimit>[,
<UpperLimit>]
Defines the absolute limit of the adjacent channels.
If you have defined an absolute limit as well as a relative limit, the FSW uses the lower
value for the limit check.
Suffix: .
<n> irrelevant
<li> irrelevant
Parameters:
<LowerLimit> The limit of the lower adjacent channel.
Range: -200 dBm to 200 dBm
*RST: -200 dBm
Default unit: dBm
<UpperLimit> The limit of the upper adjacent channel.
Range: -200 dBm to 200 dBm
*RST: -200 dBm
Default unit: dBm
Manual operation: See "Limit Check" on page 175
See "Limit Checking" on page 188
Parameters:
<State> ON | OFF | 1 | 0
Absolute limit check for lower adjacent channel
*RST: 0
<State> ON | OFF | 1 | 0
Absolute limit check for upper adjacent channel
*RST: 0
Manual operation: See "Limit Check" on page 175
See "Limit Checking" on page 188
CALCulate<n>:LIMit<li>:ACPower:ACHannel[:RELative] <LowerLimit>[,
<UpperLimit>]
Defines the relative limit of the adjacent channels. The reference value for the relative
limit is the measured channel power.
If you have defined an absolute limit as well as a relative limit, the FSW uses the lower
value for the limit check.
Suffix: .
<n> irrelevant
<li> irrelevant
Parameters:
<LowerLimit> The limit of the lower adjacent channel.
Range: 0 dB to 100 dB
*RST: 0 dB
Default unit: dB
<UpperLimit> The limit of the upper adjacent channel.
Range: 0 dB to 100 dB
*RST: 0 dB
Default unit: dB
Manual operation: See "Limit Check" on page 175
See "Limit Checking" on page 188
CALCulate<n>:LIMit<li>:ACPower:ACHannel:RESult?
Queries the state of the limit check for the adjacent channels in an ACLR measure-
ment.
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 possible
for single sweep mode.
See also INITiate<n>:CONTinuous on page 912.
Suffix: .
<n> irrelevant
<li> irrelevant
Return values:
<LowerACH> text value
Thestate of the limit check for the lower adjacent channels.
PASSED
Limit check has passed.
FAIL
Limit check has failed.
<UpperACH> text value
The state of the limit check for the upper adjacent channels.
PASSED
Limit check has passed.
FAIL
Limit check has failed.
Example: INIT:IMM;*WAI;
CALC:LIM:ACP:ACH:RES?
PASSED,PASSED
Usage: Query only
Manual operation: See "Limit Check" on page 175
See "Limit Checking" on page 188
CALCulate<n>:LIMit<li>:ACPower:ALTernate<ch>:ABSolute <LowerLimit>[,
<UpperLimit>]
Defines the absolute limit of the alternate channels.
If you have defined an absolute limit as well as a relative limit, the FSW uses the lower
value for the limit check.
Suffix: .
<n> irrelevant
<li> irrelevant
<ch> 1..n
Alternate channel number
Parameters:
<LowerLimit> The limit of the lower adjacent channel.
Range: -200 dBm to 200 dBm
*RST: -200 dBm
Default unit: dBm
<UpperLimit> The limit of the upper adjacent channel.
Range: -200 dBm to 200 dBm
*RST: -200 dBm
Default unit: dBm
Manual operation: See "Limit Check" on page 175
See "Limit Checking" on page 188
CALCulate<n>:LIMit<li>:ACPower:ALTernate<ch>:ABSolute:STATe <State>[,
<State>]
This command turns the absolute limit check for the alternate channels on and off.
You have to activate the general ACLR limit check before using this command with
CALCulate<n>:LIMit<li>:ACPower[:STATe].
Suffix: .
<n> irrelevant
<li> irrelevant
<ch> 1..n
Alternate channel number
Parameters:
<State> ON | OFF | 1 | 0
Absolute limit check for lower alternate channel
*RST: 0
<State> ON | OFF | 1 | 0
Absolute limit check for upper alternate channel
*RST: 0
CALCulate<n>:LIMit<li>:ACPower:ALTernate<ch>[:RELative] <LowerLimit>[,
<UpperLimit>]
Defines the relative limit of the alternate channels. The reference value for the relative
limit is the measured channel power.
If you have defined an absolute limit as well as a relative limit, the FSW uses the lower
value for the limit check.
Suffix: .
<n> irrelevant
<li> irrelevant
<ch> 1..n
Alternate channel number
Parameters:
<LowerLimit> The limit of the lower alternate channel.
Range: 0 dB to 100 dB
*RST: 0 dB
Default unit: dB
<UpperLimit> The limit of the upper alternate channel.
Range: 0 dB to 100 dB
*RST: 0 dB
Default unit: dB
Manual operation: See "Limit Check" on page 175
See "Limit Checking" on page 188
CALCulate<n>:LIMit<li>:ACPower:ALTernate<ch>:RESult?
Queries the state of the limit check for the adjacent or alternate channels in an ACLR
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 possible
for single sweep mode.
See also INITiate<n>:CONTinuous on page 912.
Suffix: .
<n> irrelevant
<li> irrelevant
<ch> Alternate channel number
Return values:
<LowerChan> text value
The state of the limit check for the lower alternate or adjacent
channels.
PASSED
Limit check has passed.
FAIL
Limit check has failed.
<UpperChan> text value
The state of the limit check for the upper alternate or adjacent
channels.
PASSED
Limit check has passed.
FAIL
Limit check has failed.
Example: INIT:IMM;*WAI;
CALC:LIM:ACP:ACH:RES?
PASSED,PASSED
Usage: Query only
CALCulate<n>:LIMit<li>:ACPower:ALTernate<ch>[:RELative]:STATe <State>[,
<State>]
This command turns the relative limit check for the alternate channels on and off.
You have to activate the general ACLR limit check before using this command with
CALCulate<n>:LIMit<li>:ACPower[:STATe].
Suffix: .
<n> irrelevant
<li> irrelevant
<ch> 1..n
Alternate channel number
Parameters:
<State> ON | OFF | 1 | 0
Relative limit check for lower alternate channel
*RST: 0
<State> ON | OFF | 1 | 0
Relative limit check for upper alternate channel
*RST: 0
Manual operation: See "Limit Check" on page 175
See "Limit Checking" on page 188
CALCulate<n>:LIMit<li>:ACPower:PMODe <Mode>
Selects the limit evaluation mode for ACLR measurements.
CALCulate<n>:LIMit<li>:ACPower[:STATe] <State>
Turns the limit check for ACLR measurements on and off.
In addition, limits must be defined and activated individually for each channel (see
CALCulate<n>:LIMit<li>:ACPower:ACHannel[:RELative]:STATe,
CALCulate<n>:LIMit<li>:ACPower:ALTernate<ch>[:RELative]:STATe,
CALCulate<n>:LIMit<li>:ACPower:GAP<gap>[:AUTO]:ABSolute:STATe,
CALCulate<n>:LIMit<li>:ACPower:GAP<gap>[:AUTO]:ACLR[:RELative]:
STATe and CALCulate<n>:LIMit<li>:ACPower:GAP<gap>[:AUTO][:
CACLr][:RELative]:STATe).
Suffix: .
<n> irrelevant
<li> irrelevant
Parameters:
<State> ON | OFF | 1 | 0
*RST: 0
Manual operation: See "Limit Check" on page 175
See "Limit Checking" on page 183
See "Limit Checking" on page 188
The following commands are only available in the ACLR measurements of the LTE and
5G applications.
Depending on the syntax, the commands return the limit check results for:
● adjacent channels
● alternate channels
● gap channels in multi carrier ACLR measurements (LTE and 5G downlink only)
● gap channels in cumulative ACLR measurement (LTE downlink and 5G downlink
only)
CALCulate<n>:LIMit<li>:ACPower:ACHannel:RESult:ABSolute.......................................... 936
CALCulate<n>:LIMit<li>:ACPower:ACHannel:RESult:RELative...........................................936
CALCulate<n>:LIMit<li>:ACPower:ALTernate<ch>:RESult:ABSolute................................... 937
CALCulate<n>:LIMit<li>:ACPower:ALTernate<ch>:RESult:RELative....................................937
CALCulate<n>:LIMit<li>:ACPower:GAP<gap>:ACLR:RESult:ABSolute?..............................938
CALCulate<n>:LIMit<li>:ACPower:GAP<gap>:ACLR:RESult:RELative?.............................. 938
CALCulate<n>:LIMit<li>:ACPower:GAP<gap>[:CACLr]:RESult:ABSolute?...........................939
CALCulate<n>:LIMit<li>:ACPower:GAP<gap>[:CACLr]:RESult:RELative?........................... 939
CALCulate<n>:LIMit<li>:ACPower:ACHannel:RESult:ABSolute
Queries the absolute limit check results for adjacent channels (ACLR measurements).
Prerequisites for this command
● Select absolute limit check mode
evaluation mode
ACLR: CALCulate<n>:LIMit<li>:ACPower:PMODe.
Suffix: .
<n> irrelevant
<li> irrelevant
Return values:
<LimitCheck> Returns two values, one for the upper and one for the lower
adjacent channel.
PASSED
Limit check has passed.
FAILED
Limit check has failed.
Example: //Query results of the adjacent channel limit check
CALC:LIM:ACP:ACH:RES:ABS?
CALCulate<n>:LIMit<li>:ACPower:ACHannel:RESult:RELative
Queries the relative limit check results for the adjacent channels (ACLR measure-
ments).
Prerequisites for this command
● Select relative limit check mode
ACLR: CALCulate<n>:LIMit<li>:ACPower:PMODe.
Suffix: .
<n> irrelevant
<li> irrelevant
Return values:
<LimitCheck> Returns two values, one for the upper and one for the lower
adjacent channel.
PASSED
Limit check has passed.
FAILED
Limit check has failed.
Example: //Query results of the adjacent channel limit check
CALC:LIM:ACP:ACH:RES:REL?
CALCulate<n>:LIMit<li>:ACPower:ALTernate<ch>:RESult:ABSolute
Queries the absolute limit check results for the alternate channels (MC ACLR mea-
surements).
Prerequisites for this command
● Select absolute limit check mode
ACLR: CALCulate<n>:LIMit<li>:ACPower:PMODe.
Suffix: .
<n> irrelevant
<li> irrelevant
<ch> irrelevant
Return values:
<LimitCheck> Returns two values, one for the upper and one for the lower
adjacent channel.
PASSED
Limit check has passed.
FAILED
Limit check has failed.
Example: //Query results of the alternate channel limit check
CALC:LIM:ACP:ALT:RES:ABS?
CALCulate<n>:LIMit<li>:ACPower:ALTernate<ch>:RESult:RELative
Queries the relative limit check results for the alternate channels (MC ACLR measure-
ments).
Prerequisites for this command
● Select relative limit check mode
ACLR: CALCulate<n>:LIMit<li>:ACPower:PMODe.
Suffix: .
<n> irrelevant
<li> irrelevant
<ch> irrelevant
Return values:
<LimitCheck> Returns two values, one for the upper and one for the lower
adjacent channel.
PASSED
Limit check has passed.
FAILED
Limit check has failed.
Example: //Query results of the alternate channel limit check
CALC:LIM:ACP:ALT:RES:REL?
CALCulate<n>:LIMit<li>:ACPower:GAP<gap>:ACLR:RESult:ABSolute?
Queries the absolute power limit check results for the gap channels (MC ACLR mea-
surements).
Prerequisites for this command
● Select absolute limit check mode
evaluation mode
ACLR: CALCulate<n>:LIMit<li>:ACPower:PMODe.
Suffix: .
<n> irrelevant
<li> irrelevant
<gap> irrelevant
Return values:
<LimitCheck> Returns two values, one for the upper and one for the lower
adjacent channel.
PASSED
Limit check has passed.
FAILED
Limit check has failed.
Example: //Query results of the gap channel limit check
CALC:LIM:ACP:GAP:ACLR:RES:ABS?
Usage: Query only
CALCulate<n>:LIMit<li>:ACPower:GAP<gap>:ACLR:RESult:RELative?
Queries the relative power limit check results for the gap channels (MC ACLR mea-
surements).
Prerequisites for this command
● Select relative limit check mode
evaluation mode
ACLR: CALCulate<n>:LIMit<li>:ACPower:PMODe.
Suffix: .
<n> irrelevant
<li> irrelevant
<gap> irrelevant
Return values:
<LimitCheck> Returns two values, one for the upper and one for the lower
adjacent channel.
PASSED
Limit check has passed.
FAILED
Limit check has failed.
Example: //Query results of the gap channel limit check
CALC:LIM:ACP:GAP:ACLR:RES:REL?
Usage: Query only
CALCulate<n>:LIMit<li>:ACPower:GAP<gap>[:CACLr]:RESult:ABSolute?
Queries the absolute limit check results for the gap channels (MC ACLR measure-
ments).
Prerequisites for this command
● Select absolute limit check mode
evaluation mode
ACLR: CALCulate<n>:LIMit<li>:ACPower:PMODe.
Suffix: .
<n> irrelevant
<li> irrelevant
<gap> irrelevant
Return values:
<LimitCheck> Returns two values, one for the upper and one for the lower
adjacent channel.
PASSED
Limit check has passed.
FAILED
Limit check has failed.
Example: //Query results of the gap channel limit check
CALC:LIM:ACP:GAP:RES:ABS?
Usage: Query only
CALCulate<n>:LIMit<li>:ACPower:GAP<gap>[:CACLr]:RESult:RELative?
Queries the relative limit check results for the gap channels (MC ACLR measure-
ments).
[SENSe:]POWer:HSPeed <State>
Turns high speed ACLR and channel power measurements on and off.
If on, the FSW performs a measurement on each channel in the time domain. It returns
to the frequency domain when the measurement is done.
In some telecommunications standards, high speed measurements use weighting fil-
ters with characteristic or steep-edged channel filters for band limitation.