# Easy Chart Lag?

**URL:** <https://forum.inductiveautomation.com/t/easy-chart-lag/77291>\
**Category:** Ignition\
**Tags:** vision\
**Created:** [August 2, 2023, 2:49pm UTC](https://forum.inductiveautomation.com/t/easy-chart-lag/77291 "2023-08-02T14:49:31Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![DonPancoe](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/donpancoe/32/28698_2.png) [@DonPancoe](https://forum.inductiveautomation.com/u/DonPancoe)\
**Post date:** [August 2, 2023, 2:49pm UTC](https://forum.inductiveautomation.com/t/easy-chart-lag/77291/1 "2023-08-02T14:49:31Z")

</div>

I have a client who is reporting that Easy Charts in their HMI are updating 30 to 45 sec after they see other discrete indications on the screen have updated. Is there a way to optimize this performance, or is this just the nature of a historian-based chart? Are there any other ways to chart real-time data in Vision?

Thank you!

---

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [August 2, 2023, 2:55pm UTC](https://forum.inductiveautomation.com/t/easy-chart-lag/77291/2 "2023-08-02T14:55:58Z")

</div>

How positive are you that this client's local time is actually correct? That's the most common cause of easy chart "lag" in my experience. If the local machine thinks "right now" is 45 seconds in the past, then your 'realtime' easy chart is always going to be wrong.

---

<div class="post-metadata">

**Author:** ![DonPancoe](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/donpancoe/32/28698_2.png) [@DonPancoe](https://forum.inductiveautomation.com/u/DonPancoe)\
**Post date:** [August 2, 2023, 3:05pm UTC](https://forum.inductiveautomation.com/t/easy-chart-lag/77291/3 "2023-08-02T15:05:04Z")

</div>

Thank you for the input. I will definitely check that.

There is a point in the process where the operator is watching the chart for a change to determine a set point for a subsequent step, so I do believe they are seeing a lag between discrete indications and a chart on the same screen, but I cannot confirm that this lag actually adds up to 30+ seconds.

---

<div class="post-metadata">

**Author:** ![DonPancoe](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/donpancoe/32/28698_2.png) [@DonPancoe](https://forum.inductiveautomation.com/u/DonPancoe)\
**Post date:** [August 2, 2023, 3:07pm UTC](https://forum.inductiveautomation.com/t/easy-chart-lag/77291/4 "2023-08-02T15:07:16Z")

</div>

Actually just checked and that machine is within one or two seconds of [time.gov](http://time.gov).

---

<div class="post-metadata">

**Author:** ![cdunn.home](https://avatars.discourse-cdn.com/v4/letter/c/45deac/32.png) [@cdunn.home](https://forum.inductiveautomation.com/u/cdunn.home)\
**Post date:** [February 15, 2026, 7:32pm UTC](https://forum.inductiveautomation.com/t/easy-chart-lag/77291/5 "2026-02-15T19:32:29Z")

</div>

Paul's suggestion was spot on for me

For future reference, the lag is created by the relative difference between the gateway and the client computer times.

I threw a label on a vision window and bound the text as:

> secondsBetween({[System]Client/System/CurrentDateTime},{[System]Gateway/CurrentDateTime})

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [February 15, 2026, 7:43pm UTC](https://forum.inductiveautomation.com/t/easy-chart-lag/77291/6 "2026-02-15T19:43:05Z")

</div>

A similar type of timestamp issue occurs when using OPC connections to PLCs and the PLC time is wrong. This affects both Vision and Perspective.