element14 Community
element14 Community
    Register Log In
  • Site
  • Search
  • Log In Register
  • Community Hub
    Community Hub
    • What's New on element14
    • Feedback and Support
    • Benefits of Membership
    • Personal Blogs
    • Members Area
    • Achievement Levels
  • Learn
    Learn
    • Ask an Expert
    • eBooks
    • element14 presents
    • Learning Center
    • Tech Spotlight
    • STEM Academy
    • Webinars, Training and Events
    • Learning Groups
  • Technologies
    Technologies
    • 3D Printing
    • FPGA
    • Industrial Automation
    • Internet of Things
    • Power & Energy
    • Sensors
    • Technology Groups
  • Challenges & Projects
    Challenges & Projects
    • Design Challenges
    • element14 presents Projects
    • Project14
    • Arduino Projects
    • Raspberry Pi Projects
    • Project Groups
  • Products
    Products
    • Arduino
    • Avnet Boards Community
    • Dev Tools
    • Manufacturers
    • Multicomp Pro
    • Product Groups
    • Raspberry Pi
    • RoadTests & Reviews
  • About Us
  • Store
    Store
    • Visit Your Store
    • Choose another store...
      • Europe
      •  Austria (German)
      •  Belgium (Dutch, French)
      •  Bulgaria (Bulgarian)
      •  Czech Republic (Czech)
      •  Denmark (Danish)
      •  Estonia (Estonian)
      •  Finland (Finnish)
      •  France (French)
      •  Germany (German)
      •  Hungary (Hungarian)
      •  Ireland
      •  Israel
      •  Italy (Italian)
      •  Latvia (Latvian)
      •  
      •  Lithuania (Lithuanian)
      •  Netherlands (Dutch)
      •  Norway (Norwegian)
      •  Poland (Polish)
      •  Portugal (Portuguese)
      •  Romania (Romanian)
      •  Russia (Russian)
      •  Slovakia (Slovak)
      •  Slovenia (Slovenian)
      •  Spain (Spanish)
      •  Sweden (Swedish)
      •  Switzerland(German, French)
      •  Turkey (Turkish)
      •  United Kingdom
      • Asia Pacific
      •  Australia
      •  China
      •  Hong Kong
      •  India
      •  Korea (Korean)
      •  Malaysia
      •  New Zealand
      •  Philippines
      •  Singapore
      •  Taiwan
      •  Thailand (Thai)
      • Americas
      •  Brazil (Portuguese)
      •  Canada
      •  Mexico (Spanish)
      •  United States
      Can't find the country/region you're looking for? Visit our export site or find a local distributor.
  • Translate
  • Profile
  • Settings
Autodesk EAGLE
  • Products
  • More
Autodesk EAGLE
EAGLE User Support (English) Multiple SMD pads for the same signal
  • Blog
  • Forum
  • Documents
  • Events
  • Polls
  • Files
  • Members
  • Mentions
  • Sub-Groups
  • Tags
  • More
  • Cancel
  • New
Join Autodesk EAGLE to participate - click to join for free!
Actions
  • Share
  • More
  • Cancel
Forum Thread Details
  • Replies 2 replies
  • Subscribers 176 subscribers
  • Views 678 views
  • Users 0 members are here
Related

Multiple SMD pads for the same signal

autodeskguest
autodeskguest over 17 years ago

 

I need to use a SMD connector which requires two pads per contact (Molex

52610). The problem is how to make Eagle aware of multi-part SMD pads.

I have a 10-contact connector which has 20 pads in two rows (2x10 pads).

Each contact in the connector is shaped so that it uses two separate

pads, on in each end of the contact. I know I could solve the problem by

making a 20-contact connector and then connecting the contacts pairwise

in the schematic editor. Unfortunately, this would lead to a messy

schematic and also ruin interchangeability with 10-pin FPC connectors.

Is there some smd pad naming trick which would help here? I have named

the pads 1,2,...10 and 1b,2b,...10b, but is there some way to name the

pads so that Eagle would recognize them to belong to the same potential?

Or is there some other way to connect several pads to one signal?

I do not think this problem is unique. For example, many dfn packages

have an exposed ground pad in the middle (either for better heat

conduction or for better GND contact), and that pad is seldom drawn in the

schematic.

TIA,

 

- Ville

 

--

 

 

 

  • Sign in to reply
  • Cancel
  • autodeskguest
    autodeskguest over 17 years ago

    Ville wrote:

     

    I need to use a SMD connector which requires two pads per contact (Molex

    52610). The problem is how to make Eagle aware of multi-part SMD pads.

    I have a 10-contact connector which has 20 pads in two rows (2x10 pads).

    Each contact in the connector is shaped so that it uses two separate

    pads, on in each end of the contact. I know I could solve the problem by

    making a 20-contact connector and then connecting the contacts pairwise

    in the schematic editor. Unfortunately, this would lead to a messy

    schematic and also ruin interchangeability with 10-pin FPC connectors.

    Is there some smd pad naming trick which would help here? I have named

    the pads 1,2,...10 and 1b,2b,...10b, but is there some way to name the

    pads so that Eagle would recognize them to belong to the same potential?

    Or is there some other way to connect several pads to one signal?

    I do not think this problem is unique. For example, many dfn packages

    have an exposed ground pad in the middle (either for better heat

    conduction or for better GND contact), and that pad is seldom drawn in the

    schematic.

    TIA,

     

    - Ville

     

    Symbol pins and pads have to be 1 to 1. You can make the solder stop and

    cream outlines so they match the required outline and (not knowing the

    shape) use a long smd pad to bridge the two pins.

    Paul R.

     

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • autodeskguest
    autodeskguest over 17 years ago

     

    Symbol pins and pads have to be 1 to 1. You can make the solder stop and

    cream outlines so they match the required outline and (not knowing the

    shape) use a long smd pad to bridge the two pins.

     

    A good idea! Unfortunately, this has the problem that I would like to

    have traces going in between the two rows of pads. If there are long pads,

    this is not possible (and DRC might have some complaints about vias, as

    well).

     

    I tried another approach. I made "hidden" pins into the schematic symbol

    (one contact symbol having two pins). This is something that at least

    some transistor symbols have in the library. However, I had to abandon

    that approach for two reasons. First, ERC had a lot of complaints about

    missing junctions. Second, even this did not enable me to make the two

    connectors (horizontal which has 10 pads and right angle with 20 pads)

    interchangeable, as Eagle refused to use the 20-pin symbol with 10-pin

    packages.

     

    So, the outcome was that I made a connector with 20 pins. It looks ugly

    in the schematic but the PCB is fine.

     

    However, this would be nice to have in future versions of Eagle. It

    would be useful to be able to have several connections to one pad and

    several pads to one connection. Without knowing anything about the internal

    structure of Eagle, this may be either rather simple or horrendously

    difficult.

     

    - Ville

     

    --

     

     

     

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
element14 Community

element14 is the first online community specifically for engineers. Connect with your peers and get expert answers to your questions.

  • Members
  • Learn
  • Technologies
  • Challenges & Projects
  • Products
  • Store
  • About Us
  • Feedback & Support
  • FAQs
  • Terms of Use
  • Privacy Policy
  • Legal and Copyright Notices
  • Sitemap
  • Cookies

An Avnet Company © 2025 Premier Farnell Limited. All Rights Reserved.

Premier Farnell Ltd, registered in England and Wales (no 00876412), registered office: Farnell House, Forge Lane, Leeds LS12 2NE.

ICP 备案号 10220084.

Follow element14

  • X
  • Facebook
  • linkedin
  • YouTube