Table of Contents
Advertisement
2.2 Commands
When Separating Commands with <PMT>
If a terminator is used to separate two commands,
each command is a separate message. Therefore, the
common header must be typed in for each command
even when commands of the same command group
are being concatenated.
Example
MEASURE:MODE TSTAMP<PMT>MEASURE:
FUNCTION DUTY,A<PMT>
Upper-level Query
An upper-level query is a compound header to which a
question mark is appended. Execution of an upper-
level query allows all a group
once. Some query groups comprising more than three
hierarchical levels can output all their lower level
settings.
Example
MEASURE?<PMT>
MODE HHISTOGRAM;FUNCTION PERIOD,A;
SLOPE RISE
In reply to a query, a response can be returned as a
program message to this instrument. Transmitting a
response can restore the settings made when the
query was executed. However, some upper-level
queries will not return set-up data which is not currently
in use. Note that not all a group
necessarily be sent out as a response.
2-4
'
s settings to be output at
→
:MEASURE:
'
s information will
Header Interpretation Rules
This instrument interprets the header received
according to the following rules.
• Mnemonics are not case sensitive.
Example
"MEASure"
"measure"
• The lower-case part of a header can be omitted.
Example
"MEASure"
"MEASU"
or
• If the header ends with a question mark, the
command is a query. It is not possible to omit the
question mark.
Example
"MEASure?"
anything shorter than
• If the
"
x
"
at the end of a mnemonic is omitted, it is
assumed to be
1
.
"
"
Example
If
"WINDow<x>"
represents
• Any part of a command enclosed by [ ] can be
omitted.
Example
CALCulation[:WINDow1]:AVERage?
be written as
However, a part enclosed by [ ] cannot be omitted if is
located at the end of an upper-level query.
can also be written as
or
"Measure"
.
can also be written as
"MEAS"
.
cannot be abbreviated to
"MEAS?"
.
is written as
"WIND"
"WINDow1"
.
"CALCulation:AVERage?"
IM 704310-12E
, this
can
.
Advertisement
Table of Contents
