Hi everyone I have a problem with the DRC in PcbNew. the indicator of how many connections are left gives me a sign that I left 2 pads unconnected. Yet the DRC sees nothing wrong.
I also looked up close on all pads to be sure I didn’t make a mistake.
Does anyone here have the solution for this ?
September 18, 2018, 6:13am
What version of KiCad are you currently using?
ON EDIT: The answer may well depend on the version used.
I’m running KiCad 4.0.7 on windows xp 32 bit.
September 18, 2018, 6:31am
Note: I recommend upgrading to Version 5; but be aware that the upgrade may not be painless.
Changing the Canvas from OGL to Legacy and back to OGL often fixed this issue for me. Depress F9, then F11, to achieve this result.
I’m already downloading V5 thanks for mentioning the maybe upcoming problem
September 18, 2018, 6:40am
The upgrade issues are going to depend upon many variables; it might be fairly easy, or it might really suck.
Still, V5 is, in my opinion, worth the effort to get sorted out and create new designs with.
I will surely try to get it working !
September 18, 2018, 6:44am
KiCad V5 should be stable and work just fine…
There might be issues with the libraries…
I made the libraries local so Kicad does not have to fetch them from Github. Because I’m behind a proxy.
I don’t know if this will affect your statement.
Or does V5 also have different libraries ?
September 18, 2018, 6:57am
V5 no longer uses Git; but the V4 Git are still compatible (i think).
Library Downloads for KiCad 5.0
V5 works awesome I had no problems opening my project and everything is there even the custom libraries.
September 18, 2018, 7:02am
I’m curious if your DRC issue is now fixed?
September 18, 2018, 7:36am
By now I know you have updated to V5.
DRC is independent of Unconnected test.
If you spread all footprints without any track routed, the DRC will find no errors and plenty of unconnected pads.
Sometimes we see the track on the pad and it is connected by copper but not logically connected since the track didn’t reach the center of the pad.
I know Pedro that is why I was looking for unconnected pads by the eye when the DRC did not pick up anything.
September 18, 2018, 10:08am
If you knew how the DRC works, I now understand your question.
It was the status bar showing 2 pads unconnected and not the DRC window!
A known bug in 4.0.7
As you can see, the resistor’s pad (the left one) is not connected anywhere, but it’s actually supposed to connect to the trace on the other layer. However, the status bar (on the bottom) is deceptively saying “Unconnected: 0” (which is something I actually rely on when drawing boards). A DRC check detects the lacking connection, but doesn’t even update the status bar. I’m guessing the status bar has different “unconnected net” checking mechanism than the DRC does (as I had fals…
The status bar unconnected count is not as reliable as the DRC test for unconnected. If it would be calculated the same way then it would take up too much processing power.
That is why this status bar entry has been renamed in v5. (It is now called unrouted instead of unconnected.) The behaviour will still be the same in v5 as it was in v4. In most cases restarting pcb_new will reinitialize the count in the status bar. Resulting in DRC and this count agreeing with each other.
That’s handy to know, thanks
That was indeed my problem
December 17, 2018, 11:02am
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.