All good, reset the EEPROM and all working as it should be. Thanks heapsView attachment 622655
Will that be an update to Fermentrack or to the ESP itself?As a side note, Espressif released an update earlier this week that will allow me to finally squish this bug for good. The update to the firmware is probably a bit over a month away if I was to guess.
Apologies - there sound like there are two bugs here:Will that be an update to Fermentrack or to the ESP itself?
The error happened again, just before, it counted down for around an hour, then fixed itself and went back onto idle
What's important is whether or not the beer temp is stable - not how much heat or cool runs. It looks to me like it's doing that job. How much volume in the fermenter right now? What size chamber? Are you using a fan? What size heater? Are you sure the sensor is all the way in the beer?Can someone else upload a screen capture of what their system does when holding a Beer Constant of 21 Degrees Celsius (69.8 F). I have only used an STC-1000 before this system, and now it looks like it runs way too much to hold that temp. What setting do i need to adjust to just it more ability to fluctuate the temp.
Yeah was gonna tell you that you fragged your card. Never ever ever just pull the power on your Pi. Always execute a proper shutdown.I ended up starting over and flashing the raspbian lite image and following the instructions that were provided. Seems to be working now
What's important is whether or not the beer temp is stable - not how much heat or cool runs. It looks to me like it's doing that job. How much volume in the fermenter right now? What size chamber? Are you using a fan? What size heater? Are you sure the sensor is all the way in the beer?
Yeah was gonna tell you that you fragged your card. Never ever ever just pull the power on your Pi. Always execute a proper shutdown.
Beer constant sets a fridge setpoint based on the beer's temp needs. I think with a heat belt it will work, but might overshoot a bit because the fridge temp never changes while the belt is on. Perhaps someone who has experience with that exact setup will be able to add some color.Currently fermenting 22l inside of a fridge (around 220l). I have a 20w Heat Belt wrapped around the middle of the fermentor. I just have never seen this much activity for cooling/heating as my on STC-1000 was not tracked like i can do now. The question was really just about the amount of temp activity i have and is it normal
Apr 23 2019 18:44:16 Controller debug message: INFO MESSAGE 18: Negative peak detected: 65.6, estimated: 67.0. Previous cool estimator: 11.314, New cool estimator: 13.811.
Apr 25 2019 04:05:12 Controller debug message: WARNING 2: Temperature sensor disconnected pin 0, address 2822AF8F1E130180
Apr 25 2019 04:05:12 Controller debug message: INFO MESSAGE 0: Temp sensor connected on pin 0, address 2822AF8F1E130180
Apr 25 2019 15:10:16 Controller debug message: WARNING 2: Temperature sensor disconnected pin 0, address 2822AF8F1E130180
Apr 25 2019 15:10:16 Controller debug message: INFO MESSAGE 0: Temp sensor connected on pin 0, address 2822AF8F1E130180
Apr 25 2019 16:21:29 Controller debug message: WARNING 2: Temperature sensor disconnected pin 0, address 2822AF8F1E130180
Apr 25 2019 16:21:29 Controller debug message: INFO MESSAGE 0: Temp sensor connected on pin 0, address 2822AF8F1E130180
Apr 25 2019 21:40:25 Controller debug message: WARNING 2: Temperature sensor disconnected pin 0, address 2822AF8F1E130180
Apr 25 2019 21:40:25 Controller debug message: INFO MESSAGE 0: Temp sensor connected on pin 0, address 2822AF8F1E130180
Apr 25 2019 21:43:27 Controller debug message: WARNING 2: Temperature sensor disconnected pin 0, address 2822AF8F1E130180
--------------------------------@phreaky
I had this issue, disconnecting and reconnecting within the same second, and a new power supply sorted it. I think the sensors are a bit sensitive to a bad power supply.
@Jerrydfl
When you power up the ESP use your phone to scan for WiFi networks and you should see the ESP as a network. Connect to it and then refresh your phone browser. You should now see a page in the browser where you can connect to your home WiFi and enter your home WiFi credentials. That will get the ESP on your home network.
Might sound like a simple question but,
If the raspberry Pi loses power, will the brewpi running on a ESP still continue to operate autonomously?
Well, I don't have a definite answer for your temp swings. If it were me I'd look for the PID constants and see where they are set versus a stock setup. I honestly don't know where those are on Fermentrack but I'm sure they are there somewhere. Just speaking purely from a PID loop perspective, it's got way too much P gain (kP in BrewPi).
I like your hardware setup. If I were to make a suggestion it would be to place the fan so that it circulates air in the chamber, not just across the heater. Something, maybe even a second fan, blowing so that it mixes the air below and above the shelf. There's no such thing as too much fan in there.
Also, I can't see it but it looks like you have a very short chamber temp which is likely not touching anything - that's good. If you have a longer one, something like this would help to keep it from touching anything:
@gromitdj drew this up and I have it included in the thing files for the BrewPi case on Thingiverse.
Well crap!
Flashed: April 29, 2019, 1:55 p.m.
Status: failed
Firmware Flashed: TiltBridge - 0.1 - 1
Board Type Selected: ESP32 - ESP32
Serial Port Used: /dev/ttyUSB3
Result Text: Flash process returned code 2
esptool.py v2.6
Serial port /dev/ttyUSB3
Connecting........_____....._____....._____....._____....._____....._____....._____
A fatal error occurred: Failed to connect to ESP32: Timed out waiting for packet header
(***FIXED, well Kinda***)
Apparently there is something wrong with my USB to UART Bridge. My fix was to hold down the Boot button as I was flashing with Fermentrack. Fermentrack was able to successfully flash my ESP32. Connecting the WiFi worked as planned.
Also, all my controllers become disabled. Not certain why, but this is what I’m doing to get it to happen: (Flash ESP32 procedure) disconnect power, connect controllers via USB, try to flash the ESP32, unsuccessful flash, disconnect USB’s, reconnect power...and all my devices are “Disabled, Pending an update”...then I have to change my devices to, “Active,managed by Circus” for everything to work again.
Enter your email address to join: