Stats

  • Locked Locked
  • Replies 18
  • Subscribers 128
  • Views 34359
  • 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

Schematic Probe highlight thickness

acook
I am trying to do something like CCR 1844262. I have a common SKILL file designers in my group load and I would like to implement changing the probe width there (if that is even the best way to do it).

Changing the default display.drf in the cadence install directory is not an option.

I could not find anything on how to change display settings using only SKILL and not a drf.
Parents

  • What do you get if you type these commands in the CIW:

    envGetVal("schematic" "probeHiliteLppList")
    envGetVal("schematic" "probeHiliteLppString")

    Note that the default graphic editor sets the equivalent variables to the "hilite" layers (hilite/drawing, hilite/drawing1, hilite/drawing2 etc), but the default for schematic is to set these to y0 to y9.

    The other thing is that the layers maybe y0 to y9, but your technology file may have assigned a different packet name to them. You can find the packet name used with this SKILL code (make sure your schematic window is the current window before entering this in the CIW):

    techGetLPPacketName(techGetLP(techGetTechFile(geGetEditCellView()) list("y0" "drawing")))

    For one TSMC technology I'm using, this returns "winColor5dashed_LB" whereas for a GPDK-based example it returns "y0". If the packet name is different, you'd have to set that packet rather than the y0 packet.

    Thanks,

    Andrew.

Reply

  • What do you get if you type these commands in the CIW:

    envGetVal("schematic" "probeHiliteLppList")
    envGetVal("schematic" "probeHiliteLppString")

    Note that the default graphic editor sets the equivalent variables to the "hilite" layers (hilite/drawing, hilite/drawing1, hilite/drawing2 etc), but the default for schematic is to set these to y0 to y9.

    The other thing is that the layers maybe y0 to y9, but your technology file may have assigned a different packet name to them. You can find the packet name used with this SKILL code (make sure your schematic window is the current window before entering this in the CIW):

    techGetLPPacketName(techGetLP(techGetTechFile(geGetEditCellView()) list("y0" "drawing")))

    For one TSMC technology I'm using, this returns "winColor5dashed_LB" whereas for a GPDK-based example it returns "y0". If the packet name is different, you'd have to set that packet rather than the y0 packet.

    Thanks,

    Andrew.

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.