LabWindows/CVI

cancel
Showing results for 
Search instead for 
Did you mean: 

NI-DAQmx missing from CVI 7.1 after 8 installed

Whoops, apologies if someone's already asked this (if so, point me to the thread?).

I just installed CVI 8, but had to keep 7.1 for now due to ongoing support and deployment issues. In the install, it just said to install it to a different directory. What it did *not* say, was that it would hose your configuration for CVI 7. Specifically, the drivers like DAQmx and whatnot are now missing from the 7.1 configuration.

When I try to build, I get various errors. At first, I started trying to fix them one by one (like #include <NIDAQmx> wasn't working, etc.). Eventually I got the project to compile, but not link. None of the DAQmx functions are actually there, and the library in the code editor menus is greyed out.

Silly issues no? Now I can't support my existing projects 🙂 Any idea how to fix this?

Cheers,
Avner Ginsburg


0 Kudos
Message 1 of 4
(3,854 Views)
Hello AvnerG

DAQmx installs the drivers files only in the newest version of CVI that it finds. It does not search for all the versions of CVI present on the machine. What you can do is
copy the daqmx files to the CVI 7.1 location yourself if you need to keep using CVI 7.1 with DAQmx.

grab the following files and place them in their respective CVI 7.1 locations

From the CVI80\bin folder, (to go under CVI 71\bin and so on)

nidaqmx_lvrt.lib
nidaqmx.fpc
NIDAQmx.lfp
nidaqmx.lib
NIDAQmx.sub


From CVI80\extlib:
nidaqmx.lib

From CVI80\include:
NIDAQmx.h


I hope this helps
Bilal Durrani
NI
Message 2 of 4
(3,820 Views)
Thanks for the advice!

I called NI, and the solution they came up with was to include the .lfp file in the actual project (just loading it as an instrument didn't stick, for some reason). Your advice is a bit better 🙂

Also, they should have warned us during the v8 install. At the time, I had no idea it would clobber the v7 configuration. Ah well, the price for bleeding edge stuff...

Cheers,
Avner Ginsburg

0 Kudos
Message 3 of 4
(3,812 Views)

If you just load it as an instrument without including it in the project, the next time you open that project, the instrument is not loaded automatically. For that to happen, you would either need to include it in the project or follow the instructions i gave earlier. The advantage of copying the files to the bin folders is that DAQmx becomes part of the main CVI libraries and you do not need to add lfp's to your project. It becomes just like using any of the function panels that are loaded under the library menu. The panels under the library menu are loaded for you automatically for any CVI project.

I hope this clears things up. I pass on the feedback to make this a little more clear in the installers for the future.

Bilal Durrani
NI
0 Kudos
Message 4 of 4
(3,796 Views)