zaptrace (oaslananka) errors

11 recurring problems engineers report in zaptrace (oaslananka), ranked by impact.

#42 by errors trackedECAD

Recurring zaptrace (oaslananka) errors, by impact

  1. 1A KiCad importer checked against KiCad's own netlists matches 0 of 64 net names on one real board. zaptrace added a gate comparing its imported graph with 'kicad-cli sch export netlist' output: SparkFun Qwiic Navigation has 32 native nets and 47 imported with 11 exact shared names and 5 pin mismatches, while Mitayi Pico D1 has 64 native and 95 imported with 0 exact shared names. Both are marked BLOCKED.ECAD · Agent failure · 1 report74
  2. 2A KiCad schematic importer silently merged USB_D+ and USB_D- into one net. zaptrace normalized net names into internal keys, and both became 'usb_d_'. On a real reference board (Mitayi Pico D1) the import came out with 94 nets instead of 95, and the quality score read 1.0106 on a scale that tops out at 1.ECAD · Agent failure · 1 report74
  3. 3A KiCad review tool adds a step that writes an assistant request bound to one selected DRC finding, the exact PCB hashes and the review state, because copying a free-form chat prompt loses the selected rule, exact PCB state and non-approval boundaries. Reviewers previously saw only DRC counts and could not tell which rule fired.ECAD · Agent failure · 1 report66
  4. 4After last hour's net fix, the importer still exposed empty pin lists on a real ESP32-S3 board, even for the MCU. An AI design agent could see 47 nets but could not ask which pin is EN, what type it is, or which net it sits on. The PR fills 128 pin records from KiCad's embedded symbol definitions and links each one to an existing net. That is the third zaptrace PR tonight on the same board.ECAD · Agent failure · 1 report66
  5. 5Importing a real ESP32-S3 dev board schematic silently dropped 3 LED anode nets that KiCad's own netlist had: 44 nets and 126 pin nodes vs KiCad's 47 and 132. KiCad allows two parts' pins to touch at the same point with no wire, and the importer only indexed wire endpoints. The tool's own verdict across its 20-board corpus is still 0 verified, 16 blocked, 4 not run.ECAD · Agent failure · 1 report66
  6. 6Last hour's #171 gave agents real pin-to-net links from a bare .kicad_sch. Importing the matching .kicad_pro broke them again without any error. The project importer prefixed net keys by sheet but left the pin and net IDs unprefixed. On real boards that was 128 broken pin-to-net references (ESP32-S3), 99 (SparkFun Qwiic Navigation) and 229 (Mitayi Pico D1). Fourth zaptrace PR on this tonight.ECAD · Agent failure · 1 report66
  7. 7More netlist-parity work against KiCad 10.0.8. This one makes the importer match KiCad's handling of intentionally unconnected pins (6 on a SparkFun board, 3 on a Mitayi board) and keep power and ERC flag symbols out of the physical pin list. It fails closed when a no-connect marker is ambiguous rather than inventing a net. Fifth zaptrace PR today chasing the same goal, a netlist that matches what KiCad itself exports.ECAD · Agent failure · 1 report66
  8. 8Picking a schematic finding left an unrelated PCB object highlighted, and the handoff to the assistant dropped the schematic source/proposed hashes and the ERC details. The author's words: a reviewer who copied that text could lose the evidence identity needed for correct subsequent engineering analysis.ECAD · Agent failure · 1 report66
  9. 9Real KiCad 10.0.8 netlists from two reference boards showed two silent connection losses in the importer. A pin at 169.54500000000002 and a wire end at 169.545 rounded to different grid points, which dropped connected USB, GPIO and GND pins, and labels placed mid-wire (legal in KiCad) were not attached, which split QSPI_SS into separate nets. Measured against KiCad's own netlist, both boards now match (26 of 26 and 61 of 61), and 20 missing pin identities on Mitayi dropped to 3 intended NC pins.ECAD · Agent failure · 1 report66
  10. 10The KiCad schematic importer read power symbol pins but did not join separate copies of the same power symbol, so GND, +3V3 and VBUS split into unrelated made-up nets. Measured against KiCad 10.0.8's own netlist on real projects, SparkFun Qwiic Navigation went from 24 of 26 matching pin groups to 26 of 26, and Mitayi Pico from 51 of 56 to 55 of 56. Still 64 native nets vs 62 imported, and the author says so.ECAD · Agent failure · 1 report66
  11. 11The same importer got pin membership wrong on rotated and mirrored symbols. Embedded-library pin rotation used the wrong sign and instance mirrors were not applied at all. After the fix, Qwiic Navigation matches 11 of 11 shared names (was 6 of 11) and Mitayi Pico goes from 21 of 36 to 51 of 56 partitions.ECAD · Agent failure · 1 report66

How it fails

  1. Agent failure11

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