• 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. Change NetName

Stats

  • State Not Answered
  • Replies 4
  • Subscribers 43
  • Views 17636
  • Members are here 0
More Content

Change NetName

honey1
honey1 over 10 years ago

I want to change/replace the NetName in the capture design through TCL Script. So far i've been able to change the PinNames of any particular part and the names of OffPageConnectors of whole pages. I am getting the PinName and its corresponding NetName through $lPin. What I actually want to do is to add the PinName to its corresponding NetName with an underscore "_" between them. The Net Name is not being changed but if I try to change/replace the PinName which include the (NetName_PinName) it just works fine.

 

Please give me respective suggestions.

  • Sign in to reply
  • Cancel
  • oldmouldy
    0 oldmouldy over 10 years ago

    You won't be able to change the name of a net in Capture, that's not even possible through the UI. Net Names get overridden with Net Aliases, you should be able change a Net Alias using an AliasIter on DboWire to scan the Aliases and the DboAlias object.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • honey1
    0 honey1 over 10 years ago

    Thanks for your reply but what I actually want to do is to replace the name of a net by its corresponding pin name. I've already mentioned that I am able to change the names of OffPageConnectors of the whole pages. But I just want to pick a particular part and than get the pin name of every pin of that part and than replace the respective nets of those pins. Can we have Pin Name and Net Name through DboWire? The problem is still there,we can not have lWire of any particular part as we can have wires of complete page.

    These are the commands i am using :- 

    set pinName [DboTclHelper_sMakeCString];

    set NetName [DboTclHelper_sMakeCString];

    set NetName [DboPortInst_sGetNetName $lPin $lStatus];

    DboPortInst_GetPinName $lPin $pinName

    set pinName [DboTclHelper_sGetConstCharPtr $pinName];

    set NetName [DboTclHelper_sGetConstCharPtr $NetName];

     

    Now here we can set pin name by  

    DboPortInst_SetPinName $lPin "PinChanged" 

    but couldn't change NetName as it includes $lStatus instead of $NetName as arguments.  

     

    I hope you understand my problem now. 

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • oldmouldy
    0 oldmouldy over 10 years ago

    I don't think that you have appreciated the way that the net name works. The name for a DboWire is assigned by Capture, N<some sequence number> is assigned and that is the Name of the Wire in the Capture DSN data, this can be overridden with a Net Alias, for example; more strictly a "higher order object": Net Alias, or Off-Page Connector, or Hierarchical Port. If the "higher order object(s)" are removed the net will revert to the original, Capture assigned, name. Since you have changed the Port name, the net name in the generated netlist will adopt that, or the highest level the net is named.

    As an aside, if you are doing this for the whole design, how is Net<something> / Pin<somthing else> ever going to connect through the design? Since it seems unlikely that a net of a given name is always going to be connected to a pin of the same number.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • Klaustrafob
    0 Klaustrafob over 5 years ago

    I do a similar task of correction part pin net in the schematic  accordance Altera pin file. There is some implementation github.com/.../pin2part.git

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify 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