[Imported] DNP3 point noisy - Not honouring significant change setting

[sbeadle]

>>Message imported from previous forum - Category:ClearSCADA Software<<
User: nminchin, originally posted: 2019-01-08 00:24:26 Id:345
I have a DNP3 point, an analogue point measuring motor current, that is recording over 200,000 records a week into the history, and is not honouring its significant change setting.
Point significant change is set to absolute 0.5, however as you can see from the attached image, there are sequential records in the history with less than 0.5 between them.
Historic compression isn't configured (apply to No Data).

Am I missing something?

 qr/ytsx351kahbp.png "")
 ys/bd5ju32cobmj.png "")

Cheers,
Nick

Attached file: (editor/ys/bd5ju32cobmj.png), image.png File size: 23675

Attached file: (editor/qr/ytsx351kahbp.png), sig change.PNG File size: 2844

[sbeadle · Accepted solution]

>>Responses imported from previous forum

Reply From User: JesseChamberlain, posted: 2019-01-08 01:56:37
Deadband only applies to 'Current Data'. If the RTU sends an event for Value Change, it bypasses the deadband.

You need to modify event settings on the RTU.

Doco ref _Core Reference Core Point Configuration Defining Analog Point Details Define the Criteria for a Significant Change in Value_.

Reply From User: nminchin, posted: 2019-01-08 05:04:55
Thanks Jesse, I read the help before but must have missed where it talked about only applying to the current data. The property box heading is somewhat misleading... I'll make the change in the RTU 🙂