Related Manuals for ABB 615 Series ANSI
Summary of Contents for ABB 615 Series ANSI
- Page 1 ® Relion Protection and Control 615/620 series ANSI Modbus Communication Protocol Manual...
- Page 3 615 series 620 series Product version 2.0 Product version 1.0 Document ID: 1MAC052634-MB Issued: 11/23/2010 Revision: D © Copyright 2010 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 This document has been carefully checked by ABB but deviations cannot be completely ruled out. In case any errors are detected, the reader is kindly requested to notify the manufacturer.
- Page 6 (Low-voltage directive 2006/95/EC). This conformity is the result of tests conducted by ABB in accordance with the product standards EN 50263 and EN 60255-26 for the EMC directive, and with the product standards EN 60255-6 and EN 60255-27 for the low voltage directive.
-
Page 7: Table Of Contents
Table of contents 1MAC052634-MB D Table of contents Section 1 Introduction................3 This manual....................3 Intended audience..................3 Product documentation ................4 Product documentation set ..............4 Document revision history..............5 Related documentation ............... 5 Symbols and conventions ................ 5 Safety indication symbols.............. - Page 8 Table of contents 1MAC052634-MB D Multiple digital inputs mapping ............. 19 Measurand registers................19 Primary and per-unit values ............20 Register sizes................20 Time of update ................20 Control operations ................21 Control functions ................22 Control operations through 4X register structures ....... 23 Additional control operations............
-
Page 9: Introduction
Section 1 1MAC052634-MB D Introduction Section 1 Introduction This manual The communication protocol manual describes a communication protocol supported by the IED. 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 an IED perspective. -
Page 10: Product Documentation
Section 1 1MAC052634-MB D Introduction Product documentation 1.3.1 Product documentation set Application manual Engineering manual Installation manual Operation manual Technical manual Communication Protocol manual Protocol Points List manual Figure 1: The intended use of manuals in different lifecycles The engineering manual contains instructions on how to engineer the IEDs using the different tools in PCM600. -
Page 11: Document Revision History
D/11/23/2010 615 series: 2.0 Added information about 620 series 620 series: 1.0 Download the latest documents from the ABB web site http://www.abb.com/substationautomation. 1.3.3 Related documentation Product-specific point list manuals and other product series- and product-specific manuals can be downloaded from the ABB web site http://www.abb.com/substationautomation. -
Page 12: Manual Conventions
Section 1 1MAC052634-MB D Introduction degraded process performance leading to personal injury or death. Therefore, comply fully with all warning and caution notices. 1.4.2 Manual conventions Conventions used in IED manuals. A particular convention may not be used in this manual. -
Page 13: Modbus Overview
Section 2 1MAC052634-MB D 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. -
Page 14: Application Data Implementation
Section 2 1MAC052634-MB D Modbus overview 2.1.3 Application data implementation This IED is designed to operate with a wide range of different Modbus masters and clients. The Modbus memory map offers the possibility to view IED's internal process data in a simple I/O map style which is mainly aimed at PLC masters and other process automation devices. -
Page 15: Vendor-Specific Implementation
Section 3 1MAC052634-MB D Vendor-specific implementation Section 3 Vendor-specific implementation Modbus link alternatives Modbus communication is possible over the serial communication interface, over the Ethernet interface, or over both interfaces simultaneously. 3.1.1 Serial link Modbus serial communication requires that the IED variant is equipped with a serial interface card at the slot X000. -
Page 16: Modbus Serial Diagnostic Counters
Section 3 1MAC052634-MB D Vendor-specific implementation In a multidrop RS-485 Modbus network the unit may detect and receive response messages from other slave units. Thus, consider the minimum silent time between the response frame and the beginning of master’s next request frame when setting the end delay in Modbus RTU mode. -
Page 17: Character Framing In Different Serial Link Modes
Section 3 1MAC052634-MB D Vendor-specific implementation Table 1: Serial diagnostic counters Counter Description Received frames Total amount of received Modbus frames. For example, the Modbus frames that are addressed to this instance. Transmitted Total amount of transmitted Modbus responses. frames N Cksm Err N Total amount of detected Modbus checksum errors. -
Page 18: Tcp/Ip Interface Configuration
Section 3 1MAC052634-MB D Vendor-specific implementation Modbus TCP usually shares the Ethernet connection with the other Ethernet based protocols of the IED. The number of Ethernet based clients that can be simultaneously connected to the IED is restricted. 3.1.2.1 TCP/IP interface configuration The Modbus TCP/IP protocol uses the Ethernet interface. -
Page 19: Modbus Tcp/Ip Diagnostic Counters
Section 3 1MAC052634-MB D Vendor-specific implementation Client's write authority The registering of a Modbus client affects the client's write authority and the reading of latched Modbus data. The TCP write authority parameter can be set to three different states: • 0 = No write authority for any Modbus TCP/IP client •... -
Page 20: Supported Function Codes
Section 3 1MAC052634-MB D Vendor-specific implementation Table 5: Common (instance independent) Modbus TCP/IP diagnostic counters Counter Description CnReject No The amount of connection requests that are rejected due to unavailable TCP sockets. sockets CnReject Not reg The amount of connection requests that are rejected since the client is not registered. Supported function codes 3.2.1 Application functions... - Page 21 Section 3 1MAC052634-MB D Vendor-specific implementation Function Name Description code Return bus message count The response returns the number of messages in the communication system detected by the slave since its last restart, clear counters operation and power up. Return bus communication error count The response returns the number of CRC errors encountered by the slave since its last restart, clear counters operation and power...
-
Page 22: Exception Codes
Section 3 1MAC052634-MB D Vendor-specific implementation 3.2.3 Exception codes Table 8: Supported exception codes Function Name Description code Illegal function The slave does not support the requested function. Illegal data address The slave does not support the data address or the number of items in the query is incorrect. -
Page 23: Data Mapping Principles
Section 3 1MAC052634-MB D Vendor-specific implementation Change events and time synchronization The Modbus standard does not define event reporting or time synchronization procedures. Proprietary solutions have been introduced in this IED to support these functionalities. Control operations The Modbus standard defines data types 0X for coils and 4X for holding registers to be used for control operations. -
Page 24: One Bit Data Mapping
Section 3 1MAC052634-MB D Vendor-specific implementation not result in any Modbus exception response. The value in these bits or registers is always zero. 3.3.3.2 One bit data mapping All one bit data in the IED is readable either from the 0X or 1X memory area. The Modbus bit point addresses are similar regardless of the memory area.One bit data is also available in 4X register memory area as bit packed 16 bit registers. -
Page 25: Multiple Digital Inputs Mapping
Section 3 1MAC052634-MB D Vendor-specific implementation momentary position bit and the MCD bit of a certain indication point always occur as pairs in the Modbus memory map. Observe that the MCD bit states are client dependent. The MCD bit is only reset for the specific Modbus client that reads it. -
Page 26: Primary And Per-Unit Values
Section 3 1MAC052634-MB D Vendor-specific implementation 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. 3.3.5.1 Primary and per-unit values Measurands originating from CT measurements can be obtained from the IED in two ways. -
Page 27: Control Operations
Section 3 1MAC052634-MB D Vendor-specific implementation Table 10: 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 11: Time quality register... -
Page 28: Control Functions
Section 3 1MAC052634-MB D Vendor-specific implementation An output cannot support both direct-operate and select-before-operate modes at the same time. The double point select-before-operate mode is usually used for the circuit breaker operations. It consists of four controllable objects: • Select open •... -
Page 29: Control Operations Through 4X Register Structures
Section 3 1MAC052634-MB D Vendor-specific implementation 3.3.6.2 Control operations through 4X register structures The control outputs can be operated through the control structures in the 4X register area. This means that the control output is also located as a bit within the value and bit mask registers of the 4X control structure. -
Page 30: Additional Control Operations
Section 3 1MAC052634-MB D Vendor-specific implementation Control structure register assembling order The Modbus client can assemble all the control structure registers and write them in one multiple registers write function 16 request. The Modbus client can also write the registers in several separate transactions or even one by one using registers write function 06. -
Page 31: System Status Registers
Section 3 1MAC052634-MB D Vendor-specific implementation on the command termination confirmation. In secured operation mode, the Modbus command response is always based on the termination confirmation. The update of the SSR6 bits (sequence number + command state) is based on the termination confirmation in both operation modes. -
Page 32: Ssr2
Section 3 1MAC052634-MB D Vendor-specific implementation Table 14: 16 bit SSR1 register Meaning Device global warning Device global error Slot 0 (X130) warning or error Slot 1 (X120) warning or error Slot 2 (X110) warning or error Slot 3 (X100) warning or error Slot 4 (X000) warning or error 7...15 0 = not used... -
Page 33: Ssr4
Section 3 1MAC052634-MB D Vendor-specific implementation Bit 8 is set to “1” when an event record has been recorded. The bit is reset when the client writes the reset code 4 to the event record selection register. Bit 9 is set to “1” when a fault record has been recorded. The bit is reset when the client writes the reset code 4 to the fault record selection register. -
Page 34: Ssr5
Section 3 1MAC052634-MB D Vendor-specific implementation Table 17: 16 bit SSR4 register Meaning Data category Data in category 1 changed 1 = Physical inputs Data in category 2 changed 1 = Protection function pickup/trip Data in category 3 changed 1 = LED Alarm Data in category 4 changed 1 = New disturbance record available Data in category 5 changed... -
Page 35: Event Records
Section 3 1MAC052634-MB D Vendor-specific implementation RespType 01 = Unsecured control response 10 = Secured control response 11 = Modbus 03 exception response valid. CMDResultCode is in this case 0. The reason for the 03 exception is an invalid written value. Table 19: CMDResultCode Code... -
Page 36: Single Event Record Reading
Section 3 1MAC052634-MB D Vendor-specific implementation Table 20: Event record structure Address Register Values Comment 4xxxx + 1 Event selection 1...4 and -1...-499 Write register 4xxxx + 2 Sequence Number 0...65535 4xxxx + 3 Unread records left 0...499 4xxxx + 4 TimeStamp High byte:year, low byte:month (Year,Month) -
Page 37: Other Event Record Registers
Section 3 1MAC052634-MB D Vendor-specific implementation into the next 11 registers. If this is the first time the client reads events from the IED, the oldest event of the Modbus event buffer is loaded into the 11 event record registers. Selection code 2: Reading the oldest stored record Selection code 2 always forces the event reading to go back to the oldest event in the Modbus event buffer. - Page 38 Section 3 1MAC052634-MB D Vendor-specific implementation Unread records left This register shows how many unread event records still remain unread for the client in question at a particular moment. Time stamp registers Time stamp is either in local time or UTC time. The time stamp alternative is selected with a Modbus parameter.
- Page 39 Section 3 1MAC052634-MB D Vendor-specific implementation Clock not synchronized bit 13 The quality information bit is set in the IED's real-time clock if the IED has not been synchronized. Clock failure bit 12 The quality information bit is set in the IED's real-time clock if the clock has a severe failure.
- Page 40 Section 3 1MAC052634-MB D Vendor-specific implementation Table 22: Modbus event value alternatives Object derived from One Bit Data Two Bit Data 32 bit Data Meaning IEC 61850 Class Value Value Value Single Point Status Single Point Status of a controllable object Dual Point Status Dual Point Status of a controllable...
-
Page 41: Multiple Event Records Reading
Section 3 1MAC052634-MB D Vendor-specific implementation Table 25: Interpretation of the integer status data value Meaning Register address 4xxxx Higher 16 bit part of the 32 bit integer value 4xxxx + 1 Lower 16 bit part of the 32 bit integer value 1. - Page 42 Section 3 1MAC052634-MB D Vendor-specific implementation Reading out more event records than are available in the internal event buffer The requested amount of event records is always returned for reading. For example, if 10 event records are requested, but the IED only contains five event records, the last valid event record is repeated (duplicated) in the last five event records returned.
- Page 43 Section 3 1MAC052634-MB D Vendor-specific implementation Extended event record structure Table 28: Extended event record structure with the maximum of 10 event records Register Values Description Address 4xxxx Num of records 1...10 Write: Number of Event structures 4xxxx + 1 Selection Write: Selection code 4xxxx + 2...
-
Page 44: Fault Records
Section 3 1MAC052634-MB D Vendor-specific implementation Register Values Description Address 4xxxx + 101 Sequence Number 10 Event record 10 4xxxx + 102 Unread records left 10 4xxxx + 103 TimeStamp 10 4xxxx + 104 TimeStamp 10 4xxxx + 105 TimeStamp 10 4xxxx + 106 TimeStamp 10 4xxxx + 107... - Page 45 Section 3 1MAC052634-MB D Vendor-specific implementation Table 29: Header part of the record structure Register Values Comment Address 4xxxx Fault record selection 1...4 and -1...-99 Write register 4xxxx + 1 Sequence Number 0...65535 4xxxx + 2 Unread records left 0...99 4xxxx + 3 TimeStamp (Year,Month) High byte:year, low byte:month...
- Page 46 Section 3 1MAC052634-MB D Vendor-specific implementation 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. If the client has been reading fault records before, the IED knows which internal fault record has been sent to this specific client during the last reading.
- Page 47 Section 3 1MAC052634-MB D Vendor-specific implementation Other fault record registers Sequence number Every fault record is given a sequence number. The sequence number runs from 1 to 65535 and then rolls over to one again. The client can check that the sequence numbers of the recorded data are sequential.
-
Page 48: Parameter Setting Group Selection
Section 3 1MAC052634-MB D Vendor-specific implementation Clock failure bit 12 The quality information bit is set in the IED's real-time clock if the clock has a severe failure. Do not rely on this time stamp. 3.3.10 Parameter setting group selection The active parameter setting group can be changed by writing the new setting group number to 4X register. -
Page 49: Device Information
Section 3 1MAC052634-MB D Vendor-specific implementation Method 1: Synchronization in one step The real-time clock structure registers should be written in one multiple registers preset request (function 16) by a Modbus TCP/IP client or by a serial interface master. The IED's Modbus address or the Modbus broadcast address can be used with the serial interface. -
Page 50: Ascii Character Coding
Section 3 1MAC052634-MB D Vendor-specific implementation • HMI card SW and HW revision numbers • Slot 0 (X130) card SW and HW revision numbers • Slot 1 (X120) card SW and HW revision numbers • Slot 2 (X110) card SW and HW revision numbers •... -
Page 51: Reset Time Structure
Section 3 1MAC052634-MB D Vendor-specific implementation 3.3.13 Reset time structure The time and cause of the IED's last reset are stored into this structure. The reset time is taken directly from the IED's RTC at the startup. The clock might not be accurate and the data can be corrupted. - Page 52 Section 3 1MAC052634-MB D Vendor-specific implementation 615/620 series ANSI Communication Protocol Manual...
-
Page 53: Modbus Parameters And Diagnostics
Section 4 1MAC052634-MB D 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. Table 35: MODBUS settings Parameter Values (Range) Unit Step Default... - Page 54 Section 4 1MAC052634-MB D Modbus parameters and diagnostics Parameter Values (Range) Unit Step Default Description TCPWriteAuthority 0=No clients 2=All clients Write authority 1=Reg. clients setting for Modbus 2=All clients TCP/IP clients EventID 0=Address 0=Address Event ID selection 1=UID TimeFormat 0=UTC 1=Local Time format for 1=Local...
-
Page 55: Monitored Data
Section 4 1MAC052634-MB D Modbus parameters and diagnostics Monitored data The Modbus serial monitored data can be accessed with PST or via the LHMI path Monitoring > Communication > Modbus > Serial. Table 36: Modbus serial Parameter Values (range) Description 0...2147483648 Received Modbus frames by instance N Received frames N... - Page 56 Section 4 1MAC052634-MB D Modbus parameters and diagnostics 615/620 series ANSI Communication Protocol Manual...
-
Page 57: Glossary
Section 5 1MAC052634-MB D Glossary Section 5 Glossary 615/620 series Series of numerical IEDs for basic, inexpensive and simple protection and supervision applications of utility substations, and industrial switchgear and equipment Start/pickup status Application Configuration Tool in PCM600; Trip status ANSI American National Standards Institute ASCII... - Page 58 Section 5 1MAC052634-MB D Glossary Momentary change detect Modbus A serial communication protocol developed by the Modicon company in 1979. Originally used for communication in PLCs and RTU devices. Modbus ASCII Modbus link mode. Character length 10 bits. Modbus Allocation of accessible protocol data memory map Modbus RTU Modbus link mode.
- Page 60 Contact us ABB Inc. Distribution Automation 4300 Coral Ridge Drive Coral Springs, FL 33065, USA Phone:+1 (800) 523-2620 Phone:+1 954-752-6700 Fax:+1 954 345-5329 www.abb.com/substationautomation...