Update epd3in7 sleep command #234
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This fixes an issue where after issuing a `sleep`, the display never wakes up again.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When calling the
sleepfunction on the 3.7inch e-Paper HAT (with a Pico 2W as MCU), the display stops responding altogether and a power-cycle is needed to revive it.The implemented sleep routine is not matching the driver spec PDF linked in the Waveshare wiki page:
Sleep-0x50,PowerOff-0x02, andSleep2-0x07) is not to be found in the document and theSleepandSleep2commands are not listed.DeepSleep-0x10command is listed in the flow chart instead.This PR modifies the sleep implementation for
epd3in7to use the deep sleep command instead of the previous command sequence.With the change in place, the display responds when being waken up with
wake_up. Thewake_uproutine is already doing the correct full re-initialization as specified in the datasheet.This is likely the same issue as reported in #227.