YOKOGAWA WT1800 User Manual page 27

4.2 Commands
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;TIMER
0,0,0;
ACAL 0<RMT>
The response to an upper-level query can be sent
back to the WT1800 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
parameters that are not currently in use. Exercise
caution because not all of a group's information is
necessarily returned in a response.
Header Interpretation Rules
The WT1800 interprets the header that it receives
according to the rules below.
• Mnemonics are not case sensitive.
"CURSor" can be written as "cursor"
Example
or "Cursor."
• The lower-case characters can be omitted.
"CURSor" can be written as "CURSO"
Example
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.
If "ELEMent<x>" is written as "ELEM,"
Example
it means "ELEMent1."
• Parts of commands and parameters enclosed in
square brackets ([ ]) can be omitted.
"[:INPut]SCALing[:STATe][:ALL]
Example
ON" can be written as "SCAL
ON."
However, the last section enclosed in square
brackets cannot be omitted in an upper-level query.
Example: "SCALing?" and "SCALing:STATe?"
are different queries.
4-4
IM WT1801-17EN