the vb NiDaqMx tutorial,how does the program get its input from the DAQ?

[bonosA]

This is indeed unfortunate. THe existing code is running with the Traditional NiDAQ driver and since they will be using it till mine is done, I am forced to use the traditional driver so I can keep testing it as I go along

THere is a lot of sample code in this folder I installed and the names arent descriptive for the projects. Could you please let me know which projects I should look at to read a set of voltages off a DAQ board?

thanks,

Saroj

[bonosA]

Hi Tom,,

Is there ANY way I can develop my program in DAQMx even though I dont have a DAQ board to test with? BAsically I would want to develop here at my desk with somehow debugging as I go along, so that when I finally take my app over to the lab, and install DAQMx for them, my program will run and they can retire their old program?

In other words, is it possible to develop my program without having a DAQ board to test it with:?

Rather dismayed at the ugly mess in the traditional DAQ examples folder,

Saroj

[bonosA]

Hi Tom,

This is my third question:

The functions being used in the legacy app are

Get_DAQ_DeviceT_Info, DAQ_config etc.
Are these functions in the 6.8.1 NiDAQ driver?

The functions in 7.4 are quite different.

Since I cannot break their exisiting app, does this mean I have to program in 6.8.1?

Are there any pitfalls to using such an old driver?

thanks,

saroj

[bonosA]

Question 4

Can we program in VB using 6.8.1?

THeir legacy app is in C++, and they want it now rewritten in VB, but I'll probably have to use their old 6.8.1 driver

[bonosA]

Ok. Tom,

Good news!

They had a spare PCIMIO16XE-10 board on a pc which I can use as my testbed,. So I am back to using NIDAQMx 7.5!

I will be taking some sample code over in 10 minutes to see if we can communicate with the board. I'm sure I will be back with questions.

Thanks for all the help, and at least now we have an easier road to hoe.

Saroj

[Tom_W_[DE]]

Hi Saroj-

Glad to hear you can continue working with NI-DAQmx.  There are certainly issues with working with the old 6.8 version of Traditional (Legacy) NI-DAQ; it runs more slowly, is not multi-thread safe, and it does not support any of the newer boards that you are likely to be working with.  If you are switching development platforms then this is a great opportunity to switch your driver API as well so that the application will be more portable and easily-maintained in the future.

Please let me know if you have any more questions.  To address one of your other questions, you can develop for NI-DAQmx using NI-DAQmx Simulated Devices.  These can be very helpful for developing without the hardware actually being present.

Hopefully this helps-

[bonosA]

"If you are switching development platforms then this is a great opportunity to switch your driver API as well so that the application will be more portable and easily-maintained in the future."

Hi Tom,

what do you mean by this? I think its XP, using a PCI MIO 16XE-10 board and I installed NIDAQ 7.5 as recommended by someone at NI.

Do you mean that I should use NIDAQ 8.0? Are they backward compatible (8.0 and 7.5?)

Thanks so much for the link to simulated  devices!

Saroj

[Tom_W_[DE]]

Hi Saroj-

Yes, each version of NI-DAQmx is completely backwards-compatible with all prior versions.  Obviously, NI-DAQmx is not backwards-compatible with Traditional (Legacy) NI-DAQ;  that's what I meant by my comment.

There are few significant differences for text-based development between NI-DAQmx 7.5 and 8.0, but it's always a good idea to keep your driver version up-to-date because newer versions often address bugfixes for previous versions.  In case you would like to update, NI-DAQmx is a free download from ni.com

Thanks and good luck with your app-

[bonosA]

Hi Tom,

I simulated a PCIMIO16X-E10 in mAX. I ran AcqIntClick (the VB 6 example in the folder). I get erroir -50103 specified resource is reserved. I had before this tested the CWGraph on another project and created a task in MAX to test it. I deleted that task now just in case. Please jhelp!
saroj

[Tom_W_[DE]]

Hi saroj-

I just simulated the same device and ran the example without a problem.  I would suggest that you verify you are using the correct device number.  Simulated devices appear with a yellow glyph (rather than green) in MAX next to the device name.  Is it possible you are entering a physical device instead of the simulated one?  What happens when you try to run the test panels for the simulated device in MAX?

Thanks-