Cadence® system design and verification solutions, integrated under our System Development Suite, provide the simulation, acceleration, emulation, and management capabilities.
System Development Suite Related Products A-Z
Cadence® digital design and signoff solutions provide a fast path to design closure and better predictability, helping you meet your power, performance, and area (PPA) targets.
Full-Flow Digital Solution Related Products A-Z
Cadence® custom, analog, and RF design solutions can help you save time by automating many routine tasks, from block-level and mixed-signal simulation to routing and library characterization.
Overview Related Products A-Z
Driving efficiency and accuracy in advanced packaging, system planning, and multi-fabric interoperability, Cadence® package implementation products deliver the automation and accuracy.
Cadence® PCB design solutions enable shorter, more predictable design cycles with greater integration of component design and system-level simulation for a constraint-driven flow.
An open IP platform for you to customize your app-driven SoC design.
Comprehensive solutions and methodologies.
Helping you meet your broader business goals.
A global customer support infrastructure with around-the-clock help.
24/7 Support - Cadence Online Support
Locate the latest software updates, service request, technical documentation, solutions and more in your personalized environment.
Cadence offers various software services for download. This page describes our offerings, including the Allegro FREE Physical Viewer.
Get the most out of your investment in Cadence technologies through a wide range of training offerings.
This course combines our Allegro PCB Editor Basic Techniques, followed by Allegro PCB Editor Intermediate Techniques.
Virtuoso Analog Design Environment Verifier 16.7
Learn learn to perform requirements-driven analog verification using the Virtuoso ADE Verifier tool.
Exchange ideas, news, technical information, and best practices.
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.
It's not all about the technlogy. Here we exchange ideas on the Cadence Academic Network and other subjects of general interest.
Cadence is a leading provider of system design tools, software, IP, and services.
Hello guys ,
I am trying to create a custom OLB file for pspice, for that I start by creating a .lib text file so I can convert it to OLB using the model editor. In the .lib file I type
.model Cbreak CAP C=1 dev=21.19%
so I would have a part named Cbreak, that would as the CAP definition suggests and has a deviation of %21.19 percent. When I turn this part in to a psice olb file and put it on my circuit, it goes back to the original deviation that the "Cbreak" model is defined as.
In order to solve the problem, I rename the part and code it as
.model C_cust CAP C=1 dev=21.19%
and when I do that it cannot simulate the part becuase C_cust model does not exist. I am thinking I need to create models, before I create libraries, before I create OLB files, before I use them in my circuits before I actually simulate them.
I tried the above method with a resistor and an LM117 subckt and always the same result. If you use the .model command, you are stuck with whatever is in that model.
So the question is, how do I create my own custom capacitor or resistor model?
I have asked this question before to other people and the answers I get are always in the form of
Use the model editor
Copy from a previously made library
Export as OLB
These things do not accomplish of creating a "model", but merely have you edit someone elses part. I need to know how to make them from scratch.
If you multiple definition of same models (Cbreak ), simulator would pick up the first one found in search order.
If you create a new Model (C_Cust), you need to make this model definition available to simulator. This can be done by configuring your library file in simulation profile. You can configure this library file as "GLOBAL" : This would make all model available in this new library file to all designs (old as well as new); "Design" : This would make all model available in this new library file available to all simulation profiles associated with that design; "Profile" : This would make all model available in this new library file to that specific simulation profile only.
So you need to perform just one extra step and things should work.
In reply to alokt:
That worked, thank you very much.