What controls "Value" vs Plotting on waveform window.

What is your cross() expression? Secondly, was the original waveform that you were doing a cross() on a family or a single waveform (perhaps you can plot the original signal and then do a screenshot of ViVA so that I can see the legend in ViVA which should make it clearer - make sure that any "+" in the legend is expanded).

Thanks,

Andrew.

correction: cross(OPT("device" "parameter") 0.5 1 "falling" nil nil)

OK. You have used the infotimes parameter of the tran analysis to list a single time where you want to compute the operating point, and also turned off the final operating point checkbox on the tran options form.

Because you can specify multiple times in infotimes it will plot operating point parameters with OPT versus the time at which they were captured. If there's only a single time, there's no lines to be drawn between points, but there's still an x-axis of time.

Clearly if you only have a single point, the cross() function isn't going to work - because nothing crosses. So as you can see, ADE is reporting the cross() expressions as blank - because it got no result.

So, you either need to add more time points in the infotimes parameter, or maybe better you could use the Outputs->To be Saved->Select OP parameters that was introduced in IC616 ISR10 (IC6.1.6.500.10) and then you can use the OT button that was introduced in IC616 ISR12 (IC6.1.6.500.12) to plot it (otherwise you'd have to use the results browser). With this you get the operating point information at every timepoint and then cross() will make sense on this.

Alternatively, if your objective is just to display the operating point info at the single timepoint rather than finding the crossing point of anything, use value(OPT(...) 6.5p) or whatever the time you want to measure it at is.

Regards,

Andrew.

Andrew,

I spotted some errors in my ADE setup.I guess I somehow messed it up as I used cross().Clearly, cross() gave me value  X at which my waveform would cross 0.5 volts of falling edge.Now I should have used this X to get my operating point value by using value() that would interpolate at X  

analogy said:

And yes, I did have 4000 infotimes points.Hey, is there any new feature coming up to increase infotimes points (earlier you said that you will file a feature request to increase infotimes point from ~8000).Thanks.

I'm not aware of any upcoming change to increase the number of infotimes. However, given that there's now the ability to save operating point parameters for a device through the ADE UI from IC6.1.6.500.10 onwards, and also a calculator button ("ot") to access the results, there's less of a need for this - if you do this, the operating point parameters you've selected get saved at every time point.

Regards,

Andrew