Re:Why is printing “B” dramatically slower than printing “#”?
by VLM on Tuesday February 25, 2014 @07:50AM
(#7297258)
Or that he's written low level display code that behaves exactly that way. I have. It was for a LCD display module on a 68HC11 microcontroller probably in the mid 90s. It was something like a 4x16 and you inevitably have to make some value judgements in your "display a string" subroutine about what to do when stuff doesn't fit on a line. It only had a quarter K of ram and not much more onboard eeprom so I never tried to display thousands of letters. My eventual strategy was overwriting (keep it small and simple).
What do you do with a quarter K? It was basically a very slow beamwidth analyzer for LEDs using a photodiode and a R/C servo. So the 3 dB down aka half power beamwidth of this integrated LED and diffusion lens system measures as X degrees. Kind of important if you're making LED based signs. I believe I was only using about 4 bytes of memory. No need for interrupts as it had a rather advanced hardware timer system that made excellent PWM for driving servos. The world is full of interesting problems that require lots of computation but very little stored state.
What do you do with a quarter K? It was basically a very slow beamwidth analyzer for LEDs using a photodiode and a R/C servo. So the 3 dB down aka half power beamwidth of this integrated LED and diffusion lens system measures as X degrees. Kind of important if you're making LED based signs. I believe I was only using about 4 bytes of memory. No need for interrupts as it had a rather advanced hardware timer system that made excellent PWM for driving servos. The world is full of interesting problems that require lots of computation but very little stored state.