- Python 71%
- JavaScript 20.3%
- Shell 5.2%
- HTML 3.5%
| Filename | Latest commit message | Latest commit date |
|---|---|---|
|
|
||
| cgi-bin | ||
| config | ||
| daemon | ||
| data | ||
| img | ||
| js | ||
| .gitignore | ||
| index.html | ||
| LICENSE.txt | ||
| README.md | ||
| report.pdf | ||
| requirements.txt | ||
Dry Tap Bottler
This is a raspberry pi webserver that works with the Dry Tap Bottling System.
Here's the basic breakdown of how this works:
Setup / Config
Run config/install.sh to install mod_python, and configure the apache2.conf file. Everything should work there, but if it doesn't, it shouldn't be hard to manually follow the install.sh file as a guide.
As for config, you'll need to edit index.html, and data/states.db. In the html file you can set the name of buttons, as well as which pin it'll control/report.
data/states.db contains the automatic steps. when a delay of -1 is reached, the system will stop and wait for user input to continue. Note that that step will still need to set the state of at least one pin, or it won't run properly.
States.db:
| Pin | Purpose |
|---|---|
| 11 | I ndexing |
| 13 | F illing |
| 15 | P inching |
| 19 | C apping |
| State | I | F | P | C | Delay |
|---|---|---|---|---|---|
| 0 | 0 | 0 | 0 | 0 | -1 |
| 1 | 1 | 0 | 0 | 0 | 2000 |
| 2 | 1 | 1 | 0 | 1 | 1000 |
| 3 | 1 | 1 | 1 | 0 | 10000 |
| 4 | 1 | 1 | 0 | 0 | 500 |
| 5 | 1 | 0 | 0 | 0 | 1000 |
| 6 | 0 | 0 | 0 | 0 | 500 |
I have created the Daemon using Sander Marechal's sample found here.
Mechanical System
The vast majority of the mechanical ocumentation can be found in our report, but here are a few basics.
Here are some pictures of the mechanisms. This one is the filling area taken from down the queue.
This one is the capping press, taken from the opposite side of the machine.
Price Breakdown
