LV driver+compatibility problem

[ussr123]

Hi everyone,

I am facing the same problem already for a while. I am working with different measurement devices from Tektronix, Agilent, etc. I download each time the corresponding LV drivers, I build up complicated VIs and if I try to run them couple of years later on a newer version of LV, they are crashing. It needs a lot of work and time to recover the VIs...

What is the best solution to save some time when doing this? How/what/where to save exactly? Could not I prevent somehow their crashing?

Thanks,

Ussr123

[GerdW]

Hi Ussr,

I never had any "crashes" when upgrading LV versions…

What drivers are you talking about?

Which functions do they use?

What kind of crashes do you experience? BSOD? Or Windows error messages? Or LabVIEW error messages?

[ussr123]

Hi,

Simply all the LV subVI-s that are from that library (for ex library for an oscilloscope) are not recognized. When opening the VI, it asks me couple of times, to tell the exact location of the subVIs.  

How to save today a project (which uses icons from a certain library) so that if I want to open it for ex. a year later, I'll be able to do that.

Lets suppose I have the old library... where to save it in order to not be asked by LabVIEW: where are the necessary subVIs?

Or can it be possible that the new version of LabVIEW won't recognize my old library icons?

Thanks,

Ussr123   

[GerdW · Accepted solution]

Hi Ussr,

those "libraries" (probably from NI.com/IDNet) are usually installed into "LV xxx\instr.lib" folder (with xxx being your LV version).

When you install a new LabVIEW version you need to either reinstall that library for the new LV version or to copy them from the older version to the new one.

Those hassles you describe here are one of the reasons I keep all my project related VIs (including several instrument drivers) in my own "user library", but not in "LV xxx\user.lib". This makes it much easier to maintain VIs for several LV versions (in my opinion)…