ABB Relion 670 Series Applications Manual page 115

1MRK 511 401-UEN Rev. K
ReportRates, or if rule 3 is violated. In such cases, the synchrophasors may only fail to comply
(with small error) in some particular test case(s).
For more information regarding 3PHSUM block application, please refer to the Application
Manual under section Basic IED functions.
6.2.4 Setting guidelines
Based on the functionality and appearance in PCM600, the PMU reporting functionality is
categorized into 4 different categories (function block) as follows:
1. PMUREPORT
2. PHASORREPORT
3. ANALOGREPORT
4. BINARYREPORT
Each category has its corresponding parameter settings except for BINARYREPORT function
block which does not have any specific parameters and settings.
1. PMUREPORT is the main function block which controls the operation of other PMU
reporting function blocks. Each instance of PMUREPORT function block has the following
parameters:
•
•
•
•
•
•
Bay control REC670
Application manual
Operation : Enables/Disables the operation of the corresponding instance of PMU
reporting functionality by choosing
SvcClass : It refers to the 1-byte SVC_CLASS field of the configuration frame 3
(CFG-3) organization defined in 60255-118-2011 message format. Here the user can
select the performance class (service class) used for synchrophasor data
measurement according to 60255-118-2011 standard. The options are
class .
Note: There are 2 PMUREPORT instances available (PMUREPORT:1 and
PMUREPORT:2) corresponding to 2 independent data streams. The user can set
different or identical service class for each data stream. In case of different service
classes, special rules shall be considered in PCM600 ACT for the connection of
preprocessor blocks (SMAI) and 3PHSUM blocks to PHASORREPORT blocks. More
details are available under section
PCM600 Application Configuration Tool
Global_PMU_ID : It refers to the 16-byte G_PMU_ID field of the configuration frame 3
(CFG-3) organization defined in 60255-118-2011 message format. It is a 16-character
(128 bits) user-assigned value which can be sent with the configuration 3 message. It
allows uniquely identifying PMUs in a system that has more than 65535 PMUs. The
coding for the 16 bytes is left to the user for assignment.
PMUdataStreamIDCODE : It refers to the 2-byte IDCODE field of the configuration
frame and data frame organization defined in 60255-118-2011 message format. It is
a user assigned ID number (1-65534) for each data stream sent out from the PMU.
This is especially important when having multiple data streams (multiple PMU
functionality).
Note: The data stream IDCODE is a unique code for each and every data stream in
one physical PMU device. In the IED, there are 2 PMUREPORT instances available
(PMUREPORT:1 and PMUREPORT:2) corresponding to 2 independent data streams.
The user must set different IDCODEs for each instance.
PhasorFormat : It refers to the Bit 0 of the FORMAT field of the configuration frames
1, 2 and 3 organization defined in 60255-118-2011 message format. Here the user can
select the format of the calculated synchrophasors. The options are
Polar format. Rectangular format represents the synchrophasor as real and
imaginary values, real value first (a + bj) while the Polar format represents the
synchrophasor as magnitude and angle, magnitude first (A e
PhasorDataType : It refers to the Bit 1 of the FORMAT field of the configuration
frames 1, 2 and 3 organization defined in 60255-118-2011 message format. Here the
© Copyright 2017 Hitachi Power Grids. All rights reserved
On / Off setting.
PMU Report Function Blocks Connection Rules in
(ACT).
Section 6
Wide area measurement system
GUID-83969957-DABF-4B9B-95C7-B9F0AF6E647A v3
P class or M
Rectangular or
jα
).
109