bk1285 / rpi_wordclock

Software to create a Raspberry Pi based wordclock
GNU General Public License v3.0
214 stars 107 forks source link

rasperry pi zero not compatible ? #65

Closed Carlos464 closed 6 years ago

Carlos464 commented 7 years ago

Hello,

I am trying to get the wordclock up and running with an raspberry pi zero, but that does not work. The software is running, but none of the LEDs is getting on.

The same config with an rpi2 is running fine.

Do I have to tweak the software? Anyone else having these issues?

Thanks in advance.

Carlos

adamenatsky commented 7 years ago

Hi Carlos. I have gotten the clock to start working on a pi zero w. A few possible bugs I noticed after tinkering are that I had to disable the opening message in the config file for the clock to start working, not sure why. Second issue I ran into was that the clock would only work when started from the cron at boot. When starting it manually from the command line the lights would just blink randomly and show me a jumble of colors. Otherwise it works fantastically on the pi zero. Let me know if I can help with any questions you have. I'm not an expert just a hobbyist by the way.

Carlos464 commented 7 years ago

Hi adamenatsky,

thanks for your reply.

Do you use the same GPIO Pins as mentioned in the docs? The opening message is already deactivated and the program starts via cron at boot.

best regards Carlos

adamenatsky commented 7 years ago

Yes I followed Bernd's wiring and GPIO pin usage. My python skills are quite novice so I didn't want to mess around with the source code until I got comfortable with the device working in its normal state.

bk1285 commented 7 years ago

Hi all, thanks for your input!

Find first reports and discussions on Pi0 here: https://github.com/bk1285/rpi_wordclock/issues/44 Hope it helps you make the clock run.

Just in case you find out futher tricks, it's great, if you share them here.

Best, Bernd

bk1285 commented 7 years ago

Did you take this page into consideration: https://github.com/bk1285/rpi_wordclock/blob/master/docs/doc_troubleshooting.rst

... a disabled soundcard for only one of the two Pis might be an issue?

adamenatsky commented 7 years ago

Hey Bernd I'm new this whole github community. Should I add any notes I posted here to he #44? Or is the link you put up good enough?

And yes I did look at the troubleshooting page early on. Only issue I ran into listed there was the GPIO Pin 17 thing. But that was cleared up quickly once I connected the buttons and LEDs.

Thanks for your all you work on this project! Its been fun getting it up and running.

Carlos464 commented 7 years ago

Hi Bernd. I just tried the suggestions from your link. Still no luck.

Anyone any further ideas?

best regards Carlos

Carlos464 commented 7 years ago

@adamenatsky

Can you do me a favor and post the output of

gpio readall

on your working raspberry pi zero.

Thanks in advance.

best regards Carlos

adamenatsky commented 7 years ago

@Carlos464 I will do so hopefully later this evening or tomorrow. I'm just now resoldering my buttons in a permanant placement and will have the pi up and running then.

Carlos464 commented 7 years ago

Hi all,

it's still not working with the rPi0. Would like to get it up and running.

@adamenatsky Any chance to upload a screen of the output of

gpio readall

best regards Carlos

adamenatsky commented 7 years ago

@Carlos464 Apologies for the delay. As I'm not good at soldering, I damaged some of the pixel connections while making permanent wiring placements and I am in the process of redoing them. I'll get your readall as soon as I can.

Carlos464 commented 7 years ago

@adamenatsky

I started over from scratch and now it is working with the raspberry pi zero. From smoke to smother. Now the rPi hangs randomly. I will open a new thread.

best regards Carlos

ruedli commented 6 years ago

I removed the message on missing libraries, as it turned out to be caused by a failed / missing command:

sudo pip install pytz astral feedparser pillow svgwrite freetype-py netifaces monotonic

It caused the plugins that depended on them to fail, which is logical. The wordclock now works OK with my raspberry pi zero W.