3 ms·
>> Nobody cares about autorouting trivial boards, but there are serious economic incentives to turn 8+ layer boards into 6+ layer boards. Sure, but if a tool c
by phkahler 9y ago
>> Nobody cares about autorouting trivial boards, but there are serious economic incentives to turn 8+ layer boards into 6+ layer boards.
Sure, but if a tool can't route a trivial board like the author had, what hope does it have for doing complex designs?
On a related note, pick up an old arcade game board from the 70's or 80's made by Atari. They're all double sided and are very cleanly routed. The Cinematronic CPU made from 74xx series parts is also double sided and very cleanly routed. In both cases though there is a lot of area not covered by components, but they're still works of art.
- CamperBob2 9y agoSorry, I'm done with responding to people who didn't read the article. It's a cool article, with some worthwhile points to make. Nothing too profound, but worth a few minutes' surfing. Go read it.
- phkahler 9y agoI did. Top to bottom.
- CamperBob2 9y agoSo, his whole point was exactly what you (and a half-dozen other people in the thread) are bringing up as some kind of revelation that no one considered. Yes, it's true, autorouters suck. Most professional PCB designers think of autorouting as a waste of time, and it typically is. He's complaining about how autorouters have trouble with trivial boards like the one he was working with. He's pointing out that this is costing the industry a lot of time and money. He's asking why the problem remains largely unaddressed, at a time when computers running relatively generic tree-search algorithms with minimal prior training are beating 9-dan Go players like rented mules. By trying to call the attention of ML/AI researchers to the issue, he's doing a good thing IMO. No one disputes that a well-routed PCB is a work of art, whether it was done with Altium or rubylith. But it shouldn't be.
- phkahler 9y agoPerhaps I misunderstood. Someone (was it you?) said nobody cares about trivial boards like in the blog, but they do care about complex boards. I took that as a sort of rejection of the relevance of the article. So the point I wanted to make is this: If you're hoping for a tool to do good routing on complex boards, it really should be able to do a great job on simple ones. Hence the blog is entirely relevant by eliminating a bunch of autoroutes based on his simple project. I applaud him for pointing out how bad most of them are and asking the question why they suck when machines can play GO now.