Installing an application built in Labview

[Paul_Kenn]

I have built an application in Labview that runs fine on the machine on which it was created.  When i install this on another machine the app does not seem to communicate with the cDaq or its modules that are attached.  I can see the devices in the device manager, and all are there, however when running the app there seems to be no link to them as the active light on the cDaq never comes on as it did on the other machine.  were there files I forgot to add previous to the build of the installer.

This is the first time i have tried to install an app on another machine, and am fairly new to this.

thanks for any help

PK

[Bob_Schor]

You may be missing the Run Time Engine (RTE) on the Target machine.  I'm assuming that (a) you build an Executable (.exe) on a PC that has LabVIEW installed, (b) the Executable runs fine on the the Development machine, (c) you copied the entire Build Folder (where LabVIEW put the .EXE, which also has a few files and folders included) to the Target machine, but (d) when you run the Executable in the Target, little happens.

Do a Web search for "LabVIEW 20xx RTE" and choose the one that matches the "bit-ness" of your LabVIEW system (probably 32-bit).  Install it on the Target.

Bob Schor

[Paul_Kenn]

The RTE was installed when i ran the installer, however i tried reinstalling it to make sure.  Still the same issue the app starts up but there is no connection to the Cdaq or its modules. Is there any configuration i need to do on the new machine?  Both machines are the same OS and version.

Thanks for your help.

PK

[RavensFan]

Did the installer include the DAQmx run-time engine?  That is separate entity from the LabVIEW run-time engine.

[Bob_Schor]

---

@RavensFan wrote:

Did the installer include the DAQmx run-time engine?  That is separate entity from the LabVIEW run-time engine.

---

Thanks!  I didn't know that!  But thinking about it, I've usually installed my code on PCs being used for analysis, so I never needed DAQmx on those machine (so never noticed its absence).

Bob Schor

[RavensFan]

Just to add to that, I think there are two different versions of the DAQmx run-time engine.  One that installs just what is needed to run executables with DAQmx functions, the other that installs "configuration support" or something like that name which means it installs Measurement and Automation Explorer as well.

I always go for that latter, because if for some reason I don't, I almost always wind up needing MAX to test a channel to make sure the raw signal is what I expect before I start running the LabVIEW-based executable.

[Paul_Kenn]

Thanks for the information.

I had installed NI device monitor on the target machine, and found that the 9174 is identified as cDAQ2 on the target and cDAQ3 on the original machine.  Is there a way to rename the device, or  would this cause the issue?

Regards,

PK

[RavensFan]

Go into Measurement and Automation Explorer (MAX).

You can rename it as long as it doesn't already have a device defined with the same name.

[Paul_Kenn]

Solved my issue.  The device name was not updating in the app as it was supposed to.  

Thanks for everyone's quick response and help.

Regards,

PK