In this condition, the
INITiate:IMMediate
command must b e
sent via HP-IB to change the IDLE state to the WAIT FOR
TRIGGER state after reading the measurement data bya
controller.
2.
INITiate:CONTinuous ON
condition
In this condition, the IDLE state is automatically changed
to the WAIT FOR TRIGGER state without using the
INITiate:IMMediate
command after reading the measurement
data by a controller.
Note
When the
ABORt
command is sent under any state, the HP 4284A
state is forced to the IDLE state. In this condition there are no data
stored in the HP 4284A. If the
FETCh?
query is sent in this case, an
error (error message
0
230:
"Data corrupt or stale"
) will o ccur.
WAITING FOR TRIGGER state
In this state, the HP 4284A can accept a trigger command
while in the remote condition. When the trigger command is
sent to the HP 4284A, the state is automatically c
hanged to the
MEASUREMENT state.
There are three kinds of the trigger commands:
*TRG
common
command,
Group Execution Trigger
(
get
) bus command, and
TRIGger:IMMediate
SCPI command. These commands are divided
into twotypes in this trigger system. (Refer to Figure 7-10
.)
Figure 7-10. Trigger System and Trigger Commands
1.
TRIGger:IMMediate
SCPI command
Either the WAIT FOR TRIGGER state or the IDLE state,
the HP 4284A is triggered by sending the
TRIGger:IMMediate
Remote Control 7-13
To Next Page
