I’m running version 6513.
I edited the attached board to adjust the distances among the tracks and change a couple of footprints. At the end of the editing I noticed that the program shows that I have one unconnected net, but if I run drc no unconnected net or pad is pointed out.
What’s the difference among the checks that pcbnew and drc do? This information can help me solve the problem, as up to now I’have been unable to find the error, if any.
From painful experience, it appears that the DRC will assume that overlapping tracks are connected - after all, there will be a conductive path when a board is made, whereas pcbnew counts the nets where the track segments are not properly joined.
Unfortunately, the rats nest for these improperly joined segments is often not visible, even at the greatest zoom level.
@Andy_P. Yes I’m unable too to identify where the problem lays.
@Martin_Layley So, assumed this is the difference (and I guess you’re right, as I had the same feeling), I can simply ignore the pcbnew message and rely only on the drc check result? Any negative consequence?
Did you try OpenGL instead of Default Canvas?
For those borderline cases I found the OpenGL canvas does show ratsnests more reliably than the default one… (BZR6097 on Win7)
I only use the openGL canvas - I’m on OSX and the other two are chronically slow.
I have released designs to manufacture with this discrepancy. I don’t like doing it, but until the DRC check stops ignoring same-net clearances, finding them will continue to be hard.
Yes I mainly use the opengl canvas as it runs smoother, and only switch to the standard canvas when I have problems with grid aligment, as on my monitor the grid is more visible with the standard canvas.
Maybe the mounting hole of the 7805 ground pad ?
1 Like
No, I didn’t touch that. The problem appeared after moving other tracks to have an uniform clearance among them.
If you would could you report it on the bug tracker? Especially if you can attach the board.
GAL has some issues with unconnected nets for some reason, but the dev who did much of the GAL work tends to fix them fairly quickly.
Rely on the DRC… it is correct.