GE P741, Technical Manual

Page: 496 / 560

SCADA Communications P74x/EN SC/Na7
MiCOM P741, P742, P743 (SC) 13-21
SC
3.3.2.1 Configuration Banks
To promote version management and minimize down-time during system upgrades and
maintenance, the relays have incorporated a mechanism consisting of multiple configuration
banks. These configuration banks are categorized as:
•
Active Configuration Bank
•
Inactive Configuration Bank
Any new configuration sent to the relay is automatically stored into the inactive configuration
bank, therefore not immediately affecting the current configuration. Both active and inactive
configuration banks can be extracted at anytime.
When the upgrade or maintenance stage is complete, the IED Configurator tool can be used
to transmit a command (to a single IED) authorizing the activation of the new configuration
contained in the inactive configuration bank, by switching the active and inactive
configuration banks. This technique ensures that the system down-time is minimized to the
start-up time of the new configuration. The capability to switch the configuration banks is
also available via the ‘IED CONFIGURATOR’ column.
For version management, data is available in the ‘IED CONFIGURATOR’ column in the relay
user interface, displaying the SCL Name and Revision attributes of both configuration banks.
3.3.2.2 Network connectivity
Note: This section presumes a prior knowledge of IP addressing and related
topics. Further details on this topic may be found on the Internet
(search for IP Configuration) and in numerous relevant books.
Configuration of the relay IP parameters (IP Address, Subnet Mask, Gateway) and SNTP
time synchronization parameters (SNTP Server 1, SNTP Server 2) is performed by the IED
Configurator tool, so if these parameters are not available via an SCL file, they must be
configured manually.
If the assigned IP address is duplicated elsewhere on the same network, the remote
communications will operate in an indeterminate way. However, the relay will check for a
conflict on every IP configuration change and at power up. An alarm will be raised if an IP
conflict is detected.
The relay can be configured to accept data from networks other than the local network by
using the ‘Gateway’ setting.
3.4 The data model of MiCOM relays
The data model naming adopted in the Px30 and Px40 relays has been standardized for
consistency. Hence the Logical Nodes are allocated to one of the five Logical Devices, as
appropriate, and the wrapper names used to instantiate Logical Nodes are consistent
between Px30 and Px40 relays.
The data model is described in the Model Implementation Conformance Statement (MICS)
document, which is available separately. The MICS document provides lists of Logical
Device definitions, Logical Node definitions, Common Data Class and Attribute definitions,
Enumeration definitions, and MMS data type conversions. It generally follows the format
used in Parts 7-3 and 7-4 of the IEC 61850 standard.
3.5 The communication services of MiCOM relays
The IEC 61850 communication services which are implemented in the Px30 and Px40 relays
are described in the Protocol Implementation Conformance Statement (PICS) document,
which is available separately. The PICS document provides the Abstract Communication
Service Interface (ACSI) conformance statements as defined in Annex A of Part 7-2 of the
IEC 61850 standard.