KrisKasprzak
Senior Member

No, clearDisplay literally clears everything in the video buffer. Noting that this particular display driver uses part of your Teensy memory as the video buffer. I see you have this call in your update_xpndr function....

You have a .clearDisplay() in both sections. Wont the "Standby" text erase the other?

here's how I do it. const char *kris = "cool"; displayRoundedTextBox( 10, 100, 100, 50, C_RED, C_BLUE, 4, C_WHITE, kris, 11, 12); or displayRoundedTextBox( 10, 100, 100, 50, C_RED, C_BLUE, 4, C_WHITE, "Cool",...

not sure if this will answer your question, but you can "turn on/off" the display with by setting the LED pin to high / low directly. You can also send a PWM signal to the LED pin to control brightness.

Specs say 14mm accuracy. Do you get anywhere near that?

I’m not sure how I could incorporate touch and a mechanical input device. Still thinking… What is this library blocking?

For "production" usage, I personally never power anything from the onboard regulator regardless of the power consumption by devices. However if I'm prototyping stuff on a solderless breadboard, I'll use the onboard...

50 was may hard coded byte value so the duty cycle = 50/255. With your mapping function, the PWM will will a square wave either 0 or3v3, but an average read will provide 0 TO 3v3. You will need to mess with values in...

I just tried the following code on a 4.1 and got expected PWM results. void setup() { pinMode(9, OUTPUT); } void loop() { analogWrite(9, 50); }

I have some projects that have around 50 settings. I use a display + touch and a fancy menu system to allow the user to make changes. All settings are stored in the EEPROM The process works well and no issues.

This code is from my printscreen library for and ILI9341--and relies on a writeRect. If your lib has that call, this code will probably work. I've not tested it to work on your display but I use it frequently to display...