<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Famicom on Bald Engineer</title><link>https://www.baldengineer.com/tag/famicom</link><description>Recent content in Famicom on Bald Engineer</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Thu, 31 Mar 2022 03:30:25 +0000</lastBuildDate><atom:link href="https://www.baldengineer.com/tag/famicom/index.xml" rel="self" type="application/rss+xml"/><item><title>Autorouters Suck: Autorouter: 0. Baldengineer: 1</title><link>https://www.baldengineer.com/autorouters-suck-autorouter-0-baldengineer-1.html</link><pubDate>Tue, 03 Mar 2015 15:06:54 +0000</pubDate><guid isPermaLink="false">https://www.baldengineer.com/?post_type=photo&amp;p=4391</guid><description>I am not a fan of relying on the Autorouter in EAGLE – or any PCB CAD software for that matter. When laying out a board, I’ll use the autorouter to get an idea if the part placement is going to work or not. In this case, I was reminded how much autorouters suck! Even after running for while, the autorouter could only route up 50% of the nets (signals).<p><img src="https://www.baldengineer.com/wp-content/uploads/2015/03/autorouter0baldengineer1.png" alt="Autorouters Suck:  Autorouter: 0.  Baldengineer: 1"/></p></description></item></channel></rss>