When it routes, it runs for a while (20 minutes?) all the while shortening overall trace length and number of vias.
It took the default trace length from KiCAD, but then has it's own table.
The bad news: Each time you change the board, as best I can tell, you have to load it in. You can't alter what's connected to what. Same with KiCAD. I wanted to add some pads to a set of unused jumpers on the block (the test points you see in the picture) and I couldn't. If I'd wanted to do it right, I'd have had to edit it in the schematic (which I did), THEN update the board, then reupload it to web program, (maybe it would take the current information?), let it reroute, which means recreating that table of trace widths (I ended up doing that table like 6 times - not that it's hard, but it doesn't mean I wanted to keep doing it), routing, reoptimzing by pushing the traces around, and then bringing it back into KiCAD.
Now I'm thinking maybe I could load the almost done board in and it would respect the trace widths on the nets. If so, it's a lot easier as I could just go back and forth. I haven't tried it.
But I really like the autorouter. if i'd had the layout about right and the schematic 100%, the whole routing process would have been under 30 minutes, including set up. It's not as complex a board as you've been doing, but its not bad, either.
Of course, I just thought "gee, what if someone wants launch control" so I may come back with info on how to upload a done board, or I may route those two traces by hand.
