In a transient simulation, I step a parameter, call it X.
I also have another parameter function of X, let’s call it Y=f(X).
This means that at every step I will have different values for X and Y.
All works as expected in the transient simulation results.
However, in the post-processing .meas statements, the values of Y are not X dependent anymore:
at each step, the correct value of X is taken, but Y value is always and only the value of step 1.
Is this expected?
It’s easier to understand something like this in a concrete example. You can e-mail it to me at the e-mail address on the Help=>About box. Otherwise, as I understand your post, this would be a counter example:
I have the same issue; is there a resolution for this?
.step dec param BWscope 4G 100k 1
.param BWscope=100K
.param Rscope= 10K
.param Cscope=1/(2*pi*Rscope*BWscope)
I have the above parameters in my simulation, and a simple RC-filter to mimic the bandwidth of an oscilloscope. BWscope steps nicely, but Cscope doesn’t seem to work.
Oddly enough; if I change the .step command to BWscope 100k 4G 1 (turning around the stepping direction), it does seem to work.