My short answer so far (after days of testing) is: NO - (Though, I would be extremely glad if I am proven wrong on this!)
Here is the setup:
I am using PCI 6022 and PCI 6034E boards on (Dell Optiplex 960) computers that worked fine under Windows XP. Because of a system wide upgrade we switched to Windows 7 64bit. Since there are currently no traditional DAQ drivers for Windows 64 bit, I reinstalled the machines with Windows 7 32 bit to install the Traditional (Beta) DAQ V7.5 for VISTA. I have tried many different approaches (see below) installing LabView and CVI but in each case have not been able to communicate with the cards using the most simple of traditional CVI functions, such as Init_DA_Brds, which always result in a error -10005 meaning the device could not be found or that the device is not a NI device. Note: the device shows up fine the Measurement and Automation Explorer (MAX) as NIDAQmx device and tests fine in the self test.
Here are the various failed approaches that I tried – in each case I start with a completely newly formatted HD and reinstalled Windows 7 32 bit OS:
1)
a) Install LabView Core (LabView 2010 32bit V10.0) with NI-Drivers enabled;
b) install LabWindows/CVI2009 (V 9.1.1 (450).) Card shows up in MAX but only as NIDAQmx. In CVI, both the traditional and DAQmx libraries are grayed out and cannot be located on the disk.
c) To solve this issue, I was told to install an updated device driver NI-DAQmx 9.2.1, found here http://joule.ni.com/nidu/cds/view/p/id/2174/lang/en. (Note: I was wondering if that’s a 64bit or 32 bit driver?) Finally, NI-DAQmx library functions show up in CVI. (I didn’t test them since I am only interested in traditional DAQ though.)
d) Next, I install the Traditional DAQ V7.5 for Vista, and the Traditional DAQ functions (Easy IO and Traditional NI-DAQ Libraries) appear in CVI.
Result: When trying to use them, it compiles but at runtime it results in “device not found” fatal error message. (Of course, when you try to program in the traditional DAQ library, for most of the DAQ function calls, the first argument is the board number – since the board does not show up as a traditional device in MAX this actual value is only a guess (since it’s the only board I assumed from the past it is “1” but I have tried numerous other guesses with no avail.)
2)
a) Install LabView Core (LabView 2010 32bit V10.0) without NI-Drivers enabled.
b) Install the Traditional DAQ V7.5. Card shows up in MAX only as a traditional NIDAQ.
c) Install LabWindows/CVI2009 (V 9.1.1 (450).) In CVI but both the traditional and DAQmx libraries are grayed out and cannot be located on the disk.
d) To solve this issue install an updated device driver NI-DAQmx 9.2.1 Finally, NI-DAQmx and traditional library functions show up in CVI but MAX only shows now a NI-DAQmx device.
Result: same as in 1.
3) Steps a, b, c same as in approach 2 but then tried copying all the traditional DAQ library files one by one from a machine that was installed with approach 1. Sorry, got tired of that but I think that might be the only way.
Conclusion: First, yes I have been warned about the future support of traditional DAQ. Having said that, my gut feeling, and that’s all it is at this point, is that my problem has something to do with the 9.2.1. NI-DAQmx driver because it refuses to display the traditional DAQ devices and, therefore, I speculate here, will not “bind” the traditional devices with their traditional library. I tried re-installing the version 7.5 DAQ Beta driver (in approach 1 or 2) to overwrite NI-DAQmx but it does not allow me to do this for MAX since the 9.2.1. files are obviously newer.
Thanks for any help on this.
