hpwit
595 7 pin working
Yes
On Mon, 19 May, 2025, 11:46 pm hpwit, @.***> wrote:
hpwit left a comment (hpwit/I2SClocklessVirtualLedDriver#40) https://github.com/hpwit/I2SClocklessVirtualLedDriver/issues/40#issuecomment-2891906104
Hello are you using the hc245 also ?
— Reply to this email directly, view it on GitHub https://github.com/hpwit/I2SClocklessVirtualLedDriver/issues/40#issuecomment-2891906104, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFONYGS2UH6XTEUAJLWFJ7T27INZPAVCNFSM6AAAAAB5OG37ZSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQOJRHEYDMMJQGQ . You are receiving this because you authored the thread.Message ID: @.***>
inside the .h file #define NUM_VIRT_PINS 7 if i change 7 to 8 its output are white screen
Only the clock and latch should go through the hc245. And every unused input pins of the hc745 should be grounded I can send you a board if you want to
Actually he has not explained clearly. The matter is every 8th port has noise in data , may be data timing is not proper. Every 8th data comes from Qa(pin 15) of 595. I test with 40 data port , total 5 C595 and each 595 gives 8 data. In this case data 8th, 16th, 24th, 32th and 40th gives noise.
Thanks & regards jags
I understand know.
How did you realize the circuit? On a pcb or a breadboard ?
You need to route only the latch and clock signal through the hc245 and not the data signal.
If you realize the circuit on a breadboard you may experience issue because of the wiring.
I built PTH PCB for this. We have 4 LATCH and 4 CLK in HC245 but we need 5 to make 40 port so we connect two 595 to each LATCHH and CLK so that it can support 8 HC595. However removed alternate 595 so that each DATA LATCH should connect to only 1 595, but found same issue. So connecting each DATA & LATCH to two 595 is not creating any loading issue. every thing is working except 8th data port of all 595 (i.e. pin 15).
Previously you had old code of 5 data in each 595 we built that also and that was working with all 5 ports. But unfortunately we lost the old library code and now it is missing from your git.
You are requested to check you code and try to fix it. Also you are requested to provide old 5 port library also.
My code is working fine and even other people use it on a regular basis with board that they've made.
Can you share your pcb design ?
I will look for the old 5:1.
I can also send you a board.
Where did you buy your ics because I know that if not coming from a good provider you can have issues.
Sir I can't share my PCB to this open forum. But I can share it to you personally. Please send you email.
On Fri, 30 May, 2025, 12:47 pm hpwit, @.***> wrote:
hpwit left a comment (hpwit/I2SClocklessVirtualLedDriver#40) https://github.com/hpwit/I2SClocklessVirtualLedDriver/issues/40#issuecomment-2921448230
My code is working fine and even other people use it on a regular basis with board that they've made. Can you share your pcb design ? I will look for the old 5:1. I can also send you a board. Where did you buy your ics because I know that if not coming from a good provider you can have issues.
— Reply to this email directly, view it on GitHub https://github.com/hpwit/I2SClocklessVirtualLedDriver/issues/40#issuecomment-2921448230, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAD5AG2SHLIYFWSJUSZ5IRT3BAAYJAVCNFSM6AAAAAB5OG37ZSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDSMRRGQ2DQMRTGA . You are receiving this because you commented.Message ID: @.***>
Problem solved Original IC (HC245) performs perfect.
Thanks Jags
On Fri, 30 May, 2025, 1:24 pm hpwit, @.***> wrote:
hpwit left a comment (hpwit/I2SClocklessVirtualLedDriver#40) https://github.com/hpwit/I2SClocklessVirtualLedDriver/issues/40#issuecomment-2921527710
Of course i understand. @.***
— Reply to this email directly, view it on GitHub https://github.com/hpwit/I2SClocklessVirtualLedDriver/issues/40#issuecomment-2921527710, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAD5AGYSTZRLNTC2TMBI7S33BAFFHAVCNFSM6AAAAAB5OG37ZSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDSMRRGUZDONZRGA . You are receiving this because you commented.Message ID: @.***>