Events; Event Blenders - Keithley 3700 series Reference Manual

Section 7: Scanning

Events

Event detectors monitor an event. They have one input signal, the stimulus, which is the event
that they monitor. They have two output signals (see figure below). Detected reflects the
detection state of the event detector. If an event was detected, the detected signal is asserted.
Event detectors are usually coupled to something that consumes the events. When an event is
consumed, the detected state of the event detector is reset. Should an event be detected while
the event detector is in the detected state, the overrun signal will be asserted. The overrun
signal can only be cleared by an ICL command.
Equation 1: Event detector
The Series 3700 trigger model has the following events and associated ICLs attributes.
Event
Scan Ready Event
Scan Start Event
Channel Ready Event
Measure Complete Event
Sequence Complete
Event
Scan Complete Event
Idle Event

Event blenders

Advanced scanning needs a way to wait for one of several events or all of several events. An
event blender provides for this combining or blending of events. An event blender can combine
up to four events in either an "or" mode or an "and" mode. When in or-mode, any one of the
input events will cause an output event to be generated. When in and-mode, all the input events
must occur before an output event is generated.
When operating in and-mode, if an event is detected more than once before all events
necessary for the generation of an output event, an action overrun will be generated. When
operating in or-mode, an action overrun will be generated when two or more source events are
detected simultaneously.
7-6
Series 3700 System Switch/Multimeter Reference Manual
Associated ICL attribute
scan.trigger.EVENT_SCAN_READY
scan.trigger.EVENT_SCAN_START
scan.trigger.EVENT_CHANNEL_READY
scan.trigger.EVENT_MEASURE_COMP
scan.trigger.EVENT_SEQUENCE_COMP
scan.trigger.EVENT_SCAN_COMP
scan.trigger.EVENT_IDLE
Document Number: 3700S-901-01 Rev. A / August 2007