05-17-2016 05:25 AM
05-17-2016 05:38 AM
Hi
You can distribute your exe to the customer PC, you need to install Labview runtime engine on the customer PC or you can create a installer which will include the Labview runtime engine.
If u create a exe, you and the customer cannot see the block diagram.
regards
senthil
05-17-2016 05:50 AM
Hi Salcedo,
If you build an executable and install it on your buyer's computer he won't see the block diagram with the normal settings of the application builder. But building an executable alone won't keep the customer from copying it as many times as he likes. Even if he doesn't have your installer, he could just install all the toolkits and run time engines needed and copy the .exe to make it work. If your program isn't too complex, this should be doable.
If you want true security and stop the customer from copying it, you need licensing. There's a toolkit by NI that can help you with that: Third Party Licensing and Activation Toolkit
05-17-2016 06:34 AM
An alternative I've seen to licensing (though I don't recommend it) is hard coding the program to only run on a specific computer... for example run an "getmac" command and verify the mac address hasn't changed. If it changes, the program instantly stops execution with an error message.
05-17-2016 06:45 AM - edited 05-17-2016 06:47 AM
Another pro licence solution to use a physical USB key on the PC to enable application running.
http://digital.ni.com/public.nsf/allkb/42022E0D80E3D7B2862574D5006B4D7B
edit: the above link is only for example, but if you google for "usb key licence", you can find many companies who sell USB licence key packages..
05-17-2016 07:02 AM
@PeterFoerster wrote:
If you want true security and stop the customer from copying it, you need licensing. There's a toolkit by NI that can help you with that: Third Party Licensing and Activation Toolkit
You're confusing third party addons with built executables. This licensing is to control added functionality to the LV development environment. It's entirely useless for the original poster's use case.
05-17-2016 02:24 PM
Something that I haven't seen mentioned yet is that you do need to make sure that you final executable build does not have debugging enabled. If it is enabled you could pretty easily look at the block diagram if you have the LabVIEW development environment.
05-18-2016 02:04 AM
@natasftw wrote:
@PeterFoerster wrote:
If you want true security and stop the customer from copying it, you need licensing. There's a toolkit by NI that can help you with that: Third Party Licensing and Activation Toolkit
You're confusing third party addons with built executables. This licensing is to control added functionality to the LV development environment. It's entirely useless for the original poster's use case.
On this site it says: "Add licensing to Applications Built in LabVIEW..." I understood this as: It provides the possibility to generate license keys for your built applications as well as add ons in a similar style to the way LabVIEW and its toolkits are licensed.
I haven't looked at it in too much detail, though...
05-19-2016 04:38 PM - edited 05-19-2016 04:39 PM
Yes NI has several technoligies for licensing products. There is also BLT that I've never personally used but sounds good.
http://sine.ni.com/nips/cds/view/p/lang/en/nid/211731
You can roll your own licensing software, but it probably isn't worth it, and others have the tools already if you are willing to pay for them.
Unofficial Forum Rules and Guidelines
Get going with G! - LabVIEW Wiki.
17 Part Blog on Automotive CAN bus. - Hooovahh - LabVIEW Overlord
05-31-2016 02:59 AM
Hi my friend. Thanks a lot for answering.
Do you know the difference between That toolkit of Labview and BLT? Thans a lot.
And do you kne where I can find information about the toolkit?