Support pin-indexed SOT-343 pad geometry - #780
Open
Abse2001 wants to merge 8 commits into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
sot343family with compact per-pin geometry parameters:p<number>w,p<number>h,p<number>x, andp<number>ypad<number>width,pad<number>height,pad<number>centerx, andpad<number>centerygrid5x3orp1mmparsingMotivation
C151520 uses standard SOT-343 pin placement with asymmetric geometry on pad 2. A manufacturer-specific family is unnecessary.
The compact
pNw/pNh/pNx/pNyform follows the convention already used byled2835. Full aliases keep generated footprint strings readable. The earlierpadoverrideselector was removed because no existing Footprinter family uses that abstraction.Implementation
The SOT-343 definition declares its valid pins and the four compact properties once:
Those definitions generate both compact and full parameter schemas. A template-literal type exposes the same generated names through the fluent builder, avoiding manually listed
p1w,p2w, etc.Compact C151520 example:
Equivalent full-alias example:
pNxandpNyare absolute pad-center coordinates. Unspecified pin properties retain normal SOT-343 geometry.Validation
bun test: 524 passed, 0 failedbun run build: passed