Welcome to the new Schneider Electric Community

It's your place to connect with experts and peers, get continuous support, and share knowledge.

  • Explore the new navigation for even easier access to your community.
  • Bookmark and use our new, easy-to-remember address (community.se.com).
  • Get ready for more content and an improved experience.

Contact SchneiderCommunity.Support@se.com if you have any questions.

Close
Invite a Co-worker
Send a co-worker an invite to the Exchange portal.Just enter their email address and we’ll connect them to register. After joining, they will belong to the same company.
Send Invite Cancel
84648members
353988posts

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

EcoStruxure Geo SCADA Expert Forum

Find out how SCADA systems and networks, like EcoStruxure Geo SCADA Expert, help industrial organizations maintaining efficiency, processing data for smarter decision making with IoT, RTU and PLC devices.

Solved
sbeadle
Janeway Janeway
Janeway
0 Likes
1
436

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

>>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?

![]((see attachments below) qr/ytsx351kahbp.png "")
![]((see attachments below) 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

Attachments

Accepted Solutions
sbeadle
Janeway Janeway
Janeway
0 Likes
0
435

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

>>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 🙂

See Answer In Context

1 Reply 1
sbeadle
Janeway Janeway
Janeway
0 Likes
0
436

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

>>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 🙂