Ok, so I have a mqtt broker publishing to vt scada, and vt scada doesnt like it for some reason. It gives me a flat line for a graph every time the value updates in historical data viewer. It also seems to update values from all time to the most recent value given. For exampe, i have a current value with max min and average set at 26. Then mqtt publishes to vt scada the value of 25. All values that ever existed get magically transformed into the most recent value of 25. This results in a line flatter than the fields of Iowa and a new min max and average of 25. I would not put this issue past user error, and I have provided a photo that is hopefully useful
If you are confused at all I will gladly send more pictures or whatever you need.

-Thanks

Ok, I got it by pure luck. When you go to you I/O and calculations tag, go under the logging tag and change the minimum log interval from 0 to 1-whatever time your heart desires.
For clarifications sake, I have vtscada light on the 12.2 version. If someone could explain why this happened that would be great, because I don't have a clue why it worked.

There are a number of possibilities here though they feel like VTScada there is an issue with the deadbanding (which can result from either deadbanding, or scaling settings). For example, if you scaling is -9999999999 to 99999999999 then .1% of that range is still a large number which means changes to the tag won't be registered in the historian.

I wasn't able to reproduce the issue using MQTT with a JSON payload. Can you provide more details about your driver and I/O configuration?

Additional Comments from two of our developers:

• There might still be some timing issues in their setup. Enabling the Minimum Log Interval will force the IO tag to log at the interval using the current timestamp, rather than using the timestamp provided by the driver. So the flat-line problem is likely hidden by this change rather than being resolved.

• just a FYI, the driver uses a timestamp if one comes with the measurement, otherwise the driver stamps the value with the current timestamp.
  Are they reading historic data? Is this Sparkplug? Or pure MQTT?

So, I am using Sparkplug-B I think through mqtt via hivemq.

here is my driver. I have tls encryption enabled.

this is my I/O config and i have logging settings at min log 1 and deadband at .00005. I will gladly provide more info if you need.

Ok, Dave, here is my scaling range for my I/O tag.