05-11-2007 02:46 AM - edited 05-11-2007 02:46 AM
Message Edited by ebalci on 05-11-2007 10:52 AM
05-14-2007 03:49 PM
C:\Program Files\National Instruments\NI-DAQ\Examples\DAQmx ANSI C
. If you have chosen to install support for Visual Studio you will get the native .NET DAQmx API. This will install by default, examples into:
C:\Program Files\National Instruments\MeasurementStudioVS200x\DotNET\Assemblies\Current with examples located in
C:\Program Files\National Instruments\MeasurementStudioVS200X\VCNET\Examples\DAQmx.
05-15-2007 01:29 AM
Hello Jennifer,
Thanks for the reply. This is the second time I get the suggestion to NOT to call each function separately from the dll. So I'll stick to it.
You wrote: "...Secondly, I am not sure where you have obtained the dlls that you attached in your post..."
Well, I remember downloading the .NET library dll from NI website (either a forum or an article).
I compiled the other dll (that I called in the C/C++ step) myself in CVI by following a thread in this forum. That's why its information does not say NI.
It is actually a "wrapper" of the nicaiu.dll in <system32> directory.
You open the NIDAQmx.h file, go to Options>Generate DLL Import Library in CVI, point to the nicaiu.dll file and compile a dll which is 'compatible' with TS. By compatible I mean that the functions and their parameters in the dll are recognized by TS in the Specify Module dialog box.
Now I think, I'll stop using the .NET dll that I have posted.
The wrapper library is missing some functions, I am aware of that. They are the ones with variable number of parameters. But the available ones are functional.
I am a CVI-person actually and I have no problems at all using the DAQmx C library. That was the point I started with, but then I was tempted to use TS whereever possible and reduce the coding. Now, as you pointed out, this may not be a good idea.
Thanks again Jennifer.