The answer is within the question. However; you will need to rephrase your question to answer it.
What I am speaking of is implementation. How you implement the solution is in how you want it implemented.
If you are running this in a development environment, which it seems as though you are, I would suggest one of two things: A) tell the test engineers (technicians?) to get with the program and learn how to run a LabVIEW VI or B)build this as an executable or make the VI function as an executable on the runtime engine without building it.
If this is one of many VIs that go out in the field for testing, you may wish to package them into a library or installation, and have a 'loader application' that loads them.
As you can see, the answer is much more complicated than the question. You see, the convenience of LabVIEW as a development environment means that most programmers put off learning how to implement their programs as finished products, and instead, continue to run them in the development enviornment. Believe me, this is all to common, and unfortunately, too convenient. However; the answer is a matter of practice and discipline. If this were a C++ program, you would not have any problems developing the finished product for implemention, and it would work as you wanted it, and as the field personnel expected it. However, you are able to run the program in a development environment, a convenience which is coming back to haunt you.
Go ahead and take that extra step and figure out how you want to implement this in the field. LabVIEW has the distinct advantage of allowing you to execute development level programs (VIs) in a runtime environment. Something not available in C/C++ (readily that is).
So, figure out what implementation you want, and design your finished product with that in mind.
On the VI level this means an execute button. Poll the desired control (start?) in a while loop with about a 250ms delay. When the button is pressed, the loop ends, and your code will begin (assuming you have wired the dataflow as such). Also, you have to decide how to launch the VI. If you want the user to simply be able to open it, then you need to build it as a complete application (using application builder). If you don't have the app builder, or want to be able to replace the VI with modified versions often, then create a loader. You will still have to build the application. I'm actually not sure how to use the runtime without a built application anymore.
Anyway, I hope this helps.
Good luck.
