Been playing with one of those 128x64 STN modules and an RP2040 lately, and thougt I'd share what actually made it look good instead of flickery junk. The trick with these screens is they have a slight color shift when pixels flip between on and off, so if you toggle pixels fast enugh your eyes blend it into a warm in-between tone. That's the whole effect, really, there's no magic hardware involved. The Pico drives each pixel with its own pulse pattern, wich gives you way more shades than a plain on-off image would. What burned a whole evening for me was the refresh rate. Run it too slow or too fast and the whole screen looks like static sand. There is a sweet spot somewhere in the low hundreds of frames per second where the noise almost fully vanishes, and it is diferent per module. Just sweep the frame rate slowly and watch for the flicker to calm down, then lock it in. One more tip: keep your render loop and the pixel output on seprate cores. Trying to do both on one core made my timing jitter all over the place. Also worth writing the scene code so it only redraws what changed, since pushing the full buffer every frame gets tight fast. Happy to answer questions in this thread if anyone hits a wall.
A quick guide to getting smooth dithered animation on a monochrome LCD with a Pico
Nov 19, 2026
Last reply: 1 hour ago
3 Replies
I ran into the same thing last month with a 128x64 panel off an old weather station project, except mine preferred a slower refresh than I expected. I started around 400 fps becasue someone on the Pico forum swore by it, and the whole display just looked muddy grey with wierd crawling bands. Dropped it in steps and mine calmed down right around 140, which was not where I guessed it would land at all. So the sweep advice is real, but budget an hour for it because the sweet spot moved a little when I changed the contrast pot. I also took a different route on the rendering side. Instead of splitting render and output across both cores, I set up a PIO state machine to handle the shifting and let core 0 just feed it bytes. That freed me from worrying about core 1 timing and the jitter complaints went away for me. Took a weekend of head scratching to get the DMA setup right though, and honestly the dual core split would have been faster to ship.
The partial redraw tip saved me too. My sunset scene only moves the sun and a strip of horizon per frame, so redrawing just those rows kept the loop well under budget even at the higher contrast settings where the color shift is more visible.
This is honestly the first time I've seen someone use one of these panels for color blending, I always figured they were stuck doing plain two-tone stuff. I've been messing with a similar module as a little status display on my desk, mostly text and a blinking cursor, nothing fancy. Curious how you handle the pulse pattern per pixel, is that a lookup table of duty cycles or do you dither based on brightness? Trying to picture how many shades you acutally get before the flicker creeps back in.
Agree with the PIO idea, that's what got mine stable too. I had one state machine pushing bits while the main core just updated a small dirty region, and the timing stopped wandering. One thing I noticed on my panel: the sweet spot drifted when the room got cold, it looked cleaner in the evening than first thing in the morning. So if it calms down at one rate and acts up later, don't chase it forever, just nudge the refresh a touch.
Join the Discussion
Have something to add? Share your thoughts — no account required.
Didn't find your answer?
Ask the community — no account required