Annotate -> Design">
     
Wednesday, February 08, 2012     Register | Login | Search | Contact Us
     
   
     
     

Many of you already received communications about the move of the Cadence user community into cadence.com. And many of you have already joined, with over 4000 registrations in the first two weeks.

The new Cadence Community enhances the ability of Cadence users to connect and collaborate. In addition to moving the community into cadence.com -- enabling single sign-on for community, Sourcelink and Cadence events -- the new site is organized around nine technology segments, giving you easy access to product information, training, forums and blogs. Some of the new features include:
  • Ability to respond to posts via e-mail
  • Technology-specific blogs
  • Latest Web 2.0 social networking capabilities
  • Public profile options
  • Private messaging
  • Friends lists
Visit the new Cadence Community today at www.cadence.com/community and join the discussions!

Registration note: Due to the scope of the enhancements and the new SSO registration system, we were not able to migrate existing cdnusers.org member accounts. So new registrations are required, but this enables a broader set of functionality we think you'll enjoy.

Forum note: Under the guidance of forum moderators, we have taken the 20+ cdnusers.org forums and consolidated them into 11 forums on the new site. Posts have been brought over so you can leverage that posting history. CDNusers forums will be set to read only starting 7/30, and cdnusers.org will be redirected to the new community on 8/4.

Best regards,
Mike and Tom

Michael A. Catrambone - Steering Committee Chairman
Distinguished Engineer
PCB/Mechanical
UTStarcom, Inc.

Tom Diederich
Cadence Community Manager
Home
Forums
Forums > Custom IC > Shared code - SKILL

Subject: Annotating DC Op Points, etc
Posting to forums is available to community members only.
Login or Register
Rate this topic:
   
Author Messages
rruss
Posts: 1
Online: User is Offline
9/06/2006 1:47 PM  
I would like to create bindkeys for "DC Operating Points" and "Design Defaults" to easily toggle between the displaying DC Node Voltages and Operating points, and the design defaults for devices.

Unfortunately, when I select "Results -> Annotate -> Design Defaults", etc... the ICFB window isn't showing the functions being called.

Can anyone comment on what I what the necessary procedure names are that I need to call?

No need to comment on how to bind to bindkeys, etc.
relyveld
Posts: 0
Online: User is Offline
9/07/2006 12:58 PM  
Hello,

I encountered a similar situation. My problem was to toggle the schematic node information.
First a comment about the ICFB window. Do you know that you can show more log results
in the ICFB window? But even if you know for example the "hiiSetCurrentForm('hiSomeFormName)"
command, and the following commands, repeating them from some function did not
gave me the same result. What I found out is that ICFB behaves differently if commands
are clicked by you or if they are runned from within a function. But when using the load("someFile")
function, it behaves as if you clicked the forms. So what I did, was to save the desired commands to
a file, and load them to 'replay' the form actions. To finish, here is my toggle node info function.
I think you will be able to reuse it yourself.

procedure( wrSchematicNode( @optional value)

let( ( instance wrError)

cv = geGetEditCellView( )
wrError = nil
unless( cv->mode != "r"
wrWindowName( strcat( wrDecodeBindKeysText ": wrSchematicNode: error: cell must be editable"))
wrError = t
)

;; xxx 060516 the cell must be editable. Or a copy of the device must be openend in a
;; dummy view which is editable. It is not that exactly this cell must be editable.

unless( wrError

unless( boundp( 'wrSchematicNodeValueN)
wrSchematicNodeValueN = 0
)

if( ! null( value)
then
wrSchematicNodeValue = value
else
;; 060907 Add "pin name" "net name" "voltage" "current" if you like. Increase the
;; number (now 3) for the modulo operation.
wrSchematicNodeValueList = list( "none" "pin name" "net name")
wrSchematicNodeValueN = modulo( wrSchematicNodeValueN 3)+1
wrSchematicNodeValue = nthelem( wrSchematicNodeValueN wrSchematicNodeValueList )
)
wrWindowName( strcat( wrDecodeBindKeysText ": wrSchematicNode: toggle terminal names: " wrSchematicNodeValue))
wrShFile = outfile(".wrCadenceFile")
fprintf( wrShFile "
\n ;; A device must be selected. If not, select a device.
\n instance = car( geGetSelectedSet( ))
\n if( null( instance)
\n then
\n instance = car( setof( shape cv->instances shape~>libName == wrDeviceLibName))
\n )
\n asaEditCompDisplay( )
\n hiiSetCurrentForm('_ahiiUniqueSymbolformannotateForm0)
\n _ahiiUniqueSymbolformannotateForm0->labelInfo->terminal->value = t
\n geSelectObject( instance)
\n _ahiiUniqueSymbolformannotateForm0->tdisplay->value = wrSchematicNodeValue
\n hiFormDone(_ahiiUniqueSymbolformannotateForm0)")
close( wrShFile)
load( ".wrCadenceFile")
hiRedraw( )
)
)
)

A few extra remarks:
This function is copied from my Cadence customization file. You can find it at
http://relyveld.wordpress.com/cadence-page/
wrDeviceLibName is the name of the attached technology file name.
wrWindowName is a function (part of my wrAltEdit.il file) which prints
status information in the editor window.
Posting to forums is available to community members only.
Login or Register
Forums > Custom IC > Shared code - SKILL > Annotating DC Op Points, etc


ActiveForums 3.6
     
Copyright 2006 Cadence Design Systems, Inc.