Creating a new topic as the above is vision and not perspective, and exactly the issue I am experiencing (although I expect the underlying reason to be the same). I am trying to be a good boy who does not trend everything at one second intervals and use up all the server space. This is causing me a bit of grief though as I am trending a setpoint which might change fairly irregularly against a PV that I would like to view on a timescale of a few minutes. Is there a combination of settings I am missing that will allow the trend to obtain the most recent history point (even if outside the time range) to fill out the trend?
This is particularly egregious when returning a tag history biding as a point count (the trend always starts at 0 even with data just outside the window).
See below crudely amended trend of what I would like to achieve:
I had a similar situation, where I displayed Phase changes in an XY Chart.
If the time setting is on 12:00, and there’s a phase change on 11:59 and 12:10, there’s no data between 12:00 and 12:10. In the XY Chart I got my data through QueryTagHistory, and used the includeBoundingValues argument to solve it ( I think, i’m still testing ).
I would assume that this setting would be available somewhere through the Pen’s history data source. I just haven’t been able to find it yet.
It’s not a solution, but maybe a step closer. I’m also looking for the same solution as you are, so I hope this helps us in the long run.
