Commands - YOKOGAWA WT110 User Manual

Appendix 2.2 Program Format
2.2.3

Commands

There are two types of command (program header) which can
be sent from the controller to this instrument. They differ in
the format of their program headers.
They are
• Common command header
• Compound header
Common Command Header
Commands defined in IEEE 488.2-1987 are called common
commands. The header format of a common command is
shown below. An asterisk (*) must always be attached to the
beginning of a command.
∗
<Mnemonic>
An example of a common command
*CLS
Compound Header
Commands designed to be used only with this instrument are
classified and arranged in a hierarchy according to their
function. The format of a compound header is illustrated
below. A colon (:) must be used when specifying a lower-level
header.
:
: <Mnemonic>
An example of a compound header
CONFIGURE:MODE RMS
Note
A mnemonic is a character string made up of alphanumeric
characters.
Consecutive Commands
Command Group
A command group is a group of commands which have the
same compound header. A command group may contain sub-
groups.
Example
Commands relating to integration
INTEGRATE?
INTEGRATE:MODE
INTEGRATE:TIMer
INTEGRATE:STARt
INTEGRATE:STOP
INTEGRATE:RESet
When Consecutive Commands are in the Same
Group
This instrument stores the hierarchical level of the command
which is currently being executed, and performs analysis on
the assumption that the next command to be sent will also
belong to the same level. Therefore, it is possible to omit the
header if the commands belong to the same group.
Example DISPLAY1:FUNCTION V;ELEMENT 1<PMT>
App2-4
?
?
When Consecutive Commands are in Different
Groups
A colon (:) must be included before the header of a command,
if the command does not belong to the same group as the
preceding command.
Example DISPLAY1:FUNCTION V;:SAMPLE:HOLD ON<PMT>
In Case of Consecutive Common Commands
Common commands defined in IEEE 488.2-1987 are
independent of hierarchical level. Thus, it is not necessary to
add a colon (:) before a common command.
Example DISPLAY1:FUNCTION V;*CLS;ELEMENT 1<PMT>
When Separating Commands by <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 sent.
Example
DISPLAY1:FUNCTION V<PMT>DISPLAY1:ELEMENT 1<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 settings of one group to be output at once. Some
query groups comprising more than three hierarchical levels
can output all their lower level settings.
Example INTEGRATE?<PMT>
:INTEGRATE:MODE NORMAL;TIMER 0,0
In reply to a query, a response can be returned as a program
message to this instrument.
Header Interpretation Rules
This instrument interprets the header received according to the
following rules.
• Mnemonics are not case sensitive.
Example "FUNCtion" can also be written as "function" or
"Function".
• The lower-case part of a header can be omitted.
Example "FUNCtion" can also be written as "FUNCT" or
"FUNC".
• If the header ends with a question mark, the command is a
query. It is not possible to omit the question mark.
Example "FUNCtion?" cannot be abbreviated to anything
shorter than "FUNC?".
• If the "x" at the end of a mnemonic is omitted, it is assumed
to be "1".
Example If "ELEMent<x>" is written as "ELEM", this
represents "ELEMent1".
• Any part of a command enclosed by [ ] can be omitted.
Example [CONFigure]:SCALing[:STATe] ON can be
written as "SCAL ON".
• However, a part enclosed by [ ] cannot be omitted if is
located at the end of an upper-level query.
Example "SCALing?" and "SCALing:STATe?" belong to
different upper-level query levels.
IM 253401-01E