How to install pyrobot.brewery
- Download and install ActivePython
- Open Command Prompt
- Type
pypm install pyrobot.brewery
Lastest release
Introduction
Welcome to the zeromq version of pyrobot.brewery. The original branch, which I started working on a couple of years before I actually put a physical brewery together, has a good deal of tests, and should have worked well --- but it didn't.
On the first version, I spent a lot of time attempting to make it work for anyone's brew setup. This time around, I didn't worry so much about that and instead worried about making sure it works well for my setup. So, if you build a brewery that is set up like this:
water input +----+ ---------------+--+ | solenoid valve +--+-+ | +---+---------+ | | | hot --+-- float switch | liquor | | tank --+-- thermometer | | | +-----------| - +-------------+ +++ electric burner ||| solenoid valve +++ +-------------+ +-----------+-+ | | | mash/ | | lauter | | tun --+-- thermometer | | | ------------+ +-------------+ +++ ||| solenoid valve +++ +-------------+ +-----------+-+ +---------------+ | | | | | boiler | | fermenter | | | | | | --+-- thermometer | | | | +--+ | | | +------+--+-----+ | +-------------+ +--+ +---------------+ electric burner pump
then you should be good to go, right out of the box. Most brew setups won't be set up this way, but I hope to make it easier to use for any setup in the future. I would like this to evolve into something that could be used as a cheap replacement to labview.
I currently run the brewery on a beagleboard. The brewery has my setup built in, so all you have to do, after pyrobot.brewery is installed, is call
$ start_brewery
from the command line. This starts up all the components that control all the devices and sensors that are pictured above. It does not start up a UI. When I do this, the cpu on the beagleboard is running at ~75 percent. In order to take some of the load off, I run the UI on another computer. If the beagleboard has an ip address of 192.168.1.7, then I start up the UI from the command line like this:
$ brew 192.168.1.7:4242 /home/craig/beer/recipes
The second argument to the UI command is a path to a directory that contains recipes that the brewery can use to run a brew method, which does almost everything for you. All you have to to manually is add grains, stir the mash, recirculate the mash, and maybe something else, but I can't think of it right now.
Changelog
1.0dev (unreleased)
- Initial release
2.0
- A complete rewrite based on zmq commuication.