Waveshare hardware quality: any experience?
Posted: Wed Jan 13, 2021 2:23 pm
Blaming hardware is my last call but there seems little doubt that I have encountered two of these e-ink HATs with problems.
I am trying to get nanogui to support at least one ePaper display so I wrote a driver for the board based on that of @mcauser and official Waveshare code. The first unit refused even to clear the display properly and I measured some very suspect logic levels on the board. I figured I'd struck unlucky and bought another from the Waveshare eBay store. I had more success with this one. On occasion the GUI demo programs ran perfectly, but if I left it overnight and ran the same code the next day it failed, sometimes with the weirdest symptoms. For example a display update taking 20 minutes. I could sit at the REPL watching the display faffing about on its own before eventually settling down and releasing the busy signal. Sometimes the display would show interchanged black and white pixels. And so on. The board has no concept of deterministic behaviour
By contrast I adapted the driver for an Adafruit EPD and barring one typo and one silly bug it worked first time. As always, Adafruit hardware does what it says on the tin
I studied the Waveshare boards carefully and even disconnected the display from one, cleaning the contacts and connector with IPA before reassembling. No joy. I can't see an obvious fault but I suspect there is a floating CMOS input on the second board.
Have I been extraordinarily unlucky or is Waveshare quality control generally suspect?
I am trying to get nanogui to support at least one ePaper display so I wrote a driver for the board based on that of @mcauser and official Waveshare code. The first unit refused even to clear the display properly and I measured some very suspect logic levels on the board. I figured I'd struck unlucky and bought another from the Waveshare eBay store. I had more success with this one. On occasion the GUI demo programs ran perfectly, but if I left it overnight and ran the same code the next day it failed, sometimes with the weirdest symptoms. For example a display update taking 20 minutes. I could sit at the REPL watching the display faffing about on its own before eventually settling down and releasing the busy signal. Sometimes the display would show interchanged black and white pixels. And so on. The board has no concept of deterministic behaviour
By contrast I adapted the driver for an Adafruit EPD and barring one typo and one silly bug it worked first time. As always, Adafruit hardware does what it says on the tin
I studied the Waveshare boards carefully and even disconnected the display from one, cleaning the contacts and connector with IPA before reassembling. No joy. I can't see an obvious fault but I suspect there is a floating CMOS input on the second board.
Have I been extraordinarily unlucky or is Waveshare quality control generally suspect?