• 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. CIS - Multiple symbols per library or single symbol per...

Stats

  • State Not Answered
  • Replies 13
  • Subscribers 45
  • Views 7745
  • Members are here 0
More Content

CIS - Multiple symbols per library or single symbol per library

thomasli
thomasli over 4 years ago

I admit, I do have an Altium background but I'm trying to figure out how CIS exactly works. I figured that it is very similar to Altium's DbLib feature, in fact, they seems pretty much the same. 

I'd like to know what the preferred way to handle schematic symbols is. I have seen that for Allegro PCB it is one footprint per file with the footprint name being the filename without the dra extension. This is also how we did it with Altium. For schematic symbols, I have seen that basically all symbols are stored in a single library file (or some number between 1 and 10) but not one symbol per library file (olb). Back then, we kept one symbol per file to nicely integrate with version control systems. It was always possible to determine when a symbol had been changed (and if).

I am not quite sure yet, how schematic libraries are being found. I found a reference to [Part Library Directories] which contains the location of our 3 library files. Does Orcad browse these libraries? How does that perform for .. say .. 1000 files with one symbol each?

If that is unfeasible, is there another way how to best integrate libraries into a version control system?

  • Sign in to reply
  • Cancel
  • AvengerThanos
    0 AvengerThanos over 4 years ago

    Well, it works in a way how they are defined in the database. You can use 1000 symbols in one lib file / 1 symbol per lib file. 

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • thomasli
    0 thomasli over 4 years ago in reply to AvengerThanos

    As far as I understand, the number of libraries is somewhat unlimited but the main question should be if there is a performance hit involved in having multiple files? From the standpoint of version control the 1 symbol / file strategy would be far better

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • RFinley
    0 RFinley over 4 years ago in reply to thomasli

    Manglement pushes me to "keep it simple" with three libraries covering more than 5 thousand MPNs. 

    I'm in hell.

    Subdividing your libraries saves aggravation.   Even if you have OLB files for passives, mounting/mechanical, op-amps, vregs, and memory/CPUs.  

    Symbol libraries are only accessed when CIS is launched (if you have seen the massive libraries that are included, it's just not a problem.)

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • drobny
    0 drobny over 4 years ago

    Put the full path to the symbol in the database..

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • thomasli
    0 thomasli over 4 years ago in reply to RFinley

    Thank you for the insight.

    • 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