.4mm to 2.54mm Routing

Hi!

You can't manually route to/from the QFN48 as well. Just run a DRC on

the unrouted board and you'll get a ton of errors. The package already

violates the minimum clearance rules. So the autorouter can't reach the

SMDs without violating the rules even further, hence it leaves them out.

So, to solve the problem, first check the DRC parameters. Then go to the

schematic and check the CLASS settings. Finally, ensure that the NETs

attached to ESP32 belong to the proper CLASS.

Rene

rk wrote on Sat, 17 September 2016 11:36

You can't manually route to/from the QFN48 as well. Just run a DRC on

the unrouted board and you'll get a ton of errors. The package already

violates the minimum clearance rules. So the autorouter can't reach the

SMDs without violating the rules even further, hence it leaves them out.

Oh yes.... I'm slightly embarrassed about not spotting that before putting

up my post! In my defence I was more focussed on my autorouter dying and

EAGLE exiting every 30 seconds!

Maybe a slight usability improvement they could make to EAGLE would be to

have an autorouter report which it generated when it was complete which

specified why it hadn't routed the nets which were remaining unrouted? I

have to admit I almost never use the autorouter and when I have I've never

seen this problem so maybe it does give this info already, but for me it

just goes to a certain percentage and says its finished when clearly there

was still loads to do. Maybe if it said something like "Complete: 20%

routed, 80% unrouted (70% design rule violations, 10% no routing path

found)" that might be more helpful than just saying "complete".

Still, I should have thought about running DRC though.....

Best Regards,

Rachael

--

Web access to CadSoft support forums at www.eaglecentral.ca.  Where the CadSoft EAGLE community meets.

Am 17.09.2016 um 12:56 schrieb Rachael:

have to admit I almost never use the autorouter and when I have I've never

seen this problem so maybe it does give this info already, but for me it

Even when not using the autorouter, you should always run the DRC

before doing any routing. Just to see that there is no hidden error

(dimension, keepout, ...). This is especially true when you are 100%

sure that there is no error, just let the DRC print that out.

As I am doing things wrong more often than not, this approach saved me

quite some time, actually. 

Rene

Am 17.09.2016 um 12:56 schrieb Rachael:

have to admit I almost never use the autorouter and when I have I've never

seen this problem so maybe it does give this info already, but for me it

Even when not using the autorouter, you should always run the DRC

before doing any routing. Just to see that there is no hidden error

(dimension, keepout, ...). This is especially true when you are 100%

sure that there is no error, just let the DRC print that out.

As I am doing things wrong more often than not, this approach saved me

quite some time, actually. 

Rene

CadSoft Guest wrote:

 

Am 17.09.2016 um 12:56 schrieb Rachael:

have to admit I almost never use the autorouter and when I have I've never

seen this problem so maybe it does give this info already, but for me it

 

Even when not using the autorouter, you should always run the DRC

before doing any routing.

 

Absolutely! In my normal design flow the DRC first run will happen as soon as I create my board and load the appropriate DRC settings and I'll run DRC again any time any significant changes are made.

CadSoft Guest wrote:

 

Am 17.09.2016 um 12:56 schrieb Rachael:

have to admit I almost never use the autorouter and when I have I've never

seen this problem so maybe it does give this info already, but for me it

 

Even when not using the autorouter, you should always run the DRC

before doing any routing.

 

Absolutely! In my normal design flow the DRC first run will happen as soon as I create my board and load the appropriate DRC settings and I'll run DRC again any time any significant changes are made.