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) Eagle lib creation - LQFP48 Pin Numbering
  • 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 4 replies
  • Subscribers 188 subscribers
  • Views 821 views
  • Users 0 members are here
Related

Eagle lib creation - LQFP48 Pin Numbering

e14 Contributor
e14 Contributor over 14 years ago

I have created a part in a new library and when I opt for the labeling for

the pin & pad, I get P$1, P$2, etc for the pin - why not just 1, 2, 3, etc?

Is there some option I have on or off that I need to switch? I have seen

other parts in different libraries that have the same setup, but just show

the 1, 2, 3 and not P$1.

 

Please assist,

Bob

--

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

 

  • Sign in to reply
  • Cancel
Parents
  • e14 Contributor
    e14 Contributor over 14 years ago

    bob4432 wrote on Mon, 19 March 2012 22:25

    I get P$1, P$2, etc for the pin

     

    You forgot to give the pins explicit names in the symbol.

    --

    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
  • e14 Contributor
    e14 Contributor over 14 years ago in reply to e14 Contributor

    like this or something else, as I have it set to show pin and pad as I need

    that for different setups of the stm32 chip:

     

     

     

    --

    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
  • e14 Contributor
    e14 Contributor over 14 years ago in reply to e14 Contributor

    Oops, I should have said "package" instead of "symbol".  When you make the

    package, you need to give each pad a name that will make sense when you go

    to make the connection between the symbol and package in the device editor.

    For IC packages, these would usually be pin numbers starting at 1.  When

    you make the symbol, you give each pin a name that gives you a hint of its

    function.  Usually it's best to use whatever name the datasheet uses so

    people can clearly relate pins in your schematic to things described in the

    datasheet.  In the device editor, you use the connect dialog to define the

    binding between the logical pin names from the symbol and the physical pad

    names from the device.  Your problem is you forgot to set the pad names in

    the package so they are still the P$xx defaults.

    --

    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
  • e14 Contributor
    e14 Contributor over 14 years ago in reply to e14 Contributor

    Thanks you sir, that was it image

     

    Olin wrote on Tue, 20 March 2012 12:11

    Oops, I should have said "package" instead of "symbol".  When you make

    the package, you need to give each pad a name that will make sense when

    you go to make the connection between the symbol and package in the

    device editor.  For IC packages, these would usually be pin numbers

    starting at 1.  When you make the symbol, you give each pin a name that

    gives you a hint of its function.  Usually it's best to use whatever name

    the datasheet uses so people can clearly relate pins in your schematic to

    things described in the datasheet.  In the device editor, you use the

    connect dialog to define the binding between the logical pin names from

    the symbol and the physical pad names from the device.  Your problem is

    you forgot to set the pad names in the package so they are still the P$xx

    defaults.

     

     

    --

    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
  • e14 Contributor
    e14 Contributor over 14 years ago in reply to e14 Contributor

    Thanks you sir, that was it image

     

    Olin wrote on Tue, 20 March 2012 12:11

    Oops, I should have said "package" instead of "symbol".  When you make

    the package, you need to give each pad a name that will make sense when

    you go to make the connection between the symbol and package in the

    device editor.  For IC packages, these would usually be pin numbers

    starting at 1.  When you make the symbol, you give each pin a name that

    gives you a hint of its function.  Usually it's best to use whatever name

    the datasheet uses so people can clearly relate pins in your schematic to

    things described in the datasheet.  In the device editor, you use the

    connect dialog to define the binding between the logical pin names from

    the symbol and the physical pad names from the device.  Your problem is

    you forgot to set the pad names in the package so they are still the P$xx

    defaults.

     

     

    --

    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.

Follow element14

  • X
  • Facebook
  • linkedin
  • YouTube