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 create a BUS for a symbol/device?
  • 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 1 reply
  • Subscribers 188 subscribers
  • Views 723 views
  • Users 0 members are here
Related

How to create a BUS for a symbol/device?

ghostfly18
ghostfly18 over 13 years ago

I have 256 pads in package(footprint) with name: A_1, A_2,... A_256.

 

Now I'm creating the symbol for this device, and then want to tie that symbol to the package to create a device.

 

Is there a way to create something like a Bus pin with the name A_<1:256>, so I don't need to put down 256 pins instead? Thanks.

  • Sign in to reply
  • Cancel
  • e14 Contributor
    e14 Contributor over 13 years ago

    Am 27.10.2012 22:46, schrieb Kailiang Chen:

    I have 256 pads in package(footprint) with name: A_1, A_2,... A_256.

     

    Now I'm creating the symbol for this device, and then want to tie that symbol to the package to create a device.

     

    Is there a way to create something like a Bus pin with the name A_<1:256>, so I don't need to put down 256 pins instead? Thanks.

     

     

    No, even if there were a bus someone must define which pin is connected

    to which pad image

    See the help pin before you really go to work on a 256 pin monster.

     

    The symbol you are going to create should contain the pin NAMES and can

    have any form you like. I prefer to draw the symbol pins in a way that

    they best suit the function and NOT like they are arranged on the chip.

     

    The package contains the PADS, either as a SMD-pad or a THT-via and they

    are named from 1 to... .

    You should not use the default values given by eagle (P$x).

    The package of course must be EXACT like the chip you gonna use.

    Eagle contains some already made packages in the ref-packages.lbr, and

    you can check if one suits you.

     

    Now we come to your "buswork". In the CONNECT dialog you must connect

    your pin names to your pad numbers and that can be a lot of work.

     

    Even if that is done you are not finished yet. In the symbol you must

    define the DIRECTION of each pin if you want to benefit from the

    Electrical Rules Check (ERC).

    Turn on layer 93 (pins) to see that.

     

    Last not least there is the VISIBLE parameter for each pin you can play

    with.

     

    A last word on multiple pins like GND etc. Those pins are named like

    GND@1, GND@2 etc. Don't worry, the "@x" will not become visible in your

    device.

     

     

     

    --

    Mit freundlichen Grüßen / With best regards

     

    Joern Paschedag

     

    • 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