I just realized that you've still failed to create a proper state machine. You have the logic, but you are not passing the next state to the next iteration of the state machine. Your "state machine" will just sit there and repeat the same step over and over. It's also going to seem to be stuck because you have all of those wait times buried in the subvis. It would be better to move all of that up to the main vi as I have suggested multiple times and use an elapsed time state so that you can react to your stop button.
NI has opened up the training so it is free at the moment. So has JKI.
As stated earlier
Rather than spending days writing on the forums, asking the same or similar questions over and over, a little time spent learning can exponentially reduce your development time.
I highly encourage you to take advantage while the open training time lasts.
I have told you multiple times that you need to move the code from your subvi into your state machine. You have multiple states in that subvi, generally represented by the frames of that flat sequence structure. Move those into your state machine and then it should be apparent how to do what you want
I don´t understand what do you mean, sorry...
I'm still wondering what is the answer to my question I asked long ago about have you ever done any programming before trying to work with LabVIEW.
I correct the vi like this
No. Please do some training on how to build a proper state machine. You have absolutely no way to go from one state to the next.
One resource is the JKI state machine which uses strings instead of enums. They're offering free online training right now.
Help -> Find Examples -> Search: State machine
Open State machine fundamentals.vi
Study and learn from the example.
You have sent me a link where it uses an event structure in the state machine. Why? I don't want to use an event structure. On the JKI page there are state machines without the event structure.