• 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. Allegro Extra pins and Missing Pins

Stats

  • Locked Locked
  • Replies 12
  • Subscribers 168
  • Views 25019
  • 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

Allegro Extra pins and Missing Pins

salasidis
salasidis over 16 years ago

I am new to Allegro, and have a problem with PCB Footprints for certain components.

 

For example,

 

A) one component mounts on a Dip16 footprint, but only has 4 pins (pin 1,8,9,16).

 

B) A diode uses a SOT-23 package with 3 pins, but only 2 pins are required.

 

How does one force Allegro to ignore missing pins in the schematic that are not required (example A).

 

I have "fixed" this by defining in my Orcad CIS part schematic invisible zero length pins that are not required (ie define the other 12 pins in example A, or create a new diode symbol with an extra unused pin.

 

Is there a better way?

 

 

(netrev.lst output below

 

ERROR(SPMHNI-196): Symbol 'SOT65P210X110-3N' for device 'DIODE TS_SOT65P210X110-3N_DISCR' has extra pin '3'.

#2   WARNING(SPMHNI-192): Device/Symbol check warning detected.

ERROR(SPMHNI-196): Symbol 'DIP16' for device 'CPC1945G_DIP16_DISCRETE_CPC1945' has extra pin '2'.

ERROR(SPMHNI-196): Symbol 'DIP16' for device 'CPC1945G_DIP16_DISCRETE_CPC1945' has extra pin '3'.

ERROR(SPMHNI-196): Symbol 'DIP16' for device 'CPC1945G_DIP16_DISCRETE_CPC1945' has extra pin '4'.

ERROR(SPMHNI-196): Symbol 'DIP16' for device 'CPC1945G_DIP16_DISCRETE_CPC1945' has extra pin '5'.

ERROR(SPMHNI-196): Symbol 'DIP16' for device 'CPC1945G_DIP16_DISCRETE_CPC1945' has extra pin '6'.

ERROR(SPMHNI-196): Symbol 'DIP16' for device 'CPC1945G_DIP16_DISCRETE_CPC1945' has extra pin '7'.

ERROR(SPMHNI-196): Symbol 'DIP16' for device 'CPC1945G_DIP16_DISCRETE_CPC1945' has extra pin '9'.

ERROR(SPMHNI-196): Symbol 'DIP16' for device 'CPC1945G_DIP16_DISCRETE_CPC1945' has extra pin '11'.

ERROR(SPMHNI-196): Symbol 'DIP16' for device 'CPC1945G_DIP16_DISCRETE_CPC1945' has extra pin '12'.

ERROR(SPMHNI-196): Symbol 'DIP16' for device 'CPC1945G_DIP16_DISCRETE_CPC1945' has extra pin '13'.

ERROR(SPMHNI-196): Symbol 'DIP16' for device 'CPC1945G_DIP16_DISCRETE_CPC1945' has extra pin '14'.

ERROR(SPMHNI-196): Symbol 'DIP16' for device 'CPC1945G_DIP16_DISCRETE_CPC1945' has extra pin '15'.

  • Cancel
  • tltoth
    tltoth over 16 years ago

    Hi,

    consider this:

    http://www.cadence.com/Community/forums/p/10483/11767.aspx#11767

    regards

    tltoth

    • Cancel
    • Vote Up -1 Vote Down
    • Cancel
  • redwire
    redwire over 16 years ago

    Cadence allows a "NC" property to be added.

    You can do this on a case-by-case basis or modify your global library.  Examples:

    A) NC=2,3,4,5,6,7,10,11,12,13,14,15

    B) NC=2 (because I am assuming pin 1, 3 are in use on the sot23)

     Just add this property to the parts and it will compile just fine.  You don't need to graphically edit the parts the way you were doing.

     

     

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • salasidis
    salasidis over 16 years ago

    Thanks, but could you please tell me where to set the NC propery. I looked within Allegro 'Display' 'Property' but could not find an NC entry.

     

    I would think creating a new footprint with the NC= for the pins not used would be easiest

     

    I tried adding an NC property within the part properties of Capture, but this has not worked, I still get the same netrev.lst message (I tried it for the Dip16 part)

     

    Addendum: I managed to get the DIP16 to work with an NC parameter added to teh capture side (not sure why it did not work the first time).

     However if I try making a new footprint with a DIP16 layout but only 4 pins defined (1,8,10,16) to match the capture, I still get the error message about the missing pins. Do the PCB Footprint pins have to be in a linear order (ie no skipped numbers)

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Cadpro2K
    Cadpro2K over 16 years ago

    Do this all the time in Cadence Capture (was Orcad)

    For your parts, on the schematic side: 1) select the part; 2) Edit properties; 3) add a comment called NC; make the value whatever the pin number is. (e.g. for the diode you'd add a comment called NC with the pin 1 as the value.

    Note: pins should be separated by commas: 1,2,3,4,5

    For the 4 pin IC you'd have NC: 2,3,4,5,6,9,10,11,12,13

    Works well, and is easy to set up.

    Mitch

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • John Davies
    John Davies over 16 years ago

    I'm a little puzzled to know what is precisely the problem. When you say "one component mounts on a Dip16 footprint, but only has 4 pins (pin 1,8,9,16)" do you mean:

    (a) the package has all 16 physical pins but only 4 are used (the other 12 not connected)

    (b) the package has the same outline as a DIP16 but has only 4 physical pins (those at the corners)?

    If it's (a), you should use the usual DIP16 footprint and add the NC property for the unconnected pins in Capture, as has already been explained by Mitch.

    If it's (b), you should edit the footprint in PCB Editor to remove the non-existent pins, save it under a new name, and use this new name for the footprint in Capture. Follow the instructions in algrolibdev, which are clear.(It's easy to make a completely new footprint using the New Symbol Wizard provided that you have identified the padstacks first.)

    I have no idea whether pin number have to be sequential from 1 (1, 2, 3, etc); every package that I have ever used has been numbered this way and I never worried about it! It seems an obvious convention to follow.The pin numbers used by the symbol in Capture must match those on the package used in PCB Editor.

    Good luck, John

    • 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