hzeller / rpi-rgb-led-matrix

Controlling up to three chains of 64x64, 32x32, 16x32 or similar RGB LED displays using Raspberry Pi GPIO
GNU General Public License v2.0
3.63k stars 1.15k forks source link

Top half of panels in 3rd chain has problems with blue #837

Open d3d9 opened 5 years ago

d3d9 commented 5 years ago

I use the Raspberry Pi 3 Model B+ (also tested this on a Pi Zero W, same result) with the "RGB Matrix Panel Drive Board For Raspberry Pi" from Electrodragon. The top half of both panels in the 3rd chain has problems showing the blue color.

A full blue color like in the square image demo or in the demo that lights up different colors and transitions between them does not light up at all. In between, with the less bright blue colors, there is some flickering of the blue colors, they light up, but not really like they should.

Here are some pictures (of the two panels in the third chain):

The third line has the correct color behind the text, it's rgb(0, 8, 9). image

Here's a closeup of the left part of the top 2 lines. Some of the blue lights actually light up, you can see the way it happens in this video. image

A closeup of the orange text (in the area without the blue background). The color of the text is rgb(255, 65, 0), it should not show any blue, but it is visible on some pixels. image

Here is the bottom left part of the test square, like in the demo with the color transitions, the "more than a little" blue is not visible at all: image

d3d9 commented 5 years ago

A video of the other demo: https://photos.app.goo.gl/57DFucXrPKHhjD9W6 There was no "flickering" of the light blue color today (maybe because I actually connected all 3 chains), the main problem still persists though.

hzeller commented 5 years ago

I suspect you need to inspect your hardware if the blue line is properly routed through. Either the problem is on the adapter board or the wiring to it.

hzeller commented 5 years ago

Also, if you have problems with long chains, try a higher gpio-slowdown. Always make sure to have very short cables between the panels. Make sure, power is stable.

hzeller commented 5 years ago

Also, did you make sure to switch off I2C on your Pi (see troubleshooting section)? The blue line for the third panel uses that pin.

d3d9 commented 5 years ago

I think I did that. I'm going to look at everything again in the next week and I'll check the settings, the adapter board (and the wiring without it as well) and I will try to find where the problem comes from.

d3d9 commented 5 years ago

I did the wiring manually now (only connected the 16 pins for the 3rd chain using jumper cables) and it worked without problems, so it seems like it is something with the adapter board (it happens on at least two of them, not just a problem on one board).

After reconnecting the board and being about to write this reply, I tried toggling the switch it has (between I2C for the RTC; and the 3rd chain, but don't misinterpret this as me having forgotten to switch it to the 3rd chain the whole time :smile:) just to see what happens -- as expected, the result wasn't a very useful appearance, with the whole top half being blue -- but when switching back to the 3rd chain, it was kinda weird at first and after I just put my finger close to the "switch" without turning it back to I2C again suddenly the blue color on the 3rd chain top half worked as expected..

It would be interesting to know if someone else who owns this adapter board can experience similar things. In any case, it seems like this issue can be closed.

jbodswor commented 5 years ago

I just bought two of these adapter boards and put it together last night using 3 parallel chains of 4 panels (64x32) using a Rasberry Pi 4. I am only seeing red on top half of the third chain. Changing out the board for the other, changing out the Pi with another, and swapping the panels around confirmed that there is definitely a problem with the third chain on the board.

After extensively looking at the software and disabling the I2C and 1-wire interface, I am convinced that it is something to do with the board. I plan to look more closely and use my multimeter to track the integrity of the pins. Will also look into the switch integrity as you mentioned. I will report back when done.

BTW - are you using a Pi 4? I am having trouble installing some packages with the minimal Buster Lite OS. More specifically, not finding versions of some dependencies. Are the maintainers a bit behind for Buster? Output below when trying to install python-dev, libgraphicsmagick, libwebp-dev, and some others.

sudo apt-get install libgraphicsmagick++-dev libwebp-dev -y

...<truncated> E: Failed to fetch http://raspbian.raspberrypi.org/raspbian/pool/main/b/bzip2/bzip2-doc_1.0.6-9_all.deb 404 Not Found [IP: 93.93.128.193 80] E: Failed to fetch http://raspbian.raspberrypi.org/raspbian/pool/main/libp/libpaper/libpaper1_1.1.26_armhf.deb 404 Not Found [IP: 93.93.128.193 80] E: Failed to fetch http://raspbian.raspberrypi.org/raspbian/pool/main/b/bzip2/libbz2-dev_1.0.6-9_armhf.deb 404 Not Found [IP: 93.93.128.193 80] E: Failed to fetch http://raspbian.raspberrypi.org/raspbian/pool/main/libp/libpaper/libpaper-utils_1.1.26_armhf.deb 404 Not Found [IP: 93.93.128.193 80]

hzeller commented 5 years ago

not found messages usually means you need to apt-get update first to get the current list of available packages.

jbodswor commented 5 years ago

UPDATE: Turns out that the switch was not seated correctly on both ElectroDragon boards. Once the switch was seated correctly, everything works perfectly. Must check that the switch is in the correct position.

jbodswor commented 5 years ago

I have done the apt-get update and apt-get upgrade, however the files referred to in the package are not in the archive for Raspbian Buster. For example, the file http://raspbian.raspberrypi.org/raspbian/pool/main/b/bzip2/libbz2-dev_1.0.6-9_armhf.deb doesn't exist and has been replaced by http://raspbian.raspberrypi.org/raspbian/pool/main/b/bzip2/libbz2-dev_1.0.6-9.1_armhf.deb. I think that the maintainer of the package is yet to update the package for Raspbian Buster.

I am investigating how I can either make a request to the maintainer or manually install the ever so slightly newer version.

jbodswor commented 5 years ago

SOLVED: Had to run apt-get update --allow-releaseinfo-change to allow the release of Buster to change from the version it shipped with to the latest one. Found this advice here: https://superuser.com/questions/1456989/how-to-configure-apt-in-debian-buster-after-release