After you have created your TestStand sequences, it is best to use TestStand Deployment Utility. The tool is quite simply to use as the Deploying TestStand Systems KnowledgeBase and Chapter 14 of the TestStand Reference Manual give you lots of assistance on using this utility. Chapter 14 gives you step by step instructions and information on properly deploying.
Overall, the steps that are mentioned in those documents are:
1) Create a TestStand workspace (File » New Workspace File).
2) Create a new TestStand project and add it to the workspace (right-click your workspace file and select Insert New Project into Workspace).
3) Add your TestStand sequence files.
4) Right-click on your workspace and select Insert Code Modules. This step will grab all your code modules (LabVIEW VIs) and add them to your workspace.
5) Launch the TestStand Deployment Utility (Tools » Deploy TestStand System)
You don't have to create any LLBs before using this utility. Just add your sequences, insert your code modules and then go through each tab in the deployment utility and you should be good to go.
Let us know if you have any more questions.
TO; Johnathan N
When I tried to "Insert Code Modules" I got an hour glass for about 10 to 15 seconds and a message which said "no code modules were inserted". I tried several times. Sometimes the message comes up immediately sometimes delayed as stated. The vi's are in the same directory as the seq file (which inserted OK) or directories under that directory. They are all .llb's (they were this way from the beginning). All vi's entered with "specify module" were entered using a relative path in the seq file.
If your LabVIEW step's code module is a VI inside of a LLB, when you insert code modules inside of your workspace, it should find your VI and place it under the Code Modules folder in your workspace. However, it might have a red X next to your VI as it appears this is because its inside of an LLB. I tested this out myself and I did see the red X. However, when you open the deployment utility and analyze your workspace (Distributed Files tab), it correctly finds the VIs in the LLB. I would check and make sure that your VIs are found in this tab as this is the true indicator if TestStand can find your files.
Also, you can right-click on your workspace file and select Insert Code Modules which will insert all the modules for all the sequence files you have included in your workspace.
Hope this helps!
I get no red X's , no vi's, absolutely nothing, just the message I indicated in the previous post.
The only thing I can think of is that I have installed TS ver 3.5 evaluation and LV8.2 Eval and am using the code from TS3.1 and LV7.1
OK, The workspace file window has three panes, upper left, upper right and lower. If you right click in the upper right (file and SC Status) you get the option to "insert code modules". This is where it does not work. You get the same option in the upper left pane (tree view) which does work.
Another situation popped up during this effort. Attached is a very simple sequence file (TS 3.5) and a LV 8.2 vi which should be placed in C:\TEMP Run the sequence with the input to the vi checked as default ("c:\test.txt"). Then run it with default unchecked. Then put any letter but "T" or "t" as the first charactor in the file name and run it again both default checked and un-checked. Run the TS sequence by selecting the only step and then "run selected steps."
Message Edited by Jonathan N on 01-30-2007 08:57 AM