R&S/R&S FSE Series Operation Vol 2 R&S
R&S FSEA 20/R+S FSEA 20 remote R+S FSEA 20 remote
R+S FSEA 20 remote R+S FSEA 20 remote
User Manual: R&S/R&S FSE Series Operation Vol 2
Open the PDF directly: View PDF 
.
Page Count: 429
| Download | |
| Open PDF In Browser | View PDF |
Test and
Measurement Division
Operating Manual
SPECTRUM ANALYZER
FSEA20/30
1065.6000.20/.25/35
FSEB20/30
1066.3010.20/.25/35
FSEM20/30
1080.1505.20/.21/.25
1079.8500.30/.31/.35
FSEK20/30
1088.1491.20/.21/.25
1088.3494.30/.31/.35
Volume 2
Operating manual consists of 2 volumes
Printed in the Federal
Republic of Germany
1065.6016.12-14-
II
10/01
FSE
Tabbed Divider Overview
Tabbed Divider Overview
Volume 1
Data Sheet
Safety Instructions
Certificate of quality
EC Certificate of Conformity
Support Center
List of R & S Representatives
Manuals for Signal Analyzer FSE
Tabbed Divider
1
Chapter 1:
Putting into Operation
2
Chapter 2:
Getting Started
3
Chapter 3:
Operation
4
Chapter 4:
Functional Description
10
Index
Volume 2
Safety Instructions
Manuals for Signal Analyzer FSE
Tabbed Divider
1065.6016.12
5
Chapter 5:
Remote Control – Basics
6
Chapter 6:
Remote Control – Commands
7
Chapter 7:
Remote Control – Program Examples
8
Chapter 8:
Maintenance and Hardware Interfaces
9
Chapter 9:
Error Messages
10
Index
RE
E-2
Safety Instructions
This unit has been designed and tested in accordance with the EC Certificate of Conformity and has left the
manufacturer’s plant in a condition fully complying with safety standards.
To maintain this condition and to ensure safe operation, the user must observe all instructions and warnings
given in this operating manual.
Safety-related symbols used on equipment and documentation from R&S:
Observe
operating
instructions
1.
Weight
indication for
units >18 kg
PE terminal
Ground
terminal
Danger!
Shock hazard
The unit may be used only in the operating conditions and positions specified by the manufacturer. Unless otherwise agreed, the following
applies to R&S products:
IP degree of protection 2X, pollution severity 2
overvoltage category 2, only for indoor use, altitude max. 2000 m.
The unit may be operated only from supply networks fused with max. 16 A.
Unless specified otherwise in the data sheet, a
tolerance of 10% shall apply to the nominal
voltage and of 5% to the nominal frequency.
2.
For measurements in circuits with voltages Vrms
> 30 V, suitable measures should be taken to
avoid any hazards.
(using, for example, appropriate measuring
equipment, fusing, current limiting, electrical
separation, insulation).
3.
If the unit is to be permanently wired, the PE
terminal of the unit must first be connected to
the PE conductor on site before any other connections are made. Installation and cabling of
the unit to be performed only by qualified technical personnel.
4.
For permanently installed units without built-in
fuses, circuit breakers or similar protective devices, the supply circuit must be fused such as
to provide suitable protection for the users and
equipment.
5.
Prior to switching on the unit, it must be ensured
that the nominal voltage set on the unit matches
the nominal voltage of the AC supply network.
If a different voltage is to be set, the power fuse
of the unit may have to be changed accordingly.
6.
Units of protection class I with disconnectible
AC supply cable and appliance connector may
be operated only from a power socket with
earthing contact and with the PE conductor connected.
1065.6016.12
SI.1
Warning!
Hot surfaces
Ground
Attention!
Electrostatic
sensitive devices require
special care
7.
It is not permissible to interrupt the PE conductor intentionally, neither in the incoming cable
nor on the unit itself as this may cause the unit
to become electrically hazardous.
Any extension lines or multiple socket outlets
used must be checked for compliance with relevant safety standards at regular intervals.
8.
If the unit has no power switch for disconnection
from the AC supply, the plug of the connecting
cable is regarded as the disconnecting device.
In such cases it must be ensured that the power
plug is easily reachable and accessible at all
times (length of connecting cable approx. 2 m).
Functional or electronic switches are not suitable for providing disconnection from the AC
supply.
If units without power switches are integrated in
racks or systems, a disconnecting device must
be provided at system level.
9.
Applicable local or national safety regulations
and rules for the prevention of accidents must
be observed in all work performed.
Prior to performing any work on the unit or
opening the unit, the latter must be disconnected from the supply network.
Any adjustments, replacements of parts, maintenance or repair may be carried out only by
authorized R&S technical personnel.
Only original parts may be used for replacing
parts relevant to safety (eg power switches,
power transformers, fuses). A safety test must
be performed after each replacement of parts
relevant to safety.
(visual inspection, PE conductor test, insulationresistance, leakage-current measurement, functional test).
continued overleaf
E-1
Safety Instructions
10. Ensure that the connections with information
technology equipment comply with IEC950 /
EN60950.
11. Lithium batteries must not be exposed to high
temperatures or fire.
Keep batteries away from children.
If the battery is replaced improperly, there is
danger of explosion. Only replace the battery by
R&S type (see spare part list).
Lithium batteries are suitable for environmentally-friendly disposal or specialized recycling.
Dispose them into appropriate containers, only.
Do not short-circuit the battery.
12. Equipment returned or sent in for repair must be
packed in the original packing or in packing with
electrostatic and mechanical protection.
13. Electrostatics via the connectors may dam-
age the equipment. For the safe handling and
operation of the equipment,
appropriate
measures against electrostatics should be implemented.
14. The outside of the instrument is suitably
cleaned using a soft, lint-free dustcloth. Never
use solvents such as thinners, acetone and
similar things, as they may damage the front
panel labeling or plastic parts.
15. Any additional safety instructions given in this
manual are also to be observed.
Patent Information
This product contains technology licensed by Marconi Instruments LTD. under US patent 4609881 and
under the corresponding patent in Germany and elsewhere.
1065.6016.12
SI.2
E-1
FSE
Manuals
Contents of Manuals for Spectrum Analyzer FSE
Operating Manual FSE
The operating manual describes the following models and options:
• FSEA20/30
9kHz/20 Hz to 3,5 GHz
• FSEB20/30
9kHz/20 Hz to 7 GHz
• FSEM20/30
9kHz/20 Hz to 26,5 GHz
• FSEK20/30
9kHz/20 Hz to 40 GHz
•
•
•
•
•
•
•
•
Option FSE-B3
Option FSE-B5
Option FSE-B8/9/10/11
Option FSE-B13
Option FSE-B15
Option FSE-B15
Option FSE-B16
Option FSE-B17
TV Demodulator
FFT Filter
Tracking Generator
1 dB Attenuator
DOS Controller (Id.-Nr: 1073.5696.02/.03)
Windows NT Controller (Id.-Nr.: 1073.5696.06)
Ethernet Adapter
Second IEC/IEEE Bus Interface
Options FSE-B7, Vector Signal Analysis, and FSE-B21, External Mixer Output, are described in separate manuals.
The present operating manual contains comprehensive information about the technical data of the
instrument, the setup and putting into operation of the instrument, the operating concept and controls
as well as the operation of the FSE via the menus and via remote control. Typical measurement
tasks for the FSE are explained using the functions offered by the menus and a selection of program
examples.
In addition the operating manual gives information about maintenance of the instrument and about
error detection listing the error messages which may be output by the instrument. It is subdivided into
2 volumes containing the data sheet plus 9 chapters:
Volume 1
The data sheet
Chapter 1
Chapter 2
Chapter 3
Chapter 4
Chapter 10
Volume 2
Chapter 5
Chapter 6
Chapter 7
Chapter 8
Chapter 8
Chapter 9
Chapter 10
1065.6016.12
informs about guaranteed specifications and characteristics of the instrument.
describes the control elements and connectors on the front and rear panel as
well as all procedures required for putting the FSE into operation and integration into a test system.
gives an introduction to typical measurement tasks of the FSE which are explained step by step.
describes the operating principles, the structure of the graphical interface and
offers a menu overview.
forms a reference for manual control of the FSE and contains a detailed description of all instrument functions and their application.
contains an index for the operating manual.
describes the basics for programming the FSE, command processing and the
status reporting system.
lists all the remote-control commands defined for the instrument. At the end of
the chapter a alphabetical list of commands and a table of softkeys with command assignment is given.
contains program examples for a number of typical applications of the FSE.
describes preventive maintenance and the characteristics of the instrument’s
interfaces.
gives a list of error messages that the FSE may generate.
contains a list of error messages.
contains an index for the operating manual.
0.1
E-1
Manuals
FSE
Service Manual - Instrument
The service manual - instrument informs on how to check compliance with rated specifications (performance test) and on the self tests.
Service Manual
The service manual is not delivered with the instrument but may be obtained from your R&S service
department using the order number 1065.6016.94.
The service manualinforms on instrument function, repair, troubleshooting and fault elimination. It
contains all information required for the maintenance of FSE by exchanging modules.It contains information about the individual modules of FSE. This comprises the test and adjustment of the modules, fault detection within the modules and the interface description.
1065.6016.12
0.2
E-1
FSE
Contents - Remote Control - Basics
Contents - Chapter 5 "Remote Control - "Basics"
5 Remote Control - Basics..................................................................................... 5.1
Introduction ...................................................................................................................................... 5.1
Brief Instructions ............................................................................................................................. 5.2
Switchover to Remote Control ....................................................................................................... 5.2
Indications during Remote Control .......................................................................................... 5.2
Remote Control via IEC Bus.................................................................................................... 5.3
Setting the Device Address ........................................................................................... 5.3
Return to Manual Operation .......................................................................................... 5.3
Remote Control via RS-232-Interface ..................................................................................... 5.4
Setting the Transmission Parameters ........................................................................... 5.4
Return to Manual Operation .......................................................................................... 5.4
Limitations ..................................................................................................................... 5.5
Remote Control via RSIB Interface ......................................................................................... 5.6
Windows Environment .................................................................................................. 5.6
Unix Enviroment – with Windows NT Controller ........................................................... 5.6
Remote Control ............................................................................................................. 5.6
Return to Manual Operation .......................................................................................... 5.6
Messages.......................................................................................................................................... 5.7
IEE/IEEE-Bus Interface Messages.......................................................................................... 5.7
RSIB Interface Messages........................................................................................................ 5.7
Device Messages (Commands and Device Responses) ........................................................ 5.8
Structure and Syntax of the Device Messages ............................................................................. 5.9
SCPI Introduction..................................................................................................................... 5.9
Structure of a Command ......................................................................................................... 5.9
Structure of a Command Line................................................................................................ 5.12
Responses to Queries ........................................................................................................... 5.12
Parameters ............................................................................................................................ 5.13
Overview of Syntax Elements................................................................................................ 5.14
Instrument Model and Command Processing ............................................................................ 5.15
Input Unit ............................................................................................................................... 5.15
Command Recognition .......................................................................................................... 5.16
Data Set and Instrument Hardware ....................................................................................... 5.16
Status Reporting System ....................................................................................................... 5.16
Output Unit............................................................................................................................. 5.17
Command Sequence and Command Synchronization.......................................................... 5.17
Status Reporting System .............................................................................................................. 5.18
Structure of an SCPI Status Register .................................................................................... 5.18
Overview of the Status Registers .......................................................................................... 5.20
Description of the Status Registers ....................................................................................... 5.21
Status Byte (STB) and Service Request Enable Register (SRE) ................................ 5.21
IST Flag and Parallel Poll Enable Register (PPE)....................................................... 5.22
Event-Status Register (ESR) and Event-Status-Enable Register (ESE)..................... 5.22
STATus:OPERation Register ...................................................................................... 5.23
STATus:QUEStionable Register ................................................................................. 5.24
STATus QUEStionable:ACPLimit Register ................................................................. 5.25
1065.6016.12
I-5.1
E-1
Contents - Remote Control - Basics
FSE
STATus QUEStionable:FREQuency Register............................................................. 5.26
STATus QUEStionable:LIMit Register ........................................................................ 5.27
STATus QUEStionable:LMARgin Register ................................................................. 5.28
STATus QUEStionable:POWer Register .................................................................... 5.29
STATus QUEStionable:SYNC Register ...................................................................... 5.30
STATus QUEStionable:TRANsducer Register ........................................................... 5.31
Application of the Status Reporting Systems......................................................................... 5.32
Service Request, Making Use of the Hierarchy Structure ........................................... 5.32
Serial Poll .................................................................................................................... 5.32
Parallel Poll.................................................................................................................. 5.33
Query by Means of Commands................................................................................... 5.33
Error-Queue Query...................................................................................................... 5.33
Resetting Values of the Status Reporting System................................................................. 5.34
1065.6016.12
I-5.2
E-1
FSE
Introduction
5 Remote Control - Basics
In this chapter you find:
• instructions how to put the FSE into operation via remote control,
• a general introduction to remote control of programmable instruments. This includes the description
of the command structure and syntax according to the SCPI standard, the description of command
execution and of the status registers,
• diagrams and tables describing the status registers used in the FSE.
In chapter 6, all remote control functions are described in detail. The subsystems are listed by
alphabetical order according to SCPI. All commands and their parameters are listed by alphabetical
order in the command list at the end of chapter 6.
Program examples for the FSE can be found in chapter 7.
The remote control interfaces and their interface functions are described in chapter 8.
Introduction
The instrument is equipped with an IEC-bus interface according to standard IEC 625.1/IEEE 488.2 and
two RS-232 interfaces. The connector is located at the rear of the instrument and permits to connect a
controller for remote control.
The option FSE-B15, (controller function) together with the option FSE B17 (2nd IEC-bus interface) may
also be used as a controller (see chapter 1, section "Option FSE-B17 - Second IEC/IEEE Interface).
In addition, the instrument is equipped with an RSIB interface that allows instrument control by Visual
C++ and Visual Basic programs
The instrument supports the SCPI version 1994.0 (Standard Commands for Programmable
Instruments). The SCPI standard is based on standard IEEE 488.2 and aims at the standardization of
device-specific commands, error handling and the status registers (see section "SCPI Introduction").
This section assumes basic knowledge of IEC-bus programming and operation of the controller. A
description of the interface commands is to be obtained from the relevant manuals. The RSIB interface
functions are matched to the function interface for IEC/IEEE-bus programming from National
Instruments. The functions supported by the DLLs are listed in chapter 8.
The requirements of the SCPI standard placed on command syntax, error handling and configuration of
the status registers are explained in detail in the respective sections. Tables provide a fast overview of
the commands implemented in the instrument and the bit assignment in the status registers. The tables
are supplemented by a comprehensive description of every command and the status registers. Detailed
program examples of the main functions are to be found in chapter 7.
The program examples for IEC-bus programming are all written in Quick BASIC.
1065.6016.12
5.1
E-16
Brief Instructions
FSE
Brief Instructions
The short and simple operating sequence given below permits fast putting into operation of the
instrument and setting of its basic functions. As a prerequisite, the IEC-bus address, which is factory-set
to 20, must not have been changed.
1. Connect instrument and controller using IEC-bus cable.
2. Write and start the following program on the controller:
CALL
CALL
CALL
CALL
CALL
CALL
IBFIND("DEV1", analyzer%)
’Open port to the instrument
IBPAD(analyzer%, 20)
’Inform controller about instrument address
IBWRT(analyzer%, "*RST;*CLS")
’Reset instrument
IBWRT(analyzer%, ’FREQ:CENT 100MHz’)
’Set center frequency to 100 MHz
IBWRT(analyzer%, ’FREQ:SPAN 10MHz’)
’Set span to 10 MHz
IBWRT(analyzer%, ’DISP:TRAC:Y:RLEV -10dBm’)
’Set reference level to -10 dBm
The instrument now performs a sweep in the frequency range of 95 MHz to 105 MHz.
3. To return to manual control, press the LOCAL key at the front panel
Switchover to Remote Control
On power-on, the instrument is always in the manual operating state ("LOCAL" state) and can be
operated via the front panel.
It is switched to remote control ("REMOTE" state)
IEC-bus
as soon as it receives an addressed command from a controller.
RS-232
as soon as it receives the command ’@REM’ from a controller.
RSIB
as soon as it receives an addressed command from a controller.
During remote control, operation via the front panel is disabled. The instrument remains in the remote
state until it is reset to the manual state via the front panel or via remote control interfaces. Switching
from manual operation to remote control and vice versa does not affect the remaining instrument
settings.
Indications during Remote Control
Remote control mode is indicated by the LED "REMOTE" on the instrument’s front panel. In this mode
the softkeys, the function fields and the diagram labelling on the display are not shown.
Note: Command SYSTem:DISPlay:UPDate ON activates all indications during remote control to
check the instrument settings.
1065.6016.12
5.2
E-16
FSE
Switchover to Remote Control
Remote Control via IEC Bus
Setting the Device Address
In order to operate the instrument via the IEC-bus, it must be addressed using the set IEC-bus address.
The IEC-bus address of the instrument is factory-set to 20. It can be changed manually in the SETUP GENERAL SETUP menu or via IEC bus. Addresses 0 to 31 are permissible.
Manually:
½ Call SETUP - GENERAL SETUP menu
½ Enter desired address in table GPIB ADDRESS
½ Terminate input using one of the unit keys (=ENTER).
Via IEC bus:
CALL
CALL
CALL
CALL
IBFIND("DEV1", analyzer%)
’Open port to the instrument
IBPAD(analyzer%, 20)
’Inform controller about old address
IBWRT(analyzer%, "SYST:COMM:GPIB:ADDR 18")’Set instrument to new address
IBPAD(analyzer%, 18)
’Inform controller about new address
Return to Manual Operation
Return to manual operation is possible via the front panel or the IEC bus.
Manually:
½ Press the LOCAL key.
Notes:
– Before switchover, command processing must be completed as
otherwise switchover to remote control is effected immediately.
– The LOCAL key can be disabled by the universal command LLO
(see chapter 8) in order to prevent unintentional switchover. In
this case, switchover to manual mode is only possible via the IEC
bus.
– The LOCAL key can be enabled again by deactivating the REN
line of the IEC bus (see chapter 8).
Via IEC bus:
1065.6016.12
...
CALL IBLOC(analyzer%)
...
5.3
’Set instrument to manual operation.
E-16
Switchover to Remote Control
FSE
Remote Control via RS-232-Interface
Setting the Transmission Parameters
To enable an error-free and correct data transmission, the parameters of the unit and the controller
should have the same setting. Parameters can be manually changed in menu SETUP-GENERAL
SETUP in table COM PORT 1/2 or via remote control using the command
SYSTem:COMMunicate:SERial1|2:... .
The transmission parameters of the interfaces COM1 and COM2 are factory-set to the following values:
Instruments with Windows NT controller:
baudrate = 9600, data bits = 8, stop bits = 1, parity = NONE and owner = INSTRUMENT.
Manually:
Setting interface COM1|2
½ Call SETUP-GENERAL SETUP menu
½ Select desired baudrate, bits, stopbit, parity and protocoll in table
COM PORT 1/2.
½ Set owner to Instrument or INSTR and DOS in table COM PORT1/2 (with
option FSE-B15 only)
½ Terminate input using one of the unit keys (=ENTER).
Instruments with MS DOS controller or without controller:
baudrate = 9600, data bits = 8, stop bits = 1, parity = NONE, protocoll = NONE
and owner = INSTRUMENT.
Manually:
Setting interface COM1|2
½ Call SETUP-GENERAL SETUP menu
½ Select desired baudrate, bits, stopbit, parity and protocoll in table
COM PORT 1/2.
½ Set owner to Instrument or INSTR and DOS in table COM PORT1/2 (with
MS DOS option FSE-B15 only)
½ Terminate input using one of the unit keys (=ENTER).
Return to Manual Operation
Return to manual operation is possible via the front panel or via RS-232 interface.
Manually:
½ Press the LOCAL key.
Notes:
Before switchover, command processing must be completed as
otherwise switchover to remote control is effected immediately.
– The LOCAL key can be disabled by the universal command LLO
(see chapter 8) in order to prevent unintentional switchover. In this
case, switchover to manual mode is only possible via remote
control.
– The LOCAL key can be enabled again by sending the control
codes "@LOC" via RS-232 (see chapter 8).
Via RS-232:
1065.6016.12
...
V24puts(port, ’@LOC’);
...
5.4
Set instrument to manual operation.
E-16
FSE
Switchover to Remote Control
Limitations
The following limitations apply if the unit is remote-controlled via the RS-232-C interface:
− No interface messages, some control codes are defined (see chapter 8).
− Only the Common Commands *OPC? can be used for command synchronization, *WAI and *OPC
are not available.
− Block data cannot be transmitted.
When Windows NT is booted, data are output via the COM interface because of automatic external
device recognition. Therefore, it is recommended to clear the input buffer of the controller before remote
operation of the instrument via the COM interface.
1065.6016.12
5.5
E-16
Switchover to Remote Control
FSE
Remote Control via RSIB Interface
Notes:
The RSIB interface is only available for instruments equipped with controller option, FSE-B15.
Windows Environment
To access the measuring instruments via the RSIB interface the DLLs should be installed in the
corresponding directories:
Instruments with Windows NT controller:
• RSIB.DLL in Windows NT system directory or control application directory.
• RSIB32.DLL in Windows NT system32 directory or control application directory.
On the measuring instrument the DLL is already installed in the corresponding directory.
Instruments with MS DOS controller
• RSIB.DLL in Windows NT system directory or control application directory.
Unix Enviroment – with Windows NT Controller
In order to access the measuring equipment via the RSIB interface, copy the librsib.so.X.Y file to a
directory for which the control application has read rights. X.Y in the file name indicates the version
number of the library, for example 1.0 (for details see Chapter 8).
Remote Control
The control is performed with Visual C++ or Visual Basic programs. The local link to the internal
controller is established with the name ’@local. If a remote controller is used, the instrument IP address
is to be indicated here(only with Windows NTcontroller) .
Via VisualBasic:
internal controller:
ud = RSDLLibfind (’@local’, ibsta, iberr, ibcntl)
remote controller:
ud = RSDLLibfind (’82.1.1.200’, ibsta, iberr, ibcntl)
Return to Manual Operation
The return to manual operation can be performed via the front panel (LOCAL key) or the RSIB interface.
Manually:
½ Press the LOCAL key.
Note:
Via RSIB:
1065.6016.12
Before switchover, command processing must be completed as
otherwise switchover to remote control is effected immediately.
...
ud = RSDLLibloc (ud, ibsta, iberr, ibcntl);
...
5.6
E-16
FSE
Messages
Messages
The messages transferred via the data lines of the IEC bus or the RSIB interface (see chapter 8) can be
divided into two groups:
– interface messages and
– device messages.
Some control characters are defined for the control of the RS-232-interface (see chapter 8).
IEE/IEEE-Bus Interface Messages
Interface messages are transferred on the data lines of the IEC bus, the "ATN" control line being active.
They are used for communication between controller and instrument and can only be sent by a
controller which has the IEC-bus control. Interface commands can be subdivided into
– universal commands and
– addressed commands.
Universal commands act on all devices connected to the IEC bus without previous addressing,
addressed commands only act on devices previously addressed as listeners. The interface messages
relevant to the instrument are listed in chapter 8.
RSIB Interface Messages
The RSIB interface enables the instrument to be controlled by Visual C++ or Visual Basic programs. The
interface functions are matched to the function interface for IEC/IEEE-bus programming from National
Instruments.
The functions supported by interface are listed in chapter 8.
1065.6016.12
5.7
E-16
Messages
FSE
Device Messages (Commands and Device Responses)
Device messages are transferred on the data lines of the IEC bus, the "ATN" control line not being
active. ASCII code is used. The device messages are more or less equal for the different interfaces.
A distinction is made according to the direction in which they are sent on the IEC bus:
– Commands
are messages the controller sends to the instrument. They operate the device
functions and request informations.
The commands are subdivided according to two criteria::
1. According to the effect they have on the instrument:
Setting commands
cause instrument settings such as reset of the
instrument or setting the center frequency.
Queries
cause data to be provided for output on the IEC-bus,
e.g. for identification of the device or polling the
marker.
2. According to their definition in standard IEEE 488.2:
Common Commands
Device-specific
commands
are exactly defined as to their function and
notation in standard IEEE 488.2. They refer to
functions such as management of the standar-dized
status registers, reset and selftest.
refer to functions depending on the features of the
instrument such as frequency setting. A majority of
these commands has also been standardized by the
SCPI committee (cf. Section 3.5.1).
– Device responses are messages the instrument sends to the controller after a query. They can
contain measurement results, instrument settings and information on the
instrument status (cf. Section 3.5.4).
Structure and syntax of the device messages are described in the following section. The commands are
listed and explained in detail in chapter 6.
1065.6016.12
5.8
E-16
FSE
Structure and Syntax of the Device Messages
Structure and Syntax of the Device Messages
SCPI Introduction
SCPI (Standard Commands for Programmable Instruments) describes a standard command set for
programming instruments, irrespective of the type of instrument or manufacturer. The goal of the SCPI
consortium is to standardize the device-specific commands to a large extent. For this purpose, a model
was developed which defines the same functions inside a device or for different devices. Command
systems were generated which are assigned to these functions. Thus it is possible to address the same
functions with identical commands. The command systems are of a hierarchical structure.
Fig. 5-1 illustrates this tree structure using a section of command system SENSe, which controls the
sensor functions of the devices.
SCPI is based on standard IEEE 488.2, i.e. it uses the same syntactic basic elements as well as the
common commands defined in this standard. Part of the syntax of the device responses is defined with
greater restrictions than in standard IEEE 488.2 (see Section "Responses to Queries").
Structure of a Command
The commands consist of a so-called header and, in most cases, one or more parameters. Header and
parameter are separated by a "white space" (ASCII code 0 to 9, 11 to 32 decimal, e.g. blank). The
headers may consist of several key words. Queries are formed by directly appending a question mark to
the header.
Note:
The commands used in the following examples are not in every case implemented in the
instrument.
Common commands
Common commands consist of a header preceded by an asterisk "*"
and one or several parameters, if any.
Examples:
1065.6016.12
*RST
RESET, resets the device
*ESE 253 EVENT STATUS ENABLE, sets the bits of the
event status enable register
*ESR?
EVENT STATUS QUERY, queries the
contents of the event status register.
5.9
E-16
Structure and Syntax of the Device Messages
FSE
Device-specific commands
Hierarchy:
Device-specific commands are of hierarchical structure (see
Fig. 5-1). The different levels are represented by combined headers.
Headers of the highest level (root level) have only one key word. This
key word denotes a complete command system.
Example:
SENSe
This key word denotes the command system
SENSe.
For commands of lower levels, the complete path has to be specified,
starting on the left with the highest level, the individual key words being
separated by a colon ":".
Example:
SENSe:FREQuency:SPAN:LINK STARt
This command lies in the fourth level of the SENSe system. It
determines which parameter remains unchanged when the span is
changed. If LINK is set to STARt, the values of CENTer and STOP are
adjusted when the span is changed.
SENSe
BANDwidth
FUNCtion
STARt
FREQuency
STOP
DETector
CENTer
SPAN
HOLD
OFFSet
LINK
Fig. 5-1 Tree structure the SCPI command systems using the SENSe system by way of example
Some key words occur in several levels within one command system. Their
effect depends on the structure of the command, that is to say, at which
position in the header of a command they are inserted.
Example: SOURce:FM:POLarity NORMal
This command contains key word POLarity in the third
command level. It defines the polarity between modulator and
modulation signal.
SOURce:FM:EXTernal:POLarity NORMal
This command contains key word POLarity in the fourth
command level. It defines the polarity between modulation
voltage and the resulting direction of the modulation only for the
external signal source indicated.
1065.6016.12
5.10
E-16
FSE
Structure and Syntax of the Device Messages
Optional key words:
Some command systems permit certain key words to be optionally inserted
into the header or omitted. These key words are marked by square
brackets in the description. The full command length must be recognized
by the instrument for reasons of compatibility with the SCPI standard.
Some commands are considerably shortened by these optional key words.
Example: [SENSe]:BANDwidth[:RESolution]:AUTO
This command couples the resolution bandwidth of the
instrument to other parameters. The following command has
the same effect:
BANDwidth:AUTO
Note:
Long and short form:
Parameter:
An optional key word must not be omitted if its effect is specified
in detail by a numeric suffix.
The key words feature a long form and a short form. Either the short form
or the long form can be entered, other abbreviations are not permissible.
Beispiel:
STATus:QUEStionable:ENABle 1= STAT:QUES:ENAB 1
Note:
The short form is marked by upper-case letters, the long form
corresponds to the complete word. Upper-case and lower-case
notation only serve the above purpose, the instrument itself
does not make any difference between upper-case and lowercase letters.
The parameter must be separated from the header by a "white space". If
several parameters are specified in a command, they are separated by a
comma ",". A few queries permit the parameters MINimum, MAXimum and
DEFault to be entered. For a description of the types of parameter, refer to
Section 3.5.5.
Example: SENSe:FREQuency:STOP? MAXimum
Response: 3.5E9
This query requests the maximal value for the stop frequency.
Numeric suffix:
If a device features several functions or features of the same kind, e.g.
inputs, the desired function can be selected by a suffix added to the command. Entries without suffix are interpreted like entries with the suffix 1.
Example:. SYSTem:COMMunicate:SERial2:BAUD 9600
This command sets the baudrate of the second serial interface.
1065.6016.12
5.11
E-16
Structure and Syntax of the Device Messages
FSE
Structure of a Command Line
A command line may consist of one or several commands. It is terminated by a , a with EOI or an EOI together with the last data byte. Quick BASIC automatically produces an EOI
together with the last data byte.
Several commands in a command line are separated by a semicolon ";". If the next command belongs
to a different command system, the semicolon is followed by a colon.
Example:
CALL IBWRT(analyzer, "SENSe:FREQuency:CENTer 100MHz;:INPut:ATTenuation 10")
This command line contains two commands. The first command is part of the SENSe
system and is used to specify the center frequency of the analyzer. The second command
is part of the INPut system and sets the attenuation of the input signal.
If the successive commands belong to the same system, having one or several levels in common, the
command line can be abbreviated. To this end, the second command after the semicolon starts with the
level that lies below the common levels (see also Fig. 5-1). The colon following the semicolon must be
omitted in this case.
Example:
CALL IBWRT(analyzer, "SENSe:FREQuency:STARt 1E6;:SENSe:FREQuency:STOP 1E9")
This command line is represented in its full length and contains two commands separated
from each other by the semicolon. Both commands are part of the SENSe command
system, subsystem FREQuency, i.e. they have two common levels.
When abbreviating the command line, the second command begins with the level below
SENSe:FREQuency. The colon after the semicolon is omitted.
The abbreviated form of the command line reads as follows:
CALL IBWRT(analyzer,
"SENSe:FREQuency:STARt 1E6;STOP 1E9")
However, a new command line always begins with the complete path.
Example:
CALL IBWRT(analyzer,
CALL IBWRT(analyzer,
"SENSe:FREQuency:STARt 1E6")
"SENSe:FREQuency:STOP 1E9")
Responses to Queries
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.
1 The requested parameter is transmitted without header.
Example:
INPut:COUPling?
Response: DC
2. Maximum values, minimum values and all further quantities, which are requested via a special text
parameter are returned as numerical values.
Example:
SENSe:FREQuency:STOP? MAX
Response: 3.5E9
3. Numerical values are output without a unit. Physical quantities are referred to the basic units or to the
units set using the Unit command.
Example:
SENSe:FREQuency:CENTer?
Response: 1E6 for 1 MHz
4. Truth values are returned as 0 (for OFF) and 1 (for ON).
Example:
SENSe:BANDwidth:AUTO?
Response: 1 for ON
5. Text (character data) is returned in a short form (see also Section 3.5.5).
Example:
SYSTem:COMMunicate:SERial:CONTrol:RTS? Response(for standard): STAN
1065.6016.12
5.12
E-16
FSE
Structure and Syntax of the Device Messages
Parameters
Most commands require a parameter to be specified. The parameters must be separated from the
header by a "white space". Permissible parameters are numerical values, Boolean parameters, text,
character strings and block data. The type of parameter required for the respective command and the
permissible range of values are specified in the command description (see Section 3.6).
Numerical values
Numerical 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 value range is -9.9E37 to 9.9E37. The exponent is introduced by an
"E" or "e". Entry of the exponent alone is not permissible. In the case of
physical quantities, the unit can be entered. Permissible unit prefixes are G
(giga), MA (mega), MOHM and MHZ are also permissible), K (kilo), M (milli), U
(micro) and N (nano). It the unit is missing, the basic unit is used.
Example:
SENSe:FREQuency:STOP 1.5GHz = SENSe:FREQuency:STOP 1.5E9
Special numerical
The texts MINimum, MAXimum, DEFault, UP and DOWN are interpreted as
valuesspecial numerical values.
In the case of a query, the numerical value is provided.
Example: Setting command: SENSe:FREQuency:STOP MAXimum
Query:
SENSe:FREQuency:STOP? Response: 3.5E9
MIN/MAX
MINimum and MAXimum denote the minimum and maximum value.
DEF
DEFault denotes a preset value which has been stored in the EPROM. This
value conforms to the default setting, as it is called by the *RST command
UP/DOWN
UP, DOWN increases or reduces the numerical value by one step. The step
width can be specified via an allocated step command for each parameter
which can be set via UP, DOWN.
INF/NINF
INFinity, Negative INFinity (NINF) Negative INFinity (NINF) represent the
numerical values -9.9E37 or 9.9E37, respectively. INF and NINF are only sent
as device reponses.
NAN
Not A Number (NAN) represents the value 9.91E37. NAN is only sent as
device response. This value is not defined. Possible causes are the division by
zero, the subtraction/addition of infinite and the representation of undefined
values.
Boolean Parameters
Boolean parameters represent two states. The ON state (logically true) is
represented by ON or a numerical value unequal to 0. The OFF state (logically
untrue) is represented by OFF or the numerical value 0. 0 or 1 is provided in a
query.
Example: Setting command: DISPlay:WINDow:STATe ON
Query:
DISPlay:WINDow:STATe?
1065.6016.12
5.13
Response: 1
E-16
Structure and Syntax of the Device Messages
Text
FSE
Text parameters observe the syntactic rules for key words, 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 case of a query, the short
form of the text is provided.
Example: Setting command: INPut:COUPling
Query:
INPut:COUPling?
Strings
GROund
Response GRO
Strings must always be entered in quotation marks (’ or ").
Example: SYSTem:LANGuage "SCPI"
SYSTem:LANGuage ’SCPI’
Block data
or
Block data are a transmission format which is suitable for the transmission of
large amounts of data. A command using a block data parameter has the
following structure:
Example: HEADer:HEADer #45168xxxxxxxx
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 following digits indicate the length to be 5168 bytes. The data bytes follow.
During the transmission of these data bytes all End or other control signs are
ignored until all bytes are transmitted..
Overview of Syntax Elements
The following survey offers an overview of the syntax elements.
:
The colon separates the key words of a command.
In a command line the separating semicolon marks the uppermost
command level.
;
The semicolon separates two commands of a command line.
It does not alter the path.
,
The comma separates several parameters of a command.
?
The question mark forms a query.
*
The asterisk marks a common command.
"
Double or single quotation marks introduce a string and terminate it.
’
#
The double dagger # introduces block data.
A "white space" (ASCII-Code 0 to 9, 11 to 32 decimal, e.g. blank) separates
header and parameter.
1065.6016.12
5.14
E-16
FSE
Instrument Model and Command Processing
Instrument Model and Command Processing
The instrument model shown in Fig. 5-2 has been made viewed from the standpoint of the servicing of
IEC-bus commands. The individual components work independently of each other and simultaneously.
They communicate by means of so-called "messages".
Input unit with
IEC Bus
input puffer
Command
recognition
Data set
Status reportingsystem
Instrument
hardware
IEC Bus
Output unit with
output buffer
Fig. 5-2 Instrument model in the case of remote control by means of the IEC bus
Input Unit
The input unit receives commands character by character from the IEC bus and collects them in the
input buffer. The input buffer has a size of 256 characters. The input unit sends a message to the
command recognition as soon as the input buffer is full or as soon as it receives a delimiter,
, as defined in IEEE 488.2, or the interface message DCL.
If the input buffer is full, the IEC-bus traffic is stopped and the data received up to then are processed.
Subsequently the IEC-bus traffic is continued. If, however, the buffer is not yet full when receiving the
delimiter, the input unit can already receive the next command during command recognition and
execution. The receipt of a DCL clears the input buffer and immediately initiates a message to the
command recognition.
1065.6016.12
5.15
E-16
Instrument Model and Command Processing
FSE
Command Recognition
The command recognition analyses the data received from the input unit. It proceeds in the order in
which it receives the data. Only a DCL is serviced with priority, a GET (Group Execute Trigger), e.g., is
only executed after the commands received before as well. Each recognized command is immediately
transferred to the data set but without being executed there at once.
Syntactical errors in the command are recognized here and supplied to the status reporting system. The
rest of a command line after a syntax error is analysed further if possible and serviced.
If the command recognition recognizes a delimiter or a DCL, it requests the data set to set the
commands in the instrument hardware as well now. Subsequently it is immediately prepared to process
commands again. This means for the command servicing that further commands can already be
serviced while the hardware is still being set ("overlapping execution").
Data Set and Instrument Hardware
Here the expression "instrument hardware" denotes the part of the instrument fulfilling the actual
instrument function - signal generation, measurement etc. The controller is not included.
The instrument data base is a detailed reproduction of the instrument hardware in the software.
IEC-bus setting commands lead to an alteration in the data set. The data base management enters the
new values (e.g. frequency) into the data base, however, only passes them on to the hardware when
requested by the command recognition.
The data are only checked for their compatibility among each other and with the instrument hardware
immediately before they are transmitted to the instrument hardware. If the detection is made that an
execution is not possible, an "execution error" is signalled to the status reporting system. The alteration
of the data base are cancelled, the instrument hardware is not reset.
IEC-bus queries induce the data set management to send the desired data to the output unit.
Status Reporting System
The status reporting system collects information on the instrument state and makes it available to the
output unit on request. The exact structure and function are described in the following section.
1065.6016.12
5.16
E-16
FSE
Instrument Model and Command Processing
Output Unit
The output unit collects the information requested by the controller, which it receives from the data set
management. It processes it according to the SCPI rules and makes it available in the output buffer.
The output buffer has a size of 4096 characters. If the information requested is longer, it is made
available "in portions" without this being recognized by the controller.
If the instrument is addressed as a talker without the output buffer containing data or awaiting data from
the data set management, the output unit sends error message "Query UNTERMINATED" to the status
reporting system. No data are sent on the IEC bus, the controller waits until it has reached its time limit.
This behaviour is specified by SCPI.
Command Sequence and Command Synchronization
What has been said above makes clear that all commands can potentially be carried out overlapping.
Equally, setting commands within one command line are not absolutely serviced in the order in which
they have been received.
In order to make sure that commands are actually carried out in a certain order, each command must
be sent in a separate command line, that is to say, with a separate IBWRT()-call.
In order to prevent an overlapping execution of commands, one of commands *OPC, *OPC? or *WAI
must be used. All three commands cause a certain action only to be carried out after the hardware has
been set and has settled. By a suitable programming, the contoller can be forced to wait for the
respective action to occur (cf. Table 5-1).
Table 5-1 Synchronisation using *OPC, *OPC? and *WAI
Commnd
Action after the hardware has settled
Programming the controller
*OPC
Setting the opteration-complete bit in the ESR
- Setting bit 0 in the ESE
- Setting bit 5 in the SRE
- Waiting for service request (SRQ)
*OPC?
Writing a "1" into the output buffer
Addressing the instrument as a talker
*WAI
Continuing the IEC-bus handshake
Sending the next command
An example as to command synchronization can be found in chapter 7 "Program Examples".
1065.6016.12
5.17
E-16
Status Reporting System
FSE
Status Reporting System
The status reporting system (cf. Fig. 5-3) stores all information on the present operating state of the
instrument, e.g. that the instrument presently carries out an AUTORANGE and on errors which have
occurred. This information is stored in the status registers and in the error queue. The status registers
and the error queue can be queried via IEC bus.
The information is of a hierarchical structure. The register status byte (STB) defined in IEEE 488.2 and
its associated mask register service request enable (SRE) form the uppermost level. The STB receives
its information from the standard event status register (ESR) which is also defined in IEEE 488.2 with
the associated mask register standard event status enable (ESE) and registers STATus:OPERation and
STATus:QUEStionable which are defined by SCPI and contain detailed information on the instrument.
The IST flag ("Individual STatus") and the parallel poll enable register (PPE) allocated to it are also part
of the status reporting system. The IST flag, like the SRQ, combines the entire instrument status in a
single bit. The PPE fulfills an analog function for the IST flag as the SRE for the service request.
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
Fig. 5-3.
Table 5-12 at the end of this chapter comprises the different commands and events causing the status
reporting system to be reset.
Structure of an SCPI Status Register
Each SCPI register consists of 5 parts which each have a width of 16 bits and have different functions
(cf. Fig. 5-2). 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. For example, bit 3 of the STATus:OPERation register is
assigned to the hardware status "wait for trigger" in 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
integer.
15 14 13 12
CONDition part
3 2 1 0
15 14 13 12
PTRansition part
3 2 1 0
15 14 13 12
NTRansition part
3 2 1 0
15 14 13 12
EVENt part
3 2 1 0
to higher-order register
&
&
& & & & &
& & & & & & & & &
+ Sum bit
15 14 13 12
ENABle part
& = logical AND
+ = logical OR
of all bits
3 2 1 0
Fig. 5-2 The status-register model
1065.6016.12
5.18
E-16
FSE
Status Reporting System
CONDition part
The CONDition part is directly written into by the hardware or the sum bit of
the next lower register. Its contents reflects the current instrument status. This
register part can only be read, but not written into or cleared. Its contents is
not affected by reading.
PTRansition part
The Positive-TRansition part acts as an edge detector. When a bit of the
CONDition part is changed from 0 to 1, the associated PTR bit decides
whether the EVENt bit is set to 1.
PTR bit =1: the EVENt bit is set.
PTR bit =0: the EVENt bit is not set.
This part can be written into and read at will. Its contents is not affected by
reading.
NTRansition part
The Negative-TRansition part also acts as an edge detector. When a bit of the
CONDition part is changed from 1 to 0, the associated NTR bit decides
whether the EVENt bit is set to 1.
NTR-Bit = 1: the EVENt bit is set.
NTR-Bit = 0: the EVENt bit is not set.
This part can be written into and read at will. Its contents is not affected by
reading.
With these two edge register parts the user can define which state transition of
the condition part (none, 0 to 1, 1 to 0 or both) is stored in the EVENt part.
EVENt part
The EVENt part indicates whether an event has occurred since the last
reading, it is the "memory" of the condition part. It only indicates events
passed on by the edge filters. It is permanently updated by the instrument.
This part can only be read by the user. During reading, its contents is set to
zero. In linguistic usage this part is often equated with the entire register.
ENABle part
The ENABle part determines whether the associated EVENt bit contributes to
the sum bit (cf. below). Each bit of the EVENt part is ANDed with the
associated ENABle bit (symbol ’&’). The results of all logical operations of this
part are passed on to the sum bit via an OR function (symbol ’+’).
ENABle-Bit = 0: the associated EVENt bit does not contribute to the sum bit
ENABle-Bit = 1: if the associated EVENT bit is "1", the sum bit is set to "1" as
well.
This part can be written into and read by the user at will. Its contents is not
affected by reading.
Sum bit
As indicated above, 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, e.g. a PLL that has not locked, can lead to a service request throughout
all levels of the hierarchy.
Note:
The service request enable register SRE defined in IEEE 488.2 can be taken as ENABle
part of the STB if the STB is structured according to SCPI. By analogy, the ESE can be
taken as the ENABle part of the ESR.
1065.6016.12
5.19
E-16
Status Reporting System
FSE
Overview of the Status Registers
15
14
13
12
11
10
9
8
7
6
5
4
3
2
1
0
& = logical AND
15
14
13
12
11
10
9
8
7
6
5
4
3
2
1
0
= logical OR
of all bits
SRQ
not used
PROGram running
INSTrument summary bit
HCOPy in progress
CORRecting
WAIT for ARM
WAIT for TRIGGER
MEASuring
SWEeping
RANGing
SETTling
CALibrating
not used
Subrange limit attained
Subrange 10
Subrange 9
Subrange 8
Subrange 7
Subrange 6
Subrange 5
Subrange 4
Subrange 3
Subrange 2
Subrange 1
STATus:QUEStionable:TRANsducer
15
14
13
12
11
10
9
8
7
6
5
4
3
2
1
0
STATus:OPERation
-&-&-&-&-&-
SRE
7
6 RQS/MSS
5 ESB
4 MAV
3
2
1
0
15
14
13
12
11
10
9
8
7
6
5
4
3
2
1
0
STB
-&-&-&-&-&-&-
PPE
not used
COMMand warning
TRANsducer break
ACPLimit
SYNC
LMARgin
LIMit
CALibration (= UNCAL)
MODulation
PHASe
FREQuency
TEMPerature
POWer
TIME
CURRent
VOLTage
STATus:QUEStionable
IST flag
’
Error/event
queue
bla
Fig. 5-3
1065.6016.12
Output
buffer
-&-&-&-&-&-&-&-&ESE
7
6
5
4
3
2
1
0
Power on
User Request
Command Error
Execution Error
Device Dependent Error
Query Error
Request Control
Operation Complete
15
14
13
12
11
10
9
8
7
6
5
4
3
2
1
0
15
14
13
12
11
10
9
8
7
6
5
4
3
2
1
0
not used
ALT2 LOWer FAIL (screen B)
ALT2 UPPer FAIL (screen B)
ALT1 LOWer FAIL (screen B)
ALT1 UPPer FAIL (screen B)
ADJ LOWer FAIL (screen B)
ADJ UPPer FAIL (screen B)
ALT2 LOWer FAIL (screen A)
ALT2 UPPer FAIL (screen A)
ALT1 LOWer FAIL (screen A)
ALT1 UPPer FAIL (screen A)
ADJ LOWer FAIL (screen A)
ADJ UPPer FAIL (screen A)
STATus:QUEStionable:ACPLimit
not used
LMARgin 8 FAIL
LMARgin 7 FAIL
LMARgin 6 FAIL
LMARgin 5 FAIL
LMARgin 4 FAIL
LMARgin 3 FAIL
LMARgin 2 FAIL
LMARgin 1 FAIL
STATus:QUEStionable:LMARgin
not used
LO LEVel (screen B)
LO UNLocked (screen B)
LO LEVel (screen A)
LO UNLocked (screen A)b
OVEN COLD
STATus:QUEStionable:FREQuency
15
14
13
12
11
10
9
8
7
6
5
4
3
2
1
0
15
14
13
12
11
10
9
8
7
6
5
4
3
2
1
0
15
14
13
12
11
10
9
8
7
6
5
4
3
2
1
0
not used
CARRier overload
No carrier
SYNC not found
BURSt not found
STATus:QUEStionable:SYNC
not used
LIMit 8 FAIL
LIMit 7 FAIL
LIMit 6 FAIL
LIMit 5 FAIL
LIMit 4 FAIL
LIMit 3 FAIL
LIMit 2 FAIL
LIMit 1 FAIL
STATus:QUEStionable:LIMit
not used
IF_OVerload (screen B)
UNDerload Option B7 (screen B)
OVERload (screen B)
IF_OVerload (screen A)
UNDerload Option B7 (screen A)
OVERload (screen A)
STATus:QUEStionable:POWer
ESR
Overview of the status registers
5.20
E-16
FSE
Status Reporting System
Description of the Status Registers
Status Byte (STB) and Service Request Enable Register (SRE)
The STB is already defined in IEEE 488.2. It provides a rough overview of the instrument status by
collecting the pieces of information of the lower registers. It can thus be compared with the CONDition
part of an SCPI register and assumes the highest level within the SCPI hierarchy. A special feature is
that bit 6 acts as the sum bit of the remaining bits of the status byte.
The STATUS BYTE is read out using the command "*STB?" or a serial poll.
The STB implies the SRE. It corresponds to the ENABle part of the SCPI registers as to its function.
Each bit of the STB is assigned a bit in the SRE. Bit 6 of the SRE is ignored. If a bit is set in the SRE
and the associated bit in the STB changes from 0 to 1, a Service Request (SRQ) is generated on the
IEC bus, which triggers an interrupt in the controller if this is appropriately configured and can be further
processed there.
The SRE can be set using command "*SRE" and read using "*SRE?".
Table 5-2
Meaning of the bits in the status byte
Bit No.
Meaning
2
Error Queue not empty
The bit is set when an entry is made in the error queue.
If this bit is enabled by the SRE, each entry of the error queue generates a Service Request. Thus an error can
be recognized and specified in greater detail by polling the error queue. The poll provides an informative error
message. This procedure is to be recommended since it considerably reduces the problems involved with IECbus control.
3
QUEStionable status sum bit
The bit is set if an EVENt bit is set in the QUEStionable-Status register and the associated ENABle bit is set to
1.
A set bit indicates a questionable instrument status, which can be specified in greater detail by polling the
QUEStionable-Status register.
4
MAV bit (message available)
The bit is set if a message is available in the output buffer which can be read.
This bit can be used to enable data to be automatically read from the instrument to the controller (cf. chapter 7,
program examples).
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 implies an error or an event which can be specified in greater detail by polling the event status
register.
6
MSS bit (master status summary bit)
The bit is set if the instrument triggers a service request. This is the case if one of the other bits of this registers
is set together with its mask bit in the service request enable register SRE.
7
OPERation status register sum bit
The bit is set if an EVENt bit is set in the OPERation-Status register and the associated ENABle bit is set to 1.
A set bit indicates that the instrument is just performing an action. The type of action can be determined by
polling the OPERation-status register.
1065.6016.12
5.21
E-16
Status Reporting System
FSE
IST Flag and Parallel Poll Enable Register (PPE)
By analogy with the SRQ, the IST flag combines the entire status information in a single bit. It can be
queried by means of a parallel poll or using command "*IST?".
The parallel poll enable register (PPE) determines which bits of the STB contribute to the IST flag. The
bits of the STB are ANDed with the corresponding bits of the PPE, with bit 6 being used as well in
contrast to the SRE. The Ist flag results from the ORing of all results. The PPE can be set using
commands "*PRE" and read using command "*PRE?".
Event-Status Register (ESR) and Event-Status-Enable Register (ESE)
The ESR is already defined in IEEE 488.2. It can be compared with the EVENt part of an SCPI register.
The event status register can be read out using command "*ESR?".
The ESE is the associated ENABle part. It can be set using command "*ESE" and read using command
"*ESE?".
Table 5-3
Meaning of the bits in the event status register
Bit No.
Meaning
0
Operation Complete
This bit is set on receipt of the command *OPC exactly when all previous commands have been executed.
1
Request Control
This bit is set if the instrument requests the controller function. This is the case when hardcopy is outputted to a
printer or a plotter via the IEC-bus.
2
Query Error
This bit is set if either the controller wants to read data from the instrument without having send 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 (cf. chapter 9,
Error Messages).
4
Execution Error
This bit is set if a received command is syntactically correct, however, 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 (cf. chapter 9, Error Messages).
5
Command Error
This bit is set if a command which is undefined or syntactically incorrect is received. An error message with a
number between -100 and -200, which denotes the error in greater detail, is entered into the rror queue (cf.
chapter 9, -Error Messages).
6
User Request
This bit is set on pressing the LOCAL key.
7
Power On (supply voltage on)
This bit is set on switching on the instrument.
1065.6016.12
5.22
E-16
FSE
Status Reporting System
STATus:OPERation Register
In the CONDition part, this register contains information on which actions the instrument is being
executing or, in the EVENt part, information on which actions the instrument has executed since the last
reading. It can be read using commands "STATus:OPERation:CONDition?" or "STATus
:OPERation[:EVENt]?".
Table 5-4
Meaning of the bits in the STATus.OPERation register
Bit No.
Meaning
0
CALibrating
This bit is set as long as the instrument is performing a calibration.
1
SETTling
This bit is set as long as the new status is settling after a setting command. It is only set if the settling time is
longer than the command processing time.
2
RANGing
This bit is set as long as the instrument is changing a range (e.g. Autorange).
3
SWEeping
This bit is set while the instrument is performing a sweep.
4
MEASuring
This bit is set while the instrument is performing a measurement.
5
WAIT for TRIGGER
This bit is set as long as the instrument is waiting for a trigger event.
6
WAIT for ARM
This bit is set as long as the instrument is waiting for an arming event.
7
CORRecting
This bit is set while the instrument is performing a correction.
8
HardCOPy in progress
This bit is set while the instrument is printing a hardcopy.
9-12
Device dependent
13
INSTrument Summary Bit
This bit is set when one or more logical instruments is reporting a status message.
14
PROGram running
This bit is set while the instrument is performing a program.
15
This bit is always 0
The FSE supports bits 0 and 8.
1065.6016.12
5.23
E-16
Status Reporting System
FSE
STATus:QUEStionable Register
This register comprises information about indefinite states which may occur if the unit is operated
without meeting the specifications. It can be queried by commands STATus:QUEStionable:
CONDition? and STATus:QUEStionable[:EVENt]?.
Table 5-5
Meaning of bits in STATus:QUEStionable register
Bit No.
Meaning
0
VOLTage
This bit is set if a questionable voltage occurs.
1
CURRent
This bit is set if a questionable current occurs.
2
TIME
This bit is set if a questionable time occurs.
3
POWer
This bit is set if a questionable power occurs (cf. also section "STATus:QUEStionable:POWerRegister")
4
TEMPerature
This bit is set if a questionable temperature occurs.
5
FREQuency
The bit is set if a frequency is questionable (cf. section "STATus:QUEStionable:FREQuency Register")
6
PHASe
The bit is set if a phase value is questionable.
7
MODulation
The bit is set if a modulation is performed questionably.
8
CALibration
^ label "UNCAL")
The bit is set if a measurement is performed uncalibrated (=
9
LIMit (unit-dependent)
This bit is set if a limit value is violated (see also section STATus:QUEStionable:LIMit Register)
10
LMARgin (unit-dependent)
This bit is set if a margin is violated (see also section STATus:QUEStionable:LMARgin Register)
11
SYNC (unit-dependent)
This bit is set if, during measurements with Option B7 (Signal Vector Analysis), the synchronization with
midamble or a successful search for bursts cannot be performed (see also STATus:QUEStionable:SYNC
Register)
12
ACPLimit (unit-dependent)
This bit is set if a limit for the adjacent channel power measurement is violated (see also section
STATus:QUEStionable:ACPLimit Register)
13
TRANsducer break
This bit is set when the limit of the transducer set subrange is attained.
14
COMMand Warning
This bit is set if the instrument ignores parameters when executing a command.
15
This bit is always 0.
The FSE supports bits 3, 5, 7, 8, 9, 10, 11, 12 and 13, bits 7 (MODulation) and 11 (SYNC) only with
option FSE-B7, Vector Signal Analysis’.
1065.6016.12
5.24
E-16
FSE
Status Reporting System
STATus QUEStionable:ACPLimit Register
This register Tcomprises information about the observance of limits during adjacent power
measurements. It can be queried with commands ’STATus:QUEStionable:ACPLimit
:CONDition?’ and ’STATus:QUEStionable:ACPLimit[:EVENt]?’
Table 5-
Meaning of bits in STATus:QUEStionable:ACPLimit register
Bit No.
Meaning
0
ADJ UPPer FAIL(Screen A)
This bit is set if the limit is exceeded in the upper adjacent channel.
1
ADJ LOWer FAIL (Screen A)
This bit is set if the limit is exceeded in the lower adjacent channel.
2
ALT1 UPPer FAIL (Screen A)
This bit is set if the limit is exceeded in the upper 1st alternate channel.
3
ALT1 LOWer FAIL (Screen A)
This bit is set if the limit is exceeded in the lower 1st alternate channel.
4
ALT2 UPPer FAIL (Screen A)
This bit is set if the limit is exceeded in the upper 2nd alternate channel.
5
ALT2 LOWer FAIL (Screen A)
This bit is set if the limit is exceeded in the lower 2nd alternate channel.
6
not used
7
not used
8
ADJ UPPer FAIL (Screen B)
This bit is set if the limit is exceeded in the upper adjacent channel.
9
ADJ LOWer FAIL (Screen B)
This bit is set if the limit is exceeded in the lower adjacent channel.
10
ALT1 UPPer FAIL (Screen B)
This bit is set if the limit is exceeded in the upper 1st alternate channel.
11
ALT1 LOWer FAIL (Screen B)
This bit is set if the limit is exceeded in the lower 1st alternate channel.
12
ALT2 UPPer FAIL (Screen B)
This bit is set if the limit is exceeded in the upper 2nd alternate channel.
13
ALT2 LOWer FAIL (Screen A)
This bit is set if the limit is exceeded in the lower 2nd alternate channel.
14
not used
15
This bit is always 0.
1065.6016.12
5.25
E-16
Status Reporting System
FSE
STATus QUEStionable:FREQuency Register
This register comprises information about the reference and local oscillator.
It can be queried with commands STATus:QUEStionable:FREQuency:CONDition? and "STATus
:QUEStionable:FREQuency[:EVENt]?.
Table 5-6
Meaning of bits in STATus:QUEStionable:FREQuency register
Bit No.
Meaning
0
OVEN COLD
This bit is set if the reference oscillator has not yet attained its operating temperature. ’OCXO’ will then be
displayed.
1
LO UNLocked (Screen A)
This bit is set if the local oscillator no longer locks. ’LO unl’ will then be displayed.
2
LO LEVel (Screen A)
This bit is set if the level of the local oscillator is smaller than the nominal value. ’LO LVL’ will then be displayed.
3
not used
4
not used
5
not used
6
not used
7
not used
8
not used
9
LO UNLocked (Screen B)
This bit is set if the local oscillator no longer locks.’ LO unl’ will then be displayed.
10
LO LEVel (Screen B)
This bit is set if the level of the local oscillator is smaller than the nominal value. ’LO LVL’ will then be displayed.
11
not used
12
not used
13
not used
14
not used
15
This bit is always 0.
1065.6016.12
5.26
E-16
FSE
Status Reporting System
STATus QUEStionable:LIMit Register
This register comprises information about the observance of limit lines. It can be queried with
commands STATus:QUEStionable:LIMit:CONDition? and STATus:QUEStionable:LIMit
[:EVENt]?.
Table 5-7
Meaning of bits in STATus:QUEStionable:LIMit register
Bit No.
Meaning
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
not used
9
not used
10
not used
11
not used
12
not used
13
not used
14
not used
15
This bit is always 0.
1065.6016.12
5.27
E-16
Status Reporting System
FSE
STATus QUEStionable:LMARgin Register
This register comprises information about the observance of limit margins. It can be queried with
commands
STATus:QUEStionable:LMARgin:CONDition?
and
"STATus:QUEStionable
:LMARgin[:EVENt]?.
Table 5-8
Bit No.
0
Meaning of bits in STATus:QUEStionable:LMARgin register
Meaning
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 1 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
not used
9
not used
10
not used
11
not used
12
not used
13
not used
14
not used
15
This bit is always 0.
1065.6016.12
5.28
E-16
FSE
Status Reporting System
STATus QUEStionable:POWer Register
This register comprises all information about possible overloads of the unit.
It can be queried with commands STATus:QUEStionable :POWer:CONDition? and "STATus
:QUEStionable:POWer [:EVENt]?.
Table 5-9
Meaning of bits in STATus:QUEStionable:POWer register
Bit No.
Meaning
0
OVERload (Screen A)
This bit is set if the RF input is overloaded. ’OVLD’ will then be displayed.
1
UNDerload (Screen A) - Option FSE-B7
This bit is set if, during measurements in vector analyzer mode without capture buffer used, the lower level limit
in the IF path is violated.
2
IF_OVerload (Screen A)
This bit is set if the IF path is overloaded. ’IFOVLD’ will then be displayed.
3
not used
4
not used
5
not used
6
not used
7
not used
8
OVERload (Screen B)
This bit is set if the RF input is overloaded. ’OVLD’ will then be displayed.
9
UNDerload (Screen B) - Option FSE-B7
This bit is set if, during measurements without capture buffer used, the lower level limit in the IF path is violated.
10
IF_OVerload (Screen B)
This bit is set if the IF path is overloaded. ’IFOVLD’ will then be displayed.
11
not used
12
not used
13
not used
14
not used
15
This bit is always 0.
1065.6016.12
5.29
E-16
Status Reporting System
FSE
STATus QUEStionable:SYNC Register
This register comprises information about sync and burst events related to Vector Analyzer mode,
option FSE-B7, and to GSM measurements, options FSE-K10/20/30 and FSE-K11/21/31). It can be
queried
with
commands
STATus:QUEStionable:SYNC:CONDition?
and
"STATus
:QUEStionable:SYNC[:EVENt]?.
Table 5-10
Meaning of bits in STATus:QUEStionable:SYNC register
Bit No.
Meaning
0
BURSt not found
This bit is set if a burst was not found.
1
SYNC not found
This bit is set if the sync sequence of midamble was not found.
2
No carrier
This bit is set if the carrier power determined in the pre-measurement is 20 dB belowof the expected signal
power (options FSE-K10/ FSE-K11).
3
Carrier overload
This bit is set if the carrier power determined in the pre-measurement is 4 dB above of the expected signal
power (options FSE-K10/ FSE-K11).
4 to 14
not used
15
This bit is always 0.
The ’SYNC not found’ and ’BURSt not found’ bits are set with all measurements evaluating this
information. The bits are recalculated for each sweep so that they show the current status at the end of
a sweep.
GSM measurements (options FSE-K10 and FSE-K11) carrying along the two bits synchronously with
the sweep:
- CPW Carrier Power activated with ’Sync To Midamble’ (*)
- PVT Power versus Time activated with ’Sync To Midamble’ (*)
- PFE Phase/Frequency Error
- MAC Modulation Accuracy
- TAA Trigger AutoAdjust
* With GMSK modulation, the PVT and CPW measurements do not perform a burst search. The burst search is only active
with 8PSK modulation (EDGE).
The Carrier Overload’ and ’No Carrier’ bits are reset at the beginning of each GSM measurement
(options FSE-K10 and FSE-K11) and, if required, set at the end of the pre-measurement. If single-step
measurements (CPW) are performed, the bits are set after the initial step and reset again at the
beginning of the next.
GSM measurements with bit setting as required:
- CPW Carrier Power (first step only, measurement of full power)
- PVT Power versus Time (setting possible after each of the two pre-measurements)
- MOD Modulation Spectrum
- TRA Transient Spectrum (**)
** With FSE-K10 (mobile) and power coupling OFF selected, a pre-measurement is not performed. Measuring the carrier
power is therefore not possible and so the two bits are not set.
1065.6016.12
5.30
E-16
FSE
Status Reporting System
STATus QUEStionable:TRANsducer Register
This register indicates that a transducer hold point is attained (bit 15) and what range is to be swept next
(bit 0 to 10). The sweep can be continued with command INITiate2:CONMeasure.
It can be queried with commands STATus:QUEStionable:TRANsducer:CONDition? and "STATus
:QUEStionable:TRANsducer[:EVENt]?.
Table 5-11
Meaning of bits in STATus:QUEStionable:TRANsducer register
Bit No.
Meaning
0
Range 1
This bit is set when subrange 1 is attained.
1
Range 2
This bit is set when subrange 2 is attained.
2
Range 3
This bit is set when subrange 3 is attained.
3
Range 4
This bit is set when subrange 4 is attained.
4
Range 5
This bit is set when subrange 1 is attained.
5
Range 6
This bit is set when subrange 6 is attained.
6
Range 7
This bit is set when subrange 7 is attained.
7
Range 8
This bit is set when subrange 8 is attained.
8
Range 9
This bit is set when subrange 9 is attained.
9
Range 10
This bit is set when subrange 10 is attained.
10
not used
11
not used
12
not used
13
not used
14
Subrange limit
This bit is set when the transducer is at the point of changeover from one range to another.
15
This bit is always 0.
1065.6016.12
5.31
E-16
Status Reporting System
FSE
Application of the Status Reporting Systems
In order to be able to effectively use the status reporting system, the information contained there must
be transmitted to the controller and further processed there. There are several methods which are
represented in the following. Detailed program examples are to be found in chapter 7, Program
Examples.
Service Request, Making Use of the Hierarchy Structure
Under certain circumstances, the instrument can send a service request (SRQ) to the controller. Usually
this service request initiates an interrupt at the controller, to which the control program can react with
corresponding actions. As evident from Fig. 5-3, 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 corresponding setting of the ENABle parts
of the status registers can achieve that arbitrary bits in an arbitrary status register initiate an SRQ. In
order to make use of the possibilities of the service request, all bits should be set to "1" in enable
registers SRE and ESE.
Examples (cf. Fig. 5-3 and chapter 7, Program Examples, as well):
Use of command "*OPC" to generate an SRQ at the end of a sweep.
½ Set bit 0 in the ESE (Operation Complete)
½ Set bit 5 in the SRE (ESB)?
After its settings have been completed, the instrument generates an SRQ.
The SRQ is the only possibility for the instrument to become active on its own. Each controller program
should set the instrument such that a service request is initiated in the case of malfunction. The program
should react appropriately to the service request. A detailed example for a service request routine is to
be found in chapter 7, Program Examples.
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 has already
been defined in IEEE 488.1 and used to be the only standard possibility for different instruments to poll
the status byte. The method also works with instruments which do not adhere to SCPI or IEEE 488.2.
The quick-BASIC command for executing a serial poll is "IBRSP()". Serial poll is mainly used to obtain a
fast overview of the state of several instruments connected to the IEC bus.
1065.6016.12
5.32
E-16
FSE
Status Reporting System
Parallel Poll
In a parallel poll, up to eight instruments are simultaneously requested by the controller by means of 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 logically "0" or "1". By analogy to the SRE register which determines under which
conditions an SRQ is generated, there is a parallel poll enable register (PPE) which is ANDed with the
STB bit by bit as well considering bit 6. The results are ORed, the result is then sent (possibly inverted)
as a response in the parallel poll of the controller. The result can also be queried without parallel poll by
means of command "*IST".
The instrument first has to be set for the parallel poll using quick-BASIC command "IBPPC()". 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 "IBRPP()".
The parallel-poll method is mainly used in order to quickly find out after an SRQ which instrument has
sent the service request if there are many instruments connected to the IEC bus. To this effect, SRE
and PPE must be set to the same value. A detailed example as to the parallel poll is to be found in
chapter 7, Program Examples.
Query by Means of Commands
Each part of every status register can be read by means of queries. The individual commands are
indicated in the detailed description of the registers. What is returned is always a number which
represents the bit pattern of the register queried. Evaluating this number is effected by the controller
program.
Queries are usually used after an SRQ in order to obtain more detailed information on the cause of the
SRQ.
Error-Queue Query
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 which can be looked at in the ERROR menu via manual control
or queried via the IEC bus using command "SYSTem:ERRor?". Each call of "SYSTem:ERRor?"
provides an entry from the error queue. If no error messages 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. 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.
1065.6016.12
5.33
E-16
Status Reporting System
FSE
Resetting Values of the Status Reporting System
Table 5-12 comprises the different commands and events causing the status reporting system to be
reset. None of the commands, except for *RST and SYSTem:PRESet influences the functional
instrument settings. In particular, DCL does not change the instrument settings.
Table 5-12
Resetting instrument functions
Event
Switching on supply
voltage
Power-On-StatusClear
Effect
0
DCL,SDC
(Device Clear,
Selected Device
Clear)
*RST or
SYSTem:PRESet
STATus:PRESet
*CLS
1
Clear STB,ESR
yes
yes
Clear SRE,ESE
yes
Clear PPE
yes
Clear EVENTt parts of the
registers
yes
yes
Clear Enable parts of all
OPERation and
QUEStionable registers,
Fill Enable parts of all
other registers with "1".
yes
yes
Fill PTRansition parts with
"1" ,
Clear NTRansition parts
yes
yes
Clear error queue
yes
yes
yes
Clear output buffer
yes
yes
yes
1)
1)
1)
Clear command
processing and input
buffer
yes
yes
yes
1) Every command being the first in a command line, i.e., immediately following a
clears the output buffer.
1065.6016.12
5.34
E-16
FSE
Contents - Description of Commands
Contents - Chapter 6 "Remote Control - Description
of Commands"
6 Description of Commands.................................................................................. 6.1
Notation ............................................................................................................................................ 6.1
Common Commands....................................................................................................................... 6.4
ABORt Subsystem ........................................................................................................................... 6.8
CALCulate Subsystem..................................................................................................................... 6.8
CALCulate:DELTamarker Subsystem ..................................................................................... 6.9
CALCulate:DLINe Subsystem ............................................................................................... 6.15
CALCulate:FEED Subsystem ................................................................................................ 6.18
CALCulate:FORMat and CALCulate:FSK Subsystems......................................................... 6.19
CALCulate:LIMit Subsystem.................................................................................................. 6.20
CALCulate:MARKer Subsystem ............................................................................................ 6.36
CALCulate:MATH Subsystem ............................................................................................... 6.61
CALCulate:X and CALCulate:UNIT Subsystem .................................................................... 6.62
CALibration Subsystem ................................................................................................................ 6.63
CONFigure Subsystem.................................................................................................................. 6.65
CONFigure:BTS Subsystem.................................................................................................. 6.65
CONFigure:BURSt Subsystem.............................................................................................. 6.73
CONFigure:MS Subsystem ................................................................................................... 6.77
CONFigure:SPECtrum Subsystem........................................................................................ 6.85
CONFigure:SPURious Subsystem ........................................................................................ 6.87
DIAGnostic Subsystem ................................................................................................................. 6.89
DISPlay Subsystem........................................................................................................................ 6.91
FETCh Subsystem ....................................................................................................................... 6.101
FETCh:BURSt Subsystem .................................................................................................. 6.101
FETCh:PTEMplate Subsystem............................................................................................ 6.111
FETCh:SPECtrum Subsystem ............................................................................................ 6.112
FETCh:SPURious Subsystem ............................................................................................. 6.115
FORMat Subsystem ..................................................................................................................... 6.117
HCOPy Subsystem ...................................................................................................................... 6.119
INITiate Subsystem...................................................................................................................... 6.125
INPut Subsystem ......................................................................................................................... 6.127
INSTrument Subsystem .............................................................................................................. 6.130
MMEMory Subsystem.................................................................................................................. 6.132
OUTPut Subsystem ..................................................................................................................... 6.143
READ Subsystem......................................................................................................................... 6.145
READ:BURSt Subsystem .................................................................................................... 6.145
READ:SPECtrum Subsystem .............................................................................................. 6.159
READ:SPURious Subsystem .............................................................................................. 6.161
1065.6016.12
I-6.1
E-16
Contents - Description of Commands
FSE
SENSe Subsystem ....................................................................................................................... 6.163
SENSe:ADEMod Subsystem............................................................................................... 6.163
SENSe:AVERage Subsystem ............................................................................................. 6.165
SENSe:BANDwidth Subsystem ........................................................................................... 6.167
SENSe:CORRection-Subsystem......................................................................................... 6.171
SENSe:DETector Subsystem .............................................................................................. 6.181
SENSe:DDEMod Subsystem............................................................................................... 6.182
SENSe:FILTer Subsystem .................................................................................................. 6.190
SENSe:FREQuency Subsystem.......................................................................................... 6.193
SENSe:MIXer - Subsystem ................................................................................................. 6.197
SENSe:MSUMmary Subsystem .......................................................................................... 6.201
SENSe:POWer Subsystem ................................................................................................. 6.203
SENSe:ROSCillator Subsystem .......................................................................................... 6.206
SENSe:SWEep Subsystem................................................................................................. 6.207
SENSe:TV Subsystem......................................................................................................... 6.211
SOURce Subsystem .................................................................................................................... 6.212
STATus Subsystem ..................................................................................................................... 6.214
SYSTem Subsystem .................................................................................................................... 6.226
TRACe Subsystem ....................................................................................................................... 6.233
TRIGger Subsystem..................................................................................................................... 6.235
UNIT Subsystem .......................................................................................................................... 6.240
Alphabetical List of Commands ................................................................................................. 6.241
Table of Softkeys with IEC/IEEE-Bus Command Assignment ................................................ 6.259
Basic Instrument - Signal Analysis Mode ............................................................................ 6.259
FREQUENCY Key Group.......................................................................................... 6.259
LEVEL Key Group ..................................................................................................... 6.261
INPUT Key................................................................................................................. 6.262
MARKER Key Group ................................................................................................. 6.263
LINES Key Group ...................................................................................................... 6.267
TRACE Key Group .................................................................................................... 6.269
SWEEP Key Group ................................................................................................... 6.271
Basic Instrument - General Device Settings........................................................................ 6.274
DATA VARIATION Key Group .................................................................................. 6.274
SYSTEM Key Group.................................................................................................. 6.274
CONFIGURATION Key Group .................................................................................. 6.277
STATUS Key Group .................................................................................................. 6.279
HARDCOPY Key Group ............................................................................................ 6.280
MEMORY Key Group ................................................................................................ 6.281
USER Key ................................................................................................................. 6.283
Operating Mode Vector-Signal Analyzer (Option FSE-B7) .................................................. 6.284
CONFIGURATION Key Group - Digital Demodulation.............................................. 6.284
CONFIGURATION Key Group - Analog Demodulation ............................................ 6.288
FREQUENCY Key Group.......................................................................................... 6.289
LEVEL Key Group ..................................................................................................... 6.290
INPUT Key................................................................................................................. 6.291
MARKER Key Group ................................................................................................. 6.291
LINES Key Group ...................................................................................................... 6.293
1065.6016.12
I-6.2
E-16
FSE
Contents - Description of Commands
TRACE Key Group .................................................................................................... 6.294
SWEEP Key Group ................................................................................................... 6.295
TRIGGER Key Group - Digital Demodulation ........................................................... 6.295
TRIGGER Key Group - Analog Demodulation .......................................................... 6.296
Operating Mode Tracking Generator (Option FSE-B8 to B11)............................................ 6.297
CONFIGURATION Key Group .................................................................................. 6.297
Operating Mode TV Demodulation (Option FSE-B3) .......................................................... 6.298
CONFIGURATION Key Group .................................................................................. 6.298
SWEEP Key Group ................................................................................................... 6.298
Operating Mode GSM BTS Analyzer (Option FSE-K11) ..................................................... 6.299
CONFIGURATION Key Group .................................................................................. 6.299
Operating Mode GSM MS Analyzer (Option FSE-K10) ....................................................... 6.309
CONFIGURATION Key Group .................................................................................. 6.309
External Mixer Output (Option FSE-B21) ............................................................................ 6.319
INPUT Key Group...................................................................................................... 6.319
1065.6016.12
I-6.3
E-16
Contents - Description of Commands
1065.6016.12
FSE
I-6.4
E-16
FSE
Notation
6 Description of Commands
Notation
In the following sections, all commands implemented in the instrument are first listed in tables and then
described in detail, separated according to the command system. The notation corresponds to the one
of the SCPI standards to a large extent. The SCPI conformity information can be taken from the
individual description of the commands.
Table of Commands
Command:
Parameter:
Unit:
Remark:
Indentations
In the command column, the table provides an overview of the commands
and their hierarchical arrangement (see indentations).
The parameter column indicates the requested parameters together with
their specified range.
The unit column indicates the basic unit of the physical parameters.
In the remark column an indication is made on:
– whether the command does not have a query form,
– whether the command has only one query form
– whether this command is implemented only with a certain option of the
instrument
The different levels of the SCPI command hierarchy are represented in the
table by means of indentations to the right. The lower the level is, the
farther the indentation to the right is. Please observe that the complete
notation of the command always includes the higher levels as well.
Example: :SENSe:FREQuency:CENTer is represented in the table as
follows:
:SENSe
:FREQuency
:CENTer
Individual description
1065.6016.12
first level
second level
third level
In the individual description, the complete notation of the command is
given. An example for each command, the *RST value and the SCPI
information is written out at the end of the individual description.
The modes for which a command can be used are indicated by the
following abbreviations:
A
A-F
A-Z
VA
VA-D
VA-A
BTS
MS
Spectrum analysis
Spectrum analysis - frequency domain only
Spectrum analysis - time domain only (zero span)
Vector signal analysis (option FSE-B7)
Vector signal analysis - digital demodulation (option FSE-B7)
Vector signal analysis - analog demodulation (option FSE-B7)
GSM BTS analysis (option FSE-K11)
GSM MS analysis (option FSE-K10)
Note:
The spectrum analysis (analyzer) mode is implemented in the
basic unit. For the other modes, the corresponding options are
required.
6.1
E-16
Notation
FSE
Upper/lower case notation Upper/lower case letters serve to mark the long or short form of the key
words of a command in the description (see Chapter 5). The instrument
itself does not distinguish between upper and lower case letters.
Special characters
|
A selection of key words with an identical effect exists for several
commands. These key words are indicated in the same line, they are
separated by a vertical stroke. Only one of these key words has to be
indicated in the header of the command. The effect of the command is
independent of which of the key words is indicated.
Example:SENSe:FREQuency:CW|:FIXed
The two following commands of identical meaning can be
formed. They set the frequency of the constantly frequent signal
to 1 kHz:
SENSe:FREQuency:CW 1E3 = SENSe:FREQuency:FIXed 1E3
A vertical stroke in indicating the parameters marks alternative possibilities
in the sense of "or". The effect of the command is different, depending on
which parameter is entered.
Example:Selection of the parameters for the command
INPut:COUPling
AC | DC
If parameter AC is selected, only the AC content is fed through, in
the case of DC, the DC as well as the AC content.
[ ]
Key words in square brackets can be omitted when composing the header
(cf. Chapter 5, Section "Optional Keywords"). The full command length
must be accepted by the instrument for reasons of compatibility with the
SCPI standards.
Parameters in square brackets can optionally be incorporated in the
command or omitted as well.
{ }
Parameters in braces can optionally be incorporated in the command either
not at all, once or several times.
Description of parameters Due to the standardization, the parameter section of SCPI commands
consists always of the same syntactical elements. SCPI has specified a
series of definitions therefore, which are used in the tables of commands.
In the tables, these established definitions are indicated in angled brackets
(<...>) and will be briefly explained in the following (see also Chapter 5,
Section "Parameters").
1065.6016.12
This indication refers to parameters which can adopt two states, "on" and
"off". The "off" state may either be indicated by the keyword OFF or by the
numeric value 0, the "on" state is indicated by ON or any numeric value
other than zero. Parameter queries are always returned the numeric value
0 or 1.
6.2
E-16
FSE
Notation
These indications mark parameters which may be entered as numeric
values or be set using specific keywords (character data).
The keywords given below are permitted:
MINimum This keyword sets the parameter to the smallest possible
value.
MAXimum This keyword sets the parameter to the largest possible value.
DEFault
This keyword is used to reset the parameter to its default
value.
UP
This keyword increments the parameter value.
DOWN
This keyword decrements the parameter.
The numeric values associated to MAXimum/MINimum/DEFault can be
queried by adding the corresponding keywords to the command. They
must be entered following the quotation mark.
Example:SENSe:FREQuency:CENTer? MAXimum
returns the maximum possible numeric value of the center frequency as
result.
This keyword is provided for commands the parameters of which consist of
a binary data block.
1065.6016.12
6.3
E-16
Common Commands
FSE
Common Commands
The common commands are taken from the IEEE 488.2 (IEC 625-2) standard. Same commands have
the same effect on different devices. The headers of these commands consist of an asterisk "*" followed
by three letters. Many common commands refer to the status reporting system which is described in
detail in Chapter 5.
Command
Designation
Parameter
Remark
*CAL?
Calibration Query
query only
*CLS
Clear Status
no query
*ESE
Event Status Enable
0 to 255
*ESR?
Standard Event Status Query
0 to 255
query only
*IDN?
Identification Query
query only
*IST?
Individual Status Query
0 to 255
query only
*OPC
Operation Complete
*OPT?
Option Identification Query
*PCB
Pass Control Back
0 to 30
*PRE
Parallel Poll Register Enable
0 to 255
*PSC
Power On Status Clear
0|1
*RST
Reset
*SRE
Service Request Enable
*STB?
Status Byte Query
query only
*TRG
Trigger
no query
*TST?
Self Test Query
query only
*WAI
Wait to continue
no query
query only
no query
no query
0 to 255
*CAL?
CALIBRATION QUERY triggers a calibration of the instrument and subsequently query the
calibration status. Any responses > 0 indicate errors.
*CLS
CLEAR STATUS sets the status byte (STB), the standard event register (ESR) and the EVENt-part
of the QUEStionable and the OPERation register to zero. The command does not alter the mask and
transition parts of the registers. It clears the output buffer.
1065.6016.12
6.4
E-16
FSE
Common Commands
*ESE 0 to 255
EVENT STATUS ENABLE sets the event status enable register to the value indicated. Query *ESE?
returns the contents of the event status enable register in decimal form.
*ESR?
STANDARD EVENT STATUS QUERY returns the contents of the event status register in decimal
form (0 to 255) and subsequently sets the register to zero.
*IDN?
IDENTIFICATION QUERY queries the instrument identification.
The instrument identification consists of the following elements which are separated by commas:
Manufacturer
Device (analyzer model)
Serial number of the instrument
Firmware version number
Example: "Rohde&Schwarz, FSEA30, 825082/007, 1.67"
*IST?
INDIVIDUAL STATUS QUERY returns the contents of the IST flag in decimal form (0 | 1). The IST
flag is the status bit which is sent during a parallel poll (cf. Chapter 5).
*OPC
OPERATION COMPLETE sets bit 0 in the event status register when all preceding commands have
been executed. This bit can be used to initiate a service request (cf. Chapter 5).
*OPC?
OPERATION COMPLETE QUERY writes message "1" into the output buffer as soon as all
preceding commands have been executed (cf. Chapter 5).
1065.6016.12
6.5
E-16
Common Commands
FSE
*OPT?
OPTION IDENTIFICATION QUERY queries the options included in the instrument and returns a list
of the options installed. The options are separated from each other by means of commas.
Position
Option
1
FSE-B3
TV Demodulator
2
FSE-B4
Low Phase Noise & OCXO
3
FSE-B5
FFT-Filter
4
reserved
5
FSE-B7
Vector Signal Analysis
6
FSE-B8
Tracking Generator 3.5 GHz
7
FSE-B9
Tracking Generator 3.5 GHz with I/Q modulator
8
FSE-B10
Tracking Generator 7 GHz
9
FSE-B11
Tracking Generator 7 GHz with I/Q modulator
10
FSE-B12
Output Attenuator for Tracking Generator
11
FSE-B13
1-dB Attenuator
12
13
reserved
FSE-B15
14 to 18
19
reserved
FSE-B21
20 to 21
22
controller option
External Mixer Output
reserved
FSE-B24
24 to 25
Frequency Extension to 44GHz
reserved
26
FSE-K10
GSM Test Software, Mobile
27
FSE-K11
GSM Test Software, Base Station
29
FSE-K20
GSM Test Software, Edge Mobile
30
FSE-K21
GSM Test Software, EDGE Base Station
31
FSE-K30
GSM Test Software, 850 GHz band Mobile
31
FSE-K31
GSM Test Software, 850 GHz band Base Station
Example: 0, FSE-B4, 0, 0, FSE-B7, 0, 0, 0, FSE-B11, FSE-B12, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,..
*PCB 0 to 30
PASS CONTROL BACK indicates the controller address which the IEC-bus control is to be returned
to after termination of the triggered action.
*PRE 0 to 255
PARALLEL POLL REGISTER ENABLE sets parallel poll enable register to the value indicated.
Query *PRE? returns the contents of the parallel poll enable register in decimal form.
1065.6016.12
6.6
E-16
FSE
Common Commands
*PSC 0 | 1
POWER ON STATUS CLEAR determines whether the contents of the ENABle registers is
maintained or reset in switching on.
*PSC = 0
causes the contents of the status registers to be maintained. Thus a service request
can be triggered in switching on in the case of a corresponding configuration of status
registers ESE and SRE.
*PSC = 0
resets the registers.
Query *PSC? reads out the contents of the power-on-status-clear flag. The response can be 0 or 1.
*RST
RESET sets the instrument to a defined default status. The command essentially corresponds to
pressing the [PRESET] key. The default setting is indicated in the description of the commands.
*SRE 0 to 255
SERVICE REQUEST ENABLE sets the service request enable register to the value indicated. Bit 6
(MSS mask bit) remains 0. This command determines under which conditions a service request is
triggered. Query *SRE? reads the contents of the service request enable register in decimal form. Bit
6 is always 0.
*STB?
READ STATUS BYTE QUERY reads out the contents of the status byte in decimal form.
*TRG
TRIGGER triggers a measurement. This command corresponds to INITiate:IMMediate (cf.
Section "TRIGger subsystem", as well).
*TST?
SELF TEST QUERY triggers all selftests of the instrument and outputs an error code in decimal
form.
*WAI
WAIT-to-CONTINUE only permits the servicing of the subsequent commands after all preceding
commands have been executed and all signals have settled (cf. Chapter 5 and "*OPC" as well).
1065.6016.12
6.7
E-16
ABORt / CALCulate Subsystem
FSE
ABORt Subsystem
The ABORt subsystem contains the commands for aborting triggered actions. An action can be
triggered again immediately after being aborted. All commands trigger events which is why they are not
assigned any *RST value.
COMMAND
PARAMETERS
ABORt
--
UNIT
--
COMMENT
no query
:ABORt
This command aborts a current measurement and resets the trigger system.
Example:
"ABOR;INIT:IMM"
Features:
*RST value:
SCPI:
Modes:
A, VA, BTS, MS
0
conforming
CALCulate Subsystem
The CALCulate subsystem contains commands for converting instrument data, transforming and
carrying out corrections. These functions are carried out subsequent to data acquistion, i.e., following
the SENSe subsystem.
In the split-screen representation, a distinction is made between CALCulate1 and CALCulate2:
^ screen A;
CALCulate1 =
^ screen B
CALCulate2 =
For setting REAL/IMAG PART in Vector Analyzer mode a distinction is also made between CALCulate3
and CALCulate4 in the split-screen representation:
^ screen C;
CALCulate3 =
^ screen D
CALCulate4 =
1065.6016.12
6.8
E-16
FSE
CALCulate Subsystem
CALCulate:DELTamarker Subsystem
The CALCulate:DELTamarker subsystem checks the delta-marker functions in the instrument.
COMMAND
PARAMETERS
CALCulate<1|2>
:DELTamarker<1 to 4>
[:STATe]
:MODE
:AOFF
:TRACe
:X
:RELative?
:Y?
:MAXimum
[:PEAK]
:APEak
:NEXT
:RIGHt
:LEFT
:MINimum
[:PEAK]
:NEXT
:RIGHt
:LEFT
:FUNCtion
:FIXed
[:STATe]
:RPOint
:Y
:OFFSet
:X
:PNOise
[:STATe]
:RESult?
:STEP
[:INCRement]
:AUTO
UNIT
COMMENT
ABSolute|RELative
--
---
-HZ | S | SYM
---
query only
query only
------
------
no query
no query (vector signal analysis)
no query
no query
no query
-----
-----
no query
no query
no query
no query
no query
DBM
DB
HZ |S | SYM
--
--
HZ |S | SYM
--
query only
:CALCulate<1|2>:DELTamarker<1 to 4>[:STATe] ON | OFF
This command switches on or off the selected delta marker. If no indication is made, delta marker 1
is selected automatically.
Example:
":CALC:DELT3 ON"
Features:
*RST value:
SCPI:
Modes:
A, VA, BTS, MS
1065.6016.12
OFF
device-specific
6.9
E-16
CALCulate Subsystem
FSE
:CALCulate<1|2>:DELTamarker<1 to 4>:MODE ABSolute | RELative
This command switches over between relative and absolute input of frequency of the delta marker.
Example:
":CALC:DELT:MODE ABS"
Features:
*RST value:
SCPI:
Modes:
A, VA, BTS, MS
REL
device-specific
In the RELative mode, the frequency of the delta marker is programmed relative to the reference
marker. In the ABSolute mode, the frequency is defined by the absolute values.
:CALCulate<1|2>:DELTamarker<1 to 4>:AOFF
This command switches off all active delta markers.
Example:
":CALC:DELT:AOFF"
Features:
*RST value:
SCPI:
Modes:
A, VA, BTS, MS
device-specific
:CALCulate<1|2>:DELTamarker<1 to 4>:TRACe 1 to 4
This command assigns the selected delta marker to the indicated measuring curve.
Example:
":CALC:DELT3:TRAC 2"
Features:
*RST value:
SCPI:
Modes:
A, VA, BTS, MS
device-specific
:CALCulate<1|2>:DELTamarker<1 to 4>:X
0 to MAX (frequency | sweep time | symbols)
This command positions the selected delta marker to the indicated frequency (span > 0) or time
(span = 0). The query always returns the absolute value of frequency or time.
Example:
":CALC:DELT:X
Features:
*RST value:
SCPI:
Modes:
A, VA, BTS, MS
10.7MHz"
device-specific
The SYM unit is only valid in Vector Signal Analysis mode.
:CALCulate<1|2>:DELTamarker<1 to 4>:X:RELative?
This command queries the frequency (span > 0) or time (span = 0) of the selected delta marker
relative to the reference marker.
Example:
":CALC:DELT:X:REL?"
Features:
*RST value:
SCPI:
Modes:
A, VA, BTS, MS
1065.6016.12
device-specific
6.10
E-16
FSE
CALCulate Subsystem
:CALCulate<1|2>:DELTamarker<1 to 4>:Y?
This command queries the value of the selected marker.
Example:
":CALC:DELT:Y?"
Features:
*RST value:
SCPI:
Modes:
A, VA, BTS, MS
device-specific
In complex presentations (vector signal analysis - polar diagrams), the real and the imaginary
component as well as magnitude and phase are output separated by a comma.
:CALCulate<1|2>:DELTamarker<1 to 4>:MAXimum[:PEAK]
This command positions the delta marker to the current maximum value in the trace memory.
Example:
":CALC:DELT:MAX"
Features:
*RST value:
SCPI:
Modes:
A, VA, BTS, MS
device-specific
This command is an event which is why it is not assigned an *RST value and has no query.
:CALCulate<1|2>:DELTamarker<1 to 4>:MAXimum:APEak
This command positions the delta marker to the maximum absolute value of the trace.
Example:
":CALC:DELT:MAX:APE"
Features:
*RST value:
SCPI:
Modes:
VA
device-specific
This command is an event which is why it is not assigned an *RST value and has no query.
:CALCulate<1|2>:DELTamarker<1 to 4>:MAXimum:NEXT
This command positions the delta marker to the next smaller maximum value in the trace memory.
Example:
":CALC:DELT:MAX:NEXT"
Features:
*RST value:
SCPI:
Modes:
A, BTS, MS
device-specific
This command is an event which is why it is not assigned an *RST value and has no query.
:CALCulate<1|2>:DELTamarker<1 to 4>:MAXimum:RIGHt
This command positions the delta marker to the next smaller maximum value to the right of the
current value (i.e., in ascending X direction) in the trace memory.
Example:
":CALC:DELT:MAX:RIGH"
Features:
*RST value:
SCPI:
Modes:
A, BTS, MS
device-specific
This command is an event which is why it is not assigned an *RST value and has no query.
1065.6016.12
6.11
E-16
CALCulate Subsystem
FSE
:CALCulate<1|2>:DELTamarker<1 to 4>:MAXimum:LEFT
This command positions the delta marker to the next smaller maximum value to the left of the
current value (i.e., in descending X direction) in the trace memory.
Example:
":CALC:DELT:MAX:LEFT"
Features:
*RST value:
SCPI:
Modes:
A, BTS, MS
Modes:
R, A
device-specific
This command is an event which is why it is not assigned an *RST value and has no query.
:CALCulate<1|2>:DELTamarker<1 to 4>:MINimum[:PEAK]
This command positions the delta marker to the current minimum value in the trace memory.
Example:
":CALC:DELT:MIN"
Features:
*RST value:
SCPI:
Modes:
A, VA, BTS, MS
device-specific
This command is an event which is why it is not assigned an *RST value and has no query.
:CALCulate<1|2>:DELTamarker<1 to 4>:MINimum:NEXT
This command positions the delta marker to the next higher minimum value in the trace memory.
Example:
":CALC:DELT:MIN:NEXT"
Features:
*RST value:
SCPI:
Modes:
A, BTS, MS
device-specific
This command is an event which is why it is not assigned an *RST value and has no query.
:CALCulate<1|2>:DELTamarker<1 to 4>:MINimum:RIGHt
This command positions the delta marker to the next higher minimum value to the right of the current
value (ie in ascending X direction).
Example:
":CALC:DELT:MIN:RIGH"
Features:
*RST value:
SCPI:
Modes:
A, BTS, MS
device-specific
This command is an event which is why it is not assigned an *RST value and has no query.
:CALCulate<1|2>:DELTamarker<1 to 4>:MINimum:LEFT
This command positions the delta marker to the next higher minimum value to the left of the current
value (ie in descending X direction).
Example:
":CALC:DELT:MIN:LEFT"
Features:
*RST value:
SCPI:
Modes:
A, BTS, MS
device-specific
This command is an event which is why it is not assigned an *RST value and has no query.
1065.6016.12
6.12
E-16
FSE
CALCulate Subsystem
:CALCulate<1|2>:DELTamarker<1 to 4>:FUNCtion:FIXed[:STATe] ON | OFF
This command switches the relative measurement to a fixed reference value on or off.
Example:
":CALC:DELT:FUNC:FIX ON"
Features:
*RST value:
SCPI:
Modes:
A, VA-D, BTS, MS
OFF
device-specific.
The reference value is independent of the current trace.
:CALCulate<1|2>:DELTamarker<1 to 4>:FUNCtion:FIXed:RPOint:Y
This command defines a new fixed reference value for the relative measurement.
Example:
":CALC:DELT:FUNC:FIX:RPO:Y -10dBm"
Features:
*RST value:
SCPI:
Modes:
A, VA
- (FUNction:FIXed[:STATe] is set to OFF)
device-specific
The reference value is independent of the current trace.
:CALCulate<1|2>:DELTamarker<1 to 4>:FUNCtion:FIXed:RPOint:Y:OFFSet
This command defines an additional level offset for the relative measurement.
Example:
":CALC:DELT:FUNC:FIX:RPO:Y:OFFS 10dB"
Features:
*RST value:
SCPI:
Modes:
A, VA
0 dB
device-specific
The level offset is included in the output of the level value.
:CALCulate<1|2>:DELTamarker<1 to 4>:FUNCtion:FIXed:RPOint:X
This command defines the new fixed reference frequency, time or symbols for the relative
measurement.
Example:
":CALC:DELT:FUNC:FIX:RPO:X 10.7MHz"
Features:
*RST value:
SCPI:
Mode:
A
- (FUNction:FIXed[:STATe] is set to OFF)
device-specific
The reference value is independent of the current trace. With span = 0, the reference time, otherwise
the reference frequency is defined.
:CALCulate<1|2>:DELTamarker<1 to 4>:FUNCtion:PNOise[:STATe] ON | OFF
This command switches the measurement of the phase noise on or off.
Example:
":CALC:DELT:FUNC:PNO ON"
Features:
*RST value:
SCPI:
Mode:
A
OFF
device-specific
When the phase noise is measured, the correction values for the bandwidth and the log amplifier are
automatically considered. The measurement uses the reference values defined by
FUNCtion:FIXed:RPOint:X or :Y.
1065.6016.12
6.13
E-16
CALCulate Subsystem
FSE
:CALCulate<1|2>:DELTamarker<1 to 4>:FUNCtion:PNOise:RESult?
This command queries the result of the phase noise measurement.
Example:
":CALC:DELT:FUNC:PNO:RES?"
Features:
*RST value:
SCPI:
Modes:
A, BTS, MS
device-specific
This command is only a query which is why it is not assigned an *RST value.
:CALCulate<1|2>:DELTamarker<1 to 4>:STEP[:INCRement]
This command defines the delta marker step width.
Example:
":CALC:DELT:STEP 10kHz"
":CALC:DELT:STEP 5ms"
Features:
*RST value:
SCPI:
Mode:
A
(frequency domain)
(time domain)
- (STEP is set to AUTO)
device-specific
:CALCulate<1|2>:DELTamarker<1 to 4>:STEP:AUTO ON | OFF
This command switches the automatic adaptation of the marker step width on or off.
Example:
":CALC:DELT:STEP:AUTO OFF"
Features:
*RST value:
SCPI:
Mode:
A
ON
device-specific
With AUTO ON, the step width is 10% of the span.
1065.6016.12
6.14
E-16
FSE
CALCulate Subsystem
CALCulate:DLINe Subsystem
The CALCulate:DLINe subsystem checks the display lines in the instrument, i.e., the level, frequency
and time lines (depending on the X-axis) as well as threshold and reference lines.
COMMAND
CALCulate<1|2>
:DLINe<1|2>
PARAMETERS
:STATe
:THReshold
:STATe
:CTHReshold
:STATe
:RLINe
:STATe
:FLINe<1|2>
:STATe
:TLINe<1|2>
:STATe
UNIT
COMMENT
DBM | DB | DEG | RAD | S |
HZ | PCT
DBM | DB | DEG | RAD | S |
HZ | PCT
DBM | DB | DEG | RAD | S |
HZ | PCT
DBM | DB | DEG | RAD | S |
HZ | PCT
HZ
S | SYM
:CALCulate<1|2>:DLINe<1|2> MINimum to MAXimum (depending on current unit)
This command defines the position of the display line.
Example:
":CALC:DLIN -20dBm"
Features:
*RST value:
SCPI:
Modes:
A, VA, BTS, MS
- (STATe to OFF)
device-specific
The display lines mark the given level in the display. The units DEG, RAD, S, and HZ are only valid in
conjunction with option Vector Signal Analysis, FSE-B7.
:CALCulate<1|2>:DLINe<1|2>:STATe ON | OFF
This command switches the display line on or off.
Example:
":CALC:DLIN2:STAT OFF"
Features:
*RST value:
SCPI:
Modes:
A, VA, BTS, MS
1065.6016.12
OFF
device-specific
6.15
E-16
CALCulate Subsystem
FSE
:CALCulate<1|2>:THReshold MINimum to MAXimum (depending on current unit)
This command defines the position of the thresholds.
Example:
":CALC:THR -82dBm"
Features:
*RST value:
SCPI:
Modes:
A, VA, BTS, MS
- (STATe to OFF)
device-specific
For marker scan functions MAX PEAK, NEXT PEAK etc., the threshold serves as the lowest limit for
maximum or minimum search. The units DEG, RAD, S, and HZ are only valid in conjunction with
option Vector Signal Analysis, FSE-B7.
:CALCulate<1|2>:THReshold:STATe ON | OFF
This command switches the threshold on or off.
Example:
":CALC:THR:STAT ON"
Features:
*RST value:
SCPI:
Modes:
A, VA, BTS, MS
OFF
device-specific
:CALCulate<1|2>:CTHReshold MINimum to MAXimum (depending on the current unit)
This command defines the position of a threshold line (base line), below which all measured values
are cleared.
Example:
":CALC:CTHR -82dBm"
Features:
*RST value:
SCPI:
Mode:
A, VA, BTS, MS
- (STATe to OFF)
device-specific
The units DEG, RAD, S, and HZ are only valid in conjunction with option Vector Signal Analysis,
FSE-B7.
:CALCulate<1|2>:CTHReshold:STATe ON | OFF
This command is for switching on or off the threshold line (base line), below which all measured
values are cleared.
Example:
":CALC:CTHR:STAT ON"
Features:
*RST value:
SCPI:
Mode:
A, VA, BTS, MS
OFF
device-specific
:CALCulate<1|2>:RLINe MINimum to MAXimum (depending on the current unit)
This command defines the position of the reference line.
Example:
":CALC:RLIN -10dBm"
Features:
*RST value:
SCPI:
Modes:
A, VA, BTS, MS
- (STATe to OFF)
device-specific
The reference line serves as a reference for the arithmetic operation of traces. The units DEG, RAD,
S, and HZ are only valid in conjunction with option Vector Signal Analysis, FSE-B7.
1065.6016.12
6.16
E-16
FSE
CALCulate Subsystem
:CALCulate<1|2>:RLINe:STATe ON | OFF
This command switches the reference line on or off.
Example:
":CALC:RLIN:STAT ON"
Features:
*RST value:
SCPI:
Modes:
A, VA, BTS, MS
OFF
device-specific
:CALCulate<1|2>:FLINe<1|2> 0 GHz to fmax
This command defines the position of the frequency lines.
Example:
":CALC:FLIN2 120MHz"
Features:
*RST value:
SCPI:
Modes:
A-F, VA, BTS, MS
- (STATe to OFF)
device-specific
The frequency lines mark the given frequencies in the display. Frequency lines are only valid for a
SPAN >0.
:CALCulate<1|2>:FLINe<1|2>:STATe ON | OFF
This command switches the frequency line on or off.
Example:
":CALC:FLIN2:STAT ON"
Features:
*RST value:
SCPI:
Modes:
A-F, VA, BTS, MS
OFF
device-specific
:CALCulate<1|2>:TLINe<1|2> 0 to 1000s
This command defines the position of the time lines.
Example:
":CALC:TLIN 10ms"
Features:
*RST value:
SCPI:
Modes:
A-Z, VA, BTS, MS
- (STATe to OFF)
device-specific
The time lines mark the given times in the display. Time lines are only valid for a SPAN = 0.
:CALCulate<1|2>:TLINe<1|2>:STATe ON | OFF
This command switches the time line on or off.
Example:
":CALC:TLIN2:STAT ON"
Features:
*RST value:
SCPI:
Modes:
A-Z, VA, BTS, MS
1065.6016.12
OFF
device-specific
6.17
E-16
CALCulate Subsystem
FSE
CALCulate:FEED Subsystem
The CALCulate:FEED subsystem selects the measured data in operating mode vector signal analysis.
This subsystem is only valid in connection with option FSE-B7, Vector Signal Analysis.
COMMAND
PARAMETERS
CALCulate<1|2>
:FEED
UNIT
COMMENT
Vector Signal Analysis/
no query
:CALCulate<1|2>:FEED
This command selects the measured data that are to be displayed.
Parameter:
::=
‘XTIM:DDEM:MEAS’ |
‘XTIM:DDEM:REF’ |
‘XTIM:DDEM:ERR:MPH’ |
‘XTIM:DDEM:ERR:VECT’ |
‘XTIM:DDEM:SYMB’ |
‘XTIM:AM’ |
‘XTIM:FM’ |
‘XTIM:PM’ |
‘XTIM:AMSummary’ |
‘XTIM:FMSummary’ |
‘XTIM:PMSummary’ |
‘TCAP’
Features:
*RST value:
SCPI:
‘XTIM:DDEM:MEAS’
conforming
Mode:
VA
The string parameters have the following meaning:
‘XTIM:DDEM:MEAS’
‘XTIM:DDEM:REF’
‘XTIM:DDEM:ERR:MPH’
‘XTIM:DDEM:ERR:VECT’
‘XTIM:DDEM:SYMB’
Test signal (filtered, synchronized to symbol clock)
Reference signal (internally generated from demodulated test
signal)
Error signal (magnitude and phase error)
Vector error signal
Symbol table (demodulated bits and table with modulation errors)
'XTIM:AM'
'XTIM:FM'
'XTIM:PM'
'XTIM:AMSummary'
'XTIM:FMSummary'
'XTIM:PMSummary'
‘TCAP’
Demodulated AM signal (analog demodulation)
Demodulated FM signal (analog demodulation)
Demodulated PM signal (analog demodulation)
AM-Summary Marker (analog demodulation)
FM-Summary Marker (analog demodulation)
PM-Summary Marker (analog demodulation)
Test signal in capture buffer
1065.6016.12
6.18
E-16
FSE
CALCulate Subsystem
CALCulate:FORMat and CALCulate:FSK Subsystems
The CALCulate:FORMat and CALCulate:FSK subsystems determine further processing and conversion
of measured data in operating mode vector signal analysis.
This sub system is only valid in connection with option FSE-B7, Vector Signal Analysis.
COMMAND
PARAMETERS
CALCulate<1|2>
:FORMat
UNIT
MAGNitude | PHASe | UPHase |
RIMag | FREQuency | IEYE | QEYE |
TEYE | FEYE | COMP | CONS
:FSK
:DEViation
:REFerence
:CALCulate<1|2>:FORMat
COMMENT
Vector Signal Analysis
HZ
Vector Signal Analysis
MAGNitude | PHASe | UPHase | RIMag | FREQuency | IEYE | QEYE |
TEYE | FEYE | COMP | CONS
This command defines the display of the traces.
Example:
":CALC:FORM CONS"
Features:
*RST value:
SCPI:
Mode:
VA-D
MAGNitude
conforming
The availability of the parameters depends on the selected data (see command
:CALCulate:FEED).
Available for selection measurement signal, reference signal and modulation error
(CALCulate:FEED ‘XTIM:DDEM:MEAS’,‘XTIM:DDEM:REF) ,‘XTIM:DDEM:ERR:MPH’):
MAGNitude
Display of the magnitude in the time domain (only available for settings
:CALCulate:FEED ‘XTIM:DDEM:ERR:MPH’ (error signal) or
‘XTIM:DDEM:MEAS’ (measurement signal) or ‘XTIM:DDEM:REF’
(reference signal)
Display of the phase in the time domain with or without (”unwrapped”)
limitation to ±180°
Display of the time characteristic of inphase and quadrature
component
Display of the frequency response in the time domain
Display of the polar vector diagram (complex)
Display of the polar vector diagaram (constellation)
PHASe | UPHase
RIMag
FREQuency
COMP
CONS
Available for selection measurement signal and reference signal (CALCulate:FEED
‘XTIM:DDEM:MEAS’,‘XTIM:DDEM:REF):
IEYE | QEYE
TEYE
FEYE
Eye diagram of the inphase or quadrature component
Display of the trellis diagram
Eye diagram of FSK modulation
:CALCulate<1|2>:FSK:DEViation:REFerence
This command defines the reference value of the frequency deviation for FSK modulation.
Example:
":CALC:FSK:DEV:REF 20kHz"
Features:
*RST value:
SCPI:
Mode:
VA-D
1065.6016.12
device-specific
6.19
E-16
CALCulate Subsystem
FSE
CALCulate:LIMit Subsystem
The CALCulate:LIMit subsystem comprises the limit lines and the corresponding limit checks. Limit lines
can be defined as upper and lower limit lines. The individual values of the limit lines correspond to the
values of the X-axis (CONTrol) which have to have the same number.
COMMAND
CALCulate<1|2>
:LIMit<1 to 8>
:ACTive?
:TRACe
:STATe
:UNIT
CATalog?
:CONTrol
[:DATA]
:DOMain
:OFFSet
:MODE
:UNIT
[:TIME]
:SHIFt
:SPACing
:UPPer
[:DATA]
:STATe
:OFFSet
PARAMETERS
COMMENT
Query only
DBM | DBPW | DBPT | WATT | DBUV |
DBMV | VOLT | DBUA | AMPere | DB |
DBUV_MHZ | DBMV_MHZ | DBUA_MHZ |
DBUV_M | DBUA_M | DBUV_MMHZ |
DBUA_MMHZ | DEG | RAD | S | HZ | PCT |
UNITLESS
--
Query only
,..
FREQuency | TIME
RELative | ABSolute
S | SYM
LINear | LOGarithmic
HZ | S | SYM
HZ | S | SYM
HZ | S | SYM
,..
:MARGin
:MODE
:SHIFt
UNIT
RELative | ABSolute
Vector Signal Analysis
DBM | DB | DEG |
RAD | S | HZ | PCT
-DB | DEG | RAD |
S | HZ | PCT
DB| DEG | RAD |
S | HZ | PCT
-DB | DEG | RAD|
S | HZ | PCT
LINear | LOGarithmic
:SPACing
:LOWer
[:DATA]
:STATe
:OFFSet
,..
:MARGin
:MODE
:SHIFt
RELative | ABSolute
DBM | DB | DEG |
RAD | S | HZ | PCT
-DB| DEG | RAD |
S | HZ | PCT
DB| DEG | RAD |
S | HZ | PCT
-DB | DEG | RAD |
S | HZ | PCT
LINear | LOGarithmic
:SPACing
:FAIL?
:CLEar
[:IMMediate]
1065.6016.12
---
--
query only
no query
6.20
E-16
FSE
CALCulate Subsystem
COMMAND
PARAMETERS
CALCulate<1|2>
:LIMit<1 to 8>
:COMMent
:COPY
:NAME
:DELete
:BURSt
:PTEMplate?
:POWer?
:PFERror?
:MACCuracy?
:SPECtrum
:MODulation?
UNIT
COMMENT
1 to 8 | < name>
-Option FSE-K11 or FSE-K10
query only
query only
query only
query only, option FSE-K20/K21
Option FSE-K11 or FSE-K10
query only
--
:FAILs?
:EXCeptions?
:SWITching?
:FAILs?
:SPURious?
----ARFCn | TXBand | RXBand |
COMBined | DCSRx1800
ARFCn | TXBand | RXBand |
COMBined | DCSRx1800
ARFCn | TXBand | RXBand |
COMBined | DCSRx1800
:MARGin
TXBand | OTXBand | RXBand |
IDLeband
TXBand | OTXBand | RXBand |
IDLeband
:ACPower
[:STATe]
:ACHannel
:STATe
:RESult?
:ALTernate<1|2>
:STATe
:RESult?
,
-,
--
:FAILs?
query only
query only
DB
DB; DB
query only; Option FSE-K11or FSE-K10
query only
query only; Option FSE-K11 or FSE-K10
query only
DB; DB
query only
query only
:CALCulate<1|2>:LIMit<1 to 8>:ACTive?
This command queries the names of all activated limit lines. The names are output in alphabetical
order. If no limit line is activated, an empty string will be output. The numeric suffixes in
CALCulate<1|2> and LIMit<1 to 8> are not significant.
Example:
":CALC:LIM:ACT?"
Features:
*RST value:
SCPI:
device-specific
Mode:
A, VA, BTS, MS
:CALCulate<1|2>:LIMit<1 to 8>:TRACe 1 to 4
This command assigns a trace to a limit line.
Example:
":CALC:LIM2:TRAC 2"
Features:
*RST value:
SCPI:
Modes:
A, VA, BTS, MS
1065.6016.12
1
device-specific
6.21
E-16
CALCulate Subsystem
FSE
:CALCulate<1|2>:LIMit<1 to 8>:STATe ON | OFF
This command switches the limit check for the selected limit line on or off. With limit check switched
off, the limit line is disabled.
Example:
":CALC:LIM:STAT ON"
Features:
*RST value:
SCPI:
Modes:
A, VA, BTS, MS
OFF
conforming
The result of the limit check can be queried with CALCulate:LIMit:FAIL?.
:CALCulate<1|2>:LIMit<1 to 8>:UNIT
DBM | DBPW | DBPT | WATT | DBUV | DBMV | VOLT |DBUA
| AMPere | DB | DBUV_MHZ | DBMV_MHZ | DBUA_MHZ |
DBUV_M | DBUA_M | DBUV_MMHZ | DBUA_MMHZ |
UNITLESS|
This command defines the unit of the selected limit line.
Example:
":CALC:LIM:UNIT DBUV"
Features:
*RST value:
SCPI:
Modes:
A, VA, BTS, MS
DBM
device-specific
DBUV_MHZ and DBUA_MHZ denote the units DBUV/MHZ or DBUA/MHZ.
Upon selection of the unit DB the limit line is automatically switched to the relative mode. For units
different from DB the limit line is automatically switched to the absolute mode.
The units DEG, RAD, S, HZ are available in the vector analysis mode only.
:CALCulate<1|2>:LIMit:CATalog?
This command reads out the names of all limit lines stored on the harddisk.
Syntax of output format:
,,
<1st file name>,,<1st file length>,<2nd file name>,,<2nd file length>,....,,
Example:
":CALC:LIM:CAT?"
Feature:
*RST value:
SCPI:
Mode:
A, VA, BTS, MS
device-specific
:CALCulate<1|2>:LIMit<1 to 8>:CONTrol[:DATA] ,..
This command defines the X-axis values (frequencies or times) of the upper or lower limit lines.
Example:
":CALC:LIM:CONT 1MHz,30MHz,300MHz,1GHz"
Features:
*RST value:
SCPI:
Modes:
A, VA, BTS, MS
- (LIMit:STATe is set to OFF)
conforming
The number of values for the CONTrol axis and the corresponding UPPer- and/or LOWer limit lines
have to be identical. Available units are HZ | S | SYM, SYM only for vector signal analyzer mode.
1065.6016.12
6.22
E-16
FSE
CALCulate Subsystem
:CALCulate<1|2>:LIMit<1 to 8>:CONTrol:DOMain FREQuency | TIME
This command defines the X-axis in the frequency or time domain.
Example:
":CALC:LIM:CONT:DOM TIME"
Features:
*RST value:
SCPI:
Modes:
A, VA, BTS, MS
FREQuency
device-specific
:CALCulate<1|2>:LIMit<1 to 8>:CONTrol:OFFSet
This command defines an offset for the X-axis value of the selected relative limit line in the frequency
or time domain.
Example:
":CALC:LIM:CONT:OFFS 100us"
Features:
*RST value:
SCPI:
Modes:
A, VA
0
device-specific
:CALCulate<1|2>:LIMit<1 to 8>:CONTrol:MODE
RELative | ABSolute
This command selects the relative or absolute scaling for the X-axis of the selected limit line.
Example:
":CALC:LIM:CONT:MODE REL"
Features:
*RST value:
SCPI:
Modes:
A, VA, BTS, MS
ABSolute
device-specific
Upon selection of RELative, the unit is switched to DB.
:CALCulate<1|2>:LIMit<1 to 8>:CONTrol:UNIT[:TIME]
S | SYM
This command defines the unit of the x-axis scaling of limit lines.
Example:
":CALC:LIM:CONT:UNIT SYM"
Features:
*RST value:
SCPI:
Mode:
VA
S
device-specific
:CALCulate<1|2>:LIMit<1 to 8>:CONTrol:SHIFt
This command shifts a limit line which has been specified for relative frequencies or times (X-axis).
Example:
":CALC:LIM:CONT:SHIF 50kHz"
Features:
*RST value:
SCPI:
Modes:
A, VA, BTS, MS
-device-specific
This command is an event which is why it is not assigned an *RST value and has no query.
1065.6016.12
6.23
E-16
CALCulate Subsystem
FSE
:CALCulate<1|2>:LIMit<1 to 8>:CONTrol:SPACing LINear | LOGarithmic
This command makes a selection between linear and logarithmic interpolation for determining the
limit line from the frequency points.
Example:
":CALC:LIM:CONT:SPAC LIN"
Features:
*RST value:
SCPI:
Modes:
A, VA, BTS, MS
LIN
device-specific
:CALCulate<1|2>:LIMit<1 to 8>:UPPer[:DATA] ,..
This command defines the values for the upper limit lines.
Example:
":CALC:LIM:UPP -10,0,0,-10"
Features:
*RST value:
SCPI:
Modes:
A, VA, BTS, MS
- (LIMit:STATe is set to OFF)
conforming
The number of values for the CONTrol axis and the corresponding UPPer limit line have to be
identical. The unit must be identical with the unit selected by command CALC:LIM:UNIT.
If the measured values exceed the UPPer limit line, the limit check signals errors.
The unit must be identical with the unit selected by CALC:LIM:UNIT.
The units DEG, RAD, S, and HZ are available in the vector signal analysis mode only.
:CALCulate<1|2>:LIMit<1 to 8>:UPPer:STATe ON | OFF
This command defines the selected limit line as upper limit line.
Example:
":CALC:LIM:UPPer:STAT ON"
Features:
*RST value:
SCPI:
Modes:
A, VA, BTS, MS
OFF
conforming
The limit check is switched on with command CALCulate:LIMit:STATe ON. The result of the limit
check can be queried with CALCulate:LIMit<1 to 8>:FAIL?.
:CALCulate<1|2>:LIMit<1 to 8>:UPPer:OFFSet
This command defines an offset for the Y-axis of the selected relative upper limit line.
Example:
":CALC:LIM:UPP:OFFS 3dB"
Features:
*RST value:
SCPI:
Modes:
A, VA
0
device-specific
:CALCulate<1|2>:LIMit<1 to 8>:UPPer:MARGin
This command defines the margin of the selected upper limit line.
Example:
":CALC:LIM:UPP:MARG 10dB"
Features:
*RST value:
SCPI:
Modes:
A, VA, BTS, MS
1065.6016.12
0
device-specific
6.24
E-16
FSE
CALCulate Subsystem
:CALCulate<1|2>:LIMit<1 to 8>:UPPer:MODE RELative | ABSolute
This command selects the relative or absolute scaling for the Y-axis of the selected upper limit line.
Example:
":CALC:LIM:UPP:MODE REL"
Features:
*RST value:
SCPI:
Modes:
A, VA, BTS, MS
ABSolute
device-specific
:CALCulate<1|2>:LIMit<1 to 8>:UPPer:SHIFt
This command shifts a limit line, which has relative values for the Y-axis (levels or linear units such
as volt).
Example:
":CALC:LIM:UPP:SHIF 20dB"
Features:
*RST value:
SCPI:
Modes:
A, VA, BTS, MS
-device-specific
This command is an event which is why it is not assigned an *RST value and has no query.
:CALCulate<1|2>:LIMit<1 to 8>:UPPer:SPACing LINear | LOGarithmic
This command makes a selection between linear and logarithmic interpolation for the upper limit line.
Example:
":CALC:LIM:UPP:SPAC LIN"
Features:
*RST value:
SCPI:
Modes:
A, VA, BTS, MS
LIN
device-specific
:CALCulate<1|2>:LIMit<1 to 8>:LOWer[:DATA] ,..
This command defines the values for the selected lower limit line.
Example:
":CALC:LIM:LOW -30,-40,-40,-30"
Features:
*RST value:
SCPI:
Modes:
A, VA, BTS, MS
- (LIMit:STATe is set to OFF)
conforming
The number of values for the CONTrol axis and the corresponding LOWer limit line have to be
identical.If the measured values violate the LOWer limit line, the limit check signals errors.
The unit must be identical with the unit selected by command CALC:LIM:UNIT.
The units DEG, RAD, S, and HZ are available in the vector signal analysis mode only.
1065.6016.12
6.25
E-16
CALCulate Subsystem
FSE
:CALCulate<1|2>:LIMit<1 to 8>:LOWer:STATe ON | OFF
This command defines the selected limit line as lower limit line.
Example:
":CALC:LIM:LOWer:STAT ON"
Features:
*RST value:
SCPI:
Modes:
A, VA, BTS, MS
OFF
conforming
The limit check is switched on with command CALCulate:LIMit:STATe ON. The result of the limit
check can be queried with CALCulate:LIMit:FAIL?.
:CALCulate<1|2>:LIMit<1 to 8>:LOWer:OFFSet
This command defines an offset for the Y-axis of the selected relative lower limit line.
Example:
":CALC:LIM:LOW:OFFS 3dB"
Features:
*RST value:
SCPI:
Modes:
A, VA
0
device-specific
:CALCulate<1|2>:LIMit<1 to 8>:LOWer:MARGin
This command defines the margin of the selected lower limit line.
Example:
":CALC:LIM:LOW:MARG 10dB"
Features:
*RST value:
SCPI:
Modes:
A, VA, BTS, MS
0
device-specific
:CALCulate<1|2>:LIMit<1 to 8>:LOWer:MODE RELative | ABSolute
This command selects the relative or absolute scaling for the Y-axis of the selected lower limit line.
Example:
":CALC:LIM:LOW:MODE REL"
Features:
*RST value:
SCPI:
Modes:
A, VA, BTS, MS
ABSolute
device-specific
:CALCulate<1|2>:LIMit<1 to 8>:LOWer:SHIFt
This command shifts a limit line, which has relative values for the Y-axis (levels or linear units such
as volt).
Example:
":CALC:LIM:LOW:SHIF 20dB"
Features:
*RST value:
SCPI:
Modes:
A, VA, BTS, MS
-device-specific
This command is an event which is why it is not assigned an *RST value and has no query.
1065.6016.12
6.26
E-16
FSE
CALCulate Subsystem
:CALCulate<1|2>:LIMit<1 to 8>:LOWer:SPACing LINear | LOGarithmic
This command makes a selection between linear and logarithmic interpolation for the lower limit line.
Example:
":CALC:LIM:LOW:SPAC LIN"
Features:
*RST value:
SCPI:
Modes:
A, VA, BTS, MS
LIN
device-specific
:CALCulate<1|2>:LIMit<1 to 8>:FAIL?
This command queries the result of the limit check.
Example:
":CALC:LIM:FAIL?"
Features:
*RST value:
SCPI:
Modes:
A, VA, BTS, MS
conforming
The result of the limit check responds with 0 in case of PASS and with 1 in case of FAIL.
For measurements spectrum due to modulation and spectrum due to transients (options FSE-K10
and FSE-K11), the result of the limit check is queried with this command in frequency sweep mode.
:CALCulate<1|2>:LIMit<1 to 8>:CLEar[:IMMediate]
This command deletes the result of the current limit check.
Example:
":CALC:LIM:CLE"
Features:
*RST value:
SCPI:
Modes:
A, VA, BTS, MS
conforming
This command is an event which is why it is not assigned an *RST value.
:CALCulate<1|2>:LIMit<1 to 8>:COMMent
This command defines a comment for the limit line selected.
Example:
":CALC:LIM:COMM ’Upper limit for spectrum’"
Features:
*RST value:
SCPI:
Modes:
A, VA, BTS, MS
1065.6016.12
blank comment
device-specific
6.27
E-16
CALCulate Subsystem
FSE
:CALCulate<1|2>:LIMit<1 to 8>:COPY 1 to 8 |
This command copies one limit line onto another one.
Parameter:
1 to 8 ::= number of the new limit line or, alternatively:
::= name of the new limit line given as a string
Example:
":CALC:LIM1:COPY 2"
":CALC:LIM1:COPY ’GSM2’"
Features:
*RST value:
SCPI:
Modes:
A, VA, BTS, MS
-device-specific
The name of the limit line may contain a maximum of 8 characters. This command is an "event"
which is why it is not assigned an *RST value and has no query.
:CALCulate<1|2>:LIMit<1 to 8>:NAME
This command assigns a name to a limit line numbered 1 to 8. If a limit line of the given name
doesn’t exist previously, a limit line with this name is created. The values of a previous limit line with
the selected line number are kept and the current unit is used. If no limit line with the selected line
number was defined yet, the correct values for the x and y axis have to be entered before the new
limit line will be saved (using commands CALCulate:LIMit:CONTrol:DATA and
CALCulate:LIMit:LOWer|UPPer:DATA).
Example:
":CALC:LIM1:NAME ’GSM1’"
Features:
*RST value:
SCPI:
Modes:
A, VA, BTS, MS
’REM1’ to ’REM8’ for lines 1 to 8
device-specific
The name of the limit line may contain a maximum of 8 characters.
:CALCulate<1|2>:LIMit<1 to 8>:DELete
This command deletes the limit line selected.
Examples:
":CALC:LIM1:DEL"
Features:
*RST value:
SCPI:
Modes:
A, VA, BTS, MS
-device-specific
This command is an "event" which is why it is not assigned an *RST value and has no query.
1065.6016.12
6.28
E-16
FSE
CALCulate Subsystem
:CALCulate<1|2>:LIMit<1 to 8>:BURSt:PTEMplate?
This command queries the result of the limit check for a power vs. time measurement.
Parameter:
The result is displayed in character data form. Possible values are:
FAILED
RUNNING
PASSED limit not exceeded
limit exceeded
measurement not completed
Examples:
":CALC:LIM:BURS:PTEM?"
Features:
*RST value:
SCPI:
Modes:
BTS, MS
-device-specific
This command is a query and therefore not assigned a *RST value.
If no measurement has been carried out yet, a query error is triggered off. The numeric suffixes
<1|2> or <1 to 8> are not significant for this command.
:CALCulate<1|2>:LIMit<1 to 8>:BURSt:POWer?
This command queries the total result of the carrier power measurement.
Parameter:
The result is displayed in character data form. Possible values are:
PASSED
FAILED
ABORTED
RUNNING
limit not exceeded
limit exceeded
measurement aborted
measurement not completed
Examples:
":CALC:LIM:BURS:POW?"
Result: PASSED
Features:
*RST value:
SCPI:
Modes:
BTS, MS
-device-specific
This command is a query and therefore not assigned a *RST value.
If the command is triggered off before the carrier power measurement was started for the first time, a
query error results. The numeric suffixes <1|2> or <1 to 8> are not significant for this command.
:CALCulate<1|2>:LIMit<1 to 8>:BURSt:PFERror?
This command queries the total result of the phase/frequency measurement.
Parameter:
Result
1
0
limit not exceeded
limit exceeded
Example:
":CALC:LIM:BURS:PFER?"
Result:1
Features:
*RST value:
SCPI:
Modes:
BTS, MS
-device-specific
This command is a query and therefore not assigned a *RST value.
If the command is triggered off before the phase/frequency measurement was started for the first
time, a query error results. The numeric suffixes <1|2> or <1 to 8> are not significant for this
command.
1065.6016.12
6.29
E-16
CALCulate Subsystem
FSE
:CALCulate<1|2>:LIMit<1 to 8>:BURSt:MACCuracy?
This command queries the total result of the modulation accuracy measurement.
Parameter:
1
0
limit not exceeded
limit exceeded
Example:
":CALC:LIM:BURS:MACC?"
Result:1
Features:
*RST value:
SCPI:
Modes:
BTS, MS
-device-specific
This command is a query and therefore not assigned a *RST value.
If the command is triggered off before the cphase-frequency measurement was started for the first
time, a query error results. The numeric suffixes <1|2> or <1 to 8> are not significant for this
command. This command is only available in conjunction with option FSE-K20 / FSE-K21 .
:CALCulate<1|2>:LIMit<1 to 8>:SPECtrum:MODulation? ARFCn | TXBand | RXBand | COMBined |
DCSRx1800
This command queries the total result of the spectrum due to modulation measurement for list mode.
For frequency mode, the limit violations are queried with command CALCulate:LIMit:FAIL?.
Parameter:
The result is displayed in character data form. Possible values are:
PASSED
FAILED
ABORTED
RUNNING
limit not exceeded
limit exceeded
measurement aborted
measurement not completed
Examples:
":CALC:LIM:SPEC:MOD? RXB"
Result:
PASSED
Features:
*RST value:
SCPI:
Modes:
BTS, MS
ARFCn
RXBand
DCSRx1800
-device-specific
ARFCN ± 1.8 MHz
TXBand
TX-band
RX-band
COMBined ARFCN ± 1.8 MHz / TX-band
RX-Band DCS 1800 (option FSE-K10 only)
This command is a query and therefore not assigned a *RST value.
The numeric suffixes <1|2> or <1 to 8> are not significant for this command.
1065.6016.12
6.30
E-16
FSE
CALCulate Subsystem
:CALCulate<1|2>:LIMit<1 to 8>:SPECtrum:MODulation:FAILs?
ARFCn | TXBand | RXBand |
COMBined | DCSRx1800
This command queries the number of limit violations of the spectrum due to modulation
measurement for list mode.The number of limit violations is the total of all violations above and below
the carrier. For frequency mode, the limit violations are queried with command
CALCulate:LIMit:FAIL?.
Examples:
":CALC:LIM:SPEC:MOD:FAIL? RXB"
Features:
*RST value:
SCPI:
Modes:
BTS, MS
ARFCn
TXBand
RXBand
COMBined
DCSRx1800
ARFCN ± 1.8 MHz
TX-band
RX-band
ARFCN ± 1.8 MHz / TX-band
RX-Band DCS 1800 (option FSE-K10 only)
-device-specific
This command is a query and therefore not assigned a *RST value
The numeric suffixes <1|2> or <1 to 8> are not significant for this command.
:CALCulate<1|2>:LIMit<1 to 8>:SPECtrum:MODulation:EXCeptions? ARFCn | TXBand | RXBand |
COMBined | DCSRx1800
This command queries the number of limit violations of the spectrum due to modulation
measurement which are marked as exceptions. This command is only available for list mode.
Examples:
":CALC:LIM:SPEC:MOD:EXC? RXB"
Features:
*RST value:
SCPI:
Modes:
BTS, MS
ARFCn
TXBand
RXBand
COMBined
DCSRx1800
ARFCN ± 1.8 MHz
TX-band
RX-band
ARFCN ± 1.8 MHz / TX-band
RX-Band DCS 1800 (option FSE-K10 only
-device-specific
This command is a query and therefore not assigned a *RST value. The numeric suffixes <1|2> or
<1 to 8> are not significant for this command.
1065.6016.12
6.31
E-16
CALCulate Subsystem
FSE
:CALCulate<1|2>:LIMit<1 to 8>:SPECtrum:SWITching?
This command queries the total result of the spectrum due to switching transients measurements for
list mode. For frequency mode, the limit violations are queried with command
CALCulate:LIMit:FAIL?
Parameter:
The result is displayed in character data form. Possible values are:
PASSED
limit not exceeded
FAILED
limit exceeded
ABORTED
measurement aborted
RUNNING
measurement not completed
Examples:
":CALC:LIM:SPEC:SWIT?"
Result: PASSED
Features:
*RST value:
SCPI:
Modes:
BTS, MS
-device-specific
This command is a query and therefore not assigned a *RST value. The numeric suffixes <1|2> or
<1 to 8> are not significant for this command.
:CALCulate<1|2>:LIMit<1 to 8>:SPECtrum:SWITching:FAILs?
This command queries the number of limit violations of the spectrum due to switching transient
measurement for list mode.The number of limit violations is the total of all violations above and below
the carrier. For frequency mode, the limit violations are queried with command
CALCulate:LIMit:FAIL?.
Examples:
":CALC:LIM:SPEC:SWIT:FAIL?"
Features:
*RST value:
SCPI:
Modes:
BTS, MS
-device-specific
This command is a query and therefore not assigned a *RST value. The numeric suffixes <1|2> or
<1 to 8> are not significant for this command.
:CALCulate<1|2>:LIMit<1 to 8>:SPURious? TXBand | OTXBand | RXBand | IDLeband
This command queries the total result of the spurious emissions measurement.
Parameter:
The result is displayed in character data form. Possible values are:
PASSED
limit not exceeded
FAILED
limit exceeded
ABORTED
measurement aborted
RUNNING
measurement not completed
Examples:
":CALC:LIM:SPUR? OTXB"
Result:PASSED
Features:
*RST value:
SCPI:
Modes:
BTS, MS
TXBand
OTXBand
RXBand
IDLeband
TX-band
Not TX-band
RX-band (option FSE-K11 only)
IDLeband (option FSE-K10 only)
-device-specific
This command is a query and therefore not assigned a *RST value. The numeric suffixes <1|2> or
<1 to 8> are not significant for this command.
1065.6016.12
6.32
E-16
FSE
CALCulate Subsystem
:CALCulate<1|2>:LIMit<1 to 8>:SPURious:FAILs? TXBand | OTXBand | RXBand | IDLeband
This command queries the number of limit violations of the spurious emissions measurement.
Examples:
":CALC:LIM:SPUR:FAIL? OTXB"
Features:
*RST value:
SCPI:
Modes:
BTS, MS
TXBand
OTXBand
RXBand
IDLeband
TX-band
Not TX-band
RX-band (option FSE-K11 only)
IDLeband (option FSE-K10 only)
-device-specific
This command is a query and therefore not assigned a *RST value. The numeric suffixes <1|2> or
<1 to 8> are not significant for this command.
:CALCulate<1|2>:LIMit<1 to 8>:MARGin 0 to 100DB
This command sets /changes the value of the margin (safe difference to the actual limit) for the limit
check.
Examples:
":CALC:LIM:MARG 6DB"
Features:
*RST value:
SCPI:
Modes:
BTS, MS
3DB
device-specific
The numeric suffixes <1|2> or <1 to 8> are not significant for this command.
:CALCulate<1|2>:LIMit<1 to 8>:ACPower[:STATe] ON | OFF
This command switches on and off the limit check for adjacent channel power measurements. The
commands CALC:LIM:ACP:ACH:STAT or CALC:LIM:ACP:ALT:STAT must be used in addition to
specify whether the limit check is to be performed for the upper/lower adjacent channel or for the
alternate adjacent channels.
Examples:
":CALC:LIM:ACP ON"
Features:
*RST value:
SCPI:
Modes:
A, VA
OFF
device-specific
The numeric suffixes <1|2> or <1 to 8> are not significant for this command.
:CALCulate<1|2>:LIMit<1 to 8>:ACPower:ACHannel 0 to 100 dB, 0 to 100 dB
This command defines the limit for the upper/lower adjacent channel for adjacent channel power
measurements.
Parameter:
The first (second) numeric value is the limit for the upper (lower) adjacent
channel.
Examples:
":CALC:LIM:ACP:ACH 30DB, 30DB"
Features:
*RST value:
SCPI:
Modes:
A, VA
0 dB
device-specific
The numeric suffixes <1|2> or <1 to 8> are not significant for this command.
1065.6016.12
6.33
E-16
CALCulate Subsystem
FSE
:CALCulate<1|2>:LIMit<1 to 8>:ACPower:ACHannel:STATe ON | OFF
This command activates the limit check for the adjacent channel when adjacent channel power
measurement is performed. Before, the limit check must be activated using CALC:LIM:ACP ON.
Examples:
":CALC:LIM:ACP:ACH:STAT ON"
Features:
*RST value:
SCPI:
Modes:
A, VA
OFF
device-specific
The numeric suffixes <1|2> or <1 to 8> are not significant for this command.
:CALCulate<1|2>:LIMit<1 to 8>:ACPower:ACHannel:RESult?
This command queries the result of the limit check for the upper /lower adjacent channel when
adjacent channel power measurement is performed.
Parameter:
The result is returned in the form , where
= PASSED | FAILED, and where the first returned value denotes the
lower, the second denotes the upper adjacent channel.
Examples:
":CALC:LIM:ACP:ACH:RES?"
Features:
Modes:
*RST value:
SCPI:
A, VA
-device-specific
This command is a query and therefore not assigned a *RST value. If the power measurement of the
adjacent channel is switched off, the command triggers a query error.
The numeric suffixes <1|2> or <1 to 8> are not significant for this command.
:CALCulate<1|2>:LIMit<1 to 8>:ACPower:ALTernate<1|2> 0 to 100DB, 0 to 100 dB.
This command defines the limit for the first/second alternate adjacent channel for adjacent channel
power measurements.
Parameter:
The first (second) numeric value is the limit for the lower (upper) alternate
adjacent channel. The numeric suffix after ALTernate<1|2> denotes the first
or the second alternate channel.
Examples:
":CALC:LIM:ACP:ALT2 30DB 30DB"
Features:
Modes:
*RST value:
SCPI:
A, VA
0DB
device-specific
The numeric suffixes <1|2> or <1 to 8> are not significant for this command.
1065.6016.12
6.34
E-16
FSE
CALCulate Subsystem
:CALCulate<1|2>:LIMit<1 to 8>:ACPower:ALTernate<1|2>:STATe ON | OFF
This command activates the limit check for the first/second alternate adjacent channel for adjacent
channel power measurements. Before, the limit check must be activated using CALC:LIM:ACP ON.
Examples:
":CALC:LIM:ACP:ALT2:STAT ON"
Features:
*RST value:
SCPI:
A, VA
Modes:
OFF
device-specific
The numeric suffixes <1|2> or <1 to 8> are not significant for this command.
:CALCulate<1|2>:LIMit<1 to 8>:ACPower:ALTernate<1|2>:RESult?
This command queries the result of the limit check for the first/second alternate adjacent channel for
adjacent channel power measurements.
Parameter:
The result is returned in the form , where
= PASSED | FAILED and where the first (second) returned value
denotes the lower (upper) alternate adjacent channel.
Examples:
":CALC:LIM:ACP:ALT2:RES?"
Features:
*RST value:
SCPI:
Modes:
A, VA
-device-specific
This command is a query and therefore not assigned a *RST value. If the power measurement of the
adjacent channel is switched off, the command triggers a query error.
The numeric suffixes <1|2> or <1 to 8> are not significant for this command.
1065.6016.12
6.35
E-16
CALCulate Subsystem
FSE
CALCulate:MARKer Subsystem
The CALCulate:MARKer subsystem checks the marker functions in the instrument.
COMMAND
PARAMETERS
UNIT
COMMENT
CALCulate<1|2>
:MARKer<1 to 4>
[:STATe]
:AOFF
:TRACe
:X
:SLIMits
[:STATe]
:COUNt
:RESolution
:FREQuency?
:COUPled
[:STATe]
:LOEXclude
:Y?
:MAXimum
[:PEAK]
:APEak
:NEXT
:RIGHt
:LEFT
:MINimum
[:PEAK]
:NEXT
:RIGHt
:LEFT
:STEP
[:INCRement]
:AUTO
:PEXCursion
:READout
:FUNCtion
:NDBDown
:STATe
:RESult?
:FREQuency?
:ZOOM
:NOISe
[:STATe]
:RESult?
:DEModulation
:SELect
[:STATe]
:HOLDoff
:SFACtor
:STATe
:RESult?
:FREQuency?
1065.6016.12
--
-HZ | S | SYM
--
-HZ
--
query only
--
--
query only
---
---
----
----
no query
no query,
Vector Signal Analysis
no query
no query
no query
-----
-----
no query
no query
no query
no query
MPHase | RIMaginary
HZ | S | SYM
-DB
--
DB
no query
Vector Signal Analysis
--HZ
query only
query only
no query
--
--
query only
AM|FM
S
---
---
6.36
query only
query only
E-16
FSE
CALCulate Subsystem
COMMAND
PARAMETERS
CALCulate<1|2>
:MARKer
:FUNCtion
:STRack
[:STATe]
:ADEMod
:AM
[:RESult?]
:FM
[:RESult?]
:PM
[:RESult?]
:AFRequency
[:RESult?]
:FERRor
[:RESult?]
:SINad
[:STATe]
:RESult?
:CARRier
[:RESult?]
:DDEMod
:RESult?
:POWer
:SELect
:RESult?
:PRESet
:CFILter
[:STATe]
:SUMMary
[:STATE]
:MAXimum
[:STATe]
:RESult?
:AVERage
:RESult?
:PHOLd
:RESult?
1065.6016.12
UNIT
COMMENT
Option Vector Analyzer
PPEak | MPEak | MIDDle | RMS
query only
PPEak | MPEak | MIDDle | RMS |
RDEV
query only
PPEak | MPEak | MIDDle | RMS
query only
query only
query only
query only
query only
MERM | MEPK | MEPS | PERM |
PEPK | PEPS |EVRM | EVPK |
EVPS | IQOF | IQIM | ADR | FERR |
DEV | FSRM | FSPK | FSPS | RHO |
FEPK | DTTS
ACPower | CPOWer | OBANdwidth |
OBWidth | CN | CN0
ACPower | CPOWer | OBANdwidth |
OBWidth | CN | CN0
NADC | TETRA | PDC | PHS |
CDPD | FWCDma | RWCDma |
F8CDma | R8CDma | F19Cdma |
R19Cdma | FW3Gppcdma |
RW3Gppcdma | M2CDma |
D2CDma | NONE | FO8Cdma |
RO8Cdma | FO19CDMA |
RO19CDMA | TCDMa
OFF
Option Vector Analyzer
query only
query only
no query
Option Vector Analyzer
query only
query only
query only
6.37
E-16
CALCulate Subsystem
COMMAND
CALCulate<1|2>
:MARKer
:FUNCtion
:SUMMary
:PPEak
[:STATe]
:RESult?
:AVERage
:RESult?
:PHOLd
:RESult?
:MPEak
[:STATe]
:RESult?
:AVERage
:RESult?
:PHOLd
:RESult?
:MIDDle
[:STATe]
:RESult?
:AVERage
:RESult?
:PHOLd
:RESult?
:RMS
[:STATe]
:RESult?
:AVERage
:RESult?
:PHOLd
:RESult?
:MEAN
[:STATe]
:RESult?
:AVERage
:RESult?
:PHOLd
:RESult?
:PHOLd
:AVERage
:AOFF
:CENTer
:CSTep
:STARt
:STOP
:MSTep
:REFerence
1065.6016.12
FSE
PARAMETERS
UNIT
COMMENT
Option Vector Analyzer
query only
query only
query only
Option Vector Analyzer
query only
query only
query only
Option Vector Analyzer
query only
query only
query only
query only
query only
query only
query only
query only
query only
no query
no query
no query
no query
no query
no query
no query
6.38
E-16
FSE
CALCulate Subsystem
:CALCulate<1|2>:MARKer<1 to 4>[:STATe] ON | OFF
This command switches on or off the currently selected marker. If no indication is made, marker 1 is
selected automatically.
Example:
":CALC:MARK3 ON"
Features:
*RST value:
SCPI:
Modes:
A, VA, BTS, MS
OFF
device-specific
:CALCulate<1|2>:MARKer<1 to 4>:AOFF
This command switches off all active markers.
Example:
":CALC:MARK:AOFF"
Features:
*RST value:
SCPI:
Modes:
A, VA, BTS, MS
device-specific
This command is an event which is why it is not assigned an *RST value and has no query.
:CALCulate<1|2>:MARKer<1 to 4>:TRACe 1 to 4
This command assigns the selected marker (1 to 4) to the indicated test curve.
Example:
":CALC:MARK3:TRAC 2"
Features:
*RST value
SCPI:
Modes:
A, VA, BTS, MS
device-specific
:CALCulate<1|2>:MARKer<1 to 4>:X 0 to MAX (frequency | sweep time | symbols)
This command positions the selected marker to the indicated frequency (span > 0) or time (span = 0).
Example:
":CALC:MARK:X 10.7MHz"
Features:
*RST value:
SCPI:
Modes:
A, VA, BTS, MS
device-specific
The unit SYM is available only in the vector signal analysis mode.
:CALCulate<1|2>:MARKer<1 to 4>:X:SLIMits[:STATe]
ON | OFF
This command switches between a limited (ON) and unlimited (OFF) search range.
Example:
":CALC:MARK:X:SLIM ON"
features:
*RST value:
SCPI:
Modes:
A, VA
1065.6016.12
OFF
device-specific
6.39
E-16
CALCulate Subsystem
FSE
:CALCulate<1|2>:MARKer<1 to 4>:COUNt
ON | OFF
This command switches on or off the frequency counter at the marker position.
Example:
":CALC:MARK:COUN ON"
Features:
Mode:
*RST value:
SCPI:
A
OFF
device-specific
:CALCulate<1|2>:MARKer<1 to 4>:COUNt:RESolution 0.1 | 1 | 10 | 100 | 1000 | 10000 Hz
This command specifies the resolution of the frequency counter.
Example:
":CALC:MARK:COUN:RES 1kHz"
Features:
*RST value:
1kHz
SCPI:
device-specific
Mode:
A
The numeric suffix in MARKer<1 to 4> is not significant.
:CALCulate<1|2>:MARKer<1 to 4>:COUNt:FREQuency?
This command queries the result of the frequency counter.
Example:
":CALC:MARK:COUN:FREQ?"
Features:
*RST value:
SCPI:
device-specific
Modes:
A, BTS, MS
This command is only a query and thus has no *RST value.
:CALCulate<1|2>:MARKer<1 to 4>:COUPled[:STATe] ON | OFF
This command switches the coupling of markers on or off.
Example:
":CALC:MARK:COUP ON"
Features:
*RST value:
SCPI:
OFF
device-specific
Modes:
VA
The numeric suffix in MARKer<1 to 4> is not significant.
:CALCulate<1|2>:MARKer<1 to 4>:LOEXclude ON | OFF
This command switches the local oscillator suppression on or off.
Example:
":CALC:MARK:LOEX ON"
Features:
*RST value:
OFF
SCPI:
device-specific
Mode:
A-F
The numeric suffixes 1|2 and 1 to 4 are not significant.
1065.6016.12
6.40
E-16
FSE
CALCulate Subsystem
:CALCulate<1|2>:MARKer<1 to 4>:Y?
This command queries the selected marker value.
Example:
":CALC:MARK:Y?"
Features:
*RST value:
SCPI:
Modes:
A, VA, BTS, MS
device-specific
:CALCulate<1|2>:MARKer<1 to 4>:MAXimum[:PEAK]
This command positions the marker to the current maximum value in the trace memory.
Example:
":CALC:MARK:MAX"
Features:
*RST value:
SCPI:
device-specific
Modes:
A, VA, BTS, MS
This command is an event which is why it is not assigned an *RST value and has no query.
:CALCulate<1|2>:MARKer<1 to 4>:MAXimum:APEak
This command positions the marker to the maximum absolute value of the trace.
Example:
":CALC:MARK:MAX:APE"
Features:
*RST value:
SCPI:
device-specific
Mode:
VA
This command is an event which is why it is not assigned an *RST value and has no query.
:CALCulate<1|2>:MARKer<1 to 4>:MAXimum:NEXT
This command positions the marker to the next lower maximum value in the trace memory.
Example:
":CALC:MARK:MAX:NEXT"
Features:
*RST value:
SCPI:
device-specific
Modes:
A, BTS, MS
This command is an event which is why it is not assigned an *RST value and has no query.
:CALCulate<1|2>:MARKer<1 to 4>:MAXimum:RIGHt
This command positions the marker to the next smaller maximum value to the right of the current
value (i.e., in ascending X direction) in the trace memory.
Example:
":CALC:MARK:MAX:RIGH"
Features:
*RST value:
SCPI:
device-specific
Modes:
A, BTS, MS
This command is an event which is why it is not assigned an *RST value and has no query.
1065.6016.12
6.41
E-16
CALCulate Subsystem
FSE
:CALCulate<1|2>:MARKer<1 to 4>:MAXimum:LEFT
This command positions the marker to the next smaller maximum value to the left of the current
value (i.e., in descending X direction) in the trace memory.
Example:
":CALC:MARK:MAX:LEFT"
Features:
*RST value:
SCPI:
device-specific
Modes:
A, BTS, MS
This command is an event which is why it is not assigned an *RST value and has no query.
:CALCulate<1|2>:MARKer<1 to 4>:MINimum[:PEAK]
This command positions the marker to the current minimum value in the trace memory.
Example:
":CALC:MARK:MIN"
Features:
*RST value:
SCPI:
device-specific
Modes:
A, VA, BTS, MS
This command is an event which is why it is not assigned an *RST value and has no query.
:CALCulate<1|2>:MARKer<1 to 4>:MINimum:NEXT
This command positions the marker to the next higher minimum value in the trace memory.
Example:
":CALC:MARK:MIN:NEXT"
Features:
*RST value:
SCPI:
device-specific
Modes:
A, BTS, MS
This command is an event which is why it is not assigned an *RST value and has no query.
:CALCulate<1|2>:MARKer<1 to 4>:MINimum:RIGHt
This command positions the marker to the next higher minimum value to the right of the current
value (ie in ascending X direction).
Example:
":CALC:MARK:MIN:RIGH"
Features:
*RST value:
SCPI:
device-specific
Modes:
A, BTS, MS
This command is an event which is why it is not assigned an *RST value and has no query.
:CALCulate<1|2>:MARKer<1 to 4>:MINimum:LEFT
This command positions the marker to the next higher minimum value to the left of the current value
(ie in descending X direction).
Example:
":CALC:MARK:MIN:LEFT"
Features:
*RST value:
SCPI:
device-specific
Modes:
A, BTS, MS
is command is an event which is why it is not assigned an *RST value and has no query.
1065.6016.12
6.42
E-16
FSE
CALCulate Subsystem
:CALCulate<1|2>:MARKer<1 to 4>:STEP[:INCRement]
This command defines the marker step width.
Example:
":CALC:MARK:STEP 10kHz" (frequency domain)
CALC:MARK:STEP 5ms" (time domain)
Features:
*RST value:
- (STEP is set to AUTO)
SCPI:
device-specific
Mode:
A
This command sets STEP:AUTO to OFF. The numeric suffix in MARKer<1 to 4> is not significant.
:CALCulate<1|2>:MARKer<1 to 4>:STEP:AUTO ON | OFF
This command switches the automatic adaptation of the marker step width on or off.
Example:
":CALC:MARK:STEP:AUTO OFF"
Features:
*RST value:
ON
SCPI:
device-specific
Mode:
A
With AUTO ON, the step width is 10% of the span. The numeric suffix in MARKer<1 to 4> is not
significant.
:CALCulate<1|2>:MARKer<1 to 4>:PEXCursion
This command defines the peak excursion.
Example:
":CALC:MARK:PEXC 10dB"
Features:
*RST value:
SCPI:
6dB
device-specific
Modes:
A, VA, BTS, MS
The numeric suffix in MARKer<1 to 4> is not significant.
:CALCulate<1|2>:MARKer<1 to 4>:READout MPHase | RIMaginary
This command determines the type of the marker display.
Example:
":CALC:MARK:READ RIM"
Features:
*RST value:
SCPI:
device-specific
Mode:
VA-D
The numeric suffix in MARKer<1 to 4> is not significant.
1065.6016.12
6.43
E-16
CALCulate Subsystem
FSE
:CALCulate<1|2>:MARKer<1 to 4>:FUNCtion:NDBDown
This command defines the "N dB Down" value.
Example:
":CALC:MARK:FUNC:NDBD 3dB"
Features:
*RST value:
6dB
SCPI:
device-specific
Mode:
A
The temporary markers T1 and T2 are positioned by n dB below the active reference marker. The
frequency spacing of these markers can be queried with CALCulate:MARKer:FUNCtion:
NDBDown:RESult?.
:CALCulate<1|2>:MARKer<1 to 4>:FUNCtion:NDBDown:STATe ON | OFF
This command switches the "N dB Down" function on or off.
Example:
":CALC:MARK:FUNC:NDBD:STAT ON"
Features:
*RST value:
SCPI:
Modes:
A, BTS, MS
OFF
device-specific
:CALCulate<1|2>:MARKer<1 to 4>:FUNCtion:NDBDown:RESult?
This command queries the frequency spacing (bandwidth) of the "N dB Down" markers.
Example:
":CALC:MARK:FUNC:NDBD:RES?"
Features:
*RST value:
SCPI:
device-specific
Modes:
A, BTS, MS
This command is only a query which is why it is not assigned an *RST value.
:CALCulate<1|2>:MARKer<1 to 4>:FUNCtion:NDBDown:FREQuency?
This command queries the frequencies of the "N dB Down" marker.
Example:
":CALC:MARK:FUNC:NDBD:FREQ?"
Features:
*RST value:
SCPI:
device-specific
Modes:
A, BTS, MS
The two frequency values are separated by comma and indicated in ascending order. This command
is only a query which is why it is not assigned an *RST value.
1065.6016.12
6.44
E-16
FSE
CALCulate Subsystem
:CALCulate<1|2>:MARKer<1 to 4>:FUNCtion:ZOOM
This command defines the range to be enlarged around the active marker.
Example:
":CALC:MARK:FUNC:ZOOM 1kHz"
Features:
*RST value:
SCPI:
device-specific
Mode:
A-F
The subsequent frequency sweep is stopped at the marker position and the frequency of the signal is
counted. This frequency becomes the new center frequency, the zoomed span is then set. This
command is an event which is why it is not assigned an *RST value and has no query.
:CALCulate<1|2>:MARKer<1 to 4>:FUNCtion:NOISe[:STATe] ON | OFF
This command switches the noise measurement on or off.
Example:
":CALC:MARK:FUNC:NOIS ON"
Features:
*RST value:
OFF
SCPI:
device-specific
Mode:
A
The noise power density is measured at the position of the markers. The result can be queried with
CALCulate:MARKer:FUNCtion:NOISe:RESult?.
:CALCulate<1|2>:MARKer<1 to 4>:FUNCtion:NOISe:RESult?
This command queries the result of the noise measurement.
Example:
":CALC:MARK:FUNC:NOIS:RES?"
Features:
*RST value:
SCPI:
device-specific
Modes:
A, BTS, MS
This command is an event which is why it is not assigned an *RST value and has no query.
:CALCulate<1|2>:MARKer<1 to 4>:FUNCtion:DEModulation:SELect AM | FM
This command selects the demodulation type.
Example:
":CALC:MARK:FUNC:DEM:SEL FM"
Features:
*RST value:
SCPI:
Mode:
A
1065.6016.12
AM
device-specific
6.45
E-16
CALCulate Subsystem
FSE
:CALCulate<1|2>:MARKer<1 to 4>:FUNCtion:DEModulation[:STATe] ON | OFF
This command switches the demodulation on or off.
Example:
":CALC:MARK:FUNC:DEM ON"
Features:
*RST value:
SCPI:
Mode:
A
OFF
device-specific
With demodulation switched on, the frequency sweep is stopped at the marker position and the
signal is demodulated during the given stop time.
:CALCulate<1|2>:MARKer<1 to 4>:FUNCtion:DEModulation:HOLDoff 10ms to 1000s
This command defines the duration of the stop time for the demodulation.
Example:
":CALC:MARK:FUNC:DEM:HOLD 3s"
Features:
*RST value:
SCPI:
Mode:
A
- (DEModulation is set to OFF)
device-specific
With demodulation switched on, the frequency sweep is stopped at the marker position and the
signal is demodulated during the given stop time.
:CALCulate<1|2>:MARKer<1 to 4>:FUNCtion:SFACtor (60dB/3dB) | (60dB/6dB)
This command defines the shape factor measurement 60dB/6dB or 60dB/3dB.
Example:
":CALC:MARK:FUNC:SFAC (60dB/3dB)"
Features:
*RST value:
SCPI:
(60dB/6dB)
device-specific
Modes:
A, BTS, MS
The temporary markers T1 to T4 are positioned in pairs by 60dB and by 3dB or 6dB below the active
reference marker. The frequency spacing ratio of these markers - the shape factor - can be queried
with CALCulate:MARKer:FUNCtion:SFACtor:RESult?.
:CALCulate<1|2>:MARKer<1 to 4>:FUNCtion:SFACtor:STATe ON | OFF
This command switches the shape factor measurement on or off.
Example:
":CALC:MARK:FUNC:SFAC:STAT ON"
Features:
*RST value:
SCPI:
Modes:
A, BTS, MS
OFF
device-specific
:CALCulate<1|2>:MARKer<1 to 4>:FUNCtion:SFACtor:RESult?
This command queries the result of the shape factor measurement.
Example:
":CALC:MARK:FUNC:SFAC:RES?"
Features:
*RST value:
SCPI:
device-specific
Modes:
A, BTS, MS
This command is only a query which is why it is not assigned an *RST value.
1065.6016.12
6.46
E-16
FSE
CALCulate Subsystem
:CALCulate<1|2>:MARKer<1 to 4>:FUNCtion:SFACtor:FREQuency?
This command queries the frequencies of the shape factor measurement.
Example:
":CALC:MARK:FUNC:SFAC:FREQ?"
Features:
*RST value:
SCPI:
device-specific
Modes:
A, BTS, MS
Four frequency values (at -60 dB, -6 or. -3 dB, -6 or -3 dB, -60dB) are indicated in ascending order.
They are separated by a comma. This command is only a query which is why it is not assigned an
*RST value.
:CALCulate<1|2>:MARKer<1 to 4>:FUNCtion:STRack[:STATe] ON | OFF
This command switches the signal-track function on or off.
Example:
":CALC:MARK:FUNC:STR ON"
Features:
*RST value:
OFF
SCPI:
device-specific
Mode:
A-F
With SIGNAL TRACK function activated, the maximum signal is determined after each frequency
sweep and the center frequency of this signal is set. With drifting signals the center frequency follows
the signal.
:CALCulate<1|2>:MARKer<1 to 4>:FUNCtion:ADEMod:AM[:RESult]? PPEak| MPEak| MIDDle| RMS
This command queries the results of the AM modulation measurement of the analog demodulation.
Example:
":CALC:MARK:FUNC:ADEM:AM? PPE"
Features:
*RST value:
SCPI:
Mode:
VA-A
PPEak
MPEak
MIDDle
RMS
Result of the measurement with detector +PK
Result of the measurement with detector -PK
Result of averaging ±PK/2
Result of the measurement with detector RMS
device-specific
In the modulation modes FM or PM query of the MIDDle-result is possible only. This command is
only a query which is why it is not assigned an *RST value.
1065.6016.12
6.47
E-16
CALCulate Subsystem
FSE
:CALCulate<1|2>:MARKer<1 to 4>:FUNCtion:ADEMod:FM[:RESult]? PPEak | MPEak | MIDDle |
RMS | RDEV
This command queries the results of the FM modulation measurement of the analog demodulation.
Example:
":CALC:MARK:FUNC:ADEM:FM? PPE"
Features:
*RST value:
SCPI:
Mode:
VA-A
PPEak
MPEak
MIDDle
RMS
Result of the measurement with detector +PK
Result of the measurement with detector -PK
Result of averaging ±PK/2
Result of the measurement with detector RMS
device-specific
In the modulation modes FM or PM query of the MIDDle-result is possible only. This command is
only a query which is why it is not assigned an *RST value.
:CALCulate<1|2>:MARKer<1 to 4>:FUNCtion:ADEMod:PM[:RESult]?PPEak| MPEak| MIDDle| RMS
This command queries the results of the PM modulation measurement of the analog demodulation.
Example:
":CALC:MARK:FUNC:ADEM:PM? PPE"
Features:
*RST value:
SCPI:
Mode:
VA-A
PPEak
MPEak
MIDDle
RMS
Result of the measurement with detector +PK
Result of the measurement with detector -PK
Result of averaging ±PK/2
Result of the measurement with detector RMS
device-specific
In the modulation modes FM or PM query of the MIDDle-result is possible only. This command is
only a query which is why it is not assigned an *RST value.
:CALCulate<1|2>:MARKer<1 to 4>:FUNCtion:ADEMod:AFRequency[:RESult]?
This command queries the audio frequency of the analog demodulation.
Example:
":CALC:MARK:FUNC:ADEM:AFR? "
Features:
*RST value:
SCPI:
Mode:
VA-A
device-specific
:CALCulate<1|2>:MARKer<1 to 4>:FUNCtion:ADEMod:FERRor[:RESult]?
This command queries the frequency error of the analog demodulation.
Example:
":CALC:MARK:FUNC:ADEM:FERR? "
Features:
*RST value:
SCPI:
Mode:
VA-A
device-specific
This command is only a query which is why it is not assigned an *RST value.
1065.6016.12
6.48
E-16
FSE
CALCulate Subsystem
:CALCulate<1|2>:MARKer<1 to 4>:FUNCtion:ADEMod:CARRier[:RESult]?
This command queries the results of the carrier frequency measurement.
Example:
":CALC:MARK:FUNC:ADEM:CARR?"
Features:
*RST value:
SCPI:
Mode:
VA-A
device-specific
This command is only a query which is why it is not assigned an *RST value.
:CALCulate<1|2>:MARKer<1 to 4>:FUNCtion:ADEMod:SINad[:STATe] ON | OFF
This command switches the SINAD measurement on or off.
Example:
":CALC:MARK:FUNC:ADEM:SIN ON"
Features:
*RST value:
SCPI:
Mode:
VA-A
OFF
device-specific
This command is valid only in the analog demodulation mode with Real Time ON.
:CALCulate<1|2>:MARKer<1 to 4>:FUNCtion:ADEMod:SINad:RESult?
This command queries the results of the SINAD measurement.
Example:
":CALC:MARK:FUNC:ADEM:SIN:RES?"
Features:
*RST value:
SCPI:
Mode:
VA-A
device-specific
This command is only a query and thus has no *RST value assigned.
1065.6016.12
6.49
E-16
CALCulate Subsystem
FSE
:CALCulate<1|2>:MARKer<1 to 4>:FUNCtion:DDEMod:RESult?
MERM | MEPK | MEPS | PERM | PEPK | PEPS | EVRM | EVPK | EVPS | IQOF | IQIM | ADR | FERR |
FEPK | RHO| DEV | FSRM | FSPK | FSPS | DTTS
This command queries the error measurement results of digital demodulation.The results correspond
to the values obtained when the symbol table (SYMBOL TABLE/ ERRORS softkey) is selected in
manual operation. Marker values can be queried queried with command CALCulate<1|2>:
MARKer<1...4>:Y? and trace data with command TRACe[:DATA].
Example:
":CALC:MARK:FUNC:DDEM:RES? EVRM"
Features:
*RST value:
SCPI:
Mode:
VA-D
device-specific
MERM
MEPK
MEPS
magnitude error in %rms
maximum of magnitude error in %pk
symbol number by which the maximum
of the magnitude error occurred
FERR frequency error in Hz
FEPK maximum of frequency error
in Hz
ADR amplitude drop in dB/symbol
PERM
PEPK
PEPS
phase error in deg
maximum of phase error in deg
symbol number by which the maximum
of the phase error occurred
RHO
DEV
EVRM
EVPK
EVPS
vector error in %rms
maximum of vector error in %pk
symbol number by which the maximum
of the vector error occurred
FSPK maximum of FSK deviation error
in Hz
FSRM FSK deviation error in Hz
FSPS symbol number by which the
maximum of error occurred
IQOF
IQIM
I/Q-offset error in %
I/Q Imbalance in %
DTTS trigger delay of synchronization
Rho-Factor
FSK deviation in Hz
This command is only a query which is why it is not assigned an *RST value.
:CALCulate<1|2>:MARKer<1 to 4>:FUNCtion:POWer:SELect ACPower | CPOWer | OBANdwidth |
OBWidth | CN | CN0
This command selects the type of power measurement without modifying other settings.
Example:
":CALC:MARK:FUNC:POW:SEL ACP"
Features:
*RST value:
SCPI:
device-specific
Mode:
A-F
This command is an event which is why it is not assigned an *RST value.
ACPower
adjacent channel power measurement
CPOWer
channel power measurement
OBANdwidth | OBWidth
occupied bandwidth power measurement
CN
signal / noise power measurement
CN0
signal-/ noise power measurement based on 1Hz bandwidth
1065.6016.12
6.50
E-16
FSE
CALCulate Subsystem
:CALCulate<1|2>:MARKer<1 to 4>:FUNCtion:POWer:RESult?ACPower | CPOWer | OBANdwidth |
OBWidth | CN | CN0
This command queries the results of the power measurement (see also CALCulate:MARKer:
FUNCtion:POWer:SELect.)
Example:
":CALC:MARK:FUNC:POW:RES? OBW"
Features:
*RST value:
SCPI:
Modes:
A, VA, BTS, MS
ACPower
adjacent channel power measurement; Results are output separated by commas
in the following order: Power of main channel
Power of lower adjacent channel 1
Power of upper adjacent channel 1
Power of lower adjacent channel 2
Power of upper adjacent channel 2
...
The number of results depends on the number of adjacent channels selected.
With logarithmic scaling (RANGE LOG), the power is output in dBm, with linear
scaling (RANGE LIN dB or LIN %) in W. If SENSe:POWer:ACHannel:MODE REL
is selected, adjacent channel power is output in dB.
CPOWer
channel power measurement
With logarithmic scaling (RANGE LOG), the channel power is output in dBm, with
linear scaling (RANGE LIN dB or LIN %) in W.
device-specific
OBANdwidth | OBWidth occupied bandwidth power measurement
The return value is the occupied bandwidth in Hz
CN
signal / noise power measurement
The return value is always in dB..
CN0
signal-/ noise power measurement based on 1Hz bandwidth
The return value is always in dB/Hz
This command is only a query which is why it is not assigned an *RST value.
:CALCulate<1|2>:MARKer<1 to 4>:FUNCtion:POWer[:STATe]
OFF
This command switches the power measurement off.
Example:
":CALC:MARK:FUNC:POW OFF"
Features:
*RST value:
SCPI:
Modes:
A-F, VA-D
device-specific
This command is an event which is why it is not assigned an *RST value.
1065.6016.12
6.51
E-16
CALCulate Subsystem
FSE
:CALCulate<1|2>:MARKer<1 to 4>:FUNCtion:POWer:PRESet
NADC | TETRA | PDC | PHS | CDPD | FWCDma | RWCDma | FW3Gppcdma |
RW3Gppcdma| M2CDma | D2CDma | F8CDma | R8CDma | F19Cdma | R19Cdma |
NONE| FO8Cdma | RO8Cdma | FO19CDMA | RO19CDMA | TCDMa
This command selects the settings for power measurement of one of the standards.
Example:
":CALC:MARK:FUNC:POW:PRES NADC"
Features:
Mode:
*RST value:
SCPI:
A-F
device-specific
FWCDma
W-CDMA forward
RWCDma
W-CDMA reverse
FW3Gppcdma
W-CDMA 3GPP forward
RW3Gppcdma
W-CDMA 3GPP reverse
M2CDma
CDMA2000 Multi Carrier
D2CDma
CDMA2000 Direct Sequence
F8CDma
CDMA800 forward
R8CDma
CDMA800 reverse
F19Cdma
CDMA1900 forward
R19Cdma
CDMA1900 reverse
FO8Cdma
CDMA One 800 forward
RO8Cdma
CDMA One 800 reverse
FO19CDMA
CDMA One 1900 forward
RO19CDMA
CDMA One 1900 reverse
TCDMa
TD-SCDMA
The selection of a standard influences the parameters weighting filter, channel bandwidth and
spacing, resolution and video bandwidth, as well as detector and sweep time.
This command is an event which is why it is not assigned an *RST value and query.
:CALCulate<1|2>:MARKer<1 to 4>:FUNCtion:POWer:CFILter ON | OFF
This command switches the weighting filter for the selected standard on or off.
Example:
":CALC:MARK:FUNC:POW:CFIL ON"
Features:
Mode:
*RST value:
SCPI:
A-F
OFF
device-specific
:CALCulate<1|2>:MARKer<1 to 4>:FUNCtion:SUMMary:STATe ON | OFF
This command switches the messages selected by the summary marker (eg RMS and MEAN) on
and off. One or several measurements can be selected with the commands listed in the following
and then switched jointly on and off with SUMMary:STATe.
Example:
":CALC:MARK:FUNC:SUMM:STAT ON"
Features:
Mode:
1065.6016.12
*RST value:
SCPI:
A-Z, VA
OFF
device-specific
6.52
E-16
FSE
CALCulate Subsystem
:CALCulate<1|2>:MARKer<1 to 4>:FUNCtion:SUMMary:MAXimum[:STATe] ON | OFF
This command switches on or off the measurement of the maximum of the absolute value.
Example:
":CALC:MARK:FUNC:SUMM:MAX ON"
Features:
Mode:
*RST value:
SCPI:
VA
OFF
device-specific
When the measurement is switched on, the summary marker is automatically activated (command
SUMMary:STATe set to ON). When it is switched off, the summary marker remains switched on
provided further measurements are selected. Otherwise the marker is switched off automatically.
:CALCulate<1|2>:MARKer<1 to 4>:FUNCtion:SUMMary:MAXimum:RESult?
This command queries the results of the measurement of the maximum of the absolute value.
Results of average calculation and peak hold are queried with commands
...:MAXimum:AVERage:RESult? and ...:MAXimum:PHOLd:RESult?.
Example:
":CALC:MARK:FUNC:SUMM:MAX:RES?"
Features:
Mode:
*RST value:
SCPI:
VA
device-specific
This command is only a query and thus has no *RST value assigned.
:CALCulate<1|2>:MARKer<1 to 4>:FUNCtion:SUMMary:MAXimum:AVERage:RESult?
This command is used to query the results of the measurement of the maximum of the absolute
value if the average is calculated using the command :CALCulate<1|2>:MARKer<1 to 4>:
FUNCtion:SUMMary:AVERage.
Example:
":CALC:MARK:FUNC:SUMM:MAX:AVER:RES?"
Features:
Mode:
*RST value:
SCPI:
VA
device-specific
This command is only a query and thus has no *RST value assigned.
:CALCulate<1|2>:MARKer<1 to 4>:FUNCtion:SUMMary:MAXimum:PHOLd:RESult?
This command is used to query the results of the measurement of the maximum of the absolute
value when the peak hold function is switched on with command :CALCulate<1|2>:
MARKer<1 to 4>:FUNCtion:SUMMary:PHOLd.
Example:
":CALC:MARK:FUNC:SUMM:MAX:PHOL:RES?"
Features:
Mode:
*RST value:
SCPI:
VA
device-specific
This command is only a query and thus has no *RST value assigned.
1065.6016.12
6.53
E-16
CALCulate Subsystem
FSE
:CALCulate<1|2>:MARKer<1 to 4>:FUNCtion:SUMMary:PPEak[:STATe]
ON | OFF
This command switches on or off the measurement of the positive peak value if the calculation and.
Example:
":CALC:MARK:FUNC:SUMM:PPE ON"
Features:
*RST value:
OFF
SCPI:
device-specific
Mode:
VA
When the measurement is switched on, the summary marker is automatically activated (command
SUMMary:STATe set to ON). When it is switched off, the summary marker remains switched on
provided further measurements are selected. Otherwise the marker is switched off automatically.
:CALCulate<1|2>:MARKer<1 to 4>:FUNCtion:SUMMary:PPEak:RESult?
This command is used to query the result of the measurement of the positive peak value. Results of
average calculation and peak hold are queried with commands ...:PPEak:AVERage:RESult?
and ...:PPEak:PHOLd:RESult?.
Example:
":CALC:MARK:FUNC:SUMM:PPE:RES?"
Features:
*RST value:
SCPI:
device-specific
Mode:
VA
This command is only a query and thus has no *RST value assigned.
:CALCulate<1|2>:MARKer<1 to 4>:FUNCtion:SUMMary:PPEak:AVERage:RESult?
This command is used to query the result of the measurement of the positive peak value if the
average is calculated using the command :CALCulate<1|2>:MARKer<1 to 4>:FUNCtion:
SUMMary:AVERage.
Example:
":CALC:MARK:FUNC:SUMM:PPE:AVER:RES?"
Features:
*RST value:
SCPI:
device-specific
Mode:
VA
This command is only a query and thus has no *RST value assigned.
:CALCulate<1|2>:MARKer<1 to 4>:FUNCtion:SUMMary:PPEak:PHOLd:RESult?
This command is used to query the result of the measurement of the positive peak value if the peak
hold function is switched on with command :CALCulate<1|2>:MARKer<1 to 4>:FUNCtion:
SUMMary:PHOLd.
Example:
":CALC:MARK:FUNC:SUMM:PPE:PHOL:RES?"
Features:
*RST value:
SCPI:
device-specific
Mode:
VA
This command is only a query and thus has no *RST value assigned.
1065.6016.12
6.54
E-16
FSE
CALCulate Subsystem
:CALCulate<1|2>:MARKer<1 to 4>:FUNCtion:SUMMary:MPEak[:STATe] ON | OFF
This command switches on or off the measurement of the negative peak value.
Example:
":CALC:MARK:FUNC:SUMM:MPE ON"
Features:
*RST value:
OFF
SCPI:
device-specific
Mode:
VA
When the measurement is switched on, the summary marker is automatically activated (command
SUMMary:STATe set to ON). When it is switched off, the summary marker remains switched on
provided further measurements are selected. Otherwise the marker is switched off automatically.
:CALCulate<1|2>:MARKer<1 to 4>:FUNCtion:SUMMary:MPEak:RESult?
This command queries the result of the measurement of the negative peak value. Results of average
calculation and peak hold are queried with commands ...:MPEak:AVERage:RESult? and
...:MPEak:PHOLd:RESult?.
Example:
":CALC:MARK:FUNC:SUMM:MPE:RES?"
Features:
*RST- value: SCPI:
device-specific
Mode:
VA
This command is only a query and thus has no *RST value assigned.
:CALCulate<1|2>:MARKer<1 to 4>:FUNCtion:SUMMary:MPEak:AVERage:RESult?
This command queries the result of the measurement of the negative peak value if the average is
calculated using the command :CALCulate<1|2>:MARKer<1 to 4>:FUNCtion:
SUMMary:AVERage.
Example:
":CALC:MARK:FUNC:SUMM:MPE:AVER:RES?"
Features:
*RST- value: SCPI:
device-specific
Mode:
VA
This command is only a query and thus has no *RST value assigned.
:CALCulate<1|2>:MARKer<1 to 4>:FUNCtion:SUMMary:MPEak:PHOLd:RESult?
This command queries the result of the measurement of the negative peak value if the peak hold
function is switched on with command :CALCulate<1|2>:MARKer<1 to 4>:
FUNCtion:SUMMary:PHOLd.
Example:
":CALC:MARK:FUNC:SUMM:MPE:RES?"
Features:
*RST- value: SCPI:
device-specific
Mode:
VA
This command is only a query and thus has no *RST value assigned.
1065.6016.12
6.55
E-16
CALCulate Subsystem
FSE
:CALCulate<1|2>:MARKer<1 to 4>:FUNCtion:SUMMary:MIDDle[:STATe] ON | OFF
This command switches on or off the measurement of the arithmetical mean between positive and
negative peak value.
Example:
":CALC:MARK:FUNC:SUMM:MIDD ON"
Features:
*RST value:
OFF
SCPI:
device-specific
Mode:
VA
When the measurement is switched on, the summary marker is automatically activated (command
SUMMary:STATe set to ON). When it is switched off, the summary marker remains switched on
provided further measurements are selected. Otherwise the marker is switched off automatically.
:CALCulate<1|2>:MARKer<1 to 4>:FUNCtion:SUMMary:MIDDle:RESult?
This command queries the result of the measurement of the arithmetical mean between positive and
negative peak value. Results of average calculation and peak hold are queried with commands
...:MIDDle:AVERage:RESult? and ...:MIDDle:PHOLd:RESult?.
Example:
":CALC:MARK:FUNC:SUMM:MIDD:RES? "
Features:
*RST- value: SCPI:
device-specific
Mode:
VA
This command is only a query and thus has no *RST value assigned
:CALCulate<1|2>:MARKer<1 to 4>:FUNCtion:SUMMary:MIDDle:AVERage:RESult?
This command queries the result of the measurement of the arithmetical mean between positive and
negative peak value if the average is calculated using the command :CALCulate<1|2>:
MARKer<1 to 4>:FUNCtion:SUMMary:AVERage.
Example:
":CALC:MARK:FUNC:SUMM:MIDD:AVER:RES? "
Features:
*RST- value: SCPI:
device-specific
Mode:
VA
This command is only a query and thus has no *RST value assigned
:CALCulate<1|2>:MARKer<1 to 4>:FUNCtion:SUMMary:MIDDle:PHOLd:RESult?
This command queries the result of the measurement of the arithmetical mean between positive and
negative peak value if the peak hold function is switched on using the command
:CALCulate<1|2>:MARKer<1 to4>:FUNCtion:SUMMary:PHOLd.
Example:
":CALC:MARK:FUNC:SUMM:MIDD:PHOL:RES? "
Features:
*RST- value: SCPI:
device-specific
Mode:
VA
This command is only a query and thus has no *RST value assigned
1065.6016.12
6.56
E-16
FSE
CALCulate Subsystem
:CALCulate<1|2>:MARKer<1 to 4>:FUNCtion:SUMMary:RMS[:STATe] ON | OFF
This command switches on or off the measurement of the effective (rms) value of the total trace.
Example:
":CALC:MARK:FUNC:SUM:RMS ON"
Features:
*RST value:
OFF
SCPI:
device-specific
Modes:
A-Z, VA
When the measurement is switched on, the summary marker is automatically activated (command
SUMMary:STATe set to ON). When it is switched off, the summary marker remains switched on
provided further measurements are selected. Otherwise the marker is switched off automatically.
:CALCulate<1|2>:MARKer<1 to 4>:FUNCtion:SUMMary:RMS:RESult?
This command queries the result of the measurement of the mean value of the total trace. Results of
average calculation and peak hold are queried with commands ...:RMS:AVERage:RESult? and
...:RMS:PHOLd:RESult?..
Example:
":CALC:MARK:FUNC:SUMM:RMS:RES?"
Features:
*RST- value: SCPI:
device-specific
Modes:
A-Z, VA
This command is only a query and thus has no *RST value assigned.
:CALCulate<1|2>:MARKer<1 to 4>:FUNCtion:SUMMary:RMS:AVERage:RESult?
This command queries the result of the measurement of the mean value of the total trace if the
average is calculated using the command :CALCulate<1|2>:MARKer<1 to 4>:FUNCtion:
SUMMary:AVERage.
Example:
":CALC:MARK:FUNC:SUMM:RMS:AVER:RES?"
Features:
*RST- value: SCPI:
device-specific
Modes:
A-Z, VA
This command is only a query and thus has no *RST value assigned.
:CALCulate<1|2>:MARKer<1 to 4>:FUNCtion:SUMMary:RMS:PHOLd:RESult?
This command queries the result of the measurement of the mean value of the total trace if the peak
hold function is switched on using the command :CALCulate<1|2>:MARKer<1 to 4>:
FUNCtion:SUMMary:PHOLd.
Example:
":CALC:MARK:FUNC:SUMM:RMS:PHOL:RES?"
Features:
*RST- value: SCPI:
device-specific
Modes:
A-Z, VA
This command is only a query and thus has no *RST value assigned.
1065.6016.12
6.57
E-16
CALCulate Subsystem
FSE
:CALCulate<1|2>:MARKer<1 to 4>:FUNCtion:SUMMary:MEAN[:STATe] ON | OFF
This command switches on or off the measurement of the mean value of the total trace.
Example:
":CALC:MARK:FUNC:SUMM:MEAN ON"
Features:
*RST value:
OFF
SCPI:
device-specific
Modes:
A-Z, VA
When the measurement is switched on, the summary marker is automatically activated (command
SUMMary:STATe set to ON). When it is switched off, the summary marker remains switched on
provided further measurements are selected. Otherwise the marker is switched off automatically.
:CALCulate<1|2>:MARKer<1 to 4>:FUNCtion:SUMMary:MEAN:RESult?
This command queries the result of the measurement of the mean value of the total trace. Results of
average calculation and peak hold are queried with commands ...:MEAN:AVERage:RESult? and
...:MEAN:PHOLd:RESult?..
Example:
":CALC:MARK:FUNC:SUMM:MEAN:RES?"
Features:
*RST- value: SCPI:
device-specific
Modes:
A-Z, VA
This command is only a query and thus has no *RST value assigned.
:CALCulate<1|2>:MARKer<1 to 4>:FUNCtion:SUMMary:MEAN:AVERage:RESult?
This command queries the result of the measurement of the mean value of the total trace if the
average is calculated using the command :CALCulate<1|2>:MARKer<1 to 4>:FUNCtion:
SUMMary:AVERage.
Example:
":CALC:MARK:FUNC:SUMM:MEAN:AVER:RES?"
Features:
*RST- value: SCPI:
device-specific
Modes:
A-Z, VA
This command is only a query and thus has no *RST value assigned.
:CALCulate<1|2>:MARKer<1 to 4>:FUNCtion:SUMMary:MEAN:PHOLd:RESult?
This command queries the result of the measurement of the mean value of the total trace if the peak
hold function is switched on using the command :CALCulate<1|2>:MARKer<1 to 4>:
FUNCtion:SUMMary:PHOLd.
Example:
":CALC:MARK:FUNC:SUMM:MEAN:PHOL:RES?"
Features:
*RST- value: SCPI:
device-specific
Modes:
A-Z, VA
This command is only a query and thus has no *RST value assigned.
1065.6016.12
6.58
E-16
FSE
CALCulate Subsystem
:CALCulate<1|2>:MARKer<1 to 4>:FUNCtion:SUMMary:PHOLd ON | OFF
This command switches on or off the peak-hold function.
Example:
":CALC:MARK:FUNC:SUMM:PHOL ON"
Features:
*RST value:
OFF
SCPI:
device-specific
Modes:
A-Z, VA
The peak-hold function is reset by switching off and on, again.
:CALCulate<1|2>:MARKer<1 to 4>:FUNCtion:SUMMary:AVERage ON | OFF
This command switches the calculation of the average value on or off.
Example:
":CALC:MARK:FUNC:SUMM:AVER ON"
Features:
*RST value:
OFF
SCPI:
device-specific
Modes:
A-Z, VA
The calculation of the average is reset by switching off and on, again.
:CALCulate<1|2>:MARKer<1 to 4>:FUNCtion:SUMMary:AOFF
This command switches off all measuring functions.
Example:
":CALC:MARK:FUNC:SUMM:AOFF"
Features:
*RST value:
_
SCPI:
device-specific
Modes:
A-Z, VA
This command is an "event" and therefore has no *RST value assigned and no query.
:CALCulate<1|2>:MARKer<1 to 4>:FUNCtion:CENTer
This command sets the center frequency to that of the current marker.
Example:
":CALC:MARK:FUNC:CENT"
Features:
*RST value:
SCPI:
device-specific
Mode:
A-F
This command is an "event" and therefore has no *RST value assigned and no query.
:CALCulate<1|2>:MARKer<1 to 4>:FUNCtion:CSTep
This command sets the step width of the center frequency to the x-value of the current marker.
Example:
":CALC:MARK:FUNC:CST"
Features:
*RST value:
SCPI:
device-specific
Mode:
A-F
This command is an "event" and therefore has no *RST value assigned and no query.
1065.6016.12
6.59
E-16
CALCulate Subsystem
FSE
:CALCulate<1|2>:MARKer<1 to 4>:FUNCtion:STARt
This command sets the start frequency to the frequency of the current marker.
Example:
":CALC:MARK:FUNC:STAR"
Features:
*RST value:
SCPI:
device-specific
Mode:
A-F
This command is an "event" which is why it is not assigned an *RST value and has no query.
:CALCulate<1|2>:MARKer<1 to 4>:FUNCtion:STOP
This command sets the stop frequency to the frequency of the current marker.
Example:
":CALC:MARK:FUNC:STOP"
Features:
*RST value:
SCPI:
device-specific
Mode:
A-F
This command is an "event" which is why it is not assigned an *RST value and has no query.
:CALCulate<1|2>:MARKer<1 to 4>:FUNCtion:MSTep
This command sets the marker step width to the x-value of the current marker.
Example:
":CALC:MARK:FUNC:MST"
Features:
*RST value:
SCPI:
device-specific
Modes:
A, VA
This command is an "event" which is why it is not assigned an *RST value and has no query.
:CALCulate<1|2>:MARKer<1 to 4>:FUNCtion:REFerence
This command sets the reference level to that of the current marker.
Example:
":CALC:MARK:FUNC:REF"
Features:
*RST value:
SCPI:
device-specific
Modes:
A, VA
This command is an "event" and therefore has no *RST value assigned and no query.
This command is an and has therefore neither *RST value nor query. The numeric suffixes
in CALCulate<1|2> and MARKer<1 to 4> are not significant.
1065.6016.12
6.60
E-16
FSE
CALCulate Subsystem
CALCulate:MATH Subsystem
The CALCulate:MATH - subsystem allows to process data from the SENSe-subsystem in numeric
expressions.
COMMAND
PARAMETERS
UNIT
COMMENT
CALCulate<1|2>
:MATH<1 to 4>
[:EXPRession]
[:DEFine]
:STATe
---
:CALCulate<1|2>:MATH<1 to 4>[:EXPression][:DEFine]
This command defines the mathematical expression for relating traces and reference line. Command
CALCulate:MATH:STATe switches the mathematical relation of traces on or off .
Parameter:
::= ‘OP1 - OP2 [ + RLINE]’
OP1 ::= TRACE1 | TRACE2 | TRACE3 | TRACE4
OP2 ::= TRACE1 | TRACE2 | TRACE3 | TRACE4 | RLINE
Examples:
":CALC:MATH1 (TRACE1 - TRACE3 + RLINE)"
":CALC:MATH4 (TRACE4 - RLINE)"
Features:
*RST value:
SCPI:
Modes:
A, VA
conforming
The operand [+ RLINE] may be used only if OP2 is different from RLINE. The numeric suffix in
CALCULATE<1|2> is not significant. The numeric suffix in MATH<1 to 4> denotes the trace where
the result of the mathematical operation is stored. The number must be identical to the number of the
operand OP1.
:CALCulate<1|2>:MATH<1 to 4>:STATe ON | OFF
This command switches the mathematical relation of traces on or off.
Example:
":CALC:MATH1:STAT ON"
Features:
*RST value:
SCPI:
Modes:
A, VA
OFF
conforming
The numeric suffix in CALCULATE<1|2> is not significant. The numeric suffix in MATH<1 to 4>
denotes the trace which the command refers to.
1065.6016.12
6.61
E-16
CALCulate Subsystem
FSE
CALCulate:X and CALCulate:UNIT Subsystem
The CALCulate:X and CALCulate:Unit subsystems define the units for vector signal analyzer mode and
power measurements.
COMMAND
PARAMETERS
CALCulate<1|2>
:X
:UNIT
:TIME
:UNIT
:ANGLe
:POWer
UNIT
COMMENT
Vector Signal Analysis
S | SYM
DEG | RAD
DBM | V | W | DB |
PCT | UNITLESS |
DBPW | WATT |
DBUV | DBMV | VOLT |
DBPT | DBUA | AMPere
DBUV_MHZ | DBMV_MHZ |
DBUA_MHZ | DBUV_M | DBUA_M |
DBUV_MMHZ | DBUA_MMHZ
Vector Signal Analysis
:CALCulate<1|2>:X:UNIT:TIME S | SYM
This command selects seconds or symbols as an x-axis unit.
Example:
":CALC:X:UNIT:TIME S"
Features:
*RST value:
SCPI:
Mode:
VA-D
:CALCulate<1|2>: UNIT:ANGLe
S
device-specific
DEG | RAD
This command selects the unit for angular measurement.
Example:
":CALC:UNIT:ANGL DEG"
Features:
*RST- value:
SCPI:
Mode:
VA-D
:CALCulate<1|2>: UNIT:POWer
RAD
device-specific
DBM | V | W | DB | PCT | DBPT | UNITLESS | DBPW | WATT |
DBUV |DBMV | VOLT | DBUA | AMPere | DBUV_MHZ |DBMV_MHZ|
DBUA_MHZ | DBUV_M | DBUA_M |DBUV_MMHZ | DBUA_MMHZ
This command selects the unit for power.
Example:
":CALC:UNIT:POW DBM"
Features:
*RST value:
SCPI:
Modes:
A, VA
_
device-specific
The units DEG, RAD, S, and HZ are available only in the vector analyzer mode.
DBUV_MHZ and DBUA_MHZ denote the units DBUV/MHZ or DBUA/MHZ.
1065.6016.12
6.62
E-16
FSE
CALibration Subsystem
CALibration Subsystem
The commands of the CALibration subsystem perform instrument calibrations.
COMMAND
PARAMETERS
CALibration
[:ALL]?
:BANDwidth
[:RESolution]?
:BWIDth
[:RESolution]?
:IQ?
UNIT
COMMENT
--
--
query only
--
--
query only
---
---
:LDETector?
:LOSuppression?
---
---
query only
query only /
Vector Signal Analysis
query only
query only
:PPEak?
--
--
:SHORt?
:STATe
-
---
query only
FSEM/FSEK only
query only
::CALibration[:ALL]?
This command performs a complete calibration of the instrument. A "0" is returned if the calibration
was successful.
Example:
"CAL?"
Features:
*RST value:
SCPI:
Modes:
A, VA, BTS, MS
conforming
:CALibration:BANDwidth | BWIDth[:RESolution]?
This command performs a calibration of the filter bandwidths. A "0" is returned if the calibration was
successful.
Example:
":CAL:BAND?"
Features:
*RST value:
SCPI:
Modes:
A, VA, BTS, MS
device-specific
:CALibration:IQ?
This command performs a calibration of the vector signal analyzer. A "0" is returned if the calibration
was successful.
Example:
":CAL:IQ?"
features:
*RST value:
SCPI:
Modes:
VA, BTS, MS
1065.6016.12
device-specific
6.63
E-16
CALibration Subsystem
FSE
:CALibration:LDETector?
This command performs a calibration of the log module’s characteristic and of the detectors. A "0" is
returned if the calibration was successful.
Example:
":CAL:LDET?"
Features:
*RST value:
SCPI:
Modes:
A, VA, BTS, MS
device-specific
:CALibration:LOSuppression?
This command performs a calibration of the local oscillator suppression. . A "0" is returned if the
calibration was successful.
Example:
":CAL:LOS?"
Features:
*RST value:
SCPI:
Modes:
A, VA, BTS, MS
device-specific
This command is only valid by model ‘30 instruments or by instruments which have been retrofitted.
:CALibration:PPEak?
This command performs a calibration of the tracking YIG filter (preselector peaking). A "0" is
returned if the calibration was successful.
Example:
":CAL:PPE?"
Features:
*RST value:
SCPI:
Modes:
A
device-specific
This command is only valid by the models FSEM and FSEK.
:CALibration:SHORt?
This command performs a short calibration. A "0" is returned if the calibration was successful.
Example:
":CAL:SHOR?"
Features:
*RST value:
SCPI:
Modes:
A, VA, BTS, MS
device-specific
:CALibration:STATe ON | OFF
This command determines whether (ON) or not (OFF) the current calibration data are taken into
consideration.
Example:
":CAL:STAT OFF"
Features:
*RST value:
SCPI:
Modes:
A, VA, BTS, MS
1065.6016.12
conforming
6.64
E-16
FSE
CONFigure-Subsystem
CONFigure Subsystem
The CONFigure subsystem contains commands for configuring complex measurement tasks, like those
provided by the options GSM BTS Analyzer (FSE-K11) or GSM MS Analyzer (FSE-K10). The
CONFigure subsystem is closely linked to the functions of the FETCH and READ subsystems, where
the measurement cycles are started and/or the results of the measurements are queried.
CONFigure:BTS Subsystem
This subsystem provides the commands for configuring the GSM BTS Analyzer mode (Option FSE-K11)
for analyzing the behavior of base stations corresponding to the standards P-GSM, E-GSM, R-GSM,
DCS1800 or PCS1900. EDGE measurement require option FSE-K21, and tests in the GSM 850 MHz
band option FSE-K31.
COMMAND
CONFigure
[:BTS]
:MEASurement?
:ARFCn
:AUTO
:LIMit
:PPEak
:PRMS
:EVMRms
:EVMPeak
:OSUPpress
:PERCentile
:FREQuency
:STANdard
:POWer
:CLASs
:COUPled
:STATic
:DYNamic
:EXPected
:LIMit
:SINGle
[:STATe]
:CLEar
:CHANnel
:SLOT
:AUTO
:TSC
:AUTO
:SFH
:NETWork
[:TYPE]
:PHASe
:COSiting
:TXSupp
:PRESet
:SWEeptime
:MTYPe
:STYPe
1065.6016.12
PARAMETERS
UNIT
COMMENT
Option FSE-K11/K21/31
query only
ONCE
--
DEG
DEG
no query
PCT
PCT
DB
PCT
ppm
| M1 | M2 | M3 | P1 |
EG1 | EG2 | EG3
---DBM
DBM
--
no query
ONCE
PGSM | PGSM900| EGSM |
EGSM900 | DCS | GSM1800 |
PCS | GSM1900 | RGSM |
RGSM900 | GSM850
1|2[,PLUS]
-STANdard | AUTO
GMSK | EDGE
NORMal | MICRo | PICO
6.65
--
no query
--
no query
no query
E-16
CONFigure-Subsystem
FSE
:CONFigure[:BTS]:MEASurement?
This command queries which measurement is currently set.
PFERror
MACCuracy
POWer
PTEMplate
MODulation
SWITching
SPURious
Phase-/Frequency Error
Modulation Accuracy
Carrier Power
Power v. Time
Modulation Spectrum
Transient Spectrum
Spurious
Example:
":CONF:MEAS?"
Features:
*RST-value: SCPI:
device-specific
Mode:
BTS
Answer: "PFER"
This command is a query and has therefore no *RST value assigned.
:CONFigure[:BTS]:ARFCn
This command selects the number of the transmission channel of the base station.
Parameter:
::=
Example:
":CONF:ARFC 67"
Features:
*RST value:
SCPI:
Mode:
1 to 124
0 to 124, 975 to 1023
0 to 124, 955 to 1023
512 to 885
512 to 810
128 to 251
(P-GSM phase I/II)
(E-GSM)
(R-GSM)
(DCS1800 phase I/II/II+)
(PCS1900)
(GSM850)
1
(P-GSM phase I/II)
0
(E-GSM; R-GSM)
512
(DCS1800 phase I/II/II+)
512
(PCS1900)
128
(GSM850)
device-specific
BTS
:CONFigure[:BTS]:ARFCn:AUTO
ONCE
This command is used to search for the channel number of the transmission channel of the base
station automatically. This requires only one channel to be active.
Example:
":CONF:ARFC:AUTO ONCE"
Features:
*RST value:
SCPI:
Mode:
BTS
-device-specific
This command is an event and thus has no query and no *RST value assigned.
1065.6016.12
6.66
E-16
FSE
CONFigure-Subsystem
:CONFigure[:BTS]:LIMit:PPEak
This command determines the phase error limits in degrees for the phase/frequency measurement
(peak value).
Example:
":CONF:LIM:PPE 66"
Feature:
*RST value:
SCPI:
Mode:
BTS
depending on standard
device-specific
:CONFigure[:BTS]:LIMit:PRMS
This command determines the phase error limits in degrees for the phase/frequency measurement
(mean value).
Example:
":CONF:LIM:PRMS 22"
Feature:
*RST value:
SCPI:
Mode:
BTS
Betriebsart:
BTS
depending on standard
device-specific
CONFigure[:BTS]:LIMit:EVMRms
This command determines the value in percent for the error limits of error vector magnitude
measurement with RMS weighting.
Example:
":CONF:LIM:EVMR 40"
Features:
*RST value
SCPI:
Mode:
BTS
depending on the standard
device-specific
CONFigure[:BTS]:LIMit:EVMPeak
This command determines the value in percent for the error limits of error vector magnitude
measurement with PEAK weighting.
Example:
":CONF:LIM:EVMP 30"
Features:
*RST value
SCPI:
Mode:
BTS
depending on the standard
device-specific
:CONFigure[:BTS]:LIMit:OSUPpress
This command defines the limit for the origin offset suppression.
Example:
":CONF:LIM:OSUP 30"
Features:
*RST value
SCPI:
Mode:
BTS
1065.6016.12
depending on the standard
device-specific
6.67
E-16
CONFigure-Subsystem
FSE
:CONFigure[:BTS]:LIMit:PERCentile
This command determines the 95% percentile limits. The percentile defines the value which the EVM
may exceed 5% of all symbols at maximum.
Example:
":CONF:LIM:PERC 30"
Features:
*RST value
SCPI:
Mode:
BTS
depending on the standard
device-specific
:CONFigure[:BTS]:LIMit:FREQuency
This command determines the frequency error limits in ppm for the phase/frequency measurement.
Example:
":CONF:LIM:FREQ 36"
Feature:
*RST value:
SCPI:
Mode:
BTS
depending on standard
device-specific
:CONFigure[:BTS]:LIMit:STANdard ON | OFF
This command switches between user-defined (OFF) and standard-defined (ON) limit values.
Example:
":CONF:LIM:STAN ON"
Feature:
*RST value:
SCPI:
Mode:
BTS
:CONFigure[:BTS]:POWer:CLASs
ON
device-specific
| M1 | M2 | M3 | P1
This command defines the power class of the base station.
Parameter:
M1, M2, M3
P1
Example:
":CONF:POW:CLAS 4"
Features:
*RST value:
SCPI:
Mode:
::= 1 to 8 (P-GSM phase I/II, E-GSM, R-GSM, GSM850)
::= 1 to 4 (PCS1900, DCS1800 phase I/II/II+)
::= Power Classes for Micro BTS
::= Power Class for Pico BTS
4
(P-GSM phase I/II, E-GSM, R-GSM, GSM850)
1
(DCS1800, PCS1900)
device-specific
BTS
:CONFigure[:BTS]:POWer:COUPled ON | OFF
This command switches between user-defined (OFF) and standard-defined (ON) level values.
Example:
":CONF:POW:COUP ON"
Feature:
*RST value:
SCPI:
Mode:
BTS
1065.6016.12
ON
device-specific
6.68
E-16
FSE
CONFigure-Subsystem
:CONFigure[:BTS]:POWer:STATic 0 to 6
This command defines the static power control level of the base station.
Example:
":CONF:POW:STAT 3"
Features:
*RST value:
SCPI:
Mode:
BTS
0
device-specific
:CONFigure[:BTS]:POWer:DYNamic 0 to 15
This command defines the dynamic power control level of the base station.
Example:
":CONF:POW:DYN 5"
Features:
*RST value:
SCPI:
Mode:
BTS
0
device-specific
:CONFigure[:BTS]:POWer:EXPected
This command enters directly the rated output level of the base station specified by the
manufacturer.
Example:
":CONF:POW:EXP 43DBM"
Features:
*RST value:
SCPI:
Mode:
46 dBm (P-GSM phase I/II, E-GSM, R-GSM)
43 dBm (DCS1800, PCS1900)
device-specific
BTS
:CONFigure[:BTS]:POWer:LIMit
This command defines the level for the selection of level-dependent limit lines.
Example:
":CONF:POW:LIM 65DBM"
Feature:
*RST value:
SCPI:
Mode:
BTS
depending on standard
device-specific
This command is only available for the setting :CONFigure[:BTS]:POWer:COUPled OFF.
:CONFigure[:BTS]:POWer:SINGle[:STATe] ON | OFF
This command switches single measurement of carrier power on and off.
Example:
":CONF:POW:SING ON"
Feature:
*RST value:
SCPI:
Mode:
BTS
1065.6016.12
OFF
device-specific
6.69
E-16
CONFigure-Subsystem
FSE
:CONFigure[:BTS]:POWer:SINGle:CLEar
This command clears the table containing the single-step carrier power measurements.
Example:
":CONF:POW:SING:CLE"
Feature:
*RST value:
SCPI:
Mode:
BTS
-device-specific
This command is an event and has therefore neither *RST value nor query.
:CONFigure[:BTS]:CHANnel:SLOT
0 to 7
This command selects the slot number within a transmission frame of the base station.
Example:
":CONF:CHAN:SLOT 3"
Features:
*RST value:
SCPI:
Mode:
BTS
0
device-specific
On changing the slot number, the number of the midamble (TSC) is automatically adapted to the slot.
:CONFigure[:BTS]:CHANnel:SLOT:AUTO ONCE
This command automatically searches for the slot number within a transmission frame of the base
station. This requires only one slot to be active.
Example:
":CONF:CHAN:SLOT:AUTO ONCE"
Features:
*RST value:
SCPI:
Mode:
BTS
-device-specific
This command is an event and thus has no query and no *RST value assigned.
:CONFigure[:BTS]:CHANnel:SFH
ON | OFF
This command defines whether the base station uses slow frequency hopping or not.
Example:
":CONF:CHAN:SFH ON"
Features:
*RST value:
SCPI:
Mode:
BTS
OFF
device-specific
This command is available only when spurious or transient spectrum measurement is selected. The
settings for spurious measurement are independent from those selected for transient spectrum.
1065.6016.12
6.70
E-16
FSE
CONFigure-Subsystem
:CONFigure[:BTS]:CHANnel:TSC:AUTO
ON | OFF
This command couples the midamble (training sequence TSC_0 to 7) to the slot, i.e. if the slot
number is changed the training sequence in the ON state is automatically adapted. In the OFF state,
the training sequence set is conserved even if the slot number is changed.
Example:
":CONF:CHAN:TSC:AUTO ON"
Features:
*RST value:
SCPI:
Mode:
BTS
:CONFigure[:BTS]:CHANnel:TSC
ON
device-specific
0 to 7
This command selects the midamble (training sequence TSC_0 to 7) of the active slot.
Example:
":CONF:CHAN:TSC 3"
Features:
*RST value:
SCPI:
Mode:
BTS
0
device-specific
:CONFigure[:BTS]:NETWork[:TYPE]
PGSM | PGSM900 | EGSM | EGSM900 | DCS |GSM1800 |
PCS | GSM1900 | RGSM | RGSM900 | GSM850
This command selects the standard type according to which the base station will work.
Example:
":CONF:NETW DCS"
Features:
*RST value:
SCPI:
Mode:
BTS
GSM
device-specific
:CONFigure[:BTS]:NETWork:PHASe 1|2 [,PLUS]
This command selects the phase of the standard according to which the base station will work.
Example:
":CONF:NETW:PHAS 2"
Features:
*RST value:
SCPI:
Mode:
BTS
1
device-specific
:CONFigure[:BTS]:COSiting ON | OFF
This command selects whether the base station has the "cositing" feature.
Example:
":CONF:COS ON"
Features:
*RST value:
SCPI:
Mode:
BTS
OFF
device-specific
This command is available only if spurious emission measurement is selected.
1065.6016.12
6.71
E-16
CONFigure-Subsystem
:CONFigure[:BTS]:TXSupp
FSE
ON | OFF
This command defines that an additional carrier suppression of min. 20dB is taken into account for
the measurement. If there is already suppression, a more sensitive setting of the instrument is
selected.
Example:
":CONF:TXS ON"
Features:
*RST value:
SCPI:
Mode:
BTS
OFF
device-specific
For measurements in the RX-band the value is automatically set to ON.
:CONFigure[:BTS]:PRESet
This command resets the parameters for the standard selected to their default values (DEFAULT
SETTINGS).
Example:
":CONF:PRES"
Features:
*RST value:
SCPI:
Mode:
BTS
-device-specific
This command is an event and has thus no query and no *RST value assigned.
:CONFigure[:BTS]:SWEeptime STANdard | AUTO
This command selects the sweep-time computing mode for the spurious measurement:
Example:
":CONF:SWE AUTO"
Feature:
*RST value:
SCPI:
Mode:
BTS
STANdard
The computation of the sweep time is based on a worst-case estimation
AUTO
The sweep time is reduced by a factor of 8 (assuming all slots are on).
STANdard
device-specific
CONFigure[:BTS]:MTYPe GMSK | EDGE
This command selects the modulation type (GMSK or EDGE (8PSK)).
Example:
":CONF:MTYP EDGE"
Features:
**RST value:
SCPI:
Mode:
BTS
GMSK
device-specific
CONFigure[:BTS]:STYPe NORMal | MICRo | PICO
This comman selects the type of base station.
Example:
":CONF:STYP PICO"
Features:
*RST value:
SCPI:
Mode:
BTS
1065.6016.12
NORM
device-specific
6.72
E-16
FSE
CONFigure-Subsystem
CONFigure:BURSt Subsystem
This subsystem provides the commands for configuring the measurements in the GSM BTS Analyzer
mode (option FSE-K11) or GSM MS Analyzer mode (option FSE-K10) which are performed on individual
bursts. (carrier power, phase/frequency error, power vs. time).
COMMAND
CONFigure
:BURSt
:PFERror
[:IMMediate]
:COUNt
:CONDition
:MACCuracy
[:IMMediate]
:COUNt
:CONDition
:POWer
[:IMMediate]
:COUNt
:CONDition
:PTEMplate
[:IMMediate]
:COUNt
:SELect
:REFerence
:AUTO
PARAMETERS
UNIT
-
NORMal | EXTReme
---
-
NORMal | EXTReme
---
COMMENT
no query, Option FSE-K11 or FSE-K10 &
FSE-B7
Option FSE-K11 or FSE-K10
Option FSE-K11 or FSE-K10
no query
Option FSE-K11 or FSE-K10 & FSE-B7
No query
-
NORMal | EXTReme
---
-
FULL | TOP | RISing | FALLing
Option FSE-K11 or FSE-K10
no query
--Option FSE-K11 or FSE-K10
no query
:CONFigure:BURSt:PFERror[:IMMediate]
This command selects measurement of the phase and frequency error of the base station or mobile.
Example:
":CONF:BURS:PFER"
Features:
*RST value:
SCPI:
Modes:
BTS, MS
-device-specific
This command is an event and thus has no query and no *RST value assigned.
It is available only in conjunction with option GSM BTS Analyzer FSE-K11 or option GSM MS
Analyzer, FSE-K10, and Vector Signal Analysis, FSE-B7.
:CONFigure:BURSt:PFERror:COUNt 1 to 1000
This command sets the number of bursts used for the determination of average and maximum value.
Example:
":CONF:BURS:PFER:COUN 100"
Features:
*RST value:
SCPI:
Modes:
500 (GSM/DCS1800 Phase I)
200 otherwise
device-specific
BTS, MS
It is available only in conjunction with option GSM BTS Analyzer FSE-K11 or option GSM MS
Analyzer, FSE-K10, and Vector Signal Analysis, FSE-B7.
1065.6016.12
6.73
E-16
CONFigure-Subsystem
FSE
:CONFigure:BURSt:PFERror:CONDition NORMal | EXTReme
This command defines the conditions for phase-frequency measurement.
Example:
":CONF:BURS:PFER:COND EXTR"
Features:
*RST value:
SCPI:
Modes:
BTS, MS
NORMal
device-specific
:CONFigure:BURSt:MACCuracy[:IMMediate]
This command selects measurement of the measurement accuracy of the base station or mobile.
Example:
":CONF:BURS:MACC"
Features:
*RST value:
SCPI:
Modes:
BTS, MS
-device-specific
This command is an event and thus has no query and no *RST value assigned.
It is available only in conjunction with option GSM BTS Analyzer FSE-K11 or option GSM MS
Analyzer, FSE-K10, and Vector Signal Analysis, FSE-B7.
:CONFigure:BURSt:MACCuracy:COUNt 1 to 1000
This command sets the number of bursts used for the determination of average and maximum value.
Example:
":CONF:BURS:MACC:COUN 100"
Features:
*RST value:
SCPI:
Modes:
BTS, MS
1
device-specific
It is available only in conjunction with option GSM BTS Analyzer FSE-K11 or option GSM MS
Analyzer, FSE-K10, and Vector Signal Analysis, FSE-B7.
:CONFigure:BURSt:MACCuracy:CONDition NORMal | EXTReme
This command defines the conditions for modulation accuracy measurement.
Example:
":CONF:BURS:MACC:COND EXTR"
Features:
*RST value:
SCPI:
Modes:
BTS, MS
1065.6016.12
NORMal
device-specific
6.74
E-16
FSE
CONFigure-Subsystem
:CONFigure:BURSt:POWer[:IMMediate]
This command selects measurement of the average carrier power of the base station or mobile.
Example:
":CONF:BURS:POW"
Features:
*RST value:
SCPI:
Modes:
BTS, MS
-device-specific
This command is an event and thus has no query and no *RST value assigned.
:CONFigure:BURSt:POWer:COUNt
1 to 1000
This command sets the number of bursts used for the determination of measured values.
Example:
":CONF:BURS:POW:COUN 100"
Features:
*RST value:
SCPI:
Modes:
500 (GSM/DCS1800 phase I)
200 otherwise
device-specific
BTS, MS
:CONFigure:BURSt:POWer:CONDition NORMal | EXTReme
This command defines the conditions for power measurement.
Example:
":CONF:BURS:POW:COND EXTR"
Features:
*RST value:
SCPI:
Modes:
BTS, MS
NORMal
device-specific
:CONFigure:BURSt:PTEMplate[:IMMediate]
This command selects measurement of power of the base station or mobile vs. time.
Example:
":CONF:BURS:PTEM"
Features:
*RST value:
SCPI:
Modes:
BTS, MS
-device-specific
This command is an event and thus has no query and no *RST value assigned.
:CONFigure:BURSt:PTEMPlate:COUNt 1 to 1000
This command defines the number of bursts used for determining the measured value.
Example:
":CONF:BURS:PTEM:COUN 100"
Features:
*RST value:
SCPI:
Modes:
1065.6016.12
500 (GSM/DCS1800 phase I)
200 otherwise
device-specific
BTS, MS
6.75
E-16
CONFigure-Subsystem
FSE
:CONFigure:BURSt:PTEMplate:SELect
FULL | TOP | RISing | FALLing
This command defined the burst section to be measured.
Example:
":CONF:BURS:PTEM:SEL TOP"
Features:
*RST value:
SCPI:
Modes:
BTS, MS
FULL
device-specific
:CONFigure:BURSt:REFerence:AUTO ON | OFF
This command switches between automatic and user-activated preview of power versus time. When
switched to AUTO, the preview is always performed, when switched to OFF it is omitted. Note: see
READ:BURSt:REF:IMM
Example:
":CONF:BURS:REF:AUTO ON"
Feature:
*RST value:
SCPI:
Mode:
BTS, MS
1065.6016.12
AUTO
device-specific
6.76
E-16
FSE
CONFigure-Subsystem
CONFigure:MS Subsystem
This subsystem provides the commands for configuring the GSM MS Analyzer mode (Option FSEK10/FSE-K20) for analyzing the behavior of mobiles corresponding to the standards P-GSM, E-GSM, RGSM, DCS1800 or PCS1900. EDGE measurement require option FSE-K20, and tests in the GSM
850 MHz band option FSE-K30.
COMMAND
PARAMETERS
UNIT
COMMENT
CONFigure
option FSE-K10/K20/K30
[:MS]
query only
:MEASurement?
:ARFCn
:AUTO
--
no query
ONCE
:LIMit
:PPEak
DEG
:PRMS
DEG
:EVMRms
PCT
:EVMPeak
PCT
:OSUPpress
DB
:PERCentile
PCT
:FREQuency
ppm
:STANdard
:POWer
:CLASs
| EG1 | EG2 | EG3
| M1 | M2 | M3 | P1
--
:COUPled
--
:LEVel
DBM
:LIMit
DBM
:EXPected
no query
:SINGle
[:STATe]
:CLEar
--
:SMALl
no query
:CHANnel
:SFH
:TSC
--
:NETWork
[:TYPE]
PGSM | PGSM900| EGSM |
EGSM900 | DCS | GSM1800 |
PCS | GSM1900 | RGSM |
RGSM900 | GSM850
:PHASe
1|2[,PLUS]
:TXSupp
:PRESet
--
:SWEeptime
STANdard | AUTO
:MTYPe
GMSK | EDGE
1065.6016.12
no query
6.77
E-16
CONFigure-Subsystem
FSE
:CONFigure[:MS]:MEASurement?
This command queries which measurement is currently set.
PFERror
MACCuracy
POWer
PTEMplate
MODulation
SWITching
SPURious
Phase-/Frequency Error
Modulation Accuracy
Carrier Power
Power v. Time
Modulation Spectrum
Transient Spectrum
Spurious
Example:
":CONF:MEAS?"
Features:
*RST value: SCPI:
Mode:
Answer: "PFER"
device specific
MS
This command is a query and has therefore no *RST value assigned.
:CONFigure[:MS]:ARFCn
This command selects the number of the transmission channel of the mobile.
Parameter:
::=
Example:
":CONF:ARFC 67"
Features:
*RST value:
SCPI:
Mode:
1 to 124
0 to 124, 975 to 1023
0 to 124, 955 to 1023
512 to 885
512 to 810
128 to 251
(P-GSM phase I/II)
(E-GSM)
(R-GSM)
(DCS1800 phase I/II/II+)
(PCS1900)
(GSM850)
1
(P-GSM phase I/II)
0
(E-GSM; R-GSM)
512
(DCS1800 phase I/II/II+)
512
(PCS1900)
128
(GSM850)
device-specific
MS
:CONFigure[:MS]:ARFCn:AUTO ONCE
This command selects automatically the transmission channel of the mobile.
Example:
":CONF:ARFC:AUTO ONCE"
Features:
*RST value:
SCPI:
Mode:
MS
1065.6016.12
device-specific
6.78
E-16
FSE
CONFigure-Subsystem
:CONFigure[:MS]:LIMit:PPEak
This command determines the phase error limits in degrees for the phase/frequency measurement
(peak value).
Example:
":CONF:LIM:PPE 66"
Feature:
*RST value:
SCPI:
Mode:
MS
depending on standard
device-specific
:CONFigure[:MS]:LIMit:PRMS
This command determines the phase error limits in degrees for the phase/frequency measurement
(mean value).
Example:
":CONF:LIM:PRMS 22"
Feature:
*RST value:
SCPI:
Mode:
MS
depending on standard
device-specific
:CONFigure[:MS]:LIMit:EVMRms
This command determines the value in percent for the error limits of error vector magnitude
measurement with RMS weighting.
Example:
":CONF:LIM:EVMR 40"
Features:
*RST value
SCPI:
Mode:
BTS
depending on the standard
device-specific
:CONFigure[:MS]:LIMit:EVMPeak
This command determines the value in percent for the error limits of error vector magnitude
measurement with PEAK weighting.
Example:
":CONF:LIM:EVMP 30"
Features:
*RST value
SCPI:
Mode:
BTS
depending on the standard
device-specific
:CONFigure[:MS]:LIMit:OSUPpress
This command defines the limit for the origin offset suppression.
Example:
":CONF:LIM:OSUP 30"
Features:
*RST value
SCPI:
Mode:
BTS
1065.6016.12
depending on the standard
device-specific
6.79
E-16
CONFigure-Subsystem
FSE
:CONFigure[:MS]:LIMit:PERCentile
This command defines the limit for the 95% percentile.
Example:
":CONF:LIM:PERC 30"
Features:
*RST value
SCPI:
Mode:
BTS
depending on the standard
device-specific
:CONFigure[:MS]:LIMit:FREQuency
This command determines the frequency error limits in ppm for the phase/frequency measurement.
Example:
":CONF:LIM:FREQ 36"
Feature:
*RST value:
SCPI:
Mode:
MS
depending on standard
device-specific
:CONFigure[:MS]:LIMit:STANdard ON | OFF
This command switches between user-defined (OFF) and standard-defined (ON) limit values.
Example:
":CONF:LIM:STAN ON"
Feature:
*RST value:
SCPI:
Mode:
MS
:CONFigure[:MS]:POWer:CLASs
ON
device-specific
| EG1 | EG2 | EG3
This command defines the power class of the mobile.
Parameter:
::=
Example:
":CONF:POW:CLAS 4"
Features:
*RST value:
SCPI:
Mode:
1065.6016.12
1 to 5 (P-GSM phase I)
2 to 5 (P-GSM phase II, R-GSM850)
2 to 5 (E-GSM; R-GSM)
1 to 2 (DCS1800 phase I)
1 to 3 (DCS1800 phase II/II+)
1 to 3 (PCS1900)
2
(P-GSM phase I/II, E-GSM, R-GSM, R-GSM850)
1
(DCS1800, PCS1900)
device-specific
MS
6.80
E-16
FSE
CONFigure-Subsystem
:CONFigure[:MS]:POWer:COUPled ON | OFF
This command switches between user-defined (OFF) and standard-defined (ON) level values.
Example:
":CONF:POW:COUP ON"
Feature: *RST value:
ON
OFF
SCPI:
Mode:
ON
standard
user-defined
device-specific
MS
:CONFigure[:MS]:POWer:LEVel 0 to 31
This command defines the power control level of the mobile.
Example:
":CONF:POW:LEV 5"
Features:
*RST value:
2 (P-GSM Phase I/II, E-GSM, R-GSM, GSM850)
0 (DCS1800, PCS1900)
device-specific
SCPI:
Mode:
MS
:CONFigure[:MS]:POWer:LIMit
This command defines the level for the selection of level-dependent limit lines.
Example:
":CONF:POW:LIM 65DBM"
Feature:
*RST value:
SCPI:
Mode:
MS
depending on standard
device-specific
This command is only available for the setting :CONFigure[:MS]:POWer:COUPled OFF.
:CONFigure[:MS]:POWer:EXPected
This command enters directly the rated output level of the mobile.
Example:
":CONF:POW:EXP 43DBM"
Features:
*RST value:
SCPI:
Mode:
1065.6016.12
GMSK:
39 dBm (P-GSM Phase I/II, E-GSM, R-GSM, GSM850)
30 dBm (DCS1800, PCS1900)
EDGE
33 dBm (P-GSM Phase I/II, E-GSM, R-GSM, GSM850)
30 dBm (DCS1800, PCS1900)
device-specific
MS
6.81
E-16
CONFigure-Subsystem
FSE
:CONFigure[:MS]:POWer:SINGle[:STATe] ON | OFF
This command switches single measurement of carrier power on and off.
Example:
":CONF:POW:SING ON"
Feature:
*RST value:
SCPI:
Mode:
MS
OFF
device-specific
:CONFigure[:MS]:POWer:SINGle:CLEar
This command clears the table containing the single-step carrier power measurements.
Example:
":CONF:POW:SING:CLE"
Feature:
*RST value:
SCPI:
Mode:
MS
-device-specific
This command is an event and has therefore neither *RST value nor query.
:CONFigure[:MS]:POWer:SMALl ON | OFF
This command switches the limits for spurious measurement in the RGSM range. It is only available
for phase 2+.
Example:
":CONF:POW:SMAL ON"
Feature:
*RST value:
SCPI:
Mode:
MS
OFF
device-specific
:CONFigure[:MS]:CHANnel:SFH ON | OFF
This command switches slow-frequency hopping on or off.
Example:
":CONF:CHAN:SFH ON"
Feature:
*RST value:
SCPI:
Mode:
MS
OFF
device-specific
:CONFigure[:MS]:CHANnel:TSC 0 to 7
This command selects the midamble used by the mobile.
Parameter:
0 to 7
Example:
":CONF:CHAN:TSC 3"
Features:
*RST value:
SCPI:
Mode:
MS
1065.6016.12
(training sequence for the Normal Burst)
0
device-specific
6.82
E-16
FSE
CONFigure-Subsystem
:CONFigure[:MS]:NETWork[:TYPE]
PGSM | PGSM900 | EGSM |EGSM900 | DCS |GSM1800 |
PCS|GSM1900 | RGSM | RGSM900 | GSM850
This command selects the standard type according to which the mobile will work.
Example:
":CONF:NETW DCS"
Features:
*RST value:
SCPI:
Mode:
MS
GSM
device-specific
:CONFigure[:MS]:NETWork:PHASe
1 | 2 [,PLUS]
This command selects the phase of the standard according to which the mobile will work.
Example:
":CONF:NETW:PHAS 2"
Features:
*RST value:
SCPI:
Mode:
MS
1
device-specific
:CONFigure[:MS]:TXSupp ON | OFF
This command defines that an additional carrier suppression of min. 20dB is taken into account for
the measurement. If there is already suppression, a more sensitive setting of the instrument is
selected.
Example:
":CONF:TXS ON"
Features:
*RST value:
SCPI:
Mode:
MS
OFF
device-specific
For measurements in the RX-band the value is automatically set to ON.
:CONFigure[:MS]:PRESet
This command resets the parameters for the standard selected to their default values (DEFAULT
SETTINGS).
Example:
":CONF:PRES"
Features:
*RST value:
SCPI:
Mode:
MS
-device-specific
This command is an event and has thus no query and no *RST value assigned.
1065.6016.12
6.83
E-16
CONFigure-Subsystem
FSE
:CONFigure[:MS]:SWEeptime STANdard | AUTO
This command selects the sweep-time computing mode for the spurious measurement:
Example:
":CONF:SWE AUTO"
Feature:
*RST value:
SCPI:
Mode:
MS
STANdard
The computation of the sweep time is based on a worst-case estimation
AUTO
The sweep time is reduced by a factor of 8 (assuming all slots are on).
STANdard
device-specific
:CONFigure[:MS]:MTYPe GMSK | EDGE
This command selects the standard (GMSK or EDGE).
Example:
":CONF:MTYP EDGE"
Features:
*RST value:
SCPI:
Mode:
MS
1065.6016.12
GMSK
device-specific
6.84
E-16
FSE
CONFigure-Subsystem
CONFigure:SPECtrum Subsystem
This subsystem provides the commands for configuring the measurements in the GSM BTS Analyzer
mode (FSE-K11) or in the GSM MS Analyzer mode (FSE-K10) used to determine the power of the
spectral contributions due to modulation and switching (modulation spectrum, transient spectrum).
COMMAND
PARAMETERS
CONFigure
:SPECtrum
:MODulation
[:IMMediate]
:COUNt
:RANGe
-
ARFCn | TXBand | RXBand |
COMBined | DCSRx1800 |
G8Rxband | PCSRx1900
:TGATe
:SWITching
[:IMMediate]
:COUNt
UNIT
---
---
-
COMMENT
no query, Option FSE-K11 or FSE-K10
Option FSE-K11 or FSE-K10
Option FSE-K11 or FSE-K10
Option FSE-K11
Option FSE-K11 or FSE-K10
no query
:CONFigure:SPECtrum:MODulation[:IMMediate]
This command selects measurement of the spectrum due to modulation.
Example:
":CONF:SPEC:MOD"
Features:
*RST value:
SCPI:
Modes:
BTS, MS
-device-specific
This command is an event and has thus no query and no *RST value assigned.
:CONFigure:SPECtrum:MODulation:COUNt 1 to 1000
This command sets the number of bursts used for determining the average and maximum values.
Example:
":CONF:SPEC:MOD:COUN 100"
Features:
*RST value:
SCPI:
Modes:
1065.6016.12
500 (GSM/DCS1800 phase I)
200 otherwise
device-specific
BTS, MS
6.85
E-16
CONFigure-Subsystem
FSE
:CONFigure:SPECtrum:MODulation:RANGe ARFCn | TXBand | RXBand | COMBined | DCSRx1800
| G8Rxband | PCSRx1900
This command selects the frequency range for the measurement.
Example:
":CONF:SPEC:MOD:RANG TXB"
Features:
*RST value:
SCPI:
Modes:
BTS, MS
ARFCn
TXBand
RXBand
COMBined
DCSRx1800
G8Rxband
PCSRx1900
ARFCN ± 1.8 MHz
TX-Band
RX-Band
ARFCN ± 1.8 MHz / TX-Band
RX band DCS 1800 (option FSE-K10 only)
RX band GSM 850 (option FSE-K10 only)
RX band PCS 1900 (option FSE-K10 only)
ARFCn
device-specific
:CONFigure:SPECtrum:MODulation:TGATe ON | OFF
This command switches on or off the operating mode gating for the TX band. For TGATe OFF, 8
active slots are presumed.
Example:
":CONF:SPEC:MOD:TGAT ON"
Features:
*RST value:
SCPI:
Mode:
BTS
OFF
device-specific
:CONFigure:SPECtrum:SWITching[:IMMediate]
This command selects measurement of the spectrum due to switching transients.
Example:
":CONF:SPEC:SWIT"
Features:
*RST value:
SCPI:
Modes:
BTS, MS
-device-specific
This command is an event and has thus no query and no *RST value assigned.
:CONFigure:SPECtrum:SWITching:COUNt 1 to 1000
This command defines the number of bursts used for determining the average and maximum values.
Example:
":CONF:SPEC:SWIT:COUN 100"
Features:
*RST value:
SCPI:
Modes:
1065.6016.12
500 (GSM/DCS1800 phase I)
200 otherwise
device-specific
BTS, MS
6.86
E-16
FSE
CONFigure-Subsystem
CONFigure:SPURious Subsystem
This subsystem provides commands for configuring the measurements in the GSM BTS (FSE-K11) or
GSM MS (FSE-K10) Analyzer mode used for measuring the power of spurious emissions.
COMMAND
PARAMETERS
CONFigure
:SPURious
[:IMMediate]
:COUNt
:RXBand
:RANGe
-
TXBand | OTXBand | RXBand |
IDLeband | COMBined
:STEP<1..26>
:COUNt?
:ANTenna
UNIT
COMMENT
-----
no query, Option FSE-K11, FSE-K10
Option FSE-K11, FSE-K10
Option FSE-K11
Option FSE-K11, FSE-K10
--
Option FSE-K11, FSE-K10
query only
Option FSE-K10
CONDucted | RADiated
:CONFigure:SPURious[:IMMediate]
This command selects measurement of spurious emissions.
Example:
":CONF:SPUR"
Features:
*RST value:
SCPI:
Modes:
BTS, MS
-device-specific
This command is an event and has thus no query and no *RST value assigned.
:CONFigure:SPURious:COUNt
1 to 1000
This command sets the number of bursts used for determining the average and maximum values.
Example:
":CONF:SPUR:COUN 100"
Features:
*RST value:
SCPI:
Modes:
500 (GSM/DCS1800 phase I)
200 otherwise
device-specific
BTS, MS
The number of bursts in measurements of the RX band is set by command
:CONFigure:SPURious:RANGe:RXBand (FSE K11 only).
:CONFigure:SPURious:COUNt:RXBand 1 to 1000
This command ses the number of bursts used for determining the average and maximum values in
measurements of the RX band.
Example:
":CONF:SPUR:COUN:RXB 100"
Features:
*RST value:
SCPI:
Modes:
BTS
1065.6016.12
1
device-specific
6.87
E-16
CONFigure-Subsystem
:CONFigure:SPURious:RANGe
FSE
TXBand | OTXBand | RXBand | IDLeband | COMBined
This command selects the frequency range used for the measurement.
Example:
":CONF:SPUR:RANG OTX"
Features:
*RST value:
SCPI:
Modes:
BTS, MS
TXBand
OTXBand
RXBand
IDLeband
COMBined
TX-Band
Not TX-Band
RX-Band (option FSE-K11 only)
Idle band (option FSE-K10 only)
TX-Band ± 2 MHz (option FSE-K11 only)
TXB
device-specific
:CONFigure:SPURious:STEP<1 to 26> ON | OFF
This command selects a subband of the selected band for a spurious measurement.
Each band is divided up into 1 to max. 26 subbands, which are selected by the numerical suffix
following STEP. A subband is selected for measurement by setting ON.
Example:
":CONF:SPUR:STEP24 ON"
Feature:
*RST value:
SCPI:
Mode:
BTS, MS
ON
device-specific
:CONFigure:SPURious:STEP:COUNt?
This command queries the number of subbands of the currently selected band for a spurious
measurement.
Example:
":CONF:SPUR:STEP:COUNT?"
Feature:
*RST value:
SCPI:
Mode:
BTS, MS
device-specific
This command is a query and has therefore no *RST value assigned.
:CONFigure:SPURious:ANTenna CONDucted | RADiated
This command selects the features of the measurement of spurious emmissions.
Example:
":CONF:SPUR:ANT RAD"
Feature:
*RST value:
SCPI:
Mode:
MS
1065.6016.12
COND
device-specific
6.88
E-16
FSE
DIAGnostic-Subsystem
DIAGnostic Subsystem
The DIAGnostic subsystem contains the commands which support instrument diagnostics for
maintenance, service and repair. In accordance with the SCPI standard, all of these commands are
device-specific.
COMMAND
PARAMETERS
DIAGnostic
:SERVice
:INPut
[:SELect]
:FUNCtion
:NSOurce
:INFO
:CCOunt
:ATTenuation<1|2|3>?
CALibration | RF
,>numeric_value>
UNIT
----
COMMENT
no query
query only
:DIAGnostic:SERVice:INPut[:SELect] CALibration | RF
This command toggles between the RF input on the front panel and the internal 120-MHz reference
signal.
Example:
":DIAG:SERV:INP CAL"
Features:
*RST value:
SCPI:
Modes:
A, VA
RF
device-specific
:DIAGnostic:SERVice:FUNCtion ,...
This command activates a service function.
Example:
":DIAG:SERV:FUNC 2,0,2,12,1"
Features:
*RST value:
SCPI:
Modes:
A, VA
device-specific
The service function is selected via five parameters: functional group number, board number,
function number, parameter 1 and parameter 2 (see service manual).
:DIAGnostic:SERVice:NSOurce ON | OFF
This command switches the 28-V supply at the rear connector of the noise source on and off.
Example:
":DIAG:SERV:NSO ON"
Features:
*RST value:
SCPI:
Modes:
A, VA
1065.6016.12
OFF
device-specific
6.89
E-16
DIAGnostic Subsystem
FSE
:DIAGnostic:INFO:CCOunt:ATTenuation<1 | 2 | 3>?
This command queries the cycle counters of the attenuators. The suffix selects the attenuator:
1: Basic instrument
2: Tracking Generator
3: FSE-B13
The result is output as a list of values separated by a ’,’. The list starts with the date.
Example:
":DIAG:INFO:CCO:ATT?"
Features:
*RST value:
SCPI:
Modes:
A, VA, MS, BTS
-device-specific
This command is a query and has therefore no *RST value assigned.
1065.6016.12
6.90
E-16
FSE
DISPlay Subsystem
DISPlay Subsystem
The DISPlay subsystem controls the selection and presentation of textual and graphic information as
well as of trace data on the display.
The displays in the split-screen mode are assigned to WINDow 1 (screen A) or 2 (screen B) .
COMMAND
DISPlay
:FORMat
:PROgram
[:MODE]
:ANNotation
:FREQuency
:LOGO
:CMAP<1 to 13>
:DEFault
:HSL
:PDEFined
[:WINDow<1|2>]
:SELect
:TEXT
[:DATA]
:STATe
:TIME
:MINFo
:TRACe<1 to 4>
:X
[:SCALe]
:RVALue
:ZOOM
[:FREQuency]
:STARt
:STOP
:CENTer
:Y
[:SCALe]
:MODE
:RLEVel
:OFFSet
:RVALue
:AUTO
:RPOSition
:PDIVision
:SPACing
1065.6016.12
PARAMETERS
UNIT
COMMENT
SINGle | SPLit
Controller option
0 to 100,0 to 100,0 to 100
BLACk | BLUE | BROWn | GREen |
CYAN | RED | MAGenta | YELLow |
WHITe | DGRay | LGRay | LBLue |
LGReen | LCYan | LRED | LMAGenta
Vector Signal Analysis
HZ
HZ
HZ
ABSolute | RELative
DB
DBM
DB
DBM|DB|HZ|
DEG|RAD
PCT
LINear|LOGarithmic|PERCent
6.91
DBM|DB|HZ|
DEG|RAD
--
Analyzer mode only
Vector Signal Analysis or
Tracking Generator
Vector Signal Analysis
E-16
DISPlay Subsystem
FSE
COMMAND
PARAMETERS
[:WINDow<1|2>]
:TRACe<1 to 4>
:MODE
:CWRite
:ANALog
:HCONtinuous
[:STATe]
:SYMBol
:EYE
:COUNt
:PSAVe
[:STATe]
HOLDoff
UNIT
WRITe | VIEW | AVERage |
MAXHold | MINHold
DOTS | BARS | OFF
--
SYM
-----
COMMENT
Vector Signal Analysis
Vector Signal Analysis
Vector Signal Analysis
:DISPlay:FORMat SINGle | SPLit
This command switches the test result display between FULL SCREEN and SPLIT SCREEN.
Example:
":DISP:FORM SPL"
Features:
*RST value:
SCPI:
Modes:
A, VA
SINGle
device-specific
:DISPlay:PROGram[:MODE] ON | OFF
This command switches the display between the measuring instrument and the computer function.
Example:
":DISP:PROG ON"
Features:
*RST value:
SCPI:
Modes:
A, VA, BTS, MS
OFF
device-specific
This command is only valid in conjunction with Option Computer Function (FSE-B15).
:DISPlay:ANNotation:FREQuency ON | OFF
This command switches the x-axis annotation on or off.
Example:
":DISP:ANN:FREQ OFF"
Features:
*RST value:
SCPI:
Modes:
A, VA, BTS, MS
ON
conforming
:DISPlay:LOGO ON | OFF
This command switches the factory logo on the screen on or off.
Example:
":DISP:LOGO OFF"
Features:
*RST value:
SCPI:
Modes:
A, VA, BTS, MS
1065.6016.12
ON
device-specific
6.92
E-16
FSE
DISPlay Subsystem
:DISPlay:CMAP<1 to 13>:DEFault
This command resets the screen colors of the instrument to their default settings.
Example:
":DISP:CMAP:DEF"
Features:
*RST value:
SCPI:
Modes:
A, VA, BTS, MS
-conforming
This command is an event and has thus no query and no *RST value assigned. The numeric suffix in
CMAP<1 to 13> is not significant.
:DISPlay:CMAP<1 to 13>:HSL ,,
This command defines the color table of the instrument.
Parameter:
hue = TINT
sat = SATURATION
lum = BRIGHTNESS
The value range is 0.0 to 100.0 for all parameters.
Example:
":DISP:CMAP2:HSL 0.3,0.8,1.0"
Features:
*RST value:
SCPI:
Modes:
A, VA, BTS, MS
-conforming
To each numeric suffix of CMAP is assigned one or several picture elements which can be modified
by varying the corresponding color setting. The following assignment applies:
CMAP1
CMAP2
CMAP3
CMAP4
CMAP5
CMAP6
CMAP7
Trace 1
CMAP8
Trace 2
CMAP9
Trace 3
CMAP10
Trace 4
CMAP11
Marker
CMAP12
Grid
CMAP13
softkey State On
Soft key State Data Entry
Soft key State OFF
Soft key Shade
Text
Title
Background
The values set are not changed by *RST.
:DISPlay:CMAP<1 to 13>:PDEFined
BLACk | BLUE | BROWn | GREen | CYAN | RED | MAGenta |
YELLow |WHITe | DGRay | LGRay | LBLue | LGReen |
LCYan |LRED | LMAGenta
This command defines the color table of the instrument using predefined color values. To each
numeric suffix of CMAP is assigned one or several picture elements which can be modified by
varying the corresponding color setting. The same assignment as for :DISPlay:CMAP<1 to
13>:HSL applies.
Example:
":DISP:CMAP2:PDEF GRE"
Features:
*RST value:
SCPI:
Modes:
A, VA, BTS, MS
-conforming
The values set are not changed by *RST.
1065.6016.12
6.93
E-16
DISPlay Subsystem
FSE
:DISPlay[:WINDow<1|2>]:SELect
This command selects the active measurement window via the numeric suffix in WINDow . This way,
a switch is possible from FULL SCREEN A to FULL SCREEN B (see example).
Example:
":DISP:FORM SPLit"
":DISP:WIND2:SEL"
":DISP:FORM SINGle"
Features:
*RST value:
SCPI:
Modes:
A, VA
-device-specific
This command is an event and has thus no query and no *RST value assigned.
:DISPlay[:WINDow<1|2>]:MINFo ON | OFF
This command switches the marker info list on the screen on or off.
Example:
":DISP:MINF ON"
Features:
*RST value:
SCPI:
Modes:
A, VA, BTS, MS
OFF
device-specific
:DISPlay[:WINDow<1|2>]:TEXT[:DATA]
This command defines a comment (max. 50 characters) which can be displayed on the screen.
Example:
":DISP:TEXT "signal/noise power measurement"
Features:
*RST value:
SCPI:
Modes:
A, VA, BTS, MS
"" (empty)
conforming
The numeric suffix in WINDow<1|2> is not significant.
:DISPlay[:WINDow<1|2>]:TEXT:STATe ON | OFF
This command switches on or off the screen display of the comment.
Example:
":DISP:TEXT:STAT ON"
Features:
*RST value:
SCPI:
Modes:
A, VA, BTS, MS
OFF
conforming
The numeric suffix in WINDow<1|2> is not significant.
1065.6016.12
6.94
E-16
FSE
DISPlay Subsystem
:DISPlay[:WINDow<1|2>]:TIME ON | OFF
This command switches on or off the screen display of date and time.
Example:
":DISP:TIME ON"
Features:
*RST value:
SCPI:
Modes:
A, VA, BTS, MS
OFF
device-specific
The numeric suffix in WINDow<1|2> is not significant.
:DISPlay[:WINDow<1|2>]:TRACe<1 to 4>:X[:SCALe]:RVALue