tscircuit-autorouter (tscircuit) errors

9 recurring problems engineers report in tscircuit-autorouter (tscircuit), ranked by impact.

#50 by errors trackedECAD

Recurring tscircuit-autorouter (tscircuit) errors, by impact

  1. 1Obstacle filtering used a rotated exclusion zone's unrotated width and height, so the zone was dropped and the router reported solved: true while routing straight through it.ECAD · Agent failure · 1 report82
  2. 2Bus length matching measures only newly routed copper, so it can report skew success while retained fanout copper breaks it, repro A at 19 mm against B at 10 mm against a 0.1 mm limit with zero DRC errors.ECAD · Agent failure · 1 report74
  3. 3Regional DDR repair could clear DRC errors by putting vias in signal pads, even with allowViaInPad set to false. On a real A13 circuit forbidden vias went from 3 to 0 after the fix, with 7 other clearance errors still open. An automated fixer optimizing for "DRC clean" broke a rule the designer had set.ECAD · Agent failure · 1 report74
  4. 4A PCB autorouter lost component-pad targets on one dataset board, so a 1.72 mm QFP connection ran out of search; nearly coincident top and bottom SMT terminals could also collapse into one identity during stitching, and an upstream simplifier measured a 39.56 mm route as 2,248.36 mm and silently polled its failed child.ECAD · Agent failure · 1 report66
  5. 5Joint repair now uses the same 0.2 mm default non-plated-hole clearance as DRC, the same shape as #3422 but smaller. It is part of an 11-PR stack that starts with pinning a dataset to corrected Altium source rules (#3423).ECAD · Agent failure · 1 report66
  6. 6Later routing phases lost geometry and net identity from earlier phases, which caused false open connections, duplicate ground escapes and clearance violations. A 0.005 mm numeric tolerance accepted a 0.0976 mm gap, and a 1e-9 mm placeholder could export as a zero-width Gerber aperture.ECAD · Agent failure · 1 report66
  7. 7One repair stage of the router passed a hardcoded 0.1 mm trace clearance while the board declared 0.45 mm, and the next stage enforced 0.45 mm. Candidates got rejected and pad/trace DRC violations stayed. Two stages of one tool held different clearance rules for the same board.ECAD · Agent failure · 1 report66
  8. 8Passed sample16's reference checks while one via pad stuck about 0.08 mm past the board outline; now the full via footprint has to fit the outline.ECAD · Agent failure · 1 report66
  9. 9tscircuit's autorouter DRC lost copper connections the router depended on, producing 473 false missing-connection errors across five benchmark samples. The router skipped redundant traces between pads already joined by copper, but DRC did not know that copper existed. The false errors also stopped the repair solver from accepting clean candidates, and the fix seeds the continuity graph from the dataset's terminal groups.ECAD · Agent failure · 1 report66

How it fails

  1. Agent failure9

Engineering tools that address these errors

Sourced from public community reports. Costs and delays on individual entries are modeled estimates, not measurements.