Sunteți pe pagina 1din 2

IEC 61850 Reporting and Deadband explanation.

The buffer that is available for each buffered report control is 120,000 bytes. But what does this mean?? The buffer stores ASN.1 encoded data that is also wrapped with an ethernet frame. The unit that is used in MMS to describe this is a PDU (Protocol Data Unit). The maximum size of a PDU is 12,000 bytes. So if a particular report data set required a complete PDU you could fit 10 in the buffer. However, we have limited the maximum data set size to 500 FCDAs (Functionally Constrained Data Attributes). If you look at the structure of the Logical Nodes, the lowest level is the FCDA, i.e. stVal, q, t, etc. For example, if we assume that a dataset is entirely composed of measurement values, all floats, so 500 floats (4 bytes), ASN.1 encoded (2 bytes overhead), gives a report size of 3,000 bytes, not including the ethernet frame. You can see that a lot of data can fit into a PDU. However, there are multiple optional fields that the client can enable for the report

Depending on what the client enables the size can grow significantly. For example adding the data-reference option adds up to 64 bytes for each FCDA. With all that said, there are only two situations that the entire dataset is contained in a report, General Interrogation and Periodic Update. In all other cases the data in a report are only those points that have changed during BufTm, so a typical report is relatively small. With small reports the buffer can hold up to 200 reports. Unbuffered reports are not as limited because they can be broken into segments if necessary and so are only limited by the 500 FCDA dataset size.

Deadbands
Dead bands are somewhat tricky. In a basic sense, there is no deadband for reporting. Deadbands are used in any Logical Node that has a measurement value. In each of these logical nodes there are instantaneous values and magnitude values. Based on the definition the magnitude value in the logical node is the deadbanded instantaneous value. In each of these logical nodes we have created a deadband function to make it work the way the standard requires. Architect does not have the ability to manipulate these values. There are many features and functions within our SCL file that Architect cannot (TODAY) manipulate. This is something we want Architect to be able to do, but it cannot. If there is a need for changing the deadbands in the files then TODAY someone from SEL will need to assist in the process. Here is a brief description as to what we are doing.

So in our file we have identified a max value to base the deadband % on. Then added a multiplier for 0.001% to get the deadband range as a percentage of the max. In our case we are always assuming a min of zero (0). Here is an example from our meter data: MMXU Phase Voltage <DAI name="db" esel:datasrc="imm:750000"> <esel:Val>10000</esel:Val> </DAI> For this example we have taken a max value of 750,000 volts and a multiplier on the % of 10,000, which give a deadband of 10% on the max, or 75 kV step. These values are in the ICD file and can be manually edited for a given application.

S-ar putea să vă placă și