openinput-fw / openinput-kicad-library

Kicad symbol and footprint library for input device related components not available in the official libraries

openinput-kicad-library

Kicad symbol and footprint library for input device related components not available in the official libraries.

Available components

Footprints
PXI-DIP-16 (PMW33xx/PAW3399)
Generic Micro switch
Generic Encoder

Symbols
PAW3399DM‐T4QU
PMW3360DM-T2QU
PMW3389DM‐T3QU
Generic Micro switch

Installation

This library is made with Kicad 6.0.0-rc1 and over in mind.

Through PCM (Recomended)

The library should be available in the official KiCad PCM repository, proceed if you wish to install manually or offline.

To Install open Kicad's Plugin and Content Manager (shortcut Ctrl+M) and Install from File... with the packaged library found in releases.

Kicad uses library tables to keep track of installed libraries. As of 6.0.0-rc1 Content Manager DOES NOT automatically update these library tables.

To be able to use this library you will need to add it manually in Manage Symbol Libraries... and Manage Footprint Libraries... in Preferences.

The following entries are needed:

Library	Nickname	Library Path
Symbols	openinput	${KICAD6_3RD_PARTY}/symbols/com_github_openinput-fw_openinput-kicad-library/openinput.kicad_sym
Footprints	openinput	${KICAD6_3RD_PARTY}/footprints/com_github_openinput-fw_openinput-kicad-library/openinput.pretty

Manual

Extract the same ackaged library found in releases to where you want the library stored, and add the relevant entries to the library tables in Manage Symbol Libraries... and Manage Footprint Libraries... in Preferences.

note: the path to the 3d models is fixed, so depending on where you install the library they might not show up by default

License

This library is dual licensed under MIT and CC-BY-4.0.

openinput-kicad-library's Issues

idea: workflow/action to produce a "nightly" library

Just recording the idea, this isn't necessarily useful here as changes will be few and far between but i have other libraries where it might make sense.

Have a workflow automatically pack and upload the library pack somewhere like as an artifact (sadly only lasts up to 90 days, maybe a cron job could fix that), and push to a branch the metadata so it works as package repository for kicad.
The advantage here would be that pushed changes would be immediately available to users, not having to go through a release merged on the official kicad metadata repo (those would still happen eventually)

this is something that can be done with the git directly obviously (though care must be taken because the location is fixed), or even an install scrip in the repo, I just think this makes sense and is convenient

footprint request: Hero sensor

Logitech Hero Hg11 sensor
https://github.com/perigoso/hero-re

Consider adding to Kicad package repository

https://gitlab.com/kicad/addons/metadata

Not sure If we do this now or we wait for a couple more footprints (right we only have 3 or so, so it feels small to be pushing upstream)

Ignore timestamps

Footprints contain a timestamp field, kicad uses this to keep track of modifications, this is not relevant for a versioned library, we want to set it to 0 for cleanness, a check and a pre-commit might be something we want to implement later.

For now this is a regex to find and replace said timestamps.
's/tstamp [a-zA-z0-9-]{36}/tstamp 00000000-0000-0000-0000-000000000000/g;t;d'

Fix encoder footprint

as you thought, the encoder stabilizers(?) are too small
they need to be a bit wider to allow for the hook shape to slide though
an encoder will fit if you straighten the hooks out though
@mriise in #openinput-general > DIY Design discord

footprint request: pixart paw3370 sensor

pixart paw3370 wireless sensor