GE
Grid Solutions
MiCOM P40 Agile
P746
Technical Manual
Numerical Busbar Protection
Hardware version: M
Software version: 91
Publication reference: P746/EN M/J43
Imagination at work
Grid Solutions
St Leonards Building
Redhill Business Park
Stafford, ST16 1WT, UK
+44 (0) 1785 250 070
www.gegridsolutions.com/contact
© 2021 GE. All rights reserved. Information contained in this document is indicative only.
No representation or warranty is given or should be relied on that it is complete or correct or will apply to any particular project.
This will depend on the technical and commercial circumstances. It is provided without liability and is subject to change without notice.
Reproduction, use or disclosure to third parties, without express written authority, is strictly prohibited.
P746/EN M/J43
CONTENTS
Section 1
Introduction
P746/EN IT/J43
IT
Section 2
Technical Data
P746/EN TD/J43
TD
Section 3
Getting Started
P746/EN GS/J43
GS
Section 4
Settings
P746/EN ST/J43
ST
Section 5
Operation
P746/EN OP/J43
OP
Section 6
Application Notes
P746/EN AP/J43
AP
Section 7
Programmable Logic
P746/EN PL/J43
PL
Section 8
Measurements and Recording
P746/EN MR/J43
MR
Section 9
Firmware Design
P746/EN FD/J43
FD
Section 10
Commissioning and Maintenance
P746/EN CM/J43
CM
Section 11
Maintenance
P746/EN MT/J43
MT
Section 12
Troubleshooting
P746/EN TS/J43
TS
Section 13
SCADA Communications
P746/EN SC/J43
Section 14
Symbols and Glossary
P746/EN SG/J43
Section 15
Installation
P746/EN IN/I43
Section 16
Remote HMI
P746/EN HI/I43
Section 17
Cyber Security
P746/EN CS/J43
SC
SG
IN
HI
CS
Appendix A
Ordering Options
Appendix B
Wiring Diagrams
Appendix C
Firmware and Service Manual Version History
Safety Section
P746/EN SS/J43
SS
SAFETY SECTION
P746/EN SS/J43
SS
Safety Section
Safety Section
P746/EN SS/J43
(SS) - 1
CONTENTS
1.
2.
3.
4.
OVERVIEW
HEALTH AND SAFETY
SYMBOLS
INSTALLING, COMMISSIONING AND SERVICING
3
4
5
6
4.1
Lifting Hazards
6
4.2
Electrical Hazards
6
5.
6.
DECOMMISSIONING AND DISPOSAL
REGULATORY COMPLIANCE
12
13
6.1
EMC Compliance: 2014/30/EU
13
6.2
LVD Compliance: 2014/35/EU
13
6.3
R&TTE Compliance: 2014/53/EU
13
6.4
UL/CUL Compliance
13
SS
P746/EN SS/J43
(SS) - 2
SS
Safety Section
Safety Section
P746/EN SS/J43
(SS) - 3
1.
OVERVIEW
This chapter provides information about the safe handling of the equipment. The equipment
must be properly installed and handled in order to maintain it in a safe condition and to keep
personnel safe at all times. You must be familiar with information contained in this chapter
before unpacking, installing, commissioning, or servicing the equipment.
SS
P746/EN SS/J43
Safety Section
(SS) - 4
2.
HEALTH AND SAFETY
Personnel associated with the equipment must be familiar with the contents of this Safety
Information.
SS
When electrical equipment is in operation, dangerous voltages are present in certain parts of
the equipment. Improper use of the equipment and failure to observe warning notices will
endanger personnel.
Only qualified personnel may work on or operate the equipment. Qualified personnel are
individuals who are:
•
familiar with the installation, commissioning, and operation of the equipment and the
system to which it is being connected.
•
familiar with accepted safety engineering practises and are authorised to energise and
de-energise equipment in the correct manner.
•
trained in the care and use of safety apparatus in accordance with safety engineering
practises
•
trained in emergency procedures (first aid).
The documentation provides instructions for installing, commissioning and operating the
equipment. It cannot, however cover all conceivable circumstances. In the event of questions
or problems, do not take any action without proper authorisation. Please contact your local
sales office and request the necessary information.
Safety Section
P746/EN SS/J43
(SS) - 5
3.
SYMBOLS
Throughout this manual you will come across the following symbols. You will also see these
symbols on parts of the equipment.
SS
Refer to equipment documentation. Failure to do so could result in
damage to the equipment
Risk of electric shock
Risk of damage to eyesight
Earth terminal. Note: This symbol may also be used for a protective conductor (earth) terminal if that
terminal is part of a terminal block or sub-assembly.
Protective conductor (earth) terminal
Instructions on disposal requirements
The term 'Earth' used in this manual is the direct equivalent of the North American term
'Ground'.
P746/EN SS/J43
Safety Section
(SS) - 6
4.
INSTALLING, COMMISSIONING AND SERVICING
4.1
Lifting Hazards
SS
Many injuries are caused by:
•
Lifting heavy objects
•
Lifting things incorrectly
•
Pushing or pulling heavy objects
•
Using the same muscles repetitively
Plan carefully, identify any possible hazards and determine how best to move the product.
Look at other ways of moving the load to avoid manual handling. Use the correct lifting
techniques and Personal Protective Equipment (PPE) to reduce the risk of injury.
4.2
Electrical Hazards
All personnel involved in installing, commissioning, or servicing this
equipment must be familiar with the correct working procedures.
Consult the equipment documentation before installing, commissioning, or
servicing the equipment.
Always use the equipment as specified. Failure to do so will jeopardise the
protection provided by the equipment.
Removal of equipment panels or covers may expose hazardous live parts.
Do not touch until the electrical power is removed. Take care when there is
unlocked access to the rear of the equipment.
Isolate the equipment before working on the terminal strips.
Use a suitable protective barrier for areas with restricted space, where there
is a risk of electric shock due to exposed terminals.
Disconnect power before disassembling. Disassembly of the equipment
may expose sensitive electronic circuitry. Take suitable precautions
against electrostatic voltage discharge (ESD) to avoid damage to the
equipment.
NEVER look into optical fibres or optical output connections. Always use
optical power meters to determine operation or signal level.
Safety Section
P746/EN SS/J43
(SS) - 7
Testing may leave capacitors charged to dangerous voltage levels.
Discharge capacitors by reducing test voltages to zero before
disconnecting test leads.
SS
Operate the equipment within the specified electrical and environmental
limits.
Before cleaning the equipment, ensure that no connections are energised.
Use a lint free cloth dampened with clean water.
Contact fingers of test plugs are normally protected by petroleum jelly, which should not
be removed.
4.3
UL/CSA/CUL Requirements
The information in this section is applicable only to equipment carrying UL/CSA/CUL
markings.
Equipment intended for rack or panel mounting is for use on a flat surface
of a Type 1 enclosure, as defined by Underwriters Laboratories (UL).
To maintain compliance with UL and CSA/CUL, install the equipment using
UL/CSA-recognised parts for: cables, protective fuses, fuse holders and
circuit breakers, insulation crimp terminals, and replacement internal
batteries.
4.4
Fusing Requirements
Where UL/CSA listing of the equipment is required for external fuse
protection, a UL or CSA Listed fuse must be used for the auxiliary supply.
The listed protective fuse type is: Class J time delay fuse, with a maximum
current rating of 15 A and a minimum DC rating of 250 V dc (for example
type AJT15).
Where UL/CSA listing of the equipment is not required, a high rupture
capacity (HRC) fuse type with a maximum current rating of 16 Amps and a
minimum dc rating of 250 V dc may be used for the auxiliary supply (for
example Red Spot type NIT or TIA).
For P50 models, use a 1A maximum T-type fuse.
For P60 models, use a 4A maximum T-type fuse.
Digital input circuits should be protected by a high rupture capacity NIT or
TIA fuse with maximum rating of 16 A. for safety reasons, current
transformer circuits must never be fused. Other circuits should be
appropriately fused to protect the wire used.
P746/EN SS/J43
Safety Section
(SS) - 8
CTs must NOT be fused since open circuiting them may produce lethal
hazardous voltages
SS
4.5
Equipment Connections
Terminals exposed during installation, commissioning and maintenance
may present a hazardous voltage unless the equipment is electrically
isolated.
Tighten M4 clamping screws of heavy duty terminal block connectors to a
nominal torque of 1.3 Nm.
Tighten captive screws of terminal blocks to 0.5 Nm minimum and 0.6 Nm
maximum.
Always use insulated crimp terminations for voltage and current
connections.
Always use the correct crimp terminal and tool according to the wire size.
Watchdog (self-monitoring) contacts are provided to indicate the health of
the device on some products. We strongly recommend that you hard wire
these contacts into the substation's automation system, for alarm
purposes.
4.6
Protection Class 1 Equipment Requirements
Earth the equipment with the supplied PCT (Protective Conductor Terminal).
Do not remove the PCT.
The PCT is sometimes used to terminate cable screens. Always check the
PCT’s integrity after adding or removing such earth connections.
Use a locknut or similar mechanism to ensure the integrity of studconnected PCTs.
Safety Section
P746/EN SS/J43
(SS) - 9
The recommended minimum PCT wire size is 2.5 mm² for countries whose
mains supply is 230 V (e.g. Europe) and 3.3 mm² for countries whose mains
supply is 110 V (e.g. North America). This may be superseded by local or
country wiring regulations.
For P60 products, the recommended minimum PCT wire size is 6 mm². See
product documentation for details.
The PCT connection must have low-inductance and be as short as possible.
All connections to the equipment must have a defined potential.
Connections that are pre-wired, but not used, should be earthed, or
connected to a common grouped potential.
4.7
Pre-energisation Checklist
Check voltage rating/polarity (rating label/equipment documentation).
Check CT circuit rating (rating label) and integrity of connections.
Check protective fuse or miniature circuit breaker (MCB) rating.
Check integrity of the PCT connection.
Check voltage and current rating of external wiring, ensuring it is
appropriate for the application.
4.8
Peripheral Circuitry
Do not open the secondary circuit of a live CT since the high voltage
produced may be lethal to personnel and could damage insulation. Short
the secondary of the line CT before opening any connections to it.
For most GE equipment with ring-terminal connections, the threaded terminal block for
current transformer termination is automatically shorted if the module is removed.
Therefore external shorting of the CTs may not be required. Check the equipment
documentation and wiring diagrams first to see if this applies.
Where external components such as resistors or voltage dependent
resistors (VDRs) are used, these may present a risk of electric shock or
burns if touched.
SS
P746/EN SS/J43
Safety Section
(SS) - 10
SS
Take extreme care when using external test blocks and test plugs such as
the MMLG, MMLB and P990, as hazardous voltages may be exposed.
Ensure that CT shorting links are in place before removing test plugs, to
avoid potentially lethal voltages.
Data communication cables with accessible screens and/or screen
conductors, (including optical fibre cables with metallic elements), may
create an electric shock hazard in a sub-station environment if both ends of
the cable screen are not connected to the same equipotential bonded
earthing system.
To reduce the risk of electric shock due to transferred potential hazards:
i. The installation shall include all necessary protection measures to ensure
that no fault currents can flow in the connected cable screen conductor.
ii. The connected cable shall have its screen conductor connected to the
protective conductor terminal (PCT) of the connected equipment at both
ends. This connection may be inherent in the connectors provided on the
equipment but, if there is any doubt, this must be confirmed by a continuity
test.
iii. The protective conductor terminal (PCT) of each piece of connected
equipment shall be connected directly to the same equipotential bonded
earthing system.
iv. If, for any reason, both ends of the cable screen are not connected to the
same equipotential bonded earth system, precautions must be taken to
ensure that such screen connections are made safe before work is done to,
or in proximity to, any such cables.
v. No equipment shall be connected to any download or maintenance
circuits or connectors of this product except temporarily and for
maintenance purposes only.
vi. Equipment temporarily connected to this product for maintenance
purposes shall be protectively earthed (if the temporary equipment is
required to be protectively earthed), directly to the same equipotential
bonded earthing system as the product.
Small Form-factor Pluggable (SFP) modules which provide copper Ethernet
connections typically do not provide any additional safety isolation. Copper
Ethernet SFP modules must only be used in connector positions intended
for this type of connection.
Safety Section
P746/EN SS/J43
(SS) - 11
4.9
Upgrading/Servicing
Do not insert or withdraw modules, PCBs or expansion boards from the
equipment while energised, as this may result in damage to the equipment.
Hazardous live voltages would also be exposed, endangering personnel.
Internal modules and assemblies can be heavy and may have sharp edges.
Take care when inserting or removing modules into or out of the IED.
SS
P746/EN SS/J43
Safety Section
(SS) - 12
5.
SS
DECOMMISSIONING AND DISPOSAL
Before decommissioning, completely isolate the equipment power supplies
(both poles of any dc supply). The auxiliary supply input may have
capacitors in parallel, which may still be charged. To avoid electric shock,
discharge the capacitors using the external terminals before
decommissioning.
Avoid incineration or disposal to water courses. Dispose of the equipment
in a safe, responsible and environmentally friendly manner, and if
applicable, in accordance with country-specific regulations.
Safety Section
P746/EN SS/J43
(SS) - 13
6.
REGULATORY COMPLIANCE
Compliance with the European Commission Directive on EMC and LVD is demonstrated
using a technical file.
SS
6.1
EMC Compliance: 2014/30/EU
The product specific Declaration of Conformity (DoC) lists the relevant harmonised
standard(s) or conformity assessment used to demonstrate compliance with the EMC
directive.
6.2
LVD Compliance: 2014/35/EU
The product specific Declaration of Conformity (DoC) lists the relevant harmonized
standard(s) or conformity assessment used to demonstrate compliance with the LVD
directive.
Safety related information, such as the installation I overvoltage category, pollution degree
and operating temperature ranges are specified in the Technical Data section of the relevant
product documentation and/or on the product labelling.
Unless otherwise stated in the Technical Data section of the relevant product documentation,
the equipment is intended for indoor use only. Where the equipment is required for use in an
outdoor location, it must be mounted in a specific cabinet or housing to provide the
equipment with the appropriate level of protection from the expected outdoor environment.
6.3
R&TTE Compliance: 2014/53/EU
Radio and Telecommunications Terminal Equipment (R&TTE) directive 2014/53/EU.
Conformity is demonstrated by compliance to both the EMC directive and the Low Voltage
directive, to zero volts.
6.4
UL/CUL Compliance
If marked with this logo, the product is compliant with the requirements of the Canadian and
USA Underwriters Laboratories.
The relevant UL file number and ID is shown on the equipment.
P746/EN SS/J43
(SS) - 14
SS
Safety Section
Introduction
P746/EN IT/J43
MiCOM P40 Agile P746
(IT) 1-1
IT
INTRODUCTION
Hardware Suffix:
M
Software Version:
91
P746/EN IT/J43
(IT) 1-2
IT
Introduction
MiCOM P40 Agile P746
Introduction
MiCOM P40 Agile P746
P746/EN IT/J43
(IT) 1-3
CONTENTS
1
MICOM DOCUMENTATION STRUCTURE
5
2
INTRODUCTION TO MICOM
7
2.1
Compliance
7
3
PRODUCT SCOPE
8
3.1
Ordering Options
8
3.2
Functional Overview
8
FIGURES
Figure 1: Functional diagram
9
IT
P746/EN IT/J43
(IT) 1-4
IT
Introduction
MiCOM P40 Agile P746
Introduction
P746/EN IT/J43
MiCOM P40 Agile P746
1
(IT) 1-5
MICOM DOCUMENTATION STRUCTURE
This manual provides a functional and technical description of the MiCOM protection relay
and a comprehensive set of instructions for the relay’s use and application.
The section contents are summarized below:
P746/EN IT
Introduction
This chapter provides some general information about the technical manual and an
introduction to the device(s) described in this technical manual.
P746/EN TD
Technical Data
This chapter provides technical data including setting ranges, accuracy limits, recommended
operating conditions, ratings and performance data. Compliance with norms and
international standards is quoted where appropriate.
P746/EN GS
Getting Started
This chapter provides information about the product's hardware design. It also includes
details on how to configure the device, particularly with respect to the communications setup,
as well as a description of the common methodology used to configure the device in general.
P746/EN ST
Settings
This chapter provides a list of all relay settings, including ranges, step sizes and defaults,
together with a brief explanation of each setting.
P746/EN OP
Operation
This chapter provides a comprehensive and detailed functional description of all protection
and non-protection functions.
P746/EN AP
Application Notes
This chapter includes a description of common power system applications of the relay,
calculation of suitable settings, some typical worked examples, and how to apply the settings
to the relay.
P746/EN PL
Programmable Logic
This chapter provides an overview of the programmable scheme logic and a description of
each logical node.
P746/EN MR
Measurements and Recording
This chapter provides a description of the relays recording and measurements functions
including the configuration of the event and disturbance recorder and measurement
functions.
P746/EN FD
Firmware Design
This chapter provides information about the product's hardware and software.
P746/EN CM
Commissioning
This chapter provides information on how to commission the relay.
P746/EN MT
Maintenance
This chapter provides details of how to maintain products based on the Px4x and P40Agile
platforms.
P746/EN TS
Troubleshooting
This chapter provides details of how to troubleshoot products based on the Px4x and
P40Agile platforms. Includes information on who to contact in GE for advice.
IT
P746/EN IT/J43
(IT) 1-6
Introduction
MiCOM P40 Agile P746
P746/EN SC
SCADA Communications
This chapter provides an overview regarding the SCADA communication interfaces of the
relay. Detailed protocol mappings, semantics, profiles and interoperability tables are not
provided within this manual. Separate documents are available per protocol, available for
download from our website.
P746/EN SG
Symbols and Glossary
This chapter provides a list of common technical abbreviations found within the product
documentation.
IT
P746/EN IN
Installation
This chapter provides information about installing the product.
P746/EN CS
Cyber Security
This chapter provides an overview about cyber security protection (to secure communication
and equipment within substations environment). Cyber security standards and
implementation are described.
Appendix A Ordering Options
A snapshot of the CORTEC is supplied as a static table in the appendices of this document.
Appendix B Wiring Diagrams
All external wiring connections to the relay are included in appendices of this document.
Appendix C Version History
The history of all hardware and software releases for the product are included in appendices
of this document.
Introduction
P746/EN IT/J43
MiCOM P40 Agile P746
2
(IT) 1-7
INTRODUCTION TO MICOM
MiCOM is a comprehensive solution capable of meeting all electricity supply requirements. It
comprises a range of components, systems and services from GE.
Central to the MiCOM concept is flexibility.
MiCOM provides the ability to define an application solution and, through extensive
communication capabilities, integrate it with your power supply control system.
The components within MiCOM are:
• P range protection relays;
• C range control products;
• M range measurement products for accurate metering and monitoring;
• S range versatile PC support and substation control packages.
MiCOM products include extensive facilities for recording information on the state and
behaviour of the power system using disturbance and fault records. They can also provide
measurements of the system at regular intervals to a control centre enabling remote
monitoring and control to take place.
For up-to-date information on any MiCOM product, visit our website:
2.1
Compliance
The device has undergone a range of extensive testing and certification processes to ensure
and prove compatibility with all target markets. A detailed description of these criteria can be
found in the Technical Data chapter.
IT
P746/EN IT/J43
Introduction
(IT) 1-8
3
MiCOM P40 Agile P746
PRODUCT SCOPE
The MiCOM P746 differential busbar protection relay has been designed for the protection of
a wide range of substation busbars from distribution to transmission voltage levels. The relay
includes a comprehensive range of non-protection features to aid with system diagnosis and
fault analysis. The P746 offers integral biased differential busbar, breaker failure, dead zone
and overcurrent protection and is suitable for application on solidly grounded systems. The
relay is especially suitable where a Centralised scheme solution is required.
The scheme can comprise:
IT
• A single MiCOM P746 up to 6 sets of CTs
• Three MiCOM P746 for up to 18 (single phase) CTs per relay
• As many times “three MiCOM P746 for up to 18 (single phase)” when possible.
With the S1 Agile software and the Remote HMI monitoring tool it allows full flexibility for all
configurations up to 2 zones (or n times 2 zones).
3.1
Ordering Options
All current models and variants for this product are defined in an interactive spreadsheet
called the CORTEC. This is available on the company website.
Alternatively, you can obtain it via the Contact Centre at:
contact.centre@ge.com
A copy of the CORTEC is also supplied as a static table in the Appendices of this document.
However, it should only be used for guidance as it provides a snapshot of the interactive
data taken at the time of publication.
3.2
Functional Overview
The P746 Busbar protection contains a wide variety of protection functions.
The protection features are summarized below:
Protection Functions Overview
ANSI
IEC 61850
87BB / P
PhsPDIF
87CZ / P
CzPPDIF
50 / 51 / P
OcpPTOC
50 / 51 / N
50ST / P
EfmPTOC
DzpPhsPTOC
P746
Phase segregated biased current differential high speed busbar
•
protection
Check Zone segregated biased phase current differential high speed
•
busbar protection
Phase overcurrent protection (2 stages)
•
Earth overcurrent protection (2 stages)
•
Dead zone phase protection (short zone between CTs and open CBs) •
CTS
VTS
50BF
RBRF
Current transformer supervision (single box mode only)
Voltage transformer supervision
Breaker failure protection (LBB)
89
RBRF
Lockout
ISL Isolator discrepancy alarm
OptGGIO
Digital inputs
•
•
16 to 40∗
RlyGGIO
Output relays
16 to 32∗
FnkGGIO
LedGGIO
Front communication port (RS232)
Rear communication port (Kbus/EIA(RS)485)
Rear communication port (Ethernet) *
Time synchronisation port (IRIG-B) *
Redundant Ethernet Port
Function keys
Programmable tri-colour LEDs
•
•
Option
Option
Option
10
18
∗ Refer to the data sheet for model selection
•
•
•
Introduction
P746/EN IT/J43
MiCOM P40 Agile P746
(IT) 1-9
The P746 supports the following relay management functions in addition to the functions
shown above.
• 4 Alternative setting groups
• Programmable function keys
• Control inputs
• Programmable scheme logic
• Programmable allocation of digital inputs and outputs
• Sequence of event recording
• Comprehensive disturbance recording (waveform capture)
• Fully customizable menu texts
• Multi-level password protection
• Power-up diagnostics and continuous self-monitoring of relay
Application overview
Figure 1: Functional diagram
IT
P746/EN IT/J43
(IT) 1-10
IT
Introduction
MiCOM P40 Agile P746
Technical Data
P746/EN TD/J43
MiCOM P40 Agile P746
(TD) 2-1
TD
TECHNICAL DATA
Hardware Design:
M
Software Design:
91
P746/EN TD/J43
(TD) 2-2
Technical Data
MiCOM P40 Agile P746
Technical Data
P746/EN TD/J43
MiCOM P40 Agile P746
Technical Data
Mechanical Specification
Design
Modular MiCOM Px40 platform relay, Size 16“
case (80TE)
Mounting is front of panel flush mounting.
(TD) 2-3
Optional Second Rear Communication
PortEIA(RS)232, 9 pin D-type female
connector,
socket SK4. Courier protocol: K-Bus, or
EIA(RS)485 or EIA(RS)232. Maximum cable
length: 15m.
Optional Rear Ethernet Connection for
IEC 61850
10 Base T / 100 Base TX Communications
Enclosure Protection
Per IEC 60529:1989/A2:2013
IP 52 Protection (front panel) against dust and
dripping water,
IP 50 Protection for the rear and sides of the
case against dust,
IP 10 Product safety protection for the rear due
to live connections on the terminal block.
Weight
P746: 13.4 kg
Terminals
AC Current and Voltage Measuring Inputs
Located on heavy duty (black) terminal block:
Threaded M4 terminals, for ring lug
connection.
CT inputs have integral safety shorting, upon
removal of the terminal block.
General Input/Output Terminals
For power supply, opto inputs, output contacts
and COM1& optional COM2 rear
communications.
Located on general purpose (grey) blocks:
Threaded M4 terminals, for ring lug
connection.
Case Protective Earth Connection
Two rear stud connections, threaded M4.
Must be earthed (grounded) using the
protective (earth) conductor for safety,
minimum earth wire size 2.5mm².
Front USB Port
EIA(RS)232 DCE, USB type B
Courier protocol for interface to MiCOM S1
Agile software.
Isolation to ELV (extra low voltage) level.
Maximum cable length 5 m.
Rear Communications Port
K-Bus/EIA(RS485) signal levels, two wire
Connections located on general purpose block,
M4 screw.
For screened twisted pair cable, multidrop,
1000m max. Courier protocol. SELV* rated
circuit.
Ethernet (copper & fibre)
Interface in accordance with IEEE802.3 and
IEC 61850
Isolation: 1.5 kV. Connector type: RJ45
Cable type: Screened Twisted Pair (STP)
Max. cable length: 100m
TD
100 Base FX Interface
Interface in accordance with IEEE802.3 and
IEC 61850
Wavelength: 1300 nm
Fiber: multi-mode 50/125 µm or 62.5/125 µm
Connector style: BFOC 2.5 - (ST®)
Optional Rear IRIG-B Interface modulated
or un-modulated
BNC socket
SELV* rated circuit.
50 ohms coaxial cable.
*: PEB = Protective equipotential bonded
*: SELV = Safety/Separated extra low voltage
Both PEB and SELV circuits are safe to touch
after a single fault condition.
Optional Rear redundant Ethernet
connection for IEC 61850
100 Base FX Interface
Interface in accordance with IEEE802.3 and
IEC 61850
Wavelength: 1300 nm
Fiber: multi-mode 50/125µm or 62.5/125 µm
Connector style: BFOC 2.5 -(ST®)
Transmitter optical characteristics 100 base FX
interface
Transmitter Optical Characteristics – 100
base FX interface
(TA = 0°C to 70°C, VCC = 4.75 V to 5.25 V)
Parameter
Output Optical Power
BOL: 62.5/125 µm,
NA = 0.275 Fiber
EOL
Output Optical Power
BOL: 50/125 µm,
NA = 0.20 Fiber EOL
Optical Extinction
Ratio
Output Optical Power
at Logic “0” State
Sym
Min.
Typ.
Max
Unit
POUT
–19
–20
–16.8
–14
dBm
avg.
POUT
–22.5
–23.5
–20.3
–14
dBm
avg.
10
–10
POUT
(“0”)
BOL – Beginning of life
EOL – End of life
–45
%
dB
dBm
avg.
P746/EN TD/J43
Technical Data
(TD) 2-4
MiCOM P40 Agile P746
Receiver Optical Characteristics – 100 base
FX interface
(TA = 0°C to 70°C, VCC = 4.75 V to 5.25 V)
Parameter
TD
Sym
Min.
Input Optical
P Min.
Power Minimum IN
(W)
at Window Edge
Input Optical
P Min.
Power Minimum IN
(C)
at Eye Center
Input Optical
PIN
–14
Power Maximum Max.
Typ.
Max.
Unit
–33.5
–31
dBm
avg.
–34.5
–31.8
–11.8
dBm
avg.
dBm
avg.
Fiber defect connector (watchdog relay) –
Redundant Ethernet board
Connector (3 terminals):
2NC contacts
Rated voltage:
250 V
Continuous current:
5A
Short duration current:
30 A for 3 s
Breaking capacity
DC: 50 W resistive
DC: 25 W resistive
AC: 1500 VA resistive (cos φ = unity)
AC: 1500 VA inductive (cos φ = unity)
Subject to maxima of 5 A and 250 V
Ratings
AC Measuring Inputs
Nominal frequency:
∗ 50 and 60 Hz (settable)
Operating range:
∗ 45 to 65 Hz
Phase rotation:
∗ ABC or ACB
AC Current
Nominal current (In):
∗ 1 and 5 A dual rated.
Nominal burden per phase 1 A:
∗ <0.04 VA at rated current
Impedance per phase 1 A:
∗ <40 mΩ over 0 – 30 In
Nominal burden per phase 5 A:
∗ <0.15 VA at rated current
Impedance per phase 5 A:
∗ <8 mΩ over 0 – 30 In
Thermal withstand:
∗ continuous 4 In
∗ for 10 s: 30 In
∗ for 1 s; 100 In
Linear to 64 In (non-offset AC current).
AC Voltage
Nominal voltage (Vn):
∗ 100 to 120 V phase-phase
Nominal burden per phase:
∗ < 0.02 VA at 110/√3 V
Thermal withstand:
∗ continuous 2 Vn for 10s: 2.6 Vn
Power supply
Auxiliary Voltage (Vx)
Three ordering options:
(i) Vx: 24 to 48 Vdc
(ii) Vx: 48 to 110 Vdc, and 40 to 100Vac (rms)
(iii) Vx: 110 to 250 Vdc, and 100 to 240 Vac (rms).
Operating Range
(i) 19 to 65 V
(dc only for this variant)
(ii) 37 to 150 V
(dc), 32 to 110 V (ac)
(iii) 87 to 300 V
(dc), 80 to 265 V (ac).
With a tolerable ac ripple of up to 12% for a dc
supply, per IEC 60255-11: 1979.
Nominal Burden
Quiescent burden: 12 W
Additions for energized binary inputs/outputs:
Per opto input:
∗ 0.09 W or 0.18 VA (24 to 54 V),
∗ 0.12 W or 0.24 VA (110/125 V),
∗ 0.19 W or 0.38 VA (220/250 V).
Per energized output relay: 0.13 W or 0.26 VA
Per energized high break output relay:0.73 W
or 1.46 VA
Power-up Time
Time to power up < 8 s.
Power Supply Interruption
Per IEC 60255-26: 2013
The relay will withstand a 20 ms interruption in
the DC auxiliary supply, without de-energizing.
Per IEC 60255-26: 2013
The relay will withstand a 20 ms interruption in
an AC auxiliary supply, without de-energizing.
Note: the use of a E124 extends these limits
In addition to IEC 60255-26 compliance, P746
withstands:
DC Power supply
voltage
24 V
48 V
110 V
220 V
DC Power supply interruption
20 ms
100 ms with Vx ordering option (i),
20 ms with Vx ordering option (ii)
200 ms with Vx ordering option (ii),
50 ms with Vx ordering option (iii)
20 0ms
Supercapacitor
Discharge time >14 days
Field Voltage Output
Regulated 48 Vdc
Current limited at 112 mA maximum output
Digital (“Opto”) Inputs
Universal opto inputs with programmable
voltage thresholds. May be energized from the
48 V field voltage or external battery supply.
Rated nominal voltage:
24 to 250 Vdc
Operating range:
19 to 265 Vdc
Withstand:
300 Vdc.
Nominal pick-up and reset thresholds:
∗ Pick-up: approx. 70% of
battery nominal set,
∗ Reset: approx. 66% of
battery nominal set.
Recognition time:
7 ms
Technical Data
P746/EN TD/J43
MiCOM P40 Agile P746
(TD) 2-5
Output Contacts
Environmental Conditions
Standard Contacts
General purpose relay outputs for signalling,
tripping and alarming:
Rated voltage:
∗ 300 V
Continuous current:
∗ 10 A
Short-duration current:
∗ 30 A for 3 s
Making capacity:
∗ 250A for 30 ms
Breaking capacity:
∗ DC: 50 W resistive
∗ DC: 62.5 W inductive (L/R = 50 ms)
∗ AC: 2500 VA resistive (cos φ = unity)
∗ AC: 2500 VA inductive (cos φ = 0.7)
Response to command:
∗ < 5 ms
Durability:
∗ Loaded contact: 10000 operations
minimum,
∗ Unloaded contact: 100000 operations
minimum.
Ambient Temperature Range
Ambient temperature range
Operating temperature range
–25°C to +55°C (or –13°F to +131°F)
Storage and transit
–25°C to +70°C (or –13°F to +158°F)
Fast operation and High Break Contacts
Dedicated purpose relay outputs for tripping:
∗ Uses IGBT technology
Make and Carry:
∗ 30 Amps for 3 sec, 30 A @ 250 V resistive
Carry:
∗ 250 Amps dc for 30 ms
Continuous Carry:
∗ 10 Amps dc
Break Capacity:
∗ 10 Amps @ 250 V resistive (10,000
operations) 10 Amps @ 250 V L/R=40 ms
Operating time:
∗ <200 us & Reset time: 7.5 ms
Watchdog Contacts
Non-programmable contacts for relay
healthy/relay fail indication:
Breaking capacity:
∗ DC: 30 W resistive
∗ DC: 15 W inductive (L/R = 40 ms)
∗ AC: 375 VA inductive (cos φ = 0.7)
Tested as per
IEC 60068-2-1: 2007
-25°C (–13°F) storage (96 hours)
-40°C (–40°F) operation (96 hours)
IEC 60068-2-2: 2007
+70°C (+158°F) (storage (96 hours)
+85°C (+185°F) operation (96 hours)
Ambient Humidity Range
Per IEC 60068-2-78: 2013:
∗ 56 days at 93% relative humidity and +40
°C
Per IEC 60068-2-30: 2005:
∗ Damp heat cyclic, six (12 + 12) hour cycles,
93% RH, +25 to +55 °C
Corrosive Environments
Per IEC 60068-2-42: 2003, 60068-2-43 2003
Industrial corrosive environment/poor
environmental control, Sulphur Dioxide.
21 days exposure to elevated concentrations
(25ppm) of SO2 at 75% relative humidity and
+25°C
Industrial corrosive environment/poor
environmental control, Hydrogen Sulphide.
21 days exposure to elevated concentrations
(10ppm) of H2S at 75% relative humidity and
+25°C
Salt mist.
Per IEC 60068-5-52: 1996 KB severity 3
Type Tests
Insulation
Per IEC 60255-27: 2013:
∗ Insulation resistance > 100 MΩ at 500 Vdc
(Using only electronic/brushless insulation
tester).
IRIG-B 12X Interface (Modulated)
External clock synchronization per IRIG
standard 200-98, format B12X.
Input impedance 6kΩ at 1000 Hz
Modulation ratio:
∗ 3:1 to 6:1
Input signal, peak-peak:
∗ 200 mV to 20 V
IRIG-B 00X Interface (Un-modulated)
External clock synchronization per IRIG
standard 200-98, format B00X.
Input signal TTL level
Input impedance at dc 10 kΩ
Creepage Distances and Clearances
Per IEC 60255-27: 2013:
∗ Pollution degree 3,
∗ overvoltage category III,
∗ impulse test voltage 5 kV.
High Voltage (Dielectric) Withstand
(EIA RS232 ports excepted).
(i) Per IEC 60255-27: 2013, 2 kV rms, AC, 1
minute:
Between all case terminals connected together
and the case earth.
Also, between all terminals of independent
circuits.
∗ 1 kV rms AC for 1 minute, across open
watchdog contacts and across open
contacts of changeover output relays.
TD
P746/EN TD/J43
(TD) 2-6
TD
Technical Data
MiCOM P40 Agile P746
(ii) Per ANSI/IEEE C37.90-2005 (reaffirmed
1994):
∗ 1.5 kV rms AC for 1 minute, across open
contacts of changeover output relays.
Between terminals of each group (excluding
communication ports, where applicable):
Amplitude: 2 kV
Impulse Voltage Withstand Test
Per IEC 60255-27: 2013:
Front time: 1.2 µs, Time to half-value: 50 µs,
Peak value: 5 kV, 0.5J
Between all terminals, and all terminals and
case earth.
Immunity to Radiated Electromagnetic
Energy
Per IEC 60255-26:2013
Frequency band: 80 MHz to 1.0 GHz
Spot tests at 80, 160, 380, 450, 900, 1250
MHz
Test field strength: 10 V/m,
Test using AM: 1 kHz / 80%
Compliance: IEEE/ANSI C37.90.2: 2004
Frequency band: 80 MHz to 1 GHz
Spot tests at 80, 160, 380, 450, MHz
Waveform: 1 KHz @ 80% am and pulse
modulated.
Field strength of 35 V/m.
Electromagnetic Compatibility (EMC)
1 MHz Burst High Frequency Disturbance
Test
Per IEC 60255-26: 2013
Common-mode test voltage (level 3): 2.5 kV,
Differential test voltage (level 3): 1.0 kV,
.
100 kHz Damped oscillatory Test
Per EN 61000-4-18: 2011: Level 3, 100 kHz
and 1 MHz Level 4: 3 MHz, 10 MHz and 30
MHz, IEC 60255-26:2013
Common-mode test voltage (level 3): 2.5 kV,
Common-mode test voltage (level 4): 4.0 kV,
Differential test voltage: 1.0 kV,
Immunity to Electrostatic Discharge
Per IEC 60255-26: 2013, IEC 61000-4-2:2009
Class 4 Condition: 15 kV discharge in air to
user interface, display, and exposed
metalwork.
Class 3 Condition: 8 kV discharge in air to all
communication ports.
Electrical Fast Transient or Burst
Requirements
Per IEC 60255-26:2013, IEC 61000-4-4:2012.
Applied to communication inputs: Amplitude: 2
kV, burst frequency 5 kHz and 100 KHz (level
4)
Applied directly to power supply and all other
inputs except for communication inputs:
Amplitude: 4 kV, burst frequency 5 kHz (level
4)
Surge Withstand Capability
Per IEEE/ANSI C37.90.1: 2002:
Condition 1:
4 kV fast transient and 2.5 kV oscillatory
applied common mode and differential mode to
opto inputs, output relays, CTs, VTs, power
supply
Condition 2:
4 kV fast transient and 2.5 kV oscillatory
applied common mode to communications,
IRIG-B
Surge Immunity Test
Per IEC 60255-26:2013, IEC 61000-45:2014+AMD1:2017,
Pulse duration: Time to half-value: 1.2/50 µs,
Between all groups and protective earth
conductor terminal: Amplitude: 4 kV
Radiated Immunity from Digital
Communications
Per IEC 61000-4-3:2006 + A2:2010:
Frequency bands: 900 MHz and 1.89 GHz
Test field strength: 10 V/m
Radiated Immunity from Digital Radio
Telephones
Per IEC 60255-26:2013, IEC 61000-4-3:2006
+ A2:2010
Frequency bands: 900 MHz and 1.89 GHz
Test field strength: 10 V/m .
Immunity to Conducted Disturbances
Induced by Radio Frequency Fields
Per IEC 60255-26-2013, IEC 61000-4-6:2013,
Level 3,
Frequency bands: 150 KHz to 80 MHz
Test disturbance voltage: 10 V rms
Test using AM: 1 KHz @ 80%
Spot tests: 27 MHz and 68 MHz
Magnetic Field Immunity
Per IEC 61000-4-8:2009, Level 5,
Per IEC 61000-4-9: 2016, Level 5,
Per IEC 61000-4-10: 2016, Level 5,
IEC 61000-4-8 test:100 A/m applied
continuously,1000 A/m applied for 3 s.
IEC 61000-4-9 test: 1000 A/m applied in all
planes.
IEC 61000-4-10 test: 100 A/m applied in all
planes at 100 kHz/1 MHz with a burst duration
of 2 seconds.
Technical Data
P746/EN TD/J43
MiCOM P40 Agile P746
Conducted Emissions
Per IEC 60255-26:2013
Power supply test 1: 0.15 – 0.5 MHz, 79 dBµV
(quasi peak) 66 dBµV (average)
Power supply test 2: 0.5 – 30 MHz, 73 dBµV
(quasi peak) 60 dBµV (average)
RJ45 test 1 (where applicable): 0.15 – 0.5
MHz, 97 dBµV (quasi peak) 84 dBµV
(average)
RJ45 test 2 (where applicable): 0.5 – 30 MHz,
87 dBµV (quasi peak) 74 dBµV (average)
Radiated Emissions
Per IEC 60255-26:2013:
Test 1: 30 – 230 MHz, 40 dBµV/m at 10 m
measurement distance
Test 2: 230 – 1 GHz, 47 dBµV/m at 10 m
measurement distance.
EU Directives
EMC Compliance
Per 2014/30/EU:
Compliance to the European Commission
Directive on EMC is claimed via the Technical
Construction File route. Product Specific
Standards were used to establish conformity:
IEC 60255-26:2013
(TD) 2-7
Product Safety
Per 2014/30/EU:
Compliance with European Commission Low
Voltage Directive. Compliance is demonstrated
by reference to generic safety standards:
IEC 60255-27:2013
Mechanical Robustness
Vibration Test
Per IEC 60255-21-1: 1998
Response Class 2
Endurance Class 2
Shock and Bump
Per EN 60255-21-2: 1998
Shock response Class 2
Shock withstand Class 1
Bump Class 1
Seismic Test
Per EN 60255-21-3: 1993
Class 2
TD
P746/EN TD/J43
(TD) 2-8
MiCOM P40 Agile P746
Timing and Accuracy
Three phase overcurrent protection
All quoted operating times include the closure
of the standard trip output contact.
Accuracy
Pick-up:
∗ Setting ±5% or 20 mA Whichever Is Greater
(WIG)
Drop-off:
∗ 0.95 x Setting ±5%
∗ or 20 mA WIG
Min. trip level of IDMT elements:
∗ 1.05 x Setting ±5%
∗ or 10 mA WIG
IDMT characteristic shape:
∗ ±5% or 40 ms WIG
(under reference conditions)*
IEEE reset:
∗ ±5% or 50 ms WIG
DT operation:
∗ ±2% or 50 ms WIG
DT reset:
∗ Setting ±5% or 20 ms WIG
Characteristic
UK curves:
∗ IEC 60255-3 – 1998
US curves:
∗ IEEE C37.112 – 1996
Performance Data
Busbar Protection
TD
Technical Data
Busbar fault Accuracy
Pick-up:
∗ Setting ± 5% or 20 mA, Whichever Is
Greater (WIG)
Drop-off:
∗ >0.95 × Setting or 20 mA, WIG
Busbar trip with high speed contact:
∗ 8 ms (min) & 12 ms (typical) at 3.5 ×
tripping threshold (50 Hz)
∗ 6 ms (min) & 10 ms (typical) at 4.5 ×
tripping threshold (60 Hz)
Busbar trip with standard contact:
∗ <20 ms at 3.375 x Measured Diff/ID>2
(50Hz)
∗ <20 ms at 3.25 x Measured Diff/ID>2
(60Hz)
Circuitry fault Accuracy
Pick-up:
∗ Setting ± 5% or 20 mA, Whichever Is
Greater (WIG)
Drop-off:
∗ >0.95 × Setting or 20 mA, WIG
DT operation:
∗ ±5 % or 50 ms WIG
Dead Zone Protection
Accuracy
Pick-up:
∗ Setting ± 5% or 20 mA Whichever Is
Greater (WIG)
Drop-off:
∗ >0.95 × Setting or 20 mA WIG
Min. trip level:
∗ 1.05 × Setting ± 5% or 20 mA WIG
DT operation:
∗ ±5 % or 50 ms WIG
Earth Fault Protection
Accuracy
Pick-up:
∗ Setting ±5% or 20 mA Whichever Is Greater
(WIG)
Drop-off:
∗ >0.9 x Setting or 20 mA WIG
Min. trip level of IDMT elements:
∗ 1.05 x Setting ±5% or 10 mA WIG
IDMT characteristic shape:
∗ ±5% or 40 ms WIG
(under reference conditions)*
IEEE reset:
∗ ±5% or 40ms WIG
DT operation and reset:
∗ ±2% or 50 ms WIG
Transient overreach and overshoot
Accuracy
Additional tolerance due to increasing X/R
ratios: ±5% over the X/R ratio of 1 to 120
Overshoot of overcurrent elements: <40 ms
Programmable scheme logic
Accuracy
Output, dwell and pulse conditioner timers:
∗ Setting ±2% or 50 ms whichever is greater
Technical Data
P746/EN TD/J43
MiCOM P40 Agile P746
(TD) 2-9
IRIG-B and Real Time Clock
IEC 61850 Ethernet data
Modulated IRIG-B:
Modulation ratio:
∗ 1/3 or 1/6
Input signal peak-peak amplitude:
∗ 200 mV to 20 V
Input impedance at 1000 Hz: 6000 Ω
External clock synchronization:
∗ Conforms to IRIG standard 200-98, format
B
10 Base T /100 Base TX Communications
Interface in accordance with IEEE802.3 and
IEC 61850
Isolation 1.5 kV
Cable type: Screened twisted pair STP
Max length: 100 m
Un-modulated IRIG-B:
Input signal TTL level
Input impedance at dc 10 kΩ
External clock synchronization per IRIG
standard 200-98, format B00X.
Performance Accuracy (for modulated and
un-modulated versions)
Real time clock accuracy: < ±2 seconds/day
Measurements
Accuracy
Phase current:
∗ ±1.0% of reading
Phase local current:
∗ ±1.0% of reading
∗ or ±(f-fn)/fn %
Phase remote current
∗ ±1.0% of reading
∗ or ±(f-fn)/fn %
Phase differential current:
∗ ±5.0%
Bias current:
∗ ±5.0%
Frequency:
∗ ±1%
Disturbance records
Accuracy
Waveshape:
∗ Comparable with applied quantities
Magnitude and relative phases:
∗ ±5% of applied quantities
Duration:
∗ ±2%
Trigger position:
∗ ±2% (minimum trigger 100ms)
Reference conditions
Ambient temperature:
∗ 20°C
Frequency Tracking Range
45 to 65 Hz
Breaker failure
Accuracy
Reset time < 15 ms ±2%
Thresholds: settings ±5%
100 Base FX Interface
Interface in accordance with IEEE802.3 and
IEC 61850
Wavelength: 1300 nm
Fibre: multi-mode 50/125 µm or 62.5/125 µm
Connector style: ST
Transmitter Optical Characteristics
(TA = 0°C to 70°C, VCC = 4.75 V to 5.25 V)
Parameter
Output Optical
Power
BOL 62.5/125 µm,
NA = 0.275 Fiber
EOL
Output Optical
Power
BOL 50/125 µm,
NA = 0.20 Fiber
EOL
Optical Extinction
Ratio
Output Optical
Power at
Logic “0” State
Sym
Min.
Typ.
Max
Unit
PO
-19
-20
-16.8
-14
dBm avg.
PO
-22.5
-23.5
-20.3
-14
dBm avg.
10
-10
%
dB
-45
dBm avg.
PO
(“0”)
BOL – Beginning of life
EOL – End of life
Receive Optical Characteristics
(TA = 0°C to 70°C, VCC = 4.75 V to 5.25 V)
Parameter
Input Optical
Power Minimum at
Window Edge
Input Optical
Power Minimum at
Eye Center
Input Optical
Power Maximum
Sym
PIN
Min.
(W)
PIN
Min.
(C)
PIN
Max.
Min.
-14
Typ.
Max.
Unit
-33.5
–31
dBm avg.
-34.5
-31.8
Bm avg.
-11.8
dBm avg.
TD
P746/EN TD/J43
Technical Data
(TD) 2-10
MiCOM P40 Agile P746
Settings, Measurements and
Records List
Global Settings (System Data):
Language:
∗ English/French/German/Spanish
Frequency:
∗ 50/60 Hz
Voltage transformers
TD
Phase VT Primary: 100 V...100 kV
Phase VT Secondary V: 80…140 V
Current transformers
Phase CT Primary:
Phase CT Secondary In:
1A...30 kA
1A or 5A
Current transformer and feeder
characteristics
Class:
∗ 5P (IEC185)
∗ X (BS3958)
∗ TPX (IEC 44-6)
∗ TPY (IEC 44-6)
∗ TPZ (IEC 44-6)
Supervision of I0 calculation:
∗ Kce: 0.01... 1.00
I0 error alarm time delay:
∗ Tce: 0.0...10.0 s
Differential Protection
IRef:
∗ 100A…30kA (step 5A)
Disabled/Enabled
ID>2:
∗ 10%…250% (step 1%)
k2:
∗ 20%...90% (step 1%)
tDiff:
∗ 0…10 s (step 10 ms)
Check zone
kCZ:
∗ 0%…90% (step 1%)
Circuitry fail
Disabled/Enabled
ID>1:
∗ 5%…600% (step 1%)
k1:
∗ 0%…50% (step 1%)
tID>1:
∗ 0…600.0 s (step 10 ms)
CZ circuitry modes
Alarm & No Block / AlarmSR&No Block /
Blocking Latched / Alarm Latched / Sel-Reset
Zx circuitry modes
Self-Reset / Alarm Latched / Blocking Latched
Circuitry fail blocking mode:
∗ per phase/3 phase
Circuitry reset:
∗ 0…600.0 s (step 100 ms)
V<Status / V1<Status / V2>Status /
VN>Status
∗ Disabled / Enabled
V<Set / V1<Set:
∗ 10…120 V (step 1V)
V2>Set:
∗ 1…110 V (step 1V)
VN>Set:
∗ 1…80 V (step 1V)
Pickup timer:
∗ 0…10.00 s (step 10 ms)
Dead Zone protection
Disabled/Enabled
I>Current Set:
∗ 10%... 400% (step 1%)
Time delay:
∗ 0,00…100,00 s (step 10 ms)
Breaker failure protection
Caution: the following current set values are
expressed in multiple of the local CT’s nominal
rated current inp (primary) or ins (secondary).
Breaker Failure
1ST phase O/C threshold (dead pole detection
for 50BF):
∗ I<: 0.05...1.00 xIn
Confirmation I>:
∗ Disabled/Enabled
2nd phase O/C threshold:
∗ I>: 0.05...4.00 xIn
Confirmation IN>:
∗ Disabled/Enabled
2nd residual O/C threshold:
∗ IN>: 0.05...4.00 xIn
Timers for 50BF internal tripping
CB fail 1 timer:
∗ tBF1: 0.00 s...10.00 s
CB fail 2 timer:
∗ tBF2: 0.00 s...10.00 s
Timers for 50BF external tripping (orders
from 21 or 87Tetc.)
CB fail 1 timer:
∗ TBF3: 0.00 s......10.00 s
CB fail 2 timer:
∗ TBF4: 0.00 s......10.00 s
Technical Data
P746/EN TD/J43
MiCOM P40 Agile P746
Overcurrent Protection
Phase Fault Protection (50/51)
3 phase Overcurrent function Status I>1:
∗ Disabled
∗ DT
∗ IEC S Inverse or IEC V Inverse or IEC E
Inverse
∗ UK LT Inverse
∗ IEEE M Inverse or IEEE V Inverse or IEEE
E Inverse
∗ US Inverse or US ST Inverse
Current Set if “function status” ≠0
∗ I>1: 0.10...32.00 xIn
Time delay if “function status”=1
∗ I>1: 0.00...100.00 xIn
TMS if 2≤ ”function status” ≤5
∗ I>1: 0.025...1.200 xIn (step 0.025)
Time dial if “function status”≥6
∗ I>1: 0.5...15.0 xIn
Reset Char. if “function status”≥6
I>1:
∗ DT
∗ Inverse
tReset if 2≤”function status”≤5 OR if “Reset
Char.”=1 AND “function status”≥6
∗ I>1: 0.0...100.0 xIn
3 phase Overcurrent threshold function status
I>2:
∗ Disabled
∗ Blocking 87BB
∗ High set I>2
∗ Both
∗ Current Set
I>2: 0.10... 32.00
Time Delay if “function status”=1
∗ I>2: 0.00...100.00 s
Earth Fault Protection (50N/51N) (One Box
Mode)
Residual Overcurrent Function Status IN>1:
Disabled
∗ DT
∗ IDG
∗ RI
∗ IEC S Inverse or IEC V Inverse or IEC E
Inverse
∗ UK LT Inverse, UK Rectifier
∗ IEEE M Inverse or IEEE V Inverse or IEEE
E Inverse
∗ US Inverse or US ST Inverse
Current Set if “function status” ≠0
∗ IN >1: 0.10...32.00 xIn
Time delay if “function status”=1
∗ IN >1: 0.00...100.00 xIn
TMS if 2≤”function status”≤5
∗ IN >1: 0.025...1.200 xIn (step 0.025)
Time dial if “function status”≥6
∗ IN >1: 0.5...15.0 xIn
Reset Char. if “function status”≥6
IN >1:
∗ DT
∗ Inverse
tReset if 2≤”function status”≤5 OR if “Reset
Char.”=1 AND “function status”≥6
∗ IN >1: 0.0...100.0
(TD) 2-11
Residual Overcurrent threshold function status
IN >2:
∗ Disabled
∗ Blocking 87BB
∗ High set I>2
∗ Both
Current Set
∗ IN >2: 0.10 xIn...32.00 xIn
Time Delay if “function status”=1
∗ IN >2: 0.00...100.00 s
Supervision
Voltage transformer supervision:
Status:
∗ Blocking & indication
∗ Manual & automatic mode
Time delay:
∗ 1 s...10.00 s (step 100 ms)
Current transformer supervision:
Status:
∗ Blocking & indication
Setting accuracy:
±5%
Time delay:
∗ 0…10.00 s (step 100 ms)
accuracy: ±2% or 50 ms (whichever is
greater)
CTS I1 / CTS I2/I1>1 / CTS I2/I1 >2:
∗ 5%...100% (step 1%)
Date and Time
IRIG-B Sync:
∗ Disabled/Enabled
Battery Alarm:
∗ Disabled/Enabled
Configuration
Setting Group:
.
Select via Menu
.
Select via Opto
Active Settings:
Group 1/2/3/4
Setting Group 1:
Disabled/Enabled
Setting Group 2:
Disabled/Enabled
Setting Group 3:
Disabled/Enabled
Setting Group 4:
Disabled/Enabled
Dead zone OC Prot: Disabled/Enabled
Diff Busbar Prot:
Disabled/Enabled
Overcurrent Prot:
Disabled/Enabled
Earth Fault Prot:
Disabled/Enabled
CB Fail & I>:
Disabled/Enabled
Setting Values:
Primary/Secondary
LCD Contrast: (Factory pre-set)
Fault Recorder
Records for the last 5 faults:
∗ Indication of the faulty zone
∗ Protection element operated
∗ Active setting group
∗ Fault duration
∗ Currents and frequency
∗ Faulty zone differential and bias current
∗ Topology at the fault occurrence
Event Recorder
Records for the last 512 events
TD
P746/EN TD/J43
Technical Data
(TD) 2-12
Oscillography
(Disturbance Recorder)
TD
Duration:
∗ Settable from 0.1 to 10.5 s
Trigger Position:
∗ 0...100% (step 0.1%)
Trigger Mode:
∗ Single/Extended
Analog Channel 1:
∗ up to 21
Digital Input 1
∗ up to 32
Selected binary channel assignment from any
DDB status point within the relay (opto input,
output contact, alarms, starts, trips, controls,
logic…).
Sampling frequency:
∗ 1200 Hz
Communications
RP1 Protocol:
∗ Courier
RP1 Address (courier)
∗ 6…34
Inactivity Timer: 1…30 minutes
∗ IEC 870-5-103
RP1 Address: (Courier):
∗ 6…34
RP1 InactivTimer:
∗ 1…30mins
RP1 Port Config (Courier)::
∗ K Bus
∗ EIA485 (RS485)
RP1 Comms Mode (EIA485 (RS485)):
∗ IEC 60870 FT1.2 Frame
∗ IEC 60870 10-Bit FrameRP1 Baud Rate
(EIA485 (RS485)): 9600/19200/38400 bits/s
Optional Additional Second Rear Port
Communication (RP2)
RP2 Protocol:
∗ Courier (fixed)
RP2 Port Config:
∗ Courier over EIA(RS)232
∗ Courier over EIA(RS)485
∗ K-Bus
RP2 Comms. Mode:
∗ IEC 60870 FT1.2 Frame
∗ 10-Bit NoParity
RP2 Address:
∗ 0…255
RP2 InactivTimer:
∗ 1…30mins
RP2 Baud Rate:
∗ 9600 bits/s
∗ 19200 bits/s
∗ 38400 bits/s
Optional Ethernet Port
NIC Tunl Timeout:
∗ 1...30mins
NIC Link Report:
∗ Alarm/Event/None
NIC Link Timeout:
∗ 0.1...60 s
MiCOM P40 Agile P746
COMMISSION TESTS
Monitor Bit 1(up to 8):
Binary function link strings, selecting which
DDB signals have their status visible in the
Commissioning menu, for test purposes
Test Mode:
Enabled or Disabled
87BB and 50BF trip blocked per zone
Test Pattern:
Configuration of which output contacts are to
be energized when the contact test is
applied.
Static Test Mode:
∗ Disabled/Enabled
Opto input voltage range:
∗ 24-27 V
∗ 30-34 V
∗ 48-54 V
∗ 110-125 V
∗ 220-250 V
Custom
Opto Input 1
(up to # = max. opto no. fitted)
Custom options allow independent thresholds
to be set per opto, from the same range as
above
Opto Input Labels
Opto Input 1 up to:
∗ 16 if mounted up to 32 Outputs
∗ 40 if mounted up to 24 Outputs
User defined text string to describe the
function of the particular opto input.
Outputs Labels
Relay 1 up to:
∗ 32 if mounted up to 16 Inputs
∗ 24 if mounted up to 40 Inputs
User defined text string to describe the
function of the particular relay output contact.
IED CONFIGURATOR
Switch Conf.Bank:
∗ No Action/Switch Banks
IEC 61850 GOOSE
GoEna:
∗ Disabled/Enabled
Test Mode:
∗ Disabled/Pass Through/Forced
VOP Test Pattern:
∗ 0x00000000... 0xFFFFFFFF
Ignore Test Flag:
∗ No/Yes
Getting Started
P746/EN GS/J43
MiCOM P40 Agile P746
(GS) 3-1
GS
GETTING STARTED
Hardware Suffix:
M
Software Version:
91
P746/EN GS/J43
(GS) 3-2
GS
Getting Started
MiCOM P40 Agile P746
Getting Started
MiCOM P40 Agile P746
P746/EN GS/J43
(GS) 3-3
CONTENTS
1
GETTING STARTED
5
1.1
Front Panel
5
1.1.1
Front Panel Compartments
5
1.1.2
HMI Panel
6
1.1.3
Keypad
7
1.1.3.1
Liquid Crystal Display
7
1.1.4
USB Port
7
1.1.5
Fixed Function LEDs
7
1.1.6
Function Keys
8
1.1.7
Programmable LEDs
8
2
REAR PANEL
10
2.1
Terminal Block Ingress Protection
11
3
CONFIGURATION
12
4
SETTINGS APPLICATION SOFTWARE
13
5
USING THE HMI PANEL
14
5.1
Navigating the HMI Panel
14
5.2
Getting Started
15
5.3
Default Display
16
5.4
Default Display Navigation
16
5.5
Password Entry
17
5.6
Processing Alarms and Records
18
5.7
Menu Structure
18
5.8
Changing the Settings
19
5.9
Direct Access (the Hotkey Menu)
20
5.9.1
Setting Group Selection using Hotkeys
20
5.9.2
Control Inputs
21
5.10
Function Keys
21
6
DATE AND TIME CONFIGURATION
23
6.1
Using an SNTP Signal
23
6.2
Using an IRIG-B Signal
23
6.3
Using an IEEE 1588 PTP Siganl
23
6.4
Without a Timing Source Signal
24
6.5
Time Zone Compensation
24
6.6
Daylight Saving Time Compensation
25
7
SETTING GROUPS SELECTION
26
GS
P746/EN GS/J43
(GS) 3-4
Getting Started
MiCOM P40 Agile P746
FIGURES
GS
Figure 1: Front panel
5
Figure 2: HMI panel
6
Figure 3: P746 relay rear view 80TE
10
Figure 4: Terminal block types
11
Figure 5: Example—fitted IP2x shields (cabling omitted for clarity)
11
Figure 4: Navigating the HMI
15
Figure 5: Default display navigation
17
Getting Started
P746/EN GS/J43
MiCOM P40 Agile P746
1
(GS) 3-5
GETTING STARTED
Before carrying out any work on the equipment, the user should be
familiar with the contents of the Safety Section/Safety Guide
SFTY-4LM as well as the ratings on the equipment rating label.
1.1
Front Panel
The following diagram shows an 80TE case
GS
Figure 1: Front panel
The front panel consists of:
• Top and bottom compartments with hinged cover
• LCD display
• Keypad
• USB Type B port inside the bottom compartment
• Fixed function LEDs
• Function keys and LEDs (60TE and 80TE models)
• Programmable LEDs
1.1.1
Front Panel Compartments
The top compartment contains labels for the:
• Serial number
• Current and voltage ratings.
The bottom compartment contains:
• USB Type B port
P746/EN GS/J43
Getting Started
(GS) 3-6
1.1.2
MiCOM P40 Agile P746
HMI Panel
The keypad provides full access to the device functionality using a range of menu options.
The information is displayed on the LCD. The LCD is a high resolution monochrome display
with 16 characters by 3 lines and controllable back light.
GS
Figure 2: HMI panel
Note:
As the LCD display has a resolution of 16 characters by 3 lines, some of the
information is in a condensed mnemonic form.
Getting Started
P746/EN GS/J43
MiCOM P40 Agile P746
1.1.3
(GS) 3-7
Keypad
The keypad consists of the following keys:
4 arrow keys to navigate the menus (organised around the
Enter key)
An enter key for executing the chosen option
A clear key for clearing the last command
A read key for viewing larger blocks of text (arrow keys
now used for scrolling)
2 hot keys for scrolling through the default display and for
control of setting groups. These are situated directly below
the LCD display.
1.1.3.1
Liquid Crystal Display
The LCD is a high resolution monochrome display with 16 characters by 3 lines and
controllable back light.
1.1.4
USB Port
The USB port is situated inside the bottom compartment, and is used to communicate with a
locally connected PC.
It has two main purposes:
• To transfer settings information to/from the PC from/to the device.
• For downloading firmware updates and menu text editing.
The port is intended for temporary connection during testing, installation and commissioning.
It is not intended to be used for permanent SCADA communications. This port supports the
Courier communication protocol only. Courier is a proprietary communication protocol to
allow communication with a range of protection equipment, and between the device and the
Windows-based support software package.
You can connect the unit to a PC with a USB cable up to 5 m in length.
The inactivity timer for the front port is set to 15 minutes. This controls how long the unit
maintains its level of password access on the front port. If no messages are received on the
front port for 15 minutes, any password access level that has been enabled is cancelled.
Note:
The front USB port does not support automatic extraction of event and
disturbance records, although this data can be accessed manually.
When not in use, always close the cover of the USB port to prevent
contamination.
1.1.5
Fixed Function LEDs
The fixed function LEDs on the left-hand side of the front panel are used to indicate the
following conditions:
• Trip (Red) indicates that the relay has issued a trip signal. It is reset when the
associated fault record is cleared from the front display.
GS
P746/EN GS/J43
Getting Started
(GS) 3-8
MiCOM P40 Agile P746
• Alarm (Yellow) flashes to indicate that the relay has registered an alarm. This may be
triggered by a fault, event or maintenance record. The LED will flash until the alarms
have been accepted (read), after which the LED will change to constant illumination,
and will extinguish, when the alarms have been cleared.
• Out of service (Yellow) indicates that the relay’s protection is unavailable or a test
mode is selected.
• Healthy (Green) indicates that the relay is in correct working order, and should be on
at all times. It will be extinguished if the relay’s self-test facilities indicate that there is
an error with the relay’s hardware or software. The state of the healthy LED is
reflected by the watchdog contact at the back of the relay.
Note:
GS
1.1.6
To improve the visibility of the settings using the front panel, the LCD
contrast can be adjusted using the LCD Contrast setting in the
CONFIGURATION column. This should only be necessary in very hot or
cold ambient temperatures.
Function Keys
The programmable function keys are available for custom use for some models.
Factory default settings associate specific functions to these keys, but by using
programmable scheme logic, you can change the default functions of these keys to fit
specific needs. Adjacent to these function keys are programmable LEDs, which are usually
set to be associated with their respective function keys.
1.1.7
Programmable LEDs
The device has a number of programmable LEDs, which can be associated with PSLgenerated signals. The programmable LEDs for most models are tri-colour and can be set to
RED, YELLOW or GREEN. However the programmable LEDs for some models are singlecolour (red) only. The single-colour LEDs can be recognised by virtue of the fact they are
large and slightly oval, whereas the tri-colour LEDs are small and round.
The default mappings for each of the programmable LEDs are as shown in the following
table:
LED
Number
1
2
3
4
5
6
7
8
LED Input Connection/Text
LED1 Red
LED1 Yellow
LED1 Green
LED2 Red
LED2 Yellow
LED2 Green
LED3 Red
LED3 Yellow
LED3 Green
LED4 Red
LED4 Yellow
LED4 Green
LED5 Red
LED5 Yellow
LED5 Green
LED6 Red
LED6 Yellow
LED6 Green
LED7 Red
LED7 Yellow
LED7 Green
LED8 Red
LED8 Yellow
LED8 Green
Latched
Yes
Yes
Yes
Yes
Yes
No
No
No
P746 LED Function Indication
CB1 closed
CB1 Alarm
CB1 open
CB2 closed
CB2 Alarm
CB2 open
CB3 closed
CB3 alarm
CB3 open
CB4 closed
CB4 Alarm
CB4 open
CB5 closed
CB5 Alarm
CB5 open
CB6 closed
CB6 Alarm
CB6 open
50BF Trip zone 1
87BB & 50 BF trip zone 1
87BB Trip zone 1
50BF Trip zone 2
87BB & 50 BF trip zone 2
87BB Trip zone 2
Getting Started
P746/EN GS/J43
MiCOM P40 Agile P746
LED
Number
9
10
11
12
13
14
15
16
17
18
(GS) 3-9
LED Input Connection/Text
FnKey LED1 Red
FnKey LED1 Yellow
FnKey LED1 Green
FnKey LED2 Red
FnKey LED2 Yellow
FnKey LED2 Green
FnKey LED3 Red
FnKey LED3 Yellow
FnKey LED3 Green
FnKey LED4 Red
FnKey LED4 Yellow
FnKey LED4 Green
FnKey LED5 Red
FnKey LED5 Yellow
FnKey LED5 Green
FnKey LED6 Red
FnKey LED6 Yellow
FnKey LED6 Green
FnKey LED7 Red
FnKey LED7 Yellow
FnKey LED7 Green
FnKey LED8 Red
FnKey LED8 Yellow
FnKey LED8 Green
FnKey LED9 Red
FnKey LED9 Yellow
FnKey LED9 Green
FnKey LED10 Red
FnKey LED10 Yellow
FnKey LED10 Green
Latched
No
yes
No
No
No
No
Yes
No
No
No
P746 LED Function Indication
Zone 1: blocked
Zone 1: alarm (zone blocked but not the CZ)
Zone 1: healthy
Zone 1: 87BB&50BF blocked
Not used
Zone 1: Test mode
Fault on phase A
Not used
Not used
Fault on phase B
Not used
Not used
Fault on phase C
Not used
Not used
Zone 2: blocked
Zone 2: alarm (zone blocked but not the CZ)
Zone 2: healthy
Zone 2: 87BB&50BF blocked
Not used
Zone 2: Test mode
Circuit fault
Not used
Not used
Trip latched
Not used
Indications resetting
Not used
External disturbance record
Disturbance record started
GS
P746/EN GS/J43
Getting Started
(GS) 3-10
2
MiCOM P40 Agile P746
REAR PANEL
The MiCOM Px40 series uses a modular construction. Most of the internal workings are on
boards and modules which fit into slots. Some of the boards plug into terminal blocks, which
are bolted onto the rear of the unit.
However, some boards such as the communications boards have their own connectors. The
rear panel consists of these terminal blocks plus the rears of the communications boards.
The back panel cut-outs and slot allocations vary. This depends on the product, the type of
boards and the terminal blocks needed to populate the case.
GS
A – IRIG B / Ethernet / COMMS
B – Opto \ high break
C – Opto \ high break
D – Sigma Delta analogue input board
E – Sigma Delta Opto Board
F – Sigma Delta analogue input board
Figure 3: P746 relay rear view 80TE
G–
H–
J–
K–
L–
M–
Sigma Delta Opto Board
Relay \ Opto \ high break
Relay \ high break
Relay \ high break
Relay board
Power supply board
Refer to Appendix B to see the full wiring diagrams list.
Not all slots are the same size. The slot width depends on the type of board or terminal
block. For example, HD (heavy duty) terminal blocks, as required for the analogue inputs,
require a wider slot size than MD (medium duty) terminal blocks. The board positions are not
generally interchangeable. Each slot is designed to house a particular type of board. Again
this is model-dependent.
The device may use one or more of the terminal block types shown in the following diagram.
The terminal blocks are fastened to the rear panel with screws.
• Heavy duty (HD) terminal blocks for CT and VT circuits
• Medium duty (MD) terminal blocks for the power supply, opto-inputs, relay outputs and
rear communications port
• MiDOS terminal blocks for CT and VT circuits
• RTD/CLIO terminal block for connection to analogue transducers
Getting Started
P746/EN GS/J43
MiCOM P40 Agile P746
(GS) 3-11
GS
Figure 4: Terminal block types
Note:
2.1
Not all products use all types of terminal blocks. The product described in
this manual may use one or more of the above types.
Terminal Block Ingress Protection
IP2x shields and side cover panels are designed to provide IP20 ingress protection for
MiCOM terminal blocks. The shields and covers may be attached during installation or
retrofitted to upgrade existing installations—see figure below.
Figure 5: Example—fitted IP2x shields (cabling omitted for clarity)
P746/EN GS/J43
(GS) 3-12
3
Getting Started
MiCOM P40 Agile P746
CONFIGURATION
Each product has different configuration parameters according to the functions it has been
designed to perform. There is, however, a common methodology used across the entire
product series to set these parameters.
Some of the communications setup can only be carried out using the HMI, and cannot be
carried out using settings applications software.
GS
Getting Started
MiCOM P40 Agile P746
4
P746/EN GS/J43
(GS) 3-13
SETTINGS APPLICATION SOFTWARE
To configure this device you will need to use the Settings Application Software. The settings
application software used in this range of relays is called MiCOM S1 Agile. It is a collection
of software tools, which is used for setting up and managing the relays.
Although you can change many settings using the front panel HMI, some of the features
cannot be configured without the Settings Application Software; for example the
programmable scheme logic, or IEC61850 communications.
If you do not already have a copy of the Settings Application Software, you can obtain it from
GE contact centre.
To configure your product, you will need a data model that matches your product. When you
launch the Settings Application Software, you will be presented with a panel that allows you
to invoke the “Data Model Manager”. This will close the other aspects of the software in
order to allow an efficient import of the chosen data model. If you don’t have, or can’t find,
the data model relating to your product, please call the GE contact centre.
When you have loaded all the data models you need, you should restart the Settings
Application Software and start to create a model of your system using the “System Explorer”
panel.
The software is designed to be intuitive, but help is available in an online help system and
also the Settings Application Software user guide P40-M&CR-SAS-UG-EN-n, where
'Language' is a 2 letter code designating the language version of the user guide and 'n' is the
latest version of the settings application software.
GS
P746/EN GS/J43
Getting Started
(GS) 3-14
5
MiCOM P40 Agile P746
USING THE HMI PANEL
Using the HMI, you can:
• Display and modify settings
• View the digital I/O signal status
• Display measurements
• Display fault records
• Reset fault and alarm indications
The keypad provides full access to the device functionality by means of a range of menu
options. The information is displayed on the LCD.
Keys
Description
GS
Note:
5.1
Function
Up and down cursor keys
To change the menu level or change
between settings in a particular column,
or changing values within a cell
Left and right cursor keys
To change default display, change
between column headings, or changing
values within a cell
ENTER key
For changing and executing settings
Hotkeys
For executing commands and settings
for which shortcuts have been defined
Cancel key
To return to column header from any
menu cell
Read key
To read alarm messages
Function keys (not all
models)
For executing user programmable
functions
As the LCD display has a resolution of 16 characters by 3 lines, some of the
information is in a condensed mnemonic form.
Navigating the HMI Panel
The cursor keys are used to navigate the menus. These keys have an auto-repeat function if
held down continuously. This can be used to speed up both setting value changes and menu
navigation. The longer the key is held pressed, the faster the rate of change or movement.
The figure below shows how to navigate the menu items in the form of a menu navigation
map.
Getting Started
P746/EN GS/J43
MiCOM P40 Agile P746
(GS) 3-15
Default display
option
Default display
option
Alarm message
Default display options
Subsequent column headings
Column 00
System data
Vertical cursor keys move
between setting rows
Row 01
Language
Last Column
Horizontal cursor
keys move
between values
within a cell
Row 01
The Cancel key
returns to
column header
Subsequent rows
Subsequent rows
V00437
Figure 6: Navigating the HMI
5.2
Getting Started
When you first start the relay, it will go through its power up procedure. After a few seconds it
will settle down into one of the top level menus. There are two menus at this level:
 The Alarms menu for when there are alarms present
 The default display menu for when there are no alarms present.
If there are alarms present, the yellow Alarms LED will be flashing and the menu display will
read as follows:
Alarms/Faults
Present
Even though the device itself should be in full working order when you first start it, an alarm
could still be present, for example, if there is no network connection for a device fitted with a
network card. If this is the case, you can read the alarm by pressing the 'Read' key.
Alarms
NIC Link Fail
If the device is fitted with an Ethernet card, you will first need to connect the device to an
active Ethernet network to clear the alarm and get the default display.
If there are other alarms present, these must also be cleared before you can get into the
default display menu options.
GS
P746/EN GS/J43
Getting Started
(GS) 3-16
5.3
MiCOM P40 Agile P746
Default Display
The HMI contains a range of possible options that you can choose to be the default display.
The options available are:
NERC Compliant banner
If the device is a cyber-security model, it will provide a NERC-compliant default display. If the
device does not contain the cyber-security option, this display option is not available.
ACCESS ONLY FOR
AUTHORISED USERS
Date and time
For example:
GS
11 : 09 : 15 :
23 Nov 2011
Description (user-defined)
For example:
Description
MiCOM P14NB
Plant reference (user-defined)
For example:
Plant Reference
MiCOM
Access Level
For example:
Access Level
3
In addition to the above, there are also displays for the system voltages, currents, power and
frequency etc., depending on the device model.
5.4
Default Display Navigation
The following diagram is an example of the default display navigation. In this example, we
have used a cybersecure model. This is an example only and may not apply in its entirety to
all models. The actual display options available depend on the exact model.
Getting Started
P746/EN GS/J43
MiCOM P40 Agile P746
(GS) 3-17
Use the horizontal cursor keys to step through from one display to the next.
NERC compliant
banner
NERC Compliance
Warning
NERC Compliance
Warning
System Current
Measurements
Access Level
System Voltage
Measurements
System Frequency
System Power
Measurements
Plant Reference
Description
Date & Time
V00403
Figure 7: Default display navigation
If the device is cyber-secure but is not yet configured for NERC compliance (see Cybersecurity chapter), a warning will appear when moving from the "NERC compliant" banner.
The warning message is as follows:
DISPLAY NOT NERC
COMPLIANT. OK?
You will have to confirm with the Enter button before you can go any further.
Note:
5.5
Whenever the relay has an uncleared alarm the default display is replaced
by the text Alarms/ Faults present. You cannot override this default display.
However, you can enter the menu structure from the default display, even if
the display shows the Alarms/Faults present message.
Password Entry
Configuring the default display (in addition to modification of other settings) requires level 3
access. You will be prompted for a password before you can make any changes, as follows.
The default level 3 password is ChangeMe#1
Enter password
**** Level 1
1. A flashing cursor shows which character field of the password can be changed. Press
the up or down cursor keys to change each character (tip: pressing the up arrow once
will return an upper case "A" as required by the default level 3 password).
GS
P746/EN GS/J43
Getting Started
(GS) 3-18
MiCOM P40 Agile P746
2. Use the left and right cursor keys to move between the character fields of the
password.
3. Press the Enter key to confirm the password. If you enter an incorrect password, an
invalid password message is displayed then the display reverts to Enter password.
Upon entering a valid password a message appears indicating that the password is
correct and if so what level of access has been unlocked. If this level is sufficient to
edit the selected setting, the display returns to the setting page to allow the edit to
continue. If the correct level of password has not been entered, the password prompt
page appears again.
4. To escape from this prompt press the Clear key. Alternatively, enter the password
using System data > Password. If the keypad is inactive for 15 minutes, the
password protection of the front panel user interface reverts to the default access
level.
To manually reset the password protection to the default level, select System data >
Password, then press the clear key instead of entering a password.
GS
Note: In the SECURITY CONFIG column, you can set the maximum number of attemps, the
time window in which the failed attempts are counted and the time duration for which the
user is blocked.
5.6
Processing Alarms and Records
If there are any alarm messages, they will appear on the default display and the yellow alarm
LED flashes. The alarm messages can either be self-resetting or latched. If they are latched,
they must be cleared manually.
1. To view the alarm messages, press the Read key. When all alarms have been viewed
but not cleared, the alarm LED changes from flashing to constantly on, and the latest
fault record appears (if there is one).
2. Scroll through the pages of the latest fault record, using the cursor keys. When all
pages of the fault record have been viewed, the following prompt appears.
Press clear to
reset alarms
3. To clear all alarm messages, press the Clear key. To return to the display showing
alarms or faults present, and leave the alarms uncleared, press the Read key.
4. Depending on the password configuration settings, you may need to enter a password
before the alarm messages can be cleared.
5. When all alarms are cleared, the yellow alarm LED switches off. If the red LED was
on, this will also be switched off.
Note:
5.7
To speed up the procedure, you can enter the alarm viewer using the Read
key and subsequently pressing the Clear key. This goes straight to the fault
record display. Press the Clear key again to move straight to the alarm reset
prompt, then press the Clear key again to clear all alarms.
Menu Structure
Settings, commands, records and measurements are stored inside the unit in non-volatile
memory in a local database. When using the Human Machine Interface (HMI) it is
convenient to visualize the menu navigation system as a table. Each item in the menu is
known as a cell, which is accessed by reference to a column and row address. Each column
and row is assigned a 2-digit hexadecimal numbers, resulting in a unique 4-digit cell address
for every cell in the database. The main menu groups are allocated columns and the items
within the groups are allocated rows, meaning a particular item within a particular group is a
cell.
Getting Started
P746/EN GS/J43
MiCOM P40 Agile P746
(GS) 3-19
Each column contains all related items, for example all of the disturbance recorder settings
and records are in the same column.
There are three types of cell:
• Settings: This is for parameters that can be set to different values
• Commands: This is for commands to be executed
• Data: this is for measurements and records to be viewed, which are not settable
Note:
Sometimes the term "Setting" is used generically to describe all of the three
types.
The table below provides an example of the menu structure.
SYSTEM DATA (Col 00)
VIEW RECORDS (Col 01)
Language (Row 01)
"Select Event [0...n]" (Row
01)
Password (Row 02)
Sys Fn Links Row 03)
…
MEASUREMENTS 1 (Col 02)
…
IA Magnitude (Row 01)
…
Menu Cell Ref (Row 02)
IA Phase Angle (Row 02)
…
Time & Date (Row 03)
IB Magnitude (Row 03)
…
…
…
…
It is more convenient to specify all the settings in a single column, detailing the complete
Courier address for each setting. The above table may therefore be represented as follows:
Setting
Column
Row
Description
SYSTEM DATA
00
00
First Column definition
Language (Row 01)
00
01
First setting within first column
Password (Row 02)
00
02
Second setting within first column
Sys Fn Links Row 03)
00
03
Third setting within first column
…
…
…
VIEW RECORDS
01
00
Second Column definition
Select Event [0...n]
01
01
First setting within second column
Menu Cell Ref
01
02
Second setting within second column
Time & Date
01
03
Third setting within second column
…
…
…
MEASUREMENTS 1
02
00
Third Column definition
IA Magnitude
02
01
First setting within third column
IA Phase Angle
02
02
Second setting within third column
IB Magnitude
02
03
Third setting within third column
…
…
…
The first three column headers are common throughout the entire Px40 series. However the
rows within each of these column headers may differ according to the product type. Many of
the column headers are the same for all products within the Px40 series. However, there is
no guarantee that the addresses will be the same for a particular column header. Therefore
you should always refer to the product documentation and not make any assumptions
5.8
Changing the Settings
1. Starting at the default display, press the down cursor key to show the first column
heading.
2. Use the horizontal cursor keys to select the required column heading.
3. Use the vertical cursor keys to view the setting data in the column.
4. To return to the column header, either press the up cursor key for a second or so, or
press the Cancel key once. It is only possible to move across columns at the column
heading level.
GS
P746/EN GS/J43
Getting Started
(GS) 3-20
MiCOM P40 Agile P746
5. To return to the default display, press the up cursor key or the Cancel key from any of
the column headings. If you use the auto-repeat function of the up cursor key, you
cannot go straight to the default display from one of the column cells because the
auto-repeat stops at the column heading.
6. To change the value of a setting, go to the relevant cell in the menu, then press the
Enter key to change the cell value. A flashing cursor on the LCD shows that the value
can be changed. You may be prompted for a password first.
7. To change the setting value, press the up and down cursor keys. If the setting to be
changed is a binary value or a text string, select the required bit or character to be
changed using the left and right cursor keys.
8. Press the Enter key to confirm the new setting value or the Clear key to discard it.
The new setting is automatically discarded if it is not confirmed within 15 seconds.
9. For protection group settings and disturbance recorder settings, the changes must be
confirmed before they are used. When all required changes have been entered, return
to the column heading level and press the down cursor key. Before returning to the
default display, the following prompt appears.
GS
Update settings?
Enter or clear
10.Press the Enter key to accept the new settings or press the Clear key to discard the
new settings.
Note:
5.9
For the protection group and disturbance recorder settings, If the menu timeout occurs before the setting changes have been confirmed, the setting
values are also discarded. Control and support settings, however, are
updated immediately after they are entered, without the Update settings?
Prompt.
Direct Access (the Hotkey Menu)
For settings and commands that need to be executed quickly or on a regular basis, the IED
provides a pair of keys directly below the LCD display. These so called Hotkeys can be
used to execute specified settings and commands directly.
The functions available for direct access using these keys are:
• Setting group selection
• Control inputs
The availability of these functions is controlled by the Direct Access cell in the
CONFIGURATION column. There are four options: Disabled, Enabled, CB Ctrl only and
Hotkey only.
For the Setting Group selection and Control inputs, this cell must be set to either Enabled or
Hotkey only.
5.9.1
Setting Group Selection using Hotkeys
In some models you can use the hotkey menu to select the settings group. By default, only
Setting group 1 is enabled. Other setting groups will only be available if they are first
enabled. To be able to select a different setting group, you must first enable them in the
CONFIGURATION column.
To access the hotkey menu from the default display, press the key directly below the
HOTKEY text on the LCD.
Use the right cursor keys to enter the SETTING GROUP menu.
Getting Started
P746/EN GS/J43
MiCOM P40 Agile P746
(GS) 3-21
Select the setting group with Nxt Grp and confirm by pressing Select. If neither of the cursor
keys is pressed within 20 seconds of entering a hotkey sub menu, the device reverts to the
default display.
5.9.2
Control Inputs
The control inputs are user-assignable functions. You can use the CTRL I/P CONFIG
column to configure the control inputs for the hotkey menu. In order to do this, use the first
setting Hotkey Enabled cell to enable or disable any of the 32 control inputs. You can then
set each control input to latched or pulsed and set its command to On/Off, Set/Reset,
In/Out, or Enabled/Disabled.
By default, the hotkey is enabled for all 32 control inputs and they are set to Set/Reset and
are Latched.
To access the hotkey menu from the default display, you press the key directly below the
HOTKEY text on the LCD. The following screen will appear.
User32 STG GP
HOTKEY MENU
Press the right cursor key twice to get to the first control input, or the left cursor key to get to
the last control input.
STP GP User02
Control Input 1
Now you can execute the chosen function (Set/Reset in this case).
If neither of the cursor keys is pressed within 20 seconds of entering a hotkey sub menu, the
device reverts to the default display.
Note:
5.10
With the exception of pulsed operation, the status of the control inputs
is stored in the battery/supercapacitor backed memory.
Function Keys
Most products have a number of function keys for programming control functionality using
the programmable scheme logic (PSL).
Each function key has an associated programmable tri-colour LED that can be programmed
to give the desired indication on function key activation.
These function keys can be used to trigger any function that they are connected to as part of
the PSL. The function key commands are in the FUNCTION KEYS column.
The first cell down in the FUNCTION KEYS column is the Fn Key Status cell. This contains
a binary string, which represents the function key commands. Their status can be read from
this binary string.
FUNCTION KEYS
Fn Key Status
The next cell down (Fn Key 1) allows you to activate or disable the first function key (1). The
Lock setting allows a function key to be locked. This allows function keys that are set to
Toggled mode and their DDB signal active ‘high’, to be locked in their active state,
preventing any further key presses from deactivating the associated function. Locking a
GS
P746/EN GS/J43
Getting Started
(GS) 3-22
MiCOM P40 Agile P746
function key that is set to the Normal mode causes the associated DDB signals to be
permanently off. This safety feature prevents any inadvertent function key presses from
activating or deactivating critical functions.
FUNCTION KEYS
Fn Key 1
The next cell down (Fn Key 1 Mode) allows you to set the function key to Normal or
Toggled. In the Toggle mode the function key DDB signal output stays in the set state until a
reset command is given, by activating the function key on the next key press. In the Normal
mode, the function key DDB signal stays energised for as long as the function key is pressed
then resets automatically. If required, a minimum pulse width can be programmed by adding
a minimum pulse timer to the function key DDB output signal.
GS
FUNCTION KEYS
Fn Key 1 Mode
The next cell down (Fn Key 1 Label) allows you to change the label assigned to the
function. The default label is Function key 1 in this case. To change the label you need to
press the enter key and then change the text on the bottom line, character by character. This
text is displayed when a function key is accessed in the function key menu, or it can be
displayed in the PSL.
FUNCTION KEYS
Fn Key 1 Label
Subsequent cells allow you to carry out the same procedure as above for the other function
keys.
The status of the function keys is stored in non-volatile memory. If the auxiliary supply is
interrupted, the status of all the function keys is restored. The IED only recognises a single
function key press at a time and a minimum key press duration of approximately 200 ms is
required before the key press is recognised. This feature avoids accidental double presses.
Getting Started
MiCOM P40 Agile P746
6
P746/EN GS/J43
(GS) 3-23
DATE AND TIME CONFIGURATION
The date and time setting will normally be updated automatically by the chosen UTC
(Universal Time Co-ordination) time synchronisation mechanism when the device is in
service. You can also set the date and time manually using the Date/Time cell in the DATE
AND TIME column.
6.1
Using an SNTP Signal
When using SNTP to maintain the clock, the relay must first be connected to the SNTP
server, which should be energized and functioning.
1. In the DATE AND TIME column, check that either the Primary Source or Secondary
Source setting is set to SNTP.
2. Ensure that the relay is receiving valid time synchronisation messages by checking
that the SNTP Status cell reads Server 1 OK or Server 2 OK.
3. Check that the Act. Time Source cell reads SNTP. This indicates that the relay is
using PTP as the source for its time. Note that If IRIG-B or PTP have been selected as
the Primary Source, these must first be disconnected before the device can switch to
SNTP as the active source.
4. Once the relay is using SNTP as the active time source, adjust the time offset of the
universal coordinated time on the SNTP Server equipment, so that local time is
displayed.
5. Check that the time, date and month are correct in the Date/Time cell.
6.2
Using an IRIG-B Signal
When using IRIG-B to maintain the clock, the relay must first be connected to the timing
source equipment (usually a P594/RT430), which should be energized and functioning.
1. In the DATE AND TIME column, check that either the Primary Source or Secondary
Source setting is set to IRIG-B.
2. Ensure the IED is receiving the IRIG-B signal by checking that IRIG-B Status cell
reads Active.
3. Check that the Act. Time Source cell reads IRIG-B. This indicates that the relay is
using IRIG-B as the source for its time. Note that If SNTP or PTP have been selected
as the Primary Source, these must first be disconnected before the device can switch
to IRIG-B as the active source.
4. Once the relay is using IRIG-B as the active time source, adjust the time offset of the
universal coordinated time (satellite clock time) on the satellite clock equipment, so
that local time is displayed.
5. Check that the time, date and month are correct in the Date/Time cell. The IRIG-B
signal does not contain the current year so this also needs to be set manually in this
cell.
6. If the auxiliary supply fails, the time and date are maintained by the supercapacitor.
Therefore, when the auxiliary supply is restored, you should not have to set the time
and date again. To test this, remove the IRIG-B signal, and then remove the auxiliary
supply. Leave the device de-energized for approximately 30 seconds. On
reenergization, the time should be correct.
7. Reconnect the IRIG-B signal.
6.3
Using an IEEE 1588 PTP Siganl
When using IEEE 1588 PTP to maintain the clock, the relay must first be connected to the
PTP Grandmaster, which should be energized and functioning.
1. In the DATE AND TIME column, check that either the Primary Source or Secondary
Source setting is set to PTP.
GS
P746/EN GS/J43
(GS) 3-24
Getting Started
MiCOM P40 Agile P746
2. Set the Domain Number setting. The domain defines which clocks the relay will use
for synchronisation. Therefore this number must match the domain used by the other
clocks on the network.
3. Ensure that the relay is receiving valid time synchronisation messages by checking
that the PTP Status cell reads Valid Master.
4. Check that Act. Time Source cell reads PTP. This indicates that the relay is using
PTP as the source for its time. Note that If IRIG-B or SNTP have been selected as the
Primary Source, these must first be disconnected before the device can switch to PTP
as the active source.
5. Once the IED is using PTP as the active time source, adjust the time offset of the
universal coordinated time on the Master Clock equipment, so that local time is
displayed.
6. Check that the time, date and month are correct in the Date/Time cell.
GS
6.4
Without a Timing Source Signal
If the time and date is not being maintained by an IRIG-B, PTP or SNTP signal, in the DATE
AND TIME column, ensure that both the Primary Source and Secondary Source are set to
NONE.
1. Check that Act. Time Source cell reads Free Running.
2. Set the date and time to the correct local time and date using the Date/Time cell or
the serial protocol.
3. If the auxiliary supply fails, the time and date are maintained by the supercapacitor.
Therefore, when the auxiliary supply is restored, you should not have to set the time
and date again. To test this, remove the auxiliary supply. Leave the device deenergized for approximately 30 seconds. On re-energization, the time should be
correct.
6.5
Time Zone Compensation
The UTC time standard uses Greenwich Mean Time as its standard. Without compensation,
the date and time would be displayed on the device irrespective of its location.
You may wish to display the local time corresponding to its geographical location. You can
do this with the settings LocalTime Enable and LocalTime Offset.
The LocalTime Enable has three setting options; Disabled, Fixed, and Flexible.
With Disabled, no local time zone is maintained. Time synchronisation from any interface
will be used to directly set the master clock. All times displayed on all interfaces will be
based on the master clock with no adjustment.
With Fixed, a local time zone adjustment is defined using the LocalTime Offset setting and
all non-IEC 61850 interfaces, which uses the Simple Network Time Protocol (SNTP), are
compensated to display the local time.
With Flexible, a local time zone adjustment is defined using the LocalTime Offset setting.
The non-local and non-IEC 61850 interfaces can be set to either the UTC zone or the local
time zone. The local interfaces are always set to the local time zone and the Ethernet
interface is always set to the UTC zone.
The interfaces where you can select between UTC and Local Time are the serial interfaces
RP1, RP2 and Tunnelled Courier (if applicable). This is achieved by means of the following
settings, each of which can be set to UTC or Local.:
• RP1 Time Zone
• RP2 Time Zone
• Tunnel Time Zone
The LocalTime Offset setting allows you to enter the local time zone compensation from -12
to + 12 hours at 15 minute intervals.
Getting Started
P746/EN GS/J43
MiCOM P40 Agile P746
6.6
(GS) 3-25
Daylight Saving Time Compensation
It is possible to compensate for Daylight Saving time using the following settings
• DST Enable
• DST Offset
• DST Start
• DST Start Day
• DST Start Month
• DST Start Mins
• DST End
• DST End Day
• DST End Month
• DST End Mins
These settings are described in the DATE AND TIME settings table in the configuration
column.
GS
P746/EN GS/J43
Getting Started
(GS) 3-26
7
MiCOM P40 Agile P746
SETTING GROUPS SELECTION
You can select the setting group using opto inputs, a menu selection, and for some models
the hotkey menu or function keys. You choose which method using the Setting Group setting
in the CONFIGURATION column. There are two possibilities; Select via Menu, or Select via
PSL. If you choose Select via Menu, you set the settings group using the Active Settings
setting or with the hotkeys. If you choose Select via PSL, you set the settings group with
DDB signals according to the following table:
DDB 884
‘SG Select x1’
0
1
0
1
GS
DDB 885
‘SG Select 1x’
0
0
1
1
Selected setting group
1
2
3
4
Each setting group has its own PSL. Once a PSL configuration has been designed it can be
allocated to any one of the 4 setting groups. When downloading or extracting a PSL
configuration, you will be prompted to enter the required setting group to which it will
allocated.
Settings
P746/EN ST/J43
MiCOM P40 Agile P746
(ST) 4-1
ST
SETTINGS
Hardware Suffix:
Software Version:
M
91
P746/EN ST/J43
(ST) 4-2
ST
Settings
MiCOM P40 Agile P746
Settings
P746/EN ST/J43
MiCOM P40 Agile P746
(ST) 4-3
CONTENTS
1
SETTINGS
5
1.1
Relay Settings Configuration
5
1.2
Protection Settings
8
1.2.1
System Configuration
8
1.2.2
Differential Protection Configuration
9
1.2.3
Dead Zone Overcurrent Configuration
12
1.2.4
Non Directional Phase Overcurrent Protection
12
1.2.5
Earth Fault (only available for one box mode)
14
1.2.6
Circuit Breaker Fail and Undercurrent Function
15
1.2.7
Supervision
15
1.3
Control and Support Settings
16
1.3.1
System Data
17
1.3.2
Date and Time
18
1.3.3
CT and VT Ratios
20
1.3.4
Record Control
21
1.3.5
Measurements
22
1.3.6
Communications
22
1.3.6.1
Communications Settings for Courier Protocol
23
1.3.6.2
Rear Port 2 Connection Settings
23
1.3.6.3
Ethernet Port
24
1.3.7
Commissioning Tests
25
1.3.8
Opto Configuration
26
1.3.9
Control Input Configuration
27
1.3.10
Function Keys
28
1.3.11
“IED Configurator” column
28
1.3.12
“SECURITY CONFIG” column
30
1.3.13
Control Input Labels
31
1.4
Disturbance Recorder Settings
31
ST
P746/EN ST/J43
(ST) 4-4
ST
Settings
MiCOM P40 Agile P746
Settings
P746/EN ST/J43
MiCOM P40 Agile P746
1
(ST) 4-5
SETTINGS
The P746 must be configured to the system and application through the appropriate settings.
The settings in this chapter are listed in sequence: protection setting, control and
configuration settings, and disturbance recorder settings. The relay is supplied with a factoryset configuration of default settings.
1.1
Relay Settings Configuration
The relay is a multi-function device that supports numerous different protection, control and
communication features. To simplify the setting of the relay, there is a configuration settings
column which can be used to enable or disable many of the functions of the relay. The
settings associated with any disabled function are not shown in the menu. To disable a
function change the relevant cell in the CONFIGURATION column from Enabled to
Disabled.
The configuration column controls which of the four protection settings groups is selected as
active through the Active settings cell. A protection setting group can also be disabled in
the configuration column, provided it is not the present active group. Similarly, a disabled
setting group cannot be set as the active group.
The configuration column also allows all of the setting values in one group of protection
settings to be copied to another group.
To do this first set the Copy from cell to the protection setting group to be copied, then set
the Copy to cell to the protection group where the copy is to be placed. The copied settings
are initially placed in the temporary scratchpad and will only be used by the relay following
confirmation.
To restore the default values to the settings in any protection settings group, set the restore
defaults cell to the relevant group number. Alternatively, set the restore defaults cell to all
settings to restore all of the relay’s settings to default values, not just the protection groups’
settings. The default settings are initially placed in the scratchpad and are only used by the
relay after they have been confirmed.
Note:
Restoring defaults to all settings includes the rear communication port
settings, which may result in communication via the rear port being disrupted
if the new (default) settings do not match those of the master station.
The aim of the configuration column is to allow general configuration from a single point in
the menu. Items that are disabled or made invisible do not appear in the main relay menu.
Menu Text
Default Setting
Available Settings
CONFIGURATION
Restore Defaults
No Operation
No Operation
All Settings
Setting Group 1
Setting Group 2
Setting Group 3
Setting Group 4
Setting to restore a setting group to factory default settings.
Setting Group
Select via Menu
Select via Menu
Select via PSL
Allows setting group changes to be initiated via Opto Input or via Menu.
Active Settings
Group 1
Group 1, Group 2, Group 3,
Group 4
Selects the active setting group.
Save Changes
Saves all relay settings.
No Operation
No Operation, Save, Abort
ST
P746/EN ST/J43
Settings
(ST) 4-6
MiCOM P40 Agile P746
Menu Text
Copy from
Default Setting
Group 1
Available Settings
Group 1, 2, 3 or 4
Allows displayed settings to be copied from a selected setting group.
Copy to
No Operation
No Operation
Group 1, 2, 3 or 4
Allows displayed settings to be copied to a selected setting group (ready to paste).
Setting Group 1
Enabled
Enabled or Disabled
If the setting group is disabled from the configuration, then all associated settings and
signals are hidden, with the exception of this setting (paste).
ST
Setting Group 2 (as above)
Disabled
Enabled or Disabled
Setting Group 3 (as above)
Disabled
Enabled or Disabled
Setting Group 4 (as above)
Disabled
Enabled or Disabled
OP Mode
One BOX Mode
One BOX Mode or Three
BOX Mode
Setting for one box mode or three box mode relay configuration according to the
installation.
One box mode configuration: The relay protects the three phases. Standard or reverse
phase sequence can be selected.
Three box mode configuration: The relay protects the phase A, B or C (selected in the
phase sequence menu)
Diff Protection
Enabled
Enabled or Disabled
To enable (activate) or disable (turn off) the Differential Protection function.
Dead Zone OC
Disabled
Enabled or Disabled
To enable (activate) or disable (turn off) the dead zone overcurrent function.
Overcurrent
Enabled
Enabled or Disabled
To enable (activate) or disable (turn off) the overcurrent function.
Earth fault
Enabled
Enabled or Disabled
To enable (activate) or disable (turn off) the earth fault overcurrent function.
CB fail
Disabled
Enabled or Disabled
To enable (activate) or disable (turn off) the Circuit Breaker (CB) failure function.
Supervision
Disabled
Enabled or Disabled
To enable (activate) or disable (turn off) the supervision function.
Input Labels
Visible
Invisible or Visible
Sets the Input Labels menu visible further on in the relay settings menu.
Output Labels
Visible
Invisible or Visible
Sets the Output Labels menu visible further on in the relay settings menu.
CT & VT ratios
Visible
Invisible or Visible
Sets the current transformer and voltage transformer ratios and directions visible further in
the menu.
Recorder Control
Visible
Invisible or Visible
Sets the Record Control menu visible further on in the relay settings menu.
Disturb. Recorder
Visible
Invisible or Visible
Sets the Disturbance Recorder menu visible further on in the relay settings menu.
Settings
P746/EN ST/J43
MiCOM P40 Agile P746
(ST) 4-7
Menu Text
Measure't. Set-up
Default Setting
Visible
Available Settings
Invisible or Visible
Sets the Measurement Setup menu visible further on in the relay settings menu.
Comms. Settings
Invisible
Invisible or Visible
Sets the Communications Settings menu visible further on in the relay settings menu.
These are the settings associated with the 1st and 2nd rear communications ports.
Commission Tests
Visible
Invisible or Visible
Sets the Commissioning Tests menu visible further on in the relay settings menu.
Setting Values
Primary
Primary or Secondary
This affects all protection settings that are dependent upon CT and VT ratios.
Control Inputs
Visible
Invisible or Visible
Activates the Control Input status and operation menu further on in the relay setting menu.
Ctrl I/P Config.
Visible
Invisible or Visible
Sets the Control Input Configuration menu visible further on in the relay setting menu.
Ctrl I/P Labels
Visible
Invisible or Visible
Sets the Control Input Labels menu visible further on in the relay setting menu.
Direct Access
Enabled
Enabled/Disabled/Hotkey
only/CB Cntrl. only
Defines what direct access is allowed. Enabled implies control via menu, hotkeys etc.
Function Key
Visible
Invisible or Visible
Sets the Function Key menu visible further on in the relay setting menu.
RP1 Read Only
Disabled
Enabled or Disabled
Enable Remote Read Only Mode on RP1 courier or IEC60870-5-103 communication
protocol.
RP2 Read Only
Disabled
Enabled or Disabled
Enable Remote Read Only Mode on RP2 courier communication protocol.
NIC Read Only
Disabled
Enabled or Disabled
Enable Remote Read Only Mode on the Network Interface card (IEC 61850 tunneled
courier).
LCD Contrast
Sets the LCD contrast.
11
0…31
ST
P746/EN ST/J43
Settings
(ST) 4-8
1.2
MiCOM P40 Agile P746
Protection Settings
The protection settings include all the following items that become active once enabled in the
configuration column of the relay menu database:
• Protection element settings
• Programmable scheme logic (PSL)
There are four groups of protection settings, with each group containing the same setting
cells. One group of protection settings is selected as the active group, and is used by the
protection elements. The settings for group 1 are shown. The settings are discussed in the
same order in which they are displayed in the menu.
1.2.1
System Configuration
Menu Text
ST
Default Setting
Setting Range
Min.
Step Size
Max.
SYSTEM CONFIG
OP Mode: One Box Mode / Three Box Mode
Displays one box mode or three box mode relay configuration (front panel only).
OP Mode = One Box Mode
Phase Sequence
Standard ABC
Standard ABC / Reverse ACB
Sets the phase sequence (standard or reverse, only available for one box mode)
Feeder Numbers
6
0
6
1
Sets the number of feeders connected to the relay (up to 6)
Z1 terminals
000000
0 or 1
Sets the configuration of the terminals fixed to zone 1 from terminal 6 (1st digit) to terminal
1 (last digit). The terminal is activated when its corresponding digit is set to 1.
Z2 terminals
000000
0 or 1
Sets the configuration of the terminals fixed to zone 2 from terminal 6 (1st digit) to terminal
1 (last digit). The terminal is activated when its corresponding digit is set to 1.
Xfer Terminals
011111
0 or 1
Sets the configuration of the terminals that can be switched between the two zones.
ChZONE terminal
011111
0 or 1
Sets the configuration of the terminals that are needed for Check Zone
Bus Coupling by
Breaker
Breaker / none / Isolator
Sets the configuration of the bus coupling. It indicates whether bus is coupled by breaker,
isolator or not (none).
Z1 Bus CT
CT6
No CT / CT1 to CT6
Sets the busbar current transformer belonging to zone 1.
Z1 Bus CT Pol
Inverted
Inverted / standard
Sets the direction of the busbar current transformer in zone 1.
Z2 Bus CT
CT6
No CT / CT1 to CT6
Sets the busbar current transformer belonging to zone 2.
Z2 Bus CT Pol
Standard
Inverted / standard
Sets the direction of the busbar current transformer in zone 2.
Settings
P746/EN ST/J43
MiCOM P40 Agile P746
Menu Text
(ST) 4-9
Default Setting
Setting Range
Min.
Step Size
Max.
OP Mode = Three Box Mode
Protected phase
Phase A
Phase A / Phase B / Phase C
Sets the connected phase to be protected (only available for three box mode).
Feed Numbers
6
0
18
1
Sets the number of feeders connected to the relay (up to 18)
Z1 terminals
0000000000000000
0/1
Sets the configuration of the terminals fixed to zone 1 from terminal 18 (1st digit) to
terminal 1 (last digit). The terminal is activated when its corresponding digit is set to 1.
Z2 terminals
0000000000000000
0/1
Sets the configuration of the terminals fixed to zone 2 from terminal 18 (1st digit) to
terminal 1 (last digit). The terminal is activated when its corresponding digit is set to 1.
Xfer Terminals
0000000000000000
0/1
Sets the configuration of the terminals that can be switched between the two zones.
ChZONE terminal
0000000000000000
0/1
Sets the configuration of the terminals that are needed for Check Zone
Bus Coupling by
Breaker
Breaker / none / Isolator
Sets the configuration of the bus coupling. It indicates whether bus is coupled by breaker,
isolator or none.
Z1 Bus CT
No CT
No CT / CT1 to CT18
Sets the busbar current transformer belonging to zone 1.
Z1 Bus CT Pol
Standard
Inverted / standard
Sets the direction of the busbar current transformer in zone 1.
Z2 Bus CT
No CT
No CT / CT1 to CT18
Sets the busbar current transformer belonging to zone 2.
Z2 Bus CT Pol
Standard
Inverted / standard
Sets the direction of the busbar current transformer in zone 2.
1.2.2
Differential Protection Configuration
The differential element has independent settings for phase and earth (sensitive) faults,
which are used for all zones and the check zone independently.
Menu Text
Default Setting
Setting Range
Min.
Max.
Step Size
DIFF PROTECTION
Busbar Diff
Enabled
Disabled / Enabled
To enable (activate) or disable (turn off) the busbar differential protection. If the function is
activated, the following options are accessible.
ID>2 Current
2.400 kA
50.0 A
30 kA
10.0 A
Setting that determines the minimum differential operating current for all the discriminating
zone biased differential elements.
Phase Slope k2
60.00 %
20.00 %
90.00 %
Slope angle setting for all the zones biased differential element.
1%
ST
P746/EN ST/J43
Settings
(ST) 4-10
MiCOM P40 Agile P746
Menu Text
tDIFF
Default Setting
0.000 s
Setting Range
Min.
0.000 s
Max.
10.00 s
Step Size
10.00 ms
Sets the time delay up to 10 seconds
CheckZone Status
Enabled
Disabled / Enabled
To enable (activate) or disable (turn off)
IDCZ>2 Current
2.400 kA
50.0 A
30 kA
10.0 A
Setting that determines the minimum differential operating current for the Check Zone
biased differential element.
Phase Slope kCZ
30.00 %
0.000 %
90.00 %
1.00 %
Slope angle setting for the check zone biased differential element.
ST
Circuitry fail
Enabled
Disabled / Enabled
To enable (activate) or disable (turn off) the circuitry fail protection. If the function is
activated, the following options are accessible.
ID>1 Current
200 A
50.0 A
5 kA
10.0 A
Setting for the phase circuitry fault monitoring characteristic for the minimum pickup.
Phase Slope k1
10.00 %
0.000 %
50.00 %
1.000 %
Slope angle setting for the phase circuitry fault monitoring characteristic.
ID>1 Alarm timer
5.000 s
0.000 s
600.0 s
10.00 ms
Setting for the operating time delay of the phase circuitry fault monitoring
CZ CCTFAIL MODE
AlarmSR&No Block
Alarm & No Block / AlarmSR&No Block /
Blocking Latched / Alarm Latched / SelReset
Options for the Check Zone differential element faulty calculation due to wrong position of
CB or isolator or CT failure are as follow:
– AlarmSR&No Block: The CZ does not block any zone trip and the alarm disappears as
soon as the CZ calculation is right.
– Alarm & No Block: The CZ does not block any zone trip and the alarm disappears only
after manual reset.
– Self-Reset: The CZ blocks any zone trip and both the blocking and the alarm
disappear as soon as the CZ calculation is right.
– Alarm Latched: The CZ blocks any zone trip, the blocking disappears as soon as the
CZ calculation is right but the alarm disappears only after manual reset.
– Blocking Latched: The CZ blocks any zone trip and both the blocking and the alarm
disappear only after manual reset.
Settings
P746/EN ST/J43
MiCOM P40 Agile P746
Menu Text
Zx CCTFAIL MODE
(ST) 4-11
Default Setting
Self-Reset
Setting Range
Min.
Step Size
Max.
Self-Reset / Alarm Latched / Blocking
Latched
Options for all the Zones differential element faulty calculation due to wrong position of
CB or isolator or CT failure are as follow:
– Self-Reset: The Zone is blocked and both the blocking and the alarm disappear as
soon as the Zone calculation is right.
– Alarm Latched: The Zone is blocked, the blocking disappears as soon as the Zone
calculation is right but the alarm disappears only after manual reset.
– Blocking Latched: The Zone is blocked and both the blocking and the alarm disappear
only after manual reset.
cctFailBlkMode
Blocking/Phase
Blocking/Phase
ST
3phase Blocking
Options for all the Zones and Check Zone differential element faulty calculation due to
wrong position of CB or isolator or CT failure are as follow:
– Blocking / phase: If the faulty calculation occurs on one phase only, the Zone and/or
Check Zone is blocked for this phase only.
– 3phase Blocking: If the faulty calculation occurs on one phase only, the Zone and/or
Check Zone is blocked for the 3 phases.
CCTFAIL tReset
5.000 s
0.000 s
600.0 s
100.0 ms
Setting for the reset time delay of the circuitry fail reset option.
Voltage check
Disabled
Disabled / Enabled
This setting is to disable or enable voltage check for zone current differential protection. If
it is enabled, zone current differential protection will be blocked if voltage check criteria is
not met. For example, if phase voltage is greater than the V< threshold or negative
sequence voltage is less than the V> threshold. When dead bus is detected, voltage
check will be bypassed.
VT Connected to
Zone 1
Zone 1 / Zone 2
If “voltage check” is enabled, used to indicate the voltage check zone.
Voltage Mode
Phase-Neutral
Phase-Phase / Phase-Neutral
If set to Ph-Ph, the settings threshold below (V<) will be taken as Ph-Ph value. The same
is true if Voltage Mode is set to Ph-N.
V< Status
Disabled
Disabled / Enabled
To enable (activate) or disable (turn off) the undervoltage check.
V< Set
80.00 V
10.00 V
120.0 V
1.00 V
If “V< Status” is enabled, pickup setting for undervoltage element.
V< PickUpTimer
0.000 s
0.000 s
10.00 s
2.000 ms
If “V< Status” is enabled, sets the minimum pickup for undervoltage timer.
V1< Status
Disabled
Disabled / Enabled
To enable (activate) or disable (turn off) the first stage of undervoltage element.
V1< Set
80.00 V
10.00 V
120.0 V
1.00 V
If “V1< Status” is enabled, pickup setting for first stage of undervoltage element.
V1< PickUpTimer
0.000 s
0.000 s
10.00 s
2.000 ms
If “V1< Status” is enabled, sets the minimum pickup for first stage of undervoltage timer.
P746/EN ST/J43
Settings
(ST) 4-12
MiCOM P40 Agile P746
Menu Text
V2> Status
Default Setting
Disabled
Setting Range
Min.
Step Size
Max.
Disabled / Enabled
To enable (activate) or disable (turn off) second stage of overvoltage. When activated,
V2> configuration is visible
V2> Set
10.00 V
1.000 V
110.0 V
1.000 V
If “V2> Status” is enabled, pickup setting for second stage of overvoltage element.
V2> PickUpTimer
0.000 s
0.000 s
10.00 s
2.000 ms
If “V2> Status” is enabled, sets the minimum pickup for first stage of overvoltage timer.
VN> Status
Disabled
Disabled / Enabled
To enable (activate) or disable (turn off) the zero sequence voltage check.
VN> Set
ST
10.00 V
1.000 V
80.00 V
1.000 V
If “VN> Status” is enabled, pickup setting for zero sequence voltage element.
VN> PickUpTimer
0.000 s
0.000 s
10.00 s
2.000 ms
If “VN> Status” is enabled, sets the minimum pickup for zero sequence voltage timer.
Ph Comp PU ratio
50%
5%
250%
1%
This setting is used to define the threshold above which the feeder current will be included
in the phase comparison algorithm. Individual feeder current threshold for consideration in
Phase comparison = Ph Comp PU ratio Setting x ID>2 Setting (Primary)
1.2.3
Dead Zone Overcurrent Configuration
Menu Text
Setting Range
Default Setting
Min.
Max.
Step Size
DEAD ZONE OC
I> Status
I> Status
Disabled
Disabled / Enabled
To enable (activate) or disable (turn off) the overcurrent check.
I> Current Set
120.0 %
10.00 %
400.0 %
1%
0.000 s
100.0 s
10.00 ms
Pick-up setting for overcurrent element.
I> Time Delay
50.00 ms
Sets the time-delay for the overcurrent element.
1.2.4
Non Directional Phase Overcurrent Protection
The overcurrent protection in the P746 provides two stages non-directional three-phase
overcurrent protection with independent time delay characteristics. All overcurrent settings
apply to all three phases but are independent for each of the four stages.
The first stage of overcurrent protection has time-delayed characteristics which are
selectable between inverse definite minimum time (IDMT), or definite time (DT). The second
stage has definite time characteristics only.
Settings
P746/EN ST/J43
MiCOM P40 Agile P746
Menu Text
(ST) 4-13
Default Setting
Setting Range
Min.
Max.
Step Size
OVERCURRENT
TERMINAL 1 to 6 (one box) / TERMINAL 1 to 18 (three box)
I>1 Function
IEC S inverse
Disabled / US ST Inverse / US Inverse /
IEEE E Inverse / IEEE V Inverse / IEEEE
M Inverse / RI / UK Rectifier /UK LT
Inverse / IEC E Inverse / IEC V inverse /
IEC S Inverse
Setting for the tripping characteristic for the first stage overcurrent element.
I>1 Current
1.000 kA
80.00 A
4.000 kA
10 A
100.0
0.010
Pick-up setting for first stage overcurrent element
I>1 Time Dial
1.000
0.010
Setting for the time multiplier setting to adjust the operating time of the IEEE/US IDMT
curves.
I>1 Reset Char
DT
DT / Inverse
Setting to determine the type of reset/release characteristic of the IEEE/US curves.
I>1 tReset
0.000 s
0.000 s
100.0 s
10.00 ms
Setting that determines the reset/release time for definite time reset characteristic.
I>1 k(RI)
1.000
0.100
10.00
0.050
Selects the electromechanical inverse time curve (RI) curve K value from 0.100 to 10 for
the first stage of phase overcurrent protection
I>1 TMS
1.000
0.025
1.200
0.025
Setting for the time multiplier setting to adjust the operating time of the IEC IDMT
characteristic
I>1 Time Delay
1.000 s
0.000 s
100.0 s
10.00 ms
Setting for the time-delay for the definite time setting if selected for first stage element
I>2 Function
Disabled
Disabled / DT
Setting for the second stage overcurrent element.
I>2 Current
1.000 kA
80.00 A.
32.00 kA
10 A
100.0 s
10.00 s
Pick-up setting for second stage overcurrent element.
I>2 Time delay
1.000 s
0.000 s
Setting for the operating time-delay for second stage overcurrent element.
ST
P746/EN ST/J43
Settings
(ST) 4-14
1.2.5
MiCOM P40 Agile P746
Earth Fault (only available for one box mode)
Menu Text
Default Setting
Setting Range
Min.
Max.
Step Size
EARTH FAULT
TERMINAL 1 to 6 (one box)
IN>1 Function
IEC S inverse
Disabled / US ST Inverse / US Inverse /
IEEE E Inverse / IEEE V Inverse / IEEE M
Inverse / IDG / UK Rectifier /UK LT Inverse
/ IEC E Inverse / IEC V inverse / IEC S
Inverse /DT / RI
Setting for the tripping characteristic for the first stage earth fault element.
IN>1 Current
ST
200.0 A
80.00 A
4.000 kA
10 A
100.0
0.010
Pick-up setting for the first stage earth fault element
IN>1 Time Dial
1.000
0.010
Setting for the time multiplier setting to adjust the operating time of the IEEE/US IDMT
curves.
IN>1 Reset Char
DT
DT / Inverse
Setting to determine the type of reset/release characteristic of the IEEE/US curves.
IN>1 tReset
0.000 s
0.000 s
100.0 s
10.00 ms
Setting that determines the reset/release time for definite time reset characteristic.
IN>1 IDG Is
1.500
1.000
4.000
0.100
0.025
1.200
0.025
Setting to determine the IDG characteristics
IN>1 TMS
1.000
Setting for the time multiplier setting to adjust the operating time of the IEC IDMT
characteristic
IN>1 IDG Time
1.200 s
1.000 s
2.000 s
10 ms
0.100
10.00
0.050
Setting thet determines the IDG time.
IN>1 k (RI)
1.000
Selects the electromechanical inverse time curve (RI) curve K value from 0.100 to 10 for
the first stage of ground overcurrent protection
IN>1 Time Delay
1.000 s
0.000 s
200.0 s
10.00 ms
Setting for the time-delay for the definite time setting if selected for first stage element
IN>2 Function
Disabled
Disabled / DT
Setting to enable or disable the second stage overcurrent element.
IN>2 Current
200.0 A
80.00 A.
32.00 kA
10 A
100.0 s
10.00 s
Pick-up setting for second stage overcurrent element.
IN>2 Time delay
1.000 s
0.000 s
Setting for the operating time-delay for second stage overcurrent element.
Settings
P746/EN ST/J43
MiCOM P40 Agile P746
1.2.6
(ST) 4-15
Circuit Breaker Fail and Undercurrent Function
This function consists of two-stage circuit breaker fail functions that can be initiated by:
• Internal protection element initiation.
• External protection element initiation.
For current-based protection, the reset condition is based on undercurrent operation to
determine that the CB has opened. For the non-current based protection, the reset criteria
may be selected by means of a setting for determining a CB Failure condition.
It is common practice to use low set undercurrent elements in protection relays to indicate
that circuit breaker poles have interrupted the fault or load current, as required.
Menu Text
Default Setting
Setting Range
Min.
Max.
Step Size
CB FAIL & I<
ST
BREAKER FAIL
CBF Control by
I< and 52a
52a / I< / I< and 52a
Setting which determines the elements that will reset the circuit breaker fail time protection
function.
Both means that 52a and current criteria have to indicate open to reset the CB fail.
I< Current Set
5.000 %
5.000 %
400.0 %
1.000 %
If “CBF Control by” “I<” or “I> and 52a”: setting that determines the circuit breaker fail timer
reset current for overcurrent based protection circuit breaker fail initiation
CB Fail 1 Timer
50.00 ms
0.000 s
10.00 s
10.00 ms
Setting for the circuit breaker fail timer stage 1 for which the initiating condition must be
valid.
CB Fail 2 Timer
200.0 ms
40.00 ms
10.00 s
10.00 ms
Setting to enable or disable the second stage of the circuit breaker function.
CB Fail 3 Timer
50.00 ms
0.000 s
10.00 s
10.00 ms
Setting to enable or disable the third stage of the circuit breaker function.
CB Fail 4 Timer
200.0 ms
40.00 ms
10.00 s
10.00 ms
Setting to enable or disable the fourth stage of the circuit breaker function.
I> Status
Disabled
Disabled / Enabled
To enable (activate) or disable (turn off) the overcurrent check
I> Current Set
120.0 %
5.000 %
400.0 %
1.000 %
If “I> Status” is enabled, pick-up setting for overcurrent element
1.2.7
Supervision
Menu Text
Default Setting
Setting Range
Min.
Max.
Step Size
SUPERVISION
VT SUPERVISION (One Box mode only)
VTS Status
Blocking
Blocking / indication
Sets Voltage Transformer Supervision (VTS) operation.
The relay respond as follows, on operation of any VTS element: VTS set to provide alarm
indication only or blocking of voltage dependent protection elements.
P746/EN ST/J43
Settings
(ST) 4-16
MiCOM P40 Agile P746
Menu Text
VTS Reset Mode
Default Setting
Manual
Setting Range
Min.
Max.
Step Size
Manual / Auto
This setting enables the automatic or manual mode of the voltage transformer supervision
reset mode.
VTS Time Delay
5.000 s
1.000 s
10.00 s
100.0 ms
This setting determines the operating time-delay of the element on detection of a voltage
transformer supervision condition.
Zone Bias Ratio
0.7
0
1
0.01
This setting is for One Box mode only. It is the threshold for the ratio of minimum phase
bias current to maximum phase bias current in the same zone that main VT is connected
to. When the ratio is less than the threshold, it will prevent VTS to assert.
CT SUPERVISION (One Box mode only)
ST
Diff CTS
Enabled
Enabled / Disabled
Setting to enable or disable the differential CT Supervision. Differential CTS is based on
measurement of the ratio of I2 and I1 at each zone ends.
CTS Status
Blocking
Blocking / Indication
This menu enables or disables Current Transformer Supervision (CTS): when “Indication”
is selected, CTS is enabled, the following menus are accessible and settable.
CTS Time Delay
2.000 s
0.000 s
10.00 s
100.0 ms
This setting determines the operating time-delay of the element upon detection of a
current transformer supervision condition.
CTS I1
10.00 %
5.000 %
100.0 %
1.000 %
Setting for positive sequence current that is not to be exceeded in order to determine CTS
condition
CTS I2/I1>1
5.000 %
5.000 %
100.0 %
1.000 %
Setting for low set ratio that is not to be exceeded in order to determine CTS condition
CTS I2/I1>2
40.00 %
5.000 %
100.0 %
1.000 %
Setting for the high set ratio to be exceeded at exactly one end in order to determine CTS
condition
1.3
Control and Support Settings
The control and support settings are part of the main menu and are used to configure the
relays global configuration. It includes submenu settings:
• Relay function configuration settings
• CT & VT ratio settings
• Reset LEDs
• Active protection setting group
• Password & language settings
• Communications settings
• Measurement settings
• Event & fault record settings
• User interface settings
• Commissioning settings
Settings
P746/EN ST/J43
MiCOM P40 Agile P746
1.3.1
(ST) 4-17
System Data
This menu provides information for the device and general status of the relay.
Menu Text
Language
Setting Range
Default Setting
Min.
Step Size
Max.
English
The default language used by the device. Selectable as English, French, German,
Russian, Spanish.
Password
________________
Device default password.
Sys. Fn. Links
0
1
Setting to allow the fixed function trip LED to be self resetting.
Description
ST
MiCOM P746
16 character relay description. Can be edited.
Plant Reference
MiCOM
Associated plant description and can be edited.
Model Number
P746??????????K
Relay model number. This display cannot be altered.
Serial Number
6 digits + 1 letter
Relay model number. This display cannot be altered.
Frequency
50 Hz
10Hz
Relay set frequency. Settable between 50 and 60Hz
Comms Level
2
Displays the conformance of the relay to the Courier Level 2 comms.
Relay Address
255
0
255
1
Fixed front and first rear port relay address.
Plant Status
00000000000000
Displays the circuit breaker plant status for up to 6 circuit breakers (one box mode) or up
to 18 circuit breakers (three box modes).
Control Status
0000000000000000
Not used.
Active Group
1
Displays the active settings group.
Software Ref. 1
Displays the relay software version including protocol and relay model.
Opto I/P Status
00000000000000000000000000000000
Duplicate. Displays the status of opto inputs (L1 to L32).
Opto I/P Status2
00000000
Duplicate. Displays the status of opto inputs (L33 to L40).
Plant Status
01010101010101
Displays the circuit breaker plant status for up to 6 circuit breakers (from CB1 to CB6 and
Bus CB coupler).
P746/EN ST/J43
Settings
(ST) 4-18
MiCOM P40 Agile P746
Menu Text
Rly O/P Status
Default Setting
Setting Range
Min.
Max.
Step Size
00000000
Duplicate. Displays the status of output relays.
Alarm Status 1
00000000000000000000000000000000
32 bits field give status of first 32 alarms.
Alarm Status 2
00000000
Next 32 alarm status defined.
Alarm Status 3
00000000
Next 16 alarm status defined. Assigned specifically for platform alarms.
Access Level
ST
Displays the current access level (see section P746/EN GS for level description and
access):
Level 0 = read access to some cells (system data and security config columns). Write
access to password entry and LCD contrast
Level 1 = level 0 + read access to all data and settings, poll measurements. Write access
to some cells (level 1 password setting, select event, main and fault, extract events
Level 2 = level 1 + write access to setting cells that change visibility, setting values
selector, reset indication, demand, statistics and CB data counters and level 2 password
setting,
Level 3 = All other settings.
Password Control
2
Sets the menu access level for the relay. This setting can only be changed when level 2
access is enabled.
Password Level 1
****
Allows user to change password level 1 (password may be any length between 0 and 8
characters long). See section P746/EN CS for password strengthening and validation and
blank password management.
Password Level 2
****
Allows user to change password level 2 (password may be any length between 0 and 8
characters long). See section P746/EN CS for password strengthening and validation and
blank password management.
Password Level 3
****
Allows user to change password level 3 (password may be any length between 0 and 8
characters long). See section P746/EN CS for password strengthening and validation and
blank password management.
Security Features
1
Displays the level of cyber security implemented, 1 = phase 1.
1.3.2
Date and Time
Displays the date and time as well as the battery condition.
Menu Text
Date/Time
Default Setting
Setting Range
Min.
Max.
Data
Displays the relay’s current date and time.
IRIG-B Sync
Disabled
Enable IRIG-B time synchronization (with IRIG-B option).
Disabled or Enabled
Step Size
Settings
P746/EN ST/J43
MiCOM P40 Agile P746
(ST) 4-19
Menu Text
IRIG-B Status
Setting Range
Default Setting
Min.
Step Size
Max.
Card not fitted/Card failed/ Signal
healthy/No signal
Data
Displays the status of IRIG-B (with IRIG-B option).
Battery Status
Data
Displays whether the battery is healthy or not.
Battery Alarm
Enabled
Disabled or Enabled
Setting that determines whether an unhealthy relay battery condition is alarmed or not.
SNTP Status
Data
Disabled, Trying Server 1, Trying Server
2, Server 1 OK, Server 2 OK, No
response, No valid clock
ST
For Ethernet option only:
Displays information about the SNTP time synchronization status
LocalTime Enable
Disabled
Disabled/Fixed/Flexible
Setting to turn on/off local time adjustments.
Disabled - No local time zone will be maintained. Time synchronisation from any interface
will be used to directly set the master clock and all displayed (or read) times on all
interfaces will be based on the master clock with no adjustment.
Fixed - A local time zone adjustment can be defined using the LocalTime offset setting
and all interfaces will use local time except SNTP time synchronisation and IEC61850
timestamps.
Flexible - A local time zone adjustment can be defined using the LocalTime offset setting
and each interface can be assigned to the UTC zone or local time zone with the exception
of the local interfaces which will always be in the local time zone and IEC61850/SNTP
which will always be in the UTC zone.
LocalTime Offset
0
-720
720
15
Setting to specify an offset of -12 to +12 hrs in 15 minute intervals for local time zone. This
adjustment is applied to the time based on the master clock which is UTC/GMT
DST Enable
Disabled
Disabled or Enabled
Setting to turn on/off daylight saving time adjustment to local time.
DST Offset
60mins
30
60
30min
Setting to specify daylight saving offset which will be used for the time adjustment to local
time.
DST Start
Last
First, Second, Third, Fourth, Last
Setting to specify the week of the month in which daylight saving time adjustment starts
DST Start Day
Sunday
Monday, Tuesday, Wednesday, Thursday,
Friday, Saturday
Setting to specify the day of the week in which daylight saving time adjustment starts
DST Start Month
March
January, February, March, April, May,
June, July, August, September, October,
November, December
Setting to specify the month in which daylight saving time adjustment starts
DST Start Mins
60min
0
1425
15min
Setting to specify the time of day in which daylight saving time adjustment starts. This is
set relative to 00:00 hrs on the selected day when time adjustment is to start.
P746/EN ST/J43
Settings
(ST) 4-20
MiCOM P40 Agile P746
Menu Text
DST End
Setting Range
Default Setting
Last
Min.
Max.
Step Size
First, Second, Third, Fourth, Last
Setting to specify the week of the month in which daylight saving time adjustment ends.
DST End Day
Sunday
Monday, Tuesday, Wednesday, Thursday,
Friday, Saturday
Setting to specify the day of the week in which daylight saving time adjustment ends
DST End Month
October
January, February, March, April, May,
June, July, August, September, October,
November, December
Setting to specify the month in which daylight saving time adjustment ends
DST End Mins
ST
60
0
1425
15min
Setting to specify the time of day in which daylight saving time adjustment ends. This is
set relative to 00:00 hrs on the selected day when time adjustment is to end.
RP1 Time Zone
Local
UTC or Local
Setting for the rear port 1 interface to specify if time synchronisation received will be local
or universal time coordinated
RP2 Time Zone
Local
UTC or Local
Setting for the rear port 2 interface to specify if time synchronisation received will be local
or universal time coordinated
Tunnel Time Zone
Local
UTC or Local
With Ethernet option only:
Setting to specify if time synchronisation received will be local or universal time coordinate when ‘tunnelling’ courier protocol over Ethernet.
1.3.3
CT and VT Ratios
Menu Text
Default Setting
Setting Range
Min.
Max.
Step Size
CT AND VT RATIOS
Main VT Primary
110.0 V
100.0 V
1.000 MV
1.000 V
Sets the phase Voltage Transformer input primary voltage rating.
Main VT’s Sec’y
110.0 V
80.00 V
140.0 V
1.000 V
Sets the phase Voltage Transformer input secondary voltage rating.
ReferenceCurrent
2000 kA
1.000 A
30.00 kA
1A
Used to align all currents against a common primary reference
T1 CT to T6 CT (one box) / T1 CT to T18 CT (three box)
Polarity
Standard
Standard / Inverted
Standard or reverse phase sequence can be selected. This menu sets this phase
sequence.
Primary
1.000 kA
1.000 A
30.00 kA
Sets the phase Current Transformer input primary current rating.
Secondary
1.000 A
1.000 A or 5.000 A
Sets the phase Current Transformer input secondary current rating.
1A
Settings
P746/EN ST/J43
MiCOM P40 Agile P746
1.3.4
(ST) 4-21
Record Control
It is possible to disable the reporting of events from all interfaces that supports setting
changes. The settings that control the various types of events are in the Record Control
column. The effect of setting each to disabled is as follows:
Menu Text
Default Setting
Available Settings
RECORD CONTROL
Clear Events
No
No or Yes
Selecting “Yes” will cause the existing event log to be cleared and an event will be
generated indicating that the events have been erased.
Clear Faults
No
No or Yes
Selecting “Yes” will cause the existing fault records to be erased from the relay.
Clear Maint
No
No or Yes
Selecting “Yes” will cause the existing maintenance records to be erased from the relay.
Alarm Event
Enabled
Enabled or Disabled
Disabling this setting means that all the occurrences that produce an alarm will result in no
event being generated.
Relay O/P Event
Enabled
Enabled or Disabled
Disabling this setting means that no event will be generated for any change in logic input
state.
Opto Input Event
Enabled
Enabled or Disabled
Disabling this setting means that no event will be generated for any change in logic input
state.
General Event
Enabled
Enabled or Disabled
Disabling this setting means that no General Events will be generated
Fault Rec Event
Enabled
Enabled or Disabled
Disabling this setting means that no event will be generated for any fault that produces a
fault record
Maint. Rec Event
Enabled
Enabled or Disabled
Disabling this setting means that no event will be generated for any occurrence that
produces a maintenance record.
Protection Event
Enabled
Enabled or Disabled
Disabling this setting means that any operation of protection elements will not be logged as
an event.
Clear Dist Recs
No
No or Yes
Selecting “Yes” will cause the existing disturbance records to be cleared and an event will
be generated indicating that the disturbance records have been erased.
DDB 31 - 0
11111111111111111111111111111111
Displays the status of DDB signals 0 – 31.
DDB 2047 - 2016
11111111111111111111111111111111
Displays the status of DDB signals 2047 – 2016.
ST
P746/EN ST/J43
Settings
(ST) 4-22
1.3.5
MiCOM P40 Agile P746
Measurements
Menu Text
Default Settings
Available settings
MEASUREMENT SETUP
Default Display
Description
Description / 3 ph-neutral Voltage
/ Date and Time / Plant reference
/ Frequency / Access Level
This setting (front panel user interface only) can be used to select the default display from
a range of options, note that it is also possible to view the other default displays whilst at
the default level using the  and  keys. However, once the 15 min timeout elapses the
default display will revert to that selected by this setting.
Local Values
Primary
Primary/Secondary
This setting controls whether measured values via the front panel user interface and the
front courier port are displayed as primary or secondary quantities.
ST
Remote Values
Primary
Primary/Secondary
This setting controls whether measured values via the rear communication port are
displayed as primary or secondary quantities.
Measurement ref
VA
IA1 / IB1 / IC1 / VA / VB / VC /
IA2 / IB2 / IC2 / IA3 / IB3 / IC3 /
IA4 / IB4 / IC4 / IA5 / IB5 / IC5 /
IA6 / IB6 / IC6
This menu sets the reference of the measure (phase reference and angle)
Measurement ref
VA
IA1 / IB1 / IC1 / VA / VB / VC /
IA2 / IB2 / IC2 / IA3 / IB3 / IC3 /
IA4 / IB4 / IC4 / IA5 / IB5 / IC5 /
IA6 / IB6 / IC6
This menu sets the reference of the measure (phase reference and angle)
Measurement Mode
1.3.6
0
0/1/2/3
Communications
The communications settings apply to the rear communications port. Further details are
given in the SCADA communications section (P746/EN SC).
These settings are available in the menu Communications column and are displayed.
Settings
P746/EN ST/J43
MiCOM P40 Agile P746
1.3.6.1
(ST) 4-23
Communications Settings for Courier Protocol
Menu Text
Setting Range
Default Setting
Min.
Max.
Step Size
COMMUNICATIONS
RP1 Protocol
Courier
Indicates the communications protocol that will be used on the rear communications port.
RP1 Address
255
0
255
1
This cell sets the unique address for the relay such that only one relay is accessed by
master station software.
RP1 InactivTimer
15.00 mins.
1 mins.
30 mins.
1 min.
This cell controls how long the relay will wait without receiving any messages on the rear
port before it reverts to its default state, including resetting any password access that was
enabled.
RP1 Card Status
K Bus OK
This cell indicates the status of the communication card.
RP1 Port Config.
KBus
KBus or EIA(RS)485
This cell defines whether an electrical KBus or EIA(RS)485 is being used for
communication between the master station and relay.
RP1 Comms. Mode
IEC 60870 FT1.2
Frame
IEC 60870 FT1.2 Frame or
10-Bit No Parity
The choice is either IEC60870 FT1.2 for normal operation with 11-bit modems, or 10-bit
no parity.
RP1 Baud Rate
19200 bits/s
9600 bits/s, 19200 bits/s or 38400 bits/s
This cell controls the communication speed between relay and master station.
important that both relay and master station are set at the same speed setting.
1.3.6.2
It is
Rear Port 2 Connection Settings
These settings are configurable for the second rear port, which is only available with the
courier protocol.
Menu Text
Default Setting
Setting Range
Min.
Max.
Step Size
COMMUNICATIONS
RP2 Protocol
Courier
Indicates the communications protocol that will be used on the rear communications port.
RP2 Card Status
Unsupported, Card Not Fitted, EIA232 OK, EIA485 OK or K Bus
OK
RP2 versions only. Displays the status of the card in RP2
RP2 Port Config.
RS232
EIA(RS)232, EIA(RS)485 or KBus
This cell defines whether an electrical EIA(RS)232, EIA(RS)485 or KBus is being used for
communication.
RP2 Comms. Mode
IEC60870 FT1.2
Frame
IEC60870 FT1.2 Frame or 10-Bit No
Parity
The choice is either IEC60870 FT1.2 for normal operation with 11-bit modems, or 10-bit no
parity.
ST
P746/EN ST/J43
Settings
(ST) 4-24
MiCOM P40 Agile P746
Menu Text
RP2 Address
Setting Range
Default Setting
255
Min.
0
Step Size
Max.
255
1
This cell sets the unique address for the relay such that only one relay is accessed by
master station software.
RP2 Inactivity Timer
15 mins.
1 mins.
30 mins.
1 min.
This cell controls how long the relay will wait without receiving any messages on the rear
port before it reverts to its default state, including resetting any password access that was
enabled.
RP2 Baud Rate
19200 bits/s
9600 bits/s, 19200 bits/s or 38400 bits/s
This cell controls the communication speed between relay and master station.
important that both relay and master station are set at the same speed setting.
ST
1.3.6.3
It is
Ethernet Port
Menu Text
NIC Protocol
Default Setting
Setting Range
Min.
Max.
Step Size
IEC 61850
Indicates that IEC 61850 will be used on the rear Ethernet port.
NIC MAC Address
Ethernet MAC Address
Indicates the MAC address of the rear Ethernet port.
NIC Tunl Timeout
5 mins
1 min
30 mins
1 min
Duration of time waited before an inactive tunnel to MiCOM S1 Agile is reset.
NIC Link Report
Alarm, Event, None
Alarm
Configures how a failed/unfitted network link (copper or fiber) is reported:
Alarm - an alarm is raised for a failed link
Event - an event is logged for a failed link
None
- nothing reported for a failed link
NIC Link Timeout
60 s
0.1 s
60 s
0.1 s
Duration of time waited, after failed network link is detected, before communication by the
alternative media interface is attempted.
Settings
P746/EN ST/J43
MiCOM P40 Agile P746
1.3.7
(ST) 4-25
Commissioning Tests
There are menu cells which allow the status of the opto-isolated inputs, output relay
contacts, internal digital data bus (DDB) signals and user-programmable LEDs to be
monitored. Additionally, there are cells to test the operation of the output contacts, userprogrammable LEDs.
Menu Text
Default Setting
Available Settings
COMMISSION TESTS
Opto I/P Status
00000000000000000000000000000000
This menu cell displays the status of the relay’s opto-isolated inputs (L01 to L32) as a binary
string, a ‘1’ indicating an energized opto-isolated input and a ‘0’ a de-energized one
Opto I/P Status2
00000000
Status of the next relay’s opto-isolated inputs (L33 to L40)
Rly O/P Status
ST
00000000000000000000000000000000
This menu cell displays the status of the digital data bus (DDB) signals that result in
energisation of the output relays (R01 to R32) as a binary string, a ‘1’ indicating an operated
state and ‘0’ a non-operated state.
When the ‘Test Mode’ cell is set to ‘Enabled’ the ‘Relay O/P Status’ cell does not show the
current status of the output relays and hence can not be used to confirm operation of the
output relays. Therefore, it is necessary to monitor the state of each contact in turn.
Test Port Status
00000000
This menu cell displays the status of the eight digital data bus (DDB) signals that have been
allocated in the ‘Monitor Bit’ cells.
Monitor Bit 1
Relay Label 01
0 to 1022
See PSL section for
details of digital data
bus signals
The eight ‘Monitor Bit’ cells allow the user to select the status of which digital data bus
signals can be observed in the ‘Test Port Status’ cell or via the monitor/download port.
Monitor Bit 8
Relay Label 08
0 to 1022
The eight ‘Monitor Bit’ cells allow the user to select the status of which digital data bus
signals can be observed in the ‘Test Port Status’ cell or via the monitor/download port.
Test Mode
Disabled
Disabled / Contacts
blocked / Test Mode
The Test Mode menu cell is used to allow secondary injection testing to be performed on a
Peripheral Unit relay without operation of the connected zone. It also enables a facility to
directly test the output contacts by applying menu controlled test signals. To select test
mode the Test Mode menu cell should be set to ‘Contact blocked’, which takes the relay out
of service. It also causes an alarm condition to be recorded and the yellow ‘Out of Service’
LED to illuminate and an alarm message ‘Out of Service’ is given. The 87BB and 50BF
protections are in service as long as the cells ‘87BB Monitoring’ and ‘87BB & 50BF disabl’
are equal to 0. Once testing is complete the cell must be set back to ‘Disabled’ to restore
the relay back to service.
Test Pattern
0000000000000000
0 = Not Operated
1 = Operated
This cell is used to select the output relay contacts that will be tested when the ‘Contact
Test’ cell is set to ‘Apply Test’.
P746/EN ST/J43
Settings
(ST) 4-26
MiCOM P40 Agile P746
Menu Text
Contact Test
Default Setting
Available Settings
No Operation, Apply
Test, Remove Test
No Operation
When the ‘Apply Test’ command in this cell is issued the contacts set for operation (set to
‘1’) in the ‘Test Pattern’ cell change state. After the test has been applied the command text
on the LCD will change to ‘No Operation’ and the contacts will remain in the Test State until
reset issuing the ‘Remove Test’ command. The command text on the LCD will again revert
to ‘No Operation’ after the ‘Remove Test’ command has been issued.
Note:
When the ‘Test Mode’ cell is set to ‘Enabled’ the ‘Relay O/P Status’ cell does not
show the current status of the output relays and hence can not be used to confirm
operation of the output relays. Therefore, it will be necessary to monitor the state
of each contact in turn.
Test LEDs
ST
No Operation
Apply Test
No Operation
When the ‘Apply Test’ command in this cell is issued the eighteen user-programmable
LEDs will illuminate for approximately 2 seconds before they extinguish and the command
text on the LCD reverts to ‘No Operation’.
Red LED Status
000001000100000000
This cell is an eighteen bit binary string that indicates which of the user-programmable
LEDs on the relay are illuminated with the Red LED input active when accessing the relay
from a remote location, a ‘1’ indicating a particular LED is lit and a ‘0’ not lit.
Green LED Status
000001000100000000
This cell is an eighteen bit binary string that indicates which of the user-programmable
LEDs on the relay are illuminated with the Green LED input active when accessing the relay
from a remote location, a ‘1’ indicating a particular LED is lit and a ‘0’ not lit.
Test Zone
None / Zone1 / Zone2 /
Zone 1 and Zone2
none
The Test Zone cell is used to block a zone for test. It disables the 50BF protection and block
all the tripping relays connected to the blocked zone(s). Alarm LED is lit.
On, On-blocked, Test,
IED Mod Beh Status
Test-blocked, Off
Indicates the current Mod/Beh status of whole IED
SubscriberSim
Disabled
Disabled, Enabled
Used to enable/disable the 'subscriber simulation' feature, for Sampled Values and GOOSE
subscriptions
DDB 31 - 0
00000000000000000000000000000000
Displays the status of DDB signals 0 – 31.
DDB 2047 - 2016
00000000000000000000000000000000
Displays the status of DDB signals 2047 – 2016.
1.3.8
Opto Configuration
Menu Text
Default Setting
Setting Range
Min.
Max.
Step Size
OPTO CONFIG.
Global Nominal V
48/54V
24/27V, 30/34V, 48/54V, 110/125V,
220/250V, Custom
Sets the nominal battery voltage for all opto inputs by selecting one of the five standard
ratings in the Global Nominal V settings. If Custom is selected then each opto input can
individually be set to a nominal voltage value.
Settings
P746/EN ST/J43
MiCOM P40 Agile P746
(ST) 4-27
Menu Text
Opto Input 1-40
Default Setting
Setting Range
Min.
Max.
Step Size
24/27V, 30/34V, 48/54V,
110/125V, 220/250V, Custom
48/54V
Each opto input can individually be set to a nominal voltage value if custom is selected for
the global setting. The number of inputs may be up to 32, depending on the IED and I/O
configuration.
Opto Filter Ctrl
11111111111111111111111111111111
This menu is used to control the relay’s opto-isolated inputs L1 to L32. A ‘1’ indicates an
energized and operating relay, a ‘0’ indicates a de-energized
Opto Filter Ctrl2
11111111
Controls the next relay’s opto-isolated inputs (L33 to L40).
Characteristics
Standard 60%-80%
50% - 70 % / Standard 60%-80%
Controls the changement of state of opto isolated inputs, according to the nominal voltage
value.
1.3.9
Control Input Configuration
The control inputs function as software switches that can be set or reset either locally or
remotely. These inputs can be used to trigger any function that they are connected to as part
of the PSL.
Menu Text
Default Setting
Setting Range
Step Size
CTRL I/P CONFIG.
Hotkey Enabled
11111111111111111111111111111111
Setting to allow the control inputs to be individually assigned to the “Hotkey” menu by
setting ‘1’ in the appropriate bit in the “Hotkey Enabled” cell. The hotkey menu allows the
control inputs to be set, reset or pulsed without the need to enter the “CONTROL INPUTS”
column
Control Input 1
Latched
Latched, Pulsed
Configures the control inputs as either ‘latched’ or ‘pulsed’. A latched control input will
remain in the set state until a reset command is given, either by the menu or the serial
communications. A pulsed control input, however, will remain energized for 10ms after the
set command is given and will then reset automatically (i.e. no reset command required) .
Ctrl command 1
Set/Reset
Set/Reset, ON/OFF, Enabled/Disabled,
IN/OUT
Allows the SET / RESET text, displayed in the hotkey menu, to be changed to something
more suitable for the application of an individual control input, such as “ON / OFF”, “IN /
OUT” etc.
Control Input 1 to 32
Latched
Latched, Pulsed
Configures the control inputs as either ‘No Operation’, ‘Set’ or ‘reset’.
Ctrl command 2 to 32
Set/Reset
Set/Reset, ON/OFF, Enabled/Disabled,
IN/OUT
Allows the SET / RESET text, displayed in the hotkey menu, to be changed to something
more suitable for the application of an individual control input, such as “ON / OFF”, “IN /
OUT” etc.
ST
P746/EN ST/J43
Settings
(ST) 4-28
1.3.10
MiCOM P40 Agile P746
Function Keys
Menu Text
Setting Range
Default Setting
Min.
Max.
Step Size
FUNCTION KEYS
Fn. Key Status
0000000000
Displays the status of each function key.
Fn. Key 1 Status
Unlocked
Disabled, Locked, Unlock
Setting to activate function key. The ‘Lock’ setting allows a function key output that is set to
toggle mode to be locked in its current active state.
Fn. Key 1 Mode
Normal
Toggled, Normal
Sets the function key in toggle or normal mode. In ‘Toggle’ mode, a single key press will
set/latch the function key output as ‘high’ or ‘low’ in programmable scheme logic. This
feature can be used to enable/disable relay functions. In the ‘Normal’ mode the function
key output will remain ‘high’ as long as key is pressed.
ST
Fn. Key 1 Label
Function Key 1
Allows the text of the function key to be changed to something more suitable for the
application.
Fn. Key 2 to 10
Status
Unlocked
Disabled, Locked, Unlock
Setting to activate function key. The ‘Lock’ setting allows a function key output that is set to
toggle mode to be locked in its current active position.
Fn. Key 2 to 10 Mode
Toggled
Toggled, Normal
Sets the function key in toggle or normal mode. In ‘Toggle’ mode, a single key press will
set/latch the function key output as ‘high’ or ‘low’ in programmable scheme logic. This
feature can be used to enable/disable relay functions. In the ‘Normal’ mode the function
key output will remain ‘high’ as long as key is pressed.
Fn. Key 2 to 10 Label
Function Key 2 to 10
Allows the text of the function key to be changed to something more suitable for the
application.
1.3.11
“IED Configurator” column
The contents of the IED CONFIGURATOR column (for IEC 61850 configuration) are mostly
data cells, displayed for information but not editable. To edit the configuration use the IED
(Intelligent Electronic Device) configurator tool within MiCOM S1 Agile.
Menu Text
Default Setting
Setting Range
Min.
Max.
Step Size
IED CONFIGURATOR
Switch Conf.Bank
No Action
No Action, Switch Banks
Setting which allows the user to switch between the current configuration, held in the
Active Memory Bank (and partly displayed below), to the configuration sent to and held in
the Inactive Memory Bank.
Restore MCL
No action
No action / Restore MCL
Used to restore data from MCL binary file. MCL (MiCOM Configuration Language) files are
specific, containing a single devices IEC61850 configuration information, and used for
transferring data to/from the MiCOM IED.
Active Conf.Name
Data
The name of the configuration in the Active Memory Bank, usually taken from the SCL file.
Settings
P746/EN ST/J43
MiCOM P40 Agile P746
Menu Text
Active Conf.Rev
(ST) 4-29
Default Setting
Setting Range
Min.
Step Size
Max.
Data
Configuration Revision number of the Active Memory Bank, used for version management.
Inact.Conf.Name
Data
The name of the configuration in the Inactive Memory Bank, usually taken from the SCL
file.
Inact.Conf.Rev
Data
Configuration Revision number of the Inactive Memory Bank, used for version
management.
IP PARAMETERS
IP Address
Data
ST
Displays the unique network IP address that identifies the relay.
Subnet Address
Data
Displays the sub-network that the relay is connected to.
Gateway
Data
Displays the IP address of the gateway (proxy) that the relay is connected to.
SNTP PARAMETERS
SNTP Server 1
Data
Displays the IP address of the primary SNTP server.
SNTP Server 2
Data
Displays the IP address of the secondary SNTP server.
IEC61850 SCL
IED Name
Data
8 character IED name, which is the unique name on the IEC 61850 network for the IED,
usually taken from the SCL (Substation Configuration Language for XML) file.
IEC 61850 GOOSE
GoEna
00000000
00000000
11111111
1
GoEna (GOose ENAble) is a setting to enable GOOSE (Generic Object Orientated
Substation Event, for high-speed inter-device messaging) publisher settings. This setting
enables (“1”) or disables (“0”) GOOSE control blocks from 08 (1st digit) to 01 (last digit).
Test Mode
00000000
00000000
11111111
1
The Test Mode cell allows the test pattern to be sent in the GOOSE message, for example
for testing or commissioning.
The setting enables (“1”) or disables (“0”) test mode for GOOSE control block from 08 (1st
digit) to 01 (last digit).
Once testing is complete the cell must be set back to ‘Disabled’ to restore the GOOSE
scheme back to normal service.
Ignore Test Flag
No
No, Yes
When set to ‘Yes’, the test flag in the subscribed GOOSE message is ignored, and the
data treated as normal.
P746/EN ST/J43
Settings
(ST) 4-30
1.3.12
MiCOM P40 Agile P746
“SECURITY CONFIG” column
The SECURITY CONFIG column contains the main configuration settings for Security
functions. This column is used to set the password attempts number and duration. When
these limits expire, access to the interface is blocked until timer has expired. This setting
enables or disables port access.
Menu Text
Setting Range
Default Setting
Min.
Step Size
Max.
SECURITY CONFIG
ACCESS ONLY FOR AUTHORISED USERS
User Banner
0
3
1
0
3
1
NERC compliant user IED description.
ST
Attempts Limit
2
Adjust the number of attempts to enter a valid password. When the maximum number of
attemps has been reached, access is blocked.
Attempts Timer
2
1
3
1
30
1
Adjust the time limit (minutes) to enter the correct password.
Blocking Timer
5
1
Adjust the blocking timer (minutes) after a password blocking. Once the password is
blocked, this blocking timer is initiated. Only after the blocking timer has expired will
access to the interface be unblocked, whereupon the attempts counter is reset to zero.
Front Port
Enabled
Enabled or Disabled
Enable or disable the front port access. A level 3 password is needed to perform this
action. To prevent accidental disabling of a port, a warning message “FRONT PORT TO
BE DISABLED, CONFIRM” is required to be disabled.
Rear Port 1
Enabled
Enabled or Disabled
Enable or disable the rear port 1 access. A level 3 password is needed to perform this
action. To prevent accidental disabling of a port, a warning message “REAR PORT 1 TO
BE DISABLED, CONFIRM” is required to be disabled.
Rear Port 2
Enabled
Enabled or Disabled
When fitted, enable or disable the rear port 2 access. A level 3 password is needed to
perform this action. To prevent accidental disabling of a port, a warning message “REAR
PORT 2 TO BE DISABLED, CONFIRM” is required to be disabled.
Ethernet
Enabled
Enabled or Disabled
When fitted, enable or disable the Ethernet port access. A level 3 password is needed to
perform this action. To prevent accidental disabling of a port, a warning message
“ETHERNET TO BE DISABLED, CONFIRM” is required to be disabled.
Caution: disabling the Ethernet port will disable all Ethernet based communications
Courier Tunnel
Enabled
Enabled or Disabled
Enable or disable the Courier tunneling logical port access. A level 3 password is needed
to perform this action.
Note: if this protocol is enabled or disabled, the Ethernet card will reboot.
IEC61850
Enabled
Enabled or Disabled
Enable or disable the IEC61850 logical port access. A level 3 password is needed to
perform this action.
Note: if this protocol is enabled or disabled, the Ethernet card will reboot.
Attempts Remain
Data
Indicates the number of attempts to enter a password.
Settings
P746/EN ST/J43
MiCOM P40 Agile P746
(ST) 4-31
Menu Text
Blk Time Remain
Setting Range
Default Setting
Min.
Step Size
Max.
Data
Indicates the blocking time remain (in minute)
Password Fallback
Level
0
1
3
3
The ‘fallback level’ is the password level adopted by the relay after an inactivity timeout, or
after the user logs out. This will be either the level of the highest level password that is
blank, or level 0 if no passwords are blank
Security Code
Data
Indicates the security code (user interface only). The security code is a 16-character string
of upper case characters. It is a read-only parameter. The IED generates its own security
code randomly.
This Security Code should be noted for password recovery.
1.3.13
Control Input Labels
Menu Text
Default Setting
Setting Range
Step Size
CTRL I/P LABELS
Control Input 1
Control Input 1
16 Character Text
Setting to change the text associated with each individual control input. This text will be
displayed when a control input is accessed by the hotkey menu, or it can be displayed in
the programmable scheme logic.
Control Input 2 to 32
Control Input
2 to 32
16 Character Text
Setting to change the text associated with each individual control input. This text will be
displayed when a control input is accessed by the hotkey menu, or it can be displayed in
the programmable scheme logic.
1.4
Disturbance Recorder Settings
The disturbance recorder settings include the record duration and trigger position, selection
of analog and digital signals to record, and the signal sources that trigger the recording.
Menu Text
Default Setting
Setting Range
Min.
Max.
Step Size
DISTURB. RECORDER
Duration
600 s
100.0 ms
10.5 s
10.00 ms
0.0%
100.0%
0.10 %
This sets the overall recording time.
Trigger Position
33.3%
This sets the trigger point as a percentage of the duration. For example, the default
settings show that the overall recording time is set to 1.5 s with the trigger point being at
33.3% of this, giving 0.5 s pre-fault and 1.0 s post fault recording times.
Trigger Mode
Single
Single / Extended
When set to single mode, if a further trigger occurs whilst a recording is taking place, the
recorder will ignore the trigger.
“ANALOG CHANNEL” submenus
Analog. Channel 1
VAN
Any analog channel
The Phase A calculated voltage is assigned to this channel.
ST
P746/EN ST/J43
Settings
(ST) 4-32
MiCOM P40 Agile P746
Menu Text
Analog. Channel 2
Default Setting
VBN
Setting Range
Min.
Max.
As above
The Phase B calculated voltage is assigned to this channel.
Analog. Channel 3
VCN
As above
The Phase C calculated voltage is assigned to this channel.
Analog. Channel 4
IA-T1/Ix-T1
As above
The terminal 1 phase A calculated current is assigned to this channel.
Analog. Channel 5
IB-T1/Ix-T1
As above
The Terminal 1 Phase B calculated current is assigned to this channel.
Analog. Channel 6
ST
IC-T1/Ix-T2
As above
The Terminal 1 Phase C calculated current is assigned to this channel.
Analog. Channel 7
IA-T2 /Ix-T3
As above
The Terminal 2 Phase A calculated current is assigned to this channel.
Analog. Channel 8
IB-T2/Ix-T4
As above
The Terminal 2 Phase B calculated current is assigned to this channel..
Analog. Channel 9
IC-T2/Ix-T5
As above
The Terminal 2 Phase C calculated current is assigned to this channel.
Analog. Channel 10
IA-T3/Ix-T6
As above
The Terminal 3 Phase A calculated current is assigned to this channel.
Analog. Channel 11
IB-T3/Ix-T7
As above
The Terminal 3 Phase B calculated current is assigned to this channel.
Analog. Channel 12
IC-T3/Ix-T8
As above
The Terminal 3 Phase C calculated current is assigned to this channel.
Analog. Channel 13
IA-T4/Ix-T9
As above
The Terminal 4 Phase A calculated current is assigned to this channel.
Analog. Channel 14
IB-T4/Ix-T10
As above
The Terminal 4 Phase B calculated current is assigned to this channel.
Analog. Channel 15
IC-T4/Ix-T11
As above
The Terminal 4 Phase C calculated current is assigned to this channel.
Analog. Channel 16
IA-T5/Ix-T12
As above
The Terminal 5 Phase A calculated current is assigned to this channel.
Analog. Channel 17
IB-T5/Ix-T13
As above
The Terminal 5 Phase B calculated current is assigned to this channel.
Analog. Channel 18
IC-T5/Ix-T14
As above
The Terminal 5 Phase C calculated current is assigned to this channel.
Analog. Channel 19
IA-T6/Ix-T15
As above
The Terminal 6 Phase A calculated current is assigned to this channel.
Analog. Channel 20
IB-T6/Ix-T16
As above
The Terminal 6 Phase B calculated current is assigned to this channel.
Step Size
Settings
P746/EN ST/J43
MiCOM P40 Agile P746
Menu Text
Analog. Channel 21
(ST) 4-33
Default Setting
IC-T6/Ix-T17
Setting Range
Min.
Max.
Step Size
As above
The Terminal 6 Phase C calculated current is assigned to this channel.
“DIGITAL INPUT” and “INPUT TRIGGER” submenus
Digital Input 1
Output R1
Any O/P Contacts or Any Opto Inputs or
Internal Digital Signals
The relay 1 output digital channel is assigned to this channel. The digital channel will
trigger the disturbance recorder when the corresponding assigned fault will occur. In this
case, the digital recorder will trigger when the output R1will change.
Following lines indicate default signals for the 32 channels.
Input 1 Trigger
No Trigger
No Trigger, Trigger L/H, Trigger H/L
This digital channel will not trigger the Disturbance recorder. When “Trigger L/H” is
selected, the channel will trigger the disturbance recorder when changing from ‘0’ (low
Level) to ‘1’ (High level). If “Trigger H/L” is selected, it will trigger when changing from ‘1’
(high level) to ‘0’ (low level).
Following lines give default settings up to channel 32.
Digital Input 2
Output R2
As above
The relay 2 output digital channel is assigned to this channel.
Input 2 Trigger
No Trigger
No Trigger, Trigger L/H, Trigger H/L
Digital Input 3
Output R3
As above
Relay 3 output digital channel.
Input 3 Trigger
No Trigger
No Trigger, Trigger L/H, Trigger H/L
Digital Input 4
Output R4
As above
Relay 4 output digital channel.
Input 4 Trigger
No Trigger
No Trigger, Trigger L/H, Trigger H/L
Digital Input 5
Output R5
As above
Relay 5 output digital channel.
Input 5 Trigger
No Trigger
No Trigger, Trigger L/H, Trigger H/L
Digital Input 6
Output R6
As above
Relay 6 output digital channel.
Input 6 Trigger
No Trigger
No Trigger, Trigger L/H, Trigger H/L
Digital Input 7
Output R7
As above
Relay 7 output digital channel.
Input 7 Trigger
No Trigger
No Trigger, Trigger L/H, Trigger H/L
Digital Input 8
Output R8
As above
Relay 8 output digital channel.
Input 8 Trigger
Digital Input 9
No Trigger
No Trigger, Trigger L/H, Trigger H/L
Any Trip
As above
Trigger L/H
No Trigger, Trigger L/H, Trigger H/L
Ouput R10
As above
Any trip
Input 9 Trigger
Digital Input 10
Relay 10 output digital channel.
ST
P746/EN ST/J43
Settings
(ST) 4-34
MiCOM P40 Agile P746
Menu Text
Input 10 Trigger
Digital Input 11
Default Setting
Setting Range
Min.
Max.
Step Size
Trigger L/H
No Trigger, Trigger L/H, Trigger H/L
Diff Fault Z1
As above
Busbar Differential Fault in Zone 1
Input 11 Trigger
Trigger L/H
No Trigger, Trigger L/H, Trigger H/L
Digital Input 12
Diff Fault Z2
As above
Busbar Differential Fault in Zone 2
Input 12 Trigger
Trigger L/H
No Trigger, Trigger L/H, Trigger H/L
Digital Input 13
Diff Fault CZ
As above
Busbar Differential Fault in Check Zone
ST
Input 13 Trigger
Trigger L/H
No Trigger, Trigger L/H, Trigger H/L
Digital Input 14
Idiff Start Z1
As above
Differential current in main zone 1.
Input 14 Trigger
Trigger L/H
No Trigger, Trigger L/H, Trigger H/L
Digital Input 15
Idiff Start Z2
As above
Differential current in main zone 2.
Input 15 Trigger
Trigger L/H
No Trigger, Trigger L/H, Trigger H/L
Digital Input 16
Idiff CZ Start
As above
Differential current in Check Zone.
Input 16 Trigger
Trigger L/H
No Trigger, Trigger L/H, Trigger H/L
Digital Input 17
PhComp Blk Z1.
As above
Phase comparison Block in zone 1.
Input 17 Trigger
No Trigger
No Trigger, Trigger L/H, Trigger H/L
Digital Input 18
PhComp Blk Z2.
As above
Phase comparison Block in zone 2.
Input 18 Trigger
No Trigger
No Trigger, Trigger L/H, Trigger H/L
Digital Input 19
Unused
As above
Input 19 Trigger
No Trigger
No Trigger, Trigger L/H, Trigger H/L
Digital Input 20
Idiff Trip Z1
As above
Unused.
Differential busbar trip or gate of Z1 Diff phase in zone 1
Input 20 Trigger
No Trigger
No Trigger, Trigger L/H, Trigger H/L
Digital Input 21
Idiff Trip Z2
As above
Differential busbar trip or gate of Z1 Diff phase in zone 2
Input 21 Trigger
No Trigger
No Trigger, Trigger L/H, Trigger H/L
Digital Input 22
CCtFail Blk Z1
As above
Input 22 Trigger
No Trigger
No Trigger, Trigger L/H, Trigger H/L
Digital Input 23
CctFail Blk Z2
As above
Circuity Fault in zone 1
Circuity Fault in zone 2.
Settings
P746/EN ST/J43
MiCOM P40 Agile P746
Menu Text
(ST) 4-35
Default Setting
Setting Range
Min.
Max.
Step Size
Input 23 Trigger
No Trigger
No Trigger, Trigger L/H, Trigger H/L
Digital Input 24
CctFail Blk CZ
As above
Circuity Fault in check zone
Input 24 Trigger
No Trigger
No Trigger, Trigger L/H, Trigger H/L
Digital Input 25
Diff Z1 Blked
As above
10.5 s
0.01 s
Zone 1 Busbar Diff in Block Status
Input 25 Trigger
No Trigger
No Trigger, Trigger L/H, Trigger H/L
Digital Input 26
Diff Z2 Blked
As above
100.0%
0.1%
Zone 2 Busbar Diff in Block Status
Input 26 Trigger
No Trigger
No Trigger, Trigger L/H, Trigger H/L
Digital Input 27
Diff CZ Blked
As above
Check Zone Busbar Diff in Block Status
Input 27 Trigger
No Trigger
No Trigger, Trigger L/H, Trigger H/L
Digital Input 28
Fault A
As above
Input 28 Trigger
No Trigger
No Trigger, Trigger L/H, Trigger H/L
Digital Input 29
Fault B
As above
Input 29 Trigger
No Trigger
No Trigger, Trigger L/H, Trigger H/L
Digital Input 30
Fault C
As above
Input 30 Trigger
No Trigger
No Trigger, Trigger L/H, Trigger H/L
Digital Input 31
Fault N
As above
Input 31 Trigger
No Trigger
No Trigger, Trigger L/H, Trigger H/L
Digital Input 32
Function key 10
As above
Phase A fault.
Phase B fault
Phase C fault
Earth fault
Function Key 10 activated (in ‘Normal’ mode it is high on keypress and in ‘Toggle’ mode
remains high/low on single keypress)
Input 32 Trigger
Trigger L/H
No Trigger, Trigger L/H, Trigger H/L
ST
P746/EN ST/J43
(ST) 4-36
ST
Settings
MiCOM P40 Agile P746
Operation
P746/EN OP/J43
MiCOM P40 Agile P746
(OP) 5-1
OP
OPERATION
Hardware Suffix:
M
Software Version:
91
P746/EN OP/J43
(OP) 5-2
OP
Operation
MiCOM P40 Agile P746
Operation
P746/EN OP/J43
MiCOM P40 Agile P746
(OP) 5-3
CONTENTS
1
OPERATION OF INDIVIDUAL PROTECTION FUNCTIONS
5
1.1
Busbar Biased Current Differential Protection
5
1.1.1
Operating Principle
5
1.1.2
Application of Kirchoffs Law
5
1.1.3
Bias Characteristic and Differential Current
6
1.1.4
Scheme Supervision by "Check Zone” Element
6
1.2
Busbar Protection
6
1.2.1
Bias Characteristic and Differential Current Setting
6
1.2.2
Scheme Supervision by Phase Comparison Element
7
1.2.3
Scheme Supervision by "Check Zone” Element
8
1.2.4
Tripping Criteria
9
1.2.5
Current Circuit Supervision
9
1.3
Additional Protection
9
1.3.1
Dead Zone Protection (DZ)
9
1.3.2
Circuit Breaker Fail (CBF)
9
1.3.3
Circuit Breaker Fail Reset Criteria
10
1.3.3.1
Overcurrent Criterion
10
1.3.3.2
Undercurrent Reset Criterion
10
1.3.3.3
Logic Reset Criterion
12
1.3.3.4
Logic AND Current Reset Criterion
12
1.3.3.5
Processing a Circuit Breaker Failure Condition
12
1.3.3.6
Internally Initiated CBF
14
1.3.3.7
Externally Initiated 50BF
15
1.3.3.8
Local Re-trip After Time tBf3
15
1.3.3.9
CB Fail Alarm
16
1.3.3.10 Separate external 50BF protection to the busbar protection
16
1.4
Three Phase Overcurrent Protection
16
1.4.1
Inverse Time (IDMT) Characteristic
16
1.4.2
Reset Characteristics
17
1.5
Earth Fault Protection
17
1.5.1
EF Time Delay Characteristics
17
1.5.2
External Fault Detection by High-Set Overcurrent or Earth Fault Element
17
2
ISOLATOR AND CIRCUIT BREAKER FUNCTION
18
2.1
Isolator State Monitoring Features
18
3
OPERATION OF NON PROTECTION FUNCTIONS
19
3.1
Programmable Scheme Logic
19
3.1.1
Level settings
19
3.1.2
Accuracy
19
3.2
IRIG-B Signal Only
19
OP
P746/EN OP/J43
(OP) 5-4
Operation
MiCOM P40 Agile P746
3.3
Trip LED Logic
19
3.4
Control Inputs
19
FIGURES
OP
Figure 1: Differential Busbar Protection Principle
5
Figure 2: P746 scheme characteristic
7
Figure 3: Differential and phase comparator algorithm interaction
8
Figure 4: CB element logic
11
Figure 5: CB Fail logic diagram
13
Figure 6: CB Fail element logic – internally initiated
14
Figure 7: CB Fail element logic – externally initiated
15
Operation
P746/EN OP/J43
MiCOM P40 Agile P746
1
(OP) 5-5
OPERATION OF INDIVIDUAL PROTECTION FUNCTIONS
The following sections detail the individual protection functions.
However, not all the protection functions listed below are applicable to every relay.
1.1
Busbar Biased Current Differential Protection
The primary protection element of the P746 scheme is phase segregated biased current
differential protection. The technique used is purely numerical and uses nodal analysis
throughout the scheme, on a per zone and per scheme basis.
1.1.1
Operating Principle
The basic operating principle of the differential protection is based on the application of
Kirchhoff’s law. This compares the amount of current entering and leaving the protected
zone and the check zone. Under normal operation, the amount of current flowing into the
area and the check zone concerned is equal in to the amount of the current flowing out of the
area. Therefore, the currents cancel out. In contrast, when a fault occurs the differential
current that arises is equal to the derived fault current.
Figure 1: Differential Busbar Protection Principle
1.1.2
Application of Kirchoffs Law
Several methods of summation can be used for a differential protection scheme:
• Vector sum
• Instantaneous sum
The algorithms applied in the MiCOM P746 use the vector sum method (on Fourier).
The instantaneous sum method has the advantage of cancelling the harmonic and DC
components of external origin in the calculation and in particular under transformer inrush
conditions.
The bias current is the scalar sum of the currents in the protected zone and for the check
zone. Each of these calculations is done on a per phase basis for each node and then
summated.
OP
P746/EN OP/J43
Operation
(OP) 5-6
1.1.3
MiCOM P40 Agile P746
Bias Characteristic and Differential Current
The operation of the busbar differential protection is based on the application of an algorithm
having a biased characteristic, (Figure 2), in which a comparison is made between the
differential current and a bias or restraining current. A fault is detected if this differential
current exceeds the set slope of the bias characteristic. This characteristic is intended to
guarantee the stability of protection during external faults where the scheme has current
transformers with differing characteristics, likely to provide differing performance.
The algorithm operands are as follows:
Differential Current:
idiff(t) = Σ i 
Bias or Restraining current:
ibias(t) = Σ  i 
OP
Slope of the bias characteristic (zone x):
kx
Tripping permitted by bias element for:
idiffx(t) > kx × ibias(t)
The main differential current element of the busbar protection only operates if the differential
current reaches a threshold IDx>2. This setting is adjusted above the normal full load current.
1.1.4
Scheme Supervision by "Check Zone” Element
The "Check Zone" element is based on the principle that in the event of a fault on one of the
substation busbars, the differential current measured in the faulty zone will be equal to that
measured in the entire scheme.
A frequent cause of maloperation of differential busbar protection schemes is an error in the
position of an isolator or CB in the substation to that replicated in the scheme (auxiliary
contacts discrepancy). This produces a differential current in one or more current nodes.
However, if an element monitors only the currents "entering" and "leaving" the substation, it
remains negligible in the absence of a fault, and the error lies with the zone’s assumption of
the plant position at this particular point in time.
1.2
Busbar Protection
1.2.1
Bias Characteristic and Differential Current Setting
Figure 2 shows the characteristics of the P746 scheme phase differential element.
Operation
P746/EN OP/J43
MiCOM P40 Agile P746
(OP) 5-7
OP
Figure 2: P746 scheme characteristic
The phase characteristic is determined from the following protection settings:
• Area above the ID>2 threshold zone differential current threshold setting and the set
slope of the bias characteristic (k2 × Ibias) (k2 is the percentage bias setting (“slope”)
for the zone)
1.2.2
Scheme Supervision by Phase Comparison Element
When an external fault condition causes CT saturation, a differential current is apparent. The
measured differential current may be determined as an internal fault and initiate an
unwanted trip of the busbar.
To avoid a risk of tripping under these circumstances, most of the busbar protection use a
phase comparison algorithm to detect if the fault is internal or external.
The characteristics of this algorithm are:
• It works without voltage information
• A phase by phase snapshot of the 3 phase current angles is taken for each sample
• Only the currents above a certain magnitude are taken into account
 This settable threshold is a percentage of the ID>2 Current setting
• The release criterion is that, phase by phase, all angles are within any 90° area*
• If only one current is taken into account, it’s an internal fault
* Because of the CT requirements, the calculated phase of a saturated current can only vary
from -90° to +90°.
Example:
1 bar, 1 incomer (CT1 = 2000/1) and 2 outfeeds (CT2 = 1000/1 and CT3 = 500/1) and ID>2
Setting = 2000
If the setting PU comp. PU ratio is 50%, the phase comparison algorithm will use:
• ID>2 Setting (2000) X PU comp. setting (2000x 0.5 = 1000A)
P746/EN OP/J43
Operation
(OP) 5-8
MiCOM P40 Agile P746
MiCOM S1
I1
ID>1 settings in A (CT Primary
Value)
ID>2 setting in A (CT primary value)
Ph Comp PU Ratio in %
I2
I18
Ix = Ix * ( CTx primary Setting / Iref)
ID>1 = ID>1 / Iref
Ix
ID>2 = ID>2 / Iref
Ph Comp PU Ratio
ID>2 = ID>2 / Iref
Differential Busbar Algorithm
Is1 Phase Comparator threshold in A
Is1 = Ph Comp PU Ratio * ID>2
OP
Computation of
Idiffx = F (Ix)
Ibiasx = F (Ix)
Ifault = F (ID>2, Idiffx, Ibiasx)
Ix
Is1
MEASUREMENTS
Ixprimary = Ix * Iref
Ixsecondary = Ix
Phase Comparator Algorithm
Idiffxprimary = Idiffx * Iref
Idiffxsecondary = Idiffx
Computation of
Idiff phase angle = F(Is1, Ix)
Ibiasxprimary = Ibias * Iref
Ibiasxsecondary = Ibiasx
DR
Ixprimary = Ix * Iref
Idiffxprimary = Idiffx * Iref
Ibiasxprimary = Ibiasx * Iref
Fixed Tripping
Logic
V04023
Figure 3: Differential and phase comparator algorithm interaction
1.2.3
Scheme Supervision by "Check Zone” Element
For security, the busbar protection will only trip a particular busbar zone if that zone
differential element AND the check zone element are in agreement to trip.
The principal advantage of this element is total insensitivity to topological discrepancies.
Under such circumstances the "check zone" element will see two currents with equal
amplitude but of opposite sign in adjacent zones.
The Check Zone characteristic is determined from the following protection settings:
• Area above the IDCZ>2 threshold check zone differential current threshold setting and
the set slope of the bias characteristic (kCZ × Ibias) (kCZ is the percentage bias setting
(“slope”) for the Check Zone)
Note:
The origin of the bias characteristic slope is 0.
The check zone is the sum of all the current nodes entering and leaving the substation
(feeders).
Scheme differential current = sum of all differential current feeder nodes:
Operation
P746/EN OP/J43
MiCOM P40 Agile P746
(OP) 5-9
idiff(t) CZ = Σ idiff
The Check Zone will operate as the Zone element.
1.2.4
Tripping Criteria
A trip signal for a zone will be issued:
1. If the fault is detected in the zone AND
2. Confirmed by the check zone AND
3. Confirmed by the phase comparison.
For a fault to be detected, 4 trip criterions and 4 (optional) must be met; these criterions are:
For the Zone:
1. If 2 consecutive calculations are above (ID>2) and k × Ibias
2. Confirmation of the phase comparison algorithm
3. Optional Voltage criteria (U< or V1< or V2> or V0>)
For the Check Zone:
• If 2 consecutive calculations are above (IDCZ>2) and kCZ × Ibias
1.2.5
Current Circuit Supervision
During normal operation the differential current in the scheme should be zero or negligible.
Any anomaly is detected through a given threshold ID>1.
A biased differential element is used to supervise the current circuit. A differential current will
result if the secondary circuit of a CT becomes open circuited, short circuited; the amplitude
of this current is proportional to the load current flowing in the circuit monitored by the faulty
current circuit.
The setting is chosen to be as low as possible (minimum suggested setting is 2% of the
biggest CT primary winding) but it also allows for standing differential current. For example,
due to CT mismatch and varying magnetising current losses. A typical application range is 5
to 20%.
The element is typically time delayed for 5 seconds (set greater than the maximum
clearance time of an external fault). Instead the time delay allows the relevant protection
element (which should be substantially faster) to clear the fault instead i.e. ID>2 in the case
of an internal phase fault.
1.3
Additional Protection
1.3.1
Dead Zone Protection (DZ)
On a feeder if the breaker is open, a dead zone (or end zone) exists between the open
element and the CT. The P746 can protect this zone with the Dead Zone protection. This is a
simple time delayed overcurrent and earth fault element which is only active when a dead
zone is identified in the local topology.
1.3.2
Circuit Breaker Fail (CBF)
The detailed logic of the circuit breaker failure element follows.
The P746 hardware corresponds to up to 6 circuit breaker and can accommodate 1 or 2 trip
coils per breaker. This is dependent on the relay number, defined by the model number and
PSL (CB trip signal connection to the relay output):
• 1 main trip coil
• 1 back-up trip coil
Furthermore, these can be either 3 single-phase trip coils or 1 three-phase trip coil. These
can be combined for example, 3 single-phase trip coils on the main system and 1 threephase trip coil for the back-up system.
OP
P746/EN OP/J43
Operation
(OP) 5-10
MiCOM P40 Agile P746
1.3.3
Circuit Breaker Fail Reset Criteria
1.3.3.1
Overcurrent Criterion
One of the most common causes of busbar mal-tripping is an error introduced in the back
tripping of adjacent sections. To prevent this you can condition the operation of 50BF
protection only when there is presence of a significant current i.e. a short-circuit on the
concerned feeder. This confirmation is provided by the I> threshold, which is set by default
at 1.2 times the nominal rated current of the CT.
1.3.3.2
Undercurrent Reset Criterion
The criterion normally used for the detection of a circuit breaker pole opening is the
disappearance of the current i.e. undercurrent element. This function is generally preferred
above other elements due to its very fast response time. In P746, this method of detection is
used and has the threshold I<.
See figure 4, part
for phase A.
OP
Note:
The same algorithm is used for the other phases.
These undercurrent elements have an I< threshold, which are used to supervise that every
circuit breaker opens correctly, when asked to do so. By use of the I< threshold, it is possible
to ensure that all load and fault current has been ruptured, ensuring that no arcing remains
across the circuit breaker primary contacts. Optionally, the user can decide to include 52a
supervision in the breaker fail logic (see chapters 1.3.3.3 and 1.3.3.4).
Note:
52a is the setting name, it means CB closed. The CB closed position is
created in the PSL either using 52b reversed or a combination of (52a and
52b).
The first function is to compare the current sample to the I< threshold and check for the
following sequence:
• positive value of the current
• no current (below the threshold)
• negative value of the current
• no current (below the threshold)
• positive value of the current
• …
The output signal is pl(t), it changes between 0 and 1.
Internal overcurrent signals are available per phase and neutral to confirm that the CB failure
algorithm has started to count down.
Internal undercurrent signals are available per phase to confirm that each pole has opened.
To maintain the current criterion active while the signal crosses zero, there is a drop-off timer
associated with the pl(t) signal. The latching duration is variable in order to take all cases into
account:
• Just after the initiation of the CB fail signal, the waveform can include a DC
component, and the time between two successive zero crossings can reach one
period. Therefore, the retrip time should be set long enough for the DC component to
have disappeared so that the time between two successive zero crossings is close to
one half-period. It is important to detect the opening of the circuit breaker quickly
because the end of the back trip timer is near. The drop-off duration is therefore equal
to one half period + 3 ms (13 ms at 50 Hz, 11.3 ms at 60 Hz).
Operation
P746/EN OP/J43
MiCOM P40 Agile P746
(OP) 5-11
tps
tss
0
0
T
2T
3T
4T
5T
6T
7T
OP
pl (t)
Tp = Trip pole signal
Tn1 = Switching order
tBF4 - 30ms
(T/2) < t max < T
Tn1=(T/2) + 3ms
P0712ENa
Figure 4: CB element logic
Principle of the undercurrent function.
Instantaneous current measurements are taken for both the positive and negative half
cycles, ensuring immunity to DC offset waveforms, and CT current ring-down.
The two horizontal dotted lines are instantaneous thresholds, fixed in proportion to the user's
I< setting. The instantaneous threshold is at 70 percent of the I< fundamental RMS setting.
As any current rises above the dotted line instantaneous threshold, this rising measurement
triggers a pulse timer to declare that current is flowing. The duration of the pulse is one full
cycle plus 3 ms (T+3 ms). It does not matter whether the magnitude of the current stays
above the dotted line further, as the detector is effectively edge-triggered. Current flow has
been declared based on this half cycle, and not until the current falls below the detector
setting is the edge-trigger ready to declare an output again. Whilst current is flowing, on the
rise of current in each half-cycle the pulse timer is retriggered. This sequential retriggering
ensures that current is detected.
The detection of breaker opening is made on one of two scenarios:
4. The current falls below the instantaneous detection threshold and does not rise again
before the pulse timer expires; or
5. A CT current ringdown does not change sign, it remains in one polarity sense up until
the timer expires.
Note:
The pulse timer length is variable and adapts according to the anticipated
proportion of DC current offset, which may be present in the measured
waveform. The pulse timer initially is fixed at one cycle plus 3 ms, as on fault
inception the DC offset could be appreciable. Near the end of the breaker fail
time, the pulse length is shortened to half a power cycle plus 3 ms (T/2 + 3
ms). The presumption is that the DC offset in real fault current has decayed,
and that the shorter time is all that is required. The pulse length is commuted
30ms before expiry of the tBF2 timer (for internally-initiated CBF) and 30 ms
before expiry of the tBF4 timer (for externally-initiated CBF). The reduced
pulse length means faster resetting of the current detector.
P746/EN OP/J43
Operation
(OP) 5-12
1.3.3.3
MiCOM P40 Agile P746
Logic Reset Criterion
This is where circuits carry a very low level of load, or operate unloaded from time to time.
When 52a contact (CB closed) supervision is set, the relay looks only for the opening of the
breaker to stop the breaker fail timers.
This criterion is based on checking the state of the circuit breaker auxiliary contacts. i.e. to
see if the 52b reverse or a combination of (52a and 52b) contact is open for open circuit
breaker conditions. In the P746 protection system, this detection method is used with the
'52a' threshold.
1.3.3.4
Logic AND Current Reset Criterion
This is where circuits carry a very low level of load, or operate unloaded from time to time.
When 52a contact (CB closed) supervision is set, the relay looks for I< undercurrent and the
opening of the breaker to stop the breaker fail timers.
This criterion relies on verifying the disappearance of the current AND of the state of the CB
auxiliary contacts. In the P746 protection system, this detection method is used with the 'I<
AND 52a' (setting) threshold.
OP
1.3.3.5
Processing a Circuit Breaker Failure Condition
Due to the nature of the busbar protection, the substation topology can manage the system
under circuit breaker failure conditions (50BF).
There are several options for circuit breaker failure protection installations. These depend on
the substation construction and wiring:
• Internally initiated CBF i.e. Initiation from the differential element,
• Externally initiated, for example by the feeder protection, but using the busbar
protection’s integral 50BF protection to execute tripping procedure
• Separate 50BF protection to the busbar protection (such as a MiCOM P821)
The breaker failure logic uses fast acting undercurrent elements to provide the required
current check. These elements reset within 15ms, thereby allowing the use of the P746 relay
at all voltage levels.
Since the Overcurrent element may also be used in blocking schemes to provide back-up
protection, it is possible to reset the Overcurrent start signals after the breaker fail time delay
has elapsed. This ensures that the upstream back-up protection can be maintained by
removal of the blocking signal. This would also ensure that the possible risk of re-trip on reclosure of the circuit breaker is minimised.
CB Trip 3 ph:
• Triphase Circuit Breaker Trip (Init 50BF TBF1 / TBF2), Logical OR of 87BB, 50BF,
Manual Trip Zone X
Note:
The CB fail alarm is raised as soon as tBF1 or tBF2 or tBF3 or tBF4 has
been reached.
Operation
P746/EN OP/J43
MiCOM P40 Agile P746
(OP) 5-13
OP
Figure 5: CB Fail logic diagram
P746/EN OP/J43
(OP) 5-14
1.3.3.6
Operation
MiCOM P40 Agile P746
Internally Initiated CBF
Tripping from the Differential Element 87BB
When a tripping order is generated by the busbar protection (87BB or 50BF) but not
executed due to a circuit breaker failure condition, the following circuit breakers are required
to be tripped instead:
All the circuit breakers in the adjacent busbar zone if the faulty circuit breaker is that of a bus
coupler or bus section.
Optional: The remote end circuit breaker if the faulty circuit breaker is that of a feeder (line or
transformer). This intertripping is done via PSL and may not be required on feeders, which
may be serviced automatically via the distance or other line protection.
The tripping order from the busbar protection is referenced as TpABC, it is always three-phase
and initiates timers tBF1 and tBF2. The first timer is associated with the local re-trip function
while the second timer is associated with the conveyance of the signal for tripping of the
adjacent zone in the cases of bus coupler/bus section circuit breaker failure.
OP
Description of the logic
Figure 6: CB Fail element logic – internally initiated
1.3.3.6.1
Initial trip
A trip signal is issued and then confirmed. If the (optional) threshold for the local Overcurrent
protection setting for busbar protection (I>BB) is exceeded, then the local circuit breaker trip
coil is energised and subsequently the local circuit breaker is tripped.
1.3.3.6.2
Re-Trip after Time tBF1
The dead pole detection threshold (I<) and external protection initiation (I>) trigger the first
breaker failure timer (tBF1). This signal is then passed through an AND gate with the signal
from the local Overcurrent protection for busbar protection (I>BB). If a circuit breaker failure
condition has evolved it will still be present and a re-trip command is issued. Re-trip output
contacts should be assigned using the PSL editor, including in default PSL settings.
1.3.3.6.3
Back-Trip after Time tBF2
A signal from the first circuit breaker timer triggers the second breaker failure timer (tBF2).
This is then passed through an AND gate with the signal from the local overcurrent
protection for busbar protection (I>BB). If a circuit breaker failure condition has persisted it
will still be present and a general bus-zone back-trip signal is issued.
In summary tBF1 is used for re-trip and tBF2 for general bus zone back-trip
Operation
P746/EN OP/J43
MiCOM P40 Agile P746
(OP) 5-15
Because the busbar protection scheme uses the substation topology, during circuit breaker
failure conditions, circuit breaker operations are executed according to on the current state of
the system. It is therefore of paramount importance that should an internally initiated scheme
be implemented, the circuit breaker tripping order, must be thoroughly defined within the
scheme topology to guarantee correct scheme operation.
1.3.3.7
Externally Initiated 50BF
OP
Figure 7: CB Fail element logic – externally initiated
Taking into account the relationship between the busbar protection and the circuit breaker
failure protection certain operators prefer an integrated solution where the breaker failure
may be initiated by external protection but executed in the busbar scheme. Tripping is then
worked out in the section or zone.
On an overhead line for example the external commands may be generated by the distance
protection (21). These commands and tripping commands are on a 3-phase basis. In the
diagrams these signals are labelled TpA, TpB, TpC (Tripping pole A, B or C).
The logic is similar to that for internally initiated CB fail protection but utilises tBf3 for re-trip
and tBF4 for back-trip functions.
1.3.3.8
Local Re-trip After Time tBf3
This re-trip command can be applied via either the main or back up trip coil. It is possible to
choose between the 3 following modes:
• Local re-trip activated/deactivated via PSL. The relay used for this function can use
the same fixed logic for the busbar protection or other independent relays.
• A re-trip can be applied after a time tBF3. This is typically set at 50ms when a single
phase trip and re-trip is used. This prevents loss of phase selectivity by allowing the
main protection trip to execute via the main CB trip coil before re-trip command is
executed by the back-up CB trip coil.
• Single or three phase re-trip is possible. If the feeder protection executes single-phase
tripping, the three-phase re-trip must be carried out in time tBF3 and this must be
adjusted to have a value higher than the normal operation time of the circuit breaker.
Typical setting under this condition is 150ms.
P746/EN OP/J43
Operation
(OP) 5-16
1.3.3.8.1
MiCOM P40 Agile P746
General Zone Trip After Time tBF4
When both the local trip and re-trip have failed, the countdown continues with a second timer
adjusted to have a value of tBF4 - tBF3. The end of this time thus corresponds to total time
tBF4, beyond which a persistent circuit breaker failure condition is declared.
Information is then relayed for routing, and the associated circuit breakers, in the adjacent
zone(s) for a general three-phase back-trip.
1.3.3.9
CB Fail Alarm
The CB Fail alarm is raised on any timer reached (tBF1 or tBF2 or tBF3 or tBF4)
1.3.3.10 Separate external 50BF protection to the busbar protection
This is the most common solution utilising conventional wiring. The 50BF relay is completely
independent of all others. When a circuit breaker failure condition occurs the external
protection trips all adjacent circuit breakers as defined in the separate scheme (DDB Ext. CB
fail).
OP
In view of the connection between the functions of the busbar protection and the circuit
breaker failure protection some operators prefer one of the more integrated system solutions
previously mentioned.
1.4
Three Phase Overcurrent Protection
1.4.1
Inverse Time (IDMT) Characteristic
IDMT characteristics are selectable from a choice of four IEC/UK and five IEEE/US curves
as shown in the table below.
The IEC/UK IDMT curves conform to the following formula:

 K
t = T ×  α + L
(I Is) −1


The IEEE/US IDMT curves conform to the following formula:

t = TD × 

Where:
K
(I
Is ) −1
α

+ L

t
= Operation time
K
= Constant
Ι
= Measured current
ΙS
= Current threshold setting
α
= Constant
L
= ANSI/IEEE constant (zero for IEC/UK curves)
T
= Time Multiplier Setting for IEC/UK curves
TD
= Time Dial Setting for IEEE/US curves
IDMT Curve description
Standard Inverse
Very Inverse
Extremely Inverse
Long Time Inverse
Moderately Inverse
Very Inverse
Extremely Inverse
Inverse
Standard
IEC
IEC
IEC
UK
IEEE
IEEE
IEEE
US-C08
K Constant
0.14
13.5
80
120
0.0515
19.61
28.2
5.95
α Constant
0.02
1
2
1
0.02
2
2
2
L Constant
0
0
0
0
0.114
0.491
0.1217
0.18
Operation
P746/EN OP/J43
MiCOM P40 Agile P746
(OP) 5-17
IDMT Curve description
Short Time Inverse
1.4.2
Standard
K Constant
US-C02
0.02394
α Constant
L Constant
0.02
0.01694
Reset Characteristics
For all IEC/UK curves, the reset characteristic is definite time only.
For all IEEE/US curves, the reset characteristic can be selected as either inverse curve or
definite time.
The definite time can be set (as defined in IEC) to zero. Range 0 to 100 seconds in steps of
0.01 seconds.
The Inverse Reset characteristics are dependent upon the selected IEEE/US IDMT curve as
shown in the table below.
All inverse reset curves conform to the following formula:

tr
 TD  

tReset = 
×
α
 7   1 − (I Is) 
Where:
tReset
OP
= Reset time
tr
= Constant
Ι
= Measured current
ΙS
= Current threshold setting
α
= Cconstant
TD
= Time Dial Setting (Same setting as that employed by IDMT curve)
IEEE/US IDMT Curve description
Moderately Inverse
Very Inverse
Extremely Inverse
Inverse
Short Time Inverse
1.5
Earth Fault Protection
1.5.1
EF Time Delay Characteristics
Standard
IEEE
IEEE
IEEE
US-C08
US-C02
α Constant
tr Constant
4.85
21.6
29.1
5.95
2.261
2
2
2
2
2
The earth-fault measuring elements for EF and SEF are followed by an independently
selectable time delay. These time delays are identical to those of the Phase Overcurrent
time delay. The reset time delay is the same as the Phase overcurrent reset time.
1.5.2
External Fault Detection by High-Set Overcurrent or Earth Fault Element
An ultra high-speed detection is carried out and can generate a blocking signal from the
moment of the first sample at 0.42 ms.
In this scenario de-saturation may not occur until after the scheme has eliminated the
saturation condition for the external fault.
This function can be activated independently for phase faults (Ι>2) and for Earth Faults
(ΙN>2).
P746/EN OP/J43
(OP) 5-18
Operation
MiCOM P40 Agile P746
2
ISOLATOR AND CIRCUIT BREAKER FUNCTION
2.1
Isolator State Monitoring Features
The following recommended functions, if used shall be set in the PSL:
MiCOM relays can be set to monitor normally open (89A) and normally closed (89B) auxiliary
contacts of the isolators. Under healthy conditions, these contacts will be in opposite states.
Should both sets of contacts be open, this would indicate one of the following conditions:
• Auxiliary contacts / wiring defective
• Isolator is defective
• Isolator is in isolated position
Should both sets of contacts be closed, only one of the following two conditions would apply:
• Auxiliary contacts / wiring defective
OP
• Isolator is defective
A normally open / normally closed output contact has to be assigned to this function via the
programmable scheme logic (PSL). The time delay is set to avoid unwanted operation during
normal switching duties. If any of the above conditions exist, an alarm will be issued after the
time delay set in the PSL.
In the PSL Qx must be used following the two options:
• 89A (normally open) (recommended) or 89B (normally closed) (not recommended)
• Both 89A and 89B (recommended as long as the number of Input is sufficient)
If both 89A and 89B are used then status information will be available and in addition a
discrepancy alarm will be possible. 89A and 89B inputs are assigned to relay opto-isolated
inputs via the PSL.
Operation
P746/EN OP/J43
MiCOM P40 Agile P746
(OP) 5-19
3
OPERATION OF NON PROTECTION FUNCTIONS
3.1
Programmable Scheme Logic
3.1.1
Level settings
Name
Range
Time delay t
3.1.2
0-14400000ms
Accuracy
Output conditioner timer
3.2
Step Size
1ms
Setting ±2% or 50ms whichever is greater
Dwell conditioner timer
Setting ±2% or 50ms whichever is greater
Pulse conditioner timer
Setting ±2% or 50ms whichever is greater
IRIG-B Signal Only
When using IRIG-B to maintain the clock, the device must first be connected to the timing
source equipment (usually a RT430), which should be energized and functioning.
If the auxiliary supply fails, the time and date are maintained by the supercapacitor.
Therefore, when the auxiliary supply is restored, you should not have to set the time and
date again. To test this, remove the IRIG-B signal, and then remove the auxiliary supply.
Leave the device de-energized for approximately 30 seconds. On re-energization, the time
should be correct.
3.3
Trip LED Logic
The trip LED can be reset when the flags for the last fault are displayed or through dedicated
DDBs. The flags are displayed automatically after a trip occurs or they can be selected in the
fault record menu. The reset of trip LED and the fault records is performed by pressing the
clear key once the fault record has been read.
3.4
Control Inputs
The control inputs are software switches, which can be set or reset either locally or remotely.
These inputs can be used to trigger any PSL function to which they are connected. There
are three setting columns associated with the control inputs: CONTROL INPUTS, CTRL. I/P
CONFIG. and CTRL. I/P LABELS. The function of these columns is described below:
Menu Text
CONTROL INPUTS
Ctrl I/P Status
Control Input 1
Control Input 2 to 32
Default Setting
Setting Range
00000000000000000000000000000000
No Operation
No Operation, Set, Reset
No Operation
No Operation, Set, Reset
The Control Input commands can be found in the CONTROL INPUTS column. In the Ctrl.
Ι/P status menu cell there is a 32 bit word which represent the 32 control input commands.
The status of the 32 control inputs can be read from this 32-bit word. The 32 control inputs
can also be set and reset from this cell by setting a 1 to set or 0 to reset a particular control
input. Alternatively, each of the 32 Control Inputs can be set and reset using the individual
menu setting cells ‘Control Input 1, 2, 3’ etc. The Control Inputs are available through the
relay menu as described above and also via the rear communications.
In the programmable scheme logic editor 32 Control Input signals, DDB 800 – 831, which
can be set to a logic 1 or On state, as described above, are available to perform control
functions defined by the user.
Menu Text
CTRL. I/P CONFIG.
Hotkey Enabled
Control Input 1
Ctrl Command 1
Control Input 2 to 32
Default Setting
Setting Range
Step Size
11111111111111111111111111111111
Latched
Latched, Pulsed
SET/RESET
SET/RESET, IN/OUT, ENABLED/DISABLED, ON/OFF
Latched
Latched, Pulsed
OP
P746/EN OP/J43
Operation
(OP) 5-20
MiCOM P40 Agile P746
Menu Text
Ctrl Command 2 to 32
Menu Text
CTRL. I/P LABELS
Control Input 1
Control Input 2 to 32
Default Setting
SET/RESET
Default Setting
Control Input 1
Control Input 2 to 32
Setting Range
Step Size
SET/RESET, IN/OUT, ENABLED/DISABLED, ON/OFF
Setting Range
Step Size
16 character text
16 character text
The CTRL. I/P CONFIG. column has several functions one of which allows the user to
configure the control inputs as either latched or pulsed. A latched control input will remain in
the set state until a reset command is given, either by the menu or the serial
communications. A pulsed control input, however, will remain energized for 10 ms after the
set command is given and will then reset automatically (i.e. no reset command required).
OP
In addition to the latched/pulsed option this column also allows the control inputs to be
individually assigned to the Hotkey menu by setting ‘1’ in the appropriate bit in the “Hotkey
Enabled” cell. The hotkey menu allows the control inputs to be set, reset or pulsed without
the need to enter the CONTROL INPUTS column. The Ctrl. Command cell also allows the
SET/RESET text, displayed in the hotkey menu, to be changed to something more suitable
for the application of an individual control input, such as ON/OFF, IN/OUT etc.
The CTRL. I/P LABELS column makes it possible to change the text associated with each
individual control input. This text will be displayed when a control input is accessed by the
hotkey menu, or it can be displayed in the PSL.
Note:
With the exception of pulsed operation, the status of the control inputs is
stored in supercapacitor. In the event that the auxiliary supply is interrupted
the status of all the inputs will be recorded. Following the restoration of the
auxiliary supply the status of the control inputs, prior to supply failure, will be
reinstated.
Application Notes
P746/EN AP/J43
MiCOM P40 Agile P746
(AP) 6-1
AP
APPLICATION NOTES
Hardware Suffix:
M
Software Version:
91
P746/EN AP/J43
(AP) 6-2
AP
Application Notes
MiCOM P40 Agile P746
Application Notes
MiCOM P40 Agile P746
P746/EN AP/J43
(AP) 6-3
CONTENTS
1
INTRODUCTION
7
1.1
Protection of Substation Busbars
7
2
APPLICATION OF INDIVIDUAL PROTECTION FUNCTIONS
8
2.1
Terminal Settings (for all protections)
8
2.1.1
CT Ratios
8
2.1.2
VT Ratios
8
2.2
Busbar Settings
9
2.2.1
Setting Guidelines
9
2.2.1.1
Sub-station Features
9
2.2.1.2
“Idiff_Ibias” Setting Calculation Spreadsheet
10
2.2.1.3
Differential Busbar Protection
10
2.2.1.4
87BB Settings (Compensated Earthed Network Schemes)
14
2.2.1.5
Differential Busbar Protection
14
2.3
Additional Protection Settings
14
2.3.1
Dead Zone Protection (DZ)
14
2.3.2
Circuit Breaker Fail (CBF)
15
2.3.2.1
External Backtrip Order
15
3
CURRENT TRANSFORMERS
16
4
ISOLATOR AND CIRCUIT BREAKER FUNCTION
17
4.1
Isolator State Monitoring Features
17
4.1.1
Use of One Position Information only
17
4.1.2
Use of the Two Positions Information
17
4.1.3
Use of the Two Positions Information
17
4.1.4
Use of the Two Positions Information
18
4.1.5
Use of the Two Positions Information
18
4.1.6
Isolator Supervision Alarm
18
4.2
Circuit Breaker State Monitoring
18
5
CURRENT TRANSFORMER SUPERVISION
19
5.1
Differential CTS
19
5.2
CTS Implementation
20
5.3
Application Notes
20
5.3.1
Differential CTS Setting Guidelines
20
6
VOLTAGE TRANSFORMER SUPERVISION
22
7
TRIP RELAYS AND TRIP CIRCUIT SUPERVISION
23
7.1
Trip Circuit Supervision Scheme 1
23
7.1.1
Resistor Values
23
7.1.2
PSL for TCS Scheme 1
24
AP
P746/EN AP/J43
(AP) 6-4
AP
Application Notes
MiCOM P40 Agile P746
7.2
Trip Circuit Supervision Scheme 3
24
7.2.1
Resistor Values
25
7.2.2
PSL for TCS Scheme 3
25
8
ISOLATION AND REDUCED FUNCTION MODE
26
9
BENEFITS OF SECTIONALIZED BUSBAR PROTECTION
27
9.1
Limitation of the Number of Feeders
27
9.1.1
Bias Characteristics
27
9.1.2
Bias Current in Discriminitative Zones
28
9.1.3
Bias Current in Check Zone
28
9.2
Disavantages of Busbar Schemes with Check Zone AND High Number of Feeders
28
9.2.1
Effect on Check Zone Sensitivity
28
9.2.2
Effect of Spill Current in Check Zone
29
9.2.3
Contingency during Relay / CT Failure
29
9.3
Benefits of Sectionalized Busbar Protection
29
9.3.1
Improved Sensitivity for Check Zone
29
9.3.2
Sectionalizing during Failure of Relays/CTs
29
9.3.3
Simplified Topology
29
9.4
Conclusion
29
10
TOPOLOGY
30
10.1
Topology Configuration
30
10.2
Topology Monitoring Tool
31
10.3
Topology Processing
32
10.3.1
Single Bar or Double Bus with Bus Sectionaliser
32
10.3.2
Double Bus with One CT Bus Coupler
33
10.3.3
Double Bus with Two CT Bus Coupler
34
10.3.4
CTs on One Side of Bus Coupler
36
10.3.5
CTs on both sides of bus coupler, CB closes before status acquisition.
38
10.3.6
CTs on one side of bus coupler, CB closed and fault evolves between CT and CB (even for
switch onto fault).
39
10.3.7
CTs on both sides of coupler, CB closed and fault evolves between CT and CB.
40
11
NUMERICAL DIFFERENTIAL BUSBAR PROTECTION PROJECT
42
11.1
One or Three Box Mode Selection
42
11.2
Application Solutions
44
11.2.1
1 Box Mode:
44
11.2.2
3 Box Mode:
44
11.2.3
Voltage Information
45
11.2.4
3 Boxes Mode with Simple Redundancy
49
11.2.5
2 out of 2 Solution
49
11.3
Check List
50
11.4
General Substation Information
51
11.5
Short Circuit Levels
51
11.6
Switchgear
51
Application Notes
P746/EN AP/J43
MiCOM P40 Agile P746
(AP) 6-5
11.7
Substation Architecture
52
12
STANDARD CONFIGURATIONS
53
13
APPLICATION OF NON PROTECTION FUNCTIONS
58
13.1
Function Keys
58
14
CT REQUIREMENTS
59
14.1
Notation
59
14.2
87BB Phase CT Requirements
59
14.2.1
Feeders connected to sources of significant power (i.e. lines and generators)
59
14.2.2
CT Specification according to IEC 185, 44-6 and BS 3938 (British Standard)
60
14.3
Support of IEEE C Class CTs
61
15
AUXILIARY SUPPLY FUSE RATING
62
FIGURES
Figure 1: External backtrip order
15
Figure 2: Differential CTS
20
Figure 3: TCS scheme 1
23
Figure 4: PSL for TCS Schemes 1
24
Figure 5: TCS scheme 3
24
Figure 6: PSL for TCS scheme 3
25
Figure 7: P746 Scheme editor
31
Figure 8: P746 synoptic
31
Figure 9: Bus section closed
32
Figure 10: Bus section open
32
Figure 11: Bus coupler closed
33
Figure 12: Bus coupler open
33
Figure 13: Bus coupler closed
34
Figure 14: Bus coupler open
34
Figure 15: Bus coupler closed and one isolator open
35
Figure 16: Bus coupler and one isolator open
36
Figure 17: CTs on one side of bus coupler, CB closes before status acquisition
36
Figure 18: CTs on both sides of bus coupler, CB closes before status acquisition
38
Figure 19: CTs on one side of bus coupler, CB closed and fault occurs between the CB & the CT
39
Figure 20: Zone 2 tripped, fault still present
39
Figure 21: CTs on both sides of bus coupler, CB closed fault occurs between A CT & the CB
40
Figure 22: Single busbar application with bus section isolator
54
Figure 23: Single busbar application with bus section circuit breaker
54
Figure 24: Breaker and a half scheme
56
Figure 26: Double Busbar application with bus coupler
56
Figure 26: Double bus bar with two circuit breakers per feeder
57
Figure 27: Commissioning mode default PSL
58
AP
P746/EN AP/J43
(AP) 6-6
AP
Application Notes
MiCOM P40 Agile P746
Application Notes
P746/EN AP/J43
MiCOM P40 Agile P746
1
(AP) 6-7
INTRODUCTION
Before carrying out any work on the equipment, the user should be
familiar with the contents of the safety section/safety guide
SFTY/4LM as well as the ratings on the equipment rating label.
1.1
Protection of Substation Busbars
The busbars in a substation are possibly one of the most critical elements in a power
system. If a fault is not cleared or isolated quickly, not only could substantial damage to the
busbars and primary plant result, but also a substantial loss of supply to all consumers who
depend on the substation for their electricity. It is essential that the protection associated with
them provides reliable, fast and discriminative operation.
As with any power system the continuity of supply is of the utmost importance. However,
faults that occur on substation busbars are rarely transient but more usually of a permanent
nature. Circuit breakers should be tripped and not subject to any auto-reclosure.
The busbar protection must also remain stable for faults that occur outside of the protected
zone as these faults will usually be cleared by external protection devices. In the case of a
circuit breaker failure it may be necessary to open all of the adjacent circuit breakers, which
can be achieved by issuing a backtrip to the busbar protection. Security and stability are key
requirements of a busbar protection scheme. If the busbar protection maloperates under
such conditions substantial loss of supply could result unnecessarily.
Many different busbar configurations exist. Typical arrangements are single or a double
busbar substation. The positioning of the primary plant can vary so it needs to be
considered. This in turn introduces variations, all of which have to be accommodated within
the busbar protection scheme.
Backup protection is an important feature of any protection scheme. In the event of
equipment failure, such as signalling equipment or switchgear, it is necessary to provide
alternative forms of fault clearance. It is desirable to provide backup protection, which can
operate with minimum time delay and yet discriminate with other protection elsewhere on the
system.
AP
P746/EN AP/J43
Application Notes
(AP) 6-8
2
MiCOM P40 Agile P746
APPLICATION OF INDIVIDUAL PROTECTION FUNCTIONS
The following sections detail protection functions in addition to where and how they can be
applied. Each section provides some worked examples on how the settings are applied to
the relay.
• Up to 6 sets of CTs, the P746 scheme is made with a single relay.
• Up to 18 sets of CTs, there are three relays that make up the P746 scheme.
• In some cases, 2 sets of one or three relays solutions are possible.
The P746 co-ordinates the scheme, acquires the analogue signals from the associated CT
and the binary signals from the auxiliary contacts of the primary plant (CB and isolator(s))
and acts on these signals, initiating a bus zone protection trip when necessary.
The P746 also incorporates the main circuit breaker failure logic together with additional
protections. The P746 allows for optional I/O, tricolour LEDs, function keys and additional
communication board slot (Ethernet or second rear port).
The main features of the P746 scheme are summarised below:
• Current differential busbar protection – Phase segregated biased differential protection
(sometimes referred to as low impedance type)
• Provides the main protection element for the scheme. This protection provides highspeed discriminative protection for all fault types
• Circuit breaker failure protection – two stage breaker fail logic that can be initiated
internally or externally.
AP
• Dead Zone phase protection.
• Non-directional phase fault over current protection – provides two stage protection.
• Low Burden – Allows the protection to be installed in series with other equipment on a
common CT secondary.
• Accommodates different CT classes, ratios and manufacturers.
2.1
Terminal Settings (for all protections)
For each Terminal (connected to the secondary of a High voltage CT):
2.1.1
CT Ratios
There are 3 values which can be entered:
1. Phase CT Primary current (from 1 to 30000 A) given by the manufacturer.
2. Phase CT secondary current (1 or 5 A) given by the manufacturer.
3. Polarity (Standard (towards the bar) or Inverted (opposite the bar)
Note:
For the busbar protection reference 2 values must be entered:
1. Phase reference CT Primary current (from 1 to 30000 A).
2. Phase reference CT secondary current (1 or 5 A).
2.1.2
VT Ratios
There are 2 values which can be entered:
1. Phase VT Primary voltage (from 100 to 100 kV) given by the manufacturer.
2. Phase VT secondary voltage (80 or 140 V) given by the manufacturer.
Application Notes
MiCOM P40 Agile P746
2.2
P746/EN AP/J43
(AP) 6-9
Busbar Settings
Busbar Biased Current Differential Protection
2.2.1
Setting Guidelines
87BB Phase Settings (Solid Earthed Network Schemes)
An excel spreadsheet tool “Idiff_Ibias“ is available on request to assure a reliable setting
choice:
2.2.1.1
Sub-station Features
There are eight values you need to know:
1. Number of independent bars
2. Maximum number of infeeds
3. Minimum load current in a feeder
4. Maximum load current in a feeder
5. Maximum load current in a bus
6. Biggest CT primary winding
AP
P746/EN AP/J43
Application Notes
(AP) 6-10
MiCOM P40 Agile P746
7. Minimum short-circuit value (phase to phase) in a bus
8. Voltage used (Yes or No)
2.2.1.2
“Idiff_Ibias” Setting Calculation Spreadsheet
Open the Idiff_Ibias spreadsheet and enter the eight values listed above. You should then be
able to choose seven additional values.
Note:
2.2.1.3
If the minimum internal fault detection is set below the maximum load an
additional criterion, such as voltage, must be used.
Differential Busbar Protection
1. ID>1 as high as possible with a minimum of 2% of the biggest CT primary winding and
less than 80% of the minimum load
2. Slope k1 (ID>1), usual recommendation is 10%
3. ID>2 as low as possible*, while ensuring the single CT failure will not cause tripping
under maximum load conditions with no VT.
4. Slope k2 (ID>2), usuaL recommendation is generally 50 / 65%
5. IDCZ>2 as low as possible*
6. Slope kCZ (IDCZ>2), usual recommendation is generally 30%
Explanations of the values:
AP
1. ID>1 is higher than 2% of the biggest CT to not detect noise coming from it and less
than 80% of the minimum load of a feeder to detect the minimum load imbalance in
case of a problem in that particular feeder.
2. Slope k1 recommendation is 10% to meet 10Pxx current transformers
3. ID>2 will be:
• below twice the maximum load for the phase comparison algorithm to pickup the load
and if possible below 50% of the minimum fault to be sub-cycle (80% otherwise)
• and if no voltage criteria is used above 100% (and when possible 120% to allow 20%
margin) of the biggest load to not maloperate in case of CT short-circuited or open
circuit
Note:
In one box mode voltage criteria can be used for single busbar only .
• and less than 80% of the minimum fault current to operate sub-cycle for the minimum
fault (and 50% when possible to be sure to always operate in 13ms)
1. Slope k2 (ID>2)
a.
Recommendation is 60%
To be always stable in the worth CT ratio conditions (between the biggest CT and
the smallest CT).
b.
Recommendation is 50% for China
In China, the requirement is to be able to detect a resistive fault equal to 50% of
the bias current.
2. IDCZ>2 same as ID>2
3. Slope kCZ (IDCZ>2)
a.
Recommendation is 30%
The requirement is to be able to trip for a fault that is counted twice by the Check Zone (for
example one and half circuit breaker substation) and depends on the number of bars:
• n bars (Independent bars)
• A minimum internal short-circuit value (Icc min (1 bar))
Application Notes
P746/EN AP/J43
MiCOM P40 Agile P746
(AP) 6-11
• A maximum load for a bar (IloadMax (1 bar)).
The worst case is:
• when all these buses are independent (bus sectionalizers open)
• the maximum load is on all the buses (biggest bias current)
• The internal short-circuit value is minimum.
AP
During the internal fault:
• the bias current is: Icc min (1 bar) + (n-1) x IloadMax (1 bar)
• the differential current is: Icc min (1 bar)
Therefore, the biggest slope for the Check Zone to detect the fault is:
Icc min (1 bar)
((Independent bars - 1) x IloadMax (1 bar)) + Icc min (1 bar)
If for example:
There are 3 buses and Icc min = IloadMax, the slope must be below 33%
For a one and half breaker scheme there are:
• 2 bars (Independent bars)
• A minimum internal short-circuit value (Icc min (1 bar))
• A maximum load for a bar (IloadMax (1 bar)).
P746/EN AP/J43
Application Notes
(AP) 6-12
MiCOM P40 Agile P746
Feeder
lload
lload
lload
lload
Feeder
Feeder
Feeder
Feeder
Feeder
P0872ENa
The worst case is:
AP
• when the busbar is split in 2 and goes as well through the opposite bar
• the maximum load is on the 2 buses (biggest bias current)
• The internal short-circuit value is minimum.
During the internal fault:
• the CZ bias current is:
2 x Icc min (1 bar) + 4 x IloadMax (1 bar)
• the CZ differential current is:
Icc min (1 bar)
Therefore, the biggest slope for the Check Zone to detect the fault is:
Icc min (1 bar)
(4 x IloadMax (1 bar)) + Icc min (1 bar)
If for example:
Icc min = IloadMax, the slope must be below 17%
b.
Recommendation is 25% for China
In china, the requirement is to be able to trip for a resistive fault that is counted
twice by the Check Zone (for example one and half circuit breaker substation).
4. ID>1 Alarm Timer to not operate for an external fault shall be greater than the longest
protection time (such as line, overcurrent, etc.)
5. Phase comparison.
Phase comparison is used to define the minimum current to be included in the phase
comparison algorithm; it is recommended to be 80% of (ID>2 / Σ In of Infeed CTs).
The requirement is to be able to detect a through fault that is fed by the infeeds; it does not
depend on the number of bars but depends on:
• The minimum internal short-circuit threshold (ID>2)
• The maximum number of infeeds and their CT primary nominal currents.
Application Notes
P746/EN AP/J43
MiCOM P40 Agile P746
(AP) 6-13
The worst scenario is when the CT is fully saturated and the differential algorithm picks up
on the ID>2 threshold. The phase comparison must block the trip by detecting the incoming
currents:
We assume the infeeds will contribute to the ID>2 fault in proportion to their CT primary
nominal current (worst situation).
Then we need for each infeed, phase comparison threshold to be lower than:
• PC max threshold per feeder = 0.8 x minimum primary fault current per terminal
• And phase comparison = ID>2 / (In CT / Σ(In CTs infeeds)) / In CT,
So, for any infeed, phase comparison max = ID>2 / Σ(In CTs infeeds))
We take 80% of this value so that to keep sufficient margin. The recommended resultant
setting is as follows:
Maximum resultant phase comparison = 0.8 × ID>2 / Σ(In CTs infeeds)
*Where resultant setting is
*ID>2 Current setting (in Primary) x PhComp PU Ratio setting
Example:
Infeed
CT
Contribution*
PC%
Infeed 1
2500 / 5
2500 / 11300
Infeed 2
2000 / 1
2000 / 11300
2000 / 11300 – ID>2
2000
=
ID>2
11300
Infeed 3
2000 / 1
2000 / 11300
2000 / 11300 – ID>2
2000
=
ID>2
11300
Infeed 4
1200 / 1
1200 / 11300
1200 / 11300 – ID>2
1200
=
ID>2
11300
Infeed 5
1200 / 1
1200 / 11300
1200 / 11300 – ID>2
1200
=
ID>2
11300
Infeed 6
1200 / 1
1200 / 11300
1200 / 11300 – ID>2
1200
=
ID>2
11300
Infeed 7
1200 / 1
1200 / 11300
1200 / 11300 – ID>2
1200
=
ID>2
11300
2500 / 11300 – ID>2
2500
=
ID>2
11300
ΣIn = 2500 + (2 × 2000) + (4 × 1200) = 11300
We assume the infeeds will contribute to the ID>2
fault in proportion to their CT pimary current (worst
situation)
then resultant phase comparison
setting = ID>2 / Σ In of Infeed CTs
AP
P746/EN AP/J43
Application Notes
(AP) 6-14
2.2.1.4
MiCOM P40 Agile P746
87BB Settings (Compensated Earthed Network Schemes)
Sub-station features
Only four values need to be known:
2.2.1.5
1.
Maximum load current in a feeder
2.
Minimum phase to phase fault current (Ph-Ph min.) in a bus
3.
Maximum single phase steady state faulty current (Ph-N Max.) in a bus
4.
Number of independent bars
5.
Maximum number of infeeds
Differential Busbar Protection
Nine values have to be chosen:
AP
1.
ID>1, usual recommendation is 1,2 × (Ph-N Max.) with a minimum of 2% of the
biggest CT primary winding and less than 80% of the minimum load,
2.
Slope k1 (ID>1), usual recommendation is 10%.
3.
ID>1 Alarm Timer (from 0 to 600 s) shall be greater than the longest Busbar protection
time
4.
Slope k2 usual recommendation is 50 / 65%.
5.
ID>2 recommendation is: Lower than 0.8 × (Ph-Ph min) and higher than 1.2 × Iload
Max and if possible, equal to 6 × (ID>1).
6.
Slope kCZ usual recommendation is 30%.
7.
IDCZ>2 usual recommendation is: Lower than 0.8 × (Ph-Ph min) and higher than
1.2 × Iload Max and if possible equal to 6 × (ID>1).
Explanations of the values:
1.
ID>1 shall be higher than 120% of the highest phase to neutral fault to not operate in
case of phase to neutral fault.
2.
Slope k1 recommendation is 10% to meet 10Pxx current transformers
3.
Slope k2 (ID>2) recommendation is 50 / 65%
To be stable in the worth CT ratio conditions (between the biggest CT and the smallest CT).
60% is OK if the CT ratio is less than 5.
1.
ID>2 shall be lower than 80% of the minimum phase to phase fault current to operate
sub-cycle for the minimum fault and higher than 120% Ioad Max (120% to allow 20%
margin) and if possible equal to 6 × (ID>1) to be insensitive to the worth CT saturation.
2.
IDCZ>2 same as ID>2
3.
Slope kCZ (IDCZ>2) recommendation is 30%
The requirement is to be able to trip for a fault that is counted twice by the Check Zone (for
example one and half circuit breaker substation).
2.3
Additional Protection Settings
2.3.1
Dead Zone Protection (DZ)
On a feeder, if the isolators or the breaker is open, a dead zone (or end zone) is said to exist
between the open element and the CT. The P746 can protect this zone with the Dead Zone
protection. This is a simple time delayed overcurrent element which is only active when a
dead zone is identified in the local topology.
Setting guidelines
For each CT connected to a Feeder Circuit Breaker (not on bus couplers or bus sections)
Application Notes
P746/EN AP/J43
MiCOM P40 Agile P746
(AP) 6-15
For the phase:
•
I>DZ must be below 80% of the minimum Dead Zone fault level (and if possible bigger
than the maximum load).
•
I>DZ Time delay must be at least 50ms if the CB status positions are used (any value
otherwise)
IMPORTANT NOTE:
When a dead zone fault occurs and the bias current flowing through the bus is small,
there could be a maloperation of the 87BB. To prevent this we recommend you enable
an additional criterion such as voltage. In one box mode, voltage criteria can be used
for single busbar only.
2.3.2
Circuit Breaker Fail (CBF)
Setting guidelines
The typical timer settings are as follows:
CB fail reset mechanism
CB open
Undercurrent elements
tBF time delay
CB auxiliary contacts
opening/ closing time (max.) + error in tBF
timer + safety margin
CB interrupting time + undercurrent
element (max.) + safety margin operating
time
Typical delay for 2 cycle circuit
breaker
50 + 10 + 50 = 110 ms
50 + 15 + 20 = 85 ms
The examples above consider direct tripping of a 2-cycle circuit breaker. Where auxiliary
tripping relays are used, an additional 10-15 ms must be added to allow for trip relay
operation.
The phase undercurrent settings (Ι<) must be set less than load current to ensure that Ι<
operation indicates that the circuit breaker pole is open. A typical setting for overhead line or
cable circuits is 20% Ιn, with 5% Ιn common for generator circuit breaker CBF.
2.3.2.1
External Backtrip Order
When a direct backtrip order needs to be used to trip a dedicated zone, the following PSL
should be used:
Figure 1: External backtrip order
AP
P746/EN AP/J43
(AP) 6-16
3
Application Notes
MiCOM P40 Agile P746
CURRENT TRANSFORMERS
A P746 can accommodate different CT ratios throughout the protected zone. The maximum
ratio between the smallest primary CT winding and the biggest primary CT winding is 40.
This mix must be accounted for by the scheme, which is achieved by using the primary
currents sent by the P746 to the P746 that undertakes scheme calculations.
A settable common virtual current transformer is used to convert to secondary values. The
Ref Current setting serves this purpose.
AP
Application Notes
MiCOM P40 Agile P746
4
ISOLATOR AND CIRCUIT BREAKER FUNCTION
4.1
Isolator State Monitoring Features
P746/EN AP/J43
(AP) 6-17
The P746 protection requires a reliable indication of the state of the isolators to decide which
breaker to trip in case of fault. The relay can incorporate isolator state monitoring giving an
indication of the position of the isolator, or if the state is unknown, an alarm can be raised
using the following PSL:
4.1.1
Use of One Position Information only
The use of the open position (89b) is highly recommended.
The position will be forced as closed as soon as the isolator leaves the open position.
4.1.2
Use of the Two Positions Information
AP
The position will be forced as open as soon as the isolator leaves the closed position.
This is not recommended as it could trip in 2 steps instead of 1 in case of a fault appearing
during the closing period of the isolator.
4.1.3
Use of the Two Positions Information
The position will be forced as closed as soon as the isolator leaves the open position.
P746/EN AP/J43
(AP) 6-18
4.1.4
Application Notes
MiCOM P40 Agile P746
Use of the Two Positions Information
The position will be seen as closed only when the isolator arrives at the closed position.
This is not recommended as the P746 could trip in 2 steps instead of 1 in case of a fault
appearing during the closing period of the isolator.
4.1.5
Use of the Two Positions Information
AP
The position will be seen as closed only when the isolator arrives at the closed position and
seen open only when the isolator will arrive at the open position.
This is not recommended as the P746 could trip in 2 steps instead of 1 in case of a fault
appearing during the closing period of the isolator.
4.1.6
Isolator Supervision Alarm
When using both positions information, an alarm can be raised when the 00 or 11
combination is present during a certain time:
4.2
Circuit Breaker State Monitoring
An operator at a remote location requires a reliable indication of the state of the switchgear.
Without an indication that each circuit breaker is either open or closed, the operator has
insufficient information to decide on switching operations. The relay incorporates circuit
breaker state monitoring giving an indication of the position of the circuit breaker or if the
state is unknown, an alarm is raised.
Application Notes
MiCOM P40 Agile P746
5
P746/EN AP/J43
(AP) 6-19
CURRENT TRANSFORMER SUPERVISION
The Current Transformer Supervision function (CTS) is used to detect failure of the AC
current inputs to the protection. This may be caused by internal current transformer faults,
overloading, or faults on the wiring. If there is a failure of the AC current input, the protection
could misinterpret this as a failure of the actual phase currents on the power system, which
could result in maloperation. Also, an open circuit in the AC current circuits can cause
dangerous CT secondary voltages to be generated.
The differential method uses the ratio between positive and negative sequence currents to
determine CT failure. This method is not voltage dependant and relies on channel
communications to declare a CTS condition.
5.1
Differential CTS
Differential CTS does not need any local voltage measurements to determine a CTS
condition. It is based on measurement of the ratio of negative sequence current to positive
sequence current (I2/I1) at all terminals. When this ratio is small (theoretically zero), one of
four possible conditions apply:
The system is unloaded (both I2 and I1 are zero)
• The system is loaded but balanced (I2 is zero)
• The system has a three phase fault present (I2 is zero)
• There is a genuine 3 phase CT problem (unlikely, but if this is the case it would
probably develop from a single or two phase condition)
If the ratio is non-zero, we can assume one of two conditions are present:
• The system has an unbalanced fault (both I2 and I1 are non-zero)
• There is a 1 or 2 phase CT problem (both I2 and I1 are non-zero)
Measurement at a single end cannot provide any more information than this. However, if the
ratio is calculated at all ends and compared, the device can make a decision based on the
following criteria:
• If the ratio is non-zero at more than two ends, it is almost certainly a genuine fault
condition and so the CT supervision is prevented from operating.
• If the ratio is non-zero at one end, there is a chance of either a CT problem or a
single-end fed fault condition.
A second criterion looks to see whether the differential system is loaded or not . For this
purpose the device looks at the positive sequence current I1. If load current is detected at
one-end only, the device assumes that this is an internal fault condition and prevents CTS
operation. However, if load current is detected at two or more ends, this indicates CT failure,
so CTS operation is allowed.
There are two modes of operation, Indication and Blocking. You determine the mode of
operation with the CTS Status setting. In Indication mode, a CTS alarm is raised but there
is no effect on tripping. In Blocking mode, the differential protection is blocked for 20 ms
after CT failure detection, then the Bus Differential threshold setting is raised above the load
current.
For correct operation of the scheme, Differential CTS must be enabled at each end of the
protected zone.
AP
P746/EN AP/J43
Application Notes
(AP) 6-20
MiCOM P40 Agile P746
Inhibit CTS
&
Any Trip
Disable CTS
CT1 L i1>
CT1 R1 i1>
CT1 R2 i1>
1
>
=
2
CT1 L i2/i1>>
CT1 R1 i2/i1>
CTS Time Delay
CTS Status
Indication
&
S
Pickup
CT1 R2 i2/i1>
CT Fail Alarm
Q
&
R
1
&
CTS Status
CTS Block
Restrain
CT1 R1 i2/i1>>
CT1 L i2/i1>
&
CTS Status
CT1 R2 i2/i1>
Restrain
CTS Restrain
CTS Status
AP
&
1
Indication
Pickup
&
CTS Block Diff
CTS Time Delay
1
S
Pickup
*
&
Q
CT Fail Alarm
R
CT1 R2 i2/i1>>
CT1 L i2/i1>
CT1 R1 i2/i1>
&
*In indication mode, timer is set to 20ms
V01296
Figure 2: Differential CTS
5.2
CTS Implementation
If the power system currents are healthy, no zero sequence voltage are derived. However, if
one or more of the AC current inputs are missing, a zero sequence current would be derived,
even if the actual power system phase currents are healthy. Standard CTS works by
detecting a derived zero sequence current where there is no corresponding derived zero
sequence voltage.
The voltage transformer connection used must be able to refer zero sequence voltages from
the primary to the secondary side. Therefore, this element should only be enabled where the
VT is of a five-limb construction, or comprises three single-phase units with the primary star
point earthed.
The CTS function is implemented in the SUPERVISION column of the relevant settings
group, under the sub-heading CT SUPERVISION.
The following settings are relevant for CT Supervision:
5.3
Application Notes
5.3.1
Differential CTS Setting Guidelines
The CTS i1> setting, once exceeded, indicates that the circuit is loaded. A default setting of 0.1 In is
considered suitable for most applications, but could be lowered in case of oversized CTs.
The CTS i2/i1> setting should be in excess of the worst unbalanced load expected in the circuit under normal
Application Notes
P746/EN AP/J43
MiCOM P40 Agile P746
(AP) 6-21
operation. It is recommended to read out the values of i2 and i1 in the MEASUREMENTS 1 column and set the
ratio above 5% of the actual ratio.
The CTS i2/i1>> setting should be kept at the default setting (40% In). If the ratio i2/i1 exceeds the value of
this setting at only one end, the CT failure is declared.
Note:
The minimum generated i2/i1 ratio will be 50% (case of one CT secondary
phase lead being lost), and therefore a setting of 40% is considered
appropriate to guarantee sufficient operating speed.
AP
P746/EN AP/J43
(AP) 6-22
6
Application Notes
MiCOM P40 Agile P746
VOLTAGE TRANSFORMER SUPERVISION
The Voltage Transformer Supervision (VTS) function detects failure of the AC voltage inputs
to the IED. If the IED misinterprets this as a failure of the actual phase voltages on the power
system, it could result in unnecessary tripping of a circuit breaker. To prevent this, the VTS
detects voltage input failures which are not caused by a failure of the power system phase
voltage.
The P746 does this by looking at each zone. For each zone, if VTS detects a differential
current and a voltage drop, it blocks the VT for that zone. This prevents the busbar
differential element from signalling a fault for that zone and tripping a circuit breaker.
AP
Application Notes
P746/EN AP/J43
MiCOM P40 Agile P746
7
(AP) 6-23
TRIP RELAYS AND TRIP CIRCUIT SUPERVISION
Any relays contact can be used for tripping signals from busbar protection, overcurrent
protection and breaker failure.
The trip circuit, in most protective schemes, extends beyond the relay enclosure and passes
through components such as fuses, links, relay contacts, auxiliary switches and other
terminal boards. This complex arrangement, coupled with the importance of the trip circuit,
has led to dedicated schemes for its supervision.
Several trip circuit supervision schemes with various features can be produced with the
P746. Although there are no dedicated settings for TCS, in the following schemes can be
produced using the programmable scheme logic (PSL). A user alarm is used in the PSL to
issue an alarm message on the relay front display. If necessary, the user alarm can be renamed using the menu text editor to indicate that there is a fault with the trip circuit.
7.1
Trip Circuit Supervision Scheme 1
This scheme provides supervision of the trip coil with the CB open or closed, however, it
does not provide supervision of the trip path whilst the breaker is open. The CB status can
be monitored when a self-reset trip contact is used. However, this scheme is incompatible
with latched trip contacts, as a latched contact will short out the opto-input for a time
exceeding the recommended Delayed Drop-off (DDO) timer setting of 400 ms, and therefore
does not support CB status monitoring. If you require CB status monitoring, further optoinputs must be used.
Note:
a 52a CB auxiliary contact follows the CB position and a 52b contact is the
opposite.
+ve
Trip Output Relay
Trip path
52A
Trip coil
Blocking diode
52B
R1
V01214
Opto-input
Circuit Breaker
-ve
Figure 3: TCS scheme 1
When the CB is closed, supervision current passes through the opto-input, blocking diode
and trip coil. When the CB is open, supervision current flows through the opto-input and into
the trip coil via the 52b auxiliary contact.
This means that Trip Coil supervision is provided when the CB is either closed or open,
however Trip Path supervision is only provided when the CB is closed. No supervision of the
trip path is provided whilst the CB is open (pre-closing supervision). Any fault in the trip path
will only be detected on CB closing, after a 400 ms delay.
7.1.1
Resistor Values
Resistor R1 is an optional resistor that can be fitted to prevent maloperation of the circuit
breaker if the opto input is inadvertently shorted, by limiting the current to <60 mA. The
resistor should not be fitted for auxiliary voltage ranges of 30/34 volts or less, as satisfactory
operation can no longer be guaranteed. The table below shows the appropriate resistor
value and voltage setting (OPTO CONFIG. menu) for this scheme.
AP
P746/EN AP/J43
Application Notes
(AP) 6-24
MiCOM P40 Agile P746
This TCS scheme will function correctly even without resistor R1, since the opto input
automatically limits the supervision current to less that 10 mA. However, if the opto is
accidentally shorted the circuit breaker may trip.
Auxiliary Voltage (Vx)
Resistor R1 (ohms)
48/54
110/250
220/250
Opto Voltage Setting with R1 Fitted
1.2k
2.5k
5.0k
Note:
24/27
48/54
110/125
When R1 is not fitted the opto voltage setting must be set equal to supply
voltage of the supervision circuit.
This Scheme is not compatible with Trip Circuit voltages of less than 48 V.
7.1.2
PSL for TCS Scheme 1
Opto Input
0
0
dropoff
Straight
400
&
50
pickup
0
Latching
0
*Output Relay
LED
User Alarm
AP
*NC stands for Normally Closed.
V01217
Figure 4: PSL for TCS Schemes 1
The opto-input can be used to drive a Normally Closed Output Relay, which in turn can be
used to drive alarm equipment. The signal can also be inverted to drive a latching
programmable LED and a user alarm DDB signal.
The DDO timer operates as soon as the opto-input is energised, but will take 400 ms to drop
off/reset in the event of a trip circuit failure. The 400 ms delay prevents a false alarm due to
voltage dips caused by faults in other circuits or during normal tripping operation when the
opto-input is shorted by a self-reset trip contact. When the timer is operated the NC
(normally closed) output relay opens and the LED and user alarms are reset.
The 50 ms delay on pick-up timer prevents false LED and user alarm indications during the
power up time, following a voltage supply interruption.
7.2
Trip Circuit Supervision Scheme 3
TCS Scheme 3 is designed to provide supervision of the trip coil with the breaker open or
closed. It provides pre-closing supervision of the trip path. Since only one opto input is used,
this scheme is not compatible with latched trip contacts. If you require CB Status monitoring,
further opto-inputs must be used.
+ve
R3
Output Relay
Trip path
52A
Trip coil
R2
52B
Opto-input
V01216
Figure 5: TCS scheme 3
R1
Circuit Breaker
-ve
Application Notes
P746/EN AP/J43
MiCOM P40 Agile P746
(AP) 6-25
When the CB is closed, supervision current passes through the opto-input, resistor R2 and
the trip coil. When the CB is open, current flows through the opto-input, resistors R1 and R2
(in parallel), resistor R3 and the trip coil. The supervision current is maintained through the
trip path with the breaker in either state, therefore providing preclosing supervision.
7.2.1
Resistor Values
Resistors R1 and R2 are used to prevent false tripping, if the opto-input is accidentally
shorted. However, unlike the other two schemes. This scheme is dependent upon the
position and value of these resistors. Removing them would result in incomplete trip circuit
monitoring. The table below shows the resistor values and voltage settings required for
satisfactory operation.
Auxiliary Voltage
(Vx)
Resistor R1 & R2
(ohms)
Resistor R3 (ohms)
Opto Voltage
Setting
48/54
1.2k
0.6k
24/27
110/250
2.5k
1.2k
48/54
220/250
5.0k
2.5k
110/125
This Scheme is not compatible with Trip Circuit voltages of less than 48 V.
7.2.2
PSL for TCS Scheme 3
Opto Input
0
AP
0
dropoff
Straight
400
&
50
pickup
0
Latching
0
*Output Relay
LED
User Alarm
*NC stands for Normally Closed.
Figure 6: PSL for TCS scheme 3
V01217
P746/EN AP/J43
(AP) 6-26
8
Application Notes
MiCOM P40 Agile P746
ISOLATION AND REDUCED FUNCTION MODE
The scheme permits maintenance on the busbar and, or busbar protection while maintaining
some form of protection if possible. The maintenance mode level in the P746 allows this to
be possible and forces the scheme to a reduced operating mode as follow.
• 87BB Blocked & 50BF disabled:
• It’s a per zone selection.
• In this mode, both the busbar and circuit breaker fail conditions are monitored but all
trips are inhibited for the selected zone.
• When a zone is in this mode, the P746 does take into account the local currents and
topology and keeps the other zone in normal service.
• The output relays to the breakers connected to that selected zone and dead zone will
not operate.
• A Bus can be tested locally and secondary injection tests can be carried out because
the P746 is in 87BB&50BF blocked mode for the selected zone
• On a genuine fault on that zone the P746 will not send a 87BB or 50BF backtrip order
AP
Application Notes
MiCOM P40 Agile P746
9
P746/EN AP/J43
(AP) 6-27
BENEFITS OF SECTIONALIZED BUSBAR PROTECTION
The P746 range of subcycle busbar protection relays are designed and proven for its
sensitivity and fast operation for all type of internal faults. The P746 ensures the required
stability for all the external faults even with extremely high magnitude of fault currents. The
device can be utilized in centralized schemes as per the requirements of the project.
The P746 can protect up to 2 zones and 18 feeders with all type of physical layouts like
single busbar, double busbar, busbars with reserve bus and, one and half breaker schemes
etc…
9.1
Limitation of the Number of Feeders
9.1.1
Bias Characteristics
In low impedance busbar schemes, spill current during load or fault conditions due to Imag,
CT error, remanence flux, different CT ratios are taken care by the bias characteristics,
where the differential settings of the discriminative and check zone will increase based on
the restraining current by a factor of the % slope.
Disc. Zone – Diff. setting = Ibias of main zone × slope % or ID>2, whichever is higher.
Check.Zone – Diff. setting = Ibias of check zone × slope% or ID>2, whichever is higher.
When bias current increases, differential setting will increase proportionately by the factor of
slope. This means bias characteristics provides more stability (to take care of spill) and
reduce the sensitivity; however the tripping will occur for internal faults if it falls under
operating region
AP
P746/EN AP/J43
Application Notes
(AP) 6-28
MiCOM P40 Agile P746
X
i
i
1
X
X
i
3
X
c
i
2
X
i
m
P3608ENa
9.1.2
Bias Current in Discriminitative Zones
Magnitude of bias current in discriminative zones will be equal to scalar sum of all the
currents entering/leaving that particular zone ONLY.
Zone 1 Bias current: ibiasZ(t) = |i1| + | i3| + … + |ic| = Σ |in1|
Zone 2 Bias current: ibiasZ(t) = |ic| + |i2| + |im| = Σ |in2|
AP
For example:
If we have 8 feeders and among that we have 5 feeders connected to zone1 / bus1. All the
currents involved in that zone1 will be summated as zone1 bias current. If the remaining 3
feeders are connected to zone2/bus2, all the currents in that zone2 will be summated as
zone2 bias current.
9.1.3
Bias Current in Check Zone
Magnitude of bias current in check zone will be equal to scalar sum of all the currents
entering/leaving the WHOLE substation (the current flowing into coupling is not used)
CZ Bias current: ibiasCZ(t) = |iFeeder1| + … + |iFeederm| = Σ |iFeederm|
For example:
If we have a total of 8 feeders in the station and current through all the outgoing/incoming
feeders will be summated and will be considered as check zone bias current. Therfore, the
differential current setting at any point of time could be different for discriminative zones and
check zone, based on the bias of discriminative zones and check zone.
9.2
Disavantages of Busbar Schemes with Check Zone AND High Number of Feeders
9.2.1
Effect on Check Zone Sensitivity
Let’s consider double busbar system, where bus1 has least number of feeders (say 5
feeders) with weak source and busbar 2 has more number of feeders (say 30 feeders).
check zone (CZ) bias current will be extremely large since it sums up all the currents
entering/leaving the station. When there is a fault in bus1, discriminative zone 1 will operate
considering the zone1 bias current, whereas check zone will need higher differential current
for the same fault since the bias current for the same situation could be very huge.
This reduction in sensitivity will affect the operation of CZ element based on the level of
biasing which is based on the number of feeders, ID>CZ and slope kCZ. In certain cases it
can even lead to non-operation of the CZ element during an internal fault.
It’s not recommended to use check zone with a large number of feeders (typically more than
18) for a low impedance biased differential scheme.
Application Notes
MiCOM P40 Agile P746
9.2.2
P746/EN AP/J43
(AP) 6-29
Effect of Spill Current in Check Zone
When high numbers of CTs (typically more than 18) are connected to check zone, more spill
current is expected during load conditions. Therefore, CT circuitry fault setting needs to be
set with caution. It should be more than the standing spill current to avoid spurious blocking
of busbar element. At the same time, the setting should be lower than the minimum loaded
feeder current setting. In most cases it may be difficult to satisfy the requirements.
Moreover, spill current will increase when the busbar is extended with additional feeders,
where the characteristics of new CTs are different from the existing CTs and it may
aggravate the situation.
9.2.3
Contingency during Relay / CT Failure
When CT circuit supervision operates or relay fails in the non segregated busbar schemes it
affects the check zone and completely blocks the busbar protection. With the help of
segregated busbar schemes, effect will be limited to one section of the busbar protection
only.
9.3
Benefits of Sectionalized Busbar Protection
9.3.1
Improved Sensitivity for Check Zone
When the busbar protection is segregated into two or more sections, restraining quantities of
the CZ for the individual sections are reduced significantly compared to the check zone of
the complete substation. At the same time, check zone element will maintain its inherent
advantages but with more sensitivity. Therefore, it is advantageous to use sectionalized
busbar schemes for stations with large number of CTs.
9.3.2
Sectionalizing during Failure of Relays/CTs
When we section the scheme with two or more central units, the discrepancy during the
failure of any relay or CT in one side will not block or affect the scheme on other side. This
requirement is essential since the busbar is large and we should not compromise on full
busbar protection being removed/blocked. “busbar scheme sectionalizing” is more
analogous to the requirement of the “bus section breaker”, which helps to segregate the
busbar during a failure on the other side.
With the help of sectioned schemes we will have one side of busbar protection intact during
the failure of busbar protection on the other side. Moreover, this advantage will be applicable
during bay extensions without any impact to the other side of the busbar.
9.3.3
Simplified Topology
In the topology of the P746 it is easy to handle the layout since the topology for both sides is
fully independent to each other. Extension, addition and modification of bays is easy and
secured.
9.4
Conclusion
With the above advantages and proven experience of P746 busbar protection, General
Electric recommend you use the sectionalized busbar protection scheme. Implementing the
sectionalized busbar scheme provides more benefits in all aspects with all the inherent
features of typical busbar scheme.
AP
P746/EN AP/J43
Application Notes
(AP) 6-30
10
MiCOM P40 Agile P746
TOPOLOGY
The topological analysis of the state of the substation in real time is one of the primary
factors of the reliability of numerical differential busbar protection. Therefore, in the case of a
power system fault this analysis determines the sections of the substation concerned with
the fault and only takes these sections out of service. The algorithms available for topological
analysis make this level of discrimination possible and it is these algorithms that are utilized
in the P746 scheme.
10.1
Topology Configuration
The P746 topology is determined by replication of the circuit, i.e. the connections between
the various pieces of plant on the system. This topological replication is carried out from the
setting information in SYSTEM CONFIG:
Note:
AP
The connection n°1 is on the right and increasing to the left up to 6 for one
box mode and up to 18 for three boxes mode.
Z1 Terminals
000011 to be set to 1 if the terminal connection can only be to Zone 1
Z2 Terminals
000100 to be set to 1 if the terminal connection can only be to Zone 2
Xfer Terminals
001000 to be set to 1 if the terminal connection can be to Zone 1 or
Zone 2
ChZONE Terminal
001111 to be set to 1 if the terminal connection is part of the Check
Zone
If there is no bus coupling or it is an isolator all the following settings will be none.
For Bus coupling by Breaker with 1 CT
Z1 Bus CT
CT6 is the number of the CT used
Z1 Bus CT Pol
Inverted is the direction of the CT
Z2 Bus CT
CT6 is the number of the CT used
Z2 Bus CT Pol
Standard is the direction of the CT
For Bus coupling by Breaker with 2 CTs
Note:
Z1 Bus CT
CT5 is the number of the CT used
Z1 Bus CT Pol
Standard is the direction of the CT
Z2 Bus CT
CT6 is the number of the CT used
Z2 Bus CT Pol
Standard is the direction of the CT
As the zone between the 2 CTs must belong to both zones, it is important to
set the left CT to the right zone and vice versa.
Application Notes
MiCOM P40 Agile P746
10.2
P746/EN AP/J43
(AP) 6-31
Topology Monitoring Tool
This topological monitoring is carried out from a single line diagram of the system, which is
used to recreate the system using the topology configuration software. This can be carried
out by customer.
AP
Figure 7: P746 Scheme editor
Figure 8: P746 synoptic
The topology configuration tool uses standard symbols for creating the system model by
simply dragging and dropping in the configuration screen.
P746/EN AP/J43
Application Notes
(AP) 6-32
10.3
MiCOM P40 Agile P746
Topology Processing
The following scenarios demonstrate how the dynamic topology processing works and
accommodates anomalies and discrepancies in the scheme.
10.3.1
Single Bar or Double Bus with Bus Sectionaliser
Bus Section Closed
Isolator Closed
Isolator Closed
Zone 1 = CT1 + CT2
Zone 1 = BB1 + BB2
CB Closed
CB Closed
Check Zone = CT1 + CT2
AP
P0873ENa
Figure 9: Bus section closed
A zone is defined from a CT to another CT or an open electrical element (coupler CB or
isolator).
As all the breakers and isolators are closed there is only one zone including BB1 and BB2.
Bus Section Open
Zone 1 = CT1
Zone 2 = CT2
Zone 1 = BB1
Zone 2 = BB2
Isolator Closed
CB Closed
Isolator Closed
CB Closed
Check Zone = CT1 + CT2
P0875ENa
Figure 10: Bus section open
A zone is defined from a CT to another CT or an open electrical element (coupler CB or
isolator).
When the bus section is open, a zone is created from each bar feeder CT to that open bus
section.
Application Notes
P746/EN AP/J43
MiCOM P40 Agile P746
(AP) 6-33
There is one zone for BB1 and one zone for BB2.
10.3.2
Double Bus with One CT Bus Coupler
Zone 1 = CT1 + CT3
Zone 2 = CT2 + CT3
Zone 1 = BB1
Zone 2 = BB2
Coupling Closed
Isolator Closed
CB Closed
Isolator Closed
CB Closed
Check Zone = CT1 + CT2
P0876ENa
AP
Figure 11: Bus coupler closed
A zone is defined from a CT to another CT or an open electrical element (coupler CB or
isolator).
When one CT is used in the coupling and the coupler CB is closed, a zone is created from
each bar feeder CT to that coupler CT.
There is one zone for BB1 to CT3 and one zone for BB2 to CT3.
CT 3 is not taken into account
Zone 1 = CT1
Zone 2 = CT2
Zone 1 = BB1
Zone 2 = BB2
Coupling Open
Isolator Closed
CB Closed
Isolator Closed
CB Closed
Check Zone = CT1 + CT2
P0877ENa
Figure 12: Bus coupler open
P746/EN AP/J43
Application Notes
(AP) 6-34
MiCOM P40 Agile P746
A zone is defined from a CT to another CT or an open electrical element (coupler CB or
isolator).
When one CT is used in the coupling, and the coupler CB is open, the coupler CT
measurement is not taken into account and a zone is created from each bar feeder CT to
that open coupler CB.
There is one zone for BB1 and one zone for BB2.
10.3.3
Double Bus with Two CT Bus Coupler
CT 3
CT 4
BB 2
BB 1
Coupling Closed
Isolator Closed
Zone 1 = CT1 + CT4
Zone 2 = CT2 + CT3
Zone 1 = BB1
Zone 2 = BB2
Isolator Closed
CB Closed
CB Closed
CT 2
CT 1
AP
Check Zone = CT1 + CT2
Figure 13: Bus coupler closed
A zone is defined from a CT to another CT or an open electrical element (coupler CB or
isolator).
When 2 CTs are used in the coupling and the coupler CB is closed, a zone is created from
each bar feeder CT to the opposite coupler CT.
The zone between the 2 coupler CTs belongs to both zones.
There is one zone for BB1 to CT4 and one zone for BB2 to CT3.
CT 3&4 not taken into account
Zone 1 = CT1
Zone 2 = CT2
Zone 1 = BB1
Zone 2 = BB2
Coupling Open
Isolator Closed
CB Closed
Isolator Closed
CB Closed
Check Zone = CT1 + CT2
P0879ENa
Figure 14: Bus coupler open
Application Notes
P746/EN AP/J43
MiCOM P40 Agile P746
(AP) 6-35
A zone is defined from a CT to another CT or an open electrical element (coupler CB or
isolator).
When 2 CTs are used in the coupling, and the coupler CB is open, the coupler CTs
measurements are not taken into account and a zone is created from each bar feeder CT to
that open coupler CB.
There is one zone for BB1 and one zone for BB2.
CT 3
CT 4
VZ 3
BB 2
BB 1
Coupling Closed
Coupling
Zone
Zone
Zone
Zone
1
2
1
2
=
=
=
=
CT1
CT2
BB1
BB2
Isolator Closed
Isolator Closed
CB Closed
CT 1
CB Closed
CT 2
AP
Check Zone = CT1 + CT2
P0880ENa
Figure 15: Bus coupler closed and one isolator open
A zone is defined from a CT to another CT or an open electrical element (coupler CB or
isolator).
When 2 CTs are used in the coupling and the coupler CB is closed but a coupler isolator is
open, the coupler CTs measurements are not taken into account and a zone is created from
each bar feeder CT to that open coupler isolator.
The zone between the 2 coupler CTs belongs to the closed isolator zone.
There is one zone for BB1 to the open isolator and one zone for BB2 to the open isolator.
P746/EN AP/J43
Application Notes
(AP) 6-36
MiCOM P40 Agile P746
Extended
Zone
Zone 1 = CT1
Zone 2 = CT2
Zone 1 = BB1
Zone 2 = BB2
CT 3&4 not taken into account
Coupling Open
Isolator Closed
Isolator Closed
CB Closed
CB Closed
Check Zone = CT1 + CT2
P0881ENa
Figure 16: Bus coupler and one isolator open
A zone is defined from a CT to another CT or an open electrical element (coupler CB or
isolator).
AP
When 2 CTs are used in the coupling and the coupler CB is open and a coupler isolator is
open, the coupler CTs measurements are not taken into account and a zone is created from
each bar feeder CT to the open CB coupler and to the open coupler isolator.
The zone between the 2 coupler CTs belongs to the closed isolator zone.
There is one zone for BB1 to the open breaker and one zone for BB2 to the open isolator.
10.3.4
CTs on One Side of Bus Coupler
Figure 17: CTs on one side of bus coupler, CB closes before status acquisition
As the CB has closed but the status has not yet been refreshed the topology still believes the
CB to be open.
Treating this as an open bus coupler circuit breaker the topology algorithm will have
extended Zone 1(with the area located between the CT and the circuit breaker). This then
fully replicates the scheme up to the open bus coupler CB on both sides.
Application Notes
MiCOM P40 Agile P746
P746/EN AP/J43
(AP) 6-37
If the circuit breaker was open no load current would flow through the circuit breaker. The
differential current in the two main zones would equal zero, as the current flowing into the
zones would still equal the current flowing out.
However, if the circuit breaker is actually closed, the external fault current will flow through
the circuit breaker. The differential current in main zone 1 and in main zone 2 will be equal in
magnitude but opposite in sign. (fault)
When the check zone element is calculated, the differential currents seen in zone 1 and 2,
which result from the discrepancy in the plant status, can be seen to be cancelled out.
Zone 1 Idiff = I1+ I2= idiffZ1 = -ifault > (ID>2 and k2 x IBias)
Zone 2 Idiff = I5+ I6=idiffZ2 = +ifault > (ID>2 and k2 x IBias)
Check zone Idiff = I1+ I2+ I5+ I6=(-ifault) + (+ifault) = 0
Again, the system retains its stability for discrepancies in plant status (even for switch onto
fault).
AP
P746/EN AP/J43
(AP) 6-38
10.3.5
Application Notes
MiCOM P40 Agile P746
CTs on both sides of bus coupler, CB closes before status acquisition.
Figure 18: CTs on both sides of bus coupler, CB closes before status acquisition
As the CB has closed but the status has not yet been refreshed the topology still believes the
CB to be open.
AP
Treating this as an open bus coupler the topology algorithm will have extended the two
zones with the areas located between the CTs and the circuit breaker. These then fully
replicate the scheme up to the open bus coupler CB on both sides.
If the circuit breaker was open no load current would flow through the circuit breaker. The
differential current in the two main zones would equal zero, as the current flowing into the
zones would still equal the current flowing out.
However, if the circuit breaker is actually closed, the external fault current will flow through
the circuit breaker. The differential current in the two main zones will be equal in magnitude
but opposite in sign. (ifault)
When the check zone element is calculated, the differential currents seen in the two main
zones, which result from the discrepancy in the plant status and which are taken into account
for the check zone calculation, can be seen to be cancelled out.
Zone 1 Idiff = I1+ I2= idiffZ1 = -ifault > (ID>2 and k2 x IBias)
Zone 2 Idiff = I5+ I6=idiffZ2 = +ifault > (ID>2 and k2 x IBias)
Check zone Idiff = I1+ I2+ I5+ I6=(-ifault) + (+ifault) = 0
Therefore, the system retains its stability even when there are discrepancies in plant status.
Application Notes
MiCOM P40 Agile P746
10.3.6
P746/EN AP/J43
(AP) 6-39
CTs on one side of bus coupler, CB closed and fault evolves between CT and CB (even for
switch onto fault).
Figure 19: CTs on one side of bus coupler, CB closed and fault occurs between the
CB & the CT
Treating this as a closed bus section circuit breaker the topology algorithm will have
extended the limits of the main zones to the bus coupler CT. This then fully replicates the
scheme.
Under normal operating conditions when the circuit breaker is closed load current would flow
through the circuit breaker and differential current in the two main zones would equal zero,
as the current flowing into the zones would still equal the current flowing out.
However, if a fault occurs between the CT and the circuit breaker, the current will flow from
zone 1 into zone 2 which feeds the fault. The differential current in main zone 1 will still equal
zero, as the current flowing into the zone 1 will still equal the current flowing out, but the
differential current measured in zone 2 will be equal to that of the fault current.
In this case zone 2 would operate as will the check zone element.
Zone 1 Idiff = I1+ I2+ I3= idiffZ1 = 0
Zone 2 Idiff = I3+ I5+ I6=idiffZ2 = ifault > (ID>2 and k2 x IBias)
Check zone Idiff = I1+ I2+ I5+ I6= idiffZ2 = ifault > (IDCZ>2 and kCZ x IBias)
However, when zone 2 trips the fault will still be present. The topology then analyses the
remainder of the system as follows.
Figure 20: Zone 2 tripped, fault still present
Treating this as an open bus coupler circuit breaker as before the topology algorithm will
have extended zone 1 with the area located between the CT and the circuit breaker. This
then fully replicates the scheme up to the open bus coupler CB. Remember that in this
AP
P746/EN AP/J43
(AP) 6-40
Application Notes
MiCOM P40 Agile P746
example zone 2’s limit extended up to the circuit breaker but this zone has been tripped
already.
The circuit breaker is now open and the fault current would flow to feed the fault. The
differential current in the main zone 2 would equal zero, as the current is flowing into zone 1
whereas the current measured will be equal to the fault current ifault.
Zone 2 Idiff = I5+ I6= idiffZ2 = 0
Zone 1 Idiff = I1+ I2=idiffZ1 = ifault > (ID>2 and k2 x IBias)
Check zone Idiff = I1+ I2+ I5+ I6=idiffZ1 = ifault > (IDCZ>2 and kCZ x IBias)
Hence, the system reacts to the continuing presence of the fault and trips the zone 1 as the
check zone Idiff > (IDCZ>2 and kCZ x IBias) and the zone Idiff > (ID>2 and k2 x IBias).
In this example it can be seen that the opposite zone is tripped first but the dynamic topology
reacts to the changed scheme and subsequently trips the adjacent main zone.
10.3.7
CTs on both sides of coupler, CB closed and fault evolves between CT and CB.
AP
Figure 21: CTs on both sides of bus coupler, CB closed fault occurs between A CT &
the CB
Treating this as a closed bus section circuit breaker the topology algorithm will have created
an overlapped zone that surrounds the circuit breaker with the bus coupler CTs as its limits
made by zone 1 and 2. This then fully replicates the scheme.
Under normal operating conditions when the circuit breaker is closed load current would flow
through the circuit breaker and hence both zones. The differential current in the two main
zones would equal zero, as the current flowing into the zones would still equal the current
flowing out.
However, if a fault was to occur in the overlapped zone, current would flow into both zones
and feed the fault. The differential current in the two main zones will be equal to that of the
fault current.
The main zones would operate. When the check zone element is calculated, the differential
current which results from the presence of the fault in the coupler, will confirm the presence
of a fault and initiate a simultaneous trip of both main.
Application Notes
MiCOM P40 Agile P746
P746/EN AP/J43
(AP) 6-41
(1) Hence, the system reacts to a fault occurring between the CT and the CB simultaneously
tripping both zones.
Zone 1 Idiff = I1+ I2+ I4=idiffZ1 = ifault > (ID>2 and k2 x IBias)
Zone 2 Idiff = I3+ I5+ I6= idiffZ2 = ifault > (ID>2 and k2 x IBias)
Check zone Idiff = I1+ I2+ I5+ I6=idiffZx = ifault
AP
P746/EN AP/J43
Application Notes
(AP) 6-42
11
MiCOM P40 Agile P746
NUMERICAL DIFFERENTIAL BUSBAR PROTECTION PROJECT
This light Engineering can be done by anyone.
The substation construction will influence the protection scheme installed. It is advisable that
a scheme evaluation is conducted as soon as possible, preferably at the same time as the
definition of the equipment specification.
11.1
One or Three Box Mode Selection
A P746 embeds 18 current inputs and can be connected to 6 three phase CTs or 18 single
phase CTs.
A P746 embeds 3 voltage inputs.
P746 mode selection
Single bus or radial bus with no CT coupling (1 zone)
Set of CTs
Up to 6
Up to 18
Set of VTs
0 or 1
0 or 1
Mode
One box mode
3 boxes mode
Radial bus with 1 or 2 CT coupling (2 zones)
Set of CTs
AP
Up to 6
Up to 12
Up to 18
Up to 36
Set of VTs
0 or 1
0 to 2
0 or 2
0 to 2
Mode
One box mode
One box
mode
3 boxes mode
3 boxes
mode
Note
2 sets of
2 sets of
Double bus with no transfer bus (2 zones)
Set of CTs
Up to 6
Up to 6
Up to 18
Up to 18
Set of VTs
0 or 1
0 to 2
0 or 1
0 or 2
Mode
One box mode
3 boxes
mode
3 boxes mode
3 boxes
mode
One & half breaker (2 zones)
Set of CTs
Up to 6
Up to 6
Up to 12
Up to 18
Up to 18
Up to 36
Set of VTs
0 or 1
2
0 to 1
0 or 1
0 or 2
0 to 2
Mode
One box mode 3 boxes
mode
One box
mode
3 boxes mode
3 boxes
mode
3 boxes
mode
1 sets of
2 sets of
Note
2 sets of
Double bus with transfer bus or Triple bus (3 zones)
NOT POSSIBLE
Three buses (3 zones) or Four buses (4 zones), etc…
POSSIBLE if can be split in simpler bus topology.
Application Notes
P746/EN AP/J43
MiCOM P40 Agile P746
(AP) 6-43
4 buses example:
This scheme can be protected by 2 sets of 3 P746 connected as shown below:
Double busbar with bus couplers and bus ties
AP
4 Zones
Maximum of 28 Feeders
36 CTs and Breakers and 64 isolators
(option 4 VTs)
P0847ENc
The trip information must be shared among the 2 sets of 3 P746 with high speed contact to
the filtered or via goose messages with IEC 61850-8.1.
Note:
The P746 connected on the neutral does not allow sensitive
differential earth fault protection.
P746/EN AP/J43
Application Notes
(AP) 6-44
MiCOM P40 Agile P746
11.2
Application Solutions
11.2.1
1 Box Mode:
All analogue inputs, all digital inputs and all relay outputs are connected to one P746:
1 box Application cabling
3 Phase
P0848ENc
11.2.2
3 Box Mode:
Each phase inputs, all digital inputs and all relay outputs are connected to one P746:
3 box Application cabling
Ph C
Ph B
AP
Ph A
Ph A
Ph B
Ph C
P0849ENc
Application Notes
P746/EN AP/J43
MiCOM P40 Agile P746
11.2.3
(AP) 6-45
Voltage Information
When the 3 boxes mode is set, voltage information (based on set criteria) must be shared
among the 3 P746.
Voltage information must be shared
1 P746 per CT phase
P0850ENc
The information to be shared is the voltage algorithm output that allows the trip.
There are two DDBs outputs:
• VT Check Allow Zone 1
• VT Check Allow Zone 2
• To be linked (inverted) to two DDBs inputs:
• Block Bus Diff Zone 1
• Block Bus Diff Zone 2
AP
P746/EN AP/J43
(AP) 6-46
Application Notes
MiCOM P40 Agile P746
• the blocking information has to be sent from the connected P746 to the other ones
with the following methods:
Goose messages with IEC 61850-8.1 (recommended):
AP
Application Notes
P746/EN AP/J43
MiCOM P40 Agile P746
(AP) 6-47
High speed contact to filtered optos:
AP
Note:
the tripping time is delayed by around.
Standard relay: 5 ms + opto filtering: 5 ms = 10 ms
High break/high speed relay: 0ms + opto filtering: 5 ms = 5 ms
P746/EN AP/J43
Application Notes
(AP) 6-48
MiCOM P40 Agile P746
high speed contact to unfiltered optos
AP
Note:
the tripping time is delayed by around 5 ms for Standard relay.
Application Notes
P746/EN AP/J43
MiCOM P40 Agile P746
11.2.4
(AP) 6-49
3 Boxes Mode with Simple Redundancy
When redundancy is needed, an alternative solution of doubling the number of P746 (i.e. 6
P746) is to add a forth one measuring the neutral path.
Any phase to ground fault will be seen by a phase P746 and the neutral P746 and any phase
to phase fault will be seen by two phase P746.
By wiring the trip outputs in parallel, any fault would be cleared even if one P746 fails.
3 box + 1 box Application cabling
simplified redundancy
Ph C
Ph B
Ph A
Ph A
Ph B
Ph C
AP
Neutral
P0851ENbc
11.2.5
2 out of 2 Solution
Using the same principle for the 2 out of 2 solution, the following cabling can be done:
Ph C
Ph B
Ph A
3 box + 1 box Trip order cabling
2 out of 2 tripping logic
Ph A
+ Vcc
Trip PhA
Ph B
Trip PhB
Trip PhC
Trip PhN
A&B
A&C
Ph C
A&N
B&C
Neutral
B&N
C&N
3 Phase Trip
P0852ENc
P746/EN AP/J43
Application Notes
(AP) 6-50
11.3
MiCOM P40 Agile P746
Check List
The following steps shall be performed:
Engineering phase:
1.
Check the CT compliances
(using P746 VkTest.xls & Rct_Approx.xls)
AP
2.
Design the Junction schemes
(using AUTOCAD (or equivalent))
3.
Create the material definition and the wiring plans
(distributed or centralised version)
4.
Label the relay Inputs & Outputs
(using MiCOM S1 Agile Setting (per Group))
5.
Calculate the P746 87BB settings
(using Idiff_Ibias.xls & P746 setting guide)
6.
Calculate the different other P746 settings
(transformer, coupler, line, etc…)
7.
Draw the topology line diagram (optional but to use the P746 remote HMI)
(using P746 Remote HMI Tips)
8.
Create the P746 PSL file
(using MiCOM S1 Agile & Tips)
9.
Print out the front panel Labels
(using P74x_Stickers.xls)
Testing phase:
1.
Stick the labels on the front of the P746
2.
Download the complete setting files into the relay(s)
(using MiCOM S1 Agile)
3.
Download the PSL file into the relay(s)
(using MiCOM S1 Agile)
4.
Test the PSLs & Analogue inputs
(using a Inputs / Outputs and current generator)
5.
Test the relay
(using MiCOM S1 Agile)
Commissioning phase:
1.
Check the inputs / outputs
2.
Check CT connections
3.
Check the measurements and the tripping slopes
(see documentation)
Application Notes
P746/EN AP/J43
MiCOM P40 Agile P746
11.4
(AP) 6-51
General Substation Information
Only a few system parameters are required and it is vital that these are included.
• Number of feeders, bus couplers, bus sections
• Positions of bus sections
• Positions of switchgear plant i.e. circuit breakers, isolators
• Positions of CTs (including the polarity (P1/P2 – S1/S2))
• Planned future extensions with circuit breaker, isolator and current transformer (CT)
• Type of electrical network earthing (Solid or impedance)
11.5
Short Circuit Levels
Maximum external fault current (phase to phase and phase to ground faults)
• Solid:
- Minimum two phase busbar fault current
- Minimum load current on the smallest feeder
- Maximum load current on the biggest feeder or coupler
- Optional: Maximum three phase busbar fault current
• With impedance:
- Minimum two phase busbar fault current
- Minimum single phase to earth busbar fault current
- Minimum load current on the smallest feeder
- Maximum load current on the biggest feeder
- Optional: Maximum three phase busbar fault current
Maximum substation short-circuit withstand time
11.6
Switchgear
• Nominal CT ratio
AP
P746/EN AP/J43
(AP) 6-52
11.7
Application Notes
MiCOM P40 Agile P746
Substation Architecture
Due to the flexibility of the differential busbar protection there is a number of busbar
configurations that can be accommodated via the topology. Each may have very different
architecture and, therefore, vary in complexity.
You will find in the following pages topology examples of layouts most frequently
encountered. For each example, the number of P746 necessary to protect the busbars is
specified.
Generally, the elements of the protection architecture will be identified in a similar manner to
the principal parts of the substation e.g. by the letters A and B.
AP
Application Notes
P746/EN AP/J43
MiCOM P40 Agile P746
12
(AP) 6-53
STANDARD CONFIGURATIONS
The following information relates only to the more common standard schemes. For further
information on the accommodation of other busbar configurations consult your General
Electric representative.
Here after is summarised the solution identification:
P746 mode selection
Single bus or radial bus with no CT coupling (1 zone)
Set of CTs
Up to 6
Up to 18
Set of VTs
0 or 1
0 or 1
Mode
One box mode
3 boxes mode
Radial bus with 1 or 2 CT coupling (2 zones)
Set of CTs
Up to 6
Up to 12
Set of VTs
0 or 1
0 to 2
0 or 2
0 to 2
Mode
One box mode
One box
mode
3 boxes mode
3 boxes
mode
Note
Up to 18
Up to 36
2 sets of
2 sets of
Double bus with no transfer bus (2 zones)
Set of CTs
Up to 6
Up to 6
Up to 18
Up to 18
Set of VTs
0 or 1
0 to 2
0 or 1
0 or 2
Mode
One box mode
3 boxes
mode
3 boxes mode
3 boxes
mode
AP
One & half breaker (2 zones)
Set of CTs
Up to 6
Up to 6
Up to 12
Up to 18
Up to 18
Up to 36
Set of VTs
0 or 1
2
0 to 1
0 or 1
0 or 2
0 to 2
Mode
One box mode
3 boxes
mode
One
mode
3 boxes mode
3 boxes
mode
3 boxes
mode
1 sets of
2 sets of
Note
box
2 sets of
Double bus with transfer bus or Triple bus (3 zones)
NOT POSSIBLE
Three buses (3 zones) or Four buses (4 zones), etc…
POSSIBLE if can be split in simpler bus topology.
The general rule to calculate the number of P746 to use is:
1 off P746 from 1 to 6 sets of CTs or 6 breakers (up to 7 isolators) and 2 sets of 1 P746 up to
12 sets of CTs when possible.
3 off P746 from 7 to.18 sets of CTs or 18 breakers (up to 37 isolators) and 2 sets of 3 P746
up to 36 sets of CTs when possible.
P746/EN AP/J43
(AP) 6-54
Application Notes
MiCOM P40 Agile P746
Figure 22: Single busbar application with bus section isolator
The above example shows a single busbar with a bus section isolator. It is split into two
zones.
There are up to 6 feeders connected to the busbar. This configuration requires 1 P746.
AP
If it was up to 18 feeders connected to the busbar. This configuration would require 3 P746.
There is no solution for more feeders.
The type of P746 used will depend on the i/o requirements of the scheme in question.
Figure 23: Single busbar application with bus section circuit breaker
The above example shows a single busbar with a bus section circuit breaker. It is split into
two zones.
There are 4 feeders connected to the busbar. The bus section circuit breaker has CTs on
either side. This configuration requires 1 P746.
If it was up to 10 feeders connected to the busbar. This configuration would require 2 sets of
1 P746 or 3 P746.
Application Notes
MiCOM P40 Agile P746
P746/EN AP/J43
(AP) 6-55
If it was up to 14 feeders connected to the busbar. This configuration would require 3 P746.
AP
If it was up to 34 feeders connected to the busbar. This configuration would require 2 sets of
3 P746.
The type of P746 used will depend on the i/o requirements of the scheme in question.
It is recommended that the CTs for feeder protection are sited such as to overlap with the
CTs defining the limits of each busbar protection zone.
P746/EN AP/J43
(AP) 6-56
Application Notes
MiCOM P40 Agile P746
Figure 24: Breaker and a half scheme
The above example shows a breaker and a half scheme.
There are 3 feeders connected to each busbar. This configuration requires 1 P746
AP
If it was up to 12 feeders connected to the busbars, the scheme would require 2 sets of 1
P746 or 3 P746.
If it was up to 18 feeders connected to the busbars, the scheme would require 3 P746.
If it was up to 36 feeders connected to the busbars. Each scheme would require 3 P746.
The type of P746 used will depend on the i/o requirements of the scheme in question.
Figure 25: Double Busbar application with bus coupler
The above example shows a double busbar with a bus coupler. It is split into two zones.
If there is a bus coupler with a single CT (solution 1) and up to 5 feeders connected to the
busbar. This configuration requires 1 P746.
If there is a bus coupler with CTs on both sides (solution 2) and 4 feeders connected to the
busbar. This configuration requires 1 P746.
If there is a bus coupler with a single CT (solution 1) and up to 17 feeders connected to the
busbar. This configuration requires 3 P746.
If there is a bus coupler with CTs on both sides (solution 2) and 16 feeders connected to the
busbar. This configuration requires 3 P746.
Application Notes
P746/EN AP/J43
MiCOM P40 Agile P746
(AP) 6-57
The additional P746 being for the bus section isolators is optional.
The number of additional P746 being dependant on the number of bus section/bus coupler
CTs. The type of P746 used for each bay will depend on the i/o requirements of the bay in
question.
P746
P746
P746
P746
P746
P746
P0883ENa
Figure 26: Double bus bar with two circuit breakers per feeder
AP
P746/EN AP/J43
Application Notes
(AP) 6-58
13
MiCOM P40 Agile P746
APPLICATION OF NON PROTECTION FUNCTIONS
The non-protection features for the scheme are summarised below:
• Scheme is centralised.
• Local, zone and scheme measurements – various measurements are available locally
via the relay LCD or remotely via the serial communication link.
• Event, fault and disturbance recording – Comprehensive post fault analysis available
via event lists, disturbance records and fault records which can be accessed locally
via the relay LCD or remotely via the serial communication link.
• Real time clock/time synchronisation – Time synchronisation available via IRIG-B
input.
• Four settings groups – Independent remotely selectable setting groups to allow for
customer specific applications.
• CB and isolator state monitoring – indication of the circuit breaker/isolator position via
the auxiliary contacts, scheme acts accordingly should discrepancy conditions be
detected.
• Commissioning test facilities.
• Continuous self monitoring – extensive self checking routines to ensure maximum
reliability.
• Graphical programmable scheme logic – allowing user defined protection and control
logic to be tailored to the specific application.
AP
13.1
Function Keys
The following default PSL logic shows the programming of function keys to enable/disable
the commissioning mode functionality.
Figure 27: Commissioning mode default PSL
Note:
Energizing two inputs to an LED conditioner creates a YELLOW illumination.
Function Key 2 is set to Toggle mode and on activation of the key, the commissioning mode
will be in service as long as the function has been enabled in the CONFIGURATION menu.
The associated LED will indicate the state of the protection function in service as GREEN
and RED for the Overhaul mode.
Application Notes
P746/EN AP/J43
MiCOM P40 Agile P746
(AP) 6-59
14
CT REQUIREMENTS
14.1
Notation
IF max fault
maximum fault current (same for all feeders) in A
IF max
cont
maximum contribution from a feeder to an internal fault (depends on the
feeder) in A
int
Inp
CT primary rated current
In
nominal secondary current (1A or 5A)
RCT
CT secondary winding Resistance in Ohms
RB
Total external load resistance in Ohms
Vk
CT knee point voltage in Volts
SVA
Nominal output in VA
Short-circuit current coefficient (generally 20)
KSSC
General recommendations for the specification of protection CTs use common rules of
engineering which are not directly related to a particular protection.
14.2
87BB Phase CT Requirements
14.2.1
Feeders connected to sources of significant power (i.e. lines and generators)
The primary rated current is specified above a 1/20th of the maximum contribution of the
feeder to internal faults.
i.e.
Inp = IF max int/20
e.g. A power line likely to import electricity at 20 kA gives rated primary current Inp as
1000 A.
In any case the maximum peak current shall be less than 90 In (90A for 1A input and 450A
for 5A Input) i.e. 32 In RMS fully offset.
This recommendation is used for the majority of line or transformer protection applications.
The CT must be sized so as not to saturate during internal faults:
For each CT, IFeederMax = maximum contribution of the feeder to an internal fault (could be
different for each feeder):
Vk > IFeederMax * (RCT + RB)
Note:
This specification is valid for internal faults.
AP
P746/EN AP/J43
Application Notes
(AP) 6-60
14.2.2
MiCOM P40 Agile P746
CT Specification according to IEC 185, 44-6 and BS 3938 (British Standard)
1.
Class X according to British Standard: Minimum knee point voltage for saturation
Vk min = secondary IF max x (RCT + RB)
With secondary IF max not less than 20 (if IF max < 20 In then IF max = 20)
Note:
This specification is valid for external faults.
This provides a sufficient margin of security for CT saturation immunity.
2.
Class 5P to IEC 185. Conversion of class X (BS) with the 5P equivalent (IEC)
3.
Class TPX and TPY according to IEC 44-6. IEC defines a composite error as a
percentage of a multiple of the rated current (IN) on a definite load SVA.
e.g.
CT 1000/5 A – 50VA 5P 20 [CT Inp / InA – SVA Accuracy P Kscc]
This definition indicates that the composite error must be lower than 5%, for a primary
current of 20Inp when the external load is equal to 2 ohms (50 VA to In). If secondary
resistance, RCT, is known it is easy to calculate the magnetising EMF developed with the
fault current (20In). Actually if the error is 5% (= 5A) with this EMF, the point of operation is
beyond the knee point voltage for saturation. By convention one admits that the knee point
voltage, Vk, is 80% of this value. For a conversion between a class 5P (IEC) and a class X
(BS) CT one uses the relation:
Vk=0.8 X [(SVA x Kssc)/In + (RCT x Kssc x In) ]
AP
SVA = (In x Vk/0.8 Kssc) – RCT x In2
In particular cases, calculation could reveal values too low to correspond to industrial
standards. In this case the minima will be: SVA min = 10 VA 5P 20 which correspond to a
knee point voltage of approximately Vkmin = 70 V at 5A or 350 V at 1A. Class TPY would
permit lower values of power, (demagnetisation air-gap). Taking into account the weak
requirements of class X or TPX one can keep specifications common.
For accuracy, class X or class 5P current transformers (CTs) are strongly recommended.
The knee point voltage of the CTs should comply with the minimum requirements of the
formulae shown below.
Vk
≥
k (RCT + RB)
Where:
Vk
=
Required knee point voltage
k
=
Dimensioning factor
RCT
=
CT secondary resistance
RL
=
Circuit resistance from CT to relay
RB
=
Burden resistance
k is a constant depending on:
If
=
Maximum value of through fault current for stability (multiple of In)
X/R
=
Primary system X/R ratio (for the P746 system, X/R up to 120)
The following CT requirement can be developed for the P746 scheme
Vk
>
secondary If max x (RCT + RB)
With RB = 2 RL
Application Notes
P746/EN AP/J43
MiCOM P40 Agile P746
14.3
(AP) 6-61
Support of IEEE C Class CTs
MiCOM Px40 series protection is compatible with ANSI/IEEE current transformers as
specified in the IEEE C57.13 standard. The applicable class for protection is class “C”, which
specifies a non air-gapped core. The CT design is identical to IEC class P, or British
Standard class X, but the rating is specified differently. The following table allows C57.13
ratings to be translated into an IEC/BS knee point voltage.
IEEE C57.13 – “C” Classification (volts)
CT Ratio
RCT (ohm)
100/5
200/5
400/5
800/5
1000/5
1500/5
2000/5
3000/5
0.04
0.8
0.16
0.32
0.4
0.6
0.8
1.2
C50
Vk
56.5
60.5
68.5
84.5
92.5
112.5
132.5
172.5
C100
Vk
109
113
121
137
145
165
185
225
C200
Vk
214
218
226
242
250
270
290
330
C400
Vk
424
428
436
452
460
480
500
540
C800
Vk
844
848
856
872
880
900
920
960
Assumptions:
4. For 5A CTs, the typical resistance is 0.0004 ohm secondary per primary turn (for 1A
CTs, the typical resistance is 0.0025 ohm secondary per primary turn).
5. IEC/BS knee is typically 5% higher than ANSI/IEEE knee.
Given:
6. IEC/BS knee is specified as an internal EMF, whereas the “C” class voltage is
specified at the CT output terminals. To convert from ANSI/IEEE to IEC/BS requires
the voltage drop across the CTs secondary winding resistance to be added.
7. IEEE CTs are always rated at 5A secondary
8. The rated dynamic current output of a “C” class CT (Kssc) is always 20 x In
Vk
Where:
Vk
= (C x 1.05) + (In. RCT. Kssc)
= Equivalent IEC or BS knee point voltage
C
= C Rating
In
= 5A
RCT
= CT secondary winding resistance
Kssc = 20 times
AP
P746/EN AP/J43
Application Notes
(AP) 6-62
15
MiCOM P40 Agile P746
AUXILIARY SUPPLY FUSE RATING
In the safety section of this manual, the maximum allowable fuse rating of 16A is quoted. To
allow time grading with fuses upstream, a lower fuselink current rating is often preferable.
Use of standard ratings of between 6A and 16A is recommended. Low voltage fuselinks,
rated at 250V minimum and compliant with IEC60269-2 general application type gG are
acceptable, with high rupturing capacity. This gives equivalent characteristics to HRC "red
spot" fuses type NIT/TIA often specified historically.
The table below recommends advisory limits on relays connected per fused spur. This
applies to MiCOM Px40 series devices with hardware suffix C and higher, as these have
inrush current limitation on switch-on, to conserve the fuse-link.
Maximum Number of MiCOM Px40 Relays Recommended Per Fuse
Battery Nominal Voltage
24 to 54 V
60 to 125 V
138 to 250 V
6A
2
4
6
10A Fuse
4
8
10
15 or 16A Fuse
6
12
16
Fuse Rating > 16A
Not permitted
Not permitted
Not permitted
Alternatively, miniature circuit breakers (MCB) may be used to protect the auxiliary supply
circuits.
AP
Programmable Logic
P746/EN PL/J43
MiCOM P40 Agile P746
(PL) 7-1
PL
PROGRAMMABLE LOGIC
Hardware Suffix:
M
Software Version:
91
P746/EN PL/J43
(PL) 7-2
PL
Programmable Logic
MiCOM P40 Agile P746
Programmable Logic
MiCOM P40 Agile P746
P746/EN PL/J43
(PL) 7-3
CONTENTS
1
PROGRAMMABLE EDITOR
5
1.1
Overview
5
1.2
Loading Schemes from Files
5
1.3
How to use Px40 PSL Editor
5
1.4
Warnings
5
2
PSL EDITOR TOOLBAR
7
2.1
Logic Symbols
7
3
LOGIC SIGNALS PROPERTIES
9
3.1
Link Properties
9
3.2
Opto Signal Properties
9
3.3
Input Signal Properties
9
3.4
Output Signal Properties
10
3.5
GOOSE Input Signal Properties
10
3.6
GOOSE Output Signal Properties
10
3.7
Control In Signal Properties
10
3.8
InterMiCOM In Command Properties
10
3.9
InterMiCOM Out Command Properties
11
3.10
Function Key Properties
11
3.11
Fault Recorder Trigger Properties
11
3.12
LED Signal Properties
11
3.13
Contact Signal Properties
11
3.14
LED Conditioner Properties
11
3.15
Contact Conditioner Properties
12
3.16
Timer Properties
12
3.17
Gate Properties
12
3.18
Descriptions of Logic Nodes
14
3.19
Default PSL
22
3.20
Logic Input Mapping
22
3.21
Relay Output Contact Mapping
23
3.22
Function Key Input Mapping
24
3.23
Programmable LED Output Mapping
24
3.24
Fault Recorder Start Mapping
26
3.25
PSL Scheme Version Control
26
4
VIEWING AND PRINTING PSL DIAGRAMS
27
PL
P746/EN PL/J43
(PL) 7-4
PL
Programmable Logic
MiCOM P40 Agile P746
Programmable Logic
MiCOM P40 Agile P746
1
PROGRAMMABLE EDITOR
1.1
Overview
P746/EN PL/J43
(PL) 7-5
The Programmable Scheme Logic (PSL) is a module of programmable logic gates and
timers in the relay, which can be used to create customised internal logic. This is done by
combining the relays's digital inputs with internally generated digital signals using logic gates
and timers, then mapping the resultant signals to the relays's digital outputs and LEDs.
The Programmable Scheme Logic (PSL) Editor allows you to create and edit scheme logic
diagrams to suit your own particular application.
1.2
Loading Schemes from Files
The product is shipped with default scheme files. These can be used as a starting point for
changes to a scheme. To create a new blank scheme, select File then New then 'Blank
scheme... to open the default file for the appropriate IED. This deletes the diagram
components from the default file to leave an empty diagram but with the correct configuration
information loaded.
1.3
How to use Px40 PSL Editor
With the Px40 PSL Module you can:
•
Start a new PSL diagram
•
Extract a PSL file from a Px40 IED
•
Open a diagram from a PSL file
•
Add logic components to a PSL file
•
Move components in a PSL file
•
Edit link of a PSL file
•
Add link to a PSL file
•
Highlight path in a PSL file
•
Use a conditioner output to control logic
•
Download PSL file to a Px40 IED
•
Print PSL files
See the S1 Agile program online help or ‘MiCOM P40 Agile Modular and Compact Ranges,
Settings Application Software User Guide’, P40-M&CR-UG for more detailed information on
how to use these functions.
1.4
Warnings
Checks are made before a scheme is downloaded to the relay. Various warning messages
may be displayed as a result of these checks.
In most cases, the model number of the unit will match that of the model number stored in
the PSL software on the PC. The Editor first reads in the model number of the connected
unit, then compares it with its stored model number using a "wildcard" comparison. If a
model mismatch occurs, a warning is generated before sending starts. Both the stored
model number and the number read from the IED are displayed with the warning.
It is up to the user to decide whether the settings to be downloaded are compatible, and to
be aware that incompatible settings could lead to undesirable behavior of the unit.
If there are any potential problems of an obvious nature then a list will be generated. The
types of potential problems that the program attempts to detect are:
PL
P746/EN PL/J43
(PL) 7-6
PL
Programmable Logic
MiCOM P40 Agile P746
•
One or more gates, LED signals, contact signals, and/or timers have their outputs linked
directly back to their inputs. An erroneous link of this sort could lock up the relay or
cause other more subtle problems to arise.
•
Inputs to Trigger (ITT) exceeds the number of inputs. A programmable gate has its ITT
value set to greater than the number of actual inputs; the gate can never activate. Note
that there is no lower ITT value check. A 0-value does not generate a warning.
•
Too many gates. There is a theoretical upper limit of 256 gates in a scheme, but the
practical limit is determined by the complexity of the logic. In practice the scheme would
have to be very complex, and this error is unlikely to occur.
•
Too many links. There is no fixed upper limit to the number of links in a scheme.
However, as with the maximum number of gates, the practical limit is determined by the
complexity of the logic. In practice the scheme would have to be very complex, and this
error is unlikely to occur.
Programmable Logic
P746/EN PL/J43
MiCOM P40 Agile P746
2
(PL) 7-7
PSL EDITOR TOOLBAR
There are a number of toolbars available for easy navigation and editing of PSL.
−
−
Toolbar
Description
Standard tools: For file management and
printing
Alignment tools: To snap logic elements
into horizontally or vertically aligned
groupings
Drawing tools : To add text comments and
other annotations, for easier reading of
PSL schemes
Nudge tools: To move logic elements
Rotation tools: Tools to spin, mirror and flip
Structure tools: To change the stacking
order of logic components
Zoom and pan tools: For scaling the
displayed screen size, viewing the entire
PSL, or zooming to a selection
2.1
Logic Symbols
The logic symbol toolbar provides icons to place each type of logic element into the scheme
diagram. Not all elements are available in all devices. Icons will only be displayed for those
elements available in the selected device.
−
Symbol
−
Function
−
Explanation
Link
Create a link between two logic symbols
Opto Signal
Create an opto signal
Input Signal
Create an input signal
Output Signal
Create an output signal
GOOSE In
Create an input signal to logic to receive a GOOSE message
transmitted from another IED. Used in either UCA2.0 or IEC
61850 GOOSE applications only
GOOSE Out
Create an output signal from logic to transmit a GOOSE
message to another IED. Used in either UCA2.0 or IEC
61850 GOOSE applications only.
Control In
Create an input signal to logic that can be operated from an
external command.
InterMiCOM In
Create an input signal to logic to receive an InterMiCOM
command transmitted from another IED.
InterMiCOM Out
Create an output signal from logic to transmit an InterMiCOM
command to another IED.
Function Key
Create a function key input signal.
Trigger Signal
Create a fault record trigger
LED Signal
Create an LED input signal that repeats the status of tri-color
LED
Contact Signal
Create a contact signal
LED Conditioner
Create an LED conditioner
PL
P746/EN PL/J43
Programmable Logic
(PL) 7-8
MiCOM P40 Agile P746
−
Symbol
−
−
Function
Contact Conditioner
Create a contact conditioner
Timer
Create a timer
AND Gate
Create an AND Gate
OR Gate
Create an OR Gate
Explanation
Programmable Gate Create a programmable gate
SR latch
PL
Create an SR late gate
Programmable Logic
MiCOM P40 Agile P746
3
P746/EN PL/J43
(PL) 7-9
LOGIC SIGNALS PROPERTIES
1. Use the logic toolbar to select logic signals. This is enabled by default but to hide or
show it, select View then Logic Toolbar.
2. Zoom in or out of a logic diagram using the toolbar icon or select View then Zoom
Percent.
3. Right-click any logic signal and a context-sensitive menu appears.
Certain logic elements show the Properties option. If you select this, a Component
Properties window appears. The contents of this window and the signals listed will vary
according to the logic symbol selected. The actual DDB numbers are dependent on the
model and are provided in the DDB signals table.
3.1
Link Properties
Links form the logical link between the output of a signal, gate or condition and the input to
any element. Any, which is connected to the input of a gate, can be inverted. To do this:
1. Right-click the input
2. Select Properties…. The Link Properties window appears.
3. Check the box to invert the link. Or uncheck for a non-inverted link
An inverted link is shown with a small circle on the input to a gate. A link must be connected
to the input of a gate to be inverted.
Links can only be started from the output of a signal, gate, or conditioner, and must end at
an input to any element.
Signals can only be an input or an output. To follow the convention for gates and
conditioners, input signals are connected from the left and output signals to the right. The
Editor automatically enforces this convention.
A link is refused for the following reasons:
• There has been an attempt to connect to a signal that is already driven. The
reason for the refusal may not be obvious because the signal symbol may appear
elsewhere in the diagram. In this case you can right-click the link and select
Highlight to find the other signal. Click anywhere on the diagram to disable the
highlight.
• An attempt has been made to repeat a link between two symbols. The reason for
the refusal may not be obvious because the existing link may be represented
elsewhere in the diagram.
3.2
Opto Signal Properties
Each opto input can be selected and used for programming in PSL. Activation of the opto
input will drive an associated DDB signal.
For example, activating opto input L1 will assert DDB 032 in the PSL.
3.3
Input Signal Properties
Relay logic functions provide logic output signals that can be used for programming in PSL.
Depending on the relay functionality, operation of an active relay function will drive an
associated DDB signal in PSL.
For example, DDB 261 will be asserted in the PSL should the active earth fault 1, stage 1
protection operate/trip.
PL
P746/EN PL/J43
(PL) 7-10
3.4
Programmable Logic
MiCOM P40 Agile P746
Output Signal Properties
Relay logic functions provide logic input signals that can be used for programming in PSL.
Depending on the relay functionality, activation of the output signal will drive an associated
DDB signal in PSL and cause an associated response to the relay function
For example, if DDB 216 is asserted in the PSL, it will block the sensitive earth function
stage 1 timer.
3.5
GOOSE Input Signal Properties
The Programmable Scheme Logic interfaces with the GOOSE Scheme Logic (see S1 users
manual) by means of 32 Virtual inputs. The Virtual Inputs can be used in much the same
way as the Opto Input signals.
The logic that drives each of the Virtual Inputs is contained within the relay’s GOOSE
Scheme Logic file. It is possible to map any number of bit-pairs, from any subscribed device,
using logic gates onto a Virtual Input (see S1 User’s manual for more details).
For example, DDB 832 will be asserted in PSL should virtual input 1 operate.
PL
3.6
GOOSE Output Signal Properties
The Programmable Scheme Logic interfaces with the GOOSE Scheme Logic by means of
32 Virtual outputs.
It is possible to map virtual outputs to bit-pairs for transmitting to any subscribed devices
(see S1 Users manual for more details).
For example, if DDB 865 is asserted in PSL, Virtual Output 32 and its associated mappings
will operate.
3.7
Control In Signal Properties
There are 32 control inputs which can be activated via the relay menu, ‘hotkeys’ or via rear
communications. Depending on the programmed setting i.e. latched or pulsed, an associated
DDB signal will be activated in PSL when a control input is operated.
For example, operate control input 1 to assert DDB 800 in the PSL.
3.8
InterMiCOM In Command Properties
There are 8 EIA(RS)232 InterMiCOM inputs that could be selected and used for
teleprotection. ‘InterMiCOM In’ is a received signal from remote end that could be mapped
to selected output relay or logic input.
For example, InterMiCOM Input 1 is mapped to output relay 1.
Programmable Logic
P746/EN PL/J43
MiCOM P40 Agile P746
3.9
(PL) 7-11
InterMiCOM Out Command Properties
There are 8 EIA(RS)232 InterMiCOM outputs that could be selected and used for
teleprotection. ‘InterMiCOM Out’ is a send command to a remote end that could be mapped
to any logic output or opto input. This signal will be transmitted to the remote end using
protection communication and will appear at the remote end as corresponding ‘InterMiCOM
In’ command.
For example, InterMiCOM Output 1 is mapped to opto input 4.
3.10
Function Key Properties
Each function key can be selected and used for programming in PSL. Activation of the
function key will drive an associated DDB signal and the DDB signal will remain active
depending on the programmed setting i.e. toggled or normal. Toggled mode means the DDB
signal will remain latched or unlatched on key press and normal means the DDB will only be
active for the duration of the key press.
For example, operate function key 1 to assert DDB 712 in the PSL.
3.11
Fault Recorder Trigger Properties
The fault recording facility can be activated, by driving the fault recorder trigger DDB signal.
For example, assert DDB 144 to activate the fault recording in the PSL.
3.12
LED Signal Properties
All programmable LEDs will drive associated DDB signal when the LED is activated.
For example, DDB 652 will be asserted when LED 7 is activated.
3.13
Contact Signal Properties
All relay output contacts will drive associated DDB signal when the output contact is
activated.
For example, DDB 009 will be asserted when output R10 is activated.
3.14
LED Conditioner Properties
1.
2.
3.
4.
5.
6.
Select the LED name from the list (only shown when inserting a new symbol).
Configure the LED output to be Red, Yellow or Green.
Configure a Green LED by driving the Green DDB input.
Configure a RED LED by driving the RED DDB input.
Configure a Yellow LED by driving the RED and GREEN DDB inputs simultaneously.
Configure the LED output to be latching or non-latching.
PL
P746/EN PL/J43
(PL) 7-12
3.15
Programmable Logic
MiCOM P40 Agile P746
Contact Conditioner Properties
Each contact can be conditioned with an associated timer that can be selected for pick up,
drop off, dwell, pulse, pick-up/drop-off, straight-through, or latching operation.
Straight-through means it is not conditioned in any way whereas Latching is used to
create a sealed-in or lockout type function.
To set contact properties,
1.
PL
2.
3.
4.
3.16
Select the contact name from the Contact Name list (only shown when inserting a new
symbol).
Choose the conditioner type required in the Mode tick list.
Set the Pick-up Value (in milliseconds), if required.
Set the Drop-off Value (in milliseconds), if required.
Timer Properties
Each timer can be selected for pick up, drop off, dwell, pulse or pick-up/drop-off operation.
1.
2.
3.
4.
5.
3.17
From the Timer Mode tick list, choose the mode.
Set the Pick-up Value (in milliseconds), if required.
Set the Drop-off Value (in milliseconds), if required.
From the Available timers list (not in all products), choose the timer required. Note:
The timer number will auto-increment when adding timers.
Click OK.
Gate Properties
1.
2.
3.
An AND Gate requires that all inputs are TRUE for the output to be TRUE.
An OR Gate requires that one or more input is TRUE for the output to be TRUE.
A Programmable Gate requires that the number of inputs that are TRUE is equal to or
greater than its Inputs to Trigger setting for the output to be TRUE.
To set gate properties,
1.
2.
3.
4.
Select the gate type: AND Gate, OR Gate, or Programmable Gate.
If you select Programmable Gate, set the number of Inputs to Trigger.
If you want the output of the gate to be inverted, check the Invert Output check box. An
inverted output appears as a "bubble" on the gate output.
Click OK
A Gate may be an AND, OR, programmable gate or SR Latch.
Three variants of the SR latch gate are available. They are:
•
Standard – no input dominant
Programmable Logic
P746/EN PL/J43
MiCOM P40 Agile P746
(PL) 7-13
•
Set Input Dominant
•
Reset Input Dominant
The output of the gate, Q is latched, i.e. its state is non-volatile upon power cycle.
The inversions of the input and output signals are supported.
The state of Q is reset when a new PSL is downloaded to the relay or when the active
setting group is changed. The maximum number of SR Latch gates is 64.
The evaluation of the Q state is carried out after all the DDB changes have completed, i.e. at
the end of the protection cycle and synchronised with protection task. Hence there is an
inherent delay of a protection cycle in processing every one of the SR gates and the delay
increases if the SR gates are connected one after another.
The user has to be aware that if there is a timer before the SR gate, then an additional delay
of a protection cycle will be incurred before the Q state is changed.
The logic operations of the three variants of the gate are depicted in the diagram below:Standard
S
Q
R
S
1
0
0
1
R
0
1
0
1
Q
1
0
no change / last state
no change / last state
PL
Set Input Dominant
SD
Q
R
S
1
0
0
1
R
0
1
0
1
Q
1
0
no change / last state
1
Reset Input Dominant
S
Q
RD
S
1
0
0
1
R
0
1
0
1
Q
1
0
no change / last state
0
P0737ENa
1. Select the Gate type AND, OR, or Programmable.
2. Set the number of inputs to trigger when Programmable is selected.
3. Select if the output of the gate should be inverted using the Invert Output check box. An
inverted output is indicated with a "bubble" on the gate output.
P746/EN PL/J43
Programmable Logic
(PL) 7-14
3.18
MiCOM P40 Agile P746
Descriptions of Logic Nodes
DDB
No.
PL
English Text
Source
Relay Conditioner 1
Description
0
Relay 1
Output Relay 1
31
Relay 32
Relay Conditioner 32
Output Relay 32
64
Opto Input 1
Opto Isolator Input 1
Opto Isolator Input 1
103
Opto Input 40
Opto Isolator Input 40
Opto Isolator Input 40
128
Relay Cond 1
PSL
Relay Conditioner 1
159
Relay Cond 32
PSL
Relay Conditioner 32
192
LED1 Red
PSL
Programmable Tri-LED 1 Red energized
193
LED1 Grn
PSL
Programmable Tri-LED 1 Green energized
206
LED8 Red
PSL
Programmable Tri-LED 8 Red energized
207
LED8 Grn
PSL
Programmable Tri-LED 8 Green energized
208
FnKey LED1 Red
PSL
Programmable function key Tri-LED 1 Red energized
209
FnKey LED1 Grn
PSL
Programmable function key Tri-LED 1 Green energized
226
FnKey LED10 Red
PSL
Programmable function key Tri-LED 10 Red energized
227
FnKey LED10 Grn
PSL
Programmable function key Tri-LED 10 Green energized
256
LED1 Con R
PSL
Assignment of signal to drive output Tri-LED 1 Red
257
LED1 Con G
PSL
Assignment of signal to drive output Tri-LED 1 Green
270
LED8 Con R
PSL
Assignment of signal to drive output Tri-LED 8 Red
271
LED8 Con G
PSL
Assignment of signal to drive output Tri-LED 8 Green
272
FnKey LED1 ConR
PSL
Assignment of signal to drive output FnKey Tri-LED 1
Red
273
FnKey LED1 ConG
PSL
Assignment of signal to drive output FnKey Tri-LED 1
Green
290
FnKey LED10 ConR
PSL
Assignment of signal to drive output FnKey Tri-LED 10
Red
291
FnKey LED10 ConG
PSL
Assignment of signal to drive output FnKey Tri-LED 10
Green
352
Function Key 1
User Control
Function Key 1 is activated.
In ‘Normal’ mode it is high on keypress and in ‘Toggle’
mode remains high/low on single keypress
361
Function Key 10
User Control
Function Key 10 is activated.
In ‘Normal’ mode it is high on keypress and in ‘Toggle’
mode remains high/low on single keypress
384
Timer out 1
Auxiliary Timer 1
Auxiliary Timer out 1
399
Timer out 16
Auxiliary Timer 16
Auxiliary Timer out 16
416
Timer in 1
PSL
Auxiliary Timer in 1
431
Timer in 16
PSL
Auxiliary Timer in 16
450
SG-DDB Invalid
Group Selection
Setting Group selection by DDB inputs invalid
451
CB Status Alarm
CB Status
CB Status Alarm (OR gate of all CB status alarm from
CB1 to CB18 and Bus CB Alm)
465
Prot'n Disabled
OOS ALARM
Protection disabled
466
F out of range
Frequency tracking
Frequency out of range
467
Cct Fail Z1 Alm
BUSBAR Diff
Zone 1 Circuity Fault Alarm
468
Cct Fail Z2 Alm
BUSBAR Diff
Zone 2 Circuity Fault Alarm
469
Cct Fail CZ Alm
BUSBAR Diff
Check Zone Circuity Fault Alarm
475
CT Fail Alarm
CT Supervision
CT Fail Alarm (CT Supervision)
477
VT Fail Alarm
VT Supervision
VT Fail Alarm (VT Supervision)
481
Breaker Fail
CB FAILURE
Breaker Fail Alarm (OR gate of all CB fail (CB1 to CB18,
and BusCB fail)
482
CB Fail Alm T1
CB FAILURE
CB Fail Alarm of Terminal (feeder or coupler) 1
487
CB Fail Alm T6
CB FAILURE
CB Fail Alarm of Terminal (feeder or coupler) 6
Programmable Logic
P746/EN PL/J43
MiCOM P40 Agile P746
DDB
No.
(PL) 7-15
English Text
Source
Description
499
CB Fail Alm T18
CB FAILURE
CB Fail Alarm of Terminal (feeder or coupler) 18
500
CBF Alarm Bus CB
CB FAILURE
CB Fail Alarm of the Bus CB
508
9-2LE Cfg Alarm
NCIT
9-2LE SAV Configuration Alarm
509
Z1 TestMode Alm
Commission Test
Zone 1 in Test Mode Alarm
510
Z2 TestMode Alm
Commission Test
Zone 2 in Test Mode Alarm
511
9-2 Sample Alarm
NCIT
9-2LE SAV Alarm
512
Battery Fail
Self Monitoring
Battery Fail alarm indication
513
Field Volts Fail
Self Monitoring
Relay 48V output Voltage Failure
514
GOOSE IED Absent
UCA2
The IED has not subscribed to a publishing IED
515
NIC Not Fitted
UCA2
Network Interface Card not fitted/failed alarm
516
NIC No Response
UCA2
Network Interface Card not responding alarm
517
NIC Fatal Error
UCA2
Network Interface Card fatal error alarm indication
518
NIC Soft. Reload
UCA2
Network Interface Card software reload alarm
519
Bad TCP/IP Cfg.
UCA2
Bad TCP/IP Configuration Alarm
520
Bad OSI Config.
UCA2
Bad OSI Configuration Alarm
521
NIC Link Fail
UCA2
Network Interface Card link fail alarm indication
522
NIC SW Mis-Match
UCA2
Main card/NIC software mismatch alarm indication
523
IP Addr Conflict
UCA2
IP address conflict alarm indication
532
SNTP failure
UCA2
SNTP sync fail alarm
533
NIC MemAllocFail
UCA2
MMS libraries memory allocation fails
535
PTP Fail Alarm
Ethernet Interface
PTP Failure
537
BBRAM Failure
Self Monitoring
Verify BBRAM
545
Contacts Blocked
PSL
Contacts Blocked Input
546
Block Transdiff
SW
Contacts Blocked Output
548
Block BusDiff Z1
PSL
Block the Differential protection of Zone 1
549
Block BusDiff Z2
PSL
Block the Differential protection of Zone 2
550
Block BusDiff CZ
PSL
Block the Differential protection of the Check Zone
558
Dead Bus Zone 1
SW
Dead Bus Zone 1 Detected
559
Dead Bus Zone 2
SW
Dead Bus Zone 2 Detected
560
VT Chk Allow Z1
SW
VT Check Allow Zone 1 to Trip
561
VT Chk Allow Z2
SW
VT Check Allow Zone 2 to Trip
571
Inhibit CTS
PSL
Inhibit CT Supervision
572
SAV Hold Test
SW
Test state is hold
573
SAV Inhibit Test
SW
Test state is inhibit
574
SAV Alarm Test
SW
Test DDB for sav quality alarm
578
CTS Z1
PSL
Zone 1 Blocked By CT Supervison
579
CTS Z2
PSL
Zone 2 Blocked By CT Supervision
580
CTS T1
PSL
CT Supervision Terminal 1 (feeder or coupler)
585
CTS T6
PSL
CT Supervision Terminal 6 (feeder or coupler)
586
PubPres VIP 115
IEC61850
GOOSE Virtual input 115 publisher bit
599
PubPres VIP 128
IEC61850
GOOSE Virtual input 128 publisher bit
600
VTS Block Z1
BUSBAR Diff
Block Zone 1 VTS
601
VTS Block Z2
BUSBAR Diff
Block Zone 2 VTS
602
T1 I>1 Timer Blk
PSL
Terminal 1 (feeder or coupler) I>1 Timer Blocked
603
T1 I>2 Timer Blk
PSL
Terminal 1 (feeder or coupler) I>2 Timer Blocked
612
T6 I>1 Timer Blk
PSL
Terminal 6 (feeder or coupler) I>1 Timer Blocked
613
T6 I>2 Timer Blk
PSL
Terminal 6 (feeder or coupler) I>2 Timer Blocked
636
T18 I>1 TimerBlk
PSL
Terminal 18 (feeder or coupler) I>1 Timer Blocked
PL
P746/EN PL/J43
Programmable Logic
(PL) 7-16
MiCOM P40 Agile P746
DDB
No.
PL
English Text
Source
Description
637
T18 I>2 TimerBlk
PSL
Terminal 18 (feeder or coupler) I>2 Timer Blocked
651
T1 IN>1 TimeBlk
PSL
Terminal 1 (feeder or coupler) IN>1 Timer Blocked
652
T1 IN>2 TimeBlk
PSL
Terminal 1 (feeder or coupler) IN>2 Timer Blocked
661
T6 IN>1 TimeBlk
PSL
Terminal 6 (feeder or coupler) IN>1 Timer Blocked
662
T6 IN>2 TimeBlk
PSL
Terminal 6 (feeder or coupler) IN>2 Timer Blocked
663
Virtual Input65
UCA2 GOOSE
Virtual Input 65
715
Virtual Input117
UCA2 GOOSE
Virtual Input 117
716
Set Z1 Test Mode
PSL
Enable Z1 Test Mode
717
Set Z2 Test Mode
PSL
Enable Z2 Test Mode
718
CB1 Alarm
PSL
CB1 Alarm
719
CB1 Closed
PSL
CB1 Closed
728
CB6 Alarm
PSL
CB6 Alarm
729
CB6 Closed
PSL
CB6 Closed
752
CB18 Alarm
PSL
CB18 Alarm
753
CB18 Closed
PSL
CB18 Closed
754
Q1 Z1 alarm
BUSBAR Diff
Isolator No 1 connected to Zone 1 alarm
755
Q1 Z1 Closed
BUSBAR Diff
Isolator No 1 connected to Zone 1 Closed
756
Q1 Z2 alarm
BUSBAR Diff
Isolator No 1 connected to Zone 2 alarm
757
Q1 Z2 Closed
BUSBAR Diff
Isolator No 1 connected to Zone 2 Closed
774
Q6 Z1 alarm
BUSBAR Diff
Isolator No 6 connected to Zone 1 alarm
775
Q6 Z1 Closed
BUSBAR Diff
Isolator No 6 connected to Zone 1 Closed
776
Q6 Z2 alarm
BUSBAR Diff
Isolator No 6 connected to Zone 2 alarm
777
Q6 Z2 Closed
BUSBAR Diff
Isolator No 6 connected to Zone 2 Closed
822
Q18 Z1 alarm
BUSBAR Diff
Isolator No 18 connected to Zone 1 alarm
823
Q18 Z1 Closed
BUSBAR Diff
Isolator No 18 connected to Zone 1 Closed
824
Q18 Z2 alarm
BUSBAR Diff
Isolator No 18 connected to Zone 2 alarm
825
Q18 Z2 Closed
BUSBAR Diff
Isolator No 18 connected to Zone 2 Closed
826
Q Busbar alarm
BUSBAR Diff
Tie Isolator Busbar alarm (coupling with one isolator only)
827
Q Busbar Closed
BUSBAR Diff
Tie Isolator Busbar Closed (coupling with one isolator
only)
828
Q Bus Z1 alarm
BUSBAR Diff
Isolator Bus Zone 1 alarm (coupling with one or
isolator(s) and one breaker)
829
Q Bus Z1 Closed
BUSBAR Diff
Isolator Bus Zone 1 Closed (coupling with one or
isolator(s) and one breaker)
830
Q Bus Z2 alarm
BUSBAR Diff
Isolator Bus Zone 2 alarm (coupling with one or
isolator(s) and one breaker)
831
Q Bus Z2 Closed
BUSBAR Diff
Isolator Bus Zone 2 Closed (coupling with one or
isolator(s) and one breaker)
832
Bus CB Alarm
PSL
Bus coupler CB Alarm
833
Bus CB Closed
PSL
Bus coupler CB Closed
834
CctFail Blk Z1 A
BUSBAR Diff
Zone 1 Phase A Circuity Fault
835
CctFail Blk Z1 B
BUSBAR Diff
Zone 1 Phase B Circuity Fault
836
CctFail Blk Z1 C
BUSBAR Diff
Zone 1 Phase C Circuity Fault
837
CctFail Blk Z2 A
BUSBAR Diff
Zone 2 Phase A Circuity Fault
838
CctFail Blk Z2 B
BUSBAR Diff
Zone 2 Phase B Circuity Fault
839
CctFail Blk Z2 C
BUSBAR Diff
Zone 2 Phase C Circuity Fault
840
CctFail Blk CZ A
BUSBAR Diff
Check Zone Phase A Circuity Fault
841
CctFail Blk CZ B
BUSBAR Diff
Check Zone Phase B Circuity Fault
842
CctFail Blk CZ C
BUSBAR Diff
Check Zone Phase C Circuity Fault
Programmable Logic
P746/EN PL/J43
MiCOM P40 Agile P746
DDB
No.
(PL) 7-17
English Text
Source
Description
843
CctFail Blk Z1
BUSBAR Diff
Zone 1 Circuity Fault (OR gate of Z1 phase A CCTFail,
Z1 phase B CCTFail, Z1 phase C CCTFail)
844
CctFail Blk Z2
BUSBAR Diff
Zone 2 Circuity Fault (OR gate of Z2 phase A CCTFail,
Z2 phase B CCTFail, Z2 phase C CCTFail)
845
CctFail Blk A
BUSBAR Diff
Phase A Circuity Fault (OR gate of Phase A CCTFail Z1
and Z2)
846
CctFail Blk B
BUSBAR Diff
Phase B Circuity Fault (OR gate of Phase A CCTFail Z1
and Z2)
847
CctFail Blk C
BUSBAR Diff
Phase C Circuity Fault (OR gate of Phase A CCTFail Z1
and Z2)
848
CctFail Blk CZ
BUSBAR Diff
Check Zone Circuity Fault (OR gate of CZ phase A
CCTFail, CZ phase B CCTFail, CZ phase C CCTFail)
849
Bus CB Not Ready
BUSBAR Diff
Bus CB Not Ready to open or close
851
UI pw level 1
Cyber Security
Less Significant Bit for user interface password indication
level (level 1). Each pair of DDB signal (level1, level2)
indicates the access level as follows: (off,off) = level 0,
(on,off) = level 1, (off,on) = level 2 and (on,on) = level 3
852
UI pw level 2
Cyber Security
Most Significant Bit for user interface password indication
level (level 2)
853
FCurPW level 1
Cyber Security
Less Significant Bit for courier front port password
indication level (level 1). Each pair of DDB signal (level1,
level2) indicates the access level as follows:
(off,off) = level 0, (on,off) = level 1, (off,on) = level 2 and
(on,on) = level 3
854
FCurPW level 2
Cyber Security
Most Significant Bit for courier front port password
indication level (level 2)
855
Remote1 level 1
Cyber Security
Less Significant Bit for first rear port password indication
level (level 1). Each pair of DDB signal (level1, level2)
indicates the access level as follows: (off,off) = level 0,
(on,off) = level 1, (off,on) = level 2 and (on,on) = level 3
856
Remote1 level 2
Cyber Security
Most Significant Bit for first rear port password indication
level (level 2)
857
Remote2 level 1
Cyber Security
Less Significant Bit for second rear port password
indication level (level 1). Each pair of DDB signal (level1,
level2) indicates the access level as follows:
(off,off) = level 0, (on,off) = level 1, (off,on) = level 2 and
(on,on) = level 3
858
Remote2 level 2
Cyber Security
Most Significant Bit for second rear port password
indication level (level 2)
859
RP1 Read Only
PSL
Rear Port 1 in read only mode
860
RP2 Read Only
PSL
Rear Port 2 in read only mode
861
NIC Read Only
PSL
Remote Network Interface Card in read only mode
862
103 MonitorBlock
PSL
Monitor Blocking
863
103 Command Block
PSL
Command Blocking
864
Monitor Port 1
Commissioning Test
Monitor Port 1
865
Monitor Port 2
Commissioning Test
Monitor Port 2
866
Monitor Port 3
Commissioning Test
Monitor Port 3
867
Monitor Port 4
Commissioning Test
Monitor Port 4
868
Monitor Port 5
Commissioning Test
Monitor Port 5
869
Monitor Port 6
Commissioning Test
Monitor Port 6
870
Monitor Port 7
Commissioning Test
Monitor Port 7
871
Monitor Port 8
Commissioning Test
Monitor Port 8
876
Reset Relays/LED
PSL
Reset Latched Relays & LEDs
879
Monitor Blocked
PSL
IEC60870-5-103 Monitoring Blocking
880
Command Blocked
PSL
IEC60870-5-103 Command Blocking
PL
P746/EN PL/J43
Programmable Logic
(PL) 7-18
MiCOM P40 Agile P746
DDB
No.
PL
English Text
Source
Description
881
Time Synch
PSL
Time synchronise to nearest minute on 0-1 change
882
Test Mode
PSL
Set the Test Mode
883
Fault REC TRIG
PSL
Fault Record Trigger Input
884
SG Select x1
PSL
Setting Group Selector x1 (bit 0)
885
SG Select 1x
PSL
Setting Group Selector 1x (bit 1)
886
Any Trip
SW
Any Trip
891
Trip Initial
SW
Trip Initial (same as Any trip)
892
Reset CcT Fail
PSL
Reset Circuitry fault
893
Fault A
Fixed Logic
Phase A Fault
894
Fault B
Fixed Logic
Phase B Fault
895
Fault C
Fixed Logic
Phase C Fault
896
Fault N
Fixed Logic
Earth Fault
898
Z2 BusCB Trp
DIFF
Zone 2 BusCB Trip
899
Idiff Trip A
DIFF
Differential busbar Trip A (Or gate of Z1 Diff PhaseA, Z2
Diff PhaseA)
900
Idiff Trip B
DIFF
Differential busbar Trip B (Or gate of Z1 Diff PhaseB, Z2
Diff PhaseB)
901
Idiff Trip C
DIFF
Differential busbar Trip C (Or gate of Z1 Diff PhaseB, Z2
Diff PhaseB)
902
Idiff Trip
DIFF
Differential busbar Trip (Or gate of Z1 Diff and Z2 Diff)
903
Idiff TripA Z1
DIFF
Differential busbar Zone 1 Phase A Trip
904
Idiff TripB Z1
DIFF
Differential busbar Zone 1 Phase B Trip
905
Idiff TripC Z1
DIFF
Differential busbar Zone 1 Phase C Trip
906
Idiff TripA Z2
DIFF
Differential busbar Zone 2 Phase A Trip
907
Idiff TripB Z2
DIFF
Differential busbar Zone 2 Phase B Trip
908
Idiff TripC Z2
DIFF
Differential busbar Zone 2 Phase C Trip
909
Z1 BusCB Trp
DIFF
Zone 1 BusCB Trip
912
Idiff Trip Z1
DIFF
Differential busbar Zone 1 Diff Trip
913
Idiff Trip Z2
DIFF
Differential busbar Zone 2 Diff Trip
915
Zone Trip T1
DIFF
Zone Trip Feeder 1 by Diff Trip or CBF Back Zone Trip or
External Zone Trip
920
Zone Trip T6
DIFF
Zone Trip Feeder 6 by Diff Trip or CBF Back Zone Trip or
External Zone Trip
932
Zone Trip T18
DIFF
Zone Trip Feeder 18 by Diff Trip or CBF Back Zone Trip
or External Zone Trip
933
DeadZone 1 Trip
Dead Zone
Feeder 1 DeadZone Trip
938
DeadZone 6 Trip
Dead Zone
Feeder 6 DeadZone Trip
950
DeadZone18 Trip
Dead Zone
Feeder 18 DeadZone Trip
951
Quality VIP 65
IEC61850
GOOSE Virtual input 65 Quality bit
1007
Quality VIP 121
IEC61850
GOOSE Virtual input 121 Quality bit
1008
T1 I>1 Trip
Phase Over Current
Terminal 1 (feeder or coupler) I>1 Trip
1009
T1 I>2 Trip
Phase Over Current
Terminal 1 (feeder or coupler) I>2 Trip
1018
T6 I>1 Trip
Phase Over Current
Terminal 6 (feeder or coupler) I>1 Trip
1019
T6 I>2 Trip
Phase Over Current
Terminal 6 (feeder or coupler) I>2 Trip
1042
T18 I>1 Trip
Phase Over Current
Terminal 18 (feeder or coupler) I>1 Trip
1043
T18 I>2 Trip
Phase Over Current
Terminal 18 (feeder or coupler) I>2 Trip
1044
Virtual Output33
PSL
Virtual Output 33
1103
Virtual Output92
PSL
Virtual Output 92
1104
CBF Retrip T1
CBF FAILURE
CBF Retrip Terminal 1 (feeder or coupler)
Programmable Logic
P746/EN PL/J43
MiCOM P40 Agile P746
DDB
No.
(PL) 7-19
English Text
Source
Description
1109
CBF Retrip T6
CBF FAILURE
CBF Retrip Terminal 6 (feeder or coupler)
1121
CBF Retrip T18
CBF FAILURE
CBF Retrip Terminal 18 (feeder or coupler)
1122
CBF Bktrip Z1
CBF FAILURE
Zone 1 CBF Back Trip
1123
CBF Bktrip Z2
CBF FAILURE
Zone 2 CBF Back Trip
1124
RemoteTripT1
CBF FAILURE
Terminal 1 (feeder or coupler) Remote Trip By Busbar
Diff or CBF
1129
RemoteTripT6
CBF FAILURE
Terminal 6 (feeder or coupler) Remote Trip By Busbar
Diff or CBF
1141
RemoteTripT18
CBF FAILURE
Terminal 18 (feeder or coupler) Remote Trip By Busbar
Diff or CBF
1142
T1 IN>1 Trip
Phase Over Current
Terminal 1 (feeder or coupler) IN>1 Trip
1143
T1 IN>2 Trip
Phase Over Current
Terminal 1 (feeder or coupler) IN>2 Trip
1152
T6 IN>1 Trip
Phase Over Current
Terminal 6 (feeder or coupler) IN>1 Trip
1153
T6 IN>2 Trip
Phase Over Current
Terminal 6 (feeder or coupler) IN>2 Trip
1154
PubPres VIP 1
IEC61850
GOOSE Virtual input 1 publisher bit
1267
PubPres VIP114
IEC61850
GOOSE Virtual input 114 publisher bit
1268
Ext CBF INIT T1
External Trip
External CBF Init T1
1285
Ext CBF INIT T18
External Trip
External CBF Init T18
1286
ExtCBFInit BusCB
External Trip
External CBF Init Bus CB
1287
Ext CBF Z1
External Trip
Zone 1 External CBF Trip
1288
Ext CBF Z2
External Trip
Zone 2 External CBF Trip
1289
CBF Retrp BusCB
CBF FAILURE
Bus CB CBF Retrip
1290
Int CBF Init T1
CBF FAILURE
Internal signal init CBF Terminal 1 (feeder or coupler)
1295
Int CBF Init T6
CBF FAILURE
Internal signal init CBF Terminal 6 (feeder or coupler)
1307
Int CBF Init T18
CBF FAILURE
Internal signal init CBF Terminal 18 (feeder or coupler)
1308
IntCBFInit BusCB
CBF FAILURE
Internal signal init CBF Bus CB
1312
Any Start
Protection Starts (most)
Any Start
1313
Id Bias Start A
DIFF
Busbar Diff Phase A Start
1314
Id Bias Start B
DIFF
Busbar Diff Phase B Start
1315
Id Bias Start C
DIFF
Busbar Diff Phase C Start
1316
DeadZone 1 Start
Dead Zone Over Current
Terminal 1 (feeder or coupler) DeadZone Over Current
Start
1321
DeadZone 6 Start
Dead Zone Over Current
Terminal 6 (feeder or coupler) DeadZone Over Current
Start
1333
DeadZone18 Start
Dead Zone Over Current
Terminal 18 (feeder or coupler) DeadZone Over Current
Start
1340
T1 I>1 Start
Phase Over Current
Terminal 1 (feeder or coupler) I>1 Start
1341
T1 I>1 Start A
Phase Over Current
Terminal 1 (feeder or coupler) I>1 Start A
1342
T1 I>1 Start B
Phase Over Current
Terminal 1 (feeder or coupler) I>1 Start B
1343
T1 I>1 Start C
Phase Over Current
Terminal 1 (feeder or coupler) I>1 Start C
1380
T6 I>1 Start
Phase Over Current
Terminal 6 (feeder or coupler) I>1 Start
1381
T6 I>1 Start A
Phase Over Current
Terminal 6 (feeder or coupler) I>1 Start A
1382
T6 I>1 Start B
Phase Over Current
Terminal 6 (feeder or coupler) I>1 Start B
1383
T6 I>1 Start C
Phase Over Current
Terminal 6 (feeder or coupler) I>1 Start C
1384
T6 I>2 Start
Phase Over Current
Terminal 6 (feeder or coupler) I>2 Start
1385
T6 I>2 Start A
Phase Over Current
Terminal 6 (feeder or coupler) I>2 Start A
1386
T6 I>2 Start B
Phase Over Current
Terminal 6 (feeder or coupler) I>2 Start B
1387
T6 I>2 Start C
Phase Over Current
Terminal 6 (feeder or coupler) I>2 Start C
1476
T18 I>1 Start
Phase Over Current
Terminal 18 (feeder or coupler) I>1 Start
PL
P746/EN PL/J43
Programmable Logic
(PL) 7-20
MiCOM P40 Agile P746
DDB
No.
PL
English Text
Source
Description
1477
T18 I>1 Start A
Phase Over Current
Terminal 18 (feeder or coupler) I>1 Start A
1478
T18 I>1 Start B
Phase Over Current
Terminal 18 (feeder or coupler) I>1 Start B
1479
T18 I>1 Start C
Phase Over Current
Terminal 18 (feeder or coupler) I>1 Start C
1480
T18 I>2 Start
Phase Over Current
Terminal 18 (feeder or coupler) I>2 Start
1481
T18 I>2 Start A
Phase Over Current
Terminal 18 (feeder or coupler) I>2 Start A
1482
T18 I>2 Start B
Phase Over Current
Terminal 18 (feeder or coupler) I>2 Start B
1483
T18 I>2 Start C
Phase Over Current
Terminal 18 (feeder or coupler) I>2 Start C
1484
Virtual Input118
UCA2 GOOSE
Virtual Input 118
1494
Virtual Input128
UCA2 GOOSE
Virtual Input 128
1496
T1 IN>1 Start
Phase Over Current
Terminal 1 (feeder or coupler) IN>1 Start
1497
T1 IN>2 Start
Phase Over Current
Terminal 1 (feeder or coupler) IN>2 Start
1498
T2 IN>1 Start
Phase Over Current
Terminal 2 (feeder or coupler) IN>1 Start
1499
T2 IN>2 Start
Phase Over Current
Terminal 2 (feeder or coupler) IN>2 Start
1500
T3 IN>1 Start
Phase Over Current
Terminal 3 (feeder or coupler) IN>1 Start
1501
T3 IN>2 Start
Phase Over Current
Terminal 3 (feeder or coupler) IN>2 Start
1502
T4 IN>1 Start
Phase Over Current
Terminal 4 (feeder or coupler) IN>1 Start
1503
T4 IN>2 Start
Phase Over Current
Terminal 4 (feeder or coupler) IN>2 Start
1504
T5 IN>1 Start
Phase Over Current
Terminal 5 (feeder or coupler) IN>1 Start
1505
T5 IN>2 Start
Phase Over Current
Terminal 5 (feeder or coupler) IN>2 Start
1506
T6 IN>1 Start
Phase Over Current
Terminal 6 (feeder or coupler) IN>1 Start
1507
T6 IN>2 Start
Phase Over Current
Terminal 6 (feeder or coupler) IN>2 Start
1508
Quality VIP 122
Phase Over Current
GOOSE Virtual input 122 Quality bit
1514
Quality VIP 128
Phase Over Current
GOOSE Virtual input 128 Quality bit
1516
Id Start Z1 A
DIFF
Busbar Idiff Zone 1 StartA
1517
Id Start Z1 B
DIFF
Busbar Idiff Zone 1 StartB
1518
Id Start Z1 C
DIFF
Busbar Idiff Zone 1 StartC
1519
Id Start Z2 A
DIFF
Busbar Idiff Zone 2 StartA
1520
Id Start Z2 B
DIFF
Busbar Idiff Zone 2 StartB
1521
Id Start Z2 C
DIFF
Busbar Idiff Zone 2 StartC
1522
Idiff Start Z1
DIFF
Busbar Zone 2 Diff Start (OR gate of Z2 phase A, B, C
Diff start)
1523
Idiff Start Z2
DIFF
Busbar Zone 1 Diff Start (OR gate of Z1 phase A, B, C
Diff start)
1524
Idiff CZ StartA
DIFF
Busbar Check Zone Phase A Diff Start
1525
Idiff CZ StartB
DIFF
Busbar Check Zone Phase B Diff Start
1526
Idiff CZ StartC
DIFF
Busbar Check Zone Phase C Diff Start
1527
Idiff CZ Start
DIFF
Busbar Check Zone Diff Start (OR gate of CZ phase A, B,
C Diff start)
1528
Quality VIP 1
IEC61850
GOOSE Virtual input 1 Quality bit
1591
Quality VIP 64
IEC61850
GOOSE Virtual input 64 Quality bit
1592
Virtual Output01
PSL
Virtual Output 01
1623
Virtual Output32
PSL
Virtual Output 32
1624
DeadZone1 StartA
Dead Zone Over Current
Terminal 1 (feeder or coupler) Phase A DeadZone Over
Current start
1629
DeadZone6 StartA
Dead Zone Over Current
Terminal 6 (feeder or coupler) Phase A DeadZone Over
Current start
1641
DeadZon18 StartA
Dead Zone Over Current
Terminal 18 (feeder or coupler) Phase A DeadZone Over
Current start
1642
DeadZone1 startB
Dead Zone Over Current
Terminal 1 (feeder or coupler) Phase B DeadZone Over
Current start
Programmable Logic
P746/EN PL/J43
MiCOM P40 Agile P746
DDB
No.
(PL) 7-21
English Text
Source
Description
1647
DeadZone6 startB
Dead Zone Over Current
Terminal 6 (feeder or coupler) Phase B DeadZone Over
Current start
1659
DeadZon18 startB
Dead Zone Over Current
Terminal 18 (feeder or coupler) Phase B DeadZone Over
Current start
1660
DeadZone1 startC
Dead Zone Over Current
Terminal 1 (feeder or coupler) Phase C DeadZone Over
Current start
1665
DeadZone6 startC
Dead Zone Over Current
Terminal 6 (feeder or coupler) Phase C DeadZone Over
Current start
1677
DeadZon18 startC
Dead Zone Over Current
Terminal 18 (feeder or coupler) Phase C DeadZone Over
Current start
1678
Virtual Output93
PSL
Virtual Output 93
1695
VirtualOutput110
1696
Z1 In Test Mode
Virtual Output 110
SW
Zone 1 in Test Mode
1697
Z2 In Test Mode
SW
Zone 2 in Test Mode
1698
T1 In Test Mode
SW
Terminal 1 (feeder or coupler) in Test Mode
1703
T6 In Test Mode
SW
Terminal 6 (feeder or coupler) in Test Mode
1715
T18 In Test Mode
SW
Terminal 18 (feeder or coupler) in Test Mode
1716
PhComp Blk Z1 A
SW
Zone 1 Phase A Phase Comparision Block
1717
PhComp Blk Z1 B
SW
Zone 1 Phase B Phase Comparision Block
1718
PhComp Blk Z1 C
SW
Zone 1 Phase C Phase Comparision Block
1719
PhComp Blk Z2 A
SW
Zone 2 Phase A Phase Comparision Block
1720
PhComp Blk Z2 B
SW
Zone 2 Phase B Phase Comparision Block
1721
PhComp Blk Z2 C
SW
Zone 2 Phase C Phase Comparision Block
1722
VirtualOutput111
PSL
Virtual Output 111
1739
VirtualOutput128
PSL
Virtual Output 128
1744
CBF Z1 Blocked
BUSBAR CBF
Zone 1 CBF Blocked
1745
CBF Z2 Blocked
BUSBAR CBF
Zone 2 CBF Blocked
1746
Diff CZ C Blked
BUSBAR CBF
Check Zone Diff Phase C Blocked
1747
PhComp Blk Z1
Busbar Diff
Zone 1 Phase comparison blocked (AND gate of Phase
A, B, C)
1748
PhComp Blk Z2
Busbar Diff
Zone 2 Phase comparison blocked (AND gate of Phase
A, B, C)
1749
VTS Acc Ind
VT Supervision
VTS Accelerate Indication
1750
VTS Volt Dep
VT Supervision
Any Voltage Dependent
1751
Freq High
Frequency Tracking
Frequency too High
1752
Freq Low
Frequency Tracking
Frequency too Low
1753
Freq Not found
Frequency Tracking
Frequency Not Found
1754
CB1 Not Ready
CB Monitoring
CB1 Healthy
1759
CB6 Not Ready
CB Monitoring
CB6 Healthy
1771
CB18 Not Ready
CB Monitoring
CB18 not ready to open or close
1772
Termi1 Healthy
CB Monitoring
Terminal 1 (feeder or coupler) Healthy
1777
Termi6 Healthy
CB Monitoring
Terminal 6 (feeder or coupler) Healthy
1789
Termi18 Healthy
CB Monitoring
Terminal 18 (feeder or coupler) Healthy
1800
Diff Fault Z1
BUSBAR Diff
Zone 1 Busbar Diff any Phase Fault
1801
Diff Fault Z1 A
BUSBAR Diff
Zone 1 Busbar Diff Phase A Fault
1802
Diff Fault Z1 B
BUSBAR Diff
Zone 1 Busbar Diff Phase B Fault
1803
Diff Fault Z1 C
BUSBAR Diff
Zone 1 Busbar Diff Phase C Fault
1804
Diff Fault Z2
BUSBAR Diff
Zone 2 Busbar Diff Phase Fault
1805
Diff Fault Z2 A
BUSBAR Diff
Zone 2 Busbar Diff Phase A Fault
1806
Diff Fault Z2 B
BUSBAR Diff
Zone 2 Busbar Diff Phase B Fault
PL
P746/EN PL/J43
Programmable Logic
(PL) 7-22
MiCOM P40 Agile P746
DDB
No.
PL
3.19
English Text
Source
Description
1807
Diff Fault Z2 C
BUSBAR Diff
Zone 2 Busbar Diff Phase C Fault
1808
Diff Fault CZ
BUSBAR Diff
Check Zone Busbar Diff Phase Fault
1809
Diff Fault CZ A
BUSBAR Diff
Check Zone Busbar Diff Phase A Fault
1810
Diff Fault CZ B
BUSBAR Diff
Check Zone Busbar Diff Phase B Fault
1811
Diff Fault CZ C
BUSBAR Diff
Check Zone Busbar Diff Phase C Fault
1812
Diff Z1 Blked
BUSBAR Diff
Zone 1 Busbar Diff in Block Status
1813
Diff Z1 A Blked
BUSBAR Diff
Zone 1 Busbar Diff Phase A Blocked
1814
Diff Z1 B Blked
BUSBAR Diff
Zone 1 Busbar Diff Phase B Blocked
1815
Diff Z1 C Blked
BUSBAR Diff
Zone 1 Busbar Diff Phase C Blocked
1816
Diff Z2 Blked
BUSBAR Diff
Zone 2 Busbar Diff Blocked
1817
Diff Z2 A Blked
BUSBAR Diff
Zone 2 Busbar Diff Phase A Blocked
1818
Diff Z2 B Blked
BUSBAR Diff
Zone 2 Busbar Diff Phase B Blocked
1819
Diff Z2 C Blked
BUSBAR Diff
Zone 2 Busbar Diff Phase C Blocked
1820
Diff CZ Blked
BUSBAR Diff
Check Zone Busbar Diff Blocked
1821
Diff CZ A Blked
BUSBAR Diff
Check Zone Busbar Diff Phase A Blocked
1822
Diff CZ B Blked
BUSBAR Diff
Check Zone Busbar Diff Phase B Blocked
1823
Diff CZ C Blked
BUSBAR Diff
Check Zone Busbar Diff Phase C Blocked
1824
Control Input 1
User Control 1
Control Input 1 - for SCADA and menu commands into
PSL
1855
Control Input 32
User Control 32
Control Input 32 - for SCADA and menu commands into
PSL
1856
Virtual Input 01
UCA2 GOOSE
GOOSE Input 01 - Allows binary signals to be mapped to
interface into PSL
1919
Virtual Input 64
UCA2 GOOSE
GOOSE Input 64 - Allows binary signals to be mapped to
interface into PSL
1920
PSL Int. 1
PSL
PSL Internal connection
2047
PSL Int. 128
PSL
PSL Internal connection
Default PSL
The following section details the default settings of the PSL.
Relay Outputs
Model
Logic Inputs
Total
P746xxxA
P746xxxB
P746xxxC
P746xxxD
P746xxxE
P746xxxF
P746xxxG
P746xxxH
P746xxxJ
P746xxxK
P746xxxL
3.20
16
16
16
16
24
24
24
32
32
40
32
16
16
32
32
24
24
24
24
24
24
32
relays
16
8
32
24
24
16
8
24
16
24
32
High break relays
-8
-8
-8
16
-8
---
Logic Input Mapping
The default mappings for each of the opto-isolated inputs are as shown in the following table:
Opto-Input
Number
1
P746 Relay Text
Input L1
Function
CB1 Closed
Programmable Logic
P746/EN PL/J43
MiCOM P40 Agile P746
(PL) 7-23
Opto-Input
Number
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
3.21
P746 Relay Text
Function
Input L2
Input L3
Input L4
Input L5
Input L6
Input L7
Input L8
Input L9
Input L10
Input L11
Input L12
Input L13
Input L14
Input L15
Input L16
Input L17
Input L18
Input L19
Input L20
Input L21
Input L22
Input L23
Input L24
Input L25
Input L26
Input L27
Input L28
Input L29
Input L30
Input L31
Input L32
Input L33
Input L34
Input L35
Input L36
Input L37
Input L38
Input L39
Input L40
CB2 Closed
CB3 Closed
CB4 Closed
CB5 Closed
CB6 Closed
T11 Closed
T21 Closed
T32 Closed
T42 Closed
T51 Closed
T52 Closed
T61 Closed
T62 Closed
Block CZ
Not mapped
Not mapped
Not mapped
Not mapped
Not mapped
Not mapped
Not mapped
Not mapped
Not mapped
Not mapped
Not mapped
Not mapped
Not mapped
Not mapped
Not mapped
Not mapped
Not mapped
Not mapped
Not mapped
Not mapped
Not mapped
Not mapped
Not mapped
Not mapped
Not mapped
PL
Relay Output Contact Mapping
The default mappings for each of the relay output contacts are as shown in the following
table:
Relay Contact
Number
1
2
3
4
5
6
7
8
9
P746 Relay Text
Relay R1
Relay R2
Relay R3
Relay R4
Relay R5
Relay R6
Relay R7
Relay R8
Relay R9
P746 Relay
Conditioner
Pick-up 0/0
Pick-up 0/0
Pick-up 0/0
Pick-up 0/0
Pick-up 0/0
Pick-up 0/0
Pick-up 0/0
Pick-up 0/0
Pick-up 0/0
Function
Trip CB1
Trip CB2
Trip CB3
Trip CB4
Trip CB5
Bus CB
Circuitry fault
Fault Zone 1
Fault Zone 2
P746/EN PL/J43
Programmable Logic
(PL) 7-24
MiCOM P40 Agile P746
Relay Contact
Number
P746 Relay Text
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
PL
Relay R10
Relay R11
Relay R12
Relay R13
Relay R14
Relay R15
Relay R16
Relay R17
Relay R18
Relay R19
Relay R20
Relay R21
Relay R22
Relay R23
Relay R24
Relay R25
Relay R26
Relay R27
Relay R28
Relay R29
Relay R30
Relay R31
Relay R32
Note:
P746 Relay
Conditioner
Pick-up 0/0
Pick-up 0/0
Pick-up 0/0
Pick-up 0/0
Pick-up 0/0
Pick-up 0/0
Pick-up 0/0
Function
CBF trip
87BB Trip
Fault Ph A
Fault Ph B
Fault Ph C
Maintenance
CB Alarm
Not mapped
Not mapped
Not mapped
Not mapped
Not mapped
Not mapped
Not mapped
Not mapped
Not mapped
Not mapped
Not mapped
Not mapped
Not mapped
Not mapped
Not mapped
Not mapped
It is essential that relay 1, 2 and 3 are used for tripping purposes as this
output is directly driven in the fixed logic to obtain the typical 13ms tripping
time.
A fault record can be generated by connecting one or a number of contacts to
the “Fault Record Trigger” in PSL. It is recommended that the triggering contact
be ‘self reset’ and not a latching. If a latching contact were chosen the fault
record would not be generated until the contact had fully reset.
3.22
Function Key Input Mapping
The default mappings for each of the function key inputs are as shown in the following table:
LED
Number
1
2
3
4
5
6
7
8
9
10
3.23
Text
Function Key 1
Function Key 2
Function Key 3
Function Key 4
Function Key 5
Function Key 6
Function Key 7
Function Key 8
Function Key 9
Function Key 10
Setting
Normal
Toggled
Normal
Normal
Normal
Normal
Toggled
Normal
Disabled
Normal
Function
Set zone 1 in test mode
Set zone 2 in test mode
Reset Circuitry fault
Reset Indications
Start DR
Programmable LED Output Mapping
The default mappings for each of the programmable LEDs are as shown in the following
table:
Programmable Logic
P746/EN PL/J43
MiCOM P40 Agile P746
LED
Number
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
(PL) 7-25
LED Input Connection/Text
LED1 Red
LED1 Yellow
LED1 Green
LED2 Red
LED2 Yellow
LED2 Green
LED3 Red
LED3 Yellow
LED3 Green
LED4 Red
LED4 Yellow
LED4 Green
LED5 Red
LED5 Yellow
LED5 Green
LED6 Red
LED6 Yellow
LED6 Green
LED7 Red
LED7 Yellow
LED7 Green
LED8 Red
LED8 Yellow
LED8 Green
FnKey LED1 Red
FnKey LED1 Yellow
FnKey LED1 Green
FnKey LED2 Red
FnKey LED2 Yellow
FnKey LED2 Green
FnKey LED3 Red
FnKey LED3 Yellow
FnKey LED3 Green
FnKey LED4 Red
FnKey LED4 Yellow
FnKey LED4 Green
FnKey LED5 Red
FnKey LED5 Yellow
FnKey LED5 Green
FnKey LED6 Red
FnKey LED6 Yellow
FnKey LED6 Green
FnKey LED7 Red
FnKey LED7 Yellow
FnKey LED7 Green
FnKey LED8 Red
FnKey LED8 Yellow
FnKey LED8 Green
FnKey LED9 Red
FnKey LED9 Yellow
FnKey LED9 Green
FnKey LED10 Red
FnKey LED10 Yellow
FnKey LED10 Green
Latched
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
P746 LED Function Indication
CB1 closed
CB1 Alarm
CB1 open
CB2 closed
CB2 Alarm
CB2 open
CB3 closed
CB3 alarm
CB3 open
CB4 closed
CB4 Alarm
CB4 open
CB5 closed
CB5 Alarm
CB5 open
CB6 closed
CB6 Alarm
CB6 open
50BF Trip zone 1
87BB & 50 BF trip zone 1
87BB Trip zone 1
50BF Trip zone 2
87BB & 50 BF trip zone 2
87BB Trip zone 2
Zone 1: blocked
Zone 1: alarm (CZ not blocked)
Zone 1: healthy
Zone 1 in test mode
Not used
Zone 1: healthy
Fault on phase A
Not used
Not used
Fault on phase B
Not used
Not used
Fault on phase C
Not used
Not used
Zone 2: blocked
Zone 2: alarm (CZ not blocked)
Zone 2: healthy
Zone 2 in test mode
Not used
Zone 2: healthy
Not used
Not used
Not used
Trip latched
Not used
Indications resetting
Not used
External disturbance record
Disturbance record started
PL
P746/EN PL/J43
Programmable Logic
(PL) 7-26
3.24
MiCOM P40 Agile P746
Fault Recorder Start Mapping
The default mapping for the signal which initiates a fault record is as shown in the following
table:
3.25
Initiating Signal
Fault Trigger
Trip 87BB
Initiate fault recording from main protection trip
Trip 50BF
Initiate fault recording from main protection trip
PSL Scheme Version Control
To help you keep track of the PSL loaded into products, a version control feature is included.
The user interface contains a PSL DATA column, which can be used to track PSL
modifications. A total of 12 cells are contained in the PSL DATA column; 3 for each setting
group.
Grp(n) PSL Ref: When downloading a PSL scheme to an IED, you will be prompted to enter
the relevant group number and a reference identifier. The first 32 characters of the reference
identifier are displayed in this cell. The horizontal cursor keys can scroll through the 32
characters as the LCD display only displays 16 characters.
Example:
Grp. PSL Ref.
PL
Date/time: This cell displays the date and time when the PSL scheme was downloaded to
the IED.
Example:
18 Nov 2002
08:59:32.047
Grp(n) PSL ID: This cell displays a unique ID number for the downloaded PSL scheme.
Example:
Grp. 1 PSL
ID - 2062813232
Note:
The above cells are repeated for each setting group.
Programmable Logic
P746/EN PL/J43
MiCOM P40 Agile P746
4
(PL) 7-27
VIEWING AND PRINTING PSL DIAGRAMS
You can view and print the PSL diagrams for the device. Typically these diagrams allow you
to see the following mappings:
• Opto Input Mappings
• Output Relay Mappings
• LED Mappings
• Start Indications
• Phase Trip Mappings
• System Check Mapping
To download the default PSL diagrams for the device and to print them:
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
Close the Settings Application Software.
Start the Data Model Manager.
Click Add then Next.
Click Internet then Next.
Select your language then click Next.
From the tree view, select the model and software version.
Click Install. When complete click OK.
Close the Data Model Manager and start the Settings Application Software.
Select Tools then PSL Editor (Px40).
In the PSL Editor select File then New then Default Scheme.
Select the IED type
Use the advance button to select the software, then select the model number.
Highlight the required PSL diagram and select File then Print.
PL
P746/EN PL/J43
(PL) 7-28
PL
Programmable Logic
MiCOM P40 Agile P746
Measurements and Recording
P746/EN MR/J43
MiCOM P40 Agile P746
(MR) 8-1
MEASUREMENTS AND
RECORDING
Hardware Suffix:
M
Software Version:
91
MR
P746/EN MR/J43
(MR) 8-2
MR
Measurements and Recording
MiCOM P40 Agile P746
Measurements and Recording
MiCOM P40 Agile P746
P746/EN MR/J43
(MR) 8-3
CONTENTS
1
MEASUREMENTS AND RECORDING
5
1.1
Introduction
5
1.2
Event & Fault Records
5
1.2.1.1
Types of Event
5
1.2.1.2
Change of State of Opto-isolated Inputs
5
1.2.1.3
Change of State of One or More Output Relay Contacts
5
1.2.1.4
Relay Alarm Conditions
6
1.2.1.5
Protection Element Starts and Trips
6
1.2.1.6
General Events
6
1.2.1.7
Fault Records
6
1.2.1.8
Setting Changes
6
1.2.2
Resetting of Event/Fault Records
7
1.2.3
Viewing Event Records via S1 Agile Support Software
7
1.2.4
Event Filtering
7
1.3
Disturbance Recorder
8
1.4
Measurements
8
1.4.1
Check Zone Phase Currents
8
1.4.2
Measured Currents
9
1.4.3
Sequence Voltages and Currents
9
1.4.4
Settings
9
1.4.5
Measurement Display Quantities
9
MR
P746/EN MR/J43
(MR) 8-4
MR
Measurements and Recording
MiCOM P40 Agile P746
Measurements and Recording
P746/EN MR/J43
MiCOM P40 Agile P746
1
MEASUREMENTS AND RECORDING
1.1
Introduction
(MR) 8-5
The P746 is equipped with integral measurements, event, fault and disturbance recording
facilities suitable for analysis of complex system disturbances.
The relay is flexible enough to allow for the programming of these facilities to specific user
application requirements and are discussed below.
1.2
Event & Fault Records
The relay records and time tags up to 512 events and stores them in non-volatile memory
(backed-up SRAM). This enables the system operator to establish the sequence of events
that occurred within the relay following a particular power system condition, switching
sequence etc. When the available space is exhausted, the oldest event is automatically
overwritten by the new one.
The real time clock within the relay provides the time tag to each event, to a resolution of
1ms.
The event records can be displayed on the front plate LCD or remotely using the
communications port.
The event records are detailed in the VIEW RECORDS column. The first event (0) is always
the latest event. After selecting the required event, you can scroll through the menus to
obtain further details.
To extract from a remote source using communications, refer to the SCADA
Communications section (P746/EN SC), where the procedure is fully explained.
1.2.1.1
Types of Event
An event may be a change of state of a control input or output relay, an alarm condition,
setting change etc. The following sections show the various items that constitute an event:
1.2.1.2
Change of State of Opto-isolated Inputs
If one or more of the opto (logic) inputs has changed state since the last time that the
protection algorithm ran, the new status is logged as an event. When this event is selected
to be viewed on the LCD, three applicable cells will become visible as shown below:
Time & date of event
“LOGIC INPUTS1”
“Event Value 0101010101010101”
The Event Value is a 32-bit word showing the status of the opto inputs, where the least
significant bit (extreme right) corresponds to opto input 1 etc. The same information is
present if the event is extracted and viewed using a PC.
1.2.1.3
Change of State of One or More Output Relay Contacts
If one or more of the output relay contacts have changed state since the last time that the
protection algorithm ran, then the new status is logged as an event. When this event is
selected to be viewed on the LCD, three applicable cells will become visible:
Time & date of event
“OUTPUT CONTACTS 1”
“Event Value 1010101010101010”
The Event Value is a 24 bit word showing the status of the output contacts, where the least
significant bit (extreme right) corresponds to output contact 1 etc. The same information is
present if the event is extracted and viewed using a PC.
MR
P746/EN MR/J43
Measurements and Recording
(MR) 8-6
1.2.1.4
MiCOM P40 Agile P746
Relay Alarm Conditions
Any alarm conditions generated by the relays will also be logged as individual events. The
following table shows examples of some of the alarm conditions and how they appear in the
event list:
Alarm Condition
Battery Fail
Field Voltage Fail
Event Text
Battery Fail ON/OFF
Field Volt Fail ON/OFF
Event Value
Bit position 0 in 32 bit field
Bit position 1 in 32 bit field
The table above shows the abbreviated description that is given to the various alarm
conditions and also a corresponding value between 0 and 31. This value is appended to
each alarm event in a similar way as for the input and output events previously described. It
is used by the event extraction software, such as S1 Agile, to identify the alarm and is
therefore invisible if the event is viewed on the LCD. Either ON or OFF is shown after the
description to signify whether the particular condition has become operated or has reset.
1.2.1.5
Protection Element Starts and Trips
Any operation of protection elements, (either a start or a trip condition) will be logged as an
event record, consisting of a text string indicating the operated element and an event value.
Again, this value is intended for use by the event extraction software, such as S1 Agile,
rather than for the user, and is therefore invisible when the event is viewed on the LCD.
1.2.1.6
General Events
A number of events come under the heading of ‘General Events’ - an example is shown
below:
Nature of Event
Level 1 password modified, either
from user interface, front or rear
port.
MR
Displayed Text in Event Record
PW1 modified UI, F, R or R2
Displayed Value
0 UI=6, F=11, R=16, R2=38
A complete list of the ‘General Events’ is given in the Relay Menu Database, which is a
separate document available on request.
1.2.1.7
Fault Records
Each time a fault record is generated, an event is also created. The event simply states that
a fault record was generated, with a corresponding time stamp.
Note that viewing of the actual fault record is carried out in the Select Fault cell further down
the VIEW RECORDS column, which is selectable from up to 20 records. These records
consist of fault flags, fault location, fault measurements etc. Also note that the time stamp
given in the fault record itself will be more accurate than the corresponding stamp given in
the event record as the event is logged some time after the actual fault record is generated.
The fault record is triggered from the Fault REC. TRIG. signal assigned in the default
programmable scheme logic to any trip (87BB or 50BF trip in the P746). The fault
measurements in the fault record are given at the time of the protection start. Also, the fault
recorder does not stop recording until the reset of the Fault REC. TRIG. signal in order to
record all the protection flags during the fault.
It is recommended that the triggering contact be ‘self reset’ and not latching. If a latching
contact is chosen the fault record will not be generated until the contact had fully reset.
1.2.1.8
Setting Changes
Changes to any setting within the relay are logged as an event. Two examples are shown in
the following table:
Type of Setting Change
Control/Support Setting
Group # Change
Displayed Text in Event Record
C & S Changed
Group # Changed
Displayed Value
22
#
Measurements and Recording
P746/EN MR/J43
MiCOM P40 Agile P746
(MR) 8-7
Where # = 1 to 4
Note:
1.2.2
Control/Support settings are communications, measurement, CT/VT ratio
settings etc, which are not duplicated within the four setting groups. When
any of these settings are changed, the event record is created
simultaneously. However, changes to protection or disturbance recorder
settings will only generate an event once the settings have been confirmed
at the ‘setting trap’.
Resetting of Event/Fault Records
To delete either the event, fault or maintenance reports, use the RECORD CONTROL
column.
1.2.3
Viewing Event Records via S1 Agile Support Software
When the event records are extracted and viewed on a PC they look slightly different than
when viewed on the LCD.
For further information regarding events and their specific meaning, refer to the relay menu
database document. This is a standalone document not included in this manual.
1.2.4
Event Filtering
It is possible to disable the reporting of events from all interfaces that supports setting
changes. The settings that control the various types of events are in the RECORD
CONTROL column. The effect of setting each to disabled is as follows:
Menu Text
Default Setting
Available Settings
RECORD CONTROL
Clear Events
No
No or Yes
Selecting “Yes” will cause the existing event log to be cleared and an event will be generated indicating that the
events have been erased.
Clear Faults
No
No or Yes
Selecting “Yes” will cause the existing fault records to be erased from the relay.
Clear Maint
No
No or Yes
Selecting “Yes” will cause the existing maintenance records to be erased from the relay.
Alarm Event
Enabled
Enabled or Disabled
Disabling this setting means that all the occurrences that produce an alarm will result in no event being generated.
Relay O/P Event
Enabled
Enabled or Disabled
Disabling this setting means that no event will be generated for any change in logic input state.
Opto Input Event
Enabled
Enabled or Disabled
Disabling this setting means that no event will be generated for any change in logic input state.
General Event
Enabled
Enabled or Disabled
Disabling this setting means that no General Events will be generated
Fault Rec Event
Enabled
Enabled or Disabled
Disabling this setting means that no event will be generated for any fault that produces a fault record
Maint Rec Event
Enabled
Enabled or Disabled
Disabling this setting means that no event will be generated for any occurrence that produces a maintenance
record.
Protection Event
Enabled
Enabled or Disabled
Disabling this setting means that any operation of protection elements will not be logged as an event.
Clear Dist Recs
No
No or Yes
Selecting “Yes” will cause the existing disturbance records to be erased from the relay.
DDB 31 - 0
11111111111111111111111111111111
Displays the status of DDB signals 0 – 31.
DDB 2047 - 2016
11111111111111111111111111111111
Displays the status of DDB signals 2047 – 2016.
Note:
Some occurrences will result in more than one type of event, e.g. a battery
failure will produce an alarm event and a maintenance record event.
MR
P746/EN MR/J43
(MR) 8-8
Measurements and Recording
MiCOM P40 Agile P746
If the Protection Event setting is enabled a further set of settings is revealed which allow the
event generation by individual DDB signals to be enabled or disabled.
For further information regarding events and their specific meaning, refer to relay menu
database document.
1.3
Disturbance Recorder
The disturbance recorder feature allows you to record selected current and voltage inputs to
the protection elements, together with selected digital signals. The digital signals may be
inputs, outputs, or internal DDB signals.
The integral disturbance recorder has an area of memory specifically set aside for storing
disturbance records. The number of records that can be stored is dependent on the
recording duration. The minimum duration is 0.1 s and the maximum duration is 10.5 s.
When the available memory is exhausted, the oldest records are overwritten by the newest
ones.
Each disturbance record consists of a number of analogue data channels and digital data
channels. The relevant CT and VT ratios for the analogue channels are also extracted to
enable scaling to primary quantities.
The fault recording times are set by a combination of the Duration and Trigger Position
cells. The Duration cell sets the overall recording time and the Trigger Position cell sets
the trigger point as a percentage of the duration.
For example, the default settings show that the overall recording time is set to 1.5 s with the
trigger point being at 33.3% of this, giving 0.5 s pre-fault and 1 s post fault recording times.
With the Trigger Mode set to Single, if further triggers occurs whilst a recording is taking
place, the recorder will ignore the trigger. However, with the Trigger Mode set to Extended,
the post trigger timer will be reset to zero, extending the recording time.
MR
You can select any of the device's analogue inputs as analogue channels to be recorded.
You can also map any of the opto-inputs output contacts to the digital channels. In addition,
you may also map a number of DDB signals such as Starts and LEDs to digital channels.
You may choose any of the digital channels to trigger the disturbance recorder on either a
low to high or a high to low transition, via the Input Trigger cell. The default settings are
such that any dedicated trip output contacts will trigger the recorder.
It is not possible to view the disturbance records locally via the LCD. You must be extract
these using suitable software such as MiCOM S1 Agile.
1.4
Measurements
The relay produces a variety of both directly measured and calculated system quantities.
These measurement values are updated on a per second basis and can be viewed in the
“Measurements” columns (up to three) of the relay or via S1 Agile Measurement viewer.
The P746 relay is able to measure and display the following quantities as summarized.
1.4.1
Check Zone Phase Currents
There are also measured values from the protection functions, which are also displayed
under the measurement columns of the menu; these are described in the section on the
relevant protection function.
The P746 relay is able to measure and display the following quantities as summarized.
• Phase Currents
There are also measured values from the protection functions, which are also displayed
under the measurement columns of the menu; these are described in the section on the
relevant protection function.
Measurements and Recording
P746/EN MR/J43
MiCOM P40 Agile P746
1.4.2
(MR) 8-9
Measured Currents
The P746 relay produces current values. They are produced directly from the DFT (Discrete
Fourier Transform) used by the relay protection functions and present both magnitude and
phase angle measurement.
1.4.3
Sequence Voltages and Currents
Sequence quantities are produced by the P746 relay from the measured Fourier values;
these are displayed as magnitude and phase angle values.
1.4.4
Settings
The following settings under the heading measurement set-up can be used to configure the
relay measurement function.
Menu Text
Default Settings
Available settings
MEASUREMENT SETUP
Description / Phase Voltage / Date and Time /
Plant reference / Frequency / Access Level
This setting can be used to select the default display from a range of options, note that it is also possible to view the
other default displays whilst at the default level using the left and right keys. However, once the 15 minute timeout
elapses the default display will revert to that selected by this setting.
Local Values
Primary
Primary/Secondary
This setting controls whether measured values via the front panel user interface and the front courier port are
displayed as primary or secondary quantities.
Remote Values
Primary
Primary/Secondary
This setting controls whether measured values via the rear communication port are displayed as primary or secondary
quantities.
IA1 / IB1 / IC1 / VA / VB / VC / IA2 / IB2 / IC2 /
IA3 / IB3 / IC3 / IA4 / IB4 / IC4 / IA5 / IB5 / IC5 /
Measurement ref
VA
IA6 / IB6 / IC6
This menu sets the reference of the measure (phase reference and angle)
Measurement Mode
0
0/1/2/3
Used to set the mode of measurement, according to the following diagram:
Default Display
1.4.5
Description
Measurement Display Quantities
There are “Measurement” columns available in the relay for viewing measurement quantities.
These can also be viewed with S1 Agile.
MEASUREMENTS 1
One box configuration
IA-1 Magnitude
IA-1 Phase Angle
IB-1 Magnitude
IB-1 Phase Angle
IC-1 Magnitude
IC-1 Phase Angle
IA-2 Magnitude
IA-2 Phase Angle
IB-2 Magnitude
IB-2 Phase Angle
MEASUREMENTS 2
Three box configuration
IX-1 Magnitude
IX-1 Phase Angle
IX-2 Magnitude
IX-2 Phase Angle
IX-3 Magnitude
IX-3 Phase Angle
IX-4 Magnitude
IX-4 Phase Angle
IX-5 Magnitude
IX-5 Phase Angle
IA Z1 Diff
IB Z1 Diff
IC Z1 Diff
IA Z1 Bias
IB Z1 Bias
IC Z1 Bias
IA Z2 Diff
MR
P746/EN MR/J43
Measurements and Recording
(MR) 8-10
MiCOM P40 Agile P746
MEASUREMENTS 1
One box configuration
MR
IC-2 Magnitude
IC-2 Phase Angle
IA-3 Magnitude
IA-3 Phase Angle
IB-3 Magnitude
IB-3 Phase Angle
IC-3 Magnitude
IC-3 Phase Angle
IA-4 Magnitude
IA-4 Phase Angle
IB-4 Magnitude
IB-4 Phase Angle
IC-4 Magnitude
IC-4 Phase Angle
IA-5 Magnitude
IA-5 Phase Angle
IB-5 Magnitude
IB-5 Phase Angle
IC-5 Magnitude
IC-5 Phase Angle
IA-6 Magnitude
IA-6 Phase Angle
IB-6 Magnitude
IB-6 Phase Angle
IC-6 Magnitude
IC-6 Phase Angle
I0-1 Magnitude
I1-1 Magnitude
I2-1 Magnitude
IN-1 Derived Mag
IN-1 Derived Ang
I0-2 Magnitude
I1-2 Magnitude
I2-2 Magnitude
IN-2 Derived Mag
IN-2 Derived Ang
I0-3 Magnitude
I1-3 Magnitude
I2-3 Magnitude
IN-3 Derived Mag
IN-3 Derived Ang
I0-4 Magnitude
I1-4 Magnitude
I2-4 Magnitude
IN-4 Derived Mag
IN-4 Derived Ang
I0-5 Magnitude
I1-5 Magnitude
I2-5 Magnitude
IN-5 Derived Mag
IN-5 Derived Ang
I0-6 Magnitude
I1-6 Magnitude
I2-6 Magnitude
MEASUREMENTS 2
Three box configuration
IX-6 Magnitude
IX-6 Phase Angle
IX-7 Magnitude
IX-7 Phase Angle
IX-8 Magnitude
IX-8 Phase Angle
IX-9 Magnitude
IX-9 Phase Angle
IX-10 Magnitude
IX-10 Phase Angle
IX-11 Magnitude
IX-11 Phase Angle
IX-12 Magnitude
IX-12 Phase Angle
IX-13 Magnitude
IX-13 Phase Angle
IX-14 Magnitude
IX-14 Phase Angle
IX-15 Magnitude
IX-15 Phase Angle
IX-16 Magnitude
IX-16 Phase Angle
IX-17 Magnitude
IX-17 Phase Angle
IX-18 Magnitude
IX-18 Phase Angle
IB Z2 Diff
IC Z2 Diff
IA Z2 Bias
IB Z2 Bias
IC Z2 Bias
IA CZ Diff
IB CZ Diff
IC CZ Diff
IA CZ Bias
IB CZ Bias
IC CZ Bias
Measurements and Recording
P746/EN MR/J43
MiCOM P40 Agile P746
(MR) 8-11
MEASUREMENTS 1
One box configuration
Three box configuration
MEASUREMENTS 2
IN-6 Derived Mag
IN-6 Derived Ang
VAN Magnitude
VAN Phase Angle
VBN Magnitude
VBN Phase Angle
VCN Magnitude
VCN Phase Angle
V1 Magnitude
V2 Magnitude
V0 Magnitude
VN Derived Mag
VN Derived Angle
VAB Magnitude
VAB Phase Angle
VBC Magnitude
VBC Phase Angle
VCA Magnitude
VCA Phase Angle
VAN RMS
VBN RMS
VCN RMS
Frequency
MR
P746/EN MR/J43
(MR) 8-12
MR
Measurements and Recording
MiCOM P40 Agile P746
Firmware Design
P746/EN FD/J43
MiCOM P40 Agile P746
(FD) 9-1
FIRMWARE DESIGN
FD
Hardware Suffix:
Software Version:
M
91
P746/EN FD/J43
(FD) 9-2
FD
Firmware Design
MiCOM P40 Agile P746
Firmware Design
MiCOM P40 Agile P746
P746/EN FD/J43
(FD) 9-3
CONTENTS
1
HARDWARE ARCHITECTURE
5
2
MECHANICAL IMPLEMENTATION
6
2.1
Housing Variants
6
2.2
List of Boards
7
3
BOARDS AND MODULES
8
3.1
PCBs
8
3.2
Subassemblies
8
3.3
Main Processor Board
9
3.4
Power Supply Board
10
3.4.1
Watchdog
12
3.4.2
Rear Serial Port
12
3.5
Input Module - 1 Transformer Board
13
3.5.1
Input Module Circuit Description
14
3.5.2
Transformer Board
16
3.5.3
Input Board
16
3.6
Standard Output Relay Board
17
3.7
IRIG-B Board
18
3.9
Rear Communication Board
20
3.10
Redundant Ethernet Board
20
3.11
High Break Output Relay Board
22
4
SOFTWARE DESIGN OVERVIEW
24
5
SYSTEM LEVEL SOFTWARE
25
5.1
Real Time Operating Software
25
5.2
System Services Software
25
5.3
Self Diagnostic Software
25
5.4
Start-Up Self-Testing
25
5.4.1
System Boot
25
5.4.2
System Level Software Initialization
25
5.4.3
Platform Software Initialisation and Monitoring
26
5.5
Continuous Self-Testing
26
6
PLATFORM SOFTWARE
28
6.1
Record Logging
28
6.2
Settings Database
28
6.3
Interfaces
28
7
PROTECTION AND CONTROL FUNCTIONS
29
7.1
Overview - Protection and Control Scheduling
29
7.2
Topology Processing
29
7.3
Acquisition of Samples
29
7.4
Frequency Tracking
29
FD
P746/EN FD/J43
(FD) 9-4
Firmware Design
MiCOM P40 Agile P746
7.5
Direct Use of Sample Values
29
7.6
Fourier Signal Processing
30
7.7
Programmable Scheme Logic
30
7.8
Event Recording
31
7.9
Disturbance Recorder
31
7.10
Function Key Interface
31
FIGURES
FD
Figure 1: Hardware architecture
5
Figure 2: Exploded view of relay
6
Figure 3: Rear connection to terminal block
8
Figure 4: Main processor board
9
Figure 5: Power supply board
10
Figure 6: Power supply assembly
11
Figure 7: Power supply terminals
11
Figure 8: Watchdog contact terminals
12
Figure 9: Rear serial port terminals
13
Figure 10: Input module - 1 transformer board
13
Figure 11: Input module schematic
14
Figure 12: Main input board
15
Figure 13: Transformer board
16
Figure 14: Input board
16
Figure 15: Standard output relay board – 8 contacts
17
Figure 16: High Break relay output board
18
Figure 17: Fibre optic board
19
Figure 18: Rear communication board
20
Figure 19: Redundant Ethernet board
20
Figure 20: High Break relay output board
22
Figure 21: High break contact operation
23
Figure 22: Software architecture
24
Figure 23: Frequency response (indicative only)
30
Firmware Design
P746/EN FD/J43
MiCOM P40 Agile P746
HARDWARE ARCHITECTURE
The main components comprising devices based on the Px4x platform are as follows:
• The housing, consisting of a front panel and connections at the rear
• The Main processor module consisting of the main CPU (Central Processing Unit),
memory and an interface to the front panel HMI (Human Machine Interface)
• A selection of plug-in boards and modules with presentation at the rear for the power
supply, communication functions, digital I/O, analogue inputs, and time
synchronisation connectivity
All boards and modules are connected by a parallel data and address bus, which allows the
processor module to send and receive information to and from the other modules as
required. There is also a separate serial data bus for conveying sampled data from the input
module to the CPU. These parallel and serial databuses are shown as a single
interconnection module in the following figure, which shows typical modules and the flow of
data between them.
LEDs
Front port
Memory
Flash memory for settings
Backed-up SRAM
for records
Watchdog
contacts
+ LED
Watchdog module
Auxiliary
Supply
PSU module
Opto-input boards
Note: Not all modules are applicable to all products
V00233
Figure 1: Hardware architecture
Output relay contacts
Digital inputs
I/O
Interconnection
LCD
Output relay boards
Processor module
Keypad
Front panel HMI
1
(FD) 9-5
CTs
Power system currents
VTs
Power system voltages
Analogue Inputs
RS485 modules
RS485 communication
IRIG-B module
Time synchronisation
Ethernet modules
Communications
Ethernet communication
FD
P746/EN FD/J43
Firmware Design
(FD) 9-6
2
MiCOM P40 Agile P746
MECHANICAL IMPLEMENTATION
All products based on the Px4x platform have common hardware architecture. The hardware
is modular and consists of the following main parts:
• Case and terminal blocks
• Boards and modules
• Front panel
The case comprises the housing metalwork and terminal blocks at the rear. The boards
fasten into the terminal blocks and are connected together by a ribbon cable. This ribbon
cable connects to the processor in the front panel.
The following diagram shows an exploded view of a typical product. The diagram shown
does not necessarily represent exactly the product model described in this manual.
Figure 2: Exploded view of relay
FD
2.1
Housing Variants
The Px4x range of products are implemented in a range of case sizes. Case dimensions for
industrial products usually follow modular measurement units based on rack sizes. These
are: U for height and TE for width, where:
● 1U = 1.75 inches = 44.45 mm
● 1TE = 0.2 inches = 5.08 mm
The products are available in panel-mount or standalone versions. All products are nominally
4U high. This equates to 177.8 mm or 7 inches.
The cases are pre-finished steel with a conductive covering of aluminium and zinc. This
provides good grounding at all joints, providing a low resistance path to earth that is
essential for performance in the presence of external noise.
The case width depends on the product type and its hardware options. There are three
different case widths for the described range of products: 40TE, 60TE and 80TE. The case
dimensions and compatibility criteria are as follows:
Case width (TE)
Case width (mm)
Case width (inches)
40TE
203.2
8
60TE
304.8
12
80TE
406.4
16
Note: The P746 is only available in 80TE.
Firmware Design
P746/EN FD/J43
MiCOM P40 Agile P746
2.2
(FD) 9-7
List of Boards
The product's hardware consists of several modules drawn from a standard range. The
exact specification and number of hardware modules depends on the model number and
variant. Depending on the exact model, the product in question will use a selection of the
following boards.
Board
Use
Main Processor board – 60TE or larger
Power supply board 24/54V DC
Power supply board - 48/125V DC
Power supply board 110/250V DC
Transformer board
Input board
Input board with opto-inputs
Opto-input board
Output relay board
Combined Opto-input / Output relay board
IRIG-B board - modulated
IRIG-B - demodulated input
Fibre optic board
Main Processor board – with support for function keys
Power supply input. Accepts DC voltage between 24V and 54V
Power supply input. Accepts DC voltage between 48V and 125V
Power supply input. Accepts DC voltage between 110V and 125V
Contains the voltage and current transformers
Contains the A/D conversion circuitry
Contains the A/D conversion circuitry + 8 digital opto-inputs
Contains 8 digital opto-inputs
Contains 8 digital output relays
Contains 4 digital opto-inputs and 4 digital output relays
Interface board for modulated IRIG-B timing signal
Interface board for demodulated IRIG-B timing signal
Interface board for fibre-based RS485 connection
Interface board for fibre-based RS485 connection + demodulated
Fibre optic board + IRIG-B
IRIG-B
2nd rear communications board
Interface board for RS232 / RS485 connections
2nd rear communications board with IRIG-B input Interface board for RS232 / RS485 + IRIG-B connections
Redundant Ethernet RSTP + PRP + HSR + Failover + Redundant Ethernet running RSTP + PRP + HSR + Failover (two fibre
pairs), with onboard universal IRIG-B
universal IRIG-B
Redundant Ethernet RSTP + PRP + HSR + Failover +
universal IRIG-B
Redundant Ethernet RSTP + PRP + HSR + Failover +
universal IRIG-B
Output relay output board (8 outputs)
High Break Output Relay Board
Redundant Ethernet running RSTP + PRP + HSR + Failover (two
copper pairs), with on-board universal IRIG-B
Redundant Ethernet running RSTP + PRP + HSR + Failover (one
copper, one multimode fibre), with on-board universal IRIG-B
Standard output relay board with 8 outputs
Output relay board with high breaking capacity relays
FD
P746/EN FD/J43
Firmware Design
(FD) 9-8
3
MiCOM P40 Agile P746
BOARDS AND MODULES
Each product comprises a selection of PCBs (Printed Circuit Boards) and subassemblies,
depending on the chosen configuration.
3.1
PCBs
A PCB typically consists of the components, a front connector for connecting into the main
system parallel bus via a ribbon cable, and an interface to the rear. This rear interface may
be:
• Directly presented to the outside world (as is the case for communication boards such
as Ethernet Boards)
• Presented to a connector, which in turn connects into a terminal block bolted onto the
rear of the case (as is the case for most of the other board types)
R00226
FD
Figure 3: Rear connection to terminal block
3.2
Subassemblies
A sub-assembly consists of two or more boards bolted together with spacers and connected
with electrical connectors. It may also have other special requirements such as being
encased in a metal housing for shielding against electromagnetic radiation.
Boards are designated by a part number beginning with ZN, whereas pre-assembled subassemblies are designated with a part number beginning with GN. Sub-assemblies, which
are put together at the production stage, do not have a separate part number.
The products in the Px40 series typically contain two sub-assemblies:
• The power supply assembly comprising:
 A power supply board
 An output relay board
• The input module comprising:
 One or more transformer boards, which contains the voltage and current transformers
(partially or fully populated)
 One or more input boards
 Metal protective covers for EM (electromagnetic) shielding
The input module is pre-assembled and is therefore assigned a GN number, whereas the
power supply module is assembled at production stage and does not therefore have an
individual part number.
Firmware Design
P746/EN FD/J43
MiCOM P40 Agile P746
3.3
(FD) 9-9
Main Processor Board
Figure 4: Main processor board
The main processor board performs all calculations and controls the operation of all other
modules in the relay, including the data communication and user interfaces. This is the only
board that does not fit into one of the slots.
It resides in the front panel and connects to the rest of the system using an internal ribbon
cable.
The LCD and LEDs are mounted on the processor board along with the front panel
communication ports.
The memory on the main processor board is split into two categories: volatile and nonvolatile. The volatile memory is fast access SRAM, used by the processor to run the software
and store data during calculations. The non-volatile memory is sub-divided into two groups:
• Flash memory to store software code, text and configuration data including the
present setting values.
• Supercapacitor-backed SRAM to store disturbance, event, fault and maintenance
record data.
There are two board types available depending on the size of the case:
• For models in 40TE cases
• For models in 60TE cases and larger
FD
P746/EN FD/J43
(FD) 9-10
3.4
Firmware Design
MiCOM P40 Agile P746
Power Supply Board
Figure 5: Power supply board
FD
The power supply board provides power to the unit. One of three different configurations of
the power supply board can be fitted to the unit. This is specified at the time of order and
depends on the magnitude of the supply voltage that will be connected to it.
There are three board types, which support the following voltage ranges:
• 24/54 V DC
• 48/125 V DC or 40-100V AC
• 110/250 V DC or 100-240V AC
The power supply board connector plugs into a medium duty terminal block. This terminal
block is always positioned on the right hand side of the unit looking from the rear.
The power supply board is usually assembled together with a relay output board to form a
complete subassembly, as shown in the following diagram.
Firmware Design
MiCOM P40 Agile P746
P746/EN FD/J43
(FD) 9-11
Figure 6: Power supply assembly
The power supply outputs are used to provide isolated power supply rails to the various
modules within the unit.
Three voltage levels are used by the unit’s modules:
• 5.1 V for all of the digital circuits
• +/- 16 V for the analogue electronics such as on the input board
• 22 V for driving the output relay coils.
All power supply voltages, including the 0 V earth line, are distributed around the unit by the
64-way ribbon cable.
The power supply board incorporates inrush current limiting. This limits the peak inrush
current to approximately 10 A.
Power is applied to pins 1 and 2 of the terminal block, where pin 1 is negative and pin 2 is
positive. The pin numbers are clearly marked on the terminal block as shown in the following
diagram.
Figure 7: Power supply terminals
FD
P746/EN FD/J43
(FD) 9-12
3.4.1
Firmware Design
MiCOM P40 Agile P746
Watchdog
The Watchdog contacts are also hosted on the power supply board. The Watchdog facility
provides two output relay contacts, one normally open and one normally closed. These are
used to indicate the health of the device and are driven by the main processor board, which
continually monitors the hardware and software when the device is in service.
Figure 8: Watchdog contact terminals
3.4.2
FD
Rear Serial Port
The rear serial port (RP1) is housed on the power supply board. This is a three-terminal
EIA(RS)485 serial communications port and is intended for use with a permanently wired
connection to a remote control centre for SCADA communication. The interface supports
half-duplex communication and provides optical isolation for the serial data being transmitted
and received.
The physical connectivity is achieved using three screw terminals; two for the signal
connection, and the third for the earth shield of the cable. These are located on pins 16, 17
and 18 of the power supply terminal block, which is on the far right looking from the rear. The
interface can be selected between RS485 and K-bus. When the K-Bus option is selected,
the two signal connections are not polarity conscious.
The polarity independent K-bus can only be used for the Courier data protocol. The polarity
conscious MODBUS, IEC 60870-5-103 and DNP3.0 protocols need RS485.
The following diagram shows the rear serial port. The pin assignments are as follows:
• Pin 16: Earth shield
• Pin 17: Negative signal
• Pin 18: Positive signal
Firmware Design
P746/EN FD/J43
MiCOM P40 Agile P746
(FD) 9-13
Figure 9: Rear serial port terminals
An additional serial port with D-type presentation is available as an optional board, if
required.
3.5
Input Module - 1 Transformer Board
FD
Figure 10: Input module - 1 transformer board
The input module consists of the main input board coupled together with an instrument
transformer board. The instrument transformer board contains the voltage and current
transformers, which isolate and scale the analogue input signals delivered by the system
transformers. The input board contains the A/D conversion and digital processing circuitry,
as well as eight digital isolated inputs (opto-inputs).
The boards are connected together physically and electrically. The module is encased in a
metal housing for shielding against electromagnetic interference.
P746/EN FD/J43
Firmware Design
(FD) 9-14
3.5.1
MiCOM P40 Agile P746
Input Module Circuit Description
Optical
Isolator
8 digital inputs
Noise
filter
Optical
Isolator
Noise
filter
Parallel Bus
Buffer
Transformer
board
VT
or
CT
A/D Converter
Serial
interface
Serial Link
VT
or
CT
V00239
Figure 11: Input module schematic
FD
A/D Conversion
The differential analogue inputs from the CT and VT transformers are presented to the main
input board as shown.
Each differential input is first converted to a single input quantity referenced to the input
board’s earth potential.
The analogue inputs are sampled and converted to digital, then filtered to remove unwanted
properties. The samples are then passed through a serial interface module which outputs
data on the serial sample data bus.
The calibration coefficients are stored in non-volatile memory. These are used by the
processor board to correct for any amplitude or phase errors introduced by the transformers
and analogue circuitry.
Opto-isolated inputs
The other function of the input board is to read in the state of the digital inputs. As with the
analogue inputs, the digital inputs must be electrically isolated from the power system. This
is achieved by means of the 8 on-board optical isolators for connection of up to 8 digital
signals. The digital signals are passed through an optional noise filter before being buffered
and presented to the unit’s processing boards in the form of a parallel data bus.
This selectable filtering allows the use of a pre-set filter of ½ cycle which renders the input
immune to induced power-system noise on the wiring. Although this method is secure it can
be slow, particularly for inter-tripping. This can be improved by switching off the ½ cycle filter,
in which case one of the following methods to reduce ac noise should be considered.
• Use double pole switching on the input
• Use screened twisted cable on the input circuit
The opto-isolated logic inputs can be configured for the nominal battery voltage of the circuit
for which they are a part, allowing different voltages for different circuits such as signalling
and tripping.
Firmware Design
P746/EN FD/J43
MiCOM P40 Agile P746
Note:
(FD) 9-15
The opto-input circuitry can be provided without the A/D circuitry as a
separate board, which can provide supplementary opto-inputs.
The P746 provides eighteen current inputs (6 times 3 phases or 18 times single phase).
FD
Figure 12: Main input board
P746/EN FD/J43
(FD) 9-16
3.5.2
Firmware Design
MiCOM P40 Agile P746
Transformer Board
Figure 13: Transformer board
The transformer board hosts the current and voltage transformers. These are used to step
down the currents and voltages originating from the power systems' current and voltage
transformers to levels that can be used by the devices' electronic circuitry. In addition to this,
the on-board CT and VT transformers provide electrical isolation between the unit and the
power system.
The transformer board is connected physically and electrically to the input board to form a
complete input module.
FD
For terminal connections, please refer to the wiring diagrams.
3.5.3
Input Board
Figure 14: Input board
Firmware Design
P746/EN FD/J43
MiCOM P40 Agile P746
(FD) 9-17
The input board is used to convert the analogue signals delivered by the current and voltage
transformers into digital quantities used by the relay. This input board also has on-board
opto-input circuitry, providing eight optically isolated digital inputs and associated noise
filtering and buffering. These opto-inputs are presented to the user by means of a MD
terminal block, which sits adjacent to the analogue inputs HD terminal block.
The input board is connected physically and electrically to the transformer board to form a
complete input module.
The terminal numbers of the opto-inputs are as follows:
Terminal Number
3.6
Opto-input
Terminal 1
Opto 1 -ve
Terminal 2
Opto 1 +ve
Terminal 3
Opto 2 -ve
Terminal 4
Opto 2 +ve
Terminal 5
Opto 3 -ve
Terminal 6
Opto 3 +ve
Terminal 7
Opto 4 -ve
Terminal 8
Opto 4 +ve
Terminal 9
Opto 5 -ve
Terminal 10
Opto 5 +ve
Terminal 11
Opto 6 -ve
Terminal 12
Opto 6 +ve
Terminal 13
Opto 7 –ve
Terminal 14
Opto 7 +ve
Terminal 15
Opto 8 –ve
Terminal 16
Opto 8 +ve
Terminal 17
Common
Terminal 18
Common
Standard Output Relay Board
Figure 15: Standard output relay board – 8 contacts
This output relay board has 8 relays with 6 Normally Open contacts and 2 Changeover
contacts.
FD
P746/EN FD/J43
Firmware Design
(FD) 9-18
MiCOM P40 Agile P746
The output relay board is provided together with the power supply board as a complete
assembly, or independently for the purposes of relay output expansion.
There are two cut-out locations in the board. These can be removed to allow power supply
components to protrude when coupling the output relay board to the power supply board. If
the output relay board is to be used independently, these cut-out locations remain intact.
The terminal numbers are as follows:
Terminal Number
3.7
Output Relay
Terminal 1
Relay 1 NO
Terminal 2
Relay 1 NO
Terminal 3
Relay 2 NO
Terminal 4
Relay 2 NO
Terminal 5
Relay 3 NO
Terminal 6
Relay 3 NO
Terminal 7
Relay 4 NO
Terminal 8
Relay 4 NO
Terminal 9
Relay 5 NO
Terminal 10
Relay 5 NO
Terminal 11
Relay 6 NO
Terminal 12
Relay 6 NO
Terminal 13
Relay 7 changeover
Terminal 14
Relay 7 changeover
Terminal 15
Relay 7 common
Terminal 16
Relay 8 changeover
Terminal 17
Relay 7 changeover
Terminal 18
Relay 8 common
IRIG-B Board
FD
Figure 16: High Break relay output board
The IRIG-B board can be fitted to provide an accurate timing reference for the device. The
IRIG-B signal is connected to the board via a BNC connector. The timing information is used
to synchronise the relay's internal real-time clock to an accuracy of 1 ms. The internal clock
is then used for time tagging events, fault, maintenance and disturbance records.
Firmware Design
P746/EN FD/J43
MiCOM P40 Agile P746
(FD) 9-19
IRIG-B interface is available in modulated or demodulated formats.
The IRIG-B facility is provided in combination with other functionality on a number of
additional boards, such as:
• Fibre board with IRIG-B
• Second rear communications board with IRIG-B
• Ethernet board with IRIG-B
• Redundant Ethernet board with IRIG-B
There are three types of each of these boards; one type which accepts a modulated IRIG-B
input, one type which accepts a demodulated IRIG-B input and one type which accepts a
universal IRIG-B input.
3.8
Fibre Optic Board
R00244
Figure 17: Fibre optic board
This board provides an interface for communicating with a master station. This
communication link can use all compatible protocols (Courier, IEC 60870-5-103, MODBUS
and DNP 3.0). It is a fibre-optic alternative to the metallic RS485 port presented on the
power supply terminal block. The metallic and fibre optic ports are mutually exclusive.
The fibre optic port uses BFOC 2.5 ST connectors.
The board comes in two varieties; one with an IRIG-B input and one without:
FD
P746/EN FD/J43
(FD) 9-20
3.9
Firmware Design
MiCOM P40 Agile P746
Rear Communication Board
Figure 18: Rear communication board
The optional communications board containing the secondary communication ports provide
two serial interfaces presented on 9 pin D-type connectors. These interfaces are known as
SK4 and SK5. Both connectors are female connectors, but are configured as DTE ports.
This means pin 2 is used to transmit information and pin 3 to receive.
SK4 can be used with RS232, RS485 and K-bus. SK5 can only be used with RS232 and is
used for electrical teleprotection. The optional rear communications board and IRIG-B board
are mutually exclusive since they use the same hardware slot. However, the board comes in
two varieties; one with an IRIG-B input and one without.
3.10
Redundant Ethernet Board
FD
Figure 19: Redundant Ethernet board
This board provides dual redundant Ethernet together with an IRIG-B interface for timing.
Different board variants are available, depending on the redundancy protocol and the type of
IRIG-B signal (unmodulated and modulated). The available redundancy protocols are:
• RSTP (Rapid Spanning Tree Protocol)
• PRP (Parallel Redundancy Protocol)
Firmware Design
P746/EN FD/J43
MiCOM P40 Agile P746
(FD) 9-21
• HSR (High-availability Seamless Redundancy)
• Failover
There are several variants for this board as follows:
• 100 Mbps redundant Ethernet running RSTP + PRP + HSR + Failover (two fibre
pairs), with on-board universal IRIG-B
• 100 Mbps redundant Ethernet running RSTP + PRP + HSR + Failover (two copper
pairs), with on-board universal IRIG-B
• 100 Mbps redundant Ethernet running RSTP + PRP + HSR + Failover (one copper,
one multi-mode fibre), with on-board universal IRIG-B
The Ethernet and other connection details are described below:
IRIG-B Connector
• Centre connection: Signal
• Outer connection: Earth
Link Fail Connector (Ethernet Board Watchdog Relay)
Pin
Closed
Open
1-2
Link fail Channel 1 (A)
Link ok Channel 1 (A)
2-3
Link fail Channel 2 (B)
Link ok Channel 2 (B)
LEDs
LED
Function
On
Green
Link
Link ok
Yellow
Activity
Running
Off
Flashing
Link broken
PRP, RSTP
traffic
Optical Fibre Connectors (ST)
Connector
RSTP
PRP
HSR
A
RX1
RXA
RXA
B
TX1
TXA
TXA
C
RX2
RXB
RXB
D
TX2
TXB
TXB
FD
RJ45 connector
Pin
Signal name
Signal definition
1
TXP
Transmit (positive)
2
TXN
Transmit (negative)
3
RXP
Receive (positive)
4
-
Not used
5
-
Not used
6
RXN
Receive (negative)
7
-
Not used
8
-
Not used
P746/EN FD/J43
(FD) 9-22
3.11
Firmware Design
MiCOM P40 Agile P746
High Break Output Relay Board
Figure 20: High Break relay output board
A High Break output relay board is available as an option. It comprises four normally open
output contacts, which are suitable for high breaking loads.
A High Break contact consists of a high capacity relay with a MOSFET in parallel with it. The
MOSFET has a varistor placed across it to provide protection, which is required when
switching off inductive loads. This is because the stored energy in the inductor causes a high
reverse voltage that could damage the MOSFET, if not protected.
FD
When there is a control input command to operate an output contact the miniature relay is
operated at the same time as the MOSFET. The miniature relay contact closes in nominally
3.5 ms and is used to carry the continuous load current. The MOSFET operates in less than
0.2 ms, but is switched off after 7.5 ms.
When the control input is reset, the MOSFET is again turned on for 7.5 mS. The miniature
relay resets in nominally 3.5 ms before the MOSFET. This means the MOSFET is used to
break the load. The MOSFET absorbs the energy when breaking inductive loads and so
limits the resulting voltage surge. This contact arrangement is for switching DC circuits only.
The board number is:
• ZN0042 001
High Break Contact Operation
The following figure shows the timing diagram for High Break contact operation.
Firmware Design
P746/EN FD/J43
MiCOM P40 Agile P746
(FD) 9-23
P1981ENa
Figure 21: High break contact operation
High Break Contact Applications
• Efficient scheme engineering
In traditional hard wired scheme designs, High Break capability could only be achieved using
external electromechanical trip relays. Instead, these internal High Break contacts can be
used thus reducing space requirements.
• Accessibility of CB auxiliary contacts
It is common practise to use circuit breaker 52a (CB Closed) auxiliary contacts to break the
trip coil current on breaker opening, thereby easing the duty on the protection contacts. In
some cases (such as operation of disconnectors, or retrofitting), it may be that 52a contacts
are either unavailable or unreliable. In such cases, High Break contacts can be used to
break the trip coil current in these applications.
• Breaker fail
In the event of failure of the local circuit breaker (stuck breaker), or defective auxiliary
contacts (stuck contacts), it is incorrect to use 52a contact action. The interrupting duty at the
local breaker then falls on the relay output contacts, which may not be rated to perform this
duty. High Break contacts should be used in this case to avoid the risk of burning out relay
contacts.
• Initiation of teleprotection
The High Break contacts also offer fast making, which results in faster tripping. In addition,
fast keying of teleprotection is a benefit. Fast keying bypasses the usual contact operation
time, such that permissive, blocking and intertrip commands can be routed faster.
These relay contacts are POLARITY SENSITIVE. External wiring must
comply with the polarity requirements described in the external
connection diagram to ensure correct operation.
FD
P746/EN FD/J43
Firmware Design
(FD) 9-24
4
MiCOM P40 Agile P746
SOFTWARE DESIGN OVERVIEW
The device software can be considered to be made up of four sections:
• The system level software
• The platform software
• The protection and control software
These elements are not distinguishable to the user, and the distinction is made purely for the
purposes of explanation. The following figure shows the software architecture.
Protection and Control Software Layer
Protection Task
Programmable &
fixed scheme logic
Fourier signal
processing
Protection
algorithms
Fault locator
task
Disturbance
recorder task
Protection
and control
settings
Records
Supervisor task
Platform Software Layer
Event, fault,
disturbance,
maintenance record
logging
Sampling function
Settings database
Front panel
interface
(LCD + Keypad)
Sample data + digital
logic inputs
FD
Control of output contacts
and programmable LEDs
Remote
communications
interfaces
Local
communications
interfaces
Control of interfaces to keypad, LCD, LEDs,
front & rear ports.
Self-checking maintenance records
System Level Software Layer
System services (e.g. device drivers) / Real time operating system / Self-diagnostic software
Hardware Device Layer
LEDs / LCD / Keypad / Memory / FPGA
V00300
Figure 22: Software architecture
The software, which executes on the main processor, can be divided into a number of
functions as illustrated above. Each function is further broken down into a number of
separate tasks. These tasks are then run according to a scheduler. They are run at either a
fixed rate or they are event driven. The tasks communicate with each other as and when
required.
Firmware Design
MiCOM P40 Agile P746
5
SYSTEM LEVEL SOFTWARE
5.1
Real Time Operating Software
P746/EN FD/J43
(FD) 9-25
The real-time operating system is used to schedule the processing of the various tasks. This
ensures that they are processed in the time available and in the desired order of priority. The
operating system also plays a part in controlling the communication between the software
tasks, through the use of operating system messages.
5.2
System Services Software
The system services software provides the layer between the hardware and the higher-level
functionality of the platform software and the protection and control software. For example,
the system services software provides drivers for items such as the LCD display, the keypad
and the remote communication ports. It also controls things like the booting of the processor
and the downloading of the processor code into RAM at startup.
5.3
Self Diagnostic Software
The relay includes a number of self-monitoring functions to check the operation of its
hardware and software while in service. If there is a problem with the hardware or software, it
should be able to detect and report the problem, and attempt to resolve the problem by
performing a reboot. In this case, the device would be out of service for a short time, during
which the ‘Healthy’ LED on the front of the device is switched OFF and the watchdog contact
at the rear is ON. If the restart fails to resolve the problem, the unit takes itself permanently
out of service; the ‘Healthy’ LED stays OFF and watchdog contact stays ON.
If a problem is detected by the self-monitoring functions, the device attempts to store a
maintenance record to allow the nature of the problem to be communicated to the user.
The self-monitoring is implemented in two stages: firstly a thorough diagnostic check which
is performed on bootup, and secondly a continuous self-checking operation, which checks
the operation of the critical functions whilst it is in service.
5.4
Start-Up Self-Testing
The self-testing takes a few seconds to complete, during which time the relay's
measurement, recording, control, and protection functions are unavailable. On a successful
start-up and self-test, the ‘Healthy' state LED on the front of the device is switched on. If a
problem is detected during the start-up testing, the device remains out of service until it is
manually restored to working order.
The operations that are performed at start-up are:
1. System boot
2. System software initialisation
3. Platform software initialisation and monitoring
5.4.1
System Boot
The integrity of the flash memory is verified using a checksum before the program code and
stored data is loaded into RAM for execution by the processor. When the loading has been
completed, the data held in RAM is compared to that held in the Flash memory to ensure
that no errors have occurred in the data transfer and that the two are the same. The entry
point of the software code in RAM is then called. This is the relay's initialisation code.
5.4.2
System Level Software Initialization
The initialization process includes the operations of initializing the processor registers and
interrupts, starting the watchdog timers (used by the hardware to determine whether the
software is still running), starting the real-time operating system and creating and starting the
supervisor task. In the course of the initialization process the relay checks:
• The status of the supercapacitor
• The integrity of the supercapacitor-backed SRAM that is used to store event, fault and
disturbance records
FD
P746/EN FD/J43
(FD) 9-26
Firmware Design
MiCOM P40 Agile P746
• The voltage level of the field voltage supply which is used to drive the opto-isolated
inputs
• The operation of the LCD controller
• The watchdog operation
When the initialization software routine is complete the supervisor task starts the platform
software.
5.4.3
Platform Software Initialisation and Monitoring
When starting the platform software, the relay checks the following:
• The integrity of the data held in non-volatile memory using checksum
• The operation of the real-time clock,
• The optional IRIG-B board (if applicable)
• The presence and condition of the input board
• The analogue data acquisition system (it does this by sampling the reference voltage)
At the successful conclusion of all of these tests the relay is entered into service and the
protection started-up.
5.5
Continuous Self-Testing
When the relay is in service, it continually checks the operation of the critical parts of its
hardware and software. The checking is carried out by the system services software and the
results are reported to the platform software. The functions that are checked are as follows:
• The Flash memory containing all program code and language text is verified by a
checksum.
• The code and constant data held in system memory is checked against the
corresponding data in Flash memory to check for data corruption.
• The system memory containing all data other than the code and constant data is
verified with a checksum.
FD
• The integrity of the digital signal I/O data from the opto-inputs and the output relay
coils is checked by the data acquisition function every time it is executed.
• The operation of the analog data acquisition system is continuously checked by the
acquisition function every time it is executed. This is done by sampling the reference
voltages.
• The operation of the optional Ethernet board is checked by the software on the main
processor card. If the
• Ethernet board fails to respond an alarm is raised and the card is reset in an attempt
to resolve the problem.
• The operation of the optional IRIG-B function is checked by the software that reads
the time and date from the board.
• Where fitted, the operation of the RTD board is checked by reading the temperature
indicated by the reference resistors on the two spare RTD channels
• Where fitted, the operation of the CLIO board is checked
In the event that one of the checks detects an error in any of the subsystems, the platform
software is notified and it attempts to log a maintenance record.
If the problem is with the IRIG-B board, the device continues in operation. For problems
detected in any other area, the device initiates a shutdown and re-boot, resulting in a period
of up to 10 seconds when the functionality is unavailable.
A restart should clear most problems that may occur. If, however, the diagnostic self-check
detects the same problem that caused the relay to restart, it is clear that the restart has not
cleared the problem, and the device takes itself permanently out of service. This is indicated
Firmware Design
MiCOM P40 Agile P746
P746/EN FD/J43
(FD) 9-27
by the ‘’health-state’ LED on the front of the device, which switches OFF, and the watchdog
contact which switches ON.
FD
P746/EN FD/J43
(FD) 9-28
6
Firmware Design
MiCOM P40 Agile P746
PLATFORM SOFTWARE
The platform software has three main functions:
• To control the logging of records that are generated by the protection software,
including alarms and event, fault, and maintenance records.
• To store and maintain a database of all of the relay’s settings in non-volatile memory.
• To provide the internal interface between the settings database and the user
interfaces, using the front panel interface and the front and rear communication ports
6.1
Record Logging
The logging function is used to store all alarms, events, faults and maintenance records. The
records are stored in non-volatile memory to provide a log of what has happened. The relay
maintains four types of logs on a first in first out basis (FIFO). These are:
• Alarms
• Event records
• Fault records
• Maintenance records
The logs are maintained such that the oldest record is overwritten with the newest record.
The logging function can be initiated from the protection software. The platform software is
responsible for logging a maintenance record in the event of a relay failure. This includes
errors that have been detected by the platform software itself or errors that are detected by
either the system services or the protection software function.
6.2
Settings Database
The settings database contains all the settings and data for the relay, which are stored in
non-volatile memory. The platform software manages the settings database and ensures
that only one user interface can modify the settings at any one time. This is a necessary
restriction to avoid conflict between different parts of the software during a setting change.
Changes to protection settings and disturbance recorder settings, are first written to a
temporary location SRAM memory. This is sometimes called 'Scratchpad' memory. These
settings are not written into non-volatile memory immediately. This is because a batch of
such changes should not be activated one by one, but as part of a complete scheme. Once
the complete scheme has been stored in SRAM, the batch of settings can be committed to
the non-volatile memory where they will become active.
FD
6.3
Interfaces
The settings and measurements database must be accessible from all of the interfaces to
allow read and modify operations. The platform software presents the data in the appropriate
format for each of the interfaces (LCD display, keypad and all the communications
interfaces).
Firmware Design
MiCOM P40 Agile P746
7
P746/EN FD/J43
(FD) 9-29
PROTECTION AND CONTROL FUNCTIONS
The protection and control software task processes all of the protection elements and
measurement functions. To achieve this it has to communicate with the system services
software, the platform software as well as organize its own operations.
The protection software has the highest priority of any of the software tasks in the relay in
order to provide the fastest possible protection response.
The protection and control software provides a supervisory task, which controls the start-up
of the task and deals with the exchange of messages between the task and the platform
software.
7.1
Overview - Protection and Control Scheduling
The P746 relay contains two global protections, busbar protection and circuit breaker failure,
and additional functions such as overcurrent protection.
7.2
Topology Processing
Topology algorithm determines dynamically the electric scheme of the substation from the
auxiliary contact of circuit breaker and isolators. At the end of process, the P746 knows the
node of current and zone to trip according to the fault location.
7.3
Acquisition of Samples
After initialization, the protection and control task waits until there are enough samples to
process. The acquisition of samples on the main processor board is controlled by a
‘sampling function’ which is called by the system services software.
This sampling function takes samples from the input module and stores them in a two-cycle
FIFO buffer. The sample rate is 24 samples per cycle. This results in a nominal sample rate
of 1,200 samples per second for a 50 Hz system and 1,440 samples per second for a 60 Hz
system. However the sample rate is not fixed. It tracks the power system frequency as
described in the next section.
7.4
Frequency Tracking
The device provides a frequency tracking algorithm so that there are always 24 samples per
cycle irrespective of frequency drift within a certain frequency range (see technical
specifications). If the frequency falls outside this range, the sample rate reverts to its default
rate of 1200 Hz for 50 Hz or 1440 Hz for 60 Hz.
The frequency tracking of the analog input signals is achieved by a recursive Fourier
algorithm which is applied to one of the input signals. It works by detecting a change in the
signal’s measured phase angle. The calculated value of the frequency is used to modify the
sample rate being used by the input module, in order to achieve a constant sample rate per
cycle of the power waveform. The value of the tracked frequency is also stored for use by
the protection and control task.
The frequency tracks off any voltage or current in the order VA, VB, VC, IA, IB, IC, down to
10%Vn for voltage and 5%In for current.
7.5
Direct Use of Sample Values
Most of the relay’s protection functionality uses the Fourier components calculated by the
device’s signal processing software. However RMS measurements and some special
protection algorithms available in some products use the sampled values directly.
The disturbance recorder also uses the samples from the input module, in an unprocessed
form. This is for waveform recording and the calculation of true RMS values of current,
voltage and power for metering purposes.
In the case of special protection algorithms, using the sampled values directly provides
exceptionally fast response because you do not have to wait for the signal processing task to
calculate the fundamental. You can act on the sampled values immediately.
FD
P746/EN FD/J43
(FD) 9-30
7.6
Firmware Design
MiCOM P40 Agile P746
Fourier Signal Processing
When the protection and control task is re-started by the sampling function, it calculates the
Fourier components for the analog signals. Although some protection algorithms use some
Fourier-derived harmonics (e.g. second harmonic for magnetizing inrush), most protection
functions are based on the Fourier-derived fundamental components of the measured
analog signals. The Fourier components of the input current and voltage signals are stored
in memory so that they can be accessed by all of the protection elements’ algorithms.
The Fourier components are calculated using single-cycle Fourier algorithm. This Fourier
algorithm always uses the most recent 24 samples from the 2-cycle buffer.
Most protection algorithms use the fundamental component. In this case, the Fourier
algorithm extracts the power frequency fundamental component from the signal to produce
its magnitude and phase angle. This can be represented in either polar format or rectangular
format, depending on the functions and algorithms using it.
The Fourier function acts as a filter, with zero gain at DC and unity gain at the fundamental,
but with good harmonic rejection for all harmonic frequencies up to the nyquist frequency.
Frequencies beyond this Nyquist frequency are known as alias frequencies, which are
introduced when the sampling frequency becomes less than twice the frequency component
being sampled. However, the Alias frequencies are significantly attenuated by an antialiasing filter (low pass filter), which acts on the analog signals before they are sampled. The
ideal cut-off point of an anti-aliasing low pass filter would be set at:
(samples per cycle) ´ (fundamental frequency)/2
At 24 samples per cycle, this would be nominally 600 Hz for a 50 Hz system, or 720 Hz for a
60 Hz system. The following figure shows the nominal frequency response of the anti-alias
filter and the Fourier filter for a 24- sample single cycle fourier algorithm acting on the
fundamental component:
FD
Figure 23: Frequency response (indicative only)
7.7
Programmable Scheme Logic
The purpose of the programmable scheme logic (PSL) is to allow you to configure your own
protection schemes to suit your particular application. This is done with programmable logic
gates and delay timers. To allow greater flexibility, different PSL is allowed for each of the
four setting groups.
The input to the PSL is any combination of the status of the digital input signals from the
opto-isolators on the input board, the outputs of the protection elements such as protection
starts and trips, and the outputs of the fixed protection scheme logic (FSL). The fixed
scheme logic provides the standard protection schemes. The PSL consists of software logic
gates and timers. The logic gates can be programmed to perform a range of different logic
functions and can accept any number of inputs. The timers are used either to create a
programmable delay, and/or to condition the logic outputs, such as to create a pulse of fixed
duration on the output regardless of the length of the pulse on the input. The outputs of the
PSL are the LEDs on the front panel of the relay and the output contacts at the rear.
Firmware Design
MiCOM P40 Agile P746
P746/EN FD/J43
(FD) 9-31
The execution of the PSL logic is event driven. The logic is processed whenever any of its
inputs change, for example as a result of a change in one of the digital input signals or a trip
output from a protection element. Also, only the part of the PSL logic that is affected by the
particular input change that has occurred is processed. This reduces the amount of
processing time that is used by the PSL. The protection & control software updates the logic
delay timers and checks for a change in the PSL input signals every time it runs.
The PSL can be configured to create very complex schemes. Because of this PSL desing is
achieved by means of a PC support package called the PSL Editor. This is available as part
of the settings application software MiCOM S1 Agile, or as a standalone software module.
7.8
Event Recording
A change in any digital input signal or protection element output signal is used to indicate
that an event has taken place. When this happens, the protection and control task sends a
message to the supervisor task to indicate that an event is available to be processed and
writes the event data to a fast buffer controlled by the supervisor task.
When the supervisor task receives an event record, it instructs the platform software to
create the appropriate log in non-volatile memory (backed-up SRAM). The operation of the
record logging to backed-up SRAM is slower than the supervisor buffer. This means that the
protection software is not delayed waiting for the records to be logged by the platform
software. However, in the rare case when a large number of records to be logged are
created in a short period of time, it is possible that some will be lost, if the supervisor buffer is
full before the platform software is able to create a new log in backed-up SRAM. If this
occurs then an event is logged to indicate this loss of information.
Maintenance records are created in a similar manner, with the supervisor task instructing the
platform software to log a record when it receives a maintenance record message. However,
it is possible that a maintenance record may be triggered by a fatal error in the relay in which
case it may not be possible to successfully store a maintenance record, depending on the
nature of the problem.
7.9
Disturbance Recorder
The disturbance recorder operates as a separate task from the protection and control task. It
can record the waveforms of the calibrated analog channels, plus the values of the digital
signals. The recording time is user selectable up to a maximum of 10.5 seconds. The
disturbance recorder is supplied with data by the protection and control task once per cycle,
and collates the received data into the required length disturbance record. The disturbance
records can be extracted using application software or the SCADA system, which can also
store the data in COMTRADE format, allowing the use of other packages to view the
recorded data.
7.10
Function Key Interface
The ten function keys interface directly into the PSL as digital input signals. A change of
state is only recognized when a key press is executed on average for longer than 200 ms.
The time to register a change of state depends on whether the function key press is
executed at the start or the end of a protection task cycle, with the additional hardware and
software scan time included. A function key press can provide a latched (toggled mode) or
output on key press only (normal mode) depending on how it is programmed and can be
configured to individual protection scheme requirements. The latched state signal for each
function key is written to non-volatile memory and read from non-volatile memory during
relay power up thus allowing the function key state to be reinstated after power-up should
relay power be inadvertently lost.
FD
Commissioning
P746/EN CM/J43
MiCOM P40 Agile P746
(CM) 10-1
COMMISSIONING
Hardware Suffix:
M
Software Version:
91
CM
P746/EN CM/J43
(CM) 10-2
CM
Commissioning
MiCOM P40 Agile P746
Commissioning
MiCOM P40 Agile P746
P746/EN CM/J43
(CM) 10-3
CONTENTS
1
INTRODUCTION
7
2
SETTING FAMILIARISATION
8
3
EQUIPMENT REQUIRED FOR COMMISSIONING
9
3.1
Minimum Equipment Required
9
3.2
Optional Equipment
9
4
PRODUCT CHECKS
10
4.1
With the Relay De-energised
10
4.1.1
Visual Inspection
11
4.1.2
Current Transformer Shorting Contacts
11
4.1.3
Insulation
12
4.1.4
External Wiring
13
4.1.5
Watchdog Contacts
13
4.1.6
Power Supply
13
4.2
With the Relay Energised
14
4.2.1
Watchdog Contacts
14
4.2.2
Test LCD
14
4.2.3
Date and Time
14
4.2.4
Test LEDs
15
4.2.4.1
Test Alarm and Out of Service LEDs
15
4.2.4.2
Test Trip LED
15
4.2.4.3
Test User-programmable LEDS
15
4.2.5
Field Voltage Supply
16
4.2.6
Test Opto-inputs
16
4.2.7
Test Output Relays
16
4.2.8
Rear Communications Port
17
4.2.8.1
Courier Communications
17
4.2.9
Second Rear Communications Port
17
4.2.9.1
K-Bus Configuration
17
4.2.9.2
EIA(RS)485 Configuration
18
4.2.9.3
EIA(RS)232 Configuration
18
4.2.10
Test Current Inputs
18
5
COMMISSIONING TEST MENU
20
5.1
Test Mode Cell
20
5.2
Test Zone Mode by Setting
20
5.3
Test Zone Mode by PSL
20
6
SETTING CHECKS
22
6.1
Apply Application-specific Settings
22
6.2
Demonstrate Correct Relay Operation
22
6.2.1
Current Differential Bias Characteristic
22
CM
P746/EN CM/J43
(CM) 10-4
Commissioning
MiCOM P40 Agile P746
6.2.2
Connect the Test Circuit
23
6.2.2.1
If 1 Current is available
23
6.2.2.2
If 2 Currents are available
24
6.2.2.3
Slopes and Thresholds
29
6.2.3
Phase Overcurrent Protection
29
6.2.3.1
Connect the Test Circuit
30
6.2.4
Breaker Failure Protection
31
6.2.4.1
Separate External 50BF Protection to the Busbar Protection
31
6.2.4.2
External Initiation of BF Protection
31
6.2.4.3
CB Unavailable:
32
6.2.4.4
Internal Initiation Breaker Failure Protection
32
6.3
Check Application Settings
33
7
IEC 61850 EDITION 2 TESTING
34
7.1
Using IEC 61850 Edition 2 Test Modes
34
7.1.1
IED Test Mode Behaviour
34
7.1.2
Sampled Value Test Mode Behaviour
34
7.2
Simulated Input Behaviour
35
7.3
Testing Examples
36
7.3.1
Test Procedure for Real Values
36
7.3.2
Test Procedure for Simulated values - No Plant
37
7.3.3
Test Procedure for Simulated Values - with Plant
38
7.3.4
Contact Test
39
8
ON-LOAD CHECKS
40
8.1
Confirm Current Transformer Wiring
40
9
FINAL CHECKS
41
CM
FIGURES
Figure 1: Rear terminal blocks on P746
11
Figure 2: Location of securing screws for heavy duty terminal blocks.
12
Figure 3: Terminal CB1 trip mapping
20
Figure 4: Test mode
21
Figure 3: Connection for Bias Characteristic Testing
23
Figure 4: Connection for Bias Characteristic Testing
24
Figure 7: Simulated input behaviour
36
Figure 8: Test example 1
37
Figure 9: Test example 2
38
Figure 10: Test example 3
39
Commissioning
MiCOM P40 Agile P746
P746/EN CM/J43
(CM) 10-5
TABLES
Table 1: Current transformer shorting contact locations.
12
Table 2: Watchdog contact status
13
Table 3: Operational range of auxiliary supply Vx.
13
Table 4: Field voltage terminals
16
Table 5: CT ratio settings
19
Table 6: Characteristic operating times for Ι>1
30
CM
P746/EN CM/J43
(CM) 10-6
CM
Commissioning
MiCOM P40 Agile P746
Commissioning
P746/EN CM/J43
MiCOM P40 Agile P746
1
(CM) 10-7
INTRODUCTION
The MiCOM P746 Busbar Differential Protection is fully numerical in its design, implementing
all protection and non-protection functions in software. The relay employs a high degree of
self-checking and, in the unlikely event of a failure, will give an alarm. As a result the
commissioning tests do not need to be as extensive as with non-numeric electronic or
electromechanical relays.
To commission numerical relays, it is only necessary to verify that the hardware is
functioning correctly and the application-specific software settings have been applied to the
relay (PSL, topology, differential and breaker failure protection linked to the topology/PSL). It
is considered unnecessary to test every function of the relay if the settings have been
verified by one of the following methods:
Extracting the settings applied to the relay using appropriate setting software
(preferred method) such as S1 Agile.
• through the operator interface (HMI)
Unless previously agreed to the contrary, the customer will be responsible for determining
the application-specific settings to be applied to the relay and for testing of any scheme logic
applied by external wiring and/or configuration of the relay’s internal programmable scheme
logic.
Blank commissioning test and setting records are provided at the end of this chapter for
completion as required.
As the relay’s menu language is user-selectable, it is acceptable for the Commissioning
Engineer to change it to allow accurate testing as long as the menu is restored to the
customer’s preferred language on completion.
To simplify the specifying of menu cell locations in these Commissioning Instructions, they
will be given in the form [courier reference: COLUMN HEADING, Cell Text]. For example,
the cell for selecting the menu language (first cell under the column heading) is located in the
System Data column (column 00) so it would be given as [SYSTEM DATA, Language].
Before carrying out any work on the equipment, the user should be
familiar with the contents of the safety section/safety guide
SFTY/4LM as well as the ratings on the equipment rating label.
CM
P746/EN CM/J43
(CM) 10-8
2
Commissioning
MiCOM P40 Agile P746
SETTING FAMILIARISATION
When first commissioning a P746 relay, allow sufficient time to become familiar with how to
apply the settings.
With the secondary front cover in place all keys except the enter key are accessible. All
menu cells can be read. LEDs and alarms can be reset. However, no protection or
configuration settings can be changed, or fault and event records cleared.
Removing the secondary front cover allows access to all keys so that settings can be
changed, LEDs and alarms reset, and fault and event records cleared. However, to make
changes to the menu cells that have access levels higher than the default level, the
appropriate password is needed.
Alternatively, if a portable PC with suitable setting software is available (S1 Agile), the menu
can be viewed one page at a time to display a full column of data and text. This PC software
also allows settings to be entered more easily, saved to a file on a digital medium for future
reference or printed to produce a setting record. Refer to the PC software user manual for
details. If the software is being used for the first time, allow sufficient time to become familiar
with its operation.
CM
Commissioning
P746/EN CM/J43
MiCOM P40 Agile P746
(CM) 10-9
3
EQUIPMENT REQUIRED FOR COMMISSIONING
3.1
Minimum Equipment Required
• Overcurrent test set with interval timer
• Multimeter with suitable ac current range, and ac and dc voltage ranges of
0 – 440V and 0 – 250V respectively
• Continuity tester (if not included in the multimeter)
Note:
3.2
Modern test equipment may contain many of the above features in one unit.
Optional Equipment
• Multi-finger test plug type P992 (if test block type P991 installed) or MMLB (if using
MMLG blocks)
• An electronic or brushless insulation tester with a dc output not exceeding 500V (for
insulation resistance testing when required). This equipment will be required only if the
dielectric test has not been done during the manufacturing process.
• A portable PC, with appropriate software. This enables the rear communications port
to be tested, if this is to be used, and will also save considerable time during
commissioning.
• A printer
CM
P746/EN CM/J43
Commissioning
(CM) 10-10
4
MiCOM P40 Agile P746
PRODUCT CHECKS
These product checks cover all aspects of the relay which should be checked to ensure that
it has not been physically damaged prior to commissioning, is functioning correctly and all
input quantity measurements are within the stated tolerances.
If the application-specific settings have been applied to the relay prior to commissioning, it is
advisable to make a copy of the settings so as to allow their restoration later. This could be
done by:
• Obtaining a setting file from the customer.
• Extracting the settings from the relay itself, using a portable PC with appropriate
setting software.
If the customer has changed the password that prevents unauthorised changes to some of
the settings, either the revised password should be provided, or the original password
restored before testing.
Note:
4.1
If the password has been lost, a recovery password can be obtained from
GE.
With the Relay De-energised
The following group of tests should be carried out without the auxiliary
supply being applied to the relay and with the trip circuit isolated.
The current and voltage transformer connections must be isolated from the relay for these
checks. If a P991 test block is provided, the required isolation can be achieved by inserting
test plug type P992. This open circuits all wiring routed through the test block, except CT
circuits which are automatically short circuited.
Never open-circuit the secondary circuit of a current transformer since
the high voltage produced may be lethal and could damage insulation.
CM
Before carrying out any work on the equipment, the user should be
familiar with the contents of the safety section/safety guide SFTY/4LM as
well as the ratings on the equipment rating label.
If a test block is not provided, the voltage transformer supply to the relay should be isolated
by means of the panel links or connecting blocks. The line current transformers should be
short-circuited and disconnected from the relay terminals. Where means of isolating the
auxiliary supply and trip circuit (for example, isolation links, fuses, MCB) are provided, these
should be used. If this is not possible, the wiring to these circuits will have to be
disconnected and the exposed ends suitably terminated to prevent them from being a safety
hazard.
Commissioning
P746/EN CM/J43
MiCOM P40 Agile P746
4.1.1
(CM) 10-11
Visual Inspection
Carefully examine the relay to see that no physical damage has occurred since installation.
The rating information given under the top access cover on the front of the relay should be
checked to ensure it is correct for the particular installation.
Ensure that the case earthing connections, bottom left-hand corner at the rear of the relay
case, are used to connect the relay to a local earth bar using an adequate conductor.
4.1.2
Current Transformer Shorting Contacts
Check the current transformer shorting contacts to ensure that they close when the heavyduty terminal block is disconnected from the current input board.
Figure 1: Rear terminal blocks on P746
Slot
A
B
C
D
E
F
G
H
J
K
L
M
Description
IRIG B/Ethernet/COMMS
Opto/high break
Opto/high break
Sigma Delta analogue input board
Sigma Delta Opto Board
Sigma Delta analogue input board
Sigma Delta Opto Board
Relay/Opto/high break
Relay/high break
Relay/high break
Relay/high break
Power supply board
The heavy-duty terminal blocks are fastened to the rear panel using four crosshead screws.
These are located two at the top and two at the bottom.
Note:
Use a magnetic bladed screwdriver to minimise the risk of the screws being
left in the terminal block or lost.
CM
P746/EN CM/J43
Commissioning
(CM) 10-12
MiCOM P40 Agile P746
Figure 2: Location of securing screws for heavy duty terminal blocks.
Pull the terminal block away from the rear of the case and check with a continuity tester that
all the shorting switches being used are closed.
The table below shows the terminals between which shorting contacts are fitted.
Current input
one box mode
CM
three box mode
Shorting contact between terminals
ΙA(1)
ΙA(1) (or IB(1) or IC(1))
D23 – D24
ΙB(1)
ΙA(2) (or IB(2) or IC(2))
D25 – D26
ΙC(1)
ΙA(3) (or IB(3) or IC(3))
D27 – D28
ΙA(2)
ΙA(4) (or IB(4) or IC(4))
D17 – D18
ΙB(2)
ΙA(5) (or IB(5) or IC(5))
D19 – D20
ΙC(2)
ΙA(6) (or IB(6) or IC(6))
D21 – D22
ΙA(3)
ΙA(7) (or IB(7) or IC(7))
D11 – D12
ΙB(3)
ΙA(8) (or IB(8) or IC(8))
D13 – D14
ΙC(3)
ΙA(9) (or IB(9) or IC(9))
D15 – D16
ΙA(4)
ΙA(10) (or IB(10) or IC(10))
F23 – F24
ΙB(4)
ΙA(11) (or IB(11) or IC(11))
F25 – F26
ΙC(4)
ΙA(12) (or IB(12) or IC(12))
F27 – F28
ΙA(5)
ΙA(13) (or IB(13) or IC(13))
F17 – F18
ΙB(5)
ΙA(14) (or IB(14) or IC(14))
F19 – F20
ΙC(5)
ΙA(15) (or IB(15) or IC(15))
F21 – F22
ΙA(6)
ΙA(16) (or IB(16) or IC(16))
F11 – F12
ΙB(6)
ΙA(17) (or IB(17) or IC(17))
F13 – F14
ΙC(6)
ΙA(18) (or IB(18) or IC(18))
F15 – F16
Table 1: Current transformer shorting contact locations.
4.1.3
Insulation
Insulation resistance tests are only necessary during commissioning if if explicitly requested.
Isolate all wiring from the earth and test the insulation with an electronic or brushless
insulation tester at a dc voltage not exceeding 500 V. Terminals of the same circuits should
be temporarily connected together.
The main groups of relay terminals are:
Commissioning
P746/EN CM/J43
MiCOM P40 Agile P746
(CM) 10-13
• Current transformer circuits
• Auxiliary voltage supply
• Field voltage output and opto-isolated control inputs
• Relay contacts
• Case earth
The insulation resistance should be greater than 100 MΩ at 500 V.
On completion of the insulation resistance tests, ensure all external wiring is correctly
reconnected to the relay.
4.1.4
External Wiring
Check that the external wiring is correct to the relevant relay diagram or
wiring diagram. Ensure that phasing/phase rotation appears to be as
expected.
If a P991 test block is provided, the connections should be checked against the scheme
(wiring) diagram. It is recommended that the supply connections are to the live side of the
test block [coloured orange with the odd numbered terminals (1, 3, 5, 7 etc.). The auxiliary
supply is normally routed via terminals 13 (supply positive) and 15 (supply negative), with
terminals 14 and 16 connected to the relay’s positive and negative auxiliary supply terminals
respectively. However, check the wiring against the schematic diagram for the installation to
ensure compliance with the customer’s normal practice.
4.1.5
Watchdog Contacts
Using a continuity tester, check that the watchdog contacts are in the states given in the
following table for a de-energised relay.
Terminals
M11 – M12
M13 – M14
Contact state Relay de-energised
Closed
Open
Table 2: Watchdog contact status
4.1.6
Power Supply
Depending on its nominal supply rating the P746 relay can be operated from either a DC
only or an AC/DC auxiliary supply. The incoming voltage must be within the operating range
specified in the table below.
Without energising the relay measure the auxiliary supply to ensure it is within the operating
range.
Nominal supply rating DC [AC rms]
24 – 48V
48 – 110V
110 – 250V
[–]
[30 – 100V]
[100 – 240V]
DC operating range
19 to 65V
37 to 150V
87 to 300V
AC operating range
24 to 110V
80 to 265V
Table 3: Operational range of auxiliary supply Vx.
Note:
The relay can withstand an AC ripple of up to 12% of the upper rated voltage
on the DC auxiliary supply.
CM
P746/EN CM/J43
Commissioning
(CM) 10-14
MiCOM P40 Agile P746
Do not energise the relay using the battery charger with the battery
disconnected as this can irreparably damage the relay’s power supply
circuitry.
Energise the relay only if the auxiliary supply is within the operating
range. If a test block is provided, it may be necessary to link across the
front of the test plug to connect the auxiliary supply to the relay.
4.2
With the Relay Energised
The current and voltage transformer connections must remain isolated
from the relay for these checks. The trip circuit should also remain
isolated to prevent accidental operation of the associated circuit breaker.
The following group of tests verifies that the relay hardware and software is functioning
correctly and should be carried out with the auxiliary supply applied to the relay.
4.2.1
Watchdog Contacts
Using a continuity tester, check the watchdog contacts are in the states given in Table 2 for
an energised relay.
Terminals
M11 – M12
M13 – M14
4.2.2
Contact state Relay energised
Open
Closed
Test LCD
The Liquid Crystal Display (LCD) is designed to operate in a wide range of substation
ambient temperatures. For this purpose, the relays have an LCD Contrast setting. The
contrast is factory pre-set, but it may be necessary to adjust the contrast to give the best inservice display.
CM
To change the contrast, you can increment or decrement the LCD Contrast cell in the
CONFIGURATION column.
Before applying a contrast setting, make sure that it will not make the
display so light or dark such that menu text becomes unreadable. It is
possible to restore the visibility of a display by downloading a setting file,
with the LCD Contrast set within the typical range of 7 - 11.
4.2.3
Date and Time
The date and time is stored in memory, which is backed up by a supercapacitor.
The method for setting the date and time depends on whether an IRIG-B signal is being
used or not. The IRIG-B signal will override the time, day and month settings, but not the
initial year setting. For this reason, you must ensure you set the correct year, even if the
device is using IRIG-B to maintain the internal clock.
Set the Date and Time by one of the following methods:
• Using the front panel to set the Date and Time cells respectively
• By sending a courier command to the Date/Time cell (Courier reference 0801)
Commissioning
P746/EN CM/J43
MiCOM P40 Agile P746
Note:
(CM) 10-15
If the auxiliary supply fails, the time and date will be maintained by the
supercapacitor. Therefore, when the auxiliary supply is restored, you should
not have to set the time and date again. To test this, remove the IRIG-B
signal, and then remove the auxiliary supply. Leave the device de-energised
for approximately 30 seconds. On re energisation, the time should be
correct.
When using IRIG-B to maintain the clock, the device must first be connected to the satellite
clock equipment (usually a P594/RT430), which should be energised and functioning.
1. Set the IRIG-B Sync cell in the DATE AND TIME column to Enabled.
2. Ensure the relay is receiving the IRIG-B signal by checking that cell IRIG-B Status
reads Active.
3. Once the IRIG-B signal is active, adjust the time offset of the universal co coordinated
time (satellite clock time) on the satellite clock equipment so that local time is
displayed.
4. Check that the time, date and month are correct in the Date/Time cell. The IRIG-B
signal does not contain the current year so it will need to be set manually in this cell.
5. Reconnect the IRIG-B signal.
If the time and date is not being maintained by an IRIG-B signal, ensure that the IRIG-B
Sync cell in the DATE AND TIME column is set to Disabled.
1. Set the date and time to the correct local time and date using Date/Time cell or using
the serial protocol.
4.2.4
Test LEDs
On power-up the green LED should switch on and stay on, indicating that the relay is
healthy. The relay has non-volatile memory which remembers the state (on or off) of the
alarm, trip and, if configured to latch, user-programmable LED indicators when the relay was
last energised from an auxiliary supply. Therefore, these indicators may also illuminate when
the auxiliary supply is applied.
If any of these LEDs are on, reset them before proceeding with further testing. If the LEDs
successfully reset (the LED goes out), there is no testing required for that LED because it is
known to be operational.
Note:
4.2.4.1
It is likely that alarms related to the communications channels will not reset
at this stage.
Test Alarm and Out of Service LEDs
The alarm and out of service LEDs can be tested using the COMMISSION TESTS menu
column.
1. Set cell [COMMISSION TESTS, Test Mode] to Out Of Service on the P746.
2. Check that the out of service LED illuminates continuously and the alarm LED flashes.
It is not necessary to return cell the Test Mode cell Disabled at this stage because the test
mode will be required for later tests.
4.2.4.2
Test Trip LED
The trip LED can be tested by initiating a manual circuit breaker trip. However, the trip LED
will operate during the setting checks performed later. Therefore, no further testing of the trip
LED is required at this stage.
4.2.4.3
Test User-programmable LEDS
To test the user-programmable LEDs, set the Test LEDs to Apply Test. Check that all the
LEDs on the relay illuminate.
In the P746:
CM
P746/EN CM/J43
Commissioning
(CM) 10-16
MiCOM P40 Agile P746
• The ‘Red LED Status’ cell is an eighteen bit binary string that indicates which of the
user-programmable LEDs on the relay are illuminated when accessing the relay from
a remote location, a ‘1’ indicating a particular Red LED is lit.
• The ‘Green LED Status’ cell is an eighteen bit binary string that indicates which of the
user-programmable LEDs on the relay are illuminated when accessing the relay from
a remote location, a ‘1’ indicating a particular Green LED is lit.
• If a ‘Red LED Status’ cell AND the same ‘Green LED Status’ cell are at ‘1’ the
particular LED is lit Orange
• If a ‘Red LED Status’ cell AND the same ‘Green LED Status’ cell are at ‘0’ the
particular LED is not lit.
4.2.5
Field Voltage Supply
The relay generates a field voltage of nominally 48 V dc that can be used to energise the
opto-isolated inputs (alternatively the substation battery may be used).
Measure the field voltage across the terminals 7 and 9 on the terminal block given in Table
4. Check that the field voltage is within the range 40 V to 60 V when no load is connected
and that the polarity is correct.
Repeat for terminals 8 and 10.
Supply rail
+ve
–ve
Terminals
M7 & M8
M9 & M10
Table 4: Field voltage terminals
4.2.6
Test Opto-inputs
This test checks that all the opto-inputs on the relay are functioning correctly.
The opto-inputs should be energised one at a time, For terminal numbers, please see the
external connection diagrams in Appendix. Ensuring correct polarity, connect the field supply
voltage to the appropriate terminals for the input being tested.
Note:
CM
The opto-isolated inputs may be energised from an external DC auxiliary
supply (e.g. the station battery) in some installations. Check that this is not
the case before connecting the field voltage otherwise damage to the relay
may result.
The status of each opto-isolated input can be viewed using either cell [SYSTEM DATA,
Opto I/P Status] or [COMMISSION TESTS, Opto I/P Status].
A ‘1’ indicates an energised input and a ‘0’ indicates a de-energised input. When each optoisolated input is energized, one of the characters on the bottom line of the display will
change to indicate the new state of the input.
4.2.7
Test Output Relays
This test checks that all the output relays are functioning correctly.
1. Ensure that the relay is still in test mode by viewing cell [COMMISSION TESTS, Test
Mode] to ensure that it is set to Blocked.
2. The output relays should be energised one at a time. To select output relay 1 for
testing, set cell [COMMISSION TESTS, Test Pattern] as appropriate.
3. Connect a continuity tester across the terminals corresponding to output relay 1 as
given in external connection diagram.
4. To operate the output relay set cell COMMISSION TESTS, Contact Test] to Apply
Test.
5. Check the operation with the continuity tester.
6. Measure the resistance of the contacts in the closed state.
Commissioning
P746/EN CM/J43
MiCOM P40 Agile P746
(CM) 10-17
7. Reset the output relay by setting cell [COMMISSION TESTS, Contact Test] to
Remove Test.
8. Return the relay to service by setting cell [COMMISSION TESTS, Test Mode] to
Disabled.
Note:
4.2.8
Ensure that thermal ratings of anything connected to the output relays during
the contact test procedure is not exceeded by the associated output relay
being operated for too long. It is therefore advised that the time between
application and removal of contact test is kept to the minimum.
Rear Communications Port
You need only perform this test if the IED is to be accessed from a remote location with a
permanent serial connection to the communications port. The scope of this test does not
extend to verifying operation with connected equipment beyond any supplied protocol
converter. It verifies operation of the rear communication port (and if applicable the protocol
converter) and varies according to the protocol fitted.
4.2.8.1
Courier Communications
If a K-Bus to EIA(RS)232 KITZ protocol converter is installed, connect a portable PC running
the appropriate software to the incoming (remote from relay) side of the protocol converter.
Ensure that the communications baud rate and parity settings in the application software are
set the same as those on the protocol converter (usually a KITZ but could be a SCADA
RTU).
The relays courier address in cell [0E02: COMMUNICATIONS, Remote Access] must be
set to a value between 1 and 254. Check that communications can be established with this
relay using the portable PC.
Check that, using the Master Station, communications with the relay can be established.
Note:
4.2.9
The first rear communication port (terminal M17-18) can be either K-Bus or
EIA(RS)485.
Second Rear Communications Port
You need only perform this test if the IED is to be accessed from a remote location with a
permanent serial connection to the communications port. The scope of this test does not
extend to verifying operation with connected equipment beyond any supplied protocol
converter. It verifies operation of the rear communication port (and if applicable the protocol
converter) and varies according to the protocol fitted.
4.2.9.1
K-Bus Configuration
If a K-Bus to EIA(RS)232 KITZ protocol converter is installed, connect a portable PC running
the appropriate software (S1 Agile) to the incoming (remote from relay) side of the protocol
converter.
If a KITZ protocol converter is not installed, it may not be possible to connect the PC to the
relay installed. In this case a KITZ protocol converter and portable PC running appropriate
software should be temporarily connected to the relays second rear communications port
configured for K-Bus. However, as the installed protocol converter is not being used in the
test, only the correct operation of the relays K-Bus port will be confirmed.
Ensure that the communications baud rate and parity settings in the application software are
set the same as those on the protocol converter (usually a KITZ but could be a SCADA
RTU).
1. The relays courier address in cell [0E90: COMMUNICATIONS, RP2 Address] must
be set to a value between 1 and 254.
2. The second rear communications port configuration [0E88: COMMUNICATIONS, RP2
Port Config.] must be set to K-Bus.
Check that communications can be established with this relay using the portable PC.
CM
P746/EN CM/J43
(CM) 10-18
4.2.9.2
Commissioning
MiCOM P40 Agile P746
EIA(RS)485 Configuration
If an EIA(RS)485 to EIA(RS)232 converter (CK222) is installed, connect a portable PC
running the appropriate software (e.g. S1 Agile) to the EIA(RS)232 side of the converter and
the second rear communications port of the relay to the EIA(RS)485 side of the converter.
Ensure that the communications baud rate and parity settings in the application software are
set the same as those in the relay.
1. The relays courier address in cell [0E90:COMMUNICATIONS, RP2 Address] must be
set to a value between 1 and 254.
2. The second rear communications port configuration [0E88: COMMUNICATIONS,
RP2 Port Config.] must be set to EIA(RS)485.
Check that communications can be established with this relay using the portable PC.
4.2.9.3
EIA(RS)232 Configuration
Connect a portable PC running the appropriate S1 Agile software to the rear EIA(RS)2321
port of the relay.
The second rear communications port connects via the 9-way female D-type connector
(SK4). The connection is compliant to EIA(RS)574.
Connections to the second rear port configured for EIA(RS)232 operation can be made using
a screened multi-core communication cable up to 15m long, or a total capacitance of
2500pF. The cable should be terminated at the relay end with a 9-way, metal shelled, D-type
male plug.
Ensure that the communications baud rate and parity settings in the application software are
set the same as those in the relay.
1. The relays courier address in cell [0E90:COMMUNICATIONS, RP2 Address] must be
set to a value between 1 and 254.
2. The second rear communications port configuration [0E88: COMMUNICATIONS, RP2
Port Config.] must be set to EIA(RS)232.
Check that communications can be established with this relay using the portable PC.
4.2.10
Test Current Inputs
This test verifies that the current measurement inputs are configured correctly.
CM
All relays will leave the factory set for operation at a system frequency of 50Hz.
If operation at 60Hz is required then this must be set in cell [SYSTEM DATA, Frequency].
Apply current equal to the line current transformer secondary winding rating to each current
transformer input of the corresponding rating in turn, see Table 1 or external connection
diagram for appropriate terminal numbers,
1. Check its magnitude using a multimeter. Check this value against the value displayed
on the HMI panel (usually in MEASUREMENTS 1 column).
2. Record the displayed value. The measured current values will be either be in primary
or secondary Amperes. If cell [MEASURE’T SETUP, Local Values] is set to
‘Primary’, the values displayed should be equal to the applied current multiplied by
the corresponding current transformer ratio set in the ‘CT and VT RATIOS’ menu
column (see Table 5). If cell [MEASURE’T SETUP, Local Values] is set to
‘Secondary’, the value displayed should be equal to the applied current.
The measurement accuracy of the relay is ±5%. However, an additional allowance must be
made for the accuracy of the test equipment being used.
Commissioning
P746/EN CM/J43
MiCOM P40 Agile P746
(CM) 10-19
Corresponding CT Ratio
Cell in MEASUREMENTS 1 column (02)
[IA Magnitude]
[IB Magnitude]
[IC Magnitude]
(‘CT and VT RATIOS‘ column(0A) of menu)
[Phase CT Primary]__
[Phase CT Secondary]
Table 5: CT ratio settings
CM
P746/EN CM/J43
Commissioning
(CM) 10-20
MiCOM P40 Agile P746
5
COMMISSIONING TEST MENU
5.1
Test Mode Cell
This cell allows commissioning of busbar and general breaker failure protection. It also lets
you test the output contacts by applying menu controlled tests signals.
To go into test mode, select the Test Mode option in the Test Mode cell. This takes the IED
out of service causing an alarm condition to be recorded and the Out of Service LED to
illuminate. This also freezes any information stored in the CB CONDITION column. In IEC
60870-5-103 versions, it changes the Cause of Transmission (COT) to Test Mode.
In Test Mode, the output contacts are still active. To disable the output contacts you must
select the Contacts Blocked option.
Once testing is complete, return the device back into service by setting the Test Mode Cell
back to Disabled.
When the Test Mode cell is set to Enabled, the relay scheme logic does
not drive the output relays and so the P746 will not trip the associated
circuit breaker if a busbar fault occurs (COMMISSIONING MODE 1 and 2).
However, the communications channels with remote relays remain active,
which, if suitable precautions are not taken, could lead to the remote
ends tripping when current transformers are isolated or injection tests
are performed.
5.2
Test Zone Mode by Setting
The Test Zone mode is used to select the Zone which will be commissioned. When Test
Zone cells are set for a Zone then 87BB-DZ and 50BF protection continues to operate but
blocks all tripping output DDB connected to the Zone selected.
When the Test Zone setting is set to a dedicated Zone, DDB output signal Z1 In Test Mode
is set to 1 and the related DDB output Terminal are Tx In Test Mode (x=1,2, … to 18) are
also set to 1.
By PSL, these DDB signals are configured to block tripping output DDB on 87BB and 50BF
protection. For instance, default PSL is defined like this:
CM
P4979ENa
Figure 3: Terminal CB1 trip mapping
5.3
Test Zone Mode by PSL
The following DDB input signals are available to force Zone commissioning whatever Test
Zone Setting.
Commissioning
MiCOM P40 Agile P746
P746/EN CM/J43
(CM) 10-21
DDB input signal Set Z1 Test Mode
DDB input signal Set Z2 Test Mode
When the above DDBs are set to 1, related Zx In Test Mode DDB output signal is set to 1
The default PSL file is as follows:
P4980ENa
Figure 4: Test mode
The P746 will force Z1 in commissioning mode when Function Key 2 will be pushed and
force LED2 to be activated.
As in §5.2, 87BB and 50BF are still operating but related Tripping Zone elements are
blocked.
CM
P746/EN CM/J43
Commissioning
(CM) 10-22
6
MiCOM P40 Agile P746
SETTING CHECKS
The setting checks ensure that all of the application-specific relay settings (both the relay’s
function and programmable scheme logic settings) have been correctly applied to the relay.
Note 1: The trip circuits should remain isolated during these checks to prevent
accidental operation of the associated circuit breaker.
Note 2: For busbar protection stability reasons, whatever is the maintenance mode
selected, the Check Zone will never be disabled. Therefore, the time to inject
current will be shorter than the ID>1 set timer to avoid Circuitry Fault alarms.
6.1
Apply Application-specific Settings
There are two methods of applying the settings to the relay:
• Transferring them from a pre-prepared setting file to the relay using a portable PC
running the appropriate software via the relay’s front EIA(RS)232 port, located under
the bottom access cover. This method is preferred for transferring function settings as
it is much faster and there is less margin for error. If the programmable scheme logic
other than the default settings with which the relay is supplied is to be used then this is
the only way of changing the settings. If a setting file has been created for the
particular application and provided on a digital medium, this will further reduce the
commissioning time and should always be the case where application-specific
programmable scheme logic is to be applied to the relay.
• Enter the settings manually using relay’s front panel HMI. This method is not suitable
for changing the programmable scheme logic.
Where the installation needs application-specific PSL, the relevant .psl
files, must be transferred to the relay, for each and every setting group
that will be used. If you do not do this, the factory default PSL will still be
resident. This may have severe operational and safety consequences.
6.2
Demonstrate Correct Relay Operation
The purpose of these tests is as follows:
• To determine that the primary protection function of the relay, current differential, can
trip according to the correct application settings.
CM
• To verify correct setting of any phase overcurrent protection.
• To verify correct assignment of the inputs, relays and trip contacts, by monitoring the
response to a selection of fault injections.
6.2.1
Current Differential Bias Characteristic
To avoid spurious operation of any Overcurrent, earth fault or breaker fail elements, these
should be disabled for the duration of the differential element tests. This is done in the relay’s
CONFIGURATION column. Ensure that cells, [Overcurrent Prot], [Earth Fault Prot] and
[CB Fail & I<] are all set to Disabled. Make a note of which elements need to be re-enabled
after testing.
Commissioning
P746/EN CM/J43
MiCOM P40 Agile P746
6.2.2
(CM) 10-23
Connect the Test Circuit
The following tests require an injection test set, which are able to feed the relay with one or
two currents variable in phase and magnitude.
6.2.2.1
If 1 Current is available
I2
T
Test
A
P746
Busbar
Protection
Box
P3749ENb
Figure 5: Connection for Bias Characteristic Testing
Ibias = Idiff = I2x = I
i diff(t)
2
B
Idiff = I2B = I
A
Idiff = I2A = I
S
ek
lop
C
pe k
o
l
S
Z
CM
Injection
45°
0
i bias
Ibias = I2A = I
Ibias = I2B = I
P3750ENc
An increasing current I2 is injected into a phase (and neutral) of the feeder 2 which is used
as differential and bias current.
Idiff = Ibias = I2
K2 : Zone percentage bias, Characteristic limit: Idiff = ID>2
KCZ : Check Zone percentage bias, Characteristic limit: Idiff = IDCZ>2
In this case, we increase I2 from 0 to A then B point until the differential element operates:
KCZ : Check Zone percentage bias, Characteristic limit: Idiff = IDCZ>2, point A
K2 : Zone percentage bias, Characteristic limit: Idiff = ID>2, point B
When we reach the point A the P746 LED 8 will operate and when we reach the point B the
differential element will operate.
P746/EN CM/J43
Commissioning
(CM) 10-24
MiCOM P40 Agile P746
Note 1: ID>1 alarm timer will be set to 100s during the test.
Note 2: This test does not allow checking the slopes but only the thresholds.
6.2.2.2
If 2 Currents are available
This method is preferred, whenever possible.
Note:
The 2 CTs can have different ratios. This must be taken into account when
injecting at the CT secondary side.
Figure 6: Connection for Bias Characteristic Testing
i diff(t)
2
Bz
CM
Az
Idiff = IA1- IA2 = I
Acz
Idiff = IA1- IA2 = I
Bcz
ek
p
o
Sl
pe
Slo
kCZ
Injections
45°
0
i bias
Ibias = I1 + I2 = constant
P3759ENc
Note:
The easiest way to test the thresholds is to inject an increasing slope for I1
and a decreasing slope for I2 . The Ibias = I1 + I2 is constant and I = Idiff= I2 - I1
is increasing.
Important: For the Check zone, the Ibias includes all the substation feeder currents.
Commissioning
P746/EN CM/J43
MiCOM P40 Agile P746
(CM) 10-25
To test the thresholds:
Ibias is fixed to a lowest value of ID>2/k2 and IDCZ>2/kCZ, the Az and Acz points will be ID>2
and IDCZ>2. So Ibias = I1 + I2 = fixed value (Points A)
3. To test the Differential slopes and Blocking algorithm:
Ibias is fixed to a value greater than ID>2/k2 and IDCZ>2/kCZ the Bz and Bcz points will be
Ibias x k2 and Ibias x kCZ. So Ibias = I1 + I2 = fixed value (Points B)
When we reach the point Xcz the P746 LED 8 will operate and when we reach the point Xz
the differential element will operate.
Important: This test simulates a current going out and a current going. The current
phase comparison algorithm will prevent the trip as long as the smallest injected
current is above x% of the nominal CT current (In):
Note:
Phase comparison threshold per feeder in Primary = PhComp PU Ratio
setting x ID>2 Current setting
The chosen Ibias must be lower than 2 x x% x In / (1- k2)*.
X% is the percentage of In current flowing through each CT above which the angle is taken
into account and is defined in the Excel Setting spreadsheet tool.
Example with CT of 2000/1:
CM
For example, if k2 is 60%, x% = 50% and if the CT ratio of the smallest injected current is
1000/1, Ibiasmax is 2500A (so ID>2 up to 1500 A).
For example, if k2 is 60%, x% = 50% and if the CT ratio of the smallest injected current is
500/1, Ibiasmax is 1250A (so ID>2 up to 750 A).
For example, if k2 is 60% x% = 40% and if the CT ratio of the smallest injected current is
1000/1, Ibiasmax is 2000A (so ID>2 up to 1200 A).
For example, if k2 is 60% x% = 40% and if the CT ratio of the smallest injected current is
500/1, Ibiasmax is 1000A (so ID>2 up to 600 A).
To calculate the phase comparison threshold pct, pct = (I1 – I2) / (I1 + I2)
The differential current will increase twice the value I.
Note 1: ID>1 alarm timer will be set to 100s during the test.
P746/EN CM/J43
(CM) 10-26
Commissioning
MiCOM P40 Agile P746
To test the tripping time, inject 4 × ID>2 at 60Hz and 3.5 × ID>2 at 50Hz whenever possible,
to ensure subcycle tripping times
*: for information:
During the injection: Ibias = I1 + I2 thus I1 = Ibias - I2 and I2 = x% of In thus I1 = Ibias - x% of In
To trip, IDiff must be ≥ k2 x Ibias, i.e. I1 - I2 ≥ k2 Ibias thus Ibias - x% of In - x% of In ≥ k2 Ibias
Conclusion: Ibias ≥ 2 times x% of In /(1 - k2)
1. To test the Differential slopes ONLY:
To check a slope of k%, the 2 following tests will be performed.
One showing no operation at m = 95% of k% and one showing operation at n = 105% of k%.
To avoid the blocking of the phase comparison algorithm, the following sequences will be
played (using state sequencer for example) with the smallest injected current below x% of In:
First test:
• Chose Ibias then Inject outgoing I1 = Ibias /2 and ingoing I2.= Ibias /2 for 10s (for example).
• Check on the P746 HMI Tool that the right Ibias is displayed and the differential current
is 0.
• Inject outgoing I1 = Ibias x (1 + m) / 2 and ingoing I2.= Ibias x (1 - m) / 2 for 40ms
• I2.must be lower than x% of In
• No trip
CM
Second test:
• Keep the same Ibias then Inject the same outgoing I1 and ingoing I2 for 10s (for
example).
• Check on the P746 HMI Tool that the right Ibias is displayed and the differential current
is 0.
• Inject outgoing I1 = Ibias x (1 + n) / 2 and ingoing I2.= Ibias x (1 - n) / 2 for 40 ms
• I2.must be lower than x% of In
• Trip
Commissioning
P746/EN CM/J43
MiCOM P40 Agile P746
Note:
(CM) 10-27
The same test can be performed to test the CZ signal either by mapping an
unlatched Led or a unlatched output relay on the Diff CZ Blked ddb.
Example:
Phase comparison threshold x% = 50%,
Busbar protection bias slope k% = 60% (thus m% = 57% and n% = 63%)
ID>2 = 1100 A (thus minimum bias current = ID>2/ k% = 1100 / 0.6 = 1834 A)
CT1 = 1000/1 (thus):
• Maximum current of 50% of 1000 A = 500 A to not be used by the phase comparison
• Maximum of bias current = 2 x I1./ (1 – n) = 2 x 500 / 0.43 = 2325 A
CT2 = 2000/1 (thus):
• Maximum current of 50% of 2000 A = 1000A to not be used by the phase comparison)
• Maximum of bias current = 2 x I2./ (1 – n) = 2 x 1000 / 0.43 = 4650 A
First test:
• Chose min Ibias = 2 kA (more than 1834 A and less than 4650 A)
• Inject outgoing I1 = 1000 A prim (1 A sec) and ingoing I2.= 1000 A prim (0.5 A sec) for
10s.
 I bias = 1000 + 1000 = 2000 A
 I diff = 1000 – 1000 = 0 A
• Check on the P746 HMI Tool that the right Ibias = 2 kA is displayed and the differential
current is 0.
• Inject outgoing I1 = 1570 A prim and ingoing I2.= 430 A prim for 40ms
 I bias = 1570 + 430 = 2000 A
 I diff = 1570 – 430 = 1140 A
 1140 A = 57% of 2000 A
• No trip
CM
P746/EN CM/J43
Commissioning
(CM) 10-28
MiCOM P40 Agile P746
Second test:
• Keep the same Ibias = 2 kA then Inject the same outgoing I1 and ingoing I2 for 10s.
• Check on the P746 HMI Tool that the right Ibias = 2 kA is displayed and the differential
current is 0.
 I bias = 1000 + 1000 = 2000 A
 I diff = 1000 – 1000 = 0 A
• Inject outgoing I1 = 0.815 A prim and ingoing I2.= 0.185 A prim for 40 ms
 I bias = 1630 + 370 = 2000 A
 I diff = 1630 – 370 = 1260 A
 1260 A = 63% of 2000 A
• Trip
Third test:
• Chose max Ibias = 4.5 kA (more than 1834 A and less than 4650 A)
• Inject outgoing I1 = 2250 A prim (2.25 A sec) and ingoing I2.= 2250 A prim (1.125 A
sec) for 10s.
 I bias = 2250 + 2250 = 4500 A
 I diff = 2250 – 2250 = 0 A
• Check on the P746 HMI Tool that the right Ibias = 9 kA is displayed and the differential
current is 0.
• Inject outgoing I1 = 3535.5A prim and ingoing I2.= 967.5 A prim for 40ms
 I bias = 3535.5 + 967.5 = 4500 A
 I diff = 3535.5 - 967.5 = 2565 A
 2565 A = 57% of 4500 A
• No trip
Fourth test:
• Keep the same Ibias = 4.5 kA then Inject the same outgoing I1 and ingoing I2 for 10s.
• Check on the P746 HMI Tool that the right Ibias = 2 kA is displayed and the differential
current is 0.
CM
 I bias = 2250 + 2250 = 4500 A
 I diff = 2250 – 2250 = 0 A
• Inject outgoing I1 = 3667.5 A prim and ingoing I2.= 832.5 A prim for 40 ms
 I bias = 3667.5+ 832.5= 4500 A
 I diff = 3667.5– 832.5= 2835 A
 2835 A = 63% of 4500 A
• Trip
1. To test the Phase comparison pick-up only:
When an unlatched Led or a unlatched output relay is mapped on a PhComp Blk Zx or
PhComp Blk Zx Y ddb, the 2 following tests can be performed.
Note:
PhCompBlk Zx ddb is an AND gate of the PhComp Blk Zx A, B, C ddbs so it
will only change for three phase test.
One showing no operation at m = 99% of x% and one showing operation at n = 101% of x%.
First test:
• Inject outgoing I1 = m% of CT1 and ingoing I2.= I1 for 10s (for example).
• No Led or relay output pick-up
Commissioning
P746/EN CM/J43
MiCOM P40 Agile P746
(CM) 10-29
Second test:
• Inject outgoing I1 = n% of CT1 and ingoing I2.= I1 for 10s (for example).
• Led or relay output pick-up
Note:
6.2.2.3
The same test can be performed to test it on the CZ using the adequate
DDBs.
Slopes and Thresholds
If an LED has been assigned to display the trip information they may be used to indicate
correct operation. If not, monitor option will need to be used, as described in the next
paragraph.
On P746 go to GROUP1-->BUSBAR PROTECT and set ID>1 Alarm timer to 100s
Go to the COMMISSION TESTS column in the menu, scroll down and change cells [Monitor
Bit 1] to [BUSBAR_TRIPPING]. The Test Port Status cell will set or reset the bits that now
represent BUSBAR_TRIPPING (with the rightmost bit representing Busbar Trip. From now
on monitor the Test Port Status cell. Make a note of which elements need to be re-enabled
or re-set after testing.
Test of ID>2:
ID>1 Alarm Timer should be set to 100s during testing.
Inject a I2 current smaller than ID>2 and slowly increase I2 until tripping.
Test of the operating time of the differential element:
Inject a I2 current greater than twice ID>2 threshold and measure the operating time of the
differential element.
Test of ID>1:
ID>1 Alarm Timer should be set to 100ms.
Inject a I2 current smaller than ID>1 and slowly increase I2 until circuit fault appears (LED
Alarm of LED circuitry fault).
Test of ID>1 Alarm Timer:
ID>1 Alarm Timer should be set to 5s.
Inject a I2 current greater than twice the ID>1 threshold and check that the Circuitry Fault
Alarm is coming in 5s.
6.2.3
Phase Overcurrent Protection
If the overcurrent protection function is being used, both Ι>1 and I>2 elements should be
tested.
To avoid spurious operation of any current differential, earth fault, breaker fail or CT
supervision elements, these should be disabled for the duration of the overcurrent tests. This
is done in the relay’s CONFIGURATION column. Make a note of which elements need to be
re-enabled after testing.
CM
P746/EN CM/J43
Commissioning
(CM) 10-30
6.2.3.1
MiCOM P40 Agile P746
Connect the Test Circuit
Determine which output relay has been selected to operate when an Ι>1 trip and an I>2
occur by viewing the relay’s programmable scheme logic.
The programmable scheme logic can only be changed using the appropriate software. If this
software is not available then the default output relay allocations will still be applicable.
If the trip outputs are phase-segregated (i.e. a different output relay allocated for each
phase), the relay assigned for tripping on ‘A’ phase faults should be used.
The associated terminal numbers can be found using the external connection diagrams.
Connect the output relay so that its operation will trip the test set and stop the timer.
Connect the current output of the test set to the ‘A’ phase current transformer input of the
relay.
Ensure that the timer will start when the current is applied to the relay.
6.2.3.1.1
Performing the Test
1. Ensure that the timer is reset.
2. Apply a current of twice the setting in cell [GROUP 1 OVERCURRENT, Ι>1 Current
Set] to the relay
3. Note the time displayed when the timer stops.
4. Check that the red trip LED has illuminated.
6.2.3.1.2
Check the Operating Time
Check that the operating time recorded by the timer is within the range shown in Table 6.
Note:
With the exception of the definite time characteristic, the operating times
given are for a Time Multiplier Setting (TMS) or Time Dial Setting (TDS) of 1.
For other values of TMS or TDS, the values need to be modified accordingly.
Note:
For definite time and inverse characteristics there is an additional delay of up
to 0.02 second and 0.08 second respectively.
For all characteristics, allowance must be made for the accuracy of the test equipment being
used.
CM
Characteristic
Operating time at twice current setting and time multiplier/time dial
setting of 1.0
Nominal (seconds)
DT
IEC S Inverse
IEC V Inverse
IEC E Inverse
UK LT Inverse
IEEE M Inverse
IEEE V Inverse
IEEE E Inverse
US Inverse
US ST Inverse
[: I>1 Time Delay] setting
10.03
13.50
26.67
120.00
0.64
1.42
1.46
0.46
0.26
Table 6: Characteristic operating times for Ι>1
Re-perform the tests for the function I>2.
Range (seconds)
Setting ±2%
9.53 – 10.53
12.83 – 14.18
24.67 – 28.67
114.00 – 126.00
0.61 – 0.67
1.35 – 1.50
1.39 – 1.54
0.44 – 0.49
0.25 – 0.28
Commissioning
P746/EN CM/J43
MiCOM P40 Agile P746
(CM) 10-31
On completion of the tests, you must restore all settings to customer
specifications.
6.2.4
6.2.4.1
Breaker Failure Protection
Separate External 50BF Protection to the Busbar Protection
Feeder 1
Feeder 2
Coupler
Feeder 3
Feeder 4
CB Fail
External Fault
P3751ENd
The above figure shows a CB fail in feeder 1 being stimulated. After energising the opto
input “External CB Fail” of the feeder1 we check that the P746 issues a tripping order to
feeder 2 and the coupler.
The trip of the backup phase overcurrent or earth fault overcurrent protection initiates the
timers tBF3 and tBF4.
6.2.4.2
External Initiation of BF Protection
CM
To test the retrip:
As shown in the above figure, we initiate the opto inputs “External Trip A,B,C” and apply a
current twice the I< threshold.
Check that the P746 issues a retrip order after the settable time tBF3.
Important: The time indicated on the LCD is the duration of the operation of this trip
command.
The fast reset retrip order is equal to the fault clearance time + 13ms – tBF3 pick-up time.
P746/EN CM/J43
Commissioning
(CM) 10-32
MiCOM P40 Agile P746
For example, if tBF3 = 50ms and the fault is cleared after 60ms, the P746 displayed value
will be 23ms.
To test the backtrip:
Do the same tests as for retrip however apply a faulty current for more than tBF4 and check
that the backtrip signal is sent.
Check that feeder 1 and feeder 2 connected to the bus-section 1 are tripped.
6.2.4.3
CB Unavailable:
Feeder 1
Feeder 2
Coupler
Feeder 3
Feeder 4
Zone 1
Zone 2
P3753ENd
Apply an internal fault in zone 2 and energise the opto input “CB unavailable” of the coupler
and check that both bus-sections are tripped simultaneously.
Note:
If the input “CB unavailable” is energised, the CB will be not tripped and is
normally used only for bus-coupler.
The backtrip order is equal to (the maximum between the fault clearance time and 250 ms) –
tBF4 pick-up time.
For example, if tBF4 = 200ms and the fault is cleared before 450ms, the P746 will display
450ms.
For example, if tBF4 = 200ms and the fault is cleared in 500ms, the P746 will display 500ms.
CM
6.2.4.4
Internal Initiation Breaker Failure Protection
This breaker failure protection can only be initiated by a trip command issued by the P746.
Feeder 1
Feeder 2
Coupler
Feeder 3
Feeder 4
Zone 1
Zone 2
P3753ENd
Simulate a busbar fault on the bus-section 2.
Continue to apply fault current in the bus-coupler until the timer tBF1 elapsed.
Check that the retrip signal is given by CT3 and backtrip signal is sent after tBF2.
Commissioning
MiCOM P40 Agile P746
P746/EN CM/J43
(CM) 10-33
Check that the P746 issued a trip command to both bus-sections (feeder 1, feeder 2 feeder 4
and feeder 5 should have operated).
The backtrip order is equal to (the maximum between the fault clearance time and 250 ms) –
tBF2 pick-up time.
For example, if tBF2 = 150ms and the fault is cleared before 400ms, the displayed value will
be 400ms.
For example, if tBF2 = 150ms and the fault is cleared in 500ms, the displayed value will be
500ms.
6.3
Check Application Settings
The settings applied should be carefully checked against the required application-specific
settings to ensure that they are correct and have not been altered during the injection test.
There are two methods of checking the settings:
• Extract the settings from the relay using a portable PC running the appropriate
software via the front EIA(RS)232 port, located under the bottom access cover.
Compare the settings transferred from the relay with the original written applicationspecific setting record. (For cases where the customer has only provided a printed
copy of the required settings but a portable PC is available).
• Step through the settings using the relay’s operator interface and compare them with
the original application-specific setting record.
Unless previously agreed to the contrary, the application-specific programmable scheme
logic will not be checked as part of the commissioning tests.
Due to the versatility and possible complexity of the programmable scheme logic, it is
beyond the scope of these commissioning instructions to detail suitable test procedures.
Therefore, when programmable scheme logic tests must be performed, written tests which
will satisfactorily demonstrate the correct operation of the application-specific scheme logic
should be devised by the Engineer who created it. These should be provided to the
Commissioning Engineer together with the digital medium containing the programmable
scheme logic setting file.
CM
P746/EN CM/J43
Commissioning
(CM) 10-34
MiCOM P40 Agile P746
7
IEC 61850 EDITION 2 TESTING
7.1
Using IEC 61850 Edition 2 Test Modes
In a conventional substation, functionality typically resides in a single device. It is usually
easy to physically isolate these functions, as the hardwired connects can simply be removed.
Within a digital substation architecture however, functions may be distributed across many
devices. This makes isolation of these functions difficult because there are no physical wires
that can be disconnected on a Ethernet network. Logical isolation of the various functions is
therefore necessary.
With devices that support IEC 61850 Edition 2, it is possible to use a test mode to conduct
online testing, which helps with the situation. The advantages of this are as follows:
• The device can be placed into a test mode, which can disable the relay outputs when
testing the device with test input signals.
• Specific protection and control functions can be logically isolated.
• GOOSE messages can be tagged so that receiving devices can recognise they are test
signals.
• An IED receiving simulated GOOSE or Sampled Value messages from test devices can
differentiate these from normal process messages, and be configured to respond
appropriately.
7.1.1
IED Test Mode Behaviour
Test modes define how the device responds to test messages, and whether the relay
outputs are activated or not.
You can select the mode of operation by:
• Using the front panel HMI, with the setting IED Test Mode under the COMMISSION
TESTS column.
• Using an IEC 61850 control service to System/LLN0.Mod
• Using an opto-input via PSL with the signal Block Contacts
The following table summarises the IED behaviour under the different modes:
IED Test Mode Setting
Disabled
CM
Test
Result
Normal IED behaviour
Protection remains enabled
Output from the device is still active
IEC 61850 message output has the 'quality' parameter set to 'test'
The device only responds to IEC61850 MMS messages from the
client with the'test' flag set
Protection remains enabled
Output from the device is disabled
Contacts Blocked
IEC 61850 message output has quality set to ‘test’
The device only responds to IEC 61850 MMS messages from the
client with the 'test' flag set
Setting the Test or Contacts Blocked mode puts the whole IED into test mode. The IEC
61850 data object Beh in all Logical Nodes (except LPHD and any protection Logical Nodes
that have Beh = 5 (off) due to the function being disabled) will be set to 3 (test) or 4
(test/blocked) as applicable.
7.1.2
Sampled Value Test Mode Behaviour
The SV Test Mode defines how the device responds to test sampled value messages. You
can select the mode of operation by using the front panel HMI, with the setting SV Test
Mode under the IEC 61850-9.2LE column.
Commissioning
P746/EN CM/J43
MiCOM P40 Agile P746
(CM) 10-35
The following table summarises the behaviour for sampled values under the different modes:
SV Test Mode Setting
Disabled
Result
Normal IED behaviour
All sampled value data frames received with an IEC 61850 Test
quality bit set are treated as invalid
The IED will display the measurement values for sampled values
with the Simulated flag set but the protection elements within the IED
will be blocked
Enabled
7.2
All sampled value data frames received are treated as good, no
matter if they have an IEC 61850-9-2 Simulated flag set or not
Simulated Input Behaviour
Simulated GOOSE messages and sampled value streams can be used during testing.
The Subscriber Sim setting in the COMMISSION TESTS column controls whether a device
listens to simulated signals or to real ones. An IEC 61850 control service to
System/LPHD.Sim can also be used to change this value.
The device may be presented with both real signals and test signals. An internal state
machine is used to control how the device switches between signals:
• The IED will continue subscribing to the ‘real’ GOOSE1 (in green) until it receives the first
simulated GOOSE 1 (in red). This will initiate subscription changeover.
• After changeover to this new state, the IED will continue to subscribe to the simulated
GOOSE 1 message (in red). Even if this simulated GOOSE 1 message disappears, the
real GOOSE 1 message (in green) will still not be processed. This means all Virtual
Inputs derived from the GOOSE 1 message will go to their default state.
• The only way to bring the IED out of this state is to set the Subscriber Sim setting back
to False. The IED will then immediately stop processing the simulated messages and
start processing real messages again.
• During above steps, IED1 will continuously process the real GOOSE 2 and GOOSE 3
messages as normal because it has not received any simulated messages for these that
would initiate a changeover.
The process is represented in the following figure:
CM
P746/EN CM/J43
Commissioning
(CM) 10-36
MiCOM P40 Agile P746
LPHD1
Sim stVal=true
Beh stVal=on
Simulated GOOSE 1 messages
Simulation bit goes TRUE
Real GOOSE 1 messages
Simulation bit was FALSE
Incoming data
processed
Real GOOSE 2 messages
Real GOOSE 3 messages
Reception buffer
V01058
Figure 7: Simulated input behaviour
7.3
Testing Examples
These examples show how you test the IED with and without simulated values. Depending
on the IED Test Mode, it may respond by operating plant (for example by tripping the circuit
breaker) or it may not operate plant.
7.3.1
Test Procedure for Real Values
This procedure is for testing with real values without operating plant.
CM
1.
Set device into 'Contacts Blocked' Mode
Select COMMISSION TESTS → IED Test Mode → Contacts Blocked
2. Confirm new behaviour has been enabled
View COMMISSION TESTS → IED Mod/Beh, and check that it shows Test-blocked
3. Set device into Simulation Listening Mode
Select COMMISSION TESTS → Subscriber Sim = Disabled
4. If using sampled values set the sampled values test mode
Select IEC 61850-9.2LE → SV Test Mode → Disabled
5. Inject real signals using a test device connected to the merging units. The device will
continue to listen to ‘real’ GOOSE messages and ignore simulated messages received.
6. Verify function based on test signal outputs
Binary outputs (e.g. CB trips) will not operate. All transmitted GOOSE and MMS data items
will be tagged with the 'quality' parameter set to 'test', so that the receiver understands that
they have been issued by a device under test and can respond accordingly. This is
summarised in the following diagram:
Commissioning
P746/EN CM/J43
MiCOM P40 Agile P746
(CM) 10-37
Hardwired
CB control
Fully digital bay
Station/Process Bus
q = test
No output
Yard
Yard
SC MU1
Switchgear
MU1
MU1
Test
Device
Test
Device
V01062
Figure 8: Test example 1
7.3.2
Test Procedure for Simulated values - No Plant
This procedure is for testing with simulated values without operating plant.
1.
Set device into 'Contacts Blocked' Mode
Select COMMISSION TESTS → IED Test Mode → Contacts Blocked
2. Confirm new behaviour has been enabled
View COMMISSION TESTS → IED Mod/Beh, and check that it shows test-blocked
3. Set device into Simulation Listening Mode
Select COMMISSION TESTS → Subscriber Sim = Enabled
4. If using sampled values set the sampled values test mode
Select IEC 61850-9.2LE → SV Test Mode → Enabled
5. Inject simulated signals using a test device connected to the Ethernet network. The
device will continue to listen to ‘real’ GOOSE messages until a simulated message is
received. Once the simulated messages are received, the corresponding ‘real’
messages are ignored until the device is taken out of test mode. Each message is
treated separately, but sampled values are considered as a single message.
6. Verify function based on test signal outputs
Binary outputs (e.g. CB trips) will not operate. All transmitted GOOSE and MMS data items
will be tagged with the 'quality' parameter set to 'test', so that the receiver understands that
they have been issued by a device under test and can respond accordingly. This is
summarised in the following diagram:
CM
P746/EN CM/J43
Commissioning
(CM) 10-38
MiCOM P40 Agile P746
Hardwired
CB control
Fully digital bay
Station/Process Bus
Simulated
values
q = test
No output
Yard
Test
Device
Yard
SC MU1
Switchgear
MU1
MU1
V01063
Figure 9: Test example 2
7.3.3
Test Procedure for Simulated Values - with Plant
This procedure is for testing with simulated values with operating plant.
1.
2.
3.
4.
5.
CM
6.
Set device into 'Contacts Blocked' Mode
Select COMMISSION TESTS → IED Test Mode → Test
Confirm new behaviour has been enabled
View COMMISSION TESTS → IED Mod/Beh, and check that it shows Test
Set device into Simulation Listening Mode
Select COMMISSION TESTS → Subscriber Sim = Enabled
If using sampled values set the sampled values test mode
Select IEC 61850-9.2LE → SV Test Mode → Enabled
Inject simulated signals using a test device connected to the Ethernet network.
The device will continue to listen to ‘real’ GOOSE messages until a simulated message
is received. Once the simulated messages are received, the corresponding ‘real’
messages are ignored until the device is taken out of IED test mode. Each message is
treated separately, but sampled values are considered as a single message.
Verify function based on test signal outputs.
Binary outputs (e.g. CB trips) will operate as normal. All transmitted GOOSE and MMS
data items will be tagged with the 'quality' parameter set to 'test', so that the receiver
understands that they have been issued by a device under test and can respond
accordingly. This is summarised in the following diagram:
Commissioning
P746/EN CM/J43
MiCOM P40 Agile P746
(CM) 10-39
Hardwired
CB control
Fully digital bay
Station/Process Bus
Simulated
values
q = test
Trip output
Yard
Test
Device
Yard
SC MU1
MU1
Switchgear
MU1
V01064
Figure 10: Test example 3
7.3.4
Contact Test
The Apply Test command in this cell is used to change the state of the contacts set for
operation.
If the device has been put into 'Contact Blocked' mode using an input signal (via the Block
Contacts DDB signal) then the Apply Test command will not execute. This is to prevent a
device that has been blocked by an external process having its contacts operated by a local
operator using the HMI.
If the Block Contacts DDB is not set and the Apply Test command in this cell is issued,
contacts change state and the command text on the LCD changes to No Operation. The
contacts remain in the Test state until reset by issuing the Remove Test command. The
command text on the LCD shows No Operation after the Remove Test command has been
issued.
Note:
When the relay Test Mode cell is set to Contacts Blocked, the Relay O/P
Status cell does not show the current status of the output relays so cannot
be used to confirm operation of the output relays. Therefore it is necessary
to monitor the state of each contact in turn.
CM
P746/EN CM/J43
Commissioning
(CM) 10-40
8
MiCOM P40 Agile P746
ON-LOAD CHECKS
Warning: Onload checks are potentially very dangerous and may only be carried out
by qualified and authorised personnel.
The objectives of the on-load checks are to:
• Confirm the external wiring to the current inputs is correct.
• Ensure the on-load differential current is well below the relay setting.
Onload checks can only be carried out if there are no restrictions preventing the energisation
of the plant, and the other devices in the group have already been commissioned.
Remove all test leads and temporary shorting leads, then replace any external wiring that
has been removed to allow testing.
Warning: If any external wiring has been disconnected for the commissioning
process, replace it in accordance with the relevant external connection or
scheme diagram.
8.1
Confirm Current Transformer Wiring
1. Using a multimeter, measure the voltage transformer secondary voltages to ensure
they are correctly rated.
2. Check that the current transformer polarities are correct.
3. Ensure the current flowing in the neutral circuit of the current transformers is
negligible.
4. Compare the values of the secondary phase currents with the relay’s measured
values, which can be found in the MEASUREMENTS 1 menu column.
Note:
CM
Under normal load conditions the earth fault function will measure little, if
any, current. It is therefore necessary to simulate a phase to neutral fault.
This can be achieved by temporarily disconnecting one or two of the line
current transformer connections to the relay and shorting the terminals of
these current transformer secondary windings.
If cell [MEASURE’T SETUP, Local Values] is set to Secondary, the currents displayed
should be equal to the applied secondary current. The values should be within 5% of the
applied secondary currents. However, an additional allowance must be made for the
accuracy of the test equipment being used.
If cell [MEASURE’T SETUP, Local Values] is set to Primary, the currents displayed should
be equal to the applied secondary current multiplied by the corresponding current
transformer ratio set in the CT & VT RATIOS column (see Table 5). The values should be
within 5% of the expected value, plus an additional allowance for the accuracy of the test
equipment being used.
Note:
If a single dedicated current transformer is used for the earth fault function, it
is not possible to check the relay’s measured values.
Commissioning
P746/EN CM/J43
MiCOM P40 Agile P746
9
(CM) 10-41
FINAL CHECKS
1. Remove all test leads and temporary shorting leads.
2. If you have had to disconnect any of the external wiring in order to perform the wiring
verification tests, replace all wiring, fuses and links in accordance with the relevant
external connection or scheme diagram.
3. The settings applied should be carefully checked against the required applicationspecific settings to ensure that they are correct, and have not been mistakenly altered
during testing.
4. Ensure that all protection elements required have been set to Enabled in the
CONFIGURATION column.
5. Ensure that the relay has been restored to service by checking that the Test Mode
cell in the COMMISSION TESTS column is set to Disabled.
6. If the relay is in a new installation or the circuit breaker has just been maintained, the
circuit breaker maintenance and current counters should be zero. These counters can
be reset using the Reset All Values cell. If the required access level is not active, the
device will prompt for a password to be entered so that the setting change can be
made.
7. If the menu language has been changed to allow accurate testing it should be restored
to the customer’s preferred language.
8. If a P991/MMLG test block is installed, remove the P992/MMLB test plug and replace
the cover so that the protection is put into service.
9. Ensure that all event records, fault records, disturbance records, alarms and LEDs
and communications statistics have been reset.
Note:
Remember to restore the language setting to the customer’s preferred
language on completion.
CM
P746/EN CM/J43
(CM) 10-42
CM
Commissioning
MiCOM P40 Agile P746
Maintenance
P746/EN MT/J43
MiCOM P40 Agile P746
(MT) 11-1
MAINTENANCE
Hardware Suffix:
Software Version:
M
91
MT
P746/EN MT/J43
(MT) 11-2
MT
Maintenance
MiCOM P40 Agile P746
Maintenance
MiCOM P40 Agile P746
P746/EN MT/J43
(MT) 11-3
CONTENTS
1
OVERVIEW
5
2
MAINTENANCE
6
2.1
Maintenance Checks
6
2.1.1
Alarms
6
2.1.2
Opto-isolators
6
2.1.3
Output Relays
6
2.1.4
Measurement Accuracy
6
2.2
Replacing the Device
7
2.3
Repairing the Device
8
2.4
Removing the Front Panel
8
2.5
Replacing PCBs
9
2.5.1
Replacing the Main Processor Board
10
2.5.2
Replacement of Communications Boards
10
2.5.3
Replacement of the Input Module
11
2.5.4
Replacement of the Power Supply Board
12
2.5.5
Replacement of the I/O Boards
12
2.6
Recalibration
12
2.7
Supercapacitor Discharged
13
2.8
Cleaning
13
FIGURES
Figure 1: Possible terminal block types
Figure 2: Front panel assembly
8
10
MT
P746/EN MT/J43
(MT) 11-4
MT
Maintenance
MiCOM P40 Agile P746
Maintenance
P746/EN MT/J43
MiCOM P40 Agile P746
1
(MT) 11-5
OVERVIEW
The Maintenance chapter provides details of how to maintain products based on the Px4x
and P40Agile platforms. Always follow the warning signs in this chapter. Failure to do so may
result injury or defective equipment.
Before carrying out any work on the equipment, the user should be familiar
with the contents of the safety section/safety guide SFTY/4LM and the
ratings on the equipment rating label.
MT
P746/EN MT/J43
Maintenance
(MT) 11-6
MiCOM P40 Agile P746
2
MAINTENANCE
2.1
Maintenance Checks
In view of the critical nature of the application, GE products should be checked at regular
intervals to confirm they are operating correctly. General Electric products are designed for a
life in excess of 20 years.
The devices are self-supervising and so require less maintenance than earlier designs of
protection devices. Most problems will result in an alarm so that remedial action can be
taken. However, some periodic tests should be done to ensure that the relay is functioning
correctly and the external wiring is intact. It is the responsibility of the customer to define the
interval between maintenance periods. If your organisation has a Preventative Maintenance
Policy, the recommended product checks should be included in the regular program.
Maintenance periods depend on many factors, such as:
• The operating environment
• The accessibility of the site
• The amount of available manpower
• The importance of the installation in the power system
• The consequences of failure
Although some functionality checks can be performed from a remote location, these are
predominantly restricted to checking that the unit is measuring the applied currents and
voltages accurately, and checking the circuit breaker maintenance counters. For this reason,
maintenance checks should also be performed locally at the substation.
Before carrying out any work on the equipment, the user should be familiar
with the contents of the safety section/safety guide SFTY/4LM and the
ratings on the equipment rating label.
2.1.1
Alarms
First check the alarm status LED to see if any alarm conditions exist. If so, press the Read
key repeatedly to step through the alarms.
After dealing with any problems, clear the alarms. This will clear the relevant LEDs.
MT
2.1.2
Opto-isolators
Check the opto-inputs by repeating the commissioning test detailed in the Commissioning
chapter.
2.1.3
Output Relays
Check the output relays by repeating the commissioning test detailed in the Commissioning
chapter.
2.1.4
Measurement Accuracy
If the power system is energised, compare the values measured by the relay with known
system values to check that they are in the approximate expected range. If they are, the
relay is performing the analogue/digital conversion and calculations are being performed
correctly.
Alternatively, check the values measured by the relay against known values injected into the
relay using the test block, if fitted, or injected directly into the relay terminals. These tests will
prove the calibration accuracy is being maintained.
Maintenance
P746/EN MT/J43
MiCOM P40 Agile P746
2.2
(MT) 11-7
Replacing the Device
If your product should develop a fault while in service, depending on the nature of the fault,
the watchdog contacts will change state and an alarm condition will be flagged. In the case
of a fault, you can replace either the complete device or just the faulty PCB, identified by the
in-built diagnostic software.
If possible you should replace the complete device, as this reduces the chance of damage
due to electrostatic discharge and also eliminates the risk of fitting an incompatible
replacement PCB. However, we understand it may be difficult to remove an installed product
and you may be forced to replace the faulty PCB on-site. The case and rear terminal blocks
are designed to allow removal of the complete device, without disconnecting the scheme
wiring.
Replacing PCBs requires the correct on-site environment (clean and dry) as
well as suitably trained personnel.
If the repair is not performed by an approved service centre, the warranty
will be invalidated.
Before carrying out any work on the equipment, the user should be familiar
with the contents of the safety section/safety guide SFTY/4LM and the
ratings on the equipment rating label
Before working at the rear of the relay, isolate all voltage and current
supplies to the relay.
Note:
The current transformer inputs are equipped with integral shorting switches
which will close for safety reasons, when the terminal block is removed.
To replace the complete device:
1. Carefully disconnect the cables not connected to the terminal blocks (e.g. IRIG-B, fibre
optic cables, earth), as appropriate, from the rear of the device.
2. Remove the terminal block screws using a magnetic screwdriver to minimise the risk
of losing the screws or leaving them in the terminal block.
3. Without exerting excessive force or damaging the scheme wiring, pull the terminal
blocks away from their internal connectors.
4. Remove the terminal block screws that fasten the device to the panel and rack. These
are the screws with the larger diameter heads that are accessible when the access
covers are fitted and open.
5. Withdraw the device from the panel and rack. Take care, as the device will be heavy
due to the internal transformers.
6. To reinstall the device, follow the above instructions in reverse, ensuring that each
terminal block is relocated in the correct position and the chassis ground, IRIG-B and
fibre optic connections are replaced.
The terminal blocks are labelled alphabetically with ‘A’ on the left hand side when
viewed from the rear.
Once the device has been reinstalled, it should be re-commissioned as set out in the
Commissioning chapter.
MT
P746/EN MT/J43
Maintenance
(MT) 11-8
MiCOM P40 Agile P746
If the top and bottom access covers have been removed, do not remove the
screws with the smaller diameter heads. These screws hold the front panel
on the relay.
Note:
There are four possible types of terminal block: RTD/CLIO input, heavy duty,
medium duty, and MiDOS. The terminal blocks are fastened to the rear
panel with slotted or cross-head screws depending on the type of terminal
block. Not all terminal block types are present on all products.
Figure 1: Possible terminal block types
MT
2.3
Repairing the Device
If your product should develop a fault while in service, depending on the nature of the fault,
the watchdog contacts will change state and an alarm condition will be flagged. In the case
of a fault, either the complete unit or just the faulty PCB, identified by the in-built diagnostic
software, should be replaced.
Replacement of printed circuit boards and other internal components must be undertaken by
approved Service Centres. Failure to obtain the authorization of after-sales engineers prior to
commencing work may invalidate the product warranty.
We recommend that you entrust any repairs to Automation Support teams, which are
available world-wide.
2.4
Removing the Front Panel
Before removing the front panel to replace a PCB, you must first remove the
auxiliary power supply and wait 5 seconds for the internal capacitors to
discharge. You should also isolate voltage and current transformer
connections and trip circuit.
Maintenance
P746/EN MT/J43
MiCOM P40 Agile P746
(MT) 11-9
Before carrying out any work on the equipment, the user should be familiar
with the contents of the safety section/safety guide SFTY/4LM and the
ratings on the equipment rating label
To Remove the Front Panel:
1. Open the top and bottom access covers. You must open the hinged access covers by
more than 90° before they can be removed.
2. If fitted, remove the transparent secondary front cover.
3. Apply outward pressure to the middle of the access covers to bow them and
disengage the hinge lug, so the access cover can be removed. The screws that fasten
the front panel to the case are now accessible.
4. Undo and remove the screws. The 40TE case has four cross-head screws fastening
the front panel to the case, one in each corner, in recessed holes. The 60TE/80TE
cases have an additional two screws, one midway along each of the top and bottom
edges of the front plate.
5. When the screws have been removed, pull the complete front panel forward to
separate it from the metal case. The front panel is connected to the rest of the circuitry
by a 64-way ribbon cable.
6. The ribbon cable is fastened to the front panel using an IDC connector; a socket on
the cable and a plug with locking latches on the front panel. Gently push the two
locking latches outwards which eject the connector socket slightly. Remove the socket
from the plug to disconnect the front panel.
Do not remove the screws with the larger diameter heads which are
accessible when the access covers are fitted and open. These screws hold
the relay in its mounting (panel or cubicle).
The internal circuitry is now exposed and is not protected against
electrostatic discharge and dust ingress. Therefore ESD precautions and
clean working conditions must be maintained at all times.
2.5
Replacing PCBs
1. To replace any of the PCBs, first remove the front panel.
2. Once the front panel has been removed, the PCBs are accessible. The numbers
above the case outline identify the guide slot reference for each printed circuit board.
Each printed circuit board has a label stating the corresponding guide slot number to
ensure correct relocation after removal. To serve as a reminder of the slot numbering
there is a label on the rear of the front panel metallic screen.
3. Remove the 64-way ribbon cable from the PCB that needs replacing
4. Remove the PCB in accordance with the board-specific instructions detailed later in
this section.
Note:
To ensure compatibility, always replace a faulty PCB with one of an identical
part number.
MT
P746/EN MT/J43
Maintenance
(MT) 11-10
2.5.1
MiCOM P40 Agile P746
Replacing the Main Processor Board
The main processor board is situated in the front panel. This board contains applicationspecific settings in its nonvolatile memory. You may wish to take a backup copy of these
settings. This could save time in the recommissioning process.
To replace the main processor board:
1. Remove front panel.
2. Place the front panel with the user interface face down and remove the six screws
from the metallic screen, as shown in the figure below. Remove the metal plate.
3. Remove the screws that hold the main processor board in position.
4. Carefully disconnect the ribbon cable. Take care as this could easily be damaged by
excessive twisting.
5. Replace the main processor board
6. Reassemble the front panel using the reverse procedure. Make sure the ribbon cable
is reconnected to the main processor board and that all eight screws are refitted.
7. Refit the front panel.
8. Refit and close the access covers then press the hinge assistance T-pieces so they
click back into the front panel moulding.
9. Once the unit has been reassembled, carry out the standard commissioning
procedure as defined in the Commissioning chapter.
Note:
After replacing the main processor board, all the settings required for the
application need to be re-entered. This may be done either manually or by
downloading a settings file.
MT
P3007ENa
Figure 2: Front panel assembly
2.5.2
Replacement of Communications Boards
Most products will have at least one communications board of some sort fitted. There are
several different boards available offering various functionality, depending on the application.
Some products may even be fitted with two boards of different types.
To replace a faulty communications board:
1. Remove front panel.
Maintenance
P746/EN MT/J43
MiCOM P40 Agile P746
(MT) 11-11
2. Disconnect all connections at the rear.
3. The board is secured in the relay case by two screws, one at the top and another at
the bottom. Remove these screws carefully as they are not captive in the rear panel.
4. Gently pull the communications board forward and out of the case.
5. Before fitting the replacement PCB check that the number on the round label next to
the front edge of the PCB matches the slot number into which it will be fitted. If the slot
number is missing or incorrect, write the correct slot number on the label.
6. Fit the replacement PCB carefully into the correct slot. Make sure it is pushed fully
back and that the securing screws are refitted.
7. Reconnect all connections at the rear.
8. Refit the front panel.
9. Refit and close the access covers then press the hinge assistance T-pieces so they
click back into the front panel moulding.
10.Once the unit has been reassembled, commission it according to the Commissioning
chapter.
2.5.3
Replacement of the Input Module
Depending on the product, the input module consists of two or three boards fastened
together and is contained within a metal housing. One board contains the transformers and
one contains the analogue to digital conversion and processing electronics. Some devices
have an additional auxiliary transformer contained on a third board.
To replace an input module:
1. Remove front panel.
2. The module is secured in the case by two screws on its right-hand side, accessible
from the front, as shown below. Move these screws carefully as they are not captive in
the front plate of the module.
3. On the right-hand side of the module there is a small metal tab which brings out a
handle (on some modules there is also a tab on the left). Grasp the handle(s) and pull
the module firmly forward, away from the rear terminal blocks. A reasonable amount of
force is needed due to the friction between the contacts of the terminal blocks.
4. Remove the module from the case. The module may be heavy, because it contains
the input voltage and current transformers.
5. Slot in the replacement module and push it fully back onto the rear terminal blocks. To
check that the module is fully inserted, make sure the v-shaped cut-out in the bottom
plate of the case is fully visible.
6. Refit the securing screws.
7. Refit the front panel.
8. Refit and close the access covers then press the hinge assistance T-pieces so they
click back into the front panel moulding.
9. Once the unit has been reassembled, commission it according to the Commissioning
chapter.
With non-mounted relays, the case needs to be held firmly while the module
is withdrawn. Withdraw the input module with care as it suddenly comes
loose once the friction of the terminal blocks is overcome.
Note:
If individual boards within the input module are replaced, recalibration will be
necessary. We therefore recommend replacement of the complete module
to avoid on-site recalibration.
MT
P746/EN MT/J43
Maintenance
(MT) 11-12
2.5.4
MiCOM P40 Agile P746
Replacement of the Power Supply Board
Before carrying out any work on the equipment, the user should be familiar
with the contents of the safety section/safety guide SFTY/4LM and the
ratings on the equipment rating label
The power supply board is fastened to an output relay board with push fit nylon pillars. This
doubled-up board is secured on the extreme left hand side, looking from the front of the unit.
1. Remove front panel.
2. Pull the power supply module forward, away from the rear terminal blocks and out of
the case. A reasonable amount of force is needed due to the friction between the
contacts of the terminal blocks.
3. Separate the boards by pulling them apart carefully. The power supply board is the
one with two large electrolytic capacitors.
4. Before reassembling the module, check that the number on the round label next to the
front edge of the PCB matches the slot number into which it will be fitted. If the slot
number is missing or incorrect, write the correct slot number on the label
5. Reassemble the module with a replacement PCB. Push the inter-board connectors
firmly together. Fit the four push fit nylon pillars securely in their respective holes in
each PCB.
6. Slot the power supply module back into the housing. Push it fully back onto the rear
terminal blocks.
7. Refit the front panel.
8. Refit and close the access covers then press the hinge assistance T-pieces so they
click back into the front panel moulding.
9. Once the unit has been reassembled, commission it according to the Commissioning
chapter.
2.5.5
Replacement of the I/O Boards
There are several different types of I/O boards, which can be used, depending on the
product and application.
Some boards have opto-inputs, some have relay outputs and others have a mixture of both.
1. Remove front panel.
MT
2. Gently pull the board forward and out of the case
3. If replacing the I/O board, make sure the setting of the link above IDC connector on
the replacement board is the same as the one being replaced.
4. Before fitting the replacement board check the number on the round label next to the
front edge of the board matches the slot number into which it will be fitted. If the slot
number is missing or incorrect, write the correct slot number on the label.
5. Carefully slide the replacement board into the appropriate slot, ensuring that it is
pushed fully back onto the rear terminal blocks.
6. Refit the front panel.
7. Refit and close the access covers then press at the hinge assistance T-pieces so they
click back into the front panel moulding.
8. Once the unit has been reassembled, commission it according to the Commissioning
chapter.
2.6
Recalibration
Recalibration is not required when a PCB is replaced unless it happens to be one of the
boards in the input module, the replacement of either directly affects the calibration.
Maintenance
P746/EN MT/J43
MiCOM P40 Agile P746
(MT) 11-13
Although it is possible to carry out recalibration on site, this requires test equipment with
suitable accuracy and a special calibration program to run on a PC. It is therefore
recommended that the work is carried out by the manufacturer or entrusted to an approved
service centre.
2.7
Supercapacitor Discharged
The supercapacitor maintains charge for two weeks with the relay de-energised. When first
energising the relay after this time there may be a Battery Alarm due to the supercapacitor
voltage dropping below a pre-defined threshold. The battery alarm will clear after
approximately 30 minutes of the relay being energised, and once cleared there will be
enough charge in the supercapacitor to backup status data.
Note:
2.8
Events, disturbance and maintenance records will be lost if the
supercapacitor is fully discharged.
Cleaning
Before cleaning the equipment ensure that all ac and dc supplies, current
transformer and voltage transformer connections are isolated to prevent
any chance of an electric shock while cleaning.
The equipment may be cleaned using a lint-free cloth dampened with clean water. The use
of detergents, solvents or abrasive cleaners is not recommended as they may damage the
relay’s surface and leave a conductive residue.
MT
P746/EN MT/J43
(MT) 11-14
MT
Maintenance
MiCOM P40 Agile P746
Troubleshooting
P746/EN TS/J43
MiCOM P40 Agile P746
(TS) 12-1
TROUBLESHOOTING
Hardware Suffix:
Software Version:
M
91
TS
P746/EN TS/J43
(TS) 12-2
TS
Troubleshooting
MiCOM P40 Agile P746
Troubleshooting
MiCOM P40 Agile P746
P746/EN TS/J43
(TS) 12-3
CONTENTS
1
INTRODUCTION
5
2
TROUBLESHOOTING
6
2.1
Self-diagnostic Software
6
2.2
Power-up Errors
6
2.3
Error Message or Code On Power-up
6
2.4
Out of Service LED ON at Power-up
8
2.5
Error Code During Operation
8
2.6
Mal-operation During Testing
8
2.6.1
Failure of Output Contacts
8
2.6.2
Failure of Opto-inputs
9
2.6.3
Incorrect Analog Signals
9
2.7
PSL Editor Troubleshooting
9
2.7.1
Diagram Reconstruction
10
2.7.2
PSL Version Check
10
2.8
Repair and Modification Procedure
10
TS
P746/EN TS/J43
(TS) 12-4
TS
Troubleshooting
MiCOM P40 Agile P746
Troubleshooting
P746/EN TS/J43
MiCOM P40 Agile P746
1
(TS) 12-5
INTRODUCTION
The Troubleshooting chapter provides details of how to troubleshoot products based on the
Px4x and P40Agile platforms. Always follow the warning signs in this chapter. Failure to do
so may result injury or defective equipment.
Before carrying out any work on the equipment, the user should be familiar
with the contents of the safety section/safety guide SFTY/4LM or later issue,
the technical data section and the ratings on the equipment rating label
This chapter allows an error condition on the relay to be identified so that appropriate
corrective action can be taken.
If the device develops a fault, it is usually possible to identify which module needs replacing.
It is not possible to perform an on-site repair to a faulty module.
If you return a faulty unit or module to the manufacturer or one of their approved service
centres, you should include a completed copy of the Repair or Modification Return
Authorization (RMA) form
TS
P746/EN TS/J43
Troubleshooting
(TS) 12-6
MiCOM P40 Agile P746
2
TROUBLESHOOTING
2.1
Self-diagnostic Software
The device includes several self-monitoring functions to check the operation of its hardware
and software while in service. If there is a problem with the hardware or software, it should
be able to detect and report the problem, and attempt to resolve the problem by performing a
reboot. In this case, the device would be out of service for a short time, during which the
‘Healthy’ LED on the front of the device is switched OFF and the watchdog contact at the
rear is ON. If the restart fails to resolve the problem, the unit takes itself permanently out of
service; the ‘Healthy’
LED stays OFF and watchdog contact stays ON.
If a problem is detected by the self-monitoring functions, the device attempts to store a
maintenance record to allow the nature of the problem to be communicated to the user.
The self-monitoring is implemented in two stages: firstly a thorough diagnostic check which
is performed on bootup, and secondly a continuous self-checking operation, which checks
the operation of the critical functions whilst it is in service.
2.2
Power-up Errors
If the relay does not appear to power up, use the following to determine whether the fault is
in the external wiring, auxiliary fuse, relay power supply module or the relay front panel.
Test
Action
1
Measure auxiliary voltage on terminals 1 and 2;
verify voltage level and polarity against rating If the auxiliary voltage is correct, go to test 2. Otherwise
the label on front.
check the wiring and fuses in the auxiliary supply.
Terminal 1 is –dc, 2 is +dc
2
Check the LEDs and LCD backlight switch on
at power-up. Also check the N/O (normally
open) watchdog contact for closing.
3
Check the output (nominally 48 V DC)
Table 2:
2.3
Check
If the LEDs and LCD backlight switch on, or the contact
closes and no error code is displayed, the error is probably
on the main processor board in the front panel.
If the LEDs and LCD backlight do not switch on and the
contact does not close, go to test 3.
If there is no field voltage, the fault is probably in the relay
power supply module.
Failure of relay to power up
Error Message or Code On Power-up
The relay performs a self-test during power-up. If it detects an error, a message appears on
the LCD and the powerup sequence stops. If the error occurs when the relay application
software is running, a maintenance record is created and the device reboots.
TS
Troubleshooting
P746/EN TS/J43
MiCOM P40 Agile P746
Test
(TS) 12-7
Check
Action
1
Is an error message or code permanently
displayed during power up?
If the relay locks up and displays an error code permanently,
go to test 2.
If the relay prompts for user input, go to test 4.
If the relay re-boots automatically, go to test 5
2
Record displayed error, then remove and reapply relay auxiliary supply.
Record whether the same error code is displayed when the
relay is rebooted. If no error code is displayed then contact
the local service centre stating the error code and relay
information. If the same code is displayed, go to test 3.
Error code Identification
3
The following text messages (in English) are
displayed if a fundamental problem is detected,
preventing the system from booting:
Bus Fail – address lines
These messages indicate that a problem has been detected
SRAM Fail – data lines
on the relay’s main processor board in the front panel.
FLASH Fail format error
FLASH Fail checksum
Code Verify Fail
The following hex error codes relate to errors
detected in specific relay modules:
3.1
0c140005/0c0d0000
Input Module (inc. Opto-isolated inputs)
3.2
0c140006/0c0e0000
Output Relay Cards
3.3
Other error codes relate to hardware or software problems
The last four digits provide details on the actual
on the main processor board. Contact GE with details of the
error.
problem for a full analysis.
4
The relay displays message for corrupt settings The power up tests have detected corrupted relay settings.
and prompts for restoration of defaults to the
Restore the default settings to allow the power-up to
affected settings.
complete, and then re-apply the application-specific settings.
5
Error 0x0E080000, programmable scheme logic error due to
excessive execution time. If relay powers up successfully,
check programmable logic for feedback paths.
Other error codes will relate to software errors on the main
processor board, contact GE.
Table 3:
The relay resets when the power up is
complete. A record error code displayed
Power-up self-test error
TS
P746/EN TS/J43
Troubleshooting
(TS) 12-8
2.4
MiCOM P40 Agile P746
Out of Service LED ON at Power-up
Test
Check
Action
Using the relay menu confirm the Commission If the setting is Enabled, disable the test mode and make
Test or Test Mode setting is Enabled. If it is not sure the Out of Service LED is OFF.
Enabled, go to test 2.
1
Check for the H/W Verify Fail maintenance record. This
indicates a discrepancy between the relay model number
Select the VIEW RECORDS column then view and the hardware. Examine the “Maint. Data”. This indicates
the last maintenance record from the menu
the causes of the failure using bit fields:
Bit Meaning
2
Table 4:
2.5
0
The application type field in the model number
does not match the software ID
1
The application field in the model number does
not match the software ID
2
The variant 1 field in the model number does not
match the software ID
3
The variant 2 field in the model number does not
match the software ID
4
The protocol field in the model number does not
match the software ID
5
The language field in the model number does not
match the software ID
6
The VT type field in the model number is incorrect
(110V VTs fitted)
7
The VT type field in the model number is incorrect
(440V VTs fitted)
8
The VT type field in the model number is incorrect
(no VTs fitted)
Out of service LED illuminated
Error Code During Operation
The relay performs continuous self-checking. If the relay detects an error it displays an error
message, logs a maintenance record and after a short delay resets itself. A permanent
problem (for example due to a hardware fault) is usually detected in the power-up sequence.
In this case the relay displays an error code and halts. If the problem was transient, the relay
reboots correctly and continues operation. By examining the maintenance record logged, the
nature of the detected fault can be determined.
Other error codes relate to problems within the main processor board software. Contact GE
through our Contact Centre at www.gegridsolutions.com, with details of the problem for a full
analysis.
TS
2.6
Mal-operation During Testing
2.6.1
Failure of Output Contacts
An apparent failure of the relay output contacts may be caused by the relay configuration;
the following tests should be performed to identify the real cause of the failure.
Note:
The relay self-tests verify that the coil of the contact has been energized. An
error will be displayed if there is a fault in the output relay board.
Troubleshooting
P746/EN TS/J43
MiCOM P40 Agile P746
Test
Check
Action
1
Is the Out of Service LED ON?
If this LED is ON, the relay may be in test mode or the
protection has been disabled due to a hardware verify error
2
Examine the Contact status in the
Commissioning section of the menu.
If the relevant bits of the contact status are operated, go to
test 4, if not go to test 3.
3
If the protection element does not operate, check the test is
Examine the fault record or use the test port to correctly applied.
check the protection element is operating
If the protection element operates, check the programmable
correctly.
logic to make sure the protection element is correctly
mapped to the contacts.
4
Using the Commissioning or Test mode
function, apply a test pattern to the relevant
relay output contacts.
Consult the correct external connection diagram
and use a continuity tester at the rear of the
relay to check the relay output contacts operate.
Table 6:
2.6.2
(TS) 12-9
If the output relay operates, the problem must be in the
external wiring to the relay. If the output relay does not
operate the output relay contacts may have failed (the selftests verify that the relay coil is being energized). Ensure the
closed resistance is not too high for the continuity tester to
detect.
Failure of output contacts
Failure of Opto-inputs
The opto-isolated inputs are mapped onto the relay’s internal DDB signals using the
programmable scheme logic. If an input is not recognised by the scheme logic, use the Opto
I/P Status cell in the COMMISSION TESTS column menu to check whether the problem is
in the opto-isolated input itself or the mapping of its signal to the scheme logic functions.
If the device does not correctly read the opto-input state, test the applied signal. Verify the
connections to the opto-input using the wiring diagram and the nominal voltage settings in
the OPTO CONFIG column. To do this:
1. Select the nominal voltage for all opto-inputs by selecting one of the five standard
ratings in the Global Nominal V cell.
2. Select Custom to set each opto-input individually to a nominal voltage.
3. Using a voltmeter, check that the voltage on its input terminals is greater than the
minimum pick-up level (See the Technical Data chapter for opto pick-up levels).
If the signal is correctly applied, this indicates failure of an opto-input, which may be situated
on standalone opto input board, or on an opto-input board that is part of the input module.
Separate opto-input boards can simply be replaced. If, however, the faulty opto-input board
is part of the input module, the complete input module should be replaced. This is because
the analogue input module cannot be individually replaced without dismantling the module
and recalibration of the relay.
2.6.3
Incorrect Analog Signals
If the measured analogue quantities do not seem correct, use the measurement function to
determine the type of problem. The measurements can be configured in primary or
secondary terms.
1. Compare the displayed measured values with the actual magnitudes at the terminals.
2. Check the correct terminals are used.
3. Check the CT and VT ratios set are correct.
4. Check the phase displacement to confirm the inputs are correctly connected.
2.7
PSL Editor Troubleshooting
A failure to open a connection could be because of one or more of the following:
• The relay address is not valid (this address is always 1 for the front port)
• Password in not valid
• Communication Set-up (COM port, Baud rate, or Framing) is not correct
• Transaction values are not suitable for the relay or the type of connection
TS
P746/EN TS/J43
(TS) 12-10
Troubleshooting
MiCOM P40 Agile P746
• The connection cable is not wired correctly or broken.
• The option switches on any protocol converter used may be incorrectly set
2.7.1
Diagram Reconstruction
Although a scheme can be extracted from a relay, a facility is provided to recover a scheme
if the original file is unobtainable.
A recovered scheme is logically correct, but much of the original graphical information is lost.
Many signals are drawn in a vertical line down the left side of the canvas. Links are drawn
orthogonally using the shortest path from A to B. Any annotation added to the original
diagram such as titles and notes are lost.
Sometimes a gate type may not be what was expected. For example, a single-input AND
gate in the original scheme appears as an OR gate when uploaded. Programmable gates
with an inputs-to-trigger value of 1 will also appear as OR gates.
2.7.2
PSL Version Check
The PSL is saved with a version reference, time stamp and CRC check. This gives a visual
check whether the default PSL is in place or whether a new application has been
downloaded.
2.8
Repair and Modification Procedure
Please follow these steps to return an Automation product to us:
1.
Get the Repair and Modification Authorization Form (RMA)
An electronic version of the RMA form is available from the following:
contact.centre@ge.com
2.
Fill in RMA form
Fill in only the white part of the form.
Please ensure that all fields marked (M) are completed such as:
• Equipment model
• Model No. and Serial No.
• Description of failure or modification required (please be specific)
• Value for customs (in case the product requires export)
• Delivery and invoice addresses
• Contact details
3.
TS
Send the RMA form to your local contact
For a list of local service contacts worldwide, email us at:
contact.centre@ge.com
4. The local service contact provides the shipping
Your local service contact provides you with all the information needed to ship the product:
• Pricing details
• RMA n°
• Repair center address
If required, an acceptance of the quote must be delivered before going to next stage.
5.
Send the product to the repair center
• Address the shipment to the repair center specified by your local contact
• Ensure all items are protected by appropriate packaging: anti-static bag and foam
protection
• Ensure a copy of the import invoice is attached with the unit being returned
Troubleshooting
MiCOM P40 Agile P746
P746/EN TS/J43
(TS) 12-11
• Ensure a copy of the RMA form is attached with the unit being returned
• E-mail or fax a copy of the import invoice and airway bill document to your local contact.
TS
P746/EN TS/J43
(TS) 12-12
TS
Troubleshooting
MiCOM P40 Agile P746
SCADA Communications
P746/EN SC/J43
MiCOM P40 Agile P746
(SC) 13-1
SCADA COMMUNICATIONS
Hardware Suffix:
M
Software Version:
91
SC
P746/EN SC/J43
(SC) 13-2
SC
SCADA Communications
MiCOM P40 Agile P746
SCADA Communications
MiCOM P40 Agile P746
P746/EN SC/J43
(SC) 13-3
CONTENTS
1
OVERVIEW
9
2
COMMUNICATION INTERFACES
10
3
SERIAL COMMUNICATION
11
3.1
USB Front Port
11
3.2
EIA(RS)485 Bus
11
3.2.1
EIA(RS)485 Biasing Requirements
12
3.3
K-Bus
12
4
STANDARD ETHERNET COMMUNICATION
14
5
REDUNDANT ETHERNET COMMUNICATION
15
5.1
Supported Protocols
15
5.2
Parallel Redundancy Protocol
15
5.3
High-availability Seamless Redundancy (HSR)
16
5.3.1
HSR Multicast Topology
16
5.3.2
HSR Unicast Topology
17
5.3.3
HSR Application in the Substation
18
5.4
Rapid Spanning Tree Protocol
18
5.5
Failover
19
5.6
Configuring IP Addresses
19
5.6.1
Configuring the IED IP Address
20
5.6.2
Configuring the REB IP Address
20
5.7
Redundant Ethernet Configurator
20
5.7.1
Connecting the IED to a PC
20
5.7.2
Installing the Configurator
21
5.7.3
Starting the Configurator
21
5.7.4
PRP/HSR Device Identification
21
5.7.5
Selecting the Device Mode
22
5.7.6
PRP/HSR IP Address Configuration
22
5.7.7
SNTP IP Address Configuration
22
5.7.8
Check for Connected Equipment
22
5.7.9
PRP Configuration
22
5.7.10
HSR Configuration
22
5.7.11
Filtering Database
23
5.7.12
End of Session
24
5.8
RSTP Configurator
24
5.8.1
Connecting the IED to a PC
24
5.8.2
Installing the Configurator
25
5.8.3
Starting the Configurator
25
5.8.4
RSTP Device Identification
25
SC
P746/EN SC/J43
(SC) 13-4
SC
SCADA Communications
MiCOM P40 Agile P746
5.8.5
RSTP IP Address Configuration
26
5.8.6
SNTP IP Address Configuration
26
5.8.7
Check for Connected Equipment
26
5.8.8
RSTP Configuration
26
5.8.8.1
Bridge Parameters
26
5.8.8.2
Port Parameters
27
5.8.8.3
Port States
27
5.8.9
End of Session
27
6
SIMPLE NETWORK MANAGEMENT PROTOCOL (SNMP)
28
6.1
SNMP Management Information Bases
28
6.2
Main Processor MIBS Structure
28
6.3
Redundant Ethernet Board MIB Structure
29
6.4
Accessing the MIB
32
6.5
Main Processor SNMP Configuration
32
7
DATA PROTOCOLS
34
7.1
Courier
34
7.1.1
Physical Connection and Link Layer
34
7.1.2
Courier Database
35
7.1.3
Setting Categories
35
7.1.4
Setting Changes
35
7.1.5
Event Extraction
35
7.1.5.1
Automatic Event Extraction
35
7.1.5.2
Manual Event Record Extraction
36
7.1.6
Disturbance Record Extraction
37
7.1.7
Programmable Scheme Logic Settings
37
7.1.8
Time Synchronisation
37
7.1.9
Courier Configuration
38
7.2
IEC 60870-5-103
39
7.3
Physical Connection and Link Layer
39
7.3.1
Initialisation
40
7.3.2
Time Synchronisation
40
7.3.3
Spontaneous Events
40
7.3.4
General Interrogation (GI)
40
7.3.5
Cyclic Measurements
40
7.3.6
Commands
40
7.3.7
Test Mode
41
7.3.8
Disturbance Records
41
7.3.9
Command/Monitor Blocking
41
7.3.10
IEC 60870-5-103 Configuration
41
7.4
DNP3.0
42
7.4.1
Physical Connection and Link Layer
43
SCADA Communications
MiCOM P40 Agile P746
P746/EN SC/J43
(SC) 13-5
7.4.2
Object 1 Binary Inputs
43
7.4.3
Object 10 Binary Outputs
43
7.4.4
Object 20 Binary Counters
44
7.4.5
Object 30 Analog Input
44
7.4.6
Object 40 Analogue Output
45
7.4.7
Object 50 Time Synchronisation
45
7.4.8
DNP3 Device Profile
45
7.4.8.1
DNP3 Device Profile Table
45
7.4.8.2
DNP3 Implementation Table
47
7.4.8.3
DNP3 Internal Indications
55
7.4.8.4
DNP3 Response Status Codes
56
7.4.9
DNP3 Configuration
57
7.4.9.1
DNP3 configurator
58
7.5
Modbus
58
7.5.1
Physical connection and link layer
58
7.5.2
MODBUS Functions
59
7.5.3
Response codes
59
7.5.4
Register Mapping
59
7.5.5
Event Extraction
60
7.5.5.1
Automatic Event Record Extraction
60
7.5.5.2
Manual Event Record Extraction
60
7.5.5.3
Record Data
60
7.5.6
Disturbance Record Extraction
61
7.5.6.1
Manual extraction procedure
62
7.5.6.2
Automatic Extraction Procedure
63
7.5.6.3
Extracting the Disturbance Data
65
7.5.7
Setting Changes
68
7.5.8
Password Protection
68
7.5.9
Control and Support Settings
68
7.5.10
Protection and Disturbance Recorder Settings
68
7.5.11
Time Synchronisation
69
7.5.12
Power & Energy Measurement Data Formats (G29 & G125)
70
7.5.13
Modbus Configuration
71
7.6
IEC 61850
73
7.6.1
Benefits of IEC 61850
73
7.6.2
IEC 61850 Interoperability
73
7.6.3
The IEC 61850 Data Model
73
7.6.4
IEC 61850 in MiCOM Relays
74
7.6.5
IEC 61850 Data Model Implementation
75
7.6.6
IEC 61850 communication Services Implementation
75
7.6.7
IEC 61850 Peer-to-Peer (GOOSE) Communications
75
7.6.8
Goose message Validation
75
SC
P746/EN SC/J43
(SC) 13-6
SCADA Communications
MiCOM P40 Agile P746
7.6.9
Mapping GOOSE Messages to Virtual Inputs
75
7.6.9.1
IEC 61850 GOOSE Configuration
76
7.6.10
Ethernet Functionality
76
7.6.11
IEC 61850 Configuration
76
7.6.11.1 IEC 61850 Configuration Banks
77
7.6.11.2 IEC 61850 Network Connectivity
77
7.6.12
77
IEC 61850 Edition 2
7.6.12.1 Backward Compatibility
77
7.6.12.2 Edition-2 Common Data Classes
78
7.6.12.3 Standby Protection Redundancy
79
8
READ ONLY MODE
81
8.1
IEC 60870-5-103 Protocol Blocking
81
8.2
Courier Protocol Blocking
81
8.3
IEC 61850 Protocol Blocking
82
8.4
Read-only Settings
82
8.5
Read-only DDB Signals
82
9
TIME SYNCHRONISATION
83
9.1
Demodulated IRIG-B
83
9.1.1
IRIG-B Implementation
84
9.2
SNTP
84
9.2.1
Loss of SNTP Server Signal Alarm
84
9.3
IEEE 1588 Precision Time Protocol
84
9.3.1
Accuracy and Delay Calculation
84
9.3.2
PTP Domains
85
9.4
Time Synchronsiation using the Communication Protocols
85
FIGURES
SC
Figure 1: EIA(RS)485 biasing circuit
12
Figure 2: EIA(RS)485 biasing circuit
13
Figure 3: Relay attached to Separate LANs
16
Figure 5: HSR Multicast Topology
17
Figure 6: HSR Unicast Topology
18
Figure 7: HSR Application in the Substation
18
Figure 8: IED attached to Redundant Ethernet Star or Ring Circuit
19
Figure 9: IED and REB IP Address Configuration
20
Figure 10: Connection using (a) an Ethernet switch and (b) a media converter
21
Figure 11: Connection using (a) an Ethernet switch and (b) a media converter
25
Figure 12: Control input behaviour
44
Figure 13: Manual selection of a disturbance record
63
Figure 14: Automatic selection of a disturbance – method 1
64
SCADA Communications
MiCOM P40 Agile P746
P746/EN SC/J43
(SC) 13-7
Figure 15: Automatic selection of a disturbance – option 2
65
Figure 16: Configuration file extraction
66
Figure 17: Data file extraction
67
Figure 18: Data Model Layers in IEC 61850
74
Figure 19: Edition 2 System - Backward Compatibility
78
Figure 20: Edition 1 System - Forward Compatibility Issues
78
Figure 21: Example of Standby IED
79
Figure 22: Standby IED Activation Process
80
Figure 23: GPS Satellite Timing Signal
83
Figure 24: Timing Error using Ring or Line Topology
85
SC
P746/EN SC/J43
(SC) 13-8
SC
SCADA Communications
MiCOM P40 Agile P746
SCADA Communications
MiCOM P40 Agile P746
1
P746/EN SC/J43
(SC) 13-9
OVERVIEW
This product supports Substation Automation System (SAS), and Supervisory Control and
Data Acquisition (SCADA) communication. The support embraces the evolution of
communications technologies that have taken place since microprocessor technologies were
introduced into protection, control, and monitoring relays
As standard, all products support rugged serial communications for SCADA and SAS
applications. By option, any product can support Ethernet communications for more
advanced SCADA and SAS applications.
The descriptions in this chapter do not aim to fully describe the protocol itself. Refer to the
relevant documentation protocol for this information. This chapter serves to describe the
specific implementation of the protocol in the relay.
SC
P746/EN SC/J43
SCADA Communications
(SC) 13-10
2
MiCOM P40 Agile P746
COMMUNICATION INTERFACES
The products have a number of standard and optional communication interfaces. The
standard and optional hardware and protocols are summarised below:
Port
Front
Availability
Standard
Rear Port 1
(RP1 copper)
Rear Port 1
(RP1 fibre)
Rear Port 2
(RP2)
Ethernet
Note:
Physical layer
Use
Data Protocols
USB Type B
Local settings
Courier
Standard
RS232 / RS485 /
K-Bus
SCADA
Courier, IEC60870-5-103,
Optional
Fibre
Optional
RS232 / RS485 /
K-Bus
Optional
Ethernet
Remote settings
SCADA
Courier, IEC60870-5-103,
Remote settings
SCADA
SK4: Courier only
Remote settings
SK5: InterMicom only
IEC 61850
IEC 61850, Courier
(tunnelled)
Optional communications boards are always fitted into slot A.
It is only possible to fit one optional communications board, therefore
RP2 and Ethernet communications are mutually exclusive.
SC
SCADA Communications
P746/EN SC/J43
MiCOM P40 Agile P746
3
(SC) 13-11
SERIAL COMMUNICATION
The physical layer standards that are used for serial communications for SCADA purposes
are:
• EIA(RS)485 (often abbreviated to RS485)
• K-Bus (a proprietary customization of RS485)
USB is used for local communication with the relay (for transferring settings and
downloading firmware updates).
RS485 is similar to RS232 but for longer distances and it allows daisy-chaining and multidropping of relays.
K-Bus is a proprietary protocol quite similar to RS485, but it cannot be mixed on the same
link as RS485. Unlike RS485, K-Bus signals applied across two terminals are not polarised.
It is important to note that these are not data protocols. They only describe the physical
characteristics required for two devices to communicate with each other.
For a description of the K-Bus standard see K-Bus (on page546) and GE's K-Bus interface
guide reference R6509.
A full description of the RS485 is available in the published standard.
3.1
USB Front Port
The USB interface uses the proprietary Courier protocol for local communication with the
MiCOM S1 Agile settings application software.
This is intended for temporary local connection and is not suitable for permanent connection.
This interface uses a fixed baud rate of 19200 bps, 11-bit frame (8 data bits, 1 start bit, 1
stop bit, even parity bit), and a fixed device address of '1'.
The USB interface is a Type B connector. Normally a Type A to Type B USB cable will be
required to communicate between MiCOM S1 Agile and the device.
3.2
EIA(RS)485 Bus
The RS485 two-wire connection provides a half-duplex fully isolated serial connection to the
product. The connection is polarized but there is no agreed definition of which terminal is
which. If the master is unable to communicate with the product, and the communication
parameters match, then it is possible that the two-wire connection is reversed.
The RS485 bus must at each end with 120 Ω 0.5 W terminating resistors between the signal
wires.
The RS485 standard requires that each device be directly connected to the actual bus.
Stubs and tees are forbidden. Loop bus and Star topologies are not part of the RS485
standard and are also forbidden.
Two-core screened twisted pair cable should be used. The final cable specification is
dependent on the application, although a multi-strand 0.5 mm2 per core is normally
adequate. The total cable length must not exceed 1000 m. It is important to avoid circulating
currents, which can cause noise and interference, especially when the cable runs between
buildings. For this reason, the screen should be continuous and connected to ground at one
end only, normally at the master connection point.
The RS485 signal is a differential signal and there is no signal ground connection. If a signal
ground connection is present in the bus cable then it must be ignored. At no stage should
this be connected to the cable's screen or to the product’s chassis. This is for both safety
and noise reasons.
It may be necessary to bias the signal wires to prevent jabber. Jabber occurs when the
signal level has an indeterminate state because the bus is not being actively driven. This can
occur when all the slaves are in receive mode and the master is slow to turn from receive
mode to transmit mode. This may be because the master is waiting in receive mode, in a
high impedance state, until it has something to transmit. Jabber causes the receiving
SC
P746/EN SC/J43
SCADA Communications
(SC) 13-12
MiCOM P40 Agile P746
device(s) to miss the first bits of the first character in the packet, which results in the slave
rejecting the message and consequently not responding. Symptoms of this are; poor
response times (due to retries), increasing message error counts, erratic communications,
and in the worst case, complete failure to communicate.
3.2.1
EIA(RS)485 Biasing Requirements
Biasing requires that the signal lines be weakly pulled to a defined voltage level of about 1 V.
There should only be one bias point on the bus, which is best situated at the master
connection point. The DC source used for the bias must be clean to prevent noise being
injected.
Note:
Some devices may be able to provide the bus bias, in which case external
components will not be required.
Figure 1: EIA(RS)485 biasing circuit
It is extremely important that the 120 Ω termination resistors are fitted.
Otherwise the bias voltage may be excessive and may damage the devices
connected to the bus.
It is possible to use the products field voltage output (48 V DC) to bias the bus using values
of 2.2 kΩ (½W) as bias resistors instead of the 180 Ω resistors shown in the above diagram.
The following warnings apply:
• It is extremely important that the 120 Ω termination resistors are fitted. Failure to do so
will result in an excessive bias voltage that may damage the devices connected to the
bus.
SC
• As the field voltage is much higher than required, GE cannot assume responsibility for
any damage that may occur to a device connected to the network as a result of
incorrect application of this voltage.
• Ensure that the field voltage is not being used for other purposes (i.e. powering logic
inputs) as this may cause noise to be passed to the communication network.
3.3
K-Bus
K-Bus is a robust signalling method based on RS485 voltage levels. K-Bus incorporates
message framing, based on a 64 kbps synchronous HDLC protocol with FM0 modulation to
increase speed and security.
The rear interface is used to provide a permanent connection for K-Bus, which allows multidrop connection.
SCADA Communications
P746/EN SC/J43
MiCOM P40 Agile P746
(SC) 13-13
A K-Bus spur consists of up to 32 relays connected together in a multi-drop arrangement
using twisted pair wiring. The K-Bus twisted pair connection is non-polarised.
It is not possible to use a standard EIA(RS)232 to EIA(RS)485 converter to convert IEC
60870-5 FT1.2 frames to KBus. A protocol converter, namely the KITZ101, KITZ102 or
KITZ201, must be used for this purpose. Please consult GE for information regarding the
specification and supply of KITZ devices. The following figure demonstrates a typical K-Bus
connection.
C
C
C
IED
IED
IED
RS232
mputer
RS232-USB converter
K-Bus
KITZ protocol converter
Figure 2: EIA(RS)485 biasing circuit
Note:
An RS232-USB converter is only needed if the local computer does not
provide an RS232 port.
Further information about K-Bus is available in the publication R6509: K-Bus Interface
Guide, which is available on request.
SC
P746/EN SC/J43
(SC) 13-14
4
SCADA Communications
MiCOM P40 Agile P746
STANDARD ETHERNET COMMUNICATION
The type of Ethernet board depends on the chosen model. The available boards and their
features are described in the Firmware Design chapter of this manual.
The Ethernet interface is required for IEC 61850. With either of these protocols, the Ethernet
interface also offers communication with the settings application software for remote
configuration and record extraction.
Fibre optic connection is recommended for use in permanent connections in a substation
environment, as it offers advantages in terms of noise rejection. The fibre optic port provides
100 Mbps communication and uses type BFOC 2.5 (ST) connectors. Fibres should be
suitable for 1300 nm transmission and be multimode 50/125 µm or 62.5/125 µm.
Connection can also be made to a 10Base-T or a 100Base-TX Ethernet switch using the
RJ45 port.
SC
SCADA Communications
P746/EN SC/J43
MiCOM P40 Agile P746
5
(SC) 13-15
REDUNDANT ETHERNET COMMUNICATION
Redundancy is required where a single point of failure cannot be tolerated. It is required in
critical applications such as substation automation. Redundancy acts as an insurance policy,
providing an alternative route if one route fails.
Ethernet communication redundancy is available for most GE products, using a Redundant
Ethernet Board (REB). The REB is a Network Interface Card (NIC), which incorporates an
integrated Ethernet switch. The board provides two Ethernet transmitter/receiver pairs.
In addition to the two Ethernet transmitter/receiver pairs, the REB provides link activity
indication in the form of LEDs, link fail indication in the form of watchdog contacts, and a
dedicated time synchronisation input.
The dedicated time synchronisation input is designed to connect to an IRIG-B signal. Both
modulated and un-modulated IRIG-B formats are supported according to the selected option.
Simple Network Time Protocol (SNTP) is supported over the Ethernet communications.
5.1
Supported Protocols
A range of Redundant Ethernet Boards are available to support different protocols for
different requirements. One of the key requirements of substation redundant
communications is "bumpless" redundancy. This means the ability to transfer from one
communication path to another without noticeable consequences. Standard protocols of the
time could not meet the demanding requirements of network availability for substation
automation solutions. Switch-over times were unacceptably long. For this reason, companies
developed proprietary protocols. More recently, however, standard protocols, which support
bumpless redundancy (SHP, DHP) have been developed and ratified.
As well as supporting standard non-bumpless protocols such as RSTP, the REB was
originally designed to support bumpless redundancy, using proprietary protocols (SHP, DHP)
before the standard protocols became available. Since then, variants have been produced
for the newer standard protocols.
REB variants for each of the following protocols are available:
• PRP (Parallel Redundancy Protocol)
• HSR (High-availability Seamless Redundancy)
• RSTP (Rapid Spanning Tree Protocol)
• Failover
PRP and HSR are open standards, so their implementation is compatible with any standard
PRP or HSR device respectively. PRP provides "bumpless" redundancy. RSTP is also an
open standard, so its implementation is compatible with any standard RSTP devices. RSTP
provides redundancy, however, it is not "bumpless".
Note:
5.2
The protocol you require must be selected at the time of ordering.
Parallel Redundancy Protocol
PRP (Parallel Redundancy Protocol) is defined in IEC 62439-3. PRP provides bumpless
redundancy and meets the most demanding needs of substation automation. The PRP
implementation of the REB is compatible with any standard PRP device.
PRP uses two independent Ethernet networks operating in parallel. PRP systems are
designed so that there should be no common point of failure between the two networks, so
the networks have independent power sources and are not connected together directly.
Devices designed for PRP applications have two ports attached to two separate networks
and are called Doubly Attached Nodes (DAN). A DAN has two ports, one MAC address and
one IP address.
The sending node replicates each frame and transmits them over both networks. The
receiving node processes the frame that arrives first and discards the duplicate. Therefore
SC
P746/EN SC/J43
SCADA Communications
(SC) 13-16
MiCOM P40 Agile P746
there is no distinction between the working and backup path. The receiving node checks that
all frames arrive in sequence and that frames are correctly received on both ports.
Devices such as printers that have a single Ethernet port can be connected to either of the
networks but will not directly benefit from the PRP principles. Such devices are called Singly
Attached Nodes (SAN). For devices with a single Ethernet port that need to connect to both
LANs, this can be achieved by employing Ethernet Redundancy Boxes (sometimes
abbreviated to RedBox). Devices with a single Ethernet port that connect to both LANs by
means of a RedBox are known as Virtual DAN (VDAN).
The figure below summarises DAN, SAN, VDAN, LAN, and RedBox connectivity.
DAN
DAN
DAN
SAN
LAN B
LAN A
REDUNDANCY
BOX
VDAN
VDAN
SAN
SAN
VDAN
E01028
Figure 3: Relay attached to Separate LANs
In a DAN, both ports share the same MAC address so it does not affect the way devices talk
to each other in an Ethernet network (Address Resolution Protocol at layer 2). Every data
frame is seen by both ports.
When a DAN sends a frame of data, the frame is duplicated on both ports and therefore on
both LAN segments. This provides a redundant path for the data frame if one of the
segments fails. Under normal conditions, both LAN segments are working and each port
receives identical frames.
5.3
High-availability Seamless Redundancy (HSR)
HSR is standardized in IEC 62439-3 (clause 5) for use in ring topology networks. Similar to
PRP, HSR provides bumpless redundancy and meets the most demanding needs of
substation automation. HSR has become the reference standard for ring-topology networks
in the substation environment. The HSR implementation of the redundancy Ethernet board
(REB) is compatible with any standard HSR device.
SC
HSR works on the premise that each device connected in the ring is a doubly attached node
running HSR (referred to as DANH). Similar to PRP, singly attached nodes such as printers
are connected via Ethernet Redundancy Boxes (RedBox).
5.3.1
HSR Multicast Topology
When a DANH is sending a multicast frame, the frame (C frame) is duplicated (A frame and
B frame), and each duplicate frame A/B is tagged with the destination MAC address and the
sequence number. The frames A and B differ only in their sequence number, which is used
to identify one frame from the other. Each frame is sent to the network via a separate port.
SCADA Communications
P746/EN SC/J43
MiCOM P40 Agile P746
(SC) 13-17
The destination DANH receives two identical frames, removes the HSR tag of the first frame
received and passes this (frame D) on for processing. The other duplicate frame is
discarded. The nodes forward frames from one port to the other unless it was the node that
injected it into the ring.
Source
DANH
DANH
Redbox
C frame
D frame
A frame
Switch
D frame
B frame
Singly Attached
Nodes
D frame
D frame
DANH
DANH
D frame
DANH
V01030
Figure 4: HSR Multicast Topology
Only about half of the network bandwidth is available in HSR for multicast or broadcast
frames because both duplicate frames A & B circulate the full ring.
5.3.2
HSR Unicast Topology
With unicast frames, there is just one destination and the frames are sent to that destination
alone. All non-recipient devices simply pass the frames on. They do not process them in any
way. In other words, D frames are produced only for the receiving DANH. This is illustrated
below.
SC
P746/EN SC/J43
SCADA Communications
(SC) 13-18
MiCOM P40 Agile P746
Source
DANH
DANH
Redbox
Switch
C frame
B frame
A frame
Singly Attached
Nodes
D frame
DANH
DANH
DANH
Destination
V01031
Figure 5: HSR Unicast Topology
For unicast frames, the whole bandwidth is available as both frames A & B stop at the
destination node.
5.3.3
HSR Application in the Substation
LINK
RX
TX
reset
LINK
RX
TX
C
C
C
C
C
C
C
C
SC
E01066
Figure 6: HSR Application in the Substation
5.4
Rapid Spanning Tree Protocol
RSTP is a standard used to quickly reconnect a network fault by finding an alternative path.
It stops network loops whilst enabling redundancy. It can be used in star or ring connections
as shown in the following figure.
SCADA Communications
P746/EN SC/J43
MiCOM P40 Agile P746
(SC) 13-19
Switch 1
Switch 2
Switch 1
Switch 2
IED 1
IED 2
IED 1
IED 2
Star connection with redundant ports
managed by RSTP blocking function.
Ring connection managed by RSTP
blocking function on upper switches
and IEDs interconnected directly.
V01010
Figure 7: IED attached to Redundant Ethernet Star or Ring Circuit
The RSTP implementation in this product is compatible with any devices that use RSTP.
RSTP can recover network faults quickly, but the fault recovery time depends on the number
of devices on the network and the network topology. A typical figure for the fault recovery
time is 300ms. Therefore, RSTP cannot achieve the “bumpless” redundancy that some other
protocols can.
Refer to IEEE 802.1D 2004 standard for detailed information about the opration of the
protocol.
5.5
Failover
Failover is a simple redundancy mechanism that is not tied to any protocol. It works by
selecting a main port and a switching time that can be as low as 2 seconds. When the main
port link fails, the redundant port becomes physically active. At no point are both ports
physically active, which means it can be used on any redundant or non-redundant network.
5.6
Configuring IP Addresses
An IP address is a logical address assigned to a device that uses the Internet Protocol (IP)
for communication with other devices. IP addresses are represented using Decimal Dot
Notation where four sets of decimal numbers are separated by dots as follows:
XXX.XXX.XXX.XXX
For example: 10.86.254.85
An IP address in a network is usually associated with a subnet mask. The subnet mask
defines which network the device belongs to. A subnet mask has the same form as an IP
address.
For example:
SC
255.255.255.0
Both the IED and the REB each have their own IP address. The following diagram shows the
IED as IP1 and the REB as IP2.
Note:
IP1 and IP2 are different but use the same subnet mask.
The switch IP address must be configured through the Ethernet network.
P746/EN SC/J43
SCADA Communications
(SC) 13-20
MiCOM P40 Agile P746
Set by IED Configurator
IED (IP1)
AAA.BBB.CCC.DDD
REB (IP2)
WWW.XXX.YYY.ZZZ
Set by Switch Manager for SHP and DHP
Set by Redundant Ethernet Configurator for
PRP, HSR or RSTP
Set by Hardware Dip Switch SW2 for SHP, DHP
Set by Redundant Ethernet Configurator for PRP, HSR or
RSTP
Fixed at 254 for SHP or DHP
Set by Redundant Ethernet Configurator for PRP, HSR or RSTP
V01069
Figure 8: IED and REB IP Address Configuration
5.6.1
Configuring the IED IP Address
If you are using IEC 61850, set the IED IP address using the IEC 61850 Configurator
software. In the IEC 61850 Configurator, set Media to Single Copper or Redundant Fibre.
5.6.2
Configuring the REB IP Address
The board IP address must be configured before connecting the IED to the network to avoid
an IP address conflict. The way you configure the IP address depends on the redundancy
protocol you have chosen.
PRP/HSR/RSTP
If using PRP, HSR or RSTP, configure the REB IP address using the Redundant Ethernet
Configurator software.
5.7
Redundant Ethernet Configurator
The Redundant Ethernet Configurator tool is intended for MiCOM Px4x relays with
redundant Ethernet using PRP (Parallel Redundancy Protocol), HSR (High-availability
Seamless Redundancy) or RSTP. This tool is used to identify IEDs, switch between
PRP/HSR/RSTP or configure their parameters, configure the redundancy IP address, or
configure the SNTP IP address.
5.7.1
Connecting the IED to a PC
Connect the IED to the PC on which the Configurator tool is used. This connection is done
through an Ethernet switch or through a media converter.
SC
SCADA Communications
P746/EN SC/J43
MiCOM P40 Agile P746
(SC) 13-21
RJ45
Ethernet switch
Media
Converter
TXB RXB
TXA RXA
TX
RXB TXB
RXA TXA
RX
RXB TXB
RXA TXA
IED
(a)
IED
(b)
V01806
Figure 9: Connection using (a) an Ethernet switch and (b) a media converter
5.7.2
Installing the Configurator
To install the configurator:
1. Double click the WinPcap installer.
2. Double click the Configurator installer.
3. Click Next and follow the on-screen instructions.
5.7.3
Starting the Configurator
To start the configurator:
1. Select the Configurator from the Windows Programs menu.
2. The Login screen appears. For user mode login, enter the Login name as User and
click OK with no password.
3. If the login screen does not appear, check all network connections.
4. The main window appears. In the bottom right-hand corner of the main window, click
the Language button to select the language.
5. The Network Board drop-down list shows the Network Board, IP Address and MAC
Address of the PC in which the Configurator is running.
5.7.4
PRP/HSR Device Identification
To configure the redundant Ethernet board, go to the main window and click the Identify
Device button. A list of devices are shown with the following details:
• Device address
• MAC address
• Version number of the firmware
• SNTP IP address
• Date & time of the real-time clock, from the board.
SC
P746/EN SC/J43
(SC) 13-22
SCADA Communications
MiCOM P40 Agile P746
Select the device you wish to configure. The MAC address of the selected device is
highlighted.
5.7.5
Selecting the Device Mode
You must now select the device mode that you wish to use. This will be either PRP or HSR.
To do this, select the appropriate radio button then click the Update button. You will be
asked to confirm a device reboot. Click OK to confirm.
5.7.6
PRP/HSR IP Address Configuration
To change the network address component of the IP address:
4. From the main window click the IP config button. The Device Setup screen appears.
5. Enter the required board IP address and click OK. This is the redundancy network
address, not the IEC 61850 IP address.
6. The board network address is updated and displayed in the main window.
5.7.7
SNTP IP Address Configuration
To Configure the SNTP server IP address:
1. From the main window click the SNTP Config button. The Device setup screen
appears.
2. Enter the required MAC SNTP address and server IP SNTP Address. Click OK.
3. The updated MAC and IP SNTP addresses appear in the main screen.
5.7.8
Check for Connected Equipment
To check what devices are connected to the device being monitored:
1. From the main window, select the device.
2. Click the Equipment button.
3. At the bottom of the main window, a box shows the ports where devices are
connected and their MAC addresses.
5.7.9
PRP Configuration
To view or configure the PRP Parameters:
1. Ensure that you have set the device mode to PRP.
2. Click the PRP/HSR Config button. The PRP Config screen appears.
3. To view the available parameters, click the Get PRP Parameters button.
4. To change the parameters, click the Set Parameters button and modify their values.
If you need to restore the default values of the parameters, click the Restore Defaults button.
The configurable parameters are as follows:
• Multicast Address: Use this field to configure the multicast destination address. All
DANPs in the network must be configured to operate with the same multicast address
for the purpose of network supervision.
SC
• Node Forget Time: This is the time after which a node entry is cleared in the nodes
table.
• Life Check Interval: This defines how often a node sends a PRP_Supervision frame.
All DANPs shall be configured with the same Life Check Interval.
5.7.10
HSR Configuration
To view or configure the HSR Parameters:
1. Click the PRP/HSR Config button. The HSR Config screen appears.
SCADA Communications
MiCOM P40 Agile P746
P746/EN SC/J43
(SC) 13-23
2. To view the available parameters in the board that is connected, click the Retrieve
HSR Parameters from IED button.
3. To change the parameters, click the Set Parameters button and modify their values.
If you need to restore the default values of the parameters, click the Restore Defaults
button.
The configurable parameters are as follows:
• Multicast Address: Use this field to configure the multicast destination address. All
DANPs in the network must be configured to operate with the same multicast address
for the purpose of network supervision.
• Node Forget Time: This is the time after which a node entry is cleared in the nodes
table.
• Life Check Interval: This defines how often a node sends a PRP_Supervision frame.
All DANPs must be configured with the same Life Check Interval.
• Proxy Node Table Forget Time: This is the time after which a node entry is cleared
in the ProxyTable
• Proxy Node Table Max Entries: This is the maximum number of entries in the
ProxyTable
• Entry Forget Time: This is the time after which an entry is removed from the
duplicates
• Node Reboot Interval: This is the minimum time during which a node that reboots
remains silent
5.7.11
Filtering Database
The Filtering Database is used to determine how frames are forwarded or filtered across the
on-board Ethernet switch. Filtering information specifies the set of ports to which frames
received from a specific port are forwarded.
The Ethernet switch examines each received frame to see if the frame's destination address
matches a source address listed in the Filtering Database. If there is a match, the device
uses the filtering/forwarding information for that source address to determine how to forward
or filter the frame. Otherwise the frame is forwarded to all the ports in the Ethernet switch
(broadcast).
General tab
The Filtering Database contains two types of entry; static and dynamic. The Static Entries
are the source addresses entered by an administrator. The Dynamic Entries are the source
addresses learnt by the switch process. The Dynamic Entries are removed from the Filtering
Database after the Ageing Time. The Database holds a maximum of 1024 entries.
1.
To access the forwarding database functions, if required, click the Filtering
Database button in the main window.
2.
To view the Forwarding Database Size, Number of Static Entries and Number of
Dynamic Entries, click Read Database Info.
3.
To set the Aging Time, enter the number of seconds in the text box and click the
Set button.
Filtering Entries tab
The Filtering Database configuration pages are used to view, add or delete entries from the
Filtering Database. This feature is available only for the administrator. This Filtering
Database is mainly used during the testing to verify the PRP/HSR functionality. To add an
entry in the forwarding database, click the Filtering Entries tab. Configure as follows:
1. Select the Port Number and MAC Address
2. Set the Entry type (Dynamic or Static)
3. Set the cast type (Unicast or Multicast)
SC
P746/EN SC/J43
SCADA Communications
(SC) 13-24
MiCOM P40 Agile P746
4. Set the MGMT and Rate Limit
5. Click the Create button. The new entry appears in the forwarding database.
To delete an entry from the forwarding database, select the entry and click the Delete Entry
button.
Goose Filtering tab
This page configures the source MACs from which GOOSE messages will be allowed or
blocked. The filtering can be configured by either the MAC address range boxes or by
selecting or unselecting the individual MAC addresses in the MAC table. After you have
defined the addresses to be allowed or blocked you need to update the table and apply the
filter:
• Update Table: This updates the MAC table according to the filtering range entered in
the MAC address range boxes.
• Apply Filter: This applies the filtering configuration in the MAC table to the HSR/PRP
board.
5.7.12
End of Session
To finish the session:
1. In the main window, click the Quit button, a new screen appears.
2. If a database backup is required, click Yes, a new screen appears.
3. Click the ... button to browse the path. Enter the name in the text box.
5.8
RSTP Configurator
The RSTP Configurator tool is intended for MiCOM Px4x relays with redundant Ethernet
using RSTP (Rapid Spanning Tree Protocol). This tool is used to identify relays, configure
the redundancy IP address, configure the SNTP IP address and configure the RSTP
parameters.
5.8.1
Connecting the IED to a PC
Connect the relay to the PC on which the Configurator tool is used. This connection is done
through an Ethernet switch or through a media converter.
SC
SCADA Communications
P746/EN SC/J43
MiCOM P40 Agile P746
(SC) 13-25
RJ45
Ethernet switch
Media
Converter
TX2 RX2
TX1 RX1
TX
RX2 TX2
RX1 TX1
RX
RX2 TX2
RX1 TX1
IED
(a)
IED
(b)
V01803
Figure 10: Connection using (a) an Ethernet switch and (b) a media converter
5.8.2
Installing the Configurator
To install the configurator:
5.8.3
1.
Double click the WinPcap installer.
2.
Double click the Configurator installer.
3.
Click Next and follow the on-screen instructions.
Starting the Configurator
To start the configurator:
5.8.4
1.
Select the Configurator from the Windows Programs menu.
2.
The Login screen appears. For user mode login, enter the Login name as User
and click OK with no password.
3.
If the login screen does not appear, check all network connections.
4.
The main window appears. In the bottom right-hand corner of the main window,
click the Language button to select the language.
5.
The Network Board drop-down list shows the Network Board, IP Address and
MAC Address of the PC in which the Configurator is running.
RSTP Device Identification
To configure the redundant Ethernet board, go to the main window and click Identify Device.
Note:
Due to the time needed to establish the RSTP protocol, wait 25 seconds
between connecting the PC to the IED and clicking the Identify Device
button.
The redundant Ethernet board connected to the PC is identified and its details are listed.
• Device address
• MAC address
• Version number of the firmware
SC
P746/EN SC/J43
SCADA Communications
(SC) 13-26
MiCOM P40 Agile P746
• SNTP IP address
• Date & time of the real-time clock, from the board.
5.8.5
RSTP IP Address Configuration
To change the network address component of the IP address,
From the main window click the IP Config button.
5.8.6
1.
The Device Setup screen appears showing the IP Base Address. This is the
board redundancy network address, not the IEC 61850 IP address.
2.
Enter the required board IP address.
3.
Click OK. The board network address is updated and displayed in the main
window.
SNTP IP Address Configuration
To Configure the SNTP server IP address:
5.8.7
1.
From the main window click the SNTP Config button. The Device setup screen
appears.
2.
Enter the required MAC SNTP address and server IP SNTP Address. Click OK.
3.
The updated MAC and IP SNTP addresses appear in the main screen.
Check for Connected Equipment
To check what devices are connected to the device being monitored:
5.8.8
1.
From the main window, select the device.
2.
Click the Equipment button.
3.
At the bottom of the main window, a box shows the ports where devices are
connected and their MAC addresses.
RSTP Configuration
1.
To view or configure the RSTP Bridge Parameters, from the main window, click
the device address to select the device. The selected device MAC address
appears highlighted.
2.
Click the RSTP Config button. The RSTP Config screen appears.
3.
To view the available parameters in the board that is connected, click the Get
RSTP Parameters button.
4.
To set the configurable parameters such as Bridge Max Age, Bridge Hello Time,
Bridge Forward Delay, and Bridge Priority, modify the parameter values
according to the following table and click Set RSTP Parameters.
S.No
SC
5.8.8.1
Default value
(second)
Parameter
Minimum value
(second)
Maximum value
(second)
1
Bridge Max Age
20
6
40
2
Bridge Hello Time
2
1
10
3
Bridge Forward Delay
15
4
30
4
Bridge Priority
32768
0
61440
5
Bridge Max Age
20
6
40
Bridge Parameters
To read the RSTP bridge parameters from the board,
1.
From the main window click the device address to select the device. The RSTP
Config window appears and the default tab is Bridge Parameters.
SCADA Communications
P746/EN SC/J43
MiCOM P40 Agile P746
2.
Click the Get RSTP Parameters button. This displays all the RSTP bridge
parameters from the Ethernet board.
3.
To modify the RSTP parameters, enter the values and click Set RSTP
Parameters.
4.
To restore the default values, click Restore Default and click Set RSTP
Parameters.
5.
The grayed parameters are read-only and cannot be modified.
Note:
5.8.8.2
(SC) 13-27
When assigning the bridge priority, make sure the root of the network is the
Ethernet switch, not the IEDs. This reduces the number of hops to reach all
devices in the network. Also make sure the priority values for all IEDs are
higher than that of the switch.
Port Parameters
This function is useful if you need to view the parameters of each port.
5.8.8.3
1.
From the main window, click the device address to select the device. The RSTP
Config window appears.
2.
Select the Port Parameters tab, then click Get Parameters to read the port
parameters. Alternatively, select the port numbers to read the parameters.
Port States
This is used to see which ports of the board are enabled or disabled.
5.8.9
1.
From the main window, click the device address to select the device. The RSTP
Config window appears.
2.
Select the Port States tab then click the Get Port States button. This lists the
ports of the Ethernet board. A tick shows they are enabled.
End of Session
To finish the session:
1.
In the main window, click the Quit button, a new screen appears.
2.
If a database backup is required, click Yes, a new screen appears.
3.
Click the ... button to browse the path. Enter the name in the text box.
SC
P746/EN SC/J43
SCADA Communications
(SC) 13-28
6
MiCOM P40 Agile P746
SIMPLE NETWORK MANAGEMENT PROTOCOL (SNMP)
Simple Network Management Protocol (SNMP) is a network protocol designed to manage
devices in an IP network. The MiCOM P40 Modular products can provide up to two SNMP
interfaces on Ethernet models; one to the IED’s Main Processor for device level status
information, and another directly to the redundant Ethernet board (where applicable) for
specific Ethernet network level information.
Two versions of SNMP are supported: Version 2c, and a secure implementation of version 3
that includes cyber-security. Only the Main Processor SNMP interface supports Version 3.
6.1
SNMP Management Information Bases
SNMP uses a Management Information Base (MIB), which contains information about
parameters to supervise. The MIB format is a tree structure, with each node in the tree
identified by a numerical Object Identifier (OID). Each OID identifies a variable that can be
read using SNMP with the appropriate software. The information in the MIB is standardized.
Each device in a network (workstation, server, router, bridge, etc.) maintains a MIB that
reflects the status of the managed resources on that system, such as the version of the
software running on the device, the IP address assigned to a port or interface, the amount of
free hard drive space, or the number of open files. The MIB does not contain static data, but
is instead an object-oriented, dynamic database that provides a logical collection of
managed object definitions. The MIB defines the data type of each managed object and
describes the object.
6.2
Main Processor MIBS Structure
The Main Processor MIB uses a private OID with a specific GE number assigned by the
IANA. Some items in this MIB also support SNMP traps (where indicated). These are items
that can automatically notify a host without being read.
Address
Name
0
1
3
6
1
4
1
55461
1
1
1
2
3
4
5
6
7
8
9
10
SC
2
1
2
3
4
5
ROOT NODE
ISO
Org
DOD
Internet
Private
Enterprise
GE-Grid (IANA No)
Px4x
System Data
Description
Plant Reference
Model Number
Serial Number
Frequency
Plant Status
Active Group
Software Ref.1
Software Ref.2
Access Level (UI)
Date and Time
Date Time
IRIG-B Status
Battery Status
Active Sync source
SNTP Server 1
Trigger
Trap?
YES
YES
NO
NO
NO
YES
YES
NO
NO
YES
NO
YES
YES
YES
NO
SCADA Communications
P746/EN SC/J43
MiCOM P40 Agile P746
(SC) 13-29
Address
6
7
8
SNTP Server 2
SNTP Status
PTP Status
System Alarms
Invalid Message Format
Main Protection Fail
Comms Changed
Max Prop. Alarm
9-2 Sample Alarm
9-2LE Cfg Alarm
Battery Fail
Rear Communication Fail
GOOSE IED Missing
Intermicom loopback
Intermicom message fail
Intermicom data CD fail
Intermicom Channel fail
Backup setting fail
User Curve commit to flash
failure
SNTP time Sync fail
PTP failure alarm
Device Mode
IED Mod/Beh
Simulation Mode of Subscription
3
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
4
1
2
6.3
Trigger
Trap?
Name
NO
YES
YES
YES
YES
YES
YES
YES
YES
YES
YES
YES
YES
YES
YES
YES
YES
YES
YES
YES
YES
YES
Redundant Ethernet Board MIB Structure
The Redundant Ethernet board MIB uses three types of OID:
• sysDescr
• sysUpTime
• sysName
MIB structure for RSTP
Address
Name
0
CCITT
ISO
Org
DOD
Internet
mgmt
Mib-2
sys
sysDescr
sysUpTime
sysName
1
3
6
1
2
1
1
1
3
4
Remote Monitoring
16
1
1
1
9
10
12
13
RMON
statistics
etherstat
etherStatsEntry
etherStatsUndersizePkts
etherStatsOversizePkts
etherStatsJabbers
etherStatsCollisions
SC
P746/EN SC/J43
SCADA Communications
(SC) 13-30
MiCOM P40 Agile P746
Address
Name
14
15
16
17
18
etherStatsPkts64Octets
etherStatsPkts65to127Octets
etherStatsPkts128to255Octets
etherStatsPkts256to511Octets
etherStatsPkts512to1023Octets
MIB structure for PRP/HSR
Address
Name
0
1
0
62439
3
1
0
0
1
2
1
0
1
1
SC
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
1
1
0
1
1
2
3
4
5
6
7
8
ITU
ISO
Standard
IECHighavailibility
PRP
linkRedundancyEntityObjects
lreConfiguration
lreConfigurationGeneralGroup
lreManufacturerName
lreInterfaceCount
lreConfigurationInterfaceGroup
lreConfigurationInterfaces
lreInterfaceConfigTable
lreInterfaceConfigEntry
lreInterfaceConfigIndex
lreRowStatus
lreNodeType
lreNodeName
lreVersionName
lreMacAddressA
lreMacAddressB
lreAdapterAdminStateA
lreAdapterAdminStateB
lreLinkStatusA
lreLinkStatusB
lreDuplicateDiscard
lreTransparentReception
lreHsrLREMode
lreSwitchingEndNode
lreRedBoxIdentity
lreSanA
lreSanB
lreEvaluateSupervision
lreNodesTableClear
lreProxyNodeTableClear
lreStatistics
lreStatisticsInterfaceGroup
lreStatisticsInterfaces
lreInterfaceStatsTable
lreInterfaceStatsIndex
lreCntTotalSentA
lreCntTotalSentB
lreCntErrWrongLANA
lreCntErrWrongLANB
lreCntReceivedA
lreCntReceivedB
lreCntErrorsA
SCADA Communications
P746/EN SC/J43
MiCOM P40 Agile P746
(SC) 13-31
Address
Name
9
10
11
12
3
1
1
2
3
6
1
2
1
1
1
3
5
7
2
2
1
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
16
1
1
1
1
2
3
4
5
6
7
8
lreCntErrorsB
lreCntNodes
IreOwnRxCntA
IreOwnRxCntB
lreProxyNodeTable
lreProxyNodeEntry
reProxyNodeIndex
reProxyNodeMacAddress
Org
Dod
Internet
mgmt
mib-2
System
sysDescr
sysUpTime
sysName
sysServices
interfaces
ifTable
ifEntry
ifIndex
ifDescr
ifType
ifMtu
ifSpeed
ifPhysAddress
ifAdminStatus
ifOpenStatus
ifLastChange
ifInOctets
ifInUcastPkts
ifInNUcastPkts
ifInDiscards
ifInErrors
ifInUnknownProtos
ifOutOctets
ifOutUcastPkts
ifOutNUcastPkts
ifOutDiscards
ifOutErrors
ifOutQLen
ifSpecific
rmon
statistics
etherStatsTable
etherStatsEntry
etherStatsIndex
etherStatsDataSource
etherStatsDropEvents
etherStatsOctets
etherStatsPkts
etherStatsBroadcastPkts
etherStatsMulticastPkts
etherStatsCRCAlignErrors
SC
P746/EN SC/J43
SCADA Communications
(SC) 13-32
MiCOM P40 Agile P746
Address
Name
9
10
11
12
13
14
15
16
17
18
19
20
21
6.4
etherStatsUndersizePkts
etherStatsOversizePkts
etherStatsFragments
etherStatsJabbers
etherStatsCollisions
etherStatsPkts64Octets
etherStatsPkts65to127Octets
etherStatsPkts128to255Octets
etherStatsPkts256to511Octets
etherStatsPkts512to1023Octets
etherStatsPkts1024to1518Octets
etherStatsOwner
etherStatsStatus
Accessing the MIB
Various SNMP client software tools can be used. We recommend using an SNMP MIB
browser, which can perform the basic SNMP operations such as GET, GETNEXT and
RESPONSE.
Note:
6.5
There are two IP addresses visible when communicating with the Redundant
Ethernet Card via the fibre optic ports: Use the one for the IED itself to the
Main Processor SNMP interface, and use the one for the on-board Ethernet
switch to access the Redundant Ethernet Board SNMP interface. See the
Firmware Design chapter for more information.
Main Processor SNMP Configuration
Configure the main processor SNMP interface using the HMI panel. Two different versions
are available; SNMPv2c and SNMPv3:
To enable the main processor SNMP interface:
1. Select the COMMUNICATIONS column and scroll to the SNMP PARAMETERS
heading
2. You can select either v2C, V3 or both. Selecting None will disable the main processor
SNMP interface.
SNMP Trap Configuration
SNMP traps allow for unsolicited reporting between the IED and up to two SNMP managers
with unique IP addresses. The device MIB details what information can be reported using
Traps. To configure the SNMP Traps:
1. Move down to the cell Trap Dest. IP 1 and enter the IP address of the first destination
SNMP manager. Setting this cell to 0.0.0.0 disables the first Trap interface.
SC
2. Move down to the cell Trap Dest. IP 2 and enter the IP address of the second
destination SNMP manager. Setting this cell to 0.0.0.0 disables the Second Trap
interface.
SNMP V3 Security Configuration
SNMPv3 provides a higher level of security via authentication and privacy protocols. The IED
adopts a secure SNMPv3 implementation with a user-based security model (USM).
Authentication is used to check the identity of users, privacy allows for encryption of SNMP
messages. Both are optional, however you must enable authentication in order to enable
privacy. To configure these security options:
1. If SNMPv3 has been enabled, set the Security Level setting. There are three levels;
without authentication and without privacy (noAuthNoPriv), with authentication but
without privacy (authNoPriv), and with authentication and with privacy (authPriv).
SCADA Communications
MiCOM P40 Agile P746
P746/EN SC/J43
(SC) 13-33
2. If Authentication is enabled, use the Auth Protocol setting to select the authentication
type. There are two options: HMAC-MD5-96 or HMAC-SHA-96.
3. Using the Auth Password setting, enter the 8-character password to be used by the
IED for authentication.
4. If privacy is enabled, use the Encrypt Protocol setting to set the 8-character
password that will be used by the IED for encryption.
Note:
When setting the SNMP browser for RBAC compatible relays, the Context
Name should be ‘px4x’.
SNMP V2C Security Configuration
SNMPv2c implements authentication between the master and agent using a parameter
called the Community Name. This is effectively the password but it is not encrypted during
transmission (this makes it inappropriate for some scenarios in which case version 3 should
be used instead). To configure the SNMP 2c security:
1. If SNMPv2c has been enabled, use the Community Name setting to set the
password that will be used by the IED and SNMP manager for authentication. This
may be between one and 8 characters.
SC
P746/EN SC/J43
SCADA Communications
(SC) 13-34
7
MiCOM P40 Agile P746
DATA PROTOCOLS
The products supports a wide range of protocols to make them applicable to many industries
and applications. The exact data protocols supported by a particular product depend on its
chosen application, but the following table gives a list of the data protocols that are typically
available.
SCADA data protocols
Data Protocol
Layer 1 protocol
Description
Courier
USB, K-Bus, RS232, RS485,
Ethernet
Standard for SCADA communications developed
by GE.
MODBUS
RS485
Standard for SCADA communications developed
by Modicon.
IEC 60870-5-103 RS485
IEC standard for SCADA communications
DNP 3.0
RS485
Standard for SCADA communications.
IEC 61850
Ethernet
IEC standard for substation automation. Facilitates
interoperability.
The relationship of these protocols to the lower level physical layer protocols are as follows:
IEC 60870-5-103
Data Protocols
Data Link Layer
MODBUS
DNP3.0
IEC 61850
Courier
Courier
Courier
Courier
Courier
EIA(RS)485
Ethernet
EIA(RS)232
K-Bus
USB
Physical Layer
7.1
Copper or Optical Fibre
USB Type B
Courier
This section should provide sufficient detail to enable understanding of the Courier protocol
at a level required by most users. For situations where the level of information contained in
this manual is insufficient, further publications (R6511 and R6512) containing in-depth details
about the protocol and its use, are available on request.
Courier is an GE proprietary communication protocol. Courier uses a standard set of
commands to access a database of settings and data in the IED. This allows a master to
communicate with a number of slave devices. The application-specific elements are
contained in the database rather than in the commands used to interrogate it, meaning that
the master station does not need to be preconfigured. Courier also provides a sequence of
event (SOE) and disturbance record extraction mechanism.
7.1.1
SC
Physical Connection and Link Layer
Courier can be used with four physical layer protocols: USB, K-Bus, EIA(RS)232 or
EIA(RS)485.
Several connection options are available for Courier
• The front USB port (for connection to Settings application software on, for example, a
laptop
• Rear Port 1 (RP1) - for permanent SCADA connection via RS485 or K-Bus
• Optional fibre port (RP1 in slot A) - for permanent SCADA connection via optical fibre
• Optional Rear Port 2 (RP2) - for permanent SCADA connection via RS485, K-Bus, or
RS232
For either of the rear ports, both the IED address and baud rate can be selected using the
front panel menu or by the settings application software.
SCADA Communications
P746/EN SC/J43
MiCOM P40 Agile P746
7.1.2
(SC) 13-35
Courier Database
The Courier database is two-dimensional and resembles a table. Each cell in the database is
referenced by a row and column address. Both the column and the row can take a range
from 0 to 255 (0000 to FFFF Hexadecimal. Addresses in the database are specified as
hexadecimal values, for example, 0A02 is column 0A row 02. Associated settings or data are
part of the same column. Row zero of the column has a text string to identify the contents of
the column and to act as a column heading.
The product-specific menu databases contain the complete database definition.
7.1.3
Setting Categories
There are two main categories of settings in protection IEDs:
• Control and support settings
• Protection settings
With the exception of the Disturbance Recorder settings, changes made to the control and
support settings are implemented immediately and stored in non-volatile memory. Changes
made to the Protection settings and the Disturbance Recorder settings are stored in
‘scratchpad’ memory and are not immediately implemented. These need to be committed by
writing to the Save Changes cell in the CONFIGURATION column.
7.1.4
Setting Changes
Courier provides two mechanisms for making setting changes. Either method can be used
for editing any of the settings in the database.
Method 1
This uses a combination of three commands to perform a settings change:
First, enter Setting mode: This checks that the cell is settable and returns the limits.
• Preload Setting: This places a new value into the cell. This value is echoed to ensure
that setting corruption has not taken place. The validity of the setting is not checked by
this action.
• Execute Setting: This confirms the setting change. If the change is valid, a positive
response is returned. If the setting change fails, an error response is returned.
• Abort Setting: This command can be used to abandon the setting change.
This is the most secure method. It is ideally suited to on-line editors because the setting
limits are extracted before the setting change is made. However, this method can be slow if
many settings are being changed because three commands are required for each change.
Method 2
The Set Value command can be used to directly change a setting. The response to this
command is either a positive confirm or an error code to indicate the nature of a failure. This
command can be used to implement a setting more rapidly than the previous method,
however the limits are not extracted from the relay. This method is therefore most suitable
for off-line setting editors such as MiCOM S1 Agile, or for issuing pre-configured control
commands.
7.1.5
Event Extraction
You can extract events either automatically (rear serial port only) or manually (either serial
port). For automatic extraction, all events are extracted in sequential order using the Courier
event mechanism. This includes fault and maintenance data if appropriate. The manual
approach allows you to select events, faults, or maintenance data as desired.
7.1.5.1
Automatic Event Extraction
This method is intended for continuous extraction of event and fault information as it is
produced. It is only supported through the rear Courier port.
SC
P746/EN SC/J43
(SC) 13-36
SCADA Communications
MiCOM P40 Agile P746
When new event information is created, the Event bit is set in the Status byte. This indicates
to the Master device that event information is available. The oldest, non-extracted event can
be extracted from the IED using the Send Event command. The IED responds with the
event data.
Once an event has been extracted, the Accept Event command can be used to confirm that
the event has been successfully extracted. When all events have been extracted, the Event
bit is reset. If there are more events still to be extracted, the next event can be accessed
using the Send Event command as before.
7.1.5.2
Manual Event Record Extraction
The VIEW RECORDS column (location 01) is used for manual viewing of event, fault, and
maintenance records. The contents of this column depend on the nature of the record
selected. You can select events by event number and directly select a fault or maintenance
record by number.
EVENT RECORD SELECTION ('SELECT EVENT' CELL: 0101)
This cell can set the number of stored events. For simple event records (Type 0), cells 0102
to 0105 contain the event details. A single cell is used to represent each of the event fields. If
the event selected is a fault or maintenance record (Type 3), the remainder of the column
contains the additional information.
FAULT RECORD SELECTION ('SELECT FAULT' CELL: 0105)
This cell can be used to select a fault record directly, using a value between 0 and 4 to select
one of up to five stored fault records. (0 is the most recent fault and 4 is the oldest). The
column then contains the details of the fault record selected.
MAINTENANCE RECORD SELECTION ('SELECT MAINT' CELL: 01F0)
This cell can be used to select a maintenance record using a value between 0 and 4. This
cell operates in a similar way to the fault record selection.
If this column is used to extract event information, the number associated with a particular
record changes when a new event or fault occurs.
Event types
Events will be created by the relay under the following circumstances:
• Change of state of output contact
• Change of state of opto input
• Protection element operation
• Alarm condition
• Setting change
• Password entered/timed-out
• Fault record (Type 3 Courier Event)
SC
• Maintenance record (Type 3 Courier Event)
Event record format
The IED returns the following fields when the Send Event command is invoked:
• Cell reference
• Time stamp
• Cell text
• Cell value
SCADA Communications
MiCOM P40 Agile P746
P746/EN SC/J43
(SC) 13-37
The Menu Database contains tables of possible events, and shows how the contents of the
above fields are interpreted. Fault and Maintenance records return a Courier Type 3 event,
which contains the above fields plus two additional fields:
• Event extraction column
• Event number
These events contain additional information, which is extracted from the IED using column
B4. Row 01 contains a Select Record setting that allows the fault or maintenance record to
be selected. This setting should be set to the event number value returned in the record. The
extended data can be extracted from the IED by uploading the text and data from the
column.
7.1.6
Disturbance Record Extraction
The stored disturbance records are accessible through the Courier interface. The records
are extracted using column (B4).
The Select Record cell can be used to select the record to be extracted. Record 0 is the
oldest non-extracted record. Older records which have been already been extracted are
assigned positive values, while younger records are assigned negative values. To help
automatic extraction through the rear port, the IED sets the Disturbance bit of the Status
byte, whenever there are non-extracted disturbance records.
Once a record has been selected, using the above cell, the time and date of the record can
be read from the Trigger Time cell (B402). The disturbance record can be extracted using
the block transfer mechanism from cell B40B and saved in the COMTRADE format. The
settings application software software automatically does this.
7.1.7
Programmable Scheme Logic Settings
The programmable scheme logic (PSL) settings can be uploaded from and downloaded to
the relay using the block transfer mechanism.
The following cells are used to perform the extraction:
• Domain cell (B204): Used to select either PSL settings (upload or download) or PSL
configuration data (upload only)
• Sub-Domain cell (B208): Used to select the Protection Setting Group to be uploaded
or downloaded.
• Version cell (B20C): Used on a download to check the compatibility of the file to be
downloaded.
• Transfer Mode cell (B21C): Used to set up the transfer process.
• Data Transfer cell (B120): Used to perform upload or download.
The PSL settings can be uploaded and downloaded to and from the IED using this
mechanism. The settings application software must be used to edit the settings. It also
performs checks on the validity of the settings before they are transferred to the IED.
7.1.8
Time Synchronisation
The time and date can be set using the time synchronization feature of the Courier protocol.
The device will correct for the transmission delay. The time synchronization message may
be sent as either a global command or to any individual IED address. If the time
synchronization message is sent to an individual address, then the device will respond with a
confirm message. If sent as a global command, the (same) command must be sent twice. A
time synchronization Courier event will be generated/produced whether the timesynchronization message is sent as a global command or to any individual IED address.
If the clock is being synchronized using the IRIG-B input then it will not be possible to set the
device time using the Courier interface. An attempt to set the time using the interface will
cause the device to create an event with the current date and time taken from the IRIG-B
synchronized internal clock.
SC
P746/EN SC/J43
SCADA Communications
(SC) 13-38
7.1.9
MiCOM P40 Agile P746
Courier Configuration
To configure the device:
1. Select the CONFIGURATION column and check that the Comms settings cell is set
to Visible.
2. Select the COMMUNICATIONS column.
3. Move to the first cell down (RP1 protocol). This is a non-settable cell, which shows
the chosen communication protocol – in this case Courier.
RP1 Protocol
Courier
4. Move down to the next cell (RP1 Address). This cell controls the address of the RP1
port on the device. Up to 32 relays can be connected to one spur. It is therefore
necessary for each relay to have a unique address so that messages from the master
control station are accepted by one relay only. Courier uses an integer number
between 1 and 254 for the Relay Address. It is set to 255 by default, which has to be
changed. It is important that no two relays share the same address.
RP1 Address
1
5. Move down to the next cell (RP1 InactivTimer). This cell controls the inactivity timer.
The inactivity timer controls how long the relay waits without receiving any messages
on the rear port before revoking any password access that was enabled and
discarding any changes. For the rear port this can be set between 1 and 30 minutes.
RP1 Inactiv timer
10.00 mins.
6. If the optional fibre optic connectors are fitted, the RP1 PhysicalLink cell is visible.
This cell controls the physical media used for the communication (Copper or Fibre
optic).
SC
RP1 Physical link
Copper
7. Move down to the next cell (RP1 Card Status). This cell is not settable. It displays the
status of the chosen physical layer protocol for RP1
RP1 Card status
K-Bus OK
SCADA Communications
P746/EN SC/J43
MiCOM P40 Agile P746
(SC) 13-39
8. Move down to the next cell (RP1 Port Config). This cell controls the type of serial
connection. Select between K-Bus or RS485.
RP1 Port config.
K-Bus
9. If using EIA(RS)485, the next cell (RP1 Comms Mode) selects the communication
mode. The choice is either IEC 60870 FT1.2 for normal operation with 11-bit modems,
or 10-bit no parity. If using K-Bus this cell will not appear.
RP1 Comms. Mode
IEC 60870 FT1.2
10. If using EIA(RS)485, the next cell down controls the baud rate. Three baud rates are
supported; 9600, 19200 and 38400. If using K-Bus this cell will not appear as the baud
rate is fixed at 64 kbps.
RP1 Baud rate
19200
7.2
IEC 60870-5-103
The specification IEC 60870-5-103 (Telecontrol Equipment and Systems Part 5 Section 103:
Transmission Protocols), defines the use of standards IEC 60870-5-1 to IEC 60870-5-5,
which were designed for communication with protection equipment
This section describes how the IEC 60870-5-103 standard is applied to the Px40 platform. It
is not a description of the standard itself. The level at which this section is written assumes
that the reader is already familiar with the IEC 60870-5-103 standard.
This section should provide sufficient detail to enable understanding of the standard at a
level required by most users.
The IEC 60870-5-103 interface is a master/slave interface with the device as the slave
device. The device conforms to compatibility level 2, as defined in the IEC 60870-5103.standard.
The following IEC 60870-5-103 facilities are supported by this interface:
• Initialization (reset)
• Time synchronization
• Event record extraction
• General interrogation
• Cyclic measurements
• General commands
• Disturbance record extraction
• Private codes
7.3
Physical Connection and Link Layer
Two connection options are available for IEC 60870-5-103:
SC
P746/EN SC/J43
(SC) 13-40
SCADA Communications
MiCOM P40 Agile P746
• Rear Port 1 (RP1) - for permanent SCADA connection via RS485
• Optional fibre port (RP1 in slot A) - for permanent SCADA connection via optical fibre
If the optional fibre optic port is fitted, a menu item appears in which the active port can be
selected. However the selection is only effective following the next power up.
The relay address and baud rate can be selected using the front panel menu or by the
settings application software.
7.3.1
Initialisation
Whenever the device has been powered up, or if the communication parameters have been
changed a reset command is required to initialize the communications. The device will
respond to either of the two reset commands; Reset CU or Reset FCB (Communication Unit
or Frame Count Bit). The difference between the two commands is that the Reset CU
command will clear any unsent messages in the transmit buffer, whereas the Reset FCB
command does not delete any messages.
The device will respond to the reset command with an identification message ASDU 5. The
Cause of Transmission (COT) of this response will be either Reset CU or Reset FCB
depending on the nature of the reset command. The content of ASDU 5 is described in the
IEC 60870-5-103 section of the Menu Database, available from GE separately if required.
In addition to the above identification message, it will also produce a power up event.
7.3.2
Time Synchronisation
The time and date can be set using the time synchronization feature of the IEC 60870-5-103
protocol. The device will correct for the transmission delay as specified in IEC 60870-5-103.
If the time synchronization message is sent as a send/confirm message then the device will
respond with a confirm message. A time synchronization Class 1 event will be
generated/produced whether the time-synchronization message is sent as a send confirm or
a broadcast (send/no reply) message.
If the clock is being synchronized using the IRIG-B input then it will not be possible to set the
device time using the IEC 60870-5-103 interface. An attempt to set the time via the interface
will cause the device to create an event with the current date and time taken from the IRIG-B
synchronized internal clock.
7.3.3
Spontaneous Events
Events are categorized using the following information:
• Function type
• Information Number
7.3.4
General Interrogation (GI)
The GI request can be used to read the status of the device, the function numbers, and
information numbers that will be returned during the GI cycle. These are shown in the IEC
60870-5-103 profile in the Menu Database.
SC
7.3.5
Cyclic Measurements
The device will produce measured values using ASDU 9 on a cyclical basis, this can be read
from the device using a Class 2 poll (note ADSU 3 is not used). The rate at which the device
produces new measured values can be controlled using the measurement period setting.
This setting can be edited from the front panel menu or using MiCOM S1 Agile. It is active
immediately following a change.
The device transmits its measurands at 2.4 times the rated value of the analogue value.
7.3.6
Commands
A list of the supported commands is contained in the Menu Database. The device will
respond to other commands with an ASDU 1, with a cause of transmission (COT) indicating
‘negative acknowledgement’.
SCADA Communications
P746/EN SC/J43
MiCOM P40 Agile P746
7.3.7
(SC) 13-41
Test Mode
It is possible to disable the device output contacts to allow secondary injection testing to be
performed using either the front panel menu or the front serial port. The IEC 60870-5-103
standard interprets this as ‘test mode’. An event will be produced to indicate both entry to
and exit from test mode. Spontaneous events and cyclic measured data transmitted whilst
the device is in test mode will have a COT of ‘test mode’.
7.3.8
Disturbance Records
The disturbance records are stored in uncompressed format and can be extracted using the
standard mechanisms described in IEC 60870-5-103.
Note: IEC 60870-5-103 only supports up to 8 records.
7.3.9
Command/Monitor Blocking
The device supports a facility to block messages in the monitor direction (data from the
device) and also in the command direction (data to the device). Messages can be blocked in
the monitor and command directions using one of the two following methods
• The menu command RP1 CS103Blcking in the COMMUNICATIONS column
• The DDB signals Monitor Blocked and Command Blocked
7.3.10
IEC 60870-5-103 Configuration
To configure the device:
1. Select the CONFIGURATION column and check that the Comms settings cell is set
to Visible.
2. Select the COMMUNICATIONS column.
3. Move to the first cell down (RP1 protocol). This is a non-settable cell, which shows
the chosen communication protocol – in this case IEC 60870-5-103.
RP1 Protocol
IEC 60870-5-103r
4. Move down to the next cell (RP1 Address). This cell controls the IEC 60870-5-103
address of the relay. Up to 32 relays can be connected to one spur. It is therefore
necessary for each relay to have a unique address so that messages from the master
control station are accepted by one relay only. IEC 60870-5-103 uses an integer
number between 0 and 254 for the address. It is important that no two relays have the
same IEC 60870 5 103 address. The IEC 60870-5-103 address is then used by the
master station to communicate with the relay.
RP1 address
162
5. Move down to the next cell (RP1 Baud Rate). This cell controls the baud rate to be
used. Two baud rates are supported by the relay, 9600 bits/s and 19200 bits/s. Make
sure that the baud rate selected on the relay is the same as that set on the master
station
RP1 Baud rate
9600 bits/s
SC
P746/EN SC/J43
SCADA Communications
(SC) 13-42
MiCOM P40 Agile P746
6. Move down to the next cell (RP1 Meas Period). The next cell down controls the
period between IEC 60870-5-103 measurements. The IEC 60870-5-103 protocol
allows the relay to supply measurements at regular intervals. The interval between
measurements is controlled by this cell, and can be set between 1 and 60 seconds.
RP1 Meas Period
30.00 s
7. If the optional fibre optic connectors are fitted, the RP1 PhysicalLink cell is visible.
This cell controls the physical media used for the communication (Copper or Fibre
optic).
RP1 Physical link
Copper
.
8. The next cell down (RP1 CS103Blcking) can be used for monitor or command
blocking.
RP1 CS103Blcking
Disabled
9. There are three settings associated with this cell; these are:
Setting
Disabled
Description
No blocking selected.
When the monitor blocking DDB Signal is active high, either by energising an opto
input or control input, reading of the status information and disturbance records is
Monitor Blocking
not permitted. When in this mode the device returns a "Termination of general
interrogation" message to the master station.
Command
Blocking
SC
7.4
When the command blocking DDB signal is active high, either by energising an
opto input or control input, all remote commands will be ignored (i.e. CB Trip/Close,
change setting group etc.). When in this mode the device returns a "negative
acknowledgement of command" message to the master station.
DNP3.0
This section describes how the DNP 3.0 standard is applied in the product. It is not a
description of the standard itself. The level at which this section is written assumes that the
reader is already familiar with the DNP 3.0 standard.
The descriptions given here are intended to accompany the device profile document that is
included in the Menu Database document. The DNP 3.0 protocol is not described here,
please refer to the documentation available from the user group. The device profile
document specifies the full details of the DNP 3.0 implementation. This is the standard
format DNP 3.0 document that specifies which objects; variations and qualifiers are
supported. The device profile document also specifies what data is available from the device
using DNP 3.0. The IED operates as a DNP 3.0 slave and supports subset level 2, as
described in the DNP 3.0 standard, plus some of the features from level 3.
SCADA Communications
MiCOM P40 Agile P746
P746/EN SC/J43
(SC) 13-43
The DNP 3.0 protocol is defined and administered by the DNP Users Group. For further
information on DNP 3.0 and the protocol specifications, please see the DNP website
(www.dnp.org).
7.4.1
Physical Connection and Link Layer
DNP 3.0 can be used with EIA(RS)485.
Several connection options are available for DNP 3.0
• Rear Port 1 (RP1) - for permanent SCADA connection via RS485
• Optional fibre port (RP1 in slot A) - for permanent SCADA connection via optical fibre
The baud rate can be selected using the front panel menu or by the settings application
software.
When using a serial interface, the data format is: 1 start bit, 8 data bits, 1 stop bit and
optional configurable parity bit.
7.4.2
Object 1 Binary Inputs
Object 1, binary inputs, contains information describing the state of signals in the relay which
mostly form part of the digital data bus (DDB). In general these include the state of the
output contacts and input optos, alarm signals and protection start and trip signals. The ‘DDB
number’ column in the device profile document provides the DDB numbers for the DNP3.0
point data. These can be used to cross-reference to the DDB definition list that is also found
in the menu database. The binary input points can also be read as change events via object
2 and object 60 for class 1-3 event data.
7.4.3
Object 10 Binary Outputs
Object 10, binary outputs, contains commands that can be operated via DNP3.0. As such
the points accept commands of type pulse on [null, trip, close] and latch on/off as detailed in
the device profile in the menu database and execute the command once for either
command. The other fields are ignored (queue, clear, trip/close, in time and off time).
There is an additional image of the Control Inputs. Described as Alias Control Inputs, they
reflect the state of the Control Input, but with a dynamic nature.
• If the Control Input DDB signal is already SET and a new DNP SET command is sent
to the Control Input, the Control Input DDB signal goes momentarily to RESET and
then back to SET.
• If the Control Input DDB signal is already RESET and a new DNP RESET command is
sent to the Control Input, the Control Input DDB signal goes momentarily to SET and
then back to RESET.
SC
P746/EN SC/J43
SCADA Communications
(SC) 13-44
MiCOM P40 Agile P746
DNP Latch
ON
DNP Latch
ON
DNP Latch
OFF
DNP Latch
OFF
Control Input
(Latched)
Aliased Control
Input
(Latched)
Control Input
(Pulsed)
Aliased Control
Input
(Pulsed)
The pulse width is equal to the duration of one protection iteration
V01002
Figure 11: Control input behaviour
Many of the relay’s functions are configurable so some of the object 10 commands described
in the following sections may not be available. A read from object 10 reports as off-line and
an operate command to object 12 generates an error response.
Examples of object 10 points that maybe reported as off-line are:
• Activate setting groups: Ensure setting groups are enabled
• CB trip/close: Ensure remote CB control is enabled
• Reset NPS thermal: Ensure NPS thermal protection is enabled
• Reset thermal O/L: Ensure thermal overload protection is enabled
• Reset RTD flags: Ensure RTD Inputs is enabled
• Control Inputs: Ensure control inputs are enabled
7.4.4
Object 20 Binary Counters
Object 20, binary counters, contains cumulative counters and measurements. The binary
counters can be read as their present ‘running’ value from object 20, or as a ‘frozen’ value
from object 21. The running counters of object 20 accept the read, freeze and clear
functions. The freeze function takes the current value of the object 20 running counter and
stores it in the corresponding object 21 frozen counter. The freeze and clear function resets
the object 20 running counter to zero after freezing its value.
SC
Binary counter and frozen counter change event values are available for reporting from
Object 22 and Object 23 respectively. Counter change events (Object 22) only report the
most recent change, so the maximum number of events supported is the same as the total
number of counters. Frozen counter change events (Object 23) are generated whenever a
freeze operation is performed and a change has occurred since the previous freeze
command. The frozen counter event queues store the points for up to two freeze operations.
7.4.5
Object 30 Analog Input
Object 30, analogue inputs, contains information from the IED’s measurements columns in
the menu. All object 30 points can be reported as 16 or 32-bit integer values with flag, 16 or
32-bit integer values without flag, as well as short floating point values.
SCADA Communications
P746/EN SC/J43
MiCOM P40 Agile P746
(SC) 13-45
Analogue values can be reported to the master station as primary, secondary or normalized
values (which takes into account the relay’s CT and VT ratios), and this is settable in the
COMMUNICATIONS column in the relay.
Corresponding deadband settings can be displayed in terms of a primary, secondary or
normalized value. Deadband point values can be reported and written using Object 34
variations.
The deadband is the setting used to determine whether a change event should be generated
for each point. The change events can be read using Object 32 or Object 60. These events
are generated for any point which has a value changed by more than the deadband setting
since the last time the data value was reported.
Any analogue measurement that is unavailable when it is read is reported as offline. For
example, the frequency would be offline if the current and voltage frequency is outside the
tracking range of the relay. All Object 30 points are reported as secondary values in DNP 3.0
(with respect to CT and VT ratios).
7.4.6
Object 40 Analogue Output
The conversion to fixed-point format requires the use of a scaling factor, which is
configurable for the various types of data within the relay such as current, voltage, and
phase angle. All Object 40 points report the integer scaling values and Object 41 is available
to configure integer scaling quantities.
7.4.7
Object 50 Time Synchronisation
Function codes 1 (read) and 2 (write) are supported for Object 50 (time and date) variation 1.
The DNP Need Time function (the duration of time waited before requesting another time
sync from the master) is supported, and is configurable in the range 1 - 30 minutes.
If the clock is being synchronized using the IRIG-B input then it will not be possible to set the
device time using the Courier interface. An attempt to set the time using the interface will
cause the device to create an event with the current date and time taken from the IRIG-B
synchronized internal clock.
7.4.8
DNP3 Device Profile
This section describes the specific implementation of DNP version 3.0 within GE MiCOM
P40 Agile relays for both compact and modular ranges.
The devices use the DNP 3.0 Slave Source Code Library version 3 from Triangle
MicroWorks Inc.
This document, in conjunction with the DNP 3.0 Basic 4 Document Set, and the DNP Subset
Definitions Document, provides complete information on how to communicate with the
devices using the DNP 3.0 protocol.
This implementation of DNP 3.0 is fully compliant with DNP 3.0 Subset Definition Level 2. It
also contains many Subset Level 3 and above features.
7.4.8.1
DNP3 Device Profile Table
The following table provides the device profile in a similar format to that defined in the DNP
3.0 Subset Definitions Document. While it is referred to in the DNP 3.0 Subset Definitions as
a “Document”, it is just one component of a total interoperability guide. This table, in
combination with the subsequent Implementation and Points List tables should provide a
complete interoperability/configuration guide for the device.
The following table provides the device profile in a similar format to that defined in the DNP
3.0 Subset Definitions Document. While it is referred to in the DNP 3.0 Subset Definitions as
a "Document", it is just one component of a total interoperability guide. This table, in
combination with the subsequent Implementation and Points List tables should provide a
complete interoperability/configuration guide for the device.
DNP 3.0
Device Profile Document
Vendor Name:
GE
SC
P746/EN SC/J43
SCADA Communications
(SC) 13-46
MiCOM P40 Agile P746
DNP 3.0
Device Profile Document
Device Name:
SC
MiCOM P40Agile Protection Relays – compact and
modular range
All models
Models Covered:
Highest DNP Level Supported*:
For Requests:
Level 2
*This is the highest DNP level FULLY supported. Parts of level 3
For Responses:
Level 2
are also supported
Device Function:
Slave
Notable objects, functions, and/or qualifiers supported in addition to the highest DNP levels supported (the complete list
is described in the DNP 3.0 Implementation Table):
For static (non-change event) object requests, request qualifier codes 00 and 01 (start-stop), 07 and 08 (limited quantity),
and 17 and 28 (index) are supported in addition to the request qualifier code 06 (no range (all points))
Static object requests sent with qualifiers 00, 01, 06, 07, or 08 will be responded with qualifiers 00 or 01
Static object requests sent with qualifiers 17 or 28 will be responded with qualifiers 17 or 28
For change-event object requests, qualifiers 17 or 28 are always responded
16-bit and 32-bit analogue change events with time may be requested
The read function code for Object 50 (time and date) variation 1 is supported
Analogue Input Deadbands, Object 34, variations 1 through 3, are supported
Floating Point Analogue Output Status and Output Block Objects 40 and 41 are supported
Sequential file transfer, Object 70, variations 2 through 7, are supported
Device Attribute Object 0 is supported
Transmitted: 292
Maximum Data Link Frame Size (octets):
Received: 292
Maximum Application Fragment Size (octets)
Transmitted: Configurable (100 to 2048). Default 2048
Received: 249
Maximum Data Link Retries:
Fixed at 2
Maximum Application Layer Retries:
None
Requires Data Link Layer Confirmation:
Configurable to Never or Always
When reporting event data (Slave devices only)
Requires Application Layer Confirmation:
When sending multi-fragment responses (Slave
devices only)
Timeouts while waiting for:
Data Link Confirm:
Configurable
Complete Application Fragment:
None
Application Confirm:
Configurable
Complete Application Response:
None
Others:
Data Link Confirm Timeout:
Configurable from 0 (Disabled) to 120s, default 10s.
Application Confirm Timeout:
Configurable from 1 to 120s, default 2s.
Select/Operate Arm Timeout:
Configurable from 1 to 10s, default 10s.
Need Time Interval (Set IIN1-4):
Configurable from 1 to 30, default 10min.
Application File Timeout
60 s
Analog Change Event Scan Period:
Fixed at 0.5s
Counter Change Event Scan Period
Fixed at 0.5s
Frozen Counter Change Event Scan Period
Fixed at 1s
Maximum Delay Measurement Error:
2.5 ms
Time Base Drift Over a 10-minute Interval:
7 ms
Sends/Executes Control Operations:
Write Binary Outputs:
Never
Select/Operate:
Always
Direct Operate:
Always
Direct Operate - No Ack:
Always
Count > 1
Never
Pulse On
Always
Pulse Off
Sometimes
Latch On
Always
SCADA Communications
P746/EN SC/J43
MiCOM P40 Agile P746
(SC) 13-47
DNP 3.0
Device Profile Document
Latch Off
Always
Queue
Never
Clear Queue
Never
Note:
Paired Control points will accept Pulse On/Trip and Pulse On/Close, but only single point will accept the Pulse
Off control command.
Reports Binary Input Change Events when no specific variation
Configurable to send one or the other
requested:
Reports time-tagged Binary Input Change Events when no
Binary input change with time
specific variation requested:
Sends Unsolicited Responses:
Never
Never
Sends Static Data in Unsolicited Responses:
No other options are permitted
Configurable, Point-by-point list attached
Default Counter Object/Variation:
Default object:
20
Default variation: 1
Counters Roll Over at:
32 bits
Sends multi-fragment responses:
Yes
Sequential File Transfer Support:
Append File Mode
No
Custom Status Code Strings
No
Permissions Field
Yes
File Events Assigned to Class
No
File Events Send Immediately
Yes
Multiple Blocks in a Fragment
No
Max Number of Files Open
1
7.4.8.2
DNP3 Implementation Table
The implementation table provides a list of objects, variations and control codes supported
by the device:
Object
Object
Number
Request
Response
(Library will parse)
(Library will respond with)
Variation
Number
Description
Function Codes (dec)
1
0
Binary Input
(Variation 0 is
used to request
default
variation)
1
22
1
1
Binary Input
(default see note 1)
1
2
Binary Input
with Flag
1
1
(read)
(assign class)
(read)
(read)
Qualifier Codes
(hex)
00,
(start01
stop)
06
(no
range, or
07,
all)
08
(limited
17,
qty)
27,
28
(index)
00,
(start01
stop)
06
(no
range, or
07,
all)
08
(limited
17,
qty)
27,
28
(index)
(start00,
stop)
01
(no
06
range, or
07,
all)
08
(limited
17,
qty)
28
(index)
Function Codes
(dec)
Qualifier Codes
(hex)
129
response
00,
01
17,
28
(startstop)
(index see note
2)
response
00,
01
17,
28
(startstop)
(index see note
2)
129
SC
P746/EN SC/J43
SCADA Communications
(SC) 13-48
MiCOM P40 Agile P746
Object
Request
Response
(Library will parse)
(Library will respond with)
1
(read)
06
07,
08
2
0
Binary Input
Change - Any
Variation
2
1
Binary Input
Change without
Time
1
(read)
06
07,
08
Binary Input
Change with
Time
1
(read)
06
07,
08
(read)
00,
01
06
07,
08
17,
27,
28
2
10
2
0
Binary Output
Status - Any
Variation
1
10
2
Binary Output
(default Status
see note 1)
1
(read)
00,
01
06
07,
08
17,
28
12
Control Relay
Output Block
3
4
5
6
(select)
(operate)
(direct op)
(dir. op, noack)
17,
28
20
1
0
Binary Counter - 1
Any Variation
22
7
8
9
10
SC
20
1
32-Bit Binary
Counter with
Flag
1
(index)
129
(freeze)
(freeze noack)
(freeze clear)
(frz. cl. Noack)
00,
01
06
07,
08
(startstop)
(no
range, or
all)
(limited
qty)
(index)
(startstop)
(no
range, or
all)
(limited
qty)
(read)
00,
01
06
07,
08
17,
27,
28
(startstop)
(no
range, or
129
all)
(limited
qty)
(index)
(read)
(assign class)
00,
01
06
07,
08
17,
27,
28
(no
range, or
all)
(limited
qty)
(no
range, or
all)
129
(limited
qty)
(no
range, or
all)
129
(limited
qty)
(startstop)
(no
range, or
all)
(limited
qty)
(index)
(startstop)
(no
range, or
129
all)
(limited
qty)
(index)
response
17,
28
(index)
response
17,
28
(index)
response
00,
01
17,
28
(startstop)
(index see note
2)
echo of
request
response
response
00,
01
17,
28
(startstop)
(index see note
2)
SCADA Communications
P746/EN SC/J43
MiCOM P40 Agile P746
(SC) 13-49
Object
16-Bit Binary
Counter with
Flag
Response
(Library will respond with)
20
2
20
5
32-Bit Binary
Counter without 1
(default see note 1) Flag
20
6
16-Bit Binary
Counter without 1
Flag
(read)
21
0
Frozen Counter 1
Any Variation
(read)
1
32-Bit Frozen
Counter with
Flag
2
16-Bit Frozen
Counter with
Flag
21
21
21
5
32-Bit Frozen
Counter with
Time of Freeze
1
Request
(Library will parse)
1
1
1
(read)
(read)
(read)
(read)
(read)
00,
01
06
07,
08
17,
27,
28
00,
01
06
07,
08
17,
27,
28
00,
01
06
07,
08
17,
27,
28
00,
01
06
07,
08
17,
27,
28
00,
01
06
07,
08
17,
27,
28
00,
01
06
07,
08
17,
27,
28
00,
01
06
07,
08
17,
27,
28
(startstop)
(no
range, or
all)
(limited
qty)
(index)
(startstop)
(no
range, or
all)
(limited
qty)
(index)
(startstop)
(no
range, or
all)
(limited
qty)
(index)
(startstop)
(no
range, or
all)
(limited
qty)
(index)
(startstop)
(no
range, or
all)
(limited
qty)
(index)
(startstop)
(no
range, or
all)
(limited
qty)
(index)
(startstop)
(no
range, or
all)
(limited
qty)
(index)
129
129
129
129
129
129
response
00,
01
17,
28
(startstop)
(index see note
2)
response
00,
01
17,
28
(startstop)
(index see note
2)
response
00,
01
17,
28
(startstop)
(index see note
2)
response
00,
01
17,
28
(startstop)
(index see note
2)
response
00,
01
17,
28
(startstop)
(index see note
2)
response
00,
01
17,
28
(startstop)
(index see note
1)
SC
P746/EN SC/J43
SCADA Communications
(SC) 13-50
MiCOM P40 Agile P746
Object
21
16-Bit Frozen
Counter with
Time of Freeze
1
Response
(Library will respond with)
(read)
00,
01
06
07,
08
17,
27,
28
00,
01
06
07,
08
17,
27,
28
00,
01
06
07,
08
17,
27,
28
21
9
32-Bit Frozen
Counter without 1
(default see note 1) Flag
21
10
16-Bit Frozen
Counter without 1
Flag
(read)
`22
0
Counter Change
Event - Any
1
Variation
(read)
06
07,
08
22
1
32-Bit Counter
Change Event
(default see note 1) without Time
1
(read)
06
07,
08
16-Bit Counter
Change Event
without Time
1
(read)
06
07,
08
22
SC
6
Request
(Library will parse)
2
(read)
22
5
32-Bit Counter
Change Event
with Time
1
(read)
06
07,
08
22
6
16-Bit Counter
Change Event
with Time
1
(read)
06
07,
08
23
0
Frozen Counter
Event (Variation
0 is used to
request default
variation)
1
(read)
06
07,
08
23
1
32-Bit Frozen
(default Counter Event
see note 1)
1
(read)
06
07,
08
(startstop)
(no
range, or
all)
(limited
qty)
(index)
(startstop)
(no
range, or
all)
(limited
qty)
(index)
(startstop)
(no
range, or
all)
(limited
qty)
(index)
(no
range, or
all)
(limited
qty)
(no
range, or
all)
(limited
qty)
(no
range, or
all)
(limited
qty)
(no
range, or
all)
(limited
qty)
(no
range, or
all)
(limited
qty)
(no
range, or
all)
(limited
qty)
(no
range, or
all)
(limited
qty)
(startstop)
17, 28
(index see note
1)
response
00,
01
17,
28
response
00,
01
17,
28
(startstop)
(index see note
2)
129
response
00,
01
17,
28
(startstop)
(index see note
2)
129
response
17,
28
(index)
129
response
17,
28
(index)
129
response
17,
28
(index)
129
response
17,
28
(index)
129
response
17,
28
(index)
129
129
SCADA Communications
P746/EN SC/J43
MiCOM P40 Agile P746
(SC) 13-51
Object
Request
Response
(Library will parse)
(Library will respond with)
23
2
16-Bit Frozen
Counter Event
1
(read)
06
07,
08
23
5
32-Bit Frozen
Counter Event
with Time
1
(read)
06
07,
08
23
6
16-Bit Frozen
Counter Event
with Time
1
(read)
06
07,
08
30
30
30
30
30
0
1
2
Analog Input Any Variation
32-Bit Analog
Input
16-Bit Analog
Input
3
32-Bit Analog
Input without
(default see note 1) Flag
4
16-Bit Analog
Input without
Flag
1
22
1
1
1
1
(read)
(assign class)
(read)
(read)
(read)
(read)
00,
01
06
07,
08
17,
27,
28
00,
01
06
07,
08
17,
27,
28
00,
01
06
07,
08
17,
27,
28
00,
01
06
07,
08
17,
27,
28
00,
01
06
07,
08
17,
27,
28
(no
range, or
all)
(limited
qty)
(no
range, or
all)
(limited
qty)
(no
range, or
all)
(limited
qty)
(startstop)
(no
range, or
all)
(limited
qty)
(index)
(startstop)
(no
range, or
all)
(limited
qty)
(index)
(startstop)
(no
range, or
all)
(limited
qty)
(index)
(startstop)
(no
range, or
all)
(limited
qty)
(index)
(startstop)
(no
range, or
all)
(limited
qty)
(index)
129
response
17,
28
(index)
129
response
17,
28
(index)
129
response
17,
28
(index)
response
00,
01
17,
28
(startstop)
(index see note
2)
response
00,
01
17,
28
(startstop)
(index see note
2)
response
00,
01
17,
28
(startstop)
(index see note
2)
129
129
129
SC
129
response
00,
01
17,
28
(startstop)
(index see note
2)
P746/EN SC/J43
SCADA Communications
(SC) 13-52
MiCOM P40 Agile P746
Object
30
32
32
32
Response
(Library will respond with)
5
Short floating
point
1
(read)
00,
01
06
07,
08
17,
27,
28
0
Analog Change
Event - Any
Variation
1
(read)
06
07,
08
1
32-Bit Analog
Change Event
(default see note 1) without Time
1
(read)
06
07,
08
16-Bit Analog
Change Event
without Time
1
(read)
06
07,
08
2
32
3
32-Bit Analog
Change Event
with Time
1
(read)
06
07,
08
32
4
16-Bit Analog
Change Event
with Time
1
(read)
06
07,
08
5
Short floating
point Analog
Change Event
without Time
1
(read)
06
07,
08
7
Short floating
point Analog
Change Event
with Time
1
(read)
06
07,
08
0
Analog Input
Deadband
(Variation 0 is
used to request
default
variation)
32
32
SC
Request
(Library will parse)
34
34
1
1
16 Bit Analog
1
Input Deadband
(read)
(read)
00,
01
06
07,
08
17,
27,
28
00,
01
06
07,
08
17,
27,
28
(startstop)
(no
range, or
all)
(limited
qty)
(index)
(no
range, or
all)
(limited
qty)
(no
range, or
all)
(limited
qty)
(no
range, or
all)
(limited
qty)
(no
range, or
all)
(limited
qty)
(no
range, or
all)
(limited
qty)
(no
range, or
all)
(limited
qty)
(no
range, or
all)
(limited
qty)
(startstop)
(no
range, or
all)
(limited
qty)
(index)
(startstop)
(no
range, or
all)
(limited
qty)
(index)
(startstop)
(index see note
2)
129
response
00,
01
17,
28
129
response
17,
28
(index)
129
response
17,
28
(index)
129
response
17,
28
(index)
129
response
17,
28
(index)
129
response
17,
28
(index)
129
response
17,
28
(index)
response
00,
01
17,
28
(startstop)
(index see note
2)
129
SCADA Communications
P746/EN SC/J43
MiCOM P40 Agile P746
(SC) 13-53
Object
2
34
2
32 Bit Analog
1
(default Input Deadband
see note 1)
2
34
3
Short Floating
Point Analog
1
Input Deadband
2
Analog Output
Status (Variation
0 is used to
1
request default
variation)
40
0
40
1
32-Bit Analog
(default Output Status
see note 1)
40
2
16-Bit Analog
Output Status
1
1
Request
Response
(Library will parse)
(Library will respond with)
(write)
(read)
(write)
(read)
(write)
(read)
(read)
(read)
00,
01
07,
08
17,
27,
28
00,
01
06
07,
08
17,
27,
28
00,
01
07,
08
17,
27,
28
00,
01
06
07,
08
17,
27,
28
00,
01
07,
08
17,
27,
28
00,
01
06
07,
08
17,
27,
28
00,
01
06
07,
08
17,
27,
28
00,
01
06
07,
08
17,
27,
28
(startstop)
(limited
qty)
(index)
(startstop)
(no
range, or
129
all)
(limited
qty)
(index)
response
00,
01
17,
28
(startstop)
(index see note
2)
response
00,
01
17,
28
(startstop)
(index see note
2)
response
00,
01
17,
28
(startstop)
(index see note
2)
response
00,
01
17,
28
(startstop)
(index see note
2)
(startstop)
(limited
qty)
(index)
(startstop)
(no
range, or
129
all)
(limited
qty)
(index)
(startstop)
(limited
qty)
(index)
(startstop)
(no
range, or
all)
(limited
qty)
(index)
(startstop)
(no
range, or
129
all)
(limited
qty)
(index)
(startstop)
(no
range, or
129
all)
(limited
qty)
(index)
SC
P746/EN SC/J43
SCADA Communications
(SC) 13-54
MiCOM P40 Agile P746
Object
3
Short Floating
Point Analog
Output Status
41
1
32-Bit Analog
Output Block
41
2
16-Bit Analog
Output Block
41
3
Short Floating
Point Analog
Output Block
40
50
1
(default Time and Date
see note 1)
Request
Response
(Library will parse)
(Library will respond with)
00,
01
06
07,
08
17,
27,
28
(startstop)
(no
range, or
129
all)
(limited
qty)
(index)
response
17,
28
27
(index)
(index)
129
response
17,
28
27
(index)
(index)
129
response
17,
27,
28
(index)
129
response
(limited
qty = 1)
129
response
1
(read)
3
4
5
6
3
4
5
6
3
4
5
6
(select)
(operate)
(direct op)
(dir. op, noack)
(select)
(operate)
(direct op)
(dir. op, noack)
(select)
(operate)
(direct op)
(dir. op, noack)
1
(read)
07
2
(write)
07
60
0
Not defined
60
1
Class 0 Data
1
(read)
06
60
2
Class 1 Data
1
(read)
06
07,
08
22
(assign class)
06
1
(read)
06
07,
08
22
(assign class)
06
1
(read)
06
07,
08
22
(assign class)
06
1
(read)
06
07,
08
60
3
Class 2 Data
SC
60
70
4
0
Class 3 Data
File Event - Any
Variation
(limited
qty = 1)
(no
range, or
all)
(no
range, or
all)
(limited
qty)
(no
range, or
all)
(no
range, or
all)
(limited
qty)
(no
range, or
all)
(no
range, or
all)
(limited
qty)
(no
range, or
all)
(no
range, or
all)
(limited
qty)
00,
01
17,
28
(startstop)
(index see note
2)
echo of
request
echo of
request
echo of
request
07
(limited
qty = 1)
SCADA Communications
P746/EN SC/J43
MiCOM P40 Agile P746
(SC) 13-55
Object
(assign class)
06
29
(authenticate)
5b
(open)
(delete)
(close)
(abort)
(read)
2
File
Authentication
70
3
File Command
70
4
File Command
Status
25
27
26
30
70
5
File Transfer
1
70
6
File Transfer
Status
70
7
File Descriptor
80
1
Note:
Response
(Library will respond with)
22
70
Internal
Indications
No Object
(function code
only)
No Object
(function code
only)
No Object
(function code
only)
Request
(Library will parse)
(no
range, or
all)
(free129
format)
response
5B (freeformat)
5B (freeformat)
5b
(freeformat)
5b
(freeformat)
129
response
5b
(freeformat)
129
response
129
response
129
response
129
response
28
(get file info)
5b
1
(read)
00,
01
13
(cold restart)
14
(warm restart)
23
(delay meas.)
(freeformat)
(startstop)
5B (freeformat)
5B (freeformat)
5B (freeformat)
(startstop)
00,
01
A Default variation refers to the variation responded to when variation 0 is
requested and/or in class 0, 1, 2, or 3 scans.
For static (non-change-event) objects, qualifiers 17 or 28 are only responded
to when a request is sent with qualifiers 17 or 28, respectively. Otherwise,
static object requests sent with qualifiers 00, 01, 06, 07, or 08, will be
responded to with qualifiers 00 or 01. For change-event objects, qualifiers 17
or 28 are always responded to.
7.4.8.3
DNP3 Internal Indications
The following table lists the DNP3.0 Internal Indications (IIN) and identifies those that are
supported by the device.
The IIN form an information element used to convey the internal states and diagnostic
results of a device. This information can be used by a receiving station to perform error
recovery or other suitable functions. The IIN is a two-octet field that follows the function code
in all responses from the device. When a request cannot be processed due to formatting
errors or the requested data is not available, the IIN is always returned with the appropriate
bits set.
Bit
Indication
Description
Supported
Octet 1
0
All stations message received
1
Class 1 data available
Set when a request is received with the destination address of the
all stations address (6553510). It is cleared after the next response
(even if a response to a global request is required).
Yes
This IIN is used to let the master station know that a "broadcast"
message was received by the relay.
Set when data that has been configured as Class 1 data is ready
to be sent to the master.
Yes
The master station should request this class data from the relay
when this bit is set in a response.
SC
P746/EN SC/J43
SCADA Communications
(SC) 13-56
MiCOM P40 Agile P746
Bit
Indication
2
Class 2 data available
3
Class 3 data available
4
Time-synchronization required
5
Local
6
Device in trouble
7
Device restart
Description
Set when data that has been configured as Class 2 data is ready
to be sent to the master.
The master station should request this class data from the relay
when this bit is set in a response.
Set when data that has been configured as Class 3 data is ready
to be sent to the master.
The master station should request this class data from the relay
when this bit is set in a response.
The relay requires time synchronization from the master station
(using the Time and Date object).
This IIN is cleared once the time has been synchronized. It can also
be cleared by explicitly writing a 0 into this bit of the Internal
Indication object.
Set when some or all of the relays digital output points (Object
10/12) are in the Local state. That is, the relays control outputs are
NOT accessible through the DNP protocol.
This IIN is clear when the relay is in the Remote state. That is, the
relays control outputs are fully accessible through the DNP
protocol.
Set when an abnormal condition exists in the relay. This IIN is only
used when the state cannot be described by a combination of one
or more of the other IIN bits.
Set when the device software application restarts. This IIN is
cleared when the master station explicitly writes a 0 into this bit of
the Internal Indications object.
Octet 2
0
Function code not implemented The received function code is not implemented within the relay.
The relay does not have the specified objects or there are no
objects assigned to the requested class.
1
Requested object(s) unknown
This IIN should be used for debugging purposes and usually
indicates a mismatch in device profiles or configuration problems.
Parameters in the qualifier, range or data fields are not valid or
out of range. This is a 'catch-all' for application request formatting
2
Out of range
errors. It should only be used for debugging purposes. This IIN
usually indicates configuration problems.
Event buffer(s), or other application buffers, have overflowed. The
master station should attempt to recover as much data as
3
Buffer overflow
possible and indicate to the user that there may be lost data. The
appropriate error recovery procedures should be initiated by the
user.
The received request was understood but the requested operation
4
Already executing
is already executing.
Set to indicate that the current configuration in the relay is
corrupt. The master station may download another configuration
5
Bad configuration
to the relay.
6
Reserved
Always returned as zero.
7
Reserved
Always returned as zero.
SC
7.4.8.4
Supported
Yes
Yes
Yes
No
No
Yes
Yes
Yes
Yes
Yes
Yes
DNP3 Response Status Codes
When the device processes Control Relay Output Block (Object 12) requests, it returns a set
of status codes; one for each point contained within the original request. The complete list of
codes appears in the following table:
Code Number
Identifier Name
0
Success
1
Timeout
Description
The received request has been accepted, initiated, or queued.
The request has not been accepted because the ‘operate’ message was
received after the arm timer (Select Before Operate) timed out.
The arm timer was started when the select operation for the same point was
received.
SCADA Communications
P746/EN SC/J43
MiCOM P40 Agile P746
Code Number
(SC) 13-57
Identifier Name
2
No select
3
Format error
4
Not supported
5
Already active
6
7
Hardware error
Local
8
Too many operations
9
127
Not authorized
Undefined
Description
The request has not been accepted because no previous matching ‘select’
request exists. (An ‘operate’ message was sent to activate an output that was
not previously armed with a matching ‘select’ message).
The request has not been accepted because there were formatting errors in
the control request (‘select’, ‘operate’, or ‘direct operate’).
The request has not been accepted because a control operation is not
supported for this point.
The request has not been accepted because the control queue is full or the
point is already active.
The request has not been accepted because of control hardware problems.
The request has not been accepted because local access is in progress.
The request has not been accepted because too many operations have been
requested.
The request has not been accepted because of insufficient authorization.
The request not been accepted because of some other undefined reason.
Note: Code numbers 10 through to 126 are reserved for future use.
7.4.9
DNP3 Configuration
To configure the device:
10.Select the CONFIGURATION column and check that the Comms settings cell is set
to Visible.
11.Select the COMMUNICATIONS column.
12.
Move to the first cell down (RP1 protocol). This is a non-settable cell, which
shows the chosen communication protocol – in this case DNP3.0.
RP1 Protocol
DNP3.0
13.Move down to the next cell (RP1 Address). This cell controls the DNP3.0 address of
the relay. Up to 32 relays can be connected to one spur, therefore it is necessary for
each relay to have a unique address so that messages from the master control station
are accepted by only one relay. DNP3.0 uses a decimal number between 1 and 65519
for the Relay Address. It is important that no two relays have the same address.
RP1 Address
1
14.Move down to the next cell (RP1 Baud Rate). This cell controls the baud rate to be
used. Six baud rates are supported by the relay 1200 bps, 2400 bps, 4800 bps,
9600 bps, 19200 bps and 38400 bps. Make sure that the baud rate selected on the
relay is the same as that set on the master station.
RP1 Baud rate
9600 bits/s
15.Move down to the next cell (RP1 Parity). This cell controls the parity format used in
the data frames. The parity can be set to be one of None, Odd or Even. Make sure
that the parity format selected on the relay is the same as that set on the master
station.
SC
P746/EN SC/J43
SCADA Communications
(SC) 13-58
MiCOM P40 Agile P746
RP1 Parity
None
16.If the optional fibre optic connectors are fitted, the RP1 PhysicalLink cell is visible.
This cell controls the physical media used for the communication (Copper or Fibre
optic).
RP1 PhysicalLink
Copper
17.Move down to the next cell (RP1 Time Sync). This cell affects the time
synchronisation request from the master by the relay. It can be set to enabled or
disabled. If enabled it allows the DNP3.0 master to synchronise the time on the relay.
RP1 Time Sync
Enabled
7.4.9.1
DNP3 configurator
A PC support package for DNP3.0 is available as part of the supplied settings application
software (MiCOM S1 Agile) to allow configuration of the device's DNP3.0 response. The
configuration data is uploaded from the device to the PC in a block of compressed format
data and downloaded in a similar manner after modification. The new DNP3.0 configuration
takes effect after the download is complete. To restore the default configuration at any time,
from the CONFIGURATION column, select the Restore Defaults cell then select All
Settings.
In MiCOM S1 Agile, the DNP3.0 data is shown in three main folders, one folder each for the
point configuration, integer scaling and default variation (data format). The point
configuration also includes screens for binary inputs, binary outputs, counters and analogue
input configuration.
If the device supports DNP Over Ethernet, the configuration related settings are done in the
folder DNP Over Ethernet.
7.5
Modbus
This section describes how the MODBUS standard is applied to the Px40 platform. It is not a
description of the standard itself. The level at which this section is written assumes that the
reader is already familiar with the MODBUS standard.
SC
The MODBUS protocol is a master/slave protocol, defined and administered by the
MODBUS Organization For further information on MODBUS and the protocol specifications,
please see the Modbus web site (www.modbus.org).
7.5.1
Physical connection and link layer
Only one option is available for connecting MODBUS
• Rear serial port 1 - for permanent SCADA connection via EIA(RS)485
The MODBUS interface uses ‘RTU’ mode communication rather than ‘ASCII’ mode as this
provides more efficient
use of the communication bandwidth. This mode of communication is defined by the
MODBUS standard.
SCADA Communications
P746/EN SC/J43
MiCOM P40 Agile P746
(SC) 13-59
The IED address and baud rate can be selected using the front panel menu or by a suitable
application such as MiCOM Agile.
When using a serial interface, the data format is: 1 start bit, 8 data bits, 1 parity bit with 1
stop bit, or 2 stop bits (a total of 11 bits per character).
7.5.2
MODBUS Functions
The following MODBUS function codes are supported by the relay:
Query
function code
01
Read Coil Status
02
Read Input Status
03
04
06
07
08
Read Holding Registers
Read Input Registers
Preset Single Register
Read Exception Status
Diagnostics
Fetch Communication Event
Counter
Fetch Communication Event Log
Preset Multiple Registers
11
12
16
7.5.3
MODBUS
query name
Read status of output contacts (0x addresses)
Read status of opto-isolated status inputs
(1x addresses)
Read setting values (4x addresses)
Read measurement values (3x addresses)
Write single setting value (4x addresses)
Read relay status, same value as register 3x1
Application defined by the MODBUS protocol specification
Write multiple setting values (4x addresses)
Response codes
Code
7.5.4
Application
MODBUS Description
01
Illegal Function Code
02
Illegal Data Address
03
Illegal Value
06
Slave Device Busy
MiCOM Interpretation
The function code transmitted is not supported by the slave.
The start data address in the request is not an allowable
value. If any of the addresses in the range cannot be
accessed due to password protection then all changes
within the request are discarded and this error response will
be returned.
Note: If the start address is correct but the range includes
non–implemented addresses this response is not produced.
A value referenced in the data field transmitted by the
master is not within range. Other values transmitted within
the same packet will be executed if inside range.
The write command cannot be implemented due to the
database being locked by another interface. This response
is also produced if the relay software is busy executing a
previous request.
Register Mapping
The relay supports the following memory page references:
• Memory Page
Interpretation
• 0xxxx
Read and write access of the output relays
• 1xxxx
Read only access of the opto inputs
• 3xxxx
Read only access of data
• 4xxxx
Read and write access of settings
Where xxxx represents the addresses available in the page (0 to 9999).
Note:
The “extended memory file” (6xxxx) is not supported.
A complete map of the MODBUS addresses supported by the relay is contained in the menu
database.
The MODBUS convention is to document register addresses as ordinal values whereas the
actual protocol addresses are literal values. The MiCOM relays begin their register
addresses at zero. Therefore, the first register in a memory page is register address zero.
The second register is register address 1 and so on.
SC
P746/EN SC/J43
SCADA Communications
(SC) 13-60
MiCOM P40 Agile P746
Note:
7.5.5
The page number notation is not part of the address.
Event Extraction
The relay supports two methods of event extraction providing either automatic or manual
extraction of the stored event, fault, and maintenance records.
7.5.5.1
Automatic Event Record Extraction
The automatic extraction facilities allow all types of record to be extracted as they occur.
Event records are extracted in sequential order including any fault or maintenance data that
may be associated with the event.
The MODBUS master can determine whether the device has any events stored that have
not yet been extracted.
This is performed by reading the status register 30001 (G26 data type). If the event bit of this
register is set then the device has non-extracted events available. To select the next event
for sequential extraction, the master station writes a value of 1 to the record selection
register 40400 (G18 data type). The event data together with any fault/maintenance data can
be read from the registers specified below. Once the data has been read, the event record
can be marked as having been read by writing a value of '2' to register 40400.
7.5.5.2
Manual Event Record Extraction
There are three registers available to manually select stored records, there are also three
read only registers allowing the number of stored records to be determined.
40100 - Select Event, 0 to 249
40101 - Select Fault, 0 to 4
40102 - Select Maintenance Record, 0 to 4
For each of the above registers a value of 0 represents the most recent stored record. The
following registers can be read to indicate the numbers of the various types of record stored.
30100 - Number of stored records
30101 - Number of stored fault records
30102 - Number of stored maintenance records
Each fault or maintenance record logged causes an event record to be created by the relay.
If this event record is selected the additional registers allowing the fault or maintenance
record details will also become populated.
7.5.5.3
Record Data
The location and format of the registers used to access the record data is the same whether
they have been selected using either of the two mechanisms detailed above.
Event Description
SC
MODBUS
Address
Length
Time and Date
Event Type
30103
30107
4
1
Event Value
30108
2
Comments
See G12 data type description in section 3.8.
See G13 data type. Indicates type of event.
Nature of value depends on event type. This will contain the
status as a binary flag for contact, opto, alarm, and
protection events.
SCADA Communications
P746/EN SC/J43
MiCOM P40 Agile P746
Event Description
(SC) 13-61
MODBUS
Address
Length
MODBUS Address
30110
1
Event Index
30111
1
Additional Data
Present
30112
1
Comments
This indicates the MODBUS register address where the
change occurred.
Alarm 30011
Relays 30723
Optos 30725
Protection events – like the relay and opto addresses this will
map onto the MODBUS address of the appropriate DDB
status register depending on which bit of the DDB the
change occurred. These will range from 30727 to 30785.
For platform events, fault events and maintenance events
the default is 0.
This register will contain the DDB ordinal for protection
events or the bit number for alarm events. The direction of
the change will be indicated by the most significant bit; 1 for
0 – 1 change and 0 for 1 – 0 change.
0 means that there is no additional data.
1 means fault record data can be read from 30113 to 30199
(number of registers depends on the product).
2 means maintenance record data can be read from 30036
to 30039.
If a fault record or maintenance record is directly selected using the manual mechanism then
the data can be read from the register ranges specified above. The event record data in
registers 30103 to 30111 will not be available.
It is possible using register 40401(G6 data type) to clear independently the stored relay
event/fault and maintenance records. This register also provides an option to reset the relay
indications, which has the same effect on the relay as pressing the clear key within the alarm
viewer using the front panel menu.
7.5.6
Disturbance Record Extraction
The relay provides facilities for both manual and automatic extraction of disturbance records.
The extraction mechanisms are explained below:
Records extracted over MODBUS from Px40 platform relays will be presented in
COMTRADE format. This involves extracting an ASCII text configuration file and then
extracting a binary data file.
Each file is extracted by reading a series of data pages from the relay. The data page is
made up of 127 registers, giving a maximum transfer of 254 bytes per page.
The following set of registers is presented to the master station to support the extraction of
uncompressed disturbance records:
MODBUS Register
Name
3x00001
Status register
3x00800
No of stored disturbances
Description
Provides the status of the relay as bit flags:
b0
–
Out of service
b1
–
Minor self test failure
b2
–
Event
b3
–
Time synchronization
b4
–
Disturbance
b5
–
Fault
b6
–
Trip
b7
–
Alarm
b8 to b15 –
Unused
A ‘1’ on b4 indicates the presence of a disturbance.
Indicates the total number of disturbance records
currently stored in the relay, both extracted and
unextracted.
SC
P746/EN SC/J43
SCADA Communications
(SC) 13-62
MiCOM P40 Agile P746
MODBUS Register
Description
Indicates the unique identifier value for the oldest
disturbance record stored in the relay. This is an
Unique identifier of the
integer value used in conjunction with the ‘No of
oldest disturbance record
stored disturbances’ value to calculate a value for
manually selecting records.
This register is used to manually select disturbance
records. The values written to this cell are an offset
of the unique identifier value for the oldest record.
Manual disturbance record
The offset value, which ranges from 0 to the No of
selection register
stored disturbances – 1, is added to the identifier of
the oldest record to generate the identifier of the
required record.
This register is used during the extraction process
and has a number of commands. These are:
b0
–
Select next event
b1
–
Accept event
Record selection command
b2
–
Select next disturbance record
register
b3
–
Accept disturbance record
b4
–
Select next page of disturbance
data
b5
–
Select data file
These registers return the timestamp of the
Record time stamp
disturbance record.
This register informs the master station of the
No of registers in data
number of registers in the data page that are
page
populated.
These 127 registers are used to transfer data from
the relay to the master station. They are 16-bit
Data page registers
unsigned integers.
The disturbance record status register is used
Disturbance record status during the extraction process to indicate to the
register
master station when data is ready for extraction.
See next table.
This is used to select the required data file format.
Data file format selection
This is reserved for future use.
3x00801
4x00250
4x00400
3x00930 – 3x00933
3x00802
3x00803 – 3x00929
3x00934
4x00251
Note:
Name
Register addresses are provided in reference code + address format. E.g.
4x00001 is reference code 4x, address 1 (which is specified as function
code 03, address 0x0000 in the MODBUS specification).
The disturbance record status register will report one of the following values:
State
Idle
Busy
Page ready
Configuration complete
Record complete
SC
Disturbance overwritten
No unextracted disturbances
Not a valid disturbance
Command out of sequence
7.5.6.1
Description
This will be the state reported when no record is selected; such as after power on or
after a record has been marked as extracted.
The relay is currently processing data.
The data page has been populated and the master station can now safely read the
data.
All of the configuration data has been read without error.
All of the disturbance data has been extracted.
An error occurred during the extraction process where the disturbance being
extracted was overwritten by a new record.
An attempt was made by the master station to automatically select the next oldest
unextracted disturbance when all records have been extracted.
An attempt was made by the master station to manually select a record that did not
exist in the relay.
The master station issued a command to the relay that was not expected during the
extraction process.
Manual extraction procedure
The procedure used to extract a disturbance manually is shown in the following figure. The
manual method of extraction does not allow for the acceptance of disturbance records.
SCADA Communications
P746/EN SC/J43
MiCOM P40 Agile P746
(SC) 13-63
Figure 12: Manual selection of a disturbance record
7.5.6.2
Automatic Extraction Procedure
There are two methods that can be used for automatically extracting disturbances.
Method 1
Method 1is simpler and is better at extracting single disturbance records (when the
disturbance recorder is polled regularly).
SC
P746/EN SC/J43
(SC) 13-64
SCADA Communications
MiCOM P40 Agile P746
SC
Figure 13: Automatic selection of a disturbance – method 1
Method 2
Method 2 is more complex to implement but is more efficient at extracting large quantities of
disturbance records. This may be useful when the disturbance recorder is polled only
occasionally and hence may have many stored records.
SCADA Communications
MiCOM P40 Agile P746
P746/EN SC/J43
(SC) 13-65
SC
Figure 14: Automatic selection of a disturbance – option 2
7.5.6.3
Extracting the Disturbance Data
The extraction of the disturbance record is a two-stage process that involves extracting the
configuration file first and then the data file.
P746/EN SC/J43
(SC) 13-66
Extracting the Comtrade configuration file
SC
Figure 15: Configuration file extraction
SCADA Communications
MiCOM P40 Agile P746
SCADA Communications
MiCOM P40 Agile P746
P746/EN SC/J43
(SC) 13-67
Extracting the Comtrade data file
SC
Figure 16: Data file extraction
During the extraction of the COMTRADE files, an error may occur that will be reported on the
DR Status register 3x00934. This can be caused by the relay overwriting the record being
P746/EN SC/J43
SCADA Communications
(SC) 13-68
MiCOM P40 Agile P746
extracted or due to the master station issuing a command that is not within the bounds of the
extraction procedure.
State
Description
Idle
Busy
Page ready
Configuration complete
Record complete
Disturbance overwritten
No unextracted disturbances
Not a valid disturbance
Command out of sequence
7.5.7
This will be the state reported when no record is selected; such as after power on or
after a record has been marked as extracted.
The relay is currently processing data.
The data page has been populated and the master station can now safely read the
data.
All of the configuration data has been read without error.
All of the disturbance data has been extracted.
An error occurred during the extraction process where the disturbance being
extracted was overwritten by a new record.
An attempt was made by the master station to automatically select the next oldest
unextracted disturbance when all records have been extracted.
An attempt was made by the master station to manually select a record that did not
exist in the relay.
The master station issued a command to the relay that was not expected during the
extraction process.
Setting Changes
All the relay settings are 4xxxx page addresses. The following points should be noted when
changing settings:
• Settings implemented using multiple registers must be written to using a multi-register
write operation.
• The first address for a multi-register write must be a valid address, if there are
unmapped addresses within the range being written to then the data associated with
these addresses will be discarded.
• If a write operation is performed with values that are out of range then the illegal data
response will be produced. Valid setting values within the same write operation will be
executed.
• If a write operation is performed attempting to change registers that require a higher
level of password access than is currently enabled then all setting changes in the write
operation will be discarded.
7.5.8
Password Protection
The following registers are available to control password protection:
SC
7.5.9
• 40001 & 40002
Password entry
• 40022
Default password level
• 40023 & 40024
Setting to change password level 1
• 40025 & 40026
Setting to change password level 2
• 30010
Can be read to indicate current access level
Control and Support Settings
Control and support settings are executed immediately on the write operation.
7.5.10
Protection and Disturbance Recorder Settings
Setting changes to either of these areas are stored in a scratchpad area and will not be used
by the relay unless a confirm or an abort operation is performed. Register 40405 can be
used either to confirm or abort the setting changes within the scratchpad area.
The relay supports four groups of protection settings. The MODBUS addresses for each of
the four groups are repeated within the following address ranges:
• Group 1
41000 - 42999
SCADA Communications
P746/EN SC/J43
MiCOM P40 Agile P746
(SC) 13-69
• Group 2
43000 - 44999
• Group 3
45000 - 46999
• Group 4
47000 - 48999
In addition to the basic editing of the protection setting groups, the following functions are
provided:
• Default values can be restored to a setting group or to all of the relay settings by
writing to register 40402.
• It is possible to copy the contents of one setting group to another by writing the source
group to register 40406 and the target group to 40407.
The setting changes performed by either of the two operations defined above are made to
the scratchpad area. These changes must be confirmed by writing to register 40405.
The active protection setting groups can be selected by writing to register 40404. An illegal
data response will be returned if an attempt is made to set the active group to one that has
been disabled.
7.5.11
Time Synchronisation
The date-time data type G12 allows real date and time information to be conveyed down to a
resolution of 1ms. The structure of the data type is shown in the following table and is
compliant with the IEC 60870-5-4 Binary Time 2a format.
The seven bytes of the date/time frame are packed into four 16-bit registers and are
transmitted in sequence starting from byte 1. This is followed by a null byte, making eight
bytes in total.
Register data is usually transmitted starting with the highest-order byte. Therefore byte 1 will
be in the high-order byte position followed by byte 2 in the low-order position for the first
register. The last register will contain just byte 7 in the high order position and the low order
byte will have a value of zero.
Bit Position
Byte
7
m7
m15
IV
SU
W2
R
R
1
2
3
4
5
6
7
6
m6
m14
R
R
W1
R
Y6
5
m5
m13
I5
R
W0
R
Y5
4
m4
m12
I4
H4
D4
R
Y4
3
m3
m11
I3
H3
D3
M3
Y3
2
m2
m10
I2
H2
D2
M2
Y2
1
m1
m9
I1
H1
D1
M1
Y1
0
m0
m8
I0
H0
D0
M0
Y0
Where:
• m
=
0…59,999ms
• I
=
0…59 minutes
• H
=
0…23 Hours
• W
=
1…7 Day of week; Monday to Sunday, 0 for not calculated
• D
=
1…31 Day of Month
• M
=
1…12 Month of year; January to December
• Y
=
0…99 Years (year of century)
• R
=
Reserved bit = 0
• SU
=
summertime: 0 = standard time, 1 = summer time
• IV
=
invalid value: 0 = valid, 1 = invalid
SC
P746/EN SC/J43
SCADA Communications
(SC) 13-70
MiCOM P40 Agile P746
• range =
0ms…99 years
Since the range of the data type is only 100 years, the century must be deduced. The
century is calculated as the one that will produce the nearest time value to the current date.
For example: 30-12-99 is 30-12-1999 when received in 1999 & 2000, but is 30-12-2099
when received in 2050. This technique allows 2 digit years to be accurately converted to 4
digits in a ±50 year window around the current datum.
The invalid bit has two applications:
• It can indicate that the date-time information is considered inaccurate but is the best
information available.
• Date-time information is not available.
The summertime bit is used to indicate that summertime (day light saving) is being used and,
more importantly, to resolve the alias and time discontinuity which occurs when summertime
starts and ends This is important for the correct time correlation of time stamped records.
The day of the week field is optional and if not calculated will be set to zero.
The concept of time zone is not catered for by this data type and hence by the relay. It is up
to the end user to determine the time zone utilized by the relay. Normal practice is to use
UTC (universal co-ordinated time), which avoids the complications with day light saving
time-stamp correlation’s.
7.5.12
Power & Energy Measurement Data Formats (G29 & G125)
The power and energy measurements are available in two data formats:
G29 integer format and G125 IEEE754 floating point format. For historical reasons the
registers listed in the main part of the Measurements 2 column of the menu database are of
the G29 format. The floating point, G125, versions appear at the end of the column.
Data type G29
Data type G29 consists of three registers:
The first register is the per unit power or energy measurement and is of type G28, which is a
signed 16 bit quantity. The second and third registers contain a multiplier to convert the per
unit value to a real value. The multiplier is of type G27, which is an unsigned 32-bit quantity.
Thus, the overall value conveyed by the G29 data type must be calculated as G29 =
G28×G27.
The relay calculates the G28 per unit power or energy value as G28 = ((measured
secondary quantity)/(CT secondary) × (110 V/(VT secondary)). Since data type G28 is a
signed 16-bit integer, its dynamic range is constrained to ±32768. This limitation should be
borne in mind for the energy measurements, as the G29 value will saturate a long time
before the equivalent G125 does.
The associated G27 multiplier is calculated as G27 = (CT primary) × (VT primary/110 V)
when primary value measurements are selected, and as G27 = (CT secondary) × (VT
secondary/110 V) when secondary value measurements are selected.
SC
Due to the required truncations from floating point values to integer values in the calculations
of the G29 component parts and its limited dynamic range, the use of the G29 values is only
recommended when the MODBUS master cannot deal with the G125 IEEE754 floating point
equivalents.
Note:
The G29 values must be read in whole multiples of three registers. It is not
possible to read the G28 and G27 parts with separate read commands.
Example:
For A-Phase Power (Watts) (registers 30300 - 30302) for a 110 V relay, In = 1A,
VT ratio = 110 V:110 V and CT ratio = 1A:1A.
Applying A-phase 1A @ 63.51 V
SCADA Communications
P746/EN SC/J43
MiCOM P40 Agile P746
(SC) 13-71
A-phase Watts = ((63.51 V × 1A)/In = 1A) × (110/Vn = 110 V) = 63.51 Watts
The G28 part of the value is the truncated per unit quantity, which will be equal to 64 (40h).
The multiplier is derived from the VT and CT ratios set in the relay, with the equation
((CT Primary) × (VT Primary)/110 V). Therefore, the G27 part of the value will equal 1.
Hence the overall value of the G29 register set is 64×1 = 64 W
The registers would contain:
30300 - 0040h
30301 - 0000h
30302 - 0001h
Using the previous example with a VT ratio = 110,000 V; 110 V and CT ratio = 10,000A:1A
the G27 multiplier would be 10,000A × 110,000 V/110 = 10,000,000. The overall value of
the G29 register set is 64 × 10,000,000 = 640 MW. (Note that there is an actual error of
49 MW in this calculation due to loss of resolution.)
The registers would contain:
30300 - 0040h
30301 - 0098h
30302 - 9680h
Data type G125
Data type G125 is a short float IEEE754 floating point format, which occupies 32 bits in two
consecutive registers. The high order byte of the format is in the first (low order) register and
the low order byte in the second register.
The value of the G125 measurement is as accurate as the relay’s ability to resolve the
measurement after it has applied the secondary or primary scaling factors as require. It
does not suffer from the truncation errors or dynamic range limitations associated with the
G29 data format.
7.5.13
Modbus Configuration
To configure the device:
18.Select the CONFIGURATION column and check that the Comms settings cell is set
to Visible.
19.Select the COMMUNICATIONS column.
20.Move to the first cell down (RP1 protocol). This is a non-settable cell, which shows
the chosen communication protocol – in this case Modbus.
RP1 Protocol
Modbus
21.Move down to the next cell (RP1 Address). This cell controls the Modbus address of
the device. Up to 32 relays can be connected to one spur. It is therefore necessary for
each relay to have a unique address so that messages from the master control station
are accepted by one relay. Modbus uses a decimal number between 1 and 247 for the
Relay Address. It is important that no two relays share the same address.
SC
P746/EN SC/J43
SCADA Communications
(SC) 13-72
MiCOM P40 Agile P746
RP1 Address
1
22.Move down to the next cell (RP1 InactivTimer). This cell controls the inactivity timer.
The inactivity timer controls how long the relay waits without receiving any messages
on the rear port before revoking any password access that was enabled and
discarding any changes. For the rear port this can be set between 1 and 30 minutes.
RP1 Inactiv timer
10.00 mins.
23.Move down to the next cell (RP1 Baud Rate). This cell controls the baud rate to be
used. Six baud rates are supported by the IED 1200 bits/s, 2400 bits/s, 4800 bits/s,
9600 bits/s, 19200 bits/s and 38400 bits/s. Make sure that the baud rate selected on
the relay is the same as that set on the master station.
RP1 Baud Rate
9600 bits/s
24.Move down to the next cell (RP1 Parity). This cell controls the parity format used in
the data frames. The parity can be set to be one of None, Odd or Even. Make sure
that the parity format selected on the relay is the same as that set on the master
station.
RP1 Parity
None
25.Move down to the next cell (Modbus IEC Time). This cell controls the order in which
the bytes of information are transmitted. There is a choice of Standard or Reverse.
When Standard is selected the time format complies with IEC 60870-5-4 requirements
such that byte 1 of the information is transmitted first, followed by bytes 2 through to 7.
If Reverse is selected the transmission of information is reversed.
SC
Modbus IEC Time
Standard
SCADA Communications
P746/EN SC/J43
MiCOM P40 Agile P746
7.6
(SC) 13-73
IEC 61850
This section describes how the IEC 61850 standard is applied to GE products. It is not a
description of the standard itself. The level at which this section is written assumes that the
reader is already familiar with the IEC 61850 standard.
IEC 61850 is the international standard for Ethernet-based communication in substations. It
enables integration of all protection, control, measurement and monitoring functions within a
substation, and additionally provides the means for interlocking and inter-tripping. It
combines the convenience of Ethernet with the security which is essential in substations
today.
There are two editions of most parts of the IEC 61850 standard; edition 1 and edition 2. The
edition which this product supports depends on the Software Version. For this software
version only edition 2 is supported.
An additional section detailing the enhancements in edition 2 models is documented later in
this chapter, if applicable.
7.6.1
Benefits of IEC 61850
The standard provides:
• Standardized models for IEDs and other equipment within the substation
• Standardized communication services (the methods used to access and exchange
data)
• Standardized formats for configuration files
• Peer-to-peer (e.g. relay to relay) communication
The standard adheres to the requirements laid out by the ISO OSI model and therefore
provides complete vendor interoperability and flexibility on the transmission types and
protocols used. This includes mapping of data onto Ethernet, which is becoming more and
more widely used in substations, in favour of RS485. Using Ethernet in the substation offers
many advantages, most significantly including:
• Ethernet allows high-speed data rates (currently 100 Mbps, rather than tens of kbps or
less used by most serial protocols)
• Ethernet provides the possibility to have multiple clients
• Ethernet is an open standard in every-day use
• There is a wide range of Ethernet-compatible products that may be used to
supplement the LAN installation (hubs, bridges, switches)
7.6.2
IEC 61850 Interoperability
A major benefit of IEC 61850 is interoperability. IEC 61850 standardizes the data model of
substation relays, which allows interoperability between products from multiple vendors.
An IEC 61850-compliant device may be interoperable, but this does not mean it is
interchangeable. You cannot simply replace a product from one vendor with that of another
without reconfiguration. However the terminology is pre-defined and anyone with prior
knowledge of IEC 61850 should be able to integrate a new device very quickly without
having to map all of the new data. IEC 61850 brings improved substation communications
and interoperability to the end user, at a lower cost.
7.6.3
The IEC 61850 Data Model
The data model of any IEC 61850 IED can be viewed as a hierarchy of information, whose
nomenclature and categorization is defined and standardized in the IEC 61850 specification.
SC
P746/EN SC/J43
SCADA Communications
(SC) 13-74
MiCOM P40 Agile P746
Figure 17: Data Model Layers in IEC 61850
The levels of this hierarchy can be described as follows:
Data frame format
Layer
Description
Physical Device
Identifies the actual IED within a system. Typically the
device’s name or IP address can be used (for example
Feeder_1 or 10.0.0.2.
Logical Device
Identifies groups of related Logical Nodes within the
Physical Device. For the MiCOM relays, 5 Logical
Devices exist: Control, Measurements, Protection,
Records, System.
Wrapper/Logical Node Instance
Identifies the major functional areas within the IEC
61850 data model. Either 3 or 6 characters are used as
a prefix to define the functional group (wrapper) while
the actual functionality is identified by a 4 character
Logical Node name suffixed by an instance number.
For example, XCBR1 (circuit breaker), MMXU1
(measurements), FrqPTOF2 (overfrequency protection,
stage 2).
SC
7.6.4
Data Object
This next layer is used to identify the type of data you
will be presented with. For example, Pos (position) of
Logical Node type XCBR.
Data Attribute
This is the actual data (measurement value, status,
description, etc.). For example, stVal (status value)
indicating actual position of circuit breaker for Data
Object type Pos of Logical Node type XCBR.
IEC 61850 in MiCOM Relays
IEC 61850 is implemented by use of a separate Ethernet card. This Ethernet card manages
the majority of the IEC 61850 implementation and data transfer to avoid any impact on the
performance of the protection functions.
To communicate with an IEC 61850 IED on Ethernet, it is necessary only to know its IP
address. This can then be configured into either:
• An IEC 61850 client (or master), for example a bay computer (MiCOM C264)
• An HMI
• An MMS browser, with which the full data model can be retrieved from the IED,
without any prior knowledge of the IED
SCADA Communications
P746/EN SC/J43
MiCOM P40 Agile P746
(SC) 13-75
The IEC 61850 compatible interface standard provides capability for the following:
• Read access to measurements
• Refresh of all measurements at the rate of once per second.
• Generation of non-buffered reports on change of status or measurement
• SNTP time synchronization over an Ethernet link. (This is used to synchronize the
IED's internal real time clock.
• GOOSE peer-to-peer communication
• Disturbance record extraction by file transfer. The record is extracted as an ASCII
format COMTRADE file
• Controls (Direct and Select Before Operate)
Note:
7.6.5
Setting changes are not supported in the current IEC 61850 implementation.
Currently these setting changes are carried out using the settings application
software.
IEC 61850 Data Model Implementation
The data model naming adopted in the relays has been standardised for consistency.
Therefore the Logical Nodes are allocated to one of the five Logical Devices, as appropriate.
The data model is described in the Model Implementation Conformance Statement (MICS)
document, which is available as a separate document.
7.6.6
IEC 61850 communication Services Implementation
The IEC 61850 communication services which are implemented in the relays are described
in the Protocol Implementation Conformance Statement (PICS) document, which is available
as a separate document
7.6.7
IEC 61850 Peer-to-Peer (GOOSE) Communications
The implementation of IEC 61850 Generic Object Oriented Substation Event (GOOSE)
enables faster communication between relays offering the possibility for a fast and reliable
system-wide distribution of input and output data values. The GOOSE model uses multicast
services to deliver event information. Multicast messaging means that messages are sent to
selected devices on the network. The receiving devices can specifically accept frames from
certain devices and discard frames from the other devices. It is also known as a publishersubscriber system. When a device detects a change in one of its monitored status points it
publishes a new message. Any device that is interested in the information subscribes to the
data it contains.
7.6.8
Goose message Validation
Whenever a new GOOSE message is received its validity is checked before the dataset is
decoded and used to update the Programmable Scheme Logic. As part of the validation
process a check is made for state and sequence number anomalies. If an anomaly is
detected, the 'out-of-order' GOOSE message is discarded. When a message is discarded
the last valid message remains active until a new valid GOOSE message is received or its
validity period (TAL) expires.
Out-of-order GOOSE message indicators and reporting are provided to the subscriber via
the IEC61850 LGOS logical node.
7.6.9
Mapping GOOSE Messages to Virtual Inputs
Each GOOSE signal contained in a subscribed GOOSE message can be mapped to any of
the virtual inputs within the PSL. The virtual inputs allow the mapping to internal logic
functions for protection control, directly to output contacts or LEDs for monitoring.
An IED can subscribe to all GOOSE messages but only the following data types can be
decoded and mapped to a virtual input:
• BOOLEAN
SC
P746/EN SC/J43
SCADA Communications
(SC) 13-76
MiCOM P40 Agile P746
• BSTR2
• INT16
• INT32
• INT8
• UINT16
• UINT32
• UINT8
7.6.9.1
IEC 61850 GOOSE Configuration
All GOOSE configuration is performed using the IEC 61850 Configurator tool available in the
MiCOM S1 Agile software application.
All GOOSE publishing configuration can be found under the GOOSE Publishing tab in the
configuration editor window. All GOOSE subscription configuration parameters are under the
External Binding tab in the configuration editor window.
Settings to enable GOOSE signalling and to apply Test Mode are available using the HMI.
7.6.10
Ethernet Functionality
IEC 61850 Associations are unique and made between the client and server. If Ethernet
connectivity is lost for any reason, the associations are lost, and will need to be reestablished by the client. The relay has a TCP_KEEPALIVE function to monitor each
association, and terminate any which are no longer active.
The relay allows the re-establishment of associations without disruption of its operation, even
after its power has been removed. As the relay acts as a server in this process, the client
must request the association. Uncommitted settings are cancelled when power is lost, and
reports requested by connected clients are reset. The client must re-enable these when it
next creates the new association to the relay.
7.6.11
IEC 61850 Configuration
You cannot configure the device for IEC 61850 edition 1 using the HMI panel on the product.
For this you must use the IEC 61850 Configurator, which is part of the settings application
software. If the device is compatible with edition 2, however, you can configure it with the
HMI. To configure IEC61850 edition 2 using the HMI, you must first enable the IP From HMI
setting, after which you can set the media (copper or fibre), IP address, subnet mask and
gateway address.
IEC 61850 allows relays to be directly configured from a configuration file. The relay’s
system configuration capabilities are determined from an IED Capability Description file
(ICD), supplied with the product. By using ICD files from the products to be installed, you can
design, configure and test (using simulation tools), a substation’s entire protection scheme
before the products are installed into the substation.
SC
To help with this process, the settings application software provides an IEC 61850
Configurator tool, which allows the pre-configured IEC 61850 configuration file to be
imported and transferred to the relay. As well as this, you can manually create configuration
files for all products, based on their original relay capability description (ICD file).
Other features include:
• The extraction of configuration data for viewing and editing.
• A sophisticated error checking sequence to validate the configuration data before
sending to the relay.
Note:
Some configuration data is available in the IEC61850 CONFIG. column,
allowing read-only access to basic configuration data.
SCADA Communications
MiCOM P40 Agile P746
P746/EN SC/J43
(SC) 13-77
7.6.11.1 IEC 61850 Configuration Banks
There are two configuration banks:
• 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.
Following an upgrade, the IEC 61850 Configurator tool can be used to transmit a command,
which authorises activation of the new configuration contained in the inactive configuration
bank. This is done by switching the active and inactive configuration banks. The capability of
switching the configuration banks is also available using the IEC61850 CONFIG. column of
the HMI.
The SCL Name and Revision attributes of both configuration banks are available in the
IEC61850 CONFIG. column of the HMI.
7.6.11.2 IEC 61850 Network Connectivity
Configuration of the IP parameters and SNTP (Simple Network Time Protocol) time
synchronisation parameters is performed by the IEC 61850 Configurator tool. If these
parameters are not available using an SCL (Substation Configuration Language) file, they
must be configured manually.
Every IP address on the Local Area Network must be unique. Duplicate IP addresses result
in conflict and must be avoided. Most IEDs check for a conflict on every IP configuration
change and at power up and they raise an alarm if an IP conflict is detected.
The relay can be configured to accept data from other networks using the Gateway setting.
If multiple networks are used, the IP addresses must be unique across networks.
7.6.12
IEC 61850 Edition 2
Many parts of the IEC 61850 standard have now been released as the second edition. This
offers some significant enhancements including:
• Improved interoperability
• Many new logical nodes
• Better defined testing; it is now possible to perform off-line testing and simulation of
functions
Edition 2 implementation requires use of version 3.2 of the IEC 61850 configurator, which is
installed with version 1.2 of MiCOM S1 Agile.
7.6.12.1 Backward Compatibility
IEC61850 system - backward compatibility
An Edition 1 relay can operate with an Edition 2 IEC 61850 system, provided that the Edition
1 relays do not subscribe to GOOSE messages with data objects or data attributes which are
only available in Edition 2.
The following figure explains this concept:
SC
P746/EN SC/J43
SCADA Communications
(SC) 13-78
MiCOM P40 Agile P746
Ed2
MMS
IED1
IED2
IED3
C
C
L/ R
C
Ed1
Ed1
Ed2
GOOSE
BAY
Ed1 devices in Ed2 system:
 GOOSE OK
 MMS OK
 TOOLS (SCL files) OK
V01056
Figure 18: Edition 2 System - Backward Compatibility
An Edition 2 relay cannot normally operate within an Edition 1 IEC 61850 system. An Edition
2 relay can work for GOOSE messaging in a mixed system, providing the client is compatible
with Edition 2.
Ed1
MMS
IED1
IED2
IED3
C
L/ R
C
C
Ed1
Ed1
Ed2
GOOSE
SC
Ed1 devices in Ed2 system:
 GOOSE OK
 MMS Not OK
 TOOLS (SCL files) Not OK
BAY
V01057
Figure 19: Edition 1 System - Forward Compatibility Issues
7.6.12.2 Edition-2 Common Data Classes
The following common data classes (CDCs) are new to Edition 2 and therefore should not be
used in GOOSE control blocks in mixed Edition 1 and Edition 2 systems
• Histogram (HST)
• Visible string status (VSS)
• Object reference setting (ORG)
SCADA Communications
P746/EN SC/J43
MiCOM P40 Agile P746
(SC) 13-79
• Controllable enumerated status (ENC)
• Controllable analogue process value (APC)
• Binary controlled analogue process value (BAC)
• Enumerated status setting (ENG)
• Time setting group (TSG)
• Currency setting group (CUG)
• Visible string setting (VSG)
• Curve shape setting (CSG)
Of these, only ENS and ENC types are available from a MiCOM P40 relay when publishing
GOOSE messages, so Data Objects using these Common Data Classes should not be
published in mixed Edition 1 and Edition 2 systems.
For compatibility between Edition 1 and Edition 2 relays, SCL files using SCL schema
version 2.1 must be used. For a purely Edition 2 system, use the schema version 3.1.
7.6.12.3 Standby Protection Redundancy
With digital substation architectures, measurements can be shared freely on the process bus
across the substation and between different devices without any additional wiring. This is
because there are no longer any electrical connections to instruments transformers that
restrict the location of relays.
The new IEC 61850 Edition 2 test modes enable the introduction of standby protection relays
at any location within the substation, which has access to both station and process buses. In
the case of failure, these devices can temporarily replace the protection functions inside
other relays.
MPx
MP1
MP2
Standby
BAY(S)
MP1
MP2
BAY1
BAY N
Station/Process Bus
Yard
Yard
SC MU1
MU1
SC MU2
MU2
SC MU1
MU1
SC MU2
MU2
V01059
Figure 20: Example of Standby IED
See the example below. If a failure occurs in the Bay 1 protection relay (MP2), we could
disable this device and activate a standby protection relay to replace its functionality.
SC
P746/EN SC/J43
SCADA Communications
(SC) 13-80
MiCOM P40 Agile P746
MP2
MP1
MP2
Standby
BAY(S)
MP1
(1)
MP2
BAY1
(5)
BAY N
(2)
Station/Process Bus
(4)
Yard
Test
Device
Yard
SC MU1
MU1
SC MU2
MU2
SC MU1
MU1
SC MU2
MU2
V01060
Figure 21: Standby IED Activation Process
The following sequence would occur under this scenario:
1. During the installation phase, a spare standby relay is installed in the substation. This
can remain inactive, until it is needed to replace functions in one of several bays. The
device is connected to the process bus, but does not have any subscriptions enabled.
2. If a failure occurs (in this example, bay 1), first isolate the faulty device by disabling its
process bus and station bus interfaces. You do this by turning off the attached network
interfaces.
3. Retrieve the configuration that the faulty device normally uses, and load this into the
standby redundant relay.
4. Place the relay into the "Test Blocked" mode, as defined in IEC 61850-7-4 Edition
Two. This allows test signals to be injected into the network, which will check that the
configuration is correct. GOOSE signals issued by the device will be flagged as "test"
so that subscribing switchgear controllers know not to trip during this testing. In this
way the protection can be tested all the way up to the switchgear control merging units
without having to operate primary circuit breakers, or by carrying out any secondary
injection.
5. Take the standby relay out of "Test-Blocked" mode and activate it so that it now
replaces the protection functions that were disabled from the initial device failure.
The standby relay reduces downtime in the case of device failure, as protection functions
can be restored quickly before the faulted device is replaced.
SC
SCADA Communications
P746/EN SC/J43
MiCOM P40 Agile P746
8
(SC) 13-81
READ ONLY MODE
With IEC 61850 and Ethernet/Internet communication capabilities, security has become an
important issue. For this reason, all relevant GE relays have been adapted to comply with
the latest cyber-security standards.
In addition to this, a facility is provided which allows you to enable or disable the
communication interfaces. This feature is available for products using Courier, IEC 60870-5103, or IEC 61850.
8.1
IEC 60870-5-103 Protocol Blocking
If Read-Only Mode is enabled for RP1 or RP2 with IEC 60870-5-103, the following
commands are blocked at the interface:
• INF16 auto-recloser on/off (ASDU20)
• INF17 teleprotection on/off (ASDU20)
• INF18 protection on/off (ASDU20)
• INF19 LED reset (ASDU20)
• private INFs e.g CB open/close, Control Inputs (ASDU20)
The following commands are still allowed:
• Poll Class 1 (Read spontaneous events)
• Poll Class 2 (Read measurands)
• GI sequence (ASDU7 'Start GI', Poll Class 1)
• Transmission of Disturbance Records sequence (ASDU24, ASDU25, Poll Class 1)
• Time Synchronisation (ASDU6)
• General Commands (ASDU20), namely:




INF23 activate characteristic 1
INF24 activate characteristic 2
INF25 activate characteristic 3
INF26 activate characteristic 4
Note:
8.2
For IEC 60870-5-103, Read Only Mode function is different from the existing
Command block feature.
Courier Protocol Blocking
If Read-Only Mode is enabled for RP1 or RP2 with Courier, the following commands are
blocked at the interface:
• All setting changes
• Reset Indication (Trip LED) command
• Operate Control Input commands
• CB operation commands
• Auto-reclose operation commands
• Reset demands / thermal etc... command
• Clear event / fault / maintenance / disturbance record commands
• Test LEDs & contacts commands
The following commands are still allowed:
• Read settings, statuses, measurands
• Read records (event, fault, disturbance)
SC
P746/EN SC/J43
(SC) 13-82
SCADA Communications
MiCOM P40 Agile P746
• Time Synchronisation
• Change active setting group
8.3
IEC 61850 Protocol Blocking
If Read-Only Mode is enabled for the Ethernet interfacing with IEC 61850, the following
commands are blocked at the interface:
• All controls, including:
 Enable/disable protection
 Operate Control Inputs
 CB operations (Close/Trip, Lock)
 Reset LEDs
The following commands are still allowed:
• Read statuses, measurands
• Generate reports
• Extract disturbance records
• Time synchronisation
• Change active setting group
8.4
Read-only Settings
The following settings are available for enabling or disabling Read Only Mode.
• RP1 Read Only
• RP2 Read Only (only for products that have RP2)
• NIC Read Only (where Ethernet is available)
8.5
Read-only DDB Signals
The remote read only mode is also available in the PSL using three dedicated DDB signals:
• RP1 Read Only
• RP2 Read Only (only for products that have RP2)
• NIC Read Only (where Ethernet is available)
Using the PSL, these signals can be activated by opto-inputs, Control Inputs and function
keys if required.
SC
SCADA Communications
P746/EN SC/J43
MiCOM P40 Agile P746
9
(SC) 13-83
TIME SYNCHRONISATION
In modern protection schemes it is necessary to synchronise the relay's real time clock so
that events from different devices can be time stamped and placed in chronological order.
This is achieved in various ways depending on the chosen options and communication
protocols.
• Using the IRIG-B input (if fitted)
• Using the SNTP time protocol (for Ethernet IEC 61850 versions)
• Using IEEE 1588 Precision Time Protocol (PTP)
• By using the time synchronisation functionality inherent in the data protocols
9.1
Demodulated IRIG-B
IRIG stands for Inter Range Instrumentation Group, which is a standards body responsible
for standardising different time code formats. There are several different formats starting with
IRIG-A, followed by IRIG-B and so on. The letter after the "IRIG" specifies the resolution of
the time signal in pulses per second (PPS). IRIG-B, the one which we use has a resolution of
100 PPS. IRIG-B is used when accurate time-stamping is required.
The following diagram shows a typical GPS time-synchronised substation application. The
satellite RF signal is picked up by a satellite dish and passed on to receiver. The receiver
receives the signal and converts it into time signal suitable for the substation network. Relays
in the substation use this signal to govern their internal clocks and event recorders.
GPS satellite
GPS time signal
IRIG-B
Satellite dish
Receiver
IED
IED
IED
V01040
Figure 22: GPS Satellite Timing Signal
The IRIG-B time code signal is a sequence of one second time frames. Each frame is split
up into ten 100 mS slots as follows:
• Time-slot 1: Seconds
• Time-slot 2: Minutes
• Time-slot 3: Hours
• Time-slot 4: Days
• Time-slot 5 and 6: Control functions
• Time-slots 7 to 10: Straight binary time of day
The first four time-slots define the time in BCD (Binary Coded Decimal). Time-slots 5 and 6
are used for control functions, which control deletion commands and allow different data
SC
P746/EN SC/J43
(SC) 13-84
SCADA Communications
MiCOM P40 Agile P746
groupings within the synchronisation strings. Time-slots 7-10 define the time in SBS (Straight
Binary Second of day).
9.1.1
IRIG-B Implementation
Depending on the chosen hardware options, the product can be equipped with an IRIG-B
input for time synchronisation purposes. The IRIG-B interface is implemented either on a
dedicated card, or together with other communication functionality such as Ethernet. The
IRIG-B connection is presented by a connector is a BNC connector. IRIG-B signals are
usually presented as an RF-modulated signal. There are two types of input to our IRIG-B
boards: demodulated or modulated. A board that accepts a demodulated input is used where
the IRIG-B signal has already been demodulated by another device before being fed to the
IED. A board that accepts a modulated input has an on-board demodulator.
To set the device to use IRIG-B, use the setting IRIG-B Sync cell in the DATE AND TIME
column.
The IRIG-B status can be viewed in the IRIG-B Status cell in the DATE AND TIME column.
9.2
SNTP
SNTP is used to synchronise the clocks of computer systems over packet-switched,
variable-latency data networks, such as IP. SNTP can be used as the time synchronisation
method for models using IEC 61850 over Ethernet.
The device is synchronised by the main SNTP server. This is achieved by entering the IP
address of the SNTP server into the IED using the IEC 61850 Configurator software
described in the settings application software manual. A second server is also configured
with a different IP address for backup purposes.
This function issues an alarm when there is a loss of time synchronisation on the SNTP
server. This could be because there is no response or no valid clock signal.
The HMI menu does not contain any configurable settings relating to SNTP, as the only way
to configure it is using the IEC 61850 Configurator. However it is possible to view some
parameters in the COMMUNICATIONS column under the sub-heading SNTP parameters.
Here you can view the SNTP server addresses and the SNTP poll rate in the cells SNTP
Server 1, SNTP Server 2 and SNTP Poll rate respectively.
The SNTP time synchronisation status is displayed in the SNTP Status cell in the DATE
AND TIME column.
9.2.1
Loss of SNTP Server Signal Alarm
This function issues an alarm when there is a loss of time synchronization on the SNTP
server. It is issued when the SNTP sever has not detected a valid time synchronisation
response within its 5 second window. This is because there is no response or no valid clock.
The alarm is mapped to IEC 61850.
9.3
IEEE 1588 Precision Time Protocol
The MiCOM P40 modular products support the IEEE C37.238 (Power Profile) of IEEE 1588
Precision Time Protocol (PTP) as a slave-only clock. This can be used to replace or
supplement IRIG-B and SNTP time synchronisation so that the IED can be synchronised
using Ethernet messages from the substation LAN without any additional physical
connections being required.
SC
A dedicated DDB signal (PTP Failure) his provided to indicate failure of failure of PTP.
9.3.1
Accuracy and Delay Calculation
A time synchronisation accuracy of within 5 ms is possible. Both peer-to-peer or end-to-end
mode delay measurement can be used.
In peer-to-peer mode, delays are measured between each link in the network and are
compensated for. This provides greater accuracy, but requires that every device between the
Grand Master and Slaves supports the peer-to-peer delay measurement.
SCADA Communications
P746/EN SC/J43
MiCOM P40 Agile P746
(SC) 13-85
In end-to-end mode, delays are only measured between each Grand Master and Slave. The
advantage of this mode is that the requirements for the switches on the network are lower;
they do not need to independently calculate delays. The main disadvantage is that more
inaccuracy is introduced, because the method assumes that forward and reverse delays are
always the same, which may not always be correct.
When using end-to-end mode, the relay can be connected in a ring or line topology using
RSTP or Self Healing Protocol without any additional Transparent Clocks. But because the
IED is a slave-only device, additional inaccuracy is introduced. The additional error will be
less than 1ms for a network of eight devices.
Grand Master
PTP Aware Network
RSTP Network
Figure 23: Timing Error using Ring or Line Topology
9.3.2
PTP Domains
PTP traffic can be segregated into different domains using Boundary Clocks. These allow
different PTP clocks to share the same network while maintaining independent
synchronisation within each grouped set.
9.4
Time Synchronsiation using the Communication Protocols
All communication protocols have in-built time synchronisation mechanisms. If an external
time synchronisation mechanism such as IRIG-B, SNTP, or IEEE 1588 PTP is not used to
synchronise the devices, the time synchronisation mechanism within the relevant serial
protocol is used. The real time is usually defined in the master station and communicated to
the relevant relays via one of the rear serial ports using the chosen protocol. It is also
possible to define the time locally using settings in the DATE AND TIME column.
The time synchronisation for each protocol is described in the relevant protocol description
section.
SC
P746/EN SC/J43
(SC) 13-86
SC
SCADA Communications
MiCOM P40 Agile P746
Symbols and Glossary
P746/EN SG/J43
MiCOM P40 Agile P746
(SG) 14-1
SYMBOLS AND GLOSSARY
Hardware Suffix:
Software Version:
M
91
SG
P746/EN SG/J43
(SG) 14-2
SG
Symbols and Glossary
MiCOM P40 Agile P746
Symbols and Glossary
P746/EN SG/J43
MiCOM P40 Agile P746
(SG) 14-3
Logic Symbols used
Symbols
&
Σ
τ
<
>
1
52a
52b
89a
89b
ACSI
BAR
BN>
BU
C/O
CB
CB Aux.
CBF
CLP
CS
CT
CTRL.
CTS
CZ
DDB
DEF
Df/dt
Dly
DR
DT
DZ
Explanation
Logical “AND”:
Used in logic diagrams to show an AND-gate function.
“Sigma”:
Used to indicate a summation, such as cumulative current interrupted.
“Tau”:
Used to indicate a time constant, often associated with thermal characteristics.
Less than:
Used to indicate an “under” threshold, such as undercurrent (current dropout).
Greater than:
Used to indicate an “over” threshold, such as overcurrent (current overload).
Logical “OR”:
Used in logic diagrams to show an OR-gate function.
A circuit breaker closed auxiliary contact:
The contact is in the same state as the breaker primary contacts.
A circuit breaker open auxiliary contact:
The contact is in the opposite state to the breaker primary contacts.
An Isolator closed auxiliary contact:
The contact is in the same state as the breaker primary contacts.
An Isolator open auxiliary contact:
The contact is in the opposite state to the breaker primary contacts.
Abstract Communication Service Interface:
In IEC 61850, the ACSI provides abstract definitions of a hierarchical data model and the services that operate on the
data.
Block auto-reclose signal.
Neutral over susceptance protection element:
Reactive component of admittance calculation from neutral current and residual voltage.
Backup:
Typically, a back-up protection element.
A changeover contact having normally closed and normally open connections:
Often called a “form C” contact.
Circuit breaker.
Circuit breaker auxiliary contacts:
Indication of the breaker open/closed status.
Circuit breaker failure protection.
Cold load pick-up.
Check synchronism.
Current transformer.
Abbreviation of “Control”:
As used for the Control Inputs function.
Current transformer supervision:
To detect CT input failure.
Abbreviation of “Check Zone”:
Zone taking into account only the feeders.
Digital data bus within the programmable scheme logic:
A logic point that has a zero or 1 status. DDB signals are mapped in logic to customize the relay’s operation.
Directional earth fault protection:
A directionalised ground fault aided scheme.
Rate of change of frequency protection (ROCOF).
Time delay.
Abbreviation of “Disturbance Record”
Abbreviation of “Definite Time”:
An element which always responds with the same constant time delay on operation.
Abbreviation of “Dead Zone”:
Area between a CT and an open breaker or an open isolator.
SG
P746/EN SG/J43
Symbols and Glossary
(SG) 14-4
Symbols
E/F
F<
F>
FLC
Flt.
FN
Fwd.
GN>
Gnd.
GOOSE
GRP.
GSE
HMI
I
I∧
I/O
I/P
I<
I>
I>1
I>2
I>3
I>4
SG
I>BB
I>DZ
I0
I1
I2
I2>
I2pol
IA
MiCOM P40 Agile P746
Explanation
Earth fault:
Directly equivalent to ground fault.
An underfrequency element:
Could be labelled 81U in ANSI terminology.
An overfrequency element:
Could be labelled 81O in ANSI terminology.
Full load current:
The nominal rated current for the circuit.
Abbreviation of “Fault”:
Typically used to indicate faulted phase selection.
Function.
Indicates an element responding to a flow in the “Forward” direction.
Neutral over conductance protection element:
Real component of admittance calculation from neutral current and residual voltage.
Abbreviation of “Ground”:
Used in distance settings to identify settings that relate to ground (earth) faults.
Generic Object Oriented Substation Event:
In IEC 61850, a specific definition of a type of generic substation event, for peer-peer communication.
Abbreviation of “Group”:
Typically, an alternative setting group.
Generic Substation Event:
In IEC 61850, the generic substation event model provides the possibility for a fast and reliable system-wide
distribution of input and output data values (peer-peer communication).
Human Machine Interface:
The graphical user interface of the control system.
Current.
Current raised to a power:
Such as when breaker statistics monitor the square of ruptured current squared
(∧ power = 2).
Abbreviation of “Inputs and Outputs”:
Used in connection with the number of optocoupled inputs and output contacts within the relay.
Abbreviation of “Input”.
An undercurrent element:
Responds to current dropout.
An overcurrent element:
Detects phase faults; Optionally used by the 50BF protection.
First stage of phase overcurrent protection:
Could be labelled 51-1 in ANSI terminology.
Second stage of phase overcurrent protection:
Could be labelled 51-2 in ANSI terminology.
Third stage of phase overcurrent protection:
Could be labelled 51-3 in ANSI terminology.
Fourth stage of phase overcurrent protection:
Could be labelled 51-4 in ANSI terminology.
Minimum pick-up phase threshold for the local trip order confirmation.
Minimum pick-up phase threshold for the Dead Zone protection.
Zero sequence current:
Equals one third of the measured neutral/residual current.
Positive sequence current.
Negative sequence current.
Negative sequence overcurrent protection (NPS element).
Negative sequence polarizing current.
Phase A current:
Might be phase L1, red phase. or other, in customer terminology.
Symbols and Glossary
P746/EN SG/J43
MiCOM P40 Agile P746
Symbols
IB
IbiasPh> Cur.
IC
ID
ID>1
ID>2
IDCZ>2
IDMT
IDN>1
IDN>2
IDNCZ>2
IDZ
IED
In
IN
IN>
IN>1
IN>2
IN>BB
IN>DZ
Inh
Inst.
ISEF>
K1
K2
KCZ
KN1
KN2
KNCZ
KZN
LCD
LD
LED
MCB
MICS
MMS
(SG) 14-5
Explanation
Phase B current:
Might be phase L2, yellow phase. or other, in customer terminology.
SDEF blocking bias current threshold.
Phase C current:
Might be phase L3, blue phase. or other, in customer terminology.
Abbreviation of “Identifier”:
Often a label used to track a software version installed.
Minimum pick-up phase circuitry fault threshold.
Minimum pick-up differential phase element for all the zones.
Minimum pick-up differential phase element for the Check Zone.
Inverse definite minimum time:
A characteristic whose trip time depends on the measured input (e.g. current) according to an inverse-time curve.
Minimum pick-up neutral circuitry fault threshold.
Minimum pick-up differential neutral element for all the zones.
Minimum pick-up differential neutral element for the Check Zone.
Minimum pick-up differential neutral element for the Check Zone.
Intelligent Electronic Device:
MiCOM relay
The rated nominal current of the relay:
Software selectable as 1 amp or 5 amps to match the line CT input.
Neutral current, or residual current:
This results from an internal summation of the three measured phase currents.
A neutral (residual) overcurrent element:
Detects earth/ground faults.
First stage of ground overcurrent protection:
Could be labelled 51N-1 in ANSI terminology.
Second stage of ground overcurrent protection:
Could be labelled 51N-2 in ANSI terminology.
Minimum pick-up neutral threshold for the local trip order confirmation.
Minimum pick-up neutral threshold for the Dead Zone protection.
An inhibit signal.
An element with “instantaneous” operation:
i.e. having no deliberate time delay.
Sensitive earth fault overcurrent element.
Slope of the phase circuitry fault function.
Slope of the differential phase element for all the zones.
Slope of the differential phase element for the Check Zone.
Slope of the neutral circuitry fault function.
Slope of the differential neutral element for all the zones.
Slope of the differential neutral element for the Check Zone.
The residual compensation factor:
Ensuring correct reach for ground distance elements.
Liquid crystal display:
The front-panel text display on the relay.
Abbreviation of “Level Detector”:
An element responding to a current or voltage below its set threshold.
Light emitting diode:
Bicolour: Red/black or green/black or orange/black indicator on the relay front-panel.
Tricolour: Red/orange/green/black indicator on the relay front-panel.
A “miniature circuit breaker”:
Used instead of a fuse to protect VT secondary circuits.
Model Implementation Conformance Specification:
Defines the IEC 61850 data model implemented in an IED.
Manufacturing Message Specification:
A protocol used to transport the data of IEC 61850 across an Ethernet network.
SG
P746/EN SG/J43
Symbols and Glossary
(SG) 14-6
Symbols
N
N/A
N/C
N/O
NIC
NPS
NVD
NXT
o
O/P
Opto
P1
P2
PCB
Ph
PICS
PN>
Pol
PSL
Qx
R
R Gnd.
RBN
RBPh
RCA
SG
RCT
REF
Rev.
RMS
RP
Rx
S1
MiCOM P40 Agile P746
Explanation
Indication of “Neutral” involvement in a fault:
i.e. a ground (earth) fault.
Not applicable.
A normally closed or “break” contact:
Often called a “form B” contact.
A normally open or “make” contact:
Often called a “form A” contact.
Network Interface Card:
i.e. the Ethernet card of the IED
Negative phase sequence.
Neutral voltage displacement:
Equivalent to residual overvoltage protection.
Abbreviation of “Next”:
In connection with hotkey menu navigation.
A small circle on the input or output of a logic gate:
Indicates a NOT (invert) function.
Abbreviation of “output”.
An optocoupled logic input:
Alternative terminology: binary input.
Used in IEC terminology to identify the primary CT terminal polarity:
Replace by a dot when using ANSI standards.
Used in IEC terminology to identify the primary CT terminal polarity:
The non-dot terminal.
Printed circuit board.
Abbreviation of “Phase”:
Used in distance settings to identify settings that relate to phase-phase faults.
Protocol Implementation Conformance Specification:
Defines the IEC 61850 services implemented in an IED, with reference to the ACSI.
Wattmetric earth fault protection:
Calculated using residual voltage and current quantities.
Abbreviation of “Polarizing”:
Typically, the polarizing voltage used in making directional decisions.
Programmable scheme logic:
The part of the relay’s logic configuration that can be modified by the user, using the graphical editor within S1 Agile
software.
Isolator number x (from 1 to 6).
A resistance.
A distance zone resistive reach setting:
Used for ground (earth) faults.
Lead burden for the neutral.
Lead burden for the phases.
Abbreviation of “Relay Characteristic Angle”:
The centre of the directional characteristic.
Current Transformer secondary resistance.
Restricted earth fault protection.
Indicates an element responding to a flow in the “reverse” direction.
The equivalent a.c. current:
Taking into account the fundamental, plus the equivalent heating effect of any harmonics. Abbreviation of “root
mean square”.
Abbreviation of “Rear Port”:
The communication ports on the rear of the relay.
Abbreviation of “Receive”:
Typically used to indicate a communication receive line/pin.
Used in IEC terminology to identify the secondary CT terminal polarity:
Replace by a dot when using ANSI standards.
Symbols and Glossary
P746/EN SG/J43
MiCOM P40 Agile P746
Symbols
S2
SCL
SCSM
SDEF
SEF
SSD
T
TCS
TD
TE
TMS
Tx
V
V<
V<1
V<2
V>
V>1
V>2
V0
V1
V2
V2pol
VA
VB
VC
VCO
Vk
Vn
VN
VN>1
VN>2
Vres.
VT
VTS
Vx
YN>
Z0
(SG) 14-7
Explanation
Used in IEC terminology to identify the secondary CT terminal polarity:
The non-dot terminal.
Substation Configuration Language:
In IEC 61850, the definition of the configuration files.
Specific Communication Service Mappings:
In IEC 61850, the SCSMs define the actual information exchange mechanisms currently used (e.g. MMS).
Sensitive Differential Earth Fault Protection.
Sensitive Earth Fault Protection.
Solid State Device
A time delay.
Trip circuit supervision.
The time dial multiplier setting:
Applied to inverse-time curves (ANSI/IEEE).
A standard for measuring the width of a relay case:
One inch = 5TE units.
The time multiplier setting applied to inverse-time curves (IEC).
Abbreviation of “Transmit”:
Typically used to indicate a communication transmit line/pin.
Voltage.
An undervoltage element.
First stage of undervoltage protection:
Could be labelled 27-1 in ANSI terminology.
Second stage of undervoltage protection:
Could be labelled 27-2 in ANSI terminology.
An overvoltage element.
First stage of overvoltage protection:
Could be labelled 59-1 in ANSI terminology.
Second stage of overvoltage protection:
Could be labelled 59-2 in ANSI terminology.
Zero sequence voltage:
Equals one third of the measured neutral/residual voltage.
Positive sequence voltage.
Negative sequence voltage.
Negative sequence polarizing voltage.
Phase A voltage:
Might be phase L1, red phase. or other, in customer terminology.
Phase B voltage:
Might be phase L2, yellow phase. or other, in customer terminology.
Phase C voltage:
Might be phase L3, blue phase. or other, in customer terminology.
Voltage controlled overcurrent element.
IEC knee point voltage of a current transformer.
The rated nominal voltage of the relay:
To match the line VT input.
Neutral voltage displacement or residual voltage.
First stage of residual (neutral) overvoltage protection.
Second stage of residual (neutral) overvoltage protection.
Neutral voltage displacement or residual voltage.
Voltage transformer.
Voltage transformer supervision:
To detect VT input failure.
An auxiliary supply voltage:
Typically the substation battery voltage used to power the relay.
Neutral overadmittance protection element:
Non-directional neutral admittance protection calculated from neutral current and residual voltage.
Zero sequence impedance.
SG
P746/EN SG/J43
Symbols and Glossary
(SG) 14-8
MiCOM P40 Agile P746
Symbols
Z1
Z2
SG
Explanation
Positive sequence impedance.
Negative sequence impedance.
Symbols and Glossary
P746/EN SG/J43
MiCOM P40 Agile P746
(SG) 14-9
Logic Timers
Logic
Symbols
Explanation
Time Chart
Delay on pick-up timer, t
Delay on drop-off timer, t
Delay on pick-up/drop-off timer
Pulse timer
Pulse pick-up falling edge
Pulse pick-up raising edge
Latch
SG
P746/EN SG/J43
Symbols and Glossary
(SG) 14-10
Logic
Symbols
MiCOM P40 Agile P746
Explanation
Dwell timer
Straight (non latching):
Hold value until input reset signal
SG
Time Chart
Installation
P746/EN IN/J43
MiCOM P40 Agile P746
(IN) 15-1
INSTALLATION
Hardware Suffix:
M
Software Version:
91
IN
P746/EN IN/J43
(IN) 15-2
IN
Installation
MiCOM P40 Agile P746
Installation
MiCOM P40 Agile P746
P746/EN IN/J43
(IN) 15-3
CONTENTS
1
HANDLING THE GOODS
5
1.1
Receipt of Goods
5
1.2
Unpacking the Goods
5
1.3
Storing the Goods
5
1.4
Dismantling the Goods
5
2
MOUNTING THE DEVICE
6
2.1
Panel Mounting
6
2.2
Rack Mounting
6
3
CABLES AND CONNECTORS
8
3.1
Terminal Blocks
8
3.2
Power Supply Connections
9
3.3
Earth Connection
9
3.4
Current Transformers
9
3.5
Voltage Transformer Connections
10
3.6
Watchdog Connections
10
3.7
EIA(RS)485 and K-BUS Connections
10
3.8
IRIG-B Connections
10
3.9
Opto-input Connections
10
3.10
Output Relay Connections
11
3.11
Ethernet Metallic Connections
11
3.12
USB Connection
11
3.13
Fibre Communication Connections (when applicable)
11
4
MICOM P746
12
5
EXTERNAL CONNECTION DIAGRAMS
15
IN
P746/EN IN/J43
(IN) 15-4
Installation
MiCOM P40 Agile P746
FIGURES
IN
Figure 1: Rack mounting of relays
7
Figure 2: Terminal block types
8
Figure 3: P746 (80TE) hardware description
12
Figure 4: P746 (80TE) rear view
13
Figure 6: P746 (80TE) rear view
14
Installation
P746/EN IN/J43
MiCOM P40 Agile P746
1
(IN) 15-5
HANDLING THE GOODS
Our products are of robust construction but require careful treatment before installation on
site. This section discusses the requirements for receiving and unpacking the goods, as well
as associated considerations regarding product care and personal safety.
Before carrying out any work on the equipment, the user should be
familiar with the contents of the Safety chapter of this manual.
1.1
Receipt of Goods
On receipt, ensure the correct product has been delivered. Unpack the product immediately
to ensure there has been no external damage in transit. If the product has been damaged,
make a claim to the transport contractor and notify us promptly.
For products not intended for immediate installation, repack them in their original delivery
packaging.
1.2
Unpacking the Goods
When unpacking and installing the product, take care not to damage any of the parts and
make sure that additional components are not accidentally left in the packing or lost. Do not
discard any CDROMs or technical documentation (where included). These should
accompany the unit to its destination substation and put in a dedicated place.
The site should be well lit to aid inspection, clean, dry and reasonably free from dust and
excessive vibration. This particularly applies where installation is being carried out at the
same time as construction work.
1.3
Storing the Goods
If the unit is not installed immediately, store it in a place free from dust and moisture in its
original packaging. Keep any dehumidifier bags included in the packing. The dehumidifier
crystals lose their efficiency if the bag is exposed to ambient conditions. Restore the crystals
before replacing it in the carton. Ideally regeneration should be carried out in a ventilating,
circulating oven at about 115°C. Bags should be placed on flat racks and spaced to allow
circulation around them. The time taken for regeneration will depend on the size of the bag.
If a ventilating, circulating oven is not available, when using an ordinary oven, open the door
on a regular basis to let out the steam given off by the regenerating silica gel.
On subsequent unpacking, make sure that any dust on the carton does not fall inside. Avoid
storing in locations of high humidity. In locations of high humidity the packaging may become
impregnated with moisture and the dehumidifier crystals will lose their efficiency.
The device can be stored between –25º to +70ºC for unlimited periods or between -40°C to +
85°C for up to 96 hours (see technical specifications).
To avoid deterioration of electrolytic capacitors, power up units that are stored in a deenergised state once a year, for one hour continuously.
1.4
Dismantling the Goods
If you need to dismantle the device, always observe standard ESD (Electrostatic Discharge)
precautions. The minimum precautions to be followed are as follows:
• Use an antistatic wrist band earthed to a suitable earthing point.
• Avoid touching the electronic components and PCBs.
IN
P746/EN IN/J43
Installation
(IN) 15-6
2
MiCOM P40 Agile P746
MOUNTING THE DEVICE
The products are dispatched either individually or as part of a panel or rack assembly.
Individual products are normally supplied with an outline diagram showing the dimensions for
panel cut-outs and hole centres.
The products are designed so the fixing holes in the mounting flanges are only accessible
when the access covers are open.
If you use a P991 or MMLG test block with the product, when viewed from the front, position
the test block on the right-hand side of the associated product. This minimises the wiring
between the product and test block, and allows the correct test block to be easily identified
during commissioning and maintenance tests.
2.1
Panel Mounting
Panel-mounted devices are flush mounted into panels using M4 SEMS Taptite self-tapping
screws with captive 3 mm thick washers (also known as a SEMS unit).
Note:
Do not use conventional self-tapping screws, because they have larger
heads and could damage the faceplate.
Alternatively, tapped holes can be used if the panel has a minimum thickness of 2.5mm.
For applications where relays need to be semi-projection or projection mounted, a range of
collars are available.
If several relays are mounted in a single cut-out in the panel, mechanically group them
horizontally or vertically into rigid assemblies before mounting in the panel.
Note:
2.2
Do not fasten products with pop rivets because this makes them difficult to
remove if repair becomes necessary.
Rack Mounting
Panel-mounted variants can also be rack mounted using single-tier rack frames (our part
number FX0021 001), as shown in the figure below. These frames are designed with
dimensions in accordance with IEC 60297 and are supplied pre-assembled ready to use. On
a standard 483 mm (19 inch) rack this enables combinations of case widths up to a total
equivalent of size 80TE to be mounted side by side.
The two horizontal rails of the rack frame have holes drilled at approximately 26 mm
intervals. Attach the products by their mounting flanges using M4 Taptite self-tapping screws
with captive 3 mm thick washers (also known as a SEMS unit).
Note:
Risk of damage to the front cover molding. Do not use conventional selftapping screws, including those supplied for mounting MiDOS products
because they have slightly larger heads.
Once the tier is complete, the frames are fastened into the racks using mounting angles at
each end of the tier.
IN
Installation
P746/EN IN/J43
MiCOM P40 Agile P746
(IN) 15-7
Figure 1: Rack mounting of relays
Relays can be mechanically grouped into single tier (4U) or multi-tier arrangements using the
rack frame. This enables schemes using products from different product ranges to be prewired together prior to mounting.
Use blanking plates to fill any empty spaces. The spaces may be used for installing future
products or because the total size is less than 80TE on any tier. Blanking plates can also be
used to mount ancillary components. The part numbers are as follows:
Case size summation
Blanking plate part number
5TE
GJ2128 001
10TE
GJ2128 002
15TE
GJ2128 003
20TE
GJ2128 004
25TE
GJ2128 005
30TE
GJ2128 006
35TE
GJ2128 007
40TE
GJ2128 008
IN
P746/EN IN/J43
Installation
(IN) 15-8
3
MiCOM P40 Agile P746
CABLES AND CONNECTORS
This section describes the type of wiring and connections that should be used when
installing the device.
Before carrying out any work on the equipment, the user should be
familiar with the contents of the safety section and the ratings on the
equipment rating label.
3.1
Terminal Blocks
The device may use one or more of the terminal block types shown in the following diagram.
The terminal blocks are fastened to the rear panel with screws.
• Heavy duty (HD) terminal blocks for CT and VT circuits
• Medium duty (MD) terminal blocks for the power supply, relay outputs and rear
communications port
• MiDOS terminal blocks for CT and VT circuits
• RTD/CLIO terminal block for connection to analogue transducers (not available for
P746)
Figure 2: Terminal block types
MiCOM products are supplied with sufficient M4 screws for making connections to the rear
mounted terminal blocks using ring terminals, with a recommended maximum of two ring
terminals per terminal.
If required, M4 90° crimp ring terminals can be supplied in three different sizes depending on
wire size. Each type is available in bags of 100.
IN
Installation
P746/EN IN/J43
MiCOM P40 Agile P746
(IN) 15-9
Part number
Insulation colour
0.25 – 1.65mm2 (22 – 16AWG)
Red
ZB9124 900
1.04 – 2.63mm2 (16 – 14AWG)
Blue
Note:
3.2
Wire size
ZB9124 901
IP2x shields and side cover panels may be fitted to provide IP20
ingress protection for MiCOM terminal blocks. The shields and covers
can be attached during installation or retrofitted to upgrade existing
installations. The shields are supplied with four language fitting
instructions, publication number: IP2x-TM-4L-n (where n is the current
issue number). For more information, contact your local sales office or
our worldwide Contact Centre.
Power Supply Connections
These should be wired with 1.5 mm PVC insulated multi-stranded copper wire terminated
with M4 ring terminals.
The wire should have a minimum voltage rating of 300 V RMS.
Caution:
Protect the auxiliary power supply wiring with a maximum 16 A high
rupture capacity (HRC) type NIT or TIA fuse.
3.3
Earth Connection
Every device must be connected to the cubicle earthing bar using the M4 earth terminal.
Use a wire size of at least 2.5 mm2 terminated with a ring terminal.
Due to the physical limitations of the ring terminal, the maximum wire size you can use is 6.0
mm2 using ring terminals that are not pre-insulated. If using pre insulated ring terminals, the
maximum wire size is reduced to 2.63 mm2 per ring terminal. If you need a greater crosssectional area, use two wires in parallel, each terminated in a separate ring terminal.
The wire should have a minimum voltage rating of 300 V RMS.
Note:
3.4
To prevent any possibility of electrolytic action between brass or copper
ground conductors and the rear panel of the product, precautions should be
taken to isolate them from one another. This could be achieved in several
ways, including placing a nickel-plated or insulating washer between the
conductor and the product case, or using tinned ring terminals.
Current Transformers
Current transformers would generally be wired with 2.5 mm2 PVC insulated multi-stranded
copper wire terminated with M4 ring terminals.
Due to the physical limitations of the ring terminal, the maximum wire size you can use is 6.0
mm2 using ring terminals that are not pre-insulated. If using pre insulated ring terminals, the
maximum wire size is reduced to 2.63 mm2 per ring terminal. If you need a greater crosssectional area, use two wires in parallel, each terminated in a separate ring terminal.
The wire should have a minimum voltage rating of 300 V RMS.
Caution:
Current transformer circuits must never be fused.
Note:
If there are CTs present, spring-loaded shorting contacts ensure that the
terminals into which the CTs connect are shorted before the CT contacts are
broken.
IN
P746/EN IN/J43
Installation
(IN) 15-10
MiCOM P40 Agile P746
Note:
3.5
For 5A CT secondaries, we recommend using 2 x 2.5 mm2 PVC insulated
multi-stranded copper wire.
Voltage Transformer Connections
Voltage transformers should be wired with 2.5 mm2 PVC insulated multi-stranded copper
wire terminated with M4 ring terminals.
The wire should have a minimum voltage rating of 300 V RMS.
3.6
Watchdog Connections
These should be wired with 1 mm PVC insulated multi-stranded copper wire terminated with
M4 ring terminals.
The wire should have a minimum voltage rating of 300 V RMS.
3.7
EIA(RS)485 and K-BUS Connections
For connecting the EIA(RS485) / K-Bus ports, use 2-core screened cable with a maximum
total length of 1000 m or 200 nF total cable capacitance.
To guarantee the performance specifications, you must ensure continuity of the screen,
when daisy chaining the connections.
Two-core screened twisted pair cable should be used. It is important to avoid circulating
currents, which can cause noise and interference, especially when the cable runs between
buildings. For this reason, the screen should be continuous and connected to ground at one
end only, normally at the master connection point.
The K-Bus signal is a differential signal and there is no signal ground connection. If a signal
ground connection is present in the bus cable then it must be ignored. At no stage should
this be connected to the cable's screen or to the product’s chassis. This is for both safety
and noise reasons.
A typical cable specification would be:
• Each core: 16/0.2 mm2 copper conductors, PVC insulated
• Nominal conductor area: 0.5 mm2 per core
• Screen: Overall braid, PVC sheathed
3.8
IRIG-B Connections
The IRIG-B input and BNC connector have a characteristic impedance of 50 Ω. It is
recommended that connections between the IRIG-B equipment and the relay are made
using coaxial cable of type RG59LSF with a halogen free, fire retardant sheath.
3.9
Opto-input Connections
These should be wired with 1 mm2 PVC insulated multi-stranded copper wire terminated
with M4 ring terminals.
Each opto-input has a selectable preset ½ cycle filter. This makes the input immune to noise
induced on the wiring.
This can, however slow down the response. If you need to switch off the ½ cycle filter, either
use double pole switching on the input, or screened twisted cable on the input circuit.
Caution:
Protect the auxiliary power supply wiring with a maximum 16 A high
rupture capacity (HRC) type NIT or TIA fuse.
IN
Installation
P746/EN IN/J43
MiCOM P40 Agile P746
3.10
(IN) 15-11
Output Relay Connections
These should be wired with 1 mm PVC insulated multi-stranded copper wire terminated with
M4 ring terminals.
3.11
Ethernet Metallic Connections
If the device has a metallic Ethernet connection, it can be connected to either a 10Base-T or
a 100Base-TX Ethernet hub. Due to noise sensitivity, we recommend this type of connection
only for short distance connections, ideally where the products and hubs are in the same
cubicle. For increased noise immunity, CAT 6 (category 6) STP (shielded twisted pair) cable
and connectors can be used.
The connector for the Ethernet port is a shielded RJ-45. The pin-out is as follows:
Pin
3.12
Signal name
Signal definition
1
TXP
Transmit (positive)
2
TXN
Transmit (negative)
3
RXP
Receive (positive)
4
-
Not used
5
-
Not used
6
RXN
Receive (negative)
7
-
Not used
8
-
Not used
USB Connection
The device has a type B USB socket inside the bottom compartment. A standard USB printer
cable (type A one end, type B the other end) can be used to connect a local PC to the IED.
This cable is the same as that used for connecting a printer to a PC.
3.13
Fibre Communication Connections (when applicable)
The fibre optic port consists of one or two channels using ST type connectors (one for Tx
and one for Rx). The type of fibre used depends on the option selected.
850 nm and 1300 nm multimode systems use 50/125 μm or 62.5/125 μm multimode fibres.
1300 nm and 1550 nm single mode systems use 9/125 μm single mode fibres.
Warning:
NEVER look into optical fibres or optical output connections. Always use
optical power meters to determine operation or signal level.
IN
P746/EN IN/J43
(IN) 15-12
4
IN
Installation
MiCOM P40 Agile P746
MICOM P746
Figure 3: P746 (80TE) hardware description
Installation
P746/EN IN/J43
MiCOM P40 Agile P746
A – IRIG B / Ethernet / COMMS
B – Opto \ high break
C – Opto \ high break
D – Sigma Delta analogue input board
E – Sigma Delta Opto Board
F – Sigma Delta analogue input board
Figure 4: P746 (80TE) rear view
(IN) 15-13
G–
H–
J–
K–
L–
M–
Sigma Delta Opto Board
Relay \ Opto \ high break
Relay \ high break
Relay \ high break
Relay board
Power supply board
IN
P746/EN IN/J43
Installation
(IN) 15-14
MiCOM P40 Agile P746
A – IRIG B / Ethernet / COMMS
B – Opto \ high break
C – Opto \ high break
D – Sigma Delta analogue input board
E – Sigma Delta Opto Board
F – Sigma Delta analogue input board
Figure 5: P746 (80TE) rear view
IN
G–
H–
J–
K–
L–
M–
Sigma Delta Opto Board
Relay \ Opto \ high break
Relay \ high break
Relay \ high break
Relay board
Power supply board
Installation
MiCOM P40 Agile P746
5
P746/EN IN/J43
(IN) 15-15
EXTERNAL CONNECTION DIAGRAMS
Please refer to Appendix B to see the full list of wiring and communication diagrams.
IN
P746/EN IN/J43
(IN) 15-16
IN
Installation
MiCOM P40 Agile P746
Remote HMI
P746/EN HI/J43
MiCOM P40 Agile P746
(HI) 16-1
REMOTE HMI
Hardware Design:
M
Software Version:
91
HI
P746/EN HI/J43
(HI) 16-2
Remote HMI
MiCOM P40 Agile P746
Remote HMI
MiCOM P40 Agile P746
P746/EN HI/J43
(HI) 16-1
CONTENTS
1
INTRODUCTION
3
2
COMMUNICATION SETTINGS
4
2.1
Serial Settings
4
2.2
Ethernet Settings
4
3
SCHEME EDITOR
6
3.1
Principle of Operation
6
3.2
Constraints
10
3.2.1
Creating a New Blank Scheme
11
3.2.2
Creating a Busbar
11
3.2.3
Creating a Busbar Link
11
3.2.4
Creating a Tie Group
11
3.2.5
Creating a Feeder Group
11
3.2.6
Association of Zone for Isolators
12
3.2.7
Edit Options
13
4
DYNAMIC SYNOPTIC
14
4.1
Animation of Scheme
14
4.2
Measurements Data
15
HI
P746/EN HI/J43
(HI) 16-2
HI
Remote HMI
MiCOM P40 Agile P746
Remote HMI
P746/EN HI/J43
MiCOM P40 Agile P746
1
(HI) 16-3
INTRODUCTION
The Remote HMI is an application that is used to define or create a scheme to display the
P746 measured data.
The Remote HMI application operates in two modes:
• Scheme Editor: This mode allows the user to define a scheme for the P746 unit with
the predefined Busbars, Tie Groups and Feeder Groups.
• Dynamic Synoptic: This tool is used to display the P746 measured analogue quantities
and DDB (Digital Data Bus) status information based on the scheme designed in
Scheme Editor mode.
HI
P746/EN HI/J43
(HI) 16-4
2
Remote HMI
MiCOM P40 Agile P746
COMMUNICATION SETTINGS
The Remote HMI application supports communicating with the P746 relay through Serial
COM port and Ethernet Tunneling.
The settings for these communications can be selected before communicating with the P746
in Scheme Editor or Dynamic Synoptic mode.
The selected communication option and their settings are displayed in the left side of the
status bars.
Schemes for Communication Setup:
There are three schemes allowed for Communication Setup:
• Front Serial
• Rear Serial
• Ethernet
To set up the scheme follow the steps below:
1. Choose the scheme from the list then modify the settings.
2. Select Restore Defaults to restore the default values for the selected scheme.
3. Set the Device Address
2.1
Serial Settings
To set up the Serial settings follow the steps below:
1. Select the Serial tab and set the scheme to Front Serial or Rear Serial to
communicate with the P746 through Serial COM port.
2. Set the COM port from the list. Choose the port to which the P746 is connected.
3. Set the Baud Rate to 19200 or 9600.
4. Set the Framing to 10 bit or 11 bit
5. Set the following Transaction Values:
• Busy Hold-off Time
• Busy Count
• Reset Response Time
• Response Time
• Retry Count
• Transmit Delay Time
• Global Transmit Time.
2.2
Ethernet Settings
To set up the Ethernet settings follow the steps below:
1. To set up an Ethernet communication select Ethernet as your scheme then select the
Ethernet tab to reveal the Ethernet settings.
2. Set the IP Address
HI
3. Check the TCP Port Number if a specific Ethernet TCP port has to be used. If this
option is not selected the default Ethernet port 0 is used.
4. If the P746 is connected though a Bay Unit set the Bay Address by selecting Bay
Address.
5. Set the following Transaction Values:
• Busy Hold-off Time
Remote HMI
P746/EN HI/J43
MiCOM P40 Agile P746
(HI) 16-5
• Busy Count
• Reset Response Time
• Response Time
• Retry Count
• Transmit Delay Time
• Global Transmit Time.
HI
P746/EN HI/J43
Remote HMI
(HI) 16-6
3
MiCOM P40 Agile P746
SCHEME EDITOR
The Scheme Editor is used to design the scheme for the P746 relay using the Busbar,
Feeder Group and Tie Group icons.
The main window consists of the following parts:
• Menu Bar
• Toolbar
• Toolbox
• Scheme Design Window
3.1
Principle of Operation
A library of predefined symbols allows the scheme to be created. This library is located in the
toolbox on the left side of the main window. These symbols can be easily dragged and
dropped into the Scheme Window.
The initial drag and drop placement of an object onto the scheme editor page is not possible
if the ‘grey imaginary boundary box’ is touching or overlapping with another object already
placed on the page.
The symbols provided in the toolbox are described below:
Busbar Toolbox:
S. No
Name
1
Busbar Left
3
Busbar Link
Icon
Tie Groups Toolbox:
HI
S. No
Tie Group Name
1
Tie Group 1
2
Tie Group 2
3
Tie Group 3
4
Tie Group 4
5
Tie Group 5
6
Tie Group 6
Tie Group Icon
Remote HMI
P746/EN HI/J43
MiCOM P40 Agile P746
(HI) 16-7
Feeder Groups Toolbox:
S. No
Feeder Group
Name
1
Feeder Group 1
2
Feeder Group 2
3
Feeder Group 3
4
Feeder Group 4
5
Feeder Group 5
Feeder Group Icon
HI
P746/EN HI/J43
Remote HMI
(HI) 16-8
MiCOM P40 Agile P746
S. No
Feeder Group
Name
6
Feeder Group 6
7
Feeder Group 7
8
Feeder Group 8
9
Feeder Group 9
HI
Feeder Group Icon
Remote HMI
P746/EN HI/J43
MiCOM P40 Agile P746
(HI) 16-9
S. No
Feeder Group
Name
10
Feeder Group 10
11
Feeder Group 11
12
Feeder Group 12
13
Feeder Group 13
Feeder Group Icon
HI
P746/EN HI/J43
Remote HMI
(HI) 16-10
HI
3.2
MiCOM P40 Agile P746
S. No
Feeder Group
Name
14
Feeder Group 14
15
Feeder Group 15
16
Feeder Group 16
Feeder Group Icon
Constraints
• The maximum number of Busbars that can be created in the scheme is two.
• Only one Tie group can be created in the scheme.
Remote HMI
P746/EN HI/J43
MiCOM P40 Agile P746
(HI) 16-11
• The initial drag and drop placement of an object onto the scheme editor page is not
possible if the ‘grey imaginary boundary box’ is touching or overlapping with another
object already placed on the page.
• Feeder Group cannot be created before creating at-least one busbar in the scheme.
• The Feeder group and Tie group components cannot be resized.
• The maximum number of Feeder groups that can be created is six in 1 box mode and
18 in 3 box mode.
• If vertical Busbar links are used within a scheme they must be applied to both Busbar
ends. For example, zone 1 and zone 2.
• Objects placed within a scheme must have sufficient space to allow measurements to
be displayed when in dynamic synoptic mode.
• Designing the scheme
3.2.1
Creating a New Blank Scheme
1. Select File > New menu or New icon in the toolbar.
2. Select Scheme Mode to open the Scheme Mode window
3. If the P746 relay is connected, select Relay Connected and press OK. The P746
mode will be retrieved from the P746 and a new scheme will be created.
4. If the relay is not connected select Relay Not Connected, then choose One Box
Mode or Three Box Mode. Click OK to create a new scheme.
3.2.2
Creating a Busbar
1. To create a Busbar, drag and drop the Busbar Left or Busbar Right symbol from the
Busbar Toolbox into the Scheme Window.
2. In the Set Busbar Properties window select BB1 or BB2 option and press Apply to
create the Busbar.
3. To increase the length of the Busbar, click on the endpoint and drag the mouse until
enough Busbar length is achieved.
3.2.3
Creating a Busbar Link
1. To create a Busbar Link, drag and drop the Busbar Link symbol from Busbar
Toolbox into the Scheme Window. A maximum of two Busbar Links are allowed in a
scheme.
3.2.4
Creating a Tie Group
1. Drag and drop the Tie Group symbol from Tie Group toolbox into the Scheme
Window. If the selected Tie Group does not have a CT, it will be created immediately.
2. If the selected Tie Group has one or two CTs, the Tie Group Properties window is
displayed.
3. Select CT for CT1 and CT2 and press APPLY to create the Tie Group.
Note:
3.2.5
Only one Tie Group is allowed in a scheme. Same CTs are not allowed for
CT1 and CT2 for Tie Groups with double CTs.
Creating a Feeder Group
1. Drag and drop the Feeder Group symbol from the Feeder Group Toolbox into the
Scheme Window. The Feeder Group Properties window is displayed.
2. Select the Feeder from the drop down list and press APPLY to create the Feeder
Group.
Note:
The number of Feeder Groups that can be created is restricted to six
in one Box mode and 18 in three Box mode.
HI
P746/EN HI/J43
Remote HMI
(HI) 16-12
3.2.6
MiCOM P40 Agile P746
Association of Zone for Isolators
The Zone information for isolators in Feeder Groups and Tie Groups are associated
dynamically when they are moved nearer to the Busbar.
The following are examples of association of Zone for Isolators in Feeder Groups:
HI
S. No
Description
1
Association of
Feeder Group
with
Single
Isolator Group.
2
Association of
Feeder Group
with
Double
Isolator Group.
Before Association
After Association
Remote HMI
P746/EN HI/J43
MiCOM P40 Agile P746
(HI) 16-13
The following are the examples of association of Zone for Isolators in Tie Groups:
S. No
Description
1
Association of
Tie Group with
Busbar Links.
2
Association of
Tie Group
without Busbar
Links.
3.2.7
Before Association
After Association
Edit Options
There are several edit options within the scheme. Objects can be moved anywhere in the
scheme but only one object can be copied at a time.
Commands
Steps
Move an object
Click on the object, drag and drop into the new
position. Use the arrow keys to move the object.
Copy and paste
Click on the object, select Edit > right click the
mouse and choose Paste Selection. Paste in
the new position.
Add new text
Select the Alphabet character from the tool bar.
Select the location in the scheme for new text to
be placed. The Insert Text dialog box will
appear
Modify text
Select the text object and right click. Choose
Edit Text. The Insert Text box will appear.
Remove an object
Select the object and press Del. To remove all
the objects, select Edit > Clear All.
HI
P746/EN HI/J43
Remote HMI
(HI) 16-14
4
MiCOM P40 Agile P746
DYNAMIC SYNOPTIC
This tool allows you to monitor the electrical components present in the scheme and
analogue values in real time.
In Dynamic Synoptic mode, the main window consists of following parts:
• Menu Bar
• Toolbar
• Scheme Window
• Measurements Window
• Status Bar
4.1
Animation of Scheme
The Dynamic Synoptic polls states of CBs (Circuit Breaker), CTs (Current Transformer) with
their Primary ratios and load currents, CB Bus Coupler and Isolators present in the scheme.
The respective icons are animated based on the states polled from P746 and the load
currents are displayed near each CT. These values are updated periodically with the
information polled from P746 unit connected.
Animation of Current Transformer:
CTS HEALTHY
HI
CTS FAIL
Remote HMI
P746/EN HI/J43
MiCOM P40 Agile P746
(HI) 16-15
Animation of Circuit Breaker:
CB OPEN
CB CLOSED
CB OPEN
AND NOT
READY
CB CLOSED
AND NOT
READY
CB ALARM
Animation of Isolators:
Q OPEN
4.2
Q CLOSED
Q ALARM
Measurements Data
Dynamic Synoptic polls the P746 relay and displays the P746 Mode Configuration,
differential ad bias currents per phase, neutral values of each zone and CZ (Check Zone),
voltages for connected zone, DDB Status information for Protection Status, Trip Status,
Blocked Zone, Trip Zone and Alarm DDB Signals.
HI
P746/EN HI/J43
(HI) 16-16
Remote HMI
MiCOM P40 Agile P746
Zone Measurements:
• In one Box mode, Differential and Bias Currents per phase and neutral values of
Zone1, Zone2 and Check Zone are displayed.
• In three Box mode, Differential and Bias Currents for the Protected phase of Zone1,
Zone2 and Check Zone are displayed.
• The voltage values for connected zone are displayed.
HI
Protection Status:
• This indicates the blocked state of 87BB and 50BF signals.
• The colours used are GREEN for "OK" and RED for "BLOCKED" state.
Trip Status:
• This indicates the trip state of 87BB and 50BF signals.
Remote HMI
P746/EN HI/J43
MiCOM P40 Agile P746
(HI) 16-17
• The colours used are GREEN for "NO TRIP" and "RED" for "TRIPPED" state.
Blocked Zone:
• This indicates which zone is blocked.
• The colours used are GREEN for "OK" and RED for "BLOCKED" state.
Trip Zone:
• This indicates which zone is tripped.
• The colours used are GREEN for "NO TRIP" and "RED" for "TRIPPED" state.
Alarm Signals:
• The active alarms are displayed in the "ALARMS LIST BOX".
• On clicking the button next to this list box, the list of active alarms is displayed.
• The ALARM icon will be in GREEN colour if no alarm is active. If at least 1 alarm is
active then the ALARM icon will be displayed in RED in colour.
HI
P746/EN HI/J43
(HI) 16-18
HI
Remote HMI
MiCOM P40 Agile P746
Cyber Security
P746/EN CS/J43
MiCOM P40 Agile P746
(CS) 17-1
CYBER SECURITY
Hardware Design:
M
Software Design:
91
CS
P746/EN CS/J43
(CS) 17-2
Cyber Security
MiCOM P40 Agile P746
Cyber Security
MiCOM P40 Agile P746
P746/EN CS/J43
(CS) 17-3
CONTENTS
1
OVERVIEW
5
2
THE NEED FOR CYBER SECURITY
6
3
STANDARDS
7
3.1
NERC Compliance
7
3.1.1
CIP 002
8
3.1.2
CIP 003
8
3.1.3
CIP 004
8
3.1.4
CIP 005
8
3.1.5
CIP 006
8
3.1.6
CIP 007
9
3.1.7
CIP 008
9
3.1.8
CIP 009
9
3.2
IEEE 1686-2013
9
4
CYBER-SECURITY IMPLEMENTATION
10
4.1
Initial Setup
10
5
ROLES AND PERMISSIONS
11
5.1
Roles
11
5.2
Permissions
12
6
AUTHENTICATION
14
6.1
Authentication Methods
14
6.2
Bypass
14
6.3
Login
15
6.3.1
Front Panel Login
16
6.3.2
MiCOM S1 Login
16
6.3.3
Warning Banner
16
6.3.4
Login Failed
16
6.4
User Sessions
16
6.5
User Locking Policy
17
6.6
Logout
18
6.6.1
Front Panel Logout
18
6.6.2
MiCOM S1 Logout
19
6.7
Device Users
19
6.8
Password Policy
19
6.9
Change Password
19
6.10
RADIUS
19
6.10.1
RADIUS Users
20
6.10.2
RADIUS Client
20
6.10.3
RADIUS Server Settings
21
CS
P746/EN CS/J43
(CS) 17-4
CS
Cyber Security
MiCOM P40 Agile P746
6.10.4
RADIUS Accounting
21
6.10.5
RADIUS Client-server Validation
21
6.11
Recovery
21
6.11.1
Restore to local Factory Default
21
6.11.2
Password Reset Procedure
22
6.11.3
Access Level DDBs
23
6.12
Disabling Physical Ports
23
6.13
Disabling Logical Ports
24
7
SECURITY EVENT MANAGEMENT
25
7.1
Security Events: Courier
25
7.2
Syslog
26
7.3
Syslog Client
27
7.4
Syslog Functionality
27
Cyber Security
P746/EN CS/J43
MiCOM P40 Agile P746
1
(CS) 17-5
OVERVIEW
In the past, substation networks were traditionally isolated and the protocols and data
formats used to transfer information between devices were more often than not proprietary.
For these reasons, the substation environment was very secure against cyber attacks.The
terms used for this inherent type of security are:
• Security by isolation (if the substation network is not connected to the outside world, it
can’t be accessed from the outside world).
• Security by obscurity (if the formats and protocols are proprietary, it is very difficult, to
interpret them.
The increasing sophistication of protection schemes coupled with the advancement of
technology and the desire for vendor interoperability has resulted in standardization of
networks and data interchange within substations. Today, devices within substations use
standardized protocols for communication. Furthermore, substations can be interconnected
with open networks, such as the internet or corporate-wide networks, which use
standardized protocols for communication. This introduces a major security risk making the
grid vulnerable to cyber-attacks, which could in turn lead to major electrical outages.
Clearly, there is now a need to secure communication and equipment within substation
environments. This chapter describes the security measures that have been put in place for
GE’s range of devices.
Note:
Cyber-security compatible devices do not enforce NERC compliance, they
merely facilitate it. It is the responsibility of the user to ensure that
compliance is adhered to as and when necessary.
CS
P746/EN CS/J43
(CS) 17-6
2
Cyber Security
MiCOM P40 Agile P746
THE NEED FOR CYBER SECURITY
Cyber-security provides protection against unauthorized disclosure, transfer, modification, or
destruction of information and/or information systems, whether accidental or intentional. To
achieve this, there are several security requirements:
• Confidentiality (preventing unauthorized access to information)
• Integrity (preventing unauthorized modification)
• Availability / Authentication (preventing the denial of service and assuring authorized
access to information)
• Non-Repudiation (preventing the denial of an action that took place)
• Traceability/Detection (monitoring and logging of activity to detect intrusion and
analyze incidents)
The threats to cyber security may be unintentional (e.g. natural disasters, human error), or
intentional (e.g. cyber attacks by hackers).
Good cyber security can be achieved with a range of measures, such as closing down
vulnerability loopholes, implementing adequate security processes and procedures and
providing technology to help achieve this.
Examples of vulnerabilities are:
• Indiscretions by personnel (e.g. users keep passwords on their computer)
• Bypassing of controls (e.g. users turn off security measures)
• Bad practice (users do not change default passwords, or everyone uses the same
password to access all substation equipment)
• Inadequate technology (e.g. substation is not firewalled)
Examples of availability issues are:
• Equipment overload, resulting in reduced or no performance
• Expiry of a certificate prevents access to equipment.
To help tackle these issues, standards organizations have produced various standards, by
which compliance significantly reduces the threats associated with lack of cyber security.
CS
Cyber Security
P746/EN CS/J43
MiCOM P40 Agile P746
3
(CS) 17-7
STANDARDS
There are several standards, which apply to substation cyber security. The standards
currently applicable to GE relays are NERC and IEEE1686.
Country
NERC CIP (North American Electric Reliability
Corporation)
BDEW (German Association of Energy and
Water Industries)
Germany
ANSI ISA 99
USA
IEEE 1686
International
IEC 62351
International
ISO/IEC 27002
International
NIST SP800-53 (National Institute of
Standards and Technology)
CPNI Guidelines (Centre for the Protection of
National Infrastructure)
3.1
USA
USA
UK
Framework for the protection of the grid
critical Cyber Assets
Requirements for Secure Control and
Telecommunication Systems
ICS oriented then Relevant for EPU completing
existing standard and identifying new topics
such as patch management
International Standard for substation IED
cyber security capabilities
Power system data and Comm. protocol
Framework for the protection of the grid
critical Cyber Assets
Complete framework for SCADA SP800-82and
ICS cyber security
Clear and valuable good practices for Process
Control and SCADA security
NERC Compliance
The North American Electric Reliability Corporation (NERC) created a set of standards for
the protection of critical infrastructure. These are known as the CIP standards (Critical
Infrastructure Protection). These were introduced to ensure the protection of Critical Cyber
Assets, which control or have an influence on the reliability of North America’s bulk electric
systems.
These standards have been compulsory in the USA for several years now. Compliance
auditing started in June 2007, and utilities face extremely heavy fines for non-compliance.
NERC CIP standards
CIP standard
CIP-002-1 Critical Cyber Assets
CIP-003-1 Security Management Controls
CIP-004-1 Personnel and Training
CIP-005-1 Electronic Security
CIP-006-1 Physical Security
CIP-007-1 Systems Security Management
CIP-008-1 Incident Reporting and Response
Planning
CIP-009-1 Recovery Plans
Description
Define and document the Critical Assets and the Critical Cyber
Assets
Define and document the Security Management Controls
required to protect the Critical Cyber Assets
Define and Document Personnel handling and training required
protecting Critical Cyber Assets
Define and document logical security perimeter where Critical
Cyber Assets reside and measures to control access points and
monitor electronic access
Define and document Physical Security Perimeters within which
Critical Cyber Assets reside
Define and document system test procedures, account and
password management, security patch management, system
vulnerability, system logging, change control and configuration
required for all Critical Cyber Assets
Define and document procedures necessary when Cyber
Security Incidents relating to Critical Cyber Assets are identified
Define and document Recovery plans for Critical Cyber Assets
The following sections provide further details about each of these standards, describing the
associated responsibilities of the utility company and where the relay manufacturer can help
the utilities with the necessary compliance to these standards.
CS
P746/EN CS/J43
Cyber Security
(CS) 17-8
3.1.1
MiCOM P40 Agile P746
CIP 002
CIP 002 concerns itself with the identification of:
• Critical assets, such as overhead lines and transformers
• Critical cyber assets, such as devices that use routable protocols to communicate
outside or inside the Electronic Security Perimeter; or are accessible by dial-up.
Power utility responsibilities:
Create the list of the assets
3.1.2
GE's contribution:
We can help the power utilities to create this asset register
automatically.
We can provide audits to list the Cyber assets
CIP 003
CIP 003 requires the implementation of a cyber security policy, with associated
documentation, which demonstrates the management’s commitment and ability to secure its
Critical Cyber Assets.
The standard also requires change control practices whereby all entity or vendor-related
changes to hardware and software components are documented and maintained.
Power utility responsibilities:
To create a Cyber Security Policy
3.1.3
GE's contribution:
We can help the power utilities to have access control to its
critical assets by providing centralized Access control.
We can help the customer with its change control by
providing a section in the documentation where it describes
changes affecting the hardware and software.
CIP 004
CIP 004 requires that personnel having authorized cyber access or authorized physical
access to Critical Cyber Assets, (including contractors and service vendors), have an
appropriate level of training.
Power utility responsibilities:
To provide appropriate training of its personnel
3.1.4
GE's contribution:
We can provide cyber security training
CIP 005
CIP 005 requires the establishment of an Electronic Security Perimeter (ESP), which
provides:
• The disabling of ports and services that are not required
• Permanent monitoring and access to logs (24x7x365)
• Vulnerability Assessments (yearly at a minimum)
• Documentation of Network Changes
Power utility responsibilities:
To monitor access to the ESP
To perform the vulnerability assessments
To document network changes
Power utility responsibilities:
To monitor access to the ESP
To perform the vulnerability assessments
To document network changes
3.1.5
General Electric's contribution:
To disable all ports not used in the IED
To monitor and record all access to the IED the access at all
access points of the ESP
GE's contribution:
To disable all ports not used in the IED
To monitor and record all access to the IED the access at all
access points of the ESP
CIP 006
CIP 006 states that Physical Security controls, providing perimeter monitoring and logging
along with robust access controls, must be implemented and documented. All cyber assets
used for Physical Security are considered critical and should be treated as such:
CS
Cyber Security
P746/EN CS/J43
MiCOM P40 Agile P746
(CS) 17-9
Power utility responsibilities:
Provide physical security controls and perimeter
monitoring.
Ensure that people who have access to critical
cyber assets don’t have criminal records.
Power utility responsibilities:
Provide physical security controls and perimeter
monitoring.
Ensure that people who have access to critical
cyber assets don’t have criminal records.
3.1.6
GE's contribution:
General Electric cannot provide additional help with this aspect.
General Electric's contribution:
General Electric cannot provide additional help with this aspect.
CIP 007
CIP 007 covers the following points:
• Test procedures
• Ports and services
• Security patch management
• Antivirus
• Account management
• Monitoring
• An annual vulnerability assessment should be performed
Power utility responsibilities:
To provide an incident response team and have
appropriate processes in place
3.1.7
GE's contribution:
Test procedures; We can provide advice and help on testing.
Ports and services; Our devices can disable unused ports and
services
Security patch management; We can provide assistance
Antivirus; We can provide advice and assistance
Account management; We can provide advice and assistance
Monitoring; Our equipment monitors and logs access
CIP 008
CIP 008 requires that an incident response plan be developed, including the definition of an
incident response team, their responsibilities and associated procedures.
Power utility responsibilities:
To provide an incident response team and have
appropriate processes in place.
3.1.8
GE's contribution:
General Electric cannot provide additional help with this
aspect.
CIP 009
CIP 009 states that a disaster recovery plan should be created and tested with annual drills.
Power utility responsibilities:
To implement a recovery plan
3.2
GE's contribution:
To provide guidelines on recovery plans and backup/restore
documentation
IEEE 1686-2013
IEEE 1686-2013 is an IEEE Standard for substation IEDs cyber security capabilities. It
proposes practical and achievable mechanisms to achieve secure operations.
The following features described in this standard apply:
• Passwords are 8 characters long and can contain upper-case, lower-case, numeric
and special characters.
• Passwords are never displayed or transmitted to a user.
• IED functions and features are assigned to different password levels. The assignment
is fixed.
CS
P746/EN CS/J43
(CS) 17-10
Cyber Security
MiCOM P40 Agile P746
• Record of an audit trail listing events in the order in which they occur, held in a circular
buffer.
• Records contain all defined fields from the standard and record all defined function
event types where the function is supported.
• No password defeat mechanism exists. Instead a secure recovery password scheme
is implemented.
• Unused ports (physical and logical) may be disabled.
4
CYBER-SECURITY IMPLEMENTATION
GE devices have always been and will continue to be equipped with state-of-the-art security
measures. Due to the ever-evolving communication technology and new threats to security,
this requirement is not static.
Hardware and software security measures are continuously being developed and
implemented to mitigate the associated threats and risks.
From Software Version 90 onwards, the MiCOM P40 Agile products provide enhanced
security through the following features:
An Authentication, Authorization, Accounting (AAA) Remote Authentication Dial-In User
Service (RADIUS) client that is managed centrally, enables user attribution, provides
accounting of all user activities, and uses secure standards based on strong cryptography for
authentication and credential protection. In other words, this option uses a RADIUS.
• Server for user authentication. There is provision for both remote (RADIUS) and local
(device) authentication.
• A Role-Based Access Control (RBAC) system that provides a permission model that
allows access to the device operations and configurations based on specific roles and
individual user accounts configured on the AAA server. That is, Administrator,
Engineer, Operator, and Viewer roles are used.
• Security event reporting through both proprietary event logs and the Syslog protocol
for supporting Security Information Event Management (SIEM) systems for centralised
cybersecurity monitoring.
• Encryption of passwords – stored within the IED, in network messages between the
MiCOM S1 Agile software and the IED, and in network messages between the
RADIUS server and the IED (subject to the RADIUS server configuration).
4.1
Initial Setup
The requirements for initial setup of the IED for cyber-security and RBAC will depend on:
1. which interfaces, if any, the cyber-security is required,
2. the intended authentication method, as defined in the setting Auth. Method’ in
SECURITY CONFIG column (see the Authentication methods section).
When the authentication method is configured as Device Only, there are four pre-defined
usernames, VIEWER, OPERATOR, ENGINEER, and ADMINISTRATOR that align with the
VIEWER, OPERATOR, ENGINEER and ADMINISTRATOR roles (see the Device Users
section).
When the authentication method is configured as ‘Server Only’ or ‘Server + Device’, users
must be set up on the Radius server (see the RADIUS users section). These users are
separate from the pre-defined Device users. RADIUS server information must be configured
in the IED to connect to the RADIUS server(s) for Server authentication (see the RADIUS
server settings section). It is recommended that the Radius shared secret be changed from
the default (see the RADIUS client-server validation section).
CS
Whatever the authentication method, it is strongly recommended that the password for the
Administrator be changed from the default. Changing the passwords for the other roles is
optional.
Cyber Security
P746/EN CS/J43
MiCOM P40 Agile P746
(CS) 17-11
5
ROLES AND PERMISSIONS
5.1
Roles
The P40 Agile products provide 4 specific roles to which individual user accounts can be
configured:
• VIEWER (Level 0) Read some, Write minimal
• OPERATOR (Level 1) Read All, Write Few
• ENGINEER (Level 2) Read All, Write Some
• ADMINISTRATOR (Level 3) Read All, Write All
Only one role of one type is allowed to be logged in at a time. For example, one Operator
can be logged in but not a second Operator at the same time. This prevents subsets of
settings from being changed at the same time.
Roles are mapped to Access Level definitions:
VIEWER - No password required - Read access to Security features, Model Number, Serial
Number, S/W version,
Description, Plant reference, Security code (UI Only), Encryption key (UI Only), User Banner
and security related cells.
This role will allow maximum concurrent access provided by P40. Viewer is the default role
OPERATOR – Operator password required - Read access to all data and settings. Write
access to Primary/ Secondary selector, Operator password setting, Password reset cell and
log extraction cells (record selector). This role will not allow concurrent access.
ENGINEER – Engineer password required - Read access to all data and settings. Write
access to Reset demands and counters. This role will not allow concurrent access.
ADMINISTRATOR – Administrator password required - Read access to all data and
settings. Write access to All settings, PSL, IED Config, Security settings (port disabling etc).
This role can enable the bypass mode and forcefully logout any other role. This role will not
allow concurrent access.
The device defines the following roles with reference to the roles defined by IEC 62351-8.
P40 Roles
IEC 62351- 8 Roles
VIEWER
OPERATOR
ENGINEER
ADMINISTRATOR
VIEWER
OPERATOR
ENGINEER
SECADM + SECAUD
Access Level
Level 0
Level 1
Level 2
Level 3
By default, the device is delivered with default factory roles account and passwords. These
default passwords are shown in the below table.
Role
ADMINISTRATOR
ENGINEER
OPERATOR
VIEWER
Note:
Default Password
ChangeMe1#
ChangeMe1#
ChangeMe1#
NA
It is strongly recommended that the password for the Administrator be
changed from the default. Changing the passwords for the other roles is
optional.
Administrators have the following rights as well:
• Setting the Bypass mode
• Forcefully logging out any other role
CS
P746/EN CS/J43
Cyber Security
(CS) 17-12
MiCOM P40 Agile P746
• Setting Authentication Method
'Firmware lock' is not supported by the P40 Agile device. Firmware upgrade is not managed
by the main software. The process involves using a dedicated firmware loading software
tool. There is no access or control to this process via the main product firmware.
5.2
Permissions
Authentication and authorization are two different processes. An authenticated user cannot
perform any action on the device unless a privilege has been explicit granted to him/her to
do so. This is the concept of “least privileges” access.
Privileges must be granted to users through roles. A role is a collection of privileges, and
roles are granted to users. Each user is associated to only one role. The privilege/role matrix
is stored on the IED. This is known as Role-Based-Access Control (RBAC).
On successful user authentication, the IED will load the user’s role list. If the user’s role
changes, the user must logout and log back in to exercise his/her privileges.
Existing User level/permission mapping in P40 are:
Role
CS
Meaning
Read Operation
VIEWER
SYSTEM DATA column:
Description
Plant Reference
Model Number
Serial Number
S/W Ref.
Read Some
Access Level
Write
Security Feature
Minimal
SECURITY CONFIG column:
User Banner
Attempts Remain
Blk Time Remain
Fallback PW level
Security Code (UI only)
OPERATOR
Read All
Write Few
ENGINEER
All data and settings are
Read All
readable.
Write Some
Poll Measurements
All data and settings are
readable.
Poll Measurements
Write Operation
Password Entry
LCD Contrast (UI only)
All items writeable at "Viewer".
Select Event, Main and Fault (upload)
Extract Events (e.g. via MiCOM S1 Agile)
All items writeable at "Operator".
Setting Cells that change visibility (Visible/Invisible).
Setting Values (Primary/Secondary) selector
Commands:
Reset Indication
Reset Demand
Reset Statistics
Reset CB Data / counters
Cyber Security
P746/EN CS/J43
MiCOM P40 Agile P746
(CS) 17-13
Role
Meaning
Read All
Write All
ADMINISTRATOR
Read Operation
Write Operation
All items writeable at "Engineer".
Change all Setting cells
Operations:
Extract and download Setting file.
Extract and download PSL
Extract and download MCL (IEC 61850)
Extraction of Disturbance Recorder
Courier/Modbus Accept Event (auto event extraction,
e.g. via AE2R)
Commands:
Change Active Group setting
Close / Open CB
Change Comms device address.
Set Date & Time
Switch MCL banks / Switch Conf. Bank in UI (IEC 61850)
Enable / Disable Device ports (in SECURITY CONFIG
column)
All password settings
Bypass Enable/disable
Change Authentication Method
All data and settings are
readable.
Poll Measurements
The table below shows the predefined permissions assignment for the predefined Roles
according to IEC 62351-8
Role
VIEWER
OPERATOR
ENGINEER
ADMINISTRATOR
View
x
x
x
x
Read
x
x
x
Dataset
Report
x
x
x
x
x
x
File
File
File
Read
Write
Mngt
x
x
x
x
x
Control
Config.
Setting
Group
Security
x
x
x
x
x
x
The table below shows the predefined permissions description according to IEC 62351-8
Permission
VIEW
READ
DATASET
REPORTING
FILEREAD
FILEWRITE
FILEMNGT
CONTROL
CONFIG
SETTINGGROUP
SECURITY
Description
Allows the subject/role to discover what objects are present within a Logical Device by presenting the
type ID of those objects.
Allows the subject/role to obtain all or some of the values in addition to the type and ID of objects that
are present within a Logical-Device
Allows the subject/role to have full management rights for both permanent and non-permanent
DataSets
Allows a subject/role to use buffered reporting as well as un-buffered reporting
Allows the subject/role to have read rights for file objects
Allows the subject/role to have write rights for file objects. This right includes the FILEREAD right
Allows the role to transfer files to the Logical-Device, as well as delete existing files on the Logical-Device
Allows a subject to perform control operations
Allows a subject to locally or remotely configure certain aspects of the server
Allows a subject to remotely configure Settings Groups
Allows a subject/role to perform security functions at both a Server/Service Access Point and LogicalDevice basis
CS
P746/EN CS/J43
Cyber Security
(CS) 17-14
MiCOM P40 Agile P746
6
AUTHENTICATION
6.1
Authentication Methods
The IED supports Bypass (no authentication), Device authentication and Server
authentication.
Authentication
Method
Bypass Auth.
Device Only
Server Only
Server + Device
Description
IED does not provide security, any user (Local/Remote) can login to the IED. IED does not validate user
and password. In this case, there is no need to enter user-id and password to login.
IED allows role access using local authentication.
IED uses RADIUS server to validate access.
IED uses server authentication to validate user first. And it allows fallback to device authentication if
the RADIUS server(s) are unavailable.
If Bypass Auth. is enabled, the device ignores the Auth. Method setting.
The Auth. Method setting offers the following options for user authentication:
• Server + Device (This is the default setting for IEC 61850+Courier; IEC 61850+103;
DNP3OE – where applicable)
• Device Only (This is the default setting for Courier/IEC 60870-5-103/Modbus/DNP3)
• Server Only
Only an ADMINISTRATOR role may change the Auth. Method setting. If Administrator
changes it, the role remains logged in. But only when the user log-out, their access-level is
revoked.
If Authentication method is Server Only and RADIUS Server IP addresses are configured,
no device user has access to the IED (only the RADIUS users will have access). Only the
RADIUS Administrator role will be able to switch to "Server and Device auth". When the
setting is “Server Only” but RADIUS Server IP are not configured (both
Primary & Secondary are 0.0.0.0), the IED will automatically fall back to Device
authentication.
When Authentication method is Server Only, if the RADIUS server(s) are unavailable, the
user should first take actions to recover the RADIUS connection. If both RADIUS servers
ultimately failed to recover, the user should follow the password reset procedure to reset the
Auth. Method setting to Device Only.
6.2
Bypass
In Bypass Auth. mode, the device does not provide security - any user can login. device
does not validate user and password. The bypass security feature provides an easier
access, with no authentication and encryption for situations when this is considered safe.
Only the Administrator can enable Bypass mode.
There are five modes for authentication bypass:
1. Disabled – no interfaces in Bypass Auth. mode (normal authentication is active)
2. Local & Remote




CS
Front Panel
Front Port
Rear Ports
Ethernet
Cyber Security
P746/EN CS/J43
MiCOM P40 Agile P746
(CS) 17-15
3. Local – will bypass authentication for
 Front Panel;
 Front Port
4. Remote – will bypass authentication for
 Ethernet
 Rear Ports
5. HMI-Only – will bypass authentication only for front panel
Bypass authentication for
Front panel
Bypass mode:
Disabled
Local & Remote
Local
Remote
HMI-Only
X
X
Front Port
X
X
Rear Port
Ethernet
X
X
X
X
X
The DDB signal Security Bypass is available to indicate that the IED is in Bypass Auth.
mode.
6.3
Login
A user can only login through the following methods:
• Front Panel User Interface
• Using MiCOM S1 Agile, connected to either the Front Port, Rear Port 1 or 2, or NIC
(Ethernet) interface.
The interfaces/protocols implemented in P40 are listed in the following table.
The product supports both RBAC (with Server + Device authentication) and original Access
Level. The Courier Interfaces / HMI use the RBAC whilst other protocols such as Modbus,
IEC 60870-5-103, DNP3 use the original
Access Level to authenticate.
The following table shows different product variants that supports different protocols on Rear
ports and Network port.
Local Access
Front
Port
Rear Port (1/2)
HMI Courier
Courier
Courier
HMI Courier
Courier
Courier
HMI Courier
Courier
HMI Courier
Courier
HMI Courier
Courier
HMI Courier
Courier
HMI Courier
Courier
Modbus
(no server, device auth only, old
access levels)
IEC 60870-5-103
(no server, device auth only, old
access levels)
IEC 60870-5-103
(no server, device auth only, old
access levels)
DNP3
(no server, device auth only, old
access levels)
Courier
NIC (Ethernet) Port
IEC 61850 + SNMP + Courier
tunnel
Supported Auth. mechanism
Device
Server and Device
-
Device
Old Access level for Modbus
-
Device
Old Access level for 103
IEC 61850 + SNMP + Courier
tunnel
Server and Device
Old Access level for 103
-
Device
Old Access level for DNP3
DNP3 + SNMP + Courier tunnel
Server and Device
Old Access level for DNP3
CS
P746/EN CS/J43
Cyber Security
(CS) 17-16
6.3.1
MiCOM P40 Agile P746
Front Panel Login
Front panel User Interface supports both Device authentication and Server authentication.
The P40 gives the user the option to enter a username in HMI panel.
The user can type their password in the password cell.
For Device authentication, the user must enter one of the pre-defined usernames VIEWER,
OPERATOR, ENGINEER, ADMINISTRATOR. The user can scroll through these names
using either of the hotkeys. Users must then enter their password.
For Server authentication, the user can enter any valid pre-defined Radius server username.
Using the front panel User Interface, the user can change the displayed character type (digit,
uppercase letter, lowercase letter, special character) by either of the hotkeys. For ease of
typing, it is preferable to do Server authentication login using MiCOM S1 Agile.
After successful log in, a confirmation message is displayed, showing the logged in
username. For example:
LOGIN SUCCESS
OPERATOR
6.3.2
MiCOM S1 Login
When the user attempts to login, MiCOM S1 Agile will prompt the user with a login dialog
box that contains a username text entry field and a password text entry field. The username
field is a combo-dropdown style text field that includes the fixed usernames (Administrator,
Engineer, Operator, Viewer) for Device authentication – the user can pick one of these if
they wish, or type any other pre-defined username for Radius authentication in the textbox
6.3.3
Warning Banner
After successful authentication and authorisation to access the IED, MiCOM S1 Agile will
display a security warning banner to the user.
If I Agree is selected, the integrated authentication and authorisation is completed. Selecting
I Disagree causes the program to close and the login user to logout.
6.3.4
Login Failed
When Device authentication fails, a failure message is displayed:
LOGIN FAILED
For front panel authentication, this is shown for 2 seconds on the LCD.
For S1 Agile authentication, this is a pop-up dialog that the user must click to acknowledge.
6.4
User Sessions
Open sessions will be automatically closed by the IED after a configurable session timeout.
The inactivity timer configuration setting defines the period of time that the IED waits in
idleness before a logged in user is automatically logged out.
If there is any data change that does not commit to IED, the data change is discarded when
user logged out. If there is any access that does not finish, the access will fail when user
logged out. Front panel will display the default page when user reaches the defined inactivity
time.
CS
If the keypad is inactive for configured UI inactivity timer, user logout message is displayed.
And front panel user interface reverts to the Viewer access level.
Cyber Security
P746/EN CS/J43
MiCOM P40 Agile P746
(CS) 17-17
Currently in the P40, the inactivity timer for both front port and HMI is fixed to 15 minutes.
Already, RP1 InactivTimer and RP2 InactivTimer settings control the inactivity timer for
RP1 and RP2. There are two new settings to support configurable inactivity timer for front
port and front panel user interface:
• FP InactvTimer
• UI InactivTimer
Administrator, Operator and Engineer roles will accept only one session to the device at one
time. Only Viewer allows 4 concurrent sessions at one time.
Only one user session is allowed from all the access methods mentioned below:
• Front Panel Push buttons
• Front Port (serial) FP1
• Rear Port 1 (RP1)
• Rear Port 2 (RP2)
• Ethernet Port (NIC)
Setting Name
Description
Number of failed authentications before
the device blocks subsequent
Attempts Limit authentication attempts for the lockout
period. A value of 0 means Lockout is
disabled.
The period of time in seconds a user is
Lockout Period prevented from logging in, after being
locked out.
FP Inactivity Timer is the time of idleness on
Front Port before a logged in user is
FP
automatically logged out and revert the
InactivTimer
access level to the viewer role
UI
InactivTimer
Min
Max
Default
Minimum
Units
Permissions
0 (lockout
disabled)
99
3
-
Administrator
1
5940
5
sec
Administrator
0 (no
Inactivity
Timeout)
30
10
min
Administrator
UI Inactivity Timer is the time of idleness on
0 (no
Front Panel before a logged in user is
Inactivity
automatically logged out and revert the
Timeout)
access level to the viewer role
30
10
min
Administrator
The recommended settings for Attempts Limit is 3 and Lockout Period is 5 sec to
discourage brute force attacks. If the Lockout period is too large, anybody can lockout
Device users.
6.5
User Locking Policy
A local user locking policy is implemented for Device access:
• This user locking policy applies to both Device users.
• The account is unlocked at the first successful login after the Lockout Period
• By default, if the user consecutively fails to login 3 times, the user account will be
locked for 3 minutes.
Each user account records how long it has been locked if the account is locked.
Each user account records how many times it has consecutively failed to login. User account
failed times include all interfaces login attempts. For example, if the Attempts Limit setting
is 3 and the operator failed to login from front panel 2 times, and they changed to login from
the Courier interface, but failed again, then the Operator would be locked out.
When the IED is powered on, these Attempts Limit counter resets to zero.
CS
P746/EN CS/J43
Cyber Security
(CS) 17-18
MiCOM P40 Agile P746
When the user account exceeds the Attempts Limit it is locked for Lockout period, at that
time Attempt limit resets to zero.
The locked user account will be unlocked automatically, after the configured “Lockout
Period” is expired.
All user accounts need to wait until the lockout period expires. No user can unlock the locked
account.
If the locked account attempts to login the IED from the Front Panel, the following text is
displayed (example):
OPERATOR
IS LOCKED
Usernames are specific to each user account, such as Engineer, Operator and
Administrator for Device authentication.
When supporting both RBAC enabled interfaces and non-RBAC interfaces (such as
Modbus), the P40 handles features such as user-locking feature as follows
• If an RBAC user exceeds the invalid password limit, that user gets locked for all the
interfaces.
• On a non-RBAC interface, if an Access Level exceeds the invalid password limit, P40
only blocks that.
6.6
Logout
Each user should Log out after reading or configuring the IED.
Both S1 Agile and the Front Panel provide a one-step logout.
The user can only log out from the front panel, if they logged in from the front panel. If the
user logged in from S1 Agile, they have to logout from S1 Agile.
6.6.1
Front Panel Logout
Go up to the top of the menu tree. When you are at the Column Heading level and you press
the Up button, you may be prompted to log out with the following display:
ENTER TO
LOGOUT
CLEAR TO
CANCEL
If you confirm, the following message is displayed for 2 seconds:
LOGGED OUT
<ROLE NAME>
LOGGED OUT
ADMINISTRATOR
If you decide not to log out (i.e. you cancel), the following message is displayed for 2
seconds.
CS
Cyber Security
P746/EN CS/J43
MiCOM P40 Agile P746
(CS) 17-19
LOGOUT
CANCELLED
ADMINISTRATOR
6.6.2
MiCOM S1 Logout
Right-click on the device name in the System Explorer panel in MiCOM S1 Agile and select
Log Off.
In the Log Off confirmation dialog, click Yes.
6.7
Device Users
For device authentication, the user must enter one of the pre-defined usernames VIEWER,
OPERATOR, ENGINEER, or ADMINISTRATOR. This means that device users and roles
are same in the P40, and therefore there can be only one user for each role.
6.8
Password Policy
Cyber-security requires strong passwords and validation for NERC compliance.
The NERC password complexity policy requires an alpha-numeric password (for all
accesses, front panel, and network/local port) that meets the following mandatory
requirements:
1. Passwords cannot contain the user's account name or parts of the user's full name
that exceed two consecutive characters.
2. Passwords must be at least eight characters in length, but not exceed 16 characters in
length.
3. Passwords must contain characters from all four categories:




English uppercase characters (A through Z).
English lowercase characters (a through z).
Numeric (digits 0 through 9).
Special non-alphanumeric characters (such as @,!,#,{, but not limited to only
those)
For Device authentication, the IED will enforce that configured passwords meet these
requirements.
For Server authentication, the password complexity and user locking policy is defined in the
external Radius server.
6.9
Change Password
In the Device authentication mode, VIEWER does not have a password associated with it.
The password can be changed either from the front panel User Interface, or from MiCOM S1
Agile using the Change/Set Password option in the Supervise Device dialog box.
Caution: It is recommended that user passwords are changed periodically.
6.10
RADIUS
When the Auth. Method setting is configured as Server Only or Server + Device, a user
must log in with a username and password that has been predefined on the Radius server.
This log in can be performed from any interface, as described in the Login section. The IED
will authenticate the user to the active RADIUS server, over the Ethernet connection.
CS
P746/EN CS/J43
Cyber Security
(CS) 17-20
MiCOM P40 Agile P746
User
Groups
Access Request
User login
IED
RADIUS
Client
Access
Accept
(User Role)
User
RADIUS Server
Active Directory
V01100
Figure 1: RADIUS server/client communication
6.10.1
RADIUS Users
For Server authentication, RADIUS users and passwords are created in the server (in the
Active Directory).
The username must consist of uppercase letters (A to Z) and digits (0 to 9) only. No
lowercase letters or special characters are allowed.
Each RADIUS user must have a password that meets the password policy of the Active
Directory (not the password policy of the P40) and have one of the four roles assigned in the
Active Directory.
The number of RADIUS users is not limited by the IED.
RADIUS password changes are done in the Active Directory (after password expiration).
6.10.2
RADIUS Client
Two Radius servers are supported by the IED in the configuration for redundancy. The IED
will try each in sequence until one responds.
The IED will first try server 1 up to the configured number of retries, leaving a request
timeout between each request. If, after this point there is still no valid answer from server 1,
the IED will switch to server 2 and repeat for up to the configured number of retries.
If the number of retries for the second server is exceeded, the IED will give up entirely on
Server authentication. If Authentication Method is Server + Device, the IED will fallback to
Device authentication. A RADIUS Server unavailable security event is also logged under
this condition.
The RADIUS implementation supports the following authentication protocols:
• EAP-TTLS-MSCHAP2
• PAP
• EAP-PEAP-MSCHAP2
• PAP EAP-TTLS-PAP (Default)
The RADIUS implementation queries the Role ID vendor attribute and establish the logged in
user security context with that role.
RADIUS Config.
CS
Vendor ID
Vendor Attribute
P40 Role Values
Administrator
Engineer
Operator
Viewer
Value
2910
1
3
2
1
0
Cyber Security
P746/EN CS/J43
MiCOM P40 Agile P746
6.10.3
(CS) 17-21
RADIUS Server Settings
The following RADIUS server information must be configured in the IED to connect to the
RADIUS server(s) for Server authentication.
Setting
Name
Description
Min
IP address of Server 1.
Default value indicates no
Primary Radius server is
0.0.0.0
configured, and so Radius
is disabled.
IP address of Server 2.
Default value indicates no
0.0.0.0
Secondary Radius server is
configured
RADIUS
Pri IP
RADIUS
Sec IP
RADIUS
Auth Port
RADIUS
Security
RADIUS
Timeout
RADIUS
Retries
RADIUS
Secret
Radius authentication port 1
Authentication protocol to
be used by Radius server.
Timeout in seconds
between re-transmission
requests
Number of retries before
giving up
Shared Secret used in
authentication. It is only
displayed as asterisks.
Max
Default
Units
Minimum
Permissions
255.255.255.255
0.0.0.0
-
Administrator
255.255.255.255
0.0.0.0
-
Administrator
65535
1812
-
Administrator
PAP EAP-TTLSPAP
-
Administrator
EAP-TTLSMSCHAP2
PAP
EAP-PEAPMSCHAP2
PAP EAP-TTLSPAP
1
900
2
sec
Administrator
1
99
10
-
Administrator
1 character
16 characters
-
Administrator
ChangeMe1#
The data cell RADIUS Status indicates the status of the currently-selected RADIUS server.
This will display either Disabled, Server OK, or Failed.
6.10.4
RADIUS Accounting
Radius accounting is not supported by the IED. The user can achieve accounting through
syslog (see the SYSLOG section).
6.10.5
RADIUS Client-server Validation
Client-server validation is achieved using a shared secret. The IED must be configured with
the RADIUS Secret setting to match the shared secret configured in the RADIUS server. It is
recommended (but not enforced) that this setting meets the P40 password requirements.
Note:
It is recommended that the shared secret be changed from the default
before using Radius authentication.
The relay does not support exchange of CA certificates. The RADIUS server may send a
certificate but the IED will not verify it.
6.11
6.11.1
Recovery
Restore to local Factory Default
The Restore Defaults setting is available to facilitate NERC CIP compliance requirements
for decommissioning critical cyber devices. Only the Administrator role can change this
setting.
The Restore Defaults setting under the CONFIGURATION column is used to restore a
setting group to factory default settings.
0 = No Operation
CS
P746/EN CS/J43
Cyber Security
(CS) 17-22
MiCOM P40 Agile P746
1 = All Settings
2 = Setting Group 1
3 = Setting Group 2
4 = Setting Group 3
5 = Setting Group 4
To restore the default values to the settings in any setting group, set the Restore Defaults
setting to the relevant Group number. Alternatively, it is possible to set the Restore Defaults
setting to All Settings to restore the default values to all the IEDs settings, not only one
setting group.
Note:
Restoring defaults to all settings includes the rear communication port
settings, which may result in communication via the rear port being disrupted
if the new (default) settings do not match those of the master station.
Data (events, DR, fault records, protection counters etc) is left untouched. When
decommissioning critical cyber IEDs, users may want to clear all data and events as well.
6.11.2
Password Reset Procedure
If you mislay a devices password (if Administrator forgets their password), the passwords
can be reset to default using a recovery password. To obtain the recovery password you
must contact the Contact Centre and supply the Serial Number and the security code. The
Contact Centre will use these items to generate a Recovery Password.
The security code is a 16-character string of uppercase characters. It is a read-only
parameter. The device generates its own security code randomly. A new code is generated
under the following conditions:
• On power up
• Whenever settings are set back to default
• On expiry of validity timer (see below)
• When the recovery password is entered
This reset procedure can be only accomplished through front panel exclusively and cannot
be done over any other interface. As soon as the security code is displayed on the front
panel User Interface, a validity timer is started. This validity timer is set to 72 hours and is not
configurable. This provides enough time for the Contact Centre to manually generate and
send a recovery password. The Service Level Agreement (SLA) for recovery password
generation is one working day, so 72 hours is sufficient time, even allowing for closure of the
Contact Centre over weekends and bank holidays.
The procedure is:
The security code is displayed on confirmation. The validity timer is then started. The
security code can only be read from the front panel.
This reset procedure can be only accomplished through front panel exclusively and cannot
be done over the Ethernet/serial port, but only when physically present in front of the IED. In
the event of losing all passwords (if the Administrator forgets their password) the user could
reset the IED to default passwords, following the procedure below:
1. User navigates to Security Code cell in SECURITY CONFIG column
2. To prevent accidental reading of the IED Security Code, the cell will initially display a
warning message:
PRESS ENTER TO
READ SEC. CODE
CS
3. Press Enter to read the Security Code.
Cyber Security
P746/EN CS/J43
MiCOM P40 Agile P746
(CS) 17-23
4. User sends an email to the Contact Centre providing the full IED serial number and
displayed Security Code, using a recognisable corporate email account
5. Contact Centre emails the user with the Recovery Password. The recovery password
is intended for recovery only. It is not a replacement password that can be used
continually. It can only be used once – for password recovery.
6. User logs in with the username ADMINISTRATOR and the recovery password in to
the Password setting in SYSTEM DATA column.
7. Then IED will prompt
RESET
PASSWORD?
ENTER or CLEAR
8. Press Enter to continue the reset procedure
9. If the recovery password successfully validates, the default passwords are restored for
each access level for Device authentication.
10.Change Auth. Method setting to Server + Device if applicable.
Note:
6.11.3
Restoring passwords to defaults does not affect any other settings and does
not provoke reboot of the IED. The protection and control functions of the
IED are always maintained.
Access Level DDBs
The current level of access for each interface is available for use in the Programming
Scheme Logic (PSL) as these DDB signals:
• HMI Access Lvl 1
• HMI Access Lvl 2
• FPort AccessLvl1
• FPort AccessLvl2
• RPrt1 AccessLvl1
• RPrt1 AccessLvl2
• RPrt2 AccessLvl1
• RPrt2 AccessLvl2
Each pair of DDB signals indicates the access level as follows:
• Level 1 off, Level 2 off = 0
• Level 1 on, Level 2 off = 1
• Level 1 off, Level 2 on = 2
• Level 1 on, Level 2 on = 3
KEY:
HMI = Human Machine Interface
FPort = Front Port
RPrt = Rear Port
Lvl = Level
6.12
Disabling Physical Ports
It is possible to disable unused physical ports. A level 3 password is needed to perform this
action.
CS
P746/EN CS/J43
Cyber Security
(CS) 17-24
MiCOM P40 Agile P746
To prevent accidental disabling of a port, a warning message is displayed according to
whichever port is required to be disabled. For example, if rear port 1 is to be disabled, the
following message appears:
REAR PORT 1 TO
BE
DISABLED.CONFI
RM
The following ports can be disabled, depending on the model.
• Front port (Front Port setting)
• Rear port 1 (Rear Port 1 setting)
• Rear port 2 (Rear Port 2 setting)
• Ethernet port (Ethernet Port setting)
Note:
6.13
It is not possible to disable a port from which the disabling port command
originates. We do not generally advise disabling the physical Ethernet port.
Disabling Logical Ports
It is possible to disable unused logical ports. A level 3 password is needed to perform this
action.
Note:
The port disabling setting cells are not provided in the settings file. It is only
possible to do this using the HMI front panel.
The following protocols can be disabled:
• IEC 61850 (IEC 61850 setting)
• Courier Tunnelling (Courier Tunnel setting)
Note:
CS
If any of these protocols are enabled or disabled, the Ethernet card will
reboot.
Cyber Security
P746/EN CS/J43
MiCOM P40 Agile P746
7
(CS) 17-25
SECURITY EVENT MANAGEMENT
To implement NERC-compliant cyber-security, a range of security events are logged in the
Security Event file.
7.1
Security Events: Courier
Event Value
PASSWORD LEVEL UNLOCKED
PASSWORD LEVEL RESET
PASSWORD SET BLANK
PASSWORD SET NON-COMPLIANT
PASSWORD MODIFIED
PASSWORD ENTRY BLOCKED
PASSWORD ENTRY UNBLOCKED
INVALID PASSWORD ENTERED
PASSWORD EXPIRED
PASSWORD ENTERED WHILE BLOCKED
RECOVERY PASSWORD ENTERED
IED SECURITY CODE READ
IED SECURITY CODE TIMER EXPIRED
PORT DISABLED
PORT ENABLED
DEF. DISPLAY NOT NERC COMPLIANT
PSL SETTINGS DOWNLOADED
DNP SETTINGS DOWNLOADED
TRACE DATA DOWNLOADED
IEC 61850 CONFIG DOWNLOADED
USER CURVES DOWNLOADED
PSL CONFIG DOWNLOADED
SETTINGS DOWNLOADED
PSL SETTINGS UPLOADED
DNP SETTINGS UPLOADED
Display
USER LOGGED IN
ON {int} LEVEL {n}
USER LOGGED OUT
ON {int} LEVEL {n}
P/WORD SET BLANK
BY {int} LEVEL {p}
P/WORD NOT-NERC
BY {int} LEVEL {p}
PASSWORD CHANGED
BY {int} LEVEL {p}
PASSWORD BLOCKED
ON {int}
P/WORD UNBLOCKED
ON {int}
INV P/W ENTERED
ON <int}
P/WORD EXPIRED
ON {int}
P/W ENT WHEN BLK
ON {int}
RCVY P/W ENTERED
ON {int}
IED SEC CODE RD
ON {int}
IED SEC CODE EXP
PORT DISABLED
BY {int} PORT {prt}
PORT ENABLED
BY {int} PORT {prt}
DEF DSP NOT-NERC
PSL STNG D/LOAD
BY {int} GROUP {grp}
DNP STNG D/LOAD
BY {int}
TRACE DAT D/LOAD
BY {int}
IED CONFG D/LOAD
BY {int}
USER CRV D/LOAD
BY {int} GROUP {crv}
PSL CONFG D/LOAD
BY {int} GROUP {grp}
SETTINGS D/LOAD
BY {int} GROUP {grp}
PSL STNG UPLOAD
BY {int} GROUP {grp}
DNP STNG UPLOAD
BY {int}
CS
P746/EN CS/J43
Cyber Security
(CS) 17-26
MiCOM P40 Agile P746
Event Value
TRACE DATA UPLOADED
IEC 61850 CONFIG UPLOADED
USER CURVES UPLOADED
PSL CONFIG UPLOADED
SETTINGS UPLOADED
EVENTS HAVE BEEN EXTRACTED
ACTIVE GROUP CHANGED
CS SETTINGS CHANGED
DR SETTINGS CHANGED
SETTING GROUP CHANGED
POWER ON
SOFTWARE_DOWNLOADED
Display
TRACE DAT UPLOAD
BY {int}
IED CONFG UPLOAD
BY {int}
USER CRV UPLOAD
BY {int} GROUP {crv}
PSL CONFG UPLOAD
BY {int} GROUP {grp}
SETTINGS UPLOAD
BY {int} GROUP {grp}
EVENTS EXTRACTED
BY {int} {nov} EVNTS
ACTIVE GRP CHNGE
BY {int} GROUP {grp}
C & S CHANGED
BY {int}
DR CHANGED
BY {int}
SETTINGS CHANGED
BY {int} GROUP {grp}
POWER ON
S/W DOWNLOADED
-
where:
• int is the interface definition (UI, FP, RP1, RP2, TNL, TCP)
• prt is the port ID (FP, RP1, RP2, TNL, DNP3, IEC, ETHR)
• grp is the group number (1, 2, 3, 4)
• crv is the Curve group number (1, 2, 3, 4)
• n is the new access level (0, 1, 2, 3)
• p is the password level (1, 2, 3)
• nov is the number of events (1 – nnn)
Each new event has an incremented unique number, therefore missing events appear as
gap in the sequence. The unique identifier forms part of the event record that is read or
uploaded from the IED.
Note:
7.2
It is no longer possible to clear Event, Fault, Maintenance, and Disturbance
Records.
Syslog
Security events are also logged to a remote syslog server.
All login and logout attempts from local and central authentication, whether successful or
failed, are logged. The contents of each successful or failed, login and logout security event
include a specific username.
The security log cannot be cleaned by any of the available roles.
The contents of each login and/or logout security event include the relevant interface. The
following interfaces are supported:
Interface
CS
Front Port
Rear Port 1
Abbr.
FP
RP1
Cyber Security
P746/EN CS/J43
MiCOM P40 Agile P746
(CS) 17-27
Interface
Abbr.
Rear Port 2
Ethernet
Front Panel
RP2
NET
UI
The following events are available to be logged to the syslog server:
Event Categorisation
Severity
Login - Authentication successful
Login - Authentication Failure
Logout
RADIUS Server Unavailable
Session timeout
Account Locked
User accessed while locked
ByPass Activate
ByPass Deactivate
Password Change
Recovery password is entered to reset the passwords
Settings / Configuration Changed
Settings / Configuration uploaded
(to S1 Agile)
Event Records uploaded
Default settings restored
Informational (6)
Informational (6)
Informational (6)
Alert (1)
Informational (6)
Notice (5)
Notice (5)
Notice (5)
Notice (5)
Notice (5)
Notice (5)
Notice (5)
Notice (5)
Notice (5)
Notice (5)
Notice (5)
Notice (5)
Notice (5)
Notice (5)
Notice (5)
Notice (5)
Notice (5)
Active Setting Group Changed
Default user curves restored
7.3
Syslog Client
The IED supports security event reporting through the Syslog protocol for supporting
Security Information Event Management (SIEM) systems for centralized cyber security
Monitoring over UDP protocol.
The IED is a Syslog client that supports two Syslog servers. The following settings are
available in the COMMUNICATIONS column.
Setting Name
SysLog Pri IP
SysLog Sec IP
SysLog Port
7.4
Description
The IP address of the target
Syslog server (Primary)
The IP address of the target
Syslog server (Secondary)
The UDP port number of the
target Syslog server
Min
Max
Default
Units
Min. Permission
0.0.0.0
223.255.255.254
0.0.0.0
-
Administrator
0.0.0.0
223.255.255.254
0.0.0.0
-
Administrator
1
65535
514
-
Administrator
Syslog Functionality
The P40 supports the RFC 5424 UDP protocol.
The table below shows the format of a Syslog event.
Header
<PRIVAL>1 YYYY-MM-DDTHH:mm:ss.fffZ IEDName userlog - MSGID
PRIVAL
32 + [event severity]
32 is derived from the facility number 4 (meaning security/authorization
messages)
Event severity is derived from the received message.
YYYY
4 Digit year; i.e. 2018
CS
P746/EN CS/J43
Cyber Security
(CS) 17-28
MiCOM P40 Agile P746
Derived from the received message timestamp.
2 Digit month; 01 to 12 (for January to December).
Derived from the received message timestamp.
DD
2 Digit day of month; 01 to 31 (depending upon the month)
Derived from the received message timestamp.
HH
2 Digit hour of day; 00 to 23
Derived from the received message timestamp.
mm
2 Digit count of minutes elapsed in the current hour; 00 to 59
Derived from the received message timestamp.
ss
2 Digit count of seconds elapsed in the current minute; 00 to 59
Derived from the received message timestamp.
fff
3 Digit fraction of seconds (millisecond resolution); 0 to 999
Derived from the received message timestamp.
IP Addr
IP Address assigned to the Ethernet Board.
MSGID
Unique message type identity
Derived from the received message event type.
[timeQuality tzKnown=X]
X
Timezone quality attribute for event timestamp (in header)
0; indicating Local Time offset and DST settings are not enabled (i.e.
timestamp is UTC)
[gePlatformEvt channel=IFACE accessLevel=AL evtid=UUID extra=EDATA] DETAIL
IFACE
Channel access type
Copied from the received message interface name.
AL
Access Level
Copied from the received message access level.
UUID
Unique event identification
Copied from the received message unique id.
EDATA
Extra event data – meaning of which is specific to the event type
(see MSGID in header)
Copied from the received message extra info.
DETAIL
Event details.
Derived from the received message event text and value.
[geUserInfo channel=IFACE loginId=USER] DETAIL
IFACE
Channel access type
Copied from the received message interface name.
USER
Logged in username who generated the event
Copied from the received message user id.
DETAIL
Event details.
Copied from the received message event text.
<38>1 2018-02-06T11:46:32.074Z Feeder1 userlog - 5120 [timeQuality
tzKnown=0][gePlatformEvt channel=UI accessLevel=3 evtid=4 extra=0] User Logged In on
UI Level 3User Logged In on UI Level 3
<38>1 2018-02-06T11:46:32.074Z Feeder1 userlog - 9999 [timeQuality
tzKnown=0][geUserInfo channel=UI loginId=user1] Login - Authentication successful
MM
Data
(common)
Data
(Platform
event)
Data
(Enhanced
event)
Formatted
Examples:
Sample Syslog messages are shown below:
Event
CS
Access Method
Syslog Message (As from Syslog Server)
04-17-2019 14:43:32 Auth.Info 192.168.1.30 1 1994-01-23T21:34:06.102Z
192.168.1.30 userlog - 9999 [timeQuality tzKnown=0][geUserInfo
channel=FP loginid=ADMINISTRATOR] Login - Authentication successful
Authentication
Successful
UI
Authentication
Failure
Serial
04-19-201913:36:08Auth.Info192.168.1.301 1994-01-25T20:26:42.872Z 192.168.1.30
userlog - 9999 [timeQuality tzKnown=0][geUserInfo channel=RP1 loginid=ENGINEER]
Login - Authentication fail
Network Login
Success
Courier Tunnel
(device
authentication)
04-17-201915:29:20Auth.Info192.168.1.301 1994-01-23T22:19:58.168Z 192.168.1.30
userlog - 9999 [timeQuality tzKnown=0][geUserInfo channel=NET loginid=ENGINEER]
Login - Authentication successful
Cyber Security
P746/EN CS/J43
MiCOM P40 Agile P746
Event
(CS) 17-29
Access Method
Logout
Serial
Radius
Unavailable
FP
Bypass Activated FP
Settings modified Courier Tunnel
Syslog Message (As from Syslog Server)
04-19-201913:52:08Auth.Info192.168.1.301 1994-01-25T20:42:42.782Z 192.168.1.30
userlog - 9999 [timeQuality tzKnown=0][geUserInfo channel=RP1
loginid=ADMINISTRATOR] Logout
04-18-201912:40:14Auth.Alert192.168.1.301 1994-01-24T19:30:55.839Z 192.168.1.30
userlog - 5163 [timeQuality tzKnown=0][gePlatformEvt channel=FP accessLevel=0
evtid=3715 extra=0] RADIUS UnAvailbl
04-18-201912:39:19Auth.Warning192.168.1.301 1994-01-24T19:30:00.573Z
192.168.1.30 userlog - 9998 [timeQuality tzKnown=0][geUserInfo channel=FP
loginid=ADMINISTRATOR] ByPass Activated
04-18-201911:52:35Auth.Notice192.168.1.301 1994-01-24T18:43:16.537Z 192.168.1.30
userlog - 5149 [timeQuality tzKnown=0][gePlatformEvt channel=NET accessLevel=3
evtid=3677 extra=0] Settings Upload By TNL
CS
P746/EN CS/J43
(CS) 17-30
CS
Cyber Security
MiCOM P40 Agile P746
APPENDIX A
ORDERING OPTIONS
Appendix A - Ordering Options
P746
P746/EN M/J43
P746
Variants
Appendix A - Ordering Options
Order Number
P746 Busbar Protection Relay
Vx Aux Rating :
24 - 54Vdc
48 - 125Vdc (40 - 100Vac)
110 - 250 Vdc (100 - 240 Vac)
In/Vn Rating :
CT1 - CT18 In = 1A/5A, Vn = (100/120V) (18CT/3VT)
Hardware Options :
Standard : no options
IRIG-B (Modulated) only
IRIG-B (Modulated) & Fibre Optic Converter
2nd Rear Comms port
2nd Rear comms port + IRIG-B (Modulated)
IRIG-B (Un-modulated)
Redundant Ethernet PRP/HSR/RSTP/Failover, 2 multi-mode fibre ports + Modulated/Un-Modulated IRIG-B
Redundant Ethernet PRP/HSR/RSTP/Failover, 2 coper ports RJ45 + Modulated/Un-Modulated IRIG-B
Single Ethernet PRP/HSR/RSTP/Failover, 1 multi-mode fibre port & 1 coper port RJ45 + Modulated/Un-Modulated IRIG-B
Product Specific Options :
Size 16 Case, 16 optos + 16 Relays
Size 16 Case, 16 optos + 8 Relays + 8 High Break Relays
Size 16 Case, 16 optos + 32 Relays
Size 16 Case, 16 optos + 24 Relays + 4 High Break Relays
Size 16 Case, 24 optos + 24 Relays
Size 16 Case, 24 optos + 16 Relays + 8 High Break Relays
Size 16 Case, 24 optos + 8 Relays + 12 High Break Relays
Size 16 Case, 32 optos + 24 Relays
Size 16 Case, 32 optos + 16 Relays + 8 High Break Relays
Size 16 Case, 40 optos + 24 Relays
Size 16 Case, 32 optos + 32 Relays
Protocol Options :
K-Bus/Courier
Modbus
IEC60870-5-103
DNP3.0
IEC 61850 over Ethernet and Courier via rear K-Bus/RS485
Mounting Options :
Flush/Panel Mounting with Harsh Env. Coating, with USB Port, Black and Silver Front Panel
19" Rack Mounting with Harsh Env. Coating, with USB Port, Black and Silver Front Panel
Language Options :
English, French, German, Spanish
English, French, German, Russian
Chinese, English or French via HMI, with English or French only via Communications port
Software Version Options :
Unless specified the latest version will be delivered
Settings Files Options :
Default
Customer Specific
P746
**
7
8
9
1
1
2
4
7
8
C
R
S
T
A
B
C
D
E
F
G
H
J
K
L
1
2
3
4
6
S
T
0
5
C
**
0
A
Design Suffix :
Factory Determined
This cortec should only be used for guidance as it provides a snapshot of the interactive data taken at the time of publication. All current models and variants for
this product are defined in an interactive spreadsheet, which is located in the Resources > Specifications tab on the company website.
P746/EN M/J43
A1
Appendix A - Ordering Options
A2
P746
P746/EN M/J43
APPENDIX B
WIRING DIAGRAMS
Appendix B - Wiring Diagrams
P746
P746/EN M/J43
MiCOM P40 Agile P746
Appendix A – Wiring Diagrams
Model
External Connection Diagram Title
Drawing-Sheet
Issue
All
COMMS OPTIONS MICOM Px40 PLATFORM
10Px4001-1
K
P746 BUSBAR PROTECTION (80TE) SYSTEM CONNECTIONS FOR ONE BOX SOLUTION
10P74600-1
D
P746 BUSBAR PROTECTION (80TE) SYSTEM CONNECTIONS FOR THREE BOX SOLUTION
10P74600-2
F
BUSBAR PROTECTION (80TE) WITH 16 I/P & 16 O/P
10P74601-1
E
BUSBAR PROTECTION (80TE) WITH 16 I/P & 16 O/P (8 O/P ARE HIGH BREAK)
10P74602-1
E
BUSBAR PROTECTION (80TE) WITH 16 I/P & 32 O/P
10P74603-1
E
BUSBAR PROTECTION (80TE) WITH 16 I/P & 28 O/P (4 O/P ARE HIGH BREAK)
10P74604-1
F
BUSBAR PROTECTION (80TE) WITH 24 I/P & 24 O/P
10P74605-1
E
BUSBAR PROTECTION (80TE) WITH 24 I/P & 24 O/P (8 O/P ARE HIGH BREAK)
10P74606-1
E
BUSBAR PROTECTION WITH 24 I/P & 20 O/P (12 O/P ARE HIGH BREAK)
10P74607-1
F
BUSBAR PROTECTION (80TE) WITH 32 I/P & 24 O/P
10P74608-1
E
BUSBAR PROTECTION (80TE) WITH 32 I/P & 24 O/P (8 O/P ARE HIGH BREAK)
10P74609-1
E
BUSBAR PROTECTION (80TE) WITH 40 I/P & 24 O/P
10P74610-1
E
BUSBAR PROTECTION (80TE) WITH 32 I/P & 32 O/P
10P74611-1
D
BUSBAR PROTECTION (80TE) WITH 16 I/P & 16 O/P NCIT
10P74612-1
E
BUSBAR PROTECTION (80TE) WITH 16 I/P & 16 O/P (8 O/P ARE HIGH BREAK) NCIT
10P74613-1
E
BUSBAR PROTECTION (80TE) WITH 16 I/P & 32 O/P NCIT
10P74614-1
E
BUSBAR PROTECTION (80TE) WITH 16 I/P & 28 O/P (4 O/P ARE HIGH BREAK) NCIT
10P74615-1
E
BUSBAR PROTECTION (80TE) WITH 24 I/P & 24 O/P NCIT
10P74616-1
E
BUSBAR PROTECTION (80TE) WITH 24 I/P & 24 O/P (8 O/P ARE HIGH BREAK) NCIT
10P74617-1
E
BUSBAR PROTECTION WITH 24 I/P & 20 O/P (12 O/P ARE HIGH BREAK) NCIT
10P74618-1
E
BUSBAR PROTECTION (80TE) WITH 32 I/P & 24 O/P NCIT
10P74619-1
E
BUSBAR PROTECTION (80TE) WITH 32 I/P & 24 O/P (8 O/P ARE HIGH BREAK) NCIT
10P74620-1
E
BUSBAR PROTECTION (80TE) WITH 40 I/P & 24 O/P NCIT
10P74621-1
E
10P74622-1
E
P746
BUSBAR PROTECTION (80TE) WITH 32 I/P & 32 O/P NCIT
* When selecting the applicable wiring diagram(s), refer to appropriate model’s Cortec.
P746/EN M/J43
A1
Finish:
Sub-contractor reference:
Date:
Date:
Chkd:
Name:
CAD DATA 1:1 DIMENSIONS: mm
DO NOT SCALE
Drg
Title:
Angular Tol
deg:
Linear Tol
mm:
Next Stage:
This document is the property of General Electric Company ("GE") and contains proprietary information of GE. This document is loaned on the express condition that neither it nor the information contained therein shall be disclosed to others
without the express written consent of GE, and that the information shall be used by the recipient only as approved expressly by GE. This document shall be returned to GE upon its request. This document may be subject to certain restrictions
GE PROPRIETARY AND CONFIDENTIAL INFORMATION
DESCRIPTION
Grid Solutions
PART
PLM
No:
Drg
No:
A20022917
10PX4001
Next
Sht:
Sht:
ECN No:
MATERIAL
IN WORK
Status:
K
Revision:
3
Iteration:
Date:
Date:
Issue:
4/30/2020
D
S1
S2
P2
C
B
A
C
B
A
P1
S1
S2
P2
C
B
Chkd:
Name:
S.J.BURTON
P1
S1
S2
P2
C
B
A
P1
S1
S2
P2
C
B
A
P1
S1
S2
P2
C
B
A
P2
S2
S1
P1
C (6)
B (6)
A (6)
C (5)
B (5)
A (5)
C (4)
B (4)
A (4)
C (3)
B (3)
A (3)
C (2)
B (2)
A (2)
C (1)
B (1)
A (1)
F16
F15
F14
F13
F12
F11
F22
F21
F20
F19
F18
F17
F28
F27
F26
F25
F24
F23
D16
D15
D14
D13
D12
D11
D22
D21
D20
D19
D18
D17
D28
D27
D26
D25
D24
D23
C
B
PHASE ROTATION
A
GE PROPRIETARY AND CONFIDENTIAL INFORMATION
This document is the property of General Electric Company ("GE") and contains proprietary information of GE. This document is loaned on the express
condition that neither it nor the information contained therein shall be disclosed to others without the express written consent of GE, and that the information
shall be used by the recipient only as approved expressly by GE. This document shall be returned to GE upon its request. This document may be subject to
certain restrictions under U.S. export control laws and regulations.© General Electric Company, GE CONFIDENTIAL UNPUBLISHED WORK.
A
PROTECTED BUSBAR
DIRECTION OF FORWARD CURRENT FLOW
CID006234 Outlines updated to GE Format
Revision:
P1
Drg
No:
Title:
F1
F2
D3
D4
D1
D2
VN
VC
VB
VA
CASE
EARTH
NOTE 2
n
N
a
C
b c
B
B
24
23
28
PIN TERMINAL (P.C.B. TYPE)
TERMINAL.
C.T. SHORTING LINKS MAKE BEFORE (b) DISCONNECT.
MODULE TERMINAL BLOCK
VIEWED FROM REAR
27
26
22
21
25
20
19
18
16
17
14
15
12
4
2
13
11
3
1
4. SEE DRAWINGS 10P746 01 TO 10P746 10 FOR THE VARIOUS I/O OPTIONS.
3. THE MONITORED THREE PHASE VOLTAGE MAY BE CONNECTED HV OR LV SIDE.
2. THE VT STAR POINT MUST BE MADE EXTERNALLY AS SHOWN.
(c)
(b)
1. (a)
NOTES:
NOTE 3
C
10P74600
1
2
Sht:
Next
Sht:
C
St Leonards Building
Harry Kerr Drive, Stafford.
ST16 1WT, UK
UK Grid Solutions Ltd
EXTERNAL CONNECTION DIAGRAM: P746 BUSBAR PROTECTION (80TE)
SYSTEM CONNECTIONS FOR ONE BOX SOLUTION
MiCOM P746 (PART)
A
A
Date:
Date:
Issue:
P1
S2
4/30/2020
F
S1
P2
B
A
P1
S1
S2
P2
C
B
A
P1
S1
S2
P2
C
B
A
P1
S1
S2
P2
C
B
A
P1
S1
S2
P2
C
B
P1
S1
S2
P2
Chkd:
Name:
S.J.BURTON
C
B
A
P1
S1
S2
P2
C
B
A
P1
S1
S2
P2
C
B
A
P1
S1
S2
P2
C
B
A
P1
S1
S2
P2
PROTECTED BUSBAR
C
B
A
P1
S1
S2
P2
DIRECTION OF FORWARD CURRENT FLOW
C
B
A
P1
S1
S2
P2
C
B
A
P1
S1
S2
P2
C
B
A
P1
S1
S2
P2
RELAY CONNECTIONS FOR PHASE 'A' BOX ONLY ARE SHOWN
(SIMILAR RELAY CONNECTIONS TO BE USED RESPECTIVELY FOR PHASE 'B' & 'C')
A
C
GE PROPRIETARY AND CONFIDENTIAL INFORMATION
This document is the property of General Electric Company ("GE") and contains proprietary information of GE. This document is loaned on the express
condition that neither it nor the information contained therein shall be disclosed to others without the express written consent of GE, and that the information
shall be used by the recipient only as approved expressly by GE. This document shall be returned to GE upon its request. This document may be subject to
certain restrictions under U.S. export control laws and regulations.© General Electric Company, GE CONFIDENTIAL UNPUBLISHED WORK.
CID006234 Outlines updated to GE Format
C
Revision:
C
B
A
B
P1
S1
S2
P2
C
Drg
No:
Title:
A
A
P1
S1
S2
P2
C
B
A
P1
S1
S2
P2
C
P2
S2
S1
P1
A (18)
A (17)
A (16)
A (15)
A (14)
A (13)
A (12)
A (11)
A (10)
A (9)
A (8)
A (7)
A (6)
A (5)
A (4)
A (3)
A (2)
A (1)
NOTES:
CASE
EARTH
B
C
27
25
28
26
24
22
23
20
21
18
16
14
12
19
17
15
13
4
2
NOTE 5
PHASE A, B AND C
Z1 OR Z2
NOTE 3
11
3
1
b c
C
MODULE TERMINAL BLOCK
VIEWED FROM REAR
NOTE 2
a
B
F16
3. THE MONITORED THREE PHASE VOLTAGE MAY BE CONNECTED HV OR LV SIDE.
5. FOR 3 BOXES SOLUTION THE VT INPUTS MUST BE CONNECTED IN PARALLEL IN ALL BOXES.
4. SEE DRAWINGS 10P746 01 TO 10P746 10 FOR THE VARIOUS I/O OPTIONS.
F15
PIN TERMINAL (P.C.B. TYPE)
(c)
2. THE VT STAR POINT MUST BE MADE EXTERNALLY AS SHOWN.
TERMINAL.
C.T. SHORTING LINKS MAKE BEFORE (b) DISCONNECT.
F1
F2
D3
D4
D1
D2
n
N
(b)
1. (a)
VT
VT
VT
MiCOM P746 (PART)
A
A
F14
F13
F12
F11
F22
F21
F20
F19
F18
F17
F28
F27
F26
F25
F24
F23
D16
D15
D14
D13
D12
D11
D22
D21
D20
D19
D18
D17
D28
D27
D26
D25
D24
D23
C
B
PHASE ROTATION
A
10P74600
Next
Sht:
Sht:
2
-
C
St Leonards Building
Harry Kerr Drive, Stafford.
ST16 1WT, UK
UK Grid Solutions Ltd
EXTERNAL CONNECTION DIAGRAM: P746 BUSBAR PROTECTION (80TE)
SYSTEM CONNECTIONS FOR THREE BOX SOLUTION
B
B
A
Date:
Date:
Issue:
4/30/2020
E
-
G18
G17
G16
G15
G14
Chkd:
Name:
S.J.BURTON
Title:
GE PROPRIETARY AND CONFIDENTIAL INFORMATION
This document is the property of General Electric Company ("GE") and contains proprietary information of GE. This document is loaned on the express
condition that neither it nor the information contained therein shall be disclosed to others without the express written consent of GE, and that the information
shall be used by the recipient only as approved expressly by GE. This document shall be returned to GE upon its request. This document may be subject to
certain restrictions under U.S. export control laws and regulations.© General Electric Company, GE CONFIDENTIAL UNPUBLISHED WORK.
Drg
No:
M1
M2
* POWER SUPPLY VERSION 24-48V (NOMINAL) D.C. ONLY
K18
K17
K16
K15
*
M16
SCN
M18
M17
SEE DRAWING
10Px4001
SEE DRAWING
10Px4001
MiCOM P746 (PART)
+
-
+
-
AC OR DC
x AUX SUPPLY
EIA485/
KBUS
PORT
COMMS OPTIONS
10P74601
Next
Sht:
Sht:
1
-
C
St Leonards Building
Harry Kerr Drive, Stafford.
ST16 1WT, UK
UK Grid Solutions Ltd
EXT. CONNECTION DIAG: P746 BUSBAR PROTECTION (80TE)
WITH 16 I/P & 16 O/P
RELAY 16
RELAY 15
K14
G13
K12
K11
K10
K9
K8
K7
K6
K5
K4
K3
K2
K1
L18
L17
L15
L16
L14
L12
L13
L11
L10
L9
L8
H7
L6
L5
L4
L3
L2
L1
M14
M13
M12
M11
K13
RELAY 14
RELAY 13
RELAY 12
RELAY 11
RELAY 10
RELAY 9
RELAY 8
RELAY 7
RELAY 6
RELAY 5
RELAY 4
RELAY 3
RELAY 2
RELAY 1
WATCHDOG
CONTACT
WATCHDOG
CONTACT
G12
G11
G10
G9
G8
G7
G6
G5
G4
G3
G2
G1
E18
E17
E16
E15
E14
E13
E12
E11
E10
E9
E8
E7
E6
E5
E4
E3
E2
E1
SEE DRAWING 10P74600 FOR RELAY CONNECTIONS TO SYSTEM
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
CID006234 Outlines updated to GE Format
Revision:
COMMON
CONNECTION
OPTO 16
OPTO 15
OPTO 14
OPTO 13
OPTO 12
OPTO 11
OPTO 10
OPTO 9
COMMON
CONNECTION
OPTO 8
OPTO 7
OPTO 6
OPTO 5
OPTO 4
OPTO 3
OPTO 2
OPTO 1
MiCOM P746 (PART)
Date:
Date:
Issue:
4/30/2020
E
-
G18
G17
G16
G15
G14
G13
G12
G11
G10
G9
G8
G7
G6
G5
G4
G3
G2
G1
E18
E17
E16
E15
E14
E13
E12
E11
E10
E9
E8
E7
E6
E5
E4
E3
E2
E1
SEE DRAWING 10P74600 FOR RELAY CONNECTIONS TO SYSTEM
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
Chkd:
Name:
S.J.BURTON
Drg
No:
Title:
HIGH BREAK
CONTACTS
GE PROPRIETARY AND CONFIDENTIAL INFORMATION
This document is the property of General Electric Company ("GE") and contains proprietary information of GE. This document is loaned on the express
condition that neither it nor the information contained therein shall be disclosed to others without the express written consent of GE, and that the information
shall be used by the recipient only as approved expressly by GE. This document shall be returned to GE upon its request. This document may be subject to
certain restrictions under U.S. export control laws and regulations.© General Electric Company, GE CONFIDENTIAL UNPUBLISHED WORK.
CID006234 Outlines updated to GE Format
Revision:
COMMON
CONNECTION
OPTO 16
OPTO 15
OPTO 14
OPTO 13
OPTO 12
OPTO 11
OPTO 10
OPTO 9
COMMON
CONNECTION
OPTO 8
OPTO 7
OPTO 6
OPTO 5
OPTO 4
OPTO 3
OPTO 2
OPTO 1
MiCOM P746 (PART)
*
SEE DRAWING
10Px4001
M2
M1
M16
SCN
M18
M17
SEE DRAWING
10Px4001
B16
B15
B12
B11
B8
B7
B4
B3
* POWER SUPPLY VERSION 24-48V (NOMINAL) D.C. ONLY
C16
C15
C12
C11
C8
C7
C4
C3
L18
L17
L15
L16
L14
L12
L13
L11
L10
L9
L8
H7
L6
L5
L4
L3
L2
L1
M14
M13
M12
M11
MiCOM P746 (PART)
+
-
+
-
+
-
+
-
+
-
+
-
HIGH BREAK
CONTACTS
AC OR DC
x AUX SUPPLY
EIA485/
KBUS
PORT
COMMS OPTIONS
RELAY 16
RELAY 15
RELAY 14
RELAY 13
10P74602
Next
Sht:
Sht:
1
-
C
St Leonards Building
Harry Kerr Drive, Stafford.
ST16 1WT, UK
UK Grid Solutions Ltd
EXT. CONNECTION DIAG: P746 BUSBAR PROTECTION (80TE)
WITH 16 I/P & 16 O/P (8 O/P ARE HIGH BREAK)
RELAY 12
RELAY 11
RELAY 10
RELAY 9
RELAY 8
RELAY 7
RELAY 6
RELAY 5
RELAY 4
RELAY 3
RELAY 2
RELAY 1
WATCHDOG
CONTACT
WATCHDOG
CONTACT
+
-
+
-
+
-
+
-
Date:
Date:
Issue:
4/30/2020
E
-
G18
G17
G16
G15
Chkd:
Name:
K18
K17
K16
K15
K14
G13
G14
K13
K12
K11
G12
G11
G10
K10
K9
K8
G8
G9
K7
K6
K5
K4
G7
G6
G5
G4
K2
K3
K1
G3
L18
L17
L15
L16
L14
L12
L13
L11
L10
L9
L8
H7
L6
L5
L4
L3
G2
G1
E18
E17
E16
E15
E14
E13
E12
E11
E10
E9
E8
E7
E6
L1
E5
L2
M14
M13
M12
M11
E4
E3
E2
E1
RELAY 16
RELAY 15
RELAY 14
RELAY 13
RELAY 12
RELAY 11
RELAY 10
RELAY 9
RELAY 8
RELAY 7
RELAY 6
RELAY 5
RELAY 4
RELAY 3
RELAY 2
S.J.BURTON
Title:
GE PROPRIETARY AND CONFIDENTIAL INFORMATION
This document is the property of General Electric Company ("GE") and contains proprietary information of GE. This document is loaned on the express
condition that neither it nor the information contained therein shall be disclosed to others without the express written consent of GE, and that the information
shall be used by the recipient only as approved expressly by GE. This document shall be returned to GE upon its request. This document may be subject to
certain restrictions under U.S. export control laws and regulations.© General Electric Company, GE CONFIDENTIAL UNPUBLISHED WORK.
Drg
No:
*
SEE DRAWING
10Px4001
M2
M1
M16
SCN
M18
M17
SEE DRAWING
10Px4001
* POWER SUPPLY VERSION 24-48V (NOMINAL) D.C. ONLY
H18
H17
H16
H15
H14
H13
H12
H11
H10
H9
H8
H7
H6
H5
H4
H3
H2
H1
J18
J17
J15
J16
J14
J12
J13
J11
J10
J9
J8
J7
L6
J5
J4
J3
J2
J1
MiCOM P746 (PART)
+
-
+
-
AC OR DC
x AUX SUPPLY
EIA485/
KBUS
PORT
COMMS OPTIONS
10P74603
Next
Sht:
Sht:
1
-
C
St Leonards Building
Harry Kerr Drive, Stafford.
ST16 1WT, UK
UK Grid Solutions Ltd
EXT. CONNECTION DIAG: P746 BUSBAR PROTECTION (80TE)
WITH 16 I/P & 32 O/P
RELAY 32
RELAY 31
RELAY 30
RELAY 29
RELAY 28
RELAY 27
RELAY 25
RELAY 25
RELAY 24
RELAY 23
RELAY 22
RELAY 21
RELAY 20
RELAY 19
RELAY 18
WATCHDOG
CONTACT
RELAY 1
RELAY 17
WATCHDOG
CONTACT
SEE DRAWING 10P74600 FOR RELAY CONNECTIONS TO SYSTEM
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
CID006234 Outlines updated to GE Format
Revision:
COMMON
CONNECTION
OPTO 16
OPTO 15
OPTO 14
OPTO 13
OPTO 12
OPTO 11
OPTO 10
OPTO 9
COMMON
CONNECTION
OPTO 8
OPTO 7
OPTO 6
OPTO 5
OPTO 4
OPTO 3
OPTO 2
OPTO 1
MiCOM P746 (PART)
Date:
Date:
Issue:
4/30/2020
F
-
G18
G17
G16
G15
Chkd:
Name:
K18
K17
K16
K15
K14
G13
G14
K13
K12
K11
K10
G12
G11
G10
K9
K8
G8
G9
K7
K6
K5
K4
G7
G6
G5
K3
K2
G4
K1
G3
L18
L17
L15
L16
L14
L12
L13
L11
L10
L9
L8
H7
L6
L5
L4
L3
G2
G1
E18
E17
E16
E15
E14
E13
E12
E11
E10
E9
E8
E7
E6
L1
E5
L2
M14
M13
M12
M11
E4
E3
E2
E1
RELAY 16
RELAY 15
RELAY 14
RELAY 13
RELAY 12
RELAY 11
RELAY 10
RELAY 9
RELAY 8
RELAY 7
RELAY 6
RELAY 5
RELAY 4
RELAY 3
RELAY 2
S.J.BURTON
HIGH BREAK
CONTACTS
GE PROPRIETARY AND CONFIDENTIAL INFORMATION
This document is the property of General Electric Company ("GE") and contains proprietary information of GE. This document is loaned on the express
condition that neither it nor the information contained therein shall be disclosed to others without the express written consent of GE, and that the information
shall be used by the recipient only as approved expressly by GE. This document shall be returned to GE upon its request. This document may be subject to
certain restrictions under U.S. export control laws and regulations.© General Electric Company, GE CONFIDENTIAL UNPUBLISHED WORK.
Drg
No:
Title:
*
SEE DRAWING
10Px4001
M2
M1
M16
SCN
M18
M17
SEE DRAWING
10Px4001
* POWER SUPPLY VERSION 24-48V (NOMINAL) D.C. ONLY
H16
H15
H12
C11
H8
H7
H4
H3
J18
J17
J15
J16
J14
J12
J13
J11
J10
J9
J8
J7
L6
J5
J4
J3
J2
J1
MiCOM P746 (PART)
+
-
+
-
10P74604-1E
AC OR DC
x AUX SUPPLY
EIA485/
KBUS
PORT
COMMS OPTIONS
10P74604
Next
Sht:
Sht:
1
-
C
St Leonards Building
Harry Kerr Drive, Stafford.
ST16 1WT, UK
UK Grid Solutions Ltd
EXT. CONNECTION DIAG: P746 BUSBAR PROTECTION (80TE)
WITH 16 I/P & 28 O/P (4 O/P ARE HIGH BREAK)
RELAY 28
RELAY 27
RELAY 26
RELAY 25
RELAY 24
RELAY 23
RELAY 22
RELAY 21
RELAY 20
RELAY 19
RELAY 18
WATCHDOG
CONTACT
RELAY 1
RELAY 17
WATCHDOG
CONTACT
SEE DRAWING 10P74600 FOR RELAY CONNECTIONS TO SYSTEM
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
CID006234 Outlines updated to GE Format
Revision:
COMMON
CONNECTION
OPTO 16
OPTO 15
OPTO 14
OPTO 13
OPTO 12
OPTO 11
OPTO 10
OPTO 9
COMMON
CONNECTION
OPTO 8
OPTO 7
OPTO 6
OPTO 5
OPTO 4
OPTO 3
OPTO 2
OPTO 1
MiCOM P746 (PART)
+
-
+
-
+
-
+
-
Date:
Date:
Issue:
4/30/2020
E
H17
H18
E17
E18
Chkd:
Name:
S.J.BURTON
Title:
J17
J18
L14
K12
K11
K10
K9
K8
K7
K6
K5
K4
K3
K2
K1
L18
L17
G18
G17
G16
G15
G14
GE PROPRIETARY AND CONFIDENTIAL INFORMATION
This document is the property of General Electric Company ("GE") and contains proprietary information of GE. This document is loaned on the express
condition that neither it nor the information contained therein shall be disclosed to others without the express written consent of GE, and that the information
shall be used by the recipient only as approved expressly by GE. This document shall be returned to GE upon its request. This document may be subject to
certain restrictions under U.S. export control laws and regulations.© General Electric Company, GE CONFIDENTIAL UNPUBLISHED WORK.
Drg
No:
M2
M1
M16
SCN
M18
M17
* POWER SUPPLY VERSION 24-48V (NOMINAL) D.C. ONLY
K18
K17
K16
*
SEE DRAWING
10Px4001
+
-
+
-
AC OR DC
x AUX SUPPLY
EIA485/
KBUS
PORT
COMMS OPTIONS
RELAY 24
RELAY 23
RELAY 22
RELAY 21
RELAY 20
RELAY 19
RELAY 18
RELAY 17
10P74605
Next
Sht:
Sht:
1
-
C
St Leonards Building
Harry Kerr Drive, Stafford.
ST16 1WT, UK
UK Grid Solutions Ltd
EXT. CONNECTION DIAG: P746 BUSBAR PROTECTION (80TE)
WITH 24 I/P & 24 O/P
RELAY 16
K15
K14
RELAY 15
J16
L12
L13
SEE DRAWING
10Px4001
J15
L15
L16
J14
J10
L6
L11
J9
L5
L10
J8
L4
J13
J7
L3
J12
J6
L2
L9
J5
L1
L8
J4
M14
J11
J3
H7
J2
M13
G13
RELAY 14
RELAY 13
RELAY 12
RELAY 11
RELAY 10
RELAY 9
RELAY 8
RELAY 7
RELAY 6
RELAY 5
RELAY 4
RELAY 3
RELAY 2
RELAY 1
WATCHDOG
CONTACT
J1
M12
MiCOM P746 (PART)
M11
K13
COMMON
CONNECTION
OPTO 24
OPTO 23
OPTO 22
OPTO 21
OPTO 20
OPTO 19
OPTO 18
WATCHDOG
CONTACT
G12
G11
G10
G9
G8
G7
G6
G5
G4
G3
G2
G1
H16
H15
E16
H14
E15
H13
E13
E14
H12
H11
E11
E12
H10
H9
E9
E10
H8
H7
E7
E8
H6
H5
E5
E6
H4
E4
OPTO 17
SEE DRAWING 10P74600 FOR RELAY CONNECTIONS TO SYSTEM
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
H3
E3
CID006234 Outlines updated to GE Format
Revision:
COMMON
CONNECTION
OPTO 16
OPTO 15
OPTO 14
OPTO 13
OPTO 12
OPTO 11
OPTO 10
OPTO 9
COMMON
CONNECTION
OPTO 8
OPTO 7
OPTO 6
OPTO 5
OPTO 4
OPTO 3
OPTO 2
-
H2
+
H1
+
E2
+
E1
+
-
+
+
+
OPTO 1
+
MiCOM P746 (PART)
+
Date:
Date:
Issue:
4/30/2020
E
H18
E18
G18
G17
G16
G15
G14
G13
Chkd:
Name:
J16
J15
J12
J11
G11
G12
J8
J7
J4
G10
G9
G8
G7
G6
G5
G4
G3
G2
J3
H17
E17
G1
H16
H15
E16
H14
E15
H13
E13
E14
H12
H11
E11
E12
H10
H9
E9
E10
H8
H7
E7
E8
H6
H5
E5
E6
H4
E4
H3
E3
+
-
+
-
+
-
+
-
RELAY 20
RELAY 19
RELAY 18
RELAY 17
S.J.BURTON
GE PROPRIETARY AND CONFIDENTIAL INFORMATION
This document is the property of General Electric Company ("GE") and contains proprietary information of GE. This document is loaned on the express
condition that neither it nor the information contained therein shall be disclosed to others without the express written consent of GE, and that the information
shall be used by the recipient only as approved expressly by GE. This document shall be returned to GE upon its request. This document may be subject to
certain restrictions under U.S. export control laws and regulations.© General Electric Company, GE CONFIDENTIAL UNPUBLISHED WORK.
HIGH BREAK
CONTACTS
COMMON
CONNECTION
OPTO 24
OPTO 23
OPTO 22
OPTO 21
OPTO 20
OPTO 19
OPTO 18
OPTO 17
SEE DRAWING 10P74600 FOR RELAY CONNECTIONS TO SYSTEM
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
CID006234 Outlines updated to GE Format
Revision:
COMMON
CONNECTION
OPTO 16
OPTO 15
OPTO 14
OPTO 13
OPTO 12
OPTO 11
OPTO 10
OPTO 9
COMMON
CONNECTION
OPTO 8
OPTO 7
OPTO 6
OPTO 5
OPTO 4
OPTO 3
OPTO 2
H2
+
H1
+
E2
+
E1
+
-
+
+
+
OPTO 1
+
MiCOM P746 (PART)
+
Drg
No:
Title:
*
SEE DRAWING
10Px4001
M2
M1
M16
SCN
M18
M17
SEE DRAWING
10Px4001
C16
C15
C12
C11
C8
C7
C4
C3
* POWER SUPPLY VERSION 24-48V (NOMINAL) D.C. ONLY
K18
K17
K16
K15
K14
K13
K12
K11
K10
K9
K8
K7
K6
K5
K4
K3
K2
K1
L18
L17
L15
L16
L14
L12
L13
L11
L10
L9
L8
H7
L6
L5
L4
L3
L2
L1
M14
M13
M12
M11
+
-
+
-
+
-
+
-
+
-
+
-
HIGH BREAK
CONTACTS
AC OR DC
x AUX SUPPLY
EIA485/
KBUS
PORT
COMMS OPTIONS
RELAY 24
RELAY 23
RELAY 22
RELAY 21
10P74606
Next
Sht:
Sht:
1
-
C
St Leonards Building
Harry Kerr Drive, Stafford.
ST16 1WT, UK
UK Grid Solutions Ltd
EXT. CONNECTION DIAG: P746 BUSBAR PROTECTION (80TE)
WITH 24 I/P & 24 O/P (8 O/P ARE HIGH BREAK)
RELAY 16
RELAY 15
RELAY 14
RELAY 13
RELAY 12
RELAY 11
RELAY 10
RELAY 9
RELAY 8
RELAY 7
RELAY 6
RELAY 5
RELAY 4
RELAY 3
RELAY 2
RELAY 1
WATCHDOG
CONTACT
WATCHDOG
CONTACT
MiCOM P746 (PART)
Date:
Date:
Issue:
4/30/2020
F
H18
E18
G18
G17
G16
G15
G14
G13
Chkd:
Name:
J16
J15
J12
J11
J8
J7
G11
G12
J4
J3
G10
G9
G8
G7
G6
G5
G4
G3
G2
SEE DRAWING
10Px4001
H17
E17
G1
H16
H15
E15
E16
H14
H13
E13
E14
H12
H11
E11
E12
H10
H9
E9
E10
H8
H7
E7
E8
H6
H5
E5
E6
H4
E4
H3
E3
+
-
+
-
+
-
+
-
RELAY 16
RELAY 15
RELAY 14
RELAY 13
S.J.BURTON
GE PROPRIETARY AND CONFIDENTIAL INFORMATION
This document is the property of General Electric Company ("GE") and contains proprietary information of GE. This document is loaned on the express
condition that neither it nor the information contained therein shall be disclosed to others without the express written consent of GE, and that the information
shall be used by the recipient only as approved expressly by GE. This document shall be returned to GE upon its request. This document may be subject to
certain restrictions under U.S. export control laws and regulations.© General Electric Company, GE CONFIDENTIAL UNPUBLISHED WORK.
Drg
No:
Title:
RELAY 12
RELAY 11
RELAY 10
RELAY 9
RELAY 8
RELAY 7
RELAY 6
RELAY 5
RELAY 4
RELAY 3
RELAY 2
RELAY 1
WATCHDOG
CONTACT
WATCHDOG
CONTACT
SEE DRAWING
10Px4001
*
M2
M1
M16
SCN
M18
M17
C16
* POWER SUPPLY VERSION 24-48V (NOMINAL) D.C. ONLY
K16
K15
K12
K11
K8
K7
K4
K3
L18
L17
L15
L16
L14
L12
L13
L11
L10
C15
C12
L9
L8
C11
C8
C7
C4
C3
H7
L6
L5
L4
L3
L2
L1
M14
M13
M12
M11
MiCOM P746 (PART)
+
-
+
-
+
-
+
-
+
-
+
-
AC OR DC
HIGH BREAK
CONTACTS
x AUX SUPPLY
EIA485/
KBUS
PORT
RELAY 20
RELAY 19
RELAY 18
RELAY 17
10P74607
Next
Sht:
Sht:
1
-
C
St Leonards Building
Harry Kerr Drive, Stafford.
ST16 1WT, UK
UK Grid Solutions Ltd
EXTERNAL CONNECTION DIAG: P746 BUSBAR PROTECTION
WITH 24 I/P & 20 O/P (12 O/P ARE HIGH BREAK)
HIGH BREAK
CONTACTS
HIGH BREAK
CONTACTS
COMMS OPTIONS
COMMON
CONNECTION
OPTO 24
OPTO 23
OPTO 22
OPTO 21
OPTO 20
OPTO 19
OPTO 18
OPTO 17
SEE DRAWING 10P74600 FOR RELAY CONNECTIONS TO SYSTEM
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
CID006234 Outlines updated to GE Format
Revision:
COMMON
CONNECTION
OPTO 16
OPTO 15
OPTO 14
OPTO 13
OPTO 12
OPTO 11
OPTO 10
OPTO 9
COMMON
CONNECTION
OPTO 8
OPTO 7
OPTO 6
OPTO 5
OPTO 4
OPTO 3
OPTO 2
H2
+
H1
+
E2
+
E1
+
-
+
+
+
OPTO 1
+
MiCOM P746 (PART)
+
-
+
-
+
-
+
-
+
Date:
Date:
Issue:
4/30/2020
E
C16
C17
C18
G17
G18
C15
G15
G16
C14
C13
G13
G14
C12
C11
G11
G12
C10
C9
G9
G10
C8
C7
G7
G8
C6
C5
G5
G6
C4
G4
C3
C1
G1
G3
H18
E18
C2
H17
E17
G2
H16
H15
E16
H14
E15
H13
E13
E14
H12
H11
E11
E12
H10
H9
E9
E10
H8
H7
E7
E8
H6
E6
Chkd:
Name:
COMMON
CONNECTION
OPTO 32
OPTO 31
OPTO 30
OPTO 29
OPTO 28
OPTO 27
OPTO 26
OPTO 25
COMMON
CONNECTION
OPTO 24
OPTO 23
OPTO 22
OPTO 21
OPTO 20
OPTO 19
OPTO 18
OPTO 17
SEE DRAWING 10P74600 FOR RELAY CONNECTIONS TO SYSTEM
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
H5
E5
S.J.BURTON
GE PROPRIETARY AND CONFIDENTIAL INFORMATION
This document is the property of General Electric Company ("GE") and contains proprietary information of GE. This document is loaned on the express
condition that neither it nor the information contained therein shall be disclosed to others without the express written consent of GE, and that the information
shall be used by the recipient only as approved expressly by GE. This document shall be returned to GE upon its request. This document may be subject to
certain restrictions under U.S. export control laws and regulations.© General Electric Company, GE CONFIDENTIAL UNPUBLISHED WORK.
CID006234 Outlines updated to GE Format
Revision:
COMMON
CONNECTION
OPTO 16
OPTO 15
OPTO 14
OPTO 13
OPTO 12
OPTO 11
OPTO 10
OPTO 9
COMMON
CONNECTION
OPTO 8
OPTO 7
OPTO 6
OPTO 5
OPTO 4
OPTO 3
-
+
H4
+
E4
+
+
+
OPTO 2
+
H3
+
E3
+
-
+
H2
+
H1
+
E2
+
E1
+
-
+
+
+
OPTO 1
+
MiCOM P746 (PART)
+
Drg
No:
Title:
J17
J18
L14
*
SEE DRAWING
10Px4001
M2
M1
M16
SCN
M18
M17
* POWER SUPPLY VERSION 24-48V (NOMINAL) D.C. ONLY
K18
K17
K16
K15
K14
K13
K12
K11
K10
K9
K8
K7
K6
K5
K4
K3
K2
K1
L18
L17
SEE DRAWING
10Px4001
J16
L12
L13
L15
L16
J15
J10
L6
J14
J9
L5
L11
J8
L4
L10
J7
L3
J13
J6
L2
J12
J5
L1
L9
J4
M14
L8
J3
M13
J11
J2
M12
H7
J1
M11
+
-
+
-
AC OR DC
x AUX SUPPLY
EIA485/
KBUS
PORT
COMMS OPTIONS
RELAY 24
RELAY 23
RELAY 22
RELAY 21
RELAY 20
RELAY 19
RELAY 18
RELAY 17
10P74608
1
2
Sht:
Next
Sht:
C
St Leonards Building
Harry Kerr Drive, Stafford.
ST16 1WT, UK
UK Grid Solutions Ltd
EXT. CONNECTION DIAG: P746 BUSBAR PROTECTION (80TE)
WITH 32 I/P & 24 O/P
RELAY 16
RELAY 15
RELAY 14
RELAY 13
RELAY 12
RELAY 11
RELAY 10
RELAY 9
RELAY 8
RELAY 7
RELAY 6
RELAY 5
RELAY 4
RELAY 3
RELAY 2
RELAY 1
WATCHDOG
CONTACT
WATCHDOG
CONTACT
MiCOM P746 (PART)
Date:
Date:
Issue:
4/30/2020
E
C16
C17
C18
G17
G18
C15
G16
C14
G15
C13
G13
G14
C12
C11
G11
G12
C10
C9
G9
G10
C8
C7
G7
G8
C6
C5
G5
G6
C4
G4
C3
C1
G1
C2
H18
E18
G3
H17
G2
H16
E17
H15
E15
E16
H14
H13
E13
E14
H12
H11
E11
E12
H10
H9
E9
E10
H8
H7
E7
E8
H6
E6
Chkd:
Name:
S.J.BURTON
COMMON
CONNECTION
OPTO 32
OPTO 31
OPTO 30
OPTO 29
OPTO 28
OPTO 27
OPTO 26
OPTO 25
COMMON
CONNECTION
OPTO 24
OPTO 23
OPTO 22
OPTO 21
OPTO 20
OPTO 19
GE PROPRIETARY AND CONFIDENTIAL INFORMATION
This document is the property of General Electric Company ("GE") and contains proprietary information of GE. This document is loaned on the express
condition that neither it nor the information contained therein shall be disclosed to others without the express written consent of GE, and that the information
shall be used by the recipient only as approved expressly by GE. This document shall be returned to GE upon its request. This document may be subject to
certain restrictions under U.S. export control laws and regulations.© General Electric Company, GE CONFIDENTIAL UNPUBLISHED WORK.
CID006234 Outlines updated to GE Format
Revision:
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
H5
E5
OPTO 18
OPTO 17
SEE DRAWING 10P74600 FOR RELAY CONNECTIONS TO SYSTEM
COMMON
CONNECTION
OPTO 16
OPTO 15
OPTO 14
OPTO 13
OPTO 12
OPTO 11
OPTO 10
OPTO 9
COMMON
CONNECTION
OPTO 8
OPTO 7
OPTO 6
OPTO 5
OPTO 4
OPTO 3
-
+
+
+
H4
+
H3
+
E4
+
E3
+
-
+
OPTO 2
+
H2
+
E2
+
+
+
OPTO 1
+
H1
+
E1
+
-
+
MiCOM P746 (PART)
+
Drg
No:
Title:
SEE DRAWING
10Px4001
M2
M1
M16
SCN
M18
M17
B16
B15
B12
* POWER SUPPLY VERSION 24-48V (NOMINAL) D.C. ONLY
SEE DRAWING
10Px4001
K18
K17
K16
K15
K14
K13
K12
K11
K10
K9
K8
K7
K6
K5
K4
K3
K2
K1
L18
*
B8
B11
B7
L15
L16
L17
B4
L14
B3
J16
J15
J12
J11
J8
J7
J4
J3
L12
L13
L11
L10
L9
L8
H7
L6
L5
L4
L3
L2
L1
M14
M13
M12
MiCOM P746 (PART)
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
AC OR DC
HIGH BREAK
CONTACTS
HIGH BREAK
CONTACTS
x AUX SUPPLY
EIA485/
KBUS
PORT
RELAY 24
RELAY 23
RELAY 22
RELAY 21
RELAY 20
RELAY 19
RELAY 18
RELAY 17
10P74609
Next
Sht:
Sht:
1
-
C
St Leonards Building
Harry Kerr Drive, Stafford.
ST16 1WT, UK
UK Grid Solutions Ltd
EXTERNAL CONNECTION DIAG: P746 BUSBAR PROTECTION (80TE)
WITH 32 I/P & 24 O/P (8 O/P ARE HIGH BREAK)
COMMS OPTIONS
RELAY 16
RELAY 15
RELAY 14
RELAY 13
RELAY 12
RELAY 11
RELAY 10
RELAY 9
RELAY 8
RELAY 7
RELAY 6
RELAY 5
RELAY 4
RELAY 3
RELAY 2
RELAY 1
WATCHDOG
CONTACT
WATCHDOG
CONTACT
M11
Date:
Date:
Issue:
4/30/2020
E
J3
J4
J5
J6
J7
J8
J9
J10
J11
J12
J13
J14
J15
J16
J17
J18
M13
M14
L1
L2
L3
L4
L5
L6
H7
L8
L9
L10
L11
L12
L13
L14
Chkd:
Name:
*
SEE DRAWING
10Px4001
M2
M1
M16
SCN
M18
M17
+
-
+
-
S.J.BURTON
GE PROPRIETARY AND CONFIDENTIAL INFORMATION
This document is the property of General Electric Company ("GE") and contains proprietary information of GE. This document is loaned on the express
condition that neither it nor the information contained therein shall be disclosed to others without the express written consent of GE, and that the information
shall be used by the recipient only as approved expressly by GE. This document shall be returned to GE upon its request. This document may be subject to
certain restrictions under U.S. export control laws and regulations.© General Electric Company, GE CONFIDENTIAL UNPUBLISHED WORK.
AC OR DC
x AUX SUPPLY
EIA485/
KBUS
PORT
COMMS OPTIONS
RELAY 24
RELAY 23
RELAY 22
RELAY 21
RELAY 20
RELAY 19
RELAY 18
RELAY 17
SEE DRAWING 10P74600 FOR RELAY CONNECTIONS TO SYSTEM
* POWER SUPPLY VERSION 24-48V (NOMINAL) D.C. ONLY
K18
K17
K16
K15
K14
K13
K12
K11
K10
K9
K8
K7
K6
K5
K4
K3
K2
K1
L18
L17
SEE DRAWING
10Px4001
J2
M12
L15
L16
J1
M11
CID006234 Outlines updated to GE Format
Revision:
RELAY 16
RELAY 15
RELAY 14
RELAY 13
RELAY 12
RELAY 11
RELAY 10
RELAY 9
RELAY 8
RELAY 7
RELAY 6
RELAY 5
RELAY 4
RELAY 3
RELAY 2
RELAY 1
WATCHDOG
CONTACT
WATCHDOG
CONTACT
Drg
No:
Title:
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
B9
H1
B18
B17
B16
B15
H8
B14
H7
B13
H6
B12
H5
B11
H4
H3
B10
B8
G18
H2
B7
B6
B5
B4
B3
B2
B1
G17
G16
G15
G14
G13
G12
G11
C18
C17
G10
C16
G9
C15
C14
C13
G8
G7
G6
G5
C12
C11
G4
C10
C9
G1
G3
C8
E18
G2
C7
E17
C6
C5
E16
C4
E15
C3
E14
C2
E13
C1
E12
E11
H18
H17
E10
H16
E9
H15
H14
E8
E7
E6
COMMON
CONNECTION
OPTO 40
OPTO 39
OPTO 38
OPTO 37
OPTO 36
OPTO 35
OPTO 34
OPTO 33
COMMON
CONNECTION
OPTO 32
OPTO 31
OPTO 30
OPTO 29
OPTO 28
OPTO 27
OPTO 26
OPTO 25
COMMON
CONNECTION
OPTO 24
OPTO 23
OPTO 22
OPTO 21
10P74610
Next
Sht:
Sht:
1
-
C
St Leonards Building
Harry Kerr Drive, Stafford.
ST16 1WT, UK
UK Grid Solutions Ltd
EXT. CONNECTION DIAG: P746 BUSBAR PROTECTION (80TE)
WITH 40 I/P & 24 O/P
OPTO 20
OPTO 19
OPTO 18
OPTO 17
COMMON
CONNECTION
OPTO 16
OPTO 15
OPTO 14
OPTO 13
OPTO 12
OPTO 11
OPTO 10
OPTO 9
COMMON
CONNECTION
OPTO 8
OPTO 7
OPTO 6
OPTO 5
OPTO 4
OPTO 3
+
H13
+
H12
+
E5
+
E4
+
-
+
-
+
+
+
OPTO 2
+
MiCOM P746 (PART)
+
H11
+
H10
+
E3
+
H9
+
E2
+
-
+
+
+
OPTO 1
+
MiCOM P746 (PART)
+
E1
+
Date:
Date:
Issue:
4/30/2020
D
B6
B7
B8
L5
L6
H7
B11
B12
B13
L10
L11
L12
L13
Chkd:
Name:
S.J.BURTON
*
SEE DRAWING
10Px4001
M2
M1
M16
SCN
M18
M17
SEE DRAWING
10Px4001
B18
* POWER SUPPLY VERSION 24-48V (NOMINAL) D.C. ONLY
J18
J17
J16
J15
J14
J13
J12
J11
J10
J9
J8
J7
J6
J5
J4
J3
J2
J1
K18
K17
K16
K15
K14
K13
K12
K11
K10
K9
K8
K7
K6
K5
K4
K3
K2
K1
L18
L17
B16
L15
L16
B17
B15
L14
B14
B10
L9
B9
B5
L4
L8
B4
L3
B3
B2
L2
L1
+
-
+
-
AC OR DC
OPTO 20
OPTO 19
OPTO 18
OPTO 17
COMMON
CONNECTION
OPTO 16
OPTO 15
OPTO 14
OPTO 13
OPTO 12
OPTO 11
OPTO 10
OPTO 9
COMMON
CONNECTION
OPTO 8
OPTO 7
OPTO 6
OPTO 5
OPTO 4
OPTO 3
OPTO 2
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
H8
H7
H6
H5
H4
H3
H2
H1
G18
G17
G16
G15
G14
G13
G12
G11
G10
G9
Drg
No:
Title:
COMMON
CONNECTION
OPTO 32
OPTO 31
OPTO 30
OPTO 29
OPTO 28
OPTO 27
OPTO 26
OPTO 25
COMMON
CONNECTION
OPTO 24
OPTO 23
OPTO 22
OPTO 21
10P74611
Next
Sht:
Sht:
1
-
C
St Leonards Building
Harry Kerr Drive, Stafford.
ST16 1WT, UK
UK Grid Solutions Ltd
EXT. CONNECTION DIAG: P746 BUSBAR PROTECTION (80TE)
WITH 32 I/P & 32 O/P
C18
C17
C16
C15
G8
C14
G7
C13
G5
G6
C12
G4
C11
C9
G1
C10
C8
E18
G3
C7
G2
C6
E17
C5
C4
C3
C2
C1
E16
E15
E14
E13
E12
E11
H18
H17
E10
H16
E9
H15
E8
H14
E7
H13
E6
E5
H12
H11
E4
H10
E3
H9
E2
E1
SEE DRAWING 10P74600 FOR RELAY CONNECTIONS TO SYSTEM
x AUX SUPPLY
EIA485/
KBUS
PORT
COMMS OPTIONS
RELAY 32
RELAY 31
RELAY 30
RELAY 29
RELAY 28
RELAY 27
RELAY 26
GE PROPRIETARY AND CONFIDENTIAL INFORMATION
This document is the property of General Electric Company ("GE") and contains proprietary information of GE. This document is loaned on the express
condition that neither it nor the information contained therein shall be disclosed to others without the express written consent of GE, and that the information
shall be used by the recipient only as approved expressly by GE. This document shall be returned to GE upon its request. This document may be subject to
certain restrictions under U.S. export control laws and regulations.© General Electric Company, GE CONFIDENTIAL UNPUBLISHED WORK.
CID006234 Outlines updated to GE Format
Revision:
RELAY 24
RELAY 23
RELAY 22
RELAY 21
RELAY 20
RELAY 19
RELAY 18
RELAY 17
RELAY 16
RELAY 15
RELAY 14
RELAY 13
RELAY 12
RELAY 11
RELAY 10
RELAY 9
RELAY 8
RELAY 7
RELAY 6
RELAY 5
RELAY 4
RELAY 3
RELAY 2
RELAY 1
+
+
OPTO 1
+
RELAY 25
+
B1
+
M14
+
M13
+
WATCHDOG
CONTACT
+
MiCOM P746 (PART)
+
MiCOM P746 (PART)
+
M12
+
M11
+
WATCHDOG
CONTACT
+
Name:
Chkd:
07/05/2012
Date:
TX
5
F18
F17
F16
F15
F14
N.ROBINSON
S.J.BURTON
RELAY 16
Drg
No:
Title:
P1
P2
* POWER SUPPLY VERSION 24-48V (NOMINAL) D.C. ONLY
M18
M17
M16
M15
*
P16
SCN
P18
P17
SEE DRAWING
10Px4001
SEE DRAWING
10Px4001
MiCOM P746 (PART)
+
-
+
-
AC OR DC
x AUX SUPPLY
EIA485/
KBUS
PORT
COMMS OPTIONS
10P74612
Next
Sht:
Sht:
1
-
C
St Leonards Building
Harry Kerr Drive, Stafford.
ST16 1WT, UK
UK Grid Solutions Ltd
EXT. CONNECTION DIAG: P746 BUSBAR PROTECTION (80TE)
WITH 16 I/P & 16 O/P NCIT
1. COPPER PORT IS FOR SERVICE ONLY, NOT
RECOMMENDED FOR PERMANENT CONNECTION
GE PROPRIETARY AND CONFIDENTIAL INFORMATION
This document is the property of General Electric Company ("GE") and contains proprietary information of GE. This document is loaned on the express
condition that neither it nor the information contained therein shall be disclosed to others without the express written consent of GE, and that the information
shall be used by the recipient only as approved expressly by GE. This document shall be returned to GE upon its request. This document may be subject to
certain restrictions under U.S. export control laws and regulations.© General Electric Company, GE CONFIDENTIAL UNPUBLISHED WORK.
RX
IEC 61850-9-2 LE
RELAY 15
M14
100 BASE-FX
M12
M11
M10
M9
M8
F13
RELAY 14
RELAY 13
RELAY 12
M7
M6
M5
M4
M3
M2
M1
N18
N17
N15
N16
N14
N12
N13
N11
N10
N9
N8
N7
N6
N5
N4
N3
N2
N1
P14
P13
P12
P11
M13
8
RX-
RELAY 11
RELAY 10
RELAY 9
RELAY 8
RELAY 7
RELAY 6
RELAY 5
RELAY 4
RELAY 3
RELAY 2
RELAY 1
WATCHDOG
CONTACT
WATCHDOG
CONTACT
F12
F11
F10
F9
F8
F7
6
7
IEC 61850-9-2 LE
4
SK6
100 BASE-TX
3
F6
TXRX+
F5
F4
1
2
F3
TX+
RJ45
F2
F1
G18
G17
G16
G15
G14
G13
G12
G11
G10
G9
G8
G7
G6
G5
G4
G3
G2
G1
CID006234 Outlines updated to GE Format
4/30/2020
E
Revision:
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
Date:
Issue:
COMMON
CONNECTION
OPTO 16
OPTO 15
OPTO 14
OPTO 13
OPTO 12
OPTO 11
OPTO 10
OPTO 9
COMMON
CONNECTION
OPTO 8
OPTO 7
OPTO 6
OPTO 5
OPTO 4
OPTO 3
OPTO 2
OPTO 1
MiCOM P746 (PART)
Name:
Chkd:
07/05/2012
Date:
N.ROBINSON
S.J.BURTON
SK6
8
6
7
4
5
3
1
2
RJ45
RX
TX
IEC 61850-9-2 LE
100 BASE-FX
IEC 61850-9-2 LE
100 BASE-TX
HIGH BREAK
CONTACTS
RELAY 12
RELAY 11
RELAY 10
RELAY 9
Drg
No:
Title:
RELAY 8
RELAY 7
RELAY 6
RELAY 5
RELAY 4
RELAY 3
RELAY 2
RELAY 1
WATCHDOG
CONTACT
WATCHDOG
CONTACT
*
SEE DRAWING
10Px4001
P2
P1
P16
SCN
P18
P17
SEE DRAWING
10Px4001
L16
L15
L12
L11
L8
L7
L4
L3
* POWER SUPPLY VERSION 24-48V (NOMINAL) D.C. ONLY
M16
M15
M12
M11
M8
M7
M4
M3
N18
N17
N15
N16
N14
N11
N12
N13
N10
N9
N8
N7
N6
N5
N4
N3
N2
P14
N1
P13
P12
P11
MiCOM P746 (PART)
+
-
+
-
+
-
+
-
+
-
+
-
HIGH BREAK
CONTACTS
AC OR DC
x AUX SUPPLY
EIA485/
KBUS
PORT
COMMS OPTIONS
RELAY 16
RELAY 15
RELAY 14
RELAY 13
10P74613
Next
Sht:
Sht:
1
-
C
St Leonards Building
Harry Kerr Drive, Stafford.
ST16 1WT, UK
UK Grid Solutions Ltd
EXT. CONNECTION DIAG: P746 BUSBAR PROTECTION (80TE)
WITH 16 I/P & 16 O/P (8 O/P ARE HIGH BREAK) NCIT
1. COPPER PORT IS FOR SERVICE ONLY, NOT
RECOMMENDED FOR PERMANENT CONNECTION
RX-
TXRX+
TX+
GE PROPRIETARY AND CONFIDENTIAL INFORMATION
This document is the property of General Electric Company ("GE") and contains proprietary information of GE. This document is loaned on the express
condition that neither it nor the information contained therein shall be disclosed to others without the express written consent of GE, and that the information
shall be used by the recipient only as approved expressly by GE. This document shall be returned to GE upon its request. This document may be subject to
certain restrictions under U.S. export control laws and regulations.© General Electric Company, GE CONFIDENTIAL UNPUBLISHED WORK.
CID006234 Outlines updated to GE Format
Revision:
F18
F17
F16
F15
F14
F13
F12
F11
F10
F9
F8
F7
F6
F5
F4
F3
F2
F1
G18
G17
G16
G15
G14
G13
G12
G11
G10
G9
G8
G7
G6
G5
G4
G3
G2
G1
4/30/2020
E
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
Date:
Issue:
COMMON
CONNECTION
OPTO 16
OPTO 15
OPTO 14
OPTO 13
OPTO 12
OPTO 11
OPTO 10
OPTO 9
COMMON
CONNECTION
OPTO 8
OPTO 7
OPTO 6
OPTO 5
OPTO 4
OPTO 3
OPTO 2
OPTO 1
MiCOM P746 (PART)
+
-
+
-
+
-
+
-
Name:
Chkd:
4/30/2020
07/05/2012
Date:
E
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
G5
F18
F17
F16
F15
N.ROBINSON
S.J.BURTON
RELAY 32
RELAY 31
RELAY 30
RELAY 29
RELAY 28
RELAY 27
RELAY 25
RELAY 25
RELAY 24
RELAY 23
RELAY 22
RELAY 21
RELAY 20
Drg
No:
Title:
SEE DRAWING
10Px4001
*
8
7
6
5
4
P2
P1
P16
SCN
P18
P17
SEE DRAWING
10Px4001
SK6
3
1
2
RJ45
* POWER SUPPLY VERSION 24-48V (NOMINAL) D.C. ONLY
K18
K17
K16
K15
K14
K13
K12
K11
K10
K9
K8
K7
K6
K5
K4
K3
K2
K1
L18
L17
L15
L16
L14
L12
L13
L11
L10
L9
L8
L7
L6
L5
L4
L3
L2
L1
MiCOM P746 (PART)
+
-
+
-
IEC 61850-9-2 LE
AC OR DC
x AUX SUPPLY
EIA485/
KBUS
PORT
IEC 61850-9-2 LE
100 BASE-TX
100 BASE-FX
COMMS OPTIONS
RX
TX
RX-
TXRX+
TX+
10P74614
Next
Sht:
Sht:
1
-
C
St Leonards Building
Harry Kerr Drive, Stafford.
ST16 1WT, UK
UK Grid Solutions Ltd
EXT. CONNECTION DIAG: P746 BUSBAR PROTECTION (80TE)
WITH 16 I/P & 32 O/P NCIT
1. COPPER PORT IS FOR SERVICE ONLY, NOT
RECOMMENDED FOR PERMANENT CONNECTION
RELAY 16
RELAY 15
RELAY 14
RELAY 13
RELAY 12
RELAY 11
RELAY 10
RELAY 9
RELAY 8
RELAY 7
RELAY 6
RELAY 5
RELAY 4
RELAY 3
RELAY 2
RELAY 19
RELAY 18
WATCHDOG
CONTACT
RELAY 1
RELAY 17
WATCHDOG
CONTACT
GE PROPRIETARY AND CONFIDENTIAL INFORMATION
This document is the property of General Electric Company ("GE") and contains proprietary information of GE. This document is loaned on the express
condition that neither it nor the information contained therein shall be disclosed to others without the express written consent of GE, and that the information
shall be used by the recipient only as approved expressly by GE. This document shall be returned to GE upon its request. This document may be subject to
certain restrictions under U.S. export control laws and regulations.© General Electric Company, GE CONFIDENTIAL UNPUBLISHED WORK.
M18
M17
M16
M15
M14
F13
F14
M13
M12
M11
F12
F11
F10
M10
M9
M8
F8
F9
M7
M6
M5
M4
F7
F6
F5
M3
M2
F4
M1
F3
N18
N17
N15
N16
N14
N12
N13
N11
N10
N9
N8
N7
N6
N5
N4
F2
F1
G18
G17
G16
G15
G14
G13
G12
G11
G10
G9
G8
G7
N3
N2
N1
G6
P14
P13
P12
P11
G4
G3
G2
G1
CID006234 Outlines updated to GE Format
Revision:
Date:
Issue:
COMMON
CONNECTION
OPTO 16
OPTO 15
OPTO 14
OPTO 13
OPTO 12
OPTO 11
OPTO 10
OPTO 9
COMMON
CONNECTION
OPTO 8
OPTO 7
OPTO 6
OPTO 5
OPTO 4
OPTO 3
OPTO 2
OPTO 1
MiCOM P746 (PART)
Name:
Chkd:
4/30/2020
07/05/2012
Date:
E
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
G5
F18
F17
F16
F15
N.ROBINSON
S.J.BURTON
HIGH BREAK
CONTACTS
RELAY 28
RELAY 27
RELAY 26
RELAY 25
RELAY 24
RELAY 23
RELAY 22
RELAY 21
RELAY 20
Drg
No:
Title:
*
SEE DRAWING
10Px4001
P2
P1
M16
SCN
P18
P17
* POWER SUPPLY VERSION 24-48V (NOMINAL) D.C. ONLY
K16
K15
K12
K11
K8
K7
K4
K3
L18
L17
L15
L16
L14
SEE DRAWING
10Px4001
8
L12
L13
7
-
TX
+
-
+
IEC 61850-9-2 LE
100 BASE-FX
AC OR DC
x AUX SUPPLY
EIA485/
KBUS
PORT
COMMS OPTIONS
RX
RX-
IEC 61850-9-2 LE
6
100 BASE-TX
5
TXRX+
TX+
4
L11
SK6
3
1
2
RJ45
L10
L9
L8
L7
L6
L5
L4
L3
L2
L1
MiCOM P746 (PART)
10P74615
Next
Sht:
Sht:
1
-
C
St Leonards Building
Harry Kerr Drive, Stafford.
ST16 1WT, UK
UK Grid Solutions Ltd
EXT. CONNECTION DIAG: P746 BUSBAR PROTECTION (80TE)
WITH 16 I/P & 28 O/P (4 O/P ARE HIGH BREAK) NCIT
1. COPPER PORT IS FOR SERVICE ONLY, NOT
RECOMMENDED FOR PERMANENT CONNECTION
RELAY 16
RELAY 15
RELAY 14
RELAY 13
RELAY 12
RELAY 11
RELAY 10
RELAY 9
RELAY 8
RELAY 7
RELAY 6
RELAY 5
RELAY 4
RELAY 3
RELAY 2
RELAY 19
RELAY 18
WATCHDOG
CONTACT
RELAY 1
RELAY 17
WATCHDOG
CONTACT
GE PROPRIETARY AND CONFIDENTIAL INFORMATION
This document is the property of General Electric Company ("GE") and contains proprietary information of GE. This document is loaned on the express
condition that neither it nor the information contained therein shall be disclosed to others without the express written consent of GE, and that the information
shall be used by the recipient only as approved expressly by GE. This document shall be returned to GE upon its request. This document may be subject to
certain restrictions under U.S. export control laws and regulations.© General Electric Company, GE CONFIDENTIAL UNPUBLISHED WORK.
M18
M17
M16
M15
M14
F13
F14
M13
M12
M11
M10
F12
F11
F10
M9
M8
F8
F9
M7
M6
M5
M4
F7
F6
F5
M3
M2
F3
F4
M1
N18
N17
N15
N16
N14
N12
N13
N11
N10
N9
N8
N7
N6
N5
N4
N3
F2
F1
G18
G17
G16
G15
G14
G13
G12
G11
G10
G9
G8
G7
G6
N1
N2
P14
P13
P12
P11
G4
G3
G2
G1
CID006234 Outlines updated to GE Format
Revision:
Date:
Issue:
COMMON
CONNECTION
OPTO 16
OPTO 15
OPTO 14
OPTO 13
OPTO 12
OPTO 11
OPTO 10
OPTO 9
COMMON
CONNECTION
OPTO 8
OPTO 7
OPTO 6
OPTO 5
OPTO 4
OPTO 3
OPTO 2
OPTO 1
MiCOM P746 (PART)
+
-
+
-
+
-
+
-
Name:
Chkd:
4/30/2020
07/05/2012
Date:
E
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
SK6
E18
G18
TX
L18
M12
M11
M10
M9
M8
M7
M6
M5
M4
M3
M2
M1
N18
N17
F18
F17
F16
F15
F14
N.ROBINSON
S.J.BURTON
Drg
No:
Title:
P2
P1
P16
SCN
P18
P17
* POWER SUPPLY VERSION 24-48V (NOMINAL) D.C. ONLY
M18
M17
M16
*
SEE DRAWING
10Px4001
+
-
+
-
AC OR DC
x AUX SUPPLY
EIA485/
KBUS
PORT
COMMS OPTIONS
RELAY 24
RELAY 23
RELAY 22
RELAY 21
RELAY 20
RELAY 19
RELAY 18
RELAY 17
10P74616
Next
Sht:
Sht:
1
-
C
St Leonards Building
Harry Kerr Drive, Stafford.
ST16 1WT, UK
UK Grid Solutions Ltd
EXT. CONNECTION DIAG: P746 BUSBAR PROTECTION (80TE)
WITH 24 I/P & 24 O/P NCIT
1. COPPER PORT IS FOR SERVICE ONLY, NOT
RECOMMENDED FOR PERMANENT CONNECTION
IEC 61850-9-2 LE
GE PROPRIETARY AND CONFIDENTIAL INFORMATION
This document is the property of General Electric Company ("GE") and contains proprietary information of GE. This document is loaned on the express
condition that neither it nor the information contained therein shall be disclosed to others without the express written consent of GE, and that the information
shall be used by the recipient only as approved expressly by GE. This document shall be returned to GE upon its request. This document may be subject to
certain restrictions under U.S. export control laws and regulations.© General Electric Company, GE CONFIDENTIAL UNPUBLISHED WORK.
RX
RELAY 16
M15
M14
RELAY 15
L17
N14
SEE DRAWING
10Px4001
L16
N12
N13
N15
N16
L15
L10
N6
L14
L9
N5
N11
L8
N4
N10
L7
N3
L13
L6
N2
L12
L5
N1
N9
L4
P14
N8
L3
L11
L2
P13
N7
L1
P12
MiCOM P746 (PART)
P11
F13
RELAY 14
RELAY 13
RELAY 12
RELAY 11
RELAY 10
RELAY 9
RELAY 8
RELAY 7
RELAY 6
RELAY 5
RELAY 4
RELAY 3
RELAY 2
RELAY 1
WATCHDOG
CONTACT
WATCHDOG
CONTACT
M13
8
7
100 BASE-FX
IEC 61850-9-2 LE
5
6
100 BASE-TX
RX-
TXRX+
TX+
4
3
1
2
COMMON
CONNECTION
OPTO 24
OPTO 23
OPTO 22
OPTO 21
OPTO 20
OPTO 19
OPTO 18
OPTO 17
F12
F11
F10
F9
F8
F7
F6
F5
F4
F3
F2
RJ45
E17
G17
F1
E16
E15
G16
E14
G15
E13
G13
G14
E12
E11
G11
G12
E10
E9
G9
G10
E8
E7
G7
G8
E6
E5
G5
G6
E4
G4
E3
G3
CID006234 Outlines updated to GE Format
Revision:
Date:
Issue:
COMMON
CONNECTION
OPTO 16
OPTO 15
OPTO 14
OPTO 13
OPTO 12
OPTO 11
OPTO 10
OPTO 9
COMMON
CONNECTION
OPTO 8
OPTO 7
OPTO 6
OPTO 5
OPTO 4
OPTO 3
OPTO 2
-
E2
+
E1
+
G2
+
G1
+
-
+
+
+
OPTO 1
+
MiCOM P746 (PART)
+
Name:
Chkd:
4/30/2020
07/05/2012
Date:
E
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
N.ROBINSON
S.J.BURTON
SK6
E18
G18
F18
F17
F16
F15
F14
RELAY 16
Drg
No:
Title:
P2
P1
P16
SCN
P18
P17
* POWER SUPPLY VERSION 24-48V (NOMINAL) D.C. ONLY
M18
M17
M16
M15
*
SEE DRAWING
10Px4001
SEE DRAWING
10Px4001
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
HIGH BREAK
CONTACTS
HIGH BREAK
CONTACTS
AC OR DC
x AUX SUPPLY
EIA485/
KBUS
PORT
COMMS OPTIONS
RELAY 24
RELAY 23
RELAY 22
RELAY 21
RELAY 20
RELAY 19
RELAY 18
RELAY 17
10P74617
Next
Sht:
Sht:
1
-
C
St Leonards Building
Harry Kerr Drive, Stafford.
ST16 1WT, UK
UK Grid Solutions Ltd
EXT. CONNECTION DIAG: P746 BUSBAR PROTECTION (80TE)
WITH 24 I/P & 24 O/P (8 O/P ARE HIGH BREAK) NCIT
1. COPPER PORT IS FOR SERVICE ONLY, NOT
RECOMMENDED FOR PERMANENT CONNECTION
GE PROPRIETARY AND CONFIDENTIAL INFORMATION
This document is the property of General Electric Company ("GE") and contains proprietary information of GE. This document is loaned on the express
condition that neither it nor the information contained therein shall be disclosed to others without the express written consent of GE, and that the information
shall be used by the recipient only as approved expressly by GE. This document shall be returned to GE upon its request. This document may be subject to
certain restrictions under U.S. export control laws and regulations.© General Electric Company, GE CONFIDENTIAL UNPUBLISHED WORK.
RX
IEC 61850-9-2 LE
RELAY 15
M12
M11
M10
M9
M8
M7
M6
M5
M4
M3
M2
M1
M14
RELAY 14
RELAY 13
RELAY 12
RELAY 11
K15
N17
K16
K12
N15
N16
N18
K11
N14
K7
K4
K3
L16
L15
L12
L11
L8
L7
L4
L3
K8
MiCOM P746 (PART)
N12
N13
N11
N10
N9
N8
N7
N6
N5
N4
N3
N2
N1
P14
P13
P12
F13
100 BASE-FX
IEC 61850-9-2 LE
100 BASE-TX
RELAY 10
RELAY 9
RELAY 8
RELAY 7
RELAY 6
RELAY 5
RELAY 4
RELAY 3
RELAY 2
RELAY 1
WATCHDOG
CONTACT
WATCHDOG
CONTACT
P11
M13
TX
RX-
TXRX+
TX+
COMMON
CONNECTION
OPTO 24
OPTO 23
OPTO 22
OPTO 21
OPTO 20
OPTO 19
OPTO 18
OPTO 17
F12
F11
8
7
F9
F10
6
F8
5
4
F6
F7
3
1
2
F5
F4
F3
F2
RJ45
E17
G17
F1
E16
E15
G15
G16
E14
E13
G13
G14
E12
E11
G11
G12
E10
E9
G9
G10
E8
E7
G8
E6
G7
E5
G5
G6
E4
G4
E3
G3
CID006234 Outlines updated to GE Format
Revision:
Date:
Issue:
COMMON
CONNECTION
OPTO 16
OPTO 15
OPTO 14
OPTO 13
OPTO 12
OPTO 11
OPTO 10
OPTO 9
COMMON
CONNECTION
OPTO 8
OPTO 7
OPTO 6
OPTO 5
OPTO 4
OPTO 3
OPTO 2
-
+
+
E2
+
G2
+
-
+
OPTO 1
+
E1
+
G1
+
MiCOM P746 (PART)
+
Name:
Chkd:
4/30/2020
07/05/2012
Date:
E
E18
G18
F18
F17
F16
F15
F14
F13
F12
F11
N.ROBINSON
S.J.BURTON
TX
RX
HIGH BREAK
CONTACTS
Drg
No:
Title:
*
SEE DRAWING
10Px4001
P2
P1
P16
SCN
P18
P17
K16
K15
K12
K11
K8
K7
K4
K3
L16
L15
L12
L11
L8
L7
L4
L3
* POWER SUPPLY VERSION 24-48V (NOMINAL) D.C. ONLY
M16
M15
M12
M11
M8
M7
M4
M3
N18
N17
N15
N16
N14
N12
N13
N11
N10
N9
N8
N7
N6
N5
N4
N3
N2
N1
P14
P13
P12
P11
MiCOM P746 (PART)
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
AC OR DC
HIGH BREAK
CONTACTS
HIGH BREAK
CONTACTS
x AUX SUPPLY
EIA485/
KBUS
PORT
RELAY 20
RELAY 19
RELAY 18
RELAY 17
RELAY 16
RELAY 15
RELAY 14
RELAY 13
10P74618
Next
Sht:
Sht:
1
-
C
St Leonards Building
Harry Kerr Drive, Stafford.
ST16 1WT, UK
UK Grid Solutions Ltd
EXTERNAL CONNECTION DIAG: P746 BUSBAR PROTECTION
WITH 24 I/P & 20 O/P (12 O/P ARE HIGH BREAK) NCIT
RELAY 12
RELAY 11
RELAY 10
RELAY 9
RELAY 8
RELAY 7
RELAY 6
RELAY 5
RELAY 4
RELAY 3
RELAY 2
RELAY 1
WATCHDOG
CONTACT
WATCHDOG
CONTACT
1. COPPER PORT IS FOR SERVICE ONLY, NOT
RECOMMENDED FOR PERMANENT CONNECTION
IEC 61850-9-2 LE
100 BASE-FX
GE PROPRIETARY AND CONFIDENTIAL INFORMATION
This document is the property of General Electric Company ("GE") and contains proprietary information of GE. This document is loaned on the express
condition that neither it nor the information contained therein shall be disclosed to others without the express written consent of GE, and that the information
shall be used by the recipient only as approved expressly by GE. This document shall be returned to GE upon its request. This document may be subject to
certain restrictions under U.S. export control laws and regulations.© General Electric Company, GE CONFIDENTIAL UNPUBLISHED WORK.
8
7
RX-
IEC 61850-9-2 LE
6
100 BASE-TX
5
SK6
4
F10
F9
TXRX+
TX+
3
1
2
RJ45
COMMS OPTIONS
COMMON
CONNECTION
OPTO 24
OPTO 23
OPTO 22
OPTO 21
OPTO 20
OPTO 19
OPTO 18
OPTO 17
F8
F7
F6
F5
F4
F3
F2
SEE DRAWING
10Px4001
E17
F1
E16
G17
E15
G15
G16
E14
E13
G13
G14
E12
E11
G11
G12
E10
E9
G9
G10
E8
E7
G7
G8
E6
E5
G5
G6
E4
G4
E3
G3
CID006234 Outlines updated to GE Format
Revision:
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
Date:
Issue:
COMMON
CONNECTION
OPTO 16
OPTO 15
OPTO 14
OPTO 13
OPTO 12
OPTO 11
OPTO 10
OPTO 9
COMMON
CONNECTION
OPTO 8
OPTO 7
OPTO 6
OPTO 5
OPTO 4
OPTO 3
OPTO 2
E2
+
E1
+
G2
+
G1
+
-
+
+
+
OPTO 1
+
MiCOM P746 (PART)
+
-
+
-
+
-
+
-
+
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
D17
D18
F17
F18
SEE DRAWING 10P74600 FOR RELAY CONNECTIONS TO SYSTEM
D16
D15
F16
D14
F15
D13
F13
F14
D12
D11
F12
D10
F11
D9
F9
F10
D8
D7
F8
D6
F7
D5
F5
F6
D4
F4
D3
D1
F1
F3
E18
G18
D2
E17
G17
F2
E16
E15
G15
G16
E14
E13
G14
E12
G13
E11
G11
G12
E10
E9
G9
G10
E8
E7
G7
G8
E6
G6
E5
Name:
Chkd:
07/05/2012
Date:
N.ROBINSON
S.J.BURTON
RELAY 16
RELAY 15
RELAY 14
RELAY 13
RELAY 12
RELAY 11
RELAY 10
RELAY 9
RELAY 8
RELAY 7
RELAY 6
RELAY 5
RELAY 4
RELAY 3
RELAY 2
RELAY 1
WATCHDOG
CONTACT
WATCHDOG
CONTACT
Drg
No:
Title:
1. COPPER PORT IS FOR SERVICE ONLY, NOT
RECOMMENDED FOR PERMANENT CONNECTION
COMMON
CONNECTION
OPTO 32
OPTO 31
OPTO 30
OPTO 29
OPTO 28
OPTO 27
OPTO 26
OPTO 25
COMMON
CONNECTION
OPTO 24
OPTO 23
OPTO 22
OPTO 21
OPTO 20
OPTO 19
OPTO 18
OPTO 17
GE PROPRIETARY AND CONFIDENTIAL INFORMATION
This document is the property of General Electric Company ("GE") and contains proprietary information of GE. This document is loaned on the express
condition that neither it nor the information contained therein shall be disclosed to others without the express written consent of GE, and that the information
shall be used by the recipient only as approved expressly by GE. This document shall be returned to GE upon its request. This document may be subject to
certain restrictions under U.S. export control laws and regulations.© General Electric Company, GE CONFIDENTIAL UNPUBLISHED WORK.
CID006234 Outlines updated to GE Format
4/30/2020
E
Revision:
Date:
Issue:
COMMON
CONNECTION
OPTO 16
OPTO 15
OPTO 14
OPTO 13
OPTO 12
OPTO 11
OPTO 10
OPTO 9
COMMON
CONNECTION
OPTO 8
OPTO 7
OPTO 6
OPTO 5
OPTO 4
OPTO 3
E4
G5
+
G4
+
-
+
+
+
E3
+
G3
+
-
+
OPTO 2
+
E2
+
E1
+
G2
+
G1
+
-
+
+
+
OPTO 1
+
MiCOM P746 (PART)
+
L5
L6
L7
L8
L9
L10
L11
L12
L13
L14
L15
L16
L17
L18
N1
N2
N3
N4
N5
N6
N7
N8
N9
N10
N11
N12
N13
N14
SK6
L4
P14
*
SEE DRAWING
10Px4001
P2
P1
P16
SCN
P18
P17
SEE DRAWING
10Px4001
+
-
+
-
IEC 61850-9-2 LE
AC OR DC
x AUX SUPPLY
EIA485/
KBUS
PORT
IEC 61850-9-2 LE
100 BASE-TX
100 BASE-FX
COMMS OPTIONS
RX
TX
RX-
TXRX+
TX+
RELAY 24
RELAY 23
RELAY 22
RELAY 21
RELAY 20
RELAY 19
RELAY 18
RELAY 17
10P74619
Next
Sht:
Sht:
1
-
C
St Leonards Building
Harry Kerr Drive, Stafford.
ST16 1WT, UK
UK Grid Solutions Ltd
EXT. CONNECTION DIAG: P746 BUSBAR PROTECTION (80TE)
WITH 32 I/P & 24 O/P NCIT
* POWER SUPPLY VERSION 24-48V (NOMINAL) D.C. ONLY
M18
M17
M15
M16
M14
M13
M12
M10
M11
M9
8
7
M7
M8
6
5
4
3
1
2
M5
M6
M4
M3
M1
M2
N18
N17
RJ45
L3
P13
N15
N16
L1
L2
P11
P12
MiCOM P746 (PART)
Name:
Chkd:
4/30/2020
07/05/2012
Date:
E
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
D16
D17
D18
F17
F18
D15
F16
D14
F15
D13
F13
F14
D12
D11
F11
F12
D10
D9
F9
F10
D8
D7
F7
F8
D6
D5
F5
F6
D4
F4
D3
D1
F1
F3
E18
G18
D2
E17
G17
F2
E16
E15
G15
G16
E14
E13
G13
G14
E12
E11
G11
G12
E10
E9
G9
G10
E8
E7
G7
G8
E6
G6
E5
G5
N.ROBINSON
S.J.BURTON
COMMS OPTIONS
RELAY 16
RELAY 15
RELAY 14
RELAY 13
RELAY 12
RELAY 11
RELAY 10
RELAY 9
RELAY 8
RELAY 7
RELAY 6
RELAY 5
RELAY 4
RELAY 3
RELAY 2
RELAY 1
WATCHDOG
CONTACT
Drg
No:
Title:
1. COPPER PORT IS FOR SERVICE ONLY, NOT
RECOMMENDED FOR PERMANENT CONNECTION
COMMON
CONNECTION
OPTO 32
OPTO 31
OPTO 30
OPTO 29
OPTO 28
OPTO 27
OPTO 26
OPTO 25
COMMON
CONNECTION
OPTO 24
OPTO 23
OPTO 22
OPTO 21
OPTO 20
OPTO 19
OPTO 18
OPTO 17
WATCHDOG
CONTACT
GE PROPRIETARY AND CONFIDENTIAL INFORMATION
This document is the property of General Electric Company ("GE") and contains proprietary information of GE. This document is loaned on the express
condition that neither it nor the information contained therein shall be disclosed to others without the express written consent of GE, and that the information
shall be used by the recipient only as approved expressly by GE. This document shall be returned to GE upon its request. This document may be subject to
certain restrictions under U.S. export control laws and regulations.© General Electric Company, GE CONFIDENTIAL UNPUBLISHED WORK.
CID006234 Outlines updated to GE Format
Revision:
Date:
Issue:
COMMON
CONNECTION
OPTO 16
OPTO 15
OPTO 14
OPTO 13
OPTO 12
OPTO 11
OPTO 10
OPTO 9
COMMON
CONNECTION
OPTO 8
OPTO 7
OPTO 6
OPTO 5
OPTO 4
OPTO 3
+
E4
+
G4
+
-
+
+
+
OPTO 2
+
E3
+
G3
+
+
+
E2
+
E1
+
G2
+
G1
+
-
+
OPTO 1
+
MiCOM P746 (PART)
+
SK6
*
SEE DRAWING
10Px4001
P2
P1
P16
SCN
P18
P17
8
7
6
5
4
3
+
-
+
-
RX
TX
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
AC OR DC
IEC 61850-9-2 LE
100 BASE-FX
IEC 61850-9-2 LE
100 BASE-TX
HIGH BREAK
CONTACTS
HIGH BREAK
CONTACTS
x AUX SUPPLY
EIA485/
KBUS
PORT
RX-
TXRX+
TX+
RELAY 24
RELAY 23
RELAY 22
RELAY 21
RELAY 20
RELAY 19
RELAY 18
RELAY 17
10P74620
Next
Sht:
Sht:
1
-
C
St Leonards Building
Harry Kerr Drive, Stafford.
ST16 1WT, UK
UK Grid Solutions Ltd
EXTERNAL CONNECTION DIAG: P746 BUSBAR PROTECTION (80TE)
WITH 32 I/P & 24 O/P (8 O/P ARE HIGH BREAK) NCIT
* POWER SUPPLY VERSION 24-48V (NOMINAL) D.C. ONLY
SEE DRAWING
10Px4001
M18
M17
M16
M15
M14
M13
M12
M11
M10
M9
M8
M7
1
2
RJ45
M5
M6
K16
K15
K12
M4
M3
M2
M1
N18
K11
K8
N15
N16
N17
K7
N14
K3
L16
L15
L12
L11
L8
L7
L4
L3
K4
MiCOM P746 (PART)
N12
N13
N11
N10
N9
N8
N7
N6
N5
N4
N3
N2
N1
P14
P13
P12
P11
Name:
Chkd:
4/30/2020
07/05/2012
Date:
E
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
POWER SUPPLY VERSION 24-48V (NOMINAL) D.C. ONLY
N.ROBINSON
S.J.BURTON
H18
H17
H16
H15
E7
E8
H14
H13
E5
E6
H12
E4
H11
H9
E1
H10
H8
F18
E3
H7
E2
H6
F17
H5
F16
H4
F15
H3
F14
H2
F13
H1
F12
D18
F11
D17
F9
F10
D16
D15
F7
F8
D14
D13
F5
F6
D12
F4
D11
D9
F1
F3
D8
G18
D10
D7
F2
D6
G17
D5
G16
D4
G15
D3
G14
D2
G13
D1
G12
E18
G11
E17
G9
G10
E16
G8
E15
G7
Drg
No:
Title:
L18
N14
M17
M18
M14
M15
M16
M12
M13
M9
M10
M11
M6
M7
M8
M3
M4
M5
M1
M2
N18
*
SK6
SEE DRAWING
10Px4001
8
7
6
5
4
3
1
2
RJ45
P2
P1
P16
SCN
P18
P17
SEE DRAWING
10Px4001
L15
L16
L17
N11
N12
N13
N15
N16
N17
L12
L13
L14
N8
N9
N10
-
RX
RX-
IEC 61850-9-2 LE
100 BASE-TX
IEC 61850-9-2 LE
100 BASE-FX
TXRX+
TX+
AC OR DC
x AUX SUPPLY
EIA485/
KBUS
PORT
COMMS OPTIONS
RELAY 24
RELAY 23
RELAY 22
RELAY 21
TX
+
-
+
RELAY 20
L9
L10
L11
N5
N6
N7
RELAY 19
L7
L8
N3
N4
RELAY 18
L4
L5
L6
P14
N1
N2
RELAY 17
L1
L2
L3
P11
P12
P13
MiCOM P746 (PART)
10P74621
Next
Sht:
Sht:
1
-
C
St Leonards Building
Harry Kerr Drive, Stafford.
ST16 1WT, UK
UK Grid Solutions Ltd
EXT. CONNECTION DIAG: P746 BUSBAR PROTECTION (80TE)
WITH 40 I/P & 24 O/P NCIT
RELAY 16
1. COPPER PORT IS FOR SERVICE ONLY, NOT
RECOMMENDED FOR PERMANENT CONNECTION
COMMON
CONNECTION
OPTO 40
OPTO 39
OPTO 38
OPTO 37
OPTO 36
OPTO 35
RELAY 15
RELAY 14
OPTO 33
OPTO 34
RELAY 13
RELAY 12
RELAY 11
RELAY 10
RELAY 9
RELAY 8
RELAY 7
RELAY 6
RELAY 5
RELAY 4
RELAY 3
RELAY 2
RELAY 1
WATCHDOG
CONTACT
WATCHDOG
CONTACT
COMMON
CONNECTION
OPTO 32
OPTO 31
OPTO 30
OPTO 29
OPTO 28
OPTO 27
OPTO 26
OPTO 25
COMMON
CONNECTION
OPTO 24
OPTO 23
OPTO 22
OPTO 21
GE PROPRIETARY AND CONFIDENTIAL INFORMATION
This document is the property of General Electric Company ("GE") and contains proprietary information of GE. This document is loaned on the express
condition that neither it nor the information contained therein shall be disclosed to others without the express written consent of GE, and that the information
shall be used by the recipient only as approved expressly by GE. This document shall be returned to GE upon its request. This document may be subject to
certain restrictions under U.S. export control laws and regulations.© General Electric Company, GE CONFIDENTIAL UNPUBLISHED WORK.
CID006234 Outlines updated to GE Format
Revision:
Date:
Issue:
OPTO 20
OPTO 19
OPTO 18
OPTO 17
COMMON
CONNECTION
OPTO 16
OPTO 15
OPTO 14
OPTO 13
OPTO 12
OPTO 11
OPTO 10
OPTO 9
COMMON
CONNECTION
OPTO 8
OPTO 7
OPTO 6
OPTO 5
OPTO 4
-
+
E14
E13
+
G6
+
G5
+
-
+
OPTO 3
+
E12
+
G4
+
+
+
OPTO 2
+
E11
+
E10
+
G3
+
G2
+
-
+
+
+
OPTO 1
+
E9
+
MiCOM P746 (PART)
+
G1
+
+
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
Name:
Chkd:
07/05/2012
Date:
N.ROBINSON
S.J.BURTON
SK6
7
8
5
6
3
4
1
2
RJ45
SEE DRAWING 10P74600 FOR RELAY CONNECTIONS TO SYSTEM
E8
E7
E6
E5
E4
E3
E2
E1
F18
F17
F16
F15
F14
F13
F12
F11
D18
D17
F10
D16
F9
D15
F8
D14
F7
D13
F5
F6
D12
F4
D11
D9
F1
F3
D8
G18
D10
D7
G17
F2
D6
D5
G15
G16
D4
D3
G13
G14
D2
D1
G11
G12
E18
E17
G9
G10
E16
E15
G8
E14
G7
E13
G6
E12
G4
G5
RX
TX
IEC 61850-9-2 LE
100 BASE-FX
IEC 61850-9-2 LE
100 BASE-TX
Drg
No:
Title:
RELAY 24
RELAY 23
RELAY 22
RELAY 21
RELAY 20
RELAY 19
RELAY 18
RELAY 17
RELAY 16
RELAY 15
RELAY 14
RELAY 13
RELAY 12
RELAY 11
RELAY 10
RELAY 9
RELAY 8
RELAY 7
RELAY 6
RELAY 5
RELAY 4
RELAY 3
RELAY 2
RELAY 1
WATCHDOG
CONTACT
WATCHDOG
CONTACT
K2
K3
K4
K5
K6
K7
K8
K9
K10
K11
K12
K13
N3
N4
N5
N6
N7
N8
N9
N10
N11
N12
N13
*
SEE DRAWING
10Px4001
P2
P1
P16
SCN
P18
P17
SEE DRAWING
10Px4001
K18
* POWER SUPPLY VERSION 24-48V (NOMINAL) D.C. ONLY
L18
L17
L15
L16
L14
L13
L12
L11
L10
L9
L7
L8
L6
L5
L4
L3
L2
L1
M17
M18
M16
M15
M14
M13
M12
M11
M9
M10
M8
M7
M6
M5
M4
M3
M1
M2
N18
K17
K16
N15
N16
N17
K15
N14
K14
K1
N2
N1
MiCOM P746 (PART)
P14
P13
P11
P12
+
-
+
-
AC OR DC
x AUX SUPPLY
EIA485/
KBUS
PORT
COMMS OPTIONS
RELAY 32
RELAY 31
RELAY 30
RELAY 29
RELAY 28
RELAY 27
RELAY 26
RELAY 25
10P74622
Next
Sht:
Sht:
1
-
C
St Leonards Building
Harry Kerr Drive, Stafford.
ST16 1WT, UK
UK Grid Solutions Ltd
EXT. CONNECTION DIAG: P746 BUSBAR PROTECTION (80TE)
WITH 32 I/P & 32 O/P NCIT
1. COPPER PORT IS FOR SERVICE ONLY, NOT
RECOMMENDED FOR PERMANENT CONNECTION
RX-
TX+
TXRX+
COMMON
CONNECTION
OPTO 32
OPTO 31
OPTO 30
OPTO 29
OPTO 28
OPTO 27
OPTO 26
OPTO 25
COMMON
CONNECTION
OPTO 24
OPTO 23
OPTO 22
OPTO 21
GE PROPRIETARY AND CONFIDENTIAL INFORMATION
This document is the property of General Electric Company ("GE") and contains proprietary information of GE. This document is loaned on the express
condition that neither it nor the information contained therein shall be disclosed to others without the express written consent of GE, and that the information
shall be used by the recipient only as approved expressly by GE. This document shall be returned to GE upon its request. This document may be subject to
certain restrictions under U.S. export control laws and regulations.© General Electric Company, GE CONFIDENTIAL UNPUBLISHED WORK.
CID006234 Outlines updated to GE Format
4/30/2020
E
Revision:
Date:
Issue:
OPTO 20
OPTO 19
OPTO 18
OPTO 17
COMMON
CONNECTION
OPTO 16
OPTO 15
OPTO 14
OPTO 13
OPTO 12
OPTO 11
OPTO 10
OPTO 9
COMMON
CONNECTION
OPTO 8
OPTO 7
OPTO 6
OPTO 5
OPTO 4
OPTO 3
OPTO 2
+
-
+
E11
+
G3
+
E10
+
E9
+
G2
+
G1
+
-
+
+
+
OPTO 1
+
MiCOM P746 (PART)
+
APPENDIX C
VERSION HISTORY
Appendix C - Version History
P746
P746/EN M/J43
1
HARDWARE AND SOFTWARE VERSION HISTORY
S/W
S/W
Version
Version
Major
Minor
01
H/W
Original
Version
Date of Issue
K
Feb 2008
S1
Compatibility
Technical
Documentation
 Original Issue
 First release to production
v2.14
P746/EN xx/A11
Description of Changes
01
C
K
Nov 2008
 Improvement of the CBF undercurrent detection reset Correction to make output relay test
pattern settable through Courier
v2.14
P746/EN xx/B11
01
D
K
Feb 2009
 Addition of high break boards
v2.14
P746/EN xx/C11
01
E
K
May 2009
 Improvement of internal fault tripping
v2.14
P746/EN xx/E11
01
F
K
Mar 2011
 Rebranding from AREVA to Alstom
v3.1
02
A
K
May 2010
 Ratio of virtual CT as reference for secondary currents calculation fixed,
 New phase comparison setting
v2.14
P746/EN xx/F21
02
B
K
May 2011
 New option with 32I/32O board option
 Rebranded from AREVA to Alstom
v3.1
P746/EN xx/G31
02
C
K
Oct 2011
 Upgrade IEC 61850 from ph1 to ph2
v3.1
02
D
K
Feb 2012
 Improvement of measurements courier cell display when restore all command
 Improvement of IEC 61850 data model alarm mapping
v3.1
03
A
K
Jan 2010
 Secure communications (cyber security)
 Redundant Ethernet option
v3.1
P746/EN xx/G31
03
B
K
Mar 2011
 Rebranded from AREVA to Alstom
v3.1
P746/EN xx/G31
03
C
K
Feb 2012
 Improvement of measurements courier cell display when restore all command
 Improvement of IEC 61850 data model alarm mapping
v3.1
03
D
K
May 2012
 Support for new Parallel Redundant Protocol PRP Ethernet cards
v3.1
03
E
K
April 2013
 Platform upgrade
03
F
K
June 2014
 Platform upgrade
03
G
K
October 2015
03
H
K
11
A
12
12
 Improvements to the IEC6150 application performance
v1.2.0 or later
June 2016
 Corrections to Russian Language settings names
v1.2.0 or later
M
June 2012
 Support for sampled values 9-2LE
 GOOSE performance improvements
v1.2.0 or later
B
M
Jan 2013
 Ethernet failover and SNTP Alarm added
C
M
July 2013
 Platform upgrade
 Software release compatible with both NCIT and conventional devices
S/W
S/W
Version
Version
Major
Minor
12
H/W
Original
Version
Date of Issue
D
M
Aug 2014
 Improvement in IEC61850 applications when data frequently changes
 Improvement in 9-2LE protection functions response Not released to production
12
E
M
Mar 2015
 Added DNPoE
12
F
M
Jun 2016
 Corrections to Russian Language settings names
12
G
M
Jun 2017
 GE rebranding release
v1.3.1 or later
12
H
M
Feb 2020
 Improvement to CBF reset time
v1.3.1 or later
12
J
M
March 2020
 Dead zone and Check zone alarm reporting improvement
 Improvements to IEC61850 reporting
v2.0.1 or later
March 2021
 Cybersecurity release including:
 IEC 61850 Edition 2 - with support for Ed 2 test modes for online testing.
 IEEE 1588 Precision Time Protocol - efficient time synchronizing direct from the substation
LAN.
 Editable Logical Nodes/Devices - to customize the IEC 61850 modelling and maximize
interoperability.
 Role based access control (RBAC) for centralized authentication.
 Authorization and account management via RADIUS, and directly on the relay.
 Security Event Management via Syslog.
 SNMP version 2c and cybersecure v3 - network management tools can monitor protection
IEDs
 New Ethernet Board - Improved traffic density handling, PRP, HSR and RSTP supported in the
same order option for standardization
 Multi-Client Reporting
 Compatible with both NCIT (IEC 61850 9-2 LE) and CIT
v2.0.1 or later
91
A
M
Description of Changes
S1
Compatibility
Technical
Documentation
v1.2 or later
P746/EN M/I43
2
SOFTWARE VERSION COMPATIBILITY
IED S/W
Setting File Version
Menu Text File Version
PSL File Version
00
00
00
00
01
01
01
01
02
02
02
02
03
03
03
03
12
12
12
12
91
91
91
91
Version