Inkplate 5 partial refresh safety and speed limits

Customer:

I’m building a mobile writing setup with an Inkplate 5 and a keyboard for my fiancé. I chose it for the fast partial update speed, but the code comments have warnings like “(Use this only in this scenario, otherwise YOU CAN DAMAGE YOUR SCRREN)” everywhere. I’m concerned about damaging the screen but can’t find reliable information on how to use partial updates safely.

What are the hard limitations? What will definitely work and what might cause damage? Also, does update speed vary depending on the mode I use (Arduino, MicroPython, peripheral)? I assumed Arduino would be fastest but I’m not sure.

Originally submitted via email support on 15 July 2024. Migrated to the forum for community visibility.

Soldered Support:

You can use Inkplate 5 without a problem by using partial update in basic usage. The advanced mode is for users who want extra control and are familiar with e-Ink. Check the example: Inkplate-Arduino-library/examples/Inkplate5/Basic/Inkplate5_Partial_Update/Inkplate5_Partial_Update.ino at master · SolderedElectronics/Inkplate-Arduino-library · GitHub

Use partialUpdate like normal (BASIC USAGE in the example), and count the partial updates. When you reach a certain number, do a full refresh with display.display(). For the exact number of partial updates before a full refresh, around 15 to 20 is usually fine, but for a typing sketch even more would work because there won’t be too many artifacts - you’re just drawing new black pixels over a white background, so you can increase this number.

Arduino would definitely be the fastest update.