Hacker Newsnew | past | comments | ask | show | jobs | submit | alex-a-soto's commentslogin

Our driver board works with color e-ink screens.


Yes, this is one of the areas I’m most excited about; it makes e-ink more practical for everyday use and opens the space for experimentation. In the long run, as the community grows and more people get involved, we’ll see even more possibilities.


Yes, that’s the mental model I’ve been working from. Variable refresh tied to user input makes a lot of sense: short bursts of speed for navigation or editing, then settling into a low-power static state.

Part of the challenge is deciding what belongs in hardware and what should sit higher up in the OS or software stack.

Hopefully, as more people get the kits and the community grows, we’ll be able to think through these questions together and explore where the right balance between hardware and software should be.


I agree with your points. I would add:

- Making the project open allows people to reuse displays they already own.

- Others can contribute and build on what’s been created.

- Open source firmware, documentation, and the driver board make development more accessible and help remove barriers that previously slowed community projects.

- It’s designed to work with a variety of electrophoretic panels, not only those from E Ink.

In the long run, this openness will strengthen the ecosystem, making it easier for new ideas to take shape and spread.


Another gameplay video I'd recommend seeing is Blanc: https://www.youtube.com/live/9PAKPfHBa5Q?feature=shared&t=11...


That game is beautiful, more so on the eink display...


Our driver board, under continuous use, draws about 1 to 1.5W. A recent article below goes into some detail about our design choices.

https://www.crowdsupply.com/modos-tech/modos-paper-monitor/u...


I’d recommend watching the video below, where we talk about how fast refresh affects a panel’s lifespan.

https://www.youtube.com/live/okjJURIejIY?feature=shared&t=24...


> How many shades of grey does it support?

16 levels of grayscale support.

> How bad is the ghosting?

Ghosting depends on the mode you're using and the content.

> How white is the background?

Varies, depends on the panel you're using.

> Is it clear enough to be used white-on-black?

Yes

> How often does it need a full screen refresh?

That's up to you; you can manually clear with a button press, use auto-clear mode, or programmatically control it.

https://www.youtube.com/watch?v=AoDYEZE7gDA&ab_channel=Modos


Answers would be more helpful if you answered based on the panel you were using rather than saying it depends on the panel


  > Ghosting depends on the mode you're using and the content.
I'm talking about 75 hz mode.

  >> Is it clear enough to be used white-on-black?
  > Yes
Really? My Nook and Boox devices aren't. The ghosting in even the highest quality refresh mode is just to much in "dark mode". I'd love to see this.


Back in the days when OLED screens didn’t exist, the rule was that white on black text needs to be bolder for legibility. Since super high contrast is now par for the course, designers with high end devices forgot about this.

I agree that the dark mode on the boox is terrible (I find for example obsidian absolutely unusable). But this could be easily fixed with bolder fonts.


I’d recommend watching the video below, where we talk about how fast refresh affects a panel’s lifespan.

https://www.youtube.com/live/okjJURIejIY?feature=shared&t=24...


For dynamic content, a higher refresh rate absolutely will lower an eink panel's lifespan. As the refresh rate increases, more of the underlying content's changes will be captured and more pixels will change state.


Our driver board, under continuous use, draws about 1 to 1.5W. A recent article below goes into some detail about our design choices.

https://www.crowdsupply.com/modos-tech/modos-paper-monitor/u...


Thanks. That article seems to have the quote I was looking for.

> E-ink screens are quite power hungry when it comes to peak current. Modern high-resolution panels can consume >20 W peak.

This is where I was wondering and yeah, 20+W is pretty hefty to support a relatively small 8" EInk screen or something.

All those updates cost all that power as long as updates are occurring. Maybe you can optimize many of them away (if some parts of the screen don't move, especially if software was rewritten to optimize for the display).

More importantly, it sounds like you've created a full custom FPGA controller over the voltages that go into an EInk display? That's impressive in its own right even if I don't think 75Hz is a good idea lol.

--------

FPGA or Full Blown Microprocessor are the only choices here. A high power SIMD/NEON arm64 probably could do the job, but I think the Spartan6 is a good choice as well and has more obvious and straightforward parallelism (and probably all the pins required to control the screen. Even a big microprocessor won't have as many low latency pins as an FPGA).


> Maybe you can optimize many of them away (if some parts of the screen don't move, especially if software was rewritten to optimize for the display).

Yes, that’s definitely something we want to work toward. As the community grows, we hope to tackle these kinds of optimizations together.

> A high power SIMD/NEON arm64 probably could do the job, but I think the Spartan6 is a good choice as well and has more obvious and straightforward parallelism

Yes, precisely for the reasons you stated. We also talk more about it below:

- https://www.youtube.com/live/okjJURIejIY

- https://github.com/Modos-Labs/Glider?tab=readme-ov-file#desi...


Congrats on the article either way!! I'm one of the daylight founders so I love to see progress made on electrophoresis

We personally couldn't make it work with low power but this seems promising!


Would be cool to get an actual desktop screen with something like your screen tech.


Thank you!


The article says:

> “Traditionally, the [e-paper display] controller used a single-state machine to control the entire panel, with only two states: static and updating,” says Modos cofounder Wenting Zhang. “Caster treats each pixel individually rather than as a whole panel, which allows localized control on the pixels.”

So in practice would it ever actually hit 20W unless you're doing something that requires constantly updating the whole screen, like playing a video game or watching a video? Surely updating only a few pixels at a time can't be that power hungry, right?


You guys should do a collab with the framework people. I bet they'd be happy to offer an e-ink screen on their laptops just as an option. I've been waiting on an e-ink option for ages.


We’d like to offer a kit for the MNT Reform, and possibly the Framework, in the future, though it’s not part of our current roadmap.


This...would be insanely amazing. A _real_ laptop with a proper 13" eink display at 75Hz!


I’d gladly pay for a crappy 30Hz version literally right now if they sold that. A framework with e-ink sounds like a dream


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: