I have been successfully using this code for some time on a Pi running 24/7/365 and it works well. That said, the display is now totally fried with probably 90% of the text being unreadable due to burn-in which is evidently very common for these inexpensive OLED displays. I was thinking it would be good if this code could add some configuration options to combat this:
-
Add support for a GPIO pin to wake the display and then show one cycle of stats and then turn off
-
Show one series of stats per minute and turn off
-
Maybe offer an INVERT display mode where most of the pixels are on but the usually used text pixels are turned off to give them a rest
-
Maybe consider an alternate display where some of the text lines are moved around so different pixels are used. Alternatively, maybe shift the text display over by one pixel on every other display series to give the original pixels a break.
--David
I have been successfully using this code for some time on a Pi running 24/7/365 and it works well. That said, the display is now totally fried with probably 90% of the text being unreadable due to burn-in which is evidently very common for these inexpensive OLED displays. I was thinking it would be good if this code could add some configuration options to combat this:
Add support for a GPIO pin to wake the display and then show one cycle of stats and then turn off
Show one series of stats per minute and turn off
Maybe offer an INVERT display mode where most of the pixels are on but the usually used text pixels are turned off to give them a rest
Maybe consider an alternate display where some of the text lines are moved around so different pixels are used. Alternatively, maybe shift the text display over by one pixel on every other display series to give the original pixels a break.
--David