LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Upgrade LabVIEW

I have LabVIEW licensed version 2013.Now I have to update it to 2019 version.Is it free upgradation or we need to buy new license.

And What is procedure for upgrading the  LabVIEW 2013 to LabVIEW 2019?

0 Kudos
Message 1 of 5
(4,818 Views)

Hi avana,

 

call your local NI sales rep for any license issues.

 

That being said:

Your LabVIEW2013 license is valid for LabVIEW2013, but not for LabVIEW2019.

(UNLESS you have an (still active) support contract, which delivers updates twice a year.)

 


@avana2006 wrote:

And What is procedure for upgrading the  LabVIEW 2013 to LabVIEW 2019?


You can install LabVIEW2019 in parallel with LabVIEW2013, BUT any drivers (like DAQmx) will only be available for the LabVIEW2019. Such drivers only support the current version and 3 versions before, so DAQmx will support LV2019 down to LV2016.

Use a new computer or a VM to separate your LabVIEW versions.

I guess you already use a SCC tool to keep a history of your code base?

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
Message 2 of 5
(4,805 Views)

I would be hesitant installing multiple versions on the same, let's say, image.  I had installed 2018 and all it's stuff, but had projects in 2015 that needed to be built in 2015.  None of them worked anymore.  When I went to deploy, just crashed each and every time.  I assumed maybe there was a Run Time Engine issue, so I created an installation package that would use latest drivers.  Still didn't work.

 

So like GerdW said, use VMs for all different versions of LabVIEW.  The big issue here, of course, is disk space.

Message 3 of 5
(4,649 Views)

@DailyDose wrote:

I would be hesitant installing multiple versions on the same, let's say, image.  I had installed 2018 and all it's stuff, but had projects in 2015 that needed to be built in 2015.  None of them worked anymore.  When I went to deploy, just crashed each and every time.  I assumed maybe there was a Run Time Engine issue, so I created an installation package that would use latest drivers.  Still didn't work.

 

So like GerdW said, use VMs for all different versions of LabVIEW.  The big issue here, of course, is disk space.


I believe that you will probably be okay installing anything from LV 8.x to LV 2016 alongside each other - while observing the aforementioned driver issue - or anything from LV 2017 up to the latest alongside each other, but if you cross that boundary - as you did - with having LV 2015 alongside LV 2018 - that's where you will have issues.  I think it corresponds to the introduction of NIPM.  Probably Bob would know better.

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.
0 Kudos
Message 4 of 5
(4,618 Views)

@DailyDose wrote:

I would be hesitant installing multiple versions on the same, let's say, image.  I had installed 2018 and all it's stuff, but had projects in 2015 that needed to be built in 2015.  None of them worked anymore.  When I went to deploy, just crashed each and every time.  I assumed maybe there was a Run Time Engine issue, so I created an installation package that would use latest drivers.  Still didn't work.

 

So like GerdW said, use VMs for all different versions of LabVIEW.  The big issue here, of course, is disk space.


That's generally not a problem. That being said, there's been history of problems when installing older versions after, so in your case i'd uninstall both, then install 2015, 2018 and DAQmx.

On my old laptop i have 2010, 2011, 2014 and 2016 (with DAQmx for 2014, the last version is only for pure software, no hardware) on my main install and then 2017 and NXG on separate VMs.

I've just got a new Laptop that will pick up from 2020 and if it needs older i'll use VMs for those.

/Y

 

G# - Award winning reference based OOP for LV, for free! - Qestit VIPM GitHub

Qestit Systems
Certified-LabVIEW-Developer
0 Kudos
Message 5 of 5
(4,362 Views)