Documente Academic
Documente Profesional
Documente Cultură
Bay Computer
C264/EN O/C80
Operation Guide
Operation Guide
MiCOM C264/C264C
C264/EN O/C80
Page 1/2
MiCOM C264/C264C
BAY COMPUTER
CONTENTS
C264/EN SA/C80
C264/EN IT/C80
Technical Data
C264/EN TD/C80
Functional Description
C264/EN FT/C80
Hardware
C264/EN HW/C80
Connection
C264/EN CO/C80
C264/EN HI/C80
Application
C264/EN AP/C80
Lexical
C264/EN LX/C80
C264/EN O/C80
Operation Guide
Page 2/2
MiCOM C264/C264C
BLANK PAGE
C264/EN SA/C80
MiCOM C264/C264C
C264/EN SA/C80
MiCOM C264/C264C
Page 1/12
CONTENT
1.
INTRODUCTION
2.
2.1
2.2
3.
4.
5.
6.
7.
GUARANTEES
10
8.
11
8.1
Copyrights
11
8.2
Trademarks
11
9.
12
C264/EN SA/C80
Page 2/12
MiCOM C264/C264C
BLANK PAGE
1.
C264/EN SA/C80
Page 3/12
INTRODUCTION
This document is a chapter of the MiCOM C264/C264C documentation. It describes the
safety, handling, packing and unpacking procedures applicable to MiCOM C264/C264C
modular computer series and associated equipment's and software tools.
C264/EN SA/C80
Page 4/12
2.
MiCOM C264/C264C
2.1
2.2
Note: The term earth used throughout the product documentation is the direct equivalent of
the North American term ground.
Equipment operating conditions
The equipment should be operated within the specified electrical and environmental limits.
Current transformer circuits
Do not open the secondary circuit of a live CT since the high level voltage produced may be
lethal to personnel and could damage insulation.
C264/EN SA/C80
Page 5/12
C264/EN SA/C80
Page 6/12
3.
C264/EN SA/C80
MiCOM C264/C264C
4.
Page 7/12
2.
3.
Protective class:
IEC 60255-27:
2005
Class I
Installation
Category:
IEC 60255-27:
2005
EN 60255-27:
2006
Environment:
IEC 60255-27:
2005
Pollution degree 2
EN 60255-27:
Product Safety:
73/23/EEC
2006
Compliance is
demonstrated by
reference to safety
standards.
C264/EN SA/C80
Page 8/12
5.
Before removing a module, ensure that you are a same electrostatic potential as the
equipment by touching the case.
2.
Handle the module by its front-plate, frame, or edges of the printed circuit board. Avoid
touching the electronic components, printed circuit track or connectors.
3.
Do not pass the module to any person without first ensuring that you are both at the
same electrostatic potential. Shaking hands achieves equipotential.
4.
5.
More information on safe working procedures for all electronic equipment can be found in
IEC 60147-0F and BS5783.
If you are making measurements on the internal electronic circuitry of any equipment in
service, it is preferable that you are earthen to the case with a conductive wrist strap.
Wrist straps should have a resistance to ground between 500k 10M Ohms. If a wrist strap
is not available you should maintain regular contact with the case to prevent the build up of
static. Instrumentation which may be used for making measurements should be earthen to
the case whenever possible.
Schneider Electric strongly recommends that detailed investigations on the electronic
circuitry, or modification work, should be carried out in a Special Handling Area such as
described in IEC 60147-0F or BS5783.
6.
C264/EN SA/C80
Page 9/12
C264/EN SA/C80
Page 10/12
7.
GUARANTEES
The media on which you received Schneider Electric software are guaranteed not to fail
executing programming instructions, due to defects in materials and workmanship, for a
period of 90 days from date of shipment, as evidenced by receipts or other documentation.
Schneider Electric will, at its option, repair or replace software media that do not execute
programming instructions if Schneider Electric receive notice of such defects during the
guaranty period. Schneider Electric does not guaranty that the operation of the software shall
be uninterrupted or error free.
A Return Material Authorisation (RMA) number must be obtained from the factory and clearly
marked on the package before any equipment acceptance for guaranty work.
Schneider Electric will pay the shipping costs of returning to the owner parts, which are
covered by warranty.
Schneider Electric believe that the information in this document is accurate. The document
has been carefully reviewed for technical accuracy. In the event that technical or
typographical errors exist, Schneider Electric reserves the right to make changes to
subsequent editions of this document without prior notice to holders of this edition. The
reader should consult Schneider Electric if errors are suspected. In no event shall
Schneider Electric be liable for any damages arising out of or related to this document or the
information contained in it.
Expect as specified herein, Schneider Electric makes no guaranties, express or implied and
specifically disclaims and guaranties of merchantability or fitness for a particular purpose.
Customer's rights to recover damages caused by fault or negligence on the part
Schneider Electric shall be limited to the amount therefore paid by the customer.
Schneider Electric will not be liable for damages resulting from loss of data, profits, use of
products or incidental or consequential damages even if advised of the possibility thereof.
This limitation of the liability of Schneider Electric will apply regardless of the form of action,
whether in contract or tort, including negligence. Any action against Schneider Electric must
be brought within one year after the cause of action accrues. Schneider Electric shall not be
liable for any delay in performance due to causes beyond its reasonable control. The
warranty provided herein does not cover damages, defects, malfunctions, or service failures
caused by owner's failure to follow the Schneider Electric installation, operation, or
maintenance instructions. Owner's modification of the product; owner's abuse, misuse, or
negligent acts; and power failure or surges, fire, flood, accident, actions of third parties, or
other events outside reasonable control.
8.
8.1
Copyrights
C264/EN SA/C80
Page 11/12
Under the copyright laws, this publication may not be reproduced or transmitted in any form,
electronic or mechanical, including photocopying, recording, storing in an information
retrieval system, or translating, in whole or in part, without the prior written consent of
Schneider Electric.
8.2
Trademarks
PACiS, PACiS SCE, PACiS ES, PACiS CMT, PACiS SMT, PACiS PS and PACiS SCE are
trademarks of Schneider Electric. Product and company names mentioned herein are
trademarks or trade names of their respective companies.
C264/EN SA/C80
Page 12/12
9.
Introduction
C264/EN IT/C80
MiCOM C264/C264C
INTRODUCTION
Introduction
MiCOM C264/C264C
C264/EN IT/C80
Page 1/8
CONTENT
1.
INTRODUCTION TO MiCOM
2.
2.1
Chapters description
2.1.1
2.1.2
2.1.3
2.1.4
2.1.5
2.1.6
2.1.7
2.1.8
2.1.9
2.1.10
2.1.11
2.1.12
2.1.13
2.1.14
2.1.15
2.1.16
Annex (AN)
2.2
Operation guide
2.3
Technical guide
3.
3.1
MiCOM Computers
3.2
C264/EN IT/C80
Introduction
Page 2/8
MiCOM C264/C264C
BLANK PAGE
Introduction
C264/EN IT/C80
MiCOM C264/C264C
1.
Page 3/8
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 Schneider Electric.
Central to the MiCOM concept is flexibility.
MiCOM provides the ability to define an application solution and, through extensive
communication capabilities, to integrate it with your power supply control system.
The components within MiCOM are:
A range industrial PC
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.
The MiCOM range will continue to be expanded. The general features of MiCOM will also be
enhanced, as we are able to adopt new technology solutions.
For up-to-date
information
www. schneider-electric.com
on
any
MiCOM
product,
visit
our
website:
C264/EN IT/C80
Page 4/8
2.
Introduction
MiCOM C264/C264C
2.1
Chapters description
2.1.1
2.1.2
2.1.3
2.1.4
2.1.5
2.1.6
2.1.7
2.1.8
2.1.9
Introduction
C264/EN IT/C80
MiCOM C264/C264C
2.1.10
Page 5/8
2.1.11
2.1.12
2.1.13
2.1.14
2.1.15
2.1.16
Annex (AN)
This chapter contains instructions on how to set the networks.
2.2
Operation guide
This guide contains the following chapters:
SA, IT, TD, FT, HI, AP, LX.
2.3
Technical guide
This guide contains the following chapters:
SA, IT, TD, FT, HW, CO, IN, ST, CT, CM, RS, MF, LX, AN.
C264/EN IT/C80
Page 6/8
3.
Introduction
MiCOM C264/C264C
3.1
MiCOM Computers
Driven by the requirements around the world for advanced applications in SCADA, Digital
Control Systems, Automation, control and monitoring, Schneider Electric has designed and
developed a complete range of computer products, MiCOM C264 specifically for the power
process environment and electric utility industry. It allows building a personalised solution for
Control, Monitoring, Measurement and Automation of electrical processes.
MiCOM C264/C264C computers range are designed to address the needs of a wide range
of installations, from small to large and customer applications. Emphasis has been placed on
strong compliance to standards, scalability, modularity and openness architecture. These
facilitate use in a range of applications from the most basic to the most demanding. They
also ensure interoperability with existing components and, by providing building computers,
PLC or IEDs approach, provide a comprehensive upgrade path, which allows PACiS
capabilities to track customer requirements.
Key features are that this computer family is based on a Ethernet client/server architecture,
its a modular computer that offers a large variety of applications such as Bay Computer,
Remote Terminal Unit, Sequence of Event Recorder, Data Concentrator and Programmable
Logic Controller.
Phase in time, dedicated computer available for each application will be purposed.
3.2
Introduction
C264/EN IT/C80
MiCOM C264/C264C
Page 7/8
C264C
SCADA Interface
DNP3 & IEC 60870-5-101
& IEC 60870-5-104
WEB access
Master clock
(GPS)
Operator
Interface
HV FEEDER BAY
Fast Ethernet
IEC 61850
C264
C264C
Main protection
C264
I/Os
COMMON BAY
MV FEEDER BAYS
Cubicle/ Switchboard
TRANSFORMER BAY
MV FEEDER BAYS
integration
C0001ENc
PSTN or
dedicated
line
SCADA Interface
DNP3 & IEC 60870-5-101
& IEC 60870-5-104
Px30
Remote
HMI
Px40
IE
I
M720
NP3,
DBUS,
0-5-103,
870-5-101
Px20
Px30
PLC
BC
I/Os
I/Os
C0002ENb
The system application on figure 1 uses several C264 linked together on SBUS
Ethernet. A gateway grants access to a SCADA.
Standalone application use one C264 linked to IEDs and possibly to a remote SCADA.
C264/EN IT/C80
Introduction
Page 8/8
MiCOM C264/C264C
BLANK PAGE
Technical Data
C264/EN TD/C80
MiCOM C264/C264C
TECHNICAL DATA
Technical Data
MiCOM C264/C264C
C264/EN TD/C80
Page 1/46
CONTENT
1.
2.
CONFORMITY
3.
GENERAL DATA
3.1
Design
3.2
Installation Position
3.3
Degree of Protection
3.4
Weight
3.5
3.6
3.6.1
3.6.2
10
3.6.3
11
3.6.4
12
3.6.5
13
3.7
14
3.7.1
14
3.7.2
16
3.8
Terminals
19
3.9
20
4.
RATINGS
21
4.1
Auxiliary Voltage
21
4.2
Power Supply
21
4.2.1
21
4.2.2
21
4.3
23
4.3.1
23
4.3.2
23
4.4
24
4.4.1
24
4.4.2
25
4.5
26
4.5.1
26
4.5.2
26
4.6
27
4.6.1
27
C264/EN TD/C80
Page 2/46
Technical Data
MiCOM C264/C264C
4.7
28
4.7.1
28
4.7.2
29
4.8
30
4.8.1
General
30
4.8.2
30
4.8.3
31
4.8.4
31
4.8.5
32
4.8.6
33
4.9
33
4.9.1
33
5.
BURDENS
35
5.1
Auxiliary Voltage
35
5.2
Power Supply
37
5.3
CPU Boards
37
5.4
37
5.4.1
37
5.4.2
37
5.5
38
5.5.1
38
5.5.2
38
5.6
39
5.6.1
39
5.7
39
5.7.1
39
5.7.2
39
5.8
39
5.8.1
General
39
5.8.2
39
5.9
39
5.9.1
39
5.10
39
5.11
39
6.
ACCURACY
40
6.1
Reference Conditions
40
6.2
Measurement Accuracy
40
6.2.1
40
6.2.2
41
6.3
41
Technical Data
MiCOM C264/C264C
C264/EN TD/C80
Page 3/46
7.
TYPE TESTS
42
7.1
42
7.1.1
42
7.1.2
42
7.1.3
42
7.2
Mechanical Test
43
7.3
Atmospheric Test
44
7.4
44
7.5
45
7.6
45
C264/EN TD/C80
Technical Data
Page 4/46
MiCOM C264/C264C
BLANK PAGE
Technical Data
MiCOM C264/C264C
1.
C264/EN TD/C80
Page 5/46
C264/EN TD/C80
Page 6/46
2.
Technical Data
MiCOM C264/C264C
CONFORMITY
(Per Article 10 of EC Directive 73/23/EEC).
The product designated MiCOM C264/C264C computer has been designed and
manufactured in conformance with the standard IEC 60255-27:2005 and is compliant with
the European Commission Low Voltage Directive 73/23/EEC.
Technical Data
C264/EN TD/C80
MiCOM C264/C264C
3.
GENERAL DATA
3.1
Design
Page 7/46
Surface-mounted case suitable for wall installation or flush-mounted case for 19 cabinets
and for control panels.
3.2
Installation Position
Vertical 15
3.3
Degree of Protection
In agreement with DIN VDE 0470 and EN 60255-27:2006, or with IEC 60255-27:2005:
3.4
IP20 for rear panels of C264/C264C, except reduced to IP10 when the black MiDOS
28-pin terminal block is installed for the TMU board.
Weight
Case 40 TE: approximately 4 kg
Case 80 TE: approximately 8 kg
3.5
3.6
A case
There are many types of MICOM C264 computers. Each MICOM C264 computer has a
specific purpose and includes some combination of boards to achieve that purpose:
C264 Multirack
C264/EN TD/C80
Technical Data
Page 8/46
3.6.1
MiCOM C264/C264C
Purpose
C264
80TE
C264C
40TE
C264
Multirack
MAIN Rack
C264
Multirack
Extension
Rack
BIU24x
CCU200
CCU211
DIU200
DIU211
DOU201
AIU201
AIU211
TMU210
SWU20x
SWR2xx
SWD2xx
GHU
2A1
GHU
2A0
GHU
2AB
GHU
2AB
GHU2AB: NOTE 1
Technical Data
MiCOM C264/C264C
NOTE 1:
For GHU2 A B:
B for the size
B=B includes all possibilities: B=0 or 1
B=0 Small
B=1 Large
A for the LCD
A=A includes all possibilities: A=0,1, or 2
A=0 Has LCD
A=1 Has no LCD
A=2 Has remote LCD
C264/EN TD/C80
Page 9/46
C264/EN TD/C80
Technical Data
Page 10/46
3.6.2
MiCOM C264/C264C
Board
Q
Slots
View when you look at the back of the computer
N
M
L
K
J
I
H
G
F
E
D
BIU24x
A
X
CCU200 NOTE 1
14
15
CCU211 NOTE 1
14
15
DIU200
14
15
DIU211
14
15
DOU201
14 NOTE 4
15 NOTE 4
AIU201
AIU211
TMU210 NOTE 1
TMU220 NOTE 1
AOU200
SWU20x
NOTE 2
NOTE 2
SWR2xx
NOTE 2
NOTE 2
SWD2xx
NOTE 2
NOTE 2
GHU2A1 NOTE 3
NOTE 1: If you install a TMU, do not install the CCU in slot P and do not install the CCU in the slot adjacent to the TMU.
NOTE 2: If the board is installed in Slot C; If the rack is full; and if you have no DSPIO installed; 1
If the board is installed in Slot D; If the rack is full; and if you have a DSPIO or others installed: 1
NOTE 3: For an explanation of the GHU2AB codes, please refer to C264 Computer Comparison of Board Installations Between Models
NOTE 4: If the application causes all of the DOs to go active at the same time: 6
Technical Data
C264/EN TD/C80
MiCOM C264/C264C
3.6.3
Page 11/46
Board
Slots
View when you look at the back
of the computer
H
G
F
E
D
C
B
A
BIU24x
With No TMU
CCU200 NOTE 1
CCU211 NOTE 1
DIU200
DIU211
DOU201
AIU201
AIU211
TMU210 NOTE 1
X=1
TMU220 NOTE 1
X=1
SWU20x
NOTE 2
NOTE 2
SWR2xx
NOTE 2
NOTE 2
SWD2xx
NOTE 2
NOTE 2
AOU200
GHU2A0: NOTE 3
NOTE 1: If you install a TMU, do not install the CCU in slot F and do not install the CCU in the slot adjacent to the TMU.
NOTE 2: If you do not install a DSP/DSPIO: 2 If you do install a DSP/DSPIO: 1
NOTE 3: For an explanation of the GHU2xx codes, please refer to C264 Computer Comparison of Board Installations Between Models
C264/EN TD/C80
Technical Data
Page 12/46
3.6.4
MiCOM C264/C264C
Board
Signals
AI
AO
DI
DO
CCU200 NOTE 1
13: 104 DI + 52 DO
15: 120 DI + 60 DO
CCU211 NOTE 1
13: 104 DI + 52 DO
15: 120 DI + 60 DO
DIU200
16
14: 224 DI
15: 240 DI
DIU211
16
14: 224 DI
15: 240 DI
14: 140 DO
15: 150 DO
BIU24x
CT
VT
DOU201
10
AIU201
6: 24 AI
6: 24 AI
AIU211
6: 48 AI
6: 48 AI
TMU210 NOTE 1
1: 4 CT, 4 VT
TMU220 NOTE 1
1: 4 CT, 5 VT
AOU200
6: 24 AO
6: 24 AO
SWU20x
SWR2xx
SWD2xx
GHU2A1 NOTE 2
NOTE 1: Do not install the CCU in the slot adjacent to the TMU.
NOTE 2: For an explanation of the GHU2xx codes, please refer to C264 Computer Comparison of Board Installations Between Models
Technical Data
C264/EN TD/C80
MiCOM C264/C264C
3.6.5
Page 13/46
Board
Signals
AI
AO
DI
DO
CCU200 NOTE 1
3: 24 DI + 12 DO
6: 48 DI + 24 DO
CCU211 NOTE 1
3: 24 DI + 12 DO
6: 48 DI + 24 DO
DIU200
16
4: 64 DI
6: 96 DI
DIU211
16
4: 64 DI
6: 96 DI
4: 40 DO
6: 60 DO
BIU24x
CT
VT
DOU201
10
AIU201
4: 16 AI
6: 24 AI
AIU211
4: 32 AI
6: 48 AI
TMU210 NOTE 1
1: 4 CT, 4 VT
TMU220 NOTE 1
1: 4 CT, 5 VT
AOU200
4: 16 AO
6: 24 AO
SWU20x
SWR2xx
SWD2xx
GHU2A0 NOTE 2
NOTE 1: Do not install the CCU in the slot adjacent to the TMU.
NOTE 2: For an explanation of the GHU2xx codes, please refer to C264 Computer Comparison of Board Installations Between Models
C264/EN TD/C80
Technical Data
Page 14/46
3.7
3.7.1
MiCOM C264/C264C
T101 protocol
MODBUS protocol
T104 protocol
DNP3 serial protocol
DNP3 over IP protocol
PSL:
Number of items
NOTE 1
Number of elements
NOTE 2
FBD: Number of accurate timers
Overall number of timers (configurated timers)
Printers at C264 level
Serial Communication port (for SCADA and/or legacy protocols)
SCADA protocols
Master legacy protocols (for IED communication)
IEDs allowed for each Legacy Bus
Voltage level
Bays
Circuit breakers
Disconnectors
Transformers
Maximum managed datapoints
Digital Input Points / Wired DI / System DI
Output Control Points / Wired DO
Tap Position Indication
Counters / Wired
Setpoint (digital / analyse)
ISaGRAF
TPI
CO
SP
CT
MPS
MV
SPS/DPS
Equation
Time discrimination and tagging of events
Technical Data
C264/EN TD/C80
MiCOM C264/C264C
Page 15/46
Element
Input bandwidth
Fast waveform (disturbance) file storage capacity
NOTE 1: Item: for the interlock / PSL, an item is the output of an Interlock / PSL, or an intermediate
variable used as an output (such as for the TON/TOFF/SR latch operators). In an interlock
equation, an interlock output is equal to one item.
NOTE 2: Element: After the decomposition of the equation into the sum of multiplications, an element
is the operand of an operator.
C264/EN TD/C80
Technical Data
Page 16/46
3.7.2
MiCOM C264/C264C
Global Limits for the C264 connected to the two extension racks and to the IEDs:
Element
BI Total
DI IED
SP
TPI
Command
CT Total:
wired+IED
CT wired
Limits
Including the system BI (approximately
500 )
CT IED
AI TOTAL
Wired DI & AI
AI IED
Extension racks
IED Total
128
State / bay
2300
Analogue bay
221
Command / bay
Sending of BI
430
10 digital inputs per rack change state
12 times in 10 s (16 * 10 * 12 = 1920
status changes in 10 s)
1 change of value of all measurements
Read cycle of wired AI = 1 second
in 1 second ( at same time than previous
status changes)
Sending of
measurement
Technical Data
C264/EN TD/C80
MiCOM C264/C264C
Page 17/46
DIU
DOU
CCU
AIU
CT/VT
AOU
serial lines
SCADA
15
15
15
6
1
4
4
Serial/Ethernet: 2
Ethernet IEC104, T104: 4
0
2300
IED Total
State / bay
Analogue bay
Command / bay
GOOSE Tx
GOOSE Rx
PSL
Isagraf
221
430
1 GOOSE xPS, 1 GOOSE MV
128 A.C.U.
For example:
256 items
NOTE 1
256 elements NOTE 2
128 TPI
256 CO
256 SP
512 CT
512 MPS
512 MV
512 SPS / DPS
Limits
Including the system BI
NOTE 1: Item: for the interlock / PSL, an item is the output of an Interlock / PSL, or an intermediate
variable used as an output (such as for the TON/TOFF/SR latch operators). In an interlock
equation, an interlock output is equal to one item.
NOTE 2: Element: After the decomposition of the equation into the sum of multiplications, an element
is the operand of an operator.
C264/EN TD/C80
Page 18/46
Technical Data
MiCOM C264/C264C
Limits
If you have 4 or more extension racks, make
sure that the MAIN rack has no I/O boards
Technical Data
C264/EN TD/C80
MiCOM C264/C264C
3.8
Page 19/46
Terminals
PC Maintenance Interface:
DIN 41652 connector, type female D-Sub, 9-pin, installed on the front panel
Two of the RJ-45 female connector, 8-pin for the 10/100Base-T self-negotiation
The IRIG-B interface (standard NF S 87-500, May 1987), installed on the CPU260/270
board:
BNC plug
M3 threaded terminal ends, self-centering with wire protection for conductor cross
sections from 0.2 to 2.5 mm for BIU241 board
DIN 41652 connector; type D-Sub, 9-pin, installed on the CPU260/270? board.
Optical fibres through ECU200 (external RS232/optical converter): optical plastic fibre
connection in agreement with IEC 874-2 or DIN 47258 or ST glass fibre optic
connection (ST is a registered trademark of AT&T Lightguide Cable Connectors).
M3 threaded terminal ends, self-centring with wire protection for conductor cross
sections from 0.2 to 2.5 mm for these boards:
AIU201, AIU211
AOU200
BIU241
CCU200, CCU211
DIU200, DIU211
DOU201
DSP210
The I/O boards and BIU241 include a 24-pin, 5.08 mm pitch male-connector.
M5 threaded terminal ends, self-centering with wire protection for conductor cross
sections between 2.5 and 4 mm for the TMU board.
C264/EN TD/C80
Page 20/46
3.9
Technical Data
MiCOM C264/C264C
Technical Data
C264/EN TD/C80
MiCOM C264/C264C
4.
RATINGS
4.1
Auxiliary Voltage
Page 21/46
Nominal ranges
Operative DC range
Operative AC range
A01
24VDC
A02
48 thru 60VDC
A03
88 thru 150VDC
A04
The nominal frequency (Fn) for the AC auxiliary voltage is dual rated at 50/60Hz, the operate
range is 45Hz to 65Hz.
The BIU241 board includes these attributes:
Power supply: 40 W
Supply monitoring
4.2
Power Supply
4.2.1
4.2.2
C264/EN TD/C80
Page 22/46
Technical Data
MiCOM C264/C264C
Limitation
The board contains the Port 2 only. The communication port 2 remains the same as
the BIU241.
The board has been design to support two voltage ranges, direct current only:
Case
A02
48VDC 60VDC
A03
110VDC 125VDC
Performances
Voltage insulation between Main & Secondary power supply source : 2500 V Rms.
Technical Data
C264/EN TD/C80
MiCOM C264/C264C
Page 23/46
4.3
4.3.1
Nominal voltage
(+/-20%)
A01
24VDC
YES
A02
48 thru 60VDC
YES
A03
YES
A04
220VDC
YES
A07
NO
Nominal voltage
(+/-20%)
A01
24VDC
A02
48 thru 60VDC
A03
A04 or
A07
220VDC or
if V > 50VDC Input status is set
110 thru 125VDC
if V< 29.9VDC Input status is reset
(with 80% Threshold)
A08
For more installation data about this board, please refer to the topic, MiCOM 264 Computer:
Configuration.
C264/EN TD/C80
Technical Data
Page 24/46
MiCOM C264/C264C
4.4
4.4.1
You wire the two output contacts of each relay in serial. In this event, you make the
best use of the Break function for each relay..
On the CCU200 board, the details of the 4 Output Relay Contacts show in the table that
follows:
Description
Values
Make
5A
Carry
5A continuously
30A for 500 ms or 250A for 30 ms
Operating time
Break < 7 ms
Normally open
For more installation data about this board, please refer to the topic, MiCOM 264 Computer:
Configuration.
Technical Data
C264/EN TD/C80
MiCOM C264/C264C
4.4.2
Page 25/46
A self-monitoring device for the output control chain: address check, state monitoring
You can configure the digital outputs only in the double remote signalling configuration
For more installation data about this board, please refer to the topic, MiCOM 264 Computer:
Configuration.
In the table that follows, the Break attribute shows in two cases:
You wire the two output contacts of each relay in serial. In this event, you make the
best use of the Break function for each relay.
For more details, please refer to the table that follows.
Description
Values
Make
5A
Carry
5A continuously
30A for 500 ms or 250A for 30 ms
Operating time
Break < 7 ms
Normally open
C264/EN TD/C80
Technical Data
Page 26/46
MiCOM C264/C264C
4.5
4.5.1
4.5.2
A01
24 VDC
A02
48 thru 60 VDC
A03
A04
220 VDC
For more installation data about this board, please refer to the topic, MiCOM 264 Computer:
Configuration.
DIU211 Digital Inputs
In the C264 rack, the DIU211 board replaces a DIU200 board. External connections are the
same as the ones on the previous boards.
The DIU211 board includes 16 opto-isolated digital-inputs, with one common for two inputs.
There are six versions of the DIU211 board, as follows:
Version
A01
24 VDC
A02
48 to 60 VDC
A03
A04 or
A07
A08
The inputs are suitable for use on systems with nominal battery voltages from 24Vd.c. to
220Vd.c (+/- 20%). The input responds to negative input voltages. The inputs are not selfcontrolled. The threshold voltage depends on the selection of the voltage range:
Version
24 VDC
48 to 60 VDC
220 VDC
For CPU2 and CPU3, use jumpers to select the nominal voltage.
For use with CPU 2 board, use a four-position header and jumper to select the address of
the board.
For use with CPU 3 board, the location of the DIU211 in the C264 rack defines the address
of the board. If you use the DIU211 as a spare of a previous board, you can use the jumper
to define the address of the board. Use the PACiS tool, System Configuration Editor (SCE)
to define this location.
Technical Data
C264/EN TD/C80
MiCOM C264/C264C
Page 27/46
For an input voltage from the threshold value to 18V, the input current is 30mA. The voltage
applied to the input terminals, with amplitude of between 19,2VDC and 264VDC powers the
pulse generation circuit. The circuit drives a pulse of current with amplitude of 30mA. The
pulse duration is between 1ms and 2ms.
To reduce thermal dissipation, especially at high input voltages, the inputs draw a current of
less than 1.6 mA.
For details about the input burdens, please refer to the topic DIU211 Input Burden in this
chapter.
For more installation data about this board, please refer to the topic, MiCOM 264 Computer:
Configuration.
4.6
4.6.1
In the C264 rack, a DOU201 board replaces a DOU200 board. External connections remain
the same as for earlier versions of the board.
For more details of the DOU201 board, please refer to the table that follows:
Description
Values
Make
5A
Carry
5A continuously
30A for 500 ms or 250A for 30 ms
Break
Operating time
Break < 7 ms
Normally open
For use with CPU 2 board, use a four-position header and jumper to select the address of
the board.
For use with CPU 3 board, the location of the DOU201 in the C264 rack defines the address
of the board. If you use the DOU201 as a spare of a previous board, you can use the jumper
to define the address of the board. Use the PACiS tool, System Configuration Editor (SCE)
to define this location.
Dielectric strength of the coil contacts: 5000 Vrms.
For more installation data about this board, please refer to the topic, MiCOM 264 Computer:
Configuration
C264/EN TD/C80
Technical Data
Page 28/46
MiCOM C264/C264C
4.7
4.7.1
Ranges
1mA
5 mA
10 mA
20 mA
+ 4mA thru +20mA
1,25V
2,5V
5V
10V
Sampling period
100 ms
Accuracy
AD conversion
> 100dB
> 40dB
1, 2, 4, 16
11 K
75
Technical Data
C264/EN TD/C80
MiCOM C264/C264C
4.7.2
Page 29/46
Ranges
1mA
5 mA
10 mA
20 mA
+ 4mA thru +20mA
Sampling period
100 ms
Accuracy
AD conversion
> 100dB
> 40dB
75
C264/EN TD/C80
Technical Data
Page 30/46
MiCOM C264/C264C
4.8
4.8.1
General
For C264 and C264C computers, you can install TMU210, and TMU220 boards.
For C264 Standalone computers, these are no TMU2XX boards installaed.
For the CPU260, on the TMU board, the DSP daughter board can store data for two days.
The TMU210 board provides 4 Current Transformer (CT) inputs and 4 Voltage Transformer
(VT) Inputs.
The TMU220 board provides 4 Current Transformer (CT) inputs and 5 Voltage Transformer
(VT) Inputs.
For more installation data about these boards, please refer to the topic, MiCOM 264
Computer: Configuration.
4.8.2
Description
Operating range
1A
5A
1Arms
5Arms
0.2 A r m s
0.2 A r m s
4 A r m s (4*In)
20 A r m s (4*In)
Frequency
50 or 60 Hz 10%
50 or 60 Hz 10%
Strength
1A
5A
6 A r m s (6*In)
30 A r m s (6*In)
20 A r m s (20*In)
100 A r m s (20*In)
Technical Data
C264/EN TD/C80
MiCOM C264/C264C
4.8.3
Page 31/46
Operating range
57.73 V r m s to 500 V r m s
7Vrms
577 V r m s
50 or 60 Hz 10%
VT load rating:
Duration
10 seconds with no destruction
4.8.4
Strength
880 V r m s
Description
1A
5A
1Arms
5Arms
0.1 A r m s
0.5 A r m s
40 A r m s (4*In)
200 A r m s (4*In)
Frequency
50 or 60 Hz 10%
50 or 60 Hz 10%
Values
Pass band
10th harmonic
2%
5VA 5P10
In addition, and specific for the 3 phase current inputs for each CT:
Description
3 phase current inputs
Power consumption
Operating range
1A
5A
1A
5A
< 0.05 VA
< 1,25 VA
Values
Operating range
0.1 thru 40 In
Thermal heating
C264/EN TD/C80
Technical Data
Page 32/46
MiCOM C264/C264C
In addition, and specific for the 1 earth current input for each CT:
Operating range
Description
1 earth current inputs
Power consumption
1A
5A
1A
5A
Operating range
Thermal heating
Duration
4.8.5
1A
5A
30 A r m s (30*In)
150 A r m s (30*In)
Values
Power consumption
Vn range
Thermal heating
Pass band
10th harmonic
2%
Technical Data
C264/EN TD/C80
MiCOM C264/C264C
4.8.6
Page 33/46
Values
Width
16 bits
Conversion period
< 30 s
Scanning period
64 samples/period
Linearity error
2 LSB
0db
-40db/decade
4.9
4.9.1
Maximal Impedance
4K
2K
1K
+ 4 mA thru +20 mA
After calibration, and at 25C, the precision = 0,1% X (the full scale + 20%).
Between -10C and +70C, the maximum deviation is <100ppm/C.
C264/EN TD/C80
Technical Data
Page 34/46
MiCOM C264/C264C
100ms after the command, the current output is stable. The management of the AOU200
board with an RI relay shows in Figure 1. When the RI relay is in the closed position, you can
read the value.
AOUx
100 ms
10 ms
10 ms
RI relay
C0287ENa
NO
250VDC / 230VAC
2,5A continuously
Break
Operating time
< 7ms
Maximum frequency of
commutation
Life Period
Technical Data
C264/EN TD/C80
MiCOM C264/C264C
5.
BURDENS
5.1
Auxiliary Voltage
Page 35/46
The MiCOM C264/C264C computer burdens depend on the number of cards installed in the
computer and show in the table that follows:
Version
Nominal
Maximum
C264C
15W
22W
C264
20W
40W
C264/EN TD/C80
Technical Data
Page 36/46
MiCOM C264/C264C
For more specific details about the MiCOM C264 / C264C computer burdens, please refer to the table that follows:
Computer
Version
Case Size
Voltage
Nominal
Maximum
C264
A01
24VDC
30VADC
31WAC
39VADC
39WAC
C264
A02
36WAC
NA
NA
C264
A03
C264
A04
39VADC
40WAC
NA
NA
110 thru
125VDC
220VDC and
230VAC
C264C
A01
24VDC
12VADC
13WAC
17VADC
17WAC
C264C
A02
17WAC
22 VADC
22 WAC
C264C
A03
C264C
A04
20WAC
27VADC
27 WAC
19VADC
Technical Data
C264/EN TD/C80
MiCOM C264/C264C
5.2
Page 37/46
Power Supply
For the BIU241 board, the input burden on the internal 5V bus is 1,25W. This includes the
watchdog, redundancy relays and communication ports.
The efficiency of the power supply is 78%.
NOTE:
5.3
During the start of the C264, there is a peak current. During the first
50ms, the peak current can reach 6.2A, as measured on the BIU-A03
board with a source of 125VDC.
CPU Boards
The CPU270 board manages the Flash and Ram memory in order to allow the C264 to have
more than 16 servers when possible (depending of the size of the data model).
SCE zips data model files for C264 and memorizes zipped data model files in its flash memory.
Whilst launching, AGENCY uncompress data model files one after another in computer RAM.
5.4
5.4.1
Nominal voltage
Current at Un (mA)
A01
24VDC
3.5
A02
48 thru 60VDC
5 for 48VDC
6.8 for 60VDC
A03
A04
220VDC
A07
The CCU200 board burden on the internal 5V bus is 400mW plus 400mW for each activated
relay.
5.4.2
24VDC
2.6 mA
48VDC
2.2 mA
110VDC
1.9 mA
125VDC
1.5 mA
220VDC
1 mA
For the CCU211 board, the input burden on the internal 5V bus is 290mW plus 400mW for each
activated relay.
C264/EN TD/C80
Technical Data
Page 38/46
MiCOM C264/C264C
5.5
5.5.1
Nominal voltage
Current at Un (mA)
A01
24 VDC
3.5
A02
48 thru 60 VDC
5 for 48 VDC
6.8 for 60 VDC
A03
A04
220 VDC
24VDC
2.6 mA
48VDC
2.2 mA
110VDC
1.9 mA
125VDC
1.5 mA
220VDC
1 mA
For the 24VDC voltage, there is no short peak current because of the
permanent high consumption on inputs >25ma.
35
30
Current (mA)
5.5.2
25
20
15
10
5
0
0
50
100
150
200
250
Tension (V)
300
C0159ENa
Technical Data
C264/EN TD/C80
MiCOM C264/C264C
5.6
5.6.1
Page 39/46
For the DOU201 board, the input burden on the internal 5V bus is 250mW plus 200mW for each
activated relay.
5.7
5.7.1
5.7.2
5.8
5.8.1
General
N.A.
5.8.2
TMU220
1A
< 0.02
< 0.02
5A
< 0.02
< 0.2
Vn = 130 V r m s
TMU210
TMU220
< 0.01
< 0.01
For the TMU210 board, the input burden on the internal 5V bus is 300mW.
For the TMU220 board, the input burden on the internal 5V bus is 300mW.
5.9
5.9.1
5.10
5.11
For the GHU201 and GHU211 boards the input burden on the internal 5V bus is 600mW.
For the GHU202 and GHU212 boards, the input burden on the internal 5V bus is <1mW.
C264/EN TD/C80
Technical Data
Page 40/46
6.
MiCOM C264/C264C
ACCURACY
For all specified accuracy, the repeatability is 2.5% unless otherwise specified.
If no range is specified for the validity of the accuracy, then the specified accuracy shall be valid
over the full setting range.
6.1
Reference Conditions
Quantity
Reference conditions
Test tolerance
General
Ambient temperature
20 C
2 C
Atmospheric pressure
86kPa to 106kPa
Relative humidity
45 to 75 %
Current
IN
5%
Voltage
VN
5%
Frequency
50 or 60Hz
0.5%
Auxiliary supply
24VDC, 48VDC-60VDC,
110VDC-125VDC,
220VDC
230VAC
5%
6.2
Measurement Accuracy
6.2.1
Accuracy
Current
Voltage
Frequency
0.01 Hz
Amplitude
< 1%
Phase
10 ppm/C
Harmonics
H15
Technical Data
C264/EN TD/C80
MiCOM C264/C264C
6.2.2
Page 41/46
Range
Deviation
Phase current
0.1 to 40 In
Typical 0.5% at In
Earth current
0.002 to 1 Ion
0.01 to 8 Ion
0.1 to 40 Ion
Voltage
57 to 260V
Typical 0.5% at Un
220 to 960V
Active Power
6.3
Reactive Power
Cos
Deviation
Sin
Deviation
0.866
<1.5%
0.866
<3%
0.5
< 3%
0.5
< 1.5%
2.
3.
4.
The isolation resistance must be higher than 100 M ohms, in agreement with procedure
LQD/P52/1
C264/EN TD/C80
Technical Data
Page 42/46
MiCOM C264/C264C
7.
TYPE TESTS
7.1
7.1.1
Conditions
Insulation Resistance
Dielectric Strength
5kV (CM)
Conditions
100 M at 500 VDC (CM and DM)
(between groups)
7.1.3
Conditions
Insulation Resistance
Dielectric Strength
5 kV CM and 3 kV DM
Technical Data
C264/EN TD/C80
MiCOM C264/C264C
7.2
Page 43/46
Mechanical Test
Type Test Name
Free Fall Test
Free Fall Packaging
Test
Conditions
Vibration Response
Powered On
Vibration Response
Not Powered On
Vibration Endurance
Not Powered On
Shocks Powered On
15g, 11 ms
10g, 11 ms
Bump Test Not
Powered On
C264/EN TD/C80
Technical Data
Page 44/46
7.3
MiCOM C264/C264C
Atmospheric Test
Type Test Name
Conditions
Test Ca:
IEC60068-2-1 (1990)
Test Ad:
-40C / 96 h
Powered On at 25C (for information)
Dry Heat Test
Operating
70C / 24 h
DICOT HN 46-R01-06
(1993)
55C / 10 days
Test Bd:
+70C / 96 h
Powered On at +70C
Enclosure Protection
7.4
Front: IP52
Conditions
T < 1.5 ms / I < 20 A
1.5ms < T < 150 ms / I < 10 A
T > 500 ms / I < 1.2 In
Supply variation
Vn 20%
Vn+30% & Vn-25% for information
Overvoltage (peak
strength)
N/A
1.32 Vn max
2 Vn during 10 ms (for information)
From Vn down to 0 within 1 minute
From Vn down to 0 within 100 minutes
N/A
Supply interruption
Reverse polarity
N/A
Ripple (frequency
fluctuations)
Technical Data
C264/EN TD/C80
MiCOM C264/C264C
7.5
7.6
Page 45/46
Conditions
Vn 20%
Frequency fluctuations
50 Hz: from 47 to 54 Hz
60 Hz: from 57 to 63 Hz
Voltage strength
N/A
Conditions
High Frequency
Disturbance
Electrostatic discharge
Radiated Immunity
Surge immunity
High frequency
conducted immunity
Class 3:
10 V, 0.15 80 MHz
Harmonics Immunity
Power Frequency
IEC 61000-4-8 (1993)
Magnetic Field Immunity
Class 5:
100A/m for 1mn
1000A/m for 3s
Class 5:
6.4 / 16 s
1000A/m for 3s
Damped oscillatory
IEC 61000-4-10 (1993)
magnetic field immunity + A1 (2001)
Class 5:
100 kHz & 1 MHz 100A/m
Power Frequency
Conducted emission
EN 55022 (1998) + A1
(2000) + A2 (2003)
Radiated emission
EN 55022(1998) + A1
(2000) + A2 (2003)
C264/EN TD/C80
Technical Data
Page 46/46
MiCOM C264/C264C
BLANK PAGE
Functional Description
C264/EN FT/C80
MiCOM C264
FUNCTIONAL DESCRIPTION
Functional Description
C264/EN FT/C80
MiCOM C264
Page 1/240
CONTENTS
1.
1.1
Software features
1.2
C264 Configurations
10
1.2.1
10
1.2.2
11
1.2.3
12
1.2.4
13
1.2.5
SBUS - Two C264 redundant computers with two extension racks with IEDs
14
1.2.6
15
1.2.7
16
1.2.8
SCADA TBUS - C264 Standalone with two extension racks with IEDs
17
1.2.9
18
1.3
20
1.4
C264 Standalone
20
2.
21
2.1
21
2.1.1
Definitions
21
2.1.2
Initialisation mode
21
2.1.3
Operational mode
22
2.1.4
Maintenance mode
23
2.1.5
24
2.1.6
Faulty mode
27
2.1.7
Halt mode
27
2.1.8
27
2.1.9
28
2.2
Database management
32
2.2.1
General
32
2.2.2
34
2.2.3
35
2.2.4
36
2.2.5
36
2.2.6
37
2.2.7
37
2.3
Self tests
37
2.4
Time management
38
2.4.1
External clock
39
2.4.2
40
2.4.3
40
C264/EN FT/C80
Page 2/238
Functional Description
MiCOM C264
2.4.4
40
2.4.5
41
2.4.6
42
2.4.7
Update method
42
2.4.8
42
3.
COMMUNICATIONS
43
3.1
44
3.2
44
3.3
45
3.3.1
Exchanges
45
3.3.2
46
3.3.3
Controls
46
3.4
47
3.4.1
47
3.4.2
47
3.4.3
Ethernet failure
48
3.4.4
49
3.4.5
49
3.5
50
4.
51
4.1
Input Check
51
4.2
Output check
51
4.3
Time tagging
51
4.4
51
4.4.1
Acquisition
51
4.4.2
52
4.4.3
Toggling
52
4.5
53
4.5.1
53
4.5.2
54
4.6
55
4.6.1
55
4.6.2
56
4.6.3
Encoding
57
4.7
58
4.7.1
Input ranges
58
4.7.2
Acquisition cycle
58
4.8
58
4.9
59
4.9.1
Encoding
59
4.9.2
Read Inhibit
59
Functional Description
C264/EN FT/C80
MiCOM C264
Page 3/240
4.9.3
60
4.10
Analog Setpoints
61
4.10.1
Output range
61
4.10.2
Output management
61
4.10.3
62
5.
DATA PROCESSING
63
5.1
63
5.1.1
63
5.1.2
64
5.1.3
66
5.1.4
71
5.1.5
72
5.1.6
IED inputs
73
5.1.7
Group processing
73
5.1.8
74
5.1.9
74
5.2
75
5.2.1
75
5.2.2
76
5.2.3
76
5.2.4
Scaling
76
5.2.5
77
5.2.6
77
5.2.7
78
5.2.8
79
5.2.9
82
5.2.10
82
5.2.11
83
5.2.12
84
5.2.13
85
5.2.14
88
5.2.15
90
5.2.16
90
5.2.17
91
5.2.18
91
5.2.19
93
5.2.20
TMU210: Algorithms
95
5.2.21
103
5.2.22
Manual suppression
104
5.2.23
Substitution
104
5.2.24
104
5.2.25
104
C264/EN FT/C80
Page 4/238
Functional Description
MiCOM C264
5.2.26
Transmission
105
5.3
107
5.3.1
107
5.3.2
107
5.3.3
Manual suppression
107
5.3.4
Substitution
107
5.3.5
107
5.3.6
108
5.3.7
Transmission
108
5.4
109
5.5
Energy counting
109
5.6
110
5.6.1
110
5.6.2
110
5.6.3
111
5.6.4
112
6.
CONTROL SEQUENCES
113
6.1
Description
113
6.1.1
General
113
6.1.2
114
6.1.3
117
6.1.4
118
6.1.5
121
6.1.6
123
6.1.7
Selection behaviour
127
6.1.8
128
6.1.9
Execution behaviour
128
6.1.10
129
6.1.11
132
6.2
136
6.2.1
136
6.2.2
136
6.3
137
6.3.1
137
6.3.2
138
6.3.3
143
6.4
Control of disconnectors
147
6.4.1
Disconnectors features
147
6.4.2
147
6.5
Control of transformers
148
6.5.1
Transformer features
148
6.5.2
148
Functional Description
MiCOM C264
C264/EN FT/C80
Page 5/240
6.6
151
6.7
152
6.7.1
Control to IEDs
152
6.7.2
IED controls
152
6.7.3
152
6.8
System controls
153
6.9
153
6.10
153
6.10.1
Mode Management
153
6.10.2
IED connected
153
6.10.3
Control mode
154
6.10.4
Uniqueness of control
154
6.10.5
Inter-control delay
154
6.10.6
154
6.10.7
Lock device
154
6.10.8
Running Automation
154
6.10.9
Interlocking
154
6.11
HV Control Sequences
155
6.11.1
Circuit breaker
155
6.11.2
Disconnector
155
6.11.3
Transformer
155
7.
AUTOMATIONS
7.1
156
7.1.1
Auto-Recloser (AR)
156
7.1.2
162
7.1.3
164
7.1.4
166
7.1.5
181
7.2
Synchrocheck
194
7.2.1
Synchrocheck General
194
7.2.2
Synchrocheck Schemes
195
7.2.3
Synchrocheck Algorithm
195
7.2.4
Synchrocheck Applications
196
7.2.5
196
7.2.6
196
7.2.7
197
7.2.8
Synchrocheck Calculation
197
7.2.9
197
7.2.10
197
7.2.11
197
7.2.12
Synchrocheck: Scheme LL: Live Line, Live Bus: Real Time Sequences
198
156
C264/EN FT/C80
Functional Description
Page 6/238
7.2.13
MiCOM C264
200
7.2.14
201
7.2.15
201
7.2.16
203
7.2.17
203
7.2.18
Synchrocheck Bypass
204
7.2.19
206
7.2.20
207
7.2.21
208
7.2.22
208
7.2.23
209
7.2.24
209
7.2.25
210
7.2.26
211
7.3
212
7.3.1
Interlocking: Inputs
212
7.3.2
Interlocking:Outputs
212
7.3.3
Interlocking: Control
212
7.3.4
Interlocking: Behaviour
212
7.4
216
7.4.1
Inputs
217
7.4.2
Outputs
217
7.4.3
Control
217
7.4.4
Behaviour
218
7.4.5
218
7.5
219
7.6
220
7.6.1
C264M
220
7.6.2
C264Fi
220
7.7
220
7.7.1
Inputs
220
7.7.2
Algorithm
221
7.7.3
Outputs
223
7.7.4
223
7.7.5
Configurable data
224
7.8
225
7.8.1
Inputs
225
7.8.2
Algorithm
225
7.8.3
Outputs
227
7.8.4
227
7.8.5
Configurable data
228
Functional Description
MiCOM C264
C264/EN FT/C80
Page 7/240
8.
USER INTERFACE
229
9.
RECORDS
230
9.1
230
9.1.1
Data storage
230
9.1.2
230
9.1.3
Events
230
9.1.4
231
9.1.5
231
9.1.6
233
9.1.7
Disturbance Recorder
233
9.2
235
9.2.1
Alarms
235
C264/EN FT/C80
Functional Description
Page 8/238
MiCOM C264
BLANK PAGE
Functional Description
MiCOM C264
1.
C264/EN FT/C80
Page 9/240
1.1
Software features
The C264 computer is a modular product at the hardware, software and functional levels.
You can fully configure all functions in agreement with customer needs and requirements.
The C264 computer includes:
Direct process interface through Digital Inputs (DI), Digital Outputs (DO), Analogue
Inputs (AI), Analogue Outputs (AO) and Current Transformer (CT)/Voltage
Transformer (VT) boards
Enhanced inner management with database management, self-test controls and the
capability to synchronize all of the devices.
Communications with the Telecontrol Bus (TBUS), Station Bus (SBUS) and Legacy
Bus (LBUS). Please refer to the Communications (CT) chapter
Programmable Scheme Logic (PSL) for all C264 computers except the C264
Standalone computer
C264/EN FT/C80
Functional Description
Page 10/238
MiCOM C264
Depending on whether the Main Rack is redundant or not, the software features are different
for a redundant main 1 rack and for a non-redundant main rack.
1.2
C264 Configurations
The MICOM C264 computer is the base module of the PACiS architectures.
Each C264 computer includes a rack. Computer boards are installed on the rack. The rack is
the technical name, but it can have different functional names.
The functional name depends where the C264 computer is installed in a system. The
functional names for the rack include:
Main rack:
Main 1 rack:
Main 2 rack:
Extension rack:
Multirack system:
racks
Redundant system: A system that includes an active Main 1 rack and a standby Main
2 rack
The family of C264 computers included in this chapter include the devices and configurations
that follow:
1.2.1
Functional Description
MiCOM C264
1.2.2
C264/EN FT/C80
Page 11/240
C264/EN FT/C80
Functional Description
Page 12/238
1.2.3
MiCOM C264
IEC 61850
SBUS
Ethernet port 1
C264
Main
Rack
Ethernet port 2
Inter Rack
connection
LBUS
Extension
Rack
Extension
Rack
LBUS
C0435ENb
For more technical data about the C264 with two extension racks with IEDs, please refer to
the chapter Technical Data.
Functional Description
C264/EN FT/C80
MiCOM C264
1.2.4
Page 13/240
IEC 61850
SBUS
C264
Main 1
Rack
C264
Main 2
Rack
I/O
redundancy
IED
LBUS
IED
IED
C0436ENb
C264/EN FT/C80
Functional Description
Page 14/238
1.2.5
MiCOM C264
SBUS - Two C264 redundant computers with two extension racks with IEDs
Each C264 connects through the Ethernet Port 1 to the SBUS and uses protocol IEC61850
Each C264 connects through Ethernet Port 2 to two extension racks
Each extension rack connects through the LBUS to the IEDs. These C264s each include a
CPU 270.
For more technical data about the two C264 redundant computers with two extension racks
with IEDs, please refer to the chapter Technical Data C264/EN TD/Cxx.
Functional Description
C264/EN FT/C80
MiCOM C264
1.2.6
Page 15/240
In the C264 Standalone configuration, you do not have C264 redundancy nor the multi rack.
Only one C264 Standalone computer is provided. The main rack (not redundant) manages
the direct acquisitions and controls. The C264 Standalone computer with the main rack:
Receives all data from the IO boards on the rack and updates the archives (SOE
waveform)
Manages the controls received through the active SCADA connection and sends them
to the extension racks
Manages the digital input and measurement acquisition. In event the main 1 rack and
main 2 rack are in a redundant configuration, this function is not available.
Manages the controls. In event the main 1 rack and main 2 rack are in a redundant
configuration, this function is not available.
NOTE:
The C264 Standalone is the new technical name for the C264 Remote
Terminal Unit (RTU).
C264/EN FT/C80
Functional Description
Page 16/238
1.2.7
MiCOM C264
TBU
C264
Main
Rack
LBUS
In the C264 Standalone configuration, you do not have C264 redundancy nor multi rack
configuration. Only one C264 Standalone computer is provided. The main rack (not
redundant) manages the direct acquisitions and controls. The C264 Standalone computer
with the main rack:
Receives all data from the IO boards on the rack and updates the archives (SOE
waveform)
Manages the controls received through the active SCADA connection and sends them
to the extension racks
Manages the digital input and measurement acquisition. In event the main 1 rack and
Main 2 rack are in a redundant configuration, this function is not available.
Manages the controls. In event the main 1 rack and main 2 rack are in a redundant
configuration, this function is not available.
Manages the communication with the IEDs, and the acquisition of the real time data.
In event the main 1 rack and main 2 rack are in a redundant configuration, this
function is not available.
Functional Description
C264/EN FT/C80
MiCOM C264
1.2.8
Page 17/240
SCADA TBUS - C264 Standalone with two extension racks with IEDs
The C264 connects through the Ethernet Port 1 through the TBUS to the SCADA
The C264 connects through the Ethernet Port 2 to two extension racks.
Each extension rack connects through the LBUS to the IEDs. This C264 includes a CPU
270.
TBUS
Main
Rack
Extension
Rack
Extension
Rack
LBUS
LBUS
C0440ENb
The main rack centralises all of the data acquired by all of the extension racks, and manages
the SCADA interface. In this configuration, you can configure as many as 16 extension
racks. The main rack (non redundant) manages direct acquisitions and controls. The main
rack:
Receives all data acquired from the extension rack and updates the archives (SOE
waveform)
Manages the database downloads through the SCADA connection and distributes the
new configuration to all of the other extension racks
Receives the controls through the SCADA connection, manages the controls, and
sends the controls to the extension racks
Manages the control, that is directly handled by the main rack. In event of a redundant
configuration, this function is not available
Manages the communication with the IEDs, and real-time data acquisition. In event of
a redundant configuration, this function is not available.
C264/EN FT/C80
Functional Description
Page 18/238
MiCOM C264
Manage the controls that they receive from the main rack
If there are no serial ports available on the main rack, the extension rack can manage
the printer.
The main 1 rack and the main 2 rack centralise all of the data acquired by the extension
racks and manage the SCADA interface. In this redundant C264 Configuration:
Functional Description
MiCOM C264
C264/EN FT/C80
Page 19/240
There are no I/O boards installed in the main 1 rack or in the main 2 rack
There are no IEDs connected to the serial ports of the main 1 rack and main 2 rack
Of the two computers, SCADA makes the selection and designates one computer as the
main 1 rack and the other computer as the main 2 rack.
Neither the main 1 rack nor the main 2 rack manage these Automations: PSL, PLC,
Auto-recloser, Synchrocheck, AVR, ATCC.
For hardware, the main 1 rack and main 2 rack are identical.
Receives all of the data acquired on the extension racks and updates the archives
(SOE waveform)
Manages the database downloads through the SCADA connection and distributes the
new configuration to all of the other extension racks and to the main 2 rack
Receives the controls through the SCADA connection, manages the controls, and
sends the controls to the extension racks.
Receives all of the data acquired on the extension racks and updates the archives
(SOE waveform)
Freezes all of the transmissions on the SCADA link: Reset of the Link: Function 0
In event of a SCADA General Interrogation (GI Request) to the main 2 rack, the main
2 rack assumes the functions of the main 1 rack
Receives the configuration database from the main 1 rack and updates it
Communicates the status of the main 1 rack and main 2 rack to the SCADA. You can
connect the watchdog relays to the standard DI of one extension rack.
C264/EN FT/C80
Functional Description
Page 20/238
1.3
MiCOM C264
CPU 260
CPU 270
CPU Type 2
CPU Type 3
CPU2
CPU3
No
Yes
Yes
Yes
No
Yes
No
Yes
No
Yes
Counter management
No
Yes
Function
1.4
C264 Standalone
The C264 Standalone computer includes the functions that follow:
Function
ISAGRaF
Yes
PSL
Yes
Load Shedding
Yes
Functional Description
C264/EN FT/C80
MiCOM C264
2.
Page 21/240
2.1
2.1.1
Definitions
Computer modes: the computer operates in the modes that follow:
Initialisation mode
Operational mode
Normal mode
Downgraded mode
Maintenance mode
Test mode
Faulty mode
Halt mode
2.1.2
Anomaly: a fault that causes a downgrade in the behaviour of the computer. There
are hardware and/or software anomalies, as follows:
Board failure
Loss of synchronisation
Loss of communication.
Software fault: a major software error causes a software fault, that causes the
computer to go into the Faulty mode.
Vital hardware fault: a fault that causes a software halt, that causes the computer to
stop the application software. Vital hardware faults include:
CPU fault
Bus fault
Initialisation mode
After a power on or a manual reset event occurs, the computer goes into the initialisation
mode. The initialisation mode does not exceed one minute. The computer performs different
types of tests and checks, as follows:
Flash memory test: in event of a problem, the computer tries to repair this flash memory. If a
vital hardware test fails, the computer goes out of the initialisation mode and into the Halt
mode.
C264/EN FT/C80
Page 22/238
Functional Description
MiCOM C264
The computer performs non-vital hardware tests only on those boards installed in the
computer, and on the peripheral devices connected to the computer:
Communication boards: the computer performs this test within the communication
protocol
Displays, such as the LCD and LEDs: the computer does a single test for the
presence of the HMI board
Peripheral devices, such as the printer, external clock, and so on: the computer
uses timeouts to do a check for the presence of the peripheral devices.
If one of these non-vital hardware tests fails, the computer goes into the related
downgraded mode.
At each restart of the computer, the computer performs these database coherency tests.
These tests make sure that the database is compatible with the hardware and with the
software of the computer, and that the database does not contain incoherent configuration
data. The database coherency tests include:
If any one of these checks fails, the computer goes into the Maintenance mode.
2.1.3
Operational mode
This mode includes two sub-modes: Normal mode and Downgraded mode.
Functional Description
MiCOM C264
2.1.3.1
C264/EN FT/C80
Page 23/240
Normal mode
This is the nominal operating mode of the active computer. In this mode the computer
activates the watchdog relay and all of the computer functions are available. A detection of
an error and in agreement with the cause and the severity of the failure, can cause the
computer to go into the related Downgraded mode, to the Faulty mode or to the Halt mode.
In the Normal mode, you can use the local Human Machine Interface (HMI) or upper level
maintenance request, to request a transition to the Maintenance mode.
In the Normal mode, you can use the local (HMI) or upper level simulation request, to
request a transition to the Test mode.
In the Normal mode, you can do these database operations:
Modify a database
The computer transmits the results of the Test mode to the local HMI and to the upper level
remote control point (RCP).
2.1.3.2
Downgraded mode
In event of an anomaly, the computer goes into the Downgraded mode. In this mode, the
operation of the computer is not very disturbed because only few functions are degraded.
The computer activates the watchdog relay.
The type of downgraded mode depends on the hardware configuration of the computer. The
different events that cause a downgraded mode include:
When you or the computer resolve the cause of the transition into the Downgraded mode,
the computer returns to the Normal mode.
2.1.4
Maintenance mode
In Maintenance mode, the station bus (SBUS) operates: you can communicate on the
SBUS to manage the database. The Maintenance mode shows on the local HMI (LED and
LCD) and on the upper level.
The computer deactivates the watchdog relay..
In this mode, you can manage the database:
Download a database
Modify a database
In the Maintenance mode, you can use the local Human Machine Interface (HMI) or upper
level active request, to request a transition to the Operational mode. The Operational mode
includes the Normal mode and the Degraded mode.
C264/EN FT/C80
Functional Description
Page 24/238
2.1.5
MiCOM C264
The Test mode shows on the local HMI (LED and LCD) and on the upper level.
In the Test mode, you can use the local HMI or upper level end-of-simulation request, to
request a transition to the Operational mode. The Operational mode includes the Normal
mode and the Degraded mode.
The behavior of the CPU and the DSP in agreement with the C264 mode shows in the table
that follows. This table is true only if there is no Programmable Scheme Logic (PSL),
managed by the CPU, between the start/operate BI and the DSPIO trip relay.
Functional Description
C264/EN FT/C50
MiCOM C264
Page 25/234
Functional Description
C264/EN FT/C80
MiCOM C264
2.1.6
Page 27/240
Faulty mode
In any mode, when a fault occurs to prevent the proper operation of the software, the
computer goes into the Faulty mode.
When the computer detects a failure on the DO boards, and if the configuration allows, the
computer goes into the Faulty mode. Each time the computer goes into the Faulty mode, an
internal counter increments.
There are only two ways to go out of the Faulty mode:
If the value of the internal counter remains lower than the Max_Fault parameter defined
during the configuration step, the computer goes into the Initialisation mode. When the
elapsed time since the last increment of the internal counter equals the value
Fault_Detection_Lasting parameter defined during the configuration step, the value of the
counter automatically resets
When the value of the internal counter reaches Max_Fault, the computer goes into the Halt
mode.
2.1.7
Halt mode
In this mode, the computer deactivates the watchdog relay and all the output relays. The
computer does not operate anymore. The only way to go out of this mode is to perform a
manual reset.
2.1.8
boot
INITIALISATION
automatic
reset
Major
hardware
fault
manual reset
Init OK
hardware test OK
and coherency not OK
FAULTY
major hardware fault
or software fault
no DB
major hardware fault
or software fault
maintenance request
simulation request
end of simulation
vital
hardware
fault
MAINTENANCE
OPERATIONAL
TEST
active request
vital hardware
fault
HALT
Counter of faults = Max_Fault
C0288ENa
C264/EN FT/C80
Page 28/240
2.1.9
Functional Description
MiCOM C264
The two SCADA connections, one to the main 1 rack and one to the main 2 rack, are
completely independent. For these two connections, there is no synchronisation of protocols,
and each of these racks can have a different station address. The principle here is different
from the standard redundant function, where the sequence of the messages on each
connection are synchronised and where each rack has the same station address.
In the redundant configuration, the main 1 rack does not manage direct acquisitions,
controls, or IED connections.
The main 1 rack and the main 2 rack have a single address on one of the two SCADA
connections. This allows the main 1 rack and the main 2 rack to manage two different
networks.
The main 1 rack operates when:
The communication was set up on the main 1 rack connection to the SCADA. The GI
request (ASDU 100) message confirms the set-up of the connection.
The main 2 rack was in operation, a failure occurred, and the main 1 rack received a
GI request.
When the SCADA detects a communication failure, the main 1 rack in operation becomes
the main 2 rack. The SCADA must stop to communicate with one rack when it decides to
communicate with the other rack.
For more details, please refer to the figure that follows:
C0447ENa
Functional Description
C264/EN FT/C80
MiCOM C264
Page 29/240
Receives all of the data acquired on the extension rack and updates the archives
(SOE, slow waveform)
Transmits all of the data acquired on the extension rack through the SCADA
Receives the database through the SCADA connection or from the CAT and
distributes the new configuration to all of the other racks, including the main 2 rack
Manages the controls received through the active SCADA connection and sends them
to the extension racks
Receives all of the data acquired on the extension rack and updates the archives
(SOE, slow waveform)
In event of a SCADA connection reset (GI Request), the main 2 rack does the
functions of the main 1 rack
Receives the configuration database from the main 1 rack and updates its own
configuration database
To communicate the status of the main 1 rack and main 2 rack to the SCADA, you can wire
the watchdog relays to the standard DI of one extension rack.
For the C264:
The two redundant computers are the main 1 computer and the main 2 computer. The
computer that performs the bay management is the active computer; the other one is the
standby computer. In this configuration, the redundant computer can be:
During the boot time, and if both computers operate, the main 1 computer is the active
computer.
The two computers perform the same functions at the same time: inputs acquisition and
processing; archiving; automation; but at a given time, only the active computer sends
controls to the electrical process or on the SBUS. A PACiS IEC-61850 client receives data
from the two computers: this client processes only the data it received from the computer in
the active mode. Only the computer in the active mode manages the communication with
IED or SCADA.
C264/EN FT/C80
Functional Description
Page 30/240
MiCOM C264
This switch from the active mode to the standby mode, and from the standby mode to the
active mode, is performed automatically as follows:
DI1/DO1 to indicate the Active Status: DO1 is closed if the computer is Active
A value is given to each type of computer failure: the computer IS is calculated by summing
all failure values. The healthiest computer has the minimal internal status. The healthiest
computer is active.
Computer failure
Value
0x20
0x10
0x08
0x04
0x02
0x01
The algorithm to elect the Active computer shows in the table that follows.
The initial state is Initialisation (state 0) and the DI11 event is generated.
L_IS is the internal status of the computer, R_IS is the internal status of the redundant
one.
The confirmed DI2 1 event is a detection of a Station Bus failure on the other computer
(DI2 = 0) confirmed during 20 seconds.
T1 is the timer of Active status confirmation during the computer initialisation (default value:
5 seconds for the Main 1 computer, marked in configuration, 30 seconds for the Main 2
computer). T2 is the timer of master election (default value: 5 seconds).
Functional Description
C264/EN FT/C80
MiCOM C264
Page 31/240
State 1:
State 2:
Waiting end of
Standby
initialisation / T1
timer on going
DI11
/
T1 timer
go to state 1
DI1=1
go to state 2
confirmed
DI21
State 3:
Standby / T2
timer ongoing
State 4:
Active
State 5:
Standby mode
on-going
close DO1
go to state 4
stop T2 timer /
go to state 4
stop T1 timer
go to state 2
open DO1
go to state 5 /
stop T2 timer
go to state 2
T2 timer
launching
close DO1
go to state 3
Remore IS
If (L_IS<R_IS)
then
T2 timer
launching
close DO1
go to state 3
If (L_IS>R_IS) /
then
stop T2 timer
open DO1
go to state 2
End of T1
timer
If DI11
not possible
not possible /
End of T2
timer
go to state 4
not possible
not possible
not possible
then:
T2 timer
launching
close DO1
go to state 3
else:
go to state 2
/
End of
standby mode
going-on
T2 timer
launching
go to state 3
else
go to state 2
C264/EN FT/C80
Functional Description
Page 32/240
2.2
2.2.1
MiCOM C264
Database management
General
The C264 uses structured databases to manage data. The main principle is that the
computer will only operate with other PACIS devices if their database versions are identical.
A database (DB) is a file that includes the description of the whole of the electric process,
and all of the devices that the computer is likely to communicate with: IED, HMI, and so on.
The database also includes some parameter settings for the software and for the
transmission protocols. Use a separate PACiS tool, the System Configuration Editor (SCE),
to create and version the databases. Each database has a related VDBS (System Baseline
Version).
You can download a standby database even if the computer is in operation: use the
filename.adb format.
You can download a database into the flash memory of the computer in two ways:
Use the PACiS tool, the System Management Tool (SMT) to download the database
thru the IEC61850 station bus (SBUS).
Use the PACiS tool, the Computer Administration Tool (CAT), to download the
database directly over Ethernet. Operators generally use the CAT only for the
download of the first database. During the download, the CAT sends the database to
all of the other racks. This database becomes the new Standby database. At the
Switch command, the computer cascades the switch operation to the other racks.
From SCADA, the C264 receives the database file and saves it in RAM, but does not send it
to the other racks.
On the C264, the database status shows only on the main rack LCD.
The main 1 rack does a check for the compatibility between its database and the database
installed in the main 2 rack and in the extension racks. It the databases are different, the
main 1 rack has the most recent version and deletes the databases on the other racks.
If the main database on the main 1 rack is compatible with the standby database on the
other rack, the computer switches the database.
At any moment, the computer stores as many as two DBs in its flash memory. The two DBs
and their related VDBS have the labels DB1, VDBS1; and DB2, VDBS2.
Each database of the computer, DB1 and DB2, has one of the states that follow:
Standby: the DB was downloaded into the non volatile memory of the computer, but
the software does not acknowledge this version
Current Modified: the DB had a change to a parameter setting and the software
currently acknowledges the DB
Standby Modified: the DB had a change to a parameter setting and the software
does not acknowledge the DB.
Functional Description
C264/EN FT/C80
MiCOM C264
Page 33/240
In the computer, the life cycle of the DBs shows in the figure that follows:
Absent
Downloading
Switching
Standby
Current
Parameter setting
Standby
Modified
Current
Modified
Parameter setting
Switching
C0308ENa
State 1
State 2
State 3
State 4
Current
Current Modified
Current
Current Modified
Standby
Standby
Standby Modified
Standby Modified
A file descriptor with the label DB context, stored in the flash memory of the computer,
includes the configuration of the DB installed on the device. This file descriptor, that includes
the state of each of the two databases and their related VDBS (for example, DB1 and
VDBS1; DB2 and VDBS2), allows you to know the configuration of the databases at the
moment of the computer boot (initialisation mode), and to start again with the Current
database, if it exists. To update the file descriptor DB Context, use these functions:
Download a database
Check a database
Modify a Database.
C264/EN FT/C80
Page 34/240
2.2.2
Functional Description
MiCOM C264
Use the PACiS SMT tool to send a request to start the transfer of the database.
2.
3.
Transmit the response to the device that called. If another request on the same DB is
already in progress, the device will refuse your request.
4.
Download the DB file and the related Vdbs. The computer does a check of the
integrity of the files: it calculates the checksum and control of the DB
5.
In event of a fault, the computer sends a signal to announce the failure of the transfer,
to the device that called
6.
In event of a successful transfer of the DB, the computer controls the DB compatibility
7.
In event of an invalid DB, the computer sends a signal to announce the failure of the
DB installation, to the device that called
8.
9.
Assigns the state standby to the downloaded DB and related Vdbs installed in the
computer
Sends a signal to announce the success of the DB installation to the device that
called.
The computer updates the file descriptor, Context DB, in flash memory.
Functional Description
C264/EN FT/C80
MiCOM C264
2.2.3
Page 35/240
T0 + T1
STANDBY
CURRENT
STANDBY
Vdbs n.m
Vdbs x.y
Vdbs x.y
Vdbs n.m
DB1
DB2
DB2
DB1
T0 + T1
MAINTENANCE
MAINTENANCE
T0 + T1
CURRENT
STAND-BY
Vdbs x.y
Vdbs n.m
DB2
DB1
OPERATIONAL
C0309ENa
C264/EN FT/C80
Functional Description
Page 36/240
MiCOM C264
When the computer receives the switch command, the computer downloads the database to the
other racks. Please refer to Figure 5: Database Switching
2.2.5
Functional Description
C264/EN FT/C80
MiCOM C264
2.2.6
Page 37/240
2.2.7
Is the object known to the computer, that is, is the object really present in the
database
Can the computer set the data
Is the value of the parameter setting compatible with the type of data conveyed:
does the value belong in the range of acceptable variation
2.
If the request is incoherent, the computer sends a negative report to the device that
sent the request.
3.
4.
5.
6.
7.
8.
Update the file descriptor, that is the Context database, in the flash memory
Is the object known to the computer, that is, is the object really present in the
database
Is the value of the parameter setting compatible with the type of data conveyed:
does the value belong in the range of acceptable variation
2.
If the request is incoherent, the computer sends a negative report to the device that
sent the request:
3.
Develop the response to include the parameter setting and to send it to the device that
sent the request
For the C264 , you can use the Computer Administration Tool (CAT) to upload and store a
DB as large as 20 MB in the flash memory.
2.3
Self tests
The computer performs these self-tests:
Software (software fault) cyclically to make sure that software tasks are active and do
not take all the CPU time
C264/EN FT/C80
Functional Description
Page 38/240
2.4
MiCOM C264
Time management
The main purposes of the time management include:
To synchronize the internal clock in the computer (referred to as the local clock) with:
SCADA
SBUS or LBUS
Operator
To synchronise other devices through the SBUS with the local clock
You can synchronize the local clock with an external time reference from four sources:
SCADA sends a clock message through the TBUS and through the gateway1
The system master clock sends a clock message through the SBUS - SNTP 2
There is a priority rule for these four external time references. If the external clock operates,
it locks out changes from the three other sources: you cannot make modifications to the local
clock in these ways:
Locked out: SCADA sends a clock message through the TBUS and through the
gateway
Locked out: The system master clock sends a clock message through the SBUS
For the C264 Multirack system, the main 1 rack delivers time synchronization for the main 2
rack and for the extension racks.
In event an external clock disconnects or does not operate, there is a priority order for the
three external time references that remain:
1.
SCADA sends a clock message through the TBUS and through the gateway
or
2.
The system master clock sends a clock message through the SBUS
Just after the local clock is synchronized, and if it is the master system clock of the LBUS,
the computer synchronises the Intelligent Electronic Device (IED) in agreement with the
synchronisation procedure of the protocol. If the local clock is not synchronised, the
computer synchronises periodically the IED all the same.
When the local clock is synchronised, all events and measurements include a time tag with a
synchronised attribute. If the synchronisation is lost, or was never achieved, the attributes
indicate that the time tag is not synchronised.
For a substation, the PACiS architecture can synchronize as many as 120 devices, such as
the C264, OI, gateways, IED Relays, IEC61850 Relays, and so on.
1
2
Functional Description
C264/EN FT/C80
MiCOM C264
Page 39/240
External clock
The external clock receives the synchronisation signal through one of several protocols:
GPS, DCF77, and so on. Periodically, the external clock sends the synchronisation signal,
that includes the hour and the date, to the dedicated IRIG-B input of the MiCOM C264 /
C264C computer.
Each computer has its own local clock. The local clock synchronises with the signal from the
external clock. In this system architecture, the local clock operates as the System Master
Clock.
In event of the loss of the radio signal from the external clock, two events can occur:
1.
Some external clocks include a very accurate oscillator. After a loss of radio signal,
these external clocks can synchronise the computer for 8 hours. The external clock
sends two messages thru the protocol. The text of the messages is in agreement with
the manufacturer specifications. For example:
no radio received
loss radio signal since more 8 hours
The local clock remains synchronised with the external clock until the message loss
radio signal since more 8 hours activates. The status of the local clock now shows
as not-synchronised.
C264/EN FT/C80
Page 40/240
2.
Functional Description
MiCOM C264
Some external clocks do not have the internal accuracy to support the radio signal. In
this event, when the confirmation of loss radio signal occurs in a few minutes, the
status of the local clock shows as not-synchronised
If the computer operates as the system master clock for the other devices in the substation,
then it continues to send the clock synchronisation message to the other devices, even if the
local clock, or system master clock, is not synchronised with an external time reference. A
binary input is dedicated to monitor the status of the external clock.
2.4.2
2.4.3
2.4.4
Functional Description
MiCOM C264
C264/EN FT/C80
Page 41/240
If the computer does not receive the clock synchronisation messages from the external
clock, from the SCADA gateway, or from the system master clock, you are allowed to set the
time manually.
Normally, you must manually set only the system master clock. You must use the correct
tool for the specific system master clock.
With the C264 local Operator Interface, with the Human Machine Interface (HMI) front panel,
or with the maintenance laptop computer and the Computer Administration Tool (CAT), you
can set the time and date.
You use two commands:
You can reserve a third command to do a check on the date and hour values.
You must raise a manual time-set-indication. The computer makes a record of all operator
actions.
2.4.5
Loss of the external clock; loss of SCADA gateway clock synchronisation message; or
loss of the system master clock
An indication that the local clock was roughly synchronised. This indication shows any
time difference, between the local clock and the clock synchronisation message, that
is greater than the fixed value: threshold = 20 millisecond. The computer sends a
message about the discrepancy, prints the message, and archives the event.
Indication that the operator performed a manual time set. This manual time set
indication is required to time-tag the events that occur.
The internal time format for the local clock is Universal Time Coordinate (UTC). The time
difference between UTC and the local time is set during configuration.
The local clock operates automatically:
For seasonal time changes: it uses the values for Daylight Savings Time (DST) as
shown in the Time Zone Adjustment Table (TZTAB) file. The TZTAB file shows the
differences between UTC and local time.
If the DST rules change, you can set the new rules in the computer.
The computer manages the milliseconds with its own quartz.
The Local Clock Update function manages the synchronisation status of the computer as
follows:
Not synchronized: this is the status at initialization, the computer has never been
synchronized since booting or rebooting. Date and time are invalid.
Synchronized: the computer receives periodically the date and time. Date and time
are valid. Or the computer is master clock on the Ethernet network for other
equipment.
C264/EN FT/C80
Functional Description
Page 42/240
MiCOM C264
At initialisation, the computer shows the external clock as not-synchronised with the local
clock. This status remains the same until you send a control message to the initialisation
driver to receive synchronisation frames from an external time reference. When the control is
OK and at the reception of the first external clock message, the synchronisation upon
external clock is declared valid and the external clock is considered connected.
This synchronisation with the external clock could fall back to invalid: for example, in event
the computer did not receive an external synchronisation message for N minute(s). This can
indicate an external clock failure, such as a disconnect or a message that contains invalid
data. The value of this timing is 300 seconds.
In event of an external clock failure, the local clock maintains the frequency in effect before
the external clock failed. The computer generates an internal signal or alarm and declares
the system master clock invalid. When this occurs, the computer makes a nonsynchronisation mark against each event, for as long as the synchronisation with the
external clock remains invalid.
When a device on the SBUS does not receive a clock synchronisation message in 180
seconds, it raises an alarm. The events processed by this device are tagged with a special
mark and with the time, and the device stops the transmission of the synchronization frame
to the IEDs.
2.4.6
2.4.7
If the external clock is lost, then the local clock update shows the loss of the external
clock
If the clock message from the SCADA gateway is lost, then the local clock update
shows the loss of the SCADA gateway clock message
If the system master clock is lost, then the local clock update shows the loss of the
system master clock
Update method
When the computer validates the external clock acquisition, the computer manages the
synchronisation of the internal system master clock to the external time reference as follows:
If a difference between the local clock value and the external time reference value
transmitted exists, [C Local C External] 0:
If [C Local C External] < 1 ms, the local clock is not modified
If [C Local C External] > 1ms, two different events are processed:
1.
If [C Local C External] Threshold (20 ms), the value of the local clock is
progressively corrected (reduced or increased). This compensation is performed in a
set time (t1=60 s).
2.
If [C Local C External] Threshold (20 ms), the hour in the local clock is updated
roughly.
If an operator gets the external clock time, the operator must update the local clock.
2.4.8
Functional Description
C264/EN FT/C80
MiCOM C264
3.
Page 43/240
COMMUNICATIONS
The C264 includes different types of communications:
1.
0 or 1 or 2
4 or less
2.
0 or 1 or 2 or 3
4 or less
3.
0 or 1 or 2 or 3 or 4
4 or less
allowed
SCADA
TBUS
SBUS
Telecontrol Interface
IEC 61850
I / O Boards
LBUS
IED
C0005ENd
FIGURE 7: COMMUNICATIONS
C264/EN FT/C80
Functional Description
Page 44/240
3.1
MiCOM C264
Master / Slave
C264
behaves as
Slave
DNP3
Master / Slave
Slave
MODBUS
Master / Slave
Slave
Serial
T101
Master / Slave
or Balanced
Slave
Serial
Serial
T104
Balanced
Slave
Over IP
Over IP
HNZ
Master / Slave
Slave
Elenas (Indonesia)
HNZ
Master / Slave
Slave
Yemen
Protocol
Protocol Type
DNP 3.0
C264 BCU
C264 Standalone
Master/slave protocols: DNP 3.0, DNP3 over IP, MODBUS, T101, HNZ-Elenas, HNZYemen
DNP3 over IP, T104: Ethernet 10 or 100 Mb/s: RJ45 connector or optical fibre
(multimode or monomode)
On the C264, you can configure as many as 2 different serial telecontrol protocols. If you use
the Ethernet IEC 104, you can connect as many as 4 independent clients.
The redundancy is not available for T104, DNP3 over IP, and MODBUS.
3.2
ModBus
DNP 3.0
Optical fibre
CAUTION:
CAUTION:
On the C264, as many as four serial ports are available to make four networks with as many
as four different protocols.
Functional Description
C264/EN FT/C80
MiCOM C264
3.3
Page 45/240
IEC 61850
The optical port is optional. To increase the number of Ethernet port, two Ethernet switch
boards are available:
3.3.1
SWR with 4 RJ45 ports and 2 optical ports for a redundant ring (multimode or
monomode)
Exchanges
C264 computer acquires & sends data on IEC-61850 network using REPORT/ GOOSE.
The REPORT is specific between a server and one client, it provides:
data value
data state or quality attribute (validity and several kind of invalid state)
time tag quality attribute (server synchronised or not when event has occurred)
Data quality defines if data is valid or several kind of invalidity: unknown when disconnected,
Saturated, Undefined REPORTS are sent/received with their RFI (Reason For Inclusion):
periodic, spontaneous state/value change or following control.
The GOOSE is a short message (data value and quality) sent in multicast to all SBUS
equipment, this is quicker than Report.
C264/EN FT/C80
Functional Description
Page 46/240
3.3.2
MiCOM C264
Measured Information
Controls
C264 supports Common Data Classes control expressed with SPC, DPC, INC and APC
configured as Direct Execute or SBO.
Functional Description
C264/EN FT/C80
MiCOM C264
Page 47/240
3.4
3.4.1
T104
C264
Main 1 Rack
CAT
C264
Main 2 Rack
C264
Extension Rack No.1
C264
Extension Rack No.2
Ethernet Link
Ethernet Switch
C0452ENb
The internal communication on the Ethernet C264 network uses proprietary protocol with
unicast messages. Consecutively all messages used by the computer for internal data
exchanges remain inside the C264. These messages do not pollute the external network
reserved for the SCADA interface.
Furthermore, the CAT tool uses also the Ethernet broadcast to identify racks. This tool is
used only for maintenance purpose (Software and configuration downloading)
Acquisition and front-end racks must have the same group number when they are attached
to the same C264. This group number is defined using the CAT and is limited to 16.
3.4.2
C264/EN FT/C80
Page 48/240
Functional Description
MiCOM C264
The computation of the network tree is done only one time by the spanning tree algorithm of
External switches.
3.4.3
Ethernet failure
Ethernet ring opening
The consequence of the ring opening involves to lose the communication between the Main
1 rack and the Main 2 rack.
Functional Description
C264/EN FT/C80
MiCOM C264
Page 49/240
Consecutively we have:
3.4.4
Data transfer from extension rack #1 through the External Ethernet infrastructure
(outside the C264 Ethernet network) to the Main 2 rack.
Ethernet ring opening and rebuilding of routine table ordered by the spanning tree
algorithm (> 30 s if 802.1D used)
T104
C264
Main 1 Rack
C264
Main 2 Rack
C264
Extension Rack No.1
CAT
C264
Extension Rack No.2
Ethernet Link
Ethernet Switch
C0455ENb
The other events of rupture of the Ethernet C264 network do not involve:
-
All data produced by the insulated rack are defined in an unknown state.
The other racks of the C264 (remaining on Ethernet continuity) are fully operational. Data
transferred to the Main racks through the Standalone private communication do not use the
external Ethernet infrastructures.
3.4.5
C264/EN FT/C80
Functional Description
Page 50/240
3.5
MiCOM C264
Port 1
Port 2
Comments
IEC61850 SBUS +
SCADA IP 1
SCADA IP 2
2 independent SCADA
protocols with different
database
SCADA IP 1
SCADA IP 2
2 independent SCADA
protocols with different
database
IEC61850 SBUS
SCADA IP
TABLE 2
Functional Description
C264/EN FT/C80
MiCOM C264
4.
Page 51/240
4.1
Input Check
Input data coming from the physical MiCOM C264 boards or from the different
communication networks are periodically checked.
Invalidity status of these data is internally fixed for:
4.2
Open Circuit (AI kind 4-20 mA with current value under 4mA)
Output check
Digital Output boards are periodically checked at their logical level. In the event of a logical
circuit test fail the board is set faulty, controls on this board or upon disconnected IEDs are
refused.
4.3
Time tagging
All physical input data are time tagged at 1 ms accuracy. All internal logic data are time
stamped at 1 ms accuracy.
Analogues acquisition time tagging is done but driven by periodic polling of this kind of
board. Periods are based on multiple of 100ms.
Information coming from IED are time tagged by IED itself if it has this facility otherwise it is
performed at C264 level when receiving the data.
4.4
4.4.1
Acquisition
The DIU200/DIU210/DIU211 (16 DIs) or CCU200, CCU211 (8 DIs + 4 DOs) boards acquire
the binary data.
Digital Input (DI) can have the value 1 or 0. The value 1 shows the presence of an external
voltage. The value 0 shows the absence of the external voltage.
When the external voltage is above or below a threshold, the hardware writes the value 1 or
0. The hardware specification document shows the value of the threshold.
A transition from the value 0 to 1 or from 1 to 0 is usually followed by a succession of
transitions (bounces) before the value stabilises. The software must filter these bounces.
Each change-of-state of a digital input is time-stamped with a resolution better than 1 ms.
C264/EN FT/C80
Functional Description
Page 52/240
Hardware
acquisition
MiCOM C264
Software
acquisition
Time
stamping
Debouncing &
Filtering for BI
Toggle
Filtering for
BI
Debouncing &
Filtering for
DM
Special
treatment
for DM
To measurements
treatment
Debouncing &
Filtering for
counters
Special
treatment
for
counters
To counters
treatment
To BI
treatment
C0126ENa
Filtering time
Debouncing
time
T0
T1
T2
C0127ENb
4.4.3
Toggling
A digital input is said to be toggling if its state has changed more than N times in a given
period of time T1.
A toggling DI returns in the normal state if its state has not changed within another period of
time T2.
N, T1 and T2 are parameters determined at configuration time on a per system basis (same
parameters for all MiCOM computers of a system).
The toggle filtering applies only on DI that will be used as BI (there is no toggle filtering on DI
that will be used for counters or DM).
Functional Description
C264/EN FT/C80
MiCOM C264
4.5
Page 53/240
4.5.1
Tcount
Tcount
Transition validated,
counter is incremented
Low to high transition
C0128ENa
C264/EN FT/C80
Functional Description
Page 54/240
4.5.2
MiCOM C264
Tcount
Tcount
Tdef
TC
CC
Non-complementarity
confirmed, counter is invalid
Detection of non-complementarity
C0129ENa
Functional Description
C264/EN FT/C80
MiCOM C264
4.6
Page 55/240
A Digital Measurement can be associated to a Read Inhibit (RI) signal. The acquisition
process is different depending of the presence of this signal.
4.6.1
Confirmed
DM value
Confirmed
DM value
Tstab
Tstab
C0130ENa
C264/EN FT/C80
Functional Description
Page 56/240
MiCOM C264
TInv
Confirmed
DM value
DM UNDEFINED
Tstab
Tstab
Tstab
Tinh
Tinh
RI
DM value transmitted
DM UNDEFINED
C0132ENa
Functional Description
C264/EN FT/C80
MiCOM C264
4.6.3
Page 57/240
Encoding
The following codes are allowed for DM:
CODE
Range of value
BCD
4 (1 BCD decade)
0 to 9
8 (2 BCD decades)
0 to 99
12 (3 BCD decades)
0 to 999
16 (4 BCD decades)
0 to 9,999
32 (8 BCD decades)
0 to 99,999,999
0 to 9,999,999,999,999,999
Binary
0 to 2n-1
Gray
0 to 2n-1
Decimal
16
(1 bit among 6 for the tens,
1 among 10 for the units)
32
(1 bit among 4 for the thousands,
1 bit among 9 for the hundreds,
1 bit among 9 for the tens,
1 bit among 10 for the units)
64
(1 bit among 9 for the millions,
1 bit among 9 for the hundreds of thousands,
1 bit among 9 for the tens of thousands,
1 bit among 9 for the thousands,
1 bit among 9 for the hundreds,
1 bit among 9 for the tens,
1 bit among 10 for the units)
n
0 to 69
1 among N
0 to 4,999
0 to 9,999,999
0 to n
You can use one supplementary bit for the sign (0 indicates a positive value, 1 indicates a
negative value).
Capability extension for the Tap Position Indication only:
CODE
Number of bits
Range of value
1 among N
2
to 64
0 to 2
to 0 to 64
C264/EN FT/C80
Functional Description
Page 58/240
4.7
MiCOM C264
4.7.1
Input ranges
The different input ranges are:
For voltage inputs (AIU201 only): 10 V, 5 V, 2.5 V, 1.25 V
For current inputs: 0 - 1 mA, 1 mA, 0 - 5 mA, 5 mA, 0 - 10 mA, 10 mA, 4 - 20 mA,
0 - 20 mA, 20 mA
The saturation value depends on the selected range.
4.7.2
Acquisition cycle
The analogue inputs are acquired on a periodical basis (short or long cycle, defined in
configuration).
There can be maximum 48 Wired MV for a C264. and 200 MV/sec receiving flux for a C264.
4.8
CCU200 boards for controls (8 DIs+4 normal open DOs), this board allows double
pole switching controls.
DOU200 boards for alarms (8 normal open DOs + 2 normal open/normal close DOs).
Functional Description
C264/EN FT/C80
MiCOM C264
4.9
Page 59/240
4.9.1
Encoding
The codes that follow are allowed:
CODE
Range of value
BCD
4 ( 1 BCD decade)
0 to 9
8 ( 2 BCD decades)
0 to 99
12 ( 3 BCD decades)
0 to 999
16 ( 4 BCD decades)
0 to 9,999
32 ( 8 BCD decades)
0 to 99,999,999
48 ( 12 BCD decades)
0 to 999,999,999,999
Binary
0 to 2n-1
Gray
0 to 2n-1
Decimal
16
( 1 bit among 6 for the tens,
1 bit among 10 for the units)
0 to 69
32
(1 bit among 4 for the thousands,
1 bit among 9 for the hundreds,
1 bit among 9 for the tens,
1 bit among 10 for the units)
0 to 4,999
48
(1 bit among 2 for the hundreds of thousands,
1 bit among 9 for the tens of thousands,
1 bit among 9 for the thousands,
1 bit among 9 for the hundreds,
1 bit among 9 for the tens,
1 bit among 10 for the units)
0 to 299,999
0 to n
1 among N
You can use a supplementary bit for the sign (0 indicates a positive value, 1 indicates a
negative value).
4.9.2
Read Inhibit
You can use a dedicated binary output to allow or forbid the reading of the value by the
external device.
There is one (or none) Read Inhibit (RI) output per value.
If the RI output is a logical one (external polarity applied), the reading is permitted.
To output a value with a RI output, do the steps that follow:
Wait for N ms
Wait for N ms
C264/EN FT/C80
Functional Description
Page 60/240
MiCOM C264
The 0 to 1 transition on the RI output can be used by the external device as a trigger,
indicating that a new value is available.
4.9.3
Functional Description
C264/EN FT/C80
MiCOM C264
4.10
Page 61/240
Analog Setpoints
Analog setpoints are measurement values sent on the Analog Output board.
These setpoint commands (with analog indication) are received from the Station Control
Point (SCP), Remote Control Point (RCP), or from the local HMI (with LCD).
Analog Setpoints are used to interface auxiliary devices requiring analog inputs (ex:
measurement viewers, Generator)
The Analog output values are secured with an external power supply that allows you to keep
the analog output value in event of C264 shutdown or power off.
A quality indication is available with the additional Read Inhibit output relays (NO) associated
to each analog output.
4.10.1
Output range
The various Analog output range in currents are:
5 mA, 0 - 5 mA
10 mA, 0 - 10 mA
4 - 20 mA, 0 - 20 mA, 20 mA
4.10.2
Output management
Each current output is individually managed in 2 modes:
Maintained mode: in event of computer shut down or power off, the output level is
maintained (and the Read inhibit relay is set). Only the reception of a new setpoint will
lead to an output value modification.
Un-maintained Mode: in event of computer shut down or power off, the output is set
to 0.
The Analog Output is stable 100ms after the order. During the Analog output value
modification, the Read Inhibit relay is reset (Open) and indicates that the analog output
value is not to be used.
Stable
Stable
Analog
Output
100 ms
10ms
RI relay
status
10ms
Set
Reset
C0289ENa
C264/EN FT/C80
Page 62/240
4.10.3
Functional Description
MiCOM C264
The C264 is not operational or powered off (no communication with the CPU board)
Otherwise, the analog output function is valid, the AOU watchdog relay is set.
Functional Description
C264/EN FT/C80
MiCOM C264
5.
Page 63/240
DATA PROCESSING
C264 treatment entries can be Binary Inputs or Analogue Inputs. They are issued from
IO boards
5.1
5.1.1
System Input (SI): information related to the system, to configurable and built-in
automations or to electrical process but without acquisition possibilities
SP, DP and MP are acquired with digital input boards or with IEDs connected with a serial
link.
After the acquisition on the digital input boards, the computer performs toggle filtering. When
an input has an hazardous behaviour, such as more than N state changes during a given
duration, toggle filtering prevents the input to load into the computer or into other devices.
5.1.1.1
Toggling Input
A binary input is said to be toggling if its state has changed more than N times within a given
period of time T.
After the acquisition on digital inputs boards, the computer performs toggle filtering, this
avoids loading the computer itself or other equipment when an input has an hazardous
behaviour
An SP associated with a toggling Binary Input is in the TOGGLING state.
A DP or an MP whose one of the associated DI is toggling ist in the TOGGLING state.
5.1.1.2
Suppression
A binary input can be suppressed by an order issued from an operator. No subsequent
change of state on a suppressed BI can trigger any action: for example, display, alarm,
transmission. The BI takes the SUPPRESSED state. When the operator un-suppresses the
BI, this one takes its actual state.
5.1.1.3
Substitution
A BI can be substituted to a manual set state by an operator (state SUBSTITUTED xxx).
The BI stays in the state determined by the operator until he un-substitutes it. When a BI is
substituted, no changes of state are transmitted, and computations, for instance groupings,
are made with the substituted state. When the BI is un-substituted, the actual state is
transmitted to higher control levels and subsequent changes of state are transmitted again.
5.1.1.4
Forcing
When data is invalid: that is, SELFCHECK FAULTY, TOGGLING, UNDEFINED or
UNKNOWN; it can be manually forced by an operator (state FORCED xxx). This feature is
similar to the substitution but the data is automatically updated when valid data is available
again. A SUPPRESSED or SUBSTITUTED datapoint cannot be forced. The forcing could
also be automatic: in this event, the invalid data is automatically replaced by the state
defined in configuration.
C264/EN FT/C80
Functional Description
Page 64/240
5.1.1.5
MiCOM C264
Transmission
By configuration, a BI could be transmitted on a client-server basis on the station bus using
the two modes:
GOOSE based mode: in this mode, the change of status is transmitted in multicast to
the configured receivers. On IEC61850 network, all types of BI can be transmitted
using GOOSE. Only the BI unfiltered states are transmitted with their time stamping,
the reason for change is not. The GOOSE mode is used to transmit data as soon as
possible after their acquisition and as quickly as possible, for automation purpose.
During a loss of communication, the events detected on the computer are not buffered.
5.1.2
DI/DO
association
Group
processing
From
acquisition
From IED
Toggle
filtering
IED
inputs
Manual
suppression
Persistance
filtering
Substitution
Transmission
Report based
Forcing
System
Inputs
Transmission
GOOSE based
To RCP
To HMI
To Printer
To Archive
To
automation
C0133ENa
Functional Description
C264/EN FT/C80
MiCOM C264
Page 65/240
Goose
RESET
01
SET
10
TOGGLING
11
SELFCHECK FAULTY
11
UNKNOWN
11
SUPPRESSED
11
FORCED RESET
01
FORCED SET
10
SUBSTITUTED RESET
01
SUBSTITUTED SET
10
For automation (interlock, PSL, PLC, and built in functions), GOOSE are used. Each valid
state (01, 10 and 00) is configurable to be seen by automation in False, True or Invalid sate.
5.1.2.1
Persistence filtering
For some SP, a transition must be confirmed on a certain period of time. If the opposite
transition occurs before this delay, both transitions are discarded.
Two time-out values can be associated with each SP:
Both delays are in the range 0 to 120 s by step of 100 ms. A value of 0 means that no filter is
applied.
The time tag is user-selectable:
C264/EN FT/C80
Functional Description
Page 66/240
MiCOM C264
TS
TS
TR
TR
SET
SP before filtering
RESET
SET
SP after filtering, mode 1
RESET
SET
SP after filtering, mode 2
RESET
t0
t1
t2
t3
t4
t5
t6
t7
C0310ENa
5.1.3
Functional Description
C264/EN FT/C80
MiCOM C264
Close
contact
From
acquisition
Open
contact
From
acquisition
From IED
Page 67/240
DI/DO
association
Toggle
filtering
Toggle
filtering
Group
processing
Manual
suppression
Substitution
Persistance
filtering
Motion
filtering
Transmission
Report based
Forcing
IED
inputs
System
Inputs
Transmission
GOOSE based
To RCP
To HMI
To Printer
To Archive
To
automation
C0134ENa
Open Contact
0
DPS State
Below motion delay, the state is valid motion. For
REPORT no transmission of the transitory state.
After Motion filtering, state is invalid JAMMED
OPEN
CLOSE
Preliminary treatments (filtering) for some DPs is applied to filter the MOTION state on a
certain period of time. This avoids the transmission of this (normally) transient state.
This treatment is called motion filtering.
The time tag is user-selectable:
Mode 1: the valid state (OPEN or CLOSE) is stamped with the time of the beginning of
the MOTION state
Mode 2: the valid state (OPEN or CLOSE) is stamped with the time of this valid
transition
C264/EN FT/C80
Functional Description
Page 68/240
5.1.3.1
MiCOM C264
Motion filtering
For some DP, the MOTION state must be filtered during a certain period of time in order to
avoid the transmission of this (normally) transient state.
Two time-out values can be associated with each DP:
Both delays are in the range 0 to 60 s by step of 100 ms. A value of 0 means that no filter is
applied.
The time tag is user-selectable:
Mode 1: the valid state (OPEN or CLOSE) is stamped with the time of the beginning of
the MOTION state
Mode 2: the valid state (OPEN or CLOSE) is stamped with the time of this valid
transition
OPEN
T00
T00
T11
T11
CLOSE
t0
t1
t2
t3 t4
t5
t6
t7
t8
t0 : MOTION00 transition
t1 : MOTION00 state not confirmed, CLOSE state time-stamped t0 if mode 1, t1 if mode 2
(if no persistence filtering applies)
t2 : MOTION00 transition
t3 : MOTION00 state confirmed, state JAMMED time-stamped t2
t4 : OPEN transition, time-stamped t4 whatever was the mode (if no persistence filtering applies)
t5 : MOTION11 transition
t6 : MOTION11 state not confirmed
t7 : MOTION11 transition
t8 : MOTION11 state confirmed, state UNDEFINED time-stamped t8
C0311ENa
Functional Description
C264/EN FT/C80
MiCOM C264
5.1.3.2
Page 69/240
DP persistence filtering
For some DP, a valid state (OPEN or CLOSE) must be confirmed on a certain period of time.
If a transition occurs before this delay, the state is discarded.
Two time-out values can be associated with each DP:
Both delays are in the range 0 to 60 s by step of 100 ms. A value of 0 means that no filter is
applied.
The time tag is user-selectable:
TO
TO
OPEN
TC
TC
CLOSE
t0
t1
t2
t3
t4
t5
t6
t7
t0 : CLOSE transition
t1 : CLOSE state not confirmed
t2 : CLOSE transition
t3 : CLOSE state confirmed (stamped t2 if mode 1, stamped t3 if mode 2)
t4 : OPEN transition
t5 : OPEN state not confirmed
t6 : OPEN transition
t7 : OPEN state confirmed (stamped t6 if mode 1, stamped t7 if mode 2)
C0312ENa
C264/EN FT/C80
Functional Description
Page 70/240
MiCOM C264
5.1.3.3
Goose
JAMMED
11
MOTION
00
OPEN
10
CLOSE
01
UNDEFINED
11
TOGGLING
11
SELFCHECK FAULTY
11
UNKNOWN
11
SUPPRESSED
11
FORCED JAMMED
11
FORCED OPEN
10
FORCED CLOSED
01
SUBSTITUTED JAMMED
11
SUBSTITUTED OPEN
10
SUBSTITUTED CLOSED
01
5.1.3.4
Functional Description
C264/EN FT/C80
MiCOM C264
Page 71/240
The codes for the DPS data on the C264 server, on IEC61850, and on IEC61850 clients
show in the table that follows:
Server
Data on IEC61850
Server
Client
Acquired state
stVal
Resulting state
Resulting state
C264
OI/GTW PC
All bits = 0
MOTION00
N/A
q= 0x0000
(GOOSE only)
JAMMED
JAMMED
OPEN
OPEN
CLOSED
CLOSED
All bits = 0
MOTION11
N/A
q= 0x0000
(GOOSE only)
UNDEFINED
Quality
C264
MOTION00
0x00
(GOOSE only)
JAMMED
0x00
q= 0x4000
OPEN
0x40
All bits = 0
q= 0x0000
CLOSED
0x80
All bits = 0
q= 0x0000
MOTION11
0xC0
(GOOSE only)
UNDEFINED
0xC0
UNDEFINED
q= 0x4000
NA: Not Applicable
5.1.4
contact 1
From
acquisition
Toggle
filtering
contact N
From
acquisition
Toggle
filtering
Manual
suppression
Substitution
MP filtering
Transmission
Report based
Forcing
System
Inputs
C0135ENa
C264/EN FT/C80
Functional Description
Page 72/240
5.1.4.1
MiCOM C264
5.1.4.2
STATE1 to STATE32
UNDEFINED
TOGGLING
SELFCHECK FAULTY
UNKNOWN
SUPPRESSED
State names that will be displayed at the user interface are defined at
configuration time.
NOTE 2:
MP before
filtering
Time-out
undefined
valid
MP after
filtering
undefined
valid
C0313ENa
Functional Description
C264/EN FT/C80
MiCOM C264
5.1.6
Page 73/240
IED inputs
These inputs are acquired from IEDs or protective relays via serial links.
If they are not time tagged by the IED, they are by the computer at the time of reception. This
must be configured for each IED.
An IED input is of SP, DP or MP type.
Double inputs can be processed in IEDs. If they are not, the computer must receive each
individual input and perform the DP processing. This must be configured for each IED.
The processing of an IED input is given in the SP / DP / MP data flow.
5.1.7
Group processing
A group is a logical OR, AND, NOR or NAND combination of Binary Inputs (BIs) or groups.
A group component can be a SP, DP (direct or via IED), SI, Group. A component can belong
to several groups.
A group is processed as a SP. It is time stamped with the date / time of the last data-point
that has modified the group status.
A group is calculated with filtered BIs (persistent filtering or motion filtering if configured).
Other computer BIs coming from reports.
The binary inputs states are taken into account as follows:
Single Point Status
treated in a group as
SET
RESET
SUPPRESSED
treated in a group as
SET
RESET
INVALID
SUPPRESSED
SUPPRESSED
OR
SET
RESET
INVALID
SUPPRESSED
SET
SET
SET
SET
SET
RESET
SET
RESET
INVALID
RESET
INVALID
SET
INVALID
INVALID
INVALID
SUPPRESSED
SET
RESET
INVALID
SUPPRESSED
C264/EN FT/C80
Functional Description
Page 74/240
MiCOM C264
AND
SET
RESET
INVALID
SUPPRESSED
SET
SET
RESET
INVALID
SET
RESET
RESET
RESET
RESET
RESET
INVALID
INVALID
RESET
INVALID
INVALID
SUPPRESSED
SET
RESET
INVALID
SUPPRESSED
NOT
SET
RESET
RESET
SET
INVALID
INVALID
SUPPRESSED
SUPPRESSED
SP and SI from different hierarchical levels can be mixed, for instance a group at substation
computer level can be composed of SP acquired at bay computer level or at substation
computer level.
A group is time stamped with the date / time of the last datapoint that has modified the group
status.
5.1.8
5.1.9
Functional Description
C264/EN FT/C80
MiCOM C264
5.2
Page 75/240
C264/EN FT/C80
Functional Description
Page 76/240
5.2.2
MiCOM C264
5.2.4
in the range [0 .. 3 mA ], the measurement value is set to 0 and the status is set to
OPEN CIRCUIT,
Scaling
The real value represented by the measurement can be computed by a linear or a quadratic
transformation:
Linear, multisegments
Value = Ai*X + Bi with XiX<Xi+1 .
As many as 20 configurable segments [Xi .. Xi+1]
Quadratic
Value = A
Value =
X +B
AX + B
or
Functional Description
C264/EN FT/C80
MiCOM C264
5.2.5
Page 77/240
Zero value
suppression
zero suppression
area
X
- deadband/2
+ deadband/2
C0359ENa
C264/EN FT/C80
Functional Description
Page 78/240
MiCOM C264
5.2.7
For read inhibit: in this event, the DM is acquired when the Read Inhibit bit is set.
To deliver current and voltage data that gives a reliable picture of what happens in the
high voltage part of an electrical substation
To make the galvanic insulation between the high voltage part and the measurement
and protection circuits,
To protect the measurement circuits against damage when a fault comes onto the
high voltage network.
A given electrical network sends voltage (V) and current (I) data to a CT / VT inputs
acquisition function installed on a TMU2XX board.
From the output of the CT / VT inputs acquisitions function, these samples become inputs of
the CT / VT calculation function
The CT / VT calculation function performs basic mathematical processing on the memorised
samples and gives this set of computed measurements, such as power, frequency, and so
on, to the C264 main CPU, the Power PC (PPC).
These measurements are used for the protection function and for the Internal Synchrocheck,
Type 1 and 2
Please refer to:
Functional Description
C264/EN FT/C80
INPUT
INPUT
OUTPUT
Page 79/240
OUTPUT
MiCOM C264
TMU210 Board
CT / VT
Inputs
Acquisition
Function
Conventional
inputs:
Digital
Input / Output
CT / VT
Calculation
Function
TMU210
4 CT / 4 VT
PPC
DSPIO
Daughter
Board
4 CT / 5
20100706-01-RN
Set of computed
measurements
Samples
C0458ENa
5.2.8
Wired Busbar
voltage nb
Protection
Attributes
Busbar
selection
Synchrocheck
(SC)
TMU200
No
External
Type 1
TMU210
Yes
External
Type 2
TMU220
No
Internal
Type 1
C264/EN FT/C80
Functional Description
Page 80/240
MiCOM C264
Rating
Range
57V thru130V
1A or 5A
Rating
Range
57V thru 480V
1A or 5A
Functional Description
C264/EN FT/C80
MiCOM C264
Page 81/240
Rating
Range
NA
57V to 130V
1A or 5A
0.1 to 40 In
Io normal:
1A or 5A
Io normal: Normal
0.1 to 40 Ion
Io normal: Sensitive
0.01 to 8 Ion
0.002 to 1 Ion
CT / VT Functions
These functions use the measurements from the TMU2XX boards:
Protection
Waveform
C264/EN FT/C80
Functional Description
Page 82/240
MiCOM C264
5.2.9
Board
Internal
synchrocheck
Type 1
DSP+TMU200
or DSP200
DSPIO+TMU210
or DSP210
DSP+TMU220
or DSP220
Internal
synchrocheck
Type 2
Protection
Fast
waveform
(Disturbance)
Slow
waveform
X
X
5.2.10
Reference voltage
Samples of Ia
Samples of Va
Samples of Ib
Samples of Vb
Samples of Ic
Samples of Vc
Samples of Io or Ibb1
Functional Description
C264/EN FT/C80
MiCOM C264
Page 83/240
Samples of Ia
Samples of Ib
Samples of Ic
Samples of Io or Ibb1
Samples of Vab
Samples of Vbc
Samples of Vca
Frequency
Phase angles
Total Harmonic Distortion (THD) & Total Demand Distortion (TDD) Harmonics are
evaluated through to the 15th order.
Fundamental measurements
Synchrocheck data: F V
With the synchrocheck option, the values that follow are computed:
Slip frequency
Amplitude
Phase difference
Synchrocheck voltage
C264/EN FT/C80
Functional Description
Page 84/240
MiCOM C264
These measurements are put at the disposal of the PPC at every measurement reading
cycle defined by the configuration.
A configuration option [ meas quality when missing ] allows you to choose 2 different
behaviours when all the Input signals disappear: all below the minimum thresholds, 10V for
voltage and 100mA for current:
5.2.12
Behaviour 1: the measures associated to the acquired signals are set to value 0 and
state VALID
Behaviour 2: the measures associated to the acquired signals are set to value 0 and
state FAULTY
Q: Vars (Using Active Power calculation method with the voltage samples retarded by
90)
The measurements that follow are obtained from the Fourier of sample values or the Fourier
values of the above-derived measurements (DFT ).
Phase angles
Power Factor
SVA
Functional Description
C264/EN FT/C80
MiCOM C264
5.2.13
Page 85/240
Measurements
Star
delta
Accuracy ( TMU220)
Unit
samples
samples
F < 70hz:
Ampere
Ia
Ib
I>In: 0.2% of I
Ic
F>70Hz:
Ir
I< In: 4% of In
Ibusbar1
I>In: 4% of I
Not
available
F<70Hz
10
184
Volts
U<45V: 0.3% of 45
Vb samples
45v<U<200v: 0.2% of U
Vc samples
U>200V: 0.3%of U
Vr computed
F>70Hz
Vbusbar1 samples
U<45V: 4% of 45
Vbusbar2 samples
U>45V: 4% of U
F<70Hz
3
185
Volts
Vab Computed
samples
U<45V: 0.3% of 45
Vbc Computed
samples
45v<U<200v: 0.2% of U
Vca Computed
samples
U>200V: 0.3%of U
Vr Computed
Frequency
id
computed
F>70Hz
Vbusbar1
samples
U<45V: 4% of 45
Vbusbar2
samples
U>45V: 4%of U
computed
185
Hertz
36
Watts
11
Vars
12
VA
13
Power Phase A
Active power ( P ) Samples
computed
Not
available
14
angle computed
Degree
15
Watts
16
Vars
17
VA
18
Power Phase B
Active power ( P ) Samples
Not
available
19
Degree
20
C264/EN FT/C80
Functional Description
Page 86/240
MiCOM C264
Measurements
Star
Unit
id
Watts
21
Vars
22
VA
23
Power Phase C
Active power ( P ) Samples
delta
Not
available
Accuracy ( TMU220)
24
angle computed
Degree
25
Watts
31
Vars
32
VA
33
Power r
Active power ( P ) Samples
Not
available
34
angle computed
Degree
35
Watts
26
Vars
27
VA
28
Power total
computed
computed
Active power ( P )
Cos phi
29
angle
Degree
Not
available
30
volts
175
Inverse
176
Homopolar
177
ratio
178
I Sequence components
Direct
DFT
computed
DFT
computed
Ampere
179
Inverse
180
Homopolar
181
ratio
182
Harmonics for Va
DFT
DFT
Volts
Fundamental
186
15 Harmonic
40->53
distortion ration
Harmonics for Vb
54
DFT
DFT
Volts
Fundamental
187
15 Harmonic
55->68
distortion ratio
Harmonics for Vc
69
DFT
DFT
Volts
Fundamental
188
15 Harmonic
70->83
distortion ratio
84
Functional Description
C264/EN FT/C80
MiCOM C264
Page 87/240
Measurements
Star
delta
DFT
DFT
Accuracy ( TMU220)
Unit
id
Volts
Fundamental
15 Harmonic
85->98
distortion ration
Harmonics for Vbc
99
DFT
DFT
Volts
Fundamental
15 Harmonic
100->113
distortion ratio
Harmonics for Vca
114
DFT
DFT
Volts
Fundamental
15 Harmonic
115->128
distortion ratio
Harmonics for Ia
129
DFT
DFT
Ampere
Fundamental
189
15 Harmonic
130->143
distortion ratio
Harmonics for Ib
144
DFT
DFT
Ampere
Fundamental
190
15 Harmonic
145->158
distortion ratio
Harmonics for Ic
159
DFT
DFT
Ampere
Fundamental
191
15 Harmonic
160->173
distortion ratio
174
Delta F
computed
computed
Hertz
37
Delta phi
computed
computed
Degree
38
Delta V
computed
computed
Volts
39
C264/EN FT/C80
Functional Description
Page 88/240
5.2.14
MiCOM C264
2.
Vbusbar
3.
4.
5.
I1
6.
I2
7.
I3
8.
I4 ( lower priority )
A configuration option (voltage ref change mode) allows choosing 2 different behaviours of
the frequency tracking:
When the signal with the highest priority disappears, the frequency tracking is
performed on the signal with next priority.
When a signal with a higher priority appears, the frequency tracking is performed
on this signal, even if the current reference signal is still present.
When the signal with the highest priority disappears, the frequency tracking is
performed on the signal with next priority.
Even when a signal with a higher priority appears, the frequency tracking remains
on the current reference signal.
In all events, the reference change computation (about 2 seconds), all the measurements
are considered as INVALID (SELFCHECK FAULT).
Fourier Transform
At each period, the DFT (Discrete Fourier Transform) is performed. This gives (among other
things) the value of the phase angle and the magnitude of the fundamental.
RMS values
Vrms =
1 63
Vi
64 i =0
P=
1 63
Vi I i
64 i =0
Functional Description
C264/EN FT/C80
MiCOM C264
Page 89/240
Q=
1 63
Vi I i16
64 i =0
NOTE:
5.2.14.1
Total power
Star Coupling: Total Power
P = Pa+Pb + Pc
Q = Qa + Qb + Qc
Delta Coupling: Total Active Power
P=
1 63
U BC (i ).I B (i ) U CA (i ).I A (i )
64 i =0
P=
1 63
U BC (i).I B (i / 2) U CA (i).I A (i / 2)
64 i =0
NOTE:
Apparent power:
S = P + Q
Power factor:
cos( ) =
Angle:
= tan 1 ( )
P
S
Q
P
Harmonics
Harmonic values are directly issued from the DFT.
Sequence components
The sequence component computation is based on the fundamental values of phase and
magnitude (from the DFT): that is its imaginary part and real part.
Direct component
1
Re(direct ) = (Re( A) + Re( B) cos(120) Im(B) sin(120) + Re(C ) cos(120) + Im(C ) sin(120) )
3
1
Im(direct ) = (Im( A) + Im(B) cos(120) + Re( B) sin(120) + Im(C ) cos(120) Re(C ) sin(120) )
3
Inverse component
1
Re(direct ) = (Re( A) + Re( B ) cos(120) + Im(B) sin(120) + Re(C ) cos(120) Im(C ) sin(120) )
3
1
Im(direct ) = (Im( A) + Im(B) cos(120) Re( B) sin(120) + Im(C ) cos(120) + Re(C ) sin(120) )
3
C264/EN FT/C80
Functional Description
Page 90/240
MiCOM C264
Homopolar component
1
Re(direct ) = (Re( A) + Re( B ) + Re(C ) )
3
1
Im(direct ) = (Im( A) + Im(B ) + Im(C ) )
3
Synchrocheck measurements:
F = | Fline Fbusbar |
V = | Vline Vbusbar |
= | line Vbusbar
5.2.15
5.2.16
I1: samples of IA
I2: samples of IB
I3: samples of IC
I4: samples of Io
V1: samples of UA
V2: samples of UB
V3: samples of UC
Functional Description
C264/EN FT/C80
MiCOM C264
Page 91/240
I1: samples of IA
I2: samples of IB
I3: samples of IC
I4: samples of Io
V1: samples of UA
V2: samples of UB
V3: samples of UC
5.2.17
Frequencies
Thermal status
I2t measurement
Synchrocheck data: F V
With the synchrocheck option, the values that follow are computed:
Slip frequency
Amplitude
Phase difference
Synchrocheck voltage
These measurements are put at the disposal of the computer every measurement reading
cycle defined by the configuration.
5.2.18
C264/EN FT/C80
Page 92/240
Functional Description
MiCOM C264
The primary measurements that follow are derived directly from sample values:
Thermal status
The following measurements are obtained from the Fourier of sample values or from the
Fourier values of the derived measurements (DFT ):
Power Factor
Synchrocheck measurements.
Functional Description
C264/EN FT/C80
MiCOM C264
5.2.19
Page 93/240
Accuracy
Unit
2%
In
id
Rms_Ia
Rms_Ib
Rms_Ic
Rms_Io
10
2%
Volts
Rms_Va_Vab
Rms_Vb_Vbc
Rms_Vc_Vca
Rms_Vo
Rms_Vbusbar
Frequency
0.01Hz
F: frequency tracking
Hertz
Hertz
36
Index of F
323
Index of F81
324
Rate of frequency_81
0.03Hz/sec
Hertz/sec
2%
Ia
In
300
Ib
In
301
Ic
In
302
Io
Ion
303
Io_computed
Ion
313
EPATR Io
ampere
2%
Volts
UA
UB
UC
UAB
304
UBC
305
UCA
306
Uo
307
Ubusbar
183
volts
U_positive
U_negative
In
I_positive
I_negative
Total power
Active phase power ( P )
<3%
Watts
<3%
watts
Vars
26
28
29
C264/EN FT/C80
Functional Description
Page 94/240
MiCOM C264
Measurements
Accuracy
Unit
id
Thermal status
312
IT measurement
Ampere / second
IT phase A
340
IT phase B
341
IT phase C
342
IT total
343
I t measurement
Ampere/second
I2T phase A
344
I2T phase B
345
I2T phase C
346
I2T total
347
Synchrocheck
Delta F
Hertz
37
Delta V
Volts
38
Delta phi
Degree
39
Freq line
Hertz
330
Freq bar
Hertz
331
Phase Angle
Degree
332
Anticipation angle
Degree
333
Shift freq
334
335
Functional Description
C264/EN FT/C80
MiCOM C264
5.2.20
Page 95/240
TMU210: Algorithms
Calibration
3 calibration parameters are stored in EEPROM for each input:
Amplitude
Phase
offset
The offset correction has to be re-evaluate in real time and not in static way.
So the offset correction is made by a low pass filter (0.5Hz ). So the offset parameter stored
in EEPROM is not used.
The amplitude offset is used at each acquisition cycle.
Frequencies:
Frequency tracking
The frequency tracking is made by calculating the frequency of a voltage or current channel.
For each channel a minimum threshold is used to validate the signal (1 volt for VT, 0.1A pour
CT).
If a tracking is done on a channel, there is no change until the value of this channel becomes
lower than the threshold. There is no hysteresis on them. The channel changing respects the
following list:
V1 (first)
V2
V3
I1
I2
I3 (last)
Frequency computation
The first phase voltage channel over minimum threshold (Umin_F_enable) is selected, then
a filter FIR is applied to reject harmonic. On result, we calculate period by cross zero
method, on leading edge and on trailing edge, average result of this both measurement
generated frequency used.
Between 2 computations of the frequency, if the frequency change is more than 20Hz/s
(equals to a brutal step 400mHz at 50Hz), then the frequency calculation will be frozen and
INVALID during 7 cycles (for example, at 50Hz the frequency will be frozen during 120ms)
C264/EN FT/C80
Functional Description
Page 96/240
MiCOM C264
Vrms =
1 31
Vi
32 i =0
3Vpn
3Vpn+Vo
2Vpn+Vo
2Vpp+Vo
3Vpp+Vo
3Vpn+Vb
3Vpp+Vb
Rms_UA
Rms_UA
Rms_UA
Rms_UAB
Rms_UAB
Rms_UA
Rms_UAB
Rms_UB_UBC
Rms_UB
Rms_UB
Rms_UB
Rms_UBC
Rms_UBC
Rms_UB
Rms_UBC
Rms_UC_UCA
Rms_UC
Rms_UC
NOT VALID
NOT VALID
Rms_UCA
Rms_UC
Rms_UCA
Rms_Uo
NOT VALID
Rms_Uo
Rms_Uo
Rms_Uo
Rms_Uo
NOT VALID
NOT VALID
Rms_U_busbar
NOT VALID
NOT VALID
NOT VALID
NOT VALID
NOT VALID
Rms_u_busbar
Rms_u_busbar
Rms_IA
Rms_IA
Rms_IA
Rms_IB
Rms_IC
Rms_IC
Rms_Io
Rms_Io
Rms_UA_UAB
Functional Description
C264/EN FT/C80
MiCOM C264
Page 97/240
Fundamental measurements:
General
The instantaneous direct effective fundamental measurement, to be utilised by the
protections, is supplied every samples reception frame, in terms of both module and phase
as well as that for the real part and the imaginary part of the current vector. This is calculated
using the Fourier transform (DFT), applied to the samples of the last period recorded (32
samples) and expressed in ADC points.
So a multiplier coefficient is necessary to scale them in the appropriated unit.
3Vpn
3Vpn+Vo
2Vpn+Vo
2Vpp+Vo
3Vpp+Vo
3Vpn+Vb
3Vpp+Vb
Mod_IA
Direct
Mod IB
Direct
Mod IC
Direct
Mod Io
Direct
Mod_UA
Direct
Direct
Direct
Derived
Derived
Direct
Not valid
Mod _UB
Direct
Direct
Direct
Derived
Derived
Direct
Not valid
Mod _UC
Direct
Direct
Derived
Derived
Derived
Direct
Not valid
Mod _UAB
Derived
Derived
Derived
Direct
Direct
Derived
Direct
Mod _UBC
Derived
Derived
Derived
Direct
Direct
Derived
Direct
Mod _UCA
Derived
Derived
Derived
Derived
Direct
Derived
Direct
Mod _Uo
Derived
Direct
Direct
Direct
Direct
Derived
Not valid
Mod _U_busbar
Not valid
Not valid
Not valid
Not valid
Not valid
Direct
Direct
Mod_I1
Derived
Mod_I2
Derived
Mod_V1
Derived
Mod_V2
Derived
Ioc
Derived
Conversion
KIADC is the number of ADC points corresponding to the nominal phase current to the
secondary side.
KIoADC is the number of ADC points corresponding to the nominal earth current to the
secondary side.
X is the value of the module expressed in ADC points (X = I, Io, Uxy, Uo)
X is the effective value of the module expressed in voltage or ampere to the primary
side (X = I, Io, Uxy, Uo).
I "=
I
* CT _ In
KI ADC
Io"=
Io
* CT _ Ion
KIo ADC
U xy " =
Uo" =
U xy
KU ADC Un
* VT _ Un
Uo
*VT _ Uon
KUo ADC Uon
C264/EN FT/C80
Functional Description
Page 98/240
MiCOM C264
Direct measurements
The real and the imaginary part are determined using the DFT method.
N
2 * i
Re(G ) = sample * cos
i
N
i =1
N
2 * i
Im(G ) = sample * sin
i
N
i =1
The real part and the imaginary part of every received valid sample are calculated.
Derived measurements
Voltages
3Vpn
3Vpn+Vo
2Vpn+Vo
2Vpp+Vo
3Vpp+Vo
3Vpp+Vb
3Vpn+Vb
V1
V1
V1
Not valid
V1
UB
V2
V2
V2
Not valid
V2
UC
V3
V3
kVo V1-V2
(kVo-V1 + 2V2)/3
(kVo-V3 + V2)
Not valid
V3
UAB
V1-V2
V1-V2
V1-V2
V1
V1
V1
V1-V2
UBC
V2-V3
V2-V3
2V2+V1-kVO
V2
V2
V2
V2-V3
UCA
V3-V1
V3-V1
kVO-2V1-V2
V1-V2
V3
V3
V3-V1
Not valid
k-1 (V1+V2+V3)
UA
-1
UO
k (V1+V2+V3)
Ubusbar
k-1 (V1+V2+V3)
-1
k (V1+V2+V3)
Not valid
Not valid
Not valid
Not valid
The earth to phase adaptation coefficient - (necessary for expressing the earth ADC
points in phase ADC points) amounting to:
k=
Un KU ADC VT _ Uon
I1
IA+(IB-120)+(IC+120)
I2
IA+(IB+120)+(IC-120)
Where the writing <IB/C+/-120> points out that the vector is considered rotated of +/- 120
Functional Description
C264/EN FT/C80
MiCOM C264
Page 99/240
3Vpp+Vo, 2Vpp+Vo,
3Vpp+Vb
U1
(UA+(UB+120)+(IC+240))/
3
(UA+(UB+240)+(IC+120))/3
U2
(UA-(UB-120))/3
(UA-(UB+120))/3
Where the writing <UB/C+/-alfa> points out that the vector is considered rotated of +/- alfa
Computed Homopolar current
In order to use the protective function 67N in several specific conditions, the Homopolar
current must be computed from the values of the 3 phase currents:
Re()
Im()
The earth to phase adaptation coefficient - (necessary for expressing the earth
ADC points in phase ADC points) amounting to:
k=
In KI ADC CT _ Ion
The real and imaginary part of the derived current vectors, expressed in ADC points, will be
given by:
Ioc
r
r
r
r
1
Re( I OC ) = Re( I A ) + Re( I B ) + Re( I C )
k
r
r
r
r
1
Im( I OC ) = Im( I A ) + Im( I B ) + Im( I C )
k
r
r
Re( I A )
Re(U BC )
r
r
= arctg
arctg Im(U )
BC
Im( I A )
r
r
Re(U CA )
Re( I B )
r
r
= arctg
arctg Im(U )
CA
Im( I B )
r
r
Re( I C )
Re(U AB )
r
r
= arctg
arctg Im(U )
AB
Im( I C )
Where:
I^U
is the angle between the generic phase current and the phase-phase quadrature
voltage.
r
I
r
U
Re()
Im()
C264/EN FT/C80
Functional Description
Page 100/240
MiCOM C264
Where:
Po
P" =
3 KI
ADC
P
KU
ADC
P" =
Un
CT _ In VT _ Un
P
3 KI ADC KU ADC Un
Where:
P
Pn
is the nominal three phase power to the secondary side, amounting to: Pn = 3 In Un
Since In and Un are respectively the nominal current and the voltage to the secondary side;
P
is the active three phase power to the secondary side, expressed in Watt;
is the active three phase power to the primary side expressed in Watt;
Q
3 KI ADC KU ADC Un
InTA UnTV
3 KI ADC KU ADC Un
Where:
Q
Qn
is the nominal three phase active power to the secondary side, amounting
to: Qn = 3 In Un
Since In and Un are respectively the nominal current and the voltage to the secondary side;
Q
is the active three phase power to the secondary side, expressed in Qn;
is the active three phase power to the primary side expressed in VAR;
Functional Description
C264/EN FT/C80
MiCOM C264
Page 101/240
Power factor
The power factor is an instantaneous value, used only for visualising purposes. Indicated by:
P
The power factor, or three phase cos, is calculated according to the following algebraic
function:
cos =
P
P + Q2
2
The sign of three phases cos is determined according to the following conventions:
P positive
P negative
Q positive
+L
-C
Q negative
+C
-L
Thermal status
It can be demonstrated that, for dt=0.02s, the thermal status can be estimated according to
the following equation:
2
IMAX dt
dt
(t )
I
(t + dt ) = (t ) +
Where:
IMAX
is the maximum of the three instantaneous values of the three phase RMS
currents.
is the base current of the device to be protected (ratio between the devices
nominal current in other words the current that, at full operation, implies overtemperature by 100% - and the nominal current of the TA).
I = K * Ith
The thermal status must reside in a non-volatile variable (SRAM) to allow its recovery in
event of auxiliary voltage loss.
To avoid the unwanted trip of the thermal protection, on power-on, the thermal status is
reinstated up to a maximum equalling 90% of the greater between the thermal thresholds to
then evolve normally according to the above equation.
The thermal status can be reset ((t) = 0) through a PPC CO.
C264/EN FT/C80
Functional Description
Page 102/240
MiCOM C264
I2T Measurements
There are 8 measurements dividable in 3 sets:
3 IT phase measurements
2 measurements computer by the sum of the IT phase measurements and I2T phase
measurements.
( IT _ PhaseA) N = ( IT _ PhaseA) N 1 +
( IT _ PhaseB) N = ( IT _ PhaseB) N 1 +
T nb1
ia [t j ]
32 j =0
T nb1
ib [t j ]
32 j =0
( IT _ PhaseC ) N = ( IT _ PhaseC ) N 1 +
T nb1
ic [t j ]
32 j =0
where:
These measurements must reside in a non-volatile variable (SRAM) to allow its recovery in
event of auxiliary voltage loss.
I2T phase measurements
3 measurements based on the samples of the current phase
( I 2T _ PhaseA) N = ( I 2T _ PhaseA) N 1 +
T nb 1 2
ia [t j ]
32 j =0
( I 2T _ PhaseB ) N = ( I 2T _ PhaseB) N 1 +
T nb 1 2
ib [t j ]
32 j =0
( I 2T _ PhaseC ) N = ( I 2T _ PhaseC ) N 1 +
T nb 1 2
ic [t j ]
32 j =0
These measurements must reside in a non-volatile variable (SRAM) to allow its recovery in
event of auxiliary voltage loss.
IT and I2T sum measurements
These 2 measurements are computed by the sum of the IT phase measurements and I2T
phase measurements.
Functional Description
C264/EN FT/C80
MiCOM C264
5.2.21
Page 103/240
upper
HYST
t3
t1
t4
t2
HYST
lower
C0313ENa
C264/EN FT/C80
Functional Description
Page 104/240
5.2.22
MiCOM C264
Manual suppression
A measurement can be assigned to the SUPPRESSED state by an order issued from an
operator. No subsequent change of value or state on a "SUPPRESSED" measurement can
trigger any action: for example, display, alarm, transmission. The measurement takes the
SUPPRESSED state. When the operator "un-suppresses" the measurement, this one takes
its actual state.
5.2.23
Substitution
The value of a measurement can be substituted by an operator (state SUBSTITUTED,
value defined by the operator). The measurement stays in this state until he un-substitutes it.
When a measurement is substituted, no change of value nor state is transmitted, and
computations are made with the substituted state. When the measurement is un-substituted,
the actual state and value are transmitted to higher control levels and subsequent changes
of state and value are transmitted again.
5.2.24
5.2.25
Meaning
VALID
SELFCHECK FAULTY
SUBSTITUTED
FORCED
SUPPRESSED
UNKNOWN
SATURATED
UNDEFINED
OPEN CIRCUIT
OVERSHOOT[1..3]
UNDERSHOOT[1..3]
Functional Description
C264/EN FT/C80
MiCOM C264
5.2.26
Page 105/240
Transmission
The measurement value and state are transmitted on a client-server basis on the Ethernet
IEC-61850 network, using two modes:
Report based mode: the measurement is transmitted to the subscribers with its value,
its status, its time stamping and the reason for change.
During a loss of communication between a client and a server, all server measurements are
set to UNKNOWN on the client.
The measurement information transmitted in a report include:
Cyclic change: set if the measurement value has changed, without modification of
the resulting state
Periodic Transmission
Two periods are defined in database, on a per MiCOM computer basis:
Each measurement is associated to one of the two periods. All measurements of one period
are transmitted at the beginning of each cycle.
All measurements values transmitted within one transmission cycle are the latest acquired
values.
5.2.26.2
V is computed either from the last transmitted value (mode 1) or from the full scale value
(mode 2):
V = (p/1000) * |Vt| where p is a value in the range 0 .. 255 and Vt is the last transmitted
value.
or
V = (p/1000) * |Vmax| where p is a value in the range 0 .. 255 and Vmax is the full scale
value.
C264/EN FT/C80
Functional Description
Page 106/240
5.2.26.3
MiCOM C264
5.2.26.4
TMU200
TMU210
TMU220
0.2% In
0.5% In
0.2% In
0.2% Vn
0.5% Vn
0.2% Vn
Frequency
0.01Hz
0.01Hz
0.01Hz
Angle
Time
1 ms
1 ms
1 ms
Up to x harmonic
15th
15th
15th
0.5%
1%
0.5%
Functional Description
C264/EN FT/C80
MiCOM C264
Page 107/240
5.3
5.3.1
5.3.2
Decimal
Gray
BCD
5.3.3
Manual suppression
A TPI can be suppressed by an order issued from an operator. No subsequent change of
value or state on a suppressed TPI can trigger any action: for example, display, alarm,
transmission. The TPI takes the SUPPRESSED state. When the operator unsuppresses
the TPI, this one takes its actual state.
5.3.4
Substitution
The value of a TPI can be substitute by an operator (state SUBSTITUTED, value defined
by the operator). The TPI stays in this state until he unsubstitutes it.
When a TPI is substituted, no changes of value nor state is transmitted, and computations,
for instance groupings, are made with the substituted state. When the TPI is unsubstituted,
the actual state and value are transmitted to higher control levels and subsequent changes
of state and value are transmitted again.
5.3.5
C264/EN FT/C80
Functional Description
Page 108/240
5.3.6
MiCOM C264
Comment
VALID
SELFCHECK FAULTY
SUBSTITUTED
See 4.4
FORCED
SUPPRESSED
5.3.7
UNKNOWN
UNDEFINED
OVERSHOOT[1..3]
UNDERSHOOT[1..3]
Transmission
The TPI are transmitted on a client-server basis on the IEC-61850 network using the report
mechanism.
During a loss of communication between a client and a server, all server TPI are set to
UNKNOWN on the client.
The TPI is transmitted as soon as a value change or a status change is detected. The TPI
information transmitted in a report are:
Change due to control: set if the state or quality change is due to a control
The TPI information transmitted in a GOOSE is the same than in a report, except for the
"reason for change" and the time-stamping.
Functional Description
C264/EN FT/C80
MiCOM C264
5.4
Page 109/240
5.5
Energy counting
The energy counting function aims to calculate exported and imported active energy
(in kWh) and exported and imported reactive energy (in kVarh) from active and reactive
power issued from CT/VT calculation, digital, analogue boards measurements or IEDs
measurements..
Calculation of the energy is done periodically. The period is defined either by an external
pulsed applied on a digital input, or by the internal clock of the computer. The choice of the
origin of the periodic signal is defined during the configuration phase on a per computer
basis.
Whatever is the origin of an integrated measurement, the integration is done after scaling
with a step of one second.
The integration method used is the trapezium one:
E = Ei
( M i + M i 1 ) (ti ti 1 )
Ei = S f *
*
2
3600
With:
E
Ei
Sf
Mi
ti ti-1 =
1 second
For a given measurement, the integration can be done only after receiving two consecutive
valid values with the same sign of the measurement. The integration result (Ei) is added to
the associated export or import counter according to the sign of the measurement.
The integration is stopped as soon as the power measurement becomes invalid or changes
of sign. The integration is restarted as soon as two consecutive valid measurement values
with the same sign are received.
Current values of energy counters are stored in secured memory ( 48h autonomy when
power supply is off). Current values of energy counters can be modified by an operator.
Values of energy counters are transmitted on a client-server basis on the IEC-61850 network
using mechanism through the LN MMTR.
During a loss of communication between a client and a server, all server energy counters are
set to UNKNOWN state on the client.
NOTE:
Do not use the energy counter values for the billing application.
C264/EN FT/C80
Functional Description
Page 110/240
MiCOM C264
5.6
5.6.1
manage the Test Mode in event of C264 redundancy (Test Mode is managed only if
the computer is in active mode, so a computer in standby mode can't be set in Test
Mode)
2.
In event of computer redundancy, the Test Mode activation is performed independently for
each C264 (Main 1 rack and Main 2 rack) from SMT. If the Active C264 is set in Test Mode,
it remains Active. A Standby C264 cannot be set in Test Mode.
If the control is related to a datapoint: that is, feedback datapoint defined in configuration;
this one takes the control value in Test Mode:
Open / Reset order => Open state for DPS, Reset state for SPS
Close / Set order => Close state for DPS, Set state for SPS
To leave the Test mode, the user, through the SMT, changes the C264 mode to Operational.
The C264 automatically goes in Maintenance mode (transient) before going in Operational
mode.
The user of the Test Mode owns all responsibility of controls performed during the Test
Mode, and before leaving the Test Mode, he owns all responsibility to restore the system. In
Test Mode, all controls performed may impact Isagraf programs or PSL automatisms.
5.6.2
NOTE 1:
NOTE 2:
SET as soon as the C264 accepts the control: that is, after the control checks
SET as soon as the C264 accepts the control selection: that is, after the selection
checks
An optional "order running SPS" on a per control type basis shall be available: that is, one for
open order / one for close order
In event of Direct Execute control, this SPS is:
SET as soon as the execute control is received by the C264: that is, before the checks
Functional Description
C264/EN FT/C80
MiCOM C264
Page 111/240
SET as soon as the control selection is received by the C264: that is, before the
checks
In event of direct negative acknowledgement, those SPS may be SET then RESET with the
same time stamping. Those SPS shall be available only for DPC.
5.6.3
The event Control 1 from Operator and Control 2 from Operator is already managed: in
this event, the control 2 is rejected.
Events Control 2 different from Control 1
Control 1
Control 2
Action
Acknowledgement
PSL
Operator
Control 1 cancelled
Operator
PSL
Control 1 cancelled
PSL
PSL
Control 1 cancelled
Operator
Operator
Control 2 ignored
Control 2
Action
Acknowledgement
PSL
Operator
Control 2 ignored
Operator
PSL
Control 2 ignored
PSL
PSL
Control 2 ignored
Operator
Operator
Control 2 ignored
C264/EN FT/C80
Functional Description
Page 112/240
5.6.4
MiCOM C264
The FBD output, an SPS on computer A/B, goes to the SET position
FBD output 1, an SPC wired on DO of A/B and looped to DI for feedback, goes to the
SET position
FBD output 2, an SPC wired on DO of A/B and looped to DI for feedback, goes to the
SET position
When Computer B goes into active mode and Computer A goes into standby mode, these
events occur:
The FBD output 1 (SPC) and the FBD output 2 (SPC) stay in the SET position
The FBD Output (SPS) goes to the RESET position for the Timer time (T-ON is equal
to 20 seconds).
After this time, the FBD Output (SPS) goes to the SET position.
When you use Micom S1 to modify the time of the timer, the FBD Output (SPS) goes to the
RESET position. It stays in the RESET position for the modified time and then goes to the
SET position.
When Computer A goes into the Faulty mode and Computer B goes into the active mode,
the FBD Output (SPS) goes to the RESET position for the duration equal to the Timer time.
Then the FBD Output (SPS) goes to the SET position. The FBD Output 1 (SPC) and FBD
Output 2 (SPC) stay in the SET position.
Functional Description
MiCOM C264
6.
CONTROL SEQUENCES
6.1
Description
C264/EN FT/C80
Page 113/240
A Control Sequence is a basic built-in function on a module (switch, relay, and function). It
receives control order, sending back acknowledgement. After checks, control sequence
sends control (protocol or DO), and check correct execution with feed back from protocol or
from DI.
6.1.1
General
The C264 allows the following functions:
Control of transformers
Control of IEDs
Control of automatisms
Upon reception of one of these requests, the computer behaviour is different according to:
6.1.1.1
Direct Execute mode: usually for ancillary devices a control may be performed
directly without the selection phase.
Select Before Operate once mode (SBO once): usually for circuits breakers and
disconnectors. The device must be selected before allowing the execution. In that
event the device is managed in two phases: selection and execution. Device
unselection is done automatically by the computer.
Select Before Operate many (SBO many): usually for transformers. The device
must be selected before execute one or more controls before reaching the expected
position (low/raise). In that event the device is managed in three phases: selection,
execution and unselection. The execution phase is repeated for every new control. To
end the controls sequence, the initiator of the request must send an unselection
request.
By configuration, each DPC order (close order or open order) and each SPC can activate
simultaneously two DO contacts.
C264/EN FT/C80
Page 114/240
6.1.1.2
Functional Description
MiCOM C264
Types of devices
Every control sequence may be different according to the type of the device to control. The
complexity of the control sequence may be more or less important depending on the device:
6.1.2
Transformers: They are managed in the three modes: Direct Execute, SBO
once and SBO many mode with optional hardware selection of the device in SBO
mode.
Ancillary devices: they are usually managed in Direct Execute mode but can be
managed also in SBO once mode.
Controls via Setpoints: are managed in Direct Execute mode and in SBO once
mode.
selection phase
Hardware
selection
execution phase
Execution
checks
execution phase
Execution
checks
execution phase
Execution
checks
or
or
or
or
Execution via
IED
Execution via
I/O boards
Execution via
IED
Execution via
I/O boards
System
controls
Execution via
IED
Execution via
I/O boards
Hardware
Deselection
MiCOM C264
Selection
checks
Selection
checks
Direct execute
mode
Functional Description
C264/EN FT/C80
Page 115/240
The following figures show the three control modes of the computer:
C0314ENa
Hardware
Selection
or
or
or
Execution via
IED
Execution via
I/O boards
Execution via
IED
Execution via
I/O boards
Execution via
IED
Execution via
I/O boards
Execution via
IED
unselection phase
Hardware
Deselection
unselection phase
(1) An execution phase with two execution requests is given as an example, it may have more or less
Execution
checks
Execution
checks
Execution
checks
Execution
checks
Execution via
I/O boards
Device
unselect
Device
unselect
Page 116/240
selection phase
Selection
checks
selection phase
Device
Selection
checks
C264/EN FT/C80
Functional Description
MiCOM C264
C0315ENa
Functional Description
C264/EN FT/C80
MiCOM C264
6.1.3
Page 117/240
start of
sequence
no
device direct execute
yes
execution already in
progress ?
execution in progress
Perform execution
checks
no
All checks OK
Perform execution
no
Execution OK
yes
End CO in progress
End CO in progress
send negative
acknowledge
send positive
acknowledge
End of
sequence
C0316ENa
C264/EN FT/C80
Page 118/240
6.1.4
6.1.4.1
Functional Description
MiCOM C264
During the selection phase initialised by a selection request of the control, the computer
performs selection checks in order to verify if the device is selectable or not.
If no fail occurs during these checks, the device is selected and positive acknowledgement is
sent. Otherwise the selection request is refused and a negative acknowledgement is sent
giving fails cause. If the selection of the device is accepted, the computer starts a delay and
waits for:
At the end of this delay if the execution or the cancel request is not sent, the device is
automatically unselected and a negative acknowledgement is sent. The selection delay is
defined during the configuration step.
Note that only one selection is allowed at a time for a device. When a device is already
selected any other selection is not taken into account (none acknowledgement is sent)
whichever of the initiator.
The diagram that follows shows the selection phase of a device configured in SBO once
mode.
Functional Description
C264/EN FT/C80
MiCOM C264
Page 119/240
Unselected
device
Selection request
no
Device selectable ?
yes
Device Already
selected
no
Perform Selection
checks
All checks OK
Device selection
no
Device selection OK
send positive
acknowledge
Selection Time-out
launching
Cancel request
Deselect hardware
selection Device
Execution request
Set device
unselected
send negative
acknowledge
Execution
phase
C0317ENa
C264/EN FT/C80
Functional Description
Page 120/240
6.1.4.2
MiCOM C264
yes
Execution in progress
execution in progress
to the device
Perform execution
checks
send negative
acknowledge
no
All checks OK
Operator
Cancel request
Perform execution
no
Execution OK
yes
send negative
acknowledge
send positive
acknowledge
Reset execution in
progress
deselect the device
End of
sequence
C0318ENa
Functional Description
C264/EN FT/C80
MiCOM C264
6.1.5
Page 121/240
6.1.5.1
6.1.5.2
C264/EN FT/C80
Functional Description
Page 122/240
MiCOM C264
Execution phase- device
SBO many selectd
Wait request
Execution request
Unselect request
cancel request
no
Device selected
yes
Execution in progress
execution in progress
to the device
Perform execution
checks
send negative
acknowledge
no
All checks OK
Perform execution
no
Execution OK
yes
send negative
acknowledge
send positive
acknowledge
Reset execution in
progress
Unselection
phase
End of
sequence
C0319ENa
Functional Description
C264/EN FT/C80
MiCOM C264
6.1.5.3
Page 123/240
Unselection phase
hardware selection
Error during
deselection
Not configured
Deselect the device
Send negative
acknowledge
Send positive
acknowledge
Set device
deselected
End of sequence
C0320ENa
Inter-control delay
Computer mode
Device selectable
Uniqueness
In event of fail, the initiator of the request may bypass the checks that follow:
Uniqueness
C264/EN FT/C80
Functional Description
Page 124/240
MiCOM C264
Next diagram schematises controls and bypass according the description of the device.
Unselected device
Inter-control delay
expired
Not configured
yes
yes
Computer faulty or in
maint
no
Substation and bay
mode OK
no
Bypass mode checks
Not configured
yes
no
Interlock checks
OK
no
Bypass interlock
checks
Not configured
yes
yes
Not configured
Automatism running
no
Bypass automatism
no
Device selectable
yes
Device locked
no
Not configured
no
Bypass locked device
no
Not configured
yes
no
Uniqueness
OK
Not configured
no
Bypass uniqueness
check
Abort
selection
phase
yes
Continue
selection
phase
C0321ENa
Functional Description
C264/EN FT/C80
MiCOM C264
6.1.6.1
Page 125/240
Inter-control delay
You can define a user-selectable delay during which a new order to the same device is
forbidden. If this delay is configured and not expired since the last order the request is
refused with negative acknowledgement.
6.1.6.2
Computer mode
Control requests are accepted or not depending on the operating mode of the computer.
6.1.6.3
Changing mode:
From operational mode to test mode: the specific control test mode is
refused if at least one control is in progress.
From test mode to operational mode: the specific control test mode is
refused if at least one control is in progress.
Bay mode is checked by the computer managing the device if the bay mode dependency is
configured for this device.
Substation and SBMC modes are checked by the computer having slave protocols and only for
controls coming from SCADA and if substation mode dependency is configured for this device.
If the request is refused the selection sequence is aborted with negative acknowledgement.
6.1.6.4
Interlock control
The configuration process allows to assign or not a logical equation to each order (close and
open) of the device. If configured by the user, its state (true/false) may affect the control
sequence. If is false, the selection is refused, excepted if bypass is set.
In event of fail the sequence is aborted with a negative acknowledgement.
6.1.6.5
6.1.6.6
Device selectable
A device is selectable if during configuration step its control is described to be managed in
SBO once or SBO many mode and is not already selected. Otherwise the selection
request is refused with negative acknowledgement.
C264/EN FT/C80
Functional Description
Page 126/240
6.1.6.7
MiCOM C264
6.1.6.8
6.1.6.9
The request is accepted only if the device is in the opposite state and valid
The request is accepted only if the device is in the opposite state, jammed or
undefined
The request is refused only if the device is in the same state and valid. In any event, if
the request is refused, a negative acknowledgement is sent back
Uniqueness
It is possible by configuration to prevent to have more than one control at a time.
Inside a bay
D
B
Uniqueness check is OK
Uniqueness check is OK
Uniqueness check is NOK
C0322ENa
Functional Description
MiCOM C264
C264/EN FT/C80
Page 127/240
If a device is under control and another control is sent on this device, the second one is
ignored.
In event of uniqueness of the command at least to one of these levels the selection is
refused, with negative acknowledgement. The user may bypass this control during selection
request.
6.1.7
Selection behaviour
In SBO once mode and SBO many mode, the configuration process allows to describe
optionally, a device selection to control the device.
The following configurations must be considered:
Configuration 1: device with a control for selection and its associated selection
position information.
Whatever the request control (select open/select close, select raise/select low) the selection
of the device is performed as follows:
Configuration 1:
The computer
1. verifies the selection position information, it must be open: if it is close, it is an
abnormal situation, the selection sequence is stopped with a negative
acknowledgement.
2. sends a close order of the selection control (via I/O boards or IED) and waits the
selection position information in a given delay (by configuration).
If the selection control has been normally executed, and the selection position
information of the device become set in the given delay, the selection sequence
ends sending a positive acknowledgement. The computer starts its execution
sequence. In event of fail of the execution of the selection control or if the selection
position information remains open in the given delay the selection sequence ends
abnormally sending a negative acknowledgement.
Configuration 2:
For this configuration, in which only the output control of the selection is configured,
the computer: sends a close order of the selection control (via I/O boards or IED). If
the selection control has been normally executed, the selection sequence ends by
sending a positive acknowledgement and the computer start its execution sequence.
In event of fail of the execution of the selection control, the sequence ends abnormally
by sending a negative acknowledgement.
C264/EN FT/C80
Page 128/240
6.1.8
Functional Description
MiCOM C264
Inter-control delay
Computer mode
Uniqueness
Execution checks and bypasses are identical to those of the selection phase. Moreover, in
event of SBO once mode or SBO many mode the computer verifies that the device was
previously selected.
The checks of the execution phase in SBO many mode are identical as above but they
are repeated for every execution request (low/raise).
In Direct Execute mode the device selection is not verified because it is not allowed.
6.1.9
Execution behaviour
On this stage the control request is executed via:
I/O boards
IED communication
The execution via I/O boards is performed only if the computer is in operational mode. If
the computer is in test mode, the output relay is not set. In this event the computer
simulates a positive acknowledgement of hardware execution. It allows to perform control
sequence safety in order to test Automatisms configuration, control sequence configuration
etc. Controls to IEDs are sent if the computer is in operational mode or test mode.
6.1.9.1
Digital Setpoints
Analogue Setpoints
Transient: the contact is closed and then re-opened automatically after a delay
(defined during the configuration of the xPC). For a DPC, configuration gives two
delays need to be configured, one for open and one for close.
Functional Description
C264/EN FT/C80
MiCOM C264
Page 129/240
Permanent: For this type of output control, the contact is held in the requested
position state until the a reverse order is received.
Permanent until feedback: The contact is held in the requested position state until
confirmation of the position of the device or after timeout awaiting the new position of
the device. In this event, the input information of the device status must be configured.
6.1.9.3
6.1.10
6.1.10.1
Device features: selection control wired/not wired, selection position wired/not wired,
device position wired/not wired and so on
DPC open
(resp. close)
DPS
Feedback Delay
CO Pulse Delay
0-60s
0-5s
3
1 execution request
C0323ENa
C264/EN FT/C80
Functional Description
Page 130/240
MiCOM C264
The chronogram that follows shows an abnormal termination of Direct Execute sequence.
The device hasnt taken the expected position in the given delay.
DPC open
(resp. close)
SPS close
(resp. open)
SPS open
(resp. close)
Feedback Delay
CO Pulse Delay
0-60s
0-5s
3
1 execution request
C0324ENa
Selection position
input
Device status
Selection
Feedback
Delay
Selection
Feedback
Delay
Open/Close
Feedback
Delay
Selection time-out
0-60s
0-1 s
1
0-1 s
1-10mn
2
3
Selection phase
Execution phase
C0325ENa
Stage 2: the selection is confirmed by the associated input information in the feedback
delay (0 1-sec user selectable)
Stage 3: close the device before the end of the selection timeout delay (0 10 MN
user selectable)
Stage 4: the device has taken the expected position (close) in the feedback delay (0
60 sec user selectable). The computer deselect the device (open selection output
control)
Stage 5: confirmation of the deselecting of the device in the same given delay than
stage 2.
Functional Description
C264/EN FT/C80
MiCOM C264
Page 131/240
The chronogram that follows shows controls sequence that is aborted after time-out of the
selection delay.
Stage 2: the selection is confirmed by the associated input information in the feedback
delay.
Device Configuration B: the optional selection control is configured and Selection position
information is not configured
The chronogram that follows shows a normal termination of the control sequence.
Selection of the
device
Output Control Of
The Device
Device status
Open/Close
Feedback
Delay
Selection time-out
0-60s
1-10mn
1
Execution phase
Selection phase
C0327ENa
6.1.10.3
Stage 2: close the device before the end of the selection timeout delay (0 10 MN
user selectable)
Stage 3: The device has taken the expected position (close) in the feedback delay (0
1-sec user selectable). The computer deselect the device (open selection output
control)
C264/EN FT/C80
Functional Description
Page 132/240
6.1.11
MiCOM C264
xPS State
xPC state
Action
YES
SET xPS
Open
YES
RESET xPS
Close
NO
SET xPS
Open
NO
RESET xPS
Close
The control is launched when the xPS becomes SET, after all xPS filtering (all others states
are ignored).
The state of xPS is SET only after the time delay is obeyed when delay values of
Debouncing, filtering, toggling and toggling end of the C264 is set to its maximum,
minimum and an intermediate value possible within the specified range
Functional Description
C264/EN FT/C80
MiCOM C264
Page 133/240
The xPC Control launched by bay xPS changes control originator field orCat to Bay
Level and orIdent to xPS label
NOTE 1:
Usage of order labels in profile for SPC in SCE, "order on" and "order
off" should be "Yes".
NOTE 2:
Priority 1
Priority 2
Control authorized ->
Local
n/a
LCD
Remote
Local
xPS
Control is authorised by computer LCD and not by SPS when Bay L/R is priority 1 and
operates in local mode; and Synoptic L/R is priority 2 with operating mode not taken into
account by C264.
Control is authorised by xPS and not by computer LCD when Bay L/R is priority 1 and
operates in Remote mode; and Synoptic L/R is priority 2 and operating in Local Mode.
L/R bay
L/R synoptic
Priority 2
Priority 1
Control authorized ->
n/a
Local
xPS
Local
Remote
LCD
Control is authorised by xPS and not by computer LCD when Bay L/R is priority 2 with
operating mode not taken into account by C264 and Synoptic L/R is priority 1and operating
in Local Mode.
Control is authorised by computer LCD and not by xPS when Bay L/R is priority 2 and
operates in local mode; and Synoptic L/R is priority 1 operating in Remote Mode.
C264/EN FT/C80
Functional Description
Page 134/240
MiCOM C264
ISaGRAF
Status
Status
DINT
Quality
Quality
DINT
GlobalAlarmStatus
Alarm
SINT
MOTION 00 = 3
Functional Description
MiCOM C264
Quality attribute
VALID = 0
SELFCHECK FAULTY = 1
UNKNOWN = 2
FORCED = 4
SUPPRESSED = 8
SUBSTITUTED = 16
TOGGLING = 32
C264/EN FT/C80
Page 135/240
C264/EN FT/C80
Functional Description
Page 136/240
MiCOM C264
6.2
6.2.1
DEVICE
CONTROL
OUTPUTS CB OUTPUTS
TYPE A
TYPE B (4)
INPUTS
ALL TYPES
DPC
SPC control
control for for open of
open/close device
of device
SPC control
for close of
device
SPS/ DPS
physical position
of phase A
DPS physical
position of the
device(1 phase)
SPS (optional)
phase not
together
information
SPS/ DPS
physical position
of phase B
SPS/ DPS
physical position
of phase C
system SPS
phase not
together
information (2)
system DPS:
the feedback of
the control (3)
DEVICE
SPC /DPC
SELECTION (optional)
control of
device
selection
6.2.2
SPC /DPC
(optional)
control of
device
selection
SPS /DPS
(optional) device
selection
position
information
SPC /DPC
(optional)
control of
device
selection
SPC /DPC
(optional) control
of device
selection
SPS /DPS
(optional) device
selection
position
information
1.
The computed double signal is equal to the physical status if the phase not together
status is equal to false else the computed signal is equal to jammed.
2.
The computed phases not together is equal to false if all phases are in the same
position else it is equal to true.
3.
The computed signal is equal to the phase A status if the phase not together status is
equal to false else the computed signal is equal to jammed.
4.
For open the device they send the DPC close with open request
For close the device they send the DPC close with close request
Functional Description
C264/EN FT/C80
MiCOM C264
6.3
Page 137/240
6.3.1
DEVICE
CONTROL
ONE PHASED CB
OUTPUTS
(6) TYPE A
OUTPUTS
TYPE B
INPUTS ALL
TYPES
DPC control
for
open/close
of device
SPC/DPC
control for
open phase
A
SPS/DPS
physical
position of
phase A
SPC/DPC
SPC/DPC
control for
control for
open phase
close with
synchrocheck B
(5)
SPC/DPC
control for
open phase
C
SPS/DPS
physical
position of
phase B
SPS/DPS
physical
position of the
device (1
phase)
SPS (optional)
phase not
together
information
system DPS
optional): the
feedback of
the control (1)
SPC/DPC
control for
close of
device
SPS/DPS
physical
position of
phase C
system
SPS/DPS
phase not
together
information (2)
SPC control
for close with system DPS:
synchrocheck the feedback
of the control
(3)
DEVICE
SELECTION
SPC
(optional)
control of
device
selection
SYNCHROCHEC SPC/DPC
K SET ON/SET
(optional)
OFF (4)
control of
ON/OFF
synchrocheck
SPC (optional)
control of
device
selection
SPS (optional)
device
selection
position
information
SPC
(optional)
control of
device
selection
SPC
(optional)
control of
device
selection
SPS (optional)
device
selection
position
information
SPC/DPC
(optional)
control of
ON/OFF
synchrocheck
SPS/DPS
(optional)
ON/OFF
synchrocheck
information
SPC/DPC
(optional)
control of
ON/OFF
synchrocheck
SPC/DPC
(optional)
control of
ON/OFF
synchrocheck
SPS/DPS
/DPS(optional)
ON/OFF
synchrocheck
information
1.
The computed double signal is equal to the physical status if the phase not together
status is equal to false else the computed signal is equal to jammed.
2.
The computed phases not together is equal to false if all phases are in the same
position else it is equal to true.
3.
The computed signal is equal to the phase A status if the phase not together status is
equal to false else the computed signal is equal to jammed.
4.
Wired SPC and SPS for external synchrocheck and system SPC and SPS for internal
synchrocheck. If is not configured the external synchrocheck module or the
synchrocheck automatism is considered always set on. DPC and DPS are used only
for manual synchrocheck.
C264/EN FT/C80
Functional Description
Page 138/240
MiCOM C264
Furthermore, waiting closes the CB by the external module the initiator of the request may:
6.3.2
6.3.2.1
(1)
(2)
(3)
OI
CIRCUIT
BREAKER
Synchro
Check
Module
or
GATE
WAY
SPC/DPC
MES/MHS
synchrocheck
DPC open/Close
device
select close
Execute close
force close
C0328ENa
2.
3.
4.
5.
Functional Description
C264/EN FT/C80
MiCOM C264
Page 139/240
In event of fail of one of these operations, the controls sequence is stopped with a negative
acknowledgement
Execution phase:
6.
7.
8.
9.
The chronogram that follows shows a successful control sequence close with
synchrocheck.
SPC ON/OFFt Sync
SPC select
SPS select
DPC open/close
device
DPS open
close
Feedback
Delay
Feedback
Delay
0-1 s
1
0-5 s
0-10mn
0-60mn
3
2
1
Feedback for DO
sync close
Selection timeOut
selection request
4
5
execution request
End of control
C0329ENa
SPC select
SPS select
DPC open/close
device
DPS open
close
Feedback
Delay
0-1 s
1
1 selection request
Feedback
Delay
Selection timeOut
0-5 s
0-10mn
Feedback for DO
sync close
0-60mn
3
3 execution request
4
5
End of control
C0330ENa
C264/EN FT/C80
Functional Description
Page 140/240
6.3.2.2
MiCOM C264
An SBO once sequence to close the CB by the synchrocheck module and put out of
service the synchrocheck module
Three sequences:
A direct execute sequence to put out service the external synchrocheck module
The scheme that follows shows a close control request where an operator at the OI or
gateway manually manages the external synchrocheck module.
DPC open/close
device
SPC/DPC ON/OFF
synchrocheck
(2)
(3)
(4)
Synchro
Check
Module
(1)
OI
or
GATE
WAY
SPC/DPC SET
ON synchrocheck
(5)
SPC/DPC Close
with synchrocheck
SPC/DPC SET
OFFsynchrocheck
(optional)
DPC open/Close
device
Direct execute
select close
Execute close
force close
C0331ENa
2.
Verify that the synchrocheck module is set (if on/off synchrocheck input information is
configured)
In event of fail of one of these operations, the sequence ends with a negative
acknowledgement
Second sequence (SBO ONCE): Close the device with synchrocheck:
Selection phase:
1.
2.
3.
4.
In event of fail of one of these operations the controls sequence is stopped with
a negative acknowledgement
Functional Description
C264/EN FT/C80
MiCOM C264
Page 141/240
Execution phase:
5.
6.
7.
8.
Third sequence (DIRECT EXECUTE): set off the external synchrocheck module
This sequence takes place only if the setting off of the synchrocheck module is configured
manual
1.
2.
Verify that the synchrocheck module is set on (if on/off synchrocheck input information
is configured)
The chronogram that follows shows a successful control sequence close with
synchrocheck performed in three sequences. In event of automatic setting off of the
synchrocheck module the chronogram remain identical. It is performed at the end of the SBO
sequence.
SPC ON/OFF Sync
SPC select
device
DPC open/close
device
DPS open
close
Feedback
Delay
Feedback
Delay
0-1 s
1
1
0-5 s
0-10mn
0-60mn
4
2
DE request set on
synchrocheck
Feedback for DO
sync close
Selection timeOut
selection request :
close the device
5
execution request
6
DE request set
off synchrocheck
End of control
C0332ENa
During SBO sequence after step 5 the initiator of the request may
force the closing of the device.
C264/EN FT/C80
Functional Description
Page 142/240
6.3.2.3
MiCOM C264
SPS select
(optional)
Forcing on DPC
close : DPC close
is set
SPS open
close
Feedback Delay
Feedback
Delay
0-1 s
1
0-5 s
Selection Timeout
0-10mn
Feedback
Delay
0-20s
0-60mn
3
2
3
1 selection request
execution request
4 synchrocheck bypass
5 End of control
6
C0333ENa
6.3.2.4
SPC select
SPS select
DPS open
close
Feedback
Delay
Feedback
Delay
0-1 s
1
1 selection request
0-5 s
2
FeedBack Delay
Selection timeOut
0-10mn
3
3 execution request
0-60mn
4
4
Operator CANCEL
End of control
C0334ENa
Functional Description
C264/EN FT/C80
MiCOM C264
6.3.3
Page 143/240
6.3.3.1
(1)
(2)
(3)
CIRCUIT
BREAKER
Fonction
Synchro
Check
OI
or
GATE
WAY
DPC open/Close
device
select close
Execute close
force close
C0335ENa
Selection phase:
1.
2.
Verify selection device input information associated to the output (if is configured)
3.
In event of fail of one of these operations, the device is deselected and the controls
sequence is aborted with a negative acknowledgement.
Execution phase:
4.
Active the associated internal synchrocheck automatism for authorisation to close the
device
5.
C264/EN FT/C80
Functional Description
Page 144/240
MiCOM C264
The chronogram that follows shows a successful control sequence close with internal
synchrocheck.
SPC select
SPS select
Close/open
Device control
DPS open
close
Feedback
Delay
0-1 s
1
Feedback
Delay
Selection time-out
0-5 s
0-10mn
feedback Delay
0-60mn
3
3 execution request
4
5
End of control
C0336ENa
Functional Description
C264/EN FT/C80
MiCOM C264
Page 145/240
The chronogram that follows shows an abnormal termination of control sequence close with
internal synchrocheck.
SPC select
SPS select
Close/open
Device contro
DPS open
close
Feedback
Delay
Feedback
Delay
0-1 s
1
0-5 s
FeedBack Delay
Selection timeOut
0-10mn
0-60mn
3
6.3.3.2
4
execution request
End of control
C0337ENa
SPC open/close
device
CIRCUIT
BREAKER
(2)
(3)
(4)
Synchro
Check
Module
SPC/ DPC set on
synchrocheck
OI
or
(1)
GATE
WAY
(5)
SPC/DPC set off
synchrocheck
DPC open/Close
device
Direct execute
select close
Execute close
force close
C264/EN FT/C80
Functional Description
Page 146/240
MiCOM C264
2.
2.
3.
4.
In event of fail of one of these operations the controls sequence is stopped with
a negative acknowledgement
Execution phase:
1.
The initiator of the request may force the closing of the device.
2.
3.
4.
Third sequence (DIRECT EXECUTE): set off the internal synchrocheck automatism
This sequence occurs only if the setting off of the synchrocheck automatism is
configured manual
6.3.3.3
1.
2.
Functional Description
C264/EN FT/C80
MiCOM C264
Page 147/240
SPC select
SPS select
Close via output
control
DPS open
close
Feedback
Delay
Feedback
Delay
0-1 s
0-5 s
FeedBack Delay
Selection timeOut
0-10mn
0-60mn
3
1 selection request
6
6
3 execution request
End of control
C0339ENa
6.4
Control of disconnectors
6.4.1
Disconnectors features
C264 computers manage all types of disconnecting switches such as:
Disconnectors
Earthing switch
6.4.2
DEVICE
CONTROL
DPC control for open/close of device DPS physical position of the device
DEVICE
SELECTION
C264/EN FT/C80
Functional Description
Page 148/240
MiCOM C264
6.5
Control of transformers
6.5.1
Transformer features
OUTPUTS
INPUTS
TRANFORMER
CONTROL
DPC: raise/lower
TPI value
TRANSFORMER
SELECTION
TRANFORMER
TYPE NOTE 1
A raise control is refused if the current tap position value corresponds to the
maximum position of the tap.
A lower control is refused if the current tap position value corresponds to the
minimum position of the tap.
TCIP feature: The TCIP input information (tap change in progress), is used to confirm the
right execution of the low/raise execution. Two delays are given by the configuration for the
TCIP management:
TCIP apparition delay: The TCIP information must appear before the time-out of this
delay.
TCIP disappearance delay: The TCIP information must disappear before the time-out
of this delay.
TPI feature: Because the TCIP input information is not always configured, the tap control is
performed using only the Tap Position Indication (TPI) value to verify the right execution of
the request. The TPI value must change in the given delay.
The following examples are given in SBO many mode that is the more complex. The main
difference with the SBO once mode remains to the possibility to execute many raise or
Functional Description
C264/EN FT/C80
MiCOM C264
Page 149/240
low controls before ending the sequence. Moreover, the device is not deselected
automatically but only after an unselect order sent by the initiator of the control request.
6.5.2.1
2.
3.
In event of fail of one of these operations, the device is deselected, the controls
sequence is aborted with a negative acknowledgement.
Execution phase:
4.
In agreement with the request raise or lower and the type of device, execute
the associate control
5.
Wait for the TCIP data and TIP value to confirm execution. Two events:
6.
Wait for the new execution request or unselection request to deselect the device
The chronogram that follows shows a successful sequence with device selection, two raise
controls and device unselection
SPC select
(optional)
SPS select
(optional)
DPC raise/lower
OPEN
TPI Value
(1)
raise/lower
CLOSE
SPS TCIP
FeedbackSelection
Delay timeOut
TCIP
disappearance
time Delay
Pulse
Delay
0-5 s
0-10mn
0-1 s
FeedBack
Delay
TCIP apparition
time Delay
0-1 s
0-1 s
11 End of control
0-5 s
4
6
6 second execution
request
10
11
10 unselect request
C0340ENa
NOTE (1) The TPI value must take the expected value at least at the end of TCIP
disappearance.
C264/EN FT/C80
Functional Description
Page 150/240
MiCOM C264
The chronogram that follows shows an abnormal termination of tap changer control
sequence due to absence TCIP confirmation. In this event the device is automatically
deselected and the sequence ends with a negative acknowledgement
SPC select
(optional)
SPS select
(optional)
OPEN
raise/lower
CLOSE
SPS TCIP
TIP value
Feedback
Delay
Selection
timeOut
0-1 s
0-10mn
0-5 s
1
FeedBack
Delay
Pulse
Delay
4
0-1 s
5
6
6
End of control
0-5 s
3 execution request
6.5.2.2
C0340ENa
Close the device selection output to select the device (if configured)
2.
Verify selection device input information associated to the output (if configured)
3.
In event of fail of one of these operations, the device is deselected, the controls
sequence is aborted with a negative acknowledgement.
Execution phase:
4.
In agreement with the request raise or lower and the type of device, execute
the related control
5.
Wait for the TPI data and compare with the previous value. The difference must
confirm the low or raise execution. Two events:
Event 1: The TPI value confirms in the given delay the execution request: The
computer sends a positive acknowledgement and waits a new request
(execution or unselection) from the initiator.
Event 2: Timeout awaiting the TPI value or unexpected TPI value: The device is
deselected (if it was previously selected), and the sequence is aborted with a
negative acknowledgement.
6.
Wait for the new execution request or unselection request to deselect the device
In event of new request the computer repeat the steps 4 and 5.
In event of unselection request the computer deselects the device (if it was
previously selected), and ends the sequence with a positive acknowledgement.
Functional Description
C264/EN FT/C80
MiCOM C264
Page 151/240
The chronogram that follows shows a successful sequence with device selection, a raise
control and device unselection
SPC select
(optional)
SPS select
(optional)
DPC raise/lower
OPEN
raise/lower
CLOSE
TPI
Feedback
Delay
Selection
time-out
0-5 s
0-10mn
0-1 s
1
feedback
Delay
Pulse
Delay
4
0-1 s
End of control
6 Unselect request
0-5 s
3 execution request
C0342ENa
The chronogram that follows shows an abnormal termination due to the absence of change
of the TPI value in the given delay. The device is automatically deselected, and the
sequence is aborted with negative acknowledgement.
SPC select
(optional)
SPS select
(optional)
DPC raise/lower
OPEN
raise/lower
CLOSE
TPI
Feedback
Delay
Selection
timeOut
0-1 s
0-10mn
0-5 s
1
FeedBack
Delay
Pulse
Delay
4
0-1 s
0-5 s
3 execution request
6.5.2.3
End of control
5
C0343ENa
6.6
C264/EN FT/C80
Functional Description
Page 152/240
6.7
6.7.1
Control to IEDs
MiCOM C264
Control requests to manage device via IEDs may be performed in the three modes (DE,
SBO once, SBO many).
6.7.1.1
The computer sends the control (open/close, low/raise, setpoint) via the
communication protocol to IED.
2.
Expects IEDs control acknowledgement in the given delay (If is supported by the
protocol).
3.
Expects the reception of the feedback of the request (device position SPS, DPS, TPI)
in the given delay (if is configured).
2.
3.
4.
The computer sends the control, such as the open/close, low/raise, setpoint; thru the
communication protocol to the IED.
2.
The computer expects the IED, if supported by the protocol, to send the control
acknowledgement within the given delay.
3.
The computer expects the reception of the feedback of the request, such as the
device position SPS, DPS, TPI; within the given delay, if it is configured.
6.7.2
IED controls
6.7.3
Functional Description
MiCOM C264
6.8
C264/EN FT/C80
Page 153/240
System controls
System control is used to activate or deactivate automatic functions, change computers
mode, bay mode, database management, etc.
A system output control remains internal on the computer (has no digital or IED output) and
may generate a system input information. They are managed in Direct Execute mode
only. A hardware selection has no meaning.
For some uses, such as automatisms activation/deactivation, it is necessary to generate a
system input, that gives the state of the controlled function: for example, ATCC ON/OFF.
This system input may be able to be used by the control sequence or enter to an interlocking
equation etc. The configuration process allows the user to assign or not a system input, that
may include an SPS or DPS. System inputs generated by system outputs are stored in nonvolatile memory. In event of the computers initialisation, they are restored.
6.9
6.10
IED connected,
SBMC mode,
Module conditions
Inter-control delay,
Lock condition,
Execution conditions
6.10.1
Delays upon selection feed back, start moving, final position reached.
Mode Management
Control sequences are only performed if the computer mode is in operational mode. In test
mode, control sequences are allowed but digital outputs are not set.
6.10.2
IED connected
If a control has to be sent to an IED, it is only accepted if this IED is connected to the
computer.
C264/EN FT/C80
Functional Description
Page 154/240
6.10.3
MiCOM C264
Control mode
This control sequence receives requests from the various control points:
To avoid conflict between the control points, substation and bay modes are checked. Each
control sequence can be subject or not to these checks. The switches Remote/Local can be
hardware or software (saved in non-volatile memory).
The SBMC Site Based Maintenance Control allows controlling one specific bay from Local
Display or Operator interface even if substation is in remote. This feature is dedicated to
commissioning or maintenance and has also the possibility to filter data transmitted from the
bay to SCADA.
6.10.4
Uniqueness of control
It is possible by configuration to prevent having more than one control at a time:
Inside a bay
If a device is under control and another control is sent on this device, the second one is
ignored.
In event of uniqueness of the command at least to one of these levels the selection is
refused, with negative acknowledgement. The user may bypass this control during selection
request.
6.10.5
Inter-control delay
It is possible by configuration to define an inter-control delay that is a minimum delay
between two consecutive controls on the same device.
6.10.6
6.10.7
Lock device
Controls are not allowed on a lock device.
6.10.8
Running Automation
If there is a related automation in operation, controls are not allowed on a device.
For example controls issued from PACiS OI or gateway are not allowed on a transformer
controlled by voltage regulation.
6.10.9
Interlocking
The operation of a switching device, such as circuit breakers; traditional disconnecting
switches; disconnecting switches with abrupt rupture; and ground disconnecting switches; is
directly related to the nature of the switch and to its environment.
To operate these devices you must respect some conditions. These conditions, called
interlocking, are managed by logical equations within the C264.
Interlocking prohibits a control sequence that may violate the device operating condition: for
example, break capability, isolation, and so on; or plant operating condition.
Functional Description
MiCOM C264
6.11
HV Control Sequences
6.11.1
Circuit breaker
C264/EN FT/C80
Page 155/240
For three phase breaker each phase DPS is provided separately and it is managed globally
by single (grouped) control and global DPS position. Pole Discrepancy management is
available.
6.11.2
Disconnector
The control sequence of disconnectors is identical to single non-synchronised circuit
breakers.
6.11.3
Transformer
Transformer position is determined using TPI (Tap Position Indication). TPI can be a Digital
Measurement or Analogue Measurement (from DC Analogue Input).
The transformer is the only device that supports the SBO Many control sequences. It is
linked to voltage regulation, also its Raise and Lower controls are defined for secondary
voltage (and not tap position). Except for auto wounded transformer, raise/lower voltage is
also a raise/lower tap.
C264/EN FT/C80
Functional Description
Page 156/240
7.
MiCOM C264
AUTOMATIONS
C264 provides three different ways to perform automation functions:
The choice between these three solutions depends on time and complexity.
7.1
Auto-Recloser
xPS/xPC Association
Pole Discrepancy
Synchrocheck
7.1.1
Auto-Recloser (AR)
7.1.1.1
Introduction
80-90% of faults on the electrical network are transient, such as lightning or insulator
flashover. When a fault occurs, the Circuit Breaker is tripped in order to protect the system.
The Auto-Recloser function is then used to close the circuit breaker after a set time, a time
that is long enough to allow the fault to clear. This duration is called cycle delay and is
defined in the database during the configuration phase.
But, as permanent fault can occur, an auto-recloser scheme has to be provided in order to
allow the elimination of a transient fault by an open/close sequence (auto-reclosing cycle)
and the elimination of permanent fault by, after a defined number of auto-reclosing cycle (4
cycles maximum), leaving the circuit breaker in the open state by closing the trip relay.
A transient fault, such as a lightning strike, is one that is cleared by immediate tripping of one
or more CBs to isolate the fault, and does not recur when the line is re-energised.
This means that in the majority of fault incidents, if the faulty line is immediately tripped out,
and if time is allowed for the arc to de-ionise, reclosure of the CB will result in the line being
successfully re-energised. (A Closed/Open/Closed cycle)
However, some faults will be permanent (such as a line fallen to earth). In this event the
auto-recloser must be able to react to the permanent fault, and on the first reclose and
detection of the permanent fault open the CBs (and, if required lock out the auto-reclose
functionality). (This is a Closed/Open/Closed/Open, 4 cycle system).
Auto-recloser (AR) schemes are implemented to carry out this duty automatically.
Functional Description
MiCOM C264
7.1.1.2
C264/EN FT/C80
Page 157/240
Behaviour
The general diagram of the auto-recloser function follows:
C264/EN FT/C80
Page 158/240
Functional Description
MiCOM C264
The TRIP_1P_X or TRIP signal sent by the protection relay (single-phase trip / 3phases trip)
During this phase, if the CB_HEALTHY signal is not in the SET state, the cycle is not
authorised and the automation re-initialises to wait for the first cycle. The CB_HEALTHY BI
is optional: if it does not exist, no check is done.
7.1.1.2.3 Waiting CB opening
As soon as the trip has been detected, a 150 ms timer is launched to wait for the circuit
breaker opening.
For a 3 single poles CB:
In a single phase cycle, only one phase position is awaited in the OPEN state
(CB_STATE_1P_X)
In a 3-phases cycle, each one phase positions is awaited in the OPEN state
Whatever was the cycle, the 3 phase position is awaited in the OPEN state
(CB_STATE)
For a 3-phase cycle, the DO AR_TRIP_3P is closed (if configured) as soon as the CB is
detected as open.
The auto-recloser function is locked if the CB is not opened at the end of the timer.
7.1.1.2.4 Launch cycle timer
As soon as the CB is detected as open, the timer associated to the current auto-recloser
phase is launched.
During the single-phase cycle, the trip signal must disappear: if not, the auto-recloser
function will be locked. Furthermore, a 3-phases trip could appear. In this event, the current
cycle is stopped and the second 3-phases slow cycle is launched.
Functional Description
MiCOM C264
C264/EN FT/C80
Page 159/240
A trip during the last auto-recloser cycle (in this event, the AR_STATE signal is set at
the AR_BAR_SHOTS state)
A lock signal through the AR_LOCK Binary Input at the SET state
There is no pole discordance at the end of the single-phase cycle: that is, the three
phases are opened
2 phases are in an opened state at the end of the single-phase cycle without 3-phases
trip signal
The AR_STATE signal is set at the AR_BAR_LOCK state if the auto-recloser function is
locked, and the cycle counter is set to 0.
There are two configurable methods to unlock the function. These methods are selected
during the configuration phase and can be used separately or together:
1.
A manual closing of a circuit breaker: in this event, the Reclaimmc timer is launched.
2.
If none of these methods are selected, the auto-recloser is automatically unlocked if no lock
condition is set and circuit breaker is closed. In this event, the Reclaimml timer is launched. If
the CB is not closed at the end of this timer, the auto-recloser is locked again.
C264/EN FT/C80
Functional Description
Page 160/240
7.1.1.3
MiCOM C264
Information
Description
Type
CB_STATE_1P_x
BI (DP)
CB_STATE
CB status (global)
BI (DP)
TRIP_1P_x
BI (SP)
TRIP
BI (SP)
AR_IS/OS
AR_LOCK
CB_HEALTHY
BI (SP)
AR_BLOCKING
CB_ORDER_1P_x
DO
CB_ORDER
CB order (global)
DO
AR_TRIP_3P
AR_IS/OS
SI (DP)
AR_STATE
SI (MP)
AR_READY
State1
State2
AR_FIRST_CYCLE_1P
AR_FIRST_CYCLE_3P
AR_SECOND_CYCLE_3P
AR_THIRD_CYCLE_3P
State6
AR_FOURTH_CYCLE_3P
State7
State4
State8
AR_RECLAIMC
State9
AR_BAR_SHOTS
State10
AR_BAR_LOCK
State11
AR_RECLAIMML
State12
AR_RECLAIMMC
State13
AR_FAIL
SI (MP)
AR_SYNC_NOK
State0
AR_HARD_ERROR
AR_ILOCK_NOK
State2
AR_NO_FAULT
No failure
State3
Functional Description
C264/EN FT/C80
MiCOM C264
Page 161/240
Parameter
Description
Value
AR_TYPE
Mono / Tri
AR_CYCLE_NUMBER
Number of cycles
1, 2, 3 or 4
1P_CYCLE1_TIMER
From 10 ms to 5 seconds,
with a 10 ms step
3P_CYCLE1_TIMER
From 10 ms to 60 seconds,
with a 10 ms step
3P_CYCLE2_TIMER
3P_CYCLE3_TIMER
3P_CYCLE4_TIMER
RECLAIM_TIMER
Reclaim timer
RECLAIMMC_TIMER
Reclaimmc timer
RECLAIMML_TIMER
Reclaimml timer
UNLOCKING_METHOD
SYNC_ENABLE
Yes / No
C264/EN FT/C80
Functional Description
Page 162/240
7.1.2
MiCOM C264
The C264 computer supports these two diagrams used in Trip Circuit Supervision:
Trip Circuit Supervision with one Digital Input + external resistor: FIGURE 55: TRIP
CIRCUIT SUPERVISION WITH ONE DI
Trip Circuit Supervision with two Digital Inputs without external resistor: FIGURE 56:
TRIP CIRCUIT SUPERVISION WITH TWO DI.
For the Trip Circuit Supervision with one Digital Input + external resistor, please refer to
FIGURE 55: TRIP CIRCUIT SUPERVISION WITH ONE DI.
The resistor (R) in the trip circuit supervision scheme should have a value in agreement with
2 limits:
1.
High enough so that once the CB is open, the tripping coil powered via the resistor
has no magnetic effect anymore so that the tripping mecanism is released (within a
possible delay due to inductive effect of the coil).
2.
Low enough so that the C264 input powered via the resistor (and the tripping coil) is
detected active.
Therefore:
1.
It is assumed that 10% of nominal voltage applied on the tripping coil makes its
magnetic effect low enough to release the tripping mechanism after activation. Taking
into account normal tolerance on power supply, this leads to a minimum value of R
being approximately 10 to 12 times the resistance of the tripping coil.
2.
The input was tested to operate with a series resistor up to 40kOhm, still leaving
voltage across the input above the minimum. Taking into account tolerances, this
defines a maximum value for the resistor of 20kOhm.
We recommend the value in the middle of the range (geometrically). If Rc is the resistance of
the tripping coil, then:
R / 12xRc = 20kOhm / R
The power rating of the resistor must be such that it withstands permanent application of
maximum trip circuit voltage. Therefore:
P = (1.2 x Uaux)2 / R
Functional Description
C264/EN FT/C80
MiCOM C264
Page 163/240
+ Uaux
Computer
Protection relay
Vn+
DI-1
VnVn+
DI-2
Vn-
Load Supply
Vn+
DI-3
VnR
CB
Uaux
C0138ENc
Use this diagram for inputs that have a detection threshold > 55% for
the "set" state: for example, CCU200 A07.
C264/EN FT/C80
Functional Description
Page 164/240
7.1.3
MiCOM C264
7.1.3.1
The number of CB operations for the 3 poles (i.e. the highest of the pole values)
Each integral is calculated between the trip command time and the time when the RMS
value is less than 0.1A.
Example:
Reset
All the stored values can be simultaneously reset. This control can be available at all controls
points.
Functional Description
C264/EN FT/C80
MiCOM C264
7.1.3.3
Page 165/240
Monitoring
The C264 can monitor each cumulated value with two thresholds settable independently and
display an overrun event on the local mimic or activate a LED.
The information can feed in any local or distributed automation scheme.
7.1.3.4
Inhibition
The function can be disabled through a setting.
To prevent the sums from accruing, for example during a test, use:
7.1.3.5
The Micom S1
Storage
The values are stored in a non-volatile memory to save them in event of auxiliary power
outage.
A dedicated procedure allows you to set the stored values with the CAT on a per
measurement basis.
The switch of any new configuration database does not reset any of the stored values, but a
software download does.
In event of a C264 redundancy, the stored values in the standby computer are exchanged
from Main to Standby after each calculation.
C264/EN FT/C80
Functional Description
Page 166/240
MiCOM C264
7.1.4
7.1.4.1
Presentation
7.1.4.1.1 Role
MiCOM C264 with AVR (Automatic Voltage Regulation) is a compact Voltage Regulation
solution for Electrical Substations; it automatically regulates the voltage level on the
secondary side of HV/MV and/or MV/MV transformers.
It is able to automatically send secured commands (Raise, Lower) to the Tap Changer, fully
aware of the transformer characteristics (voltage,), the Tap Changer characteristics
(position number, inter tap timers,), the voltage targets and the various transformer or tap
changer alarms.
Note: the AVR function cannot be used on one C264 together with another built-in function.
7.1.4.1.2 Topologies
Two C264 types are defined to address specific AVR issues:
7.1.4.1.3 Modes
The operator decides on the LHMI which way he/she wants to operate the AVR:
Manual (open loop): the operator forcefully issues Raise/Lower commands to the tap
changer from the LHMI
Automatic (closed loop): the AVR algorithm issues Raise/Lower commands to the tap
changer when the voltage is outside limits and tap changer conditions permit; the
operator can still deactivate the algorithm from the LHMI.
The possibilily of other manual controls In automatic mode depends on the parameter
manual controls allowed:
Not allowed
Only when AVR is locked (whether it is due to the External regulation locking or to an
AVR additional features: overcurrent detection, tap changer blocking)
Always
Optional:
Analog Inputs
WD
output signals
contacts
Optional:
Analog Outputs
Raise/lower
Optional:
Serial Comm.
to IEDs
VT fuse
CB posit.
Functional Description
C264/EN FT/C80
MiCOM C264
Page 167/240
7.1.4.1.5 Hardware
The MiCOM C264 includes in a 40 TE rack:
2 CB positions
1 VT Fuse
+7 customizable DIs (Bay L/R, AVR Auto/Manu, AVR on/off, alarms, external lock,
voltage target selection)
2 Raise/Lower controls
1 AVR ON/OFF
A TMU220 board (4 CTs / 5 VTs) for direct acquisition of currents and voltages
An AOU board (option) for analogue outputs (4-20 mA) to repeat the Tap changer
positions or measurement values (voltages, circulating currents,)
power factor
topology information from IEDs (in place of serial bus) or other C264
C264/EN FT/C80
Functional Description
Page 168/240
MiCOM C264
Each transformer is controlled by one computer but the AVR function is only activated on
one computer. The figure exemplifies an architecture that controls two transformers:
acquisition of U,I,Q,P
Tr2
station bus
(iec 61850)
C264-2
command of tap changer
C264-1
AVR on
acquisition of U,I,Q,P
Tr3
C264-3
command of tap changer
C0344ENa
AVR function is activated on computer C264-1. This computer gets analogue values through
the station bus from computers C264-2 and C264-3 and issues tap changer commands
through the station bus.
7.1.4.2
The actual voltage can include a Line Drop Compensation (see further).
For double wound transformer (double wound set to Yes), according to the setting double
wound voltage, the automatic voltage regulation applies to the:
If the difference between the 2 voltages is larger than a set value (double wound voltage
difference), the signal Double wound voltage difference is positioned.
Functional Description
MiCOM C264
C264/EN FT/C80
Page 169/240
At AVR start up, the local target voltage mode is active for a defined delay (end of
local target voltage delay).
If a valid remote target voltage value is received before the end of the delay, the
remote target voltage mode is set at the end of the delay.
If a valid remote target voltage value is received after the end of the delay, the remote
target voltage mode is set immediately.
When the target voltage mode changes from remote to local, the same delay is launched,
and the behavior is identical.
An operator can, with a dedicated control, forcefully put the target voltage mode to local
target voltage. In this event, the mode is set immediately.
Period dependent
For example:
C264/EN FT/C80
Functional Description
Page 170/240
MiCOM C264
7.1.4.2.3 Regulation
The actual voltage is compared to the target voltage.
If the actual voltage remains outside of the regulation deadband for an initial tap time
delay (TA1), the C264 with AVR commands a tap change.
Any voltage swing that passes through the complete deadband, causes the initial tap time
delay to be reset and a new time cycle to be started.
If more than one tap change is required to bring back the voltage within the deadband, the
second tap changer is activated after TA2 (inter tap time delay). Note: TA2 < TA1.
If applicable, the last tap changing is delayed by an end tap delay.
The command occurs only if the following conditions prevail:
Primary CB state, Circuit Breaker position on the primary side of the transformer is
set to CLOSED
Functional Description
C264/EN FT/C80
MiCOM C264
7.1.4.3
Page 171/240
In the first case, the tap changer position (on voltage loss) behaviour can be set to:
keep the tap changer on the current tap (no tap control performed)
The function sets the tap changer on the defined tap position, only if the following
conditions prevail:
The Primary CB state, Circuit Breaker position on the primary side of the transformer
is set to OPEN
Sequencing of commands: the subsequent command occurs not earlier than the preset tap
delay.
C264/EN FT/C80
Functional Description
Page 172/240
MiCOM C264
7.1.4.3.2 Fast Tap Changer move AFTER Voltage Loss and Voltage recovery
When the Fast tap changer move after voltage loss function is set, the AVR issues
Lower/Raise commands TA3 after the voltage has overrun the voltage presence threshold.
The command occurs only if the following conditions prevail:
The Primary CB state, Circuit Breaker position on the primary side of the transformer
is set to CLOSED
If all the above conditions prevail, and the voltage is present (voltage above voltage present
threshold) longer than the voltage present delay (Ta), the first tap delay is bypassed for
TA3 (first tap delay bypass delay). The first tap control activation is delayed by TA2.
C0465ENa
If the fast tap changer move after voltage loss function is NOT active, when the voltage is
detected, the first tap control activation is delayed by TA1.
7.1.4.3.3 Abnormal Voltage signalisation
The voltage is considered as abnormal if, till the confirmation time expires, the actual
voltage is moving outside the range: [Vtarget x (1- %) ; Vtarget x (1+ %)] , % is the
abnormal voltage (threshold). This range is wider than the deadband. Refer to the
preceding schematic.
In this event, the signalisation is positioned after the abnormal voltage delay.
Any return of the voltage into the normal range resets the delay and deactivates the
abnormal voltage signal.
7.1.4.3.4 Tap Changer Failure supervision Tap Blocking
The Tap Position Indication value may be wired on digital inputs (or optional analog inputs).
If the Current Tap value is not valid, all the functions using this information are locked.
The signalisation indicates the kind of problem on the tap changer.
The signalisation Tap Changer Fault results from one of these conditions:
after the TCIP time out delay, the TCIP (Tap Changer In Progress) signalisation is
not positioned (on tap control sequence)
after the TCIP end time out delay, the TCIP signalisation input is not reset (on tap
control sequence)
Functional Description
C264/EN FT/C80
MiCOM C264
Page 173/240
after the TCIP signalisation reset, the tap has not the expected value
after the global sequence delay (start on 1st tap control), the voltage is not normal yet
When the signalisation Tap Changer Fault is positioned, the tap control or the sequence of
tap controls in progress is cancelled, and no more tap control is accepted (whether it is
manual or automatic).
Depending on the tap changer fault behaviour, when a tap changer fault occurs, AVR can:
position the Tap Changer Fault signalisation, and reset it when none of the faulty
condition prevail (automatic reset)
position the Tap Changer Fault signalisation, and keep it set until an operator
deactivates the automatic regulation, and activates it again (manual reset).
If the tap changer blocking activation is on, a Tap changer Blocked is positioned in event
the Tap command is issued for a time longer than the tap changer blocking delay. This
means that the tap position is not reached during this time and this is considered abnormal.
A signalisation Voltage Regulation Fault is positioned with the corresponding status, when:
a VT fuse is detected
When none of the above problems is detected, the signalisation Voltage Regulation Fault
status is OK.
7.1.4.3.5 Tap Changer Lowest/ Highest position
MiCOM C264 with AVR monitors the pair Tap changer Lowest/Highest reached position.
When the current tap equals the highest/lowest tap value, the indication
Highest/Lowest Tap reached is positioned.
If the Tap Position Indication value is not valid, The Lowest / Highest Tap reached
indications are not valid.
C264/EN FT/C80
Functional Description
Page 174/240
MiCOM C264
On the slipping
period for counting
Overall
changes
up to 6,000,000
Raise
up to 3,000,000
Lower
up to 3,000,000
Limits
reached
Time of use
On operator reset
the partial number of tap changes, raise and lower controls are reset
the partial time of use with voltage present of each tap is reset
The time of use is recorded, only if the voltage is present, and the Tap
Position Indication and the TCIP signalisation are valid.
Functional Description
MiCOM C264
C264/EN FT/C80
Page 175/240
7.1.4.4
on C264 restart
Vr = Vm - Vcomp
Z = R + jX, R and X are % of Vn/In
R = Active compounding method parameter A1, % of Vn/In (nominal voltage and current)
X = Active compounding method parameter B1, % of Vn/In (nominal voltage and current)
The reactive compounding method is used only when two transformers are in parallel.
C264/EN FT/C80
Functional Description
Page 176/240
7.1.4.5
MiCOM C264
Other functions
Frequency
Cos
These calculated measurements can be viewed locally on the Local HMI (LCD Screen).
7.1.4.5.2 Raise/lower control and voltage target from external signals
Depending on AVR mode, additional inputs can be used:
These external commands have precedence over the Local LCD commands and are active
as the external signal is positioned.
The activation of Raise/lower Controls also depends on the usual AVR conditions (CB
status, TC fault,).
7.1.4.5.3 Reverse Power Flow (RPF)
7.1.4.5.3.1 Detection
Reverse power flow is detected with the sign of the secondary Active Power measurement
value.
As long as the Active Power measurement value is above 0, no reverse power flow is
detected.
If the Active Power measurement value is under 0, the reverse power flow detection delay
starts. At the end of the delay, if the Active Power measurement value is still under 0, the
signaling Reverse power flow detected is positioned.
When reverse power flow is detected, if the Active Power measurement value is above 0, the
reverse power flow detection delay starts. At expiry, if the Active Power measurement value
is still above 0, the signaling Reverse power flow detected is reset.
Reverse power flow detection is done only if the line current value is more than or equal to
the defined RPF current threshold. Otherwise, no reverse power flow detection is
performed.
Functional Description
C264/EN FT/C80
MiCOM C264
Page 177/240
Active power
Time counter
Tconfirm
T
Reverse power
flow detected
On
On
7.1.4.5.3.2 Behavior
When reverse power flow is detected, the RPF management mode defines the behavior:
Ignore: nothing specific is done is this case, regulation is still performed in the same
way.
Block operation: no more automatic regulation is performed, only manual raise and
lower control are allowed (if set). The automatic voltage regulation is locked by
reverse power flow, and the signal AVR locked by reverse power flow is positioned.
This signal is reset when the reverse power flow detection ends.
Regulate in reverse: the automatic regulation is running in reverse power flow mode.
The transformer primary side analog measurements (U, and if compounding is used: I and
) are needed for automatic regulation. These measurements are received by the AVR, and
not computed from transformer secondary side analog measurements.
The automatic voltage regulation is monitoring the primary voltage, current and phase
difference, and keeps the primary voltage in a deadband within a target voltage by activating
raise/lower controls. The parameters defined for normal power flow regulation are not used
in the case of RPF regulation.
The AVR activates the tap changer with a RAISE control, after a first (or next) tap delay, if:
The AVR activates the tap changer with a LOWER control, after a first (or next) tap delay, if:
C264/EN FT/C80
Page 178/240
Functional Description
MiCOM C264
nominal voltage: the same nominal voltage as for normal regulation (secondary of
transformer)
Compounding in reverse power flow mode is available only with single phase voltage.
If no compounding is needed, the A1, B1, A2 and B2 values must be set to 0.
7.1.4.5.3.4 Other differences
No check on voltage presence is done. When RPF is detected, it means the voltage is
present on both sides of the transformer.
The following AVR functions are not available:
Overcurrent detection
Overvoltage detection
Undervoltage detection
The target voltage can be changed (within its range) with the setting tool or with a dedicated
setpoint control. All the target voltage management modes usable in the normal power flow
regulation mode are not available.
Limits:
7.1.4.6
Usable only with standalone transformer management even when in normal power
flow (not with a transformer in parallel method). Master / follower configuration must
be set to none.
Transformers in parallel
Two methods can be used whether the transformers are identical and work together or not.
Functional Description
C264/EN FT/C80
MiCOM C264
Page 179/240
C264 with
BB
BB
C0467ENa
The Master compares the tap position of the followers with its own tap position and if
deviations are detected, the master put commands to bring them to its own position.
No circulation currents are evaluated; this imposes severe limitations on the network
operation:
The indication of which C264 is the Master and which one is Follower can be viewed
It can be available
on an output contact
If the master recovers, the backup master remains master. The master regulates its voltage
in stand alone mode.
NOTE:
If the mode goes automatically to standalone, returning requires a manual operation (reset
process in which the master restarts all the followers).
C264/EN FT/C80
Functional Description
Page 180/240
MiCOM C264
Current seen by #1 = IL + Ic
Current seen by #2 = IL Ic
#2
IL-Ic
2IL
Ic
IL+Ic
#1
C0468ENa
#2
IL-Ic
Vxl
Ic
Vr
2IL
T
IL+Ic
#1
As Ic is not present in the feeder, another method is needed: compensating the voltage
attenuation due to currents circulating from one transformer to the other.
With reactive compounding, the voltage to be regulated (Vr) is evaluated as follows:
Vr = Vm Vxl, where:
Vr = actual voltage to regulate
Vm = measured voltage
Vxl = Compounding voltage = Z.I where Z = R jX
Functional Description
C264/EN FT/C80
MiCOM C264
Page 181/240
R = Reactive compounding method parameter A2, % of Vn/In (nominal voltage & current),
this the resistive part of the load line
X = Reactive compounding method parameter B2, % of Vn/In (nominal voltage & current),
this the reactive part of the transformer impedance (the transformer impedance is mostly a
reactance)
NOTE:
7.1.5
7.1.5.1
Presentation
7.1.5.1.1 Topologies
A substation includes busbars and transformers.
A group is a set of interconnected busbars. A transformer belongs to a group if it is
electrically connected to a busbar of this group at the low voltage level. The voltage target is
that of the highest priority busbar.
The partition is dynamic: two independent groups may be merged as a result of the closing
of a circuit breaker.
Typical topologies:
several coupled busbars in a group that includes one transformer or several ones in
parallel (see an example further)
Each transformer is controlled by one computer but ATCC function is only activated on
one computer. The figure that follows shows an example of the architecture for the
ATCC function that controls two transformers
acquisition of U,I,Q,P
Tr2
station bus
(iec 61850)
C264-2
command of tap changer
C264-1
AVR on
acquisition of U,I,Q,P
Tr3
C264-3
command of tap changer
C0344ENa
ATCC function is activated on computer C264-1. This computer gets analogue values
through the station bus from computers C264-2 and C264-3 and sends tap changer
commands through the station bus.
C264/EN FT/C80
Page 182/240
Functional Description
MiCOM C264
The voltage in one group is far from the Target Voltage. This is the most common
situation.
The voltage is correct, but there is a circulating current between parallel transformers.
This happens when two groups are interconnected.
The voltage is correct, but the Tpi range and patterning may be changed when the
state of any relevant switchgear changes.
Functional Description
MiCOM C264
C264/EN FT/C80
Page 183/240
7.1.5.1.4 Capacity
A MiCOM C264 is able to manage a maximum of:
7 transformers
4 transformers in parallel
8 busbars
2 voltage levels
MCB trip. If a transformer is in automatic control and there is an invalid evolution of the
tap changer, the tap changer MCB is tripped
Run away: if the Tap changer operates without valid commands or if tap changer
operation causes Tap Changer to move further away from the set values. This alarm
is reset 30 s after the group is switched to ATCC Off
TCIP signal is too late [TAP bad TCIP] or too long [TAP long TCIP]
The tap is invalid [TAP invalid]: tap number is not the required tap; you may have
this problem after a tap operation if the tap number is not the expected one.
This TAP bad TCIP alarm is reset 30 s after the group is switched to ATCC Off
ATCC hunting: this alarm is reset 30 s after the group is switched to ATCC Off.
Overcurrent, overvoltage
Busbar:
Invalid voltage (when different values for parallel transformers) [inv voltage]
Global:
Target unreached
ATCC defect: raised if one of these alarms is raised, and is reset if all of them are
reset
Error Log Indication: raised if one of the input is raised and is reset if the operator
selects the "Clear ATCC Faults" command.
DBI override
C264/EN FT/C80
Functional Description
Page 184/240
7.1.5.2
MiCOM C264
Monitoring logic
7.1.5.2.1 Modes
From the PACiS OI or from a SCADA, in agreement with the Substation control mode, the
operator controls the Global ATCC mode (substation level) and the busbar ATCC modes.
Substation control mode
Local
inhibited
allowed
Remote
allowed
inhibited
It is up to the operator to choose, on a global basis, how the mode (that is, the ATCC status)
is changed:
The Circuit Breaker at the other side of the transformer (primary) is closed
No regulation locking information (AVR defect alarm, external lock, run away,
overcurrent on a transformer)
the measured voltage must be within tolerances set as ratios of the nominal voltage:
the deviation to the target voltage must be lesser than a set ratio of the nominal
voltage:
Moreover, before sending a tap changer control (Raise/Lower), the following conditions are
required:
No tap in progress
Functional Description
C264/EN FT/C80
MiCOM C264
Page 185/240
OR
one of the voltage differs by more than max voltage difference (ratio) from the
average voltage
OR
A busbar in
the group &
Mode on
group interconnection are
Off
More than 4
transformers
in the group
Global ATCC
status is Off
Group Status
= Off
Invalid
average
voltage
Invalid
disconnector/
circuit breaker
in the group
C264/EN FT/C80
Functional Description
Page 186/240
7.1.5.3
MiCOM C264
2 deadbands, one is coarse (DB1, to initiate tapping), the other is fine (DB2, to end
tapping)
a max tap change rate of change that cannot be exceeded when moving the tap.
Each busbar voltage target is selected among the 5 through controls, in accordance with the
voltage target ramping rate.
If the busbar is part of a group, the target in force is the one of the highest priority busbar. A
single tap is changed at a time within a group but several groups may be active
simultaneously.
Each group has to reach the target voltage.
If the voltage is outside DB1, then an initial timer T1 is set and the tap control is issued once
the timer has elapsed.
More tap changing may be necessary in order to enter DB2: they are actuated when the
second timer T2 has elapsed; the changing is subjected to the max tap change rate.
+DB1
+DB2
Vtarge
-DB2
-DB1
T1
T2
Time
REMOTE BUSBAR:
The voltage target may be set for a point far from the LV transformer side.
Reference_ULV = (Target_ ULV + Drop_U) x set point ponderation (0.9 1)
ULV is the actual measured value
Compounding methods:
PLV and QLV are local measured active and reactive powers
R% and X% are resistive/reactive coefficients
Functional Description
C264/EN FT/C80
MiCOM C264
Page 187/240
C0474ENa
NOTE:
If line drop compensation is not used, set the resistive and reactive
coefficients to the minimum.
2/3
1/2
OR
Voltage < Target Voltage - Voltage Deadband x Nominal Voltage for more than the
time-out T1.
Dual deadbands are used to ensure that the post tapping voltage is sufficiently closed to the
selected target voltage. DB1 is used to initiate tapping and DB2 is used to end tapping.
7.1.5.3.3 Timeouts
Moving the taps of the transformers is achieved with respect to some time-outs:
The "Initial tap" of a transformer is delayed by a time out T1, the next ones by a time out T2.
Several taps are used if one is not enough to reach the voltage target or the optimisation of
the circulating current. T2 begins after the end of the TCIP.
When the voltage drifts in and out of the deadbands, the system counts up to T1 when the
voltage is outside of the deadband1. If the voltage returns within the deadband2 before T1 is
reached, then the system counts down to 0.
C264/EN FT/C80
Functional Description
Page 188/240
MiCOM C264
Any voltage swing that passes from through the complete deadband from one side to the
other, causes the initial tap time delay to be reset and a new time cycle to be started.
After an auto-recloser operation, the group (or the two new groups) keeps the same ATCC
modes; however the count is reset to zero and the new time delay is T1.
To ensure that transient voltage fluctuations do not cause unnecessary tap change, the
voltage must remain outside of the deadband for an initial Tap Time Delay (settable T1).
Any voltage swing that passes from through the complete deadband from one side to the
other, causes the initial tap time delay to be reset and a new time cycle to be started.
If a tap changing is required after a previous tap control:
RateMax
Time
T1
T2
T2
T0
Tap RAISE 1
Tap RAISE 2
Tap RAISE 3
C0010ENa
Functional Description
C264/EN FT/C80
MiCOM C264
Page 189/240
0,36
0,26
40,00
139,03 2,39
1,76
22,75
140,01 3,37
2,48
16,14
141,01 4,37
3,21
12,44
143,04 6,40
4,71
8,50
145,04 8,40
6,18
6,47
146,01 9,37
6,89
5,80
150,01 13,37
9,83
4,07
151,02 14,38
10,58
4,00
152,05 15,41
11,33
4,00
153,03 16,39
12,06
4,00
When a transformer belongs to a group of several transformers, the time out is applied to the
group. 2 different groups have separate timeout references, thus allowing simultaneous taps.
The tap is defined as the "first one" when (logical OR):
When the voltage crosses from one side of the deadband to the other side.
C264/EN FT/C80
Functional Description
Page 190/240
MiCOM C264
7.1.5.3.4 Homing
When the mode of the busbar is in automatic control, homing taps transformers such that
their open circuit terminal volts follows the volts on the busbars that they are selected to
within 3% of the busbar voltage.
Homing is active:
Homing is disabled while the busbar voltage is less than Umin (80% of nominal voltage).
If a transformer is under Homing Mode, a manual control is not accepted.
If (and only) a fault on the Tap Changer remains active, the transformer remains OUT of
automatic control. As a consequence, homing ceases as long as the Tap Changer is faulty
and until the operator selects "Clear AVR faults".
Homing Initial tap delay is used for the first tap in the homing mode.
Homing Inter tap delay is used between successive taps.
7.1.5.4
The number of taps and tapping ranges of the transformers are identical
Then the maximum Tpi range between the transformers will be 1 and there will be a
balanced control of them when the voltage is changing.
Calculation is as follows:
under the deadband -> action is raise on the transformer with the lowest Tap
over the deadband -> action is lower on the transformer with the highest Tap
if voltage is IN the deadband, the system sets the transformer within one tap
Functional Description
C264/EN FT/C80
MiCOM C264
Page 191/240
under the deadband -> action is raise on the transformer with the lowest
transformer ratio
over the deadband -> action is lower on the transformer with the highest
transformer ratio
if voltage is IN the deadband, the system sets the transformer within a percentage of the
transformer ratio. This percentage P is calculated for all groups:
SGT1
SGT2
I1
I2
Sn (power value)
U, I, P, Q
Current tap
C264/EN FT/C80
Functional Description
Page 192/240
MiCOM C264
I
Ic
X1
I1
X2
U
I2
E1
E2
I2
I1
Functional Description
C264/EN FT/C80
MiCOM C264
Page 193/240
If the voltage is under the target then transformer with highest || is tapped UP
If the voltage is over the target then transformer with lowest || is tapped DOWN
If the voltage is out of the deadband and active power < 0 (|| > /2) then:
If the voltage is under the target then transformer with lowest || is tapped UP
If the voltage is over the target then transformer with highest || is tapped DOWN
If the voltage is under the target then transformer with highest || is tapped UP
If the voltage is over the target then transformer with lowest || is tapped DOWN
If the voltage is out of the deadband and active power < 0 (|| > /2) then:
If the voltage is under the target then transformer with lowest || is tapped UP
If the voltage is over the target then transformer with highest || is tapped DOWN
C264/EN FT/C80
Page 194/240
Functional Description
MiCOM C264
7.2
Synchrocheck
7.2.1
Synchrocheck General
It is impossible to plug the computers directly into the high voltage electric network. The
computers receive the data from the Current Transformers (CT) and from Voltage
Transformers (VT) installed on the TMU2xx boards.
The purposes of the CT and VT include:
To deliver current and voltage data that gives a reliable picture of what happens in the
high voltage part of an electrical substation
To make the galvanic insulation between the high voltage part and the measurement
and protection circuits,
To protect the measurement circuits against damage when a fault comes onto the
high voltage network.
These measurements are used for the protection function and for the Internal Synchrocheck,
Type 1 and 2
The synchrocheck device allows you to couple together 2 electrical networks.
These networks can be connected to different sources (generator), so they are not
synchronised with each other.
The Synchrocheck function measures two voltages with respect to phase angle, frequency
and magnitude to protect against the connection of two systems that are not synchronized
with each other.
In a computer, you can use the synchrocheck function for as many as 2 circuit breakers. You
can control only one circuit breaker at one time. The set of parameters defined for the
synchrocheck applies for both circuit breakers.
There are 2 types of internal synchrochecks:
The synchrocheck computes these measurements and accepts or not the closure of the
circuit breaker that would connect them.
The three phase voltages of the line and one phase of the bus bar are connected to the
synchrocheck.
Functional Description
C264/EN FT/C80
MiCOM C264
Page 195/240
Line
CB
SYNCHROCHECK
SYNCHRO
L CHECK
L
L
B1 B2
Bus Bar 1
Bus Bar 2
C0476ENa
Synchrocheck Schemes
The synchrocheck schemes include:
7.2.3
Synchrocheck Algorithm
C264/EN FT/C80
Functional Description
Page 196/240
7.2.4
MiCOM C264
Synchrocheck Applications
For synchrocheck applications, please refer to the figure that follows:
CB
close
controls
Check
synchroniser
Close
Generator
Network
Busbar
(a) Application to generator
CB
close
controls
Check
synchroniser
Close
Network
#
Line A
Network
#1
CB 1
Busbar B
(b) Application to two networks
C0006ENa
7.2.6
Manual Close Close request without synchrocheck or when the synchrocheck is out
of service.
Automatic Close
Manual override
Synchrocheck override.
The differences between them are the requirements used to accept closure.
Functional Description
C264/EN FT/C80
MiCOM C264
7.2.7
Page 197/240
Synchrocheck
Bus bar 2
Open/close
contact
Type 1
Type 2
TMU200+DSP
YES
NO
NO
DOU
TMU220+DSP
YES
NO
YES
DOU
TMU210+DSPIO
YES
YES
NO
DSPIO or DOU
When the CB is wired on the DSPIO board, the DSPIO directly manages the close/open
contacts.
Otherwise, the PPC manages the contacts using a CCU or a DOU board.
Both contacts must be wired on the same kind of board: 2 on DOU/CCU or 2 on DSPIO. One
contact wired on the DOU, and one contact wired on the DSPIO is not allowed.
7.2.8
Synchrocheck Calculation
Whatever the synchronising mode V, and F have to be calculated. These values are
available through the measurement module.
V is calculated through the RMS value of the voltages on both bus bar and line side.
The value of F is assumed to be constant across the period. As a result, knowing
(through measurement), we know when the synchrocheck conditions are achieved (this will
easily include the reaction time of the breaker aso).
time_synchro = 2 * pi *F /
For more details, please refer to the topic Focus 3: TMU2XX: CT / VT measurement
processing as far as Threshold Detection.
7.2.9
7.2.10
7.2.11
C264/EN FT/C80
Functional Description
Page 198/240
7.2.12
MiCOM C264
Synchrocheck: Scheme LL: Live Line, Live Bus: Real Time Sequences
For LL we have two types of synchronization:
1.
2.
3.
Functional Description
C264/EN FT/C80
MiCOM C264
7.2.12.2
Page 199/240
Locking Conditions
Confirmation
Time
2
T1
T2
4
T3
T4
C0479ENa
1.
If a close order comes before T1, it is sent to the DSP board, and the control is
executed at T2 coming from DSP board.
2.
If a close order comes between T1 and T2, it is buffered until T2 if the locking
conditions are not lost. If the locking conditions are lost before T2 then the command
is rejected.
3.
Example 2
1.
If a close order comes before T1, it is sent to the DSP board, and the control is
executed at T4 coming from DSP board.
2.
If a close order comes between T1 and T2, it is buffered. As the locking conditions are
lost then the order is sent to the DSP and executed at T4.
3, 4.
If a close order comes between T2 and T4, it is sent to the DSP board, and the control
is executed at T4 coming from DSP board.
5.
If a close order comes after T4, it is sent to the DSP board, and the control is executed
immediately from DSP board.
C264/EN FT/C80
Functional Description
Page 200/240
MiCOM C264
Example 3
Anticipation Time
Coupling Conditions
Locking Conditions
Confirmation
Time
1
T1
7.2.13
2
T2
4
T3
5
T4
6
T5
1.
If a close order comes before T1, it is sent to the DSP board, and the control is
executed at T4 coming from DSP board.
2.
If a close order comes between T1 and T2, it is buffered. As the locking conditions are
lost then the order is sent to the DSP and executed at T4.
3, 4.
If a close order comes between T2 and T4, it is sent to the DSP board, and the control
is executed at T4 coming from DSP board.
5.
If a close order comes between T4 and T5, it is sent to the DSP board, and the control
is executed immediately from DSP board.
6.
If a close order comes after T5, it is sent to the DSP board, and the control is rejected
after the synchrocheck waiting time (not illustrated on the above drawing).
Synchrocheck Schemes that use VLINE and not(VBUSBAR) or not(Vline) and VBUSBAR
voltage controls
In event of the absence of one of the two voltages, at the end of a settable delay T2, the
authorisation to close is given:
Vline
and
Not(Vbusbar)
Closing authorization
C0482ENa
and
Not(Vline)
Closing authorization
Functional Description
C264/EN FT/C80
MiCOM C264
7.2.14
Page 201/240
and
Not(Vbusbar)
Closing authorization
The difference in amplitude (algebraic) between the two voltages (V) is lower than
the configurable / settable threshold (Evect) AND
The phase difference between the two voltages () is lower than the configurable /
settable threshold (Ephase) AND
For type 1:
The frequencies are as Fline and Fbusbar are such Fmin<F<Fmax where Fmin
and Fmax are the extreme acceptable frequencies AND
The difference between the two frequencies (F) is lower than the configurable /
settable threshold (Efreq)
For type 2:
The frequency shift between signals (S) is lower than the configurable / settable
threshold (Sfreq)
These conditions must be still met before the time-out of a delay T1 started on the
appearance of the conditions else the synchrocheck function will not authorise the CB
closing.
If during the delay time T1 one of these conditions is lost, T1 is reinitialised and is relaunched on reappearance of all the conditions.
F <Efreq
and
T1
Reclosing authorization
< Ephase
V < Evect
C264/EN FT/C80
Functional Description
Page 202/240
MiCOM C264
Vline
Vbusbar
T1
and
S <Sfreq
Reclosing authorization
< Ephase
V < Evec t
The difference in amplitude (algebraic) between the two voltages (V) is lower than
the configurable / settable threshold (Evect) AND
For type 1
The frequencies are as Fline and Fbusbar are such Fmin<F<Fmax where Fmin
and Fmax are the extreme acceptable frequencies AND
The difference between the two frequencies (F) is lower than the configurable /
settable threshold (Efreq)
For type 2
The shift between signals (S) is lower than the configurable / settable threshold
(Sfreq) AND
The shift acceleration (accShift) is lower than the configurable / settable threshold
(accSfreq)
These conditions must be still met before the time-out of a delay T4 started on the
appearance of the conditions else the synchrocheck function will not authorise the CB
closing.
If during the delay time T4 one of these conditions is lost, T4 is reinitialised and is relaunched
on reappearance of all the conditions.
Fmin < Fline < Fmax
Fmin < Fbusbar < Fmax
Vline
and
T4
Authorisation to check
Vbusbar
F <Efreq
V < Evec t
Functional Description
C264/EN FT/C80
MiCOM C264
Page 203/240
Vline
Vbusbar
S <Sfreq
and
T4
Authorisation to check
accShift< assSfreq
V < Evec t
If the measured voltage is above the threshold V>, then VLINE and VBUSBAR TRUE
If the measured voltage is below the threshold V<, then not(VLINE) and not(VBUSBAR)
TRUE.
The selection of the voltage control is made during the configuration phase.
CAUTION:
C264/EN FT/C80
Functional Description
Page 204/240
MiCOM C264
If the measured voltage is above the threshold V>, then VLINE and VBUSBAR TRUE
If the measured voltage is below the dropout value defined by a configurable parameter,
then not(VLINE) and not(VBUSBAR) TRUE. The configurable parameter is a percent of the
threshold V> (95% for presence condition and 105% for absent condition).
The selection of the voltage control is made during the configuration phase.
CAUTION:
Synchrocheck Bypass
7.2.18.1
If the synchrocheck is in service, the Conduite process sends a Coupling Close request to
the Synchrocheck process.
If the synchrocheck is out of service, the Conduite process sends a Manual Close request
to the Synchrocheck process.
Synchrocheck process replies with a positive (close is possible) or negative (close is not
possible) acknowledge.
7.2.18.2
Coupling scheme BI
Locking scheme BI
When the BI bypass state is SET, the Bypass BI enables the closing.
If the Flag Yes/No is set to NO for one type of voltage check, the close request is refused
(acknowledge: Synchro NOK).
Functional Description
C264/EN FT/C80
MiCOM C264
Page 205/240
The table that follows shows 1. the different voltage checks; 2. the state; 3. the close
requests; and 4. the synchrocheck aknowledge:
2. State
1. Voltage checks
- Coupling
- Locking
- Bus Live Line Dead
- Bus Dead Line Live
- Bus Dead Line Dead
3. Close Requests:
- Synchro Close
- Manual Close
- Automatic Close
Flag Yes /
No
BI scheme
state
BI bypass
state
4. Synchrocheck
Acknowledge
No
Reset
Reset
Refused
No
Reset
Set
Refused
No
Set
Reset
Refused
No
Set
Set
Refused
Yes
Reset
Reset
Refused
Yes
Reset
Set
Bypassed
Yes
Set
Reset
Accepted
Yes
Set
Set
Bypassed
Refused:
Accepted:
If the voltage conditions agree with the closing scheme, involves a positive
acknowledge sent to the Conduite process.
Bypassed:
When the synchrocheck process sends the positive acknowledge to the Conduite process,
perform a new interlock check, before you close the Circuit Breaker. If the interlock condition
is True, the Circuit Breaker closes immediately, else the synchrocheck process sends a
negative acknowledge (Interlock NOK) to the control sender.
C264/EN FT/C80
Functional Description
Page 206/240
MiCOM C264
7.2.19
7.2.19.1
Measure
3Vpn+Vo
2Vpn+Vo
2Vpp+Vo
3Vpp+Vo
3Vpn+VB
3Vpp+VB
UA
direct
Direct
Direct
indirect
indirect
direct
not
UB
direct
Direct
Direct
indirect
indirect
direct
not
UC
direct
Direct
indirect
indirect
indirect
direct
not
UAB
indirect
Indirect
indirect
direct
direct
Indirect
Direct
UBC
indirect
Indirect
indirect
direct
Direct
Indirect
Direct
UCA
indirect
Indirect
indirect
indirect
Direct
Indirect
Direct
UO
indirect
Direct
Direct
Direct
Direct
Indirect
not
UBusbar
not
Not
Not
not
not
Direct
Direct
Protection
all
All
all
all
all
all
Excepted
59N
dir 67N
Internal
SC
not
Not
not
not
not
yes
yes
TMU200 / 220
Type-of-connection
Electrical-network-topology
parameters
parameters
3Vpn
3Vpn ( star )
3Vpn + Vo
3Vpn + Vo ( star )
2Vpn + Vo
2Vpp+ Vo
3Vpp + Vo
3Vpp + Vo ( delta )
3Vpn + Vb
3Vpn + Vb ( star )
3Vpp + Vb
3Vpp + Vb ( delta )
Functional Description
C264/EN FT/C80
MiCOM C264
Page 207/240
CAUTION:
Make sure that the VT wiring scheme is identical between line and busbar: Delta: Delta or
Star: Star.
7.2.19.2
In this configuration, the calculation of voltage, angle and frequency are the same as for
phase neutral.
Phase-to-Neutral synchro-check (SC PN) and Phase-to-phase synchrocheck (SC PP)
configurations show in the table that follows.
SC PN
SC PP
Mounting (wiring)
Star
Delta
Type of connection
3Vpn + Vb (star)
3Vpp + Vb (delta)
Reference phase
Va, Vb, Vc
7.2.19.3
When the LL scheme is valid and to allow the breaker to close, you must do a check of the
synchronization conditions between the 2 voltages.
The locking mode is the default synchronising mode. If the requirements are valid, at least
during a delay T1, the closure is made immediately. Otherwise the coupling mode is tried.
The different coupling modes are defined in agreement with the type of synchrocheck.
C264/EN FT/C80
Functional Description
Page 208/240
MiCOM C264
Define the authorized schemes that follow during the configuration phase. The synchrocheck
function operates for these schemes:
Operator
manual closure
Operator
Synchrocheck
closure
Auto-recloser
7.2.21
7.2.22
Network frequency
Reference phase: A, B or C
Nominal voltage
Functional Description
C264/EN FT/C80
MiCOM C264
Page 209/240
7.2.23
LL- locking
DL
LD
DD
Close with
synchro
YES or NO
YES or NO
YES or NO
YES or NO
YES or NO
Manual Close
NOT
POSSIBLE
YES or NO
YES or NO
YES or NO
YES or NO
Automatic Close
request from
auto-recloser
NOT
POSSIBLE
YES or NO
YES or NO
YES or NO
YES or NO
In event of manual override, the close request is allowed and there is no check.
When coupling is configured, locking is mandatory.
In coupling conditions, a manual or automatic close is always refused: LL and locking
conditions not met.
7.2.24
C264/EN FT/C80
Functional Description
Page 210/240
7.2.25
MiCOM C264
Parameter
Label
Range of value
Type
SC type
1 or 2
1 and 2
T2
1 and 2
T3
1 and 2
V> line
1 and 2
V< line
V> busbar
1 and 2
V< busbar
T1
1 and 2
Evect_locking
1 and 2
Minimum frequency
Fmin_locking
Maximum frequency
Fmax_locking
Efreq_locking
Ephase
0 to 90, 1 step
1 and 2
Sfreq_locking
T4
1 and 2
1 and 2
Ta
1 and 2
Evect_coupling
1 and 2
Minimum frequency
Fmin_coupling
Maximum frequency
Fmax_coupling
Efreq_coupling
Ephase
0 to 90, 1 step
Sfreq_coupling
accSfreq_coupling
= Ks (Tk-Ta) where
General
Synchrocheck kind
Voltage control
Locking scheme
Coupling scheme
Ks = 1% fixed
Tk = 0.5s
Ta: see above
Functional Description
MiCOM C264
C264/EN FT/C80
Page 211/240
7.2.26
5% on voltages thresholds
Transient
If you use a DOU, both contacts must be connected on it with same previous constraint.
C264/EN FT/C80
Functional Description
Page 212/240
7.3
MiCOM C264
Circuit breakers
The operating of a switching device is directly related on its nature and its environment. It
can be operated only with respect of certain conditions. These conditions, therefore called
interlocking, are managed in the form of logical equations within the computer.
Moreover, interlocking can be applied on whatever module or whatever control.
Interlocking prohibits an operation that would be ordered by error, in remote control, to a
switching device beyond its standard conditions of operation.
Some equations of substation interlocking also manage the operations of the disconnecting
switches according to topology and by respecting some preset rules: topological interlocking.
The equations of topological interlocking are generated by independent software. This
software takes in account the topology and some predefined rules to provide these
equations
7.3.1
Interlocking: Inputs
Interlocking function can use the following inputs:
7.3.2
Digital inputs from the systems digital input boards, from other system computers,
from protection relays and other IEDs via communication network (single and double
point, digital groups),
Internal indications: for example, system failures, equipment operation modes and so
on.
Limits derived from measured values from the systems analog input boards (CT, VT,
transducers), from other system computers, from protection relays and other IEDs via
communication network.
Interlocking:Outputs
Result of the interlocking equation is transmitted through a system binary output and saved,
locally in RAM, by the function managing interlocking logical equations.
And, a service is available for any task to get the result of the computation.
Thus , the function managing control of sequence uses this service to know whether control
can be executed.
Then, a simple transient binary input can be set if defined in configuration. The same SPS is
used for the commands open and close of a xPC
7.3.3
Interlocking: Control
No control. An equation is computed each time that one of its input changes of state or of
validity.
7.3.4
Interlocking: Behaviour
7.3.4.1
Principle
In computer, a logical interlocking equation is defined as a sum of product (AB+CDE+F for
example).
Functional Description
MiCOM C264
C264/EN FT/C80
Page 213/240
7.3.4.1.1 Introduction
Interlocking function uses as many as two interlocking equations per switching device on
bay-level and on substation-level. During configuration process the definition of the switching
devices can be:
With only one interlocking equation: for example, for opening, closing being not
checked or vice-versa,
With two interlocking equations (for opening and closing). The interlocking equations
can be different but can also be identical.
The equation is composed of Boolean information mainly representing the position of other
switching devices.
The interlocking for a switching device may be composed of substation interlocking
equations and local interlocking equations.
Both interlocking are managed by the computer that controls the switching device.
The local equation is made up of information obtained from its own digital inputs and IEDs
connected to this computer.
Substation interlocking is made up information obtained from its digital inputs and inputs
provided by the communication network from other computers, from bay computers and from
IEDs (protection relays, etc.). Substation interlocking can also be managed by the
topological interlocking function. Refer to Topological interlocking for more details.
7.3.4.1.2 Local interlocking
The local interlocking is done by calculation of a logical equation. You can have as many as
one equation for each switching device and for each direction (open and close). If there is no
equation for a switching device for a direction, the related variable is true.
7.3.4.1.3 Substation interlocking
The substation interlocking analyses the position of all switching devices in the substation
and calculates the substation interlocking equation to authorise control of a switching device
according to the mechanical and electrical capabilities of the switching device. If there is no
equation for a switching device for a direction, the corresponding variable is true.
7.3.4.1.4 Interlocking: Validity of data
The interlocking equation does not only use the value of the information but also the validity
of the information (invalid, ...).
Thus the result, saved in RAM, of a logical equation is only TRUE or FALSE, An Interlocking
equation in the INVALID state will be considered as FALSE .
But, the system binary input also generated can be valid (SET or RESET) or invalid.
C264/EN FT/C80
Functional Description
Page 214/240
MiCOM C264
The evaluation of the result of basic logical function such as NOT, AND or OR is defined as
follows:
NOT
True
False
False
True
Invalid
Invalid
OR
True
False
Invalid
True
True
True
True
False
True
False
Invalid
Invalid
True
Invalid
Invalid
AND
True
False
Invalid
True
True
False
Invalid
False
False
False
False
Invalid
Invalid
False
Invalid
Software tasks
A logical equation is a sum of products. Each product comprises logical data that can be
complemented. Each electrical component has two logical equations at the most, and each
logical equation is associated with one electrical component.
Example of Logical equation: X = A.B + C.D.E
Functional Description
C264/EN FT/C80
MiCOM C264
Page 215/240
OR
(C is in the lower state) AND (D is in the higher state) AND (E is in the lower state)
1 among N BI (SIG)
Measurement (MEAS)
At configuration time, operator has to define the interlocking profile of each data included in
an interlocking equation. It means that operator must select for each state or validity of a
data a logical state: TRUE, FALSE or INVALID.
Interlocking computation
An interlocking equation:
Is computed each time that one of its element changes of quality or state and
Get logical state related to the received state and validity of the data
Send the new state of the system binary input (BI) that represents the result of the
interlock. BI can be: SET, RESET or INVALID
Interlocking consultation
On reception of open or close request, if the logical equation related to with the switching
device exists, the control of sequence function used the service offered by the interlocking
function to get the result of the interlocking associated to the received request.
If result of the interlocking is TRUE, the check is considered as achieved, else request must
be refused and a negative acknowledgement sent to the origin of the request.
Simulation and test of interlocking equations
The interlocking system is checked during the in house test of the substation control system.
Each interlocking equation may be checked by issuing a control to the corresponding
switching device.
For checking the interlocking on site a SIMULATION mode is implemented in the computer.
In this operating mode, a valid control is sent to the output, but closing the contact is not
performed and a positive acknowledgement message is generated.
7.3.4.3
C264/EN FT/C80
Functional Description
Page 216/240
7.4
MiCOM C264
Edit
Generate code
Simulate
Debug
Project management.
The software logic package supports standard programming languages of the IEC 1131-3:
For action and transition description, you can use this language with Function Block Diagram
(FBD), Ladder Diagram (LD) or Instruction List (IL).
Structured Text, ST
The logic development workbench generates code. The code is uploaded to the computer
target system that operates the code.
Control logic
application
code
Target
hardware
C0019ENb
Functional Description
C264/EN FT/C80
MiCOM C264
7.4.1
Page 217/240
Inputs
All the datapoints of the C264 can be used as an input of a PLC.
7.4.1.1
7.4.1.2
MEAS
CT
CO
NOTE:
7.4.1.3
Acknowledgement of control
A PLC function can manage a control sequence:
7.4.2
Send control
Outputs
A PLC function can:
7.4.3
Generate a BI, for example. PLC is considered as source of acquisition of the data
point
Generate an MEAS
Generate a CT
Generate an SPI
Generate an SIG
Control
Automations can be triggered:
By operator request,
C264/EN FT/C80
Functional Description
Page 218/240
7.4.4
MiCOM C264
Behaviour
The computer has a software execution engine that interprets the automation application
code as shown in the cycle that follows:
Read inputs
Execute programs
Write outputs
C0345ENa
The cycle duration depends on the number of I/O to be scanned and the complexity of the
operations to be performed. Set the cycle during the configuration process.
7.4.4.1
7.4.5
The two different time cycles of a PLC-program can be set from 10 ms up to several
seconds. For some specific equations a cycle less or equal to 10ms and a cycle less
or equal to 100ms for the other logic equations. The time cycle for the automatic
functions shall be less than 100ms.
Routing of the automatism applications to the memory must be in agreement with the
memory and hardware design.
To debug the applications, you can connect a PC to the front face. The hardware
design separates the debug function and the application download function.
Functional Description
C264/EN FT/C80
MiCOM C264
7.5
Page 219/240
"bistable" functions
The equations management rules described for interlocking equations apply on PSL.
Digital outputs used as outputs are mandatory local hardwired DO directly managed by the
computer.
I1
&
DO1
setting
&
DO2
setting
I2
&
1
1
BI1
setting
I3
I4
1
C0140ENa
C264/EN FT/C80
Functional Description
Page 220/240
7.6
MiCOM C264
7.6.1
C264M
The C264M supports:
7.6.2
The ISAGRAF automation that allows you to define the FLS preselections
Automations (ISAGRAF and/or PSL) that allow you to test or simulate the FLS.
C264Fi
As many as 48 C264Fi (feeder) computers support the FLS Function. You can create as
many as 300 output breaker commands.
7.7
List2
f2< control
List3
f3< control
List4
f4< control
LS On/Off control
Blocking condition x
setting
GROUP 1
GROUP 2
blocking condition
information
GROUP 4
LS CB x failed
CBx status
List x Status
Inter-group delay
CBx control
time-out
GROUP 3
LS On/Off Status
LS Group x status
LS CB x rejected by
blocking condition
LS CB x completed
LOAD SHEDDING
Blocking condition
x status
CBx open control
Database (.adb)
C0293ENa
NOTE: The Load Shedding function is available only on the C264 Standalone.
7.7.1
Inputs
f1<, f2<, f3<, f4<: digital inputs, coming from frequency relay. Each input is a
frequency threshold and is associated to a group.
List1, List2, List3, List4 control: each list input is a set of three setpoints associated
to a group. These setpoints give the list of Circuit Breaker attached to a group. They
can be only received from the SCADA interface. ASDU 48 (setpoint normalised value)
is used for these setpoints.
LS On/Off Control: control (DPC type) that allows you to set On or Off the Load
Shedding automation. This control can be received from the SCADA interface or from
the C264 local HMI.
Blocking condition x setting (1x6): each blocking condition setting is a set of three
setpoints. These setpoints give the list of Circuit Breaker blocked by the condition x. It
can be only received from the SCADA interface. ASDU 48 (setpoint normalised value)
is used for these setpoints.
Blocking condition data: digital inputs that blocks the CB trip is set, according to the
CBx blocking condition setting. A maximum of 6 SPS / DPS can be defined as
blocking condition information.
CBx status: status of each circuit breaker (Feedback of the CBx control).
Functional Description
C264/EN FT/C80
MiCOM C264
7.7.2
Page 221/240
Inter-group delay: delay between each group when several group are activated: that
is, when CB of a group have to be tripped. This delay is defined in configuration and
settable through a setpoint (ASDU 48) that can be only received from the SCADA
interface. The delay is stored in flash memory, but set to the value defined in
configuration in event of database switch.
CBx control time-out: one time-out per circuit breaker. For a circuit breaker, this timeout defines the authorized delay between the CB control activation and the CB
position change. These time-out are defined in configuration thru PACiS SCE as
the CB controls Feedback time-out.
Algorithm
Group definition
At configuration time (with PACiS SCE), the operator defines the list of CB attached to each
Load Shedding group. The minimum number of CB in a group is 0, the maximum number is
40. No more than 40 CB can be defined for the whole automation. The 40 CB that you can
use in the load shedding function are tagged in configuration with a number from 1 to 40.
When the database is downloaded and switched, the load shedding automation considers
the data described in the database (last setting sent by the SCADA is lost). The Listx status
information is updated and sent to the SCADA.
The assignment of CB to the groups is performed on-line through the SCADA interface,
whatever was the status of the automation (On or Off). Three setpoints are defined per
group, each value combination gives the allocation of a CB to the group as defined in the
table below:
Breaker Number /
setpoint 1
15
14
13
12
11
10
Breaker Number /
setpoint 2
30
29
28
27
26
25
24
23
22
21
20
19
18
17
16
Breaker Number /
setpoint 3
40
39
38
37
36
35
34
33
32
31
Bit
16
15
14
13
12
11
10
16384
8192
4096
2048
1024
512
256
128
64
32
16
Value
C264/EN FT/C80
Functional Description
Page 222/240
MiCOM C264
Blocking conditions
You can define as many as 6 SPS / DPS as blocking condition: they are numbered from 1 to 6.
At configuration time (with PACiS SCE), the operator defines the list of blocking conditions
activated for each Circuit Breaker.
When the database is downloaded and switched, the load shedding automation takes into
account information described in the database (last setting sent by the SCADA is lost).
The use of blocking condition is also performed through the SCADA interface, whatever was
the status of the automation (On or Off). Three setpoints are defined on a per blocking
condition basis; each value combination gives the association between the CB and the
blocking condition (refer to the table of group definition).
The usage of blocking conditions is saved in flash memory and restored after a computer
reboot. It is erased in event of database switch.
After assignment, the Blocking condition x status information for blocking condition(s) that
has(have) been modified is sent to the SCADA.
Automation
The automation is activated only if it is On. The On / Off control (DPC) is performed through
the SCADA interface or the computer local HMI. The automation status is provided through a
DPS.
As soon as a fx< SPS is detected in a SET state, the CB belonging to the group x are
tripped, with the following constraints:
The order to trip the first CB will be sent in less than 100ms after the fx< detection
whatever was the number of CB in the group
If the group contains as many as 20 CB, the order to trip the 20th CB will be sent in
less than 500 ms after the fx< detection
If the group contains as many as 40 CB, the order to trip the 20th CB will be sent in
less than 500 ms after the fx< detection and the order to trip the last CB will be sent in
less than 1 second after the fx< detection
No other information than the blocking condition can prevent the CB trip, such as
interlocking, control uniqueness, bad CB state (already open, jammed, and so on.)
NOTE:
Any invalid state of the fx< SPS (Selfcheck faulty, toggling) will be not taken into account to
trig the automation.
In event of simultaneous fx< detection: that is, multiple fx< detection with the same time tag,
the groups will be activated in the order of trigger detection:
If the inter-group delay is null, the time constraints given above will be respected
for each group ;
If the inter-group delay is not null, all CB of one group will be tripped before
beginning to trip all CB of the following group.
In event of multiple fx< detection: that is, fx detection during activation of an other group, the
groups will be activated in the order of trigger detection. So, all CB of the first group will be
tripped before beginning to trip all CB of the following group.
Functional Description
C264/EN FT/C80
MiCOM C264
7.7.3
7.7.4
Page 223/240
Outputs
LS Group x status (SPS permanent type, 1x4): set as soon as a group is activated:
that is, the fx< input is set and automation status is On. Reset when the last CB
control has been performed, whatever was the control result
LS CB x rejected for blocking condition (SPS transient type, 1x40): one information
on a per circuit breaker basis. Set during 100 ms if the control is refused due to a
blocking condition
LS CB x failed (SPS transient type, 1x40): one information on a per circuit breaker
basis. Set during 100 ms if the CB is not opened at the end of the control time-out
Blocking condition x Status (1x6): list of CBs for which the blocking condition is set,
transmitted to the SCADA through an analogue value (ASDU 09 or 10)
All DOU or CCU boards used for CB controls must be in the same rack
All configurable information used for Load Shedding function are configured using the
PACiS SCE
There is no way to visualise / modify the settings from the computer local HMI or from
the CAT
LS function can be set On or Off from the SCADA interface. The SCADA sends
this order to only one main 1 rack. The order must be automatically transmitted to
other main 1 racks.
All settings defined on a main 1 rack are also automatically transmitted to other
main 1 racks.
[settings = Inter-group delay; List of Circuit Breaker attached to each group; List of
Circuit Breaker blocked by each blocking condition]
In event of a group activation (fx< goes in Set state), the LS automation operates
in parallel on all front-end main racks.
The LS On/Off state is saved in non volatile memory. This data is erased only
when the computer boots with a DB without LS (so, this information is kept on DB
switch).
Management of Settings
LS setting are saved in non volatile memory. These information are erased on DB
switch.
After a computer reboot, if saved LS settings are found these settings are used,
otherwise settings given by the DB are used.
C264/EN FT/C80
Functional Description
Page 224/240
7.7.5
MiCOM C264
Configurable data
Attribute
Default
Value
Range
Provided
through
S9R file
Comments
100 millisecond
from 0 to
9999ms
Yes
Group assignment
[0..4]
Yes
0 = no assignment to a group
Breaker number
[0..40]
Yes
control time-out
600 ms
[0..6000000]
Yes
Blocking condition n 1
No
Yes / No
Yes
Blocking condition n 2
No
Yes / No
Yes
Blocking condition n 3
No
Yes / No
Yes
Blocking condition n 4
No
Yes / No
Yes
Blocking condition n 5
No
Yes / No
Yes
Blocking condition n 6
No
Yes / No
Yes
Blocking condition
number
[0..6]
Yes
Blocking state
On
On / Off
Yes
Furthermore, all datapoints described above are configured using the PACiS SCE and must
be provided by the S9R file.
Functional Description
C264/EN FT/C80
MiCOM C264
7.8
Page 225/240
List3
List4
control
control
G3
G4
activation
activation
LC On/Off control
Blocking condition x
setting
GROUP 1
GROUP 2
GROUP 3
GROUP 4
blocking condition
information
LC CB x failed
List x Status
CBx status
CBx control
time-out
LC On/Off Status
LC Group x status
LC CB x rejected by
blocking condition
LC CB x completed
LOAD CURTAILMENT
Blocking condition
x status
CBx open control
Database (.adb)
7.8.1
7.8.2
C0294ENa
Inputs
List1, List2, List3, List4 control: each list input is a set of two setpoints associated to
a group. These setpoints give the list of Circuit Breaker attached to a group. They can
be only received from the SCADA interface. ASDU 48 (setpoint normalised value) is
used for these setpoints.
Gx activation: SPC, for each group, that allows you to activate the Load Curtailment
function for the Group x when a SET control is received (the RESET control has no
effect).
LC On/Off Control: control (DPC type) that allows you to set On or Off the Load
Curtailment automation. This control can be received from the SCADA interface or
from the C264 local HMI.
Blocking condition information: digital inputs that block the CB trip is set, according to
the CBx blocking condition setting. A maximum of 6 SPS / DPS can be defined as
blocking condition information.
CBx status: status of each circuit breaker (Feedback of the CBx control).
CBx control time-out: one time-out per circuit breaker. For a circuit breaker, this timeout defines the authorized delay between the CB control activation and the CB
position change. These time-outs are defined in configuration thru PACiS SCE as
the CB controls Feedback time-out.
Algorithm
Group definition
At configuration time (with PACiS SCE), the operator defines the list of CB attached to each
Load Curtailment group. The minimum number of CB in a group is 0, the maximum number
is 5. No more than 20 CB can be defined for the whole automation. The 20 CB that can be
used in load curtailment function are tagged in configuration with a number from 1 to 20.
When the database is downloaded and switched, the load curtailment automation takes into
account information described in the database (last setting sent by the SCADA is lost). The
Listx status information is updated and sent to the SCADA.
C264/EN FT/C80
Functional Description
Page 226/240
MiCOM C264
The assignment of CB to the groups is performed on-line through the SCADA interface,
whatever was the status of the automation (On or Off). Two setpoints are defined per group,
each value combination gives the allocation of a CB to the group as defined in the table
below:
Breaker Number /
setpoint 1
15
14
13
12
11
10
Breaker Number /
setpoint 2
20
19
18
17
16
Bit
16
15
14
13
12
11
10
16384
8192
4096
2048
1024
512
256
128
64
32
16
Value
In event of multiple reception of Gx Activation controls, the groups will be activated in the
order of control reception. So the CB of one group will be tripped before beginning to trip the
CB of an other group. In this event, the time to trip the CB of the other(s) group(s) can be
more then 300ms.
Functional Description
MiCOM C264
7.8.3
7.8.4
C264/EN FT/C80
Page 227/240
Outputs
LC Group x status (SPS permanent type, 1x4): set as soon as a group is activated:
that is, one Gx Activation control received and automation status is On. Reset when
the last CB control has been performed, whatever was the control result
LC CB x rejected for blocking condition (SPS transient type, 1x20): one information
on a per circuit breaker basis. Set during 100 ms if the control is refused due to a
blocking condition
LC CB x failed (SPS transient type, 1x20): one information on a per circuit breaker
basis. Set during 100 ms if the CB is not opened at the end of the control time-out
Blocking condition x Status (1x6): list of CBs for which the blocking condition is set,
transmitted to the SCADA through an analogue value (ASDU 09 or 10)
All DOU or CCU board used for CB controls must be in the same rack
All configurable information used for Load Curtailment function are configured using
the PACiS SCE
C264/EN FT/C80
Functional Description
Page 228/240
7.8.5
MiCOM C264
Configurable data
Attribute
Default
Value
Range
Provided
through
S9R file
Comments
Group assignment
[0..4]
Yes
0 = no assignment to a group
Breaker number
[0..20]
Yes
control time-out
600 ms
[0..6000000]
Yes
Blocking condition n 1
No
Yes / No
Yes
Blocking condition n 2
No
Yes / No
Yes
Blocking condition n 3
No
Yes / No
Yes
Blocking condition n 4
No
Yes / No
Yes
Blocking condition n 5
No
Yes / No
Yes
Blocking condition n 6
No
Yes / No
Yes
Blocking condition
number
[0..6]
Yes
Blocking state
On
On / Off
Yes
Circuit Breaker
Furthermore, all datapoints described above are configured using the PACiS SCE and must
be provided by the S9R file.
Functional Description
MiCOM C264
8.
USER INTERFACE
Please refer to the chapter Human Interface (HI).
C264/EN FT/C80
Page 229/240
C264/EN FT/C80
Functional Description
Page 230/240
9.
MiCOM C264
RECORDS
Several kinds of records are stored in the C264.
9.1
9.1.1
Data storage
All parameters or settings that can be modified via front face LCD are stored in flash disk.
Lists of system information are also stored in the flash disk.
9.1.2
9.1.3
Fast Waveform recording that gives access to samples. This record is useful for
transient electrical events.
Slow scan triggered recording (SST) referred to as Slow Waveform recording that
gives access to RMS values. This record is useful to define load profile or power
regulation.
Events
All data change or events declared in the C264 configuration database To be logged are
stored in a circular queue.
The event records are available for viewing either via the front panel LCD, via slave protocol
at SCADA level or on CAT equipment. They also can be printed.
Events, following the C264 configuration, may typically contain the C264 description, the
date of the event and the time of the event with an accuracy of 1 ms, plus specific
information regarding the causes of the events.
The C264 under the following circumstances may create events:
Alarm acknowledgement.
Functional Description
C264/EN FT/C80
MiCOM C264
9.1.4
Page 231/240
CT:
as many as
VT:
as many as
DSP
DSPIO
Digital
Inputs and
Outputs
Analogue
Inputs and
Outputs
TMU200
DSP
NO
NO
YES
TMU210
NO
DSPIO
YES
YES
TMU220
DSP
NO
NO
YES
You can capture as many as 128 digital channels. The choice of selected inputs/outputs is
defined in configuration.
The waveform recorder provides as many as 8 analogue measurements and as many as
128 digital channels for extraction by a remote device.
A maximum of 480 cycles ( 9,6 seconds at 50 Hz) of measurements samples, with 32
samples per cycle, can be stored, divided in 1, 2, 4 or 8 files saved in flash disk.
A timer channel is also required to provide accurate timing information for each sample. The
delay between each sample is assumed constant over a single cycle.
Number of Files
Number of cycles
60
120
240
480
The waveform recorder can be triggered by the following events, each of which is user
configurable:
Changes in state of binary inputs (SP, DP, MP, SI or Groups). Fast Waveform
Recorder is triggered by the valid change in state of events (like SPS ->SET /RESET,
DPS -> OPEN >CLOSE). It changes the only with VALID quality (ex SET/RESET;
OPEN/CLOSE) to a state/value with VALID Quality
Operator request
Only one re-trig is allowed: it means that a new trigger can only be accepted after the end of
recording of the current waveform.
Waveform records are available in COMTRADE 2001 format.
NOTE:
9.1.5
Digital inputs
Digital outputs
C264/EN FT/C80
Functional Description
Page 232/240
MiCOM C264
Active Power
Reactive Power
Apparent Power
Frequency
Harmonics levels
5000
2500
1000
10
500
20
250
50
100
Changes in state of binary inputs (SP, DP, MP, SI or Groups). Slow Waveform
Recorder is triggered by the valid change in state of events (like SPS ->SET/RESET,
DPS -> OPEN >CLOSE). It changes the only with VALID quality (ex SET/RESET;
OPEN/CLOSE) to a state/value with VALID Quality
Operator request
Functional Description
C264/EN FT/C80
MiCOM C264
9.1.6
Page 233/240
4) The measurements issued from analogue inputs boards are processed as follows:
If the integration period is less or equal to 1 second, the recorded value is the
current measurement value
TMi
i =1 N
Record =
Disturbance Recorder
The PPC sends a command, referred to as a trigger, to the DSP to start a disturbance
recorder.
The DSP stores in a buffer 32 samples by period of the 8 analogue channels according to
the configuration:
- pre time
- total time
PPC convert this buffer in fast wave form adding binary inputs/output defined in
configuration.
trigger
pre
time
post time
total time
The maximum length of a disturbance buffer from the DSP is: 2 * total time.
One record contains at least one trigger and maximum 2 trigger.
If a second trigger appears during the post time of the first trigger, only one record is
generated.
C264/EN FT/C80
Functional Description
Page 234/240
MiCOM C264
2 trigger
1 trigger
pre
time
pre
time
If a second trigger appears after the post time of the first trigger, a second record is
generated.
2 trigger
1 trigger
pre
time
pre
time
post time
post time
post time
1 disturbance
buffer
pre
time
2 disturbance
buffer
C0491ENa
If a third trigger appears, it is ignored if the previous buffer are not downloaded by the PPC.
Functional Description
MiCOM C264
9.2
9.2.1
Alarms
9.2.1.1
Definitions
C264/EN FT/C80
Page 235/240
Each Binary Input (SP, DP, MP, SI, IED input, Groups) state related to the reason for
change of these events
Each Measurement state related to the reason for change of these events
Each TPI state or value related to the reason for change of these events
Each metering state related to the reason for change of these events
.For example, the OPEN state of a circuit breaker can be un-alarmed if the change is due to
a control, and alarmed if the change is due to an other reason.
An alarm can be related to a control acknowledgement. In this event, the alarm is considered
as spurious.
9.2.1.1.3 Alarm states definition
An alarm is generated by an event: for example, a particular datapoint in a state defined
during the configuration phase as to be alarmed.
While this event is still present: for example, the previous particular datapoint is still in the
same state, the alarm is active.
When this event disappears: for example, the previous particular datapoint is now in another
not alarmed state; the previous alarm is inactive.
An existing alarm (active or inactive), can be acknowledged by an operator from the FP.
An alarm can have the following states:
Active-acknowledged: the cause is still present but the active state has been taken
into account by the operator
Active-unacknowledged: the cause is still present and the active state has not been
taken into account by the operator
Inactive-unacknowledged: the cause has disappeared but the inactive state has not
been taken into account by the operator (only available for events alarmed on
appearance and disappearance)
Inactive-acknowledged: the cause has disappeared and the inactive state has been
taken into account by the operator
C264/EN FT/C80
Functional Description
Page 236/240
MiCOM C264
Immediate or differed:
a differed alarm is displayed only after a user-selectable time delay following its
detection (the event associated with the alarm must remain present during the
delay; if not, the alarm will be not displayed) ; this delay is in the range of 1 to 120
seconds and can be set to particular value for each differed alarm.
Gravity level: this level is defined for each alarm allowing a hierarchical classification
to deal with the urgency of the events; the gravity level value can be: 0, 1, 2, 3, 4 or 5,
5 being the most grave and 0 meaning that there is no gravity level.
Alarm generated:
OR
when the associated event appears AND when it disappears
In this event the differed parameter is taken into account only when event appears;
when event disappears the new state of the alarm is displayed immediately.
manual: the alarm is cleared only on an operator request; this clearing command
is only allowed on inactive-acknowledged alarms.
gravity basis
Functional Description
C264/EN FT/C80
MiCOM C264
9.2.1.2
Page 237/240
Alarm processing
Only one alarm (the last one) associated with a state change of a data is displayed. The
previous one (concerning the data) is replaced by the current one.
According to the previous example, only one from the three alarmed states can be displayed
for the switching device: for example, JAMMED or TOGGLING or OPEN state
(the last one that has appeared).
By configuration, one of the following behaviours is chosen:
Alarm inactive
/ cleared
0
AL+
AL+
AL- (auto)
Alarm activeunacknowledged
AL+
1
ACK
AL+
ALAlarm inactiveactiveunacknowledged
3
Alarm activeacknowledged
2
AL-
ACK
ACK (auto)
Alarm inactiveacknowledged
CLEAR
AL+
C0143ENa
C264/EN FT/C80
Functional Description
Page 238/240
MiCOM C264
Alarm inactive
/ cleared
0
AL+
AL+
AL+
Alarm activeunacknowledged
AL+
1
AL-
AL+
Alarm inactiveactiveunacknowledged
5
ACK
ACK
Alarm inactiveunacknowledged
Alarm activeacknowledged
AL-
3
ACK
ACK (auto)
CLEAR
Alarm inactiveacknowledged
4
AL+
C0144ENa
Transition conditions:
Transition description:
The transition from alarm state "0" to alarm state "1" is crossed when the alarmed event
appears (AL+).
The alarm state transitions "1 1" and "2 1" are crossed when the state of the data
associated with the alarm goes from a state that is flagged to be alarmed with any gravity
level to another state that is also flagged to be alarmed with any gravity level (AL+). In this
event the active alarm stays active but the time tagging of the alarm is changed. The new
alarm time stamp corresponds to the last associated data state change. The alarm becomes
unacknowledged if not already unacknowledged.
Functional Description
MiCOM C264
C264/EN FT/C80
Page 239/240
The alarm state transitions "1 2", "3 4" and 5 3 are crossed on operator
acknowledge action. The time stamp of the alarm is unchanged.
The alarm state transitions "1 3" and 1 5 are crossed when the alarmed event
disappears (AL-). The time stamp of the alarm is modified.
The alarm state transition "2 4" is crossed when the event disappears (AL-) the alarm
being configured to be activated only "on appearance of the event". The time stamp of the
alarm is modified.
The alarm state transition "2 3" is crossed when the event disappears (AL-) the alarm
being configured to be activated "on appearance and disappearance of the event". The time
stamp of the alarm is modified and the alarm will have to be acknowledged again.
The alarm state transitions "3 1", "4 1" and 5 1 are crossed when the previous
alarmed event appears again or when another state that is also flagged to be alarmed with
any gravity level appears (AL+). The alarm becomes active-unacknowledged. The time
stamp of the alarm is modified.
The alarm state transition "2 0" is crossed when the event disappears (AL-) the alarm
being configured to be activated only "on appearance of the event" and to be cleared
automatically. The alarm is suppressed from the alarm list.
The alarm state transition "3 0" is crossed on operator acknowledgement only if the alarm
associated with the event is configured as to be cleared automatically. The alarm is
suppressed from the alarm list.
The alarm state transition "4 0" is crossed on operator clearing action. The alarm is
suppressed from the alarm list.
9.2.1.2.1 Acknowledgement
Acknowledgement of an alarm can be done by two ways:
On operator request: an operator can acknowledge an existing alarm from the front
panel to signify that it has been taken into account.
Globally: at substation level it is possible to use an SPS (named Global alarm ack)
specially dedicated to a global acknowledgement of alarms: When this SPS is set to
the SET state all alarms present in the computer are acknowledged. As long as this
SPS remains in the SET state, any new alarm is inserted in the alarm list with the
ACKLOWLEDGED status.
In addition to the Global Alarm Acknowledgement SPS, a Local Alarm
Acknowledgement SPS can be defined on a per C264 basis: that is, one for each
C264.
This SPS can be wired or managed by an automation. When this SPS is configured in
a C264, the Global Alarm Acknowledgement SPS is no more taken into account by
this C264.
When this SPS is SET, all C264 alarms are immediately acknowledged.
This SPS cannot be transmitted on the Station Bus network: that is, it remains local to
the C264, so it cannot be associated to a remote OI or SCADA - control.
C264/EN FT/C80
Functional Description
Page 240/240
MiCOM C264
9.2.1.2.2 Clearing
Whatever the clearing mode is, the clearing of an alarm is immediately taken into account:
suppression from the alarm list.
Automatic clearing
An alarm can be configured as to be cleared automatically. It means that when this alarm
reaches the appropriate state, it is cleared automatically without any operator action. The
events of automatic clearing are:
the alarm is in the active-acknowledged state and the alarm disappears (for event
alarmed on appearance only)
Hardware
C264/EN HW/C80
MiCOM C264/C264C
HARDWARE
Hardware
MiCOM C264/C264C
C264/EN HW/C80
Page 1/44
CONTENT
1.
2.
HARDWARE DESCRIPTION
2.1
Components
2.1.1
Hardware Overview
2.2
Rack styles
2.2.1
MiCOM C264C
2.2.2
MiCOM C264
10
2.3
13
2.4
Modules description
14
2.4.1
14
2.4.2
16
2.4.3
19
2.4.4
20
2.4.5
DSPIO board
21
2.4.6
22
2.4.7
23
2.4.8
25
2.4.9
26
2.4.10
27
2.4.11
29
2.4.12
30
2.4.13
31
2.4.14
32
2.4.15
33
2.4.16
34
2.4.17
35
2.4.18
36
2.4.19
38
2.4.20
42
2.4.21
43
C264/EN HW/C80
Hardware
Page 2/44
MiCOM C264/C264C
BLANK PAGE
Hardware
MiCOM C264/C264C
1.
C264/EN HW/C80
Page 3/44
C264/EN HW/C80
Page 4/44
Hardware
MiCOM C264/C264C
2.
HARDWARE DESCRIPTION
2.1
Components
The MiCOM C264/C264C is based on a modular and scalable architecture to support
dedicated hardware modules adapted to the plant data interfaces.
Each MiCOM C264/C264C rack can be equipped with the following modules:
BIU241: Basic Interface Unit. This board includes the auxiliary power supply
converter, the watchdog relay, 2 digital outputs/2 digital inputs for C264 redundancy
and 2 isolated RS485/RS232 interfaces
BIU 261: Basic Interface Unit. This board includes the dual source power supply for
C264 power supply redundancy, the watchdog relay, 2 digital outputs/2 digital inputs
for C264 redundancy and 1 isolated RS232/RS422RS485 interfaces
CPU260 (also named CPU2) or CPU270 (also named CPU3): Central Processing
Unit and communications board based on PowerPC processor
CCU200: Circuit breaker Control Unit each with 8 digital inputs and 4 digital outputs
CCU211: Circuit breaker Control Unit each with 8 digital inputs and 4 digital outputs
(versions are jumper-selected)
DIU210: Digital Inputs Unit each with 16 digital inputs for voltages from 24 to 220Vdc
DIU211: Digital Inputs Unit each with 16 digital inputs for voltages from 24 to 220Vdc
(versions are jumper-selected)
AIU201: Analogue Input Unit each with 4 analogue inputs direct current or voltage
AIU211: Analogue Input Unit each with 8 analogue inputs direct current
SWU20x: Ethernet SWitch Unit board with 4 electrical links and x= 0 or x=2 optical
links
SWR2xx: Ethernet SWitch board for Redundant Ethernet ring with 4 electrical links
and 2 optical links for the Dual ring.
SWD2xx: Ethernet SWitch board for Dual Homing Ethernet star, with 4 electrical links
and 2 optical links for a Dual star.
ECU200: Extended Communication Unit board to convert non isolated RS232 into
optical signal
ECU201: Extended Communication Unit board to convert non isolated RS232 into
isolated RS485 signal
GHU201 (for C264) or GHU200 (for C264C): Graphical Human machine interface
Unit: Front Panel including 17 LEDs (13 are user-configurable) + 7 pushbuttons (L/R,
Open, Close, etc) + LCD (resolution of 128 x 128 pixels /16 lines of 21 characters
each) and a keypad at the front plate for local HMI management
Hardware
C264/EN HW/C80
MiCOM C264/C264C
2.1.1
Page 5/44
GHU211 (for C264) or GHU210 (for C264C): Front Panel including 17 LEDs (12 are
user-configurable) + 1 pushbutton (L/R)
GHU221 (for C264) or GHU220 (for C264C): Front Face used to connect a
detachable HMI (GHU20x or GHU21x)
Hardware Overview
FBP28x
or FBP24x
BIU 241/261
(1)
Watchdog
Redundancy
COM 1 / COM 2
Power Supply
Electrical link (CPU270)
CPU 260/270
(1)
Ethernet
COM 1 / COM 2
DSP200 for
CPU260
IRIG -B
RS 232
ECU20x
RS 232
ECU20x
RS 485
RS 422
Optical
GHU200/201
OR
GHU210/211
OR
GHU220/221
SWU20x
(up to 1)
GHU20X/21X
Optical 1 / Optical 2
Electrical 1 to 4
SWR 2xx/SWD2xx
(up to 1)
Optical 1 / Optical 2
Mandatory
Optional
Electrical 1 to 4
AIU2x1
(up to 6)
DOU200/201
(up to 15)
10 digital outputs
CCU 200/211
(up to 15)
8 digital intputs
4 digital outputs
DIU200 /DIU21X
(up to 15)
AOU 200
16 digital inputs
4 analogue outputs
(up to 4)
TMU2xx
(up to 1)
4 current intputs
4/5 voltage inputs
C0117
ENh
C264/EN HW/C80
Hardware
Page 6/44
2.2
MiCOM C264/C264C
Rack styles
The mechanical rack is 4 U high.
Two styles are available:
2.2.1
MiCOM C264C
2.2.1.1
Overview
Dimensions of this rack are in the figure below:
Metallic case
Hardware
C264/EN HW/C80
MiCOM C264/C264C
Page 7/44
Front Panels
2.2.1.2.1 GHU200
The GHU200 is the front panel with LCD and LEDs used for the MiCOM C264C:
a keypad at the front plate for local HMI management with 5 pushbuttons
C264/EN HW/C80
Hardware
Page 8/44
MiCOM C264/C264C
2.2.1.2.2 GHU210
The GHU210 is the front panel with LEDs used for the MiCOM C264C:
1 pushbutton (L/R)
Hardware
C264/EN HW/C80
MiCOM C264/C264C
2.2.1.3
Page 9/44
Sockets
The FBP242 board is the front backplane of MiCOM C264C equipped with the CPU260.
FIGURE 8: MiCOM C264C REAR PANEL EQUIPPED WITH A CT/VT BOARD (TMU2XX)
The FBP243 board is the front backplane of the MiCOM C264C equipped with the CPU270:
FIGURE 10: MiCOM C264C REAR PANEL OVERVIEW WITHOUT CT/VT BOARD
C264/EN HW/C80
Hardware
Page 10/44
MiCOM C264/C264C
2.2.2
MiCOM C264
2.2.2.1
Overview
Dimensions of this rack are in the figure below:
Front Panel degree of protection: IP52 (for front panel with LEds or LCD)
Metallic case
Hardware
C264/EN HW/C80
MiCOM C264/C264C
2.2.2.2
Page 11/44
Front Panels
2.2.2.2.1 GHU201
The GHU201 is the front panel with LCD and LEDs used for the MiCOM C264:
a keypad at the front plate for local HMI management with 5 pushbuttons
1 pushbutton (L/R)
C264/EN HW/C80
Hardware
Page 12/44
2.2.2.3
MiCOM C264/C264C
Sockets
The FBP28X board is the front backplane of MiCOM C264C equipped with the CPU260.
FIGURE 17: MiCOM C264 REAR PANEL EQUIPPED WITH A CT/VT CONNECTOR
The FBP283 board is the front backplane of the MiCOM C264 equipped with the CPU270.
FIGURE 19: MiCOM C264 REAR PANEL OVERVIEW WITHOUT CT/VT CONNECTOR
Hardware
C264/EN HW/C80
MiCOM C264/C264C
2.3
Page 13/44
Jumper
missing => 1
present => 0
Example:
0
2
0
8
1
0
0
0
address
=1
address
= 10
C0030ENa
NOTE:
Two boards of the same type must not have the same address
C264/EN HW/C80
Hardware
Page 14/44
MiCOM C264/C264C
2.4
Modules description
2.4.1
Hardware
C264/EN HW/C80
MiCOM C264/C264C
Page 15/44
C0033ENa
Configuration:
The hardware jumpers arrangement is as follow.
2.4.1.2
In RS232 set the jumpers S14, S16 and between S12.1 and S12.3
In RS485 set the jumpers S13, S15 and between S12.1 and S12.2. It is possible to
end the line with a 124 resistor by setting S17. (See CO chapter to know when the
resistor has to be used).
Configuration:
The hardware jumpers arrangement is as follow.
In RS485 set the jumpers S7, S8, S2. It is possible to end the line with a 124
resistor by setting S11. (See CO chapter to know when the resistor has to be used).
In RS422 set the jumpers S7, S8, S4 and S2. It is possible to end the line with a 124
resistor by setting the jumpers S10 and S11. (See CO chapter to know when the
resistor has to be used).
C264/EN HW/C80
Hardware
Page 16/44
2.4.2
MiCOM C264/C264C
Supply C264 from two power supplies (main and secondary) of the same range.
This following figure locates the serial link configuration jumpers (S2 to S9)
Hardware
C264/EN HW/C80
MiCOM C264/C264C
Page 17/44
S6
S7
S3
S8
S2
S9
S4
S5
C264/EN HW/C80
Hardware
Page 18/44
2.4.2.1
MiCOM C264/C264C
Jumper
RS232
RS422
RS485
Note
Hardware
C264/EN HW/C80
MiCOM C264/C264C
2.4.3
Page 19/44
Two non isolated RS232 links. The transmission rate must be the same on both links
(values from 50 to 56000 bps configurable with the configuration tool or settable via
GHU20x)
An IRIG-B input
The board is interfaced with all I/O boards and the front panel.
CPU260 has the following key features:
Calendar saved
C264/EN HW/C80
Hardware
Page 20/44
2.4.4
MiCOM C264/C264C
Two non isolated RS232 links. The transmission rate must be the same on both links
(values from 50 to 56000 bps configurable with the configuration tool or settable via
GHU20x)
An IRIG-B input
This board is interfaced with all I/O boards and the front panel.
CPU270 has the following key features:
Calendar saved
Hardware
C264/EN HW/C80
MiCOM C264/C264C
2.4.5
Page 21/44
DSPIO board
The DSPIO board is carried by the CPU260/270 board. It is used in conjunction with the
TMU210 board.
C264/EN HW/C80
Hardware
Page 22/44
2.4.6
MiCOM C264/C264C
The digital inputs can be configured in single or double remote signalling inputs on the same
module.
The digital output (DO) capabilities of the CCU200 boards are:
A self-monitoring device for the output control chain is provided (address check, state
monitoring)
The +5V voltage is monitored to avoid issuing uncommanded events.
The digital outputs can be configured in double remote signalling only.
Hardware
C264/EN HW/C80
MiCOM C264/C264C
2.4.7
Page 23/44
The digital inputs can be used for single or double remote signalling, pulse or digital
measurement input on the same module.
The input responds to negative input voltages and they are not self controlled
All voltages between 24V and 220V DC selected using jumpers (with CPU3)
J2 connector:
J2-4
J2-3
J2- 2
J2-1
Only one jumper is to be installed on J2 connector.
Version
A01
No
J2-1
A02
No
J2-2
A03
No
J2-3
A04- A07
No
J2-4
A08
Yes
J2-4
C264/EN HW/C80
Page 24/44
Hardware
MiCOM C264/C264C
From 24V to 220VDC: a peak current (> 27mA) circulates during a short time ( 2 ms)
to clean external contacts:
A self-monitoring device for the output control chain is provided (address check, state
monitoring).
The +5V voltage is monitored to avoid issuing uncommanded events.
The digital outputs can be configured in double remote signalling only.
For use with CPU 2 board, the address of the board is selected using a four-position
header and jumper.
For use with CPU 3 board, the address of the board can be defined by the location of
the CCU211 in the C264 rack (or by jumper if the board is used as spare of a previous
board). This location is defined using the SCE.
Hardware
C264/EN HW/C80
MiCOM C264/C264C
2.4.8
Page 25/44
The digital inputs can be used for single or double status, pulse or digital
measurement input on the same module.
C264/EN HW/C80
Hardware
Page 26/44
2.4.9
MiCOM C264/C264C
The digital inputs can be used for single or double status, pulse or digital
measurement input on the same module.
From 48V to 220VDC: High current circulation inside binary contacts inputs during a
short time (to clean external contacts): see the current peak response curve
Hardware
C264/EN HW/C80
MiCOM C264/C264C
2.4.10
Page 27/44
The digital inputs can be used for single or double status, pulse or digital
measurement input on the same unit.
J2 connector:
J2-4
J2-3
J2- 2
J2-1
Only one jumper is to be installed on J2 connector.
Version
A01
No
J2-1
A02
No
J2-2
A03
No
J2-3
A04- A07
No
J2-4
A08
Yes
J2-4
C264/EN HW/C80
Page 28/44
Hardware
MiCOM C264/C264C
From 24Vdc to 220Vdc: a peak current (> 27mA) circulates during a short time
( 2 ms) to clean external relays contacts:
Settings: for use with CPU 3 board, the address of the board can be defined by the location
of the DIU211 in the C264 rack (or by jumper if the board is used as spare of a previous
board). This location is defined using the SCE.
Hardware
C264/EN HW/C80
MiCOM C264/C264C
2.4.11
Page 29/44
A self-monitoring device for the output control chain is provided (address check, state
monitoring)
The +5V voltage is monitored to avoid issuing uncommanded events.
The digital outputs can be configured in single or double remote control or set point outputs
on the same module.
C264/EN HW/C80
Hardware
Page 30/44
2.4.12
MiCOM C264/C264C
DOU201 has 8 single pole contacts which are normally open and 2 double pole contacts in
which one pole contact is normally open and one pole contact is normally close.
For use with CPU 2 board, the address of the board is selected using a four-position header
and jumper.
For use with CPU 3 board, the address of the board can be defined by the location of the
DOU201 in the C264 rack (or by jumper if the board is used as spare of a previous board).
This location is defined using the SCE.
Hardware
C264/EN HW/C80
MiCOM C264/C264C
2.4.13
Page 31/44
C264/EN HW/C80
Hardware
Page 32/44
2.4.14
MiCOM C264/C264C
Hardware
C264/EN HW/C80
MiCOM C264/C264C
2.4.15
Page 33/44
for the TMU200 4 measurement Voltage Transformers (4 VT) inputs. For the TMU220
5 measurement Voltage Transformers (5 VT) inputs
Processor
Processor board
TMU200
TMS320C6711
DSP260
TMU220
TMS320C6713
DSP220
C264/EN HW/C80
Hardware
Page 34/44
2.4.16
MiCOM C264/C264C
Each transformer has two AC voltage ranges (VN): 57.73 Vrms to 130 Vrms or
220Vrms to 480 Vrms
Hardware
C264/EN HW/C80
MiCOM C264/C264C
2.4.17
Page 35/44
C264/EN HW/C80
Hardware
Page 36/44
2.4.18
MiCOM C264/C264C
Open
Closed
Factory
setting
W1
No watching port 5
Open
W3
Open
W4
Open
W5
Open
W6
Open
W7
Closed
W8
No priority reserve
Closed
W9
Closed
W10
W11
Closed
W12
Closed
W13
Open
Hardware
C264/EN HW/C80
MiCOM C264/C264C
OPEN
Page 37/44
CLOSE
Port 6
W12
Port 5 (optional)
LED1
LED2
LED3
Port 4
LED4
LED5
Port 3
LED6
W13
W4
W3
Port 2
W5
W6
W8
W9
W11
W7
W10
W1
Port 1
C0118ENa
SWU202 optical links: these 2 optical links are monitored; if one link comes down the default
is announced by the contacts (250V/5A):
Components side
1 2 3
Pin
State
Open
Common
Close
Close if default
C0119ENa
C264/EN HW/C80
Hardware
Page 38/44
2.4.19
MiCOM C264/C264C
Ethernet Switch Unit SWx202/SWx212, SWx204/SWx214 (x=R for dual Ring, x= D for
Dual homing)
These boards include 4 electrical links and 2 optical links for a dual ring/homing.
The SWx21y switches are SNMP-managed.
The SWx202/SWx212 models have a Multi-mode optical interface.
The SWx204/SWx214 models have a Single mode (mono-mode) optical interface.
Hardware
C264/EN HW/C80
MiCOM C264/C264C
Page 39/44
J2
8
9
1
MDC
2
3
11
18
19
20
21
22
C0122ENa
C264/EN HW/C80
Hardware
Page 40/44
MiCOM C264/C264C
SWR200
SWR200
1
SWR200
SWR200
2
Patch
Panel
Patch
Panel
SWR200
SWR200
C0123ENa
Wavelengh:1300nm
62.5/125 m or
50/125 m
9/125 m or 10/125 m
- 19 dBm
- 15 dBm
Sensitivity
- 31 dBm
- 34 dBm
12 dB
19 dB
0.8 dB
0.8 dB
Safety Margin
4 dB
4 dB
6.4 dB
13.4 dB
1 dB/km
0.4 dB/km
Maximum range
6.4 km
33 km
(2)
12 dB
19 dB
Connector loss
(6)
0.8 dB
0.8 dB
Patch loss
(2)
2 dB
1 dB
Safety Margin
4 dB
4 dB
-0.8 dB
8.2 dB
1 dB/km
0.4 dB/km
Maximum range
20 km
The values given above are only approximate ones. Always use cable and connector losses
as specified by the manufacturer.
Hardware
C264/EN HW/C80
MiCOM C264/C264C
Page 41/44
RA
RA
LINK A
LINK A
EA
EA
SWD2xx
SWD2xx
RB
RB
LINK B
LINK B
EB
EB
C0298ENa
RA
RA
LINK A
EA
EA
SWD2xx
SWD2xx
RB
RB
LINK B
LINK B
EB
RE
LINK A
RE
EB
RE RE
Simple Switch Fx
Simple Switch Fx
B
C0299ENb
C264/EN HW/C80
Hardware
Page 42/44
2.4.20
MiCOM C264/C264C
For IEC870-5-103 standard, the circle must be visible (light is sent for the 0 level)
Otherwise the circle must be hidden (light is sent for the 1 level).
Optical characteristics:
Connector type: ST
Wavelength: 820 nm
Hardware
C264/EN HW/C80
MiCOM C264/C264C
2.4.21
Page 43/44
RS422 (4 wires): TA (+), TB(-), RA (+) and RA (-) are used. The circle must be hidden
RS485 (2 wires): only TA (+), TB (-) are used. The circle must be visible
C264/EN HW/C80
Hardware
Page 44/44
MiCOM C264/C264C
BLANK PAGE
Connections
C264/EN CO/C80
MiCOM C264/C264C
CONNECTIONS
Connections
C264/EN CO/C80
MiCOM C264/C264C
Page 1/44
CONTENT
1.
2.
CONNECTOR BLOCKS
2.1
2.2
2.3
2.4
2.5
3.
3.1
Earthing
3.2
Cable fitting
4.
11
4.1
11
4.2
14
4.3
16
4.4
19
4.5
21
4.6
23
4.7
25
4.8
27
4.9
29
4.10
31
4.11
33
4.12
35
4.13
37
4.14
39
4.15
41
4.16
42
4.17
43
4.18
Front panel
44
C264/EN CO/C80
Page 2/44
1.
Connections
MiCOM C264/C264C
Connections
C264/EN CO/C80
MiCOM C264/C264C
Page 3/44
2.
CONNECTOR BLOCKS
2.1
Value
Continuous rating
10 A
Connection method
Screw M3
Cable size
Connection pitch
5,08 mm
Standards
UL, CSA
PIN
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
C0041ENa
C264/EN CO/C80
Connections
Page 4/44
2.2
MiCOM C264/C264C
Value
Continuous rating
10 A
3 second rating
30 A
30 ms rating
250 A
Connection method
Screw M4
Cable size
VT connection
CT connection
Continuous rating
20 A
10 second rating
150 A
1 second rating
500 A
Connection method
Screw M4
Cable size
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
C0042ENa
The connector is fixed to the rack with 4 Phillips screws M4; 2 are
located on the top part and 2 on the bottom part.
Connections
C264/EN CO/C80
MiCOM C264/C264C
2.3
Page 5/44
MiCOM C264
(Slave)
(Slave)
(Slave)
Rear panel
RS485 connector
Relay or IED
Relay or IED
Relay or IED
Rx Tx Gnd
Rx Tx Gnd
Rx Tx Gnd
Rx Tx Gnd
120 Ohms
120 Ohms
Earthing (*)
Earthing
( )
C0043ENb
MiCOM C264
(Slave)
(Slave)
(Slave)
Relay or IED
Relay or IED
Relay or IED
C0044ENa
C264/EN CO/C80
Connections
Page 6/44
MiCOM C264/C264C
MiCOM C264
MiCOM C264
(Slave)
(Slave)
(Slave)
Relay or IED
Relay or IED
Relay or IED
(Slave)
(Slave)
(Slave)
(Slave)
Relay or IED
Relay or IED
Relay or IED
Relay or IED
C0045ENa
2.4
Master (c264)
Slave(IED)
TA(+)
R+
TB(-)
R-
RA(+)
T+
RB(-)
T-
Connections
C264/EN CO/C80
MiCOM C264/C264C
2.5
Page 7/44
C0046ENa
C264/EN CO/C80
Connections
Page 8/44
MiCOM C264/C264C
3.
3.1
Earthing
MiCOM C264/C264C must be connected to the earth according to product safety standard
EN60255-27:2005 clause 5.1.5 using the protective conductor (earth) terminal located on
the rear panel.
Connection of the Protective conductor (earth).
The MiCOM C264/C264C racks must be earthed, for safety reasons, by connection of the
protective conductor (earth) to the M4 threaded stud allocated as the protective conductor
terminal (PCT), marked with the symbol shown.
WARNING
The protective conductor (earth) must be as short as possible with low resistance and
inductance. The best electrical conductivity must be maintained at all times, particularly the
contact resistance of the plated steel stud surface. The resistance between the MiCOM
C264/C264C protective conductor (earth) terminal (PCT) and the protective earth conductor
must be less than 10 m at 12 Volt, 100 Hz.
Cable fitting
It is recommended to use cables (0.8 mm2) as following:
Screened multi-strand cable has to be used for digital input-output signals. For cables
within the cubicle the cable screen can be connected to the earth at both ends of the
cable. If the cable is taken beyond the system cubicle the cable screen should be
earthed at one end only to prevent current flowing in the screen due any differences in
ground potential.
Screened and twisted pair has to be used for analogue input-output signals. The
screen is connected to the earth by the end of Bay Module side.
One or two screened and twisted pairs have to be used for lower communication
signals. The screen is connected to the earth by two cable ends.
It is recommended to group cables and fit them as near as possible to an earth plane or to
an element of an earth wire-mesh.
Connections
C264/EN CO/C80
MiCOM C264/C264C
Page 9/44
Functional earth
Protective
Conductor (earth)
Terminal
C264/EN CO/C80
Connections
Page 10/44
MiCOM C264/C264C
Second example: MiCOM C264/C264C fitted in a metallic cubicle with other devices.
Metallic cubicle
other device
Earth
Functional Earth
Protective Conductor
(earth) Terminal
Protective Conductor
(earth)
Auxiliary power
Protective Conductor
(earth)
Power
connector
Digital
boundary
connector
Analogue
boundary
connector
C0049ENd
Connections
C264/EN CO/C80
MiCOM C264/C264C
Page 11/44
4.
4.1
Port N1
Port N2
RS232
RS232
RS232
RS485
RS422
RS232
RS422
RS485
RS485
RS232
RS485
RS485
Connector description
Pin n
Signal
Redundancy relay 2
- NO contact
Redundancy relay
- common 1-2
Redundancy relay 1
- NO contact
Watchdog relay
- NO contact
Watchdog relay
- NC contact
Watchdog relay
- common
Redundancy input
- 1+
Redundancy input
- common 1 / 2
Redundancy input
- 2+
10
11
12
RS232: RxD
13
RS232: SG (0 V)
14
RS232: TxD
15
RS232: SG (0 V)
- Port 2
16
RS232: CTS
- Port 2
17
RS232: RxD
RS485 B
RS422: TB
- Port 2
18
RS232: TxD
RS485 A
RS422: TA
- Port 2
19
RS232: RTS
RS422: RB
- Port 2
RS422: RA
- Port 2
20
RS485: B
- Port 1
- Port 1
RS485: A
- Port 1
21
RS232: DCD
- Port 2
22
Gnd
23
(+)
24
()
C264/EN CO/C80
Connections
Page 12/44
4.1.2
MiCOM C264/C264C
Block diagram
PIN
Output relays
1
O2
2
3
O1
Watchdog
5
6
7
V IN
DI1
VIN
DI2
9
10
11
12
RXD / TB
13
SG (0 V)
14
TXD / TA
RS232/
RS485
Serial
link 1
#
15
SG (0 V)
16
17
18
19
RS232/
CTS
RS422
RXD / TB RS485
TXD / TA
RTS / RB
RA
20
Serial
link 2
#
DCD
21
22
23
24
V aux
Power
supply
C0050ENf
Connections
C264/EN CO/C80
MiCOM C264/C264C
Page 13/44
RS232:
4.1.3
In this case, the GND signal of the daisy chain extremity is not to be
earthed.
C264_1
BIU Pin
C264_2
BIU Pin
C264_2
Signal
------>
Redundancy input:
2+
(+)
------>
Redundancy input:
Redundancy input:
<------
1+
1+
(-)
Redundancy input:
<------
- 2+
C264/EN CO/C80
Connections
Page 14/44
4.2
MiCOM C264/C264C
Supply C264 from two power supplies (Main and secondary) of the same range.
The factory settled possibilities for the isolated base legacy port are configurated by
hardware jumpers:
Case
Port N2
RS232
RS422
RS485
Connector description
Pin n
Signal
Redundancy relay 2
NO contact
Redundancy relay
common 1-2
Redundancy relay 1
NO contact
Watchdog relay
NO contact
Watchdog relay
NC contact
Watchdog relay
common
Redundancy input
1+
Redundancy input
common 1-2
Redundancy input
2+
10
DC( + )
11
DC( )
12
Not Used
13
Not Used
14
Not Used
15
RS232: SG (0 V)
Port 2
16
RS232: CTS
Port 2
17
Port 2
18
Port 2
19
Port 2
20
RS422: RA
Port 2
21
RS232: DCD
Port 2
22
GND
23
DC( + )
24
DC( )
Connections
C264/EN CO/C80
MiCOM C264/C264C
4.2.2
Page 15/44
Safety recommandations
For safety reasons, with the communication port of board BIU261 connected to devices, it is
mandatory to earth some of the "Signal Ground pin" of the communication port, according
to the following applications.
Interface
Note
Recommandation wiring
RS232
RS485 / RS422
RS485 / RS422
4.2.3
C264_2
BIU Pin
C264_1
BIU Pin
C264_2
Signal
------>
Redundancy input: 2+
(+)
------>
Redundancy input: 1+
Redundancy input:
<------
(-)
<------
1+
2+
C264/EN CO/C80
Connections
Page 16/44
4.3
MiCOM C264/C264C
4.3.1
Block diagram
Connector description
DB9 connectors:
1
CD
RX
TX
SG (0 V)
Not used
RTS
CTS
Not used
Connections
C264/EN CO/C80
MiCOM C264/C264C
Page 17/44
NOTE:
DB 9
5
1
6
5
9
6
C0152ENa
TA (+)
TB (-)
Ground
RA (+)
RB (-)
RS422 (4 wires): TA(+), TB(-), RA(+), RB(-) are used. The circle must be hidden.
RS485 (2 wires): only TA(+) and TB(-) are used. The circle must be visible.
4.3.3
DSPIO board
The Protection Input & Ouputs module is a daughter board of the CPU board dedicated to
the Circuit-breaker Protection feature management. It provides 4 optically isolated digital
inputs (with 1 common for 2DI) and 3 outputs (3 DO with 1 common) using relays.
C264/EN CO/C80
Connections
Page 18/44
MiCOM C264/C264C
Signal
Logic Selectivity
Digital Input
Disturbance start
K4/1 + Output
10
K4/1 Output
11
K4/2 + Output
12
K4/2 Output
13
K3/1 + Output
14
K3/1 Output
15
K3/2 + Output
16
K3/2 Output
17
Not connected
18
Trip phase C
19
Not connected
20
Trip phase B
21
Not connected
22
Trip phase A
23-24
Connections
C264/EN CO/C80
MiCOM C264/C264C
4.4
Page 19/44
4.4.1
Block diagram
Circuit breaker
Control U nit
board
CCU 200
PIN
1
2
Digital Inputs
+
-
VIN
-
DI1
+
-
DI3
+
-
DI5
+
-
DI7
+
-
VIN
-
DI2
3
4
5
+
-
VIN
-
VIN
-
DI4
6
7
8
+
-
VIN
-
VIN
-
DI6
9
10
11
+
-
VIN
-
VIN
-
DI8
12
13
14
15
16
17
Digital Outputs
B
A
A
B
CO 1
CO 2
18
19
20
21
22
23
B
A
A
B
CO 3
CO 4
24
C0058ENa
NOTE:
C264/EN CO/C80
Connections
Page 20/44
4.4.2
MiCOM C264/C264C
Connector description
The CCU2xx board is equipped with a 24-pin 5.08 mm pitch connector.
Pin N.
Signal
Digital Input 1+
Digital Input 2+
Digital Input 3+
Digital Input 4+
Digital Input 5+
Digital Input 6+
10
Digital Input 7+
11
Digital Input 8+
12
13
Digital Output 1 B
14
Digital Output 1 A
15
16
Digital Output 2 A
17
Digital Output 2 B
18
19
Digital Output 3 B
20
Digital Output 3 A
21
22
Digital Output 4 A
23
Digital Output 4 B
24
Connections
C264/EN CO/C80
MiCOM C264/C264C
4.5
Page 21/44
4.5.1
Block diagram
DIU200
Signal inputs
PIN
1
2
+
-
VIN
-
DI1
+
-
DI3
+
-
DI5
+
-
DI7
+
-
VIN
-
DI2
3
4
5
+
-
VIN
-
VIN
-
DI4
6
7
8
+
-
VIN
-
VIN
-
DI6
9
10
11
+
-
VIN
-
VIN
-
DI8
12
13
14
VIN
-
DI9
VIN
-
DI10
15
16
17
VIN
-
DI11
VIN
-
DI12
18
19
20
+
-
VIN
-
DI13
+
-
DI15
+
-
VIN
-
DI14
21
22
23
+
-
VIN
-
VIN
-
DI16
24
C0056ENa
C264/EN CO/C80
Connections
Page 22/44
4.5.2
MiCOM C264/C264C
Connector description
The DIU200 board is equipped with a 24-pin 5.08 mm pitch connector.
Pin N.
Signal
Digital Input 1+
Digital Input 2+
Digital Input 3+
Digital Input 4+
Digital Input 5+
Digital Input 6+
10
Digital Input 7+
11
Digital Input 8+
12
13
Digital Input 9+
14
15
16
17
18
19
20
21
22
23
24
Connections
C264/EN CO/C80
MiCOM C264/C264C
4.6
Page 23/44
4.6.1
Block diagram
There is only one type of DIU210 board, including all wetting voltages
between 24 and 220V AC/DC.
C264/EN CO/C80
Connections
Page 24/44
4.6.2
MiCOM C264/C264C
Connector description
The DIU210 board is equipped with a 24-pin 5.08 mm pitch connector.
Pin N.
Signal
Digital Input 1
Digital Input 2
Digital Input 3
Digital Input 4
Digital Input 5
Digital Input 6
10
Digital Input 7
11
Digital Input 8
12
13
Digital Input 9
14
Digital Input 10
15
16
Digital Input 11
17
Digital Input 12
18
19
Digital Input 13
20
Digital Input 14
21
22
Digital Input 15
23
Digital Input 16
24
Connections
C264/EN CO/C80
MiCOM C264/C264C
4.7
Page 25/44
4.7.1
Block diagram
C264/EN CO/C80
Connections
Page 26/44
4.7.2
MiCOM C264/C264C
Connector description
The DIU211 board is equipped with a standard type of connector with a 24-pin and 5.08mm
pitch.
Pin N.
Signal
Digital Input 1-
Digital Input 2-
Digital Input 3-
Digital Input 4-
Digital Input 5-
Digital Input 6-
10
Digital Input 7-
11
Digital Input 8-
12
13
Digital Input 9-
14
15
16
17
18
19
20
21
22
23
24
NOTE:
Connections
C264/EN CO/C80
MiCOM C264/C264C
4.8
Page 27/44
4.8.1
Block diagram
PIN
DOU200
Signal outputs
1
2
DO 1
3
4
DO 2
5
6
DO 3
7
8
DO 4
9
10
DO 5
11
12
DO 6
13
14
DO 7
15
16
DO 8
17
18
19
20
21
DO 9
22
23
24
DO 10
C0057ENb
C264/EN CO/C80
Connections
Page 28/44
4.8.2
MiCOM C264/C264C
Connector description
The DOU200/201 board is equipped with a 24pin 5.08 mm pitch connector.
Pin N.
Signal
Digital output 1 +
Digital output 1 -
Digital output 2 +
Digital output 2 -
Digital output 3 +
Digital output 3 -
Digital output 4 +
Digital output 4 -
Digital output 5 +
10
Digital output 5 -
11
Digital output 6 +
12
Digital output 6 -
13
Digital output 7 +
14
Digital output 7 -
15
Digital output 8 +
16
Digital output 8 -
17
NC
18
NC
19
20
21
22
23
24
Connections
C264/EN CO/C80
MiCOM C264/C264C
4.9
Page 29/44
Signal inputs
+
AI 1
#
mA
PIN
1
AIU201
AI 1
#
5
6
10
AI 2
#
mA
AI 2
#
11
12
15
16
AI 3
#
mA
14
AI 3
#
17
18
21
22
AI 4
#
mA
20
24
Insulated
GND
GND
19
23
Insulated
GND
GND
13
Insulated
GND
GND
4.9.1
AI 4
#
Insulated
GND
GND
C0059ENb
C264/EN CO/C80
Connections
Page 30/44
4.9.2
MiCOM C264/C264C
Connector description
The AIU201 board is equipped with a 24-pin 5.08 mm pitch connector.
Pin N.
Signal
Insulated Ground 1
Ground
10
11
Insulated Ground 2
12
Ground
13
14
15
16
17
Insulated Ground 3
18
Ground
19
20
21
22
23
Insulated Ground 4
24
Ground
Connections
C264/EN CO/C80
MiCOM C264/C264C
4.10
Page 31/44
4.10.1
Block diagram
C264/EN CO/C80
Connections
Page 32/44
4.10.2
MiCOM C264/C264C
Connector description
The AIU211 board is equipped with a 24-pin 5.08 mm pitch connector.
Pin N.
Signal
Not Connected
Ground
10
11
Not Connected
12
Ground
13
14
15
16
17
Not Connected
18
Ground
19
20
21
22
23
Not Connected
24
Ground
Connections
C264/EN CO/C80
MiCOM C264/C264C
4.11
Page 33/44
4.11.1
Block diagram
Transducerless 1A
Current and Voltage
U nit board
TMU 200
Transducerless
current inputs
PIN
1
Transducerless 5A
Current and Voltage
U nit board
TMU 200
Transducerless
current inputs
PIN
N1
10
11
12
13
14
15
16
17
18
19
20
21
22
N2
N1
3
N2
C1
C2
C1
7
10
11
12
13
14
C2
B1
B2
B1
B2
A1
A2
A1
15
16
17
18
19
20
21
22
A2
Transducerless
voltage inputs
U1
U2
Transducerless
voltage inputs
U1
V1
U2
V1
23
24
V2
W1
23
24
V2
W1
25
26
W2
25
26
W2
27
28
N1
27
28
N2
N1
N2
C0060ENb
C264/EN CO/C80
Connections
Page 34/44
4.11.2
MiCOM C264/C264C
Connector description
The TMU200 board is equipped with a standard MiDOS 28 connector (see Figure 2:
Standard MiDOS 28 connectors).
Pin N.
Signal
Current Input 5A - N1
Current Input 5A N2
Current Input 1A N1
Current Input 1A N2
Current Input 5A C1
Current Input 5A C2
Current Input 1A C1
Current Input 1A C2
Current Input 5A B1
10
Current Input 5A B2
11
Current Input 1A B1
12
Current Input 1A B2
13
Current Input 5A A1
14
Current Input 5A A2
15
Current Input 1A A1
16
Current Input 1A A2
17
NC
18
NC
19
NC
20
NC
21
Voltage Input U1
22
Voltage Input U2
23
Voltage Input V1
24
Voltage Input V2
25
Voltage Input W1
26
Voltage Input W2
27
Voltage Input N1
28
Voltage Input N2
Connections
C264/EN CO/C80
MiCOM C264/C264C
4.12
Page 35/44
4.12.1
Block diagram
C264/EN CO/C80
Connections
Page 36/44
4.12.2
MiCOM C264/C264C
Connector description
The TMU220 board is equipped with a standard MiDOS 28 connector (see Figure 2:
Standard MiDOS 28 connectors).
STAR topology
Measure type in
PACIS
Configurator
DELTA topology
Measure type in
PACIS
Configurator
Wave form:
Related
channel
Ibusbar RMS 1
value of the
busbar current
phase
Ibusbar RMS 1
value of the
busbar current
phase
CI#3
CI#2
CI#1
CI#0
Pin N.
Signal
Electrical
Signal
Current Input 5A - N1
IBusbar1 5A -
Current Input 5A N2
IBusbar1 5A +
Current Input 1A N1
IBusbar1 1A -
Current Input 1A N2
IBusbar1 1A +
Current Input 5A C1
IC 5A -
Current Input 5A C2
IC 5A +
Current Input 1A C1
IC 1A -
Current Input 1A C2
IC 1A +
Current Input 5A B1
IB 5A -
10
Current Input 5A B2
IB 5A +
11
Current Input 1A B1
IB 1A -
12
Current Input 1A B2
IB 1A +
13
Current Input 5A A1
IA 5A -
14
Current Input 5A A2
IA 5A +
15
Current Input 1A A1
IA 1A -
16
Current Input 1A A2
IA 1A +
17
NC
NC
NA
NA
NA
18
NC
NC
NA
NA
NA
19
Voltage Input X1
U Busbar2 -
20
Voltage Input X2
Vbusbar RMS 2
value of the
busbar voltage
phase
Vbusbar RMS 2
value of the
busbar voltage
phase
VI#4
VI#0
VI#1
VI#2
Vbusbar RMS 1
value of the
busbar voltage
phase
Vbusbar RMS 1
value of the
busbar voltage
phase
VI#3
U Busbar2 +
21
Voltage Input U1
UA -
22
Voltage Input U2
UA +
23
Voltage Input V1
UB -
24
Voltage Input V2
UB +
25
Voltage Input W1
UC -
26
Voltage Input W2
UC+
27
Voltage Input N1
U Busbar1 -
28
Voltage Input N2
U Busbar1 +
Connections
C264/EN CO/C80
MiCOM C264/C264C
4.13
Page 37/44
4.13.1
Block diagram
Protection
Current & Voltage
1 & 5 Amps
Unit board
PIN
TMU 210
Current inputs
Voltage inputs
C0363ENa
C264/EN CO/C80
Connections
Page 38/44
4.13.2
MiCOM C264/C264C
Connector description
The TMU210 board is equipped with a standard MiDOS 28 connector (see Figure 2:
Standard MiDOS 28 connectors).
Pin N.
Signal
Current Input 5A - N1
Current Input 5A N2
Not connected
Not connected
Not connected
10
Not connected
11
12
13
Not connected
14
Not connected
15
16
17
Not connected
18
Not connected
19
Not connected
20
Not connected
21
Voltage Input U1
22
Voltage Input U2
23
Voltage Input V1
24
Voltage Input V2
25
Voltage Input W1
26
Voltage Input W2
27
Voltage Input N1
28
Voltage Input N2
Connections
C264/EN CO/C80
MiCOM C264/C264C
4.14
Page 39/44
4.14.1
Block diagram
C264/EN CO/C80
Connections
Page 40/44
4.14.2
MiCOM C264/C264C
Connector description
Description
NIL
NIL
WDOG+
WDOG-
NIL
READ INHIBIT AO n 1+
READ INHIBIT AO n 1-
10
READ INHIBIT AO n 2+
11
READ INHIBIT AO n 2-
12
READ INHIBIT AO n 3+
13
READ INHIBIT AO n 3-
14
READ INHIBIT AO n 4+
15
READ INHIBIT AO n 4-
16
NIL
17
AO n 1+
18
AO n 1-
19
AO n 2+
20
AO n 2-
21
AO n 3+
22
AO n 3-
23
AO n 4+
24
AO n 4-
Connections
C264/EN CO/C80
MiCOM C264/C264C
4.15
Page 41/44
4.15.1
Signal
Rx+
Rx-
Tx+
not used
not used
Tx-
not used
Components side
1 2 3
Pin
State
Open
Common
Close
Close if default
C0119ENa
Wiring recommendation:
Due to the proximity of the port 4 Ethernet connector, it is strongly recommended that the
Fault signal connector connections are visually checked before any hand manipulation of
the Ethernet connectors.
Particular attention is to be paid during the wiring phase, not to damage the cables isolation.
C264/EN CO/C80
Connections
Page 42/44
4.16
MiCOM C264/C264C
4.16.1
Signal
Rx+
Rx-
Tx+
not used
not used
Tx-
not used
Components side
1 2 3
Pin
State
Default Rp-Es
Common
Default Rs-Ep
Close if default
C0121ENa
Wiring recommendation:
Due to the proximity of the port 4 Ethernet connector, it is strongly recommended that the
Fault signal connector connections are visually checked before any hand manipulation of
the Ethernet connectors.
Particular attention is to be paid during the wiring phase, not to damage the cables isolation.
Connections
C264/EN CO/C80
MiCOM C264/C264C
4.17
Page 43/44
4.17.1
Signal
Rx+
Rx-
Tx+
not used
not used
Tx-
not used
Components side
1 2 3
Pin
State
Default Link A
common
Default Link B
Close if default
C0297ENa
Wiring recommendation:
Due to the proximity of the port 4 Ethernet connector, it is strongly recommended that the
Fault signal connector connections are visually checked before any hand manipulation of
the Ethernet connectors.
Particular attention is to be paid during the wiring phase, not to damage the cables isolation.
C264/EN CO/C80
Connections
Page 44/44
4.18
MiCOM C264/C264C
Front panel
The front panel includes an RS232 interface, not galvanically isolated. This RS232 interface
is dedicated to maintenance and settings.
The properties of the serial link (DB9 female connector) for the maintenance dialogue are:
Baud rate:
19200
Data bits:
Parity:
No
Stop bit:
Control Xon/Xoff
Connector description:
4
9
3
8
2
7
1
6
C0061ENa
Pin N.
Signal
NC
Human Interface
C264/EN HI/C80
MiCOM C264/C264C
HUMAN INTERFACE
Human Interface
MiCOM C264/C264C
C264/EN HI/C80
Page 1/48
CONTENT
1.
2.
2.1
Overview
2.1.1
LEDs management
2.2
Configuration data
2.2.1
2.2.2
Language support
10
2.2.3
11
2.2.4
Bay panels
12
2.2.5
Events panel
22
2.2.6
Faults panel
23
2.2.7
Alarms panel
24
2.2.8
25
2.2.9
Configuration panel
26
2.2.10
31
2.2.11
32
2.2.12
Menu tree
33
2.2.13
35
2.2.14
Password management
42
3.
44
4.
45
5.
THE PRINTER
46
5.1
Inputs
46
5.2
Outputs
46
5.3
Printer management
47
5.3.1
47
5.3.2
47
5.3.3
47
5.3.4
47
C264/EN HI/C80
Human Interface
Page 2/48
MiCOM C264/C264C
BLANK PAGE
Human Interface
MiCOM C264/C264C
1.
C264/EN HI/C80
Page 3/48
The Printer
C264/EN HI/C80
Human Interface
Page 4/48
MiCOM C264/C264C
2.
2.1
Overview
The MiCOM C264/C264C front panel exists in two versions:
A simple FP with LEDs, L/R push-button and the serial link (GHU21x)
A graphical FP with LEDs, L/R push-button, the Local Control Display and the serial
link ( GHU20x)
LEDs
Key-pad
Local/Remote
push-button
Graphical
LCD
C0020ENd
setpoint
counters value
Human Interface
C264/EN HI/C80
MiCOM C264/C264C
Page 5/48
Display:
Device position
Alarms list
Disturbance record
Configuration
Events list
Fault list
Status information
Bypass indications
Setting points
Board state
IED state
LEDs management
There are 17 LEDs available; 16 of them are managed by the software. One is directly
connected to the internal power.
2.1.1.1
First LEDs
The first LEDs indicate the MiCOM C264/C264C status information, that is from top to down.
LED id Colour
LED on
LED off
Red
Yellow
Yellow
Computer in
reboot
Green
Power on
Not used
Not used
Power off
5 (4)
Red
Not used
All bays
managed by the
computer are in
REMOTE
Red
Not used
Not used
No fault at all
No fault
No alarm
(1) Major fault: MiCOM C264 not available due to internal failure (database error, CPU
board failure, ).
(2) A minor fault is a fault causing only the non availability of a part of the functionality.
(3) When the alarm disappears, the LED returns automatically to OFF.
(4) Assigned by computer only for without LCD panel: GHU2x1 or for an extension C264.
(5) It may be a board fault, an IED fault, a power off, a watchdog issue (DO#0 of BIU
board), an IED or extension disconnected.
C264/EN HI/C80
Human Interface
Page 6/48
2.1.1.2
MiCOM C264/C264C
Other LEDs
Other LEDs default assignment:
LED 12: At least one IED is disconnected (mono / main / extension rack)
Computer
Led
Graphical Panel
Principal Rack
Simple Panel
Graphical Panel
Extension Rack
Simple Panel
Simple Panel
1
2
Assigned by
computer
Assigned by
computer
Assigned by
computer
Assigned by
computer
Assigned by
computer
Assigned by
computer
Assigned by
computer
3
4
5
6
Not Used
Assigned by
computer
Assigned by
computer
7
8
9
Predefined
10
Predefined
Predefined
Predefined
Pre-defined
Not
Used
Not Used
11
12
Free
Free
Free
Free
13
14
15
16
17
Not
Used
Not
Used
Not Used
Human Interface
C264/EN HI/C80
MiCOM C264/C264C
2.1.1.3
Page 7/48
Color
Description
01
red
Hardware Fault
02
amber
03
amber
Maintenance Mode
04
green
Power Supply
05
red
06
red
07
red
Vn-5%
08
red
09
red
10
red
11
red
Loss of Voltage
12
red
Abnormal Voltage
13
red
14
red
15
red
16
red
17
red
C264/EN HI/C80
Human Interface
Page 8/48
2.2
MiCOM C264/C264C
Configuration data
The behaviour of the user-configurable LEDs is defined in the computer DataBase.
When using a simple DHMI, the 11 user-configurable LEDs give the status of the associated
BI. Each BI state is displayed using the ON / OFF / BLINKING led state.
When using a graphical DHMI (with LCD), the 13 user-configurable LEDs can be configured
to have 2 different behaviours:
1.
give the status of the associated BI. Each BI state is displayed using the ON / OFF /
BLINKING led state (same way as with a Simple DHMI),
2.
if the BI is transient:
if the BI is SET, the associated LED is ON or Blinking Slow (depends of the DB),
after pressing the C button, the LEDs state goes OFF (without any password).
if the BI is permanent:
after pressing the C button, the LED goes ON (without any password),
if the BI is RESET, the associated LED remains Blinking if the C button has not
been pressed or is OFF if it has.
Remarks:
The C button is used for the navigation in the menu tree. This feature remains and
so alarm acknowledgement will be not allowed from the menu tree.
The alarm acknowledgement function is not available with the simple panel (no C
button available).
The 11 other LEDs are freely configurable: they can be attached to a datapoint.
Furthermore, the datapoint state is displayed through a led state: on, off, slow blinking, fast
blinking.
For a Single Point, the Set / Reset / Invalid (i.e. all other states) can be attached to a LED.
For a Double Point, the Open / Close / Invalid (i.e. all other states) can be attached to a LED.
2.2.1
is used for menu navigation. During the menu navigation it has no effect on
LED management.
There are 7 main groups of panels; each group can have several kinds of panel.
The key
The keys
and
Human Interface
C264/EN HI/C80
MiCOM C264/C264C
Page 9/48
graphical one or two panels for each bay with sub panel displays:
controls
Group 2:
alarm - one panel displays the alarm list and allows acknowledgement and
clearing
Group 3:
Group 4:
Group 5:
if a hardware fault occurs, the board panel is accessible and shows only faulty
boards
if an IED fault occurs, the IED panel is accessible and shows only disconnected
IEDs
if one or several IEC61850 clients are not connected, the number of real
connected clients is displayed against the maximum number of clients
Group 6:
Group 7:
service:
Group 8:
physical:
Group 9:
banner - one panel displays general information on C264 to avoid any mistake
Group 10:
login & password - two panels, accessible from several panels and used to
select login and enter password
C264/EN HI/C80
Human Interface
Page 10/48
MiCOM C264/C264C
From any panel, a help panel is accessible using the book key. From this panel, a new press
on help key allows to display the graphical panel of the first bay in active mode or the service
panel in maintenance mode.
A number of panels (graphic bay, defaults, AVR, service, banner) are eligible as start panel.
Refer to the AP chapter. If a login panel is required, banner must be the start panel.
Inactivity panel (screen saver) and delay are configurable. Refer to the AP chapter.
2.2.2
Language support
The LHMI supports 2 languages that are chosen during configuration phase. A parameter in
the menu tree allows switching between both languages.
NOTE:
Human Interface
C264/EN HI/C80
MiCOM C264/C264C
2.2.3
Page 11/48
1 char
_
8 characters
H
S
C0154ENa
DD/MM/YY
MM/DD/YY
YY/MM/DD
State of date and time: the application software of the computer manages the different
state of the date and time:
Time, date and state are visible and modifiable in the menu tree. To modify time or date,
refer to the ST chapter.
C264/EN HI/C80
Human Interface
Page 12/48
2.2.4
MiCOM C264/C264C
Bay panels
Graphical representations of bays are visible in panels. Each bay has its own panels (up to
2). Up to 12 bays can be displayed via the Front Panel of the computer. A maximum of 9
devices can be displayed on a per panel basis.
All information of these panels is configurable except for the time indication.
Bay
Panel 1
Bay
Panel 2
Key 4
Bay
Panel n
Key 4
Key 4
Key 4
Key 3
Key 3
Key 3
Key 3
Key 2
Key 2
Key 2
Key 1
Help
sub-panel
Measurement
sub-panel
Control
sub-panel
State
sub-panel
Bypass
sub-panel
Interlock
sub-panel
C0156ENa
Human Interface
C264/EN HI/C80
MiCOM C264/C264C
Page 13/48
and
measurement to display on the bargraph. The totality of the bargraph represents either
120% or 200% of the nominal value.
Example:
local/remote mode
L/R
interlock bypass
EQL BP
synchrocheck bypass
S/C BP
vertical bargraph
DPS1
SBMC mode
DPS2
measure value
value
horizontal bargraph
measure name
measure name
command report message
message
M S C
C264/EN HI/C80
Human Interface
Page 14/48
MiCOM C264/C264C
The AVR Graphical bay panel shows up to 8 measurement values; their position and label
are settable, but the top and bottom lines are excluded.
Format: <Measure Name> : <Value> <Unit>
2.2.4.1
State sub-panel
This panel allows to display the state of the digital datapoints (single points, double points
and multiple points).
3 lines are necessary to display any information.
Human Interface
C264/EN HI/C80
MiCOM C264/C264C
Page 15/48
i n c
C
R
S L o c a l
o
2
e
/
h
6
s
r
1 2 : 3 4 : 5 6
.
S P S
4 P
e t
e m o t e D P S
R e m o t e
G o s M s g
S e l f
c h e c k
M o d u l e
D P S
G e n e r a l
J a mm e d
f a u l t
1 / 5
S T A T E
C 2 6 4 P
H H : MM : S S
M o d u l e
S P S
G e n e r a l
S e t
L o c a l / r e m o t e D P S
S B MC
L o c a l
S P S
R
s w
D
C
D S 1
e
g
S
l
s e t
r
p o s .
1
o s e d
2 / 5
Measurement 1
Measurement 2
Measurement 3
C264/EN HI/C80
Human Interface
Page 16/48
MiCOM C264/C264C
Display of measurements
Analogue values or digital measurements can be displayed in this panel if defined in
database. The value is displayed with 2 digits after the dot and 5 before.
<Label of the meas > = 16 characters maximum
Module of the measurement = 16 characters maximum
Value: 7 char
Unit (5 char)
Unit (5 char)
Human Interface
C264/EN HI/C80
MiCOM C264/C264C
Page 17/48
M E A S
C O U N T
C 2 6 4 P
T e m p 1
M E A S
U n d e f i n e d
_ _ _ _ _ _ _ _ _ _ _ _ _
T e m p 2
M E A S
U n d e f i n e d
1 / 1
M E A S
C O U N T
C A L C U 1
M V
D a t a p o i n t s
C 1
U n k n o w n
M V
1
D a t a p o i n t s
C 1
U n k n o w n
M V
2
D a t a p o i n t s
C 1
U n k n o w n
1 / 2
FIGURE 7: EXAMPLES OF MEASUREMENTS SUB-PANELS
Command 1
Command 2
Command 3
Command 4
Page
does not exist in Chinese LHMI
NOTE:
In Chinese LHMI, the bay and module names are not displayed, only
the data point label does.
C264/EN HI/C80
Page 18/48
Human Interface
MiCOM C264/C264C
The SCE software permits to customize data model informations (labels and values), for
example, operator can be the need to modify some informations (embedded dictionary in the
langage) in order to obtain more accuracy; refer to the SCE operating guide for langage
customization process.
Voltage/Target V in %
Human Interface
C264/EN HI/C80
MiCOM C264/C264C
Page 19/48
View 1
A V R
1 /
3
<Bay name>= 16 char max
M
S
O
T
D
A
E
T
V
M E A S
<measurement 3 digits
double size>
T
:
:
k
k
V
V
I
W
A
A
<meas 2 digit>
D
<Meas>
View 2
A V R
2 /
3
<Bay name>= 16 char max
M
S
V
V
T
D
T
O
T
D
A
E
T
A
E
P
M
T
R
V
I
E
A
G
I
A
R
E
A
S
G
T
T
:
:
: <meas 5 digits>
: <meas 5 digits>
: <meas 3digits> %
: <meas 3digits> %
: <meas 2dg
+
-
R
L
A
O
M M
View 3
A V R
3 /
3
<Bay name>= 16 char max
M
S
O
T
D
A
V
I
P
Q
S
C
E
T
:
:
:
:
:
:
:
<meas 5 digits>
<meas 5 digits>
<meas 5 digits>
<meas 5 digits>
<meas 5 digits>
:
:
<meas 5 digits>
<meas 5 digits>
k
A
M
M
M
V
W
V
V
C264/EN HI/C80
Human Interface
Page 20/48
MiCOM C264/C264C
DEVIATION: Delta between Target voltage value and Measured Value (%): fixed
format on 2 digits: xx
V TARGET: Target Voltage for the concerned transformer (come from a remote
Setpoint or from local command, or from predefined value in database) fixed format
on 5 digits: xxx.xx
Local HMI offers also all the needed maintenance Functions to facilitate the C264 with AVR
Commissioning and Maintenance (Visualization of input/outputs)
Local HMI offers facility to adjust the local date/Time (when not synchronized with an
external GPS Clock).
2.2.4.3
Controls sub-panel
The operator is allowed to control devices from the controls sub-panel.
The commands are displayed as following:
Label order
On this panel, the operator selects the chosen command using the key
.
Human Interface
C264/EN HI/C80
MiCOM C264/C264C
Page 21/48
Command 1
Command 2
Command 3
Command 4
Page
C OMM A N
C A L
D P C 1
D
ON
O
K l a x o n
D
D
C U 1
a t a p o i n t s
r d e r
O p e n
C 1
a t a p o i n t s
C 1
S B MC
c o n t r o l
O f f
O r d e r
S P C
O n
1 / 2
C OMM A N D
C A L C
S e t P o i n
D a
+ 0 0 0 0 6
U 1
t
t a p o i n t s
. 0 0
C 1
2 / 2
FIGURE 8: EXAMPLES OF CONTROL SUB-PANELS
C264/EN HI/C80
Human Interface
Page 22/48
2.2.4.4
MiCOM C264/C264C
Interlocking sub-panel
When a module is selected in the graphic bay panel, the button
c allows to access to
the interlocking panel. Any button allows to leave this panel and come back to the graphic
bay panel.
This panel displays the interlocking equation result (TRUE / FALSE) associated to a device
control.
C
state
state
2.2.5
Events panel
The event panel allows to display the event list of the computer in a chronological order.
Display of events is done from newest to oldest: that means that the newest event declared
is displayed at the top of the events panel (i.e. newest event is always rank 1).
This event list is a circular queue. List maximum size depends of computer version series.
This list is displayed in a scrollable view using arrows buttons. When the circular queue is full
and a new event appears, then the rank of each event is increased and the oldest event in
the queue is removed.
One screen of the LCD contains at maximum 2 events.
At first time the user enters the events panel, the 2 newest events are displayed.
<state of the time> <time>
Human Interface
C264/EN HI/C80
MiCOM C264/C264C
Page 23/48
If the operator visualises the first page, it is assumed that he is looking for the newest
events. Therefore, the page will be updated at the apparition of any new event.
The operator visualises one page between the first page and the last one, it is
assumed that he examines more precisely these events.
Therefore, when n events appear, the user keeps visualising the 2 same events.
However, the rank of each event is incremented by n in real time in the list. When the
displayed event is removed from the FIFO, the oldest event is displayed.
Last page means visualisation of the two oldest event of the FIFO and the FIFO is full.
When the displayed event is removed from the FIFO, the new oldest event is
displayed.
E
0
0
C
C
L
V E N
0 1 6 /M 0
2 6 4
2 6 4
o c a
T
- - - - 5 / 10 2 *
P
P
l / r e m
R e m o
* 1 2 : 3 4 : 5 6
- - - - - - - - - - - 1 1 : 2 2 : 3 3 . 1 2 3
0
0
C
C
I
0 2 6 /M 0
2 6 4
2 6 4
S A G
- - - - - - - - - - - - - - - - 5 / 10 2 * 1 1 : 2 2 : 3 3 . 5 6 7
P
P
R A F
s t a t u s
o t e
t e
D P S
WA I T I N G
0 0 1 / 10 0 0
FIGURE 9: EXAMPLE OF EVENT SUB-PANEL
2.2.6
Faults panel
The first LED of the local HMI indicates 2 levels of fault.
When the LED is ON, a major fault is present. It can be:
A database incoherence
A hardware fault
A disconnected IED
C264/EN HI/C80
Human Interface
Page 24/48
2.2.7
MiCOM C264/C264C
Alarms panel
Alarms are displayed in the form of one list in the panel. This list is a circular buffer and is
displayed in a scrollable view in the same way as for the events panel.
One screen of the LCD can contain a maximum of 2 alarms:
<Date, time and state of time of the last alarm state change > =21 char.
<State of the alarm>=19 char. Max.
Gr
<Date, time and state of time of the last alarm state change > =21 char.
<State of the alarm>=19 char. Max.
<Information about event that generate
the apparition or the state change of the alarm>
5 lines * 21 char./line maximum
Gr
Human Interface
C264/EN HI/C80
MiCOM C264/C264C
A
0
I
C
D
D
S
K
0
A
C
C
G
Page 25/48
L A R
6 /M 0
N C T
2 6 4
S 1
S 1
e l e
O 6 /M 0
C T
2 6 4
2 6 4
o s M
M
* 1 2 : 3 4 : 5 6
5 / 0 4 * 1 1 : 2 2 : 3 3 . 1 2 3
A C T
U N A C K
A L
1
P
C
c
i
5
U
P
P
s
t
t
n
/
N
r
e
t
0
A
l
D P
d
e r l o
4 * 1 1
C K
A
C
c k
: 2 2 : 3 2 . 4 5 6
L
g
R e s e t
0 0 1 / 0 0 2
A
0
A
C
D
S
L A R
6 /M 0
C T
A L C
a t a
P S 7
M
5
U
U
p
0 1 : 0 2 : 0 3
/ 0 4 * 1 1 : 2 2 : 3 3 . 7 8 9
N A C K
A L
1
o i n t s
C 1
R e s e t
0
A
C
D
S
6 /M 0
C T
A L C
a t a
P S 7
5
U
U
p
/ 0 4 * 1 1 : 2 2 : 3 1 . 9 6 3
N A C K
A L
1
o i n t s
C 1
R e s e t
0 0 1 / 0 1 6
FileName
<Record beginning date, time and state of time > =21 char.
<Information about event that causes the recording>:
2 lines * 21 char./line maximum for computer waveform record
Name of the IED for IED disturbance record
FileName
<Record beginning date, time and state of time > =21 char.
C264/EN HI/C80
Human Interface
Page 26/48
MiCOM C264/C264C
The records are displayed on the panel using 2 lists according to the origin. Displayed
information depends on the origin of the file:
waveform records are in COMTRADE format, 3 files can be displayed per page. Only
the .cfg file name is displayed on the panel (the .dat files are only available to be
uploaded).
Type (F,S)
Time stamp
Bay Name / Module Name / Datapoint label (up to 2 lines)
Configuration panel
The configuration panel allows to display several panels concerning the computer itself:
Board panel
Ext. device
panels
Service Information
panel
Key 4
Key 4
Key 4
Key 3
Key 3
Key 3
Key 2
Key 1
Key 2
Key 2
Human Interface
C264/EN HI/C80
MiCOM C264/C264C
2.2.9.1
Page 27/48
Boards panel
Boards list view is a text list containing the status of I/O boards.
For each board, the following information is displayed in one line of the board panel:
its type,
its state among the following ones: OK (Board connected and operational), MISSING
(Board missing), FAILURE (Board in fault), TOO MANY (Board present but not
configured).
board label
board status
B O A R
B I U
O
G H U 2
O
D I
0
O
D I
1
O
D I
2
O
D I
3
O
* 1 2 : 3 4 : 5 6
k
0 0
k
k
k
k
k
1 / 2
B O A R
D O
0
O
D O
1
O
D O
2
O
D O
3
O
A I U 2
O
A I U 2
O
* 1 2 : 3 4 : 5 7
k
k
k
k
1 0
k
1 0
k
2 / 2
page number
number of pages
C0301ENa
C264/EN HI/C80
Human Interface
Page 28/48
2.2.9.2
MiCOM C264/C264C
IP client connection number: it defines the number of client currently connected to the
computer.
IP server connection state: it defines the list of the server connected to the computer.
Each server is displayed with its name, its IP address, and the state of its connection.
server name
IP address
state
Legacy protocol connection state: each IED is displayed with its name, its address,
and the state of its connection.
IED name
address
state
protocol
Server 1
Server 2
Server 3
page
The panel for Legacy IED is as follows:
E
protocol
IED 1
IED 2
IED 3
IED 4
page
Human Interface
C264/EN HI/C80
MiCOM C264/C264C
Page 29/48
I E D
I P
*
C L I E N T
S C A D A
T 1 0 1
N B
1 2 : 3 4 : 5 6
0 0 0
I E D
D I S C O N N
0 0 1 / 0 0 2
I E D
I E D s
P 4 4
0
P 6 3
0
P 1 3
0
P 1 2
0
2
0
2
0
9
0
7
0
*
:
_3
3
_4
4
_
2
_
1
1 2 : 3 4 : 5 7
T 1 0 3
3
D I S C O N N
4
D I S C O N N
2
D I S C O N N
1
D I S C O N N
0 0 2 / 0 0 2
FIGURE 13: EXAMPLE OF EXTERNAL DEVICES PANEL
C264/EN HI/C80
Human Interface
Page 30/48
2.2.9.3
MiCOM C264/C264C
software version
operating modes
redundancy mode
S E R V I C E
S E R I A L
N
0 0 0 0 3 9 6
S O F T WA R E
A 4 .
D B 1
V E R S
0 . 3
D B 2
V E R S
1 2 : 3 4 : 5 6
B
2
V E R S I O
3 1 A
I O N
S T A
A C
I O N
S T A
N O
O P E R A T I N G
H O U R S
6 0
O P E R A T I N G
MO D E
O P E R A
R E D U N D A N C Y
MO D E
N O T
R
N
T E
T I V E
T E
B D
1
T I O N A L
E D U N D E
Human Interface
C264/EN HI/C80
MiCOM C264/C264C
2.2.10
Page 31/48
The state of the physical input with 3 possible values (On, off , fault)
<state of the time> <time>
Board type
value
value
value
value
value
value
value
value
value
value
value
value
value
value
value
value
value
value
value
value
E T O R
* 1 2 : 3 4 : 5 6
board number
B O A R D
board type
D
D
D
D
D
D
D
D
I
I
I
I
I
I
I
I
0
1
2
3
4
5
6
7
O
O
O
O
O
O
O
O
N
F
N
F
N
F
N
F
F
F
F
F
D I U
D
D
D
D
D
D
D
D
I
I
I
I
I
I
I
I
8
9
1
1
1
1
1
1
0
1
2
3
4
5
O
O
O
O
O
O
O
O
N
F
N
F
N
F
N
F
F
F
F
F
input number
input status
1 / 4
C0302ENa
C264/EN HI/C80
Human Interface
Page 32/48
2.2.11
MiCOM C264/C264C
The state of the physical output with 3 possible values (on, off, fault)
<state of the time> <time>
value
value
value
value
value
value
value
value
value
value
value
value
value
value
value
value
value
value
value
value
S T O R
* H H : M M : S S
board number
B O A R D
board type
D
D
D
D
D
D
D
D
O
O
O
O
O
O
O
O
0
1
2
3
4
5
6
7
O
O
O
O
O
O
O
O
N
F
N
F
N
F
N
F
D O U
D O
D O
8
9
O N
O F F
F
F
F
output number
output status
1 / 4
C0303ENa
Human Interface
C264/EN HI/C80
MiCOM C264/C264C
2.2.12
Page 33/48
Menu tree
Some parameters of the computer can be set by the operator from local HMI. The display /
modification of the parameter value is done in the menu tree from the local HMI. All the
parameters are group in the same path of the menu tree.
The parameters that can be modified on-line are:
language
counters value
autorecloser parameters
toggling parameters
The controls that can be performed from the menu tree are:
database switching
NOTE:
The C button is used for the navigation in the menu tree. This
feature remains and so alarm acknowledgement will be not allowed
from the menu tree.
The following figures show the menu tree in the three operating modes.
C264/EN HI/C80
Human Interface
Page 34/48
MiCOM C264/C264C
root
COMMAND
MAIN
RESET OP HOURS
CHANGE MODE OP
GLB ACK ALARM
GLB CLR ALARM
DATE
TIME
DB SWITCH
LANGUAGE
COUNTER
CONFIG
COMPUTER
MAIN
BAY
IP ADDRESS
(name of bay)
INTERNAL S/C
AR
DEVICE
(name of device 1)
(name of device i)
BI
MV
COMM. PORT
HMI
( name of BI 1)
MOTION 00 FILT
MOTION 11 FILT
PERS CLOSE FILT
PERS OPEN FILT
TOGGLING OPTION
( name of BI i)
MOTION 00 FILT
MOTION 11 FILT
PERS CLOSE FILT
PERS OPEN FILT
TOGGLING OPTION
( name of MV 1)
HYSTERESIS
DEADBAND
THRESHOLD1
THRESHOLD2
THRESHOLD3
THRESHOLD4
THRESHOLD5
THRESHOLD6
( name of MV i)
HYSTERESIS
DEADBAND
THRESHOLD1
THRESHOLD2
THRESHOLD3
THRESHOLD4
THRESHOLD5
THRESHOLD6
COMM. PORT 4
MAIN
EXIT MT TIME
BACK LIGHT DELAY
SELECT EXIT TIME
PASSWORD
BYPASS DELAY
BAY
(name of bay)
TIME OPEN
TIME CLOSE
TIME OPEN
TIME CLOSE
BAUDRATE
PARITY
STOP BIT
NB BIT PER CHAR
Human Interface
C264/EN HI/C80
MiCOM C264/C264C
Page 35/48
root
COMMAND
CONFIG
MAIN
CHANGE MODE OP
DATE
TIME
DB SWITCH
MAIN
COMPUTER
HMI
MAIN
IP ADDRESS
EXIT MT TIME
BACK LIGHT DELAY
SELECT EXIT TIME
PASSWORD
BYPASS DELAY
C0305ENa
Computer mode
Database switch
Alarms acknowledgement
Alarms clearing
Control
Protection
Device command
Computer mode
Protected by a password
Protected by a password
Protected by a password
Protected by a password
Protected by a password
Alarms Acknowledge
Protected by a password
Alarms clearing
Protected by a password
C264/EN HI/C80
Page 36/48
2.2.13.1
Human Interface
MiCOM C264/C264C
If the computer manages several bays, the state local / remote of bays is set bay by bay.
Change of bay mode is enabled if a bay panel is defined. It means that, if a bay is not
associated to a bay panel, its local/remote control mode cannot be controlled through the
L/R button of the panel.
Local / Remote control of bay for simple panel with LEDs (GHU21x)
In case of simple panel, the operator controls all the bays of the computer in the same time.
To change mode, s/he has to press of the button during at least 3 seconds. No password is
necessary to check the control. The 5th LED is used to display the current mode. If all the
bays are NOT in the same state, the command switches them all too local mode.
2.2.13.2
Circuit breakers, disconnecting switches or generic command are ordered from the local HMI
by the operator. Commands allowed from the local HMI are:
open
close
close with bypass on a synchronised circuit breaker (forcing closure), available only
when the DI Accept Forcing is configured
The button
SBO command
In case of the select/execution order (SBO) for opening or closing a module, the operator
has to make on the local HMI a selection before an execution command.
command.
After a positive acknowledgement of the selection command, the device is displayed in
reverse video.
DE command
In event of the Direct execute order (DE) for opening or closing module, the operator sends
directly the command using the command buttons.
Human Interface
C264/EN HI/C80
MiCOM C264/C264C
Page 37/48
Interlocking bypass
To get access to the bypass flag modification panel, use the [ ENTER ] button
Set the interlocking bypass command before you send the execute order.
To send the bypass command, use the bypass flag on the interlocking equation.
B
C264/EN HI/C80
Human Interface
Page 38/48
MiCOM C264/C264C
Synchrocheck bypass
The operator can send the command using bypass flag on synchrocheck (forcing closure).
The S/C bypass flag is present when the Accept Forcing DI is configured. The S/C bypass
flag can be set before or after the execute order sending.
Operator accesses to the bypass flag modification panel by the enter button.
B
allows to select graphically the device or the command of the bay. When
(for ON).
The button allows to abort the choice during the selection step (in event of SBO
order).
Human Interface
C264/EN HI/C80
MiCOM C264/C264C
2.2.13.3
Page 39/48
allows to select one by one the devices of the bay. When a transformer is
selected, the operator can control it from local control panel by dealing with associated tap
changer positions.
In order to command the tap changer, the bay that the transformer belongs to has to be in
local mode.
The commands that can be sent through the local HMI are:
2.2.13.4
Computer mode
Control of the C264 with AVR and manual orders to the Tap Change are available from the
C264 with AVR local HMI with simple and intuitive actions on the animated Single Line
Page.
The operator controls:
C264/EN HI/C80
Human Interface
Page 40/48
MiCOM C264/C264C
* NOTE:
Controls Raise and Lower use front panel keys for navigation:
Selection, Enter, Up and Down.
The Single Line Page 1 is graphically showing the AVR Running Mode, CB status, Tap
Changer Position Indication and the Current Voltage.
2.2.13.5
2.2.13.6
2.2.13.7
2.2.13.8
M E N U
T R E E
* H H : M M : S S
/ / C O M M A N D / C O U N T E R /
c o u n t e r
1 /
C O U N T E R
current value
v a l u e
0 0 0 0 0 0 0 0 0 4
wanted value
0 0 0 0 0 0 0 0 0 4
M I N
M A X
0
2 1 4 7 4 8 3 6 4 7
C0306ENa
are used to select the digit of the wanted value that has to be
modified. Buttons and allow to change the value of the selected digit.
Buttons
and
Once the correct wanted counter value is defined, it can be validated by pressing button
.
Human Interface
C264/EN HI/C80
MiCOM C264/C264C
2.2.13.9
Page 41/48
Acknowledgement of alarms
Acknowledgement of alarms is performed globally or on a per alarm basis:
Alarm per alarm acknowledgement: the operator can perform the alarm acknowledge
one by one. It is performed from the alarm panel.
the operator select (in the alarm panel) one alarm with the select button:
. Once
the alarm is selected, the two first lines of the alarm in the alarm panel are blinking.
.
the operator press the enter button , enter the password if necessary
The button
Global clear: the operator can clear all the inactive acknowledged alarms of the
computer. It is performed from the menu tree (with password check).
Alarm per alarm clear: the operator can perform the alarm clear one by one. It is
performed from the alarm panel.
C264/EN HI/C80
Human Interface
Page 42/48
MiCOM C264/C264C
The operator selects (in the alarm panel) one alarm with the select button:
.
Once the alarm is selected, the two first lines of the alarm in the alarm panel are
blinking. (deselecting is performed by the button
The button
.
If the button sequence is correct, the selected alarm is cleared and disappears from the list.
2.2.14
Password management
2 profiles are defined in CAT and allowed in the computer:
observer
system engineer
These profiles can be named differently in the login panel depending on configuration.
The second one is necessary to activate commands from local HMI:
Human Interface
C264/EN HI/C80
MiCOM C264/C264C
Page 43/48
Function
Corresponding profiles
Observer
System engineer
there is only one account: System Engineer; an observer can still view data without
entering password
When a password is required, a string password??: is displayed in the current panel. The
operator has to enter it.
The first character is selected. The buttons and are used to change of selected
character.
The buttons and are used to change the value of selected character.
The character is displayed at each button press. The button validates the entered
password. If you press the enter key without entering any password, the string AAAAAAAA
is taken in.
The current type of characters is repeated in the right bottom corner of the panel:
The password cannot be changed and its validity time is 15 minutes. During this delay, user
can run another command. This delay is re-armed at each button press.
C264/EN HI/C80
Page 44/48
3.
Human Interface
MiCOM C264/C264C
Human Interface
MiCOM C264/C264C
4.
C264/EN HI/C80
Page 45/48
C264/EN HI/C80
Page 46/48
5.
Human Interface
MiCOM C264/C264C
THE PRINTER
Some specific events (the events to log are declared in the database) are printed and
chronologically sorted on logbook printers. They are printed with their time stamping and a
complete description (location and event description).
Logbook printers can be connected to SCP operator interface or to a bay level computer.
The printout format, which can be defined by user during the system configuration phase, is
the same across the whole log book printers connected.
A computer does not print information coming from other computers.
5.1
Inputs
A computer receives acquisition from various equipment (protection, captors, etc.) and, after
processing, may generate events that have to be printed. These kinds of events are defined
in the database during the configuration phase.
Types of events can be:
5.2
Measurement
Operator action:
Devices control
Outputs
The 5 following properties can be printed. Each property is separated from the other by one
blank character The position of each property in the printed line (i.e. position 1, 2, 3, 4 or 5)
is defined in configuration:
Chronology 1 character: refer to SOE events
TimeStamp 24 or 26 characters: refer to SOE events
Origin - 67 characters: for BI, TPI, measurements, controls and alarms, the origin gives the
access path to the object (refer to SOE events)
ObjectName - 16 characters
ObjectMessage - 16 characters
The Origin, ObjectName and ObjectMessage properties contain different information
depending of the associated event type.
Human Interface
C264/EN HI/C80
MiCOM C264/C264C
Page 47/48
5.3
Printer management
5.3.1
Date / Time
<Log Book>
<blank line>
Page Number
C0141ENa
5.3.3
5.3.4
Buffer Length
Printers
Data flow
C0142ENa
C264/EN HI/C80
Human Interface
Page 48/48
MiCOM C264/C264C
When the buffer is full, the oldest information are deleted (300 information suppressed) in
order to have place for new ones.
A specific message is inserted in the buffer to indicate the lost of information, this message
has the following information:
TimeStamp
Origin
ObjectName
ObjectMessage
substation-C264_GTW
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
05/07/06
05/07/06
05/07/06
05/07/06
05/07/06
05/07/06
05/07/06
05/07/06
05/07/06
05/07/06
05/07/06
05/07/06
05/07/06
05/07/06
05/07/06
05/07/06
05/07/06
05/07/06
05/07/06
05/07/06
05/07/06
05/07/06
05/07/06
05/07/06
05/07/06
05/07/06
05/07/06
05/07/06
05/07/06
05/07/06
05/07/06
05/07/06
05/07/06
05/07/06
05/07/06
05/07/06
05/07/06
05/07/06
05/07/06
05/07/06
05/07/06
05/07/06
05/07/06
05/07/06
05/07/06
05/07/06
05/07/06
05/07/06
05/07/06
09:08:35.232
09:08:35.232
09:08:35.232
09:08:35.232
09:08:35.232
09:08:35.232
09:08:35.232
09:08:35.232
09:08:35.232
09:08:35.232
09:08:35.232
09:08:35.232
09:08:35.232
09:08:35.232
09:08:35.232
09:08:35.232
09:08:35.232
09:08:35.232
09:08:35.232
09:08:35.232
09:08:35.232
09:08:35.232
09:08:35.232
09:08:35.232
09:08:35.232
09:08:35.232
09:08:35.232
09:08:35.232
09:08:35.232
09:08:35.232
09:08:35.232
09:08:35.232
09:08:35.232
09:08:35.232
09:08:35.232
09:08:35.232
09:08:35.232
09:08:35.232
09:08:35.232
09:08:35.232
09:08:35.232
09:08:35.232
09:08:35.232
09:08:35.232
09:08:35.232
09:08:35.232
09:08:35.232
09:08:35.232
09:08:35.232
05/07/06 09:08:35.232
CALC
CALC
CALC
CALC
CALC
CALC
CALC
CALC
CALC
CALC
CALC
CALC
CALC
CALC
CALC
CALC
CALC
CALC
CALC
CALC
CALC
CALC
CALC
CALC
CALC
CALC
CALC
CALC
CALC
CALC
CALC
CALC
CALC
CALC
CALC
CALC
CALC
CALC
CALC
CALC
CALC
CALC
CALC
CALC
CALC
CALC
CALC
CALC
CALC
C264N3
C264N3
C264N3
C264N3
C264N3
C264N3
C264N3
C264N3
C264N3
C264N3
C264N3
C264N3
C264N3
C264N3
C264N3
C264N3
C264N3
C264N3
C264N3
C264N3
C264N3
C264N3
C264N3
C264N3
C264N3
C264N3
C264N3
C264N3
C264N3
C264N3
C264N3
C264N3
C264N3
C264N3
C264N3
C264N3
C264N3
C264N3
C264N3
C264N3
C264N3
C264N3
C264N3
C264N3
C264N3
C264N3
C264N3
C264N3
C264N3
/Generic
/Group 0
/Group 0
/Group 0
/Group 0
/Group 0
/Group 0
/Group 0
/Group 0
/Group 0
/Group 0
/Group 0
/Group 0
/Group 0
/Group 0
/Group 0
/Group 0
/Group 0
/Group 0
/Group 0
/Group 0
/Group 0
/Group 0
/Group 0
/Group 0
/Group 0
/Group 0
/Group 0
/Group 0
/Group 0
/Group 0
/Group 0
/Group 0
/Group 0
/Group 0
/Group 0
/Group 0
/Group 0
/Group 0
/Group 0
/Group 0
/Group 0
/Group 0
/Group 0
/Group 0
/Group 0
/Group 0
/Group 0
/Group 0
module
to 499
to 499
to 499
to 499
to 499
to 499
to 499
to 499
to 499
to 499
to 499
to 499
to 499
to 499
to 499
to 499
to 499
to 499
to 499
to 499
to 499
to 499
to 499
to 499
to 499
to 499
to 499
to 499
to 499
to 499
to 499
to 499
to 499
to 499
to 499
to 499
to 499
to 499
to 499
to 499
to 499
to 499
to 499
to 499
to 499
to 499
to 499
to 499
Group
Group
Group
Group
Group
Group
Group
Group
Group
Group
Group
Group
Group
Group
Group
Group
Group
Group
Group
Group
Group
Group
Group
Group
Group
Group
Group
Group
Group
Group
Group
Group
Group
Group
Group
Group
Group
Group
Group
Group
Group
Group
Group
Group
Group
Group
Group
Group
Group
Permanent
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
Self
Self
Self
Self
Self
Self
Self
Self
Self
Self
Self
Self
Self
Self
Self
Self
Self
Self
Self
Self
Self
Self
Self
Self
Self
Self
Self
Self
Self
Self
Self
Self
Self
Self
Self
Self
Self
Self
Self
Self
Self
Self
Self
Self
Self
Self
Self
Self
Self
Check
Check
Check
Check
Check
Check
Check
Check
Check
Check
Check
Check
Check
Check
Check
Check
Check
Check
Check
Check
Check
Check
Check
Check
Check
Check
Check
Check
Check
Check
Check
Check
Check
Check
Check
Check
Check
Check
Check
Check
Check
Check
Check
Check
Check
Check
Check
Check
Check
fault
fault
fault
fault
fault
fault
fault
fault
fault
fault
fault
fault
fault
fault
fault
fault
fault
fault
fault
fault
fault
fault
fault
fault
fault
fault
fault
fault
fault
fault
fault
fault
fault
fault
fault
fault
fault
fault
fault
fault
fault
fault
fault
fault
fault
fault
fault
fault
fault
PAGE
001
Application
C264/EN AP/C80
MiCOM C264/C264C
APPLICATION
Application
MiCOM C264/C264C
C264/EN AP/C80
Page 1/348
CONTENT
1.
2.
REQUIREMENTS
10
3.
11
3.1
11
3.2
11
3.3
Sparing object
12
4.
13
4.1
13
4.2
16
4.3
17
4.3.1
18
4.3.2
19
4.3.3
20
4.3.4
20
4.3.5
20
4.3.6
21
4.3.7
21
4.4
23
4.4.1
Adding boards
23
4.4.2
24
4.4.2.1
24
4.4.2.2
25
4.4.2.3
27
4.4.3
29
4.4.4
30
4.4.5
Configuring an AI channel
32
4.4.6
Adding a printer
33
4.4.7
Configuring an AO channel
36
4.5
37
4.5.1
37
4.5.2
40
4.6
42
4.6.1
42
4.6.2
44
4.6.2.1
45
4.6.3
60
C264/EN AP/C80
Page 2/348
Application
MiCOM C264/C264C
4.7
61
4.7.1
61
4.7.1.1
61
4.7.1.2
61
4.7.1.3
62
4.7.1.4
62
4.7.1.5
63
4.7.1.6
64
4.7.1.7
65
4.7.1.8
65
4.7.1.9
66
4.7.1.10
67
4.7.1.11
68
4.7.1.12
69
4.7.2
71
4.7.2.1
72
4.7.2.2
74
4.7.2.3
75
4.7.2.4
80
4.7.2.5
82
4.7.2.6
84
4.7.2.7
86
4.7.3
88
4.8
89
4.8.1
89
4.8.1.1
89
4.8.1.2
90
4.8.1.3
90
4.8.1.4
91
4.8.1.5
92
4.8.1.6
94
4.8.1.7
96
4.8.2
97
4.8.2.1
97
4.8.2.2
100
4.8.2.3
102
4.8.2.4
104
4.8.2.5
105
4.8.2.6
107
4.8.2.7
108
4.8.2.8
110
4.8.3
111
Application
MiCOM C264/C264C
C264/EN AP/C80
Page 3/348
4.8.4
113
4.9
114
4.9.1
114
4.9.2
115
4.9.2.1
115
4.9.2.2
116
4.9.3
118
4.9.3.1
119
4.9.3.2
123
4.10
127
4.11
128
4.11.1
129
4.11.2
134
4.11.3
135
4.11.4
136
4.11.5
137
5.
DEFINING DATAPOINT
5.1
Creating a datapoint
138
5.1.1
138
5.1.2
139
5.1.2.1
SPS processing
139
5.1.2.2
139
5.1.3
143
5.1.3.1
DPS processing
143
5.1.3.2
143
5.1.4
146
5.1.4.1
MPS processing
146
5.1.4.2
146
5.1.5
149
5.1.5.1
149
5.1.5.2
Adding an MV datapoint
150
5.1.5.3
152
5.1.5.4
153
5.1.5.5
153
5.1.6
155
5.1.6.1
155
5.1.6.2
155
5.1.6.3
156
5.1.6.4
156
5.1.6.5
156
5.1.6.6
157
5.1.7
158
138
C264/EN AP/C80
Page 4/348
Application
MiCOM C264/C264C
5.1.7.1
158
5.1.7.2
159
5.1.7.3
161
5.1.8
163
5.1.9
163
5.1.9.1
165
5.1.9.2
165
5.1.10
167
5.1.10.1
169
5.1.10.2
170
5.1.11
171
5.1.11.1
171
5.1.11.2
173
5.1.11.3
175
5.1.11.4
176
5.2
177
5.2.1
179
5.2.1.1
179
5.2.1.2
179
5.2.1.3
180
5.2.1.4
180
5.2.1.5
181
5.2.1.6
182
5.2.2
183
5.2.2.1
183
5.2.2.2
184
5.2.2.3
184
5.2.2.4
184
5.2.2.5
185
5.2.2.6
187
5.2.3
187
5.2.3.1
187
5.2.3.2
188
5.2.3.3
188
5.2.3.4
189
5.2.3.5
189
5.2.3.6
190
5.2.4
Defining an MV profile
191
5.2.4.1
Adding an MV Profile
191
5.2.4.2
192
5.2.4.3
192
5.2.4.4
192
Application
MiCOM C264/C264C
C264/EN AP/C80
Page 5/348
5.2.4.5
193
5.2.4.6
194
5.2.4.7
194
5.2.5
195
5.2.5.1
195
5.2.5.2
196
5.2.5.3
196
5.2.5.4
197
5.2.5.5
197
5.2.5.6
198
5.2.6
198
5.2.6.1
198
5.2.6.2
199
5.2.6.3
199
5.2.6.4
200
5.2.6.5
200
5.2.6.6
201
5.2.7
201
5.2.7.1
201
5.2.7.2
202
5.2.7.3
202
5.2.7.4
203
5.2.7.5
203
5.2.7.6
204
5.2.8
204
5.2.8.1
204
5.2.8.2
205
5.2.8.3
206
5.3
208
5.4
208
5.5
208
5.6
209
5.6.1
209
5.6.1.1
209
5.6.1.2
210
5.6.1.3
211
5.6.1.4
211
5.6.1.5
212
5.6.2
213
5.6.3
214
5.6.4
215
5.6.4.1
215
C264/EN AP/C80
Page 6/348
Application
MiCOM C264/C264C
5.6.4.2
215
5.6.4.3
215
5.6.4.4
216
5.7
217
5.7.1
217
5.7.1.1
217
5.7.1.2
217
5.7.1.3
218
5.7.1.4
219
5.7.2
220
5.7.3
221
5.7.4
222
5.7.4.1
222
5.7.4.2
222
5.7.4.3
222
5.7.5
222
5.8
223
5.8.1
223
5.8.2
224
5.8.3
225
6.
226
6.1
226
6.1.1
Defining a Site
228
6.1.2
Defining a Substation
228
6.1.2.1
229
6.1.2.2
230
6.1.2.3
231
6.1.2.4
232
6.1.3
233
6.1.3.1
234
6.1.3.2
234
6.1.4
Defining a Bay
235
6.1.4.1
237
6.1.4.2
237
6.1.4.3
239
6.1.4.4
240
6.1.5
Defining Module
240
6.1.5.1
242
6.1.5.2
243
6.1.5.3
243
6.1.5.4
244
Application
MiCOM C264/C264C
C264/EN AP/C80
Page 7/348
6.1.5.5
Defining a circuit-breaker
245
6.1.5.8
Defining a transformer
251
6.2
254
6.2.1
254
6.2.2
258
6.2.3
258
6.2.4
258
6.2.5
261
6.2.5.1
263
6.2.5.2
265
6.3
267
6.3.1
Auto-recloser behaviour
267
6.3.2
267
6.4
276
6.4.1
276
6.4.2
277
6.5
279
6.5.1
279
6.5.2
AVR behaviour
284
6.6
285
6.6.1
ATCC behaviour
285
6.6.2
285
6.6.2.1
285
6.6.2.2
288
6.6.2.3
289
6.6.2.4
291
6.6.2.5
293
6.7
296
6.7.1
296
6.7.1.1
296
6.7.1.2
298
6.7.1.3
298
6.7.1.4
299
6.7.1.5
300
6.7.1.6
302
6.7.2
303
6.7.2.1
304
6.7.2.2
305
6.7.2.3
306
6.7.2.4
307
6.7.3
Defining a group
311
6.7.4
313
C264/EN AP/C80
Page 8/348
Application
MiCOM C264/C264C
6.7.5
314
6.7.6
Defining interlocking
314
6.7.7
316
6.8
317
6.8.1
Data flow
317
6.8.2
Priority Setpoints
318
6.8.3
318
6.8.4
320
6.8.5
320
6.8.6
321
6.8.7
Datapoints
322
6.8.8
322
6.8.9
Topology calculation
324
6.8.10
325
6.9
326
7.
7.1
328
7.2
331
7.2.1
331
7.2.2
Creating a workspace
332
7.3
333
7.3.1
333
7.3.2
336
7.3.2.1
Adding a line
336
7.3.2.2
Adding a bitmap
337
7.3.2.3
338
7.3.3
339
7.3.3.1
340
7.3.3.2
341
7.3.3.3
341
7.3.3.4
342
7.3.3.5
344
7.3.4
346
7.4
347
328
Application
MiCOM C264/C264C
1.
C264/EN AP/C80
Page 9/348
C264/EN AP/C80
Page 10/348
2.
Application
MiCOM C264/C264C
REQUIREMENTS
First, if it is not already done, you will need to install the PACiS SCE (System Configuration
Editor), see the chapter IN (Installation) of this product.
This document presents you the objects and the attributes of a referenced database made
with the PACiS SCE. For understanding this document you first need to be familiar with
PACiS SCE and PACiS computer C264.
To add an IEC-61850 computer into an existing system you need to have the mapping of the
system (IP address, Network names of equipment).
To generate a template, for an existent IEC-61850 computer, see the chapter Functional
Description of the SCE product.
Application
C264/EN AP/C80
MiCOM C264/C264C
3.
3.1
Page 11/348
To define a complete PACiS system, three aspects should be taken into account.
The first one is the system topology. It consists of device composition that manages the
customers electrical process. Generally, this part of furniture is relevant to
Schneider Electric and corresponds to Schneider Electric system process definition to
respond customers needs.
The second one is the electrical topology. It consists of the customers electrical process
definition in term of typed electrical devices (transformer, disconnector, circuit-breaker)
that are connected each other through busbars or lines. Generally, this part of furniture is
relevant to the customer.
The third one is the graphical topology. It consists of the mimic and their graphical animation
descriptions that appear at substation control points (operator interface) and bay control
points (computer local HMI).
When creating a new configuration using SCE, these three topologies are automatically
instantiated via root objects:
A Site object for the electrical topology, containing one Substation object.
A Scs object for the system topology, containing one Ethernet network object (SCS
is an abbreviation of Substation Control System).
Electrical topology (Site): computer manages bays and relevant modules or substation
information.
Graphical topology (Graphic): computer can own a LCD display used for animated
graphical bay panel representation and others list panels.
C264/EN AP/C80
Application
Page 12/348
3.3
MiCOM C264/C264C
Sparing object
At SCE level, a spare object is an object having its spare attribute set to true. The
configurations of this object and of its spare attribute are the same as for any other object
and attribute. Any objects can be spare and particularly those concerning the computer
configuration.
Spare objects are not provided to the generator tools, respecting the following rules:
An object O2, not spare, linked directly or not to a spare composite parent object O1,
is considered as spare.
O1 (Spare = Yes)
O2 (Spare = No)
S0387ENa
A relation defined on an object O1, not spare, and linked to a spare object O2, is
considered as a relation without link.
O1 (Spare = No)
Relation
link
O2 (Spare = Yes)
S0388ENa
Application
C264/EN AP/C80
MiCOM C264/C264C
Page 13/348
4.
4.1
Common labels used for control acknowledgement, time quality logging, alarm
management logging, computer board management.
Designation of the master clock computer(s) in the system. Up to two computers can
be declared as System Master Clock. A System Master Clock computer gives the time
reference to all others devices connected to the station-bus network through SNTP
(Simple Network Time Protocol). A System Master Clock computer is always located
in a substation.
Some attributes of SCS objects concern all the computers defined under the station network.
Hereafter, are listed these attributes:
1.
2.
behaviour on DOU failure (Control refused on faulty board / computer goes in faulty
mode).
3.
4.
5.
C264/EN AP/C80
Page 14/348
Application
MiCOM C264/C264C
Application
C264/EN AP/C80
MiCOM C264/C264C
Page 15/348
Please refer to the C264 IP address and routing table paragraph for details.
C264/EN AP/C80
Page 16/348
4.2
Application
MiCOM C264/C264C
Binder Hardware, that groups all defined boards and printers of the computer.
2.
Binder System infos, that groups all general system datapoints of the computer.
3.
PLC object for Programming Logic Chart that corresponds to ISaGRAF and PSL
project directory.
Application
C264/EN AP/C80
MiCOM C264/C264C
4.3
Page 17/348
2.
rack model (80 TE / 40 TE): there exist two models of computers: C264 and C264C.
The C264 is a large size computer (80TE) and C264C is the compact one (40TE). The
height of both computers is 4U.
3.
date format: this attribute defines the date format used in the computer HMI (LCD).
4.
5.
6.
7.
8.
The "TCP/IP address" value of a device must be unique among all the devices per
Ethernet Network (except for OI server and OI client).
The "network name" value of a device must be unique among all the devices per
Ethernet Network (except for OI server and OI client).
C264/EN AP/C80
Application
Page 18/348
4.3.1
MiCOM C264/C264C
Debouncing: the start transition is signalled with the correct time, the following
changes within the debounce time are ignored. The range of the debounce time is
from 0 to 20 ms (with a 1 ms step). The event is time tagged at the instant of the first
transition.
Filtering: the transition is only signalled if the signal is stable for minimum as long as
the filtering time. The range of the filtering time is from 0 to 20 ms (with a 1 ms step).
The filtering is allowed only if the debouncing is applied (i.e. the filtering cannot be
applied if there is no debouncing before). The event is time tagged at the instant of the
first transition.
Filtering time
Debouncing
time
t0
t1
t2
C0127ENa
one for all Digital Inputs which will be used as Binary Inputs.
one for all Digital Inputs which will be used as Digital Measurements.
2.
Application
C264/EN AP/C80
MiCOM C264/C264C
3.
Page 19/348
A digital input (DI) is said to be toggling if its state has changed more than N
times in a given period of time T1.
A toggling DI returns in the normal state if its state has not changed within
another period of time T2.
4.3.2
If the attribute "debouncing delay" is set to 0, then the attribute "filtering delay" must
be set to 0.
2.
Analogue measurements acquired on AIU board: acquisition samples ranges for long
scanning (range [500 ms, 10000 ms], step 500 ms) and short scanning (range [100
ms, 1000 ms], step 100 ms). For each channel of AIU board, short or long scan period
should be chosen (refer to section 4.4.5 Configuring an AI channel).
3.
4.
Short transmission period on station bus (range [0,.60 s],step 100 ms) and long
transmission period given by a multiple of the short period ([0..600]x short
transmission period).
If the attribute "debouncing delay" is set to 0, then the attribute "filtering delay" must
be set to 0.
C264/EN AP/C80
Application
Page 20/348
4.3.3
MiCOM C264/C264C
debouncing delay and filtering delay: used for digital counters (see 4.3.1 for details)
4.3.4
If the attribute "debouncing delay" is set to 0, then the attribute "filtering delay" must
be set to 0.
4.3.5
Number of software faults allowed in a given period else the computer remains in
HALT mode. Computer reboots automatically as long as it does not reach the fault
max number in the fault detection time period. When this critera is reached computer
remains in HALT mode.
Application
C264/EN AP/C80
MiCOM C264/C264C
4.3.6
Page 21/348
2.
Via the contextual menu of the computer, run Create backup (1).
Then:
Extra relation has for IEC server is automatically created for the main computer.
Once the backup computer has been created, its attributes and constitution are locked
for updating and follow the main computer ones. The only exceptions are its short
name and long name and network identification (IP address and network name) that
must be correctly updated. When an object is added to (resp. removed from ) the main
computer the same object is added to (resp. removed from) the backup computer but
attributes cannot be modified.
C264/EN AP/C80
Page 22/348
Application
MiCOM C264/C264C
Application
C264/EN AP/C80
MiCOM C264/C264C
4.4
4.4.1
Adding boards
Page 23/348
CCU2xx - Mixed digital 8 input and 4 output boards with digital input and output
channels (take good care that the DO 4,5,6,7 are defined but not used):
- Circuit breaker Control Unit
Computer hardware definition is done in SCE by adding typed boards below computer
object. Mandatory boards (CPU260/CPU270, GHU200, BIU241/BIU261) are automatically
created at computers creation.
Linking datapoint to channels corresponds to datapoint wiring.
The addition of a board definition is done via the Objects entry window by clicking on
mouses right button as the following:
C264/EN AP/C80
Application
Page 24/348
MiCOM C264/C264C
BIU
CPU
Slots from C to P may contain a board of the following types: AIU201, AIU211,
AOU200, DOU200, DOU201, DIU20x, DIU210, DIU211 or CCU2xx
Slot Q may contain one TMU200 board or one board of the above types.
If a TMU200/220 is present, then the maximum count of boards must be 14; else the
maximum count of boards must be 15.
BIU
CPU
Slots from C to F may contain a board of the following types: AIU201, AIU211,
AOU200, DOU200, DOU201, DIU20x, DIU211 or CCU2xx
Slots G and H may contain one TMU200/ board or two boards of the above types.
If a TMU200 is present, then the maximum count of boards must be 4; else the
maximum count of boards must be 6.
A C264 is able to manage up to 4 AOU boards and the AOU board cannot be used in
a C264 redundant environment
4.4.2
4.4.2.1
Application
C264/EN AP/C80
MiCOM C264/C264C
Page 25/348
4.4.2.2
Per board type (AIU201, AIU210/AIU211, DOU200, DOU201, DIU20x, CCU2xx), the
physical board number attribute values must begin from 0, be unique and
contiguous.
the default start panel can be bay, defaults, AVR, service, banner; it must be set to
banner if the attribute Login panel present is set to Yes
the attribute Login panel present is set to Yes (Login panel shows after the banner)
or No
the banner must include at least 32 characters (10 char per line at most):
The extra relation has for workspace (1) must be filled. For details
about computer workspace, refer to section 7.2 defining a computer
workspace.
C264/EN AP/C80
Page 26/348
Application
MiCOM C264/C264C
If the value of the "HMI type" attribute is "Simple", then "Led#5" must not be used (no
relation link from "Led#5" to a datapoint).
If the value of the "HMI type" attribute is different from "Complete", then the relation
"has for workspace" must not be linked.
Application
C264/EN AP/C80
MiCOM C264/C264C
4.4.2.3
Page 27/348
short name
2.
3.
4.
reference phase side (Phase A, B, C wired line side / Phase A, B, C wired busbar
side).
5.
6.
nominal current
7.
nominal voltage.
8.
9.
10.
11.
Default voltage reference: as soon as the stated reference phase is valid again,
the TMU locks onto it.
Current voltage reference: the TMU stays locked onto the phase that has a valid
signal.
Unknown: When there is no signal on the TMU, the C264 returns the value
0/self-Check fault on the network: IEC, HMI, Gateway.
Value 0: When there is no signal on the TMU, the C264 returns the value 0 /
Valid on the network: IEC, HMI, Gateway.
During the synchronisation of the TMU frequency, set the related measurement values to 0
/self-Check fault. Do not set the related measurement values to 0 / Valid.
If reference phase signal is absent, values transmitted by TMU board are set to invalid.
Extra attributes are reserved for future use. TMU220 board has the same attributes as
TMU200 except that it has an additional attribute physical board number which is set to 0
by default.
C264/EN AP/C80
Application
Page 28/348
4.4.2.4
MiCOM C264/C264C
2.
3.
reference phase side (Phase A, B, C wired line side / Phase A, B, C wired busbar
side).
4.
5.
nominal and transformer nominal currents (positive and zero sequence) and
nominal and transformer nominal voltages (positive and zero sequence).
6.
(1)
(2)
(3)
(4)
(5)
(6)
Application
C264/EN AP/C80
MiCOM C264/C264C
Page 29/348
BIU board type : choice BIU mono source for BIU241 / BIU dual source for BIU261
For BIU261, Three SPS are available in order to monitor dual source feature.
4.4.3
Voltage source 1: Indicate the presence (SET) of voltage at the right electrical level
on main power supply source.
Voltage source 2: Indicate the presence (SET) of voltage at the right electrical level
on secondary power supply source.
Volt source used: Indicate the secondary power supply in use (SET) / the main
power supply in use (RESET).
C264/EN AP/C80
Application
Page 30/348
4.4.4
MiCOM C264/C264C
2.
3.
2.
baud rate (bits/s) (50 / 100 / 200 / 300 / 600 / 1200 / 2400 / 4800 / 9600 / 19200 /
38400 / 56000 / 64000)
NOTE:
For the CPU260 board with serial ports 3 and 4, this attribute (baud
rate) must be set to the same value. For the CPU270 ports 3 and 4,
the baud rates can be different.
3.
4.
5.
Application
C264/EN AP/C80
MiCOM C264/C264C
6.
Page 31/348
Switched: when the computer has to send a frame it sets the RTS line and
waits for the CTS line to be set by the receiver. It then waits during a time
defined by attribute (9) before starting the transmission of the frame. At the end
of the transmission the computer waits during a time defined by attribute (10)
before resetting the RTS line
Constant: the RTS line is always set by the computer. When it has to send a
frame it waits for the CTS line to be set by the receiver to start the transmission.
Soft: the RTS and CTS line are not managed by the computer.
7.
CTS wired (No / Yes): this attribute must be set to YES if the TX carrier management
attribute is set to Switched or to Constant
8.
CD wired (No / Yes): in order for the DCD line to be managed by the computer this
attribute must be set to YES if the TX carrier management parameter is set to
Switched.
9.
pre TX time (range [0, 1 s], step 1 ms): this attribute is visible and therefore significant
only if attribute (6) is set to Switched.
10. post TX time (range [0, 1 s], step 1 ms): this attribute is visible and therefore significant
only if attribute (6) is set to Switched.
C264/EN AP/C80
Application
Page 32/348
4.4.5
MiCOM C264/C264C
Configuring an AI channel
An AI channel is an analogue input available on AIU201 and AIU21x boards at their creation.
AI channels are used for analogue measurement acquisition.
2.
acquisition period (short period / long period): refer to section 4.3.2 Configuring
measurement acquisition and transmission.
Application
C264/EN AP/C80
MiCOM C264/C264C
4.4.6
Page 33/348
Adding a printer
SCE data modelling describes printers used in PACiS system for sequence of events and
log book functions at operator interface level and computer level.
A printer at computer level must be a serial one connected to a communication channel of
the computer.
To create a computer printer:
Update its has for communication port relation (1) and its attribute printer control (2).
C264/EN AP/C80
Page 34/348
Application
MiCOM C264/C264C
(1)
(2)
(3)
(4)
(5)
(6)
FIGURE 32: UPDATING THE COMMUNICATION PORT RELATION FOR A SERIAL PRINTER
To control the way logging is managed and formatted on a serial printer, updating printer
attributes is necessary:
3.
4.
buffer size (range [100 events, 3000 events ], step 100 events)
5.
number of events to suppress when buffer is saturated (.range [30 events, 1000
events ], step 10 events)
6.
The following constraint must be respected: buffer size > nb of events to suppress
when saturated
Application
C264/EN AP/C80
MiCOM C264/C264C
Page 35/348
Hereafter an extract of logging that illustrates the different columns used for printing formats:
C264/EN AP/C80
Application
Page 36/348
4.4.7
MiCOM C264/C264C
Configuring an AO channel
An AO channel is an analogue output available on AOU200 at their creation in SCE.
Maintained mode: in case of computer shut down or power off, the output level is
maintained (and the Read inhibit relay is set). Only the reception of a new set point will
lead to an output value modification.
Un-maintained Mode: in case of computer shut down or power off, the output is set
to 0.
2.
Application
C264/EN AP/C80
MiCOM C264/C264C
4.5
Page 37/348
4.5.1
192.168.10.0
192.168.10.99
192.168.20.99
PACiS
192.168.20.0
192.168.20.1
subnet mask 255.255.255.0
192.168.20.98
192.168.30.12
C0426ENa
C264/EN AP/C80
Application
Page 38/348
4.5.1.2
MiCOM C264/C264C
In the example the C264 have address 192.168.20.1 and subnet mask 255.255.255.0
(default value) he is able to reach all equipment with address 192.168.30.x.
4.5.1.4
Application
C264/EN AP/C80
MiCOM C264/C264C
Page 39/348
Example: 10.22.92.52
This field can have an optional subnet mask of the form inet_adrs:subnet_mask.
Example:
10.22.92.52:0xFFFF0000
10.22.92.52:0xFF000000
4.5.1.7
C264/EN AP/C80
Application
Page 40/348
4.5.2
MiCOM C264/C264C
In this example, C264 must have address 192.168.20.1 and SubNetwork mask must be set
to 255.255.0.0; it will accept connection from SCADA 192.168.30.4
4.5.3
Application
C264/EN AP/C80
MiCOM C264/C264C
Page 41/348
In this example, the IP address for the SCADA DNP-IP protocol defined for the client1
(192.168.30.1) is configured in the SCE as figure below:
C264/EN AP/C80
Page 42/348
4.6
Application
MiCOM C264/C264C
4.6.1
Application
C264/EN AP/C80
MiCOM C264/C264C
Page 43/348
When adding the has for IEC61850 server relation to computer (A), a specific attribute of
the relation, modelling/goose usage (1), can be set to precise the way data are transmitted
from server (B) to computer (A). There are three possibilities:
Goose only.
Basically, the Report mode is used to transmit filtered data for displaying, printing and
archiving. The Goose mode is used to transmit data as soon as possible after their
acquisition and as quickly as possible, for automation purpose.
Goose transmission must be used if computer (A) uses BIs served by computer (B), for
ISaGRAF, FBD or interlock computation (refer to section 6.7 Defining an electrical regulation
by user function).
During a loss of communication between a client and a server, all server BIs are set to
UNKNOWN on the client.
Configuration rules and checks
A client must not be linked to the same server through multiple relations "has for
IEC61850 server".
the state and quality (the BI resulting state is split in state and quality on IEC-61850)
the reason for change, which could be one of the below values:
change of data (set if the state has changed, before persistence or motion filtering)
change of quality (set if the quality has changed, before persistence or motion
filtering)
change due to control (set if the state or quality change is due to a control)
From one server, all BI reports are not transmitted in a chronological order (it is an IEC61850 client feature to put, if needed, all information in a chronological order).
During a loss of communication, the events detected on the computer are not buffered.
GOOSE based mode
A BI (only SPS and DPS) can be configured to be transmitted in GOOSE mode. In this
mode, the change of status is transmitted in multicast to the configured receivers. Only the
BI unfiltered states are transmitted, the time stamping and the reason for change are not.
C264/EN AP/C80
Application
Page 44/348
MiCOM C264/C264C
Due to GOOSE format, all BI resulting states given below cannot be transmitted. So, the
following mapping is applied:
BI Resulting State
GOOSE value
01
10
00
11
Application
C264/EN AP/C80
MiCOM C264/C264C
4.6.2.1
Page 45/348
C264/EN AP/C80
Application
Page 46/348
MiCOM C264/C264C
Some datapoints are out of scope of automatic addressing. Theses datapoints are
identified by their data model mnemonic and their short name. They are listed in the
following table:
Excluded datapoints
Parent object
mnemonic
Module Circuit breaker
name
SynCheck_Close_DPC
Sync CB close
SynCheck_Close_SPC
Sync CB close
Select_SPC
Selection SPC
Switch_SPC_PhA
Switch_SPC_PhB
Switch_SPC_PhC
SwitchPos_PhA (DPS)
SwitchPos_PhB (DPS)
SwitchPos_PhC (DPS)
SwitchPos_SPS_PhA
SwitchPos_SPS_PhB
SwitchPos_SPS_PhC
SwitchPos (DPS)
Switchgear pos.
SwitchPos_SPS
Switchgear pos.
PhaseNotTogether_SPS
Ph not together
External automatic
synchrocheck built-in function
CS_CtrlOnOff_DPC
CS_CtrlOnOff_SPC
XX_thresholdY_trip
XX tY trip
examples:
46 t1 trip
67 t3 trip
XX tY in di rev
examples:
67 t1 in dir rev
67 t3 in dir rev
XX tY interlock
example:
67 t1 interlock
Relay [automatism]
start_disturbance
49_trip_th_overload
49 trip th over.
Application
C264/EN AP/C80
MiCOM C264/C264C
mod Vo (ADC)
mod I1 (ADC)
mod I2 (ADC)
mod V1 (ADC)
mod V2 (ADC)
thermal status
NOTE:
4.6.2.2
Page 47/348
DBID (DataBase
management,
C26xDIAG brick.
IDentity)
used
for
computer
databases
identification
and
For each IED connected to a PACiS computer via an IED legacy network, an implicit
IEDDIAG (diagnostic for the IED) brick exists, and an extra brick RDRE (for
disturbance information) can be added.
Be careful, when creating an IED on a computer legacy network, its IEDDIAG brick
name must be updated to avoid double values of bricks in the computer LD0.
C264/EN AP/C80
Application
Page 48/348
MiCOM C264/C264C
LD0 extension
for IED
optional RDRE
brick for IED
C0172ENa
An extra brick RDRE (for disturbance information) can be added in LD0 of the
computer if it manages its own disturbance file.
standard LD0
for computer
optional
RDRE brick
for computer
C0174ENa
Application
C264/EN AP/C80
MiCOM C264/C264C
Page 49/348
C26xDIAG brick:
Description
Comment
Mod
INC
Mandatory
Beh
INS
Behaviour
Mandatory
Health
INS
Health
Mandatory
NamPlt
LPL
Name plate
SyncSt
SPS
Mandatory
stVal =0= non-synchronised
stVal =1= synchronised
AllBIUSt
SPS
AllCCUSt
SPS
AllDIUSt
SPS
AllDOUSt
SPS
AllAIUSt
SPS
AllAOUSt
SPS
AllCOMMSt
SPS
AllIEDSt
SPS
GHUSt
INS
(INS8_ST)
stVal =0= OK
stVal =1= self-check failure
stVal =2= configured but missing
stVal =3= not configured but present
stVal =4 = missing
BIUSt
Idem GHUSt
CCUSt<15>
Idem GHUSt
DIStop
SPS
DIUSt<15>
Idem GHUSt
DOUSt<15>
Idem GHUSt
AIUSt<6>
Idem GHUSt
AOUSt<4>
Idem GHUSt
TMUSt
PrintSt
RedSt
SPS
Idem GHUSt
stVal = 0 => OK
stVal = ???
stVal = 0 => StandBy
stVal = 1 => Active
FailSt
PLCSt
urcbST
URCB
Redundancy Mode
Unbuffered
C264/EN AP/C80
Application
Page 50/348
Object name
Mod
Beh
Health
NamPlt
BIUSt
CDC
INC
INS
INS
LPL
INS
(INS8_ST)
CCUSt<15>
DIStop
DIUSt<15>
DOUSt<15>
AIUSt<6>
AOUSt<4>
TMUSt
CommIRSt
INS (INS8_ST)
SPS
INS (INS8_ST)
INS (INS8_ST)
INS (INS8_ST)
INS (INS8_ST)
INS (INS8_ST)
SPS
PLCSt
urcbST
MiCOM C264/C264C
Description
Device Mode (status only)
Behaviour
Health
Name plate
BIU 240 status
Comment
Mandatory
Mandatory
Mandatory
Mandatory
stVal =0= OK
stVal =1= self-check failure
stVal =2= configured but missing
stVal =3= not configured but present
stVal =4 = missing
Idem GHUSt
Idem GHUSt
Idem GHUSt
Idem GHUSt
Idem GHUSt
Not managed.
stVal = 0 => failure
stVal = 1 => OK
Unbuffered
FIGURE 51: SYSTEM FOR MICOM C264 WITH HARDWARE EXTENSION (SCE)
Application
C264/EN AP/C80
MiCOM C264/C264C
4.6.2.3
Page 51/348
At OI level:
System and electrical process supervision and control (mimic animation, control
popup),
At SMT level:
Feeding PACiS Gateway acquisition to transmit data between PACiS system and
SCADA,
To insure real-time data exchange on station-bus, specific logical devices (called here
application logical devices) must be created in the IEC61850 mapping of the PACiS subsystem that is server of the exchanged data (for definition of client/server, see chapter
4.6.1 Connecting computer to other station-bus sub-systems). PACiS MiCOM C264 is the
only PACiS sub-system that allows user-defined application logical devices.
The general philosophy to create manually application logical devices is:
in each application logical device, one brick per module or function contained in the
bay,
for each brick, one data object per datapoint contained in the module/function, that
needs to be exchanged on the station-bus. In a brick, data object are grouped by
functional component. Datapoint addressing on station-bus network is done via linking
datapoint to the relevant IEC61850 data object. Available associations between type
of datapoint and type of IEC61850 data object are described in the following table.
C264/EN AP/C80
Application
Page 52/348
MiCOM C264/C264C
Type of datapoint
SI
DPS
SIT
MPS
SIG
MV
Counter
ACCI
SPC
BO
DPC
DCO
SetPoint
AO
update its IEC name attribute (1), that must be unique for a given IEC61850 mapping.
(1)
For each Logical Device defined under the IEC61850/IEC mapping, its name must be
unique in the mapping.
if the Logical Device is a generic one, its name must not contain the sub-string "LD0"
(reserved for system Logical Devices).
Application
C264/EN AP/C80
MiCOM C264/C264C
Page 53/348
add GenLNxx from object entry available at IEC61850 logical device level; do not
use RDRE brick reserved for non-PACiS IEC61850 IED.
update its IEC61850 name attribute (1), that must be unique for a given IEC61850
logical device.
(1)
optional wrapper (up to 6 characters), that can not begin with a digit.
Each part is made with the following characters: 0-9, a-z, A-Z.
Configuration rules and checks
For each Brick defined under a Logical Device, its name must be unique in the Logical
Device.
C264/EN AP/C80
Page 54/348
Application
MiCOM C264/C264C
CO to group controls,
SV to group setpoints,
add specific data object from object entry available at IEC61850 functional component
level. Each kind of functional components owns its own available list of data objects.
The following table shows the different lists useful for MiCOM C264 IEC61850
mapping:
Application
C264/EN AP/C80
MiCOM C264/C264C
Page 55/348
Functional component
ST
ACDxST
ACDxSTPhs
ACTxST
ACTxSTPhs
BCRxST
BCSxST
BCSxORxST
DPCxST
DPCxORxST
DPSxST
INC8xST
INCxST
INCxORIGxST
INS8xST
INSxST
SPCxORxST
SPCxST
SPSxST
MX
APCxMX
APCxORxMX
CMVxMX
DELxMX
MVxMX
WYExMX
CO
APCxDir
APCxSBOxS
BSCxDir
BSCxSBOxS
INCxDir
SPCDPCxDir
SPCDPCxSBO
SV
BSCxSV
CMVxSV
DELxSV
SPCxSV
DPSxSV
INSxSV
MVxSV
SPCxSV
SPSxSV
WYExSV
CF
APCxCF
BCRxCF
BSCxCF
DELxCF
DirectxCF
DPCxCF
MVxCF
SPCxCF
WYExCF
C264/EN AP/C80
Application
Page 56/348
MiCOM C264/C264C
update its IEC61850 name attribute (1), that must be unique for a given IEC61850
functional component.
(1)
4.6.2.4
For each Data Object defined under a Functional Component (CO), its name must be
unique in the Functional Component.
For the following Functional Component types of a MiCOM C264: CO, MX and ST, the
maximum count of Data Objects is 50.
Application
C264/EN AP/C80
MiCOM C264/C264C
Page 57/348
processed and finally slow automation datapoints. An event of GOOSE buffer overflow is
signalled and stops the process of GOOSE addressing. For details about Goose modelling /
configuration see further).
(1)
(1)
C264/EN AP/C80
Application
Page 58/348
MiCOM C264/C264C
Suppose you have generated the database 1.0 for IED1 only. After adding IED2, you
generate a version 1.1.
SBUS IEC61850
n
In regular text is the
content of the goose
ST message
broadcast over
IEC61850 with the
C264 database 1.0
Goose ST message:
<DATASET>
<FCDA SPS1.stVal>
<FCDA SPS1.q>
<FCDA SPS2.stVal>
<FCDA SPS2.q>
<FCDA SPS3.stVal>
<FCDA SPS3.q>
C264
IED1:
IED2:
q
SPS1
sent as
goose
to
IED1
SPS2
sent as
goose
to
IED2
SPS3
sent as
goose
to
IED1
The defined 'goose rank' is not updated if the DtObj is still 'transmitted by goose' (that
is either goose transmission attribute is set to Yes),
The undefined 'goose rank' is ranked after the last used rank for the whole 61850
mapping,
The defined 'goose rank' is reset with an undefined value (0) if the DtObjs is NOT
'transmitted by goose'.
Application
C264/EN AP/C80
MiCOM C264/C264C
Page 59/348
In this event, do a check of the configuration and fix it manually (see the SCE/ EN MF
chapter).
NOTE:
You can check the box reset of goose rank' to forcefully reset ALL of the Goose ranks of
61850 mapping at the current level in the treelike structure: they are reset with an undefined
value (as they are not goosed anymore) & all the remaining goose ranks are re-computed in
a new order.
Typical update cycle of data objects:
C264/EN AP/C80
Application
Page 60/348
4.6.3
MiCOM C264/C264C
Doing a manual addressing, by adding at datapoint level the relation has for
IEC61850 address (1) and filling it with the corresponding IEC61850 data object in a
pre-configured IEC61850 addressing mapping:
(1)
automatic linking between data objects in this IEC61850 mapping and datapoints
managed by the MiCOM C264.
Application
C264/EN AP/C80
MiCOM C264/C264C
Page 61/348
4.7
4.7.1
4.7.1.1
Add a legacy network relevant to a specific protocol from object entry available at
computer level (1),
Update its has for main comm. port relation and the communication port
characteristics (see section 4.4.4 Configuring a communication channel),
C264/EN AP/C80
Page 62/348
4.7.1.3
Application
MiCOM C264/C264C
number of retries (range [1, 10]): number of tries of the same frame without IED
response, the computer will send it before setting it disconnected.
2.
acknowledgement time-out (range [100 ms, 30 s], step 100 ms): maximum delay an
IED answer is awaited when the computer asks it a information.
3.
synchronisation cycle (range [10 s, 655350 s]): time synchronisation period of the IED
by the computer.
4.
downgraded cycle (range [1 s, 10 s], step 100 ms): if an IED is set disconnected by
the computer, it tries to re-connect it regularly at this cycle.
5.
inter frame duration (range [1 , 50 ], step 1): this attribute represents the minimum
time, expressed in number of characters, that must exist between two frames.
number of retries (range [1, 10], step 1): corresponds to the number of tries of the
same frame without IED response, the computer will send it before setting it
disconnected.
2.
station address size (range [1 byte, 2 bytes]): size of the IED addresses
3.
4.
info address size (range [1 byte, 3 bytes]): size of the information addresses.
5.
transmission cause size (range [1 byte, 2 bytes]): size of the transmission cause.
6.
frame length (range [64 bytes, 255 bytes]): if an IED cannot manage frame whose
length is superior to 255, the frame length attribute must be set to the available length
for the IED.
7.
acknowledgement time-out (range [100 ms, 30 s], step 100 ms): maximum delay an
IED answer is awaited when the computer asks it an information.
8.
synchronisation cycle (range [10 s, 655350 s], step 10 s): time synchronisation period
of the IED by the computer.
9.
downgraded cycle (range [1 s, 10 s], step 100 ms): if an IED is set disconnected by
the computer, it tries to re-connect it regularly at this cycle.
10. Type of link (Balanced / Unbalanced): if unbalanced link, only master (here computer)
asks IED. If balanced link, IED can also ask the master (here computer) without
solicitation.
11. test frame time-out (range [1 s, 255 s], step 1 s): in case of balanced link (cf. attribute
(10)), a life message (test frame) is sent periodically between computer and IED. This
attribute corresponds to maximum delay to receive this life message, to computers
point of view. If no reception within this delay, IED is set disconnected.
Application
C264/EN AP/C80
MiCOM C264/C264C
12.
Page 63/348
inter frame duration (range [1, 50 ], step 1): this attribute represents the minimum
time, expressed in number of characters, that must exist between two frames.
number of retries (range [1, 10], step 1): corresponds to the number of tries of the
same frame without IED response, the computer will send it before setting it
disconnected.
2.
acknowledgement time-out (range [100 ms, 30 s], step 100 ms): maximum delay an
IED answer is awaited when the computer asks it an information.
3.
4.
synchronisation cycle (range [10 s, 655350 s], step 10 s): time synchronisation
period of the IED by the computer. Only significant if attribute (3) is set to
Schneider Electric, 'Flexgate' or to 'SEPAM'. To keep the Px4x synchronised, C264
must send the frame at least every 5 minutes; therefore the value must be lesser than
30 in this case.
5.
downgraded cycle (range [1 s, 10 s], step 100 ms): if an IED is set disconnected by
the computer, it tries to re-connect it regularly at this cycle.
6.
inter frame duration (range [1, 50], step 1): this attribute represents the minimum
time, expressed in number of characters, that must exist between two frames.
Schneider Electric
C264/EN AP/C80
Page 64/348
4.7.1.6
Application
MiCOM C264/C264C
2.
acknowledgement time-out (range [100 ms, 30 s], step 100 ms): maximum delay an
IED answer is awaited when the computer asks it a information.
3.
number of retries (range [1, 10], step 1): corresponds to the number of tries of the
same frame without IED response, the computer will send it before setting it
disconnected.
4.
application time-out (range [0 s, 255 s], step 1 s): time-out used by the computer, at
application layer of DNP3 protocol.
5.
class 0 polling period (range [0 s, 3600 s], step 1 s): emission period of the general
request message. If this attribute equals zero, no general request message is sent.
6.
synchronisation cycle (range [10 s, 655350 s], step 10 s): time synchronisation period
of the IED by the computer.
7.
downgraded cycle (range [1 s, 10 s], step 100 ms): if an IED is set disconnected by
the computer, it tries to re-connect it regularly at this cycle.
8.
inter frame duration (range [1, 50], step 1): this attribute represents the minimum time,
expressed in number of characters, that must exist between two frames.
Application
C264/EN AP/C80
MiCOM C264/C264C
4.7.1.7
Page 65/348
Add an IED from object entry available at Legacy networks level (1).
For DNP3, T103, or Mobdus IED, update the has for acquisition profile relation with a
previously created IED acquisition type.
short name and long name: used for correct logging and alarm discrimination
concerning IED status datapoint.
2.
3.
4.
localisation for disturbance file: non-significant for DNP3 IED, used for basic file
name upload by SMT on OWS hard disk: <localisation>_N#.
C264/EN AP/C80
Page 66/348
Application
MiCOM C264/C264C
4.7.1.9
For each IED, its "network address" and "short name" attributes value must be unique,
per Legacy Network.
Add an IED acquisition from object entry available at legacy network level (1).
Update the IED acquisition type attributes relevant to its protocol characteristics.
For each computer and all its Legacy Networks, the maximum count of "xxx acq type"
components is 10.
Application
C264/EN AP/C80
MiCOM C264/C264C
4.7.1.10
Page 67/348
IED type (T103 standard IED / Px3x Serie / Px2x Serie / REG-D / Tapcon 240)
2.
function type (range [0, 255]: function type number used for acquisition: see IED
documentation to set correctly this attribute
3.
general interrogation period (range [0, 24 h], step 1 s): cycle used to fetch regularly
statuses and measurements from IED and to avoid loss of event information
4.
MV reduction coefficient (1.2 / 2.4 ): used for scaling (ASDU 3 usage): refer to T103
documentation for details about this scaling
5.
Four sets of three nominal values (voltage, current and frequency) used for scaling.
Refer to International Standard IEC 60870-5-103 for details about this scaling.
C264/EN AP/C80
Application
Page 68/348
4.7.1.11
MiCOM C264/C264C
IED type:
2.
3.
mapping address (range [0, 232-1]): associated to attribute (2), it gives which start
address is used to test the IED connection
Pro
M10,
ABB
Flexgate,
SEPAM
(Specific
Modbus
size to read (range [0, 2048]: associated to attribute (3), it gives which length is used
to test the IED connection.
if MODBUS function is set to 1 or 2 this attributes defines a number of bits
if MODBUS function is set to 3 or 4 this attributes defines a number of words
if MODBUS function is set to 7 or 8 this attributes is not significant
5.
data frame length (range [2 bytes, 256 bytes]): if an IED cannot manage frames
longer than 256 bytes, this attribute must be set to the available length for the IED.
Application
C264/EN AP/C80
MiCOM C264/C264C
4.7.1.12
Page 69/348
global class usage (No / Yes): used for addressing. Not yet implemented. Always
considered as yes at computer level.
2.
3.
CROB parameters (Usage of 'code' field / Usage of 'Trip/Close' field / Usage of 'code'
and 'trip/close' fields):
C264/EN AP/C80
Page 70/348
Application
MiCOM C264/C264C
Application
C264/EN AP/C80
MiCOM C264/C264C
4.7.2
Page 71/348
DNP3: address identification is given by the attribute "address" of the "xxx addr. on
IED".
C264/EN AP/C80
Page 72/348
4.7.2.1
Application
MiCOM C264/C264C
FIGURE 80: ADDING AN IED SPS ADDRESS (E.G. FOR T101 IED)
Once added, IED SPS address attributes must be set at SCE level:
1.
mapping address (range [0, 65535], step 1): word address or bit address depending
on the function
3.
bit number (range [0, 65535], step 1): used only if word read or status read is used
4.
function (range [0, 65535], step 1): number of the Modbus function used to read the
SPS:
- 1, 2: read bit,
- 3, 4: read word,
- 7 : read status
6.
common address of ASDU (range [-1, 65535],step 1): by default (1) is equal to IED
address (see section 4.7.1.8 Setting attributes of a legacy IED).
8.
9.
10.
common address of ASDU (range [-1, 65535],step 1): by default (1) is equal to IED
address (see section 4.7.1.8 Setting attributes of a legacy IED.).
Application
C264/EN AP/C80
MiCOM C264/C264C
For DNP3 protocol:
11. address (range [0, 65535],step 1).
Page 73/348
C264/EN AP/C80
Page 74/348
4.7.2.2
Application
MiCOM C264/C264C
FIGURE 82: ADDING AN IED DPS ADDRESS (E.G. FOR T101 IED)
Once added, IED DPS address attributes must be set at SCE level:
1.
mapping address (range [0, 65535], step 1): Word address or Bit address depending
on the function.
3.
bit number (range [0, 65535], step 1): Used only if Word read or status read is used
4.
function (range [0, 65535], step 1): Modbus function to use to read the DPS:
- 1, 2: read bit,
- 3, 4: read word,
- 7 : read status
6.
common address of ASDU (range [-1, 65535],step 1): by default (1) is equal to IED
address (see section 4.7.1.8 Setting attributes of a legacy IED).
8.
9.
10.
common address of ASDU (range [-1, 65535],step 1): by default (1) is equal to IED
address (see section 4.7.1.8 Setting attributes of a legacy IED).
Application
C264/EN AP/C80
MiCOM C264/C264C
Page 75/348
For all protocol types, DPS acquisition on IED can also be done via two different addresses.
In that case, two DPS address on IED must be created for this DPS. For each of them, the
attribute contact identifier (12) must be set to Open or Closed, to precise which state of
the DPS is concerned by the IED address. If DPS status is given by only one IED address,
set contact identifier value to unused.
C264/EN AP/C80
Page 76/348
Application
MiCOM C264/C264C
3.
function (range [0, 65535], step 1): Modbus function to use to read the MV:
- 3, 4: read word,
- 7 : read status
4.
data format: see following paragraph (Measurement formats that can be used with
the MODBUS protocol).
6.
common address of ASDU (range [-1, 65535],step 1): by default (1) is equal to IED
address (see section 4.7.1.8 Setting attributes of a legacy IED).
8.
9.
10.
11.
common address of ASDU (range [-1, 65535],step 1): by default (1) is equal to IED
address.
12.
13.
For this protocol it is possible to perform acquisition of measurements only using the Generic
Services of IEC 60870-5-103 protocol by polling. This can be done by setting some
parameters as follows:
ASDU number: 21
index in the ASDU: Generic Identification Number given by the mapping of the IED
Application
C264/EN AP/C80
MiCOM C264/C264C
Page 77/348
C264/EN AP/C80
Page 78/348
Application
MiCOM C264/C264C
Description
Transmission order
INT8_LB
INT8_HB
UINT8_LB
UINT8_HB
INT16
2-1
UINT16
2-1
INT32_LW_LB
1-2-3-4
INT32_LW_HB
2-1-4-3
INT32_HW_LB
3-4-1-2
INT32_HW_HB
4-3-2-1
UINT32_LW_LB
1-2-3-4
UINT32_LW_HB
2-1-4-3
UINT32_HW_LB
3-4-1-2
UINT32_HW_HB
4-3-2-1
REAL32_LW_LB
1-2-3-4
Application
C264/EN AP/C80
MiCOM C264/C264C
Page 79/348
Format
Description
Transmission order
REAL32_LW_HB
2-1-4-3
REAL32_HW_LB
3-4-1-2
REAL32_HW_HB
4-3-2-1
M230_T5_TYPE
4-3-2-1
4-3-2-1
4-3-2-1
4-3-2-1
ION_MODULUS_
10000_signed
4-3-2-1
C264/EN AP/C80
Page 80/348
4.7.2.4
Application
MiCOM C264/C264C
FIGURE 85: ADDING AN IED COUNTER ADDRESS (E.G. FOR T101 IED)
Once added, an IED Counter address attributes must be set at SCE level:
1.
3.
fonction (range [0, 65535],step 1): Modbus function used to read the MV:
- 3, 4: read word
4.
6.
common address of ASDU (range [-1, 65535], step 1): by default (1) is equal to IED
address.
8.
9.
10.
11.
Application
C264/EN AP/C80
MiCOM C264/C264C
Page 81/348
C264/EN AP/C80
Page 82/348
4.7.2.5
Application
MiCOM C264/C264C
FIGURE 87: ADDING AN IED SPC ADDRESS (E.G. FOR T101 IED)
Once added, IED SPC address attributes must be set at SCE level:
1.
mapping address (range [0, 65535],step 1): Bit address for function 5 or 15, Word
address for function 6.
3.
bit number (range [0, 65535],step 1): Used only if Function 6 is used (see function
attribute).
4.
function (range [0, 65535],step 1): Modbus function to use to send the SPC:
- 5: write 1 bit (Mapping address indicates the address of the bit),
- 6: write 1 word (Mapping address indicates the address of the word, bit number
indicates the number of the bit in the word),
- 15: write N bits (used to set only 1 bit at a time, Mapping address indicates the
address of the bit)
6.
common address of ASDU (range [-1, 65535],step 1): by default (1) is equal to IED
address.
8.
9.
Application
C264/EN AP/C80
MiCOM C264/C264C
Page 83/348
C264/EN AP/C80
Page 84/348
4.7.2.6
Application
MiCOM C264/C264C
FIGURE 89: ADDING AN IED DPC ADDRESS (E.G. FOR T101 IED)
Once added, IED DPC address attributes must be set at SCE level:
1.
mapping address (range [0, 65535],step 1): Bit address for function 5 or 15, Word
address for function 6.
3.
bit number (range [0, 65535],step 1): used only if Function 6 is used (see function
attribute).
4.
function (range [0, 65535],step 1): Modbus function to use to send the DPC:
- 5: write 1 bit (Mapping address indicates the address of the bit),
- 6: write 1 word (Mapping address indicates the address of the word, bit number
indicates the number of the bit in the word),
- 15: write N bits (used to set only 1 bit at a time, Mapping address indicates the
address of the bit)
6.
common address of ASDU (range [-1, 65535],step 1): by default (1) is equal to IED
address.
8.
9.
Application
C264/EN AP/C80
MiCOM C264/C264C
Page 85/348
contact type (open / close / unused): For all protocol type, DPC control on IED can
also be done via two different addresses. In that case, two DPC address on IED must
be created for this DPC. For each of them, this attribute must be set to Open or
Close, to precise which order of the DPC is concerned by the IED address. If DPC
control is given by only one IED address, set contact type value to unused.
C264/EN AP/C80
Page 86/348
4.7.2.7
Application
MiCOM C264/C264C
FIGURE 91: ADDING AN IED SETPOINT ADDRESS (E.G. FOR T101 IED)
Once added, IED SetPoint address attributes must be set at SCE level:
1.
mapping address (range [0, 65535],step 1): Word address for function 6.
3.
function (range [0, 65535],step 1): Modbus function to use to send the SetPoint:
- 6: write 1 word (Mapping address indicates the address of the word, bit number
indicates the number of the bit in the word).
5.
SetPoint address on T103 is only available for REGD relay, where output format is
configurable.
7.
8.
9.
10.
For all protocol type, values of SetPoint control on IED must be verified and scaled
depending on output format, before transmission. This is done via two extra attributes
minimal value (11) and maximal value (12).
Application
C264/EN AP/C80
MiCOM C264/C264C
Page 87/348
C264/EN AP/C80
Application
Page 88/348
4.7.3
MiCOM C264/C264C
DP type
Counter
xPC
xPS
MV
Set
point
Identifier
DNP3
ModBus
T103
T101
basic address
default
address
Mapping
address
ASDU number
Not used
extra address #1
default
Not
used
Not used
fonction type
Not used
extra address #2
default
Not
used
fonction
information number
Information object
address
extra address #3
default
Not
used
Not used
common address
of ASDU
extra address #4
default
Not
used
Not used
common address of
ASDU
Not used
basic address
address
Mapping
address
ASDU number
Not used
extra address #1
default
Not
used
bit number
fonction type
Not used
extra address #2
default
Not
used
fonction
information number
Information object
address
extra address #3
default
Not
used
Not used
Not used
common address
of ASDU
basic address
address
Mapping
address
ASDU number
Not used
extra address #1
default
Not
used
bit number
fonction type
Not used
extra address #2
default
Not
used
fonction
information number
Information object
address
extra address #3
default
Not
used
Not used
common address of
ASDU
common address
of ASDU
basic address
address
Mapping
address
ASDU number
Not used
extra address #1
default
Not
used
Not used
fonction type
Not used
extra address #2
default
Not
used
fonction
information number
Information object
address
extra address #3
default
Not
used
Not used
Not used
extra address #4
default
Not
used
Not used
common address of
ASDU
common address
of ASDU
basic address
address
Mapping
address
ASDU number
Not used
extra address #1
default
Not
used
bit number
fonction type
Not used
extra address #2
default
Not
used
fonction
information number
Information object
address
extra address #3
default
Not
used
Not used
common address of
ASDU
common address
of ASDU
Application
C264/EN AP/C80
MiCOM C264/C264C
Page 89/348
4.8
4.8.1
4.8.1.1
Add a SCADA network from object entry available at computer level (1),
Update the SCADA network attributes relevant to its protocol characteristics (see
section 4.8.2 Defining addressing mapping of SCADA network).
If SCADA does not use the substation network to communicate with the computer,
update its has for main communication port relation and the communication port
characteristics.
For DNP3 and T101 protocol on serial line, SCADA link can be redundant. To create a
redundant SCADA link, just add the relation has for auxiliary communication port (2)
extra relation on computer SCADA network and fill it with the relevant serial port.
A computer can manage up to two T104 SCADA clients. These two clients have
separate configurations but may have same data. On the SCADA port, up to four front
ends can be defined, corresponding to one active port and three backup ports. So, up
to four IP addresses will be defined during the configuration of each T104 client
(attributes (13) in section 4.8.1.6 Setting specific attributes of a T104 SCADA
network). If both clients are communicating with the computer, they must manage
thein own redundancy for doing controls with coherency.
C264/EN AP/C80
Application
Page 90/348
MiCOM C264/C264C
redundancy type (Active line after GI received / Active line after Reset line received /
Active line on traffic):
4.
Application
C264/EN AP/C80
MiCOM C264/C264C
4.8.1.4
Page 91/348
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
interframe duration (range [1, 50], step 1): this attribute represents the minimum
time, expressed in number of characters, that must exist between two frames
15.
16.
17.
SOE file address: this attribute is visible and significant only if attribute SOE file
support is set to Yes
18.
SOE file format (T101 / S900) this attribute is visible and significant only if attribute
SOE file support is set to Yes
19.
SOE file nb of events (range [0, 1000], step 1) this attribute is visible and significant
only if attribute SOE file support is set to Yes
20.
'full' SOE file nb of events (range [0, 1000], step 1) file message sent to SCADA
(this attribute is visible and significant only if attribute SOE file support is set to Yes)
21.
22.
C264/EN AP/C80
Page 92/348
Application
MiCOM C264/C264C
FIGURE 96: SETTING PROTOCOL AND SOE ATTRIBUTES OF A T101 SCADA NETWORK
Configuration rules and checks
The
following
constraints
between
the
attributes
"SOE file nb of events" > "'full' SOE file nb of events".
4.8.1.5
must
be
respected:
Application
C264/EN AP/C80
MiCOM C264/C264C
Page 93/348
TCP/IP usage (No / Yes): set to Yes substation network is used by the DNP3-IP
SCADA to communicate with the computer
2.
3.
SPS/DPS class (1 / 2 / 3)
4.
MV class (1 / 2 / 3)
5.
SPS/DPS class (1 / 2 / 3)
6.
Counter class (1 / 2 / 3)
7.
8.
9.
10.
11.
12.
13.
SBO time-out: maximum time between select orde and execute order
14.
inter frame duration (range [1, 50], step 1): this attribute represents the minimum
time, expressed in number of characters, that must exist between two frames
15.
spontaneous message enable (No / Yes): this attribute defines if the unsolicited
mode is allowed or not for the protocol. If this attribute is set to No there is possibility
to allowed it from the SCADA. If this attribute is set to Yes the computer can send
unsolicited messages as soon as the SCADA is initialiazed. Furthermore the SCADA
may disable or enable this unsolicited mode.
16.
spontaneous message class (none / class 1 / class 2 / class 1 & 2 / class 3 / class 1
& 3 / class 2 & 3 / class 1 & 2 & 3): This attribute is only significant if the previous
attribute is set to Yes. This attribute defines which class(es) is (are) concerned by this
unsolicited mode.
Setting SOE information SOE tab-panes, for DNP3-IP SCADA network is not significant (not
implemented).
C264/EN AP/C80
Page 94/348
4.8.1.6
Application
MiCOM C264/C264C
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
18.
SOE file address (this attribute is visible and significant only if attribute SOE file
support is set to Yes)
19.
SOE file format (T101 / S900) (this attribute is visible and significant only if attribute
SOE file support is set to Yes)
20.
SOE file nb of events (range [0, 1000], step 1) (this attribute is visible and significant
only if attribute SOE file support is set to Yes)
21.
'full' SOE file nb of events (range [0, 1000], step 1) file message sent to SCADA
(this attribute is visible and significant only if attribute SOE file support is set to Yes)
Application
C264/EN AP/C80
MiCOM C264/C264C
Page 95/348
C264/EN AP/C80
Page 96/348
4.8.1.7
Application
MiCOM C264/C264C
2.
link address.
3.
inter frame duration (range [1 , 50 ], step 1): this attribute represents the minimum
time, expressed in number of characters, that must exist between two frames.
For a MODBUS SCADA network, the SOE tab-panes attributes are not significant (not
implemented).
Application
C264/EN AP/C80
MiCOM C264/C264C
4.8.2
Page 97/348
4.8.2.1
In the SCADA Mapping, the address identification of each "Gtw xxx addr." must be
unique. In the particular cases of T101 and T104 protocols, the uniqueness constraint
is applicable only for addresses of the same type. Addresses of different types can
have identical addresses and therefore this does not lead to an error but to a warning.
On a DNP3 protocol, a "Gtw MV addr.", which is the SCADA address of a "Tap pos
ind" datapoint, must have its "Format" attribute set to the "Natural" value.
C264/EN AP/C80
Application
Page 98/348
MiCOM C264/C264C
object address.
4.
Event (No / Yes with time tag / Yes witout time tag): when set to Yes with time tag,
indicates that change of state of the datapoint are transmitted spontaneously with time
Tag.
5.
Event record ( Does not involved in a transfert of file / Create a RECORD EVENT if
there is not it current / Add to the current record EVENT / Create a RECORD EVENT
and adds to the current record EVENT): when set to a value different from Does not
involved in a transfer of file, indicates if change of state of the datapoint must be
saved in Sequence of Event file. At computer level, values different from Does not
involved in a transfer of file are associated to the same treatment, because only one
SOE file is managed by computer. The set of available values is maintained for
compatibility with MiCOM gateway addressing in MiCOM gateway.
6.
Inversion (No / Yes): Indicates that the datapoint value needs to be inverted before
transmission.
7.
Background scan (No / Yes): indicates if the datapoint belongs to the background
scan cycle.
8.
Application
C264/EN AP/C80
MiCOM C264/C264C
Page 99/348
10.
Event (No / Yes with time tag): when set to Yes with time tag, indicates if change of
state of the datapoint are transmitted spontaneously with time Tag.
11.
Inversion (No / Yes): indicates that the datapoint value needs to be inverted before
transmission.
Modbus
(1)
(2)
T101/T104
(3)
(4)
(5)
(6)
(7)
(8)
DNP3
(9)
(10)
(11)
FIGURE 105: DEFINING A SCADA ADDRESS FOR AN SPS DATAPOINT
C264/EN AP/C80
Application
Page 100/348
4.8.2.2
MiCOM C264/C264C
double address usage (No / Yes): only available for Modbus SCADA protocol. If set
to Yes, DPS is transmitted to SCADA via two distinct SCADA address, one for the
open state, the other one for the close state.
3.
4.
open state address: used if Double address usage is set to Yes. This attribute
defines the SCADA address for the open state of the DPS.
5.
Closed state address: used if Double address usage is set to Yes. This attribute
defines the SCADA address for the closed state of the DPS.
Event (No / Yes with time tag /Yes without time tag): when set to Yes with time tag,
indicates if change of state of the datapoint are transmitted spontaneously with time
Tag.
7.
Event record (Does not involved in a transfert of file / Create a RECORD EVENT if
there is not it current / Add to the current record EVENT / Create a RECORD EVENT
and adds to the current record EVENT): when set to a value different from Not
involved in a transfer of file, indicates if change of state of the datapoint must be
saved in Sequence of Event file. At computer level, values different from Not involved
in a transfer of file are associated to the same treatment, because only one SOE file
is managed by computer. The set of available values is maintained for compatibility
with MiCOM gateway addressing in MiCOM gateway.
8.
Inversion (No / Yes): indicates that the datapoint value needs to be inverted before
transmission.
9.
Background scan: (No / Yes): indicates if the datapoint belongs to the background
scan cycle.
Application
C264/EN AP/C80
MiCOM C264/C264C
Page 101/348
10.
11.
Event (No / Yes with time tag): when set to Yes with time tag, indicates if change of
state of the datapoint are transmitted spontaneously with time Tag
13.
Inversion (No / Yes): indicates that the datapoint value needs to be inverted before
transmission
14.
Modbus
(1)
(2)
(3)
(4)
(5)
T101/T104
(6)
(7)
(8)
(9)
(10
)
(11)
DNP3
(12)
(13)
(14)
FIGURE 107: DEFINING A SCADA ADDRESS FOR A DPS DATAPOINT
C264/EN AP/C80
Application
Page 102/348
4.8.2.3
MiCOM C264/C264C
3.
4.
object address.
6.
Event (No / Yes with time tag / Yes without time tag): when set to Yes with time tag,
indicates that change of state of the datapoint are transmitted spontaneously with time
Tag.
7.
Event record ( No / Yes): indicates if change of state of the datapoint must be saved
in Sequence of Event file or not..
8.
9.
cycle type (None / Periodic / Background scan): indicates which transmission cycle
the MEAS belongs to.
10.
Application
C264/EN AP/C80
MiCOM C264/C264C
Page 103/348
object address
12.
Event (No / Yes with time tag): when set to Yes with time tag, indicates if change of
state of the datapoint are transmitted spontaneously with time Tag.
13.
Modbus
(1)
(2)
(3)
(4)
T101/T104
(5)
(6)
(7)
(8)
(9)
(10)
DNP3
(11)
(12)
(13)
FIGURE 109: DEFINING A SCADA ADDRESS FOR A MV DATAPOINT
C264/EN AP/C80
Application
Page 104/348
4.8.2.4
MiCOM C264/C264C
3.
Format (Natural / Unsigned normalized / Real IEEE754 little endian / Real IEEE754
big endian): transmission format.
object address.
5.
Event (No / Yes with time tag / Yes without time tag): when set to Yes with time tag,
indicates if changes of state of the datapoint are transmitted spontaneously with time
Tag.
6.
Group ([0..4] / 0=no group): indicates which T101/T104 General Interrogation group
the datapoint is assigned to. 0 means no group assignation.
object address.
8.
Event (No / Yes with time tag): when set to Yes with time tag, indicates if change of
state of the datapoint are transmitted spontaneously with time Tag.
Application
C264/EN AP/C80
MiCOM C264/C264C
Page 105/348
Modbus
(1)
(2)
(3)
T101/T104
(4)
(5)
(6)
DNP3
(7)
(8)
FIGURE 111: DEFINING A SCADA ADDRESS FOR A COUNTER DATAPOINT
4.8.2.5
C264/EN AP/C80
Application
Page 106/348
MiCOM C264/C264C
Once added, SCADA SPC address attributes must be set at SCE level:
1.
object address
4.
SCADA execute order type (Select execute / Direct execute): precise if SCADA uses
a Select execute or a Direct execute sequence to send control on the datapoint.
object address
6.
SCADA execute order type (Select execute / Direct execute):precise if SCADA uses
a Select execute or a Direct execute sequence to send control on the datapoint.
Modbus
(1)
(2)
T101/T104
(3)
(4)
DNP3
(5)
(6)
FIGURE 113: DEFINING A SCADA ADDRESS FOR A SPC DATAPOINT
Application
C264/EN AP/C80
MiCOM C264/C264C
4.8.2.6
Page 107/348
object address.
4.
SCADA execute order type (Select execute / Direct execute): precises if SCADA
uses a Select execute or a Direct execute sequence to send control on the
datapoint.
6.
SCADA execute order type (Select execute / Direct execute): precises if SCADA
uses a Select execute or a Direct execute sequence to send control on the
datapoint.
C264/EN AP/C80
Application
Page 108/348
MiCOM C264/C264C
Modbus
(1)
(2)
T101/T104
(3)
(4)
DNP3
(5)
(6)
Application
C264/EN AP/C80
MiCOM C264/C264C
Page 109/348
Once added, SCADA SetPoint address attributes must be set at SCE level:
1.
3.
format.(signed 16 bits / Real IEEE754 little endian: the lower byte is transmitted first
/ Real IEEE754 big endian: the higher byte is transmitted first)
object address.
5.
SCADA execute order type (Select execute / Direct execute): this attibute defines if
SCADA uses a Select execute or a Direct execute sequence to send control on the
datapoint.
6.
Minimal value: available minimal value on the protocol (used for scaling and checks).
7.
Maximal value: available maximal value on the protocol (used for scaling and
checks).
8.
10.
SCADA execute order type (Select execute / Direct execute): precises if SCADA
uses a Select execute or a Direct execute sequence to send control on the
datapoint.
11.
minimal value: available minimal value on the protocol (used for scaling and checks).
12.
maximal value: available maximal value on the protocol (used for scaling and
checks).
13.
C264/EN AP/C80
Application
Page 110/348
MiCOM C264/C264C
Modbus
(1)
(2)
(3)
T101/T104
(4)
(5)
(6)
(7)
(8)
DNP3
(9)
(10)
(11)
(12)
(13)
FIGURE 117: DEFINING A SCADA ADDRESS FOR A SETPOINT DATAPOINT
4.8.2.8
Create the SCADA SPC (resp. DPC) address (A) to send SPC (resp. DPC) control of
the synchronised breaker.
Create a SCADA SPC (resp. DPC) address (B) for bypass synchrocheck in the
SCADA mapping.
Add the relation has for bypass synchrocheck address via the Objects entry window
at SCADA address (A) and fill it with the SCADA address (B).
Application
C264/EN AP/C80
MiCOM C264/C264C
Page 111/348
FIGURE 118: ADDING A BYPASS S/C ADDRESS TO A SCADA SPC/DPC ADDRESS (E.G. FOR DPC)
4.8.3
The following protocols of gateway: IEC61850 and GI74 are not concerned by this edition.
Each tab present addresses datapoint data in left part of the table and address data in the
right part of the table.
For datapoint data, attributes displayed are the same than other table:
Kind
Path
Short name
Long name
For address data, attributes displayed are different for each type of protocol:
For xPS:
Addr: value of the SCADA address, only active for SPS address, or DPS
address if Double address usage is set to No.
Close Addr: value of the close state address for DPS address, only active for a
DPS address if Double address usage is set to Yes.
Open Addr: value of the open state address for DPS address, only active for a
DPS address if Double address usage is set to Yes.
Double address: flag to indicate if the address is double or not, only active for a
DPS address.
C264/EN AP/C80
Application
Page 112/348
For xPC:
MiCOM C264/C264C
For MV:
For Counter:
For SetPoint:
Application
C264/EN AP/C80
MiCOM C264/C264C
4.8.4
Page 113/348
(1)
C264/EN AP/C80
Page 114/348
4.9
Application
MiCOM C264/C264C
4.9.1
IED connected to computer legacy network can produce disturbance files. In that
case, computer monitors their availability. As soon as available, they are uploaded
and stored at computer level. Computer computes for System Management Tool
(SMT) a real-time data per IED basis that gives the availability of a disturbance file, via
station-bus network. Then, SMT downloads it from computer. At the end of successful
downloading, computer erases the real-time data of availability.
Via a CT/VT board (TMU200/220), computer can manage its own waveform record
files. Waveform channels are directly acquired on CT/VT board channels and
buffered. Triggered by pre-defined change of state, associated buffers are flushed on
files that correspond to waveform record files. In that case computer computes for
SMT a real-time data that gives the availability of a computer waveform record file, via
station-bus network. Then processing is similar to IEDs one.
Adding RDRE brick (1) for the IED in LD0 logical device of the IEC-61850 mapping of
the computer.
Adding the system SPS datapoint DREC ready (2) at IED level, linked to a predefined datapoint profile.
Fill the mandatory IEC address for this datapoint, with the relevant data object of the
RDRE brick (3).
FIGURE 121: ADDING RDRE BRICK AND DREC READY DATAPOINT FOR IED
Application
C264/EN AP/C80
MiCOM C264/C264C
Page 115/348
FIGURE 122: SETTING IEC-61850 ADDRESS OF DREC READY DATAPOINT FOR IED
For T103 IED extra information must be configured to process correct disturbance file
COMTRADE structure at computer level (see following section).
4.9.2
4.9.2.1
channel label.
2.
3.
4.
channel number: (cf. mapping IED field ACC in IEC 60870-5-103 documentation).
5.
6.
coefficient (0: not used): value which the samples must be multiplied by in order to
get the real value (0: not used). Generally, data uploaded from IED allows to compute
this multiply coefficient. Unfortunately, some IED dont give correct data. In this case,
this coefficient must be set here.
7.
shift time (range [0 s, 1 s], step 1 s): elapsed time since the beginning of the
sampling period.
8.
9.
C264/EN AP/C80
Page 116/348
Application
MiCOM C264/C264C
Application
C264/EN AP/C80
MiCOM C264/C264C
Page 117/348
channel label.
2.
3.
function number (range [0 , 255], step 1): corresponds to function type of the channel
in T103 protocol.
4.
5.
(1)
(2)
(3)
(4)
(5)
FIGURE 126: SETTING T103 DIGITAL CHANNEL DEFINITION
For more details about the digital channel definition, refer to COMTRADE (IEEE C37.11)
external documentation.
C264/EN AP/C80
Application
Page 118/348
4.9.3
MiCOM C264/C264C
fast waveform recording gives access to samples acquired via CT/VT board.
slow waveform recording gives access to analogues (MV) and digital values
(SPS, DPS, SPC, DPC) file recording.
Adding RDRE brick (1) for the computer in LD0 logical device of the IEC-61850
mapping of the computer.
Adding the system SPS datapoint C26x DREC ready (2) at computer level, linked to
a pre-defined datapoint profile.
Fill the mandatory address for this datapoint, with the relevant data object of the
RDRE brick (3).
(2)
(1)
FIGURE 127: ADDING A RDRE IEC-61850 BRICK AND A DREC READY DATAPOINT FOR A
COMPUTER
Application
C264/EN AP/C80
MiCOM C264/C264C
Page 119/348
(3)
FIGURE 128: SETTING IEC 61850 ADDRESS OF DREC READY DATAPOINT FOR COMPUTER
4.9.3.1
Number of cycles
60
120
240
480
The waveform recorder can be triggered by the following events, each of which is user
configurable:
Operator request
Only one re-trig is allowed: it means that a new trigger can only be accepted after the end of
recording of the current waveform.
Waveform records are available in COMTRADE 2001 format.
The addition of a fast waveform recording is done via the Objects entry window at
computer level by clicking on mouses right button. Only one fast waveform recording can be
created under a computer.
C264/EN AP/C80
Application
Page 120/348
MiCOM C264/C264C
short name and long name: used for internal SCE identification.
2.
pre-trigger cycle (range [0 , 480], step 1): corresponds to number of cycles (up to
480), that are stored before triggering.
3.
4.
(1)
(2)
(3)
(4)
FIGURE 130: SETTING FAST WAVEFORM RECORDING
To define the inputs of a fast waveform recording, just add the relevant relation (1) available
at recording level and fill the relation with proper CT/VT channel or datapoint. Be careful,
only CT/VT channels and datapoints acquired on the computer can be defined as input of its
fast waveform recording.
(1)
Application
C264/EN AP/C80
MiCOM C264/C264C
Page 121/348
To define the triggers of a fast waveform recording, just add the relevant relation (2)
available at recording level and fill the relation with proper datapoint. Be careful, only
datapoints acquired on the computer can be defined as input of its fast waveform recording.
(2)
C264/EN AP/C80
Page 122/348
Application
MiCOM C264/C264C
Application
C264/EN AP/C80
MiCOM C264/C264C
4.9.3.2
Page 123/348
The slow wave form manages up to 24 analogues (MV) and 48 digital values (SPS, DPS,
SPC, DPC).
MiCOM C264 stores at maximum 5000 integrated values as follow:
Number of Files
5000
2500
1000
10
500
20
250
50
100
Operator request
The addition of a slow waveform recording is done via the Objects entry window at
computer level by clicking on mouses right button. Only one slow waveform recording can
be created under a computer.
C264/EN AP/C80
Page 124/348
Application
MiCOM C264/C264C
short name and long name of the recording used for internal SCE identification.
2.
pre-trigger cycle (range [0 , 5000], step 1): corresponds to the number of cycles (up
to 480) that are stored before triggering.
3.
4.
5.
arbitration period (range [0 , 100], step 1): this data represents the percentage of
time during which the logical data must be set to 1 to consider the integrated data set
to 1.
6.
7.
activation period (Non periodic trigger / Daily trigger / weekly trigger / Daily and
weekly trigger): see previous description.
(1)
(2)
(3)
(4)
(5)
(6)
(7)
FIGURE 135: SETTING FAST WAVEFORM RECORDING
Application
C264/EN AP/C80
MiCOM C264/C264C
Page 125/348
To define the inputs of a slow waveform recording, just add the relevant relation (1) available
at recording level and fill the relation with proper datapoint. Be careful, only datapoints
acquired on the computer can be defined as input of its slow waveform recording.
(1)
(2)
C264/EN AP/C80
Page 126/348
Application
MiCOM C264/C264C
Application
C264/EN AP/C80
MiCOM C264/C264C
4.10
Page 127/348
The "SPC" link of the relation "has its klaxon controlled by" must be wired on a DO
channel of the Computer.
C264/EN AP/C80
Page 128/348
4.11
Application
MiCOM C264/C264C
(2)
(4)
(3)
(5)
(1)
Application
MiCOM C264/C264C
4.11.1
C264/EN AP/C80
Page 129/348
C264/EN AP/C80
Application
Page 130/348
MiCOM C264/C264C
This datapoint has the "RESET" state if the Local/remore DPS datapoint of all
the bays managed by the computer have the "OPEN" state and has the "SET"
state if at least the Local/remore DPS datapoint of one bay managed by the
computer has not the "OPEN" state.
Application
C264/EN AP/C80
MiCOM C264/C264C
Page 131/348
Database switch control SPC (2): this datapoint is only used by the SMT to turn
device functioning mode to Maintenance or Operational/Run.
The available state of this datapoint is:
ON for Switch
Synchronisation status
Synchronisation SPS (17): this is put in SET state if device is synchronised.
The available states of this datapoint are:
RESET for not synchronised device
SET for synchronised device
Communication status
Device link SPS (3): although this datapoint is under the computer, it is not
managed by it. Each IEC-61850 client of the computer computes locally this
datapoint status by supervising the IEC-61850 real-time link with the computer. In
fact, there are as many Device link SPS per computer basis as IEC-61850 clients
connected to the computer. Is put in SET state if device link is operational. The
available states of this datapoint are:
RESET for not OK
SET for OK
C264/EN AP/C80
Application
Page 132/348
MiCOM C264/C264C
Health statuses
DI acquisition stopped SPS (4): in case of saturation of the internal file used for
acquisition of wired digital inputs and gooses, acquisition is automatically stopped
and this datapoint is put in SET state. As soon as this internal file is un-saturated,
this datapoint is reset and acquisition restarts.
The available states of this datapoint are:
RESET for acquisition running
SET for acquisition stopped
Watchdog SPS (19): in case of software watchdog time-out, this datapoint is put in
SET state and computer enters the Faulty mode.
The available states of this datapoint are:
RESET for watchdog OK
SET for watchdog time-out
Application
C264/EN AP/C80
MiCOM C264/C264C
Page 133/348
DREC ready SPS (22): this datapoint indicates the availability of a waveform
record file for the computer (for details, refer to section 4.9 Defining wave record
file management).
The available states of this datapoint are:
RESET for no waveform record available
SET for waveform record file available
C264/EN AP/C80
Application
Page 134/348
4.11.2
MiCOM C264/C264C
(1)
FIGURE 143: MANDATORY SYSTEM INFOS DATAPOINT FOR A BOARD
(E.G. FOR AIU BOARD)
Board status MPS (1): this datapoint indicates the status of the board. Addressing
this datapoint can be done:
1) by using SBUS automatic addressing.
Application
C264/EN AP/C80
MiCOM C264/C264C
Page 135/348
(1)
(2)
FIGURE 146: MANDATORY SYSTEM INFOS DATAPOINTS FOR A LEGACY IED
These datapoints must be configured (see section 5 DEFINING DATAPOINT) according to
their described features:
IED communication status SPS (1): is put in SET state if communication with the
IED is operational.
The available states of this datapoint are:
RESET for communication not OK
SET for communication OK
C264/EN AP/C80
Page 136/348
Application
MiCOM C264/C264C
(1)
FIGURE 148: MANDATORY SYSTEM INFOS DATAPOINT FOR A SERIAL PRINTER
Printer status MPS (1): this datapoint indicates the status of the printer.
The available states of this datapoint are:
STATE 0 for printer OK
STATE 1 for self-check failure
Application
C264/EN AP/C80
MiCOM C264/C264C
4.11.5
Page 137/348
(2)
(1)
FIGURE 149: MANDATORY SYSTEM INFOS DATAPOINT FOR A SCADA NETWORK
SCADA communication status SPS (1): this datapoint is put in SET state if
communication with the SCADA is operational.
The available states of this datapoint are:
RESET for communication with the SCADA not OK
SET for communication with the SCADA OK
C264/EN AP/C80
Application
Page 138/348
MiCOM C264/C264C
5.
DEFINING DATAPOINT
5.1
Creating a datapoint
Electrical and system topologies share entities called datapoints. A datapoint corresponds to
an atomic object with real-time value, status or control relevant to electrical or system
process. Moreover, datapoints support extra system functions like forcing, suppression,
filtering, and alarms, logging.
Several kinds of datapoint exist:
SPS (Single Point Status), DPS (Double Point Status), MPS (Multiple Point
Status)
Setpoint
Input datapoints can be acquired through sensors (input channels), addressed on IED at IED
legacy network level or substation network level. They can also be calculated or deduced by
the system devices. They can be sent to SCADA by addressing them on SCADA networks.
Output datapoints can be controlled through relays (output channels), addressed on IED at
IED legacy network level or substation network level or on SCADA networks. They can also
be managed by built-in functions or user functions.
At SCE level, datapoints belonging to the system topology are called system datapoints, and
those of the electrical topology are named electrical datapoints.
Generally, system datapoint creation is automatic when adding system devices or subcomponents to system devices. They are never wired, except for system datapoint used by
redundancy and more often correspond to system diagnostics (device, printer board status,
control of device mode,).
Electrical datapoint creation is rarely automatic except when they are required for correct
PACiS system behaviour (for instance, Order running SPS at bay level, Computed
switchgear position at circuit-break level), or relevant to an electrical built-in function that
imposes their existence.
Be careful:
(Refer to section 4.6.1 Connecting computer to other station-bus sub-systems, for Client /
Server definition).
In the set of all the computers of a SCS, the previous described SPS attributes (except short
name and long name) are only useful and given to the computer that serves the datapoint
because the relevant functions are always done at computer server level.
5.1.1
System inputs (SI) are seen as particular SPS, DPS or MPS depending on the number
of elementary information they represents (for details about SI, see section4.11
Setting system information for computer components).
Application
C264/EN AP/C80
MiCOM C264/C264C
5.1.2
5.1.2.1
SPS processing
Page 139/348
Add an SPS from object entry available at the wished system or electrical object level
(1). Depending on the object level, different pre-defined kinds of SPS exist. They are
used for specific needs at electrical topology level (for details see relevant section in 6
DEFINING COMPUTER CONFIGURATION IN ELECTRICAL ARCHITECTURE) or
system topology level (for details see section 4.11 Setting system information for
computer components).
Update the SPS attributes (see following topic); some attributes can be fixed or
masked depending on the pre-defined kind of SPS.
Update its relation has for profile to point to a specific existing profile (2). See section
5.2 Linking a datapoint to a profile, for details about profile definition and setting.
FIGURE 150: ADDING AN SPS DATAPOINT (SAMPLE GIVEN AT BAY LEVEL FOR GENERIC SPS)
C264/EN AP/C80
Page 140/348
Application
MiCOM C264/C264C
Application
C264/EN AP/C80
MiCOM C264/C264C
Page 141/348
C264/EN AP/C80
Page 142/348
Application
MiCOM C264/C264C
short name and long name of the datapoint used for logging, alarms ...
2.
3.
4.
reset confirmation delay (range [0 s, 120 s], step 100 ms]: confirmation delay for
stable reset state.
5.
set confirmation delay (range [0 s, 120 s], step 100 ms]: confirmation delay for
stable set state.
6.
7.
state panel assignment (No / Yes): set to yes to enable SPS state display at
computer local HMI level.
Application
C264/EN AP/C80
MiCOM C264/C264C
5.1.3
5.1.3.1
DPS processing
Page 143/348
Add a DPS from object entry available at the wished system or electrical object level
(1). Depending on the object level, different pre-defined kinds of DPS exist. They are
used for specific needs at electrical topology level (for details see relevant section in 6
DEFINING COMPUTER CONFIGURATION IN ELECTRICAL ARCHITECTURE) or
system topology level (for details see section 4.11 Setting system information for
computer components).
Update the DPS attributes (see following topic); some attributes can be fixed or
masked depending on the pre-defined kind of DPS.
Update its relation has for profile to point to a specific existing profile (2). See section
5.2 Linking a datapoint to a profile, for details about profile definition and setting.
(1)
C264/EN AP/C80
Page 144/348
Application
MiCOM C264/C264C
Application
C264/EN AP/C80
MiCOM C264/C264C
Page 145/348
short name and long name of the datapoint used for logging, alarms ...
2.
stable state time reference ( Start motion / End motion): this attribute defines the
time reference for a stable state: at start of motion filtering or end of motion filtering
3.
complementary delay jammed (range [0 s, 60 s), step 100 ms): this attribute defines
the delay for the MOTION00 (JAMMED) state filtering. It corresponds to parameter T00
mentioned in 5.1.3.1 of chapter C264/EN FT
4.
complementary delay undefined (range [0 s, 60 s), step 100 ms): this attribute
defines the delay for the MOTION11 (UNDEFINED) state filtering. It corresponds to
parameter T11 mentioned in 5.1.3.1 of chapter C264/EN FT
5.
open confirmation delay (range [0 s, 60 s), step 100 ms): this attribute defines the
confirmation delay for the OPEN state. It corresponds to parameter TO mentioned in
5.1.3.2 of chapter C264/EN FT
6.
closed confirmation delay (range [0 s, 60 s), step 100 ms): this attribute defines the
confirmation delay for the CLOSE state. It corresponds to parameter TC mentioned in
5.1.3.2 of chapter C264/EN FT
7.
8.
state panel assignment (No / Yes): set to yes to enable the display of the DPS state
at the computer local HMI level.
C264/EN AP/C80
Application
Page 146/348
5.1.4
5.1.4.1
MPS processing
MiCOM C264/C264C
Add an MPS from object entry available at the wished system or electrical object level
(1). Depending on the object level, different pre-defined kinds of MPS exist. They are
used for specific needs at electrical topology level (for details see relevant section in 6
DEFINING COMPUTER CONFIGURATION IN ELECTRICAL ARCHITECTURE) or
system topology level (for details see section 4.11 Setting system information for
computer components).
Update the MPS attributes (see following topic); some attributes can be fixed or
masked depending on the pre-defined kind of MPS.
Update its relation has for profile to point to a specific existing profile (2). See section
5.2 Linking a datapoint to a profile, for details about profile definition and setting.
(1)
FIGURE 156: ADDING AN MPS DATAPOINT (SAMPLE GIVEN AT BAY LEVEL FOR GENERIC MPS)
Application
C264/EN AP/C80
MiCOM C264/C264C
Page 147/348
C264/EN AP/C80
Page 148/348
Application
MiCOM C264/C264C
short name and long name of the datapoint used for logging, alarms ...
2.
3.
4.
forcing management (Not automatic / Automatic to state <i> (i [0, 15])): when a
MPS goes in invalid state, computer can force or not its status to set or reset state
automatically. This attribute defines the way this forcing management is done.
Automatic forcing management is independent of FSS facility gives at user by the
MPS profile.
5.
state panel assignment (No / Yes): set to yes to enable MPS state display at
computer local HMI level.
Application
C264/EN AP/C80
MiCOM C264/C264C
5.1.5
Page 149/348
5.1.5.1
Saturation values
10 V
-12.6 V / +12.6 V
5V
-6.3 V / +6.3 V
2.5 V
-3.2 V / +3.2 V
1.25 V
-1.26 V / +1.26 V
0 - 1 mA
1.26 mA
1 mA
-1.26 mA / +1.26 mA
0 5 mA
6.3 mA
5 mA
-6.3 mA / +6.3 mA
0 10 mA
12.5 mA
10 mA
-12.5 mA / +12.5 mA
0 20 mA
25 mA
20 mA
-25 mA / +25 mA
4-20 mA
26 mA
Acquisition
Acquisition cycle
The analogue inputs are acquired on a periodical basis. Each channel on a board can be
assigned one of these cycles independently of the others channels (see section 4.4.5
Configuring an AI channel).
There exists two acquisition cycles:
a short cycle (Nsc x 100 ms, Nsc configurable from 1 to 10 with a default value of 1).
a long cycle (Nlc x 500 ms, Nlc configurable from 1 to 20, with a default value of 2).
AD conversion
The Analogue to Digital Converter has a 16 bits resolution (15 bits + sign bit).
The zero offset value is computed by the conversion of a 0 V voltage reference.
The gain is adjusted automatically by software by connecting a known voltage reference to
the amplifier.
The zero offset values and the gain are adjusted regularly in order to compensate for the
deviations caused by variations of temperature and ageing.
C264/EN AP/C80
Application
Page 150/348
MiCOM C264/C264C
Self-checks
Two two kinds of self-checks are performed:
These self-checks are performed at each scan (defined during the configuration phase).
Time tagging
An AI is time stamped with the date/time of the scanned value.
5.1.5.2
Adding an MV datapoint
To create an MV datapoint:
Add an MV from object entry available at the wished system or electrical object level
(1). Depending on the object level, different pre-defined kinds of MV exist. They are
used for specific needs at electrical topology level (for details see relevant section in 6
DEFINING COMPUTER CONFIGURATION IN ELECTRICAL ARCHITECTURE) or
system topology level (for details see section 4.11 Setting system information for
computer components).
Update the MV attributes (see following sections); some attributes can be fixed or
masked depending on the pre-defined kind of MV.
Update its relation has for profile to point to a specific existing profile (2). See section
5.2 Linking a datapoint to a profile, for details about profile definition and setting.
(1)
Application
C264/EN AP/C80
MiCOM C264/C264C
Page 151/348
C264/EN AP/C80
Page 152/348
5.1.5.3
Application
MiCOM C264/C264C
short name and long name: used for logging, alarms ...
2.
For details about digital encoding see section 4.6.3 of chapter C264/EN FT.
3.
4.
automatic forcing (No / Yes): when a MV goes in invalid state, computer can force or
not its value automatically. Automatic forcing management is independent of FSS
facility gives at user by the MV profile.
5.
6.
7.
deadband ( variation) (range [0,255], step 1): this attribute is significant only if the
previous parameter is set to According to a of ...: this attribute corresponds to p
parameter described in section 5.2.9.2 of chapter C264/EN FT.
8.
Application
C264/EN AP/C80
MiCOM C264/C264C
5.1.5.4
Page 153/348
minimum value (range [-3.4e38, 3.4e38]: used for full scale calculation and scaling
2.
maximum value (range [-3.4e38, 3.4e38]: used for full scale calculation and scaling.
(Full scale = maximum value - minimum value)
3.
zero value suppression (% of full scale value) (range [0,10], step 0.1): this parameter
is used to define the zero suppression area for the zero value suppression processing
(refer to section 5.2.3 of chapter C264/EN FT for details)
4.
Hysteresis used for threshold detection (see section 5.2.4 of chapter C264/EN FT for
details)
For each available threshold (see section 5.2.4 of chapter C264/EN FT for details):
5.
6.
Threshold value
(1)
(2)
(3)
(4)
(5)
(6)
scaling rule: available values are (see section 5.2.4 of chapter C264/EN FT for
details):
Linear
Quadratic
2.
3.
C264/EN AP/C80
Page 154/348
Application
MiCOM C264/C264C
Ai coefficient
5.
Bi coefficient
(1)
(2)
(3)
(4)
(5)
FIGURE 163: SETTING SCALING ATTRIBUTES OF AN MV DATAPOINT
(SAMPLE GIVEN AT BAY LEVEL FOR GENERIC MV)
Application
C264/EN AP/C80
MiCOM C264/C264C
5.1.6
5.1.6.1
Page 155/348
5.1.6.2
Update its relation has for profile to point to a specific existing MV profile (2). See
section 5.2 Linking a datapoint to a profile, for details about profile definition and
setting.
(2)
FIGURE 165: LINKING TPI DATAPOINT TO ITS PROFILE
C264/EN AP/C80
Page 156/348
5.1.6.3
Application
MiCOM C264/C264C
short name and long name of the datapoint used for logging, alarms ...
2.
Digital tap position coded 1 among N (only used for digital acquisition)
Digital tap position coded decimal (only used for digital acquisition)
Digital tap position coded gray (only used for digital acquisition)
Digital tap position coded BCD (only used for digital acquisition)
For details about digital encoding see section 4.6.3 of chapter C264/EN FT.
3.
MV panel assignment (No / Yes): set to yes to enable MV value display at computer
local HMI level.
(1)
(2)
(3)
FIGURE 166: SETTING GENERAL ATTRIBUTES OF A TPI DATAPOINT
5.1.6.4
5.1.6.5
2.
current valid range (% maximum value) (range [0 , 20 %], step 1 %): only used for
analogue TPI corresponds to N parameter described in section 5.3 of chapter
C264/EN FT.
(1)
(2)
FIGURE 167: SETTING TAP POSITION ATTRIBUTES OF A TPI DATAPOINT
Application
C264/EN AP/C80
MiCOM C264/C264C
5.1.6.6
Page 157/348
2.
(1)
(2)
FIGURE 168: SETTING SCALING ATTRIBUTES OF A TPI DATAPOINT
C264/EN AP/C80
Application
Page 158/348
MiCOM C264/C264C
5.1.7
5.1.7.1
Continuous register
From counters
acquisition
Scaling
+1
Accumulator
Transmission
Periodic register
Scaling
To RCP
To HMI
To archive
To automation
in
24h - FIFO
C0195ENa
The periodic register is used to store the accumulator value of the previous period.
The continuous register is used to store the accumulator value since the origin.
The FIFO memory is used to store the periodic register of each period (up to 16
counters), during 24h.
Periodic processing
A period is defined either:
By the internal clock: the period length is settable: 10', 15', 30', 1h to 24h , each period
begins at a regular hour: 12:00 , 12:30 , 13:00 ...
This choice is defined during the configuration phase on a per computer basis. The period
delimiter is also defined at configuration time for each counter.
At each period:
The content of the periodic register is inserted into the FIFO queue.
Either the continuous register or the periodic register is transmitted. The choice is
made by configuration on a per accumulator basis.
If the chosen transmitted register reaches its maximum value (232), the counter status is set
to OVERRANGE. Only a counter modification can re-validate the counter.
Application
C264/EN AP/C80
MiCOM C264/C264C
Page 159/348
Scaling
Scaling is used for printing or displaying a counter. EPI is a parameter giving the amount of
energy in KW-h or KVAR-h equivalent to a pulse. The displayed value is:
N x EPI KW-h
With N = the value of a counter.
Counter resulting states
The state of a counter can be:
State
Comment
VALID
SELFCHECK
FAULTY
UNKNOWN
UNDEFINED
OVERRANGE
Transmission
The counters are transmitted on a client-server basis on the IEC-61850 network using the
report mechanism.
During a loss of communication between a client and a server, all server counters are set to
UNKNOWN on the client.
The counter informations transmitted in a report are:
the reason for change, which could be one of the following values:
change due to control (set if the value or quality change is due to a control)
Counter modification
When an accumulator value is modified, the request is immediately taken into account. The
continuous register is set with the accumulator value.
The modification could be a reset of the counter.
5.1.7.2
Add a Counter from object entry available at the wished system or electrical object
level (1). Depending on the object level, different pre-defined kinds of counter exist.
They are used for specific needs at electrical topology level (for details see relevant
section in 6 DEFINING COMPUTER CONFIGURATION IN ELECTRICAL
ARCHITECTURE) or system topology level (for details see section 4.11 Setting
system information for computer components).
C264/EN AP/C80
Application
Page 160/348
MiCOM C264/C264C
Update its relation has for profile to point to a specific existing profile (2). See section
5.2 Linking a datapoint to a profile, for details about profile definition and setting.
(1)
Application
C264/EN AP/C80
MiCOM C264/C264C
Page 161/348
short name and long name of the datapoint used for logging, alarms ...
2.
counter type (Standard, Energy import, Energy export): when this attribute is set to
"Standard" associated attributes are Validation duration (3), Invalidity duration (4), IED
value already totalled (5), Cumul period (6) and Reset at cumulative period (7). When
this attribute is set to Energy import or Energy export associated attributes are energy
type (9), Scale factor (10), Transmission period (11) and reset after transmission (12).
3.
validation duration (range [0, 10 s], step 1 ms): corresponds to Tcount parameter
described in section 4.5 of chapter C264/EN FT.
C264/EN AP/C80
Page 162/348
Application
MiCOM C264/C264C
4.
invalidity duration (range [5, 10 s], step 1 ms): corresponds to Tdef parameter
described in section 4.5 of chapter C264/EN FT.
5.
IED value already totalled (No / Yes): attribute must be set to Yes if counter value
acquired on IED must not be totalled periodically (total done at IED level)
6.
7.
reset at cumulative period (No / Yes): when set to Yes that the way to transmit the
periodic register, if not the cumulative register is transmitted.
8.
MV panel assignment (No / Yes): set to yes to enable Counter value display at
computer local HMI level.
9.
scale factor.
10.
11.
12.
Application
C264/EN AP/C80
MiCOM C264/C264C
5.1.8
Page 163/348
System output: control information related to the system, to configurable and built-in
automations or to electrical process but without acquisition possibilities.
SPC, DPC and SetPoints are mainly controlled via digital output boards (DOU board) or via
IEDs connected by a serial link (for details see section 5.6).
By extension, at SCE level, system outputs are seen as particular SPC or DPC depending
on the number of elementary information they represent (for details about system outputs,
see section 4.11 Setting system information for computer components).
Control sequences are described in chapter C264/EN FT (Functional Description).
5.1.9
Add an SPC from object entry available at the wished system or electrical object level
(1). Depending on the object level, different pre-defined kinds of SPC exist. They are
used for specific needs at electrical topology level (for details see relevant section in 6
DEFINING COMPUTER CONFIGURATION IN ELECTRICAL ARCHITECTURE) or
system topology level (for details see section 4.11 Setting system information for
computer components).
Update the SPC attributes (see following topic); some attributes can be fixed or
masked depending on the pre-defined kind of SPC.
Update its relation has for profile to point to a specific existing profile (2). See section
5.2 Linking a datapoint to a profile, for details about profile definition and setting.
(1)
C264/EN AP/C80
Page 164/348
Application
MiCOM C264/C264C
Application
C264/EN AP/C80
MiCOM C264/C264C
5.1.9.1
Page 165/348
short name and long name: used for logging, alarms ...
2.
3.
4.
5.
order on duration (range [0, 15 s], step 10ms): this attribute is only available if the
activation mode is set to Transient. It defines the time while the contact is closed
before re-opening. hold duration (range [0, 10 s], step 10ms): this attribute is only
available if the activation mode is set to Permanent until feedback. It defines the
time while the contact is held in the requested position after reception of the
confirmation of the position of the device.
6.
time between two orders (range [0, 10 s], step 100ms): this attribute corresponds to
the inter-control delay .
7.
command panel assignment (No / Yes): set to yes to enable SPC control at
computer local HMI level.
8.
9.
10.
bay Contol uniqueness: (No / Yes): only significant if control uniqueness is set to
bay at substation level.
11.
12.
Add the relation has for feedback at SPC level: choose exclusively one of the two
relations has for feedback: SPS datapoint (1) or has for feedback: DPS datapoint (2)
depending on the kind of feedback datapoint.
C264/EN AP/C80
Application
Page 166/348
MiCOM C264/C264C
(1)
(2)
execution time-out (range [0, 6000 s], step 100 ms): in this given delay, feedback must
change relatively to the control. If not, a negative acknowledgement is sent for the
control (for details see section 5.1.8 Overview of control sequence processing).
4.
status check for command (No check / Control authorized only if the device is in the
opposite state / Control authorized only if the device is in the opposite state, jammed
or undefined / Control refused if the device is in the same state): this attribute
corresponds to the current status check for the device described in section 6.1.6.8 of
chapter C264/EN FT and used also for execution checks (see section 6.1.8 of chapter
C264/EN FT).
(3)
(4)
FIGURE 177: SETTING ATTRIBUTES OF AN SPC FEEDBACK RELATION
Configuration rules and checks
For each "SPC", two relations "has for feedback" are available, but they are mutually
exclusive
A datapoint and its feedback datapoint must comply with the following rules:
- both must have the same Server device
- if one of them is a "Wired" datapoint, the other one must be "Wired" too (Here, the
term "Wired" means that the datapoint is linked to a digital or analog channel of a
computer, or linked to an IED address, else it's "System")
- if one of them is a "System" datapoint, the other one must be "System" too.
- if one of them is linked to an " IEC61850 gen IED" through the relation "has for
IEC61850 address", this relation must also be defined for the other one
For a "SPC" datapoint, if its attribute "activation mode" is set to the "Transient" value,
then the following rule must be respected:
"execution timeout" > "order on duration"
Application
C264/EN AP/C80
MiCOM C264/C264C
5.1.10
Page 167/348
Add a DPC from object entry available at the wished system or electrical object level
(1). Depending on the object level, different pre-defined kinds of DPC exist. They are
used for specific needs at electrical topology level (for details see relevant section in 6
DEFINING COMPUTER CONFIGURATION IN ELECTRICAL ARCHITECTURE) or
system topology level (for details see section 4.11 Setting system information for
computer components).
Update the DPC attributes (see following topic); some attributes can be fixed or
masked depending on the pre-defined kind of DPC.
Update its relation has for profile to point to a specific existing profile (2). See section
5.2.7, for details about profile definition and setting.
(1)
C264/EN AP/C80
Page 168/348
Application
MiCOM C264/C264C
Application
C264/EN AP/C80
MiCOM C264/C264C
5.1.10.1
Page 169/348
short name and long name: used for logging, alarms ...
2.
3.
4.
close duration (range [0, 15 s], step 10ms): this attribute is only available if the
activation mode is set to Transient. It defines the time while the DPC is held in the
"close" state before returning to the "open" state.
5.
open duration (range [0, 15 s], step 10ms): this attribute is only available if the
activation mode is set to Transient. It defines the time while the DPC is held in the
"open" state before returning to the "close" state.
6.
hold duration (range [0, 10 s], step 10ms): this attribute is only available if the
activation mode is set to Permanent until feedback. It defines the time while the
contact is held in the requested state after reception of the confirmation of the position
of the device.
7.
time between two orders (range [0, 10 s], step 100ms): this attribute corresponds to
the inter-control delay defined in section 6.1.6.1 of chapter C264/EN FT and use also
used for execution checks (see section 6.1.8 of chapter C264/EN FT).
8.
command panel assignment (No / Yes): set to Yes to enable SPC control at
computer local HMI level.
9.
10.
11.
12.
13.
C264/EN AP/C80
Application
Page 170/348
5.1.10.2
MiCOM C264/C264C
Add the relation has for feedback at DPC level: choose exclusively one of the two
relations has for feedback: SPS datapoint (1) or has for feedback: DPS datapoint (2)
depending on the kind of feedback datapoint.
2.
execution timeout (range [0, 6000 s] step 100 ms): in this given delay, feedback
must change relatively to the control. If not, a negative acknowledgement is sent for
the control (for details see section 5.1.8 Overview of control sequence processing).
4.
status check for command (No check / Control authorized only if the device is in the
opposite state / Control authorized only if the device is in the opposite state, jemmed
or undefined / Control refused if the device is in the same state): this attribute
corresponds to the current status check for the device described in section 6.1.6.8 of
chapter C264/EN FT and also used for execution checks (see section 6.1.8 of chapter
C264/EN FT).
(1)
(2)
Application
C264/EN AP/C80
MiCOM C264/C264C
Page 171/348
For each "DPC", two relations "has for feedback" are available, but they are mutually
exclusive
A datapoint and its feedback datapoint must comply with the following rules:
- both must have the same Server device
- if one of them is a "Wired" datapoint, the other one must be "Wired" too (Here, the
term "Wired" means that the datapoint is linked to a digital or analog channel of a
computer, or linked to an IED address, else it's "System")
- if one of them is a "System" datapoint, the other one must be "System" too.
- if one of them is linked to an " IEC61850 gen IED" through the relation "has for
IEC61850 address", this relation must also be defined for the other one
For a "DPC" datapoint, if its attribute "activation mode" is set to the "Transient" value,
then the following rule must be respected:"execution timeout"> max ["open duration" ,
"close duration" ]
5.1.11
5.1.11.1
Digital SetPoints
SetPoints to IEDs
System SetPoints
Analog Setpoints
Digital SetPoints
Digital SetPoints are executed via DO channels of Digital Output boards. This type of
controls is managed in Direct Execute mode only.
The checks performed during execution phase for SetPoints are:
Digital SetPoints may be configured with digital refresh DO (see following topic)
The configuration allows also to define two methods of activation of the SetPoint relays:
Raw activation: all activated relays which must be open are deactivated, all relays
which must be closed are activated. If a read inhibit DO is configured this one must
be deactivated during the relay positioning (see following topic).
Incremental activation: the restitution of the SetPoint and relays can be done by
successive increments from the initial value to the final one. The value of increments
and the duration of the activation are user selectable. If a read inhibit DO is
configured this one must be deactivated during every incremental activation (see
following topic).
C264/EN AP/C80
Application
Page 172/348
MiCOM C264/C264C
The 0 to 1 transition on the RI output can be used by the external device as a trigger,
indicating that a new value is available.
Value
RI
C0210ENa
Application
C264/EN AP/C80
MiCOM C264/C264C
Page 173/348
The AO values are secured with an external power supply which allows keeping the analog
output value in case of C264 shutdown or power off. A quality indication is available with the
additional Read Inhibit output relays (NO) associated to each AO.
5.1.11.2
Add a SetPoint from object entry available at the wished system or electrical object
level (1). Depending on the object level, different pre-defined kinds of SetPoint exist.
They are used for specific needs at electrical topology level (for details see relevant
section in 6 DEFINING COMPUTER CONFIGURATION IN ELECTRICAL
ARCHITECTURE) or system topology level (for details see section 4.11 Setting
system information for computer components).
Update the SetPoint attributes (see following topic); some attributes can be fixed or
masked depending on the pre-defined kind of SetPoint.
Update its relation has for profile to point to a specific existing profile (2). See section
5.2.8 Defining a SetPoint profile, for details about profile definition and setting.
(1)
C264/EN AP/C80
Page 174/348
Application
MiCOM C264/C264C
Application
C264/EN AP/C80
MiCOM C264/C264C
5.1.11.3
Page 175/348
short name and long name of the datapoint used for logging, alarms ...
2.
type:
3.
4.
progressive step usage: only used for digital SetPoint. No corresponds to Raw
activation, Yes to Incremental Activation, described in section Defining a SetPoint
datapoint.
5.
minimum value (range [-3.4E38, 3.4E38]): used for value control and scaling.
6.
maximum value (range [-3.4E38, 3.4E38]): used for value control and scaling.
7.
command panel assignment (Yes / No): set to yes to enable SetPoint control at
computer local HMI level.
8.
9.
10.
11.
12.
C264/EN AP/C80
Application
Page 176/348
MiCOM C264/C264C
5.1.11.4
A Setpoint datapoint wired on DO channels of a computer, must be digital and have its
profile attribute SBO mode set to "Direct Execute" or Direct Execute with SBO
popup.
execution timeout (range [0, 999 s], step 1 s): in this given delay, feedback must
change relatively to the control. If not, a negative acknowledgement is sent for the
control (for details see section 5.1.8 Overview of control sequence processing).
(1)
(2)
FIGURE 188: SETTING ATTRIBUTES OF A SETPOINT FEEDBACK RELATION
Configuration rules and checks
A datapoint and its feedback datapoint must comply with the following rules:
- both must have the same Server device
- if one of them is a "Wired" datapoint, the other one must be "Wired" too (Here, the
term "Wired" means that the datapoint is linked to a digital or analog channel of a
computer, or linked to an IED address, else it's "System")
- if one of them is a "System" datapoint, the other one must be "System" too.
- if one of them is linked to an "IEC61850 gen IED" through the relation "has for
IEC61850 address", this relation must also be defined for the other one
Application
C264/EN AP/C80
MiCOM C264/C264C
5.2
Page 177/348
links to printers defined in the system topology for alarm and event logging purpose.
For output datapoints, the following characteristics are set at profile level:
links to printers defined in the system topology for alarm and event logging purpose.
Profile objects can be put at any level of the system topology but never in the electrical
topology: they concern only system characteristics. For details about the system topology,
see section 4 DEFINING COMPUTER CONFIGURATION IN SYSTEM ARCHITECTURE.
A profile object can be added at the following levels of the system topology:
SCS.
Ethernet network.
When configuring a computer, the best practice is to group all profiles relevant to its system
datapoints at computer level or eventually its sub-components. Upper levels (Ethernet
network or SCS) can be used to define profiles if sharing datapoint profile between several
computers is wished.
C264/EN AP/C80
Page 178/348
Application
MiCOM C264/C264C
Mixing the two previous approaches, particularly for profiles relevant to datapoints
whose level is upper than bay or belonging to same kind of bays fed by several bay
computers.
Be careful:
(Refer to section 4.6.1 Connecting computer to other station-bus sub-systems, for Client /
Server definition)
In the set of all the computers of an SCS:
the following profile functional characteristics logging, alarm, archiving and FSS, are
only useful and given to the computer that serves the linked datapoints because these
functions are always done at computer server level. So, a computer A using a
datapoint acquired on a computer B will never log, alarm or archive events relevant to
this datapoint.
the following profile functional characteristics state interlocking values are given to
server and client computers using a datapoint, because interlock evaluation is a
distributed function done on every computer that needs it before controlling its own
electrical modules.
the following profile functional characteristics SBMC facilities are given to server or
client computers using a datapoint exchanged on a SCADA network they manage,
because SBMC filtering is a distributed function done on computers managing SCADA
networks.
the following profile characteristics state/order labels are given to server or client
computers using a datapoint but are only used by the server: computer bay mimics,
logging, alarm definitions are reduced to datapoints that the computer is server of.
Application
C264/EN AP/C80
MiCOM C264/C264C
5.2.1
5.2.1.1
Page 179/348
Add (icon +) an SPS profile from object entry available at the wished system object
level (1).
Define if necessary on which printers event logging of linked SPS datapoint is done,
via adding and filling the relation has events logged on at profile level (2).
Define if necessary on which printers alarm event logging of linked SPS datapoint is
done, via adding and filling the relation has alarm events logged on at profile level
(3).
The alarm logging printer is defined at the same time as Event Logging (figure 163)
short name and long name of the profile only used for profile identification in SCE.
C264/EN AP/C80
Page 180/348
Application
MiCOM C264/C264C
3.
4.
SBMC state substitution value (Suppressed / Set / Reset): significant and visible if
SBMC dependant is set to Yes.
5.
toggling filtering (No / Yes): useful for a datapoint acquired on a DI board to filter
toggling.
6.
initial status (Reset / Set): used for computer software initialisation especially for
system datapoints.
5.2.1.3
The profile of a datapoint of the System topology must have its enable
Force/Subst/Sup attribute set to No.
OI no archive, no logging:
Application
C264/EN AP/C80
MiCOM C264/C264C
Page 181/348
3.
masking due to control (No / Yes): this attribute must be set to Yes to manage
correctly discrepancy (alarm only appears in case of spontaneous change of state
without previous control).
4.
delay (range [0 s, 120 s], step 1 s): to avoid alarm generation if alarm condition
disappears within this delay.
5.
6.
7.
clearing mode (Manual / Automatic / Gravity basis): to precise the way alarm is
cleared when alarm condition disappears:
Gravity basis: the clearing mode is deduced from the one given at Scs object
level for the relevant gravity
For Set and Reset state, extra attribute spurious is settable ((8) and (9)). This information
is only significant when the user wants to alarm a spurious SPS datapoint on a particular
event Set or Reset. In fact, the datapoint has got no state, but generates an event. It is
useful to alarm trip information of relays for instance. When setting a spurious alarm, only the
relative state must be defined as alarmed; the other states must be set to not defined alarm.
For computer configuration, all attributes are significant for datapoints it is server of.
C264/EN AP/C80
Page 182/348
Application
MiCOM C264/C264C
Application
C264/EN AP/C80
MiCOM C264/C264C
5.2.2
5.2.2.1
Page 183/348
Add a DPS profile from object entry available at the wished system object level (1).
Defines if necessary on which printers event logging of linked DPS datapoint is done,
via adding and filling the relation has events logged on at profile level (2).
Defines if necessary on which printers alarm event logging of linked DPS datapoint is
done, via adding and filling the relation has alarm events logged on at profile level
(3).
The alarm logging printer is defined is the same time as Event Logging.
C264/EN AP/C80
Page 184/348
5.2.2.2
Application
MiCOM C264/C264C
short name and long name of the profile only used for profile identification in SCE.
3.
4.
5.
toggling filtering (No / Yes): useful for datapoint acquired on DI board to filter
toggling.
6.
initial status (Motion / Open / Closed / Undefined), used for computer software
initialisation especially for system datapoints.
5.2.2.3
The profile of a datapoint of the System topology must have its enable
Force/Subst/Sup attribute set to No.
OI : no archive, no logging:
OI : archive, no logging:
Application
C264/EN AP/C80
MiCOM C264/C264C
Page 185/348
3.
masking due to control (No / Yes): this attribute must be set to Yes to manage
correctly discrepancy (alarm only appears in case of spontaneous change of state
without previous control)
4.
delay (range [0 s, 120 s], step 1 s): to avoid alarm generation if alarm condition
disappears within this delay
5.
6.
7.
clearing mode (Manual / Automatic / Gravity basis): to precise the way alarm is
cleared when alarm condition disappears:
Gravity basis: the clearing mode is deduced from the one given at Scs object
level for the relevant gravity.
For Open and Closed states, extra attribute spurious is settable ((8) and (9)). This
information is only significant when the user wants to alarm a spurious DPS datapoint on a
particular event Open or Closed. In fact, the datapoint has got no state, but generates an
event. It is useful to alarm trip information of relays for instance. When setting a spurious
alarm, only the relative state must be defined as alarmed; the other states must be set to not
defined alarm.
For computer configuration, all attributes are significant for datapoints it is server of.
C264/EN AP/C80
Page 186/348
Application
MiCOM C264/C264C
Application
C264/EN AP/C80
MiCOM C264/C264C
5.2.2.6
Page 187/348
5.2.3.1
Add an MPS profile from object entry available at the wished system object level (1).
Defines if necessary on which printers event logging of linked MPS datapoint is done,
via adding and filling the relation has events logged on at profile level (2).
Defines if necessary on which printers alarm event logging of linked MPS datapoint is
done, via adding and filling the relation has alarm events logged on at profile level
(3).
The alarm logging printer is defined is the same time as Event Logging (figure 179)
C264/EN AP/C80
Page 188/348
5.2.3.2
Application
MiCOM C264/C264C
short name and long name: only used for profile identification in SCE.
3.
4.
5.2.3.3
The profile of a datapoint of the System topology must have its enable
Force/Subst/Sup attribute set to No.
Application
C264/EN AP/C80
MiCOM C264/C264C
5.2.3.4
Page 189/348
OI : no archive, no logging:
OI : archive, logging:
OI : archive, no logging:
3.
masking due to control (No / Yes): this attribute must be set to Yes to manage
correctly discrepancy (alarm only appears in case of spontaneous change of state
without previous control).
4.
delay (range [0 s, 120 s], step 1 s): to avoid alarm generation if alarm condition
disappears within this delay.
5.
6.
7.
clearing mode (Manual / Automatic / Gravity basis): to precise the way alarm is
cleared when alarm condition disappears:
C264/EN AP/C80
Page 190/348
Application
MiCOM C264/C264C
Gravity basis: the clearing mode is deduced from the one given at Scs object level
for the relevant gravity.
For computer configuration, all attributes are significant for datapoints it is server of.
Application
C264/EN AP/C80
MiCOM C264/C264C
5.2.4
Defining an MV profile
5.2.4.1
Adding an MV Profile
Page 191/348
To create an MV profile:
Add an MV profile from object entry available at the wished system object level (1).
The alarm logging printer is defined is the same time as Event Logging.
C264/EN AP/C80
Page 192/348
5.2.4.2
Application
MiCOM C264/C264C
short name and long name: only used for profile identification in SCE.
3.
4.
5.
5.2.4.3
The profile of a datapoint of the System topology must have its enable
Force/Subst/Sup attribute set to No.
Application
C264/EN AP/C80
MiCOM C264/C264C
Page 193/348
3.
delay (range [0 s, 120 s], step 1 s): to avoid alarm generation if alarm condition
disappears within this delay
4.
5.
6.
clearing mode (Manual / Automatic / Gravity basis): to precise the way alarm is
cleared when alarm condition disappears:
Gravity basis: the clearing mode is deduced from the one given at Scs object level
for the relevant gravity.
For computer configuration, all attributes are significant for datapoints it is server of.
C264/EN AP/C80
Page 194/348
Application
MiCOM C264/C264C
2.
3.
Application
C264/EN AP/C80
MiCOM C264/C264C
5.2.5
5.2.5.1
Page 195/348
Add a Counter profile from object entry available at the wished system object level (1).
Defines if necessary on which printers alarm event logging of linked Counter datapoint
is done, via adding and filling the relation has alarm events logged on at profile level
(3).
The alarm logging printer is defined is the same time as Event Logging (figure 196)
C264/EN AP/C80
Page 196/348
5.2.5.2
Application
MiCOM C264/C264C
short name and long name: only used for profile identification in SCE.
3.
4.
5.
(1)
(2)
(3)
(4)
(5)
FIGURE 220: SETTING GENERAL ATTRIBUTES OF A COUNTER PROFILE
5.2.5.3
Application
C264/EN AP/C80
MiCOM C264/C264C
5.2.5.4
Page 197/348
OI : no archive, no logging:
OI : archive, logging:
OI : archive, no logging:
2.
delay (range [0 s, 120 s], step 1 s): to avoid alarm generation if alarm condition
disappears within this delay.
3.
4.
5.
clearing mode (Manual / Automatic / Gravity basis): to precise the way alarm is
cleared when alarm condition disappears:
Gravity basis: the clearing mode is deduced from the one given at Scs object level
for the relevant gravity.
For computer configuration, all attributes are significant for datapoints it is server of.
C264/EN AP/C80
Page 198/348
5.2.5.6
Application
MiCOM C264/C264C
5.2.6.1
Add an SPC profile from object entry available at the wished system object level (1).
Define if necessary on which printers event logging of linked SPC datapoint is done,
via adding and filling the relation has events logged on at profile level (2).
Define if necessary on which printers alarm event logging of linked SPC datapoint is
done, via adding and filling the relation has alarm events logged on at profile level
(3).
The alarm logging printer is defined is the same time as Event Logging (figure 204)
Application
C264/EN AP/C80
MiCOM C264/C264C
5.2.6.2
Page 199/348
short name and long name of the profile only used for profile identification in SCE
3.
see
section
6.1.2
of
chapter
C264/EN
FT)
Direct execute
Direct execute with SBO control box (reserved to substation control point usage),
similar to Direct execute for computer
SBO timeout (range [0, 600 s], step 1s), significant if SBO mode is set to SBO
operate once or SBO operate many.
2.
3.
4.
Order on label
C264/EN AP/C80
Page 200/348
5.2.6.4
Application
MiCOM C264/C264C
OI : no archive, no logging:
OI : archive, logging:
OI : archive, no logging:
2.
delay (range [0 s, 120 s], step 1 s): to avoid alarm generation if alarm condition
disappears within this delay
3.
4.
5.
clearing mode (Manual / Automatic / Gravity basis): to precise the way alarm is
cleared when alarm condition disappears:
Gravity basis: the clearing mode is deduced from the one given at Scs object level
for the relevant gravity
For computer configuration, all attributes are significant for datapoints it is server of.
Application
C264/EN AP/C80
MiCOM C264/C264C
5.2.6.6
Page 201/348
On order interlock value (Invalid / False / True): this attribute defines the value
affected to the On order state of the SPC for evaluation of an interlock equation or a
FBD using this SPC.
2.
Off order interlock value (Invalid / False / True): this attribute defines the value
affected to the Off order state of the SPC for evaluation of an interlock equation or a
FBD using this SPC.
For computer configuration, all attributes are significant for datapoints it is server of.
5.2.7.1
Add a DPC profile from object entry available at the wished system object level (1).
Define if necessary on which printers event logging of linked DPC datapoint is done,
via adding and filling the relation has events logged on at profile level (2).
Define if necessary on which printers alarm event logging of linked DPC datapoint is
done, via adding and filling the relation has alarm events logged on at profile level
(3).
The alarm logging printer is defined at the same time as Event Logging (figure 213)
C264/EN AP/C80
Page 202/348
Application
MiCOM C264/C264C
short name and long name: only used for profile identification in SCE
3.
SBO mode
Available values are:
Direct execute
Direct execute with SBO control box (reserved to substation control point usage),
similar to Direct execute for computer
SBO timeout (range [0, 600 s], step 1s), significant if SBO mode is set to SBO
operate once or SBO operate many.
2.
3.
4.
Application
C264/EN AP/C80
MiCOM C264/C264C
5.2.7.4
Page 203/348
OI : no archive, no logging:
OI : archive, logging:
OI : archive, no logging:
2.
delay (range [0 s, 120 s], step 1 s): to avoid alarm generation if alarm condition
disappears within this delay
3.
4.
5.
clearing mode (Manual / Automatic / Gravity basis): to precise the way alarm is
cleared when alarm condition disappears:
Gravity basis: the clearing mode is deduced from the one given at Scs object level
for the relevant gravity
For computer configuration, all attributes are significant for datapoints it is server of.
C264/EN AP/C80
Page 204/348
Application
MiCOM C264/C264C
Open order interlock value (Invalid / False / True): this attribute defines the value
affected to the Open order state of the DPC for evaluation of an interlock equation or
a FBD using this DPC
2.
Close order interlock value (Invalid / False / True): this attribute defines the value
affected to the Close order state of the DPC for evaluation of an interlock equation or
a FBD using this DPC
For computer configuration, all attributes are significant for datapoints it is server of.
5.2.8.1
Add a SetPoint profile from object entry available at the wished system object level
(1).
Define if necessary on which printers alarm event logging of linked SetPoint datapoint
is done, via adding and filling the relation has alarm events logged on at profile level
(3).
The alarm logging printer is defined at the same time as Event Logging (figure 236)
Application
C264/EN AP/C80
MiCOM C264/C264C
Page 205/348
short name and long name of the profile only used for profile identification in SCE
Direct execute
Direct execute with SBO control box (reserved to substation control point usage),
similar to Direct execute for computer, reserved for future use
3.
SBO timeout (range [0, 600 s], step 1s), significant if SBO mode is set to SBO
operate once or SBO operate many.
4.
C264/EN AP/C80
Page 206/348
5.2.8.3
Application
MiCOM C264/C264C
OI : archive, logging:
OI : archive, no logging:
2.
delay (range [0 s, 120 s], step 1 s): to avoid alarm generation if alarm condition
disappears within this delay
3.
4.
5.
clearing mode (Manual / Automatic / Gravity basis): to precise the way alarm is
cleared when alarm condition disappears:
Gravity basis: the clearing mode is deduced from the one given at Scs object level
for the relevant gravity
Application
C264/EN AP/C80
MiCOM C264/C264C
Page 207/348
For computer configuration, all attributes are significant for datapoints it is server of.
C264/EN AP/C80
Page 208/348
5.3
Application
MiCOM C264/C264C
5.4
5.5
Application
C264/EN AP/C80
MiCOM C264/C264C
5.6
Page 209/348
5.6.1
5.6.1.1
Mode
SPS state
ON
Normal
SET
OFF
Normal
RESET
ON
Inverted
RESET
OFF
Inverted
SET
Faulty
SELFCHECK FAULTY
If necessary update the relation attribute inverted value (2), whose meaning is given
previously.
C264/EN AP/C80
Application
Page 210/348
MiCOM C264/C264C
(1)
(2)
FIGURE 245: UPDATING THE WIRING OF A SPS DATAPOINT
5.6.1.2
Add the relations closed' wired on (1) and 'open' wired on (2) at DPS level.
(1)
(2)
Application
C264/EN AP/C80
MiCOM C264/C264C
5.6.1.3
Page 211/348
Add the relations state <i> wired on (1) at MPS datapoint level, for each available
state of the MPS (i begins from 0).
Fill the relations with the relevant DI channels: when datapoint level is lower than or
equal to bay level, only DI channels from DIU boards belonging to the computer that
manages the bay, are available. To define the computer that manages a bay, refer to
section 6.1.4 Defining a Bay.
If a read inhibit signal exists for the MPS, add the relations read inhibit wired on (2) at
MPS datapoint level.
(2)
(1)
Fill the relation with the relevant AI channel: when datapoint level is lower than or
equal to bay level, only AI channels from AIU boards belonging to the computer that
manages the bay, are available. To define the computer that manages a bay, refer to
section 6.1.4 Defining a Bay.
C264/EN AP/C80
Application
Page 212/348
MiCOM C264/C264C
(1)
Add the relations bit <i> wired on (1) at MV or TPI datapoint level, for each available
bit channel of the MV or TPI (i begins from 0).
Fill the relations with the relevant DI channels: when datapoint level is lower than or
equal to bay level, only DI channels from DIU boards belonging to the computer that
manages the bay, are available. To define the computer that manages a bay, refer to
section 6.1.4 Defining a Bay.
If a read inhibit signal exists for the MV or TPI, add the relations read inhibit wired on
(2) at MV or TPI datapoint level.
If a sign bit exists for the MV, add the relations sign bit wired on (3) at MV datapoint
level.
(1)
(2)
(3)
Add the relation primary input wired on (1) at Counter datapoint level.
If it is a double counter, add the extra relation secondary input wired on (2) at
Counter datapoint level.
Fill the relations with the relevant DI channel: when datapoint level is lower than or
equal to bay level, only DI channels from DIU boards belonging to the computer that
manages the bay, are available. To define the computer that manages a bay, refer to
section 6.1.4 Defining a Bay.
Application
C264/EN AP/C80
MiCOM C264/C264C
Page 213/348
When the counter is used as an energy counter ("counter type" attribute set to "Energy
import" or "Energy Export") no wiring is needed but the relation "integrate: MV
electrical datapoint" (3) must be added to define the input of the counter. This relation
must be filled with the relevant MV datapoint.
(1)
(2)
(3)
Add the relation has for IED address (1) at datapoint level. Generally, only one
relation adding is available for datapoint, except for DPS datapoint where up to 2
relations can be added, corresponding to each elementary bit of the DPS if the legacy
protocol does not support the DPS feature. In that case, the DPS is split in two SPS
regarding to the legacy protocol.
Fill the relation with the relevant IED address: when datapoint level is lower than or
equal to bay level, only IED addresses from IEDs belonging to the computer that
manages the bay, are available. To define the computer that manages a bay, refer to
section 6.1.4 Defining a Bay.
(1)
FIGURE 251: ACQUIRING INPUT DATAPOINT VIA IED LEGACY NETWORK (E.G. SPS DATAPOINT)
C264/EN AP/C80
Application
Page 214/348
MiCOM C264/C264C
5.6.3
A "DPS" datapoint can have one or two relation(s) "has for IED address":
- In the case of one IED address, the attribute "contact type" of the IED address must
be set to the "Unused" value.
- In the case of two IED addresses, the attribute "contact type" of one of the IED
addresses must be set to the "open" value, and the attribute "contact type" of the other
IED address must be set to the "close" value.
Add the relation has for IED address (1) at datapoint level
Do not confuse:
Give an IEC61850 address to a datapoint, still wired on a computer, via has for IEC
address relation adding.
Give an IEC address to a datapoint on an IEC IED. In that case the datapoint can not
be wired, because it is seen as produced or managed by the IEC IED.
(1)
Application
C264/EN AP/C80
MiCOM C264/C264C
5.6.4
Page 215/348
5.6.4.1
IED
managed
by
PACiS
computers
5.6.4.2
5.6.4.3
C264/EN AP/C80
Page 216/348
5.6.4.4
Application
MiCOM C264/C264C
Active Power
Reactive Power
Apparent Power
Frequency
Fill the relation with the relevant CT/VT board. When datapoint level is lower than or
equal to bay level, only the CT/VT board belonging to the computer that manages the
bay, is available. To define the computer that manages a bay, refer to section 6.1.4
Defining a Bay.
Update the relation attribute measure type (2), giving the computation type.
(1)
Application
C264/EN AP/C80
MiCOM C264/C264C
5.7
Page 217/348
5.7.1
5.7.1.1
Fill the relation with the relevant DO channel: when datapoint level is lower than or
equal to bay level, only DO channels from DOU boards belonging to the computer that
manages the bay, are available. To define the computer that manages a bay, refer to
section 6.1.4 Defining a Bay.
(1)
Add the relations closed wired on (1) and open wired on (2) at DPC datapoint level
(these relations can be added two times in case of 4 DO channels use).
Fill the relations with the relevant DO channels: when datapoint level is lower than or
equal to bay level, only DO channels from DOU boards belonging to the computer that
manages the bay, are available. To define the computer that manages a bay, refer to
section 6.1.4 Defining a Bay.
C264/EN AP/C80
Application
Page 218/348
MiCOM C264/C264C
(1)
(2)
Add the relations bit <i> wired on (1) at SetPoint datapoint level, for each available bit
channel of the SetPoint (i begins from 0)
Fill the relations with the relevant DO channels: when datapoint level is lower than or
equal to bay level, only DO channels from DOU boards belonging to the computer that
manages the bay, are available. To define the computer that manages a bay, refer to
section 6.1.4 Defining a Bay.
If a read inhibit signal exists for the SetPoint (see section 5.1.11.1 Overview of
SetPoint processing), add the relations read inhibit wired on (2) at SetPoint datapoint
level.
If a refresh signal exists for the SetPoint (see section 5.1.11.1 Overview of SetPoint
processing), add the relations refresh wired on (3) at SetPoint datapoint level.
If a sign bit exists for the SetPoint, add the relations sign bit wired on (4) at SetPoint
datapoint level.
Application
C264/EN AP/C80
MiCOM C264/C264C
Page 219/348
5.7.1.4
A Setpoint datapoint wired on DO channels of Computer, must be digital and have its
profile attribute SBO mode set to "Direct Execute" or Direct Execute with SBO
popup
C264/EN AP/C80
Application
Page 220/348
5.7.2
MiCOM C264/C264C
Add the relation has for IED address (1) at datapoint level. Generally, only one
relation adding is available for a datapoint, except for a DPC datapoint where up to
two relations can be added, corresponding to each elementary bit of the DPC if the
legacy protocol does not support the DPC feature. In that case, the DPC is split in two
SPC regarding to the legacy protocol.
Fill the relation with the relevant IED address: when datapoint level is lower than or
equal to bay level, only IED addresses from IEDs belonging to the computer that
manages the bay, are available. To define the computer that manages a bay, refer to
section 6.1.4 Defining a Bay.
(1)
A "DPC" datapoint can have one or two relation(s) "has for IED address":
- In the case of one IED address, the attribute "contact type" of the IED address must
be set to the "Unused" value.
- In the case of two IED addresses, the attribute "contact type" of one of the IED
addresses must be set to the "open" value, and the attribute "contact type" of the other
IED address must be set to the "close" value.
Application
C264/EN AP/C80
MiCOM C264/C264C
5.7.3
Page 221/348
Add the relation has for IED address (1) at datapoint level
Do not confuse:
Give an IEC address to a datapoint, still wired on a computer, via has for IEC
address relation adding.
Give an IEC address to a datapoint on an IEC IED. In that case the datapoint can not
be wired, because it is seen as produced or managed by the IEC IED.
(1)
C264/EN AP/C80
Application
Page 222/348
5.7.4
MiCOM C264/C264C
5.7.4.1
Facilities given by built-in electrical and grouping functions or users function, in PACiS
computers.
5.7.4.2
5.7.4.3
5.7.5
Cmd2
Action
Ack
PSL
PSL
Cmd 1 cancelled
NA
PSL
Operator
Cmd 1 cancelled
NA
Operator
PSL
Cmd 1 cancelled
Operator
Operator
Cmd 2 Ignored
CO_REQUEST_IN_PROGRESS (ACK 6)
Application
C264/EN AP/C80
MiCOM C264/C264C
Page 223/348
When two identical orders (Open/Open or Close/Close) are simultaneous and from different
origins, the acknowledgment management is described on the following table:
5.8
Cmd1
Cmd2
Action
Ack
PSL
PSL
Cmd 2 Ignored
NA
PSL
Operator
Cmd 2 Ignored
CO_REQUEST_IN_PROGRESS (ACK 6)
Operator
PSL
Cmd 2 Ignored
NA
Operator
Operator
Cmd 2 Ignored
CO_REQUEST_IN_PROGRESS (ACK 6)
(1)
C264/EN AP/C80
Application
Page 224/348
5.8.2
MiCOM C264/C264C
(1)
(2)
Application
C264/EN AP/C80
MiCOM C264/C264C
5.8.3
Page 225/348
(5)
(6)
(7)
The original datapoint and the target datapoint can belong to different computers. In
this case the states of the original datapoints are transmitted through GOOSE
messages
A MPS original datapoint can only be associated to a SPS ( the relation "is mapped
on: Mapping DPS Electrical datapoint" is not available in the "Object entry" window
associated to a MPS)
A MV original datapoint can only be associated to a SPS ( the relation "is mapped on:
Mapping DPS Electrical datapoint" is not available in the "Object entry" window
associated to a MV)
C264/EN AP/C80
Application
Page 226/348
MiCOM C264/C264C
6.
DEFINING
COMPUTER
ARCHITECTURE
6.1
CONFIGURATION
IN
ELECTRICAL
At SCE data modelling level, the entry point of electrical topology is the Site object. At the
moment, a Site object (1) can be composed of only one Substation object.
A substation (2) is constituted of Voltage level objects, each of them corresponding to an
electrical partitioning of the substation by voltage level value (in kV).
A voltage level (3) is an aggregation of Bay object (4), grouping of electrical devices, called
module (5). Generally this grouping is electrically self-safety, i.e. can be isolated from others
bays by switchgears for maintenance and managed by only one PACiS computer. There are
different kinds of bays: feeder, transformer, busbar, bus coupler, bus section, capacitor bank
and generic bay.
Coupling two voltage levels is commonly done via transformer. To respect SCE data
modelling electrical partitioning, this transformer must belong to a transformer bay (6)
arbitrary put in one of both voltage levels (generally its primary). An extra relation on
transformer defines to which voltage level its secondary (or primary) belongs.
Final electrical components are modules composing bays. There are different kinds of
modules: circuit breaker, switchgear, transformer, motor, generator, battery, capacitor,
inductor, converter and generic module. An extra module exists to describe substation
external connection (external line).
Every level of the electrical topology, except Site level, can own datapoints whose features
and configuration are described in section 5 DEFINING DATAPOINT.
Application
C264/EN AP/C80
MiCOM C264/C264C
Page 227/348
Feeder bay
Bus coupling bay
Transformer bay
Busbar bay
Switchgear
module
Q1
Circuit-breaker
module
Q0
Switchgear
module
Q9
Switchgear
Module (earth)
Q8
External line
module
C0213ENa
C264/EN AP/C80
Application
Page 228/348
6.1.1
MiCOM C264/C264C
Defining a Site
When creating a new configuration with the SCE, the electrical topology is automatically
instantiated via a Site root object, containing a mandatory Substation object.
A Site object corresponds to customer project identification: its attributes short name and
long name (1) can be entered at SCE level. At the moment, these attributes are not used.
(1)
Defining a Substation
When creating a new configuration using SCE, the electrical topology is automatically
instantiated via Site root object, containing a mandatory Substation object.
A Substation object corresponds to customer substation identification: its attributes short
name and long name (1) must be entered at SCE level, for proper logging formatting and
datapoint identification, at computer and operator interface levels.
At substation level, the attribute default uniqueness (2) defines the way control uniqueness
is managed for the whole substation. Available values are:
Substation level: control uniqueness is provided by PACiS system for the whole
substation, i.e. 2 simultaneous controls are refused within the substation, except for
control datapoints configured as substation uniqueness independent (see section
Erreur ! Source du renvoi introuvable.) Erreur ! Source du renvoi introuvable.,
Bay level: control uniqueness is provided by PACiS system for an entire bay, i.e. 2
simultaneous controls are refused within the same bay, except for control datapoints
configured as bay uniqueness independent (see section Erreur ! Source du renvoi
introuvable. Erreur ! Source du renvoi introuvable.,Erreur ! Source du renvoi
introuvable.).
(1)
(2)
FIGURE 268: SETTING ATTRIBUTES OF A SUBSTATION
Bay and substation uniqueness are managed by computer by synthesis of mandatory SPS
datapoints Order running, automatically added under a bay at its creation (see section 6.1.4
Defining a Bay).
Configuration rules and checks
Application
C264/EN AP/C80
MiCOM C264/C264C
6.1.2.1
Page 229/348
Local/remote for substation (see section 6.1.2.2 Defining Local/Remote for substation)
Taking Control for substation and SCDA links (see section 6.1.2.3 Defining Taking
Control for substation and SCADA links)
For more details about datapoints and their configuration, refer to section 5 DEFINING
DATAPOINT.
(2)
(1)
A Global alarm ack SPS (1) can be added to the substation level in
order to automatically acknowledge the new alarms in the C264 and
also in the OI. The detection mode attribute of this SPS must be set
to "Permanent" or "Permanent with computer auto-reset". This SPS
may be any wired SPS or SPS activated by a control ( by using the
Glb alm ack ctrl SPC(2)) from the SCADA or generated by any PSL.
It is also possible to launch a global alarm acknowledment at a fixed
time by using a cyclic SPS ( described in section 6.1.4.1 Adding bay
generic datapoint)
C264/EN AP/C80
Application
Page 230/348
6.1.2.2
MiCOM C264/C264C
SPC: 5.1.9,
DPC: 5.1.10,
SetPoint: 5.1.11.
In Local or Remote mode the information acquired by computers and IEDs are always sent
to RCP and PACiS Operator Interface.
The automatic Forcing of Invalid BI function is used to avoid processing of invalid states of
the substation mode (the local or remote replacement state is defined in configuration). The
Forced Local state is processed as the Local state. The Forced Remote state is
processed as the Remote state.
Moreover, all IEC61850 clients (i.e. Operator Interface, gateway, computers) will
automatically forced the substation mode to Forced Local or Forced Remote if it takes the
UNKNOWN state (due for example to the loss of communication between the computer
which manages the substation mode and the IEC61850 clients).
To activate Local/remote substation facilities:
add the optional datapoints Local/remote DPS (1) and/or Loc/rem ctrl DPC (2), via
the Objects entry window at substation level by clicking on mouses right button,
if necessary, do not forget to link via has for feedback relation, the control of the
Local/remote with the Local/remote status datapoint.
(2)
(1)
Application
C264/EN AP/C80
MiCOM C264/C264C
Page 231/348
6.1.2.3
If "Loc/rem ctrl DPC" is present, then "Local/remote DPS" must be present (it's the
feedback).
If "Local/remote DPS" is wired, then "Loc/rem ctrl DPC" is not mandatory but, if it's
present, it must be wired.
If, under a Substation, a "DPC" or "SPC" datapoint has its attribute "Substation mode
dependency" set to "Yes", then the Substation "Local/remote DPS" datapoint must be
present.
If the two datapoints "Local/remote DPS" and "Loc/rem ctrl DPC" are present, they
must have the same Server device.
"Loc/rem ctrl DPC" datapoint must have its profile attribute SBO mode set to "Direct
Execute" or Direct Execute with SBO popup.
add the optional datapoints Taking Control (2) and Taking status (1), via the
Objects entry window at substation level by clicking on mouses right button.
add the relation is taken control of at Taking status datapoint level (3), and fill it with
the relevant given SCADA network.
do not forget to link via has for feedback relation, the control with the status
datapoint.
(2)
(1)
(1)
C264/EN AP/C80
Page 232/348
Application
MiCOM C264/C264C
6.1.2.4
If, at least, one SCADA network is linked to a Taking Control function, all the SCADA
Networks of the system must be linked to a Taking Control function.
A "Taking Control" datapoint must be linked to a "Taking Status" datapoint through the
relation "has for feedback".
The "Taking Control" datapoint must have its "activation mode" attribute set to a
"Permanent" value. The "Taking Status" datapoint must have its "detection mode"
attribute set to the "Permanent" value.
Both "Taking Control" and "Taking Status" datapoints must be linked to a SCADA
address in the mapping of their SCADA network.
If a Taking-Control function is defined then, the "Loc/rem ctrl DPC" for substation must
be present and not wired.
The Server of the Local/Remote datapoints is the Server of each datapoints couple
"Taking Status" / "Taking Control".
All the devices having a SCADA network linked to a Taking-Control function are:
- Clients of each datapoints couple "Taking Status" / "Taking Control".
- Clients of the datapoints couple "Local/remote DPS" / "Loc/rem ctrl DPC".
Application
C264/EN AP/C80
MiCOM C264/C264C
6.1.3
Page 233/348
short name and long name: used for logging, alarms ...
2.
nominal value in kV
3.
ATCC existence (No / Yes): when set to yes, an extra tab-pane appears for the
voltage level, to enter specific ATCC regulation feature for the voltage level. For
details about ATCC configuration and this attribute, refer to section 6.6)
(1)
(2)
(3)
FIGURE 274: SETTING GENERAL ATTRIBUTES OF AN MV DATAPOINT
(SAMPLE GIVEN AT BAY LEVEL FOR GENERIC MV)
C264/EN AP/C80
Page 234/348
6.1.3.1
Application
MiCOM C264/C264C
Application
C264/EN AP/C80
MiCOM C264/C264C
6.1.4
Page 235/348
Defining a Bay
At voltage level level, several bay objects can be added. A voltage level corresponds to a
substation area whose electrical bays and sub-modules refer to the same nominal voltage.
There is an exception for transformer bay, coupling two different voltage levels that must be
arbitrary located on one of the both.
To create a bay:
Add a typed one from object entry available at voltage level (1).
Update its is managed by relation, to define which computer manages the bay (2).
(1)
short name and long name of the bay used for logging, alarms ...
2.
C264/EN AP/C80
Page 236/348
Application
MiCOM C264/C264C
(1)
(2)
Feeder: a circuit-breaker and external line modules are mandatory and implicitly
created,
Busbar: no module is available. This typed bay must be seen as a single electrical
node. A specific attribute node reference used for electrical topology definition for
ATCC function can be entered for a busbar. For details about ATCC configuration and
this attribute, refer to section 6.6).
Generic bay: no sub-component constraint. Used for general usage outside the scope
of other previous typed bays.
Application
C264/EN AP/C80
MiCOM C264/C264C
6.1.4.1
Page 237/348
Local/remote for bay (see section 6.1.4.2 Defining Local/Remote for bay)
SBMC for bay (see section 6.1.4.3 Defining SBMC for bay)
For more details about datapoints and their configuration, refer to section 5 DEFINING
DATAPOINT.
6.1.4.2
SPC: 5.1.9,
DPC: 5.1.10,
SetPoint: 5.1.11.
C264/EN AP/C80
Application
Page 238/348
MiCOM C264/C264C
In Local or Remote mode, the information issued from the bay is always sent to SCP and
RCP.
The automatic Forcing of Invalid BI function is used to avoid processing of invalid states of
the bay mode (the local or remote replacement state is defined in configuration). The
Forced Local state is processed as the Local state. The Forced Remote state is
processed as the Remote state.
To activate Local/remote bay facilities:
add the optional datapoints Local/remote DPS (1) and/or Loc/rem ctrl DPC (2), via
the Objects entry window at bay level by clicking on mouses right button
if necessary, do not forget to link via has for feedback relation, the control of the
Local/remote with the Local/remote status datapoint.
(2)
(1)
If "Loc/rem ctrl DPC" is present, then "Local/remote DPS" must be present (it's the
feedback).
If "Local/remote DPS" is not wired, then "Loc/rem ctrl DPC" is not mandatory but, if it's
present, it must not be wired.
If "Local/remote DPS" is wired, then "Loc/rem ctrl DPC" is not mandatory but, if it's
present, it must be wired.
If, under a Bay, a "DPC" or "SPC" datapoint has its attribute "bay mode dependency"
set to "Yes", then the Bay "Local/remote DPS" datapoint must be present.
"Loc/rem ctrl DPC" datapoint must have its profile attribute SBO mode set to "Direct
Execute" or Direct Execute with SBO popup.
If the "GHU200" board of a computer has its attribute "HMI type" set to the "Simple" value,
then the "Local/remote DPS" datapoints of the bays managed by this computer must be all
be "Wired" or all "System".
Application
C264/EN AP/C80
MiCOM C264/C264C
6.1.4.3
Page 239/348
SPC: 5.1.9,
DPC: 5.1.10,
SetPoint: 5.1.11.
This function provides a facility to control selected bays from the Substation Control Point
(SCP) and optionally to suppress or force to a pre-defined state, datapoint for the RCP while
the substation is in Remote mode. If configured as SBMC dependant at its profile level, a
datapoint belonging to a bay in SBMC mode takes the state defined in the profile
configuration for the RCP, but is still processed normally in the SCS (e.g. all processes
inside the system are unaffected by the state modification of an information at the RCP
interface).
The state of a datapoint sent to RCP is defined in its profile configuration. For each type of
datapoint, they are:
SPS
DPS
MPS
SUPPRESSED, UNDEFINED
SUPPRESSED
add the optional datapoints SBMC SPS (1) and SBMC control SPC (2), via the
Objects entry window at bay level by clicking on mouses right button,
do not forget to link via has for feedback relation, the control of the SBMC with the
SBMC status datapoint.
(2)
(1)
C264/EN AP/C80
Application
Page 240/348
MiCOM C264/C264C
6.1.4.4
If "SBMC control SPC" is present, then its attribute "bay mode dependency" must be
set to "No".
If a "DPC" or "SPC" datapoint has its attribute "SBMC mode dependency" set to "Yes",
then the "SBMC SPS" datapoint must be present.
If a "DPS" or "SPS" datapoint has the attribute "SBMC dependant" of its profile set to
"Yes", then the "SBMC SPS" datapoint must be present.
Defining Module
This section deals with general module configuration. Configuring specific typed module is
described in following relevant section.
At bay level, several module objects can be implicitly or explicitly added. A module
corresponds generally to a substation electrical device.
To create explicitly a module:
Application
C264/EN AP/C80
MiCOM C264/C264C
Page 241/348
(1)
short name and long name of the module used for logging, alarms ...
2.
node reference, used for electrical topology definition. For details about this
attribute, refer to section 6.6)
(1)
(2)
C264/EN AP/C80
Page 242/348
Application
MiCOM C264/C264C
Capacitor, Inductor:
Specific attribute reactive power value (in MVA). For details about this attribute,
refer to section 6.6..
Transformer:
Lockable module.
Circuit-breaker module:
Lockable module.
Switchgear module
Lockable module.
External line:
6.1.5.1
Generic module:
Lockable module.
Used for general usage outside the scope of other previous typed modules.
For more details about datapoints and their configuration, refer to section 5 DEFINING
DATAPOINT.
Application
C264/EN AP/C80
MiCOM C264/C264C
Page 243/348
FBD user
Circuit-breaker,
Switchgear,
Transformer,
Generic module.
C264/EN AP/C80
Application
Page 244/348
MiCOM C264/C264C
Add the pre-defined SPS datapoint Lock SPS at module level (1) and configure it
(see section 5 DEFINING DATAPOINT),
Add the pre-defined SPC datapoint Lock control SPC at module level (2) and
configure it (see section 5 DEFINING DATAPOINT),
Define the Lock SPS as feedback of the Lock control SPC by adding and filling has
for feedback relation at the SPC level (see section 5.1.9.2 Defining an SPC
feedback).
(2)
(1)
FIGURE 288: DEFINING A LOCKABLE MODULE
Lock SPS and Lock control SPC are datapoints fed and controlled directly by the computer
that manages the module. They can not be wired.
Configuration rules and checks
6.1.5.4
Withdraw information is useful for bay mimic animation at computer LCD level. For more
details see section 7.3 Defining a computer bay mimic.
(1)
Application
C264/EN AP/C80
MiCOM C264/C264C
6.1.5.5
Page 245/348
Defining a circuit-breaker
This section deals with general circuit-breaker features and available associated input and
output datapoints at computer level.
If the circuit-breaker is synchronised by internal or external synchrocheck, extra datapoints
exist. For more details refer to section 6.2 Defining a Synchrocheck function.
General module features described in section 6.1.5 Defining Module are applicable to circuitbreaker module and not reviewed here.
When adding a circuit-breaker module, the following specific general attribute must be
updated:
1.
Circuit-breaker type:
Triple phase circuit-breaker, where the 3 phases can only be managed together.
do not forget to link via has for feedback relation, the control(s) (1), (11) or (10) of the
breaker with the computed switch position (20) datapoint.
C264/EN AP/C80
Application
Page 246/348
MiCOM C264/C264C
Triple phase circuit-breaker
OUTPUTS CB TYPE A
DEVICE
CONTROL
DEVICE
SELECTION
(HARDWARE)
DEVICE
CONTROL
DEVICE
SELECTION
(HARDWARE)
(i)
The computed double signal is equal to the physical status if the phase not together
status is equal to false else the computed signal is equal to jammed.
(ii)
The computed phases not together is equal to false if all phases are in the same
position else it is equal to true.
(iii)
The computed signal is equal to the phase A status if the phase not together status is
equal to false else the computed signal is equal to jammed.
(iv)
Application
C264/EN AP/C80
MiCOM C264/C264C
Page 247/348
Order Running
is new addition
C0505ENa
The two datapoints "Switch Ctrl DPC" and "Switch Ctrl SPC" are mutually exclusive.
None is mandatory
If physical position of the device is given by an SPS (19), phase not together
information (14) is mandatory
C264/EN AP/C80
Application
Page 248/348
MiCOM C264/C264C
Set1: {Switch phA DPC, Switch phB DPC, Switch phC DPC}
Set2: {Switch phA SPC, Switch phB SPC, Switch phC SPC}
Set3: {Switch phA pos. DPS, Switch phB pos. DPS, Switch phC pos. DPS}
Set4: {Switch phA pos. SPS, Switch phB pos. SPS, Switch phC pos. SPS}
If the "circuit-breaker type" is set to the "Single phase CircuitBreaker" value, then:
- in a set, if one datapoint is present for a phase, then the two others must be present
as well.
- the datapoints of the two sets (1) and (2) are mutually exclusive.
- the datapoints of the two sets (3) and (4) are mutually exclusive.
- if the datapoint "Switchgear pos." is present, but none of the three datapoints "Switch
PhA pos", "Switch PhB pos", and "Switch PhC pos" then the SPS datapoint "Ph not
together" is mandatory.
If the "circuit-breaker type" is set to the "Triple phase CircuitBreaker" value, then
no DPC referencing a phase (phA, phB or phC) is allowed.
"Selection SPC" datapoint must have its profile attribute SBO mode set to "Direct
Execute" or Direct Execute with SBO popup
2.
Link them to the TMU210 and give the link the right Measurement type from the dropdown list. Select the TMU210 board and do a check of the table suming up the wiring.
4.
5.
Application
C264/EN AP/C80
MiCOM C264/C264C
Page 249/348
6.
Map the measurements in the IEC 61850 XCBR Logical Node with the following
objects:
IT_Phase A
SumSwAARs
IT_Phase B
SumSwABRs
IT_PhaseC
SumSwACRs
IT_Total
SumSwARs
I2T_Phase A
SumSwA2ARs
I2T_Phase B
SumSwA2BRs
I2T_PhaseC
SumSwA2CRs
I2T_Total
SumSwA2Rs
C264/EN AP/C80
Application
Page 250/348
MiCOM C264/C264C
Defining a switchgear
This section deals with general switchgear features and available associated input and
output datapoints at computer level.
General module features described in section 6.1.5 Defining Module are applicable to
switchgear module and not reviewed here.
When adding a switchgear module, the following specific general attribute must be updated:
1.
Switchgear type:
Available values are:
Busbar disconnector
Disconnector
Bypass disconnector
Earth switch
Application
C264/EN AP/C80
MiCOM C264/C264C
Page 251/348
do not forget to link via has for feedback relation, the control (3) of the switchgear (if it
exists) with the switch position (1) or (5) datapoint.
Switchgear
OUTPUTS TYPE A
DEVICE
CONTROL
DEVICE
SELECTION
(HARDWARE)
Defining a transformer
This section deals with general transformer features and available associated input and
output datapoints at computer level.
General module features described in section 6.1.5 Defining Module are applicable to
transformer module and not reviewed here.
When adding implicitly a transformer module via transformer bay creation (refer to 6.1.4
Defining a Bay), the following general attribute must be updated:
1.
Transformer type:
Double wound: a double wound (or two winding transformer) is a transformer with
galvanic isolation between primary and secondary coil. Tap Changer (with
additional winding) is usually located at HV-neutral side for economic reasons.
Tapping-up (raise order) reduces primary winding and increase LV tension.
C264/EN AP/C80
Application
Page 252/348
MiCOM C264/C264C
3.
Impedance, whose unit is a percent of value for S=100 MVA (range [0,01 to 24,99 by
step 0,01) , useful for ATCC regulation
(1)
(2)
(3)
(1)
Application
C264/EN AP/C80
MiCOM C264/C264C
Page 253/348
When adding a transformer, some optional datapoints can be created at module level and
must be configured (see section 5 DEFINING DATAPOINT):
1.
2.
MCB position DPS: used for ATCC function (see section 6.5 to give Mini Circuit-Breaker
position of associated tap-changer, via DPS datapoint
MCB position SPS: used for ATCC function (see section 6.5 )
CO495ENa
C264/EN AP/C80
Application
Page 254/348
MiCOM C264/C264C
6.2
6.2.1
do not forget to link via has for feedback relation, the control(s) (1), (11) or (10) of the
breaker with the computed switch position (20) datapoint.
configure properly the synchrocheck function itself (for details see 6.2.5 Creating a
synchrocheck function).
Triple phase circuit-breaker with synchrocheck
OUTPUTS CB TYPE A
DEVICE SELECTION
(HARDWARE)
SYNCHROCHECK
SET ON / SET OFF
DEVICE CONTROL
Application
C264/EN AP/C80
MiCOM C264/C264C
Page 255/348
DEVICE CONTROL
DEVICE SELECTION
(HARDWARE)
SYNCHROCHECK
SET ON / SET OFF (v)
(i)
The computed double signal is equal to the physical status if the phase not together
status is equal to false else the computed signal is equal to jammed.
(ii)
The computed phases not together is equal to false if all phases are in the same
position else it is equal to true.
(iii)
The computed signal is equal to the phase A status if the phase not together status is
equal to false else the computed signal is equal to jammed.
(iv)
(v)
Wired SPC and SPS for external synchrocheck and system SPC and SPS for internal
synchrocheck. If is not configured the external synchrocheck module or the
synchrocheck automatism is considered always set on. DPC and DPS are used only
for manual synchrocheck.
C264/EN AP/C80
Page 256/348
Application
MiCOM C264/C264C
C0496ENa
Application
C264/EN AP/C80
MiCOM C264/C264C
Page 257/348
The two datapoints "Switch Ctrl DPC" and "Switch Ctrl SPC" are mutually exclusive.
None is mandatory.
If physical position of the device is given by an SPS (19), phase not together
information (14) is mandatory.
Set1: {Switch phA DPC, Switch phB DPC, Switch phC DPC}
Set2: {Switch phA SPC, Switch phB SPC, Switch phC SPC}
Set3: {Switch phA pos. DPS, Switch phB pos. DPS, Switch phC pos. DPS}
Set4: {Switch phA pos. SPS, Switch phB pos. SPS, Switch phC pos. SPS}
If the "circuit-breaker type" is set to the "Single phase CircuitBreaker" value, then:
- in a set, if one datapoint is present for a phase, then the two others must be present
as well.
- the datapoints of the two sets (1) and (2) are mutually exclusive.
- the datapoints of the two sets (3) and (4) are mutually exclusive.
- if the datapoint "Switchgear pos." is present, but none of the three datapoints "Switch
PhA pos", "Switch PhB pos", and "Switch PhC pos" then the SPS datapoint "Ph not
together" is mandatory.
If the "circuit-breaker type" is set to the "Triple phase CircuitBreaker" value, then no
DPC referencing a phase (phA, phB or phC) is allowed.
A Circuit Breaker must be linked only once to a Synchrocheck function (relation "is
synchrocheck of").
"Sync CB close" datapoint of a "Circuit breaker" linked to a "Ext manual CS" or "Int
synchrocheck" synchrocheck must have its profile attribute SBO mode set to "Direct
Execute" or Direct Execute with SBO popup.
Furthermore, waiting closes the CB by the external module the initiator of the request can:
C264/EN AP/C80
Application
Page 258/348
6.2.2
MiCOM C264/C264C
6.2.3
6.2.4
Operator manual
closure
Operator
Synchrocheck
closure
Auto-recloser
X
(param 26)
X
(param 20)
X
(param 31)
X
(param 19)
X
(param 28)
X
(param 22)
X
(param 33)
X
(param 27)
X
(param 21)
X
(param 32)
X
(param 29)
X
(param 23)
X
(param 34)
The authorised schemes are defined during the configuration phase. The operator
synchrocheck closure behaviour is described in following sections.
Logic of authorisation of interlocking
The absolute values of the two voltages (Vline and Vbusbar) must be above or below settable
thresholds, to permit the circuit breaker closing. The following voltage controls are available:
with Vline and Vbusbar TRUE if the measured voltage is above the threshold V> (param 15 and
param 17), and not(Vline) and not(Vbusbar) TRUE if the measured voltage is below the
threshold V< (param 16 and param 18). These threshold are given in % of the nominal
voltage value, updated at TMU200 board level (refer to section 4.4.2.3 Setting specific
attributes of a TMU200/220 board).
The selection of the voltage control is made during the configuration phase.
Application
C264/EN AP/C80
MiCOM C264/C264C
Page 259/348
Schemes using Vline and not(Vbusbar) / not(Vline) and Vbusbar voltage controls
In case of the absence of one of the two voltages, at the end of a settable delay T2 (param
2), the authorisation of closing is given:
Vline
&
T2
Closing authorization
Not(Vbusbar)
C0227ENa
Vbusbar
&
T2
Closing authorization
Not(Vline)
C0228ENa
Not(Vline)
&
T3
Closing authorization
Not(Vbusbar)
C0229ENa
The difference in amplitude (algebraic) between the two voltages (V) is lower than
the seized threshold (Evect) (param 5) AND
The frequencies are as Fline and Fbusbar are such Fmin<F<Fmax where Fmin (param 6) and
Fmax (param 7) are the extreme acceptable frequencies AND
The difference between the two frequencies (F) is lower than the seized threshold
(Efreq) (param 8) AND
The phase difference between the two voltages () is lower than the seized threshold
(Ephase) (param 9)
These criteria must be still met before the time-out of a delay T1 started on the criteria
appearance else the synchrocheck function will not authorise the CB closing.
If during the delay time T1 one of these criteria is lost, T1 is reinitialised and is relaunched on
reappearance of all the criteria.
C264/EN AP/C80
Application
Page 260/348
MiCOM C264/C264C
T1 depends on the way circuit breaker is controlled (manual closure, manual synchronised
closure, automatic with auto-recloser), given 3 parameters at SCE level: (param 25), (param
30), (param 35).
&
F <Efreq
T1
Reclosing authorization
< Ephase
V < Evect
C0230ENa
The difference in amplitude (algebraic) between the two voltages (V) is lower than
the seized threshold (Evect) (param 10) AND
The frequencies are as Fline and Fbusbar are such Fmin<F<Fmax where Fmin (param 11)
and Fmax (param 12) are the extreme acceptable frequencies AND
The difference between the two frequencies (F) is lower than the seized threshold
(Efreq) (param 13)
These criteria must be still met before the time-out of a delay T1 started on the criteria
appearance else the synchrocheck function will not authorise the CB closing.
If during the delay time T1 one of these criteria is lost, T1 is reinitialised and is relaunched on
reappearance of all the criteria.
T1 depends on the way circuit breaker is controlled (manual closure, manual synchronised
closure, automatic with auto-recloser), given 3 parameters at SCE level: (param 25), (param
30), (param 35).
&
T1
Autorisation to check
Vbusbar
F <Efreq
V < Evect
C0231ENa
Application
C264/EN AP/C80
MiCOM C264/C264C
6.2.5
Page 261/348
Bay level, in case of the synchrocheck function dedicated to a particular breaker of the
bay, or shared by two breakers in two different bays managed by the same computer.
The addition of a synchrocheck is done via the Objects entry window at substation or bay
level by clicking on mouses right button.
For more details about bay creation, refer to section 6.1.4 Defining a Bay.
Several types of synchrochecks exist:
Busbar,
Bus coupler,
Bus section,
Feeder,
Transformer,
Generic bay.
(1)
(2)
(3)
(4)
FIGURE 307: ADDING A SYNCHROCHECK AT BAY LEVEL (E.G. FOR FEEDER)
(2)
C264/EN AP/C80
Page 262/348
Application
MiCOM C264/C264C
Fill the relation is synchrocheck of, giving which circuit-breaker module is concerned
by the function. For substation synchrocheck, several relations is synchrocheck of
can be added and filled for all concerned breakers by the same synchrocheck. For
bay synchrocheck, two relations is synchrocheck of can be filled for breakers of two
different bays. Nevertheless, these bays must be managed by the same computer,
and the same synchrocheck parameters will be used for the two breakers closure.
2.
short name and long name of the synchrocheck used for logging, alarms ...
3.
automatic out of service (No / Yes): defines if the synchrocheck is set off manually
(No) or automatically (Yes). When manually set off, an extra sequence is done by
computer (see previous sections). For automatic synchrocheck, this attribute is fixed
to Yes.
4.
running time (range [0, 60s],step 1 s): this attribute appears in case of automatic out
of service. It corresponds to a latency time before setting out of service the
synchrocheck after successful or unsuccessful closure of the synchronised breaker.
(1)
FIGURE 310: ACCEPT FORCING MANDATORY DATAPOINT FOR SYNCHROCHECK
(E.G. FOR EXTERNAL MANUAL SYNCHROCHECK AT BAY LEVEL)
Application
C264/EN AP/C80
MiCOM C264/C264C
6.2.5.1
Page 263/348
Acceptance Conditions
C264/EN AP/C80
Page 264/348
Application
MiCOM C264/C264C
2.
3.
Possible closing SPS: in locking mode, all the conditions after delay are met to
authorise synchronised closure
4.
5.
6.
7.
Application
C264/EN AP/C80
MiCOM C264/C264C
Page 265/348
(1)
(2)
(3)
(4)
(5)
(6)
(7)
FIGURE 312: INTERNAL SYNCHROCHECK MANDATORY DATAPOINTS
6.2.5.2
on/off control DPC: to control in / out of service of the synchrocheck via DPC
2.
on/off control SPC: to control in / out of service of the synchrocheck via SPC
3.
4.
on/off SPS (mandatory on internal synchrocheck and implicitly created): giving in/out
of service status of the synchrocheck via SPS
Do not forget to define on/off SPS/DPS as feedback of on/off control SPC/DPC if they exist.
(1)
(2)
(3)
(4)
FIGURE 313: SYNCHROCHECK OPTIONAL DATAPOINTS
C264/EN AP/C80
Application
Page 266/348
MiCOM C264/C264C
Substation
Ext manual CS
on/off ctrl DPC
on/off ctrl SPC
on/off DPS
on/off SPS
Feeder
Ext auto CS
on/off ctrl DPC
on/off ctrl SPC
on/off DPS
on/off SPS
Ext manual CS
on/off ctrl DPC
on/off ctrl SPC
on/off DPS
on/off SPS
Int synchrocheck
on/off ctrl DPC
on/off ctrl SPC
on/off SPS
mutually exclusive
mutually exclusive
- Yes
- No
S0280ENa
For an "Int synchrocheck" function, having its "automatic out of service" attribute set to
the "Yes" value, the "on/off ctrl DPC" or "on/off ctrl SPC" datapoint must be present.
"on/off ctrl DPC" or "on/off ctrl SPC" datapoint of "Int synchrocheck" synchrocheck
must have its profile attribute SBO mode set to "Direct Execute" or Direct Execute
with SBO popup
Application
C264/EN AP/C80
MiCOM C264/C264C
6.3
6.3.1
Auto-recloser behaviour
Page 267/348
The AutoRecloser built-in function is described in section 3.1.2 of chapter C264/EN FT.
6.3.2
Busbar,
Bus coupler,
Bus section,
Feeder,
Transformer,
Generic bay.
C264/EN AP/C80
Page 268/348
Application
MiCOM C264/C264C
Fill the relation is auto-recloser of, giving which circuit-breaker module is concerned
by the function.
2.
short name and long name of the auto-recloser used for logging, alarms ...
3.
4.
5.
unlocking way (Not used / Reinitialisation / Manual close / Both ways). For details
refer to previous description of lock of auto-recloser in section 6.3.1 Auto-recloser
behaviour.
6.
Fast 3 P reclose enable (No, Yes): if a synchrocheck exists for the breaker, autorecloser can bypass it during the 3-phases first cycle if the attribute is set to Yes.
7.
1st period monophased (range [100 ms, 5 s], step 10 ms): timer of the first singlephase cycle.
8.
1st period triphased (range [1 s, 60 s], step 10 ms): timer of the first 3-phases cycle.
9.
2nd period triphased (range [1 s, 3600 s], step 1 s): timer of the second 3-phases
cycle.
10.
3rd period triphased (range [1 s, 3600 s], step 1 s): timer of the third 3-phases cycle.
11.
4th period triphased (range [1 s, 3600 s] step 1 s): timer of the fourth 3-phases cycle.
12.
reclaim delay (range [1 s, 600 s], step 1 s): corresponds to reclaimc recovering timer
previously described in launch recovering timer of section 6.3.1 Auto-recloser
behaviour.
13.
unlock delay (range [1 s, 600 s], step 1 s): corresponds to reclaimml recovering
timer previously described in lock of auto-recloser of section 6.3.1 Auto-recloser
behaviour.
14.
manual close delay (range [1 s, 600 s], step 1 s): corresponds to reclaimmc
recovering timer previously described in lock of auto-recloser of section 6.3.1 Autorecloser behaviour.
Application
C264/EN AP/C80
MiCOM C264/C264C
Page 269/348
C264/EN AP/C80
Page 270/348
Application
MiCOM C264/C264C
Application
C264/EN AP/C80
MiCOM C264/C264C
Page 271/348
The two attributes "functioning mode (1 ph trip)" and "functioning mode (3 ph trip)"
must not be both set to "Not used" value
If "functioning mode (1 ph trip)" value is set to "1P-3P-3P-3P", then the following rules
must be respected:
- "1st period monophased" < "2nd period triphased"
- "1st period monophased" < "3rd period triphased"
- "1st period monophased " < "4th period triphased"
If "functioning mode (1 ph trip)" value is set to "1P-3P-3P", then the following rules
must be respected:
- "1st period monophased" < "2nd period triphased"
- "1st period monophased" < "3rd period triphased"
If "functioning mode (1 ph trip)" value is set to "1P-3P", then the following rule must be
respected:
- "1st period monophased" < "2nd period triphased"
If "functioning mode (3 ph trip)" value is set to "3P-3P-3P-3P", then the following rules
must be respected:
- "1st period triphased" < "2nd period triphased"
- "1st period triphased" < "3rd period triphased"
- "1st period triphased" < "4th period triphased"
If "functioning mode (3 ph trip)" value is set to "3P-3P-3P", then the following rules
must be respected:
- "1st period triphased" < "2nd period triphased"
- "1st period triphased" < "3rd period triphased"
If "functioning mode (3 ph trip)" value is set to "3P-3P", then the following rule must be
respected:
- "1st period triphased" < "2nd period triphased"
If "functioning mode (1 ph trip)" value is different from "Not used", then the "circuitbreaker type" must be set to "Single phase CircuitBreaker"
If "functioning mode (3 ph trip)" value is set to "Not used", then the "circuit-breaker
type" must be set to "Single phase CircuitBreaker"
State3: no failure
C264/EN AP/C80
Page 272/348
2.
Application
MiCOM C264/C264C
Auto-recloser st: is a MPS datapoint which gives the status of the auto-recloser
function. This is a system datapoint whose available states are:
3.
4.
5.
Application
C264/EN AP/C80
MiCOM C264/C264C
Page 273/348
C264/EN AP/C80
Application
Page 274/348
MiCOM C264/C264C
2.
lock/reinit: is a SPS used to lock / unlock the auto-recloser via SPS. Corresponds to
the AR_LOCK signal described in section 6.3.1 Auto-recloser behaviour
3.
4.
5.
6.
lock/reinit SPC: Signal to lock/unlock the auto-recloser via SPC. Corresponds to the
AR_LOCK signal described in section 6.3.1 Auto-recloser behaviour
7.
on/off ctrl DPC: to control in/out of service of the auto-recloser via DPC
8.
on/off ctrl DPS: to control in/out of service of the auto-recloser via DPS
Application
C264/EN AP/C80
MiCOM C264/C264C
Page 275/348
If "functioning mode (1 ph trip)" value is different from "Not used", then at least one of
the three SPS datapoints { "Trip PhA", "Trip PhB", "Trip PhC" } is mandatory
If "functioning mode (1 ph trip)" value is set to "Not used", then none of the three SPS
datapoints { "Trip PhA", "Trip PhB", "Trip PhC" } is allowed
The two datapoints { "on/off ctrl DPC", "on/off ctrl DPS" } are mutually exclusive and,
at least one of them is mandatory
The two datapoints { "lock/reinit SPC", "lock/reinit SPS" } are mutually exclusive. If the
"unlocking way" attribute value is set to "Reinitialization" or "Both ways" then, at least
one of the two datapoints is mandatory
C264/EN AP/C80
Page 276/348
Application
MiCOM C264/C264C
6.4
6.4.1
reset confirmation delay (range [0 s, 120 s], step 100 ms]: this delay corresponds to
time-out TR given in section 5.1.2.1 Persistence filtering of chapter C264/EN FT.
2.
set confirmation delay (range [0 s, 120 s], step 100 ms]: this delay corresponds to
time-out TS given in section 5.1.2.1 Persistence filtering of chapter C264/EN FT.
3.
start confirmation delay (range [1 s, 60 s], step 100 ms): the TCIP information must
appear before the time-out of this delay
4.
stop confirmation delay (range [1 s, 60 s], step 100 ms): the TCIP information must
disappear before the time-out of this delay
Application
C264/EN AP/C80
MiCOM C264/C264C
6.4.2
Page 277/348
(1)
short name and long name of the tap changer used for logging, alarms ...
2.
3.
maximal usable position (range [1, 64], step 1): must be greater than attribute (2).
4.
execution timeout (range [0, 60 s], step 100 ms): It is the maximum delay in which
tap position must have changed relatively to the current tap control in progress. If
delay expired bad acknowledgement is sent for tap control.
C264/EN AP/C80
Application
Page 278/348
MiCOM C264/C264C
DEVICE CONTROL
DEVICE SELECTION
(HARDWARE)
INPUTS
(i)
This SPS is a generic one added at transformer module level and configured as
feedback of SPC transformer selection (4).
1.
Goto min/max DPC: this datapoint is not managed by the tap changer built-in
function. If it is needed an ISAGRAPH automation has to be used.
2.
Raise/lower DPC: this datapoint is managed by the tap changer built-in function.
3.
MCB open SPC: this datapoint is managed by the tap changer built-in function.
4.
TAP Select SPC: this datapoint is managed by the tap changer built-in function
5.
Higher position: this SPS is not taken into account by the tap changer built-in
function. If it is needed an ISAGRAPH automation has to be used.
6.
Lower position: this SPS is not taken into account by the tap changer built-in
function. If it is needed an ISAGRAPH automation has to be used.
7.
Tap in progress: this SPS is taken into account by the tap changer built-in function.
(1)
(2)
(3)
(4)
(5)
(6)
(7)
(8)
"Raise/lower DPC" datapoint must have its profile attribute SBO mode set to "SBO
Operate Many"
Application
C264/EN AP/C80
MiCOM C264/C264C
Page 279/348
6.5
6.5.1
Tab
A
V
R
Parameter name
Min
Max
ON/OFF
Manual / Automatic
ON
Automatic
20000.0 V
100 V
1A
Type of regulation
PhAse voltage /
Compound voltage
Phase voltage
No/Only on AVR
locked/Always
AVR state*
AVR mode*
Transformer nominal voltage
Nominal voltage
Nominal current
Values
Step
No
-
No
T
A
R
G
E
T
V
O
L
T
A
G
E
60 s
Controls/RemoteNo/1/2/3/4/5
In % of Vn
In % of Vn
10
300
10
90% 105% 0,25%
95% 110% 0,25%
Controls
1
120
90%
110%
50V
10V
200V
0mn 480mn
10mn
60mn
3mn 10mn
1mn
5mn
0.1%
100%
100% 104%
0.1%
102%
103% 107%
0.1%
105%
106% 110%
0.1%
108%
93%
0.1%
95%
Default
500V
97%
100%
C264/EN AP/C80
Application
Page 280/348
Tab
MiCOM C264/C264C
Parameter name
Values
V
O
Min
Max
Step
10
0.1
0.5
No
Double wound
Yes/no
Voltage 1 / voltage 2 /
average
% of Vn
% of Vc
Voltage 1
0%
10%
1%
5%
80%
10%
50%
4%
0.25%
1.25%
2%
11%
1%
5%
20s
600s
10s
300s
L
T
A
G
E
0s
Tp
0s
120s
1s
0s
Ta
30s
180s
10s
120s
Compounding activation*
Active/ Inactive
Inactive
Compounding method
Active / Reactive
Active
0%
20%
0.5%
0%
0%
20%
0.5%
0%
0%
20%
0.5%
0%
0%
20%
0.5%
0%
0.01
0.1
Voltage correction
0.01
0%
Double A1
No/yes
No
Double B1
No/yes
No
Double A2
No/yes
No
Double B2
No/yes
No
Internal only
Autom/manual reset/
manual mode
Automatic
64
39
64
No
T
A
P
Default
Intermediate position
No/yes
Off/on
Off
0s
60s
1s
10s
Intermediate tap
64
T1
10s
70s
5s
60s
T2
2s
30s
2s
10s
0s
180s
5s
60s
Tb
20s
120s
10s
30s
Preset tap
39
0s
10s
1s
1s
5s
180s
5s
10s
1s
120s
1s
10s
60s
600s
10s
120s
10
10
120
30
0s
60s
1s
30s
Period in days
Application
C264/EN AP/C80
MiCOM C264/C264C
Tab
Page 281/348
Parameter name
Values
Min
Max
Step
Default
Only lower
on defined tap/lock
automatic reg
defined tap
Preset/current/lowest
Preset
Primary CB state
Open/close
Open
Overcurrent/overvoltage/
undervoltage
Signalization
Off
Off
Off/on
Off
Overcurrent threshold
% of In
50%
500% 10%
250%
0s
30s
0.1s
2s
Overcurrent delay
T
I
O
Off/on
Overvoltage threshold
% of Vn
Overvoltage delay
in
//
R
P
2s
30s
0.1s
-
Off/on
% of Vn
50%
100% 1%
70%
0s
30s
0.1s
2s
Off
0s
300s
10s
60s
No
Off/on
Transformer in parallel
Yes/No
Role
Master/Followe/Foll master
backup
Initial state
Off/on
Neg
Off
Off
-
Folbecmaster
Master/Follow
0s
120s
1s
60s
RPF used
Yes/No
No
In kV
0 kV
400 k
1 kV
63 kV
in % of In
0%
20%
1%
5%
Tconfirm in seconds
0s
30s
1s
5s
Ignore/block operat/reg.
reversely
Blockoperaton
in % of primary Vn
88%
120% 0.1%
100%
RPF deadband
in % of primary Vn
0.5
4.0
0.25
2.0
10s
70s
5s
60s
0s
Undervoltage threshold
T
R
130%
Off
100% 130% 1%
2s
30s
2s
10s
No compdg
RPF compound A1
20
RPF compound B1
20
No
RPF compound A2
RPF compound B2
in % of primary Vn/In
20
20
C264/EN AP/C80
Application
Page 282/348
MiCOM C264/C264C
double click the link Associated with; this opens the Relation link editor
click OK
click OK
In the MiCOM C264 that manages the bay where the AVR built-in function is created, set
that an AVR panel must be present.
The Period binder includes four bricks. Each includes a timetable H1 thru H24 (Hour tab)
and a definition of the days where this timetable applies (third tab):
WE#2 target: second day in the week-end (it must follow the preceding day in order)
Application
MiCOM C264/C264C
C264/EN AP/C80
Page 283/348
Example: define the target voltage number according to the schedule that follows:
Holidays definition is set in configuration, with a maximum of 10 days with a fixed date (ex:
14/07). If the current day is defined as a holiday, the target voltage values used are the ones
defined for holiday.
C264/EN AP/C80
Page 284/348
Application
MiCOM C264/C264C
Special days definition is set in configuration, with a maximum of 10 days with a fixed date
(ex: 11/01). If the current day is defined as a special day, the target voltage values used are
the ones defined for the weekdays (even if the day is a week end day 1 or 2, or a holiday).
6.5.2
AVR behaviour
The AVR built-in function is described in chapter C264/EN FT.
Application
C264/EN AP/C80
MiCOM C264/C264C
6.6
6.6.1
ATCC behaviour
Page 285/348
6.6.2.1
a "Voltage level" must have its "ATCC existence" attribute set to "No".
the "ATCC fct needs" is allowed neither under a "transformer" nor under a
"BusBar".
the "Tap changer" with its "Raise/lower DPC" datapoint are mandatory.
one of the two datapoints { "MCB position DPS", "MCB position SPS" } is
mandatory. They are mutually exclusive
the "transformer" must be linked to a Voltage level through one and only one of
the relations { "has its primary on", "has its secondary on" }. The Voltage level
must be different from the one under which the transformer is located.
(1)
Fill the relation is managed by, giving which computer runs and supervises ATCC
function at substation level.
2.
short name and long name of the ATCC used for logging, alarms ...
C264/EN AP/C80
Page 286/348
Application
MiCOM C264/C264C
General attributes:
calculation attributes
calculation period
calculation mode
Homing attributes
active homing
homing deadband
Compounding attributes
compounding method
Delays attributes:
Nominal attributes
Homing attributes
Hunting attributes
Inhibition attributes
Inhibition conditions attributes
Application
C264/EN AP/C80
MiCOM C264/C264C
Page 287/348
(1)
(2)
(3)
(4)
(5)
(6)
(7)
(8)
(9)
(10)
(11)
(12)
(13)
(14)
(15)
(16)
(17)
(18)
(19)
(20)
(21)
(22)
(23)
C264/EN AP/C80
Application
Page 288/348
MiCOM C264/C264C
When adding an ATCC to a substation, the following mandatory datapoints are automatically
created and must be configured (see section 5 DEFINING DATAPOINT):
(DPT_Sub 1)
(DPT_Sub 2)
(DPT_Sub 3)
(DPT_Sub 4)
(DPT_Sub 5)
ErrorLog SPS
(DPT_Sub 6)
On/off SPS
(DPT_Sub 7)
(DPT_Sub 1)
(DPT_Sub 2)
(DPT_Sub 3)
(DPT_Sub 4)
(DPT_Sub 5)
(DPT_Sub 6)
(DPT_Sub 7)
C0246ENb
voltage target 1
voltage target 2
voltage target 3
voltage target 4
voltage target 5
regulation attributes
Application
C264/EN AP/C80
MiCOM C264/C264C
Page 289/348
When a voltage level is concerned by an AVR function, do not forget to set correctly its
attribute nominal value (kV) (refer to section 6.1.3 Defining a Voltage level). It is used for
transformer nominal ratio computation.
(1)
(2)
(3)
(4)
(5)
(6)
(7)
(8)
(9)
(10)
(11)
FIGURE 331: SETTING ATCC FUNCTION ATTRIBUTES AT VOLTAGE LEVEL
6.6.2.3 Defining ATCC function needs at busbar level
For each busbar bay concerned by an ATCC function, extra ATCC configuration must be
done. For details about busbar bay creation, refer to section 6.1.4 Defining a Bay.
This is done via the Objects entry window at busbar level by clicking on mouses right
button.
setpoint ponderation
priority
C264/EN AP/C80
Application
Page 290/348
MiCOM C264/C264C
resistive coefficient
reactive coefficient
(1)
(2)
(3)
(4)
(5)
(6)
FIGURE 333: SETTING GENERAL BUSBAR FEATURES OF AN ATCC
When adding an ATCC function needs at busbar level, the following mandatory datapoints
are automatically created and must be configured (see section 5 DEFINING DATAPOINT):
(DPT_Bb 1)
ATCC inhibited
(DPT_Bb 2)
(DPT_Bb 3)
(DPT_Bb 4)
(DPT_Bb 5)
ATCC on/off
(DPT_Bb 6)
(DPT_Bb 7)
(DPT_Bb 8)
(DPT_Bb 9)
(DPT_Bb 10)
(DPT_Bb 11)
(DPT_Bb 12)
ATCC target 1
(DPT_Bb 13)
ATCC target 2
(DPT_Bb 14)
ATCC target 3
(DPT_Bb 15)
ATCC target 4
(DPT_Bb 16)
ATCC target 5
(DPT_Bb 17)
ATCC to target
(DPT_Bb 18)
BusBar voltage
Application
C264/EN AP/C80
MiCOM C264/C264C
Page 291/348
(DPT_Bb 1)
(DPT _Bb 2)
(DPT_Bb 3)
(DPT_Bb 4)
(DPT_Bb 5)
(DPT_Bb 6)
(DPT_Bb 7)
(DPT_Bb 8)
(DPT_Bb 9)
(DPT_Bb 10)
(DPT_Bb 11)
(DPT_Bb 12)
(DPT_Bb 13)
(DPT_Bb 14)
(DPT_Bb 15)
(DPT_Bb 16)
(DPT_Bb 17)
(DPT_Bb 18)
C0348ENa
Impedance attribute, whose unit is a percent of value for S=100 MVA (range
[0,01 to 24,99 by step 0,01):
MCB position SPS or DPS is mandatory (refer to 6.1.5.8).
Add and configure a Tap-changer built-in function for the transformer module (refer to
section 6.4 Defining a Tap changer built-in function), with the following features:
Add and configure an ATCC fct needs object for transformer, via the Objects entry
window at transformer module level by clicking on mouses right button (1):
C264/EN AP/C80
Application
Page 292/348
MiCOM C264/C264C
(1)
up range
down range
Overcurrent ratio
(1)
(2)
(3)
FIGURE 336: SETTING GENERAL TRANSFORMER FEATURES OF AN ATCC
When adding ATCC function needs at transformer level, the following mandatory datapoints
are automatically created and must be configured (see section 5 DEFINING DATAPOINT):
(DPT_Trf 1)
ATCC on/off
(DPT_Trf 2)
ATCC homing
(DPT_Trf 3)
ATCC hunting
(DPT_Trf 4)
(DPT_Trf 5)
(DPT_Trf 6)
TAP invalid
(DPT_Trf 7)
Run away
(DPT_Trf 8)
(DPT_Trf 9)
(DPT_Trf 10)
MCB trip
(DPT_Trf 11)
ATCC overcurrent
(DPT_Trf 12)
ATCC overvoltage
Application
C264/EN AP/C80
MiCOM C264/C264C
(DPT_Trf 13)
ATCC low-voltage
(DPT_Trf 14)
(DPT_Trf 15)
Second. voltage
(DPT_Trf 16)
Second. current
(DPT_Trf 17)
Second. active P
(DPT_Trf 18)
Second. react. Q
Page 293/348
(DPT_Trf 1)
(DPT_Trf 2)
(DPT_Trf 3)
(DPT_Trf 4)
(DPT_Trf 5)
(DPT_Trf 6)
(DPT_Trf 7)
(DPT_Trf 8)
(DPT_Trf 9)
(DPT_Trf 10)
(DPT_Trf 11)
(DPT_Trf 12)
(DPT_Trf 13)
(DPT_Trf 14)
(DPT_Trf 15)
(DPT_Trf 16)
(DPT_Trf 17)
(DPT_Trf 18)
C0349ENa
special (german) double switch, in fact association of earth switch and disconnector,
C264/EN AP/C80
Application
Page 294/348
MiCOM C264/C264C
At SCE level, nodes are special attributes of module, whose values are given by integers.
Each identified node in the electrical topology has a unique arbitrary value. Two
interconnected modules share the same node value. The best practice to value nodes is to
do it directly from the substation electrical diagram.
obsolete
External line module of Feeder bay, where one node reference must be filled (2),
Circuit-breaker and Switchgear module, where two node references must be filled
(3),
Transformer module, where at least two node references must be filled, and a extra
one in case of neutral compensation (4),
Capacitor & inductor module, used for neutral compensation, where one node
reference must be filled (5); it corresponds to the neutral node of the associated
transformer.
(1)
Application
C264/EN AP/C80
MiCOM C264/C264C
Page 295/348
(2)
(3)
(4)
(5)
FIGURE 343: SETTING CAPACITOR NODE REFERENCES (ATCC FUNCTION)
C264/EN AP/C80
Page 296/348
6.7
Application
MiCOM C264/C264C
Using ISaGRAF workbench for slow automations, where the execution of the
automation is cyclic, based on a cycle that can not be less than 50 ms.
Using extended logical function modelling (boolean, timer, bistable functions) via FBD
workbench, where the execution is event-driven.
User function can be put at any level of the electrical topology except Site. Moreover, slow
automation is unavailable at module level. User function must always specify on which
computer it runs.
Extra solutions for simpler needs exist at configuration level (they could be seen as
restriction of particular FBD functions):
6.7.1
6.7.1.1
FBD body (coding in PSL) definition via launching at SCE level the FBD editor
(contextual menu on the FBD interface object) and doing diagram edition of boolean,
timer and bistable functions, and links to input/output plugs.
Application
C264/EN AP/C80
MiCOM C264/C264C
Page 297/348
FIGURE 344: ADDING AN FBD FAST AUTOMATION (E.G. FOR FEEDER BAY LEVEL)
The FBD fast automation features must be set:
1.
Edit the relation runs on, to set computer PLC manages the automation. This relation
is automatically established by SCE if FBD automation is located under a bay whose
computer manager has ever been entered (inheritance mechanism, for details about
computer manager of a bay refer to section 6.1.4 Defining a Bay).
2.
Type the short name and long name of the fast automation used for internal SCE
identification.
C264/EN AP/C80
Application
Page 298/348
6.7.1.2
MiCOM C264/C264C
short name and long name of the fast automation used for identification in FDB
editor
Application
C264/EN AP/C80
MiCOM C264/C264C
Page 299/348
Once added, FBD output plug features must be set at SCE level:
1.
short name and long name: used for identification in FDB editor
C264/EN AP/C80
Application
Page 300/348
MiCOM C264/C264C
Once launched, FBD editor allows diagram edition of the automation. For details about FBD
user manual refer to <the PACiS-SCE Documentation>
1.
2.
3.
4.
5.
6.7.1.5
Add the relation uses <XXX> (1) at FBD input level, where XXX corresponds to the
datapoint kind (SPS, DPS, MPS, MV, SPC or DPC)
(1)
Application
C264/EN AP/C80
MiCOM C264/C264C
Page 301/348
Add the relation controls <XXX> (1) or produces SPS at FBD input level, where XXX
corresponds to the control datapoint kind (SPC or DPC)
(1)
C264/EN AP/C80
Page 302/348
6.7.1.6
Application
MiCOM C264/C264C
Default value, that is the value till it is not modified with MiCOM S1
Application
C264/EN AP/C80
MiCOM C264/C264C
6.7.2
Page 303/348
client link, that means that the slow automation uses the datapoint that is acquired or
managed outside the ISaGRAF automation. For instance, the load shedding
automation can be client of some circuit-breaker status input datapoints and some
circuit-breaker control output datapoints.
server link, that means that the slow automation produces or manages the datapoint.
For instance, a slow automation can be used to produce the sum of feeder
measurements. This sum is also a measurement located at voltage level for instance.
define the slow automation body definition via launching from the SCE the ISaGRAF
editor (contextual menu on the slow automation interface object) and using available
languages and previously client/server defined links
C264/EN AP/C80
Page 304/348
6.7.2.1
Application
MiCOM C264/C264C
Fill the relation runs on, giving which computer PLC will manage the automation. This
relation is automatically filled by SCE if slow automation is located under a bay whose
computer manager has ever been entered (for details about computer manager of a
bay refer to section 6.1.4 Defining a Bay)
2.
short name and long name of the slow automation used for logging and alarm
Application
C264/EN AP/C80
MiCOM C264/C264C
6.7.2.2
Page 305/348
C264/EN AP/C80
Application
Page 306/348
6.7.2.3
MiCOM C264/C264C
Application
C264/EN AP/C80
MiCOM C264/C264C
6.7.2.4
Page 307/348
FIGURE 358
C264/EN AP/C80
Application
Page 308/348
6.7.2.5
MiCOM C264/C264C
(4)
FIGURE 359: DEFINING ISAGRAF IO PREFIX FOR AN INPUT
Configuration rules and checks
6.7.2.6
Application
C264/EN AP/C80
MiCOM C264/C264C
6.7.2.7
Page 309/348
C264/EN AP/C80
Application
Page 310/348
6.7.2.8
MiCOM C264/C264C
6.7.2.9
Application
C264/EN AP/C80
MiCOM C264/C264C
Page 311/348
ISaGRAF editor allows diagram edition of the automation. For details about ISaGRAF
workbench and SCE datapoint coupling, refer to SCE_ENAP.Erreur ! Source du renvoi
introuvable..
Defining a group
A group is a logical OR, AND, NOR or NAND combination of components whose kind is
SPS, DPS or groups. A component can belong to several groups. Resulting datapoint
associated to a group is a SPS object called Group SPS in data modelling.
Group SPS can only belong to bays or modules. The computer that manages the bay (of
eventually the bay of the module) always computes it. Its composition description is done via
linking it to SPS, DPS, or Group SPS.
A group SPS can be seen as a particular fast automation reduced to one boolean function
with one implicit output plug (the group SPS itself) and input plugs corresponding to each
component of the group.
The addition of a group SPS is done via the Objects entry window at bay or module level of
the electrical topology by clicking on mouses right button.
For more details about electrical topology creation, refer to section 6.1 Defining an electrical
topology.
FIGURE 365: ADDING A GROUP SPS (E.G. FOR FEEDER BAY LEVEL)
C264/EN AP/C80
Application
Page 312/348
MiCOM C264/C264C
Once added, Group SPS features must be set at SCE level, as SPS datapoint. For details
about SPS datapoint configuration, refer to section 5.1.2 Defining an SPS datapoint.
Nevertheless, the specific attribute group type (1) must be set for the group. It corresponds
to the logical function (OR, AND, NOR or NAND) applied on all the components of the group.
Add the relation contains the <XXX> (1) at Group SPS level, where XXX corresponds
to the datapoint kind (SPS or DPS)
(1)
Application
C264/EN AP/C80
MiCOM C264/C264C
6.7.4
Page 313/348
Add the relation controls on state change (1) at SPS/DPS level; two relations are
available depending on control kind to act (SPC or DPC). Choose the correct one.
Set the relation attributes (3) giving for each state of the xPS, the order to send: None,
Open (resp. Off) or Close (resp. On) for DPC (resp. SPC).
direct to output relay i.e the xPS activates directly the associated xPC
through control sequence i.e. the xPS activates a full control sequence
C264/EN AP/C80
Application
Page 314/348
6.7.5
MiCOM C264/C264C
Create the three datapoints and configure them (see section 5 DEFINING
DATAPOINT)
At the DPS level, add the relations has open state given by (1) and has closed state
given by (2)
Fill the two relations with the previously created SPS datapoint
(1)
(2)
Defining interlocking
Any DPC (or SPC) belonging to a bay or module can have interlocking equation for opening
order (Off order for SPS) and/or closing order (On order for SPC).
Interlocking equation corresponds to a logical function that must be true to send the order.
In data modelling, interlocking equation are put under SPC or DPC by adding specific SPS:
These SPS contain the logical function definition of the interlocking that is coded with the
FBD editor.
Interlocking equation diagrams seem FBD fast automation diagrams, except that:
The addition of an interlock SPS is done via the Objects entry window at SPC/DPC
datapoint level by clicking on mouses right button (1).
For more details about electrical topology creation, refer to section 6.1 Defining an electrical
topology.
Application
C264/EN AP/C80
MiCOM C264/C264C
Page 315/348
FIGURE 370: ADDING AN INTERLOCK SPS (E.G. FOR MODULE DPC LEVEL)
Once added, interlock SPS features must be set at SCE level, as SPS datapoint. For details
about SPS datapoint configuration, refer to section 5.1.2 Defining SPS datapoint.
To define interlocking equation for an interlock SPS:
Configure this FBD interlock (refer to section 6.7.1 Defining an FBD fast automation),
with the existing following restrictions:
For its body description via FBD editor, timer and bistable functions do not exist.
C264/EN AP/C80
Page 316/348
6.7.7
Application
MiCOM C264/C264C
Add the relation has for AutoManu dependency (1) at control level; two relations are
available depending on the input kind setting the dependency (SPS or DPS). Choose
the correct one.
For each "DPC", "SPC" or "Setpoint" datapoint, 2 relations "has for AutoManu
dependency" are available, but they are mutually exclusive.
Application
C264/EN AP/C80
MiCOM C264/C264C
6.8
Page 317/348
Including IsaGraf functions for Load Shedding priority process and topology
calculation
Data flow
IsaGraph
OI or (Scada+GTW)
SetPoint for MaskPrio x LSP1-1
SetPoint for MaskPrio x LSP2-1
Begin
Set_LSP (MaskPrio, REF_LSP1-1)
Set_LSP (MaskPrio, REF_LSP2-1)
xPSTriggers
input
xPSTriggers
input
R output MASK
LSPi-1
R output MASK
C264 Fi
C264F2
LSP2-1
C264 F1
LSP1-1
6.8.1
C0497ENa
The C264-M supports the ISAGRAF automation which allows defining FLS preselections
and also automations (ISAGRAF and/or PSL) which allow to test / simulate the FLS.
It is a client of the OI and receives the setpoints from it. The FLS preselections are
transmitted to C264-Fi using the LSP (Load Shedding Preselection) datapoints, transmitted
by GOOSE.
It is a server of the OI and is used to re-transmit the datapoints coming from C264-Fi to OI
using datapoint associations mechanisms.
The C264-Fi control the feeder and the breaker trip.
In order to secure performance time of breaker trip, C264-Fi are not servers of the OI and
C264-M. They only manage the PSL which allows to trip the feeder regarding the cause and
the preselection. They are dedicated to the acquisition of datapoints used for the Fast Load
Shedding function (only FLS triggers as input and breaker trip as output).
C264/EN AP/C80
Page 318/348
Application
MiCOM C264/C264C
The C264-Fi can be redundant. To avoid time performance limitation, the client/server
mechanism used in case of C264 redundancy (to exchange the FailSt information) will be
replaced by a GOOSE transmission of this information.
6.8.2
Priority Setpoints
Priority setpoints are analogue setpoints whose value range from 0 to 65535.
The profile is as follows:
6.8.3
Short name
Long name
Used profile The profile is only used to define the printing / archiving status at OI
level (alarms, interlocking values are not used).
Application
C264/EN AP/C80
MiCOM C264/C264C
Page 319/348
C264/EN AP/C80
Application
Page 320/348
6.8.4
MiCOM C264/C264C
3 graphical symbols, associated to the ON, OFF and UNKNOWN states of the LSP
bits
This representation forces to have the same graphical representation for the 16 bits of the
LSP.
6.8.5
NOTE:
Application
C264/EN AP/C80
MiCOM C264/C264C
6.8.6
Page 321/348
16
6.8.6.1
15
14
13
12
11
10
6.8.6.2
Uncertain: if not connected or not unconnected (in the event of a faulty board
connection measurement for example)
C264/EN AP/C80
Page 322/348
6.8.7
Application
MiCOM C264/C264C
Datapoints
For SPC data Point:
Input xPS Triggers can be SPS, DPS. The possible states are described into the
Product specification document. The FSS can be applied to the xPS datapoints
6.8.8.1
MASK object
For each command breaker using into Fast Load Shedding, a PSL/FBD is created.
This PSL included the new MASK object.
One or more MASK object can be created into the FBD/PSL.
This MASK object has:
6.8.8.2
One Input LSP value. The LSP value is GOOSE sending from Isagraf.
Trigger definition
The triggers are standard xPS. As soon as they will be used in a PSL, they will be
automatically GOOSE-defined using the SBUS automatic addressing.
An xPS input Trigger is mapped on input bit priority MASK Object of PSL/FBD
The combination of the xPS input triggers and the ISaGRAF LSP (transmitted by GOOSE)
process the output PSL command datapoint (link to a breaker command).
The xPS input triggers state can be changed from:
Another C264 Fi
Application
C264/EN AP/C80
MiCOM C264/C264C
Options:
Page 323/348
C264/EN AP/C80
Page 324/348
6.8.9
Application
MiCOM C264/C264C
xPS triggers comes from another C264 M, C264P (frequency threshold), SPS from out
of range measurement:
Topology calculation
An ISaGRAF function allows to define if 2 devices are connected:
is_connected_to (node1, node2, state) with state = connected, unconnected, uncertain, and
node1 / node2 the reference of the nodes of the 2 devices.
The FORCED <state> and SUBSTITUTED <state> status are taken into account as the
normal <state> of the datapoint in the topology calculation. The SUPPRESSED status is
taken into account as the UNKNOWN status.
Two nodes are connected if it exists at least one chain of devices between the 2 nodes
which are closed, forced closed or substituted closed. Two nodes are unconnected if all
chains of devices between the 2 nodes are open, forced open or substituted open. In all
others cases, the status between two nodes is uncertain.
Application
MiCOM C264/C264C
6.8.10
C264/EN AP/C80
Page 325/348
C264/EN AP/C80
Page 326/348
6.9
Application
MiCOM C264/C264C
Once the Load function object is edited, the user cant change its type,
No child of Load function object can be added from the Object Entry Area,
No predefined profile available for data points of a Load function object can be
deleted.
The user can edit a Load function by the contextual menu Load function Edit as show it
the figure below:
Application
MiCOM C264/C264C
Fill out the window fields:
C264/EN AP/C80
Page 327/348
C264/EN AP/C80
Application
Page 328/348
7.
MiCOM C264/C264C
7.1
short name and long name: used for internal SCE identification.
2.
reference index (range [0, 150]: that must be unique for the set of defined bitmaps.
This index will be used in bay mimic definition as described previously.
3.
type (Single / 5-uple): single is used for static bitmap definition, 5-uple allows dynamic
bitmap definition as described previously.
4.
file name by default: corresponds to the filename containing the bitmap definition
used for default representation.
5.
file name for 'open' state: visible only if type is set to 5-uple: corresponds to the
filename containing the bitmap definition used for open state representation.
6.
file name for 'closed' state: visible if type is set to 5-uple: corresponds to the
filename containing the bitmap definition used for closed state representation.
7.
file name for 'withdrawn open' state: visible if type is set to 5-uple: corresponds to
the filename containing the bitmap definition used for withdrawn open state
representation.
Application
C264/EN AP/C80
MiCOM C264/C264C
8.
Page 329/348
file name for 'withdrawn closed' state: (visible if type is set to 5-uple): corresponds
to the filename containing the bitmap definition used for withdrawn closed state
representation.
(1)
(2)
(3)
(4)
(5)
(6)
(7)
(8)
FIGURE 374: SETTING BITMAP ATTRIBUTES
Attributes (7) and (8) can be omitted if breakers and switchgears represented in bay mimic
are not concerned with withdrawn information.
To set a file name (attributes (4) to (8)) and define graphically a bitmap:
save the graphical definition of the bitmap by giving a file name in bitmap editor
For details about bitmap editor usage refer to SCE users manual.
C264/EN AP/C80
Page 330/348
Application
MiCOM C264/C264C
The "reference index" attribute value of each "Bitmap" of the "Bitmap table" must be
unique.
Depending on the "type" attribute value, 1 or 5 PNG file(s) can be linked to a Bitmap.
For each one, the bitmap size must be 512 bytes.
Application
C264/EN AP/C80
MiCOM C264/C264C
7.2
Page 331/348
7.2.1
C264/EN AP/C80
Application
Page 332/348
MiCOM C264/C264C
To define labels of login, 17 characters are available (only 10 in case of Chinese language).
The CYBER SECURITY tab is used to customize the warning and security log labels:
7.2.2
Creating a workspace
The addition of a workspace is done via the Objects entry window at graphic level by
clicking on the mouses right button. Once added, computer workspace general features
must be set:
Define which GHU200 board is concerned by created workspace by filling the relation
has for workspace at concerned GHU board level (refer to section 4.4.2.2).
Define the short and long name attributes of the workspace used for internal SCE id:
Application
C264/EN AP/C80
MiCOM C264/C264C
Page 333/348
7.3
7.3.1
short name of the bay mimic used for internal SCE identification.
2.
3.
module name display (No / Yes) this attribute defines if module short names are
displayed at mimic level when a module is represented on bay mimic (refer to section
7.3.3 Defining dynamic part: pre-defined dynamic text, generic module representation,
transformer representation).
4.
Fill the relation represents, giving which bay is represented by the mimic (for details
about bay refer to section 6.1.4 Defining a Bay).
5.
If necessary, set the attribute mimic rank of the represents relation to correct value.
This attribute is used when 2 mimics are configured to display an entire bay: as bay is
split in 2 representations, the mimic rank attribute gives their display rank at computer
LHMI level (1 or 2).
C264/EN AP/C80
Application
Page 334/348
MiCOM C264/C264C
(1)
(2)
(3)
(4)
(5)
FIGURE 379: SETTING BAY MIMIC FEATURES
When adding a bay mimic at workspace level, its core structure (canvas) is automatically
created and displayed at SCE level, via bay mimic editor and in SCE tree browser. Its core
structure consists of:
1.
2.
3.
Reserved zone for interlocking bypass in progress information ((3) in tree browser)
4.
5.
Configurable zone for graphical representation of the bay (static and dynamic parts)
6.
Application
C264/EN AP/C80
MiCOM C264/C264C
Page 335/348
(1)
(2)
(3)
(4)
(5)
(3)
(2)
(4)
C264/EN AP/C80
Application
Page 336/348
MiCOM C264/C264C
The computer managing a bay represented by a "Bay mimic" must be the same as the
one linked to the "Comp. workspace" (computer workspace) of this "Bay mimic".
For a Computer, the maximum count of managed bays (relation "is managed by")
which are linked to a "Bay mimic" (relation "represents"), is 12.
Graphic
Comp. workspace
Bay mimic
LHMI Transformer
LHMI Gen module
LHMI bitmap
LHMI line
LHMI text
7.3.2
LHMI line: horizontal or vertical line with configurable thickness and length
LHMI bitmap: bitmap that references a bitmap object in the bitmap table (see 7.1
Defining a bitmap) where default representation is only taken into account
Once added, these elements automatically appear in the window of the bay mimic editor at
SCE level.
Configuration rules and checks
7.3.2.1
The coordinates (x, y) of a symbol must not be located outside the mimic area.
Adding a line
The addition of a line in bay mimic is done via the Objects entry window at bay mimic level
by clicking on mouses right button.
Application
C264/EN AP/C80
MiCOM C264/C264C
Page 337/348
2.
3.
4.
5.
6.
(1)
(2)
(3)
(4)
(5)
(6)
FIGURE 382: SETTING LINE ATTRIBUTES
Abscissa, ordinate, length and thickness of a LHMI line can be directly adjusted with the
mouse in bay mimic editor (for detail, refer to SCE users manual)
7.3.2.2
Adding a bitmap
The addition of a bitmap in bay mimic is done via the Objects entry window at bay mimic
level by clicking on mouses right button.
C264/EN AP/C80
Application
Page 338/348
MiCOM C264/C264C
2.
3.
4.
bitmap reference: corresponds to a link in the bitmap table (refer to section 7.1
Defining a bitmap table)
(1)
(2)
(3)
(4)
FIGURE 384: SETTING BITMAP ATTRIBUTES
Abscissa and ordinate of a bitmap can be directly adjusted with the mouse in bay mimic
editor (for detail, refer to SCE users manual)
Configuration rules and checks
7.3.2.3
The link from an element to its bitmap is defined with the attribute "bitmap reference".
The value of this attribute must refer to an existing bitmap in the "Bitmap table".
Application
C264/EN AP/C80
MiCOM C264/C264C
Page 339/348
2.
3.
Defining dynamic part: pre-defined dynamic text, generic module representation, transformer
representation
To define dynamic part of computer bay mimics, 3 kinds of objects are available:
Generic module representation: used to display module status, linked to a specific SPS or
DPS electrical datapoint. Implicit link to possible xPC associated datapoint is given to
computer for command purpose at local HMI level, via the existence of the relation is
feedback of between the xPS and the xPC.
an optional current TPI value object to display dynamically the current value of
the TPI,
an optional max TPI value object to display upper available value for the TPI
an optional min TPI value object to display lower available value for the TPI
C264/EN AP/C80
Page 340/348
7.3.3.1
Application
MiCOM C264/C264C
short name of the time information area used for internal SCE identification
2.
3.
Application
C264/EN AP/C80
MiCOM C264/C264C
7.3.3.2
Page 341/348
2.
Local/remote status
3.
(1)
(2)
(3)
FIGURE 389: POSITIONNING PRE-DEFINED TEXT INFORMATION IN BAY MIMIC
7.3.3.3
C264/EN AP/C80
Page 342/348
7.3.3.4
Application
MiCOM C264/C264C
the dynamic representation itself (LHMI Gen module), that is linked to SPS or DPS
datapoint and to a dynamic bitmap in bitmap table
the graphical name of the module (Name), always located on the right of the module
representation
The addition of a generic module representation in bay mimic is done via the Objects entry
window at bay mimic level by clicking on mouses right button.
2.
3.
4.
control availability (No / Yes): attribute to precise if control of the module can be
directly done via bay mimic. This attribute is significant if SPS/DPS linked to the
generic module representation (via (5) relation) is feedback of a control SPC or DPC.
If so, control availability concerns this SPC/DPC
5.
Relation is managed by that must be filled to precise which SPS or DPS is used for
bitmap animation
6.
multi-bitmap reference: corresponds to a link in the bitmap table (refer to section 7.1
Defining a bitmap table)
7.
Application
C264/EN AP/C80
MiCOM C264/C264C
Page 343/348
(1)
(2)
(3)
(4)
(5)
(7)
(6)
FIGURE 392: SETTING FEATURES OF GENERIC MODULE REPRESENTATION
Coordinates (x and y) of a generic module can be directly managed by using mouse in bay
mimic editor (for detail, refer to SCE users manual).
Configuration rules and checks
The link from an element to its bitmap is defined with the attribute: "bitmap reference".
The value of this attribute must refer to an existing bitmap in the "Bitmap table".
The "Bitmap" linked to a "LHMI xPS MultiSt" MultiState must be defined as follows:
- its "type" attribute must be set to "5-uple" value
-its 3 first file names { "file name by default", "file name for 'open' state", "file name for
'closed' state" } are mandatory and each one must be unique.
Furthermore, if the MultiState is linked to a SPS or DPS datapoint of a module
containing a "Withdrawn" SPS datapoint, through the "is managed by" relation, then
the following constraints are added to the "Bitmap" definition:
- its 2 file names { "file name for 'withdrawn open' state", "file name for 'withdrawn
closed' state" } are both mandatory and each one must be unique.
C264/EN AP/C80
Page 344/348
7.3.3.5
Application
MiCOM C264/C264C
the dynamic representation itself (LHMI Gen module), that is linked to SPS or DPS
datapoint and to a dynamic bitmap in bitmap table
the graphical name of the module (Name), always located on the right of the module
representation
The addition of a transformer representation in bay mimic is done via the Objects entry
window at bay mimic level by clicking on mouses right button.
2.
3.
4.
control availability (No / Yes): attribute to precise if control of the transformer can be
directly done via bay mimic. This attribute is significant if Raise/Lower DPC control
exists for Tap changer built-in function containing the TPI datapoint used for
transformer animation (via (5) relation). If so, control availability concerns this DPC.
5.
Relation is managed by that must be filled to precise which TPI is used for
transformer animation.
6.
bitmap reference: corresponds to a link in the bitmap table (refer to section 7.1
Defining a bitmap table).
7.
module name value: name of the transformer: text displayed on LCD (up to 4
characters).
Application
C264/EN AP/C80
MiCOM C264/C264C
Page 345/348
(1)
(2)
(3)
(4)
(5)
(7)
(6)
FIGURE 394: SETTING FEATURES OF TRANSFORMER REPRESENTATION
Abscissa and ordinate of a transformer can be directly adjusted with the mouse in bay mimic
editor (for detail, refer to SCE users manual)
When adding a transformer representation, extra values about associated TPI datapoint can
be placed in the bay mimic:
The addition of such TPI information in bay mimic is done via the Objects entry window at
transformer representation level by clicking on mouses right button.
C264/EN AP/C80
Application
Page 346/348
MiCOM C264/C264C
7.3.4
The link from an element to its bitmap is defined with the attribute: "bitmap reference".
The value of this attribute must refer to an existing bitmap in the "Bitmap table".
scale (120% / 200% / No bargraph), to precise which representation is used for the
MV in the bay mimic
For each visualized MV datapoint, the "transmission on event" attribute must be set
neither to "Cyclic short period" value nor to "Cyclic long period" value to avoid overflow
of the Bay mimic input buffer.
Application
C264/EN AP/C80
MiCOM C264/C264C
7.4
Page 347/348
(1)
FIGURE 398: DISPLAYING DATAPOINT STATUS WITH LED (E.G. FOR BAY SPS DATAPOINT)
Once added at SPS (resp. DPS) level, the relation must be filled with the relevant associated
led and the following relation attributes should be updated:
1.
Led status for Set state (resp 'Closed'): ( Off / On / Blinking slow / Blinking fast)
2.
Led status for Reset state (resp 'Open'): ( Off / On / Blinking slow / Blinking fast)
3.
Led status for Invalid state: ( Off / On / Blinking slow / Blinking fast)
(1)
(2)
(3)
FIGURE 399: SETTING LED STATUS FOR A DATAPOINT (E.G. FOR SPS DATAPOINT)
Configuration and checks
If the value of the "HMI type" attribute is "Simple", then "Led#4" must not be used (no
relation link from "Led#4" to a datapoint).
C264/EN AP/C80
Application
Page 348/348
MiCOM C264/C264C
BLANK PAGE
Lexicon
C264/EN LX/C80
LEXICON
Lexicon
C264/EN LX/C80
Page 1/14
CONTENT
1.
2.
LEXICON
C264/EN LX/C80
Lexicon
Page 2/14
BLANK PAGE
Lexicon
C264/EN LX/C80
Page 3/14
1.
C264/EN LX/C80
Lexicon
Page 4/14
2.
LEXICON
AC
Alternating Current
AccI
Accumulator Input
ACSI
A/D
Analog/Digital
ADC
AE
qualifier
AI
AIS
AIU
Analogue Input Unit (Computer C264 Board name for DC Analogue Input)
Alarm
AO
Analogue Output
Value corresponding to a desired output current applied to a DAC.
AOU
Analogue Output Unit (computer C264 board name for Analogue Output)
API
AR
Auto-Reclose
ARS
Auto-Recloser
ASCII
ASDU
ASE
ATCC
AVR
Bay
BCD
BCP
BCU
BI
Lexicon
C264/EN LX/C80
Page 5/14
BIU
BNC
B-Watch
CAD
CAS
CASe
Computer C264 rack
CB
Circuit Breaker
Specific dipole switch with capability to make line current and break fault
current. Some have isolation capability (nominal-earth at each side)
CBC
CC
Complemented Contact
CCU
CDM
Class
Define in IEC61850 as: description of a set of objects that share the same
attributes, services, relationships, and semantics
Client
Define in IEC61850 as: entity that requests a service from a server and that
receives unsolicited messages from a server
CM
CoMissioning
CAT
CO
COMTRA
DE
CPU
CRC
CSV
CT
Current Transformer
Basically the electric device connected to process and extracting a current
measurement. By extension part of a device (C264) that receives AC values
and convert it to numerical measurement value.
CT/VT
Current and Voltage transformers
(Conventio By extension, it is the C264 TMU board.
nal)
CT/VT
(NonConventio
nal or
intelligent)
C264/EN LX/C80
Lexicon
Page 6/14
CSV
DAC
DAC
DB
DataBase
Tool or set of data that define all configuration of a system or specific device
like computer. Opposed to setting or parameter DB has a structure that can not
be modified on line. DB are always versioned.
DB-9
DBI
Dont Believe It
Term used for undefined state of a double point when input are not
complementary. DBI00 is state motion or jammed. DBI11 is undefined.
DBID
DC
Direct Current
DC, DPC
DCF77
DCO
DCP
DCS
DCT
Double CounTer
Counter based on 2 DI with complementary states (counting switchgear
manoeuvre for example)
DE
Direct Execute
DELTA
Device
DHMI
DI
Digital Input
Binary information related to the presence or to the absence of an external
signal, delivered by a voltage source.
DIN
DIU
DC Input Unit
Computer C264 Board name for Digital Input
DLL
Lexicon
C264/EN LX/C80
Page 7/14
DM
Digital Measurement
Is a measurement value which acquisition is done by DI and a specific coding
BCD, Gray, 1 among N
DNP3.0
DO
Digital Output
Used to apply a voltage to an external device via a relay, in order to execute
single or dual, transient or permanent commands.
DOF
Degree Of Freedom
Used for a template attribute, that can be modified or not when used. An attribute has a degree of freedom if a user can modify its values on its instances
DOU
DP
Double Point
Information/control derived from 2 digital inputs/output; usually used for
position indication of switching devices (OPEN, CLOSE).
DPC
DPS
ECDD
ECU
EH90
EMC
Electro-Magnetic Compatibility
EPATR
Event
FAT
FBD
FIFO
FO
Fibre Optic
FP
Front Panel
FTP
FLS
FSS
Gateway
Level 6 session of OSI, the gateway is any device transferring data between
different networks and/or protocol. The RTU function of the C264 gives a
gateway behaviour to SCADA or RCP level. PACIS Gateway is separate PC
base device dedicated to this function.
GHU
GIS
C264/EN LX/C80
Lexicon
Page 8/14
GLOBE
GLOBE Brick
GMT
GPS
GOOSE
GPT
Group
GSSE
Hand
Dressing
HMGA
HMI
HSR
HTML
HV
I/O
Input/Output
ICD
IEC
IED
IP
Internet Protocol
IRIG-B
JAMMED
Kbus
(Kbus
Courier)
Term used for the protocol Courier on K-Bus network (kind of RS422).
LAN
L-BUS
Legacy Bus
Generic name of Legacy or field networks and protocols used to communicate
between C264 (Legacy Gateway function) and IED on field bus. Networks are
based on (RS232,) 422, 485. Protocols are IEC 60850-5-103 (T103 or VDEW),
Modbus Schneider Electric or MODICON
LCD
LD
LED
LF
Low Frequency
Lexicon
C264/EN LX/C80
Page 9/14
LOC
L/R
Local / Remote
Local /
Remote
Control
Mode
When set to local for a given control point it means that the commands can be
issued from this point, else in remote control are issue for upper devices.
LSB
LSP
LV
Low Voltage
MAFS
MC
Modular Computer
MCB
MDIO
Measurem Values issued from digital inputs or analogue inputs (with value, state, time tag)
ents
Metering Values computed depending on the values of digital or analogue inputs during
(non-tariff) variable periods of time (time integration).
Metering
(tariff)
MIDOS
MMC
MMS
ModBus
Module
Word reserved in PACIS SCE for all electric HV devices. It groups all switchgears, transformer, motors, generators, capacitors,
MOTION
MPC
MV
Medium Voltage
MVAR
NBB
NC
NO
OBS
OI
Operator Interface
OLE
C264/EN LX/C80
Lexicon
Page 10/14
OLTC
OMM
OPC
Operation Sum of time periods, a primary device is running under carrying energy, e.g.
hours
circuit breaker is in Close state and the current is unequal 0 A.
OSI
OWS
PACiS
PLC
POW
Point On Wave
Point on wave switching is the process to control the three poles of an HVcircuit breaker in a way, to minimise the effects of switching.
PSL
PSTN
RCC
RCP
Remote
Control
Mode
When set for a control point it means that the commands are issued from an
upper level and are not allowed from this point.
Remote
HMI
Remote HMI is a client of the substation HMI server. The client may provide all
or part of functions handled by the substation HMI.
RI
Read Inhibit
This output indicates the availability of an analogue output (e.g. during DAC
converting time)
RJ-45
Registered Jack-45
A 8-pin female connector for 10/100 Base-T Ethernet network
RMS
RRC
Rapid ReClosure
RSE
RSVC
RS-232
RS-422
A standard for serial interfaces that extends distances and speeds beyond RS232. Is intended for use in multipoint lines.
RS-485
Lexicon
C264/EN LX/C80
Page 11/14
RSVC
RTC
RTU
SAT
SBMC
SBO
S-BUS
SCADA
SCD
SCE
SCL
SCP
SCS
SCSM
SCT
Single Counter
SER
Server
Setpoints Analogue setpoints are analogue outputs delivered as current loops. Analogue
(analogue) setpoints are used to send instruction values to the process or auxiliary device
Setpoints
(digital)
Digital values sent on multiple parallel wired outputs Each wired output
represent a bit of the value. Digital setpoints are used to send instruction
values to the electrical process or to auxiliary devices.
SFC
SI
System Indication
Binary information that do not come from external interface. It is related to an
internal state of the computer (time status, hardware faults). It is the result of
all inner function (AR, ), PSL, or ISaGRAF automation.
SICU 4
SIG
C264/EN LX/C80
Lexicon
Page 12/14
SINAD
SIT
SNTP
SOE
Sequence Of Events
Other term for the event list.
SP
SPS
SPC
Single Point
Single Point Status
Single Point Control
ST
Structured Text
An IEC1131-3 programming languages to define configurable automation
STP
Switch Redundant
Computer C264 board Ethernet switch with redundant Ethernet
SWU
T101
T103
T104
TC
True Contact
TCIP
TCU
TDD
Total Demand Distorsion, similar to the THD but applied to currents and with a
rated current (In) as reference
TG
Telecontrol Gateway
THD
TI
Tele Interface
TM
Analogue Measurement
TMU
TS
Logic position
Lexicon
C264/EN LX/C80
Page 13/14
TVU
UCA
UPI
UTC
VdBS
Versioned data Base System, databag generated by SCE & ready to download
VDEW
VMGA
Voltage
level
Set of bays whose plants & devices are dealing with same voltage (e.g. 275kV)
VT
Voltage Transformer
Basically the electric device connected to process and extracting a voltage
measurement. By extension part of a device (C264) that receives this AC value
and convert it to numerical measurement value. VT are wired in parallel.
WTS
WYE
C264/EN LX/C80
Lexicon
Page 14/14
BLANK PAGE
http://www.schneider-electric.com/CCC
Schneider Electric
35 rue Joseph Monier
92506 Rueil-Malmaison
FRANCE
Phone:
Fax:
+33 (0) 1 41 29 70 00
+33 (0) 1 41 29 71 00
www.schneider-electric.com
Publication: C264/EN O/C80