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.
I am investigating adding PSpice modeling capability to existing CIS library database. The best way I have seen it so far, is to obtain or create a PSpice model .lib or other ascii, and use that to create a symbol. Then basically place the symbol and copy the PSpice Template string to our existing library part. The existing library part would then need a couple of additional properties that are called out in the PSpice template string, as well as the "Implementation", and "Implementation Type" property's.
So here's my question, does anyone have any experience doing something like this, and know of a different way to do this? Can the Ascii pspice file / .lib be compressed to the "PSpice Template" string in any other fashion?
Maybe, but probably not...
If you create a Capture symbol from a PSpice subcircuit, the pins will be named after the node names in the .SUBCKT statement, these are unlikely to match your actual graphical circuit symbol pin names.
Take a typical op-amp:
.SUBCKT OPAMP 1 2 49 50 99
The PSpiceTemplate will reflect the node names:- X^@REFDES %1 %2 %49 %50 %99 @MODEL
You part will likely have pin names of + / - / V+ / V- / OUT, this will require the PSpiceTemplate to be:- X^@REFDES %+ %- %V+ %V- %OUT @MODEL
So simply copying the PSpiceTemplate automatically created by the Model Editor is not likely to work. Having said that, a typical 5-pin op-amp only needs one graphical symbol for all parts, the PSpiceTemplate property is set in the graphical library and the Implementation stored in the Database is set to "Transfer to Design", this will apply to many common parts that are needed for PSpice simulations.
You don't want to put the Model data anywhere the database, the simulator needs to find the LIB file data when it runs, otherwise you will see "... missing definition for ..." messages when trying to create a netlist for simulation.
I agree with Oldmouldy, I think approach suggested by you would not work. If you can do the reverse, where you use the symbol generated for PSpice Model instead of one from existing library by adding additional properties, that is likely to work. Not sure if this is a viable route. PSpiceTemplate need to be in agreement with Symbol and OldMouldy has described this well.