What exactly do I have to install on a PC to run a program using NI-DAQmx?

[Graziano]

Hi!
I developed my program, for data acquisition in LabWindows v. 7.0, and I'd like to install it on a PC where Labwindows is not installed. I thought that it was enough to install DAQ 7.2 driver provided with my acquisition board, and install the program created with "create distribution kit", but my program does not work properly. In effect I developed it with DAQ 7.3 driver, and I don't know if that's the problem...

The strange effect is that in menus for selecting channels of the board I don't have possibility to make choices (the arrows on the left does not appear), while in the PC that has driver 7.3 these arrows appear and when pushed prompt the list of available channels.

Or maybe I have to do something more when I create the distribution kit?

Thanks!

[Nick_]

Hi,it could be related to different ni-daqmx versions, if I try to run an example created with NI-daq 7.4 in a PC with NI-DAQ 7.3 i receive an error ("... DLL exist but the version is incorrect ...").
Anyway the empty physical channel control sounds a little different...
Do you use some instrument? (daqmxioctrl.fp for example).
If you do, double check if you added it to your executable (look in target settings configuration!).

Get back with more details if you need more help!

Ciao.

NicolaC
National Instruments

[Graziano]

Thanks Nick,
Now it works, it was a driver problem! I compiled my program using DAQ 7.3, while I installed it in a PC using DAQ 7.2, shipped with the board. I didn' thought it could make such a difference....

Now it all works with DAQ7.3.

I have a further question: I actually use daqmxioctrl.fp, but how can I include it in "target settings"? It is included in project, but when I click Target settings... --> Add files to executable I get a list in which daqmxioctrl is not included, and there seems to be no way to include it....

Thanks!

[bilalD]

You don't need to deploy the daqmxioctrl.fp with your application or manually add it to the executable, which is why it does not show up. It gets included in the exe automatically when you use it, just like any of the other CVI custom controls.