• 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. Digital Implementation
  3. createPGPin replacement?

Stats

  • Locked Locked
  • Replies 2
  • Subscribers 91
  • Views 13020
  • Members are here 0
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

createPGPin replacement?

jgentry
jgentry over 15 years ago

I've been using the createPGPin command to model our boundary-edge via-array via-enclosure metal as PG pins.  This works great in 8.* but is REALLY slow in 7.1.  Because of the way our licensing system is setup, it is prefered that we use 7.1 as we have many more licenses there.  Any alternatives to createPGPin?

  • Cancel
  • BobD
    BobD over 15 years ago

    I checked with R&D and unfortunately we don't have a way besides createPGPin and defIn to create PG pins.  And as you're aware defIn is non-incremental for PG pins so you need to capture all of the PG pins in a def to use that as a workaround.

    createPGPin was a big breakthrough because the only way we used to be able to create them was to defIn a floorplan that had them already or create them as part of the PG striping process.  Too bad it was slow in 7.1- hope you can find a solution you can use between 8.1 and/or defIn.  Let me know if you have any other questions on this.

    Thanks for your participation in the forums- we appreciate it.

    -Bob

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • jgentry
    jgentry over 15 years ago

     I kind of expected that.  Rarely does someone create two commands that do the exact same thing although some times there is a user-friendly command (i.e. without 'db' on the front) and also a 'db' version.  Oh well, I have code around that duplicates the existing pins in DEF form so this shouldn't be an issue.

    Thanks for checking,
    JG

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel

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