LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

2 save location's keep calling eachother

I have two labview projects saved on my computer. One is our code which we have as our base code which we are not going to be editing. The other is the one which we are changing and using for the competition this year. When I try and load one (as of right now they are the same code due to some other computer errors) it is asking me to determine where to call the global variables from. When I try and switch between the codes the global varibles are called from the perviously used file, even though they are different locations. Is this normal when two codes are saved on the same device and if not is there any way to fix it?

0 Kudos
Message 1 of 6
(2,717 Views)

Are you using project files?  If not, you really should.  They help a lot keeping your different projects separate.

 

Your problem is that your VIs from the different projects have the same.  It is very easy to get "cross linking" in this situation.  Setting up the project files will help a lot to alleviate this.


GCentral
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines
"Not that we are sufficient in ourselves to claim anything as coming from us, but our sufficiency is from God" - 2 Corinthians 3:5
0 Kudos
Message 2 of 6
(2,713 Views)

Do you open something from the second location while any of the VIs from the first location are still open?

0 Kudos
Message 3 of 6
(2,686 Views)

They are a two seprate .lvproj files. One is labeled 2012 and the other 2013. I close down labview entirely before opening either of the files so there should not be anything transfering over. Am I only able to have one set of global variables?

0 Kudos
Message 4 of 6
(2,678 Views)

Make sure your projects are pointing to the right dirctories and files.

 

You can't be using two files with the same name in a single project.


GCentral
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines
"Not that we are sufficient in ourselves to claim anything as coming from us, but our sufficiency is from God" - 2 Corinthians 3:5
0 Kudos
Message 5 of 6
(2,664 Views)

It is also helpful to use libraries (lvlib NOT llb). Within the project, create a library for the VIs that are specific to that particular project, and only include in the project the library that is holding its VIs.

 

Once you have done this, you can look in the Dependencies and find where the wrong library is being called. In addition, once you have everything sorted out, the libraries can help the problem from repeating because each library creates its own namespace.

 

Mike...


Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion

"... after all, He's not a tame lion..."

For help with grief and grieving.
0 Kudos
Message 6 of 6
(2,660 Views)