4 ms·

You can, I've used Pervasive Displays (I bought them from Digikey, they also have breakout boards): http://www.pervasivedisplays.com/ http://www.pervasivedispla

You can, I've used Pervasive Displays (I bought them from Digikey, they also have breakout boards): http://www.pervasivedisplays.com/ http://www.pervasivedisplays.com/ But yeah they are kind of complicated to drive. I've only used the small ones, but you do the refresh pattern manually - you also need to compensate for the temperature, and the pixel layout is a bit funky. Luckily there's already software for this at repaper.org, so you don't have to worry about it. The complicated logic being in software opens the doors for more complex refresh logic as well. Just keep in mind if you do this you can burn in the display, so buy a couple if you plan to experiment :)

i336_ 10y ago
Huh. I thought controllers were insanely complicated or used proprietary technology. This is interesting to hear! What exactly is temperature compensation? I'm aware that it's a thing, but I haven't yet figured out what it is. Do you have to alter the drive voltage or current or something? Also, I'm not currently aware of any open e-ink driver designs. A few people might be interested in the one you built, regardless of how simple it is. Of course standard disclaimers would apply.
- TD-Linux 10y ago
  It's way simpler than that, you just write the displayed image more times based on temperature. If you don't do it your display will just have less contrast in the code. 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. What do you mean by e-ink driver? If you mean the software, check out the Arduino and Raspberry Pi librares on the repaper site. If you mean the hardware, just follow the schematics in the datasheet and repaper.org.
  - i336_ 10y ago
    > 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.
    - TD-Linux 10y ago
      You do need part of that - a lot of it is capacitors wired directly to the ribbon cable, for the COG's charge pump. There's also a temperature sensing chip and a couple of external mosfets, one of which is to fix a bug on older COGs. On my own layout I was able to shrink it quite a bit by using 0603 parts. Still expect to burn 300mm^2 on the passives. https://0x0.st/tqo.png https://0x0.st/tqo.png
      - i336_ 10y ago
        Ah, I see. Thanks.

i336_ 10y ago

Huh. I thought controllers were insanely complicated or used proprietary technology. This is interesting to hear! What exactly is temperature compensation? I'm aware that it's a thing, but I haven't yet figured out what it is. Do you have to alter the drive voltage or current or something? Also, I'm not currently aware of any open e-ink driver designs. A few people might be interested in the one you built, regardless of how simple it is. Of course standard disclaimers would apply.

TD-Linux 10y ago
It's way simpler than that, you just write the displayed image more times based on temperature. If you don't do it your display will just have less contrast in the code. 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. What do you mean by e-ink driver? If you mean the software, check out the Arduino and Raspberry Pi librares on the repaper site. If you mean the hardware, just follow the schematics in the datasheet and repaper.org.
- i336_ 10y ago
  > 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.
  - TD-Linux 10y ago
    You do need part of that - a lot of it is capacitors wired directly to the ribbon cable, for the COG's charge pump. There's also a temperature sensing chip and a couple of external mosfets, one of which is to fix a bug on older COGs. On my own layout I was able to shrink it quite a bit by using 0603 parts. Still expect to burn 300mm^2 on the passives. https://0x0.st/tqo.png https://0x0.st/tqo.png
    - i336_ 10y ago
      Ah, I see. Thanks.