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) label of supply symbols
  • 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 7 replies
  • Subscribers 188 subscribers
  • Views 3026 views
  • Users 0 members are here
Related

label of supply symbols

autodeskguest
autodeskguest over 9 years ago

Hi all,

I wonder if there is a way to automatically label a supply symbol (i.e.

GND) to reflect the actual name of the net it is connected to.

 

In my schematic I have about ten isolated ground nets. I named each one

with different (and meaningful) names, like: GND_MCU, GND_AUDIO,

GND_UART, etc...

 

To improve the readability of the schematic I would like to place a

label close to each ground symbol to show the name of "its" net.

 

Right now I'm able to do so only using the LABEL command, attaching it

to the net. It works, but it would be much easier if the symbols can

show it by itself, using something like >NAME or >VALUE placeholders.

 

Thanks

Marco

 

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

    Hi Marco,

     

    You can create library parts for all your alternative voltages that you

    require and then these will have the right name and automatically set the

    signal name of the signal they are connected to. Manually setting the net

    name to be different from what the symbol implies and adding net labels to

    show the right value runs the risk of missing something and ending up with

    things not connected where you expect.

     

    In the library manager, duplicate the GND device and rename it to for

    example GND_MCU and do the same with the GND symbol. Then open the GND_MCU

    symbol and change the pin name from GND to GND_MCU also. Finally, open the

    GND_MCU device, delete the GND symbol and add in the GND_MCU symbol. Now

    when you place this in your schematics it will work correctly and put the

    correct name on your nets.

     

    IMPORTANT Remember to rename the symbol pin. Failure to remember this

    will result in the original name being placed on the nets which you may not

    see until it's too late, so check, check and check again when you create

    alternative power supply symbols!

     

    Best Regards,

     

    Rachael

    --

    EAGLE support forums at http://www.eaglecentral.ca :: Where the EAGLE community meets.

     

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

    Hi Marco,

     

    You can create library parts for all your alternative voltages that you

    require and then these will have the right name and automatically set the

    signal name of the signal they are connected to. Manually setting the net

    name to be different from what the symbol implies and adding net labels to

    show the right value runs the risk of missing something and ending up with

    things not connected where you expect.

     

    In the library manager, duplicate the GND device and rename it to for

    example GND_MCU and do the same with the GND symbol. Then open the GND_MCU

    symbol and change the pin name from GND to GND_MCU also. Finally, open the

    GND_MCU device, delete the GND symbol and add in the GND_MCU symbol. Now

    when you place this in your schematics it will work correctly and put the

    correct name on your nets.

     

    IMPORTANT Remember to rename the symbol pin. Failure to remember this

    will result in the original name being placed on the nets which you may not

    see until it's too late, so check, check and check again when you create

    alternative power supply symbols!

     

    Best Regards,

     

    Rachael

    --

    EAGLE support forums at http://www.eaglecentral.ca :: Where the EAGLE community meets.

     

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

    Il 12/05/2017 12:52, Rachael ha scritto:

     

    You can create library parts for all your alternative voltages that you

    require and then these will have the right name and automatically set the

    signal name of the signal they are connected to. Manually setting the net

    name to be different from what the symbol implies and adding net labels to

    show the right value runs the risk of missing something and ending up with

    things not connected where you expect.

     

     

    Thanks for your answer.

    Yes, this could be a solution. The drawback is I will end up with a list

    of symbols some of them used only in one project...

     

     

    In the library manager, duplicate the GND device and rename it to for

    example GND_MCU and do the same with the GND symbol. Then open the GND_MCU

    symbol and change the pin name from GND to GND_MCU also. Finally, open the

    GND_MCU device, delete the GND symbol and add in the GND_MCU symbol. Now

    when you place this in your schematics it will work correctly and put the

    correct name on your nets.

     

    IMPORTANT Remember to rename the symbol pin. Failure to remember this

    will result in the original name being placed on the nets which you may not

    see until it's too late, so check, check and check again when you create

    alternative power supply symbols!

     

     

    Yeah, I'm aware of this.

    Do you think it would possible to write an ulp to do all this stuff? It

    needs several actions and it's error prone if you have to make dozens of

    such a device...

     

     

     

    • 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 © 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