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 want to use an Infineon CoolMOS in a medium/high power switching application. The chip of choise is the IPD60R600E6. The spice model can be found here:
I copied the source code from the file to a new .spi file. Then i added a new Item to my schematic, a nmos4 from the analogLib. I changed the model name to IPD60R600E6 an added the spice file to the library list.
Then i changed the pin setup in the spice file to
.SUBCKT IPD60R600E6_L0 source gate bulk drain
because in the nmos4 lib it says that Source is pin 1, Gate is pin 2 etc. The bulk contact in the spice file is not connected because in the spice model it is connected to source.
Plotting the transfer characteristic i get far too high currents in the range of kA. Even with Vgs = 1V the transistor seems to conduct with the same current... (Vth>= 2.1V)
Any idea what i did wong? Is it the correct way to use a analogLib nmos4 and change the model name? I did the same with a IRF430 MOSFET and this worked without a problem.
Thanks in advance!
In reply to oldmouldy:
Hi, thanks for your response!
oldmouldy[...]I just used the LIB file "as is", created "default rectangular" parts and wired up a trivial test circuit[...]
What do you mean with "default rectangular"parts? Could you describe what you did to make it work?
What i did was not using the import wizard because it fails with unknown model parameters for the MOSFETs (after creating a portmap for all unknown devices). I just used a standard NMOS from the analogLib and changed the model name to the one in the spice file. This is what i also did with a IRF430 spice file and this worked out very well. Using the same pin mapping on the CoolMOS model it did not work. The plot of the transfer characteristics has nearly the right form but the current is in the order of 25 to 75 uA (DC Sweep over Vds from 0V to 500V, Vgs = 5V = const.).
In reply to Elektrofreak:
Use the Model Editor, under PSpice Accessories in the product Program Group. Save the original model LIB file to a convenient location, File>Open in the Model Editor to open the LIB file, File>Save to write the PSpice formatting, File>Export to Capture Part Library, this will create an OLB file to use in Capture to place the parts in the schematic, these parts will have a "default rectangular" appearance for the subcircuit defined parts like the one that you are using. Since the model pins are named Source, Gate, Drain they should be readily identified for connecting.
Another issue may well be that the IRF430 is defined as a Model, .model statement for the LIB definition and the part that you are trying to use is defined as a Sub-circuit, .subckt statement for the LIB definition. This will need a change to the PSpice Template from M^@REFDES ... for the mosfet model to X^@REFDES ... for a subcircuit. (If you create the "default" Capture symbol, you will see the PSpice Template definition for that graphical symbol in the properties.)