04-13-2015 09:31 AM
@natasftw wrote:
I'd argue the application builder isn't very useful without a commercial application.
What are you doing with it that you believe it's what makes or breaks LabVIEW in a personal application use case?
Do you run all your programs from the development environment?
I want to be able to write a program and compile it so I can run it on a less powerful computer, like I do now at work.
Compare the requirements of an development system vurses the runtime
http://www.ni.com/labview/requirements/
Processor | Pentium III/Celeron 866 MHz or equivalent | Pentium 4/M or equivalent |
RAM | 256 MB | 1 GB |
04-13-2015 09:44 AM
I vote for including the Application Builder, there are some instances where I'd like to deploy an app to another PC in my residence withouth having the burden of installing LabVIEW.
-AK2DM
04-13-2015 09:46 AM
04-13-2015 09:56 AM
@Dennis_Knutson wrote:
So you would have multiple computers at home? Probably not very typical and I suspect unlikely to happen just like the student edition will never have the app builder.
I have 6 computers at home
if I count my Rasberry Pi's I have 11
Plus 3 tablets.
04-13-2015 09:58 AM
04-13-2015 09:59 AM - edited 04-13-2015 09:59 AM
@RTSLVU wrote:
@Dennis_Knutson wrote:
So you would have multiple computers at home? Probably not very typical and I suspect unlikely to happen just like the student edition will never have the app builder.I have 6 computers at home
if I count my Rasberry Pi's I have 11
Plus 3 tablets.
Not to mention I can throw together an Intel Atom based Mini-ITX computer for <$200 to dedicate to a task.
04-13-2015 10:07 AM
@AnalogKid2DigitalMan wrote:
I vote for including the Application Builder, there are some instances where I'd like to deploy an app to another PC in my residence withouth having the burden of installing LabVIEW.
I suspect NI will never include the application builder in a student or home edition. If they did then for a very minimal cost a company can build an EXE and deploy it to thousands of test systems, which might or might not have NI hardware. There is room for lots of lost revenue. I'm guessing the intent of this license scheme is to get peoples feet wet, and get them interested in LabVIEW. These new-comers can then try to influence the company they work for, to increase using NI products.
Unofficial Forum Rules and Guidelines
Get going with G! - LabVIEW Wiki.
17 Part Blog on Automotive CAN bus. - Hooovahh - LabVIEW Overlord
04-13-2015 10:16 AM - edited 04-13-2015 10:16 AM
@Hooovahh wrote:
I suspect NI will never include the application builder in a student or home edition. If they did then for a very minimal cost a company can build an EXE and deploy it to thousands of test systems, which might or might not have NI hardware. There is room for lots of lost revenue. I'm guessing the intent of this license scheme is to get peoples feet wet, and get them interested in LabVIEW. These new-comers can then try to influence the company they work for, to increase using NI products.
I suspect you are right, but even if they offered it as an extra cost add on, as long as it was reasonably priced, I would be satisfied.
I would even accept a notification at launch of a compiled program that said "Licensed for non-commercial and personal use only".
04-13-2015 11:47 AM
Thats a great Idea.
Personally I think if NI were to offer a application builder it would not be a complete one but instead some scaled down version that supports no device drivers. Otherwise why have all this expensive LaBVIEW software stuff along with the Device driver set if you could get basically the same for like less than 100 bucks. Perhaps I am missing something here.
The SSA is of little value to me personally (except for upgraded) as these forums are far more experienced and talented than anyone I have ever spoken to on the phone at NI. I will admit I do not call them much because most of what I do is not technically super complex
and works just fine.
So if its possible to get a licensed copy that works on a home PC I would buy it for myself, just to have something that works at home. But if NI starts limiting it to bare bones stuff, then it probably would not be worth the trouble to install it.
I could live with no application builder as long as the licensed copy was able to talk to Device drivers and hardware (in the LV environment of course)
04-13-2015 02:46 PM
@RTSLVU wrote:
Compare the requirements of an development system vurses the runtime
You need to be careful, for example the listed Pentium III does not support SSE2 and thus requires a special build flag to even run executables of newer LabVIEW versions.
(I still remember running LabVIEW executables on a 486SX (no floating point unit!) back in the days. Worked just fine. :D)
Instead of the application builder, it would be nice to include RT and FPGA for "home hardware" similar to the myRIO, for example. Embedded distributed computing is the future (and present!). Instead of buiding an executable you just deploy it to a RT target.