> It's way simpler than that, you just write the displayed image more times based on temperature. Oh! Nice. > If you don't do it your display will just have l

> It's way simpler than that, you just write the displayed image more times based on temperature. Oh! Nice. > If you don't do it your display will just have less contrast in the code. That's a really great failure mode for debugging/development :) you can just use a single repaint count until you have temperature sensing wired up. > The chip-on-glass has tons of registers to set drive voltages and the like, but the datasheet just gives you values to write to all of them. Oh okay - so there _is_ a controller. (I didn't know; totally ignorant about the subject.) > What do you mean by e-ink driver? Ah; I've just done some poking around, and I just realized I misunderstood things a bit when I last did some research (way too quickly, apparently) - I saw http://www.pervasivedisplays.com/images/Kits/Extension%20board/Eink%20epaper%20Extension%20kit%20by%20Pervasive.jpg http://www.pervasivedisplays.com/images/Kits/Extension%20boa... and thought I'd need to cram everything on that board onto the final design. I didn't realize the displays were more or less self-contained (with a builtin/COG controller) and could be driven directly like LCDs or VFDs etc and that that board was the "kitchen sink" test/dev breakout kit.