Table Of Contents

Generate Tag Cluster (Timestamp) (G Dataflow)

Last Modified: November 18, 2019

Creates or adds to an array of tag clusters, which specifies the tag data values for Multi Write to communicate.

The data type of the tag cluster must be a timestamp.

Programming Patterns

Wire this node to Multi Write to record values for multiple tags in a single operation. This improves performance compared to writing each tag individually.

connector_pane_image
datatype_icon

time stamp

Date and time the server obtained the most recent data value. Leave the time stamp input empty to have the server manage the timestamp.

datatype_icon

tag clusters in

Clusters of tags the web service references to communicate data.

datatype_icon

tag in

Tag the server references to communicate measurement data.

datatype_icon

value

Data value of the tag or tags.

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

tag clusters out

Clusters of tags the web service references to communicate data.

datatype_icon

tag out

Tag the server references to communicate measurement data.

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.

Where This Node Can Run:

Desktop OS: Windows

FPGA: Not supported

Web Server: Supported in VIs that run in a web application


Recently Viewed Topics