Table Of Contents

Create Advanced Sequence Step (Create Advanced Sequence Commit Step with Channels) (G Dataflow)

Last Modified: March 27, 2020

Creates a Commit step in the active advanced sequence. A Commit step configures the device to a user-defined known state before starting the advanced sequence. When you create an advanced sequence step, each property you passed to the Create Advanced Sequence node is reset to its default value for the new step. To configure the step, you must first designate the new step as the active step using the Active Advanced Sequence Step property or the set as active step parameter of this node. Once the step is active, use the niDCPower Property Node to configure new values for the step.

spd-note-note
Note  

You can specify the active advanced sequence using the Active Advanced Sequence property.

connector_pane_image
datatype_icon

channel name

Output channel(s) to which to apply this configuration value.

Channel Name Syntax

You can input the channel name with the following options:
  • A single channel, such a 0
  • A list of channels, such as 0,1 or 3,2,1,0.
  • A range of channels, such as 0-7 or 0:7.
spd-note-note
Note  

The order of channels in a list is important. NI-DCPower performs configurations of multiple output channels in the order the channels occur in the list.

datatype_icon

set as active step

Boolean value that specifies whether the current step in the active sequence is active.

True The current step in the advanced sequence is active.
False The current step in the advanced sequence is not active.
datatype_icon

session in

Instrument session obtained from the Initialize With Channels node.

datatype_icon

error in

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

datatype_icon

session out

Handle used to identify the session in all subsequent NI-DCPower node calls.

datatype_icon

error out

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.

Commit Step Node Compatibility

  • Using the Set Sequence node with Advanced Sequence Mode nodes is not supported.
  • When a Commit step exists in the active advanced sequence, you cannot set Output Function to Pulse Voltage or Pulse Current in either the Commit step (-1) or step 0.

When Does the Commit Step Run in a Sequence?

The driver applies the Commit step to the device when the session transitions to the Committed state. After the driver applies the Commit step to the device, the driver waits until the Source Delay has elapsed before waiting for the Start trigger.

spd-note-note
Note  
  • You can provide a specific Source Delay for the Commit step if you set Source Delay as one of the properties to be configured with Create Advanced Sequence.
  • If you call the Initiate node while the device is in the Uncommitted state, the session implicitly moves through the Committed state before moving to the Running state.

Differences Between the Commit Step and Other Advanced Sequence Steps

  • The source unit does not wait on any triggers before running the Commit step.
  • The source unit does not emit a Source Complete Event when the Commit step is complete.
  • No measurements are taken in the Commit step, therefore you cannot set the Aperture Time, Measure Record Length, and DC Noise Rejection properties in the Commit step.
  • The Sequence Step Delta Time property does not apply to the Commit step, and you cannot configure the Sequence Step Delta Time property in the Commit step.

Where This Node Can Run:

Desktop OS: Windows

FPGA:

Web Server: Not supported in VIs that run in a web application

Hardware Support:

This node does not support the following hardware:

  • PXI-4110
  • PXIe-4112
  • PXIe-4113
  • PXI-4130
  • PXI-4132
  • PXIe-4154
  • PXIe-4162
  • PXIe-4163

Recently Viewed Topics