[Version 2 Release] RaspberryPints - Digital Taplist Solution
- Thread starter skemp45
- Start date
Help Support Homebrew Talk:
I was looking at this morass of data wondering WTF is all THAT about? 
I don't think incorporating the whole recipe in tabular form was what the authors ever intended.
Considering how long it's taken just to realize what a "hard break" is, you might want to strip things down to one word per beer to get started...
Cheers!
I don't think incorporating the whole recipe in tabular form was what the authors ever intended.
Considering how long it's taken just to realize what a "hard break" is, you might want to strip things down to one word per beer to get started...
Cheers!
I was looking at this morass of data wondering WTF is all THAT about?
I don't think incorporating the whole recipe in tabular form was what the authors ever intended.
Considering how long it's taken just to realize what a "hard break" is, you might want to strip things down to one word per beer to get started...
Cheers!
yeah perhaps, I've just never heard a carriage return or line feed called a hard break before...but perhaps that is just the 17+ years of IT in me...LOL...plus, I saw in the default beers more data then what I had in there, so i figured, character limits wasn't an issue...not realizing where I copied FROM had those CR's and LF's built in...but, of course not "human visible" in the programs I was using at the time....but no worries, it's npp from here on out for me to avoid that hopefully in the future...
we got it working properly now CaptnDelta, day_trippr...many many thanks...I select a beer and it pulls the info I've populated from the table as expected.
thanks again for your help, and also your patience with me :rockin:
Excellent! Now, go forth and make a backup!
Then have fun with it!
Then have fun with it!
Excellent! Now, go forth and make a backup!
Then have fun with it!
thanks, LOL....now, don't shoot me or anything....but....how do you make your backups? for my other rpi projects, I just normally image my SD....you?
![Craft A Brew - Safale BE-256 Yeast - Fermentis - Belgian Ale Dry Yeast - For Belgian & Strong Ales - Ingredients for Home Brewing - Beer Making Supplies - [3 Pack]](https://m.media-amazon.com/images/I/51bcKEwQmWL._SL500_.jpg)
Yup, I do most backups using Win32diskimager with a card reader.
I also did a live backup just in case...
Cheers!
I also did a live backup just in case...
Cheers!
yeah, that's one of the programs I've used before too.
how did you do a live backup?
It's a process.
I wrote it up on hbt a little while back, lemme Google-Fu that beyotch...
.
.
.
Ok, start with this post, which will provide a link to the holy grail of RPi live backups.
Then go to this post where I posted the procedure with all of the console commands and responses.
If you keep that one on the screen as you go you'll be able to see what I saw at each step.
Should be a confidence enhancer
Why a live backup? Because win32diskimager (like most imagers) does a block copy to a single file for the full extent of the SD card.
And if you try to use that to write a replacement card and that card is even one block smaller in capacity, you're fooked.
A live backup, otoh, can create a clone even if it's substantially smaller than the card in the system.
As long as the target card is larger than the used space on the original, you can create a clone...
Cheers!
I wrote it up on hbt a little while back, lemme Google-Fu that beyotch...
.
.
.
Ok, start with this post, which will provide a link to the holy grail of RPi live backups.
Then go to this post where I posted the procedure with all of the console commands and responses.
If you keep that one on the screen as you go you'll be able to see what I saw at each step.
Should be a confidence enhancer
Why a live backup? Because win32diskimager (like most imagers) does a block copy to a single file for the full extent of the SD card.
And if you try to use that to write a replacement card and that card is even one block smaller in capacity, you're fooked.
A live backup, otoh, can create a clone even if it's substantially smaller than the card in the system.
As long as the target card is larger than the used space on the original, you can create a clone...
Cheers!
fwiw, my SF800 meters are 12" from the beer QDs and 11 feet from the faucet shank couplers.
[edit] Aside from the stout on beer gas, the other five are @ 12 psi.
All line is 3/16" ID Bevlex-200, this would not work with BevSeal Ultra 235.
Perfect pours from all six faucets.
Also, there's a 40mm tower cooler and a 120mm stirring fan involved, both run 24/7.
Together there's no stratification inside the keezer and the tower is usually within 10°F of the keezer...
Cheers!
[edit] Aside from the stout on beer gas, the other five are @ 12 psi.
All line is 3/16" ID Bevlex-200, this would not work with BevSeal Ultra 235.
Perfect pours from all six faucets.
Also, there's a 40mm tower cooler and a 120mm stirring fan involved, both run 24/7.
Together there's no stratification inside the keezer and the tower is usually within 10°F of the keezer...
Cheers!
Wow. I am running about 11 feet of line from meter to tap and 1 foot from keg to meter. 11-12 psi at about 40 F with no real foam issue. Maybe a touch more than I got pre-adding the meters but not bad at all.
What is your serving pressue? How high do you carb?
CadiBrewer
Well-Known Member
I upgraded my Pi from a B to a new Pi 2. In order to upgrade, I updated all of the packages, etc. on the old Pi, then booted the new Pi with the SD card. Everything worked well and it booted okay, but now I'm not getting my pours updated and the Chromium browser doesn't start automatically on boot.
I tried a couple of things with the Python script, but I'm in over my head. Here's what I get from an lxterminal when I run the Python script and pour a tap. Any suggestions before I try reinstalling from scratch?
View attachment 1456701869974.jpg
I tried a couple of things with the Python script, but I'm in over my head. Here's what I get from an lxterminal when I run the Python script and pour a tap. Any suggestions before I try reinstalling from scratch?
View attachment 1456701869974.jpg
CadiBrewer
Well-Known Member
Shameless bump for some help before I resort to reinstalling everything.
If Chromium runs properly when manually launched, you likely put its auto-run stuff in the wrong LXDE-startup folder
(at some point Wheezy moved the cheese
).We used to use /etc/xdg/lxsession/LXDE/autostart, but now you should use /etc/xdg/lxsession/LXDE-pi/autostart (note the '-pi'). Give that a try.
As for the pours, if you do
Code:
$ sudo /etc/init.d/flowmon startfollowed by
Code:
$ sudo /etc/init.d/flowmon statusThe response should be
Code:
[ ok ] /var/www/python/flow_monitor.py is running.Cheers!
I am currently reinstalling mine from scratch and Jessie has given me some strife. I am caught up on the flowmonitor stuff as well. One thing I caught and wonder if may be part of the problem, yet may be part of mine instead is didnt Jessie move the folder from /var/www to var/www/html? Shouldnt Rpints and the like have been copied to the html folder?
Then again, wouldnt that have required the /var/www references in the flowmonitor.py etc to be updated to /var/www/html? Is this where I am screwing up myself?
and to make the autolaunch thing work, I did what DroneDeveloper reccomends here https://www.raspberrypi.org/forums/viewtopic.php?f=36&t=122444 in the second post. I am using iceweasel because I cant get chromium working on my Pi B (I dont have a 2). Copying the desktop shortcut to the autostart folder works great for me though. and since I put it in fullscreen mode then alt-f4 to close when it starts it does so in full screen mode.
I believe the whole /var/www/html thing is actually due changes made in the 2.4 release of Apache2 (which likely fell into the same time frame as the Jessie release).
By default there is a file link at /etc/apache2/sites-enabled/000-default.conf
which points to the file /etc/apache2/sites-available/000-default.conf
You can edit the latter and change the DocumentRoot from /var/www/html to /var/www.
It'll take a restart of Apache (or a system restart) to make that change effective, but it should make things behave.
Of course you'll want to actually locate the R'Pints tree there as well
Cheers!
By default there is a file link at /etc/apache2/sites-enabled/000-default.conf
which points to the file /etc/apache2/sites-available/000-default.conf
You can edit the latter and change the DocumentRoot from /var/www/html to /var/www.
It'll take a restart of Apache (or a system restart) to make that change effective, but it should make things behave.
Of course you'll want to actually locate the R'Pints tree there as well
Cheers!
nice. Looks like I may be reinstalling pints again tomorrow.
Reformatted, installed raspbian (unfortunately Jessie is all that's available) managed with lots of help from Google to get to step 9.
It looks like they updated the alamode-setup today. That version did not work for me. Luckily I had an older version on my computer and loaded that up.
I took @day_trippr 's advice to save trouble by taking the html folder part out of the equation. Now when trying to run the flowmon service I get this.
View attachment 1456852392858.jpg
Thoughts?
Edit: 2:25 PM
Figured it out. It appears that you can no longer use step 9 with Jessie and get the service working. It seems this is due to Jessie now using systemctl to run/manage services. Here is what I did to make mine work.
Following Step 9, I ran
$ sudo cp flowmon /etc/init.d
then for permissions
$ sudo chmod a+x /etc/init.d/flowmon
since $ sudo /etc/init.d/flowmon start $ ps aux | grep flow_monitor.py does not work for me and gave me the above pictured error I started working with systemctl as per the workaround detailed in the post at 2014-12-17 22:41 http://forums.debian.net/viewtopic.php?f=5&t=119485
$ sudo cp /run/systemd/generator.late flow.service /run/systemd
$ sudo cp /run/systemd/generator.late flowmon.service /run/systemd
Then I ran flowmon
$ sudo systemctl start flowmon
Then to confirm it is running
$ sudo systemctl status flowmon
Then to make it start at startup
$ sudo systemctl enable flowmon
From there I picked back up at the part where you reboot the pi and did step 10. Tested and all is well.
It looks like they updated the alamode-setup today. That version did not work for me. Luckily I had an older version on my computer and loaded that up.
I took @day_trippr 's advice to save trouble by taking the html folder part out of the equation. Now when trying to run the flowmon service I get this.
View attachment 1456852392858.jpg
Thoughts?
Edit: 2:25 PM
Figured it out. It appears that you can no longer use step 9 with Jessie and get the service working. It seems this is due to Jessie now using systemctl to run/manage services. Here is what I did to make mine work.
Following Step 9, I ran
$ sudo cp flowmon /etc/init.d
then for permissions
$ sudo chmod a+x /etc/init.d/flowmon
since $ sudo /etc/init.d/flowmon start $ ps aux | grep flow_monitor.py does not work for me and gave me the above pictured error I started working with systemctl as per the workaround detailed in the post at 2014-12-17 22:41 http://forums.debian.net/viewtopic.php?f=5&t=119485
$ sudo cp /run/systemd/generator.late flow.service /run/systemd
$ sudo cp /run/systemd/generator.late flowmon.service /run/systemd
Then I ran flowmon
$ sudo systemctl start flowmon
Then to confirm it is running
$ sudo systemctl status flowmon
Then to make it start at startup
$ sudo systemctl enable flowmon
From there I picked back up at the part where you reboot the pi and did step 10. Tested and all is well.
Oh, and if anyone needs the "how I finagled it into working on Raspian Jessie" here is what I did different from the instructions
Since just downloading the image of Raspian Jessie is not the same as NOOBS I first set up the display Rotation and Resolution
Then since there is no automatically running Configuration Tool I typed the following in to launch the equivalent
$ Sudo raspi-config
This allowed me to set my timezone, keyboard type (it defaulted to GB rather than US), expand file system, etc
Then I Set up Internet (I used the ethernet port and not wifi)
$ sudo nano /etc/dhcpcd.conf
and entered the following at the bottom
interface eth0
static ip_address=192.168.1.55/24
static routers=192.168.1.1
static domain_name_servers=192.168.1.1
...Continued with normal directions until step 4
Since Chromium does not work for me I installed iceweasel (the masking does not work which sucks but oh well)
$ sudo apt-get -y install iceweasel
to get it to autorun on startup I did the following
Click the Menu button, then expand Internet and right click Iceweasel and choose Add to Desktop
Then in terminal window I typed the following to make it autorun
$ sudo cp /home/pi/Desktop/iceweasel.desktop /home/pi/.config/autostart/iceweasel.desktop
$ cd /home/pi/.config/autostart/
$ sudo nano iceweasel.desktop
Scrolled to the bottom and changed
Exec=iceweasel %u
to
Exec=iceweasel http://localhost
saved and closed. Then I ran iceweasel and hit F-11 to fullscreen. Alt-f4 to close and now when it launches it will launch fullscreen. Nifty huh?
Back to the walkthrough from the site
until... Screen Blanking. This never works twice for me so I brute forced it
$ sudo apt-get xscreensaver
Then Menu > Preferences > Screensaver and changed Mode to Disable Screen Saver. Take that screen blanking.
Then as @day_trippr suggested adjusted the www/html thing
$ sudo nano /etc/apache2/sites-available/000-default.conf
changed the DocumentRoot from /var/www/html to /var/www
Back to your regularly scheduled setup instructions. (hopefully the alamode-setup thing gets fixed, otherwise I will find some way to get you the copy I downloaded previously)
You will use the command
$ sudo ./jessie-setup
instead of $ sudo ./setup
back to the setup document until Step 9 where do do what I did in my above post.
I believe this covers everything. Let me know if you have any questions but it is working for me.
Also, a question for those who have used theirs all this time. When was the last time you thoroughly inspected and cleaned your flowmeters? I am embarassed to say that I found that two of mine were not working. I replaced them with spares I bought (which are working) and pulled an dusgusting amount of hair, lint, and other crap out of them. They now work again but yuck.
Since just downloading the image of Raspian Jessie is not the same as NOOBS I first set up the display Rotation and Resolution
Then since there is no automatically running Configuration Tool I typed the following in to launch the equivalent
$ Sudo raspi-config
This allowed me to set my timezone, keyboard type (it defaulted to GB rather than US), expand file system, etc
Then I Set up Internet (I used the ethernet port and not wifi)
$ sudo nano /etc/dhcpcd.conf
and entered the following at the bottom
interface eth0
static ip_address=192.168.1.55/24
static routers=192.168.1.1
static domain_name_servers=192.168.1.1
...Continued with normal directions until step 4
Since Chromium does not work for me I installed iceweasel (the masking does not work which sucks but oh well)
$ sudo apt-get -y install iceweasel
to get it to autorun on startup I did the following
Click the Menu button, then expand Internet and right click Iceweasel and choose Add to Desktop
Then in terminal window I typed the following to make it autorun
$ sudo cp /home/pi/Desktop/iceweasel.desktop /home/pi/.config/autostart/iceweasel.desktop
$ cd /home/pi/.config/autostart/
$ sudo nano iceweasel.desktop
Scrolled to the bottom and changed
Exec=iceweasel %u
to
Exec=iceweasel http://localhost
saved and closed. Then I ran iceweasel and hit F-11 to fullscreen. Alt-f4 to close and now when it launches it will launch fullscreen. Nifty huh?
Back to the walkthrough from the site
until... Screen Blanking. This never works twice for me so I brute forced it
$ sudo apt-get xscreensaver
Then Menu > Preferences > Screensaver and changed Mode to Disable Screen Saver. Take that screen blanking.
Then as @day_trippr suggested adjusted the www/html thing
$ sudo nano /etc/apache2/sites-available/000-default.conf
changed the DocumentRoot from /var/www/html to /var/www
Back to your regularly scheduled setup instructions. (hopefully the alamode-setup thing gets fixed, otherwise I will find some way to get you the copy I downloaded previously)
You will use the command
$ sudo ./jessie-setup
instead of $ sudo ./setup
back to the setup document until Step 9 where do do what I did in my above post.
I believe this covers everything. Let me know if you have any questions but it is working for me.
Also, a question for those who have used theirs all this time. When was the last time you thoroughly inspected and cleaned your flowmeters? I am embarassed to say that I found that two of mine were not working. I replaced them with spares I bought (which are working) and pulled an dusgusting amount of hair, lint, and other crap out of them. They now work again but yuck.
First, thank you for taking the time to write those two posts.
This place works best when folks kick in stuff when they run into - and especially, solve - issues.
Second...eeeeeewwwwww! Where have your meters been??
I installed my six meters almost 18 months ago with the release of 2.0.1.
Up until now I haven't had any reason to pop 'em out of service for a full inspection.
So, thanks for that
Cheers!
This place works best when folks kick in stuff when they run into - and especially, solve - issues.
Second...eeeeeewwwwww! Where have your meters been??
I installed my six meters almost 18 months ago with the release of 2.0.1.
Up until now I haven't had any reason to pop 'em out of service for a full inspection.
So, thanks for that
Cheers!
First, thank you for taking the time to write those two posts.
This place works best when folks kick in stuff when they run into - and especially, solve - issues.
Second...eeeeeewwwwww! Where have your meters been??
I installed my six meters almost 18 months ago with the release of 2.0.1.
Up until now I haven't had any reason to pop 'em out of service for a full inspection.
So, thanks for that
Cheers!
Well. I am embarrassed to say that I have configured it 3 times this week so I wrote it for my reference then was inspired to share. I just hope it helps someone. I tell you though. Jessie has slowed my Pi B down drastically compared to Wheezy.
Yeah. I was surprised too. My only guess is that it either came in from little bits of debris left in the kegs, fermenters, etc and or came in through my keg line cleaning and sanitizing system. It got bad enough that the pinwheel in the meter was not spinning. I got some of the cheap sf800s so yeah... Wouldn't be a bad idea to check yours.
CadiBrewer
Well-Known Member
If Chromium runs properly when manually launched, you likely put its auto-run stuff in the wrong LXDE-startup folder
(at some point Wheezy moved the cheese
We used to use /etc/xdg/lxsession/LXDE/autostart, but now you should use /etc/xdg/lxsession/LXDE-pi/autostart (note the '-pi'). Give that a try.
Cheers!
So I think I figured out what is happening to me, but I'm still having a problem. I keep trying to update my sd card on my old pi so I can run it on the new pi. Somewhere in the upgrade process, it does what you're saying, which is the upgrade causes wheezy to look for the autostart stuff in LXDE-pi instead of LXDE where it currently resides on my machine.
After the upgrade, I've been trying to write stuff to the autostart file in LXDE-pi, but I've gotten permission issues and I can't write there. I tried sudo chmod -R 777 / and I borked my system and had to start over from a clean backup point. I realize now that changing all of the file permissions for every folder under / is a terrible idea. What is the right way to go about getting the proper permissions for the folders that the upgrade is changing?
Hmmm... If the file was there a sudo nano /etc/xdg/lxsession/LXDE-pi/autostart should have worked as the sudo part uses administration credentials. You should have had no issue. What happened when you tried? Did you get a black file? An error? The file names and locations are care sensitive.
CadiBrewer
Well-Known Member
I'll try it again tonight when I get home. I think I tried it from the GUI and that gave me the permission error. I was trying to cut and paste from one autostart to the other, hence the GUI. I'll try the terminal with sudo and give it another shot.
Copy paste works in nano. You could also use leafpad or vi. Just use the mouse and right click to copy/paste
I installed my six meters almost 18 months ago with the release of 2.0.1.
Up until now I haven't had any reason to pop 'em out of service for a full inspection.
So, thanks for that
Cheers!
Day Tripper
Question for you about cleaning the lines. Do you leave you Swiss flows inline during cleaning? Could the solution damage the sensor?
Matt
Yes, I have a manifold that accepts all six beer QDs and hooks up to a pond pump in a bucket of BLC mix, with return lines slipped over the faucet spouts.
So everything except the kegs is exposed to the cleaner.
I've run cleaner through the meters at least monthly for 18 months, and there's been no apparent status change.
In our favor, these meters have a lot of experience in dispensing systems where CIP is the rule.
And the materials are rated well wrt the sodium hydroxide concentrations and temperatures typically used for cleaning (eg: standard BLC/water mix).
At this point I'm pretty comfortable about the whole thing
Cheers!
So everything except the kegs is exposed to the cleaner.
I've run cleaner through the meters at least monthly for 18 months, and there's been no apparent status change.
In our favor, these meters have a lot of experience in dispensing systems where CIP is the rule.
And the materials are rated well wrt the sodium hydroxide concentrations and temperatures typically used for cleaning (eg: standard BLC/water mix).
At this point I'm pretty comfortable about the whole thing
Cheers!
Off topic. I have been looking to build/buy a manifold like this. Where did you find the manifold?
CadiBrewer
Well-Known Member
Thanks for everyone's help. I'm back up and running on a new Pi2, with a BrewPi working as well. Now to make my BrewPi look nicer in a case, and then to repurpose the old Pi into a controller for my smoker...
Similar threads
