• No results found

Nu-Lec_MODBUS - Technical Manual

N/A
N/A
Protected

Academic year: 2021

Share "Nu-Lec_MODBUS - Technical Manual"

Copied!
73
0
0

Loading.... (view fulltext now)

Full text

(1)

A Schneider Electric Company

Modbus Protocol

Technical Manual

For Automatic Circuit Reclosers

And

Load Break Switches

With

CAPM-4/5 Controllers

Scope

This document describes the Modbus Protocol and Database Implementation on

Nu-Lec Automatic Circuit Reclosers and Load Break Switches utilising CAPM-4/5 controllers.

Document Part No:

N00-665

Document

Revision

Level:

R05

(2)

ACN 085 972 425

37 South Street,

Lytton,

QLD 4178,

Australia.

Tel +61 7 3249 5444

Fax +61 7 3249 5888

LIMITATIONS

This document is copyright and is provided solely for the use of the recipient. It is not to be copied

in any way, nor its contents divulged to any third party, nor to be used as the basis of a tender or

specification without the express written permission of Nu-Lec Industries Pty Ltd.

This document discloses confidential intellectual property that belongs to Nu-Lec Industries P/L.

This document does not invest any rights to Nu-Lec Industries intellectual property in the recipient.

Moreover the recipient is required not to disclose any of the intellectual property contained in this

document to any other party unless authorised in writing by Nu-Lec Industries Pty Ltd.

Public Access: \stdprod\N00\Current\N00-665Rev5.pdf

Source: \R&D\CAPM4\manuals\N00-665.doc

(3)

R00 DPC 24/10/01 Initial revision

R01 DPC 12/11/01 Alteration from first meeting 8/11/01

R02 DPC 10/05/02 Correct Loop Automation ON rejection reasons. R03 DPC 18/12/02 Add new points for Version 28.

Removed reference to Frame Timeout.

R04 PJM 24/10/03 Added new appendix for CAPM2 N00-321 & N00-360 emulation. Altered the Mapping selection field

(4)

2.1 Data Types ...4

2.2 Controls...4

2.3 Terminology...4

2.4 LBS vs ACR Point Mapping. ...5

2.5 Password Protection...5

3 Applicability ...5

3.1 Control Cubicle Software ...5

3.2 Modbus Protocol Definition ...5

3.3 Switchgear Type ...5

4

Year 2000 Compliance Statement ...5

5 Protocol

Configuration...5

5.1 Protocol Parameter Configuration ...6

6 Physical

Layer...6

6.1 Communications Ports Supported...6

6.2 RS-232 Communication Specifications...6

6.2.1

RS-232 Hardware Signals...6

6.2.2

RS-232 Character Definition ...7

6.2.3

Communication Configuration Parameters...7

6.2.4 RS-232

Configuration...7

6.3 V23 FSK Communication Specifications...9

6.3.1

V23 Hardware Signals ...9

6.3.2

V23 Configuration Parameters ...10

6.3.3

V23 Handshaking Signals...12

6.4 Communication Statistics ...12

Appendix A Protocol Timings ...14

Appendix B Modbus Implementation Table...15

Appendix C - ACR Modbus Points ...16

Appendix C.1 ACR Modbus - Digitial Inputs ...16

Appendix C.2 ACR Modbus - Analogue Inputs...34

Appendix C.3 ACR Modbus - Digital Control ...42

Appendix C.4 ACR Modbus - Analogue Control...47

Appendix D LBS Modbus Points ...48

Appendix D.1 LBS Modbus - Digital Inputs...48

Appendix D.2 LBS Modbus - Analogue Inputs...55

Appendix D.3 LBS Modbus - Digital Control...61

Appendix D.4 LBS Modbus - Analogue Control ...64

Appendix E CAPM2 Modbus Point Map ...65

Appendix E.1 Data Available over Modbus ...65

Appendix E.2 Controls Available over Modbus...68

Appendix F CAPM2 N00-321 and N00-360 Modbus Point Map ...69

Appendix F.1 Data Available over Modbus ...69

(5)

For more information about the Automatic Circuit Recloser or Load Break Switch refer to relevant

technical manual for your switchgear type.

2 Overview

The Nu-Lec CAPM controller combines the functions of protection relay and switchgear controller

into a single intelligent electronic device (IED).

The controller provides a user friendly operator interface on a four line LCD control panel which

allows configuration and control of the switchgear and configuration of the Modbus Protocol, refer

section 5.1.

Electricity supply utilities frequently link the controller into their SCADA systems as a Remote

Terminal Unit (RTU).

To make this simple the controller provides….

• Mounting room for a radio or modem in the control cubicle.

• Power supply for the radio or modem in the control cubicle.

• Embedded protocol handler for the required SCADA protocol in the controller firmware.

This document describes the embedded Modbus protocol handler for the CAPM4/5 controller.

2.1 Data Types

The Modbus protocol handler supports the following data exchange between the CAPM4/5 and a

SCADA system Master Station.

• Digital Inputs

• Analogue Inputs

• Digital Control

• Analogue Control

More information is given in later sections.

2.2 Controls

A list of the controls supported by the protocol handler is detailed in Appendix C.3 and Appendix

D.3.

All digital controls have a corresponding digital input. The master station must use these input

points to verify that the control action has been successful. Sometimes a control will be rejected

because of an underlying CAPM condition preventing the action. These conditions are detailed in

the table in the appendices.

The Modbus protocol handler triggers two events that are recorded in the CAPM event log -

“Modbus Trip Req” and “Modbus Close Req”. This event log reporting indicates only that the

protocol handler has requested a trip or a close from the CAPM. It does not necessarily mean that

the action has been taken.

The Modbus protocol handler is designated as a remote user. Refer to the equipment manual for

more information.

2.3 Terminology

The terminology used in this document is that Earth Fault or Ground Fault is described as Earth /

Ground Fault and Sensitive Earth Fault (SEF) or Sensitive Ground Fault (SGF) is described as

SEF/SGF.

Also, bushing terminology used in this document is for U and W series switchgear ie I and X for the

switchgear terminals. On N or RL series switchgear the 1 side is described as I and the 2 side is

described as X.

Also note that the phase terminology is ABC and refers always to the phase set by the Terminal

Designation or “Phasing” option, never to the physical bushing or terminal on the switchgear.

(6)

is firmware dependant and determined by the CAPM on power up. If the incorrect configuration is

supplied please refer to Nulec Industries or your distributor.

2.5 Password Protection

All Modbus panel fields require password entry unless described as ‘Display only’ or otherwise

stated.

For more information on operator control panel usage refer to the equipment manual.

3 Applicability

3.1 Control Cubicle Software

This document applies to Nu-Lec pole top reclosers using a CAPM Controller which displays

“Modbus Protocol Manual N00-665 R05+” on the controller capability pages.

To find these pages refer to the main equipment manual.

3.2 Modbus Protocol Definition

The protocol version implemented by Nu-Lec is Modbus and is described in the following

document: -

• 'Gould Modbus Protocol Reference Guide', PI-MBUS-300 RevB, January 1985

The Modbus protocol handler implements a sub-set of the complete Modbus protocol definition.

The subset of Modbus communication function codes that are supported are listed in Appendix B.

This sub-set allows a Modbus master station to poll a Nulec recloser and:

• scan the current values of inputs, holding registers

• force logic coils

• preset holding registers

3.3 Switchgear Type

Applicable to the following switchgear types:

• N-Series ACR, all models with CAPM-4/5 controllers.

• U-Series ACR, all models with CAPM-4/5 controllers

• W-Series ACR, all models with CAPM-4/5 controllers

• RL-Series LBS, all models with CAPM-4/5 controllers

4 Year 2000 Compliance Statement

The Modbus protocol software complies with rules 1, 2, 3 and 4 of the British Standards Institute

Year 2000 Conformity Requirement (DISC PD2000-1 A Definition of Year 2000 Conformity

Requirements). A copy of this statement can be found on the Nu-Lec Industries Pty Ltd web site

(

http://www.Nu-Lec.com.au/

).

5 Protocol

Configuration

The Modbus protocol handler adds several pages to the “System Status” menus. The additional

pages fall into the following groups,

• Protocol Parameter Configuration

• Communications Parameter Configuration

• Communications Statistics

All protocol configuration parameters can be viewed, modified and stored on a personal computer

with the WSOS utility.

(7)

---- Modbus Protocol Configuration 1 ---

RTU Address 1 Framing RTU

Mapping NORMAL

Parameter Description

RTU Address

RTU Address

The station address of this unit on the communication link.

Range 1 to 247

Factory default is 1

Framing

Framing Type

Display only. Transmission mode used by RTU.

Mapping

Database Point Mapping

The point map provided by the CAPM. The range is

CAPM4/5 ACR

(Refer to Appendix C)

CAPM4/5 LBS

(Refer to Appendix D)

CAPM2 424

(Refer to Appendix E)

CAPM2 321

(Refer to Appendix F)

CAPM2 360

(Refer to Appendix F)

Default: CAPM4/5 ACR

6 Physical

Layer

6.1 Communications Ports Supported

The CAPM can communicate to the Master station via one of the following ports.

• RS-232 Port P8

• V23 FSK Port P10

6.2 RS-232 Communication Specifications

6.2.1 RS-232 Hardware Signals

P8 Pin

Direction

Description

2

From CAPM

Tx Data (TxD)

3

To CAPM

Rx Data (RxD)

4

From CAPM

Request To Send (RTS)

5

To CAPM

Clear To Send (CTS)

7 -

Signal

Ground

8

To CAPM

Carrier Detect (CD)

20

From CAPM

Data Terminal Ready (DTR)

Note: The CAPM uses RTS/CTS hardware handshaking. If not supported by the master then a loop

back is required at the CAPM end of the communication cable.

(8)

6.2.3 Communication Configuration Parameters

The following communications configuration pages allow the user to specify parameters required

for operation of the physical link between the recloser and the master station.

--- Modbus Communications 1 ---

P8 RS-232 RUNNING

Pre-Tx 250ms Post-Tx 35ms

Parameter Description

OFF

P8 RS-232

P10 V23

Port Selection

This field selects the communications medium the Modbus protocol

uses for transmission.

When OFF is selected, the protocol handler is disabled.

When P8 RS–232 is selected, the protocol handler uses the P8 serial

port for all data. Also, the Modbus Communications 1 and 2 pages are

automatically updated to reflect relevant RS-232 data as detailed below.

When P10 V23 FSK is selected, the protocol uses the built in V23

modem on P10. Also, the Modbus Communications 1 and 2 pages are

automatically updated to reflect relevant FSK data. Refer to section 6.3

for the P10 configuration details.

Range: OFF, P8 RS-232, P10 V23

Factory default is P8 RS–232

RUNNING

INACTIVE

Protocol Status

Indication of the current status of the communications. (Display only)

RUNNING means that the protocol handler has connected to the

communication port (P8 or P10) and is running.

INACTIVE means that the protocol handler has been disabled via the

OFF state above or has been unable to connect to a communication

port. This is usually caused by another application already having

exclusive access to the port.

Range: INACTIVE, RUNNING

Pre-Tx

Pre-Transmission Period

The time delay between keying RTS to when the message starts.

Range: 50 to 1000 ms.

Factory default is 250 ms

Post-Tx

Post-Transmission Period

The time after the last character is sent before RTS is negated.

Range: 0 to 1000 ms.

Factory default is 35 ms

6.2.4 RS-232 Configuration

The following communications configuration pages allow the user to specify parameters required

for operation of a RS-232 / Modem physical link between the recloser and the master station.

(9)

DCD Ignore

Baud 9600

Parameter Description

Parity

Communication Parity

Determines the parity of the communication port.

Range: NONE, ODD, EVEN

Factory default is EVEN

DCD Ignore

DCD Don’t

Ignore

DCD Usage

If the modem does not support a Data Carrier Detect (DCD) signal this

parameter should be set to DCD Ignore.

Even if the modem does support a DCD signal this parameter is usually

set to DCD Ignore. This is because most point-point systems using

conventional modems run as full duplex so that the DCD is always

asserted during normal operation.

When set to the ‘Ignore’ mode, the protocol uses any received data to

build an incoming packet irrespective of DCD input signal. Also the

protocol will transmit irrespective of the DCD input signal.

If the modem supports a Data Carrier Detect (DCD) signal this parameter

can be set to DCD Don’t Ignore. When set to this mode, the protocol will

only read data and build an incoming protocol packet when DCD is

asserted. In addition, the protocol will not transmit when DCD is

asserted. This is necessary for multi-dropped systems or ones shared with

voice users or some radio-modems.

Range: DCD Ignore, DCD Don’t Ignore

Factory default is DCD Ignore

Baud

Communications Baud Rate

Range: 300, 1200, 2400, 4800, 9600 or 19200

1

baud.

Factory default is 9600 Baud

--- Modbus Communications 3 ---

Pre-amble DISABLED First Char 0x55

Repeat First 3 Last Char 0xFF

Parameter Description

Pre-amble

Preamble Usage

Determines whether the protocol transmits some preamble characters

prior to the start of a protocol message. The message itself is not

otherwise modified. Some modems require these characters to assist with

message reception and synchronisation at the master station. Start of

frame filtering at the master station ensures identification of the protocol

(10)

preamble characters.

Range: ENABLED, DISABLED

Factory default is DISABLED

First Char

Preamble First Character

This is the first character to be transmitted as a preamble. The character

is specified by entering its ASCII code in hexadecimal format.

Range: is 0 to FF hexadecimal.

Factory default is 0x55

Repeat First

Number of Preamble First Characters

This is the number of times the first character will be repeated as part of

the preamble.

Eg if all preamble settings are at default values then the preamble sent is

0x55, 0x55, 0x55, 0xFF

Range: 0 to 20.

Factory default is 3

Last Char

Last Preamble Character

This is the last char that will be sent as part of the preamble. The

character is specified by entering its ASCII code in hexadecimal format.

Range: is 0 to FF hexadecimal.

Factory default is 0xFF

6.2.4.1 Carrier

Detect

When “DCD Ignore” is configured, the Data Carrier Detect (DCD) input is not used. All data is

received and transmitted irrespective of the state of the DCD signal.

When “DCD Don’t Ignore” is configured, the CAPM will not begin to transmit a packet until

DCD is negated, and will only receive data when DCD is asserted.

Refer to the DCD Usage parameter description for more information.

6.2.4.2

Transmitting a Modbus Message

Transmission of a Modbus packet follows the steps below

1. RTS line is asserted

2. CAPM waits until the pre-transmission delay expires (Delay set from the panel)

3. Checks CTS is asserted.

4. The pre-amble is transmitted (Optional. Set from the panel).

5. Checks CTS is asserted.

6. The Modbus packet is transmitted

7. Waits until the post-transmission delay expires (Delay set from the panel)

8. RTS is negated

6.2.4.3 DTR

DTR is asserted by the Modbus protocol handler at power-up and remains asserted.

6.3 V23 FSK Communication Specifications

6.3.1 V23 Hardware Signals

Standard Cable

Type N03-530

(11)

15

15

From CAPM

Press To Talk (PTT)

11

11

From CAPM

Transmit, 600 Ohm impedance

Level 2.5V pk-pk

6

6

To CAPM

Busy, 10kOhm impedance

Signal frequencies conform to V23 standard.

The protocol only supports half duplex (ie receive and transmit can not occur at the same time)

when using the V23 port.

All transmissions are 1200 baud, 8 bit, and one stop bit. Parity is configurable.

6.3.2 V23 Configuration Parameters

The Modbus communications configuration page allows the user to specify parameters required for

operation of the physical link between the recloser and the master station.

--- Modbus Communications 1 ---S

P10 FSK V23 RUNNING

Pre-Tx 250ms Post-Tx 35ms

Tx NORMAL Parity EVEN

--- Modbus Communications 2 ---S

Busy Disabled

Busy when input low

Busy Idle

--- Modbus Communications 3 ---S

Pre-amble DISABLED First Char 0x55

Repeat First 3 Last Char 0xFF

Parameter Description

OFF

P8 RS-232

P10 V23 FSK

Port Selection

This field selects the communications medium the Modbus protocol

handler uses for transmission.

When OFF is selected, the protocol handler is disabled.

When P8 RS –232 is selected, the protocol uses the P8 serial port for all

data. Also, the Modbus Communications 1 and 2 pages are automatically

updated to reflect relevant RS-232 data. Refer to section 6.2 for the P8

configuration details.

When P10 V23 FSK is selected, the protocol uses the built in V23

modem on P10. Also, the Modbus Communications 1 and 2 pages are

automatically updated to reflect relevant FSK data as detailed below.

(12)

RUNNING

INACTIVE

RUNNING means that the protocol handler has connected to the

communication port (P8 or P10) and is running.

INACTIVE means that the protocol handler has been disabled via the

OFF state above or has been unable to connect to a communication port.

This is usually caused by another application already having exclusive

access to the port.

Range: INACTIVE, RUNNING

Pre-Tx

Pre-Transmission Period

The time delay between keying PTT to when the message starts.

During this time a logic 1 is sent.

Range: 50 to 1000 ms.

Factory default is 250 ms

Post-Tx

Post-Transmission Period

The time after the last character is sent before PTT is negated.

During this time a logic 1 is sent.

Range: 0 to 1000 ms.

Factory default is 35 ms

Tx NORMAL

Tx TEST

Transmission Mode

This field can be used to test the radio transmitter.

Tx NORMAL means that the protocol handler controls the radio for

normal Modbustransmissions.

Tx TEST means that the protocol handler will send continuous text

strings of “TX TEST”. This string is transmitted as an asynchronous

message with 8 bit, no parity, 1 stop bit, 1 start bit format.

Range: Tx NORMAL, Tx TEST

Factory default is Tx NORMAL.

Busy Idle

Busy Asserted

BUSY Signal Status

The status of the BUSY signal into the CAPM (Display only)

“BUSY Idle” indicates that the signal is in the ‘not BUSY’ state.

“BUSY Asserted” indicates that the signal is in the ‘BUSY’ state. This

usually means that the radio squelch has opened.

Range: Busy Idle, Busy Asserted

Busy Disabled

Busy Enabled

Busy Signal Usage

The “Busy Disabled” mode is used when there is no busy signal

available. Eg A twisted pair link. When set to this mode, the protocol

uses any received data to build a Modbus frame. The protocol is able to

transmit at any time.

The “Busy Enabled” mode is the normal operating mode for radio

systems that have a busy signal available. When set to this mode, the

protocol will only read data and build Modbus frames when busy is

asserted. In addition, the protocol will not transmit when busy is asserted.

This reduces clashes with voice users.

Range: Busy Disabled, Busy Enabled

Factory default is Busy Disabled

Busy when input

low

Busy when input

Polarity of Busy Signal

This field determines the polarity of the input signal from the radio (P10

pin 6) that the CAPM uses as BUSY.

“Busy when input low” means that a low input signal will assert BUSY.

“Busy when input high” means that a high input signal will assert

(13)

ENABLED

DISABLED

When ENABLED the protocol handler inserts a string of characters in

front of a message packet. The message frame is otherwise not affected.

Start of frame filtering at the master station will ensure identification of

the message. This parameter is sometimes required for modems to aid

with their keying.

When DISABLED the protocol handler does not insert any preamble

characters.

Range: ENABLED, DISABLED

Factory default is DISABLED

First Char

Preamble First Character

This is the first character to be transmitted as a preamble. The character

is specified by entering its ASCII code in hexadecimal format.

Range: is 0 to FF hexadecimal.

Factory default is 0x55

Repeat First

Number of Preamble First Characters

This is the number of times the first character will be repeated as part of

the preamble.

Eg if all preamble settings are at default values then the preamble sent is

0x55, 0x55, 0x55, 0xFF

Range: 0 to 20.

Factory default is 3

Last Char

Last Character of Preamble

This is the last char that will be sent as part of the preamble. The

character is specified by entering its ASCII code in hexadecimal format.

Range: is 0 to FF hexadecimal.

Factory default is 0xFF

6.3.3 V23 Handshaking Signals

The V23 interface uses two signals, PTT from the CAPM, and Busy to the CAPM.

The PTT signal is used to key up a half-duplex radio transmitter. At the start of transmission the

CAPM asserts the PTT line and signals logic 1 for the pre-transmission time. It then transmits the

data blocks. Once the data has been sent it asserts logic 1 for the post-transmission time and then

negates PTT. Some radio systemsdo not require a PTT signal.

The Busy signal can utilise the squelch signal from a radio that indicates that the channel is busy. If

the communications equipment does not have such a signal then “Busy Disabled” should be

selected.

If a busy signal is available then the “Busy Enabled” should be set. In this mode the polarity of the

busy signal must be correctly set to match the operation of the radio. This is done with the “Busy

when input high/low” parameter.

When “Busy Enabled” is selected and Busy is asserted the protocol handler will…

• Process all characters coming in on the receive line and attempt to decode these as Modus

frames. This prevents attempting to process channel noise in the absence of radio carrier.

• Delay all transmissions until Busy is negated. This avoids clashes with other channel users.

6.4 Communication Statistics

The communication statistics give communication information, such as CRC errors, bytes not being

sent, received or processed or frames being incorrectly addressed. The communication statistics

page appears as below:

(14)

Rx Protocol Error 0

Statistic Description

Tx Count OK

Transmission Message Count

The number of messages transmitted from this recloser into the

communication link.

Range: 0 to 99999

Rx Count OK

Receive Message Count

The number of messages received by this recloser from the

communication link.

Range: 0 to 99999

Rx Protocol Error

Receive Message Protocol Error Count

The number of messages received with protocol related errors such

as CRC or parity.

Range: 0 to 9999

All of the above counters are zeroed when the CAPM is reset or the reset all button is selected in

Windows SOS. Any field can be cleared individually via the control operator panel by selecting it

and pressing either the left or right keys.

(15)

Initialisation Time

The protocol handler will not respond to master station requests for several seconds after power up

whilst it waits for the CAPM database to be initialised and for high priority boot up tasks to be

completed.

Turnaround Time

The turnaround time for the protocol, from the end of receiving a message until the start of the

pre-transmission time, is typically < 30 milliseconds with a range of 5 to 100 milliseconds.

Latency of Data

The protocol task examines the real-time database every 500 milliseconds to see if anything has

changed and to construct the underlying protocol database that is sent to the master station. This

introduces a delay between the actual event and updating the protocol database of up to 500

milliseconds. This is the data latency.

(16)

Supported Function Codes

Function Code

Dec Hex

Meaning

Support

01

01

Read Coil Status ( Read Discrete Output )

No

02

02

Read Input Status ( Read Discrete Inputs )

Yes

03

03

Read Holding Registers ( Read Multiple Registers )

Yes

04 04

Read

Input

Registers

No

05

05

Force Single Coil ( Write Single Output )

Yes

06

06

Preset Single Register ( Write Single Register )

Yes

07

07

Read Exception Status

No

08

08

Loopback Diagnostic Test

No

09 09

Program

No

10

0A

Poll Program Complete

No

11

0B

Get Communications Event Counter

No

12

0C

Get Communications Event Log

No

13 0D

Program

No

14

0E

Poll Program Complete

No

15

0F

Write Multiple Outputs

No

16

10

Write Multiple Registers

No

17

11

Report Slave ID

No

18 12

Program

No

19

13

Reset Communications Link

No

20

14

Read General Reference

No

21

15

Write General Reference

No

Mode of Transmission

This implementation of the Modbus protocol uses the Remote Terminal Unit (RTU) Framing.

Exceptions

A read of a non-existent coil or register will return an exception.

Broadcast Messages

(17)

The phase designation A, B, C is determined by the user, refer to the equipment manual for more information. Phase terminology is explained in section 2.3.

W series support is indicated below by a ‘Y’. If indicated as ‘N’ then value is always OFF.

Modbus Implementation

Request Code(s): 02 (Read Input Status) Reply Codes(s): 02 (Read Input Status) Error Code: 0x82

Exception Code: 01 (Illegal Function), 02 (Illegal Data Address), 03 (Illegal Data Value), 04 (Slave Device Failure)

ACR Recloser and Controller State Flags

Bit Name

W Series

Set = ‘1’ Cleared = ‘0’ Comment

0 Abnormal Operator

conditions Y For any of the following conditions:- • Trip or Close

Isolated, • ACR

Mechanically locked open (if applicable) • Work Tag Applied

None of the specified

conditions are true This flag shows that the operator has the ACR in an abnormal state such as “work tag applied”. This means that it will operate differently to its normal mode of operation.

1 Maintenance Required Y For any of the following conditions:- • Battery not normal • Capacitor charge

failure

• Low power mode • Low SF6 gas

pressure (if applicable) • ACR data not

valid (includes connection to an invalid switch type) • Any vacuum interrupter contact life is less than 20%

• Mechanical failure

No maintenance required

The controller has detected one or more conditions which require maintenance. This point cannot become Set until at least five minutes after controller start.

2 Auxiliary Supply Fail

Y Auxiliary supply has failed

Auxiliary supply is normal

(18)

3 Control Mode Y Local Control Enabled Remote Control Disabled Local control Disabled Remote control Enabled

The controller is either in Local or Remote control mode. This affects the closing command the permission to set/remove work tag.

4 ACR Tripped (open) Y ACR Tripped ACR not Tripped 5 ACR Closed Y ACR Closed ACR not Closed

These are repeats of the mechanism travel switches. When the ACR is

disconnected from the control cubicle they are both cleared. 6 Phase Ai Live Y 7 Phase Bi Live N 8 Phase Ci Live N 9 Phase Ax Live Note 1 Y 10 Phase Bx Live Note 1 N 11 Phase Cx Live Note 1 N

Phase is live Phase is dead Shows if the phase bushings are above or below the live line threshold. Phase designation is determined by user.

12 Source Voltage Status Y All of the source side Terminals dead 13 Load Voltage Status Y

Shows that any of the three phases of the designated Source side

or Load side are live. All of the load side Terminal dead

Note that these points are different to the Load/Source Live/Dead events in the controller event record 14 Load Current On

Note 1

Y Current of 2.5A or more is flowing in at least one phase

Current of less than 2.5A is flowing in all three phases 15 Reserved

16 Power Flow Direction Y Source X, Load I Source I, Load X 17 Reserved

18 Reserved 19 Reserved

20 Locked Y ACR Locked. ACR not locked. Shows that the ACR is mechanically locked in position. Not supported on the N-Series where it will always be zero.

21 ACR Memory Data Invalid

Y ACR Memory Data

not valid ACR Memory Data Valid Shows that the controller has retrieved the data from the ACR memory. When invalid the switchgear attributes and the gas pressure are zeroed,

(19)

22 Switchgear Connection Y Switch disconnected

from control cubicle. Switch connected from control cubicle. Shows the connection state of the cable between the switchgear and the controller. When connected to the ACR Trip, Close and Locked indications are valid. When disconnected from the ACR data will be forced invalid

23 Contacts Life Low Y When any vacuum interrupter contact life is less than 20%.

When all vacuum interrupters have contact life >= 20% 24 SF6 Gas Pressure Low

or Invalid N Gas pressure Low or Invalid Gas Pressure Normal, or Not Known, or Not a switchgear which has SF6.

Only set when switchgear is connected and ACR memory data is valid and switchgear type has SF6. 25 Close Isolate Y Close Isolate Switch

OFF/ISOLATE(i.e. Close is disabled)

Close Isolate Switch ON/ENABLE (i.e. Close is enabled) 26 Trip Isolate Y Trip Isolate Switch

OFF (i.e. Trip is disabled)

Trip Isolate Switch ON(i.e. Trip is enabled)

Shows the state of the Trip and Close isolate switches on the control panel

27 Work Tag Y Work Tag Applied Work Tag Removed The controller can have a work tag. This affects the closing command 28 Battery Supply Y Battery supply not

normal. This includes :- Battery Off Battery Overvolt Battery Low Volts

Battery supply normal

29 Capacitor Charge Failure Y Capacitor Charge

Failed Capacitor Charge OK The Trip/Close Capacitors have failed to charge 30 Mechanism Failure Y Mechanism Failure Mechanism OK The switchgear has failed to

Trip or Close electrically 31 Dummy Circuit Breaker

Closed Y DCB Closed DCB Not Closed The dummy circuit breaker is an internal point useful for SCADA system testing. The value of the DCB is non-volatile.

32 Reserved 33 Supply Outage

Measurement Y Supply Outage Measurement is ON. Supply Outage Measurement is OFF.

34 Door Open Y Door Open. Door Closed. Status of cubicle door. Only valid if hardware option installed.

(20)

36 Auxiliary Supply Fail

Delayed Y Auxiliary supply has failed for more than 120sec.

Auxiliary supply restored for more than 20sec.

Status of controller auxiliary supply (delayed).

37 Reserved 38 Reserved 39 Reserved Note

1. Not available with standard U series ACR without external CVTs, always 0

ACR Protection Group Flags

Bit Name

W Series

Set = ‘1’ Cleared = ‘0’ Comment

40 Prot A Active Y Protection Group A is

active Protection Group A is not active

Only one protection group is active at any one time.

41 Prot B Active Y Protection Group B is

active Protection Group B is not active 42 Prot C Active Y Protection Group C is

active Protection Group C is not active 43 Prot D Active Y Protection Group D is

active Protection Group D is not active 44 Prot E Active Y Protection Group E is

active Protection Group E is not active 45 Prot F Active Y Protection Group F is

active Protection Group F is not active 46 Prot G Active Y Protection Group G is

active Protection Group G is not active 47 Prot H Active Y Protection Group H is

active Protection Group H is not active 48 Prot I Active Y Protection Group I is

active Protection Group I is not active 49 Prot J Active Y Protection Group J is

active Protection Group J is not active

ACR Automation Flags

Bit Name

W Series

Set = ‘1’ Cleared = ‘0’ Comment

50 ACO Auto Restore

Y ACO Auto Restore is ON.

ACO Auto Restore is OFF. 51 ACO Enable Y Auto-Changeover is

(21)

52 ACO Mode Y Auto-Changeover is set

to Break before Make. Auto-Changeover is set to Make before Break.

The logic required for an ACO operation.

53 ACO Rank Y Auto-Changeover is set

to Master. Auto-Changeover is set to Slave operation.

The ACO hierachy setting for the Controller.

54 Generator

Control Y Generator Control is ON. Generator Control is OFF.

Generator Control Enable.

55 Reserved

ACR Protection Operation Flags

This group of points indicates what happened in the last protection sequence. For example the recloser may have tripped, closed, tripped again and locked out. Or it may have tripped, closed and stayed closed because the fault was cleared.

In both cases the flags below are set to show the causes of the trips and whether the lockout state has been reached or not.

A set of flags is available for each trip in a protection sequence.

In addition analogue data is available which shows the fault currents which occurred during the sequence and the number of trips which took place (refer Appendix C.2)

Note that a sequence starts when there is a protection trip or a sequence advance.

Most of these flags are cleared either by protocol command or when the switchgear is tripped/closed by the operator or when a new protection sequence starts.

This data is volatile i.e. it is zeroed on controller software reset.

Bit Name

W Series

Set = ‘1’ Cleared = ‘0’ Comment

56 Sequence in

Progress Y Start of sequence ie a protection trip of a sequence advance has occurred

End of sequence. Either lockout or reclaim.

This shows that a protection sequence has started and not yet completed.

Note that operator trip does not cause a “sequence in progress.

Event time is the time of the trip or sequence advance. 57 Protection Data

Valid Y End of sequence either lockout or reclaim All fault flags are cleared by one of the following actions :- • “Reset Fault Flags

and Currents” protocol control command

• Any Operator Close action

• Controller software reset

• Start of a new sequence

This shows that the protection sequence is over and the other flags are set.

This could be used to drive an operator alarm at the SCADA system to alert him to the fact that a protection sequence has occurred. Note that operator trip alone does not cause a “protection data valid” Event time is the time of lockout or reclaim.

(22)

58 Single Shot Protection

Y Single Shot Protection was active at the time of the trip.

One flag only provided because a single shot trip forces lockout.

Event time is the time of the pickup.

59 Loss Of Phase Trip Y Trip was caused by Loss of Phase Protection

sequence

One flag only provided because LOP protection forces lockout.

Event time is the time of the trip.

60 Loss Of Phase -

Phase A Lost Y Phase A was lost at time of Loss of Phase Trip

Set if A Phase is lost at time of Loss of Phase trip 61 Loss Of Phase -

Phase B Lost

N Phase B was lost at time of Loss of Phase Trip

Set if B Phase is lost at time of Loss of Phase trip 62 Loss Of Phase

-Phase C Lost N Phase C was lost at time of Loss of Phase Trip

Set if C Phase is lost at time of Loss of Phase trip 63 High Current

Lockout

Y The high current lockout function forced the controller to lockout during the last

protection sequence

One flag only because High Current Lockout forces lockout Time stamp as for flags above. Event time is the time of the lockout event. 64 Lockout Y The controller is in

lockout Cleared by any close action This flag shows that the controller is in lockout. Therefore no auto-reclosing will take place.

If the ACR is closed this flag will clear. Therefore when this flag is clear and the ACR is closed it indicates that the protection sequence cleared the fault.

65 Operator Trip Y The last trip was caused by a local or remote operator

Cleared by any close

action One flag only because operator trip forces lockout. 66 Last Trip Phase

Overcurrent Y The most recent protection operation was caused by a Phase Overcurrent Protection Trip

67 Last Trip Earth/Ground Overcurrent

Y The most recent protection operation was caused by an Earth/Ground

Overcurrent Protection Trip

Protection Flags are cleared by one of the following actions:- • “Reset Fault Flags

and Currents” protocol command • Operator Close • At the time of the

next trip – the flags are ‘refreshed’ at this time old flags

(23)

68 Last Trip SEF/SGF Overcurrent

Y The most recent protection operation was caused by an SEF/SGF Overcurrent Protection Trip

this time – old flags are cleared and the cause of the ‘most recent’ protection operation set. • Protection turned

OFF

69 Operator Close Y Most recent close caused by local or remote panel close request.

Indicates the most recent close was caused by a local or remote panel close request.

70 IOEX Close Y Most recent close caused by an IOEX close input.

Indicates the most recent close was caused by an IOEX close input. 71 Protocol Close Y Most recent close

caused by a protocol close request.

Cleared by one of the following actions: • 'Reset Flags and Currents' protocol command. • Controller Software

Reset (data is volatile). • At the time of the

next Close. • Start of a new

sequence.

Indicates the most recent close was caused by a protocol close request. 72 Automation Close Y Most recent close

caused by a Distributed Automation Close request.

Cleared by one of the following actions • 'Reset Flags and

Currents' protocol command. • Controller Software

Reset (data is volatile). • At the time of the

next Close.

Indicates the most recent close was caused by a Distributed Automation Close request (ie Loop Automation, Auto Changeover, or Generator Control).

73 Normal Frequency Close

Y Most recent close caused by Normal Frequency Close request.

Cleared by one of the following actions: • 'Reset Flags and Currents' protocol command. • Controller Software

Reset (data is volatile). • At the time of the

next Close.

Indiciates the most recent close was caused by a Normal Frequency Close request

(24)

74 External Close Y Set if any of the following caused the most recent close: • CCEM external button on N-Series. • Mechanical action. The switchgear detected as closed without a close reques. • Electrical action (only available on the Advanced controller).

Cleared by one of the following actions: • 'Reset Flags and Currents' protocol command. • Controller Software

Reset (data is volatile). • At the time of the

next Close.

The most recent close caused by an action external to the Controller.

75 Under Frequency

Protection Flag Protection operation was caused by Under Frequency

76 Over Frequency

Protection Flag Protection operation was caused by Over Frequency

Protection Flags are cleared by one of the following actions:- • “Reset Fault Flags

and Currents” protocol command • Operator Close • At the time of the

next trip – the flags are ‘refreshed’ at this time – old flags are cleared and the cause of the ‘most recent’ protection operation set. • Protection turned

OFF 77 Last Trip External Y Last Trip caused by

either a FTI or an IOEX Protection Input.

Protection Flags are cleared by one of the following actions:- • "Reset Fault Flags

and Currents" protocol command. • Operator Close. • At the time of the

next trip the flags are 'refreshed' at this time old flags are cleared and the cause of the 'most recent' protection operation set. • Protection turned OFF. • Start of a new sequence.

(25)

78 Last Trip Phase Overcurrent (Close Reset)

Y The last trip was caused by a Phase Overcurrent Fault.

This flags whether the last trip was caused by a Phase Overcurrent Fault. 79 Last Trip

Earth/Ground Overcurrent (Close Reset)

N The last trip was caused by an Earth/Ground Overcurrent Fault.

This flags whether the last trip was caused by an Earth/Ground Overcurrent Fault.

80 Last Trip SEF/SGF Overcurrent (Close Reset)

N The last trip was caused by an

SEF/SGF Overcurrent Fault.

These flags are cleared by one of the following actions:

• "Reset Fault Flags and Currents" protocol control command. • Any Close action. • Controller software

reset (data is volatile).

This flags whether the last trip was caused by an SEF/SGF Overcurrent Fault.

81 Most Recent Trip Phase A

Overcurrent

Y The most recent trip was caused by a A Phase Overcurrent Protection Trip 82 Most Recent Trip

Phase B Overcurrent

N The most recent trip was caused by a B Phase Overcurrent Protection Trip 83 Most Recent Trip

Phase C Overcurrent

N The most recent trip was caused by a C Phase Overcurrent Protection Trip 84 Instantaneous Most

Recent Trip Y The peak current for the most recent trip was greater than the instantaneous setting.

Protection Flags are cleared by one of the following actions:- • “Reset Fault Flags

and Currents” protocol command • Operator Close • At the time of the

next trip – the flags are ‘refreshed’ at this time – old flags are cleared and the cause of the ‘most recent’ protection operation set. • Protection turned

OFF 85 Source Dead Y Set if a lockout caused

by the ‘Dead Lockout’ Feature occurred.

Cleared by:

• protocol command • any operator close

or operator trip. This includes remote control commands. • start of a new

sequence. The time stamp reflects this. 86 Work Tag Trip Y Trip while Work Tag or

Hot Line Tag applied. Cleared by: • Operator Close • At the time of the

next trip the flags are ‘refreshed’, at this time old flags are cleared and the cause of the ‘most recent’ protection operation set. • Protection turned

(26)

87 Live Load Block Occurred

Y Set if the most recent close request was blocked due to a Live Load condition.

Cleared by one of the following actions: • 'Reset Flags and Currents' protocol command. • Controller Software Reset (data is volatile). • Protection OFF. • At the time of the

next Close.

ACR Operator/Protection Flags

Bit Name

W Series

Set = ‘1’ Cleared = ‘0’ Comment

88 Earth / Ground Protection Enabled

N Earth / Ground Protection ON

Earth / Ground Protection OFF 89 SEF/SGF Protection Enabled N SEF/SGF protection ON

SEF/SGF protection OFF 90 Auto Reclose Y Auto Reclose ON Auto Reclose OFF 91 Loss of Phase

Alarm Setting Y Loss of Phase Protection, if ON, is set to alarm only (ie. no Trip will occur).

Loss of Phase Protection, if ON, is set to normal operation (ie. will Trip). 92 Cold Load Idle Y Cold Load is Idle or is

turned off. This means that the threshold multiplier is not being affected by the cold load function.

Cold load is NOT Idle. This means that the threshold multiplier is being raised by the cold load pickup function in order to pick up cold load. 93 High Current

Lockout

Y High current lockout ON

High current lockout OFF 94 Loss of Phase

Protection N Loss of Phase Protection ON Loss of Phase Protection OFF 95 Sequence

Control

Y Sequence Control ON

Sequence Control OFF 96 Live Load

blocking

Y Live Load blocking ON Live Load blocking OFF 97 Protection

enable

Y Protection Enabled Protection turned OFF 98 Automatic Protection Group Selection Y Automatic Protection Group Selection ON Automatic Protection Group Selection OFF

(27)

99 Normal Frequency Close Note 1 Y The Under/Over Frequency protection has “Normal Frequency Close” ON

The Under/Over Frequency protection has “Normal Frequency Close” OFF 100 Dead Lockout Y Dead Lockout Setting

is ON

Dead Lockout Setting is OFF

101 LOP / Loop N LOP / Loop Linked LOP / Loop Unlinked 102 Under Frequency Trip Note 1 Y The Under/Over Frequency protection “Under Frequency Trip” is enabled.

The Under/Over Frequency protection “Under Frequency Trip” is disabled. 103 Over Frequency Trip Note 1 Y The Under/Over Frequency protection “Over Frequency Trip” is enabled.

The Under/Over Frequency protection “Over Frequency Trip” is disabled.

Note 1 Under/Over Frequency Protection unavailable on CAPM-4

ACR Accumulated Protection Trip Operation Flags

Multiple Flags can be set in this section because they accumulate all the trips in the sequence

Bit Name

W Series

Set = ‘1’ Cleared = ‘0’ Comment

104 Phase Over Current Trip

Y One or more trips were caused by Phase Overcurrent Protection

All fault flags are cleared by one of the following actions :-

• “Reset Fault Flags and Currents” protocol control command 105 Earth / Ground Over Current Trip

N One or more trips were caused by Earth / Ground Overcurrent Protection

• Any Operator Close action

106 SEF/SGF Over Current Trip

N One or more trips were caused by Sensitive Earth / Ground Fault Protection

• Controller software reset (data is volatile) 107 Sequence

Advance

Y One or more sequence

advances occurred. • Start of a new sequence

(28)

108 A Phase Pickup Y A phase A pickup has

been detected The pick up condition has reset 109 B Phase Pickup N A phase B pickup has

been detected The pick up condition has reset 110 C Phase Pickup N A phase C pickup has

been detected The pick up condition has reset 111 Earth/Ground

Pickup N An earth/ground pickup has been detected The pick up condition has reset 112 SEF/SGF

Pickup

N A SEF/SGF pickup has

been detected The pick up condition has reset 113 Under

Frequency Pickup

N An under frequency pickup has been detected

The pick up condition has reset

114 Over Frequency Pickup

N An over frequency pickup has been detected

The pick up condition has reset

115 Accumulated Phase Overcurrent Trip

Y One or more trips were caused by Phase Overcurrent protection.

This flags whether a Phase Overcurrent Trip occured. This flag can be set at the same time as other accumulated flags. 116 Accumulated

Earth/Ground Overcurrent Trip.

N One or more trips were caused by

Earth/Ground

Overcurrent protection.

This flags whether an Earth/Ground Overcurrent Trip occured. This flag can be set at the same time as other accumulated flags. 117 Accumulated

SEF/SGF Overcurrent Trip

N One or more trips were caused by Sensitive Earth/Ground fault protection.

This flags whether an SEF/SGF Overcurrent Trip occurred. This flag can be set at the same time as other accumulated flags. 118 Accumulated

Sequence Advance

Y One or more sequence advances occurred.

All fault flags are cleared by one of the following actions:

• "Reset Fault Flags and Currents" protocol control command. • Any operator close

action.

• Controller software reset (data is volatile). • Start of a new

sequence.

This flags whether a Sequence Advance ocurred. This flag can be set at the same time as other accumulated flags. 119 NPS Alarm N A NPS fault has been

picked up. If NPS protection is on, a trip will have occurred.

The fault flag is cleared by one of the following actions:

• "Reset Fault Flags and Currents" protocol control command. • The NPS current level

falls below the pickup value.

• Controller software reset (data is volatile).

This flags that a NPS fault has been picked up.

(29)

120 Accumulated NPS Overcurrent Trip.

N One or more trips were caused by NPS Overcurrent protection.

All fault flags are cleared by one of the following actions:

• "Reset Fault Flags and Currents" protocol control command. • Any operator close

action.

• Controller software reset (data is volatile). • Start of a new

sequence.

This flags whether an NPS Overcurrent Trip occured. This flag can be set at the same time as other accumulated flags.

121 LOP Alarm N A LOP condition has been detected. If LOP protection was on, a trip would have occurred.

The flag is cleared by one of the following actions: • The LOP condition is

removed.

• Controller software reset (data is volatile).

This flags that a LOP condition has been detected but LOP tripping is Off.

ACR NPS Flags

Bit Nam e W Series Set = ‘1 Cleared = ‘0 Com m ent an d Time Resolu tio n 122 Protection Flag – NPS Overcurrent

N The most recent protection operation was caused by an NPS Overcurrent Protection Trip.

Protection Flags are cleared by one of the following actions:- • "Reset Fault Flags and

Currents" protocol command. • Operator Close. • At the time of the next

protection trip the flags are 'refreshed'. Old flags are cleared and the cause of the 'most recent' protection operation set.

• Protection turned OFF.

Indicates if the most recent protection operation was caused by an NPS Overcurrent Protection Trip.

(30)

123 Last Trip NPS N The Last Trip was caused by a NPS overcurrent fault.

Last Trip Flags are cleared by one of the following actions:-

• "Reset Fault Flags and Currents" protocol command. • Operator Close. • Protection turned OFF. • Start of a new

sequence.

• At the time of the next trip the flags are 'refreshed'. Old flags are cleared and the cause of the 'most recent' trip set. • Controller reset 124 NPS Overcurrent Trip 1 N NPS Overcurrent Protection Trip 1 125 NPS Overcurrent Trip 2 N NPS Overcurrent Protection Trip 2 126 NPS Overcurrent Trip 3 N NPS Overcurrent Protection Trip 3 127 NPS Overcurrent Trip 4 N NPS Overcurrent Protection Trip 4

Protection Flags are cleared by one of the following actions:-

• "Reset Fault Flags and Currents" protocol command. • Operator Close. • Protection turned OFF. • Start of a new sequence. • Controller reset. 128 Last Trip NPS Overcurrent (Close Reset)

N The last trip was caused by an NPS Overcurrent Fault.

These flags are cleared by one of the following actions:

• "Reset Fault Flags and Currents" protocol control command. • Any Close action. • Protection turned OFF. • Controller software

reset (data is volatile). 129 Reserved

130 Reserved 131 Reserved

ACR Loop Automation Flags

These flags are only valid when the Loop Automation option is enabled for the current CAPM configuration. They are otherwise always reported as OFF.

(31)

132 Loop Auto On N Loop Automation is On Loop Automation is Off 133 Auto Restore

On N Auto Restore is On Auto Restore is Off 134 Loop Auto

Tie Restore On

N The Tie recloser is configured to restore supply in both directions

The Tie Recloser will only restore supply to its Load side or the Recloser type is not set to Tie 135 Loop Auto

Type Feeder

N Recloser type is set to Feeder Recloser type is not set to Feeder 136 Loop Auto

Type Midpoint

N Recloser type is set to

Midpoint Recloser type is not set to Midpoint 137 Loop Auto

Type Tie

N Recloser type is set to Tie Recloser type is not set to Tie 138 Loop Auto

Trip Pending

N Loop automation has issued a Trip Request

A loop automation trip is not pending

139 Loop Auto Close Pending

N Loop automation has issued a

Close Request A loop automation close is not pending 140 Loop Auto

Trip Request

N Set when Loop Automation issues a Trip Request.

Normal state, cleared on next internal scan after set 141 Loop Auto

Close Request

N Set when Loop Automation

issues a Close Request. Normal state, cleared on next internal scan after set 142 Reserved

143 Reserved

ACR Input Status

Bit Name

W Series

Set = ‘1’ Cleared = ‘0’ Comment

Protection Trip 1

144 Phase Over Current

Trip Y Trip was caused by Phase Overcurrent Protection

All fault flags are cleared by one of the following actions :-

• “Reset Fault Flags and Currents” protocol control command 145 Earth / Ground Over

Current Trip

N Trip was caused by Earth / Ground

Overcurrent Protection Any Operator Close action 146 SEF/SGF Over

Current Trip N Trip was caused by Sensitive Earth / Ground

Fault Protection Controller software reset 147 Sequence Advance Y Sequence advance

occurred. Start of a new sequence 148 Phase A Overcurrent

Trip Y Phase A Overcurrent Protection Trip 149 Phase B Overcurrent

Trip N Phase B Overcurrent Protection Trip 150 Phase C Overcurrent

Trip N Phase C Overcurrent Protection Trip

Cleared by:

• protocol command • any operator close or

operator trip. This includes remote control commands.

(32)

151 Instantaneous Trip Flag

N

Peak Fault Current for trip was above the instantaneous multiplier setting. control commands. • start of a new sequence. The time stamp reflects this.

Set at the instant of the most recent trip peak current event if the peak current for the trip was greater than the instantaneous setting.

Four of these flags are provided: one for each trip in the sequence. Protection Trip 2

152 Phase Over Current

Trip Y Trip was caused by Phase Overcurrent Protection

All fault flags are cleared by one of the following actions :-

• “Reset Fault Flags and Currents” protocol control command 153 Earth / Ground Over

Current Trip

N Trip was caused by Earth / Ground Overcurrent Protection

Any Operator Close action 154 SEF/SGF Over

Current Trip N Trip was caused by Sensitive Earth / Ground

Fault Protection Controller software reset 155 Sequence Advance Y Sequence advance

occurred. • Start of a new sequence 156 Phase A Overcurrent

Trip Y Phase A Overcurrent Protection Trip 157 Phase B Overcurrent Trip N Phase B Overcurrent Protection Trip 158 Phase C Overcurrent Trip N Phase C Overcurrent Protection Trip 159 Instantaneous Trip

Flag N Peak Fault Current for trip was above the instantaneous multiplier setting.

Cleared by:

• protocol command • any operator close or

operator trip. This includes remote control commands. • start of a new sequence. The time stamp reflects this.

Set at the instant of the most recent trip peak current event if the peak current for the trip was greater than the instantaneous setting.

Four of these flags are provided: one for each trip in the sequence. Protection Trip 3

160 Phase Over Current

Trip Y

Trip was caused by Phase Overcurrent Protection

All fault flags are cleared by one of the following actions :-

• “Reset Fault Flags and Currents” protocol control command 161 Earth / Ground Over

Current Trip N Trip was caused by Earth / Ground Overcurrent Protection

• Any Operator Close action

(33)

162 SEF/SGF Over Current Trip

N Trip was caused by Sensitive Earth / Ground Fault Protection

• Controller software reset

163 Sequence Advance Y Sequence advance occurred. • Start of a new sequence 164 Phase A Overcurrent Trip Y Phase A Overcurrent Protection Trip 165 Phase B Overcurrent Trip N Phase B Overcurrent Protection Trip 166 Phase C Overcurrent

Trip N Phase C Overcurrent Protection Trip 167 Instantaneous Trip

Flag N

Peak Fault Current for trip was above the instantaneous multiplier setting.

Cleared by:

• protocol command • any operator close or

operator trip. This includes remote control commands. • start of a new sequence. The time stamp reflects this.

Set at the instant of the most recent trip peak current event if the peak current for the trip was greater than the instantaneous setting.

Four of these flags are provided: one for each trip in the sequence. Protection Trip 4

168 Phase Over Current Trip

Y

Trip was caused by Phase Overcurrent Protection

All fault flags are cleared by one of the following actions :-

• “Reset Fault Flags and Currents” protocol control command 169 Earth / Ground Over

Current Trip N Trip was caused by Earth / Ground Overcurrent Protection

• Any Operator Close action

170 SEF/SGF Over

Current Trip N Trip was caused by Sensitive Earth / Ground Fault Protection

• Controller software reset

171 Reserved

172 Phase A Overcurrent

Trip Y Phase A Overcurrent Protection Trip 173 Phase B Overcurrent

Trip N Phase B Overcurrent Protection Trip 174 Phase C Overcurrent

Trip N Phase C Overcurrent Protection Trip 175 Instantaneous Trip

Flag

N

Peak Fault Current for trip was above the instantaneous multiplier setting.

Cleared by:

• protocol command • any operator close or

operator trip. This includes remote control commands. • start of a new

sequence. The time stamp reflects this.

Set at the instant of the most recent trip peak current event if the peak current for the trip was greater than the instantaneous setting.

Four of these flags are provided: one for each trip in the sequence.

(34)

W Series

176 IOEX Input 1 Y Input Asserted Input Not Asserted 177 IOEX Input 2 Y Input Asserted Input Not Asserted 178 IOEX Input 3 Y Input Asserted Input Not Asserted 179 IOEX Input 4 Y Input Asserted Input Not Asserted 180 IOEX Input 5 Y Input Asserted Input Not Asserted 181 IOEX Input 6 Y Input Asserted Input Not Asserted 182 IOEX Input 7 Y Input Asserted Input Not Asserted 183 IOEX Input 8 Y Input Asserted Input Not Asserted 184 IOEX Input 9 Y Input Asserted Input Not Asserted 185 IOEX Input 10 Y Input Asserted Input Not Asserted 186 IOEX Input 11 Y Input Asserted Input Not Asserted 187 IOEX Input 12 Y Input Asserted Input Not Asserted

Returned State changes after 30ms debounce.

(35)

terminology is explained in section 2.3.

W series: support is indicated in tables below by a ‘Y’. If indicated as ‘N’ then value is always 0.

Scaling

Modbus analogue values are transmitted as a 16 bit value with an additional sign bit. Where the CAPM range of analogue values exceeds the range of a 16 bit number (-32768 to 32767) the values are scaled.

All analogue values are scaled with 1 count = 1 Resolution/Units. In other words, 1 transmitted count = raw value ÷ resolution. For example: a phase voltage of 1000V will be transmitted as a count of 250 (=1000 ÷ 4)

The transmitted value must therefore be re-scaled at the master station before being displayed to the SCADA operator, logged, etc.

Modbus Implementation

Request Code(s): 03 (Read Holding Registers) Reply Codes(s): 03 (Read Holding Registers) Error Code: 0x83

Exception Code: 01 (Illegal Function), 02 (Illegal Data Address), 03 (Illegal Data Value), 04 (Slave Device Failure) ACR Line Currents

Note that these relate to user-designated phases rather than the physical bushings.

Ho lding Regis ter Nam e W Series Min Ma x Reso lution/ Units 0 A-Phase Current Y 0 16000 1 A 1 B-Phase Current N 0 16000 1 A 2 C-Phase Current N 0 16000 1 A

3 (Earth / Ground) Current Note 1 N 0 16000 1 A

Note

1) Not available for a standard U-series ACR without external CVTs. Value is always zero. ACR Voltage Measurements

Voltages are provided either for all 6 Terminals or for only 3 Terminals depending upon the model of ACR.

Ho lding Regis ter Nam e W Series Min Ma x Reso lution/ Units

4 Ai Phase-(Earth / Ground) Voltage Y 0 40000 2 V 5 Bi Phase-(Earth / Ground) Voltage N 0 40000 2 V 6 Ci Phase-(Earth / Ground) Voltage N 0 40000 2 V 7 Ax Phase-(Earth / Ground) Volts

Note 1

Y 0 40000 2 V

8 Bx Phase-(Earth / Ground) Volts

Note 1

N 0 40000 2 V

9 Cx Phase-(Earth / Ground) Volts

Note 1

N 0 40000 2 V

10 A-Bi Phase-Phase Voltage N 0 40000 2 V 11 B-Ci Phase-Phase Voltage N 0 40000 2 V

References

Related documents