Customer:
I just received my Inkplate 5 Gen 2. The display looked fine with the static image out of the box. But when I use the drivers for MicroPython as instructed at SolderedElectronics/Inkplate-micropython: Micropython driver for Inkplate boards github.com, the resolution appears to be wrong. In the driver file it says D_ROWS = const(540) and D_COLS = const(960), but the Inkplate 5 Gen 2 is 720x1280. Is it as simple as just modifying the resolution in the driver, or do other things require modification? When I do this and run one of the basic examples, it is somehow mirrored. What do you recommend? Do you have an Inkplate 5 Gen 2 MicroPython module available somewhere?
Attachment omitted in migration: Inkplate-micropython.png
Attachment omitted in migration: image.jpeg
Attachment omitted in migration: image.jpeg
Originally submitted via email support on 31 October 2024. Migrated to the forum for community visibility.
Soldered Support:
Official MicroPython support doesn’t yet exist for Inkplate 5V2. We have only made one for Inkplate 5 so far, and our R&D team has been alerted to try and create it as soon as possible using Inkplate 5 as a base.
I would strongly recommend giving the Arduino library a try. It has all the possible latest features on Inkplate. The MicroPython library was originally a user contribution that we adapted to create support for more boards, but it’s not nearly as fully-featured as the Arduino one, as that’s where our expertise is. The actual writing of code and syntax are not too different between them, and the Arduino library works well.
Customer:
I am getting weird display issues after switching to the Arduino library. The display is perfectly fine and normal when using MicroPython (after my modifications). But in Arduino I get weird blurry, repeated text, and strange lines at the left edge of the screen. Do you know why? Is there any other support channel where I could ask questions like this?
Attachment omitted in migration: IMG_1301.jpeg
Soldered Support:
The display issues you’re describing look like a timing or connection issue with the panel. Please check the following:
- That you’re using the latest Inkplate 5V2 board definition
- That you’re using the latest version of the Inkplate library (a short guide for both is in our docs)
- That you’re using the example basic->black and white (this is the most basic example so it’s good to test)
If it still doesn’t work, could you please try opening the case (there should be a mark “open here” on the side) and gently pressing down on the flat cable connector to see if the display can update better while you press this. You can also try re-connecting it, just be gentle with the flat cable to not crease it hard. Sometimes, in shipping this connector can get a tad loose which can cause artefacts like this.
Attachment omitted in migration: image.png
Customer:
It turned out that the problem was that there is display corruption when the display is refreshed while the device is plugged into my computer. Of course, because it is eink, the corruption does not go away when you simply unplug. In case other customers have a similar experience: one image was refreshed while plugged in, the other which was refreshed without being plugged in. Both photos show the difference clearly.
Attachment omitted in migration: Screenshot 2024-11-08 at 08.44.43.png
Attachment omitted in migration: Screenshot 2024-11-08 at 08.44.54.png
Soldered Support:
This seems to be quite a low-level issue. I will report this to our R&D team because we have had this kind of thing happen but with a different model. First time I see this on Inkplate 5V2.
Customer:
It is the other way around. It’s fine when powered via the battery, but has artifacts when plugged directly into my MacBook Pro M4 with a USB-C cable. So it is mostly fine, as long as I mostly refresh it on battery.
Soldered Support:
This could be resolved with a library update. Our R&D team lead, who wrote all the drivers and knows the intricate timings of ePaper panels, may have insights on this.
Soldered Support:
We suggest trying one more thing: use a different USB-C cable and port to power the device. These panels are sensitive and maybe the Mac USB port and cable just aren’t suited for powering it. Give that a try and see if you can remove the issue that way.