Re: [Kicad-developers] Differential pair DRC Errors

2017-03-14 Thread Andy Peters
> On Mar 11, 2017, at 12:58 PM, Tomasz Wlostowski > wrote: > > On 13.02.2017 01:59, Andy Peters wrote: >> I route the signals and run the DRC, and for every corner in the trace >> pairs, I get an ErrType(x): “Two Track Ends Too Close” complaint. >> Sometimes it’s

Re: [Kicad-developers] Differential pair DRC Errors

2017-03-14 Thread Joseph Chen
On 03/11/2017 12:58 PM, Tomasz Wlostowski wrote: On 13.02.2017 01:59, Andy Peters wrote: I route the signals and run the DRC, and for every corner in the trace pairs, I get an ErrType(x): “Two Track Ends Too Close” complaint. Sometimes it’s ErrType(16), sometimes it’s ErrType(17), the rest

Re: [Kicad-developers] Differential pair DRC Errors

2017-03-11 Thread Tomasz Wlostowski
On 13.02.2017 01:59, Andy Peters wrote: > I route the signals and run the DRC, and for every corner in the trace > pairs, I get an ErrType(x): “Two Track Ends Too Close” complaint. > Sometimes it’s ErrType(16), sometimes it’s ErrType(17), the rest > ErrType(18), but they are for all corners. See

Re: [Kicad-developers] Differential pair DRC Errors

2017-02-13 Thread Tomasz Wlostowski
On 13.02.2017 17:26, Jon Evans wrote: > I verified using Novak's test case on the Launchpad bug report. DRC > error is generated if the distance between the tracks is exactly equal > to the clearance. > If you increase the spacing by the minimum distance recognized by the > software's precision,

Re: [Kicad-developers] Differential pair DRC Errors

2017-02-13 Thread Jon Evans
I verified using Novak's test case on the Launchpad bug report. DRC error is generated if the distance between the tracks is exactly equal to the clearance. If you increase the spacing by the minimum distance recognized by the software's precision, the DRC passes. So, I think it's an issue of DRC

Re: [Kicad-developers] Differential pair DRC Errors

2017-02-13 Thread Andy Peters
> On Feb 13, 2017, at 2:06 AM, Clemens Koller wrote: > > Hello! > > If the global minimum mandatory clearance/spacing (pitch) of a design (due to > manufacturing limitations) is set (& activated) it should complain when some > other settings are violating that. I purposely

Re: [Kicad-developers] Differential pair DRC Errors

2017-02-13 Thread Clemens Koller
Hello! If the global minimum mandatory clearance/spacing (pitch) of a design (due to manufacturing limitations) is set (& activated) it should complain when some other settings are violating that. It could be assisting if the user gets a clear warning when the differential pair dimensions

Re: [Kicad-developers] Differential pair DRC Errors

2017-02-12 Thread Jon Evans
I took a quick look at the DRC code, and it looks like it is doing an exclusive check on the minimum distances for clearance -- i.e. it is requiring the clearance be greater than the minimum, not greater or equal. I'm not familiar enough with this part of the code to want to submit a patch for

Re: [Kicad-developers] Differential pair DRC Errors

2017-02-12 Thread Andy Peters
> On Feb 12, 2017, at 5:59 PM, Andy Peters wrote: > > I am using a nightly build from 26 January 2017 on a Mac. > > The design has a handful of differential pairs. I have set up design rules > for most nets in the design as 1.6 mm trace width and 1.6 mm clearance. I >