Understanding TestStand Debug Deployment License

[mase26]

After reading the License Agreement and the TestStand Help section on licenses I still would like an explanation as to exactly what the license does and does not allow. My understanding is with a TestStand Debug/Deployment license I can install TestStand on a machine, let's call it the development machine, and also install TestStand on another machine, my production machine. The development machine is where I would develop applications to deploy onto my production machine. The production machine is where I would actually test my products. The production machine can also be used as a platform to debug my deployed applications. If this is true then can I develop any additional tests on the production machine, e.g. I found a problem in the sequence so I need to add a new sequence to correct the error? Or I found a problem with a LabVIEW VI and I need to create a new VI to correct it. Can I develop VI's and sequences on the production machine or do I need to develop on the development machine transfer the files over to the production machine and hope it works (this type of process could prove to be very time consuming and tedious)?

[tbob]

You can use TestStand in the development mode on your production machine just like at your development machine. No difference. So yes you can create new sequences, new vi's, etc. on your production machine. The debug license allows you to develop on your production machine. You can legally install the development environment on both machines, but you can only use one at a time. The purpose of the debug license is to save you money. Instead of buying two full development systems, you buy only one and buy the debug license (costs much less than the full development system). Since you can only work on one machine at a time, this allows you to debug your applications on the production floor, or even create new applications on the production floor. You cannot however, install the development system on your machine and a co-workers machine and use the debug license for the co-worker since it is quite possible that both of you will be using the development environment at the same time. This would be illegal.

[mase26]

Thanks for the info. Now what about LabVIEW. Here are some options I'm considering:

1. Run a LabVIEW Runtime Engine on the production machine and a FDS of LabVIEW on the development machine. In turn run a TestStand Deployment license on the production machine. This seems the most cost effective method. The problem I'm having is some VI's are developed in LabVIEW 6i, 7.0, and 7.1 and the LabVIEW 7.0 RT Engine does not work with TestStand 3.1. It seems only the LabVIEW 7.1 RT Engine will work with TestStand 3.1. But I don't have a LabVIEW 7.1 development license (not sure how the 7.1 VI's came to be, before my time). I've also thought of using standalone LabVIEW applications but the only license I have for Application Builder is from LabVIEW 6i PDS from the Developer's Suite. If TestStand 3.1 is suppose to work with any LabVIEW RT engine then I'm doing something wrong.

2. Run a LabVIEW Development/Deployment license with a TestStand Development/Deployment license. This is the most expensive method but the easiest to implement.

3. Run a LabVIEW FDS and a TestStand Deployment license on the production machine.

A finally question, does NI make available a TestStand Run-time Engine that is available as a free download, similar to the LabVIEW Run-Time Engine?

[tbob]

The TestStand RTE is not free. It costs $500 per computer it is installed on. Of your choices, number 2 is the best and that is why it costs more. This allows freedom to develop and debug both LV and TS on your production machine. Otherwise, you have to develop LV at your desk, create an exe to run on the production machine, and you must have the LV RTE that TestStand will work with. You would have to upgrade to LV7.1. No matter what you choose, it will cost.