Correcting Bad Wiring

[anemali]

Hello, I am currently trying to fix a VI that was given to me but I am very inexperienced when it comes to Labview and programming in general and I have encountered an error when I was uploading SubVI's into the program. The wiring the is incorrect because the the terminals are different types, but I do not know how to fix it. I am working with Labview 2012 because of the .NET configuration. I Attached a picture of the error below.

[Bob_Schor]

I'm not sure how you expect us to find a bad wire in that tiny picture.  Please, if you want us to look at a Block Diagram of a VI, attach the VI!  That lets us see it at "normal" magnification, scroll around, even have LabVIEW locate the errors for us in case we can't find them.

You mention sub-VIs.  You should also submit the subVI (as a VI!) that won't connect.  If you have a lot of VIs and subVIs, especially if they are part of a LabVIEW Project (with an associated Project, .lvproj, File), and if (as is usually the case) the VIs and Project File are all in a single folder, compress the folder and attach the resulting .zip file.  This gives us "all the pieces" and we'll be much better able to help you.

Bob Schor

[LV_Pro]

Ok, not sure what the unnamed vi with the default LabVIEW icon is supposed to do, but its output is a string, which is wired, incorrectly to a VI property node's reference input. When you say you were uploading vi's what do you mean? The unnamed vi is obviously not the correct one, not sure what should be there instead though.

[lh845 · Accepted solution]

My guess is that you are trying to open a SubVI by using a property node.  You will need to create a reference to the VI that you are trying to open and replace the "SubVI" with the VI reference.  Sorry, I don't have LabVIEW right now, so I can't help much more than that.

[altenbach]

You cannot just randomly connect functions until there are no wiring errors and expect the code to make sense. Wiring a string output to a reference input definitely makes no sense. You can get rid of the wiring error if you simply remove the wire (unless the terminal is marked as required), but that won't solve your real problem.

There are several instances of a subVI with a "1" in the lower right corner, but there is no guarantee that they are the same. Most likely they aren't (some have strings as outputs and inputs, some DBL numeric scalars).

This is definitely not something for an inexperienced programmer. Why were you "uploading" (sic) this VI to the caller block diagram in the first place? What was the primary reason to do so and what did you expect as a result?

What does LabVIEW 2012 have to do with .NET configuration?

Who wrote the original code?

[anemali]

Thanks alot It was not the exact solution but it led me in the right direction i just made the VI a static reference

[billko]

---

@anemali wrote:

Thanks alot It was not the exact solution but it led me in the right direction i just made the VI a static reference

---

What precipitated this?  This is a BIG change.  Are you sure the code will work now?

[anemali]

it seems to be working. I am getting readouts from the equipment and they seem to be correct there are some issues with the graph when it is displaying the data but that seems fixable. The VI's purpose is to collect data from the Lakeshore, load cells, and other equipment in the lab and it seems to be doing that. I am not an expert with LabView though and I did not make this vi. Its been worked on by several people over the years and i just arrived recently and I am just trying to get it up an running again.