Table of Contents
Advertisement
Making Coordinated Measurements
When CMB is enabled, each emulator is required to break to background
when CMB READY goes false, and will wait for CMB READY to go true before
returning to the run state. When an enabled emulator breaks, it will drive the
CMB READY false and will hold it false until it is ready to resume running.
When an emulator is reset, it also drives CMB READY false.
EXECUTE The CMB EXECUTE line is low true. Any HP 64700 on the
CMB can drive this line. It serves as a global interrupt and is processed
by both the emulator and the analyzer. This signal causes an emulator to
run from a specified address when CMB READY returns true.
BNC Trigger Signal
The BNC trigger signal is a positive rising edge TTL level signal. The BNC
trigger line can be used to either drive or receive an analyzer trigger, or
receive a break request for the emulator.
Comparison Between CMB and BNC Triggers The CMB trigger and
BNC trigger lines have the same logical purpose: to provide a means for
connecting the internal trigger signals (trig1 and trig2) to external
instruments. The CMB and BNC trigger lines are bi-directional. Either
signal may be used directly as a break condition.
The CMB trigger is level-sensitive, while the BNC trigger is edge-sensitive.
The CMB trigger line puts out a true pulse following receipt of EXECUTE,
despite the commands used to configure it. This pulse is internally ignored.
Note that if you use the EXECUTE function, the CMB TRIGGER should not
be used to trigger external instruments, because a false trigger will be
generated when EXECUTE is activated.
306
Advertisement
Table of Contents
