[Version 2 Release] RaspberryPints - Digital Taplist Solution

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.
Is there a way to get php5 otherwise or can I use the more recent version without issues? !

Unfortunately PHP5 is not available on the latest version of Raspbian, but if you upgrade to PHP7 the original Raspberry Pints code does not work because of removed functions Rpints uses.

Instead you could use a different fork of Rpints from GitHub that have been updated to use the new calls like mine https://github.com/rtlindne/RaspberryPints
 
Thanks! Noob question so would my LAMP command like look this instead:

sudo apt-get -y install apache2 php7 mysql-client mysql-server php7-mysql phpmyadmin

Also is it still apache2 or shoud that be updated as well?
 
Thanks! Noob question so would my LAMP command like look this instead:

sudo apt-get -y install apache2 php7 mysql-client mysql-server php7-mysql phpmyadmin

Also is it still apache2 or shoud that be updated as well?

Try

sudo apt-get -y install apache2 php7.0 mysql-client mysql-server php7.0-mysql phpmyadmin

if that doesn't work use

sudo apt-get -y install apache2 libapache2-mod-php7.0 mysql-client mysql-server php7.0-mysql phpmyadmin
 
Try

sudo apt-get -y install apache2 php7.0 mysql-client mysql-server php7.0-mysql phpmyadmin

if that doesn't work use

sudo apt-get -y install apache2 libapache2-mod-php7.0 mysql-client mysql-server php7.0-mysql phpmyadmin

Thanks! One more question is whats on the github link you posted for RPi3 or RPiB? I am using RPi 1 B+
 
After a few hours of fiddling, I got RaspberryPints up and running on my RPi 3 B+ running Stretch. That was somewhat annoying, tricking it into thinking it was running Jessie so that I could install both php5 and php7...

Now I'm attempting to install Fermentrack, but it appears that that program also has issues running alongside RaspberryPints. I know people have done both, but it appears that there are defaults that need to be changed in RaspberryPints in order for it to work. Can anyone who has gotten this working chime in with some guidance or instructions? If worse comes to worst I guess I can just have a separate headless RPi running Fermentrack, and just access everything via the webpage, but I'd really prefer to only use the one RPi if possible. Thanks!
 
It's been years since I got BrewPi running on the same RPi as R'Pints, but as they both wanted to "own" index.php, something had to give.
As I needed four instances of BrewPi running on that system anyway, I rooted them below /var/www (or /var/www/html on my Jessie machines), which resolved the root file name conflict.

Didn't need to change anything on my R'Pints installation.

Might ping thorrak and see what his take on this might be, but I suspect if you install Fermentrack somewhere other than /var/www/html - and you've installed its dependencies - everything should work...

Cheers!
 
Thanks for the reply! Good to know that it's possible to get BrewPi, at least, to work alongside R'Pints!

I ended up getting errors related to nginx, which prevented anything from happening. I'm not super experienced with RPi, but from what I saw I didn't even have the opportunity to choose a directory. @Thorrak any thoughts here?
 

Attachments

  • install_log.txt
    17.4 KB · Views: 81
Last edited:
Finally got it working! Took me the whole evening, but I got it. Now I just have to remember what I did so I can write it up for others to use...
 
Thanks for the reply! Good to know that it's possible to get BrewPi, at least, to work alongside R'Pints!

I ended up getting errors related to nginx, which prevented anything from happening. I'm not super experienced with RPi, but from what I saw I didn't even have the opportunity to choose a directory. @Thorrak any thoughts here?

Here’s the docs I wrote for installing Fermentrack and RPints side-by-side using Nginx awhile back:
http://docs.fermentrack.com/en/master/getting started/Apache and PHP Support.html

I haven’t tested it with recent versions of Raspbian, however, so no guarantees it still works, but conceptually it should for any systems that have the names dependencies.
 
Those instructions helped me get there, but I did have to make a few changes. Off the top of my head, I had to trick it into looking for Jessie files on Stretch, same as I had to do to get R'Pints installed properly.
sudo nano /etc/apt/sources.list --> change stretch to jessie
sudo nano /etc/apt/sources.list.d/raspi.list --> change stretch to jessie
You have to make sure to change these back after you're done, or other stuff will be messed up. Even after doing this, although the rest of php5 installs fine, php5-fpm can't be obtained normally, so I had to download a .zip from the php website, and install it that way. I also had to make sure all the R'Pints files were in /etc/var/www/html, not just /etc/var/www. Before I fixed that, Fermentrack worked fine but R'Pints no longer did.

If I have time after brewing this weekend, I'm going to try to write a set of in-depth instructions for getting R'Pints and Fermentrack working together on Stretch. I'm going to do a fresh install for both on a different RPi, so I'll just keep track of everything I do. I'll post it here once I'm finished so hopefully nobody else has as much of a problem!
 
Last edited:
I'm running into some issues getting LAMP installed when using:

sudo apt-get -y install apache2 php5 mysql-client mysql-server php5-mysql phpmyadmin

I get the error that package php5 and php5-mysql are unavailable and do not have installation candidates. From what I am reading on other forums is that php5 isn't supported anymore so it will not install. Is there a way to get php5 otherwise or can I use the more recent version without issues? Any help would be much appreciated, I am trying to get this operational by next weekend. Thanks!

@Virginia_Ranger Did you ever get this up and running? You can absolutely get php5 and php5-mysql running on Stretch, you just have to do a workaround. R'Pints won't work with php7, so installing those newer versions won't help you with this. I have php5 running alongside php7, so I can run things that require either.
 
I'm having an issue with one of my taps - its not reporting a pour when I use it but when I use one of the other taps it registers pours to two taps. I likely have something hosed in my wiring/soldering but since was working for about 6 months before swapped out a keg I thought I thought I'd try another pin (I'm currently using 8, 9, 10 and 5) before I go tearing things apart. What other pins are available? I can change it in the DB and the wire to the board but I vaguely recall another change I need to make. I'm using an alamode board. Hope that makes sense
 
If you are using an Alamode board I can vouch for digital IO 2 and 5 through 11. I had issues with 3 & 4, and I'm not certain 12 and 13 will work (but might) as they are shared with other functions (the TOY clock and the LED).

fwiw, when using an UNO R3 I suspect 2 through 13 are all usable. I should test that one of these days but none of them are shared with anything so they should work.

btw, I haven't tried it, but it wouldn't surprise me that you could get those symptoms simply by duplicating the Tap ID between two taps. That scenario would fit yours...especially the sudden onset after tapping a keg...

Cheers!
 
If you are using an Alamode board I can vouch for digital IO 2 and 5 through 11. I had issues with 3 & 4, and I'm not certain 12 and 13 will work (but might) as they are shared with other functions (the TOY clock and the LED).

fwiw, when using an UNO R3 I suspect 2 through 13 are all usable. I should test that one of these days but none of them are shared with anything so they should work.

btw, I haven't tried it, but it wouldn't surprise me that you could get those symptoms simply by duplicating the Tap ID between two taps. That scenario would fit yours...especially the sudden onset after tapping a keg...

Cheers!
My first thought was wrong pin id but looks good in the taps table (although I think I checked the pin id not the tap id so that's a good suggestion). It does register as a pour on pins 9 AND 10 in the pours table when I pour out of 9 and nothing for what should be pour on pin 10 so I'm scratching my head a bit on that one. I guess I could try to kick the keg and re add it before I start messing with other items.

Wasn't there something to load on to the alamode board too that defined the pins? I thought there was some definition file there I need to upload to it but I'm going from memory from over a year ago (and many beers). Maybe I'm thinking of something else and my notes don't mention it - I may have been sampling too much. :)
 
Yes, the first few lines of raspberrypints.ino has two entries that need user-customization:

Code:
//This line is the number of flow sensors connected.
const uint8_t numSensors = 4;
//This line initializes an array with the pins connected to the flow sensors
uint8_t pulsePin[] = {8,9,10,11};

But the way the communication between Arduino and the mysql database is "wired" I don't think even double-clutching the pin list would result in what you're seeing....

Cheers!
 
Yes, the first few lines of raspberrypints.ino has two entries that need user-customization:

Code:
//This line is the number of flow sensors connected.
const uint8_t numSensors = 4;
//This line initializes an array with the pins connected to the flow sensors
uint8_t pulsePin[] = {8,9,10,11};

But the way the communication between Arduino and the mysql database is "wired" I don't think even double-clutching the pin list would result in what you're seeing....

Cheers!
Everything in the DB looks fine (no duplicated ids). Thought I just see if anything is coming back while monitoring so I do this:
$ sudo /etc/init.d/flowmon stop
$ sudo python /var/www/html/python/flow_monitor.py

But when I pour out of a tap that is working I get this:
There are no windows in the stack
Invlaid window '%1'
Usage: windowactiveate [options] [window=%1]
--sync - only exit once the window in the active (is visible + active)
If no window is given, %1 is used. See WINDOW STACK in xdotool(1)
^[[15;5~

I think its coming out of the refresh.sh file which is this:
#!/bin/bash
export DISPLAY=":0"
WID=$(xdotool search --onlyvisible --class chromium|head -1)
xdotool windowactivate ${WID}
xdotool key ctrl+F5

what am I missing?
 
Running the flow monitor from the command line used to work with Wheezy - you'd get a nice clean three line "pour" message with pin ID and volume and one more line that I can't remember.

But once the Jessie kit was released you get that mess instead. I think it's trying to pop a window for the output instead of directing it to the terminal session.

I think I would move one of your meters to a different pin, make the appropriate changes to the ino file and the tap list assignments, and see what happens...

Cheers!
 
On
Running the flow monitor from the command line used to work with Wheezy - you'd get a nice clean three line "pour" message with pin ID and volume and one more line that I can't remember.

But once the Jessie kit was released you get that mess instead. I think it's trying to pop a window for the output instead of directing it to the terminal session.

I think I would move one of your meters to a different pin, make the appropriate changes to the ino file and the tap list assignments, and see what happens...

Cheers!
Once again Day Tripper to the rescue - thanks. Wasn't sure what I was seeing - seemed to be something with xdotool but that's nothing I'm familiar with. I'll be digging into my setup this weekend - just looking to try to debug a bit while I have a few minutes.
 
Does anyone have the original index.php and style.css? I accidentally copied over the originals, and would rather not have to reinstall to get them back...

Also - does anyone have any suggestions on how to change those files to get things to display on a 7" screen? I have 5 taps, and plan to use the 7" Raspberry Pi touchscreen as the display, in landscape mode.
 
Does anyone have the original index.php and style.css? I accidentally copied over the originals, and would rather not have to reinstall to get them back...

Also - does anyone have any suggestions on how to change those files to get things to display on a 7" screen? I have 5 taps, and plan to use the 7" Raspberry Pi touchscreen as the display, in landscape mode.
Yeah, you should still have unadulterated copies of them in the original .zip you downloaded as part of the install. It'll be located in /home/pi just transfer it to your PC with Filezilla or WinSCP, or unzip in the home directory of your Pi.
 
More than a year, several reinstallations, many hours dabbling in code and learning my way around Linux, I have a working Pints system. Feel free to skip the rest of my rambling post - I'm stuck at home with kids and bored.

I installed the Tilt Hydrometer image to manage my fermentation logging to the cloud on the SD card first, then I installed Pints on the backend. My system is set up for seven flow meters, though I'm currently only running 4. I will finish installing my proximity sensor later this month (we had a birthday party and I was under time constraints. The wiring and software has already been installed, I just need to figure out where the hardware is going to go).

I ran two ethernet cables into my keezer to supply power and signal wires for the meters. These were run into a Carlon conduit enclosure. I purchased 3 wire PC fan extension wires to run into the enclosure. I had to swap two of the wires, as they were opposite from the adafruit flow meters I had purchased, but that was easy enough. I also purchased a quadcopter power board, which allowed me to solder the power wires together in an organized manner. Next, I somehow managed to solder the signal leads together without burning myself too much. These leads were also covered with heat shrink.

After I buttoned up the enclosure, I had to figure out which wire went to which lead for later pin assignment, which was easy enough with a multimeter set to continuity. My Pi was placed into an additional Carlon dual gang conduit box, as I have the alamode and could not find a sufficient case to house it. This worked out because I drilled a hole in the bottom, which is where my proximity sensor will be mounted in the coming weeks.

After everything was set to go, naturally it required a test. Three of the four faucets worked fine and updated my pours total - the fourth did not. I was several hours into working on the project, it was late, and I was tired, so I opted for bed. When I came back in the morning to troubleshoot the non-working meter, the first thing I checked was the wiring. Somehow I managed to wire meter #2 to wire #5. Because SWMBO was already ill with me playing with it while she was prepping for the party I decided the quickest fix would be to update the pin assignment in the administration page for now. After I did that, success!! It was quite the hit with the party guests. I did manage to assess that even after I had calibrated my meters last year, it is not calculating correctly, an easy enough fix. I used a cup of water through the meter last time to calculate it, this time I will use more. I poured a pint when I got home in the wee hours this morning and it only registered 12 oz poured.

In reality, the hardest part of the project for me was setting up the hardware - mainly the wiring - because I wanted something that would hold up and still look decent. I'm the kind of guy that will redo something five times if I don't like the way it looks.

In closing, thank you to the many people who helped this project become a success. I know there are several that contributed in small ways, but the two largest were day_tripper and kaljade.
 
After first having issue with pours not recording I'm now back into the ghost pouring phase. I've had this as an on/off issue since I first put it together. I thought/think it may be due to my taps being nearly the same height as the top of the keg so any foam built up in the lines tends to be all over the coils I have on top of the keg and the line never clears completely of air. My sensors are about a foot away from the keg with roughly 10ft of line after that coiled as best I can on top of the keg in my tight space.

This is from the db from last night - at some point about 5:30 am it started recording multiple pours a minute for various amounts. Although most are around 1oz there is a 42, 59, and 25 oz pours which effectively indicated my keg is empty when in fact is 2/3 full.

Could the air in the lines be part of it? I'm pretty limited for my setup until the kegerator dies.

I also noticed the sensors seem to come with a wiring diagram that indicate some resistors could be added between the pins - I haven't done anything with that - I'm guessing that a red herring but anyone done anything with that?

This can happen on any keg but right now its on a keg with its own line to the C02 while the 3 other kegs go through a 1x3 splitter to supply the CO2 from a separate reg. I could possibly understand if there is some slight fluctuations as the fridge kicks on an off but an ounce would a lot and there is no way it would be bigger than that.

Its getting rather annoying to have to babysit the DB to check for what appears to be invalid pours and then hope I'm removing the incorrect entries and not missing a bunch of others. I have been off by as much as 50-100 oz by time the keg kicks and I'm thinking it due to this but who knows.

sorry tough to read but you can see the time stamp and the last value is oz - I've shortened it but you get the idea
pulses modifiedDate ounces
31 9/23/2018 13:20 2.612
193 9/23/2018 6:15 1.17
342 9/23/2018 6:15 2.073
145 9/23/2018 6:01 0.879
157 9/23/2018 6:01 0.952
153 9/23/2018 6:01 0.927
187 9/23/2018 6:01 1.133
130 9/23/2018 6:01 0.788
187 9/23/2018 6:01 1.133
182 9/23/2018 6:01 1.103
148 9/23/2018 6:01 0.897
167 9/23/2018 6:01 1.012
148 9/23/2018 6:01 0.897
4208 9/23/2018 6:01 25.503
106 9/23/2018 5:35 0.642
119 9/23/2018 5:34 0.721
175 9/23/2018 5:34 1.061
242 9/23/2018 5:34 1.467
104 9/23/2018 5:34 0.63
301 9/23/2018 5:34 1.824
9888 9/23/2018 5:34 59.927
283 9/23/2018 5:31 1.715
173 9/23/2018 5:31 1.048
221 9/23/2018 5:31 1.339
224 9/23/2018 5:31 1.358
312 9/23/2018 5:31 1.891
240 9/23/2018 5:30 1.455
195 9/23/2018 5:30 1.182
240 9/23/2018 5:30 1.455
228 9/23/2018 5:30 1.382
191 9/23/2018 5:30 1.158
321 9/23/2018 5:30 1.945
229 9/23/2018 5:30 1.388
226 9/23/2018 5:30 1.37
291 9/23/2018 5:30 1.764
208 9/23/2018 5:30 1.261
204 9/23/2018 5:30 1.236
222 9/23/2018 5:30 1.345
197 9/23/2018 5:30 1.194
194 9/23/2018 5:30 1.176
198 9/23/2018 5:30 1.2
199 9/23/2018 5:30 1.206
205 9/23/2018 5:30 1.242
185 9/23/2018 5:30 1.121
191 9/23/2018 5:30 1.158
187 9/23/2018 5:29 1.133
183 9/23/2018 5:29 1.109
221 9/23/2018 5:29 1.339
196 9/23/2018 5:29 1.188
183 9/23/2018 5:29 1.109
215 9/23/2018 5:29 1.303
192 9/23/2018 5:29 1.164
199 9/23/2018 5:29 1.206
246 9/23/2018 5:29 1.491
239 9/23/2018 5:29 1.448
206 9/23/2018 5:29 1.248
212 9/23/2018 5:29 1.285
187 9/23/2018 5:29 1.133
194 9/23/2018 5:29 1.176
221 9/23/2018 5:29 1.339
184 9/23/2018 5:29 1.115
218 9/23/2018 5:29 1.321
175 9/23/2018 5:29 1.061
186 9/23/2018 5:29 1.127
171 9/23/2018 5:29 1.036
202 9/23/2018 5:29 1.224
172 9/23/2018 5:29 1.042
195 9/23/2018 5:29 1.182
179 9/23/2018 5:28 1.085
198 9/23/2018 5:28 1.2
185 9/23/2018 5:28 1.121
190 9/23/2018 5:28 1.152
186 9/23/2018 5:28 1.127
202 9/23/2018 5:28 1.224
193 9/23/2018 5:28 1.17
177 9/23/2018 5:28 1.073
200 9/23/2018 5:28 1.212
170 9/23/2018 5:28 1.03
240 9/23/2018 5:28 1.455
139 9/23/2018 5:28 0.842
174 9/23/2018 5:28 1.055
177 9/23/2018 5:28 1.073
171 9/23/2018 5:28 1.036
186 9/23/2018 5:28 1.127
167 9/23/2018 5:28 1.012
251 9/23/2018 5:28 1.521
191 9/23/2018 5:28 1.158
201 9/23/2018 5:28 1.218
194 9/23/2018 5:28 1.176
187 9/23/2018 5:28 1.133
262 9/23/2018 5:28 1.588
212 9/23/2018 5:27 1.285
192 9/23/2018 5:27 1.164
205 9/23/2018 5:27 1.242
191 9/23/2018 5:27 1.158
204 9/23/2018 5:27 1.236
188 9/23/2018 5:27 1.139
194 9/23/2018 5:27 1.176
197 9/23/2018 5:27 1.194
186 9/23/2018 5:27 1.127
224 9/23/2018 5:27 1.358
258 9/23/2018 5:27 1.564
211 9/23/2018 5:27 1.279
182 9/23/2018 5:27 1.103
204 9/23/2018 5:27 1.236
208 9/23/2018 5:27 1.261
201 9/23/2018 5:27 1.218
208 9/23/2018 5:27 1.261
202 9/23/2018 5:27 1.224
176 9/23/2018 5:27 1.067
187 9/23/2018 5:27 1.133
177 9/23/2018 5:27 1.073
194 9/23/2018 5:27 1.176
205 9/23/2018 5:27 1.242
203 9/23/2018 5:26 1.23
193 9/23/2018 5:26 1.17
193 9/23/2018 5:26 1.17
183 9/23/2018 5:26 1.109
194 9/23/2018 5:26 1.176
165 9/23/2018 5:26 1
184 9/23/2018 5:26 1.115
181 9/23/2018 5:26 1.097
173 9/23/2018 5:26 1.048
152 9/23/2018 5:26 0.921
194 9/23/2018 5:26 1.176
190 9/23/2018 5:26 1.152
204 9/23/2018 5:26 1.236
235 9/23/2018 5:26 1.424
204 9/23/2018 5:26 1.236
184 9/23/2018 5:26 1.115
192 9/23/2018 5:26 1.164
186 9/23/2018 5:26 1.127
196 9/23/2018 5:26 1.188
212 9/23/2018 5:26 1.285
213 9/23/2018 5:26 1.291
162 9/23/2018 5:26 0.982
185 9/23/2018 5:26 1.121
193 9/23/2018 5:25 1.17
199 9/23/2018 5:25 1.206
195 9/23/2018 5:25 1.182
192 9/23/2018 5:25 1.164
176 9/23/2018 5:25 1.067
200 9/23/2018 5:25 1.212
212 9/23/2018 5:25 1.285
204 9/23/2018 5:25 1.236
195 9/23/2018 5:25 1.182
176 9/23/2018 5:25 1.067
197 9/23/2018 5:25 1.194
249 9/23/2018 5:25 1.509
197 9/23/2018 5:25 1.194
185 9/23/2018 5:25 1.121
182 9/23/2018 5:25 1.103
195 9/23/2018 5:25 1.182
164 9/23/2018 5:25 0.994
183 9/23/2018 5:25 1.109
210 9/23/2018 5:25 1.273
215 9/23/2018 5:25 1.303
173 9/23/2018 5:25 1.048
191 9/23/2018 5:25 1.158
186 9/23/2018 5:25 1.127
219 9/23/2018 5:25 1.327
199 9/23/2018 5:24 1.206
230 9/23/2018 5:24 1.394
185 9/23/2018 5:24 1.121
198 9/23/2018 5:24 1.2
203 9/23/2018 5:24 1.23
206 9/23/2018 5:24 1.248
181 9/23/2018 5:24 1.097
192 9/23/2018 5:24 1.164
191 9/23/2018 5:24 1.158
186 9/23/2018 5:24 1.127
263 9/23/2018 5:24 1.594
180 9/23/2018 5:24 1.091
209 9/23/2018 5:24 1.267
188 9/23/2018 5:24 1.139
218 9/23/2018 5:24 1.321
204 9/23/2018 5:24 1.236
172 9/23/2018 5:24 1.042
213 9/23/2018 5:24 1.291
191 9/23/2018 5:24 1.158
202 9/23/2018 5:24 1.224
174 9/23/2018 5:24 1.055
211 9/23/2018 5:24 1.279
223 9/23/2018 5:24 1.352
201 9/23/2018 5:23 1.218
222 9/23/2018 5:23 1.345
185 9/23/2018 5:23 1.121
189 9/23/2018 5:23 1.145
202 9/23/2018 5:23 1.224
177 9/23/2018 5:23 1.073
243 9/23/2018 5:23 1.473
195 9/23/2018 5:23 1.182
200 9/23/2018 5:23 1.212
304 9/23/2018 5:23 1.842
173 9/23/2018 5:23 1.048
191 9/23/2018 5:23 1.158
194 9/23/2018 5:23 1.176
192 9/23/2018 5:23 1.164
207 9/23/2018 5:23 1.255
233 9/23/2018 5:23 1.412
200 9/23/2018 5:23 1.212
258 9/23/2018 5:23 1.564
201 9/23/2018 5:23 1.218
195 9/23/2018 5:23 1.182
211 9/23/2018 5:23 1.279
211 9/23/2018 5:23 1.279
215 9/23/2018 5:22 1.303
178 9/23/2018 5:22 1.079
197 9/23/2018 5:22 1.194
198 9/23/2018 5:22 1.2
226 9/23/2018 5:22 1.37
196 9/23/2018 5:22 1.188
188 9/23/2018 5:22 1.139
202 9/23/2018 5:22 1.224
229 9/23/2018 5:22 1.388
231 9/23/2018 5:22 1.4
197 9/23/2018 5:22 1.194
243 9/23/2018 5:22 1.473
237 9/23/2018 5:22 1.436
193 9/23/2018 5:22 1.17
280 9/23/2018 5:22 1.697
181 9/23/2018 5:22 1.097
235 9/23/2018 5:22 1.424
286 9/23/2018 5:22 1.733
275 9/23/2018 5:22 1.667
227 9/23/2018 5:21 1.376
196 9/23/2018 5:21 1.188
213 9/23/2018 5:21 1.291
816 9/23/2018 5:21 4.945
6950 9/23/2018 5:21 42.121
490 9/23/2018 5:19 2.97
235 9/23/2018 5:19 1.424
413.836
 
Last edited:
Gas traveling through idle lines is the culprit, and a mismatch between the carbonation level and the current gas pressure/temperature combination can often be the root cause of the constant outgassing. Another cause is large temperature swings inside the keezer.

wrt the two resistors you saw - Rs and Rl. Rs is a current limiter and is only needed if you're running the meters on greater than 5 volts and the value would be 50 ohms * (Voltage - 5). A 9V supply would require a 200 ohm resistor, but again in our application Rs is not needed.

Rl is a "pull-up" resistor and a 2.2K resistor is recommended. My R'Pints systems have that resistor going to 5 volts on each flow meter. To be honest I never tried running the meters without the pull-up resistors so I don't know for a fact that they are needed, but if you're having issues I'd put them in and see what happens (if anything)...

Cheers!
 
Day_trippr, how do I go about manually changing the number of ounces poured and number of ounces left that is displaying on my taplist. I had an issue where it didn't register a few 12 ounce pours so I want to update it to reflect the correct amounts.
 
Editing the R'Pints database is readily done using phpmyadmin (which should have been installed along the way to getting R'Pints running).
You will need to use the same username and password that you used during the original Mysql installation.

Before you do this I recommend making a backup copy of the database file: /var/lib/mysql/ibdata1 (there is no file extension).
Just copy it to the same /var/lib/mysql/ folder with a different name.

Once you have phpmyadmin up in a web browser, make sure the selected database is for raspberrypints (select it from the list box if not) then click on the 'pours' table entry below.

rpints_phpmyadmin_1.jpg


That will bring up the full pours table, where you can do all kinds of neat things like delete or edit existing records.

rpints_phpmyadmin_2.jpg



Note, I don't recall ever adding a record to the pours table, as there may be a "last record" pointer that would need to be altered - I don't know either way. The easiest way is to find a record with matching tapid and pinid (so it's for that specific keg on that tap) and modify it to bring your total pours on that keg up to where you think it should be...

Cheers!
 
After first having issue with pours not recording I'm now back into the ghost pouring phase. I've had this as an on/off issue since I first put it together. I thought/think it may be due to my taps being nearly the same height as the top of the keg so any foam built up in the lines tends to be all over the coils I have on top of the keg and the line never clears completely of air. My sensors are about a foot away from the keg with roughly 10ft of line after that coiled as best I can on top of the keg in my tight space.

This is from the db from last night - at some point about 5:30 am it started recording multiple pours a minute for various amounts. Although most are around 1oz there is a 42, 59, and 25 oz pours which effectively indicated my keg is empty when in fact is 2/3 full.

Could the air in the lines be part of it? I'm pretty limited for my setup until the kegerator dies.

I also noticed the sensors seem to come with a wiring diagram that indicate some resistors could be added between the pins - I haven't done anything with that - I'm guessing that a red herring but anyone done anything with that?

This can happen on any keg but right now its on a keg with its own line to the C02 while the 3 other kegs go through a 1x3 splitter to supply the CO2 from a separate reg. I could possibly understand if there is some slight fluctuations as the fridge kicks on an off but an ounce would a lot and there is no way it would be bigger than that.

Its getting rather annoying to have to babysit the DB to check for what appears to be invalid pours and then hope I'm removing the incorrect entries and not missing a bunch of others. I have been off by as much as 50-100 oz by time the keg kicks and I'm thinking it due to this but who knows.

sorry tough to read but you can see the time stamp and the last value is oz - I've shortened it but you get the idea
pulses modifiedDate ounces
31 9/23/2018 13:20 2.612
193 9/23/2018 6:15 1.17
342 9/23/2018 6:15 2.073
145 9/23/2018 6:01 0.879
157 9/23/2018 6:01 0.952
153 9/23/2018 6:01 0.927
187 9/23/2018 6:01 1.133
130 9/23/2018 6:01 0.788
187 9/23/2018 6:01 1.133
182 9/23/2018 6:01 1.103
148 9/23/2018 6:01 0.897
167 9/23/2018 6:01 1.012
148 9/23/2018 6:01 0.897
4208 9/23/2018 6:01 25.503
106 9/23/2018 5:35 0.642
119 9/23/2018 5:34 0.721
175 9/23/2018 5:34 1.061
242 9/23/2018 5:34 1.467
104 9/23/2018 5:34 0.63
301 9/23/2018 5:34 1.824
9888 9/23/2018 5:34 59.927
283 9/23/2018 5:31 1.715
173 9/23/2018 5:31 1.048
221 9/23/2018 5:31 1.339
224 9/23/2018 5:31 1.358
312 9/23/2018 5:31 1.891
240 9/23/2018 5:30 1.455
195 9/23/2018 5:30 1.182
240 9/23/2018 5:30 1.455
228 9/23/2018 5:30 1.382
191 9/23/2018 5:30 1.158
321 9/23/2018 5:30 1.945
229 9/23/2018 5:30 1.388
226 9/23/2018 5:30 1.37
291 9/23/2018 5:30 1.764
208 9/23/2018 5:30 1.261
204 9/23/2018 5:30 1.236
222 9/23/2018 5:30 1.345
197 9/23/2018 5:30 1.194
194 9/23/2018 5:30 1.176
198 9/23/2018 5:30 1.2
199 9/23/2018 5:30 1.206
205 9/23/2018 5:30 1.242
185 9/23/2018 5:30 1.121
191 9/23/2018 5:30 1.158
187 9/23/2018 5:29 1.133
183 9/23/2018 5:29 1.109
221 9/23/2018 5:29 1.339
196 9/23/2018 5:29 1.188
183 9/23/2018 5:29 1.109
215 9/23/2018 5:29 1.303
192 9/23/2018 5:29 1.164
199 9/23/2018 5:29 1.206
246 9/23/2018 5:29 1.491
239 9/23/2018 5:29 1.448
206 9/23/2018 5:29 1.248
212 9/23/2018 5:29 1.285
187 9/23/2018 5:29 1.133
194 9/23/2018 5:29 1.176
221 9/23/2018 5:29 1.339
184 9/23/2018 5:29 1.115
218 9/23/2018 5:29 1.321
175 9/23/2018 5:29 1.061
186 9/23/2018 5:29 1.127
171 9/23/2018 5:29 1.036
202 9/23/2018 5:29 1.224
172 9/23/2018 5:29 1.042
195 9/23/2018 5:29 1.182
179 9/23/2018 5:28 1.085
198 9/23/2018 5:28 1.2
185 9/23/2018 5:28 1.121
190 9/23/2018 5:28 1.152
186 9/23/2018 5:28 1.127
202 9/23/2018 5:28 1.224
193 9/23/2018 5:28 1.17
177 9/23/2018 5:28 1.073
200 9/23/2018 5:28 1.212
170 9/23/2018 5:28 1.03
240 9/23/2018 5:28 1.455
139 9/23/2018 5:28 0.842
174 9/23/2018 5:28 1.055
177 9/23/2018 5:28 1.073
171 9/23/2018 5:28 1.036
186 9/23/2018 5:28 1.127
167 9/23/2018 5:28 1.012
251 9/23/2018 5:28 1.521
191 9/23/2018 5:28 1.158
201 9/23/2018 5:28 1.218
194 9/23/2018 5:28 1.176
187 9/23/2018 5:28 1.133
262 9/23/2018 5:28 1.588
212 9/23/2018 5:27 1.285
192 9/23/2018 5:27 1.164
205 9/23/2018 5:27 1.242
191 9/23/2018 5:27 1.158
204 9/23/2018 5:27 1.236
188 9/23/2018 5:27 1.139
194 9/23/2018 5:27 1.176
197 9/23/2018 5:27 1.194
186 9/23/2018 5:27 1.127
224 9/23/2018 5:27 1.358
258 9/23/2018 5:27 1.564
211 9/23/2018 5:27 1.279
182 9/23/2018 5:27 1.103
204 9/23/2018 5:27 1.236
208 9/23/2018 5:27 1.261
201 9/23/2018 5:27 1.218
208 9/23/2018 5:27 1.261
202 9/23/2018 5:27 1.224
176 9/23/2018 5:27 1.067
187 9/23/2018 5:27 1.133
177 9/23/2018 5:27 1.073
194 9/23/2018 5:27 1.176
205 9/23/2018 5:27 1.242
203 9/23/2018 5:26 1.23
193 9/23/2018 5:26 1.17
193 9/23/2018 5:26 1.17
183 9/23/2018 5:26 1.109
194 9/23/2018 5:26 1.176
165 9/23/2018 5:26 1
184 9/23/2018 5:26 1.115
181 9/23/2018 5:26 1.097
173 9/23/2018 5:26 1.048
152 9/23/2018 5:26 0.921
194 9/23/2018 5:26 1.176
190 9/23/2018 5:26 1.152
204 9/23/2018 5:26 1.236
235 9/23/2018 5:26 1.424
204 9/23/2018 5:26 1.236
184 9/23/2018 5:26 1.115
192 9/23/2018 5:26 1.164
186 9/23/2018 5:26 1.127
196 9/23/2018 5:26 1.188
212 9/23/2018 5:26 1.285
213 9/23/2018 5:26 1.291
162 9/23/2018 5:26 0.982
185 9/23/2018 5:26 1.121
193 9/23/2018 5:25 1.17
199 9/23/2018 5:25 1.206
195 9/23/2018 5:25 1.182
192 9/23/2018 5:25 1.164
176 9/23/2018 5:25 1.067
200 9/23/2018 5:25 1.212
212 9/23/2018 5:25 1.285
204 9/23/2018 5:25 1.236
195 9/23/2018 5:25 1.182
176 9/23/2018 5:25 1.067
197 9/23/2018 5:25 1.194
249 9/23/2018 5:25 1.509
197 9/23/2018 5:25 1.194
185 9/23/2018 5:25 1.121
182 9/23/2018 5:25 1.103
195 9/23/2018 5:25 1.182
164 9/23/2018 5:25 0.994
183 9/23/2018 5:25 1.109
210 9/23/2018 5:25 1.273
215 9/23/2018 5:25 1.303
173 9/23/2018 5:25 1.048
191 9/23/2018 5:25 1.158
186 9/23/2018 5:25 1.127
219 9/23/2018 5:25 1.327
199 9/23/2018 5:24 1.206
230 9/23/2018 5:24 1.394
185 9/23/2018 5:24 1.121
198 9/23/2018 5:24 1.2
203 9/23/2018 5:24 1.23
206 9/23/2018 5:24 1.248
181 9/23/2018 5:24 1.097
192 9/23/2018 5:24 1.164
191 9/23/2018 5:24 1.158
186 9/23/2018 5:24 1.127
263 9/23/2018 5:24 1.594
180 9/23/2018 5:24 1.091
209 9/23/2018 5:24 1.267
188 9/23/2018 5:24 1.139
218 9/23/2018 5:24 1.321
204 9/23/2018 5:24 1.236
172 9/23/2018 5:24 1.042
213 9/23/2018 5:24 1.291
191 9/23/2018 5:24 1.158
202 9/23/2018 5:24 1.224
174 9/23/2018 5:24 1.055
211 9/23/2018 5:24 1.279
223 9/23/2018 5:24 1.352
201 9/23/2018 5:23 1.218
222 9/23/2018 5:23 1.345
185 9/23/2018 5:23 1.121
189 9/23/2018 5:23 1.145
202 9/23/2018 5:23 1.224
177 9/23/2018 5:23 1.073
243 9/23/2018 5:23 1.473
195 9/23/2018 5:23 1.182
200 9/23/2018 5:23 1.212
304 9/23/2018 5:23 1.842
173 9/23/2018 5:23 1.048
191 9/23/2018 5:23 1.158
194 9/23/2018 5:23 1.176
192 9/23/2018 5:23 1.164
207 9/23/2018 5:23 1.255
233 9/23/2018 5:23 1.412
200 9/23/2018 5:23 1.212
258 9/23/2018 5:23 1.564
201 9/23/2018 5:23 1.218
195 9/23/2018 5:23 1.182
211 9/23/2018 5:23 1.279
211 9/23/2018 5:23 1.279
215 9/23/2018 5:22 1.303
178 9/23/2018 5:22 1.079
197 9/23/2018 5:22 1.194
198 9/23/2018 5:22 1.2
226 9/23/2018 5:22 1.37
196 9/23/2018 5:22 1.188
188 9/23/2018 5:22 1.139
202 9/23/2018 5:22 1.224
229 9/23/2018 5:22 1.388
231 9/23/2018 5:22 1.4
197 9/23/2018 5:22 1.194
243 9/23/2018 5:22 1.473
237 9/23/2018 5:22 1.436
193 9/23/2018 5:22 1.17
280 9/23/2018 5:22 1.697
181 9/23/2018 5:22 1.097
235 9/23/2018 5:22 1.424
286 9/23/2018 5:22 1.733
275 9/23/2018 5:22 1.667
227 9/23/2018 5:21 1.376
196 9/23/2018 5:21 1.188
213 9/23/2018 5:21 1.291
816 9/23/2018 5:21 4.945
6950 9/23/2018 5:21 42.121
490 9/23/2018 5:19 2.97
235 9/23/2018 5:19 1.424
413.836


Rl is a "pull-up" resistor and a 2.2K resistor is recommended. My R'Pints systems have that resistor going to 5 volts on each flow meter. To be honest I never tried running the meters without the pull-up resistors so I don't know for a fact that they are needed, but if you're having issues I'd put them in and see what happens (if anything)...

Cheers!

If the flowmeter has an open collect/drain type output then there needs to be a pull resistor somewhere on the output line, preferablely at the input of the receiver if the flowmeter can be disconnected.

An open/floating input could give unpredictable results.

I know on some devices you can program a pull up resistor on input pins.
 
Last edited:
I'm sure it's probably been addressed, but I've just tried to install RaspberryPints on a relatively fresh install of raspbian (also running CraftBeerPi for my fermentation fridge). Managed to install it after placing the files in /var/www/html, got to the set up stage, input my taps etc all fine. When I put in my IP, I only come up with an Index of / page showing the files in the var/www/ folder. Anyone know how to fix this so I can actually display the taplist?
 
Unfortunately PHP5 is not available on the latest version of Raspbian, but if you upgrade to PHP7 the original Raspberry Pints code does not work because of removed functions Rpints uses.

Instead you could use a different fork of Rpints from GitHub that have been updated to use the new calls like mine https://github.com/rtlindne/RaspberryPints

After banging my head against the wall, I finally found this post and solved my issue. Thanks for going through and updating compatibility with PHP7. Good lookin' out.
 
Just finished installing RandR's Pints but script wont go through if I select "Load Sample data" and when I dont and script does finish BUT 127.0.0.1/index.php wont show anything at all and administrator page wont let me log in, any idea where im wrong? thanks
 
If the flowmeter has an open collect/drain type output then there needs to be a pull resistor somewhere on the output line, preferablely at the input of the receiver if the flowmeter can be disconnected.

An open/floating input could give unpredictable results.

I know on some devices you can program a pull up resistor on input pins.


Are you suggesting these should be put on the wires right at the flowmeter? I was thinking I'd just put in a bread board between the PI and the wires into the fridge as that would be the easiest.
 
I'm sure it's probably been addressed, but I've just tried to install RaspberryPints on a relatively fresh install of raspbian (also running CraftBeerPi for my fermentation fridge). Managed to install it after placing the files in /var/www/html, got to the set up stage, input my taps etc all fine. When I put in my IP, I only come up with an Index of / page showing the files in the var/www/ folder. Anyone know how to fix this so I can actually display the taplist?

Which Raspbian version are you using? It would give a hint as to which version of Apache2 you have.
The version of Apache2 that was included in Wheezy had inbound html requests resolved by default in /var/www, so when you use just a host's ip address, that's the folder the request will land in. If your target file isn't there, it won't be found.

Otoh, Jessie and Stretch shipped with a version of Apache2 that changed the default folder to /var/www/html, so if you put your target file in /var/www, it won't be found.

That default folder is referred to as the Apache2 DocumentRoot. It is defined by /etc/apache2/sites-available/default.conf (Wheezy) or 000-default.conf (Jessie and Stretch). If you open the appropriate .conf file you'll see it sets DocumentRoot /var/www or DocumentRoot /var/www/html.

So, bottom line, figure out where Apache2 wants the files to go, and move them there. Or, edit the .conf file to change DocumentRoot to where you want...

Cheers!
 
Are you suggesting these should be put on the wires right at the flowmeter? I was thinking I'd just put in a bread board between the PI and the wires into the fridge as that would be the easiest.

I used a small piece of perf board on stand-offs for the same purpose. Any passives that were needed ended up there...

Cheers!
 
I don't mean to question the master, but are you sure you have the pull up resistors in your builds? I don't remember those being required in the original Alamode build. I also seem to remember that you were mistaken about this once before. But I am almost assuredly wrong because you're the man for all of this stuff.
 
Never question the master, especially when he already raised the question you're asking ;)

"To be honest I never tried running the meters without the pull-up resistors so I don't know for a fact that they are needed"

While the presence of a pull-up in the SF800 "instructions" could be taken as a requirement, there's no characterization of the meter output circuit available to know for sure, and tbh I'm not inclined to remove a pull-up on my system to prove it isn't needed or not. I'll leave that to you folks ;)

Cheers!
 
I saw your response, but to be honest, I thought you might be going from memory on your answer. My poor memory remembers you checking on that a while back and finding it not to be the case. But I humbly stand corrected.
 
As I document everything (as an ee engineer it's what I do) I can assure you I have schematics showing a 2.2K pull-up on every meter.
But...I did that because the only information I had available showed a 2.2K pull-up to the meter VCC rail.
Engineering Philosophy 101: understand exactly, or copy precisely :D

Now, if the RPi digital IO were programmed to do so there'd be roughly 50K ohm pull-ups on each of them. I don't know if that was ever in the code, and even if it was I don't know that 50K would do the job...

Cheers!
 
lol!

btw, I acknowledge the original build instructions on raspberrypints.com never mentions these resistors. I don't know if that was oversight, or if they never saw any issues without them...

Cheers!
 
Are you suggesting these should be put on the wires right at the flowmeter? I was thinking I'd just put in a bread board between the PI and the wires into the fridge as that would be the easiest.

No I was not suggesting by the flowmeter, but to put it by the receiver(alamode). If you put the pull up resistors add them close to the receiving device like you said on your bread board.

If you added the resistor by the flowmeter or part of that assembly and the flowmeter assembly was removed the input would not have a pull up resistor and would be open. That also allow you to run with a meter removed if needed.

Did some more reading on the thread and the device on the alamode has built in pulls up when the data pin is configured as an input.

@day_trippr I looked at the sf800 website and there is not much information but I did find a couple webpages that said the SF800 is an open collector output.
https://www.eeweb.com/circuit-projects/flow-sensor-frequency-meter
 
Back
Top