GE Grid Solutionsgridautomation.pl/dane/Dokumentacja PDF/1.Zabezpieczenia... · 2017. 4. 18. · GE...

GEGrid Solutions

Product version: 7.41x

GE publication code: 1601-0401-AE1 (GEK-130990)

UR FamilyCommunications Guide

1601-0401-AE1

LISTED

IND.CONT. EQ.

E83849

Copyright © 2017 GE Multilin Inc. All rights reserved.

UR Family Communications Guide for version 7.41x.

UR Family, EnerVista, Multilin, and GE Multilin are trademarks or registered trademarks of GE Multilin Inc.

The contents of this manual are the property of GE Multilin Inc. This documentation is furnished on license and may not be reproduced in whole or in part without the permission of GE Multilin. The content of this manual is for informational use only and is subject to change without notice.

Part number: 1601-0401-AE1 (January 2017)

UR FAMILY – COMMUNICATIONS GUIDE iii

UR Family

Table of contents

1 INTRODUCTION 1.1 Products ............................................................................................................ 1-11.2 Features per product ...................................................................................... 1-11.3 Communication ports...................................................................................1-141.4 Safety symbols and definitions...................................................................1-141.5 For further assistance ..................................................................................1-14

2 MODBUS COMMUNICATION

2.1 Modbus RTU protocol...................................................................................... 2-12.1.1 Introduction............................................................................................................................. 2-12.1.2 Configuration.......................................................................................................................... 2-12.1.3 Physical layer.......................................................................................................................... 2-12.1.4 Data link layer ........................................................................................................................ 2-22.1.5 Modbus RTU CRC-16 algorithm..................................................................................... 2-3

2.2 Modbus function codes .................................................................................. 2-42.2.1 Supported function codes................................................................................................ 2-42.2.2 Read actual values or settings (function code 03/04h)...................................... 2-42.2.3 Execute operation (function code 05h) ...................................................................... 2-52.2.4 Store single setting (function code 06h) .................................................................... 2-52.2.5 Store multiple settings (function code 10h) ............................................................. 2-62.2.6 Exception responses........................................................................................................... 2-6

2.3 File transfers..................................................................................................... 2-72.3.1 Obtaining relay files using Modbus.............................................................................. 2-7

2.4 Memory map ..................................................................................................2-112.4.1 Modbus memory map......................................................................................................2-112.4.2 Data formats .....................................................................................................................2-179

3 IEC 61850 COMMUNICATION

3.1 Overview ........................................................................................................... 3-13.1.1 Introduction............................................................................................................................. 3-13.1.2 Abstract Communication Service Interface (ASCI)................................................ 3-33.1.3 Datasets.................................................................................................................................... 3-63.1.4 TxGOOSE................................................................................................................................... 3-73.1.5 RxGOOSE .................................................................................................................................. 3-93.1.6 Reports ....................................................................................................................................3-103.1.7 Commands............................................................................................................................3-123.1.8 Substation Configuration Language (SCL)..............................................................3-12

iv UR FAMILY – COMMUNICATIONS GUIDE

TABLE OF CONTENTS

3.2 Configuring the UR using SCL......................................................................3-183.2.1 Merge SCL file ......................................................................................................................3-233.2.2 Configurable logical devices.........................................................................................3-24

3.3 Protocol implementation conformance statement (PICS) .....................3-243.3.1 Basic conformance statement ....................................................................................3-24

3.4 ACSI conformance statement .....................................................................3-253.4.1 ACSI basic conformance statement .........................................................................3-253.4.2 ACSI models conformance statement .....................................................................3-253.4.3 ACSI services conformance statement ...................................................................3-27

3.5 Model implementation conformance statement (MICS).........................3-293.5.1 Master (root) logical device ...........................................................................................3-303.5.2 Protection (Prot) logical device ....................................................................................3-383.5.3 Control (Ctrl) logical device ......................................................................................... 3-1123.5.4 System logical device.................................................................................................... 3-1443.5.5 Meter logical device....................................................................................................... 3-1583.5.6 General (Gen) logical device....................................................................................... 3-1793.5.7 GE namespace ................................................................................................................. 3-1933.5.8 Enumerations.................................................................................................................... 3-207

3.6 SCL implementation conformance statement (SICS) ............................3-2083.7 PIXIT conformance statement...................................................................3-2103.8 TICS conformance statement....................................................................3-2153.9 SCL logging ...................................................................................................3-217

3.9.1 Overview of process ...................................................................................................... 3-2173.9.2 SCL file storage on UR................................................................................................... 3-2183.9.3 Generation Of CID files ................................................................................................. 3-2183.9.4 Schema version used by UR/EnerVista ................................................................ 3-2183.9.5 CID file processing steps.............................................................................................. 3-2183.9.6 SCL log file format and examples ........................................................................... 3-2183.9.7 Troubleshooting log file errors.................................................................................. 3-220

3.10 G2 implementation model for GOOSE configuration via SCL..............3-2203.10.1 Introduction ....................................................................................................................... 3-2203.10.2 Configuration process .................................................................................................. 3-2213.10.3 Configuration process with IED setup tool.......................................................... 3-2233.10.4 IED Capability Description (ICD) file......................................................................... 3-2233.10.5 Instantiated IED capability description (IID) file ................................................ 3-2273.10.6 Configured IED description (CID) file....................................................................... 3-2273.10.7 Sample SCL files............................................................................................................... 3-2293.10.8 Annex - Optional intermediate GOOSE reception objects ........................... 3-234

3.11 E3-2.0 implementation model for GOOSE configuration via SCL........3-2373.11.1 Introduction ....................................................................................................................... 3-2373.11.2 Workflow............................................................................................................................. 3-2373.11.3 ICD files ................................................................................................................................ 3-2383.11.4 CID files ................................................................................................................................ 3-2393.11.5 IID files.................................................................................................................................. 3-240

4 DNP COMMUNICATION

4.1 Device profile document ................................................................................ 4-14.1.1 Implementation table .........................................................................................................4-4

4.2 DNP point lists................................................................................................4-104.2.1 Binary input points ............................................................................................................4-104.2.2 Binary and control relay output ..................................................................................4-104.2.3 Counters.................................................................................................................................4-124.2.4 Analog inputs .......................................................................................................................4-12

TABLE OF CONTENTS

UR FAMILY – COMMUNICATIONS GUIDE v

5 IEC 60870-5-103 COMMUNICATION

5.1 Overview ........................................................................................................... 5-15.2 Factor and offset calculation to transmit measurand ............................. 5-15.3 Interoperability document............................................................................. 5-2

6 IEC 60870-5-104 COMMUNICATION

6.1 Interoperability document............................................................................. 6-16.2 IEC 60870-5-104 points.................................................................................6-10

A MISCELLANEOUS A.1 Revision history ...............................................................................................A-1

INDEX

vi UR FAMILY – COMMUNICATIONS GUIDE

TABLE OF CONTENTS

UR FAMILY – COMMUNICATIONS GUIDE 1-1

UR Family

Chapter 1: Introduction

Introduction

This document outlines the communications protocols for the Universal Relay (UR) family of products. It is intended for customers who need detailed knowledge of the UR implementation of the communications protocols, for example to design a client or to troubleshoot an interoperability issue. Use this guide with the appropriate Instruction Manual for the product. Network and IP address configuration, passwords, and user roles, for example, are explained in the Instruction Manual.

This chapter outlines general, safety, and technical support information.

1.1 ProductsThis document applies to the following UR products: B30, B90, C30, C60, C70, D30, D60, F35, F60, G30, G60, L30, L60, L90, M60, N60, T35, T60.

The communications protocols that apply depend on those ordered. Check the order code of the device.

1.2 Features per productThe table outlines the theoretical maximum.

Features also can be viewed in the EnerVista software under Settings > Protection Summary.

Table 1-1: Maximum number of elements per product

Feature Rule Max B30 B90 C30 C60 C70 D30 D60 F35 F60 G30 G60 L30 L60 L90 M60 N60 T35 T60

Accidental Energization

1 1 1

1-2 UR FAMILY – COMMUNICATIONS GUIDE

FEATURES PER PRODUCT CHAPTER 1: INTRODUCTION

1 Automatic Voltage Regulator# of elements if voltage banks present; 0 if Enhanced Capacitor Bank Control software option not ordered

3 3

Autoreclose # of current banks; 0 for L30 when Three-Pole Auto-Reclose not ordered

6 1 6 4 1

Autoreclose 1P 3P

1 1 1 1 1

Auxiliary Overvoltage

# of elements; 1 per voltage bank and 3 if C70 has voltage banks

3 3 2 3 1 2 3 2 2 2 1 1 2 2 3

Auxiliary Undervoltage

#of elements if at least one voltage bank

3 3 3 3 3 3 3 3 3 3 3 3 3

B90 Breaker Failure

# of feeders from software option

24 24

B90 Bus Differential

# of zones from software option

6 6

Bus configuration

6 6

Saturation detector

6 6

B90 IOC # of current terminals

24 24

B90 TOC # of current terminals

24 24


CHAPTER 1: INTRODUCTION FEATURES PER PRODUCT


1B90 Undervoltage # of voltage terminals

12 12

Basic UR Features

Clock 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1

Control pushbuttons

7

Display properties

1

Default messages

1

LED test 1

Setting file template

1

Security 1

Trip and Alarm LEDs

1

Flex state parameters

256

User programmable self-tests

1

Installation

1

Voltage rail monitor

1

Temperature monitor

1

Breaker Arcing Current (I2t)

# of current banks; 2 if current banks < 2

6 6 4 3 2 2 6 4 2 2 2 2 4 2 6 6

Breaker Control

# of elements;2 if current banks < 2

6 6 2 4 3 2 4 6 4 2 2 2 2 4 2 6 6 6

(Disconnect) Breaker Switch

# of elements

24 24 8 16 12 8 16 24 16 8 8 8 8 24 8 24 24 24

Breaker Failure


6 6 4 3 4 4 2 2 2 4 2 6

Breaker Flashover


2 2 2 1 2 2 2 2 2 2 2 2




1 Breaker Restrike # of elements;2 if current banks < 2

6 6 4 3 2 6 4 2 2 4 2 6

Broken Conductor Detection

# of sources

6 2 2 6 2 2 2 2

Broken Rotor Bar

1 1

Bus Differential

2 2

Bus configuration

2

Saturation detector

2

Bus Replica Isolator

48 48

Capacitor Bank Overvoltage

# of elements

3 3

Capacitor Control

3 3

Change Phase Rotation

1 1 1

Charging Current Compensation

1 1

Cold Load Pickup

6 6 2

Compensated Bank Neutral Unbalance

# of current banks

3 3

Compensated Overvoltage

1 1 1 1

Cont. Monitor 1 1

Contact Inputs

# of inputs

96 96 96 96 96 96 96 96 96 96 96 96 96 96 96 96 96 96 96

Contact Outputs

Latching can be only 14

64 64 64 64 64 64 64 64 64 64 64 64 64 64 64 64 64 64 64

CT Fail # of current banks

6 2 4 4 4 4 2 4 4 4 6 6 6

CT Trouble # of zones from software option; 2 on B30

6 2 6

Current CT settings

# of CT banks

6 6 6 6 2 4 6 4 4 4 2 4 4 4 6 6 6

Current Terminal Metering

24 24




1Current Unbalance 2 2Data Logger 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1

Demand # of sources

6 6 4 4 6 4 4 4 4 6 6

Digital Counters

8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8

Digital Elements

48 48 48 48 48 48 48 48 48 48 48 48 48 48 48 48 48 48 48

Digitizer 5 5

Direct Inputs/Outputs

16 inputs and 8 outputs

1 1 1

Disturbance Detection

# of sources

6 6 4 6 2 4 6 4 4 4 2 4 4 4 6 6 6

Downed Conductor Detection (Hi-Z)

Available for 8Z DSP only; # of HIZ records is 4; # of RMS records is 4

1

EGD Protocol Fast production = 1; slow production = 2

1 1 1 1 1 1 1 1 1 1 1

End of Fault Protection

# of elements; 1 per CT terminal

24 24

Energy Metering

# of sources

6 6 4 4 6 4 4 4 4 4 6 6

Event Recorder

1024 events

1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1

Fault Location # of elements; 1 per current bank

5 1 1 1 5 2 1 1 1

Field Ground Protection

1 1




1 Field Resources 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1Field unit brick types

1

Field unit contact inputs

40

Field unit contact outputs

8

Field unit CT/VT settings

6

Field unit I/O states

1

Field unit latching outputs

8

Field unit raw data actuals

8

Field unit raw data settings

1

Field unit RTDs

8

Field unit shared inputs

16

Field unit shared outputs

16

Field unit transducers

8

Field units

8

FlexElements 16 8 8 8 16 8 8 16 8 16 16 8 8 8 16 16 16 16

FlexLogic Equations

1024 lines

1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1

Flexlogic timers

32

FlexMath 1

Direct analogs

32 32

Direct integers

16 16

Summator

6 6

Frequency Rate of Change

4 2 4 4 4 4 2 4 4 4

Generator Unbalance

1 1 1

Generic Comparator

8-bit comparator

6 6




1Ground Distance Fast distance is not available on L60

5 5 5 3 5 5

Ground Instantaneous Overcurrent

# of elements if at least one CT bank

12 6 8 12 2 6 12 6 1 1 4 4 8 6 12 12 12

Ground Time Overcurrent


6 6 4 6 2 4 6 4 1 1 2 2 4 4 6 6 6

IEC 61850 Communications

1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1

Configurable GOOSE Rx

16

Configurable GOOSE Tx

8

GGIO2 configuration

64

GGIO4 analog points

32

GGIO5 unsigned interger points

16

MMXU deadbands

6

Received analogs

32

Received integers

16

XCBR configuration

6

XSWI configuration

24

IPv4 Routes

6




1 IEC 61850 Remote I/O (Fixed GOOSE/GSSE/GOOSE)

1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1

Remote devices

32 16 16 32 16 16 16 16 16 16 16 16 16 16 16 16 16 16 16

Remote DPS inputs

5

Remote inputs

64 32 32 64 32 32 32 32 32 32 32 32 32 32 32 32 32 32 32

Remote output DNA pairs

32

Remote output UserSt pairs

32

IEC 103 Communications

1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1

Incipient Cable Fault

# of elements

6 1 6 2 1

L60 Channel Tests

1 1

Line Differential (87L) In-Zone Transformer

1 1 1

Line Differential (87L) L90

1 1

L90 Power system

1

87L trip logic

1

L90 phase select

1

L90 channels tests

1

Line Differential (87L)

No muti-end fault location

1

Line Pickup 1 1 1 1 1

Load Encroachment

1 1 1 1 1 1 1

Loss of Excitation

1 1 1

Modbus Communications

1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1

Modbus User Map

1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1

Motor Acceleration Time

1 1

Motor Mechanical Jam

1 1




1Motor Start Supervision 1 1Negative Sequence Directional OC

# of elements if at least one CT bank and one VT bank

3 2 2 2 2 2 2 2 2 3

Negative Sequence Instantaneous Overcurrent


3 2 2 2 2 2 2 2 2 3

Negative Sequence Overvoltage C70

# of voltage banks if at least one

3 3

Negative Sequence Overvoltage

# of elements if at least one voltage bank

3 3 3 3 3 3 3 3 3 3

Negative Sequence Time Overcurrent


3 2 2 2 2 2 2 2 2 3

Neutral Current Unbalance

# of current banks

3 3

Neutral Directional Overcurrent

3 1 2 2 2 2 2 2 2 2 2 3 3

Neutral Instantaneous Overcurrent

# of CT banks if at least one

6 6 1 1

Neutral Instantaneous Overcurrent


12 8 6 2 6 12 6 4 4 8 4 12 12

Neutral Overvoltage

# of elements if at least one VT bank

3 3 3 3 3 3 3 3 3 3 3 3 3 3 3

Neutral Time Overcurrent


6 6 4 3 2 4 6 4 2 2 2 2 4 2 6 6

Neutral Voltage Unbalance

# of voltage banks

3 3

Non Volatile Latches

16 16 16 16 16 16 16 16 16 16 16 16 16 16 16 16 16 16 16

Open Pole Detect (supervisory)

1 1




1 Oscillography 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1Over Under Frequency Accumulation

Frequency out of band

1 1 1

Overfrequency

4 4 4 4 4 4 4 4 4 4

Phase Comparison

1 1

Phase Current Unbalance

# of current banks

3 3

Phase Directional

# of elements if at least one CT and one VT bank

3 2 2 2 2 2 1 1 2 2 2 2 3 3

Phase Distance

L60 does not support fast distance (L60 must become fast distance)

5 5 5 3 3 5 5

Phase Instantaneous Overcurrent


12 12 8 6 2 6 12 6 4 4 4 4 8 4 12 12 12

Phase Overvoltage


3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3

Phase Time Overcurrent


6 6 4 3 2 4 6 4 2 2 2 2 4 4 6 6 6

Phase Undervoltage


3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3

PID Regulator 4 4 4




1Pilot Schemes 1Pilot blocking (1P)

Pilot blocking 1 (1P)

1 1

Pilot DCUB

1 1

Pilot DUTT (1P)

1 1

Pilot Hybrid POTT (1P)

1 1

Pilot POTT (1P)

1 1

Pilot POTT1 (1P)

1 1

Pilot PUTT (1P)

1 1

Pilot POTT

1 1 1

Pilot POTT3

1

Pilot blocking 3 (DCB3)

1

Platform Direct I/O

256 32 256 64 32 32 32 32 32 32 32 32 32 32 64 32 32

Power Swing Detect

1 1 1 1 1 1 1 1

Precision Time Protocol (1588)

3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3

Reduced Voltage Starting

1 1

Restricted Ground Fault

# of elements; 0 if L90 has no inzone transformer

6 4 4 4 4 6 6

RRTD Protection

12 12 12 12

RTD Protection

48 48 48 48

Security 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1

Selector Switch

2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2

Sensitive Directional Power


2 2 2 2 2 2 2 2 2 2

Setting Groups

6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6




1 Simple Network Time Protocol1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1

Single Pole Tripping

1 1 1 1 1

Open pole detect (1P)

Phase selection

Trip output

Sources (1 per CT/VT bank)

# of sources

6 6 4 6 2 4 6 4 4 4 2 4 4 4 6 6 6

Split Phase Protection

1 1 1

Stator Differential

1 1 1

Saturation detector

1

Stator Ground 1 1 1

Stub Bus 1 1 1

Subharmonic Stator Ground

1 1

Switch 6 6 6 6

Synchrocheck 10 10 4 10 4 4 4 4 4 10 6 6

Synchrophasors

# of PMUs; software option

6 2 1 1 1 1 1 6 1

# of Aggregators

4 2 1 1 1 1 1 4 1

Teleprotection I/O

1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1

Thermal Model

1 1

Motor setup

1

Thermal Overload Protection

2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2

Third Harmonic Neutral Undervoltage

1 1 1

Time of Day Timer

5 5

Transducer I/O

1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1

DCMA inputs

24

DCMA outputs

24

Ohm inputs

2

RTD inputs

48




1Transformer Instantaneous Differential

1 1 1

Transformer Percent Differential

1 1 1 1

Transformer windings

6 2 6 6

Transformer Thermal Model

1 1 1 1

Trip Bus 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6

Undercurrent 1 1

Underfrequency

6 6 6 6 6 6 6 6 6 6 6 6 6

UnderPower 2 2

User-Programmable Fault Report

2 2 2 2 2 2 2 2 2 2

User-Programmable LEDs

48 48 48 48 48 48 48 48 48 48 48 48 48 48 48 48 48 48 48

User- Programmable Pushbuttons

# of pushbuttons; 16; 6 for vertical front panel

1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1

control push-buttons

3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3

User-Definable Displays

16 16 16 16 16 16 16 16 16 16 16 16 16 16 16 16 16 16 16

Virtual Inputs 64 64 64 64 64 64 64 64 64 64 64 64 64 64 64 64 64 64 64

Virtual Outputs

96 96 96 96 96 96 96 96 96 96 96 96 96 96 96 96 96 96 96

Voltage Differential

# of VT banks

3 3

Volts Per Hertz


2 2 2 2 2

VT Fuse Failure

# of sources if CT bank or VT bank

6 4 6 2 4 6 4 4 4 2 2 4 4 6 6

Wattmetric Ground Fault

# of elements

4 2 2 4 2 2 2



COMMUNICATION PORTS CHAPTER 1: INTRODUCTION

11.3 Communication portsURs are equipped with an RS232 port on the faceplate, a rear RS485 port, an IRIG-B input port, and three Ethernet ports. The Ethernet ports are a combination of 100Base-TX and 100Base-FX depending on the order code option. See the relevant Instruction Manual for information on these ports.

1.4 Safety symbols and definitionsBefore attempting to install or use the device, review all safety indicators in this document to help prevent injury, equipment damage, or downtime.

The following safety and equipment symbols are used in this document.

See the Instruction Manual for safety information.

1.5 For further assistanceFor product support, contact the information and call center as follows:

GE Grid Solutions650 Markland StreetMarkham, OntarioCanada L6C 0M1Worldwide telephone: +1 905 927 7070Europe/Middle East/Africa telephone: +34 94 485 88 54North America toll-free: 1 800 547 8629Fax: +1 905 927 5098Worldwide e-mail: [email protected] e-mail: [email protected]: http://www.gegridsolutions.com/multilin

Indicates a hazardous situation which, if not avoided, will result in death or serious injury.

Indicates a hazardous situation which, if not avoided, could result in death or serious injury.

Indicates a hazardous situation which, if not avoided, could result in minor or moderate injury.

Indicates practices not related to personal injury.

mailto:[email protected]://gegridsolutions.com/multilinmailto:[email protected]


UR Family

Chapter 2: Modbus communication

Modbus communication

This chapter outlines the Modbus protocol, which is a standard protocol used for communication among devices. Use the Modbus memory map provided when designing a client to access the UR device using Modbus.

2.1 Modbus RTU protocol

2.1.1 IntroductionThe UR family supports several communications protocols to allow connection to equipment such as personal computers, remote terminal units (RTUs), supervisory control and data acquisition (SCADA) masters, and programmable logic controllers. The Modicon Modbus protocol is the most basic protocol supported by the UR. Modbus RTU is available via the RS232 and RS485 serial links, and Modbus TCP/IP is available over Ethernet. The following description is intended primarily for users who want to develop their own master communication drivers. Note that:• The UR always acts as a slave device, meaning that it never initiates communications. It listens and responds to

requests issued by a master computer.• A subset of Modbus RTU and Modbus TCP/IP protocol format is supported that allows extensive monitoring,

programming, and control functions using read and write register commands.

2.1.2 ConfigurationThe Modbus slave address and TCP port number are configured during installation. See the Modbus Protocol section in the Settings chapter of the Instruction Manual.

The number of remaining Modbus TCP connections available can be viewed in the Actual Values > Status > Comm Status Remaining Connect option. The value is 4 when the EnerVista software is closed. See the Remaining Connection Status section in the Actual Values chapter of the Instruction Manual.

2.1.3 Physical layerThe Modbus RTU protocol is hardware-independent so that the physical layer can be any of a variety of standard hardware configurations including RS232 and RS485. The relay includes a faceplate (front panel) RS232 port and a rear terminal RS485 port. Data flow is half-duplex in all configurations. See chapter 3 of the Instruction Manual for communications wiring.


MODBUS RTU PROTOCOL CHAPTER 2: MODBUS COMMUNICATION

2

Each data byte is transmitted in an asynchronous format consisting of 1 start bit, 8 data bits, 1 stop bit, and possibly 1 parity bit. This produces a 10 or 11 bit data frame. This can be important for transmission through modems at high bit rates (11 bit data frames are not supported by many modems at baud rates greater than 300).

The faceplate RS232 port is intended for local use, with baud rate set at 115200 or 19200 bps under Settings > Product Setup > Communications > Serial Ports. The rear terminal RS485 port can be set for baud rates of 300, 1200, 2400, 4800, 9600, 14400, 19200, 28800, 33600, 38400, 57600, or 115200 bps, and even, odd, and no parity options are available. See the Communications section of chapter 5 in the Instruction Manual for details.

The Modbus TCP/IP protocol is available on each of the rear Ethernet ports. These ports are 100Base-FX.

2.1.4 Data link layerModbus RTU communications takes place in packets that are groups of asynchronously framed byte data. The master transmits a packet to the slave and the slave responds with a packet. The following information describes the general format for both transmit and receive packets. For details on packet formatting, see subsequent sections describing each function code.

Table 2-1: Modbus RTU packet format

SLAVE ADDRESS — This is the address of the slave device that is intended to receive the packet sent by the master and to perform the desired action. Each slave device on a communications bus must have a unique address to prevent bus contention. All of the relay’s ports have the same address which is programmable from 1 to 254; see chapter 5 in the Instruction Manual for details. Only the addressed slave will respond to a packet that starts with its address. Note that the faceplate port is an exception to this rule; it acts on a message containing any slave address.

A master transmit packet with slave address 0 indicates a broadcast command. All slaves on the communication link take action based on the packet, but none respond to the master.

FUNCTION CODE — This is one of the supported functions codes of the unit which tells the slave what action to perform. See the Supported function codes section on page 2-4 for details. An exception response from the slave is indicated by setting the high order bit of the function code in the response packet. See the Exception responses section on page 2-6 for details.

DATA — This is a variable number of bytes depending on the function code. It can include actual values, settings, or addresses sent by the master to the slave or by the slave to the master.

CRC — This is a two byte error checking code. The RTU version of Modbus includes a 16-bit cyclic redundancy check (CRC-16) with every packet which is an industry standard method used for error detection. If a Modbus slave device receives a packet in which an error is indicated by the CRC, the slave device does not act upon or respond to the packet thus preventing any erroneous operations. See the Modbus RTU CRC-16 algorithm section on page 2-3 for details on calculating the CRC.

DEAD TIME — A packet is terminated when no data is received for a period of 3.5 byte transmission times (about 15 ms at 2400 bps, 2 ms at 19200 bps, and 300 µs at 115200 bps). Consequently, the transmitting device must not allow gaps between bytes longer than this interval. Once the dead time has expired without a new byte transmission, all slaves start listening for a new packet from the master except for the addressed slave.

Modbus-TCP/IP communications takes place in application data units (ADUs), which are wrapped in the TCP/IP/Ethernet protocols. Ethernet provides layer 2 addressing and CRC-32 error checking. IP provides layer 3 addressing. TCP provides communication establishment and ending and manages data flow. The Parallel Redundancy Protocol (PRP) can also be used to provide seamless data flow in case of a single failure in the network, by using a combination of LAN duplication and frame duplication. See chapter 5 in the instruction manual for information on setting up TCP for Modbus (in the Modbus section), IP and PRP (Network section).

The ADU is described as follows.

Description Size

SLAVE ADDRESS 1 byte

FUNCTION CODE 1 byte

DATA N bytes

CRC 2 bytes

DEAD TIME 3.5 bytes transmission time

CHAPTER 2: MODBUS COMMUNICATION MODBUS RTU PROTOCOL


2

Table 2-2: Modbus TCP/IP format

MBAP header — This Modbus Application Protocol header contains the following fields:• Transaction Identifier: Used for transaction pairing. The Modbus server copies in the response the transaction

identifier of the request.• Protocol Identifier: Used for intra-system multiplexing. The Modbus protocol is identified by the value 0.• Length: The length field is a byte count of the following fields, including the Unit Identifier and data fields.

– Unit Identifier: For the purposes of the UR, this field is equivalent to the Modbus RTU SLAVE ADDRESS field. The client must use the same value here as programmed in the UR setting MODBUS SLAVE ADDRESS.

FUNCTION CODE — This is the same as the Modbus RTU function code field described above.

DATA — This is the same as the Modbus RTU data field described above.

2.1.5 Modbus RTU CRC-16 algorithmThe Modbus TPC/IP CRC-32 algorithm is universally executed in hardware, so there is no need to describe it here.

The Modbus RTU CRC-16 algorithm essentially treats the entire data stream (data bits only; start, stop and parity ignored) as one continuous binary number. This number is first shifted left 16 bits and then divided by a characteristic polynomial (11000000000000101b). The 16-bit remainder of the division is appended to the end of the packet, MSByte first. The resulting packet including CRC, when divided by the same polynomial at the receiver will give a zero remainder if no transmission errors have occurred. This algorithm requires the characteristic polynomial to be reverse bit ordered. The most significant bit of the characteristic polynomial is dropped, since it does not affect the value of the remainder.

A C programming language implementation of the CRC algorithm can be provided upon request.

Table 2-3: Modbus RTU CRC-16 algorithm

Description Size

MBAP header Transaction identifier 2 bytes

Protocol identifier 2 bytes

Length 2 bytes

Unit identifier 1 byte

FUNCTION CODE 1 byte

DATA N bytes

Symbols --> data transfer

A 16 bit working register

Alow low order byte of A

Ahigh high order byte of A

CRC 16 bit CRC-16 result

i,j loop counters

(+) logical EXCLUSIVE-OR operator

N total number of data bytes

Di i-th data byte (i = 0 to N-1)

G 16 bit characteristic polynomial = 1010000000000001 (binary) with MSbit dropped and bit order reversed

shr (x) right shift operator (th LSbit of x is shifted into a carry flag, a '0' is shifted into the MSbit of x, all other bits are shifted right one location)


MODBUS FUNCTION CODES CHAPTER 2: MODBUS COMMUNICATION

2

2.2 Modbus function codes

2.2.1 Supported function codesModbus officially defines function codes from 1 to 127 though only a small subset is generally needed. The relay supports some of these functions, as summarized in the following table. Subsequent sections describe each function code.

Table 2-4: Function codes

2.2.2 Read actual values or settings (function code 03/04h)This function code allows the master to read one or more consecutive data registers (actual values or settings) from a relay. Data registers are always 16-bit (two-byte) values transmitted with high order byte first. The maximum number of registers that can be read in a single packet is 125. See the Reading PMU records section on page 2-10 for the data registers.

Since some PLC implementations of Modbus only support one of function codes 03h and 04h. The UR interpretation allows either function code to be used for reading one or more consecutive data registers. The data starting address determines the type of data being read. Function codes 03h and 04h are therefore identical.

The following table shows the format of the master and slave packets in Modbus RTU. Modbus TCP/IP ADUs have a MBAP instead of slave address, and CRC is in another stack layer. The example shows a master device requesting three register values starting at address 4050h from slave device 11h (17 decimal); the slave device responds with the values 40, 300, and 0 from registers 4050h, 4051h, and 4052h, respectively.

Table 2-5: Master and slave device packet transmission example

Algorithm 1. FFFF (hex) --> A

2. 0 --> i

3. 0 --> j

4. Di (+) Alow --> Alow

5. j + 1 --> j

6. shr (A)

7. Is there a carry? No: go to 8; Yes: G (+) A --> A and continue.

8. Is j = 8? No: go to 5; Yes: continue

9. i + 1 --> i

10. Is i = N? No: go to 3; Yes: continue

11. A --> CRC

Function code Modbus definition GE Multilin definition

Hex Dec

03 3 Read holding registers Read actual values or settings

04 4 Read holding registers Read actual values or settings

05 5 Force single coil Execute operation

06 6 Preset single register Store single setting

10 16 Preset multiple registers Store multiple settings

Master transmission Slave response

Packet format Example (Hex) Packet format Example (Hex)

SLAVE ADDRESS 11 SLAVE ADDRESS 11

FUNCTION CODE 04 FUNCTION CODE 04

DATA STARTING ADDRESS - high 40 BYTE COUNT 06

DATA STARTING ADDRESS - low 50 DATA #1 - high 00

CHAPTER 2: MODBUS COMMUNICATION MODBUS FUNCTION CODES


2

2.2.3 Execute operation (function code 05h)This function code allows the master to perform various operations in the relay. Available operations are shown in the summary table below.

The following table shows the format of the master and slave packets in Modbus RTU. Modbus TCP/IP ADUs have a MBAP instead of slave address, and CRC is in another stack layer. The example shows a master device requesting the slave device 11h (17 decimal) to perform a reset. The high and low code value bytes always have the values “FF” and “00” respectively and are a remnant of the original Modbus definition of this function code.


Table 2-7: Summary of operation codes for function 05h

2.2.4 Store single setting (function code 06h)This function code allows the master to modify the contents of a single setting register in an relay. The following table shows the format of the master and slave packets in Modbus RTU. Modbus TCP/IP ADUs have a MBAP instead of slave address, and CRC is in another stack layer. The example shows a master device storing the value 200 at memory map address 4051h to slave device 11h (17 dec).

NUMBER OF REGISTERS - high 00 DATA #1 - low 28

NUMBER OF REGISTERS - low 03 DATA #2 - high 01

CRC - low A7 DATA #2 - low 2C

CRC - high 4A DATA #3 - high 00

DATA #3 - low 00

CRC - low 0D

CRC - high 60





OPERATION CODE - high 00 OPERATION CODE - high 00

OPERATION CODE - low 01 OPERATION CODE - low 01

CODE VALUE - high FF CODE VALUE - high FF

CODE VALUE - low 00 CODE VALUE - low 00

CRC - low DF CRC - low DF

CRC - high 6A CRC - high 6A

Operation code (Hex)

Definition Description

0000 NO OPERATION Does not do anything

0001 RESET Performs the same function as the faceplate RESET key0005 CLEAR EVENT RECORDS Performs the same function as the faceplate CLEAR EVENT RECORDS menu

command

0006 CLEAR OSCILLOGRAPHY Clears all oscillography records

1000 to 103F VIRTUAL IN 1 to 64 ON/OFF Sets the states of Virtual Inputs 1 to 64 either “ON” or “OFF”




MODBUS FUNCTION CODES CHAPTER 2: MODBUS COMMUNICATION

2


2.2.5 Store multiple settings (function code 10h)This function code allows the master to modify the contents of a one or more consecutive setting registers in a relay. Setting registers are 16-bit (two byte) values transmitted high order byte first. The maximum number of setting registers that can be stored in a single packet is 123. The following table shows the format of the master and slave packets in Modbus RTU. Modbus TCP/IP ADUs have a MBAP instead of slave address, and CRC is in another stack layer. The example shows a master device storing the value 200 at memory map address 4051h, and the value 1 at memory map address 4052h to slave device 11h (17 decimal).


2.2.6 Exception responsesProgramming or operation errors usually happen because of illegal data in a packet. These errors result in an exception response from the slave. The slave detecting one of these errors sends a response packet to the master with the high order bit of the function code set to 1.

The following table shows the format of the master and slave packets in Modbus RTU. Modbus TCP/IP ADUs have a MBAP instead of slave address, and CRC is in another stack layer. The example shows a master device sending the unsupported function code 39h to slave device 11h.





DATA STARTING ADDRESS - high 40 DATA STARTING ADDRESS - high 40

DATA STARTING ADDRESS - low 51 DATA STARTING ADDRESS - low 51

DATA - high 00 DATA - high 00

DATA - low C8 DATA - low C8

CRC - low CE CRC - low CE

CRC - high DD CRC - high DD





DATA STARTING ADDRESS - hi 40 DATA STARTING ADDRESS - hi 40

DATA STARTING ADDRESS - lo 51 DATA STARTING ADDRESS - lo 51

NUMBER OF SETTINGS - hi 00 NUMBER OF SETTINGS - hi 00

NUMBER OF SETTINGS - lo 02 NUMBER OF SETTINGS - lo 02

BYTE COUNT 04 CRC - lo 07

DATA #1 - high order byte 00 CRC - hi 64

DATA #1 - low order byte C8

DATA #2 - high order byte 00

DATA #2 - low order byte 01

CRC - low order byte 12

CRC - high order byte 62

CHAPTER 2: MODBUS COMMUNICATION FILE TRANSFERS


2


2.3 File transfers

2.3.1 Obtaining relay files using Modbus

2.3.1.1 DescriptionThe UR has a generic file transfer facility, meaning that you use the same method to obtain all of the different types of files from the unit. The Modbus registers that implement file transfer are found in the "Modbus File Transfer (Read/Write)" and "Modbus File Transfer (Read Only)" modules, starting at address 3100h in the Modbus Memory Map. To read a file from the UR, use the following steps:

1. Write the filename to the "Name of file to read" register using a write multiple registers command. If the name is shorter than 80 characters, you may write only enough registers to include all the text of the filename. Filenames are not case sensitive.

2. Repeatedly read all the registers in "Modbus File Transfer (Read Only)" using a read multiple registers command. It is not necessary to read the entire data block, since the UR remembers which was the last register you read. The "position" register is initially zero and thereafter indicates how many bytes (2 times the number of registers) you have read so far. The "size of..." register indicates the number of bytes of data remaining to read, to a maximum of 244.

3. Keep reading until the "size of..." register is smaller than the number of bytes you are transferring. This condition indicates end of file. Discard any bytes you have read beyond the indicated block size.

4. If you need to re-try a block, read only the "size of.." and "block of data", without reading the position. The file pointer is only incremented when you read the position register, so the same data block is returned as was read in the previous operation. On the next read, check to see if the position is where you expect it to be, and discard the previous block if it is not (this condition would indicate that the UR did not process your original read request).

The UR retains connection-specific file transfer information, so files may be read simultaneously on multiple Modbus connections.

2.3.1.2 Other protocolsAll the files available using Modbus can also be retrieved using the standard file transfer mechanisms in other protocols (for example, TFTP or Manufacturing Message Specification, MMS).

2.3.1.3 COMTRADE, oscillography, data logger, and PMU record filesOscillography, data logger, and PMU record files are formatted using the COMTRADE file format per IEEE C37.111 (1999 or 2013) Standard Common Format for Transient Data Exchange (COMTRADE) for Power Systems. The files can be obtained in either text or binary COMTRADE format.

The EnerVista UR Setup software includes the ability to work with COMTRADE files. Access File > COMTRADE Utility. See the Waveforms chapter of the EnerVista Viewpoint Monitoring Instruction Manual (accessible on the website) for information on how to use the tool.




FUNCTION CODE 39 FUNCTION CODE B9

CRC - low order byte CD ERROR CODE 01

CRC - high order byte F2 CRC - low order byte 93

CRC - high order byte 95


FILE TRANSFERS CHAPTER 2: MODBUS COMMUNICATION

2

Figure 2-1: COMTRADE utility

Preferences are set within the EnerVista software as follows.

To set COMTRADE waveform display preferences:

1. In the EnerVista software, click File > Preferences. The window opens. The preferences here affect only the type of file retrieved by the software from Actual Values > Records, by single-click in the software, or by oscillography. The same file can be retrieved in another format in the software under Maintenance > Retrieve File or some other means, such as TFTP or MMS, by requesting the file with the file name that reflects the format wanted.

2. Select the COMTRADE panel and set the options.IEEE 1999 — All UR releases support this standard. When this option is selected, no other options are selectable and 16 bit binary data are used.

Figure 2-2: Select the COMTRADE format

IEEE 2013 — UR 7.4 supports this standard.16 Bit Binary — UR 7.4 supports this.32 Bit Binary — UR 7.4 supports this.

CHAPTER 2: MODBUS COMMUNICATION FILE TRANSFERS


2

32 Bit Float — UR 7.4 supports this.Single-file (.CFF) — Supported by devices that support IEEE 2013, so UR 7.4 supports this. One file with .CFF extension instead of four separate .CFG, .INF, .HDR, and .DAT files.Multi-file (.CFG) — When IEEE 1999 is selected, this option is selected automatically. When IEEE 2013 is selected, choose between CFF or CFG format.

3. Click the Ok button to save and exit.

2.3.1.4 Reading oscillography filesFamiliarity with the oscillography feature is required to understand the following description. See the Oscillography section in chapter 5 of the Instruction Manual for details.

The "Oscillography Number of Triggers" register increments by one every time a new oscillography file is triggered (captured) and cleared to zero when oscillography data is cleared. When a new trigger occurs, the associated oscillography file is assigned a file identifier number equal to the incremented value of this register; the newest file number is equal to the "Oscillography Number of Triggers" register. This register can be used to determine if any new data has been captured by periodically reading it to see if the value has changed; if the number has increased then new data is available.

The "Oscillography Number of Records" register specifies the maximum number of files (and the number of cycles of data per file) that can be stored in memory of the relay. The "Oscillography Available Records" register specifies the actual number of files that are stored and still available to be read out of the relay.

Writing “Yes” (that is, the value 1) to the "Oscillography Clear Data" register clears oscillography data files, clears both the "Oscillography Number of Triggers" and "Oscillography Available Records" registers to zero, and sets the "Oscillography Last Cleared Date" to the present date and time.

For the IEEE 2013 standard, to read binary COMTRADE oscillography files, read the following filenames, where # stands for 16B, 32B, or 32F, and nnn stands for the oscillography trigger number.

Table 2-11: Oscillography records for IEEE C37.111-2013, by data format

For the IEEE 1999 standard, to read binary COMTRADE oscillography files, read the following files.

Table 2-12: Oscillography records for IEEE C37.111-1999, by data format

For HiZ records, only the ASCII 1999 format is supported.

2.3.1.5 Reading data logger filesFamiliarity with the data logger feature is required to understand this description. See the Data Logger section of chapter 5 in the Instruction Manual for details.

For IEEE 2013, to read the entire data logger in binary COMTRADE format, read the following files.

Table 2-13: Data logger records for IEEE C37.111-2013, by data format

For IEEE 1999, to read the entire data logger in binary COMTRADE format, read the following files.

BINARY BINARY32 FLOAT32 ASCII

Multiple files OSC16Bnnn.CFGOSC16Bnnn.DATOSC16Bnnn.HDR

OSC32Bnnn.CFGOSC32Bnnn.DATOSC32Bnnn.HDR

OSC32Fnnn.CFGOSC32Fnnn.DATOSC32Fnnn.HDR

OSC###Annn.CFGOSC###Annn.DATOSC###Annn.HDR

Single file OSC16Bnnn.CFF OSC32Bnnn.CFF OSC32Fnnn.CFF OSC###Annn.CFF

BINARY ASCII

Multiple files OSCnnn.CFGOSCnnn.DATOSCnnn.HDR

OSCAnnn.CFGOSCAnnn.DATOSCAnnn.HDR

BINARY BINARY32 FLOAT32 ASCII

Multiple files Datalog16B.CFGDatalog16B.DAT

Datalog32B.CFGDatalog32B.DAT

Datalog32F.CFGDatalog32F.DAT

Datalog###A.CFGDatalog###A.DAT

Single file Datalog16B.CFF Datalog32B.CFF Datalog32F.CFF Datalog###A.CFF


FILE TRANSFERS CHAPTER 2: MODBUS COMMUNICATION

2

Table 2-14: Data logger records for IEEE C37.111-1999, by data format

To limit the range of records to be returned in the COMTRADE files, append the following to the filename before writing it:• To read from a specific time to the end of the log: startTime• To read a specific range of records: startTime endTime• Replace and with the number of seconds since Jan. 1 1970 as numeric text

2.3.1.6 Reading event recorder filesTo read the entire event recorder contents in ASCII format (the only available format), use the following filename:

EVT.TXT

To read from a specific record to the end of the log, use the following filename:EVTnnn.TXT (replace nnn with the desired starting record number)

To read from a specific record to another specific record, use the following filename:EVT.TXT xxxxx yyyyy (replace xxxxx with the starting record number and yyyyy with the ending record number) Memory mapping

2.3.1.7 Reading fault report filesFault report data has been available via the UR file retrieval mechanism since UR firmware version 2.00. The file name is faultReport#####.htm. The ##### refers to the fault report record number. The fault report number is a counter that indicates how many fault reports have ever occurred. The counter rolls over at a value of 65535. The last 15 fault reports are available for retrieval. It starts from 1 to 15, then if you have 18 reports, 3 to 18 are retrieved. A request for a non-existent fault report file yields a null file. The current value fault report counter is available in "Number of Fault Reports" Modbus register at location 3020h.

For example, if 14 fault reports have occurred then the files faultReport5.htm, faultReport6.htm, up to faultReport14.htm are available to be read. The expected use of this feature has an external master periodically polling the "Number of Fault Reports' register. If the value changes, then the master reads all the new files.

The contents of the file is in standard HTML notation and can be viewed via any commercial browser.

2.3.1.8 Reading PMU recordsFor URs that support PMU, familiarity with the PMU recording feature is required to understand the following description. For example, see the PMU Recording and later sections in the N60 instruction manual.

The "PMU Recording Number of Triggers" register increments by one every time a new PMU record is triggered (captured) on any of the PMU units in the relay (depending on the software option in the order code up to six PMUs can be available in a relay). When a new trigger occurs, the associated PMU record file is assigned a file identifier based on the number of the PMU module, the incremented value of this register module 1000 and the format of the COMTRADE file, as described here. This register can be used to determine if any new data has been captured by periodically reading it to see if the value has changed; if the number has increased then new data can be available.

The file "PMU_Records_List.txt" lists the available PMU records in the relay. This file can be retrieved by TFTP. This file includes information about the file name for every PMU record in the relay.

The PMU records can be retrieved using the EnerVista software or by TFTP. The file name has the format

PMUp_xxxxn.eee

where

p is the PMU recorder instance

xxxx is the COMTRADE format shown in the following tables

n is the file sequence number in integer format from 1 to 999. The file sequence number is unique among all PMUs.

BINARY ASCII

Multiple files Datalog.CFGDatalog.DAT

DatalogA.CFGDatalogA.DAT

CHAPTER 2: MODBUS COMMUNICATION MEMORY MAP


2

eee is the extension (cfg, dat, hdr, cff)

For example, to retrieve file 7 from PMU 3 in binary 16 bit CFF format, retrieve the file PMU3_16B7.cff.

Table 2-15: PMU records for IEEE C37.111-2013, by data format

Table 2-16: PMU records for IEEE C37.111-1999, by data format

2.4 Memory map

2.4.1 Modbus memory mapThe table provides the Modbus memory map. The addresses in the table are expressed in hexadecimal. The particular registers actually present depend on the UR product and on the order codes software and module options.

The map is also viewable in a web browser. In the browser, enter the IP address of the UR and click the option.

In the table, "Grouped Setting" refers to content in the Settings > Grouped Elements > Group menus.

The data format tables that follow the memory map provide more information for some entries.

Table 2-17: Modbus memory map

Binary Binary32 Float32 ASCII

Multiple files PMUp_16Bn.cfgPMUp_16Bn.datPMUp_16Bn.hdr

PMUp_32Bn.CFGPMUp_32Bn.DATPMUp_32Bn.HDR

PMUp_32Fn.CFGPMUp_32Fn.DATPMUp_32Fn.HDR

PMUp_###An.cfgPMUp_###An.datPMUp_###An.hdr

Single file PMUp_16Bn.CFF PMUP_32Bn.CFF PMUp_32Fn.CFF PMUp_###An.cff

Binary ASCII

Multiple files PMUp_n.cfgPMUp_n.datPMUp_n.hdr

PMUp_An.cfgPMUp_An.datPMUp_An.hdr

Products Address Register name Range Units Step Format Default

Product Information (Read Only)

All 0000 UR Product Type 0 to 65535 --- 1 F001 0

" 0002 Product Version 0 to 655.35 --- 0.01 F001 1

" 0003 Boot Configuration Register 0 to 65535 --- 1 F001 0

Product Information (Read Only -- Written by Factory)

All 0010 Serial Number --- --- --- F203 “0”

" 0020 Manufacturing Date 0 to 4294967295 --- 1 F050 0

" 0022 Modification Number 0 to 65535 --- 1 F001 0

" 0040 Order Code --- --- --- F204 “Order Code x”

" 0090 Ethernet MAC Address --- --- --- F072 0

" 0093 Reserved (13 items) --- --- --- F001 0

" 00A0 CPU Module Serial Number --- --- --- F203 (none)

" 00B0 CPU Supplier Serial Number --- --- --- F203 (none)

" 00C0 Ethernet Sub Module Serial Number (8 items)

--- --- --- F203 (none)

Product Information (Read Only)

G60 0100 GPM-F Version 0 to 655.35 --- 0.01 F001 0

" 0101 GPM-F Compile Date 0 to 4294967295 --- 1 F050 0

" 0103 GPM-F Order Code --- --- --- F205 (none)

" 0109 GPM-F Serial Number --- --- --- F205 (none)


MEMORY MAP CHAPTER 2: MODBUS COMMUNICATION

2

" 010F GPM-F Hardware Revision 0 to 65535 --- 1 F001 0

Product Information (Read Only -- Written by Factory)

All 0110 FPGA Version --- --- --- F206 (none)

" 0113 FPGA Date 0 to 4294967295 --- 1 F050 0

Product Information (Read/Write Setting)

All 0120 Compatible Diagnostics Mode 0 to 1 --- 1 F102 0 (Disabled)

Self Test Targets (Read Only)

All 0200 Self Test States (4 items) 0 to 4294967295 0 1 F143 0

Front Panel (Read Only)

All 0208 LED Column n State, where n = 1 to 10 (10 items)

0 to 65535 --- 1 F501 0

" 0220 Display Message --- --- --- F204 (none)

" 0248 Last Key Pressed 0 to 47 --- 1 F530 0 (None)

Keypress Emulation (Read/Write)

All 0280 Simulated keypress -- write zero before each keystroke

0 to 46 --- 1 F190 0 (No key -- use between real keys)

Non Volatile Latches (Read/Write Setting) (16 Modules)

All 0281 Non-Volatile Latch 1 Function 0 to 1 --- 1 F102 0 (Disabled)

" 0282 Non-Volatile Latch 1 ID --- --- --- F636 "NV Latch 1"

" 028C Non-Volatile Latch 1 Type 0 to 1 --- 1 F519 0 (Reset Dominant)

" 028D Non-Volatile Latch 1 Set 0 to 4294967295 --- 1 F300 0

" 028F Non-Volatile Latch 1 Reset 0 to 4294967295 --- 1 F300 0

" 0291 Non-Volatile Latch 1 Target 0 to 2 --- 1 F109 0 (Self-reset)

" 0292 Non-Volatile Latch 1 Events 0 to 1 --- 1 F102 0 (Disabled)

" 0293 Reserved (4 items) --- --- --- F001 0

" 0297 ...Repeated for Non-Volatile Latch 2

" 02AD ...Repeated for Non-Volatile Latch 3

" 02C3 ...Repeated for Non-Volatile Latch 4

" 02D9 ...Repeated for Non-Volatile Latch 5

" 02EF ...Repeated for Non-Volatile Latch 6


" 031B ...Repeated for Non-Volatile Latch 8



" 035D ...Repeated for Non-Volatile Latch 11



" 039F ...Repeated for Non-Volatile Latch 14

" 03B5 ...Repeated for Non-Volatile Latch 15

" 03CB ...Repeated for Non-Volatile Latch 16

Virtual Input Commands (Read/Write Command) (64 Modules)

All 0400 Virtual Input 1 State 0 to 1 --- 1 F108 0 (Off)

" 0401 Virtual Input 2 State 0 to 1 --- 1 F108 0 (Off)







2






" 040A Virtual Input 11 State 0 to 1 --- 1 F108 0 (Off)

" 040B Virtual Input 12 State 0 to 1 --- 1 F108 0 (Off)

" 040C Virtual Input 13 State 0 to 1 --- 1 F108 0 (Off)

" 040D Virtual Input 14 State 0 to 1 --- 1 F108 0 (Off)

" 040E Virtual Input 15 State 0 to 1 --- 1 F108 0 (Off)

" 040F Virtual Input 16 State 0 to 1 --- 1 F108 0 (Off)








































2













IEC103 Protocol Settings (Read/Write Setting)

All 0582 IEC103 Common ASDU Address 0 to 254 --- 1 F001 0

" 0583 IEC103 Sync Timeout 1 to 1440 min 1 F001 1

IEC103 Binary Inputs (Read/Write Setting) (96 Modules)

All 0584 IEC103 Binary Input 1 FUN 0 to 255 --- 1 F001 0

" 0585 IEC103 Binary Input 1 INF 0 to 255 --- 1 F001 0

" 0586 IEC103 Binary Input 1 Operand 0 to 4294967295 --- 1 F300 0

" 0588 ...Repeated for Binary Input 2

" 058C ...Repeated for Binary Input 3





" 05A0 ...Repeated for Binary Input 8



" 05AC ...Repeated for Binary Input 11

" 05B0 ...Repeated for Binary Input 12



" 05BC ...Repeated for Binary Input 15

" 05C0 ...Repeated for Binary Input 16



" 05CC ...Repeated for Binary Input 19

" 05D0 ...Repeated for Binary Input 20



" 05DC ...Repeated for Binary Input 23

" 05E0 ...Repeated for Binary Input 24



" 05EC ...Repeated for Binary Input 27

" 05F0 ...Repeated for Binary Input 28





2


" 05FC ...Repeated for Binary Input 31












































" 06AC ...Repeated for Binary Input 75





2



" 06BC ...Repeated for Binary Input 79




" 06CC ...Repeated for Binary Input 83




" 06DC ...Repeated for Binary Input 87




" 06EC ...Repeated for Binary Input 91




" 06FC ...Repeated for Binary Input 95


IEC103 ASDU Settings (Read/Write Setting) (4 Modules)

All 0704 IEC103 ASDU1 TYP 0 to 1 --- 1 F630 1(9)

" 0705 IEC103 ASDU 1 FUN 0 to 255 --- 1 F001 0

" 0706 IEC103 ASDU 1 INF 0 to 255 --- 1 F001 0

" 0707 IEC103 ASDU 1 Scan Timeout 0 to 1000 --- 1 F001 0

" 0708 IEC103 ASDU 1 Analog Parameter 1 0 to 65535 --- 1 F600 0

" 0709 IEC103 ASDU 1 Analog Factor 1 0 to 65.535 --- 0.001 F001 1000

" 070A IEC103 ASDU 1 Analog Offset 1 -32768 to 32767 --- 1 F002 0

" 070B IEC103 ASDU 1 Analog Parameter 2 0 to 65535 --- 1 F600 0

" 070C IEC103 ASDU 1 Analog Factor 2 0 to 65.535 --- 0.001 F001 1000

" 070D IEC103 ASDU 1 Analog Offset 2 -32768 to 32767 --- 1 F002 0

" 070E IEC103 ASDU 1 Analog Parameter 3 0 to 65535 --- 1 F600 0

" 070F IEC103 ASDU 1 Analog Factor 3 0 to 65.535 --- 0.001 F001 1000

" 0710 IEC103 ASDU 1 Analog Offset 3 -32768 to 32767 --- 1 F002 0










" 071A IEC103 ASDU 1 Analog Parameter 7 0 to 65535 --- 1 F600 0

" 071B IEC103 ASDU 1 Analog Factor 7 0 to 65.535 --- 0.001 F001 1000

" 071C IEC103 ASDU 1 Analog Offset 7 -32768 to 32767 --- 1 F002 0

" 071D IEC103 ASDU 1 Analog Parameter 8 0 to 65535 --- 1 F600 0




2

" 071E IEC103 ASDU 1 Analog Factor 8 0 to 65.535 --- 0.001 F001 1000

" 071F IEC103 ASDU 1 Analog Offset 8 -32768 to 32767 --- 1 F002 0




" 0723 ...Repeated for IEC103 ASDU 2



IEC103 Commands (Read/Write Setting) (32 Modules)

All 0780 IEC103 Command 1 FUN 0 to 255 --- 1 F001 0

" 0781 IEC103 Command 1 INF 0 to 255 --- 1 F001 0

" 0782 IEC103 Command 1 Param ON 0 to 64 --- 1 F631 0 (OFF)

" 0783 IEC103 Command 1 Param OFF 0 to 64 --- 1 F631 0 (OFF)

" 0784 ...Repeated for IEC103 Command 2


" 078C ...Repeated for IEC103 Command 4




" 079C ...Repeated for IEC103 Command 8

" 07A0 ...Repeated for IEC103 Command 9



" 07AC ...Repeated for IEC103 Command 12

" 07B0 ...Repeated for IEC103 Command 13



" 07BC ...Repeated for IEC103 Command 16

" 07C0 ...Repeated for IEC103 Command 17



" 07CC ...Repeated for IEC103 Command 20

" 07D0 ...Repeated for IEC103 Command 21



" 07DC ...Repeated for IEC103 Command 24

" 07E0 ...Repeated for IEC103 Command 25



" 07EC ...Repeated for IEC103 Command 28

" 07F0 ...Repeated for IEC103 Command 29



" 07FC ...Repeated for IEC103 Command 32

Digital Counter States Actual Values (Read Only Non-Volatile) (8 Modules)

All except B90 0800 Digital Counter 1 Value -2147483647 to 2147483647

--- 1 F004 0




2

" 0802 Digital Counter 1 Frozen -2147483647 to 2147483647

--- 1 F004 0

" 0804 Digital Counter 1 Frozen Time Stamp 0 to 4294967295 --- 1 F050 0

" 0806 Digital Counter 1 Frozen Time Stamp us 0 to 4294967295 --- 1 F003 0

" 0808 ...Repeated for Digital Counter 2







FlexStates (Read Only)

All 0900 FlexState Bits (16 items) 0 to 65535 --- 1 F001 0

RxGOOSE Boolean (Read/Write Setting) (256 Modules)

All 0912 RxGOOSE Boolean 1 Default State 0 to 3 --- 1 F086 0 (Off)

" 0913 RxGOOSE Boolean 1 Events 0 to 1 --- 1 F102 0 (Disabled)

" 0914 ...Repeated for RxGOOSE Boolean 2



" 091A ...Repeated for RxGOOSE Boolean 5

" 091C ...Repeated for RxGOOSE Boolean 6

" 091E ...Repeated for RxGOOSE Boolean 7





























2








































" 09A0 ...Repeated for RxGOOSE Boolean 72





" 09AA ...Repeated for RxGOOSE Boolean 77

" 09AC ...Repeated for RxGOOSE Boolean 78

" 09AE ...Repeated for RxGOOSE Boolean 79




2

" 09B0 ...Repeated for RxGOOSE Boolean 80





" 09BA ...Repeated for RxGOOSE Boolean 85

" 09BC ...Repeated for RxGOOSE Boolean 86

" 09BE ...Repeated for RxGOOSE Boolean 87

" 09C0 ...Repeated for RxGOOSE Boolean 88





" 09CA ...Repeated for RxGOOSE Boolean 93

" 09CC ...Repeated for RxGOOSE Boolean 94

" 09CE ...Repeated for RxGOOSE Boolean 95

" 09D0 ...Repeated for RxGOOSE Boolean 96





" 09DA ...Repeated for RxGOOSE Boolean 101

" 09DC ...Repeated for RxGOOSE Boolean 102

" 09DE ...Repeated for RxGOOSE Boolean 103

" 09E0 ...Repeated for RxGOOSE Boolean 104





" 09EA ...Repeated for RxGOOSE Boolean 109

" 09EC ...Repeated for RxGOOSE Boolean 110

" 09EE ...Repeated for RxGOOSE Boolean 111

" 09F0 ...Repeated for RxGOOSE Boolean 112





" 09FA ...Repeated for RxGOOSE Boolean 117

" 09FC ...Repeated for RxGOOSE Boolean 118

" 09FE ...Repeated for RxGOOSE Boolean 119






" 0A0A ...Repeated for RxGOOSE Boolean 125

" 0A0C ...Repeated for RxGOOSE Boolean 126




2

" 0A0E ...Repeated for RxGOOSE Boolean 127











































" 0A64 ...Repeated for RxGOOSE B

GE Grid Solutionsgridautomation.pl/dane/Dokumentacja PDF/1.Zabezpieczenia... · 2017. 4. 18. · GE...

Documents

Transcript of GE Grid Solutionsgridautomation.pl/dane/Dokumentacja PDF/1.Zabezpieczenia... · 2017. 4. 18. · GE...