LabVIEW (including NXG) Base licence for home users - opinions please!

[Blokk]

We have LV Home Edition, which stuck at version 2014. Whenever I considered to purchase a LV licence for my personal use (hobby projects, keep my knowledge fresh, etc) in the past, the prices were not on a level which I could afford for such non-business usage. Except the "Base edition", but there was no Event driven programming feature included in this version, what was a game stopper for me!

However, I just realized very recently, that the recent LV and NXG Base versions now include Event driven programming (maybe this was true already in many of the previous versions? I remember back, around 2010, Base did not have Events). Considering the price, (~320 GBP per year), I would say it is even affordable for a hobby user...

Well, caveats are that, you do not get application builder, and object oriented programming with the Base version...

Opinions people? 🙂

link for comparison: http://www.ni.com/en-gb/shop/labview/select-edition.html

edit: another benefit of this licence, not to forget, is that you can access all the online trainings 24/7...We do not have such access with Home Edition.

[crossrulz]

---

@Blokk wrote:

Except the "Base edition", but there was no Event driven programming feature included in this version, what was a game stopper for me!

---

That changed in 2012.  So the LabVIEW Home and Base should have the Event Structure.

Home Edition now has the application builder, but your application will have the watermark on it.

Personally, for me just messing around at home, I would probably just go with the Home edition and supplement with the latest betas as they become available.

[Blokk]

Hmm, makes sense what you say...

And who knows, maybe in a couple of years, when the "business model" of NI let it, we get an update on the LV Home Edition...LV2017 would be nice as Home Edition 🙂 Channels, etc. Well, LINX is only compatible with LV2014, but it is not a problem to have LV2014+2017 on the same PC anyway...

[crossrulz]

---

@Blokk wrote:

And who knows, maybe in a couple of years, when the "business model" of NI let it, we get an update on the LV Home Edition...LV2017 would be nice as Home Edition 🙂

---

My guess is that we will see a new home edition with LabVIEW 2019 (5 years after the previous).

[Blokk]

---

@crossrulz wrote:

---

@Blokk wrote:

And who knows, maybe in a couple of years, when the "business model" of NI let it, we get an update on the LV Home Edition...LV2017 would be nice as Home Edition 🙂

---

My guess is that we will see a new home edition with LabVIEW 2019 (5 years after the previous).

---

That would be just great! I think the first official mention of Home Edition was at this post, in 2015: https://forums.ni.com/t5/LabVIEW/LabVIEW-Home-Edition/m-p/3117676/highlight/true#M894733

So maybe if NI releases a new Home Edition in 2019, we would get LV2018 SP1 as new Home Edition??

I guess if NI plans this for 2019, they must also update LINX under MakerHub, to be compatible with LV2018...if so, this upgrade work must be already ongoing at NI, anyone heard some non-official rumors related to this? 🙂

EDIT: and an interesting question, if this will happen, I wonder if the Home Edition will also contain NXG, like all the rest of other licenses...

[Hooovahh]

---

@Blokk wrote: 

I guess if NI plans this for 2019, they must also update LINX under MakerHub, to be compatible with LV2018...if so, this upgrade work must be already ongoing at NI, anyone heard some non-official rumors related to this? 🙂

---

I'd be nice if NXG was included in home.  That being said I've never bought or used home.

I think it was Sam that I talked to at NI Week last year about updating LINX.  He said that to get LINX with deploying capabilities for the Pi, and other microcontrollers, they needed to talk to another department about compiling something specific for them in the project explorer.  This is why it is only for 2014 since it had to be compiled for a specific version of LabVIEW.  Now that 2017 and newer versions have a forward compatibility feature, he seemed on board to the idea of updating the toolkit for some version 2017 or newer.  Since that would mean the work they needed to do could be moved forward from that version onward.