Table Of Contents

XNET Database Merge (XNET Database Merge (LIN Schedule)) (G Dataflow)

Last Modified: November 2, 2017

Merges a LIN schedule object with all child objects into the destination cluster.

connector_pane_image
datatype_icon

wait for complete?

An input used to split the merging process into parts (for example, to display a progress bar).

datatype_icon

target cluster in

The I/O name of the cluster where the source cluster is merged.

datatype_icon

source LIN schedule

The I/O name of the LIN schedule to be merged into the target cluster.

datatype_icon

copy mode

An input that defines the merging behavior if the target cluster already contains elements with the same name.

datatype_icon

prefix

An input added to the source cluster name if an element with the same name exists in the target cluster.

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

percent complete

An output used when wait for complete? is false.

datatype_icon

target cluster out

A copy of target cluster in. You can use this output to wire the node to subsequent nodes.

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 merges a LIN schedule with all schedule entries to the target cluster. Frames referenced in the schedule entries should be merged before merging the LIN schedule; otherwise, the reference get lost.

If the source LIN schedule name was not used in the target cluster, this node copies the source LIN schedule with the entries to the target. If a LIN schedule with the same name exists in the target cluster, you can avoid name collisions by specifying the prefix to be added to the name.

If a LIN schedule with the same name exists in the target cluster, the merge behavior depends on the copy mode input:

  • Copy using source: The target LIN schedule with entries is removed from the target cluster and replaced by the source objects.
  • Copy using destination: The source LIN schedule is ignored (the target cluster schedule with entries remains unchanged).
  • Merge using source: This adds schedule entries from the source schedule at the end of the destination schedule table. The copied entries become new names, so all entry names in the schedule are unique. The source schedule properties replace the target schedule properties (comment, priority, run mode).
  • Merge using destination: This adds schedule entries from the source schedule at the end of the destination schedule table. The copied entries become new names, so all entry names in the schedule are unique. The target schedule properties (comment, priority, run mode) remain unchanged.

Example

Target LIN schedule LS1(v1) has entries e1, e2. Source LIN schedule LS1(v2) has entries e3, e4.

(v1) and (v2) are two versions of one object with same name but with different properties.

  • Result of Copy using source: LS1(v1), e1, e2.
  • Result of Copy using destination: LS1(v2), e3, e4.
  • Result of Merge using source: LS1(v2),e1, e2, e3, e4.
  • Result of Merge using destination: LS1(v1), e1, e2, e3, e4.

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