Adds the source ECU to the target cluster.


icon

Inputs/Outputs

  • cbool.png wait for complete? (T) —

    wait for complete? Use this input only if the source object is a cluster (refer to the XNET Database Merge (Cluster) VI).

  • cgenclassrntag.png target cluster in —

    target cluster in is the I/O name of the cluster where the source ECU is merged.

  • cgenclassrntag.png source ECU —

    source ECU is the I/O name of the ECU to be merged into the target cluster.

  • cu32.png copy mode —

    copy mode defines the merging behavior if the target cluster already contains an ECU with the same name.

  • cstr.png prefix —

    prefix is added to the source ECU name if an ECU with the same name exists in the target cluster.

  • cerrcodeclst.png error in (no error) —

    error in can accept error information wired from VIs previously called. Use this information to decide if any functionality should be bypassed in the event of errors from other VIs. Right-click the error in control on the front panel and select Explain Error or Explain Warning from the shortcut menu for more information about the error.

  • iu32.png percent complete —

    percent complete is used when wait for complete? is false. (This output does not apply to the ECU instance.)

  • igenclassrntag.png target cluster out —

    target cluster out is a copy of target cluster in. You can use this output to wire the VI to subsequent VIs.

  • ierrcodeclst.png error out —

    error out passes error or warning information out of a VI to be used by other VIs. Right-click the error out indicator on the front panel and select Explain Error or Explain Warning from the shortcut menu for more information about the error.

    • 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.

    Description

    This VI 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 VI 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).