EAGLE (v5.7) Library Component DRC Errors

vicatcu wrote:

Hi,

 

I made a custom footprint for an SMD connector I'm using. I wanted to

build vias into the footprint for each pad and to connect a trace

from each pad to its via. The reason I want to do this is so that I

don't need to re-do that routing effort in every component that I

place (there are a bunch), and since I know I want to route the

signals from the connector on a buried layer. When I defined the

device that uses the footprint, I simply did not "connect" the SMD

pads and associated the schematic signal pins with the aforementioned

vias.

 

I made the library part without a problem, but now that I'm going to

use it, I am getting lots and lots of DRC errors. These are all

related to Clearance between vias, traces, and SMD pads in the

library component, and Overlap between my vias and pads and the

library traces, without even routing anything. Furthermore, when I

actually do route a signal to one of the vias by way of the SMD pad,

I get Overlap lape errors where my trace runs through the SMD pad to

get to the library connected via. So my question is, how do I define

my library part correctly so as to avoid these fictional DRC errors?

 

Cheers,

Vic

There is an explanation for all the errors.

When making a package there are no VIAs only through hole PADS and SMD pads.

There is no SIGNAL routing/traces only wires that have no logical connection

to nets. They are just foreign copper to the DRC

So all the DRC errors are because of the proximity of another object that is

of a different  signal name.

I feel this could be solved/faked  with a ULP.  This would save you routing

these portions, as you desired. The down side is once routed, if you moved

the connector those traces and vias (real vias) would not move or you would

need to group them all first.

Post a picture of your package to clarify what you are attempting . I may

have some time over the weekend to write such a ULP.

Warren

--

Viewed / responded via the newsgroup at

news.cadsoft.de

Am 20.03.2012 22:22, schrieb vicatcu:

So my question is, how do I define my library part correctly so as to avoid these fictional DRC errors?

With version 5.7, that is impossible.

Version 6 can do that, but I haven't properly tested it yet, since we're

still using 5.12 here. And, like Warren Brayshaw, I also recommend 5.12,

because lots of problems from 5.7 are fixed there (NOT your current

problem, though).

Andreas Weidner

Not an answer to your question but I would recommend upgrading from v5.7 to

the last version 5.12

v5.7 introduced many issues due to some core changes. Checkout the release

notes for the versions to understand the fixes and added functionality added

since your version.

HTH

Warren

--

Viewed / responded via the newsgroup at

news.cadsoft.de