• 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. PCB Design
  3. Tcl script, for library manipulation

Stats

  • Locked Locked
  • Replies 13
  • Subscribers 165
  • Views 20216
  • Members are here 0
More Content
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

Tcl script, for library manipulation

nandikkara
nandikkara over 8 years ago

Hi all,

I am trying to use CapLibPropUtil.tcl script in the tools/capture/tcl folder. But the parameters are vague. In the add property command the parameter "Olb path" is ok. But what is the "log file path"and "force" parameters..????.

And also i tried to read the script andtcl guide but i didnt understand the concept. Can any also tell me what this command means

"Set lstatus [Dbostate]"  Dbostate means?.  

Hope helping hands :)

Thanks in advance

  • Cancel
  • oldmouldy
    oldmouldy over 8 years ago
    How about a log file of you changes and what you want to do if the Property already exists? DboState returns success / failure, you will see DboState used to track status in any of the supplied examples.
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • nandikkara
    nandikkara over 8 years ago

    thanks for the reply :)
    Also there was a parameter called <?force>  what is this and i want to know what these database functions returns....

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • oldmouldy
    oldmouldy over 8 years ago
    Force: what you want to do if the Property already exists. The Database TCL routines are all documented in the PDF in tools\Capture\tclscripts in the product installation. Strictly speaking, all TCL functions handle "text", the "text" values can contain references to objects and that is how it is possible to handle objects when "text" is the only "type".
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • nandikkara
    nandikkara over 8 years ago
    Thank you oldmouldy :)

    the drawback of this PDF is, they never explains any script. therefore cant get an idea.if you're so kind, one last question,two lines from script" adding property to schematics"
    Set lstatus [Dbostate]
    set pPartInstsIter [$pPage NewPartInstsIter $lStatus]
    set pInst [$pPartInstsIter NextPartInst $lStatus]

    if you are so kind,can you please explain these above two lines. inferences of mine,
    1. a variable called pPartInstsIter is set by value obtained by executing NewPartInstsIter with parameters pPage and lStatus.
    2. second one is same like this. i understood two commands seperately.what is the logic here? what contains (the value) inside pPartInstsIter, pInst ,lstatus. all contains text!!!??..

    thanks for all support.
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • oldmouldy
    oldmouldy over 8 years ago
    See page 29 and on in the PDF for reference iterating over the design and the previous section on "how TCL works". These three lines start with getting a reference to DboState, this needs to get passed to return the Status, the next line gets a reference to a NewPartInstIter, a function to iterate over all of the Part Instances, in this case on a Page because a reference to a Page was also passed, the next line gets reference to a Part Instance from the NextPartInst function from the NewPartInstsIter and also gets the Status reference passed. Probably the next thing to check is that the "pInst" returned isn't "null" as that would indicate the end of the Part Insts iteration, assuming that the "pInst" is valid, operations could be invoked using the Part Inst.
    • Cancel
    • Vote Up 0 Vote Down
    • 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