ai03-2725 / mx_alps_hybrid Goto Github PK

KiCad Library of custom MX-Alps footprints

License: MIT License

footprint mx-alps-hybrid kicad-library cherry-mx alps keyboard mechanical-keyboard

mx_alps_hybrid's Introduction

Deprecation Warning

This library has been succeeded by the MX_V2 Library.
This library will remain available since it is very different structurally from the new one, but will not be updated or maintained.
Please migrate to the new one whenever possible.

MX_Alps_Hybrid

KiCad Libraries of keyboard switch footprints

Included Libraries

MX_Alps_Hybrid.pretty - The original MX/Alps hybrid support footprints.
- FLIPPED - Reversed LED pads for overlapping switch footprints.
- NoLED - No LED pads.
- ReversedStabilizers - Stabilizer mirrored vertically (i.e. for bottom row).
MX_Only.pretty - Only for Cherry MX and derivative clones.
- FLIPPED - Reversed LED pads for overlapping switch footprints.
- NoLED - No LED pads.
- ReversedStabilizers - Stabilizer mirrored vertically (i.e. for bottom row).
- Hotswap - Kailh hotswap sockets of both LED and non-LED variants.
ALPS_Only.pretty - Only for alps SKCM/SKCL, SKBM/SKBL, and clones with same pin structure.
- LED - Specifically for Alps SKCL with in-switch indicators.
Kailh_Choc.pretty - Only for Kailh Choc switches.

Features

Designed from scratch using official datasheets and accurate measurements
Various footprints for all occasions
Almost every switch size in existence
Topside soldermask to prevent solder overflow and improve appearance

Upgrading

The library was overhauled on June 1st, 2019 due to its aging structure and contents.

The schematic components were updated to work on the 50mil grid. You can replace the components; however, it will take a decent amount of work.
- If you wish to do this, remove the old schematic library, re-add the new one, and replace the schematic components.
The footprint library was divided into four distinct libraries. Remove the previous, re-add the libraries with the footprints you are using, then rebind the footprints in the schematic.

Request More Footprints

I'll be more than happy to make more custom footprints to fit your needs, time permitting. I will admit that I'm definitely short on time nowadays, so I may not be able to respond right away.

Contributing

Feel free to create pull requests with more footprints. I only ask that they are of high quality, and that they are based on official dimensions, if possible.

mx_alps_hybrid's People

Stargazers

Watchers

Forkers

hpartanen jmdaly samlli coarse tyetye ropp sidcarter kaylynb vladantrhlik coredump 529systems coquizen aaarsene keyaki-namiki aeberbach jstein91 ludekin3 obra ctrlkismet donutcables ramonimbao giggox 2moons-jp westfoxtrot engee974 bandakkalokka eswai squantor dsanchezseco cerkit pokeimon gummyblumpkins romanchoub kkatano masterzen 2ndstar jaredchesnut perigoso chefdoba arakashic qpockets mkmoses god8565 jsong09 illvsixn gigahawk mattyams jasperamorgan richard-steele-bluefruit mehmetcanbudak p3bis ac90b671 nico-and-steph-studios bogeysparadise arya-sourav gonzagaeagles16 keynes12 park-csu speedypotato mel8dy f3r214 grumiothespoongod mattjoyce fr4nky9000 gavimingram sybutter akariiinmkii fvogeler bishopj7 ruland39 either0r shwilliam q-ata keymystry lil-benq razerban hyphonetics 9n9n7s michaelrlee jcondoriu frooastside bcalow dcpedit desuko-mirai fractalysid shortlurker wastedketchup an-achronism subrezon swampmonster lokurn ateliermizumi kgamerstrong anjew catmunch ashcoding jtotis aussiehossie haobogu robyscar

mx_alps_hybrid's Issues

doesnt have a valid metadata.json file (found solution)

im trying to make a new keyboard but every time i try to install the libary on kicad it says that that the file doesent have a valid metadata.json file edit: i am using kicad 6.0

Use oval holes in the hybrid MX-Alps footprints

Why not use one oval hole for the hybrids instead of two overlaping pads/holes??
With the oval ones you can also get rid of the kicad drc errors about the drilled holes being to close.

I can PR if you will.

It would be something like this

Upstreaming footprints

Hey there. I was wondering if you'd be interested in upstreaming these footprints to KiCAD. I try my hardest to only use KiCAD parts, as it makes it easier to share my projects, and as such would love for these to be upstreamed.

If you need someone to deal with the PR to kicad I can happily help out with that, though I don't really know how I'd go about that.

I think as a first step I'd try and fork your repo and see what work would be needed for it to mostly conform with the KLC, but before I put too much work into it, I'd want to know if you'd be interested in attempting to upstream the footprints? :)

Make use of multi-part symbols

With Eeshema 5.0, you can have different units for a single package. For example, the SW_DPST_x2 footprint in Switch.lib has units A and B.

The resulting symbol in the Assign Footprints window would only show one symbol

We could use this for the existing symbol library so that we could still make use of the footprints with LED pads but have the LED symbols in another schema.

are these files can be used in proteus ares??

Hotswap incorrect courtyard when running DRC

On any of the MX_Only:MXOnly-#U-Hotswap* I'm greeted with a "Footprint has incorrect courtyard (not a closed shape). Since it's just courtyard I don't expect there to be any issues, right? I'm not really too sure what's wrong with the hotswap footprint.