5-4
IM WT3001E-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 query groups which are comprised of more than
three hierarchical levels can output all the lower level
settings.
Example
:INTEGrate?<PMT> ->
:INTEGRATE:MODE NORMAL;
ACAL 0;TIMER 0,0,0<RMT>
The response to an upper-level query can be
transmitted as a program message back to the
instrument. In this way, the settings that existed when
the upper-level query was made can be restored.
However, some upper-level queries do not return setup
information that is not currently in use. It is important
to remember that not all the group’s information is
necessarily returned as part of a response.
Header Interpretation Rules
The instrument interprets the header that is received
according to the rules below.
• Mnemonics are not case sensitive.
Example “
CURSor
” can also be written as “
cursor
”
or “
CUrsor
.”
• The lower-case section of the header can be
omitted.
Example “
CURSor
” can also be written as “
CURSO
”
or “
CURS
.”
• The question mark (
?
) at the end of a header
indicates that it is a query. The question mark (
?
)
cannot be omitted.
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 “
ELEMent<x>
” is written as “
ELEM
,” it
means “
ELEMent1
.”
• The section enclosed by braces ([]) can be omitted.
Example “
[:INPut]:SCALing[:STATe][:ALL]
ON
” can be written as “
SCAL ON
.”
However, the last section enclosed by braces ([])
cannot be omitted in an upper-level query.
Example “
SCALing?
” and “
SCALing:STATe?
” are
different queries.
5.2 Commands