5-136
T60 Transformer Protection System
GE Multilin
5.4 SYSTEM SETUP
5 SETTINGS
5
The following is a summary of LNs that are in each Logical Device (LD2 through LD7):
- PxxxMMXU1 ClcMth = P-Class (Note Vaux is mapped to Vneut of MMXU)
- PxxxMSQI1 ClcMth = P-CLASS
- MxxMMXU1 ClcMth = M-Class (Note Vaux is mapped to Vneut of MMXU)
- MxxMSQI1 ClcMth = M-CLASS
- NxxMMXU1 ClcMth = M-Class (Note Vaux is mapped to Vneut of MMXU)
- NxxMSQI1 ClcMth = M-CLASS
- GGIO1 which contains 16 digital status indication points and 16 analog points. The Analog GGIO values are selectable
from any FlexAnalog value in the UR.
The Synchro Logical Nodes in an LD report at the same rate as set in the PMUn Basic Configuration setting. This is
reflected in the instantiation of the Data Object – SmpRate in the msvcb## of LLN0 in the LD1. SmpRate is a Read
Only Integer Status (INS).
When the first PMU from any LD is mapped into an aggregator, the aggregator inherits the Sample Rate (SmpRate) and
IEEE C37.118 Class (P or M) of that PMU. The value of the SmpRate DO in the Report Control Block is set based on the
value of the Sample Rate in the PMU. The Class of the Dataset are mapped into the MSVID of the Dataset (see text below
for the overall name of the MSVID). If other PMUs are mapped into the same aggregator with different Sample Rates or
from different classes, then a Self-Test error (DatSetErr) is set and dataset transmission is blocked.
A setting value – MSVID – is created with a maximum input range of 56 characters (=64 less 6 for the IDCode less 2 for the
Class).
The value of MSVID in the dataset is a concatenation of the aggregator IDCode and the MSVID setting value in the format:
MSVID-AggregatorIDCode-CLASS where CLASS is P, M, or N (for None) – depending on the Class of the first PMU
included in the Aggregator.
Synchrophasor Rectangular Format and Integer data types are NOT supported in IEC 61850-90-5 (only supported
with IEEE C37.118) and not to set — GGIO1 which contains 16 digital status indication points — aggregated as a
16 bit bitstring and 16 analog points. The Analog GGIO values are selectable from any FlexAnalog value in the UR.
For version 7.0 and later the description fields for the phasors, analog and digital channels are populated with the
16 character name field provided within the Basic Configuration menu. Additionally, the names of the 16 binary
points are implemented as numbered descriptions — d1, d2, d3, and so on. The number of descriptions are equal
to the number of bits configured in the 16 bit digital status word.
All bitstrings less than or equal to 32 bits in length map into a 32 bit bitstring in an IEC 61850-90-5 dataset.
The Value of the Nominal Frequency of the chassis is instantiated as a DO in LPHD of LD1. The value is named
HzNom and is an Integer Status (INS).
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 version 7.0 and later, only FCDA data is supported. The
Implementation by Model Number
table earlier
describes the maximum size of each PMU data set for version 7.2 and later using FCDA data (non-structured data).
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).
NOTE
NOTE
NOTE
Summary of Contents for T60
Page 6: ...vi T60 Transformer Protection System GE Multilin TABLE OF CONTENTS ...
Page 14: ...xiv T60 Transformer Protection System GE Multilin TABLE OF CONTENTS ...
Page 34: ...1 20 T60 Transformer Protection System GE Multilin 1 5 USING THE RELAY 1 GETTING STARTED 1 ...
Page 490: ...5 344 T60 Transformer Protection System GE Multilin 5 10 TESTING 5 SETTINGS 5 ...
Page 522: ...6 32 T60 Transformer Protection System GE Multilin 6 5 PRODUCT INFORMATION 6 ACTUAL VALUES 6 ...
Page 536: ...7 14 T60 Transformer Protection System GE Multilin 7 1 COMMANDS 7 COMMANDS AND TARGETS 7 ...
Page 568: ...10 12 T60 Transformer Protection System GE Multilin 10 6 DISPOSAL 10 MAINTENANCE 10 ...
Page 596: ...A 28 T60 Transformer Protection System GE Multilin A 1 PARAMETER LISTS APPENDIX A A ...
Page 716: ...B 120 T60 Transformer Protection System GE Multilin B 4 MEMORY MAPPING APPENDIX B B ...
Page 762: ...E 10 T60 Transformer Protection System GE Multilin E 1 IEC 60870 5 104 PROTOCOL APPENDIX E E ...
Page 774: ...F 12 T60 Transformer Protection System GE Multilin F 2 DNP POINT LISTS APPENDIX F F ...