开云体育

using round to get better readable results (e.g. mV's with one further number after the dot) in the measurements does not work for me in AC measurements while it works fine for TRAN.

?

running .AC the following statements bring the below listed results

?

.OPTIONS meascplxfmt=polar
.MEAS V_ACOMP_max_IC7_p18_mV ? ? ? ? ? ? ? ? ? ?PARAM (V_ACOMP_max_IC7_p18*1000*10)/10

.MEAS V_ACOMP_max_IC7_p18_mV_2 ? ? ? ? ? ? ? ? ? ?PARAM round(mag((V_ACOMP_max_IC7_p18*1000*10)/10))
.MEAS AC V_ACOMP_max_IC7_p18_mV_3 ? ? ? ? ? ? ? ? PARAM round(mag((V_ACOMP_max_IC7_p18*1000*10)/10))

leads to

v_acomp_max_ic7_p18_mv: (V_ACOMP_max_IC7_p18*1000*10)/10=(24.2389660125,0?°)
v_acomp_max_ic7_p18_mv_2: round(mag((V_ACOMP_max_IC7_p18*1000*10)/10))=(0,0?°)
v_acomp_max_ic7_p18_mv_3: round(mag((V_ACOMP_max_IC7_p18*1000*10)/10))=(0,0?°)

?

In former versions e.g. 24.0.12 using round() even crashed and said: this is a bug, please report it.

Now with 24.1.8 it does not crash but reports zero...but maybe I am doin wrong because I don't get converted (not even with mag() ) this cartesian numbers to normal values.
Also the ASCII character in front of ° looks weired since new version installed.

By using round() in .AC analyses, you're requesting the round operation is performed on a complex number. I'm not sure that is meaningful. Just because you're using it on the result of a mag() function doesn't change this, as as mag() still returns a complex number.

I'm not surprised it doesn't work.

--
Regards,
Tony