Solved - Pad report has not connected to Zone, but it is

The pad is connected with only one branch of a thermal relief. In this case that is just fine given the connection is to a low power LED.

If I run a track from pad to the Zone the not-connected goes away.

Another like pad with two branch’s connected is okay.

Try looking at your tracks and pads in outline mode, to check if they are truly connected.

1 Like

outline mode, I’m not sure what to make of this.

does the track have to reach center of pad to make a real connection? or be considered connected. it appears to pierce the center hole

Not electrically because the copper will connect anyway.

But is needed for the logic of the program to read it as connected.

Try also a solid connection of the zone. In the zone properties.

1 Like

I added a very short stub from pad center to track and that resolved the issue.

Can anyone tell me why it would be considered not connected without the stub?

So the rule checking looks for pad center connection. Okay

Thanks

And why not keepint R11 “vertical” as in the former layout? Now that the GND zone is not broken there isn’t any need to move it.

I do not want to reduce the width of the MD0_VIN+ zone. It is a power line reaching 8 amps for short durations.

I re-traced the thin green line with a bright fat color.
image

This line indicates the boundary of the other zone, which apparently has higher priority.
You can draw a track to the center of the GNDD pin, because tracks have higher priority then zones, and zone boundaries are re-calculated around tracks (with the b key).

Tracks do not always have to reach the center of a pad to be recognized as connected by DRC. But if you connect to the center of the pad, then it is always recognized as connected.

I’m not sure where the boundaries are, I usually just connect to the center of pads just to be sure. Drawing nets snaps to pin centers anyway.

2 Likes

When I have designed touch key and placed it at PCB I got many connection lines asking me to connect pads that are connected. And the same for all keys of keyboard. See below:


I reported it as a bug (I don’t know how to find it to add a link).
From the discussion there (I didn’t understand everything) I know that developers know that the connection detecting algorithm should be corrected, but as always there are more important things to be done first.

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.