LabVIEW
Boolean buttons not functioning well within loops and array indicators not populating.
Your problem is the loop inside of the event case. The event case is set (by default) to "Lock panel until event case completes". So when you press the button, the panel is locked and your buttons will not work. Based purely on what I see in your code, I would get rid of the event structure and just use a case structure.
In addition to what Tim just said, please start with a few simple LabVIEW tutorials, because large parts of your code make little sense.
For the loop on the right left (edit), you know the number of iterations before the loop starts, thus you should use a FOR loop. No need to check the counter with each iteration.
You are probably trying to build an array of instrument strings in this loop. Building the last reponse into an array with one element does not seem to be very useful? If you would use a FOR loop, you could create the array of all responses using an autoindexing output tunnel. Try it!
If you use an event structure, you also need an event for the stop button.
never use interactive loops inside event cases. You can use the outer loop for everything (e.g. by utilizing the timeout event). But I agree that you should not even use an event structure here.
In the inner loop you are doing a "not equal FALSE?" comparison. Try to make a truth table for all possible inputs and see of you can simplify the code. 😄 How different would the result be if you would just delete that function and only leave a wire?
Learn about mechanical action settings of booleans.
@mprince956 wrote:
I'm not sure how I'll replace the event structure with a for loop and still get the program to wait for a trigger, but I'll look into it. Any suggestions on that would be helpful.
Nobody suggested to replace the event structure with a FOR loop (I said that the outside while loop on the left should be a FOR loop instead).
In terms of program architecture, the magic word is "state machine". All you need is a single outer while loop with a state variable held in a shift register and a case structure to define what the program should do and where the program should go next as a function of state.
@mprince956 wrote:
So the while loop on the left should be a for loop with N wired to Number of Instruments. I'll do that. Thanks.
Here's how that could look like (sorry, I don't have your subVIs)
Of course you probably want to add a bit more intelligent error handling, e.g. if one returns an error, for example.
@mprince956 wrote:
If I put a state variable into a shift register on the while loop (I'm guessing you mean the one on the right, now?), will that make the program wait for the user to push the trigger to begin displaying data?
One of the states is the "idle state" that just waits for the controls to change and goes to another state depending on the new values.
@mprince956 wrote:
How do I make a state variable and put it into the shift register?
Have a look at the examples and design templates that ship with LabVIEW.
@mprince956 wrote:
. Any suggestions?
You really need to go back to the tutorials and learn about the various types of tunnels. The default FOR loop output tunnel is autoindexing, turning your error into an array of errors. You can change the tunnel to "last value", use a shift register, or insert a "merge error" afterwards.
