NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

Specifying VI modules in instr.lib on 64 bit Windows 7

I am looking for some suggestions as to how best to handle a situation I am having with specifying a VI module step that is in the instr.lib directory of LabVIEW.  I am developing from two different machines depending on the company facility that I am at.  One computer is a Windows 7 64bit machine the other is 32 bit.  The situation is that the location of the instr.lib is not the same between a 64 bit and a 32 bit windows 7 computer (the 64 bit installs NI software in the "program file (x86)").  This causes all of the paths for my modules on one computer to not be found on the other.

Anyone else run into this issue and have a solution?

 

0 Kudos
Message 1 of 2
(2,812 Views)

I think I have solved my own issue...

 

Here is what I do.  Specify the module to be absolute to start and then change the path to be relitve by removing the "C:\Program Files (x86)\National Instruments" and replacing it with ".." resutling in a path similar to "..\LabVIEW 2010\instr.lib\<driver>\<filename>" .  Since the TestStand directory is already in the search paths it will find the file on either machine as long as it is installed.

0 Kudos
Message 2 of 2
(2,811 Views)