Thanks for your reply, but the track to the left isn't the problem. PCBNew specifically mentions the proximity between the two pads as being the problem, not the pad-to-track separation. Moreover, if I delete the adjacent track (which is not connected to either pad), the through-hole pad still fails the DRC. This track shouldn't cause a DRC failure anyway, as the separation is greater than the 0.3mm minimum I have specified. The failure is also not caused by the green track connected to the through-hole pad, BTW.
I should have added that I tried slowly reducing the Y dimension of the through-hole pad, and found that it passed the DRC when the separation exceeded twice the minimum track spacing. That suggests there is a logic to this, but I don't know what that might be :). Regards, Robert. Andy Eskelson wrote: > Your attachment ended up inthe attachments folder and a link was > generated to the message. > > Have a very close look at the track to the left of the pad with the > error arrow. It is very close to the pad clearance line,and it may be a > little too close. > > As a test make that pad smaller and or reduce it's clearance zone and > see if that clears the problem. > > Andy > > > > On Fri, 04 Sep 2009 12:09:11 +0100 > Robert <[email protected]> wrote: > >> I have the minimum track spacing set to 0.3mm. After a DRC check on my >> board design PCBNew does not mark surface mount pads that are more than >> 0.3mm apart (as expected), but it does mark a through-hole pad that is >> 0.6mm away from a surface mount pad, complaining that the pads are too >> close. Why is this? >> >> I'm not sure if attachments work, but if they do I've provided one and >> made it as small as possible. Note that the DRC lines on the two >> adjacent surface mount pads (which pass the DRC) intersect but do not >> intersect the pads themselves, but the through-hole pad fails the DRC >> even though its DRC line only just touches the DRC line of the surface >> mount pad above it. >> >> Regards, >> >> Robert. >> >> >> >> >> >> ------------------------------------ >> >> Please read the Kicad FAQ in the group files section before posting your >> question. >> Please post your bug reports here. They will be picked up by the creator of >> Kicad. >> Please visit http://www.kicadlib.org for details of how to contribute your >> symbols/modules to the kicad library. >> For building Kicad from source and other development questions visit the >> kicad-devel group at http://groups.yahoo.com/group/kicad-develYahoo! Groups >> Links >> >> >> > > > ------------------------------------ > > Please read the Kicad FAQ in the group files section before posting your > question. > Please post your bug reports here. They will be picked up by the creator of > Kicad. > Please visit http://www.kicadlib.org for details of how to contribute your > symbols/modules to the kicad library. > For building Kicad from source and other development questions visit the > kicad-devel group at http://groups.yahoo.com/group/kicad-develYahoo! Groups > Links > > > > > ------------------------------------------------------------------------ > > > No virus found in this incoming message. > Checked by AVG - www.avg.com > Version: 8.5.409 / Virus Database: 270.13.76/2345 - Release Date: 09/04/09 > 05:51:00 >
No virus found in this outgoing message. Checked by AVG - www.avg.com Version: 8.5.409 / Virus Database: 270.13.76/2345 - Release Date: 09/04/09 05:51:00
