Subscribing is a smart move!
You can subscribe to this forum after you log in or create your free account.
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.
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.
Send Invite Cancel
Link copied. Please paste this link to share this article on your social media post.
📖 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).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.
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.
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):
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
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).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
Create your free account or log in to subscribe to the forum - and gain access to more than 10,000+ support articles along with insights from experts and peers.