Adds the source schedule 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 LIN schedule is merged.

  • cgenclassrntag.png source LIN schedule —

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

  • cu32.png copy mode —

    copy mode defines the merging behavior if the target cluster already contains a LIN schedule with the same name.

  • cstr.png prefix —

    prefix is added to the source LIN schedule name if a LIN schedule 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 LIN schedule 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 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.

    Description

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