LabVIEW VI Compiled Information Storage Path

[PalanivelThiruvenkadam]

Hello All,

I am Using LabVIEW Modules in TestStand in Run Time Environment by compiling the Developed VI's, but every time when the New User is Logged in the same System again the Compilation of LabVIEW Modules is required.

Finally its Found that the information is stored in LabVIEW Data in Documents Folder.

So Every time the New user is logged in  the LabVIEW Data Folder needs to be replaced  in the respective user Documents.

Is there anyway i can bypass this process.

[dkfire]

What is a LabVIEW module to you? 

Normally a vi, hope that is your module, is the compiled code, and as long a is can load all its components, sub-vi and controls, it can be run with the Run-Time Engine. 

So where are you storing the vi compared to your TestStand sequence? 

You should store the vi's under C:\Users\Public\Documents\National Instruments\TestStand XXXX\Components\StepTypes

To work in Run-Time, the vi should be saved using the development version in that location also. 

[PalanivelThiruvenkadam]

LabVIEW Modules  are my VI's and Its Stored in C Driver  and its called in TestStand  as a Modules, where my Module adapter is set to LaBVIEW RunTime Engine, so to make my LabVIEW Code to Work in RunTime i am doing a MassCompile of Developed VI's

When the New user is accessing the same machine again LabVIEW Module needs to be compiled.

[dkfire]

So are the vi looking for something the LabVIEW Data folder? 

where on the c-drive is you vi's located?

[PalanivelThiruvenkadam]

When the New user is logged the VI's in the C driver remains as non Compiled Files, only when i replace the LabVIEW data (From the user where its being compiled earlier) Folder in Documents my VI's Work properly in Runtime Engine

which means the compiled info data is getting stored in LabVIEW Data under Documents.

[dkfire]

I think you have a dependency to something in the LabVIEW Data folder. 

There is no compile information stored in that folder. Else I would have a hard time making programs for my customer. I never take the LabVIEW data folder to my customers. 

If a .vi can't run in TestStand, most of the time it is because of missing sub-vi's or a path has changed. 

Please make sure that you do not have any dependencies in that folder, and that you store the vi's in the recommended folder for TestStand. 

[PalanivelThiruvenkadam]

Works fine in Development Environment / After compilation Even in Run Time Engine

[dkfire]

Again, it is all about dependencies. 

If you have development version installed, you have all the vi's (function) available in vi.llb. 

Even if you ask TestStand to run the vi's in Run-time engine, all the functions are still pressent in the system and for the current users document folder. 

You have to be very very sure about your dependencies.

[zVisior81]

Hi,

I'm sorry for opening this old thread, but have you found any solution o this problem?

I have the same issue. System is running Teststand Base Deployment Engine / Labview Runtime licenses. It's not working once you create new Windows user because some compiled Labview files are stored in %user%\Documents\Labview Data folder. And this folder is created only when you run VIs for the first time in Development / Debug Deployment licenses.

Now for each new user I need to copy these folders or switch license, run once with full license and go back to runtime.

Can I point in Labview/Teststand to store these files in public documents or some other folder instead of %user%?

[zVisior81]

Have found something in LV options. Maybe this is the option to change. I'll reply once it's verified.