Licensing question

[duncannz]

Background:

I have a prototype system which is running on a dedicated laptop.

I threw together a VI in the evaluation version of LabVIEW which is currently running on the laptop.

I built an exe, and this is what is currently being used for testing. 

The client is keen to have a backup laptop on hand in case the first one dies.

The have installed the LabVIEW runtime, and the exe seems to run just fine.

I have since bought the LabVIEW Full with the intention of putting this licence on the dedicated laptop.

I now have several questions:

1) Will the exe still work when my evaluation licence expires? (i.e. will I have to modify my shortcuts to run the vi file instead of the exe?)

2) Is there any way to devlop on a LabVIEW Full licence and deploy as a runtime without further licences? Or is this the intention of the deployment add-on?

3) If the prototype is successful, three more systems will be required immediately with an order for 7 more to follow.

As I see it, my options for this are:

a) Get a deployment licence, build exe and run on each laptop with LabVIEW runtime (no licence required?)

b) Get a LabVIEW licence for each system and run the vi from a shortcut.

Does this sound right?

Just not quite sure how it's all supposed to piece together.

Thanks for any insight!

Duncan

[altenbach]

Only LabVIEW professional includes the application builder.

If you only got LabVIEW full, you can purchase the application builder seperately.

Typically you would build an an installer and deploy it to an unlimited number of target machines. They don't need any license, just the free run time engine (unless you use certain special toolkits, I heard.). You can even include the runtime in the installer.

I would guess the existing exe will continue to run, but I have not tried this.

II would recommend not to run production VIs from the development system. As the name implies, it is for development, testing and debugging. If you have all these projects in all these locations, you can never be sure that they are all the same version and that nobody makes unauthorized local changes.

[crossrulz]

1. You will want LabVIEW Pro to have the Application Builder (to make your executables).

2. Make sure that source code is safely stored on a server that gets backed up regularly.  I would also recommend using a Software Code Control software (like SVN or GIT) so you can track changes, etc.

3. You do not need a LabVIEW license for every machine to run the executable.  Just build and installer for your code and install that on the production line.

4. I highly recommend you contact your local NI representative and have a nice sit down with them to discuss your situation, especially if hardware is going to enter the picture.

[Alexander_Sobolev]

Yes, toolkits that require deployment license exist.

See full list here. https://www.ni.com/en/shop/software-portfolio/deployment-and-debug-licenses-for-ni-software.html

One more link 

What is National Instruments' Policy on Run-Time / Deployment License Upgrades?