• 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. Allegro X Capture CIS
  3. Editing the schematic symbol part properties using the TCL...

Stats

  • State Verified Answer
  • Replies 7
  • Subscribers 43
  • Views 6269
  • Members are here 0
More Content

Editing the schematic symbol part properties using the TCL command in OrCAD Capture

RohitRohan
RohitRohan over 1 year ago

Hai Community,

I want to copy all the values of one property tab to another property tab using the TCL command in the Capture.

For example, in the below image, there is PCB Footprint value property defined for all the schematic symbols, also there is PCB_FP properties for which values are blank for all the schematic symbols.

Can i use the TCL command such that all the values of PCB Footprint property will be transfer or copied to PCB_FP property for all schematic symbols.

For reference, Once the TCL command executed / completed, below is how it should look like after execution  (Note: In the below image the values are edited using Microsoft paint and not using the OrCAD Capture, (Edited image))

Regards,

Rohit Rohan

  • Sign in to reply
  • Cancel
  • RohitRohan
    0 RohitRohan over 1 year ago in reply to CadAP

    Hai CadAP,

    Thank you so much for the previous TCL code and I really appreciate it. Slight smile

    Currently I have an very urgent requirement, I have a schematic symbol of 100 pins, the problem is all the 100 pins are having the same pin name which is "Vss", when I create netlist from the schematic it creates an error stating that pin names are duplicated, I have disabled the DRC check for duplicate pin names but still the same problem.

    Is it possible to create a TCL command such that I want to change the Pins names of the schematic symbol in sequence order, like the schematic symbol has 100 pins with all being Vss, I want to make them like Vss1 to Vss100 using the TCL command. 

    Regards,

    Rohit Rohan

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • CadAP
    +1 CadAP over 1 year ago in reply to RohitRohan

    Hi Rohit Rohan,

    Please find the tcl for changing the selected Part pin name from VSS to Vss$Pin_Number.

    For example,

              If a part has the pin name VSS and the same pin has pin number 1, then the new pin name will be VSS1.

    set lStatus [DboState]
    set lInst [GetSelectedObjects]

    set lPlacedInst [DboPartInstToDboPlacedInst $lInst]
    #Get DboLibPart from the Placed Inst
    set lPart [$lPlacedInst GetPart $lStatus]
    set lIter [$lPart NewPinsIter $lStatus]
    set lNullObj NULL
    set lPinNameCS [DboTclHelper_sMakeCString]
    set lPinNumberCS [DboTclHelper_sMakeCString]
    #get the first pin of the part
    set lPin [$lIter NextPin $lStatus]
    while {$lPin !=$lNullObj } {
    $lPin GetPinName $lPinNameCS
    set lPinName "[DboTclHelper_sGetConstCharPtr $lPinNameCS]"
    # puts $lPinPos
    if {$lPinName == "VSS"} {
    set lPinPos [$lPin GetPinPosition $lStatus]
    set lNewPinPos [expr {$lPinPos + 1}]
    set lNewPinName "$lPinName$lNewPinPos"
    set lNewPinNameCS [DboTclHelper_sMakeCString "$lNewPinName"]
    set lStatus [$lPin SetPinName $lNewPinNameCS]
    if {[$lStatus OK] != 1} {
    puts "Error in changing the pin name of $lNewPinName"

    }
    }
    #get the next pin of the part
    set lPin [$lIter NextPin $lStatus]
    }
    $lStatus -delete
    delete_DboSymbolPinsIter $lIter

    Hope this will address your current concern and let you move forward in your design process.

    • Cancel
    • Vote Up +1 Vote Down
    • Sign in to reply
    • Reject Answer
    • Cancel
<
Cadence Guidelines

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