Is there a way to "lock in" BCS at a single state?
Posted: Thu Mar 17, 2016 11:45 pm
Hi folks,
So we are a commercial brewery using BCS solely for temperature sensing and control of electronic ball valves on our glycol system. As such, we don't really have much programming going on. Just a single process called "temp control" and a single state called "temp set points". We simply adjust the temp set point manually when we want to alter fermentation temp, do diacetyl rest, crash a beer, or a tank is empty, etc. Anyway, it just so happened today that while checking a temp on their smartphone, one of my brewers accidentally pressed a button on the web interface to switch the process to a different state, which changed all the set points to "null" and closed all the ball valves in the brewery. We noticed it right away and simply stopped and restarted the process to get it back to normal, but it would be nice if there was a way to prevent the BCS from moving to a different state so easily. Is there any way to get rid of the other states, or require user confirmation before switching states, or some other work around that would help us to stay locked into our single process and state that we desire to be running?
Cheers,
Jason
So we are a commercial brewery using BCS solely for temperature sensing and control of electronic ball valves on our glycol system. As such, we don't really have much programming going on. Just a single process called "temp control" and a single state called "temp set points". We simply adjust the temp set point manually when we want to alter fermentation temp, do diacetyl rest, crash a beer, or a tank is empty, etc. Anyway, it just so happened today that while checking a temp on their smartphone, one of my brewers accidentally pressed a button on the web interface to switch the process to a different state, which changed all the set points to "null" and closed all the ball valves in the brewery. We noticed it right away and simply stopped and restarted the process to get it back to normal, but it would be nice if there was a way to prevent the BCS from moving to a different state so easily. Is there any way to get rid of the other states, or require user confirmation before switching states, or some other work around that would help us to stay locked into our single process and state that we desire to be running?
Cheers,
Jason