• Please visit and share your knowledge at our sister communities:
  • If you have not, please join our official Homebrewing Facebook Group!

    Homebrewing Facebook Group

TiltBridge - Tilt-to-WiFi Device for Tilt Hydrometer

Homebrew Talk

Help Support Homebrew Talk:

This site may earn a commission from merchant affiliate links, including eBay, Amazon, and others.
Unless you have either changed computers since it worked last or the driver has been uninstalled by other software. Try installing these drivers:

https://www.silabs.com/developers/usb-to-uart-bridge-vcp-drivers
So, I wasn't seeing the 'demand' for drivers - no 'Other devices' arriving to apply the drivers against. I happily installed the drivers mentioned but alas no difference. I did try the same PC as it was originally flashed with - along with a couple of others. It so looks like I'm using a power-only USB cable (I'm not) or the CH340 chip has indeed taken a dive.
 
As part of some upcoming work on Fermentrack, I've designed a standalone, docker-friendly Tilt daemon which I'm calling "TiltBridge Junior". This is not something that the vast majority of people need to know/care about, but for those select few who might want to turn their Raspberry Pi into a tilt receiver (but who don't want to install either Tilt Pi or Fermentrack) it might be helpful. The source code is on GitHub here.

Right now, it's specifically designed with an eye towards Fermentrack, but I'm happy for anyone interested to add other targets that are also supported in the ESP32 TiltBridge. It should work with BrewPi-Remix as well but I've not had a chance to test it (and lets be honest, if you're using BPR, why not just use the code @LBussy already has built in?).
 
I'm trying to create an account at tiltbridge. I filled in the sign-up portion and it said it sent me an email to confirm the address, but I never got one. I tried to just sign in, but it said the email had not been confirmed yet. I tried to reset the password, and it said it sent me an email, which I never received. Same thing happens on the phone app (android). Yes, I have the correct email entered. :)
 
It’s possible that I didn’t set the download correctly in BrewFlasher, or it’s possible that I mislabeled the version in the firmware.

That aside - what exactly were you experiencing with calibration?
I too still have the issue where calibration equations disappear after a few days and so I have to go back and set them back up.
But if I don't notice it, then it mucks up my logging to Brewers Friend and there are too many data points to go back and edit.
I am running v1.1.3 [master] (e8240ef)
 
I too still have the issue where calibration equations disappear after a few days and so I have to go back and set them back up.
But if I don't notice it, then it mucks up my logging to Brewers Friend and there are too many data points to go back and edit.
I am running v1.1.3 [master] (e8240ef)
Is it only the calibration data that is being lost, or is it other configuration options as well?
 
I’m trying to flash my new TiltBridge using BrewFlasher desktop and the web version. The desktop never worked, it always said “Firmware flashing FAILED. esptool.py raised an error. Try flashing again, or try flashing with a slower speed.” I tried slower speeds and always got the same error - even at the lowest speed! The web version seems to have worked - at least it said it was successful and didn’t throw any errors. Although now it’s not creating the wifi point. Here are the details:

This is the hardware:
I connected the parts and connected it to a PC via USB and the light on the board started flashing. I started the BrewFlasher (v.1.5.2 for windows) app and used these options:

Serial Port- Auto-select port
Project - TitlBridge
Device Family - ESP32 (the only one available)
Firmware- TiltBridge - v1.2.1 - TFT
Baud Rate- 230400
Erase flash- Yes, wipes all data

This is the error log:

Verifying firmware list is up-to-date before downloading...
Downloading firmware...
Downloading partitions file...
Downloading SPIFFS/LittleFS file...
Downloading bootloader file...
Downloading otadata file...
Downloading main firmware file...
Downloaded successfully!

Command: esptool.py --chip esp32 --baud 74880 --before default_reset --after hard_reset write_flash 0x10000 C:\Users\kimpa\AppData\Local\Temp\firmware.bin 0x8000 C:\Users\kimpa\AppData\Local\Temp\partitions.bin 0x1000 C:\Users\kimpa\AppData\Local\Temp\bootloader.bin 0x330000 C:\Users\kimpa\AppData\Local\Temp\spiffs.bin 0xe000 C:\Users\kimpa\AppData\Local\Temp\otadata.bin --erase-all -fs detect

esptool.py v4.6.2
Found 1 serial ports
Serial port COM4
Connecting.......
Chip is ESP32-D0WD-V3 (revision v3.0)
Features: WiFi, BT, Dual Core, 240MHz, VRef calibration in efuse, Coding Scheme None
Crystal is 40MHz
MAC: c8:f0:9e:71:a0:10
Uploading stub...
Running stub...
Stub running...
Configuring flash size...
Auto-detected Flash size: 16MB
Erasing flash (this may take a while)...
Chip erase completed successfully in 0.0s
Compressed 12 bytes to 20...
Writing at 0x00010000... (100 %)
Wrote 12 bytes (20 compressed) at 0x00010000 in 0.0 seconds (effective 6.1 kbit/s)...
File md5: 0ebab0ef3c513282b156b91165674d34
Flash md5: 713e15afa2ab6727d6f09e517f5e7a25
MD5 of 0xFF is c1fa1f22fa36d331be4027e683baad06
Firmware flashing FAILED. esptool.py raised an error.

Try flashing again, or try flashing with a slower speed.


I tried slower speeds, and the BETA D32_Pro_TFT firmware and got the same errors.

I then tried using the web version of BrewFlasher with the same options as above and clicked on “Flash to Controller.” It started, showed it’s progress, finished a couple minutes later and said it was successful. The log said:


MicroPython v1.20.0-124-g17c3f6b6aa on 2023-05-08; LOLIN D32 PRO with ESP32
Type "help()" for more information.
>>> ets Jul 29 2019 12:21:46

rst:0x1 (POWERON_RESET),boot:0x37 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:1
load:0x3fff0030,len:4560
load:0x40078000,len:14548
ho 0 tail 12 room 4
load:0x40080400,len:3928
entry 0x4008062c
MicroPython v1.20.0-124-g17c3f6b6aa on 2023-05-08; LOLIN D32 PRO with ESP32
Type "help()" for more information.


The thing is now it doesn’t seem to be creating the wifi point. It does not show up on the PC I did all of the above, my phone (android) nor a Chromebook. The screen on the board is blank as well, though, this may be normal at this point.

Any ideas, anyone?

Thanks!
 
I’m trying to flash my new TiltBridge using BrewFlasher desktop and the web version. The desktop never worked, it always said “Firmware flashing FAILED. esptool.py raised an error. Try flashing again, or try flashing with a slower speed.” I tried slower speeds and always got the same error - even at the lowest speed! The web version seems to have worked - at least it said it was successful and didn’t throw any errors. Although now it’s not creating the wifi point. Here are the details:

This is the hardware:
I connected the parts and connected it to a PC via USB and the light on the board started flashing. I started the BrewFlasher (v.1.5.2 for windows) app and used these options:

Serial Port- Auto-select port
Project - TitlBridge
Device Family - ESP32 (the only one available)
Firmware- TiltBridge - v1.2.1 - TFT
Baud Rate- 230400
Erase flash- Yes, wipes all data

This is the error log:

Verifying firmware list is up-to-date before downloading...
Downloading firmware...
Downloading partitions file...
Downloading SPIFFS/LittleFS file...
Downloading bootloader file...
Downloading otadata file...
Downloading main firmware file...
Downloaded successfully!

Command: esptool.py --chip esp32 --baud 74880 --before default_reset --after hard_reset write_flash 0x10000 C:\Users\kimpa\AppData\Local\Temp\firmware.bin 0x8000 C:\Users\kimpa\AppData\Local\Temp\partitions.bin 0x1000 C:\Users\kimpa\AppData\Local\Temp\bootloader.bin 0x330000 C:\Users\kimpa\AppData\Local\Temp\spiffs.bin 0xe000 C:\Users\kimpa\AppData\Local\Temp\otadata.bin --erase-all -fs detect

esptool.py v4.6.2
Found 1 serial ports
Serial port COM4
Connecting.......
Chip is ESP32-D0WD-V3 (revision v3.0)
Features: WiFi, BT, Dual Core, 240MHz, VRef calibration in efuse, Coding Scheme None
Crystal is 40MHz
MAC: c8:f0:9e:71:a0:10
Uploading stub...
Running stub...
Stub running...
Configuring flash size...
Auto-detected Flash size: 16MB
Erasing flash (this may take a while)...
Chip erase completed successfully in 0.0s
Compressed 12 bytes to 20...
Writing at 0x00010000... (100 %)
Wrote 12 bytes (20 compressed) at 0x00010000 in 0.0 seconds (effective 6.1 kbit/s)...
File md5: 0ebab0ef3c513282b156b91165674d34
Flash md5: 713e15afa2ab6727d6f09e517f5e7a25
MD5 of 0xFF is c1fa1f22fa36d331be4027e683baad06
Firmware flashing FAILED. esptool.py raised an error.

Try flashing again, or try flashing with a slower speed.


I tried slower speeds, and the BETA D32_Pro_TFT firmware and got the same errors.

I then tried using the web version of BrewFlasher with the same options as above and clicked on “Flash to Controller.” It started, showed it’s progress, finished a couple minutes later and said it was successful. The log said:


MicroPython v1.20.0-124-g17c3f6b6aa on 2023-05-08; LOLIN D32 PRO with ESP32
Type "help()" for more information.
>>> ets Jul 29 2019 12:21:46

rst:0x1 (POWERON_RESET),boot:0x37 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:1
load:0x3fff0030,len:4560
load:0x40078000,len:14548
ho 0 tail 12 room 4
load:0x40080400,len:3928
entry 0x4008062c
MicroPython v1.20.0-124-g17c3f6b6aa on 2023-05-08; LOLIN D32 PRO with ESP32
Type "help()" for more information.


The thing is now it doesn’t seem to be creating the wifi point. It does not show up on the PC I did all of the above, my phone (android) nor a Chromebook. The screen on the board is blank as well, though, this may be normal at this point.

Any ideas, anyone?

Thanks!

There's definitely some strange stuff going on in there. The fact that your logs reference MicroPython indicates that it definitely didn't flash correctly. Additionally, "Chip erase completed successfully in 0.0s" and "Compressed 12 bytes to 20..." indicate additional problems (the chip erase took 28.4s for me, and the firmware being flashed should be much larger than 20 bytes uncompressed).

I would try a couple things:
  • Try flashing the board at either 460800 bps or 115200 bps (I can personally attest that both of these work with this board, where other speeds might not
  • Try a different USB cable/port
  • Check your C:\Users\kimpa\AppData\Local\Temp\ folder and delete any .bin files you see there (e.g. firmware.bin, otadata.bin, etc.)
  • If you have one, try flashing another board
 
Thanks for your quick reply!

I tried all of your suggestions except for a different cable and different board because I have only one of each. I'll try getting a new cable today or tomorrow and try again. Then I'll try a different board (it took quite a while for it to get here).

I watched the error messages and they all came up with the problems you mention. Different ports, different speeds and erasing the .bin files between each try. I also tried the web version again and saw that it didn't write any of the .bin files, but that might be the way it's supposed to work.

You said that MicroPython indicates that it didn't flash correctly. The board I have is called "LOLIN D32 Pro V2.0.0 - wifi & bluetooth board based ESP-32 esp32 Rev1 ESP32-WROVER 16MB 8MB 4MB FLASH PSRAM MicroPython" It's the one linked to from the TiltBridge Hardware — TiltBridge documentation page.

Thanks for your help!
 
On the MicroPython thing, my thinking was simply that since none of my projects (and to my knowledge, none of the projects currently in BrewFlasher) use MicroPython, the fact that you're seeing a MicroPython message pop up indicates that the device is still running some other kind of firmware -- likely the "test" firmware that comes preinstalled on the device.

The only two other suggestions I can make are - if you haven't already - to try flashing the device without the cable/screen attached and to check from the computer that you are using to run BrewFlasher that you can access https://github.com/thorrak/tiltbridge/releases/download/v1.2.1/ . That is the URL that BrewFlasher is downloading the firmware from, so if you can't access that for some reason (or can't download the firmware linked there) then that would explain the difficulty that you're facing.
 
Bought the recommended parts from Aliexpress and it flashed and worked right away. However, after a few days the screen developed two one-pixel wide white vertical lines, separated by a one-pixel wide dark line (perhaps working normally?), roughly in line with the second "i" in "TiltBridge".

Anyone else experienced something like this? Any debugging suggestions before I start buying/swapping new parts and seeing when it goes away?
 
It seems I'm playing with all Thorrak's designs lately, but this one's almost anticlimactic. D32 Pro, TFT, and cable got here Tuesday, and a Tilt Pro today. Flashed the D32 using BrewFlasher Web, plugged in the TFT, and what do you know, it Just Worked™. Cool! Having a little trouble getting the case (especially the lid) to print, but it's working nicely. Haven't tried getting it to report to Fermentrack, BrewFather, or anything else yet, but one thing at a time.
 
For some reason, I am unable to reset my password for tilt bridge.. I am unable to access the configuration page for my latest brew and all of my previous files are not accessible.... can I get a proper reset..?
 
Yeah, just choose that option in BrewFlasher
Are you implying that I need to completely reflash my controller? For the past 9 months All I've had to do is go into the web portal and change the beer name and it would automatically update the Google doc...
 
Are you implying that I need to completely reflash my controller? For the past 9 months All I've had to do is go into the web portal and change the beer name and it would automatically update the Google doc...
Right, but you’re having issues accessing the controller’s webpage, are you not? The easiest solution would be to just reflash it, depending on what the underlying issue is. Is the problem entirely with Google Sheets?
 
Right, but you’re having issues accessing the controller’s webpage, are you not? The easiest solution would be to just reflash it, depending on what the underlying issue is. Is the problem entirely with Google Sheets?
When I go to the web app, it does not allow me to log in. I have entered my email in the forgotten password and I never receive an email.. my controller is plugged in and running (never stopped the last run) and when I access the Google sheets of previous brews, there are errors .)
 

Attachments

  • Screenshot_20231031_094840_Chrome.jpg
    Screenshot_20231031_094840_Chrome.jpg
    204.3 KB
  • Screenshot_20231031_095117_Sheets.jpg
    Screenshot_20231031_095117_Sheets.jpg
    310.1 KB
When I go to the web app, it does not allow me to log in. I have entered my email in the forgotten password and I never receive an email.. my controller is plugged in and running (never stopped the last run) and when I access the Google sheets of previous brews, there are errors .)
OH. I apologize - I didn’t realize that is what you were referring to. The TiltBridge web app is actually maintained by @UncleD so he would have to jump in on that.

The errors you see in Google Sheets indicate that you can’t access the individual sheets for each individual brew from the master sheet. You don’t need the links if you can see the sheets themselves in your Google drive. If you can’t see the sheets themselves, then the data unfortunately isn’t saved there.
 
Has anyone had any luck using an external OLED display with a non-pro Lolin D32? I had ordered a couple for a since-abandoned project that I was planning on re-purposing to use with TiltBridge. I know that the Lolin D32 Pro/TFT is the recommended hardware, but I was hoping that there's a way to use a screen with what I've got.
 

Latest posts

Back
Top