New to NI-DAQmx? Check out the new Getting Started with NI-DAQmx Series!

[nasrul]

Thanks Nick, I've tried it with another PC using Windows XP and it works. But since I don't think I would want to switch to XP (yet) , I still wanna have a try. I tried you suggestion on going to the Device Manager and Update Driver. It still doesn't work. Actually the PC do detect the DAQ card but I think the main problem here is that the MAX doesn't have "NI-DAQmx" under Devices and Interfaces and it put the DAQ Card under PXI System. When you said "rename the data folder" does it mena that I have to Rename the folder to other name. I've tried this but it won't allow me to rename the folder. Looking forward for reply again .. Regards nasrul

[ASTDan]

Hello,

Is there a .pdf manual for Daqmx?  I am trying to find a 300+ page .pdf manual for DAQmx.  Is all the available daqmx documentation in the help file?  Is there any more?

Thanks

Dan

[Robert_F]

Hello Dan,

There is no DAQmx manual.  However, there are several documents on how to program in DAQmx.  When you install the DAQmx driver, several help files will be installed on your hard drive.  (Start >> All Programs >> National Instruments >> NI-DAQ)  Here are a few documents that might help you understand how to use DAQmx.  The examples are also a great resource.  (Help >> Find Examples >> Hardware Input and Output >> DAQmx)

M-Series Manual

Learn 10 Functions in NI-DAQmx and Handle 80 Percent of Your Data Acquisition Applications

[Rafo]

Hello,

I am trying to install NI-DAQ for NI 9233 but it does not work. I have labview 8.0 and windows Vista. Labview 8 works good until now in this windows, so the problem is with windows, with labview?. I can not install the software NI-DAQ 8.5 or 8.6 because  appear this message:

Unsupported version of National Instruments system component detected

Unsupported version of NI-VISA detected

Unsupported version of NI PXI Platform Services detected

Unsupported version of NI-DAQmx detected

Does anybody know what can I do???????????????

[Tom_W_[DE]]

See reply to Rafo's question here.

[Merlin-3]

A serious stuff....
We bought recently 3 x 6023E boards.
In the boxes and CDs, there was no Tradtional anymore. Only the NiDAQMx cds.
We installed the 7.4x Traditional to use with our product as usual (more than 6 years)  and.... a bad surprise: only one of the boards worked with the Traditional. The other two did NOT work.

Did NI change something in the 6023E hardware???????? to make it work only with the NiDAQMx??????

Thanks,
LMP

[ASTDan]

NI is phasing out Traditional DAQ.  What I do with my customers who have code using traditional daq is I don't update their drivers.  You can download for free previous versions of drivers.  I would recomend downloading the version of traditional DAQ you are familer with.  I have very old DAQ drivers working with newer versions of LabVIEW

Another more painfull option is to refactor your code using  DAQmx.

https://www.ni.com/en/support/downloads/drivers/download.ni-daq-mx.html

Hope that helps

Dan

[Merlin-3]

// Another more painfull option is to refactor your code using  DAQmx.

Yes, it has been done, unfortunately we HAD to do it, as it is written in the msg board: Where are nidaqmx low level functions? - Multifunction DAQ

// NI is phasing out Traditional DAQ.  What I do with my customers who have code using traditional daq is I don't update their drivers. 

So, you are saying that nothing changed in the E series hardware boards, but the most recent Traditional drivers (7.4.4) can do weird things and we should trust only on the older ones (6.9.3) ? 😉

// You can download for free previous versions of drivers.  I would recomend downloading the version of traditional DAQ you are familer with.

Yes, that's wise. To not change what is working.

But don't you think weird if, among 3 x 6023E boards bought, one works with Traditional 7.4.x and other 2 do not?

Thanks,

LMP

[Merlin-3]

I need to fix one thing I wrote:

> But don't you think weird if, among 3 x 6023E boards bought, one works with Traditional 7.4.x and other 2 do not?

After my partner returned from the field installation, I checked what did happen and this was exaclty:

We always have installed the Traditional 6.9.3 with our product, to not change what is working fine.

BUT... among the last three 6023E boards we bought, only one worked with the Trad. 6.9.3. The others two did not, only with the 7.4.x.

And with the 7.4.x, although for MAX it was "working", with our product it was unstable, doing weird things we had a bad time trying to discover what was going on, if it was a problem in our product or something with the NI board and the 7.4.x driver.

I do not see any benefit for NI clients if NI changes things this way.

LMP

[Matt_A]

Hello LMP,

There has been no substantive hardware change to the NI 6023E that would cause it to be incompatible with Traditional NI-DAQ (Legacy) version 7.4.4. In fact, if you look at the Data Acquisition (DAQ) Installation/Configuration Troubleshooter, you will see that Traditional NI-DAQ (Legacy) 7.4.4 is the recommended version to run with the PCI-6023E.

It is possible (but unlikely) that you were shipped malfunctioning devices or that they were damaged during shipping. I would recommend that you use the E Series Diagnostic Utility to confirm the behavior of the devices. What exactly do you mean when you say that the "among the last three 6023E boards we bought, only one worked with the Trad. 6.9.3. The others two did not, only with the 7.4.x."? I do not understand what you mean by "did not [work]"? Perhaps, running the diagnostic utility would help provide more insight into the behavior of the devices. You may also want to provide some details about how the devices fail. You mention "with our product it was unstable, doing weird things", could you provide more details about this behavior? Is it an issue with analog channels? Digital channels? Acquisition or generation? What are the "weird things"?

I agree with you that it would be of no benefit to you or us to make a change such that the device was not backwards compatible with the older version of the same driver, so the behavior you describe seems very strange. Hopefully the results of these tests will determine the cause of the issue.