pcb

DRC errors for precisely minimum distance

Bug #1399656 reported by Joakim Nilsson
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
pcb
Fix Released
Low
Unassigned

Bug Description

I was designing a break out board for a chip, so I needed to use really thin wires. Anyways, I had the minimum wire width (and spacing) set to 5.91 mil while routing my board and everything seemed to work well and I didn't get any DRC errors. Anyways, when I restarted pcb and made a new DRC, I started getting errors claiming that the minimum widths and spacings were violated in several places even though the distances were given in the error equal to the minimum width. An example:

Line width is to thin (5.91 mil)
Process specifications dictate a minimum feature-width that can readily be produced
Required: 5.91 mil

Note here that it states 5.91 mil in both places. The DRC errors went away if I lowered the minimum requirements to 5.90 mil.

Tags: drc
description: updated
Revision history for this message
DJ Delorie (djdelorie) wrote :

Could you upload a sample board that fails? There might be some rounding issues in the mil-nm conversion...

Revision history for this message
Joakim Nilsson (nijoakim) wrote :

Yes, of course. Unfortunately, I cannot reproduce the "Copper areas to close" error, so I'll forward both my entire project which is in the "gaf" folder and also a minimum layout ("pcb-bug") which produces the "Minimumm width" error.

Revision history for this message
Joakim Nilsson (nijoakim) wrote :

Sorry for spamming, but I forgot to add that the footprints used in project ("gaf" folder) is contained in "gaf/pcb-elements/".

Revision history for this message
Joakim Nilsson (nijoakim) wrote :

Also, as a suggestion, I think it would be useful if the actual spacing is printed out even in the case for the "Copper areas to close" errors. (This is done for the "Minimum feature width" errors.)

tags: added: drc
Traumflug (mah-jump-ing)
Changed in geda-project:
importance: Undecided → Medium
Changed in pcb:
milestone: none → pcb-4.2.0
Revision history for this message
Chad Parker (parker-charles) wrote :

This issue is specifically about the size of objects. This has been corrected at some point. There are still issues associated with clearances that are equal, but those are covered under different reports.

Changed in pcb:
importance: Undecided → Low
milestone: pcb-4.2.0 → none
status: New → Fix Released
Changed in geda-project:
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.