SCPI Conventions and Data Formats
64
Series N6700 User’s Guide
Message Unit Separator
When two or more message units are combined into a compound
message, separate the units with a semicolon.
STATus:OPERation?(@1);QUEStionable?(@1)
Root Specifier
When it precedes the first header of a message unit, the colon
becomes the root specifier. It tells the command parser that this is
the root or the top node of the command tree.
Message Terminator
A terminator informs SCPI that it has reached the end of a message.
The following messages terminators are permitted:
newline <NL>, which is ASCII decimal 10 or hex 0A.
end or identify <END> (EOI with ATN false)
both of the above <NL><END>
also <CR><NL>
In the examples of this guide, there is an assumed message
terminator at the end of each message.
SCPI Conventions and Data Formats
Conventions
The following SCPI conventions are used throughout this guide.
Angle brackets < >
Items within angle brackets are parameter abbreviations. For example, <NR1>
indicates a specific form of numerical data.
Vertical bar
|
Vertical bars separate alternative parameters. For example, VOLT | CURR indicates
that either "VOLT" or "CURR" can be used as a parameter.
Square Brackets [ ]
Items within square brackets are optional. The representation [SOURce:]VOLTage
means that SOURce: may be omitted.
Braces
{ }
Braces indicate parameters that may be repeated zero or more times. It is used
especially for showing arrays. The notation <A>{<,B>} shows that parameter "A"
must be entered, while parameter "B" may be omitted or may be entered one or
more times.
Parentheses ( )
Items within parentheses are used in place of the usual parameter types to specify
a channel list. The notation (@1:3) specifies a channel list that includes channels
1, 2, and 3. The notation (@1,3) specifies a channel list that includes only channels
1 and 3.
