Stats

  • Locked Locked
  • Replies 8
  • Subscribers 63
  • Views 26920
  • 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

Transient Simulation with NPORT from analogLib

Amit221

I am using ICADV12.3-64b.500.11.

I have simulated a set of interconnects in ADS Momentum. I have then saved the S-parameter data into a ".snp" file using ADS' "Data File Tool" Option. I have added a part of the file which shows that there are 12 ports.

Now I use the nportcomponent from "analogLib" to perform a transient simulation with this data. 

But I keep on getting this error that netlisting failed because of a non-existent terminal 'common'. See image below.

I dont understand where this terminal is, because if you check my snp file there is no 'common' terminal there either. So i dnt know what this error means. Can anyone shed some light on this? I am attaching the images below.

Parents
  • Andrew Beckett

    My guess is that you're not using a Cadence version of analogLib, but one that has been adapted for another simulator (you may even be using a different simulator - you didn't say). The reason I suspect this is because the nport form doesn't look like it normally does nowadays - it usually looks like this (and has done for some time - your version is recent enough):

    Can you go to analogLib in the library manager, and do Right Mouse->Properties over the name of the library and check the read path. It should be coming from within the ICADV123 installation. Maybe it has been generated via some script which updates the CDF to suit another simulator, and this has messed up the CDF so that it doesn't match the device? Normally the nport has a common reference node (at the bottom) and then each port terminal is single ended rather than differential - it looks as if you have a different (non-standard) netlisting procedure which doesn't know how to deal with this - or your nport doesn't have that pin, and it's confused.

    Anyway, I'd start with checking whether you have a non-Cadence analogLib in your cds.lib.

    Regards,

    Andrew.

  • Amit221
    in reply to Andrew Beckett

    Andrew,

    As always you figured it out at first shot. We had the following readpath in our cds.lib. I dnt know why.

    /data/cad/Cadence/IC6/615_HF506/tools/dfII/etc/cdslib/artist/analogLib

    Is this the old analogLib?

    So thats why I didnt see a common terminal and also my input ports were all differential. And to answer your question, I am using ADE L for my simulations.

    Now we have changed it to the path you mentioned, in our ICADV installation and that error is gone.

    Thanks a lot for your help and support. I am not sure what we would do without this forum and especially you.

    Thanks for making our lives easier.

    Have a nice day.

    Regards,

    Amit

  • Andrew Beckett
    in reply to Amit221

    Hi Amit,

    Yes, it's an old analogLib - not one for a different simulator, just one from an old IC version. The netlist procedure used comes with the IC tools themselves, so clearly there's an inconsistency between the symbol/CDF and the netlist procedure.

    Anyway, glad it's solved and happy to help!

    Regards,

    Andrew.

Reply
  • Andrew Beckett
    in reply to Amit221

    Hi Amit,

    Yes, it's an old analogLib - not one for a different simulator, just one from an old IC version. The netlist procedure used comes with the IC tools themselves, so clearly there's an inconsistency between the symbol/CDF and the netlist procedure.

    Anyway, glad it's solved and happy to help!

    Regards,

    Andrew.

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.