I found this tutorial http://www.ni.com/tutorial/3303/en/ but am just looking for some further guidance to make use of it. As the reviews below the article indicate it's not the most helpful...
I have a .vi I put together, it takes in data from a cDAQ, does some live analysis, spits out some .lvm files on demand. It uses a few subVIs. Nothing that fancy really. One thing to note is I never bothered to set it up as a project or anything, just the .vi's (and a control).
I want to be able to use it on another PC with no LabVIEW programs of any kind installed. I'm wondering how I'll handle the challenges of it assigning different names to different cDAQ chassis. I'm also not really understanding the distinctions between the different options in that tutorial and how to choose which is appropriate for me. Any guidance would be super appreciated.
I do agree that the example reminds me of the LabVIEW examples I read a decade ago that made building applications sound much more difficult than it needs to be. In the vast majority of the Applications that I've built, I've built Stand-Alone Executables where the only VI I put in the Build Specification is the Top-Level VI, which calls other VIs (and pulls them into the Build) that call still other VIs that call DAQmx functions that call other functions, and before you know it, everything is in memory, built into an Executable, and loads and runs.
The best way to convince yourself is to try it. Start with something simple. Build it in a Project. Write a Build Spec. Run it.
If it behaves strangely, do the following: