12: SCPI command reference 2470 High Voltage SourceMeter Instrument
12-170 2470-901-01 Rev. A / May 2019
All items in the list are subject to the same action; you cannot combine AND and OR logic in a single
bl
ock.
You cannot leave the first event as no trigger. If the first event is not defined, the trigger model errors
when you attempt to initiate it.
The following usage has been deprecated; replace it with the usage above that includes the <clear>
parameter.
:TRIGger:BLOCk:WAIT <blockNumber>, <event>, <logic>, <event>
:TRIGger:BLOCk:WAIT <blockNumber>, <event>, <logic>, <event>, <event>
The following table shows the constants for the events.
Trigger events
Event description Event constant
Trigger event blender <n> (up to two), which combines trigger
events
A command interface trigger:
ï‚§ Any remote interface: *TRG
ï‚§ GPIB only: GET bus command
ï‚§ USB only: A USBTMC TRIGGER message
ï‚§ VXI-11: VXI-11 command
Line edge (either rising, falling, or either based on the
configuration of the line) detected on digital input line
(1 to 6)
Front-panel TRIGGER key press
Appropriate LXI trigger packet is received on LAN trigger object
<n>
(1 to 8)
<n>
(1 to 8); the trigger model generates a
trigger event when it executes the notify block
Source limit condition occurs
Trigger timer <n> (1 to 4) expired
Line edge detected on TSP-Link synchronization line <n> (1 to 3)
Example 1
:TRIGger:BLOCk:WAIT 9, DISP
Set trigger model block 9 to wait for a user to press the
TRIGGER key on the front panel before continuing and to act
on a recorded TRIGGER key event that gets detected either
before or after reaching block 9.
Example 2
:TRIGger:BLOCk:WAIT 9, DISP, ENTer
Set trigger model block 9 to wait for a user to press the
TRIGGER key on the front panel before continuing and to act
only on a recorded TRIGGER key event that gets detected
Also see
Wait block (on page 8-29)