Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

64x32 P5 panel "YS-P5-320X160-8S-1921(PRO)-V1" not displaying any output. Completely Blank. #1744

Open
Croconaw-bot opened this issue Dec 18, 2024 · 4 comments

Comments

@Croconaw-bot
Copy link

I am trying to display to a 64 by 32 P5 panel. It has the code: YS-P5-320-160-8S-1921(PRO)-V1
No pixels light up when trying to display to the panel.

The panel has the following chip specs.
Driver: SM16169SH
Line Decoder: 74HC138
Additionally there are two chips labelled on the input HUB75 side RUC7258d, and then 2 more on the output HUB75 side, if that helps.

From the namecode I would assume 1/8 scan. And the pinout printed on the output HUB75 socket seems to imply ABC addressing, however I have it on relatively decent authority that it might have a D line on the pin labelled GND opposite the C pin, for some reason. probing on the pin, points to it being grounded though.
I have managed to make maps for panels of different pixel size before by reverse engineering pixels positions, this one is a bit different.
With previous panels, I could test different multiplexing and row addressing methods and work backwards from there to remap pixels to their correct places.
In this case the entire panel is blank no matter which mapping scheme or row addressing I perform.
No pixels light up on test, including when it is set to display a completely white box the size of the panel.

Any advice or insight into getting a panel like this to work is appreciated.

IMG_0574
IMG_0575
IMG_0578
IMG_0579
IMG_0572
IMG_0573 (1)

@davemaster
Copy link

davemaster commented Dec 18, 2024

Greetings,

And, WHERE is your command line? Where your connection from RPi (what Rpi do You have) to HUB75

@Croconaw-bot
Copy link
Author

Croconaw-bot commented Dec 18, 2024

Hi,
I'm using the Pi Compute Module 3, the gpio is mapped to go from the DIMM socket pins to a HUB75 connector through bus transceiver chips, operating mostly as a high speed logic level convertor. from there, a standard ribbon cable for the Hub75 connector connects to the panel.
The command I have used is:

./led-image-viewer --led-chain=1 --led-parallel=1 --led-gpio-mapping=cm3-custom --led-rows=32 --led-cols=64 --led-row-addr-type=0 --led-multiplexing=1 -C -w5  ../images

The gpio mapping is custom to the pcb, and has worked with other p5, p8, and p10 panels.
I have varied the multiplexing and row addressing to no avail, and have also played with gpio-slowdown, led-pwm-lsb-nanoseconds, and led-pwn-dither-bits; From what I have been able to test with those parameters, I have not been able to get a pixel to show.

@davemaster
Copy link

Every panel (RGB) it's a different story. Try first, using demo... and wiring "regular", picture and result if any....

@board707
Copy link

board707 commented Dec 22, 2024

I would assume 1/8 scan. And the pinout printed on the output HUB75 socket seems to imply ABC addressing

Every panel with 1/8 scan has only a A B C pins (not D or E) for addressing. And it can be either shift registering or binary type multiplexing. According to line driver type (TC7258) - your panel has a standard line driver type, so your --led-row-addr-type=0 option is correct.

As about a LED driver chip - SM16169SH - I afraid it is a new PWM-type led driver, most of them are not supported by the library. Most likely this is the reason why your panel does not work. Unfortunately, if the problem is in the driver, there is no way to fix it, you will have to look for another panel.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants