Teststand deployment does not package TestStand VIs

[chasgl1]

I am trying to create a deployment package for a TestStand application that uses LabVIEW VIs.  I have the LabVIEW target directory set to LabviewVIs, the default.  But after it runs there is no such directory.  After a source code analysis the directories with the VIs is not listed in the tree.

Any ideas?

Thanks

[Russell_G.]

Hi chasgl1

Can you be a little more specific about where you are setting the LabVIEW target directory?  Are you setting this in the "Distributed Files" tab by selecting the "LabVIEW Options" button? 

When you say that "after it runs there is no such directory", do you mean after you build the deployment there is no such directory?  Or just after you select "Analyze Source Files"?  Are you creating an installer?

With a little more information we may be able to help you better.

Russell G.
NI Applications Engineering

[chasgl1]

Yes I am setting this in the "Distributed Files" tab by selecting the "LabVIEW Options" button?  After I build the deployment there is no such directory.  If I copy the installer to another machine and run it no such directory.  After I noticed that I went back and look at the Analyze source directory results and I notice the VI directories were not there. I figured that was probably significant.
THanks,

[Russell_G.]

chasgl1

The "LabVIEW VI Options" dialog box will only set the folder location of any subvi's that your code modules call.  For example, if the code modules that you are calling from TestStand do not have any subvi's, then this folder will not be created. 

However, if you're code modules do have subvi's than they should definitely be installed in the folder that you specify.  There is a ring control at the top of the "Distributed Files" tab.  If you select "View Destination", you should see the subvi folder (that you specified) listed in the tree control.  This directory structure should also be reflected in the Image folder that you create ("System Source" tab).  When you analyze your source files, are the code module VI's showing up anywhere in the tree view? 

What is the error you are getting after running your deployed system? 

Russell G.
NI Applications Engineering

[chasgl1]

I haven't tried running it yet because the VIs are not there.  The VI directories are not showing up in either source or destination (see attached). 

[Russell_G.]

chasgl1

Have you tried deploying a different TestStand Sequence that uses LabVIEW VI's?  I would suggest trying to deploy the Computer Motherboard Sequence Located at
C:\Program Files\National Instruments\TestStand 3.1\Examples\Demo\LabVIEW\Computer Motherboard Test\Computer Motherboard Test Sequence.seq

If you try to deploy this sequence as part of a workspace file, do the VI's still not show up?  Below is a screenshot of what the Tree View should look like with "View Source" selected after Analyzing the Source Files.

I assume you are using TestStand 3.1.  What version of LabVIEW are you using?

Russell G.
NI Applications Engineering

[chasgl1]

NO the example does not do it either.  Here is the result and the workspace I created to do it.  Maybe I'm creating workspaces wrong?

[chasgl1]

OOPs I just noticed the *s on the files and saved the workspace now it does include the VIs