Building labview executable file with a DAQ

[smalinowski]

Hi all,

I've built a labview code that uses the NI USB 9213 device to measure temperatures from thermocouples, and display each thermocouple's temperature as indicators and graphs. The code works great, the only issue I encounter is when I try to build the code as a .exe file, to be run on a computer without labview. The issue that occurs, is when you open the newly created application, the program does not collect any data. The program will run, however it doesn't do anything, and all the temperature indicators and graphs read 0 for each thermocouple. As if the DAQ is not measuring anything at all. To build the installer, I followed the instructions on the link I posted below, and I consulted my Universities labview course professor, and he could not figure it out either.

Any ideas why this might be occurring or potential things to try to solve it would be great. The instructions that I followed originally were from the following links:

http://www.ni.com/white-paper/4039/en/

and

http://www.ni.com/white-paper/5406/en/ 

[EccentRick]

Hi smalinowski,

Would you mind answering a few questions regarding this issue?

1. What version of LabVIEW are you developing your code?

2. Have you tried running the executable on the development computer as well as the computer without LabVIEW?

3. Are you configuring your channels in Measurement and Automation Explorer as global virtual channels, or configuring the channels within your code?

Thanks!

[andcp360]

I made an installer for any PC (with or witout LV) using simulated cDAQ chassis and modules. Firstly i inly made an application and obviously it didn´t work when i run it on LV less PC. Then i made an installer without include any additional installer (only auto-checked ones) and again it fell. Finally i include DAQ config support in additional installers and it worked... The only thing that seems you dont make is as Rick posted is you NI MAX configuration, you must have your channles and task configured there to acces it using DAQmx pallete functions. If you are using DAQ assistant you must be carefull, i recommend use global vitrual channels and global channels in MAX.

[andcp360]

Correcting:

...and DAQmx pallete.

[smalinowski]

Hi guys,

To answer your questions:

1) We are using labVIEW 2013, the latest version, we actually upgraded it a few weeks ago

2) We've tried to run the application on the computer where the code was written, as well as other computers

3) I'm actually not sure about this, but I think it's within the code. Maybe this is where I'm going wrong. 

I'll also try the advice andcp360 gave me as well as looking into your 3rd question to see if that solves anything/.

Thanks guys

[EccentRick]

No problem! If you are creating an installer in LabVIEW 2013 the LabVIEW run-time and DAQmx runtime should be bundled with the installer. However, depending on how you configured your virtual channels (which could be done by using DAQmx functions within the VI, creating a global virtual channel in MAX, or using the DAQ Assistant express VI), you could have some type of inconsistency in hardware references between the machines. Definitely take a look at how you're configuring your hardware 🙂

Regards,

[smalinowski]

We actually were able to solve it last night. We just missed the step during the build installer to configure/add the DAQ hardware device, and after we did that the .exe file worked for us on both computers, including one that never had labVIEW installed on it before.

Thanks for all your help and advice!

[EccentRick]

Good to hear! Good luck on your project!