When placing two pads belonging to GND net on the same location, and then asking to fill the copper zone around, I witness an erratic copper filling on the left side of the pad.
Platform: Windows 10 (build 19045), 64-bit edition, 64 bit, Little endian, wxMSW
Build Info:
Date: Apr 27 2024 23:05:17
wxWidgets: 3.2.4 (wchar_t,wx containers)
Boost: 1.83.0
OCC: 7.7.1
Curl: 8.5.0-DEV
ngspice: 42
Compiler: Visual C++ 1936 without C++ ABI
Build settings:
#More info
. I tried to rotate the whole block : the bug remains at the left side of the PCB. When place vertically, the bug remains at the top side
. When slightly moving up the right pad, the width of the strange copper zone at the left is growing. When moving up the pad too much, the bug disappear
I am not exactly sure but I assume those GND pads are part of those connector footprints. I would probably remove a GND pad from one of the two connectors. You can do this easily by:
Hover mouse cursor over one of those footprints.
Press [Ctrl + e] to load the footprint in the footprint editor.
Delete the GND pad.
Close the footprint editor. It will prompt you to save the modified footprint back into the PCB editor.
To do this properly though, you would also have to add some library management (Footprints which are only on the PCB easily get replaced by library footprints, which would result in your changes being undone). The schematic editor will also complain about this missing pad when the PCB gets updated, Fixing that is very much parallel to the PCB, but only with the schematic editor and symbol editor.
Another option is RaptoUK’s suggestion to change the pad properties:
Select the pad.
Press e to edit the pad properties.
On the Connections tab, modify the Pad connection option. Setting this to Solid probably works. Another option is to set this to None, and then draw a track from it yourself to use a track segment as a “thermal spoke”. If you draw this manually, I also recommend to lock this track segment, so it does not get deleted or moved by the interactive router or track cleanup.
Okay I get it thanks you all ! So it is trying to connect the two pads together and it is doing so with a thermal spoke ? and so I can prevent him drom doing so by specifying a solid connection type that is fullfilled since the pads are in contact ?
