LabVIEW
Use one Boolean control in several places in various structures
Solved!
Hi wjstraka,
The simple answer may just be that I need to entirely restructure my labview program
Yes, that's the simple answer!
Is it possible to have just one button to control all three event structures depending on which case structure I am in?
No, not the way you programmed it.
In a VI only one event structure can be assigned to handle the button!
(You might try to start with user-defined events and enabling/disabling them for each case, but then a clean "restructure" is the better way to go with less hazzle in the end.)
On your "main application": this all looks way to complicated. It might get mentioned in the Rube-Goldberg thread… 😄
Example:
The Search1DArray does most of the work for you and FormatIntoString most often can replace ConcatString…
Thanks for the reply. Unfortunately, that's what no formal training and occassional self learning looks like. 
Hi wjstraka,
the event structure is not the easiest to master by a LabVIEW beginner.
I can recommend to read its help entry as well as the "Event structure caveats" mentioned in the help…
I want to clear up some misinformation. There is no problem having multiple event structures in a single VI, but you should never hide them inside case structures unless you can guarantee that they are reached by dataflow with little delay. If you have multiple event strictures, they should each be in their own while loop. You can also have multiple event structures reacting to the same button. They all will fire. (exceptions are discarded filtering events, etc.). What is this VI actually supposed to do?
(linkam pump speed) Yes, your iteration using a while loop is extremely dangerois, for example if there is no match, the loop will spin forever. Unlike a FOR loop, a while loop does not stop if it runs out of elements at an autoindexing input tunnel. Yes search array is the correct function. There is a +1 primitive. You should use a array diagram constant. The addition and division belongs after the loop. You can add the percentage sing to the format statement (as %%), no need to concatenate. Are you sure there is mo "math" way to convert the bytes to speed?
(full linkam controller) How often is the "Pre T command" case executed? If the code spends any length of time in other cases, you cannot have the event structure there. I strongly suggest to make your enum a typedef. You already have mismatched version.
(Lincam convert temp) Pure rube goldberg! Way too much duplicate and unnecessary code. Do you have a spec sheet describing the math? I am sure the correct method could fit on a postage stamp. 😄
If you can guarantee that the input to "pump speed" is not malformed, here's a VI that does exactly the same thing! try it!
(Of course you might want to do some input and output range checking, but that should not be hard)
