FSWP UserManual en 12
FSWP UserManual en 12
FSWP UserManual en 12
(;ÛÆQ2)
1177563302
Version 12
This manual describes the following R&S®FSWP models with firmware version 1.92 or higher:
● R&S®FSWP8 (1322.8003K08)
● R&S®FSWP26 (1322.8003K26)
● R&S®FSWP50 (1322.8003K50)
Throughout this manual, products from Rohde & Schwarz are indicated without the ® symbol , e.g. R&S®FSWP is indicated as
R&S FSWP.
R&S®FSWP Contents
Contents
1 Preface.................................................................................................. 15
1.1 Key Features................................................................................................................15
1.2 Conventions Used in the Documentation.................................................................15
1.2.1 Typographical Conventions...........................................................................................15
1.2.2 Conventions for Procedure Descriptions.......................................................................16
1.2.3 Notes on Screenshots...................................................................................................16
2 Safety Information................................................................................17
3 Documentation Overview.................................................................... 18
3.1 Getting Started Manual...............................................................................................18
3.2 User Manuals and Help...............................................................................................18
3.3 Service Manual............................................................................................................ 18
3.4 Instrument Security Procedures................................................................................19
3.5 Basic Safety Instructions........................................................................................... 19
3.6 Data Sheets and Brochures....................................................................................... 19
3.7 Release Notes and Open Source Acknowledgment (OSA)..................................... 19
3.8 Application Notes, Application Cards, White Papers, etc....................................... 19
5 Instrument Tour....................................................................................34
5.1 The Front Panel........................................................................................................... 34
5.1.1 Display (Touchscreen)...................................................................................................35
5.1.2 Power Key.....................................................................................................................37
5.1.3 System Control Keys.....................................................................................................37
5.1.4 The Function Keys........................................................................................................ 38
5.1.5 The Keypad...................................................................................................................39
5.1.6 Navigation Control.........................................................................................................40
5.1.7 RF Input (50 Ω)............................................................................................................. 41
5.1.8 Signal Source Output.................................................................................................... 42
5.1.9 USB Ports..................................................................................................................... 42
5.1.10 Power Sensors..............................................................................................................42
5.1.11 Probe Power Connector (3 Pins).................................................................................. 42
5.1.12 Noise Source Control.................................................................................................... 43
5.1.13 Trigger Input and Output............................................................................................... 43
5.1.14 Baseband Input............................................................................................................. 43
5.1.15 External Mixer (Optional).............................................................................................. 43
5.1.16 DC Power Supply..........................................................................................................44
5.1.17 LO AUX Input (Optional)............................................................................................... 44
5.2 The Rear Panel............................................................................................................ 44
5.2.1 Removable Hard Disk................................................................................................... 46
5.2.2 AC Power Connector and Main Power Switch..............................................................46
5.2.3 DisplayPort and DVI......................................................................................................46
5.2.4 LAN Connector..............................................................................................................46
5.2.5 USB Ports..................................................................................................................... 46
5.2.6 IF / Video / Demod Output.............................................................................................47
5.2.7 IF Wide Out................................................................................................................... 47
5.2.8 Sync Trigger Input and Output...................................................................................... 47
5.2.9 AUX Port....................................................................................................................... 47
5.2.10 GPIB Interface...............................................................................................................48
8 Applications..........................................................................................98
8.1 R&S MultiView............................................................................................................. 98
8.2 Available Applications................................................................................................ 99
8.3 Starting an Application.............................................................................................101
8.4 Running a Sequence of Measurements.................................................................. 103
8.4.1 The Sequencer Concept............................................................................................. 103
8.4.2 Sequencer Settings.....................................................................................................105
8.4.3 How to Set Up the Sequencer.....................................................................................105
16 Maintenance....................................................................................... 628
16.1 Cleaning..................................................................................................................... 628
17 Troubleshooting................................................................................. 630
17.1 Error Information.......................................................................................................630
17.2 Error Messages in Remote Control Mode...............................................................631
17.3 Troubleshooting Remote Operation........................................................................632
17.4 Miscellaneous Troubleshooting Hints.................................................................... 634
17.5 System Recovery...................................................................................................... 635
17.6 Collecting Information for Support..........................................................................635
Index....................................................................................................651
1 Preface
This chapter provides safety-related information, key features of the instrument, and
the conventions used in the documentation.
Convention Description
"Graphical user interface ele- All names of graphical user interface elements on the screen, such as
ments" dialog boxes, menus, options, buttons, and softkeys are enclosed by
quotation marks.
Filenames, commands, Filenames, commands, coding samples and screen output are distin-
program code guished by their font.
Links Links that you can click are displayed in blue font.
When operating the instrument, several alternative methods may be available to per-
form the same task. In this case, the procedure using the touchscreen is described.
Any elements that can be activated by touching can also be clicked using an addition-
ally connected mouse. The alternative procedure using the keys on the instrument or
the on-screen keyboard is only described if it deviates from the standard operating pro-
cedures.
The term "select" may refer to any of the described methods, i.e. using a finger on the
touchscreen, a mouse pointer in the display, or a key on the instrument or on a key-
board.
When describing the functions of the product, we use sample screenshots. These
screenshots are meant to illustrate as many as possible of the provided functions and
possible interdependencies between parameters. The shown values may not represent
realistic usage scenarios.
The screenshots usually show a fully equipped product, that is: with all options instal-
led. Thus, some functions shown in the screenshots may not be available in your par-
ticular product configuration.
2 Safety Information
The product documentation helps you use the R&S FSWP safely and efficiently. Follow
the instructions provided here and in the printed "Basic Safety Instructions". Keep the
product documentation nearby and offer it to other users.
Intended use
The R&S FSWP is intended for the development, production and verification of elec-
tronic components and devices in industrial, administrative, and laboratory environ-
ments. Use the R&S FSWP only for its designated purpose. Observe the operating
conditions and performance limits stated in the data sheet.
3 Documentation Overview
This section provides an overview of the R&S FSWP user documentation. Unless
specified otherwise, you find most of the documents on the R&S FSWP product page
at:
www.rohde-schwarz.com/manual/fswp
https://gloris.rohde-schwarz.com
Check the equipment for completeness using the delivery note and the accessory lists
for the various items. Check the instrument for any damage. If there is damage, imme-
diately contact the carrier who delivered the instrument. Make sure not to discard the
box and packing material.
Packing material
Retain the original packing material. If the instrument needs to be transported or ship-
ped later, you can use the material to protect the control elements and connectors.
The R&S FSWP is designed for use under laboratory conditions, either on a bench top
or in a rack.
Rackmounting
The R&S FSWP can be installed in a rack using a rack adapter kit (order no. see data
sheet). The installation instructions are part of the adapter kit.
In the standard version, the R&S FSWP is equipped with an AC power supply connec-
tor. The R&S FSWP can be used with different AC power voltages and adapts itself
automatically to it. Refer to the datasheet for the requirements of voltage and fre-
quency. The AC power connector is located on the rear panel of the instrument.
For details on the connector refer to Chapter 5.2.2, "AC Power Connector and Main
Power Switch", on page 46.
► Connect the R&S FSWP to the AC power supply using the supplied power cable.
Since the instrument is assembled in line with the specifications for safety class
EN61010, it may only be connected to an outlet that has a ground contact.
2. Set the AC power switch on the rear panel to position "O", or disconnect the instru-
ment from the AC power supply.
The R&S FSWP changes into off mode.
During instrument start, the installed hardware is checked against the current firmware
version to ensure the hardware is supported. If not, an error message is displayed
("WRONG_FW") and you are asked to update the firmware. Until the firmware version
is updated, self-alignment fails.
(For details refer to the R&S FSWP User Manual).
Operating temperature
Before performing this functional test, make sure that the instrument has reached its
operating temperature (for details, refer to the data sheet).
A message in the status bar ("Instrument warming up...") indicates that the operating
temperature has not yet been reached.
Performing a self-alignment
1. Press the [SETUP] key.
Performing a selftest
The selftest does not need to be repeated every time the instrument is switched on. It
is only necessary when instrument malfunction is suspected.
1. Press the [SETUP] key.
The instrument may be equipped with both hardware and firmware options. In order to
check whether the installed options correspond to the options indicated on the delivery
note, proceed as follows.
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.
Tested software
The drivers and programs used on the instrument under Microsoft Windows are adap-
ted 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.
Firewall settings
A firewall protects an instrument by preventing unauthorized users from gaining access
to it through a network. Rohde & Schwarz highly recommends the use of the firewall on
your instrument. Rohde & Schwarz instruments are shipped with the Windows firewall
enabled and preconfigured in such a way that 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 the "Network and Remote Control" chapter of the
R&S FSWP user manual.
All necessary system settings can be defined in the "Start > Settings" menu.
For required settings, refer to the Microsoft Windows documentation and to the hard-
ware description.
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 R&S FSWP:
● German
● Swiss
● French
● Russian
2. Select "Start > Settings > Time & language > Region & language > Add a lan-
guage" .
When printing a file, the instrument checks whether a printer is connected and turned
on and whether the appropriate printer driver is installed. If necessary, printer driver
installation is initiated. You only have to install a printer driver once.
You can load updated and improved driver versions or new drivers from an installation
disk, USB memory stick or another external storage medium. If the instrument is inte-
grated in a network, you can also install driver data stored in a network directory.
7. Tap "Apply" to try out the settings before they are accepted permanently, then you
can easily return to the previous settings, if necessary.
● Exchanging hardware
Errors can affect the entire network.
Connect the R&S FSWP to the LAN via the LAN interface on the rear panel of the
instrument.
Windows automatically detects the network connection and activates the required
drivers.
By default, the R&S FSWP is configured to use DHCP and no static IP address is
configured.
For more information on LAN configuration, see the R&S FSWP user manual.
4. Press the "Set Date and Time" button to open the standard Windows "Date and
Time Properties" dialog box.
5. If necessary, toggle the "Date and Time Format" between German (DE) and US.
After you have made a change and closed the dialog box, the new date and time is
also adopted by the instrument.
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 R&S FSWP.
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.
ged on to the R&S FSWP automatically using the auto-login function. While the secure
user mode is active, a message is displayed in the status bar at the bottom of the
screen.
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 Microsoft Windows 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 302).
Remote control
Initially after installation of the R&S FSWP-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.
5 Instrument Tour
On the instrument tour, you can learn about the different control elements and connec-
tors on the front and back panel of the R&S FSWP.
● The Front Panel...................................................................................................... 34
● The Rear Panel.......................................................................................................44
17
16
1 15
2 3 4 5 6 7 8 9 10 11 12 13 14
1 = Display (touchscreen)
2 = Power key
3 = System control keys
4 = USB 2.0 interfaces
5 = Power sensor connector
6 = Probe power connector
7 = DC power connectors
8 = Baseband connectors
9 = Signal source output (optional)
10 = External LO input (optional)
11 = External mixer ports (optional)
12 = Noise source control
13 = RF input
14 = Trigger in- and output
15 = Keypad
16 = Navigation control
17 = Function keys
● Display (Touchscreen).............................................................................................35
● Power Key...............................................................................................................37
● System Control Keys...............................................................................................37
● The Function Keys.................................................................................................. 38
● The Keypad.............................................................................................................39
● Navigation Control...................................................................................................40
● RF Input (50 Ω)....................................................................................................... 41
● Signal Source Output..............................................................................................42
● USB Ports............................................................................................................... 42
● Power Sensors........................................................................................................42
● Probe Power Connector (3 Pins)............................................................................ 42
● Noise Source Control.............................................................................................. 43
● Trigger Input and Output......................................................................................... 43
● Baseband Input.......................................................................................................43
● External Mixer (Optional)........................................................................................ 43
● DC Power Supply....................................................................................................44
● LO AUX Input (Optional)......................................................................................... 44
The touchscreen on the front panel of the R&S FSWP displays the measurement
results. Additionally, the screen display provides status and setting information and
allows you to switch between various measurement tasks. The screen is touch-sensi-
tive, offering an alternative means of user interaction for quick and easy handling of the
instrument.
1 2 3 4 5 6 7 8 9
ple. Any user interface elements that can be clicked on by a mouse pointer can also be
tapped on the screen to trigger the same behavior, and vice versa.
Using the touchscreen, the following tasks (among others) can be performed by the tap
of your finger:
● Changing a setting
● Changing the display
● Moving a marker
● Zooming into a diagram
● Selecting a new evaluation method
● Scrolling through a result list
● 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.
The Power key on the front panel turns the instrument on and off.
The color of the LED above the key shows its current state.
● Orange: instrument is in stand-by mode.
● Green: instrument is running.
For more information see Chapter 4.1.5, "Switching the Instrument On and Off",
on page 24.
Selects a window in split screen mode or browses through active windows in full
screen mode.
Function keys provide access to the most common measurement settings and func-
tions.
Refer to the user manual for an extensive description of the measurement settings and
functions.
Provides functionality to automatically define various parameters like the level or fre-
quency.
Provides functionality to configure data acquisition and analyze measured data, for
example:
● the trace mode
● the displayed result
n/a
Provides functionality to activate and position absolute and relative markers (markers
and delta markers).
n/a
The alphanumeric keys allow you to enter alphanumeric characters where necessary
(for example in dialog boxes or input fields). The keypad containing the alphanumeric
keys also provides keys that select a particular unit.
...
Changes the sign of a numeric value or inserts a dash character ("-") in case of
alphanumeric input.
Select a particular unit for a numeric value. The labels on and next to the key state
the units it selects.
Pressing one of the unit keys also completes the entry of a numeric value. Note that
... in case of level entries (dB, dBm etc.) or dimensionless values, all unit keys have the
value "1" as multiplying factor and thus work like the [ENTER] key..
Deletes the character to the left of the cursor (if an (alpha)numeric entry has been
started already.
Navigation control consists of a rotary knob and cursor keys. These keys allow you to
navigate within the display or within dialog boxes.
In addition to the rotary knob and the cursor keys, the navigation control also provides
undo / redo functionality.
Rotary knob
The rotary knob allows you to do several things:
● It increases or decreases any kind of numeric value. In most cases, the rotary knob
changes numeric values with a fixed step size.
Turning it to the right corresponds to an increase, turning it to the left to a decrease
of a numeric value.
● It works like a cursor key in dialog boxes or lists (for example dropdown menus). In
that case you can navigate to one of the items with the rotary knob. If the dialog
box covers more than one screen page, it also scrolls through the dialog box.
Turning it to the right corresponds to a downward movement. Moving it to the left to
an upward movement.
● It moves around markers and other graphical elements on the screen. In most
cases, the step size is fix.
● Pressing the rotary knob has the same effect as pressing the [ENTER] key as it
confirms an entry or selection.
Cursor keys
The cursor keys allow you to do several things:
● The up and down keys increase or decrease any kind of numeric value if an input
field is active.
The cursor keys change numeric values with a fixed step size.
● The cursor keys navigate through dialog boxes or lists (for example dropdown
menus).
● The left and right keys move the cursor in an input field in the corresponding direc-
tion.
● The up and down keys move markers around.
The step size is fix.
● The cursor keys allow you to navigate to a cell in a table.
● The cursor keys move a scroll bar (vertical or horizontal) in dialog boxes that have
one.
Reverts the software to an older state by erasing the last change you have applied.
The undo function is useful, for example, if you are performing a measurement with
several markers and a limit line and accidentally select a different measurement. In
this case, a lot of settings would be lost. However, if you press [UNDO] immediately
afterwards, the previous status is retrieved.
The [UNDO] function is not available after a [PRESET] or "RECALL" operation. When
these functions are used, the history of previous actions is deleted.
The RF Input allows you to connect a device under test (or DUT) to the R&S FSWP,
usually via cable and an appropriate connector (for example a male N connector).
The supported frequency range depends on the R&S FSWP model you have. Refer to
the datasheet for details.
The RF Input also serves as an attenuator in case you are measuring signal with high
levels. The supported attenuation range depends on the R&S FSWP model you have.
Refer to the datasheet for details..
The optional "Signal Source" output allows you to generate a signal that can be fed
into the DUT or other external accessories like frequency dividers or amplifiers. You
can connect the DUT or accessories with a cable that has a male N connector.
The three USB ports on the front panel (type A) allow you to connect devices like key-
boards, mouses or memory sticks.
The R&S FSWP provides additional USB ports (including one type B port) on the rear
panel.
All USB ports support standard 2.0.
The female Lemosa connector allows you to connect power sensors of the R&S NRP-
Zxy family to the R&S FSWP.
For an extensive list of supported power sensors, refer to the data sheet.
For details on configuring and using power sensors, see the User Manual.
The Probe Power connector allows you to supply external equipment with power (for
example probes or transducers).
The three-pinned probe power connector supports supply voltages from +15 V to
-12.6 V and ground. The maximum permissible current is 150 mA. This probe power
connector is suitable, for example, for high-impedance probes.
The female BNC connector labeled "Noise Source" allows you to connect and control
an external noise source, and supplies the required supply voltage.
You can use a noise source, for example, to measure the noise figure and gain of
amplifiers and frequency converting devices.
Conventional noise sources require a voltage of +28 V in order to be switched on and
0 V to be switched off. The output supports a maximum load of 100 mA.
The female BNC connector labeled "Trigger Input / Output" allows you to receive an
external trigger signal or send a trigger signal to another device.
When you are using the connector as a trigger input, you can apply voltages in the
range from 0.5 V to 3.5 V (the default value is 1.4 V). The typical input impedance is
10 kΩ.
When you are using the connector as a trigger output, the TTL compatible signal is
transmitted (0 V / 5 V).
Note that you can find another connector for trigger input and output on the rear panel.
For more information about controlling and configuring trigger input and output, refer to
the User Manual.
The two connectors labeled "Baseband Input 50 Ω" are two female BNC connectors
that you can use to connect a DUT for Baseband Noise measurements.
When you perform measurements with two external mixers, the "Ch2" connector is the
IF input for the second mixer. This function is available with the optional external mixer
support.
The two (optional) SMA connectors (LO OUT/IF IN and IF IN) allow you to connect
external mixers.
External mixers increase the available frequency range. The way to connect an exter-
nal mixer depends on the type of mixer and the test setup. For more information about
connecting and controlling external mixers refer to the user manual.
If not in use, it is recommended to cover the SMA connectors with the provided protec-
tive caps.
The female BNC connectors labeled "VTune", "VAux" and "VSupply" allow you to supply
external devices, for example a DUT or an external reference oscillator, with the
required voltage.
The VSupply connector provides supply voltage from 0 V to +16 V, for example to pro-
vide voltage for an oscillator. The supported maximum current is 2000 mA.
The VTune connector provides tuning voltage from ‑10 V to +28 V. The supported maxi-
mum current is 20 mA.
The VAux connector provides DC voltage from ‑10 V to +10 V. The supported maximum
current is 100 mA.
For more information about configuring the DC Power supply, refer to the User Manual.
The two optional connectors labeled "LO AUX Input - Ch1" and "LO AUX Input - Ch2"
are two female SMA connectors that you can use to connect an external local oscillator
(LO). The external LO requires two connectors ("Ch1" and "Ch2") to work properly.
The "LO AUX Input" connectors are part of the optional Signal Source.
3 1 4 5 2
6 7 8 9 10
11
For information about the trigger in- and output available on the rear panel, see Chap-
ter 5.1.13, "Trigger Input and Output", on page 43.
The digital baseband in- and outputs shown in the image above are not supported by
the R&S FSWP.
● Removable Hard Disk............................................................................................. 46
● AC Power Connector and Main Power Switch........................................................46
● DisplayPort and DVI................................................................................................46
● LAN Connector........................................................................................................46
● USB Ports............................................................................................................... 46
● IF / Video / Demod Output...................................................................................... 47
● IF Wide Out............................................................................................................. 47
● Sync Trigger Input and Output................................................................................ 47
● AUX Port................................................................................................................. 47
● GPIB Interface.........................................................................................................48
● External Generator Control (Optional).................................................................... 48
● OCXO (Optional).....................................................................................................48
● REF INPUT / REF OUTPUT................................................................................... 49
The removable hard disk is accessible from the rear of the instrument.
In addition to the operating system and the firmware, the R&S FSWP also stores mea-
surement data on that disk. When you remove the hard disk, you can store it and the
data on it somewhere secure.
The AC power supply and main power switch are located in a unit on the rear panel of
the instrument.
The main power switch has the following states.
● Position "1": The instrument is supplied with power.
● Position "0": The instrument is disconnected from the power supply.
For details refer to Chapter 4.1.5, "Switching the Instrument On and Off", on page 24.
You can connect an external monitor or other display device to the R&S FSWP.
Another display device allows you to view the user interface on a bigger screen. Two
different types of connectors are provided for this purpose:
● DisplayPort
● DVI (Digital Visual Interface)
For details see Chapter 4.4, "Connecting an External Monitor", on page 29.
The LAN interface allows you to connect the R&S FSWP to a local network for remote
control, printouts or data transfer. The assignment of the RJ-45 connector supports
twisted-pair category 5 UTP/STP cables in a star configuration (UTP stands for
unshielded twisted pair, and STP for shielded twisted pair).
For details see Chapter 14, "Network and Remote Operation", on page 311.
The four USB ports on the rear panel (type A) allow you to connect devices like key-
boards, mouses or memory sticks.
The male USB connector (type B) allows you to connect the R&S FSWP to a computer
and establish a remote control connection, for example.
All USB connectors support standard 2.0.
The two female BNC connectors can be used for various outputs:
● Output of the intermediate frequency (IF)
● Output of the video signal
Details about configuring the output type and characteristics are part of the user man-
ual.
Note that you can use this connector for applications available with the optional spec-
trum analyzer hardware and analog modulation analysis application.
You can extend the signal analysis bandwidth of the R&S FSWP by installing a hard-
ware option. The bandwidth extension allows for a linear bandwidth up to 320 MHz.
You can activate and deactivate the bandwidth extension manually in the I/Q analyzer
that is integral part of the optional spectrum analyzer (R&S FSWP-B1) or other optional
applications that require the spectrum analyzer hardware.
Together with the bandwidth extension an additional IF output connector is provided (if
wide output). As opposed to the default IF / Video / Demod Output connector, the IF
output frequency of the optional connector cannot be defined manually, but is deter-
mined automatically depending on the center frequency. For details on the used fre-
quencies, see the data sheet. The IF Wide Output connector is used automatically
when the bandwidth extension is activated (i.e. for bandwidths > 80 MHz).
The "Sync Trigger Input / Output" connectors allow you to synchronize several devices
(for example two R&S FSWPs) with respect to the trigger signal, but also the reference
frequency. A 100 MHz signal can be output as a trigger or reference signal to another
device, and an external trigger or reference signal can be received at the input connec-
tor by the R&S FSWP.
The 9 pole SUB-D male connector provides control signals for controlling external devi-
ces. The voltage levels are TTL compatible (max. 5 V).
8 GND Ground
Short-circuit hazard
Always observe the designated pin assignment. A short-circuit can damage the port.
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 "Setting Up Remote Control" in the User
Manual.
The optional "External Generator Control" provides an additional GPIB interface and
AUX port.
The GPIB connector can be used to connect an external generator to the R&S FSWP.
The AUX port is required for TTL synchronization, if supported by the generator (see
Chapter 5.2.9, "AUX Port", on page 47).
For details on connecting an external generator see the "External Generator Control"
section of the R&S FSWP User Manual.
This optional OCXO generates a 10 MHz reference signal with a very precise fre-
quency. 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.
The REF INPUT connectors are used to provide an external reference signal to the
R&S FSWP.
The REF OUTPUT connectors can be used to provide an external reference signal (or
the optional OCXO reference signal) from the R&S FSWP to other devices that are
connected to this instrument.
Various connectors are provided for different reference signals:
REF OUTPUT 1...20 MHz To provide the same external reference signal received
by the REF INPUT 1...20 MHz connector to another
0...10 dBm
device, when available.
REF OUTPUT 10 MHz To provide the internal reference signal from the
R&S FSWP to another device continuously.
10 dBm
Also used to provide OCXO reference signal to another
device.
REF OUTPUT 100 MHz To provide a 100 MHz reference signal from the
R&S FSWP to another device.
6 dBm
REF OUTPUT 640 MHz To provide a 640 MHz reference signal from the
R&S FSWP to another device.
16 dBm
SYNC TRIGGER
The SYNC TRIGGER connector can also be used to synchronize the reference fre-
quency on several devices.
2. Turn on the R&S FSWP as described in Chapter 4.1.5, "Switching the Instrument
On and Off", on page 24.
Performing a preset
Before configuring and starting a new measurement, it is always recommended to per-
form a preset and restore the default configuration of the instrument or the measure-
ment application.
1. Select the [PRESET] key on the front panel to restore the default state of the
R&S FSWP.
2. Enter the "Overview" dialog box and select the "Preset Channel" item to restore the
default state of the selected measurement channel. All other measurement chan-
nels keep their custom configuration.
6.2 Measurements
Measuring the phase noise characteristics of a DUT requires a simple measurement
setup consisting of the R&S FSWP and a DUT.
Some measurements require additional equipment.
● For additive noise measurements, the R&S FSWP must be equipped with the
optional Signal Source hardware.
● For pulsed noise measurements, the R&S FSWP must be equipped with the
optional Pulsed Phase Noise Measurement application.
● For pulsed additive noise measurements, the R&S FSWP must be equipped with
the optional Pulsed Phase Noise Measurement application and the optional Signal
Source hardware.
● Measurement Selection.......................................................................................... 53
● The Phase Noise Measurement..............................................................................53
● The Additive Noise Measurement........................................................................... 56
● The Baseband Noise Measurement........................................................................58
● The Pulsed Phase Noise Measurement..................................................................60
● The Pulsed Additive Noise Measurement............................................................... 60
● Adding Another Measurement Channel.................................................................. 62
Selecting a measurement
► Select the [MEAS] key.
The R&S FSWP opens a dialog box to select the measurement.
Test setup
Connect the DUT via cable to the RF input of the R&S FSWP as shown in the illustra-
tion.
required connections
R&S FSWP
optional connections
Vsupply
Vtune
Vaux
DUT RF
2. You can stop the measurement (to analyze the measurement data in detail) with
the [RUN SGL] or [RUN CONT] key; [RUN SGL] performs one more measurement,
then stops, [RUN CONT] stops immediately.
By default, two traces are displayed: the first trace shows the smoothed data with-
out spurs, the second trace the raw data including spurs.
2. Select the vertical "Trace" tab, and then the horizontal "Traces" tab.
3. For any trace, select "AM Noise" from the "Result" dropdown menu.
In addition to the graphical representation of the phase noise characteristics, the appli-
cation also provides several tables that show specific phase noise characteristics.
Measuring spurs
In addition to the graphical display of spurs in the diagram (spikes on the trace), the
application also features a result display that contains a list of all detected spurs.
► Open the SmartGrid ( ) and drag the "Spurious List" item from the evaluation bar
into the display.
The spurious list contains all detected spurs (including their characteristics) on all
traces and all windows.
More information:
● Spurious list
● Spur removal
The table contains a list of spot noise values for selected frequency offsets (in the
default state, these are the decade edges) on each active trace.
More information:
● Spot noise table
Tip: You can define custom spot noise frequencies in the "Spot Noise" tab of the
"Noise Config" dialog box.
1. Perform a [PRESET].
2. Select the [MEAS] key and select the "Phase Noise" measurement.
3. Enter the "Overview" dialog box, and from there, enter the "Input" dialog box.
4. Configure both mixers in the "External Mixer" tab of the "Input Source" dialog box.
More information:
● External mixer
Additive noise measurements require the signal source output that is available as an
optional hardware component.
Test setup
Connect the DUT via cable to the RF input and the signal source output of the
R&S FSWP as shown in the illustration.
required connections
R&S FSWP
optional connections
Signal
Source
Vsupply
Vaux
DUT RF
5. You can stop the measurement (to analyze the measurement data in detail) with
the [RUN SGL] or [RUN CONT] key; [RUN SGL] performs one more measurement,
then stops, [RUN CONT] stops immediately.
By default, two traces are displayed: the first trace shows the smoothed data with-
out spurs, the second trace the raw data including spurs.
required connections
R&S FSWP
optional connections
LO Aux Ch1
Splitter
LO Aux Ch1
Ext.
Splitter
Source
Amplifier RF
a) Configure the external signal source to generate the required fixed frequency.
b) Connect the first power splitter to the amplifier and the second power splitter.
c) Connect the amplifier to the RF input of the R&S FSWP.
d) Connect the second power splitter to both LO AUX input channels of the
R&S FSWP.
The power at each LO AUX input must have a level between 5 dBm and
10 dBm.
Except for the second power splitter, do not add any additional hardware to this
signal path.
e) If required, you can add an attenuator between the first splitter and the ampli-
fier to reduce the amplifier input level.
f) Select "Overview" > "Select Measurement" > "Additive Noise"
g) Select "Overview" > "Input" > "Input Source" > "Radio Frequency" > "Local
Oscillator" > "External"
h) Start the measurement ([RUN SINGLE] or [RUN CONT].
LO Aux Ch1
Divider Splitter
LO Aux Ch1
Ext.
Splitter
Source
Divider RF
a) Configure the external signal source to generate the required fixed frequency.
b) Connect both frequency dividers to the first power splitter.
c) Connect the first frequency divider to the RF input of the R&S FSWP.
d) Connect the second power splitter to the other frequency divider and connect
the resulting signal streams to both LO AUX input channels of the R&S FSWP.
Regarding the frequency divider, make sure that both dividers are the same
model and have the same dividing factor.
Also make sure that the frequency fed into all inputs of the R&S FSWP is the
same.
e) Select "Overview" > "Select Measurement" > "Additive Noise"
f) Select "Overview" > "Input" > "Input Source" > "Radio Frequency" > "Local
Oscillator" > "External"
g) Start the measurement ([RUN SINGLE] or [RUN CONT].
The results in this measurements are 3 dB higher than they actually are. This is
because the divider at the LO AUX inputs is not cancelled out. To get the actual
results, subtract 3 dB from the results, for example by shifting the trace by this
amount ("Overview" > "Analysis" > "Traces" > "Traces" > "Trace Offset: 3 dB").
a) Configure the external signal source to generate the required fixed frequency.
b) Connect the first frequency dividers to the first power splitter.
c) Connect the first frequency divider to the RF input of the R&S FSWP.
d) Connect the second power splitter to the first power splitter.
e) Connect the other two frequency dividers to the second power splitter and con-
nect the resulting signal streams to both LO AUX input channels of the
R&S FSWP.
Regarding the frequency divider, make sure that all three dividers are the same
model and have the same dividing factor.
Also make sure that the frequency fed into all inputs of the R&S FSWP is the
same.
f) Select "Overview" > "Select Measurement" > "Additive Noise"
g) Select "Overview" > "Input" > "Input Source" > "Radio Frequency" > "Local
Oscillator" > "External"
h) Start the measurement ([RUN SINGLE] or [RUN CONT].
Compared to measurements on two dividers, this setup displays the correct
additive noise of the first frequency divider. The results do not have to be cor-
rected. The additive noise of the frequency dividers connected to the LO AUX
inputs is cancelled out because of the cross-correlation properties in the two
channels of the LO AUX input.
You can use either the RF input for these measurements, or the baseband inputs. The
baseband inputs are DC coupled and extend the lower frequency range to 1 mHz (the
lowest supported frequency on the RF input is 1 MHz). Using the baseband input, you
can, for example, test the voltage supply of DC sources.
Test setup
required connections
R&S FSWP
optional connections
Vsupply
Vtune
Vaux
DUT RF / BB*
* = See text below for instructions on how to use the baseband input.
2. Perform a [PRESET].
The application automatically starts a continuous measurement and measures the
noise characteristics of the DUT in the default frequency range.
4. You can stop the measurement (to analyze the measurement data in detail) with
the [RUN SGL] or [RUN CONT] key; [RUN SGL] performs one more measurement,
then stops, [RUN CONT] stops immediately.
By default, two traces are displayed: the first trace shows the smoothed data with-
out spurs, the second trace the raw data including spurs.
Tip: Integrated measurement results. Note that the "PM", "FM" and "Jitter" results
are always "0" for baseband noise measurements.
2. Perform a [PRESET].
4. Enter the "Overview" dialog box, and from there, enter the "Input" dialog box.
7. Select the "Input" channel you are using for the measurement ("CH1", "CH2" or
"CH1xCH2".
The application automatically starts a continuous measurement and measures the
noise characteristics of the DUT in the default frequency range.
Noise measurements on pulses are available with the optional pulsed phase noise
measurements firmware application.
Test setup
required connections
R&S FSWP
optional connections
Vsupply
Vtune
Vaux
DUT RF
Trigger Input
2. Perform a [PRESET].
3. Select the [MEAS] key and select the "Pulsed Phase Noise" measurement.
The application tries to detect a pulse in the signal you have applied, using two
automatic mechanisms:
• search for the pulse frequency
• detection of the pulse characteristics
If successful, it configures a gate based on the pulse characteristics and starts the
noise measurement of the pulse.
The results are displayed the same way as in the other measurements (two traces
in the diagram and results for the integrated measurements).
If no frequency or pulse could be found, a corresponding error message is dis-
played in the status bar below the diagram.
If required, you can also define the frequency and the pulse characteristics man-
ually.
Additive noise measurements on pulses require the optional pulsed phase noise mea-
surements firmware application and the optional signal source output.
The test setup depends on whether you use internal or external modulation with a
pulse modulator.
DUT RF
Trigger Input
3. Perform a [PRESET].
4. Select the [MEAS] key and select the "Pulsed Additive Noise" measurement.
5. Enter the "Overview" dialog box, and from there, enter the "Output" dialog box.
6. Select the "Signal Source" tab and turn on the "Pulse Modulator".
For pulsed measurements using the LO AUX input, do not apply pulses with a fre-
quency below 1024 MHz. Pulses below that frequency will abort the measurement.
required connections
R&S FSWP
optional connections
Signal
Source
Vsupply
Vtune
Vaux
Pulse
DUT RF
Modulator
Trigger Out
The signal source in that case provides a continuous wave signal which is modula-
ted into a pulse by the pulse modulator.
5. Perform a [PRESET].
6. Select the [MEAS] key and select the "Pulsed Phase Noise" measurement.
7. Select the "Signal Source" tab and turn off the "Pulse Modulator".
Measuring the noise characteristics in two different measurement channels allows you,
for example, to capture and analyze two different data streams with different measure-
ment configurations.
2. Define the cross-correlation factor as required in the "XCORR Factor" input field.
The application calculates the number of cross-correlations for each half decade
based on this factor. You can see the resulting operations in the table of the "Noise
Config" dialog box.
The number of operations calculated for each half decade targets a similar mea-
surement time for all half decades, so that the measurement is done at roughly the
same time in each half decade.
You can also see the resulting number of operations in the green bar at the bottom
of the diagram area.
More information:
● Cross-correlation
2. Select the vertical "Trace" tab, and then the horizontal "Traces" tab.
3. For any trace, turn on "Smoothing" and define the amount by which the trace
should be smoothed (in %) in the corresponding input field.
2. Select the vertical "Trace" tab, and then the horizontal "Traces" tab.
3. For any trace, remove or display spurs individually. You can also enter a threshold
that defines a level from which a spur is recognized as a spur.
The application removes all signals that are above the threshold from the trace
spur removal is applied to. Signals with levels below the threshold are not regarded
as spurs and are still displayed.
More information:
● Spur removal
Note: Note that the threshold is always taken into account in the spur table,
regardless of whether spur removal is on or off.
3. Select the "Trace" whose data you would like to integrate from the "Show "drop-
down menu.
Tip: If you select a trace that is currently not displayed in the diagram, no integra-
ted measurement results will be displayed for the corresponding range.
4. Select "Manual" integration ranges.
5. Define the frequency ranges ("Range Start" and "Range Stop") over which you
would like to integrate.
The application calculates the measurement results as defined. Result in the inte-
grated measurements result table are adjusted accordingly (see "Measuring inte-
grated noise" on page 55 for a description on how to view that table).
Figure 6-2: Custom integration range results (frequency range from 3 kHz to 500 kHz, applied to
trace 2)
Note that the integration ranges are displayed graphically in the noise diagram.
Figure 6-3: Custom integration ranges are represented in the diagram as colored lines
The dropdown menu contains all filters currently available on the hard disk of the
R&S FSWP.
When you apply the weighting filter, the results are automatically corrected by the
filter characteristics.
If you do not have a filter yet, or want to change filter characteristics for an existing
filter, design one or change one.
More information:
● Weighting filter design
● Weighting filter management
3. Change the "XCORR Factor", run a single measurement, and see how the position
of the gray area changes.
4. If required, you can turn this area on and off as required with the "XCORR Gain
Indicator" feature.
2. In the diagram, select the area you want to zoom in to (while doing this, the area is
marked by a dotted line).
3. You can return to the full display any time with the "Unzoom" icon in the toolbar
( ).
Labeling traces
Labeling traces with a short keyword is a good way to distinguish traces and see
immediately what the trace actually represents.
1. Enter the "Overview" dialog box and, from there, enter the "Analysis" dialog box.
2. Select the vertical "Traces" tab and the horizontal "Trace Label" tab.
3. Turn on the trace label for a certain trace and define a string of text as a label.
The application adds a label to the trace. The color of the label is the same as the
trace color.
Tip: You can move trace labels around via drag and drop.
2. Select the vertical "Traces" tab and the horizontal "Trace / Data Export" tab.
3. Select the data types as required (trace data only or together with numerical results
and / or measurement settings).
4. Select the "Export to ASCII File" button and select the destination where you want
to save that data.
5. View the .dat file that has been created with your preferred program.
3. Define the measurement range with the "Start Offset" and "Stop Offset" properties.
The application adjusts the measurement range. You can see this change, for
example, in the noise diagram result display.
Note: In case of baseband measurements, the measurement range is defined by
an absolute start and stop frequency instead of offsets.
More information:
● Measurement range
3. Define the frequency range in which the search should take place ("Start" and
"Stop"). By default the search is done in the maximum frequency range supported
by the hardware.
4. Define a "Threshold" for the search. Signals below the threshold are ignored during
the search.
When the application finds a signal with appropriate characteristics, it starts a
phase noise measurement in the measurement range you have defined.
Note: Automatic signal search is only available in phase noise and pulsed phase
noise measurements.
2. Select automatic or manual configuration mode with the "Half Decade Config" fea-
ture.
2. Select the [MEAS CONFIG] key and enter the "Pulse" dialog box with the "Pulse
Config" softkey.
5. Configure the gate as required ("Gate Type", "Gate Level", "Gate Delay" and "Gate
Length").
The shape of the gate is represented by various lines and bars in the "Preview"
diagram that is part of the dialog box.
More information:
● Pulsed phase noise
Tip: You can turn off the gate, if one is not required for the measurement.
To do so, select "Gate Type: Off".
2. Enter the "Overview" dialog box, and from there, enter the "Output" dialog box.
4. Define the frequency and level of the CW signal in the corresponding input fields.
4. Select the output type at the "Trigger 1 Output" (on the front panel) to generate a
pulse at the trigger output.
● "High" generates a high active pulse at the trigger 1 output.
1
V trigger
1
0
t
2
V trigger
1
0
t
Note: In the phase noise application, the trigger connector on the front panel
always serves as an output.
5. Define the required pulse "Width" and "Period".
3. Turn on the output of voltage or current with the "DC Power" feature.
Tip: You can turn the output on and off easily with the "DC On / Off" button in the
toolbar. The "DC Config" button provides access to a softkey menu that lets you
define the signal characteristics without entering a dialog box.
1 2 3 4 5 6 7 8 9
7 = Input field.
8 = Diagram footer: contains diagram-specific information.
9 = Softkeys: provide access to measurement functions.
● Channel Bar............................................................................................................ 75
● Window Title Bar..................................................................................................... 77
● Marker Information.................................................................................................. 78
● Spot Noise Information............................................................................................78
● Measurement Progress Information........................................................................79
● Frequency Information in Diagram Footer.............................................................. 80
● Instrument and Status Information.......................................................................... 80
● Error Information..................................................................................................... 81
Using the R&S FSWP 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. In order to switch from one channel
display to another, simply select the corresponding tab.
Alternatively, if many tabs are displayed, select the tab selection list icon at the right
end of the channel bar and select the channel you want to switch to from the list.
MultiView tab
An additional tab labelled "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 to switch to the corresponding channel dis-
play quickly.
Label Information
RBW Current Resolution bandwidth (RBW). The RBW is a function of the start offset
frequency of each half decade included in the measurement.
XCORR Factor Current cross-correlation factor. The cross-correlation factor defines the number
of cross-correlations are done in each half decade included in the measure-
ment.
Count The current signal count for measurement tasks that involve a specific number
of subsequent sweeps.
Meas Currently selected measurement (Phase Noise, Additive Phase Noise etc.).
Label Information
Input ExtMix Currently selected waveguide band of an external mixer. Only displayed if an
external mixer is selected as an input source.
Gain Difference between DUT signal level and signal source level.
Displayed in Additive Noise measurements.
Each channel in the R&S FSWP display may contain several windows. Each window
can display 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 configu-
ration (see Chapter 7.5, "Displaying Results", on page 88). The window's title bar
indicates which type of evaluation is displayed.
Result type
Trace number Spur removal
Trace smoothing Trace smoothing characteristics. Only displayed if trace smoothing has been
turned on for a trace.
Spur removal Spur removal characteristics. Only displayed if spur removal has been turned
on for a trace.
Trace offset Trace offset characteristics. Only displayed if an offset has been defined for a
trace.
Marker information is provided either in the diagram grid or in separate marker tables,
depending on the configuration.
Label Information
Label Information
Wnd Measurement window that the spot noise has been calculated for.
(Only if there is more than one window containing a phase noise diagram.)
Offset Offset frequency or spot noise position on the x-axis of the Phase Noise dia-
gram.
Noise [T<x>] Measured noise on the spot noise position for each active trace.
The Phase Noise result display shows the progress of the measurement in a series of
green bars at the bottom of the diagram area. For each half decade in the measure-
ment, the R&S FSWP adds a bar that spans the frequency range of the corresponding
half decade.
The bar has several features.
● Measurement times less than 1 s
The numbers within the green bar indicate the number of cross-correlation opera-
tions applied to the corresponding half decade.
● Measurement times greater than 1 s
The numbers within the green bar show the progress of the cross-correlation oper-
ations in the half decade the application currently works on.
The first number is the current, the second number the total count of cross-correla-
tions for that half decade. The bars of half decades in which a measurement is still
running has a lighter tone of green than bars of half decades in which the measure-
ment has already finished (see image below).
● A double-click on the bar opens the "Noise Config" dialog box to define the cross-
correlation factor for that half decade.
● A right-click on the bar opens a context menu.
The context menu provides easy access to various parameters to set up the mea-
surement.
Graphical result displays contain information in the diagram footer. The information
(beneath the diagram) depends on the result display.
The contents depend on the application and the result display.
Label Information
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
Progress
The status of the current operation is displayed in the status bar. This includes the
remaining measurement time for measurements that last longer than 1 second.
Display of the remaining measurement time is supported by the following measure-
ments:
● (Additive) phase noise
● Pulsed (additive) phase noise
● Baseband noise
In the MultiView tab, the progress bar indicates the status of the currently selected
measurement, not the measurement currently being performed by a Sequencer, for
example.
Depending on the type of message, the status message is indicated in varying colors.
Table 7-4: 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 successfull by show-
successful ing a messsage.
Message Meaning
IF OVLD Overload of the IF signal path in the A/D converter or in the digital IF.
Increase attenuation or remove the signal from the RF input.
NO REF Instrument was set to an external reference but no signal was detected on the refer-
ence input.
OVEN The optional OCXO reference frequency has not yet reached its operating tempera-
ture. The message usually disappears a few minutes after power has been switched
on.
WRONG_FW The firmware version is out-of-date and does not support the currently installed hard-
ware. Until the firmware version is updated, this error message is displayed and self-
alignment fails.
(For details refer to the R&S FSWP User Manual).
7.2.1 Toolbar
You can hide the toolbar display, for example when using remote control, in order to
enlarge the display area for the measurement results ("Setup > Display > Displayed
Items"). See the R&S FSWP User Manual for details.
Open: opens a file from the instrument or an external device ("Save/Recall" menu).
Select: the cursor can be used to select (and move) elements in the display (mark-
ers, lines etc.).
Zoom mode: displays a dotted rectangle in the diagram that can be expanded to
define the zoom area.
Multiple zoom mode: multiple zoom areas can be defined for the same diagram.
Signal Source: turns the optional signal source output on and off.
(Available when the optional signal source output is installed.)
RF Config: provides quick access to configure the main parameters of the signal
source.
(Available when the optional signal source output is installed.)
Help (+ Select): allows you to select an element for which context-specific help is dis-
played.
7.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: depending on the selected function key, a different list of soft-
keys 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.
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, in order 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 (for example markers, traces or
the channel bar). If you right-click on one of these items (or tap it for about 1 second), a
menu is displayed which contains the same functions as the corresponding softkey.
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.
(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 the
[ENTER] key or any of the unit keys.
The editing line is highlighted to confirm the entry.
If a field requires alphanumeric input, you can use the on-screen keyboard to enter
numbers and (special) characters (see Chapter 7.2.4, "On-screen Keyboard",
on page 85).
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 7-6.
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 303.
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 7-6.
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 the "0" key 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.
7 7µΩ°€¥$¢
8 A B C 8 Ä ÆÅ Ç
9 DEF9É
4 GHI4
5 JKL5
6 MNO6ŇÖ
1 PQRS1
2 TUV2Ü
3 WXYZ3
. .*:_,;"'?()#
The R&S FSWP 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
application. Whenever you switch channels, the corresponding measurement settings
are restored. Each channel is displayed in a separate tab on the screen.
An additional tab ("MultiView") provides an overview of all currently active channels at
once.
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 consecu-
tively, a Sequencer function is provided.
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 389/ INSTrument:CREate:DUPLicate
on page 389
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 390
Remote command:
INSTrument:DELete on page 390
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..................................................91
● How to Activate SmartGrid Mode............................................................................92
● How to Add a New Result Window......................................................................... 93
● How to Close a Result Window...............................................................................93
● How to Arrange the Result Windows...................................................................... 94
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 7-2). 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.
● Select the "Display Config" softkey from the [Meas Config] menu.
The SmartGrid functions and the evaluation bar are displayed.
To close the SmartGrid mode and restore the previous softkey menu select the "Close"
icon in the right-hand corner of the toolbar, 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 Chapter 7.5.2.5,
"How to Arrange the Result Windows", on page 94 for more information on posi-
tioning the window).
Remote command:
LAYout:ADD[:WINDow]? on page 501 / LAYout:WINDow<n>:ADD? on page 507
► To close a window, activate SmartGrid mode and select the "Delete" icon for the
window.
Remote command:
LAYout:REMove[:WINDow] on page 504 / LAYout:WINDow<n>:REMove
on page 508
1. Select an icon from the evaluation bar or the "Move" icon for an existing evaluation
window.
Remote command:
LAYout:REPLace[:WINDow] on page 505 / LAYout:WINDow<n>:REPLace
on page 508
LAYout:MOVE[:WINDow] on page 504
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 the [SPLIT/MAXIMIZE] key on the front panel. In maximized display,
the currently focused window is maximized. In split display, all active windows are dis-
played.
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 Chapter 13.2, "Display Settings",
on page 281 and Chapter 11.1, "Result Display Configuration", on page 193.
● 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
The R&S FSWP is delivered with IECWIN installed, the auxiliary remote control tool
provided free of charge by Rohde & Schwarz.
For details on the IECWIN tool, see the "Network and Remote Control" chapter of the
R&S FSWP User Manual.
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. Remote Desktop provides access to all of the applications, files, and network
resources of the instrument. Thus, remote operation of the instrument is possible.
The Remote Desktop Client is part of the installed Windows operating system. For
other versions of Windows, Microsoft offers the Remote Desktop Client as an add-on.
You can connect a PC to the R&S FSWP via the GPIB interface to send remote com-
mands to control and operate the instrument. You can configure the GPIB address and
the ID response string. The GPIB language is set as SCPI by default but can be
changed to emulate other instruments.
A GPIB interface is integrated on the rear panel of the instrument.
8 Applications
The R&S FSWP is a dedicated Phase Noise Analyzer whose main feature is the phase
noise measurement application.
When equipped accordingly (with optional hardware or software), it is able to provide
several additional applications for different analysis tasks (for example the spectrum
application).
When you activate an application, the R&S FSWP creates a new measurement chan-
nel which in turn determines the measurement settings for that application. You can
use the same application with different measurement settings by creating several
channels for the same application. Each channel is represented by a separate tab on
the screen.
Note that the number of channels can be limited by the available memory of the
R&S FSWP.
● R&S MultiView........................................................................................................ 98
● Available Applications............................................................................................. 99
● Starting an Application.......................................................................................... 101
● Running a Sequence of Measurements................................................................103
Remote command:
DISPlay:FORMat on page 500
Phase Noise
The phase noise application provides measurement functions to measure the phase
noise characteristics of a DUT.
This application is used in the initial configuration.
For details, refer to Chapter 9, "Measurements and Result Displays", on page 107.
Remote command:
INST:SEL PNO, see INSTrument[:SELect] on page 392
Spectrum Monitor
The spectrum monitor application provides measurement functions for basic I/Q data
analysis.
It runs on the phase noise analyzer hardware and is available for free with firmware
version 1.60.
Compared to the full I/Q analyzer, which runs on the optional spectrum analyzer hard-
ware, it has the following characteristics and limitations.
● When you open a spectrum monitor, the frequency, level and input parameters are
initially adopted from the phase noise application (you can change them in the
spectrum monitor, of course).
Those settings are the same as in the full I/Q analyzer.
● Maximum analysis bandwidth of 20 MHz and sample rate of 25 MHz (and no sup-
port of bandwidth extensions).
● Advanced data acquisition settings are unavailable.
● I/Q data import and export are the same as in the full I/Q analyzer.
● Spectrograms, general marker functionality, marker functions and limit lines are the
same as in the full I/Q analyzer.
● Only external triggers are supported.
● Only evaluation of the frequency spectrum is supported.
Spectrum
The spectrum application is an optional application that is available with R&S FSWP-
B1.
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.
For details, refer to the user manual of the spectrum analyzer measurement applica-
tion.
Remote command:
INST:SEL SAN, see INSTrument[:SELect] on page 392
I/Q Analyzer
The I/Q analyzer application requires an instrument equipped with the spectrum ana-
lyzer hardware component (R&S FSWP-B1).
The I/Q analyzer application provides measurement and display functions for I/Q data.
For details, refer to the user manual of the I/Q analyzer.
Remote command:
INST:SEL IQ, see INSTrument[:SELect] on page 392
Noise Figure
The noise figure application requires an instrument equipped with the spectrum ana-
lyzer hardware (R&S FSWP-B1) and the noise figure Measurements option
(R&S FSWP-K30).
For details, refer to the user manual of the noise figure measurement application.
Remote command:
INST:SEL NOISE, see INSTrument[:SELect] on page 392
Pulse Measurements
The pulse application requires an instrument equipped with the spectrum analyzer
hardware (R&S FSWP-B1) and the pulse measurements option (R&S FSWP-K6(S)).
This application provides measurement functions for pulsed signals.
For details, refer to the user manual of the pulse measurement application.
Remote command:
INST:SEL PULSE, see INSTrument[:SELect] on page 392
Spurious Measurements
The Spurious Measurements application requires an instrument equipped with the
Spurious Measurements option, R&S FSWP-K50. This application provides measure-
ments and evaluations for spurious signal effects.
For details, refer to the user manual of the spurious measurements application.
Remote command:
INST:SEL SPUR, see INSTrument[:SELect] on page 392
Transient Analysis
The Transient Analysis application requires an instrument equipped with the Transient
Analysis option, R&S FSWP-K60. This application provides measurements and evalu-
ations for Transient Analysis.
For details, refer to the user manual of the transient analysis measurement application.
Remote command:
INST:SEL TA, see INSTrument[:SELect] on page 392
The remote commands required to perform these tasks are described in Chapter 15.4,
"Selecting the Operating Mode and Application", on page 389.
The measurement channels are labeled with their default name. If that name already
exists, a sequential number is added.
In remote control, the name of the measurement channel can be changed. For details
and an overview of default names, see INSTrument:LIST?.
New Channel...............................................................................................................102
Replace Current Channel............................................................................................102
Duplicate Current Channel .........................................................................................102
New Channel
The applications selected on this tab are started in a new measurement channel, i.e. a
new tab in the display.
Remote command:
INSTrument:CREate[:NEW] on page 389
INSTrument[:SELect] on page 392
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
required. If activated, the measurements configured in the currently defined "Channel"
s are performed one after the other in the order of the tabs.
For each individual measurement, the sweep count is considered. Thus, each mea-
surement may consist of several sweeps. The currently active measurement is indica-
ted by a symbol in the tab label.
The result displays of the individual channels are updated in the tabs as the measure-
ments are performed. Sequential operation itself is independent of the currently dis-
played tab.
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 394
INITiate:SEQuencer:IMMediate on page 393
INITiate:SEQuencer:ABORt on page 393
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.
Remote command:
INITiate:SEQuencer:MODE on page 394
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.
Residual noise effects are modulation products that originate directly from the phase
noise. It is possible to deduct them mathematically from the phase noise of a DUT.
The application calculates three residual noise effects. All calculations are based on an
integration of the phase noise over a particular offset frequency range.
Residual PM
The residual phase modulation is the contribution of the phase noise to the output of a
PM demodulator. It is evaluated over the frequency range you have defined.
f stop
Residual PM 2 L( f m ) df m rad
f start
Residual FM
The residual frequency modulation is the contribution of the phase noise to the output
of an FM demodulator. It is evaluated over the frequency range you have defined.
f stop
Residual FM 2 f
2
m L ( f m ) df m Hz
f start
Jitter
The jitter is the RMS temporal fluctuation of a carrier with the given phase noise evalu-
ated over a given frequency range of interest.
ResidualPM [rad]
Jitter[s]
2 f 0
with f 0 Carrier frequency
Figure 9-1: Residual noise based on an integration between 10 kHz and 100 kHz offset
2. Configure the number of measurements you would like to perform in a single mea-
surement ("Sweep Config" dialog box, see " Sweep/Average Count "
on page 157).
3. Define how the results are evaluated for display ("Trace" dialog box, see Chap-
ter 11.3, "Trace Configuration", on page 202).
5. To repeat the same number of measurements without deleting the last trace, select
the "Continue Single Sweep" softkey in the "Sweep" menu.
For details on the Sequencer, see Chapter 8.4.1, "The Sequencer Concept",
on page 103.
Remote command:
INITiate<n>[:IMMediate] on page 402
PN Transient analysis..................................................................................................112
Pulsed phase noise measurements (optional)............................................................ 112
Pulsed additive noise measurements (optional)..........................................................112
VCO characterization
Provides tools to measure various characteristics of DUTs whose characteristics
change depending on the applied voltage or current. Examples would be voltage con-
trolled oscillators (VCOs) or YIG oscillators.
The measurement is designed to evaluate DUT characteristics as a function of the tun-
ing voltage (also known as sweep voltage).
Remote command:
CONFigure:VCO:MEASurement[:STATe] on page 399
PN Transient analysis
Provides tools to analyze the transient response of a DUT.
The measurement is designed to monitor the frequency and phase variations of a sig-
nal over time and to find out how long it takes until the signal is in a stable state.
Remote command:
CONFigure:TRANsient:MEASurement[:STATe] on page 398
Noise Diagram
The "Noise Diagram" result display shows the power level of the noise over a variable
frequency offset from the carrier frequency.
The unit of both axes in the diagram is fix. The x-axis always shows the offset frequen-
cies in relation to the carrier frequency on a logarithmic scale in Hz. It always has a
logarithmic scale to make sure of an equal representation of offsets near and far away
from the carrier. The range of offsets that the x-axis shows is variable and depends on
the measurement range you have defined and the scope of the x-axis that you have
set.
The y-axis always shows the noise power level contained in a 1 Hz bandwidth in rela-
tion to the level of the carrier.
The unit of the y-axis depends on which version of the "Noise Spectrum" diagram you
have selected.
● "Noise Spectrum": Default display showing the single sideband phase noise with
linear y-axis in dBc/Hz.
● "Noise Spectrum L(f)": Same as the "Noise Spectrum" without AM noise calcula-
tion.
● "Noise Spectrum SΦ(f)": Display showing the spectral density of phase fluctuations
with linear y-axis in dB/Hz.
● "Noise Spectrum Sv(f)": Display showing the spectral density of frequency fluctua-
tions with logarithmic y-axis in Hz/sqrt(Hz).
● "Noise Spectrum Sy(f)": Display showing the spectral density of fractional fre-
quency fluctuations with logarithmic y-axis in 1/sqrt(Hz).
The R&S FSWP adjusts numerical results like integrated measurements and spot
noise accordingly. AM noise calculation is only supported by the "Noise Spectrum"
result display.
The scale of the y-axis is variable. Usually it is best to use the automatic scaling that
the application provides, because it makes sure that the whole trace is always visible.
You can, however, also customize the range, the minimum and the maximum values
on the y-axis by changing the y-axis scale.
The measurement results are displayed as traces in the diagram area. Up to six active
traces at any time are possible. Each of those can have a different setup and thus
show different aspects of the measurement results.
In the default state, the application shows two traces. A yellow one and a blue one.
Both result from the same measurement data, but have been evaluated differently. On
the first trace, smoothing has been applied, the second one shows the raw data.
The diagram also contains a grey area in its default state. This trace represents the
cross-correlation gain indicator.
Remote command:
TRACe<n>[:DATA]? on page 408
TRACe<n>[:DATA]:X? on page 411
TRACe<n>[:DATA]:X:POINts? on page 411
TRACe<n>[:DATA]:Y? on page 411
TRACe<n>[:DATA]:Y:POINts? on page 412
Integrated Measurements
The "Integrated Measurements" result display summarizes the residual effects results
in a table.
The table consists of up to four rows with each row representing a different integration
interval. Each row basically contains the same information, which depends on the
residual effects configuration.
Result Description
Start / Stop Offset Shows the start and stop offset of the integration
interval.
Result Description
Remote command:
Int. PHN: FETCh<n>[:RANGe<j>]:PNOise<t>:IPN? on page 405
FM: FETCh<n>[:RANGe<j>]:PNOise<t>:RFM? on page 406
AM: FETCh<n>[:RANGe<j>]:PNOise<t>:RAM? on page 405
PM: FETCh<n>[:RANGe<j>]:PNOise<t>:RPM? on page 407
Jitter: FETCh<n>[:RANGe<j>]:PNOise<t>:RMS? on page 406
Spurious List
Spurs are peak levels at one or more offset frequencies and are caused mostly by
interfering signals. The "Spurious List" result display shows the location of all detected
spurs in a table.
Note that only signals above a certain threshold are regarded as spurs. This threshold
is also considered in the spurious list if spur removal has been turned off for a trace.
The order of the spurs in the table depends on the sort order.
The table consists of a variable number of rows. For each detected spur, the table
shows several results.
* For baseband noise measurements, the result is the absolute frequency that the spur is located at.
** For baseband noise measurements, the unit is variable.
*** For baseband noise measurements, the jitter is always 0.
Remote command:
FETCh<n>:PNOise<t>:SPURs? on page 403
FETCh<n>:PNOise<t>:SPURs:COUNt? on page 403
FETCh<n>:PNOise<t>:SPURs:JITTer? on page 404
FETCh<n>:PNOise<t>:SPURs:DISCrete? on page 404
FETCh<n>:PNOise<t>:SPURs:RANDom? on page 404
Spot Noise
The "Spot Noise" result display shows the noise at a certain frequency offset (or spot)
that is part of the measurement range. It is thus like a fixed marker.
The unit of spot noise results is dBc/Hz (variable unit for baseband noise measure-
ments). The application shows the results in a table.
The table consists of a variable number of 10x frequencies (depending on the mea-
surement range), and a maximum of six user frequencies, with each row containing the
spot noise information for a particular frequency offset.
The spot noise information is made up out of several values.
Offset Frequency* Shows the offset frequency the spot noise is evalu-
ated for. You can add any offset that is part of the
measurement range.
The number in brackets (T<x>) indicates the trace
the result refers to.
* For baseband noise measurements, the result is the absolute frequency of the spot.
Remote command:
Querying spot noise results on 10x offset frequencies:
CALCulate<n>:SNOise<s>[:TRACe<t>]:DECades:X? on page 467
CALCulate<n>:SNOise<s>[:TRACe<t>]:DECades:Y? on page 467
Querying custom spot noise results:
CALCulate<n>:SNOise<s>[:TRACe<t>]:Y? on page 468
fh = integration bandwidth
Sy = spectral density of fractional frequency fluctuations
τ = observation time
f = offset frequency
Overall, low values, both variance and deviation, correspond to a stable DUT, high val-
ues to an unstable DUT.
When you measure the stability of an oscillator, the resulting curve has a characteristic
shape. The shape is the same for variance and deviation.
The point of interest in the diagram is the minimum of the curve. First, the deviation is
high, because of noise. During the progression of the observation, the noise averages
out until the minimum is reached. The minimum thus corresponds to the point in time
when the deviation from the specified frequency is at its lowest. After that, the stability
deteriorates due to temperature effects and aging.
From the slope of the curve, you can also identify the type of noise that is in effect
(white noise, flicker phase, white frequency, flicker frequency, random walk).
For a comprehensive discussion of the Allan variance, refer to application note 1EF69:
Time Domain Oscillator Stability Measurement - Allan Variance.
The logarithmic x-axis corresponds to the observation time ("Tau"). Note that Tau is not
the measurement time, but the evaluated time - the measurement lasts longer than
Tau. Because the R&S FSWP calculates the Allan variance based on the measure-
ment range of the phase noise measurement (offset frequency), the observation time
corresponds to the measurement range and vice versa.
The start time also defines the measurement bandwidth or integration bandwidth (fh in
the equation above):
Sensitivity
The "Sensitivity" result display shows the slope of the DUT characteristics, expressed
as the frequency change between measurement points.
The x-axis shows the tuning characteristics of the DC source.
● For Vsupply the tuning voltage in Volt or current in Ampere, depending on the output
type.
● For Vtune and Vaux the tuning voltage in Volt.
The tuning voltages (alternatively: current) applied during the measurement depends
on the tuning range you have defined.
The y-axis shows the sensitivity of the VCO at a given tuning voltage or current in
Hz/V.
Remote command:
TRACe<n>[:DATA]? on page 408
Power
The "Power" result display shows the output power characteristics of the DUT as a
function of the tuning voltage or current.
The x-axis shows the tuning characteristics of the DC source.
● For Vsupply the tuning voltage in Volt or current in Ampere, depending on the output
type.
● For Vtune and Vaux the tuning voltage in Volt.
The tuning voltages (alternatively: current) applied during the measurement depends
on the tuning range you have defined.
The y-axis shows the output power of the VCO at a given tuning voltage or current in
Hz.
Remote command:
TRACe<n>[:DATA]? on page 408
Current / Voltage
The "Current / Voltage" result display shows the voltage or current that the DUT is sup-
plied with by the selected fix source and displays the result for each measurement
point. Each measurement point corresponds to a specific tuning voltage (or current)
that was applied to the DUT.
The x-axis shows the tuning characteristics of the DC source.
● For Vsupply the tuning voltage in Volt or current in Ampere, depending on the output
type.
● For Vtune and Vaux the tuning voltage in Volt.
The tuning voltages (alternatively: current) applied during the measurement depends
on the tuning range you have defined.
The y-axis shows the current or voltage of the selected fix DC source. When VSupply is
configured to supply current and selected as the "Fix Source", the diagram shows the
voltage in Volt. In all other cases, it shows the current in mA.
Remote command:
TRACe<n>[:DATA]? on page 408
Harmonic Power
The "Harmonic Power" result display explicitly shows the power of the fundamental
wave and the power of the harmonics of a DUT measured for each measurement
point.
The x-axis shows the tuning characteristics of the DC source.
● For Vsupply the tuning voltage in Volt or current in Ampere, depending on the output
type.
● For Vtune and Vaux the tuning voltage in Volt.
The tuning voltages (alternatively: current) applied during the measurement depends
on the tuning range you have defined.
The y-axis shows the output power of the DUT at a given tuning voltage or current in
dBm.
Remote command:
TRACe<n>[:DATA]? on page 408
Remote command:
Trace data: TRACe<n>[:DATA]? on page 408
Y-axis scale: Chapter 15.6.10.1, "Frequency Configuration", on page 484
Frequency Deviation
The "Frequency Deviation" result display shows the frequency deviation of the transi-
ent response of the DUT from an ideal linear behavior over time.
The x-axis shows the time period over which the signal has been measured. The scale
depends on the defined start and stop time.
The y-axis shows the deviation of the signal from the reference line within the time-
frame between start and stop time. The scale of the y-axis depends on your configura-
tion.
The frequency deviation calculation settings are described in Chapter 10.10.7, "Fre-
quency Deviation", on page 190.
Remote command:
Trace data: TRACe<n>[:DATA]? on page 408
Phase
The "Phase" result display shows the phase characteristics of the transient response of
the DUT over time.
The x-axis shows the time period over which the signal has been measured. The scale
depends on the measurement time.
The y-axis shows the phase. The scale of the y-axis depends on your configuration.
Remote command:
Trace data: TRACe<n>[:DATA]? on page 408
Y-axis scale: Chapter 15.6.10.5, "Y-Axis Scale", on page 491
Marker Table
Displays a table with the current marker values for the active markers.
This table is displayed automatically if configured accordingly.
Type Shows the marker type and number ("M" for a nor-
mal marker, "D" for a delta marker).
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 501
Results:
CALCulate<n>:MARKer<m>:X on page 529
In addition to the main measurement settings, the "Overview" provides quick access to
the main settings dialog boxes. The individual configuration steps are displayed in the
order of the data flow. Thus, you can easily configure an entire measurement channel
from input over processing to output and analysis by stepping through the dialog boxes
as indicated in the "Overview".
In particular, the "Overview" provides quick access to the following configuration dialog
boxes (listed in the recommended order of processing):
1. Input
See Chapter 10.2, "Input Source", on page 125.
2. Amplitude / Scaling
See Chapter 10.3, "Level Characteristics", on page 142.
3. Frequency
See Chapter 10.4, "Frequency", on page 146.
4. Noise
See Chapter 10.5, "Noise Measurement Configuration", on page 151.
5. Output
See Chapter 10.6, "Output", on page 165.
6. Analysis
See Chapter 11, "Common Analysis and Display Functions", on page 193.
7. Display Configuration
See Chapter 9, "Measurements and Result Displays", on page 107.
In addition, the dialog box provides the "Select Measurement" button that serves as a
shortcut to select the measurement type.
Selecting the noise measurement type....................................................................... 124
Preset Channel........................................................................................................... 125
Specific Settings for ................................................................................................... 125
Remote command:
CONFigure:PNOise:MEASurement on page 397
Preset Channel
Select the "Preset Channel" button in the lower left-hand corner of the "Overview" to
restore all measurement settings in the current channel to their default values.
Do not confuse the "Preset Channel" button with the [Preset] key, which restores the
entire instrument to its default values and thus closes all channels on the R&S FSWP
(except for the default channel)!
See " Preset Mode " on page 302
Remote command:
SYSTem:PRESet:CHANnel[:EXEC] on page 564
10.2.1 RF Input
Access (RF input settings): "Overview" > "Input" > "Input Source" > "Radio Frequency"
> "Config"
Access (schematic test setups): "Overview" > "Input" > "Input Source" > "Radio Fre-
quency" > "Test Setup"
The RF Input is the default input source.
A typical test setup for measurements over the RF input depends on the selected mea-
surement and the equipment used in the test setup. A schematic representation of
such a setup is provided in the dialog box.
● The DUT directly sends a signal to the RF input of the R&S FSWP.
● If necessary, the R&S FSWP can supply the DUT with power over the DC ports.
For more information about configuring the DC ports used in the setup, see Chap-
ter 10.6.1, "DC Source Configuration", on page 165.
The remote commands required to configure the frequency are described in Chap-
ter 15.6.1.1, "RF Input", on page 413.
Radio Frequency State .............................................................................................. 126
Input Coupling ............................................................................................................ 126
Local Oscillator............................................................................................................126
Input Coupling
The RF input of the R&S FSWP can be coupled by alternating current (AC) or direct
current (DC).
AC coupling blocks any DC voltage from the input signal. This is the default setting to
prevent damage to the instrument. Very low frequencies in the input signal may be dis-
torted.
However, some specifications require DC coupling. In this case, you must protect the
instrument from damaging DC input voltages manually. For details, refer to the data
sheet.
Remote command:
INPut<ip>:COUPling on page 413
Local Oscillator
Selects the type of the local oscillator you are using for the measurement.
● Internal
Uses the local oscillator of the R&S FSWP.
● External
Uses an external local oscillator, connected to the "LO AUX Input" (Ch1 and Ch2)
of the R&S FSWP.
R&S FSWP
For an external LO, specify whether the signal at the input has a low or high
"Level". A low level corresponds to signals with a level of approximately 0 dBm. A
high level corresponds to signals with a level between about +5 dBm and
+10 dBm.
The exact definitions of low and high depend on the signal frequency and are
specified in the data sheet.
Note that for low phase noise boards with material number 1331.6439.xx, the low /
high setting is not available.
You can check the material number of the low phase noise board in the hardware
information dialog box (column "order #, see Chapter 13.4.1, "Hardware Informa-
tion", on page 296).
Available for additive noise measurements.
Remote command:
INPut<1|2>:LOSCillator:SOURce on page 414
INPut<1|2>:LOSCillator:SOURce:EXTernal:LEVel on page 414
Access (baseband input settings): "Overview" > "Input" > "Input Source" > "Baseband"
> "Config"
Access (schematic test setups): "Overview" > "Input" > "Input Source" > "Baseband" >
"Test Setup"
Baseband measurements
In addition to the RF input, baseband noise measurements also support measure-
ments on the two channels of the baseband input.
You can either perform measurements on a single channel (select either "CH1" or
"CH1" for that) or perform measurements on both channels simultaneously ("CH1 x
CH2"). In the latter case, the I/Q data is cross-correlated before the results are dis-
played, which allows you to determine the noise characteristics of your DUT very accu-
rately.
Remote command:
Input selection: INPut<ip>:SELect on page 414
Channel selection: INPut<1|2>:CONNector on page 415
The baseband input is always DC coupled, which allows you to measure the noise
characteristics of a DUT near 0 Hz (DC) in the context of baseband noise measure-
ments.
Note that you have to turn on the baseband input deliberately before you can use it.
When the baseband input is active, the RF input is automatically turned off.
A typical test setup for measurements over the RF input depends on the selected mea-
surement and the equipment used in the test setup. A schematic representation of
such a setup is provided in the dialog box.
See Chapter 6.2.4, "The Baseband Noise Measurement", on page 58 for more infor-
mation on how to set up and perform baseband noise measurements.
Access (mixer settings): "Overview" > "Input" > "Input Source" > "External Mixer" >
"Mixer Settings"
Access (basic settings): "Overview" > "Input" > "Input Source" > "External Mixer" >
"Basic Settings"
Access (conversion loss table): "Overview" > "Input" > "Input Source" > "External
Mixer" > "Conversion Loss Table"
Access (schematic test setups): "Overview" > "Input" > "Input Source" > "External
Mixer" > "Test Setup"
The optional support for external mixers allows you to connect up to two external three-
port mixers to the R&S FSWP. An external mixer allows you to perform measurements
on frequencies that are out of the frequency range supported by the R&S FSWP.
External mixers are supported by several measurements in the phase noise applica-
tion.
● Phase noise measurement
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................................................................................................129
● Bias Current.......................................................................................................... 130
● Conversion Loss Tables........................................................................................ 131
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 and span)
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 band "USER", the order of harmonic is defined by the user. The order of har-
monic can be between 2 and 61, the lowest usable frequency being 16.88 GHz.
The frequency ranges for pre-defined bands are described in Table 15-3.
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.
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
R&S FSWP. 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 137 and " Bias " on page 140.
The voltage U0 at the output of the operational amplifier can be set in the range –2.0 to
+2.0 V. An open-circuit voltage Ubias of –0.5 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-
circuit current. A DC return path is ensured via the 66 Ω resistor, which is an advant-
age in some mixers.
Predefined conversion loss tables are often provided with the external mixer and can
be imported to the R&S FSWP.
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 138 for more information about con-
version loss tables.
Before copying any files to the C:\R_S\INSTR\USER\cvl\ directory, the R&S FSWP
firmware 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.
Access: "Overview" > "Input" > "Input Source" > "External Mixer" > "Mixer Settings"
With the R&S FSWP, you can control either one or two three-port mixers.
Most settings are applied globally for both mixers (like the frequency band settings).
Settings that you can configure for each mixer separately are labeled accordingly in the
description below.
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 135).
For details on available frequency ranges, see table 15-3 on page 417.
Remote command:
[SENSe:]MIXer<x>:FREQuency:STARt on page 416
[SENSe:]MIXer<x>:FREQuency:STOP on page 417
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 416
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 15-3 on
page 417.
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 135).
Remote command:
[SENSe:]MIXer<x>:HARMonic:BAND on page 417
RF Overrange
In some cases, 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 421
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 418
Mixer XCORR
Turns the simultaneous use of two external mixers on and off.
Using two external mixers allows you to perform measurements with external cross-
correlation. Through cross-correlation operations, the noise of the DUT is kept constant
while the noise of the signal path (including the external mixers) is reduced.
Remote command:
[SENSe:]MIXer<x>:XCORr on page 421
Range 1 / Range 2
Enables the use of one or two frequency ranges, where the second range is based on
another harmonic frequency of the mixer to cover the band's frequency range.
For each range, you can define which harmonic to use and how the conversion loss is
handled.
If you are using two mixers, this property is always the same for both mixers.
Remote command:
[SENSe:]MIXer<x>:HARMonic:HIGH:STATe on page 418
Harmonic Type
Defines if only even, only odd, or even and odd harmonics can be used for conversion.
Depending on this selection, the order of harmonic to be used for conversion changes
(see " Harmonic Order " on page 136). Which harmonics are supported depends on
the mixer type.
If you are using two mixers, the harmonic type is always the same for both mixers.
Remote command:
[SENSe:]MIXer<x>:HARMonic:TYPE on page 419
Harmonic Order
Defines which order of the harmonic of the LO frequencies is used to cover the fre-
quency range.
By default, the lowest order of the specified harmonic type is selected that allows con-
version of input signals in the whole band. If due to the LO frequency the conversion is
not possible using one harmonic, the band is split.
For the "USER" band, you define the order of harmonic yourself. The order of har-
monic can be between 2 and 61, the lowest usable frequency being 16.88 GHz.
If you are using two mixers, the harmonic type is always the same for both mixers..
Remote command:
[SENSe:]MIXer<x>:HARMonic[:LOW] on page 419
[SENSe:]MIXer<x>:HARMonic:HIGH[:VALue] on page 418
Conversion Loss
Defines how the conversion loss is handled. The following methods are available:
If you are using two mixers, you can define the source of the conversion loss data for
each mixer separately.
"Average" Defines the average conversion loss for the entire frequency range in
dB.
"Table" Defines the conversion loss via the table selected from the list. Pre-
defined conversion loss tables are often provided with the external
mixer and can be imported to the R&S FSWP. Alternatively, you can
define your own conversion loss tables. Imported tables are checked
for compatibility with the current settings before being assigned.
Conversion loss tables are configured and managed in the Conver-
sion Loss Table tab.
For details on importing tables, see " Import Table " on page 139.
Remote command:
Average for range 1:
[SENSe:]MIXer<x>:LOSS[:LOW] on page 420
Table for range 1:
[SENSe:]MIXer<x>:LOSS:TABLe[:LOW] on page 420
Average for range 2:
[SENSe:]MIXer<x>:LOSS:HIGH on page 419
Table for range 2:
[SENSe:]MIXer<x>:LOSS:TABLe:HIGH on page 420
Access: "Overview" > "Input" > "Input Source" > "External Mixer" > "Basic Settings"
With the R&S FSWP, you can control either one or two three-port mixers.
Most settings are applied globally for both mixers (like the frequency band settings).
Settings that you can configure for each mixer separately are labeled accordingly in the
description below.
LO Level .....................................................................................................................137
Bias Value .................................................................................................................. 137
└ Write to CVL table ........................................................................................137
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.
If you are using two mixers, you can define the LO level for each mixer separately.
Remote command:
[SENSe:]MIXer<x>:LOPower on page 423
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 the Write
to CVL table button.
The "Bias Value" is available for mixer 1 only.
Remote command:
[SENSe:]MIXer<x>:BIAS[:LOW] on page 422
[SENSe:]MIXer<x>:BIAS:HIGH on page 422
New Table
Opens the "Edit conversion loss table" dialog box to configure a new conversion loss
table.
For details on table configuration, see "Editing Conversion Loss Tables" on page 139.
Remote command:
[SENSe:]CORRection:CVL:SELect on page 427
Edit Table
Opens the "Edit conversion loss table" dialog box to edit the selected conversion loss
table.
For details on table configuration, see "Editing Conversion Loss Tables" on page 139.
Remote command:
[SENSe:]CORRection:CVL:SELect on page 427
Delete Table
Deletes the currently selected conversion loss table after you confirm the action.
Remote command:
[SENSe:]CORRection:CVL:CLEar on page 425
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 136).
Note:
Before copying any files to the C:\R_S\INSTR\USER\cvl\ directory, the R&S FSWP
firmware 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.
Remote command:
MMEM:COPY '<conversionlosstable>',C:\R_S\INSTR\USER\cvl\
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 with 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 427
Comment
An optional comment that describes the conversion loss table. The comment is user-
definable.
Remote command:
[SENSe:]CORRection:CVL:COMMent on page 425
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 15-3 on
page 417.
Remote command:
[SENSe:]CORRection:CVL:BAND on page 424
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 426
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 137.
Remote command:
[SENSe:]CORRection:CVL:BIAS on page 424
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 426
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 427
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 426
Position / Value
Each position/value pair defines the conversion loss value in dB for a specific fre-
quency. The reference values must be entered in order of increasing frequencies. A
maximum of 50 reference values can be entered. To enter a new value pair, select an
empty space in the "Position" / "Value" table, or select the Insert Value button.
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 that 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 425
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.
Signal attenuation reduces the level of the signal that you feed into the R&S FSWP.
Reducing the level is necessary to protect the input mixer from signals with high levels,
because high levels can cause an overload of the input mixer. An input mixer overload
in turn can lead to incorrect measurement results or even damage or destroy the input
mixer.
The level at the input mixer is determined by the set RF attenuation according to the
formula:
levelmixer = levelinput - RF attenuation
The maximum level that the input mixer can handle is 0 dBm. Levels above this value
cause an overload. The R&S FSWP indicates an overload situation by the "RF OVLD"
label in the status bar.
The R&S FSWP features a mechanical attenuator. The mechanical attenuator is loca-
ted directly after the RF input of the R&S FSWP. Its step size is 5 dB.
For ideal sinusoidal signals, the displayed signal level is independent of the RF attenu-
ation.
In the default state, the R&S FSWP automatically determines the attenuation according
to the signal level that is currently applied. Automatic determination of the attenuation
is a good way to find a compromise between a low noise floor, high intermodulation
levels, and protecting the instrument from high input levels.
However, you can also define the attenuation manually, if necessary.
Note that you should attenuate the signal if its level is too high, especially if you have
no idea about the signal strength you are measuring. For more information, see
"Attenuating the signal" on page 144.
The measurement starts only if the signal level is within the level threshold that you
have defined via the "Auto Search" feature.
If the signal level is outside the threshold that you have defined, it is ignored.
Level
search
area
pthr
The remote commands required to configure the amplitude are described in Chap-
ter 15.6.4, "Remote Commands to Configure Level Characteristics", on page 443.
Scaling the y-axis........................................................................................................ 145
Selecting the unit of the y-axis.................................................................................... 146
● When you change the "Range" only, the "Bottom" value is adjusted.
In addition, you can perform a single automatic scale adjustment with the "Auto Scale
Once" feature. When you do so, the R&S FSWP selects the ideal scale for the current
measurement results, but will not update the scale for the next measurement.
Remote command:
Mode: DISPlay[:WINDow<n>]:TRACe<t>:Y[:SCALe]:AUTO on page 445
Top: DISPlay[:WINDow<n>]:TRACe<t>:Y[:SCALe]:RLEVel on page 446
Bottom: DISPlay[:WINDow<n>]:TRACe<t>:Y[:SCALe]:RLEVel:LOWer
on page 446
Range: DISPlay[:WINDow<n>]:TRACe<t>:Y[:SCALe] on page 445
10.4 Frequency
Access (carrier frequency): "Overview" > "Frequency"
Access (measurement range): "Overview" > "Noise Config" > "Noise Config"
Frequency settings allow you to control the characteristics of the measurement fre-
quency.
The auto search features are available for phase noise and pulsed phase noise mea-
surements.
The remote commands required to configure the frequency are described in Chap-
ter 15.6.5, "Remote Commands to Configure the Frequency", on page 449.
Defining the signal frequency......................................................................................147
Searching for a signal................................................................................................. 148
Capture Range............................................................................................................149
Defining the measurement range................................................................................149
Measuring low frequency and low level signals.......................................................... 150
└ Low signal frequencies................................................................................. 150
└ Low signal levels...........................................................................................150
└ Multicarrier signals........................................................................................ 151
For pulsed measurements (phase noise and additive noise), the minimum supported
carrier frequency is 30 MHz.
Not available for baseband noise measurements.
Remote command:
[SENSe:]FREQuency:CENTer on page 452
In case you already know the signal frequency, you can also turn off the "Auto Search"
and define it manually. When you turn off automatic search, the R&S FSWP still veri-
fies if a signal is present at the frequency you have defined and, if necessary, adjusts
the frequency if the signal is a few Hz off. If you want to skip the signal verification and
measure exactly the frequency you have entered manually, turn off the "Signal Count"
feature. In that case, the R&S FSWP tunes to the frequency you have entered and
measures its phase noise characteristics, even if no signal is present. Turning off the
frequency counter can improve measurement speed, however.
The measurement starts only if a signal is present within the frequency search limits
that you have defined via the "Auto Search" feature. The search range is defined by a
minimum and maximum value. The maximum frequency range that you can scan
depends on the hardware you are using. Note that a signal must also be within a cer-
tain level range for it to be detected.
No measurement will be initiated if no signal can be found in the frequency search
range you have defined.
Level
search
area
pthr
During a frequency scan, the R&S FSWP steps through the frequency search range
you have defined in a predefined step size (one step usually covers the full I/Q band-
width).
Signal search is only available for phase noise and pulsed phase noise measurements.
Remote command:
Signal frequency: [SENSe:]FREQuency:CENTer on page 452
Mode: [SENSe:]ADJust:CONFigure:FREQuency:AUTosearch[:STATe]
on page 449
Signal count: [SENSe:]ADJust:CONFigure:FREQuency:COUNt on page 449
Capture Range
The "Capture Range" defines the bandwidth with which the R&S FSWP searches for a
signal or tracks drifting signals.
Use a "Normal" capture range for stable or slowly drifting DUTs. For fast drifting DUTs,
use a "Wide" capture range.
Use a "40 MHz" capture range to measure carriers swept from -40 MHz to +40 MHz
relative to the center frequency. Additional spurs and restrictions of the measurement
accuracy are possible for CW signals, or carriers swept in other frequency ranges. For
specifics of the measurement accuracy, refer to the data sheet.
The capture range is available for the phase noise measurement.
Remote command:
[SENSe:]SWEep:CAPTure:RANGe on page 454
Low signal frequencies ← Measuring low frequency and low level signals
The R&S FSWP provides a low pass filter that suppresses the DC offset of the I/Q
mixer to measure signal frequencies below 1 MHz. Applying the filter results in a better
sensitivity.
When you are measuring such signals, turn on the filter ("State"), and define its "Cutoff
Frequency". The cutoff frequency should be the same as the signal frequency. For
example, the cutoff frequency to measure a signal frequency of 100 Hz should also be
100 Hz.
Measuring low frequencies and levels is available for phase noise measurements on
continuous wave signals.
Note that using the filter has several effects.
● The automatic search for a signal is not supported. Define the signal frequency
manually instead.
● A signal count is not possible.
● The stop offset is limited to 30 % of the carrier signal frequency.
For measurements on frequencies below 10 MHz, you must use DC coupling (inde-
pendent of the low pass filter).
Remote command:
Filter state: [SENSe:]FILTer:LPASs[:STATe] on page 451
Cutoff frequency: [SENSe:]FILTer:LPASs:FREQuency:MANual on page 451
Low signal levels ← Measuring low frequency and low level signals
The R&S FSWP supports different modes to measure signals with different levels.
Depending on the measurement, select the appropriate "Level Setting".
● "High": The R&S FSWP works like a traditional phase noise tester with zero IF and
is therefore limited in the sensitivity.
● "Low": The R&S FSWP uses an IF of 15 MHz. Therefore, the DC offset of the I/Q
mixers does not limit the sensitivity. It is recommended to use this level setting for
signal levels below -20 dBm.
For very low signal levels (below approximately -40 dBm), the broadband noise in
the demodulator becomes an issue and disables the measurement. To measure
such signals, apply the low pass filter, because it reduces the noise bandwidth.
The nominal improvement of the sensitivity is 10 dB for 10 MHz, 20 dB for 1 MHz
cutoff frequency.
The start of the noise measurements can be defined via the "Trigger" hardkey. If "Free
Run" is selected, no trigger source is considered. You can start the measurement man-
ually any time and stop it as required. If "External Trigger 1" is selected, a measure-
ment starts when a TTL signal is fed into the specified input connector.
This breakdown into several half decades is made to speed up measurements. See
"Working with the half decade configuration table" on page 157 for more information
about the measurement configuration in each half decade.
The main issue in this context is the resolution bandwidth (RBW) and its effect on the
measurement time. In general, it is best to use a resolution bandwidth as small as pos-
sible for the most accurate measurement results. However, accuracy comes at the
price of measurement speed.
To avoid long measurement times, the application provides only a certain range of
RBWs that are available for each half decade.
The remote commands required to configure the measurement range are described in
Chapter 15.6.6.1, "Noise Configuration", on page 455.
Functions to configure the measurement range described elsewhere:
● Start Offset
● Stop Offset
● Capture Range
Estimating the measurement time...............................................................................153
Defining the resolution bandwidth............................................................................... 154
Ultra-Small RBWs....................................................................................................... 154
Defining cross-correlation parameters........................................................................ 155
Turning the display of the cross-correlation gain indicator on and off......................... 156
Capture Range............................................................................................................156
Sweep/Average Count ............................................................................................... 157
Selecting the sweep direction..................................................................................... 157
Working with the half decade configuration table........................................................157
Ultra-Small RBWs
Provides functionality to enable ultra-small resolution bandwidths (RBW) for the current
measurement. It can only be used in phase noise and additive noise measurements.
The minimum RBW can be set to 0.0003% (instead of 0.1%) if this function is enabled.
Also, only one measurement channel can be used due to memory limitation.
Be aware that if the function is enabled, and the function is enabled in an instrument
saveset, recall of the saveset fails. If the function is enabled in a saveset used for
startup recall, every second preset acts as if startup recall had been disabled.
If this function is enabled and RBWs below 0.1% are used, the estimated measure-
ment time is not available.
Remote command:
[SENSe:]LIST:BWIDth[:RESolution]:USMall on page 458
Example:
The operations in the first half decade need 1 s to finish. The number of operations
done in the other half decades is calculated with respect to this 1 s timeframe. For
example, if the application can perform 10 cross-correlation operations in 1 s in
another half decade, it will do so, but no more than that number.
You can control the number of cross-correlations for the first half decade with the
cross-correlation factor ("XCORR Factor"). By multiplying this value with the base num-
ber of operations for the first half decade, the application calculates the time it takes to
perform these operations in the first half decade and then adjusts the number of opera-
tions for all other half decades.
When you turn on the "XCORR Optimization" feature, cross-correlation operations are
only performed as long as the measurement results still improve. When this is not the
case, the R&S FSWP stops calculating results, even when the selected number of
operations has not yet been reached. This is thus a good tool to speed up the mea-
surement.
The point at which measurement results cannot be improved anymore is defined by the
"XCORR Optimization Threshold". The threshold is the distance between the gain indi-
cator and the actual trace. When the distance between those two traces exceeds the
threshold in any given half decade, the R&S FSWP stops measuring in this half dec-
ade and resumes with the next one.
Example:
The number of operations in a half decade is 30. When optimization is on, and the
results do not improve any more after 20 operations, the application stops measure-
ments in that half decade.
You can also finish the measurement of a specific half decade manually with the "Fin-
ish Segment" softkey available in the "Sweep" menu. The R&S FSWP resumes the
measurement of the next half decade in that case.
For offsets greater than 30 MHz, each half decade is divided into smaller segments.
For these offsets, the "Finish Segment" feature does not resume with the next half dec-
ade, but with the next offset segment.
Remote command:
Configuration mode: [SENSe:]SWEep:MODE on page 459
XCORR factor: [SENSe:]SWEep:XFACtor on page 460
XCORR number: [SENSe:]LIST:RANGe<r>:XCOunt on page 457
Optimization: [SENSe:]SWEep:XOPTimize[:STATe] on page 460
Optimization threshold: [SENSe:]SWEep:XOPTimize:THReshold on page 460
Finish segment: [SENSe:]SWEep:FSEGment on page 459
Capture Range
The "Capture Range" defines the bandwidth with which the R&S FSWP searches for a
signal or tracks drifting signals.
Use a "Normal" capture range for stable or slowly drifting DUTs. For fast drifting DUTs,
use a "Wide" capture range.
Use a "40 MHz" capture range to measure carriers swept from -40 MHz to +40 MHz
relative to the center frequency. Additional spurs and restrictions of the measurement
accuracy are possible for CW signals, or carriers swept in other frequency ranges. For
specifics of the measurement accuracy, refer to the data sheet.
The capture range is available for the phase noise measurement.
Remote command:
[SENSe:]SWEep:CAPTure:RANGe on page 454
Sweep/Average Count
Defines the number of measurements to be performed in the single sweep mode. Val-
ues from 0 to 200000 are allowed. If the values 0 or 1 are set, one measurement is
performed.
The sweep count is applied to all the traces in all diagrams.
For "Average" trace mode, the "Sweep Count" also determines the number of individ-
ual measurements used to average the trace.
In continuous sweep mode, a "Sweep Count" = 0 (default) calculates a moving aver-
age over 10 measurements. A "Sweep Count" = 1 calculates no averages.
Remote command:
[SENSe:]SWEep:COUNt on page 458
Remote command:
State: CALCulate<n>[:RANGe<j>]:EVALuation[:STATe] on page 463
Start: CALCulate<n>[:RANGe<j>]:EVALuation:STARt on page 462
Stop: CALCulate<n>[:RANGe<j>]:EVALuation:STOP on page 462
The remote commands required to configure spot noise measurements are described
in Chapter 15.6.6.3, "Spot Noise Configuration", on page 465.
Displaying spot noise information............................................................................... 161
Selecting the spot noise positions...............................................................................161
You can define any offset frequency that is part of the measurement range as a new
spot noise position. To exclude an offset frequency, uncheck the checkbox of the cur-
rent offset.
The results for the user defined spot noise positions are displayed in the spot noise
table in addition to the decade edge spot noise results.
When you turn off the "Decade Edges" spot noise positions, the spot noise table con-
tains only the user defined spot noise positions.
Remote command:
See Chapter 15.6.6.3, "Spot Noise Configuration", on page 465.
The remote commands required to configure the spur display are described in Chap-
ter 15.6.6.4, "Spur Display", on page 469.
Hiding spurs
Hiding spurs is a method to remove displayed peak levels visually.
You can apply spur removal to all active traces individually (spurious removal "Hide In
Diagram"), and define a threshold (in dB) that defines when a peak level is recognized
as a spur (spurious removal "Detection Threshold").
Note: In the spot noise vs tune measurement, spur removal properties apply to all
traces.
Remote command:
State: DISPlay[:WINDow<n>]:TRACe<t>:SPURs:SUPPress on page 470
Value: DISPlay[:WINDow<n>]:TRACe<t>:SPURs:THReshold on page 470
State (SN vs Tune): [SENSe:]SPURs:SUPPress on page 483
Value (SN vs Tune): [SENSe:]SPURs:THReshold on page 483
Sorting spurs
The sort order of the spurs in the spurious list result display depends on the "Sort
Order" you select.
"Power" Sorts the spurs according to their power (highest to lowest power).
"Offset" Sorts the spurs according to their offset from the carrier (lowest to
highest offset).
Remote command:
[SENSe:]SPURs:SORT on page 471
Filtering spurs
Filtering spurs is a method to show or hide items of the spurious list.
Mode ● "Off": No spurious filter is applied.
● "Suppress": The spurs in the spurious filter are removed from the
spurious list, the diagram and dependent calculations.
● "Show": Only the spurs in the spurious filter are displayed in the
spurious list, the diagram and dependent calculations.
Include Har- In addition to the spurs in the defined spurious filter list, also their har-
monics monics are displayed or removed in the spurious list.
Range Defines the filter range as a multiple of the resolution bandwidth.
Name Displays the name of the currently selected spurious filter.
Spurious Filter The spurious filter configuration table provides several management
Management tools:
● "Insert": Adds a new offset frequency to the spurious filter.
● "Delete": Removes an existing offset frequency from the spurious
filter.
● "Clear": Clears the spurious filter.
● "Save": Saves the spurious filter configuration. With this function,
the name of the spurious filter can be defined.
● "Load": Loads an existing spurious filter configuration.
Remote command:
[SENSe:]SPURs:FILTer:MODE on page 471
[SENSe:]SPURs:FILTer:HARMonics on page 472
[SENSe:]SPURs:FILTer:RANGe on page 472
[SENSe:]SPURs:FILTer:NAME? on page 472
[SENSe:]SPURs:FILTer:OFFSet on page 472
[SENSe:]SPURs:FILTer:CLEar on page 473
[SENSe:]SPURs:FILTer:SAVE on page 473
[SENSe:]SPURs:FILTer:LOAD on page 473
10.6 Output
The phase noise application is able to provide different kinds of output for various pur-
poses.
For more information about the available connectors, refer to the getting started man-
ual.
● DC Source Configuration...................................................................................... 165
● Signal Source Configuration................................................................................. 168
● Miscellaneous Output............................................................................................172
Access (all DC port settings): "Overview" > "Output" > "Output" > "DC Config"
Access (most relevant DC port settings): (in the toolbar)
Access (DC port state): "Overview" > (in the toolbar)
The "DC Power" settings allow you to configure the DC power supply sources available
on the front panel for different purposes.
The remote commands required to configure the DC power output are described in
Chapter 15.6.2, "Output", on page 428.
Turning the DC output on and off................................................................................ 166
Coupling the output configuration across measurement channels............................. 166
Configuring the DC power output................................................................................166
└ Turning the output on and off........................................................................ 167
└ Selecting the output type (Vsupply only).......................................................167
└ Defining the output level............................................................................... 167
└ Reading the actual output levels...................................................................168
Note: If you change one of the DC power output parameters during a measurement,
the measurement is aborted and restarted.
For more information about the output connectors, refer to the getting started.
Basically, you can define the same parameters for all three outputs.
● "Turning the output on and off" on page 167
● "Selecting the output type (Vsupply only)" on page 167
● "Defining the output level" on page 167
● "Reading the actual output levels" on page 168
Selecting the output type (Vsupply only) ← Configuring the DC power output
The supply voltage output (Vsupply) supports variable voltages and variable current. For
this output, you can select whether you want to control the output in terms of current or
voltage.
When you select "Voltage", you can define the output in terms of the voltage that is
supplied. The supplied current is adjusted accordingly (up to the maximum current you
have allowed).
When you select "Current", you can define the output in terms of the current that is
supplied. The supplied voltage is adjusted accordingly (up to the maximum voltage you
have allowed).
The other outputs are already limited regarding the output current; only the voltage is
variable for these outputs.
Note: When you switch between "Voltage" and "Current", DC output is turned off as a
precaution. You have to turn it on again deliberately.
Remote command:
SOURce:VOLTage:POWer<i>:LEVel:MODE on page 435
Note that when you change the output voltage while a measurement is running, this
measurement is aborted and restarted.
Controlling the supply current for the Vsupply output
For the supply voltage output (Vsupply), you can select whether you want to control the
output in terms of current or voltage (➙ Output Type).
If you select output type "Voltage", you can define the output level and limits in terms of
voltage (the current is adjusted, if necessary).
If you select output type "Current", you can define the output level and limits in terms of
current (the voltage is adjusted, if necessary) . In that case, the range defining the soft
limits are also defined in terms of current.
In addition, you can define the maximum output current (or voltage) that is supplied in
the "Max Curr / Volt" field.
For the other two outputs (Vtune and Vaux), the maximum current that can be drawn by
the DUT is fixed to the value supported by the hardware. The "Max Curr / Volt" infor-
mation is read-only information for these two outputs.
Remote command:
Level Vsupply: SOURce:VOLTage:POWer<i>:LEVel:AMPLitude on page 433
Level Vtune: SOURce:VOLTage:CONTrol<i>:LEVel:AMPLitude on page 432
Level Vaux: SOURce:VOLTage:AUX:LEVel:AMPLitude on page 430
Limits Vsupply: SOURce:VOLTage:POWer<i>:LEVel:LIMit:LOW on page 434 /
SOURce:VOLTage:POWer<i>:LEVel:LIMit:HIGH on page 434
Limits Vtune: SOURce:VOLTage:CONTrol<i>:LEVel:LIMit:LOW on page 432 /
SOURce:VOLTage:CONTrol<i>:LEVel:LIMit:HIGH on page 432
Limits Vaux: SOURce:VOLTage:AUX:LEVel:LIMit:LOW on page 430 / SOURce:
VOLTage:AUX:LEVel:LIMit:HIGH on page 430
Max. V / A: SOURce:VOLTage:POWer<i>:LIMit:HIGH on page 435
Access (all settings): "Overview" > "Output" > "Output" > "Signal Source"
Access (most relevant signal source settings): (in the toolbar)
The remote commands required to configure the signal source output are described in
Chapter 15.6.2.2, "Signal Source", on page 437.
Functions to configure the signal source output described elsewhere:
● "Coupling the output configuration across measurement channels" on page 166
Signal source state......................................................................................................170
Signal source frequency..............................................................................................170
Signal source level...................................................................................................... 170
This can come in handy when measuring the additive noise, and you would like to
draw a trace that shows the contribution of the R&S FSWP to the overall noise charac-
teristics.
The feature works for additive noise and pulsed additive noise measurements. It is also
available in the optional applications, Spectrum application, the I/Q Analyzer etc.
Remote command:
SOURce:GENerator:DUTBypass on page 437
Pulse characteristics
The signal source hardware allows you to generate a pulse when you perform pulsed
measurements.
The pulse with the defined characteristics is generated internally when you turn on the
Pulse Modulation feature.
● "Period"
The pulse period defines the distance between two consecutive pulses (off time of
the pulse).
● "Width"
The pulse width defines the length of the pulse (on time of the pulse).
Note: Pulse period and width apply to the pulse that is output at the signal source
as well as the pulse that is output at the trigger 1 output.
● "Trigger 1 Output"
Selects the pulse type sent to the trigger output.
You can use the signal on the trigger 1 output to control an external pulse modula-
tor, for example.
– "Off": Provides no signal at the trigger output.
– "High": Provides a (high active) pulse with the defined width and period at the
trigger output.
1
V trigger
1
0
t
– "Low": Provides a (low active) pulse with the defined width and period at the
trigger output.
2
V trigger
1
0
t
Note that the pulse at the trigger output is generated even when the "Pulse Modu-
lation" feature is turned off.
Remote command:
Period: SOURce:GENerator:PULSe:PERiod on page 439
Width: SOURce:GENerator:PULSe:WIDTh on page 440
Trigger Output: SOURce:GENerator:PULSe:TRIGger:OUTPut on page 439
The R&S FSWP provides a connector ([NOISE SOURCE CONTROL]) with a voltage
supply for an external noise source. By switching the supply voltage for an external
noise source on or off in the firmware, you can activate or deactive the device as
required.
External noise sources are useful when you are measuring power levels that fall below
the noise floor of the R&S FSWP itself, for example when measuring the noise level of
an amplifier.
In this case, you can first connect an external noise source (whose noise power level is
known in advance) to the R&S FSWP and measure the total noise power. From this
value you can determine the noise power of the R&S FSWP. Then when you measure
the power level of the actual DUT, you can deduct the known noise level from the total
power to obtain the power level of the DUT.
The noise source is controlled in the "Output" settings, see "Noise Source Control"
on page 172
External noise sources are useful when you are measuring power levels that fall below
the noise floor of the R&S FSWP itself, for example when measuring the noise level of
an amplifier.
In this case, you can first connect an external noise source (whose noise power level is
known in advance) to the R&S FSWP and measure the total noise power. From this
value you can determine the noise power of the R&S FSWP. Then when you measure
the power level of the actual DUT, you can deduct the known noise level from the total
power to obtain the power level of the DUT.
Remote command:
DIAGnostic:SERVice:NSOurce on page 441
The remote commands required to configure pulses are described in Chapter 15.6.7,
"Pulsed Phase Noise Configuration", on page 474.
When you already know the pulse characteristics, you can also configure the measure-
ment manually by selecting "Manual" mode and entering the values as required.
Remote command:
[SENSe:]SWEep:PULSe:DETection on page 475
In the default state, when automatic pulse detection is on, the gate characteristics are
determined based on the pulse characteristics. In that case, changes here not neces-
sary.
The "Gate Level" defines the signal level that opens the gate. As long as the signal
level is below the gate level, no data is recorded. When the signal level rises above the
gate level, the measurement starts. For the "Gate Type: Level", the gate level also
defines the moment when the gate closes, and data acquisition stops.
In the preview diagram, the gate level is indicated by a red horizontal line. A label also
indicates the currently defined gate level.
The "Gate Delay", defines a time offset between the moment the level rises above the
gate level (= the beginning of the pulse) and the actual start of the measurement.
When you define a gate delay, the first few measurement points after the gate opens
are not considered in the measurement results.
In the preview diagram, the gate delay is indicated by a blue bar. The actual starting
point of data acquisition is indicated by a red vertical line in the preview diagram.
The "Gate Length" defines the time period that the gate is open. It is closed when the
time define by the gate length has elapsed. The gate length is only available for "Gate
Type: Edge".
In the preview diagram, the gate length is indicated by a magenta colored bar. The end
of the gate in that case is indicated by second red vertical line.
Remote command:
Level: [SENSe:]SWEep:EGATe:LEVel on page 475
Delay: [SENSe:]SWEep:EGATe:HOLDoff on page 474
Length: [SENSe:]SWEep:EGATe:LENGth on page 474
Most of the functionality for VCO characterization is the same as in the phase noise
measurement, differences and additional functionality is described in this section of the
documentation.
Refer to the following topics for more information about equivalent functionality.
● Input configuration: Chapter 10.2, "Input Source", on page 125
● Amplitude configuration and diagram scale: Chapter 10.3, "Level Characteristics",
on page 142
● DC source configuration: Chapter 10.6.1, "DC Source Configuration", on page 165
● Measurement configuration: Chapter 9.2, "Performing Measurements",
on page 108
● Limit line configuration: Chapter 11.5, "Limit Lines", on page 232
● Marker configuration: Chapter 11.4, "Markers", on page 223
Notable differences are the measurement configuration itself and the trace configura-
tion, as described in this topic.
● Sweep Configuration.............................................................................................177
● Trace Configuration...............................................................................................180
DC source configuration
The functionality to configure the DC sources is basically the same as in the "DC Con-
fig" dialog box. The main difference is that the dialog box does not show all available
DC sources. Instead, you have to select the DC source you would like to use.
● "Sweep Source"
Selects the DC source that tunes the DUT. Voltage or current change supplied by
the sweep source on each measurement point.
Remote command:
VCO characterization: CONFigure:VCO:SWEep:SOURce on page 479
Spot noise vs tune: CONFigure:SNTune:SWEep:SOURce on page 481
● "Fix Source"
Selects the DC source that is considered in the Current / Voltage result display.
Current or voltage supplied by the fix source remains on a fix value during the
measurement.
Remote command:
CONFigure:VCO:FIX:SOURce on page 477
For the other features, refer to the following topics.
● "Turning the DC output on and off" on page 166
● "Turning the output on and off" on page 167
● "Selecting the output type (Vsupply only)" on page 167
● "Defining the output level" on page 167
Sweep settings
The sweep settings define the tuning properties. They control the output of the
selected DC source over the course of a measurement: which voltage or current is
applied for each measurement, the sweep range and the measurement time for each
measurement point.
You can define sweep settings for each DC source individually.
Defining the sweep range........................................................................................... 178
Defining the settling time.............................................................................................179
Selecting the frequency resolution.............................................................................. 179
Example:
The start and stop values are 0 V and 5 V respectively. The number of measurement
points is 10.
This means that a measurement is performed on every 0.5 V of voltage:
0 V, 0.5 V, 1 V, 1.5 V, etc.
Remote command:
Start (VCO Characteristics): CONFigure:VCO:SWEep:STARt on page 479
Stop (VCO Characteristics): CONFigure:VCO:SWEep:STOP on page 479
Points (VCO Characteristics): CONFigure:VCO:SWEep:POINts on page 478
Start (Spot Noise vs Tune): CONFigure:SNTune:SWEep:STARt on page 481
Stop (Spot Noise vs Tune): CONFigure:SNTune:SWEep:STOP on page 481
Points (Spot Noise vs Tune): CONFigure:SNTune:SWEep:POINts on page 480
In the VCO characterization measurement, you can select the Trace Mode for each
trace.
Most of the functionality for spot noise vs tune measurements is the same as in the
phase noise measurement. Differences and additional functionality are described in
this section of the documentation.
Refer to the following topics for more information about equivalent functionality.
● Input configuration: Chapter 10.2, "Input Source", on page 125
● Amplitude configuration and diagram scale: Chapter 10.3, "Level Characteristics",
on page 142
● Frequency configuration: Chapter 10.4, "Frequency", on page 146
● Noise configuration: Chapter 10.5.3, "Noise Configuration", on page 152
● Spot noise configuration: Chapter 10.5.5, "Spot Noise Information", on page 161
● Sweep configuration: Chapter 10.8.1, "Sweep Configuration", on page 177
Note: The "Fix Source" and "Frequency Resolution" settings are not available in
the spot noise vs tune measurement.
● DC source configuration: Chapter 10.6.1, "DC Source Configuration", on page 165
● Measurement configuration: Chapter 9.2, "Performing Measurements",
on page 108
● Limit line configuration: Chapter 11.5, "Limit Lines", on page 232
● Marker configuration: Chapter 11.4, "Markers", on page 223
The one notable difference is the trace configuration, as described in this topic.
● Trace Configuration...............................................................................................181
The remote commands required to configure the frequency are described in Chap-
ter 15.6.10.1, "Frequency Configuration", on page 484.
Selecting the measurement mode.............................................................................. 182
Defining the frequency range of the measurement..................................................... 183
Defining a frequency step size.................................................................................... 183
Transient measurement support trigger functionality that allows you to control when a
measurement begins.
Trigger Offset
Defines the time offset between the trigger event and the start of the measurement.
Remote command:
TRIGger[:SEQuence]:HOLDoff[:TIME] on page 490
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.
Remote command:
TRIGger[:SEQuence]:IFPower:HOLDoff on page 490
Example:
The trigger event is a certain frequency on falling slope.
The first trigger event that initiates the measurement occurs. After some time, the trig-
ger frequency again falls below the trigger frequency - this happens several times, until
the DUT is stable.
Without a drop-out time, the R&S FSWP would start a measurement each time the fre-
quency falls below the trigger frequency. With a drop-out time, however, only the first
trigger event initiates a measurement. The other trigger events after the first are
ignored, because the undesired events are within the drop-out time.
Drop-out time
Drop-out time
For the external trigger, the drop-out time defines a minimum duration that the input
signal must stay below the trigger level before triggering again. The dropout time helps
you stabilize triggering when the analyzer is triggering on undesired events.
Remote command:
TRIGger[:SEQuence]:DTIMe on page 489
The remote commands required to configure the data acquisition are described in
Chapter 15.6.10.3, "Data Acquisition", on page 487.
Functions in the "Data Acquisition" dialog box described elsewhere:
● Sweep count: " Sweep/Average Count " on page 157
● Continuous sweep: " Continuous Sweep / Run Cont " on page 110
● Single sweep: " Single Sweep / Run Single " on page 109
● Continue single sweep: " Continue Single Sweep " on page 110
Defining the measurement time.................................................................................. 187
Defining the video bandwidth...................................................................................... 187
The remote commands required to configure the amplitude are described in Chap-
ter 15.6.10.2, "Amplitude Configuration", on page 487.
Functions in the "Amplitude" dialog box described elsewhere:
● RF attenuation: "Attenuating the signal" on page 144
● Input coupling: " Input Coupling " on page 126
Defining a reference level........................................................................................... 187
Because the hardware of the R&S FSWP is adapted according to this value, it is rec-
ommended that you set the reference level close above the expected maximum signal
level.
The reference level is a value between 0 dB, and 30 dBm and is always coupled to the
attenuation. When you turn on auto attenuation, the R&S FSWP selects an attenuation
that results in a nominal signal level of (about) 0 dBm to protect the input mixer.
Remote command:
INPut<1|2>:RLEVel on page 487
The remote commands required to configure the diagram axes are described in Chap-
ter 15.6.10.5, "Y-Axis Scale", on page 491.
Scaling the y-axis of the frequency diagram............................................................... 188
Scaling the y-axis of the phase diagram..................................................................... 189
Selecting the AF coupling mode................................................................................. 189
Positioning the zero-phase..........................................................................................189
You can also define a different position of the zero phase when you select manual
"Zero Phase Ref Pos" mode. For manual zero-phase positioning, define any point on
the x-axis (time value) as the zero-phase position, and the R&S FSWP adjusts the
trace of the phase display accordingly.
Manual selection of the zero-phase position is available for DC AF coupling mode.
Remote command:
Mode: CONFigure:TRANsient[:WINDow<n>]:AF:COUPling:RPOint:MODE
on page 492
Position: CONFigure:TRANsient[:WINDow<n>]:AF:COUPling:RPOint[:X]
on page 493
The remote commands required to configure the settling time calculation are described
in Chapter 15.6.10.6, "Settling Time", on page 495.
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 result displays described here are available for most measurements in the phase
noise application.
Find a list of supported result displays in Chapter 9, "Measurements and Result Dis-
plays", on page 107.
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................................................194
● How to Activate SmartGrid Mode..........................................................................196
● How to Add a New Result Window....................................................................... 196
● How to Close a Result Window.............................................................................197
● How to Arrange the Result Windows.................................................................... 197
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 7-2). 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 in the right-hand corner of the toolbar, 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 Chapter 7.5.2.5,
"How to Arrange the Result Windows", on page 94 for more information on posi-
tioning the window).
Remote command:
LAYout:ADD[:WINDow]? on page 501 / LAYout:WINDow<n>:ADD? on page 507
► To close a window, activate SmartGrid mode and select the "Delete" icon for the
window.
Remote command:
LAYout:REMove[:WINDow] on page 504 / LAYout:WINDow<n>:REMove
on page 508
1. Select an icon from the evaluation bar or the "Move" icon for an existing evaluation
window.
Remote command:
LAYout:REPLace[:WINDow] on page 505 / LAYout:WINDow<n>:REPLace
on page 508
LAYout:MOVE[:WINDow] on page 504
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 511
DISPlay[:WINDow<n>][:SUBWindow<w>]:ZOOM:AREA on page 509
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 511
DISPlay[:WINDow<n>][:SUBWindow<w>]:ZOOM:MULTiple<zn>:AREA
on page 510
Restores the original display, that is, the originally calculated displays for the entire
capture buffer, and closes all zoom windows.
Remote command:
DISPlay[:WINDow<n>][:SUBWindow<w>]:ZOOM[:STATe] on page 511
The remote commands required to zoom into a display are described in Chap-
ter 15.7.2, "Zoom", on page 509.
The following tasks are described here:
● "To zoom into the diagram at one position" on page 200
● "To return to selection mode in the diagram" on page 201
● "To return to original display" on page 201
● "To zoom into multiple positions in the diagram" on page 201
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 200. 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 11-4.
4. Repeat these steps, if necessary, to zoom into further trace areas (up to four).
2. To resize a zoom area, tap directly on the corresponding frame in the overview
window and drag the line to change the size of the frame.
To move a zoom area, tap inside the corresponding frame in the overview window
and drag the frame to the new position.
The contents of the zoom windows are adapted accordingly.
If several measurement are performed one after the other, or continuous measurement
are performed, the trace mode determines how the data for subsequent traces is pro-
cessed. After each measurement, the trace mode determines whether:
● The data is frozen (View)
● The data is hidden (Blank)
● The data is replaced by new values (Clear Write)
● The data is replaced selectively (Max Hold, Min Hold, Average)
Each time the trace mode is changed, the selected trace memory is cleared.
Clear Write Overwrite mode: the trace is overwritten by each measurement. This is the default set-
ting.
All available detectors can be selected.
Max Hold The maximum value is determined over several measurements and displayed. The
R&S FSWP saves the measurement result in the trace memory only if the new value
is greater than the previous one.
Min Hold The minimum value is determined from several measurements and displayed. The
R&S FSWP saves the measurement result in the trace memory only if the new value
is lower than the previous one.
View The current contents of the trace memory are frozen and displayed.
Write Hold The trace is overwritten when new data is available, but only after all cross-correlation
operations defined for a half decade are done.
If a trace is frozen ( "View" mode), the measurement settings, apart from scaling set-
tings, can be changed without impact on the displayed trace. The fact that the dis-
played trace no longer matches the current measurement settings is indicated by a yel-
low asterisk on the tab label.
If you change any parameters that affect the scaling of the diagram axes, the
R&S FSWP automatically adapts the trace data to the changed display range. This
allows you to zoom into the diagram after the measurement to show details of the
trace.
The application provides several methods of trace averaging that you can use sepa-
rately or in any combination.
The order in which averaging is performed is as follows.
1. Cross-correlation
The application performs a certain number of cross-correlation operations in each
half decade.
2. Sweep count.
The application measures the complete measurement range a particular number of
times.
It again includes the cross-correlation operations as defined.
After the measurement over the sweep count is finished, the application displays
the averaged results.
3. Trace smoothing.
Calculates the moving average for the current trace.
Sweep Count
The sweep count defines the number of sweeps that the application performs during a
complete measurements.
A sweep in this context is the measurement over the complete measurement range
once. A complete measurement, however, can consist of more than one sweep. In that
case, the application measures until the number of sweeps that have been defined are
done. The measurement configuration stays the same all the time.
In combination with the average trace mode and cross-correlation operations, the
sweep count averages the trace even more.
Trace Smoothing
(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.
hold, min hold or write hold. For the smoothing process, a median filter is applied on
the logarithmic data.
You can turn trace smoothing on and off for all traces individually and compare, for
example, the raw and the smooth trace.
The median trace smoothing uses a median filter which takes the median value over a
sliding window. The window size can be set in the trace menu in percent of the total
evaluation range. A median filter suppresses outliers while smoothing the underlying
noise curve.
Most phase noise results contain unwanted spurs. Spurs are peak levels at one or
more offset frequencies and are caused mostly by interfering signals. For some appli-
cations, you might want to identify the location of spurs. For other applications, spurs
do not matter in evaluating the results and you might want to remove them from the
trace to get a "smooth" phase noise trace.
Spur display
Usually, spurs are visible on the trace as a peak. In addition, the R&S FSWP draws a
straight, vertical line to represent the position of a spur visually. The length of these
lines indicates the level of the spur in dBc and refers to the scale on the right side of
the phase noise diagram.
The lines indicating a spur are not part of the trace data. When you export the trace, for
example, the spur data is not exported.
Spur data is evaluated in the Spurious List.
Spur suppression
The application allows you to (visually) remove spurs from the trace. Spur removal is
based on an algorithm that detects and completely removes the spurs from the trace
and fills the gaps with data that has been determined mathematically.
The spur removal functionality separates the actual spur power from the underlying
phase noise and displays the latter in a two-stage process. The first stage of spur
detection is based on an eigenvalue decomposition during the signal processing.
Spur threshold
During the second stage, the application uses statistical methods to remove a spur. A
spur is detected, if the level of the signal is above a certain threshold. The spur thresh-
old is relative to an imaginary median trace that the application calculates.
If parts of the signal are identified as spurs, the application removes all signal parts
above that level and substitutes them with the median trace.
traces in the diagram: One for the phase noise, one for the AM noise and the third
showing the sum of the phase noise and AM noise (PN + AM).
Functions in the "Traces" dialog box described elsewhere:
● "Hiding spurs" on page 162
The remote commands required to configure traces are described in Chapter 15.7.3.1,
"Trace Characteristics", on page 512.
Trace Mode
Defines the update mode for subsequent traces.
For details, see Chapter 11.3.1.1, "Analyzing Several Traces - Trace Mode",
on page 203.
"Clear/ Write" Overwrite mode (default): the trace is overwritten by each measure-
ment.
"Max Hold" The maximum value is determined over several measurements and
displayed. The R&S FSWP saves each trace point in the trace mem-
ory only if the new value is greater than the previous one.
Not supported by Spot Noise vs Tune measurements.
"Min Hold" The minimum value is determined from several measurements and
displayed. The R&S FSWP saves each trace point in the trace mem-
ory only if the new value is lower than the previous one.
Not supported by Spot Noise vs Tune measurements.
"Average" The average is formed over several measurements.
"View" The current contents of the trace memory are frozen and displayed.
"Blank" Removes the selected trace from the display.
"Write Hold" The trace is overwritten when new data is available, but only after all
cross-correlation operations defined for a half decade are done. (Or
when the trace cannot be improved further when "XCORR Optimiza-
tion" is on).
Example: 100 cross-correlation operations are defined for a half dec-
ade. The trace is updated when all 100 cross-correlations are done,
not after each individual cross-correlation operation.
Remote command:
DISPlay[:WINDow<n>]:TRACe<t>:MODE on page 512
Smoothing traces
The R&S FSWP allows you to smooth traces and thus remove unwanted anomalies.
You can apply smoothing to all active traces individually (Smoothing "State"), and
define the magnitude of trace smoothing in percent (Smoothing "Value").
The range is from 1% to 20%.
Note: In the spot noise vs tune measurement, trace smoothing properties apply to all
traces.
Remote command:
State: DISPlay[:WINDow<n>]:TRACe<t>:SMOothing[:STATe] on page 517
Value: DISPlay[:WINDow<n>]:TRACe<t>:SMOothing:APERture on page 517
State (SN vs Tune): [SENSe:]SMOothing[:STATe] on page 483
Value (SN vs Tune): [SENSe:]SMOothing:APERture on page 482
Displaying persistence
The term persistence has its origins in cathode ray tube devices (CRTs). It describes
the time period one point on the display stays illuminated after it has been lit by the
cathode ray. The higher the persistence, the longer you could observe the illuminated
point on the display.
In the phase noise application, the persistence defines for how long a trace remains
visible before it fades away. An event that has occurred a single time is visible for up to
8 seconds. As the statistical frequency of an event gets smaller at coordinates with sig-
nal parts that are not constantly there, the trace fades away.
A signal with constant frequency or phase characteristics does not show the effects of
persistence on the trace. When the frequency or phase of a signal change slightly,
however, the effect of persistence becomes visible through color changes or changes
in the shape of the trace.
You can turn on persistence for all traces in the display ("State"). The "Decay" property
defines the time that shadows of past traces remain visible in the display before fading
away. With a decay of 0 s, all past traces remain visible.
When you change a measurement setting, the R&S FSWP resets the persistence
effect.
Persistence is supported by phase noise measurements (CW and pulsed) and the
transient measurement.
Remote command:
DISPlay[:WINDow<n>]:TRACe<t>:PERSistence[:STATe] on page 515
DISPlay[:WINDow<n>]:TRACe<t>:PERSistence:DECay on page 514
Access: "Overview" > "Analysis" > "Traces" > "Trace / Data Export"
The R&S FSWP provides various evaluation methods for the results of a measure-
ment. However, if you want to evaluate the data with external applications, you can
export the measurement data to a standard format file (ASCII or XML).
The following data types can be exported (depending on the application):
● Trace data
● Table results, for example result summaries, marker peak lists.
You can also import existing trace data from a file, for example to compare your latest
measurement results with results that you have saved some time ago.
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.
The standard data management functions (e.g. saving or loading instrument settings)
that are available for all R&S FSWP applications are not described here.
See Chapter 12, "Data Management", on page 244 for a description of the standard
functions.
The remote commands required to import and export traces are described in Chap-
ter 15.7.3.3, "Trace Export and Import", on page 518.
Export all Traces and all Table Results ...................................................................... 210
Include Instrument & Measurement Settings ............................................................. 210
Trace to Export ...........................................................................................................210
Export Trace to ASCII File ..........................................................................................211
└ File Type ...................................................................................................... 212
└ Decimal Separator ....................................................................................... 212
└ Column Separator.........................................................................................212
└ File Explorer..................................................................................................212
Select ASCII File......................................................................................................... 212
Source Window / Source Trace...................................................................................213
Destination Trace........................................................................................................ 213
Import.......................................................................................................................... 213
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.
For details on the file format, see Chapter 11.3.8.1, "Reference: ASCII File Export For-
mat", on page 216.
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 Chapter 4.7, "Protecting Data Using the Secure User Mode",
on page 31.
Remote command:
MMEMory:STORe<n>:TRACe on page 576
Example for tabulator (tab after the last column is not visible):
Type FSWP26
Version 1.80
Date 01.Jan 3000
The selected column separator settings remains the same, even after a preset.
Remote command:
FORMat:DEXPort:CSEParator on page 519
Example:
If you want to import trace 1 of a previously exported noise diagram:
● Select the phase noise measurement and open a noise diagram from the Smart-
Grid.
Importing phase noise trace data into a transient measurement diagram is not pos-
sible.
● Select "Noise Diagram" from the "Source Window" dropdown menu.
● Select "1" from the "Source Trace" dropdown menu.
If you select "All Traces", the R&S FSWP imports all traces of the selected result
type.
Remote command:
MMEMory:LOAD<n>:TRACe on page 521
Destination Trace
The "Destination Trace" dropdown menu becomes available when you select to import
a single trace only.
In that case, you can select the trace number you want to write the trace data to.
If you select a trace that already exists, the trace import overwrites the currently dis-
played trace. Imported traces always get the trace mode "View".
Example:
You have selected trace "1" as the trace you want to import from the "Source Trace"
dropdown menu.
If you select "1: Clear Write" ("Clear Write" indicates the trace is currently displayed)
from the "Destination Trace" dropdown menu, the import overwrites the trace. The
trace mode for trace 1 is replaced by trace mode "View".
If you select "5: Blank" ("Blank" indicates that the trace is currently not displayed) from
the "Destination Trace" dropdown menu, the imports adds a new trace to the diagram
(with trace mode "View". All other traces remain in the diagram.
Remote command:
MMEMory:LOAD<n>:TRACe on page 521
Import
The "Import" button imports the selected trace(s).
THe R&S FSWP does not import numeric results associated with the imported trace
(spot noise, values from the spurious list etc.)
Remote command:
MMEMory:LOAD<n>:TRACe on page 521
The remote commands required to copy traces are described in Chapter 15.7.3.2,
"Trace Copy", on page 518.
Copy Trace .................................................................................................................214
Copy Trace
Access: "Overview" > "Analysis" > "Traces" > "Copy Trace"
Or: [TRACE] > "Copy Trace"
Copies trace data to another trace.
Remote command:
TRACe<n>:COPY on page 518
Figure 11-7: Example: the yellow and blue traces have a label.
You can define trace labels in the "Trace Label" tab of the "Trace" dialog box.
2. Move the trace label to any position on the display by dragging it to the new posi-
tion.
Remote command:
State: DISPlay[:WINDow<n>]:TRACe<t>:LABel[:STATe] on page 513
Label: DISPlay[:WINDow<n>]:TRACe<t>:LABel:TEXT on page 514
The measured trace data and numerical measurement results in tables can be expor-
ted to an ASCII file. For each measurement point, the measured trace position and
value are output. The file is stored with a .DAT extension. For details on the storage
format, see Chapter 11.3.8.1, "Reference: ASCII File Export Format", on page 216.
2. Select "Export all Traces and all Table Results" to export all available measurement
result data for the current application. Alternatively, select a specific "Trace to
Export" .
3. Optionally, select the "Include Instrument & Measurement Settings" option to insert
additional information in the export file header.
4. If necessary, change the decimal separator used in the ASCII export file.
6. In the file selection dialog box, select the storage location and file name for the
export file.
11.3.8 References
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 Chapter 11.3.7.1, "How to Export Trace Data and Numerical Results",
on page 215).
The file consists of the header information (general configuration of the measurement)
and the measurement results. Optionally, the header can be excluded from the file.
The file of the Phase Noise application contains several sections, each section contain-
ing related data as shown in the tables below. Each section can contain header infor-
mation and / or result information (header information is represented by a blue font in
the tables below).
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), followed by the measured data in one or
several columns (depending on the measurement) which are also separated by a sem-
icolon.
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 may
require a different handling of the decimal point. Thus you can define the decimal sep-
arator to be used (decimal point or comma).
Blue font: header data only written to file if header data is exported, too.
Black font: result data is always exported to the file
Half decade configuration (amount of data depends on number of half decades in measurement)
SubSweep;1; Number of half decade
Start;1000.000000;Hz; Start offset frequency of half decade
Stop;3000.000000;Hz; Stop offset frequency of half decade
RBW;30.000000;Hz; Resolution bandwidth applied in half decade
XCORR Count;10; Number of cross-correlation operations in half decade
(…)
Spot noise measurement configuration (amount of data depends on number of spot noise positions)
SpotNoiseDecadeEdges;ON; State of spot noise evaluation on decade edges
SpotNoiseUserDefined;ON; State of user defined spot noise evaluation
SpotNoiseUserDefinedOffset;1; User defined spot noise information
State;ON; State of user defined spot noise information
Offset;500000.000000;Hz; Position of user defined spot noise
(…)
Noise Spectrum measurement results (amount of data depends on the number of phase measurement
windows and the number of traces in each window)
Integrated measurement results (amount of data depends on the number of integration ranges)
Window;3;Integrated Measurements; Number and type of window
Window;Range;Trace; Window and trace number a integration range applies to
Start Offset;Unit; Start offset of the integration range
Stop Offset;Unit; Stop offset of the integration range
Weighting; Name of the weighting filter, if present
Int Noise;Unit; Value for integrated noise
PM;Unit; Value for the Residual PM
FM;Unit; Value for the Residual FM
Jitter;Unit; Value for the jitter
Window;3;Range2;Trace;
(…)
Spot noise measurement results (amount of data depends on the number of spot noise markers)
Window;4;Spot Noise; Number and type of window
Window;Trace; Window and trace number the spot noise marker is positioned in
X-Value;Unit; Position of the spot noise marker
Y-Value;Unit; Spot noise
(…)
Blue font: header data only written to file if header data is exported, too.
Black font: result data is always exported to the file
Frequency Counter
Start offset frequency
Resolution;1.000000000;Hz;
VCO Characterization + SN vs Tune: Results (amount of data depends on evaluated result displays)
Window;1;Frequency; Number and type of window (Frequency, Sensitivity etc.)
Trace;1; Trace number
Trace Mode;CLR/WRITE; Trace mode
Trace Label;ON; State of trace label
Trace Label;LabelDesignation; Trace label
X-Unit;V; Unit of the x-axis
Y-Unit;Hz; Unit of the y-axis
Values;601; Number of measurement points
<x-value>;<y-value>; Results (one value for every measurement point)
(…)
Trace;2;
(…)
Window;2;Power;
(…)
Blue font: header data only written to file if header data is exported, too.
Black font: result data is always exported to the file
11.4 Markers
Markers help you analyze your measurement results by determining particular values
in the diagram. Thus you can extract numeric values from a graphical display.
● Basics on Markers and Marker Functions.............................................................223
● Marker Settings..................................................................................................... 225
● Marker Search Settings and Positioning Functions.............................................. 229
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. R&S FSWP provides 16 markers per display window.
In the Phase Noise application, markers across measurement windows are independ-
ent from each other - thus you can move a marker in one window without moving it in
another window.
● The easiest way to work with markers is using the touchscreen. Simply drag the
marker and drop it at the required position. When a marker label is selected, a ver-
tical 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.
● You can also set an active marker to a new position by defining its position on the
x-axis numerically. When you select the softkey for a marker, an edit dialog box is
displayed.
● The most commonly required marker settings and functions are also available as
softkeys or via the context menu. Tap the marker on the touchscreen 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 set individual markers 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.
Marker types
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).
● Activating Markers.................................................................................................224
● Marker Results...................................................................................................... 224
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.
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.
Window Window the marker is in (only if you have opened more than one Phase Noise dia-
gram)
For more information about marker search, see Chapter 11.4.3, "Marker Search Set-
tings and Positioning Functions", on page 229
● Individual Marker Setup........................................................................................ 226
● General Marker Settings....................................................................................... 228
The remote commands required to define these settings are described in Chap-
ter 15.7.4, "Marker", on page 524.
Selected Marker ......................................................................................................... 226
Marker State ...............................................................................................................226
Marker Position X-value ............................................................................................. 227
Marker Type ............................................................................................................... 227
Reference Marker ...................................................................................................... 227
Linking to Another Marker .......................................................................................... 227
Assigning the Marker to a Trace ................................................................................ 228
Select Marker ............................................................................................................. 228
All Markers Off ............................................................................................................228
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 528
CALCulate<n>:DELTamarker<m>[:STATe] on page 526
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 528
CALCulate<n>:DELTamarker<m>[:STATe] on page 526
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.
Remote command:
CALCulate<n>:DELTamarker<m>:MREFerence on page 526
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 528
CALCulate<n>:DELTamarker<m>[:STATe] on page 526
The remote commands required to define these settings are described in Chap-
ter 15.7.4, "Marker", on page 524.
Marker Table Display ..................................................................................................229
Linked Markers............................................................................................................229
Linked Markers
If enabled, the markers in all diagrams with the same x-axis are linked, i.e. when you
move a marker in one window, the markers in all other windows are moved to the
same x-value.
Remote command:
CALCulate<n>:MARKer<m>:LINK on page 530
Several functions are available to set the marker to a specific position quickly and
easily, or to use the current marker position to define another characteristic value. In
order to determine the required marker position, searches can be performed. The
search results can be influenced by special settings.
Most marker positioning functions and the search settings are available in the [MKR ➙]
menu.
Search settings are also available via the [Marker] key or in the vertical "Marker Con-
fig" tab of the "Analysis" dialog box (horizontal "Search Settings" tab).
● Marker Search Settings.........................................................................................229
● Positioning Functions............................................................................................ 231
The remote commands required to define marker search are described in Chap-
ter 15.7.4.3, "Marker Search", on page 531.
Search Mode for Next Peak ....................................................................................... 230
Peak Excursion .......................................................................................................... 230
Spurious Tracking....................................................................................................... 230
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 60 dB are allowed; the resolution is 0.1 dB. The default setting for
the peak excursion is 1 dB.
For transient measurements, the peak excursion is either a value in Hz (frequency dia-
gram) or rad / deg (phase diagram). The value range is from 0 Hz to 10 MHz (default:
50 kHz) and 0 rad to 10 rad (default: 0.5 rad) respectively.
Remote command:
CALCulate<n>:MARKer<m>:PEXCursion on page 531
Spurious Tracking
Spurs can be unstable regarding their frequency characteristics. In such cases, mark-
ers would not remain on the spur, but on the frequency you have set them on initially.
You can avoid this situation using spurious tracking. Spur tracking makes sure that the
marker remains on the spur, even if the spur changes its frequency. When you turn on
spur tracking, you can define a frequency range within which the R&S FSWP tracks
the spur and adjusts the marker position automatically.
The tracking "Range" defines an area around the marker position and is a function of
the resolution bandwidth (RBW) used in the half decade the marker is in. Note that the
tracking range is dynamic and always relative to the latest marker position, not the ini-
tial marker position.
Example:
You are measuring with an RBW of 10 kHz and place the marker on a spur.
The tracking range is defined as 1 * RBW = 10 kHz.
If the spur changes its position by up to ±10 kHz, the R&S FSWP changes the marker
position along with the spur.
Note that the spurious list contains the tracked spurs and always shows the latest posi-
tion of the spur.
Remote command:
State: CALCulate<n>:MARKer<m>:FUNCtion:SPTRacking[:STATe]
on page 532
Range: CALCulate<n>:MARKer<m>:FUNCtion:SPTRacking:RANGe on page 531
Access: [MKR ➙]
The following functions set the currently selected marker to the result of a peak search
or set other characteristic values to the current marker value.
The remote commands required to position markers are described in Chapter 15.7.4.4,
"Positioning Markers", on page 532.
Peak Search ...............................................................................................................231
Search Next Peak ...................................................................................................... 231
Search Minimum ........................................................................................................ 231
Search Next Minimum ................................................................................................232
Peak Search
Sets the selected marker/delta marker to the maximum of the trace. If no marker is
active, marker 1 is activated.
Remote command:
CALCulate<n>:MARKer<m>:MAXimum[:PEAK] on page 535
CALCulate<n>:DELTamarker<m>:MAXimum[:PEAK] on page 533
Search Minimum
Sets the selected marker/delta marker to the minimum of the trace. If no marker is
active, marker 1 is activated.
Remote command:
CALCulate<n>:MARKer<m>:MINimum[:PEAK] on page 536
CALCulate<n>:DELTamarker<m>:MINimum[:PEAK] on page 534
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 R&S FSWP 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 R&S FSWP 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.
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.
● The entered frequencies or times need not necessarily be selectable in
R&S FSWP. A limit line may also exceed the specified frequency or time range.
The minimum frequency for a data point is -200 GHz, the maximum frequency is
200 GHz. For the time range representation, negative times may also be entered.
The allowed range is -1000 s to +1000 s.
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.
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 232.
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 539
CALCulate<n>:LIMit<li>:UPPer:STATe on page 541
CALCulate<n>:LIMit<li>:ACTive? on page 538
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 541
Comment
An optional description of the limit line.
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 538
Delete Line
Delete the selected limit line configuration.
Remote command:
CALCulate<n>:LIMit<li>:DELete on page 539
Access: "Overview" > "Analysis" > "Lines" > "Limit Lines" > "New" / "Edit" / "Copy To"
or: [LINES] > "Line Config" > "Limit Lines" > "New" / "Edit" / "Copy To"
Name ..........................................................................................................................238
Comment ....................................................................................................................238
X-Axis .........................................................................................................................239
Y-Axis ......................................................................................................................... 239
Data Points .................................................................................................................239
Insert Value ................................................................................................................ 239
Delete Value ...............................................................................................................239
Shift x ......................................................................................................................... 240
Shift y ......................................................................................................................... 240
Save ........................................................................................................................... 240
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 546
Comment
Defines an optional comment for the limit line.
Remote command:
CALCulate<n>:LIMit<li>:COMMent on page 542
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
– V: for VCO Characterization or Spot Noise vs Tune
– mA: for VCO Characterization or Spot Noise vs Tune
● Scaling mode: absolute or relative values
Not supported
● Scaling: linear or logarithmic
Remote command:
CALCulate<n>:LIMit<li>:LOWer:MODE on page 544
CALCulate<n>:LIMit<li>:UPPer:MODE on page 547
CALCulate<n>:LIMit<li>:CONTrol:DOMain on page 543
CALCulate<n>:LIMit<li>:CONTrol:SPACing on page 544
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 center frequency (frequency diagram) or the refer-
ence value (phase diagram).
● Limit type: upper or lower limit; values must stay above the lower limit and below
the upper limit to pass the limit check
Available for transient measurements.
Remote command:
CALCulate<n>:LIMit<li>:UNIT on page 546
CALCulate<n>:LIMit<li>:LOWer:SPACing on page 545
CALCulate<n>:LIMit<li>:UPPer:SPACing on page 547
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 542
CALCulate<n>:LIMit<li>:LOWer[:DATA] on page 544
CALCulate<n>:LIMit<li>:UPPer[:DATA] on page 546
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.
Remote command:
CALCulate<n>:LIMit<li>:CONTrol:SHIFt on page 543
Shift y
Shifts the y-value of each data point vertically by the defined shift width.
Remote command:
CALCulate<n>:LIMit<li>:LOWer:SHIFt on page 545
CALCulate<n>:LIMit<li>:UPPer:SHIFt on page 547
Save
Saves the currently edited limit line under the name defined in the "Name" field.
To deactivate all limit lines at once, select the "Disable All Lines" button.
The limit checks for the deactivated limit lines are stopped and the results are
removed form the display.
3. Edit the line configuration as described in "How to configure a new limit line"
on page 241.
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 241.
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 the "Shift x" or
"Shift y" button and defining the shift width.
2. To shift the complete limit line parallel in the horizontal direction, select the "X-Off-
set" button and enter an offset value.
To shift the complete limit line parallel in the vertical direction, select the "Y-Offset"
button 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 the "Edit" button.
b) In the "Edit Limit Line" dialog box, select the "Shift x" or "Shift y" button and
define the shift width.
12 Data Management
The R&S FSWP 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.
● Restoring the Default Instrument Configuration (Preset)...................................... 244
● Protecting Data Using the Secure User Mode...................................................... 245
● Storing and Recalling Instrument Settings and Measurement Data..................... 247
● Import/Export Functions........................................................................................ 258
● Creating Screenshots of Current Measurement Results and Settings................. 260
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 564
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 R&S FSWP.
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 Microsoft Windows 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 302).
Remote control
Initially after installation of the R&S FSWP-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 Chapter 12.3.2.1, "Stored
Data Types", on page 251). 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.
Note: Saving instrument settings in secure user mode.
Settings that are saved via Quick Save in secure user mode are only available during
the current session. As soon as the power is switched off on the R&S FSWP, the data
is cleared (see Chapter 4.7, "Protecting Data Using the Secure User Mode",
on page 31).
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 562
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................................................................................................ 251
● Storage Location and Filename............................................................................ 252
● Save and Recall Dialog Boxes..............................................................................252
● Startup Recall Settings..........................................................................................255
The following types of data can be stored to and loaded from files via the "Save" dialog
box on the R&S FSWP:
Table 12-1: Items that can be stored to files
Item Description
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.
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 Chapter 12.3.2.2, "Storage Location and
Filename", on page 252.
Comment
An optional description for the data file. A maximum of 60 characters can be displayed.
Remote command:
MMEMory:COMMent on page 554
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 Chapter 12.3.2.1, "Stored Data Types",
on page 251).
Depending on the application, items may or may not be available. For example, saving
spectrogram data is only possible in applications that feature a spectrogram.
Remote command:
MMEMory:SELect[:ITEM]:ALL on page 559
MMEMory:SELect[:ITEM]:DEFault on page 559
MMEMory:SELect[:ITEM]:NONE on page 560
MMEMory:SELect[:ITEM]:HWSettings on page 559
MMEMory:SELect[:ITEM]:LINes:ALL on page 560
MMEMory:SELect[:ITEM]:SGRam on page 560
MMEMory:SELect[:ITEM]:TRACe<1...3>[:ACTive] on page 560
MMEMory:SELect[:ITEM]:TRANsducer:ALL on page 561
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 Chapter 4.7, "Protecting Data Using the Secure User Mode",
on page 31.
Remote command:
MMEMory:STORe<1|2>:STATe on page 563
MMEMory:STORe<1|2>:STATe:NEXT on page 563
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 562
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 Chapter 12.3.2.2, "Storage Location and
Filename", on page 252.
Comment
An optional description for the data file. A maximum of 60 characters can be displayed.
Remote command:
MMEMory:COMMent on page 554
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 Chap-
ter 12.3.2.1, "Stored Data Types", on page 251).
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" .
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 other optional applications.
See the corresponding user manuals for those applications for details.
Import
Access: "Save/Recall" > Import
Provides functions to import data.
Currently, only I/Q data can be imported, and only by applications that process I/Q
data.
See the R&S FSWP I/Q Analyzer user manual for more information.
Export
Access: "Save/Recall" > Export
Opens a submenu to configure data export.
For more information, see " Export Trace to ASCII File " on page 211.
To store data permanently, select an external storage location such as a USB memory
device.
For details, see Chapter 4.7, "Protecting Data Using the Secure User Mode",
on page 31.
To print a screenshot of the current display with the current settings immediately, with-
out switching to the "Print" menu, use the "Print immediately" icon in the toolbar.
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 567
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 263.
Remote command:
HCOPy:ITEM:WINDow<1|2>:TEXT on page 570
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 565
Remote command:
HCOPy:PAGE:COUNt:STATe on page 570
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 263).
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 Chapter 12.5.1.1,
"Print Content Settings", on page 261).
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 Chapter 12.5.1.3,
"Printer Settings", on page 264).
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<1|2>] on page 570
HCOPy[:IMMediate<1|2>]:NEXT on page 570
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 "Print immediately" function, the selected
printing device and its settings determine the behavior of the R&S FSWP.
Destination
Defines the medium to which the printout is output.
"File" Stores the printout to a file in the selected format. The filename is
queried at the time of storage, or a default name is used (see Sup-
press File Name Dialog ).
Multiple windows can only be printed to a file in PDF format. If you
select an image file format, the content setting is automatically set to
Print Screenshot . Page settings are not available for image files;
however, you can configure the colors used for the screenshot (see
Chapter 12.5.1.5, "Print Color Settings", on page 268).
"Clipboard" Copies the printout to the clipboard. Since only single pages can be
copied, only screenshots can be copied to this destination, not multi-
ple windows (see Chapter 12.5.1.1, "Print Content Settings",
on page 261). Page settings are not available; however, you can con-
figure the colors used for the screenshot (see Chapter 12.5.1.5, "Print
Color Settings", on page 268).
If you select the clipboard as the printing destination, the content set-
ting is automatically set to Print Screenshot .
"Printer" Sends the printout to the printer selected from the Printer Name list.
Remote command:
HCOPy:DESTination<1|2> on page 568
HCOPy:DEVice:LANGuage<1|2> on page 569
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 266.
Remote command:
SYSTem:COMMunicate:PRINter:ENUMerate[:NEXT] on page 575
SYSTem:COMMunicate:PRINter:ENUMerate:FIRSt on page 575
SYSTem:COMMunicate:PRINter:SELect<1|2> on page 575
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.
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 266).
Select Device 1/2 ....................................................................................................... 268
Orientation ..................................................................................................................268
Windows Per Page .....................................................................................................268
Scaling ....................................................................................................................... 268
Margins ...................................................................................................................... 268
Orientation
Selects the page orientation of the printout: portrait or landscape.
Remote command:
HCOPy:PAGE:ORIentation<1|2> on page 572
Scaling
Determines the scaling of the windows in the printout if Print Multiple Windows is active
(see Chapter 12.5.1.1, "Print Content Settings", on page 261).
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<1|2>:SCALe on page 573
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<1|2>:BOTTom on page 571
HCOPy:PAGE:MARGin<1|2>:LEFT on page 571
HCOPy:PAGE:MARGin<1|2>:RIGHt on page 571
HCOPy:PAGE:MARGin<1|2>:TOP on page 572
HCOPy:PAGE:MARGin<1|2>:UNIT on page 572
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 287.
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 "Print immediate" icon at the far right end of 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\FSWP_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 press the
"Print immediate" icon at the far right end of 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.
● Alignment.............................................................................................................. 275
● Display Settings.................................................................................................... 281
● Reference Frequency Settings..............................................................................292
● System Configuration Settings..............................................................................296
● Service Functions..................................................................................................303
13.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 276).
The correction data and characteristics required for the alignment are determined by
the firmware. It compares the results at different settings with the known characteristics
of the high-precision calibration signal source at 64 MHz.
During instrument start, the firmware checks whether the installed hardware is suppor-
ted. 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-alignment
fails.
If you start a self-alignment remotely and 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.
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.
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 found correction values according to function/module
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 (as soon as
the instrument has warmed up completely). 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 588).
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 R&S FSWP firmware, you can configure an automatic self-
alignment to be performed directly after installation. In addition, you can activate a pre-
ceding warmup time before self-alignment, which is strongly recommended. If you do
not activate this option, make sure the instrument has reached its operating tempera-
ture 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.
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 586
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 functional test, make sure that the instrument has reached its
operating temperature (for details, refer to the data sheet).
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 functional test, make sure that the instrument has reached its
operating temperature (for details, refer to the data sheet).
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" .
Remote command:
SYSTem:DATE on page 580
SYSTem:TIME on page 580
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 590
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.
Remote command:
DISPlay:SBAR[:STATe] on page 590
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 590
Channel Bar
The channel bar provides information on firmware and measurement settings for a
specific channel.
Remote command:
DISPlay:ANNotation:CBAR on page 589
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 R&S FSWP 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 activate or deactivate the front panel temporarily, press the [F6] key on the external
keyboard (if available) or the remote computer.
For more information, see Chapter 13.2.3, "How to Work with the Soft Front Panels",
on page 291.
Remote command:
SYSTem:DISPlay:FPANel[:STATe] on page 592
Note:
You can also activate 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 592
Theme
The theme defines the colors and style used to display softkeys and other screen
objects.
The default theme is "BlueOcean" .
Remote command:
DISPlay:THEMe:SELect on page 594
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 289).
Remote command:
DISPlay:CMAP<it>:DEFault<ci> on page 592
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 289).
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 566
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 566
Setup ..........................................................................................................................290
Screen Resolution: Restore to Default........................................................................290
Setup
Opens the standard Windows configuration dialog box to configure the used display
devices.
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 activate or deactivate the front panel temporarily, press the [F6] key on the external
keyboard (if available) or on the remote computer.
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 584
SOURce<si>:EXTernal<ext>:ROSCillator:EXTernal:FREQuency
on page 583
For measurements with a start offset > 1 Hz, we recommend that you select a cou-
pling bandwidth of 1 Hz to speed up the settling time of the reference loop.
● When the signal source is on, the R&S FSWP selects a coupling bandwidth of
100 kHz. With this setting the phase noise of the signal source and the receiving
path correlate, which leads to better results measuring additive phase noise on fre-
quency translating DUTs.
Remote command:
State: [SENSe:]ROSCillator:COUPling:MODE on page 582
Bandwidth (mode): [SENSe:]ROSCillator:COUPling:BANDwidth:MODE
on page 581
Bandwidth (value): [SENSe:]ROSCillator:COUPling:BANDwidth on page 581
Remote command:
DIAGnostic:SERVice:HWINfo? on page 602
Remote commands:
SYSTem:FORMat:IDENt on page 604
DIAGnostic:SERVice:BIOSinfo? on page 601
DIAGnostic:SERVice:VERSinfo? on page 602
Install Option
Opens an edit dialog box to enter the license key for the option that you want to install.
Only user accounts with administrator rights are able to install options.
If the number of error messages exceeds the capacity of the error buffer, "Message
Buffer Overflow" is displayed. To clear the message buffer use the "Clear All Mes-
sages" button.
The following information is available:
Remote command:
SYSTem:ERRor:LIST? on page 603
During instrument start, the installed hardware is checked against the current firmware
version to ensure the hardware is supported. If not, an error message is displayed
( "Wrong Firmware Version" ) and you are asked to update the firmware. Until the firm-
ware version is updated, self-alignment fails. To see which components are not suppor-
ted, see the System Messages.
The firmware on your R&S FSWP may also need to be updated in order to enable
additional new features or if reasons for improvement come up. Ask your sales repre-
sentative or check the Rohde&Schwarz website for availability of firmware updates. A
firmware update package includes at least a setup file and release notes.
Before updating the firmware on your instrument, read the release notes delivered with
the firmware version.
Enter the name or browse for the firmware installation file and press the "Install" but-
ton.
Remote command:
SYSTem:FIRMware:UPDate on page 604
2. NOTICE! Stop measurement. The firmware update must not be performed during a
running measurement.
If a measurement is running, stop it by pressing the highlighted [Run Cont] or [Run
Single] key.
Preset Mode
The preset mode selects the application that is started after an instrument preset.
The presettings can be defined in the "Config" tab of the "System Configuration" dialog
box.
For details on operating modes see Chapter 8, "Applications", on page 98.
"SAN" Signal and Spectrum Analyzer mode
(Only when the optional Spectrum application has been installed.)
"MSRA" Multi-Standard Radio Analysis mode
(Only when the optional Spectrum application has been installed.)
"PNO" Phase Noise application
Remote command:
SYSTem:PRESet:COMPatible on page 605
SecureUser Mode
If activated, the R&S FSWP requires a reboot and then automatically logs in using the
"SecureUser" account.
Data that the R&S FSWP normally stores on the solid-state drive is redirected to vola-
tile 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 Chapter 4.7, "Protecting Data Using the
Secure User Mode", on page 31.
Remote command:
SYSTem:SECurity[:STATe] on page 605
Note: Initially after installation of the R&S FSWP-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
displayed, 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 all user
accounts. Although it is possible to continue in secure user mode without changing the
passwords (and you will not be prompted to do so again), it is strongly recommended
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" .
For more helpful information for support, see also Chapter 17.6, "Collecting Information
for Support", on page 635
● R&S Support Information...................................................................................... 304
● Self-test Settings and Results............................................................................... 305
● Calibration Signal Display..................................................................................... 305
● Service Functions..................................................................................................307
● Hardware Diagnostics........................................................................................... 309
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 388
DIAGnostic:SERVice:STESt:RESult? on page 588
Alternatively to the RF input signal from the front panel connector you can use the
instrument's calibration signal as the input signal, for example to perform service func-
tions on.
NONE .........................................................................................................................306
Calibration Frequency RF .......................................................................................... 306
└ Spectrum ......................................................................................................306
└ Frequency .................................................................................................... 306
Calibration Frequency MW .........................................................................................307
Calibration Synthesizer 2 ........................................................................................... 307
NONE
Uses the current RF signal at the input, i.e. no calibration signal (default).
Remote command:
DIAGnostic:SERVice:INPut[:SELect] on page 587
Calibration Frequency RF
Uses the internal calibration signal as the RF input signal.
Remote command:
DIAGnostic:SERVice:INPut[:SELect] on page 587
DIAGnostic:SERVice:INPut:PULSed:CFRequency on page 587
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.
Remote command:
DIAGnostic:SERVice:INPut[:SELect] on page 587
DIAGnostic:SERVice:INPut:MC[:DISTance] on page 587
Calibration Synthesizer 2
This function is used to check the phase noise of the synthesizers on a certain fre-
quency. You can define the frequency in the corresponding input field.
If you enter a frequency on which calibration is not possible, the R&S FSWP uses the
next available frequency.
Available if the R&S FSWP is equipped with the optional hardware and has more than
one synthesizer.
For more information on the calibration process, refer to the service manual.
Remote command:
DIAGnostic:SERVice:INPut[:SELect] on page 587
DIAGnostic:SERVice:INPut:SYNThtwo[:FREQuency] on page 588
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 606
Send
Starts the selected service function.
Remote command:
DIAGnostic:SERVice:SFUNction on page 606
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 R&S FSWP. 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 608
SYSTem:PASSword:RESet on page 608
Clear Results
Clears the result display for all previously performed service functions.
Remote command:
DIAGnostic:SERVice:SFUNction:RESults:DELete on page 607
Save Results
Opens a file selection dialog box to save the results of all previously performed service
functions to a file.
Remote command:
DIAGnostic:SERVice:SFUNction:RESults:SAVE on page 607
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.
For additional information on remote control of spectrum analyzers see the following
application notes available from the Rohde & Schwarz website:
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
The instrument supports different interfaces and protocols for remote control. The fol-
lowing table gives an overview.
Local Area ● HiSLIP High-Speed LAN Instrument Protocol (IVI-6.1) A LAN connector is located on the
Network TCPIP::host address::hislip0[::INSTR] rear panel of the instrument.
(LAN) ● VXI-11
TCPIP::host address::inst0[::INSTR] The interface is based on TCP/IP and
supports various protocols.
Library: VISA
● socket communication (Raw Ethernet, simple Telnet) For a description of the protocols refer
TCPIP::host address[::LAN device name]::<port>:: to:
SOCKET
VXI-11 Protocol
Library: VISA or socket controller
HiSLIP Protocol
Socket Communication
GPIB (IEC/ VISA*) address string: A GPIB bus interface according to the
IEEE Bus GPIB::primary address[::INSTR] IEC 625.1/IEEE 488.1 standard is
Interface) located on the rear panel of the instru-
(no secondary address) ment.
For a description of the interface refer
to 14.1.1.2 GPIB Interface (IEC 625/
IEEE 418 Bus Interface).
*) 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.
(See also Chapter 14.1.3, "VISA Libraries", on page 320).
Within this interface description, the term GPIB is used as a synonym for the IEC/IEEE
bus interface.
VISA library
Instrument access is usually achieved from high level programming platforms using
VISA as an intermediate abstraction layer. VISA encapsulates the low level VXI, GPIB,
LAN or USB function calls and thus makes the transport interface transparent for the
user. See Chapter 14.1.3, "VISA Libraries", on page 320 for details.
The R&S FSWP supports various LAN protocols such as VXI11, RSIB, raw socket or
the newer HiSLIP protocol.
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 newer 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 FSWP26-123456; the valid resource string using HiSLIP is:
TCPIP::FSWP26-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 Chapter 14.4.1, "How to Configure
a Network", on page 363.
● VXI-11 Protocol..................................................................................................... 314
● HiSLIP Protocol.....................................................................................................314
● Socket Communication......................................................................................... 314
● LAN Web Browser Interface..................................................................................315
VXI-11 Protocol
The VXI-11 standard is based on the ONC RPC (Open Network Computing Remote
Procedure Call) protocol which in turn relies on TCP/IP as the network/transport layer.
The TCP/IP network protocol and the associated network services are preconfigured.
TCP/IP ensures connection-oriented communication, where the order of the
exchanged messages is adhered to and interrupted links are identified. With this proto-
col, messages cannot be lost.
HiSLIP Protocol
The HiSLIP (High Speed LAN Instrument Protocol) is the successor protocol for
VXI-11 for TCP-based instruments specified by the IVI foundation. The protocol uses
two TCP sockets for a single connection - one for fast data transfer, the other for non-
sequential control commands (e.g. Device Clear or SRQ).
HiSLIP has the following characteristics:
● High performance as with raw socket network connections
● Compatible IEEE 488.2 support for Message Exchange Protocol, Device Clear,
Serial Poll, Remote/Local, Trigger, and Service Request
● Uses a single IANA registered port (4880), which simplifies the configuration of fire-
walls
● Supports simultaneous access of multiple users by providing versatile locking
mechanisms
● Usable for IPv6 or IPv4 networks
Using VXI-11, each operation is blocked until a VXI-11 device handshake returns. How-
ever, using HiSLIP, data is sent to the device using the "fire and forget" method with
immediate return. Thus, a successful return of a VISA operation such as viWrite()
does not guarantee that the instrument has finished or started the requested com-
mand, but is delivered to the TCP/IP buffers.
Socket Communication
An alternative way for remote control of the software is to establish a simple network
communication using sockets. The socket communication, also referred to as "Raw
Ethernet communication", does not necessarily require a VISA installation on the
remote controller side. It is available by default on all operating systems.
The simplest way to establish socket communication is to use the built-in telnet pro-
gram. The telnet program is part of every operating system and supports a communi-
cation with the software on a command-by-command basis. For more convenience and
to enable automation by means of programs, user-defined sockets can be program-
med.
Socket connections are established on a specially defined port. The socket address is
a combination of the IP address or the host name of the instrument and the number of
the port configured for remote-control. All R&S FSWP use port number 5025 for this
purpose. The port is configured for communication on a command-to-command basis
and for remote control from a program.
If you do not want other users in the LAN to be able to access and operate the
R&S FSWP you can deactivate this function.
See Chapter 14.4.6, "How to Deactivate the Web Browser Interface", on page 373.
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.
The "Device Indicator" button allows you to physically identify the instrument.
This is useful if you have several instruments and want to know which instru-
ment the LAN home page belongs to. To identify the instrument, activate the
"Device Indicator" . Then check the "LAN Status" indicator of the instruments.
– "LAN Configuration" allows you to configure LAN parameters and to initiate a
ping.
(See "Ping Client" on page 368.)
– "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 Chapter 14.4.5, "How to Control the R&S FSWP via the Web Browser Inter-
face", on page 372.)
● "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.
Universal Commands
Universal commands are encoded in the range 10 through 1F hex. They affect all
instruments connected to the bus and do not require addressing.
DCL (Device Clear) Aborts the processing of the commands just received and sets the com-
mand processing software to a defined initial state. Does not change the
instrument settings.
LLO (Local Lockout) The "Local" softkey is disabled. Manual operation is no longer available
until GTL is executed.
*) IFC is not a real universal command, it is sent via a separate line; however, it also affects all instruments
connected to the bus and does not require addressing
Addressed Commands
Addressed commands are encoded in the range 00 through 0F hex. They only affect
instruments addressed as listeners.
GET (Group Execute Trigger) Triggers a previously active instrument function (e.g. a sweep).
The effect of the command is the same as with that of a pulse at
the external trigger signal input.
PPC (Parallel Poll Configure) Configures the instrument for parallel poll.
SDC (Selected Device Clear) Aborts the processing of the commands just received and sets the
command processing software to a defined initial state. Does not
change the instrument setting.
For remote control via the USB connection, the PC and the instrument must be con-
nected via the USB type B interface. A USB connection requires the VISA library to be
installed. VISA detects and configures 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:
FSWP8 11E
FSWP26 11F
FSWP50 120
Example:
USB::0x0AAD::0x0011F::100001::INSTR
0x0AAD is the vendor ID for Rohde & Schwarz
0x0011F is the product ID for the R&S FSWP26
100001 is the serial number of the particular instrument
SCPI commands - messages - are used for remote control. Commands that are not
taken from the SCPI standard follow the SCPI syntax rules. The R&S FSWP supports
the SCPI version 1999. The SCPI standard is based on standard IEEE 488.2 and aims
at the standardization of device-specific commands, error handling and the status reg-
isters. The tutorial "Automatic Measurement Control - A tutorial on SCPI and IEEE
488.2" from John M. Pieper (R&S order number 0002.3536.00) offers detailed informa-
tion on concepts and definitions of SCPI.
Tables provide a fast overview of the bit assignment in the status registers. The tables
are supplemented by a comprehensive description of the status registers.
VISA is a standardized software interface library providing input and output functions to
communicate with instruments. The I/O channel (LAN or TCP/IP, USB, ...) is selected
at initialization time by one of the following:
● The channel–specific address string ("VISA resource string") indicated in
Table 14-1
● An appropriately defined VISA alias (short name).
A VISA installation is a prerequisite for remote control using the following interfaces:
● Chapter 14.1.1.2, "GPIB Interface (IEC 625/IEEE 418 Bus Interface)", on page 317
● Chapter 14.1.1.1, "LAN Interface", on page 312
14.1.4 Messages
The messages transferred on the data lines are divided into the following categories:
● Interface messages
Interface messages are transmitted to the instrument on the data lines, with the
attention line being active (LOW). They are used to communicate between the con-
troller and the instrument. Interface messages can only be sent by instruments that
have GPIB bus functionality. For details see the sections for the required interface.
● Instrument messages
Instrument messages are employed in the same way for all interfaces, if not indica-
ted otherwise in the description. Structure and syntax of the instrument messages
are described in Chapter 14.1.5, "SCPI Command Structure", on page 322. A
detailed description of all messages available for the instrument is provided in the
chapter "Remote Control Commands".
There are different types of instrument messages, depending on the direction they
are sent:
– Commands
– Instrument responses
Commands
Commands (program messages) are messages the controller sends to the instrument.
They operate the instrument functions and request information. The commands are
subdivided according to two criteria:
● According to the effect they have on the instrument:
– Setting commands cause instrument settings such as a reset of the instru-
ment or setting the frequency.
– Queries cause data to be provided for remote control, e.g. for identification of
the instrument or polling a parameter value. Queries are formed by directly
appending a question mark to the command header.
● According to their definition in standards:
– Common commands: their function and syntax are precisely defined in stan-
dard IEEE 488.2. They are employed identically on all instruments (if imple-
mented). They refer to functions such as management of the standardized sta-
tus registers, reset and self-test.
– Instrument control commands refer to functions depending on the features of
the instrument such as frequency settings. Many of these commands have also
been standardized by the SCPI committee. These commands are marked as
"SCPI confirmed" in the command reference chapters. Commands without this
SCPI label are device-specific; however, their syntax follows SCPI rules as per-
mitted by the standard.
Instrument responses
Instrument responses (response messages and service requests) are messages the
instrument sends to the controller after a query. They can contain measurement
results, instrument settings and information on the instrument status.
SCPI commands consist of a header and, in most cases, one or more parameters. The
header and the parameters are separated by a "white space" (ASCII code 0 to 9, 11 to
32 decimal, e.g. blank). The headers may consist of several mnemonics (keywords).
Queries are formed by appending a question mark directly to the header.
The commands can be either device-specific or device-independent (common com-
mands). Common and device-specific commands differ in their syntax.
*ESE EVENT STATUS ENABLE Sets the bits of the event status enable registers.
*ESR? EVENT STATUS QUERY Queries the contents of the event status register.
Not all commands used in the following examples are necessarily implemented in the
instrument. For demonstration purposes only, assume the existence of the following
commands for this section:
● DISPlay[:WINDow<1...4>]:MAXimize <Boolean>
● FORMat:READings:DATA <type>[,<length>]
● HCOPy:DEVice:COLor <Boolean>
● HCOPy:DEVice:CMAP:COLor:RGB <red>,<green>,<blue>
● HCOPy[:IMMediate]
● HCOPy:ITEM:ALL
● HCOPy:ITEM:LABel <string>
● HCOPy:PAGE:DIMensions:QUADrant[<N>]
● HCOPy:PAGE:ORIentation LANDscape | PORTrait
● HCOPy:PAGE:SCALe <numeric value>
● MMEMory:COPY <file_source>,<file_destination>
● SENSE:BANDwidth|BWIDth[:RESolution] <numeric_value>
● SENSe:FREQuency:STOP <numeric value>
● SENSe:LIST:FREQuency <numeric_value>{,<numeric_value>}
Example:
HCOPy:DEVice:COLor ON is equivalent to HCOP:DEV:COL ON.
Case-insensitivity
Upper case and lower case notation only serves to distinguish the two forms in the
manual, the instrument itself is case-insensitive.
Numeric Suffixes
If a command can be applied to multiple instances of an object, e.g. specific channels
or sources, the required instances can be specified by a suffix added to the command.
Numeric suffixes are indicated by angular brackets (<1...4>, <n>, <i>) and are replaced
by a single value in the command. Entries without a suffix are interpreted as having the
suffix 1.
Example:
Definition: HCOPy:PAGE:DIMensions:QUADrant[<N>]
Command: HCOP:PAGE:DIM:QUAD2
This command refers to the quadrant 2.
Optional Mnemonics
Some command systems permit certain mnemonics to be inserted into the header or
omitted. These mnemonics are marked by square brackets in the description. The
instrument must recognize the long command to comply with the SCPI standard. Some
commands are considerably shortened by these optional mnemonics.
Example:
Definition: HCOPy[:IMMediate]
Command: HCOP:IMM is equivalent to HCOP
Numeric Values
Numeric values can be entered in any form, i.e. with sign, decimal point and exponent.
Values exceeding the resolution of the instrument are rounded up or down. The man-
tissa may comprise up to 255 characters, the exponent must lie inside the value range
-32000 to 32000. The exponent is introduced by an "E" or "e". Entry of the exponent
alone is not allowed.
Example:
SENS:FREQ:STOP 1500000 = SENS:FREQ:STOP 1.5E6
Units
For physical quantities, the unit can be entered. If the unit is missing, the basic unit is
used. Allowed unit prefixes are:
● G (giga)
● MA (mega), MOHM, MHZ
● K (kilo)
● M (milli)
● U (micro)
● N (nano)
Example:
SENSe:FREQ:STOP 1.5GHz = SENSe:FREQ:STOP 1.5E9
Some settings allow relative values to be stated in percent. According to SCPI, this unit
is represented by the PCT string.
Example:
HCOP:PAGE:SCAL 90PCT
● INF and NINF: INFinity and negative INFinity (NINF) represent the numeric values
9.9E37 or -9.9E37, respectively. INF and NINF are only sent as instrument respon-
ses.
● NAN: Not A Number (NAN) represents the value 9.91E37. NAN is only sent as a
instrument response. This value is not defined. Possible causes are the division of
zero by zero, the subtraction of infinite from infinite and the representation of miss-
ing values.
Example:
Setting command: SENSe:LIST:FREQ MAXimum
Query: SENS:LIST:FREQ?
Response: 3.5E9
Boolean Parameters
Boolean parameters represent two states. The "ON" state (logically true) is represen-
ted by "ON" or a numeric value 1. The "OFF" state (logically untrue) is represented by
"OFF" or the numeric value 0. The numeric values are provided as the response for a
query.
Example:
Setting command: HCOPy:DEV:COL ON
Query: HCOPy:DEV:COL?
Response: 1
Text Parameters
Text parameters observe the syntactic rules for mnemonics, i.e. they can be entered
using a short or long form. Like any parameter, they have to be separated from the
header by a white space. In the response to a query, the short form of the text is provi-
ded.
Example:
Setting command: HCOPy:PAGE:ORIentation LANDscape
Query: HCOP:PAGE:ORI?
Response: LAND
Character Strings
Strings must always be entered in quotation marks (' or ").
Example:
HCOP:ITEM:LABel "Test1"
HCOP:ITEM:LABel 'Test1'
Block Data
Block data is a format which is suitable for the transmission of large amounts of data.
For example, a command using a block data parameter has the following structure:
FORMat:READings:DATA #45168xxxxxxxx
The ASCII character # introduces the data block. The next number indicates how many
of the following digits describe the length of the data block. In the example the 4 follow-
ing digits indicate the length to be 5168 bytes. The data bytes follow. During the trans-
mission of these data bytes all end or other control signs are ignored until all bytes are
transmitted.
#0 specifies a data block of indefinite length. The use of the indefinite format requires a
NL^END message to terminate the data block. This format is useful when the length of
the transmission is not known or if speed or other considerations prevent segmentation
of the data into blocks of definite length.
The following tables provide an overview of the syntax elements and special charac-
ters.
Table 14-4: Syntax elements
; The semicolon separates two commands of a command line. It does not alter the path.
'' Quotation marks introduce a string and terminate it (both single and double quotation marks are
possible).
"
# The hash symbol introduces binary, octal, hexadecimal and block data.
● Binary: #B10110
● Octal: #O7612
● Hexa: #HF3A7
● Block: #21312
A "white space" (ASCII-Code 0 to 9, 11 to 32 decimal, e.g. blank) separates the header from the
parameters.
| Parameters
A vertical stroke in parameter definitions indicates alternative possibilities in the sense of "or". The
effect of the command differs, depending on which parameter is used.
Example:
Definition:HCOPy:PAGE:ORIentation LANDscape | PORTrait
Command HCOP:PAGE:ORI LAND specifies landscape orientation
Command HCOP:PAGE:ORI PORT specifies portrait orientation
Mnemonics
A selection of mnemonics with an identical effect exists for several commands. These mnemonics are
indicated in the same line; they are separated by a vertical stroke. Only one of these mnemonics
needs to be included in the header of the command. The effect of the command is independent of
which of the mnemonics is used.
Example:
DefinitionSENSE:BANDwidth|BWIDth[:RESolution] <numeric_value>
The two following commands with identical meaning can be created:
SENS:BAND:RES 1
SENS:BWID:RES 1
[] Mnemonics in square brackets are optional and may be inserted into the header or omitted.
Example: HCOPy[:IMMediate]
HCOP:IMM is equivalent to HCOP
{} Parameters in curly brackets are optional and can be inserted once or several times, or omitted.
Example: SENSe:LIST:FREQuency <numeric_value>{,<numeric_value>}
The following are valid commands:
SENS:LIST:FREQ 10
SENS:LIST:FREQ 10,20
SENS:LIST:FREQ 10,20,30,40
Example:
MMEM:COPY "Test1","MeasurementXY";:HCOP:ITEM ALL
This command line contains two commands. The first command belongs to the MMEM
system, the second command belongs to the HCOP system. If the next command
belongs to a different command system, the semicolon is followed by a colon.
Example:
HCOP:ITEM ALL;:HCOP:IMM
This command line contains two commands. Both commands are part of the HCOP
command system, i.e. they have one level in common.
If the successive commands belong to the same system, having one or several levels
in common, the command line can be abbreviated. When abbreviating the command
line, the second command begins with the level below HCOP. The colon after the semi-
colon is omitted. The abbreviated form of the command line reads as follows:
HCOP:ITEM ALL;IMM
Example:
HCOP:ITEM ALL
HCOP:IMM
A new command line always begins with the complete path.
A query is defined for each setting command unless explicitly specified otherwise. It is
formed by adding a question mark to the associated setting command. According to
SCPI, the responses to queries are partly subject to stricter rules than in standard
IEEE 488.2.
● The requested parameter is transmitted without a header.
Example: HCOP:PAGE:ORI?, Response: LAND
● Maximum values, minimum values and all other quantities that are requested via a
special text parameter are returned as numeric values.
Example: SENSe:FREQuency:STOP? MAX, Response: 3.5E9
● Numeric values are output without a unit. Physical quantities are referred to the
basic units or to the units set using the Unit command. The response 3.5E9 in
the previous example stands for 3.5 GHz.
● Truth values (Boolean values) are returned as 0 (for OFF) and 1 (for ON).
Example:
Setting command: HCOPy:DEV:COL ON
Query: HCOPy:DEV:COL?
Response: 1
● Text (character data) is returned in a short form.
Example:
Setting command: HCOPy:PAGE:ORIentation LANDscape
Query: HCOP:PAGE:ORI?
Response: LAND
● Invalid numerical results
In some cases, particularly when a result consists of multiple numeric values, inva-
lid values are returned as 9.91E37 (not a number).
*OPC Sets the Operation Complete bit in the ESR ● Setting bit 0 in the ESE
after all previous commands have been exe- ● Setting bit 5 in the SRE
cuted. ● Waiting for service request (SRQ)
*OPC? Stops command processing until 1 is Send *OPC? directly after the command
returned. This occurs when all pending opera- whose processing must be terminated before
tions are completed. other commands can be executed.
*WAI Stops further command processing until all Send *WAI directly after the command whose
commands sent before *WAI have been exe- processing must be terminated before other
cuted. commands are executed.
2. Set bit no. 5 in the SRE: *SRE 32 to enable ESB service request.
3. Poll the operation complete state periodically (with a timer) using the sequence:
*OPC; *ESR?
A return value (LSB) of 1 indicates that the overlapped command has finished.
The status reporting system stores all information on the current operating state of the
instrument, and on errors which have occurred. This information is stored in the status
registers and in the error queue. Both can be queried via GPIB bus or LAN interface
(STATus... commands.
(See Chapter 15.10, "Using the Status Register", on page 614).
● Hierarchy of Status Registers............................................................................... 332
● Structure of a SCPI Status Register......................................................................334
● Contents of the Status Registers.......................................................................... 335
● Application of the Status Reporting System..........................................................346
● Reset Values of the Status Reporting System...................................................... 348
15 not used 15 not used 15 not used 15 not used 15 not used 15 not used
& logic AND
of all bits 14 14 14 14 14 14
logic OR
13 13 13 13 13 13
*) one register for each channel
12 12 12 12 12 12
Red font: Phase Noise application only
11 11 11 11 11 11
Blue font: Spectrum application only
Analog Demodulator and I/Q Analyzer = 10 Range completed 10 10 10 10 10
Spectrum mode
9 9 9 9 9 9
8 HCOPy in progress 8 8 8 8 8
7 7 7 CACLR FAIL 7 LMARgin 8 FAIL 7 LIMit 8 FAIL 7
6 6 6 ALT3...11 LOWer/UPPer FAIL 6 LMARgin 7 FAIL 6 LIMit 7 FAIL 6
5 Waiting for TRIGger 5 5 ALT2 LOWer FAIL 5 LMARgin 6 FAIL 5 LIMit 6 FAIL 5
4 MEASuring 4 4 ALT2 UPPer FAIL 4 LMARgin 5 FAIL 4 LIMit 5 FAIL 4
3 SWEeping 3 3 ALT1 LOWer FAIL 3 LMARgin 4 FAIL 3 LIMit 4 FAIL 3
2 2 PULSe not found 2 ALT1 UPPer FAIL 2 LMARgin 3 FAIL 2 LIMit 3 FAIL 2 Vaux too high
1 1 SIGnal not found 1 ADJ LOWer FAIL 1 LMARgin 2 FAIL 1 LIMit 2 FAIL 1 Vtune too high
SRQ
0 CALibrating 0 0 ADJ UPPer FAIL 0 LMARgin 1 FAIL 0 LIMit 1 FAIL 0 Vsupply/ Isupply too high
STATus:OPERation STAT:QUES:PNOise *) STAT:QUES:ACPLimit *) STAT:QUES:LMARgin<n> *) STAT:QUES:LIMit<n> *) STAT:QUES:POW:DCPN *)
& 7
6 RQS/MSS
& 5 ESB
& 4 MAV
15 not used 15 not used 15 not used
& 3 15 not used
14 DCPNoise
& 2 14
9 9
1 13 PNOise
8 External REFerence 8 8
0 12 ACPLimit
7 7 7
SRE STB 11
6 6 6
10 LMARGin
5 5 5
9 LIMit
4 4 4
8 CALibration (=UNCAL)
3 3 3 INPut_overload
& 7
2 2 2 IF_OVerload
& 6
1 LO UNLocked 1 1 UNDerload
& 5 FREQuency
0 OVEN COLD 0 Frontend temp. error 0 OVERload
& 4 TEMPerature
STAT:QUES:FREQuency *) STAT:QUES:TEMPerature *) STAT:QUES:POWer *)
& 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
Figure 14-2: Graphical overview of the R&S FSWP status registers hierarchy
● STB, SRE
The STatus Byte (STB) register and its associated mask register Service Request
Enable (SRE) form the highest level of the status reporting system. The STB pro-
vides a rough overview of the instrument status, collecting the information of the
lower-level registers.
● ESR, SCPI registers
The STB receives its information from the following registers:
– The Event Status Register (ESR) with the associated mask register standard
Event Status Enable (ESE).
– The STATus:OPERation and STATus:QUEStionable registers which are
defined by SCPI and contain detailed information on the instrument.
● IST, PPE
The IST flag ("Individual STatus"), like the SRQ, combines the entire instrument
status in a single bit. The PPE fulfills the same function for the IST flag as the SRE
for the service request.
● Output buffer
The output buffer contains the messages the instrument returns to the controller. It
is not part of the status reporting system but determines the value of the MAV bit in
the STB and thus is represented in the overview.
All status registers have the same internal structure.
SRE, ESE
The service request enable register SRE can be used as ENABle part of the STB if the
STB is structured according to SCPI. By analogy, the ESE can be used as the ENABle
part of the ESR.
Each standard SCPI register consists of 5 parts. Each part has a width of 16 bits and
has different functions. The individual bits are independent of each other, i.e. each
hardware status is assigned a bit number which is valid for all five parts. Bit 15 (the
most significant bit) is set to zero for all parts. Thus the contents of the register parts
can be processed by the controller as positive integers.
Sum bit
The sum bit is obtained from the EVENt and ENABle part for each register. The result
is then entered into a bit of the CONDition part of the higher-order register.
The instrument automatically generates the sum bit for each register. Thus an event
can lead to a service request throughout all levels of the hierarchy.
In the following sections, the contents of the status registers are described in more
detail.
● Status Byte (STB) and Service Request Enable Register (SRE)..........................336
● IST Flag and Parallel Poll Enable Register (PPE)................................................ 337
● Event Status Register (ESR) and Event Status Enable Register (ESE)............... 337
● STATus:OPERation Register................................................................................ 338
● STATus:QUEStionable Register............................................................................339
● STATus:QUEStionable:ACPLimit Register............................................................340
● STATus:QUEStionable:EXTended Register.......................................................... 341
● STATus:QUEStionable:EXTended:INFO Register................................................ 341
● STATus:QUEStionable:FREQuency Register....................................................... 342
● STATus:QUEStionable:LIMit Register...................................................................342
● STATus:QUEStionable:LMARgin Register............................................................343
● STATus:QUEStionable:POWer Register...............................................................344
● STATus:QUEStionable:POWer:DCPNoise........................................................... 344
● STATus:QUEStionable:PNOise.............................................................................345
● STATus:QUEStionable:TEMPerature Register..................................................... 345
● STATus:QUEStionable:TIMe Register.................................................................. 346
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.
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 14-8: 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.
STATus:OPERation Register
The STATus:OPERation register contains information on current activities of the
R&S FSWP. It also contains information on activities that have been executed since
the last read out.
Table 14-9: Meaning of the bits used in the STATus:OPERation register
0 CALibrating
This bit is set as long as the instrument is performing a calibration.
3 SWEeping
Sweep is being performed in base unit (applications are not considered); identical to bit 4
Available in the optional Spectrum application.
4 MEASuring
Measurement is being performed in base unit (applications are not considered); identical to bit 3
Available in the optional Spectrum application.
8 HardCOPy in progress
This bit is set while the instrument is printing a hardcopy.
9 Not used
10 Range completed
This bit is set when a range in the sweep list has been completed if "Stop after Range" has
been activated.
Available in the optional Spectrum application.
STATus:QUEStionable Register
The STATus:QUEStionable register contains information on instrument states that do
not meet the specifications.
You can read out the register with STAT:QUES:COND or STAT:QUES:EVEN.
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-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.
Available in the optional Spectrum application.
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 R&S FSWP is unaligned ("UNCAL" display)
9 LIMit
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
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.
Available in the optional Spectrum application.
11 SYNC (device-specific)
This bit is set if the R&S FSWP is not synchronized to the signal that is applied.
The R&S FSWP is not synchronized if the results deviate too much from the expected value
during premeasurements
12 ACPLimit
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.
Available in the optional Spectrum application.
13 PNOise
This bit is set if an event occurs in the Phase Noise measurement.
The "STATus:QUEStionable:PNOise" on page 345 provides more information on the event
type.
STATus:QUEStionable:ACPLimit Register
Available for the Spectrum application.
The STATus:QUEStionable:ACPLimit register contains information about the results of
a limit check during ACLR measurements. A separate ACPLimit register exists for
each active channel.
You can read out the register with STATus:QUEStionable:ACPLimit:CONDition?
or STATus:QUEStionable:ACPLimit[:EVENt]?
Table 14-11: Meaning of the bits used in the STATus:QUEStionable:ACPLimit register
7 CACLR FAIL
This bit is set if the CACLR limit is exceeded in one of the gap channels.
9 to 14 Unused
STATus:QUEStionable:EXTended Register
The STATus:QUEStionable:EXTended register contains further status information
not covered by the other status registers of the R&S FSWP. A separate EXTended reg-
ister exists for each active channel.
You can read out the register with STATus:QUEStionable:EXTended:CONDition?
or STATus:QUEStionable:EXTended[:EVENt]?
Table 14-12: Meaning of the bits used in the STATus:QUEStionable:EXTended register
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
Register.
2 to 14 Unused
STATus:QUEStionable:EXTended:INFO Register
The STATus:QUEStionable:EXTended:INFO register contains information on the
type of messages that occur during operation of the R&S FSWP. A separate INFO reg-
ister exists for each active channel.
You can read out the register with STATus:QUEStionable:EXTended:INFO:
CONDition? or STATus:QUEStionable:EXTended:INFO[:EVENt]?. You can
query all messages that occur for a specific channel using the command SYSTem:
ERRor:EXTended? on page 603.
Table 14-13: Meaning of the bits used in the STATus:QUEStionable:EXTended:INFO register
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
STATus:QUEStionable:FREQuency Register
The STATus:QUEStionable:FREQuency register contains information about the condi-
tion of the local oscillator and the reference frequency. A separate frequency register
exists for each active channel.
You can read out the register with STATus:QUEStionable:FREQuency:
CONDition? or STATus:QUEStionable:FREQuency[:EVENt]?.
Table 14-14: Meaning of the bits used in the STATus:QUEStionable:FREQuency register
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
STATus:QUEStionable:LIMit Register
The STATus:QUEStionable:LIMit register contains information about the results of a
limit check when you are working with limit lines.
A separate LIMit register exists for each active channel and for each window.
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
STATus:QUEStionable:LMARgin Register
This register contains information about the observance of limit margins.
A separate LMARgin register exists for each active channel and for each window.
It can be read using the commands
STATus:QUEStionable:LMARgin:CONDition? and
STATus:QUEStionable:LMARgin[:EVENt]?.
Table 14-16: Meaning of the bits used in the STATus:QUEStionable:LMARgin register
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
STATus:QUEStionable:POWer Register
The STATus:QUEStionable:POWer register contains information about possible
overload situations that may occur during operation of the R&S FSWP. A separate
power register exists for each active channel.
You can read out the register with STATus:QUEStionable:POWer:CONDition? or
STATus:QUEStionable:POWer[:EVENt]?
Table 14-17: Meaning of the bits used in the STATus:QUEStionable:POWer register
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 R&S FSWP displays the keyword "RF OVLD".
1 Unused
2 IF_OVerload
This bit is set if an overload occurs in the IF path.
The R&S FSWP displays the keyword "IF 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.
The R&S FSWP displays the keyword "INPUT OVLD".
(Available with the optional Spectrum application.)
4 to 13 Unused
14 DCPNoise
This bit is set in case of an event at the DC power supply.
For more information see "STATus:QUEStionable:POWer:DCPNoise" on page 344.
STATus:QUEStionable:POWer:DCPNoise
Available for the phase noise application.
0 Vsupply / Isupply
This bit is set if something is wrong with the voltage or current supply.
1 Vtune
This bit is set if something is wrong with the tuning voltage supply.
2 Vaux
This bit is set if something is wrong with the auxiliary voltage supply.
3 to 14 Unused
STATus:QUEStionable:PNOise
Available for the phase noise application.
The STATus:QUEStionable:PNOise register contains information about the state and
condition of the phase noise application. A separate PNOise register exists for each
active channel.
You can read out the register with STATus:QUEStionable:PNOise:CONDition?
on page 615 or STATus:QUEStionable:PNOise[:EVENt]? on page 616.
Table 14-19: Meaning of the bits used in the STATus:QUEStionable:PNOise register
0 Unused
3 to 14 Unused
STATus:QUEStionable:TEMPerature Register
The STATus:QUEStionable:TEMPerature register contains information about possible
temperature deviations that may occur during operation of the R&S FSWP. A separate
temperature register exists for each active channel.
You can read out the register with STATus:QUEStionable:TEMPerature:
CONDition? or STATus:QUEStionable:TEMPerature[:EVENt]?
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 276.
1 to 14 Unused
STATus:QUEStionable:TIMe Register
Available for the Spectrum application.
The STATus:QUEStionable:TIMe register contains information about possible time
errors that may occur during operation of the R&S FSWP. A separate time register
exists for each active channel.
Table 14-21: Meaning of the bits used in the STATus:QUEStionable:TIMe register
0 not used
2 to 14 Unused
The purpose of the status reporting system is to monitor the status of one or several
devices in a measuring system. To do this and react appropriately, the controller must
receive and evaluate the information of all devices. The following standard methods
are used:
● Service request (SRQ) initiated by the instrument
● Serial poll of all devices in the bus system, initiated by the controller in order to
find out who sent a SRQ and why
● Parallel poll of all devices
● Query of a specific instrument status by means of commands
● Query of the error queue
Service Request
Under certain circumstances, the instrument can send a service request (SRQ) to the
controller. A service request is a request from an instrument for information, advice or
treatment by the controller. Usually this service request initiates an interrupt at the con-
troller, to which the control program can react appropriately. As evident from Fig-
ure 14-2, an SRQ is always initiated if one or several of bits 2, 3, 4, 5 or 7 of the status
byte are set and enabled in the SRE. Each of these bits combines the information of a
further register, the error queue or the output buffer. The ENABle parts of the status
registers can be set such that arbitrary bits in an arbitrary status register initiate an
SRQ. In order to make use of the possibilities of the service request effectively, all bits
should be set to "1" in enable registers SRE and ESE.
The service request is the only possibility for the instrument to become active on its
own. Each controller program should cause the instrument to initiate a service request
if errors occur. The program should react appropriately to the service request.
Serial Poll
In a serial poll, just as with command *STB, the status byte of an instrument is queried.
However, the query is realized via interface messages and is thus clearly faster.
The serial poll method is defined in IEEE 488.1 and used to be the only standard pos-
sibility for different instruments to poll the status byte. The method also works for
instruments which do not adhere to SCPI or IEEE 488.2.
The serial poll is mainly used to obtain a fast overview of the state of several instru-
ments connected to the controller.
Parallel Poll
In a parallel poll, up to eight instruments are simultaneously requested by the controller
using a single command to transmit 1 bit of information each on the data lines, i.e., to
set the data line allocated to each instrument to a logical "0" or "1".
In addition to the SRE register, which determines the conditions under which an SRQ
is generated, there is a Parallel Poll Enable register (PPE) which is ANDed with the
STB bit by bit, considering bit 6 as well. This register is ANDed with the STB bit by bit,
considering bit 6 as well. The results are ORed, the result is possibly inverted and then
sent as a response to the parallel poll of the controller. The result can also be queried
without parallel poll using the command *IST?.
The instrument first has to be set for the parallel poll using the command PPC. This
command allocates a data line to the instrument and determines whether the response
is to be inverted. The parallel poll itself is executed using PPE.
The parallel poll method is mainly used to find out quickly which one of the instruments
connected to the controller has sent a service request. To this effect, SRE and PPE
must be set to the same value.
Example:
The decimal value 40 = 32 + 8 indicates that bits no. 3 and 5 in the status register (e.g.
the QUEStionable status summary bit and the ESB bit in the STatus Byte ) are set.
Error Queue
Each error state in the instrument leads to an entry in the error queue. The entries of
the error queue are detailed plain text error messages that can be looked up in the
Error Log or queried via remote control using SYSTem:ERRor[:NEXT]?. Each call of
SYSTem:ERRor[:NEXT]? provides one entry from the error queue. If no error mes-
sages are stored there any more, the instrument responds with 0, "No error".
The error queue should be queried after every SRQ in the controller program as the
entries describe the cause of an error more precisely than the status registers. Espe-
cially in the test phase of a controller program the error queue should be queried regu-
larly since faulty commands from the controller to the instrument are recorded there as
well.
The following table contains the different commands and events causing the status
reporting system to be reset. None of the commands, except *RST and
1) The first command in a command line that immediately follows a <PROGRAM MESSAGE TERMINA-
TOR> clears the output buffer.
Command sequence
As a general rule, send commands and queries in different program messages. Other-
wise, the result of the query may vary depending on which operation is performed first
(see also Chapter 14.1.6.1, "Preventing Overlapping Execution", on page 331).
Reacting to malfunctions
The service request is the only possibility for the instrument to become active on its
own. Each controller program should instruct the instrument to initiate a service
request in case of malfunction. The program should react appropriately to the service
request.
Error queues
The error queue should be queried after every service request in the controller pro-
gram as the entries describe the cause of an error more precisely than the status regis-
ters. Especially in the test phase of a controller program the error queue should be
queried regularly since faulty commands from the controller to the instrument are
recorded there as well.
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
R&S FSWP User Manuals.
Starting IECWIN
IECWIN is available from the Windows "Start" menu on the R&S FSWP, or by execut-
ing the following file:
C:\Program Files (x86)\Rohde-Schwarz\FSWP\<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 R&S FSWP you
want to control. If you are using the tool directly on the R&S FSWP, 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.
The remote commands required to define these settings are described in Chap-
ter 15.9.5, "Configuring Network and Remote Control", on page 595.
Step-by-step instructions are provided in Chapter 14.4, "How to Set Up a Network and
Remote Control", on page 362.
● General Network Settings..................................................................................... 352
● GPIB Settings........................................................................................................354
● Compatibility Settings............................................................................................357
● LAN Settings......................................................................................................... 358
● Remote Errors.......................................................................................................360
● Returning to Manual Mode ("Local")..................................................................... 361
Network settings can only be edited in the firmware if a LAN cable is connected to the
R&S FSWP.
Computer Name..........................................................................................................353
IP Address...................................................................................................................354
Subnet Mask............................................................................................................... 354
DHCP.......................................................................................................................... 354
Network Configuration.................................................................................................354
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 FSWP26-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 596
Identification String
Defines the identification string for the R&S FSWP which is provided as a response to
the *IDN? query. Maximum 36 characters are allowed.
Remote command:
SYSTem:IDENtify[:STRing] on page 598
Remote command:
SYSTem:IDENtify:FACTory on page 598
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 596
*IDN Format
Defines the response format to the remote command *IDN? (see *IDN?
on page 386). This function is intended for re-use of existing control programs
together with the R&S FSWP.
"Leg" Legacy format, as in the R&S FSP/FSU/FSQ family.
"New" R&S FSWP format.
Remote command:
SYSTem:FORMat:IDENt on page 604
I/O Logging
Activates or deactivates the SCPI error log function. All remote control commands
received by the R&S FSWP 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 580
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 Chapter 14.3.5, "Remote Errors", on page 360).
Remote command:
SYSTem:ERRor:DISPlay on page 597
SYSTem:ERRor:CLEar:REMote on page 597
The R&S FSWP supports different system languages that are compatible to other
products.
Note that aside from the "Language" feature (and for PSA compatibility, the "Wide-
band" feature), all other functions in this dialog are currently not supported.
Language.................................................................................................................... 358
Wideband.................................................................................................................... 358
Language
Defines the system language used to control the instrument.
The following languages are supported.
● SCPI
● 5052
For a list of supported commands, see Chapter 15.9.8, "Reference: Command Set
of 5052 Emulation", on page 608.
● PSA
For a list of supported commands, see Chapter 15.9.9, "Reference: Command Set
of Emulated PSA Models", on page 610.
The 5052 language is only available in the Phase Noise application. If you select the
5052 mode in an application other than the Phase Noise application, the R&S FSWP
automatically closes all applications and opens one channel with the Phase Noise
application.
The PSA language is only available for the Spectrum application. If you select the PSA
mode in an application other than the Spectrum application, the R&S FSWP automati-
cally closes all applications and opens one channel with the Spectrum application.
Remote command:
SYSTem:LANGuage on page 598
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 599
LAN Password
Password for LAN configuration. The default password is LxiWebIfc.
Remote command:
SYSTem:LXI:PASSword on page 599
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 599
Access: [SETUP] > "Network + Remote" > "Remote Errors " tab
The error messages generated by the R&S FSWP during remote operation are dis-
played here.
The messages are displayed in the order of their occurrence; the most recent mes-
sages are placed at the top of the list.
The most recent error message during remote operation can be displayed on the
screen, see "Display Remote Errors" on page 357.
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 the "Clear Error List" button. It is automatically cleared when the R&S FSWP
is shut down.
The following information is available:
Remote command:
SYSTem:ERRor:LIST? on page 603
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 except the [PRESET] key are dis-
abled. The "LOCAL" softkey and the Remote Display Update softkey are displayed.
Local
The instrument switches from remote to manual operation, but only if the local lockout
function has not been activated in the remote control mode (see "GPIB Interface Mes-
sages" on page 317).
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 the "LOCAL" softkey, 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 the "LOCAL" softkey is pressed.
Note: Before you switch back to manual operation, all remote command processing
must be completed. Otherwise, the instrument will switch back to remote control imme-
diately.
If you select the "Local" softkey 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.
Remote command:
SYSTem:KLOCk on page 598
Remote operation
You can operate the instrument remotely from a connected computer using SCPI com-
mands (see Chapter 14.1.2, "SCPI (Standard Commands for Programmable Instru-
ments)", on page 320). Before you send remote commands you must configure the
instrument in a LAN network or connect it to a PC via the GPIB interface as described
in Chapter 14.4.1, "How to Configure a Network", on page 363.
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 R&S FSWP ideally meets requirements
for use in production. The computer that is used for remote operation is called "control-
ler" 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 R&S FSWP. For details refer to the Microsoft Windows operating system documen-
tation.
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. This means that it is safe to establish a
physical connection to the LAN without any previous instrument configuration.
When a DHCP server is used, a new IP address may be assigned each time the PC is
restarted. This address must first be determined on the PC itself. Thus, when using a
DHCP server, it is recommended that you use the permanent computer name, which
determines the address via the DNS server (see "Using a DNS server to determine the
IP address" on page 365).
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 DHCP is changed from "On" to "Off", the previously set IP address
and subnet mask are retrieved.
If DHCP is "On", the IP address of the DHCP server is obtained automatically. The
configuration is saved, and you are prompted to restart the instrument. You can
skip the remaining steps.
Note: When a DHCP server is used, a new IP address may be assigned each time
the instrument is restarted. This address must first be determined on the instrument
itself. Thus, when using a DHCP server, it is recommended that you use the per-
manent computer name, which determines the address via the DNS server
(See "Using a DNS server to determine the IP address" on page 365 and Chap-
ter 14.4.1.3, "How to Change the Instrument Name", on page 366).
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.
2. Press the [Setup] key and then the "Network + Remote" softkey.
3. In the "Network" tab, select the "Open Dialog 'Network Connections'" button.
5. In the "Local Area Connection Status" dialog box, select the "Properties" button.
The items used by the LAN connection are displayed.
6. Tap the entry named "Internet Protocol Version 4 (TCP/IPv4)" to highlight it.
8. On the "General" tab, select "Use the following DNS server addresses" and enter
your own DNS addresses.
For more information refer to the Microsoft Windows operating system Help.
In a LAN that uses a DNS server (Domain Name System server), each PC or instru-
ment 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.
This is especially useful when a DHCP server is used, as a new IP address may be
assigned each time the instrument is restarted.
Each instrument is delivered with an assigned computer name, but this name can be
changed.
2. Enter the new computer name and close the dialog box.
The configuration is saved, and you are prompted to restart the instrument.
14.4.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.
► Press the "Device Indicator" button on the "Instrument Home Page" to activate or
deactivate the "LAN" status icon on the status bar of the R&S FSWP. A green
"LAN" status symbol indicates that a LAN connection has been 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 "Device Indica-
tor" setting is not password-protected.
The most important control elements in the navigation pane of the browser interface
are the following:
● "LAN Configuration" opens the menu with configuration pages.
● "Status" displays information about the "LAN" status of the instrument.
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.
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:
1. Enable "ICMP Ping" on the "Advanced LAN Configuration" page (enabled after an
LCI).
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".
In order 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
Microsoft Windows requires that users identify themselves by entering a user name
and password in a login window. You can set up two types of user accounts, either an
administrator 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 automati-
cally 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 Microsoft Win-
dows for any user at any time. Some administrative tasks require administrator rights
(e.g. firmware updates or the configuration of a LAN network).
Refer to Chapter 13, "General Instrument Setup", on page 275 to find out which func-
tions are affected.
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 R&S FSWP and in the network, the password must be adapted to the
network 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.
5. Enter the new password in the upper text line and repeat it in the following line.
6. Press [Enter].
The new password is now active.
The auto-login function is reactivated. It will be applied the next time the instrument
is switched on.
Sharing directories makes data available for other users. This is only possible in Micro-
soft networks. Sharing is a property of a file or directory.
1. In the "Start" menu, select "Programs", "Accessories" and then select "Windows
Explorer".
4. Select a user from the list or add a new name and select the "Add" button.
14.4.5 How to Control the R&S FSWP via the Web Browser Interface
Via the LAN web browser interface to the R&S FSWP, one or more users can control
the instrument remotely from another PC without additional installation. Most instru-
ment controls are available via the front panel simulation. File upload and download
between the instrument and the remote PC is also available.
2. Enter the IP address of the R&S FSWP in the browser's address bar.
The R&S FSWP's Welcome page is displayed.
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
those that contain user data, as well as the top-most My Computer folder, from
which you can access all other folders on the instrument.
3. To download a file from the R&S FSWP, select the file from the displayed folders
and then select "Download File".
If you want to prevent other users in the LAN from accessing or operating the
R&S FSWP 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 R&S FSWP is possi-
ble.
With Microsoft Windows, 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 Microsoft Windows operating system documentation.
With the factory settings, the default "instrument" user can connect to the R&S FSWP
with the Remote Desktop program of the controller immediately. No further configura-
tion 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
R&S FSWP.
14.4.7.1 How to Configure the R&S FSWP for Remote Operation via Remote Desktop
1. Create a fixed IP address for the TCP/IP protocol as described in Chapter 14.4.1.2,
"How to Assign the IP Address", on page 364.
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 R&S FSWP
via Remote Desktop.
2.
Select the "Windows" icon in the toolbar to access the operating system.
6. Define which users are to be given access to the R&S FSWP via Remote Desktop.
Note: The user account under which configuration is carried out is automatically
enabled for Remote Desktop.
7. The R&S FSWP is now ready for connection setup with the Remote Desktop pro-
gram 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 for enabling printers, local drives and serial inter-
faces.
8. If you will need to access drives of the controller from the R&S FSWP (e.g. in order
to store settings or to copy files from the controller to the R&S FSWP), select
"More", then enable the "Drives" option.
Windows will then map drives of the controller to the corresponding network drives.
9. To use printers connected to the controller while accessing them from the
R&S FSWP, activate the "Printers" option. Do not change the remaining settings.
11. Under "Remote desktop size", you can set the size of the R&S FSWP 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 R&S FSWP will appear
at the top edge of the screen. You can use this bar to reduce, minimize or close
the window.
● If deactivated, the only way you can return to the controller desktop from the
R&S FSWP screen in full screen mode is to select "Disconnect" from the
"Start" menu.
6. If the "Disk drives" option is activated on the "Local Resources" tab, a warning is
displayed indicating that the drives are enabled for access from the R&S FSWP.
Select "OK" to confirm the warning.
The firmware restarts and then automatically opens the "Soft Front Panel", i.e. the
user interface on which all front panel controls and the rotary knob are mapped to
buttons.
For more information see Chapter 13.2.3, "How to Work with the Soft Front Pan-
els", on page 291.
The Windows "Start" menu can be made available by expanding the "Remote
Desktop" window to full size.
During the connection with the controller, the login entry is displayed on the
R&S FSWP screen.
Follow the instructions above for setting up a connection to the R&S FSWP. If the con-
nection is terminated and then restored, the R&S FSWP remains in the same state.
14.4.7.4 How to Shut Down the R&S FSWP via Remote Operation
1. Select the R&S FSWP softfrontpanel and close the application with the key combi-
nation [ALT] + [F4].
2. Select the desktop and press the key combination [ALT] + [F4].
A safety query is displayed to warn you that the instrument cannot be reactivated
via remote operation and asks you whether you want to continue the shutdown
process.
When you switch on the R&S FSWP, 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 R&S FSWP 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 will switch back to remote control immediately.
If you select the "Local" softkey 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.
15 Remote Control
● Conventions Used in SCPI Command Descriptions............................................. 383
● Common Suffixes..................................................................................................384
● Common Commands............................................................................................ 384
● Selecting the Operating Mode and Application..................................................... 389
● Measurements and Result Displays......................................................................397
● Common Measurement Settings...........................................................................413
● Common Analysis and Display Functions.............................................................500
● Managing Settings and Results............................................................................ 552
● Configuring the R&S FSWP.................................................................................. 579
● Using the Status Register..................................................................................... 614
● Programming Examples........................................................................................618
<m> 1 to 16 Marker
(or spot noise marker)
<t> 1 to 6 Trace
*TRG............................................................................................................................ 388
*TST?........................................................................................................................... 388
*WAI............................................................................................................................. 388
*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 278
*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,FSWP-26,1322.8003K26/100005,1.00
Usage: Query only
Manual operation: See "*IDN Format" on page 356
*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 data sheet.
Usage: Query only
*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
*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.
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.
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, the self-test cannot be aborted.
Return values:
<ErrorCode> integer > 0 (in decimal format)
An error occurred.
(For details, see the Service Manual supplied with the instru-
ment).
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................................................................................................................389
INSTrument:CREate:DUPLicate...................................................................................... 389
INSTrument:CREate[:NEW]............................................................................................ 389
INSTrument:CREate:REPLace........................................................................................ 390
INSTrument:DELete....................................................................................................... 390
INSTrument:LIST?......................................................................................................... 391
INSTrument:REName.....................................................................................................392
INSTrument[:SELect]......................................................................................................392
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 the function off
ON | 1
Switches the function on
INSTrument:CREate:DUPLicate
This command 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.
This command is not available if the MSRA Master channel is selected.
Example: INST:SEL 'PhaseNoise'
INST:CRE:DUPL
Duplicates the channel named 'PhaseNoise' and creates a new
channel named 'PhaseNoise 2'.
Usage: Event
Manual operation: See " Duplicate Current Channel " on page 102
See also
● INSTrument[:SELect] on page 392
● INSTrument:DELete on page 390
Parameters:
<ChannelType> Channel type of the new channel.
For a list of available channel types see INSTrument:LIST?
on page 391.
<ChannelName> String containing the name of the channel.
Note that you can not assign an existing channel name to a new
channel; this will cause an error.
Example: INST:CRE SAN, 'Spectrum 2'
Adds an additional spectrum display named "Spectrum 2".
Manual operation: See "New Channel" on page 102
INSTrument:CREate:REPLace <ChannelName1>,<ChannelType>,<ChannelName2>
This command replaces a channel with another one.
Setting parameters:
<ChannelName1> String containing the name of the channel you want to replace.
<ChannelType> Channel type of the new channel.
For a list of available channel types see INSTrument:LIST?
on page 391.
<ChannelName2> String containing the name of the new channel.
Note: If the specified name for a new channel already exists, the
default name, extended by a sequential number, is used for the
new channel (see INSTrument:LIST? on page 391).
Channel names can have a maximum of 31 characters, and
must be compatible with the Windows conventions for file
names. In particular, they must not contain special characters
such as ":", "*", "?".
Example: INST:CRE:REPL 'PhaseNoise',PNO,'PNO2'
Replaces the channel named "PhaseNoise" by a new channel of
type "Phase Noise" named "PNO2".
Usage: Setting only
Manual operation: See "Replace Current Channel" on page 102
INSTrument:DELete <ChannelName>
This command deletes a channel.
If you delete the last channel, the default "Phase Noise" channel is activated.
Setting parameters:
<ChannelName> String containing the name of the channel you want to delete.
A channel must exist in order to be able delete it.
Example: INST:DEL 'PhaseNoise'
Deletes the channel with the name 'PhaseNoise'.
Usage: Setting only
INSTrument:LIST?
This command queries all active channels. This is useful in order to obtain the names
of the existing channels, which are required in order 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 2 channels:
'PNO','PhaseNoise','PNO','Phase Noise 2'
Usage: Query only
Table 15-2: Available channel types and default channel names
Note: the default channel name is also listed in the table. If the specified name for a new channel already
exists, the default name, extended by a sequential number, is used for the new channel.
INITiate:SEQuencer:ABORt............................................................................................ 393
INITiate:SEQuencer:IMMediate....................................................................................... 393
INITiate:SEQuencer:MODE.............................................................................................394
SYSTem:SEQuencer...................................................................................................... 394
INITiate:SEQuencer:ABORt
This command stops the currently active sequence of measurements.
You can start a new sequence any time using INITiate:SEQuencer:IMMediate
on page 393.
Usage: Event
Manual operation: See " Sequencer State " on page 105
INITiate:SEQuencer:IMMediate
This command 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 394).
Example: SYST:SEQ ON
Activates the Sequencer.
INIT:SEQ:MODE SING
Sets single sequence mode so each active measurement will be
performed once.
INIT:SEQ:IMM
Starts the sequential measurements.
Manual operation: See " Sequencer State " on page 105
INITiate:SEQuencer:MODE <Mode>
Defines the capture mode for the entire measurement sequence and all measurement
groups and channels it contains.
Note: In order to synchronize to the end of a measurement sequence using *OPC,
*OPC? or *WAI you must use SINGle Sequence 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 explicitely.
*RST: CONTinuous
Manual operation: See " Sequencer Mode " on page 105
SYSTem:SEQuencer <State>
This command turns the Sequencer on and off. The Sequencer must be active before
any other Sequencer commands (INIT:SEQ...) are executed, otherwise an error will
occur.
A detailed programming example is provided in Chapter 15.4.3, "Programming Exam-
ple: Performing a Sequence of Measurements", on page 395.
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 will
be performed once.
INIT:SEQ:IMM
Starts the sequential measurements.
SYST:SEQ OFF
Manual operation: See " Sequencer State " on page 105
SENS:SWEEP:COUNT 2
//Change trace modes
DISP:TRAC1:MODE MAXH
DISP:TRAC2:MODE MINH
//Create new analyzer channel
INSTrument:CREate:NEW SANalyzer,'Spectrum 2'
//Activate ACLR measurement in channel 'Spectrum 2'
CALCulate:MARKer:FUNCtion:POWer:SELect ACPower
//Load W-CDMA Standard
CALCulate:MARKer:FUNCtion:POWer:PRESet FW3Gppcdma
//Change trace modes
DISP:TRAC2:MODE MAXH
DISP:TRAC1:MODE MINH
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
CONFigure:PNOise:MEASurement..................................................................................397
CONFigure:SNTune:MEASurement[:STATe]..................................................................... 398
CONFigure:TRANsient:MEASurement[:STATe]................................................................. 398
CONFigure:VCO:MEASurement[:STATe].......................................................................... 399
CONFigure:PNOise:MEASurement <Measurement>
This command selects the measurement.
● To select the Spot Noise vs Tune measurement, use CONFigure:SNTune:
MEASurement[:STATe].
● To select the VCO characterization, use CONFigure:VCO:MEASurement[:
STATe].
● To select the Transient Analysis measurement, use CONFigure:TRANsient:
MEASurement[:STATe].
Parameters:
<Measurement> BASeband
Selects the Baseband Noise measurement.
PNOise
Select the Phase Noise measurement.
PPNoise
Selects the Pulsed Phase Noise measurement.
PRESidual
Selects the Additive Pulsed Phase Noise measurement.
RESidual
Selects the Additive Noise measurement.
*RST: PNOise
Example: //Select the additive noise measurement
CONF:PNO:MEAS RES
Manual operation: See "Phase noise Measurement" on page 111
See "Additive noise measurements (optional)" on page 111
See "Baseband noise measurement" on page 111
See "Pulsed phase noise measurements (optional)" on page 112
See "Pulsed additive noise measurements (optional)"
on page 112
See "Selecting the noise measurement type" on page 124
CONFigure:SNTune:MEASurement[:STATe] <State>
This command selects the Spot Noise vs Tune measurement.
● To select the VCO characterization measurement, use CONFigure:VCO:
MEASurement[:STATe].
● To select the Transient Analysis measurement, use CONFigure:TRANsient:
MEASurement[:STATe].
● To select other measurements, use CONFigure:PNOise:MEASurement.
Parameters:
<State> ON | 1
Selects the Spot Noise vs Tune measurement.
OFF | 0
Selects the Phase Noise measurement (CONF:PNO:MEAS
PNO).
*RST: OFF
Example: //Select the phase noise measurement
CONF:VCO:MEAS OFF
Manual operation: See "Spot noise vs tune" on page 111
CONFigure:TRANsient:MEASurement[:STATe] <State>
This command selects the PN Transient Analysis measurement.
● To select the Spot Noise vs Tune measurement, use CONFigure:SNTune:
MEASurement[:STATe].
● To select the VCO characterization measurement, use CONFigure:VCO:
MEASurement[:STATe].
● To select other measurements, use CONFigure:PNOise:MEASurement.
Parameters:
<State> ON | 1
Selects the PN Transient Analysis measurement.
OFF | 0
Selects the Phase Noise measurement (CONF:PNO:MEAS
PNO).
*RST: OFF
Example: //Select the phase noise measurement
CONF:VCO:MEAS OFF
Manual operation: See "PN Transient analysis" on page 112
CONFigure:VCO:MEASurement[:STATe] <State>
This command selects the VCO Characterization measurement.
● To select the Spot Noise vs Tune measurement, use CONFigure:SNTune:
MEASurement[:STATe].
● To select the Transient Analysis measurement, use CONFigure:TRANsient:
MEASurement[:STATe].
● To select other measurements, use CONFigure:PNOise:MEASurement.
Parameters:
<State> ON | 1
Selects the VCO Characterization measurement.
OFF | 0
Selects the Phase Noise measurement (CONF:PNO:MEAS
PNO).
*RST: OFF
Example: //Select the phase noise measurement
CONF:VCO:MEAS OFF
Manual operation: See "VCO characterization" on page 111
ABORt.......................................................................................................................... 399
INITiate<n>:CONMeas................................................................................................... 400
INITiate<n>:CONTinuous................................................................................................ 401
INITiate<n>[:IMMediate]..................................................................................................402
ABORt
This command 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 see Chapter 14.1.6.1, "Preventing Overlapping Execution", on page 331.
INITiate<n>:CONMeas
This command restarts a (single) measurement that has been stopped (using ABORt)
or finished in single measurement 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
INITiate<n>:CONTinuous <State>
This command controls the measurement mode for an individual channel.
Note that in single measurement mode, you can synchronize to the end of the mea-
surement with *OPC, *OPC? or *WAI. In continuous measurement mode, synchroniza-
tion to the end of the measurement is not possible. Thus, it is not recommended that
you use continuous measurement mode in remote control, as results like trace data or
markers are only valid after a single measurement end synchronization.
For details on synchronization see Chapter 14.1.6, "Command Sequence and Syn-
chronization", on page 330.
If the measurement mode is changed for a channel while the Sequencer is active the
mode is only considered the next time the measurement in that channel is activated by
the Sequencer.
Suffix: .
<n> irrelevant
Parameters:
<State> ON | OFF | 0 | 1
ON | 1
Continuous measurement
OFF | 0
Single measurement
*RST: 1
Example: INIT:CONT OFF
Switches the measurement mode to single measurement.
INIT:CONT ON
Switches the measurement mode to continuous measurement.
Manual operation: See " Continuous Sweep / Run Cont " on page 110
INITiate<n>[:IMMediate]
This command starts a (single) new measurement.
With measurement count or average count > 0, this means a restart of the correspond-
ing 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 Chapter 14.1.6, "Command Sequence and Syn-
chronization", on page 330.
Suffix: .
<n> irrelevant
Manual operation: See " Single Sweep / Run Single " on page 109
FETCh<n>[:RANGe<j>]:PNOise<t>:DUT:GAIN?
This command queries the DUT gain.
The DUT gain is the ratio of the power measured at the DUT output and the power
applied to the DUT input (signal power at the signal source output).
Suffix: .
<n> irrelevant
<j> irrelevant
<t> irrelevant
Return values:
<values> <numeric value>
Default unit: dB
Example: //Query DUT gain
FETC:RANG:PNO:DUT:GAIN?
would return, e.g.
2.28
Usage: Query only
FETCh<n>:PNOise<t>:SPURs?
This command queries the location and level of all spurs that have been detected.
Suffix: .
<n> Window
<t> Trace
Return values:
<SpurCoordinates> Returns two values (frequency and level) for each each spur that
has been detected.
Example: //Query spur characteristics
FETC:PNO:SPUR?
would return, e.g.
1999.232666,-0.639974,6494.312500,-0.760579,
19992.324219,-0.639974
Usage: Query only
Manual operation: See "Spurious List" on page 115
FETCh<n>:PNOise<t>:SPURs:COUNt?
This command queries the number of spurious included in the spurious list.
Suffix: .
<n> 1..n
Window
<t> 1..n
Trace
Return values:
<Count> Number of spurious
Example: FETCh:PNO:SPURs:COUNt?
FETCh<n>:PNOise<t>:SPURs:DISCrete?
This command queries the discrete jitter result.
Suffix: .
<n> Window
<t> Trace
Return values:
<Jitter> <numeric value>
Default unit: s
Example: //Query discrete jitter
FETC:PNO:SPUR:DISC?
would return, e.g.
2.3e-08
Usage: Query only
Manual operation: See "Spurious List" on page 115
FETCh<n>:PNOise<t>:SPURs:JITTer?
This command queries the jitter of the measured spurs.
Suffix: .
<n> Window
<t> Trace
Return values:
<Jitter> <numeric value>
Default unit: s
Example: //Query jitter of spurs
FETC:PNO:SPUR:JITT?
would return, e.g.
+2.199886328E+004,+2.440125142E-012,
+7.332938281E+004,[...]
Usage: Query only
Manual operation: See "Spurious List" on page 115
FETCh<n>:PNOise<t>:SPURs:RANDom?
This command queries the random jitter result.
Suffix: .
<n> Window
<t> Trace
Return values:
<arg0> <numeric value>
Default unit: s
Example: //Query random jitter
FETC:PNO:SPUR:RAND?
would return, e.g.
3.59e-09
Usage: Query only
Manual operation: See "Spurious List" on page 115
FETCh<n>[:RANGe<j>]:PNOise<t>:IPN?
This command queries the integrated phase noise.
Suffix: .
<n> Window
<j> Integration range
<t> Trace
Return values:
<Level> <numeric value>
Default unit: dBc
Example: //Query integrated phase noise
FETC:RANG2:PNO2:IPN?
would return, e.g.
-16.79
Usage: Query only
Manual operation: See "Integrated Measurements" on page 114
FETCh<n>[:RANGe<j>]:PNOise<t>:RAM?
This command queries the residual AM.
Suffix: .
<n> Window
<j> Integration range
<t> Trace
Return values:
<Am> <numeric value>
In case of Baseband Noise measurements, the result is always
0.
Default unit: PCT
FETCh<n>[:RANGe<j>]:PNOise<t>:RFM?
This command queries the residual FM.
Suffix: .
<n> Window
<j> Integration range
<t> Trace
Return values:
<Frequency> <numeric value>
In case of Baseband Noise measurements, the result is always
0.
Default unit: Hz
Example: //Query residual FM
FETC:RANG2:PNO:RFM?
would return, e.g.
88110000
Usage: Query only
Manual operation: See "Integrated Measurements" on page 114
FETCh<n>[:RANGe<j>]:PNOise<t>:RMS?
This command queries the residual RMS jitter.
Suffix: .
<n> Window
<j> Integration range
<t> Trace
Return values:
<Jitter> <numeric value>
In case of Baseband Noise measurements, the result is always
0.
Default unit: s
FETCh<n>[:RANGe<j>]:PNOise<t>:RPM?
This command queries the residual PM.
Suffix: .
<n> Window
<j> Integration range
<t> Trace
Return values:
<Phase> <numeric value>
In case of Baseband Noise measurements, the result is always
0.
Default unit: deg
Example: //Query residual PM
FETC:RANG2:PNO:RPM?
would return, e.g.
11.73
Usage: Query only
Manual operation: See "Integrated Measurements" on page 114
Setting parameters:
<FileName> String containing the path and name of the target file.
<Trace> <numeric value> (integer only)
Trace from which the spur information is collected.
If you do not define a trace, all spurs over all traces are expor-
ted.
Example: //Store spur information of trace 1
MMEM:STOR:SPUR 'c:\spurs.asc',1
Usage: Setting only
[SENSe:]BWIDth:MEASurement?
This command queries the measurement bandwidth of the frequency stability mea-
surements (Allan variance and deviation).
Return values:
<Bandwidth> <numeric value>
Default unit: Hz
Example: //Query measurement bandwidth
BWID:MEAS?
Usage: Query only
Manual operation: See "Allan Variance / Allan Deviation" on page 117
TRACe<n>[:DATA]? <Trace>
This command queries the trace data (measurement results).
Suffix: .
<n> 1..n
Window
Query parameters:
<Trace> TRACE1 | ... | TRACE6
Queries the data of one of the colored line traces.
XGINdicator
Queries the data of the cross-correlation gain indicator (grey
area).
Return values:
<Result> • Phase noise measurements
Coordinates of the trace as list of comma-separated values,
beginning at the nearest offset frequency.
• Baseband noise measurements
Coordinates of the trace as list of comma-separated values,
beginning at the start frequency.
• VCO characterization
TRACe<n>:POINts? <Trace>
This command queries the number of measurement points of a specific trace.
Suffix: .
<n> 1..n
Window
Query parameters:
<Trace> TRACe1 | TRACe2 | TRACe3 | TRACe4 | TRACe5 | TRACe6 |
XGINdicator
"XGINdicator" only available for phase noise measurements.
Return values:
<Points> <numeric value> (integer)
TRACe<n>[:DATA]:X? <Trace>
Queries X trace values merged with spurs for a given window and trace.
Suffix: .
<n> 1..n
Window
Query parameters:
<Trace> TRACe1 | TRACe2 | TRACe3 | TRACe4 | TRACe5 | TRACe6
Return values:
<Result> Comma separated list of X values
Usage: Query only
Manual operation: See "Noise Diagram" on page 113
TRACe<n>[:DATA]:X:POINts? <Trace>
Queries number of points of trace data merged with spurs.
Suffix: .
<n> 1..n
Window
Query parameters:
<Trace> TRACe1 | TRACe2 | TRACe3 | TRACe4 | TRACe5 | TRACe6
Return values:
<Points> <numeric value> (integer)
Usage: Query only
Manual operation: See "Noise Diagram" on page 113
TRACe<n>[:DATA]:Y? <Trace>
Queries Y trace values merged with spurs for a given window and trace.
Suffix: .
<n> 1..n
Window
Query parameters:
<Trace> TRACe1 | TRACe2 | TRACe3 | TRACe4 | TRACe5 | TRACe6
Return values:
<Result> Comma separated list of Y values
Usage: Query only
TRACe<n>[:DATA]:Y:POINts? <Trace>
Queries number of points of trace data merged with spurs.
Suffix: .
<n> 1..n
Window
Query parameters:
<Trace> TRACe1 | TRACe2 | TRACe3 | TRACe4 | TRACe5 | TRACe6
Return values:
<Points> <numeric value> (integer)
Usage: Query only
Manual operation: See "Noise Diagram" on page 113
● RF Input................................................................................................................ 413
● Baseband Input.....................................................................................................415
● External Mixer....................................................................................................... 415
15.6.1.1 RF Input
INPut<ip>:COUPling.......................................................................................................413
INPut<ip>:SELect...........................................................................................................414
INPut<1|2>:LOSCillator:SOURce.....................................................................................414
INPut<1|2>:LOSCillator:SOURce:EXTernal:LEVel............................................................. 414
INPut<ip>:COUPling <CouplingType>
This command selects the coupling type of the RF input.
Suffix: .
<ip> 1|2
irrelevant
Parameters:
<CouplingType> AC | DC
AC
AC coupling
DC
DC coupling
*RST: AC
Example: INP:COUP DC
Manual operation: See " Input Coupling " on page 126
INPut<ip>:SELect <Source>
This command selects the signal source for measurements, i.e. it defines which con-
nector is used to input data to the R&S FSWP.
Suffix: .
<ip> 1|2
irrelevant
Parameters:
<Source> ABB
Analog Baseband signal
RF
Radio Frequency ("RF INPUT" connector)
*RST: RF
Manual operation: See " Radio Frequency State " on page 126
INPut<1|2>:LOSCillator:SOURce <Location>
This command selects the type of local oscillator in the test setup.
Prerequisites for this command
● Select additive noise or pulsed additive noise measurement (CONFigure:
PNOise:MEASurement).
Suffix: .
<1|2> 1|2
irrelevant
Parameters:
<Location> EXTernal
External local oscillator connected to the "LO AUX Input" of the
R&S FSWP.
INTernal
Internal local oscillator of the R&S FSWP.
*RST: INTernal
Example: //Select external oscillator
CONF:PNO:MEAS RES
INP:LOSC:SOUR EXT
Manual operation: See "Local Oscillator" on page 126
INPut<1|2>:LOSCillator:SOURce:EXTernal:LEVel <Level>
This command selects the level of an external LO signal that is fed into the
R&S FSWP.
Prerequisites for this command
● Select additive noise or pulsed additive noise measurement (CONFigure:
PNOise:MEASurement).
INPut<1|2>:CONNector.................................................................................................. 415
INPut<1|2>:CONNector <Mode>
This command selects the measurement channel for baseband noise measurements.
Suffix: .
<1|2> 1|2
irrelevant
Parameters:
<Mode> CH1
Measurement on baseband channel 1.
CH2
Measurement on baseband channel 2.
XCOR
Measurement on both baseband channels (cross-correlation
measurements).
Example: //Perform measurement on baseband channel 1
INP:CONN CH1
Mixer Settings
[SENSe:]MIXer<x>:FREQuency:HANDover...................................................................... 416
[SENSe:]MIXer<x>:FREQuency:STARt............................................................................ 416
[SENSe:]MIXer<x>:FREQuency:STOP.............................................................................417
[SENSe:]MIXer<x>:HARMonic:BAND...............................................................................417
[SENSe:]MIXer<x>:HARMonic:BAND:PRESet.................................................................. 418
[SENSe:]MIXer<x>:HARMonic:HIGH[:VALue]................................................................... 418
[SENSe:]MIXer<x>:HARMonic:HIGH:STATe..................................................................... 418
[SENSe:]MIXer<x>:HARMonic:TYPE............................................................................... 419
[SENSe:]MIXer<x>:HARMonic[:LOW].............................................................................. 419
[SENSe:]MIXer<x>:LOSS:HIGH...................................................................................... 419
[SENSe:]MIXer<x>:LOSS:TABLe:HIGH............................................................................420
[SENSe:]MIXer<x>:LOSS:TABLe[:LOW]...........................................................................420
[SENSe:]MIXer<x>:LOSS[:LOW]..................................................................................... 420
[SENSe:]MIXer<x>:PORTs..............................................................................................421
[SENSe:]MIXer<x>:RFOVerrange[:STATe]........................................................................ 421
[SENSe:]MIXer<x>:XCORr..............................................................................................421
[SENSe:]MIXer<x>:FREQuency:HANDover <Frequency>
This command defines the frequency at which the mixer switches from one range to
the next (if two different ranges are selected). The handover frequency for each band
can be selected freely within the overlapping frequency range.
This command is only available if the external mixer is active (see [SENSe:
]MIXer<x>[:STATe] on page 423).
Suffix: .
<x> 1..n
irrelevant
Parameters:
<Frequency> Default unit: HZ
Example: MIX ON
Activates the external mixer.
MIX:FREQ:HAND 78.0299GHz
Sets the handover frequency to 78.0299 GHz.
Manual operation: See " Handover Freq " on page 134
[SENSe:]MIXer<x>:FREQuency:STARt
This command sets or queries the frequency at which the external mixer band starts.
Suffix: .
<x> 1..n
irrelevant
Example: MIX:FREQ:STAR?
Queries the start frequency of the band.
Manual operation: See " RF Start / RF Stop " on page 134
[SENSe:]MIXer<x>:FREQuency:STOP
This command sets or queries the frequency at which the external mixer band stops.
Suffix: .
<x> 1..n
irrelevant
Example: MIX:FREQ:STOP?
Queries the stop frequency of the band.
Manual operation: See " RF Start / RF Stop " on page 134
[SENSe:]MIXer<x>:HARMonic:BAND <Band>
This command selects the external mixer band. The query returns the currently
selected band.
This command is only available if the external mixer is active (see [SENSe:
]MIXer<x>[:STATe] on page 423).
Suffix: .
<x> 1..n
irrelevant
Parameters:
<Band> KA | Q | U | V | E | W | F | D | G | Y | J | USER
Standard waveguide band or user-defined band.
Manual operation: See " Band " on page 134
Table 15-3: Frequency ranges for pre-defined bands
Q 33.0 50.0
U 40.0 60.0
V 50.0 75.0
E 60.0 90.0
W 75.0 110.0
F 90.0 140.0
D 110.0 170.0
G 140.0 220.0
J 220.0 325.0
Y 325.0 500.0
[SENSe:]MIXer<x>:HARMonic:BAND:PRESet
This command restores the preset frequency ranges for the selected standard wave-
guide band.
Note: Changes to the band and mixer settings are maintained even after using the
[PRESET] function. Use this command to restore the predefined band ranges.
Suffix: .
<x> 1..n
irrelevant
Example: MIX:HARM:BAND:PRES
Presets the selected waveguide band.
Manual operation: See " Preset Band " on page 135
[SENSe:]MIXer<x>:HARMonic:HIGH[:VALue] <HarmOrder>
This command specifies the harmonic order to be used for the high (second) range.
Suffix: .
<x> 1..n
irrelevant
Parameters:
<HarmOrder numeric value
Range: 2 to 61 (USER band); for other bands: see band
definition
Example: MIX:HARM:HIGH:STAT ON
MIX:HARM:HIGH 2
Manual operation: See " Harmonic Order " on page 136
[SENSe:]MIXer<x>:HARMonic:HIGH:STATe <State>
This command specifies whether a second (high) harmonic is to be used to cover the
band's frequency range.
Suffix: .
<x> 1..n
Parameters:
<State> ON | OFF
*RST: ON
Example: MIX:HARM:HIGH:STAT ON
Manual operation: See " Range 1 / Range 2 " on page 135
[SENSe:]MIXer<x>:HARMonic:TYPE <OddEven>
This command specifies whether the harmonic order to be used should be odd, even,
or both.
Which harmonics are supported depends on the mixer type.
Suffix: .
<x> 1..n
irrelevant
Parameters:
<OddEven> ODD | EVEN | EODD
ODD | EVEN | EODD
*RST: EVEN
Example: MIX:HARM:TYPE ODD
Manual operation: See " Harmonic Type " on page 135
[SENSe:]MIXer<x>:HARMonic[:LOW] <HarmOrder>
This command specifies the harmonic order to be used for the low (first) range.
Suffix: .
<x> 1..n
irrelevant
Parameters:
<HarmOrder> Range: 2 to 61 (USER band); for other bands: see band
definition
*RST: 2 (for band F)
Example: MIX:HARM 3
Manual operation: See " Harmonic Order " on page 136
[SENSe:]MIXer<x>:LOSS:HIGH <Average>
This command defines the average conversion loss to be used for the entire high (sec-
ond) range.
Suffix: .
<x> 1..n
Mixer
Parameters:
<Average> Range: 0 to 100
*RST: 24.0 dB
Default unit: dB
Example: MIX:LOSS:HIGH 20dB
Manual operation: See " Conversion Loss " on page 136
[SENSe:]MIXer<x>:LOSS:TABLe:HIGH <FileName>
This command defines the conversion loss table to be used for the high (second)
range.
Suffix: .
<x> 1..n
Mixer
Setting parameters:
<FileName> String containing the path and name of the file, or the serial
number of the external mixer whose file is required. The
R&S FSWP automatically selects the correct cvl file for the cur-
rent IF. As an alternative, you can also select a user-defined
conversion loss table (.acl file).
Return values:
<FileName> As the result of a query, the actually used file is returned.
Manual operation: See " Conversion Loss " on page 136
[SENSe:]MIXer<x>:LOSS:TABLe[:LOW] <FileName>
This command defines the file name of the conversion loss table to be used for the low
(first) range.
Suffix: .
<x> 1..n
Mixer
Parameters:
<FileName> String containing the path and name of the file, or the serial
number of the external mixer whose file is required. The
R&S FSWP automatically selects the correct cvl file for the cur-
rent IF. As an alternative, you can also select a user-defined
conversion loss table (.acl file).
Example: MIX:LOSS:TABL '101567'
MIX:LOSS:TABL?
//Result:
'101567_MAG_6_B5000_3G5.B5G'
Manual operation: See " Conversion Loss " on page 136
[SENSe:]MIXer<x>:LOSS[:LOW] <Average>
This command defines the average conversion loss to be used for the entire low (first)
range.
Suffix: .
<x> 1..n
Mixer
Parameters:
<Average> Range: 0 to 100
*RST: 24.0 dB
Default unit: dB
Example: MIX:LOSS 20dB
Manual operation: See " Conversion Loss " on page 136
[SENSe:]MIXer<x>:PORTs <PortType>
This command queries the connected mixer type. Currently, only three-port mixers are
supported.
Suffix: .
<x> 1..n
irrelevant
Parameters:
<PortType> 2|3
2
Two-port mixer.
3
Three-port mixer.
*RST: 2
Example: MIX:PORT 3
[SENSe:]MIXer<x>:RFOVerrange[:STATe] <State>
If enabled, the band limits are extended beyond "RF Start" and "RF Stop" due to the
capabilities of the used harmonics.
Suffix: .
<x> 1..n
irrelevant
Parameters:
<State> ON | OFF | 1 | 0
*RST: 0
Manual operation: See " RF Overrange " on page 135
[SENSe:]MIXer<x>:XCORr <State>
This command turns cross-correlation with two external mixers on and off.
Suffix: .
<x> 1..n
irrelevant
Parameters:
<State> ON | OFF | 1 | 0
*RST: ON
Example: //Turn on cross-correlation with two mixers
MIX:XCOR ON
Manual operation: See "Mixer XCORR" on page 135
Basic Settings
[SENSe:]MIXer<x>:BIAS:HIGH........................................................................................422
[SENSe:]MIXer<x>:BIAS[:LOW].......................................................................................422
[SENSe:]MIXer<x>[:STATe]............................................................................................. 423
[SENSe:]MIXer<x>:LOPower.......................................................................................... 423
[SENSe:]MIXer<x>:BIAS:HIGH <BiasSetting>
This command defines the bias current for the high (last) range.
This command is only available if the external mixer is active (see [SENSe:
]MIXer<x>[:STATe] on page 423).
Suffix: .
<x> 1..n
irrelevant
Parameters:
<BiasSetting> *RST: 0.0 A
Default unit: A
Manual operation: See " Bias Value " on page 137
[SENSe:]MIXer<x>:BIAS[:LOW] <BiasSetting>
This command defines the bias current for the low (first) range.
This command is only available if the external mixer is active (see [SENSe:
]MIXer<x>[:STATe] on page 423).
Suffix: .
<x> 1..n
irrelevant
Parameters:
<BiasSetting> *RST: 0.0 A
Default unit: A
Manual operation: See " Bias Value " on page 137
[SENSe:]MIXer<x>[:STATe] <State>
Activates or deactivates the use of a connected external mixer as input for the mea-
surement. This command is only available if the optional External Mixer is installed and
an external mixer is connected.
Suffix: .
<x> 1..n
irrelevant
Parameters:
<State> ON | OFF | 1 | 0
*RST: 0
Example: MIX ON
Manual operation: See " External Mixer (State)" on page 134
[SENSe:]MIXer<x>:LOPower <Level>
This command specifies the LO level of the external mixer's LO port.
Suffix: .
<x> 1..n
irrelevant
Parameters:
<Level> numeric value
Range: 13.0 dBm to 17.0 dBm
Increment: 0.1 dB
*RST: 15.5 dBm
Example: MIX:LOP 16.0dBm
Manual operation: See " LO Level " on page 137
[SENSe:]CORRection:CVL:BAND <Band>
This command defines the waveguide band for which the conversion loss table is to be
used. This setting is checked against the current mixer setting before the table can be
assigned to the range.
Before this command can be performed, the conversion loss table must be selected
(see [SENSe:]CORRection:CVL:SELect on page 427).
This command is only available with option B21 (External Mixer) installed.
Parameters:
<Band> K | KA | Q | U | V | E | W | F | D | G | Y | J | USER
Standard waveguide band or user-defined band.
For a definition of the frequency range for the pre-defined bands,
see Table 15-3).
*RST: F (90 GHz - 140 GHz)
Example: CORR:CVL:SEL 'LOSS_TAB_4'
Selects the conversion loss table.
CORR:CVL:BAND KA
Sets the band to KA (26.5 GHz - 40 GHz).
Manual operation: See " Band " on page 140
[SENSe:]CORRection:CVL:BIAS <BiasSetting>
This command defines the bias setting to be used with the conversion loss table.
Before this command can be performed, the conversion loss table must be selected
(see [SENSe:]CORRection:CVL:SELect on page 427.
This command is only available with option B21 (External Mixer) installed.
Parameters:
<BiasSetting> *RST: 0.0 A
Default unit: A
Example: CORR:CVL:SEL 'LOSS_TAB_4'
Selects the conversion loss table.
CORR:CVL:BIAS 3A
Manual operation: See " Write to CVL table " on page 137
See " Bias " on page 140
[SENSe:]CORRection:CVL:CATalog?
This command queries all available conversion loss tables saved in the
C:\R_S\INSTR\USER\cvl\ directory on the instrument.
This command is only available with option B21 (External Mixer) installed.
Return values:
<Files> 'string'
Comma-separated list of strings containing the file names.
Example: CORR:CVL:CAT?
Usage: Query only
[SENSe:]CORRection:CVL:CLEar
This command deletes the selected conversion loss table. Before this command can
be performed, the conversion loss table must be selected (see [SENSe:
]CORRection:CVL:SELect on page 427).
This command is only available with option B21 (External Mixer) installed.
Example: CORR:CVL:SEL 'LOSS_TAB_4'
Selects the conversion loss table.
CORR:CVL:CLE
Manual operation: See " Delete Table " on page 139
[SENSe:]CORRection:CVL:COMMent <Text>
This command defines a comment for the conversion loss table. Before this command
can be performed, the conversion loss table must be selected (see [SENSe:
]CORRection:CVL:SELect on page 427).
This command is only available with option B21 (External Mixer) installed.
Parameters:
<Text>
Example: CORR:CVL:SEL 'LOSS_TAB_4'
Selects the conversion loss table.
CORR:CVL:COMM 'Conversion loss table for
FS_Z60'
Manual operation: See " Comment " on page 140
[SENSe:]CORRection:CVL:HARMonic <HarmOrder>
This command defines the harmonic order for which the conversion loss table is to be
used. This setting is checked against the current mixer setting before the table can be
assigned to the range.
Before this command can be performed, the conversion loss table must be selected
(see [SENSe:]CORRection:CVL:SELect on page 427.
This command is only available with option B21 (External Mixer) installed.
Parameters:
<HarmOrder> Range: 2 to 65
Example: CORR:CVL:SEL 'LOSS_TAB_4'
Selects the conversion loss table.
CORR:CVL:HARM 3
Manual operation: See " Harmonic Order " on page 140
[SENSe:]CORRection:CVL:MIXer <Type>
This command defines the mixer name in the conversion loss table. This setting is
checked against the current mixer setting before the table can be assigned to the
range.
Before this command can be performed, the conversion loss table must be selected
(see [SENSe:]CORRection:CVL:SELect on page 427).
This command is only available with option B21 (External Mixer) installed.
Parameters:
<Type> string
Name of mixer with a maximum of 16 characters
Example: CORR:CVL:SEL 'LOSS_TAB_4'
Selects the conversion loss table.
CORR:CVL:MIX 'FS_Z60'
Manual operation: See " Mixer Name " on page 141
[SENSe:]CORRection:CVL:PORTs <PortType>
This command defines the mixer type in the conversion loss table. This setting is
checked against the current mixer setting before the table can be assigned to the
range.
Before this command can be performed, the conversion loss table must be selected
(see [SENSe:]CORRection:CVL:SELect on page 427).
This command is only available with option B21 (External Mixer) installed.
Parameters:
<PortType> 2|3
*RST: 2
Example: CORR:CVL:SEL 'LOSS_TAB_4'
Selects the conversion loss table.
CORR:CVL:PORT 3
Manual operation: See " Mixer Type " on page 141
[SENSe:]CORRection:CVL:SELect <FileName>
This command selects the conversion loss table with the specified file name. If
<file_name> is not available, a new conversion loss table is created.
This command is only available with option B21 (External Mixer) installed.
Parameters:
<FileName> String containing the path and name of the file.
Example: CORR:CVL:SEL 'LOSS_TAB_4'
Manual operation: See " New Table " on page 138
See " Edit Table " on page 138
See " File Name " on page 140
[SENSe:]CORRection:CVL:SNUMber <SerialNo>
This command defines the serial number of the mixer for which the conversion loss
table is to be used. This setting is checked against the current mixer setting before the
table can be assigned to the range.
Before this command can be performed, the conversion loss table must be selected
(see [SENSe:]CORRection:CVL:SELect on page 427).
This command is only available with option B21 (External Mixer) installed.
Parameters:
<SerialNo> Serial number with a maximum of 16 characters
Example: CORR:CVL:SEL 'LOSS_TAB_4'
Selects the conversion loss table.
CORR:CVL:MIX '123.4567'
Manual operation: See " Mixer S/N " on page 141
15.6.2 Output
● DC Power..............................................................................................................428
● Signal Source........................................................................................................437
● Miscellaneous Output............................................................................................441
15.6.2.1 DC Power
SOURce:CURRent:AUX:LIMit:HIGH?.............................................................................. 428
SOURce:CURRent:CONTrol<i>:LIMit:HIGH?.................................................................... 428
SOURce:CURRent:POWer<i>:LIMit:HIGH........................................................................429
SOURce:CURRent:SEQuence:RESult?........................................................................... 429
SOURce:POWer:SEQuence:RESult?...............................................................................430
SOURce:VOLTage:AUX:LEVel:AMPLitude........................................................................430
SOURce:VOLTage:AUX:LEVel:LIMit:HIGH....................................................................... 430
SOURce:VOLTage:AUX:LEVel:LIMit:LOW........................................................................ 430
SOURce:VOLTage:AUX:LEVel[:STATe]............................................................................ 431
SOURce:VOLTage:CHANnel:COUPling............................................................................431
SOURce:VOLTage:CONTrol<i>:LEVel:AMPLitude............................................................. 432
SOURce:VOLTage:CONTrol<i>:LEVel:LIMit:HIGH............................................................. 432
SOURce:VOLTage:CONTrol<i>:LEVel:LIMit:LOW..............................................................432
SOURce:VOLTage:CONTrol<i>:LEVel[:STATe].................................................................. 433
SOURce:VOLTage:POWer<i>:LEVel:AMPLitude............................................................... 433
SOURce:VOLTage:POWer<i>:LEVel:LIMit:HIGH............................................................... 434
SOURce:VOLTage:POWer<i>:LEVel:LIMit:LOW................................................................434
SOURce:VOLTage:POWer<i>:LEVel:MODE..................................................................... 435
SOURce:VOLTage:POWer<i>:LEVel[:STATe].................................................................... 435
SOURce:VOLTage:POWer<i>:LIMit:HIGH........................................................................ 435
SOURce:VOLTage:SEQuence:RESult?............................................................................ 436
SOURce:VOLTage[:STATe]............................................................................................. 436
SOURce:CURRent:AUX:LIMit:HIGH?
This command returns the maximum current of the Vaux connector.
Return values:
<Current> <numeric value>
The return value is always 0.1 A.
Example: //Query maximum current
SOUR:CURR:AUX:LIM:HIGH?
returns
0.1
Usage: Query only
SOURce:CURRent:CONTrol<i>:LIMit:HIGH?
This command returns the maximum current of the Vtune connector.
Suffix: .
<i> 1..n
irrelevant
Return values:
<Current> <numeric value>
The return value is always 0.02 A.
Default unit: A
Example: //Query maximum current
SOUR:CURR:CONT:LIM:HIGH?
returns
0.02
Usage: Query only
SOURce:CURRent:POWer<i>:LIMit:HIGH <Current>
This command defines the maximum current of the Vsupply connector.
SOURce:CURRent:SEQuence:RESult?
This command queries the actually measured current on the DC power sources.
Prerequisites for this command
● Turn on the DC power source (SOURce:VOLTage[:STATe]).
Example: //Query current on all DC power sources
SOUR:CURR:SEQ:RES?
would return, e.g.
0.000000, -0.100000, -0.020000
Usage: Query only
Manual operation: See "Reading the actual output levels" on page 168
SOURce:POWer:SEQuence:RESult?
This command queries the actually measured power (U*I) on the DC power sources.
Prerequisites for this command
● Turn on DC power sources (SOURce:VOLTage[:STATe]).
Example: //Query power output by the DC power sources
SOUR:POW:SEQ:RES?
would return, e.g.
0.000000, 1.000000, 0.200000
Usage: Query only
Manual operation: See "Reading the actual output levels" on page 168
SOURce:VOLTage:AUX:LEVel:AMPLitude <Voltage>
This command defines the output voltage for the Vaux source.
Parameters:
<Voltage> <numeric value>
Range: -10 to 10
*RST: 0
Default unit: V
Example: //Defines an output voltage of 1 V on the Vaux source
SOUR:VOLT:AUX:LEV:AMPL 1
Manual operation: See "Defining the output level" on page 167
SOURce:VOLTage:AUX:LEVel:LIMit:HIGH <Voltage>
This command defines the maximum voltage that may be supplied by the Vaux source.
Parameters:
<Voltage> <numeric value>
Range: -10 to 10
*RST: 0
Default unit: V
Example: //Define a maximum voltage of 5 V
SOUR:VOLT:AUX:LEV:LIM:HIGH 5
Manual operation: See "Defining the output level" on page 167
SOURce:VOLTage:AUX:LEVel:LIMit:LOW <Voltage>
This command defines the minimum voltage that may be supplied by the Vaux source.
Parameters:
<Voltage> <numeric value>
Range: -10 to 10
*RST: 0
Default unit: V
Example: //Define a minimum voltage of -5 V
SOUR:VOLT:AUX:LEV:LIM:LOW -5
Manual operation: See "Defining the output level" on page 167
SOURce:VOLTage:AUX:LEVel[:STATe] <State>
This command turns the auxiliary voltage source (Vaux) on and off.
Note that DC power is actually supplied only if you additionally activate the outputs in
general.
Prerequisites for this command
● Turn on DC power sources (SOURce:VOLTage[:STATe]).
Parameters:
<State> ON | OFF | 1 | 0
*RST: OFF
Example: //Turns on the Vaux source.
SOUR:VOLT:AUX:LEV ON
Manual operation: See "Turning the output on and off" on page 167
SOURce:VOLTage:CHANnel:COUPling <State>
This command couples or decouples the DC power configuration across measurement
channels.
Parameters:
<State> ON | 1
DC power configuration is the same across all measurement
channels.
OFF | 0
DC power configuration is different for each measurement chan-
nel.
*RST: ON
Example: //Use a different DC power setup for each active measurement
channel
SOUR:VOLT:CHAN:COUP OFF
Manual operation: See "Coupling the output configuration across measurement
channels" on page 166
SOURce:VOLTage:CONTrol<i>:LEVel:AMPLitude <Voltage>
This command defines the output voltage for the Vtune source.
Suffix: .
<i> 1..n
irrelevant
Parameters:
<Voltage> <numeric value>
Range: -10 to 28
*RST: 0
Default unit: V
Example: //Defines an output voltage of 1 V on the Vtune source
SOUR:VOLT:CONT:LEV:AMPL 1
Manual operation: See "Defining the output level" on page 167
SOURce:VOLTage:CONTrol<i>:LEVel:LIMit:HIGH <Voltage>
This command defines the maximum voltage that may be supplied by the Vtune source.
Suffix: .
<i> 1..n
irrelevant
Parameters:
<Voltage> <numeric value>
Range: -10 to 28
*RST: 0
Default unit: V
Example: //Defines a maximum voltage of 5 V
SOUR:VOLT:CONT:LEV:LIM:HIGH 5
Manual operation: See "Defining the output level" on page 167
SOURce:VOLTage:CONTrol<i>:LEVel:LIMit:LOW <Voltage>
This command defines the minimum voltage that may be supplied by the Vtune source.
Suffix: .
<i> irrelevant
Parameters:
<Voltage> <numeric value>
Range: -10 to 28
*RST: 0
Default unit: V
Example: //Define a minimum voltage of -5 V
SOUR:VOLT:CONT:LEV:LIM:LOW -5
SOURce:VOLTage:CONTrol<i>:LEVel[:STATe] <State>
This command turns the tuning voltage source (Vtune) on and off.
Note that DC power is actually supplied only if you additionally activate the outputs in
general.
Prerequisites for this command
● Turn on DC power sources (SOURce:VOLTage[:STATe]).
Suffix: .
<i> 1..n
irrelevant
Parameters:
<State> ON | OFF | 1 | 0
*RST: OFF
Example: //Turn on the Vtune voltage source
SOUR:VOLT:CONT:LEV ON
Manual operation: See "Turning the output on and off" on page 167
SOURce:VOLTage:POWer<i>:LEVel:AMPLitude <Voltage/Current>
This command defines the output voltage for the Vsupply source.
Suffix: .
<i> 1..n
irrelevant
Parameters:
<Voltage/Current> <numeric value>
The type of value depends on whether you control the output in
terms of current or voltage (SOURce:VOLTage:POWer<i>:
LEVel:MODE).
When you control it in terms of voltage, the value is a voltage
(V). When you control it in terms of current, the value is the cur-
rent (A).
Range: 0 to 16 V or 2000 mA
*RST: 0 V or 2000 mA
Default unit: V or A
Example: //Define an output voltage of 1 V on the Vsupply source
SOUR:VOLT:POW:LEV:AMPL 1
Manual operation: See "Defining the output level" on page 167
SOURce:VOLTage:POWer<i>:LEVel:LIMit:HIGH <Voltage/Current>
This command defines the maximum voltage that may be supplied by the Vsupply
source.
Suffix: .
<i> 1..n
irrelevant
Parameters:
<Voltage/Current> <numeric value>
The type of value depends on whether you control the output in
terms of current or voltage (SOURce:VOLTage:POWer<i>:
LEVel:MODE).
When you control it in terms of voltage, the value is a voltage
(V). When you control it in terms of current, the value is the cur-
rent (A).
Range: 0 to 16 V or 2000 mA
*RST: 16 V or 2000 mA
Default unit: V or A
Example: //Define a maximum current of 1000 mA
SOUR:VOLT:POW:LEV:LIM:HIGH 1000MA
Manual operation: See "Defining the output level" on page 167
SOURce:VOLTage:POWer<i>:LEVel:LIMit:LOW <Voltage/Current>
This command defines the minimum voltage that may be supplied by the Vsupply source.
Suffix: .
<i> irrelevant
Parameters:
<Voltage/Current> <numeric value>
The type of value depends on whether you control the output in
terms of current or voltage (SOURce:VOLTage:POWer<i>:
LEVel:MODE).
When you control it in terms of voltage, the value is a voltage
(V). When you control it in terms of current, the value is the cur-
rent (A).
Range: 0 to 16 V or 2000 mA
*RST: 16 V or 2000 mA
Default unit: V or A
Example: //Define a minimum current of 500 mA
SOUR:VOLT:POW:LEV:LIM:LOW 500MA
Manual operation: See "Defining the output level" on page 167
SOURce:VOLTage:POWer<i>:LEVel:MODE <Mode>
This command selects whether you want to control the output in terms of current or
voltage.
Suffix: .
<i> 1..n
irrelevant
Parameters:
<Mode> CURRent
Control the output in terms of current.
VOLTage
Controls the output in terms of voltage.
*RST: VOLTage
Example: //Control the Vsupply source in terms of voltages
SOUR:VOLT:POW:LEV:MODE VOLT
Manual operation: See "Selecting the output type (Vsupply only)" on page 167
SOURce:VOLTage:POWer<i>:LEVel[:STATe] <State>
This command turns the supply voltage source (Vsupply) on and off.
Note that DC power is actually supplied only if you additionally activate the outputs in
general.
Prerequisites for this command
● Turn on DC power sources (SOURce:VOLTage[:STATe]).
Suffix: .
<i> 1..n
irrelevant
Parameters:
<State> ON | OFF | 1 | 0
*RST: ON
Example: //Turn on the Vsupply voltage source
SOUR:VOLT:POW:LEV ON
Manual operation: See "Turning the output on and off" on page 167
SOURce:VOLTage:POWer<i>:LIMit:HIGH <Voltage>
This command defines the maximum current or voltage that may be supplied by the
Vsupply source.
Suffix: .
<i> 1..n
irrelevant
Parameters:
<Voltage> <numeric value>
The type of value depends on whether you control the output in
terms of current or voltage (SOURce:VOLTage:POWer<i>:
LEVel:MODE).
When you control it in terms of voltage, the value is a current
(A). When you control it in terms of current, the value is a volt-
age (V).
Range: 0 to 16 V or 2000 mA
*RST: 16 V or 2000 mA
Default unit: V or A
Example: //Define a maximum output of 1000 mA
SOUR:VOLT:POW:LEV:MODE VOLT
SOUR:VOLT:POW:LIM:HIGH 1000MA
Manual operation: See "Defining the output level" on page 167
SOURce:VOLTage:SEQuence:RESult?
This command queries the actually measured voltages on the DC power sources.
Prerequisites for this command
● Turn on DC power sources (SOURce:VOLTage[:STATe]).
Example: //Query voltages of the DC power sources
SOUR:VOLT:SEQ:RES?
would return, e.g.
0.000000, -10.000000, -10.000000
Usage: Query only
Manual operation: See "Reading the actual output levels" on page 168
SOURce:VOLTage[:STATe] <State>
This command turns DC power sources on and off in general.
When you turn off the DC power sources, no power is supplied even when you have
turned on one of the sources individually with one of the following commands.
● SOURce:VOLTage:AUX:LEVel[:STATe]
● SOURce:VOLTage:CONTrol<i>:LEVel[:STATe]
● SOURce:VOLTage:POWer<i>:LEVel[:STATe]
Note that you can turn on the global power supply if at least one of the individual sup-
plies has been turned on.
Parameters:
<State> ON | 1
DC power sources are ready for use.
OFF | 0
DC power sources are turned off.
*RST: OFF
Example: //Turn on signal source
SOUR:VOLT:AUX:LEV ON
SOUR:VOLT ON
Manual operation: See "Turning the DC output on and off" on page 166
SOURce:GENerator:DUTBypass.....................................................................................437
SOURce:GENerator:CHANnel:COUPling......................................................................... 437
SOURce:GENerator:FREQuency.....................................................................................438
SOURce:GENerator:FREQuency:STEP........................................................................... 438
SOURce:GENerator:LEVel..............................................................................................438
SOURce:GENerator:MODulation..................................................................................... 439
SOURce:GENerator:PULSe:PERiod................................................................................ 439
SOURce:GENerator:PULSe:TRIGger:OUTPut.................................................................. 439
SOURce:GENerator:PULSe:WIDTh................................................................................. 440
SOURce:GENerator[:STATe]........................................................................................... 440
SOURce:GENerator:DUTBypass <State>
This command turns the DUT bypass on and off.
When you turn on the bypass, the application measures the noise characteristics of the
R&S FSWP.
The DUT bypass is available with the optional Signal Source hardware component.
Parameters:
<State> ON | OFF | 1 | 0
*RST: OFF
Example: //Turn on DUT bypass
SOUR:GEN:DUTB ON
Manual operation: See "Bypassing the DUT" on page 170
SOURce:GENerator:CHANnel:COUPling <State>
This command couples or decouples the signal source configuration across measure-
ment channels.
Parameters:
<State> ON | 1
Signal source configuration is the same across all measurement
channels.
OFF | 0
Signal source configuration is different for each measurement
channel.
*RST: ON
Example: //Use the same signal source configuration across all channels
SOUR:GEN:CHAN:COUP ON
Manual operation: See "Coupling the output configuration across measurement
channels" on page 166
SOURce:GENerator:FREQuency <Frequency>
This command defines the frequency of the signal that is generated by the signal
source.
Parameters:
<Frequency> <numeric value>
Default unit: Hz
Example: See SOURce:GENerator[:STATe] on page 440.
Manual operation: See "Signal source frequency" on page 170
SOURce:GENerator:FREQuency:STEP <Stepsize>
This command defines the frequency stepsize of the signal generated by the optional
signal source.
Parameters:
<Stepsize> 1 mHz | 1 Hz | 1 kHz | 1 MHz | 1 GHz
*RST: 1 MHz
Default unit: Hz
Example: //Define signal source stepsize
SOUR:GEN:FREQ:STEP 1KHZ
Manual operation: See "Signal source frequency" on page 170
SOURce:GENerator:LEVel <Level>
This command defines the level of the signal that is generated by the signal source.
Parameters:
<Level> <numeric value>
Default unit: dBm
Example: See SOURce:GENerator[:STATe] on page 440.
Manual operation: See "Signal source level" on page 170
SOURce:GENerator:MODulation <State>
This command turns internal pulse modulation for pulsed measurements on and off.
Parameters:
<State> ON | 1
A pulse is output on the signal source.
You can define the pulse characteristics with
•SOURce:GENerator:PULSe:PERiod
•SOURce:GENerator:PULSe:WIDTh
OFF | 0
A sine signal is output on the signal source.
*RST: OFF
Example: //Generate and output a pulse on the signal source
SOUR:GEN:MOD ON
SOUR:GEN:PULS:PER 10MS
SOUR:GEN:PULS:WIDT 1MS
Manual operation: See "Pulse modulation state" on page 170
SOURce:GENerator:PULSe:PERiod <PulsePeriod>
This command defines the pulse period (distance between two consecutive pulses) of
the pulse that is generated.
Prerequisites for this command
● Optional pulsed phase noise measurements.
● Turn on signal source (SOURce:GENerator[:STATe]).
● Turn on pulse modulation (SOURce:GENerator:MODulation).
Parameters:
<PulsePeriod> <numeric value>
*RST: 10 ms
Default unit: s
Example: //Generate a pulse with a length of 15 ms and a pulse period of
50 ms.
SOUR:GEN ON
SOUR:GEN:MOD ON
SOUR:GEN:PULS:WIDT 15MS
SOUR:GEN:PULS:PER 50MS
Manual operation: See "Pulse characteristics" on page 171
SOURce:GENerator:PULSe:TRIGger:OUTPut <SignalLevel>
This command selects the signal type provided at the trigger output connector.
The signal can be used, for example, to control an external pulse modulator.
Parameters:
<SignalLevel> HIGH
Provides a high active pulse at the trigger output.
Note that the signal is provided even if internal pulse
modulation has been turned off.
You can define the pulse characteristics with
•SOURce:GENerator:PULSe:WIDTh
•SOURce:GENerator:PULSe:PERiod
LOW
Provides a low active pulse at the trigger output.
Note that the signal is provided even if internal pulse
modulation has been turned off.
OFF | 0
Provides no signal at the trigger output.
*RST: OFF
Example: //Generate a low pulse at the trigger output
SOUR:GENPULS:TRIG:OUTP LOW
Manual operation: See "Pulse characteristics" on page 171
SOURce:GENerator:PULSe:WIDTh <PulseWidth>
This command defines the length of the pulse that is generated.
Prerequisites for this command
● Optional pulsed phase noise measurements.
● Turn on signal source (SOURce:GENerator[:STATe]).
● Turn on pulse modulation (SOURce:GENerator:MODulation).
Parameters:
<PulseWidth> <numeric value>
*RST: 1 ms
Default unit: s
Example: //Generate a pulse with a length of 15 ms
SOUR:GEN ON
SOUR:GEN:MOD ON
SOUR:GEN:PULS:WIDT 15MS
Manual operation: See "Pulse characteristics" on page 171
SOURce:GENerator[:STATe] <State>
This command turns the optional signal source output on and off.
When you turn on the signal source, the R&S FSWP generates a signal with the fre-
quency and level defined with SOURce:GENerator:FREQuency and SOURce:
GENerator:LEVel.
Parameters:
<State> ON | OFF | 1 | 0
*RST: OFF
Example: //Turn on the signal source output
SOUR:GEN:FREQ 100MHZ
//Generate a signal at 100 MHz and a level of -10 dBm.
SOUR:GEN:LEV -10
SOUR:GEN ON
Manual operation: See "Signal source state" on page 170
DIAGnostic:SERVice:NSOurce........................................................................................441
DIAGnostic:SERVice:NSOurce <State>
This command turns the 28 V supply of the BNC connector labeled [noise source
control] on the R&S FSWP on and off.
Parameters:
<State> ON | OFF | 0 | 1
OFF | 0
Switches the function off
ON | 1
Switches the function on
Example: DIAG:SERV:NSO ON
Manual operation: See "Noise Source Control" on page 172
INPut<ip>:UPORt:STATe.................................................................................................441
INPut<ip>:UPORt[:VALue]...............................................................................................442
OUTPut<up>:UPORt:STATe............................................................................................442
OUTPut<up>:UPORt[:VALue]..........................................................................................442
INPut<ip>:UPORt:STATe <State>
This command toggles the control lines of the user ports for the AUX PORT connector.
This 9-pole SUB-D male connector is located on the rear panel of the R&S FSWP.
See the R&S FSWP Getting Started manual for details.
Suffix: .
<ip> 1|2
irrelevant
Parameters:
<State>
ON | 1
User port is switched to INPut
OFF | 0
User port is switched to OUTPut
*RST: 1
INPut<ip>:UPORt[:VALue]
This command queries the control lines of the user ports.
For details see OUTPut<up>:UPORt[:VALue] on page 442.
Suffix: .
<ip> 1|2
irrelevant
Return values:
<Level> bit values in hexadecimal format
TTL type voltage levels (max. 5V)
Range: #B00000000 to #B00111111
Example: INP:UPOR?
//Result: #B00100100
Pins 5 and 7 are active.
OUTPut<up>:UPORt:STATe <State>
This command toggles the control lines of the user ports for the AUX PORT connector.
This 9-pole SUB-D male connector is located on the rear panel of the R&S FSWP.
Suffix: .
<up> irrelevant
Parameters:
<State> ON | OFF | 0 | 1
OFF | 0
User port is switched to INPut
ON | 1
User port is switched to OUTPut
Example: OUTP:UPOR:STAT ON
OUTPut<up>:UPORt[:VALue] <Value>
This command sets the control lines of the user ports.
The assignment of the pin numbers to the bits is as follows:
Bit 7 6 5 4 3 2 1 0
DISPlay[:WINDow<n>]:TRACe<t>:X[:SCALe] <Range>
This command defines the display range of the x-axis.
Prerequisites for this command
● Turn off automatic scaling of the x-axis (DISPlay[:WINDow<n>]:TRACe<t>:
X[:SCALe]:AUTO).
Suffix: .
<n> 1..n
Window
<t> 1..n
irrelevant
Parameters:
<Range> Default unit: Depending on the selected diagram
Example: //Define a value range of 100 MHz.
DISP:TRAC:X:AUTO OFF
DISP:TRAC:X 100 MHz
DISPlay[:WINDow<n>]:TRACe<t>:X[:SCALe]:AUTO <Mode>
This command turns automatic configuration of the horizontal axis on and off.
Suffix: .
<n> 1..n
Window
<t> 1..n
irrelevant
Parameters:
<Mode> ON | 1
Scales the x-axis after each measurement.
OFF | 0
Allows you to define the scale manually.
ONCE
Scales the x-axis once. The scale remains the same for subse-
quent measurements.
*RST: ON
Example: //Select manual scaling of the x-axis.
DISP:TRAC:X:AUTO OFF
DISPlay[:WINDow<n>]:TRACe<t>:X:SPACing?
This command queries the scale of the x-axis in any measurement window.
Suffix: .
<n> 1..n
Window
<t> 1..n
irrelevant
Return values:
<Spacing> LINear
X-axis has a linear scale.
LOGarithmic
X-axis has a logarithmic scale.
Example: //Query scale of the x-axis in the second measurement window
DISP:WIND2:TRAC:X:SPAC?
Usage: Query only
DISPlay[:WINDow<n>]:TRACe<t>:Y[:SCALe] <Range>
This command defines the value range displayed on the y-axis.
Prerequisites for this command
● Turn off automatic scaling of the y-axis (DISPlay[:WINDow<n>]:TRACe<t>:
Y[:SCALe]:AUTO).
Suffix: .
<n> 1..n
Window
<t> 1..n
irrelevant
Parameters:
<Range> <numeric value>
Default unit: Depending on the selected diagram
Example: //Define a value range of 100 dB.
DISP:TRAC:Y:AUTO OFF
DISP:TRAC:Y 100
Manual operation: See "Scaling the y-axis" on page 145
DISPlay[:WINDow<n>]:TRACe<t>:Y[:SCALe]:AUTO <Mode>
This command turns automatic scaling of the y-axis in graphical result displays on and
off.
Suffix: .
<n> 1..n
Window
<t> 1..n
irrelevant
Parameters:
<Mode> ON | 1
Scales the y-axis after each measurement.
OFF | 0
Allows you to define the scale manually.
ONCE
Scales the y-axis once. The scale remains the same for subse-
quent measurements.
*RST: ON
Example: //Select manual scaling of the y-axis.
DISP:TRAC:Y:AUTO OFF
Manual operation: See "Scaling the y-axis" on page 145
See "Scaling the y-axis of the phase diagram" on page 189
DISPlay[:WINDow<n>]:TRACe<t>:Y[:SCALe]:RLEVel <Level>
This command defines the maximum level displayed on the y-axis.
Prerequisites for this command
● Turn off automatic scaling of the y-axis (DISPlay[:WINDow<n>]:TRACe<t>:
Y[:SCALe]:AUTO).
Suffix: .
<n> 1..n
Window
<t> 1..n
irrelevant
Parameters:
<Level> <numeric value>
Default unit: Depending on the selected diagram
Example: //Define maximum level on the y-axis
DISP:TRAC:Y:RLEV -20
Manual operation: See "Scaling the y-axis" on page 145
DISPlay[:WINDow<n>]:TRACe<t>:Y[:SCALe]:RLEVel:LOWer <Level>
This command defines the minimum level displayed on the y-axis.
Prerequisites for this command
● Turn off automatic scaling of the y-axis (DISPlay[:WINDow<n>]:TRACe<t>:
Y[:SCALe]:AUTO).
Suffix: .
<n> 1..n
Window
<t> 1..n
irrelevant
Parameters:
<Level> <numeric value>
Default unit: Depending on the selected diagram
Example: //Query minimum level on the y-axis
DISP:TRAC:Y:RLEV:LOW?
would return, e.g.
-135
Manual operation: See "Scaling the y-axis" on page 145
DISPlay[:WINDow<n>]:TRACe<t>:Y:UNIT <Unit>
This command selects the unit of the y-axis.
INPut<1|2>:ATTenuation <Attenuation>
This command defines the RF attenuation for the RF input.
Prerequisites for this command
● Turn off automatic attenuation configuration (INPut<1|2>:ATTenuation:AUTO).
Suffix: .
<1|2> 1|2
irrelevant
Parameters:
<Attenuation> <numeric value> (integer only)
Range: See data sheet
Increment: 5
Default unit: dB
Example: //Defines an attenuation of 10 dB
INP:ATT:AUTO OFF
INP:ATT 10
Manual operation: See "Attenuating the signal" on page 144
INPut<1|2>:ATTenuation:AUTO <State>
This command turns automatic configuration of the attenuation on and off.
Suffix: .
<1|2> 1|2
irrelevant
Parameters:
<State> ON | 1
Automatically defines the ideal attenuation based on the current
signal level.
OFF | 0
Allows you to define the attenuation manually with
INPut<1|2>:ATTenuation
*RST: ON
Example: //Turn on automatic configuration of the attenuation
INP:ATT:AUTO ON
Manual operation: See "Attenuating the signal" on page 144
[SENSe:]ADJust:CONFigure:LEVel:THReshold <Level>
This command defines the threshold of the signal search.
Prerequisites for this command
● Turn on the automatic signal search with [SENSe:]ADJust:CONFigure:
FREQuency:AUTosearch[:STATe]
Parameters:
<Level> <numeric value>
Default unit: dBm
Example: //Define a threshold of -10 dBm
ADJ:CONF:LEV:THR -10
Manual operation: See "Searching for the signal level" on page 144
[SENSe:]POWer:RLEVel?
This command queries the currently measured signal level.
Return values:
<Level> <numeric value>
Default unit: dBm
Example: //Query signal level
POW:RLEV?
would return, e.g.
-9.28192
Usage: Query only
Manual operation: See "Searching for the signal level" on page 144
[SENSe:]POWer:RLEVel:OFFSet <Offset>
This command defines an arithmetic level offset. The offset is applied to the signal
level.
The level offset takes external attenuation or gain into account.
Parameters:
<Offset> <numeric value>
Range: -100 to 200
*RST: 0
Default unit: dB
Example: //Define a level offset of 20 dB
POW:RLEV:OFFS 20
Manual operation: See "Shifting the level" on page 144
[SENSe:]ADJust:CONFigure:FREQuency:AUTosearch[:STATe].......................................... 449
[SENSe:]ADJust:CONFigure:FREQuency:COUNt............................................................. 449
[SENSe:]ADJust:CONFigure:FREQuency:LIMit:HIGH........................................................450
[SENSe:]ADJust:CONFigure:FREQuency:LIMit:LOW........................................................ 450
[SENSe:]FILTer:LPASs:FREQuency:MANual.................................................................... 451
[SENSe:]FILTer:LPASs[:STATe]....................................................................................... 451
[SENSe:]FREQuency:CENTer......................................................................................... 452
[SENSe:]FREQuency:STARt........................................................................................... 452
[SENSe:]FREQuency:STOP............................................................................................453
[SENSe:]POWer:RLEVel:MODE...................................................................................... 454
[SENSe:]SWEep:CAPTure:RANGe..................................................................................454
[SENSe:]ADJust:CONFigure:FREQuency:AUTosearch[:STATe] <State>
This command turns the automatic (carrier) frequency search on and off.
When you turn of the automatic frequency search, you can define the signal frequency
with [SENSe:]FREQuency:CENTer.
Parameters:
<State> ON | OFF | 1 | 0
Example: //Define a signal frequency of 100 MHz
ADJ:CONF:FREQ:AUT OFF
FREQ:CENT 100MHZ
Manual operation: See "Searching for a signal" on page 148
[SENSe:]ADJust:CONFigure:FREQuency:COUNt <State>
This command turns verification of the signal frequency on and off.
[SENSe:]ADJust:CONFigure:FREQuency:LIMit:HIGH <Frequency>
This command defines the upper limit of the frequency search range.
Prerequisites for this command
● Turn on the automatic signal search with [SENSe:]ADJust:CONFigure:
FREQuency:AUTosearch[:STATe]
Parameters:
<Frequency> <numeric value>
Range: See data sheet
*RST: 8 GHz
Default unit: Hz
Example: //Define a frequency search range from 10 MHz to 500 MHz
ADJ:CONF:FREQ:LIM:LOW 10MHZ
ADJ:CONF:FREQ:LIM:HIGH 500MHZ
Manual operation: See "Searching for a signal" on page 148
[SENSe:]ADJust:CONFigure:FREQuency:LIMit:LOW <Frequency>
This command defines the lower limit of the frequency search range.
Prerequisites for this command
● Turn on the automatic signal search with [SENSe:]ADJust:CONFigure:
FREQuency:AUTosearch[:STATe]
Parameters:
<Frequency> <numeric value>
Range: See data sheet
*RST: 1 MHz
Default unit: Hz
Example: //Define a frequency search range from 10 MHz to 500 MHz
ADJ:CONF:FREQ:LIM:LOW 10MHZ
ADJ:CONF:FREQ:LIM:UPP 500MHZ
Manual operation: See "Searching for a signal" on page 148
[SENSe:]FILTer:LPASs:FREQuency:MANual <Frequency>
This command defines the cutoff frequency of the low pass filter you can use to mea-
sure small carrier frequencies.
Prerequisites for this command
● Turn on low pass filter ([SENSe:]FILTer:LPASs[:STATe]).
Parameters:
<Frequency> <numeric value>
*RST: 1 MHz
Default unit: Hz
Example: //Configure low pass filter
FILT:LPAS ON
FILT:LPAS:FREQ:MAN 500KHZ
Manual operation: See "Low signal frequencies" on page 150
See "Low signal levels" on page 150
[SENSe:]FILTer:LPASs[:STATe] <State>
This command turns a low pass filter for measurements on small carrier frequencies on
and off.
Effects of using thelow pass filter:
● Auto search feature is turned off ([SENSe:]ADJust:CONFigure:FREQuency:
AUTosearch[:STATe]).
● Signal count is turned off ([SENSe:]ADJust:CONFigure:FREQuency:COUNt).
● The stop offset is limited to 30 % of the filter cut-off frequency ([SENSe:
]FREQuency:STOP).
● DC coupling should be used for measurements on carrier frequencies below
1 MHz (INPut<ip>:COUPling).
Parameters:
<State> ON | OFF | 1 | 0
When you turn on the filter, you can define a cutoff frequency
with [SENSe:]FILTer:LPASs:FREQuency:MANual.
*RST: OFF
Example: //Turn on low pass filter
FILT:LPAS ON
Manual operation: See "Low signal frequencies" on page 150
See "Low signal levels" on page 150
[SENSe:]FREQuency:CENTer <Frequency>
CW, pulsed and VCO measurements:
This command defines or queries (in case of automatic frequency search) the current
signal frequency.
Transient measurement:
This command defines the center frequency of the transient measurement.
Parameters:
<Frequency> <numeric value>
Default unit: Hz
Example: //Query signal frequency
FREQ:CENT?
Example: //Define center frequency
FREQ:CENT 1GHZ
Manual operation: See "Defining the signal frequency" on page 147
See "Searching for a signal" on page 148
See "Defining the frequency range of the measurement"
on page 183
[SENSe:]FREQuency:STARt <Frequency>
CW, pulsed and VCO measurements:
This command defines the start frequency offset of the measurement range.
Transient measurement:
This command defines the start frequency of the transient measurement.
Frequency stability measurement:
The start frequency offset is coupled to the stop time of the frequency stability mea-
surement ([SENSe:]TIME:STOP).
If you change the start frequency offset, the stop time is adjusted accordingly. For
example, 1 mHz corresponds to 1000 s.
Parameters:
<Frequency> Offset frequencies in half decade steps.
Range: See data sheet
*RST: 1 kHz
Default unit: Hz
Example: //Define a start offset of 10 kHz
FREQ:STAR 10KHZ
Example: //Define a span of 500 MHz from 500 MHz to 1 GHz
FREQ:STAR 500MHZ
FREQ:STOP 1GHZ
Manual operation: See "Defining the measurement range" on page 149
See "Defining the frequency range of the measurement"
on page 183
[SENSe:]FREQuency:STOP <Frequency>
CW, pulsed and VCO measurements:
This command defines the stop frequency offset of the measurement range.
Transient measurement:
This command defines the stop frequency of the transient measurement.
Frequency stability measurement:
The stop frequency offset is coupled to the start time of the frequency stability mea-
surement ([SENSe:]TIME:STARt).
If you change the stop frequency offset, the start time is adjusted accordingly. For
example, 1 MHz corresponds to 1 ms.
Parameters:
<Frequency> Offset frequencies in half decade steps.
Range: See data sheet
*RST: 1 MHz
Default unit: Hz
Example: //Define a stop offset of 10 MHz
FREQ:STOP 10MHZ
Example: //Define a span of 500 MHz from 500 MHz to 1 GHz
FREQ:STAR 500MHZ
FREQ:STOP 1GHZ
Manual operation: See "Defining the measurement range" on page 149
See "Defining the frequency range of the measurement"
on page 183
[SENSe:]POWer:RLEVel:MODE <Level>
This command selects the level measurement mode.
Parameters:
<Level> HIGH
Use this mode to measure normal signal levels.
LOW
Use this mode to measure low signal levels.
When you select this mode, apply a low pass filter and define its
characteristics with:
•[SENSe:]FILTer:LPASs[:STATe]
•[SENSe:]FILTer:LPASs:FREQuency:MANual
*RST: HIGH
Example: //Measure low level signal
POW:RLEV:MODE LOW
Manual operation: See "Low signal levels" on page 150
[SENSe:]SWEep:CAPTure:RANGe <CaptureRange>
This command selects the signal capture range.
Parameters:
<CaptureRange> NORMal
Normal capture range for stable DUTs or DUTs whose frequency
drifts slowly over a short distance.
WIDE
Wide capture range for DUTs whose frequency drifts quickly and
over big distances.
R40Mhz
This setting is designed to work with carriers swept in -40 MHz
to +40 MHz around the center frequency. Additional spurs and
restrictions of the measurement accuracy are possible for CW
signals. For specifics of the measurement accuracy, refer to the
data sheet.
*RST: NORMal
Example: //Select a wide signal capture range
SWE:CAPT:RANG WIDE
Manual operation: See "Capture Range" on page 149
● Noise Configuration...............................................................................................455
● Residual Calculation Configuration....................................................................... 462
● Spot Noise Configuration...................................................................................... 465
● Spur Display..........................................................................................................469
DISPlay:XGINdicator[:STATe] <State>
This command turns the cross-correlation gain indicator (gray area in the Noise Spec-
trum result display) on and off.
Parameters:
<State> ON | OFF | 1 | 0
*RST: ON
Example: //Remove the gray area from the diagram area.
DISP:XGIN OFF
Manual operation: See "Turning the display of the cross-correlation gain indicator
on and off" on page 156
[SENSe:]LIST:BWIDth[:RESolution]:RATio <Percentage>
This command defines the factor that the resolution bandwidth applied to each half
decade is based on.
More information
Parameters:
<Percentage> <numeric value>
Range: 0.1 to 30
*RST: 10
Default unit: PCT
[SENSe:]LIST:RANGe<r>:BWIDth[:RESolution] <BandWidth>
This command defines the resolution bandwidth applied in a half decade.
The application of the command depends on the half decade configuration mode
([SENSe:]SWEep:MODE):
● Automatic mode: The RBW can only be queried, because it is calculated based on
an RBW factor.
● Manual mode: The RBW can be defined directly as an absolute value.
Suffix: .
<r> 1..n
Half decade
Parameters:
<BandWidth> <numeric value>
*RST: Automatic configuration mode is on.
Default unit: Hz
Example: //Define an RBW of 1 kHz for the fifth half decade
SWE:MODE MAN
LIST:RANG5:BWID 1KHZ
Manual operation: See "Defining the resolution bandwidth" on page 154
See "Working with the half decade configuration table"
on page 157
[SENSe:]LIST:RANGe<r>:FREQuency:STARt?
This command queries the start frequency offset of a half decade.
Suffix: .
<r> 1..n
Half decade
Return values:
<Frequency> <numeric value>
Default unit: Hz
Example: //Query start frequency for fifth half decade
LIST:RANG5:FREQ:STAR?
would return, e.g.
100000
Usage: Query only
Manual operation: See "Working with the half decade configuration table"
on page 157
[SENSe:]LIST:RANGe<r>:FREQuency:STOP?
This command queries the stop frequency offset of a half decade.
Suffix: .
<r> 1..n
Half decade
Return values:
<Frequency> <numeric value>
Default unit: Hz
Example: //Query stop frequency offset for fifth half decade
LIST:RANG5:FREQ:STOP?
would return, e.g.
300000
Usage: Query only
Manual operation: See "Working with the half decade configuration table"
on page 157
[SENSe:]LIST:RANGe<r>:XCOunt <Count>
This command defines the number of cross-correlation operations done in a half dec-
ade.
The application of the command depends on the half decade configuration mode
([SENSe:]SWEep:MODE):
● Automatic mode: The number of cross-correlations can only be queried, because it
is calculated based on an RBW factor.
● Manual mode: The number of cross-correlations can be defined directly as an
absolute value.
Suffix: .
<r> 1..n
Half decade
Parameters:
<Count> <numeric value> (integer only)
*RST: Automatic configuration mode is on.
Default unit: ---
Example: //Define 50 cross-correlation operations for the fifth half decade
SWE:MODE MAN
LIST:RANG5:XCO 50
Manual operation: See "Defining cross-correlation parameters" on page 155
See "Working with the half decade configuration table"
on page 157
[SENSe:]LIST:BWIDth[:RESolution]:USMall <State>
Provides functionality to enable ultra-small resolution bandwidths (RBW) for the current
measurement.
Parameters:
<State> ON | OFF | 1 | 0
*RST: OFF
Example: SENS:LIST:BWID:RES:USM ON
Manual operation: See "Ultra-Small RBWs" on page 154
[SENSe:]SWEep:COUNt <SweepCount>
This command defines the number of measurements that the application uses to aver-
age traces.
In continuous measurement mode, the application calculates the moving average over
the average count.
In single measurement mode, the application stops the measurement and calculates
the average after the average count has been reached.
Parameters:
<SweepCount> When you set a sweep count of 0 or 1, the R&S FSWP performs
one single measurement in single measurement mode.
In continuous measurement mode, if the sweep count is set to 0,
a moving average over 10 measurements is performed.
Range: 0 to 200000
*RST: 0
Example: SWE:COUN 64
Sets the number of measurements to 64.
INIT:CONT OFF
Switches to single measurement mode.
INIT;*WAI
Starts a measurement and waits for its end.
Manual operation: See " Sweep/Average Count " on page 157
[SENSe:]SWEep:FORWard <SweepForward>
This command selects the sweep direction.
Parameters:
<SweepForward> ON
Measurement in forward direction.
OFF
Measurement in reverse direction.
*RST: OFF
[SENSe:]SWEep:FSEGment
This command stops a measurement in any given half decade and resumes the mea-
surement of the next half decade.
Usage: Event
Manual operation: See "Defining cross-correlation parameters" on page 155
[SENSe:]SWEep:MODE <Mode>
This command selects the configuration mode of the half decade table.
Parameters:
<Mode> MANual
Manual mode: allows you to select a custom resolution band-
width and number of cross-correlations for each half decade.
• Define the RBW for a half decade with [SENSe:]LIST:
RANGe<r>:BWIDth[:RESolution].
• Define the number of cross-correlations for a half decade with
[SENSe:]LIST:RANGe<r>:XCOunt.
NORMal
Automatic mode: the application selects the resolution band-
width and number of cross-correlations based on the RBW and
XCORR factors.
• Define the RBW factor with [SENSe:]LIST:BWIDth[:
RESolution]:RATio.
• Define the XCORR factor with [SENSe:]SWEep:XFACtor.
*RST: NORMal
Example: //Automatically select RBW and XCORR based on an RBW fac-
tor of 5 % and an XCORR factor of 1.5.
SWE:MODE NORM
LIST:BWID:RAT 5
LIST:RANG5:XCO 1.5
Manual operation: See "Defining the resolution bandwidth" on page 154
See "Defining cross-correlation parameters" on page 155
See "Working with the half decade configuration table"
on page 157
[SENSe:]SWEep:TIME <Time>
CW, pulsed and VCO measurements (query only):
This command queries the estimated measurement time.
Transient measurement:
This command defines the measurement time
Parameters:
<Time> <numeric value>
Default unit: s
Example: //Query measurement time
SWE:TIME?
would return, e.g.
0.050432
Example: //Define measurement time
SWE:TIME 2S
Manual operation: See "Estimating the measurement time" on page 153
See "Defining the measurement time" on page 187
[SENSe:]SWEep:XFACtor <Factor>
This command defines the cross-correlation factor (XCORR factor) that defines the
cross-correlation operations in each half decade.
Parameters:
<Factor> <numeric value>
Range: 1
Example: //Define an XCORR factor of 10
SWE:XFAC 10
Manual operation: See "Defining cross-correlation parameters" on page 155
[SENSe:]SWEep:XOPTimize[:STATe] <State>
This command turns optimization of the cross-correlation operations on and off.
Parameters:
<State> ON | OFF | 1 | 0
*RST: ON
Example: SWE:XOPT OFF
Turns off optimization (always performs the full number of opera-
tions).
Manual operation: See "Defining cross-correlation parameters" on page 155
[SENSe:]SWEep:XOPTimize:THReshold <Threshold>
This command defines the threshold for the cross-correlation optimization feature.
When the threshold (distance between measured values and gain indicator) is reached
in any given half decade, the measurement in that half decade stops and resumes to
measure the next one.
[SENSe:]TIME:STARt <Tau>
This command defines the start time for the frequency stability measurements.
Effects of this command
● The start time is coupled to the stop frequency offset of the measurement range of
the phase noise measurement ([SENSe:]FREQuency:STOP).
If you change the start time, the R&S FSWP adjusts the stop frequency offset
accordingly. For example, 1 MHz stop offset corresponds to 1 µs.
Parameters:
<Tau> <numeric value>
*RST: 1 ms
Default unit: s
Example: //Define start time for frequency stability measurement
TIME:STAR 1US
Manual operation: See "Defining the measurement range" on page 149
[SENSe:]TIME:STOP <Tau>
This command defines the stop time for the frequency stability measurements.
Effects of this command
● The stop time is coupled to the start frequency offset of the measurement range of
the phase noise measurement ([SENSe:]FREQuency:STARt).
If you change the stop time, the R&S FSWP adjusts the start frequency offset
accordingly. For example, 1 mHz start offset corresponds to 1000 s.
Parameters:
<Tau> <numeric value>
*RST: 1 ms
Default unit: s
Example: //Define stop time for frequency stability measurement
TIME:STAR 1000S
Manual operation: See "Defining the measurement range" on page 149
CALCulate<n>[:RANGe<j>]:EVALuation:STARt <Frequency>
This command defines the start frequency of a custom integration range for residual
effects calculation.
Prerequisites for this command
● Turn off integration over the complete measurement range (CALCulate<n>[:
RANGe<j>]:EVALuation[:STATe]).
Suffix: .
<n> Window
<j> Integration range
Parameters:
<Frequency> <numeric value>
Range: Depends on the measurement range.
*RST: 1 MHz
Default unit: Hz
Example: See CALCulate<n>[:RANGe<j>]:EVALuation[:STATe].
Manual operation: See "Defining the integration range" on page 159
CALCulate<n>[:RANGe<j>]:EVALuation:STOP <Frequency>
This command defines the stop frequency of a custom integration range for residual
effects calculation.
Prerequisites for this command
● Turn off integration over the complete measurement range (CALCulate<n>[:
RANGe<j>]:EVALuation[:STATe]).
Suffix: .
<n> Window
<j> Integration range
Parameters:
<Frequency> <numeric value>
Range: Depends on the measurement range.
*RST: 1 kHz
Default unit: Hz
Example: See CALCulate<n>[:RANGe<j>]:EVALuation[:STATe].
Manual operation: See "Defining the integration range" on page 159
CALCulate<n>[:RANGe<j>]:EVALuation:TRACe <Trace1>
This command selects the trace for calculation of residual effects.
Suffix: .
<n> Window
<j> Integration range
Parameters:
<Trace1> TRACE1 | ... | TRACE6
Selects the trace. You can select a trace that is inactive, but for
residual effect calculation, it must be active.
NONE
Turns off residual calculation for the respective range.
*RST: Depends on the range.
Example: //Use trace 1 as the data source for range 2
CALC:RANG2:EVAL:TRAC TRACE1
Manual operation: See "Selecting the trace for residual calculations" on page 159
CALCulate<n>[:RANGe<j>]:EVALuation[:STATe] <State>
This command turns integration of the entire measurement range for residual calcula-
tions on and off.
Suffix: .
<n> Window
<j> Integration range
Parameters:
<State> ON | 1
Integrates over the complete measurement range.
OFF | 0
Integrates over a custom measurement range.
Example: //Define an integration range from 1 kHz to 3 kHz in range 2
CALC:RANG2:EVAL OFF
CALC:RANG2:EVAL:STAR 100000
CALC:RANG2:EVAL:STOP 300000
Manual operation: See "Defining the integration range" on page 159
CALCulate<n>[:RANGe<j>]:EVALuation:WEIGhting <Name>
This command selects a weighting filter whose values are applied to the calculation of
residual effects.
Suffix: .
<n> Window
<j> Integration range
Setting parameters:
<Name> String containing the name of the filter.
*RST: NONE
Example: //Apply a weighting filter to the residual calculations in integration
range 1
CALC:RANG1:EVAL:WEIG 'A FILTER'
Manual operation: See "Applying weighting filters" on page 159
[SENSe:]CORRection:WEIGhting:COMMent <Name>
This command defines a comment for a weighting filter whose values are applied to
the calculation of residual effects.
Setting parameters:
<Name> String containing the comment.
Example: See [SENSe:]CORRection:WEIGhting:NAME on page 465.
Manual operation: See "Designing weighting filters" on page 160
[SENSe:]CORRection:WEIGhting:DELete
This command deletes the currently selected weighting filter.
[SENSe:]CORRection:WEIGhting:NAME <Name>
This command defines the name for a weighting filter whose values are applied to the
calculation of residual effects.
Setting parameters:
<Name> String containing the name of the filter.
Example: //Create a weighting filter called "FILTER", with a comment and
a few data points
CORR:WEIG:NAME 'FILTER'
CORR:WEIG:COMM 'Here's an example for a
filter.'
CORR:WEIG:DATA 10MHZ,0DB,20MHZ,2DB,40MHZ,5DB
Manual operation: See "Designing weighting filters" on page 160
[SENSe:]CORRection:WEIGhting:SELect <Name>
This command selects a weighting filter whose values are applied to the calculation of
residual effects.
Setting parameters:
<Name> String containing the name of the weighting filter.
Example: //Select a weighting filter called "filter"
CORR:WEIG:SEL 'FILTER'
Manual operation: See "Managing weighting filters" on page 159
CALCulate<n>:SNOise<s>:AOFF.................................................................................... 466
CALCulate<n>:SNOise<s>:STATe................................................................................... 466
CALCulate<n>:SNOise<s>:X.......................................................................................... 466
CALCulate<n>:SNOise<s>[:TRACe<t>]:DECades:X?........................................................ 467
CALCulate<n>:SNOise<s>[:TRACe<t>]:DECades:Y?........................................................ 467
CALCulate<n>:SNOise<s>[:TRACe<t>]:DECades[:STATe].................................................468
CALCulate<n>:SNOise<s>[:TRACe<t>]:USERdefined[:STATe]........................................... 468
CALCulate<n>:SNOise<s>[:TRACe<t>]:Y?.......................................................................468
DISPlay:SNINfo[:STATe]................................................................................................. 469
DISPlay:SNINfo:TRACe..................................................................................................469
CALCulate<n>:SNOise<s>:AOFF
This command turns all spot noise information off (custom and 10x information). It also
turns user defined spot noise markers off.
In the Spot Noise vs Tune measurement, the command also selects "Trace Mode" =
"Blank" for all traces.
Suffix: .
<n> irrelevant
<s> irrelevant
Example: //Turn off all spot noise information
CALC:SNO:AOFF
Usage: Event
CALCulate<n>:SNOise<s>:STATe <State>
This command turns a custom spot noise position on and off.
In the Spot Noise vs Tune measurement, turning off a spot noise position also selects
"Trace Mode" = "Blank" for the corresponding spot noise trace. Turning on a spot noise
position selects the trace mode that was selected last for the corresponding spot noise
trace.
Suffix: .
<n> irrelevant
<s> Spot noise marker
Parameters:
<State> ON | OFF | 1 | 0
*RST: All ON
Example: See CALCulate<n>:SNOise<s>[:TRACe<t>]:
USERdefined[:STATe].
CALCulate<n>:SNOise<s>:X <Frequency>...
This command defines the horizontal position of a custom spot noise position. The
position is changed in all windows.
Suffix: .
<n> irrelevant
<s> Spot noise marker
Parameters:
<Frequency> For minimum and maximum offsets, refer to the data sheet.
The default values are the decade edges (1 kHz, 10 kHz etc.)
Default unit: Hz
CALCulate<n>:SNOise<s>[:TRACe<t>]:DECades:X?
This command queries the horizontal position of the 10x offset frequency spot noise
information.
Suffix: .
<n> irrelevant
<s> irrelevant
<t> irrelevant
Return values:
<Frequency> List of offset frequencies, one for each 10x spot noise position.
The number of return values depends on the measurement
range.
Default unit: Hz
Example: //Query spot noise information
CALC:SNO:DEC:X?
would return, e.g.
1000,10000,100000,1000000
Usage: Query only
Manual operation: See "Spot Noise" on page 116
CALCulate<n>:SNOise<s>[:TRACe<t>]:DECades:Y?
This command queries the vertical position of the 10x offset frequency spot noise infor-
mation.
Suffix: .
<n> Window
<s> irrelevant
<t> Trace
Return values:
<Level> List of phase noise level values, one for each 10x spot noise
positions.
The number of return values depends on the measurement
range.
Default unit: dBc/Hz
Example: //Query spot noise information
CALC:SNO:DEC:Y?
would return, e.g.
-152.560974121094,-136.443389892578,
-145.932891845703,-152.560974121094
CALCulate<n>:SNOise<s>[:TRACe<t>]:DECades[:STATe] <State>
This command turns the spot noise calculation on every 10x offset frequency on and
off.
Suffix: .
<n> irrelevant
<s> irrelevant
<t> irrelevant
Parameters:
<State> ON | OFF | 1 | 0
*RST: ON
Example: //Turn on the spot noise calculation for all decade edges.
CALC:SNO:DEC ON
CALCulate<n>:SNOise<s>[:TRACe<t>]:USERdefined[:STATe] <State>
This command turns calculation of custom spot noise positions on and off
Suffix: .
<n> irrelevant
<s> irrelevant
<t> irrelevant
Parameters:
<State> ON | OFF | 1 | 0
*RST: OFF
Example: //Turn on user defined spot noise positions
CALC:SNO:USER ON
//Turn on custom spot noise marker 2 at an offset of 500 kHz
CALC:SNO3:STAT ON
CALC:SNO3:X 500000
//Query spot noise
CALC:SNO3:Y?
would return, e.g.
-90.1154022217
CALCulate<n>:SNOise<s>[:TRACe<t>]:Y?
This command queries the level measured for a custom spot noise position.
DISPlay:SNINfo[:STATe] <State>
This command turns the display of spot noise information in the diagram area on and
off.
Parameters:
<State> ON | OFF | 1 | 0
*RST: ON
Example: //Display the spot noise information
DISP:SNIN ON
Manual operation: See "Displaying spot noise information" on page 161
DISPlay:SNINfo:TRACe <Trace>
This command selects the trace for which spot noise information is evaluated.
Parameters:
<Trace> Range: 1 to 6
*RST: 1
Example: //Evaluate spot noise for trace 2.
DISP:SNIN:TRAC 2
Manual operation: See "Displaying spot noise information" on page 161
DISPlay[:WINDow<n>]:TRACe<t>:SPURs:SUPPress........................................................ 470
DISPlay[:WINDow<n>]:TRACe<t>:SPURs:THReshold.......................................................470
[SENSe:]SPURs:SORT.................................................................................................. 471
[SENSe:]SPURs:WEIGhting............................................................................................471
[SENSe:]SPURs:FILTer:MODE........................................................................................471
[SENSe:]SPURs:FILTer:HARMonics................................................................................ 472
[SENSe:]SPURs:FILTer:RANGe...................................................................................... 472
[SENSe:]SPURs:FILTer:NAME?...................................................................................... 472
[SENSe:]SPURs:FILTer:OFFSet...................................................................................... 472
[SENSe:]SPURs:FILTer:CLEar........................................................................................ 473
[SENSe:]SPURs:FILTer:SAVE......................................................................................... 473
[SENSe:]SPURs:FILTer:LOAD.........................................................................................473
[SENSe:]SPURs:COLor..................................................................................................473
DISPlay[:WINDow<n>]:TRACe<t>:SPURs:SUPPress <State>
This command turns spur removal for a specific trace on and off.
When you turn on spur removal, you can define a level threshold with DISPlay[:
WINDow<n>]:TRACe<t>:SPURs:THReshold.
In the Spot Noise vs Tune measurement, you can only remove spurs over all traces.
Use [SENSe:]SPURs:SUPPress in that case.
Suffix: .
<n> 1..n
Window
<t> 1..n
Trace
Parameters:
<State> ON | OFF | 1 | 0
*RST: OFF
Example: See DISPlay[:WINDow<n>]:TRACe<t>:SMOothing[:
STATe].
Manual operation: See "Hiding spurs" on page 162
DISPlay[:WINDow<n>]:TRACe<t>:SPURs:THReshold <Threshold>
This command defines a level threshold for spur removal.
Prerequisites for this command
● Turn on spur removal (DISPlay[:WINDow<n>]:TRACe<t>:SPURs:THReshold
).
In the Spot Noise vs Tune measurement, you can only define a threshold that applies
to all traces. Use [SENSe:]SPURs:THReshold in that case.
Suffix: .
<n> 1..n
Window
<t> 1..n
Trace
Parameters:
<Threshold> <numeric value>
*RST: 0
Default unit: dB
Example: See DISPlay[:WINDow<n>]:TRACe<t>:SMOothing[:
STATe].
Manual operation: See "Hiding spurs" on page 162
[SENSe:]SPURs:SORT <Order>
This command selects the sort order of the spurs in the spur list.
Parameters:
<Order> POWer
Sorts spurs according to their power.
OFFSet
Sorts spurs according to their offset from the carrier.
*RST: POWer
Example: //Select spur sort order
SPUR:SORT POW
Manual operation: See "Sorting spurs" on page 163
[SENSe:]SPURs:WEIGhting <Weightingfilter>
This command selects a spurious weighting filter.
Setting parameters:
<Weightingfilter>
Example: //Select no defined weighting filter
SENS:SPUR:WEIG NONE
Manual operation: See "Applying a spurious weighting filter" on page 163
[SENSe:]SPURs:FILTer:MODE <Mode>
This command defines the spurious filter mode
Parameters:
<Mode> OFF | SUPPress | SHOW
OFF
No spurious filter is applied.
SUPPress
The spurs in the spurious filter are removed from the spurious
list, the diagram and dependent calculations.
SHOW
Only the spurs in the spurious filter are displayed in the spurious
list, the diagram and dependent calculations.
Example: SENS:SPUR:FILT:MOD OFF
Manual operation: See "Filtering spurs" on page 163
[SENSe:]SPURs:FILTer:HARMonics <State>
This command defines if harmonics are included in the spurious filter.
Parameters:
<State>
Example: //Exclude harmonics from the spurious filter
SENS:SPUR:FILT:HARM OFF
Manual operation: See "Filtering spurs" on page 163
[SENSe:]SPURs:FILTer:RANGe <Range>
This command defines the range of the spurious filter. The range is defined as a multi-
ple of the resolution bandwidth.
Parameters:
<Range>
Example: SENS:SPUR:FILT:RANG 1
Manual operation: See "Filtering spurs" on page 163
[SENSe:]SPURs:FILTer:NAME?
This command returns the name of the selected spurious filter.
Example: SENS:SPUR:FILT:NAME?
Usage: Query only
Manual operation: See "Filtering spurs" on page 163
[SENSe:]SPURs:FILTer:OFFSet <OffsetValues>...
This command creates a new offset table with defined frequency ranges.
Parameters:
<OffsetValues> Default unit: Hz
Example: SENS:SPUR:FILT:OFFS 1.3e3, 2.6e5
Manual operation: See "Filtering spurs" on page 163
[SENSe:]SPURs:FILTer:CLEar
This command clears the currently selected spurious filter.
Example: SENS:SPUR:FILT:CLE
Usage: Event
Manual operation: See "Filtering spurs" on page 163
[SENSe:]SPURs:FILTer:SAVE <Filename>
This command saves the spurious filter configuration to a file. The spurious filter name
can be defined.
Location of filter files: C:\R_S\instr\SpuriousFilter\
Setting parameters:
<Filename>
Example: SENS:SPUR:FILT:SAVE "MyFile"
Usage: Setting only
Manual operation: See "Filtering spurs" on page 163
[SENSe:]SPURs:FILTer:LOAD <Filename>
This command loads an existing spurious filter configuration from a file.
Location of filter files: C:\R_S\instr\SpuriousFilter\
Setting parameters:
<Filename>
Example: SENS:SPUR:FILT:LOAD "MyFile"
Usage: Setting only
Manual operation: See "Filtering spurs" on page 163
[SENSe:]SPURs:COLor <Color>
Provides functionality to enable an automatic shift of the color of the displayed spurious
lines.
Parameters:
<Color> TRACe | SHIFted
Example: SENS:SPUR:COL TRAC
Manual operation: See "Defining the spurious color" on page 163
[SENSe:]SWEep:EGATe:HOLDoff....................................................................................474
[SENSe:]SWEep:EGATe:LENGth.....................................................................................474
[SENSe:]SWEep:EGATe:LEVel........................................................................................475
[SENSe:]SWEep:EGATe:TYPE........................................................................................475
[SENSe:]SWEep:PULSe:DETection................................................................................. 475
[SENSe:]SWEep:PULSe:GATE....................................................................................... 476
[SENSe:]SWEep:PULSe:PRI.......................................................................................... 476
[SENSe:]SWEep:EGATe:HOLDoff <GateDelay>
This command defines the gate delay time.
Prerequisites for this command
● Optional pulsed phase noise measurement application.
● Turn off automatic pulse detection ([SENSe:]SWEep:PULSe:DETection).
Parameters:
<GateDelay> <numeric value>
*RST: Automatic pulse detection is on.
Default unit: s
Example: //Define a gate delay of 10 µs.
SWE:PULS:DET MAN
SWE:EGAT:HOLD 10us
Manual operation: See "Defining the shape of the gate" on page 175
[SENSe:]SWEep:EGATe:LENGth <Length>
This command defines the gate length.
Prerequisites for this command
● Optional pulsed phase noise measurement application.
● Turn off automatic pulse detection ([SENSe:]SWEep:PULSe:DETection).
● Select gate mode "Edge" ([SENSe:]SWEep:EGATe:TYPE).
Parameters:
<Length> <numeric value>
*RST: Automatic pulse detection is on.
Default unit: s
Example: //Define a gate length of 200 µs
SWE:PULS:DET MAN
SWE:EGAT:TYPE EDGE
SWE:EGAT:LENG 200us
Manual operation: See "Defining the shape of the gate" on page 175
[SENSe:]SWEep:EGATe:LEVel <Level>
This command defines the gate level.
Prerequisites for this command
● Optional pulsed phase noise measurement application.
● Turn off automatic pulse detection ([SENSe:]SWEep:PULSe:DETection).
Parameters:
<Level> <numeric value>
*RST: Automatic pulse detection is on.
Default unit: dBm
Example: //Define a gate level of -10 dBm
SWE:PULS:DET MAN
SWE:EGAT:LEV -10
Manual operation: See "Defining the shape of the gate" on page 175
[SENSe:]SWEep:EGATe:TYPE <GateType>
This command selects the gate type.
Prerequisites for this command
● Optional pulsed phase noise measurement application.
Parameters:
<GateType> EDGE
The gate opens when the gate level has been exceeded and
closes when the time defined by the gate length has elapsed.
LEVel
The gate opens when the gate level has been exceeded and
closes when the signal level again falls below the gate level.
OFF
The gate is off.
Example: //Select gate type
SWE:EGAT:TYPE EDGE
Manual operation: See "Selecting the gate type" on page 175
[SENSe:]SWEep:PULSe:DETection <Mode>
This command selects the pulse detection mode.
[SENSe:]SWEep:PULSe:GATE <PulseGate>
This command selects the source for the pulse gate.
Parameters:
<PulseGate> EXTernal
Selects an external pulse gate connected to trigger 1 connector.
Prerequisites:
• Turn off trigger 1 output (SOURce:GENerator:PULSe:
TRIGger:OUTPut).
Effects:
• Pulse modulation is turned off (SOURce:GENerator:
MODulation).
IFPower
Selects the internal IF power pulse gate.
*RST: IFPower
Example: //Select internal pulse gate
SWE:PULS:GATE IFP
Manual operation: See "Selecting the source for pulse gating" on page 174
[SENSe:]SWEep:PULSe:PRI <Time>
This command defines the pulse repetition interval.
Prerequisites for this command
● Optional pulsed phase noise measurement application.
● Turn off automatic pulse detection ([SENSe:]SWEep:PULSe:DETection).
Parameters:
<Time> <numeric value>
*RST: Automatic pulse detection is on.
Default unit: s
Example: //Define a pulse repetition interval of 500 µs.
SWE:PULS:DET MAN
SWE:PULS:PRI 500US
Manual operation: See "Defining the pulse repetition interval" on page 175
● Sweep Configuration.............................................................................................477
CONFigure:VCO:FIX:SOURce........................................................................................ 477
CONFigure:VCO:SWEep:DELay:INITial........................................................................... 477
CONFigure:VCO:SWEep:DELay[:POINt].......................................................................... 478
CONFigure:VCO:SWEep:FCOunter:RESolution................................................................478
CONFigure:VCO:SWEep:POINts.....................................................................................478
CONFigure:VCO:SWEep:SOURce.................................................................................. 479
CONFigure:VCO:SWEep:STARt......................................................................................479
CONFigure:VCO:SWEep:STOP...................................................................................... 479
CONFigure:VCO:FIX:SOURce <PowerSource>
This command selects the DC source that is considered in the Current / Voltage result
display.
Parameters:
<PowerSource> VAUX
Selects the Vaux connector.
VSUPply
Selects the Vsupply connector.
VTUNe
Selects the Vtune connector.
*RST: VSUPply
Example: //Measure the Vaux connector in the Supply Current / Voltage
result.
CONF:VCO:FIX:SOUR VAUX
CONFigure:VCO:SWEep:DELay:INITial <SettlingTime>
This command defines an initial delay time that allows the DUT to settle before the first
measurement starts.
Parameters:
<SettlingTime> <numeric value>
*RST: 10 ms
Default unit: s
Example: //Define an initial settling time of a 100 ms.
CONF:VCO:SWE:DEL:INIT 100MS
Manual operation: See "Defining the settling time" on page 179
CONFigure:VCO:SWEep:DELay[:POINt] <SettlingTime>
This command defines a delay time that allows the DUT to settle when a new tuning
voltage is applied and before the measurement starts.
Parameters:
<SettlingTime> <numeric value>
*RST: 10 ms
Default unit: s
Example: //Define a settling time of a 100 ms.
CONF:VCO:SWE:DEL 100MS
Manual operation: See "Defining the settling time" on page 179
CONFigure:VCO:SWEep:FCOunter:RESolution <Frequency>
This command selects the frequency resolution for VCO characterization.
Parameters:
<Frequency> <numeric value>
If you select a frequency resolution that is not supported, the
next available frequency resolution is selected.
*RST: 1 kHz
Default unit: Hz
Example: //Select a frequency resolution of 100 Hz.
CONF:VCO:SWE:FCO 100HZ
Manual operation: See "Selecting the frequency resolution" on page 179
CONFigure:VCO:SWEep:POINts <MeasPoints>
This command defines the number of measurement points for the VCO measurement.
Parameters:
<MeasPoints> <numeric value> (integer only)
*RST: 10
Example: See CONFigure:VCO:SWEep:SOURce.
Manual operation: See "Defining the sweep range" on page 178
CONFigure:VCO:SWEep:SOURce <PowerSource>
This command selects the source (connector) which tunes the VCO.
Parameters:
<PowerSource> VAUX
Selects the Vaux connector as the sweep source.
VSUPly
Selects the Vsupply connector as the sweep source.
VTUNe
Selects the Vtune connector as the sweep source.
CONFigure:VCO:SWEep:STARt <Value>
This command defines the start value of the tuning range.
Parameters:
<Value> <numeric value>
The unit depends on whether you tune the VCO with a voltage
or current (see CONFigure:VCO:SWEep:SOURce).
*RST: 0
Default unit: V or A
Example: See CONFigure:VCO:SWEep:SOURce.
Manual operation: See "Defining the sweep range" on page 178
CONFigure:VCO:SWEep:STOP <Value>
This command defines the stop value of the tuning range.
Parameters:
<Value> <numeric value>
The unit depends on whether you tune the VCO with a voltage
or current (see CONFigure:VCO:SWEep:SOURce).
*RST: 0
Default unit: V or A
Example: See CONFigure:VCO:SWEep:SOURce.
● Sweep Configuration.............................................................................................480
● Trace Configuration...............................................................................................482
CONFigure:SNTune:SWEep:DELay:INITial.......................................................................480
CONFigure:SNTune:SWEep:DELay[:POINt]..................................................................... 480
CONFigure:SNTune:SWEep:POINts................................................................................ 480
CONFigure:SNTune:SWEep:SOURce..............................................................................481
CONFigure:SNTune:SWEep:STARt................................................................................. 481
CONFigure:SNTune:SWEep:STOP..................................................................................481
CONFigure:SNTune:SWEep:DELay:INITial <SettlingTime>
This command defines an initial delay time that allows the DUT to settle before the first
measurement starts.
Parameters:
<SettlingTime> <numeric value>
*RST: 10 ms
Default unit: s
Example: //Define an initial settling time of a 100 ms.
CONF:VCO:SWE:DEL:INIT 100MS
Manual operation: See "Defining the settling time" on page 179
CONFigure:SNTune:SWEep:DELay[:POINt] <SettlingTime>
This command defines a delay time that allows the DUT to settle when a new tuning
voltage is applied and before the measurement starts.
Parameters:
<SettlingTime> <numeric value>
*RST: 10 ms
Default unit: s
Example: //Define a settling time of a 100 ms
CONF:SNT:SWE:DEL 100MS
Manual operation: See "Defining the settling time" on page 179
CONFigure:SNTune:SWEep:POINts <MeasPoints>
This command defines the number of measurement points for the VCO measurement.
Parameters:
<MeasPoints> <numeric value> (integer only)
*RST: 10
Example: See CONFigure:SNTune:SWEep:SOURce.
Manual operation: See "Defining the sweep range" on page 178
CONFigure:SNTune:SWEep:SOURce <PowerSource>
This command selects the source (connector) which tunes the VCO.
Parameters:
<PowerSource> VAUX
Selects the Vaux connector as the sweep source.
VSUPly
Selects the Vsupply connector as the sweep source.
VTUNe
Selects the Vtune connector as the sweep source.
CONFigure:SNTune:SWEep:STARt <Value>
This command defines the start value of the tuning range.
Parameters:
<Value> <numeric value>
The unit depends on whether you tune the VCO with a voltage
or current (see CONFigure:SNTune:SWEep:SOURce).
*RST: 0
Default unit: V or A
Example: See CONFigure:SNTune:SWEep:SOURce.
Manual operation: See "Defining the sweep range" on page 178
CONFigure:SNTune:SWEep:STOP <Value>
This command defines the stop value of the tuning range.
Parameters:
<Value> <numeric value>
The unit depends on whether you tune the VCO with a voltage
or current (see CONFigure:SNTune:SWEep:SOURce).
*RST: 0
Default unit: V or A
Example: See CONFigure:SNTune:SWEep:SOURce.
Manual operation: See "Defining the sweep range" on page 178
[SENSe:]SMOothing:APERture <Value>
This command defines the magnitude (aperture) of trace smoothing.
Prerequisites for this command
● Select Spot Noise vs Tune measurement (CONFigure:SNTune:MEASurement[:
STATe]).
● Turn on trace smoothing ([SENSe:]SMOothing[:STATe]).
This command smoothes all traces. If you need to smooth each trace separately (pos-
sible in all measurements except Spot Noise vs Tune), use DISPlay[:WINDow<n>]:
TRACe<t>:SMOothing:APERture.
Parameters:
<Value> <numeric value>
Range: 1 to 20
*RST: 1
Default unit: PCT
Example: //Smooth the traces by a magnitude of 10 %
SMO ON
SMO:APER 10
Manual operation: See "Smoothing traces" on page 208
[SENSe:]SMOothing[:STATe] <State>
This command turns trace smoothing for a specific trace on and off.
When you turn on trace smoothing, you can define the smoothing magnitude
with[SENSe:]SMOothing:APERture .
Prerequisites for this command
● Select Spot Noise vs Tune measurement (CONFigure:SNTune:MEASurement[:
STATe]).
This command smoothes all traces. If you need to smooth each trace separately (pos-
sible in all measurements except Spot Noise vs Tune), use DISPlay[:WINDow<n>]:
TRACe<t>:SMOothing[:STATe].
Parameters:
<State> ON | OFF | 1 | 0
Example: //Smooth the traces by a magnitude of 10 %
SMO ON
SMO:APER 10
Manual operation: See "Smoothing traces" on page 208
[SENSe:]SPURs:SUPPress <State>
This command turns spur removal for all traces and windows on and off.
When you turn on spur removal, you can define a level threshold with [SENSe:
]SPURs:THReshold.
Prerequisites for this command
● Select Spot Noise vs Tune measurement (CONFigure:SNTune:MEASurement[:
STATe]).
If you need to remove spurs for each trace separately (possible in all measurements
except Spot Noise vs Tune), use DISPlay[:WINDow<n>]:TRACe<t>:SPURs:
SUPPress.
Parameters:
<State> ON | OFF | 1 | 0
Example: //Remove spurs
SPUR:SUPP ON
Manual operation: See "Hiding spurs" on page 162
[SENSe:]SPURs:THReshold <Threshold>
This command defines a level threshold for spur removal.
Prerequisites for this command
● Select Spot Noise vs Tune measurement (CONFigure:SNTune:MEASurement[:
STATe]).
● Frequency Configuration.......................................................................................484
● Amplitude Configuration........................................................................................487
● Data Acquisition.................................................................................................... 487
● Trigger Configuration............................................................................................ 488
● Y-Axis Scale.......................................................................................................... 491
● Settling Time......................................................................................................... 495
● Frequency Deviation............................................................................................. 497
● Trace Configuration...............................................................................................499
● Marker Configuration.............................................................................................499
● Limit Lines............................................................................................................. 499
CONFigure:TRANsient:MODE <OrderBy>
This command selects the transient measurement mode.
Parameters:
<OrderBy> NARRow
Narrowband mode: For measurement with a frequency span <
40 MHz.
If you define a span < 40 MHz while wideband is selected, or
define a frequency range outside the supported frequency
range, the R&S FSWP automatically selects narrowband mode
and adjusts the center, start and stop frequencies, if necessary.
WIDE
Wideband mode: For measurements with a frequency span > 40
MHz, but only in frequency range between 276 MHz and
7.980 GHz.
If you define a span > 40 MHz while narrowband mode is
selected, the R&S FSWP automatically selects wideband mode,
and adjusts the center, start and stop frequencies, if necessary.
*RST: WIDE
Example: //Configure measurement with wideband mode
FREQ:CENT 1GHZ
FREQ:SPAN 100MHZ
CONF:TRAN:MODE?
//returns
WIDE
//Select narrowband mode instead - keeps center frequency but
reduces span
CONF:TRAN:MODE NARR
FREQ:CENT?
//returns
1000000000
FREQ:SPAN?
//returns
40000000
Manual operation: See "Selecting the measurement mode" on page 182
[SENSe:]FREQuency:CENTer:STEP <Frequency>
This command defines a frequency stepsize.
Prerequisites for this command
● Select custom stepsize ([SENSe:]FREQuency:CENTer:STEP:LINK).
Parameters:
<Frequency> <numeric value>
Default unit: Hz
[SENSe:]FREQuency:CENTer:STEP:LINK <Mode>
This command selects the frequency step size mode.
Parameters:
<Mode> The step size is either a function of the span (x % of the span) or
an absolute value.
OFF
Step size is a custom percentage of the span or an absolute
custom value in Hz.
You can define a percentage with [SENSe:]FREQuency:
CENTer:STEP:LINK:FACTor.
You can define a custom value with [SENSe:]FREQuency:
CENTer:STEP.
SPAN
Step size is 10 % of the span.
*RST: SPAN
Example: //Select a custom step size
FREQ:CENT:STEP:LINK OFF
FREQ:CENT:STEP:LINK:FACT 20
Manual operation: See "Defining a frequency step size" on page 183
[SENSe:]FREQuency:CENTer:STEP:LINK:FACTor <Percentage>
This command defines a custom frequency step size.
Parameters:
<Percentage> <numeric value>
The value is a percentage. The step size is a function of the per-
centage and the span:
Step size = x % * span
Range: 0 to 100
*RST: 10
Default unit: PCT
Example: //Select a custom step size
FREQ:CENT:STEP:LINK OFF
FREQ:CENT:STEP:LINK:FACT 20
Manual operation: See "Defining a frequency step size" on page 183
[SENSe:]FREQuency:SPAN <Frequency>
This command defines the frequency span.
Parameters:
<Frequency> <numeric value>
Default unit: Hz
Example: //Define a frequency span
FREQ:SPAN 500MHZ
Manual operation: See "Defining the frequency range of the measurement"
on page 183
INPut<1|2>:RLEVel <Reflevel>
This command defines the reference level (expected signal level).
Note that the reference level is coupled to the attenuation.
Suffix: .
<1|2> 1|2
irrelevant
Parameters:
<Reflevel> <numeric value>
*RST: 0
Default unit: dBm
Example: //Define reference level
INP:RLEV 10DBM
Manual operation: See "Defining a reference level" on page 187
[SENSe:]AVERage<n>:COUNt........................................................................................ 488
[SENSe:]BWIDth:VIDeo..................................................................................................488
[SENSe:]BWIDth:VIDeo:AUTO........................................................................................ 488
[SENSe:]AVERage<n>:COUNt <AverageCount>
This command defines the number of measurements that the application uses to aver-
age traces.
In case of continuous sweep mode, the application calculates the moving average over
the average count.
In case of single sweep mode, the application stops the measurement and calculates
the average after the average count has been reached.
Suffix: .
<n> irrelevant
[SENSe:]BWIDth:VIDeo <Bandwidth>
This command defines the video bandwidth.
Prerequisites for this command
● Turn off automatic VBW selection ([SENSe:]BWIDth:VIDeo:AUTO).
Parameters:
<Bandwidth> Default unit: HZ
Example: //Select VBW manually
BWID:VID:AUTO OFF
BWID:VID 819672
Manual operation: See "Defining the video bandwidth" on page 187
[SENSe:]BWIDth:VIDeo:AUTO <State>
This command turns automatic selection of the video bandwidth on and off.
Parameters:
<State> ON | OFF | 1 | 0
*RST: ON
Example: //Turn on automatic VBW selection
BWID:VID:AUTO ON
Manual operation: See "Defining the video bandwidth" on page 187
TRIGger[:SEQuence]:DTIMe...........................................................................................489
TRIGger[:SEQuence]:FREQuency................................................................................... 489
TRIGger[:SEQuence]:FREQuency:HYSTeresis................................................................. 489
TRIGger[:SEQuence]:HOLDoff[:TIME]..............................................................................490
TRIGger[:SEQuence]:IFPower:HOLDoff........................................................................... 490
TRIGger[:SEQuence]:LEVel[:EXTernal<1|2>].................................................................... 490
TRIGger[:SEQuence]:SLOPe.......................................................................................... 491
TRIGger[:SEQuence]:SOURce........................................................................................491
TRIGger[:SEQuence]:DTIMe <Time>
This command defines the trigger drop-out time.
Parameters:
<Time> <numeric value>
*RST: 0
Default unit: s
Example: //Define a drop-out time
TRIG:DTIM 200MS
Manual operation: See "Defining a trigger drop-out time" on page 185
TRIGger[:SEQuence]:FREQuency <Frequency>
This command defines the trigger frequency.
Prerequisites for this command
● Select the frequency trigger (TRIGger[:SEQuence]:SOURce).
Parameters:
<Frequency> <numeric value>
Default unit: Hz
Example: //Configure frequency trigger
TRIG:SOUR FREQ
TRIG:FREQ 1GHZ
Manual operation: See "Defining the trigger level and frequency" on page 185
TRIGger[:SEQuence]:FREQuency:HYSTeresis <Hysteresis>
This command defines the trigger hysteresis.
Prerequisites for this command
● Select the frequency trigger (TRIGger[:SEQuence]:SOURce).
Parameters:
<Hysteresis> <numeric value>
*RST: 100 kHz
Default unit: Hz
Example: //Define a trigger hysteresis
TRIG:SOUR FREQ
TRIG:FREQ:HYST 200KHZ
Manual operation: See "Defining a trigger hysteresis" on page 185
TRIGger[:SEQuence]:HOLDoff[:TIME] <Offset>
Defines the time offset between the trigger event and the start of the measurement.
Parameters:
<Offset> *RST: 0s
Default unit: S
Example: TRIG:HOLD 500us
Manual operation: See " Trigger Offset " on page 185
TRIGger[:SEQuence]:IFPower:HOLDoff <Period>
This command defines the holding time before the next trigger event.
Note that this command can be used for any trigger source, not just IF Power
(despite the legacy keyword).
Parameters:
<Period> Range: 0 s to 10 s
*RST: 0s
Default unit: S
Example: TRIG:SOUR EXT
Sets an external trigger source.
TRIG:IFP:HOLD 200 ns
Sets the holding time to 200 ns.
Manual operation: See " Trigger Holdoff " on page 185
TRIGger[:SEQuence]:LEVel[:EXTernal<1|2>] <Level>
This command defines the external trigger level.
Prerequisites for this command
● Select the external trigger (TRIGger[:SEQuence]:SOURce).
Suffix: .
<1|2> 1|2
Selects the trigger port.
Parameters:
<Level> <numeric value>
Default unit: V
Example: //Configure external trigger on trigger port 2
TRIG:SOUR EXT2
TRIG:LEV:EXT2 1.4V
Manual operation: See "Defining the trigger level and frequency" on page 185
TRIGger[:SEQuence]:SLOPe <Slope>
This command selects the trigger slope.
Parameters:
<Slope> NEGative
Triggering occurs on a falling signal edge.
POSitive
Triggering occurs on a rising signal edge.
*RST: POSitive
Example: //Select trigger slope
TRIG:SLOP POS
Manual operation: See "Defining a trigger slope" on page 185
TRIGger[:SEQuence]:SOURce <Source>
This command selects the trigger source.
Parameters:
<Source> EXTernal | EXT2
External trigger: The measurement starts when the signal
applied to the input connector meets or exceeds a certain level.
FREQuency
Frequency trigger: The measurement starts when the signal
applied to the RF input meets or exceeds a certain frequency.
IMMediate
Free run: No trigger is used.
IQPower
Power trigger: The measurement starts when the signal level
within the demodulation bandwidth rises or falls by a certain
amount.
*RST: IMMediate
Example: //Select trigger source
TRIG:SOUR FREQ
Manual operation: See "Selecting the trigger source" on page 184
Commands to scale the y-axis in the frequency result display described elsewhere.
● Center frequency: [SENSe:]FREQuency:CENTer
Start frequency: [SENSe:]FREQuency:STARt
Stop frequency: [SENSe:]FREQuency:STOP
Span: [SENSe:]FREQuency:SPAN
● Stepsize: [SENSe:]FREQuency:CENTer:STEP:LINK
● Stepsize factor: [SENSe:]FREQuency:CENTer:STEP:LINK:FACTor
Commands to scale the y-axis in the phase result display described elsewhere.
● Mode: DISPlay[:WINDow<n>]:TRACe<t>:Y[:SCALe]:AUTO
● Auto scale once: DISPlay[:WINDow<n>]:TRACe<t>:Y[:SCALe]:AUTO
CONFigure:TRANsient[:WINDow<n>]:AF:COUPling.......................................................... 492
CONFigure:TRANsient[:WINDow<n>]:AF:COUPling:RPOint:MODE.................................... 492
CONFigure:TRANsient[:WINDow<n>]:AF:COUPling:RPOint[:X]..........................................493
DISPlay[:WINDow<n>]:TRACe<t>:Y[:SCALe]:MODE.........................................................493
DISPlay[:WINDow<n>]:TRACe<t>:Y[:SCALe]:PDIVision.................................................... 494
DISPlay[:WINDow<n>]:TRACe<t>:Y[:SCALe]:RPOSition................................................... 494
DISPlay[:WINDow<n>]:TRACe<t>:Y[:SCALe]:RVALue.......................................................495
DISPlay[:WINDow<n>]:TRACe<t>:Y[:SCALe]:UNIT...........................................................495
CONFigure:TRANsient[:WINDow<n>]:AF:COUPling <Mode>
This command selects the AF coupling mode.
Suffix: .
<n> 1..n
Window
Parameters:
<Mode> AC
AC coupling: Frequency offset and phase offset are automati-
cally corrected and DC signal contains a phase offset of ±π.
DC
DC coupling: Phase runs according to the existing frequency off-
set.
*RST: AC
Example: //Select AF coupling mode
CONF:TRAN:AF:COUP AC
Manual operation: See "Selecting the AF coupling mode" on page 189
CONFigure:TRANsient[:WINDow<n>]:AF:COUPling:RPOint:MODE <Mode>
This command selects the zero phase positioning mode.
Suffix: .
<n> 1..n
Window
Parameters:
<Mode> AUTO
Positions the zero phase at the end of the trace (right diagram
border).
MANual
Manual selection the position of the zero phase.
You can define the zero phase position with CONFigure:
TRANsient[:WINDow<n>]:AF:COUPling:RPOint[:X].
*RST: AUTO
Example: //Select zero phase positioning mode
CONF:TRAN:AF:COUP:RPO:MODE AUTO
Manual operation: See "Positioning the zero-phase" on page 189
CONFigure:TRANsient[:WINDow<n>]:AF:COUPling:RPOint[:X] <Position>
This command defines the position of the zero phase.
Prerequisites for this command
● Turn on manual selection of the zero phase position (CONFigure:TRANsient[:
WINDow<n>]:AF:COUPling:RPOint:MODE).
● Select "DC" AF coupling (CONFigure:TRANsient[:WINDow<n>]:AF:
COUPling on page 492).
Suffix: .
<n> 1..n
Window
Parameters:
<Position> <numeric value>
Default unit: s
Example: //Define position of the zero phase manually
CONF:TRAN:AF:COUP:RPO:MODE MAN
CONF:TRAN:AF:COUP:RPO 1US
Manual operation: See "Positioning the zero-phase" on page 189
DISPlay[:WINDow<n>]:TRACe<t>:Y[:SCALe]:MODE <Mode>
This command selects how frequencies are displayed on the y-axis.
Prerequisites for this command
● Frequency result display must be available and selected.
Suffix: .
<n> 1..n
Window
<t> 1..n
irrelevant
Parameters:
<Mode> ABSolute
Displays the frequencies in absolute values.
RELative
Displays the frequencies as an offset to the center frequency.
*RST: ABSolute
DISPlay[:WINDow<n>]:TRACe<t>:Y[:SCALe]:PDIVision <Value>
This command defines the range of a single diagram division on the y-axis of the
phase result display.
Prerequisites for this command
● Phase result display must be available and selected.
Suffix: .
<n> 1..n
Window
<t> 1..n
irrelevant
Parameters:
<Value> <numeric value>
Default unit: Depends on the selected unit (rad or deg)
Example: //Display 0.5 rad per grid division
DISP:TRAC:Y:UNIT
DISP:TRAC:Y:PDIV 0.5
Manual operation: See "Scaling the y-axis of the phase diagram" on page 189
DISPlay[:WINDow<n>]:TRACe<t>:Y[:SCALe]:RPOSition <Position>
This command defines the position of the reference value on the y-axis.
Prerequisites for this command
● Phase result display must be available and selected.
Suffix: .
<n> 1..n
Window
<t> 1..n
irrelevant
Parameters:
<Position> Percentage of the diagram height with 100 % corresponding to
the upper diagram border
*RST: 50
Default unit: PCT
Example: //Shift reference position to top of the diagram
DISP:TRAC:Y:RPOS 100
Manual operation: See "Scaling the y-axis of the phase diagram" on page 189
DISPlay[:WINDow<n>]:TRACe<t>:Y[:SCALe]:RVALue <RefValue>
This command defines the value assigned to the reference position.
Prerequisites for this command
● Phase result display must be available and selected.
Suffix: .
<n> 1..n
Window
<t> 1..n
irrelevant
Parameters:
<RefValue> <numeric value>
*RST: 0
Default unit: Depends on the selected unit (deg or rad)
Example: //Define reference value in rad
DISP:TRAC:Y:UNIT RAD
DISP:TRAC:Y:RVAL 5
Manual operation: See "Scaling the y-axis of the phase diagram" on page 189
DISPlay[:WINDow<n>]:TRACe<t>:Y[:SCALe]:UNIT <YScalUnit>
This command selects the unit in which the phase results are displayed.
Prerequisites for this command
● Phase result display must be available and selected.
Suffix: .
<n> 1..n
Window
<t> 1..n
irrelevant
Parameters:
<YScalUnit> DEG | RAD
*RST: RAD
Example: //Select unit for phase results
DISP:TRAC:Y:UNIT DEG
Manual operation: See "Scaling the y-axis of the phase diagram" on page 189
CALCulate<n>:SETTling:TIME:STATe.............................................................................. 496
CALCulate<n>:SETTling:TIME:DIAGram..........................................................................496
CALCulate<n>:SETTling:TIME:TRACe.............................................................................496
CALCulate<n>:SETTling:TIME:FREQuency:LIMit:LOWer...................................................496
CALCulate<n>:SETTling:TIME:FREQuency:LIMit:UPPer................................................... 497
CALCulate<n>:SETTling:TIME:RESult?........................................................................... 497
CALCulate<n>:SETTling:TIME:STATe <State>
This command defines the state of settling time measurement.
Suffix: .
<n> irrelevant
Parameters:
<State> ON | OFF | 1 | 0
*RST: 0
Example: CALC1:SETT:TIME:STAT OFF
CALCulate<n>:SETTling:TIME:DIAGram <Diagram>
This command selects the diagram for settling time calculation.
Suffix: .
<n> irrelevant
Parameters:
<Diagram> Number of the diagram
Example: CALC:SETT:TIME:DIAG 1
CALCulate<n>:SETTling:TIME:TRACe <Trace>
This command selects the trace for settling time calculation.
Suffix: .
<n> irrelevant
Parameters:
<Trace> TRACe1 | TRACe2 | TRACe3 | TRACe4 | TRACe5 | TRACe6
Example: CALC:SETT:TIME:TRAC Trace1
CALCulate<n>:SETTling:TIME:FREQuency:LIMit:LOWer <Frequency>
This command defines the lower frequency of settling time measurement.
Suffix: .
<n> irrelevant
Parameters:
<Frequency> Default unit: Hz
Example: CALC1:SETT:TIME:LOW:FREQ:LIM 100
CALCulate<n>:SETTling:TIME:FREQuency:LIMit:UPPer <Frequency>
This command defines the upper frequency of settling time measurement.
Suffix: .
<n> irrelevant
Parameters:
<Frequency> Default unit: Hz
Example: CALC1:SETT:TIME:UPP:FREQ:LIM 1000
CALCulate<n>:SETTling:TIME:RESult?
This command returns the settling time.
Suffix: .
<n> irrelevant
Example: CALC1:SETT:TIME:RES?
Usage: Query only
CALCulate<n>:FREQuency:DEViation:STATe................................................................... 497
CALCulate<n>:FREQuency:DEViation:DIAGram...............................................................497
CALCulate<n>:FREQuency:DEViation:TRACe..................................................................498
CALCulate<n>:FREQuency:DEViation:STARt................................................................... 498
CALCulate<n>:FREQuency:DEViation:STOP....................................................................498
CALCulate<n>:FREQuency:DEViation:REGRession?........................................................498
CALCulate<n>:FREQuency:DEViation:REGRession:POINts?............................................ 499
CALCulate<n>:FREQuency:DEViation:SLOPe?................................................................ 499
CALCulate<n>:FREQuency:DEViation:STATe <State>
This command defines the state of frequency deviation measurement.
Suffix: .
<n> irrelevant
Parameters:
<State> ON | OFF | 1 | 0
*RST: 0
Example: CALC1:FREQ:DEV:STAT OFF
CALCulate<n>:FREQuency:DEViation:DIAGram <Diagram>
This command selects the diagram for frequency deviation calculation.
Suffix: .
<n> irrelevant
Parameters:
<Diagram> Number of the diagram
Example: CALC:FREQ:DEV:DIAG 1
CALCulate<n>:FREQuency:DEViation:TRACe <Trace>
This command selects the trace for frequency deviation calculation.
Suffix: .
<n> irrelevant
Parameters:
<Trace> TRACe1 | TRACe2 | TRACe3 | TRACe4 | TRACe5 | TRACe6
Example: CALC:FREQ:DEV:TRAC Trace1
CALCulate<n>:FREQuency:DEViation:STARt <Range>
This command defines the start frequency of frequency deviation measurement.
Suffix: .
<n> irrelevant
Parameters:
<Range> Default unit: s
Example: CALC1:FREQ:DEV:STAR 100
CALCulate<n>:FREQuency:DEViation:STOP <Range>
This command defines the stop frequency of frequency deviation measurement.
Suffix: .
<n> irrelevant
Parameters:
<Range> Default unit: s
Example: CALC1:FREQ:DEV:STOP 1000
CALCulate<n>:FREQuency:DEViation:REGRession?
This command returns the data of the regression line.
Suffix: .
<n> irrelevant
Example: CALC1:FREQ:DEV:REGR?
Usage: Query only
CALCulate<n>:FREQuency:DEViation:REGRession:POINts?
This command queries the number of points of the regression line.
Suffix: .
<n> irrelevant
Return values:
<Points>
Example: CALC1:FREQ:DEV:REGR:POIN?
Usage: Query only
CALCulate<n>:FREQuency:DEViation:SLOPe?
This command returns the slope of the regression line. A single floating point value
with the unit Hz/s is returned.
Suffix: .
<n> irrelevant
Example: CALC1:FREQ:DEV:SLOP?
Usage: Query only
See Chapter 15.7.4, "Marker", on page 524 for a complete list of commands to control
markers.
See Chapter 15.7.5, "Limit Lines", on page 537 for a complete list of commands to
control limit lines.
DISPlay:FORMat........................................................................................................... 500
DISPlay:WSELect?........................................................................................................ 500
DISPlay[:WINDow<n>][:SUBWindow<w>]:SELect............................................................. 501
DISPlay[:WINDow<n>]:SIZE........................................................................................... 501
LAYout:ADD[:WINDow]?................................................................................................. 501
LAYout:CATalog[:WINDow]?............................................................................................ 503
LAYout:IDENtify[:WINDow]?............................................................................................ 503
LAYout:MOVE[:WINDow]................................................................................................ 504
LAYout:REMove[:WINDow]............................................................................................. 504
LAYout:REPLace[:WINDow]............................................................................................ 505
LAYout:SPLitter..............................................................................................................505
LAYout:WINDow<n>:ADD?............................................................................................. 507
LAYout:WINDow<n>:IDENtify?........................................................................................ 507
LAYout:WINDow<n>:REMove..........................................................................................508
LAYout:WINDow<n>:REPLace........................................................................................ 508
DISPlay:FORMat <Format>
This command determines which tab is displayed.
Parameters:
<Format> SPLit
Displays the MultiView tab with an overview of all active chan-
nels
SINGle
Displays the measurement channel that was previously focused.
*RST: SING
Example: DISP:FORM SPL
DISPlay:WSELect?
This command queries the currently active window (the one that is focused) in the cur-
rently selected measurement channel.
Return values:
<SelectedWindow> Index number of the currently active window.
Range: 1 to 16
DISPlay[:WINDow<n>][:SUBWindow<w>]:SELect
This command sets the focus on the selected result display window.
This window is then the active window.
For measurements with multiple results in subwindows, the command also selects the
subwindow. Use this command to select the (sub)window before querying trace data.
Suffix: .
<n> Window
<w> subwindow
Not supported by all applications
Example: //Put the focus on window 1
DISP:WIND1:SEL
Example: //Put the focus on subwindow 2 in window 1
DISP:WIND1:SUBW2:SEL
DISPlay[:WINDow<n>]:SIZE <Size>
This command maximizes the size of the selected result display window temporarily.
To change the size of several windows on the screen permanently, use the LAY:SPL
command (see LAYout:SPLitter on page 505).
Suffix: .
<n> Window
Parameters:
<Size> LARGe
Maximizes the selected window to full screen.
Other windows are still active in the background.
SMALl
Reduces the size of the selected window to its original size.
If more than one measurement window was displayed originally,
these are visible again.
*RST: SMALl
Example: DISP:WIND2:SIZE LARG
LAYout:ADD[:WINDow]? <WindowName>,<Direction>,<WindowType>
This command adds a window to the display in the active channel.
This command is always used as a query so that you immediately obtain the name of
the new window as a result.
To replace an existing window, use the LAYout:REPLace[:WINDow] command.
Query parameters:
<WindowName> String containing the name of the existing window the new win-
dow is inserted next to.
By default, the name of a window is the same as its index. To
determine the name and index of all active windows, use the
LAYout:CATalog[:WINDow]? query.
<Direction> LEFT | RIGHt | ABOVe | BELow
Direction the new window is added relative to the existing win-
dow.
<WindowType> text value
Type of result display (evaluation method) you want to add.
See the table below for available parameter values.
Return values:
<NewWindowName> When adding a new window, the command returns its name (by
default the same as its number) as a result.
Example: LAY:ADD? '1',LEFT,MTAB
Result:
'2'
Adds a new window named '2' with a marker table to the left of
window 1.
Usage: Query only
Manual operation: See " Marker Table " on page 121
Table 15-4: <WindowType> parameter values for the phase noise application
FREQuency Frequency2,4
PHASe Phase4
POWer Power2
SENSitivity Sensitivity2
1 Phase noise, additive noise, baseband noise, pulsed phase noise and pulsed additive noise measure-
ments
2 VCO characterization
3 Spot noise vs tune
4 Transient analysis
5 Phase noise
6 Phase noise, additive noise, pulsed phase noise and pulsed additive noise measurements
LAYout:CATalog[:WINDow]?
This command queries the name and index of all active windows in the active channel
from top left to bottom right. The result is a comma-separated list of values for each
window, with the syntax:
<WindowName_1>,<WindowIndex_1>..<WindowName_n>,<WindowIndex_n>
Return values:
<WindowName> string
Name of the window.
In the default state, the name of the window is its index.
<WindowIndex> numeric value
Index of the window.
Example: LAY:CAT?
Result:
'2',2,'1',1
Two windows are displayed, named '2' (at the top or left), and '1'
(at the bottom or right).
Usage: Query only
LAYout:IDENtify[:WINDow]? <WindowName>
This command queries the index of a particular display window in the active channel.
LAYout:REMove[:WINDow] <WindowName>
This command removes a window from the display in the active channel.
Setting parameters:
<WindowName> String containing the name of the window. In the default state,
the name of the window is its index.
Example: LAY:REM '2'
Removes the result display in the window named '2'.
LAYout:REPLace[:WINDow] <WindowName>,<WindowType>
This command replaces the window type (for example from "Diagram" to "Result Sum-
mary") of an already existing window in the active channel while keeping its position,
index and window name.
To add a new window, use the LAYout:ADD[:WINDow]? command.
Setting parameters:
<WindowName> String containing the name of the existing window.
By default, the name of a window is the same as its index. To
determine the name and index of all active windows in the active
channel, use the LAYout:CATalog[:WINDow]? query.
<WindowType> Type of result display you want to use in the existing window.
See LAYout:ADD[:WINDow]? on page 501 for a list of availa-
ble window types.
Example: LAY:REPL:WIND '1',MTAB
Replaces the result display in window 1 with a marker table.
Usage: Setting only
Setting parameters:
<Index1> The index of one window the splitter controls.
<Index2> The index of a window on the other side of the splitter.
<Position> New vertical or horizontal position of the splitter as a fraction of
the screen area (without channel and status bar and softkey
menu).
The point of origin (x = 0, y = 0) is in the lower left corner of the
screen. The end point (x = 100, y = 100) is in the upper right cor-
ner of the screen. (See Figure 15-1.)
The direction in which the splitter is moved depends on the
screen layout. If the windows are positioned horizontally, the
splitter also moves horizontally. If the windows are positioned
vertically, the splitter also moves vertically.
Range: 0 to 100
Example: LAY:SPL 1,3,50
Moves the splitter between window 1 ('Frequency Sweep') and 3
('Marker Table') to the center (50%) of the screen, i.e. in the fig-
ure above, to the left.
LAYout:WINDow<n>:ADD? <Direction>,<WindowType>
This command adds a measurement window to the display. Note that with this com-
mand, the suffix <n> determines the existing window next to which the new window is
added, as opposed to LAYout:ADD[:WINDow]?, for which the existing window is
defined by a parameter.
To replace an existing window, use the LAYout:WINDow<n>:REPLace command.
This command is always used as a query so that you immediately obtain the name of
the new window as a result.
Suffix: .
<n> Window
Query parameters:
<Direction> LEFT | RIGHt | ABOVe | BELow
<WindowType> Type of measurement window you want to add.
See LAYout:ADD[:WINDow]? on page 501 for a list of availa-
ble window types.
Return values:
<NewWindowName> When adding a new window, the command returns its name (by
default the same as its number) as a result.
Example: LAY:WIND1:ADD? LEFT,MTAB
Result:
'2'
Adds a new window named '2' with a marker table to the left of
window 1.
Usage: Query only
LAYout:WINDow<n>:IDENtify?
This command queries the name of a particular display window (indicated by the <n>
suffix) in the active channel.
Note: to query the index of a particular window, use the LAYout:IDENtify[:
WINDow]? command.
Suffix: .
<n> Window
Return values:
<WindowName> String containing the name of a window.
In the default state, the name of the window is its index.
Example: LAY:WIND2:IDEN?
Queries the name of the result display in window 2.
Response:
'2'
Usage: Query only
LAYout:WINDow<n>:REMove
This command removes the window specified by the suffix <n> from the display in the
active channel.
The result of this command is identical to the LAYout:REMove[:WINDow] command.
Suffix: .
<n> Window
Example: LAY:WIND2:REM
Removes the result display in window 2.
Usage: Event
LAYout:WINDow<n>:REPLace <WindowType>
This command changes the window type of an existing window (specified by the suffix
<n>) in the active channel.
The effect of this command is identical to the LAYout:REPLace[:WINDow] com-
mand.
To add a new window, use the LAYout:WINDow<n>:ADD? command.
Suffix: .
<n> Window
Setting parameters:
<WindowType> Type of measurement window you want to replace another one
with.
See LAYout:ADD[:WINDow]? on page 501 for a list of availa-
ble window types.
Example: LAY:WIND2:REPL MTAB
Replaces the result display in window 2 with a marker table.
Usage: Setting only
15.7.2 Zoom
DISPlay[:WINDow<n>][:SUBWindow<w>]:ZOOM:AREA.................................................... 509
DISPlay[:WINDow<n>][:SUBWindow<w>]:ZOOM:MULTiple<zn>:AREA...............................510
DISPlay[:WINDow<n>][:SUBWindow<w>]:ZOOM:MULTiple<zn>[:STATe].............................511
DISPlay[:WINDow<n>][:SUBWindow<w>]:ZOOM[:STATe].................................................. 511
DISPlay[:WINDow<n>][:SUBWindow<w>]:ZOOM:AREA <x1>,<y1>,<x2>,<y2>
This command defines the zoom area.
To define a zoom area, you first have to turn the zoom on.
Suffix: .
<n> Window
<w> subwindow
Not supported by all applications
Parameters:
<x1> Diagram coordinates in % of the complete diagram that define
the zoom area.
The lower left corner is the origin of coordinate system. The
upper right corner is the end point of the system.
Range: 0 to 100
Default unit: PCT
<y1> Diagram coordinates in % of the complete diagram that define
the zoom area.
The lower left corner is the origin of coordinate system. The
upper right corner is the end point of the system.
Range: 0 to 100
Default unit: PCT
<x2> Diagram coordinates in % of the complete diagram that define
the zoom area.
The lower left corner is the origin of coordinate system. The
upper right corner is the end point of the system.
Range: 0 to 100
Default unit: PCT
DISPlay[:WINDow<n>][:SUBWindow<w>]:ZOOM:MULTiple<zn>:AREA
<x1>,<y1>,<x2>,<y2>
This command defines the zoom area for a multiple zoom.
To define a zoom area, you first have to turn the zoom on.
Suffix: .
<n> Window
<w> subwindow
Not supported by all applications
<zn> Selects the zoom window.
Parameters:
<x1> Diagram coordinates in % of the complete diagram that define
the zoom area.
The lower left corner is the origin of coordinate system. The
upper right corner is the end point of the system.
Range: 0 to 100
Default unit: PCT
<y1> Diagram coordinates in % of the complete diagram that define
the zoom area.
The lower left corner is the origin of coordinate system. The
upper right corner is the end point of the system.
Range: 0 to 100
Default unit: PCT
DISPlay[:WINDow<n>][:SUBWindow<w>]:ZOOM:MULTiple<zn>[:STATe] <State>
This command turns the multiple zoom on and off.
Suffix: .
<n> Window
<w> subwindow
Not supported by all applications
<zn> Selects the zoom window.
If you turn off one of the zoom windows, all subsequent zoom
windows move up one position.
Parameters:
<State> ON | OFF | 0 | 1
OFF | 0
Switches the function off
ON | 1
Switches the function on
Manual operation: See " Multi-Zoom " on page 199
DISPlay[:WINDow<n>][:SUBWindow<w>]:ZOOM[:STATe] <State>
This command turns the zoom on and off.
Suffix: .
<n> Window
<w> subwindow
Not supported by all applications
Parameters:
<State> ON | OFF | 0 | 1
OFF | 0
Switches the function off
ON | 1
Switches the function on
Example: DISP:ZOOM ON
Activates the zoom mode.
Manual operation: See " Single Zoom " on page 199
See " Restore Original Display " on page 200
See " Deactivating Zoom (Selection Mode) " on page 200
DISPlay[:WINDow<n>]:TRACe<t>:MODE <Mode>
This command selects the trace mode. If necessary, the selected trace is also activa-
ted.
In case of max hold, min hold or average trace mode, you can set the number of single
measurements with [SENSe:]SWEep:COUNt. Note that synchronization to the end of
the measurement is possible only in single sweep mode.
Suffix: .
<n> Window
<t> Trace
Parameters:
<Mode> WRITe
Overwrite mode: the trace is overwritten by each sweep. This is
the default setting.
AVERage
The average is formed over several sweeps. The "Sweep/Aver-
age Count" determines the number of averaging procedures.
MAXHold
The maximum value is determined over several sweeps and dis-
played. The R&S FSWP saves the sweep result in the trace
memory only if the new value is greater than the previous one.
MINHold
The minimum value is determined from several measurements
and displayed. The R&S FSWP saves the sweep result in the
trace memory only if the new value is lower than the previous
one.
VIEW
The current contents of the trace memory are frozen and dis-
played.
BLANk
Hides the selected trace.
WRHold
The trace is overwritten when new data is available, but only
after all cross-correlation operations defined for a half decade
are done.
*RST: Depends on the trace.
Example: INIT:CONT OFF
Switching to single sweep mode.
SWE:COUN 16
Sets the number of measurements to 16.
DISP:TRAC3:MODE WRIT
Selects clear/write mode for trace 3.
INIT;*WAI
Starts the measurement and waits for the end of the measure-
ment.
Manual operation: See " Trace Mode " on page 207
DISPlay[:WINDow<n>]:TRACe<t>:LABel[:STATe] <State>
This command turns the display of the trace label for a specific trace on and off.
The command can only be applied to active traces.
Suffix: .
<n> 1..n
Window
<t> 1..n
Trace
Parameters:
<State> ON | OFF | 1 | 0
*RST: OFF
Example: //Turn on the label for trace 2
DISP:TRAC2:LAB ON
DISPlay[:WINDow<n>]:TRACe<t>:LABel:TEXT <Label>
This command defines the contents of a trace label.
Suffix: .
<n> 1..n
Window
<t> 1..n
Trace
Parameters:
<Label> String containing the trace label.
Example: //Assign a label to trace 2.
DISP:TRAC2:LAB:TEXT 'A YELLOW TRACE'
DISPlay[:WINDow<n>]:TRACe<t>:PERSistence:DECay <Decay>
This command defines the time period that an event remains visible until it fades away
(decay).
Prerequisites for this command
● Turn on persistence (DISPlay[:WINDow<n>]:TRACe<t>:PERSistence[:
STATe]).
Suffix: .
<n> 1..n
Window
<t> 1..n
Trace
Parameters:
<Decay> <numeric value>
Range: 0 s to 8 s
*RST: 0
Default unit: s
Example: //Turn on persistence for trace 2 with a decay of 2 seconds
DISP:TRAC2:PERS ON
DISP:TRAC2:PERS:DEC 2s
Manual operation: See "Displaying persistence" on page 208
DISPlay[:WINDow<n>]:TRACe<t>:PERSistence[:STATe] <State>
This command turns persistence for a trace on and off.
Suffix: .
<n> 1..n
Window
<t> 1..n
Trace
Parameters:
<State> ON | OFF | 1 | 0
*RST: OFF
Example: //Turn on persistence for trace 2
DISP:TRAC2:PERS ON
Manual operation: See "Displaying persistence" on page 208
DISPlay[:WINDow<n>]:TRACe<t>:RESult[:TYPE] <Resulttype>
This command selects the type of noise represented by the trace.
Suffix: .
<n> 1..n
Window
<t> 1..n
Trace
Parameters:
<Resulttype> PN
Phase noise results.
AM
AM noise results.
PNAM
Sum of phase noise and AM noise.
Example: //Show AM noise characteristics on trace 2
DISP:TRAC2:RES AM
Manual operation: See "Selecting the displayed result" on page 207
DISPlay[:WINDow<n>][:SUBWindow<w>]:TRACe<t>[:STATe] <State>
This command turns a trace on and off.
The measurement continues in the background.
Suffix: .
<n> Window
<w> subwindow
Not supported by all applications
<t> Trace
Parameters:
<State> ON | OFF | 0 | 1
OFF | 0
Switches the function off
ON | 1
Switches the function on
Example: DISP:TRAC3 ON
Manual operation: See " Trace 1 / Trace 2 / Trace 3 / Trace 4 / Trace 5 / Trace 6 "
on page 207
DISPlay[:WINDow<n>]:TRACe<t>:Y[:SCALe]:RLEVel:OFFSet <Offset>
This command defines the amount by which a trace is shifted.
Prerequisites for this command
● Turn on trace offset (DISPlay[:WINDow<n>]:TRACe<t>:Y[:SCALe]:RLEVel:
OFFSet:STATe).
Suffix: .
<n> 1..n
irrelevant
<t> 1..n
irrelevant
Parameters:
<Offset> <numeric value>
*RST: 0
Default unit: dB
Example: //Define a level offset of 10 dB
DISP:TRAC:Y:RLEV:OFFS 10
Manual operation: See "Shifting the trace" on page 208
DISPlay[:WINDow<n>]:TRACe<t>:Y[:SCALe]:RLEVel:OFFSet:STATe <State>
This command turns the offset for a trace on and off.
When you turn that feature on, the trace is shifted vertically by a certain amount.
Suffix: .
<n> 1..n
Window
<t> 1..n
Trace
Parameters:
<State> ON | OFF | 1 | 0
*RST: OFF
Example: //Shift trace 2 vertically by 10 dB.
DISP:TRAC2:Y:RLEV:OFFS:STAT ON
DISP:TRAC2:Y:RLEV:OFFS 10
Manual operation: See "Shifting the trace" on page 208
DISPlay[:WINDow<n>]:TRACe<t>:SMOothing:APERture <Aperture>
This command defines the magnitude (aperture) of trace smoothing.
Prerequisites for this command
● Turn on trace smoothing (DISPlay[:WINDow<n>]:TRACe<t>:SMOothing[:
STATe]).
In the Spot Noise vs Tune measurement, trace smoothing applies to either all traces or
none. Use [SENSe:]SMOothing[:STATe] in that case.
Suffix: .
<n> 1..n
Window
<t> 1..n
Trace
Parameters:
<Aperture> <numeric value>
Range: 1 to 20
*RST: 1
Default unit: PCT
Example: See DISPlay[:WINDow<n>]:TRACe<t>:SMOothing[:
STATe].
Manual operation: See "Smoothing traces" on page 208
DISPlay[:WINDow<n>]:TRACe<t>:SMOothing[:STATe] <State>
This command turns trace smoothing for a specific trace on and off.
When you turn on trace smoothing, you can define the smoothing magnitude with
DISPlay[:WINDow<n>]:TRACe<t>:SMOothing:APERture.
In the Spot Noise vs Tune measurement, trace smoothing applies to either all traces or
none. Use [SENSe:]SMOothing[:STATe] in that case.
Suffix: .
<n> 1..n
Window
<t> 1..n
Trace
Parameters:
<State> ON | OFF | 1 | 0
*RST: Depends on the trace.
Example: //Turns on trace 3 (average mode based on 10 measurements)
to display the AM noise results
DISP:TRAC3:MODE AVER
SWE:COUN 10
DISP:TRAC3:RES AM
//Smooth the trace by a magnitude of 10 %
DISP:TRAC3:SMO ON
DISP:TRAC3:SMO:APER 10
//Remove spurs from trace 3
DISP:TRAC3:SPUR:SUPP ON
DISP:TRAC3:SPUR:THR 5
Manual operation: See "Smoothing traces" on page 208
TRACe<n>:COPY.......................................................................................................... 518
FORMat[:DATA]............................................................................................................. 519
FORMat:DEXPort:CSEParator........................................................................................ 519
FORMat:DEXPort:DSEParator........................................................................................ 520
FORMat:DEXPort:FORMat............................................................................................. 520
FORMat:DEXPort:HEADer..............................................................................................520
FORMat:DEXPort:TRACes............................................................................................. 521
MMEMory:LOAD<n>:TRACe...........................................................................................521
FORMat:DEXPort:CSEParator <Separator>
This command selects the column separator for exported trace data.
The selected value is not affected by a preset. The command therefore has no reset
value.
Parameters:
<Separator> COMMa
Selects a comma as a separator.
SEMicolon
Selects a semicolon as a separator.
TAB
Selects a tabulator as a separator.
*RST: n/a
Example: //Select column separator
FORM:DEXP:CSEP TAB
Manual operation: See "Column Separator" on page 212
FORMat:DEXPort:DSEParator <Separator>
This command selects the decimal separator for data exported in ASCII format.
Parameters:
<Separator> POINt | COMMa
COMMa
Uses a comma as decimal separator, e.g. 4,05.
POINt
Uses a point as decimal separator, e.g. 4.05.
*RST: *RST has no effect on the decimal separator.
Default is POINt.
Example: FORM:DEXP:DSEP POIN
Sets the decimal point as separator.
Manual operation: See " Decimal Separator " on page 212
FORMat:DEXPort:FORMat <FileFormat>
Determines the format of the ASCII file to be imported or exported. Depending on the
external program in which the data file was created or will be evaluated, a comma-sep-
arated list (CSV) or a plain data format (DAT) file may be required.
Parameters:
<FileFormat> CSV | DAT
*RST: DAT
Example: FORM:DEXP:FORM CSV
Manual operation: See " File Type " on page 212
FORMat:DEXPort:HEADer <State>
If enabled, additional instrument and measurement settings are included in the header
of the export file for result data. If disabled, only the pure result data from the selected
traces and tables is exported.
Parameters:
<State> ON | OFF | 0 | 1
*RST: 1
Manual operation: See " Include Instrument & Measurement Settings " on page 210
FORMat:DEXPort:TRACes <Selection>
This command selects the data to be included in a data export file (see MMEMory:
STORe<n>:TRACe on page 576).
Parameters:
<Selection> SINGle | ALL
SINGle
Only a single trace is selected for export, namely the one speci-
fied by the MMEMory:STORe<n>:TRACe command.
ALL
Selects all active traces and result tables (e.g. Result Summary,
marker peak list etc.) in the current application for export to an
ASCII file.
The <trace> parameter for the MMEMory:STORe<n>:TRACe
command is ignored.
*RST: SINGle
Manual operation: See " Export all Traces and all Table Results " on page 210
CALCulate<n>:MATH:STATe........................................................................................... 522
CALCulate<n>:MATH[:EXPRession][:DEFine]...................................................................523
CALCulate<n>:MATH:STATe <State>
This command turns trace mathematics on and off.
Suffix: .
<n> 1..n
Window
Parameters:
<State> ON | 1
Turns trace mathematics on and selects the operation that has
been selected last (or (TRACE1-TRACE3) if you have not yet
selected one).
OFF | 0
Turns trace mathematics off.
*RST: OFF
Example: //Turn on trace 3, subtract it from trace 2 and write the result to
trace 2
DISP:TRAC3:MODE WRIT
CALC:MATH (TRACE2-TRACE3)
//Turn off trace mathematics
CALC:MATH:STAT OFF
//Turn them on again and selects the operation (TRACE2-
TRACE3).
CALC:MATH:STAT ON
Manual operation: See "Selecting the math operation" on page 214
CALCulate<n>:MATH[:EXPRession][:DEFine] <Operation>
This command selects the operation for trace mathematics.
Suffix: .
<n> 1..n
Window
Setting parameters:
<Operation> Depending on the operation you select, one trace is subtracted
from another. The result is written to the first trace indicated in
the operation.
An operation is only available if both traces are actually turned
on.
(TRACE1-TRACE3)
(TRACE2-TRACE3)
(TRACE4-TRACE6)
(TRACE5-TRACE6)
*RST: Trace mathematics are off.
Example: //Subtract trace 2 from trace 1 and write the result to trace 1
CALC:MATH (TRACE1-TRACE2)
Manual operation: See "Selecting the math operation" on page 214
15.7.3.5 Formats for Returned Values: ASCII Format and Binary Format
When trace data is retrieved using the TRAC:DATA or TRAC:IQ:DATA command, the
data is returned in the format defined using the FORMat[:DATA] on page 519. The
possible formats are described here.
● ASCII Format (FORMat ASCII):
The data is stored as a list of comma-separated values (CSV) of the measured val-
ues in floating point format.
● Binary Format (FORMat REAL,16/32/64):
The data is stored as binary data (definite length block data according to IEEE
488.2), each measurement value being formatted in 16-bit/32-bit/64-bit IEEE 754
floating-point-format.
The schema of the result string is as follows:
#41024<value1><value2>…<value n> with:
Reading out data in binary format is quicker than in ASCII format. Thus, binary format
is recommended for large amounts of data.
15.7.4 Marker
CALCulate<n>:DELTamarker<m>:AOFF...........................................................................525
CALCulate<n>:DELTamarker<m>:LINK............................................................................ 525
CALCulate<n>:DELTamarker<ms>:LINK:TO:MARKer<md>................................................525
CALCulate<n>:DELTamarker<m>:MODE......................................................................... 526
CALCulate<n>:DELTamarker<m>:MREFerence................................................................ 526
CALCulate<n>:DELTamarker<m>[:STATe]........................................................................ 526
CALCulate<n>:DELTamarker<m>:TRACe.........................................................................527
CALCulate<n>:DELTamarker<m>:X................................................................................. 527
CALCulate<n>:MARKer<m>:AOFF..................................................................................528
CALCulate<n>:MARKer<ms>:LINK:TO:MARKer<md>....................................................... 528
CALCulate<n>:MARKer<m>[:STATe]............................................................................... 528
CALCulate<n>:MARKer<m>:TRACe................................................................................529
CALCulate<n>:MARKer<m>:X........................................................................................ 529
CALCulate<n>:DELTamarker<m>:AOFF
This command turns off all delta markers.
Suffix: .
<n> Window
<m> irrelevant
Example: CALC:DELT:AOFF
Turns off all delta markers.
CALCulate<n>:DELTamarker<m>:LINK <State>
This command links delta marker <m> to marker 1.
If you change the horizontal position (x-value) of marker 1, delta marker <m> changes
its horizontal position to the same value.
Suffix: .
<n> Window
<m> Marker
Parameters:
<State> ON | OFF | 0 | 1
OFF | 0
Switches the function off
ON | 1
Switches the function on
Example: CALC:DELT2:LINK ON
Manual operation: See " Linking to Another Marker " on page 227
CALCulate<n>:DELTamarker<ms>:LINK:TO:MARKer<md> <State>
This command links delta marker <m1> to any active normal marker <m2>.
If you change the horizontal position of marker <m2>, delta marker <m1> changes its
horizontal position to the same value.
Suffix: .
<n> Window
<ms> source marker, see Marker
<md> destination marker, see Marker
Parameters:
<State> ON | OFF | 0 | 1
OFF | 0
Switches the function off
ON | 1
Switches the function on
Example: CALC:DELT4:LINK:TO:MARK2 ON
Links the delta marker 4 to the marker 2.
Manual operation: See " Linking to Another Marker " on page 227
CALCulate<n>:DELTamarker<m>:MODE <Mode>
This command defines whether the position of a delta marker is provided as an abso-
lute value or relative to a reference marker.
Note that when the position of a delta marker is queried, the result is always an abso-
lute value (see CALCulate<n>:DELTamarker<m>:X on page 527)!
Suffix: .
<n> Window
<m> irrelevant
Parameters:
<Mode> ABSolute
Delta marker position in absolute terms.
RELative
Delta marker position in relation to a reference marker.
*RST: RELative
Example: CALC:DELT:MODE ABS
Absolute delta marker position.
CALCulate<n>:DELTamarker<m>:MREFerence <Reference>
This command selects a reference marker for a delta marker other than marker 1.
Suffix: .
<n> Window
<m> Marker
Parameters:
<Reference>
Example: CALC:DELT3:MREF 2
Specifies that the values of delta marker 3 are relative to marker
2.
Manual operation: See " Reference Marker " on page 227
CALCulate<n>:DELTamarker<m>[:STATe] <State>
This command turns delta markers on and off.
If necessary, the command activates the delta marker first.
No suffix at DELTamarker turns on delta marker 1.
Suffix: .
<n> Window
<m> Marker
Parameters:
<State> ON | OFF | 0 | 1
OFF | 0
Switches the function off
ON | 1
Switches the function on
Example: CALC:DELT2 ON
Turns on delta marker 2.
Manual operation: See " Marker State " on page 226
See " Marker Type " on page 227
See " Select Marker " on page 228
CALCulate<n>:DELTamarker<m>:TRACe <Trace>
This command selects the trace a delta marker is positioned on.
Note that the corresponding trace must have a trace mode other than "Blank".
If necessary, the command activates the marker first.
Suffix: .
<n> Window
<m> Marker
Parameters:
<Trace> Trace number the marker is assigned to.
Example: CALC:DELT2:TRAC 2
Positions delta marker 2 on trace 2.
CALCulate<n>:DELTamarker<m>:X <Position>
This command moves a delta marker to a particular coordinate on the x-axis.
If necessary, the command activates the delta marker and positions a reference
marker to the peak power.
Suffix: .
<n> Window
<m> Marker
Parameters:
<Position> Numeric value that defines the marker position on the x-axis.
Range: The value range and unit depend on the measure-
ment and scale of the x-axis.
Example: CALC:DELT:X?
Outputs the absolute x-value of delta marker 1.
Manual operation: See "Marker Position X-value " on page 227
CALCulate<n>:MARKer<m>:AOFF
This command turns off all markers.
Suffix: .
<n> Window
<m> Marker
Example: CALC:MARK:AOFF
Switches off all markers.
Manual operation: See " All Markers Off " on page 228
CALCulate<n>:MARKer<ms>:LINK:TO:MARKer<md> <State>
This command links normal marker <m1> to any active normal marker <m2>.
If you change the horizontal position of marker <m2>, marker <m1> changes its hori-
zontal position to the same value.
Suffix: .
<n> Window
<ms> source marker, see Marker
<md> destination marker, see Marker
Parameters:
<State> ON | OFF | 0 | 1
OFF | 0
Switches the function off
ON | 1
Switches the function on
Example: CALC:MARK4:LINK:TO:MARK2 ON
Links marker 4 to marker 2.
Manual operation: See " Linking to Another Marker " on page 227
CALCulate<n>:MARKer<m>[:STATe] <State>
This command turns markers on and off. If the corresponding marker number is cur-
rently active as a delta marker, it is turned into a normal marker.
Suffix: .
<n> Window
<m> Marker
Parameters:
<State> ON | OFF | 0 | 1
OFF | 0
Switches the function off
ON | 1
Switches the function on
Example: CALC:MARK3 ON
Switches on marker 3.
Manual operation: See " Marker State " on page 226
See " Marker Type " on page 227
See " Select Marker " on page 228
CALCulate<n>:MARKer<m>:TRACe <Trace>
This command selects the trace the marker is positioned on.
Note that the corresponding trace must have a trace mode other than "Blank".
If necessary, the command activates the marker first.
Suffix: .
<n> Window
<m> Marker
Parameters:
<Trace>
Example: //Assign marker to trace 1
CALC:MARK3:TRAC 2
Manual operation: See " Assigning the Marker to a Trace " on page 228
CALCulate<n>:MARKer<m>:X <Position>
This command moves a marker to a specific coordinate on the x-axis.
If necessary, the command activates the marker.
If the marker has been used as a delta marker, the command turns it into a normal
marker.
Suffix: .
<n> Window
<m> Marker
Parameters:
<Position> Numeric value that defines the marker position on the x-axis.
The unit depends on the result display.
Range: The range depends on the current x-axis range.
Default unit: Hz
DISPlay[:WINDow<n>]:MTABle....................................................................................... 530
CALCulate<n>:MARKer<m>:LINK................................................................................... 530
DISPlay[:WINDow<n>]:MTABle <DisplayMode>
This command turns the marker table on and off.
Suffix: .
<n> irrelevant
Parameters:
<DisplayMode> ON | 1
Turns on the marker table.
OFF | 0
Turns off the marker table.
*RST: AUTO
Example: DISP:MTAB ON
Activates the marker table.
Manual operation: See " Marker Table Display " on page 229
CALCulate<n>:MARKer<m>:LINK <State>
This command defines whether all markers within the selected result display are
linked. If enabled, and you move one marker along the x-axis, all other markers in the
display are moved to the same x-axis position.
Suffix: .
<m> irrelevant
<n> Window
Parameters:
<State> ON | OFF | 1 | 0
*RST: 0
Example: CALC2:MARK:LINK ON
Manual operation: See "Linked Markers" on page 229
CALCulate<n>:MARKer<m>:PEXCursion.........................................................................531
CALCulate<n>:MARKer<m>:FUNCtion:SPTRacking:RANGe............................................. 531
CALCulate<n>:MARKer<m>:FUNCtion:SPTRacking[:STATe]............................................. 532
CALCulate<n>:MARKer<m>:PEXCursion <Excursion>
This command defines the peak excursion (for all markers).
The peak excursion sets the requirements for a peak to be detected during a peak
search.
The unit depends on the measurement.
Suffix: .
<n> Window
<m> irrelevant
Example: CALC:MARK:PEXC 10dB
Defines peak excursion as 10 dB.
Manual operation: See " Peak Excursion " on page 230
CALCulate<n>:MARKer<m>:FUNCtion:SPTRacking:RANGe <Range>
This command defines the frequency range in which spur tracking takes place.
Prerequisites for this command
● Turn on spur tracking (CALCulate<n>:MARKer<m>:FUNCtion:SPTRacking[:
STATe]).
Suffix: .
<n> 1..n
irrelevant
<m> 1..n
irrelevant
Parameters:
<Range> <numeric value>
Number without unit that defines the frequency range as a func-
tion of the resolution bandwidth.
Tracking range = x * RBW
*RST: 1.0
Example: //Turn on spur tracking and define a tracking range of 2 x RBW
CALC:MARK:FUNC:SPTR ON
CALC:MARK:FUNC:SPTR:RANG 2
Manual operation: See "Spurious Tracking" on page 230
CALCulate<n>:MARKer<m>:FUNCtion:SPTRacking[:STATe] <State>
This command turns spurious tracking on and off.
Suffix: .
<n> 1..n
irrelevant
<m> 1..n
irrelevant
Parameters:
<State> ON | OFF | 1 | 0
*RST: OFF
Example: //Turn on spur tracking
CALC:MARK:FUNC:SPTR ON
Manual operation: See "Spurious Tracking" on page 230
CALCulate<n>:DELTamarker<m>:MAXimum:LEFT........................................................... 532
CALCulate<n>:DELTamarker<m>:MAXimum:NEXT...........................................................533
CALCulate<n>:DELTamarker<m>:MAXimum:RIGHt.......................................................... 533
CALCulate<n>:DELTamarker<m>:MAXimum[:PEAK].........................................................533
CALCulate<n>:DELTamarker<m>:MINimum:LEFT............................................................ 533
CALCulate<n>:DELTamarker<m>:MINimum:NEXT............................................................534
CALCulate<n>:DELTamarker<m>:MINimum:RIGHt........................................................... 534
CALCulate<n>:DELTamarker<m>:MINimum[:PEAK].......................................................... 534
CALCulate<n>:MARKer<m>:MAXimum:LEFT...................................................................534
CALCulate<n>:MARKer<m>:MAXimum:NEXT.................................................................. 534
CALCulate<n>:MARKer<m>:MAXimum:RIGHt..................................................................535
CALCulate<n>:MARKer<m>:MAXimum[:PEAK]................................................................ 535
CALCulate<n>:MARKer<m>:MINimum:LEFT....................................................................535
CALCulate<n>:MARKer<m>:MINimum:NEXT................................................................... 535
CALCulate<n>:MARKer<m>:MINimum:RIGHt...................................................................536
CALCulate<n>:MARKer<m>:MINimum[:PEAK]................................................................. 536
CALCulate<n>:DELTamarker<m>:MAXimum:LEFT
This command moves a delta marker to the next higher value.
The search includes only measurement values to the left of the current marker posi-
tion.
Suffix: .
<n> Window
<m> Marker
Manual operation: See " Search Next Peak " on page 231
CALCulate<n>:DELTamarker<m>:MAXimum:NEXT
This command moves a marker to the next higher value.
Suffix: .
<n> 1..n
Window
<m> 1..n
Marker
Manual operation: See " Search Next Peak " on page 231
CALCulate<n>:DELTamarker<m>:MAXimum:RIGHt
This command moves a delta marker to the next higher value.
The search includes only measurement values to the right of the current marker posi-
tion.
Suffix: .
<n> Window
<m> Marker
Manual operation: See " Search Next Peak " on page 231
CALCulate<n>:DELTamarker<m>:MAXimum[:PEAK]
This command moves a delta marker to the highest level.
If the marker is not yet active, the command first activates the marker.
Suffix: .
<n> Window
<m> Marker
Manual operation: See " Peak Search " on page 231
CALCulate<n>:DELTamarker<m>:MINimum:LEFT
This command moves a delta marker to the next higher minimum value.
The search includes only measurement values to the right of the current marker posi-
tion.
Suffix: .
<n> Window
<m> Marker
Manual operation: See " Search Next Minimum " on page 232
CALCulate<n>:DELTamarker<m>:MINimum:NEXT
This command moves a marker to the next higher minimum value.
Suffix: .
<n> Window
<m> Marker
Manual operation: See " Search Next Minimum " on page 232
CALCulate<n>:DELTamarker<m>:MINimum:RIGHt
This command moves a delta marker to the next higher minimum value.
The search includes only measurement values to the right of the current marker posi-
tion.
Suffix: .
<n> Window
<m> Marker
Manual operation: See " Search Next Minimum " on page 232
CALCulate<n>:DELTamarker<m>:MINimum[:PEAK]
This command moves a delta marker to the minimum level.
If the marker is not yet active, the command first activates the marker.
Suffix: .
<n> Window
<m> Marker
Manual operation: See " Search Minimum " on page 231
CALCulate<n>:MARKer<m>:MAXimum:LEFT
This command moves a marker to the next lower peak.
The search includes only measurement values to the left of the current marker posi-
tion.
Suffix: .
<n> Window
<m> Marker
Manual operation: See " Search Next Peak " on page 231
CALCulate<n>:MARKer<m>:MAXimum:NEXT
This command moves a marker to the next lower peak.
Suffix: .
<n> Window
<m> Marker
Manual operation: See " Search Next Peak " on page 231
CALCulate<n>:MARKer<m>:MAXimum:RIGHt
This command moves a marker to the next lower peak.
The search includes only measurement values to the right of the current marker posi-
tion.
Suffix: .
<n> Window
<m> Marker
Manual operation: See " Search Next Peak " on page 231
CALCulate<n>:MARKer<m>:MAXimum[:PEAK]
This command moves a marker to the highest level.
If the marker is not yet active, the command first activates the marker.
Suffix: .
<n> Window
<m> Marker
Manual operation: See " Peak Search " on page 231
CALCulate<n>:MARKer<m>:MINimum:LEFT
This command moves a marker to the next minimum value.
The search includes only measurement values to the right of the current marker posi-
tion.
Suffix: .
<n> Window
<m> Marker
Manual operation: See " Search Next Minimum " on page 232
CALCulate<n>:MARKer<m>:MINimum:NEXT
This command moves a marker to the next minimum value.
Suffix: .
<n> Window
<m> Marker
Manual operation: See " Search Next Minimum " on page 232
CALCulate<n>:MARKer<m>:MINimum:RIGHt
This command moves a marker to the next minimum value.
The search includes only measurement values to the right of the current marker posi-
tion.
Suffix: .
<n> Window
<m> Marker
Manual operation: See " Search Next Minimum " on page 232
CALCulate<n>:MARKer<m>:MINimum[:PEAK]
This command moves a marker to the minimum level.
If the marker is not yet active, the command first activates the marker.
Suffix: .
<n> Window
<m> Marker
Manual operation: See " Search Minimum " on page 231
CALCulate<n>:DELTamarker<m>:X:RELative?
This command queries the relative position of a delta marker on the x-axis.
If necessary, the command activates the delta marker first.
Suffix: .
<n> Window
<m> Marker
Return values:
<Position> Position of the delta marker in relation to the reference marker.
Example: CALC:DELT3:X:REL?
Outputs the frequency of delta marker 3 relative to marker 1 or
relative to the reference position.
Usage: Query only
CALCulate<n>:DELTamarker<m>:Y?
Queries the result at the position of the specified delta marker.
Suffix: .
<n> 1..n
<m> 1..n
Return values:
<Result> Result at the position of the delta marker.
The unit is variable and depends on the one you have currently
set.
Default unit: DBM
Usage: Query only
CALCulate<n>:MARKer<m>:Y?
Queries the result at the position of the specified marker.
Suffix: .
<n> 1..n
<m> 1..n
Return values:
<Result> Default unit: DBM
Usage: Query only
CALCulate<n>:LIMit<li>:ACTive?.....................................................................................538
CALCulate<n>:LIMit<k>:COMPatible?..............................................................................538
CALCulate<n>:LIMit<li>:COPY........................................................................................538
CALCulate<n>:LIMit<li>:DELete...................................................................................... 539
CALCulate<n>:LIMit<li>:LOWer:OFFSet...........................................................................539
CALCulate<n>:LIMit<li>:LOWer:STATe.............................................................................539
CALCulate<n>:LIMit<li>:STATe........................................................................................540
CALCulate<n>:LIMit<li>:TRACe<t>..................................................................................540
CALCulate<n>:LIMit<li>:TRACe<t>:CHECk...................................................................... 541
CALCulate<n>:LIMit<li>:UPPer:STATe............................................................................. 541
CALCulate<n>:LIMit<li>:ACTive?
This command queries the names of all active limit lines.
Suffix: .
<n> irrelevant
<li> irrelevant
Return values:
<LimitLines> String containing the names of all active limit lines in alphabeti-
cal order.
Example: CALC:LIM:ACT?
Queries the names of all active limit lines.
Usage: Query only
Manual operation: See " Visibility " on page 237
CALCulate<n>:LIMit<k>:COMPatible?
This command queries if the currently selected limit line is compatible to the current
measurement configuration.
Suffix: .
<n> 1..n
irrelevant
<k> 1..n
Limit line
Return values:
<MkrIndex> 1
Limit line is compatible to the current measurement settings.
0
Limit line is not compatible to the current measurement settings.
Example: //Query limit line compatibility
CALC:LIM:NAME 'Limit'
CALC:LIM:COMP?
Usage: Query only
CALCulate<n>:LIMit<li>:COPY <Line>
This command copies a limit line.
Suffix: .
<n> Window
CALCulate<n>:LIMit<li>:DELete
This command deletes a limit line.
Suffix: .
<n> Window
<li> Limit line
Manual operation: See " Delete Line " on page 238
CALCulate<n>:LIMit<li>:LOWer:OFFSet <Offset>
This command defines an offset for a complete lower limit line.
Compared to shifting the limit line, an offset does not actually change the limit line defi-
nition points.
Suffix: .
<n> Window
<li> Limit line
Parameters:
<Offset> Numeric value.
*RST: 0
Default unit: dB
CALCulate<n>:LIMit<li>:LOWer:STATe <State>
This command turns a lower limit line on and off.
Before you can use the command, you have to select a limit line with CALCulate<n>:
LIMit<li>:NAME on page 546.
Suffix: .
<n> irrelevant
CALCulate<n>:LIMit<li>:STATe <State>
This command turns the limit check for a specific limit line on and off.
To query the limit check result, use CALCulate<n>:LIMit<li>:FAIL?.
Note that a new command exists to activate the limit check and define the trace to be
checked in one step (see CALCulate<n>:LIMit<li>:TRACe<t>:CHECk
on page 541).
Suffix: .
<n> irrelevant
<li> Limit line
Parameters:
<State> ON | OFF | 0 | 1
OFF | 0
Switches the function off
ON | 1
Switches the function on
Example: CALC:LIM:STAT ON
Switches on the limit check for limit line 1.
Manual operation: See " Disable All Lines " on page 238
CALCulate<n>:LIMit<li>:TRACe<t> <TraceNumber>
This command links a limit line to one or more traces.
Note that this command is maintained for compatibility reasons only. Limit lines no lon-
ger need to be assigned to a trace explicitly. The trace to be checked can be defined
directly (as a suffix) in the new command to activate the limit check (see
CALCulate<n>:LIMit<li>:TRACe<t>:CHECk on page 541).
Suffix: .
<n> Window
<li> Limit line
<t> irrelevant
Example: CALC:LIM2:TRAC 3
Assigns limit line 2 to trace 3.
CALCulate<n>:LIMit<li>:TRACe<t>:CHECk <State>
This command turns the limit check for a specific trace on and off.
To query the limit check result, use CALCulate<n>:LIMit<li>:FAIL?.
Note that this command replaces the two commands from previous signal and spec-
trum analyzers (which are still supported, however):
● CALCulate<n>:LIMit<li>:TRACe<t> on page 540
● CALCulate<n>:LIMit<li>:STATe on page 540
Suffix: .
<n> Window
<li> Limit line
<t> Trace
Parameters:
<State> ON | OFF | 0 | 1
OFF | 0
Switches the function off
ON | 1
Switches the function on
Example: CALC:LIM3:TRAC2:CHEC ON
Switches on the limit check for limit line 3 on trace 2.
Manual operation: See " Traces to be Checked " on page 237
CALCulate<n>:LIMit<li>:UPPer:STATe <State>
This command turns an upper limit line on and off.
Before you can use the command, you have to select a limit line with CALCulate<n>:
LIMit<li>:NAME on page 546.
Suffix: .
<n> irrelevant
<li> Limit line
Parameters:
<State> ON | OFF | 0 | 1
OFF | 0
Switches the function off
ON | 1
Switches the function on
Manual operation: See " Visibility " on page 237
CALCulate<n>:LIMit<li>:COMMent.................................................................................. 542
CALCulate<n>:LIMit<li>:CONTrol[:DATA]......................................................................... 542
CALCulate<n>:LIMit<li>:CONTrol:DOMain........................................................................543
CALCulate<n>:LIMit<li>:CONTrol:MODE..........................................................................543
CALCulate<n>:LIMit<li>:CONTrol:SHIFt........................................................................... 543
CALCulate<n>:LIMit<li>:CONTrol:SPACing...................................................................... 544
CALCulate<n>:LIMit<li>:LOWer[:DATA]............................................................................544
CALCulate<n>:LIMit<li>:LOWer:MODE............................................................................ 544
CALCulate<n>:LIMit<li>:LOWer:SHIFt..............................................................................545
CALCulate<n>:LIMit<li>:LOWer:SPACing......................................................................... 545
CALCulate<n>:LIMit<li>:NAME........................................................................................546
CALCulate<n>:LIMit<li>:UNIT......................................................................................... 546
CALCulate<n>:LIMit<li>:UPPer[:DATA].............................................................................546
CALCulate<n>:LIMit<li>:UPPer:MODE.............................................................................547
CALCulate<n>:LIMit<li>:UPPer:SHIFt.............................................................................. 547
CALCulate<n>:LIMit<li>:UPPer:SPACing..........................................................................547
CALCulate<n>:LIMit<li>:COMMent <Comment>
This command defines a comment for a limit line.
Suffix: .
<n> irrelevant
<li> Limit line
Parameters:
<Comment> String containing the description of the limit line.
Manual operation: See " Comment " on page 238
CALCulate<n>:LIMit<li>:CONTrol[:DATA] <LimitLinePoints>
This command defines the horizontal definition points of a limit line.
Suffix: .
<n> irrelevant
<li> Limit line
Parameters:
<LimitLinePoints> Variable number of x-axis values.
Note that the number of horizontal values has to be the same as
the number of vertical values set with CALCulate<n>:
LIMit<li>:LOWer[:DATA] or CALCulate<n>:LIMit<li>:
UPPer[:DATA]. If not, the R&S FSWP either adds missing val-
ues or ignores surplus values.
*RST: -
Default unit: HZ
Manual operation: See " Data Points " on page 239
CALCulate<n>:LIMit<li>:CONTrol:DOMain <SpanSetting>
This command selects the domain of the limit line.
Suffix: .
<n> irrelevant
<li> Limit line
Parameters:
<SpanSetting> FREQuency | TIME
FREQuency
For limit lines that apply to a range of frequencies.
TIME
For limit lines that apply to a period of time.
CURRent
For limit lines that apply to a range of currents.
VOLTage
For limit lines that apply to a range of voltages.
*RST: FREQuency
Example: CALC:LIM:CONT:DOM FREQ
Select a limit line in the frequency domain.
Manual operation: See " X-Axis " on page 239
CALCulate<n>:LIMit<li>:CONTrol:MODE <Mode>
This command selects the horizontal limit line scaling.
Suffix: .
<n> irrelevant
<li> Limit line
Parameters:
<Mode> ABSolute
Limit line is defined by absolute physical values (Hz or s).
RELative
Limit line is defined by relative values related to the center fre-
quency (frequency domain) or the left diagram border (time
domain).
*RST: ABSolute
CALCulate<n>:LIMit<li>:CONTrol:SHIFt <Distance>
This command moves a complete limit line horizontally.
Compared to defining an offset, this command actually changes the limit line definition
points by the value you define.
Suffix: .
<n> irrelevant
<li> Limit line
Parameters:
<Distance> Numeric value.
The unit depends on the scale of the x-axis.
Default unit: HZ
Manual operation: See " Shift x " on page 240
CALCulate<n>:LIMit<li>:CONTrol:SPACing <InterpolMode>
This command selects linear or logarithmic interpolation for the calculation of limit lines
from one horizontal point to the next.
Suffix: .
<n> Window
<li> Limit line
Parameters:
<InterpolMode> LINear | LOGarithmic
*RST: LIN
Example: CALC:LIM:CONT:SPAC LIN
Manual operation: See " X-Axis " on page 239
CALCulate<n>:LIMit<li>:LOWer[:DATA] <LimitLinePoints>
This command defines the vertical definition points of a lower limit line.
Suffix: .
<n> irrelevant
<li> Limit line
Parameters:
<LimitLinePoints> Variable number of level values.
Note that the number of vertical values has to be the same as
the number of horizontal values set with CALCulate<n>:
LIMit<li>:CONTrol[:DATA]. If not, the R&S FSWP either
adds missing values or ignores surplus values.
*RST: Limit line state is OFF
Default unit: DBM
Manual operation: See " Data Points " on page 239
CALCulate<n>:LIMit<li>:LOWer:MODE <Mode>
This command selects the vertical limit line scaling.
Suffix: .
<n> Window
<li> Limit line
Parameters:
<Mode> ABSolute
Limit line is defined by absolute physical values.
The unit is variable.
RELative
Limit line is defined by relative values related to the reference
level (dB).
*RST: ABSolute
Manual operation: See " X-Axis " on page 239
CALCulate<n>:LIMit<li>:LOWer:SHIFt <Distance>
This command moves a complete lower limit line vertically.
Compared to defining an offset, this command actually changes the limit line definition
points by the value you define.
Suffix: .
<n> Window
<li> Limit line
Parameters:
<Distance> Defines the distance that the limit line moves.
Default unit: DB
Manual operation: See " Shift y " on page 240
CALCulate<n>:LIMit<li>:LOWer:SPACing <InterpolType>
This command selects linear or logarithmic interpolation for the calculation of a lower
limit line from one horizontal point to the next.
Suffix: .
<n> Window
<li> Limit line
Parameters:
<InterpolType> LINear | LOGarithmic
*RST: LIN
Manual operation: See " Y-Axis " on page 239
CALCulate<n>:LIMit<li>:NAME <Name>
This command selects a limit line that already exists or defines a name for a new limit
line.
Suffix: .
<n> Window
<li> Limit line
Parameters:
<Name> String containing the limit line name.
*RST: REM1 to REM8 for lines 1 to 8
Manual operation: See " Name " on page 238
CALCulate<n>:LIMit<li>:UNIT <Unit>
This command defines the unit of a limit line.
Suffix: .
<n> irrelevant
<li> Limit line
Parameters:
<Unit> If you select dB as the limit line unit, the command automatically
turns the limit line into a relative limit line.
*RST: DBM
Manual operation: See " Y-Axis " on page 239
CALCulate<n>:LIMit<li>:UPPer[:DATA] <LimitLinePoints>
This command defines the vertical definition points of an upper limit line.
Suffix: .
<n> irrelevant
<li> Limit line
Parameters:
<LimitLinePoints> Variable number of level values.
Note that the number of vertical values has to be the same as
the number of horizontal values set with CALCulate<n>:
LIMit<li>:CONTrol[:DATA]. If not, the R&S FSWP either
adds missing values or ignores surplus values.
*RST: Limit line state is OFF
Default unit: DBM
Manual operation: See " Data Points " on page 239
CALCulate<n>:LIMit<li>:UPPer:MODE <Mode>
This command selects the vertical limit line scaling.
Suffix: .
<n> Window
<li> Limit line
Parameters:
<Mode> ABSolute
Limit line is defined by absolute physical values.
The unit is variable.
RELative
Limit line is defined by relative values related to the reference
level (dB).
*RST: ABSolute
Manual operation: See " X-Axis " on page 239
CALCulate<n>:LIMit<li>:UPPer:SHIFt <Distance>
This command moves a complete upper limit line vertically.
Compared to defining an offset, this command actually changes the limit line definition
points by the value you define.
Suffix: .
<n> irrelevant
<li> Limit line
Parameters:
<Distance> Defines the distance that the limit line moves.
Manual operation: See " Shift y " on page 240
CALCulate<n>:LIMit<li>:UPPer:SPACing <InterpolType>
This command selects linear or logarithmic interpolation for the calculation of an upper
limit line from one horizontal point to the next.
Suffix: .
<n> Window
<li> Limit line
Parameters:
<InterpolType> LINear | LOGarithmic
*RST: LIN
Manual operation: See " Y-Axis " on page 239
CALCulate<n>:LIMit<li>:CLEar[:IMMediate]...................................................................... 548
CALCulate<n>:LIMit<li>:FAIL?........................................................................................ 548
CALCulate<n>:LIMit<li>:CLEar[:IMMediate]
This command deletes the result of the current limit check.
The command works on all limit lines in all measurement windows at the same time.
Suffix: .
<n> Window
<li> irrelevant
Example: CALC:LIM:CLE
Deletes the result of the limit check.
CALCulate<n>:LIMit<li>:FAIL?
This command queries the result of a limit check in the specified window.
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 measurement mode.
Suffix: .
<n> Window
<li> Limit line
Return values:
<Result> 0
PASS
1
FAIL
Example: INIT;*WAI
Starts a new sweep and waits for its end.
CALC2:LIM3:FAIL?
Queries the result of the check for limit line 3 in window 2.
Usage: Query only
CALC:LIM1:UPP:MODE ABS
//Select the unit dBc_Hz for limit line 1
CALC:LIM1:UNIT DBC_HZ
//Define 5 vertical definition points for limit line 1
CALC:LIM1:UPP -60,-80,-90,-100,-110
The following example demonstrates how to configure result displays in a remote envi-
ronment.
Starting from the default initial display in the Spectrum application (Frequency Sweep),
we will configure the following result displays:
Starting from the display configured in Example 1: Adding and Arranging Windows, we
will remove and replace result displays to obtain the following configuration:
1 Frequency Sweep
4 Marker Table
Addressing drives
The various drives can be addressed via the "mass storage instrument specifier"
<msis> using the conventional Windows syntax. The internal hard disk is addressed by
"C:". For details on storage locations refer to Chapter 12.3.2.2, "Storage Location and
Filename", on page 252.
The file names (<FileName> parameter) are given as string parameters enclosed in
quotation marks. They also comply with Windows conventions. Windows file names do
not distinguish between uppercase and lowercase notation.
Wildcards
The two characters "*" and "?" can be used as "wildcards". Wildcards are variables for
a selection of several files. The question mark "?" replaces exactly one character, the
asterisk replaces any of the remaining characters in the file name. "*.*" thus means all
files in a directory.
Path names
Storage locations can be specified either as absolute (including the entire path) or rela-
tive paths (including only subfolders of the current folder). Use the MMEM:CDIR? query
to determine the current folder.
● Managing Files......................................................................................................553
● Selecting Items to Store........................................................................................ 558
● Saving and Loading Instrument Settings.............................................................. 561
● Storing and Printing Screenshots..........................................................................565
● Saving Measurement Results............................................................................... 576
● Examples: Managing Data.................................................................................... 576
MMEMory:CATalog <FileName>
This command returns the contents of a particular directory.
Parameters:
<FileName> String containing the path and directory
If you leave out the path, the command returns the contents of
the directory selected with MMEMory:CDIRectory
on page 554.
The path may be relative or absolute. Using wildcards ('*') is
possible to query a certain type of files only.
If you use a specific file as a parameter, the command returns
the name of the file if the file is found in the specified directory,
or an error if the file is not found ("-256,"File name not
found").
Example: MMEM:CAT? 'C:\Data\SPOOL?.PNG'
Returns all files in C:\Data\ whose names start with SPOOL,
have 6 characters and the extension .PNG, e.g.:
SPOOL1.PNG,SPOOL2.PNG,SPOOL3.PNG
Example: MMEM:CAT? 'C:\Data\SPOOL6.PNG'
Query whether the file 'SPOOL6.PNG' also exists in the directory;
Result:
-256,"File name not found;:MMEMory:CATalog?
'C:\Data\SPOOL6.PNG'
Manual operation: See " Selecting Storage Location - Drive/ Path/ Files"
on page 253
MMEMory:CATalog:LONG <Directory>
This command returns the contents of a particular directory with additional information
about the files.
Parameters:
<Directory> String containing the path and directory.
If you leave out the path, the command returns the contents of
the directory selected with MMEMory:CDIRectory
on page 554.
The path may be relative or absolute. Using wildcards ('*') is
possible to query a certain type of files only.
MMEMory:CDIRectory <Directory>
This command changes the current directory.
Parameters:
<Directory> String containing the path to another directory.
The path may be relative or absolute.
MMEMory:COMMent <Comment>
This command defines a comment for the stored settings.
Parameters:
<Comment> String containing the comment.
Example: MMEMory:COMMent "ACP measurement with Standard
Tetra from 23.05."
MMEMory::MMEMory:STORe1:STATe 1, "ACP_T"
As a result, in the selection list for recall settings, the comment
"ACP measurement with Standard Tetra from
23.05." is added to the ACP entry.
Manual operation: See " Comment " on page 254
<FileName> String containing the path and name of the target file.
The path may be relative or absolute.
MMEMory:DELete:IMMediate <FileName>
This command deletes a file.
Parameters:
<FileName> String containing the path and file name of the file to delete.
The path may be relative or absolute.
MMEMory:MDIRectory <Directory>
This command creates a new directory.
Parameters:
<Directory> String containing the path and new directory name
The path may be relative or absolute.
MMEMory:MSIS <Device>
This command selects the default storage device used by all MMEMory commands.
Parameters:
<Device> 'A:' | 'C:' | … | 'Z:'
String containing the device drive name
*RST: n.a.
MMEMory:NAME <FileName>
This command has several purposes, depending on the context it is used in.
● It creates a new and empty file.
● It defines the file name for screenshots taken with HCOPy[:IMMediate<1|2>].
Note that you have to route the printer output to a file.
Parameters:
<FileName> String containing the path and name of the target file.
Example: MMEM:NAME 'C:\Data\PRINT1.BMP'
Selects the file name.
Parameters:
<Drive> String containing the drive name.
<State> 1 | 0 | ON | OFF
Optional: determines whether disconnection is forced or not
1 | ON
Disconnection is forced.
0 | OFF
Disconnect only if not in use.
*RST: 0
MMEMory:NETWork:UNUSeddrives?
This command returns a list of unused network drives.
Return values:
<DriveName> List of network drives in alphabetically descending order, e.g.
'W:,V:,U:,...'
Usage: Query only
MMEMory:NETWork:USEDdrives [<State>]
This command returns a list of all network drives in use.
Parameters:
<State> You do not have to use the parameter. If you do not include the
parameter, the command returns a list of all drives in use.
This is the same behavior as if you were using the parameter
OFF.
ON | 1
Returns a list of all drives in use including the folder information.
OFF | 0
Returns a list of all drives in use.
MMEMory:RDIRectory <arg0>
This command deletes the indicated directory.
Parameters:
<arg0> String containing the path of the directory to delete.
Note that the directory you want to remove must be empty.
The following commands select the items to be included in the configuration file.
Depending on the used command, either the items from the entire instrument
(MMEMory:SELect[:ITEM]...), or only those from the currently selected channel
(MMEM:SELect:CHANnel[:ITEM]...) are stored.
MMEMory:SELect:CHANnel[:ITEM]:ALL...........................................................................559
MMEMory:SELect[:ITEM]:ALL......................................................................................... 559
MMEMory:SELect:CHANnel[:ITEM]:DEFault.....................................................................559
MMEMory:SELect[:ITEM]:DEFault................................................................................... 559
MMEMory:SELect:CHANnel[:ITEM]:HWSettings............................................................... 559
MMEMory:SELect[:ITEM]:HWSettings..............................................................................559
MMEMory:SELect:CHANnel[:ITEM]:LINes:ALL................................................................. 560
MMEMory:SELect[:ITEM]:LINes:ALL................................................................................560
MMEMory:SELect:CHANnel[:ITEM]:NONE....................................................................... 560
MMEMory:SELect[:ITEM]:NONE..................................................................................... 560
MMEMory:SELect:CHANnel[:ITEM]:SGRam.....................................................................560
MMEMory:SELect[:ITEM]:SGRam................................................................................... 560
MMEMory:SELect:CHANnel[:ITEM]:TRACe[:ACTive].........................................................560
MMEMory:SELect[:ITEM]:TRACe<1...3>[:ACTive]............................................................. 560
MMEMory:SELect:CHANnel[:ITEM]:TRANsducer:ALL....................................................... 561
MMEMory:SELect[:ITEM]:TRANsducer:ALL......................................................................561
MMEMory:SELect:CHANnel[:ITEM]:WEIGhting.................................................................561
MMEMory:SELect[:ITEM]:WEIGhting............................................................................... 561
MMEMory:SELect:CHANnel[:ITEM]:ALL
MMEMory:SELect[:ITEM]:ALL
This command includes all items when storing or loading a configuration file.
The items are:
● Hardware configuration: MMEMory:SELect[:ITEM]:HWSettings on page 559
● Limit lines: MMEMory:SELect[:ITEM]:LINes:ALL on page 560
● Spectrogram data: MMEMory:SELect[:ITEM]:SGRam on page 560
● Trace data: MMEMory:SELect[:ITEM]:TRACe<1...3>[:ACTive]
on page 560
Example: MMEM:SEL:ALL
Manual operation: See " Items: " on page 254
MMEMory:SELect:CHANnel[:ITEM]:DEFault
MMEMory:SELect[:ITEM]:DEFault
This command selects the current settings as the only item to store to and load from a
configuration file.
Manual operation: See " Items: " on page 254
MMEMory:SELect:CHANnel[:ITEM]:HWSettings <State>
MMEMory:SELect[:ITEM]:HWSettings <State>
This command includes or excludes measurement (hardware) settings when storing or
loading a configuration file.
Measurement settings include:
● general channel configuration
● measurement hardware configuration including markers
● limit lines
Note that a configuration may include no more than 8 limit lines. This number
includes active limit lines as well as inactive limit lines that were used last.
Therefore the combination of inactivate limit lines depends on the sequence of use
with MMEMory:LOAD:STATe on page 562.
● color settings
● configuration for the hardcopy output
Parameters:
<State> ON | OFF | 0 | 1
*RST: 1
Example: MMEM:SEL:HWS ON
Manual operation: See " Items: " on page 254
MMEMory:SELect:CHANnel[:ITEM]:LINes:ALL <State>
MMEMory:SELect[:ITEM]:LINes:ALL <State>
This command includes or excludes all limit lines (active and inactive) when storing or
loading a configuration file.
Parameters:
<State> ON | OFF | 1 | 0
*RST: 0
Example: MMEM:SEL:LIN:ALL ON
Manual operation: See " Items: " on page 254
MMEMory:SELect:CHANnel[:ITEM]:NONE
MMEMory:SELect[:ITEM]:NONE
This command does not include any of the following items when storing or loading a
configuration file.
● Hardware configuration: MMEMory:SELect[:ITEM]:HWSettings on page 559
● Limit lines: MMEMory:SELect[:ITEM]:LINes:ALL on page 560
● Spectrogram data: MMEMory:SELect[:ITEM]:SGRam on page 560
● Trace data: MMEMory:SELect[:ITEM]:TRACe<1...3>[:ACTive]
on page 560
Example: MMEM:SEL:NONE
Manual operation: See " Items: " on page 254
MMEMory:SELect:CHANnel[:ITEM]:SGRam <State>
MMEMory:SELect[:ITEM]:SGRam <State>
This command includes or excludes spectrogram data when storing or loading a con-
figuration file.
Parameters:
<State> ON | OFF | 1 | 0
*RST: 0
Example: MMEM:SEL:SGR ON
Adds the spectrogram data to the list of data subsets.
Manual operation: See " Items: " on page 254
MMEMory:SELect:CHANnel[:ITEM]:TRACe[:ACTive] <State>
MMEMory:SELect[:ITEM]:TRACe<1...3>[:ACTive] <State>
This command includes or excludes trace data when storing or loading a configuration
file.
Suffix: .
<1...3> irrelevant
Parameters:
<State> ON | OFF | 1 | 0
*RST: 0, i.e. no traces are stored
Example: MMEM:SEL:TRAC ON
Manual operation: See " Items: " on page 254
MMEMory:SELect:CHANnel[:ITEM]:TRANsducer:ALL <State>
MMEMory:SELect[:ITEM]:TRANsducer:ALL <State>
This command includes or excludes transducer factors when storing or loading a con-
figuration file.
The command is available in the optional Spectrum application.
Parameters:
<State> ON | OFF | 1 | 0
*RST: 0
Example: MMEM:SEL:TRAN:ALL ON
Manual operation: See " Items: " on page 254
MMEMory:SELect:CHANnel[:ITEM]:WEIGhting <State>
MMEMory:SELect[:ITEM]:WEIGhting <State>
Parameters:
<State>
MMEMory:CLEar:ALL.....................................................................................................561
MMEMory:CLEar:STATe................................................................................................. 562
MMEMory:LOAD:AUTO.................................................................................................. 562
MMEMory:LOAD:STATe..................................................................................................562
MMEMory:STORe<1|2>:STATe....................................................................................... 563
MMEMory:STORe<1|2>:STATe:NEXT.............................................................................. 563
MMEMory:STORe<1|2>:TYPE........................................................................................ 564
SYSTem:PRESet........................................................................................................... 564
SYSTem:PRESet:CHANnel[:EXEC]................................................................................. 564
MMEMory:CLEar:ALL
This command deletes all instrument configuration files in the current directory.
You can select the directory with MMEMory:CDIRectory on page 554.
Example: MMEM:CLE:ALL
Parameters:
<1>
<FileName> String containing the path and name of the file to load.
The string may or may not include the file's extension.
Example: MMEM:SEL:ALL
//Save all items (User Settings, All Traces, All Limit Lines) from
the R&S FSWP.
MMEM:LOAD:STAT 1,'C:\R_S\INSTR\USER\TEST01'
//Reloads all items
In the "Recall" dialog, select only "User Settings" and "All Limit
Lines".
MMEM:LOAD:STAT 1,'C:\R_S\INSTR\USER\TEST01'
//Reloads user settings and all limit lines.
*RST
//Reset instrument.
MMEM:LOAD:STAT 1,'C:\R_S\INSTR\USER\TEST01'
//Selected items are retained. Reloads user settings and all limit
lines.
Restart the instrument.
(Switch the [ON/OFF] key off and on).
MMEM:LOAD:STAT 1,'C:\R_S\INSTR\USER\TEST01'
// Selected items are set to default. Reloads only the user set-
tings.
Manual operation: See " Recall " on page 251
See " Recall in New Channel / Recall in Current Channel "
on page 255
MMEMory:STORe<1|2>:STATe:NEXT
This command saves the current instrument configuration in a *.dfl file.
The file name depends on the one you have set with MMEMory:STORe<1|2>:STATe
on page 563. This command adds a consecutive number to the file name.
Suffix: .
<1|2> irrelevant
Example: MMEM:STOR:STAT 1,'Save'
Saves the current instrument settings in the file Save.dfl.
MMEM:STOR:STAT:NEXT
Saves the current instrument settings in the file Save_001.dfl
MMEM:STOR:STAT:NEXT
Saves the current instrument settings in the file Save_002.dfl
Manual operation: See " Save File " on page 254
MMEMory:STORe<1|2>:TYPE <Type>
This command defines whether the data from the entire instrument or only from the
current channel is stored with the subsequent MMEM:STOR... command.
Suffix: .
<1|2> irrelevant
Parameters:
<Type> INSTrument | CHANnel
INSTrument
Stores data from the entire instrument.
CHANnel
Stores data from an individual channel.
*RST: INST
Example: INST:SEL 'SPECTRUM2'
Selects channel'SPECTRUM2'.
MMEM:STOR:TYPE CHAN
Specifies that channel data is to be stored.
SYSTem:PRESet
This command presets the R&S FSWP. It is identical to *RST.
Example: SYST:PRES
Usage: Event
SYSTem:PRESet:CHANnel[:EXEC]
This command restores the default instrument settings in the current channel.
Use INST:SEL to select the channel.
DISPlay:LOGO <State>
Activates/deactivates the printout of the Rohde & Schwarz company logo at the top of
each page.
Parameters:
<State> 1 | 0 | ON | OFF
1 | ON
Logo is printed.
0 | OFF
Logo is not printed.
*RST: 1
Example: DISP:LOGO OFF
Manual operation: See " Print Logo " on page 262
HCOPy:ABORt
This command aborts a running hardcopy output.
Example: HCOP:ABOR
HCOPy:CMAP<it>:DEFault<ci>
This command defines the color scheme for print jobs.
For details see " Print Colors " on page 287.
Suffix: .
<it> Selects the item for which the color scheme is to be defined.
For more information see Chapter 15.9.4.3, "CMAP Suffix
Assignment", on page 594.
<ci> See table below
Example: HCOP:CMAP:DEF2
Selects the optimized color set for the color settings of a print-
out.
Manual operation: See " Print Colors " on page 287
"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.
Suffix: .
<it> Selects the item for which the color scheme is to be defined.
For more information see Chapter 15.9.4.3, "CMAP Suffix
Assignment", on page 594.
Parameters:
<hue> hue
tint
Range: 0 to 1
<sat> sat
saturation
Range: 0 to 1
<lum> lum
brightness
Range: 0 to 1
Example: HCOP:CMAP2:HSL 0.3,0.8,1.0
Changes the grid color
Manual operation: See "Defining User-specific Colors" on page 289
HCOPy:CMAP<it>:PDEFined <Color>
This command selects a predefined color for various screen elements in print jobs.
Suffix: .
<it> 1..n
Selects the item for which the color scheme is to be defined.
For more information see Chapter 15.9.4.3, "CMAP Suffix
Assignment", on page 594.
Parameters:
<Color> BLACk | BLUE | BROWn | GREen | CYAN | RED | MAGenta |
YELLow | WHITe | DGRay | LGRay | LBLue | LGReen | LCYan |
LRED | LMAGenta
Example: HCOP:CMAP2:PDEF GRE
Manual operation: See " Predefined Colors " on page 289
HCOPy:CONTent <arg0>
This command determines the type of content included in the printout.
This setting is independent of the printing device.
Parameters:
<arg0> WINDows | HCOPy
WINDows
Includes only the selected windows in the printout. All currently
active windows for the current channel (or "MultiView") are avail-
able for selection. How many windows are printed on a each
page of the printout is defined by HCOPy:PAGE:WINDow<1|2>:
COUNt on page 573.
This option is not available when copying to the clipboard
(HCOP:DEST 'SYST:COMM:CLIP' or an image file (see
HCOPy:DEVice:LANGuage<1|2> on page 569).
If the destination is currently set to an image file or the clipboard,
it is automatically changed to be a PDF file for the currently
selected printing device.
HCOPy
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
size and position of the elements in the printout is identical to the
screen display.
*RST: HCOPy
Example: HCOP:DEST1 'SYST:COMM:CLIP'
HCOP:CONT WIND
HCOP:DEST1?
//Result: 'MMEM'
HCOP:DEV:LANG1?
//Result: 'PDF'
"Print to clipboard" is automatically switched to "print to PDF file"
when the contents are switched to "multiple windows".
Manual operation: See " Print Screenshot " on page 262
See " Print Multiple Windows " on page 262
HCOPy:DESTination<1|2> <arg0>
This command selects the destination of a print job.
Suffix: .
<1|2> Printing device.
Parameters:
<arg0> 'MMEM'
Sends the hardcopy to a file.
You can select the file name with MMEMory:NAME.
You can select the file format with HCOPy:DEVice:
LANGuage<1|2>.
'SYST:COMM:PRIN'
Sends the hardcopy to a printer.
You can select the printer with SYSTem:COMMunicate:
PRINter:SELect<1|2> .
'SYST:COMM:CLIP'
Sends the hardcopy to the clipboard.
The format should be WEMF.
*RST: 'SYST:COMM:CLIP'
Manual operation: See " Destination " on page 266
HCOPy:DEVice:COLor <State>
This command turns color printing on and off.
Parameters:
<State> ON | OFF | 0 | 1
ON | 1
Color printing
OFF | 0
Black and white printing
*RST: 1
Example: HCOP:DEV:COL ON
HCOPy:DEVice:LANGuage<1|2> <arg0>
This command selects the file format for a print job.
Suffix: .
<1|2> 1|2
Printing device.
Parameters:
<arg0> WMF | GDI | EWMF | BMP | PNG | JPEG | JPG | PDF | SVG |
DOC | RTF
GDI
Graphics Device Interface
Default format for output to a printer configured under Windows.
Must be selected for output to the printer interface.
Can be used for output to a file. The printer driver configured
under Windows is used to generate a printer-specific file format.
BMP | JPG | PNG | PDF | SVG
Data format for output to files
Example: HCOP:DEV:LANG1 PNG
Manual operation: See " Destination " on page 266
HCOPy[:IMMediate<1|2>]
This command initiates a print job.
If you are printing to a file, the file name depends on MMEMory:NAME.
Suffix: .
<1|2> Printing device.
Manual operation: See " Print " on page 264
HCOPy[:IMMediate<1|2>]:NEXT
This command initiates a print job.
If you are printing to a file, the file name depends on MMEMory:NAME. This command
adds a consecutive number to the file name.
Suffix: .
<1|2> Printing device.
Manual operation: See " Print " on page 264
HCOPy:ITEM:WINDow<1|2>:TEXT <arg0>
This command defines a comment to be added to the printout.
Suffix: .
<1|2> 1|2
Parameters:
<arg0> String containing the comment.
Manual operation: See " Comment " on page 262
HCOPy:PAGE:COUNt:STATe <arg0>
This command includes or excludes the page number for printouts consisting of multi-
ple pages (HCOPy:CONTent on page 567).
Parameters:
<arg0> 1 | 0 | ON | OFF
1 | ON
The page number is printed.
0 | OFF
The page number is not printed.
*RST: 1
Example: HCOP:PAGE:COUN:STAT ON
Manual operation: See " Print Page Count " on page 262
HCOPy:PAGE:MARGin<1|2>:BOTTom <arg0>
This command defines the margin at the bottom of the printout page on which no ele-
ments are printed. The margins are defined according to HCOPy:PAGE:
MARGin<1|2>:UNIT on page 572.
Suffix: .
<1|2> 1|2
Printing device.
Parameters:
<arg0> *RST: 4.23 mm
Example: HCOP:PAGE:MARG2:BOTT 2
Manual operation: See " Margins " on page 268
HCOPy:PAGE:MARGin<1|2>:LEFT <arg0>
This command defines the margin at the left side of the printout page on which no ele-
ments are printed. The margins are defined according to HCOPy:PAGE:
MARGin<1|2>:UNIT on page 572.
Suffix: .
<1|2> 1|2
Printing device.
Parameters:
<arg0> *RST: 4.23 mm
Example: HCOP:PAGE:MARG2:LEFT 2
Manual operation: See " Margins " on page 268
HCOPy:PAGE:MARGin<1|2>:RIGHt <arg0>
This command defines the margin at the right side of the printout page on which no
elements are printed. The margins are defined according to HCOPy:PAGE:
MARGin<1|2>:UNIT on page 572.
Suffix: .
<1|2> 1|2
Printing device.
Parameters:
<arg0> *RST: 4.23 mm
Example: HCOP:PAGE:MARG2:RIGH 2
Manual operation: See " Margins " on page 268
HCOPy:PAGE:MARGin<1|2>:TOP <arg0>
This command defines the margin at the top of the printout page on which no elements
are printed. The margins are defined according to HCOPy:PAGE:MARGin<1|2>:UNIT
on page 572.
Suffix: .
<1|2> 1|2
Printing device.
Parameters:
<arg0> *RST: 4.23 mm
Example: HCOP:PAGE:MARG2:TOP 2
Manual operation: See " Margins " on page 268
HCOPy:PAGE:MARGin<1|2>:UNIT <arg0>
This command defines the unit in which the margins for the printout page are config-
ured.
Suffix: .
<1|2> 1|2
Printing device.
Parameters:
<arg0> MM | IN
MM
millimeters
IN
inches
*RST: MM
Example: HCOP:PAGE:MARG2:BOTT 2
Manual operation: See " Margins " on page 268
HCOPy:PAGE:ORIentation<1|2> <arg0>
The command selects the page orientation of the printout.
The command is only available if the output device is a printer or a PDF file.
Suffix: .
<1|2> 1|2
Printing device.
Parameters:
<arg0> LANDscape | PORTrait
*RST: PORTrait
Example: HCOP:DEV:LANG1 PDF
HCOP:PAGE:ORI2 LAND
HCOPy:PAGE:WINDow<1|2>:COUNt <arg0>
This command defines how many windows are displayed on a single page of the print-
out for HCOPy:CONTent on page 567.
Suffix: .
<1|2> irrelevant
Parameters:
<arg0> integer
*RST: 1
Example: HCOP:PAGE:WIND2:COUN 2
Manual operation: See " Windows Per Page " on page 268
HCOPy:PAGE:WINDow<1|2>:SCALe <arg0>
This command determines the scaling of the windows in the printout for HCOPy:
CONTent on page 567.
Suffix: .
<1|2> irrelevant
Parameters:
<arg0> 1 | 0 | ON | OFF
1 | ON
Each window is scaled to fit the page size optimally, not regard-
ing the aspect ratio of the original display. If more than one win-
dow is printed on one page (see HCOPy:PAGE:WINDow<1|2>:
COUNt on page 573), each window is printed in equal size.
("Size to fit")
0 | OFF
Each window is printed as large as possible while maintaining
the aspect ratio of the original display.
("Maintain aspect ratio")
*RST: 1
Example: HCOP:PAGE:WIND2:SCAL 0
Manual operation: See " Scaling " on page 268
HCOPy:TDSTamp:STATe<1|2> <arg0>
This command includes or excludes the time and date in the printout.
Suffix: .
<1|2> 1|2
Printing device.
Parameters:
<arg0> 1 | 0 | ON | OFF
1 | ON
The time and date are printed.
0 | OFF
The time and date are not printed.
*RST: 1
Manual operation: See " Print Date and Time " on page 263
SYSTem:COMMunicate:PRINter:ENUMerate:FIRSt
This command queries the name of the first available printer.
To query the name of other installed printers, use SYSTem:COMMunicate:PRINter:
ENUMerate[:NEXT] on page 575.
Manual operation: See " Printer Name " on page 266
SYSTem:COMMunicate:PRINter:ENUMerate[:NEXT]
This command queries the name of available printers.
You have to use SYSTem:COMMunicate:PRINter:ENUMerate:FIRSt on page 575
for this command to work properly.
Manual operation: See " Printer Name " on page 266
SYSTem:COMMunicate:PRINter:SELect<1|2> <arg0>
This command selects the printer that processes jobs sent by the R&S FSWP.
Use HCOPy:DESTination<1|2> to select another output destination.
Suffix: .
<1|2> 1|2
Printing device.
Parameters:
<arg0> String containing the printer name.
Use
•SYSTem:COMMunicate:PRINter:ENUMerate:FIRSt
on page 575and
•SYSTem:COMMunicate:PRINter:ENUMerate[:NEXT]
on page 575
to query all available printers.
*RST: NONE
Manual operation: See " Printer Name " on page 266
MMEM:MSIS 'C:'
//Selects drive C: as the default storage device.
-----Connecting a network drive--------
MMEM:NETW:USED?
//Returns a list of all drives in use in the network.
MMEM:NETW:UNUS?
//Returns a list of free drive names in the network.
MMEM:NETW:MAP 'T:','Server\ACLRTest'
//Maps drive T: to the directory 'Server\ACLRTest'
-----Saving data on the instrument-----
MMEM:MDIR 'C:\R_S\INST\USER\ACLRTest'
//Creates a directory called 'ACLRTest' on drive C:
MMEM:NAME 'C:\R_S\INST\USER\Test001.txt'
//Creates a file called 'Test001.txt'
MMEM:COMM 'ACLR test results'
//Creates a comment for the file.
MMEM:DATA 'Test001.txt',#212FileContents
//Writes 12 characters to the file 'Test001.txt'
-----Copying the data to another location---
MMEM:COPY 'C:\R_S\INST\USER\Results\Test001.txt','T:'
//Copies the specified file to network drive T:.
MMEM:DEL 'C:\R_S\INST\USER\Results\Test001.txt'
//Deletes the specified file from the instrument hard disk.
//or
MMEM:MOVE 'C:\R_S\INST\USER\Results\Test001.xml','D:\TestResults.txt'//
//Moves the file 'Test001.txt' to drive T:, renames it to 'Testresults.txt'
//and removes it from the instrument hard disk.
MMEM:RDIR 'C:\R_S\INST\USER\Results'
//Deletes the directory called 'Results' from drive C:, unless it still contains any content.
-----Disconnecting the network drive---
MMEM:NETW:DISC 'T:'
//Disconnect drive T:.
MMEM:CDIR?
//Returns the path of the current directory.
//e.g.
C:\R_S\Instr\user\
MMEM:CDIR 'C:\R_S\INST\USER\Results'
//Changes the current directory.
MMEM:CAT? 'C:\R_S\INST\USER\Results\*.xml'
//or
MMEM:CAT? '*.xml'
//Returns a list of all xml files in the directory 'C:\R_S\INST\USER\Results'.
MMEM:CAT:LONG? '*.xml'
//Returns additional information about the xml files in the directory 'C:\R_S\INST\USER\Result
In this example we will store the instrument settings for the "Spectrum" channel.
INST:SEL 'SPECTRUM'
//Selects measurement channel 'SPECTRUM'.
MEMM:STOR:TYPE CHAN
//Specifies that channel-specific data is to be stored.
MMEM:STOR:STAT 1, 'C:\R_S\Instr\user\Spectrum'
//Stores the channel settings from the 'Spectrum' channel
// to the file 'Spectrum.dfl'.
In this example we will load the hardware settings from the configuration file
Spectrum.dfl to a new "Spectrum2" channel.
MEMM:LOAD:TYPE NEW
//Specifies that settings will be loaded to a new channel besides the existing
//'Spectrum' channel.
MMEM:SEL:CHAN:HWS ON
//Selects only hardware settings to be loaded.
MMEM:LOAD:STAT 1, 'C:\R_S\Instr\user\Spectrum'
//Loads the channel-specific settings from the file 'C:\R_S\Instr\user\Spectrum.dfl'
//to a new channel. The new channel is named 'Spectrum2' to avoid a naming conflict
//with the existing 'Spectrum' channel.
INST:REN 'Spectrum2','Spectrum3'
//Renames the loaded channel to 'Spectrum3'.
HCOP:DEST 'MMEM'
//Prints the data to a file.
HCOP:DEV:LANG BMP
//Selects bmp as the file format.
MMEM:NAME 'C:\R_S\INST\USER\Screenshot.bmp'
//Selects the file name for the printout.
HCOP:ITEM:ALL
//Prints all screen elements
HCOP:ITEM:WIND:TEXT 'ACLRResults'
//Adds a comment to the printout.
HCOP
//Stores the printout in a file called 'Screenshot.bmp'.
HCOP:NEXT
//Stores the printout in a file called 'Screenshot_001.bmp'.
HCOP:DEST2 'SYST:COMM:PRIN'
//Prints the data on a printer.
SYST:COMM:PRIN:ENUM:FIRS?
SYST:COMM:PRIN:ENUM?
//Returns the available printers, e.g.
'LASER on LPT1'
''
//Means that one printer is available.
SYST:COMM:PRIN:SEL2 'LASER on LPT1'
//Selects the printer for the print job on device 2.
HCOP:PAGE:ORI2 LAND
//Selects the landscape format for the printout.
HCOP:TDST:STAT2 ON
//Includes date and time on the printout.
HCOP:ITEM:ALL
//Prints all screen elements
HCOP
//Initiates the printout.
SYSTem:CLOGging....................................................................................................... 580
SYSTem:REBoot............................................................................................................580
SYSTem:SHUTdown...................................................................................................... 580
SYSTem:DATE.............................................................................................................. 580
SYSTem:TIME............................................................................................................... 580
SYSTem:CLOGging <State>
This command turns logging of remote commands on and off.
Parameters:
<State> ON | OFF | 1 | 0
ON | 1
Writes all remote commands that have been sent to a file.
The destination is 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.
OFF | 0
*RST: 0
Manual operation: See "I/O Logging" on page 356
SYSTem:REBoot
This command reboots the instrument, including the operating system.
SYSTem:SHUTdown
This command shuts down the instrument.
Manual operation: See " Set Date and Time " on page 282
[SENSe:]ROSCillator:COUPling:BANDwidth..................................................................... 581
[SENSe:]ROSCillator:COUPling:BANDwidth:MODE.......................................................... 581
[SENSe:]ROSCillator:COUPling:MODE............................................................................ 582
[SENSe:]ROSCillator:LBWidth.........................................................................................582
[SENSe:]ROSCillator:O640............................................................................................. 582
SOURce<si>:EXTernal<ext>:ROSCillator:EXTernal:FREQuency.........................................583
[SENSe:]ROSCillator:OSYNc.......................................................................................... 583
[SENSe:]ROSCillator:SOURce........................................................................................ 584
[SENSe:]ROSCillator:SOURce:EAUTo?........................................................................... 584
[SENSe:]ROSCillator:TRANge.........................................................................................585
[SENSe:]ROSCillator:COUPling:BANDwidth <Bandwidth>
This command defines coupling bandwidth for the internal reference frequency.
Prerequisites for this command
● Options R&S FSWP-B60 or -B61 must be available.
● Select manual bandwidth mode ([SENSe:]ROSCillator:COUPling:
BANDwidth:MODE)
Parameters:
<Bandwidth> <numeric value>
Bandwidths 20 mHz, 1 Hz and 100 kHz are supported.
Default unit: Hz
Example: //Define coupling bandwidth
ROSC:COUP:BAND:MODE MAN
ROSC:COUP:BAND 1HZ
Manual operation: See "Advanced reference frequency configuration" on page 295
[SENSe:]ROSCillator:COUPling:BANDwidth:MODE <Mode>
This command selects coupling bandwidth mode for the internal reference frequency.
Prerequisites for this command
● Options R&S FSWP-B60 or -B61 must be available.
Parameters:
<Mode> AUTO
Automatically selects an appropriate coupling bandwidth.
MANual
Manual selection of coupling bandwidth. You can select the
bandwidth with [SENSe:]ROSCillator:COUPling:
BANDwidth.
*RST: AUTO
Example: //Select coupling bandwidth mode
ROSC:COUP:BAND:MODE AUTO
Manual operation: See "Advanced reference frequency configuration" on page 295
[SENSe:]ROSCillator:COUPling:MODE <State>
This command turns the coupling of the internal reference frequency on and off.
Prerequisites for this command
● Options R&S FSWP-B60 or -B61 must be available.
Parameters:
<State> AUTO
Automatically turns the coupling on and off, depending on the
current measurement scenario.
OFF
Decouples the reference frequencies.
ON
Couples the reference frequencies.
*RST: AUTO
Example: //Synchronize reference frequencies
ROSC:COUP:MODE ON
Manual operation: See "Advanced reference frequency configuration" on page 295
[SENSe:]ROSCillator:LBWidth <Bandwidth>
Defines the loop bandwidth, that is, the speed of internal synchronization with the refer-
ence frequency. The setting requires a compromise between performance and increas-
ing phase noise.
For a variable external reference frequency with a narrow tuning range (+/- 0.5 ppm),
the loop bandwidth is fixed to 0.1 Hz and cannot be changed.
Parameters:
<Bandwidth> 0.1 Hz | 1 Hz | 3 Hz | 10 Hz | 30 Hz | 100 Hz | 300 Hz
The possible values depend on the reference source and tuning
range (see Table 13-1).
Default unit: Hz
Example: ROSC:LBW 3
Manual operation: See "Loop Bandwidth" on page 294
[SENSe:]ROSCillator:O640 <State>
This command turns the output of a reference signal on the corresponding connector
("Ref Output") on and off.
SOURce<si>:EXTernal<ext>:ROSCillator:EXTernal:FREQuency <Frequency>
This command defines the frequency of the external reference oscillator.
If the external reference oscillator is selected, the reference signal must be connected
to the rear panel of the instrument.
Suffix: .
<si> 1..n
<ext> 1..n
Parameters:
<Frequency> Range: 1 MHz to 50 MHz
Default unit: HZ
Example: ROSC:EXT:FREQ 13MHZ
Sets the frequency to 13 MHz.
SOUR:EXT:ROSC:EXT:FREQ 13MHZ
Manual operation: See "Reference Frequency Input" on page 293
[SENSe:]ROSCillator:OSYNc <State>
If enabled, a 100 MHz reference signal is provided to the "SYNC TRIGGER OUTPUT"
connector.
Parameters:
<State> ON | OFF | 1 | 0
*RST: 0
Example: ROSC:OSYN ON
Manual operation: See "Reference Frequency Output" on page 295
[SENSe:]ROSCillator:SOURce <Source>
This command selects the reference oscillator.
If you want to select the external reference, it must be connected to the R&S FSWP.
Parameters:
<Source> INTernal
The internal reference is used (10 MHz)
EXTernal | EXTernal1 | EXT1
The external reference from the "REF INPUT 10 MHZ" connec-
tor is used; if none is available, an error flag is displayed in the
status bar
E10
The external reference from "REF INPUT 1..50 MHZ" connector
is used with a fixed 10 MHZ frequency; if none is available, an
error flag is displayed in the status bar
E100
The external reference from the "REF INPUT 100 MHZ / 1 GHz"
connector is used with a fixed 100 MHZ frequency; if none is
available, an error flag is displayed in the status bar
E1000
The external reference from "REF INPUT 100 MHZ / 1 GHz"
connector is used with a fixed 1 GHZ frequency; if none is avail-
able, an error flag is displayed in the status bar
EAUTo
The external reference is used as long as it is available, then the
instrument switches to the internal reference
SYNC
The external reference is used; if none is available, an error flag
is displayed in the status bar
Example: ROSC:SOUR EXT
Manual operation: See "Reference Frequency Input" on page 293
See "Behavior in case of missing external reference"
on page 294
[SENSe:]ROSCillator:SOURce:EAUTo?
This command queries the current reference type in case you have activated an auto-
matic switch to the internal reference if the external reference is missing.
Return values:
<Reference> INT | EXT
INT
internal reference
EXT
external reference
Example: SENS:ROSC:SOUR:EAUT?
Queries the currently available reference type.
Usage: Query only
Manual operation: See "Behavior in case of missing external reference"
on page 294
[SENSe:]ROSCillator:TRANge <Range>
Defines the tuning range. The tuning range is only available for the variable external
reference frequency. It determines how far the frequency may deviate from the defined
level in parts per million (10-6).
Parameters:
<Range> WIDE | SMALl
The possible values depend on the reference source (see
Table 13-1).
SMALl
With this smaller deviation (+/- 0.5 ppm) a very narrow fixed loop
bandwidth of 0.1 Hz is realized. With this setting the instrument
can synchronize to an external reference signal with a very pre-
cise frequency. Due to the very narrow loop bandwidth, unwan-
ted noise or spurious components on the external reference
input signal are strongly attenuated. Furthermore, the loop
requires about 30 seconds to reach a locked state. During this
locking process, "NO REF" is displayed in the status bar.
WIDE
The larger deviation (+/- 6 ppm) allows the instrument to syn-
chronize to less precise external reference input signals.
Example: ROSC:TRAN WIDE
Manual operation: See "Tuning Range" on page 294
CALibration[:ALL]?......................................................................................................... 586
CALibration:RESult?.......................................................................................................586
DIAGnostic:SERVice:INPut:MC[:DISTance]...................................................................... 587
DIAGnostic:SERVice:INPut:PULSed:CFRequency............................................................ 587
DIAGnostic:SERVice:INPut:RF[:SPECtrum]...................................................................... 587
DIAGnostic:SERVice:INPut[:SELect]................................................................................ 587
DIAGnostic:SERVice:INPut:SYNThtwo[:FREQuency]........................................................ 588
DIAGnostic:SERVice:STESt:RESult?............................................................................... 588
SOURce<si>:TEMPerature:FRONtend.............................................................................588
CALibration[:ALL]?
This command initiates a calibration (self-alignment) routine and queries if calibration
was successful.
During the acquisition of correction data the instrument does not accept any remote
control commands.
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.
In order to recognize when the acquisition of correction data is completed, the MAV bit
in the status byte can be used. If the associated bit is set in the Service Request
Enable (SRE) register, the instrument generates a service request after the acquisition
of correction data has been completed.
Return values:
<CalibrationFailed> ON | OFF | 0 | 1
OFF | 0
Calibration was successful.
ON | 1
Calibration was not successful.
Example: *CLS
Resets the status management.
*SRE 16
Enables MAV bit in the Service Request Enable register.
*CAL?
Starts the correction data recording, and then a service request
is generated.
Usage: Query only
Manual operation: See " Start Self Alignment " on page 278
CALibration:RESult?
This command returns the results collected during calibration.
Return values:
<CalibrationData> String containing the calibration data.
Example: CAL:RES?
would return, e.g.
Total Calibration Status:
PASSED, Date (dd/mm/yyyy): 12/07/2004,
Time: 16:24:54,Runtime: 00.06
Usage: Query only
Manual operation: See " Alignment Results: " on page 280
DIAGnostic:SERVice:INPut:MC[:DISTance] <Bandwidth>
This command selects the distance of the peaks of the microwave calibration signal for
calibration of the YIG filter.
Parameters:
<Bandwidth> WIDE | SMALl
SMALl
Small offset of combline frequencies.
WIDE
Wide offset of combline frequencies.
Manual operation: See " Calibration Frequency MW " on page 307
DIAGnostic:SERVice:INPut:PULSed:CFRequency <Frequency>
This command defines the frequency of the calibration signal.
Before you can use the command, you have to feed in a calibration signal with
DIAGnostic:SERVice:INPut[:SELect] on page 587.
Manual operation: See " Calibration Frequency RF " on page 306
DIAGnostic:SERVice:INPut:RF[:SPECtrum] <Bandwidth>
This command selects the bandwidth of the calibration signal.
Parameters:
<Bandwidth> NARRowband | BROadband
NARRowband
Narrowband signal for power calibration of the frontend.
BROadband
Broadband signal for calibration of the IF filter.
Manual operation: See " Spectrum " on page 306
DIAGnostic:SERVice:INPut[:SELect] <Signal>
This command activates or deactivates the use of an internal calibration signal as input
for the R&S FSWP.
Parameters:
<Signal> CALibration
Uses the calibration signal as RF input.
MCALibration
Uses the calibration signal for the microwave range as RF input.
RF
Uses the signal from the RF input.
SYNTtwo
Uses the calibration signal to check the phase noise of the two
synthesizers. A second synthesizer is available as an hardware
option.
*RST: RF
Example: DIAG:SERV:INP CAL
Uses the calibration signal as RF input.
Manual operation: See " NONE " on page 306
See " Calibration Frequency RF " on page 306
See " Calibration Frequency MW " on page 307
See " Calibration Synthesizer 2 " on page 307
DIAGnostic:SERVice:INPut:SYNThtwo[:FREQuency] <Frequency>
This command selects the frequency which the synthesizers are calibrated for.
The command is available when you select the synthesizer as the calibration source
with DIAGnostic:SERVice:INPut[:SELect] on page 587.
Parameters:
<Frequency> Default unit: Hz
Example: DIAG:SERV:INP:SEL SYNT
DIAG:SERV:INP:SYNT 10MHZ
Manual operation: See " Calibration Synthesizer 2 " on page 307
DIAGnostic:SERVice:STESt:RESult?
This command queries the self-test results.
Return values:
<Results> String of data containing the results.
The rows of the self-test result table are separated by commas.
Example: DIAG:SERV:STES:RES?
would return, e.g.
"Total Selftest Status:
PASSED", "Date (dd/mm/yyyy): 09/07/2004 TIME:
16:24:54", "Runtime: 00:06", "...
Usage: Query only
SOURce<si>:TEMPerature:FRONtend
This command queries the current frontend temperature of the R&S FSWP.
DISPlay:ANNotation:CBAR <State>
This command hides or displays the channel bar information.
Parameters:
<State> ON | OFF | 0 | 1
*RST: 1
Example: DISP:ANN:CBAR OFF
Manual operation: See " Channel Bar " on page 284
DISPlay:ANNotation:FREQuency <State>
This command turns the label of the x-axis on and off.
Parameters:
<State> ON | OFF | 0 | 1
*RST: 1
Example: DISP:ANN:FREQ OFF
Manual operation: See " Diagram Footer (Annotation) " on page 284
DISPlay:SBAR[:STATe] <State>
This command turns the status bar on and off.
Parameters:
<State> ON | OFF | 0 | 1
*RST: 1
Example: DISP:SBAR:OFF
Manual operation: See " Status Bar " on page 284
DISPlay:SKEYs[:STATe] <State>
This command turns the softkey bar on and off.
Parameters:
<State> ON | OFF | 0 | 1
*RST: 1
Example: DISP:SKEY:OFF
Manual operation: See " Softkey Bar " on page 284
DISPlay:TBAR[:STATe] <State>
This command turns the toolbar on or off.
Parameters:
<State> ON | OFF | 1 | 0
*RST: 0
Example: DISP:TBAR ON
Manual operation: See " Toolbar " on page 283
DISPlay:TOUChscreen[:STATe] <State>
This command controls the touch screen functionality.
Parameters:
<State> ON | FRAMe | OFF
ON | 1
Touch screen is active for entire screen
OFF | 0
Touch screen is inactivate for entire screen
FRAMe
Touch screen is inactivate for the diagram area of the screen,
but active for softkeys, toolbars and menus.
*RST: 1
Example: DISP:TOUC:STAT ON
Manual operation: See " Deactivating and Activating the Touchscreen "
on page 282
DISPlay[:WINDow<n>]:TIME <State>
This command adds or removes the date and time from the display.
Suffix: .
<n> irrelevant
Parameters:
<State> ON | OFF | 1 | 0
*RST: 0
Example: DISP:TIME ON
Manual operation: See " Date and Time " on page 284
DISPlay[:WINDow<n>]:TIME:FORMat <Format>
This command selects the time and date format.
Suffix: .
<n> irrelevant
Parameters:
<Format> US | DE
DE
dd.mm.yyyy hh:mm:ss
24 hour format.
US
mm/dd/yyyy hh:mm:ss
12 hour format.
*RST: DE
Example: DISP:TIME ON
Switches the screen display of date and time on.
DISP:TIME:FORM US
Switches the date and time format to US.
Manual operation: See " Date and Time Format " on page 283
SYSTem:DISPlay:FPANel[:STATe] <State>
This command includes or excludes the front panel keys when working with the remote
desktop.
Parameters:
<State> ON | OFF | 0 | 1
*RST: 1
Manual operation: See " Front Panel " on page 284
See " Mini Front Panel " on page 285
DISPlay:CMAP<it>:DEFault<ci>
This command resets the color scheme for the display. The query returns the default
color scheme.
Suffix: .
<it> Selects the item for which the color scheme is to be defined.
For more information see Chapter 15.9.4.3, "CMAP Suffix
Assignment", on page 594.
<ci> 1
Current colors with a white background and a black grid.
2
Optimized colors.
3
Customized colors.
4
Current screen colors (setting for hardcopies).
Suffix irrelevant for query
Return values:
<DefScheme> 1|2|3|4
The default color scheme for the selected item, as specified by
the <ci> suffix.
Example: DISP:CMAP:DEF2
Selects default setting 2 for setting the colors.
DISP:CMAP:DEF?
//Result: 2
Manual operation: See " Screen Colors " on page 287
DISPlay:CMAP<it>:PDEFined <Color>
This command selects a predefined color for various screen elements.
Suffix: .
<it> 1..n
Selects the item for which the color scheme is to be defined.
For more information see Chapter 15.9.4.3, "CMAP Suffix
Assignment", on page 594.
Parameters:
<Color> BLACk | BLUE | BROWn | GREen | CYAN | RED | MAGenta |
YELLow | WHITe | DGRay | LGRay | LBLue | LGReen | LCYan |
LRED | LMAGenta
Example: DISP:CMAP2:PDEF GRE
Manual operation: See "Restoring the User Settings to Default Colors" on page 289
DISPlay:THEMe:CATalog?
This command queries all available display themes.
Return values:
<Themes> String containing all available display themes.
Example: DISP:THEMe:CAT?
Usage: Query only
DISPlay:THEMe:SELect <Theme>
This command selects the display theme.
Parameters:
<Theme> String containing the name of the theme.
*RST: SPL
Example: DISP:THEM:SEL "BlueOcean"
Manual operation: See " Theme " on page 287
Several commands to change the color settings of individual items of the display or
printout are available. Which item is to be configured is defined using a <CMAP> suffix.
The following assignment applies:
Suffix Description
CMAP1 Background
CMAP2 Grid
CMAP8 Trace 1
CMAP9 Trace 2
CMAP10 Trace 3
Suffix Description
CMAP24 Logo
CMAP25 Trace 4
CMAP27 Marker
CMAP40 Trace 5
CMAP41 Trace 6
*) these settings can only be defined via the theme (DISPlay:THEMe:SELect) and are thus ignored in
the SCPI command
SYSTem:COMMunicate:GPIB[:SELF]:ADDRess............................................................... 596
SYSTem:COMMunicate:GPIB[:SELF]:RTERminator.......................................................... 596
SYSTem:DISPlay:LOCK................................................................................................. 597
SYSTem:DISPlay:UPDate...............................................................................................597
SYSTem:ERRor:CLEar:REMote...................................................................................... 597
SYSTem:ERRor:DISPlay................................................................................................ 597
SYSTem:IDENtify:FACTory..............................................................................................598
SYSTem:IDENtify[:STRing]............................................................................................. 598
SYSTem:KLOCk............................................................................................................ 598
SYSTem:LANGuage.......................................................................................................598
SYSTem:LXI:LANReset.................................................................................................. 599
SYSTem:LXI:MDEScription............................................................................................. 599
SYSTem:LXI:PASSword..................................................................................................599
SYSTem:PSA:WIDeband................................................................................................ 599
SYSTem:SHIMmediate:STATe......................................................................................... 599
SYSTem:SHIMmediate ONCE.........................................................................................600
SYSTem:COMMunicate:GPIB[:SELF]:ADDRess <Address>
This command sets the GPIB address of the R&S FSWP.
Parameters:
<Address> Range: 0 to 30
*RST: (no influence on this parameter, factory default 20)
Example: SYST:COMM:GPIB:ADDR 18
Manual operation: See "GPIB Address" on page 355
SYSTem:COMMunicate:GPIB[:SELF]:RTERminator <Terminator>
This command selects the GPIB receive terminator.
Output of binary data from the instrument to the control computer does not require
such a terminator change.
Parameters:
<Terminator> LFEOI | EOI
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 com-
puter 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.
*RST: LFEOI
Example: SYST:COMM:GPIB:RTER EOI
Manual operation: See "GPIB Terminator" on page 356
SYSTem:DISPlay:LOCK <State>
Defines whether the "Display Update" function remains available in remote operation
or not.
Parameters:
<State> ON | OFF | 0 | 1
OFF | 0
The function remains available.
ON | 1
The function is not available and the display is not updated dur-
ing remote operation.
*RST: 0
SYSTem:DISPlay:UPDate <State>
This command turns the display during remote operation on and off.
If on, the R&S FSWP updates the diagrams, traces and display fields only.
The best performance is obtained if the display is off during remote control operation.
Parameters:
<State> ON | OFF | 1 | 0
*RST: 0
Example: SYST:DISP:UPD ON
Manual operation: See "Remote Display Update" on page 356
SYSTem:ERRor:CLEar:REMote
This command deletes all contents of the "Remote Errors" table.
Note: The remote error list is automatically cleared when the R&S FSWP is shut down.
Example: SYST:ERR:CLE:REM
Manual operation: See "Display Remote Errors" on page 357
See "Clear Error List" on page 361
SYSTem:ERRor:DISPlay <State>
This command the error display during remote operation on and off.
If activated, the R&S FSWP displays a message box at the bottom of the screen that
contains the most recent type of error and the command that caused the error.
Parameters:
<State> ON | OFF | 1 | 0
*RST: 0
Example: SYST:ERR:DISP ON
SYSTem:IDENtify:FACTory
This command resets the query to *IDN? to its default value.
Manual operation: See "Reset to Factory String" on page 355
SYSTem:IDENtify[:STRing] <String>
This command defines the response to *IDN?.
Parameters:
<String> String containing the description of the instrument.
Manual operation: See "Identification String" on page 355
SYSTem:KLOCk <State>
This command activates the local lockout (remote control) or returns to the local mode.
Parameters:
<State> ON
LLO (local lockout)
OFF
GTL (go to local)
*RST: OFF
Example: SYST:KLOC ON
Activates LLO (remote control)
Manual operation: See "Local" on page 361
SYSTem:LANGuage <Language>
This command selects the system language.
Parameters:
<Language> String containing the name of the language.
'SCPI'
SCPI language.
'PSA'
PSA emulation.
For a list of supported commands, see Chapter 15.9.9, "Refer-
ence: Command Set of Emulated PSA Models", on page 610.
*RST: SCPI
Example: SYST:LANG 'PSA'
Emulates the PSA.
Manual operation: See "Language" on page 358
SYSTem:LXI:LANReset
This command resets the LAN configuration, as well as the "LAN" password and
instrument description.
Manual operation: See " LAN Reset" on page 360
SYSTem:LXI:MDEScription <Description>
This command defines the "LAN" instrument description.
Parameters:
<Description> String containing the instrument description.
SYSTem:LXI:PASSword <Password>
This command defines the "LAN" password.
Parameters:
<Password> String containing the password.
Manual operation: See "LAN Password" on page 360
SYSTem:PSA:WIDeband <State>
This command 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.
Parameters:
<State> ON | OFF | HIGH
OFF
The option is indicated as "B7J"
ON
The 40 MHz wideband is used.
The option is indicated as "B7J, 140".
HIGH
The 80 MHz wideband is used.
The option is indicated as "B7J, 122".
*RST: OFF
Manual operation: See "Wideband" on page 358
SYSTem:SHIMmediate:STATe <State>
Determines when the remote commands that change hardware settings on the
R&S FSWP are executed.
Regardless of this setting, the firmware automatically sets the hardware when a sweep
is started.
SYSTem:SHIMmediate ONCE
Executes any received remote commands that cause changes to the hardware and
have not been executed yet due to a SYST:SHIM:STAT OFF command.
Example: SYST:SHIM:STAT ON
...
SYST:SHIM ONCE
Usage: Event
Manual operation: See "Set Hardware Immediately" on page 357
DIAGnostic:INFO:CCOunt? <Relay>
This command queries how many switching cycles the individual relays have per-
formed since they were installed.
Query parameters:
<Relay> ACDC
Mechanical Attenuation Coupling
ATT5
Mechanical Attenuation 05 DB
ATT10
Mechanical Attenuation 10 DB
ATT20
Mechanical Attenuation 20 DB
ATT40
Mechanical Attenuation 40 DB
CAL
Mechanical Calibration Source
EATT
Electrical Attenuation Bypass
PREamp
Preamplifier Bypass
SATT10 | SATT20 | SATT40
Mechanical attenuation (10, 20 and 40 dB) for the optional Sig-
nal Source hardware.
SCAL
DUT bypass (available with the optional Signal Source hard-
ware).
Return values:
<Cycles> Number of switching cycles.
Example: DIAG:INFO:CCO? CAL
Usage: Query only
Manual operation: See " Relays Cycle Counter " on page 310
DIAGnostic:SERVice:BIOSinfo?
This command queries the BIOS version of the CPU board.
Return values:
<BiosInformation> String containing the BIOS version.
Example: DIAG:SERV:BIOS?
Returns the BIOS version.
Usage: Query only
DIAGnostic:SERVice:HWINfo?
This command queries hardware information.
Return values:
<Hardware> String containing the following information for every hardware
component.
<component>: name of the hardware component
<serial#>: serial number of the component
<order#>: order number of the component
<model>: model of the component
<code>: code of the component
<revision>: revision of the component
<subrevision>: subrevision of the component
Example: DIAG:SERV:HWIN?
Queries the hardware information.
"FRONTEND|100001/003|1300.3009|03|01|00|00",
"MOTHERBOARD|123456/002|1300.3080|02|00|00|00",
...
Usage: Query only
DIAGnostic:SERVice:VERSinfo?
This command queries information about the hardware and software components.
Return values:
<Information> String containing the version of hardware and software compo-
nents including the types of licenses for installed options.
Example: DIAG:SERV:VERS?
Queries the version information.
Response:
Instrument Firmware |1.10,
BIOS |R&S ANALYZER BIOS V1.80-5-07-1 IPC11,
Image Version |1.6.0,
Device Installation Version |1.0.0,
PCIE-FPGA |13.06,
SA-FPGA |6.46,
MB-FPGA |2.1.3.0,
SYNTH-18G-FPGA |4.8.0.0,
SYNTH-18G-FPGA 2 |4.8.0.0,
REF-FPGA |3.4.0.0,
MWC-FPGA |3.4.0.0,
PNDIGIT-FPGA |0.46,
Data Sheet Version |01.00,
Time Control Management ||active,
Cross Correlation Measurements B60||,
Signal Source B64||,
80 MHz Analysis Bandwidth B80||permanent
SYSTem:ERRor:CLEar:ALL
This command deletes all contents of the "System Messages" table.
Example: SYST:ERR:CLE:ALL
SYSTem:ERRor:LIST? [<MessType>]
This command queries the error messages that occur during R&S FSWP operation.
Query parameters:
<MessType> SMSG | REMote
SMSG
(default) Queries the system messages which occurred during
manual operation.
REMote
Queries the error messages that occurred during remote opera-
tion.
Note: The remote error list is automatically cleared when the
R&S FSWP is shut down.
Return values:
<SystemMessages> String containing all messages in the "System Messages" table.
<RemoteErrors> <Error_no> | <Description> | <Command> | <Date> | <Time>
Comma-separated list of errors from the "Remote Errors" table,
where:
<Error_no>: device-specific error code
<Description>: brief description of the error
<Command>: remote command causing the error
<Date>|<Time>: date and time the error occurred
Usage: Query only
SYSTem:ERRor[:NEXT]?
This command queries the most recent error queue entry and deletes it.
Positive error numbers indicate device-specific errors, negative error numbers are error
messages defined by SCPI. If the error queue is empty, the error number 0, "No error",
is returned.
For details on error queues see Chapter 14.1.7, "Status Reporting System",
on page 332.
Usage: Query only
SYSTem:FIRMware:UPDate <Directory>
This command starts a firmware update using the *.msi files in the selected directory.
The default path is D:\FW_UPDATE. The path is changed via the MMEMory:COMMent
command. To store the update files the MMEMory:DATA command is used.
Only user accounts with administrator rights can perform a firmware update.
Setting parameters:
<Directory>
Example: SYST:FIRM:UPD 'D:\FW_UPDATE'
Starts the firmware update from directory "D:\FW_UPDATE".
SYSTem:FORMat:IDENt <IDNFormat>
This command selects the response format to the *IDN? query.
Parameters:
<IDNFormat> LEGacy
Format is compatible to R&S FSP/FSU/FSQ/FSG family.
NEW | FSL
R&S FSWP format
Format is also compatible to the R&S FSL and R&S FSV family
*RST: not reset!
Example: SYST:FORM:IDEN LEG
Adapts the return value of *IDN? to the R&S FSP/FSU/FSQ fam-
ily.
Manual operation: See "*IDN Format" on page 356
SYSTem:PRESet:COMPatible <OpMode>
This command defines the operating mode that is activated when you switch on the
R&S FSWP or press the [PRESET] key.
Parameters:
<OpMode> SANalyzer
Defines Signal and Spectrum Analyzer operating mode as the
presetting.
OFF
Selects the phase noise application as the default application
(default value).
Manual operation: See " Preset Mode " on page 302
SYSTem:PRESet:FILTer <FilterType>
This command selects the resolution filter type that is selected after a preset in the
Spectrum application.
Parameters:
<FilterType> NORMal
Selects 3 dB filter.
NOISe
Selects 3 dB filter.
(NORMal and NOISe have the same effect.)
PULSe
Selects 6 dB filter.
*RST: NORMal
Example: //Select the 6 dB filters as the default filter type
SYST:PRES:FILT PULS
SYSTem:SECurity[:STATe] <State>
Activates or queries secure user mode.
Note: Before you activate secure user mode, store any instrument settings that are
required beyond the current session, such as predefined instrument settings, trans-
ducer files, or self-alignment data.
Note: Initially after installation of the R&S FSWP-K33 option, secure user mode must
be enabled manually once before remote control is possible. This is necessary to
prompt for a change of passwords.
For details on the secure user mode see Chapter 4.7, "Protecting Data Using the
Secure User Mode", on page 31.
Parameters:
<State> ON | OFF | 0 | 1
ON | 1
The R&S FSWP automatically reboots and starts in secure user
mode. In secure user mode, no data is written to the instru-
ment's internal solid-state drive. Data that the R&S FSWP nor-
mally stores on the solid-state drive is redirected to SDRAM.
OFF | 0
The R&S FSWP is set to normal instrument mode. Data is
stored to the internal solid-state drive.
Note: this parameter is for query only. Secure user mode cannot
be deactivated via remote operation.
*RST: 0
Manual operation: See " SecureUser Mode " on page 302
DIAGnostic:SERVice:SFUNction......................................................................................606
DIAGnostic:SERVice:SFUNction:LASTresult?................................................................... 607
DIAGnostic:SERVice:SFUNction:RESults:DELete............................................................. 607
DIAGnostic:SERVice:SFUNction:RESults:SAVE................................................................607
DIAGnostic:SERVice:SINFo?.......................................................................................... 607
SYSTem:PASSword:RESet............................................................................................. 608
SYSTem:PASSword[:CENable]........................................................................................608
DIAGnostic:SERVice:SFUNction <ServiceFunction>
This command starts a service function.
The service functions are available after you have entered the level 1 or level 2 system
password.
Parameters for setting and query:
<ServiceFunction> String containing the ID of the service function.
The ID of the service function is made up out of five numbers,
separated by a point.
• function group number
• board number
• function number
• parameter 1 (see the Service Manual)
• parameter 2 (see the Service Manual)
DIAGnostic:SERVice:SFUNction:LASTresult?
This command queries the results of the most recent service function you have used.
Return values:
<Result>
Usage: Query only
DIAGnostic:SERVice:SFUNction:RESults:DELete
This command deletes the results of the most recent service function you have used.
Usage: Event
Manual operation: See " Clear Results " on page 309
DIAGnostic:SERVice:SFUNction:RESults:SAVE [<FileName>]
This command saves the results of the most recent service function you have used.
Parameters:
<FileName> String containing the file name.
Manual operation: See " Save Results " on page 309
DIAGnostic:SERVice:SINFo?
This command creates a *.zip file with important support information. The *.zip file con-
tains the system configuration information ("device footprint"), the current eeprom data
and a screenshot of the screen display (if available).
This data is stored to the C:\R_S\INSTR\USER directory on the instrument.
As a result of this command, the created file name (including the drive and path) is
returned.
You can use the resulting file name information as a parameter for the MMEM:COPY
command to store the file on the controller PC.
If you contact the Rohde&Schwarz support to get help for a certain problem, send this
file to the support in order to identify and solve the problem faster.
Return values:
<FileName> C:\R_S\INSTR\USER
\<R&S Device ID>_<CurrentDate>_<CurrentTime>
String containing the drive, path and file name of the created
support file, where the file name consists of the following ele-
ments:
<R&S Device ID>: The unique R&S device ID indicated in the
"Versions + Options" information
<CurrentDate>: The date on which the file is created
(<YYYYMMDD>)
<CurrentTime>: The time at which the file is created
(<HHMMSS>)
Example: DIAG:SERV:SINF?
Result:
"c:\R&S\instr\user\FSWP-26_1322.8003K26-100005-xx_20130116_165858.zip"
MMEM:COPY "c:\R&S\instr\user\FSWP-26_
1322.8003K26-100005-xx_20130116_165858.zip",
"S:\Debug\FSWP-26_1322.8003K26-100005-xx_
20130116_165858.zip"
SYSTem:PASSword:RESet
Clears any previously provided password and returns to the most restrictive service
level.
Manual operation: See " Password " on page 309
SYSTem:PASSword[:CENable] <arg0>
Provides a password for subsequent service functions.
Parameters:
<arg0> string
Example: SYST:PASS:CEN '894129'
Manual operation: See " Password " on page 309
CALCulate:PN{xch}:DATA:CARRier
CALCulate:PN{xch}:TRACe{trc}:BDMarker:X:STARt
CALCulate:PN{xch}:TRACe{trc}:BDMarker:X:STATe
CALCulate:PN{xch}:TRACe{trc}:BDMarker:X:STOP
CALCulate:PN{xch}:TRACe{trc}:FUNCtion:INTegral:DATA
CALCulate:PN{xch}:TRACe{trc}:FUNCtion:DOMain:X
CALCulate:PN{xch}:TRACe{trc}:FUNCtion:DOMain:Y
CALCulate:PN{xch}:TRACe{trc}:FUNCtion:TYPE
CALCulate:PN{xch}:TRACe{trc}:LIMit:FAIL
CALCulate:PN{xch}:TRACe{trc}:LIMit:LOWer:SEGMent:CLEar
CALCulate:PN{xch}:TRACe{trc}:LIMit:LOWer:SEGMent:COUNt
CALCulate:PN{xch}:TRACe{trc}:LIMit:LOWer:SEGMent:DATA
CALCulate:PN{xch}:TRACe{trc}:LIMit:STATe
CALCulate:PN{xch}:TRACe{trc}:LIMit:UPPer:SEGMent:CLEar
CALCulate:PN{xch}:TRACe{trc}:LIMit:UPPer:SEGMent:COUNt
CALCulate:PN{xch}:TRACe{trc}:LIMit:UPPer:SEGMent:DATA
CALCulate:PN{xch}:TRACe{trc}:MARKer{mk}:SEARch:EXECute:LPEak
CALCulate:PN{xch}:TRACe{trc}:MARKer{mk}:SEARch:EXECute:MAXimum
CALCulate:PN{xch}:TRACe{trc}:MARKer{mk}:SEARch:EXECute:MINimum
CALCulate:PN{xch}:TRACe{trc}:MARKer{mk}:SEARch:EXECute:PEAK
CALCulate:PN{xch}:TRACe{trc}:MARKer{mk}:SEARch:EXECute:RPEak
CALCulate:PN{xch}:TRACe{trc}:MARKer{mk}:SEARch:PEAK:EXCursion
CALCulate:PN{xch}:TRACe{trc}:MARKer{mk}:STATe
CALCulate:PN{xch}:TRACe{trc}:MARKer{mk}:X
CALCulate:PN{xch}:TRACe{trc}:MARKer{mk}:Y
CALCulate:PN{xch}:TRACe{trc}:SMOothing:APERture
CALCulate:PN{xch}:TRACe{trc}:SMOothing:STATe
CALCulate:PN{xch}:TRACe{trc}:SPURious:OMISsion
CALCulate:PN{xch}:TRACe{trc}:SPURious:POWer
DISPlay:MAXimize
DISPlay:PN{xch}:MAXimize
DISPlay:PN{xch}:STATe
DISPlay:WINDow:ACTive
INITiate:PN{xch}:CONTinuous
INITiate:PN{xch}:IMMediate
[SENSe]:ATTenuation:LEVel
[SENSe]:PN{xch}:ASET
[SENSe]:PN{xch}:AVERage:CLEar
[SENSe]:PN{xch}:AVERage:STATe
[SENSe]:PN{xch}:AVERage:COUNt
[SENSe]:PN{xch}:CORRelation:COUNt
[SENSe]:PN{xch}:CRANge
[SENSe]:PN{xch}:FBANd
[SENSe]:PN{xch}:FREQuency:STARt
[SENSe]:PN{xch}:FREQuency:STOP
[SENSe]:PN{xch}:IFGain
[SENSe]:PN{xch}:LOBandwidth
[SENSe]:PN{xch}:ROSCillator:BANDwidth
[SENSe]:PN{xch}:ROSCillator:REFerence{ref}:SOURce
[SENSe]:PN{xch}:SEGTable:MEASurement:QUALity
[SENSe]:PN{xch}:SWEep:POINts
TRIGger:AVERage
TRIGger:MODE
TRIGger:PN:SOURce
TRIGger:SOPC
The R&S FSWP analyzer family supports a subset of the GPIB commands of
PSA89600 instruments.
Despite the differences in system architecture and device features, the supported com-
mands have been implemented in a way to ensure a sufficiently high degree of corre-
spondence with the original.
In many cases the selection of commands supported by the R&S FSWP is sufficient to
run an existing GPIB program without adaptation.
*CAL?
*CLS
*ESE
*ESR?
*IDN?
*IST?
*OPC
*OPT?
*PCB
*PRE
*PSC
*RST
*SRE
*STB?
*TRG
*TST?
*WAI
:CALibration:AUTO OFF|ON|ALERt
:CALibration:TCORrections AUTO|ON|OFF
:CONFigure:WAVeform
:DIAGnostic:EABY ON|OFF
:DIAGnostic:LATCh:VALue <numeric>
:DIAGnostic:LATCh:SELect <string>
:DISPlay:ANNotation:TITLe:DATA <string>
:DISPlay:ENABle OFF|ON
:DISPlay:WINDow:TRACe:Y:[SCALe]:PDIVision <numeric>
:DISPlay:WINDow:TRACe:Y:[SCALe]:RLEVel <numeric>
:DISPlay:WINDow:TRACe:Y:[SCALe]:RLEVel:OFFSet <numeric>
:FORMat:BORDer NORMal|SWAPped
:FORMat[:DATA] ASCii|REAL|UINT|MATLAB,<numeric>
:INITiate:CONTinuous OFF|ON
:INITiate[:IMMediate]
:INSTrument:CATalog?
:INSTrument:NSELect <numeric>
:MMEMory:CATalog? <dir_name>
:MMEMory:COPY <‘file_name1’>,<‘file_name2’>
:MMEMory:DATA <‘file_name’>,<definite_length_block>
:MMEMory:DELete <‘file_name’>
:MMEMory:LOAD:STATe 1,<‘file_name’>
:MMEMory:LOAD:TRACe 1,<‘file_name’>
:MMEMory:MDIRectory <‘dir_name’>
:MMEMory:MOVE <‘file_name1’>,<‘file_name2’>
:MMEMory:STORe:STATe 1,<‘file_name’>
:MMEMory:STORe:TRACe <numeric>,<‘file_name’>
:READ:WAVform?
[:SENSe]:FREQuency:CENTer <numeric>
[:SENSe]:FREQuency:STARt <numeric>
[:SENSe]:FREQuency:STOP <numeric>
[:SENSe]:FREQuency:SPAN <numeric>
[:SENSe]:POWer:ATTenuation <numeric>
[:SENSe]:ROSCillator:EXTernal:FREQuency <numeric>
[:SENSe]:ROSCillator:OUTPut OFF|ON
[:SENSe]:ROSCillator:SOURce INTernal|EXTernal|EAUTo
[:SENSe]:SPECtrum:TRIGger:SOURce EXTernal<1|2>|IF|IMMediate
[:SENSe]:WAVeform:ADC:RANGe P6
[:SENSe]:WAVeform:APER?
[:SENSe]:WAVeform:AVERage:TACount <numeric>
[:SENSe]:WAVeform:BWIDth:ACTive?
[:SENSe]:WAVeform:BWIDth:TYPE FLAT|GAUSsian
[:SENSe]:WAVeform:IFGain <numeric>
[:SENSe]:WAVeform:IFPath NARRow|WIDE
[:SENSe]:WAVeform:NCPTrace ON|OFF
[:SENSe]:WAVeform:PDIT ON|OFF
[:SENSe]:WAVeform:SRATe <numeric>
[:SENSe]:WAVeform:SWEep:TIME <numeric>
[:SENSe]:WAVeform:TRIGger:EOFFset?
[:SENSe]:WAVeform:TRIGger:INTerpolation ON|OFF
[:SENSe]:WAVeform:TRIGger:SOURce EXTernal<1|2>|IF|IMMediate
:STATus:QUEStionable:CONDition?
:STATus:QUEStionable:ENABle <number>
:STATus:QUEStionable:NTRansition <number>
:STATus:QUEStionable:PTRansition <number>
:STATus:QUEStionable[:EVENt]?
:STATus:QUEStionable:CALibration:CONDition?
:STATus:QUEStionable:CALibration:ENABle <number>
:STATus:QUEStionable:CALibration:NTRansition <number>
:STATus:QUEStionable:CALibration:PTRansition <number>
:STATus:QUEStionable:CALibration[:EVENt]?
:STATus:QUEStionable:FREQuency:CONDition?
:STATus:QUEStionable:FREQuency:ENABle <number>
:STATus:QUEStionable:FREQuency:NTRansition <number>
:STATus:QUEStionable:FREQuency:PTRansition <number>
:STATus:QUEStionable:FREQuency[:EVENt]?
:STATus:QUEStionable:INTegrity:CONDition?
:STATus:QUEStionable:INTegrity:ENABle <number>
:STATus:QUEStionable:INTegrity:NTRansition <number>
:STATus:QUEStionable:INTegrity:PTRansition <number>
:STATus:QUEStionable:INTegrity[:EVENt]?
:STATus:OPERation:CONDition?
:STATus:OPERation:ENABle <integer>
:STATus:OPERation:NTRansition <integer>
:STATus:OPERation:PTRansition <integer>
:STATus:OPERation[:EVENt]?
:SYSTem:COMMunicate:GPIB[:SELF]:ADDRess <integer>
:SYSTem:DATE <year>,<month>,<day>
:SYSTem:ERRor[:NEXT]?
:SYSTem:KLOCK?
:SYSTem:MESSage <string>
:SYSTem:PRESet
:SYSTem:TIME <hour>,<minute>,<second>
:SYSTem:VERSion?
:TRACe:COPY <src_trace>,<dest_trace>
:TRACe:MODE WRITe|MAXHold|MINHold|VIEW|BLANk
:TRIGger[:SEQuence]:DELay <numeric>
:TRIGger[:SEQuence]:DELay:STATe OFF|ON|0|1
:TRIGger[:SEQuence]:EXTermal:DELay <numeric>
:TRIGger[:SEQuence]:EXTermal:LEVel <numeric>
:TRIGger[:SEQuence]:EXTermal:SLOPe POSitive|NEGative
:TRIGger[:SEQuence]:HOLDoff <numeric>
:TRIGger[:SEQuence]:IF:DELay <numeric>
:TRIGger[:SEQuence]:IF:LEVel <numeric>
:TRIGger[:SEQuence]:IF:SLOPe POSitive|NEGative
:TRIGger[:SEQuence]:SLOPe POSitive|NEGative
:TRIGger[:SEQuence]:SOURce IMMediate|VIDeo|EXTernal<1|2>
:TRIGger[:SEQuence]:VIDeo:LEVel <numeric>
:TRIGger[:SEQuence]:VIDeo:LEVel:FREQuency <freq>
STATus:PRESet.............................................................................................................615
STATus:QUEue[:NEXT]?................................................................................................ 615
STATus:PRESet
This command resets the edge detectors and ENABle parts of all registers to a defined
value. All PTRansition parts are set to FFFFh, i.e. all transitions from 0 to 1 are
detected. All NTRansition parts are set to 0, i.e. a transition from 1 to 0 in a
CONDition bit is not detected. The ENABle part of the STATus:OPERation and
STATus:QUEStionable registers are set to 0, i.e. all events in these registers are not
passed on.
Usage: Event
STATus:QUEue[:NEXT]?
This command queries the most recent error queue entry and deletes it.
Positive error numbers indicate device-specific errors, negative error numbers are error
messages defined by SCPI. If the error queue is empty, the error number 0, "No error",
is returned.
This command is identical to the SYSTem:ERRor[:NEXT]? command.
Usage: Query only
For more information on the condition part see Chapter 14.1.7.2, "Structure of a SCPI
Status Register", on page 334.
STATus:OPERation:CONDition?
STATus:QUEStionable:CONDition?
STATus:QUEStionable:ACPLimit:CONDition? <ChannelName>
STATus:QUEStionable:EXTended:CONDition? <ChannelName>
STATus:QUEStionable:EXTended:INFO:CONDition? <ChannelName>
STATus:QUEStionable:FREQuency:CONDition? <ChannelName>
STATus:QUEStionable:LIMit<n>:CONDition? <ChannelName>
STATus:QUEStionable:LMARgin<n>:CONDition? <ChannelName>
STATus:QUEStionable:PNOise:CONDition? <ChannelName>
STATus:QUEStionable:POWer:CONDition? <ChannelName>
STATus:QUEStionable:POWer:DCPNoise:CONDition? <ChannelName>
STATus:QUEStionable:TEMPerature:CONDition? <ChannelName>
STATus:QUEStionable:TIME:CONDition? <ChannelName>
These commands read out the CONDition section of the status register.
The commands do not delete the contents of the CONDition section.
Suffix: .
<n> Window
Query parameters:
<ChannelName> String containing the name of the channel.
The parameter is optional. If you omit it, the command works for
the currently active channel.
Usage: Query only
For more information on the event part see Chapter 14.1.7.2, "Structure of a SCPI Sta-
tus Register", on page 334.
STATus:OPERation[:EVENt]?
STATus:QUEStionable[:EVENt]?
STATus:QUEStionable:ACPLimit[:EVENt]? <ChannelName>
STATus:QUEStionable:EXTended[:EVENt]? <ChannelName>
STATus:QUEStionable:EXTended:INFO[:EVENt]? <ChannelName>
STATus:QUEStionable:FREQuency[:EVENt]? <ChannelName>
STATus:QUEStionable:LIMit<n>[:EVENt]? <ChannelName>
STATus:QUEStionable:LMARgin<n>[:EVENt]? <ChannelName>
STATus:QUEStionable:PNOise[:EVENt]? <ChannelName>
STATus:QUEStionable:POWer[:EVENt]? <ChannelName>
STATus:QUEStionable:POWer:DCPNoise[:EVENt]? <ChannelName>
STATus:QUEStionable:TEMPerature[:EVENt]? <ChannelName>
STATus:QUEStionable:TIME[:EVENt]? <ChannelName>
These commands read out the EVENt section of the status register.
At the same time, the commands delete the contents of the EVENt section.
Suffix: .
<n> Window
Query parameters:
<ChannelName> String containing the name of the channel.
The parameter is optional. If you omit it, the command works for
the currently active channel.
Usage: Query only
For more information on the enable part see Chapter 14.1.7.2, "Structure of a SCPI
Status Register", on page 334.
STATus:OPERation:ENABle <SumBit>
STATus:QUEStionable:ENABle <SumBit>
STATus:QUEStionable:ACPLimit:ENABle <SumBit>,<ChannelName>
STATus:QUEStionable:EXTended:ENABle <SumBit>,<ChannelName>
STATus:QUEStionable:EXTended:INFO:ENABle <SumBit>,<ChannelName>
STATus:QUEStionable:FREQuency:ENABle <SumBit>,<ChannelName>
STATus:QUEStionable:LIMit<n>:ENABle <SumBit>,<ChannelName>
STATus:QUEStionable:LMARgin<n>:ENABle <SumBit>,<ChannelName>
STATus:QUEStionable:PNOise:ENABle <SumBit>,<ChannelName>
STATus:QUEStionable:POWer:ENABle <SumBit>,<ChannelName>
STATus:QUEStionable:POWer:DCPNoise:ENABle <SumBit>,<ChannelName>
STATus:QUEStionable:TEMPerature:ENABle <SumBit>,<ChannelName>
STATus:QUEStionable:TIME:ENABle <SumBit>,<ChannelName>
These commands control the ENABle part of a register.
The ENABle part allows true conditions in the EVENt part of the status register to bere-
ported in the summary bit. If a bit is 1 in the enable register and its associated event bit
transitions to true, a positive transition will occur in the summary bit reported to the
next higher level.
Suffix: .
<n> Window
Parameters:
<SumBit> Range: 0 to 65535
<ChannelName> String containing the name of the channel.
The parameter is optional. If you omit it, the command works for
the currently active channel.
For more information on the positive transition part see Chapter 14.1.7.2, "Structure of
a SCPI Status Register", on page 334.
STATus:OPERation:NTRansition <SumBit>
STATus:QUEStionable:NTRansition <SumBit>
STATus:QUEStionable:ACPLimit:NTRansition <SumBit>,<ChannelName>
STATus:QUEStionable:EXTended:NTRansition <SumBit>,<ChannelName>
STATus:QUEStionable:EXTended:INFO:NTRansition <SumBit>,<ChannelName>
STATus:QUEStionable:FREQuency:NTRansition <SumBit>,<ChannelName>
STATus:QUEStionable:LIMit<n>:NTRansition <SumBit>,<ChannelName>
STATus:QUEStionable:LMARgin<n>:NTRansition <SumBit>,<ChannelName>
STATus:QUEStionable:PNOise:NTRansition <SumBit>,<ChannelName>
STATus:QUEStionable:POWer:NTRansition <SumBit>,<ChannelName>
STATus:QUEStionable:POWer:DCPNoise:NTRansition <SumBit>,<ChannelName>
STATus:QUEStionable:TEMPerature:NTRansition <SumBit>,<ChannelName>
STATus:QUEStionable:TIME:NTRansition <SumBit>,<ChannelName>
These commands control the Negative TRansition part of a register.
Setting a bit causes a 1 to 0 transition in the corresponding bit of the associated regis-
ter. The transition also writes a 1 into the associated bit of the corresponding EVENt
register.
Suffix: .
<n> Window
Parameters:
<SumBit> Range: 0 to 65535
<ChannelName> String containing the name of the channel.
The parameter is optional. If you omit it, the command works for
the currently active channel.
For more information on the negative transition part see Chapter 14.1.7.2, "Structure of
a SCPI Status Register", on page 334.
STATus:OPERation:PTRansition <SumBit>
STATus:QUEStionable:PTRansition <SumBit>
STATus:QUEStionable:ACPLimit:PTRansition <SumBit>,<ChannelName>
STATus:QUEStionable:EXTended:PTRansition <SumBit>,<ChannelName>
STATus:QUEStionable:EXTended:INFO:PTRansition <SumBit>,<ChannelName>
STATus:QUEStionable:FREQuency:PTRansition <SumBit>,<ChannelName>
STATus:QUEStionable:LIMit<n>:PTRansition <SumBit>,<ChannelName>
STATus:QUEStionable:LMARgin<n>:PTRansition <SumBit>,<ChannelName>
STATus:QUEStionable:PNOise:PTRansition <SumBit>,<ChannelName>
STATus:QUEStionable:POWer:PTRansition <SumBit>,<ChannelName>
STATus:QUEStionable:POWer:DCPNoise:PTRansition <SumBit>,<ChannelName>
STATus:QUEStionable:TEMPerature:PTRansition <SumBit>,<ChannelName>
STATus:QUEStionable:TIME:PTRansition <SumBit>,<ChannelName>
These commands control the Positive TRansition part of a register.
Setting a bit causes a 0 to 1 transition in the corresponding bit of the associated regis-
ter. The transition also writes a 1 into the associated bit of the corresponding EVENt
register.
Suffix: .
<n> Window
Parameters:
<SumBit> Range: 0 to 65535
<ChannelName> String containing the name of the channel.
The parameter is optional. If you omit it, the command works for
the currently active channel.
Sub Main()
Console.WriteLine("Example of initialization _
of the SRQ in the case of errors.")
Dim SRQWaitTimeout = 4000 ' Timeout As Integer for WaitOnEvent
'Opening session
Try
'Analyzer is alias, instead of using resource string.
'------------------------------------------------
' Your command plase use here
' mbSession.Write("Your command")
'------------------------------------------------
Console.ReadKey()
End Sub
There are basically two methods of waiting for the arrival of a service request:
The method necessitates a waiting loop that checks the status of the SRQ line at regu-
lar intervals and returns control to the operating system during the time the expected
event has not yet occurred. In this way, the system can respond to user inputs (mouse
clicks, key entries) during the waiting time.
It is advisable to employ the Hold() auxiliary function, which returns control to the oper-
ating system for a selectable waiting time (see section Waiting Without Blocking the
Keyboard and Mouse), so enabling user inputs during the waiting time.
result% = 0
For i = 1 To 10 'Abort after max. 10 loop
'iterations
Status = viWaitOnEvent(analyzer, VI_EVENT_SERVICE_REQ, VI_TMO_IMMEDIATE, VI_NULL,
VI_NULL)
'Check event queue
If (status = VI_SUCCESS) Then
result% = 1
CALL Srq 'If SRQ is recognized =>
'subroutine for evaluation
Else
CALL Hold(20) 'Call hold function with
'20 ms 'waiting time. User inputs
'are possible.
Endif
Next i
If result% = 0 Then
Debug.Print "Timeout Error; Program aborted"'Output error message
STOP 'Stop software
Endif
A frequent problem with remote control programs using Visual Basic is to insert waiting
times without blocking the keyboard and the mouse.
If the program is to respond to user inputs also during a waiting time, control over the
program events during this time must be returned to the operating system. In Visual
Basic, this is done by calling the DoEvents function. This function causes keyboard-or
mouse-triggered events to be executed by the associated elements. For example, it
allows the operation of buttons and input fields while the user waits for an instrument
setting to be completed.
The following programming example describes the Hold() function, which returns
control to the operating system for the period of the waiting time selectable in millisec-
onds.
Rem ***********************************************************************
Rem The waiting function below expects the transfer of the desired
Rem waiting time in milliseconds. The keyboard and the mouse remain
Rem operative during the waiting period, thus allowing desired elements
Rem to be controlled
Rem ***********************************************************************
Reading out the status event registers, the output buffer and the error/event queue is
effected in subroutines.
Console.WriteLine(exp.Message)
End Try
End Sub
REM ------ Subroutine for evaluating the Event Status Register ------------
Public SUB Esrread()
Esr$ = SPACE$(20) 'Preallocate blanks to text
'variable
CALL InstrWrite (analyzer, "*ESR?") 'Read ESR
CALL InstrRead(analyzer, Esr$)
IF (VAL(Esr$) AND 1) > 0 THEN Debug.Print "Operation complete"
IF (VAL(Esr$) AND 2) > 0 THEN Debug.Print "Request Control"
IF (VAL(Esr$) AND 4) > 0
THEN Debug.Print "Query Error"
IF (VAL(Esr$) AND 8) > 0
THEN Debug.Print "Device dependent error"
IF (VAL(Esr$) AND 16) > 0
THEN Debug.Print "Execution Error; Program aborted"'Output error message
STOP 'Stop software
END IF
IF (VAL(Esr$) AND 32) > 0
THEN Debug.Print "Command Error; Program aborted"'Output error message
STOP 'Stop software
END IF
IF (VAL(Esr$) AND 64) > 0 THEN Debug.Print "User request"
IF (VAL(Esr$) AND 128) > 0 THEN Debug.Print "Power on"END SUB
REM **********************************************************************
REM ------ Subroutine for evaluating the Event Status Register ------------
Public Sub Esrread()
Try
Dim myESR As Short = mbSession.Query("*ESR?") 'Read ESR
If (myESR And 1) > 0 Then Console.WriteLine("Operation complete")
If (myESR And 2) > 0 Then Console.WriteLine("Request Control")
If (myESR And 4) > 0 Then Console.WriteLine("Query Error")
If (myESR And 8) > 0 Then Console.WriteLine("Device dependent error")
If (myESR And 16) > 0 Then
Console.WriteLine("Execution Error; Program aborted") 'Output error message
Stop 'Stop software
End If
If (myESR And 32) > 0 Then
Console.WriteLine("Command Error; Program aborted") 'Output error message
Stop 'Stop software
End If
If (myESR And 64) > 0 Then Console.WriteLine("User request")
If (myESR And 128) > 0 Then Console.WriteLine("Power on")
Catch exp As Exception
Console.WriteLine(exp.Message)
End Try
End Sub
16 Maintenance
The R&S FSWP does not require regular maintenance. Maintenance is essentially
restricted to cleaning the R&S FSWP. It is, however, recommended that you check the
nominal data from time to time.
The data sheet specifies the storage temperature range for the R&S FSWP. Protect the
instrument against dust if it is to be stored for a long period.
16.1 Cleaning
1. Clean the outside of the instrument using a soft, dry, lint-free dust cloth.
2. Check and clean the fans regularly to ensure that they always operate properly.
17 Troubleshooting
If the results do not meet your expectations, the following sections may contain helpful
hints and information.
● Error Information................................................................................................... 630
● Error Messages in Remote Control Mode.............................................................631
● Troubleshooting Remote Operation...................................................................... 632
● Miscellaneous Troubleshooting Hints................................................................... 634
● System Recovery.................................................................................................. 635
● Collecting Information for Support.........................................................................635
● Contacting Customer Support...............................................................................637
Depending on the type of message, the status message is indicated in varying colors.
Table 17-1: 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.
"INPUT OVLD" The signal level at the RF input connector exceeds the maximum.
The RF input is disconnected from the input mixer to protect the device. To re-enable
measurement, decrease the level at the RF input connector and reconnect the RF
input to the mixer input.
"LO UNL" Error in the instrument's frequency processing hardware was detected.
"NO REF" Instrument was set to an external reference but no signal was detected on the refer-
ence input.
"OVENCOLD" The optional OCXO reference frequency has not yet reached its operating tempera-
ture. The message usually disappears a few minutes after power has been switched
on.
"WRONG_FW" The firmware version is out-of-date and does not support the currently installed hard-
ware. Until the firmware version is updated, this error message is displayed and self-
alignment fails.
Example:
The command TEST:COMMAND generates the following answer to the query
SYSTem:ERRor?
-113,"Undefined header;TEST:COMMAND"
1060 Trigger-Block Gate Delay Error- gate length < Gate Delay
This message is displayed when the gate signal length is not sufficient for the pull-in delay
with a predefined gate delay.
Zeroing could not be per- Zeroing could not be performed because the RF power applied is too
formed high.
2. Send a "Device Clear" command from the control instrument to the R&S FSWP to
clear all currently active remote channels. Depending on the used interface and
protocol, send the following commands:
● Visa: viClear()
● GPIB: ibclr()
● RSIB: RSDLLibclr()
The remote channel currently processing the incompleted command is then ready
to receive further commands again.
3. On the remote channel performing the measurement, send the SCPI command
ABORt to abort the current measurement and reset the trigger system.
4. If the R&S FSWP still does not react to the remote commands, switch it off and
back on.
Ignored commands
When a remote command attempts to define incompatible settings, the command is
ignored and the instrument status remains unchanged, i.e. other settings are not auto-
matically adapted. Therefore, control programs should always define an initial instru-
ment status (e.g. using the *RST command) and then implement the required settings.
After the default image is restored, upgrade to the desired firmware version (see Chap-
ter 13.4.4, "Firmware Updates", on page 299).
2. Select "Service" > "R&S Support" and then "Create R&S Support Information" .
The file is stored as
C:\Program Files (x86)\Rohde-Schwarz\FSWP\<version>\user\
<inst_model>_<serial-no>_<date_and_time>.zip
The file is stored as
C:\Program Files (x86)\Rohde-Schwarz\FSWP\<version>\user\
FSWP_*.zip.
Collect the error information and attach it to an email in which you describe the prob-
lem. Send the email to the customer support address for your region as listed in Chap-
ter 17.7, "Contacting Customer Support", on page 637.
Contact information
Contact our customer support center at www.rohde-schwarz.com/support, or follow this
QR code:
List of commands
[SENSe:]ADJust:CONFigure:FREQuency:AUTosearch[:STATe]...................................................................449
[SENSe:]ADJust:CONFigure:FREQuency:COUNt........................................................................................ 449
[SENSe:]ADJust:CONFigure:FREQuency:LIMit:HIGH.................................................................................. 450
[SENSe:]ADJust:CONFigure:FREQuency:LIMit:LOW...................................................................................450
[SENSe:]ADJust:CONFigure:LEVel:THReshold............................................................................................ 448
[SENSe:]AVERage<n>:COUNt......................................................................................................................488
[SENSe:]BWIDth:MEASurement?................................................................................................................. 408
[SENSe:]BWIDth:VIDeo.................................................................................................................................488
[SENSe:]BWIDth:VIDeo:AUTO......................................................................................................................488
[SENSe:]CORRection:CVL:BAND................................................................................................................. 424
[SENSe:]CORRection:CVL:BIAS...................................................................................................................424
[SENSe:]CORRection:CVL:CATalog?............................................................................................................424
[SENSe:]CORRection:CVL:CLEar.................................................................................................................425
[SENSe:]CORRection:CVL:COMMent...........................................................................................................425
[SENSe:]CORRection:CVL:DATA..................................................................................................................425
[SENSe:]CORRection:CVL:HARMonic..........................................................................................................426
[SENSe:]CORRection:CVL:MIXer................................................................................................................. 426
[SENSe:]CORRection:CVL:PORTs................................................................................................................426
[SENSe:]CORRection:CVL:SELect............................................................................................................... 427
[SENSe:]CORRection:CVL:SNUMber........................................................................................................... 427
[SENSe:]CORRection:WEIGhting:COMMent................................................................................................ 464
[SENSe:]CORRection:WEIGhting:DATA....................................................................................................... 464
[SENSe:]CORRection:WEIGhting:DELete.....................................................................................................464
[SENSe:]CORRection:WEIGhting:NAME...................................................................................................... 465
[SENSe:]CORRection:WEIGhting:SELect..................................................................................................... 465
[SENSe:]FILTer:LPASs:FREQuency:MANual................................................................................................ 451
[SENSe:]FILTer:LPASs[:STATe]..................................................................................................................... 451
[SENSe:]FREQuency:CENTer....................................................................................................................... 452
[SENSe:]FREQuency:CENTer:STEP.............................................................................................................485
[SENSe:]FREQuency:CENTer:STEP:LINK....................................................................................................486
[SENSe:]FREQuency:CENTer:STEP:LINK:FACTor.......................................................................................486
[SENSe:]FREQuency:SPAN.......................................................................................................................... 487
[SENSe:]FREQuency:STARt......................................................................................................................... 452
[SENSe:]FREQuency:STOP..........................................................................................................................453
[SENSe:]LIST:BWIDth[:RESolution]:RATio.................................................................................................... 455
[SENSe:]LIST:BWIDth[:RESolution]:USMall.................................................................................................. 458
[SENSe:]LIST:RANGe<r>:BWIDth[:RESolution]............................................................................................456
[SENSe:]LIST:RANGe<r>:FREQuency:STARt?............................................................................................ 456
[SENSe:]LIST:RANGe<r>:FREQuency:STOP?.............................................................................................457
[SENSe:]LIST:RANGe<r>:XCOunt................................................................................................................ 457
[SENSe:]MIXer<x>:BIAS:HIGH..................................................................................................................... 422
[SENSe:]MIXer<x>:BIAS[:LOW].................................................................................................................... 422
[SENSe:]MIXer<x>:FREQuency:HANDover..................................................................................................416
[SENSe:]MIXer<x>:FREQuency:STARt.........................................................................................................416
[SENSe:]MIXer<x>:FREQuency:STOP......................................................................................................... 417
[SENSe:]MIXer<x>:HARMonic:BAND........................................................................................................... 417
[SENSe:]MIXer<x>:HARMonic:BAND:PRESet..............................................................................................418
[SENSe:]MIXer<x>:HARMonic:HIGH:STATe................................................................................................. 418
[SENSe:]MIXer<x>:HARMonic:HIGH[:VALue]...............................................................................................418
[SENSe:]MIXer<x>:HARMonic:TYPE............................................................................................................ 419
[SENSe:]MIXer<x>:HARMonic[:LOW]........................................................................................................... 419
[SENSe:]MIXer<x>:LOPower.........................................................................................................................423
[SENSe:]MIXer<x>:LOSS:HIGH.................................................................................................................... 419
[SENSe:]MIXer<x>:LOSS:TABLe:HIGH........................................................................................................ 420
[SENSe:]MIXer<x>:LOSS:TABLe[:LOW]....................................................................................................... 420
[SENSe:]MIXer<x>:LOSS[:LOW]...................................................................................................................420
[SENSe:]MIXer<x>:PORTs............................................................................................................................ 421
[SENSe:]MIXer<x>:RFOVerrange[:STATe].................................................................................................... 421
[SENSe:]MIXer<x>:XCORr............................................................................................................................ 421
[SENSe:]MIXer<x>[:STATe]........................................................................................................................... 423
[SENSe:]POWer:RLEVel:MODE....................................................................................................................454
[SENSe:]POWer:RLEVel:OFFSet..................................................................................................................448
[SENSe:]POWer:RLEVel?............................................................................................................................. 448
[SENSe:]ROSCillator:COUPling:BANDwidth.................................................................................................581
[SENSe:]ROSCillator:COUPling:BANDwidth:MODE..................................................................................... 581
[SENSe:]ROSCillator:COUPling:MODE........................................................................................................ 582
[SENSe:]ROSCillator:LBWidth.......................................................................................................................582
[SENSe:]ROSCillator:O640........................................................................................................................... 582
[SENSe:]ROSCillator:OSYNc........................................................................................................................ 583
[SENSe:]ROSCillator:SOURce...................................................................................................................... 584
[SENSe:]ROSCillator:SOURce:EAUTo?........................................................................................................584
[SENSe:]ROSCillator:TRANge...................................................................................................................... 585
[SENSe:]SMOothing:APERture..................................................................................................................... 482
[SENSe:]SMOothing[:STATe].........................................................................................................................483
[SENSe:]SPURs:COLor.................................................................................................................................473
[SENSe:]SPURs:FILTer:CLEar...................................................................................................................... 473
[SENSe:]SPURs:FILTer:HARMonics............................................................................................................. 472
[SENSe:]SPURs:FILTer:LOAD.......................................................................................................................473
[SENSe:]SPURs:FILTer:MODE......................................................................................................................471
[SENSe:]SPURs:FILTer:NAME?.................................................................................................................... 472
[SENSe:]SPURs:FILTer:OFFSet....................................................................................................................472
[SENSe:]SPURs:FILTer:RANGe.................................................................................................................... 472
[SENSe:]SPURs:FILTer:SAVE....................................................................................................................... 473
[SENSe:]SPURs:SORT................................................................................................................................. 471
[SENSe:]SPURs:SUPPress...........................................................................................................................483
[SENSe:]SPURs:THReshold......................................................................................................................... 483
[SENSe:]SPURs:WEIGhting.......................................................................................................................... 471
[SENSe:]SWEep:CAPTure:RANGe...............................................................................................................454
[SENSe:]SWEep:COUNt............................................................................................................................... 458
[SENSe:]SWEep:EGATe:HOLDoff.................................................................................................................474
[SENSe:]SWEep:EGATe:LENGth.................................................................................................................. 474
[SENSe:]SWEep:EGATe:LEVel..................................................................................................................... 475
[SENSe:]SWEep:EGATe:TYPE..................................................................................................................... 475
[SENSe:]SWEep:FORWard........................................................................................................................... 458
[SENSe:]SWEep:FSEGment......................................................................................................................... 459
[SENSe:]SWEep:MODE................................................................................................................................ 459
[SENSe:]SWEep:PULSe:DETection.............................................................................................................. 475
[SENSe:]SWEep:PULSe:GATE..................................................................................................................... 476
[SENSe:]SWEep:PULSe:PRI.........................................................................................................................476
[SENSe:]SWEep:TIME.................................................................................................................................. 459
[SENSe:]SWEep:XFACtor............................................................................................................................. 460
[SENSe:]SWEep:XOPTimize:THReshold......................................................................................................460
[SENSe:]SWEep:XOPTimize[:STATe]............................................................................................................460
[SENSe:]TIME:STARt.................................................................................................................................... 461
[SENSe:]TIME:STOP.....................................................................................................................................461
*CAL?.............................................................................................................................................................385
*CLS...............................................................................................................................................................385
*ESE.............................................................................................................................................................. 385
*ESR?............................................................................................................................................................ 385
*IDN?............................................................................................................................................................. 386
*IST?..............................................................................................................................................................386
*OPC..............................................................................................................................................................386
*OPT?............................................................................................................................................................ 386
*PCB.............................................................................................................................................................. 386
*PRE.............................................................................................................................................................. 387
*PSC.............................................................................................................................................................. 387
*RST.............................................................................................................................................................. 387
*SRE.............................................................................................................................................................. 387
*STB?.............................................................................................................................................................388
*TRG..............................................................................................................................................................388
*TST?.............................................................................................................................................................388
*WAI...............................................................................................................................................................388
ABORt............................................................................................................................................................399
CALCulate<n>:DELTamarker<m>:AOFF.......................................................................................................525
CALCulate<n>:DELTamarker<m>:LINK........................................................................................................ 525
CALCulate<n>:DELTamarker<m>:MAXimum:LEFT...................................................................................... 532
CALCulate<n>:DELTamarker<m>:MAXimum:NEXT..................................................................................... 533
CALCulate<n>:DELTamarker<m>:MAXimum:RIGHt.....................................................................................533
CALCulate<n>:DELTamarker<m>:MAXimum[:PEAK]................................................................................... 533
CALCulate<n>:DELTamarker<m>:MINimum:LEFT....................................................................................... 533
CALCulate<n>:DELTamarker<m>:MINimum:NEXT...................................................................................... 534
CALCulate<n>:DELTamarker<m>:MINimum:RIGHt...................................................................................... 534
CALCulate<n>:DELTamarker<m>:MINimum[:PEAK].................................................................................... 534
CALCulate<n>:DELTamarker<m>:MODE......................................................................................................526
CALCulate<n>:DELTamarker<m>:MREFerence........................................................................................... 526
CALCulate<n>:DELTamarker<m>:TRACe.....................................................................................................527
CALCulate<n>:DELTamarker<m>:X.............................................................................................................. 527
CALCulate<n>:DELTamarker<m>:X:RELative?............................................................................................ 536
CALCulate<n>:DELTamarker<m>:Y?............................................................................................................ 537
CALCulate<n>:DELTamarker<m>[:STATe].................................................................................................... 526
CALCulate<n>:DELTamarker<ms>:LINK:TO:MARKer<md>.........................................................................525
CALCulate<n>:FREQuency:DEViation:DIAGram..........................................................................................497
CALCulate<n>:FREQuency:DEViation:REGRession:POINts?..................................................................... 499
CALCulate<n>:FREQuency:DEViation:REGRession?.................................................................................. 498
CALCulate<n>:FREQuency:DEViation:SLOPe?........................................................................................... 499
CALCulate<n>:FREQuency:DEViation:STARt.............................................................................................. 498
CALCulate<n>:FREQuency:DEViation:STATe...............................................................................................497
CALCulate<n>:FREQuency:DEViation:STOP............................................................................................... 498
CALCulate<n>:FREQuency:DEViation:TRACe............................................................................................. 498
CALCulate<n>:LIMit<k>:COMPatible?.......................................................................................................... 538
CALCulate<n>:LIMit<li>:ACTive?.................................................................................................................. 538
CALCulate<n>:LIMit<li>:CLEar[:IMMediate]..................................................................................................548
CALCulate<n>:LIMit<li>:COMMent............................................................................................................... 542
CALCulate<n>:LIMit<li>:CONTrol:DOMain................................................................................................... 543
CALCulate<n>:LIMit<li>:CONTrol:MODE......................................................................................................543
CALCulate<n>:LIMit<li>:CONTrol:SHIFt....................................................................................................... 543
CALCulate<n>:LIMit<li>:CONTrol:SPACing.................................................................................................. 544
CALCulate<n>:LIMit<li>:CONTrol[:DATA]......................................................................................................542
CALCulate<n>:LIMit<li>:COPY......................................................................................................................538
CALCulate<n>:LIMit<li>:DELete....................................................................................................................539
CALCulate<n>:LIMit<li>:FAIL?...................................................................................................................... 548
CALCulate<n>:LIMit<li>:LOWer:MODE.........................................................................................................544
CALCulate<n>:LIMit<li>:LOWer:OFFSet.......................................................................................................539
CALCulate<n>:LIMit<li>:LOWer:SHIFt.......................................................................................................... 545
CALCulate<n>:LIMit<li>:LOWer:SPACing..................................................................................................... 545
CALCulate<n>:LIMit<li>:LOWer:STATe......................................................................................................... 539
CALCulate<n>:LIMit<li>:LOWer[:DATA]........................................................................................................ 544
CALCulate<n>:LIMit<li>:NAME..................................................................................................................... 546
CALCulate<n>:LIMit<li>:STATe..................................................................................................................... 540
CALCulate<n>:LIMit<li>:TRACe<t>...............................................................................................................540
CALCulate<n>:LIMit<li>:TRACe<t>:CHECk..................................................................................................541
CALCulate<n>:LIMit<li>:UNIT....................................................................................................................... 546
CALCulate<n>:LIMit<li>:UPPer:MODE......................................................................................................... 547
CALCulate<n>:LIMit<li>:UPPer:SHIFt........................................................................................................... 547
CALCulate<n>:LIMit<li>:UPPer:SPACing......................................................................................................547
CALCulate<n>:LIMit<li>:UPPer:STATe..........................................................................................................541
CALCulate<n>:LIMit<li>:UPPer[:DATA]......................................................................................................... 546
CALCulate<n>:MARKer<m>:AOFF............................................................................................................... 528
CALCulate<n>:MARKer<m>:FUNCtion:SPTRacking:RANGe...................................................................... 531
CALCulate<n>:MARKer<m>:FUNCtion:SPTRacking[:STATe]...................................................................... 532
CALCulate<n>:MARKer<m>:LINK.................................................................................................................530
CALCulate<n>:MARKer<m>:MAXimum:LEFT.............................................................................................. 534
CALCulate<n>:MARKer<m>:MAXimum:NEXT............................................................................................. 534
CALCulate<n>:MARKer<m>:MAXimum:RIGHt............................................................................................. 535
CALCulate<n>:MARKer<m>:MAXimum[:PEAK]........................................................................................... 535
CALCulate<n>:MARKer<m>:MINimum:LEFT............................................................................................... 535
CALCulate<n>:MARKer<m>:MINimum:NEXT...............................................................................................535
CALCulate<n>:MARKer<m>:MINimum:RIGHt.............................................................................................. 536
CALCulate<n>:MARKer<m>:MINimum[:PEAK].............................................................................................536
CALCulate<n>:MARKer<m>:PEXCursion.....................................................................................................531
CALCulate<n>:MARKer<m>:TRACe.............................................................................................................529
CALCulate<n>:MARKer<m>:X...................................................................................................................... 529
CALCulate<n>:MARKer<m>:Y?.................................................................................................................... 537
CALCulate<n>:MARKer<m>[:STATe]............................................................................................................ 528
CALCulate<n>:MARKer<ms>:LINK:TO:MARKer<md>................................................................................. 528
CALCulate<n>:MATH:STATe......................................................................................................................... 522
CALCulate<n>:MATH[:EXPRession][:DEFine].............................................................................................. 523
CALCulate<n>:SETTling:TIME:DIAGram...................................................................................................... 496
CALCulate<n>:SETTling:TIME:FREQuency:LIMit:LOWer............................................................................ 496
CALCulate<n>:SETTling:TIME:FREQuency:LIMit:UPPer............................................................................. 497
CALCulate<n>:SETTling:TIME:RESult?........................................................................................................497
CALCulate<n>:SETTling:TIME:STATe...........................................................................................................496
CALCulate<n>:SETTling:TIME:TRACe......................................................................................................... 496
CALCulate<n>:SNOise<s>:AOFF................................................................................................................. 466
CALCulate<n>:SNOise<s>:STATe.................................................................................................................466
CALCulate<n>:SNOise<s>:X.........................................................................................................................466
CALCulate<n>:SNOise<s>[:TRACe<t>]:DECades:X?.................................................................................. 467
CALCulate<n>:SNOise<s>[:TRACe<t>]:DECades:Y?.................................................................................. 467
CALCulate<n>:SNOise<s>[:TRACe<t>]:DECades[:STATe].......................................................................... 468
CALCulate<n>:SNOise<s>[:TRACe<t>]:USERdefined[:STATe]....................................................................468
CALCulate<n>:SNOise<s>[:TRACe<t>]:Y?...................................................................................................468
CALCulate<n>[:RANGe<j>]:EVALuation:STARt............................................................................................462
CALCulate<n>[:RANGe<j>]:EVALuation:STOP............................................................................................ 462
CALCulate<n>[:RANGe<j>]:EVALuation:TRACe.......................................................................................... 463
CALCulate<n>[:RANGe<j>]:EVALuation:WEIGhting.....................................................................................464
CALCulate<n>[:RANGe<j>]:EVALuation[:STATe].......................................................................................... 463
CALibration:RESult?......................................................................................................................................586
CALibration[:ALL]?.........................................................................................................................................586
CONFigure:PNOise:MEASurement............................................................................................................... 397
CONFigure:SNTune:MEASurement[:STATe]................................................................................................. 398
CONFigure:SNTune:SWEep:DELay:INITial.................................................................................................. 480
CONFigure:SNTune:SWEep:DELay[:POINt].................................................................................................480
CONFigure:SNTune:SWEep:POINts.............................................................................................................480
CONFigure:SNTune:SWEep:SOURce.......................................................................................................... 481
CONFigure:SNTune:SWEep:STARt.............................................................................................................. 481
CONFigure:SNTune:SWEep:STOP...............................................................................................................481
CONFigure:TRANsient:MEASurement[:STATe].............................................................................................398
CONFigure:TRANsient:MODE.......................................................................................................................485
CONFigure:TRANsient[:WINDow<n>]:AF:COUPling.................................................................................... 492
CONFigure:TRANsient[:WINDow<n>]:AF:COUPling:RPOint:MODE............................................................ 492
CONFigure:TRANsient[:WINDow<n>]:AF:COUPling:RPOint[:X].................................................................. 493
CONFigure:VCO:FIX:SOURce...................................................................................................................... 477
CONFigure:VCO:MEASurement[:STATe]...................................................................................................... 399
CONFigure:VCO:SWEep:DELay:INITial........................................................................................................477
CONFigure:VCO:SWEep:DELay[:POINt]...................................................................................................... 478
CONFigure:VCO:SWEep:FCOunter:RESolution........................................................................................... 478
CONFigure:VCO:SWEep:POINts.................................................................................................................. 478
CONFigure:VCO:SWEep:SOURce................................................................................................................479
CONFigure:VCO:SWEep:STARt................................................................................................................... 479
CONFigure:VCO:SWEep:STOP.................................................................................................................... 479
DIAGnostic:INFO:CCOunt?........................................................................................................................... 601
DIAGnostic:SERVice:BIOSinfo?.................................................................................................................... 601
DIAGnostic:SERVice:HWINfo?......................................................................................................................602
DIAGnostic:SERVice:INPut:MC[:DISTance].................................................................................................. 587
DIAGnostic:SERVice:INPut:PULSed:CFRequency....................................................................................... 587
DIAGnostic:SERVice:INPut:RF[:SPECtrum]..................................................................................................587
DIAGnostic:SERVice:INPut:SYNThtwo[:FREQuency]...................................................................................588
DIAGnostic:SERVice:INPut[:SELect].............................................................................................................587
DIAGnostic:SERVice:NSOurce......................................................................................................................441
DIAGnostic:SERVice:SFUNction................................................................................................................... 606
DIAGnostic:SERVice:SFUNction:LASTresult?.............................................................................................. 607
DIAGnostic:SERVice:SFUNction:RESults:DELete........................................................................................ 607
DIAGnostic:SERVice:SFUNction:RESults:SAVE...........................................................................................607
DIAGnostic:SERVice:SINFo?........................................................................................................................ 607
DIAGnostic:SERVice:STESt:RESult?............................................................................................................588
DIAGnostic:SERVice:VERSinfo?...................................................................................................................602
DISPlay:ANNotation:CBAR............................................................................................................................589
DISPlay:ANNotation:FREQuency.................................................................................................................. 590
DISPlay:ATAB................................................................................................................................................ 389
DISPlay:CMAP<it>:DEFault<ci>....................................................................................................................592
DISPlay:CMAP<it>:HSL.................................................................................................................................593
DISPlay:CMAP<it>:PDEFined....................................................................................................................... 593
DISPlay:FORMat........................................................................................................................................... 500
DISPlay:LOGO...............................................................................................................................................565
DISPlay:SBAR[:STATe]..................................................................................................................................590
DISPlay:SKEYs[:STATe]................................................................................................................................ 590
DISPlay:SNINfo:TRACe.................................................................................................................................469
DISPlay:SNINfo[:STATe]................................................................................................................................ 469
DISPlay:TBAR[:STATe].................................................................................................................................. 590
DISPlay:THEMe:CATalog?............................................................................................................................ 593
DISPlay:THEMe:SELect................................................................................................................................ 594
DISPlay:TOUChscreen[:STATe].....................................................................................................................590
DISPlay:WSELect?........................................................................................................................................500
DISPlay:XGINdicator[:STATe]........................................................................................................................ 455
DISPlay[:WINDow<n>]:MTABle..................................................................................................................... 530
DISPlay[:WINDow<n>]:SIZE..........................................................................................................................501
DISPlay[:WINDow<n>]:TIME......................................................................................................................... 591
DISPlay[:WINDow<n>]:TIME:FORMat.......................................................................................................... 591
DISPlay[:WINDow<n>]:TRACe<t>:LABel:TEXT............................................................................................514
DISPlay[:WINDow<n>]:TRACe<t>:LABel[:STATe].........................................................................................513
DISPlay[:WINDow<n>]:TRACe<t>:MODE.....................................................................................................512
DISPlay[:WINDow<n>]:TRACe<t>:PERSistence:DECay.............................................................................. 514
DISPlay[:WINDow<n>]:TRACe<t>:PERSistence[:STATe]............................................................................. 515
DISPlay[:WINDow<n>]:TRACe<t>:RESult[:TYPE]........................................................................................ 515
DISPlay[:WINDow<n>]:TRACe<t>:SMOothing:APERture.............................................................................517
DISPlay[:WINDow<n>]:TRACe<t>:SMOothing[:STATe]................................................................................ 517
DISPlay[:WINDow<n>]:TRACe<t>:SPURs:SUPPress.................................................................................. 470
DISPlay[:WINDow<n>]:TRACe<t>:SPURs:THReshold.................................................................................470
DISPlay[:WINDow<n>]:TRACe<t>:X:SPACing?............................................................................................444
DISPlay[:WINDow<n>]:TRACe<t>:X[:SCALe]...............................................................................................443
DISPlay[:WINDow<n>]:TRACe<t>:X[:SCALe]:AUTO....................................................................................444
DISPlay[:WINDow<n>]:TRACe<t>:Y:UNIT.................................................................................................... 446
DISPlay[:WINDow<n>]:TRACe<t>:Y[:SCALe]...............................................................................................445
DISPlay[:WINDow<n>]:TRACe<t>:Y[:SCALe]:AUTO....................................................................................445
DISPlay[:WINDow<n>]:TRACe<t>:Y[:SCALe]:MODE................................................................................... 493
DISPlay[:WINDow<n>]:TRACe<t>:Y[:SCALe]:PDIVision.............................................................................. 494
DISPlay[:WINDow<n>]:TRACe<t>:Y[:SCALe]:RLEVel..................................................................................446
DISPlay[:WINDow<n>]:TRACe<t>:Y[:SCALe]:RLEVel:LOWer..................................................................... 446
DISPlay[:WINDow<n>]:TRACe<t>:Y[:SCALe]:RLEVel:OFFSet.................................................................... 516
DISPlay[:WINDow<n>]:TRACe<t>:Y[:SCALe]:RLEVel:OFFSet:STATe.........................................................516
DISPlay[:WINDow<n>]:TRACe<t>:Y[:SCALe]:RPOSition............................................................................. 494
DISPlay[:WINDow<n>]:TRACe<t>:Y[:SCALe]:RVALue.................................................................................495
DISPlay[:WINDow<n>]:TRACe<t>:Y[:SCALe]:UNIT..................................................................................... 495
DISPlay[:WINDow<n>][:SUBWindow<w>]:SELect........................................................................................ 501
DISPlay[:WINDow<n>][:SUBWindow<w>]:TRACe<t>[:STATe]..................................................................... 515
DISPlay[:WINDow<n>][:SUBWindow<w>]:ZOOM:AREA.............................................................................. 509
DISPlay[:WINDow<n>][:SUBWindow<w>]:ZOOM:MULTiple<zn>:AREA...................................................... 510
DISPlay[:WINDow<n>][:SUBWindow<w>]:ZOOM:MULTiple<zn>[:STATe]....................................................511
DISPlay[:WINDow<n>][:SUBWindow<w>]:ZOOM[:STATe]............................................................................511
FETCh<n>:PNOise<t>:SPURs:COUNt?....................................................................................................... 403
FETCh<n>:PNOise<t>:SPURs:DISCrete?.................................................................................................... 404
FETCh<n>:PNOise<t>:SPURs:JITTer?......................................................................................................... 404
FETCh<n>:PNOise<t>:SPURs:RANDom?....................................................................................................404
FETCh<n>:PNOise<t>:SPURs?.................................................................................................................... 403
FETCh<n>[:RANGe<j>]:PNOise<t>:DUT:GAIN?...........................................................................................402
FETCh<n>[:RANGe<j>]:PNOise<t>:IPN?..................................................................................................... 405
FETCh<n>[:RANGe<j>]:PNOise<t>:RAM?................................................................................................... 405
FETCh<n>[:RANGe<j>]:PNOise<t>:RFM?....................................................................................................406
FETCh<n>[:RANGe<j>]:PNOise<t>:RMS?................................................................................................... 406
FETCh<n>[:RANGe<j>]:PNOise<t>:RPM?................................................................................................... 407
FORMat:DEXPort:CSEParator...................................................................................................................... 519
FORMat:DEXPort:DSEParator...................................................................................................................... 520
FORMat:DEXPort:FORMat............................................................................................................................520
FORMat:DEXPort:HEADer............................................................................................................................ 520
FORMat:DEXPort:TRACes............................................................................................................................521
FORMat[:DATA]............................................................................................................................................. 519
HCOPy:ABORt...............................................................................................................................................566
HCOPy:CMAP<it>:DEFault<ci>.....................................................................................................................566
HCOPy:CMAP<it>:HSL................................................................................................................................. 566
HCOPy:CMAP<it>:PDEFined........................................................................................................................ 567
HCOPy:CONTent...........................................................................................................................................567
HCOPy:DESTination<1|2>.............................................................................................................................568
HCOPy:DEVice:COLor.................................................................................................................................. 569
HCOPy:DEVice:LANGuage<1|2>..................................................................................................................569
HCOPy:ITEM:WINDow<1|2>:TEXT...............................................................................................................570
HCOPy:PAGE:COUNt:STATe........................................................................................................................ 570
HCOPy:PAGE:MARGin<1|2>:BOTTom......................................................................................................... 571
HCOPy:PAGE:MARGin<1|2>:LEFT.............................................................................................................. 571
HCOPy:PAGE:MARGin<1|2>:RIGHt............................................................................................................. 571
HCOPy:PAGE:MARGin<1|2>:TOP................................................................................................................ 572
HCOPy:PAGE:MARGin<1|2>:UNIT...............................................................................................................572
HCOPy:PAGE:ORIentation<1|2>...................................................................................................................572
HCOPy:PAGE:WINDow<1|2>:CHANnel:STATe............................................................................................ 573
HCOPy:PAGE:WINDow<1|2>:COUNt........................................................................................................... 573
HCOPy:PAGE:WINDow<1|2>:SCALe........................................................................................................... 573
HCOPy:PAGE:WINDow<1|2>:STATe............................................................................................................ 574
HCOPy:TDSTamp:STATe<1|2>..................................................................................................................... 575
HCOPy[:IMMediate<1|2>]..............................................................................................................................570
HCOPy[:IMMediate<1|2>]:NEXT................................................................................................................... 570
INITiate:SEQuencer:ABORt...........................................................................................................................393
INITiate:SEQuencer:IMMediate..................................................................................................................... 393
INITiate:SEQuencer:MODE........................................................................................................................... 394
INITiate<n>:CONMeas.................................................................................................................................. 400
INITiate<n>:CONTinuous...............................................................................................................................401
INITiate<n>[:IMMediate]................................................................................................................................ 402
INPut<1|2>:ATTenuation................................................................................................................................447
INPut<1|2>:ATTenuation:AUTO.....................................................................................................................447
INPut<1|2>:CONNector................................................................................................................................. 415
INPut<1|2>:LOSCillator:SOURce.................................................................................................................. 414
INPut<1|2>:LOSCillator:SOURce:EXTernal:LEVel........................................................................................ 414
INPut<1|2>:RLEVel........................................................................................................................................487
INPut<ip>:COUPling......................................................................................................................................413
INPut<ip>:SELect.......................................................................................................................................... 414
INPut<ip>:UPORt:STATe............................................................................................................................... 441
INPut<ip>:UPORt[:VALue]............................................................................................................................. 442
INSTrument:CREate:DUPLicate....................................................................................................................389
INSTrument:CREate:REPLace......................................................................................................................390
INSTrument:CREate[:NEW]...........................................................................................................................389
INSTrument:DELete.......................................................................................................................................390
INSTrument:LIST?......................................................................................................................................... 391
INSTrument:REName.................................................................................................................................... 392
INSTrument[:SELect]..................................................................................................................................... 392
LAYout:ADD[:WINDow]?................................................................................................................................501
LAYout:CATalog[:WINDow]?.......................................................................................................................... 503
LAYout:IDENtify[:WINDow]?.......................................................................................................................... 503
LAYout:MOVE[:WINDow]...............................................................................................................................504
LAYout:REMove[:WINDow]............................................................................................................................504
LAYout:REPLace[:WINDow].......................................................................................................................... 505
LAYout:SPLitter..............................................................................................................................................505
LAYout:WINDow<n>:ADD?............................................................................................................................507
LAYout:WINDow<n>:IDENtify?...................................................................................................................... 507
LAYout:WINDow<n>:REMove........................................................................................................................508
LAYout:WINDow<n>:REPLace...................................................................................................................... 508
MMEMory:CATalog........................................................................................................................................ 553
MMEMory:CATalog:LONG............................................................................................................................. 554
MMEMory:CDIRectory................................................................................................................................... 554
MMEMory:CLEar:ALL....................................................................................................................................561
MMEMory:CLEar:STATe................................................................................................................................ 562
MMEMory:COMMent..................................................................................................................................... 554
MMEMory:COPY........................................................................................................................................... 554
MMEMory:DATA............................................................................................................................................ 555
MMEMory:DELete:IMMediate........................................................................................................................555
MMEMory:LOAD:AUTO.................................................................................................................................562
MMEMory:LOAD:STATe................................................................................................................................ 562
MMEMory:LOAD<n>:TRACe.........................................................................................................................521
MMEMory:MDIRectory...................................................................................................................................556
MMEMory:MOVE........................................................................................................................................... 556
MMEMory:MSIS.............................................................................................................................................556
MMEMory:NAME........................................................................................................................................... 556
MMEMory:NETWork:DISConnect..................................................................................................................556
MMEMory:NETWork:MAP............................................................................................................................. 557
MMEMory:NETWork:UNUSeddrives?........................................................................................................... 557
MMEMory:NETWork:USEDdrives................................................................................................................. 558
MMEMory:RDIRectory................................................................................................................................... 558
MMEMory:SELect:CHANnel[:ITEM]:ALL....................................................................................................... 559
MMEMory:SELect:CHANnel[:ITEM]:DEFault................................................................................................ 559
MMEMory:SELect:CHANnel[:ITEM]:HWSettings.......................................................................................... 559
MMEMory:SELect:CHANnel[:ITEM]:LINes:ALL.............................................................................................560
MMEMory:SELect:CHANnel[:ITEM]:NONE................................................................................................... 560
MMEMory:SELect:CHANnel[:ITEM]:SGRam.................................................................................................560
MMEMory:SELect:CHANnel[:ITEM]:TRACe[:ACTive]...................................................................................560
MMEMory:SELect:CHANnel[:ITEM]:TRANsducer:ALL................................................................................. 561
MMEMory:SELect:CHANnel[:ITEM]:WEIGhting............................................................................................ 561
MMEMory:SELect[:ITEM]:ALL....................................................................................................................... 559
MMEMory:SELect[:ITEM]:DEFault................................................................................................................ 559
MMEMory:SELect[:ITEM]:HWSettings.......................................................................................................... 559
MMEMory:SELect[:ITEM]:LINes:ALL.............................................................................................................560
MMEMory:SELect[:ITEM]:NONE................................................................................................................... 560
MMEMory:SELect[:ITEM]:SGRam.................................................................................................................560
MMEMory:SELect[:ITEM]:TRACe<1...3>[:ACTive]........................................................................................560
MMEMory:SELect[:ITEM]:TRANsducer:ALL................................................................................................. 561
MMEMory:SELect[:ITEM]:WEIGhting............................................................................................................ 561
MMEMory:STORe<1|2>:STATe..................................................................................................................... 563
MMEMory:STORe<1|2>:STATe:NEXT...........................................................................................................563
MMEMory:STORe<1|2>:TYPE...................................................................................................................... 564
MMEMory:STORe<n>:SPURs.......................................................................................................................407
MMEMory:STORe<n>:TRACe.......................................................................................................................576
OUTPut<up>:UPORt:STATe.......................................................................................................................... 442
OUTPut<up>:UPORt[:VALue]........................................................................................................................442
SOURce:CURRent:AUX:LIMit:HIGH?........................................................................................................... 428
SOURce:CURRent:CONTrol<i>:LIMit:HIGH?............................................................................................... 428
SOURce:CURRent:POWer<i>:LIMit:HIGH....................................................................................................429
SOURce:CURRent:SEQuence:RESult?........................................................................................................429
SOURce:GENerator:CHANnel:COUPling......................................................................................................437
SOURce:GENerator:DUTBypass.................................................................................................................. 437
SOURce:GENerator:FREQuency.................................................................................................................. 438
SOURce:GENerator:FREQuency:STEP........................................................................................................438
SOURce:GENerator:LEVel............................................................................................................................ 438
SOURce:GENerator:MODulation...................................................................................................................439
SOURce:GENerator:PULSe:PERiod............................................................................................................. 439
SOURce:GENerator:PULSe:TRIGger:OUTPut............................................................................................. 439
SOURce:GENerator:PULSe:WIDTh.............................................................................................................. 440
SOURce:GENerator[:STATe]......................................................................................................................... 440
SOURce:POWer:SEQuence:RESult?........................................................................................................... 430
SOURce:VOLTage:AUX:LEVel:AMPLitude....................................................................................................430
SOURce:VOLTage:AUX:LEVel:LIMit:HIGH................................................................................................... 430
SOURce:VOLTage:AUX:LEVel:LIMit:LOW.................................................................................................... 430
SOURce:VOLTage:AUX:LEVel[:STATe]......................................................................................................... 431
SOURce:VOLTage:CHANnel:COUPling........................................................................................................ 431
SOURce:VOLTage:CONTrol<i>:LEVel:AMPLitude........................................................................................ 432
SOURce:VOLTage:CONTrol<i>:LEVel:LIMit:HIGH........................................................................................432
SOURce:VOLTage:CONTrol<i>:LEVel:LIMit:LOW.........................................................................................432
SOURce:VOLTage:CONTrol<i>:LEVel[:STATe]............................................................................................. 433
SOURce:VOLTage:POWer<i>:LEVel:AMPLitude.......................................................................................... 433
SOURce:VOLTage:POWer<i>:LEVel:LIMit:HIGH.......................................................................................... 434
SOURce:VOLTage:POWer<i>:LEVel:LIMit:LOW...........................................................................................434
SOURce:VOLTage:POWer<i>:LEVel:MODE................................................................................................. 435
SOURce:VOLTage:POWer<i>:LEVel[:STATe]................................................................................................435
SOURce:VOLTage:POWer<i>:LIMit:HIGH.................................................................................................... 435
SOURce:VOLTage:SEQuence:RESult?........................................................................................................ 436
SOURce:VOLTage[:STATe]............................................................................................................................436
SOURce<si>:EXTernal<ext>:ROSCillator:EXTernal:FREQuency................................................................. 583
SOURce<si>:TEMPerature:FRONtend......................................................................................................... 588
STATus:OPERation:CONDition?................................................................................................................... 615
STATus:OPERation:ENABle.......................................................................................................................... 616
STATus:OPERation:NTRansition...................................................................................................................617
STATus:OPERation:PTRansition................................................................................................................... 618
STATus:OPERation[:EVENt]?........................................................................................................................616
STATus:PRESet.............................................................................................................................................615
STATus:QUEStionable:ACPLimit:CONDition?...............................................................................................615
STATus:QUEStionable:ACPLimit:ENABle..................................................................................................... 616
STATus:QUEStionable:ACPLimit:NTRansition.............................................................................................. 617
STATus:QUEStionable:ACPLimit:PTRansition.............................................................................................. 618
STATus:QUEStionable:ACPLimit[:EVENt]?................................................................................................... 616
STATus:QUEStionable:CONDition?...............................................................................................................615
STATus:QUEStionable:ENABle..................................................................................................................... 616
STATus:QUEStionable:EXTended:CONDition?............................................................................................. 615
STATus:QUEStionable:EXTended:ENABle....................................................................................................616
STATus:QUEStionable:EXTended:INFO:CONDition?................................................................................... 615
STATus:QUEStionable:EXTended:INFO:ENABle.......................................................................................... 616
STATus:QUEStionable:EXTended:INFO:NTRansition...................................................................................617
STATus:QUEStionable:EXTended:INFO:PTRansition................................................................................... 618
STATus:QUEStionable:EXTended:INFO[:EVENt]?........................................................................................616
STATus:QUEStionable:EXTended:NTRansition............................................................................................ 617
STATus:QUEStionable:EXTended:PTRansition.............................................................................................618
STATus:QUEStionable:EXTended[:EVENt]?................................................................................................. 616
STATus:QUEStionable:FREQuency:CONDition?.......................................................................................... 615
STATus:QUEStionable:FREQuency:ENABle.................................................................................................616
STATus:QUEStionable:FREQuency:NTRansition......................................................................................... 617
STATus:QUEStionable:FREQuency:PTRansition..........................................................................................618
STATus:QUEStionable:FREQuency[:EVENt]?.............................................................................................. 616
STATus:QUEStionable:LIMit<n>:CONDition?................................................................................................615
STATus:QUEStionable:LIMit<n>:ENABle...................................................................................................... 617
STATus:QUEStionable:LIMit<n>:NTRansition............................................................................................... 617
STATus:QUEStionable:LIMit<n>:PTRansition............................................................................................... 618
STATus:QUEStionable:LIMit<n>[:EVENt]?.................................................................................................... 616
STATus:QUEStionable:LMARgin<n>:CONDition?.........................................................................................615
STATus:QUEStionable:LMARgin<n>:ENABle............................................................................................... 617
STATus:QUEStionable:LMARgin<n>:NTRansition........................................................................................ 617
STATus:QUEStionable:LMARgin<n>:PTRansition........................................................................................ 618
STATus:QUEStionable:LMARgin<n>[:EVENt]?............................................................................................. 616
STATus:QUEStionable:NTRansition.............................................................................................................. 617
STATus:QUEStionable:PNOise:CONDition?................................................................................................. 615
STATus:QUEStionable:PNOise:ENABle........................................................................................................617
STATus:QUEStionable:PNOise:NTRansition.................................................................................................617
STATus:QUEStionable:PNOise:PTRansition.................................................................................................618
STATus:QUEStionable:PNOise[:EVENt]?......................................................................................................616
STATus:QUEStionable:POWer:CONDition?..................................................................................................615
STATus:QUEStionable:POWer:DCPNoise:CONDition?................................................................................ 615
STATus:QUEStionable:POWer:DCPNoise:ENABle.......................................................................................617
STATus:QUEStionable:POWer:DCPNoise:NTRansition............................................................................... 617
STATus:QUEStionable:POWer:DCPNoise:PTRansition................................................................................618
STATus:QUEStionable:POWer:DCPNoise[:EVENt]?.................................................................................... 616
STATus:QUEStionable:POWer:ENABle........................................................................................................ 617
STATus:QUEStionable:POWer:NTRansition................................................................................................. 617
STATus:QUEStionable:POWer:PTRansition................................................................................................. 618
STATus:QUEStionable:POWer[:EVENt]?...................................................................................................... 616
STATus:QUEStionable:PTRansition.............................................................................................................. 618
STATus:QUEStionable:TEMPerature:CONDition?........................................................................................ 615
STATus:QUEStionable:TEMPerature:ENABle...............................................................................................617
STATus:QUEStionable:TEMPerature:NTRansition........................................................................................617
STATus:QUEStionable:TEMPerature:PTRansition........................................................................................618
STATus:QUEStionable:TEMPerature[:EVENt]?.............................................................................................616
STATus:QUEStionable:TIME:CONDition?..................................................................................................... 615
STATus:QUEStionable:TIME:ENABle............................................................................................................617
STATus:QUEStionable:TIME:NTRansition.................................................................................................... 617
STATus:QUEStionable:TIME:PTRansition.....................................................................................................618
STATus:QUEStionable:TIME[:EVENt]?......................................................................................................... 616
STATus:QUEStionable[:EVENt]?................................................................................................................... 616
STATus:QUEue[:NEXT]?............................................................................................................................... 615
SYSTem:CLOGging.......................................................................................................................................580
SYSTem:COMMunicate:GPIB[:SELF]:ADDRess...........................................................................................596
SYSTem:COMMunicate:GPIB[:SELF]:RTERminator.....................................................................................596
SYSTem:COMMunicate:PRINter:ENUMerate:FIRSt..................................................................................... 575
SYSTem:COMMunicate:PRINter:ENUMerate[:NEXT]...................................................................................575
SYSTem:COMMunicate:PRINter:SELect<1|2>............................................................................................. 575
SYSTem:DATE...............................................................................................................................................580
SYSTem:DISPlay:FPANel[:STATe].................................................................................................................592
SYSTem:DISPlay:LOCK................................................................................................................................ 597
SYSTem:DISPlay:UPDate............................................................................................................................. 597
SYSTem:ERRor:CLEar:ALL...........................................................................................................................603
SYSTem:ERRor:CLEar:REMote.................................................................................................................... 597
SYSTem:ERRor:DISPlay............................................................................................................................... 597
SYSTem:ERRor:EXTended?..........................................................................................................................603
SYSTem:ERRor:LIST?...................................................................................................................................603
SYSTem:ERRor[:NEXT]?...............................................................................................................................604
SYSTem:FIRMware:UPDate..........................................................................................................................604
SYSTem:FORMat:IDENt................................................................................................................................604
SYSTem:IDENtify:FACTory............................................................................................................................ 598
SYSTem:IDENtify[:STRing]............................................................................................................................598
SYSTem:KLOCk............................................................................................................................................ 598
SYSTem:LANGuage...................................................................................................................................... 598
SYSTem:LXI:LANReset................................................................................................................................. 599
SYSTem:LXI:MDEScription............................................................................................................................599
SYSTem:LXI:PASSword................................................................................................................................ 599
SYSTem:PASSword:RESet........................................................................................................................... 608
SYSTem:PASSword[:CENable]..................................................................................................................... 608
SYSTem:PRESet........................................................................................................................................... 564
SYSTem:PRESet:CHANnel[:EXEC].............................................................................................................. 564
SYSTem:PRESet:COMPatible.......................................................................................................................605
SYSTem:PRESet:FILTer................................................................................................................................ 605
SYSTem:PSA:WIDeband...............................................................................................................................599
SYSTem:REBoot............................................................................................................................................580
SYSTem:SECurity[:STATe]............................................................................................................................ 605
SYSTem:SEQuencer..................................................................................................................................... 394
SYSTem:SHIMmediate ONCE.......................................................................................................................600
SYSTem:SHIMmediate:STATe.......................................................................................................................599
SYSTem:SHUTdown......................................................................................................................................580
SYSTem:TIME............................................................................................................................................... 580
TRACe<n>:COPY..........................................................................................................................................518
TRACe<n>:POINts?...................................................................................................................................... 410
TRACe<n>[:DATA]:LINear?........................................................................................................................... 409
TRACe<n>[:DATA]:X:POINts?....................................................................................................................... 411
TRACe<n>[:DATA]:X?....................................................................................................................................411
TRACe<n>[:DATA]:Y:POINts?....................................................................................................................... 412
TRACe<n>[:DATA]:Y?....................................................................................................................................411
TRACe<n>[:DATA]?.......................................................................................................................................408
TRIGger[:SEQuence]:DTIMe......................................................................................................................... 489
TRIGger[:SEQuence]:FREQuency................................................................................................................ 489
TRIGger[:SEQuence]:FREQuency:HYSTeresis............................................................................................ 489
TRIGger[:SEQuence]:HOLDoff[:TIME].......................................................................................................... 490
TRIGger[:SEQuence]:IFPower:HOLDoff....................................................................................................... 490
TRIGger[:SEQuence]:LEVel[:EXTernal<1|2>]................................................................................................490
TRIGger[:SEQuence]:SLOPe........................................................................................................................ 491
TRIGger[:SEQuence]:SOURce......................................................................................................................491
Index
Symbols Bias
Conversion loss table ....................................... 137, 140
*IDN External Mixer ................................................... 130, 137
Format ...................................................................... 356 External Mixer (remote) ............................................ 422
*OPC ............................................................................... 331 Block data ....................................................................... 327
*OPC? ............................................................................. 331 Boolean parameters ........................................................ 326
*RST ................................................................................ 349 Brackets .......................................................................... 327
*WAI ................................................................................ 331 Brochures .......................................................................... 19
9.91E37
Remote control ......................................................... 329 C
A Calibration
Frequency ................................................................. 305
Aborting Frequency MW ......................................................... 307
Sweep ............................................................... 109, 110 Frequency RF ........................................................... 306
AC/DC coupling ............................................................... 126 Remote ..................................................................... 385
Alignment Remote control ......................................................... 586
Basics ....................................................................... 275 Results (remote control) ........................................... 586
Performing ........................................................ 280, 281 RF ............................................................................. 306
Results ...................................................... 276, 277, 280 Settings ..................................................................... 305
Settings ..................................................................... 277 Signal ........................................................................ 305
touchscreen ...................................................... 276, 280 Capture Range ........................................................ 149, 156
Touchscreen ............................................................. 277 Case-sensitivity
Alphanumeric keys ............................................................ 39 SCPI ......................................................................... 323
Alphanumeric parameters ................................................. 87 Channel
AM (trace information) ....................................................... 77 Creating (remote) .............................................. 390, 392
Analog Modulation Analysis Deleting (remote) ...................................................... 390
Application ................................................................ 100 Duplicating (remote) ................................................. 389
Annotations Querying (remote) ..................................................... 391
Hiding/restoring ......................................................... 284 Renaming (remote) ................................................... 392
Application cards ............................................................... 19 Replacing (remote) ................................................... 390
Application notes ............................................................... 19 Selecting (remote) .................................................... 392
Applications Channel bar
Analog Modulation Analysis ...................................... 100 Hiding/restoring ......................................................... 284
I/Q Analyzer .............................................................. 100 Information .................................................................. 75
Noise Figure ............................................................. 100 channel settings
Phase Noise ............................................................... 99 Presetting .................................................................. 245
Pulse ......................................................................... 101 Channel settings
Spectrum .................................................................. 100 Display ........................................................................ 75
Spectrum Monitor ....................................................... 99 Channels
Spurious Measurements ........................................... 101 Duplicating ................................................................ 102
Transient Analysis .....................................................101 New ........................................................................... 102
Vector Signal Analysis (VSA) .................................... 101 Replacing .................................................................. 102
Arranging see also Measurement channels ................................ 89
Windows ............................................................. 94, 197 Sequential operation ................................................. 103
ASCII trace export ........................................................... 216 Switching .................................................................... 75
Att (channel bar) ................................................................ 76 Cleaning .......................................................................... 628
Autologin mechanism Clear status
Activating/Deactivating ............................................. 370 Remote ..................................................................... 385
AUX PORT Closing
Connector ................................................................... 47 Channels ..................................................................... 90
Average count ................................................................. 157 Channels (remote) .................................................... 390
AVG (trace information) ..................................................... 77 Windows ............................................................. 93, 197
Windows (remote) ..................................................... 508
B CLRW (trace information) ..................................................77
Colon ............................................................................... 327
Band Colors
Conversion loss table ............................................... 140 Assigning to object .................................................... 288
External Mixer ................................................... 134, 135 Configuring ....................................................... 288, 290
External Mixer (remote) ............................................ 418 Display ...................................................................... 286
Baseband input ................................................................. 43 Editing ....................................................................... 286
Predefined ................................................................ 289
Print .......................................................................... 287
F H
File format Handover frequency
Export Files ............................................................... 216 External Mixer ................................................... 130, 134
Trace export .............................................................. 216 External Mixer (remote) ............................................ 416
File type Hard drive .......................................................................... 46
Storage settings ........................................................ 254 Hardware
filename Check ........................................................................ 299
Data files ................................................................... 252 Diagnostics ............................................................... 309
Settings ............................................................. 254, 256 Information ................................................................ 296
Firmware Supported ................................................................. 299
Updating ................................................................... 299 Harmonics
Firmware Update Conversion loss table ............................................... 140
Remote control ......................................................... 604 External Mixer (remote) ............................................ 419
Firmware updates LO ............................................................................. 129
see User Manual ......................................................... 20 Order (External Mixer) .............................................. 136
Focus Type (External Mixer) ................................................ 135
Changing .................................................................... 86 Hiding/restoring
Format Display items ............................................................ 283
Data .......................................................................... 524 HiSLIP ............................................................................. 313
Data (remote) .................................................... 520, 521 Protocol ..................................................................... 314
Date and time ........................................................... 283 Resource string ......................................................... 313
see also File format .................................................. 216
Frequency I
External reference .................................................... 294
Offset ........................................................................ 149 I/O Logging ......................................................................356
Reference ................................................................. 292 I/Q Analyzer
Frequency (channel bar) ................................................... 76 Application ................................................................ 100
Frequency range I/Q data
Extending .................................................................. 129 Exporting ................................................................... 259
External Mixer ........................................................... 129 Identification
Frequency response ....................................................... 181 Remote ..................................................................... 386
Frequency search ........................................................... 148 String, R&S FSWP .................................................... 355
Front panel String, resetting (R&S FSWP) .................................. 355
Hiding/restoring ......................................................... 284 IEC/IEEE bus
Frontend see GPIB .................................................................. 312
Temperature .............................................................. 276 IECWIN ........................................................................... 350
Temperature (remote) ............................................... 588 IF OVLD
Temperature, status bit ............................................. 345 Error .................................................................... 82, 631
Full screen mode ............................................................... 37 IF/VIDEO/DEMOD
Function keys Connector ................................................................... 47
Details - see user manual ........................................... 38 IFC .................................................................................. 319
Overview ..................................................................... 38 Importing
Functions .................................................................. 252
G Softkey ...................................................................... 259
INF .................................................................................. 325
GET ................................................................................. 319 Information
Getting started ................................................................... 18 Hardware .................................................................. 296
GPIB ................................................................................ 312 Options ..................................................................... 297
Address ............................................................. 355, 368 Version ...................................................................... 297
Characteristics .......................................................... 317 Input
interface messages ................................................... 317 Coupling .................................................................... 126
Language (remote control) ....................................... 598 RF ............................................................................. 126
Settings ..................................................................... 354 Input ExtMix (channel bar) ................................................ 77
Terminator ................................................................. 356 INPUT OVLD
GPIB bus control Error .......................................................................... 631
Remote ..................................................................... 386 INPUT OVLD (status display) ......................................... 631
GPIB interface Input source .................................................................... 125
Configuring - see User Manual ................................... 48 Inserting
Connector ................................................................... 48 Limit line values ........................................................ 239
Remote control ........................................................... 96 Installing
GTL ................................................................................. 319 Options ..................................................................... 298
Instrument messages ...................................................... 321
Instrument name
Changing .................................................................. 366
Instrument settings
Secure user mode .................................................... 248
Touchscreen Updating
Alignment .......................................................... 277, 281 Firmware ................................................................... 299
Colors ............................................................... 286, 287 USB
De-/Activating ........................................................... 282 Address ..................................................................... 319
Displayed items ........................................................ 283 Connector ................................................................... 46
Overview ..................................................................... 35 Interfaces .................................................................. 319
Settings ..................................................................... 281 USB port ............................................................................ 42
Theme ....................................................................... 287 User ports
Trace information .............................................................. 77 Remote control ......................................................... 442
Trace number ..............................................................77 Users
Window title bar .......................................................... 77 Network ..................................................................... 369
Trace labels ..................................................................... 215 Password .................................................................. 370
Trace math
Settings ..................................................................... 214 V
Trace mode ..................................................................... 180
Trace offset ....................................................................... 78 VCO measurements ................................................ 176, 180
Trace smoothing ................................................78, 204, 208 Vendor ID
Traces Rohde & Schwarz ..................................................... 319
Configuration (Softkey) ............................................. 214 Version information ......................................................... 297
Copying ..................................................................... 214 Vertical stroke .................................................................. 327
Copying (remote control) .......................................... 518 VIEW (trace information) ................................................... 77
Export format ............................................................ 212 View filter
Exporting ................................................... 210, 211, 215 Limit lines .................................................................. 237
Mode ......................................................................... 207 VISA ........................................................................ 312, 313
Mode (remote) .......................................................... 512 Libraries .................................................................... 320
Saving ....................................................................... 251 Resource string ................................................. 313, 320
Traces to be Checked Visible
Limit lines .................................................................. 237 Limit lines .................................................................. 237
Transducers Volatile memory
Recalling ................................................................... 248 Secure user mode .............................................. 31, 245
Saving ............................................................... 248, 251 Voltage supply ................................................................. 165
Transient analysis ........................................................... 181 VSA (Vector Signal Analysis)
Transient Analysis Application ................................................................ 101
Application ................................................................ 101 VXI protocol .....................................................................314
Trigger
Event (remote) .......................................................... 388 W
External, errors ......................................................... 632
Holdoff .......................................................................185 Wait
Input ............................................................................ 43 Remote ..................................................................... 388
Offset ........................................................................ 185 Waiting for trigger
Output ......................................................................... 43 Status register ........................................................... 338
Status register ........................................................... 338 Warmup time ................................................................... 279
Troubleshooting Web browser
File name error ......................................................... 562 Configuration interface .............................................. 366
Hardware .................................................................. 309 White papers ..................................................................... 19
Low frequencies ........................................................ 634 White space .................................................................... 327
Remote control programs ................................. 356, 633 Wideband
Timeout for data capture ........................................... 634 PSA89600 ................................................................. 358
Trace display .............................................................634 Window title bar ................................................................. 77
Tuning ..................................................................... 176, 180 Windows
Tuning range ................................................................... 178 Adding ................................................................. 93, 196
External reference .................................................... 294 Adding (remote) ........................................................ 501
Tuning voltage ................................................................. 178 Arranging ............................................................ 94, 197
Closing ................................................................ 93, 197
U Closing (remote) ....................................................... 508
Configuring ............................................................... 125
Ultra-Small RBWs ........................................................... 154 Dialog boxes ............................................................... 86
UNCAL Layout (remote) ........................................................ 505
Error .................................................................... 82, 631 Maximizing (remote) ................................................. 501
UNCAL (status display) ................................................... 631 Querying (remote) ..................................................... 503
Undo ............................................................................40, 41 Replacing (remote) ................................................... 505
UP ................................................................................... 325 Size ............................................................................. 94
Update Path Splitting (remote) ...................................................... 501
Remote control ......................................................... 604 Types (remote) .......................................................... 501
Update rate WRH (trace information) ................................................... 77
Display ...................................................................... 282 WRONG_FW
Error .................................................... 82, 275, 299, 631
X
X-axis
Limit lines .................................................................. 239
X-value
Marker ....................................................................... 227
XCORR ........................................................................... 155
XCORR Factor (channel bar) ............................................ 76
Y
Y-axis
Limit lines .................................................................. 239
Scale ......................................................................... 145
Z
Zooming .................................................................. 198, 200
Activating (remote) .................................................... 511
Area (Multiple mode, remote) ................................... 510
Area (remote) ............................................................ 509
Deactivating .............................................................. 200
Multiple mode ................................................... 198, 199
Multiple mode (remote) ............................................. 511
Restoring original display .......................................... 200
Single mode ...................................................... 198, 199