High Voltage SourceMeter Instrument Reference Manual Section 8:
2470-901-01 Rev. A / May 2019 8-3
Triggering
Triggering allows you to start and synchronize source and measure actions on one or more
instruments with a trigger event or a combination of trigger events that you set. This section describes
some of the options available for triggering, including command interface triggering, timers, and event
blenders.
Command interface triggering
A command interface trigger event 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 use a command interface trigger event as an input stimulus for another trigger object, set the
stimulus as TSP event trigger.EVENT_COMMAND or the SCPI event COMMAND. To ensure that
trigger commands 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
Command interface triggering does not generate action overruns. The triggers are processed in the
order that they are received in the 2470 command queue. The 2470 only processes incoming
commands when no commands are running. Unprocessed input triggers can cause an overflow in the
command queue. It is important to make sure a script processes triggers while it is running.
If you are using a test script using TSP, the command queue can fill up with trigger entries if over 50
*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 (on page 14-92
) attribute, and by using
trigger.wait() calls that remove the *TRG messages from the command queue. If the command
queu
e fills with too many trigger entries, messages such as abort are not processed.
To Next Page
Loading...
Need help?
General
