Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issues with 7in5_V2 screen since Waveshare Update #143

Closed
TomWhitwell opened this issue Jan 11, 2023 · 11 comments · Fixed by waveshareteam/e-Paper#289
Closed

Issues with 7in5_V2 screen since Waveshare Update #143

TomWhitwell opened this issue Jan 11, 2023 · 11 comments · Fixed by waveshareteam/e-Paper#289
Labels
bug Something isn't working

Comments

@TomWhitwell
Copy link
Owner

Notes on the issue highlighted and worked around in #134

Between June 2021 and October 2022
there were two significant updates to epd7in5_V2.py in the Waveshare repo.

  1. The system for writing data over SPI was changed - send_data2 uses spi_writebyte2 rather than spi_writebyte
    This was discussed here back in Changes in v0.2 #18

  2. getBuffer is significantly changed - I don't understand the changes there

The impact on SlowMovie is that the screen is very streaky (see images in #134 ) if SlowMovie is installed or updated.

The workaround is explained here - by @robweber

I don't know if this impacts any other screens - there were a couple of specific bugfixes on epd7in5_V2.py

I don't know which change (or something different) is causing the streaking.

@TomWhitwell TomWhitwell added the bug Something isn't working label Jan 11, 2023
@missionfloyd
Copy link
Collaborator

missionfloyd commented Jan 12, 2023

This is caused by waveshareteam/e-Paper@99f6a13. It's supposed to refresh faster.

@robweber
Copy link
Collaborator

What is a proper "fix" on the part of either SlowMovie or omni-epd for this? It seems to only affect a handful of displays (the 7.5 for sure). We could tag a specific Waveshare version but that might affect potential fixes for other issues across other devices in that same repo. Is this more of an FYI and we put some disclaimers up for people in various places in the README or install scripts?

@TomWhitwell
Copy link
Owner Author

I don't know, I'm not sure of the best approach.

It feels sad to me because all the work you've done to get a simple beginner-friendly one-line install now fails for the 'original' screen in the article and the default.

Do you think that update of the 7.5 inch monochrome screen driver is just a mistake on their end - will it break anything trying to render complex images on the screen? I don't really understand the system well enough. Should I report it as a bug? Should they have implemented a new fast method that doesn't break the existing method?

Options might be:

  • Change default and documentation to recommend another screen in a similar size that works properly
  • Just document the one-line installation fix
  • Point to a specific waveshare version
  • Ask Waveshare to fix it

@robweber
Copy link
Collaborator

Been thinking about this for a while - how does this sound for a tentative fix?

  1. Definitely file a bug with Waveshare - this may or may not go anywhere but fix at the source would be best
  2. Add a disclaimer to both the README and install script regarding the issue with the 7.5in devices
  3. Add a menu option in the install script to rollback the waveshare driver to the known working version

Thoughts?

@TomWhitwell
Copy link
Owner Author

Hi Rob, hesitating on this because my OG VSMP isn't working - just did a completely fresh install of Raspberry OS, checked the mode switches on the hat, ran your fix above and I'm getting super noisy & streaky images, similarly with the waveshare test script - it's like it loads the image correctly, then as it refreshes, a lot of black pixels turn white.

I think your suggestion sounds ideal, but not currently working for me unfortunately.

IMG_0971

@robweber
Copy link
Collaborator

That's really bizarre given that the old version from above has fixed it before. I'm hesitant to mess up my own setup but I'll flash a new SD and do a clean install as well to see if I get the same result.

@TomWhitwell
Copy link
Owner Author

TomWhitwell commented Feb 24, 2023

I know - it feels more like a hardware problem - I reverted right back to my original code and it behaved the same. I think had it set in the wrong switch position for a while, wonder if that did some damage. Maybe 25,000 hours of use is excessive?
BUT still, it's clearly receiving data and refreshing. So maybe not hardware at all!

@robweber
Copy link
Collaborator

I did a clean install of the most current branch of the waveshare python libraries. Noticed streaking on every image I tried to load. I uninstalled this and did an install using commit b36cfab0ea336673982640ea21969e5a54714448 from above. Streaking stopped and things went back to normal.

Your issue may very well be hardware related :(

@robweber
Copy link
Collaborator

I've started a PR to add a disclaimer to the README and allow for the option to rollback the driver via the install script. Hopefully this should catch most use cases.

@wobblewoo
Copy link

I've just purchased and attached a 7.5 V2 Waveshare without any problems.
Used this driver waveshare_epd.epd7in5_V2
if that helps any.
Wx

@robweber
Copy link
Collaborator

Going to close this out since @missionfloyd has fixed this in the Waveshare lib.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
4 participants