YOKOGAWA WT210, User Manual, Page: 225 / 316

14-9
IM 760401-01E
Communication Commands 2 (System of Commands Complying to the IEEE 488.2-1992 Standard)
14
<Block data>
<Block data> is arbitra 8-bit data. <Block data> is only
used for response messages. Response messages
are expressed in the following form.
Form Example
#N<N-digit decimal value><Data byte string> #500012ABCDEFGHIJKL
#N
Indiates that the data is <Block data>. “ N ” is an ASCII
character string number (digits) which indicates the
number of data bytes that follow.
<N-digits decimal value>
Indicates that number of bytes of data. (Example:
00012 = 12bytes )
<Data byte string>
The actual data. (Example:
ABCDEFGHIJKL
)
Data is comprised of 8-bit values (0 to 255). This
means that the ASCII code “ 0AH ”, which stands for
“
NL
”, can also be a code used for data. Hence, care
must be taken when programming the controller.
14.2.6 Synchronization with the
Controller
There are two kinds of command; overlap commands
and sequential commands. Execution of an overlap
command may start before execution of the previously
sent command is completed.
For example, if the next program message is
transmitted after the measurement range has been
changed and an query is made about the
measurement data, it may occur that regardless
whether the measurement data have been updated,
MEASure[:NORMal]:VALue? will be executed. The
display becomes “
- - - - -
” (no data) and “
9.91E+37
(Not a number) ” will be output.
[CONFigure:]VOLTage:RANGe 60V;:
MEASure[:NORMal:VALue?<PMT>
In this case, synchronization with the time at which the
update of measurement data is completed must be
accomplished, as shown next.
Using STATus:CONDition? query
A “
STATus:CONDition?
” query is used to make an
inquiry about the contents of the condition register
(section 14.4). It is possible to judge whether updating
measurement data is in progress or not by reading bit
0 of the condition register. Bit 0 is “
1
” if updating is in
progress, and “ 0 ” if updating is stopped.
Using the extended event register
Changes in the condition register are reflected in the
extended event register (section 14.4).
Example STATus:FILTer1 FALL;:STATus:EESE 1;
EESR?;*SRE 8;[:CONFigure]:VOLTage:
RANGe 60V<PMT>
(Service request is awaited.)
MEASure[:NORMal]:VALue?<PMT>
“
STATus:FILTer1 FALL
” indicates that the transit filter
is set so that bit 0 is set to “ 1 ” when bit 0 ( FILTer1 ) of
the condition register is changed from “
1
” to “
0
”.
“ STATus:EESE 1 ” is a command used only to reflect
the status of bit 0 of the extended event register in the
status byte.
“
STATus:EESR?
” is used to clear the extended event
register.
The “
*SRE 8
” command is used to generate a service
request caused solely by the extended event register.
“
MEASure[:NORMal]:VALue?
” will not be executed until
a service request is generated.
14.2 Program Format