NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

deploy run time engine

Solved!
Go to solution

Hello everybody,

I am trying to deploy my teststand application to a target computer. My teststand application uses: TestStand 2014 (32 bits), LV 2014 SP1 (32 bits).

 

Following is the problem I encouter while using the deployment tool. 

1. While trying to include the LV RTE into my installer, the deployment utility is requesting that I provide LV 2015 installer. See the attached picture.

I wonder why it is asking for LV 2015-64bit installer median. If I ignore the request, the build process failed.

 

Deployment1.png

 

2. I am using shared variable to communicate with the compactRIO controller. The compactRIO controller is the SVE host. My question are,

       a. Do I need to 'deploy' my shared variable library, eventhough my system is not a SVE?

       b. I read in manual that I can deploy the shared variable libry through the LV utility deploy lilbrary step. So I added this step into the test sequence. Everytime I run the sequence, that step deploys the shared variables. On the target, I wonder if it is necessary to deploy the shared variable on every execution of the test sequence. I think it should only be deployed only once on the target system. Am I right? If so, how do I remove that LV utility deploy library step from the test sequence on the target, since there is no test stand development system on the target.

 

3. I am using a database to save the test results after each test sequence execution. I can export the database table schema and copy over to the target computer. My question is, how do I import the database table schema into the target, since there is no teststand development system on it (no way to call up the Configure->Result Processing->Database to import the table schema)?

 

I hope the teststand experts out there can provide me some helping hints to help me understand the whole deployment process. Thank you.

 

Yours,

lhuckj

 

 

 

 

0 Kudos
Message 1 of 3
(4,409 Views)
Solution
Accepted by topic author hlim

1) Make sure LabVIEW 2015 Run time is NOT slected from Installer options -> Drivers and Components

 

 

2) I don't know

 

3.  

I generally set my data link to a  UDL file and include that in my distribution .  I set the  coonection string to use a relative path to this udl and make sure the UDL is copied to the same location on the targer

 

I also include in my CFg TestStand Application Directory:

 

TestStandDatabaseSchemas.ini

TestExec.ini

Users.ini

StationGlobals.ini  (careful if you don't want to overwrite the existing one; i use it to store instrument addresses)

 

0 Kudos
Message 2 of 3
(4,395 Views)
Solution
Accepted by topic author hlim

Hello NIExpert, thanks for the hints.

I have not included the LV 2015 Run Time. But I noticed that as soon as I included the 2015 Test Stand run time, it immediately requested LV 2015 Run Time Installer.

 

Thanks for the tips on the .ini files you included in your deployment.

 

Yours,

hlim

0 Kudos
Message 3 of 3
(4,377 Views)