What to do with probes

[Svenn Are Bjerkem]

Hi,

I am reading a bit in the skdfref.pdf and wonder what to do with probes.
I know probes from Pspice, and they control which signals get plotted.
Doesn't look like that in Virtuoso. What are the typical uses of a
probe?
--
Svenn

 

[Jean-Marc Bourguet]

Svenn Are Bjerkem <svenn.are@bjerkem.de> writes:

I am reading a bit in the skdfref.pdf and wonder what to do with
probes. I know probes from Pspice, and they control which signals
get plotted. Doesn't look like that in Virtuoso. What are the
typical uses of a probe?

Probe is a way of highlighting things.

Yours,

--
Jean-Marc

 

[fogh]

Svenn Are Bjerkem wrote:

Hi,

I am reading a bit in the skdfref.pdf and wonder what to do with probes.
I know probes from Pspice, and they control which signals get plotted.
Doesn't look like that in Virtuoso. What are the typical uses of a
probe?

I had a few thoughts about this. It probably possible to make a symbol
that will have the same effect as the analog artist "add signal to
outputs". However, the probes in pspice keep working when a change
occurs in the instance names that make up the hierarchy path to the
probe. That is the difficult bit with analog artist: even though ADE and
the schematic editor can communicate, there is no ready made support
for this. You would need to callback ADE after any instance name change
in a schematic, so that the running ADE sessions will check wether they
have this instance in the outputs. Thinks get worse if you want to
update not only signal outputs but also expressions. And things get
hairy if you want to also update artist states (you can also wonder
wether you really want to always do that, w.r.t. to version control.).

I don t want to paint it black though: if you want the functionality
to work only on toplevel or top-1 (testbench) that must be doable.

I once opened a SR for this, and it was void'ed. Wishing you better luck.