You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I initially set up this project on my 7.5" BW Waveshare EPD with the Waveshare ESP32 driver board (v3), the DISP_BW_V2 macro called the GxEPD2_750_T7 constructor. I got a really washed out image with low contrast, which is an issue I have seen on some other forums while looking around for a fix.
I noticed the startup sequence did not match the Waveshare demo that works just fine. Eventually I came across this in the GxEPD examples and noticed the FPC-C001 identifier. Lo and behold, my ribbon matches. So I swapped out the constructors and this project works like a charm.
I got my display from Amazon. I am not sure if they ship different controller versions or what. I am more familiar with OLED display drivers.
I would be happy to submit a PR with and additional macro for this display type, but wanted to ask first. Maybe one of them are being phased out and I just got unlucky?
The text was updated successfully, but these errors were encountered:
When I initially set up this project on my 7.5" BW Waveshare EPD with the Waveshare ESP32 driver board (v3), the
DISP_BW_V2
macro called theGxEPD2_750_T7
constructor. I got a really washed out image with low contrast, which is an issue I have seen on some other forums while looking around for a fix.I noticed the startup sequence did not match the Waveshare demo that works just fine. Eventually I came across this in the GxEPD examples and noticed the FPC-C001 identifier. Lo and behold, my ribbon matches. So I swapped out the constructors and this project works like a charm.
I got my display from Amazon. I am not sure if they ship different controller versions or what. I am more familiar with OLED display drivers.
I would be happy to submit a PR with and additional macro for this display type, but wanted to ask first. Maybe one of them are being phased out and I just got unlucky?
The text was updated successfully, but these errors were encountered: