LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

nidaq32.dll error using Windows 7

1. When I first started learning DAQmx to use an M-series board, I remember that ni had some kind of toolkit available to help with the transition from traditional NI-DAQ to DAQmx.  I never actually used it, deciding to take the (eventually) inevitable plunge.

   As I recall, the toolkit was supposed to give you a bunch of wrapper vi's that would look & feel like traditional NI-DAQ function calls, but which would do all the actual interaction with the hardware via DAQmx under the hood.

   I *think* I was still running Win 2000 at the time.  I dunno if it's still buried on the ni site somewhere, and even if it is, I wouldn't be at all sure that it'd still work under Win 7.

 

2. As to the conversion process, you really need to start with at least 1 of the following 2 kinds of detailed knowledge:

- either a thorough understanding of the functional behavior of the old traditional NI-DAQ tasks

- or a thorough knowledge of traditional NI-DAQ so you can decipher the task behavior from the code and the config inputs

 

You can't really implement the same behavior in DAQmx until you know exactly what "same" means.  Once you do, there are a lot of DAQmx examples and resources in the help and on the ni site.

 

-Kevin P

 

 

ALERT! LabVIEW's subscription-only policy coming to an end (finally!). Permanent license pricing remains WIP. Tread carefully.
0 Kudos
Message 11 of 12
(965 Views)

You are thinking about the Compatability VIs. I once looked at them when I was first starting DAQmx as well. They only supported a few of the traditional DAQ functions but the requirement that you have traditional DAQ installed as well will probably rule out it's use.

 

I totally agree with Kevin about the requirements he mentions in point 2.

0 Kudos
Message 12 of 12
(961 Views)