fix: make the sot343 footprint symmetric#668
Conversation
|
Heads-up on the red The sot343 tests themselves pass. Once the parity comparison can read the reference again I'll regenerate the two kicad-parity sot343 snapshots — the fix should line up with the KiCad SOT-343 reference more closely (its courtyard is symmetric at ±1.45, which is exactly what this change is about). |
cbefafd to
f490bd4
Compare
|
Reworked this against the now-restored parity test. The original version made the pads symmetric but at the wrong position ( |
sot343 placed pins 1/2 at -p*1.92 and pins 3/4 at just p, so the pads were lopsided. Beyond the asymmetry, p*1.92 (= +-1.056) didn't match a real SOT-343 either: the KiCad SC-70-4 reference has its pads at +-0.825 (= p*1.5) and a +-1.45 courtyard. Use p*1.5 for all four pads and match the courtyard to KiCad -- the parity courtyard diff is now 0%. Regenerated the sot343 snapshots (including kicad-parity). Co-authored-by: abdalrouf-AAA <236259618+technologyet31-create@users.noreply.github.com>
f490bd4 to
4c01c88
Compare
sot343was the only SOT footprint with lopsided pads. Pins 1 and 2 are placed atx = -p * 1.92, but pins 3 and 4 were placed at justx = p, so the right column sat much closer to the center than the left:So the part was off-center and the spacing didn't match a real SC-70-4. I gave the right column the same
* 1.92spacing as the left so the four pads mirror each other.One catch: the courtyard outline was hardcoded to the old off-center pads (it ran from
-1.703to+1.197), so once the right pad moved outward it would have stuck outside the courtyard. I mirrored the right side of the outline too, so it stays symmetric and still wraps the pads. The silkscreen already centers itself off the pad bounds, so that fixed itself.Regenerated the two sot343 snapshots.
Closes #667