• 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. List ambigous parts in tcl

Stats

  • Locked Locked
  • Replies 4
  • Subscribers 166
  • Views 13905
  • 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

List ambigous parts in tcl

fsdb
fsdb over 8 years ago

For BOM generation I need to check if a BOM has ambiguous parts.

I have found no tcl examples for this.

How can I do this?

I only need to know if the there is an ambiguity, I don't need the affected parts.

  • Cancel
  • oldmouldy
    oldmouldy over 8 years ago
    TCL is general purpose programming language, to which has been added specific library functions to manipulate Capture objects, for example. A BOM is just a text file output, you could use TCL to manipulate a text file but there are probably better ways to do that. If you want to use the Capture TCL functions to inspect the Part properties in Capture that might form the BOM output, that would be a potential application of the Capture TCL API, the next thing to identify is what might constitute an ambiguity?
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • fsdb
    fsdb over 8 years ago

    Using the Capture TCL API is exacly what im I want to do.

    If a part is not defined in a BOM Variant then I get this:

    I need to detect if there is such an ambiguity, else I get a wrong BOM.

    All Capture TCL API commands I found do not work.

    Thanks to the great documentation with perfect explanation of the parameters you can only guess what the functions expect as valid input.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • oldmouldy
    oldmouldy over 8 years ago
    Good luck trying to get into the variant data and uncover what is within. In this case, with a little effort, you can change things around and "never" encounter this issue again. The way to organise your Variants is with subgroups within groups. Once you have all of you Variant Parts in groups and subgroups, you can set the fitted / not fitted / different value within the subgroups and then combine the "common" and subgroups into your variant and never see the "ambiguous" message again.
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • fsdb
    fsdb over 8 years ago
    I already have the components in groups and subgroups, but sometimes it happens that a component is added to two groups accidentally.
    Since I can now create all documentation and data for manufacturing with only one click I would like to check, if there is an error and output a warning.
    I don't open the part manager an create all BOMs manually anymore, so I don't see these information and I have to obtain it in another way.
    • 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