Install LV2013 and LV2017 with drivers and a toolkit

[EDGAR_PLATRONICS]

Hello:

I need to replace my development PC and I have problems with LV installation

I need LV2013, LV2017 cDAQmx for each one and Sound and vibration toolkit

I followed next order:

LV2013, cDAQmx 2013, SVT, LV2017, cDAQmx 2017, SVT.

Everything works fine but SVT does not install in LV2017 because NI meas & automation already installed.

Which sequence it is recommended in this case?

Regards

Edgar

[RavensFan]

There is no such thing as "cDAQmx".

You cannot install DAQmx for both LabVIEW 2013 and 2017 as there is no version that supports both versions of LabVIEW.

See https://www.ni.com/en/support/documentation/compatibility/16/ni-daqmx-and-labview-compatibility.html

The first version to support LabVIEW 17 is DAQmx 17.0

The last version to support LabVIEW 13 is DAQmx 16.1

I don't know how Sound and Vibration Toolkit would be affected by Measurement and Automation Explorer.

You need two different PC's to support each version in its entirety.  Or as some people do, 2 virtual machines on the same PC.

[EDGAR_PLATRONICS]

Thank you for your answer. I will consider 2 PC's or 2 virtual machines but it is some complicated for my development.

Regards

[Bob_Schor]

The recommended sequence is as follows:

• Install "oldest first".  [There is an interesting "exception to this rule", but please, let's not go there].
• Install all of a Version before installing the next Version (sometimes this rule can also be relaxed).
• Install LabVIEW first (with or without VIPM -- I recommend "with").  Reboot (for maximum safety).
• Install LabVIEW Real-Time (if you need it) next.  Reboot.
• Install any Modules and Toolkits that you need (such as SVT).  Reboot.
• Install all Device Drivers that you need (and only those that you need).

It is usually the case that there is a 4-5 year "compatibility window" with Versions and Device Drivers.  I would expect that if you installed LabVIEW 2013, you'd (probably) get away with installing LabVIEW 2017 next, and both would work, but the other response (suggesting this is not the case) might also be true.

I forgot to mention that before doing a new LabVIEW Installation, you want to do a complete removal of all NI Software.  Start with Programs and Features, find NI Software, and choose Remove All.  This may take > 1 hour, so be patient.  If you are unfortunate enough to also have NIPM installed, you also want to get rid of this.  After you reboot and see no more NI Software in Programs and Features, you can try to uninstall NIPM.  You should get a warning "Are you sure?" -- if you've really uninstalled all other NI Software, you can (and should) say "Yes".  If you are unsure about this last step, come back here and ask for help -- you don't want to do a complete reinstall of Windows XX and all your other software on your PC!

Once NIPM is gone, you might find that there are still some NI Products on your machine (I think this might only happen with versions of LabVIEW more recent than 2017, but am not sure) -- go ahead and uninstall them.

Bob Schor

[EDGAR_PLATRONICS]

Thank you very much for your detail answer. I will try it.

[rwunderl]

Bob is absolutely right that you always need to install from the oldest to the newest when it comes to LabVIEW. That includes drivers for sure, but many toolkits as well.

As RavensFan pointed out, common LabVIEW components generally only supports up to 3 years back. This means that having any two versions of LabVIEW on a single computer (or single virtual machine) that are more than 3 years apart is asking for trouble (read: failure). Support for core things like DAQmx is actually removed from LabVIEW versions older than that which the latest installed version supports. On the flip side, if you install the newest one first, you run into the issue of it saying it is already installed (and it won't add support for older versions).

This 3-year logic also applies to upgrading your LabVIEW applications. Always upgrade in steps of 3 years or less (whenever possible) if you need to be able to quickly roll back deployed code. Otherwise, you'll find yourself wiping the computer and starting again (which is sometimes preferred to uninstalling).

[Bob_Schor]

---

@rwunderl wrote:

Otherwise, you'll find yourself wiping the computer and starting again (which is sometimes preferred to uninstalling).

---

In my experience, I would change the above sentence to "... and starting again {which is almost always preferable to uninstalling, which 95% of the time doesn't work, so you end up removing everything anyway)".  [Hmm -- he said "wiping the computer" -- the only time I had to actually do that was because I tried to "uninstall" and "remove from the registry" (hint -- don't do this!!).

Bob Schor

[rwunderl]

I do mean wiping, as in formatting the drive and starting over. It is also of great value when deploying to multiple computers to have recovery images of the drive just before and/or just after installing LabVIEW for just such occasions. Storage is cheap, your time is not.

---

@Bob_Schor wrote:

... because I tried to "uninstall" and "remove from the registry"

---

Indeed, no good can come of typing "regedit" while attempting to uninstall an application...

[EDGAR_PLATRONICS]

Thank all you guys for your help