Feature request: Add net for NPTH

Currently, the pad number of NPTH is not editable


In a single-layer board, such as aluminum substrate PCB drawing, you need to set up a mounting hole, and it needs to be connected to GND, at this time, the pad number cannot be used, and the net cannot be assigned, so I need to place an SMD+NPTH to implement it, and it will be much more convenient if the pad number can be edited to distribute the net

NPTH does not have a pad number and can not be part of the netlist because it has no copper to connect anything to.

If you want to connect a net to a mounting hole, then use mounting holes with pads, KiCad has both schematic symbols and PCB footprints for those.

NPTH just does not have copper plating in the hole, copper is currently allowed to be added in each layer, you can see the settings in my screenshot, the copper of the F.Cu layer is retained, as for the MountingHole footprint in the library, the single-layer PCB is also composed of two pad stacks of SMD and NPTH like me

That may be a small bug / oversight in KiCad. NPTH does not have copper, so there is no use in setting copper layers for it. I may be wrong, but I guess nobody found it terribly interesting.

In PCB terminology, a Pad Stack has a quite specific meaning. One complete pad stack can have different sized copper areas on different layers and a hole (maybe more), but it’s still a single pad stack. All copper in the pad stack is connected to the same net. (At this moment KiCad does not support a full pad stack yet. (or was this introduced in V9?)

Yes creating a pad (“stack”) from an NPTH and a SMT pad is a (sort of) normal way of doing things in KiCad. KiCad may complain that it can’t reach the center of the SMT pad when you’re connecting a track to it. I’ve looked at a bunch of mounting holes in KiCad’s library and NTPH is only used for mounting holes without copper. All the others use a THT pad for the hole (appended with SMT pads and other stuff).

I would suggest adding a net to NPTH

You may read the following discussions on gitlab: