LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

subvi not able to find location

Also, in case you transfer a VI to a different machine you need to ensure that you include all subVIs.
For this you should select "Save As" >> "Duplicate hierarchy to new location"

If you are working on the same machine ignore this. Smiley Indifferent

 

0 Kudos
Message 11 of 13
(508 Views)
yes .Am developing the program in one system and running the program in another ssytem.I used to copy from this system to the other one. This problem happens in both the systems. Now I am trying to sort this problem by arranging all the subvi into a library. Am learning how to do so.
0 Kudos
Message 12 of 13
(494 Views)

xdaf wrote:

Other possible reason: In your PC there are 2 different sub-VIs with the same name, and when you open the main VI, the "wrong" one is already in memory.

I'm quite convinced you'll solve your problems just putting some order in your VI hierarchy.


Awesome.  In the dark old days when my team was trying to optimize code, we had several cases where the VIs were calling the same VI from different places.  It was madness to try to sort out all the heirarchy problems!  I believe this to be the problem also.  Kudos of course.

 

Bill

Bill
CLD
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.
Humble author of the CLAD Nugget.
0 Kudos
Message 13 of 13
(483 Views)