Remote Control
R&S
®
NRT2
93
User Manual 1178.5550.02 ─ 04
11
Remote Control
For information on remote basics, see the Rohde
&
Schwarz website at
11.1
Notation for SCPI Commands
In the following sections, all commands implemented in the device are listed according
to the command system and then described in detail. For the most part, the notation
used complies with SCPI specifications. The commands are separated in high-level
and low-level commands, where the high-level commands combine several low-level
commands in one command.
Numeric suffixes <n>
If a command can be applied to multiple instances of an object, e.g. specific sensors,
the required instances can be specified by a suffix added to the command. Numeric
suffixes are indicated by angular brackets (<1...4>, <n>, <i>) and are replaced by a sin-
gle value in the command. Entries without a suffix are interpreted as having the suffix
1.
Optional keywords [ ]
Some command systems permit certain keywords to be inserted into the header or
omitted. These keywords are marked by square brackets in the description. The instru-
ment must recognize the long command to comply with the SCPI standard. Some com-
mands are considerably shortened by these optional mnemonics.
Therefore, not only is there a short and a long form for the commands (distinguished
here by lowercase and uppercase letters) but also a short form which is created by
omitting optional keywords.
Example:
Command
[SENSe<[1]..4>]:CORRection:GAIN2[:INPut][:MAGNitude] 1
can be written as:
SENSe1:CORRection:GAIN2:INPut:MAGNitude 1
SENSe1:CORRection:GAIN2:INPut 1
SENSe1:CORRection:GAIN2 1
SENSe:CORRection:GAIN2 1
CORRection:GAIN2 1
Parameters
Parameters must be separated from the header by a "white space". If several parame-
ters are specified in a command, they are separated by a comma (,).
Notation for SCPI Commands
