Display's Start/End Time in Vision Calculation

Rats, i jumped the gun with my original statement below, reading closer, the request is 'Vision Calc'. I thought that did work. If not, that's a fail from the start regarding Vision Calcs - thought that's how it's supposed to work.

I'm thinking of apply the times back to an AF calc. Probably needs to be a different request???

Actually have a few use cases here. Most recent request was for comparing fuel usage for each shift to see if a particular shift was using more energy than another during various times - it could be 2 days, or 2 weeks.
Currently, we're using Software Athlete's extensibility object to manually write to some AF attributes, but it's convoluted and doesn't affect other data on the page. Would sure be nice to set the time for the entire display and affect all data on the display.

I have a use-case where we can use this for PE calcs for example:

TimeGT('phTag', starttime, endtime, 7)

Please make an enhacement to provide the ability to PE Calc to grab the displays: starttime and endtime

thanks

I agree. I would find it helpful if the PI Vision local calculations included functionality which returned the start time, duration and end time of the PI Vision display. I think this would provide PI Vision displays similarly effective calculation potentials as the EventFrame([xxx]) function.

DisplayTime("StartTime") => Start time of display

DisplayTime("Duration") => Duration of display

DisplayTime("EndTime") => End time of display

(While I reference this using a format based upon the EventFrame([xxx]) function within EventFrame Analyses, I am happy for any format.)

My Use Case:

Within PI ProcessBook we had custom code which allowed the user to enter start and end times and the VBA Code would update every trend and data set to reflect those times. These VBA-created data sets were embedded with timestamps implementing similar functionality to what is now in the EventFrame([xxx]) function within analyses. We used this for event reviews to easily find the extrema values and times for a large set of tags for any random event. Since moving to PI Vision, we have made a proxy of this functionality forcing all reviews to be a static duration of one hour. This adds a lot of noise to our reviews.

Another, more general use case would be to use PI Vision for EventFrame Analysis design and simulation.