It's lacking a rather important feature that EAGLE added somewhat recently—just in version 7?—which is the ability to tell the autorouter to avoid, where practical, running traces through fill areas.
There's an option to treat fill areas as keepouts, but that's not the same. I want to make use of fill areas (or fill-area-rich layers, but preferably the fill areas themselves) expensive, and it's best if I can make it expensive per unit distance, to keep violations short.
As things currently stand, I can forbid the autorouter to violate fill areas at all, in which case it's unlikely to complete a typical design of mine, or allow it to do as it pleases, in which case it'll surely cut up my ground zones something fierce, typically creating many islands and generally requiring massive manual cleanup.
(This becomes less of a problem if I start using more layers for my somewhat-complex boards, taking advantage of cheap Chinese fab services, but I'd really like to have this handled right for 2-layer designs.)
On the upside: the libraries are looking good. I find the mini-USB connector I'm currently using, and the STM32F446 variants I'm contemplating for upcoming designs. A fair selection of Actel (now Microsemi) parts, including some I might use at some point. Quite a few from Lattice, but not the ones of current interest. NXP/Freescale Kinetis parts, again, quite a few, but not the ones I'm using. Resistor packs, at least some of the ones I use. That and having a fair supply of 3D models corresponding to library footprints, and life is good.
So, if I go that route (which is looking likely), I won't need to do a huge amount of custom component-building (and much of that can probably be handled by importing my EAGLE library, I suppose, though I haven't tried that yet). But I may need to pester the vendor to add some more tuning parameters to the autorouter.
Comments