From 04:00 PM CDT – 08:00 PM CDT (09:00 PM UTC – 01:00 AM UTC) Tuesday, April 16, ni.com will undergo system upgrades that may result in temporary service interruption.

We appreciate your patience as we improve our online experience.

LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

selling exe file

My company is looking into using LabVIEW to build an application that will be sold as part of a product.  The product would have the executable file installed before shipping to the customer.  Is this permitted given the licensing agreement or is there some other licensing required?




metzler CLAD
0 Kudos
Message 1 of 15
(3,039 Views)

Although some of us work for NI (not I), this is a "legal" question about licensing that you should discuss directly with them.  Call your NI Representative or go on the Web and look them up.  

 

Bob Schor

Message 2 of 15
(3,013 Views)

I know certain toolkits or modules need additional deployment run-time licenses. Vision is one that does and there will be some others I'm sure.

 

Most don't need anything additional and just having the application builder is enough, but best to check with NI for your specific case.

 

 

 

 

 

 

 

Message 3 of 15
(2,970 Views)

Thank you for the advice.  Since the LabVIEW run-time engine is free, I would think any built application would also be allowed to be distributed without additional licenses.  

 

I have emailed NI and will post their response.  




metzler CLAD
0 Kudos
Message 4 of 15
(2,955 Views)

From what I understand you are legally allowed to sell and distribute your source code and executables.

 

After all the code you write is your (company's) intellectual property, not National Instrument's.

 

You just can not charge for any of the required NI-runtime libraries your executable needs or sell your LabVIEW development package or NI-toolkits you have purchased.

========================
=== Engineer Ambiguously ===
========================
Message 5 of 15
(2,915 Views)

@metzler wrote:

Thank you for the advice.  Since the LabVIEW run-time engine is free, I would think any built application would also be allowed to be distributed without additional licenses.  

 

I have emailed NI and will post their response.  


Disclaimer: I am not a legal consultant.  I am a LabVIEW Consultant. 

 

Your exe developed with LabVIEW may be sold by your company to your clients.  There are requirements for some addons and toolkits.  Also, be aware that your company is also responsible to your government to comply with any import/export restrictions or tariffs.   

 

Get a lawyer.


"Should be" isn't "Is" -Jay
0 Kudos
Message 6 of 15
(2,888 Views)

Thanks Jeff for your reply, as selling the exe file with the hardware product is what is the plan. 

The only toolkit I believe may be used is the MS Office toolkit, which I cannot find any requirement for an additional license.  

 

I have not received a reply to my email directly to NI about this, so responses here are valuable (in addition to researching the issue) in determining the answer.




metzler CLAD
0 Kudos
Message 7 of 15
(2,883 Views)

The only response you should consider to be the "answer" should be the official response you get from NI.

Bill
CLD
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.
Humble author of the CLAD Nugget.
Message 8 of 15
(2,876 Views)

No idea about legal issues, but I believe the toolkit requires MS Office to be installed; not sure what minimum version is required or if it will work with bought permanently Office, leased Office, etc.

 

mcduff

0 Kudos
Message 9 of 15
(2,872 Views)

Who calls the Report Generation Toolkit the MS Office Toolkit (the name I recall from LabVIEW 7)?

 

Anyway, you should also know that LabVIEW Versions vary independently of Office Versions.  The current RGT is configured for an earlier (not sure which) version of Excel -- it's an easy fix to make if you have the LabVIEW source, but once you make an EXE, it will either be compatible with Excel or not.  Something to consider ...

 

Bob Schor

Message 10 of 15
(2,865 Views)