Technical data

SCPI Basics 6
Agilent N8211A/N8212A Performance Upconverter Synthetic Instrument Module, 250 kHz to 20 / 40 GHz 157
Command Types
Commands can be separated into two groups: common commands and subsystem
commands. Figure 9, shows the separation of the two command groups. Common
commands are used to manage macros, status registers, synchronization, and data storage
and are defined by IEEE 488.2. They are easy to recognize because they all begin with an
asterisk. For example *IDN?, *OPC, and *RST are common commands. Common
commands are not part of any subsystem and the N8211A/N8212A interprets them in the
same way, regardless of the current path setting.
Subsystem commands are distinguished by the colon (:). The colon is used at the
beginning of a command statement and between keywords, as in :FREQuency[:CW?].
Each command subsystem is a set of commands that roughly correspond to a functional
block inside the N8211A/N8212A. For example, the power subsystem (:POWer) contains
commands for power generation, while the status subsystem (:STATus) contains
commands for controlling status registers.
Figure 9 Command Types
If a command requires more than one parameter, you must separate
adjacent parameters using a comma. Parameters are not part of the
command path, so commas do not affect the path level.
[:SOURce]:LIST:
DWELl <val>{,<val>}
A semicolon separates two commands in the same program message
without changing the current path.
:FREQ 2.5GHZ;:POW 10DBM
White space characters, such as <tab> and <space>, are generally
ignored as long as they do not occur within or between keywords.
However, you must use white space to separate the command from the
parameter, but this does not affect the current path.
:FREQ uency or :POWer
:LEVel are not allowed.
A <space> between :LEVel and
6.2 is mandatory.
:POWer:LEVel 6.2
Table 14 Command Syntax
Characters, Keywords, and Syntax Example