Discussion:
NI TestStand Base Deployment Engine License
(too old to reply)
mrbean
2008-02-14 15:40:16 UTC
Permalink
Since I haven't ordered this yet, I wanted to get a little clearer picture of the inner workings ...
 
I plan to order NI TestStand Base Deployment Engine License for our target system that we'll ship in a few months.  Right now, it has LabVIEW 8.5, TestStand 4.0, and DIAdem 10.2 on it, as we're also using it for development.  When we ship, we don't want the user to be able to create/edit sequence files, or to open up VIs and make modifications.  DIAdem, however, they will use as their post-test data mining tool, so it must remain fully functional.
 
(1) Would I use the NI License Manager and (a) deactivate TestStand and LabVIEW, then (b) activate them with the activation code I receive with the NI TestStand Base Deployment Engine License?
 
(2) Would this disable the user's edit capability for BOTH TestStand AND LabVIEW, but leave DIAdem unchanged?
 
(3) To protect our intellectual property, would I still need to either (a) place our VI's in a DLL, (b) lock them, (c) disable their block diagrams (while using the deployment/distribution tools).
Jervin_J
2008-02-18 21:40:11 UTC
Permalink
Hi mrbean,
Jhoskins is right, all you need are the multiple licenses, you don't need a set of CD's for each license.
As far as your questions specific you your application, you are right on the ball.

- Using NI License Manager, deactivate LabVIEW and switch your TestStand activation to the deployment activation using the deployment activation code.

- Yes, this should leave DIAdem still activated and fully functional.

- Either of those options (dll, locking/disabling block diagram) would work to protect your Intellectual Property.

Hope this helps!
Ray Farmer
2008-02-19 08:10:11 UTC
Permalink
Hi,
I believe you would have to have a separate runtime license for the labview.
Regards
Ray Farmer
Jervin_J
2008-02-20 00:10:14 UTC
Permalink
Hi mrbean,Activating TestStand with the Base Deployment license should disable the sequence editor. I would refer to the following document that enumerates the&nbsp;differences between the different license types:<a href="http://www.ni.com/teststand/depcompare.htm" target="_blank">http://www.ni.com/teststand/depcompare.htm</a>
If you already have LabVIEW installed, it will not make any changes to the LabVIEW license. You mentioned that you don't want to allow the users to be able to open up the VI's so you might also want to uninstall LabVIEW and install (if you don't have it) the LabVIEW Runtime Engine.<a href="http://www.ni.com/support/" target="_blank">http://www.ni.com/support/</a>
Also, you would have to set your LabVIEW adaptor in TestStand to use the LabVIEW Runtime Engine instead of LabVIEW.From TestStand, click Configure»Adaptors..., select the LabVIEW adaptor and click Configure. From the dialog box that pops open, pick the LabVIEW Runtime Engine instead of the Development System.
Hope this helps.

mhousel
2008-02-19 14:40:13 UTC
Permalink
Thanks, Jhoskins wrote:Mhousel,

You only need one set of CD's for multiple licenses. No license is tied to any CD. When you are prompted for the serial # all you do is put int eh one that want to use. Heck really you do not even need the CD's at all. you can download the trial version and activate it with the deployment license you have.That is the piece of information that I was missing.&nbsp; I was associating the S/N that came withour CD's as the license for that setof CD's (Like WIndoze, et. al.)
Loading...