Hedehodo,
@hedehodo wrote:
Hi,
I need to call a VI develop to use NI 6001 DAQ module. The VI was developed in Labview 2015. I compiled it in LV 2014. I installed latest DAQMx, 2014RTE, 2014RTE SP1 on target computer. When i try to call the VI, Teststand tries to search for some other VI's in Teststand's sub folders?
Can anyone tell me some rule of thumbs to call VI's from Teststand?
Both TestStand and LabVIEW use relative paths and search directories to locate files. From your description, it sounds like you have a VI being located by a relative path, but do not have the parent directory listed in TestStand's Search Directories. There are a number of Search Directories included by default which cover TestStand's primary directories.
Each project has its own requirements and best practices, but as a rule of thumb I suggest having a single LabVIEW project directory, which I would place in the Sequence File directory, so all of your LabVIEW code modules share a parent directory. That way you only need to add a single path to the TestStand Search Directories.
LabVIEW has its own search paths which include common locations such as <vi.lib> and <instr.lib>. When LabVIEW loads the code module, it will search for the dependencies in these locations.
Steven Gloor
Staff Customer Engineer - CTA, CLD
