Skip to content
This repository was archived by the owner on Oct 26, 2021. It is now read-only.
This repository was archived by the owner on Oct 26, 2021. It is now read-only.

Document when to use the generic footprint generators vs. when specialized footprints must be made #438

@poeschlr

Description

@poeschlr

We currently require every generic package for which we have an IPC generator to use this in preference over the manufacturer suggested footprint.

There are however exceptions to this. MEMS and RF applications sometimes require an exact layout (MEMS to avoid mechanical stress, RF applications to ensure perfect matching) These specialized footprints are to be placed in the footprint lib meant for this special function.

I would go so far as to require a symbol request for such a specialized footprint to be considered as it is useless otherwise.

Also if the manufacturer names a highly specilized package after a generic package then we might also consider this to be an exception (example if they even list "non JEDEC compliant" in the datasheet)

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions