02-02-2007 12:37 PM
02-02-2007 01:40 PM
It seems silly to start and stop a built LabVIEW application from the toolbar. A complete application should always run and have the LabVIEW toolbar hidden. A user of you code is not supposed to be familiar with LabVIEW mechanics.
You should do all this in code. Really!
Do a nice state machine with at least two states. (1) a state for where the device has not been entered and is simply waiting for your input, and (2) another state that verifies your device input and hands it to the rest of the code for afterwards.
Still, what LabVIEW version do you have. Did you set the "run when openend" setting in the application builder for the desired VI or just in the VI itself?
02-02-2007 03:03 PM
I already have a state machine with about a dozen states. The 8451's sub-VI's require that you connect something called a "Device Reference" to one of their inputs. They (meaning NI) provide a sub-VI that does nothing but output the Device Reference. Note that the Device Reference comes from the MAX tool (or at least its alias does, since I entered the alias). Regardless, the problem is that the Device Reference sub-VI puts a control input on the front panel. When I compile to an EXE it's grayed-out, so it doesn't matter what kind of a state machine you use - the user can't enter anything.
Fortunately someone suggested that I change it from a Control to a Constant. And that solved the problem although it still doesn't allow the user to change the device that is being driven!
02-05-2007 08:43 AM
02-05-2007 11:14 AM
Hi Kirshme,
This was reported to R&D (# 40HEDDJG) for further investigation.
A workaround for this setting is tot go to the Advanced page of the build specification and check "Enable debugging" and "Wait for debugger on launch". One side effect is this will include the block diagrams of the VIs and extra code for debug tool support.
Here is a link that contains workarounds to several known issues in LabVIEW 8.2.
Hope this helps!