• 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. Eye diagram function

Stats

  • Locked Locked
  • Replies 5
  • Subscribers 125
  • Views 15368
  • 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

Eye diagram function

starsky
starsky over 15 years ago

 Hello everyone,

 I have a VCO schematic in which the phase noise is measured using pnoise analysis, the time period is  start: 1; stop: 100M with PSS beat frequency as 5G.

How to use the eye diagram function for this phase noise? I mean, I know the syntax will be 

EyeDiag(Signal, TDelay , TPer , N)  but when I give expression as eyeDiagram(phaseNoise(1 "pss_fd" ?result "pnoise"), 5M, 100M, 3)

 I am able to plot but not able to see the eye diagram as such.

 Pls help.

  • Cancel
  • Andrew Beckett
    Andrew Beckett over 15 years ago

    This doesn't make any sense, for several reasons:

    1. pnoise produces frequency domain results - you see the output noise power spectral density versus frequency.
    2. An eye diagram is a time domain metric - you need time domain waveforms coming into the function - so phaseNoise is completely inappropriate.
    3. Even assuming that you'd run (say) transient noise instead to get a noisy time domain waveform, using the eyeDiagram function doesn't make sense, because it relies on having a fixed clock frequency, which is unlikely to be the case with a VCO.
    4. More likely to be useful with a time domain VCO waveform is to run time domain noise, and then use the freq function to get the instantaneous frequency, and then plot a histogram of that (exactly how depends on whether you're using IC5141 or IC61).
    5. But to be honest, pnoise will be more efficient. Perhaps you can use the "jitter" mode if you want to get some idea of jitter metrics - not really sure what  your goal is.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • starsky
    starsky over 15 years ago

    Hello Andrew,

    I got it now, I was using eye diagram function in wrong context.

    So, what is the use of eye diagram function or rather how should I use this function to calculate frequency in an LC VCO circuit?

    Oh and I am using spectre ICI5141.

    Regards

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 15 years ago

    You'd probably be better off using the "freq" function in the calculator instead, from a transient run, to plot instantaneous frequency versus time for the VCO. Or use the harmonicFreq function to get the frequency from the PSS results (easiest way to do this is to use the Results->Direct Plot->Main form, check the "Add to Outputs" checkbox, and then pick the "frequency" choice (I think that's what it is) and choose harmonic 1, say; this will add the right expression into your ADE Outputs Pane).

    Regards,

    Andrew.

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • starsky
    starsky over 15 years ago

     Hello Andrew,

    I GOT IT :)

    Now, how do I calculate the phase noise?

    Thanks & regards,

    starsky

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 15 years ago
    By using pss/pnoise (or hb/hbnoise) and then using the phaseNoise function (or do it from the direct plot form)M

    Best thing is to look in your MMSIM installation under tools.lnx86/spectre/examples and the look in the SpectreRFworkshop dir (or whatever it is called) which will have examples of how to do this kind of simulation for an oscillator.

    Regards,

    Andrew
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel

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