Deployment of TS & LV files

[mrbean]

We are not quite at this point, but I'm taking a proactive approach.  Right now, we have a test system that runs TestStand 3.5 and most of the steps are calls to LabVIEW VIs.  Our sequence file currently points to VIs that reside right there on the hard drive (also under configuration management), along side everything else.  This particular system is staying in house.  However, we're building a second, identical, system that we have to deliver to the customer.  My questions ...

1) We don't want the source code to be exposed - what is the best way to package our VIs/Seq files at development/delivery (if different) such that TestStand can find the items it needs, but still disallow the user from viewing/modifying the source code?

2) Does the TestStand Base Deployment License help in this situation?

[AEDavid]

Hi MrBean,

The best way to hide the source code, while allowing TestStand to find the files it needs, is to lock the VI diagrams.  This can be done when using the Deployment Utility using the "LabVIEW Options".

The TestStand Base Deployment Engine License is the minimum license required for all deployed TestStand-based applications. This license allows you to deploy the TestStand Engine, a TestStand Operator Interface, and TestStand sequence files to the single test station for which the license is applicable.

The TestStand Base Deployment Engine License provides simple sequence debugging capabilities, including setting breakpoints and single stepping through test sequences in your Operator Interface. You cannot save sequences and open the sequence editor.

For more information on TestStand licensing, please see the TestStand Licensing KnowledgeBase Article.

Message Edited by AEDavid on 03-05-2007 10:45 AM

Message Edited by SarahM on 03-05-2007 07:08 PM

Message Edited by SarahM on 03-06-2007 08:25 AM

[AEDavid]

Hi MrBean,

You can also lock your source sequence files from Edit >> Sequence Files Properties by the following dialog:

Message Edited by AEDavid on 03-05-2007 11:03 AM

[AEDavid]

Hi MrBean,

Here is a screenshot for locking your LabVIEW VIs:

Message Edited by AEDavid on 03-08-2007 03:49 PM