Incon OPTImizer 2 User Manual

Download

Page 1

OPTImizer

On-Line Circuit Breaker Performance And SF6 Gas Density Monitor

User’s Guide

INCON

P.O Box 638, Saco, Me. 04072 Tel: 207-283-0156 Fax: 207-238-0158

Page 2

This manual is written for the OPTImizer2 Circuit Breaker Monitor with rmware revision 1.0.1.

LIABILITY DISCLAIMER

INCON (Intelligent Controls) reserves the right to change this document and specications at any time without notice. INCON makes no express or implied warranty with regard to the content of this manual. INCON assumes no liability for errors or omissions, or for any damages, direct or consequential, that may result from the use of this

document or the equipment that it describes. This manual specically pertains to the OPTImizer2 with rmware version 1.0.1.

Intellectual Property

This document contains proprietary information and is protected by copyright. All rights reserved. This document may be reproduced so long as it remains in the custody of the original purchaser, and is used only by the original purchaser’s

personnel for informational purposes. OPTImizer® is a registered trademark of Intelligent Controls.

Warning

Return Shipping Charges

INCON will not accept shipments of returned products without a Return Goods Authorization (RGA) number. RGAs are obtained by contacting INCON’s Technical Service Division – NO RGAs will be given without the unit’s serial number. Return material remains the property of the buyer until replaced or repaired.

Only qualied personnel should undertake application, installation, and use of the OPTImizer² on power systems. While applying this device on the power system, there is always the possibility of faulty equipment operation and electrical shock. Any of these situations may result in injury or death.

Under Warranty: INCON will pay all freight and insurance charges for RGAs.

Non-Warranty: It is the buyer’s responsibility to prepay all freight and insurance charges for RGAs. Refer to INCON

Warranty Policy document #000-1397

CONTACT INFORMATION

Expect this OPTImizer2 User’s Guide to be revised as new information is available and feedback is gathered from the

eld. We welcome and appreciate any comments. Should any questions develop during application, please contact us for

assistance.

COMMENTS ASSISTANCE

INCON - Power Reliability Systems INCON - Power Reliability Systems

Product Manager Technical Service Division

34 Spring Hill Road Tel: 800-872-3455

PO Box 638 www.incon.com / contact.aspx

Saco, ME 04072

e-mail: JWebber@incon.com

Tel: 207-283-0156 Fax: 207-283-0158

Page 3

Contents

List of Tables ........................................................................................................................... 6

1 INTRODUCTION ...........................................................................................................7

1.1 Overview .......................................................................................................................... 7

1.2 Operation Overview ........................................................................................................ 7

2 INSTALLATION ........................................................................................................... 10

2.1 External Connections (Termination) ............................................................................... 10

2.2 Mounting Dimensions .................................................................................................... 11

2.3 SF6 Sensor Mounting .................................................................................................... 13

General Planning Considerations................................................................................................ 15

3 APPLICATION GUIDE ................................................................................................17

3.1 Breaker Wear Symptoms ............................................................................................... 17

3.2 Description of Circuit Breaker Monitoring ...................................................................... 18

Interface to the Breaker Control Circuits ..................................................................................... 19

I2 x T or I x T Wear Duty ................................................................................................................ 21

Time Line to Trip Trace Correlation (Examples) .......................................................................... 22

Alarm Set-points .......................................................................................................................... 26

3.3 Description of SF6 Density Monitoring ......................................................................... 28

4 PROGRAMMING .......................................................................................................29

4.1 Initial Communication With the OPTImizer2 ................................................................... 29

Conguring IP Properties for Communication ............................................................................. 29

Initial Set-up ................................................................................................................................ 33

4.2 General .......................................................................................................................... 35

IP ADDRESS ............................................................................................................................... 35

DATE / TIME ............................................................................................................................... 35

DIAGNOSTICS ............................................................................................................................ 35

DNP3.0 SETTINGS ..................................................................................................................... 35

CIRCUIT BREAKER INFORMATION .......................................................................................... 36

4.3 Circuit Breaker Monitor Settings .................................................................................... 36

Input Mode .................................................................................................................................. 41

Contact Wear Mode ................................................................................................................... 43

If breaker is Rated in MVA, and is being Applied at Voltage other than Nameplate: ................... 45

Contact Life Warning Limit ......................................................................................................... 45

Trip Time Alarm Limit ................................................................................................................... 45

Arc Time Alarm Limit ................................................................................................................... 46

Clearing Time Alarm Limit ........................................................................................................... 46

Travel Time Alarm Limit ............................................................................................................... 46

Closing Time Alarm Limit ............................................................................................................. 46

Operations Count Alarm Limit ..................................................................................................... 47

No Operations Alarm Limit .......................................................................................................... 47

Restrike Alarm ............................................................................................................................ 47

4.4 SF6 MONITOR SETTINGS ............................................................................................49

Low Gas Warning Limit ............................................................................................................... 49

Low Gas Alarm Limit ................................................................................................................... 49

Density or Pressure Trend Limit .................................................................................................. 49

SF6 Sensor Signals ..................................................................................................................... 50

Analog Sensor - Signal Low (Milliamps) ..................................................................................... 50

Analog Sensor - Signal Low Represents (Units) ......................................................................... 50

Analog Sensor - Signal High (Milliamps) .................................................................................... 50

Analog Sensor - Signal High Represents (Units) ........................................................................ 50

4.5 ACTIONS ........................................................................................................................ 51

Preset Remaining Contact Life.................................................................................................... 51

Preset Operation Number ........................................................................................................... 52

Clear Latched Alarms .................................................................................................................. 52

Reset Operations Counter........................................................................................................... 52

Reset SF6 Density Trend Data .................................................................................................... 53

Page 4

5 User Interface ............................................................................................................54

5.1 Post Maintenance Resetting / Presetting ........................................................................ 54

5.2 Periodic Data Dump ........................................................................................................ 54

Alarm History Report ................................................................................................................... 55

Application Event History Report................................................................................................. 56

Circuit Breaker Event History Report .......................................................................................... 57

SF6 Logged History Report .......................................................................................................... 58

SF6 Daily Summary Report ........................................................................................................ 58

Data Interpreting.......................................................................................................................... 58

5.3 Alarm Acknowledgement / Cancellation .......................................................................... 60

5.4 USB Scripts ...................................................................................................................60

6 COMMUNICATION DETAILS .....................................................................................61

6.1 RS-232 ...........................................................................................................................61

6.2 Fiber-Optic Interconnection ............................................................................................ 63

6.3 RS-485 ...........................................................................................................................63

6.4 Ethernet ........................................................................................................................63

6.5 XML .............................................................................................................................. 64

6.6 DNP3.0 .........................................................................................................................66

6.6.1 Device Prole Document ............................................................................................. 66

6.6.2 DNP3.0 Implementation Table .................................................................................. 68

6.6.3 DNP3.0 Point List ..................................................................................................... 69

7 SPECIFICATIONS .......................................................................................................72

DSDP SF6 Density & Temperature Sensor Specications ................................................... 73

Page 5

List of Figures

Figure 1: OPTImizer2 Field Wiring ...................................................................................... 10

Figure 2: OPTImizer2 Mounting Dimensions (Not actual size) ........................................... 11

Figure 3: OPTImizer2 General Dimensions ......................................................................... 12

Figure 4: DSDP Sensor Connections ...................................................................................13

Figure 5: Breaker Cabinet and Control House Interface ...................................................... 15

Figure 6: Typical Trip Trace, with Arc Duration Information Superimposed .......................... 18

Figure 6A: Trip Trace, Using Trip Coil Voltage to Start OPTImizer2 .................................... 22

Figure 6B: Event to Time Correlation of Fig 4, ..................................................................... 23

Figure 6C: Event to Time Correlation of Fig 4, .....................................................................24

Figure 7: Trip Trace, Using Trip Initiate to Start OPTImizer2 ............................................... 25

Figure 8: Alarm Relay Assignments ...................................................................................... 27

Figure 9: User Interface, Conguration Page ....................................................................... 33

Figure 10: User Interface, Conrming Conguration Update ................................................ 34

Figure 11: User Interface, Action Page ................................................................................. 34

Figure 12: Aux A Interface, using Trip Initiate (Red Light) ..................................................... 37

Figure 13: Aux A Interface, using 52 / a Contact in Trip Circuit ............................................. 38

Figure 14: Aux A Interface, using Trip Coil Excitation Voltage .............................................38

Figure 15: Aux A Interface using Individually Wetted 52 / a Contact ..................................... 39

Figure 16: Aux B Interface, using Green Light ...................................................................... 39

Figure 17: Aux B Interface, using 52 / b Contact in Green Light Circuit ................................ 40

Figure 18: Aux B Interface, using Individually Wetted 52 / b Contact ................................... 40

Figure 19: Trip Trace illustrating A Input Delay Setting Considerations ................................ 41

Figure 20: Estimated Trip Latch Release Times based on Nameplate Breaker Voltage ......43

Figure 21: Estimated Arc Time based on Nameplate Breaker Voltage ................................. 44

Figure 22A: A 3-Cycle Arc, No Restrike ................................................................................48

Figure 22B, A 5½-Cycle Arc, No Restrike ............................................................................. 48

Figure 22C, A 5½-Cycle Arc, Restrike Detected ................................................................... 48

Figure 23: User Interface, History Page ............................................................................... 54

Figure 24: User Interface, Status Page with Active Alarms .................................................. 60

Figure 25: 9-pin to 9-pin Cable Connections ........................................................................ 61

Figure 26: 25-pin to 9-pin Cable Connections ...................................................................... 62

Figure 27: Schweitzer Fiber-Optic Interface ......................................................................... 63

Figure 28: RS-485 Full-Duplex Wiring .................................................................................. 63

Figure 29: RS-485 Half-Duplex Wiring ................................................................................. 63

Figure 30: User Interface, Preferences Page ....................................................................... 64

Figure 31: User Interface, Editing the Preferences Page ..................................................... 64

Figure 32: User Interface, XML Page ...................................................................................65

Figure 33: User Interface, XML Command Access ............................................................... 65

Page 6

List of Tables

Table 1: Required Information for Application ....................................................................... 14

Table 2A: Breaker Cabinet Installation Considerations ......................................................... 16

Table 2B: Control House Installation Considerations ............................................................ 16

Table 3: Alarm Set-points ...................................................................................................... 26

Table 4: Alarm Outputs, LED’s and Relays ........................................................................... 26

Table 5: Impact of A Input Assertion on the A Input Delay Setting ........................................ 42

Table 6: Must-Clear Times of Breakers, Voltage Dependent ................................................ 43

Table 7: Accumulated Duty Wear Calculation Example based on Trip History ..................... 52

Table 8: Alarm Codes ............................................................................................................ 55

Table 9: Application Event Codes .........................................................................................56

Table 10, OPTImizer2 Specications...................................................................................72

Page 7

1 INTRODUCTION

1.1 Overview

The OPTImizer2 is an On-Line Circuit Breaker Performance and SF6 Gas Density Monitor that is used for implementing predictive maintenance, maintenance deferral, just-in-time (JIT) maintenance and environmental protection. This intelligent electronic device (IED) monitors the condition of the main contacts, mechanism and dielectric; and logs the following information during CB operation:

• Trip Time (mS) (also known as Opening Time)

• Arc duration (mS) (phase segregated)

• Clearing Time (mS) (also known as Interrupting Time)

• Cumulative I

segregated) from arcing

• Restrike Occurrence (phase segregated)

• Mechanism opening travel time (mS)

• Mechanism closing travel time (mS)

• Operation Counts

The OPTI

hexauoride) gas density and temperature, and then

calculates gas pressure, density and pressure trend rates and changes in mass. The present density, pressure, mass, density and pressure trend rates, and temperature are recorded in the history log at regular intervals. There are alarms for low density and high density or pressure trend rate.

In addition to alarming of anomalies by LEDs and contact alarms, digital information is available for retrieval through a DNP3.0 network or a web browser. The ability to provide historical data, in addition to alarming at setpoints, makes the OPTImizer2 ideal for reliability centered maintenance (RCM) programs.

The OPTImizer2 has passed rigorous standards for survivability in the electric utility substation environment. It may be mounted directly in the circuit breaker cabinet, or in the control house.

A minimal interface to the breaker control and secondary current circuits is used, employing snap-on CT pickup coils and two parallel wiring connections. This minimal interface

to the power circuit breaker makes the OPTImizer2 ideal

for both retrot and new applications. One, two or three

SF6 gas density sensors may be used.

The OPTImizer2 is specically designed for use on gas (SF6) circuit breakers, but can be used on oil and vacuum

breakers.

The wear models used in the OPTImizer2 are valid for any voltage class and correspond to ANSI / IEEE C37.06-1989.

x T or I x T on the main contacts (phase-

mizer

continuously monitors SF6 (Sulfur

1.2 Operation Overview

CONDITION and WEAR LOGGING

• SF6 Density (g / L), Pressure (PSIG, BAR, Kilopascals)

Mass (Pounds, Kilograms)

Trend Rate (units / day) Mass Loss (Pounds,

• SF

Kilograms, Pounds CO2, Metric Tonnes CO2)

• Trip Time (mS)

• Duration of the arcs (by phase) during tripping (mS)

• Clearing Time (mS)

• Cumulative I

segregated) from the arcs during tripping

• Restrike Occurrence (by phase)

• Mechanism opening travel time (mS)

• Mechanism closing travel time (mS)

• Operation Counts (Time and Date Stamping is provided

for each trip operation.)

Alarm set-points may be entered against these items.

SENSING INPUTS

AC Current Input Channels

Three signals (one per phase) from split-core CT pickup coils placed around the secondary of each circuit breaker primary phase CT. The signal is proportional to 0-(Max) A in the primary CT’s secondary circuit (where “Max”= 20, 30, 50, 100,160, 250, 400 or 800 Amps depending upon the CT range chosen).

System frequency may be at 50 or 60 Hz. These signals

are used to record the arc duration and cumulative I I x T contact duty. I2 x T or I x T calculations are accurate in

the presence of DC offset and sinusoidal harmonics up to the 16th.

Split-Core CTs

The OPTImizer2 is designed to be used with INCON Split-Core pickup coils only. Models CT-20, CT-30, CT-50, CT-100, CT-160, CT-250, CT-400 and CT-800

are custom designed for the accuracy required by the

OPTImizer2. Range is 1.4-20A, 2.1-30A, 3.5-50A, 7.0-

100A, 11.2-160A, 17.5-250A, 28.0-400A and 56.0-800A respectively. Three CT’s (one per phase) are provided in a CT kit. These split-core CT pickup coils snap-on for easy, non-intrusive installation to the circuit breaker secondary current circuits. Burden is 0.05VA @ 5 amp.

SF6 Input Channels

Two types of SF6 gas density sensors may be used: 2-wire 4-20mA “analog” or INCON Model DSSP “digital”

type sensor. This input is user-congurable for up to

three sensors. For analog sensors, the density units (grams / liter) are scalable over all or a portion of the 4-20mA signal range. Sensor power of 20VDC is provided for each channel. SF6 gas temperature can also be measured if the “digital” sensor is used.

x T or I x T on the contacts (phase

x T or

Page 8

DC Input Channels

Two discrete voltage signals, 48-250 VDC. The “Aux A” input is used to initiate the trip time log, the mechanism time log, the arc duration time log, and the cumulative I2 T or I T duty log. The “Aux B” input is used to stop the mechanism time log.

A continuous interrogation process detects Aux input logic failure when both inputs are asserted or de-asserted at

the same time for longer than 3 seconds. This conicting

input would indicate a serious problem with the circuit, DC power has been lost, a wire is broken, etc. This condition causes an “A-B Logic” alarm.

EVENT TRIGGERING

• TRIP TIME (opening time log) – (Available in

INPUT MODEs 2 & 4 only.) The start is triggered by a positive assertion (rising edge) to the Aux A input. The stop is triggered by the de-assertion (falling edge) of the Aux A input, with the actual buffer stop time adjusted by the software setting A INPUT DELAY, which accounts for the time difference between the Aux A de-assertion and the actual parting of the main contacts.

• ARC TIME (arc duration log) – maximum duration

is 10 cycles per trip operation; the start time is indexed by an assertion of the Aux A input, with the actual buffer start time adjusted by the software setting A INPUT DELAY, which accounts for the time difference between the Aux A assertion and the actual parting of the main contacts. A proprietary algorithm that detects the end of arc current in all three phases triggers the stop. See Figure 6.

• CLEARING TIME (interrupting time log) –

(Available in INPUT MODEs 2 & 4 only.) The start is triggered by the assertion (rising edge) of the Aux A input. A proprietary algorithm that detects the end of arc current in all three phases triggers the stop.

• TRAVEL TIME (mechanism time log) – (Available

in INPUT MODEs 1 & 4 only.) maximum duration is 10 cycles per trip operation; the start is triggered by a change in state of the Aux A input. An assertion to the Aux B input triggers the stop.

• CLOSING TIME (mechanism time log) – (Available

in INPUT MODE 1 only.) maximum duration is 10 cycles per trip operation; the start is triggered by an assertion to the Aux B input. An assertion to the Aux A input triggers the stop.

• MAIN CONTACT ARCING DUTY LIFE (phase

segregated I2 T or I T per trip operation and phase cumulative I2 T or I T data log); A mathematically

calculated value representative of the destructive arc energy.

FIELD OUTPUTS

Visual Display

On-board LEDs will illuminate and latch when reaching an alarm setpoint or detecting a failure mode. These may be reset by software command.

The circuit breaker OPEN / CLOSED status is also shown by green and red LEDs on the OPTImizer2. This OPEN / CLOSED status indicator should only be used as a secondary indication and to verify correct programming of A INPUT POLARITY and B INPUT POLARITY assertion states.

An LED bar graph alternates every 10 seconds between indicating the remaining contact life and the SF6 gas level. In both cases, the condition of the worst phase is displayed. When more than one LED is lit, the contact life is being displayed. When a single LED is lit, the SF6 level is being displayed.

The scale is -50% to +100% for contact life. The scale for SF6 gas level is based upon the programmed SF6 Fill (density or pressure), the Low Gas Warning Limit and the low Gas Alarm Limit.

When displaying remaining contact life, the green zone is scaled from 100% remaining life to the Warning Limit. The yellow zone is scaled from the Warning Limit to the Danger Limit (0% life). The red zone is scaled from the Danger Limit to 50% below the Limit.

When displaying

SF6 gas level, the green zone is scaled from the Fill (density or pressure) value to the Low Gas Warning Limit. The yellow zone is scaled from the Low Gas Warning Limit to the Low Gas Alarm Limit. The red zone is scaled from the Low Gas Alarm Limit to zero (pressure or density).

When the display is in the green zone, the LED(s) will be lit continuously. When the display is in the yellow zone, the

LED(s) will ash slowly to indicate an approaching alarm

condition. When the display is in the red zone, the LED(s) will

ash rapidly to indicate an alarm condition exists.

A slowly

ashing green heartbeat LED indicates that the OPTImizer² system is functioning normally.

Relay Contacts

Two Form C relays and one Form A relay are provided for alarms. The dry contacts are rated for 3A at 250 VAC or 1 / 2A at 125VDC. These contacts are not intended for breaking DC inductive loads. (For Alarm / relay assignments, see Figure 8):

• The “RED” relay asserts when a Restrike or excess arc

duration is detected, or when the Contact Life Danger limit is reached.

• The “YELLOW” relay asserts when a failed CT pickup

coil is detected, the Contact Life Warning limit is reached, the Operations Count limit is reached, the open or close mechanism time limit is reached, the Trip Time limit is reached, the Clearing Time limit is reached, the No Operations time limit is reached, or an A-B Logic Alarm condition occurs.

• The SF

relay asserts when a Low Gas Alarm limit or

Trend Alarm limit is reached or if there is a malfunction of the SF6 sensor.

Page 9

POWER INPUT

The OPTImizer2 operates from station battery DC or from AC station service power. Input Range: 110 to 250VDC, 90 to 264VAC. Power Consumption: 15 VA maximum.

COMMUNICATION PORTS

These ports are for setting, alarm acknowledgment, history reset, and data viewing / dumping using the DNP3.0 protocol.

RS-232:

Connection: RS-232C, 9-pin female, DCE. A “straight through” cable should be used for connection to a DTE device, such as a PC. (Note: The ASCII protocol is no

longer supported on this port.)

Factory preprogrammed settings for RS-232 and RS485 communication:

Data bits: 8

Stop bits: 1

Parity: None

Baud rate: 9600 bps

Flow control: None

DATA STORAGE

Data is stored in non-volatile memory. The memory holds the most recent 5000 records in a database. A “record” will be made of events that include: program settings changes, CB opening, CB closing, alarm occurrences and scheduled data logs.

SELF DIAGNOSTICS

A blinking green “power on” LED indicates satisfactory operation of the microprocessor system. An "Input Signal" LED indicates the malfunction of a CT Pickup Coil or

sensor.

PHYSICAL

Size: 8.69W x 5.63H x 2.75D, Inches Nominal

Weight: 4 Lbs. 8 Oz.

PERFORMANCE

• Temperature: -20 to +150° F

• Surge Withstand: ANSI C37.90.1, SWC Test

• Electrostatic Dissipation: IEC 810-2

• Environmental: ANSI C37.1

RS-485:

The port is full-duplex and un-terminated. The port can

be congured for half-duplex by adding jumpers from Tx+

to Rx+ and from Tx- to Rx-. If the OPTImizer² is the last device in a network, the Transmit and Receive lines need to be properly terminated with a 120 ohm resistor.

Ethernet:

This port is can be used with DNP 3.0 and TCP / IP protocols simultaneously (in multi-sessions). When connected to a secure local area network (LAN) the OPTImizer² can be accessed remotely with a web browser, providing the correct IP address is given. Firmware upgrades can also be performed through this port using a special upgrade tool (contact INCON Technical Services).

USB COMMUNICATION PORT

This port is for data dumping (BIN les and ASCII text les), alarm acknowledgement or rmware upgrades. It

will Interface only to a USB memory stick. A memory stick with a special software tool can be used to acknowledge alarms. This software tool can be downloaded from the

OPTImizer2 Product CD. A memory stick containing a

special upgrade script and les can be used to upgrade the rmware (contact INCON Technical Services). (See

section 6)

COMMUNICATIONS SOFTWARE

The OPTImizer² is equipped as a web server. A common web browser is all that is needed to communicate to the OPTImizer² using the TCP / IP protocol. If DNP3.0 protocol is used, the DNP Master device will have the proper software for network communication. The OPTImizer² will respond to properly addressed and validated DNP commands.

Page 10

2 I N S TA L L A T I O N

2.1 External Connections (Termination)

110-250 VDC (Twisted Pair Recommended)

90-264 VAC 50/60Hz

Contact Rating: 3A @ 250 VAC or

1/2A @ 125VDC

Terminal Screw

maximum torque

12 inch-Lbs

Use Twisted Pair Cable

Figure 1: OPTImizer² Field Wiring

Density Sensors

The OPTImizer

should be installed as close to the CT Pickup Coils as possible. Cut any excess cable from the Pickup Coils. It is not recommended to extend the Pickup Coil cables.

Page 11

2.2 Mounting Dimensions

Figure 2: OPTImizer² Mounting Dimensions (Not actual size)

Page 12

Figure 3: OPTImizer² General Dimensions

Page 13

2.3 SF6 Sensor Mounting

Pipe Thread

INCON offers an SF6 density sensor as an accessory to the OPTI

signal. This sensor uses a G 3 / 8” British Standard parallel pipe thread with an O-ring seal. An appropriate adaptor

tting will be required when installing one of these sensors

into a manifold or vessel with a different thread.

Other brands of SF6 density sensor are available with many other pipe thread options. Be sure you are combining the appropriate sensor threads with the

appropriate adaptor tting threads.

Location

It is always preferable that the mounted as close to the gas vessel as possible, so that the sensor can be close to the same temperature as the vessel.

The INCON DSDP is a “true density” sensor, not a temperature-compensated pressure sensor. For this reason, it is less critical that it be mounted as close as possible to the SF is not as affected by temperature.

Other brands of SF6 density sensor may be used. Virtually all other brands are temperature-compensated-pressuretype sensors. It is more critical to mount this type of sensor

mizer²: The Model DSDP with digital output

SF6

density sensor be

gas vessel. The density measurement

as close as possible to the SF

gas vessel, so that the

temperature of the SF6 gas can properly affect the sensor. A difference in temperature between the SF6 gas in the vessel and a sensor of this type will cause an error in the density output signal.

The SF6 density sensor may be installed alongside an existing SF6 density switch or gauge. If only one opening

is available, a “T” tting may be used to create a second

opening for the sensor.

Any air in the piping to the sensor can delay accurate density measurement for up to two weeks. The sensor should be installed with the gas port facing upward if possible. A SMALL amount of SF6 can be bled past the sensor threads before tightening the sensor to purge trapped air.

Extreme care must be taken when

Caution

installing sensors. A gas-tight seal must be achieved on all pipe tting and sensor threads.

Vacuum

If a vacuum is used to extract air before lling a breaker

with SF6 gas, do not expose the density sensor to vacuum greater than one atmosphere.

SF6 Sensor Connections Pin 1: Connect to Optimizer² + Terminal (Red Wire) Pin 2: Connect to Optimizer

² — Terminal (Black Wire)

Pins 3 & 4: No Connection

G ⅜" Thread

1.06" Dia. (27 mm)

0.454"

(11.5 mm)

3.24"

(82.3 mm)

1 2

Viewed from end

2.00"

(50.8 mm)

1.135"

(28.8 mm)

Figure 4: DSDP Sensor Connections

Page 14

2.4 Planning for Installation and Programming, Required Field Documentation

The OPTImizer2 application should be planned, much like the application of other IEDs, such as a protective relay, fault recorder, or monitor. Actual programming and installation can be accomplished in a few hours (typically 2 hours) after the

setpoints are calculated and determined. The required information is tabulated below:

Information Source(s)

CT Primary Coil Ratio

Logic and Assertion Levels of Aux A and Aux B inputs

Time Difference Between Aux A input Assertion and Parting of Main Contacts

One Line Diagram, Visual Inspection of Applied CT Ratio

Circuit Breaker Elementary Diagram

Trip Trace, ANSI Standards (C37.06)

• Bushing CT Ratio

• Input Mode

• A Input Polarity

• B Input Polarity

•A Input Delay

(Time Difference between Aux A input and the main contacts parting)

AffecTed SeTTINgS / USe

• Contact Life Mode

x T or I x T)

• Contact Life Danger Limit

• Contact Life Warning Limit (%)

• Operations Count Limit

• SF6 Gas Fill Weight

Breaker Nameplate Data

Breaker Manufacturer’s Data Sheets, Breaker Nameplate, ANSI Standards (C37.06)

• SF6 Gas Fill Pressure

• SF6 Gas Fill Temperature

• Breaker Volume

Breaker Trip History

Type of Breaker for employing Restrike Detection

Operations Logs, Relay Fault Records, Digital Fault Recorders, Oscillographs, Estimation

Generally used on SF

Gas Breakers • Restrike Alarm (Enable / Disable)

• Preset Remaining Contact Life (% for each phase)

System Frequency • Power System Frequency

Date • DATE Time • TIME Site Identication System Topology, Mapping • Site Name Baud Rate, Parity, Flow

Control, Stop Bits

Pre-programmed Setting, Interfaced

Communication Equipment if Networked

Table 1: Required Information for Application

• Port Settings

Page 15

General Planning Considerations

Aux B Interface

Aux A Interface

Phase A, Snap-on CT

Phase B, Snap-on CT

Phase C, Snap-on CT

Phase A, Snap-on CT

Phase B, Snap-on CT

Phase C, Snap-on CT

Aux A Interface

Aux B Interface

Bushing CT (Typ.)

Phase Relay (Typ.)

Ground Relay

(Typ.)

BREAKER CABINET

CONTROL HOUSE

or TI

The OPTImizer2 may be installed in a control house or breaker cabinet. The required interfaces can be obtained at either location. The SF6 sensors must be installed on the circuit breaker itself. Sensor accuracy is best when installed nearest to the interrupter vessel.

The OPTImizer2 should be installed as close to the CT Pickup Coils as possible. Cut any excess cable from the Pickup Coils. It is not recommended to extend the Pickup Coil cables.

Phase A, CT Pickup Coil

Phase B, CT Pickup Coil

Phase C, CT Pickup Coil

Phase A, CT Pickup Coil

Phase B, CT Pickup Coil

Phase C, CT Pickup Coil

Figure 5: Breaker Cabinet and Control House Interface

Page 16

The actual installation location may be determined after review of many factors, some of which are outlined below:

Circuit Breaker Cabinet Mounting

Pros Cons

Trip initiate signal may not be available should

Readily accessible to Maintenance personnel.

A 52 / a contact (in the actual trip circuit or individually wetted) for asserting the Aux A input, and a 52 / b contact (in the actual green light circuit or individually wetted) signal for asserting the Aux B input are readily available. A trip initiate signal may also be available for the Aux A input assertion if desired.

it be the desired interface for the Aux A input assertion.

May be environmentally unfriendly (temperature, humidity, electrical noise, transients) for both the

equipment and personnel.

Secondary current circuit interface is readily available (from bushing CTs).

Table 2A: Breaker Cabinet Installation Considerations

Control House Mounting

Pros Cons

Centralized location for multiple unit installations.

Trip Initiates (red light) signal for asserting the Aux A input, and an end of mechanism travel (green light) signal for asserting the Aux B interfaces are readily available. A 52 / a contact signal may also be available for the Aux A input assertion if desired.

Secondary current circuit interface is readily available (from relays).

Usually easier to integrate (short physical wiring runs in close proximity to an RTU, PLC, substation computer, modem, port switcher, etc.).

Environmentally friendly (temperature, humidity,

electrical noise, transients) for both the equipment

and personnel.

Integration may be more difcult (long distances,

electrical noise, step potential).

May lie within an area not readily accessible to Maintenance personnel.

The 52/a and 52/b may not be available if they are the desired interface for the Aux A and Aux B input assertion.

Not near SF

ports on circuit breaker, long cable

runs from sensors may increase noise.

Table 2B: Control House Installation Considerations

Page 17

3 APPLICATION GUIDE

3.1 Breaker Wear Symptoms

Breaker Wear Symptoms

Power circuit breakers exhibit symptoms of wear from the stresses of operation. The wearing of a breaker may adversely affect the mechanism, the dielectric capabilities for extinguishing an arc, and the main contacts by erosion due to duty (wear).

Mechanism Condition

The mechanism operation during a trip essentially consists of three events:

• Trip Latch Operation

• Travel Mechanism Operation

• End of Travel Mechanism (dashpot, including

preparation for closing)

• Closing Mechanism Operation

Samples of issues that may cause problems within the mechanism are:

• Poor trip coil action due to high impedance or

shorted turns

• Sticking in the latch

• Lack of lubrication

• Binding of components

• Bearing wear or seizure

• Compromise in the stored energy system (spring,

pneumatics)

Any of these may manifest themselves as a decrease in the breaker travel velocity. Accompanying a slowing in velocity would be a detectable increase in transit time from the closed to tripped (open) position. This is due to the relationship of V T = D, where V is velocity, or rate (in. / sec.), T is time (secs.), and D is distance (in.).

Solving for T, the equation transforms to T = V / D. Any

decrease in velocity must be accompanied by an increase in time. In the case of a power circuit breaker, if the time interval between two signals is monitored, one being the beginning of travel and the other the end of travel, increases in transit time can be detected.

The OPTI mechanism travel transit times (open and close) to aid in determining the condition of the mechanism, and predicting when maintenance is needed.

mizer

monitors trip response time and

Dielectric Capability

The ability of a circuit breaker to extinguish an arc can be monitored by examining the amount of time an arc is present after a trip command to the breaker is given. If the mechanism transit time remains constant, but an increase in arc duration is noted from a baseline level, some “dielectric” compromise can be assumed to have occurred in the arc chamber. Samples of issues that may cause problems in the ability of a circuit breaker to extinguish an arc are:

• Contaminated oil

• Contaminated gas

• Low gas density

• Worn bafes

• Nozzle ablation

The OPTI determining if maintenance is needed to prevent loss of dielectric and to predict when gas needs to be added.

The OPTImizer2 monitors arc duration time to aid in

determining the condition of the dielectric quality within the

arc chamber, and predicting when maintenance is needed.

The OPTImizer2 monitors phase segregated I2 x T or I x T values from each operation, and maintains a phase segregated summation log of the cumulative duty that each pole has undergone to aid in determining the condition of the main contacts within the arc chamber.

Main Contacts Erosion Due to Duty

The main contacts of a circuit breaker erode (wear) from the heat present during the arc interval. The relationship for breakers with a medium (air, gas, oil) is expressed in ANSI C37.06, Rating of Power Circuit Breakers on a

Symmetrical Basis, as a dI / dT function, which can be reduced to an I2 x T expression.

The erosion of the main circuit breaker contacts is directly proportional to the I2 x T present during each arc. To effectively measure the I2 x T during the arc interval, steps must be taken to insure that DC offset is included in the calculation, and the sampling rate is high enough to insure that harmonics present within the arc are also accounted for in the calculation.

mizer

monitors SF6 gas density to aid in

Page 18

3.2 Description of Circuit Breaker Monitoring

Typical Trip Trace Example

A typical trip trace is illustrated in Figure 6. The OPTImizer2, by examining signals corresponding the start of the trip (trip initiate or the 52 / a contact opening), the end of mechanism travel (green light or 52 / b contact closing), and secondary phase currents can obtain a wealth of information about the power circuit breaker.

Figure 6: Typical Trip Trace, with Arc Duration Information Superimposed

General Comments

Examination of a typical trip trace allows the quantities the

OPTImizer2 records to be visualized. Arc duration (ARC),

although not possible to record during a de-energized trip

test using conventional test equipment, is shown here for

illustration.

The time line corresponding to the parting of the main contacts (mains) is used to determine the time difference between this event and either the trip initiate or the 52 / a contact opening. In each case the A INPUT DELAY time will be different. The choice to use the trip initiate or the parting of the 52 / a will depend on where the OPTImizer’s Aux A input is wired in the circuit. The proper A INPUT DELAY must be programmed accordingly. The ability to know this time difference allows the OPTImizer2 to precisely start timing the arc for both the arc duration record and the wear duty (I2 x T or I x T) calculations. Reference for the following function descriptions in this section should be made to Figure 6A, Typical Trip Trace Diagram.

Interface to Breaker Secondary Current

Secondary Current Interface - The per phase (fA,

fB, fC) interrupting duty information and arc duration information is ascertained by interfacing to the bushing CT secondary current circuits using snap-on CT Pickup

Coils. The acquisition of interrupting current information

is therefore non-intrusive, as the CT secondary current

circuits do not have to be cut or otherwise modied. No shunts are required.

The CT secondary circuits are available at the breaker cabinet and the control house, (if there is a control house). The Protective Relay Bushing CT’s secondary circuits should be used, since Metering CTs may saturate at high current levels associated with fault duty.

Page 19

Interface to the Breaker Control Circuits

Two discrete voltage inputs are used to obtain information to determine the start of the trip (Aux A) and the end of mechanism travel (Aux B). These two inputs may be directly coupled, using parallel wiring connections, to the breaker control circuit or separately wetted breaker auxiliary contacts. Additionally, auxiliary relays or diodes may be used for isolation or to accommodate dual trip

circuits. No shunts are required.

Depending on the application, the voltage state can change from no-voltage to voltage, or voltage to novoltage. The OPTImizer² is programmed to react to one of the changes as an assertion to an input. De-bounce

circuitry is employed, and input assertions are dened as the rst transition point in voltage.

Aux A Input Interface

The Aux A input is the starting trigger for the Trip Time log and the mechanism time log. With the time adjustment from the A INPUT DELAY setting, the Aux A starts the arc duration log and the wear duty logs.

The Aux A input interface is made using a parallel connection in the actual breaker control circuit: to the trip initiate (shunting of the red light or the Trip Coil); to the 52 / a contact (closed to opened), or an individually wetted 52 / a contact (closed to opened) that is not in the actual trip circuit.

There are other possibilities using additional interface devices, such as isolating relays and diodes.

There are advantages to using the Trip Coil signal for assertion of the Aux A input:

• Allows capture of the latch time in the Trip Time log.

As many mechanism problems are in the latch, this is the most important advantage. Use of the 52 / a contact for interface will not allow capture of the latch time in the mechanism time log.

• Repeatable signal with no “slop” issues as can occur

with mechanically linked auxiliary contacts.

The OPTImizer²’s Aux A input is fused, optically isolated and transient protected. If it fails, it will be open, therefore it cannot cause a false trip or short circuit when applied in actual breaker control circuits.

Aux B Input Interface

The Aux B input is the stopping trigger for the mechanism time log. The Aux B input assertion can be made using either a green light signal (off to on) or a 52 / b contact state change (opened to closed). There are other possibilities using additional interface, such as isolating relays and diodes.

INPUT MODE

The Aux Input logic mode can be programmed for one of four conditions:

Mode 1: Use this mode when the Aux A & B Input voltages remain continuously high or low until a breaker event occurs (as when wired across the red and green lights), then change to the opposite state and remain constant until the breaker is reset. In this mode, TRIP TIME and CLEARING TIME are not logged and their alarms are disabled.

Mode 2: Use this mode when the Aux A Input voltage changes state momentarily, when a breaker event occurs (as when wired to the trip coil signal), but Aux B is not wired. In this mode, TRAVEL TIME and CLOSING TIME , and A-B LOGIC data are not recorded and their alarms are disabled. The circuit breaker OPEN and CLOSED states cannot be indicated in this mode. The red “CLOSED” LED will be lit continuously.

Mode 3: Use this mode when the Aux A Input voltage is continuous, as in Mode 1, but Aux B is not wired . (Used in cases where there is no Aux B switch available) In this mode, TRIP TIME, CLEARING TIME, TRAVEL TIME, CLOSING TIME, and A-B LOGIC data are not logged and their alarms are disabled.

Mode 4: Use this mode when the Aux A Input voltage changes state momentarily, when a breaker event occurs (as when wired to the trip coil signal) and the Aux B input voltage remains continuously high or low until a breaker event occurs, then changes to the opposite state and remains constant until the breaker is reset. In this mode, the OPTImizer² can record TRIP TIME, CLEARING TIME, TRAVEL TIME and A-B LOGIC data and their alarms can be active. Closing Time cannot be recorded and its alarm will be disabled.

TRIP TIME (Trip Mechanism Time Log) (Input Modes 2 & 4 only)

When INPUT MODE 2 or 4 is selected and the "Aux A" input is wired as shown in Figure 14, the OPTImizer² will record TRIP TIME. The TRIP TIME log consists of a timer. The timer starts from an assertion of the “Aux A” input, and stops with the de-assertion of the “Aux A” input, adjusted by the A INPUT DELAY value. The assertion level is dened in software (A INPUT POLARITY), and is application-dependent. The TRIP TIME measurement starts with the Trip Initiate voltage application to the Trip Coil and ends when the 52a contact opens (+ / - A Input Delay value), de-energizing the Trip Coil.

The Aux B input is fused, optically isolated and transient protected. If it fails, it will be open, therefore it cannot cause a false indication or short circuit when applied in actual breaker control circuits.

Page 20

TRAVEL TIME (Mechanism Time Log) (Input Modes 1 & 4 only)

When INPUT MODE 1 or 4 is selected, the OPTImizer² will record mechanism TRAVEL TIME. The mechanism time log consists of a timer. The timer starts from an assertion (or de-assertion in Mode 4) of the “Aux A” input, and stops with an assertion to the “Aux B” input. The assertion levels are dened in software (A INPUT POLARITY & B INPUT POLARITY), and are application-dependent.

It is possible to start the mechanism trip transit time log from one of two instances, either the trip initiate signal, or the opening of the 52 / a contact.

Note: The “Aux A” input is the common start for both the mechanism time log and the arc time log functions.

ARC TIME (Arc Time Log)

The individual, phase-segregated Arc Time logs employ a timer, starting with the main breaker contacts parting and ending with the cessation of current in each phase.

Starting of the Arc Time Log

The arc time log is indexed to start with an assertion (or de-assertion in Modes 2 & 4) of the “Aux A” input. The assertion level is dened in software (A INPUT POLARITY), and is application dependent. The actual starting of the log is dependent on a setting used to adjust the time interval difference between the “Aux A” assertion and the actual parting of the mains. This adjustment time is referred to as A INPUT DELAY in Figure 6.

The A INPUT DELAY value may be either positive or negative, depending on if the “Aux A” assertion is later or earlier than the mains parting:

• The adjustment time (A INPUT DELAY) is positive (+), if the mains part later than the “Aux A” assertion

• The adjustment time (A INPUT DELAY) is negative (-), if the mains part earlier than the “Aux A” assertion

Note: The “Aux A” input is the common start for both the mechanism time log and the arc time log functions.

Stopping of the Arc Time Log

The arc time logs stop with the cessation of current in each phase. The cessation of current is determined by a proprietary software algorithm which does waveform analysis in addition to checking for CT Secondary current falling below 7% of the Pickup Coil full scale current rating for more than 8 consecutive samples (1 / 4 cycle).

Note: In instances where the CT Secondary phase currents are less than 7% of Pickup Coil full-scale current rating and

the breaker trips, an ARC TIME of 000 mS will be recorded.

Page 21

CLEARING TIME (Clearing Time Log) (Input Modes 2 & 4 only)

The individual, phase-segregated CLEARING TIME logs use a timer, with the starting point at the beginning of the Trip signal and ending with the cessation of current in each phase. Thus the Clearing Time for each phase is the sum of the measured TRIP TIME and ARC TIME. The programmable A INPUT DELAY value has no effect on the CLEARING TIME.

This time represents the interrupter's overall efciency, both mechanical and dielectric.

I2 x T or I x T Wear Duty

(Phase segregated per Trip Operation & Phase Segregated Cumulative Duty Log)

The individual, phase-segregated main contact wear duty logs employ a method of recording the destructive energy of each arc incident that is programmable for I2 x T or I x T. The measured current is (squared for I2 x T and then) multiplied by the time between measurement samples. The sum of these sample calculations is recorded in the main contact duty

wear logs for each phase, for each arc event. As subsequent arc events occur, the measured I2 x T or I x T is added to the

phase-segregated main contact wear duty accumulation logs.

Note: If the CT Secondary phase currents are less than 7% of the Pickup Coil’s full-scale current rating and the breaker

trips, an ARC TIME of 000mS will be recorded. The values of I2 x T or I x T recorded for such incidents are recorded as 0 in the wear duty log.

Operations Counter

A counter will increment each time the circuit breaker opens. An Operations Count alarm limit can be programmed. When the operations count reaches the limit an alarm is asserted.

Restrike Detection

The RESTRIKE setting is used to enable the detection of restrikes. When Restrike detection is activated, the ANSI C37.100 criterion is used, which states that if an arc is extinguished, and more than ¼ cycle later it re-ignites, that is considered a restrike (see Figure 22 on page 46). If a re-ignition takes place before the ¼ cycle period elapses, it is not

considered a restrike, but rather a continuance of the original arc. The rst restrike detected will assert the alarm. Each CB

Trip record in the Circuit Breaker Event History will indicate whether a restrike has occurred by phase - true or false.

Page 22

Time Line to Trip Trace Correlation (Examples)

The following examples show how the OPTImizer2 logs events. They include:

• Arc record examples

• Interactions of the Aux A and Aux B inputs

• The phase currents

• The A INPUT DELAY setpoint

• The ARC TIME and TRAVEL TIME setpoints

The setpoints and applied limits for the following examples are given below each time line (Figs. 6A, 6B, 6C and 7).

MECHANISM

TRIP MECHANISM TIME (TRIP TIME),

(24 mS)

TRAVEL TIME, difference

between Aux A and Aux B

Input state changes

(49 mS)

Figure 6A: Trip Trace, Using Trip Coil Voltage to Start OPTImizer

Page 23

Figure 6B: Event to Time Correlation of Fig 6A,

Using Trip Coil Voltage to Start OPTImizer

Example:

• The Aux A input on the OPTImizer2 is asserted by the Trip Signal voltage measured across the Trip Coil.

• The recorded TRIP TIME is 25mS

• The recorded TRAVEL TIME is 51mS (94mS – 43mS)

• The recorded ARC TIME is 32mS

• The recorded CLEARING TIME is 56mS

• The A INPUT DELAY Setting is -19mS, as the assertion to the Aux A input on the OPTImizer2 is the breaker Aux A

contact, which opens 19mS after the main contacts part (A INPUT DELAY is negative when the assertion to the Aux A input is later than the main contacts parting)

• The TRIP TIME alarm limit is 30mS

• The ARC TIME alarm limit is 48mS (32mS plus 16mS margin)

• The CLEARING TIME alarm limit is 78mS (56mS plus 22mS margin)

• The TRAVEL TIME alarm limit is 76mS (51mS plus 25mS margin)

This OPTImizer2 would not be in an alarm state after this operation.

Page 24

Figure 6C: Event to Time Correlation of Fig 6A

Using a Separately Wetted 52 / a Contact to Start OPTImizer2 Measurements

Example:

• The Aux A input on the OPTImizer2 is asserted by voltage from a separate contact on the 52 / a switch.

• The TRIP TIME cannot be recorded with this wiring method.

• The CLEARING TIME cannot be recorded with this wiring method.

• The recorded TRAVEL TIME is 51ms

• The recorded ARC TIME is 32mS

• The A INPUT DELAY Setting is -19mS, as the assertion to the Aux A input on the OPTImizer2 is the same Aux A

switch, which opens 19mS after the main contacts part (A INPUT DELAY is negative when the assertion to the Aux A input is later than the main contacts parting)

• The ARC TIME alarm limit is 48mS (32mS plus 16mS margin)

• The TRAVEL TIME alarm limit is 76mS (51mS plus 25mS margin)

This OPTImizer2 would not be in an alarm state after this operation.

Page 25

ref

Current

"Aux A" input

"Aux B" input

30 40 50 60 70 80 9020

TIME (mS)

Not Asserted

Asserted

Pre- or Post Trip Event, Asserted

Pre- or Post Trip Event, Not Asserted

Aux A Input asserts at T

ref

= 0

Main Contacts open at T=24mS

Arc Extingushes at T=56mS

Arc Duration 56mS minus 24mS=32mS

Aux B Input asserts at T=94mS

Aux A assertion is 24mS earlier than Mains Parting

AD = +24

Total Arc Duration =

32mS

100

110

A Input Delay = +24

Figure 7: Trip Trace, Using Trip Initiate to Start OPTImizer2

Example:

• The Aux A input on the OPTImizer2 is asserted by the trip initiate signal (red light) in the breaker trip circuit

• The recorded TRAVEL TIME is 94ms

• The recorded ARC TIME is 32mS

• The A INPUT DELAY Setting is +24mS, as the assertion to the Aux A input on the OPTImizer2 is the trip initiate

signal, which asserts 24mS before the main contacts part (A INPUT DELAY is positive when the assertion to the Aux A input is earlier than the main contacts parting)

• The ARC TIME alarm limit is 48mS (32mS plus 16mS margin)

• The TRAVEL TIME alarm limit is 141mS (94mS plus 47mS margin)

This OPTImizer2 would not be in an alarm state after this operation.

Page 26

Alarm Set-points

The following recorded parameters have alarm set-points placed against them. Specically, these alarm points are:

Parameter Units SeTpOINT ReSOLUTION Range

Trip Time mS 1mS 0-999 mS Arc Time mS 1 mS 0-165 mS Clearing Time mS 1mS 0-265 mS Travel Time mS 1 mS 0-265 mS Contact Life Warning Percent 0.1 Percent 0.0% to 99.0%

Contact Life Danger Amp (Squared) - Seconds

0.1 • 10x, where x is the

base 10 exponent

0.1 to 9.9 • 10

Operation Counts Occurrences 1 Count 0-9999 Counts No Operations Time Days 1 Day 0-999 Days Closing Time mS 1 mS 0-999 mS SF6 Low Gas Warning Bar; PSI; g / L (Kg / m3); Kilopascals 0.1 0.0 to 25 Bar, 60 g / L SF6 Low Gas Alarm Bar; PSI; g / L (Kg / m3); Kilopascals 0.1 0.0 to 25 Bar, 60 g / L

Gas Trend Rate Bar; PSI; g/L; Kilopascals per day 0.1

Table 3: Alarm Set-points

0.0 to 40 Bar, 100 g / L per day

Note: To disable any function, set the value to “0” (The Contact Wear Danger function cannot be disabled).

Alarm Outputs, Indications & Relay Assertions

Upon reaching an alarm setpoint, output designations are:

Alarm LED ReLAy cONTAcT

TRIP TIME

ARC TIME

CLEARING TIME

TRAVEL TIME

Contact Life Warning

Contact Life Danger

Restrike

Operation Counts

NO OPERATION TIME

CLOSING TIME

A-B INPUT LOGIC

Failed CT Pickup

SF6 Low Gas Warning

Low Gas Alarm

Density or pressure Trend Rate

Loss of SF

Sensor Signal Out of Range

Invalid Conguration

Internal Error

Input Invalid

Unknown CB Monitor Activity

Unknown SF

Sensor

Monitor Activity

Slow Speed Yellow

Excess Arc, Flashing Red

Excess Arc Red

Slow Speed Flashing Yellow

Bargraph Slow Flash Yellow

Bargraph Fast Flash Red

Restrike Red

Operations Flashing Yellow

Operations Yellow

Slow Speed Yellow

Input Signal Yellow

, Bargraph Slow Flash None

, Bargraph Fast Flash Blue (SF6)

, Blue (SF6)

, Input Signal, No Bargraph Blue (SF6)

No Bargraph Blue (SF6)

Closed & Open Fast Flashing None

Input Signal Fast Flash Yellow

Operation Fast Flash Yellow

Fast Flash Blue (SF6)

Table 4: Alarm Outputs, LED’s and Relays

Page 27

Viewed graphically, the alarm relay assignments are:

I²T Danger

Restrike

Excess Arc Duration

Excess Clearing Time

Excess Trip Time

A-B Input Logic

Excess Travel Time

I²T Warning

Operations Count

No Operations

Excess Closing Time

Failed CT Pickup

Internal Error

Input Invalid

Unknown CB Monitor Activity

Low Gas

Trend

Loss of SF

Unknown SF

Sensor

Signal out of Range

Monitor Activity

Red

Yellow

Blue SF

Figure 8: Alarm Relay Assignments

Page 28

3.3 Description of SF6 Density Monitoring

The OPTImizer2 monitors SF6 gas density to aid in identifying circuit breakers with potential problems. Investigation and maintenance can be scheduled sooner, keeping SF6 gas loss to a minimum.

Density Loss

Power circuit breakers that use SF6 gas as a dielectric can lose gas from one or a combination of several causes. Lost gas may adversely affect the dielectric capability for

extinguishing an arc, and consequently, the main contacts

by erosion (wear).

Gas Loss Causes

The following issues may cause problems leading to loss of SF6 gas:

• Gasket deterioration

• Shaft Seal deterioration

• Tank porosity

• Bushing porosity

• Tubing & pipe ttings

• Heater failure (allowing liquefaction)

Any of these may manifest themselves as a decrease in SF gas density. Accompanying a loss of SF6 gas density may be a detectable increase in arc duration.

SF6 Gas Monitoring

SF6 Gas Density Sensors The OPTImizer2 monitors

the signal from two types of SF6 gas density sensors: Analog (4-20mA) and Digital (INCON DSDP). Both types

are connected to the OPTImizer2 with two wires. The

OPTImizer2 provides DC power to the sensors. The

Digital sensor will provide a temperature signal in addition to the density signal.

SF6 Mass Loss Reporting

Once a day, the OPTImizer2 will calculate the change in SF6 mass. This value will be logged in the SF6 History, Daily Summary.

Density or Pressure Trends and Alarms

Once a day, the OPTI

mizer

will compute density or

pressure trends for each active SF6 input channel. Each density or pressure trend is based upon measurements

collected over a 15-day time period. A Condence Level

(%) will be associated with each of these trends, indicating the number of valid readings each trend is based upon and the stability of the readings. Fifteen days of valid readings

are required for 100% condence in the computed Density

or Pressure Trend.

If the Density or Pressure Trend Alarm Limit is reached or exceeded, the SF6 Alarm LED will light, the SF6 Alarm Relay will close and a time-stamped record of the alarm will be recorded in the history log.

Low Gas Alarm Forecast

Once a day, the OPTI

mizer

computes the number of days before the SF6 gas will reach the Low Gas Alarm Limit. This forecast will be based upon the Density or Pressure Trends just computed.

SF6 Gas Data Logging

Every 2 hours, the OPTImizer2 will log the present SF6 gas density, pressure & temperature readings. Once a day, the OPTImizer2 will log the average density, average

pressure, density or pressure trend, condence level,

mass, change in mass and accumulated mass loss.

At any time, when a warning or alarm occurs, its occurrence is recorded in the history log.

The OPTImizer2 measures SF6 gas density and calculates SF6 gas pressure from the measured density. Pressure calculations are based upon entered or calculated SF6 gas volume and temperature measurements. The Pressure Trend is calculated from the Density Trend and temperature measurements. SF6 volume is calculated from entered nameplate gas ll weight, pressure and temperature, or taken directly from entered gas volume.

Low Gas Warning and Alarm

If the SF6 gas density or pressure decreases, the

OPTImizer2 will give a warning when a programmable

limit is reached. The SF6 Alarm LED will light and a timestamped record of the warning will be logged in the history. If the SF6 gas density or pressure decreases further, a Low Gas Alarm will be activated, closing the SF6 Alarm Relay. A time-stamped record of the alarm will be recorded in the history log.

Page 29

4 PROGRAMMING

4.1 Initial Communication With the OPTImizer2

To initialize communications with an OPTImizer2, use the provided “crossover” cable to connect the Ethernet port on the OPTImizer2 to the Ethernet port on a computer. Power-up the OPTImizer2 and computer, then set the computer’s IP

address to “192.12.27.2”

Conguring IP Properties for Communication

Before attempting to modify any computer settings, contact the Information Technologies department of your business, if available. Some computer accounts may have restricted permissions to overcome before any changes are allowed to be made to TCP / IP settings. At the PC:

Windows XP™

1. Log into your PC with Windows™ operating system.

2. Click on Start, then select Control Panel.

• In Classic View, click on Network Connections.

4. Right-click on Local Area Connection and select Properties.

• In Classic View, click on Network Connections.

Page 30

5. In the Local Area Connection Properties dialog box, under “This connection uses the following items,” select Internet Protocol (TCP / IP) and click Properties.

6. Select Use the following IP

address.

7. Enter the IP address “192.12.27.2”

Subnet Mask: Masking is a way to diversify the use of multiple subnets. The mask must match that of the network the

OPTImizer2 is connected to. Masks are used in networking to create ‘sub-networks’ within a whole, like slicing an apple.

You have separate slices that may be in different locations, but they are still from the same apple. Administrators use this

to make separate networks, to maximize bandwidth or capacity of medium resources (cables or ber). Therefore, when

your network uses static IP addressing (assigned by an administrator), this mask must match the Subnet Mask of the router port that it is attached to. If the network uses a DHCP server (automatically assigns IP addresses) then the mask

should meet the specications set by your administrator.

Default Gateway: The Gateway is the logical address to the nearest router port, commonly the one that is connected to the console. Consult your administrator for details on this and other network parameters.

8. Leave the DNS information blank. Click “OK” and close the Control Panel.

Page 31

Windows 7™

Below is shown one way to congure the connection using Windows 7™.

1. Open Windows™ Explorer and right-click on Network.

2. Select Properties.

3. Select Change Adapter Settings

Page 32

4. The screen should show the Local Area Connection. Right click on the connection and select Properties.

5. Select Internet Protocol Version 4 (TCP/IPv4)

6. Select Properties

7. Enter the IP address 192.12.27.2

Page 33

Check Status of Connection

1. Check the status of your connection by going to the Network Connections window.

2. If the connection status is disabled, enable it by right-clicking on the Local Area Connection and selecting

Enable. If technical difculties arise, please contact INCON Technical Support before proceeding.

Open the web browser. Type the OPTImizer2’s default IP address (192.12.27.1) in the browser’s address eld. You should see the OPTImizer2’s STATUS page. Click “Conguration”, at the top left, to move to the CONFIGURATION page. Click “Edit”, at the top right, to make changes to the OPTImizer2’s conguration.

Figure 9: User Interface, Conguration Page

Initial Set-up

Conguration settings required to initially set-up (commission or test) an OPTI

mizer

are included under the following

headings:

• Passwords (The default Administrator’s password is “admin”)

• Date / Time

• DNP3

• Circuit Breaker Information

• Circuit Breaker Monitor

Monitor

• SF

Sensor A

• SF

Sensor B

• SF

Sensor C

• SF

Page 34

Figure 10: User Interface, Conrming Conguration Update

Following the guidelines listed in this manual, make the appropriate changes to each conguration parameter. When all changes are entered, click “Yes” to update the conguration. The correct Administrator’s password (initially set to “admin”)

will need to be given for the changes to be saved.

Commissioning the OPTI

mizer

involves setting most of the available programming parameters. Note that during initial setup

and programming, alarms may be triggered inadvertently. When all conguration programming is done it is recommended to

"Clear Latched Alarms" on the ACTION page to clear alarms and preset the remaining contact life (if desired).

Figure 11: User Interface, Action Page

Page 35

4.2 General

IDENTIFICATION

The OPTImizer2 provides four text elds (ID Line 1 through 4) that can be used to identify the circuit breaker, substation, etc... Up to 40 text characters of all types can

be entered in each eld. (Site Name, Address, City, State

and Telephone are a few suggestions. Any desired text can be entered). Note that the text entered in ID Line 1 will be used in the heading of the user interface.

To change the identication text, select the

CONFIGURATION tab and click "EDIT". Type the desired

text in the eld.

PASSWORD

The OPTImizer2 uses three levels of access rights, Administrator, User and Guest. Each has a separate password. The Default password for the Administrator is “admin”.

The Default password for the User is “user”. There is no default password for the Guest. It is STRONGLY recommended that the password for the Administrator be changed immediately. The password for the User should also be changed for better security.

A password for the Guest can be also added to prevent access to viewing all data. Passwords are limited to a maximum of 40 characters. The password can contain upper and lower case letters and any keyboard character.

If the Administrator’s password is changed and then forgotten, program settings will not be able to be changed. If this occurs call the INCON factory for assistance. An INCON service technician can use a diagnostic password to reset the Administrator’s password. Remote internet access to the OPTImizer2 is required for the technician to do this.

Guest Level rights include the ability to VIEW all

Status, Alarms, Conguration and Preferences data, and

download reports from the history page.

User Level rights include all of the above plus the ability to clear all alarms, reset the Operations Count and preset Contact Life.

Administrator Level rights include all of the above plus saving changes to passwords and program settings.

IP ADDRESS

The OPTImizer2 is capable of internet communication. A web browser can be used to “log on” to the OPTImizer2 either locally (with the short cable provided) or remotely through a network and perform all user interface functions. To access an OPTImizer2, its IP address is needed. A new OPTImizer2 is shipped with the default IP address of “192.12.27.1” As part of a network, the OPTImizer2 will need a different IP address.

To change the IP address, select the CONFIGURATION tab and click “EDIT”:

Program: IP Address = “nnn.nnn.nnn.nnn”

To change the passwords, select the CONFIGURATION tab and click “EDIT”:

Program: Administrator = “ABCdef123%^&…” Program: User = “ABCdefg123%^&…” Program: Guest = “ABCdefg123%^&…”

The correct (old) Administrator’s password will need to be given for the changes to be saved.

DATE / TIME

The date and time are needed for reference on the trip records and event history logging.

To change the date and time, select the CONFIGURATION tab and click “EDIT”:

Time Zone: The local time zone is selected from a pulldown list.

System Clock: The clock time and date can be manually entered using the pull-down lists or…

Time Server: The system clock can be set from an NTP server. The IP address of this server can be entered in the

blank eld.

DIAGNOSTICS

The OPTImizer2 is capable of sending diagnostic information to an IP address. This is used by INCON Technical Service to help in troubleshooting. It should be used only when instructed by an INCON Service Technician. The Technician will provide the IP address and further instructions. Always call the INCON Technical Service Division for assistance when troubleshooting a

problem. This Diagnostics utility may help in nding the

source of your problem.

DNP3.0 SETTINGS

The OPTImizer2 can communicate using the DNP3.0 protocol through its Ethernet port, RS-232 port or RS485 port, but only through one port at a time. Therefore, the DNP3.0 Mode must be selected. If TCP / IP mode is

selected, the TCP / IP port must be specied. If the RS-232

or RS-485 mode is selected, further serial port settings must be made.

To set up the DNP3.0 Mode, select the CONFIGURATION tab and click “EDIT”:

Local & Remote Addresses: The DNP3.0 Local and Remote Address numbers are manually entered in these

elds.

DNP3.0 Mode: The DNP3.0 Mode is selected from a pulldown list.

TCP / IP Port: The DNP3.0 TCP / IP Port is manually

entered in this eld.

Port Settings: The RS-232 & RS-485 Port Settings (Baud Rate, Data Bits, Parity, Stop Bits) are selected from pulldown lists.

Page 36

CIRCUIT BREAKER INFORMATION

The OPTImizer2 can store information about the circuit breaker in memory. This information is for reference only. It has no effect on functionality.

To enter Circuit Breaker Information, select the CONFIGURATION tab and click “EDIT”:

Program: Manufacturer = “ABCxyz123%^&…”

Program: Voltage Rating (KV) = “12345”

Program: Max. Interrupting Current (Amps) =

“1234567890”

4.3 Circuit Breaker Monitor Settings

The following settings are used by the OPTImizer2

specically for circuit breaker monitoring.

POWER SYSTEM FREQUENCY

The applied power line frequency is entered as 60 or 50 Hz.

Note: When the OPTImizer2 is cold-started, the Power

System Frequency parameter is set to 60Hz.

To set Power System Frequency, select the

CONFIGURATION tab and click “EDIT”:

Power System Frequency: The System Frequency is

selected from a pull-down list.

Program: Max. Operations Count = “1234567890”

BUSHING CT RATIO

Entering the applied CT ratio allows the OPTImizer2 to

reect Duty values to the primary base. Enter the applied CT

ratio to set the OPTImizer2 (Primary current to Secondary current).

Example:

Given: A CT of 1000:5 is applied for a given breaker.

Calculate: Primary Current / Secondary Current = CT Ratio

1000 / 5 = 200

CT Ratio = 200

To set Bushing CT Ratio, select the CONFIGURATION tab and click “EDIT”:

Program: Bushing CT Ratio = “200”

PICKUP COIL RATING

Entering the applied Pickup Coil Rating allows the OPTImizer2 to scale the input signal correctly for the

Pickup Coils being used.

Note: When the OPTImizer2 is cold-started, the Pickup

Coil Rating parameter is set to “160 Amps”.

Pickup Coil Rating: The Pickup Coil Rating is selected from a pull-down list.

Page 37

A INPUT POLARITY

(Aux A Input Assertion Level)

Entering the proper Aux A input assertion level allows the OPTImizer2 to properly start the mechanism time, arc

time, and duty wear logs. The OPTImizer2 reacts to a change in voltage state when the breaker is proceeding from the closed position to the open position. These are

dened to the OPTImizer2 as:

• No-voltage to voltage = “Positive”

• Voltage to no-voltage = “Negative”

Note: When the OPTI

Polarity parameter is set to “Positive”.

A Input Polarity: The A Input Polarity is selected from a pull-down list.

To determine the assertion level, reference is made to the following diagrams.

mizer

T/2T/1

is cold-started, the A Input

OPTImizer

Aux A

Input

• Trip Command - One of the trip initiate contacts

closes, shunting the red light and the Aux A input.

This causes high current to ow through the trip coil,

which begins to pull the latch. The Aux A input would sense a transition from voltage to no-voltage.

• Breaker Travel - As the breaker begins to travel, the

52 / a contact opens, effectively causing an open trip circuit. The Aux A input would still sense a novoltage condition (which will remain even after reset of the trip initiate contacts).

• Fully Opened - The 52 / a contact remains open,

effectively causing an open trip circuit. The Aux A input would continue to sense a no-voltage condition.

In summation, the OPTI with the trip initiates, should be set as:

• A Input Polarity = “Negative”

• INPUT MODE = “1” or “3”

mizer

, when applied in parallel

52/a

A Input Polarity = Negative

Closed Open

Figure 12: Aux A Interface, using Trip Initiate (Red Light)

This is an elementary diagram of a typical trip circuit. The elements T / 1 and T / 2 are trip-initiating contacts. These could be from protective relays, manual trip switches, SCADA contacts, etc. With the OPTImizer2 Aux A input wired in parallel with the trip initiates, (red light), the voltage levels sensed by the Aux A input during a trip operation would be as follows:

• Breaker Closed - The trip initiates are open, the red

light is lit, as the 52 / a contact is closed and a low current is passing through the trip coil. The Aux A input would sense voltage.

Page 38

T/2T/1

OPTImizer

52/a

Aux A Input

A Input Polarity

Figure 13: Aux A Interface, using 52 / a Contact in Trip Circuit

This is an elementary diagram of a typical trip circuit. The elements T / 1 and T / 2 are trip-initiating contacts. These could be from protective relays, manual trip switches, SCADA contacts, etc. With the OPTImizer2 Aux A input wired in parallel with the 52 / a contact in the trip circuit, the voltage levels sensed by the Aux A input during a trip operation would be as follows:

• Breaker Closed - The 52 / a contact is closed. The

Aux A input would sense a no-voltage condition, as the voltage to the input is shunted.

• Trip Command - One of the trip initiate contacts closes. This causes high current to ow through the

trip coil, which begins to pull the latch. The Aux A input would sense a no-voltage condition, with the 52 / a contact remaining closed, as the breaker has not yet begun to travel.

• Breaker Travel - As the breaker begins to travel, the 52 / a contact opens. The Aux A input would sense a transition from no-voltage to voltage.

• Fully Opened - The 52 / a contact remains open, and the Aux A input would continue to sense a voltage.

In summation, the OPTI with the 52 / a Contact in the trip circuit, should be set as:

mizer

= Positive

Closed Open

, when applied in parallel

52/a

A Input Polarity = Positive

Trip

Closed

Figure 14: Aux A Interface, using Trip Coil Excitation Voltage

This is an elementary diagram of a typical trip circuit. The elements T / 1 and T / 2 are trip-initiating contacts. These could be from protective relays, manual trip switches, SCADA contacts, etc. With the OPTImizer2 Aux A input wired in parallel with the Trip Coil in the trip circuit, the voltage levels sensed by the Aux A input during a trip operation would be as follows:

• Breaker Closed - The 52 / a contact is closed. The

Aux A input would sense a low-voltage condition, as the voltage dropped across the Trip Coil is minimal.

• Trip Command - One of the trip initiate contacts closes. This causes high current to ow through the

trip coil, which begins to pull the latch. The Aux A input would sense a high-voltage condition, with the 52 / a contact remaining closed, as the breaker has not yet begun to travel.

• Breaker Travel - As the breaker begins to travel, the 52 / a contact opens. The Aux A input would sense a transition from high-voltage to no-voltage.

• Fully Opened - The 52 / a contact remains open, and the Aux A input would continue to sense no voltage.

In summation, the OPTI with the Trip Coil in the trip circuit, should be set as:

• A Input Polarity = “Positive”

• INPUT MODE = “2” or “4”.

Open

mizer

, when applied in parallel

OPTImizer

Aux A Input

• A Input Polarity = “Positive”

• INPUT MODE = “1” or “3”.

Page 39

52/a

OPTImizer

Aux A Input

B INPUT POLARITY (Aux B Input Assertion Level) Entering the proper Aux B input assertion level allows the

OPTImizer2 to properly stop the mechanism time log. The OPTImizer2 reacts to a change in voltage state when the

breaker is proceeding from the closed position to the open position. These are dened to the OPTImizer2 as:

• No-voltage to voltage = “Positive”

• Voltage to no-voltage = “Negative”

Note: When the OPTImizer2 is cold-started, the B Input Polarity parameter is set to “Positive”.

B Input Polarity: The B Input Polarity is selected from a pull-down list.

A Input Polarity = Negative

Closed Open

Figure 15: Aux A Interface using Individually Wetted 52 / a

Contact

This is an elementary diagram of a typical trip circuit. With the OPTImizer2 Aux A input wired in series with an individually wetted SPARE 52 / a contact, the voltage levels sensed by the Aux A input during a trip operation would be as follows:

• Breaker Closed - The trip initiates are open, and

the 52 / a is closed. The Aux A input would sense voltage.

• Trip Command - One of the trip initiate contacts closes. This causes high current to ow through

the trip coil, which begins to pull the latch. The Aux A input would continue to sense a voltage, with the 52 / a contact remaining closed, as the breaker has not yet begun to travel.

• Breaker Travel - As the breaker begins to travel, the 52 / a contact opens. The Aux A input would sense a transition from voltage to no-voltage.

• Fully Opened - The 52 / a contact remains open, and the Aux A input would continue to sense a novoltage condition.

In summation, the OPTImizer2, when applied in series with an individually wetted 52 / a contact, should be set as:

• A Input Polarity = “Negative”

• INPUT MODE = “1” or “3”.

To determine the assertion level, refer to the following diagrams.

52/b

OPTImizer

B Input Polarity = Positive

Closed Open

Figure 16: Aux B Interface, using Green Light

This is an elementary diagram of a typical 52 / b contact / green light circuit. With the OPTImizer2 Aux B input wired in parallel with the green light, the voltage levels sensed by the Aux B input during a trip operation would be as follows:

• Breaker Closed - The 52 / b contact is opened. The

Aux B input would sense a no-voltage condition.

• Trip Command - One of the trip initiate contacts closes. This causes high current to ow through the

trip coil, which begins to pull the latch. The Aux B input would sense a no-voltage condition, with the 52 / b contact remaining opened, as the breaker has not yet begun to travel.

• Breaker Travel - As the breaker nears the end of travel, the 52 / b contact closes. The Aux B input would sense a transition from no-voltage to voltage.

• Fully Opened - The 52 / b contact remains closed, and the Aux B input would continue to sense a voltage.

Aux B Input

Page 40

In summation, the OPTImizer2, when applied in parallel with the green light, should be set as:

• B Input Polarity = “Positive”.

52/b

OPTImizer

Aux B Input

B Input Polarity = Negative

Closed Open

Figure 17: Aux B Interface, using 52 / b Contact in Green

Light Circuit

This is an elementary diagram of a typical 52 / b contact / green light circuit. With the OPTImizer2 Aux B input wired in parallel with the 52 / b contact in the breaker control circuit, the voltage levels sensed by the Aux B input during a trip operation would be as follows:

• Breaker Closed - The 52 / b contact is opened. The

Aux B input would sense a voltage from the low current circuit through the green light.

• Trip Command - One of the trip initiate contacts closes. This causes high current to ow through the

trip coil, which begins to pull the latch. The Aux B input would sense a voltage, with the 52 / b contact remaining opened, as the breaker has not yet begun to travel.

• Breaker Travel - As the breaker nears the end of travel, the 52 / b contact closes. The Aux B input would sense a transition from voltage to no-voltage, as the voltage to the Aux B input is shunted.

• Fully Opened - The 52 / b contact remains closed, and the Aux B input would continue to sense a novoltage condition.

OPTImizer

Aux B Input

B Input Polarity = Positive

Closed Open

Figure 18: Aux B Interface, using Individually Wetted 52 / b

Contact

This is an elementary diagram of an individually wetted SPARE 52 / b contact. With the OPTImizer2 Aux B input wired in series with this contact, the voltage levels sensed by the Aux B input during a trip operation would be as follows:

• Breaker Closed - The 52 / b contact is opened. The

Aux B input would sense a no-voltage condition.

• Trip Command - One of the trip initiate contacts closes. This causes high current to ow through the

trip coil, which begins to pull the latch. The Aux B input would sense a no-voltage condition, with the 52 / b contact remaining opened, as the breaker has not yet begun to travel.

• Breaker Travel - As the breaker nears the end of travel, the 52 / b contact closes. The Aux B input would sense a transition from no-voltage to voltage.

• Fully opened - The 52 / b contact remains closed, and the Aux B input would continue to sense a voltage.

In summation, the OPTI individually wetted contact, should be set as:

• B Input Polarity = “Positive”.

mizer

, when applied to an

In summation, the OPTI with the 52 / b contact, should be set as:

• B Input Polarity = “Negative”.

mizer

, when applied in parallel

Page 41

Input Mode

Entering the Input Mode, in combination with the A Input Polarity and B Input Polarity, allows The OPTImizer2 to monitor the circuit breaker control circuit’s logic states in the closed and open positions. The Input Mode also governs whether or not Trip Time, Clearing Time, Travel Time and Closing Time are measured.

If the B Input is not wired, Input Modes 2 or 3 must be used, depending upon the wiring of the A Input. Mode 3 is used when the A Input signal is a continuous source, as shown in Figures 12, 13 and 15. Mode 2 is used when the A Input signal is a momentary (pulse) source, as shown in Figure 14.

If the A Input is wired as shown in Figures 12, 13 or 15, then Input Modes 1 or 3 must be used, depending upon the wiring of the B Input: Mode 1 is used when the B Input is wired. Mode 3 is used when the B Input is not wired.

If the A Input is wired across the trip coil, as shown in Figure 14, then Input Modes 2 or 4 must be used, depending upon the wiring of the B Input: Mode 2 is used when the B Input is not wired. Mode 4 is used when the B Input is wired.

To set the Input Mode, select the CONFIGURATION tab and click “EDIT”:

The Input Mode is selected from a pull-down list.

Mode 1 = Continuous A Signal with Continuous B Signal

Mode 2 = Momentary A Signal, No B Signal

Mode 3 = Continuous A Signal, No B Signal

Mode 4 = Momentary A Signal with Continuous B Signal

A Input Delay

(Time Difference between Aux A Input Assertion and Parting of Main Contacts)

Entering the A Input Delay setting allows the OPTImizer2 to accurately time the arcs, and calculate Contact Wear values during the arcing intervals. This Delay setting impacts the starting of the arc time log and the Contact Wear logs to align with the parting of the main contacts.

To set the A Input Delay, select the CONFIGURATION tab and click “EDIT”:

Program: A Input Delay = “-19”

• To account for an Aux A input assertion that occurs

before the main contacts part, use a positive (+) value for the A Input Delay setting. Example: Aux A assertion occurs 24 mS before the main contacts part, A Input Delay = “+24”

• To account for an Aux A input assertion that occurs

after the main contacts part, use a negative (-) value for the A Input Delay setting. Example: Aux A assertion occurs 19 mS after the main contacts part, A Input Delay = “-19”

Figure 19: Trip Trace illustrating A Input Delay Setting Considerations

Page 42

Depending on what is being used to assert the Aux A input, there are multiple methods available to derive the A Input Delay setting value.

A Input Assertion Methods to Derive A INPUT DELAY Setting

• Use breaker trip trace, A Input Delay setting is the time difference between

Parallel connection to “Red

Light” or trip initiate contacts

the trip initiate signal and the parting of the main contacts

• Use ANSI C37.06 to approximate latch release times based on kV level of breaker if a breaker trip trace is unavailable

• Use breaker trip trace, A Input Delay setting is the time difference between the opening of the 52 / a contact and the parting of the main contacts

Parallel connection to 52 / a

contact in breaker trip circuit

• Use breaker operation time line provided by the manufacturer in Instruction literature, provided the 52 / a contact has not been adjusted from the manufacturer

• Use breaker trip trace, A Input Delay setting is the time difference between the opening of the 52 / a contact and the parting of the main contacts

3 Parallel connection to Trip Coil

• Use breaker operation time line provided by the manufacturer in Instruction literature, provided the 52 / a contact has not been adjusted from the manufacturer

• Use breaker trip trace, A Input Delay setting is the time difference between

Series connection to wetted

52 / a contact not in breaker trip circuit

the opening of the 52 / a contact and the parting of the main contacts

• Use breaker operation time line provided by the manufacturer in Instruction literature, provided the 52 / a contact has not been adjusted from the manufacturer

Use of auxiliary relay in

conjunction with method 1

Use of another input that

indexes the trip initiate contacts

• Same as method 1, but the delay in pick-up or drop out of the auxiliary relay (depending on application) must be added or subtracted from the A Input Delay time setting

• Same as method 1, but the delay in pick-up or drop out of the initiating input (depending on application) must be added or subtracted from the A Input

Delay time setting

Table 5: Impact of A Input Assertion on the A Input Delay Setting

Page 43

Use of ANSI / IEEE C37.06-1989, Rating of Power Circuit Breakers under a Symmetrical Fault Basis

ANSI / IEEE C37.06-1989 can provide guidance for the time of latch release and the duration of arcs for power circuit breakers. The latch release time is approximately the same time value as the main contacts parting, which is required for the A Input Delay setting. This standard addresses power circuit breakers with voltage ratings

from 13 kV to in excess of 500 kV. To be qualied as an

ANSI rated breaker, which most utilities use, the following performance criteria must be met under symmetrical fault conditions:

MUST cLeAR TIMe

Breaker Voltage

<230kV

>230kV

Table 6: Must-Clear Times of Breakers, Voltage Dependent

Note: Pre-1989 breakers may not conform to this

standard. Always use manufacturers data or oscillographic data if available.

(TRIp INITIATe TO ARc

exTINgUIShMeNTS)

3 cycles at 60Hz

2 cycles at 60Hz

Contact Wear Mode

The OPTImizer2 can be programmed to use one of two available Contact Wear modes, I x T or I 2T. In I 2T

mode, the square of the current measurement is used in

calculating contact wear units.

Note: When the OPTImizer2 is cold-started, the Contact Wear Mode is set to “I 2T”.

To set the Contact Wear Mode, select the CONFIGURATION tab and click “EDIT”: The Contact Wear Mode is selected from a pull-down list.

Contact Life Danger Limit

The Contact Life Danger Limit is the alarm setpoint for cumulative I x T or I 2T duty. This limit is usually correlated to the ultimate wear-out of the contacts. Breaker manufacturers typically provide nameplate data that supplies enough information to calculate the Contact Life limit. Some breaker

nameplates do not supply all of the information required,

however, ANSI C37.06-1989 provides guidelines that can

assist in deriving ultimate duty wear estimates. The equation

used is:

Danger Limit = (NF) I (squared for I 2T) • T, where

• NF is the rated number of fault interruptions,

•I is the full rated fault current (Amps RMS symmetrical)

•T is the arc time of the breaker.

Notice that it is only the arc time that is used in the calculation, and not the total clearing time. The arc time is used because it is during the arc interval that the heating takes place, which degrades the breaker. During the current carrying phase of clearing a fault, no arcing, and therefore no heating takes place. The current carrying interval from trip initiate to main contacts parting should not be included in the wear limit calculation.

Figure 20: Estimated Trip Latch Release Times based on

Nameplate Breaker Voltage

Based on these limits, and using the assumption that breakers are designed to clear a fault faster as the applied voltage increases; the following timing graph is based on ANSI C37.06-1989 for latch release times. These approximations should be helpful to determine the A INPUT DELAY setting when a time trace is unavailable, and the

OPTImizer2 is being applied with the trip initiates (red light)

for the Aux A input assertion. These approximations may also have use if the 52 / a contact of the breaker is being used for the Aux A assertion, however, the time interval from the trip initiate signal to the 52 / a contact opening must be known. The breaker manufactures instruction literature or original factory trip trace will provide useful information.

The required nameplate data are:

• Full fault (symmetrical) current capability (I). If this

value is not available, or if the breaker is rated in MVA, see Incomplete Nameplate Data, addressed later in this section.

• Number of times breaker can interrupt full fault

(symmetrical) current (N

). If this value is not

available, see Incomplete Nameplate Data, addressed later in this section.

• The rated voltage of the breaker.

To arrive at the arc duration time of the breaker, which is used for T, several methods may be used:

• Viewing of a recent oscillographic record of the

breaker clearing, noting the time from main contacts parting to arc extinguishments, all phases.

• Using ANSI / IEEE C37.06-1989 as a guideline to

arrive at an arc duration estimate (see ANSI / IEEE C37.06-1989, Figure 15, and Appendix B).

Note:

When the OPTImizer2 is cold-started, the Danger Limit parameter is set to 0.1

Page 44

Arc Duration (mS)

Breaker Voltage (kV)

50 100 150 200 250 300 350 400 450 500

Figure 21: Estimated Arc Time based on Nameplate Breaker

Voltage

Example:

Given: Breaker is rated at 69kV, 30kA fault interrupt

(RMS symmetrical), and it can withstand 5 operations at fault interrupt current.

Assume: 69kV breaker has an arc duration of 24mS

(0.024s).

Calculate: Danger Limit = (NF ) I2 T

Danger Limit = (5) (30kA)2 (0.024s) Danger Limit = 108,000,000 A2S

Danger Limit = 1.1 x 108 A2S

Note: The answer is expressed in amp2-seconds (A2S),

converted to scientic notation, base 10, rounded to two signicant digits.

Incomplete Nameplate Data

There are occasions when the breaker nameplate data does not state how many full-rated faults (symmetrical) the breaker can withstand. For those instances, to arrive at an estimate of the full-rated fault operations capability, use the number of rated load current operations a breaker

can withstand and employ the equation NF = (NL IL) / IF,

where NF is the number of fault current operations, NL is the number of rated load breaker operations, IL is the rated load breaker current, and IF is the full-rated fault current.

ANSI / IEEE C37.06-1989 states that all outdoor circuit breakers, all voltages, must be able to undergo 100 trip operations at rated load interruption before an inspection of the contacts is warranted.

Example:

Given: Breaker is rated at 69kV, 20kA fault interrupt

(symmetrical), 1200A rated load break. No information is given on the number of fault rated interruptions.

Assume: 69kV breakers have an arc duration T of 24mS

(0.024s). 69kV breaker can withstand 100 rated load break operations, NL, before an inspection

(ANSI / IEEE C37.06-1989).

Calculate: NF = (N

IL) / IF

NF = (100) (1200A) / 20kA NF = 6

Danger Limit = (NF ) I

x T Danger Limit = (6) (20kA)2 (0.024s) Danger Limit = 57,600,000 A2s

Danger Limit = 5.76 x 107 A2s

Note: The answer is expressed in amp2-seconds (A2s),

converted to scientic notation, base 10.

To set the Contact Life Danger Limit, select the CONFIGURATION tab and click “EDIT”:

Program: Contact Life Danger Limit = “5.76e7”

If breaker is Rated in MVA, not kA, or is being Applied at Voltage other than Nameplate:

There are occasions when the breaker is rated in MVA at a given voltage. No kA value is available. To arrive at kA maximum rated fault (symmetrical) current, it is necessary to convert the MVA to kA on the voltage base. Employ the

equation IL = S3 / √3 (VLL) to derive single phase current,

where IL is the individual phase current in kA, S

is the three

3

phase power in MVA, and VLL is the line-to-line voltage in kV.

Example:

Given: Breaker is rated at 69kV, 2,500 MVA

interrupting duty

Breaker is to be applied at 69kV.

Calculate: IL = S3 / √3 (VLL),

IL = 2,500 MVA / 69kV √3

IL = 20.943kA, or approximately 21kA

Danger Limit = (NF ) I2 x T

Danger Limit = (100) (21kA) 2 (0.024s)

Danger Limit = 10,584,000,000 A2s

Danger Limit = 1.06 x 1010 A2s

Program: Contact Life Danger Limit = “1.06e10”

Page 45

If breaker is Rated in MVA, and is being Applied at Voltage other than Nameplate:

There are occasions when the breaker is rated in MVA at a given voltage, and the breaker is being applied at a different voltage. No kA value is available. To calculate kA maximum rated symmetrical fault current from MVA, use

= S

the equation I

current, where IL is the individual phase current in kA, S is the three phase power in MVA, and VLL is the line-to-line

voltage in kV.

Example:

Given: Breaker is rated at 38kV, 1,200 MVA

interrupting duty.

Breaker is to be applied at 34kV.

/ √3 (VLL) to derive single phase

3

Set at One Fault Rated Interruption less than the Danger

Limit

Setting the Warning Limit at one fault interruption operation allows a Warning alarm to be issued before another fault takes place and brings the breaker cumulative I2 x T

to the Danger Limit. Use the equation Warning Limit =

1 / NF , where NF is the maximum number of fault rated interruptions.

Example:

Given: Breaker DANGER setpoint has been determined

to be (6.4) 10

A2s and it can withstand 15

operations at fault interrupt current

Calculate: Warning Limit = 1 / N

Warning Limit = 1 /15]

Calculate: IL = S3 / √3 (VLL),

IL = 1,200 MVA / 34kV √3

IL = 20.401kA, or approximately 20kA

Danger Limit = (NF ) I2 x T

Danger Limit = (100) (20kA)2 (0.024s)

Danger Limit = 9,600,000,000 A2s

Danger Limit = 9.6 x 109 A2s

Program: Contact Life Danger Limit = “9.6e9”

Contact Life Warning Limit

The Contact Life Warning Limit is the warning setpoint for cumulative I x T or I 2T duty. The intent of this setpoint is to allow the generation of a warning alarm prior to ultimate contact wear (Danger Limit). Accordingly, when used in this mode it is set at a fraction of the Danger Limit setpoint.

Note: When the OPTImizer2 is cold-started, the Warning

Limit parameter is set to ZERO, which disables this alarm.

Set at an Arbitrary Percentage of the Danger Limit

To set the WARNING setpoint at an arbitrary percentage of the DANGER setpoint simply use the WARNING command followed by the percentage value.

Example:

Given: Breaker Danger Limit setpoint has been determined

to be (6.4) 106 A2S.

To set the Warning Limit to 30% of the Danger

limit…

Program: Contact Life Warning Limit(%) = “30”

The OPTI

calculate the Warning Limit I2 x T.

mizer

will automatically

Warning Limit = 0.067 or 6.7%, round to 7%

To set the Contact Life Warning Limit, select the CONFIGURATION tab and click “EDIT”:

Program: Contact Life Warning Limit(%) = “7”

(The OPTImizer2 will automatically calculate the Warning Limit I2 x T.)

There is no guidance from standards on the following issues, so Alarm Limit selection is for the applying company to decide.

The correct Administrator’s password is needed for these settings to be saved.

Trip Time Alarm Limit

The OPTImizer2 will measure the response time of the trip latch mechanism, if programmed for Input Modes 2 or 4. A Trip Time Alarm Limit can be programmed in milliseconds. When the measured Trip Time reaches or exceeds this Alarm Limit an alarm will be asserted.

It is recommended that this limit be set for 25% to 35% above the typical trip latch response time to reduce nuisance alarms.

Note: When the OPTImizer2 is cold-started, the Trip

Time Alarm Limit parameter is set to ZERO, which disables this alarm.

To set the Trip Time Alarm Limit, select the CONFIGURATION tab and click “EDIT”:

Program: Trip Time Alarm Limit = “13”

Page 46

Arc Time Alarm Limit

The OPTImizer2 will measure the duration of the fault arcs as the interrupter contacts separate. An Arc Time Alarm Limit can be programmed in milliseconds. When the measured Arc Times reach or exceed this Alarm Limit an alarm will be asserted.

Travel Time Alarm Limit

The OPTImizer2 will measure the time between the opening of the 52a switch and the closing of the 52b switch, if programmed for Input Modes 1 or 4. A Travel Time Alarm Limit can be programmed in milliseconds. When the measured Travel Time reaches or exceeds this Alarm Limit an alarm will be asserted.

It is recommended that this limit be set for 25% to 35% above the typical arc duration time (see Figure 21 for suggested typical arc times) to reduce nuisance alarms.

Note: When the OPTImizer2 is cold-started, the Arc

Time Alarm Limit parameter is set to ZERO, which disables this alarm.

To set the Arc Time Alarm Limit, select the CONFIGURATION tab and click “EDIT”:

Program: Arc Time Alarm Limit = “42”

Clearing Time Alarm Limit

The OPTImizer2 will measure the combined time of the trip latch mechanism and arc duration, if programmed for Input Modes 2 or 4. A Clearing Time Alarm Limit can be programmed in milliseconds. When the measured Clearing Times reach or exceed this Alarm Limit an alarm will be asserted.

Good practice is to set this limit for 25% to 35% above the typical fault clearing time to reduce nuisance alarms. We recommend that the sum of the Trip Time and Arc Time alarm limits be used as the Clearing Time Alarm Limit.

Note: When the OPTImizer2 is cold-started, the Clearing

Time Alarm Limit parameter is set to ZERO, which disables this alarm.

To set the Clearing Time Alarm Limit, select the CONFIGURATION tab and click “EDIT”:

It is recommended that this limit be set for 25% to 35% above the typical breaker opening time to reduce nuisance alarms.

Note: When the OPTI

Time Alarm Limit parameter is set to ZERO, which disables this alarm.

To set the Travel Time Alarm Limit, select the CONFIGURATION tab and click “EDIT”:

Program: Travel Time Alarm Limit = “75”

mizer

is cold-started, the Travel

Closing Time Alarm Limit

The OPTImizer2 will measure the time between the opening of the 52b switch and the closing of the 52a switch, if programmed for Input Mode 1 only. A Closing Time Alarm Limit can be programmed in milliseconds. When the measured Closing Time reaches or exceeds this Alarm Limit an alarm will be asserted.

Good practice is to set this limit for 25% to 35% above the typical breaker closing time to reduce nuisance alarms.

Note: When the OPTImizer2 is cold-started, the Closing

Time Alarm Limit parameter is set to ZERO, which disables this alarm.

To set the Closing Time Alarm Limit, select the CONFIGURATION tab and click “EDIT”:

Program: Closing Time Alarm Limit = “105”

Program: Clearing Time Alarm Limit = “55”

Page 47

Operations Count Alarm Limit

The OPTImizer2 will increment a counter with each circuit breaker trip operation. An Operations Count Alarm Limit may be set to turn on the Operations LED and close the Yellow relay when the breaker has reached a certain number of operations. This Alarm Limit is different than the Operations Number. The Alarm Limit may be set for a small number of operations and counter may be reset several times over the life of the breaker (like a trip odometer in a car), while the Operations Number will continue to increment for the life of the breaker (like a car’s main odometer).

The Operations Count Alarm can be used to alert maintenance staff to perform maintenance that is

recommended after a specic number of operations. Once

the maintenance is done, the Operations Counter can be

reset, and the alarm will recur when the specic number

of operations is reached again. When the OPTImizer2 is cold started, the Operations Count Alarm Limit parameter is set to ZERO, which disables this alarm.

Restrike Alarm

The ability to detect restrikes is important, especially for gas (SF

The following gure illustrates how the OPTImizer2

perceives typical arcs and restrikes. The OPTI sampling the phase-segregated waveforms at 32 times per line cycle.

The Restrike Alarm may be enabled or disabled.

If enabled, the rst detection of a restrike will assert the

Restrike Alarm, turning on the Restrike LED and energizing the Red relay. A time-stamped record of the alarm will be recorded in the history log. The Restrike Alarm may be reset, opening the relay and turning off the LED. The record of the alarm will remain in the history log even if the alarm is reset.

Note: When the OPTImizer2 is cold-started, the Restrike

) breakers.

Alarm parameter is set to “Disabled”.

mizer

To set the Operations Count Alarm Limit, select the CONFIGURATION tab and click “EDIT”:

Program: Operations Count Alarm Limit = “75”

No Operations Alarm Limit

The OPTImizer2 will count the number of days since the last trip operation. A No Operations Alarm Limit can be programmed in days. When the number of days since the last trip operation reaches or exceeds this Alarm Limit an alarm will be asserted.

This limit should be set according to the breaker manufacturer’s recommendations.

Note: When the OPTImizer2 is cold-started, the No

Operations Alarm Limit parameter is set to ZERO, which disables this alarm.

To set the No Operations Alarm Limit, select the CONFIGURATION tab and click “EDIT”:

To set the Restrike Alarm, select the CONFIGURATION tab and click “EDIT”:

Program: Restrike Alarm = “Enabled”

Program: No Operations Alarm Limit = “90”

Page 48

Arc Time = 3 Cycles

Arc begins here

Restrike not detected

Possible total arc duration = 10 cycles

Figure 22A: A 3-Cycle Arc, No Restrike

Arc Time = 5.5 Cycles Restrike not detected

Possible total arc duration = 10 cycles

Figure 22B, A 5½-Cycle Arc, No Restrike

Less than ¼ cycle

Arc Time = 5.5 Cycles Restrike detected

More than ¼ cycle

Possible total arc duration = 10 cycles

Figure 22C, A 5½-Cycle Arc, Restrike Detected

Page 49

4.4 SF6 MONITOR SETTINGS

The following settings are used by the OPTImizer2

specically for SF6 monitoring.

• SF6 Monitoring Units: Density; Pressure

• Pressure Units: PSI; BAR; Kilopascals

• Temperature Units: Celsius; Fahrenheit

• Volume Units: Cubic Feet; Liters; Cubic Meters

• Mass Units: Pounds; Kilograms

• Mass Loss Units: Pounds; Kilograms; Pounds CO

Metric Tonnes CO

• Breaker Nameplate SF6 Gas Fill Weight (mass), in the

chosen units:________

• Breaker Nameplate SF

Fill Pressure, in the chosen

units:________

• Rated Temperature, in the chosen units:________

Volume (optional), in the chosen units:________

• SF

Low Gas Warning Limit

As the OPTImizer2 monitors the SF6 density or pressure, an alarm will be asserted when the density or pressure reaches or falls below the programmed Low Gas Warning Limit.

The Low Gas Warning Limit can be set to the circuit

breaker manufacturer’s “Alarm Limit” specication. If

the OPTImizer2 is used in conjunction with an electromechanical SF6 monitoring device, this Warning Limit can be set higher than the manufacturer’s “Alarm Limit”

specication to provide an “early warning” that SF6 density

or pressure is getting low.

Note: When the OPTImizer2 is cold-started, the Low

Gas Warning Limit parameter is set to ZERO, which disables this alarm.

To set the Low Gas Warning Limit, select the CONFIGURATION tab and click “EDIT”:

Program: Low Pressure Warning Limit = “76”

Low Density Warning Limit = "39.8"

;

Low Gas Alarm Limit

An alarm will be asserted when the density or pressure reaches or falls below the programmed Low Gas Alarm Limit.

The Low Gas Alarm Limit can be set to the circuit

breaker manufacturer’s “Lock-Out Limit” specication. If

the OPTImizer2 is used in conjunction with an electromechanical gas monitoring device, this Alarm Limit can be set higher than the manufacturer’s “Lock-Out Limit”

specication to provide an “early warning” that a Lock-Out

is imminent.

Note: When the OPTImizer2 is cold-started, the Low

Gas Alarm Limit parameter is set to ZERO, which disables this alarm.

To set the Low Gas Alarm Limit, select the CONFIGURATION tab and click “EDIT”:

Program: Low Pressure Alarm Limit = “72”

Low Density Alarm Limit = "38.2"

Density or Pressure Trend Limit

The OPTImizer2 will analyze the SF6 density and pressure

uctuations over a 15 day period and calculate the Density

and Pressure Trends once an hour. The magnitude of these trends indicate whether the SF6 density and pressure are stable or decreasing. The Density Trend is expressed in grams-per-liter-per-day (g / L / d). The Pressure Trend is expressed in the chosen units-per-day. They are shown as negative numbers in the Status, if there is a loss of gas. The Trend Limit is programmed as a positive number.

An alarm will be asserted when the magnitude of the trend is the same or greater than the programmed Trend Limit.

Note: When the OPTImizer2 is cold-started, the Trend

Alarm Limit parameter is set to ZERO, which disables this alarm.

To set the Trend Alarm Limit, select the CONFIGURATION tab and click “EDIT”:

Program: Density Trend Alarm Limit = “0.03”

Pressure Trend Alarm Limit = "0.3"

Page 50

SF6 Sensor Signals

The OPTImizer2 can monitor the signal from two types of SF6 density sensor:

Analog Sensors with an output current signal within

the range of 4mA and 20mA

Analog Sensor - Signal Low Represents

(Units)

Each SF6 input on the OPTImizer2 can be programmed to scale the analog Signal Low (programmed above) to a grams per liter value that may be something other than zero.

Digital Sensors with a special frequency & pulse-

width-modulated signal (INCON DSDP)

Each of the three input channels can be separately programmed for an Analog or Digital sensor or disabled (Off). If the SF6 Sensor Signal chosen is “Analog”, four

more parameter elds will appear for that sensor (see

below).

Note: When the sensor signal chosen is "Analog", the

chosen units cannot be "Pressure".

Note: When the OPTImizer2 is cold-started, the SF6

Sensor Signal parameters are all set to “Off”, which disables the inputs.

To set the SF6 Sensor Signals, select the CONFIGURATION tab and click “EDIT”:

Under the headings “SF6 Sensor A”, “SF6 Sensor B”, “SF6 Sensor C”:

Program: Signal = “Digital”

Signal = “Analog”

Note: When the OPTImizer2 is cold-started, the Signal

Low Represents parameter is set to 0.0 g / L.

To set the Signal Low Represents parameter, select the CONFIGURATION tab and click “EDIT”:

Under the headings “SF6 Sensor A”, “SF6 Sensor B”, “SF6 Sensor C”:

Program: Signal Low Represents (g / L) = “10.0”

Analog Sensor - Signal High (Milliamps)

Each SF6 input on the OPTImizer2 can be programmed to monitor an analog signal with a high scale that may be something other than 20mA.

Note: When the OPTI

High parameter is set to 20.0mA.

Note: If the measured sensor signal is higher than the

programmed Signal High value, a “Sensor Signal Out of Range” alarm will be asserted.

To set the Signal High parameter, select the CONFIGURATION tab and click “EDIT”:

mizer

is cold-started, the Signal

Analog Sensor - Signal Low (Milliamps)

Each SF6 input on the OPTImizer2 can be programmed to monitor an analog signal with a low scale that may be something other than 4mA. For example, some sensors have a working range of 6.5 to 20mA.

Note: When the OPTImizer2 is cold-started, the Signal

Low parameter is set to 4.0mA.

Note: If the measured sensor signal is lower than the

programmed Signal Low value, a “Sensor Signal Out of Range” alarm will be asserted.

To set the Signal Low parameter, select the CONFIGURATION tab and click “EDIT”:

Under the headings “SF6 Sensor A”, “SF6 Sensor B”, “SF6 Sensor C”:

Program: Signal Low (mA) = “6.5”

Under the headings “SF6 Sensor A”, “SF6 Sensor B”, “SF6 Sensor C”:

Program: Signal High (mA) = “16.0”

Analog Sensor - Signal High Represents

(Units)

Each SF6 input on the OPTImizer2 can be programmed to scale the analog Signal High (programmed above) to a grams per liter value.

Note: When the OPTImizer2 is cold-started, the Signal

High Represents parameter is set to 400.0 g / L.

To set the Signal High Represents parameter, select the CONFIGURATION tab and click “EDIT”:

Under the headings “SF6 Sensor A”, “SF6 Sensor B”, “SF6 Sensor C”:

Program: Signal High Represents (g / L) = “70.0”

Page 51

4.5 ACTIONS

An “Action” is taken in response to an alarm or maintenance activity. Actions include clearing active alarms; resetting data; resetting the operations counter; pre-setting the remaining contact life percentage and presetting the operation number. The OPTImizer2 allows these things to be done from the “ACTION” tab of the user interface (see Figure 10).

Preset Remaining Contact Life

The ability to preset the remaining contact life as a percentage of the Danger Limit for each phase allows the

OPTImizer2 to account for any interrupting duty wear that

has occurred prior to installation. This issue may be divided into two general categories:

• New breakers, or breakers that have been

recently refurbished, have essentially 100 percent life remaining on one or more of the contacts.

Refurbished is dened here as replaced contacts, oil and grids (bafes) in OCBs, and replaced contacts

and gas cleaning in SF6 breakers, or contact and

bafe replacement in magblast air breakers.

• Existing breakers that have not had recent

maintenance (refurbishment)

There are two processes for estimating the percentage of remaining contact life for existing breakers that have not been recently maintained:

• Experience based on eld engineers / technicians

who can evaluate the condition of contacts and rate a percent of life lost, or percent of life remaining.

• Calculation from trip duty records from

Oscillographs, relays with Oscillographic capabilities, relay target logs.

Experience Method of presetting Remaining Contact Life per phase

A breaker may have been recently inspected by a eld

engineer / technician whose expert knowledge of breaker wear characteristics may allow declaration of a percent of life remaining on contacts.

Calculation Method of presetting Remaining Contact

Life

In the calculation method, an attempt is made to

quantify the cumulative currents interrupted since the

last refurbishing of each phase of the breaker. This

quantication would include the summation of fault

operations and load breaks. (No-load breaks would be of

no consequence to the wear duty of the breaker.)

The general method is to add the total I² x T (or I x T) from all fault operations to the total I² x T (or I x T) from all load

breaks for each phase. The equation used is similar to the

one used to derive the Danger Limit value, except that the variables represent individual operations.

Use the equation WN = IN² T to determine Duty Wear for

each operation, where “W” is the Duty Wear, “N” is the operation number, IN is the current interrupted for that

operation (squared if using the I² x T mode), and T is the

arc duration time of the breaker. Determining the time (T) is discussed in the Danger Limit calculation, addressed earlier in this section.

The summation of all interrupting duty (WN’s) for a

particular phase is used to arrive at a nal accumulated

Duty Wear value for that phase. Divide this calculated Duty Wear by the Danger Limit to get the accumulated Duty Wear percentage. Subtract this percentage value from 100 to get the Remaining Contact Life percentage. This percentage value is programmed as the Preset Remaining Contact Life for this phase.

It may be difcult to obtain exact interrupted amps for each

and every operation. In these cases, some assumptions must be made to arrive at an estimated setting. Possible information sources may be from protective relay targets. By examining the settings that relate to the targets, estimates of the fault current may be obtained.

Lacking precise targets, by separating the operations into fault operations and load break operations, some assumptions can be made. One assumption may be

that load breaks equal ½ the maximum load the breaker

is subjected to, and fault operations are some factor of expected short circuit ground current, or phase-to-phase current.

As the great majority of fault incidences are phase-toground, some factor relating to the expected ground short circuit current can be made. The factors applied would depend on knowledge of the relative fault currents that have been recorded on the line to the short circuit ground fault current assuming zero ground fault impedance. System Protection and Operations personnel are helpful sources for obtaining data for estimating the accumulated Duty Wear if hard data is not available.

Page 52

Example for Calculating Accumulated Duty Wear

Given: A breaker has operated 8 times since the last

refurbishing. The breaker is a 38 kV breaker. The Danger Limit is calculated to be 2.5e+07 I2 x T.

Assume: Equation used for accumulated I2 T is:

∑ WN = (IN)2 T

Arc duration time of a 69kV breaker is 24mS (0.024s), per explanation under Danger Limit calculation derived earlier in this section.

Clear Latched Alarms

When an alarm occurs, an LED will be lit to give a general indication of what has caused the alarm. Table 4 gives a listing of which LED is lit for each alarm. Some of the LED’s can indicate a number of different alarms. To know

specically what alarm is active when an LED is lit, browse

to the Status page. A complete listing of all alarms is shown with the status of each. Some "ALARM" indications are hyper-links to the ACTION tab, where the alarm can be cleared.

It has been determined by examination of Operations records that the history was:

Trip #

1 Fault 5,000 600,000 6.0 E+05

2 Fault 4,000 384,000 3.8 E+05

3 Load Break 800 15,360 1.5 E+04

4 Fault 15,000 5,400,000 5.4 E+06

5 Load Break 400 3,840 3.8 E+03

6 Fault 5,000 600,000 6.0 E+05

7 Fault 6,000 864,000 8.6 E+05

8 Load Break 200 960 9.6 E +02

Table 7: Accumulated Duty Wear Calculation Example based

Divide 7.9 e+06 by 2.5 e+07 to determine Contact Wear percentage = 31.6 Subtract 31.6 from 100 to determine Preset Remaining Contact Life percentage = 68.4

To preset the remaining contact life for a phase, select the

ACTION tab and click “Preset Remaining Contact Life Phase (A, B or C)”. A yellow bar will appear at the top of the window. Type the desired remaining contact life percentage

into the eld (The acceptable range is -50 to +100).

Type of

Clearing

Approx.

Interrupt

Current

on Trip History

I2 x T

(decimal)

I2 x T

(Notation)

Preset Operation Number

The OPTImizer2 will assign an operation number that is increased by one with each circuit breaker trip operation. Normally this count will start at “1”. The operation number may be preset to a number other than “1”. This allows the

OPTImizer2 to indicate the same operation number as the

counter on the circuit breaker. The OPTImizer2 will count to a maximum of 9999 operations before “rolling over” to

0000. The operation number will continue to increment after “rolling over”.

On the action page, certain active alarms can be cleared and others cannot. “Latched Alarms” can be cleared because they are not tied to accumulated or persistent

data. “Persistent Alarms” cannot be cleared without rst

addressing the cause of the problem, altering the alarm limit or resetting the data. The No Operations Alarm cannot be cleared directly. It will automatically clear upon the next circuit breaker trip operation. Raising the No Operations Alarm Limit will also clear that alarm.

Latched Alarms include: Trip Time; Travel Time; Closing Time; Restrike; Excess Arc and Clearing Time. These alarms can only be cleared by clicking the “Clear Latched Alarms” button or using the USB Alarm Clearing script. These alarms can NOT be cleared by altering their alarm limit.

Persistent Alarms include: A-B LOGIC; No Operations; Operations Count; Remaining Contact Life Warning; Remaining Contact Life Danger; Low Density; Density Trend and Sensor Malfunction. These alarms cannot be

cleared without rst addressing the cause of the problem,

altering the alarm limit or resetting the data.

To Clear Latched Alarms, select the ACTION tab and click

“Clear Latched Alarms”. A yellow bar will appear at the top

of the window. Click "Yes" to conrm.

Reset Operations Counter

When an Operations Count Alarm occurs, it can be cleared by either increasing the Operations Count Alarm Limit on the CONFIGURATION tab, or by resetting the counter. This action will zero the counter.

To reset the operation counter, select the ACTION tab and

click “Reset Operations Counter”. A yellow bar will appear

at the top of the window. Click "Yes" to conrm.

To preset the operation number, select the ACTION tab and

click “Preset Operation Number”. A yellow bar will appear at the top of the window. Type the desired operation number

into the eld. Click "Yes" to conrm.

Page 53

Reset SF6 Density Trend Data

If an SF6 density sensor is found to be faulty, the SF6 Trend calculation should be re-started after replacing the sensor. This can be done by resetting the accumulated SF6 data for that channel. When this action is taken, a new array of data will be accumulated and a new SF6 Trend will be calculated for that channel. Until there is a full array of data

to calculate the new Trend, the Condence Level for that

channel will indicate less than 100%.

To reset the SF6 Trend Data for a channel, select the

ACTION tab and click “Reset Channel A, B or C”. A yellow bar will appear at the top of the window.

Click “YES” to conrm the action. The correct

Administrator’s password will need to be given for the change to be saved. Click “Apply” to complete the action.

Trend Data and Alarm

Page 54

5 User Interface

There are ve general interface activities with the

OPTImizer2:

1. Initial Conguration

2. Post Maintenance Resetting / Presetting

3. Periodic Data dump

4. Alarm Acknowledgment / Cancellation

5. Archiving and Exporting Data to a PC

The following are typical steps for each of the preceding major interface activities. The order of the tasks have been arranged to allow a logical approach to these activities.

5.1 Post Maintenance Resetting / Presetting

Typical interface activities performed on an OPTImizer2 after breaker maintenance include:

• PRESET REMAINING CONTACT LIFE (for

changing or presetting the contact life to 100%, for the appropriate phases of the circuit breaker after contact inspection, refurbishment, or replacement). Note that the PRESET settings are entered as a percentage of the Danger Limit on a phase-by-phase basis.

• CLEAR LATCHED ALARMS (for resetting any

asserted alarms after maintenance).

• RESET OPERATIONS COUNTER (for resetting the

Operations Count to zero after maintenance.)

• RESET SF

to calculate SF6 density trends after replacing a SF6 gas sensor). Note that these Trend Data are

automatically reset when gas lling is detected.

5.2 Periodic Data Dump

Typical interface activities to perform a periodic datadump from an OPTImizer2 include:

• Move to the HISTORY Page.

• Select the type of history report from the Available

Data list.

• Select the Date Range.

• Click “Download", at the upper right.

• A CSV (Comma Separated Values) le will be created. Choose to Open, Save or Cancel this le. (Typically, MS™ Excel will be used to open this le).

TREND DATA (for resetting data used

• The data can then be viewed, graphed, sorted, as

desired.

• See also page 59 for instructions for downloading

the complete OPTI

mizer

database using a USB

Script.

See pages 54 - 58 in this manual for a detailed explanation of each item in each report.

History Log

The OPTI

mizer

records all alarm events, application

events, circuit breaker events and SF6 density measurements in a large History Log database. Five types of reports can be downloaded from the History Log:

• Alarm History – Maximum 500 records This report lists the occurrence of all alarms of any type.

• Application Event History – Maximum 500 records This report lists the occurrence of all application

events, including: system restarts; conguration

changes;

• Circuit Breaker Event History – Maximum 500 records This report lists the occurrence of all circuit breaker operations and the data measured during those operations.

Daily Summary – Maximum 750 records This

• SF

report lists all SF6 measurements and calculations for the past day, including: average density, temperature, pressure, mass, trends, change in mass and accumulated mass loss.

Logged History - Maximum 5000 records

• SF

This report lists the density, pressure and temperature measurements taken at the programmed logging interval.

When the maximum number of records is reached in each history log, the oldest record will be erased when each new record is written to that log.

Downloading Reports

To download a report, select the HISTORY tab and choose a report from the Available Data list on the left. Select the time frame of the report from the Data Range on the right. Click “Download” to extract the report from the database. A

comma separated values (CSV) le will be generated. You can choose to open or save the le. The le can be opened

by Microsoft Excel

or an equivalent spreadsheet program.

Figure 23: User Interface, History Page

Page 55

Alarm History Report

The Alarm History Report consists of: Code; Category; Device; Data; State; (Date & Time) Occurred and (Date & Time) Cleared.

Code: The alarm Code is an abbreviation for the description of the alarm seen on the ALARM tab. The prex “al” is used to indicate that it is an Alarm code. The table below gives a description of each alarm Code:

Code: Description: Cause: How to Clear:

alInvalidConguration

alCongurationDNP3

alWarningLimit

alDangerLimit

Invalid Setup

Conguration

Invalid DNP3

Conguration

Remaining Contact Life Warning Limit Remaining Contact Life Danger Limit

alArcTimeLimit Arc Time Limit

alRestrike Restrike

alClearingTimeLimit Clearing Time Limit

alTripTimeLimit Trip Time Limit

alTravelTimeLimit Travel Time Limit

alClosingTimeLimit Closing Time Limit

alOperationCountLimit

alNoOperationsTimeLimit

Operation Count Limit No Operations Time Limit

alABLogicAlarm A-B Logic Alarm

alCongurationCbMonitor

alLowGasYellowLimit

alLowGassRedLimit

alErraticSignal

Invalid CB Monitor

Cong.

Low Gas Yellow

Limit SF6 Low Gas Red Limit Erratic Sensor Signal

alTrendLimit SF6 Trend Limit

alNoSensorSignal

alSignalRangeError

alCongurationSf6

No Sensor Signal Detected

Sensor Signal

Range Error Invalid SF

Conguration

alCTInputFailure CT Input Failure Bad CT Pickup Coil Check wiring or replace CT Pickup Coil

The unit has not been programmed

Enter conguration settings

DNP3 settings are illegal Reprogram DNP3 settings

Contact Life has reached the Warning Limit Contact Life has reached the Danger Limit Excess Arc Time has been detected A Restrike has been detected Excess Clearing Time has been detected Excess Trip Time has been detected Excess Travel Time has been detected Excess Closing Time has been detected Operation Count has reached the Limit Time between CB operations too long Logic violation on A & B inputs CB Monitor settings are illegal

On ACTION Tab: Preset Remaining Contact Life below the Warning Limit On ACTION Tab: Preset Remaining Contact Life below the Danger Limit

On ACTION Tab: Clear Latched Alarms

On ACTION Tab: Reset Operations Counter

Operate the circuit breaker

Self-clears when the A-B Input logic is OK

Reprogram CB Monitor settings

Low SF6 gas detected Add gas to the CB

Very low SF6 gas detected Erratic SF6 Sensor Signal detected SF6 Trend Limit has been reached No SF6 sensor signal Detected

SF6 sensor signal out of range

SF6 Monitor settings are illegal

Add gas to the CB

Self-clears when a signal is stable

Stop loss of SF6; On ACTION Tab: Reset SF6 Trend Data

Self-clears when a signal is detected

Self-clears when the signal is in range

Reprogram SF6 Monitor settings

alInternalError1 Internal Error #1 Data Overload Contact Technical Support

alInputInvalid Input Invalid Software Malfunction Contact Technical Support

alCBMonitorUnknownActity CBM Unknown Activity Software Malfunction Contact Technical Support

Unknown

alSF6UnknownActivity

Activity

alInternalErrorDNP3 Internal DNP3 Error Software Malfunction Contact Technical Support

Software Malfunction Contact Technical Support

Table 8: Alarm Codes

Page 56

Category:

The alarm Category identies what class the

alarm belongs to: System, Circuit Breaker

Monitoring (CBM) or SF6 Monitoring. The prex

“alc” is used to indicate that it is a Category code.

Type: The alarm Type indicates the severity of the

alarm condition: Warning, Alarm or Failure. The

prex “alt” is used to indicate that it is a Type

code

Application Event History Report

The Application Event History Report consists of: Code; Category; Device; Data; (Date & Time) Occurred

Code: This Code is an abbreviation for the description

of the Application Event. The prex “ae” is used

to indicate that it is an Application Event code. The table below gives the description of each Application Event Code:

Device: The alarm Device and Data combine to indicate

the location of the alarm condition. The prex

“ald” is used to indicate that it is a Device code.

Device code “aldChannelCBM” indicates that

the alarm relates to one of the circuit breaker phases.

Device code “aldChannelSF6” indicates

that the alarm relates to one of the SF6 input channels.

Device code “aldNone” indicates that the alarm

is a non-phase or non-channel related alarm.

Data:

The Device Data indicates which CB phase or SF6 input channel caused the alarm; 0 = None; 1 = A; 2 = B; 3 = C.

State: The State code indicates the present state of

the alarm: Active or Inactive. The prex “als” is

used to indicate that it is a State code.

Occurred: The report indicates the date and time the alarm

occurred.

Cleared:

The report indicates the date and time the alarm was cleared. Alarms that are presently in the active state will not have a cleared date and time.

Category: The Application Event Categories are the same

as Alarm Categories.

Device: The Application Event Devices are the same as

Alarm Devices.

Data: The Application Event Data are the same as

Alarm Data.

Occurred: The report indicates the date and time the

Application Event occurred.

Code: Description: Cause:

aeCongurationChanged Conguration Changed One or more program setting has changed

aeSystemTimeChanged System Time Changed The system clock time or date has changed

aeCircuitBreakerOpened Circuit Breaker Opened The CB was closed and now is open

aeCircuitBreakerClosed Circuit Breaker Closed The CB was open and now is closed

aeSF6DensityIncrease Density Increase Detected SF

gas has been added or density sensor malfunction

Table 9: Application Event Codes

Page 57

Circuit Breaker Event History Report

The Circuit Breaker Event History Report consists of:

• Report ID

• Time Stamp

• Type

• Operation Number

• Over Trip Time Limit (Input modes 2 & 4 only)

• Over Travel Time Limit (Input modes 1 & 4 only)

• Over Closing Time Limit (Input mode 1 only)

• Over Operation Count Limit

• Travel Time (Input modes 1 & 4 only)

• Trip Time (Input modes 2 & 4 only)

• Closing Time (Input mode 1 only)

Each phase has a record for:

• Restrike Occurred

• Over Warning Limit

• Over Danger Limit

• Over Arc Time Limit

• Arc Time

• Clearing Time (Input modes 2 & 4 only)

• Wear

• Wear Total

• Peak Current

Report ID: This is a number used by the system to identify the individual events in the report. It is not referenced to any external or programmable value. Its only purpose is to

keep events in sequential order in the database.

Time Stamp: The date and time each circuit breaker event was recorded.

Type: The event Type indicates what caused the circuit breaker event to be recorded: Trip (Opening); Closing; A-B Logic Failure (Alarm); No Operation (Alarm); Preset Wear; Preset Operation Number; Reset Operation Count

• Type code “cbTrip” indicates that the event record

was recorded because the circuit breaker has opened.

• Type code “cbClose” indicates that the event record

was recorded because the circuit breaker has closed.

• Type code “cbABLogicFailure” indicates that the

event record was recorded because an A-B Logic Failure Alarm occurred.

• Type code “cbNoOperation” indicates that the event

record was recorded because a No Operations Alarm occurred.

• Type code “cbPresetWear” indicates that the event

record was recorded because the remaining contact life was preset on one phase.

• Type code “cbPresetOperationNumber” indicates

that the event record was recorded because the Operation Number was preset.

• Type code “cbResetOperationCount” indicates

that the event record was recorded because the Operation Counter was reset.

Operation Number: This number is associated with the total operations on the circuit breaker and, if correctly preset, should match the circuit breaker’s mechanical counter.

Over Trip Time Limit: This indicates (True or False) whether the Trip Time Limit was reached or exceeded during this CB event.

Over Travel Time Limit: This indicates (True or False) whether the Travel Time Limit was reached or exceeded during this CB event.

Over Closing Time Limit: This indicates (True or False) whether the Closing Time Limit was reached or exceeded during this CB event.

Over Operation Count Limit: This indicates (True or False) whether the Operation Count Limit was reached or exceeded during this CB event.

Travel Time : This number is the measured Travel Time for this CB event.

Trip Time : This number is the measured Trip Time for this CB event.

Closing Time : This number is the measured Closing Time for this CB event.

Restrike Occurred (A,B,C): This indicates (True or False) whether a Restrike was detected on this phase (A,B,C) during this CB event.

Over Warning Limit (A,B,C): This indicates (True or False) whether the Contact Life Warning Limit was reached or exceeded on this phase during this CB event.

Over Danger Limit (A,B,C): This indicates (True or False) whether the Contact Life Danger Limit was reached or exceeded on this phase during this CB event.

Over Arc Time Limit (A,B,C): This indicates (True or False) whether the Arc Time Limit was reached or exceeded on this phase during this CB event.

Over Clearing Time Limit (A,B,C): This indicates (True or False) whether the Clearing Time Limit was reached or exceeded on this phase during this CB event.

Wear (A,B,C): This number is the measured contact wear

(I T or I

T) for this phase (A,B,C) for this CB event.

Wear Total (A,B,C): This number is the accumulated contact wear (I T or I 2T) for this phase (A,B,C) up to this CB event.

Peak Current (A,B,C): This number is the measured peak current in amps (not RMS) for this phase (A,B,C) for this CB event.

Page 58

SF6 Logged History Report

The SF6 Logged History Report consists of: Record ID; Time Stamp; Density (A,B,C); Pressure (A,B,C); Temperature (A,B,C).

Record ID: This is a number used by the system to identify the individual records in the report. It is not referenced to any external or programmable value. Its only purpose is to

keep records in sequential order in the database.

Time Stamp: The date and time each SF6 record was logged.

Density (A,B,C): The measured density (Grams / Liter) for this input channel (A,B,C) at the time the density record was logged.

Pressure (A,B,C): The calculated pressure (in the chosen units) for this input channel (A,B,C) at the time the gas record was logged.

Temperature (A,B,C): The measured temperature (in the chosen units) for this input channel (A,B,C) at the time the density record was logged.

SF6 Daily Summary Report

Date Stamp: The date each SF6 Summary record was logged.

Average Density (A,B,C): Average density (Grams/Liter) for the past 24 hours.

Average Pressure (A,B,C): Average pressure (in the chosen units) for the past 24 hours.

Average Temperature: Average temperature (in the chosen units) for the past 24 hours.

Density Trend (A,B,C): The calculated SF6 Density Trend (Grams / Liter / day) for this input channel (A,B,C) at the time the gas record was logged.

Pressure Trend (A,B,C): The calculated SF6 Pressure Trend (in the chosen units) for this input channel (A,B,C) at the time the gas record was logged.

Trend Conf (A,B,C): The calculated SF6 Trend Condence Level (%), for both density and pressure, for this input channel (A,B,C) at the time the gas record was logged.

Average Mass: Average mass (in the chosen units) for the past 24 hours.

Mass Change: The calculated change in mass (in the chosen units) over the past 24 hours, a negative number represents mass lost, a positive number represents mass gained

Accumulated Mass Loss: A running total of mass loss (in the chosen units), from the beginning of the Date Range to the date of that record in the report, a negative number represents mass lost. Accumulated Mass Loss is not

affected by gas lling events.

Data Interpreting

Circuit Breaker Data:

Data from the OPTImizer2 reveals absolute setpoint limit violation and trends in degradation:

• The phase segregated I

values allow analysis of the duty wear impressed on the breaker for that particular operation. Fault type can often be determined by examining which phase(s) has a higher value than the other phases.

• The phase segregated

per phase allows analysis to determine which pole(s) are nearing their life limits. Other uses for

this value involve correlation to grid (bafe) wear, oil

contamination, and gas contamination.

• The TRAVEL TIME (Opening Mechanism Time)

allows trending of the mechanical speed of the breaker. Rapid departures from normal values

suggest a mechanical compromise requiring urgent

attention. Small departures over a long time period may indicate a minor maintenance item, such as lubrication.

• The TRIP TIME (Breaker Trip Mechanism Time)

allows trending of the mechanical speed of the tripping mechanism. Rapid departures from normal

values suggest a mechanical compromise requiring

urgent attention. Small departures over a long time period may indicate a minor maintenance item, such as lubrication. Although no “Trip Coil Signature” data is recorded, the TRIP TIME measurement can indicate general condition and effectiveness of the tripping mechanism.

• The ARC TIME (Arc Duration) allows trending of the

dielectric capabilities of the breaker. By examining the ratio of TRAVEL TIME to ARC TIME, it can be determined if the ARC TIME is growing in duration while the TRAVEL TIME remains constant. If this is

observed, a compromise in the dielectric quality of

the breaker is suggested. Rapid departures from normal values suggest a dielectric compromise

requiring urgent attention. Small departures over a

long time period may indicate a minor maintenance item, such as gas reconditioning or oil replacement.

• CLEARING TIME (Breaker Interrupting Time) is the

sum of TRIP TIME and ARC TIME. This important measurement represents the breaker’s ability

to quickly interrupt current ow in reaction to a

fault condition. The CLEARING TIME data allows trending of the breaker’s overall effectiveness, mechanical and dielectric.

• CLOSING TIME (Closing Mechanism Time) allows

trending of the mechanical closing speed of the breaker. Rapid departures from normal values suggest

a mechanical compromise requiring urgent attention.

Small departures over a long time period may indicate a minor maintenance item, such as lubrication.

x T or I x T per trip event

I2 x T or I x T accumulated

Page 59

SF6 Data

Data from the OPTImizer2 can call attention to potential SF6 gas leaks; long before critical gas levels are reached.

• SF6 DENSITY indicates the dielectric strength of

the insulating gas. As density decreases, dielectric strength decreases.

TREND indicates the rate of gas loss averaged

• SF

over a 15 day period. A negative trend value

indicates gas loss. This trend may uctuate positive,

then negative, back and forth a small amount, due to the effects of temperature changes. If it shows a consistent negative value, this is a good indication that the SF6 may be leaking.

• CONFIDENCE LEVELS indicate the statistical

validity of the SF

trends. A combination of two

things affects the Condence Level value: the

amount of data collected and the linearity of the SF6 density data.

o It takes one full time period (15 days) to collect

enough SF

data to have a high Condence

Level in the trend calculation. Until the full array

of data is collected, the Condence Level will be

lower.

o If the SF6 data has signicant variation, the

Condence Level will be lower. If the SF6 data is very consistent, the Condence Level will be higher. Low Condence Levels, after the full time period has passed, indicate uctuations in

the SF6 measurements. This can be caused by temperature differences between the SF6 density sensor and the SF6 vessel itself. Another cause

of uctuations in the SF6 measurements could

be a sensor malfunction.

• The LOW GAS ALARM FORECAST is a prediction

(based upon the most recently calculated SF6 trend) of how many days before the SF6 reaches the Low Gas Alarm Limit. This forecast aids in scheduling and prioritizing of maintenance resources.

Page 60

5.3 Alarm Acknowledgement / Cancellation

Figure 24: User Interface, Status Page with Active Alarms

Typical interface activities performed on an OPTImizer2 to acknowledge and cancel an alarm include:

• Some active alarms appear as red “ALARM”

hyperlinks on the STATUS page (see Figure 22). Clicking on the red hyperlink will automatically move you to the ACTION page (see Figure 11).

• CLEAR LATCHED ALARMS (Latched Alarms include:

Trip Time; Travel Time; Closing Time; Restrike; Excess Arc and Clearing Time. These alarms can be cleared by clicking the “Clear Latched Alarms” button.)

• Move to the ALARMS Page to view a list of active

alarms.

• Contact Life (I2 T or I T) Warning and Danger alarms

must be cleared by presetting the Contact Life (by phase, see Figure 11) to a value lower than the alarm limit. This should only be done after maintenance to replace or recondition the interrupter contacts is completed.

• See below for instructions for clearing alarms using a

USB Script.

5.4 USB Scripts

The OPTImizer2 has the special capability to perform

certain operations from script les installed on a USB

memory stick. These operations include: clearing alarms; downloading the full database; resetting the IP address;

uploading new rmware. INCON Technical Support can

provide these scripts on memory sticks or through e-mail.

Downloading the Database: The full database will be automatically downloaded to the USB memory stick.

Resetting the IP Address: The OPTI

mizer

’s IP address

will be automatically reset to “192.12.27.1”. Uploading New Firmware: The new rmware will be

automatically uploaded. All conguration settings and

recorded history will be retained.

Transferring a script to a USB memory stick: Insert a USB memory stick into the USB port on the computer. Copy the les provided to the memory stick. (Only one script may be installed at a time on a memory stick). Remove the USB memory stick from the computer. It is ready to use. Insert it into the OPTImizer2’s USB port.

While the USB script is running, all LED’s will be lit. If there is a problem with the USB script or an error occurs

while running the script, the LED’s will ash rapidly. When

a script has completed its operation, the OPTI

ash all its LED’s slowly. When the LED’s are ashing the

USB memory stick can be removed and the OPTImizer

mizer

will

will return to normal operation. If the USB memory stick is

not removed, after 5 minutes the LED’s will stop ashing

and the OPTImizer2 will return to normal operation.

Clearing Alarms: All latched alarms will be automatically cleared.

Page 61

6 COMMUNICATION DETAILS

6.1 RS-232

The OPTImizer2 uses asynchronous RS-232 communications. It is congured as a DCE device. A 9-pin female connector is on the OPTImizer2 for cable connection. The end of the cable that connects with

the OPTImizer2 therefore is a 9-pin male.

OPTIMIZER2

DTE Device

STRAIGHT- THROUGH

(IN) DCD 1

(IN) RXD 2

(OUT) TXD 3

(OUT) DTR 4

GND 5

(OUT) RTS 7

(IN) CTS 8

1 DCD (OUT)

2 RXD (OUT)

3 TXD (IN)

5 GND

6 N/C

7 RTS (IN)

8 CTS (OUT)

9 N/C

(IN) DTR 4

(IN) TXD 3

(OUT) RXD 2

(OUT) DCD 1

(OUT) CTS 8

(IN) RTS 7

GND 5

4 DTR (IN)

OPTImizer

1 DCD (OUT)

2 RXD (OUT)

3 TXD (IN)

4 DTR (IN)

5 GND

6 N/C

7 RTS (IN)

8 CTS (OUT)

9 N/C

DCE Device

DCE DeviceDCE Device

Pins 1 and 4 are connected internally

“NULL MODEM”

Note: All references are to DTE 9-pin convention.

CABLE

Figure 25: 9-pin to 9-pin Cable Connections

Page 62

OPTImizer

DTE Device

(OUT) DTR 20

(OUT) RTS 4

STRAIGHT- THROUGH

DCE Device

(OUT) DCD 8

(OUT) CTS 5

(IN) DCD 8

(IN) RXD 3

(OUT) TXD 2

GND 7

(IN) CTS 5

(IN) DTR 2

(IN) TXD 2

(OUT) RXD 3

GND 7

(IN) RTS 4

DCE Device

1 DCD (OUT)

2 RXD (OUT)

3 TXD (IN)

4 DTR (IN)

5 GND

6 N/C

7 RTS (IN)

8 CTS (OUT)

9 N/C

OPTImizer

DCE Device

1 DCD (OUT)

2 RXD (OUT)

3 TXD (IN)

4 DTR (IN)

5 GND

6 N/C

7 RTS (IN)

8 CTS (OUT)

9 N/C

Pins 1 and 4 are connected internally

“NULL MODEM”

Cable

Figure 26: 25-pin to 9-pin Cable Connections

Note: All references are to DTE 25 and 9 pin conventions.

Page 63

6.2 Fiber-Optic Interconnection

2814 M

2814 F

TRANSCEIVER

Male End Female End

The OPTImizer2’s serial port is congured to support the use of Schweitzer ber-optic transceivers. A 9-pin female null modem adaptor must be used between the OPTImizer2 and the transceiver.

The transceiver will be powered directly from the OPTImizer2’s serial port’s CTS line. No other

programming is needed. The ber-optic connection labeled “T” on each transceiver should connect to the ber-optic connection labeled “R” on the other transceiver.

Figure 27: Schweitzer Fiber-Optic Interface

6.3 RS-485

The OPTImizer2 employs full duplex RS-485 communications, but can be wired for half duplex communication if needed. The same RS-232 port settings apply to the RS-485 port.

Figure 28: RS-485 Half-Duplex Wiring Figure 29: RS-485 Full-Duplex Wiring

6.4 Ethernet

The OPTImizer2 uses a standard 10-Base T / 100-Base T Ethernet connector. A special “crossover cable” is provided to facilitate connection directly to a computer’s RJ45 port. This cable may not be suitable for connection to a router or other communication device.

Page 64

6.5 XML

The OPTImizer2 will respond to manual XML commands. To access XML command mode, select the PREFERENCES page. Click on “EDIT” in the upper right.

Figure 30: User Interface, Preferences Page

Check the box next to “Show XML Tool”.

Click “Yes” to update the preferences.

Enter the Administrator’s password if prompted.

Figure 31: User Interface, Editing the Preferences Page

Page 65

Figure 32: User Interface, XML Page

Click “Query”. The Command eld can now be pulled down and an XML command selected. Click “Help” to view an

explanation of the command and its proper syntax.

Figure 33: User Interface, XML Command Access

Once selected, a command can be executed by clicking “Send”. The response will be listed in the lower portion of the window.

Page 66

6.6 DNP3.0

The following table provides a “Device Prole Document” in the standard format dened in the DNP3 Subset Denitions Document. While it is referred to in the DNP3 Subset Denitions as a

“Document,” it is only a component of a total interoperability guide. This table in combination with

the Implementation Table should provide a complete interoperability/conguration guide for the

OPTImizer

6.6.1 Device Prole Document

DNP V3.0

Device Prole Document

(Also see the DNP Implementation Table, beginning on page 68)

Vendor Name: Franklin Fueling Systems, Inc.

INCON Power Reliability Systems

Device Name: OPTImizer

Highest DNP Level Supported:

For Requests: Level 2

For Responses: Level 2

Notable objects, functions, and/or qualiers supported in addition to the Highest DNP Levels Supported (the

complete list is described in the Implementation Table):

NONE

Maximum Data Link Frame Size (octets):

Transmitted: 292

Received: 292

Maximum Data Link Re-tries:

1 None

1 Fixed g Congurable from 0 to 255

Requires Data Link Layer Conrmation:

Device Function:

1 Master

g Slave

Maximum Application Fragment Size (octets):

Transmitted: Fixed at 4096

Received: Fixed at 4096

Maximum Application Layer Re-tries:

1 None g Congurable from 0 to 65535

Requires Application Layer Conrmation:

1 Never

1 Always

g Sometimes 1 Congurable

Timeouts while waiting for: Data Link Conrm: 1 None g Fixed at 1 sec. 1 Variable 1 Congurable Complete Appl. Fragment 1 None g Fixed at 5 sec. 1 Variable 1 Congurable Application Conrm: 1 None g Fixed at 5 sec. 1 Variable 1 Congurable Complete Appl. Response: 1 None g Fixed at 5 sec. 1 Variable 1 Congurable

1 Never

1 Always

g Sometimes 1 Congurable

Page 67

Sends/Executes Control Operations:

WRITE Binary Outputs: g Never 1 Always 1 Sometimes 1 Congurable SELECT/OPERATE: 1 Never g Always 1 Sometimes 1 Congurable DIRECT OPERATE: g Never 1 Always 1 Sometimes 1 Congurable DIRECT OPERATE – No ACK: g Never 1 Always 1 Sometimes 1 Congurable

Count>1: g Never 1 Always 1 Sometimes 1 Congurable Pulse On: 1 Never g Always 1 Sometimes 1 Congurable Pulse Off: g Never 1 Always 1 Sometimes 1 Congurable Latch On: g Never 1 Always 1 Sometimes 1 Congurable Latch Off: g Never 1 Always 1 Sometimes 1 Congurable

Queue: g Never 1 Always 1 Sometimes 1 Congurable Clear Queue: g Never 1 Always 1 Sometimes 1 Congurable

Reports Binary Input Change Events when no

specic variation requested:

Reports Time-Tagged Binary Input Change Events when no

specic variation requested:

1 Never

1 Only Time-Tagged

1 Only Non-Time-Tagged g Congurable

Sends Unsolicited Responses:

1 Never 1 Congurable

1 Only certain objects

1 Sometimes

g ENABLE/DISABLE UNSOLICITED

Default Counter Object/Variation:

1 No Counter Reported g Congurable

1 Default Object ____

Default Variation ____

1 Point by Point List Attached

Sends Multi-Fragment Responses:

1 Never

1 Binary Input Change With Time

1 Binary Input Change With Relative Time g Congurable

Sends Static Data in Unsolicited Responses:

g Never

1 When Device Restarts

1 When Status Flags Change

Counters Roll Over at:

1 No Counter Reported 1 Congurable

g 16 Bits (65,535)

g 32 Bits (4,294,967,295)

1 Other Value ______

1 Point by Point List Attached

g Yes

1 No

Page 68

6.6.2 DNP3.0 Implementation Table

The following table identies the variations, function codes, and qualiers supported by the

OPTImizer

Object Number

12 1

20 1

22 1

30 5

32 5

41 1

41 2

41 3

DNP Slave in both request messages and in response messages.

Variation Number

1 1

2 2

OBJECT REQUEST RESPONSE

Description Function

Binary Input - Singlebit packed

Binary Input Change Event - with absolute time

Pulsed Control control relay output block

Counter - 32-bit with

ag

Counter Change

Event - 32-bit with ag

Analog Input - single-

precision, oatingpoint with ag

Analog Input Change Event - single-

precision, oating-

point without time

Analog Output Block

- 32-bit

Analog Output Block

- 32-bit

Analog Output Block

- 32-bit

Analog Output Block

- 16-bit

Analog Output Block

- 16-bit

Analog Output Block

- 16-bit

Analog Output Block

- single-precision,

oating-point

Analog Output Block

- single-precision,

oating-point

Code (Dec)

1(read) 06 (no range, or all) 129 (Response) 00, 01 (start-stop),

1(read) 06 (no range, or all),

3(select) 17, 28 (index),

4(operate) 17, 28 (index),

(direct op.)

1(read) 06 (no range, or all) 129 (Response) 00, 01 (start-stop),

1(read) 06 (no range, or all),

1(read) 06 (no range, or all) 129 (Response) 00, 01 (start-stop),

1(read) 06 (no range, or all),

3(select) 17, 28 (index),

4(operate) 17, 28 (index),

(direct op.)

3(select) 17, 28 (index),

4(operate) 17, 28 (index),

(direct op.)

3(select) 17, 28 (index),

4(operate) 17, 28 (index),

Qualier Code

(Hex)

07, 08 (limited qty), 09

17, 28 (index), 39

07, 08 (limited qty), 09

17, 28 (index), 39

Function Code

Qualier Code (Hex)

(Dec)

129 (Response) 17, 28 (index),

129 (Response) echo of request

129 (Response) 17, 28 (index),

129 (Response) echo of request

Page 69

6.6.3 DNP3.0 Point List

The following table identies for each data type, the data points available in the device.

Binary Input Points Slave >> Master

Static (Steady-State) Object Number: 1

Change Event Object Number: 2

Static Variation reported when variation 0 requested: 1 (Binary Input 2 without status) Change Event Variation reported when variation 0 requested: 3 (Binary Input Change with Time)

Event

Class

Circuit Breaker Monitor

1 0 2 2

1 1 2 2

1 2 2 2

1 3 2 2

1 4 2 2

1 5 2 2

1 6 2 2

1 7 2 2

1 8 2 2

1 9 2 2

1 10 2 2

1 11 2 2

1 12 2 2

1 13 2 2

1 14 2 2

1 15 2 2

1 16 2 2

1 17 2 2

1 18 2 2

1 19 2 2

1 20 2 2

1 21 2 2

1 22 2 2

1 23 2 2

1 24 2 2

1 25 2 2

1 26 2 2

1 27 2 2

Point

Index

Default

Group

Default Variable

Name/Description

Breaker Is Open

A-B Logic Failure Alarm Acve

Contact Life Warning Acve Phase A

Contact Life Warning Acve Phase B

Contact Life Warning Acve Phase C

Contact Life Danger Alarm Acve Phase A

Contact Life Danger Alarm Acve Phase B

Contact Life Danger Alarm Acve Phase C

Trip Time Alarm Acve

Arc Time Alarm Acve Phase A

Arc Time Alarm Acve Phase B

Arc Time Alarm Acve Phase C

Clearing Time Alarm Acve Phase A

Clearing Time Alarm Acve Phase B

Clearing Time Alarm Acve Phase C

Travel Time Alarm Acve

Closing Time Alarm Acve

Operaon Count Alarm Acve

No-Operaons Alarm Acve

Restrike Alarm Acve Phase A

Restrike Alarm Acve Phase B

Restrike Alarm Acve Phase C

Monitor

Sensor Malfuncon Alarm Acve

Low Density Alarm Acve

Trend Alarm Acve

CT Failure Alarm Acve Phase A

CT Failure Alarm Acve Phase B

CT Failure Alarm Acve Phase C

30 5 Default Static Analog

32 5 Default Event Analog

20 1 Default Static Counter

22 1 Default Event Counter

1 2 Default Static Binary

2 2 Default Event Counter

Page 70

Analog Input Points Slave >> Master

Static (Steady-State) Object Number: (30,1)

Change Event Object Number: (32,1)

Static Variation reported when variation 0 requested: (30,1) Change Event Variation reported when variation 0 requested: (32,1)

Event

Class

Circuit Breaker Monitor

2 0 32 5

2 1 32 5

2 2 32 5

2 3 32 5

2 4 32 5

2 5 32 5

2 6 32 5

2 7 32 5

2 8 32 5

2 9 30 5

2 10 30 5

2 11 30 5

0 12 30 5

0 13 30 5

0 14 30 5

0 15 30 5

SF6 Monitor

0 16 30 5

0 17 30 5

0 18 30 5

0 19 30 5

0 20 30 5

0 21 30 5

0 22 30 5

0 23 30 5

0 24 30 5

0 25 30 5

0 26 30 5

0 27 30 5

0 28 30 5

0 29 30 5

0 30 30 5

0 31 30 5

0 32 30 5

0 33 30 5

Point

Index

Default

Group

Default Variable

Name/Description Dead Band

Current Wear Phase A

Current Wear Phase B

Current Wear Phase C

Percent of Warning Limit Phase A

Percent of Warning Limit Phase B

Percent of Warning Limit Phase C

Percent Of Danger Limit Phase A

Percent Of Danger Limit Phase B

Percent Of Danger Limit Phase C

Percent Remaining Contact Life Phase A

Percent Remaining Contact Life Phase B

Percent Remaining Contact Life Phase C

RMS Current Phase A

RMS Current Phase B

RMS Current Phase C

Days since last operaon

Current Density Channel A

Current Density Channel B

Current Density Channel C

Current Temperature Channel A

Current Temperature Channel B

Current Temperature Channel C

Trend Channel A

Trend Channel B

Trend Channel C

Trend Condence Level Channel A

Trend Condence Level Channel B

Trend Condence Level Channel C

Average Mass Channel A

Average Mass Channel B

Average Mass Channel C

Average Pressure Channel A

Average Pressure Channel B

Average Pressure Channel C

Page 71

Counter Input Points Slave >> Master

Static (Steady-State) Object Number: (20,1)

Change Event Object Number: (22,1)

Static Variation reported when variation 0 requested: (20,1)

Change Event Variation reported when variation 0 requested: (22,1)

Point

Index

1 0 22 1

1 1 22 1

Point

Index

Default

Group

Default Variable

Name/Description

Current Operaon Number

Operaon Count

Control Output Points Master >> Slave

Static (Steady-State) Object Number: (12,1)

Change Event Object Number: NA

Static Variation reported when variation 0 requested: NA

Change Event Variation reported when variation 0 requested: NA

Point

Index

Circuit Breaker Monitor

Name/Description

Clear Circuit Breaker Alarms

Reset Operaon Count

Preset Operaon Number

Preset Contact Life

Monitor

Clear SF6 Alarms

Reset Trend Data

Setpoint Output Points Master >> Slave

Static (Steady-State) Object Number: (40,2)

Change Event Object Number: NA

Static Variation reported when variation 0 requested: NA

Change Event Variation reported when variation 0 requested: NA

Circuit Breaker Monitor

Preset Operaon Number Value

Preset Contact Life Value Phase A

Preset Contact Life Value Phase B

Preset Contact Life Value Phase C

Page 72

7 SPECIFICATIONS

Electrical:

Power Supply Input Voltage 110-250 VDC / 90-264 VAC, 50 / 60 Hz

Aux A & B Input Voltage 0 to 48 - 250 VDC

CT (Pickup Coil) Input Signal 0 to 5 VAC

Input Sampling Rate 32 Samples per line cycle

Input Signal

Sensor Power 20 VDC @ 25mA Max

Relay Outputs Dry Contact; 2 ea. Form C, 1 ea. Form A

Relay Contact Rating 3 Amps @ 250 VAC or ½ Amps @ 125 VDC

Environmental:

Operating Temperature -40 to 65° C

Storage Temperature -40 to 65° C

Humidity 0 to 95% Non-condensing

Communication: RS-485 Full / Half Duplex

Analog: 4 to 20 mA

Digital: Frequency & Pulse-Width Modulated

RS-232

USB Master

Ethernet

User Interface: 19 LED’s

Immunity and Emissions Certication:

CISPR 16-2-1 (Conducted Emissions)

CISPR 16-2-3 (Radiated Emissions)

IEC61000-4-2 (ESD)

IEC61000-4-3 (Radiated RF)

IEC61000-4-4 (EFT)

IEC61000-4-5 (Surge)

IEC61000-4-6 (Conducted RF)

IEC 61000-4-11 (Voltage Dips & Interrupts)

IEC 61000-4-12 (Damped Osc. Wave, Power Ports)

FCC Part 15, Subpart B; ICES-003 (Emissions)

Physical:

184 L x 146 W x 76 H Millimeters

Dimensions

7.25 L x 5.75 W x 3.00 H Inches

Shipping Weight 5 lbs. (2.25Kg)

Table 10, OPTImizer2 Specications

Page 73

DSDP SF6 Density & Temperature Sensor Specications

Principal: Oscillating Quartz Measurement

Density Measuring Range: 0 to 60 Grams per Liter (kg/m3) SF

Temperature Measuring Range: -40 to +85 Degrees Celsius

Accuracy: +/- 1% of measured value and +/- 1% of range

Repeatability: +/-0.2% of measured value

Stability: <+/-0.3% per year

Temperature Signal: +/-1ºC @ ambient temperature, +/-3ºC at -40 to 85ºC Output Signal: Current pulses, frequency & pulse-width modulated

Supply Voltage: 10 to 20 Volts DC

Electrical Connections: 2-Wire (10 foot cable provided)

Operating Temperature: -40 to +70 Degrees Celsius

Operating Pressure: -1 to +20 Bar

Humidity: 98% Relative, Suitable for outdoor use

Vibration: 15 g (max 6 mm, 5-2000Hz) Shock 100g/6mS Mounting Thread: G ⅜" Male British Standard Parallel

Seal: Neoprene O-ring (provided)

Weight: Approx. 250 g without cable, 325g with cable

Page 74

P.O Box 638, Saco, Me. 04072 Tel: 207-283-0156

Fax: 207-238-0158

Incon OPTImizer 2 User Manual

Specifications and Main Features

Frequently Asked Questions

User Manual