zudo-osc-hole-field (Takazudo) errors

3 recurring problems engineers report in zudo-osc-hole-field (Takazudo), ranked by impact.

#216 by errors trackedECAD

Recurring zudo-osc-hole-field (Takazudo) errors, by impact

  1. 1An accepted board had copper UUIDs that each named two different objects: 5 segment UUIDs and 1 via UUID each name two distinct AGND stitching objects. Every UUID-keyed repair or removal list could silently pick one occurrence, so the author built an inventory and a fail-closed check rather than renumbering the released board.ECAD · Agent failure · 1 report66
  2. 2An agent-built PR swaps 439 generic parts for exact manufacturer identities and adds 95 new capacitor MPNs. Values, pins, nets and footprints are unchanged, and every generator and ERC check passes. Still, 8 tests fail because retained studies and reports were tied to the old inputs: a protection study needs engineering reassessment, an audit report is stale, a layout MPN is stale. The PR is on HOLD because the change alters netlist metadata that board receipts depend on. The C0603 land pattern is still open against both Murata and KEMET recommendations.ECAD · Agent failure · 1 report66
  3. 3Five track UUIDs and one via UUID each label two different copper objects, so a UUID-keyed removal could act on the wrong copper.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.