Stats

  • Locked Locked
  • Replies 6
  • Subscribers 126
  • Views 16338
  • 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

Unable to plot phase noise

sebastion

Hi,

After running pnoise: jitter analysis, I wanted to plot the phase noise by choosing:

Direct Plot Form => pnoise jitter => Phase Noise => dBc => Plot

I got some error messages shown as follow:

*Error* flip: can't handle flip(nil)
*Error* flip: can't handle flip(nil)
*Error* flip: can't handle flip(nil)
*Error*   Evaluating expression (_drplPmNoise(?modifier "dBc" ?dsb
          t)).
*Error* ("abs" 0 t nil ("*Error* abs: can't handle abs(nil)"))
*Error*   Trying to plot expression <_drplPmNoise(?modifier "dBc"
          ?dsb t)>, which does not evaluate to an object that can be
          plotted, like waveform or parametric wave. Please refer to
          the Wavescan User Guide to see what all types of objects
          can be plotted in Wavescan. Expression which evaluates to
          only those type(s) of objects can be plotted.

I could get the plot when I choose:

 Direct Plot Form => pnoise => Phase Noise => Plot

May I know what is the problem?

 Thanks.

Parents

  • Thanks for the quick reply, Tawna & Andrew.

    Tawna: I am currently using 5.10.41.500.6.138 and I did not use any + or - sign for the nets.

    My setup is shown as follow:

    simulatorOptions options reltol=1e-3 vabstol=1e-6 iabstol=1e-12 temp=65.0 \
        tnom=27 scalem=1.0 scale=1.0 gmin=1e-12 rforce=1 maxnotes=5 maxwarns=5 \
        digits=5 cols=80 pivrel=1e-3 sensfile="../psf/sens.output" \
        checklimitdest=psf
    pss  (  IVCOTOP.cko\<9\>  0  )  pss  fund=2e9  harms=20
    +    errpreset=conservative  tstab=15n  saveinit=no  annotate=status
    +    tstabenvlp=no
    jitter1  (  net23\<5\>  0  )  pnoise  sweeptype=relative
    +       relharmnum=1  start=100k  stop=10M  dec=10  maxsideband=7
    +       annotate=status
    jitter2  (  net23\<5\>  0  )  pnoise  sweeptype=relative
    +       relharmnum=1  start=-(100k)  stop=-(10M)  dec=10  maxsideband=7
    +       noisetype=correlations  cycles=[0  -2]  annotate=status
    modelParameter info what=models where=rawfile
    element info what=inst where=rawfile
    outputParameter info what=output where=rawfile
    designParamVals info what=parameters where=rawfile
    primitives info what=primitives where=rawfile
    subckts info what=subckts  where=rawfile
    saveOptions options save=allpub

    So is it something fixable by upgrading the ISR? Thanks.

Reply

  • Thanks for the quick reply, Tawna & Andrew.

    Tawna: I am currently using 5.10.41.500.6.138 and I did not use any + or - sign for the nets.

    My setup is shown as follow:

    simulatorOptions options reltol=1e-3 vabstol=1e-6 iabstol=1e-12 temp=65.0 \
        tnom=27 scalem=1.0 scale=1.0 gmin=1e-12 rforce=1 maxnotes=5 maxwarns=5 \
        digits=5 cols=80 pivrel=1e-3 sensfile="../psf/sens.output" \
        checklimitdest=psf
    pss  (  IVCOTOP.cko\<9\>  0  )  pss  fund=2e9  harms=20
    +    errpreset=conservative  tstab=15n  saveinit=no  annotate=status
    +    tstabenvlp=no
    jitter1  (  net23\<5\>  0  )  pnoise  sweeptype=relative
    +       relharmnum=1  start=100k  stop=10M  dec=10  maxsideband=7
    +       annotate=status
    jitter2  (  net23\<5\>  0  )  pnoise  sweeptype=relative
    +       relharmnum=1  start=-(100k)  stop=-(10M)  dec=10  maxsideband=7
    +       noisetype=correlations  cycles=[0  -2]  annotate=status
    modelParameter info what=models where=rawfile
    element info what=inst where=rawfile
    outputParameter info what=output where=rawfile
    designParamVals info what=parameters where=rawfile
    primitives info what=primitives where=rawfile
    subckts info what=subckts  where=rawfile
    saveOptions options save=allpub

    So is it something fixable by upgrading the ISR? Thanks.

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.