View attachment 223277
Not finished but making some styling changes to all the tables <boo-but-cool>
Install xscreensaver from an LXDE terminal:
apt-get install xscreensaver
Cheers!
Mr. Tripper - your work is much appreciated. I was able to set this up the first time and it worked great. I can't believe how much fun a $4 sensor has added to my life. Perhaps that's a comment on an empty life?
Anyway, I had to add "sudo" before the above command in order to get and install the xscreensaver. Without it, the command gave me errors about not being the root user. I'm a Linux idiot, so it took me a few tries to figure out what was going on. I added sudo before and everything was smooth sailing from there. Is that an edit for your instructable for other dolts who follow, or is that by design and I had a problem with my directory rights, etc.?
Thanks again for your work.
[...]I am only currently concerned over the compatability with a RPi B+ that has 4 USB ports. I am concerned over the plug in capability of the AlaMode board.
Sorry I just thought of a follow up query. How close to my tap shanks can I mount the flow sensors without increasing the foam output? I currently have 10 feet of 3/16 " beer line, but I do not want the sensors and wiring hanging too far away from the beer shank mount point.
Thanks in advance.
Mike
fwiw, I have mine in the middle of 12' runs and sitting atop my kegs (pic below). I'll be doing a major overhaul of my keezer soon and will be replacing the tubing so the meters are within a running foot of the Out posts...
Cheers!
It's probably in the other R'Pints thread, but I posted a picture of an AlaMode atop a B+. It fits fine...
Cheers!
Cool and thanks for the input. I was not sure when they changed the GPIO header connector and was concerned over compatibility. I will worry about a case later.
Thanks again.
fwiw, I have mine in the middle of 12' runs and sitting atop my kegs (pic below). I'll be doing a major overhaul of my keezer soon and will be replacing the tubing so the meters are within a running foot of the Out posts...
Cheers!
fwiw, I have mine in the middle of 12' runs and sitting atop my kegs (pic below). I'll be doing a major overhaul of my keezer soon and will be replacing the tubing so the meters are within a running foot of the Out posts...
Cheers!
I use the famous DIY pump cleaners and I understand what you're saying.
But I have a solution using a beer QD, about 4 feet of beer line, and a corny keg beer post with a couple of adapters. Stick that on the pump and it'll provide the reach to get to the QDs inside the keezer...
Cheers!
I've seen some talk and saw one persons tap list have Untappd integrated into their RaspberryPints. Is there any documentation on how to do this?
Hope it is - that would be one cool feature. Of course, it would be great if they had badges for trying home brew as well... 😉
I don't have any documentation on how I did it and it's not complete by far. It may be in the V3 release if we ever get that far.
There is a badge for homebrew
Huh - I cannot seem to figure out how to add one of my own brews to the list then...
I was messing around with JonW index.php file and finally got everything the way I wanted it to look, but now when I start my Pi up, the chromium doesn't automatically start up. If I go to my laptop browser and type in the Pi's address I can see my taplist fine. I've also checked the "/etc/xdg/lxsession/LXDE/autostart" file and everything looks fine. Anyone have any suggestions?
Does the local console make it to the LXDE desktop?
Or is it stuck in CLI mode?
If you configured your system based on the "official instructions, your tap list would be started by this line in /etc/xdg/lxsession/LXDE/autostart"
@chromium -kiosk localhost (note the double-dash)
The 'localhost' url by default will look for index.html, index.php, etc. Make sure you don't have an index.html or you'll need more than just 'localhost' to get to your tap list. And make sure index.php has the proper ownership (either 'pi' or 'www-data' are typical users) and access rights.
If all else fails, look at the tail of /var/log/apache2/error.log as it is often very helpful...
Cheers!