Tracks on the outline layer can cause shorts.
Bug #1492966 reported by
Traumflug
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| gEDA project |
In Progress
|
High
|
Unassigned | ||
| pcb |
Triaged
|
Wishlist
|
Unassigned | ||
Bug Description
Up front: I vaguely remember there was a similar bug, but I can't find it.
The bug is, lines on the outline layer are obviously taken into account when looking up connections. For example with 'Menu -> Connects -> Lookup connection' or with 'Menu -> Connects -> Optimize rats nest'.
Sample attached. There are six lines on the outline layer, four for the old board size and two additional ones for the planned, smaller new board size. Optimizing rats nest brings up some 50 shorts. All shorts vanish when the two lines on the outline layer marking the smaller board size are removed. The outline layer is in its own group.
Revision history for this message
| Traumflug (mah-jump-ing) wrote | #1 |
| Changed in pcb: | |
| importance: | Undecided → High |
Revision history for this message
| Traumflug (mah-jump-ing) wrote | #2 |
Revision history for this message
| Traumflug (mah-jump-ing) wrote | #3 |
| Changed in pcb: | |
| status: | New → In Progress |
| Changed in geda-project: | |
| importance: | Undecided → High |
| status: | New → In Progress |
Revision history for this message
| Bert Timmerman (bert-timmerman) wrote | #4 |
| Changed in pcb: | |
| status: | In Progress → Triaged |
| importance: | High → Wishlist |
| milestone: | none → next-feature-release |
| Changed in pcb: | |
| milestone: | pcb-4.1.0 → pcb-4.1.1 |
| Changed in pcb: | |
| milestone: | pcb-4.1.1 → pcb-4.2.1 |
| Changed in pcb: | |
| milestone: | pcb-4.2.1 → future-bug-fix-release |
To post a comment you must log in.
After some investigation I think I've found the problem: It's true that connects are searched on one layer group, only, but as soon as a track connects to a pin or via, this no longer plays a role. Because pins/vias connect to all layers, no matter which group.
Now, instead of adding more band-aid and making the stuff in find.c aware of layers with specific names, I think it's better to invest into a more general solution. That would be the introduction of layers which are neither copper nor silk.
A few steps in this direction implemented and pushed to branch LP1492966: http://
The stack of layers distinguishes now not only copper and silk, but copper, non-copper and silk layers. Non-copper layers are detected by their name, then moved at the end of non-silk layers, the number of copper layers decremented. No changes in operation other than the rearrangement of the layers, yet.