The only other thing I can think of is file ownership, i.e. the user the script is running as, doesn’t have permissions to access hardware peripherals.
In the terminal, I typed sudo mousepad /etc/rc.local to edit it
I added /home/pi/inky/examples/7color/html.sh /home/pi/inky/examples/7color/hello-world.html
and it did something interesting. It created a new screenshot in the filesystem root folder /screenshot.png with the content that I want to display.
It didn’t put it on the e-ink display, but it did something, which was the lightbulb moment! That image.py it references didn’t know where that picture was and therefore couldn’t run.
I edited the last line of html.sh to /home/pi/examples/7color/image.py /screenshot.png
and it works perfectly!!
Thank you so much James(!!!) for your help in getting this going, and I will share the final project once its finished.
Oh yes! (sory for the late reply) I saw this one a while back and it’s the PERFECT size for my art. Upscaling the art I make comes out to the exact same height of 480. I’m actually waiting on a photoframe made using that screen. I’m looking forward to displaying multiple art pieces!
Hi - I really like the colors you achieved with your code. Is there a way I can use this for the inky frame? It uses the same screen, but with a picow, so it uses Thonny to communicate with the screen.
Looks like the image example script doesn’t provide a saturation option (processing images is hard work, probably beyond a Pico), so I would up the saturation in paint.NET or GIMP before transferring it to the Pico.
When I run “python3 run-on-boot.py”, I get “Detected 7-Colour (UC8159)
Usage:
image.py --file image.png (–saturation 0.5)”
Has the image.py command changed?
Welcome to the forum! When running python3 run-on-boot.py you will need to specify your file path. Have you done this? Which Pi and OS are you using as well?
I have set up a new RPi in a venv and followed the directions as per your instructions and also those on PyPi. I get this error when trying to update the display:
“Woah there, some pins we need are in use! Chip Select: (line 8, GPIO8) currently claimed by spi0 CS0”
There is a thread on the pimoroni site addressing the issue, but with no clear solution. There is a suggestion you have to play with the config file, but this worked for one person, and not for another.
I feel that (if something extra has to be done) why the information is not provided by the Inky vendors; the onus is on them to provide clear details as to what has to be done to make their product work! What I’m trying to do is simple, i.e. display an image on the screen, and whilst I admit I am a relative beginner, I just don’t think it has to be so hard!!
Any thoughts?
David
I have done some light research into this and it seems like the solution of adding the line dtoverlay=spi0-0cs to the bottom of the config.txt file (located at /boot/firmware/config.txt on bookworm) seems to fix this issue for most users.
The post I have found that don’t have success with the method seem to have at least moved on to a different error message after making this change so if you haven’t already, I would give this a shot and see if it helps out!
Let us know how that goes for you and we can help out with any other problems that pop up
Hi Sam,
Thanks! Reinforcing my idea that the RPi is proving to be a bizarre hobby, that line was already the last in my config file on starting up the RPi again! I absolutely did not put it there!! But suffice to say that after giving my code one last go, I have now successfully refreshed the image on the inky display!
Cheers, David