• 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 Design
  3. Change size of all the solder dots in the schematic

Stats

  • Locked Locked
  • Replies 6
  • Subscribers 125
  • Views 18206
  • 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

Change size of all the solder dots in the schematic

bid75
bid75 over 6 years ago

Is there a simple command to reduce the size of all the solder dots in schematic so that the schematic pic captured with "export image" look neater.

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

    This article might help: How to change the size of the solder dot on wire intersections?

    Andrew

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

    This article might help: How to change the size of the solder dot on wire intersections?

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
  • bid75
    bid75 over 6 years ago in reply to Andrew Beckett

    Thanks - that helps. If I may trouble you again, is there a way to reduce the size of terminals which are created by default in a symbol (both standard dir and user created symbols). That fat square terminal really sticks out in a schematic screenshot capture. Bhavin 

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 6 years ago in reply to bid75

    Copy the schSymbolPinMasters (for manual pins) and tsgConnectorMasters (for pins created by create cellView from cellView) variable definitions from <ICinstDir>/tools/dfII/samples/local/schConfig.il into your .cdsinit and change to point at your own pin graphics cellViews (you can copy the originals from basic - e.g. basic/sympin/symbolNN) - you can then change the size of those pins. The "square" entry for tsg is probably the main one to change.

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • bid75
    bid75 over 6 years ago in reply to Andrew Beckett

    I was not able to alter the "square" shape terminal when I copied symbolNN to my own local dir - could find the attributes to change.

    If I edit the above variables and alter the pin shapes, will it alter pre-existing symbols like res, nmos, pmos in analogLib or tsmc libs ? (I require terminal edits only for purpose of capturing neat schematics using "export image" - i.e. all these are temporary changes.)

    Bhavin

    (Virtuoso sub-version  IC6.1.7-64b.500.17)

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 6 years ago in reply to bid75

    To edit it  you would need to go to Options->Display Options and change the snap spacing to (say) 0.00625 (which will be the database resolution of symbol views anyway most likely). Then use the stretch command and do an area select of the edge you wish to just (and repeat for all the edges).

    This will not affect existing symbols, because generally symbols have flat pin shapes in the view and not an instantiation of the  pin (even when new symbols are created, it uses the pin graphic information from views like the one you're editing as a template rather than as an instance).

    You didn't make clear that this was for exporting images. In that case, this approach will not work. One thing you could do (this might not be what you want, but it's a simple thing) is to just make the pins invisible. I suspect however that's not what you want. If you did, you could just use this code: abSetLayerVisible(?layer "pin") or to make it visible again abSetLayerVisible(?layer "pin" ?visible t)

    /* abSetLayerVisible.il
    
    Author     A.D.Beckett
    Group      Custom IC (UK), Cadence Design Systems Ltd.
    Language   SKILL
    Date       May 28, 2019 
    Modified   
    By         
    
    Simple function to change layer visibility
    
    ***************************************************
    
    SCCS Info: @(#) abSetLayerVisible.il 05/28/19.09:30:44 1.1
    
    */
    
    /************************************************************************
    *                                                                       *
    *             abSetLayerVisible(?cv cvId ?layer t_layerName             *
    *              ?purpose "drawing" ?visible nil ?redraw t)               *
    *                                                                       *
    *  Function to simply change the visibility of a layer purpose. Mostly  *
    * created to work with schematic views as can't use leSetLayerVisible.  *
    * cv defaults to current cellView, purpose to "drawing", visible to nil *
    *                            and redraw to t                            *
    *                                                                       *
    ************************************************************************/
    
    procedure(abSetLayerVisible(@key (cv geGetEditCellView()) layer 
            (purpose "drawing") visible (redraw t) "dttgg")
        let((tf lp)
            tf=techGetTechFile(cv)
            lp=techGetLP(tf list(layer purpose))
            destructuringBind(
                    (priority (_visible) (selectable) (contToChg) (drgEnable) (valid))
                    techGetLPAttr(lp)
                techSetLPAttr(lp 
                    list(priority visible selectable contToChg drgEnable valid)
                )
            )
            when(redraw
                hiRedraw()
            )
            t
        )
    )
    

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • bid75
    bid75 over 6 years ago in reply to Andrew Beckett

    That's precisely what I wanted - turning "off" those ugly square terminals. Thanks a ton. 

    • 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