Naming Conventions - R&S OSP Operating Manual

R&S OSP
Parameters
Many commands are supplemented by a parameter or a list of parameters.
Parameters either provide alternative options (setting a or setting b or setting c ..., see
special character "|"), or they form a list separated by commas (setting x,y).
<Par_Name> In the command tables and lists, parameters are generally described by
a name (literal) written in angle brackets (<>). This literal merely serves as a
parameters description; in an application program it must be replaced by one of the
possible settings reported in the detailed parameter description.
Example: ROUTe:CLOSe <channel_ist>
with <channel_list> is for example: (@F01A11(0101))
possible command syntax: ROUTe:CLOSe (@F01A11(0101))
Upper / lower case
Upper/lower case characters characterize the long and short form of the mnemonics in
a command. The short form consists of all upper-case characters, the long form of all
upper case plus all lower case characters. On the R&S OSP, either the short form or
the long form is allowed; mixed forms will generally not be recognized. Either the short
form or the long form are permissible. The instrument itself does not distinguish upper
case and lower case characters.
Special characters
[ ] in square brackets can be omitted when composing the command header (see
SCPI Command Structure and Syntax). The complete command must be recognized
by the instrument for reasons of compatibility with the SCPI standard. Parameters in
square brackets are optional as well. They may be entered in the command or omitted.
Example: The following command has an optional element:
ROUTe:PATH[:DEFine] <path_name>,<channel_list> equals
ROUTe:PATH <path_name>,<channel_list>
{ } Braces or curly brackets enclose one or more parameters that may be included zero
or more times.

7.2 Naming Conventions

Some SCPI control commands which are introduced in the following chapters need
R&S OSP instrument specific parameter strings like <instr_name>, <module_name>
or <channel_list>.
For a better understanding on how these parameters strings are built up, this chapter
serves as an overview of the naming conventions.
<instr_name> (example: ROUTe:MODule:DEFine <instr_name>,<instr_address>)
An R&S OSP instrument can be operated as stand alone device controlled via LAN.
Beside that, it is possible to build up a larger system of several R&S OSP instruments
by connecting one or more further R&S OSP instruments to the LAN controlled
instrument via CAN bus.
Operating Manual 1505.3896.12 - 14
Remote Command Reference
149