Table of Contents
Advertisement
Linking
Commands
Chapter 6
integer indicates the number of <data byte(s)> in the block.
Example of sending or receiving 1024 data bytes:
#41024<byte><byte1><byte2><byte3><byte4>...
...<byte1021><byte1022><byte1023><byte1024>
OR
Indefinite Length;
Example of sending or receiving 4 data bytes:
#0<byte><byte><byte><byte><NL^END>
Optional Parameters
Parameters shown within square brackets ([ ]) are optional parameters. (Note that
the brackets are not part of the command, and should not be sent to the instrument.)
If you do not specify a value for an optional parameter, the instrument chooses a
default value. For example, consider the
FORMAT:DATA <type>[,<length>] command. If you send the command without
specifying <length>, a default value for <length> will be selected depending on the
<type> of format you specify. For example:
FORMAT:DATA ASC will set [,<length>] to the default for ASC of 7
FORMAT:DATA REAL will set [,<length>] to the default for REAL of 32
FORMAT:DATA REAL, 64 will set [,<length>] to 64
Be sure to place a space between the command and the first parameter.
Linking commands is used when you want to send more than one complete command
in a single command statement.
Linking IEEE-488.2 Common Commands with SCPI Commands. Use a
semicolon between the commands. For example:
*RST;OUTP:TTLT3 ON
Linking Multiple complete SCPI Commands. Use both a semicolon and a colon
between the commands. For example:
OUTP:TTLT2 ON;:TRIG:SOUR EXT
The semicolon as well as separating commands tells the SCPI parser to expect the
command keyword following the semicolon to be at the same hierarchical level (and
part of the same command branch) as the keyword preceding the semicolon. The
colon immediately following the semicolon tells the SCPI parser to reset the expected
hierarchical level to Root.
Linking a complete SCPI Command with other keywords from the same branch
and level. Separate the first complete SCPI command from next partial command
with the semicolon only. For example take the following portion of the [SENSE]
subsystem command tree (the FUNCtion branch):
#0<data byte(s)><NL^END>
TRIG:SOUR IMM;*TRG
or
HP E1415 Command Reference
161
Advertisement
Table of Contents
