2020-01-18 (Sa) ProjectHoneybee

I went to the store and bought a new ESP32-WROOM-32 breakout board from Sparkfun, but when I got home, an order of bare modules was in my mailbox, and I already had a programming jig. This configuration was what I planned from the beginning, but raw modules are surprisingly expensive compared to the breakout board versions. Now, I had hardware I wanted, so I paired them up and had no trouble running a test program.
New hardware

The programming jig had header pins so I could connect the display without fuss. Struggles with poor documentation were nearly over, but I hadn't displayed anything yet, so there was still work. In the end, the biggest problem was that the pin labeled "SDA" should have read "MOSI," and this was extra confusing because SDA indicates the I2C protocol, whereas "MOSI" is indicative of the SPI protocol.
Working display example

Once I ran a test example, I wanted to integrate the screen into a single program where all the components worked together. Sensor data still controlled the LEDs, as before, but it also displayed on the screen as a value from zero to one-hundred. I could have shown raw readings, but those numbers were much longer and continuously changing. I found that blanking the entire screen was time -consuming and lead to flickering. The solution was to write over the old values with the same text but the same color as the background, then write the updated value. By erasing only the changed values, the display looks completely inactive when the numbers aren't changing.
Displaying live values in respective colors

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

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 in 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.