Generalizing the component library

[obra]

Poking around, I haven't found a general cherry keyswitch library for KiCAD other than this one.

I've been working on generalizing the component library you use in the tutorial, with an eye to making it available to GH/DT/everybody under a liberal license.

So far, I've been playing with:

• making the switch footprints reversible so they can be used for keyboards like the ergodox
• making variants of the switch footprints with builtin pin placement for diodes (through-hole, SMD and in-switch) - This also means that designers could build 'simpler' schematics with half the component and wire count.
• making variants of the switch footprints with 18mm keycap outlines

Does this all just sound like a bad idea?

Am I missing a better general keyswitch component library?

Should I be using some other keyboard as a starting point?

Is it worth me submitting these as a pull request to footprints or would it be better to create a standalone github repo?

Thanks!

[BathroomEpiphanies]

Hi,

I'm not sure but I think anything released on github automatically receives some kind of open license. Feel free to use my cherry library anyway you want.

I think there may be several versions of Cherry libraries around. There is a CAD-resources thread on GH which may contain something, I'm not really sure.

My needs from the footprints have been varying from time to time. Built in diode pads usually ends up interfering with something else at least in a few places. On the other hand they guarantee the diode footprints end up in the correct locations. Having built in diodes also requires a 4-pin schematic symbol. Then when you realize you need to put a diode externally somewhere you need to go back and change the schematic.

Having different footprints for different widths with drawings showing the actual size helps against screwing placements up. Which I think is good for the tutorial.

If you want to extend the library with footprints for built in diodes that is fine. I think my latest take on the matter is to have as few footprints as possible. I tend to only have one without any drawing elements, only a box to show the switch size itself to avoid placing stuff on top of each other. I also use separate footprints for the stabilizers, sometimes I want to modify them or something and end up with yet another specialized footprint. That soon gets out of hand =)

I think the needs varies and that you should always make your own footprints anyway. That's just good practice, never blindly trust someone else's work...

/Fredrik

On Wed, Dec 25, 2013 at 8:47 PM, Jesse Vincent notifications@github.comwrote:

Poking around, I haven't found a general cherry keyswitch library for KiCAD other than this one.

I've been working on generalizing the component library you use in the tutorial, with an eye to making it available to GH/DT/everybody under a liberal license.

So far, I've been playing with:

• making the switch footprints reversible so they can be used for keyboards like the ergodox
• making variants of the switch footprints with builtin pin placement for diodes (through-hole, SMD and in-switch) - This also means that designers could build 'simpler' schematics with half the component and wire count.
• making variants of the switch footprints with 18mm keycap outlines

Does this all just sound like a bad idea?

Am I missing a better general keyswitch component library?

Should I be using some other keyboard as a starting point?

Is it worth me submitting these as a pull request to footprints or would it be better to create a standalone github repo?

Thanks!

— Reply to this email directly or view it on GitHubhttps://github.com/BathroomEpiphanies/KiCAD-Keyboard-Tutorial/issues/1 .

[obra]

Hiya,

Hi,

I'm not sure but I think anything released on github automatically receives some kind of open license. Feel free to use my cherry library anyway you want.

While much of the internet treats it that way, it's...not actually legally 'correct'. Thanks for clarifying :)

I think there may be several versions of Cherry libraries around. There is a CAD-resources thread on GH which may contain something, I'm not really sure.

nod When I last looked, there wasn't , but I'll redig.

My needs from the footprints have been varying from time to time. Built in diode pads usually ends up interfering with something else at least in a few places. On the other hand they guarantee the diode footprints end up in the correct locations. Having built in diodes also requires a 4-pin schematic symbol. Then when you realize you need to put a diode externally somewhere you need to go back and change the schematic.

Understood.

Having different footprints for different widths with drawings showing the actual size helps against screwing placements up. Which I think is good for the tutorial.

I've been finding them useful when designing new keyboards. Thanks!

If you want to extend the library with footprints for built in diodes that is fine. I think my latest take on the matter is to have as few footprints as possible. I tend to only have one without any drawing elements, only a box to show the switch size itself to avoid placing stuff on top of each other. I also use separate footprints for the stabilizers, sometimes I want to modify them or something and end up with yet another specialized footprint. That soon gets out of hand =)

I'm definitely still a newbies at this. I appreciate the advice.

I think the needs varies and that you should always make your own footprints anyway. That's just good practice, never blindly trust someone else's work...

Well, hopefully, with well-audited components, it'll be easier for folks. I'm a big believer in software libraries and haven't yet found the reasons why this stuff is any different.

Best, Jesse

[technomancy]

I would also really like to see a license on this. I haven't found any other component libraries for Cherry MX switches that work, and I can't legally use this without a license. Would you consider a CC0 license? https://creativecommons.org/choose/zero/

[kejadlen]

@technomancy What did you wind up doing for the Atreus? Did the footprints for the switches in the Ergodox PCB not work either? (I'm using those, so would like to know if they aren't feasible for some reason.) The Ergodox is GPL'ed, although I'm not sure if that works for you or not. Kind of a moot point now, I guess!

[technomancy]

Yeah, I ended up using the Ergodox footprint. The Atreus is GPLed, so it's a perfect fit. However, I haven't yet tested it for Alps compatibility. I hope to do so in a month or two.

[kejadlen]

@technomancy Whew, thanks - I'm glad to hear that.