LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Wrong vi version being used

Solved!
Go to solution

Friday I edited a VI by opening it from "My Computer" and made a mistake in the edit. This VI has a combo dropdown and I was editing the items in that combo box. The next time I edited the VI(today) I opened it from its lvlib file. Now when I run TestStand it finds the flawed version and uses it. I can find no other copies of the vi on the disk with a recent date. Where is TS finding this corrupt VI? Is the combo box stored separately from the VI?

 

Thanks,

 

jvh 

0 Kudos
Message 1 of 3
(2,443 Views)

Hi jvh,

 

Usually everything in the front panel or BD of the VI is stored in the VI. When you launch TestStand and you edit the VI throughTestStand, check the VI properties and observe if the path is different from the path you're expecting the VI to be pulled out from. If it is different, I guess you've found the problem. 🙂

 Hope it helps.

 

Message 2 of 3
(2,407 Views)
Solution
Accepted by topic author jvh75021

NItinD, thanks for the post. The problem was found between my ears. I need to learn more about combo boxes.

 

On the Edit Items tab, there are Items/Values pairs, or I thought they were paired. Turns out the items were loaded via a property node and when the load order was changed, the values stayed where they were. I initially thought the values were set in the combo box as they were there when the VI was opened for editing and TS had not been started.

 

jvh  

0 Kudos
Message 3 of 3
(2,382 Views)