I will explain how this works....On the left you have (4) inputs, I1, I2, I3, and I4. I1 will be hooked to a thermostat set to make at 32° or whatever temp you have the thermostat set at. They are connected to an "AND" block, meaning that all inputs to this block have to be on before the relay makes.
I2, I3, and I4 (Bay 2, 3, and 4) are all inputs from the bays that have the Tri-Foam. They are hooked to a 2 second ON delay relay set for 2 seconds. I explained how that works in my previous post. When the relay makes, the next block is the "AND" block. Since the connection has been made from both the bay and thermostat, it allows flow through it to the next stop. Which is a double set of On Delay Relays and Interval Time Delay Relays w/ pulse output. The timers on these relays are such that the top row delays for a preset amount of time then turns the output (Solenoid) on for a preset amount of time. The second row is basically the same, only the On delay is set to like 5 or 10 minutes for the second blowdown. The "OR" block is just a simple connection block because you can't have two relays going to a single output. The "OR" block allows throughput from either circuit.
Now to explain how the simulator works. At the bottom of the diagram, you see (4) green buttons. I1, I2, I3, and I4. They are your inputs. The 3 lightbulbs beside the switches are your outputs/solenoids. In order for the circuits to work, you have to turn on I1 or the thermostat. Then if you turn on either of the other three switches (Bay inputs) nothing happens. The program only starts when power is turned off to any of the switches, which is what we want. Then the relays all work together to give you the output you are looking for. Its easy to change the time values of each relay...
So...It took me about 3-4 hours playing with the program to see how it worked...Once I got started it only to me about an hour to get to the finished product.
The ONLY ISSUE I see with my program, is that when the simulator starts, it cycles each relay (turning on the output) just one time then it sets waiting on bay activity. I'm wondering if all controllers do this. It may not do it on the controller. I don't have it yet to test. On order! But I'm relieved I have a usable program for when it does come in.
Any suggestion on how to make it better, I'm all ears!