vitotai
OLED firmware restarts continuously
BrewPiLess.v4.2a4.4m2m.bin BrewPiLess.v4.2a4.oled.newui.4m2m.bin
There are two types of firmware. The same motherboard. The LCD version is normal but the display lacks characters after a few hours). The OLED version keeps restarting. what is the reason?
Turn on the iSpindel power switch. The OLED board will restart continuously. Turn off the iSpindel power switch, it will not restart.
https://user-images.githubusercontent.com/32890201/124131999-f1299480-dab2-11eb-9204-574998b478ed.mp4
The cycling LCD display is under verifying and development. I have tested it on OLED while all my OLED LCDs are broken.
Hello, I can provide the hardware you need for your experiment for free, including the experiment board of ESP8266 and ESP32, and also provide the display screen. How can I mail it to you?
Thank you, but what I need is time. I am hunting an issue of frozen display right now. It hasn't happened since I adding some debugging code a week ago. The issue of your LCD is strange, I can't reproduce it, either.
The OLED issue can be reproduced without hooking OLED. It seems that updating LCD takes too long to be done in HTTP session. I've made modification. Please try a5.
https://github.com/vitotai/BrewPiLess/tree/4.2pre
Building and pushing take some time to finish.
These are the four display states of OLED. The bottom row is scrolled. It is recommended to fix the time display on the first page and the IP display on the second page. So there are only 4 lines on the second page, and one line of voltage display is added.
There is only one Beer temperature sensor in the hardware setting, set Beer Set 20. Fridge temp:30 Fridge Set:10 These two are automatically generated?
Can you send me a bin with version 4.2 for oled and wemos d1 mini? I can't comple it.
你能给我寄一个 oled 和 wemos d1 mini 的 4.2 版本的 bin 吗？我无法完成它。
Don't use this software anymore. many problems. I have given up.
I have a problem with version without oled too. What version is stable? I have countinousely reboot.
Here the same thing is happening when I use ESP32. With ESP8266 it works as normal.
