Table Of Contents

XNET Database Merge (XNET Database Merge (PDU)) (G Dataflow)

Version:
    Last Modified: February 22, 2017

    Merges a PDU 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 PDU

    The I/O name of the PDU 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.

    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.

    Description

    This node merges a PDU with all dependent child objects (subframes and signals) to the target cluster.

    If the source PDU name was not used in the target cluster, this node copies the source PDU with the child objects to the target. If a PDU 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 PDU with the same name exists in the target cluster, the merge behavior depends on the copy mode input:

    • Copy using source: The target PDU with all dependent child objects is removed from the target cluster and replaced by the source objects.
    • Copy using destination: The source PDU is ignored (the target cluster PDU with child objects remains unchanged).
    • Merge using source: This adds child objects from the source PDU to child objects from the destination PDU. If the target PDU contains a child object with the same name, it is replaced by the child object from the source PDU. The source PDU properties (for example, payload length) replace the target PDU properties.
    • Merge using destination: This adds child objects from the source PDU to child objects from the destination PDU. If the target PDU contains a child object with the same name, it remains unchanged. The target PDU properties remain unchanged (for example, payload length).

    Example

    Target PDU Pdu1(v1) has signals S1 and S2(v1). Source PDU Pdu1(v2) has signals S2(v2) and S3.

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

    • Result of Copy using source: Pdu1(v2), S2(v2), S3.
    • Result of Copy using destination: Pdu1(v1), S1, S2(v1).
    • Result of Merge using source: Pdu1(v2), S1, S2(v2), S3.
    • Result of Merge using destination: Pdu1(v1), S1, S2(v1), S3.

    Where This Node Can Run:

    Desktop OS: Windows

    FPGA: Supported


    Recently Viewed Topics