• 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. Custom IC Design
  3. How to transfer spice model to spectre model

Stats

  • Locked Locked
  • Replies 10
  • Subscribers 126
  • Views 27654
  • Members are here 0
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

How to transfer spice model to spectre model

archive
archive over 15 years ago

I got following spice model for external MOSFET from the vandor, how can I import this into spectre to get the right simulation results.

I added "simulator lang=spice" line at the top, but it doesn't give me the right result.

MODEL REMOVED BY MODERATOR BECAUSE VENDOR MODEL REQUEST PAGE MAKES IT CLEAR THAT THE MODEL MAY NOT BE DISTRIBUTED.

 

  • Cancel
Parents
  • Andrew Beckett
    Andrew Beckett over 11 years ago

    Steve,

    I removed the content of the model file that you posted above; it's NXP's model, so it should not be re-published on this forum.

    The fundamental problem is that it isn't really in SPICE syntax. First of all, there's no .SUBCKT header - I was expecting that there would be something like:

    .SUBCKT JBF862 1 2 3

    at the top. Secondly, there's a bunch of L, R and C components, but no instantiation of the model - it just defines the model. So no transistor instance. And finally it doesn't have a "." before the last line. I'm not that familiar with PSPICE (this may be a PSPICE model), despite it being a Cadence product, and so I tried using the new "pspice_include" statement that is in MMSIM13.1 to see if that helps. It didn't, because even then I would expect it to have a .SUBCKT statement. I suspect this is a file that can be read into Orcad Capture and then used within that environment (again, not my product area).

    So the best bet would probably be to contact customer support so we can explore this together in more detail; you might also need to contact the model vendor for some support.

    Kind Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Andrew Beckett
    Andrew Beckett over 11 years ago

    Steve,

    I removed the content of the model file that you posted above; it's NXP's model, so it should not be re-published on this forum.

    The fundamental problem is that it isn't really in SPICE syntax. First of all, there's no .SUBCKT header - I was expecting that there would be something like:

    .SUBCKT JBF862 1 2 3

    at the top. Secondly, there's a bunch of L, R and C components, but no instantiation of the model - it just defines the model. So no transistor instance. And finally it doesn't have a "." before the last line. I'm not that familiar with PSPICE (this may be a PSPICE model), despite it being a Cadence product, and so I tried using the new "pspice_include" statement that is in MMSIM13.1 to see if that helps. It didn't, because even then I would expect it to have a .SUBCKT statement. I suspect this is a file that can be read into Orcad Capture and then used within that environment (again, not my product area).

    So the best bet would probably be to contact customer support so we can explore this together in more detail; you might also need to contact the model vendor for some support.

    Kind Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
No Data

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