Linking Commands
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;OUTPut:TTLTrg3 ON
or
TRIG:SOUR IMM;*TRG
Linking Multiple complete SCPI Commands. Use both a semicolon and a colon
between the commands. For example:
OUTPut:TTLTrg2 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):
[SENSe:]
FUNCtion
:RESistance <
range
>,(@<
ch_list
>)
:TEMPerature <
sensor_type
>,<
sub_type
>[,<
range
>,](@<
ch_list
>)
:VOLTage[:DC] [<
range
>,](@<
ch_list
>)
Rather than send a complete SCPI command to set each function, you could send:
FUNC:RES 10000,(@100:107);TEMP RTD,92,(@108:115);VOLT (@116,123)
This sets the first 8 channels to measure resistance, the next 8 channels to measure
temperature, and the next 8 channels to measure voltage.
Note
The command keywords following the semicolon must be from the same command
branch and level as the complete command preceding the semicolon or Error -113,
“ Undefined header” will be generated.
Chapter 5
HP E1313/E1413 Command Reference 157
Artisan Technology Group - Quality Instrumentation ... Guaranteed | (888) 88-SOURCE | www.artisantg.com