• 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. RF Design
  3. hbnoise: difference between sweep-type relative harmonic...

Stats

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

hbnoise: difference between sweep-type relative harmonic=0 and absolute

Immalario
Immalario over 7 years ago

Hi,

I am simulating a direct conversion receiver and I am interested in simulating the noise at baseband. The problem is that I get different results when using hbnoise with sweep-type relative harmonic=0 and absolute to sweep through the baseband bandwidth. Shouldn't it be identical as eventually the swept bandwidth is the same for both cases. Thanks in advance.

Best regards,

Immalario

  • Cancel
  • Immalario
    Immalario over 7 years ago
    Anyone here knows the answer :(( ? Is it a bug in Cadence spectre?!
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 7 years ago

    I meant to reply to this the other day. It sounds strange and I don't recall seeing this before. I'd be surprised if it's a bug in the simulator.

    There's not really enough information to go on. Can you please provide:

    1. The exact subversion of spectre you're using
    2. The analysis statements from the bottom of the input.scs (ideally the parameters at the top of the netlist too if you're using any of those in the analysis setup)

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Immalario
    Immalario over 7 years ago

    Hi Andrew,

    Thanks for your response!, I am using IC6.17.713_SPECTRE16.10.284. The node I am plotting is the one from hbnoiseOut1. Thanks in advance!


    simulator lang=spectre
    global 0
    parameters harm=9 flo=2G prf=-50
    include "netlist"
    simulatorOptions options reltol=5e-3 vabstol=1e-6 iabstol=1e-12 temp=27 \
    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" \
    dochecklimit=yes checklimitdest=both
    dcOpCheckLimit checklimit checkallasserts=yes severity=none
    dcOp dc write="spectre.dc" homotopy=dptran maxiters=150 maxsteps=10000 \
    annotate=status
    dcOpInfo info what=oppoint where=rawfile
    hb hb tstab=80n saveinit=yes autosteady=yes oversample=[2]
    + fundfreqs=[(flo/2)] maxharms=[harm] errpreset=moderate
    + tstabmethod=gear2only annotate=status
    +hbstb hbstb start=10 stop=300M dec=20
    +annotate=status
    hbac hbac sweeptype=relative relharmvec=[1] start=10 stop=300M
    + dec=30 maxsideband=3 annotate=status
    hbnoiseOut1 ( vop von )
    + hbnoise sweeptype=relative relharmvec=[0] start=1k stop=200M
    + dec=5 values=[10 100] iprobe=PORT1 refsideband=[0]
    + noisetype=timeaverage noiseout=[am pm usb lsb]
    + separatenoise=yes annotate=status krylov_max_iter=400
    hbnoiseOut2 ( vop2 von2 )
    + hbnoise sweeptype=relative
    + relharmvec=[0] start=1k stop=200M dec=1 values=[10 100 100k]
    + iprobe=PORT1 refsideband=[0] noisetype=timeaverage noiseout=[am
    + pm usb lsb] separatenoise=yes annotate=status
    + krylov_max_iter=400
    primitives info what=primitives where=rawfile
    subckts info what=subckts where=rawfile
    asserts info what=assert where=rawfile

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 7 years ago
    I’m using IC617 ISR14, and if I try to set up the simulation with am or pm noise and pick “absolute” it disallows this - it tells me I must pick “relative”. I don’t think it makes any sense to pick absolute if you are simulating with am/pm noise; in fact I don’t think it makes any sense if you are picking relative harmonic 0 either. So probably you should just pick “USB”.

    For me, if I do that, I get identical results whether I use relative with harmonic 0 or absolute.

    Regards,

    Andrew.
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Immalario
    Immalario over 7 years ago in reply to Andrew Beckett

    Hi Andrew,

    I delayed my reply until I did further investigations. First, The above error disappeared and I couldn't reproduce it. It disappeared after creating new maestro veiw!

    Regarding your reply, I did noise sim "ALL" not "USB", as I was simulating phase noise simultaneously for other nodes (LO signal of a receiver) together with the Rx output at baseband (relative harmonic=0) or absolute (while sweeping the target baseband frequency range).

    I expected that regardless of ALL or USB, for the baseband signal, should get the same result. The issue is that when plotting USB noise after doing USB-noise sim or ALL-noise sim, I get different results. This I cannot understand. Also when plotting the noise summary, different components are having different contribution for ALL and USB noise sims. So which one can I trust?

    Thanks for your support!

    Best regards,

    Ahmed.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 7 years ago in reply to Immalario

    Ahmed,

    I can't think of a good reason why you'd get different USB noise results between running USB or ALL mode - that doesn't make sense to me. I think we'd need to look at this via customer support to understand whether it's a usage issue or a bug.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Immalario
    Immalario over 7 years ago in reply to Andrew Beckett

    Hi Andrew,

    Thanks for your reply. I escalated this inside my company. My colleagues from the methodology department is tackling the issue. They will probably escalate it to Cadence support team. Thanks for your time!

    Best regards,

    Ahmed.

    • 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