LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

User vi path


@RHutchings wrote:
OK I created a project and all of the dependencies are listed. Where are the files located now and how can I change it?

The files locations don't change. If you go to "Files" view in your project it will show the location of files. You should put your project VIs in the project, not in dependencies (other than standard files such as vi.lib). Just drag them from dependencies into the project. 

0 Kudos
Message 11 of 23
(800 Views)
I did that and now they are on my PC instead of the project location.
0 Kudos
Message 12 of 23
(812 Views)

Capture.JPG

0 Kudos
Message 13 of 23
(812 Views)

@RHutchings wrote:
I did that and now they are on my PC instead of the project location.

No, that did NOT move the files. If you choose that "Files" tab it shows you where they're located.

 

Also, if you're using almost identical files I would not use the exact same name for the file - use some notation to show which VI calls it. I NEVER have vi's with the same name but different functionality unless they're in separate related classes (which gives them different names in a LabVIEW context since the class name is part of the name). Using libraries as others have said will also give the files different names from a LabVIEW context.

0 Kudos
Message 14 of 23
(807 Views)
I'm getting nowhere.
0 Kudos
Message 15 of 23
(801 Views)

@RHutchings wrote:
I'm getting nowhere.

Are you sure you want to link to a network folder location for your vi's? That just seems like such a bad idea.

This always blows up in my face, but here we go anyway....

 

Steps to "link" to the new location:

1) exit LV

2) Go to "old" folder location and rename the folder (add a couple XX to the end)

3) open just LV (not a file, not a project)

4) navigate to the LV options and ADD a temporary search path to the "new" folder location.

5) Open your top level VI

6) Resolve any missing file in your code.

7) Save and close your vis (I recommend even exiting LV at this point)

8 ) UNDO Temporary search directory.

9) UNDO "old" folder rename.

 

Good luck 💣

 

---------------------------------------------
Former Certified LabVIEW Developer (CLD)
Message 16 of 23
(790 Views)

@Frozen wrote:

@RHutchings wrote:
I'm getting nowhere.

Are you sure you want to link to a network folder location for your vi's? That just seems like such a bad idea.

This always blows up in my face, but here we go anyway....

 

Steps to "link" to the new location:

1) exit LV

2) Go to "old" folder location and rename the folder (add a couple XX to the end)

3) open just LV (not a file, not a project)

4) navigate to the LV options and ADD a temporary search path to the "new" folder location.

5) Open your top level VI

6) Resolve any missing file in your code.

7) Save and close your vis (I recommend even exiting LV at this point)

8 ) UNDO Temporary search directory.

9) UNDO "old" folder rename.

 

Good luck 💣

 


BTW, when you say "sharing many user vi's...", I hope you don't mean the files in "C:\Program Files (x86)\National Instruments\LabVIEW 20XX\user.lib"

---------------------------------------------
Former Certified LabVIEW Developer (CLD)
0 Kudos
Message 17 of 23
(778 Views)

@RHutchings wrote:

Capture.JPG


No, they are not! They are targeted to run on MyComputer (as opposed to some Remote, RT or FPGA TARGET)

 

To see where they live on disc either A) switch to the files view (see the Items and Files tabs?) Or B) Show full paths of project items from the View menu (or is it under Project? I can't recall) and a vertical splitter will show in the items view with the full path of each item.

 

It is also helpful to create virtual folders to help organize your sub vis in the items view.  Just rigtclick ot the target or an existing virtual folder and create new virtual folder.

 

Typically my project might look like this

MyProject.lvproj

>Target MyComputer 

+>Main.vi

+>Hardware Drivers

+>>dev0

++>>dev0subvi1...n

+>>dev1

+>>User Interface

++>>UIsubvi1....n

+>Unit Tests

>Target cRIO0(CHASSIS FUNCTION)

....

 


"Should be" isn't "Is" -Jay
0 Kudos
Message 18 of 23
(765 Views)
No, I don't mean the files in "C:\Program Files (x86)\National Instruments\LabVIEW 20XX\user.lib" I'm talking about vi's that I have created and stored on the network drive.
0 Kudos
Message 19 of 23
(751 Views)

@RHutchings wrote:
No, I don't mean the files in "C:\Program Files (x86)\National Instruments\LabVIEW 20XX\user.lib" I'm talking about vi's that I have created and stored on the network drive.

Not to beat you up too much but, if that network location was really a Source Code Control Repository,  ..... you would be much better off!

 

However,  let's get that project together first. 


"Should be" isn't "Is" -Jay
0 Kudos
Message 20 of 23
(749 Views)