Waveshare ESP32 Driver board no e-paper display

[janssenuwe]

Hello,

I tried to operate a waveshare 1,54" V2 e-paper display with a Waveshare ESP32 driver board,
the display does not even flicker.
It does not display the lines which I preset in the device settings nor react on commands like st77xx,clear,black.

There is a demo from waveshare which is working with that hardware.
In ESP Easy I set up SPI and in the device tab display ST77xx : ST7735 128x128 .

SPI settings:
CLK - GPIO 13
MOSI-GPIO 14
MISO -GPIO 19 (I had to;))

Device settings:
CS - GPIO 15
D/C - GPIO 27
RST - GPIO 26

Am I missing something?

Any Help will be appreciated,
Uwe

[Ath]

For e-Paper displays you need the P096 e-Paper plugin. That can't be controlled using a TFT driver.
Not sure if your display model is supported though, as we only have support for a few very specific display types and resolutions.

NB: e-Paper displays are not suitable for frequent display updates! (I think that was mentioned before)

[Ath]

I've resolved some merge issues with P096, and a new build is running for PR #4223 (to add some 1.54" ePaper displays)in this GH Actions run, that (still) includes the Waveshare 1.54" 200x200 display. Don't own the hardware so haven't been able to test that yet .

[chromo23]

Don't own the hardware so haven't been able to test that yet .

Can somebody give this man some e-paper displays please

[janssenuwe]

Success!
I checkout the branch and build it.
It's working with a 1.54 V2 waveshare ink display .
Thanks a lot
Uwe

[Ath]

Success!
I checkout the branch and build it.
It's working with a 1.54 V2 waveshare ink display .
Thanks a lot
Uwe

Ah, great news

I do own an MH-ET-Live 1.54" 200x200 ePaper (eInk) display, but haven't been able to get it working yet. (this has been a 'sleeping' project for quite some time now...)

This PR has been 'sleeping' because of the very poor documentation for these modules (except for the Waveshare ones), but there are so much of them, nearly the same, displays that all need a slightly different, and quite elaborate/large, initialization that it's nearly impossible to support them, as it will explode the .bin size when including them all.

[janssenuwe]

Hello Ton and the team,

I would like to test it with an 7,5" e ink display (800x 480) from waveshare as well.
Is the implementation possible at all, I heard sth. about memory problems?

If possible and you tell me where and what to change I could implement a trial version and test it.
I haven't looked up the code yet.

Just a proposal.

Have a nice day,
Uwe

[Ath]

I would like to test it with an 7,5" e ink display (800x 480) from waveshare as well.
Is the implementation possible at all, I heard sth. about memory problems?

Should be possible, but haven't tried that yet. And they are also rather expensive, compared to TFT displays, with all the disadvantages of ePaper (slow updates, low frequency of content updates as they cause wear on the display, very limited color options).
You will need to provide the exact model you have, as there are already quite a lot of models listed, that are not software compatible, and some of the hardware is no longer available...

If possible and you tell me where and what to change I could implement a trial version and test it.
I haven't looked up the code yet.

If you have a look in the code for P096, you can see how I've implemented other added displays, maybe you can extend on that? Be sure to use #if conditional inclusion of the code, as it probably won't fit in the ESP8266 Display build (that's at about 99.9% code limit).
I assume you've forked the letscontrolit/ESPEasy repository to your own repo, and cloned that to your computer to work in. If not, the development documentation describes how to set that up, and create a pull request once you have something working

[janssenuwe]

Thank you Ton for your quick reply.

I already own a 7,5" V2 waveshare e-ink display.
You are right concerning disadvantages of those types.
Yes, I forked from letscontrolit/ESPEasy repository to my own repo already.
That's my working environment.
I'll check the code and figure out.

Best Regards, Uwe