← Back to community index
# contributor·Active

techmannih - Screenshot2026-10-29at10.01.40.png

This is a JLCPCB imported USB C connector. When I download the KiCad Project ZIP from tscircuit.com and run DRC in KiCad, I get hole clearance errors because the clearance between the holes and SMD pads is only 0.1451 mm , while KiCad requires a minimum of 0.20 mm . What should w

Started by techmannihOct 29, 202613 messages

Discussion

Last active 7 days ago · plain text
techmannihoriginal post
This is a JLCPCB-imported USB-C connector. When I download the KiCad Project ZIP from tscircuit.com and run DRC in KiCad, I get hole-clearance errors because the clearance between the holes and SMD pads is only **0.1451 mm**, while KiCad requires a minimum of **0.20 mm**. What should we do in this case?
techmannih
<@757706909351411845> <@809856037376491570>
Rishabh
Check with jlcpcb tolerance, kicad can have different drc min values. We care about the fabricator value
techmannih
i found NPTH-to-track is 0.20 mm, but the hole-to-pad gap is 0.1451 mm, Does the NPTH-to-track requirement also apply to NPTH-to-SMD-pad clearance?
Rishabh
They should be different, check in here https://jlcpcb.com/capabilities/pcb-capabilities
techmannih
yea I checked same, but couldn’t find a separate NPTH-to-SMD-pad clearance value. It lists 0.20 mm for NPTH-to-track and 0.15 mm for SMD pad-to-pad
Seve
drc rules don't really apply within a footprint
Seve
i'm sure kicad can correctly know this if we import properly (?)
Seve
what you need to test is whether or not using the usb without tscircuit being involved, e.g. using a different importer, resolves the issue
Seve
that test is obvious and useless, we already knew that kicad was throwing the warning when converting from tscircuit. You were supposed to test if other tools avoid the issue by forming the kicad footprint/kicad project differently
techmannih
no, that standalone USB-C footprint was taken directly from the KiCad library; it wasn’t imported or exported through tscircuit. That test had no tscircuit involvement. KiCad still reports hole-clearance violations.
techmannih
I also tested an independent USB-C breakout PCB from GitHub, created directly in KiCad without involving tscircuit. KiCad still reports hole-clearance violations

Want to add to the conversation?

Reply in Discord so your notes stay connected to the source.
Continue in Discord ↗