It all sounds good.
I have my Pi and I'm working on the brewstand its going on right now. My one wire device should be here in a week or so and I want to brew a beer before Christmas.
Where do we go from here ?
I only have the equipment for BIAB so my configuration will be different than a traditional system.
Will it handle multiple devices on the bus ? How long does it tie up the system when its communicating with devices, say getting temps from 10 or so sensors ?
I've since been playing with the 1-Wire switches and some other 1-Wire devices, and I think my current Arduino / RPi configuration is the most flexible, and makes best use of each board's strengths.. The Arduino is a far better solution for process control, and the RPi is better suited for front-end operations. The only thing I might change is trying to get the I2C interface running, which would allow me to access multiple arduinos with one RPi
brewman ! said:I think we should split this thread off into RPi + Arduino efforts for those that want that and RPi alone efforts for those that want that.
however, this 3.3V - 5V disparity is not the only reason to use an arduino for IO...
hey guys, longtime lurker, brewer and EE here who started in automated control systems. Wanted to say the arduino / pi combo is the way to go as it is a great analogy to the PLC / SCADA combo at the heart of a lot of industrial automation.
these relay boards will certainly work, they take a 5V connection and then you can apply 3.3V to control each relay. The thing to watch is probably current draw, i'd probably use another 5V source - having all eight on at once might be a decent draw. in this case, the 3.3V - 5V interfacing is taken care of. Adafruit makes a simple bi-direction interfacing chip for the pi for this specific purpose.
however, this 3.3V - 5V disparity is not the only reason to use an arduino for IO, thought it does make voltage screwups much cheaper, just a new chip in the arduino vs. a whole new pi. The real advantage is that linux is too slow/sloppy to properly control IO, but is clearly the winner in terms of http (web serving), logging (data acquisition) and supervisory control (changing setpoints, starting/stopping processes, etc.).
my ultimate setup will go as follows:
- start with just raspberry pi controlling ferm temp (currently following this tut: http://learn.adafruit.com/send-raspberry-pi-data-to-cosm)
- expand to control keezer and ferm with arduino/pi combo
- finish electric single tier stand (BCS) and use pi to run web interface showing keezer and ferm temps as well as an interface into the BCS during brewing.
next pi project is a desktop arcade enclosure (MAME) which, IMO, goes great with friends and freshly brewed beer.
keep this thread going and good luck to all :rockin:
There is a place......
The only one.
The Raspberry Pi with a complete professional Process Control System.
Proview.
Just to let you know.
http://maba.dk
So, we found both a cheap housing....
Anyway, Proview is open source (GPLv2).
Maybe you should have a look at proview.se
Cheers..,
Marc
Enter your email address to join: