• 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
Parents
  • 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 drobny

    Thank you for the insight. Can you give an example for that? What do you mean by "full path"?

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

    If you have several symbols with the same name in different libraries, Orcad will use the first found symbol.

    It is better to use the full path to the symbol in the database, Orcad will use it from that location.

    for exaple 

    If you want to track changes in libraries and individual symbols, export the symbol from the library to xml.

    Then it is easier to see the changes. You can do this with the TCL and OLB2XML commands and vice versa XML2OLB.
    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • thomasli
    0 thomasli over 4 years ago in reply to drobny

    Thanks, that is great help. The OLB2XML would have been my next question :-)

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

    drobny: I've been trying to locate the OLB2XML and XML2OLB commands but was unable to find them. I was able to create an XML via the File -> Export menu option. Are you aware of a possibility to extract metadata (symbol name, default reference designator, ...) from an OLB file from the command line?

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

    drobny: I've been trying to locate the OLB2XML and XML2OLB commands but was unable to find them. I was able to create an XML via the File -> Export menu option. Are you aware of a possibility to extract metadata (symbol name, default reference designator, ...) from an OLB file from the command line?

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

    Mea culpa! The right command is XMATIC_OLB2XML etc.  Method of the xmatic class.

    The command should be entered in the OrCada window  or selected from the File -> Export menu

    It is possible to run this command from the Windows command line, but not directly... If you want, I can write a console application for you..

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

    drobny Thank you for the offer which I happily accept. Is there some resource which outlines how to run arbitrary scripts from the command line somewhere? Do those need to be run through some tcl/tk interpreter?

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

    What version of a software you have installed - 17.4 or 16.6 ?

    Application Notes  -> c:\Cadence\SPB_17.4\tools\capture\tclscripts\OrCAD_Capture_TclTk_Extensions.pdf

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

    I'm on 17.4. 

    I think I may have used the wrong meaning of command line: What I meant was to run some kind of TCL interpreter/script from the DOS command line, without opening OrCad Capture. The idea is to read all library files and check if certain values are consistent. The further idea would be to run this automatically each night and then come up with a list of things which are not ok in the next morning. I'd like to get some structure into our libraries. 

    • 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