Gi Optimization; Troubleshooting - ABB RELION 620 Series Communication Protocol Manual

Section 3
Vendor-specific implementation
3.6.1
3.7
Table 13:

Troubleshooting

Condition Cause
Slow or no update of Protocol data is available for active IED applications
data, reports disabled and the IED system. Active IED applications mean the
function blocks that have been added into the
protection relay's configuration using the Application
Configuration tool in PCM600. IED system data is
always available and is not dependent on the
application configuration.
A protection relay variant has a standard application
configuration that has been done in advance. This
configuration can be modified with PCM600. It is also
possible to start a completely new configuration from an
emptied configuration state in Application
Configuration. When a new IED configuration is created
from an empty configuration state, an additional
PCM600 check must be done at the end.
30

GI optimization

The master should initiate a GI always after the IED has reported a Class 1 event buffer
overflow. The IED starts then to send GI data through the Class 1 event buffer. As the
standard defines, new events always have higher send priority than GI data in the
IED's Class 1 buffer. The standard also defines that all data that are subject to GI is
sent by the IED.
Optimization of GI data is a non-standard feature. As default the Optimize GI n
parameter is set to "Standard behaviour", meaning that the GI cycle operates as
defined by the standard. GI optimization strives to send less data to the master through
the Class 1 report. The GI optimization in the IED is based on two facts:
• It is enough to send a certain Class 1 data once to the master after a GI initiation.
This could be either the GI data report or a spontaneously updated data report. In
either case the master has the true position of the Class 1 data in its database.
• The IED also remembers which specific Class 1 data objects changes that has
overflown. After the GI initiation only these marked Class 1 data objects are
reported through the GI cycle.
Table 12: GI optimization alternatives
Parameter value Description
Standard behaviour No optimization.
Skip spontaneous Enables the IED to not send GI data for those objects that already have been
spontaneously updated by the IED (that is, sent as Class 1 events) after the
initiation of a GI.
Only overflown Enables the IED to send only the Class 1 data that it knows have overflown in the
Class 1 buffer. The first GI cycle initiated after a master Reset CU or Reset FCB
does not use this feature, that is, the IED keeps track of that it actually has
reported a value at least once to the master since the last reset.
Combined Combines the two optimization features explained above.
Troubleshooting
Remedy
Select manually the check boxes for clients of all visible
61850 data sets in the IEC 61850 Configuration tool,
see the engineering guide for detailed instructions. This
procedure enables reporting for the data sets, and
report control blocks should appear on the Report
Control tab.
Communication Protocol Manual
1MRS757647 C
620 series