Please attach or send me /var/log/apache2/error.log. This will tell me what the problem is.
You'd still have to do the stuff at the end of step 9, which starts with
sudo cp flowmon /etc/init.dsudo /etc/init.d/flowmon start
ps aux | grep PintDispatchsudo update-rc.d flowmon defaultsmore /var/log/rpints.logsudo service flowmon stop
sudo service flowmon start
sudo service flowmon restart
tail -f /var/log/rpints.logsudo cp /var/www/python/flowmon /etc/init.d/sudo /etc/init.d/flowmon start
ps aux | grep flow_monitor.py
So, I thought about your scenario, and made a few extra changes. First off, as I mentioned, if the raspberrypints.hex file is not present in the admin/arduino/raspberrypints directory, then it will not even attempt to flash the sketch. You'll have to do that yourself, with the .ino sketch provided in the download. There is nothing to change in there, just compile and upload.
I also reorganized things a bit, so that for your setup things should be easier to work with. Basically, here is how it should work for you:
* Power off your nano
* Make any configuration changes necessary via the web interface (add/remove taps, change parameters, etc).
* Then start your nano, the new settings will be uploaded via BT.
I also added logic that when you happen to power cycle your nano, the RPints flow monitor part senses that, restarts itself, uploads the config parameters, and your nano should be ready to count pours.
I don't have a nano here, so the only way for me to test it was to emulate that behavior thru resetting the Alamode from the outside. I'd be interested to see it work out, make sure to send me your rpints.log file when you try it.
I also added a new file in the python directory called Config.py. This is for expert level parameters (like changing the serial port), which is probably not something needed in the web interface. You'll have to change the serial port there to the one that's used by your BT device.
Make sure to grab the latest from github, and backup your current stuff
Good luck,
-Th
Hehe, no prob, take your time, github is still gonna be here tomorrow (hopefully
)Yea, I'm afraid there is quite a bit of work on your part necessary to get that working. Those BT boards typically don't have access to the DTR line on the Uno, so it would mean to add a few wires between the BT board and the Uno. And even if you do that, it's not guaranteed that your boot loader on the Uno supports hex uploads from anything but the USB port, so you most likely would have to change the boot loader too...
Yea, that's true for your case, but i.e. if you wanna try out the auto-kick feature, you'll probably have to fiddle a few times with that value. Doing that w/o reflashing is probably a bit easier on you...
Yes, "Jessie" switched to apache 2.4 which has /var/www/html as default (reason being security concerns). If you wanna use flow meters, and move it to /var/www/html, you need to edit the code in at least 2 other places, otherwise it won't work (in the flowmon python script and the service start/stop script). Otherwise you can also edit /etc/apache2/sites-enabled/000-default and reset it there to /var/www
The post how to fix this is here:
I made some updates/bug-fixes and added some features to RPints in the version discussed here and forward: https://www.homebrewtalk.com/showthread.php?p=7128949#post7128949
So I went to our hardware folks at work, and they gave me a Nano, one of the guys there even had a bluetooth board in his desk...
Hooked it up to the RPints, and yes, the power cycling part works
Just comes right back, gets the config and starts counting, takes about a second or so after the nano is plugged back in.
Also, started porting the Pints stuff to the BeagleBone Black, should make the whole thing a bit cheaper.
Cheers,
-Th
BTW, one thing I meant to ask you: Are you powering your Nano with batteries?
if( $remaining > 0 ){
?><div class="abv-offthechart"></div><?php
} if( $abv > 9.0 ){
?><div class="abv-offthechart"></div><?php
}
