Stats

  • Locked Locked
  • Replies 1
  • Subscribers 132
  • Views 17327
  • 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

Is there a voltage probe symbol for analog lib?

Milkman

Designers want a voltage probe that can be instantiated on a schematic.  The voltage probe translates to a .probe statement in hspice netlists or a save netname statement in a spectre netlist.

Here are my questions

1.Do I need to use a formInitProc to get the attached netname or a callback procedure?

2. In the formInitProc or Callback proc, how do I get the value of the netname attached to the terminal?

 Here are the code fragments below.

;; netlist procedure to print save netname line in spectre netlist

;; procedure( sgSpectreVprobe(inst)
    let((fp net_name enable complete_line cv)
    fp=nlGetNetlister(inst)
;; Get value from instance
    net_name = nlGetParamStringValue(inst 'net_name)
    ;cv = nlGetCurrentCellView(inst)
    ;l_nets = nlGetSimTerminalNets(cv)
    ;this_net=car(l_nets)
    enable = nlGetParamStringValue(inst 'enable)
    complete_line = strcat("save net_name")
    nlPrintString(fp)
    nlPrintString(fp complete_line)
    ); let
);procedure

 

############# CDF pararmeter

    cdfCreateParam( cdfId
        ?name           "net_name"
        ?prompt         "net_name"
        ?defValue       "net_name"
        ?type           "string"
    )

 

 

  • aplumb

    I took a different approach and created a 'voltage bsource' device that could be instantiated in a schematic.  A designer can then set the 'v' parameter value to the anything, including simple v(path.to.internal.net) or differential signal expressions.  Then you assign a top-level net name to the bsource output and save as you see fit.

     I created a one-liner model file include to 'save all top-level signals' that designers can quickly enable:

    save * depth=1

    Not precisely what you're looking for, but may be useful if you can't get the vprobe working. 

    Andrew. 

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.