Replies: 3 comments 3 replies
-
Update: // Make sure Vext is properly configured in setup() display.init(); I found that init and setContrast were already being called in heltec_setup(). I only added this code to my setup() after heltec_setup(): It looks like heltec_ve() was handling this functionality already so now I am just calling heltec_ve(true) right after heltec_setup() in setup() function. |
Beta Was this translation helpful? Give feedback.
-
Brilliant (literally) - thank you! :-) |
Beta Was this translation helpful? Give feedback.
-
I'll make Vext on the default soon, so one has to turn it off explicitly. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I wrote a program with V3.1 which utilized the OLED. It worked great. I just bought (2) new V3 boards. (1) came in as V3.2 and (1) was V3.1. I uploaded the same program onto the V3.2 board but now the OLED is so dim that I cannot read what it says even with the lights out. I can tell that it is operating though. Before I programmed it the demo was running and it looked good so I don't think the hardware is faulty. I uploaded the same program to the new V3.1 and it worked just like my first V3.1 board.
I haven't seen anywhere where I can set the brightness or contrast of the OLED. Am I just overlooking it?
Do you have any other thoughts on what might cause this?
Beta Was this translation helpful? Give feedback.
All reactions