Keithley 2461, Справочное руководство, Страница: 302 / 1109

Model 2461 Interactive SourceMeter® Instrument Reference Manual Section 3: Functions and features
2461-901-01 A/November 2015 3-131
Using trigger events to start actions in the trigger model
You can set up trigger blocks to respond to trigger events. Trigger events are signals that can be
generated by the instrument or by other system components.
Sources of the trigger event signals can be:
•
Front-panel TRIGGER key
•
Notify trigger blocks
•
Branch-on-event trigger blocks
•
Command interface triggers
•
Digital I/O lines
•
TSP-Link synchronization lines
•
LAN triggers
•
Event blenders, which combine other trigger events
•
Trigger timers
For information about the options that are not specific to the trigger model, see Triggering (on page 3-
99).
Trigger events
To use trigger events, you need to specify the event constant. The tables below show the constants
for the trigger events in the system.
Trigger events — SCPI command set
Trigger events
Event description Event constant
No trigger event
NONE
Front-panel TRIGGER key press
DISPlay
Notify trigger block
<n>
(1 to 8); the trigger model generates a
trigger event when it executes the notify block
NOTify<n>
A command interface trigger:
•
Any remote interface: *
TRG
•
GPIB only: GET bus command
•
VXI-11: VXI-11 command
device_trigger
COMMand
Line edge (either rising, falling, or either based on the
configuration of the line) detected on digital input line
<n>
(1 to 6)
DIGio<n>
Line edge detected on TSP-Link synchronization line
<n>
(1 to 3)
TSPLink<n>
Appropriate LXI trigger packet is received on LAN trigger object
<n>
(1 to 8)
LAN<n>
Trigger event blender
<n>
(1 or 2), which combines trigger events
BLENder<n>
Trigger timer
<n>
(1 to 4) expired
TIMer<n>
Source limit condition occurs
SLIMit