• 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. Custom IC SKILL
  3. How to change the origin of the selection point when instantiating...

Stats

  • Locked Locked
  • Replies 4
  • Subscribers 143
  • Views 15860
  • 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

How to change the origin of the selection point when instantiating custom symbols

LuisGutierrez
LuisGutierrez over 7 years ago

Hi all,

I'm using IC6.1.7-64b.500.15

Maybe this is a silly question, but I haven't found a solution for this yet. I'm trying to instantiate a custom border sheet (but it happens with any symbol, really) and the origin of the instantiation is far away from the symbol itself (see screenshot). How can I edit this such that the symbol is handled from its bottom left corner when instantiated? Sometimes when doing a fit in the schematic I find random instances lying around because of this issue.

Regards,

  • Cancel
Parents
  • Andrew Beckett
    Andrew Beckett over 7 years ago

    Did you try opening the symbol (or sheet itself) and doing Edit->Origin to move the origin of that component to where it makes more sense?

    It's a bit odd why you have this problem though. You need to be aware that changing the origin of the component would affect any existing instantiations of the component/sheet.

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Andrew Beckett
    Andrew Beckett over 7 years ago

    Did you try opening the symbol (or sheet itself) and doing Edit->Origin to move the origin of that component to where it makes more sense?

    It's a bit odd why you have this problem though. You need to be aware that changing the origin of the component would affect any existing instantiations of the component/sheet.

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
  • LuisGutierrez
    LuisGutierrez over 7 years ago in reply to Andrew Beckett

    Hi Andrew,

    Thanks for the answer. I fixed it using edit > origin. Question: How is the origin first defined in a symbol? I simply created the custom border sheet and first time I tried to instantiate it was already being handled from afar. Maybe a skill script triggered at check and save of the symbol that locates the origin to the bottom left of the bounding box is possible?

    Regards,

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 7 years ago in reply to LuisGutierrez

    Luis,

    The trouble is that people often don't have the coordinates or axes shown in the schematic/symbol editor. These can be enabled via the Options->Display Options form. This isn't normally an issue because people usually start symbols from an existing symbol or using the Create->CellView from CellView forms which do pick one of the pins to be the origin. I can only imagine that you must have deleted all the contents and started drawing in free space? Or accidentally moved everything by an offset? It's not a problem I hear users complaining about in general, so I think it must be related to however you've edited them (or possibly something odd in your environment - but this seems less likely).

    Whilst it would be possible to have a save trigger to update the origin automatically, I think that could be rather dangerous if ever you've intentionally moved the origin to a more desirable location; it would affect any existing placements.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • LuisGutierrez
    LuisGutierrez over 7 years ago in reply to Andrew Beckett

    Hi Andrew,

    Thanks for the comments and extra hints. Definitely it makes more sense to have the sort of freedom for the origin definition the way you indicate.

    Regards,

    • 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