ABB Relion 620 Series Protocol Manual
  1. Manuals
  2. Brands
  3. ABB Manuals
  4. Controller
  5. Relion 620 Series
  6. Protocol manual
ABB Relion 620 Series Protocol Manual

ABB Relion 620 Series Protocol Manual

Modbus communication
Hide thumbs Also See for Relion 620 Series:
Table of Contents

Advertisement

Quick Links

Download this manual See also: Installation Manual
®
Relion
Protection and Control
620 series
Modbus Communication Protocol Manual

Advertisement

Table of Contents
loading

Related Manuals for ABB Relion 620 Series

Summary of Contents for ABB Relion 620 Series

  • Page 1 ® Relion Protection and Control 620 series Modbus Communication Protocol Manual...
  • Page 3 Document ID: 1MRS757645 Issued: 2015-12-11 Revision: B Product version: 2.0 FP1 © Copyright 2015 ABB. All rights reserved...
  • Page 4 Copyright This document and parts thereof must not be reproduced or copied without written permission from ABB, and the contents thereof must not be imparted to a third party, nor used for any unauthorized purpose. The software or hardware described in this document is furnished under a license and may be used, copied, or disclosed only in accordance with the terms of such license.
  • Page 5 In case any errors are detected, the reader is kindly requested to notify the manufacturer. Other than under explicit contractual commitments, in no event shall ABB be responsible or liable for any loss or damage resulting from the use of this manual or the application of the equipment.
  • Page 6 (EMC Directive 2004/108/EC) and concerning electrical equipment for use within specified voltage limits (Low-voltage directive 2006/95/EC). This conformity is the result of tests conducted by ABB in accordance with the product standard EN 60255-26 for the EMC directive, and with the product standards EN 60255-1 and EN 60255-27 for the low voltage directive.

  • Page 7: Table Of Contents

    Table of contents Table of contents Section 1 Introduction...............5 This manual..................5 Intended audience................5 Product documentation...............6 Product documentation set............6 Document revision history............. 6 Related documentation..............7 Symbols and conventions..............7 Symbols..................7 Document conventions..............7 Section 2 Modbus overview............. 9 Modbus standard................9 Serial communication..............
  • Page 8 Table of contents Data mapping principles.............. 23 Default data organization............23 Data in monitoring direction............23 One-bit data mapping.............23 Data in control direction............24 Digital input data................24 Multiple digital inputs mapping..........25 Digital input configuration............25 Measurand registers..............26 Register value update............27 Primary and per-unit values...........
  • Page 9 Table of contents Fault record structure............. 56 Fault record reading............... 57 Other fault record registers.............58 Parameter setting group selection..........60 Time synchronization ..............60 Real-time clock structure............60 Writing to real-time structures..........60 Device information...............61 ASCII character coding............62 ASCII string syntax..............62 Reset time structure..............63 Accessing of non-protocol-mapped data........

  • Page 11: Section 1 Introduction

    Section 1 1MRS757645 B Introduction Section 1 Introduction This manual The communication protocol manual describes a communication protocol supported by the protection relay. The manual concentrates on vendor-specific implementations. Intended audience This manual addresses the communication system engineer or system integrator responsible for pre-engineering and engineering for communication setup in a substation from a protection relay perspective.

  • Page 12: Product Documentation

    ABB Website http://www.abb.com/relion. 1.3.2 Document revision history Document revision/date Product series version History A/2013-05-07 First release B/2015-12-11 2.0 FP1 Content updated to correspond to the product series version Download the latest documents from the ABB Website http://www.abb.com/substationautomation. 620 series Communication Protocol Manual...

  • Page 13: Related Documentation

    Section 1 1MRS757645 B Introduction 1.3.3 Related documentation Product-specific point list manuals and other product series- and product-specific manuals can be downloaded from the ABB Website http://www.abb.com/substationautomation. Symbols and conventions 1.4.1 Symbols The caution icon indicates important information or warning related to the concept discussed in the text.
  • Page 14 Section 1 1MRS757645 B Introduction The corresponding parameter values are "On" and "Off". • Input/output messages and monitored data names are shown in Courier font. When the function starts, the START output is set to TRUE. • This document assumes that the parameter setting visibility is "Advanced". 620 series Communication Protocol Manual...

  • Page 15: Section 2 Modbus Overview

    Section 2 1MRS757645 B Modbus overview Section 2 Modbus overview Modbus standard Modbus is a communication protocol developed by the Modicon company in the 1970’s. Originally it was used for communication in PLCs and RTU devices. Later on the Modbus protocol has been used in a variety of different device applications. Today the Modbus protocol is mainly used over serial communication networks and Ethernet.

  • Page 16: Application Data Implementation

    Section 2 1MRS757645 B Modbus overview reserved for Modbus. If the connection request is accepted by the server, the client can start communicating with the server unit. IEDs can usually accept several simultaneous Modbus TCP/IP client connections even though the number of connections is limited. It is possible to configure the IED to only accept socket connection requests from known client IP addresses.
  • Page 17 Section 2 1MRS757645 B Modbus overview outlook, that is, the Modbus memory map, of REF620-FE201 differs, for example, from the one of REF620-FE202. A newer SW version of the same 620 series configuration may contain additional Modbus points. The Modbus memory map documentation of a certain 620 series configuration and SW version is available in addition to this document.

  • Page 19: Section 3 Vendor-Specific Implementation

    Section 3 1MRS757645 B Vendor-specific implementation Section 3 Vendor-specific implementation Protocol server instances The word "client" refers to the protocol master. The IED is referred to as "server" or a slave device. The IED can communicate with several protocol clients simultaneously. Furthermore, it is possible to configure the IED to provide different protocol data and data outlook for different clients.

  • Page 20: Protocol Server Attachment To A Client

    Section 3 1MRS757645 B Vendor-specific implementation the IED can have only five client connections in total, regardless of the protocols to which the clients belong. This includes the MMS clients and other communication protocol clients. Protocol instances are identified with numbers 1...5. There are different and unique setting and monitoring parameters for each instance in the HMI menu.

  • Page 21: Modbus Link Alternatives

    Section 3 1MRS757645 B Vendor-specific implementation In PCM600, it is necessary to always define the mappings to be edited or viewed. Each protocol instance has the setting parameter Mapping selection, which defines the protocol mappings to be used by this instance. Several protocol instances can use the same mapping.
  • Page 22 Section 3 1MRS757645 B Vendor-specific implementation RTU frame in the RTU mode. This parameter can be given with the accuracy of one character. The default setting is three characters but the user can increase or decrease the value. In a multidrop RS-485 Modbus network the unit may detect and receive response messages from other slave units.

  • Page 23: Modbus Serial Diagnostic Counters

    Section 3 1MRS757645 B Vendor-specific implementation 3.2.1.2 Modbus serial diagnostic counters Modbus Serial diagnostic counters can be viewed via the LHMI path Monitoring/ Communication/Modbus/MBS0n. The counters show complete Modbus protocol link frames and Modbus errors. The serial communication drivers (COM1, COM2) maintain their own counters for lower level serial communication diagnostics.

  • Page 24: Character Framing In Different Serial Link Modes

    Section 3 1MRS757645 B Vendor-specific implementation Check the receive and send delay settings in the relay. If link frames are not received properly there might be character timing problems. Check for receive errors, checksum errors or several retransmissions. If these are found, the line may be noisy.

  • Page 25: Modbus Tcp/Ip Diagnostic Counters

    Section 3 1MRS757645 B Vendor-specific implementation 3.2.2.1 Modbus TCP/IP diagnostic counters Modbus TCP/IP counters can be viewed via the LHMI path Monitoring/ Communication/Modbus/MBS0n. The counters show the complete Modbus protocol link frames and Modbus errors. The Ethernet communication driver maintains its own counters for lower level communication diagnostics.

  • Page 26: Diagnostic Functions

    Section 3 1MRS757645 B Vendor-specific implementation Function Name Description code Force single coil Sets the status of a discrete output. Preset single register Sets the value of a holding register. Diagnostics Checks the communication system between the master and the slave. Force multiple coils Sets the status of multiple discrete outputs.

  • Page 27: Exception Codes

    Section 3 1MRS757645 B Vendor-specific implementation Function Name Description code Return slave no response count The response returns the number of messages addressed to the slave for which a response (neither a normal response nor an exception response) has not been sent since its last restart, clear counters operation or power up.

  • Page 28: Modbus Data Implementation

    Section 3 1MRS757645 B Vendor-specific implementation For a list of the available data objects, see the point list manual. 3.4.2 Modbus data implementation The IED is internally modeled according to the IEC 61850 standard. The Modbus protocol is implemented on top of this model. However, not all features of the IEC61850 data model are available through the Modbus interface.

  • Page 29: Data Mapping Principles

    Section 3 1MRS757645 B Vendor-specific implementation • The Modbus fault record gives a summary of the captured max-min values and protection stages starting and possibly tripping during a fault. • The addressing of the application data in the documentation and tools follows the so-called Modbus-PLC addressing principle, where the base address 1 is used.

  • Page 30: Data In Control Direction

    Section 3 1MRS757645 B Vendor-specific implementation This is easier to understand when the address numbers are expressed in the hexadecimal format: 2893 = 0xB4D, where the register 180 = 0xB4 and bit 13 = 0xD. 3.4.3.4 Data in control direction IED controls, set points and acknowledgements are mapped to Modbus 0X data (coils).

  • Page 31: Multiple Digital Inputs Mapping

    Section 3 1MRS757645 B Vendor-specific implementation The MCD bit states are client-dependent. The MCD bit is only reset for the specific Modbus client that reads it. Thus, other Modbus clients may still receive value 1 from the same MCD bit when it is read. MOM indication changes are captured in the IED's sequential Modbus event buffer.

  • Page 32: Measurand Registers

    Section 3 1MRS757645 B Vendor-specific implementation The bit address field shows the 1x and 0x Modbus memory addresses on which the data occur as default. The Modbus register address and bit within the register are shown under the 3x and 4x register views. The address field may also be empty, meaning that the object is not located in the Modbus memory at all as default.

  • Page 33: Register Value Update

    Section 3 1MRS757645 B Vendor-specific implementation 61850 Value scaleFactor Offset × Modbus value (Equation 1) A070857 V1 EN The range of the original IEC 61850 value can be seen in the Modbus memory map point list. All frequently updated data are readable from a sequential data area. Additionally, there is a separate sequential data area for measurands and counters with a slow update rate.

  • Page 34: Primary And Per-Unit Values

    Section 3 1MRS757645 B Vendor-specific implementation 3.4.5.2 Primary and per-unit values Measurands originating from CT or VT measurements can be obtained from the IED in two ways. They can be viewed either as primary values or as per-unit values. The primary values are represented internally as decimal numbers. The primary units are [A] for current and [kV] for voltage.

  • Page 35: Rearranging Of Register Value Ranges

    Section 3 1MRS757645 B Vendor-specific implementation 3.4.5.5 Rearranging of register value ranges The pre-defined original Modbus register does not always fit inside the whole value range of the source value. Example A counter in the motor protection IED shows the running hours of the motor. The original system counter value has a range of 0…999999 hours.

  • Page 36: Register Configuration

    Section 3 1MRS757645 B Vendor-specific implementation Table 12: Time structure data Address Register Values Comment TimeStamp High byte:year, low (Year,Month) byte:month TimeStamp (Day,Hour) High byte:day, low byte:hour TimeStamp (Min,Sec) High byte:min, low byte:seconds TimeStamp Word: milliseconds (Milliseconds) Time quality See the table about time quality register Table 13: Time quality register...

  • Page 37: Control Operations

    Section 3 1MRS757645 B Vendor-specific implementation Table 14: Setting columns in the Modbus Communication Management tool in PCM600 Setting column Alternatives Description Register address Not adjustable The 3x and 4x Modbus memory map addresses where the register resides as default. If the field is empty, the register is not visible in the Modbus memory map as default.
  • Page 38 Section 3 1MRS757645 B Vendor-specific implementation The control objects in this IED are either single point or double point control objects. Single point control object output types Single point control objects can be either pulse outputs or persistent outputs. The Modbus client should only write "1" to the pulse outputs. This write operation activates the control operation and there is no need for the Modbus client to write "0"...

  • Page 39: Control Functions

    Section 3 1MRS757645 B Vendor-specific implementation 3.4.6.1 Control functions Generally, output objects are controlled one at a time. The IED accepts only functions 05 (force single coil) and 15 (force multiple coils), when the 0X coils control structure is used for control operation. Only one control bit can be operated at a time when the 4X control structures are used.
  • Page 40 Section 3 1MRS757645 B Vendor-specific implementation With the control operations the client must assemble the control structure register values and write them into the IED. Execute register The control step is executed when value "1" is written into this register. Password register 1 If a password is defined, the first two ASCII characters of the four character password are written into this register: the first character into the higher byte and the second...

  • Page 41: Additional Control Operation Features

    Section 3 1MRS757645 B Vendor-specific implementation If several clients are allowed to perform control operations simultaneously, this method should not be used by more than one of the multiple clients in question. Exception codes Only a few exception code alternatives exist for control structures: •...

  • Page 42: Control Bit Configuration

    Section 3 1MRS757645 B Vendor-specific implementation Enhanced security object • Positive confirmation means that control has been activated. The application behind the control point has started, but has not yet finished. SSR6 state is set into ‘In progress’. • Exception 03 response means that the control is not activated. SSR6 reason code is updated.
  • Page 43 Section 3 1MRS757645 B Vendor-specific implementation Table 16: Control bits Setting column Alternatives Description Bit address Empty Control point is not in use. It can be edited with Delete + Enter keys. 1...65535 Control point is not in use on this Coil (0x) address.

  • Page 44: System Status Registers

    Section 3 1MRS757645 B Vendor-specific implementation Modbus memory map Application configuration Physical SPCGAPC output Write-only addr 100 Coil Read-only addr 100 MVGAPC GUID-8FE88A9A-20F7-4AE8-A2CF-CED69016B575 V1 EN Figure 4: Write and read coil example The state of the physical output is wired to an MVGAPC input. The MVGAPC “Mom- only”...

  • Page 45: Ssr2

    Section 3 1MRS757645 B Vendor-specific implementation If a specific bit in this register is "1", it signifies a warning or an error in the hardware entity in question. More specific warning and error codes can be read from elsewhere in the Modbus memory.

  • Page 46: Ssr3

    Section 3 1MRS757645 B Vendor-specific implementation 3.4.7.3 SSR3 The data available 1 SSR3 register is located at address 40130. The bit values in the SSR3 register are Modbus client dependent. Bits 0 and 1 are set to "1" as long as the client in question has not read out the available Modbus event or fault records.

  • Page 47: Ssr5

    Section 3 1MRS757645 B Vendor-specific implementation If a bit is set to "1", some data belonging to the category in question has changed since the client last scanned the register. The SSR4 bit or bits are cleared when the register is read.

  • Page 48: User-Definable Data

    Section 3 1MRS757645 B Vendor-specific implementation Table 22: 16 bit SSR6 register ClientCmdSEQNo Cmd State Resp Type CMDResultCode ClientCmdSEQNo Counts the client's control operations from 0000...1111, that is 0...15, and then starts over. CmdState 00 = No write command has ever been issued by this client 01 = Command in progress 11 = Response Ready RespType...

  • Page 49: User Definable Registers

    Section 3 1MRS757645 B Vendor-specific implementation retrofit purposes and are not needed for normal installations. Some rescaling features are redundant at the moment. 3.4.8.1 User definable registers The Modbus register areas 3X and 4X from 1 to 127 can be compiled freely by the user.

  • Page 50: Udr Data Configuration

    Section 3 1MRS757645 B Vendor-specific implementation 3.4.8.6 UDR data configuration UDR definitions can be created using the Communication Management tool in PCM600. 3.4.8.7 UDR register value manipulation UDR values are initially copied from the source register. Thereafter the following manipulations can be applied to the UDR value. Additional rescaling of the source data value There are three possibilities for UDR rescaling of the Modbus source register value.

  • Page 51: Udr Register Configuration

    Section 3 1MRS757645 B Vendor-specific implementation Table 24: UDR scaling alternatives Scaling alternative Setting Description No scaling No change is made to the sourceValue Ratio scaling UDRScaleArg1 = Min in UDRScaleArg2 = Max in Uses all 4 scaling arguments UDRScaleArg3 = Min UDRScaleArg1...UDRScaleArg4.
  • Page 52 Section 3 1MRS757645 B Vendor-specific implementation Table 25: Configuration columns in Modbus Communication Management tool in PCM600 Setting column Alternatives Description Initial properties Scale value format Regular Modbus register UDR value initially inherits scaling from the source Modbus value register. This includes the Primary scale in source value use setting.
  • Page 53 Section 3 1MRS757645 B Vendor-specific implementation Setting column Alternatives Description Scaling No rescaling of the Modbus UDR No scaling value. Scaling arguments are ignored. Ratio scaling Linear scaling of the source value between the source range “Min In”...”Max In” into UDR value range “Min Out”...”Max Out”.

  • Page 54: Event Records

    Section 3 1MRS757645 B Vendor-specific implementation Setting column Alternatives Description Bit size Register bit size reduction not in use. All bits in register used by the value. 2...31 Register bit size reduced to this value. Saturation limits of the value according to the configured bit size, including possible sign bit.

  • Page 55: Single Event Record Structure

    Section 3 1MRS757645 B Vendor-specific implementation buffer the different clients are reading at the moment. Clients are identified either by the serial port from where the requests are issued or by the client's IP address in the TCP/IP network. Up to 25 different IP addresses, belonging to both registered and unregistered Modbus clients, can be memorized by the IED.
  • Page 56 Section 3 1MRS757645 B Vendor-specific implementation Event records can be read by using two commands, function 6 for the write operation and function 3 for the read operation, or by using function 23 that includes write and read operations in the same transaction.

  • Page 57: Other Event Record Registers

    Section 3 1MRS757645 B Vendor-specific implementation as no new selection write operation is performed, the contents of the 11 event record registers are not changed. 3.4.9.3 Other event record registers Sequence number Every Modbus event record is given a sequence number. The sequence number runs from 1 to 65535 and then rolls over to 1 again.
  • Page 58 Section 3 1MRS757645 B Vendor-specific implementation Meaning Values Reserved Data object 0 = Modbus address 1 = UID data ID type 7...0 Data value 00000000 = One bit indication 00000001 = ACD indication identification 00000010 = Two bit indication 00000011 = SEC indication+add data 00000100...
  • Page 59 Section 3 1MRS757645 B Vendor-specific implementation Different Modbus indications originating from the same IEC 61850 data attribute have an identical UID. It is therefore recommended to use the Modbus address as the identification instead of the UID. Data value identification bits 5..0 Coding of the event data value is one bit, two bits or 32 bits.

  • Page 60: Multiple Event Records Reading

    Section 3 1MRS757645 B Vendor-specific implementation Table 32: Interpretation of the ACD data Register address Meaning 49261 xxxx.xxxx.xxxx.xxx0 Object in OFF position xxxx.xxxx.xxxx.xxx1 Object in ON position 49262 xxxx.xxxx.xxxx.xx00 Start in unknown direction xxxx.xxxx.xxxx.xx01 Start in forward direction xxxx.xxxx.xxxx.xx10 Start in backwards direction xxxx.xxxx.xxxx.xx11 Start in both directions Table 33: Interpretation of the SEC data...
  • Page 61 Section 3 1MRS757645 B Vendor-specific implementation easiest way to detect the duplication is to check the sequence number of the event records. The sequence numbers remain similar to the duplicated event records. Extended event record structure The extended register addresses are 49250 and 49263-49361. Table 34: Extended event record structure with the maximum of 10 event records Address...

  • Page 62: Fault Records

    Section 3 1MRS757645 B Vendor-specific implementation Address Register Values Description 49329 Sequence Number 8 Event record 8 49340 Sequence Number 9 Event record 9 49351 Sequence Number 10 49352 Unread records left 10 49353 TimeStamp 10 49354 TimeStamp 10 49355 TimeStamp 10 49356 TimeStamp 10...

  • Page 63: Fault Record Reading

    Section 3 1MRS757645 B Vendor-specific implementation Table 35: Header part of the record structure Address Register Values Comment 49401 Fault record selection 1...4 and -1...-99 Write register 49402 Sequence Number 0...65535 49403 Unread records left 0...99 49404 TimeStamp (Year,Month) High byte:year, low byte:month 49405 TimeStamp (Day, Hour) High byte:day, low byte:hour...

  • Page 64: Other Fault Record Registers

    Section 3 1MRS757645 B Vendor-specific implementation contain the value 0. The Modbus protocol will give an exception response if the client tries to read out too few registers from the fault record structure. Selection code 1: Reading the oldest unread record When writing the selection code 1, the IED first checks the client.
  • Page 65 Section 3 1MRS757645 B Vendor-specific implementation of the recorded data are sequential. During the fault record buffer overflow the client can notice a jump in the sequence numbers when some fault records are lost. The gap between the new and the previous sequence number reveals exactly how many records have been lost.

  • Page 66: Parameter Setting Group Selection

    Section 3 1MRS757645 B Vendor-specific implementation 3.4.11 Parameter setting group selection In the current IED version, parameter setting group selection and reading is defined through regular Modbus registers. Formerly this was achieved by a special 4x register 9231. The new register has the default address 2301. The new register has the default address 2301.

  • Page 67: Device Information

    Section 3 1MRS757645 B Vendor-specific implementation address "0". Thus, all IEDs in the same serial network can be synchronized at the same time. Method 1: Synchronization in one step The registers 49201...49208 (49211...49218) should be written in one multiple registers preset request (function 16) by a Modbus TCP/IP client or by a serial interface master.

  • Page 68: Ascii Character Coding

    Section 3 1MRS757645 B Vendor-specific implementation • IED model (max. 12 characters) • IED type (max. 6 characters) • IED serial number (max. 12 characters) • IED location information (max. 34 characters) • CPU card SW and HW revision numbers •...

  • Page 69: Reset Time Structure

    Section 3 1MRS757645 B Vendor-specific implementation Example of an identification string could be C(REF620;FE201;1VHR123456R2;feeder 15.12;1.6;2.0)H(1.2;3.1)0(-;-)1(-;1.1)2(-; 1.0)3(-;1.1)4(-;2.0) The data within the C section is restricted to certain maximum lengths. For example, the user-definable IED location is here restricted to a maximum of 34 characters. If the IED location information on system level contains more characters, only the 34 first characters are displayed.

  • Page 70: Accessing Of Non-Protocol-Mapped Data

    Section 3 1MRS757645 B Vendor-specific implementation 3.4.15 Accessing of non-protocol-mapped data The IED application includes a number of general-purpose I/O data. By default, these data are mapped to this protocol. See the point list manual for the exact mappings. The general-purpose objects can be connected to any internal object in the IED configuration application using the Application Configuration or Signal Matrix tool.

  • Page 71: Spa Application Data

    Section 3 1MRS757645 B Vendor-specific implementation SPA application data 3.5.1 SPA protocol The Modbus protocol includes an internal Modbus ASCII to SPA protocol converter. The SPA protocol is available as a resident extension to the Modbus ASCII protocol and it operates only through the asynchronous serial interface. This interface provides connection to gateway products requiring SPA.

  • Page 72: Reading Of One Register

    Section 3 1MRS757645 B Vendor-specific implementation The SPA data type and number define the value response format. 3.5.3.1 Reading of one register The examples below are from reading the register 138. The SPA slave number is 25. The actual value in register 138 is assumed to be 52342 (decimal). It does not matter from SPA point of view if the register value is formed from one measurand or if it is a register packed with indication bits.

  • Page 73: Special Reading Of Indication Bits

    Section 3 1MRS757645 B Vendor-specific implementation >25R146I42:CC <25D:F025A476:CC The SPA implementation has no way of checking that the two Modbus registers actually belong together as one value. Any two independent consecutive 16 bit registers can be read freely in one 32 bit data value packet. 3.5.3.3 Special reading of indication bits Many Modbus indications (one bit data) in the device are coded as MOM and MCD...

  • Page 74: Writing Of Spa Data

    Section 3 1MRS757645 B Vendor-specific implementation 3.5.4 Writing of SPA data Writing SPA data refers here either to writing to a Modbus Coil (one bit data) or to a writable Modbus Register (up to 16 bit data). SPA write operation can only be performed to one Modbus object at a time.

  • Page 75: Spa Time Synchronization

    Section 3 1MRS757645 B Vendor-specific implementation code is E0…E31 depending on which bit within the register indication is (0…15) and into which state the indication has changed (0…1). For example an event code like 23.543 35E23 would mean that event occurred at the time 23.543 and that register 35 bit 11 (23 div 2) changed to value “1”...

  • Page 76: Modbus User Definable Area Set Up For Spa Zc-302 Polling

    Section 3 1MRS757645 B Vendor-specific implementation case the UDR mapped indication point has no original Modbus point location, then the event comes from its UDR point location. 3.5.7.2 Modbus user definable area set up for SPA ZC-302 polling In this example phase currents IL1...IL3 are mapped into user definable register addresses 0xB…0xC (11…13).

  • Page 77: Troubleshooting

    Section 3 1MRS757645 B Vendor-specific implementation • >10R11I31: Read register 11 as an unsigned integer … map to Profibus offset 4...5 • >10R12I31: Read register 12 as an unsigned integer … map to Profibus offset 6...7 • >10R13I31: Read register 13 as an unsigned integer … map to Profibus offset 8...9 The bits in register 14 can be fetched as an integer value.

  • Page 79: Section 4 Modbus Parameters And Diagnostics

    Section 4 1MRS757645 B Modbus parameters and diagnostics Section 4 Modbus parameters and diagnostics Parameter list The Modbus parameters can be accessed with PCM600 or via the LHMI path Configuration/Communication/Modbus/MBS0n. Some parameters are not visible in the “Basic” setting visibility mode. To view all parameters use “Advanced”...

  • Page 80: Monitored Data

    Section 4 1MRS757645 B Modbus parameters and diagnostics Parameter Values (Range) Unit Step Default Description Event ID selection 0=Address 0=Address Selects whether the events are reported 1=UID using the MB address or the UID number. Event buffering 0=Keep oldest 0=Keep oldest Selects whether the oldest or newest 1=Keep newest events are kept in the case of event buffer...
  • Page 81 Section 4 1MRS757645 B Modbus parameters and diagnostics Parameter Values (range) Description Transmitted exc A 0...2147483648 Transmitted exception responses 1 and 2 Transmitted exc B 0...2147483648 Transmitted exception responses 3 Checksum errors 0...2147483648 Checksum errors detected CnReject no sockets 0...2147483648 Connection rejections due to no free sockets CnReject unregistered 0...2147483648...

  • Page 83: Section 5 Glossary

    Section 5 1MRS757645 B Glossary Section 5 Glossary 620 series Series of numerical protection and control relays for high- end protection and supervision applications of utility substations, and industrial switchgear and equipment Start/pickup status 1. Application Configuration tool in PCM600 2.
  • Page 84 Serial link according to EIA standard RS485 Real-time clock Remote terminal unit SCADA Supervision, control and data acquisition Security violation Strömberg protection acquisition. ABB proprietary serial master-slave protocol used in substation automation for point-to-point communication. Single-point status of a controllable object Single-point status SSR1...
  • Page 85 Section 5 1MRS757645 B Glossary Coordinated universal time Voltage transformer WHMI Web human-machine interface 620 series Communication Protocol Manual...
  • Page 88 Contact us ABB Oy Medium Voltage Products, Distribution Automation P.O. Box 699 FI-65101 VAASA, Finland Phone +358 10 22 11 +358 10 22 41094 www.abb.com/mediumvoltage www.abb.com/substationautomation Nanjing SAC Power Grid Automation Co. Ltd. NO.39 Shuige Road, Jiangning Development Zone 211100 Nanjing, China...

Table of Contents