Table Of Contents

XNET Database Merge (XNET Database Merge (ECU)) (G Dataflow)

Version:
    Last Modified: February 22, 2017

    Merges an ECU object with Tx/Rx frames 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 ECU

    The I/O name of the ECU 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 an ECU with all Tx/Rx frames to the target cluster. It does not merge the frames itself, but only the transmitting or receiving information. This happens based on frame names. If the source cluster defines new frames not contained in the destination cluster, they should be merged before merging the ECU; otherwise, the Tx/Rx information is removed.

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

    • Copy using source: The target ECU with all Tx/Rx information is removed from the target cluster and replaced by the source objects.
    • Copy using destination: The source ECU is ignored (the target cluster ECU with child objects remains unchanged).
    • Merge using source: This adds Tx/Rx frames from the source ECU to Tx/Rx from the destination ECU. The source ECU properties (for example, comment) replace the target ECU properties.
    • Merge using destination: This adds Tx/Rx frames from the source ECU to Tx/Rx from the destination ECU. The target ECU properties remain unchanged (for example, comment).

    Example

    Target ECU Ecu1(v1) has Tx frames F1 and F2. Source ECU Ecu1(v2) has Tx frames F2 and F3.

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

    • Result of Copy using source: Ecu1(v2), F2, F3.
    • Result of Copy using destination: Ecu1(v1), F1, F2.
    • Result of Merge using source: Ecu1(v2), F1, F2, F3.
    • Result of Merge using destination: Ecu1(v1), F1, F2, F3.

    Where This Node Can Run:

    Desktop OS: Windows

    FPGA: Supported


    Recently Viewed Topics