LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Labview2009 and Traditional NI-DAQ

Solved!
Go to solution

Hello NI Friends!

 

I'm running LV2009 on a 32bit win7 machine with a PCI-MIO-16E-1 DAQ board.  We have a program to calibrate pressure transducers, but it was written with the Traditional NI-DAQ.  I plan on writing a new program to do the calibrations, but until then I'd like to use the old one. 

 

I see that some DAQ devices can support both drivers, including the device I mentioned above (http://download.ni.com/support/softlib//multifunction_daq/nidaqmx/7.4/readme.html).  I also found the location to download the Traditional NI-DAQ driver for 32bit Win7 (http://digital.ni.com/public.nsf/allkb/8EC9E81C3DE4E619862573930083BD7A).  Based on the information I have so far, it sounds like it will work.

 

However, I remember seeing something that said if I install a different driver, the current one will be overwritten (I can't find the original source).  I also came across this warning: "NI recommends not installing NI-DAQmx on the same machine as the Traditional NI-DAQ (Legacy) beta driver." (http://digital.ni.com/public.nsf/allkb/8EC9E81C3DE4E619862573930083BD7A)

 

I am not interested in screwing up this machine since I'm not the only person who uses it.  I don't have enough NI experience to make the call without first checking with those who do here on the forum.

 

Thanks for the help.

 

Darren

0 Kudos
Message 1 of 5
(2,560 Views)

anyone?

I have had them both on a labview 8.6 machine but that was a long  time ago and things have probably changed alot

Please remember to accept any solutions and give kudos, Thanks


LV 8.6.1, LV2010,LV2011SP1, FPGA, Win7
Message 2 of 5
(2,539 Views)

Hi,

 

You can find some information here:

http://digital.ni.com/public.nsf/allkb/8EC9E81C3DE4E619862573930083BD7A

 

But the best solution is to rewrite your program with DAQmax.

 

Regards,

 

Yoann

Message 3 of 5
(2,521 Views)
Solution
Accepted by topic author dZack

You have a deployment problem.

 

my strong recommendation would be to not change drivers on the machine that is working and develop your replacement code on new hardware.

 

Yes, you could get away with developing a new solution on a working machine but, that is almost garunteed to cause some conflict somewhere with some driver.  Unless you know everything everyone does with that functioning system AND you really understand NI Device drivers and what exactly changes where and in what version,  you are asking for a few "Learning experiences" by developing on a functionally necessary system.


"Should be" isn't "Is" -Jay
Message 4 of 5
(2,510 Views)

Thanks for the thorough responses.

0 Kudos
Message 5 of 5
(2,501 Views)