ROUTe:SEQuence:TRIGger[:IMMediate]
Syntax
ROUTe:SEQuence:TRIGger[:IMMediate] <name>
Description
This command executes the specified sequence from non-volatile memory. If the specified sequence name is not currently stored in memory, an error will be generated.
Parameters
|
Name |
Type |
Range of Values |
Default Value |
|
<name> |
ASCII String |
A previously-defined sequence name consisting of up to 30 characters (see ROUTe:SEQuence:DEFine command). |
This is a required parameter |
Remarks
If you attempt to trigger a sequence while one is already executing, the trigger will be placed in a queue. When the trigger queue is full, a "trigger ignored" error will be generated.
To abort a sequence execution, use the ROUTe:SEQuence:ABORt command or a Device Clear. When the sequence is terminated, the resultant instrument state will be determined by how much of the sequence had been executed when the ABORt/Device Clear was received. An ABORt command (system abort) executed from within a sequence will not terminate the sequence. The *RST and SYSTem:PRESet commands will also abort a sequence execution prior to performing their own actions.
When a sequence is defined (see ROUTe:SEQuence:DEFine command), the specified commands are checked for proper syntax and absolute parameter range limits. If an error is detected during compilation, the entire sequence will be discarded. More extensive error checking, such as channel range expansion and validation, is performed when the sequence is executed.
A sequence may invoke another sequence. but may not invoke itself recursively. In addition, the number of invocations is limited to four levels of nesting and this is enforced at the time of execution. Exceeding the limit will abort the sequence and an error will be generated.
You can also execute a sequence when an alarm condition is reached (see ROUTe:SEQuence:TRIGger:SOURce command). Regardless of whether or not an alarm association is configured, you can always execute a sequence using the ROUTe:SEQuence:TRIGger[:IMMediate] command.
While a scan is running (see ROUTe:SCAN command), the instrument prevents use of all channels in banks that contain one or more channels in the specified scan list (these channels are dedicated to the scan). Therefore, if a sequence attempts to operate a channel in a scanned bank, an error is generated and the entire sequence will be discarded.
Example
The following command executes a sequence named "MYSEQ_1", which closes several channels on the module in slot 1 and opens a single channel on the module in slot 2.
ROUT:SEQ:DEF MYSEQ_1,"ROUT:CLOS (@1001:1009);OPEN (@2001)" !Define sequence ROUT:SEQ:TRIG MYSEQ_1 !Execute sequence