Actions
Forum Thread Details
  • Replies 8 replies
  • Subscribers 179 subscribers
  • Views 1400 views
  • Users 0 members are here
Related

Restriction of autorouter?

Former Member

Hi,

 

I'm still pretty new to Eagle. I've made a few PCB's so far, and they've

turned out great, but I hadn't used the autoroute function at all until

now. I need some advice.

 

I've already routed a particular area of the board since it is a

measurement circuitry area. However, now that I want to route all of the

digital signals, is there a way to restrict the autorouter such that it

does not mess with my already routed measurement circuitry?

 

Regards,

Brian

 

Parents

  • The net classes allow you to specify different track sizes and spacings for

    different nets.

    This is used by DRC and the autorouter.

     

     

    "Brian Zuelke" <brian.zuelke@ndcpower.com> wrote in message

    news:hleoki$t9o$1@cheetah.cadsoft.de...

    Olin,

     

    Yes, that's well and good to look in the help, except that I don't find

    the help article on this particularly helpful. What is the purpose of

    specifying net classes? What are they used for?

     

    Regards,

    Brian

     

    On 2/16/2010 11:23 AM, Olin Lathrop wrote:

    Quote:

    I've already routed a particular area of the board since it is a

    measurement circuitry area. However, now that I want to route all of

    the digital signals, is there a way to restrict the autorouter such

    that it

     

    does not mess with my already routed measurement circuitry?

     

    As James already said, the autorouter leaves alone anything already

    routed

    before you run it. You may want to put polygons in tRestrict, bRestrict,

    and vRestrict in specific places to keep the auto router from running new

    tracks thru your analog section.

     

    Quote:

    For all intents and purposes, the circuitry that I've routed is

    perfect, but it wasn't to the autorouter because it looks to end traces

    smack-dab in the middle of SMD pads. Since I've got a mix of packages,

    it added all of these crazy angular traces, which I have to go back and

    delete now. Is there any way to stop the router from doing this?

     

    Yes, don't leave dangling ends. Route your own traces to the middle of

    the

    pads and you won't have a problem. You should have had a bunch of

    airwires

    indicating that Eagle thought the connections weren't complete. If you

    got

    wierd angles, then you must have left the ends fairly far from the pad

    centers. Don't do that. As long as you get them close, the remaining

    route will all be within the pad and not change the resulting copper.

    It's

    really not that hard to do it right though, and that way Eagle knows for

    sure the connection is made.

     

    Quote:

    what do net classes have to do with the autorouter?

     

    HELP CLASS.

     

    Quote:

    Can these be used to route only certain classes of signals?

     

    I don't think so. The point is to tell the autorouter parameters for the

    tracks it creates.

     

     

     

Reply

  • The net classes allow you to specify different track sizes and spacings for

    different nets.

    This is used by DRC and the autorouter.

     

     

    "Brian Zuelke" <brian.zuelke@ndcpower.com> wrote in message

    news:hleoki$t9o$1@cheetah.cadsoft.de...

    Olin,

     

    Yes, that's well and good to look in the help, except that I don't find

    the help article on this particularly helpful. What is the purpose of

    specifying net classes? What are they used for?

     

    Regards,

    Brian

     

    On 2/16/2010 11:23 AM, Olin Lathrop wrote:

    Quote:

    I've already routed a particular area of the board since it is a

    measurement circuitry area. However, now that I want to route all of

    the digital signals, is there a way to restrict the autorouter such

    that it

     

    does not mess with my already routed measurement circuitry?

     

    As James already said, the autorouter leaves alone anything already

    routed

    before you run it. You may want to put polygons in tRestrict, bRestrict,

    and vRestrict in specific places to keep the auto router from running new

    tracks thru your analog section.

     

    Quote:

    For all intents and purposes, the circuitry that I've routed is

    perfect, but it wasn't to the autorouter because it looks to end traces

    smack-dab in the middle of SMD pads. Since I've got a mix of packages,

    it added all of these crazy angular traces, which I have to go back and

    delete now. Is there any way to stop the router from doing this?

     

    Yes, don't leave dangling ends. Route your own traces to the middle of

    the

    pads and you won't have a problem. You should have had a bunch of

    airwires

    indicating that Eagle thought the connections weren't complete. If you

    got

    wierd angles, then you must have left the ends fairly far from the pad

    centers. Don't do that. As long as you get them close, the remaining

    route will all be within the pad and not change the resulting copper.

    It's

    really not that hard to do it right though, and that way Eagle knows for

    sure the connection is made.

     

    Quote:

    what do net classes have to do with the autorouter?

     

    HELP CLASS.

     

    Quote:

    Can these be used to route only certain classes of signals?

     

    I don't think so. The point is to tell the autorouter parameters for the

    tracks it creates.

     

     

     

Children
No Data