E560 Function Description

RTU560 Remote Terminal Unit
Function Description
Contents:
This manual describes the functions provided by the Remote Terminal Unit RTU560
RTU560 Function Description
Revision
Revision
Document identity:
1KGT 150 450 V000 1
Revision:
Date: 10/2000
We reserve all rights in this document and the information contained therein. Reproduction, use or disclosure to third parties without permission is strictly forbidden. Copyright 2000 ABB Utility Automation GmbH Ladenburg/Germany
ABB Utility Automation GmbH E560_FD.doc
1KGT 150 450 V000 1
iii
Contents
Contents
FUNCTION DESCRIPTION.....................................................................1-1 ABBREVIATIONS ......................................................................................1 ABOUT THE RTU560 FUNCTION DESCRIPTION ...................................3 1 RTU560 REMOTE TERMINAL UNIT ..................................................1-1
1.1 1.2 1.3 Overview ........................................................................................................... 1-1 Hardware .......................................................................................................... 1-3 1.2.1 Hardware Structure.............................................................................. 1-4 Software............................................................................................................ 1-9 1.3.1 RTU560 Software Structure............................................................... 1-10 1.3.2 I/O Bus Master and RTU560 I/O bus ................................................. 1-13 1.3.3 Event flow through RTU560............................................................... 1-14 Tools ............................................................................................................... 1-16 1.4.1 RTUtil NT ........................................................................................... 1-16 1.4.2 RTU560 Web Server ......................................................................... 1-19 1.4.3 RTU560 Web-Server System Requirements..................................... 1-19 1.4.4 Configuration File Transfer ................................................................ 1-19 1.4.5 Administration .................................................................................... 1-20 1.4.6 MULTIPROG wt ................................................................................. 1-21
1.4
2 SCADA MONITORING DIRECTION...................................................2-1

2.1 Indication Processing........................................................................................ 2-1 2.1.1 Function Distribution ............................................................................ 2-2 2.1.2 23BE21 Functions................................................................................ 2-2 2.1.3 PDP Functions of the CMU................................................................. 2-5 2.1.4 Group Information ................................................................................ 2-8 2.1.5 Error Handling.................................................................................... 2-10 Analog Measured Value Processing............................................................... 2-11 2.2.1 Analog measured value types............................................................ 2-11 2.2.2 Function Distribution .......................................................................... 2-11 2.2.3 23AE21 functions............................................................................... 2-12 2.2.4 PDP Functions of the CMU................................................................ 2-17 2.2.5 Error Handling.................................................................................... 2-19 Digital Measured Value Processing ................................................................ 2-21 2.3.1 Function Distribution .......................................................................... 2-23 2.3.2 23BE21 Functions.............................................................................. 2-23 2.3.3 PDP Functions of the CMU................................................................ 2-24 2.3.4 Error Handling.................................................................................... 2-26 Integrated Total Processing........................................................................... 2-27 2.4.1 Integrated Total Value Types ............................................................ 2-27
2.2
2.3
2.4
1KGT 150 450 V000 1
Contents
2.5
2.4.2 Function Distribution........................................................................... 2-28 2.4.3 23BE21 Functions .............................................................................. 2-28 2.4.4 PDP Functions of the CMU ................................................................ 2-29 2.4.5 Error Handling .................................................................................... 2-32 Bitstring Input Value Processing ..................................................................... 2-33 2.5.1 Bitstring value presentation ................................................................ 2-33 2.5.2 Function Distribution........................................................................... 2-33 2.5.3 23BE21 Functions .............................................................................. 2-34 2.5.4 PDP Functions of the CMU ................................................................ 2-34 2.5.5 Error Handling .................................................................................... 2-35
3 SCADA COMMAND DIRECTION....................................................... 3-1

3.1 3.2 3.3 Output Command Types................................................................................... 3-1 Function Distribution ......................................................................................... 3-1 Object Command Output .................................................................................. 3-2 3.3.1 Single Object Command Output .......................................................... 3-2 3.3.2 Double Object Command Output......................................................... 3-3 3.3.3 Single and Double Object Commands ................................................. 3-4 Regulation Step Command Output ................................................................. 3-14 Setpoint Command ......................................................................................... 3-15 3.5.1 Analog Setpoint Command Output .................................................... 3-15 3.5.2 Digital Setpoint Command Output...................................................... 3-18 Bitstring Output ............................................................................................... 3-21 Error Handling ................................................................................................. 3-22
3.4 3.5
3.6 3.7
4 HOST COMMUNICATION INTERFACE ............................................ 4-1

4.1 4.2 Overview HCI Software Structure ..................................................................... 4-3 Queue- and Buffer Handling ............................................................................. 4-4 4.2.1 Priority Read Queues ........................................................................ 4-7 4.2.2 Queue Transitions and Overflow.......................................................... 4-7
5 SUB-DEVICE COMMUNICATION INTERFACE ................................ 5-1

5.1 5.2 5.3 5.4 5.5 Message Flow in Monitoring Direction .............................................................. 5-3 Message Flow in Command Direction .............................................................. 5-3 General Interrogation ........................................................................................ 5-4 Time Synchronization........................................................................................ 5-4 System events................................................................................................... 5-5
6 INTERFACES AND NETWORK......................................................... 6-1

6.1 6.2 6.3 Network Configuration....................................................................................... 6-1 Interface Configuration...................................................................................... 6-2 6.2.1 The Interfaces ...................................................................................... 6-2 Duplex communication...................................................................................... 6-4 6.3.1 WT link full duplex (23WT21-23, no handshake)................................. 6-4 6.3.2 Direct Link (TxD/RxD only)................................................................... 6-5 6.3.3 Direct / Modem link (DTR, RTS/CTS, DCD handshake) ..................... 6-5 Half Duplex communication .............................................................................. 6-7
6.4
vi
1KGT 150 450 V000 1
Contents
6.4.1 6.4.2 6.4.3 6.4.4
WT link half duplex (23WT22, with CTS handshake).......................... 6-7 WT link half duplex (23WT21-23, with transmit delay time) ................ 6-8 Network Configuration Rules and Restrictions .................................... 6-9 Interface Configuration Rules and Restrictions ................................ 6-10
7 STARTUP, CONFIGURATION AND TIME MANAGEMENT ..............7-1

7.1 Startup Procedures ........................................................................................... 7-1 7.1.1 RTU560 CMU Start.............................................................................. 7-2 7.1.2 RTU560 System Start .......................................................................... 7-3 7.1.3 CMU Integration................................................................................... 7-3 7.1.4 CMU Removal...................................................................................... 7-4 RTU560 Configuration ...................................................................................... 7-5 7.2.1 General Requirements......................................................................... 7-5 7.2.2 Configuration File Load Procedure ...................................................... 7-5 RTU560 Time Management ............................................................................. 7-7 7.3.1 Time Management Principle ................................................................ 7-7 7.3.2 RTU560 Time Slave............................................................................. 7-9 7.3.3 Time Synchronization Modes............................................................... 7-9 7.3.4 Synchronization of Sub-RTUs............................................................ 7-12
7.2
7.3
8 STATUS AND DIAGNOSTIC INFORMATION ..................................8-13

8.1 8.2 Status and Error Report to NCC ..................................................................... 8-13 Web-Server Diagnosis.................................................................................... 8-13 8.2.1 System Diagnosis .............................................................................. 8-13 8.2.2 Status Information.............................................................................. 8-14 LEDs, Alarm and Warning .............................................................................. 8-16 8.3.1 CMU Alarm and Warning................................................................... 8-16 8.3.2 RTU560 Alarm and Warning.............................................................. 8-16 8.3.3 LED Indications .................................................................................. 8-16
8.3
9 TABLES ..............................................................................................9-1
9.1 9.2 System Messages ............................................................................................ 9-1 System Events .................................................................................................. 9-5
1KGT 150 450 V000 1
vii
Contents
Figures
Figure 1-1: Figure 1-2: Figure 1-3: Figure 1-4: Figure 1-5: Figure 1-6 Figure 1-7: Figure 1-8: Figure 1-9: Figure 1-10: Figure 2-1: Figure 2-2: Figure 2-3: Figure 2-4: Figure 2-5: Figure 2-6: Figure 2-7: Figure 2-8: Figure 2-9: Figure 2-10: Figure 2-11: Figure 2-12: Figure 2-13: Figure 2-14: Figure 2-15: Figure 3-1: Figure 3-2: Figure 3-3: Figure 3-4: Figure 3-5: Figure 3-6: Figure 3-7: Figure 3-8: 8 Figure 3-9: Figure 3-10: Figure 3-11: 11 Figure 3-12: Figure 3-13: Figure 3-14: Figure 3-15:: Figure 3-16: Figure 3-17: Figure 4-1: Figure 4-2: Figure 4-3: Figure 4-4: Figure 5-1: Figure 5-2: Figure 6-1: Figure 6-2: Figure 6-3: RTU560 communication capabilities in principle..............................................................1-2 RTU560 Hardware structure in principle ..........................................................................1-4 RTU560A (configuration example) ...................................................................................1-7 Main Subrack RTU560C (configuration example with 23ET23).......................................1-8 Software packages of RTU560 ......................................................................................1-10 Software Structure..........................................................................................................1-10 Dialog RAM array between SLC and IOC ......................................................................1-13 Event polling by MPU .....................................................................................................1-14 Event flow through RTU560 ...........................................................................................1-15 Network RTU Hardware Primary Process................................................................1-17 Indication Type Definition .................................................................................................2-1 Digital Filter for Contact Bouncing ....................................................................................2-3 Oscillation Suppression on 23BE21 .................................................................................2-5 Midposition suppression for Double Indication .................................................................2-7 Analog Value Presentation by ADC................................................................................2-11 Zero Value Supervision and Switching Detection...........................................................2-13 Smoothing of Analog Values ..........................................................................................2-14 Threshold Supervision with Integration ..........................................................................2-15 Live Zero Conversion .....................................................................................................2-17 Analog Value Conversion AMI........................................................................................2-18 Threshold Supervision on Absolute Value......................................................................2-19 Digital Measured Value presentation..............................................................................2-22 Example for inversion of DMI8 .......................................................................................2-25 Integrated Total Values Definition for EPR and IR ........................................................2-27 Reading ITI within the RTU560 .....................................................................................2-31 Single Command definition: pulse output.........................................................................3-2 Single Command definition: persistant output..................................................................3-3 Double Command definition: pulse output .......................................................................3-3 Double Command definition: persistent output ................................................................3-4 Response Indication procedure........................................................................................3-5 Process commands without supervision (1 pole) .............................................................3-6 Process command without supervision (2 pole)...............................................................3-7 Interaction PDP - 23BA20 for a process command output without command supervision3Object command output with supervision (1,5 pole) ........................................................3-9 Object command output with supervision (2 pole) .........................................................3-10 Interaction PDP - 23BA20 - 23BA22 for a process command with command supervision3Retrigger / stop of a regulation command ......................................................................3-14 Live Zero Output Conversion by a 23AA20 board..........................................................3-15 Analog Value Conversion ASO ......................................................................................3-16 Set Point Command for Analog Output ..........................................................................3-17 Digital Setpoint Value presentation ................................................................................3-19 Set Point Command for Digital Output ...........................................................................3-20 RTU560 Network ..............................................................................................................4-1 Interface IC Application Layer Link Layer ...................................................................4-3 RTU HCI queues ..............................................................................................................4-4 Queue handling transition diagram...................................................................................4-7 RTU560 Network ..............................................................................................................5-1 Internal structure of the SCI .............................................................................................5-2 RTU Network with Interfaces............................................................................................6-1 Duplex communication .....................................................................................................6-4 WT link full duplex transmit control ..................................................................................6-5
viii
1KGT 150 450 V000 1
Contents
Figure 6-4: Figure 6-5: Figure 6-6: Figure 6-7: Figure 6-8: Figure 7-1: Figure 7-2: Figure 7-3: Figure 8-1: Figure 8-2: Figure 8-3: Figure 8-4: Figure 8-5: Figure 8-6: Figure 8-7:
Direct / Modem link ......................................................................................................... 6-6 Dial up configuration......................................................................................................... 6-6 Half Duplex communication ............................................................................................. 6-7 WT-Mode, Halfduplex, with CTS transmit control............................................................ 6-8 WT-Mode, Halfduplex, no handshake transmit control.................................................... 6-9 Principal of time synchronization in RTU560.................................................................... 7-8 Time Master and Slave dependencies............................................................................. 7-9 Time accuracy in a multi level network (CS Commands only) ....................................... 7-12 LEDs 560SLI01 .............................................................................................................. 8-17 LEDs 560ETH01 ............................................................................................................ 8-17 LEDs 23AA20 / 23AE21 / 23BE21 ................................................................................. 8-18 LEDs 23BA20 / 23BA22 ................................................................................................. 8-18 LEDs 23WT22................................................................................................................ 8-22 LEDs 560RTC01 ............................................................................................................ 8-23 LEDs 560RTC02 ............................................................................................................ 8-24
1KGT 150 450 V000 1
ix
Introduction
Abbreviations
CMU AMI ASO BCU BSI CS CSC CS-Command DCO DMI DPI DSO EPI GCD HCI IED IOC IOD IOM ITI MFI MPU
NCC
Communication and Data Processing Unit Analog Measured value Input Analog Setpoint command Output Bus Connection Unit Bit String Input (8, 16 bit) Control System Command Supervision Channel Clock Synch Command Double Command Output Digital Measured value Input (8, 16 bit) Double Point Input Digital Setpoint command Output (8, 16 bit) Event of Protection equipment Input (1bit) General Configuration Data Host Communication Interface Intelligent Electronic Device I/O Controller (Controller on I/O Board) Input Output Data I/O Bus Master (Function of SLC) Integrated Totals Input Analog Measured value Floating Input Main Processing Unit Network Control Center Peripheral Bus Peripheral Bus Processor Process Data Processing
PB PBP PDP
1KGT 150 450 V000 1
Introduction
PLC PPP PSU RCO RTC RTC SBO SCADA SCI SCO SEV SLC SOC SPI STI TSI TSO
Programmable Logic Control Point to Point Protocol Power Supply Unit Regulation step Command Output Real Time Clock Real Time Clock Select before Operate Supervision, Control and Data Acquisition Sub-Device Communication Interface Single Command Output System Events Serial Line Controller Strobe Output Channel Single Point Input Step position Input (8 bit) Time Synch Input Time Synch Output
1KGT 150 450 V000 1
Introduction
About the RTU560 Function Description

Application Hints for the Use of RTU560
The following chapters have to be regarded before a RTU560 Remote Terminal Unit is mounted and commissioned.
Regulations for the installation and operation of electrical systems

The ABB RTU560 devices are produced under the attention of the relevant regulations and appointments, especially to IEC 61131 part 2. Die RTU560 is classified according to IEC 60664-1 (DIN VDE 0110): Insulation coordination for equipment within low-voltage systems Part 1: Principles, requirements and tests
Pollution degree 2 Only non-conductive pollution occurs except that occasionally a temporary conductivity caused by condensation is to be expected Overvoltage category II is in accordance with the appointment in IEC 61131 part 2
The user has to ensure that the devices and the components belonging to them are mounted under the attention of such safety regulations and standards as may from time to time be in force.
DIN VDE 0100 DIN VDE 0106
Erection of power installations with nominal voltages up to 1000 V Protection against electrical shock Part 100: Actuating members positioned close to parts liable to shock Safety of machinery; Electrical equipment of machines Part 1: General requirements Electronic equipment for use in electrical power installations and their assembly into electrical power installations Telecommunications Programmable controllers Part 2: Equipment requirements and tests
EN 60204 EN 50178
DIN VDE 0800 IEC 61131
If the pollution degree 2 (VDE 0110) cannot be guaranteed or an ongoing protection against direct contact is required the devices should be mounted into appropriate cubicles. If ABB RTU560 devices are coupled with or fed by power-frequency voltage networks of overvoltage category III qualified protective provisions have to be taken to guarantee
1KGT 150 450 V000 1
Introduction
overvoltage category II according to VDE 0110 at the terminal connectors (e.g. surge voltage protectors).
Installation and application hints

Documentation
This document contains all essential functions of the RTU560 boards for the use in the RTU560. For more details and additional information the documents described in chapter "Related documents" have to be used.
Qualified personnel
The RTU560 modules conduct partly dangerous contact voltages at their connectors. Touching parts which are alive can force heavy injuries of health. Installation, commissioning and maintenance of such systems is therefore only allowed by technical instructed personnel. It should have relevant knowledge:
dealing with dangerous voltages the use of specifications and standards. In particular EN (VDE-) and accident preventation regulations.
Use according to the rules

The RTU560 was developed, manufactured, tested and documented while observing the relevant standards. When observing the valid regulations for installation, commissioning and maintenance, the product poses no danger to health and objects in normal case. Use according to the rules means that the RTU560 is operating and maintained exclusively in the form as described in the functional- and module description documents. Especially the technical data for the process-circuits and the supply should be regarded. Any liability for the consequences of incorrect use or after unauthorized repairs is rejected.
1KGT 150 450 V000 1
Introduction
WARNINGS, CAUTIONS
Earth the devices
Before connecting any power to the device, the 6.3 mm Faston connector should be wired to protection earth. The earthing may be removed only if it is certain that no more power is being supplied to the device. Regard the earthing principles for the serial peripheral bus (direct or capacitive earthing)
Connection of the supply voltage
A terminal block feeding dangerous contact voltages (supply voltage, input/output channels) should only be plugged or withdrawn in off load state.
Protect the device from dampness, dirt and damage during transport, storage and operation. Do not operate device outside of the specified technical data Operate device according to the protection degree IP 20
Mount it into a closed cubicle or rack if the environmental conditions that requires.
Do not obstruct the ventilation for cooling
Do not cover the ventilation slots by cables or wires.
Lead signal- and power-lines separately
Capacitive and inductive interferences of the power lines to signal lines should be prevented by appropriate cable laying (distance, crossing).
Use overvoltage protection in cables to outdoor antenna
1KGT 150 450 V000 1
Introduction
Graphic Aids in the Function Description

Throughout the description three different graphical aids are used to indicate:
Symbol Description An information hint which should be regarded or which helps to find an essential point of the chapter etc.
A caution hint which is important to know if you configure the RTU560. Which informs about a restriction etc. A configuration hint which shows where a parameter or any other configurable point is described.
Find the cross reference

Description of... Function of RTU560. Tables Chapter 1 to 8 9
Cross reference to RTUtil NT Users guide
Digital Filter
The configuration param eter Digital filter specifies how m any milliseconds an input must be stable before it is accepted as a new signal state. The typical value is 10 m s. Digital filter is used to prevent ordinary contact bouncing. Param eter: Digital filter (SPI/DPI PDP Parameters)
ABB Utility Automation GmbH
1KGT 150 450 V000 1
2-3
Chapter in RTUtil NT Users Guide
1KGT 150 450 V000 1
Introduction
Related documents
The RTU560 Function Description is part of the total documentation of the RTU560 remote terminal unit. For more details and additional information use the following documents:
1 KGT 150 451
RTUtil NT Users guide
Handling etc. of all RTU560 PC-based utilities Handling the RTU560 Web Server Hardware data sheets of all RTU560 boards and units Connection and Settings of all RTU560 boards and units
1KGT 150 456
Web Server Users guide
1 KGT 150 457
Hardware 1
1 KGT 150 458
Hardware 2
1KGT 150 450 V000 1
1.1
Overview
Based on a modular multi-CPU concept, RTU560 is designed for extremely high communication and data processing capability. Maintaining the proven I/O board family of RTU200 and RTU232, it fulfills the requirements for high end remote terminal units:
Modular hardware and software configuration Compact construction Low number of board types Up to 8 communication interfaces to NCCs Up to 60 communication interfaces to sub-devices Support of various communication protocols Scaleable performance State-of-the-art configuration tool RTUtil NT with external data interface Web Server based access to configuration data and application program files Web Server based process and system diagnosis Programmable logic control function according to IEC 61131-3 Redundancy concept for central components (CMUs and power supply)
RTU560s communication capabilities are shown in principle in Figure 1-1.
1KGT 150 450 V000 1
1-1
Station Control
Telecontrol Center(s)
IEC 60870-5-104 WAN

IEC 60870-5-104 IEC 60870-5-101 DNP 3.0 IEC 60870-5-101 DNP 3.0
IEC 60870-5-104
RTU 560
IEC 60870-5-101 DNP 3.0 SPABus Modbus IEC 60870-5-103 IEC 60870-5-101 DNP 3.0
IED IED IED

Protection and Control Units
Sub-RTU
Process
Marshalling Rack
IED
Figure 1-1:
RTU560 communication capabilities in principle
1-2
1KGT 150 450 V000 1
1.2
Hardware
Each hardware board is described in detail in the hardware data sheet. Board settings and wiring principles are explained in the unit and application descriptions. All RTU560 hardware boards are based on the European standard card format (100 x 160 mm). Table 1-1 lists the board types that are available to configure a RTU560 remote terminal unit.
Type
Communication and Processing Units
Ident
560ETH01 560SLI01 560BCU01 560BCU02
Function
Ethernet Unit Serial Line Interface Unit Connection Unit to extend the RTU560 system bus to a second 560CSR01 (RTU560A) Connection Unit to provide the RTU560 system bus to a pair of two CMUs within an I/O subrack 23TP21 (RTU560C) Connection Unit to provide the RTU560 system bus to a pair of two CMUs within an I/O subrack 23ET23 (RTU560C) Analog Output 2 channels / board Analog Input 8 channels / board Binary Output 16 output relays / board Binary Input 16 inputs / board Binary Output 16 interposing relays Interposing Binary Input 16 inputs for 110 V DC and interposing / or total galvanic isolation Fibre Optic Coupler Fibre optic coupler for 1 serial interface RTU560 I/O bus / RS422 / RS485 / RS232 C Real time clock GPS time receiver Real time clock DCF77 time receiver Leased line modem FSK CCITT V.23 modem Leased line modem FSK selective modem Communication Subrack I/O Subrack Mounting plate version I/O Subrack Hinged frame version Power Supply Unit Input ranges 24 ... 60VDC / with redundancy logic 110 ... 220VDC for Communication Subracks Power Supply Unit Input ranges 24 ... 60VDC / 110 ... 220VDC for I/O Subracks AC / DC converter 24 V DC / 2 A output battery charging function AC / DC converter 24 V DC / 10 A output
Bus Connection Units 560BCU03
I/O Boards with IOC
23AA20 23AE21 23BA20 23BE21 23BA30 23BE30 23OK22
Interposing I/O boards
General boards / units
Subracks
560RTC01 560RTC02 23WT21 23WT22 560CSR01 23TP21 23ET23 560PSU01
Power supply / mains adapter
23NG24
23VG23 23VG24
Table 1-1:
RTU560 boards
1KGT 150 450 V000 1
1-3
1.2.1
Hardware Structure
RTU560 in principle is built up by one or two main subracks containing the Communication and Processing Units (CMUs) with the serial or Ethernet communication interfaces and I/O subracks with the I/O boards. There are two types of RTU configurations:
RTU560A with up to 16 CMUs placed in one or two communication subracks 560CSR01, I/O boards placed within up to 24 I/O subracks 23ET23 or 23TP21. RTU560C with one or two CMUs placed in one of the I/O subracks 23ET23 or 23TP21 together with up to 15 I/O boards within this main subrack; further I/O boards placed within another up to 23 I/O subracks 23ET23 or 23TP21.
Network Control Centers
CMU
CMU
CMU
CMU
RTU560 System Bus
CMU
CMU
CMU
CMU
I/O Boards IED

Sub-RTU
IED
I/O Boards I/O Boards I/O Boards
IED
Sub-RTU
IED
Figure 1-2:
RTU560 Hardware structure in principle
1-4
1KGT 150 450 V000 1
The CMUs communicate over the RTU560 system bus which is provided on the backplane of the communication subrack 560CSR01 (RTU560A) or by means of bus connection units (RTU560C). The I/O subracks are connected to the CMUs serial RS485 interfaces A or B. In total up to four I/O bus segments may be configured, with up to 6 I/O subracks connected to each of them. This gives a maximum capacity of 24 I/O subracks for one RTU560. If one of the serial interfaces of a CMUs interface pair A and B is used for I/O bus connection, the pairs other interface may only be used for another I/O bus segment (cannot be used for other types of communication protocols)! Bus connection units do not only provide the system bus connection between communication subracks (RTU560A) resp. CMUs (RTU560C), but in addition the system signals
local alarm (relay contact) local warning (relay contact) TSI (Time Sync Input signal) TSO (Time Sync Output signal)
If one of these signals has to be provided externally, e.g. if the RTU has to be synchronized by any type of time synchronization pulse signal (including those used with 560RTC01 and 560RTC02 real time clocks), one of the appropriate BCU boards has to be configured within the RTU, although if not required for system bus interconnection between communication subracks (RTU560A) or CMUs (RTU560C).
1KGT 150 450 V000 1
1-5
1.2.1.1
Configuration type RTU560A

RTU560A is the RTU560 configuration type providing - in addition to the local I/O connections - multiple communication interfaces to NCCs and Sub-Devices like SubRTUs, Protection Equipment, Bay Control Units and IEDs (e.g. intelligent Transducers). This configuration type has also to be used when redundant power supplies for the main subracks are required. Up to 8 CMUs can be configured within one communication subrack 560CSR01. Adding a second communication subrack provides another 8 CMU slots giving a maximum number of 16 CMUs for one RTU560. In this configuration, within both communication subracks, a system bus connection unit 560BCU01 has to be used which provides the system bus interconnection between the two communication subracks. Besides PSUs, CMUs and bus connection units, the two real time clock units 560RTC01 (GPS receiver) and 560RTC02 (DCF77 receiver) are the only boards of RTU560s board family that can be placed within the communication subrack. All other boards have to be placed within I/O subracks.
1-6
1KGT 150 450 V000 1
Communication subrack 560RTC01

560PSU01
5V 24 V
560PSU01
5V 24 V A B
560ETH01
Tx Rx CE ERR A E MMI C E A B
560ETH01
Tx Rx CE ERR A C E MMI A A B
560ETH01
Tx Rx CE ERR A C MMI A A B 1 2
560SLI01
Tx Rx CE ERR A B 1 2 MMI A
560SLI01
560SLI01
560SLI01
Tx Rx CE ERR
560RT C02
ERR
560BCU01
ALR WRN TSI TSO SEB
S1 123 4 OFF
FR MMI A LS MN
UE + UE PE
UE + UE PE
B E
B E
ON OFF
ON OFF
1 2
1 2
1 2
1 2
I/O subrack 23TP21

23NG24
24 V 5V
UE + UE PE
ON
0FF
Max. 6 I/O subracks per I/O bus segment I/O subrack 23TP21
23NG24
24 V 5V
UE + UE PE
ON
0FF
Figure 1-3:
RTU560A (configuration example)
1KGT 150 450 V000 1
RTU I/O bus segment
1-7
1.2.1.2
Configuration type RTU560C

RTU560C is the compact RTU560 configuration type, providing - in addition to the local I/O connections - up to 6 communication interfaces to NCCs or Sub-Devices like SubRTUs, Protection Equipment, Bay Control Units and IEDs (e.g. intelligent transducers). One or two CMUs can be configured within one of the RTUs I/O subracks, thus building the RTUs main subrack. In this configuration, if two CMUs are to be configured, a system bus connection unit 560BCU02 (23TP21) or 560BCU03 (23ET23) has to be used which provides the system bus interconnection between the two CMUs. Besides the two slots reserved for CMUs, within RTU560Cs main subrack 15 slots remain available for I/O boards, modems, RTCs or optical couplers from the RTU560 board family. The I/O bus (first segment) is provided by one of the CMUs serial interface CPB, internally connected to the I/O bus on the backplane of the main subrack. Additional I/O subracks are added to this first I/O bus segment using the standard I/O bus interfaces provided by the I/O subracks. Interface CPA of the CMU which provides the I/O bus interface may be used as additional I/O bus segment only.
23NG24
23BE21 23BE21 23BE21 23BE21 23BE21 23BE21 23BE21 23BE21 23BE21 23BE21 23BE21 23BE21 23BA21 23BA21 23BA21
A
560SLI01
Tx Rx CE A B 1 2 MMI
560SLI01
Tx Rx CE
5V 24 V
ST
ST
ST
ST
ST
ST
ST
ST
ST
ST
ST
ST
ST PST
ST PST
ST PST
B 1 2
1 2 3 OFF
UE + UE PE ON
1 2 3 4 5 6 7 8
9 10 11 12 13 14 15 16
1 2 3 4 5 6 7 8
9 10 11 12 13 14 15 16
1 2 3 4 5 6 7 8
9 10 11 12 13 14 15 16
1 2 3 4 5 6 7 8
9 10 11 12 13 14 15 16
1 2 3 4 5 6 7 8
9 10 11 12 13 14 15 16
1 2 3 4 5 6 7 8
9 10 11 12 13 14 15 16
1 2 3 4 5 6 7 8
9 10 11 12 13 14 15 16
1 2 3 4 5 6 7 8
9 10 11 12 13 14 15 16
1 2 3 4 5 6 7 8
9 10 11 12 13 14 15 16
1 2 3 4 5 6 7 8
9 10 11 12 13 14 15 16
1 2 3 4 5 6 7 8
9 10 11 12 13 14 15 16
1 2 3 4 5 6 7 8
9 10 11 12 13 14 15 16 CO CO CO
MMI
OFF
Figure 1-4:
Main Subrack RTU560C (configuration example with 23ET23)
1-8
1KGT 150 450 V000 1
1.3
Software
The high processing performance of the RTU560 Remote Terminal Unit is accomplished by effective distribution of the tasks to the communication and processing units (CMU) and the microcontrollers on the I/O boards. Each of the input/output boards has its own input/output microcontroller (IOC) which is used to support the basic input/output functions of the board. The CMUs have various tasks:
Communication with the network control center(s) Communication with subordinated devices Updating of the data base for the process signals, handling of the SCADA functions which are not performed by the I/O-boards
The different processors of a CMU (MPU and SLC) can work independently of each other and are decoupled from each other via shared memories. Different CMUs can handle different tasks independently and communicate with each other via the internal system bus. By this means optimal execution of the individual tasks is accomplished. The program system of the RTU560 remote terminal unit is of modular design and consists of the following program types:
Microcontroller programs Standard programs Application programs
The microcontroller programs of the boards are optimized to the components and for the defined functions. They are an integral part of the boards. The standard programs written in C programming language cover the programs for all telecontrol functions, for system monitoring, time management and for the handling of the process data base. The 32 bit operating system used in RTU560 is VxWorks (Wind River Systems). The PLC programs for the tasks of station automation functions are cyclically executed by the optionally installed PLC software.
1KGT 150 450 V000 1
1-9
Local I/O and Process Data Processing
Communication Protocols
System Control and Diagnosis
PLC Function
Application Software
Hardware Networking Device Drivers
PC-Card Drivers
File Systems
FTP Server
Web Server
Standard Software Packages
VxWorks Real Time Operating System
Operating System
Figure 1-5: Software packages of RTU560
1.3.1
RTU560 Software Structure

The RTU560 software is structured into different activities. All activities can run on one CMU or the activities can be distributed to different CMUs. The number of CMUs depends on type and number of the required communication interfaces (e.g. Ethernet, RS232 Interface).
NCCs
HCI Host Communication Interfaces
Data Base
Configuration Files
PLC IEC1131
IC Internal Communication
SCI Sub-Device Communication Interfaces
MMI Interfaces
Board Control and Diagnosis
Central System Control and Time Administration
PDP Process Data Processing and IO-Board Control
IEDs
Sub-RTUs
Local I/O Board
Figure 1-6
Software Structure
1-10
1KGT 150 450 V000 1
The different activities and the distribution to the CMUs is configured automatically within RTUtil NT. The information is available in the configuration files.
IC Internal Communication
All activities communicate with each other via the internal communication (IC). The IC is a protocol independent communication system. Every activity can distribute messages. Every activity receives all messages distributed. The internal communication is used to communicate between the activities of one CMU or between the activities on different CMUs.
RTU560 System Control and Time Administration

This activity is running once in the RTU560 on the CMU configured as Administrator Mode: Master. RTU560 System Control is handling the system startup and supervision of all CMU boards. The runtime integration of a configured CMU board is handled by this activity. The Time Administration for the complete RTU560 is done by this activity.
Board Control and Diagnosis

This activity is running once on each CMU with board. Board Control and Diagnosis is handling startup and supervision of a CMU board. The Web-Server for Diagnosis belongs to this activity.
PDP Process Data Processing and I/O Bus Master

This activity is running on each CMU for the interfaces COMA or COMB connected to I/O bus segments. This activity handles the process data processing and supervision and control of the local I/O boards. The serial line controller (SLC) is loaded with the I/O bus master (IOM) firmware. The IOM controls the I/O bus interfaces (COM A and COM B).
HCI Host Communication Interfaces

This activity is running on each CMU with interfaces COM1, COM2, COMA, COMB or ETH which are connected to a control center communication line. It is possible to run multiple HCIs on one CMU. The HCI activity handles the complete communication protocol including all individual communication queues and buffers. If CPA or CPB is used the SLC is loaded with the communication interface firmware.
1KGT 150 450 V000 1
1-11
SCI Subordinate Device Communication Interfaces

This activity is running on each CMU with interfaces CP1, CP2, CPA or CPB connected to a sub-device communication line. It is possible to run multiple SCIs on one CMU. The HCI activity handles the complete communication protocol including all individual communication queues and buffers. If CPA or CPB is used the SLC is loaded with the communication interface firmware.
Data Base
The Data Base activity is running on each CMU board. The data base collects all process messages and all system status messages. In the data base the actual state of this data points and the qualifiers are stored. The Web-Server shows the actual state of the data base of the requested CMU.
PLC IEC 61131-3

It is possible to define one PLC activity per CMU board. The activity is running on each CMU where a PLC FUNCTION is configured with RTUtil NT. The PLC function can run on a CMU with other communication functions (HCI or SCI). In these cases the priority of the CMU is below the communication. It is possible to run a PLC function on a CMU without communication functions (HCI or SCI).
MMI Interface
The MMI Interface activity is running on each CMU board. Via PPP protocol the diagnosis Web-Server can be accessed.
1-12
1KGT 150 450 V000 1
1.3.2
I/O Bus Master and RTU560 I/O bus

The I/O bus master IOM is the master for the I/O boards connected to the RTU560 I/O bus. The communication protocol between IOM and I/O board is tailored to achieve a maximum throughput. The protocol is totally independent of any communication protocol used to communicate with the network control center. The main processing unit (MPU) is master to the IOM. The MPU stores any output request to an I/O board etc. in a dialog RAM. The IOM will read that part and expand it to complete dialogs with the addressed I/O board. The IOM stores any event or answer from I/O boards in the dialog RAM and forces an interrupt to the MPU that there is a message from IOM.
CMU
MPU
I/O Board
Input signal state RAM Output signal state Relocation register for ITI SLC FIFO Parameter register Requests Dialog registers Status etc. Busmodule IOC I/O Task I/O Part
Figure 1-7:
Dialog RAM array between SLC and IOC
The main task of the IOM is to poll all configured boards for events. To be independent of the board type (23BE21, 23AE21 etc.), a dialog RAM array is specified which has the same structure for all RTU560 I/O boards with an I/O controller (IOC). Within the IOC software the "Busmodule" task handles in a standardized form the dialog with the IOM. The IOC reads and writes directly into the dedicated registers and informs the busmodule. The busmodule handles the dialog RAM for the I/O task. The I/O task is board specific.
1KGT 150 450 V000 1
1-13
Read event flag of subrack
Subrack: = 1
NO
Is there any event message within subrack ?
YES
Read event flag of each configured board within subrack. Create list of board with event
Read one event into RAM to MPU. Increment event list pointer
Address next board with event
More events in subrack ?
YES Subrack: = subrack + 1
NO
All subracks polled for events ?
NO
YES Poll one board and read board status Increment board pointer
Board status o.k. ?
NO
Store board status into RAM to MPU YES
Command output requests will be inserted if pending
Figure 1-8:
Event polling by MPU
1.3.3
Event flow through RTU560

Figure 1-9 explains and qualifies the different levels which an event has to pass before it is transmitted to the NCC.
1-14
1KGT 150 450 V000 1
NCC Network Control Center
Communication Buffer, Queues Signal processing MPU < 1 ms / event
MPU - HCI Task
IC
Internal Communication < 1 ms / event
Signal processing MPU < 1 ms / event
MPU - SCI Task MPU - HCI Task
MPU - PDP Task
Signal processing MPU < 1 ms / event
IED or Sub-Station
RAM
SLC - IOM Task
I/O bus transmission typ. 20 .. 60 ms for a complete polling cycle (approx. 7 ms / event)
FIFO Process signal scanning and peprocessing time depends on signal type Binary input: 1 ms cycle Analog input: typ. 580 ms (at 50 Hz)
IOC
Process Signal
Figure 1-9:
Event flow through RTU560
SLC IOM Task

The transmission time from I/O board to the MPU depends on the overall situation of the IOM.

MPU
Number of subracks and boards Number of pending events within a subrack Output requests from MPU to I/O board To increase the transmission time it is possible to split the I/O boards on up to 4 I/O bus segments managed by up to four CMUs.
The transmission time through the MPU depends on the CMU configuration. PDP and HCI may run on the same CPU or on different CPUs
1KGT 150 450 V000 1
1-15
1.4
Tools
The RTU560 is easy to engineer and maintain by using the utility RTUtil NT to configure the RTU560, MULTIPROG wt to program and test the PLC functions and the RTU560 Web-Server for diagnosis and file transfer issues. There is no proprietary tool delivered by ABB for protocol analysis issues. For further information ask your local distributor to get a recommendation for third party protocol analysis tools.
1.4.1
RTUtil NT
RTUtil NT is the configuration and engineering tool for the RTU560, contains the following topics: Features:

1.4.1.1
Configuration and engineering tool for RTU560 networks Generating of files for each RTU560 The principles of user interface structuring according to IEC 61346-1 MS Windows NT 4.0 platform The User Interface of RTUtil NT is application based on the Microsoft standard presentation format Documentation of all project steps External data interface Multilingual tool (user interface and help files) Delivered on CD-ROM with installation and uninstallation program
RTUtil NT System Requirements

The performance requirements for the configuration and engineering tool RTUtil NT, particularly the free disc space, depends on the project size. Basic requirements are:
Operating system: Microsoft Windows NT 4.0 Memory: 64 MB RAM Processor: Pentium class Hard disc: > 200MB free disc space Hard lock (dongle)
1-16
1KGT 150 450 V000 1
1.4.1.2
Basic Concept
RTUtil NT is designed to engineer all types and sizes of RTU560 including interfaces to IEDs that are used in a common station network. The process signal mapping to the different communication protocols is one of the main tasks needed in hierarchical communication network structures. The general view of the user to the engineering data is implemented on the basis of international Standard IEC 61346-1. This Standard describes the structuring principles and reference designations for industrial systems, installations and equipment. The user interface structure offers three trees to build up the system.
NetworkTree The NetworkTree shows the lines and protocols for routing the data points through the network. SignalTree The location and designation of signals are shown in the SignalThree. The signal location describes the place of the data points in the primary process. HardwareTree The HardwareTree presents the structure of an RTU with the levels cabinet, rack, board and the reference to the data points defined in SignalTree.
The structuring in trees allows a common presentation format and a general user interface of the RTU data and the environment.
04 Plant Ladenburg 110kV CS 1

Line 1
CS 2
Line 2 Line 4
Line 1 Com Subrack Line 2 Segment 1 560CSR01 Rack TP21 Segmen 2 Rack TP 21
RTU 01
Line 3
23 NG 23560SLI01 Tx Rx CE 560SLI01 Tx Rx CE 1 1 5V MMI A 2 1 MMI 2 1 24V UP 2 2 B B A B B On A A Off
Q0
Segment 1 Rack TP21 Segment 2 Rack TP21
RTU 11
RTU 21 SPAx1 SPAx2 SPAx2

Line 4
Line 3
RTU 12 Line 5
Peripherie Bus
21.03 MW
Figure 1-10:
Network RTU Hardware Primary Process
1KGT 150 450 V000 1
1-17
1.4.1.3
Engineering Steps
The engineering of the RTU560 data consists of several steps that demand a sequence in the data engineering process. The engineering steps could be different, if interfaces for external data import are used (e. g. Excel import). The following steps describe the basic engineering sequence:
Project configuration (start) Set the project environment data. Build up the tree structures
Build up the station network topology in the NetworkTree. Define the lines and the communication protocols between the stations. The NetworkTree is required for routing the process data points through the RTU network. Definition of data points in SignalTree. The Result of this definition is the unique object identifier for each data point. Definition of all RTUs and IEDs with their data points in the HardwareTree. The HardwareTree contains the full description of the RTU hardware in detail (cabinets, racks, boards). Also link steps to build up the relations between the trees are done in the HardwareTree. If a data point is added or linked to the HardwareTree the automatic signal routing functionality for this data point will be executed. The signal routing depends on the topology and the communication protocols in the NetworkTree.
Set parameters, communication addresses Set single parameters for several tree objects. Check project plausibility and generate the download file for a single RTU. Documentation
Generate the project documentation. Choose the RTU and the configuration parts, which have to be documented.
1-18
1KGT 150 450 V000 1
1.4.2
RTU560 Web Server

The RTU560 Web Server, integrated in the RTU560 firmware, presents information to a standard browser (e. g. Microsoft Explorer) and offers the following functions:

1.4.3
Loading configuration files to and from the RTU Loading firmware to the RTU System diagnosis with a chronological view to events in the RTU Process diagnosis that indicates the actual process status Administrate different user groups
RTU560 Web-Server System Requirements

To get access to the RTU560 Web-Server pages a standard browser with Java Script implementation is needed. There are no restrictions to the operating system that is used. The physical connection to the RTU may be a serial connection or an Ethernet connection. If the CMV is not configured, the RS232 connection must be used.
1.4.4
Configuration File Transfer

The user menu allows the following operations:
Get information about the actual used file versions Write of the GCD-File to the RTU (basic hardware data of the RTU) Write of the IOD-File to the RTU (IO data of the RTU) Read of the IOD-File from the RTU (to extract a complete RTUtil NT project from the configuration file) Delete GCD-File file in the RTUs file system Delete IOD-File file in the RTUs file system Reset of the RTU
1KGT 150 450 V000 1
1-19
1.4.4.1
Firmware File Transfer

The user menu allows the following operations:

1.4.4.2
Get information about the actual used firmware version Loading of the application firmware files to the RTU Loading of the IO-Bus Master firmware files to the RTU Loading of the license file to the RTU Reset of the RTU
System diagnosis
The system diagnosis indicates RTU560 events in a list in chronological order. The information for each indication in this list is structured as follows:

1.4.4.3
Date Time Indication text
Status information
The status information page shows the RTU560 hardware structure as known from the RTUtil NT HardwareTree. Next to the static hardware configuration following information is provided:
Display the actual process data states for all information in monitoring direction Get information about the actual state of the system event and status indications Get information about several parameters (e. g. TCP/IP address of the Ethernet board)
1.4.5
Administration
The administrator point in the RTU560 Web-Server allows to restrict the access to the different pages on the RTU.
Modify user groups (add or delete new users) Change passwords for existing users
1-20
1KGT 150 450 V000 1
1.4.6
MULTIPROG wt
The RTU 560 PLC development system MULTIPROG wt is a standard programming and test system for IEC 61131-3 designed PLCs. It is based on the standard IEC 61131-3. MULTIPROG wt allows an easy programming in function block diagram (FBD) and/or instruction lists (IL) under Windows NT. The programming system offers powerful features for the different development steps of a PLC application:
Edit Compile Debug Print
The programming system is based on a modern 32 bit windows technology, providing comfortable handling using:

1.4.6.1
zooming scrolling customizable toolbars drag & drop operations a shortcut manager movable windows.
MULTIPROG wt System Requirements

To run the MULTIPROG wt PLC programming system, the following workstation requirements must at least be fulfilled
Operating system: Microsoft Windows NT 4.0 Memory: 64 MB RAM Processor: Pentium class (133 MHz minimum, 200 MHz Recommended) Hard disc: > 60MB free disc space Hard lock (dongle)
1KGT 150 450 V000 1
1-21
SCADA Monitoring Direction
2.1
Indication Processing
There are two types of indications:
Single point input (SPI) Double point input (DPI)
Figure 2-1 shows the signal definition for SPI and DPI. Double indications are represented by two sequential bits within a 23BE21 board. The normal state of a DPI is an antivalent bit combination (10 or 01). The two intermediate positions 11 or 00 are handled with no difference within the RTU560. An intermediate state is given during the runtime of a unit from one position to the other (e.g. an isolator from OFF to ON).
Signal state OFF 1 0 ON 1 0 10 OFF
Double point indication (DPI)
Signal state ON OFF 1 0
Single point indication (SPI)
00
01 ON
11 faulty position
0 OFF OFF ON 4 3 2 1
1 ON
0 OFF
normal position
intermediate position 8 7 6 5
16 15 14 13 12 11 10 9
Bit position within board DPI number within board
DPI 8 DPI 7 DPI 6 DPI 5 DPI 4 DPI 3 DPI 2 DPI 1
Figure 2-1:
Indication Type Definition
Within an indication board of max. 16 bit SPI and DPI can be mixed. But a DPI can start on an odd bit-position only. Within a 23BE21 board it is possible to mix any type of binary inputs. E.g. inputs not assigned to DPI or SPI may be configured to indications as pulse counters, digital measured values on bitstring inputs. Digital measured values and bitstring inputs must be configured starting with bit position 1.
1KGT 150 450 V000 1
2-1
2.1.1 Function Distribution

The process data acquisition functions for indications processed by the RTU560 can be split into functions handled by the:
I/O controller (IOC) of the binary input board 23BE21 Process data processing (PDP) part of the CMU Protocol specific communication interface part at a CMU
The data processing functions of the communication interface is described in the documentation of the specific communication protocol. 23BE21 functions:
-
Reading input register (every millisecond) Digital filter (contact bouncing) Oscillation suppression (signal chattering) Signal inversion Time out monitoring for DPI intermediate position Store events in FIFO with time stamp
CMU - PDP:
-
Intermediate midpoint position handling for DPI Command output response Group signals Transmission to internal communication
2.1.2 23BE21 Functions

The IOC of the 23BE21 supports the indication functions. The parameter of each function is loaded from PDP part of the CMU at start up or if it must be initialized. Some parameters are valid for the complete 16 inputs, others can be set individually per input. The 23BE21 reads all 16 inputs periodically every millisecond regardless of specified data point type. The IOC handles the necessary activities for all 16 bits within that millisecond. Reading every millisecond allows the high event resolution for indications. Each board does this independently from each other for a block of 16 bits. If the data point is Blocked the status is set to blocked and no changes are reported from the PDP. Parameter: Blocked (SPI/DPI PDP Parameters)
2-2
1KGT 150 450 V000 1
Digital Filter
The configuration parameter Digital filter specifies how many milliseconds an input must be stable before it is accepted as a new signal state. The typical value is 10 ms. Digital filter is used to prevent ordinary contact bouncing. Parameter: Digital filter (SPI/DPI PDP Parameters)
If an indication has changed its state and should be transmitted as an event to the PDP, the time stamp of the event is the time of the last edge before the filter time elapsed.
input channel
1
0
digital filter time counter 255

7 6 5 4 3 2 1 0
digital filter time (e.g. 7 ms)
1ms
(a)
time event into FIFO with time stamp of (a)
Figure 2-2:
Digital Filter for Contact Bouncing
1KGT 150 450 V000 1
2-3
Oscillation Suppression
Indications which change their state very often produce a higher transmission load to NCC. To prevent a permanent transmission it is possible to specify an automatic indication blocking if the number of events per time period exceeds a defined value. Oscillation suppression may be activated or deactivated individually per indication. The configuration parameter is Maximum chatter frequency . Maximum Chatter Frequency is defined to:
MAX CHA FREQ = number of changes second
The monitoring period is calculated:
Tosc =
2000 [milliseconds] MAX CHA FREQ
Parameter: Maximum Chatter Frequency
(SPI/DPI PDP Parameters)
Tosc is the monitoring period. The max. value is 100Hz, a typical value is 2. The 23BE21 is loaded with the parameter. Each leading edge of 0->1 starts the monitoring period tosc. Within that time interval each leading edge increments the chatter counter register of that indication. The third change within that period puts the indication into the dynamically blocked state. The 23BE21 informs the PDP by an event with the qualifier BL = 1 (blocked). It starts a reset time period (fix to 60 seconds). Within that reset time each new start trigger (0->1 edge) starts tosc again. If the indication state is stable for at least this reset time period, the 23BE21 informs PDP by an event with the qualifier BL = 0 (normal).
2-4
1KGT 150 450 V000 1
Input channel 1 indication 0
chatter counter register
60 sec reset time

3 2 1 0
tosc
tosc
tosc
time
event into FIFO with status: Input = Invalid
event into FIFO with status: Input = Valid
Figure 2-3:
Oscillation Suppression on 23BE21
Intermediate Midposition Handling for DPI

The 23BE21 handles the two bits of the double indication. Signal state changes of the DPI are transmitted to the PDP. Intermediate positions (0-0; 1-1) are indicated by a special status bit to PDP. The 23BE21 monitors the time window for intermediate position. The time out value is loaded as a parameter from PDP. If the DPI does not get a new end position within the allowed time, the 23BE21 generates an event with the actual state and status DPI intermediate position time out.
FIFO storage on 23BE21

To decouple event bursts from I/O bus transmission etc., the events are stored into the 23BE21 board FIFO. Up to 50 events can be stored within the FIFO. If the FIFO becomes full the 23BE21 stops its activities until there is space. Each event has a time stamp with a resolution of one millisecond within a minute. The absolute time is expanded by the PDP.
2.1.3 PDP Functions of the CMU

The PDP receives all events out of the 23BE21 FIFO. The PDP handles all other functions specified for that indication.
Command output response

The functionality of a response indication to stop an related command output pulse is described at command processing section of this document.
Intermediate Midposition suppression for DPI

This function is only valid for double indications (DPI). Figure 2-4 shows how that is handled within the RTU560.
1KGT 150 450 V000 1
2-5
The configuration parameter Supervision Time for MIDPOINT specifies whether or not a DPI message should be transmitted for the event when the indication changes to a midposition. PDP keeps the first signal change internal. If an abnormal situation occurs, the message of the leading edge is sent to NCC in addition and allows a more detailed analysis of the error situation of the unit. The parameter Supervision time for midpoint specifies the time window where the RTU560 should inhibit the transmission of the midposition. If the new state is not indicated to the RTU in this time the RTU generates a DPI telegram with the actual position (normally then 00). The qualifier IV (invalid) keeps 0, because this is a valid process information. Parameter: Supervision time for midpoint (DPI PDP Parameters)
2-6
1KGT 150 450 V000 1
Supervision time for mid point = active

Supervision time 1 0 OFF 1 0 DPI 1 ON OFF 0 1 0 DPI 1 ON 0 1 OFF 0 DPI Abnormal state change time out Abnormal state change ON -> intermediate -> ON ON Normal signal state change ON -> OFF
DPI
Supervision time for mid point = inactive

1 0 OFF 1 0 DPI 1 ON OFF 0 1 0 DPI 1 ON OFF 0 1 0 DPI Abnormal state change time out DPI Abnormal state change ON -> intermediate -> ON DPI ON Normal signal state change ON -> OFF
Figure 2-4:
Midposition suppression for Double Indication
1KGT 150 450 V000 1
2-7
Signal Inversion
After having a stable indication signal it is possible to define the logical state for the signal, corresponding to the signal voltage level. This function is the signal inversion. The inversion is defined by a configuration parameter Invert the input value.
logical 0 = OFF logical 1 = ON
INVERSION = NO 0V Process Voltage
INVERSION = YES Process Voltage 0V
Table 2-1:
Definition of Inversion
All other functions are then based on the signal state given by the inversion parameter. Parameter: Invert the input value (SPI/DPI PDP Parameters)
2.1.4 Group Information

Group information are single point information data objects that are calculated from other SPIs by logical operations. The RTU560 supports different group information types:
OR groups (>=) AND groups (&) NOR groups Dynamic OR groups
A group information data object can be generated out of all single point information (SPI) processed in the RTU560. A group information can also be an input to another group information. The number of input signals per group information is limited to 16 signals. The group information is communicated as SPI event on the internal communication. The time stamp of the event will be the time of the input signal which forces the new event message.
OR group
The output signal of an OR group is set to 1 when at least one input signal is set to 1. The first signal which is set to 1 forces the transmission of the OR group signal. The output signal of an OR group is set to 0, when all input signals are 0. The trailing edge of the last signal which is set to 0 forces the transmission of the OR group signal.
2-8
1KGT 150 450 V000 1
AND group
The output signal of an AND group is set to 1 when all input signals are set to 1. The last input signal which is set to 1 forces the transmission of the AND group signal. The output signal of an AND group is set to 0, when at least one input signal goes to 0. The trailing edge of this signal forces the transmission of the AND group signal.
NOR group
The output signal of a NOR group is set to 0 when at least one input signal is set to 1. The first signal which is set to 1 forces the transmission of the NOR group signal. The output signal of a NOR group is set to 1, when all input signal are 0. The trailing edge of the last signal which is set to 0 forces the transmission of the NOR group signal.
Dynamic OR group
The output signal of a dynamic OR group is set to 1 every time a input signal is set to 1. Every signal which is set to 1 forces the transmission of the OR group signal. The output signal of a dynamic OR group is set to 0, when all input signal are 0. The trailing edge of the last signal which is set to 0 forces the transmission of the OR group signal.
Qualifier for group signals

A group signals qualifiers represent the logical OR of the qualifiers of all input signals of the group information.
1KGT 150 450 V000 1
2-9
2.1.5 Error Handling

23BE21 board failure
A 23BE21 board can be set "out of service":
the board has never been in service (configuration error) the board failed during normal operation (hardware failure, I/O bus failure etc.) the board has been removed or subrack power was lost. If a board is set out of service the qualifiers of all configured indications are set INVALID due to board failure. The RTU560 treats all DPI and SPI messages of that board with qualifiers IV = 1.
A 23BE21 board can be set in service again during runtime:
if the board is replaced if power is turned on again in the subrack if the I/O bus is O.K.
When this happens the following sequence recovers the indications: normalize the 23BE21 load all parameters for the configured indications (done by PDP) read all values (signal state) Reset qualifier IV to 0 and transmit the actual value and qualifier status to NCC.
Dynamic Qualifier Changes

An indication can change qualifier status at runtime if:
the 23BE21 board fails (qualifier IV = 1) the oscillation suppression is activated and triggered for that indication (qualifier BL = 1)
2-10
1KGT 150 450 V000 1
2.2
Analog Measured Value Processing
2.2.1 Analog measured value types

Each analog value is converted by the analog digital converter (ADC) of the 23AE21 board into a signed integer presentation. The presentation is shown in Figure 2-5. The 100% input signal value is represented with 12 bit plus sign.
[digits] + 4096
3000 2000 1000 e.g. -20..+20 mA
-20 -100
-15
-10
-5
5 25
10 50
15 75
20 [e.g. mA] 100 [%]
-2000 -3000
Input signal
- 4096
Analog Value Presentation according to IEC 870-5-101
Figure 2-5:
Analog Value Presentation by ADC
The PDP converts the value to a normalized presentation.

The process data acquisition functions for analog measured values (AMI analog measured value input) processed by the RTU560 can be split into functions handled by:
IOC of the analog input board 23AE21 Process data processing (PDP) part of the CMU Protocol specific communication interface at a CMU
1KGT 150 450 V000 1
2-11
The data processing functions of the communication interface is described in the documentation of the specific communication protocol. 23AE21:
-
Scan analog input cyclically Zero value supervision and switching detection Smoothing Threshold supervision on integrator algorithm Periodic update of RTU data base Store events into FIFO with time stamp
CMU - PDP functions:

-
Unipolar and live zero conversion Scaling Threshold supervision on absolute threshold value Transmission to internal communication
2.2.3 23AE21 functions

The IOC of the 23AE21 board supports the analog measured value (AMI) functions. The parameters of each function and each AMI are loaded from PDP at start up or if the board must be initialized during runtime. If the data point is blocked the status is set to Blocked and no changes are reported from the PDP. Parameter: Blocked (AMI PDP Parameters)
Line Frequency and Scan Cycle

Each channel is scanned by the IOC of the 23AE21 cyclically. The scan cycle is given by the AC line frequency:
50 Hz: 60 Hz: 16.6 Hz:
580 milliseconds for all 8 channels 500 milliseconds for all 8 channels 1620 milliseconds for all 8 channels
The scan frequency is independent from the number of configured channels. The Line frequency must be equal to the 23AE21 hardware setting (boardwide parameter). Parameter: Line frequency (AMI PDP Parameter)
2-12
1KGT 150 450 V000 1
Zero Value Supervision and Switching Detection

An input signal between + 0.25 % and - 0.25 % is forced to 0 %. This allows to reject noise on the input signal produced by the transducer etc. The zero value supervision is fixed to 0.25 % and always active The switching detection is a special function of the 23AE21. It is used to force a value update to PDP if a signal changes only some few percent from/to zero. The function is only active when threshold supervision with integration is selected. The threshold supervision on integrator algorithm would need some cycles before the threshold is exceeded and reported to NCC. This gives a transient situation, e.g. the 380 kV transmission line is switched but the actual current does not change more or less immediately. Switching detection operates in that form that every time a signal changes to/from 0 % from/to more than 2.5 % the new value is transmitted to PDP immediately. If the new value is below 2.55 % an event is not forced. PDP transmits the received value to NCC regardless of any other parameter. Switching detection is a fixed parameter and can not be parameterized
Event transmission to UB due to switching detection Input Signal [%] +2.5
+0.25 zero value zone 0 - 0.25 scan cycle 23AE21 -2.5 time
Figure 2-6:
Zero Value Supervision and Switching Detection
1KGT 150 450 V000 1
2-13
Smoothing
Unstable input signals may be smoothed to prevent too many CS updates. Smoothing can be parameterized per input by the configuration parameter Smoothing . No smoothing can be configured. The smoothing factor is given in binary factors. Parameter: Smoothing (AMI PDP Parameter)
Input Signal [%] 80 70 60 50 40 30 20 10
MW
MWngl for e.g. k=2
scan cycle 23AE21
time
Figure 2-7:
Smoothing of Analog Values
The IOC calculates the new value by the formula:
MWngl =
MW ngl MW MW agl k = = = =
MW MWagl K
+ MWagl
new calculated analog measured value raw analog measured value (result of A/D conversion) last calculated value smoothing factor (2, 4, 8, 16, .. 128)
2-14
1KGT 150 450 V000 1
Threshold Supervision on Integrator Algorithm

Threshold supervision can be done on two different methods within RTU560. The decision of which method is active depends on the configured parameters. If threshold supervision with integration is selected the 23AE21 board is doing it. The IOC calculates at each cycle the difference between the last reported analog value and the actual value. The difference is added to the accumulated value in the threshold difference register. If the accumulated deltas exceed the parameterized threshold value, the actual value is stored into the FIFO and reported to PDP . The actual value becomes the last reported value. The threshold difference register is set to zero. The accumulation is done in consideration of the sign of the difference.
Input Signal [%] 60 new value transmission 40 new value transmission
new value transmission
20 deltas (differences) to last reported value 0 time scan cycle 23AE21
Threshold DifferenceRegister [% of input signal] + 10 + threshold 0 - threshold -10
exceed threshold
exceed threshold
exceed threshold
time
example = threshold = 10 % of input signal
Figure 2-8:
Threshold Supervision with Integration
1KGT 150 450 V000 1
2-15
The threshold difference register is cleared if:
the value exceeds the threshold value the switching detection supervision was triggered the value passed a monitored limit
The threshold value can be parameterized by Threshold. To be independent of the scan cycle the threshold is calculated on a threshold integration per second. The threshold is rescaled according to the Line frequency:
50 Hz: 60 Hz: 16.6 Hz:
threshold threshold threshold
= = =
Threshold / 0.58 Threshold / 0.5 Threshold / 1.62
The maximum loadable threshold for an 23AE21 board is 50 % (1024 digits) of the nominal value and referenced to a scan cycle. By rescaling the threshold to a per second standard the nominal threshold will be:
50 Hz: 60 Hz: 16.6 Hz:
threshold threshold threshold
= = =
up to 29% of nominal value up to 25% of nominal value up to 81% of nominal value ( AMI PDP Parameter) ( AMI PDP Parameter)
Parameter: Threshold Line frequency
Periodic update of RTU data base

If a periodic update of the RTU560 data base is required, the 23AE21 board can be parameterized to transmit the AMV periodically. The configuration parameter Periodic Update specifies how often the data base should be updated. Parameter: Periodic Update ( AMI PDP Parameter)
The periodic update is independent of threshold supervision with integration. That means a value might be transmitted twice to PDP in a cycle: 1. 2. caused by threshold exceeding caused by periodic update
The periodic update time is selectable between 1, 2, 4, 8, 30 and 60 seconds.
2-16
1KGT 150 450 V000 1
FIFO storage of 23AE21

To decouple event bursts from I/O bus transmission etc. the events are stored into the 23AE21 board FIFO. Up to 50 events can be stored within the FIFO. If the FIFO becomes full and the IOC has to store events it stops its activities until there is space. Each event has a time stamp with a resolution of one millisecond within a minute. The absolute time is expanded by the PDP . For each measured value written to the FIFO the IOC reads the actual time. The effective time quality is equivalent to the scan cycle of the analog input board.

Bipolar, Unipolar and Live Zero conversion
The input signal type allows to specify unipolar input signals. That means a negative value is not allowed (possible). The RTU560 flags an unipolar defined input signal with the qualifier invalid (qualifier IV = 1) if the value becomes negative (> Zero Value Supervision = - 0.25 %). Input signals with live zero presentation (standard = 4..20 mA) are transformed to the standard presentation of 0...100 % by the PDP. The conversion is done in the form that:
20 % of the input signal rage (standard: 4 mA) becomes 0 % of the normalized AMI value 100 % of the input signal rage (standard: 20 mA) becomes 100 % of the normalized AMI value
Input signals below 20 % (4 mA) are set to 0 %. For a value below 17,5 % (3,5 mA) the AMI is indicated to be faulty (qualifier IV=1)
100 %
0%
4 mA (0%) < 3,5 mA = invalid' 20 mA (100%) Input signal
Figure 2-9:
Live Zero Conversion
The configuration parameter Input signal type specifies the input is a bipolar, a unipolar or a live zero signal. The configuration parameter Input signal range specifies the hardware setting of the 23AE21 board.
1KGT 150 450 V000 1
2-17
Parameter: Input signal range Input signal type
( AMI PDP Parameter) ( AMI PDP Parameter)
Scaling
The PDP converts the value to a normalized AMI format. The configuration parameter Conversion factor specifies the percentage of the maximum input signal that is defined as 100 % of the normalized value. Parameter: Conversion factor ( AMI PDP Parameter)
Normalized AMI value

[digits] + 100 %
e.g. conv. factor = 75 %
-20 -100
-15 -75
-10 -50
-5 -25
5 25
10 50
15 75
20 [e.g. mA] 100 [%]
Input signal
- 100 %
Figure 2-10:
Analog Value Conversion AMI
Threshold Supervision on absolute Threshold Value

Threshold supervision can be done on two different methods within RTU560. The decision of which method is active depends on the configured parameters. In this mode the PDP checks each AMI received from 23AE21 against the last reported value. If the new value exceeds the last reported value plus threshold the received AMI will become last reported value and is transmitted to NCC. The threshold value can be parameterized by Threshold. The threshold is monitored every nn seconds. Therefore the 23AE21 transmits the actual value periodically. The period is given by the configuration parameter Periodic update.
2-18
1KGT 150 450 V000 1
Parameter: Threshold Periodic update
(AMI PDP Parameter) (AMI PDP Parameter)
Input [%] 100 new value 80 new value 60 threshold value new value 40 New value transmission to CCI 20 new value new value
time periodic update cycle (uc)
Figure 2-11:
Threshold Supervision on Absolute Value
Only one method can be used for threshold supervision. Either the integration method or on absolute threshold.

AMV overflow and/or A/D converter errors
The 23AE21 board checks at start up and during each conversion the functionality of the A/D converter. If an error is detected the AMIs are marked invalid. The qualifier IV is set to 1 and transmitted to NCC with the new state. For AMIs with live zero conversion a value below 17,5 % (standard: 3,5 mA) is marked invalid.
1KGT 150 450 V000 1
2-19
23AE21 board failure

A 23AE21 board can be set "out of service":
the board has never been in service (configuration error) the board failed during normal operation (hardware failure, I/O bus failure etc.) the board has been removed on-line or subrack power was lost.
If a board is set out of service all configured AMIs are set to the invalid state. The RTU560 transmits all AMI messages of that board to the NCC with the qualifier IV = 1. A 23AE21 board can be set in service again during runtime:
When this happens the following sequence recovers the AMIs: normalize the 23AE21 load all parameters for configured channels (from PDP) read all values and update status reset qualifier IV to 0 and transmit the actual value and qualifier status to NCC.

An AMI can change qualifier status at runtime if:
the 23AE21 board fails (qualifier IV = 1) the live zero supervision detects a current below 17.5 % input range (3.5 mA) (qualifier IV = 1) the unipolar value is below 0.25 % input range (qualifier IV=1) the value has an overflow of the ADC signal input (qualifier OV = 1) the scaling by means of conversion factor gives a result of more than 100 % (qualifier OV = 1)
2-20
1KGT 150 450 V000 1
2.3
Digital Measured Value Processing

There are two types of digital measured values (DMV):
Digital measured input value (DMI) Step position input value (STI)
The RTU560 can handle different bit pattern to read them and convert them into a digital measured value :
8 bit digital measured value (DMI8) 16 bit digital measured value (DMI16) 8 bit step position value (STI)
The RTU can handle conversions for: binary data (BIN) binary coded decimals (BCD) Gray code (GRAY)
The maximum length of a digital measured value is the word of 16 bit (= one 23BE21 board). Double word values (23 bit) are not supported.
1KGT 150 450 V000 1
2-21
Digital measured value presentation

Each type is converted and scaled by the PDP.
16 15 14 13 12 11 10 9 (a) (b) (c) (d) (e) (f) (g) (h) (i) (j) (k) (l) S S S 0..9 0..7 0..9 0..9 S S
23BE21 Input Channel
16 bit unsigned binary data 15 bit + sign binary data 8 bit unsigned binary data 7 bit + sign binary data 0..9 0..9 0..9 S 0..7 0..9 0..9 0..9 0..9 4 Decade BCD unsigned 4 Decade BCD signed 2 Decade BCD unsigned 2 Decade BCD signed 16 bit gray code 15 bit signed gray code
8 bit gray code 7 bit signed gray code
Scaling and/or Conversion
(A)
STI Word = Step Position (Value = -64 ... +63 steps) Word = Signed Integer DMI
(B)
S value two's complement S = Sign bit / Sign position
Figure 2-12:
Digital Measured Value presentation
An digital measured input value DMI is scaled to a normalized 16 bit value representation (+/- 100 %) For the step position information (STI) of a transformer or Petersen coil the value can only be in the range of -64 .. +63. If an eight bit pattern is selected the residual 8 bit of the 23BE21 board can be used for another digital value, for pulse counter values or indications.
2-22
1KGT 150 450 V000 1

The data acquisition functions for digital measured values processed by the RTU560 can be split into functions handled by:
IOC of the binary input board 23BE21 Process data processing (PDP) part of the CMU Protocol specific communication interface part at a CMU
-
Reading input register (every millisecond) Digital filter (contact bouncing) Consistency check Store events in FIFO with time stamp
CMU - PDP:
-
Signal inversion Scaling and format conversion Transmission to internal communication

The IOC of the 23BE21 board supports the digital measured value (DMV) functions. The parameter of each function and each DMV is loaded from PDP at start up or if the board must be initialized during runtime. The 23BE21 reads all 16 inputs periodically every millisecond regardless of the specified data point type. The IOC handles the necessary activities for all 16 bits within that millisecond. If the data point is Blocked the status is set to blocked and no changes are reported from the PDP. Parameter: Blocked (DMI/STI PDP Parameters)
1KGT 150 450 V000 1
2-23
Digital filter
The configuration parameter Digital filter specifies how many milliseconds an input must be stable before it is accepted as a new signal state. The typical value is 10 ms. Digital filter are used to prevent ordinary contact bouncing. Parameter: Digital filter (DMI/STI PDP Parameters)
Consistency check
A DMV is a bit pattern of 8 or 16 bit length. The value is valid only if all binary channels of the DMV are valid and stable for at least the consistency check time. This is given if no input changed for the parameterized consistency check time. Any change on an input channel retriggers the settling time. The minimum settling time is defined by the PDP parameter Consistency check time. The minimum consistency time is 100 milliseconds. Parameter: Consistency check time (DMI/STI PDP Parameters)
FIFO storage of 23BE21

If a DMV has changed and is stable for at least the consistency time, it is stored into the FIFO and transmitted to the PDP.

The PDP receives all events out of the 23BE21 FIFO. The PDP handles all other functions specified for that DMV.
Signal Inversion
Inversion is only possible for DMI not for STI inputs. The PDP parameters Invert input signal and Invert sign of input value specify a bit inversion of the digital input value. The inversion of the sign bit can be configured independent from the inversion of the value bits. Parameter: Invert the input signal Invert the sign of input value (DMI PDP Parameters) (DMI PDP Parameters)
2-24
1KGT 150 450 V000 1
DMI 8 Process Input Invert the input value = NO = YES = NO = YES Invert the sign = NO = NO = YES = YES
S PV
7 0V
6 0V
5 0V
4 0V
3 0V
2 0V
1 PV
1 1 0 0
0 1 0 1
0 1 0 1
0 1 0 1
0 1 0 1
0 1 0 1
0 1 0 1
1 0 1 0
0V = 0V;
PV = Process voltage;
S = Sign bit
Figure 2-13:
Example for inversion of DMI8
Scaling and format conversion

The PDP parameter DMI/STI Value presentation and Input signal type specifies which DMV type is connected to the 23BE21 board. STI values are always handled as 7 bit signed integer, range -64 ... +63. For DMI inputs, the parameter Maximum value specifies the binary value that is converted to 100 % of the scaled DMV value. The binary value of the STI is limited to the range 64..+63 steps. Parameter: DMI/STI Value presentation Input signal type Maximum value (DMI/STI PDP Parameters) (DMI PDP Parameters) (DMI PDP Parameters)
1KGT 150 450 V000 1
2-25

the board has never been in service (configuration error) the board failed during normal operation (hardware failure, I/O bus failure etc.) the board has been removed or subrack power was lost.
If a board is set out of service the configured digital measured values are to the invalid state. All DMI/STI are set faulty. The RTU560 transmits the DMI/STI values of that board to the NCC with the corresponding message and the qualifier IV = 1. A 23BE21 board can be set in service again during runtime:
When this happens the following sequence recovers the DMVs: normalize the 23BE21 load all parameters for the configured DMIs/STIs (done by PDP) read all values Reset qualifier IV to 0 and transmit the actual value and qualifier status to NCC .

A DMV can change qualifier status at runtime if:
the 23BE21 board fails (qualifier IV = 1) if the maximum value specified for a DMI input is exceeded (qualifier 0V = 1) if any digit of a BCD coded DMI input has an invalid code > 9 ( Qualifier IV = 1)
2-26
1KGT 150 450 V000 1
2.4
Integrated Total Processing
2.4.1 Integrated Total Value Types

There are two types of integrated total values (ITI) defined in the RTU560:
End of period reading counters (EPR) Intermediate reading counters (IR)
Both types have only one source and the IR is only an intermediate value of the corresponding EPR. That means there is one ITI which is transmitted periodically in fixed periods.
Counts
Integrated Total Values with reset to zero at end of period The IR reading cycle must be 1/n of end of period time e.g.: if period = 60 minutes and n = 5 the IR cycle = 12 min
Period Intermediate reading cycle
Period End of IR Period reading reading End of Period reading
Period End of Period reading
Period End of Period reading
time
Figure 2-14:
Integrated Total Values Definition for EPR and IR
Integrated Total Value presentation

Although the internal value representation is 32 bit signed integer the RTU560 supports on its local inputs positive ITI values only. This allows ITI values between:
0..and...+ 2 147 483 647
1KGT 150 450 V000 1
2-27

The process data acquisition functions for ITIs processed by the RTU560 can be split into functions handled by:
IOC of the binary input board 23BE21 Process data processing (PDP) part of the CMU Protocol specific communication interface part at a CMU in the
The data processing functions of the communication interface is described documentation of the specific communication protocol. 23BE21 functions:
-
Reading input register (every millisecond) Digital filter (contact bouncing) Increment integration register Freeze integration register into relocation register
CMU - PDP:
-
Freeze and read ITIs periodically Transmission to internal communication

The IOC of the 23BE21 supports the integrated total functions. The parameter of each function is loaded from PDP at start up or if it must be initialized. Parameters can be set individually per input. The 23BE21 reads all 16 inputs each millisecond. If the channel is configured for integrated total a signal change of 0->1 is accepted after digital filtering to be a pulse count and increments the pulse counter register. Whenever the PDP sent a broadcast command to freeze counter values, the 23BE21 reads the actual integration register and stores the contents into the relocation register. The PDP receives the frozen ITI value from the 23BE21.
Digital filter
The configuration parameter Digital filter specifies how many milliseconds an input must be stable before it is accepted as a new signal state. The typical value is 10 ms. Digital filter are used to prevent ordinary contact bouncing. Parameter: Digital filter (ITI PDP Parameters)
2-28
1KGT 150 450 V000 1
Integrated Total Frequency

The RTU560 can read ITI counter increments with a frequency of max. 25 Hz. The default digital filter is 10 ms (necessary when normal relay contacts are used). The ratio for the 0 and 1 state should be 1:1 (min. 20 ms each).
Freeze ITI value

EPR or IR readings are forced by the PDP periodically. The PDP sends a broadcast command to all I/O boards: "freeze ITI registers". Each 23BE21 on which ITI's are configured stores the actual integrated total register contents into a relocation register. This is done within normal signal processing, the integrated total register continues counting. The frozen values are transmitted afterwards to the PDP.

Reading ITI counter values and update ITI status
Reading is done:
for each configured IR cycle for each configured EPR period
The frozen ITI values are read from all ITIs which are configured for the actual period. It is not necessary to have all ITIs in the same EPR periods or IR cycles. The time accuracy for reading ITIs is 0.5 seconds referenced to the internal RTU560 system time. A new hard time synchronization will also actualize the next ITI reading cycle event. There are some qualifier information which inform NCC about the quality of the ITI. This qualifiers are updated at each ITI reading.
1KGT 150 450 V000 1
2-29
EPR / IR parameters
With the PDP parameter Acquisition of end of period reading ITI the transmission of EPR readings can be switched off or the EPR period in minutes is specified. The parameter End of period wrap around counter specifies that the ITI value is not reset after an EPR reading. Parameter: Acquisition of end of period reading ITI End of period wrap around counter (ITI - PDP parameters) (ITI - PDP parameters)
With the PDP parameter Acquisition of intermediate reading ITI the transmission of IR readings can be switched of or the IR period is specified. With Unit of IR cycle it is possible to decide whether IR period is defined in second or minute cycles. Parameter: Acquisition of intermediate reading ITI Unit of IR cycle (ITI - PDP parameters) (ITI - PDP parameters)
CA = Counter was adjusted since last reading

This flag is set if the counter is:
restarted due to RTU560 restart the time changed during the period / cycle (new time synchronization)
If the RTU560 system time has changed due to a new received time base (hard synchronization) the CA qualifier is set. CA is set if the time changed more than 5 seconds from the old system time. The flag is set in the first telegram of an intermediate value (IR) and in the first telegram of an end of period value (EPR). If the EPR telegram comes first the qualifier is not set in the following IR telegram.
2-30
1KGT 150 450 V000 1
IV = ITI is invalid
This flag is set if the ITI value is not valid because the PDP could not receive the value from the 23BE21 board.
CS
RTU560
EPR period IR cycle EPR and IR values ITI queue
freeze PCV register
relocation register
Integration Register
23BE21
Puls from Metering Device
Figure 2-15:
Reading ITI within the RTU560
IT = Invalid time
This flag is set in the time information element of the ITI telegram until the RTU560 has a valid system time and is synchronized after start up.
1KGT 150 450 V000 1
2-31

If a board is set out of service the configured ITIs qualifiers are set to invalid due to board failure. The RTU560 transmits all ITI messages of that board to the NCC with an ITI message and the qualifier IV = 1. A 23BE21 board can be set in service again during runtime:
When this happens the following sequence recovers the pulse counter values: normalize the 23BE21 load all parameters for the configured channels (done by PDP part of CMU) read all values and update status Reset qualifiers IV for affected ITIs

An integrated total value can change qualifier status at runtime if:
the 23BE21 board fails (qualifier IV = 1)
2-32
1KGT 150 450 V000 1
2.5
Bitstring Input Value Processing

The RTU560 can handle bit patterns to read them and convert them into a bitstring input value (BSI):
8 bit bitsting (BSI8) 16 bit bitstring (BSI16)
The maximum length of a bitstring is the word of 16 bit (= one 23BE21 board). Double word values are not supported.
2.5.1 Bitstring value presentation

Bitstring input values are transparent mapped into 32 bit BSI messages of the internal communication. If an eight bit pattern is selected the residual 8 bit of the 23BE21 board can be used for another bitstring value, digital measured value, integrated total values or indications.

The data acquisition functions for bitstring values processed by the RTU560 can be split into functions handled by:
IOC of the binary input board 23BE21 Process data processing (PDP) part of the CMU Protocol specific communication interface part at a CMU
-
Reading input register (every millisecond) Digital filter (contact bouncing) Consistency check Store events in FIFO with time stamp
CMU - PDP:
-
Transmission to internal communication
1KGT 150 450 V000 1
2-33

The IOC of the 23BE21 board supports the bitstring value (BSI) functions. The parameter of each function and each BSI is loaded from PDP at start up or if the board must be initialized during runtime. The 23BE21 reads all 16 inputs periodically every millisecond regardless of the specified data point type. The IOC handles the necessary activities for all 16 bits within that millisecond.
Digital filter
The configuration parameter Digital filter specifies how many milliseconds an input must be stable before it is accepted as a new signal state. The typical value is 10 ms. Digital filter is used to prevent ordinary contact bouncing. Parameter: Digital filter (BSI PDP Parameters)
Consistency check
A BSI is a bit pattern of 8 or 16 bit length. The value is valid only if all binary channels of the BSI are valid and stable for at least the consistency check time. This is given if no input changed for the parameterized consistency check time. Any change on an input channel retriggers the settling time. The minimum check time is defined by the PDP parameter Consistency check time. The minimum consistency time is 100 milliseconds. Parameter: Consistency check time (BSI PDP Parameters)
FIFO storage of 23BE21

If a BSI has changed and is stable for at least consistency time, it is stored into the FIFO and transmitted to the PDP.

The PDP receives the BSI events out of the 23BE21 FIFO. The PDP handles all other functions specified for that BSI. The BSI input value is transparent copied in the BSI message starting with bit 1.
2-34
1KGT 150 450 V000 1

the board has never been in service (configuration error) the board failed during normal operation (hardware failure, I/O bus failure etc.) the board has been removed or subrack power was lost. If a board is set out of service the configured bitstring values are set to invalid due to board failure
A 23BE21 board can be set in service again during runtime:
When this happens the following sequence recovers the indications: normalize the 23BE21 load all parameters for the configured BSIs (done by PDP) read all values Reset qualifier IV to 0 and transmit the new value on the internal communication.

A BSI can change qualifier status at runtime if:
the 23BE21 board fails (qualifier IV = 1)
1KGT 150 450 V000 1
2-35
SCADA Command Direction
3.1
Output Command Types

The RTU560 knows following output command types:
Object Command Output

-
Single Object Command Output (SCO) Double Object Command Output (DCO)
Regulation Step Command Output (RCO) Setpoint Command Output

-
Analog Setpoint Command Output (ASO) Digital Setpoint Command Output (DSO)
Bitstring Output Command (BSO)
3.2
Function Distribution
Within RTU 560 the output boards 23BA20, 23AA20 and if requested the command supervision board 23BA22 are responsible to do the command outputs. They are coordinated and monitored by the PDP. The IOC of the output boards are responsible to switch the output relays or to set the analog output value. They supervise and monitor also the hardware. Which kind of output is configured and wired on which channel is loaded by the PDP to the boards during initialization in a similar form as for the input boards. Regulation step commands (RCO) are handled by the RTU 560 in a direct command sequence only.
1KGT 150 450 V000 1
3-1
3.3
Object Command Output

Object command outputs (SCO or DCO):

3.3.1
can be wired for one, 1.5 and two pole switching allows additional (1 out of n)-check (command supervision) 1.5 pole and two pole switching allows two step commands (Select before operate SBO sequence) allows command termination by a response indication allows persistent output
Single Object Command Output

A single command has only one output relay. It can be configured pulse ON or OFF command or as persistent output. Parameter: Command type (SCO PDP Parameters)
Single object commands can be wired with one relay contact per command (23BA20: 1 pole) or with two relay contacts per command (23BA20: 2 pole). Single Object commands are pulse outputs whereas the pulse duration is specified by the parameter Command pulse length per command. Only the configured direction is used for pulse output. The not configured direction is ignored. One relay is occupied within a 23BA20 output board. Parameter: Command pulse length (SCO PDP Parameters)
K1 23BA20
ON or OFF Interposing Relays
output pulse
Figure 3-1:
Single Command definition: pulse output
3-2
1KGT 150 450 V000 1
Single object commands are configurable as persistent output. In persistent mode a ON command switches the relay persistent on and the OFF command switches the relay to off.
K1 23BA20 Interposing Relays ON-Command OFF-Command
Figure 3-2:
Single Command definition: persistant output
3.3.2
Double Object Command Output

A double command has two independent output relays:
one relay for ON direction one relay for OFF direction
Double object commands can be wired with one relay contact per command (23BA20: 1 pole) or with two relay contacts per command (23BA20: 2 pole). Double Object commands can be pulse outputs whereas the pulse duration is specified by the parameter Command pulse length per command. Only one channel ON or OFF can be active at the same time. The two relays occupies two consecutive bits within a 23BA20 output board. The ON-relay is always on the odd channel and the OFF-relay on the even channel. Parameter: Command pulse length (DCO PDP Parameters)
k1
ON Output pulse
k2 23BA20
OFF Interposing Relays Output pulse
Figure 3-3:
Double Command definition: pulse output
1KGT 150 450 V000 1
3-3
Double object commands are configurable as Persistent output. In persistent mode a ON command switches the relay persistent on and the OFF command switches the relay to off. Parameter: Persistent output (DCO PDP Parameters)
k1
ON
k2 23BA20
OFF Interposing Relays ON-Command OFF-Command
Figure 3-4:
Double Command definition: persistent output
3.3.3
Single and Double Object Commands

The following options are available for single and double object commands.
One Step Command / Select Before Operate Procedure

Commands for objects can be given either direct in one step or for higher security requests in the select before operate procedure. The SBO mode decreases the residual error probability in command direction essentially. If the parameter Select before operate only is selected always a select before operate sequence is necessary. Parameter: Select before operate only (SCO/DCO PDP Parameters)
If RTU 560 receives a SELECT command it checks whether the object is available and if no other object is already reserved. If the check is O.K. it acknowledges the reservation with a positive confirmation. The reservation is valid for approx. 20 seconds. Within that time window either the corresponding EXECUTE Command or a DESELECT command should be received. If not, the RTU 560 clears the reservation. If an EXECUTE command is received within time the object number is compared with the number of the reserved object. If both object numbers are the same, the command is executed. The command is finished, when the RTU 560 transmits the activation termination for that command. The SBO procedure depends on the protocol of the communication line.
3-4
1KGT 150 450 V000 1
Termination of Command output by Response Indication

The pulse duration of an object command can be limited to the runtime of the switching device (e.g. isolator). The run time end is recognized by the new position indication. To prevent that the command is stopped before the new position is settled, a Command release delay time can be specified. The use of a response indication is specified by the parameters of the Response indication for each object command. The response delay time can be specified by the parameter Command release delay time. The default is 200 ms. Parameter: Response indication Parameter: Command release delay time (SCO/DCO PDP Parameters) (SCO/DCO PDP Parameters)
RTU560 Command Switch Gear Response 23BE21 23BA20 UB DPI DCO CS
Pulse length without response Pulse length with response Command output ON 1 0 OFF 1 0
Response message
DPI Message
Command release delay time
Figure 3-5:
Response Indication procedure
The response indication is a SPI or DPI message. Therefore only the end positions ( ON / OFF) can stop the command. It is not required that the reported indication state and the command direction ( ON / OFF ) do match. A new command from NCC is accepted only when the command is switched off, that means after the response delay time and the final termination of the command with ACTTERM to NCC.
1KGT 150 450 V000 1
3-5
Object Command output without supervision

The 23BA20 board is doing the final output by switching the output relay(s). The 23BA20 monitors and checks an output by:
reading back the output bit pattern from the relay coils driver supervision of the 24 V DC which switches the output relays monitoring the output pulse time indicating the command state by LEDs
Figure 3-6 shows the principle wiring for object commands in one pole technique. In two pole technique two relays per command direction are needed and will be switched by the 23BA20 board (e.g. k1 and k9), see Figure 3-7. In that form object commands and regulation step commands can be mixed within a board.
k1 - k16 = output relays

k11 k12 k13 k14 k15 k2 k10 k1 k16 k5 k3 k4 k6 k7 k8 k9
Interposing Relays
UD ON ON ON ON ON ON ON ON OFF OFF OFF OFF OFF OFF OFF OFF Ch 2 Ch 3 Ch 4 Ch 5 Ch 6 Ch 7 Ch 8
R2
R1
Ch 1
SCO, DCO Commands
Figure 3-6:
Process commands without supervision (1 pole)
3-6
1KGT 150 450 V000 1
23BA20
k1 - k16 = output relays

k12 k11 k13 k14 k15 k1 k2 k10 k16 k5 k6 k3 k4 k8 k7 k9
UD Interposing Relays
R2
SCO, DCO Commands
Figure 3-7:
Process command without supervision (2 pole)
The coordination of the output board is done by the PDP. The interaction is shown in Figure 3-8. If a process command is received to switch the selected output channel, the assigned 23BA20 is requested to do the output.
Check if no other output is active etc. Switch selected output relay Start output pulse timer Transmit a positive acknowledge (output active) to the PDP Switch off output relay when the pulse time has elapsed Transmit output deactivated to PDP
The PDP monitors the output commands. If it does not receive the acknowledge information within time it will stop the output by forcing the 23BA20 to stop. The 23BA20 acknowledge output active will response the command with Activation Confirmation to NCC.
1KGT 150 450 V000 1
R1
OFF OFF OFF OFF Ch 1 Ch 2 Ch 3 Ch 4
23BA20
3-7
PDP
Receive, check and prepare output command
23BA20
Comment
RTU 560 receives output command from CS. It checks command on plausibility and no output active If o.k. PDP transmits command to related 23BA20 output board with pulse time parameter
Check output cmnd. switch output relay start timer set flag output active Pulse time elapsed swicth off output relay reset flag output active output pulse time
23BA20 checks received command and activates output channel if o.k. 23BA20 starts timer with received pulse time length and indicates output active to PDP.
23BA20 switch off output channel when pulse time elapsed. 23BA20 indicates output deactivated to PDP PDP receives output deactivated and resets output active. A new command may receive.
Figure 3-8:
Interaction PDP - 23BA20 for a process command output without command supervision
Command output with supervision

To increase the security that only one interposing relay is switched at a time when a command is given, object commands can be expanded with the (1 out of n)-check function. Figure 3-9 and Figure 3-10 show the principle wiring between the 23BA20 board and the additional required 23BA22 command supervision board.
3-8
1KGT 150 450 V000 1
- UD + UD = Process Voltage to switch Interposing Relays GO 23BA22 *) = 1.5 pole is also possible if R1 or R2 is wired only. the other route may be used for other Commands
(1 out of n)-check check circuit P1 / P2
P2-
P2+
P1-
P1 + *) R2 R1 k1 k2 k3 k4 k5
to other 23BA20 Boards with same Relay Type connected
Object Interposing Relays
k6 k7 k8 k9 k10 k11 k12 k13 k14 k15 k16 23BA20
23BA20 Relay Test Period Switch over from "TEST" to "SWITCH" Output Pulse given by "GO" Relay
output pulse 1 out of n test period (with positive result)
Figure 3-9:
Object command output with supervision (1,5 pole)
1KGT 150 450 V000 1
3-9
- UD + UD = Process Voltage to switch Interposing Relays (1 out of n)-check check circuit P1 / P2 GO *) = only 2 pole Object Commands possible if wired for (1 out of n)-check 23BA22
P2-
P2+
P1-
P1 + *) R2 R1 k1 k2 k3 k4 k5 k6 k7 k8 k9 k10 k11 k12 k13 k14 k15 k16 23BA20
to other 23BA20 Boards with same Relay Type connected Object Interposing Relays
23BA20 Relay Test Period Switch over from "TEST" to "SWITCH" Output Pulse given by "GO" Relay
output pulse 1 out of n test period (with positive result)
Figure 3-10:
Object command output with supervision (2 pole)
3-10
1KGT 150 450 V000 1
PDP
Receive, check and prepare output command
23BA20
23BA22
Comment
Command is checked on plausibility and no other output active. Related 23BA20 output channel is switched on by transmitting command to 23BA20 board with a longer pulse length than defined for the Command
Check output cmnd. switch output relay set flag output active start test circuit "n" Run 1 out of n check for circuit "n" switch over to output position and start output by "GO" relay start output timer set flag output command running Pulse time elapsed switch off "GO" relay reset flag output running prepare stop for 23BA20 relay switch off output relay reset timer reset flag output active
PDP indicates Output Active and starts 23BA22 with pulse time parameter. 23BA22 runs (1 out of n)-check If Positive: output and timer started Output Pulse Time
23BA22 switch off GO relay if pulse time elapsed It indicates Output Deactivatedto UB PDP transmits Output Stop to 23BA20 board 23BA20 will switch off related Output Channel 23BA20 indicates Output Deactivatedto UB PDP receives Output Deactivatedand resets output active. A new command may receive
Figure 3-11:
Interaction PDP - 23BA20 - 23BA22 for a process command with command supervision
The coordination between the two output boards is done by the PDP. The interaction between the three boards is shown in Figure 3-11.When a process command is received the 23BA20 output relay is switched first with a pulse time which is longer than the configured output pulse duration for that channel. After the 23BA20 has acknowledged that the output relay is switched on, the 23BA22 is started to check the output circuit and if positive to do the final output with the configured time for that channel. The 23BA22 allows to check two different output circuits with different nominal resistance's. But only one channel can be active at the same time (P1 or P2). If the
1KGT 150 450 V000 1
3-11
23BA22 receives a request to test and switch a command on P1 or P2 the following sequence is started:
Check that no other output is active etc. Select P1 or P2 for checking Start to measure the resistance in the switched output channel (interposing relay) Compare the measured resistance against the parameterized upper and lower limits Abort all activities and transmit a negative acknowledge if the resistance is out of limits Switch the auxiliary relays from TEST to SWITCH position if the resistance check is O.K. Start the output pulse by switching the GO relays which feed the process voltage to the selected interposing relay Start output pulse timer Transmit a positive acknowledge (command running) to PDP Switch off GO relay when the pulse time elapsed Switch back to TEST position Transmit command stopped to PDP
The PDP will then stop the 23BA20 output by a stop command. The PDP part of the CPU monitors the output commands. If it does not receive the acknowledge information within time it will stop the output by forcing the 23BA22 to reset and the 23BA20 to stop output. The assignment between 23BA22 and 23BA20 and the upper and lower resistance limits has to be parameterized for each channel on the command supervision board 23BA22. Two command supervision channels CSC (P1 / P2) can be defined on each 23BA22 board. On the 23BA20 board can be selected which command supervision channel monitors the board. For 1,5 pole 23BA20 two channel can be selected (relays 1-8 and relays 9-16) . The command supervision is valid for all SCO and DCO commands on this board. It must be regarded that channels connected to the same route (R1 / R2) must have the same supervision channel CSCn. Parameter: Check circuit number Low limit resistance High limit resistance (CSC General Parameters) (CSC General Parameters) (CSC General Parameters)
3-12
1KGT 150 450 V000 1
23BA22 LOCAL key

The 23BA22 board has a push-button on the front panel which allows to inhibit any active output. This button is marked with LOC and a LED indicates if LOCAL is active or not. To switch from remote to local and vice versa the push-button must be pressed two times within 5 seconds. The LED LOC flashes -after the push-button is pressed once- for five seconds. If LOCAL is active and a message is sent, indicating 23BA22 is set to local. Each object command received while local mode active is negative acknowledged. Any command which addresses one channel wired to a 23BA22 output channel (P1/P2) is disabled. If the LOC push button is pressed again the 23BA22 switch back to remote mode and will accept and handle each command in the normal way. In addition a message is sent with the corresponding bit reset.
1KGT 150 450 V000 1
3-13
3.4
Regulation Step Command Output

Regulation step command outputs (RCO)
can be wired for one and two pole switching 23BA20 cannot be wired with command supervision allows single step command only cannot be terminated by a response indication
The object command pulse length is described by the parameter PULSE LENGTH. The pulse duration for HIGHER and LOWER is the same. Parameter: Command pulse length (RCO PDP Parameters)
Retrigger of regulations commands

The output pulse duration of a regulation command can be expanded if the same command is received within the output pulse time and can be send to the output board before the time elapsed. 23BA20 starts the timer again. An output pulse can also be shortened by a new command with DEACTIVATION flag. If a DEACTIVATION command is received the running regulation command is stopped immediately.
Start RCO ACT
Retrigger Retrigger RCO RCO ACT ACT
Retrigger Stop Pulse duration RCO RCO without stop DEACT ACT
Command output relay
Nominal pulse duration
Figure 3-12:
Retrigger / stop of a regulation command
3-14
1KGT 150 450 V000 1
3.5
Setpoint Command
A set point command is specified by an analog or digital set point value output. The output can be done with or without strobe. For a strobe output the value is valid for the receiving unit during the additional strobe pulse output. The strobe pulse has a fixed pulse length of 500 milliseconds. The set point command types are:
analog output value (ASO) Analog output channel on a 23AA20 board (current or voltage output) digital output value (DSO) Digital output on 23BA20 board
3.5.1
Analog Setpoint Command Output

The analog set point command output (ASO) can be done in two ways, either with strobe or without strobe. The strobe output allows to trigger the concerned unit when a new value is received. When this is not requested the set point command can be done without strobe.
Bipolar, Unipolar and Live Zero conversion

The analog output value is converted to an analog output signal by the 23AA20 board. The Output signal type allows to specify unipolar output signals. That means a negative ASO value is set to zero. Output signals with live zero presentation (standard = 4..20 mA) are transformed by the PDP. The conversion is done in the form that:
0% of the normalised ASO value becomes 20 % of the output signal range (standard: 4 mA) 100 % of the normalized ASO value becomes 100 % of the input signal range (standard: 20 mA).
100 %
0% 4 mA (0%) 20 mA (100%) Output Value
Figure 3-13:
Live Zero Output Conversion by a 23AA20 board
1KGT 150 450 V000 1
3-15
The configuration parameter Output signal type specifies if the output is a bipolar, a unipolar or a live zero signal. The configuration parameter Output signal range specifies the hardware setting of the 23AA20 board. Parameter: Output signal range Output signal type (ASO PDP Parameters) (ASO PDP Parameters)
Scaling
The PDP converts the value of a normalized ASO. The configuration parameter Conversion factor specifies the percentage of the maximum output signal that is defined as 100 % of the normalized value. Parameter: Conversion factor (ASO PDP Parameter)
Normalized ASO value

[digits] + 100 %
e.g. conv. factor = 75 %
-20 -100
-15 -75
-10 -50
-5 -25
5 25
10 50
15 75
20 [e.g. mA] 100 [%]
Output signal
- 100 %
Figure 3-14:
Analog Value Conversion ASO
3-16
1KGT 150 450 V000 1
Analog Setpoint command with strobe

For analog setpoints with strobe, the corresponding Strobe output channel (SOC) should be configured to any output channel of a 23BA20 board. The strobe Pulse length is configurable. The default value is 500 milliseconds. The ASO should be configured to a analog output board 23AA20. Parameter: Pulse length Strobe (SOC) (SOC PDP Parameters) (ASO PDP Parameters)
The PDP coordinates the output of the analog output value and the strobe pulse. There is a delay of approx. 50 ms between the output of the analog value and the strobe. This delay allows the value to become stable. The analog output stays stable until a new ASO is received.
Analog value Strobe unit 23AA20 Analog value Strobe unit
k1 kn 23BA20 km Analog output value
Strobe output (k n) 500 ms
k16
50 ms
Figure 3-15::
Set Point Command for Analog Output
1KGT 150 450 V000 1
3-17
3.5.2
Digital Setpoint Command Output

A digital setpoint output (DSO) is an output of a normalised value on a 23BA20. The following types are possible:
Digital Setpoint Output 8 bit (DSO8) Digital Setpoint Output 16 bit (DSO16)
The RTU knows conversions for: Binary data (BIN) Binary coded decimals (BCD) Gray code (GRAY)
The maximum length of a digital measured value is the word of 16 bit (= one 23BA20 board). Double word values are not supported.
Digital Setpoint value presentation

Each type is converted by the PDP.
3-18
1KGT 150 450 V000 1
16 15 14 13 12 11 10 9 (A) S
23BA20 Output Channel Word = Signed Integer DSO
value two's complement
Conversion by PDP
(a) (b) (c) (d) (e) (f) (g) (h) (i) (j) (k) (l) S S S S 0..9 0..7 0..9 0..9 S 0..9 0..9 0..9 0..7 0..9 0..9 0..9 0..9 S
16 bit unsigned binary data 15 bit + sign binary data 8 bit unsigned binary data 7 bit + sign binary data 4 Decade BCD unsigned 4 Decade BCD signed 2 Decade BCD unsigned 2 Decade BCD signed 16 bit gray code 15 bit signed gray code
8 bit gray code 7 bit signed gray code
= Sign bit / Sign position
Figure 3-16:
Digital Setpoint Value presentation
Scaling and format conversion

A digital setpoint output is converted from a normalized value (+/- 100%) to a bit pattern output on 23BA20 by the PDP. The PDP parameter DSO value presentation and Output signal type specifies which DSO type is connected to the 23BA20 board. The PDP receives the bit pattern of the DMV. The PDP parameter Maximum value specifies the binary value output for 100 % of the DSO value. Parameter: DSO Value presentation Input signal type Maximum value (DSO PDP Parameters) (DSO PDP Parameters) (DSO PDP Parameters)
1KGT 150 450 V000 1
3-19
Digital Setpoint command with strobe

For digital setpoints with strobe, the corresponding Strobe output channel (SOC) should be configured to any output channel of a 23BA20 board. The strobe Pulse length is configurable. The default value is 500 milliseconds. The DSO should be configured to a binary output board 23BA20. SOC and DSO8 can be located on the same 23BA20. Parameter: Pulse length Strobe (SOC) (SOC PDP Parameters) (ASO PDP Parameters)
The PDP coordinates the output of the digital output value and the strobe pulse. There is a delay of approx. 50 ms between the output of the digital value and the strobe. This delay allows the value to become stable. The digital output stays stable until a new DSO is received.
Digital value 23BA20 Strobe unit
Digital value 23BA20 Strobe unit
k1 kn 23BA20 km Digital output value
Strobe output (k n) 500 ms
k16
50 ms
Figure 3-17:
Set Point Command for Digital Output
3-20
1KGT 150 450 V000 1
3.6
Bitstring Output
A bitstring output (BSO) is a persistant output on a 23BA20. The following types are possible:
Bitstring Output 1 bit (BSO1) Bitstring Output 2 bit (BSO2) Bitstring Output 8 bit (BSO8) Bitstring Output 16 bit (BSO16)
Bitstring output values are transparent mapped 23BA20 output channels. The output value is switched on the output board and stays stable until a new value is received from NCC for this output channel. The maximum length of a digital measured value is the word of 16 bit (= one 23BA20 board). Double word values are not supported.
1KGT 150 450 V000 1
3-21
3.7
Error Handling
Output Board Failure
An output board can be set out of service:
If an output board is set out of service the configured output channels are set faulty due to board failure in the data base. The RTU232 indicates that to the NCCC with diagnostic message. An output board can be set in service again during runtime:
If this happens the following sequence recovers the output channels: normalize the output board load all parameters for configured channels by the PDP clear faulty state in data base and update NCC
For set point commands the output channel and the corresponding strobe channel (when selected) must be available before the ASO/DSO is set O.K. again. For object commands with command supervision the 23BA20 board and the 23BA22 board must be available.
3-22
1KGT 150 450 V000 1
Host Communication Interface
This chapter describes the general part of Host Communication Interface (HCI) of the RTU560. The communication with multiple NCCs with different communication protocols is one of the basic concepts for RTU560.
Station Control
Network Control Center
IEC 60870-5-104 WAN

IEC 60870-5-104 IEC 60870-5-1010 DNP 3.0 IEC 60870-5-101 DNP 3.0 IEC 60870-5-104
RTU560
HCI
HCI
IC
HCI
SCI
IEC 60870-5-101 DNP 3.0
PDP SCI
SPABus Modbus
SCI
IEC 60870-5-103 IEC 60870-5-101
IED Sub-RTU Process

Marshalling Rack Protection and Control Units
IED
IED IED
Figure 4-1:
RTU560 Network
The RTU560 allows the communication up to eight different NCCs by using the serial interfaces of 560SLI01 CMU or serial and Ethernet interfaces from the 560ETH01 CMU. The configuration of the interfaces as host and communication lines with their protocols is completely done in RTUtil NT. There are no hardware switches to configure the interfaces.
1KGT 150 450 V000 1
4-1
Dialog RTU560 NCC

The assignment of UART host protocols to the serial interfaces is totally free. There are no dependencies between the different protocols on one CMU. The only restriction is the number of communication protocols offered in one firmware package. Protocols that work not UART based are restricted to the interfaces CPA and CPB on the CMU 560SLI01 and 560ETH01. Ethernet and TCP/IP based protocols could only be used with the Ethernet interface on the 560ETH01 CMU.
Monitoring Direction
All active NCCs get any message that is created in the RTU560. Also any message that comes from a substation and could be translated between the protocols is sent to the activated NCCs. To avoid transmission of certain data points on certain HCIs, a filter can be set in the configuration for these data points.
Command Direction
Commands to the RTU560 are accepted equal from all central systems. There is no restriction to the number of different commands that could be handled at one time in the RTU560. The acknowledge of a command will be sent to every NCC.
General Interrogation
The HCI contains a database with the actual state of the process data objects and the state of the objects from sub-stations. A general interrogation command is answered directly from HCI with the entries of this database.
Failure of a Host-Line
The RTU560 can manage up to eight lines to a NCC. To indicate if a communication between RTU560 and one NCC fails there is a system event message which indicates the number of the host interface. SEV(101 ... 108): Host no. x online
4-2
1KGT 150 450 V000 1
4.1
Overview HCI Software Structure

The internal software of the Host Communication Interface (HCI) is hierarchical structured into the three parts
Interface to the Internal Communication (IC) Application layer in monitoring and command direction Link layer
NCC
Host Communication Interfaces (HCI)
Link Layer
Application Layer Monitoring Direction
Application Layer Command Direction
Interface to Internal Communication
Internal Communication
Figure 4-2:
Interface IC Application Layer Link Layer
1KGT 150 450 V000 1
4-3
4.2
Queue- and Buffer Handling

The events which the HCI receive from the IC are stored into five queues to handle the different priorities and overflow mechanism. The interface to the IC is responsible for filter and distribution of the events to the different queues. The Link Layer handles the transmission of the events from the different queues to the NCC. The picture below shows the five internal queues between the interface to the internal communication and the application layer in monitoring direction. These queues are used independent from the communication protocol in every RTU560 HCI.
NCC
Host Communication Interfaces (HCI)
HCI- Database
Link Layer Application Layer Monitoring Direction
Prio 1 queue
Prio 2 queue
AMI spont . transm queue

AMI spontaneous transmission
AMI cycl. transm queue

AMI cyclic transmission
ITI queue
Information objects priority 1
Information objects priority 2
Integrated totals
Figure 4-3:
RTU HCI queues
Depending on the priority of the queues the application layer monitoring task reads out the queues and send the telegrams to the link layer.
Interface to IC gets a telegram Interface to IC distributes the telegram to one of the queues Dependent to the priority the application layer in monitoring direction reads out the queues Telegrams in the AMI cyclic transmission queue are stored in the data base. Telegrams in the other queues are stored in the host data base and send by the link layer.
4-4
1KGT 150 450 V000 1
The link layer sends the telegram
An exception to this handling is made for the periodic transmission of analog measured values. For these values there is a separated queue named AMI cyclic transmission queue. The application layer in monitoring direction reads the telegrams from this queue with highest priority and writes them directly to the HCI-Database. Dependent on the Background cycle time parameter that could be set for every AMI, the application layer monitoring direction task reads out the database and writes the telegram to the link layer. Parameter: Background cycle (AMI Protocol Address and Parameter)
1KGT 150 450 V000 1
4-5
The Queues
Prio 1 queue
The Prio1 queue contains the data types SPI, DPI, EPI, BSI, DMI, STI of priority 1 and also System Events Queue size: 100 ... 3000 entries, default 500 Parameter: Buffer size for priority 1 data points (Interface Parameter)
Prio 2 queue
The Prio2 queue contains the data types SPI, DPI, EPI, BSI, DMI, STI of priority 2. Queue size: 100 ... 3000 entries, default 500 Parameter: Buffer size for priority 2 data points (Interface Parameter)
AMI spontaneous transmission queue
This queue includes analogue measured values, which are transmitted spontaneous. Queue size: 100 ... 3000 entries, default 500 Parameter: Buffer size for spontaneous transmitted analog measured values (Interface Parameter)
AMI cyclic transmission queue
This queue includes analogue measured values which are only transmitted in a background cycle. Queue size: 300 entries (fix size, not configurable) Priority: highest
ITI queue
The ITI queue includes the end of period and intermediate reading integrated totals. For the ITI queue there is no fix priority. The priority can be configured between 1 and 3. Also there is a timeout parameter to adjust the offline timeout for the ITI queue (Queue storage timeout).If this timer is expired, the queue entries are read and written into the host database. The data is marked in the database for later transmission. Queue size: 10 ... 10000 entries, default 1000 Parameter: Parameter: Parameter: Buffer size for integrated totals (ITI) (Interface Parameter) Priority of ITI queue (Interface Parameter) Queue storage timeout (Interface Parameter
4-6
1KGT 150 450 V000 1
4.2.1
Priority Read Queues

The read access mechanisms for the queues depends on the priority of the queues. The AMI cyclic transmission queue is read out with the highest priority.The other queues got priorities from 1 to 3
Priority 1: Prio 1 queue Priority 2: Prio 1 queue Priority 3: AMI spontaneous transmission queue
The priority for the ITI queue is configurable (1 ... 3).
4.2.2
Queue Transitions and Overflow

This topic gives information about the various states and transition conditions of the queue control of the HCI in monitoring direction. If the host interface starts, all queue entries are discarded until the internal system event DB_UPDATED is received. Then the host database is updated. From this time on the queue control works. The control mechanism are described in detail below.
START
QUEUE DISCARDED OFFLINE NCC online
System Event DB_UPDATED QUEUE OK read queue and send messages ONLINE 4 NCC offline QUEUE OK NCC online 1 OFFLINE offline Timer expired
no more marked messages in database
NCC online QUEUE OK or OVERFLOW all queue entries will be discarded, read queue and write marked messages to database ONLINE 3
Queue overflow
QUEUE OK transmit marked messages from database 6 ONLINE Queue ok Queue overflow
NCC offline Queue overflow
QUEUE OVERFLOW read queue and write marked messages to database 5 ONLINE
NCC offline NCC online
QUEUE OVERFLOW read queue and write marked messages to database 2 ONLINE
offline Timer expired
Figure 4-4:
Queue handling transition diagram
1KGT 150 450 V000 1
4-7
1. The host interface is offline, the queues are okay and buffer all information. 2. The host interface is offline and one or more queues are overflown. The overflown queue entries are read and written into the database. The data is marked in the database for later transmission. 3. The host is offline and the offline timer is expired, all queue entries will be discarded. The queue entries are read and written into the database. The data is marked in the database for later transmission. 4. The host interface is online and the queues are okay, the queues are emptied and messages are sent. 5. The host interface is online and one or more queues are overflown. The overflown queue entries are read and written into the database. The data is marked in the database for later transmission. 6. The host interface is online and the queues are okay, marked elements of the database are read and messages are sent.
ITI Queue Overflow Handling

Intermediate reading (IR) messages are not stored, when the queue is full. Only end of period (EPR) messages are then stored in the queue, by overwriting the IR messages in the queue. In the case that all stored IR messages are overwritten, the oldest EPR message will be overwritten. So that the queue contains from the actual time backwards the EPR messages. Also these two events will be indicated by system event messages (SEV(171): IR integrated totals lost due to queue overflow, SEV(172): EPR integrated totals lost due to queue overflow)
All Other Queues Overflow Handling

To avoid an overflow in the queues, there is a queue supervision for all queues except the ITI queue. If any of these queues has reached the high level (80% filled) the queue is read with the highest priority, as long as the queue has reached its low level (40% filled) again. The total number of readings for each queue remains. If not guaranteed, that the in- and outflow of telegrams can be handled quickly enough, all telegrams from the input queues are read out and will be written to the host database. No telegrams are sent to the Link Layer. If the Link Layer works again the telegrams are build out of the database but without timestamps. A system event message which indicates the queue overflow is generated and filled into the Prio 1 queue. SEV(152): Prio 1 queue overflow SEV(152): Prio 2 queue overflow
4-8
1KGT 150 450 V000 1
Sub-Device Communication Interface
This chapter describes the general part of Sub-Device Communication Interface (SCI) of the RTU560. The sub-device communication interface is used for communication between RTU560 and subordinated devices. Subordinated devices are RTU560s or in general- other intelligent electronic devices (IED). The communication with multiple IEDs with different communication protocols is one of the basic concepts of RTU560. A network configuration with subordinated devices is shown in Figure 5-1.
Station Control
IEC 60870-5-104 WAN

IEC 60870-5-104 IEC 60870-5-1010 DNP 3.0 IEC 60870-5-101 DNP 3.0 IEC 60870-5-104
RTU560
HCI
HCI IC
HCI
SCI PDP SCI

IEC 60870-5-101 DNP 3.0 SPABus Modbus
SCI
IEC 60870-5-103 IEC 60870-5-101
IED Sub-RTU Process

IED
IED IED
Figure 5-1:
RTU560 Network
The SCI supports varios communication protocols. The protocol specific configuration parameters are decripted in additional documents. The configuration of the SCI and communication lines with their protocols is completely done in RTUtil NT. There are no hardware switches to configure the interfaces. The SCI can manage up to 32 devices per line. In a RTU560 it is possible to have up to 60 sub-lines.
1KGT 150 450 V000 1
5-1
The assignment of UART sub protocols to the serial interfaces is totally free. There are no dependencies between the different protocols on one CMU. The only restriction is the number of communication protocols offered in one firmware package. Not all existing protocols can be combined on one CMU board. Only certain combinations of protocols are possible. Protocols that work not UART based are restricted to the interfaces CPA and CPB on the CMU 560SLI01 and 560ETH01. Ethernet and TCP/IP based protocols could only be used with the Ethernet interface on the 560ETH01 CMU. The structure of the sub-device interface is independent of the protocol and shown in Figure 5-2.
Sub-Device Communication Interface (SCI)
Application Layer Monitoring Direction
Link Layer
Sub-Device
Figure 5-2:
Internal structure of the SCI
5-2
1KGT 150 450 V000 1
5.1
Message Flow in Monitoring Direction

The messages from a subordinated device are checked by the link layer on valid format of the configured protocol. If the message is valid it is given to the application layer in monitoring direction. The application layer for the monitoring direction decodes the user data. All values, flags and other informations are mapped into the RTU560 internal format The mapping is shown in the protocol specific description. If the user data is valid and configured part of this SCI it is sent to the internal communication. The queueing between link layer and application layer is secured no messages can be lost. The sizes of these queues are not configurable by RTUtil NT.
5.2
Message Flow in Command Direction

The messages on the internal communication are all detected and checked by the application layer for the control direction if they are configured part of this SCI. The application layer for the control direction encodes the user data. All values, flags and other informations are mapped into the protocol specific format. This mapping is shown in the protocol specific description. The user data is given to the link layer where the link informations are added and sent to the subordinated line. The queuing between application layer and link layer is secured so no messages can be lost. The sizes of these queues are not configurable by RTUtil NT. For some specific protocols it is necessary that the application layer for the control direction of the SCI simulates messages which are not sent by the subordinated line protocol and sends them to the internal communication to have consistency to the internal sequences of the RTU560.
1KGT 150 450 V000 1
5-3
5.3
General Interrogation
The general interrogation command is done by the sub device communication interface automatically in following situations:
System start up Redundancy switchover (also when the concerning CMU board is not part of the redundant system; to actualize the process data from subordinated devices) Sub device line status changed from offline to online
If the general interrogation command is not supported by the configured protocol the SCI simulates a general interrogation in e.g. with reading of all values or other procedures to get the actual values of the subordinated devices.
5.4
Time Synchronization
The time synchronization of a subordinated device is autonomously managed by the SCI and only implemented if it is supported by the configured protocol. The time synchronization must be configured once per sub-line. It is not possible to configure different time synchronization modes on one line. Parameter: Time interval of clock synchronization commands (Line Parameters - IEC 60870-5-101) If the RTU560 is synchronized the sub-device communication interface reads the RTU560 internal time and sends it in a configured period of time to all subordinated devices if they are in state online. If the RTU560 has no valid time information the time synchronization command is not sent to any subordinated device.
5-4
1KGT 150 450 V000 1
5.5
System events
The Subdevice communication interface (SCI) contains the system event block for every device that is connected to the line. If the sub-device is a RTU560, the complete system event block of 255 messages is supported. If the sub-device is an other IED, only three system events of the system event block are supported:
System event
RTU is active RTU inoperable RTU out of service
Address offset 24 48 49
The system events RTU is active (24) and RTU out of service (49) are always send automatically in the start up procedure of the SCI to have defined values for the RTU560 database. The values are:
RTU is active = 1 RTU out of service = 0
This means that subordinated device is active and in service. After the startup of the SCI these system events can be handled by the subordinated device. To indicate to a host system if a subordinated device is available the SCI manages the system event RTU inoperable for all connected subordinated devices on this line. The link layer detects if the device is available and sends this status information to the application layer in monitoring direction. The application layer sends the system event to the internal communication with the address of the subordinated device. The meaning of this system event is:
-
RTU inoperable = 0 RTU inoperable = 1
subordinated device is online subordinated device is offline
1KGT 150 450 V000 1
5-5
Interfaces and Network
6.1
Network Configuration
Station Control
IEC 60870-5-104 WAN

IEC 60870-5-1 04 IEC 60870-5-1 010 DN P 3.0 IEC 60870-5-1 01 DN P 3.0 IEC 60870- 5-1 04
RTU560
56 0 S LI0 1
56 0 S LI0 1
56 0 ETH0 1
56 0 SLI0 1
A B 1 2
A B 1 2
A B E
A B 1 2
IEC 60870- 5-1 01 DN P 3.0
SPABus Mod bus IEC 60870- 5-1 03 IEC 60870-5-1 01
IED Sub-RTU Process

IED
IED IED
Figure 6-1:
RTU Network with Interfaces
The complete station network with router RTUs, sub-RTUs and IEDs will be configured in RTUtil NT. The configuration of the station network topology will be done in the NetworkTree of RTUtil NT. The start point in this tree is the router RTU in the station network. For a detailed description how to build up the NetworkTree see also the RTUtil NT Users Guide 1KGT150 451 V0001.
1KGT 150 450 V000 1
6-1
6.2
Interface Configuration
6.2.1
The Interfaces
CP1 ,CP2
Only 560SLI01
Possible Interfaces types are RS232 and RS422. The communication runs at baud rates from 50 to 38400 Baud
Parameter: Interface Type (Interface Parameter) Parameter: COM Speed (Interface Parameter)
CPA ,CPB
560ETH01 & 560SLI01
Possible Interfaces types are RS232 and RS485. The communication runs at baud rates from 50 to 38400 Baud
Parameter: Interface Type (Interface Parameter) Parameter: COM Speed (Interface Parameter)
ETH
Only 560ETH01
The TCP/IP address must be configured
Parameter: IP Address (Interface Parameter) Parameter: Subnet mask (Interface Parameter) Parameter: Default Gateway IP (Interface Parameter)
6-2
1KGT 150 450 V000 1
MMI
560SLI01 & 560ETH01 The interface is only used for PPP (Point to Point Protocol). The baud rate is 38400 and the IP Address is 10.0.10.50. The interface cannot be configured. But the connection partner (PC example) has to be configured (look Document RTU 560 Web Server Users Guide chapter Dial-Up, Network and RAS).
1KGT 150 450 V000 1
6-3
6.3
Duplex communication
WT Duplex 4 Wire
NCC WT WT
Tx Rx Tx Rx
Figure 6-2:
Duplex communication
6.3.1
WT link full duplex (23WT21-23, no handshake)

Used with 4-wire or 2 channels in WT-Modems 23WT22 and 4-wire with 23WT21. It is the same as No HW-Handshake: a Full Duplex transmission with TxD and RxD. DTR and RTS are set to continuous On. This switches the Carrier from the WTs to on state. DSR, DCD and CTS are ignored. No transmit delay time is available. Parameter: Modem Control (Interface Parameter)
6-4
1KGT 150 450 V000 1
RTU560
DTR DSR
Not used used
DCD
Not used
RTS CTS
Not used
TxD RxD
Figure 6-3:
WT link full duplex transmit control
6.3.2
Direct Link (TxD/RxD only)

Used lines are TxD / RxD in separate Duplex Transmission No control signals used, CTS and DCD simulated to active. Works in RS232 and RS422 (see Figure 6-3). RTU and communication partner are directly connected together. Communication partner may be a PC, an other RTU, a PC-Modem or a CS. Parameter: Modem Control (Interface Parameter) Parameter: Transmit delay time (Interface Parameter)
6.3.3
Direct / Modem link (DTR, RTS/CTS, DCD handshake)

Used lines are TxD / RxD in separate Duplex Transmission Control signals DTR / DSR, RTS / CTS and DCD are used for Flow Control . Works in RS232 only. No transmit delay time is available. RTU and communication partner are directly connected together. Communication partner may be a PC, an other RTU, a PC-Modem (dial up) or a CS. Parameter: Modem Control (Interface Parameter)
1KGT 150 450 V000 1
6-5
DTR DSR
Not used
DCD
No effect for transmit
RTS CTS TxD RxD

No effect for transmit
Figure 6-4:
Direct / Modem link
NCC
NCC
NCC
Hayes Modem
Hayes Modem
Hayes Modem
RTU560
Figure 6-5:
RTU560
RTU560
Dial up configuration
6-6
1KGT 150 450 V000 1
6.4
Half Duplex communication

WT Half Duplex 4 Wire WT Half Duplex 2 Wire
NCC WT
RTU560
Tx Rx Tx
NCC WT
Tx
WT
Rx
WT
Rx
RTU560
Tx Rx
Tx
Tx
WT
Rx
WT
Rx
Figure 6-6:
Half Duplex communication
6.4.1
WT link half duplex (23WT22, with CTS handshake)

Used in the WT-Modems 23WT22 with 2-wire. The Control signals control the Carrier on the transmission line. No transmit delay time is available! Parameter: Modem Control (Interface Parameter)
1KGT 150 450 V000 1
RTU560
RTU560
6-7
WT Mode, Half duplex,with CTS DTR DSR

Not used for 23WT21 and 23WT22
DCD
Maybeactive in Half Duplex
RTS CTS
Switch carrier on
Carrier is on
TxD RxD
End of last stop bit
Figure 6-7:
WT-Mode, Halfduplex, with CTS transmit control
6.4.2
WT link half duplex (23WT21-23, with transmit delay time)

Used with WT-Modems 23WT21 with 2-wire. The Control signals control the Carrier on the transmission line. Parameter: Modem Control (Interface Parameter) Parameter: Transmit delay time (Interface Parameter)
6-8
1KGT 150 450 V000 1
W-Mode, Half duplex, with CSTD Carrier Setup Time Delay DTR DSR
Not usedfor 23WT21and 23WT22
DCD
Maybeactive in Half Duplex
RTS CTS intCTS
Switch carrier on
CTS is not connectedor useable
CSTD
CTS is simulated
TxD RxD
Figure 6-8:
WT-Mode, Halfduplex, no handshake transmit control
6.4.3
Network Configuration Rules and Restrictions

The configuration of a sub-RTU network is limited by some definitions, physical restrictions, address ranges etc.:
In 2 racks, with 8 560SLI01 CMUs in each rack, there are 64 physical serial interfaces. Max. 8 host-lines Max. 60 sub-lines Max. 32 sub-stations (RTUs and IEDs) each line Each router RTU can be a process RTU
The practical restrictions can be different dependent on the communication speed of the station network, the used communication protocols and the amount of process data points connected to a RTU560.
1KGT 150 450 V000 1
6-9
6.4.4
Interface Configuration Rules and Restrictions

The assignment of UART host protocols to the serial interfaces is totally free. There are no dependencies between the different protocols on one CMU. The only restriction is the number of communication protocols offered in one firmware package. Protocols that work not UART based are restricted to the interfaces CPA and CPB on the CMU 560SLI01 and 560ETH01. The SLC works only in one mode (IO Bus, Bit protocols or UART protocols). It is impossible to mix the mode type. For example it is not possible that CPA works in IO Bus mode and CPB in Bit protocol. Ethernet and TCP/IP based protocols can only be used with the Ethernet interface on the 560ETH01 CMU.
6-10
1KGT 150 450 V000 1
Startup, Configuration and Time Management
7.1
Startup Procedures
A RTU560 System may contain several Communication Units (CMUs, e.g. 560SLI01 or 560ETH01). Activities, e.g. communication protocols, I/O Bus Interfaces or PLC functions, may be configured freely to be running on different CMUs. A central RTU560 System Control coordinates the startup of Activities on the CMUs and manages removal and integration of CMUs via RTU560 system bus. System Control is running on the CMU configured with administration mode MASTER, that is allowed only once in the RTU, all other CMUs must be SLAVEs. Parameter: Administration mode (560SLI01 or 560ETH01 Parameters)
RTU560 supports the following startup procedures:
RTU560 CMU Start Power ON or reset of a CMU RTU560 System Start Power ON or reset of the RTU560 RTU560 CMU Integration Plug in of one CMU in a running RTU560 (only in multiple CMU systems) Protocol restart Communication protocols often provide methods to restart the RTU. Since the RTU560 may support various protocols, the restart methods are described in the specific protocol description.
1KGT 150 450 V000 1
7-1
Status and Diagnostic Information
7.1.1
RTU560 CMU Start

When a CMU is started after Power ON or reset command by NCC or RTU560 WebServer, it does the following startup sequence:
Initialization and hardware test (RAM, FLASH, Watchdog etc.), firmware load from FLASH memory Send System Message [14.1] " CMU in rack x, slot y: STARTUP "
Check if other CMUs are present in the RTU for 10 s. If yes, the CMU compares its own firmware and configuration with all present CMUs in the following way:
-
The firmware release version no. (first digit, e.g.: 2 for a Version 2.5) must be the same on every CMU. If not, the CMU stops further initialization and sends System Message [12.1] " Firmware-Error on CMU in rack x, slot y version Vn.xx ". It waits for load of a new firmware and a reset. The .gcd configuration (General Configuration Data) must be present and equal on every CMU. If not, the CMU stops further initialization, sends System Message [10.4] " Config-Error on CMU in rack x, slot y: GCD File date " and waits for load of a new ".gcd" configuration and a reset. The .iod configuration (Input Output Data), if present, must be equal on every CMU. If not, or if it is missing on any other CMU, the CMU does its further initialization without ".iod" configuration and sends System Message [10.2] " Config-Error on CMU in rack x, slot y: IOD File date " or [10.3] " Config-Error on CMU in rack x, slot y: IOD File size ". The password configuration for the RTU560 Web-Server must be present and equal on every CMU. If not, the CMU sends System Message [10.5] " Config-Error on CMU in rack x, slot y: Password " does its further initialization with default password configuration.
Check if the configuration is formally valid (CMU type, rack and slot address are correct). If not, the CMU sends System Message [10.1] " Config-Error on CMU in rack x, slot y: WRONG RACK OR SLOT ADDRESS ", stops further initialization and waits for load of a new .gcd configuration and/or replacement Check if the own CMU is configured with Administration mode MASTER. Launch System Control and Time Master management on the MASTER CMU. Else launch Time Slave management Wait for registration request by RTU560 System Control for 10 sec. If System Control is not present, System Message [11.1] " Master for CMU in rack x, slot y: Error " is sent Start Activities as called by System Control (s. 7.1.2). If an Activity cannot be started, System Message [13] Activity Error for <Activity Type> in rack x, slot y: <Activity-Error Type> is sent by the CMU (details s. table System Messages in Chapter 8) When All Activities are started, and System Control has started successfully, System Message [14.2] " CMU in rack x, slot y: STARTUP READY " is sent by the CMU
7-2
1KGT 150 450 V000 1
7.1.2
RTU560 System Start

The RTU560 system start (Power ON or reset of the RTU560) is managed by System Control which is running on the configured MASTER CMU. The system start sequence is:
After CMU start (s. 7.1.1), System Control requests the configured boards and waits 5 s for their registration. RTU560 System Control starts the configured Activities on the registered CMUs in the following order:
-
PLC and Local Function tasks Host Communication Interfaces (Slave Protocols) Sub-Device Communication Interfaces (Master Protocols) I/O Bus Interfaces

7.1.3
Sub-Device Interfaces and I/O bus request data from Sub-Devices and I/O Boards. System Control waits until they report the database update. Configured host-interface(s) start(s) communication to the NCC. System supervision is started to enable CMU removal and integration.
CMU Integration
In a multiple-CMU system, a single CMU may be integrated into a running RTU560. During the integration process, already running Activities in the RTU continue their operation. To be able to integrate a CMU the following conditions must be fulfilled:
The CMU must be configured in the RTU560 If a SLAVE CMU is integrated, the MASTER CMU must be present and must have successfully finished the System Start (s. 7.1.2)
During integration, a CMU does a similar startup-sequence as described in 7.1.1 except the following:
If any configuration (.gcd, .iod or password) is not present or different to the files on the other CMUs, the integrating CMU tries to load it from a CMU that is running. Afterwards the integrating CMU automatically performs a reset in order to repeat CMU start with the new configuration. After successful startup of the CMU, RTU560 System Control requests a data update from I/O Bus and Sub-Devices on the CMU(s) that were already running before the integration to actualize the integrated CMU`s database. Host interfaces on the integrating board (if present) start communication to the NCC, when this data update is finished.
1KGT 150 450 V000 1
7-3
7.1.4
CMU Removal
A CMU may be removed from a running RTU560. Already running Activities on other CMUs continue their operation:
If a SLAVE CMU is removed, after timeout of 10 s the System Message [15.1] "Slave CMU in rack x, slot y: Error" in case of removed SLAVE CMU is sent by the MASTER CMU If the MASTER CMU is removed, after timeout of 10 s the System Message [11.1] "Master for CMU in rack x, slot y: Error" in case of removed MASTER CMU the message is sent by every SLAVE CPU If a CMU running I/O busses or Sub-Devices is removed the remaining boards in the RTU560 are triggered to stamp the related process data invalid in their database.
7-4
1KGT 150 450 V000 1
7.2
RTU560 Configuration
7.2.1
General Requirements
The RTU560 needs valid configuration for operation. A RTU560 with multiple CMUs must keep equal configuration in each CMU. There are three different types of configuration files:
General Configuration Data (GCD) configuration: hardware and protocol information Input Output Data (IOD) configuration: process data point information Password configuration: password settings for the RTU560 Web-Server
The password configuration has a default setting in a new RTU and may be changed via Web-Server. The IOD and GCD configuration is provided by means of two binary files with .iod and .gcd suffix. The files are stored non-volatile in FLASH memory and are copied into RAM at CMU boot for read-only access. The files are generated with the configuration tool RTUtil NT by command (See RTUtil NT Users Guide, chapter Generate RTU-Files). The configuration files may be loaded to the RTU via RTU560 Web-Server or via NCC using a file transfer service of the communication protocol.
7.2.2
Configuration File Load Procedure

The configuration file load is done for each of the different types separately. During and after file load the RTU continues normal operation with its present configuration in RAM. Activation of the new configuration in FLASH memory is done after the next CMU start.
7.2.2.1
Load Configuration Files via RTU560 Web-Server

The RTU560 Web-Server enables a user to load configuration files into the FLASH memory file system of the addressed CMU. The addressed CMU cares for distribution of the loaded files to all CMUs in the RTU, no matter whether they are configured or not. The user is informed about the success of the file load procedure and about the number of boards that received the file. He may now decide about the activation of the new configuration via reset command to the RTU.
1KGT 150 450 V000 1
7-5
7.2.2.2
Load Configuration Files via NCC File Transfer

The configuration file load via NCC is handled together with the host-interface running a specific communication protocol. The relating file transfer service is documented in the respective protocol description. The distribution process after file load is the same as in 7.2.2.1.
7-6
1KGT 150 450 V000 1
7.3
RTU560 Time Management
7.3.1
Time Management Principle

RTU560 provides a general time base that may be synchronized in three different modes to be configured:
Clock Synchronization Command (CS Command) Synchronize by a (cyclic) time message from NCC (s. 7.3.3). CS Command & external minute pulse Synchronize by a cyclic message via a host communication interface plus an external minute pulse wired to the TSI (Time Synch. Input) of the RTU560 (s. 7.3.3.2). Radio Clock Synchronize to the GPS or DCF 77 standard (middle Europe only) (s. 7.3.3.3).
Parameter: Time synchronization mode
(RTU Parameter)
The RTU560 MASTER CMU decides during startup - by reading the GCD configuration what kind of time synchronization is configured. It synchronizes the RTU time to the provided synchronization mode and acts as the Time Master. Until the RTU is synchronized, the absolute time starts with:
Year 1980
month 01
Day 01
hour 00
minute 00
second 00
The Time Master CMU keeps the time information for the entire RTU. It generates a controlled 10 KHz clock and the internal TSO minute pulse which are needed by all Time Slaves and I/O Master. It distributes the absolute time information in time message telegrams to Time Slaves and I/O Masters.
1KGT 150 450 V000 1
7-7
NCC
CS-Command
MPU GPS TSI input
sub RTU sub RTU
Logic
IOM antenna
Master CMU
560RTC minute pulse DCF 77 transmitter Minute pulse to slow to fast I/O board Minute circuit 560RTC01 or 560RTC02
I/O Controller
Master CMU Time regulation concept for Master CMU and I/O Controller
Figure 7-1:
Principal of time synchronization in RTU560
Differences between the internal time and the received time on the Time Master are regulated by scaling predevider registers. This method allows a soft regulation of time differences and a long time correction of crystal clock errors. The Time Slave CMUs are hard coupled with the 10 khz clock and the TSO generated by the Time Master. They cyclically receive a time message by the Time Master via Internal Communication and synchronize their time accordingly. The I/O Master (IOM) - on every CMU - is hard coupled with the 10 khz clock and the TSO generated by the Time Master. It cyclically receives a time message by the MPU via the DPRAM interface and synchronizes its time accordingly. The IOM again transmits a time synchronization instruction (broadcast) cyclically to all I/O Controllers (IOC) on the I/O boards via I/O bus (typically every 2 seconds). The IOCs independently regulate deviations between their internal current time and the cyclic synchronization instructions. All I/O boards are time synchronized by the IO with a resolution of +/- 100s and accurancy of +/- 0.3ms.
7-8
1KGT 150 450 V000 1
I/O Bus
Time Master
Time Slave
Time Slave
Logic
Logic
Logic
Time Message 10 kHz TSO TSI
Time Message
Time Message
RTU560 Internal Communication
Figure 7-2:
Time Master and Slave dependencies
7.3.2
RTU560 Time Slave

A Time Slave is running on each RTU560 SLAVE CMU. Its time management is hard coupled to the Time Master. Its time base is fed by the 10 khz signal, synchronization is done via TSO minute pulse, absolute time is received via time message on Internal Communication that are provided by the Time Master. Negative System Event [25] RTU is not synchronized is sent if:

7.3.3
the 10 khz signal is missed for 5 sec or the TSO minute pulse is missed for 10 min or the time message is missed for 5 min
Time Synchronization Modes
7.3.3.1
Synchronization by CS Command from NCC

The time and date of the first received CS Command from NCC after start-up is taken to initialize all time bases on that reference. The Time Master calculates its deviation with each received CS Command and starts to compensate the difference. The long term accuracy to NCC is given to:
5 milliseconds
The CS Command should be sent from primary NCC approx. every 5 minutes. A supervision time for CS Command may be defined by configuration.
1KGT 150 450 V000 1
7-9
Parameter: Time synchronization lost
(RTU Parameter)
If no CS Command is received within the supervision time, the RTU560 Time Master indicates by negative System Event [25] RTU is not synchronized that the synchronization is lost. The RTU560 then runs with the accuracy of its own crystal clock. The time within the process messages is still valid but not synchronized to NCC. The communication line that receives the CS Command must be configured via configuration tool. The CS Command may also be sent to a communication line on a Time Slave. Parameter: Time synchronization from line (RTU Parameter)
7.3.3.2
Synchronization by CS Command & external minute pulse

This method means receiving CS Commands from NCC (s. 7.3.3.3) but synchronizing the time trigger to an external minute pulse reference, wired to the TSI input. This could be the minute pulse of a local central clock. To get a high synchronization accuracy no filter is allowed at input TSI. This method should only be used if it is guaranteed that no spikes or additional minute pulses are received from the external minute pulse source. Each time the RTU560 receives a CS Command from NCC it calculates the received time to the next full minute. The RTU560 waits for the external minute pulse to start trigger (just after the first CS Command) or as reference for synchronization. By receiving the minute pulse it regulates the time difference in the same way than for the other two modes. As in CS Command mode, a supervision time for CS Command and the communication line that receives the CS Command may be defined by configuration. Parameter: Time synchronization lost Parameter: Time synchronization from line (RTU Parameter) (RTU Parameter)
Additionally to the time synch. supervision timeout in CS Command mode, if the TSI minute pulse fails for 10 minutes, the RTU560 Time Master indicates by negative System Event [25] RTU is not synchronized the lost synchronization.
7.3.3.3
Synchronization by Radio Clock

To synchronize the time via Radio Clock, a RTC board (560RTC01 for GPS or 560RTC02 for DCF77 - middle Europe only) must be configured and available. The minute pulse output of the RTC must be wired to the TSI input. Hardware hint: In case of a RTU560 placed in a 560CSR01 rack, the TSI connection is 560BCU02/03 (see Hardware 2, connections and settings 1KGT 150 458). The RTC board receives and synchronizes itself to the DCF 77 / GPS time standard. To ensure the functionality of the RTC, the alignment and position of the antenna should be carefully checked. After power-on the RTC needs approx. 3 - 4 minutes to receive the complete information from the DCF 77 / GPS transmitter.
7-10
1KGT 150 450 V000 1
Each minute the RTU560 Time Master reads the time of the RTC via I/O bus to compare it with the RTU560 time. When RTU560 is synchronized via RTC it indicates that with positive System Events [25] RTU is synchronized and [26] External Clock of RTU is operable. If the RTC loses the synchronization (e.g. antenna error), it runs with its internal crystal clock with the specified accuracy for the next max. 2.5 hours. The Time Master sends negative System Events [25] RTU is not synchronized and [26] External clock of RTU is inoperable if:
the RTC board fails for 5 min or the minute pulse of the RTC board is lost for 10 minutes or the RTC is not synchronized to DCF 77 / GPS for more than 2.5 hours.
1KGT 150 450 V000 1
7-11
7.3.4
Synchronization of Sub-RTUs
In case of sub-RTUs time synchronization may be done via CS Command. Here any RTU560 CMU is time master for its sub-RTUs. It simulates the NCC functions by sending CS Commands cyclically with the used communication protocol. Therefor the cycle time must be configured. The parameter(s) is described in the specific protocols description (Line parameters). In case of CS Command only synchronization, the transmission time over the line makes the time accuracy on the sub-RTU worse by 5 ms per sub-ordinated line (s. Figure 7-3). To keep the same accuracy for all RTUs within a network, they have to be synchronized by an RTC each or by CS Command & ext. minute pulse.
NCC CS-Command RTU 560 + 5 ms CS-Command RTU 560 + 5 ms CS-Command RTU 560 + 15 ms + 5 ms + 10 ms
Figure 7-3:
Time accuracy in a multi level network (CS Commands only)
7-12
1KGT 150 450 V000 1
8.1
Status and Error Report to NCC

RTU560 may report about its Status and Error conditions to the NCC via the System Events (see chapter 9.2). It depends on the used communication protocol, in which way the System Event offset number is processed into address information and which data type is used for state transmission to the NCC.
8.2
Web-Server Diagnosis
The RTU560 Web-Server is the common maintenance and diagnosis tool of RTU560. In this chapter the diagnosis functions are described. For full functionality of the Web-Server s. document RTU560 Web-Server User`s Guide (1KGT 150 451).
8.2.1
System Diagnosis
For indication of the RTU560 system status System Messages are provided (see chapter 9.1). These messages are displayed after choosing the hyperlink System Diagnosis on a standard web browser surface addressing the RTU560 Web-Servers homepage. The opening page with header System Diagnosis prints the contents of a list in standard text format line by line. The general format of a System Message print is:
System Time->System Message
Where System Time is printed in the format : yy.mm.dd, hh:mm:ss

y: m: d: h: m: s:
year month day hour minute second
During the first 30 seconds after CMU boot the printed system time is set to the constant start value: 80.01.01, 00:00:00
1KGT 150 450 V000 1
8-13
Afterwards every sending CMUs internal time is printed. When the RTU is succesfully synchronized by an external source, this is indicated by System Message [9.4] RTU is synchronized. In multi-CMU configurations there is no synchronization of the System message buffer contents between the CMUs. This means, that the display of the CMU System Messages in different CMUs could be different. Every CMU starts to listen to System Messages between 15 -> 20 sec after its power-on or reset. Example: in a RTU with two CMUs -> a MASTER CMU in slot 3 and a SLAVE CMU in Slot 4, after remove and integration of CMU slot 3 the System Message printout of the CMU in slot 4 might look like:
80.01.01, 00:00:00->CMU in rack 0, slot 4: STARTUP 80.01.01, 00:00:00->CMU in rack 0, slot 3: STARTUP 80.01.01, 00:00:42->CMU in rack 0, slot 4: STARTUP READY 80.01.01, 00:00:45->CMU in rack 0, slot 3: STARTUP READY 02.11.12, 14:36:02->RTU is synchronized 02.11.12, 23:27:08->Slave CMU in rack 0, slot 3: Error 80.01.01, 00:00:00->CMU in rack 0, slot 3: STARTUP 02.11.12, 23:33:10->CMU in rack 0, slot 3: STARTUP READY 02.11.12, 23:33:12->Slave CMU in rack 0, slot 3: OK
whereas CMU in slot 3 shows only the last three entries:

80.00.01, 00:00:00->CMU in rack 0, slot 3: STARTUP 02.11.12, 23:33:10->CMU in rack 0, slot 3: STARTUP READY 02.11.12, 23:33:12->Slave CMU in rack 0, slot 3: OK
As documented in the System Message table (see chapter 9.2), most of the System Messages influence the Error Status (Warning / Alarm / OK) of the single CMUs and RTU560 (s. 8.3).
8.2.2
Status Information
The Web-Servers Status Information page gives information about the configuration of RTU560 and the actual System Event list. These messages are displayed after choosing the hyperlink Status Information on a standard web browser surface addressing the RTU560 Web-Server. The actual configuration is shown in tree structure. It is the same structure as the hardware tree in RTUtil NT. The information that could be seen in this tree includes the following points:
If anywhere a wrong measured value for example the IO Board is missing or if the measured value is invalid it is shown as a red iv sign next to the IO card. This frame is not cyclicly refreshed. Only input Board can be chosen about to see more information about measure value. The information are shown on the right frame. The actual value and status of the process objects are shown (invalid (iv) and overflow (ov)). The information are refreshed after 5 seconds.
8-14
1KGT 150 450 V000 1

If a 560ETH01 board was configured you get more information about this (IPAddress, Net- Address and Netmask) if you chosen it per mouse. The System Event list is shown after choosing RTU symbol in the tree structure. The right frame shows the actual System Event list to refresh after 10s. The positive System Event are shown green, the negative are red (s. table System Events in 9.2.).
1KGT 150 450 V000 1
8-15
8.3
LEDs, Alarm and Warning

RTU560 supports signalization to report its error state. There are three different error states: OK / Warning / Alarm
8.3.1
CMU Alarm and Warning

The CMU Alarm and Warning conditions are caused by receiving and evaluating System Messages that are described in 9.1. The signaling on a CMU is as follows: OK: Warning: Alarm: ERR LED is off ERR LED is flashing (ca. 1 Hz) ERR LED is on
8.3.2
RTU560 Alarm and Warning

The error state of any CMU in RTU560 is reported to the CMU with administration mode MASTER which evaluates a RTU560 sum state. The RTU560 error state is signalized via a Board Connection Unit (560BCU01 /02 /03) device as follows: OK: Warning: Alarm: All relays contacts off Warning relays on Warning relays on Alarm relays on
The MASTER CPU cyclically refreshes the watchdog register of the BCU device to enable RTU560 to activate the Alarm relays in case of a MASTER CMU error after 30 s.
8.3.3
LED Indications
All RTU560 boards have LEDs to indicate errors or operating modes. These LEDs allow a general visual check of the overall situation of the RTU560. The following chapters describe the LEDs for each board. Each RTU560 board has the general Error-LED "ERR" or ST. This LED indicates errors which are detected by the microprocessor / microcontroller on the board or by a hardware supervision logic. Under normal conditions the LED will go off after some time. If the LED stays on, one of the above described errors or an error of the board specific extensions is true.
8-16
1KGT 150 450 V000 1
8.3.3.1
LED indications 560SLI01 and 560ETH01
560SLI01
Tx Rx CE A B 1 2 ERR
ERR = Error (red) Tx = Transmitted Data(green) Rx = Received Data (green) CE = Communication Error(yellow) A = Serial Interface A B = Serial Interface B 1 = Serial Interface 1 2 = Serial Interface 2
Figure 8-1:
LEDs 560SLI01
560ETH01
Tx Rx CE A B A C E ERR
ERR = Error (red) Tx = Transmitted Data(green) Rx = Received Data (green) CE = Communication Error(yellow) A = Ethernet Active (green) C = Ethernet Collision (yellow) A = Serial Interface A B = Serial Interface B E = Ethernet Interface
Figure 8-2:
LEDs 560ETH01
LED
ERR
Status
ON Alarm (s. 8.3.1)
LED indications
Tx / Rx
CE A C
flashing 1 Warning (s. 8.3.1) Hz OFF - No Communication configured - Communication not initialized yet - Communication lost or broken ON Communication active flashing - I/O-Bus configuration in progress 2,5 Hz ON - Ethernet communication active ON - Collision on Ethernet line
1KGT 150 450 V000 1
8-17
8.3.3.2
LED indications 23AA20 / 23AE21 / 23BE21
23BE21 red red
23AE21 red
23AA20 "Strung" (Error)
Figure 8-3:
LEDs 23AA20 / 23AE21 / 23BE21
LED indication
Board indication
Board runs initialization procedure Board is doing a cold- or warm start Board has detected a memory error (EPROM and/or RAM) 23AA20 The microcontroller / - processor has an error 23BE21 Peripheral bus processor did not poll the board for at least two minutes. Time out IOM cycle A/D converter faulty -
23AE21
8.3.3.3
LED indications 23BA20 / 23BA22
23BA22
red red "Strung" (Error) "Proze-Strung" (Process error) red red
23BA20
"Strung" (Error) "Proze-Strung" (Process error) Command output
green green green red
TM1 TM0 CO LOC
green Test Mode circuit 2 Test Mode circuit 1 Command output LOCAL / REMOTE LOCAL / REMOTE push button
Figure 8-4:
LEDs 23BA20 / 23BA22
8-18
1KGT 150 450 V000 1
LED
ST
Status
ON
LED indications
Board runs initialization procedure. Board is doing a cold- or warm start. Board has detected a memory error (EPROM and/or RAM). The microcontroller / - processor has an error. 24 V DC for output relays failed or internal short circuit etc. Time out IOM cycle. An active output is stopped (switched off). (1 out of n)- check active for circuit P1 (TM0) or P2 (TM1). At least one relay is switched on. Command output active (pulse output or persistent if a GOM output is activated). 23BA22 is switched to local mode. No active output possible (GO relay disabled). Remote = normal command output. LOCAL / REMOTE toggle time window
PST TM0 / TM1 CO LOC
ON ON ON ON OFF Flash
LOC pushbutton
press key twice within 5 seconds to switch to LOCAL or back to REMOTE. If you press only once it is ignored. The LOC-LED will flash during that time window.
1KGT 150 450 V000 1
8-19
Object command output with (1 out of n)-check

For an object command output with command supervision the LEDs of 23BA20 and 23BA22 must be regarded together. See also chapter: Command output with supervision and see figures: 3-9 to 3-11 how the two boards are operating together for a command output.
Normal object command output
23BA20 LED
Error Process voltage error Command output
23BA22 Error Process voltage error Testmode circuit 1 Testmode circuit 2 Command output Local
= ON
Meaning 2 3 4
ST PST CO ST PST TM0 TM1 CO LOC

1 Hz
Serial data
2,5 Hz
Fig. 1 - 4 :
Normal object command output
(1) (2) (3)
Before the pulse output 23BA20 has switched the output channel 23BA22 does the (1 out of n)- check (positive) and activates GO relay for the given pulse time 232BA20 is still active; but the output relay will be switched off by the communication unit After the pulse output
(4)
(5)
8-20
1KGT 150 450 V000 1
Object command output and failure at (1 out of n)-check
23BA20 LED Error Process voltage error Command output 23BA22 Error Process voltage error Testmode circuit 1 Testmode circuit 2 Command output Local
= ON
Meaning 1 2 3 4 4a 5
ST PST CO
ST PST TM0 TM1 CO LOC

2,5 Hz 1 Hz
Serial data
Fig. 1 - 5 : Object command output and failure at (1 out of n)-check
(1) (2) (3) (4) (5)
Before the pulse output 23BA20 has switched the output channel 23BA22 does the (1 out of n)-check. The result is negative. 23BA22 flashes LED PST and TMx Alternative to 3: If the result is positive the command is switched on. If the 24 V DC fails during command output PST and CO flashes.
23BA20 relay is switched off. If failure 4 occurred The 23BA22 LEDs keeps flashing until the next output command.
1KGT 150 450 V000 1
8-21
8.3.3.4
LED indications 23WT22
23 WT 22
TxD CTS RxD SQL TxD EQZ RxD DCD
TxD = Transmitted data CTS = Clear to send EQZ = Equalizer RxD = Received data SQL = Signal quality level DCD = Data carrier detected
Figure 8-5:
LEDs 23WT22
LED
TxD TxD RxD RxD CTS DCD EQZ SQL
Status
ON ON ON ON ON ON ON ON
LED indications
Transmitted data true Inverted transmitted data true Received data true Inverted received data true Clear to send = ON Data carrier detected = ON Equalizer Signal quality level
8-22
1KGT 150 450 V000 1
8.3.3.5
LED indications 560RTC01
560RTC01
red
"Strung"
red green yellow
FR LS MN
Free running Lock status (GPS receive signal) Minute pulse
Figure 8-6:
LEDs 560RTC01
LED
ST FR LS MN
Status
ON ON ON ON
LED indications
Antenna / converter unit is defect Antenna cable is defect - Watchdog overflow because of an error on the board 560RTC01 is not synchronized by the GPS time standard or has lost the synchronization The LED indicates that min. 4 satellites are received after start up of the board and the receiver has calculated his position Minute pulse. - Flashes every minute for about 1 second.
1KGT 150 450 V000 1
8-23
8.3.3.6
LED indications 560RTC02
560RTC02
red
"Strung"
red green yellow
FR CD MN
Free running Carrier detect (DCF77 receive signal) Minute pulse
Figure 8-7:
LEDs 560RTC02
LED ST
Status ON
FR CD MN
ON ON ON
LED indications - Board runs initialization procedure - Board is doing a cold- or warm start - Board has detected a memory error (EPROM and/or RAM) - The microcontroller / - processor has an error 23RC20 is not synchronized by the DCF77 time standard or has lost the synchronization The LED indicates the receiving level of DCF77 transmitter. It allows to adjust the antenna to the maximum receiving level. Minute pulse. - Flashes every minute for about 1 second.
8-24
1KGT 150 450 V000 1
Tables
9.1
System Messages
This table shows the messages that are handled in RTU560 System Diagnosis.
Columns
No. Message number System Message text Text shown in System Diagnosis if the message occurs Reason(s) Possible reason(s) for the occurrence of the message Countermeasure(s) In case of an error the colum describes the countermessage(s) for removing it. SEV offset: If the message is derived from a System Event the number in this column means the System Event offset number. Error Status Error level that is caused by the System Message ( Alarm / Warning / OK / None). In case of OK, the message removes the corresponding error sent before (example: message 3.2 removes the Warning that was caused by message 3.1.). None means that the message has no influence to the Error Status.
1KGT 150 450 V000 1
9-1
No.
1.1
System Message text

At least one indication faulty
Reason(s)
23BE21/30 or I/O Bus error
Countermeasure(s)
SEV offset
Error Status
Warning
1.2 2.1
All indications correct At least one analog value faulty
2.2 3.1
All analog values correct At least one digital value faulty
3.2 4.1 4.2 5.1 5.2 6.1 6.2 7.1 7.2 8.1
All digital values correct At least one pulse counter faulty All pulse counters correct At least one command faulty
8.2 8.3
All object or regulation commands correct At least one analog output 23AA20 or I/O Bus error faulty All analog outputs correct At least one digital output 23BA20/30 or I/O Bus error faulty All digital outputs correct External clock is inoperable RTU not synchronized yet with RTC RTC or minute pulse is missing RTC antenna error External clock is operable RTU is synchronized with RTC RTU is not synchronized RTU Sync. not configured
Check I/O-Board and I/O- 16 Bus Oscillation suppression has Wait at least 1 minute for triggered stabile state 16 23AE21 or I/O Bus error Check I/O-Board and I/O- 17 Bus Live zero underflow Care for correct analog scaling 17 23BE21 or I/O Bus error Check I/O-Board and I/O- 18 Bus Different BCD coding Adapt BCD coding or detected configuration 18 23BE21 or I/O Bus error Check I/O-Board and I/O- 19 Bus 19 23BA20/30 or I/O Bus error Check I/O-Board and I/O- 20 Bus 20 Check I/O-Board and I/O- 21 Bus 21 Check I/O-Board and I/O- 22 Bus 22 Wait until RTU is 26 synchronized Check RTC and wiring Check RTC antenna 26
OK Warning
OK Warning
OK Warning OK Warning OK Warning OK Warning OK Warning
OK None
8.4 9.1
RTU is synchronized
Power supply failure in RTU central subrack 9.2 Power supply OK in RTU central subrack 10.1 Config-Error on CMU in rack x, slot y: WRONG RACK OR SLOT ADDRESS 10.2 Config-Error on CMU in rack x, slot y: IOD File date 10.3 Config-Error on CMU in rack x, slot y: IOD File size
Configure RTU 25 synchronization Line to NCC missing Check line to NCC Minute pulse missing Check minute pulse wiring RTC missing, error or not Check RTC, wait for sync synchronized yet RTU is synchronized from 25 RTC or by CS Command One of two configured PSU Check or replace PSU 59 boards failed boards Redundant PSU board is 59 error-free Rack address wrong Correct rack address Slot address wrong Correct slot address Configuration does not fit to Check and reload hardware Configuration Different IOD files on at If CMU integration->wait for least two CMUs CMU reboot, else reload IOD configuration IOD file(s) missing Error during IOD file If CMU integration->wait for transfer CMU reboot, else reload IOD configuration
OK Warning OK Alarm
Alarm
Alarm
9-2
1KGT 150 450 V000 1
No.
System Message text
Reason(s)
Countermeasure(s)
If CMU integration->wait for CMU reboot, else reload IOD and GCD configuration Redefine password in WebServer (based on default setting) Add a line, a peripheral bus or a PLC on the CMU
SEV offset
Error Status
Alarm
10.4 Config-Error on CMU in rack x, At least GCD files different slot y: GCD File date on at least two CMUs At least GCD file(s) missing 10.5 Config-Error on CMU in rack x, Different password settings slot y: Password 10.6 Config-Error on CMU in rack x, slot y: NO ACTIVITIES CONFIGURED 10.7 Config-Error on CMU in rack x, slot y: OK CMU is configured but no item is added Booting CMU has succesfully loaded configuration file(s) from another (running) CMU Master CMU is not configured, Master CMU is missing or has an error Master CMU is integrated Different firmware detected on at least two CMUs
Alarm
Alarm
OK
11.1 Master for CMU in rack x, slot y: Error
Correct configuration,
Alarm
Check Master Board OK Load correct firmware, care for equal firmware (first digit) on all CMUs Alarm
11.2 Master for CMU in rack x, slot y: OK 12.1 Firmware-Error on CMU in rack x, slot y version Vn.xx 12.2 No Firmware-Error on CMU in rack x, slot y 13 Activity Error for <Activity Type> in rack x, slot y: <Activity-Error Type> Activity Types 1 DATABASE 2 HOST INTERFACE 3 PERIPHERAL BUS 4 SUB INTERFACE 5 PLC 6 LOGIC FUNCTIONS 7 DATA UPDATE Activity-Error Types 1 NOT IMPLEMENTED 2 3 4 5 NOT LICENSED SUPERVISION ERROR START ERROR START TIMEOUT
OK s. Activity-Error Types s. Activity-Error Types Warning
Activity type not implemented in firmware Activity type not licensed MPU overload Configuration could not be processed Common Activity start error Memory overflow CMU performed a reset CMU succesful started SLAVE CMU is missing or has an error SLAVE CMU is integrated
Load correct firmware Apply for license key and load to RTU Shrink configuration Check configuration Check supplementary error information Shrink configuration Wait for STARTUP READY
6 INTERNAL ERROR 14.1 CMU in rack x, slot y: STARTUP 14.2 CMU in rack x, slot y: STARTUP READY 15.1 Slave CMU in rack x, slot y: Error 15.2 Slave CMU in rack x, slot y: OK
Alarm OK
Integrate missing Slave Board
Alarm OK
1KGT 150 450 V000 1
9-3
No.
System Message text
Reason(s)
Countermeasure(s)
SEV offset
Error Status
Warning
16.1 Slave CMU in rack x, slot y: Warning 16.2 Slave CMU in rack x, slot y: OK 17.1 RTU A is active 17.2 RTU A is not active 18.1 RTU B is active 18.2 RTU B is not active 19.1 19.2 20.1 20.2 21.1 RTU A is operable RTU A is inoperable RTU B is operable RTU B is inoperable RTU is inoperable
Non-redundant SLAVE Integrate missing Slave CMU in redundant system is Board missing or has an error
OK Redundant system A is active to NCC Redundant system A is not active to NCC Redundant system B is active to NCC Redundant system B is not active to NCC Redundant system A error Redundant system B error Sub RTU inoperable Sub RTU operable Wait for system A startup Wait for system B startup Check Sub-RTU and communication 60 60 61 61 62 62 63 63 48 48 None None None None OK Warning OK Warning Warning
21.2 RTU is operable
9-4
1KGT 150 450 V000 1
9.2
System Events
This table shows the System Events that are handled in Status/Error report to NCC and Status Information in Web-Server.
Columns
SEV offset: System Event offset address within the System Event Block System Event Meaning of System Event list in case of positive transmission value. The default value is not set Reason(s) Possible reason(s) for the occurrence of the message
SEV offset
16 17 18 19 20 21 22 23 24 25 26 48 49 59 60 61 62 63 64 - 79 80 - 95 96 101..108 152 154 155 171 172
System Event
At least one indication is faulty At least one analog value faulty At least one digital value faulty At least one pulse counter faulty At least one command is faulty At least one analog output faulty At least one digital output is faulty RTU is faulty RTU is active RTU is synchronized External clock is inoperable RTU is inoperable RTU out of service Power supply failure in RTU central subrack RTU 'A' is Active RTU 'B' is Active RTU 'A' is operable RTU 'B' is operable Line is faulty 1..16.Cmd. supervision circuit disconnected or faulty Disturbance data ready for transmission Host 1 .. 8 Online Prio1 queue overflow Prio2 queue overflow Insuff. space for data base in RTU IR pulse counter lost due to queue overflow EPR pulse counter lost due to queue overflow
Reason(s)
s. System Message No. 1 s. System Message No. 2 s. System Message No. 3 s. System Message No. 4 s. System Message No. 5 s. System Message No. 6 s. System Message No. 7 Not supported Iod configuration is correct s. System Message No. 8.4 s. System Message No. 8.1 Sub RTU is inoperable Not supported s. System Messages No. 9 s. System Message No. 17 s. System Message No. 18 s. System Message No. 19 s. System Message No. 20 Not supported s. 2. Not supported NCC connection established Prio1 queue is overflow (s. 4.: Queue Transitions and Overflow) Prio2 queue is overflow (s. 4.: Queue Transitions and Overflow) Memory error Queue overflow (s. 4.: Queue Transitions and Overflow) Queue overflow (s. 4:: Queue Transitions and Overflow)
1KGT 150 450 V000 1
9-5
9-6
1KGT 150 450 V000 1

E560 Function Description

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

E560 Function Description

Hochgeladen von

Copyright:

Verfügbare Formate

RTU560 Remote Terminal Unit

RTU560 Function Description

1KGT 150 450 V000 1

ABB Utility Automation GmbH E560_FD.doc

1KGT 150 450 V000 1

RTU560 Function Description

2 SCADA MONITORING DIRECTION...................................................2-1

ABB Utility Automation GmbH E560_FD.doc

1KGT 150 450 V000 1

RTU560 Function Description

3 SCADA COMMAND DIRECTION....................................................... 3-1

4 HOST COMMUNICATION INTERFACE ............................................ 4-1

5 SUB-DEVICE COMMUNICATION INTERFACE ................................ 5-1

6 INTERFACES AND NETWORK......................................................... 6-1

1KGT 150 450 V000 1

ABB Utility Automation GmbH E560_FD.doc

RTU560 Function Description

6.4.1 6.4.2 6.4.3 6.4.4

7 STARTUP, CONFIGURATION AND TIME MANAGEMENT ..............7-1

8 STATUS AND DIAGNOSTIC INFORMATION ..................................8-13

ABB Utility Automation GmbH E560_FD.doc

1KGT 150 450 V000 1

RTU560 Function Description

1KGT 150 450 V000 1

ABB Utility Automation GmbH E560_FD.doc

RTU560 Function Description

ABB Utility Automation GmbH E560_FD.doc

1KGT 150 450 V000 1

RTU560 Function Description

ABB Utility Automation GmbH E560_FD.doc

1KGT 150 450 V000 1

RTU560 Function Description

1KGT 150 450 V000 1

ABB Utility Automation GmbH E560_FD.doc

RTU560 Function Description

About the RTU560 Function Description

Regulations for the installation and operation of electrical systems

DIN VDE 0100 DIN VDE 0106

DIN VDE 0800 IEC 61131

ABB Utility Automation GmbH E560_FD.doc

1KGT 150 450 V000 1

RTU560 Function Description

Installation and application hints

Use according to the rules

1KGT 150 450 V000 1

ABB Utility Automation GmbH E560_FD.doc

RTU560 Function Description

Connection of the supply voltage

Do not obstruct the ventilation for cooling

Do not cover the ventilation slots by cables or wires.

Lead signal- and power-lines separately

Use overvoltage protection in cables to outdoor antenna

ABB Utility Automation GmbH E560_FD.doc

1KGT 150 450 V000 1

RTU560 Function Description

Graphic Aids in the Function Description

Find the cross reference

Cross reference to RTUtil NT Users guide

ABB Utility Automation GmbH

1KGT 150 450 V000 1

Chapter in RTUtil NT Users Guide

1KGT 150 450 V000 1

ABB Utility Automation GmbH E560_FD.doc