Download as pdf or txt
Download as pdf or txt
You are on page 1of 47

Mr. Gilberto Maioli, Mr.

Patrick Cost - Integrator Partner Seminar 2012

Hints for smart engineering of IEDs


in generation, transmission and sub-
transmission applications
Hints for smart engineering of IEDs
Content of the presentation

 Abstract
 Why making difficult what is easy?
 Correct use of analog inputs
 Adding ordering options
 Conclusion

© ABB Group
June 12-14, 2012 | Slide 2
Hints for smart engineering of IEDs
Abstract

In this presentation…
 Some real cases are presented
 Some basic concepts about Application Configuration and
Parameter Settings are recalled
 We start from some wrong configurations/settings: the idea
is ”learning from mistakes to avoid them”
 We have a flexible and powerful configuration tool: it is a
point of strength, if we use it in the right way

© ABB Group
June 12-14, 2012 | Slide 3
Hints for smart engineering of IEDs
Content of the presentation

 Abstract
 Why making difficult what is easy?
 The mystery of cycle time and execution order
 To trip or not to trip
 Why doing again what is already done?

 Correct use of analog inputs


 Adding ordering options
 Conclusion

© ABB Group
June 12-14, 2012 | Slide 4
Why making difficult what is easy?
The preconfigured application
Preconfigured RET650 A01 – Main Application ”TRIP”

| Slide 5
Why making difficult what is easy?
The Case: RET650 configuration in 150 kV Substation
Modified configuration of RET650

| Slide 6
Why making difficult what is easy?
The mystery of cycle time and execution order

Back to the basic concepts


 Execution order of the
function block

 Cycle Time of the funcyion


block

 Instance of the function


block

Note:
The data in the bottom area of the FBs are not active by default in
PCM600. The activation of these data is made by select ing
”Tool/Options…” and set the flag of the option ”Show Cycle Time,
Execution Order, Instance Number” in the tab ”Function Blocks” of the
windows ”Options”.

| Slide 7
Why making difficult what is easy?
The mystery of cycle time and execution order

 670 series: The Cycle Time can be 1, 3, 8


or 100 ms.
 650 series: The Cycle Time can be 5, 20 or
100 ms.

Manual 1MRK 511 240-UEN:


670 Engineering Manual.
 A function block that is placed after a
Cycle Time function block in the execution flow must
have the same or a higher cycle time.
Advice: in the logic flow connect together
FBs with the same cycle time!
 A function block that is placed after a
function block in the execution flow must
Execution Order have a higher execution order.
| Slide 8
Why making difficult what is easy?
The mystery of cycle time and execution order
Manual 1MRK 511 240-UEN: 670 Engineering Manual.
For the same time
point, faster cycle times
are executed first.

 The execution order of the function


blocks in group 2 defines the execution
orders needed in group 1 and 3.
 The function blocks in the preceding
logic group 1 must have a lower
execution order than the ones in group
2.
 The following function blocks in group 3
must have a higher execution order
than the function blocks in group 2.
| Slide 9
Why making difficult what is easy?
The mystery of cycle time and execution order
Modified configuration of RET650: …order of evaluation of the FBs

| Slide 10
Why making difficult what is easy?
The mystery of cycle time and execution order
Modified configuration of RET650: order of evaluation of the FBs
 The OR gate is the last FB in the
logic flow, but it is the first FB to be
evaluated in each cycle; its
evaluation is based on the old values
of its inputs, i.e. the values which are
related to the previous cycle
 Consequence:
the trip is delayed of one cycle
time (5 ms) because the execution
order is wrong

| Slide 11
Hints for smart engineering
Content of the presentation

 Abstract
 Why making difficult what is easy?
 The mystery of cycle time and execution order
 To trip or not to trip
 Why doing again what is already done?

 Correct use of analog inputs


 Adding ordering options
 Conclusion

© ABB Group
June 12-14, 2012 | Slide 12
Why making difficult what is easy?
Application Configuration… and Parameter Setting Tools
Is the logic in the
Application Configuration No,
enough to set the behaviour it is not
of the IED? enough.

Also the settings in the PST


(Parameter Setting Tool)
are fundamental.

The logic in the


Application Configuration
and the settings in PST
work together to define
the behavior of the IED.

| Slide 13
Why making difficult what is easy?
The Trip Matrix TMAGGIO…

Let us consider the main application


”TRIP” in the preconfigured IED.
What is the behaviour of the trip Matrix
function block ”TMAGGIO” with the
settings in the picture here below?

 The outputs of
”TMAGGIO” with
settings ”Steady”
follow the inputs
with a settable delay
at pick-up (OnDelay)
and at drop-off
(OffDelay)

| Slide 14
Why making difficult what is easy?
…and the Trip Logic

 The Trip Logic function blocks


”SMPPTRC” and ”SPTPTRC” are used
to trip the circuit breaker
 They also grant the needed minimum
trip time, the single phase trip (if
needed), the internal signals to the
application configuration logic (if any
needed) and perform the lock-out (if
there is no external lock-out relay)

| Slide 15
Why making difficult what is easy?
To trip or not to trip

Back to the case:


What are the effects of the strange logic
and of the wrong settings of TMAGGIO?
 The trip logic function blocks ”SMPPTRC” are
bypassed and are not used to trip the CBs
 The Operation Mode of TMAGGIO is ”Steady”
without any drop-off delay
 Consequence:
- no minimum trip pulse is granted for the CB
trip coils;
- there is the risk that the trip pulse is too
short to trip the CB if the protection function
blocks drop-off in a too short time.
Note:

If the trip matrix ”TMAGGIO” is wired to the Trip Logic FB, the
adviced setting is ”Steady” with no ”OffDelay”/ ”OnDelay”.

When used for direct tripping of CBs, ”TMAGGIO” shall be set as


”Pulsed”, and the “Pulse Time” shall be set to approximately 150
ms in order to obtain satisfactory minimum trip pulse to the
circuit breaker trip coils. (see TRM 1MRK 504 125-UEN).

| Slide 16
Why making difficult what is easy?
To trip or not to trip

…I added
just an OR
gate!!!

| Slide 17
Hints for smart engineering
Content of the presentation

 Abstract
 Why making difficult what is easy?
 The mystery of cycle time and execution order
 To trip or not to trip
 Why doing again what is already done?

 Correct use of analog inputs


 Adding ordering options
 Conclusion

© ABB Group
June 12-14, 2012 | Slide 18
Why making difficult what is easy?
Why doing again what is already done?
 Several strange and wrong
changes were made
 The Trip Output Contact was moved
from the main application ”TRIP” to the
main application ”DIFF_PROT” to
perform an alarm.
A trip output with built in TCS is used for
an alarm

 All these strange changes


Main Application ”DIFF_PROT” are not needed: the right
approach is the
customization of the inputs
of the two trip Matrixes
TMAGGIO in the
preconfigured application
configuration

| Slide 19
Why making difficult what is easy?
Why doing again what is already done?

 650 series: the IED are already


configured
 670 series: preconfigured IEDs are
available
 You can save a lot of time by using
preconfigured IEDs
 You can avoid mistakes in the
application configuration logic by
using preconfigured IEDs
 You may learn by preconfigured
applications and copy them

| Slide 20
Why making difficult what is easy?
Why doing again what is already done?

650 series:
 Typical application examples are
available

 The IEDs are already configured


 Documentation about the configuration
of the HW channels is available (Update
Manager or Connectivity Package DVD)

| Slide 21
Why making difficult what is easy?
How to be smart during the engineering?

650 series
 You can select the package that is more
suitable for your application

 You can base the HW design and wiring of


the protection system on the drawings about
HW channels configuration of the IED

 You can reduce the needs of customization


of the preconfigured application

 That means:
 Shorter time to engineering the application
configuration;
cost reduction;
higher efficiency
higher competitiveness.

| Slide 22
Why making difficult what is easy?
Why doing again what is already done?

670 series:
 You can select either preconfigured or
customized IEDs

 The selection of the HW is open

 You can reduce the engineering time by using


the preconfigured applications

 That means:
 high flexibility;
shorter time to engineering the application
configuration;
cost reduction;
higher efficiency;
higher competitiveness.
| Slide 23
Why making difficult what is easy?
Flexibility is an advantage…

 …but flexibility shall be used in the


right way
 Flexibility allows the fulfillment of the
particular needs of your system…
…but do not forget the basic rules
during the developing of your
configuration

| Slide 24
Hints for smart engineering of IEDs
Content of the presentation

 Abstract
 How to make difficult what is easy
 Correct use of analog inputs
 Mistakes in cycle time

 Adding ordering options


 Conclusion

© ABB Group
June 12-14, 2012 | Slide 25
Correct use of analog inputs
Case study: Measurements

 Consider the following example where an active and


reactive power measurent function is connected through
two different analog input cycle times

| Slide 26
Correct use of analog inputs
Case study: Measurements

| Slide 27
Correct use of analog inputs
Case study: Measurements

 Consider the following


example where an active
and reactive power
measurent function is
connected through two
different analog input cycle
times.

| Slide 28
Correct use of analog inputs
Mistakes in cycle time
Position Phase shift
1ms = 5% of 20ms i.e. 50Hz 1 0
360 * 5% = 18 degree phase shift 2 (+3ms) 54
per 1 ms 3 (+6ms) 108
Only once every 24 ms (3ms * 8ms) 4 (-2ms) -36
will both current and voltage 5 (+1ms) 18
samples match!
… 11 0

| Slide 29
Correct use of analog inputs
Mistakes in cycle time

 Injection of a symetrical
system without any phase
angle shift between voltage
and current should result in
only active power

 However, due to the


incorrect configuration a
reactive power portion is
measured as well

| Slide 30
Correct use of analog inputs
Mistakes in cycle time

 How do we avoid such


mistakes?
 We use the templates that
ABB provides

 But what about functionality


that is not available in these
templates, such as ordering
options for the 670 series?

| Slide 31
Hints for smart engineering
Content of the presentation

 Abstract
 How to make difficult what is easy
 Correct use of analog inputs
 Adding optional functions
 Conclusion

© ABB Group
June 12-14, 2012 | Slide 32
Adding optional functions
Copy by example

 Pre-configured 670 series


IEDs can be ordered with
additional options, such as
backup distance protection
in RED670 or control
functionality in RET670
 Options are never
configured though
 So what is smart practise to
add these options to the
configuration?

| Slide 33
Adding optional functions
License update

 The pre configured


templates provided by ABB
have no ordering options in
the function library
 We have to do a license
update to enable the extra
functionality in the
application, either online or
offline

| Slide 34
Adding optional functions
License update

 Config540.seapr@se.abb.com
 Order Number – Item Number e.g.
2000001-10

| Slide 35
Adding optional functions
Example: RED670

 Consider the RED670 A31


configuration
 Fully functional
 Tested
 Documented
 .. And missing ordered
functionality

 Don’t invent, the


functionality exists! REL670
is fully functional, tested
and documented as well

| Slide 36
Adding optional functions
Example: RED670

| Slide 37
Adding optional functions
Example: RED670

| Slide 38
Adding optional functions
Copy / Paste

 Simply lift functionality from


one application into the
other…
 … and tie all loose ends
into the new application:
1. Analog inputs
2. Binary inputs
3. Trip matrix
4. Binary outputs
5. Disturbance recorder

| Slide 39
Adding optional functions
Feed in- and outputs into the application

 Simply lift functionality from


one application into the
other…
 … and tie all loose ends
into the new application:
1. Analog inputs
2. Binary inputs
3. Trip matrix
4. Binary outputs
5. Disturbance recorder

| Slide 40
Adding optional functions
Application migration

 Whenever moving or
adding functionality,
remember the mentioned
concepts of:
1. Cycle time matching
2. Increasing execution order

| Slide 41
Adding optional functions
Application migration

| Slide 42
Adding optional functions
Application migration

 Whenever moving or
adding functionality,
remember the mentioned
concepts of:
1. Cycle time matching
2. Increasing execution
order

| Slide 43
Adding optional functions
Lifecycle managment

 Configure new templates


and build a library of your
own solutions through:
 PCMP
 PCMI
 Main application
templates

 Migrate your configurations


over the lifetime of the
product
 Migrate your configurations
over the lifetime of PCM600

| Slide 44
Hints for smart engineering
Content of the presentation

 Abstract
 How to make difficult what is easy
 Correct use of analog inputs
 Adding ordering options
 Conclusion

© ABB Group
June 12-14, 2012 | Slide 45
Hints for smart engineering
Conclusion

 Configured, pre-confiured and customized, the solutions


are already there
 Flexibility is a point of strength, but shall be used in the
right way
 Take the basic rules into consideration during the
development of the configuration
 Create new templates and build a thoroughly tested library
of solutions based on pre-configurations

© ABB Group
June 12-14, 2012 | Slide 46

You might also like