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) Tidy schematic after pinswap
  • 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 Verified Answer
  • Replies 12 replies
  • Answers 1 answer
  • Subscribers 191 subscribers
  • Views 2427 views
  • Users 0 members are here
  • pinswap schematic
Related

Tidy schematic after pinswap

alberthall
alberthall over 10 years ago

I am working on a design using a microcontroller using analogue inputs and digital I/O.   The analogue pins can be swapped and the digital pins can be swapped at will (with commensurate changes in the firmware).  I have set the swap levels on the part to allow this.  I put short wires on each pin and named them and did likewise with the parts they connected to.  The parts on the board layout are connected correctly but the layout would be better if some pins were swapped.   So, on the schematic I swap some pins and the board layout correctly reflects the changes.   The problem is that the schematic is now a mess wire wires draped all over the microcontroller.  I tried using Bus/Net but the result is similar.

 

Is there a way of using pinswap without making a mess of the schematic?

  • Sign in to reply
  • Cancel
Parents
  • hanseltime
    0 hanseltime over 8 years ago

    Hey all,

     

       I came across this question and almost lost hope based on the comments.  HOWEVER, there is a work around that will allow for modularity in schematics without changing PCB pad design.  What i wanted was a schematic symbol that I can physically alter the pin arrangement so i don't have a schematics rats nest, all while maintaining the pin-to-pad linking that was there in the first place.

     

       The Solution I have:

      

    1. Create a symbol level pin for the library you are working in.
      1. This is a simple as simply placing a pin and saving it as a generic PIN1
      2. Note: If you want to be able to PIN SWAP STILL you will need to produce a number of pins equal to the number of swappable pins on your final schematic part (i.e. if you expect 36 swappable pins on a part, then that library can have PIN1 -PIN36 defined).  This is because pinswap will not occur if the pins have the same symbol name for a component part.
    2. Create the symbol for the package SANS pins.
      1. This takes a little bit of work on your part to make sure the package is the right size for the size pins you created.
    3. Create a Device
      1. Choose the Package you already have designated for the part you will use
      2. Go to Change-> Add Level (Always), means that every component you add will be placed immediately.  You can look at the other levels if you are interesting in more interesting device placements.
      3. In order to do a gateswap, change the swap level to non-0 in the device creation manager.  Note, this is different than the swap level of the individual PINS you will be adding in regards to pin swapping.
      4. Add+ :
        1. Your Strictly Symbolic Package Body
        2. Each Pin the body should have
          1. Place them according to how you would have if designing the symbol as a single package.  (You can place PIN 1 for all of them if you don't care about pinswapping, or can add different pin symbols for swappability in the future)
          2. Change the NAME of each pin to the PIN number you expect (i.e. 1,2,3, etc.)
      5. Connect the Pins on the Package to the Pins on the Device; the pins will have format {NAME.SchematicPinName}.
    4. In your schematic you may now Place the Device.
      1. Caveats:
        1. Each Pin and the body are now moveable on their own.  To do operations or rotations, use group select and group move or rotate.
        2. If you have not Net connected any pins, a quick way to swap pin orientation is to use GATE SWAP.  Warning:  If you have Connect Pin1 to Vin and Pin 3 to D+, GATE Swap on Pin 1 and 3 will swap the pins on the schematic, but will not maintain the routed connection (i.e. Pin 3 now goes to Vin, and Pin 1 now goes to D+)
        3. If you want to maintain the already routed net, then individually select the pins and reposition them in the schematic.

     

    I hope this helps.  While there are some caveats, this beats having to version name every single pin change if you want to have a nice schematic and useable device!

     

    Let me know if this fails in any ways!

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

    Hey all,

     

       I came across this question and almost lost hope based on the comments.  HOWEVER, there is a work around that will allow for modularity in schematics without changing PCB pad design.  What i wanted was a schematic symbol that I can physically alter the pin arrangement so i don't have a schematics rats nest, all while maintaining the pin-to-pad linking that was there in the first place.

     

       The Solution I have:

      

    1. Create a symbol level pin for the library you are working in.
      1. This is a simple as simply placing a pin and saving it as a generic PIN1
      2. Note: If you want to be able to PIN SWAP STILL you will need to produce a number of pins equal to the number of swappable pins on your final schematic part (i.e. if you expect 36 swappable pins on a part, then that library can have PIN1 -PIN36 defined).  This is because pinswap will not occur if the pins have the same symbol name for a component part.
    2. Create the symbol for the package SANS pins.
      1. This takes a little bit of work on your part to make sure the package is the right size for the size pins you created.
    3. Create a Device
      1. Choose the Package you already have designated for the part you will use
      2. Go to Change-> Add Level (Always), means that every component you add will be placed immediately.  You can look at the other levels if you are interesting in more interesting device placements.
      3. In order to do a gateswap, change the swap level to non-0 in the device creation manager.  Note, this is different than the swap level of the individual PINS you will be adding in regards to pin swapping.
      4. Add+ :
        1. Your Strictly Symbolic Package Body
        2. Each Pin the body should have
          1. Place them according to how you would have if designing the symbol as a single package.  (You can place PIN 1 for all of them if you don't care about pinswapping, or can add different pin symbols for swappability in the future)
          2. Change the NAME of each pin to the PIN number you expect (i.e. 1,2,3, etc.)
      5. Connect the Pins on the Package to the Pins on the Device; the pins will have format {NAME.SchematicPinName}.
    4. In your schematic you may now Place the Device.
      1. Caveats:
        1. Each Pin and the body are now moveable on their own.  To do operations or rotations, use group select and group move or rotate.
        2. If you have not Net connected any pins, a quick way to swap pin orientation is to use GATE SWAP.  Warning:  If you have Connect Pin1 to Vin and Pin 3 to D+, GATE Swap on Pin 1 and 3 will swap the pins on the schematic, but will not maintain the routed connection (i.e. Pin 3 now goes to Vin, and Pin 1 now goes to D+)
        3. If you want to maintain the already routed net, then individually select the pins and reposition them in the schematic.

     

    I hope this helps.  While there are some caveats, this beats having to version name every single pin change if you want to have a nice schematic and useable device!

     

    Let me know if this fails in any ways!

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