Help
  • Explore Community
  • Get Started
  • Ask the Community
  • How-To & Best Practices
  • Contact Support
Notifications
Login / Register
Community
Community
Notifications
close
  • Forums
  • Knowledge Center
  • Events & Webinars
  • Ideas
  • Blogs
Help
Help
  • Explore Community
  • Get Started
  • Ask the Community
  • How-To & Best Practices
  • Contact Support
Login / Register
Sustainability
Sustainability

Join our "Ask Me About" community webinar on May 20th at 9 AM CET and 5 PM CET to explore cybersecurity and monitoring for Data Center and edge IT. Learn about market trends, cutting-edge technologies, and best practices from industry experts.
Register and secure your Critical IT infrastructure

Event Change Detection in Filtered Values Maps for DNP3 Slave Outstations

Geo SCADA Knowledge Base

Access vast amounts of technical know-how and pro tips from our community of Geo SCADA experts.

cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 
  • Home
  • Schneider Electric Community
  • Knowledge Center
  • Geo SCADA Knowledge Base
  • Event Change Detection in Filtered Values Maps for DNP3 Slave Outstations
Invite a Co-worker
Send a co-worker an invite to the portal.Just enter their email address and we'll connect them to register. After joining, they will belong to the same company.
You have entered an invalid email address. Please re-enter the email address.
This co-worker has already been invited to the Exchange portal. Please invite another co-worker.
Please enter email address
Send Invite Cancel
Invitation Sent
Your invitation was sent.Thanks for sharing Exchange with your co-worker.
Send New Invite Close
Top Labels
Top Labels
  • Alphabetical
  • database 32
  • Web Server and Client 31
  • WebX 19
  • Request Form 18
  • Lists, Events & Alarms 16
  • ViewX 15
  • Application Programming 12
  • Setup 12
  • Telemetry 8
  • Events & Alarms 7
  • Lists 7
  • Mimic Graphics 7
  • Downloads 6
  • Support 5
  • IoT 5
  • SCADA 5
  • Geo SCADA Expert 5
  • Drivers and Communications 4
  • Security 4
  • DNP 3 3
  • IEC 61131-3 Logic 3
  • Trends and Historian 2
  • Virtual ViewX 2
  • Geo Scada 1
  • ClearSCADA 1
  • Templates and Instances 1
  • Releases 1
  • Maps and GIS 1
  • Mobile 1
  • Architectures 1
  • Tools & Resources 1
  • Privacy Policy 1
  • OPC-UA 1
  • Previous
  • 1 of 4
  • Next
Latest Blog Posts
  • OPC UA - Driver and Server
  • Requirements for Generating a Valid OPC UA Server Certificate
  • Load Events Using LoadRecord and LoadRecords
  • Geo SCADA Embedded Component Licenses
  • Geo SCADA 2023 Known Issues
Related Products
product field
Schneider Electric
EcoStruxure™ Geo SCADA Expert

Invite a Colleague

Found this content useful? Share it with a Colleague!

Invite a Colleague Invite
Anonymous user
Not applicable
‎2021-06-09 10:40 AM
0 Likes
0
782
  • Bookmark
  • Subscribe
  • Email to a Friend
  • Printer Friendly Page
  • Report Inappropriate Content

Link copied. Please paste this link to share this article on your social media post.

‎2021-06-09 10:40 AM

Event Change Detection in Filtered Values Maps for DNP3 Slave Outstations

Originally published on Geo SCADA Knowledge Base by Anonymous user | June 09, 2021 07:40 PM

📖 Home  Back  
In ClearSCADA, each DNP3 Slave outstation object represents a pseudo outstation that can be polled for static data (current data) and alarm and event data. The points that are monitored by the DNP3 Slave outstation are configured using Filtered Value Maps.

Each Filtered Value Map is associated with database points. These points are the source of the data that can be retrieved from the DNP3 Slave outstation by the DNP3 Master.



Filtered Value Map (DNP3).JPGFiltered Value Map (DNP3).JPGFiltered Value Map (DNP3).JPG

When you are configuring a Filtered Value Map for a DNP3 Slave outstation, you need to consider whether the point sources have their own event data.

Point Sources without Event Data




If the point sources do not have event data, you can configure the Filtered Value Map so that it will generate events for the data. To do this, you should change the Event Change Detection entry on the Filtered Value Map to:

Generate on Update---The Filtered Value Map will generate events for the data that is reported by the point sources (and stored in the Filtered Value Map). As an event is  for every new point update, this can mean that a lot of events are generated.
 
or:

Filtered Chronological Update---The Filtered Value Map will only generate events for the data that has changed since the last update. An event is only created if the point value has changed by the significant change deadband amount or more, crossed a configured limit boundary, and has a timestamp that is later than the previously reported value for the point. The point data must meet all three criteria before the Filtered Value Map will generate an event for the point.

You can use the Alarm Mode and Event Mode settings on the Filtered Value Map to determine whether the DNP3 Slave can contact the DNP3 Master unsolicited with alarm data (Alarm Mode) or logs the event data in its buffer (Event Mode). When Event Mode is selected, the Filtered Value Map logs the event data in its buffer area where it is stored until the DNP3 Slave is read by the DNP3 Master (at which point the event data is reported to the DNP3 Master).

Note that you will need to define the Event Change Detection and Alarm and Event Modes for each row in the Value Map.



Point Sources With Event Data



If the point sources do have event data, the DNP3 Master can read the event data as well as the static data during a normal 'read'. As there can be many events  by the point sources, you can use the Reason for Logging and Reason Mask settings to filter the events. This ensures that only those events that meet certain criteria are logged in the Filtered Value Map's buffer area and reported to the DNP3 Master.

To define which events are to be logged in the Filtered Value Map's buffer area (when the point sources report event data):


  • On the Filtered Value Map, configure the  Event Change Detection setting to Reason for Logging. This instructs the system to log the events from the point sources into the Filtered Value Map's buffer area. Note that you should only use the Reason for Logging option with point sources that have their own event data.


  • Use the Reason Mask setting to define which types of events are to be logged in the Filtered Value Map's buffer area.



You can use the Alarm Mode and Event Mode settings on the Filtered Value Map to determine whether the DNP3 Slave can contact the DNP3 Master unsolicited with alarm data (Alarm Mode) or logs the event data in the Filtered Value Map's buffer (Event Mode). When Event Mode is selected, the Filtered Value Map logs the event data in its buffer area where it is stored until the DNP3 Slave is read by the DNP3 Master (at which point the event data is reported to the DNP3 Master).

Note that if your Filtered Value Map has point sources that report event data, using the  Generate on Update or Filtered Chronological Update options will prevent the point sources' event data being logged in the buffer. Instead, the Filtered Value Map will log the events that it generates itself (these will be stored in the Filtered Value Map's buffer area). The events generated by the Filtered Value Map will be reported to the DNP3 Master, whereas the event data from the point sources will be disregarded.

Go: Home Back

Author

Biography

Anonymous user

Link copied. Please paste this link to share this article on your social media post.

  • Back to Blog
  • Newer Article
  • Older Article
To The Top!

Forums

  • APC UPS Data Center Backup Solutions
  • EcoStruxure IT
  • EcoStruxure Geo SCADA Expert
  • Metering & Power Quality
  • Schneider Electric Wiser

Knowledge Center

Events & webinars

Ideas

Blogs

Get Started

  • Ask the Community
  • Community Guidelines
  • Community User Guide
  • How-To & Best Practice
  • Experts Leaderboard
  • Contact Support
Brand-Logo
Subscribing is a smart move!
You can subscribe to this board after you log in or create your free account.
Forum-Icon

Create your free account or log in to subscribe to the board - and gain access to more than 10,000+ support articles along with insights from experts and peers.

Register today for FREE

Register Now

Already have an account? Login

Terms & Conditions Privacy Notice Change your Cookie Settings © 2025 Schneider Electric

This is a heading

With achievable small steps, users progress and continually feel satisfaction in task accomplishment.

Usetiful Onboarding Checklist remembers the progress of every user, allowing them to take bite-sized journeys and continue where they left.

of