Table Of Contents

XNET Database Create Object (PDU » Signal) (G Dataflow)

Last Modified: November 2, 2017

Create a new dynamic signal (signal within a multiplexed PDU). This node selection is the same as XNET Database Create (Dynamic Signal), except that it uses a PDU as the signal's parent, not a frame.

connector_pane_image
datatype_icon

PDU in

The PDU parent object.

datatype_icon

signal name

The name of the signal to create. Lowercase letters, uppercase letters, numbers, and the underscore (_) are valid characters for the name. The space ( ), period (.), and other special characters are not supported within the name. The name must begin with a letter (uppercase or lowercase) or underscore, and not a number. The name is limited to 128 characters.

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

PDU out

The reference to the newly created PDU object.

datatype_icon

signal out

The I/O name of the newly created signal object.

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.

Description

This node creates an XNET signal object. It is an instance of XNET Database Create Object.

The signal name input becomes the Name (Short) property of the created object. This is distinct from the string contained within signal out, which uses the syntax described in XNET Signal I/O Name.

The signal object is created and remains in memory until the database is closed. This node does not change the open database file on disk. To save the newly created object to the file, use XNET Database Save.

Where This Node Can Run:

Desktop OS: Windows

FPGA: Supported

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


Recently Viewed Topics