3 ms·
>BUT, the autorouter is unusable. Wonder why Apple/Google/LAB126/MSFT maintain an army of "eCAD" engineers. Because: 1. They're working on the cutting edge of
by ChuckNorris89 7y ago
>BUT, the autorouter is unusable. Wonder why Apple/Google/LAB126/MSFT maintain an army of "eCAD" engineers.
Because:
1. They're working on the cutting edge of miniaturization and autoroute functionality just doesn't cut it at that level. You need a human understanding of the end product as in consumer electronics you have to plan in advance several (often for lower cost) revisions of the same product for the future.
2. All the ML/AI experts are expensive and they have much lucrative fish to fry such as getting you to buy or click on things rather than optimize PCB aoutoroute for some eCAD company that can't justify their expense as most of their customers will still route by hand since the hardware business is very resilient to change.
3. PCB layout is done(in Western Europe at least) mostly by technicians, not engineers, and their labor costs are cheap as technical high-schools churn hundreds every year. You don't need a university degree and sometimes the company will pay your training for the eCAD tool they're using. In my area, a city with lots of hardware industry, it's basically a blue collar job.
Source: FW dev in the consumer electronics business
- thecleaner 7y agoJust out of interest which city in Western Europe ?
- radarsat1 7y agoAlso from my limited experience in Eagle, the autorouter output is terrible. I mean, it works, but it makes it very hard to "read" the layout and tweak it if necessary. Sometimes it helps do some percentage of the work, but you almost always end up ripping it all out and redoing most of it. Or running it multiple times until you get something that is semi-usable. Perhaps some kind of GAN approach could be used to force an optimizer to perform autorouting with a bias towards "human-like" circuits that actually readable and understandable.