Table of Contents
Advertisement
2.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 (page App2-37). 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 (page App2-38).
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" when bit 0 (FILTer 1) 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" 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.
IM 253401-01E
Appendix 2.2 Program Format
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? is decoded.)
COMMunicate:WAIT 1;:MEASure[:NORMal]
:VALue?<PMT>
For a description of "STATus:FILTer 1 FALL" and
"STATus:EESR?", refer to "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?" will not be executed until bit 0
of the extended event register is set to "1".
App
App2-7
Advertisement
Table of Contents
