reda (openreda) errors

3 recurring problems engineers report in reda (openreda), ranked by impact.

#195 by errors trackedECAD

Recurring reda (openreda) errors, by impact

  1. 1Writing the product spec for a new EDA tool, the author found four places where earlier decisions disagree, including auto net names written as Net-R1-1 in one issue and Net-(R1-1) in another. The bigger gap is where the BOM reads part data: the PCB's footprint copies hold only designator, value, footprint and pad nets, while the BOM needs LCSC, MPN and Not Fitted, which live on the schematic, and mechanical parts that exist only on the PCB have no home either way.ECAD · Agent failure · 1 report74
  2. 2Free text and graphics on a copper layer are written to the Gerbers but aren't in the copper index, so DRC never checks them and zones don't clear around them. "Copper text can therefore short a Net without DRC noticing." Found in the v0.1 review.ECAD · Agent failure · 1 report66
  3. 3KiCad paste-only pads became copper on import, mask and paste opening expansion used fixed constants, and Gerber, drill and CPL could use different origins. The fix makes one resolver feed Gerbers, DRC and silkscreen clearing, with one Output Origin for every file.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.