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:
