DataReport
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 Data Reports (Unbuffered Reports):
- Data Reports, or Unbuffered Reports, are sent directly from the IED (Intelligent Electronic Device) to the client without any intermediary storage of the report data within the IED.
- If there is a communication interruption or if the client is unable to receive the report (for example, due to network congestion or client unavailability), the reports that occur during this time are lost. There is no mechanism to retrieve missed reports once the communication is restored.
- This type of reporting is simpler and requires less memory and processing power within the IED, making it suitable for applications where real-time monitoring is essential, and data loss during communication failures is acceptable.
The item type has the following properties:
| Name | Description | ID | Flags |
|---|---|---|---|
| SrcItmID | Data reference to the report, on the form LDName/LNodeName.RP.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 | |
| Reserved | if the setting was successful the RCB will be reserved exclusively for this client | 17010 | |
| 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 | |
| Report ID | The report ID identifies the RCB that has caused the generation of the report. It equals the RptID field of the RCB. | 17014 | |
| Optional fields | A bitstring where each bit indicates whether an optional field is included in the reports caused by this RCB. 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 | |
| Sequence number | the current sequence number of the RCB. After sending a report the RCB will increment the sequence number by one | 17017 | ReadOnly |