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 & Tria Boards Community
    • Dev Tools
    • Manufacturers
    • Multicomp Pro
    • Product Groups
    • Raspberry Pi
    • RoadTests & Reviews
  • About Us
    About the element14 Community
  • 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
      •  Japan
      •  Korea (Korean)
      •  Malaysia
      •  New Zealand
      •  Philippines
      •  Singapore
      •  Taiwan
      •  Thailand (Thai)
      •  Vietnam
      • 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) How to apply net class to unconnected pad?
  • 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
  • State Not Answered
  • Replies 8 replies
  • Subscribers 190 subscribers
  • Views 2010 views
  • Users 0 members are here
  • pad
  • pin
  • class
  • creepage
  • net
  • unconnected
  • clearance
Related

How to apply net class to unconnected pad?

electrodevab
electrodevab over 11 years ago

Hi all,

 

I would be glad to have some input on an issue I ran into recently:

 

Assume I added a diode in a sot23 package. The diode symbol only have two (anode and cathode) connecting pins but the package has three pads. To the two connecting pins I assign netclasses with different clearance and creepage restrictions but then there will be no netclass assigned to the third pad of the package. This generates tons of errors when running drc and I dont have full control of the clearance and creepage distances.

 

For the devices I create myself I can add a connecting pin for each pad in the device and then add a short unconnected net to the unconnected pads so that I can apply a netclass. This is not the correct way to do it, does anyone know if is there any other way to do this?

 

/Tomas

  • Sign in to reply
  • Cancel
Parents
  • autodeskguest
    0 autodeskguest over 11 years ago

    On 2/02/2015 9:06 p.m., Tomas Bergh wrote:

    Hi all,

     

    I would be glad to have some input on an issue I ran into recently:

     

    Assume I added a diode in a sot23 package. The diode symbol only have

    two (anode and cathode) connecting pins but the package has three pads.

    To the two connecting pins I assign netclasses with different clearance

    and creepage restrictions but then there will be no netclass assigned to

    the third pad of the package. This generates tons of errors when running

    drc and I dont have full control of the clearance and creepage

    distances.

     

    For the devices I create myself I can add a connecting pin for each pad

    in the device and then add a short unconnected net to the unconnected

    pads so that I can apply a netclass. This is not the correct way to do

    it, does anyone know if is there any other way to do this?

     

    You say you get "tons of errors" to this unconnected pad so I assume it

    is a polygon pour that is getting too close to this unused pad. If this

    is the case keep the polygon away by surrounding the pad with a fence

    wires on the tRestrict layer.The width of the wire is at least the

    clearance you require and should be close to but not touch the pad.

     

    HTH

    Warren

     

     

     

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
Reply
  • autodeskguest
    0 autodeskguest over 11 years ago

    On 2/02/2015 9:06 p.m., Tomas Bergh wrote:

    Hi all,

     

    I would be glad to have some input on an issue I ran into recently:

     

    Assume I added a diode in a sot23 package. The diode symbol only have

    two (anode and cathode) connecting pins but the package has three pads.

    To the two connecting pins I assign netclasses with different clearance

    and creepage restrictions but then there will be no netclass assigned to

    the third pad of the package. This generates tons of errors when running

    drc and I dont have full control of the clearance and creepage

    distances.

     

    For the devices I create myself I can add a connecting pin for each pad

    in the device and then add a short unconnected net to the unconnected

    pads so that I can apply a netclass. This is not the correct way to do

    it, does anyone know if is there any other way to do this?

     

    You say you get "tons of errors" to this unconnected pad so I assume it

    is a polygon pour that is getting too close to this unused pad. If this

    is the case keep the polygon away by surrounding the pad with a fence

    wires on the tRestrict layer.The width of the wire is at least the

    clearance you require and should be close to but not touch the pad.

     

    HTH

    Warren

     

     

     

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
Children
  • electrodevab
    0 electrodevab over 11 years ago in reply to autodeskguest

    Hi,

    No, I do not use a fill in the top layer here. The clearance issues of importance are between the unconnected pad (top right pad of D9) and the other two pads on the same sot23 package. (D9)

    There are also clearance errors to other components in this example. (between T1, D7 and D9)

     

    image

     

    Any ideas?

     

    Regards,

    Tomas

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • 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 © 2026 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.

Follow element14

  • X
  • Facebook
  • linkedin
  • YouTube