Executable doesn't want to communicate with my DAQ

[jamessrc]

I am having an issue getting my executable file to communicate with my DAQ. I am using a Asus Eeebook (Windows 7) to run an executable file that I made in LabVIEW. If I am running the executable on my LabVIEW computer (Windows 7) it works perfectly. However if I take that same program and copy to my Asus all of my displays read as if it was not hooked up. If I replug the chassis into the Asus, the computer detects the DAQ chassis. The chassis with the DAQ is still hooked up straight to the Asus.  I have all the drivers for the DAQs updated from the NI site and according to device manager they are working correctly. Can anyone give me some suggestions to troubleshoot this issue?

[James.M]

On the executable computer, can you communicate with the device in MAX? Are you transferring the executable to the computer using an installer, or just copy/paste? Using an installer would help you identify any required add-ons that your program needs.

[Dennis_Knutson]

When you built the installer, food you include MAX? If so, can you run the test panels there? You did create an installer, didn't you?

What is the DAQ that you have?

[jamessrc]

I am simply copying and pasting the executable. I also copy the application.aliases file and the configuration settings file that comes with the executable. As for NI MAX I can see the DAQ and the chassis under devices and interfaces. When I run test panels on the LABview computer I get an error message "The driver fail to communicate with cDAQ2Mod5 through self-test. Error -201105 occurred at Self-Test". The DAQs I have are 9203 and 9208. The one that I am using right now is the 9203 DAQ. As far as I know I did not create an installer but just an executable. How to I make an installer?

[James.M]

In your LabVIEW project (hopefully you're using a project to organize your code), you can do a new Build Specification and select Installer. In the INstaller settings you can select your executable as the target and adjust settings from there (include support files, etc.). One of the options is the include additional installers to install on the target computer. This would include anything the project thinks that your executable needs in order to function.

[jamessrc]

I created the installer and included from my Project Files View my actual application under Build specifications. I moved this file into the destination view. The only additional installers that I included was NI LabView Run Time Engine 2012 SP1 f9. I installed it on to my Asus and the program did not display the correct number. However when I looked at MAX under test panel I found that it was giving me the correct number. Why is MAX displaying the correct number and my program is not? Should I just install the entire LabView program on the Asus? It usually takes all day to install and I wanted to avoid doing that. If not what additional installers should I include in order to get my program to read from my DAQ?

[James.M]

You're able to communicate now, but the data coming in isn't the same? I'm unsure what you mean by "did not display the correct number."

Can you share your code? It would be easier to figure out what else could be causing the problem. If you're able to communicate with the device now, then maybe something else isn't transferring right. Do you have absolute paths coded in for the "configuration settings file" that you're bringing with you, or did you make sure to set the path as relative to the application directory?

[crossrulz]

Time to show some code.  How are you defining the channels to read in the DAQmx API in LabVIEW?  Does the Asus laptop have the exact same settings in MAX (device name, channel names, etc) as your development computer?

My gut feel is that last question is your issue.  You should export your MAX configuration (only what is needed for this project) and include that configuration in your installer.