LV7.1 and LV2009 on same PC

[MogaRaghu]

I now have LV7.1, LV8.0 and LV 2009 loaded on my notebook.

However when I try to open a VI done in LV7.1 which has plenty of DAQMX functions, I am totally stuck. When I loaded LV2009, the version of DAQMX that loaded was 8.9 and now LV7.1 finds it impossible to handle these new functions.

Also I am now unable to load DAQMX 8.01 ( since I have a newer version ) which was used when developing with the LV7.1.

Can not two different versions of DAQMX drivers co-exist on  the same PC without conflicts ??

[Ray.R]

Although multiple versions of LabVIEW can co-exist, I am not sure that the same is true for DAQmx drivers...

I didn't read the compatibility issues with 8.1  http://joule.ni.com/nidu/cds/view/p/id/319/lang/en 

Hopefully Dennis will see this thread and provide more advice..  😉 

Here is what it says for DAQmx 8.1:   It mentions support for LV8.  I would suspect that it should be okay for LV7x. 

"

NI-DAQmx 8.1 is the latest measurement services software for your data acquisition and signal conditioning devices. NI-DAQmx 8.1 contains support for:

• NI CompactDAQ chassis and C Series I/O module support — NI cDAQ-9172
• M Series USB — NI USB-6251 and NI USB-6259
• NI PCI-6154, NI 6230, NI 6255, NI SCXI-1502, and NI SCXI-1503
• Additional NI-DAQmx installer types -- Create installers that bundle various sizes of NI-DAQmx.
• New S Series feature—Tasks can now contain channels from multiple S Series devices.
• Support for LabVIEW 8 -- LabVIEW Project, Shared Variable, etc..
• Human-readable configuration import/export from MAX for NI-DAQmx configuration data.
• Usability improvements and features enhancements to DAQ Assistant.
• LabVIEW support for synchronous and asynchronous DAQ events.
• Querying of DAQ device capabilities including available physical channels and bus type.

For more information on NI-DAQmx features and benefits, click here. For more information on what is new in NI-DAQmx 8.1, refer to the NI-DAQ Readme, accessible from Start>>Programs>>National Instruments>>NI-DAQ after you install NI-DAQmx as described below.

National Instruments supports the latest version of NI-DAQmx for Windows driver software for application development with NI LabVIEW, LabWindows/CVI, and Measurement Studio 7.x or later on Windows 2000/XP. "

[Dennis_Knutson · Accepted solution]

NI dropped support for LabVIEW 7.1 a couple of DAQmx versions ago. The latest does not support 8.0 either. You can only have a single version of DAQmx installed at a time so you only have a few options. One is to use a separate pc for each version. Another is to use a VM on your pc for each version. Another is to convert all of your 7.1/8.0 VIs to LabVIEW 2009.

[smercurio_fc]

Is this purely for development? If so, I wonder if simply copying the DAQmx VIs from the older DAQmx version into the LabVIEW 7.1 folder would be sufficient just to be able to open the code. You couldn't run it, obiviously, but it might be enough just to code it. I've never tried this, and I don't even know if it would even work.

[JÞB]

---

smercurio_fc wrote:
Is this purely for development? If so, I wonder if simply copying the DAQmx VIs from the older DAQmx version into the LabVIEW 7.1 folder would be sufficient just to be able to open the code. You couldn't run it, obiviously, but it might be enough just to code it. I've never tried this, and I don't even know if it would even work.

---

Hey it DOES work for development- I haven't tried yet but I think you can even build an app in this manner.  DO overwrite the DAQ library.  DO NOT have two daqmx libraries unless you a a master of configuring search paths.  (Hint:) if all DAQmx functions are called dynamicly in the project you just "Might" get away with debugging too--- (hmmmm... maybe COOL maybe KOOL-AID):smileysurprised:

Regardless- this is not an ideal way to develope code!  just a possible work-around if you are in a real bind and have to do it.

[JÞB]

Before I start getting slaughter by the respected posters over this I want to clarify!

In No Way Whatsoever am I suggesting that this would work well

---

Jeff Bohrer wrote:

---

smercurio_fc wrote:
Is this purely for development? If so, I wonder if simply copying the DAQmx VIs from the older DAQmx version into the LabVIEW 7.1 folder would be sufficient just to be able to open the code. You couldn't run it, obiviously, but it might be enough just to code it. I've never tried this, and I don't even know if it would even work.

---

Hey it DOES work for development- I haven't tried yet but I think you can even build an app in this manner.  DO overwrite the DAQ library.  DO NOT have two daqmx libraries unless you a a master of configuring search paths.  (Hint:) if all DAQmx functions are called dynamicly in the project you just "Might" get away with debugging too--- (hmmmm... maybe COOL maybe KOOL-AID):smileysurprised:

Regardless- this is not an ideal way to develope code!  just a possible work-around if you are in a real bind and have to do it.

---

After some reflection I want to assure you that I could find much better ways to force myself to write overly complicated code with problematic (at best) maintainability if I so desired 

In the situation the OP presented I would have to argue for a second development machine that has suitable drivers on it to develop 7.1 applications.  And a great SCC archetecture that clearly partitions source code by version!  This is the approach I have found the least objectionable especially for my LabVIEW 6.1 / TestStand 2.0 clients. 

In summary: the approach of using one machine withadulterated vi.lib for old versions is potentially problematic (What Flavor IS the Kool-aid ? )

[MogaRaghu]

Hi Dennis,

Thanks for clarifying. Looks like my worst fears have become true.

Of all the options that you mentioned, converting all earlier projects to LV2009 seems to be the safe bet in the long run. ( quite painful though )

But I am curious how an EXE  built with LV7.1 runs on my notebook ( that has DAQmx 8.9) without any complaints ?? Maybe its simply because the DAQmx run time is backward compatible ?