SnipsControllers (thePunderWoman) errors

5 recurring problems engineers report in SnipsControllers (thePunderWoman), ranked by impact.

#103 by errors trackedECAD

Recurring SnipsControllers (thePunderWoman) errors, by impact

  1. 1A firmware bench test showed PWR_HOLD on IO42 is lost on USB reset and during a full USB upload, so the V2 board would cut its own power while flashing, and the pin moves to IO3.ECAD · Agent failure · 1 report74
  2. 2C_3V3 designators had to be renamed because PCBWay read 3V3 as a rating, and PWR_HOLD moves to IO42, which changes firmware, with an order hold until a bench test passes.ECAD · Agent failure · 1 report74
  3. 3Third SnipsControllers PR on the same latch in a few hours: IO3 hold depended on firmware and was tested with no load. PWR_HOLD goes back to RXD0, whose pull-up holds through uploads with no firmware, plus a new 470 nF feedback cap and a 22k pulldown for hysteresis.ECAD · Agent failure · 1 report74
  4. 4Adding an XBee carrier board raised the 3V3 rail from about 36 uF to 47 uF, and a slower-collapsing rail gave a pull-up longer to act at power-off, so worst-case latch margin fell to about 0.03 V. One board change ate the other board margin, and the fix is a 1 uF cap on the same pads, checked by a sim script at the harder case.ECAD · Agent failure · 1 report66
  5. 5Moving V2 board files into a new folder meant updating 80 Stackup Source fields because the CI sync check requires them. To prove nothing else changed, the author checked all 11 gerber layers against production, confirmed the purchasing BOM was byte-identical, and reran DRC, sync, stackup and BOM checks.ECAD · 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.