You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 26, 2021. It is now read-only.
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)
The text was updated successfully, but these errors were encountered:
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)
The text was updated successfully, but these errors were encountered: