Stats

  • Locked Locked
  • Replies 8
  • Subscribers 143
  • Views 8644
  • 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

BindKey for probing

ocsav

Hi to all,

I am trying to create a bindkey to use with the letter "W" where it trigger the probe function of the net selected in the schematic to be displayed in the layout and the the "shift W" to remove the probe of the specific net.

The command in the log is this :

_asstSetProbeColor(hiGetCurrentWindow() "y1" "drawing") 

but when I add it to the bindkey editor it returns an error ! 

Can anyone help me with the code for this please.

Thank you and best regards
Vasco

Parents

  • Thank you for the Help, the issue is that I can't script skill code so I'll try to explain the functionality:

    The probing activated with the key 9 is only probing the schematic, not the layout, to make it keep the probe in the layout I have to go to net-> probe and select a color !
    I would like the key 9 and ctrl 9 to keep this schematic-layout correspondence. 

    Please let me know how to write this in the bindkeys saved file directly so I can load it when I start virtuoso.

    thanks a lot.

  • in reply to ocsav

    You could just use:

    geSetCrossProbeValue("schematic" t)

    Then if you press the 9 key in the schematic, it will also cross-probe with the same colour on the layout. Is that what you want?

    If you really wanted to define the bindkey using the private function, you'd add this to your .cdsinit :

    hiSetBindKey("Schematics" "Shift<Key>W" "_asstSetProbeColor(schSingleSelectPt()&&hiGetCurrentWindow() \"y1\" \"drawing\")")

    Regards,

    Andrew

  • in reply to Andrew Beckett

    geSetCrossProbeValue("schematic" t) loaded in the icfb works fine, what an elegant solution !

    Can we do a "remove probe" for the 9 in case is already probed.

    Thank you for the help.

Reply Children

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.