PSDR (MichaelRColton) errors

3 recurring problems engineers report in PSDR (MichaelRColton), ranked by impact.

#193 by errors trackedECADFirmware

Recurring PSDR (MichaelRColton) errors, by impact

  1. 1Two typoed Ref Des cells in the BOM spreadsheet. R97,-99 reads as R97 and R99, so R98, the red LED series resistor, has no BOM line and an order built from it misses the part. Row 41 lists R6 and R14 again after they got their own rows, so quantities overcount by two. The contributor expanded every Ref Des cell and reconciled it against the PADS .asc part records: 20 board parts had no BOM line before the fix.ECAD · Agent failure · 1 report74
  2. 2An outside reader compared main.c with the 2.6.1 board netlist. Of seven signal paths, three have code, and the two VNA cases are empty even though the bridge, the AD8302 and the switch pins are all routed. A plug-in filter bank is "accounted for in hardware and no code path ever selects it." The maintainer said back in 2021 that most of his code isn't on main. #20 is a duplicate post.ECAD · Agent failure · 1 report66
  3. 3Someone rebuilding the 2.6.1 design in KiCad, with BOM and manufacturing data, did a read-only firmware survey and found an unconditional debug while(1) sitting before the real main loop, plus an I2C wait with no timeout. They asked for the maintainer's view before sending any PR. The board files and the firmware had drifted apart in a way only someone working both sides would notice.Firmware · 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.