10-27-2010 08:54 AM
Hello,
I have a single VI that I have built into an application and then into an installer, including the run-time engine.
The VI uses DAQmx code the write and read a few values using NI hardware (6008), and not much else.
For the installation on a machine without LabVIEW, I noticed a few errors, all relating to DAQmx. I am using LabVIEW 09.
Could someone tell me exactly what I need to install other than the run-time engine?
Do I need one of these in order to use NI-DAQmx?
http://search.ni.com/nisearch/app/main/p/bot/no/ap/tech/lang/en/pg/1/ps/10/sn/catnav:du,n8:3478-PERI...
Also, do I need drivers for the specific hardware I am using, to get that to recognize and work on another machine?
thanks
10-27-2010 09:01 AM - edited 10-27-2010 09:03 AM
Did you include NI-DAQmx runtime in your installer? It's in the 'Additional Installers' page of the Build Installer. I usually check all the DAQmx choices but I think you really only need the runtime for most apps.
EDIT: Oop, I see that you DID include it already. What errors are you getting exactly???
10-27-2010 09:15 AM
I included the LabVIEW run-time engine. The errors all refer the the DAQmx code, like error finding DAQmx write, read and things like that. So obviously I am not set up to use the DAQmx on the non LabVIEW machine.
I wondering If I needed one the installations from the link I included. I looked at the table for the devices on this link, http://zone.ni.com/devzone/cda/tut/p/id/6913, and clicked to the one it has listed for 6008. This one, http://joule.ni.com/nidu/cds/view/p/id/2214. But then I look at some of the other downloads like for example, http://joule.ni.com/nidu/cds/view/p/id/2215/lang/en, this one has configuration for MAX, which sounds useful to me. Or is it the same thing, but with MAX included.
So again, I need to get the other machine to recognize the hardware, and for the installed program to work with DAQmx as it needs to.
The program works fine on the LabVIEW machine, it's the installation that I am still working on.
10-27-2010 09:18 AM - edited 10-27-2010 09:18 AM
You also need to install DAQmx, and based on what you are saying it sounds like you did not do that. The LabVIEW Run-Time Engine is just for the application. As noted previously you can include this with your installer by checking it on the "Additional Installers" page, or you can install it separately.
10-27-2010 09:32 AM
OK I checked "additional installers" and saw NI-DAQmx 8.9.5 and install type "full" or runtime 1, runtime 2, runtime 3, etc.
If I am not mistaken, including this in the installer will require the dvd, won't it?
10-27-2010 09:48 AM
If I install NI-DAQmx version 9.2.2 on the other machine, but the program was done with version 8.9.5 , would there be an issue there?
10-27-2010 10:00 AM
@nano_era wrote:
OK I checked "additional installers" and saw NI-DAQmx 8.9.5 and install type "full" or runtime 1, runtime 2, runtime 3, etc.
If I am not mistaken, including this in the installer will require the dvd, won't it?
Don't really remember about this one. If it does it would be just for the building of the installer. If you no longer have the DVD you can download DAQmx from the NI site: http://search.ni.com/nisearch/app/main/p/bot/no/ap/tech/lang/en/pg/1/sn/catnav:du,n8:3478.41.181.549...
If I install NI-DAQmx version 9.2.2 on the other machine, but the program was done with version 8.9.5 , would there be an issue there?
There should not be, since both versions support LV 2009. You're better off, though, installing the version you developed in.
10-27-2010 10:14 AM
OK, I will try that.
But what about these device drivers? http://search.ni.com/nisearch/app/main/p/bot/no/ap/tech/lang/en/pg/1/sn/catnav:du,n8:4.9547.9548,ssn...
Are these needed for using NI DAQ devices or are they just bundles of different drivers that are not necessary?
10-27-2010 10:18 AM
They're just bundles of various device drivers. They should be the equivalent of the device driver DVDs. It's up to you whether to download just the DAQmx or the entire DVD.
10-27-2010 10:19 AM
Device Drivers are to support other external hardware like DMMs, etc. If you developed your code with them, they should just work in the executable as well.