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) Why do I need to draw the same symbol N times?
  • 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 16 replies
  • Subscribers 181 subscribers
  • Views 2330 views
  • Users 0 members are here
Related

Why do I need to draw the same symbol N times?

autodeskguest
autodeskguest over 9 years ago

More often than not the same chip is available in different packages,

quite often with different number of pins and the packages with fewer

pins omit some of the lesser used signals.

 

Currently, you need to create a different symbol for every package: if

you have a chip that comes in 5 different packages, with a few pin

differences, you need a symbol drawn for ABC1234-SOIC, ABC1234-BGA,

ABC1234-TSOP and so on. It's the same damn chip, just on some packages

some pins are missing.

 

I wonder if I'm alone with the wish of having just one symbol, with

every possible signal drawn. Then, when it gets placed to the schematic

with a package selected, the not bonded pins grey out and don't allow

wires to be connected to them?

--

Zoltán Kócsi

Bendor Research Pty. Ltd.

 

 

  • Sign in to reply
  • Cancel
Parents
  • rachaelp
    rachaelp over 9 years ago

    zoltan wrote on Fri, 23 September 2016 05:29

    I wonder if I'm alone with the wish of having just one symbol, with

    every possible signal drawn. Then, when it gets placed to the

    schematic

    with a package selected, the not bonded pins grey out and don't allow

    wires to be connected to them?

     

     

    Morten Leikvoll wrote on Fri, 23 September 2016 07:47

    But currently (7.x), if the symbol differs slightly betweeen packages,

     

    you have to copy/make a new symbol, and add/remove pins. Sometimes it

    would have been nice if unconnected pins at the symbol were hidden at

    the schematics, if they are not user/connected to the chosen package.

     

     

    Yes I think this would be nice. For a lot of cases the existing system

    works fine but being able to have a single device which deals with the

    entire part in all its variants rather than having to have duplicate parts

    with slightly different symbols would be a big benefit in terms of having

    much tidier and easier to use libraries. I like the idea of greying out or

    hiding unconnected pins but sometimes that might not be enough as a variant

    can possibly change a pin function (i.e. it bonds the pin to another

    function internally). For this reason I think being able to specify

    alternative symbols within the device as well as alternative packages would

    be a big benefit too.

     

    Best Regards,

     

    Rachael

     

     

     

     

    --

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

     

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

    Hi All,

     

    This is definitely a pretty split topic it would be hard to make a

    suggestion either way.

     

    To answer the original question, the way I would handle this is a I

    would create one symbol which would represent the smallest( the one with

    the fewest pads) of the packages.

     

    I would create a device for the smallest package using just that symbol.

     

    Let's say that the next package up has 4 extra pins. I would create a

    new symbol with just those 4 pins. When I go to make the device for this

    package, I would add this symbol plus the symbol with the 4 extra pins.

     

    Repeat this for as many packages as necessary. Basically, instead of

    subtracting pins from the largest package configuration, we add pins to

    the lowest. You can adjust the add levels to make the two symbols come

    in together.

     

    I don't like the idea of greying out pins in the schematic or x-ing them

    out in some way. I think it makes the schematic untidy and adds

    unnecessary additional info.

     

    hth,

    Jorge Garica

     

     

     

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

    Jorge Garcia wrote on Tue, 27 September 2016 17:36

    Hi All,

     

    This is definitely a pretty split topic it would be hard to make a

    suggestion either way.

     

    To answer the original question, the way I would handle this is a I

    would create one symbol which would represent the smallest( the one

    with

    the fewest pads) of the packages.

     

    I would create a device for the smallest package using just that

    symbol.

     

    Let's say that the next package up has 4 extra pins. I would create a

    new symbol with just those 4 pins. When I go to make the device for

    this

    package, I would add this symbol plus the symbol with the 4 extra

    pins.

     

    Repeat this for as many packages as necessary. Basically, instead of

    subtracting pins from the largest package configuration, we add pins to

     

    the lowest. You can adjust the add levels to make the two symbols come

     

    in together.

     

    I don't like the idea of greying out pins in the schematic or x-ing

    them

    out in some way. I think it makes the schematic untidy and adds

    unnecessary additional info.

     

    hth,

    Jorge Garica

     

     

    I'm sort of in agreement with you regarding the negatives of greying out or

    x-ing out the pins, but then for a lot of cases adding extra symbol parts

    just for the additional pins could quickly lead to a messy schematics too

    and you may not be able to group pins how you would like.

     

    So the only other solution I can think of would be to have the ability to

    specify a symbol variant based on the "master" symbol which could then have

    pins removed / renamed / added as necessary. Then anything in the master

    symbol which was unrelated to the changes on the variants would be

    inherited such that any changes to these parts of the master symbol would

    occur in the variant symbols. This would remove the issue of having

    multiple copies of a single symbol to maintain.

     

    There are several other use cases for having the ability to specify

    multiple symbols (I covered one of these in one of my earliest posts on

    this forum) but the way of using the feature would probably need to be

    slightly tweaked. It would be good if there was a way to support multiple

    symbols which could cover all use cases.

     

    Best Regards,

     

    Rachael

     

     

     

     

    --

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

     

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
Reply
  • rachaelp
    rachaelp over 9 years ago in reply to autodeskguest

    Jorge Garcia wrote on Tue, 27 September 2016 17:36

    Hi All,

     

    This is definitely a pretty split topic it would be hard to make a

    suggestion either way.

     

    To answer the original question, the way I would handle this is a I

    would create one symbol which would represent the smallest( the one

    with

    the fewest pads) of the packages.

     

    I would create a device for the smallest package using just that

    symbol.

     

    Let's say that the next package up has 4 extra pins. I would create a

    new symbol with just those 4 pins. When I go to make the device for

    this

    package, I would add this symbol plus the symbol with the 4 extra

    pins.

     

    Repeat this for as many packages as necessary. Basically, instead of

    subtracting pins from the largest package configuration, we add pins to

     

    the lowest. You can adjust the add levels to make the two symbols come

     

    in together.

     

    I don't like the idea of greying out pins in the schematic or x-ing

    them

    out in some way. I think it makes the schematic untidy and adds

    unnecessary additional info.

     

    hth,

    Jorge Garica

     

     

    I'm sort of in agreement with you regarding the negatives of greying out or

    x-ing out the pins, but then for a lot of cases adding extra symbol parts

    just for the additional pins could quickly lead to a messy schematics too

    and you may not be able to group pins how you would like.

     

    So the only other solution I can think of would be to have the ability to

    specify a symbol variant based on the "master" symbol which could then have

    pins removed / renamed / added as necessary. Then anything in the master

    symbol which was unrelated to the changes on the variants would be

    inherited such that any changes to these parts of the master symbol would

    occur in the variant symbols. This would remove the issue of having

    multiple copies of a single symbol to maintain.

     

    There are several other use cases for having the ability to specify

    multiple symbols (I covered one of these in one of my earliest posts on

    this forum) but the way of using the feature would probably need to be

    slightly tweaked. It would be good if there was a way to support multiple

    symbols which could cover all use cases.

     

    Best Regards,

     

    Rachael

     

     

     

     

    --

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

     

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
Children
No Data
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.

ICP 备案号 10220084.

Follow element14

  • X
  • Facebook
  • linkedin
  • YouTube