Rohde & Schwarz FSEK30, FSEM30, FSEB30, FSEA30, FSEM20 Operating Manual
...
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 Instructi ons
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 Instructi ons
Manuals for Signal Analyzer FSE
Tabbed Divider
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
1065.6016.12 RE E-2
Safety Instructions
Shock hazard
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
Weight
indication for
units >18 kg
PE terminal Ground
1. 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 V
> 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 c onnections 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.
terminal
Danger!
Warning!
Ground Attention!
Hot surfaces
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
rms
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
Electrostatic
sensitive devices require
special care
1065.6016.12 SI.1 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.
Electrostatics via the connectors may dam-
13.
age the equipment. For the s afe 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 f ront
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 TV Demodulator
• Option FSE-B5 FFT Filter
• Option FSE-B8/9/10/11 Tracking Generator
• Option FSE-B13 1 dB Attenuator
• Option FSE-B15 DOS Controller (Id.-Nr: 1073.5696.02/.03)
• Option FSE-B15 Windows NT Controller (Id.-Nr.: 1073.5696.06)
• Option FSE-B16 Ethernet Adapter
• Option FSE-B17 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 c ontains comprehensive information about the technical data of the
instrument, the setup and putting into operation of the ins tr ument, the operating concept and contr ols
as well as the operation of the FSE via the m enus and via remote control. Typical measurement
tasks for the FSE ar e explained us ing the f unc tions of f er ed by the menus and a selec tion of pr ogram
examples.
In addition the operating manual gives information about maintenance of the instrument and about
error detection listing the error messages which m ay be output by the instrument. It is subdivided into
2 volumes containing the data sheet plus 9 chapters:
Volume 1
The data sheet informs about guaranteed specifications and characteristics of the instrument.
Chapter 1 describes the control elem ents 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.
Chapter 2 gives an introduction to typical measurement tasks of the FSE which are ex-
plained step by step.
Chapter 3 describes the operating principles, the structure of the graphic al interface and
offers a menu overview.
Chapter 4 forms a ref erence for manual control of the F SE and contains a detailed de-
scription of all instrument functions and their application.
Chapter 10 contains an index for the operating manual.
Volume 2
Chapter 5 describes the basics for program ming the FSE, c omm and pr ocessing and the
status reporting system.
Chapter 6 lists all the remote-control com m ands def ined for the ins trum ent. At the end of
the chapter a alphabetical list of com mands and a table of softk eys with command assignment is given.
Chapter 7 contains program examples for a number of typical applications of the FSE.
Chapter 8 describes preventive maintenanc e and the characteristics of the instrument’s
interfaces.
Chapter 8 gives a list of error messages that the FSE may generate.
Chapter 9 contains a list of error messages.
Chapter 10 contains an index for the operating manual.
1065.6016.12 0.1 E-1
Manuals FSE
Service Manual - Instrument
The service manual - instrum ent inform s on how to check c ompliance with rated spec ifications (per formance test) and on the self tests.
Service Manual
The service manual is not delivered with the instrument but m ay 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. T his compr ises the test and adjustm ent 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 ins truments. This includes the description
of the command str ucture and syntax according to the SCPI standard, the description of c ommand
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 accor ding to standard IEC 625.1/IEEE 488.2 and
two RS-232 interfaces. The connector is located at the r ear of the instrum ent 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 instrum ent control by Visual
C++ and Visual Basic programs
The instrument supports the SCPI version 1994.0 (Standard Commands for Programmable
Instruments). T he SCPI standard is based on standard IEEE 488.2 and aim s 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 c omm ands is to be obtained from the relevant m anuals.
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 com m and syntax, error handling and configur ation of
the status registers are explained in detail in the r espective sections. Tables provide a fast overview of
the commands implem ented in the instrument and the bit assignm ent in the status regis ters. T he tables
are supplemented by a comprehensive desc ription of every com m and and the s tatus register s. 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.
The RSIB interface
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 bas ic functions. As a prerequisite, the IEC-bus addr es s, which is f ac tor y-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 IBFIND("DEV1", analyzer%) ’Open port to the instrument
CALL IBPAD(analyzer%, 20) ’Inform controller about instrument address
CALL IBWRT(analyzer%, "*RST;*CLS") ’Reset instrument
CALL IBWRT(analyzer%, ’FREQ:CENT 100MHz’) ’Set center frequency to 100 MHz
CALL IBWRT(analyzer%, ’FREQ:SPAN 10MHz’) ’Set span to 10 MHz
CALL 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 f ront panel is disabled. The ins trument remains in the remote
state until it is reset to the manual s tate via the front panel or via remote control interf aces. 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 m ode
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 addres sed using the s et IEC-bus addr ess.
The IEC-bus address of the instrument is factory-set to 20. It can be changed m anually 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 IBFIND("DEV1", analyzer%) ’Open port to the instrument
CALL IBPAD(analyzer%, 20) ’Inform controller about old address
CALL IBWRT(analyzer%, "SYST:COMM:GPIB:ADDR 18")’Set instrument to new address
CALL 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 proces sing must be completed as
otherwise switchover to remote control is effected immediately.
– The LOCAL key can be disabled by the universal c ommand LLO
(see chapter 8) in order to prevent unintentional switchover. In
this case, switchover to manual mode is only pos s ible 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: ...
CALL IBLOC(analyzer%) ’Set instrument to manual operation.
...
1065.6016.12 5.3 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 Instrum ent or INSTR and DOS in table COM PORT 1/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 Instrum ent or INSTR and DOS in table COM PORT 1/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 switc hover. 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: ...
V24puts(port, ’@LOC’); Set instrument to manual operation.
...
1065.6016.12 5.4 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 Comm on Commands *OPC? can be us ed for command s ynchronization, *WAI and *OPC
are not available.
− Block data cannot be transmitted.
When W indows NT is booted, data are output via the COM interface because of automatic external
device recognition. Therefor e, it is r ec ommended to clear the input buff er of the c ontroller bef or e 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 interfac e, c opy 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 instrum ent 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: Before switchover, command processing must be completed as
otherwise switchover to remote control is effected immediately.
Via RSIB: ...
ud = RSDLLibloc (ud, ibsta, iberr, ibcntl);
...
1065.6016.12 5.6 E-16
FSE Messages
Messages
The messages transf err ed via the data lines of the IEC bus or the RSIB interf ac e ( see c hapter 8) c an 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 trans fer red on the data lines of the IEC bus, the "AT N" contr ol 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 comm ands only act on devices previously addressed as listeners. The inter face 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 Vis ual Bas ic pr ogr ams. 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 are exactly defined as to their function and
notation in standard IEEE 488.2. They refer to
functions such as managem ent of the standar-dized
status registers, reset and selftest.
Device-specific
commands refer to functions depending on the features of the
instrument such as f requency 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. T he com m ands 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 inst ruments, irres pective of the type of instrument or m anufacturer. T he goal of the SCPI
consortium is to standar dize the device-specific com mands to a large extent. F or 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 func tions. T hus it is possible to address the sam e
functions with identical commands. The command systems are of a hierarchical structure.
Fig. 5-1 illustrates this tree structure using a section of com mand system SENSe, which controls the
sensor functions of the devices.
SCPI is based on standard IEEE 488.2, i.e. it uses the sam e syntactic basic elements as well as the
common com m ands defined in this standard. Part of the syntax of the device r esponses is def ined with
greater restrictions than in standard IEEE 488.2 (see Section "Responses to Queries").
Structure of a Command
The comm ands c onsist of a so-c alled header and, in m ost c ases , one or m ore 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 form ed 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: *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.
1065.6016.12 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 k ey 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 CENT er and ST OP are
adjusted when the span is changed.
SENSe
BANDwidth FUNCtion
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 comm and system . Their
effect depends on the structure of the comm and, that is to say, at which
position in the header of a command they are inserted.
Example: SOURce:FM:POLarity NORMal
FREQuency
STOP
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 m odulation only for the
external signal source indicated.
CENTer
DETector
SPAN OFFSetSTARt
HOLD LINK
1065.6016.12 5.10 E-16
FSE Structure and Syntax of the Device Messages
Optional key words: Some command systems permit c er tain k e y words to be optionally inserted
into the header or omitted. These key words are marked by square
brackets in the descr iption. 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: An optional key word must not be omitted if its effect is specified
in detail by a numeric suffix.
Long and short form: T he key words feature a long form and a short form. Either the short f orm
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 mark ed by upper-case letters, the long form
corresponds to the complete word. Upper- case and lower-c ase
notation only serve the above purpose, the instrument itself
does not make any difference between upper-case and lowercase letters.
Parameter: T he parameter must be separated from the header by a "white space". If
several parameters ar e specified in a command, they are separated by a
comma ",". A f ew queries perm it the param eters MINim um , MAXim um 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:
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 selec ted 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.
3.5E9
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 comm ands. It is terminated by a <New Line>, a <New
Line> 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 comm and 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 frequenc y of the analyzer. The second com mand
is part of the INPut system and sets the attenuation of the input signal.
If the successive com mands belong to the sam e system, having one or several levels in comm on, the
command line can be abbr eviated. T o this end, the s ec ond command after the s emicolon starts with the
level that lies below the common levels (see also Fig. 5-1). The colon following the semicolon m ust be
omitted in this case.
Example:
CALL IBWRT
CALL IBWRT(analyzer, "SENSe:FREQuency:STARt 1E6;STOP 1E9")
However, a new command line always begins with the complete path.
Example: CALL IBWRT(analyzer, "SENSe:FREQuency:STARt
(analyzer, "SENSe:FREQuency:STARt 1E6;:SENSe:FREQuency:STOP 1E9")
This comm and line is represented in its f ull length and contains two comm ands 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 c ommand 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:
1E6")
CALL IBWRT(analyzer, "SENSe:FREQuency:STOP 1E9")
Responses to Queries
A query is defined for each setting com mand unless explicitly specified other wise. It is f or med by adding
a question mark to the ass ociated setting command. Ac cording 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, m inimum 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 <Boolean 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?
1065.6016.12 5.12 E-16
Response(for standard): STAN
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 comm and 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, dec imal point and
exponent. Values exceeding the resolution of the instrum ent are rounded up or
down. The value range is -9.9E37 to 9.9E37. The exponent is intr oduced 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 perm issible), K (k ilo), M (m illi), 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, DOW N 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, respec tively. 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 c auses ar e the divis ion 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. T he 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? Response: 1
1065.6016.12 5.13 E-16
Structure and Syntax of the Device Messages FSE
Text 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 GROund
Query: INPut:COUPling? Response GRO
Strings Strings must always be entered in quotation marks (’ or ").
Example: SYSTem:LANGuage "SCPI"
SYSTem:LANGuage ’SCPI’
Block data Block data are a transmission form at 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 ex ample
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 contr ol signs are
ignored until all bytes are transmitted..
or
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 mark s the upp ermost
command level.
The semicolon separates two commands of a command line.
;
It does n ot alter the path.
,
The comma separates several para meters of a command.
The question mark forms a query.
?
*
The asterisk marks a common command.
"
Double or single quotation mark s introduce a string and terminate it.
’
The double dagger # introduces block data.
#
A "white space" (ASCII - Code 0 to 9, 1 1 to 32 decimal, e.g. blank) separates
header a nd 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 m ade viewed from the s tandpoint of the servicing of
IEC-bus commands . The individual components work independently of each other and sim ultaneously.
They communicate by means of so-called "messages".
Input unit with
IEC Bus
input puffer
Command
recognition
Data set
Status reporting-
system
Instrument
hardware
Output unit with
IEC Bus
Fig. 5-2 Instrument model in the case of remote control by means of the IEC bus
output buf f er
Input Unit
The input unit receives com mands 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,
<PROGRAM MESSAGE TERMINATOR>, as defined in IEEE 488.2, or the interface message DCL.
If the input buffer is full, the IEC-bus traf fic is stopped and the data rec eived up to then are processed.
Subsequently the IEC-bus traffic is continued. If, however, the buf fer 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 comm and 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 T rigger), e.g., is
only executed after the comm ands received before as well. Eac h recognized comm and is im mediately
transferred to the data set but without being executed there at once.
Syntactical errors in the comm and ar e rec ognized here and supplied to the s tatus r epor ting 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 ins trum ent hardware as well now. Subsequently it is imm ediately 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 comm ands lead to an alteration in the data set. The data base m anagem ent 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 com patibility among each other and with the instrum ent 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 alter ation
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 c ollects information on the instrum ent 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 inform ation requested by the controller, which it receives fr om the data set
management. It proces ses 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 address ed as a talk er without the output buff er containing data or awaiting data from
the data set management, the output unit sends error m essage "Quer y UNTERMINATED" to the status
reporting system. No data are sent on the IEC bus, the c ontroller waits until it has reac hed its tim e lim it.
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 ar e actually carried out in a certain order, each comm and 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 comm ands, one of commands *OPC, *OPC? or *WAI
must be used. All three commands cause a cer tain 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 Sett i ng the opteration-complete bit in the ESR - Setting bit 0 in the ESE
*OPC? Writing a "1" into the output buffer Addressing the instrument as a talker
*WAI Continuing the IEC-bus handshake Sending the next command
- Setting bit 5 in the SRE
- Waiting for service request (SRQ)
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 instrum ent presently carries out an AUTORANGE and on errors which have
occurred. This inf ormation is stored in the status registers and in the error queue. T he status registers
and the error queue can be queried via IEC bus.
The information is of a hierarchic al structure. T he register status byte (STB) defined in IEEE 488.2 and
its associated mask regist er service r equest enable (SRE) for m the upper mos t level. The STB receives
its information f rom the standard event status register ( ESR) which is also defined in IEEE 488.2 with
the associated mask register standard event s tatus enable ( ESE) and r egister s ST ATus:OPERation and
STATus:QUEStionable which are defined by SCPI and contain detailed information on the instrument.
The IST flag ("Individual ST atus") and the parallel poll enable regis ter (PPE) alloc ated to it are also part
of the status reporting system. T he IST flag, like the SRQ, com bines 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 instrum ent 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 compris es the diff erent com mands and events c ausing the st atus
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 func tions
(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 f ive par ts. Bit 15 ( the most significant bit) is s et to
zero for all parts. Thus the contents of the register parts can be process ed 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 high er -or der reg ister
& & & & & & & & & & & & & & & &
15 14 13 1 2 ENABle part 3 2 1 0
Sum b it
+
& = logical AND
= logical OR
+
of all bits
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 ins trum ent status . T his
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 af fected by
reading.
NTRansition part The Negative-TRansition part also acts as an edge detec tor . 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 af fected 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 c ontributes 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 f rom the EVENt and ENABle part
for each register. The r esult is then entered into a bit of the CONDition part of
the higher-order register.
The instrument autom atic ally generates the sum bit f or each register . T hus 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
not used
14
Subrange limit attained
13
12
11
10
9
Subrange 10
8
Subrange 9
7
Subrange 8
6
Subrange 7
5
Subrange 6
4
Subrange 5
3
Subrange 4
2
Subrange 3
1
Subrange 2
0
Subrange 1
STATus:QUEStionable:TRANsducer
& = log ic al AND
= logical OR
of all bits
SRQ
-&-
-&-
-&-
-&-
-&-
SRE
-&-
-&-
-&-
-&-
-&-
-&-
PPE
IST flag
’
7
RQS/MSS
6
5
ESB
MAV
4
3
2
1
0
STB
Error/event
queue
bla
15
14
13
12
11
10
15
14
13
12
11
10
STATus:QUEStionable
-&-
-&-
-&-
-&-
-&-
-&-
-&-
Output
buffer
-&-
ESE ESR
not used
PROGram running
INSTrument summary bit
9
8
HCOPy in progress
CORRecting
7
WAIT for ARM
6
WAIT for TRIGGER
5
MEASuring
4
SWEeping
3
RANGing
2
SETTling
1
0
CALibrating
STATus:OPERation
not used
COMMand warning
TRANsducer break
ACPLimit
SYNC
LMARgin
9
LIMit
8
CALibration (= UNCAL)
7
MODulation
6
PHASe
5
FREQuency
4
TEMPerature
3
POWer
2
TIME
1
CURRent
0
VOLTage
7
Power on
6
User Request
5
Command Error
4
Execution Error
3
Device Dependent Error
2
Query Error
1
Reques t Contro l
0
Operation Complete
15
not used
14
13
ALT2 LOWer FAIL (screen B)
12
ALT2 UPPer FAIL (screen B)
11
ALT1 LOWer FAIL (screen B)
10
ALT1 UPPer FAIL (screen B)
9
ADJ LOWer FAIL (screen B)
8
ADJ UPPer FAIL (screen B)
7
6
5
ALT2 LOWer FAIL (screen A)
4
ALT2 UPPer FAIL (screen A)
3
ALT1 LOWer FAIL (screen A)
2
ALT1 UPPer FAIL (screen A)
1
ADJ LOWer FAIL (screen A)
0
ADJ UPPer FAIL (screen A)
STATus:QUEStionable:ACPLimit
15
not used
14
13
12
11
10
9
8
7
LMAR gin 8 FAIL
6
LMAR gin 7 FAIL
5
LMAR gin 6 FAIL
4
LMAR gin 5 FAIL
3
LMAR gin 4 FAIL
2
LMAR gin 3 FAIL
1
LMAR gin 2 FAIL
0
LMAR gin 1 FAIL
STATus:QUEStionable:LMARgin
15
not used
14
13
12
11
10
LO LEVel (screen B)
9
LO UNLoc ked (scree n B)
8
7
6
5
4
3
2
LO LEVel (screen A)
1
LO UNLoc ked (scree n A)b
0
OVEN COLD
STATus:QUEStionable:FREQuency
15
not used
14
13
12
11
10
9
8
7
6
5
4
3
CARRier overload
2
No carrier
1
SYNC not found
0
BURSt not found
STATus:QUEStionable:SYNC
15
not used
14
13
12
11
10
9
8
7
LIMit 8 FAIL
6
LIMit 7 FAIL
5
LIMit 6 FAIL
4
LIMit 5 FAIL
3
LIMit 4 FAIL
2
LIMit 3 FAIL
1
LIMit 2 FAIL
0
LIMit 1 FAIL
STATus:QUEStionable:LIMit
not used
15
14
13
12
11
IF_OVe rl oa d (s creen B)
10
UNDerload Option B7 (screen B)
9
OVERload (screen B)
8
7
6
5
4
3
IF_OVe rl oa d (s creen A)
2
UNDerload Opt ion B7 (screen A)
1
OVERload (screen A)
0
STATus:QUEStionable:POWer
Fig. 5-3 Overview of the status registers
1065.6016.12 5.20 E-16
Loading...