• 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. Creating a "virtual short" in simulations

Stats

  • Locked Locked
  • Replies 11
  • Subscribers 126
  • Views 5105
  • 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

Creating a "virtual short" in simulations

jehh
jehh over 5 years ago

Hi,

In my APS simulations I have added some inductors from the analogLib (ind), to represent the effect of bond wires. These slow down the simulation, but is necessary in order to understand some dynamics.

In some situations I do not wishto test these dynamics, and was wondering if it is possible to specify that 'all inductors are shorted', or something of similar effect?

Br,
JEHH

  • Cancel
Parents
  • Frank Wiedmann
    Frank Wiedmann over 5 years ago

    From typing "spectre -h options" at the command line:

    102 lshort=0 H Fixed value inductors with L<=lshort are shorted.
    lshort can additionally be applied to variable value
    inductors using the option 'short_cut_var_elem=yes'.

    • Cancel
    • Vote Up +1 Vote Down
    • Cancel
  • jehh
    jehh over 5 years ago in reply to Frank Wiedmann

    Thank you - this seems like the right path.

    However, I try to specify lshort=10n, under additional arguments in the spectre simulator options, and then run a transient simulation. However, it doens't seem to short the inductor. Am I using the lshort correctly, or did I misinterpret?

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • ShawnLogan
    ShawnLogan over 5 years ago in reply to jehh

    Dear jehh,

    I was going to suggest a slightly different approach. Have you considered including an ideal resistor in parallel with each inductor with a value set by a variable, for example, "rshort"? In this fashion, when you want to include the inductors in your simulation, you set "rshort" to very large value. For  simulations where you do not wish to include the inductors, you set "rshort" to a very small value (1 milliohm, as an example).

    Shawn

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Frank Wiedmann
    Frank Wiedmann over 5 years ago in reply to jehh

    In earlier versions of Spectre, the option was named lcut instead of lshort. You can check with "spectre -h options" if this is the case.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Frank Wiedmann
    Frank Wiedmann over 5 years ago in reply to jehh

    In earlier versions of Spectre, the option was named lcut instead of lshort. You can check with "spectre -h options" if this is the case.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
  • Andrew Beckett
    Andrew Beckett over 5 years ago in reply to Frank Wiedmann

    Note that in some pretty old versions (I tried even MMSIM15.1) lshort wasn't advertised but did work (it was an alias for lcut, I think). In SPECTRE 17.1 we removed lcut and made lshort the documented option. I tried it with old versions, and it was fine.

    I would expect if lshort was not working in the version you were trying that it would tell you in the log file. No mention was made of the simulation version being used, so it's hard to guess what the issue might really be.

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • jehh
    jehh over 5 years ago in reply to Andrew Beckett

    Hi Andrew,

    I am using spectre_17.1-ISR14_64 (also, lshort does show up, when I look type "spectre -h"). The only mention of lshort in the log file, is under global options sections, see setion below >

    ===================

    Global user options:

    psfversion = 1.4.0
    vabstol = 1e-06
    iabstol = 1e-12
    temp = 27
    gmin = 1e-12
    rforce = 1
    maxnotes = 5
    maxwarns = 5
    digits = 5
    cols = 80
    pivrel = 0.001
    sensfile = ../psf/sens.output
    checklimitdest = psf
    lshort = 2e-05
    save = allpub
    tmioutput = /scratch/jehh/simulation/test_libraries/ind_short_test/maestro/results/maestro/ExplorerRun.0/1/test_libraries:ind_short_test:1/netlist/input
    degfile = /scratch/jehh/simulation/test_libraries/ind_short_test/maestro/results/maestro/ExplorerRun.0/1/test_libraries:ind_short_test:1/netlist/input
    scalefactor = 0.855
    reltol = 0.001
    tnom = 27
    scalem = 1
    scale = 1

    ========================================================

    And the input.scs netlist is very simple, but still contain the inductor >

    ========================================================

    // Point Netlist Generated on: Aug  5 12:45:33 2020
    // Generated for: spectre
    // Design Netlist Generated on: Aug  4 15:20:31 2020
    // Design library name: test_libraries
    // Design cell name: ind_short_test
    // Design view name: schematic
    simulator lang=spectre
    global 0
    parameters fs=10000000
    *** INCLUDE OPTIONS REMOVED FOR LEGAL REASONS ***

    // Library name: test_libraries
    // Cell name: ind_short_test
    // View name: schematic
    L0 (vout vin) inductor l=1u
    C0 (vout 0) capacitor c=1u
    R0 (vout 0) resistor r=1K
    I1 (vin 0) isource type=pulse val0=0 val1=1 period=1/fs delay=10n \
            rise=200p fall=200p width=0.5/fs
    simulatorOptions options psfversion="1.4.0" reltol=1e-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" checklimitdest=psf lshort=20u
    tran tran stop=10u errpreset=conservative write="spectre.ic" \
        writefinal="spectre.fc" annotate=status maxiters=5
    finalTimeOP info what=oppoint where=rawfile
    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
    save I1:sink L0:1 C0:1 R0:1
    saveOptions options save=allpub

    Is there any obvious thing I am doing wrong?

    BR,

    JEHH

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Frank Wiedmann
    Frank Wiedmann over 5 years ago in reply to jehh

    Of course the inductor still appears in the netlist, this option does not change the behavior of the netlister, after all. However, the inductor should behave like a short in the simulation (which you would see in the simulation results). If the option is listed in the log file (as in your case), it is supposed to work.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • jehh
    jehh over 5 years ago in reply to Frank Wiedmann

    Hi Frank,

    Sorry if I seem like a young buck. ;) Below I tried to insert the simulation result. I am pulsing a current through an inductor, at node /vin - this node is seen to spike at several kV, unexpected with the inductor shorted.

    If you have any suggestion on how to investigate further, they are very welcome.

    BR,

    JEHH

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • jehh
    jehh over 5 years ago in reply to jehh

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 5 years ago in reply to jehh

    Please contact customer support. I did some experiments, and in SPECTRE16.1 versions the lshort appears to work with this example, but in later versions it doesn't. The inductor is still listed in the circuit inventory (which may be OK), but I still see the behaviour of the inductor present in the circuit.

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • jehh
    jehh over 5 years ago in reply to Andrew Beckett

    Thank you, Andrew,

    I will do that.

    BR,

    JEHH

    • 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