Section 7: Triggering
Using trigger events to start actions on trigger objects
You can configure trigger objects 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 performs 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.
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
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. Refer to
conditions that generate an action overrun.
7-10
Figure 63: Using trigger events to start actions
Status model
(on page 10-1) and the sections on each trigger object for details on the
Model 2606B System SourceMeter® Instrument Reference Manual
Event blenders
(on page 7-21) for more information.
2606B-901-01 Rev. C November 2021
Need help?
Do you have a question about the KEITHLEY SourceMeter 2606B and is the answer not in the manual?