
2-8
IM 704310-12E
Using the extended event register
Changes in the condition register are reflected in the
extended event register (page 4-4).
Example
STATus:FILTer1 RISE;:STATus:EESE 1;
EESR?;*SRE 8;SSTart<PMT>
(Service request is awaited.)
MEMory:SEND?<PMT>
"STATus:FILTer1 RISE"
indicates that the transit filter
is set so that bit 0 (
FILTer1
) of the extended register is
set to
"1"
when bit 0 of the condition register is
changed from [
0
] to [
1
].
"STATus:EESE 1"
is a command used to reflect the
status of only 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 by the extended event register only.
"MEMory:SEND?"
will not be executed until 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 RISE;:STATus:EESR?;
SSTart<PMT>
(Response to
STATus:EESR?
is decoded.)
COMMunicate:WAIT 1;:MEMory:
SEND?<PMT>
For a description of
"STATus:FILTer1 RISE"
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
].
"MEMory:SEND?"
will not be executed until bit 0 of the
extended event register is set to [
1
].
2.5 Synchronization with the Controller