Escolar Documentos
Profissional Documentos
Cultura Documentos
MiCOM C264-R
FUNCTIONAL DESCRIPTION
Functional Description C264R/EN FT/C11
CONTENT
4. COMMUNICATIONS 15
4.1 Telecontrol bus 15
4.2 Legacy bus 16
6. DATA PROCESSING 25
6.1 Binary Input Processing 25
6.1.1 Binary Input Definition 25
6.1.2 Processing of Single Point Status 25
6.1.3 Processing of Double Point Status 26
6.1.4 Group processing 27
6.1.5 SBMC Mode Processing 27
6.2 Measurement Input Processing 27
6.2.1 Analogue processing 27
6.2.2 Digital Measurement Processing 28
6.3 Accumulator Input Processing 28
7. CONTROL SEQUENCES 29
7.1 Kind of control sequences 29
7.2 Control sequences checks 29
7.2.1 Mode Management 29
7.2.2 IED connected 29
7.2.3 Control mode 30
7.2.4 Uniqueness of control 30
7.2.5 Inter-control delay 30
7.2.6 Status of the device 30
8. USER INTERFACE 31
8.1 Front Panel 31
8.1.1 Local Control Display 32
8.1.2 Local/Remote push-button 32
8.2 Computer Maintenance Tool 32
Functional Description C264R/EN FT/C11
8.3 Printer 33
8.3.1 Inputs 33
8.3.2 Outputs 33
8.3.3 Printer management 34
9. RECORDS 36
9.1 Permanent records storage 36
9.1.1 Data storage 36
9.1.2 Waveform Recording 36
9.1.3 Events 37
10. AUTOMATIONS 38
10.1 Load Shedding 38
10.1.1 Inputs 38
10.1.2 Algorithm 39
10.1.3 Outputs 40
10.1.4 Hypothesis & Constraints 41
10.1.5 Configurable data 42
10.2 Load Curtailment 42
10.2.1 Inputs 43
10.2.2 Algorithm 43
10.2.3 Outputs 44
10.2.4 Hypothesis & Constraints 45
10.2.5 Configurable data 45
C264R/EN FT/C11 Functional Description
BLANK PAGE
Functional Description C264R/EN FT/C11
• Direct Process interface through DIs, DOs and AIs, A0s boards
• RTC (Real Time Clock), time management; synchronisation, time tagging (see Time
management chapter)
SCADA link
T101 or T104
Secondary Rack
I/O
C264 Acquisition
IED Link
C0238ENa
− receive all information acquired on secondary rack and update the archives (SOE
waveform)
− Transmission via the SCADA interface of all information acquired on secondary rack.
− Manage the database downloading. Reception through the SCADA link and
distribution of the new configuration on all other racks.
− Manage the control received through the active SCADA link, dispatch it on the racks.
− Manage the digital input and measurement acquisition. (Not available in case of main
racks redundancy)
− Manage the control, which is directly handled by the main rack. (Not available in case
of main racks redundancy)
− Manage the IED communication, and real time data acquisition. (Not available in case
of main racks redundancy)
The functions done by the secondary racks are:
1.1.2 Multi-rack application with a redundant Main Rack (Master and Backup)
SCADA link
T101 or T104 SCADA link
T101 or T104
Secondary Rack
I/O
C264 Acquisition
IED Link
Secondary Rack
I/O
C264 Acquisition
IED Link
C0239ENa
− receive all information acquired on secondary rack and update the archives (SOE
waveform)
− Transmission via the SCADA interface of all information acquired on secondary rack.
− Manage the database downloading. Reception through the SCADA link and
distribution of the new configuration on all other racks (including the main rack
backup)
− Receive all information acquired on the secondary rack and update the archives (SOE
waveform)
− Freeze all transmission on the SCADA link (Reset of the Link: Function 0)
− Become the master main rack in case of SCADA General Interrogation (GI Request)
received on its line.
− Receive and update the configuration database received by the master main rack
through the active SCADA link
− To communicate to the SCADA the status of main racks (master and backup) the
watchdog relays could be wired to standard DI of one secondary rack.
C264R/EN FT/C11 Functional Description
• Open Circuit (AI kind 4-20 mA with current value under 4mA)
3.1.1 Definitions
The terms defined below are used in this whole section 3.
• Anomaly: an anomaly is a fault causing a downgraded behaviour of the computer.
There are hardware and/or software anomalies:
− Board failure
− Loss of synchronisation
− Loss of communication
• Software fault : A software fault results of a major software error. In this case the
computers enters the Faulty mode.
• Vital harware fault: a vital hardware fault is a fault causing a software halt. This kind
of fault causes the computer to stop the application software.
− CPU fault
− Bus fault
− Display (LCD, LED’s): the single test that can be done is the presence of the HMI
board.
− Peripheral devices (printer, external clock ..). Check of the presence of the
devices by use of timeouts.
If any of these non-vital hardware tests fails the computer enters the
operational/downgraded mode depending on the type of the fault.
C264R/EN FT/C11 Functional Description
Major
automatic hardware
reset fault Init OK manual reset
hardware test OK
and coherency not OK
FAULTY
no DB
major hardware fault major hardware fault
or software fault or software fault
vital
hardware vital hardware
fault vital hardware fault fault
vital hardware fault
HALT
Counter of faults = Max_Fault
C0288ENa
They have a single address on one of the two SCADA links. This allows handling two
different networks.
The master rack is eligible on the following conditions:
− The communication has been set-up on its link. The message used to confirm the set-
up of the link is the GI request (ASDU 100).
The previous rules could be presented on the automation schema below:
MR1
MR1
BACKUP MASTER
GI received on MR1
MR2
MR2
BACKUP BACKUP
MR1
BACKUP
GI received on MR2
MR2
MASTER
RUNNING
MR1 : Main Rack 1 STATE 2
MR2 : Main Rack 2 C0250ENa
SCADA link
T101 or T104 SCADA link
T101 or T104
Internal DB
Secondary Rack
I/O
C264 Acquisition
Secondary Rack
I/O
C264 Acquisition
IED Link
C0252ENa
• IRIG-B signal
• Clock message from a SCADA gateway (T-Bus)
When computer is synchronised all events and measurement have a time tag with
synchronised attribute. If synchronisation is lost, or has never been received attributes
indicates that time tag is not synchronised.
The time management organisation is based on the following principe:
• only the main racks can be synchronised from IRIG-B or from SCADA.
• the secondary racks can be synchronised by the both main racks according to the
following priority level:
− 1: IRIG-B
− 2: Master Rack
− 3: Backup Rack
3.4.1 External clock
The external clock device receives the synchronisation signal through several possible
protocols (GPS, DCF77, etc…) and then sent to the MiCOM C264/C264C using IRIG-B
standard. A specific input is dedicated for this application.
3.4.2 Clock message from a SCADA gateway
SCADA clock synchronisation depends on protocol. The synchronisation message is directly
acquires by the MiCOM C264/C264C through the SCADA link.
3.4.3 Time set by an operator
The user may set time and date directly using the MiCOM C264/C264C local Operator
Interface or the CMT tool.
Functional Description C264R/EN FT/C11
4. COMMUNICATIONS
MiCOM C264/ C264C ensure up to three different type of communications:
T-BUS S-BUS
Telecontrol
Interface UCA2
Computer Kernel
L-Bus
IED
C0005ENb
FIGURE 3 : COMMUNICATIONS
4.1 Telecontrol bus
The available slave protocols are:
• ModBus
Devices connected to: IEDs
Physical layer:
• Optical fibre
Up to four serial ports are available to make four networks with different protocols or not.
For T103 and Modbus, a tunnelling mode is available. This allows a setting software running
on a personal computer to access the IEDs through the C264.
WARNING : - WHEN USING THE CPU BOARD’S SERIAL PORTS, THE BAUDRATE
MUST BE THE SAME ON BOTH OF THE CPU SERIAL PORTS (COM3 AND COM4).
- THERE IS NO LEGACY BUS ON THE MAIN RACK WHEN IT IS
REDUNDANT.
- THE LEGACY BUSES ARE NOT REDUNDED.
Functional Description C264R/EN FT/C11
C0126ENa
Filtering time
Debouncing
time
t0 t1 t2
C0127ENa
t0 is the instant of detection of the first transition. t1 is the instant of validation of the change of
state. t2 is the end of the filtering. (the signal has remained stable from t1 to t2). The change of
state is time stamped at t0 .
A value of 0 means that no filter is applied : a change of state is validated as soon as it is
detected.
Three couple of delays (deboucing / filtering) are defined :
5.1.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).
5.2 Counters acquisition (CT)
The counters are acquired on the same boards as the DIs. There are two types of counters
SCT (Single counter) and DCT (Double counters).
This interface allows acquisitions of pulses delivered from energy metering devices
corresponding to a calibrated quantity of energy.
Each valid pulse increments the value of an accumulator used to compute the quantity of
energy delivered during a given period.
Counter values are stored in static memory (secured with a capacitor, > 48h autonomy) ; The
counters are kept for more than 48H when the C264 power supply is off.
The pulse frequency should be 20 Hz as a maximum. So, the debouncing and filtering
values must be chosen in consequence.
5.2.1 Single counter (SCT)
A SCT is acquired on a single contact.
The value of the accumulator is incremented after a low to high transition, confirmed after a
filtering time (Tcount). Tcount is defined for the whole system, with a step of 5 ms : the chosen
value must be coherent with the pulse frequency (i.e. all counters of a system use the same
Tcount).
A subsequent pulse can be taken into account only after a high to low transition.
Tcount Tcount
Transition validated,
Low to high transition
counter is incremented
Transition discarded
Low to high transition
C0128ENa
Functional Description C264R/EN FT/C11
CC
Tstab
Tstab
Bit change => new Bit change => Bit change =>
calculation new calculation new calculation
∆≤V stab=> confirmed ∆>V stab => Tstab ∆>V stab => Tstab
DM value launched re-launched
Furthermore, an invalidity processing is applied : at the first change of state of one bit
following a confirmed DM value, the TInv delay is launched (value defined in configuration,
from 0 to 300s, with a 10 ms step). If the value is not confirmed at the end of this delay, the
DM is declared UNDEFINED.
TInv
Confirmed
DM value DM UNDEFINED
Tstab
Tstab
Tstab
If Vstab is equal to 0, there is no stability processing : all DM values are sent at each
calculation.
Functional Description C264R/EN FT/C11
Tinh Tinh
RI
One supplementary bit can be used for the sign (0 indicates a positive value, 1 indicates a
negative value).
Capability extension for the Tap Position Indication only :
• DOU200 boards for alarms (8 normal open DOs + 2 normal open/normal close DOs).
5.6 Digital Setpoints
Digital setpoints are digital values sent on multiple parallel wired outputs. Each wired output
represents a bit of the value. Digital setpoints are used to send instruction values to the
process or to auxiliary devices.
The Digital Setpoints are processed on the same boards as the Digital Outputs. The Digital
Outputs characteristics described above apply on Digital Setpoints. Nevertheless, only
standard DO boards with single pole N/O relays can be used.
5.6.1 Encoding
The following codes are allowed:
Moreover a supplementary bit can be used for the sign (0 indicates a positive value, 1
indicates a negative value).
Functional Description C264R/EN FT/C11
• Wait for N ms
• Wait for N ms
± 5 mA, 0 - 5 mA,
± 10 mA, 0 - 10 mA,
4 - 20 mA, 0 - 20 mA, ± 20 mA
5.7.2 Output management
Each current output is individually managed in 2 modes:
• 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 setpoint 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.
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.
C264R/EN FT/C11 Functional Description
Analog
Output
100 ms
10ms 10ms
Set
RI relay
status Reset
C0289ENa
• the C264 is not operational or powered off (no communication with the CPU board)
6. DATA PROCESSING
MiCOM C264/C264C treatment entries can be Binary Inputs or Analogue Inputs. They are
issues from
• IOs boards,
• System Input (SI): information related to the system, to configurable and built-in
automations or to electrical process but without acquisition possibilities
DI/DO
association
Group
processing
From Toggle
acquisition filtering Manual
suppression Persistance
filtering Transmission
From IED Substitution Data Logging
IED
Archiving
inputs
Forcing
System
Inputs
C0290ENa
A preliminary treatment (filtering) is applied to specific Single Points (SP) in order to confirm
the state.
The choice of these SPs and the filtering time are fixed by the MiCOM C264/C264C
configuration. If the opposite transition occurs before this delay, both transitions are
discarded.
This treatment is said to be a persistent filtering.
States (Report)
RESET 01
SET 10
TOGGLING 11
SELFCHECK FAULTY 11
UNKNOWN 11
Close DI/DO
association
contact
From Toggle
acquisition filtering Group
processing
Open
Manual
contact Toggle suppression Motion
From filtering
filtering
acquisition Persistance
Substitution filtering
Transmission
From IED Forcing Data Logging
IED
inputs Archiving
System
Inputs
C0291ENa
DPS are commonly used for all switchgears position. From board valid acquisition the two
contacts are Close and Open (set by configuration when voltage is present). The position of
the switch is:
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 said to be a motion filtering.
• valid state (OPEN or CLOSE) is stamped with the time of the beginning of the
MOTION state
Functional Description C264R/EN FT/C11
States (report)
JAMMED 11
MOTION 00
OPEN 10
CLOSE 01
UNDEFINED 11
TOGGLING 11
SELFCHECK FAULTY 11
UNKNOWN 11
From IED
acquisition
Manual
suppression
From analogue Open Circuit Thresholds
Scaling Substitution
acquisition Management detection
Forcing
From digital
acquisition
Transmission
Data Logging
Archiving
C0292ENa
C264R/EN FT/C11 Functional Description
The Measurement resulting states, following the various filters, which can be applied, are:
States Meaning
VALID
SELFCHECK FAULTY AI, DI board fault
UNKNOWN MV is acquired via a transmission link, and the link is
disconnected
SATURATED MV is beyond its nominal input range
UNDEFINED MV is Digital Measurement with invalid coding or computation
on analogue leads to error
OPEN CIRCUIT MV is DC 4-20 mA with input value under 4mA
• For read inhibit: in this case, the DM is acquired when the read inhibit bit is set.
7. CONTROL SEQUENCES
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 send
control (protocol or DO), and check correct execution with feed back from protocol or from
DI.
7.1 Kind of control sequences
The control sequences automation receives three kind of input triggers (as order from higher
level) with selection, execution and unselection. Control order may have a normal or
abnormal termination with positive or negative acknowledgement to operator and to
communication.
By configuration, at PACiS SCE level a control sequence may be executed in one of the
following mode:
• SBO many: Selection, several Execution, until Unselection (for transformers only)
By configuration, each DPC order (close order or open order) and each SPC can activate
simultaneously two DO contacts.
7.2 Control sequences checks
Receiving control, the control sequence execute configured checks:
Operational conditions
− IED connected
− SBMC mode
Module conditions
− Delays upon selection feed back, start moving, final position reached
7.2.1 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.
7.2.2 IED connected
If a control has to be send to an IED, it is only accepted if this IED is connected to the
computer.
C264R/EN FT/C11 Functional Description
8. USER INTERFACE
MiCOM C264/C264C provides three user interfaces:
• The Printer
8.1 Front Panel
The MiCOM C264/C264C front panel exists in two versions:
• A simple FP with LEDs, L/R push-button and the serial link (GHU210 or GHU211)
• A graphical FP with LEDs, L/R push-button, the Local Control Display and the serial
link (GHU200 or GHU201)
LEDs
Key-pad
Local/Remote
Graphical push-button
LCD
C0020ENc
• Select information
• Local
• Remote
When a control depends on bay mode, it is accepted from front panel when the bay is in
Local mode and from other control points when the bay is in Remote Mode.
Front serial Link
The Front panel RS232 serial link is located under the lower flap.
This serial link is dedicated for maintenance purpose to connect a PC with the MiCOM
C264/C264C maintenance software tools:
• HyperTerminal
• Access to C264 databases versions and descriptions and facility to download and
switch new database
8.3 Printer
The events (the events to log are declared in the database) can be printed and
chronologically sorted on logbook printer. They are printed with their time stamping and a
complete description (location and event description).
One logbook printer can be connected to a computer. Some printout format parameters can
be defined by user during the system configuration phase.
8.3.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 :
• Measurement
• Operator action
• Devices control
8.3.2 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
TimeStamp – 24 or 26 characters
Origin - 67 characters : for BI, TPI, measures, controls, the origin gives the access path to
the object
ObjectName - 16 characters
ObjectMessage - 16 characters
The Origin, ObjectName and ObjectMessage properties contain different information
depending of the associated event type.
C264R/EN FT/C11 Functional Description
<Log Book>
<blank line>
Page Number
C0141ENa
latency
9. RECORDS
Several kinds of records are stored into MiCOM C264.
9.1 Permanent records storage
They are stored on flash disk.
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 Waveform Recording
MiCOM C264/C264C provides
• Digital inputs
• Digital outputs
The slow wave form manages up to 24 analogue and 48 digital values.
MiCOM C264 stores at maximum 5000 integrated values as follow:
• Operator request
9.1.3 Events
All data change or events declared in MiCOM C264/C264C 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 CMT equipment. They also can be printed.
Events , following MiCOM C264/C264C configuration, may typically contain the MiCOM
C264/C264C 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 MiCOM C264/C264C under the following circumstances may create events:
10. AUTOMATIONS
10.1 Load Shedding
LS On/Off Status
LS On/Off control
LS Group x status
Blocking condition x GROUP 1 GROUP 2 GROUP 3 GROUP 4 LS CB x rejected by
setting blocking condition
blocking condition LS CB x completed
information LS CB x failed
CBx status List x Status
Inter-group delay Blocking condition
x status
CBx control LOAD SHEDDING CBx open control
time-out
C0293ENa
Database (.adb)
10.1.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) which allows to set On or Off the Load
Shedding automation. This control can be received from the SCADA interface or from
the C264-R local HMI
• Blocking condition x setting (1•x•6) : 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 information : digital inputs which 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)
• Inter-group delay : delay between each group when several group are activated (i.e.
when CB of a group have to be tripped). This delay is defined in configuration and
settable through a setpoint (ASDU 48) which can be only received from the SCADA
interface. The delay is stored in non-volatile memory, but set to the value defined in
configuration in case of database switch.
• CBx control time-out : one time-out per circuit breaker. For a circuit breaker, this time-
out defines the authorized delay between the CB control activation and the CB
position change. These time-out are defined in configuration – thru SCT – as the CB
control’s Feedback time-out.
10.1.2 Algorithm
Group definition
At configuration time (with SCT), 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 which can be used
in 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 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.
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 / / 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
setpoint 1
Breaker Number / / 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
setpoint 2
Breaker Number / / / / / / / 40 39 38 37 36 35 34 33 32 31
setpoint 3
Bit 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
Value 16384 8192 4096 2048 1024 512 256 128 64 32 16 8 4 2 1
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 up to 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 up to 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 (interlocking,
control uniqueness, bad CB state (already open, jammed, …), …)
Note : time constraints are given from fx< transition detection to Digital
Output closure.
Any invalid state of the fx< SPS (Selfcheck faulty, toggling) will be not taken into account to
trig the automation.
In case of simultaneous fx< detection - i.e. 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 case of multiple fx< detection – i.e. 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.
10.1.3 Outputs
• LS Group x status (SPS permanent type, 1•x•4) : set as soon as a group is activated
(i.e. 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, 1•x•40) : 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, 1•x•40) : 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 (1•x•6) : list of CBs for which the blocking condition is set,
transmitted to the SCADA through an analogue value (ASDU 09 or 10)
• Only one frequency relay will provide frequency thresholds to the C264-R
• All DOU or CCU board used for CB controls must be in the same rack
• All configurable information used for Load Shedding function are configured using the
SCT
− LS function can be set On or Off from the SCADA interface. The SCADA sends
this order to only one Main Rack. The order must be automatically transmitted to
other Main Racks.
− All settings defined on a Main rack are also automatically transmitted to other
Main Racks.
[settings = Inter-group delay; List of Circuit Breaker attached to each group; List of
Circuit Breaker blocked by each blocking condition]
− In case of a group activation (fx< goes in Set state), the LS automation is run in
parallel on all Main Racks.
− The LS On/Off state is saved in non volatile memory. This information 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.
C264R/EN FT/C11 Functional Description
Furthermore, all datapoints described above are configured using the SCT and must be
provided by the S9R file.
10.2 Load Curtailment
LC On/Off Status
LC On/Off control
LC Group x status
Blocking condition x GROUP 1 GROUP 2 GROUP 3 GROUP 4 LC CB x rejected by
setting blocking condition
blocking condition LC CB x completed
information LC CB x failed
List x Status
CBx status
Blocking condition
x status
CBx control LOAD CURTAILMENT CBx open control
time-out
C0294ENa
Database (.adb)
Functional Description C264R/EN FT/C11
10.2.1 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, which allows 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) which allows to set On or Off the Load
Curtailment automation. This control can be received from the SCADA interface or
from the C264-R local HMI
• Blocking condition information : digital inputs which 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)
• CBx control time-out : one time-out per circuit breaker. For a circuit breaker, this time-
out defines the authorized delay between the CB control activation and the CB
position change. These time-out are defined in configuration – thru SCT – as the CB
control’s Feedback time-out.
Breaker Number / / 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
setpoint 1
Breaker Number / / / / / / / / / / / / 20 19 18 17 16
setpoint 2
Bit 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
Value 16384 8192 4096 2048 1024 512 256 128 64 32 16 8 4 2 1
The group definition is saved in non-volatile memory and restored after a computer reboot. It
is erased in case of database switch.
Locally to the computer, assignments of CB to a group can be performed only through a
database download.
Blocking conditions
Up to 6 SPS / DPS can be defined as blocking condition : they are numbered from 1 to 6.
At configuration time (with SCT), 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 performed through the SCADA interface, whatever was the
status of the automation (On or Off). Two 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 non-volatile memory and restored after a
computer reboot. It is erased in case of database switch.
After assignment, the Blocking condition x status information for blocking condition(s) which
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.
When the SET control is received through the Gx Activation SPC (i.e. reception by the
computer of the order), all the CB belonging to the group x must be tripped in less than
300 ms.
Notes : - A blocking condition on a CB prevents its trip
- No other information than the blocking condition can prevent the CB
trip (interlocking, control uniqueness, bad CB state (already open,
jammed, …), ….)
In case 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 case, the time to trip the CB of the other(s) group(s) can be
more then 300ms.
10.2.3 Outputs
• LC Group x status (SPS permanent type, 1•x•4) : set as soon as a group is activated
(i.e. 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, 1•x•20) : 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, 1•x•20) : 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 (1•x•6) : 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 SCT
Furthermore, all datapoints described above are configured using the SCT and must be
provided by the S9R file.
C264R/EN FT/C11 Functional Description
BLANK PAGE