2025-02-13 (Th) EWC_Soother New controller and screen

I found an ESP32 controller with a small screen in my stock. I thought it was an OLED, but it was a color TFT. More specifically, it was a LILYGO T-Display. It lacked mounting holes, the buttons were hard to reach, and it was smaller than the previous model. I found the manufacturer's page quickly, and it had some basic instructions on how to find the example code in a GitHub repo. The level of documentation was a nice change from budget hardware. I updated several libraries and drivers on my system and deleted the old LCD library, which may have been causing issues.

I tried uploading example code, but they failed to compile, or they went through but did not do anything. I got rid of the manufacturer's library and used one from Bodmer, which was updated recently. These would reliably upload, but the screen still failed. I read more and saw that I had to choose my board in a file contained within the library. I have not had to do this before, and it probably explained some of my issues with the previous screen.
Uncommenting lines 58 did the trick

Once I set everything correctly, I uploaded the example code, and my screen worked! The first example chaotically placed alert symbols on the screen, which was the point. I opened a different sketch that used custom fonts and changed it to show "24Eng" since it was pretty large. The prototype will be a text list that I will manipulate with a couple of encoders.
Working screen in a day

The rest of the posts for this project have been arranged by date.
First time here?

Completed projects from year 1
Completed projects from year 2
Completed projects from year 3
Completed projects from year 4
Completed projects from year 5
Completed projects from year 6
Completed projects from year 7
Completed projects from year 8
Completed projects from year 9
Completed projects from year 10
Completed projects from year 11

Disclaimer for http://24hourengineer.blogspot.com and 24HourEngineer.com

This disclaimer must be intact and whole. This disclaimer must be included if a project is distributed.

All information on this blog, or linked by this blog, is not to be taken as advice or solicitation. Anyone attempting to replicate, in whole or in part, is responsible for the outcome and procedure. Any loss of functionality, money, property, or similar, is the responsibility of those involved in the replication.

All digital communication regarding the email address 24hourengineer@gmail.com becomes the intellectual property of Brian McEvoy. Any information contained within these messages may be distributed or retained at the discretion of Brian McEvoy. Any email sent to this address, or any email account owned by  Brian McEvoy, cannot be used to claim property or assets.

Comments to the blog may be utilized or erased at the discretion of the owner. No one posting may claim property or assets based on their post.

This blog, including pictures and text, is copyright to Brian McEvoy.
2025-02-09

Comments