Incorporate one of the following options to leverage hardware binding (in which the license file is bound to your hardware) in your add-on license. For a complete tutorial on how to license a deployment add-on, refer to: Licensing a Deployment Add-on.
To implement hardware binding in which the license file is bound to the computer ID number use the Protection Plus Enhanced computer ID Algorithms.
3. After you have created a license file for the add-on use the Third Party Licensing & Activation VIs to enforce licensing in deployment add-ons that you build in LabVIEW.
If you want to bind a license to a specific hardware target, use the custom hardware licensing method. It allows you to bind your license file to a custom hardware ID you specify. You can use the serial number of the hardware target to which you want to bind the license while activating it and if a user tries to use the license on a different target, the status of the license would show up as invalid.
3. After you have created a license file for the add-on use the Third Party Licensing & Activation VIs to enforce licensing in deployment add-ons that you build in LabVIEW.
NOTE: The license also shows up as activated if the custom hardware ID input is not wired or is set to zero.
Refer to Third Party Licensing & Activation VIs for more details on how to add licensing checks to source code.
Hello Sumedha,
I want to bind the license with the specific hardware. For this, I used TPLAT Activate License for Custom Hardware API VI. I was able to activate the license successfully. After activation, I wanted to check the status of the license. For this, I used Get License Status API VI I am getting activated status even if I enter wrong custom hardware id. I am using LabVIEW 2015.
As per Get License Status API VI documentation if the custom hardware id is given wrong input I should get license status invalid but I am always getting activated status.
Regards
Hemant