Large 8 panel (64x32 pixel) display #16
Replies: 7 comments 32 replies
-
|
Hey there, thanks for the question. Unfortunately the quick answer is "I don't know". I am not sure the Adafruit HAT can handle that many displays or how much power each needs. If you make any progress on this such as alternative RGB Matrix HAT that supports this many displays please let me know. A quick check on the Adafruit displays says the 4amps per display is when every pixel is lit - and there are very few display modes on this project that light every pixel. I may need to bite the bullet and order more displays to see how many I can chain together... |
Beta Was this translation helpful? Give feedback.
-
|
@legoguy1000 - What did you do to make this work? I purchased 2 64x64 matrix displays figuring it would just be an edit to the display rows but that doesn't seem to be the case. It seems like it's separated the display vertically into 4 - row groups. @ChuckBuilds - Any ideas? Pi 3, Adafruit Bonnet, 2 64x64 displays
|
Beta Was this translation helpful? Give feedback.
-
|
The 64x64 pannels use a 5 address driver, you'll need to do some soldering to make it work with the bonnet, see https://www.adafruit.com/product/3649?srsltid=AfmBOorovlyUvNH-R3snW3JrNYJ_ESQLA3chgiWWwCHg7yuG11EmduB9 |
Beta Was this translation helpful? Give feedback.
-
|
I'm using 8 of the 64x32 panels which use 4 address drivers that is native to the adafruit bonnet (I'm also using a different IO board but same thing) |
Beta Was this translation helpful? Give feedback.
-
|
You likely need to solder the "e" pin to "8" Depending on which adafruit bonnet you have. My "e" pad was underneath, the one in the picture is the one with the RTC |
Beta Was this translation helpful? Give feedback.
-
|
Thank you both. I found that page and tried a temporary short with wire and tape but after your comments I went ahead with soldered and that fixed it. Everything is looking good now except I am getting a flash on the music (Spotify) screen. It must have to do with the refresh rate because I changed it from 1 to 5 and that reduced the flash on the screen. Any fix for that? I changed it to 30 for now. |
Beta Was this translation helpful? Give feedback.
-
|
@ChuckBuilds I saw a lot of the changes ur made in 2.4. I have a slew of ideas to try and improve the codebase, make it easier to modify, more sustainable, especially by multiple people if you're interested. Cause as I go through the code and the massive merges you're doing to main, it makes it hard to try and contribute. I am a software developer for work so I'm happy to provide best practices and ways that will make this easier. I want to contribute back but currently its very difficult and I'll just end up maintaining my own fork and do my own thing which i don't want to do. |
Beta Was this translation helpful? Give feedback.
-
|
Sure, sorry for the mass changes. I am just trying to get things working
again after the last update broke other managers and displays.
…On Wed, Sep 17, 2025 at 9:48 AM Alex Resnick ***@***.***> wrote:
@ChuckBuilds <https://github.com/ChuckBuilds> I saw a lot of the changes
ur made in 2.4. I have a slew of ideas to try and improve the codebase,
make it easier to modify, more sustainable, especially by multiple people
if you're interested. Cause as I go through the code and the massive merges
you're doing to main, it makes it hard to try and contribute. I am a
software developer for work so I'm happy to provide best practices and ways
that will make this easier. I want to contribute back but currently its
very difficult and I'll just end up maintaining my own fork and do my own
thing which i don't want to do.
—
Reply to this email directly, view it on GitHub
<#16 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AH6H674R4VQTP3VR6HBW3M33TFRBDAVCNFSM6AAAAACFIKLKT6VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTINBSHEZDQOA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
I think I see what happened. After approving your PR's, I didn't add them
to my development branch - so when I went to merge with main they weren't
there. I am still learning git and best practices on all this, I apologize
for any frustration! I think I've got them all added back now, checking
deeper.
On Wed, Sep 17, 2025 at 9:53 AM Charles Mynard ***@***.***>
wrote:
… Sure, sorry for the mass changes. I am just trying to get things working
again after the last update broke other managers and displays.
On Wed, Sep 17, 2025 at 9:48 AM Alex Resnick ***@***.***>
wrote:
> @ChuckBuilds <https://github.com/ChuckBuilds> I saw a lot of the changes
> ur made in 2.4. I have a slew of ideas to try and improve the codebase,
> make it easier to modify, more sustainable, especially by multiple people
> if you're interested. Cause as I go through the code and the massive merges
> you're doing to main, it makes it hard to try and contribute. I am a
> software developer for work so I'm happy to provide best practices and ways
> that will make this easier. I want to contribute back but currently its
> very difficult and I'll just end up maintaining my own fork and do my own
> thing which i don't want to do.
>
> —
> Reply to this email directly, view it on GitHub
> <#16 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AH6H674R4VQTP3VR6HBW3M33TFRBDAVCNFSM6AAAAACFIKLKT6VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTINBSHEZDQOA>
> .
> You are receiving this because you were mentioned.Message ID:
> ***@***.***>
>
|
Beta Was this translation helpful? Give feedback.
-
|
To my point, i have some recommendations on how to help prevent these issues. First, I'd stop using a "dev" branch. Just branch off of main, make ur changes, make a PR and merge into main. That way u have very clear and easy to track method of what changes will get merged into main. |
Beta Was this translation helpful? Give feedback.
-
|
Just like I did for my contributions, when u have a merge request its very easy to see every file/line thats modified AND by doing smaller more frequent changes, its easier to resolve conflicts and fix things or identify breaking things |
Beta Was this translation helpful? Give feedback.
-
I see where you are going with this. However, would it make more sense to branch off of dev, then add it back into dev until it has been tested thoroughly? I've been trying to isolate main from any changes until I know it is working as intended. I am trying to greatly reduce bugs reaching end-users, but have been unsuccessful so far. |
Beta Was this translation helpful? Give feedback.
-
|
so it really depends on what ur "main" branch is. FOr all the projects I work on, the main branch is the development branch and the releases are the deliverable and if i'm supporting patches to released versions, i create long lived "release" branches instead. This model prevents massive dev to main merges and keeps everything clean. |
Beta Was this translation helpful? Give feedback.
-
|
Interesting, I guess it could go either way. I don't think many of the
users of the display have ever used a github project before so I thought
keeping "main" as my best version for a new user to download would keep it
easy for them. I guess if we switched to the release model we would need to
use a :latest tag or something? Open to direction, I just don't know
better. Happy to talk it out on Discord too if these emails get annoying.
Thanks for the help, I really appreciate having a second set of eyes
involved. I hadn't had any merge requests until last week so I haven't
thought about this.
…On Wed, Sep 17, 2025 at 10:39 AM Alex Resnick ***@***.***> wrote:
so it really depends on what ur "main" branch is. FOr all the projects I
work on, the main branch is the development branch and the releases are the
deliverable and if i'm supporting patches to released versions, i create
long lived "release" branches instead. This model prevents massive dev to
main merges and keeps everything clean.
—
Reply to this email directly, view it on GitHub
<#16 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AH6H672PGMNDIWYMCXOSKLL3TFXC5AVCNFSM6AAAAACFIKLKT6VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTINBTGAZTENA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
so when u release, it will auto tag |
Beta Was this translation helpful? Give feedback.
-
|
we can go either way, IF u do want to merge into Dev and then merge dev into main, i still recommend using a PR to merge dev into main AND squash the commits. That way it shows a single commit in main with all the changes, there is still a PR that allows u to review everything that will change from dev to main.... and its a lot cleaner history in main. Then delete dev branch and make a new one off of main to start the process over again and u could call the dev branch |
Beta Was this translation helpful? Give feedback.
-
|
also happy to talk on discord, i'm US central time. The other reason using PRs is value is u can link them to issues, so create issues for everything then make the PR for it and then everyone knows what is being worked and by who.... and then when the PR is merged, it can auto close the issue |
Beta Was this translation helpful? Give feedback.
-
|
That sounds messier. If the latest tag is automatic to the release and not
straight into main, let's do it your way and just PR into Main with a
branch for each effort of changes. I need to get better at smaller chunks.
Trying a rebase now then we should be good to go from here on. Thanks!
…On Wed, Sep 17, 2025 at 10:56 AM Alex Resnick ***@***.***> wrote:
we can go either way, IF u do want to merge into Dev and then merge dev
into main, i still recommend using a PR to merge dev into main AND squash
the commits. That way it shows a single commit in main with all the
changes, there is still a PR that allows u to review everything that will
change from dev to main.... and its a lot cleaner history in main. Then
delete dev branch and make a new one off of main to start the process over
again and u could call the dev branch dev-2.5 then dev-2.6.....
—
Reply to this email directly, view it on GitHub
<#16 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AH6H676HN6NEIYGJQFCKOTT3TFZCVAVCNFSM6AAAAACFIKLKT6VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTINBTGA2TSMI>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
I think I'm tracking hah. Thanks for the walkthrough. Opened a PR with the fix to the NCAAFB Rankings. I can delete Development once it's into main. |
Beta Was this translation helpful? Give feedback.
-
|
Also with PRs, u can have them auto delete the source branch too so u don't even have to think about it. |
Beta Was this translation helpful? Give feedback.
-
|
I must've missed that option. Just when I thought I was getting the hang of git! |
Beta Was this translation helpful? Give feedback.
-
|
:) Just remember, Git and GitHub are not the same. Github is just a git hosting service. So things like PRs are not a function of core git, but are capaabilities by Github, gitlab.... that work on top of Git to provide more features.... so there are a lot of settings in Github that aren't technically part of the actual git but extend it. THings like PRs, branch protection to prevent people for pushing directly to main (or whatever branches u want to protect) without going through a PR..... |
Beta Was this translation helpful? Give feedback.
-
|
and while we're talking, here's a lit of my ideas to try to simplify the code.
Overall the more u can simplify and centralize code, the much easier it is to maintain, update, and change in the future. |
Beta Was this translation helpful? Give feedback.
-
|
Run the command “git pull” on your pi from the LedMatrix folder. I fixed
the flashing Spotify late last night.
…On Sat, Sep 20, 2025 at 3:19 PM sjleto ***@***.***> wrote:
Thank you both. I found that page and tried a temporary short with wire
and tape but after your comments I went ahead with soldered and that fixed
it.
Everything is looking good now except I am getting a flash on the music
(Spotify) screen. It must have to do with the refresh rate because I
changed it from 1 to 5 and that reduced the flash on the screen. Any fix
for that? I changed it to 30 for now.
—
Reply to this email directly, view it on GitHub
<#16 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AH6H67YEOQFTCNGVONIPTJL3TWSFBAVCNFSM6AAAAACFIKLKT6VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTINBWGU2TKNY>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
That fixed it. Thank you! |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I came across this repo and video today and it's exactly what I've been looking for. I want to make a large display, 4x2 panel display and want to make sure I get everything I need. For power at full use I'm looking at over 32Amps at 4 amps per panel but it sounds like ur doing fine with 2 per so that brings me down to 16. I'm thinking to get 2 of the 10A power supplies and split them so 4 panels (2.5A each) per power supply and then only power the pi and bonnet via the USB connector. Do u see any issues with that?? I'm also looking to get a ras pi 4, hopefully that should have enough resources to power all those LEDs. Anything else I should consider to make this work?
Beta Was this translation helpful? Give feedback.
All reactions