How can I get TestStand to use a custom labview.ini when it calls a VI.

[brick]

Hi All,

How can I get TestStand to use a custom labview.ini when it calls a VI.

I am executing a seq that calls labview VIs. By Configuring the Test Stand Search Directories the top level VIs are found but the sub VIs cannot be found.  If executing the top level VI from Labview I can point Labview to a custom labview.ini and all is well.

Thx

[Adri_K.]

Hi,

How have you configured the TestStand search directories to locate the top level VI? Are you indicating this path an absolute or relative? Also, could you please indicate what versions of TestStand and LabVIEW you are using.

Regards,

Adri K

[brick123]

Using Labview 7.1.1 with TestStand 3.1

The search directory spec in TestExec.ini is set to the root directory of all of the support VIs.

 [Config.SearchDirectories[9]]
SearchSubDirs = True
Path = "D:\\Base Support Files"

In order for Labview to locate the correct subVIs it's search directory spec in labview.ini is also:

viSearchPath="<topvi>:\*;D:\Base Support Files\*;<vilib>:\*;<userlib>:\*;<instrlib>:\*"

These two .ini files are controlled files and we would like to invoke teststand and labview pointing to these files in the CM repository.

We have a work around for Labview by simply starting labview before TestStand using:

D:\Applications\LabVIEW 7.1\LabVIEW.exe   -pref    Z:\verification\labview.ini

Would like to know if it is possible to execute:

D:\Applications\TestStand 3.1\OperatorInterfaces\User\LabVIEW\TestExec.exe    using the controlled file  Z:\verification\TestExec.ini

and have TestStand open LabView using its controlled file Z:\verification\labview.ini

Thx,

Paul

[RayFarmer]

Hi,

The LabVIEW ini file has to be in the same location as LabVIEW.EXE. If its not then LabVIEW will just create an new file which will contain the default settings.

Likewise the TestStand LabVIEW UI has a similiar ini file as LabVIEW which again has to be in the same folder as the exe.

If you need the search path to be the same as labVIEW just add the visearchDir setting in the Testexec.ini found in D:\Applications\TestStand 3.1\OperatorInterfaces\User\LabVIEW\TestExec.exe 

By the way this testexec.ini is not the same ini file as the TestStand testexec.ini found in the cfg folder. This is the one Teststand will use.

The one found in \User\LabVIEW is the one the labVIEW TestStand UI will use.

What is the setting of your LabVIEW adaptor using, is it still the LabVIEW development, RTE or the RuntimeActiveX Server? 

regards

Ray Farmer

[Adri_K.]

Hi,

Ray is correct that the .ini file must reside in the same folder at the .exe. It is important to mention that these two files must also have the same name. For example, if your executable is named TestExec.exe, your initialization file should be named TestExec.ini.

Regards,
-Adri

[brick123]

Well, I know that if I execute LabView alone I can specify whatever ini file I like such as:

"D:\Applications\LabVIEW 7.1\LabVIEW.exe" -pref Z:\RIUSigp\verification\labview.ini

What I understand from this discussion is that TestStand cannot do this when I run the LabView TestStand UI such as:

"D:\Applications\TestStand 3.1\OperatorInterfaces\User\LabVIEW\TestExec.exe"

 

You say the TestExec.ini must be in the same folder as the .exe but when I execute TestExec from that folder the ini file used is:

"D:\Applications\TestStand 3.1\Cfg\TestExec.ini"

So, is the bottom line that I cannot execute TestExec from ....\User\LabVIEW\  and use anything other than the  .ini files (LabVIEW and TestExec) located in the default locations?

Paul

[RayFarmer]

Paul,

[So, is the bottom line that I cannot execute TestExec from ....\User\LabVIEW\  and use anything other than the  .ini files (LabVIEW and TestExec) located in the default locations?]

That is correct

[You say the TestExec.ini must be in the same folder as the .exe but when I execute TestExec from that folder the ini file used is:

"D:\Applications\TestStand 3.1\Cfg\TestExec.ini"]

You are missing the point here, this ini file is not the same ini file that is located in ..\User\LabVIEW\...

Regards

Ray Farmer

[brick123]

Ray,

[You are missing the point here, this ini file is not the same ini file that is located in ..\User\LabVIEW\...]

Does this mean  ...\User\LabVIEW\TestExec.exe     loads multiple TestExec.ini files?

Would

\TestStand 3.1\OperatorInterfaces\User\LabVIEW\TestExec.exe

LOAD

\TestStand 3.1\Cfg\TestExec.ini

AND

\TestStand 3.1\OperatorInterfaces\User\LabVIEW\TestExec.ini   ?

Just for my own understanding.

In any case, I have a solution that will give us the controlled environment we need.

Thanks to the group.

You're been very patient.

Paul