KiCad - the KiCad Bridge
Public Made by Adomby adom
Drive your own KiCad from an AI, in the background: open every editor, read the whole board as data (the EDA Bridge Standard board model), stack-up, part heights, netlists, place, route, pour, DRC and exports.
update_pcb_from_schematic (apply) leaves REF** on some footprints
kicad_update_pcb_from_schematic (apply) leaves REF** on footprints whose library reference text is the placeholder
Bridge: KiCad Bridge 1.0.98, KiCad 10.0.4 on Windows. kicad_update_pcb_from_schematic {"filePath": <empty board>, "schematicPath": <sheet>, "apply": true} with KiCad closed.
What happened: all 90 footprints were added with pad nets and (path "/<symbol uuid>") set, but 9 of them kept (property "Reference" "REF**" ...): the parts whose PCM-library footprint is named after the MPN (CR0402-FX-1002GLF, CR0402-FX-1003GLF, CR0402-FX-2200GLF, IN-S63BTR; library PCM_am32-esc-2s6s-molecule). The other 81 got their schematic reference. KiCad's own netlist check then reads them as missing (missing on the board: D1, R15, R16, ...).
Expected: every added footprint's Reference set from its symbol, whatever text the library footprint carries.
Workaround used: set each Reference from the schematic symbol whose uuid matches the footprint's path (no other change); the pin-by-pin netlist comparison then matched 214/214.
1 Reply
Log in to reply.