← How-Tos
electronics 5 days ago ◑ 11 views ◯ 5 min read

Driving Color E-Paper Displays: Spectra 6 and ACeP Panels with ESP32 and Raspberry Pi

e-papere-inkSpectra 6ACePcolor displayESP32Raspberry PiGxEPD2low power display

The black-and-white (and black/white/red three-color) e-paper panels most makers reach for are well understood: SPI wiring, GxEPD2, partial refresh for fast updates. True color e-paper is a different animal entirely. Panels built on E Ink's Spectra 6 (six-color pigment, formerly "E6") or the older ACeP (Advanced Color ePaper) process can render real color images — not dithered red/black approximations — and hold that image with zero power once drawn. That capability comes with real tradeoffs in refresh time, driver complexity, and available panel sizes that catch makers off guard the first time they try to port a monochrome e-paper project to a color panel. This guide covers how these color panels actually work, how to wire and drive one from an ESP32 or Raspberry Pi, and where the real limitations are before you commit a design to one.

How Spectra 6 and ACeP Differ from Black/White/Red E-Paper

A standard monochrome e-paper panel has one layer of black and white charged pigment particles that migrate toward or away from the viewing surface under an applied field — one bit per pixel, sometimes with gray levels achieved through time-domain dithering. A black/white/red panel adds a second pigment layer, letting you address three fixed colors directly. Spectra 6 and ACeP go further: each pixel contains multiple colored pigment particle types (cyan, magenta, yellow, black, white, plus in Spectra 6's case a true separate red and sometimes orange/blue depending on panel generation) that are driven through a sequence of voltage waveforms to settle into a specific color at each pixel, closer to how a color photographic print layers dyes than how a binary e-paper panel works. The practical consequence: a full-color refresh is not instant. Where a monochrome partial refresh can update in under a second, a full-color Spectra 6/ACeP refresh typically takes 15-35 seconds depending on panel size and temperature, because the controller is cycling through multiple waveform phases to settle every pigment type into position. There is no meaningful "partial refresh" mode on most color panels — budget for a full redraw on every content change.

Wiring: SPI, But More of It

Electrically these panels use the same SPI interface as monochrome e-paper — MOSI, SCK, CS, DC, RESET, and BUSY — and the same families of driver chips makers already associate with Waveshare and Good Display boards. The practical difference is panel voltage and current draw during a refresh: color panels pull noticeably more current for longer during the multi-phase update sequence, which matters if you're running one from a coin cell or a thin LiPo on a battery-powered sign. Waveshare's and Good Display's color e-paper HATs for Raspberry Pi handle level translation and the boost converter for you; on bare panels wired directly to an ESP32, make sure your 3.3V rail can source the panel's peak refresh current (check the datasheet — it is usually in the 100-200 mA range during the drive pulses, not the microamp-scale "e-paper uses no power" number everyone remembers from the holding state).

Panel lineColorsTypical refresh timeCommon sizes Monochrome / 3-color (BWR)2-3 fixed<1s partial / 1-2s full1.5" - 13.3" ACeP (older color)~7 fixed palette colors15-30s4.3" - 7.3" Spectra 6 (E6)6 primaries, broader gamut via dithering15-35s4" - 13.3", growing

Driving a Panel from ESP32

GxEPD2, the library most ESP32/Arduino e-paper projects already use, has growing but incomplete support for color panels — check the library's supported-panel list against your exact part number before buying, since color e-paper driver ICs vary more between panel generations than the monochrome ones do. Where GxEPD2 doesn't yet support a specific color panel, Good Display and Waveshare both publish their own C demo drivers for their boards, which is usually the more reliable starting point: strip the demo down to the display-init and image-send functions and wrap your own content around it rather than trying to force a mismatched library to drive hardware it wasn't written for. Image data is sent as packed multi-bit-per-pixel buffers (the exact packing depends on panel generation — some use indexed-color nibbles, others separate color-plane buffers), which means your source images need palette-reduction and dithering to the panel's specific color set before conversion to a C byte array; Pillow's Image.quantize() with a custom palette matched to the panel's documented color values is the standard preprocessing step, and it matters more for color panels than monochrome ones because getting the dither wrong produces visibly wrong hues, not just a slightly rougher gray.

Driving a Panel from Raspberry Pi

On a Pi, Waveshare's Python libraries for their color HATs are the path of least resistance — install the vendor library, run their example with a test image, and you have a known-good reference point before writing your own content pipeline. The Pi's advantage over an ESP32 here is horsepower for the image-processing side: converting a photo to the panel's native palette with proper dithering (Waveshare's libraries use Floyd-Steinberg by default, which is adequate but not great for photographic images; a custom ordered-dither pass tuned to the panel's primaries usually looks noticeably better) is trivial on a Pi and awkward on a memory-constrained microcontroller trying to do the same math on a large framebuffer.

Where Color E-Paper Actually Makes Sense

Given the slow refresh and higher per-panel cost, color e-paper is the wrong tool for anything that updates often or needs motion — a status dashboard that refreshes every few seconds is miserable on a 20-second-redraw panel. It's the right tool for content that changes rarely and needs to look good while holding that state indefinitely on no power: a framed piece of generated art that changes daily, a shelf-edge price label, a battery-powered farmers-market sign, a static dashboard of yesterday's print-farm stats checked once in the morning, or a photo frame that cycles one image per hour. If you've been eyeing color e-paper as a drop-in upgrade for a fast-updating ESP32 dashboard project, the refresh time alone should redirect you back to a backlit TFT instead — color e-paper's advantage is holding a picture forever for free, not showing you fresh numbers quickly.