.4mm to 2.54mm Routing

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.

On 9/17/2016 5:23 AM, rachaelp wrote:

CadSoft Guest wrote:

I was afraid you were going to say that

 

Why afraid? Manual routing - particularly of localised bits - is a lot

easier than setting up the autorouting rules!

I agree, manually routing for the most part is much simpler, the autorouter isn't good enough or stable enough to be used for full on routing. For me I can cause it to abruptly exit within minutes of starting to use it, that's just not an acceptable level of stability for me.

 

Back to the OP's question, I have downloaded the design and have confirmed that for no obvious reason it just won't route from the QFN to anywhere else. I don't know if this is something odd in the library part (I had a look but couldn't see anything) or something relating to the grid, etc. I couldn't see anything on keepout/restrict layers. Unfortunately I can't keep the autorouter open for long enough without crashing for me to do any in depth analysis of why it is not working.

 

Manual routing of this is simple though if you rotate the IC by 45 degrees and move it down slightly and then all of the signals just flow nicely out to the connectors so not using the autorouter shouldn't be a big problem.

 

Best Regards,

 

Rachael

 

--

To view any images and attachments in this post, visit:

https://www.element14.com/community/message/205878

 

Hi Rachel, thanks for checking this for me.

I use autorouting mostly for rough placement scenarios and sometimes for

lazy simple routing like this.

I did not created this library but did add an extra symbol and moved the

pads on the footprint slightly as they were not lining up with the pad

centers on .2mm grid spacing (which I thought was the original issue

with it not routing) but it did not help.

https://dl.dropboxusercontent.com/u/2238318/esp32.lbr

Glenn

On 9/17/2016 6:36 AM, René König wrote:

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

 

Thanks René

On 9/17/2016 8:52 AM, Glenn Jones wrote:

On 9/17/2016 5:23 AM, rachaelp wrote:

CadSoft Guest wrote:

I was afraid you were going to say that

 

Why afraid? Manual routing - particularly of localised bits - is a lot

easier than setting up the autorouting rules!

I agree, manually routing for the most part is much simpler, the

autorouter isn't good enough or stable enough to be used for full on

routing. For me I can cause it to abruptly exit within minutes of

starting to use it, that's just not an acceptable level of stability

for me.

 

Back to the OP's question, I have downloaded the design and have

confirmed that for no obvious reason it just won't route from the QFN

to anywhere else. I don't know if this is something odd in the library

part (I had a look but couldn't see anything) or something relating to

the grid, etc. I couldn't see anything on keepout/restrict layers.

Unfortunately I can't keep the autorouter open for long enough without

crashing for me to do any in depth analysis of why it is not working.

 

Manual routing of this is simple though if you rotate the IC by 45

degrees and move it down slightly and then all of the signals just

flow nicely out to the connectors so not using the autorouter

shouldn't be a big problem.

 

Best Regards,

 

Rachael

 

--

To view any images and attachments in this post, visit:

https://www.element14.com/community/message/205878

 

 

Hi Rachel, thanks for checking this for me.

 

I use autorouting mostly for rough placement scenarios and sometimes for

lazy simple routing like this.

 

I did not created this library but did add an extra symbol and moved the

pads on the footprint slightly as they were not lining up with the pad

centers on .2mm grid spacing (which I thought was the original issue

with it not routing) but it did not help.

 

https://dl.dropboxusercontent.com/u/2238318/esp32.lbr

 

Glenn

Hi Rachel,

As Rene, indicated it was my default routing class specs that caused the

routing not to work.

Thanks for your help

Glenn