Wire Class Conflict and Broken Wires in LabVIEW

Updated Jun 25, 2020

Reported In

Software

  • LabVIEW

Issue Details

  1. I have a working project. I copied some of the VIs for a second project. Now I am seeing broken resource wires that say "Wire Class Conflict."
  2. I have a Type Definition Control (ctl) with some controls (clusters, arrays, strings, etc.) and refnum controls for each of them. I am using this ctl in my main code and everything is working fine. Now, I am trying to add some elements to one of my clusters inside the ctl. However, after saving and applying changes inside the ctl, my main code has some broken wires.

Solution

  1. A wire class conflict error indicates that you have connected a wire of one resource type to another. You can try resolving this issue by deleting and recreating the wires and references to ensure that the properties are the same.
  2. When using type definitions is important to match data types and references. If you have references inside a type definition pointing to the controls in there, you should update them every time that you update any of the controls. For example, if you need to add one more element to a cluster, and if you have a refnum control for that cluster, then you will need to update the refnum control too.

You can find more information about this on the class conflict help page.