<connector standard="usb_c" /> default part fails its own cutout clearance check, so autorouting is skipped for the whole board

Open
#5,103 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@Shokun123 is already working on this.

Since Nov 3, 2026.

  • #5105 by @Shokun123 — open
  • #5195 by @Crodify — open
  • #5261 by @jeffrey-graham — closed without merging

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
react, typescript
Domain
devtools

Research direction

Reproduce with the TSX snippet via tsci build, which should report two placement errors on USBC.pin15 and USBC.pin26. Start from how <connector standard="usb_c" /> picks its default JLCPCB part (C2765186), and from the placement clearance check that runs before Board._runLocalAutorouting. Done means the default part passes the built-in checks, so the trace from USBC.CC1 to R1.pin1 gets routed without placementDrcChecksDisabled.

Written by the indexing model from the issue text.

Description

Summary

With no part pinned, <connector standard="usb_c" /> resolves to JLCPCB C2765186. That footprint's pads pin15 and pin26 sit 0.171mm from the footprint's own cutouts, below the 0.200mm placement rule. The two pcb_placement_errors make autorouting skip the entire board, so a board with the default USB-C connector ends up with no traces at all, even when the connector is placed with plenty of free space.

Reproduction

export default () => (
  <board width="30mm" height="20mm">
    <connector name="USBC" standard="usb_c" />
    <resistor name="R1" resistance="5.1k" footprint="0402" pcbX={10} />
    <trace from="USBC.CC1" to="R1.pin1" />
  </board>
)

tsci build output:

Copper for USBC.pin15 violates clearance to cutout unnamed cutout (measured 0.171mm, required 0.200mm)
Copper for USBC.pin26 violates clearance to cutout unnamed cutout (measured 0.171mm, required 0.200mm)
Autorouting was skipped because 2 PCB placement errors were found. Fix the placement errors or set placementDrcChecksDisabled to true to route anyway.
Trace [USBC.CC1 to R1.pin1] is not connected (it has no PCB trace)

Resulting circuit JSON: 0 pcb_trace. The source component has supplier_part_numbers: { jlcpcb: ["C2765186", "C456012", "C393939"] }.

Expected

The default part for a built-in standard passes the built-in placement checks, so a board using <connector standard="usb_c" /> routes without extra configuration.

Workarounds confirmed

  • Pin a different part: supplierPartNumbers={{ jlcpcb: ["C165948"] }} reports no placement errors and routes (1 trace).
  • placementDrcChecksDisabled on <board> lets routing run, at the cost of disabling all placement checks.

Possibly related

In tsci dev, a board with the default USB-C connector did not draw the connector, and the console repeatedly logged:

Async effect error in PcbTraceRender "autorouting":
TypeError: Cannot read properties of undefined (reading 'x')
    at getSimpleRouteJsonFromCircuitJson
    at Board._runLocalAutorouting

That was on a larger board, and I haven't reduced it to a minimal case.

Environment

  • tscircuit 0.0.3062 (latest on npm at time of writing), @tscircuit/core 0.0.2259
  • Bun 1.4.4, Node 26.9.0
  • macOS 26.6.2 (Apple Silicon)
Dominant language
TypeScript
Stars
61
Forks
256
Avg merge
20h 21m
Merged PRs (30d)
289

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from tscircuit/core

All issues in tscircuit/core

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.