:SET
:USER
:USER?
The colon character (:) is important to using this structure. It plays two syntax
roles:
• A colon (with no spaces) must separate the command path from the command. In the
Okay
Mode:dB
• A leading colon on a command causes the FPM-8200 to begin searching for the next
These commands are different because EVE? is a command on the ENAB: path,
and also exists at the root level. Each command string queries enabled condition,
then another register. The first command string queries the events enabled
register. The second string queries the event status register. The contents of
these two registers can be different, with confusing results.
Syntax Summary
GPIB commands must contain all of the letters shown in upper case in the
command definition. Optional letters shown in lower case for some device
dependent commands in Chapter 4, GPIB Command Reference are useful for
clarity, but must be in the correct sequence. Upper/lower case does not matter to
the FPM-8200.
A single white space must separate a command from its parameters or data.
White space is normally the space character (space bar). Other control
01_10
Note: The Mode:dB command accomplishes the same result as pressing the dB button
on the front panel.
CAL
ENAB
:COND
:COND?
:EVE
:EVE?
Figure 3.3 Command Tree Structure
example above, there must be a colon and no spaces between MODE and dB.:
command at the root node. Otherwise (after a semicolon) the FPM-8200 will first search the
most recently used node for the command. These examples illustrate this distinction:
ENAB:COND?; EVE?
ENAB:COND?; :EVE?
R E M O T E O P E R A T I O N
Command Syntax
(root)
MODE
RAN
:DB
:AUTO
:DBM
:AUTO?
:W
Not Okay
Mode : dB
Mode dB
3
C H A P T E R
(all other
commands)
29
FPM-8200