01-23-2023 08:54 AM
I have been running Labview home 2014 on two machines for a near continuous astronomy project since 2018. I now have to upgrade my machines to windows 10. I have reinstalled Labview home 2014 from files but previously it had updated to 2017 and all my VI's use the NI 2017 MODBUS library.
Is there a way to make Labview update to 2017 again? I have two files in a folder called LabView 2017/resource/Framework/providers, files called mxwProjectProvider, a max configuration UI (121kb) and mxwProjectProvider.mxxlic (1kb) what might they be? I dont want to go through the hassle of replacing all the NI modbus vis with Plasmionique ones as I had a few problems with them previously.
01-23-2023 09:22 AM - edited 01-23-2023 09:22 AM
LabVIEW Home edition has been discontinued and replaced with LabVIEW Community Edition
01-23-2023 03:19 PM - edited 01-23-2023 03:20 PM
Yes, but has to be renewed each year and will I be able to rely on NI to continue to provide it? also I have three copies of home in use which I paid for - will I be able to download and use three copies of Labview community?
01-23-2023 03:32 PM - edited 01-23-2023 03:33 PM
@EdHarris wrote:
Yes, but has to be renewed each year and will I be able to rely on NI to continue to provide it? also I have three copies of home in use which I paid for - will I be able to download and use three copies of Labview community?
Well that's a question for NI but...
Why did you buy three copies? Before NI went to a subscription model, as long as you were only using one development copy at a time you could install a single LabView licence on multiple computers.
You didn't buy another full licence for every deployment target computer did you?
01-23-2023 04:48 PM
Yes the Home bundle was only licensed for use on one computer. At a low cost