Differences

This shows you the differences between two versions of the page.

--- arduino:displays_for_classic_arduinos:nokia_5110_displays_and_classic_arduinos_speed_test [2018/01/28 05:16] – mithat
+++ arduino:displays_for_classic_arduinos:nokia_5110_displays_and_classic_arduinos_speed_test [2018/01/28 05:35] – [Summary evaluation] mithat
@@ Line 3: / Line 3: @@
 ===== Summary evaluation =====
-The good news is that it is pretty fast, which no doubt is a result of the limited 84×48 resolution and 1 bit color depth. The bad news is that it's still a bit of a memory glutton, consuming 42% of program storage and 24% of dynamic memory. Most of that is probably the data for the lovely fonts.
+One might expect this 84×48 display with 1 bit color depth to be updateable pretty quickly even with a torpid Uno/Nano/Pro Mini, and indeed it is. The frame update time of 100 ms (the inverse of the fps noted in the [[display_nokia_5110_u8g2_counter.ino | source code]]) is respectable, and
+character change artifacts are not objectionable. The frame update time is expected to halve with a 16 MHz board, but there are no 16 MHz 3.3V boards, so that means you'll have to complicate things a bit with level shifters.
-The frame update time of 100 ms (the inverse of the fps noted in the [[display_nokia_5110_u8g2_counter.ino | source code]]) is respectable, and
+The bad news is that it's still a bit of a memory glutton, consuming 42% of program storage and 24% of dynamic memory. Most of that is probably the data for the lovely fonts. Lunches are never free.
-character change artifacts are not objectionable. The frame update time is expected to halve with a 16 MHz board, but there are no 16 MHz 3.3V boards, so that means you'll have to complicate things a bit with level shifters.
 ===== Tests =====