thyirishmen
Well-Known Member
Anyone hook up a tilt. Mine starts logging and then stops and each graph after is same temp and gravity but when I open up phone tilt app it's updating every 10 sec. My fermentrack is on a pi 3 b+
If I had to guess I’d say you have a stuck relay - those cheap relay modules I find to be very susceptible to such issues.
Alternatively, if you changed your device constants that could also explain a change in behaviour.
I changed the beer setting constant after it started to act strange to see if it would correct it but didn't seem to. I have the Pi connected to a SainSmart Uno arduino. Maybe I need to reflash the arduino or something?
Edit: I'm just going to replace the relay module like you mentioned and see if that works
If you do have non default device constants, you can post them here and we can let you know if anything looks funky... based on the plot the chamber temperature is following the chamber set point quite well, so that’d be my guess. Or just reset the device constants to the defaults.
Hi Thorrak,
Thanks for all the work making (and supporting) Fermentrack. Back in the original thread you mentioned that support for glycol-chilled fermenters was on the to-do list (somewhere down the line). I'm curious as to your thoughts on whether you think this would work for a single fermenter with Fermentrak as currently written (maybe with some modifications to the PID variables): having a reservoir of liquid that acts as the "fridge" by being circulated through coils in (or a jacket outside) the fermenter, and then controlling the temperature of the liquid as you currently control the fridge now. I was thinking of a 4-8 gallon reservoir of water (or glycol solution) in a cooler with an aquarium chiller on the "cool" circuit and an aquarium heater on the "heat" circuit.
For a single fermenter I'm sure it would be simpler to just put the fermenter in a fridge, but I think this might work better for my planned brew space.
I just installed Fermentrack a couple of days ago after using Brewpi for the last couple of years. It started great until last night there were some really weird fluctuations. I did change the beer constant this morning to 70 because it had dipped down to 66 while at a 68 setpoint.
Any suggestions why this would have such a dramatic change?
I don't currently have plans to run more than one fermenter; I agree that it gets much more complicated for multiple fermenters.Fermentrack will support whatever you throw at it - the issues you'll face will be with the BrewPi controllers. That said, what you're discussing doesn't sound unreasonable. You might need some custom wiring/sensors in addition to BrewPi if your plan is to use a single reservoir for multiple fermenters, but that depends on how exactly you design your glycol circuit.
Happy to be a guinea pig whenever I get my conical set up!Unfortunately, glycol support isn't something I've prioritized adding to the ESP firmware as I have no means of testing it in my apartment. I'll try to add it using what has worked for others, but it will unfortunately remain a black box to me until I can find somewhere with more space.
Does Fermentrack not plot the actual cooling and heating states ala BrewPi?
That'd be a show-stopper for me...
Cheers!
[edit] The info might be in those traces - I dunno - but the colors are so indistinguishable it's impossible to tell...
It tracks it, but doesn’t plot it. If anyone knows dygraphs and is willing to help, I’d appreciate it. Working with dygraphs was one of the more painful parts of getting Fermentrack built...
Is there a reason your using Dygraphs instead of something like charts.js? I know nothing of your setup so keep that in mind lol.
I have a bit of a different setup here. I had access to a mac mini that has both wifi and bluetooth so I figured I would attempt to put the raspian OS on and install Fermentrack to work with my new Tilt. Not being a linux guy, I fumbled my way through the install and got it up and running and managed to get Fermentrack installed. I have run the configuration and I can add the tilt but when I look at the tilt page, I get the following message: Bluetooth packages for python have not been installed. Tilt support will not work. Click here to learn how to resolve this issue.
I ran through the steps in the resolution but I get a couple of error codes when I run the pip install pybluez. The first error comes back saying:
error: invalid command 'bdist_wheel'
And later in the script I get this error:
In file included from bluez/btmodule.c:20:0:
bluez/btmodule.h:5:33: fatal error: bluetooth/bluetooth.h: No such file or directory
#include <bluetooth/bluetooth.h>
Any idea on how to resolve this?
Cheers
See - What makes me sad is that I haven't yet found out how to get FindChips to give me a price for a complete BoM rather than each of the components within a BoM. That is - I want it to say, "Buying everything from Mouser costs $16.95, Buying everything from Digikey costs $19.02." Even better if it included shipping.
I am still trying to figure out why it wont work with my Pi 3 B+ and i bought a second one and it will not connect. If i put it in my PI 3 standard like i have it in now, it has been communicating to it for 14 days with no issues. If i switch the card back in again it does not pick it up.Very quick update on Tilt support:
For the past two months there's been a lack of official updates to Fermentrack available to users of either the dev or master branch as I've been focused on a handful of unreleased features - mostly focused on Tilt Hydrometer support/improvements. One of the features I'm working on now is a complete rewrite of both the Tilt monitor & configuration code.
Amongst other things, the rewrite is going to change a handful of the values associated with the TiltConfiguration object, including:
While I'm not anticipating much of an impact, if anyone out there has had to change the bluetooth_device_id parameter to get your Tilt to connect, let me know and I'll see if I can find a way to re-create that setting somewhere.
- Remove the average_period_secs option for smoothing data coming from the Tilt
- Change median_window_vals to smoothing_window_vals and only provide a moving average function (not median filter)
- Remove the option to set a bluetooth_device_id
I am still trying to figure out why it wont work with my Pi 3 B+ and i bought a second one and it will not connect. If i put it in my PI 3 standard like i have it in now, it has been communicating to it for 14 days with no issues. If i switch the card back in again it does not pick it up.
the image is Strech with latest Fermentrack and did latest get update and get upgrade.
Bummer.. I haven't tried yet but I also have a 3 B+ and a tilt. TiltPi works really well on it so I'm not sure its a bluetooth issue.I'm guessing that it has something to do with the Bluetooth receiver in the B+, but it's very strange. One thing I'm adding in the upcoming update is the ability to see what the signal strength was on the last received broadcast from each Tilt. Not sure how helpful it will ultimately be, but it might be an interesting diagnostic point!
Bummer.. I haven't tried yet but I also have a 3 B+ and a tilt. TiltPi works really well on it so I'm not sure its a bluetooth issue.
Thanks for your work on this!!TBQH, neither am I. After playing with it a bit, I decided to just rip out & rewrite everything from scratch. I'm in the process now of testing everything & finishing up a few new features - my hope is to have everything released to dev within the next two weeks.
any tips on getting fermentrack to auto connect with a wemos d1 mini? I've got what is the most recent fermentrack build on a pi zero w and the wemos is powered properly through Thorrak's wonderful PCBA (I can see the pythonwifi)
Perhaps a thumb drive is preventing the software from seeing the comm ports open up during the process? I connect the USB cable when the procedure prompts me to, and I can see the comm port open in my device manager but it fails to detect any differences in my serial bus.
Perhaps I should just flash the wemos and connect it to my wifi manually? Anyone have a good procedure for that?
Do you know the exact device name of the Wemos (something beginning with /dev/)? If so, I can add a feature to the flash mechanism to let you specify the path directly without using the autodetection process.
Enter your email address to join: