element14 Community
element14 Community
    Register Log In
  • Site
  • Search
  • Log In Register
  • Community Hub
    Community Hub
    • What's New on element14
    • Feedback and Support
    • Benefits of Membership
    • Personal Blogs
    • Members Area
    • Achievement Levels
  • Learn
    Learn
    • Ask an Expert
    • eBooks
    • element14 presents
    • Learning Center
    • Tech Spotlight
    • STEM Academy
    • Webinars, Training and Events
    • Learning Groups
  • Technologies
    Technologies
    • 3D Printing
    • FPGA
    • Industrial Automation
    • Internet of Things
    • Power & Energy
    • Sensors
    • Technology Groups
  • Challenges & Projects
    Challenges & Projects
    • Design Challenges
    • element14 presents Projects
    • Project14
    • Arduino Projects
    • Raspberry Pi Projects
    • Project Groups
  • Products
    Products
    • Arduino
    • Avnet & Tria Boards Community
    • Dev Tools
    • Manufacturers
    • Multicomp Pro
    • Product Groups
    • Raspberry Pi
    • RoadTests & Reviews
  • About Us
  • Store
    Store
    • Visit Your Store
    • Choose another store...
      • Europe
      •  Austria (German)
      •  Belgium (Dutch, French)
      •  Bulgaria (Bulgarian)
      •  Czech Republic (Czech)
      •  Denmark (Danish)
      •  Estonia (Estonian)
      •  Finland (Finnish)
      •  France (French)
      •  Germany (German)
      •  Hungary (Hungarian)
      •  Ireland
      •  Israel
      •  Italy (Italian)
      •  Latvia (Latvian)
      •  
      •  Lithuania (Lithuanian)
      •  Netherlands (Dutch)
      •  Norway (Norwegian)
      •  Poland (Polish)
      •  Portugal (Portuguese)
      •  Romania (Romanian)
      •  Russia (Russian)
      •  Slovakia (Slovak)
      •  Slovenia (Slovenian)
      •  Spain (Spanish)
      •  Sweden (Swedish)
      •  Switzerland(German, French)
      •  Turkey (Turkish)
      •  United Kingdom
      • Asia Pacific
      •  Australia
      •  China
      •  Hong Kong
      •  India
      • Japan
      •  Korea (Korean)
      •  Malaysia
      •  New Zealand
      •  Philippines
      •  Singapore
      •  Taiwan
      •  Thailand (Thai)
      • Vietnam
      • Americas
      •  Brazil (Portuguese)
      •  Canada
      •  Mexico (Spanish)
      •  United States
      Can't find the country/region you're looking for? Visit our export site or find a local distributor.
  • Translate
  • Profile
  • Settings
Autodesk EAGLE
  • Products
  • More
Autodesk EAGLE
EAGLE User Support (English) Restriction of autorouter?
  • Blog
  • Forum
  • Documents
  • Events
  • Polls
  • Files
  • Members
  • Mentions
  • Sub-Groups
  • Tags
  • More
  • Cancel
  • New
Join Autodesk EAGLE to participate - click to join for free!
Actions
  • Share
  • More
  • Cancel
Forum Thread Details
  • Replies 8 replies
  • Subscribers 179 subscribers
  • Views 1396 views
  • Users 0 members are here
Related

Restriction of autorouter?

Former Member
Former Member over 15 years ago

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

 

  • Sign in to reply
  • Cancel
Parents
  • Former Member
    Former Member over 15 years ago

    James,

     

    Ok, thanks for the advice. Is there literature out there that goes over

    the "art of autorouting" in Eagle or anything?

     

    What I've ended up doing so far is to route the simple digital stuff,

    most of the analog measurement circuitry, and the power lines, but then

    divided my board into the parts that I've routed and those that haven't

    using the "restrict" layers. It seems to have worked: I ran the

    autorouter and it routed the complicated digital signals that would have

    taken me forever.

     

    However, I guess I should clarify what I mean by "touching" the analog

    circuitry that I've already routed. 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?

     

    Regards,

    Brian

     

     

     

    On 2/15/2010 1:12 PM, James Morrison wrote:

    Telemachus wrote on Mon, 15 February 2010 13:04

    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?

     

    Hello Brian,

     

    Of course, you could do your own experiments to determine this--just backup

    the files first.

     

    But to answer your question, the auto-router doesn't touch anything that

    was routed before it starts. So if you hand-route power and critical

    traces then it won't touch that stuff.

     

    This is generally good but sometimes if you pushed a critical route just a

    bit one way or the other you can fit one more trace through but the

    auto-router needs to add a via and things get way congested very

    quickly. So be careful where you put your critical routes. Your first

    pass of the

    auto-router may simple to figure out where congestion is going to occur and

    then go back to original design (copy of design before auto-router was run)

    and adjust critical traces accordingly.

     

    Cheers,

     

    James.

     

     

     

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
Reply
  • Former Member
    Former Member over 15 years ago

    James,

     

    Ok, thanks for the advice. Is there literature out there that goes over

    the "art of autorouting" in Eagle or anything?

     

    What I've ended up doing so far is to route the simple digital stuff,

    most of the analog measurement circuitry, and the power lines, but then

    divided my board into the parts that I've routed and those that haven't

    using the "restrict" layers. It seems to have worked: I ran the

    autorouter and it routed the complicated digital signals that would have

    taken me forever.

     

    However, I guess I should clarify what I mean by "touching" the analog

    circuitry that I've already routed. 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?

     

    Regards,

    Brian

     

     

     

    On 2/15/2010 1:12 PM, James Morrison wrote:

    Telemachus wrote on Mon, 15 February 2010 13:04

    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?

     

    Hello Brian,

     

    Of course, you could do your own experiments to determine this--just backup

    the files first.

     

    But to answer your question, the auto-router doesn't touch anything that

    was routed before it starts. So if you hand-route power and critical

    traces then it won't touch that stuff.

     

    This is generally good but sometimes if you pushed a critical route just a

    bit one way or the other you can fit one more trace through but the

    auto-router needs to add a via and things get way congested very

    quickly. So be careful where you put your critical routes. Your first

    pass of the

    auto-router may simple to figure out where congestion is going to occur and

    then go back to original design (copy of design before auto-router was run)

    and adjust critical traces accordingly.

     

    Cheers,

     

    James.

     

     

     

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
Children
No Data
element14 Community

element14 is the first online community specifically for engineers. Connect with your peers and get expert answers to your questions.

  • Members
  • Learn
  • Technologies
  • Challenges & Projects
  • Products
  • Store
  • About Us
  • Feedback & Support
  • FAQs
  • Terms of Use
  • Privacy Policy
  • Legal and Copyright Notices
  • Sitemap
  • Cookies

An Avnet Company © 2026 Premier Farnell Limited. All Rights Reserved.

Premier Farnell Ltd, registered in England and Wales (no 00876412), registered office: Farnell House, Forge Lane, Leeds LS12 2NE.

ICP 备案号 10220084.

Follow element14

  • X
  • Facebook
  • linkedin
  • YouTube