Inky Impressions 7.3 Interfacing Error

Support
1

Hello,

Up until two days ago everything was going swimmingly. I was using my new Inky Impressions eink 7.3 inch 2025 frame with no issues. I’m pretty new to python and I’ve been programming a simple image cycle program as well as quote/joke cycle programs. It has been fun learning using this tool.

Interfacing with the board I almost exclusively use the following lines of code:

from inky.auto import auto,

inky = auto(ask_user=True, verbose=True)

inky.set_image(resizedimage, saturation=0.7)

inky.show()

Up until the last two days I have had no issue uploading images to the screen. But all of a sudden I have not been able to interface with it.

Initially, I got the following terminal output when using the auto() recognise function:

warnings.warn(
Failed to detect an Inky board. Trying --type/–colour arguments instead…

usage: joke_display.py [-h] [–simulate] --type

  •                   {what,phat,phatssd1608,impressions,7colour,whatssd1683,impressions73,spectra13,spectra73}*

  •                   [--colour {red,black,yellow}]*

joke_display.py: error: the following arguments are required: --type/-t

And when I try to us the inky.ac073tcla driver (from inky.inky_ac073tc1a import Inky) directly I get the following terminal output:

warnings.warn(
/home/allan/.virtualenvs/pimoroni/lib/python3.11/site-packages/inky/inky_ac073tc1a.py:224: UserWarning: SPI: Cannot disable chip-select!

  • warnings.warn(“SPI: Cannot disable chip-select!”)*
    /home/allan/.virtualenvs/pimoroni/lib/python3.11/site-packages/inky/inky_ac073tc1a.py:285: UserWarning: Busy Wait: Held high. Waiting for 1.00s
  • warnings.warn(“Busy Wait: Held high. Waiting for {:0.2f}s”.format(timeout))*
    [1905:1905:0524/150247.946121:ERROR:components/dbus/xdg/request.cc:169] Request ended (non-user cancelled).

I have checked that both the i2c and SPI are enabled but with no change in function.

I can use both the button.py and led.py provided examples with no issue.

The quote I have been stuck looking at for the last two days, proof I did have this working prior to this issue:

PXL_20250524_054054531
PXL_20250524_0540545311920×1446 183 KB

Any help on this issue is appreciated. Not sure what to do from here.

Cheers,
Allan

2

This driver is definitely the wrong choice. you will need the inky_e673-driver.

What I would suggest: start with a clean PiOS install and try to run the example programs. Also re-check the mechanical connection. If you have a second Pi, also test with that alternative device.

If all of this fails, it is probably a defective unit. It seems that you cannot communicate anymore with your Inky. You should then contact support (and link to this post).

3

Thanks for the reply :)

So I’ve tried your suggestions. Unfortunately, using the unit with a different raspberry pi did not change the outcome. I get the same error.

I’ll get in touch with the pimoroni team support team.

Cheers,