LabVIEW license enquiry

Hello,
I would like to get some details regarding NI license programs available.
What are the available license programs and what would be best for a company with 3 to 4 labView users?
Can we have computer based license on 4 computers?

kdm7 wrote:
[...] P.S I prefer posting on discussion forums to talking over the phone, as I get fast replies and I am an introvert!
How do you tell an extroverted engineer from an introverted one?
Spoiler (Highlight to read)
The extroverted engineer looks at your shoes when he's talking to you.
The extroverted engineer looks at your shoes when he's talking to you.
Jim
You're entirely bonkers. But I'll tell you a secret. All the best people are. ~ Alice

Similar Messages

Error 2: Failure to perform LabVIEW license activation

I bought and downloaded LabVIEW student edition. When i downloaded it, it all went fine. Then when i got to the page to put in a serial #, i put the one that the download gave me, and a message popped up saying, "Error 2: Failure to perform LabVIEW License Activation" So, i tried to look up the problem and it said to disable my firewall and restart my computer and try to download again from scratch. When i did all of that, it still had the same problem and the same message. I dont know what to do...
P.S. - I called the company that i bought the product from and they told me to call National Instruments and i did, the lady that answered was very rude and told me its not their problem, call the other company back. When i did, they said they were going to call NI. They called me back and told me to go to this site and post my question.

That is really strange if y ou called and some lady told you it wasn't her problem. If you got her name, you should contact customer service.
As a matter of fact, you should contact your local customer representative. Tell them you may become a long term client and wish to be treated that way..
If you cannot automatically activate the software over the internet and have tried several times, then calling in may be the only way. There are insatnces when you get the error message, but it still activates the software. Did you re-start LabVIEW to see if it is now activated? Did you try multiple times?

Error 2 failed to perform action labview license activation

Bonjour,
Quand j'installe Labview, à la fin de l'installation, j'obtiens le message d'erreur suivant :
"error 2 failed to perform action labview license activation"
Et quand j'essaye d'ouvrir Labview par lasuite j'obtiens ce message :
"Il se peut que l'installation de cette application soit corrompue. Essayer de réparer ce programme en utilisant la fonctionnnalité Ajout/Suppression de programmes du panneau de configuration Windows"
Seulement Labview n'apparait pas dans cette liste de programmes...
J'ai un numéro de série pour une licence étudiante que je rentre durant l'installation.
Merci de m'aider si quelqu'un a une solution.

Bonjour Vincent,
As-tu déjà retenté une réinstallation de LabVIEW ? L'erreur fait référence à une corruption d'installation.
Je te propose donc de désinstaller/nettoyer manuellement LAbVIEW ou en utilisant un "cleaner" type Windows Installer Cleanup Utility et de procéder ensuite à une réinstallation du logiciel.
Cordialement,
Antonin G. Associated LabVIEW Developper
National Instruments France
#adMrkt{text-align: center;font-size:11px; font-weight: bold;} #adMrkt a {text-decoration: none;} #adMrkt a:hover{font-size: 9px;} #adMrkt a span{display: none;} #adMrkt a:hover span{display: block;}
Communauté francophone des développeurs LabVIEW et des enseignants en STI2D
Si vous souhaitez partage...

Issues with labview on TestStand deployment system (wont run without a labview License)

I am trying to deploy a system using testStand to a deployment machine for the 1st time. I have built my installer and image files etc.The files install successfully on the target machine however when I try and run my program in TestStand operator mode I have getting errors relating to Labview. The only way I can get around these error is to activate a Labview License on the deployment machine, this is not viable.
The error I see when I disable my Labview License simply states an error occurred accessing the Labview ActiveX automation server.
I have included the run time engines etc in my installer. As this is my first build is there something obvious I have missed here??
Thanks for any input.
Vinny
Solved!
Go to Solution.

Vinny,
my first guess is that the setting for the LV adapter on the deployment machine is still configured for "LabVIEW Development Environment". You have to change this to "Runtime Engine".
hope this helps,
Norbert
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.

Are LabView licenses for Windows transferrable to Mac OS X?

I can't seem to find any information on this subject on the National Instruments or in a search on this forum, so hopefully someone can answer these questions.
My lab has 3 licenses for the use of LabView 8.5 in our lab, although the instructions that I've been given to install LabView involve downloading the trial software from National Instruments' website, and then using the activation code to activate the software. Trouble is, the trial software is for Windows only, and I was hoping to be able to run LabView on the Mac in our lab.
Are the licenses for LabView transferrable across platforms, or does my lab need to specifically purchase a version of LabView for the Mac? If the licenses *are* transferrable, how do I request a CD for the Mac installers if we've already purchased LabView for Windows? Furthermore, if I'm able to use these licenses on a Mac, is it possible to install the Windows version on my Mac on my Boot Camp partition, and install the Mac version on my Mac OS X partition and only use up one license? I'm not sure if all of our hardware has drivers that will run under Mac OS X on an Intel Mac, and I don't want to be penalized for this by having to use up two licenses on the same machine.
Any answers to these questions would be much appreciated.

Hi SimX,
The LabVIEW licenses are not transferrable directly, since LabVIEW for Windows and LabVIEW for Mac are entirely different products and have different installers.
In this case, you should contact your local sales representative to see what your options are. You can find the email contact information at http://sine.ni.com/apps/utf8/nicc.call_me?p_lang_id=us, or call in to 866-ASK-MYNI (866-275-6964).
Regards,
Stephen S.
National Instruments
Applications Engineering

How many LabVIEW licenses out there?

This Q isn't of a technical nature; but I'm searching for reasons for my superiors to support my effort in creating a LV solution for our device. The bean counters need to count their (potential) beans.
Does anybody have a ballpark idea about how many LabView licenses are out there? I realize this is a big number, but what order of magnitude?
I realize that universities are big users.. would you say that MOST schools use LV in some capacity?
In industry: What industries?
If you can help me with this, then I can go back to being a software weenie and take off this ill-fitted marketing hat. Then I'll start pelting you with tech Qs.
Thanks-
Suz.

LabVIEW is everywhere!
I am not sure if the total number of LabVIEW developers is public information, a better number would probably be the market share in test/measurement/instrument control, etc. software. Another number would be the count of deployed system with LabVIEW under the hood or used in development. This is probably also rapidly growing, especially counting FPGA and embedded systems.
Have a look at figures 1&2 from this article. It shows LabVIEW way ahead at 32% long ago (Q1 2004). There are probably newer numbers available somewhere.
Just wait a few years until all the particiants of FIRST enter the job market and things will really start rolling exponentially.
Message Edited by altenbach on 01-28-2009 12:26 PM
LabVIEW Champion . Do more with less code and in less time .

Run labview program without necessity of labview license . is it possible?

Hi
I wonder is it possible to have a labview program that can be run without of necessity for labview license?
now we can produce executable labview programs but they need labview licences.
Best regards
s Farashi
Solved!
Go to Solution.

That does not make any sense. You have a license for the development system. You can create an exe and distribute as many copies as you want without further licenses. The only thing you have to distribute with the exe is the runtime engine. Where did you get the idea you needed a license for each exe?
Message Edited by Dennis Knutson on 01-30-2010 12:11 PM

Deactivate LabVIEW License to Use Elsewhere

Good morning,
My company has a number of license for the LabVIEW Professional Development System and LabVIEW Application Builder. I used the LV Prof. Development System to create the program I needed on a PXI Chassis. I then built an application and installer. I then completely removed all NI software from the PXI and just used the installer to reinstall the necessary files for the application. I went into the LV License Manager and it just says that I have no licenses installed on the PXI.
Everything works, but I want to make sure that the license I had previously used for the LV Prof. Development System is now available for another computer, since I'm no longer using it on this one.
Thank you in advance,
Ben B.
Solved!
Go to Solution.

Did you deactivate the licence on the NI Licence manager before uninstalling? If you didn't then the NI licencing server still thinks you are using the PXI box. Give your local NI office a call and they'll sort it out for you.
- Cheers, Ed

NI Labview License Manager

I'm thinking about using license manager to keep track of users of
labview full development packages and remote front panel. Is anyone
familiar with its operation?

That's what I was afraid of. I was looking for something to manage labview
full development licenses running on a number of machines. Thanks.
"Jeremy Braden" wrote in message
news:[email protected]..
> How are you planning to use the License manager? NI did not make the
> manager as a tool so that you can licence out programs yourself. This
> is not say that it cannot be done--it is that you will be on your own.
> I believe the functionality is built in to monitor the users to your
> front panel web page in the remote panel connection manager.

LabVIEW license for terminal servers and thin clients (e.g. LTSP)

Does NI plan to provide a license agreement for terminal servers and thin
clients?
I've been told to purchase a multi-seat license. That doesn't make much
sense since the thin clients won't be accessing DAQ hardware. They're
just used for developing the LV source.
Comments/suggestions?

On Thu, 04 Nov 2004 13:43:58 -0600, jbrohan wrote:
> As far as I know it's the capability to edit the source code that NI has
Yes, this is a very good point. Quite a unique situation when compared to
text based languages. Keep in mind I certainly don't mind paying for that
but I see no need to pay for much of the other features - like running it.
This is certainly one of the other features you pay for with LV. Since
we never plan to run the app on the thin client, why pay for that
feature?
What we do is crank out source code on the thin clients. We then send the
source code to this wireless mobile DAQ station running WindowsXP. From
there we can roll it up to our clients' target systems. That machine is
used for debugging then compilin
g so it has its own LV Prof Dev license
installed on it. Also, it can be operated locally or remotely via remote
desktop (one user at a time).
I know it may sound strange but it works great. And as the NI Software
License Agreement(NISLA) specifies, we have separate licenses on all
machines that load LV into local memory. The thin clients load nothing
into local memory, hence no need for a separate license.
> I express myself clearly in the hope of guidance. I am a one man shop
Yes, this is understandable. Installing one license on multiple machines
is a big no-no. However, that is not what I'm trying to do. Take a peek
at the "Grant of License" and "Single Seat License" sections of the NISLA.
> You say "That doesn't make much sense since ..." One of my clients has a
Ha! How about this scenario: As wireless hardware (bluetooth, wifi)
becomes more common, perhaps NI will have a peer scanner on all PCs with
LV installed. That way if you get within 100 feet of a P
C with the same
LV serial number, you get locked out and it sends a small message to the
NI batcave.
Thanks for the response. I'm hoping NI chimes in soon.

LabVIEW 8.5 Executable on Windows System 7 64-bit

I have a program that uses the Vision RTE and LabVIEW 8.5. The Program was written and compiled on a PC with Windows XP (32-bit). A customer installed the program onto a PC with System 7 64-bit and is having problems running the program.
Is there a way out of this without upgrading LabVIEW and recompiling the program?
Thanks in advance...

@Peter_steier -
First off, you should create your own thead next time you have an issue.
Second, according to here: http://digital.ni.com/public.nsf/allkb/B972242574D4BB99862575A7007520CB you would need AT LEAST LabVIEW 2009 SP1 as a minimum for Windows 7:
You did, however, mention you were doing development on the LabVIEW 8.5.1 application. If you have the original files, they should open fine on any of the newer versions of LabVIEW. As a result, you could rebuild the EXE for a newer version of the Runtime Engine as well. Unfortunately this would mean that you need a new LabVIEW license to install on the newer Windows 7 or later PC.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
If someone helped you out, please select their post as the solution and/or give them Kudos!

LabVIEW 8.6.1 did not fix glaring Mixed Signal Graph bug :(

I'm pretty dissapointed that NI has JUST NOW released 8.6.1 (more than 6-months after releasing the buggiest LabVIEW version, ever). The Mixed Signal Graph bug still exists and is very annoying. The visual bug occures when you add more than 1 plot on a mixed signal graph and then try to resize the legend. The Y-Axis labels do not move appropriatly. You really can't resize the legend with this bug.
Where can I find a list of known bugs in LabVIEW and verify that this is in that list? How can I add weight to this bug report so that NI will address it for the LabVIEW release? How can I express to NI that I don't want LabVIEW 9 until they can fix all the problems in v8?

LV_Pro wrote:
One way might be to get in on the LabVIEW 2009 Beta, see if it fixes the problem, if not, report it while there may still be time to fix it.
Not sure about the "buggiest version", v2.5 had its share. Had to save your work every 1/2 hr. or risk loosing everything when you got the almost guaranteed "insane error" which always seemed to occure when you had done the most editing since your last save.
Message Edited by LV_Pro on 02-10-2009 09:07 PM
The OP obviously never had to work withLabVIEW versions prior to 5.1.
And while 8.6 had a few nagging bugs including visual ones it is actually quite stable and good. No comparison with 8.0 for instance or even 8.0.1
Nickerbocker wrote:
I'm pretty dissapointed that NI
has JUST NOW released 8.6.1 (more than 6-months after releasing the
buggiest LabVIEW version, ever). The Mixed Signal Graph bug still
exists and is very annoying. The visual bug occures when you add more
than 1 plot on a mixed signal graph and then try to resize the legend.
The Y-Axis labels do not move appropriatly. You really can't resize
the legend with this bug.
Where can I find a list of
known bugs in LabVIEW and verify that this is in that list? How can I
add weight to this bug report so that NI will address it for the
LabVIEW release? How can I express to NI that I don't want LabVIEW 9
until they can fix all the problems in v8?
You just did! But unless you are a site with several 1000 LabVIEW licenses you will not outweigth those other customers who do have that many licenses and do want more features as soon as possible rather than an annoying graph display bug getting fixed.
Rolf Kalbermatter
Message Edited by rolfk on 02-11-2009 10:02 AM
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Toolkit license issue

Hi all,
Am owning LabVIEW 8.6 license, I am trying to install sound and vibration toolkit with some other license.
Is it possible to use different license toolkit with my labview license?
Thanks in advance!

The sound and vibration toolkit license is separated from the Labview development license. You will also have 30 day full trail option. Then this trail period is over, only the toolkit will stop working.
Besides which, my opinion is that Express VIs Carthage must be destroyed deleted
(Sorry no Labview "brag list" so far)

Using SignalExpress with LabVIEW VIs

Hi everyone,
a short question about interaction of SignalExpress and LabVIEW: does the integration of LabVIEW Code work although LabVIEW is not installed? I may have an application where users need to use some VIs in SignalExpress but they don't need to edit them. So it would be nice not to have too spend the money on antoher LabVIEW license.
Cheers
Oli
Programming languages don't create bad code, programmers create bad code....

Hi Oli,
take a look into Knowledge Base Entry 3LAGNBL2: http://digital.ni.com/public.nsf/websearch/F6D5EF4620EE12EB86256FFE007D2086?OpenDocument, it tells you the requirements for doing that.
Furthermore you will find useful information about creating these steps in the following docs:
http://zone.ni.com/devzone%5Cconceptd.nsf/webmain/5A807DFBE89D7EAD86256ED30008D88A/$File/WP2466.pdf
http://zone.ni.com/devzone/conceptd.nsf/webmain/B19A4046EADBFA6C86256EE90078C35E
Hope it helps!
Good luck programming your plug- ins and kind regards
Stefan
Impossible is nothing - nothing is impossible

The flaw in LabVIEW Tools Network: VI Package Manager

At first I was impressed with the LabVIEW Tools Network (see here). Its seemed like a plus for everyone:
- Developers who didn't want to reinvent the wheel, could easily find and download code using the VI Package Manager.
- Developers who want to re-sell their code, could easily package it and sell it via the Tools Network marketplace (similar to the iPhone's App Store).
But then I found the flaw: The VI Package Manager
Developers (essentially) need to use the VI Package Manager if they want to sell their code ... and it costs $999. And you'll need to add on the cost of a LabVIEW license ($2k+), of course. This will surely elimate many coders from participating. In fact, it'll probably also artificially raise the price of all the SW being sold on the Tools Network.
And by the way: Why is NI relying on a third-party SW delivery tool for their marketplace at all? Especially one that costs developers $1k to package their add-on? Why doesn't NI just build their own VI Package Manager and dump JKI Tools all together? In this case, building their own Package Manager would make sense for NI. Cut ot the middle-man. And after all, didn't NI do this to Endevo when they built their own LVOOP tool (thereby dumping Endevo's GOOP toolkit into oblivion?).
Oh... and need I remind anyone that Apple only charges developers $99 to distribute iPhone apps? And their development environment is given away totally free.
Solved!
Go to Solution.

Hi
josborne,
Thanks for the feedback on the LabVIEW Tools Network. We wanted to make it easy for developers to share/sell reusable code with eatch other, and make it easier for developers to get their hands on reusable code rather than program everything from scratch. We wanted to build an ecosystem and marketplace for LabVIEW developers.
It sounds like your biggest pain point is the $999 price point for VI Package Manager. We worked with JKI this past year to make package building a feature of the free edition of VIPM 2010, the Community Edition. So you do not need the $999 Professional Edition to create a LabVIEW Add-on. The Pro version does have several nice benefits though, and you can read about these here: http://jki.net/vipm/compare
You also contrasted our program with the Apple Developer Program which gives you the development tools for free (with the $99 program fee). Well, the main difference here is that the development environment for LabVIEW is LabVIEW! (As opposed to Apple where you are developing for the iPhone/iPad). So I don't think we're comparing Apples to Apples (no pun intended). However, we do offer start-up assistance to developers who want to develop LabVIEW Add-ons to further reduce the barrier to entry. More here: Add-on Dev Center - Startup Assistance.
To answer your question about why we chose to go with a third party solution (JKI's VIPM) instead of developing our own - we had several reasons. But I can summarize in one - we had a partner, JKI, who has developed an excellent solution for distributing LabVIEW Code, and was willing to work with us to make the integration with LabVIEW even better, so why create a brand new solution from scratch rather than let them continue to innovate in this area?
By the way, if you haven't seen the integration between the Tools Network and VIPM 2010, you really should give it a try! Here's a sample free Add-on to try - the OpenG Libraries (Click the Download button).
Jervin Justin
NI TestStand Product Manager

LabVIEW license enquiry

Similar Messages

Maybe you are looking for