User manual
2400 Series SourceMeter
®
User’s Manual Remote Operations 14-11
:stat:oper:enab <NRf>
:stat:oper:enab?
:stat:pres
In each of the above program messages, the path pointer starts at the root com-
mand (:stat) and moves down the command levels until the command is exe-
cuted.
Multiple command messages
You can send multiple command messages in the same program message as
long as they are separated by semicolons (;). The following is an example show-
ing two commands in one program message:
:stat:oper; :stat:oper:enab <NRf>
When the above is sent, the first command word is recognized as the root com-
mand (:stat). When the next colon is detected, the path pointer moves down to the
next command level and executes the command. When the path pointer sees the
colon after the semicolon (;), it resets to the root level and starts over.
Commands that are on the same command level can be executed without having
to retype the entire command path. Example:
:stat:oper:enab <NRf>; enab?
After the first command (:enab) is executed, the path pointer is at the third com-
mand level in the structure. Since :enab? is also on the third level, it can be typed
in without repeating the entire path name. Notice that the leading colon for :enab?
is not included in the program message. If a colon were included, the path pointer
would reset to the root level and expect a root command. Since :enab? is not a
root command, an error would occur.
Command path rules
• Each new program message must begin with the root command, unless it
is optional (e.g., [:SENSe]). If the root is optional, simply treat a command
word on the next level as the root. For fastest operation, do not send
optional data.
• The colon (:) at the beginning of a program message is optional and need
not be used. However, eliminating the first colon will result in fastest opera
-
tion. Example:
• :stat:pres = stat:pres
• When the path pointer detects a colon (:) it moves down to the next com-
mand level. An exception is when the path pointer detects a semicolon (;),
which is used to separate commands within the program message (see
next rule).