Skip to content

Use unique and IPC package sizes for R, L, and C, Fuse, LED, Inductor

evanshultz requested to merge github/fork/evanshultz/separate-rlc into master

Chip capacitors were using resistor package information when IPC-SM-782 shows distinct resistor and capacitor packages; to fix this some chip package info was modified based on datasheet anlysis was tweaking. Also, the same IPC doc includes unique chip inductor package sizes and they were again using resistor package information. See https://github.com/pointhi/kicad-footprint-generator/issues/420.

The script update is at https://github.com/pointhi/kicad-footprint-generator/pull/438 and you should find the most useful information there and the file diff to assess this.

Related: https://github.com/KiCad/kicad-footprints/pull/3 https://github.com/KiCad/kicad-footprints/pull/469 https://github.com/KiCad/kicad-footprints/issues/711 https://github.com/KiCad/kicad-footprints/pull/712 https://github.com/pointhi/kicad-footprint-generator/issues/420

The only significant changes are on some R, L, and C footprints, but most of the changes are quite close to the existing footprints which had made-up info to suit packages found in datasheets (especially see the 0805 capacitor footprint); this validates that the IPC-SM-782 doc is reasonable and that chip component manufacturers were roughly adhering to it all along. All chip footprints are re-generated here since there are a handful of typos.

Marking as a bug since the library claimed to be IPC-compliant and called out IPC-SM-782 but the footprints didn't actually adhere to those documents.

All contributions to the kicad library must follow the KiCad library convention

Thanks for creating a pull request to contribute to the KiCad libraries! To speed up integration of your PR, please check the following items:

  • Provide a URL to a datasheet for the footprint(s) you are contributing
  • An example screenshot image is very helpful
  • If there are matching symbol or 3D model pull requests, provide link(s) as appropriate
  • Check the output of the Travis automated check scripts - fix any errors as required
  • Give a reason behind any intentional library convention rule violation.

Be patient, we maintainers are volunteers with limited time and need to check your contribution against the datasheet. You can speed up the process by providing all the necessary information (see above). And you can speed up the process even more by providing a dimensioned drawing of your contribution. A tutorial on how to do that is found here: https://forum.kicad.info/t/how-to-check-footprint-correctness/9279 (This is optional!)

Merge request reports