What Route Do You Take?

There are a lot of polar opposites in the “what is my philosophy” world: Mac vs. PC, on shore vs. off shore manufacturing, Ford vs. Chevy, Atmel vs. Microchip (well, maybe not that one so much any more), auto router vs. hand route…. Yes, I’m specifically avoiding political opposites.

DB 1Routing is what I’m really interested in today. The conventional debate is hand vs. auto route. CAD companies spend a lot of time and money on autorouters, but there’s definitely a line of thought that says it’s not ready for prime time yet. This shirt designed by Chris Gammel, on Teespring pretty much says it all.

But, it’s more complex than that. Most auto-routes end up requiring some hand work, either to finish routes that can’t be found automatically, or to clean up a few less than efficient choices. There are differing techniques for complete hand-routing as well.

I often find myself looking at a layout project a bit like a chess game. I don’t just start at one end of the board and work my way to the other side. I tend to focus on specific parts or critical requirements first, like signal paths that need to be short, or sections with more critical grounding requirements. (The image above isn’t mine. It’s from the Beagleboard.)

When it gets to the mass, I tend to try and think ahead, projecting moves out, as though it were a chess game. When I’m looking for the best route for signal path A, I try and think ahead to how it will impact B, D, D… as far ahead as I can go.

I’m not sure if doing it this way is easier, of if it would be better to just start routing and then re-route as I run into roadblacks. What about you? How do you approach a complex layout?

Duane Benson
Holy cow. I Googled “Trust no one” to get some ideas for my signature
Never do that. It’s going to take a week to shake off all the negativity