dataPointvalue quality to indicate datapoint is good or bad
hussam last edited by
In on_change loggingType , we can't differentiate one datapoint is communication error or is really have value just because value not change,this will impact datapointvalue query in chart, report and other place,especially in chart,if one point communication error on a peroid time then recovered, the chart line display straight line.
if add one quality field,it would avoid this issue.
phildunlap last edited by
I am unsure what you mean by "quality field"
The 'All Data' logging type will keep the value from those periods of time. You can also use "No Change" or "No Update" event detectors if you are trying to catch those communication interruptions. Another option is to use point links to connect one point which keeps all its data to another which logs on an interval. Interval logs often make for smoother charts.
hussam last edited by hussam
quality field means in pointvalues database table direct indicate one point is good or bad in a exact timestamt.
in ALL loggingType, if one timestamt no value,this can indicate it communication error.
in on_change type,we can use use "No Change" or "No Update" event detectors to indicate it communication error.
but when query pointvalue in api,chart,report ,just query data from pointvalue table,we don't join the event detectors to indicate one point is bad or good in a exact timestamt.