Skip to content

Add split resistor network symbols

evanshultz requested to merge github/fork/evanshultz/r-split into master

R_Network*_Split units A and B showing the 'dummy' pin on units B and above: image image

R_Pack*_SIP_Split units A and B: image image

R_Pack*_Split: image image

The R_Network* symbols really should have 'SIP' in their name because they are only for pinouts in a SIP package. There are DIP and SOIC and convex/concave packages with bussed resistor networks, but they come in other pinouts. See https://www.bourns.com/docs/Product-Datasheets/4100R.pdf and http://www.vishay.com/docs/31511/31511.pdf and https://www.ctscorp.com/wp-content/uploads/766.pdf for DIP/SOIC, and then https://www.seielect.com/catalog/sei-ravf.pdf and https://industrial.panasonic.com/cdbs/www-data/pdf/AOC0000/AOC0000C12.pdf and https://www.ctscorp.com/wp-content/uploads/74x.pdf for concave/convex packages. This is just to show that while these symbol names don't include the word SIP, they have a SIP FP filter and we would need symbols with different pinouts to cover non-SIP packages.

Note that R_Pack04_Split already existed, which oddly was the only one, and it changes notably just in having a RN ref des prefix like all other resistor networks and now has pin numbers visible.

I didn't do the US resistor shapes but by the time I finished pasting these sections into the huge Device.lib file it probably would have been easier...

Script PR: https://github.com/KiCad/kicad-library-utils/pull/325

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 symbol(s) you are contributing
  • An example screenshot image is very helpful
  • Ensure that the associated footprints match the official footprint library
    • A new fitting footprint must be submitted if the library does not yet contain one.
  • If there are matching footprint PRs, 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.

Merge request reports