LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

What situations result in an event structure not capturing the change of a boolean value?

Solved!
Go to solution

I added the small event structure on the outside, only because I wanted user to confirm if all the settings which need to be done externally were set. As the while loop executed continuously without the small event structure, the program would prompt the user after every run completes. But the way I have it now, it will only prompt the user when he wants to start the test run.

 

I am unable to figure out how can I add a state machine for top level, as they can be considered independent events.

 

The original question took the back seat. Any reason why value change in "EXIT" would not execute?

 

Thanks,

Nevil

0 Kudos
Message 31 of 33
(566 Views)

Attach a simplified version of your program. This cannot be debugged by looking at a picture.

0 Kudos
Message 32 of 33
(564 Views)

I did figure out what was causing the EXIT event to not execute. The small evevent structure outside the main one was the culprit. I got rid of it and all worked as it should have.

Thanks for pointing it out.

0 Kudos
Message 33 of 33
(549 Views)