Hi, I have a problem when I want to implement an event in my state machine. The state machine is reading serial communication through 10+ different states. The problem came when I tried to add an event inside state number 10. In state number 9 the code seems to run only partially (one radio button is not possible to change value on). It looks almost that it is frozen but when I highlight the code I can see it is running though (radio button is not). It is strange that when I remove the event in state 10 everything is fine again? The event code is not even run yet because it is in the frame after! Any thought?? I am running LabView 2013 on a Windows 7 PC.

I'm trying to figure out which of the two cases is the one that seems to hang so the name would be better than a number. When using am event structure you don't we want to use a local variable. In fact, you should only use local variables on rare occasions as they break data flow. An event structure is fine for input. The problem is the way you're handling things after the button is pressed. Again, I think you need to look at a Producer/Consumer design pattern with a queued state machine. The easiest way to have a write happen only after a button press is to have the code for the write in a case that is only active when the button is true and is simply empty when it's false.