Verify Labview Vis before starting execution in release mode

[Steve_Block]

   I have a TestStand sequence that calls a number of Vis. When I switch from development mode to the run-time engine, sometimes the TestStand sequence crashes at certain Vis. I then find that when I switch back to developement mode and open the vi, it has a start next to the filename, which indicates that the file needs to be saved. When I save the files, that step works fine in run-time mode, but then the sequence crashes on the next step that has this problem.

   How can I find out which files need to be resaved before running something with the run-time engine? Is there a way to precompile everything so this doesn't happen?

[StevieZ]

Steve,

I would first try Mass Compiling your VI's and see if that fixes the problem you are experiencing. Here's a KnowledgeBase that describes the steps and benefits of mass compiling.

What Does Mass Compile Do in LabVIEW?

Regards,

Steven Zittrower

Applications Engineer

National Instruments

http://www.ni.com/support

[Steve_Block]

What I need is a mass compile for TestStand.

[StevieZ]

Steve,

Sorry, you'll have to do this in LabVIEW. There is not a mass compile for TestStand.

Regards,

Steven Zittrower

Applications Engineer

National Instruments

http://www.ni.com/support

[Josh_W]

Steve,

It sounds like you are running your VIs with the LabVIEW runtime engine.  For this operation, we recommend that you do a TestStand deployment using the Deployment Utility.  The TestStand Deployment utility will save all of your VIs and make sure that they are packaged correctly so you can call them from TestStand without the LabVIEW development environment installed.

Please see Chapter 14 of the reference manual for detailed instructions for deployment.  You also might find this knowledge base helpful: Deploying TestStand Systems