• 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. File Type Clarity - Using Built-in Capture Symbol Models...

Stats

  • Locked Locked
  • Replies 2
  • Subscribers 165
  • Views 1317
  • 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

File Type Clarity - Using Built-in Capture Symbol Models to Create Non-Associated Custom Parts and Software Version Capabilities

Maviday
Maviday over 7 years ago

What I'm trying to do...

      I need to simulate two NMOS transistors each with custom parameters. I would like to have my own Library in which I can build individual non-associated (meaning: if I change the modal name and parameters for one it only applies to that model), custom parts that have functionality and can be used in the same schematic. I've been trying for two days now and have read many articles, but still I don't clearly understand what's going on with all the different file types and  there functionality in the different programs (ie: lite/student versions of Pspice, Capture, Pspice-Model editor).

What I've tried to do so far...

     In Capture I add a part to the screen. Then, I select, right click the part and "Edit Pspice Model".. Then, in Model Editor I try to change the Model Name and a one off "part" the that will be the same king of device in my Schematics but with different parameters and a different model name. I've also tried to open Model Editor on it's own and make a library and add parts but it doesn't recognize the .OLB Breakout files.

What I don't Know...

      I don't know what the difference is between the file types (.LIB .OLB .MOD .OBJ) and I don't understand the association in models and libraries and (you name it). I understand that there maybe can also be different models based on locality, meaning simulation profile specific vs global library vs Schematic and such.

RESTATED. I just want individual N-Channel MOSFETs on the same schematic in Capture, Whose properties can be different (ie LAMBDA, VTO, W, L, ETC.) AND Whose names can be different.

Thank you in advance, to anyone that can help.

  • Cancel
  • Maviday
    Maviday over 7 years ago

    Also I'd like to use the 4 terminal device as well, and this seems to be maybe unavailable to make your own custom variant? 

    • Cancel
    • Vote Up +1 Vote Down
    • Cancel
  • oldmouldy
    oldmouldy over 7 years ago

    There are two libraries in use, the graphical library for Capture, an OLB file containing the parts that are placed in the schematic, and the model simulation library used by the simulator, a LIB file containing "plain" text (for the most part) describing the model. The graphical library and the simulation library are linked by two properties attached to the schematic part, the Implementation - name of the model in the Model library, and the PSpiceTemplate - used to map the Pin Names on the schematic part to the Nodes in the simulation model. IF you place a part from the breakout library, you can use Edit PSpice Model from the pop-up with the part selected, this will create a local library specific to the design with a copy of the default breakout part that can then have the parameters modified and the name of the model changed within the Model Editor. Without a license, the Model Editor only supports creating new Diode models from scratch.

    • 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