Clarification Please- Creating a deployment system

[SimpleJack]

Hi all,

So I have created multiple applications in the past using the Labview app builder with no issues. This is the first time I am attempting to create a TestStand installer and I having a tough time with it.

First of all, I have a deployment license for the machine I am attempting to install it to and I am running the latest versions for TS and LV. I also modified the simple user labview interface to what I need and am using that as the user interface.

So I have a couple questions and I have trolled the discussion boards and read the NI documents. Either I haven't found my answers or my skull is too thick.

First of all, relative paths or static paths? Which do I use when developing a sequence I am going to deploy. I have been specifying the paths, should  I use relative?

Second, I am tried to create an installer a couple times but I get the error it can't find the labview engine... I have checked the labview 2009 run-time engine. Do I also need to install the Teststand Engine? I guess if I do, then I don't have to manually install it first and enter the license, yada yada. Should my VI icons after the installation look like VI icons or the classic windows "i don't know what you are" icon? After I install it doesn't recognize the VI icon.

Finally, in the TSW file I created, do I need to add the TestExec.exe file to it (that is my user interface). Because if I don't, I don't see oit created.

I hope this makes sense.....please clarify if you can.

Thanks,

Ryan

[tom.drake]

Hi Ryan,

---

SimpleJack wrote: 

First of all, relative paths or static paths? Which do I use when developing a sequence I am going to deploy. I have been specifying the paths, should  I use relative?

 

---

The TestStand Reference Manual (4.2) states the following on page 14-6, in the section "Guidelines for Successful Deployment":

Use relative paths and search paths so TestStand can find files even when you install the files in a location on the target computer that is different than the location of the files on the development computer. Refer to the Configuring Search Paths for Deployment section of Chapter 5, Module Adapters, for more information about configuring estStand search directories for deployment.

The "Configuring Search Paths for Deployment" section on page 5-3 states the following:

When you want to configure search directories for deploying a TestStand system, you can manually add additional search paths to the list of default search paths on the target computer. The TestStand Deployment Utility does not copy additional search paths because the new directories might not exist on the target computer.

National Instruments recommends installing the <TestStand Application Data>\Cfg\TestExec.ini file with the deployment for that system because TestStand stores the search directories in TestExec.ini. You can use the Force File to Install option on the Distributed Files Tab of the TestStand Deployment Utility to overwrite existing files.

Does that help you at all with your first question?

[SimpleJack]

Yes it does. Thank you. Hmmm....is there any easy way to switch back to relative paths? My VI is now called by Teststand in the specified path under step settings. I'm not sure how to switch that back for one VI and more importantly, for all VI's.

Thanks,

Ryan