S331E, S332E, S361E, S362E Site Master™MS2711E, MS2712E, MS2713E Spectrum Master™MT8212E, MT8213E Cell Master™ Programming Manual : Programming with SCPI : Notational Examples
Notational Examples
Table: Creating Valid Commands provides examples of valid command syntax:
Creating Valid Commands
Command Specification
Valid Forms
[:SENSe]:FREQuency:STARt <freq>
The following all produce the same result:
:sense:frequency:start 1000000
:CALCulate:MARKer{1|2|3|4|5|6}:X <x-parameter>
The first 2 commands set the location of marker 1. The third command sets the location of marker 2.
The following commands are identical:
:unit:pow dbm
:INITiate:CONTinuous OFF|ON|0|1
The following commands are identical:
:INITiate:CONTinuous OFF
:init:cont 0
Command statements read from left to right and from top to bottom. In the command statement above, the :FREQuency keyword immediately follows the :SENSe keyword with no separating space. A space (sp) is used between the command string and its argument.
Note that the first keyword in the command string does not require a leading colon; however, it is good practice to always use a leading colon for all keywords. Note also that the :SENSe keyword is optional. This is a SCPI convention for all voltage or signal source type instruments that allows shorter command statements to be used.
The following is an example of a multiple-command statement that uses two separate commands in a single statement:
:FREQuency:STARt 10E6;:FREQuency:STOP 20E9
A semicolon is used to join the commands and a leading colon used immediately after the semicolon to start the second command.
Command Terminators
The <new line> character (ASCII 10) in the last data byte of a command string is used as a command terminator. Use of a command terminator resets the command path to the root of the tree.