GE C60 Instruction Manual page 318

SYSTEM SETUP CHAPTER 5: SETTINGS
The UR also supports the option to apply no filtering to the synchrophasors. If no filtering is applied (PMU Class = None),
according to the standard, the ClcMth attribute is PRES. The semantic of the ClcMth used is not carried in the individual DO
and so it is recommended that one of letters of the prefix on the instantiated LNs be set to "P" or "M" accordingly in order
to differentiate. For firmware versions 7.0 and later, only FCDA data is supported. The PMU Implementation by UR Device
table earlier indicates the maximum size of each PMU data set for version 7.2 and later using FCDA data (non-structured
data).
5.5.7.4 Example: Protection synchrophasors data set with reporting rate 60 frames/second
This example gives the protection synchrophasors data set with a reporting rate of 60 frames per second (P60MMXU1). See
the figure earlier, Logical Nodes Supported in Each Logical Device. This data or list of items, as shown in the following
figure, is not available to the UR setup program but is available to be mapped by the user into a selected aggregator or
aggregators dataset. The logical device name (LDName) of each PMU LD is a 64 character user setting. The IEEE C37.118
STN and IDCode is to be mapped as a concatenated value in the (d)escription field of LPL CDC of the NamPlt DO in LLN0.
The mapping is implemented as STN-IDCode (text string).
From each PMU, the user selects the phasor information of interest that is mapped into the selected aggregator datset(s).
For version 7.0 and later, only FCDA data is supported.
Figure 5-77: Data set created from user-selected internal items
5
5.5.7.5 Example: Creation of different data sets
The aggregators allow the aggregation of phasors from multiple PMUs (with the same reporting rate) into a single custom
data set to optimize bandwidth when streaming.
5-150 C60 BREAKER PROTECTION SYSTEM – INSTRUCTION MANUAL