Not able to measure -ve delay

[Manoj Maskey]

Hi Xyce team,

Xyce is not able to measure the -ve delay. The fourth measurement statement is suppose to measure the delay from first fall (input, LUTD) to first rise (output, Y4), but it is measuring the delay from first fall to first fall instead of first rise (which should give the -ve delay).

.   

The following are the measurement statements: 

.MEASURE tran LUTD_y_rr TRIG V(LUTD)=0.375 RISE=1 TARG V(Y4)=0.375 RISE=1
.MEASURE tran LUTD_y_ff TRIG V(LUTD)=0.375 FALL=1 TARG V(Y4)=0.375 FALL=1
.MEASURE tran LUTD_y_rf TRIG V(LUTD)=0.375 RISE=1 TARG V(Y4)=0.375 FALL=1

.MEASURE tran LUTD_y_fr TRIG V(LUTD)=0.375 FALL=1 TARG V(Y4)=0.375 RISE=1

Following are the measurement results:

LUTD_Y_RR = 8.523248e-11 with trig time= 1.575000e-10 and targ time= 2.427325e-10

LUTD_Y_FF = 8.947844e-11 with trig time= 1.157500e-09 and targ time= 1.246978e-09
LUTD_Y_RF = 1.089478e-09 with trig time= 1.575000e-10 and targ time= 1.246978e-09

LUTD_Y_FR = 8.947844e-11 with trig time= 1.157500e-09 and targ time= 1.246978e-09

Please suggest if this is an issue or Xyce feature to not measure -ve delays.

Regards,

Manoj

[xyce-users]

Thanks for reporting this.  If we can confirm it, this might be a bug.  We'll investigate.

thanks,

The Xyce Team

[xyce-users]

Hi Manoj,

I haven't had time to look at this yet, but I was reminded that you have been using Xyce 7.3, which is relatively old (about a year).

A LOT of bugfixes for .measure happened after that release.    I think it is likely that you won't observe this bug in Xyce 7.4, and I encourage you to try 7.4 (or wait and try 7.5, which is nearly done).

thanks,

The Xyce Team