I have seen the entries in the forum but they were all more or less the same and did not convert to what I want to do. I want my program to start when I push the button, and I want it to stop when I push it again. And after I start again, I want the programme to execute from the beginning of the flat sequence. But it does not start from the beginning, it continues from the same place left. Thanks in advance!

Dividing the measure state would mean a lot of work, what about putting a while loop there and stop the execution by controlling that loop? You have implemented your while loop already. Use ONLY the outer while loop and add for every case an entry in your State- Enum. Something like: Initialize Program Start Stop Initialize Mesurement Measure SS End ... Make a TypeDef of your Enum, so every change to the list of states are applied to all instances of this TypeDef. The type of your Queue could be this Enum, so you could force your state machine from the "producer loop" to jump into every state and only have to decide (with a "select" node) whether you get the next state from the "dequeue Element" function or from the shift register. Btw. in this way you have to wire a constant to the timeout- input of the dequeue node. As Gerd stated, it doesn't seem very complicated to brake your code into chunks. Use "Edit - Create SubVI" from the Block Diagram menu to modularize your widespread code. As an example I took a part of your code as a very good candidate to be hidden into a SubVI: Select this (except the "Measurement range" control) and execute the menu command and all of this shrinks to 32x32 Pixel with very few wires going in and out. You could put this into its own state and after executing this code-part the loop will check whether the producer loop has sent a Stop- Signal or continues with the next state. (Unbundle these boolean wires and the two Dbl wires outside the SubVI) Another point is the long name of this control in your "timing range" Cluster control. The "unbundle by Name" node uses the label of the sub- control. Instead of showing the label of that control you could show the Caption on the Front Panel and use a short name for the label which then is hidden. This can be done very convenient via the properties dialog of the sub- control. I would need a more practical way as I will apply this to larger VIs in the future. With these strategy you will easily handle much larger VIs. I understand your "large" as "more complicated", not bigger in Block Diagram size. Take care that your BD always fits to a single monitor. There are a lot of approaches to programming LabVIEW programs which are easily expandable and maintainable (as a start like this, what I explained before) like the JKI State Machine, the State Machine Editor from NI or something like the Actor Framework.