I figured it out. i disabled the flow meter column and everything worked. I assume since I didnt have a pin, it failed. although it might be nice to have some error handling around it. It is, or should I say was, a vanilla build.
I looked into doing that and then i go into the file explorer in the Raspberry Pi and navigate to the /img directory it shows a thumbnail of what it it supposed to be and even when i change the background remotely through the RaspberryPints interface I see the thumbnail immediately change to whatever image I upload yet still wont change when i view the taplist on the RaspberryPi. I have no idea what is going on here.
Clearing the cache did work.
Thanks for all the input guys. It is much appreciated.
Any chance your optical registration is off by one pin?
I've never run into an issue like that, but if I did the first thing I'd do is get a fresh copy of the raspberrypints.ino file and start over.
And double check my wiring.
fwiw, I run six taps and use digital IO 2 and 5 through 9, and have not had a single problem in over two years.
Back when we first got the flow meters working I tried using 2 through 7 but had unresolved issues with 3 and 4.
On the AlaMode digital IO 3 is shared with the RTC chip on the back of the board so potential conflict there seemed logical, but I was never able to find a similar shared status for digital IO 4. As I didn't need to use it I simply avoided it as well...
Cheers!
Was hoping that someone can assist on this more me. Running an rp3 with Jessie and Firefox. Everything was working fine and the pours were showing in the browser just fine. Today all of a sudden Firefox is not updating after the pour. You have to refresh the browser to get the pour to update. How can you code to get Firefox to update every 30 seconds or so?
<meta http-equiv="refresh" content="30">
<html>
<head>
<title>RaspberryPints</title>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta http-equiv="refresh" content="30">
<!-- Set location of Cascading Style Sheet -->
<link rel="stylesheet" type="text/css" href="style.css">
<?php if($config[ConfigNames::UseHighResolution]) { ?>
<link rel="stylesheet" type="text/css" href="high-res.css">
<?php } ?>
<link rel="shortcut icon" href="img/pint.ico">
</head>
Just to test things out and make sure I'm not losing my mind and plugging things in in the wrong place I have only one sensor plugged in to pin 2 on the UNO (which is connected to the RPi3 through USB). I also flashed a fresh .ino with just pin 2 mentioned. It's working but it's updating the pour count to my tap #3 on the taplist.
Just to be clear, I'm using the numbers printed on the board itself. Is this correct?
In the raspberry pints software, when you are tapping a keg, you set the pin number that you have that flow meter connected to, to the tap number on your tap list. Check the settings on the beer you have hooked up to tap #3 and make sure that tap doesn't have pin 2 assigned to it.
Only two more things it can be:
1. Browser cache needs to be cleared (CTRL + F5 should do it)
2. File permissions there's a couple of ways to fix that, but try step 1 first
As long as you're in there not breaking stuff, you may want to take a look at the "pours" table. When the Pints software is installed, the table isn't set up to put a date/time stamp on the pour. If you enable that stamp, it makes troubleshooting phantom pours much easier since you can see pours very close together in time or at odd times of the day. If you don't have that set, the time date just shows "null". I also envision the time stamp will come in handy as my boys become teenagers.
Gentlemen,
First off, let me say thank you to those that have contributed to this and the original thread. I wish I had taken the time to read all of both of them BEFORE I made a parts order, LOL.
I'm working on an install on the RP3B that was installed using the current version of NOOBS to load Raspbian. I'm waiting for the Adafruit flow sensors to ship, they're currently on backorder, and thought I would knock out a majority of the system installation, save the hardware.
I was pleasantly surprised to find that Chromium is supported on the current version of Jessie, although that may have contributed to some of my errors. First off, I'm a newb when it comes to Linux. I managed to remove my permissions from the /var/www directory relatively quickly when the commands didn't work exactly as written. Luckily I am a master of Google-Fu and fixed it. So far I've spent about 3.5 hours fumbling through this install and I've only come to two issues. My first is I can't seem to get Chromium to autostart and direct it to my server. My second is I cannot, for the life of me, get the flowmeter function to work. Each time I run the command line it returns a "failure".
I should mention I plan on running an Alamode board - like I said, wish I had finished reading first. All that said, the first round of popcorn is on me. I'll give it another run in a few days when all the pieces are finally here and I'm no longer sleep deprived from work.
Hi there! day_trippr put a really good post on install updates on post# 2643. For Chromium to start on autostart, do the following:
...
As for the sensors failing, i'm thinking that since you do not have the actual sensors installed, they cannot provide any feedback to the programs. If you disable them until you install the hardware, it should work. TheSkaz had an issue where this resolved it in the last week or so. Post# 2681 and the preceding few posts.
Hi there! day_trippr put a really good post on install updates on post# 2643. For Chromium to start on autostart, do the following:
- Instead of using the autostart file shown in the instructions as
/etc/xdg/lxsession/LXDE-pi/autostart
use
/home/pi/config/lxsession/LXDE-pi/autostart
Should the latter location already exist? It doesn't on my installation, however the former does. It just doesn't autostart Chromium.
EDIT:
Fixed it. My file location was actually:
/home/pi/.config/lxsession/LXDE-pi/autostart
Pulls up perfectly now. All I need to do now is solder up my alamode, wait on the flow meters, and get that side installed properly.
Okay, so I still welcome responses to my first question, and my second for that matter, but I wanted to provide an update. Thinking of other things I could test/try, I switched out the motion sensor and DuPont wires for my spare and new ones, respectively - no effect. I inspected my autostart file (see prior post), and it appeared correct. I elected to save it without changing a thing. I shut the Pi down, installed the original sensor, and restarted. NOW it seems to work. Huh?Thanks to all those who have worked so hard and collaboratively to get newbies like me up and running. So, I am running Pints on a RPi 3, with a UNO to monitor my DIGITEN flow meters. I've added the HC SR501 PIR motion sensor for the screen saver. All was working great, but if it still were I wouldn't be writing. I have two questions.
1) did anyone have success in getting the motion sensor and screen saver to move a display into power saving mode? Please inform.
2) can anyone suggest a solution to my problem? I was finding that the motion sensors were plenty sensitive for my installation, which has my keezer and display in our kids' old toy closet. Thus, I mounted the sensor to my near ceiling height display pointed down and attached it to the back of the display, such that the display partially blocked the sensor. Once adjusted, this way it only turned the screen on when I entered the closet. It was sweet, and working great. However, the Velcro I used to mount the sensor allowed some range of movement of the sensor. The other day, I was trying to adjust and better affix it. The result was that the sensor is no longer controlling the screen saver. The only change was physical configuration.
Since, I have run pir_test.py to confirm sensor function, and it detects motion. I have also tried rebooting. No change.
Any ideas?
FWIW, here is my autostart file -
I'm all ears if you find a solution.
pi@raspberrypi:~ $ sudo apt-get -y install php5-mysql
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
php5-mysql : Depends: libmysqlclient18 but it is not installable
E: Unable to correct problems, you have held broken packages.
Enter your email address to join: