Executable is not activating DAQ on alternate machines

[Kturner]

Hi all,

I have created a fairly simple labview program using the DAQ assistant to read the the differential between AI0+ and AI0-.  The executable works exactly as I want it to when I run it on the machine I built the program on.  However after installing all the required drivers on two other machines I have had no luck getting them to work.  The blue "active" led on the front of the DAQ does not turn on when I run my software on the other machines.  However it does turn on when I run a test on those machines via the NI Device monitor.  

I have created a controller for the device input on the DAQ assistant.  I have made sure the names of the devices are the same in the configure tab of the NI MAX and I have even exported the configuration .nce file from the machine I created the software on to the other machines.   To no avail.

The code is simple, the DAQs are named identically on each machine.  The drivers are all there.  The DAQs work fine on all machines in test mode via NI device manager.  However when I run the executable on any other machine than the one I made the executable on the software reads nothing but 0s and the blue activate LED on the front of the DAQ does not illuminate.

Thanks for your help.  The code is below.  Should I just not use DAQ assistant and write my own code?  

[RavensFan · Accepted solution]

Highly recommend dumping DAQ assistant and write your own code using real DAQmx functions.

But before you do that, create an error indicator on your from panel coming from the DAQ assistant.  It just might give you a clue as to what is going on.

[Bob_Schor]

Is the appropriate LabVIEW RunTime System on the "other" machines, as well as the Device Drivers?

Bob SChor

[Kturner]

The error indictator showed no errors.  When I dumped the DAQ assistant and created the channel in the way shown I no longer had issues.  It seems plauisble the DAQ assistant has something going on behind the scenes I am unaware of. 

[Bob_Schor]

In my opinion, the DAQ Assistant should (almost) never be used for Serious Code.  If you want to do a quicky "Can I get some data out of this just to look at", I recommend using MAX and its Test Panels first.  Going the DAQ Assistant route hides so many details from you and tries to steer you through such simplistic paths that you can easily fall into problems such as you have experienced.

Bob Schor