dcrog
Well-Known Member
I thought I had done that already but give me a minute and I'll try it again.
http://url.from.desktop.equals not found/install/index.php
http://url.from.desktop.equals not found/install/index.php
I thought I had done that already but give me a minute and I'll try it again.
http://url.from.desktop.equals not found/install/index.php
$ sudo service mysql stop
I'm having a problem with my system. I add beers via the "add beers" page but when I go to tap a keg the new beers are not on the list. I looked in the database via phpmyadmin and they are in fact in the beer database but will not show up to be tapped. Any suggestions for a php novice?
No weird characters. But the problem is solved... I unplugged it and reconnected it a couple of times and it fixed itself. I appreciate self healing problems.
I totally get that, which is a compelling reason to keep the instructions around on how to do it the way we've been doing it, but not really a reason there can't ALSO be the option to do it using a stock image for those that aren't looking to do anything but run raspberrypints or who are starting there.
Just be careful doing that...enough hard reboots and it will corrupt your drive. I learned that the hard way with my first install, so hopefully you've made a backup once everything's good and setup to your liking.
I'm working on a new version of a tap list system, based on different hardware, and also a different software framework.
Beaglebone with Linux?
CaptnDelta thanks so much! IMHO these were much needed features. I wish I was familiar with the languages that you guys are coding in so that I could contribute. Is there any chance of integrating some sort of RFID based user consumption stats into the new build? I ask mainly because you've already integrated the solenoid valve into the interface and I think that sort of feature would really lend itself best to allowing or disallowing beer pouring based on who is an authenticated user or whose account is in good standing or something like that.
Also I have been working on seeing of I can get raspberry pints to see d me an email or text in certain instances and so far I have gotten it to be able to send me a text and email when a beer is poured, but I can't seem to figure out how to add in the details I want into the email/text such as which beer it was and how much was poured. What is the best way to pass this info into the python script?
import smtplib
from email.mime.text import MIMEText
msg = MIMEText('your msg text goes here')
me = '[email protected]'
you = '[email protected]'
msg['Subject'] = 'The contents of foo'
msg['From'] = me
msg['To'] = you
s = smtplib.SMTP( 'localhost' )
s.sendmail(me, [you], msg.as_string())
s.quit()
Havent installed in a while but I seem to remember that chromium is not available for whatever flavor they changed the os to. Did you use noobs? Look back a few pages and you should be able to find the working version of raspbian that you can get chromium on. When I am in front of a computer I will work on it for you.
Can't offer a fix, but I downloaded Chromium on a new raspberry pi this weekend, no issues.
I did use noobs, based on the instructions for deploying RaspberryPints and when watching the install, it looks like it's 'jessie'.
So if I want to go with the 'wheezy', then I have to do the entire install from the beginning with recovery, correct?
Unfortunately, yes. It looks like there is no compiled version of chromium available for Jessie. Wheezy has an older version that you can still download and use.
Save yourself the trouble of using noobs and just download the raspbian wheezy from https://www.raspberrypi.org/downloads/raspbian/. Unfortunately you probably will have to go through the entire setup process again.
Hi folks,
So, I made my updates last nite, but didn't get around to testing with actual flow meters, since SWMBO was already in bed and the whistling of me blowing thru the flow meters would have driven her mad...
Got around to testing today, and also added a few things that should make dealing with the flow meter stuff a little easier.
This means that you won't have to fiddle with the arduino IDE anymore to change parameters (in fact they are no longer in the same form in the code). You still have to install the arduino software (RPints uses it internally), but no need to change anything in that anymore and upload it etc..
- The RPints software now flashes the binary (the compiled arduino .ino file) to the alamode when it starts up. The hex file for this is included in the distribution.
- The alamode software (the one that was flashed) is now able to listen for configuration parameters. What they are is explained below.
Now for the mentioned parameters:
When changing the tap config, the software now uploads the number of flow meters and their pin numbers.
It also uploads:
As a note, all but the last parameter were already in the original .ino file, they ware just hardcoded values.
- the pour message delay: This is the time in milli-seconds that we wait for more counts to come in after the counter already stopped. It basically waits for that amount of time after the flow already stopped to see if it restarts again to be considered for the pour
- the pour trigger count: that's the minimum flow meter count that needs to be received before it is considered a pour. For high-resolution meters like the swissflow, this should probably be around 200 to 300 (the original value was 300). For low-resolution meters, this needs to be set lower to not miss smaller pours (I got it at 25 on mine)
- the kick trigger count: this is the count the flow meters need to issue within one millisecond to kick the keg. The original value was 30 for swissflow meters. This may not work too well on lower resolution meters, I set mine to 5 and it's not always triggering. If you don't want your keg to automatically be kicked when this counter trips, set this to a high value (500 should do for any counter)
- the pour update count: This is the count after which the alamode reports a flow update to RPints. This is currently only used for the automatic shutoff when large pours occur. For high-resolution meters, a good value is probably around 1500 or 2000. For low-resolution meters, I've set mine to 250. If this value is too low for your flow meters, it may make the alamode miss pour counts, so high is better than low.
The screen shot attached below shows the tap config screen as it is now, and you can see the text fields to change the alamode parameters in the middle. When you hit "Update Alamode Config", or if you hit any "Save Tap Config" or if you reduce the number of taps, the alamode is reset, the parameters are uploaded, and the alamode is again ready to count with the new settings. This process takes about 2 seconds.
As far as installing: I already posted some instructions a few posts ago here:
https://www.homebrewtalk.com/showpost.php?p=7130076&postcount=1387.
Some additional notes on that:
Make sure you get the right Zip file from the github page, that page wants to switch on you to the master branch, but the changes are all in the 'Version2' branch. Here is a direct link to the zip file:
https://github.com/HentschelT/RaspberryPints/archive/Version2.zip
If you get thru the install, and the Pints web site shows up for the first time, in the admin panel go to the 'personalize' page (the little gear in the upper right corner), and enable everything but '4k monitor support' for now. Hit save.
With that you can set up your taps in the tap config panel by hitting "My tap config" on the left. You can set the valve pins even tho you don't have anything hooked up, it just doesn't do anything. You can use '0' for all valves, or use the valve pin values in the screen shot, they should be ok, but *don't* ever use pin 18, it resets the alamode.
If you get up and running, you can disable solenoids and fan support in the personalize page (it can always be turned on later).
To trouble shoot your (non-reading) flow meters: the flowmon service now logs what it has been up to to the file /var/log/rpints.log. This file gets overwritten when the service is restarted (just so it doesn't fill up your sd card over time). This also means that in case of trouble, you'll have to save that file *before* rebooting or restarting the flowmon service, so that we have a chance to see what went wrong.
You can look at this log via:
if you wanna see it update live in a terminal, useCode:more /var/log/rpints.log
Code:tail -f /var/log/rpints.log
Good luck with the install, post any problems into the thread here. For a meaningful problem report, please include the following two files:
* /var/log/apache2/error.log
* /var/log/rpints.log
You can rename those to a .xml extension since the forum software doesn't allow you something with an extension with .log (silly stuff)...
Whatever you do, make sure to have good backups of your current stuff!
Have fun,
-Th
Enter your email address to join: