How to unify or merge the variables from several TestStand platforms to one TestStand platform?

[James_Grey]

Ray's suggestion to programmatically create the globals you need is the most robust solution for sequence files that must deploy to different stations.

However, if you still want to manually create a globals file that has the union of the globals from several stations, you could probably copy the station globals from each station into the file globals of an empty sequence file, use the differ to merge these file globals into a single file, and then copy the merged variables back to the station globals on the machine were you build your deployment.

[Yuri_IL]

1. Thank you, i think that i choose that solution. It is easy to just a merge it. Where can i read the information about my question?

2. In the books that i got from my training i have only information about single deployment and not for multiple, where i can find

   information about multiple deployment to a single target station?

[AllenP]

I would not recommend you try to run multiple deployments on a single target machine (especially if you are using LabVIEW).  Instead, you may want to create a workspace with many projects.

Allen P.

NI

[Yuri_IL]

Hi, Allen

1. Why you do not recommend to run multiple deployments on a single target machine (and you are right i use LabVIEW)

     Which problem that multiple deployments can cause?

 2.  How i can create a workspace with many projects? Did you mean that i can unify/consolidate many of my projects to

      one global project and after that deploy it? 

      If you meant it, have you at LabVIEW/TestStand a special way to do? (i familiar only with TestStand Deployment Utility) 

Message Edited by Yuri_IL on 06-14-2006 01:35 AM

[AllenP]

Yuri,

1.  My main concerns are related to LabVIEW.  Whenever a deployment is made, VIs are packaged so that they can be executed without LabVIEW on the deployed machine.  Making multiple deployments often results in the same VI being placed (because of packaging) in different locations.  In this case, your VIs will not be executable, since LabVIEW cannot have two different VIs in memory with the same name.  There may be other issues, but this is one I have run into in the past.

2.  I am referring to TestStand workspaces, which are the basis for TestStand deployments.  Each TestStand workspace contains one or more projects.  You must have at least one project, but can add more.  Rather than making several workspaces, and trying to create one project for each, it is much cleaner to make one workspace and add the neccesary projects to it.  You can do this in the Workspace window by right-clicking and selecting "Insert New Project" or "Add Existing Project".

Allen P.

NI

[Yuri_IL]

Thank you, I will try it and after that i inform if i successed in it