LabVIEW
how to stop a while loop...
Hi Sparrow,
nooo
The student version is (maybe) limited in the number of functions, but will not change the way functions (or structures) work!
Why don't you attach your vi? You were ask to do so, but all we get is a crappy scan... (sorry for harsh words)
Message Edited by GerdW on 04-25-2008 09:16 AM
nooo
The student version is (maybe) limited in the number of functions, but will not change the way functions (or structures) work!
Why don't you attach your vi? You were ask to do so, but all we get is a crappy scan... (sorry for harsh words)
Message Edited by GerdW on 04-25-2008 09:16 AM
sparrowroad wrote:
Is it because I have a student version of the software that the while loop will not stop?
No, the student version has exactly the same while loop and stop button functionality.
Maybe something is corrupt in your installation. Try to repair or reinstall LabVIEW.
In the first post, he said it's the same using the example "Generate Random Signal vi" (search for "random" in the example finder), so we have a real VI.
GerdW wrote:
Why don't you attach your vi? You were ask to do so, but all we get is a crappy scan... (sorry for harsh words)
I think I found your problem though!
Use the "run button" NOT the "continuous run button" to run the VI !!!!!!
EDIT: Ahh, Norbert beat me to it. 😄
Message Edited by altenbach on 04-25-2008 12:22 AM
Norbert B wrote:
Well, i would appriciate it if future releases of LV wouldn't even have that button......I just want to remind all of you of Ed Dickens signature 😉
I somewhat agree, but maybe I would not go that far. The functionality of the continuous run button is somewhat useful for debugging purposes. I use it to troubleshoot "loop free" subVIs, if I quickly want to play with a few input alternatives. One of the nice features of LabVIEW is the fact that you can easily run subVIs in standalone mode.
Clearly, something needs to be done, here are some ideas:
Name: "Continues Run" should be renamed to something more appropriate, such as "Auto Restart".
Layout: The "auto restart" button should be grouped with the debug tools (execution highlighting, stepping, etc.). It should NOT be next to the regular run button.
Visibility: Maybe it should only be visible on the block diagram window, and never visible on the front panel window? (like the other debugging tools!)
Function: The plain Run button should be the ONLY way to run a VI. The other (=auto restart) button should act like a modifier, similar to the execution highlighting button. In order to run a VI continuously, we would need to activate (toggle) the "Auto Restart" from the debugging group, then hit run. There should be an automatic 100ms wait before it restarts to keep CPU use to a small percentage when running continuously. It should only work if the VI is manually started with its own run button (i.e. not when called as subVI).
Color Hint: The "execution highlighting" and "auto restart" buttons should look prominently abnormal when enabled, e.g. Red outline, bright color, flashing, etc.
FP clue: The front panel of any VI that has any of the debugging options enabled (highlighting, continous, pause, retain wires, etc.) should indicate this, e.g. by showing the warning button with the exclamation mark. Pressing the warning button should give a list of the currently enabled debugging options.
Just some randon thoughts. I am sure there are other ideas out there. 😄
Message Edited by altenbach on 04-25-2008 07:53 AM
