Hello everyone,
I am new to Teststand and have been trying to deploy my Teststand applicatino to a target computer for the past 2 days and have a few questions regarding the process of deployment.
1. I developed my TestStand application on the D drive of my development computer. My target computer has only C drive. In this case, (note: TestExec.ini is also being deployed) I would always need to:
a) change the search path configuration on the target computer after the deployment, e.g., adding/changing all the relevant paths in the search configuration to start with C drive. or
b) I can also do some tricks, by setting the search configuration to C: in the development computer just for the sake of deployment. This way, the deployment on the target computer will have the right search path (and report files output directory because I specify a fix output report directory). Then I would have to change the search configuration back to D drive for continuing the development on the deveopment computer.
The question is, if I choose a) as deployment strategy, in order to add/change the search configuration on the target computer, I will need a development teststand license. If I download a development teststand (as evaluation) on the target computer, after the add/change of the search configuration on the target computer, I would turn off the development Teststand and switch the license to base deployment license on the target computer, this will do it, right?
2. Deploying network published shared variable is not so straight forward. My target computer will communicate with a compactRIO through shared variables. The compactRIO controller is the SVE. I added a 'Labview Utility LIbrary Deploy step' in a sequence step and deploy this sequence to the target computer. I ran this sequence in order to deploy the shared variables on the target computer. However, I got an error saying that the shared variable library cannot be deployed and asking to make sure that there is only shared variables in the library. I checked and can see that there are only shared variables in the lilbrary. What could be other possible reasons? Can anyone give me hints on this problem? Is there a tool that can scan this library and tell me if there is a 'hidden' vi in this library because I cannot see anything wrong with the library even with my thick glasses.
I am thinking of other shared variable deployment options, for example: a) maybe I should download an evaluation LabView deveopment system on the target and copy over the Labview Project and deploy the shared variable through the labview project. or b) I can create a vi that uses the shared variable and using labview build process to deploy the vi as exe. Check the appropriate 'deploy shared variable' option in the build process, run the exe in the target computer. This way I can deploy the shared variable. After the deployment, turn off the LabView deveopment evaluation license so that there is only LVRTE on the target computer.
Does the above a) and b) options make sense as shared variable deployment strategies?
At this point, I realize the TestStand deployment is a skill. There is no systematic deployment approach for TestStand. Do experts out there agree? I just need some inputs so that I am not on the wrong path. Thanks in advance for your feedback.
Yours,
hlim