Multifunction DAQ

cancel
Showing results for 
Search instead for 
Did you mean: 

LabView 6.1 and Visual C

I am trying to figure out how to work with communicate between LabView and Visual C++. What software do I need? I have a DAQ card (6115). My compiler is VC++ 6. And my LabView version is 6.1.
0 Kudos
Message 1 of 6
(3,290 Views)
This is one hellofa open ended question. Lets see... You can communicate via:
activex
function calls (dlls)
tcp
datasocket
udp

What method you use depends on what kind of control or information you want to pass. You do not need any additional software other than the obvious--OS, and drivers. You can communicate to your daq card from both languages and the versions of your compilers (VC and LabVIEW) are new enough to have the capabilities you need.

You will need to explain your project in more detail so that a helpful and intellegent recommendation can be made. (what does it do and what kind of information do you want to pass).
0 Kudos
Message 2 of 6
(3,290 Views)
Thanks Jeremy.
I gotten a bit futher and was able to call NI-DAQ library functions from Visual C++.

I need some help in figuring out how to trigger both the DAC output and ADC input, i.e. if I want to create a series of short pulses, which will be fed into a black box, and I would like to measure the response of the the black box from this input. Is there a way to trigger both the ADC and DAC from one of the digital outputs? Basically I would like to measure the delay through the black box.

Also I would like to figure out how to use CVI library in Visual C++, is there any sample code available making use of the LabView/CVI library in Visual C++?

Thanks,

-frankie
0 Kudos
Message 3 of 6
(3,290 Views)
Frankie:

I am taking over this discussion because I support our DAQ products...

There is no way to use the LabVIEW or the Labwindows/CVI DAQ libraries in Visual C++. This is one of the advantages you get when using LabVIEW or CVI and they are not available outside of those ADEs... However, you can use the NI DAQ C++ Function Calls (nidaq.dll) in visual C++. There are quite a few examples that are installed with NI-DAQ for Visual C++ (ANSI C) that should get you started in the right direction.

Please refer to your DAQ subdirectory (usually located at C:\Program Files\National Instruments\NI-DAQ\). From ..\NI-DAQ\Examples\VisualC you sould be able to find a wealth of helpful examples including (under the AI folder) DAQsingleBufExtTri
g.C which acquires a finite number of points after an external trigger. As far as analog output with a start trigger, try (under the AO folder) WFMsingleBufExtTrig_Eseries.C. Your application would be a combination of these two examples...

If you don't have these examples in your NI-DAQ folder, please re-run the NI DAQ installation and make sure you add in text-based/visual C++ support.

Good Luck!

Sincerely,

Brooks B
Applications Engineer
National Instruments
0 Kudos
Message 4 of 6
(3,292 Views)

Hi ,Brooks B.
I'm having trouble using an example from Visual C++, AOonePointSample. I have DAQ card PCI6723and I am using Visual C++ 6.0I followed instructions to run Visual C++ programs in Visual C++. it can be compiled successfully,but getting running error

[AO_VWrite] returned NI-DAQ error-104041
The specified device is not a National Instruments product,the driver does not support the device (for example,the driver was released before the device was supported),or the device has not been cofigured using the Measurement & Automation Explorer.

I don't know,what is the problem. Can you suggest what I am doing wrong?

Thanks

0 Kudos
Message 5 of 6
(3,208 Views)


I'm having trouble using an example from Visual C++, AOonePointSample. I have DAQ card PCI6723and I am using Visual C++ 6.0I followed instructions to run Visual C++ programs in Visual C++. it can be compiled successfully,but getting running error

[AO_VWrite] returned NI-DAQ error-104041
The specified device is not a National Instruments product,the driver does not support the device (for example,the driver was released before the device was supported),or the device has not been cofigured using the Measurement & Automation Explorer.

I don't know,what is the problem. Can you suggest what I am doing wrong?

Thanks

0 Kudos
Message 6 of 6
(3,206 Views)