Professional Documents
Culture Documents
Application Guide: Implementation of Mx3Eg1A (Auto Synchronizer) in P40 Agile
Application Guide: Implementation of Mx3Eg1A (Auto Synchronizer) in P40 Agile
Application Guide
Page 1 of 30
Application Guide – Implementation of MX3EG1A (Auto-Synchronizer) in P40 Agile Issue - A
Record of Revision:
Page 2 of 30
Application Guide – Implementation of MX3EG1A (Auto-Synchronizer) in P40 Agile Issue - A
Purpose:
This document describes the context for the implementation of Auto Synchronizer
(MX3EG) in P40 Agile.
Software Used:
IED Description:
Page 3 of 30
Application Guide – Implementation of MX3EG1A (Auto-Synchronizer) in P40 Agile Issue - A
Introduction:
When a Circuit Breaker is to be closed, it is imperative to ensure that the all the
parameters of the voltages on either sides of the CB are in synchronism. Closing
CB without ensuring required synchronism level may result in system
disturbances, Shock to generators and sometimes, a serious damage to other
electrical equipments including generator.
The three factors, also called synchronizing variable, that are to be monitored to
achieve synchronism are:
• Difference between Magnitude of the Voltages (∆V)
• Difference between Frequency of the Voltages (∆F)
• Phase angle Difference between the voltages(∆Φ)
Ideally, the above three factors should be zero. But, considering practical system
limitation, a small difference is allowed. Thus, the above three factors shall be in
defined range to achieve the synchronism.
Methods of Synchronization:
Page 4 of 30
Application Guide – Implementation of MX3EG1A (Auto-Synchronizer) in P40 Agile Issue - A
hence the frequency) of the generator so that the synchronizing variables
are within limit. As soon as the synchronization is established, CB is closed.
In the conventional Mx3EG scheme, both the voltages are supplied to the relay as
shown below.
CB (52) Status, start & Stop “Auto-Synch” pulse and Close on “Dead Bus” signals
are wired to the relay as shown below:
Page 5 of 30
Application Guide – Implementation of MX3EG1A (Auto-Synchronizer) in P40 Agile Issue - A
Operating Modes:
When the relay receives a “START LB” pulse, it starts monitoring the
synchronization variables and generates outputs according to the delta limits
(∆Φ, ∆V, ∆F) set in the relay.
To control the frequency, the speed of the governor is adjusted using output
contacts of the relay as shown below:
E.g. when frequency is low, contact K119 & K113 are closed and the governor
starts increasing the speed which in turn increases the frequency. As soon as the
frequency comes within the defined limit, the contacts are opened (OR No more
controlling pulse is generated – depending upon the output configuration.)
To control the voltage, the voltage regulator is adjusted using output contacts of
the relay:
E.g. when voltage is low, contact K129 & K143 are closed and the Voltage
Regulator starts increasing the voltage. As soon as the voltage comes within the
defined limit, the contacts are opened (OR No more controlling pulse is
generated – depending upon the output configuration.)
The scheme has an option to allow closing of the CB when the bus voltages is not
available, known as dead-bus closing.
Page 6 of 30
Application Guide – Implementation of MX3EG1A (Auto-Synchronizer) in P40 Agile Issue - A
When the relay receives “START-DB” pulse, it starts monitoring the input Voltage
& Frequency, if the voltage & frequency are within specified limit; a CB Closing
pulse is issued.
The relay has the following two modes for output contacts configuration:
1. Continuous Mode:
In this mode, the controlling output contacts are continuously “CLOSED” until
the respective signal reaches the predefined limit.
E.g. In the above example of frequency control, the contacts “K119 & K113”
will remain close until the frequency reaches within the limit.
In this mode, two timers are used – Pulse Timer and Pause Timer. The
controlling output contacts are closed for the time of “Pulse Timer” only. Once
this timer elapses, the contact is opened.
Before generating next pulse, there is a wait time which is defined by the
“Pause Timer” i.e. next pulse is generated only when this timer has been
elapsed and the desired variable is still out of limit.
Predictive Closing:
The relay can take care of CB Closing delay time while generating CB close
command so that required synchronism is ensured at the time of closing.
The relay has an option to choose “between 1 to 10” as the number of CB closing
attempts.
Page 7 of 30
Application Guide – Implementation of MX3EG1A (Auto-Synchronizer) in P40 Agile Issue - A
Implementation of Auto-Synchronizer in P40 Agile:
Note:
All the Pictures, I/O, CT-VT signals, DDB’s etc. shown below pertain to the
particular relay model mentioned in the IED description.
Page 8 of 30
Application Guide – Implementation of MX3EG1A (Auto-Synchronizer) in P40 Agile Issue - A
Measuring the Voltage Inputs:
Both the voltage Inputs are wired to the relay at the respective terminals.
We are using Function Key-1 & Function Key-2 to Start & Stop the “Auto-
Synch” Sequence respectively.
Page 9 of 30
Application Guide – Implementation of MX3EG1A (Auto-Synchronizer) in P40 Agile Issue - A
LED mappings:
• Function Key LED-2 RED signal shows that CB has failed to close in
response to an “Auto-Synch CB Close” command OR “Dead-Bus” closing
command OR “Manual Closing” command OR “Remote Closing”
command. Function Key LED-2 yellow signal shows that Auto-Synch
function has failed to achieve Auto-Synchronism conditions within the
specified time.
• Function Key LED-3 GREEN signal shows that a “Dead Bus-Live Line” CB
Closing is initiated.
Page 10 of 30
Application Guide – Implementation of MX3EG1A (Auto-Synchronizer) in P40 Agile Issue - A
A consolidated list of signals used in the implementation is shown below for easy
reference:
Remarks
Opto-Input
Input-1 CB AUX 3Ph 52-A
CB Status
Input-2 CB AUX 3Ph 52-B
FnKey
FnKey-1 Start Auto-Sync Basic “Start-Stop”
FnKey-2 Stop Auto-Sync Inputs
FnKey-3 Start “Dead Bus – Live Line” Closing
LED
FnKey-1RED Auto-Sync Running Default - Green
FnKey-1GREEN Auto-Sync NOT running
FnKey-2RED CB Closing Failed
FnKey-2 Yellow Auto-Sync Failed to achieve Sync condition
FnKey-3 Green Dead Bus – Live Line closing initiated
LED-1 RED Synch 1 NOT OK – CS1 NOT OK
LED-1 GREEN Synch 1 OK – CS1 OK
LED-2 GREEN Dead Bus-Live Line
LED-3 RED Increase Voltage output command
LED-4 RED Decrease Voltage output command
LED-5 RED Increase Frequency output command
LED-6 RED Decrease Frequency output command
LED-7 GREEN Synch 2 OK – CS2 OK
LED-8 RED Auto Sync CB Close Command
Output Relay
RL-5 Increase Voltage output command Pulse-Pause Mode
RL-9 Decrease Voltage output command Pulse-Pause Mode
RL-11 Increase Frequency output command Continuous Mode
RL-10 Decrease Frequency output command Pulse-Pause Mode
RL-12 Auto-Sync CB Close Command
Control Input
Control Input 1 Load Pulse ON/OFF Latched
Page 11 of 30
Application Guide – Implementation of MX3EG1A (Auto-Synchronizer) in P40 Agile Issue - A
Calculating Voltage & Frequency difference:
The relay has the following in-built DDB’s to show voltage difference-
This DDB is “SET” when Line Voltage is lesser than Bus Voltage.
This DDB is “SET” when Line Voltage is greater than the Bus Voltage.
The relay has the following in-built DDB’s to show frequency difference –
This DDB is “SET” when Line Frequency is lesser than Bus Frequency.
This DDB is “SET” when Line Frequency is greater than Bus Frequency.
Page 12 of 30
Application Guide – Implementation of MX3EG1A (Auto-Synchronizer) in P40 Agile Issue - A
Controlling the Voltage & Frequency difference:
As we have the above four DDB’s, the respective output commands (Relay
outputs) can be generated by using a simple PSL. However, while issuing the
controlling commands to control the “Voltage Regulator” and/or “Governor”, we
need to take care of the following points:
• The controlling process shall START only after the “Auto-Sync” START
command is initiated, AND the CB status is “OPEN”, AND “Check Sync
CS1” is NOT OK, AND both the voltages are within set limits for
synchronization i.e. neither under voltage nor over voltage*$.
• The controlling process shall END if the operator has initiated an “Auto-
Sync” STOP command OR the “Auto-Sync” Timer# has expired OR the
signal has reached the specified range.
* Under voltage and over voltage limits for synchronization are set under the
“Group1 System Checks” settings of the relay as shown below.
The “Check Sync 1 OK” signal is “SET” or “RESET” as per the delta limits set in
the “System Checks” settings. This is worth noticing that this is applicable only in
the case of Live Bus-Live Line.
Page 13 of 30
Application Guide – Implementation of MX3EG1A (Auto-Synchronizer) in P40 Agile Issue - A
The PSL shown below shows the basic “Start” and “Stop” conditions for the
“Auto-Sync” sequence.
As shown in the PSL above, the output “Condition 1” is “HIGH” until the “60
seconds-pulse timer” expires AND other conditions are also satisfied. As soon as
F2 is pressed, the output of “S-RD” Latch becomes “HIGH” which in turn stops
the logic. Also, once an “Auto-Sync CB-Close” output is generated, the logic is
stopped after 20 msec of this. This 20 msec time is required to provide enough
time to generate the output for CB Close.
“Check-Sync 1 – CS1” parameters are used for the controlling of voltage &
frequency.
Page 14 of 30
Application Guide – Implementation of MX3EG1A (Auto-Synchronizer) in P40 Agile Issue - A
Now, to initiate the voltage & frequency controlling, the “Condition 1” shall be
“HIGH” as shown below.
Page 15 of 30
Application Guide – Implementation of MX3EG1A (Auto-Synchronizer) in P40 Agile Issue - A
Output Contacts Configuration:
Similar to “MX3EG”, this output can be used to control the output relays in two
modes:
1. Continuous Mode:
Page 16 of 30
Application Guide – Implementation of MX3EG1A (Auto-Synchronizer) in P40 Agile Issue - A
Closing the Circuit Breaker:
Page 17 of 30
Application Guide – Implementation of MX3EG1A (Auto-Synchronizer) in P40 Agile Issue - A
Note:
1. In order to take care of “CB closing delay” while issuing a close command,
“Check Sync 2 – CS2” is used for only CS2 has the option of “Predictive
Closing”. To use the predictive closing, “Cs2 slip control” shall be set as
“Freq + CB comp”. “CB closing delay” is defined in the settings of the relay
as “CB close Time”.
Also, it is to be ensured that both CS1 & CS2 are enabled in the setting and
have the same configuration parameters.
Page 18 of 30
Application Guide – Implementation of MX3EG1A (Auto-Synchronizer) in P40 Agile Issue - A
Provision of Load Pulse Configuration:
Page 19 of 30
Application Guide – Implementation of MX3EG1A (Auto-Synchronizer) in P40 Agile Issue - A
Generating “CB CLS FAIL” for “Auto-Sync CB Closing”:
To generate an alarm, the generated CB Cls Fail signal is linked to “MR User
Alarm 18”. The text of this alarm can be edited to “Auto CB Cls Fail” using the
“Menu Text Editor” of the IED.
Page 20 of 30
Application Guide – Implementation of MX3EG1A (Auto-Synchronizer) in P40 Agile Issue - A
Generating “Auto-Sync Controlling Failed” Alarm:
The status of “CS1 Ok” is checked after the expiration of “Auto-Sync” Timer, if
the process has failed to achieve “CS1 OK” condition within the time, a failure
alarm has to be generated.
The failure condition is also linked to “MR User Alarm 19”. The text of this alarm
can be edited to “Auto Sync Controlling Failed” using the “Menu Text Editor” of
the IED.
It is to be noted that the failure condition shall not be alarmed if the used has
manually stopped the “Auto-Sync” sequence.
Page 21 of 30
Application Guide – Implementation of MX3EG1A (Auto-Synchronizer) in P40 Agile Issue - A
Live Line - Dead Bus Closing:
To use this feature, the user has to manually start the “Dead Bus” Closing
sequence by pressing Function Key-3.
When the “Dead Bus” closing is initiated, the relay check if the voltage &
frequency are within specified limit, If it is so and CB is open, a CB close
command is initiated.
Note:
Page 22 of 30
Application Guide – Implementation of MX3EG1A (Auto-Synchronizer) in P40 Agile Issue - A
3. To check whether the voltage is within limit, we are using “Volt protection”
DDB’s. To use these DDB’s, voltage protection must be enabled in the relay.
Also, the protection stages used here shall be removed from default Tripping
PSL.
Page 23 of 30
Application Guide – Implementation of MX3EG1A (Auto-Synchronizer) in P40 Agile Issue - A
Management of Function Key-1 LED:
Function Key-1 LED shows the status of “Auto-Sync”. As long as the “Auto-Sync”
is running, the RED LED shall glow.
As soon as the “Auto-Sync timer” expires OR “Auto-Sync” is stopped manually
OR first CB Close command has been generated, the GREEN LED shall glow.
Page 24 of 30
Application Guide – Implementation of MX3EG1A (Auto-Synchronizer) in P40 Agile Issue - A
Known Limitations of current Implementation:
6. Dependency on PSL:
It is not possible to change the timer values/output pulse time through the
local HMI of the relay. Generally, these values are changed frequently during
actual operation; complete dependency on PSL makes it a cumbersome task.
Page 25 of 30
Application Guide – Implementation of MX3EG1A (Auto-Synchronizer) in P40 Agile Issue - A
Also, need of a laptop/PC is inevitable.
7. Accuracy of Timers:
Since the implementation is largely based on PSL timers, the accuracy of
timers has a huge impact on the performance of the functionality.
Page 26 of 30
Application Guide – Implementation of MX3EG1A (Auto-Synchronizer) in P40 Agile Issue - A
Annexure – A
Simulation using Omicron’s State sequencer:
1. First, the IED generates two output commands – One is to Increase voltage
and the other is to decrease frequency.
(Now, in the next state, the voltage comes within specified range but the
frequency is still out of range.)
Page 27 of 30
Application Guide – Implementation of MX3EG1A (Auto-Synchronizer) in P40 Agile Issue - A
2. The IED generates “Decrease Frequency” output one more time.
(Now, both voltage and frequency are within specified range.)
3. CS1 is ok when the phase angle difference comes within specified 20° range.
CS2 is NOT OK.
4. CS1 is ok.
5. CS2 is OK.
6. IED generates “CB Close” output.
Page 28 of 30
Application Guide – Implementation of MX3EG1A (Auto-Synchronizer) in P40 Agile Issue - A
Annexure – B
Setting Equivalent of MX3EG1A in P40 Agile:
Page 29 of 30
Application Guide – Implementation of MX3EG1A (Auto-Synchronizer) in P40 Agile Issue - A
END OF DOCUMENT
Page 30 of 30
Application Guide – Implementation of MX3EG1A (Auto-Synchronizer) in P40 Agile Issue - A