Rohde & Schwarz R&S UPP, User Manual

Page: 697 / 938

Remote Control - Command Description
R&S
®
UPP
681 User Manual 1411.1055.32 ─ 10
7.1 Notation of Device-Specific Commands
Long and short form
The mnemonics feature a long form and a short form. The short form is marked by
upper case letters, the long form corresponds to the complete word. Either the short
form or the long form can be entered; other abbreviations are not permitted.
Example:
INPut:COUPling AC
is equivalent to
INP:COUP AC
.
Case-insensitivity
Upper case and lower case notation only serves to distinguish the two forms in the
manual, the instrument itself is case-insensitive.
Numeric suffixes
If a command can be applied to multiple instances of an object, e.g. specific channels
or sources, the required instances can be specified by a suffix added to the command.
Numeric suffixes are indicated by angular brackets (<1...4>, <n>, <i>) and are replaced
by a single value in the command. Entries without a suffix are interpreted as having the
suffix 1.
Example:
Definition:
DATA:BARGraph:Y<ch>?
Command:
DATA:BARG:Y2?
This command reads out the Y axis value of channel 2.
Optional mnemonics
Some command systems permit certain mnemonics to be inserted into the header or
omitted. These mnemonics are marked by square brackets in the description. The
instrument must recognize the long command to comply with the SCPI standard. Some
commands are considerably shortened by these optional mnemonics.
Example:
Definition:
STATus:OPERation[:EVENt]?
Command:
STAT:OPER:EVEN?
is equivalent to
STAT:OPER?
, the command reads out
the content of the EVENt part of the STATus:OPERation register
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 (,). For a description
of the parameter types, refer to
Chapter 6.5.3, "Parameter" , on page 654..
Notation of Device-Specific Commands