traxide (h3ll5ur7er) errors

3 recurring problems engineers report in traxide (h3ll5ur7er), ranked by impact.

#210 by errors trackedECAD

Recurring traxide (h3ll5ur7er) errors, by impact

  1. 1Adding 'route only these nets' exposed a bug. A net left out, like a GND that a plane joins later, still got copper, because its pads lacked plane joins and the post-route pass took them for walled-off pads. Routing only USB_D_P and USB_D_N on TokenBoard reported 37 connections; with the fix it routes 10, all USB.ECAD · Agent failure · 1 report74
  2. 2The router's own check and KiCad's DRC disagreed twice on one board (a plane join walled off by vias, copper 0.8 um too close to a cutout), and wiring KiCad DRC into CI then found 698 errors from stale GND pour fills the tool had never warned designers to refill.ECAD · Agent failure · 1 report74
  3. 3The router's own checker did not report dangling copper, and only KiCad's DRC found stray escape stubs, including traxide's own dangling stub on Mars-64.ECAD · Agent failure · 1 report66

How it fails

  1. Agent failure3

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