I was looking through the SOT footprints and sot343 seems to be the odd one out — its pads aren't symmetric.
If you generate it and check the pad X positions:
sot343: [-1.056, -1.056, 0.55, 0.55] center = -0.253 columns ~1.6mm apart
sot323: [-0.891, -0.891, 0.891] center = 0 (symmetric)
sot363: [-0.84, -0.84, -0.84, 0.84, …] center = 0 (symmetric)
The left column is at -1.056 but the right column only reaches +0.55, so the whole part is shifted off its origin and the two rows of pads end up ~1.6mm apart instead of ~2.1mm. Every other SOT footprint is symmetric about the center, so this one looks wrong — the land pattern wouldn't match a real SC-70-4 part, and the right-hand leads would miss their pads.
It looks like a small typo in getCcwSot343Coords (src/fn/sot343.ts): pins 1 and 2 use x: -p * 1.92, but pins 3 and 4 just use x: p — the * 1.92 is missing on the right side. The hardcoded courtyard outline just above it is shifted to match those off-center pads too.
I'll open a PR.
I was looking through the SOT footprints and
sot343seems to be the odd one out — its pads aren't symmetric.If you generate it and check the pad X positions:
The left column is at -1.056 but the right column only reaches +0.55, so the whole part is shifted off its origin and the two rows of pads end up ~1.6mm apart instead of ~2.1mm. Every other SOT footprint is symmetric about the center, so this one looks wrong — the land pattern wouldn't match a real SC-70-4 part, and the right-hand leads would miss their pads.
It looks like a small typo in
getCcwSot343Coords(src/fn/sot343.ts): pins 1 and 2 usex: -p * 1.92, but pins 3 and 4 just usex: p— the* 1.92is missing on the right side. The hardcoded courtyard outline just above it is shifted to match those off-center pads too.I'll open a PR.