
Model 2450 Interactive SourceMeter® Instrument Reference Manual
Section 3: Functions and features
2450-901-01 Rev. B/September 2013
3-109
Checking the state of the trigger model
The trigger model can be in one of several states. The state is shown in the indicator bar on the Home page of
the instrument. You can also check the status using remote commands.
The trigger model states are described in the following table. This table also shows the indicator that is shown on
the front panel and the feedback you get from the remote interface.
Front panel
indicator
Remote feedback
Description
CONT
Not available through remote interface
Instrument is making measurements
continuously
MAN
Not available through remote interface
Instrument makes measurements when you
press the front-panel TRIGGER key.
IDLE
trigger.STATE_IDLE
Trigger model stopped.
RUN
trigger.STATE_RUNNING
Trigger model is running
WAIT
trigger.STATE_WAITING
The trigger model has been in the same
wait block for more than 100 ms
Using the front panel
The state of the trigger model is indicated on the status bar with the indicators shown in the previous
table.
Using SCPI commands:
Send the command:
:TRIGger:STATe?
Using TSP commands:
Send the command:
print(trigger.model.state())
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