-
Notifications
You must be signed in to change notification settings - Fork 299
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
SK6812-MINI-E #45
Comments
There should be no need to update the schematic, and it will only give more
places for things to go wrong.
Just create a new footprint, allocate it to the schematic parts and update
the PCB.
I'm happy to do a review and approve it, but as I'm not going to update
mine, I'm not going to do the change myself, if the pinout matches it
shouldn't be too much work to route though.
…On Wed, 3 Mar 2021, 4:35 pm tiadobatima, ***@***.***> wrote:
Hello there... Not sure this is wanted, but I'm starting the work to
update the SofleRGB to use SK6812-MINI-E which seems to be considerably
easier to solder vs the regular SK6812-MINI.
I have updated the schematics to use the MINI-E. I'm not good with Kicad,
so I'll need some more time to update the footprint, but I think this is
ready for early review if you're interested.
I couldn't find an official datasheet only but this is what some vendors
on Aliexpress are publishing:
https://ae01.alicdn.com/kf/H79d59ee537124777a478665921acaa59A.jpg
I have the work on this branch on my fork:
https://github.com/tiadobatima/SofleKeyboard/tree/sk6812-mini-e
And to make your review a bit easier, I created a PR against my fork's
master:
tiadobatima#1 <https://github.com/tiadobatima/SofleKeyboard/pull/1>
Thanks! :)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#45>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFIRN4LMB6NPJZP6QX5QZ7DTBXDDPANCNFSM4YQRR7NQ>
.
|
Yeah... The pinout for the mini-e seems to be different than the mini, and that's the reason I thought the schematics needed to be changed, though I kept pretty much everything as is, apart from the mini-e itself and some minor cosmetic changes. Thank you very much @DaneEvans ! :) |
@tiadobatima Each symbol in schematics has assigned so called "footprint" which defines how the given component will look in the PCB design. Here's a bit more about how to change footprints: https://forum.kicad.info/t/how-can-i-assign-a-footprint-to-a-symbol/8901 |
Thank you for the reply guys! Yeah, I started playing around with the footprints yesterday, and in fact that was another reason I thought the changing the schematics would be the way to go, because unless I'm not looking into this the right way, if the component's pinout is different and we don't change the schematics they would be "documented" wrong in two places (in the symbol schematics and footprint)? What am I missing? I'm sure there's a logic behind it, but I didn't catch it yet :) Anyways, the footprint brings me to a more important question: The current RGB LED is defined in two different footprints:
Between these two footprints, the RGB pads in the copper layer and the cutout squares for the Edge.Cuts/Fab layer have different sizes. Is there a reason they're different because my first impression is that the smaller cutout and bigger pads would work better for the switch as well (lower probability for the LED to fall thru; and bigger pads would give slightly better heat dissipation and area when soldering). Thank you again! This is a top notch open source project! 😃 |
@tiadobatima Just regarding the first bit since I don't have the knowledge to answer the second question.
I think the the detail you might be missing is to fully understand what is the purpose of schematic and what it actually means that the component has a different "pinout". The two LEDs are internally equivalent therefore they require to be connected in the same way - GND, PWR, data in, data out. That's the only point you care about in schematics and this haven't changed. What changes is how are those connections placed in the real world when it comes to the particular instance of hardware (its package). And to capture this we have footprints. For example, you can have a simple resistor: that's always a simple component with 2 connections where orientation doesn't matter. You'll have one symbol in schematics for it, but there is a whole range of packages which vary in size and the way how they are mounted to the PCB. So you have huge amount of footprints you can use when designing your PCB in order to support this variety. But the symbol in schematics is always the same. |
The reason for two completely different footprints is that the underglow
one is a SMD footprint, it has no cutout, so the pads have to go under the
LED to work.
The combined one is for the per key lighting, and has the cutout (although
I'm not sure I found a way to get it into the footprint in KiCad, it may
only be on a mechanical layer).
Any other sizes differences were because I stole footprints that worked
(crkbd I think) rather than doing them myself, especially for the glorious
hack that is putting LEDs on the back side of the board shining through. I
didn't want to do multiple runs to find a working footprint.
The combined footprint was my addition - I didn't want to have to line up
the LED each time, or have different part numbers for the key and
associated LED. I'm hoping it catches on, because apart from the creation
of the footprint, it's much easier to work with.
I need to relink my footprint library (thanks KiCad) and then I should be
able to just do a footprint swap to match the mini-e recommended footprint.
They seem close enough that it should only be a matter of pushing a few
traces if needed.
…On Thu, 4 Mar 2021, 6:48 pm tiadobatima, ***@***.***> wrote:
Thank you for the reply guys! Yeah, I started playing around with the
footprints yesterday, and in fact that was another reason I thought the
changing the schematics would be the way to go, because unless I'm not
looking into this the right way, if the component's pinout is different and
we don't change the schematics they would be "documented" wrong in two
places (in the symbol schematics and footprint)? What am I missing? I'm
sure there's a logic behind it, but I didn't catch it yet :)
But yeah, I agree with "don't change if it works!" :)
Anyways, the footprint brings me to a more important question: The current
RGB LED is defined in two different footprints:
- K6812MINI_underglow_dev (the RGB by itself)
- SK6812MINI_and_cherry (RGB + switch)
Between these two footprints, the RGB pads in the copper layer and the
cutout squares for the Edge.Cuts/Fab layer have different sizes. Is there a
reason they're different because my first impression is that the smaller
cutout and bigger pads would work better for the switch as well (lower
probability for the LED to fall thru; and bigger pads would give slightly
better heat dissipation and area when soldering).
I imagine it's because the the board can be used both sides, but I feel
the smaller footprint would still work on switch and single footprint could
be use for both?
Thank you again! This is a top notch open source project! 😃
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#45 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFIRN4IZKCHNO2LE6AWQHTLTB43LPANCNFSM4YQRR7NQ>
.
|
@tiadobatima I compared the two footprints, and they should be compatible (mini-e in green) It won't be ideal, the pin may overhang the pad a little, but it should work as a drop in. I'll order some LEDs and try it out on one of my spare boards. (in whatever the ali-express lead time is) I'll probably redesign the footprint to take both varieties (not that it really works on the mini anyway), the identical pinout means that there should be no routing required, just a footprint swap |
That's very cool @DaneEvans!! Mini
Mini-e
Since the pins don't match and aren't even symmetric between the mini and mini-e, I'm not really seeing how they could work with the board as is unless these RGBs can work with polarity reversed? What am I missing? 🤔 Anyways, I ordered some mini-e from Aliexpress a few weeks ago and Plcpcb should be shipping my Sofle board today or tomorrow. Might get it here early next week, and can run a test with the mini-e. Will let you know :) |
The crkbd classic, the do-everything symetrical board is apparently no longer the head revision over there, and isn't mini-e compatible, The Cherry version is, and does have a different pinout, (which I think should also be compatible with the rolled pad version of the sk6812, which I have a reel of because of bad suppliers). Sorry for the bad info earlier, I hadn't realised that the crkbd directory layout had changed so much since I built my travel board. I'll do the new footprint tonight (Aussie time) , and talk you through swapping the footprints over, but you'll need to handle the last 5mm or so of routing to each LED. |
Hey @tiadobatima, I've made you a board to start on on my repo (https://github.com/DaneEvans/SofleKeyboard/tree/mini-e) I've made the footprint, placed it on the board, locked the switches and stripped back the nearby tracks, so it should be fairly simple for you to route. Please check the footprint (SK6812MINI-E_and_cherry(mini-pinout) ) - note that the numbers are different - this is because kicad apparently doesn't support pin tables, so the only way to remap it is to change the numbers on the schematic. Because I want to keep the schematics the same, I've chosen to mess up the footprint numbering reletive to the mini-e datasheet. The net names match however. After that you are free to route the new mini-e version of the pcb, |
Very cool @DaneEvans ! Thank you very much! I'll likely be building at least a couple more later, and when I do I plan to use the mini-e. Thank you for all the help! |
Howdy @DaneEvans... Not sure if you have permissions, but would it be possible to push this branch to the |
@tiadobatima he doesn't have permission to merge. This is only an issue, no branches are linked to it. Do you mean the |
@tiadobatima Oh, I actually misunderstood what you mean, like completely :D My bad, just ignore me. Anyway, I merged your PR so just in the case it helps. |
Thanks for merging that PR @josefadamcik ! Thanks! |
o what's the next step?, currently, Sofle RGB pinout is not compatible yet with |
@joecabezas Someone takes the time to route the branch on my fork, at the moment it sounds like noone is in a rush to do it
|
thank you, I am working on my own version, kailh choc compatible |
@DaneEvans bro is SofleKeyboard_mini-E.kicad_pcb ready to be used? |
No |
@DLopezGo90 It's hard to find time, but now that I got my Sofle RGB working, I'll try to set some time aside to get the Mini-e version going. I'll update this thread when I get something worth sharing. |
@tiadobatima Thanks bro, I'll be expectant |
If it helps, I have another Sofle variant (Choc switches) that uses SK6812-MINI-E here: They are pretty easy to solder though I haven't tried the non-MINI-E. |
Howdy folks... Sorry for taking this long, but I thought it would be better to also change the underglow and indicator lights to mini-e as well from @DaneEvans amazing initial work on this, so people have to deal with only one type of RGB. I also found that soldering the regular underglow/indicator minis on the SMD was a LOT more challenging than the drop-in per-key RGBs. Here's the PR #90 . This should be considered a rough draft, since I'm new to Kicad, I haven't printed the PCB yet, and it's been over 20 years since I last worked on a PCB design. I definitely need adult supervision here. |
Just read @josefadamcik's cool post and wanted to mention that I am in the process of building the mini-e variant of the RGB Sofle. Its early days, but the PCB has been manufactured, just waiting on other bits and pieces before putting it all together. Will keep y'all updated. |
@utlandr Thanks, looking forward! Are you using https://github.com/tiadobatima/SofleKeyboard/tree/mini-e ? |
|
Can I use SK6812 Mini-E with the Sofle RGB as it is published in the Github repo? Or a mixture of both Mini-E and Mini for different parts of the keyboard? I've already ordered the PCB and I am now getting the components. Sorry if this has already been talked about and I didn't catch the information. edit: I was able to cancel my order and I will get https://github.com/tiadobatima/SofleKeyboard/tree/mini-e |
Please re-read this thread.
…On Tue, 23 Nov 2021, 3:33 am Benoit Brummer, ***@***.***> wrote:
Can I use SK6812 Mini-E with the Sofle RGB as it is published in the
Github repo? Or a mixture of both Mini-E and Mini? I've already ordered the
PCB and I am now getting the components.
Sorry if this has already been talked about and I didn't catch the
information.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#45 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFIRN4OH7LX66VW4LH3HUCLUNJWENANCNFSM4YQRR7NQ>
.
|
Any updates on your trials @utlandr ? |
Hi @pfn! As of about two weeks ago I have finally received all the pieces to the puzzle. I unfortunately haven't found the time to put it together since then. That said, I hope to at least get the LEDs going this weekend. I am a complete novice when it comes to soldering and electronics so expect to see a picture of magic smoke before pretty lights 👍 |
That's awesome that you got all your parts together @utlandr best of luck in your build! I am settling for a standard sk6812-mini build for now, and maybe will consider mini-e in the future. |
Any news on this? |
Still no news? I am interested in this build. |
Hi @utlandr, Can you share the results of the tests please? I am interested in using this version =) |
@utlandr Thanks!!! |
Hello there... Not sure this is wanted, but I'm starting the work to update the SofleRGB to use
SK6812-MINI-E
which seems to be considerably easier to solder vs the regularSK6812-MINI
.I have updated the schematics to use the
MINI-E
. I'm not good with Kicad, so I'll need some more time to update the footprint, but I think this is ready for early review if you're interested.I couldn't find an official datasheet only but this is what some vendors on Aliexpress are publishing:
https://ae01.alicdn.com/kf/H79d59ee537124777a478665921acaa59A.jpg
I have the work on this branch on my fork:
https://github.com/tiadobatima/SofleKeyboard/tree/sk6812-mini-e
And to make your review a bit easier, I created a PR against my fork's master:
https://github.com/tiadobatima/SofleKeyboard/pull/1
Thanks! :)
The text was updated successfully, but these errors were encountered: