• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. PCB Design
  3. Best practices for schematic pins connected to multiple...

Stats

  • Locked Locked
  • Replies 8
  • Subscribers 164
  • Views 18181
  • Members are here 0
More Content
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Best practices for schematic pins connected to multiple package pins

archive
archive over 19 years ago

I am new to Cadence SPB/Allegro, so there may be something simple I'm missing.
I am trying to set up some basic library components, such as an LM317 regulator.  The regulator comes in two styles we may use, a TO220 with 4 pins (3 pins and the heatsink), and a D-PAK with 3 pins.  In the TO220 package, pins 2 and 4 (the heatsink) are the same.  I want a schematic symbol with 3 pins connected to both possible footprints.

In Part Developer, I can only connect a schematic pin to multiple footprint pins if I set it as a global pin, but then, as far as I can tell, I can't make it show up in the schematic symbol.  Alternatively, I can create a footprint with the same pin number for pin 2 and the heatsink (maybe?), but then I can't reuse the footprint between components. 

Is there a better solution I'm missing?


Originally posted in cdnusers.org by colincross
  • Cancel
  • archive
    archive over 19 years ago

    If I understand what you need, you wish to short pins 2 & 4 on the
    footprint to a single pin on the schematic device.

    Please review the attached document and see if this helps.

    Essentially, you'll be adding a PACK_SHORT property to the symbol.


    Jerry


    Originally posted in cdnusers.org by geraldg
    multipin.doc
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • archive
    archive over 19 years ago

    You may also consider the SourceLink Solution# 1816165


    Jerry


    Originally posted in cdnusers.org by geraldg
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • archive
    archive over 19 years ago

    Posted By geraldg on 3/22/2006 5:27 PM
    You may also consider the SourceLink Solution# 1816165

    Jerry
    Sorry - Please use this SourceLink direct link for Solution# 1816165

    http://sourcelink.cadence.com/docs/db/kdb/1998/July/1816165.html

    Jerry


    Originally posted in cdnusers.org by geraldg
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • archive
    archive over 19 years ago

    Thanks for the link, it solves half my problem.
    However, the result of following the instructions is to create a symbol that looks like it has only 3 pins, but actually has 4, which can then be associated with a footprint with 4 pins.  The resulting symbol then cannot be used with a 3 terminal footprint.  Is there any way to create a single, 3 pin transistor symbol that could allow either a 3 pin SOT-23 footprint or a 4 pin TO220 footprint to be chosen from a part table file, or do I have to suck it up and make two parts in my library?


    Originally posted in cdnusers.org by colincross
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • archive
    archive over 19 years ago

    Well ... from what you're trying to accomplish, this cannot even be considered
    an asymmetrical part. Since you needed to match either a 3 --or-- 4 pin
    physical package, the cleanest method would be to make 2 different components
    and reference their respective JEDEC_TYPE values for the footprints via the
    PTF files.

    Jerry


    Originally posted in cdnusers.org by geraldg
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
>
Cadence Guidelines

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information