08-24-2023 05:11 AM
Hello All
I have several TestStand codes for different products, I store each product's TestStand VIs in a separate folder. So when working on one product I don't change the other product's VIs. Or that's what I hope for.
Below are my different products in a separate folder:
Last week I worked on Proloc II_Full_Test_01_22_A_01.seq and got everything to work.
Today I worked on another product (NC_Relay). Then out of curiosity, I opened Proloc II_Full_Test_01_22_A_01.seq again to see if it still runs. Now there are VI's missing. It happened in the past as well. Every time I change to another product the other product gets messed up.
I don't understand why. Each product's VIs are in separate folders. The only common VIs are the OMICRON driver VIs (See below)
What can I be doing wrong, see the Error I get in TestStand. Below
08-24-2023 08:43 AM
This sounds rather like a file organization issue....
Are the VIs organize in an lvlib for each product? Do some product folders contain VIs with the same name?
08-24-2023 09:06 AM
Hello Oli
Not sure what lvlibs are, don't think I use it.
The VIs are duplicated in each product folder, so yes most VIs have duplicate names.
Marinus
08-24-2023 09:48 AM
I guess, what you are experiencing is an effect of the following: LabVIEW differentiates VIs by name. And it can only have one single VI with a given name loaded in memory at a time.
What could've happend is, that you had two instruments loaded at a time an referring to a VI in their respective folder but with the same name. Only one got loaded and one of the instruments got changed. Maybe there was a Save As dialog (which can also acta as a file move) and you accidentally removed one of the VIs.
You can circumvent issues like this by using lvlibs https://www.ni.com/docs/de-DE/bundle/labview/page/using-libraries-in-labview-projects.html
since they will create namespaces and allow you to load two files which would otherwise be conflicting.