foostan
RGB footprint pin marking is on 4 rather than 1
Standard engineering would have the marking on the footprint on pin 1 -
this works if you are using the build logs, but if you know what you are doing, and go to the data sheets, you end up realising that the geometry just doesn't work. Then you go looking at the build documents, and realise that for some reason convention was thrown out the window, and the pin 1 marking is actually on pin 4 - Vdd
Changing it now is probably not worth the additional headaches, and as I said, the geometry doesn't work, so it's unlikely to fry LEDs, this is more here in case someone else goes looking for an answer.
I have been working in a fork version of this same keyboard and doing the BOM I discovered this. I almost lost my mind when I checked the documentation. I will correct the footprints when I have time and will upload in a personal fork :) this is an amazing keyboard that has a lot of potential.
I have been working in a fork version of this same keyboard and doing the BOM I discovered this. I almost lost my mind when I checked the documentation. I will correct the footprints when I have time and will upload in a personal fork :) this is an amazing keyboard that has a lot of potential.
Disregard this, I realize there are several footprints and the one in this datasheet https://cdn-shop.adafruit.com/product-files/2686/SK6812MINI_REV.01-1-2.pdf so I guess you should be careful when sourcing your components haha :D
That might explain the confusion, though that datasheet is an abomination.
The pin 1 index is visible on the diagram of the LED, yet that pin is labelled pin 3.
This it the problem with knockoffs. An alternative might be to add the notch on the silkscreen, as it appears to be consistent.
On Fri, 16 Oct 2020, 8:23 am Werner, [email protected] wrote:
I have been working in a fork version of this same keyboard and doing the BOM I discovered this. I almost lost my mind when I checked the documentation. I will correct the footprints when I have time and will upload in a personal fork :) this is an amazing keyboard that has a lot of potential.
Disregard this, I realize there are several footprints and the one in this datasheet https://cdn-shop.adafruit.com/product-files/2686/SK6812MINI_REV.01-1-2.pdf https://cdn-shop.adafruit.com/product-files/2686/SK6812MINI_REV.01-1-2.pdf so I guess you should be careful when sourcing your components haha :D
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/foostan/crkbd/issues/58#issuecomment-709598336, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFIRN4KA7DUBNI7CZLMFPTDSK5R6LANCNFSM4PXS4RNA .
No it's not
On Thu, 13 Oct 2022, 8:47 am Agustin Marquez, @.***> wrote:
this is the same as #166 https://github.com/foostan/crkbd/issues/166
— Reply to this email directly, view it on GitHub https://github.com/foostan/crkbd/issues/58#issuecomment-1276770277, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFIRN4OJ7JVWIPOOMCO2Q3DWC4WXRANCNFSM4PXS4RNA . You are receiving this because you authored the thread.Message ID: @.***>
No it's not … On Thu, 13 Oct 2022, 8:47 am Agustin Marquez, @.> wrote: this is the same as #166 <#166> — Reply to this email directly, view it on GitHub <#58 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFIRN4OJ7JVWIPOOMCO2Q3DWC4WXRANCNFSM4PXS4RNA . You are receiving this because you authored the thread.Message ID: @.>
:man_facepalming: you are right... i miss read this somehow... now i just read it again and realized it.. i deleted my comment to avoid having the links between the 2 separated issues
All good. I figured it was something of the sort
On Fri, 14 Oct 2022, 2:10 am Agustin Marquez, @.***> wrote:
No it's not … <#m_-4993367040160581766_> On Thu, 13 Oct 2022, 8:47 am Agustin Marquez, @.> wrote: this is the same as #166 https://github.com/foostan/crkbd/issues/166 <#166 https://github.com/foostan/crkbd/issues/166> — Reply to this email directly, view it on GitHub <#58 (comment) https://github.com/foostan/crkbd/issues/58#issuecomment-1276770277>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFIRN4OJ7JVWIPOOMCO2Q3DWC4WXRANCNFSM4PXS4RNA https://github.com/notifications/unsubscribe-auth/AFIRN4OJ7JVWIPOOMCO2Q3DWC4WXRANCNFSM4PXS4RNA . You are receiving this because you authored the thread.Message ID: @.>
🤦♂️ you are right... i miss read this somehow... now i just read it again and realized it.. i deleted my comment to avoid having the links between the 2 separated issues
— Reply to this email directly, view it on GitHub https://github.com/foostan/crkbd/issues/58#issuecomment-1277774013, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFIRN4IT3OH6DGPE2BO6XGLWDAQ75ANCNFSM4PXS4RNA . You are receiving this because you authored the thread.Message ID: @.***>