<?xml-stylesheet type="text/xsl" href="https://community.element14.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>EAGLE Autorouter Exploration</title><link>/products/eagle/b/blog/posts/eagle-autorouter-exploration</link><description>Most people who get into PCB design will automatically be intrigued by the concept of an autorouter. It would make sense to the outside observer that an algorithm would be able to process millions of iterations of routings that finds the best b...</description><dc:language>en-US</dc:language><generator>Telligent Community 12</generator><item><title>RE: EAGLE Autorouter Exploration</title><link>https://community.element14.com/products/eagle/b/blog/posts/eagle-autorouter-exploration</link><pubDate>Thu, 03 Oct 2013 18:01:52 GMT</pubDate><guid isPermaLink="false">93d5dcb4-84c2-446f-b2cb-99731719e767:1e4b363d-8145-4d34-a56f-2b45c6c452b7</guid><dc:creator>jmsaltzman</dc:creator><slash:comments>1</slash:comments><description>&lt;p&gt;Interesting post, DRC rule adjustment is definitely the key to getting usable results.&amp;nbsp; This autorouted example shows a typically odd result: unevenly-spaced traces, vias where they shouldn&amp;#39;t be, and a nonsensical mix of 45- and 90-degree corners.&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;I&amp;#39;ve found EAGLE&amp;#39;s autorouter useful for guiding component placement: if it can autoroute, then I can route by hand easily.&amp;nbsp; But its results remind me of monkeys mashing on typewriters: you might get an OK result sometimes, but do you want to develop monkey-wrangling skills or board-routing skills?!&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;For usable results, I&amp;#39;d recommend preparing more than just component placement before autorouting:&lt;/p&gt;&lt;ul&gt;&lt;li&gt;Add power polygons,&lt;/li&gt;&lt;li&gt;Hand-route short/obvious/important traces,&lt;/li&gt;&lt;li&gt;Set up net classes (eg. power vs. signal),&lt;/li&gt;&lt;li&gt;SAVE before autorouting so you don&amp;#39;t rip up hand-routed prep with the autorouter results.&lt;/li&gt;&lt;/ul&gt;&lt;img src="https://community.element14.com/aggbug?PostID=16609&amp;AppID=69&amp;AppType=Weblog&amp;ContentType=0" width="1" height="1"&gt;</description></item><item><title>RE: EAGLE Autorouter Exploration</title><link>https://community.element14.com/products/eagle/b/blog/posts/eagle-autorouter-exploration</link><pubDate>Tue, 01 Oct 2013 19:54:12 GMT</pubDate><guid isPermaLink="false">93d5dcb4-84c2-446f-b2cb-99731719e767:1e4b363d-8145-4d34-a56f-2b45c6c452b7</guid><dc:creator>DAB</dc:creator><slash:comments>0</slash:comments><description>&lt;p&gt;Hi Dave,&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;Good post.&amp;nbsp; As I recall, most of the algorithms used for auto-routing have their origines in early AI research.&lt;/p&gt;&lt;p&gt;There are many ways to help the router out by learning how to plan your component layout so that there are clear short routes for your circuit lines.&lt;/p&gt;&lt;p&gt;There were many good layout artists in my day who could take a design and set it up to make the routing, done by hand in my day, so that the board layout was very clean.&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;I suspect that if you dig into the autorouting software you can find some &amp;quot;prefferences&amp;quot; tables where you can help the router in its decision process.&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;It is like any other good piece of software, you need to learn how to use it properly to get the most benefit from it.&lt;/p&gt;&lt;p&gt;If you let the defaults loose on your design, you will end up with some very creative solutions.&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;Makes good art though.&lt;/p&gt;&lt;p&gt;DAB&lt;/p&gt;&lt;img src="https://community.element14.com/aggbug?PostID=16609&amp;AppID=69&amp;AppType=Weblog&amp;ContentType=0" width="1" height="1"&gt;</description></item><item><title>RE: EAGLE Autorouter Exploration</title><link>https://community.element14.com/products/eagle/b/blog/posts/eagle-autorouter-exploration</link><pubDate>Mon, 30 Sep 2013 22:44:18 GMT</pubDate><guid isPermaLink="false">93d5dcb4-84c2-446f-b2cb-99731719e767:1e4b363d-8145-4d34-a56f-2b45c6c452b7</guid><dc:creator>shabaz</dc:creator><slash:comments>1</slash:comments><description>&lt;p&gt;Hi Dave,&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;Great article. Another suggestion for complex boards would be to use as few through-hole parts as possible, particularly dense connectors, because it is so much easier to route when the&amp;nbsp; planes&amp;nbsp; do not have component lead holes, so that traces can run under components too (assuming that is ok from a circuit design point of view).&lt;/p&gt;&lt;img src="https://community.element14.com/aggbug?PostID=16609&amp;AppID=69&amp;AppType=Weblog&amp;ContentType=0" width="1" height="1"&gt;</description></item></channel></rss>