But a good word on the way could be draw everything down before starting coding that way the produced code will have less errors and be done a lot faster. Ooh looked at earlier post by Lancie1 he gives you a good example of clean logic to so now you should have all the tools you need to solve your problem. This example may have some errors but it ought to give you an idea how to deal with these kind of problems when you have a sequence of events. If one would like to be able to pause in the middle of the sequence just use the run flag in the actions to stop appropiate outputs and maybe in the sequence so a transition doesnt get triggered. The example operation cannot be paused even if the stop button is pushed the operation will do its cycle to the end before it stops. I have a digital input for when the tank reaches 48 degrees.
In my example you have valve a and valve b one for each product both uses the same pipe and flowmeter to get down in the tank.
Made an exampleprocess with first design and then implementation.
