MaD (RileyMcCarthy) errors

5 recurring problems engineers report in MaD (RileyMcCarthy), ranked by impact.

#98 by errors trackedECADFirmware

Recurring MaD (RileyMcCarthy) errors, by impact

  1. 1An isolator's drive-side ground sat on an orphan net with no EN_GND label and no link to the pour, so as drawn STEP, DIR and ENA could not drive the servo; ERC showed only 9 pre-existing errors and did not flag the orphan net, and only a software-in-the-loop migration caught it.ECAD · Agent failure · 1 report74
  2. 2On the P2-EVAL USB and on a Prop Plug, the adapter's DTR is wired to the P2's reset, and the OS raises DTR whenever a program opens the port, so every connect, page refresh and auto-reconnect rebooted the test machine and aborted running tests. During reset the pins float, and the bench drive reads a floating ENA as enabled.Firmware · Agent failure · 1 report74
  3. 3The MaD test-machine project re-exported its Edge carrier netlist so the software-in-the-loop sim matches KiCad v0.3. The diff moved the isolator grounds, four Pi link pins and a 5 V to 3.3 V rail, two parts had no simulation model at all, and two encoder pin names are swapped against v0.3.ECAD · Agent failure · 1 report74
  4. 4a KiCad carrier board revision made from SIL hardware findings still carries 55 library footprint mismatch DRC violations and one schematic parity error (a shield pin with no pad) that both revisions share.ECAD · Agent failure · 1 report66
  5. 5MaD firmware HW_pins.h has the servo encoder Z and ZI pins swapped against the v0.3 Edge carrier board, so firmware reads the wrong index channel.Firmware · Agent failure · 1 report66

How it fails

  1. Agent failure5

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