BufferedReport
Reporting allows a server to send data based on events and without explict request by the client. What data is sent and which events that cause the reports to be sent are configured through the attributes of the item.
Main characteristics of Buffered Reports:
- Buffered Reports involve an intermediary buffering of report data within the IED before it is sent to the client. This buffer stores a sequence of reports.
- In case of a communication interruption or if the client is temporarily unable to receive reports, the buffered reports are stored in the IED and can be retrieved once the communication is restored. This ensures that no data is lost during the period of communication failure.
- Buffered reporting is more complex and requires additional memory and processing resources within the IED. It is essential for applications where data continuity and retrieval of missed reports are critical, such as in disturbance recording or where detailed post-event analysis is required.
The item type has the following properties:
| Name | Description | ID | Flags |
|---|---|---|---|
| SrcItmID | Data reference to the buffered report, on the form LDName/LNodeName.BR.reportName. [string] | 5030 | Persisted |
| DataSet | The DataSet reference, must be on the form LDName/LNodeName.dataSetName. [string] | 17007 | |
| Integrity period [ms] | The integrity period specifies the interval for the periodic sending of intergrity messages in report if integrity is specified as trigger option in the report. [0-4,294,967,295] | 17008 | |
| Trigger options | Specifies which events will trigger reports | 17009 | |
| GI | Setting this parameter to true will initiate a report to be sent to the client. This report will contain all the data of the associated data set. The GI parameter will be reset to false automatically by the server once the report has been sent | 17011 | |
| Enabled | By setting this variable to true reporting will be enabled. Note that changing/writing and configuration fields of the RCB will fail as long as reporting is enabled | 17012 | |
| ResvTms [ms] | Value of -1 = reserved by configuration for a certain set of clients, value 0 = report is not reserved, value > 0 = the time that the reservation shall be maintained after the association was closed or interrupted. [-32,768 to 32,767] | 17013 | |
| Report ID | The report ID identifies the RCB that has caused the generation of the report. [string] | 17014 | |
| Optional fields | A bitstring where each bit indicates whether an optional field is included in the reports. The following optional fields exist: sequence-number, report- timestamp, reason-for-inclusion, data-set-name, data-reference, buffer-overflow, entryID, segmentation, and conf-revision. For URCBs the values of buffer-overflow and entryID are ignored | 1705 | |
| Buffer time [ms] | For buffered reports, this is the interval between each report sent from the server. [0-4,294,967,295] | 17016 | |
| Purge buffer | If the rate of report generation exceeds the transmission or processing capacity, the buffer may become full. If enabled, older reports in the buffer may be purged (deleted) to make room for new reports. This ensures that the most recent and relevant data is available for transmission, at the cost of losing older, untransmitted reports. | 17018 | |
| Sequence number | Number of received events from the server, incremented each time a new update is received from the server. | 17017 | ReadOnly |
Notes:
- Make sure DataSet item that corresponds to the DataSet reference used in the report is present.