Heltec paper

[thebentern]

Created from @ixt's fork

[CLAassistant]

All committers have signed the CLA.

[ixt]

here is an image of my flex cable, HINK-E0213A162-FPC-AO, DEN 2242

[markbirss]

@ixt is there no print on the other side (outside) of the e-ink flex cable ?

this was just before i tried to move up those dots long ago (rak14000 e-ink)

[thebentern]

@ixt is there no print on the other side (outside) of the e-ink flex cable ?

Mine has FPC-7528B on the outside

[markbirss]

@thebentern and the changes work ok on your version ?

[ixt]

@markbirss nope, there isnt, that photo is of the screen of the v1 board (red tab) -> https://docs.heltec.org/en/node/esp32/hardware_update_log.html

[markbirss]

@ixt

Ok,v1.1 it leads to sample code of a b/w/r e-ink.....

QYEG0213RWS800_BWR
Sample code V1.1 - https://github.com/Heltec-Aaron-Lee/WiFi_Kit_series/tree/master/esp32/libraries/Heltec-Example/examples/E-INK/QYEG0213RWS800_BWR

[ixt]

@markbirss that isnt the sample code for v1.1, its linked wrong. this is for v1.1 https://github.com/Heltec-Aaron-Lee/WiFi_Kit_series/blob/master/esp32/libraries/Heltec-Example/examples/E-INK/HT_lCMEN2R13EFC1/HT_lCMEN2R13EFC1.ino

For the v1 I believe the QYE... code is correct, BUT its also not BWR... (To my understanding). The sample code, documentation in general is all over the place for wireless paper :/

[ixt]

@markbirss if you see on this page there is a tip that is the most correct about which example is which https://docs.heltec.org/en/node/esp32/wireless_paper/via_program_refresh.html#summary

There are currently two versions of the diplay, if the protector sticker has a red mark, please select the code ‘QYEG0213RWS800_BWR’; For others, select ‘HT ICMEN2R13EFC1’. If you are not sure which version you have, please contact us

[thebentern]

@thebentern and the changes work ok on your version ?

Just tested. Sadly it does not. I suspect mine is the original version and they made changes similar to the Wireless Tracker v1.1 vs 1.0

[ixt]

@thebentern I'm guessing that the v1 may work with one of the other display's drivers as it looks much more like what I've been seeing in other displays here: https://github.com/Heltec-Aaron-Lee/WiFi_Kit_series/blob/master/esp32/libraries/DISPLAY/src/HT_QYEG0213RWS800_BWR.h

Pulling Vext low might still be needed tho since if the driver was all that was needed it would have been fixed by now

[StevenCellist]

https://forum.arduino.cc/t/new-e-ink-display-not-in-gxepd2/1196494 here is a discussion about this new panel - Heltec has not responded in any way other than pointing to their stupid incomplete HT_ICMEN driver.

[markbirss]

https://forum.arduino.cc/t/new-e-ink-display-not-in-gxepd2/1196494 here is a discussion about this new panel - Heltec has not responded in any way other than pointing to their stupid incomplete HT_ICMEN driver.

Thank you for pointing us to the already existing discussion in understanding some of the issues

[geoffwatts]

I have tried this (on my v1.1 stickered device) and it's working great.

[thebentern]

I'm going to go ahead and merge this and then try to get my v1.0 working with the a different driver I guess

[ixt]

@thebentern I'm guessing if you clone the driver I wrote, swap out the 0x13 commands for 0x24s, update full and part's 0x12s for

		sendCommand(0x22); 
		sendData(0xF7);
		sendCommand(0x20); 

it might just work??

https://github.com/Heltec-Aaron-Lee/WiFi_Kit_series/blob/master/esp32/libraries/DISPLAY/src/HT_QYEG0213RWS800_BWR.h is heltechs driver for the v1 display, you can compare that with the v1.1 https://github.com/Heltec-Aaron-Lee/WiFi_Kit_series/blob/master/esp32/libraries/DISPLAY/src/HT_lCMEN2R13EFC1.h and the one I smashed together. It shouldn't be too difficult.

Other than the driver the .ino examples look pretty much the same. The GPIO's look different but I'd be surprised if they bothered, and just copied whatever vendor's example they got....

I found eerily similar examples on gooddisplay's website when i was looking it up. for prosperity here is a link also to the correct .ino example for the v1 display, https://github.com/Heltec-Aaron-Lee/WiFi_Kit_series/blob/master/esp32/libraries/Heltec-Example/examples/E-INK/QYEG0213RWS800_BWR/QYEG0213RWS800_BWR.ino

good luck! I messaged a few sellers to see if i can get a hold of a v1 device but no replies yet. Glad to see this merged though!

0x12 is soft reset in v1s command set, 0x12 is refresh in v1.1, the difference isnt clear to me but it might be worth swapping out for 0x20 in the v1 driver if it gives issues.

[markbirss]

@ixt @StevenCellist

Have you seen this already ?
https://www.good-display.com/public/html/pdfjs/viewer/viewernew.html?file=https://v4.cecdn.yun300.cn/100001_1909185148/UC8151C%20to%20UC8151D%20instructions--20210305.pdf

[ixt]

@markbirss I think I saw this in passing, but it didnt really help much for the v1.1s EPD, the controller isn't entirely UC8151D like, the resolution setting stuff (0x61) always crashed the display for me. And the example code included commands post-0x90 that weren't documented in any screen I looked at. I think either there are parts that are left in from an OLED driver or we are looking at a hypothetical UC815E/UC815 Variant in the v1.1 case. But almost certainly it's built on the UC8151D set.

Though, having said all that, it is hopeful that these displays can do partial update with how its explicitly labeled there for both versions