3-4
IM DL350-17EN
Upper-Level Query
An upper-level query is a query that is made by
appending a question mark to a command higher in
the group. The controller can receive all of the settings
in a group collectively by executing a highest-level
query. Some upper-level queries of a group, which may
be comprised of more than three hierarchical levels,
can cause the instrument to transmit all the lower level
settings.
Example
: CHANnel1?<PMT>
-> :CHANNEL1:DISPLAY ON;
LABEL "CH1";COUPLING DC;
POSITION 0.00;PROBE 10;
VDIV 50.0E+00;BWIDTH FULL;
OFFSET 0.0E+00;LSCALE:MODE 0
The response to an upper-level query can be sent back
to the instrument as a program message. This enables
the settings that were present when the upper-level
query was made to be reproduced later on. However,
some upper-level queries do not return setup data that
is not currently in use. Exercise caution because not
all of a group’s information is necessarily returned in a
response.
Header Interpretation Rules
The instrument interprets the header that it receives
according to the rules below.
• Mnemonics are not case sensitive.
Example
CURSor
can be written as
cursor
or
Cursor
.
• The lower-case characters can be omitted.
Example
CURSor
can be written as
CURSO
or
CURS
.
• The question mark at the end of a header indicates
that it is a query. You cannot omit the question mark.
Example The shortest abbreviation for
CURSor?
is
CURS?
.
• If the <x> (value) at the end of a mnemonic is
omitted, it is interpreted as a 1.
Example If you write
CHAN
for
CHANnel<x>
,
CHANnel1
is specified.
• Parts of commands and parameters enclosed in
square brackets ([ ]) can be omitted.
Example
TRIGger[:SIMPle]:LEVel
can be
written as
TRIG:LEV
.
However, the last section enclosed in square
brackets cannot be omitted in an upper-level query.
Example
TRIGger?
and
TRIGger:SIMPle?
are different queries.
3.2 Commands