waveshare 7.5inches v2 won't draw

[deguilardi]

I'm just trying to run any test to see if the screen draws anything. By simply running pi@raspberrypi:~/Workspace/e-Paper/RaspberryPi&JetsonNano/python/examples $ python3 epd_7in5_test.py I get all logs as it's all good, but there is absolutely nothing drawn on the screen.

The screen is all white.

logs: INFO:root:epd7in5 Demo INFO:root:init and Clear DEBUG:root:e-Paper busy DEBUG:root:e-Paper busy release DEBUG:root:e-Paper busy DEBUG:root:e-Paper busy release INFO:root:1.Drawing on the Horizontal image... DEBUG:root:1234 DEBUG:root:imwidth = 640 imheight = 384 DEBUG:root:e-Paper busy DEBUG:root:e-Paper busy release INFO:root:2.Drawing on the Vertical image... DEBUG:root:1234 DEBUG:root:imwidth = 384 imheight = 640 DEBUG:root:e-Paper busy DEBUG:root:e-Paper busy release INFO:root:3.read bmp file DEBUG:root:1234 DEBUG:root:imwidth = 640 imheight = 384 DEBUG:root:e-Paper busy DEBUG:root:e-Paper busy release INFO:root:4.read bmp file on window DEBUG:root:1234 DEBUG:root:imwidth = 384 imheight = 640 DEBUG:root:e-Paper busy DEBUG:root:e-Paper busy release INFO:root:Clear... DEBUG:root:e-Paper busy DEBUG:root:e-Paper busy release DEBUG:root:e-Paper busy DEBUG:root:e-Paper busy release INFO:root:Goto Sleep... DEBUG:root:e-Paper busy DEBUG:root:e-Paper busy release DEBUG:root:spi end DEBUG:root:close 5V, Module enters 0 power consumption ...

[dev-ng]

Hi, I own 7.5" v1. It has native resolution 640x384. You've got v2. As far as I know it comes with 800x480. There is also HD version with 880x528. Looking at the log you provided you are using script compatible with v1. It's actually clear from your post: epd_7in5_test.py

Try epd_7in5_V2_test.py

It has:

Display resolution

EPD_WIDTH = 800 EPD_HEIGHT = 480

[sh969]

Had the same issue. Worked by selecting 7in5_V2 for my 800x480 display (one colour).

[sh969]

You have the colour version but neither V2 nor HD so it should be epd7in5bc. The files in the lib folder define the resolution.

[sh969]

Interesting. When you say the code runs do you get the full console output? When I run my example (via sudo python epd_7in5_V2_test.py for my version) I get:

INFO:root:epd7in5_V2 Demo INFO:root:init and Clear DEBUG:root:e-Paper busy DEBUG:root:e-Paper busy INFO:root:1.Drawing on the Horizontal image... DEBUG:root:Vertical DEBUG:root:e-Paper busy INFO:root:2.Drawing on the Vertical image... DEBUG:root:Horizontal DEBUG:root:e-Paper busy INFO:root:3.read bmp file DEBUG:root:Vertical DEBUG:root:e-Paper busy INFO:root:4.read bmp file on window DEBUG:root:Horizontal DEBUG:root:e-Paper busy INFO:root:Clear... DEBUG:root:e-Paper busy DEBUG:root:e-Paper busy INFO:root:Goto Sleep... DEBUG:root:e-Paper busy DEBUG:root:spi end DEBUG:root:close 5V, Module enters 0 power consumption ...

If yes, maybe the error is not software related. Since you are using the HAT there is little chance the GPIO connections are connected wrongly (maybe a loose soldering patch) but you could check if all the molex display connections on the HAT cables are inserted correctly.

[technimad]

Hi, I also have the color version, not V2, and I am experiencing the same issues. Nothing is displayed, yet the test runs ok. The screen is connected to the HAT. Dipswitches are in the following positions: Display config: B Interface config: 0

This is the output I get from the test script:

INFO:root:epd7in5bc Demo
INFO:root:init and Clear
DEBUG:root:e-Paper busy
DEBUG:root:e-Paper busy release
DEBUG:root:e-Paper busy
DEBUG:root:e-Paper busy release
INFO:root:Drawing
INFO:root:1.Drawing on the Horizontal image...
DEBUG:root:imwidth = 640  imheight =  384 
DEBUG:root:Horizontal
DEBUG:root:imwidth = 640  imheight =  384 
DEBUG:root:Horizontal
DEBUG:root:e-Paper busy
DEBUG:root:e-Paper busy release
DEBUG:root:e-Paper busy
DEBUG:root:e-Paper busy release
INFO:root:2.Drawing on the Vertical image...
DEBUG:root:imwidth = 384  imheight =  640 
DEBUG:root:Vertical
DEBUG:root:imwidth = 384  imheight =  640 
DEBUG:root:Vertical
DEBUG:root:e-Paper busy
DEBUG:root:e-Paper busy release
DEBUG:root:e-Paper busy
DEBUG:root:e-Paper busy release
INFO:root:3.read bmp file
DEBUG:root:imwidth = 640  imheight =  384 
DEBUG:root:Horizontal
DEBUG:root:imwidth = 640  imheight =  384 
DEBUG:root:Horizontal
DEBUG:root:e-Paper busy
DEBUG:root:e-Paper busy release
DEBUG:root:e-Paper busy
DEBUG:root:e-Paper busy release
INFO:root:4.read bmp file on window
DEBUG:root:imwidth = 640  imheight =  384 
DEBUG:root:Horizontal
DEBUG:root:imwidth = 640  imheight =  384 
DEBUG:root:Horizontal
DEBUG:root:e-Paper busy
DEBUG:root:e-Paper busy release
DEBUG:root:e-Paper busy
DEBUG:root:e-Paper busy release
INFO:root:Clear...
DEBUG:root:e-Paper busy
DEBUG:root:e-Paper busy release
DEBUG:root:e-Paper busy
DEBUG:root:e-Paper busy release
INFO:root:Goto Sleep...
DEBUG:root:e-Paper busy
DEBUG:root:e-Paper busy release
DEBUG:root:spi end
DEBUG:root:close 5V, Module enters 0 power consumption ...

[technimad]

just confirmed the c example also doesn't output anything to the screen.

./epd 
EPD_7IN5BC_test Demo
/***********************************/ 
Current environment: Raspbian
set wiringPi lib success !!! 
/***********************************/ 
e-Paper Init and Clear...
Debug: e-Paper busy
Debug: e-Paper busy release
Debug: e-Paper busy
Debug: e-Paper busy release
NewImage:BlackImage and RYImage
show window BMP-----------------
pixel = 100 * 100
Debug: e-Paper busy
Debug: e-Paper busy release
Debug: e-Paper busy
Debug: e-Paper busy release
show red bmp------------------------
pixel = 640 * 384
pixel = 640 * 384
Debug: e-Paper busy
Debug: e-Paper busy release
Debug: e-Paper busy
Debug: e-Paper busy release
show image for array
Debug: e-Paper busy
Debug: e-Paper busy release
Debug: e-Paper busy
Debug: e-Paper busy release
EPD_Display
Debug: e-Paper busy
Debug: e-Paper busy release
Debug: e-Paper busy
Debug: e-Paper busy release
Clear...
Debug: e-Paper busy
Debug: e-Paper busy release
Debug: e-Paper busy
Debug: e-Paper busy release
Goto Sleep...
Debug: e-Paper busy
Debug: e-Paper busy release
free(): invalid next size (normal)
Aborted

[tanahy]

I also have problems to draw anything at all on the 7in5_V2, but in my case the example file is more explicit about the errror:

sudo python3 epd_7in5_V2_test.py

INFO:root:epd7in5_V2 Demo
INFO:root:init and Clear
DEBUG:root:e-Paper busy
DEBUG:root:e-Paper busy
INFO:root:cannot open resource

I get two flashes of black and white and then the program ends due to the error.

[markolson]

I'm having the same issue with the 7.5 color + hat and the included examples. Going to email email support and see if they have anything helpful to say 🤷

[tanahy]

So I solved the issue I had by installing the libraries using the setup.py file, which is missing in the docs. Before doing so I had to manually set the library on the same folder as the examples but it didn't work properly as I explained before.

I would advise the dev to include the following instructions in the readme_rpi_XX.txt files, the same files for the jetson and in the wiki:

cd python 
sudo python3 setup.py build
sudo python3 setup.py install

[markolson]

Unfortunately that didn't work for me, but I do feel a bit dumb that I didn't use setup.py earlier.

[mchen0037]

I'm getting this error too, was anyone able to fix?

[jfreax]

Same display, some problems. I think that the v2 version just doesn't work with the current examples.

[mchen0037]

Is there any indicator or file I could use to verify that this is a code issue instead of a hardware issue?

[tanahy]

@mchen0037 I would recommend running the C program because it's just easier to follow the steps but in any case I was able to draw correctly with the python demo as well by using the setup.py commands I commented on before.

I also updated a small library for micropython in case you have an esp32 or similar and want to try it (check the dev branch): https://github.com/tanahy/micropython-waveshare-epaper/tree/dev

[jfreax]

@tanahy Thanks for trying to help! Neither the C, nor the Python Version works for me. My display just keeps being blank. Tried with a Raspberry Pi and an Arduino.

But I think, I probably have a completely different version. It's clearly marked as "V2" and it's 7.5" in size. That's all I know for sure. I bought it as "WaveShare 7.5inch E-Ink Display HAT for Raspberry Pi 880×528 Red / Black / White (WS17960)" from https://eckstein-shop.de/WaveShare-75inch-E-Ink-Display-HAT-for-Raspberry-Pi-880528-Red-Black-White

As you can see, it should have a resolution of 880×528 pixel, red / black / white and is version 2. None of the example matches this specification. Also none of the datasheets provided by waveshare...

[markolson]

@jfreax that’s the exact model I ordered (direct from waveshare), and they said I really ordered the “HD” model and should use that code. It still didn’t work for me, but could be worth trying.

[jfreax]

@markolson I tried all 7in5* example codes. No luck yet. I also wrote an email to waveshare's support team. Let's see if they can help.

[mchen0037]

Thanks @tanahy

I'm in the same boat as @jfreax. Neither C nor Python work out, but I also wrote them an email.

[pixelspark]

Same issue here! Interested to hear support's reply...

[markolson]

Last communication I got back from them said to try using wires instead header pins as a connection. so I'm pretty close to giving up. :-\

[jfreax]

I got an answer from the support. They told me, that my device is in fact a "HD" version, but that there is no "V2" variant of the HD devices. Otherwise, they just send me a link to their wiki. Not that helpful.

My screen is clearly labeled as "V2" on the backside. So, I'm not sure who is right here. But regardless of which version it is, I tested all 7in5 examples. On different devices, C and Python... It just doesn't work.

@markolson I'm also pretty close to giving up :(

[pixelspark]

@jfreax interesting, mine has a sticker saying "SKU: 14144. 7.5inch e-Paper (C)". What I ordered is the kit with a HAT (SKU 14229), listed as 640x384, 7.5inch E-Ink display HAT for Raspberry Pi, yellow/black/white three-color. The resolution seems to imply this to be a V1 panel.

Output from the C demo:

pi@raspberrypi:~/e-Paper/RaspberryPi&JetsonNano/c $ sudo ./epd
EPD_7IN5BC_test Demo
/***********************************/ 
Current environment: Raspbian
set wiringPi lib success !!! 
/***********************************/ 
e-Paper Init and Clear...
Debug: e-Paper busy
Debug: e-Paper busy release
Debug: e-Paper busy
Debug: e-Paper busy release
NewImage:BlackImage and RYImage
show window BMP-----------------
pixel = 100 * 100
Debug: e-Paper busy
Debug: e-Paper busy release
Debug: e-Paper busy
Debug: e-Paper busy release
show red bmp------------------------
pixel = 640 * 384
pixel = 640 * 384
Debug: e-Paper busy
Debug: e-Paper busy release
Debug: e-Paper busy
Debug: e-Paper busy release
show image for array
Debug: e-Paper busy
Debug: e-Paper busy release
Debug: e-Paper busy
Debug: e-Paper busy release
EPD_Display
Debug: e-Paper busy
Debug: e-Paper busy release
Debug: e-Paper busy
Debug: e-Paper busy release
Clear...
Debug: e-Paper busy
Debug: e-Paper busy release
Debug: e-Paper busy
Debug: e-Paper busy release
Goto Sleep...
Debug: e-Paper busy
Debug: e-Paper busy release
free(): invalid next size (normal)
Aborted

Python examples (i.e. epd_7in5bc_test.py) are showing more or less the same: the 'busy' line apparently is going up and down (indicating valid communication between the Pi and the controller on the HAT), but nothing ever shows up on the screen.

[technimad]

Last communication I got back from them said to try using wires instead header pins as a connection. so I'm pretty close to giving up. :-\

Hi,

Did you try connecting using wire pins? I did, and now the examples work!

Details of my setup: rpi4b SKU: 14144. 7.5inch e-Paper (C) HAT rev2.1

Connected not directly as Hat to the gpio headers, I use the supplied wires, connected to the hat:

Reference for the pinout of the wires:

• https://pinout.xyz/pinout/spi
• https://www.waveshare.com/wiki/7.5inch_e-Paper_HAT_(B) (Hard- software tab)

Don't know why this works, and not when directly connected. But it seems to work as expected.

[pixelspark]

I did actually use the wires, with an ancient Raspberry Pi original model B. The old Pi might be the culprit (will try with a Pi Zero as soon as I can find the header to solder to the board).

[markolson]

I used wires on my Pi Zero W, but will try with a Pi B+ this weekend

[mchen0037]

I just tried wires again, no luck. I'm using a Rasp Pi 4 Model B.

[waveshare]

Hello everyone, I want to say sorry first because we do not check the GitHub all the time and it is hard for us to reply to issues. If you have any question want to confirm with us directly, please send an email to [email protected].

[waveshare]

As you know, we have three kinds of 7.5inch e-Paper. The oldest one is the V1 version with 640x384 resolution and it stops producing. The demo codes for the V1 version should be epd_7in5_test.py and epd_7inch5bc_test.py. The V2 version has 800x480 resolution and the codes should be epd_7in5_V2_test.py and epd_7in5b_V2_test.py The HD version has 880 x 528 resolution and the codes should be ped_7inch5_HD_test.py and epd_7in5b_HD_test.py.

Please confirm the type of e-Paper you bought and use the correct codes.

[waveshare]

And please check if you have connected the e-Paper panel in the correct way, we found that some of the users reverse the cables and it causes the problem. Please set the Display Config switch to B sides.

If you check that all the cables and confirm that all are connected properly, please clone the newest demo codes and try again. And make sure that the SPI interface was enabled and doesn't use for other drivers or devices.

[waveshare]

Last communication I got back from them said to try using wires instead header pins as a connection. so I'm pretty close to giving up. :-\

Hi,

Did you try connecting using wire pins? I did, and now the examples work!

Details of my setup: rpi4b SKU: 14144. 7.5inch e-Paper (C) HAT rev2.1

Connected not directly as Hat to the gpio headers, I use the supplied wires, connected to the hat:

Reference for the pinout of the wires:

• https://pinout.xyz/pinout/spi
• https://www.waveshare.com/wiki/7.5inch_e-Paper_HAT_(B) (Hard- software tab)

Don't know why this works, and not when directly connected. But it seems to work as expected.

Do you have a multimeter to test if there are shorted pins in the black connector of the driver board?