10-8
IM 704610-01E
Using the Extended Event Register
The changes in the condition register can be reflected
in the extended event register (page 10-37).
Example:
STATus:FILTer1 RISE;:STATus:
EESE 1;EESR?;*SRE 8;SSTart<PMT>
(Wait for a service request)
CALCulation:JITTer?<PMT>
The “
STATus:FILTer1 RISE
” command sets the
transition filter so that bit 0 (FILTer1) of the extended
event register is set to “
1
” when bit 0 of the condition
register changes from “
0
” to “
1
.”
The “
STATus:EESE 1
” command is used to reflect
only bit 0 of the extended event register to the status
byte.
The “
STATus:ESSR?
” command clears the extended
event register after querying its contents.
The “
*SRE
” command is used to generate a service
request solely on the cause of the extended event
register.
The “
CALCulation:JITTer?
” command will not be
executed until a service request is generated.
Using the COMMunicate:WAIT command
The “
COMMunicate:WAIT
” command is used to wait
for a specific event to occur.
Example:
STATus:FILTer1 RISE;:STATus:
EESR?;SSTart<PMT>
(reads the response to
STATus:ESSR?
)
COMMunicate:WAIT 1;:
CALCulation:JITTer?<PMT>
The descriptions of “
STATus:FILTer1 RISE
” and
“
STATus:EESR?
” are the same as those given in the
previous section regarding the extended event register.
The “
COMMunicate:WAIT 1
” command indicates that
the program will wait for bit 0 of the extended event
register to be set to “
1
.”
The “
CALCulation:JITTer?
” command will not be
executed until bit 0 of the extended event register is
set to “
1
.”
Note
On the TA220, the statistical data can be read during
measurement without having to synchronize with the controller.
The value queried in this case is the previous statistical value.
Example:
CALCulation:JITTer?
10.1 Program Format