Skip to content

Add OnSemi QRE1113 and Everlight ITR1201SR10AR

Sávio Carlos Martins Costa requested to merge github/fork/saviocmc/Sensor_Proximity_lib_fix_2623 into master

Add footprints for OnSemi QRE1113 and Everlight ITR1201SR10AR

This footprints are required to fix the issues in the Sensor_Proximity library described here: https://github.com/KiCad/kicad-symbols/issues/2623

Datasheets: https://www.onsemi.com/pub/Collateral/QRE1113-D.PDF https://www.everlight.com/file/ProductFile/ITR1201SR10AR-TR.pdf

Issue summary

Both OnSemi and Everlight provide very similar (identical) proximity reflective sensors. Both provide the sensors as SMD or THT devices. The main difference is in the way each chose to assign the pin numbers. Before the changes I intent to introduce, the SMD footprint was using one numbering format and the THT was using another, causing an internal inconsistency, as they were used by symbols aliases inside the library. So by adding the two footprints I present, each symbol will use a particular footprint, without the need for aliases avoiding inconsistencies with each manufacture datasheets. The issue provides more details about the problem and the intended solution.

⚠ Deprecation warning

On Oct 1, 2020 this repository, including issues and pull requests, will be archived and transferred to gitlab.com. In order for your pull requests and issues to be imported into GitLab you must set your email address on GitHub to public and use the same address for your GitLab account. Or login to GitLab at least once using the GitHub icon. Otherwise the importer can't correlate the account information and the issues/comments on GitLab will be owned by kicad-bot (importer documentation).

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