Inky Impression library doesn't work about omni-epd HOT 9 CLOSED

That all sounds really crazy! At a very low level it makes each EPD driver is just sending commands to the board, so perhaps there is some overlap in the low level IO; but the fact that a completely different vendor's implementation is working on the Inky is some bizarre behavior.

One telling thing is that the Pimoroni examples aren't working. These are default from the manufacturer so those not working as designed is kind of a red flag. I'm curious why you tried the waveshare driver, and why that particular one?

@missionfloyd - you had originally verified the Inky Impression code so I'm guessing you have one? Any troubleshooting steps you can think of?

from omni-epd.

I tried SlowMovie and changed the preference, and it didn't work. I then tried the helloworld demo that came with SlowMovie - and for the first time something happened - a Pimoroni demo I had submitted earlier (or the previous day) showed up on the screen. I looked at the code and it imported the epd7in5_v2 driver. I tried drivers in your omni-epd call (starting with inky.impression - which did nothing) until one worked regularly (5in83) in your draw rectangles test. Now I can regularly reproduce the following - 1. Submitting Pimoroni script (nothing happens but script thinks it succeeds' 2. run omni-end-test -e waveshare_epd.epd5in83 and the image from step 1 appears. Odd, right? I was hoping your inky.impression driver would just work..

from omni-epd.

here is a video (zipped). if you look at the screen before you play the video you can see identify.py telling me my display properly. then I run stripes. nothing happens..a previous logo image remains on screen. Video starts with me run omni-epd-test with the waveshare driver and you can see the inky screen - and it draws stripes based on the stripes.py script.
IMG_2473.mov.zip

from omni-epd.

curious - as I'm not a developer/engineer - is there some command that is missing from the inky.impression driver that exists and is triggered at the start of the waveshare epd7in5_v2 driver..that could result in activating whatever was in the 'buffer' (for lack of a better term)

from omni-epd.

I just installed the latest inky and omni-epd versions, and omni-epd-test -e inky.impression seems to work here.

As for the pimoroni examples, did you enable i2c? It's needed for autodetection to work. You can also manually specify a display with the --type impressions argument

from omni-epd.

from omni-epd.

Thanks for the update. Please follow-up, perhaps it's just a hardware issue after all.

from omni-epd.

from omni-epd.

That's great news - although not super awesome you had to get a whole new piece of hardware. Glad it's working.

from omni-epd.