-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
can ‘Disconnect airwires from pads’ also act as a split-net command #6
Comments
This rough code works around the Select Copper Connection issue, which is awaiting a fix.
|
.. and the good news, is the bug reported Fixed in revision 9eec296b0a0d9e9ff6a152aa1ef91d7ae92920dc So that last slower code is not strictly needed, unless you want to allow any single segment select, to be enough to seed the selection ? (or want it to work on older KiCads ) With a properly working Select Copper Connection, that code should exit with nothing to do, after 1 x 2 axis pass. |
Request: can ‘Disconnect airwires from pads’ also act as a split-net command, where someone selects N segments of a NET, but not the whole net.
Usually one split keeps the old net name, and a new net name is assigned to now isolated connection set. PADS and Vias touched would have that new net name applied.
One use case, is in manual duplicate of a cell array, where currently that slavish clones all net names where exact clones may not be desired.
Being able to split some routed nets, after clone, would be useful.
eg keep GND +3V, but make some local by removing the rats-connection due to same-net-name.
Code example below collects selected TRACK items, and then collects PADS of that Netname, and tests for PADs touching selected segments. End outcome is a selected set (trk/via/PAD), ready for NET split rename.
Other issue - I've raised a BUG report in KiCad PCB as to work best, this will need a fix made to Select Copper Connection.
https://bugs.launchpad.net/kicad/+bug/1789807
Currently, KiCad menu Select Copper Connection 'travels over' & selects vias in the sub-group, and can travel-over a PAD but fails if entry/exit traces are on different layers.
My thinking here, is Select Copper Connection should work like a multimeter, and via is the same as a pad.
I did find a workaround, which is to manually Shft-Clk select one segment in each PAD fragmented sub-net, and then 'I' will collect all the Select Copper Connections. A little klunky and error prone.
`
The text was updated successfully, but these errors were encountered: