Sie sind auf Seite 1von 73

NU-LEC INDUSTRIES PTY LTD

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

COPYRIGHT NU-LEC INDUSTRIES PTY LTD 2001

Nu-Lec Industries Pty Ltd. 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

Revision

Author

Revision Control

Date

Comment

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.

R04

PJM

24/10/03

Removed reference to Frame Timeout. Added new appendix for CAPM2 N00-321 & N00-360 emulation.

R05

PJM

28/11/03

Altered the Mapping selection field Corrected N00-321/N00-360 Digital Status Word 2

Content

1 Introduction

4

 

2 Overview

4

2.1 Data Types

4

 

2.2 Controls

4

2.3 Terminology

4

2.4 LBS vs ACR Point

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

Appendix F.2 Controls Available over Modbus

72

1

Introduction

This document describes the Modbus implementation for Nu-Lec Automatic Circuit Reclosers (ACRs) and Load Break Switches (LBSs) on Control and Protection Module types 4 & 5 (CAPM). 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.

2.4

LBS vs ACR Point Mapping.

The Modbus protocol handler supports independent point maps for the ACR and LBS switchgear types. The mapping for each is listed in the appendices. The type supported by the protocol handler 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.

5.1

Protocol Parameter Configuration

These pages allow the SCADA engineer to configure the Modbus protocol parameters.

---- 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) (Refer to Appendix D) (Refer to Appendix E) (Refer to Appendix F) (Refer to Appendix F)

CAPM4/5 LBS

CAPM2

424

CAPM2

321

CAPM2

360

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.

6.2.2

RS-232 Character Definition

RS-232 characters are 8 bit, with 1 stop bit. Parity is optional, and can be configured to either none, odd or even.

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

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

P8 RS-232

P10 V23

RUNNING

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

INACTIVE

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.

--------

Modbus Communications 2 ------

Parity

EVEN

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 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

DCD Don’t

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

1 19200 baud is not available on CAPM4 controllers

ENABLED

message. ENABLED means that the preamble characters are transmitted prior to a protocol message. DISABLED means that protocol message are transmitted without any preamble characters. Range: ENABLED, DISABLED Factory default is DISABLED

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

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.

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

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

P10 Pin

Direction

Use

15 Way D Female

     

5

5

-

Signal Ground

4

4

To CAPM

Receive, 10kOhm impedance Sensitivity 0.1V to 2V pk-pk

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

OFF

P8 RS-232

P10 V23 FSK

Description

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.

Also, the Modbus Communications 1 and 2 pages are automatically updated to reflect relevant FSK data
Also, the Modbus Communications 1 and 2 pages are automatically updated to reflect relevant FSK data
 

Range: OFF, P8 RS-232, P10 V23 FSK Factory default is P8 RS-232

RUNNING

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

INACTIVE

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

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.

Tx TEST

Busy Idle

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 Asserted

Busy Disabled

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 Enabled

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 lowmeans that a low input signal will assert BUSY. Busy when input high” means that a high input signal will assert

high

BUSY. Range: Busy when input low, Busy when input high. Factory default is Busy when input low

Pre-amble

Preamble Usage 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

ENABLED

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:

--- Modbus Communication Statistics ---

582

Rx Protocol Error 0

Tx Count OK

582 Rx Count OK

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. All communication statistic parameters are not password protected.

Appendix A Protocol Timings

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.

Modbus Protocol Technical Manual

Appendix B Modbus Implementation Table

This version of the Modbus protocol handler implements the following sub-set of the Modbus function codes:

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 Broadcast messages are not supported. A slave address of zero is invalid.

Modbus Protocol Technical Manual

Appendix C - ACR Modbus Points

Appendix C.1 ACR Modbus - Digitial Inputs

These points show the state of the switchgear and/or the controller. 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

Y

For any of the following conditions:-

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.

conditions

Trip or Close Isolated,

 

ACR Mechanically locked open (if applicable)

Work Tag Applied

 

1

Maintenance Required

Y

For any of the following conditions:-

No maintenance

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

required

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

2

Auxiliary Supply

Y

Auxiliary supply has failed

Auxiliary supply is normal

 

Fail

Modbus Protocol Technical Manual

Bit

Name

W Series

Set = ‘1’

Cleared = ‘0’

Comment

3

Control Mode

Y

Local Control

Local control

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

Enabled

Disabled

Remote Control

Remote control

Disabled

Enabled

4

ACR Tripped (open)

Y

ACR Tripped

ACR not Tripped

These are repeats of the mechanism travel switches. When the ACR is disconnected from the control cubicle they are both cleared.

5

ACR Closed

Y

ACR Closed

ACR not Closed

6

Phase Ai Live

Y

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.

7

Phase Bi Live

N

8

Phase Ci Live

N

9

Phase Ax Live

Y

Note 1

10

Phase Bx Live

N

 

Note 1

11

Phase Cx Live

N

Note 1

12

Source Voltage Status

Y

Shows that any of the three phases of the

All of the source side Terminals dead

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

13

Load Voltage Status

Y

designated Source side or Load side are live.

All of the load side Terminal dead

14

Load Current On

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

 

Note 1

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,

Modbus Protocol Technical Manual

Bit

Name

W Series

Set = ‘1’

Cleared = ‘0’

 

Comment

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)

Shows the state of the Trip

and

Close isolate switches

on the control panel

26

Trip Isolate

Y

Trip Isolate Switch OFF (i.e. Trip is disabled)

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

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

Capacitor Charge OK

The Trip/Close Capacitors have failed to charge

Failed

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

Y

Supply Outage Measurement is ON.

Supply Outage Measurement is OFF.

 

Measurement

34

Door Open

Y

Door Open.

Door Closed.

Status of cubicle door. Only valid if hardware option installed.

35

Switch Function

Y

Function is ACR

Function is LBS

 

Modbus Protocol Technical Manual

Bit

Name

W Series

Set = ‘1’

Cleared = ‘0’

Comment

36

Auxiliary Supply Fail Delayed

Y

Auxiliary supply has failed for more than

Auxiliary supply restored for more than

Status of controller auxiliary supply (delayed).

120sec.

20sec.

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

Y

ACO Auto Restore is ON.

ACO Auto Restore is OFF.

 

Restore

51

ACO Enable

Y

Auto-Changeover is

Auto-Changeover is OFF.

 

ON.

Modbus Protocol Technical Manual

Bit

Name

W Series

Set = ‘1’

Cleared = ‘0’

Comment

 

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

Y

Generator Control is ON.

Generator Control is OFF.

Generator Control Enable.

Control

 

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

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.

Progress

57

Protection Data

Y

End of sequence either lockout or reclaim

All

fault

flags are

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

Valid

cleared by one of the

 

following actions :-

“Reset Fault Flags and Currents” protocol control command

This could be used to drive an operator alarm at the SCADA system to alert him to the fact that a protection sequence has

Any Operator Close action

occurred. Note that operator trip alone does not cause a

Controller software reset

“protection data valid” Event time is the time of lockout or reclaim.

Start of a new se uence

Modbus Protocol Technical Manual

Bit

Name

W Series

Set = ‘1’

Cleared = ‘0’

Comment

58

Single Shot

Y

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

sequence

One flag only provided because a single shot trip forces lockout. Event time is the time of the pickup.

Protection

59

Loss Of Phase Trip

Y

Trip was caused by Loss of Phase Protection

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

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.

Lockout

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

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

 

“Reset Fault Flags and Currents”

67

Last Trip

Y

The most recent protection operation was caused by an Earth/Ground Overcurrent Protection Trip

protocol command

 

Earth/Ground

Operator Close

Overcurrent

At the time of the next trip – the flags are ‘refreshed’ at ti

thi

ld fl

Modbus Protocol Technical Manual

Bit

Name

W Series

Set = ‘1’

 

Cleared = ‘0’

Comment

68

Last Trip

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.

 

SEF/SGF

Overcurrent

 

Protection turned OFF

69

Operator Close

Y

Most recent close caused by local or remote panel close request.

Cleared by one of the following actions:

Indicates the most recent close was caused by a local

or remote panel close

'Reset Flags and Currents' protocol

request.

70

IOEX Close

Y

Most recent close caused by an IOEX close input.

 

command.

Indicates the most recent

Controller Software

close was caused by an IOEX close input.

 

Reset (data is volatile).

71

Protocol Close

Y

Most recent close caused by a protocol close request.

 

At the time of the next Close.

Indicates the most recent close was caused by a

 

Start of a new sequence.

protocol close request.

72

Automation Close

Y

Most recent close caused by a Distributed Automation Close request.

Cleared by one of the following actions

 

Indicates the most recent

'Reset Flags and Currents' protocol command.

close was caused by a Distributed Automation Close request (ie Loop

 

Controller Software Reset (data is volatile).

Automation, Auto Changeover, or Generator Control).

At the time of the next Close.

73

Normal Frequency

Y

Most recent close caused by Normal Frequency Close request.

Cleared by one of the following actions:

 

Close

'Reset Flags and Currents' protocol command.

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

 

Controller Software Reset (data is volatile).

request

At the time of the next Close.

Modbus Protocol Technical Manual

Bit

Name

W Series

 

Set = ‘1’

Cleared = ‘0’

Comment

74

External Close

Y

Set if any of the following caused the most recent close:

Cleared by one of the following actions:

 

'Reset Flags and

CCEM external button on N- Series.

Currents' protocol command.

Controller Software

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

Mechanical action. The switchgear detected as closed without a close reques.

Reset (data is volatile).

At the time of the next Close.

 

Electrical action (only available on the Advanced controller).

75

Under Frequency

 

Protection operation was caused by Under Frequency

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

 

Protection Flag

76

Over Frequency

 

Protection operation was caused by Over Frequency

“Reset Fault Flags and Currents” protocol command

Operator Close

 

Protection Flag

 

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.

Modbus Protocol Technical Manual

Bit

Name

W Series

Set = ‘1’

Cleared = ‘0’

Comment

78

Last Trip Phase Overcurrent (Close Reset)

Y

The last trip was caused by a Phase Overcurrent Fault.

These flags are cleared by one of the following actions:

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

79

Last Trip

N

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

"Reset Fault Flags and Currents" protocol control command.

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

Earth/Ground

Overcurrent (Close

Reset)

Any Close action.

80

Last Trip SEF/SGF Overcurrent (Close Reset)

N

The last trip was caused by an SEF/SGF Overcurrent Fault.

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

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

 

“Reset Fault Flags

82

Most Recent Trip Phase B Overcurrent

N

The most recent trip was caused by a B Phase Overcurrent Protection Trip

and Currents” protocol command

 

Operator Close

 

At the time of the

83

Most Recent Trip Phase C Overcurrent

N

The most recent trip was caused by a C Phase Overcurrent Protection Trip

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

 

84

Instantaneous Most

Y

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

cause of the ‘most recent’ protection operation set.

Protection turned OFF

 

Recent Trip

85

Source Dead

Y

Set if a lockout caused

Cleared by:

 

protocol command

by the ‘Dead Lockout’ Feature occurred.

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 OFF.

Modbus Protocol Technical Manual

Bit

Name

W Series

Set = ‘1’

Cleared = ‘0’

Comment

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.

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

N

SEF/SGF protection

SEF/SGF protection OFF

 

Protection

ON

Enabled

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

Y

High current lockout ON

High current lockout OFF

 

Lockout

94

Loss of Phase Protection

N

Loss of Phase Protection ON

Loss of Phase Protection OFF

 

95

Sequence

Y

Sequence

Sequence Control OFF

 

Control

Control ON

96

Live Load

Y

Live Load blocking ON

Live Load blocking OFF

 

blocking

97

Protection

Y

Protection Enabled

Protection turned OFF

 

enable

98

Automatic

Y

Automatic Protection Group Selection ON

Automatic Protection Group Selection OFF

 

Protection

Group Selection

   

ACR Operator/Protection Flags

Modbus Protocol Technical Manual

Bit

Name

W Series

Set = ‘1’

Cleared = ‘0’

Comment

99

Normal

Y

The Under/Over Frequency protection has “Normal Frequency Close” ON

The Under/Over Frequency protection has “Normal Frequency Close” OFF

 

Frequency

Close

Note 1

 

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

Y

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

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

 

Frequency Trip

Note 1

103

Over Frequency

Y

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

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

 

Trip

Note 1

Bit

Name

W Series

Set = ‘1’

Cleared = ‘0’

Comment

104

Phase Over

Y

One or more trips were caused by Phase Overcurrent Protection

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

 

Current Trip

 

“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

N

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

 

Current Trip

Controller software reset (data is volatile)

107

Sequence

Y

One or more sequence advances occurred.

Start of a new sequence

 

Advance

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

ACR Protection Pickup Flags

Modbus Protocol Technical Manual

Bit

Name

W Series

 

Set = ‘1’

Cleared =

‘0’

Comment

and Time

Resolution

108

A Phase Pickup

Y

A

phase A pickup has

The pick up condition has reset

 

been detected

109

B Phase Pickup

N

A

phase B pickup has

The pick up condition has reset

 

been detected

110

C Phase Pickup

N

A

phase C pickup has

The pick up condition has reset

 

been detected

111

Earth/Ground

N

An earth/ground pickup

The pick up condition has reset

 

Pickup

has been detected

112

SEF/SGF

N

A

SEF/SGF pickup has

The pick up condition has reset

 

Pickup

been detected

113

Under

N

An under frequency

The pick up condition has reset

 

Frequency

pickup has been

Pickup

detected

 

114

Over Frequency

N

An over frequency

The pick up condition has reset

 

Pickup

pickup has been

detected

 

115

Accumulated

Y

One or more trips were

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

This flags whether a Phase Overcurrent Trip occured. This flag can be set at the

Phase

caused by Phase

Overcurrent