• 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. CIS Derive database part Schematic part Libraries

Stats

  • Locked Locked
  • Replies 8
  • Subscribers 165
  • Views 20959
  • 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

CIS Derive database part Schematic part Libraries

Gareth Savage
Gareth Savage over 12 years ago

 Hi all,

Can anyone tell me which sections of the Capture.ini file will populate the "Schematic Part Libraries:" and  the "Schematic Part:" drop down when you attempt a Derive Database Part operation please?

Left Click on Part.

Edit ->Derive Database Part.

Pop-up = "New Database Part"

"Schematic Part" -> Browse  "Schematic Part" and "Scematic Part Libraries" boxes are empty.

"Footprint" -> Browse .... under Footprint dropdown box shows Footprints contained in libraries pointed to by:

[Allegro Footprints]
Dir0=J:\PhysicsandAstronomy\Electronics\ORCAD\Allegro-PCB_Editor\Allegro Footprints

Dir1=J:\PhysicsandAstronomy\Electronics\ORCAD\Allegro-PCB_Editor\Allegro Padstacks

in the Capture.INI file and BackupCaptureCIS.INI

The "Configured Libraries:" box is empty.

 

All very curious, the tools for looking at the ini files seem rather "clunky" to say the least!

 

Many Thanks in advance.

 

Gareth

 

 

  • Cancel
Parents
  • oldmouldy
    oldmouldy over 12 years ago

    You have [Part Library Directories] set, any [Part Selector Configured Libraries] entries will be irrelevant.

    I recommend that you don't get too specific with the Schematic Part location definition in the database. IF you specify the full path and library in the database, the symbol MUST come from that EXACT location, this might be good for quality but it is not very helpful when trying to debug library location issues, or the libraries get moved to another path - the database Schematic Part entries will all have to be changed. I prefer the "just the symbol name", this has the least chance of not being located but it does require a bit of attention to ensure that the same symbol name does not exist in more than one library; if the library names aren't "ever" going to change, you can go with the <library name>\<schematic part> when defining the Schematic Part value in the database, just remember that, if the part is not located within the specified library, CIS won't be able to place the part (reported as "unable to read Part information").

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • oldmouldy
    oldmouldy over 12 years ago

    You have [Part Library Directories] set, any [Part Selector Configured Libraries] entries will be irrelevant.

    I recommend that you don't get too specific with the Schematic Part location definition in the database. IF you specify the full path and library in the database, the symbol MUST come from that EXACT location, this might be good for quality but it is not very helpful when trying to debug library location issues, or the libraries get moved to another path - the database Schematic Part entries will all have to be changed. I prefer the "just the symbol name", this has the least chance of not being located but it does require a bit of attention to ensure that the same symbol name does not exist in more than one library; if the library names aren't "ever" going to change, you can go with the <library name>\<schematic part> when defining the Schematic Part value in the database, just remember that, if the part is not located within the specified library, CIS won't be able to place the part (reported as "unable to read Part information").

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
No Data
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