Indicating Recovered Events
This item presents the characteristics of the Recovered Events feature, implemented in Action.NET. It is widely used when reading dated events and reading health. In several communication protocols, the General Interrogation (IG) request is available for the Client to request from the Server the complete set of static data, that is, as they are currently.
Â
Recovered Events
Context of the function
In several communication protocols, the General Interrogation (IG) request is available for the Client to request from the Server the complete set of static data, that is, as they are currently.
Typically this request is made at the beginning of the connection, to establish a complete initial database, in the supervisory memory, mirroring the IED memory. In several protocols in these messages states and measures are not tracked by Timestamp.
Ig request is also made periodically as a way to provide a health check. If you have lost any digital data change submission, when you receive this status it will be different from the existing one on the client.
The purpose of this feature is to mark this message so that the occurrence can be checked later in historical event searches.
Functionality
As a result of this functionality in Action.NET, when a state is detected, through general reading, and not change reads, the timestamp will be done by the client communication module, with ZERO milliseconds, and in the change event message the acronym ** will be includedRCP{}, indicative of a recovered change event.
It is only applied to tags with DIGITAL data types (including dual digital) by communication modules.
Implementation
Occurrence detection
The detection of the occurrence that the state of a tag, read by IG is different from the current one in memory, is made by each of spin's communication modules, which use IG with data without timestamp. (IEC104, DNP3 and IEC101).
When detected, the millisecond part of the timestamp is passed to ZERO.
And the attribute PrefixAlarmMessage of the tag is filled with the text indicative of the recovered event (by default **RCP{}).
Publication of the occurrence
As a result of changing the status of the tag, an alarm message will be generated if registered in the tag. The DataAccess module of Action.NET after creating the message and before publishing it adds in front of the message the text that exists in the attribute
PrefixAlarmMessage. Goes for a single message, that is, after using the message generation mechanism itself puts empty in this attribute.
Configuration
The acronym **CPR** is used by default, prefixing the tag status change alarm. If you want another acronym, simply put the preferred text in the StartValue attribute of the tetxo tag: zz_system. PrefixForRecoveredEventStartValue.
On this page: