BCS Process Editor

Homebrew Talk - Beer, Wine, Mead, & Cider Brewing Discussion Forum

Help Support Homebrew Talk - Beer, Wine, Mead, & Cider Brewing Discussion Forum:

This site may earn a commission from merchant affiliate links, including eBay, Amazon, and others.

TylerAI

Well-Known Member
Joined
Nov 10, 2009
Messages
109
Reaction score
22
Location
Tyler
I have searched and surprisingly have not found any threads with good information on the BCS Process Editor. I am trying to program my BCS and I think I am missing some of the concepts of getting multiple processes running to efficiently automate the brew.

Simply put, I need some help. Any links to examples or snapshots of your own would be very helpful. :confused:

Thanks.
 
Oh, wow, read the documentation. Why didn't I think of that.

Thanks to the PM's I got. The offers to check out personal settings online was helpful.
 
Ok, I just read it wrong. Trying to explain. I understand the nuts and bolts of how to make the system work. What I am having problems with issues like: how to work a hop schedule with a boil, transitioning from HLT to Mash to Boil, programming in whirlpools. I honestly believed when setting this up that I had eight processes with eight states each. Logically that would allow me to have eight different ways to brew beer. One for a 152 mash with a 60 minute boil, another for a 90 minute boil, another process for a step mash, probably a fourth for a different step mash, etc. Then I would have 4 processes left over. Obviously I am completely wrong on how that works.

I understand now (I think) that the HLT needs to be it's on Process, the Mash another, the boil another and the hop additions another. Thats the part I was not understanding. I believe now I have enough to see how it all works together, it's just time for experimentation.

b0007e7ded70ee4c22b400208e8dedc39affbe337f1e317278bc6baccae0b2cb.jpg
 
looking forward to getting to the point I can start messing around with the BCS! Just (finally after almost 2 year delay!) starting my control panel build now.
 
Think of each 'State' as of a "way things are" for a period of time. That period of time could be as little as zero seconds to as much as hours. And the system goes from one state to another based on "exit conditions" which mean a certain criteria was met.

The BCS has 8 processes, each containing 8 states. There can only be one state running in each process at a time. But you can have as many processes running at at time as you like.

My BCS is set up in a somewhat chronological format. Note that my system is fairly automated, so it lends it self to sequential operation. Each of my processes have a "Process Timer", which continues through each state, and each state has a "State Timer" that does not continue. These help differentiate process times (like boil time) and state times to help with timed exit sequences.

The first process is Mash Prep, and it has states for filling the MLT, heating the strike water, maintaining the strike water temp, and doughing in. The second process is my mash steps, where I have four states each covering a certain mash rest (e.g. acid, protein, sach, etc.), and one state covering mash out. The third process is my sparge sequence, with states for heating/pumping sparge water with and without draining the MLT (I use electronic autosparge - see the video in my build for operation). The fourth process is boiling, which has states for bringing up to boil, boiling, and sanitizing my chillers. This process will run in parallel with the sparge process, as the boil heating begins during MLT draining. The fifth process is whirlpool and transfer - this one might be of interest to you.

The first state in that process is to turn the chillers on and recirculate through the whirlpool arm. This will cool the boiling wort in the kettle so I can add flameout/hopstand hops without isomerizing the oils. The exit of that state is based upon a 30 second state timer. The second state keeps pumping but turns off the chillers - this enables mixing of the wort to ensure an even temperature, and it exits based upon a state timer. The third state keeps pumping but checks for either the state timer of 5 seconds to expire, or the temperature to be at or below 180 degrees. If the timer expires, it exits to the first state to cool the wort further. If the temperature criteria is met, the state exits to the whirlpool state. There are two whirlpool states (with and without chillers inline), then on to fermenter transfer.

I do not think your HLT should be on its own process. I think you should have your brew steps grouped into processes. You can have any process affect your HLT temp. For example, if you are doing a step mash, and you have a mash process, each state in there would dictate the HLT temp, raising it as needed.

I think the best approach is to write out all the brew steps in "states". First, this happens (e.g. heat HLT to a temperature). Then this happens, etc. Once written out, group them together and build those into discrete processes. Make sense?

-BD
 
That sounds like a good idea in literally diagramming my brew steps as States. From reading your post, I definitely had the wrong mindset when starting. Going from my basic setup to a highly automated one is almost like learning to brew again.

I did brew another batch yesterday. I liked being able to set up and program my strike water to be ready when I woke up. I do think I have some wiring glitch. When the programed alarm activates, it sounds odd and the pumps shut down. Like something is shorting out the relays.
 
..... I do think I have some wiring glitch. When the programed alarm activates, it sounds odd and the pumps shut down. Like something is shorting out the relays.

Found it. There is a 4-relay board that controls two pump outs, an external alarm, and a lighted Input button. The -12v also needs to be tied to the system ground. Probably a "Duh" but it was new to me.
 
Back
Top