Two max7219 yaml

[pableitordasauto]

Hi @paradajz,
I have a board based on opendeck 2.2
I have modified with two max7219 in cascade. How I must type it in the yaml file.
The pins are connected in same configuration like 1 max only (48leds). Then the "dout" is connected to "din" and the control pins are shared.
With only 48 leds, it works well, but I don't know which number corresponding t9 the other max
Thanks!!!

[paradajz]

What is your current configuration?

[pableitordasauto]

But, which numbers must type?
My instinc says to me to complete with another 48 (total 96). The problem is that I don't know which values.

[paradajz]

As I said, remove it completely.

[pableitordasauto]

Ok...I'll do Sir!!!
Thanks!!!!

[pableitordasauto]

Hi again...
I have checked the firmware...
I think that the problem is in the communication between the rpi and the two max7219.
I didn't mention that I'm using RGB leds. Then, I detect that only pass one led change instead the three states...the second max7219 no follow the selected color.
Where is the file in the source code that manage the max?

[pableitordasauto]

Hi again...

I'm trying with different options...but the daisy chain not working

[pableitordasauto]

Finally, after many tests...I reach a conclusion. The data transmitted is only for the first max. The second max only received the previous data stored in the first max when the first max receives new one. The daisy chain mode no works....

[pableitordasauto]

Hi again @paradajz,
I'm thinking about the issue. In case that the firmware doesn't allow two max in daisy chain mode, Is it possible manage two max in parallel?
And in affirmative case, how we can configure the yaml and indexing the leds?

[paradajz]

I've checked the driver and yes, the driver doesn't actually handle multiple chips, only the first one. I can't test this behaviour so I'm leaving it as is.

[pableitordasauto]

Hi @paradajz, I see...in that case, what do you think if I send to you a pcb with the hardware configuration? I have made a couple of them, and it could be a pleasure send one to you. This feature is very interesting, if the problem is "not to have" the behaviour...I could be a pleasure helping you 😀 Give me your contact to ***@***.*** and I send you one. El dom, 24 nov 2024, 18:07, paradajz ***@***.***> escribió:

…

I've checked the driver and yes, the driver doesn't actually handle multiple chips, only the first one. I can't test this behaviour so I'm leaving it as is. — Reply to this email directly, view it on GitHub <#313 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AUX2XQETSYSJHGQDSIKT3P32CIBW3AVCNFSM6AAAAABRY7GO5WVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCMZWGQYDOMI> . You are receiving this because you authored the thread.Message ID: ***@***.*** com>