• 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. *Error* dbTransformPoint: Invalid point - nil

Stats

  • Locked Locked
  • Replies 10
  • Subscribers 144
  • Views 4380
  • 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

*Error* dbTransformPoint: Invalid point - nil

Reinice
Reinice over 13 years ago

Hi All,

I want to get the points of a terminal(a "polygon" object type) pins(e.g. PLUS-MINUS, E-B-C) from a schematic symbol

Here is my script:

foreach( cell ddGetObj("QCBGB7_09T")~>cells

cvId=dbOpenCellViewByType("QCBGB7_09T" cell~>name "schematic" "schematic" "a")

foreach(inst cvId~>instances

if(inst~>cellName=="ndio" then

when(inst~>purpose == "cell"

foreach(insTerm inst~>insTerms

insTermPntsO=car(insTerm~>terms~>pins~>fig~>points)

ll=nth(0 insTermPntsO)

ur=nth(2 insTermPntsO)

tform=inst~>transform

;;transform ll=lower right and ur=upper right points of a symbol

insTermPntLL=dbTransformPoint(ll tform)

insTermPntUR=dbTransformPoint(ur tform)

);end of foreach

);end of when

);end of if

);end of foreach

);end of foreach

I' am having this error everytime I run this script for the "ndio" schematic symbol. By the way "ndio" is a symbol_xform(symbol pcell)

*Error* dbTransformPoint: Invalid point - nil

But if I use the script first time for other symbol such as pnp, for once I 'am not encountering this error. By the way "pnp" is also a symbol_xform(symbol pcell)

After I run the script again for pnp I' am encountering the same error.

Please correct the wrong part of my script.

Can anyone help me. It will be highly appreciated if anyone can help.

Thank You Very Much in advance.

Thanks and Regards,

Reinice

  • Cancel
Parents
  • Reinice
    Reinice over 13 years ago

    Hi Marcel,

    Yup, your right the inst~>xy does the job. I' am getting the origin of my instance schematic. It's just a flow issue on my real code. Thanks. = )

    Hi Andrew,

    On the starting code that you gave to me before(forum #1313594)

    1. Is there a way to make placement of new instance(new process) in the center and not depending on pinOrigin from the config.file?

    2. How can I modify the code for me to migrate also other cellview other than the curent open cellview without opening them all?

    When I migrate old instance that have connection to wire on the edge of it's terminal box, it is left hang and not connected when replaced by the new instance. 

    3. How can I wire the new instance(new process) in the middle on each of it's terminal if it's counter part old instance(old process) was wired on the edge on each of it's terminal box?

    Thank you very much in advance.

    Thanks and Regards,

    Reinice

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Reinice
    Reinice over 13 years ago

    Hi Marcel,

    Yup, your right the inst~>xy does the job. I' am getting the origin of my instance schematic. It's just a flow issue on my real code. Thanks. = )

    Hi Andrew,

    On the starting code that you gave to me before(forum #1313594)

    1. Is there a way to make placement of new instance(new process) in the center and not depending on pinOrigin from the config.file?

    2. How can I modify the code for me to migrate also other cellview other than the curent open cellview without opening them all?

    When I migrate old instance that have connection to wire on the edge of it's terminal box, it is left hang and not connected when replaced by the new instance. 

    3. How can I wire the new instance(new process) in the middle on each of it's terminal if it's counter part old instance(old process) was wired on the edge on each of it's terminal box?

    Thank you very much in advance.

    Thanks and Regards,

    Reinice

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
No Data

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