-
Notifications
You must be signed in to change notification settings - Fork 32
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
I can't get this to work on a Raspberry pi running rpi-matrix-pixelpusher. #21
Comments
First make sure to have the 64x64 matrix working by running the demos in the parent project For 64x64 panels, there are various options, some have A,B,C,D,E address lines, others only have A,B and a different address mode. Start with reading about the settings and things you can configure there to make the panel work. Then from there, you can apply the same configuration settings for your set-up here. |
@hzeller I am having the same issue. Would you mind checking if I am doing something stupid? Banging my head against the wall after failing to get a ZeroMQ-server setup (REQ-RES working on pi but failing to send from desktop through same ping-able ip). All the code I have tried in the parent library works perfectly. Hoping this is not related to the new Apple M1 chip. example (sudo ./led-image-viewer /home/aidan/rgbMatrix/content/Spirald.gif --led-rows=32 --led-cols=64 --led-chain=7 --led-slowdown-gpio=4). Runs great. When I run the pixel push program with the same flags (sudo ./pixel-push --led-rows=32 --led-cols=64 --led-chain=7 --led-slowdown-gpio=4 -u 65507/8192) everything starts up fine and the device is recognized and pushed to from processing but there is no light. eth0: IP: 169.254.165.35; MAC: dc:a6:32:cd:23:92 Updating pusher from bcast. (Running pixelpusher_tester but have also tried a handful of other examples) |
I tried running Processing on both OS X and on the same unit... It recognizes the pixel pusher device, it sees it-- but nothing displays on the LED...
I have a 64x64 2.5pim LED RGB matrix.. Help?
The text was updated successfully, but these errors were encountered: