Are you designing with multi-hundred pin FPGAs? Do you need to highlight all the I/O pins in bank 2 that are in the 3 outermost columns so you can decide which pins should hook to what? PadPainter does that. And more.
Now that looks nifty !
There is still some debate around Pin/group swapping (see other threads) - maybe V6 ?
How hard is it to add a menu subfield for pins/groups to swap ?
I envision you run it once to see whatâs possible, then decide to swap a few.
User enters the pins to swap, in some list form, or even picks from a list ?
In parts like resistor networks, you want group swap - aka paired pinswap.
I got the same error a few days ago. I just pushed a fix to Github.
The WireIt tool is what I use to swap pins, but itâs done on a pin-by-pin basis. Group swapping is harder to envision unless you do it as a strict unit-to-unit swap like with resistor networks.
2 Likes
Wow, now that is brilliant.
Suggestions:
You could add that shift-clk is how to select 2 pads ready for swap.
It seems to swap routed pins just fine too, so the âswap airwires between two padsâ is verbose and not quite accurate.
Maybe hint of âPinswap netnamesâ is shorter and more accurate ?
Playing with it, it says âconnect pads with an airwireâ and icon shows 2 pads.
but itâs actually smarter than that, you can âapply Netname to N Selected Padsâ using this, and if any on those N already has a NetName it applies that.
Iâd suggest change the hint to the more powerful âapply Netname to N selected padsâ
Likewise âdisconnect airwires from padsâ is âremove Netname from N selected padsâ
Airwires / ratsnests auto-follow the net names.
There is no path I can see to edit a netname ? eg if you make a typo, and need to correct
Can that be added ?
Currently it brick-walls on merge of nets, can that enhance to give the choice to use either name ?
(ie allow net merge?) Some CAD flows give the 3rd choice of enter-net name when merging nets.
The ability to edit net name would permit that in 2 steps.
Dump to file give access error if I type a simple name. It seems to not use the PCB directory as default ?
The report file looks like
Part J1: Pad 5 moved from Net (0) to Net fixname (12).
Part J1: Pad 8 moved from Net (0) to Net /NTH (2).
Part J4: Pad 3 moved from Net (0) to Net Net-(J1-Pad3) (3).
Part J4: Pad 6 moved from Net (0) to Net /NTH (2).
Can that add a line for the Design file these changes applied to, and maybe a default swap file name can be suggested, derived from the Design File ? (avoids everyone inventing new namesâŚ)
What does the (12) (2) etc suffix numbers mean ?
Another small enhancement suggestion for the âapply net nameâ feature.
If you select N-Pads and >= 1 NET segment, can it âseedâ the NET name, from that selected segment ?
Currently, if it finds a net name, on any PAD, it applies that. This extends that IQ very slightly, to checking if anything selected has a net name.
Currently, this is pin-focused, but Iâve seen cases where a new footprint was added, or traces imported with NET names, and then a KiCad footprint swapped. Pin+Segment select to attach net names, allows higher zoom levels to be used.
For porting designs from other CAD tools, it is simpler to export traces/nets than fully translate footprints.
These are good ideas. Most of them. I think.
It would probably be helpful to have you add them as issues in Github so they donât get lost in the forum. Iâll work on them as I get the chance.
As for the output to the report file, the nets are denoted using their net name (a string) and net code (an integer) because some nets donât have an actual string name (such as net 0, the net of unconnected pads).
AhâŚok, the location of the number at then end had me fooled a little.
The pcbnew file has this format for net names
(net 0 ââ)
(net 1 âNet-(C1-Pad2)â)
so you could modify your report slightly to become
Part J1: Pad 8 moved from net 0 ââ to net 1 âNet-(C1-Pad2)â
or
Part J1: Pad 8 moved from (net 0 ââ) to (net 1 âNet-(C1-Pad2)â)
The last one exactly matches the KiCad PCB net format, so parsers could work on this.
Will do.
@devbisme and xesscorp coming up with KiCad edge ideasâŚ
Could be interesting, with possible add this specific plugin as the context menu, when we click right on the chip. But I think that KiCad support this plugin behavior.
Iâm not following ? - The Tools.External Plugins is where WireIt shows up, and once enabled, the icons are on the top row.
KiCad does not support right click on an item, to then give a plug-in option.
The right click menu is already quite busy, and WireIt has a Select-N operation approach when using it.
I was thinking that was missing some better user experience like: mouse right clicking to access this tool with the already selected component. But KiCad Pcbnew not allow to add the plugin on the context menu.
Now really testing the on my designs, you did great. I just have a propose of improvement on the GUI, but you will report this on Git.
@devbisme, what do you think about this GUI layout? It fit better in my âsmall displayâ.
I pushed the code on GitHub, but needs to fix the call of class menuSelection( wx.Menu ) that I developed on wxPy4 and have some problem with wxPy3 (used by Pcbnew).
Thanks for the change in the GUI. It looks better. Unfortunately, it doesnât appear to work. I tried for 10 minutes to get it to paint or clear some pads and nothing happened. Iâm using a recent KiCad nightly.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.