EasyManua.ls Logo

Alstom MiCOM P546 - 5.3.2.1 Configuration banks; 5.3.2.2 Network connectivity; 5.4 The data model of MiCOM relays

Alstom MiCOM P546
1024 pages
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
P54x/EN SC/La4 SCADA Communications
(SC) 13-30
MiCOM P543, P544, P545 & P546
SC
Other features include the extraction of configuration data for viewing and editing, and a
sophisticated error checking sequence which ensures that the configuration data is valid for
sending to the IED and that the IED will function within the context of the substation.
To aid the user, some configuration data is available in the ‘IED CONFIGURATOR’ column
of the relay user interface, allowing read-only access to basic configuration data.
5.3.2.1 Configuration banks
To p
romote version management and minimize down-time during system upgrades and
maintenance, the MiCOM 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.
5.3.2.2 Network connectivity
Not
e: 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.
5.4 The data model of MiCOM relays
The data mo
del naming adopted in the 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 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.

Table of Contents

Related product manuals