-
Notifications
You must be signed in to change notification settings - Fork 190
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add screen diagnostics example app #218
Conversation
Include and link against the epd_driver component.
Taken from https://github.com/espressif/esp-idf/blob/v4.4.3/examples/system/console/basic Remove command registration and some undefined macros.
Import fonts Alexandria and Amiri.
Whenever the user draws/renders something to the screen, the screen will immediately be updated. Remove update_screen command, because it is unnecessary.
Also get rid of initial display clearing.
Thank you, that looks useful! I'll test it a bit and hopefully merge it soon :) |
Wow, that's awesome, I really like the interactive console! |
Hm, that's interesting. How do you know, it tries to read the temperature again? No, I have no clue why this happens.
That's probably a good idea! Gonna add this check. |
Dear @jdoubleu what is the status of this I would also like to test it. |
The epd must be turned on before.
Sorry for the long delay.
I am unable to reproduce this issue. With my v5 board, reading the temperature, even if the board isn't manually Nonetheless I've added a fix which always turns on and off the epd before reading the temp. |
This weekend I will start testing this that I think is a great contribution. @jdoubleu could you please merge back master that is now updated into your pull request? |
Nvm, I can actually just merge this and then apply the fix :D Thanks again for the nice contribution, very useful! |
This example app implements a simple interactive shell that lets you tinker with the display. You can draw simple shapes (i.e. everything the epd driver provides), read system information, etc. I've ported some of my screen test algorithms (i.e.
render_stairs
andrender_grid
) as well.This can be helpful when debugging incompatible or broken displays or just experimenting with the draw functions.
Also note: the
power_on
command basically obsoletes the calibration_helper example.