Actions
Forum Thread Details
  • Replies 4 replies
  • Subscribers 181 subscribers
  • Views 1351 views
  • Users 0 members are here
Related

Pad diameter on board doesn't match pad diameter in library package

Former Member

Greetings! Hoping someone can help me with a strange issue.

 

I've created a new device in Eagle 7.6, where the holes are fairly close to each other. I've adjusted the hole diameter and pad dimensions, but the size of the pad doesn't seem to be carrying over correctly to the package in my board. here's a screenshot of the pad/hole dimensions:

 

image

And in my library package, everything looks correct:

 

image

 

But when I place the device in my schematic and generate the board, the pad dimensions have "grown" significantly.

 

image

 

I read in another thread that the DRC could be overriding these values - so I opened the DRC rules I've been using (OSHPark) and tried setting the top/inner/bottom pad min to 0mil in the "Restring" options - just to see if this was what was causing the issue, but no change.

 

So anyway, I hope that someone can give me some advice as to what I might be doing wrong.

 

Thanks much!

Parents

  • Phillip Fisk wrote:

     

    I read in another thread that the DRC could be overriding these values - so I opened the DRC rules I've been using (OSHPark) and tried setting the top/inner/bottom pad min to 0mil in the "Restring" options - just to see if this was what was causing the issue, but no change.

    Hi Phillip,

     

    Hopefully from the link in Warrens post above you'll see where you went wrong as that explains how it works clearly. In a nutshell all you did was change the min allowed values, not the % value which is used in the actual calculation so you will need to adjust that as well.

     

    Best Regards,

     

    Rachael

     

    P.S. To those familiar with the other very very long thread which ended up on this subject recently, I suspect this is the mistake the originator of that thread made when he claimed his problem wasn't caused by restring.

Reply

  • Phillip Fisk wrote:

     

    I read in another thread that the DRC could be overriding these values - so I opened the DRC rules I've been using (OSHPark) and tried setting the top/inner/bottom pad min to 0mil in the "Restring" options - just to see if this was what was causing the issue, but no change.

    Hi Phillip,

     

    Hopefully from the link in Warrens post above you'll see where you went wrong as that explains how it works clearly. In a nutshell all you did was change the min allowed values, not the % value which is used in the actual calculation so you will need to adjust that as well.

     

    Best Regards,

     

    Rachael

     

    P.S. To those familiar with the other very very long thread which ended up on this subject recently, I suspect this is the mistake the originator of that thread made when he claimed his problem wasn't caused by restring.

Children
No Data