Section 3: Functions and features
2606B System SourceMeter® Instrument Reference Manual
3-38
2606B-901-01 Rev. B / May 2018
Figure 52: Front panel TRIG key triggering
Using trigger events to start actions on trigger objects
Trigger objects can be configured to respond to events generated by other trigger objects, such as
using a digital I/O trigger to initiate a sweep. To configure a trigger object to monitor for an event,
assign the event ID of the trigger event to the stimulus input. When the specified trigger event occurs,
the trigger object will perform an action. The programming example below illustrates how to generate
a digital I/O line 2 output trigger pulse for each SMU A source complete event:
-- Configure digio line 2 to generate an output trigger pulse each
-- time SMU A generates a source complete event.
digio.trigger[2].stimulus = smua.trigger.SOURCE_COMPLETE_EVENT_ID
The following figure illustrates this example.
Figure 53: Using trigger events to start actions
A stimulus input can be configured to monitor for only one trigger event ID at a time. To monitor more
than one event, use an event blender.
See
(on page 3-46) for more information.
Action overruns
An action overrun occurs when a trigger object receives a trigger event and is not ready to act on it.
The action overruns of all trigger objects are reported in the operation event registers of the status
model. Please refer to
(on page 5-12, on page E-1) and the appropriate sections on
each trigger object for further details on conditions under which an object generates an action
overrun.