3: Functions and features Model 2450 Interactive SourceMeter® Instrument
3-112 2450-901-01 Rev. B/September 2013
Respond to an event with a wait block
The wait building block causes the trigger model to stop and wait for an event or set of events to
occur before continuing. You can specify up to three events for each wait block.
You can use the wait block to synchronize measurements with other instruments and devices.
Events that you can set the instrument to wait for include:
• Digital input/output signals, such as DB-9 and TSP-Link
• LAN events
• Blenders
The event can occur before the trigger model reaches the wait block. If the event occurs after the
trigger model starts but before the trigger model reaches the wait block, the trigger model records the
event. When the trigger model reaches the wait block, it executes the wait block without waiting for
the event to happen again.
The instrument clears the memory of the recorded event when the trigger model is at the start block
and when the trigger model exits the wait block.
You can have up to eight wait blocks in a trigger model.
All items in the list are subject to the same action — you cannot combine AND and OR logic in a single
command.
The events can be one of the events shown in the following table.
Using the branch-on-event trigger blocks
The branch-on-event building block goes to a branching block after a specified trigger event occurs. If
the trigger event has not yet occurred when the trigger model reaches the branch-on-event block, the
trigger model continues to execute the blocks in the normal sequence. After the trigger event occurs,
the next time the trigger model reaches the branch-on-event block, it goes to the branching block.
The event can be one of the events shown in the following table.
Command interface triggering
A command interface trigger occurs when:
• A GPIB GET command is detected (GPIB only)
• A VXI-11 device_trigger method is invoked (VXI-11 only)
• A *TRG message is received
To monitor for command interface trigger, use the event trigger.EVENT_COMMAND (TSP) or the
event COMMAND (SCPI). To ensure that commands and triggers that are issued over the command
interface are processed in the correct order, the instrument does not generate a trigger event until:
• The trigger command is executed
• TSP only: trigger.wait() retrieves the trigger command from the command queue before it
would normally be executed
To Next Page
Loading...
Need help?
General
