NI-DAQmx 8.0 and TDAQ 7.4.1 cannot co-exist

[dfousek]

Hi !

I am a developper using (mainly) the VB6 and the (traditional) NI-DAQ 6.9.3.
I downloaded and installed both NI-DAQmx 8.0 and TDAQ 7.4.1, so that I start shifting to NI-DAQmx (using the DAQmx ANSI C wrapper).
However, it seems that NI-DAQmx and TDAQ cannot co-exist on 2 PCs, I tried.

Both PCs were running Measurement Studio 6 and NI-DAQ 6.9.3. I uninstalled the last one, before installing NI-DAQmx (first) and TDAQ.
The PCs run US-WinXPsp2 (local:Greek), my devices were a PC-MIO-16E-1 and a PC-6602.

Running both the Test Panels in DAQmx and TDAQ, in NI-MAX is ok.

ALL the NI-DAQmx pre-installed examples at C:\Program Files\National Instruments\NI-DAQ\Examples\Visual Basic 6.0. work fine.

However, not even the pre-installed examples of the TRADITIONAL NI-DAQ work. They report a missing "nidaq32.dll" file, although it is there (in system32 dir of winXP). In my VB program the first call to Init_DA_Brds() returns a 8888 code !!!.

Of course, I reset devices every time I change NI-DAQ.

Can anybody tell what's going wrong ?

[McKala[DE]]

Hi!

I have not had any problems running the TDAQ example programs.  I am also using DAQmx 8.0 and T-DAQ 7.4.1 and VB6.  There may be something corrupt with your installation.  I recommend uninstalling and reinstalling the drivers.  Just to be sure that you have a clean install, you should download the latest drivers from the Drivers and Updates page.

Let me know if you are still having problems!
Micaela

[dfousek]

Hi Michaela !

The ZIP format of the downloaded files guarantees that are OK. After all, I did it at  two different PCs.

Probably, the main difference in your installation, is that you haven't installed the Measurement Studio 6 (+updater)...

I suspect that this causes the problem....

Dimitri

[McKala[DE]]

This KB talks about the nidaq32.dll file not found error. 

Let me know if that doesn't fix the problem.

[dfousek]

Hi Michaela !

Yes,  the  palBase -b 64000000 -s 44000000 command resolved the problem in both PCs.

I just note that the KB article begins saying that "The recommended solution is to migrate to the new NI-DAQmx 7.x driver where this issue has been fixed".

Now, should I worry about the NI-DAQ performance ? .... and if yes for the NI-DAQmx or the Traditional NI-DAQ or both ?

Dimitri

[McKala[DE]]

Hi Dimitri,

There are specific use cases for the Traditional NI-DAQ driver; however, the Traditional NI-DAQ driver is not as reliable as the NI-DAQmx driver.  The Answers to Frequently Asked Questions abut NI-DAQmx and Traditional NI-DAQ explains the use cases and differences between the two drivers.

I highly recommend developing for the NI-DAQmx driver and only using the Traditional NI-DAQ driver when necessary.

Regards.