Data Acquisition Idea Exchange
The DAQ Assistant was presumably created to simplify data acquisition. The idea seems to be to put all of the needed pieces in one place, so that all the low level 'traditional' DAQ vi functions are not needed.
Consider the following simple vi:
This could be as simple as one analog input channel.
The program will compile into an .exe and work just fine, as long as you don't use one of the features of the DAQ Assistant: Custom scales.
Custom scales are not stored with the VI or project, but in a system file that does not automatically get included in an .exe build. The .exe will work fine on the original PC that built it, but it will not work when the .exe is loaded on a different PC.
There is a method that allow the user to port the custom scales to another PC, but it is not automatic.
http://digital.ni.com/public.nsf/allkb/12288DEB3C6A185B862572A70043C353
The fundamental problem is that the DAQ Assistant is intended to make life simple and give you everything you need to make a program. Custom scales are included in the DAQ Assistant so that the programmer does not need to manually create scaling in their vi. But what good does that do if they are not included in the .exe build, and there is no obvious clue that this requires extra work or what that work is?
The build .exe process needs to be upgraded to automatically include custom scales and possibly other MAX settings that are essential to the operation of a compiled program. It does not matter if the build process ciphers and includes only the specific scales or setting used by the particular program / vi, or if it just takes all the settings.
These are critical pieces to make the final compiled program run on another machine. The user should not have to somehow know that these pieces are separate but need to be included, and have to take extra steps to go out and select them in order for them to be used in the build. That is totally counter intuitive to the simplicity intended by the DAQ Assistant.
