Table Of Contents

Fire Software-Triggered Timing Source (G Dataflow)

Last Modified: January 12, 2018

Activates a software-triggered timing source.

spd-note-note
Note  

Because the identifier of the timing source is an integer rather than a string, you can use this node in time-critical code.

Programming Patterns

Use Create Timing Source to create a software-triggered timing source that interfaces with this node.

connector_pane_image
datatype_icon

trigger ID in

Numeric identifier of the software-triggered timing source. The valid range of trigger ID in values is 0-127.

Default: 0

datatype_icon

number of ticks

Number of ticks to increment the internal tick counter of the timing source.

Default: 1

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

trigger ID out

Unchanged value of the input trigger ID.

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.

Triggering Multiple Iterations

If you want to trigger multiple Timed Loop iterations with a single call to Fire Software-Triggered Timing Source, configure the mode of the Timed Loop to process data that becomes available during missed periods. The internal tick counter of the Timed Loop advances by number of ticks when this node executes. If the internal tick counter jumps past one or more Timed Loop periods, the Timed Loop regards those periods as missed periods.

Where This Node Can Run:

Desktop OS: Windows

FPGA: Not supported

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


Recently Viewed Topics