My TestStand / LabVIEW project is done and ready to be released.... Need help please

[JD99]

I have finished my TestStand structure and have completed all of my LabVIEW vi's.  What is the proper way to release this?  I am ready to put this on a test system for production use.  I plan to use the "simple labview" user interface that comes with TestStand.  I may change that later, but thats another day. 

-Do i need to compile all of my VI's together into a LLB or a executable? 

-Anythign special need to be done with my SEQ file?

-Do I just leave everythign as is?

I have DevSuite Professional version, so i know i have the ability to create labview executables, but I wasnt sure what the proper way was, since i am using teststand.

Thanks for the help,

Jason

[daijoubu]

Have you tried the TestStand deployment utility?  It's capable of handling all the VIs and the sequence files.

Why do you want to make an exe out of the VIs?

[Tonythetiger]

Hi JD

If you going with a stand alone verison...using Teststand Deployment engine and Labview runtime enginer, there a few things you need to go through first.

You should make all your steps  dynamical loading.

Check all you VI's to see they contents in them is supported by the run time engine.   There are items in labview development that is not supported by run time enginee.

Look to see where all your VI's are pointing to (there location)   if any of the components are pointing to  where you labview install is   especially VI.lib folder you need to move those compents to another folder and relink them in you program.   Those files need to be included in your installer program  items like timers, merge errors...so on.

You will need to create a TSW  and  a TSD   in teststand..... where you folders are  and where they will be installed.      Possible need look into a bootstrap loader if you going make a cd install.

O yes you going need make a file(text, ini)  that has your report file options in it that is loaded when program runs.

I'm new to this also  that all i know so far.

[daijoubu]

JD:

When you started your TestStand project did you start with a TestStand Workspace or just jumped into the sequence editor?  A workspace file would hold your TestStand Project file.  The TestStand project file will contain all your sequence files and code modules (.c, .vi, .dll).   If you have gone this route, the TestStand Deployment Utility can handle deploying all your files.  It will place them exactly where it found them on your development system (unless you tell it otherwise), install the TestStand deployment engine, LabVIEW run time engine and will create the bootstrap installer for you as well.  I really recommend you look at Ch 14 of the TestStand Reference Manual.

[JD99]

Thanks for the replys.

When I started, I just created a sequence file.  I did not create a workspace.  I have a sequence file that calls many VI's and also calls one other sequence file that contains another VI. 

I will look more into this and also read the chapter you requested. 

Can i easy create a workspace after i have already created my sequence, or is it too late? 

In the end, my goal is to have deployed package that can run on the testers in production and will not spawn open labview and take away one of my development licenses while the tester is running.  Thanks again

Jason

[AllenP]

It is very easy to create a workspace with a single project with a single sequence included.  The deployment utility will include all of the VIs used, and repackage them so that they can be used by the Run-Time Engine.  To create a workspace, select File >> New Workspace.  You will need to create a Project inside of your workspace, and you can insert your sequence file or any other support files needed.

Hope this helps!

Allen P.

NI

[Tonythetiger]

hi JD,

Creating a Workplace can be  done at anytime.  Modifying it also  is very easy.

Go to file...then  you have option...New sequence   or New work place.

CHoose the workplace, then you have an kinda like a blank screen,   You add files to it.

The TSW tells the deployment file  TSD  where all the files you want you use are on your HD.

The TSD is  where you choose where you want the files to be installed to with the teststand installer.

Hm  with your goal........ the Deployment verison of Teststand  has needs it's own license to run the deployment teststand runtime.  It's not a free ride like the labview runtime engine.

[JD99]

OK.. Thanks guys.  I will look further into that before I ask any more questions since it may be self explainatory....

Thanks,

Jason

[trout00]

JD,
Did you deploy the program?

I am in the same situation,  jump into creating sequence files and VI files,
now I need to go back to create deployment

any tips ,  experiences....  encouragement

[RayFarmer]

Hi,

One tip is to make sure all your VI's and the teststand related VI's are all at the same version of labview.  Therefore, if didn't mass compile when you installed TestStand, or you have installed a later version of LabVIEW after your TestStand installation then mass compile before you start the deployment process.

Regards

Ray Farmer