Can I view the value of a calculated parameter in my simulation?

I am debugging a symbol that accepts parameters. Is there a way that I can view the values of the calculated parameters so I can check my calculations I used in the parameters?
For instance, using these parameters (below), can I see the value used for Lx to verify that I’ve entered the correct equations in my parameters?

.param L=Zo**2C
.param C=31p
.param Len=2
.param Zo=52
.param N=100
.param Lx=L/N
Len

Thanks,
Carl

you need a .meas command add:
.meas L_x Lx

Does .option listparam print that? I don’t have a laptop to verify currently.

Using your suggestion, I get the Post Process results showing:
.meas l_x lx:
5.20833e-10 1.99988e-08
The lx value is correct (as expected). What is the second number?

Thanks,
Carl

The .option listparam shows the expected parameter values in the simulation tab and then stops (no post processing or waveform display). It gives me the calculated values that I want. Is it supposed to skip the simulation?
Thanks,
Carl

This simple test is fine. From what you describe, it seems like either you made a mistake in the schematic, or your schematic can trigger a bug in Qspice.

Listparam.qsch (987 Bytes)

The time when the parameter calculation was performed (default is the end of the simulation)

Without time in .meas for a parameters, use this .meas L_x param Lx instead of .meas L_x Lx

OK, that does what I was hoping for (without the extra confusion).

Is this stuff documented somewhere?

Thanks,
Carl

About .meas <> param <> format?
Not documented in Qspice help, but was in LTspice help.
I also included this in my command guide in .meas section.

1 Like

Exploring the problem, I found that a more complicated circuit causes .option listparam to skip the simulation. I’ve attached an example that shows the problem. If you delete M3 (or some larger quantity of other components), the simulation will run as expected. I sent an example to Mike.

Later,
Carl

listparamtest9.qsch (18.4 KB)

1 Like

Today’s QSPICE release seems to have addressed the problem!
Later,
Carl