DAQ Code Runs Slowly in Executable

[xkenneth]

All,

    I've got a bit of DAQ code here from a much larger project that seems to run very slowly when compiled into an executable. The code is set up to auto-identify one of several devices, configured them through DAQmx calls, and then combine the data into a standard cluster of waveforms no matter what the device. Please have a look and see if there's anything you could suggest I try. If I'm employing any bad practices/techniques, please let me know. Thanks for your time!

Regards,

Ken 

[Jason_D]

xkenneth,

This .exe runs slower on all computers including the computer you develop on?  What is the time difference we are talking about?  Do you know which specific parts use the most time?  You might be interested in this link which shows you how you can monitor what parts of your code are taking the longest and focus on those.

[Hillman]

Hi Ken,

Thanks for the post and I hope your well.

I a few things I'd like to check - as well as more information on your which areas of code are an issue?

I assume your comparing the speed of the code against the delovement machine;

1) You may have the wrong version of DAQmx installed on the target machine. If this is the case I would recommend completely uninstall the software and then install the correct driver - and then confirm this driver has been installed correctly.

2) Have you tried running the EXE on another machine? Maybe that your deployment machine has lower specs.

3) I would check that any file paths your using are valid, remember they change when code is deployed. Please see,

How Can I Change or Set the VI Search Path for LabVIEW Executables?

http://digital.ni.com/public.nsf/websearch/3F27220C34DDA65386256F9000771289?OpenDocument

Generally, you need to locate which area of the code is slowing...

Hope this helps, please let us know.