Hello, during the DNP3 check, the following problem occurred:
~ 2:02:00 PM there was a connection break, then at 2:23:52 PM the connection was restored. Data was pulled from the buffer until 2:31:47 PM. While the buffer is being emptied, we do not receive data for the history. The graph shows this as a flat line. At the same time, the value and timestamp change.
We noticed that a value appears during data collection. The timestamp of this value is larger than the ones that are unloaded next.
As an example: 8:30:14, 8:31:08, 8:30:16. The time 8:31:08 corresponds to the end time of the buffer loading into the history.
Video speed x0.5
Can you post the data from your history database from around the time the value flatlines?
There is a know issue with history, deadband and charts when you have loss of connection.
SELECT *, from_unixtime(t_stamp/1000) as time FROM sqlt_data_XXXX where tagid = XXX and t_stamp order by t_stamp DESC
replace sqlt_data_XXXX and tagid number with your database and tagid.
Thanks for the hint.
Executed the following query in MSSQL:
SELECT TOP (1000) [tagid]
,dateadd(s,[t_stamp]/1000,'01-01-1970') as ctime
where tagid = 1 and t_stamp between 1671096477000 and 1671096614000
order by t_stamp desc
Received the following response:
The values change every second. From this table it can be seen that there is no data for 2 minutes. On the graph, this data shows flat.
The dataintegrity colom is the most interesting part here, and its missing from your response.
Would also be more interesting if we could see the data from the timeperiod you posted first, December 12, 02:00-02:35
If dataintegrity is 0, then the intvalue in the database will not be taken into account on the chart(this is stupid), but it will use the timestamp, and create a flat line from the previous entry in the database.
Then from the entry where data integrity is 0 to the next entry, there will be a line break in the chart, if this option is turned on. This is fine, because you have a loss of communication here.
I wrote a post trying to explain my findings here:
[[FEATURE] Increase usability of the Perspective Power Chart component - #57 by Simen]