How to resolve Labview load conflicts

Question

I am developing a data collection program in Labview, which uses several stages of translation, cameras, high-speed digitizer and other equipment. I am developing an application on one computer and will deploy it on another computer. The development computer has a 2013 lab, and the computer on which the application will be deployed currently has Labview 2012, but we will upgrade it to Labview 2013 when we move the application there. Some of the drivers need different versions of the driver to work in Labview 2012 than for Labview 2013. I'm trying to save all vi, subvi and toolkit drivers in one directory tree so that I can move the whole tree to the computer on which it will be deployed.

When I load a project in Labview, I get a lot of "Allow load loading" dialog boxes. When I come to the study, Labview says that it cannot find one of the files causing the conflict, but still it appears in the dialog box. The following is an example:

This happens every time I load this project - saving all does not introduce new paths in Labview. I also tried to create a new project and pull for it, but the new project has the same load conflicts.

Obviously, Labview or these vis believe that these vi, which no longer exist, still exist.

How do I fix my project, vi or Labview, so that it uses only vi and it doesn't get all these conflicts, many of which have non-existent files?

Answer 1

I had the same problem, but she solved it like this:

In the project window, expand the Dependencies group. You should see each of the unwanted subwines listed there.
Right-click on each of them and select "Replace the item found in the project ...". This will bring up the familiar conflict resolution dialog box, go and select the correct path and click OK.
Now, as the dependency has changed, Labview is about to change the dependency path that is stored in the calling VI. You will see a save dialog box asking if you want to save the changes to the VI (s) that / cause the dependency whose path you just changed. You want to save the changes. Do this for all the addictions, and you should be good to go.

Answer 2

I found that when you need to move driver files and libraries from the default NI locations, renaming the files prevents further confusion.

For example, if you have “instr.vi” that you need to move to a user folder, renaming the file “my_instr.vi” and linking to the renamed file prevent future conflicts.

Of course, initially this may require some work to rename all the files and then direct your calling VIs to use these recently renamed driver files, but after this initial time you shouldn't have any problems.

Answer 3

This doesn't seem to be a problem with posters, but if your problem is lvlib pointing to the instr.lib folder and not the new folder, do a bulk compilation to fix it.