e-Paper icon indicating copy to clipboard operation
e-Paper copied to clipboard

7.3inch e-Paper HAT (E) - stuck in the well known "e-Paper busy H"

Open dreimer1986 opened this issue 8 months ago • 3 comments

I am no big story teller, but this one is like a fairy tale by now... My plan was to use the e-Paper for a picture frame I would be able to control via Home Assistant. So I bought the e-Paper and a RasPi Zero W. I happily put everything together and ... it worked. I followed the manual in the Wiki and as my aim was Python I chose this one. Then I decided to add the resize to the libraray when the image size does not work and even that still worked and I was able to pass over the "N-Color1.bmp" from the pic folder to it, too as it was detected to be of incorrect size, but then was resized to self.witdth and self.height.

https://photos.app.goo.gl/E8BfQxFaZmDxYwUR6

All looked great until from one sec to another the first "DEBUG:waveshare_epd.epd7in3e:e-Paper busy H" showed up mid drawing the manga stype eye image it originally should draw in the example. Since then I read through all kinds of reports here. I replced the Pi Zero W with my old Pi 3 B and it worked for a while again. Well.... "worked"

https://photos.app.goo.gl/PEVhqtBRrjj4cTZ66 https://photos.app.goo.gl/iw5n7MUfpHqjZDiU7

This distortion is not really what I call working...

And this is all I was able to get out of it. And now after a while of trying to get it back to shape I am stuck on "DEBUG:waveshare_epd.epd7in3e:e-Paper busy H" again... This time forever as it seems.

Yes, I checked the wires. Yes, I went from directly plugging he PCB onto the 40 Pins connector to the 8 wire solution. I removed the long cable and directly plugged the e-Ink into the pcb that is connected to the 40 pin connector of the RPI or the 8 wires that are on the same RPI. All the same...

Well, if you have another idea... tell me. Otherwise I send it back and give up on this brand.

dreimer1986 avatar May 31 '25 14:05 dreimer1986

I have some news. I tested a bit more and got past the busy message again... This time by changing PWR_PIN = 18 to PWR_PIN = 1 in epdconfig.py. But still... Well, just look at this result...

https://photos.app.goo.gl/wtGgsj73kbDm8UAQ7

Weak and washed out... and adding the long ribbon cable makes things even worse... I need 3.3V here, right?

dreimer1986 avatar Jun 01 '25 07:06 dreimer1986

I know it's been a while but I was able to get a better image by using epd7in3f instead of 3g. with 3g the image was washed out and the background always ended up black

BumpyClock avatar Oct 14 '25 23:10 BumpyClock

It was even worse on my case. I forgot which one by now, but one port should have been set to pull-up or something like that was explained to me. Using the script caused a hardware defect. I sent it back and did not try again until now

dreimer1986 avatar Oct 15 '25 06:10 dreimer1986