Using traditional NI-DAQ & NI-DAQmx in the same application

[JoeSavage]

Hi Steve, I have still been unable to reproduce the problem you are seeing (though I have heard reports of others seeing it too, so I don't believe it is just an isolated incident). Can you post a VI that reliably reproduces the problem? That would greatly help us to track down the cause. Also, please report the computer type and which operating system (and service pack level) you are running on, in case this is a problem that is specific to certain types of computers and/or OSs.

Thanks,
Joe

P.S. When you get a chance, can you also post the exact error codes you alluded to in your earlier post?

[Sasmar]

Hi Joe,
I have all the details you asked for, I just can't see how to post a VI to this forum! Please advise. Thanks.

Steve

[JoeSavage]

When you are about to post, look towards the bottom of the page, above the "reply to" section. There is an "attachment" field with a browse button.

[Sasmar]

Hi Joe,
1. BTW, thanks for the posting directions.
2. The VI to be posted is Traditional DAQ_Reset_Plus DAQmx.vi. It is from the traditional DAQ example directory with added code for Device Reset that produces the lockup problem.
3. The VI locks up after acquisition inside the device reset. Notice the number of channels is important to produce the problem. Lockup occurs when acquiring data with multiple channels. Lockup does not occur when acquiring data with a single channel.
4. The goal is to reset daq card after performing data acquisition with the traditional daq and prior to proceeding with another data acquisition using daqmx.
5. Hardware description: Dell Pentium Mobile 1.2Mhz, Usoft Win2000 & SP4, DaqCard-6062E.
6. The error code (10041) is no longer relevant to this problem. The error was due to using DI/O Clear.vi after DI/O R/W in the application that I’m using. This is no longer a problem. If you are still interested why: per NI “You will get error -10041 if you call DIO Clear without calling DIO Buffer Config. DIO Buffer Config is called by DIO Config, which should only be included for buffered digital operations. Immediate DIO VI's, such as Write/Read to Digital Line or Write/Read to Digital Port, do not require DIO Buffer Config. Therefore, calling DIO Clear without first calling DIO Config results in error -10041. To prevent this error from occuring, do not include DIO Clear with immediate DIO VIs.”

Thanks.

Steve