Keithley System SourceMeter 2601B, Справочное руководство

Страница: 188 / 864

Series 2600B System SourceMeter® Instrument Reference Manual Section 3: Functions and features
2600BS-901-01 Rev. B / May 2013 3-53
The command queue can fill up with trigger entries if too many
*TRG
messages are received while a
test script is running, even if the script is processing triggers. You can avoid this by using the
localnode.prompts4882
attribute (see TSP command reference (on page 7-1) for more
information), and by using
trigger.wait()
calls that remove the
*TRG
messages from the
command queue. If the command queue fills with too many trigger entries, messages like
abort
will
not be processed.
Trigger generator
The Series 2600B has two trigger generators that can be used to generate trigger events. Use the
trigger.generator[ N ].assert()
function to directly trigger events from the command interface
or a script (for example, you can trigger a sweep while the instrument is under script control).
The
trigger.generator[ N ].EVENT_ID
constant is an identification number that identifies events
generated by this generator. To have another trigger object respond to trigger events generated by
this generator, set the other object's stimulus attribute to the value of this constant.
Manual triggering
The TRIG key is used for manual triggering. Each time the TRIG key is pressed, a trigger event is
generated. You can monitor for a manual trigger event using the event ID
display.trigger.EVENT_ID
. See Using the TRIG key to trigger a sweep (on page 3-39) for an
example of how to use a manual trigger.
There are no action overruns for manual triggering.
Interactive triggering
The complexity of some test system configurations may not allow a static trigger setup. These
configurations would require more dynamic control of triggering than the static trigger setup provides.
For such cases, a setup providing interactive trigger programming would allow the generation and
detection of trigger events that can be controlled on demand under remote control. For example,
interactive triggering can be used when you need to make multiple source function changes or
implement conditional branching to other test setups based on recent measurements.