Send Software Edge Trigger (G Dataflow)

Instrument session obtained from the Initialize Acquisition Session node, the Initialize Generation Session node, or the Initialize External Calibration node.

The trigger you want to assert.

You can select Start Trigger, Reference Trigger, Advance Trigger, Script Trigger, or Stop Trigger as the value for this control.

The specified details of the script trigger.

This parameter can be ScriptTrigger0, ScriptTrigger1, ScriptTrigger2, or ScriptTrigger3; or you can leave this parameter blank for the Start, Reference, Advance, and Stop triggers.

Note  

PXI-6544/6545/6547/6548 devices do not support ScriptTrigger 3.

Error conditions that occur before this node runs.

The node responds to this input according to standard error behavior.

Standard Error Behavior

Many nodes provide an error in input and an error out output so that the node can respond to and communicate errors that occur while code is running. The value of error in specifies whether an error occurred before the node runs. Most nodes respond to values of error in in a standard, predictable way.

error in does not contain an error	error in contains an error
If no error occurred before the node runs, the node begins execution normally. If no error occurs while the node runs, it returns no error. If an error does occur while the node runs, it returns that error information as error out.	If an error occurred before the node runs, the node does not execute. Instead, it returns the error in value as error out.

Default: No error

Handle that identifies the session in all subsequent node calls.

The session out parameter is obtained from the Initialize Acquisition Session node or the Initialize Generation Session node.

Error information.

The node produces this output according to standard error behavior.

Standard Error Behavior

Many nodes provide an error in input and an error out output so that the node can respond to and communicate errors that occur while code is running. The value of error in specifies whether an error occurred before the node runs. Most nodes respond to values of error in in a standard, predictable way.

error in does not contain an error	error in contains an error
If no error occurred before the node runs, the node begins execution normally. If no error occurs while the node runs, it returns no error. If an error does occur while the node runs, it returns that error information as error out.	If an error occurred before the node runs, the node does not execute. Instead, it returns the error in value as error out.