[kicad 4.0.4-stable] inconsistent net assignment for zones and pads
Bug #1642414 reported by
Michal
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
KiCad |
Expired
|
Undecided
|
Unassigned |
Bug Description
When exporting netlist from Eeschema to Pcbnew, when using hierarchical schematic, and user defined net name (label):
- component pads are assigned to the YYY net, where: YYY - label name
- zones are assigned to XXX/YYY net, where: XXX - hierarchical sheet name, YYY - label name
Pcbnew treats these nets as Unconnected.
BZR4022 properly assigned the pads to XXX/YYY net for the same project.
Changed in kicad: | |
status: | New → Incomplete |
To post a comment you must log in.
Well' seems more complicated. and_protection" (underscores instead of spaces), and generated new netlist, the zones and pads are properly connected.
Today I have performed some more experiments.
Project is imported from BZR3025.
Originally my hierarchical sheet used name with spaces ("Power and protection").
I've generated netlist, read the netlist in PCBnew (4.0.4). Pads and zones are assigned to "/Power and protection/PH" NET ("Power and protection" being hierarchical sheet name, PH being local net label).
Pcbnew indicated the zone not connected to the pads.
However, after I've changed the sheet name to "Power_
What is strange, when for the experiment sake I've renamed the sheet back to "Power and protection" (spaces again), and read the updated netlist in Pcbnew, the zones are still properly connected to pads..