Synchronization With The Controller - YOKOGAWA WT200 User Manual

Digital power meter
Table of Contents

Advertisement

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 "
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 "
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?;
*SRE8;[: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
the condition register is changed from "
IM 253421-01E
9.91E+37 (Not
1
" if updating is in
" when bit 0 (
) of
FILTer 1
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 "
" command is used to generate a service
*SRE
request caused solely by the extended event register.
"
MEASure[:NORMal]:VALue?
a service request is generated.
Using the COMMunicate:WAIT command
The "
COMMunicate:WAIT
" command halts
communications until a specific event is generated.
Example
STATus:FILTer1 FALL;:STATus:
EESE 1;EESR?;
[:CONFigure]:VOLTage:RANGe 60V<PMT>
(Response to
STATus:EESR?
COMMunicate:WAIT 1;:
MEASure[:NORMal] :VALue?<PMT>
For a description of "
STATus:FILTer 1 FALL
"
STATus:EESR?
", see "Using the extended event
register" on this page.
"
COMMunicate:WAIT 1
" means that communications is
halted until bit 0 of the extended event register is set to
"
1
".
"
MEASure[:NORMal]:VALue?
bit 0 of the extended event register is set to "
14.2 Program Format
" will not be executed until
is decoded.)
" and
" will not be executed until
1
".
14-9
14

Advertisement

Table of Contents
loading

Table of Contents