LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

NI Software Licensing [aka: product activation] (thread from info-labview to LAVA)

There has been an interested thread developping on info labview about NI incoming product activation for Labview.

I think, everyone should have a look at it and give NI some feedback.

If you do not have access to info labview, check out that link (most of the discussion has been copied to the LAVA website): NI Software Licensing, Future LabVIEW licensing Policies

PJM


  


vipm.io | jki.net

Message 1 of 8
(6,785 Views)
It is a very interesting thread. I've already had to deal with product activation because I use TestStand which has had it since version 3. I've also been informed that the next major release of LabVIEW (8.0?) will have it.

In the thread there has been several comments in favor of dongles. Personally, I dislike those little things more than the hassle of requesting an activation key. I've had them get lost and damaged and getting a replacement has always been more of a problem for me than logging onto NI's site. My use of LabVIEW is probably different than many other users so it will be interesting to see comments from the rest of the communicty.
0 Kudos
Message 2 of 8
(6,778 Views)
I like the way MATLAB and DXP2004 handle network licensing: when you attempt to start the program, an attempt is made to use a license from the pool. If there are no licenses available, the program will not start. In some cases it can be determined which users and/or hosts are using licenses. All software runs locally.
0 Kudos
Message 3 of 8
(6,760 Views)
How do you get access to info-labview? I would like to see more on this subject. To anyone at NI that is concerned: PLEASE DO NOT DO THIS. I've had nightmares with TestStand 3 because of this activation code thing. I am the only developer so I should only need one development license. OK, so I develop on my desktop. Then I need to debug on the shop floor. I am still the only one using TestStand, but now I need a debug license for the shop floor. This is an outrage. What about having to debug at many different stations? How much is this going to cost in license fees? TOO MUCH. Also, I have had major problems with the way the activation code marries to computer IDs. Other software/hardware caused my computer ID to change, so I had to request another activation code each time the computer ID would change. This is NOT a good solution. Please, NI, do not do this to Labview. You will lose customers and it will hurt your business many times more than you would gain by eliminating any piracy that goes on.
- tbob

Inventor of the WORM Global
Message 4 of 8
(6,756 Views)

@tbob wrote:
How do you get access to info-labview?



http://www.info-labview.org/

PJM


  


vipm.io | jki.net

0 Kudos
Message 5 of 8
(6,751 Views)
Adding to PJM,

The Info-LabVIEW archieves can be searched using Brian Renken's search engine.

http://www.searchview.net/

Info-LabVIEW is were the "big-boys" (that is "boys" generic) hang out.

Ben
Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
Message 6 of 8
(6,699 Views)
I’ve recently been informed of the discussions about the NI licensing policies on info-LabVIEW and wanted to provide some insight and clarification.

NI has implemented license activation in many of our software products and plans to add license activation to our other major application software products. It seems that there have been misperceptions about how and why we are implementing this technology. It is also important to understand that there are differences between the underlying activation software mechanisms and the legal license agreement specifying appropriate use of our software.

Benefits to Activation
While I understand the skepticism, licensed activation will actually provide benefits to many LabVIEW users, as well as to NI. Let me provide you with a few examples.

With licensed activation, it will be possible for us to ship on a single CD an Evaluation Version, Student Edition, Base Package, Full Development System, Professional Development System, Debug Deployment License, and Application Builder. Of course NI will benefit from these streamlined activation mechanisms, as it means that we can spend less time producing and verifying countless different CDs and instead focus on delivering additional features and functionality to you. Today we actually produce, verify, re-verify, and stock more than 30 different variants of LabVIEW. We want to reduce the amount of time and effort it takes us to actually put out a release. This will also make it easier for us to produce more periodic maintenance updates, something which many of you have also requested.

But this alone did not drive our decision to implement licensed activation in our products. For years we have heard our user community complain that it is difficult to receive all the software they need at the same time, and in an easy-to-install manner. As an example, as a LabVIEW developer is writing a LabVIEW application, he often realizes that he needs a LabVIEW add-on to complete his project. This can cause a delay of several days while he purchases it and waits for it to arrive. And, in some of those situations, of course, a new version of LabVIEW has since started shipping, leading to further complications. We’ve seen this happen, not only with the Real Time Module and Application Builder, but also with numerous other add-on Modules and Toolsets. Licensed activation will mean that all this software can be installed on your machine, and with a simple activation, you can begin using the software in minutes. In the future, you’ll have the added benefit of being able to purchase and install software from the web immediately. In addition, by having all software install in an Evaluation Mode, you can more easily share your CD with colleagues to try out LabVIEW without worrying that the software is being used illegally.

Clarification on the Technology
There seems to be some confusion about exactly how the licensed activation tools work. When the software is installed, it will run in a fully-functional evaluation mode for 7 days if not activated. Thus, you need never worry about getting caught in a situation where you cannot activate your software at midnight to get your system running again. To activate your software, we provide numerous 24-hour a day mechanisms, including the web, email, phone, fax, etc. (see ni.com\license for details). We also understand that you may need to activate again because you have bought a new machine. That is why we allow you to activate multiple times, without forcing you to uninstall first.

Use Policies of Our Software
As previously stated, the introduction of this license activation mechanism did not drive changes in our end-user license agreement in any way. Our license agreement has been machine-based for many years. What became apparent to me in the email thread was that this has been misunderstood and has caused inconvenience to some of you.

Thus, I’d like to thank each of you who took the time to provide constructive feedback by outlining your use scenarios. This is the best possible way for us to understand your concerns. We value your feedback and take it seriously. It is not our intention to put roadblocks in place to reduce your productivity.

To that end, we have already started evaluating options for changes in our licensing agreement and supporting technologies to better address your needs. This includes evaluating a user-based license solution. Please send any use cases or feedback that you have on the topic to license.management@ni.com. (It will be functional by Noon Dec 20.) We are committed to your continued success with our products, and will not let licensing agreements be a hindrance.

Thanks for your feedback, and we’ll work with you to find an acceptable solution.

David Gardner
Director, LabVIEW R&D
National Instruments
Message 7 of 8
(6,639 Views)
well said tbob!

We often develop at our desk then try it in the lab (when the instruments are available).
Resources such as test instruments are often shared within a lab, so when you develop, it is more convenient to do so at the desk.

JLV
Message 8 of 8
(6,403 Views)