• 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. Orcad netlist error caused by duplicated pin name

Stats

  • Locked Locked
  • Replies 4
  • Subscribers 168
  • Views 26240
  • 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

Orcad netlist error caused by duplicated pin name

kevinwinder
kevinwinder over 9 years ago

Some old orcad allows duplicated pin name on lib. but the newer orcad does not.

It is very time consuming the pin name one by one.

Is there any way to ignore the duplicate pin errors?    

Any other method is welcome

  • Cancel
  • steve
    steve over 9 years ago
    Most duplicates are Power and Ground pins so if you set the Pin Type correctly to be Power and you won't see this error. For NC pins instead of adding them to the symbol add them as a property name NC value a comma separated list of the NC pins 1,6,9,10 etc. The rest you will need to fix. There is a command under Accessories - Library Correction Utility that will fix the libraries and add a #pin number to each pin name if you don't want to do it yourself.
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • kevinwinder
    kevinwinder over 9 years ago
    Hi, tried that utility but no luck, it said no duplicated pin part was found. It seems bug s on this utility.
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Quantum7
    Quantum7 over 8 years ago
    this is really undesirable and bad. If I do for example USB Jack symbol with two pin names named "D+" but different pin numbers, why would CAD tool prohibit me from doing this?

    Developers should fix this ASAP. Duplicated Pin *NAMES* should be allowed, I am ok with no duplicate pin *NUMBERS* being allowed, but what's wrong with having same pin names? I need duplicated pin names with "Passive" property!
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • UlfK
    UlfK over 8 years ago
    There is a lot of fancy tricks like duplicating pins and adding various properties to the schematic symbols.
    I have however experienced problems with approaches like this. Sooner or later, there will be
    mistakes made in the mapping between schematic symbols and footprints shared by other symbols.

    OrCAD Capture is not always very detailed when a net list generation has failed.

    So in order to avoid possible mistakes, I never hide pins. I always make schematic symbols
    with == number of pins compared to the footprint. Typical examples are TO220 (tab and one the pins
    share the same net). NC-pins are designated NC1, NC2, NC3, etc. Large BGA's wit a lot of NC-pins
    are created as fractured symbols with NC-blocks.

    I create schematic symbols like diodes with pins "A" and "C" and map them to corresponding
    footprints with pins named like that.

    I even create fiducials and mounting holes
    as schematic symbols. Then place them on the last page.

    It is a primitive approach and it does not look nice. I agree on that, but: If these things are visible in the schematic and that schematic is subject
    to a thorough review before going to layout, the risk is minimized that things are forgotten and there is no need
    for detailed check-lists.

    My 5 cents.
    • 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