AI Flow
Public Made by Adomby adom
Adom's AI Flow: a tool to help the AI follow all of the steps it takes to build a board.
testplan check (netlist mode) adds test points on nets a machine contact already carries
testplan check (netlist mode) adds test points on nets a machine contact already carries
Seen on: adom-aiflow 0.2.40, testplan check --tests tests.json --netlist netlist.json --add, a large-pin ESC molecule (AM32, 2S-6S).
What happened: every measured net got a TP, including the nets that sit on a MachineContactLarge / MachineContactMedium (VBAT, PHA/PHB/PHC, SIG, TLM, NRST) and the kind: "ground" test on GND (the tether's own contact). 21 TPs were added; 8 of them duplicate a contact.
Why it is wrong: skill aiflow-test-plan says "A net that can already be probed on a contact or a corner pin needs no test pad (GND on the contacts and corner pins): leave it out rather than crowd the board", and "ground is the tether's machine contact". Board mode already counts an exposed contact pad as a landing; netlist mode (testplan.rs is_tp) only counts parts whose ref starts with TP or whose text says testpoint.
Suggested fix: in netlist mode, treat a pin of a MachineContact* part (fp/page/mpn contains machinecontact) as a landing (status: "contact"), and do not require a spot for kind: "ground" when a MachineContact on that net exists (or at all, since the tether needs a contact, not a pad). Add a test with a netlist where VBAT is on a MachineContactLarge.
Workaround used: kept the 13 TPs on nets with no contact, removed the 8 duplicates from the netlist; the board-mode check at finish uses the contacts' exposed copper.
1 Reply
Log in to reply.