fix: keep tssop and sot457 silkscreen clear of the pads (#734) - #736
Open
DPS0340 wants to merge 1 commit into
Open
fix: keep tssop and sot457 silkscreen clear of the pads (#734)#736DPS0340 wants to merge 1 commit into
DPS0340 wants to merge 1 commit into
Conversation
This was referenced Jul 25, 2026
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.
Part of #734 — the two non-quad overlaps found by the same scan. Independent of #735 (different files, no conflict).
Two different causes, same symptom
tssop10_w3mm_p0.5mm— outline 0.025 mm onto the pads. The outline was sized fromparameters.w:but fine-pitch parts place their pads from
wForPads = w - 0.15mm, so the formula describes a body the copper doesn't actually match. The flat- 0.2is also only 0.1 of inset per side — less than the 0.05 stroke half-width plus any clearance. Now both dimensions are derived from the pads that were really placed:shneeded it too: the horizontal runs pass above and below the outermost pads and had the same problem. Both areMath.min/Math.maxagainst the original expressions, so footprints that already cleared the copper keep their existing geometry.sot457_w2_pl1.5_pw0.6— pin 1 marker 0.005 mm onto pad 1. The marker was offset by a multiple of the pad width:pwis the pad's short dimension here while the marker moves along the long axis, so the offset is unrelated to how far the pad actually extends. Withplandpwset independently the triangle lands on the pad. Now it's placed from pad 1's real outer edge:Verification
Segment-to-pad distance minus half the stroke:
0.2 mm matches KiCad's own
TSSOP-10_3x3mm_P0.5mmandSOT-457T, which I measured first — both report exactly 0.2000 mm silk-to-pad.The test bites, and I checked each fix separately rather than trusting one combined run. Reverting only
tssop.tsfails the tssop cases; reverting onlysot457.tsfails with"clears": false. It covers 9 variants and assertspaths.length > 0so it can't pass vacuously.Suite:
468 pass / 0 fail,biome formatclean,bun run buildok. Courtyard parity is unaffected — both parity tests still report IoU 100.00% (diff 0.00%). I rendered the tssop10 parity snapshot against the KiCad reference: the outline now sits clear of the pad columns with the same margin KiCad uses.Remaining from #734:
sod123andsot723emit no silkscreen at all. Happy to send that one next.