I also found that if additional images are sent to the e-paper screen at a later time, it is best to power off the screen instead of deep sleep. Deep sleep clears the "Old" image registers and the screen should be cleared before a new image is sent. Sending a power off command when you are done with an image, then a power on command before the new image is the proper way to do this and the screen response time is good. So I added On, Off and Wake methods. The Wake method basically re-initializes the screen, which I understand is the best practice for coming out of a deep sleep.
I did not add unit tests to your driver for On and Off since I don't know for sure they are work as they are supposed to. I looked at the specifications for the device and the code should be the same as for the Epd7In5_V2 but you may want to verify functionality first.
Hi,
I added UnitTests for Epd7In5_V2 device.
I also found that if additional images are sent to the e-paper screen at a later time, it is best to power off the screen instead of deep sleep. Deep sleep clears the "Old" image registers and the screen should be cleared before a new image is sent. Sending a power off command when you are done with an image, then a power on command before the new image is the proper way to do this and the screen response time is good. So I added On, Off and Wake methods. The Wake method basically re-initializes the screen, which I understand is the best practice for coming out of a deep sleep.
I did not add unit tests to your driver for On and Off since I don't know for sure they are work as they are supposed to. I looked at the specifications for the device and the code should be the same as for the Epd7In5_V2 but you may want to verify functionality first.
Cheers from the United States!
Best regards, Greg