Irtu, Igw & Irtue Series: User Manual [PDF]
iRTU, iGW & iRTUe Series User Manual June 2017 Revision 2 iRTU, iGW & iRTUe Series User Manual About this manual Comp
31 0 8MB
Papiere empfehlen
![Irtu, Igw & Irtue Series: User Manual [PDF]](https://vdoc.tips/img/200x200/irtu-igw-amp-irtue-series-user-manual.jpg)
- Author / Uploaded
- Fabricio Morales
Datei wird geladen, bitte warten...
Zitiervorschau
iRTU, iGW & iRTUe Series User Manual June 2017 Revision 2
iRTU, iGW & iRTUe Series User Manual
About this manual Company iGrid T&D is a specialized company in the development of electrical facility control applications, with a wide experience in the power industry. Products and services focus on telecontrol of power generation, transmission and distribution facilities, covering from generic substation I/O IEDs to medium voltage grid SCADA systems, including Remote Terminal Units (RTU) and gateways, both for substations and transformer or power stations.
Copyrights The information in this document is subject to change without notice and should not be construed as a commitment by iGrid T&D. iGrid T&D assumes no responsibility for any errors that may appear in this document. If you have any suggestions for improvements or amendments or have found errors in this publication, please notify us. In no event shall iGrid T&D be liable for direct, indirect, special, incidental, or consequential damages of any nature or kind arising from the use of this document, nor shall iGrid T&D be liable for incidental or consequential damages arising from use of any software or hardware described in this document. No part of this document may be reproduced in any form or by any means, electronic or mechanical, including photocopying, without express written permission of iGrid T&D. The software or hardware described in this document is furnished under a license and may be used, copied, or disclosed only in accordance with the terms of such license. © 2017 iGrid T&D. All rights reserved.
General This manual provides thorough technical information on the iRTU, iGW and iRTUe Series products. Information on this manual is intended for engineers who install and commission iRTU, iGW and iRTUe devices.
Warranty All products designed and supplied by iGrid T&D are bound by a 2 year Warranty Certificate against design and/or manufacturing defects, except for specific contracts. Any damage caused to products will not be covered by this certificate.
Version history Version
Date
Comment
0
1 June 2014
Initial version.
1
1 July 2016
Document reformatted.
2
1 June 2017
This revision includes new models technical specification and new features description. Table 1 – Version history
─ Index ─ About this manual
2
iRTU, iGW & iRTUe Series User Manual
Use of symbols This publication includes information icons that point out important information. It also includes tip icons to point out useful information to the reader. The corresponding icons should be interpreted as follows. The information icon alerts the reader to relevant facts and conditions.
The tip icon indicates advice on, for example, how to design, configure or use a certain functionality.
Abbreviations Abbreviation
Description
AC AI CC CI DC DI DO HV IED I/O LV MV RTU SCADA SOE
Alternate Current Analog Input Control Center Counter Input Direct Current Digital Input Digital Output High Voltage Intelligent Electronic Device Input/Output Low Voltage Medium Voltage Remote Terminal Unit Supervisory Control and Data Acquisition Sequence of Events Table 2 – Abbreviations list
─ Index ─ About this manual
3
iRTU, iGW & iRTUe Series User Manual
Safety Information Please read these instructions carefully and familiarize yourself with the product prior to installation, operation, servicing and/or maintenance.
Equipment operation The user is responsible for verifying that characteristics stated for the product are suitable for the application. The user is responsible for reading and following the installation and operation instructions prior to commissioning and maintenance. Non observance of these instructions may impact equipment operation and create a potential hazard.
Electrical connections The user is responsible for complying with all current national and international electrical standards.
Prior to connecting any power supply to the equipment, the user should ensure that the grounding terminal is properly grounded. The ground connection serves a significant safety function. This connection should not be made by using any component other than the grounding terminal.
Figure 1 shows the location of the grounding terminal in an iRTU unit:
Grounding terminal Figure 1 – Grounding terminal is located at the bottom of the iRTU & iGW units, and at the top of the iRTUe units
─ Index ─ Safety information
4
iRTU, iGW & iRTUe Series User Manual
iRTU & iGW Products License All iRTU & iGW Series products are supplied with a license that sets the communication capabilities of the device in terms of number of supported devices (IEDs and control centers), maximum number of points and used protocols. The license also defines advanced functionalities such as hot-standby redundancy, PLC and file transfer functionalities. The license file name is made up of the device’s license code and a .bin extension. All iRTU & iGW units have a unique license code that identifies them. This license code consists of 32 characters (numbers and letters) separated in 4 groups by a hyphen (e.g.: 74498229-23BB7F2D01149794-03CAA291). Please, refer to section 16 for further information on:
License update process. iRTU & iGW license troubleshooting.
─ Index ─ iRTU & iGW Products License
5
iRTU, iGW & iRTUe Series User Manual
Table of Contents About this manual .....................................................................................................................................2 Company....................................................................................................................................................................... 2 Copyrights..................................................................................................................................................................... 2 General ......................................................................................................................................................................... 2 Warranty....................................................................................................................................................................... 2 Version history ............................................................................................................................................................. 2 Use of symbols ............................................................................................................................................................. 3 Abbreviations ............................................................................................................................................................... 3
Safety Information.....................................................................................................................................4 Equipment operation ................................................................................................................................................... 4 Electrical connections .................................................................................................................................................. 4
iRTU & iGW Products License ....................................................................................................................5 1. Introduction ....................................................................................................................................12 2. Products overview ...........................................................................................................................14 2.1. iRTU Series: RTUs for Substation Automation and Telecontrol of MV grids .................................................. 14 2.1.1. Product main features .............................................................................................................................. 14 2.1.2. Product models ......................................................................................................................................... 15 2.2. iGW Series: versatile communication gateways for electrical facilities .......................................................... 18 2.2.1. Product main features .............................................................................................................................. 18 2.2.2. Product models ......................................................................................................................................... 19 2.3. iRTUe Series: I/O expansion modules for iRTU & iGW units ........................................................................... 22 2.3.1. Product main features .............................................................................................................................. 22 2.3.2. Product models ......................................................................................................................................... 23
3. 4. 5.
Power supply specifications .............................................................................................................24 I/O modules technical characteristics ..............................................................................................25 iRTU-B0 Series (iRTU-B0C1 & iRTU-B0D1): physical description and technical characteristics..........27 5.1.1. Serial communication ports ..................................................................................................................... 30 Serial port COM1 pinout ............................................................................................................... 30 Serial ports COM2 & COM3 pinout .............................................................................................. 31 EXP422 serial port ......................................................................................................................... 32 Serial ports DIP switch .................................................................................................................. 32 RS485 (2-wires) connection considerations ................................................................................ 33 5.1.2. 5.1.3. 5.1.4. 5.1.5. 5.1.6. 5.1.7.
6.
Ethernet communication ports ................................................................................................................ 34 Configuration microswitch ....................................................................................................................... 34 Reset button .............................................................................................................................................. 35 I/O configuration ....................................................................................................................................... 36 LED functions ............................................................................................................................................ 36 Configuration and maintenance .............................................................................................................. 37
iGW-B0 Series: physical description and technical characteristics ...................................................38 6.1.1. Serial communication ports ..................................................................................................................... 40 Serial port COM1 pinout ............................................................................................................... 40 Serial ports COM2 & COM3 pinout .............................................................................................. 40 EXP422 serial port ......................................................................................................................... 40 Serial ports DIP switch .................................................................................................................. 40 RS485 (2-wires) connection considerations ................................................................................ 40 6.1.2. 6.1.3. 6.1.4. 6.1.5. 6.1.6.
Ethernet communication ports ................................................................................................................ 40 Configuration microswitch ....................................................................................................................... 40 Reset button .............................................................................................................................................. 41 I/O configuration ....................................................................................................................................... 41 LED functions ............................................................................................................................................ 41
Table of Contents
6
iRTU, iGW & iRTUe Series User Manual
6.1.7. Configuration and maintenance .............................................................................................................. 41
7.
iGW-B1 Series: physical description and technical characteristics ...................................................42 7.1.1. Serial communication ports ..................................................................................................................... 44 Serial port COM1 pinout ............................................................................................................... 44 Serial port COM2 pinout ............................................................................................................... 44 Serial ports DIP switch .................................................................................................................. 44 RS485 (2-wires) connection considerations ................................................................................ 44 7.1.2. Ethernet communication ports ................................................................................................................ 44 7.1.3. LED functions ............................................................................................................................................ 44 7.1.4. Configuration and maintenance .............................................................................................................. 45
8.
iRTU-S3 Series (iRTU-S3C1 & iRTU-S3D1): physical description and technical characteristics...........46 8.1.1. Serial communication ports ..................................................................................................................... 50 Serial port COM1 pinout ............................................................................................................... 50 Serial ports COM2 & COM3 pinout .............................................................................................. 50 EXP422 serial port ......................................................................................................................... 50 Serial ports DIP switch .................................................................................................................. 50 RS485 (2-wires) connection considerations ................................................................................ 50 8.1.2. 8.1.3. 8.1.4. 8.1.5. 8.1.6. 8.1.7.
9.
Ethernet communication ports ................................................................................................................ 50 Configuration microswitch ....................................................................................................................... 50 Reset button .............................................................................................................................................. 50 I/O configuration ....................................................................................................................................... 50 LED functions ............................................................................................................................................ 51 Configuration and maintenance .............................................................................................................. 51
iGW-S3 Series: physical description and technical characteristics ....................................................52 9.1.1. Serial communication ports ..................................................................................................................... 55 Serial port COM1 pinout ............................................................................................................... 55 Serial ports COM2 & COM3 pinout .............................................................................................. 55 EXP422 serial port ......................................................................................................................... 55 Serial ports DIP switch .................................................................................................................. 55 RS485 (2-wires) connection considerations ................................................................................ 55 9.1.2. 9.1.3. 9.1.4. 9.1.5. 9.1.6. 9.1.7.
Ethernet communication ports ................................................................................................................ 55 Configuration microswitch ....................................................................................................................... 55 Reset button .............................................................................................................................................. 55 I/O configuration ....................................................................................................................................... 55 LED functions ............................................................................................................................................ 55 Configuration and maintenance .............................................................................................................. 55
10. iRTU-M Series (iRTU-M0, iRTU-M1 and iRTU-M2): physical description and technical characteristics .........................................................................................................................................56 10.1.1. Serial communication ports .................................................................................................................. 60 Serial ports COM2 & COM3 pinout .............................................................................................. 60 EXP422 serial port ......................................................................................................................... 60 Serial ports DIP switch .................................................................................................................. 60 RS485 (2-wires) connection considerations ................................................................................ 60 10.1.2. Ethernet communication ports ............................................................................................................. 60 10.1.3. Configuration microswitch .................................................................................................................... 60 10.1.4. Reset button ........................................................................................................................................... 60 10.1.5. I/O configuration .................................................................................................................................... 61 10.1.6. LED functions.......................................................................................................................................... 61 10.1.7. 4G/3G/GSM/GPRS built-in modem technical specifications ............................................................... 61 10.1.8. SIM Access .............................................................................................................................................. 62 10.1.9. Configuration and maintenance ........................................................................................................... 62 10.1.10. 4G/3G/GSM/GPRS modem management ............................................................................................ 63
Table of Contents
7
iRTU, iGW & iRTUe Series User Manual
11. iGW-M Series (iGW-M0, iGW-M1 and iGW-M2): physical description and technical characteristics 64 11.1.1. Serial communication ports .................................................................................................................. 66 Serial ports COM2 & COM3 pinout .............................................................................................. 66 EXP422 serial port ......................................................................................................................... 66 Serial ports DIP switch .................................................................................................................. 66 RS485 (2-wires) connection considerations ................................................................................ 66 11.1.2. Ethernet communication ports ............................................................................................................. 66 11.1.3. Configuration microswitch .................................................................................................................... 66 11.1.4. Reset button ........................................................................................................................................... 66 11.1.5. I/O configuration .................................................................................................................................... 66 11.1.6. LED functions.......................................................................................................................................... 66 11.1.7. 4G/3G/GSM/GPRS built-in modem technical specifications ............................................................... 66 11.1.8. SIM Access .............................................................................................................................................. 66 11.1.9. Configuration and maintenance ........................................................................................................... 66 11.1.10. 4G/3G/GSM/GPRS modem management ............................................................................................ 67
12. iRTUe I/O expansion devices: physical description and technical characteristics .............................68 12.1. 12.2. 12.3. 12.4.
Connection to iRTU, iGW and other iRTUe devices via EXP422 port ........................................................... 76 I/O configuration ............................................................................................................................................. 77 LED functions .................................................................................................................................................. 77 iRTUe address configuration .......................................................................................................................... 78
13. Time synchronization in iRTU & iGW series products.......................................................................80 13.1. Synchronization priority and fault tolerance ................................................................................................. 80 13.2. Time validity .................................................................................................................................................... 80 13.3. Internal alarms and events ............................................................................................................................. 80
14. Configuration and maintenance of the iRTU and iGW units .............................................................82 14.1. Introduction: accessing the configuration of iRTU & iGW units .................................................................. 82 14.1.1. Using iConf ............................................................................................................................................. 82 14.1.2. Using a USB drive ................................................................................................................................... 82 14.1.3. Using FTP ................................................................................................................................................ 82 Through USB .................................................................................................................................. 83 Through Ethernet .......................................................................................................................... 83 14.2. First steps: downloading and installing the iRTU/iGW driver ....................................................................... 84 14.2.1. 14.2.2. 14.2.3. 14.2.4.
Downloading the driver using iConf tool .............................................................................................. 84 Downloading the driver using a USB drive ........................................................................................... 85 Downloading the driver using FTP ........................................................................................................ 85 Installing the driver ................................................................................................................................ 86
14.3. Configuring the iRTU & iGW units database and communication via iConf tool ........................................ 87 14.4. Applying configuration to the iRTU & iGW units ........................................................................................... 87 14.4.1. Using iConf tool ...................................................................................................................................... 87 14.4.2. Using a USB drive ................................................................................................................................... 87 14.4.3. Using FTP ................................................................................................................................................ 89 14.5. Updating the firmware ................................................................................................................................... 90 14.5.1. Using iConf tool ...................................................................................................................................... 90 14.5.2. Using a USB drive ................................................................................................................................... 90 14.5.3. Using FTP ................................................................................................................................................ 90 14.6. Updating license ............................................................................................................................................. 91 14.6.1. Using iConf tool ...................................................................................................................................... 91 14.6.2. Using a USB drive ................................................................................................................................... 91 14.6.3. Using FTP ................................................................................................................................................ 91 14.7. Updating timezones ........................................................................................................................................ 92 14.7.1. Using iConf tool ...................................................................................................................................... 92 14.7.2. Using FTP ................................................................................................................................................ 92
Table of Contents
8
iRTU, iGW & iRTUe Series User Manual
14.8. Downloading the configuration ..................................................................................................................... 92 14.8.1. Using iConf tool ...................................................................................................................................... 92 14.8.2. Using a USB drive ................................................................................................................................... 93 14.8.3. Using FTP ................................................................................................................................................ 93 14.9. Management of the iRTU & iGW units via iConf tool ................................................................................... 94 14.9.1. 14.9.2. 14.9.3. 14.9.4. 14.9.5. 14.9.6.
Connect option ....................................................................................................................................... 94 Load device configuration option .......................................................................................................... 96 Apply configuration to device option .................................................................................................... 96 Backup device configuration option...................................................................................................... 97 Open console option .............................................................................................................................. 97 Advanced options................................................................................................................................... 98 Update timezones ......................................................................................................................... 98 Update license ............................................................................................................................... 98
14.9.7. Update firmware option ........................................................................................................................ 99
15. Maintenance console ....................................................................................................................100 15.1. Accessing the maintenance console ............................................................................................................ 100 15.2. Maintenance console password .................................................................................................................. 100 15.3. Maintenance console sections and commands .......................................................................................... 100 15.3.1. Basic definitions ................................................................................................................................... 100 15.3.2. Main section commands ..................................................................................................................... 101 help and ? commands ................................................................................................................. 102 sections command ...................................................................................................................... 103 continue and c commands .......................................................................................................... 104 cd command ................................................................................................................................ 104 trace command ........................................................................................................................... 104 ver command............................................................................................................................... 108 date command ............................................................................................................................ 108 shutdown command ................................................................................................................... 108 reload command ......................................................................................................................... 109 modules or mod command ......................................................................................................... 109 files command ............................................................................................................................. 110 versions command ...................................................................................................................... 113 modon command ........................................................................................................................ 113 modoff command ........................................................................................................................ 114 info command ............................................................................................................................. 114 list command ............................................................................................................................... 115 list dv command ........................................................................................................................... 115 list mv command .......................................................................................................................... 116 list cm command .......................................................................................................................... 116 list sp command ........................................................................................................................... 117 list cnt command .......................................................................................................................... 117 list all command ....................................................................................... 117 argument ......................................................................................................................... 118 soe command .............................................................................................................................. 120 commands command ................................................................................................................. 122 display command ........................................................................................................................ 122 soe_note command .................................................................................................................... 123 15.3.3. Section sim commands ........................................................................................................................ 124 dv command ................................................................................................................................ 125 mv command ............................................................................................................................... 125 cm command ............................................................................................................................... 126 sp command ................................................................................................................................ 127 cnt command .............................................................................................................................. 127 cnt [value] [quality] command .......................................................................................... 127
Table of Contents
9
iRTU, iGW & iRTUe Series User Manual
cnt add [quality] command ................................................................................. 128 cnt reset command............................................................................................................ 128
dva command .............................................................................................................................. 128 mva command............................................................................................................................. 129 mvs command ............................................................................................................................. 129 cnts command ............................................................................................................................. 129 15.3.4. Section ip commands ........................................................................................................................... 129 ping command ............................................................................................................................ 130 ipconfig command ...................................................................................................................... 130 filter command ............................................................................................................................ 130 ipstats command......................................................................................................................... 131 route command ........................................................................................................................... 131 15.3.5. Other sections commands and options .............................................................................................. 131 15.4. iDevSetup menu ............................................................................................................................................ 132 15.4.1. Accessing the iDevSetup menu ........................................................................................................... 132 15.4.2. iDevSetup menu options ...................................................................................................................... 132 Show IP settings option............................................................................................................... 133 Change IP settings option ........................................................................................................... 133 Show system info option ............................................................................................................. 133 Execute factory test option ......................................................................................................... 134 Field user test (key “m”)............................................................................................................... 134 Factory test (key “a”) ................................................................................................................... 134 EXP422 patch cord test (key “p”) ................................................................................................ 134 Check test validation code (key “c”) ............................................................................................ 135 Execute iRTU application in test mode option ........................................................................... 135 Redundancy setup option ........................................................................................................... 135 Internal PPS calibration option ................................................................................................... 136 Update iKernel option ................................................................................................................. 136 Quit option .................................................................................................................................. 136 15.4.3. iDevSetup update process via FTP....................................................................................................... 136
16. Licensing system ............................................................................................................................137 16.1. iRTU & iGW license errors ............................................................................................................................ 137
17. Hot-Standby redundancy ...............................................................................................................138 17.1. Redundancy configuration in iConf.............................................................................................................. 141 17.2. First time redundancy configuration ........................................................................................................... 143 17.2.1. Configuration and redundancy operation test example .................................................................... 143 17.3. 17.4. 17.5. 17.6.
Redundancy section (rdcy) in iRTU/iGW maintenance console ................................................................. 149 Redundancy states ........................................................................................................................................ 150 Redundancy internal points ......................................................................................................................... 155 Direct serial link between redundant iRTU/iGW: serial cable layout ......................................................... 158
18. iKernel version and update process ...............................................................................................159 18.1. Checking the iKernel version ........................................................................................................................ 159 18.2. iKernel update process ................................................................................................................................. 160
19. Field User Test ...............................................................................................................................162 19.1. iRTU & iGW user test .................................................................................................................................... 163 19.1.1. General tests ........................................................................................................................................ 163 Get Version (key “a”) ................................................................................................................... 163 Activation Code (key “b”) ............................................................................................................ 163 Eeprom Test (key "c").................................................................................................................. 163 RTC Test (key "d") ........................................................................................................................ 163 LEDs Test (key "e") ...................................................................................................................... 164
Table of Contents
10
iRTU, iGW & iRTUe Series User Manual
USwitch Test (key "f") ................................................................................................................. 164 USB port Test (key "g") ................................................................................................................ 164 I/O board firmware version ........................................................................................................ 165 19.1.2. Communication ports tests ................................................................................................................. 165 COM1 mode RS-232 data test .................................................................................................... 165 COM1 mode RS-232 control lines test ....................................................................................... 166 COM1 - COM2 mode RS-422 data test ...................................................................................... 166 COM2 - COM1 mode RS-422 data test ...................................................................................... 166 COM1 - COM3 mode RS-422 data test ...................................................................................... 167 COM3 - COM1 mode RS-422 data test ...................................................................................... 167 EXP422 data test ......................................................................................................................... 167 Ethernet ports tests .................................................................................................................... 168 19.1.3. I/O ports tests ...................................................................................................................................... 169 Digital input test .......................................................................................................................... 170 Digital output test ....................................................................................................................... 170 Analog input test ......................................................................................................................... 170 19.2. iRTUe user test .............................................................................................................................................. 170
20. Dimensional outline drawings........................................................................................................172 21. iRTU & iGW series type tests .........................................................................................................175 22. Ordering information.....................................................................................................................178 22.1. iRTU-B0 Series ............................................................................................................................................... 178 22.2. iGW-B0 Series ............................................................................................................................................... 178 22.3. iGW-B1 Series ............................................................................................................................................... 179 22.4. iRTU-S3 Series ............................................................................................................................................... 179 22.5. iGW-S3 Series ................................................................................................................................................ 180 22.6. iRTU-M Series ................................................................................................................................................ 181 22.7. iGW-M Series ................................................................................................................................................ 181 22.8. iRTUe Series .................................................................................................................................................. 182 22.9. iRTU & iGW communication capabilities and advanced functionalities .................................................... 183 22.10. Connectoring kits .......................................................................................................................................... 183 22.10.1. iRTU-B0 Series connectoring kits ........................................................................................................ 183 22.10.2. iGW-B0 Series connectoring kits ......................................................................................................... 184 22.10.3. iGW-B1 Series connectoring kits ......................................................................................................... 184 22.10.4. iRTU-S3 Series connectoring kits ......................................................................................................... 184 22.10.5. iGW-S3 Series connectoring kits ......................................................................................................... 185 22.10.6. iRTU-M Series connectoring kits ......................................................................................................... 185 22.10.7. iGW-M Series connectoring kits .......................................................................................................... 186 22.10.8. iRTUe Series connectoring kits ............................................................................................................ 186
ANNEX I: iAppManager version .............................................................................................................188
Table of Contents
11
iRTU, iGW & iRTUe Series User Manual
1. Introduction The iRTU & iGW Series includes a range of products designed for electrical facility control and supervision, whether at power stations, HV substations or MV/LV transformer stations. iRTU Series products concentrate all data coming from the various facility devices, either through high point density digital and analog inputs or using communication protocols, subsequently sending them to different control centers as defined by the electric utility. The main product in the range is the iRTU, which operates as an electrical facility Remote Terminal Unit with high scalability, both for process and input/output configuration capabilities. iRTUe auxiliary units allow simple expansion with both digital and analog additional inputs and outputs. Other products, such as the iGW units, are designed to be used as communication protocol concentrators, similar to the iRTU but without direct input/output option. Thus, iRTU & iGW Series products may perform different functions within a facility based on their configuration, either at the software and database level or at the acquisition and communication card level. Therefore, they may operate within a facility as Remote Terminal Units (RTU), as concentrators of data from other devices (gateways), as BCUs (Bay Control Units) or as I/O IEDs, complying at all times with the required power transmission and distribution industry standards.
Figure 2 – Communication schema using iRTU, iGW and iRTUe units
Figure 3 and Figure 4 show the front and rear view, respectively, of an iRTU unit (iRTU-B0C1) with detail of the communication ports, wiring duct, front LEDs, I/O ports, DIN rail mounting clips and the grounding terminal.
─ Index ─ 1. Introduction
12
iRTU, iGW & iRTUe Series User Manual
Communication ports (COM1 & COM2) Wiring duct Indicator LEDs
Configuration microswitch
I/O ports
PC connection USB drive connection
Communication ports (COM3, EXP422, ETH)
Figure 3 – iRTU & iGW series products: iRTU-B0C1 front view
DIN rail mounting clips
Grounding terminal
Figure 4 – iRTU & iGW series products: iRTU-B0C1 rear view
─ Index ─ 1. Introduction
13
iRTU, iGW & iRTUe Series User Manual
2. Products overview This chapter will describe the general characteristics and features of the iRTU, iGW and iRTUe series.
2.1. iRTU Series: RTUs for Substation Automation and Telecontrol of MV grids The iRTU units are designed to be used as Remote Terminal Units for information transfer between an electrical facility and a SCADA system, or between different RTU/IED levels within a single facility. These units provide both for direct data acquisition, including various digital and analog input/output configurations, and for communications with other devices through different serial ports (RS232/RS422/RS485) and Ethernet ports.
2.1.1.
Product main features
Product main features are summarized below:
General: o Smart and modular remote telecontrol units suitable for HV Substation Automation and Telecontrol of MV grids. o Availability of multiple communication options including serial ports, embedded Ethernet switches, and built-in 4G, 3G, GPRS or PSTN modems. o High I/O density. iRTU devices provide I/O capabilities for direct data acquisition which can be expanded by using iRTUe devices. o CPU characteristics: ARM9 @ 400MHz, with 128MB NAND Flash and 64MB SDRAM. o Real time processing with 1ms accuracy. o High accuracy real time clock with 1.5ppm drift. o Complies with IEC61850-3 EMC.
Configuration and maintenance: o Easy configuration and maintenance by using iGrid T&D’s free iConf tool. o Possibility of local and remote maintenance connection, using USB or Ethernet ports. o Availability of command line console where the packets exchange is displayed in real time for all available protocols, and where the user can simulate, consult and act over the product behavior.
iRTU software application (iGComms): o Time synchronization options: SNTP (client and server), IEC60870-5-101, IEC60870-5-102, IEC60870-5-103, IEC60870-5-104, DNP3.0, DLMS, Procome and Profibus DP. o Definition of arithmetic, logical and relational operations, and mathematical functions using LUA (Lua 5.2, http://www.lua.org/) as programming language, via iConf tool. o IEC61131-3 automation: logic and PLC programming. o iRTU models come with a full range of protocols including IEC60870-5-101 (master and slave), IEC60870-5-102 (master), IEC60870-5-103 (master), IEC60870-5-104 (master and slave), IEC61850 MMS client/server, IEC61850 GOOSE publisher/subscriber, Modbus RTU/TCP/UDP (master and slave), DNP3.0 serial/TCP (master and slave), DLMS (master), IEC62056-21 (master), Profibus DP (master) and Procome (master), in order to ensure the communication with new and legacy IEDs and SCADA master stations. o Redundancy: iRTU units can be deployed on a hot-standby configuration, and include redundant power supply. S3 Series includes IEEE 802.1d RSTP (Rapid Spanning Tree Protocol). ─ Index ─
2. Products overview
14
iRTU, iGW & iRTUe Series User Manual
Device Features: o Two options of power supply: Wide range power supply: 32 - 250Vdc / 80 - 250Vac (2.5kVrms isolation). 24 Vdc power supply: 19.5-60Vdc (2.5kVrms isolation). o EMC type test: IEC 60950-1, IEC 60255-5:2000, EC 60255-22:2000, EN 55022, IEC 61000-64, IEC 61000-6-5, IEC 61000-4-2, IEC 61000-4-3, IEC 61000-4-4, IEC 61000-4-5, IEC 610004-6, IEC 61000-4-8, IEC 61000-4-9, IEC 61000-4-10, IEC 61000-4-12, IEC 61000-4-16, IEC 61000-4-17, IEC 61000-4-18, IEC 61000-4-29. o Environmental: Operating temperature: -25ºC to +70ºC. IEC 60068-2-1, IEC 60068-2-2, IEC 60068-2-3, IEC 60068-2-14, IEC 60068-2-30, IEC 60068-2-38. o Vibration & Shock test: IEC 60068-2-6, IEC 60068-2-7. o Physical: External dimensions: 173 x 137 x 78.4 (mm). Rail mounting.
2.1.2.
Product models
This section will describe the available iRTU models and options. The basic communication configuration for iRTU units (model iRTU-B0) is as follows:
(4) serial ports (2.5 kVrms isolation) with TX/RX LED indicators: o (1) Full RS232/RS422/RS485 serial port, software configurable (COM1 port). o (2) Basic RS232/RS422/RS485 serial ports, software configurable (COM2 & COM3 ports). o (1) RS422/RS485 serial port, software configurable (EXP422 port), for connection to iRTUe I/O expansion units (refer to section 12). (1) 10/100BaseTx Ethernet port (RJ45 connector). (1) USB port to connect peripheral devices (e.g. USB drives). (1) MGMT port (MiniUSB connector) to connect to a PC for local maintenance. (1) MicroSD internal slot for data storage.
This basic configuration may be expanded by adding different communication options. As an example, iRTU-S3 units include a S3 module (switch module) with the following characteristics:
Equipped with embedded Ethernet switch. Serial ports: same as iRTU-B0. (2) Ethernet 10/100BaseTX ports (RJ45 connector). (2) Redundant 100BaseFX Ethernet ports. Available interfaces: optical interface with ST or SC connectors, or SFP interface. (1) USB port. (1) MGMT port (MiniUSB connector). (1) MicroSD internal slot for data storage.
The redundant Ethernet ports of the S3 modules are available with the following interfaces:
Optical interface with SC or ST connectors, multimode fiber (62.5/125 µm and 50/125 µm) and 1300 nm wavelength. SFP (Small Form-factor Pluggable) interface.
─ Index ─ 2. Products overview
15
iRTU, iGW & iRTUe Series User Manual
The iRTU units are also available with built-in 4G/3G/GSM/GPRS modem for wireless connection (iRTUM0, iRTU-M1 and iRTU-M2 models):
Equipped with 4G(LTE)/3G/GSM/GPRS built-in modem, with dual SIM card support: o iRTU-M0: GPRS modem. o iRTU-M1: 3G modem. o iRTU-M2: 4G (LTE) modem. (3) 2.5 kVrms isolated serial ports with TX/RX LED indicators: o (2) Basic RS232/RS422/RS485 serial ports, software configurable (COM2 & COM3 ports). o (1) RS422/RS485 serial port, software configurable (EXP422 port), for connection to iRTUe I/O expansion units (refer to section 12). (1) Ethernet 10/100BaseTX port (RJ45 connector). (1) USB port. (1) MGMT port (MiniUSB connector). (1) MicroSD internal slot for data storage.
The iRTU series products have different digital and analog signal I/O options available, allowing the units to be adapted to the requirements of each facility. iRTU units include an internal I/O card. Available internal I/O boards are the following:
D1: 24 digital inputs. iRTU models with D1 internal card: iRTU-B0D1, iRTU-S3D1, iRTU-M0D1, iRTUM1D1 and iRTU-M2D1. C1: 8 digital inputs, 4 relay outputs and 2 DC current analog inputs. iRTU models with C1 internal card: iRTU-B0C1, iRTU-S3C1, iRTU-M0C1, iRTU-M1C1 and iRTU-M2C1. Other options available upon request.
I/O capacity may be expanded externally by using iRTUe units. These iRTUe devices can be connected to the iRTU through the EXP422 port, each device providing up to two additional I/O cards. iRTU series products support the connection of up to 7 iRTUe units per EXP422 port. If more than 7 iRTUe devices are to be used, it is possible to use another serial port of the iRTU unit configured as RS422 to connect the additional iRTUe modules (refer to section 12.1 for EXP422 port layout), up to a maximum of 7 iRTUe units per iRTU serial port. Table 3 summarizes the iRTU available models with their communication capabilities and internal I/O options. iRTU Features
iRTU-B0
iRTU-S3
iRTU-M0/1/2
x
x
x
Communication protocols - Master/Slave IEC60870-5-101 - Master/Slave IEC60870-5-104 - Master/Slave DNP3.0 (serial, UDP, TCP) - Master/Slave Modbus RTU/TCP/UDP - Master IEC60870-5-103 - Master IEC60870-5-102 - Master DLMS - Master Profibus DP - Master Procome - Master IEC62056-21 - SNMP Agent/Manager - IEC61850 MMS Client/Server - IEC61850 GOOSE Publisher/Subscriber
─ Index ─ 2. Products overview
16
iRTU, iGW & iRTUe Series User Manual
iRTU Features
iRTU-B0
iRTU-S3
iRTU-M0/1/2
1 2 1
1 2 1
2 1
1
2 2
Communication ports Serial Ports: - Full RS232/422/485 - Basic RS232/422/485 - EXP422 (RS442/485) Ethernet ports: - Ethernet 10/100BaseTX port (RJ45 connector) - Redundant Ethernet 100BaseFX ports (ST, SC or SFP)
1
4G(LTE)/3G/GSM/GPRS built-in modem: x - Built-in dual-SIM 4G/3G/GSM/GPRS modem
M0: GPRS, M1: 3G, M2: 4G (LTE)
USB ports: - USB port (USB A connector) - MGMT port (miniUSB connector)
1 1
1 1
1 1
x
x
(iRTU-B0C1)
(iRTU-S3C1)
(iRTU-M0C1, iRTU-M1C1, iRTU-M2C1)
x
x
(iRTU-B0D1)
(iRTU-S3D1)
I/O configuration: available internal I/O modules x C1: 8DI + 2AI (0-20 mA) + 4 relay outputs
x D1: 24DI
(iRTU-M0D1, iRTU-M1D1, iRTU-M2D1)
Table 3 – iRTU units: available models and configurations
─ Index ─ 2. Products overview
17
iRTU, iGW & iRTUe Series User Manual
2.2. iGW Series: versatile communication gateways for electrical facilities The iGW units are specialized communication units for electrical facilities that allow data conversion between different protocols. Data from multiple devices (meters, protection relays, and other IEDs) may be acquired using field protocols (e.g.: IEC60870-5-101/102/103/104, IEC61850, DNP3.0, DLMS, Modbus, Procome, etc.), processed and transferred to one or multiple Control Centers using protocols such as IEC60870-5104/101, IEC61850, DNP3.0, and Modbus RTU/TCP.
iGW units provide the same communication capabilities, features and technical specifications than the iRTU units. The only difference between iRTU and iGW units is the I/O capability for direct acquisition: iGW units have no internal I/O board. Anyway, if required, iGW units can be connected to external iRTUe units (2.3) in order to provide them with I/O capabilities.
2.2.1.
Product main features
Product main features are summarized below:
General: o From meter data concentration to protocol conversion, iGW can act in any kind of control or automation system, especially in generation plants or high voltage substations, using any kind of communication protocol and media. o Availability of multiple communication options including serial ports, embedded Ethernet switches, and built-in 4G, 3G, GPRS or PSTN modems. o CPU characteristics: ARM9 @ 400MHz, with 128MB NAND Flash and 64MB SDRAM. o Real time processing with 1ms accuracy. o High accuracy real time clock with 1.5ppm drift. o Complies with IEC61850-3 EMC.
Configuration and maintenance: o Easy configuration and maintenance by using iGrid T&D’s free iConf tool. o Possibility of local and remote maintenance connection, using USB or Ethernet ports. o Availability of command line console where the packets exchange is displayed in real time for all available protocols, and where the user can simulate, consult and act over the product behavior.
iGW software application (iGComms): o Time synchronization options: SNTP (client and server), IEC60870-5-101, IEC60870-5-102, IEC60870-5-103, IEC60870-5-104, DNP3.0, DLMS, Procome and Profibus DP. o Definition of arithmetic, logical and relational operations, and mathematical functions using LUA (Lua 5.2, http://www.lua.org/) as programming language, via iConf tool. o IEC61131-3 automation: logic and PLC programming. o iGW models come with a full range of protocols including IEC60870-5-101 (master and slave), IEC60870-5-102 (master), IEC60870-5-103 (master), IEC60870-5-104 (master and slave), IEC61850 MMS client/server, IEC61850 GOOSE publisher/subscriber, Modbus RTU/TCP/UDP (master and slave), DNP3.0 serial/TCP (master and slave), DLMS (master), IEC62056-21 (master), Profibus DP (master) and Procome (master), in order to ensure the communication with new and legacy IEDs and SCADA master stations. o Redundancy: iGW units can be deployed on a hot-standby configuration, and include redundant power supply. ─ Index ─
2. Products overview
18
iRTU, iGW & iRTUe Series User Manual
S3 Series includes IEEE 802.1d RSTP (Rapid Spanning Tree Protocol).
Device Features: o Two options of power supply: Wide range power supply: 32 - 250Vdc / 80 - 250Vac (2.5kVrms isolation). 24 Vdc power supply: 19.5-60Vdc (2.5kVrms isolation). o EMC type test: IEC 60950-1, IEC 60255-5:2000, EC 60255-22:2000, EN 55022, IEC 61000-64, IEC 61000-6-5, IEC 61000-4-2, IEC 61000-4-3, IEC 61000-4-4, IEC 61000-4-5, IEC 610004-6, IEC 61000-4-8, IEC 61000-4-9, IEC 61000-4-10, IEC 61000-4-12, IEC 61000-4-16, IEC 61000-4-17, IEC 61000-4-18, IEC 61000-4-29. o Environmental: Operating temperature: -25ºC to +70ºC. IEC 60068-2-1, IEC 60068-2-2, IEC 60068-2-3, IEC 60068-2-14, IEC 60068-2-30, IEC 60068-2-38. o Vibration & Shock test: IEC 60068-2-6, IEC 60068-2-7. o Physical: External dimensions: 173 x 137 x 78.4 (mm). Rail mounting.
2.2.2.
Product models
This section will describe the available iGW models and options. The basic communication configuration for iGW units (model iGW-B0) is as follows:
(4) serial ports (2.5 kVrms isolation) with TX/RX LED indicators: o (1) Full RS232/RS422/RS485 serial port, software configurable (COM1 port). o (2) Basic RS232/RS422/RS485 serial ports, software configurable (COM2 & COM3 ports). o (1) RS422/RS485 serial port, software configurable (EXP422 port), for connection to iRTUe I/O expansion units (refer to section 12). (1) 10/100BaseTx Ethernet port (RJ45 connector). (1) USB port to connect peripheral devices (e.g. USB drives). (1) MGMT port (MiniUSB connector) to connect to a PC for local maintenance. (1) MicroSD internal slot for data storage.
iGW-B1 model is the lite version of the iGW-B0 model. iGW-B1 units are equipped with:
(2) serial ports (2.5 kVrms isolation) with TX/RX LED indicators: o (1) Full RS232/RS422/RS485 serial port, software configurable (COM1 port). o (1) Basic RS232/RS422/RS485 serial port, software configurable (COM2 port). (1) 10/100BaseTx Ethernet port (RJ45 connector). (1) USB port. (1) MGMT port (MiniUSB connector). (1) MicroSD internal slot for data storage.
The iGW-B0 basic configuration may be expanded by adding different communication options. As an example, iGW-S3 units include a S3 module (switch module) with the following characteristics:
Equipped with embedded Ethernet switch. Serial ports: same as iGW-B0. (2) Ethernet 10/100BaseTX ports (RJ45 connector). (2) Redundant 100BaseFX Ethernet ports. Available interfaces: optical interface with ST or SC connectors, or SFP interface. (1) USB port. (1) MGMT port (MiniUSB connector). ─ Index ─
2. Products overview
19
iRTU, iGW & iRTUe Series User Manual
(1) MicroSD internal slot for data storage.
The redundant Ethernet ports of the S3 modules are available with the following interfaces:
Optical interface with SC or ST connectors, multimode fiber (62.5/125 µm and 50/125 µm) and 1300 nm wavelength. SFP (Small Form-factor Pluggable) interface.
The iGW units are also available with built-in 4G/3G/GSM/GPRS modem for wireless connection (iGWM0, iGW-M1 and iGW-M2 models):
Equipped with 4G(LTE)/3G/GSM/GPRS built-in modem, with dual SIM card support: o iGW-M0: GPRS modem. o iGW-M1: 3G modem. o iGW-M2: 4G (LTE) modem. (3) 2.5 kVrms isolated serial ports with TX/RX LED indicators: o (2) Basic RS232/RS422/RS485 serial ports, software configurable (COM2 & COM3 ports). o (1) RS422/RS485 serial port, software configurable (EXP422 port), for connection to iRTUe I/O expansion units (refer to section 12). (1) Ethernet 10/100BaseTX port (RJ45 connector). (1) USB port. (1) MGMT port (MiniUSB connector). (1) MicroSD internal slot for data storage.
iGW units are not equipped with internal I/O modules but they can be connected to external iRTUe units in order to provide I/O capabilities. The EXP422 port shall be used to connect the iGW units to the I/O external modules. iGW units support the connection of up to 7 iRTUe devices per EXP422 port. If more than 7 iRTUe modules are to be used, it is possible to use another serial port of the iGW unit configured as RS422 to connect the additional iRTUe units (refer to section 12.1 for EXP422 port layout), up to a maximum of 7 iRTUe units per iGW serial port. Table 4 summarizes the iGW available models with their communication capabilities. iGW Features
iGW-B0
iGW-B1
iGW-S3
iGW-M0/1/2
x
x
x
x
1 2 1
1 1
1 2 1
2 1
Communication protocols - Master/Slave IEC60870-5-101 - Master/Slave IEC60870-5-104 - Master/Slave DNP3.0 (serial, UDP, TCP) - Master/Slave Modbus RTU/TCP/UDP - Master IEC60870-5-103 - Master IEC60870-5-102 - Master DLMS - Master Profibus DP - Master Procome - Master IEC62056-21 - SNMP Agent/Manager - IEC61850 MMS Client/Server - IEC61850 GOOSE Publisher/Subscriber Communication ports Serial Ports: - Full RS232/422/485 - Basic RS232/422/485 - EXP422 (RS442/485)
─ Index ─ 2. Products overview
20
iRTU, iGW & iRTUe Series User Manual
iGW Features
iGW-B0
iGW-B1
iGW-S3
iGW-M0/1/2
1
1
2 2
1
Ethernet ports: - Ethernet 10/100BaseTX port (RJ45 connector) - Redundant Ethernet 100BaseFX ports (ST, SC or SFP) 4G/3G/GPRS built-in modem: x M0: GPRS, M1: 3G, M2: 4G (LTE)
- Built-in dual-SIM 4G/3G/GSM/GPRS modem USB ports: - USB port (USB A connector) - MGMT port (miniUSB connector)
1 1
1 1
1 1
1 1
Table 4 – iGW units: available models and configurations
─ Index ─ 2. Products overview
21
iRTU, iGW & iRTUe Series User Manual
2.3. iRTUe Series: I/O expansion modules for iRTU & iGW units iRTUe devices are auxiliary equipment for the iRTU and iGW units that allow to expand their acquisition and command capabilities in order to suit the requirements of each application and facility. iRTUe units are equipped with one serial port (EXP422 port) for communication with iRTU & iGW units and other iRTUe I/O modules via RS422 straight cable.
2.3.1.
Product main features
Product main features are summarized below:
General: o Auxiliary equipment that allows the iRTU and iGW units to expand their I/O capabilities. o Communication with iRTU and iGW devices: Serial RS422 port to connect to iRTU & iGW devices (EXP422 port) using Modbus RTU protocol. Supports buffering of time tagged digital events. Up to 7 iRTUe devices can be connected per RS422 bus. o CPU: 32 bits microcontroller @ 40MHz.
I/O specifications: o Digital inputs: Digital inputs are grouped into isolated blocks of 8 inputs + the common terminal. Rated input voltage: 24 Vdc, 48 Vdc, 110Vdc, 125 Vdc or 220Vdc (other options upon request). 2.5 kVrms isolation. Activation and deactivation voltages: ON (activation) voltage: Vi > 85%Vn (Vn = nominal voltage) OFF (deactivation) voltage: Vi < 60%Vn (Vn = nominal voltage) Other levels upon request. 1 millisecond accuracy. Configurable debounce filter. Possibility of configuring each digital input as 16-bit counter input.
o
Analog inputs: Analog inputs are grouped in blocks of 2 independent inputs. 2.5 kVrms isolation. Range: ±20 mA range (other options upon request). Precision better than 0.15%.
o
Relay outputs: Dry contact electromechanical relay. Outputs are independent, but grouped in blocks of 2 relays. Isolation between solenoid and contacts: 6kVrms. Breaking capacity: 8A @ 220Vac. 8/0.3/0.12A @ 30/110/220Vdc.
Device Features: o Two options of power supply: Wide range power supply: 32 - 250Vdc / 80 - 250Vac (2.5kVrms isolation) 24 Vdc power supply: 19.5-60Vdc (2.5kVrms isolation) o EMC type test: IEC 60950-1, IEC 60255-5:2000, EC 60255-22:2000, EN 55022, IEC 61000-64, IEC 61000-6-5, IEC 61000-4-2, IEC 61000-4-3, IEC 61000-4-4, IEC 61000-4-5, IEC 61000─ Index ─
2. Products overview
22
iRTU, iGW & iRTUe Series User Manual
o
o o
2.3.2.
4-6, IEC 61000-4-8, IEC 61000-4-9, IEC 61000-4-10, IEC 61000-4-12, IEC 61000-4-16, IEC 61000-4-17, IEC 61000-4-18, IEC 61000-4-29. Environmental: Operating temperature : -25ºC to +70ºC IEC 60068-2-1, IEC 60068-2-2, IEC 60068-2-3, IEC 60068-2-14, IEC 60068-2-30, IEC 60068-2-38 Vibration & Shock test: IEC 60068-2-6, IEC 60068-2-7. Physical: External dimensions: 173 x 137 x 78.4 (mm). Rail mounting.
Product models
Each iRTUe auxiliary unit includes up to two I/O cards. Table 5 details the available iRTUe models and their configurations. iRTUe model
I/O Configuration [*]
iRTUe-D1D1 iRTUe-D1R1 iRTUe-D1A1 iRTUe-A1A1 iRTUe-A1R1 iRTUe-R1
48 Digital Inputs 24 Digital Inputs + 8 Relay Outputs 24 Digital Inputs + 8 Analog Inputs (0-20mA) 16 Analog Inputs 8 Analog Inputs + 8 Relay Outputs 8 Relay Outputs Table 5 – iRTUe units: available models and configurations
[*] Other configurations upon request. Contact iGrid T&D ([email protected]) for further information.
─ Index ─ 2. Products overview
23
iRTU, iGW & iRTUe Series User Manual
3. Power supply specifications iRTU, iGW and iRTUe series products offer the following power supply characteristics:
Power supply options: o 24Vdc power supply: 19.5-60Vdc. o Wide range power supply: 32 - 250Vdc, 80 - 250Vac. Reversible polarity. 2.5 kVrms isolation. Power consumption: o iRTU-B0, iGW-B0 and iGW-B1 series: below 3W. o iRTU-M0, iRTU-M1, iRTU-M2, iGW-M0, iGW-M1 and iGW-M2 series: below 6W. o iRTU-S3 and iGW-S3 series: below 5W.
Figure 5 shows how to connect the DC supply:
Vdc+
Vdc-
GND
Figure 5 – Power supply connection
To connect the supply, a Phoenix Contact connector, model MSTB 2,5/ 3-ST-5,08 (code no.: 1757022), should be used.
─ Index ─ 3. Power supply specifications
24
iRTU, iGW & iRTUe Series User Manual
4. I/O modules technical characteristics Analog and digital inputs/outputs for iRTU and iRTUe units offer the following technical characteristics: Digital inputs:
Rated input voltage options: 24Vdc, 48Vdc, 110Vdc, 125Vdc or 220Vdc (other options upon request). Activation/Deactivation voltage: o Activation voltage (ON voltage): >85% of rated voltage. o Deactivation voltage (OFF voltage): Update license option of the iConf’s iRTU menu. Refer to section 14.9 for further details.
14.6.2. Using a USB drive These are the steps to follow to upload/update the license of the iRTU/iGW unit using a USB flash drive: 1) Connect the USB flash drive to a PC. 2) Create a directory named UPLOAD_BIN in the root directory of the USB drive. If the directory is already present, its contents should be deleted. 3) Copy the license file to be uploaded to the UPLOAD_BIN directory in the USB drive. 4) Connect the USB drive to the USB port in the iRTU/iGW unit. 5) Open the maintenance console (section 15) and reload the iRTU/iGW unit with the reload command. When the iRTU/iGW unit initializes, the new license is loaded. 6) Once the license has been correctly updated, the USB flash drive may be removed.
If an UPLOAD_CONF directory is present in the root directory of the USB drive (section 14.4.2), it is recommended to delete the directory or its contents. Otherwise, not only the license will load, but also the configuration (.ccx files) located in the UPLOAD_CONF directory of the USB drive, which will replace the current configuration of the unit.
If the configuration upload and the firmware & license update of the iRTU/iGW unit are to be performed simultaneously, an UPLOAD_CONF directory (containing the configuration .ccx files to be uploaded; refer to section 14.4.2) and an UPLOAD_BIN directory (containing the new firmware and the license) should be created in the root directory of the USB drive.
14.6.3. Using FTP These are the steps to follow to update the license of the iRTU/iGW unit using FTP: 1) From the FTP manager, connect to the appropriate address (10.10.10.100 for USB port connection; IP address of the iRTU/iGW unit for Ethernet connection) entering user name and password as discussed in section 14.1.3 (user = isupport, password = irtusupport). 2) Access the BIN directory in the iRTU/iGW unit.
─ Index ─ 14. Configuration and maintenance of the iRTU and iGW units
91
iRTU, iGW & iRTUe Series User Manual
3) Replace the existing license file in the BIN directory of the iRTU/iGW unit with the one supplied by iGrid T&D. 4) Open the maintenance console (section 15) and reboot the iRTU/iGW unit with the reload command. When the iRTU/iGW unit initializes, the new license will be loaded.
14.7. Updating timezones This operation consists of updating the internal timezones folder of the iRTU/iGW units which includes the settings for all available world time zones. Timezones folder content should be updated only upon iGrid T&D instructions. This may be accomplished in two different ways:
iConf tool (recommended) Using FTP (through USB or Ethernet)
14.7.1. Using iConf tool Select the Advanced -> Update timezones option of the iConf’s iRTU menu. Refer to section 14.9 for further details.
14.7.2. Using FTP These are the steps to follow to update the timezones folder of the iRTU/iGW unit using FTP: 1) From the FTP manager, connect to the appropriate address (10.10.10.100 for USB port connection; IP address of the iRTU/iGW unit for Ethernet connection) entering user name and password as discussed in section 14.1.3 (user = isupport, password = irtusupport). 2) Access the BIN directory in the iRTU/iGW unit. 3) Replace the existing timezones folder in the BIN directory of the iRTU/iGW unit with the one supplied by iGrid T&D. 4) Open the maintenance console (section 15) and reboot the iRTU/iGW unit with the reload command. When the iRTU/iGW unit initializes, the new timezones will be loaded.
14.8. Downloading the configuration The configuration download process from the iRTU/iGW unit may be accomplished in three different ways:
iConf tool (recommended) Using a USB flash drive (pen drive) Using FTP (through USB or Ethernet)
14.8.1. Using iConf tool There are two options available by using iConf tool:
Load device configuration option of the iConf’s iRTU menu: allows user to import and open the current configuration of the connected iRTU/iGW unit. Refer to section 14.9 for further details. Backup device configuration option of the iConf’s iRTU menu: this option allows backing-up the current configuration of the iRTU/iGW device, to which iConf is currently connected. Refer to section 14.9 for further details.
─ Index ─ 14. Configuration and maintenance of the iRTU and iGW units
92
iRTU, iGW & iRTUe Series User Manual
14.8.2. Using a USB drive These are the steps to follow to download a configuration from iRTU/iGW units with iAppManager versions 3.0.0 and later (ANNEX I) using a USB flash drive: 1) 2) 3) 4)
Connect the USB flash drive to a PC. Create a directory named DOWNLOAD_CONF in the root directory of the USB drive. Connect the USB drive to the USB port in the iRTU/iGW unit. The iRTU/iGW detects the USB drive automatically and saves the contents of the CONF directory to the DOWNLOAD_CONF directory that has been created. The front panel LED STATE blinks in red during the writing operation. 5) Once the configuration is downloaded, remove the USB drive from the iRTU/iGW unit and connect it to a USB port in the PC. 6) The configuration of the iRTU/iGW unit is now in the DOWNLOAD_CONF directory of the USB drive. For iRTU/iGW units with iAppManager versions prior to 3.0.0 the steps to follow to download the configuration are described below: 1) 1) 2) 3)
Connect the USB flash drive to a PC. Create a directory named DOWNLOAD_CONF in the root directory of the USB drive. Connect the USB drive to the USB port in the iRTU/iGW unit. Then, shutdown the iRTU/iGW unit. During start up, the iRTU/iGW detects the USB drive automatically and saves the contents of the CONF directory to the DOWNLOAD_CONF directory that has been created. 4) Once the configuration is downloaded, remove the USB drive from the iRTU/iGW unit and connect it to a USB port in the PC. 5) The configuration of the iRTU/iGW unit is now in the DOWNLOAD_CONF directory of the USB drive. This procedure not only downloads the configuration (.ccx files) of the iRTU/iGW unit, but also the rest of files saved in the CONF directory. If the contents of the BIN folder is to be downloaded, the above steps should be followed, but creating a DOWNLOAD_BIN directory instead of a DOWNLOAD_CONF directory in the root directory of the USB drive. The .bin files (firmware file, license file, etc.), timezones folder, etc. will be stored in the DOWNLOAD_BIN directory.
14.8.3. Using FTP The configuration of an iRTU/iGW unit may also be downloaded using FTP. These are the steps to follow: 1) From the FTP manager, connect to the appropriate address (10.10.10.100 for USB port connection; IP address of the iRTU/iGW unit for Ethernet connection) entering user name and password as discussed in section 14.1.3 (user = isupport, password = irtusupport). 2) Access the CONF directory in the iRTU/iGW unit and copy its contents (.ccx configuration files) to the PC. The firmware (iGRTU.bin or iGComms.bin file), license files, and timezones folder may also be downloaded from the BIN directory.
─ Index ─ 14. Configuration and maintenance of the iRTU and iGW units
93
iRTU, iGW & iRTUe Series User Manual
14.9. Management of the iRTU & iGW units via iConf tool The iConf’s iRTU menu should be used for maintenance and setup of iRTU & iGW units.
Figure 73 – iConf’s iRTU menu options
iRTU menu includes the following options:
14.9.1. Connect option This option allows user to connect to the iRTU/iGW unit via USB or Ethernet ports.
For USB connection: select “USB” from the Connect to iRTU window. For Ethernet connection: enter the IP address of the iRTU/iGW unit in the Connect to iRTU dialog.
Figure 74 – Connect option of iConf’s iRTU menu
Figure 75 – Connecting to iRTU/iGW via USB port
Figure 76 – Connecting to iRTU/iGW via Ethernet connection
─ Index ─ 14. Configuration and maintenance of the iRTU and iGW units
94
iRTU, iGW & iRTUe Series User Manual
The default IP address of the iRTU/iGW units is: 192.168.1.100 If you are connecting for the first time to an iRTU/iGW unit trough Ethernet port, use the default IP address in order to connect to and manage it. Afterwards, change the default IP address setting through the iConf tool (refer to iConf User Manual) or through the iRTU/iGW’s iDevSetup menu (section 15.4.2.2), as required to suit the system’s network configuration. If the default IP address is changed, the new user defined IP address should be used for communication through Ethernet.
iConf uses ftp and telnet in order to upload/download data (configuration, firmware, license, etc.) and to access to the maintenance console, respectively. Default ports are as follows:
ftp: 21 telnet: 23
User can change the default ports by clicking on the Advanced button of the Connect to iRTU dialog:
Figure 77 – Advanced option of the Connect to iRTU dialog allows the user to change the default telnet and ftp ports used to connect to the iRTU/iGW unit.
After choosing “USB” option or setting the iRTU/iGW IP address, click on Connect button. If iConf connects to the iRTU/iGW unit successfully, iConf will display a message at the bottom of the main window as depicted in Figure 78:
Figure 78 – The message and image at the bottom of the iConf window shows that the connection with the iRTU/iGW unit with IP address = 172.25.1.25 is successful
─ Index ─ 14. Configuration and maintenance of the iRTU and iGW units
95
iRTU, iGW & iRTUe Series User Manual
14.9.2. Load device configuration option This option allows users to import the current configuration of an iRTU/iGW unit so that it can be verified and edited by the user using the iConf application.
14.9.3. Apply configuration to device option Allows user to apply the iConf’s system configuration to the connected iRTU/iGW unit. The Apply configuration to device option performs the following tasks automatically:
Saves the configuration. Validates and generates the configuration files. Uploads the new configuration to the iRTU/iGW device. Performs an automatic reload in the iRTU/iGW unit, for the new configuration to take effect.
The steps to apply the iConf configuration to an iRTU/iGW device are as follow: 1) Connect to the iRTU/iGW as described in section 14.9.1. 2) Select the option Apply configuration to device of the iRTU menu 3) A message asking for user’s confirmation will be displayed (Figure 79). Click Yes.
Figure 79 – iConf asks user for confirmation on the operation
4) The Apply configuration to device operation is password protected. Please, enter password “irtufirmware” in the dialog of Figure 80.
Figure 80 – Most iRTU menu operations are password protected. Password for all these operations is “irtufirmware”
5) The configuration loading process will start (see Figure 81).
─ Index ─ 14. Configuration and maintenance of the iRTU and iGW units
96
iRTU, iGW & iRTUe Series User Manual
Figure 81 – Loading configuration to iRTU/iGW unit
6) If the configuration loading process is successful the message depicted in Figure 82 will be displayed.
Figure 82 – The loading process is successful
7) Next step is to reload the iRTU/iGW unit. This can be accomplished by two ways: a) Automatically through the message of Figure 82, by clicking on Yes button. b) Opening the iRTU/iGW console (refer to section 14.9.5) and entering the command reload. The new configuration will be loaded during iRTU/iGW initialization after reload.
14.9.4. Backup device configuration option This option allows backing-up the current configuration of the iRTU/iGW device, to which iConf is currently connected. Configuration files (.ccx files) will be saved in the directory chosen by the user.
14.9.5. Open console option Opens a command line interface (console) for iRTU/iGW maintenance and supervision tasks. The maintenance console displays the communication traces of the iRTU/iGW devices. That is, it shows the data flow between the unit and the devices (IEDs and/or master stations), and also information regarding the unit’s current condition. Refer to section 15 for further information on iRTU/iGW maintenance console options and commands.
iConf stores the console traces automatically in an iRTU.log file located in the iConf folder. For further information about the console traces, options and commands, please refer to iGComms command line console manual.
─ Index ─ 14. Configuration and maintenance of the iRTU and iGW units
97
iRTU, iGW & iRTUe Series User Manual
14.9.6. Advanced options The following advanced options are available in the iRTU menu:
Figure 83 – iRTU menu: Advanced options
Update timezones This option consists of updating the internal timezones folder of the iRTU/iGW units which includes the settings for all available world time zones. Timezones folder content should be updated only upon iGrid T&D instructions. The steps to update the timezones folder are as follow: 1) Connect to the iRTU/iGW unit as described in section 14.9.1. 2) Select the option Advanced -> Update timezones of the iRTU menu 3) The Update timezones operation is password protected. Please, enter password “irtufirmware” in the dialog of Figure 80. 4) Select the folder containing the new timezones folder provided by iGrid T&D. 5) The timezones loading process will start (see Figure 84).
Figure 84 – Loading timezones to iRTU/iGW unit
6) If the loading process is successful the message depicted in Figure 82 will be displayed. 7) Next step is to reload the iRTU/iGW unit. This can be accomplished by two ways: a) Automatically through the message of Figure 82, by clicking on Yes button. b) Opening the iRTU/iGW console (refer to section 14.9.5) and entering the command reload. The new timezones folder will be loaded during iRTU/iGW initialization after reload. Update license This option must be used when the user needs to update the license of the iRTU/iGW unit. The steps to update the license are as follow: 1) Connect to the iRTU/iGW unit as described in section 14.9.1. 2) Select the option Advanced -> Update license of the iRTU menu
─ Index ─ 14. Configuration and maintenance of the iRTU and iGW units
98
iRTU, iGW & iRTUe Series User Manual
3) The Update license operation is password protected. Please, enter password “irtufirmware” in the dialog of Figure 80. 4) Select the folder containing the license file provided by iGrid T&D. 5) The loading process will start (see Figure 85).
Figure 85 – Loading license file to iRTU/iGW unit
6) If the loading process is successful the message depicted in Figure 82 will be displayed. 7) Next step is to reload the iRTU/iGW unit. This can be accomplished by two ways: a) Automatically through the message of Figure 82, by clicking on Yes button. b) Opening the iRTU/iGW console (refer to section 14.9.5) and entering the command reload. The new license will be loaded during iRTU/iGW initialization after reset.
14.9.7. Update firmware option This option must be used when the user needs to update the firmware of the iRTU/iGW unit. The steps to update the firmware of an iRTU/iGW device are as follow: 1) Connect to the iRTU/iGW as described in section 14.9.1. 2) Select the option Update firmware of the iRTU menu 3) The Update firmware operation is password protected. Please, enter password “irtufirmware” in the dialog of Figure 80. 4) Select the folder containing the new firmware (iGRTU.bin or iGComms.bin file) provided by iGrid T&D. 5) The firmware loading process will start (see Figure 86).
Figure 86 – Loading firmware to iRTU/iGW unit
6) If the firmware loading process is successful the message depicted in Figure 82 will be displayed. 7) Next step is to shutdown the iRTU/iGW unit. This can be done by two ways: a) Automatically through the message of Figure 82, by clicking on Yes button. b) Opening the iRTU/iGW console (refer to section 14.9.5) and entering the command shutdown. The new firmware will be loaded during iRTU/iGW initialization after reset.
─ Index ─ 14. Configuration and maintenance of the iRTU and iGW units
99
iRTU, iGW & iRTUe Series User Manual
15. Maintenance console In order to support communication troubleshooting, the iRTU and iGW debugging console may be used to show data flow between the unit and the IEDs and Control Centers (master stations) of the system in real time, in addition to information on current unit condition. Users are also able to simulate, consult or act over the iRTU & iGW units through the command line console.
15.1. Accessing the maintenance console The maintenance console access can be accomplished in two different ways:
iConf tool (recommended): iConf includes a telnet client that allows accessing the iRTU/iGW console. Select the Open console option of the iConf’s iRTU menu in order to open the iRTU/iGW’s console. Refer to section 14.9.5 for further details.
Using user’s telnet software (Hyperterminal, PuTTY, or similar). Two channels may be used: the MGMT port (USB maintenance port) or a connection to the Ethernet port: o MGMT port: use the following IP address and port: Host Name (or IP address): 10.10.10.100 Port: 23 o If the Ethernet connection is used: Host Name (or IP address): IP address of the device Port: 23
15.2. Maintenance console password The iRTU/iGW command line console is password protected. User must enter “irtutrace” password to access to the communication traces and commands.
Figure 87 – iRTU/iGW console is password protected. Use password “irtutrace” to monitor communication traces and to be able to use available commands.
15.3. Maintenance console sections and commands In this section we will describe the available sections and commands of the iRTU/iGW’s command line console.
15.3.1. Basic definitions
Trace: information line displayed automatically on the console. The information is generated by the iRTU/iGW application to display some kind of event, from communication packets to alarms. The degree of information detail is defined by the trace level. iRTU & iGW traces are automatically stored by iConf in the file iConf\iRTU.log.
Trace level: configurable between 0 and 20, it allows the user to choose the detail level (and quantity) of information displayed on the maintenance console (see section 15.3.2.5)
─ Index ─ 15. Maintenance console
100
iRTU, iGW & iRTUe Series User Manual
Sections: concept similar to directories on a file system. It allows users to navigate through the command structure of the maintenance console, to gain access to different groups of commands. E.g. ip section gives information about the TCP/IP stack, m61850 section about the IEC61850 client, etc. Available sections are listed below: o o o o o o o o o o o o o o o
os ports procedure term pcap ip EXP422 m102 m104 mDLMS sim rdcy s61850 m61850 NTP
Command syntax: all commands are composed of two different groups of orders: o o
Mandatory fields: fields which are strictly necessary for the command to be executed. They are represented between “< >”. Optional fields: fields and parameters which add functionalities to the command but are not strictly necessary for its execution. They are represented by “[ ]”.
Navigation through sections: in order to change of section, the cd command must be used, as described in section 15.3.2.4.
Help: the user can ask for help at any moment by using the help command: o o o
15.3.2.
help: shows the available commands on the “current section”. help : shows the available commands on the section (e.g.: help ip). ?: same as above.
Main section commands
Main section (root) contains global commands that are available from all sections.
─ Index ─ 15. Maintenance console
101
iRTU, iGW & iRTUe Series User Manual
Figure 88 – Main section available commands
help and ? commands Lists the available commands on current section (folder). Syntax: help or ? They can also be used to display the available commands of any other sections. Syntax: help [section] ? [section] [section] ? These commands can be called from any section. E.g. help ip: lists the available commands inside the ip section (Figure 89)
Figure 89 – Example of usage of help and ? commands
The ? command can also be used to get further information on a command. Syntax: ? In this case, the user must be inside the command’s respective section.
─ Index ─ 15. Maintenance console
102
iRTU, iGW & iRTUe Series User Manual
E.g. ipconfig ?: this command displays information of the ipconfig command. User must have changed to the ip section before entering this command (Figure 90) by using the cd ip command (section 15.3.4).
Figure 90 – Example of usage of the ? command
It is also possible to get information on a command without needing to be inside the command’s respective section. Syntax: ? E.g. ip ipconfig ?: this command displays information of the ipconfig command, which is inside the ip section, from the current section:
Figure 91 – Example of usage of the ? command
sections command Lists available sections.
Figure 92 – List of available sections
─ Index ─ 15. Maintenance console
103
iRTU, iGW & iRTUe Series User Manual
rdcy section will be available only when working with iRTU/iGW in redundant configuration. m61850 and s61850 sections will be available only when the iRTU/iGW configuration includes communication with IEC61850 server(s) and/or an IEC61850 client, respectively. NTP section will be available only when the iRTU/iGW configuration includes synchronization with NTP server/s. PLC section will be available only when iRTU/&iGW unit includes a PLC program in its configuration.
continue and c commands These commands resume trace display with the same detail level. Refer to section 15.3.2.5 for further details. cd command This command changes the current section to another section. Syntax: cd E.g. cd ip: this command changes the current section to the ip section (Figure 93).
Figure 93 – Example of usage of cd command
In order to return to the main section (root), type the following command: cd..
Figure 94 – The cd.. command returns to the main section
trace command This command allows for real time monitoring of the traces generated by the system. Syntax for the trace command is as follows: trace [level|-l|-t| task < list | > ]
─ Index ─ 15. Maintenance console
104
iRTU, iGW & iRTUe Series User Manual
Figure 95 – trace command syntax
where:
trace [level]: is the value of the detail level of the traces. This value defines the maximum allowed trace level when generating traces (i.e., traces with trace level equal or below that value will be displayed). The more higher, the more detail. E.g. trace 15: sets the global trace level to 15 (see example of Figure 96)
Figure 96 – Example of trace [level] command (trace 15)
Example of Figure 96 shows traces of an iRTU unit that is communicating with: o o o
Internal I/O module: the communication with the internal I/O modules is done via Modbus protocol and COM4 port. Modbus TCP IED: using VP1 virtual port. IEC104 master station.
First column of the traces shows the task identifier, which in this example is as follows:
─ Index ─ 15. Maintenance console
105
iRTU, iGW & iRTUe Series User Manual
o o o
Internal I/O module: task 17 Modbus TCP IED: task 19 IEC104 master station: task 15
Next column is the time stamp, with indication of the time and date. Third column shows information about the protocol and the port used to connect to the device: o o o
“mMBus.COM4”: Modbus master protocol and COM4 serial port are used to communicate with internal I/O module. “mMBus.VP1”: Modbus master protocol and virtual port VP1 are used to communicate with Modbus TCP IED. “s104.APCI”: IEC104 slave protocol used to communicate with an IEC104 master station.
Fourth column displays the RTU/IED address. In IEC104 case, the first “[1]” corresponds to the module identifier (section 15.3.2.10) and the second “[1]” corresponds to the common address. Fifth column shows the direction of the information: o o
“>>” symbol identifies outgoing messages (traces from iRTU to IED/master station) “ trace 0 Global trace level set to 0 iRTU> trace task COM2 15 task level of 'COM2' set to 15
fields support the use of wildcard characters: o o
“*”: matches zero or more characters. E.g. trace task TMW* 18: sets the task trace level to 18 for all tasks that begin with “TMW”. “?”: represents any individual character. E.g. trace task VP? 15: sets the task trace level to 15 for all tasks with name “VP” + an individual character.
trace task all : sets all the tasks’ trace level to . For example: o trace task all 0: all tasks stop tracing. o trace task all 18: all tasks’ trace level is set to “18”.
─ Index ─ 15. Maintenance console
107
iRTU, iGW & iRTUe Series User Manual
Examples of trace levels:
“trace 8”: displays the events when occur. “trace 15”: displays all the communication packets, on any protocol. “trace 20”: displays all the possible information. This is the level required to inform iGrid about a problem. It should only be used when a problem appears as it takes a lot of CPU.
After rebooting the iRTU/iGW units, the detail level of the trace display will be according to the default value (i.e. 6). To stop the display of traces on the console, press Enter. To resume the display of traces, command continue or c may be used (section 15.3.2.3). This command resumes trace display with the same detail level. ver command Displays iRTU/iGW firmware version.
Figure 99 – ver command
date command The date command recalls the local and UTC date and time of the unit (Figure 100).
Figure 100 – date command
This command also allows the user to set the system time and date (Figure 101) as follows: date [ ] where:
WI|SU: WInter (WI) or SUmmer (SU) time. Summer time is used in areas with DST (Daylight Saving Time). NIV|IV: NOT INVALID (NIV, i.e. valid) or INVALID (IV) date and time.
Figure 101 – Setting the date and time by using the date command
shutdown command This command shuts the system down (soft reset). The iDevSetup menu is displayed before restarting (Figure 102).
─ Index ─ 15. Maintenance console
108
iRTU, iGW & iRTUe Series User Manual
Figure 102 – shutdown command
If used in conjunction with the -h option, it performs a hard reset (shutdown –h).
Figure 103 – shutdown –h command: it forces a hardware reset
shutdown command options (Figure 102):
-h: forces a hardware reset. COR: forces a Cause Of Reset code. Reserved use. reload command
This command should be used to reload the configuration quickly. The iDevSetup menu is not displayed before the unit restarts.
Figure 104 – reload command
modules or mod command Displays status information of all loaded modules, that is, all IEDs, RTUs, and master stations or Control Centers included in the system configuration. Displayed fields are the following (Figure 105):
─ Index ─ 15. Maintenance console
109
iRTU, iGW & iRTUe Series User Manual
id: device identifier Name: device name Status: communication status (“ok” or “fail”) Class: communication protocol Address: device address and physical port
Figure 105 – modules or mod command
files command This command allows the user to display the iRTU/iGW’s file repository content in file transfer functionality. Contact iGrid T&D for further information on this functionality. Files are shown in absolute path.
Figure 106 – files command syntax
Syntax is as follows: files [-m] [-r] [-a] [FILES] Where:
FILES: this argument allows user to filter available folders and file names. Only files and folders that match this pattern will be listed. The FILES argument supports the use of wildcard characters: “*” (matches zero or more characters) and “?” (matches any individual character).
-r: recursive mode. Shows the recursive list of files from folders in absolute path.
-m: displays the following information (columns) for each file: o Flags: m: mount point d: directory r: read only s: system file h: hidden t: temporal v: volatile x: pending to be deleted A: being accessed S: being synchronized o State: dwPend: pending to be downloaded upPend: pending to be uploaded
─ Index ─ 15. Maintenance console
110
iRTU, iGW & iRTUe Series User Manual
o o o o
remDel: pending to be deleted from remote device dwInProg: download in progress upInProg: upload in progress dwQueued: queued to be downloaded upQueued: queued to be uploaded tranFail: last transfer failed notFound: file not found in remote device no_IED: file orphan. There is no connection to the IED notInRem: file not present in remote IED Ok: file is OK and up-to-date. Size and date are valid Name of the IED module that the file is related to. File size in bytes. File modification date. When protocol supports it, this is the file’s date in remote device. File name.
-a: displays all the available information (columns) for each file: o Flags: m: mount point d: directory r: read only s: system file h: hidden t: temporal v: volatile x: pending to be deleted A: being accessed S: being synchronized o State: dwPend: pending to be downloaded upPend: pending to be uploaded remDel: pending to be deleted from remote device dwInProg: download in progress upInProg: upload in progress dwQueued: queued to be downloaded upQueued: queued to be uploaded tranFail: last transfer failed notFound: file not found in remote device no_IED: file orphan. There is no connection to the IED notInRem: file not present in remote IED Ok: File OK and up-to-date. Size and date are valid o Update mode: local: File is in local file system. demand: File will be updated from IED before access it. per_sync: File is being synchronized periodically. o Remaining time to next synchronization. o Transferred bytes. o Code returned by last transfer (reserved use). o Name of the IED module that the file is related to. o File size in bytes. o File modification date. When protocol supports it, this is the file’s date in remote device. o File name.
─ Index ─ 15. Maintenance console
111
iRTU, iGW & iRTUe Series User Manual
Figure 107 – Example of usage of files command: files -r
Figure 108 – Example of usage of files command: files -m
Figure 109 – Example of usage of files command: files –r -m
Figure 110 – Example of usage of files command: files -a
─ Index ─ 15. Maintenance console
112
iRTU, iGW & iRTUe Series User Manual
Figure 111 – Example of usage of files command: files –r -a
versions command Lists the module versions used by the application, including the protocol stack versions.
Figure 112 – versions command
modon command Enables the communication with a module (i.e. device). Syntax is as follows: modon
─ Index ─ 15. Maintenance console
113
iRTU, iGW & iRTUe Series User Manual
Figure 113 – modon command syntax
The modon command is only available for master DLMS, master Procome, master IEC608705-102, master IEC60870-5-103, SQL client, and IEC61850 client protocols.
When the communication with a device is turned off, the modon command allows user to restart communication with the IED. modoff command Disables the communications with a module (i.e. IED). Syntax is as follows: modoff Where is the module identifier or device identifier (see section 15.3.2.10).
Figure 114 – modoff command syntax
The modoff command is only available for master DLMS, master Procome, master IEC608705-102, master IEC60870-5-103, SQL client, and IEC61850 client protocols.
The modoff command turns off communications with the given device as soon as possible. In certain cases it may be required to send an end of session before closing the communications. Once communications are disabled, all data points from the module (device) will get invalid. If iRTU/iGW unit is restarted when the modoff command is active, communications will be enabled again at start-up. info command Displays general system information, including firmware version, license code, model, iKernel version, serial number, date of configuration, configuration tool (i.e. iConf) version, system date, etc.
─ Index ─ 15. Maintenance console
114
iRTU, iGW & iRTUe Series User Manual
Figure 115 – info command in an iRTU unit
list command Lists current values/states of the system data points, filtering them by point type: digital inputs, analog inputs, digital outputs, analog outputs and counter inputs. Syntax for the list command is as follows: list [ | ] The arguments for the list command are described in next sections: list dv command
By entering the list dv command, the list of digital input points of the system will be displayed. Displayed fields/columns are the following:
TAG: digital input point identifier, as defined in the iRTU/iGW configuration files. Q: shows the quality of the digital input signal. For example, a signal with quality “!” means a signal with invalid quality. VALUE: shows the current state of the digital input point. TEXT: shows the text for that signal as defined in the system configuration.
─ Index ─ 15. Maintenance console
115
iRTU, iGW & iRTUe Series User Manual
Figure 116 - Example: list of digital input points (list dv command)
list mv command
The list mv command displays the list of measured values (analog inputs) in the system. Displayed fields are the following:
TAG: analog input point identifier, as defined in the system configuration files. Q: shows the quality of the measured value. For example, a point with quality “!” means a measured value with invalid quality. VALUE: shows the current measured value under the format defined in the system configuration. TEXT: shows the text for that point as defined in the system configuration.
Figure 117 – Example: list of analog input points (list mv command)
list cm command
The list cm command displays the list of commands (digital outputs) in the system. Displayed fields are the following:
TAG: digital output point identifier, as defined in the system configuration files. VALUE: current state of the command. TEXT: shows the text for that command as defined in the system configuration.
─ Index ─ 15. Maintenance console
116
iRTU, iGW & iRTUe Series User Manual
Figure 118 – Example: list of digital output points (list cm command)
list sp command
The list sp command displays the list of setpoints (analog outputs) in the system. Displayed fields are the following:
TAG: analog output point identifier, as defined in the system configuration files. VALUE: shows current setpoint value. TEXT: shows the text for that setpoint as defined in the system configuration.
Figure 119 – Example: list of analog output points (list sp command)
list cnt command
The list cnt command displays the list of counter input points in the system. Displayed fields are the following:
TAG: counter input point identifier, as defined in the system configuration files. Q: shows the quality of the counter point. VALUE: shows the current value of the counter. TEXT: shows the text for that counter as defined in the system configuration.
Figure 120 – Example: list of counter input points (list cnt command)
list all command
all argument allows the user to display both, user points and internal points.
─ Index ─ 15. Maintenance console
117
iRTU, iGW & iRTUe Series User Manual
Figure 121 shows an example of usage of the list dv all command in an iRTU unit. Internal points’ tags start with “#” character, and provide the following information:
iRTU current condition: o #id0/deviceError: alerts the user if there is an internal error. o #id0/notSync: clock synchronization status. If On value, iRTU is not synchronized. o #health: this internal point can take the following values: Alarm: communication with one or more system IEDs fails. Warning: communication with all IEDs is ok, but communication with one or more control centers (master stations) fails. Ok: communication with all IEDs and CCs of the system is ok. Points providing information on the iRTU internal module’s status: #id5/deviceError, #id6/deviceError, etc. Redundancy related-points (#rdcy.MyState, #rdcy.PeerState, #rdcy.IamActive and #rdcy.SwitchOverReady). etc.
Figure 121 – Example: list dv all command of an iRTU unit
argument
The argument of the list command, allows the user to filter points based on the value of the iConf’s Options field for that point (Figure 122).
─ Index ─ 15. Maintenance console
118
iRTU, iGW & iRTUe Series User Manual
Figure 122 - Example of iConf’s Options field
For example: In order to only display digital input points of Figure 122 containing “3” option (Category 3), the following command must be entered: list dv 3
Figure 123 – Example of list dv command
If digital input points with “p” option are to be displayed, type list dv p command:
─ Index ─ 15. Maintenance console
119
iRTU, iGW & iRTUe Series User Manual
Figure 124 – Example of list dv command
soe command soe command lists the event history (i.e. sequence of events list), one event per line, with the following columns/fields:
Event’s date and timestamp Date and timestamp quality: o blank: valid time and date o i: invalid time and date Event’s quality: o blank: valid o !: invalid Event’s state/value Text or tag of the event. If no Text is configured for the event through the iConf tool, the tag identifier of the event will be displayed.
Figure 125 – Example of soe command
Events are ordered by time of arrival, i.e. the newest event is displayed at the top of the list. By default, it shows the last 100 entries, but this number can be modified by using the limit argument. Figure 126 shows the syntax for the soe command:
─ Index ─ 15. Maintenance console
120
iRTU, iGW & iRTUe Series User Manual
Figure 126 – soe command syntax
SOE registry can be configured to be stored in volatile or non-volatile registry. This is configured through the iConf tool in the SOE persistent mode field. Arguments for the soe command are described below:
ram: shows events in volatile registry. I.e. it displays the entries since the last boot when SOE is stored in volatile memory. all: shows both, user and internal points. Refer to example of Figure 127. filter: allows the user to filter events based on the value of the iConf’s Options field for that point. Refer to section 15.3.2.16.7 for further details. Figure 128 shows an example of usage of the filter argument. noMsg: hides user’s messages, written by using the soe_note command (see section 15.3.2.20). limit [NUM_LINES]: sets the maximum number of entries to display. By default, the soe command shows the last 100 entries. See examples on Figure 129 and Figure 130. nolimit: by default, the soe command shows the last 100 events. When the nolimit argument is used, all events will be shown with no limit.
Figure 127 – Example of soe all command
Figure 128 – Example of filter argument usage: in this case only events with category “2” (i.e. iConf’s Options field value set to “2”) are displayed
─ Index ─ 15. Maintenance console
121
iRTU, iGW & iRTUe Series User Manual
Figure 129 – Example of limit [NUM_LINES] argument usage: in this case the user has limited the number of entries to display to 5
Figure 130 – Example of filter and limit [NUM_LINES] arguments usage: the console lists last 3 entries corresponding to events with category “2”
commands command Lists commands and setpoints currently in progress with a limit of 4 simultaneous commands. commands all displays the entire command table:
Figure 131 – Example of commands all command usage
display command Sets console display options. Figure 132 shows the syntax for the display command:
─ Index ─ 15. Maintenance console
122
iRTU, iGW & iRTUe Series User Manual
Figure 132 – display command syntax
Arguments for the display command are described below:
sq: shows quality in “short” format (e.g.: ! symbol represents invalid quality). Default value. lq: shows quality in “long” format (e.g.: INV represents invalid quality). See example of Figure 133. ms: timestamps are shown in milliseconds. Default value. us: timestamps are shown in microseconds. See example of Figure 134.
Figure 133 – Example of lq argument usage: quality is displayed in “long” format (e.g. INV instead of !)
Figure 134 – Example of us argument usage: timestamps are displayed in microseconds (instead of milliseconds)
soe_note command This command allows user to write a message to the sequence of events (SOE) registry. Syntax is as follows: soe_note [comment2] ... [comment15]
─ Index ─ 15. Maintenance console
123
iRTU, iGW & iRTUe Series User Manual
Figure 135 – soe_note command syntax
This command will only be available when SOE persistent mode is enabled. That is, when the SOE persistent mode field in iConf is set to SDCard. For further details on the SOE storage in microSD card, please contact iGrid T&D. Figure 136 shows an example of usage of the soe_note command, where user writes a message (User_Comment_01) in the sequence of events registry:
Figure 136 – Example of usage of the soe_note command
The messages written by the user can be displayed by using the soe command (see section 15.3.2.17). The soe command will display the user’s messages with the corresponding date and timestamp, and the following state and text columns (see example of Figure 137):
State: comment Text: user’s message
Figure 137 – soe command displays the user’s messages with the corresponding date and timestamp, and state comment.
15.3.3.
Section sim commands
The cd sim command enters the simulation mode. This allows simulating a point (DI, DO, AI, AO or counter) by entering its tag identifier and a value for the point to be simulated. Quality of the point can also be simulated. sim section commands are described in following sections:
Figure 138 – sim section commands
─ Index ─ 15. Maintenance console
124
iRTU, iGW & iRTUe Series User Manual
dv command Simulates a digital spontaneous event. Syntax: dv [value] [quality] where:
tag: point identifier. value: state/value of the digital input point to be simulated. quality: simulates the quality of the point: iv (invalid) or niv (not invalid).
Figure 139 – Example of dv [value] [quality] command
Without the value and quality arguments, the dv command returns the point current value. Refer to example on Figure 140.
Figure 140 – Example of dv command without the [value] and [quality] arguments: the command returns the current value, quality and time stamp of the point
The following options are available for IEC61850 client: dv remote subs dv remote unsubs Abbreviated forms are: dv remote s dv remote us
remote subs or remote s options are intended to be used for remote substitution of a digital input point. remote unsubs or remote us options are intended to be used to release a substituted digital input point. mv command
Simulates analog values (i.e. analog input points’ value) with an update. Syntax: mv [value] [quality] where:
tag: point identifier. value: numerical value of the measurement to be simulated. quality: simulates the quality of the point: iv (invalid) or niv (not invalid).
─ Index ─ 15. Maintenance console
125
iRTU, iGW & iRTUe Series User Manual
Figure 141 – Example of mv [value] [quality] command
Without the value and quality arguments, the mv command returns the measurement current value. Refer to example on Figure 142.
Figure 142 – Example of mv command without the [value] and [quality] arguments: the command returns the current value, quality and time stamp of the measurement
The following options are available for IEC61850 client: mv remote subs dv remote unsubs Abbreviated forms are: mv remote s mv remote us
remote subs or remote s options are intended to be used for remote substitution of an analog input point. remote unsubs or remote us options are intended to be used to release a substituted analog input point. cm command
Simulates digital commands. Users can also simulate the pulse time of the command. Syntax: cm [pulse_time] where:
tag: point identifier value: command value to be operated. pulse_time: duration of the command (in milliseconds).
Figure 143 – Example of command simulation
─ Index ─ 15. Maintenance console
126
iRTU, iGW & iRTUe Series User Manual
CAUTION: Please, note that the above command performs a real command (digital output). Take this into account before using this command. sp command Simulates analog output values with an update (i.e. setpoints). Syntax: sp [quality] where:
tag: point identifier. value: value used to operate the setpoint. quality: simulates the quality of the point: iv (invalid) or niv (not invalid). CAUTION: Please, note that the above command performs a real setpoint (analog output). Take this into account before using this command. cnt command
Simulates counter values. Syntax for this command is as follows: cnt [reset|add] [value] [quality] where:
tag: point identifier. value: value to simulate. quality: simulates the quality of the point: iv (invalid) or niv (not invalid).
Figure 144 – cnt command syntax
cnt [value] [quality] command
For values less than or equal to 4294967295, the value argument can be entered in decimal format as in the following example: cnt CI_0009 145 niv For values greater than 4294967295 (0xFFFFFFFF), the value argument must be entered in hexadecimal format as in the examples below:
value = 8589934591 (0x1FFFFFFFF): cnt CI_0009 0x00000000:00000000:00000001:ffffffff niv value = 281474976710655 (0x FFFFFFFFFFFF) cnt CI_0009 0x00000000:00000000:0000ffff:ffffffff niv
─ Index ─ 15. Maintenance console
127
iRTU, iGW & iRTUe Series User Manual
Without the value and quality arguments, the cnt command returns the counter current value. Refer to examples on Figure 145:
Figure 145 – cnt [value] [quality] command examples
cnt add [quality] command
The add argument allows the user to increment the counter by adding a value. Figure 146 shows examples of the cnt add command:
The initial value of the counter is 0x00000000:00000000:00000001:FFFFFFFF The user increments this value by 1 by using the cnt add CI_0009 1 niv command. The counter incremented value is 0x00000000:00000000:00000002:00000000. The user again increments the counter value by 0xFFFF0000000000000000000000000000 by using the cnt add CI_0009 0xffff0000:00000000:00000000:00000000 niv command. The counter incremented value is 0xFFFF0000:00000000:00000002:00000000.
Figure 146 – cnt add [quality] command examples
cnt reset command
Resets the value of the counter. Refer to example on Figure 147:
Figure 147 – cnt reset command example
dva command Allows the user to simulate all digital values with an update: dva [quality] where:
value: value to simulate. quality: simulates the quality of the points: iv (invalid) or niv (not invalid).
─ Index ─ 15. Maintenance console
128
iRTU, iGW & iRTUe Series User Manual
The dva command sets all the digital input points with the same value and quality, at the same time. It is useful for initialization simulation. mva command Allows the user to simulate all analog values with an update: mva [quality] where:
value: numerical value to simulate. quality: simulates the quality of the points: iv (invalid) or niv (not invalid).
The mva command sets all the analog input points with the same value and quality, at the same time. It is useful for initialization simulation. mvs command Simulates an analog spontaneous event. Syntax: mvs [quality] Where:
tag: point identifier. value: numerical value to simulate. quality: simulates the quality of the point: iv (invalid) or niv (not invalid). cnts command
Simulates a counter spontaneous value. Syntax: cnts [quality]
tag: point identifier. value: numerical value to simulate. Refer to section 15.3.3.5.1 for further details. quality: simulates the quality of the point: iv (invalid) or niv (not invalid).
15.3.4. Section ip commands The ip section displays information about the TCP/IP stack used in the system.
Figure 148 – ip section commands
The following commands are available in the ip section:
─ Index ─ 15. Maintenance console
129
iRTU, iGW & iRTUe Series User Manual
ping command Identical to the ping command in Windows and Linux systems. This command sends ICMP packets to the destination address, and displays the ping statistics. Syntax: ping [ [timeout]] [-t] [-n N]
Figure 149 - ping command syntax
where:
address: destination address. packetsize: data size in bytes (“32” by default). Example: ping 172.25.1.20 64 timeout: maximum response time in milliseconds (“1000”ms by default). Example: ping 172.25.1.20 32 2000 -n N: repeats the ping command N times. Example: ping 172.25.1.20 -n 8 -t: pings continuously. To stop it, type ping stop. Example: ping 172.25.1.20 –t ipconfig command
Displays current IP configuration for all interfaces.
Figure 150 – ipconfig command
filter command Some protocols require that several slaves listen to the same TCP port (e.g. IEC60870-5-104 protocol which forces to listen to the same port 2404), but connections must be handled independently depending on the master’s source IP address. The filter command displays the table of current established connections, and relates the source IP/port with the local IP/port.
Figure 151 – filter command example
─ Index ─ 15. Maintenance console
130
iRTU, iGW & iRTUe Series User Manual
ipstats command Displays IP traffic statistics for PPP connections such as TETRA, GPRS and 3G. It should be used to troubleshoot communication problems. route command Allows users to show and manage the IP routing table. When the sub-network where the iRTU/iGW unit is connected, has access to other sub-networks, it may be required to set up some routing rules. For field testing purposes, the iRTU/iGW console features a command that is able to create/delete IP routes: route add (creates a new route) & route del (deletes an existing route). This allows the user to set and test routing rules without restarting the device. Syntax for the route command is as follows: route [list|print|show]
add: adds an entry to the IP routing table. del: deletes an entry from the IP routing table. list, print and show: route list, route print and route show commands display current routing table.
Example: The following command sets the gateway (next hop) 192.165.1.1 to access to network 172.10.x.x: route add 172.10.0.0 mask 255.255.0.0 gw 192.165.1.1 In order to display the current routing table after adding the route above: route list, or route print, or route show The following command will delete the route above: route del 172.10.0.0 mask 255.255.0.0 gw 192.165.1.1 All modifications done by this command are volatile, being lost if iRTU/iGW device is restarted. Once routes are tested and known, they can be configured through the iConf’s TCP/IP interface properties, Routes section (refer to iConf User Manual) and therefore, routes will be added to the iRTU/iGW configuration and will we kept (i.e. they will not get lost when the device restarts).
15.3.5.
Other sections commands and options
The following sections are also available in the iRTU/iGW’s maintenance console:
os: displays information related to the iRTU/iGW unit operative system. ports: displays basic information on the used serial ports. It also includes virtual ports tunneled over a TCP connection. procedure: displays a list of the available procedures, as defined in the iRTU/iGW configuration. PLC: shows current PLC status and statistics, and allows user to pause & resume the PLC execution. term: this section allows users to configure, test and monitor modems connected to the iRTU/iGW units. pcap: allows user to capture live packet data from Ethernet interface and to save the packet data captured into a .pcap (packet capture) file.
─ Index ─ 15. Maintenance console
131
iRTU, iGW & iRTUe Series User Manual
EXP422: displays basic information about the iRTUe modules (either internal or external) connected to the iRTU/iGW unit. m102: displays information about the system’s IEC60870-5-102 IEDs. m104: displays information about the system’s IEC60870-5-104 IEDs mDLMS: displays information about the system’s DLMS meters. rdcy: shows redundancy state (in iRTU/iGW units in redundant configuration). See section 17. s61850: displays information about the IEC61850 clients connected to the iRTU/iGW unit when configured as IEC61850 server. m61850: displays information about the system’s IEC61850 servers. NTP: shows information about the system’s NTP servers and data about the last NTP synchronization.
For further information on the above sections options and commands, please refer to the Command Line Console Manual.
15.4. iDevSetup menu In this section we will describe how to access the iRTU/iGW iDevSetup menu, as well as the available options. In case it is required to update the iDevSetup application version, please follow steps described in section 15.4.3.
15.4.1. Accessing the iDevSetup menu These are the steps to follow in order to access the iDevSetup menu: 1) Open the iRTU/iGW maintenance console (15.1) and enter the password “irtutrace” (15.2). 2) Shutdown the iRTU/iGW unit. 3) When the iRTU/iGW unit initializes, press key “i” after the “Welcome to iDevSetup” message to enter the iDevSetup menu.
Figure 152 – Press key “i” after the welcome message in order to enter the iDevSetup menu
15.4.2. iDevSetup menu options Figure 153 shows the options available in the iDevSetup menu:
Figure 153 – iDevSetup menu available options
─ Index ─ 15. Maintenance console
132
iRTU, iGW & iRTUe Series User Manual
Press the corresponding key to select the desired option. For example: press the key “3” to select the “Show system info” option; or press the key “r” to access the “Redundancy setup” menu. Show IP settings option This option displays the current iRTU/iGW IP configuration.
Figure 154 – Show IP settings option
Change IP settings option The device’s IP configuration can be set through the iConf tool (refer to iConf User Manual) or through the “Change IP settings” option of the iDevSetup menu by entering the new IP, mask and gateway.
Figure 155 – Change IP settings option
Press the Esc key to exit the IP configuration without saving. Show system info option The “Show system info” option retrieves the following info (Figure 156):
iDevSetup version iKernel version RTC (Real-Time Clock) chip model Ethernet switch model and status for iRTU-S3 and iGW-S3 series.
Figure 156 and Figure 157 show examples of different devices’ system information.
Figure 156 – Example: system information of an iRTU/iGW-B0 unit
─ Index ─ 15. Maintenance console
133
iRTU, iGW & iRTUe Series User Manual
Figure 157 – Example: system information of an iRTU/iGW-S3 unit
Execute factory test option This option allows executing the following device tests:
Figure 158 – Device test utility options
Field user test (key “m”)
Guided test for users at field. Refer to section 19 for further information. Factory test (key “a”)
Extended test intended to be carried out at iGrid T&D lab. Contact iGrid T&D for further information ([email protected]). EXP422 patch cord test (key “p”)
This test allows the user to verify the EXP422 patch cord used to connect an iRTU/iGW unit with an iRTUe device, and for interconnecting iRTUe units. EXP422 patch cord pin layout is explained in section 12.1. Follow steps below to check the EXP422 patch cord with terminal blocks at both ends:
Connect one of the ends to the EXP422 port of the iRTU/iGW unit. Leave the other end loose. Interconnect “Rx+” and “Tx+” pins (external bridge between 1st and 4th pin) of the loose end. Interconnect “Rx-” and “Tx-” pins (external bridge between 2nd and 3rd pin) of the loose end. Press key “p” to start the EXP422 patch cord test. After the test, remove the external bridges in the loose end.
─ Index ─ 15. Maintenance console
134
iRTU, iGW & iRTUe Series User Manual
Check test validation code (key “c”)
In order to pass this test, user will be required to enter the validation code, model, serial number, and date of issue of the factory test. All this data can be found on the header of the Factory test sheet delivered with the device (see example of Figure 159).
Figure 159 – Example of factory test sheet header
Execute iRTU application in test mode option Reserved for future use. Redundancy setup option This option allows setting the role of the iRTU/iGW in a redundant system. When working with two redundant iRTU/iGW units, one must be set with Primary role, and the other with Secondary role. This setting is done through the iDevSetup menu, Redundancy setup option. When selecting the Redundancy setup option, the Redundancy setup menu will be opened, showing the current role of the device (see Figure 160). By default, iRTU/iGW units have Primary role. In order to change the role of the iRTU/iGW unit that will act as Secondary, press the “y” key when asked to change the role to secondary. See example of Figure 160.
Figure 160 – Redundancy setup menu. The device has Primary role. In order to change to Secondary, press the “y” key.
In order to change the role of a Secondary unit to Primary, press the “y” key when asked to change the role to primary. See example of Figure 161.
Figure 161 – Redundancy setup menu. The device has Secondary role. In order to change to Primary, press the “y” key.
─ Index ─ 15. Maintenance console
135
iRTU, iGW & iRTUe Series User Manual
For further information on iRTU/iGW redundancy functionality, please refer to section 17. Internal PPS calibration option Factory functionality. Update iKernel option Select this option when an iKernel update is required. This option will remain hidden in the iDevSetup’s menu until the user connects a USB flash drive with a folder named UPLOAD_IKERNEL to the USB port of the iRTU/iGW device. Refer to section 18 for further information about the iKernel update process. Quit option Exits the iDevSetup menu.
15.4.3. iDevSetup update process via FTP iDevSetup application version should be updated only upon iGrid T&D instructions. These are the steps to follow to update the iDevSetup application of your iRTU/iGW unit using FTP: 1) From the FTP manager, connect to the appropriate address (10.10.10.100 for USB port connection; IP address of the iRTU/iGW unit for Ethernet connection) entering user name and password as discussed in section 14.1.3 (user = isupport, password = irtusupport). 2) Access the BIN directory in the iRTU/iGW unit. 3) Replace the existing iDevSetup.bin file in the BIN directory of the iRTU/iGW unit with the one supplied by iGrid T&D. 4) Open the maintenance console (section 15) and reboot the iRTU/iGW unit with the shutdown command.
─ Index ─ 15. Maintenance console
136
iRTU, iGW & iRTUe Series User Manual
16. Licensing system iRTU and iGW unit licensing system is accomplished by a .bin file which defines the communication capabilities including number of devices (IEDs, master stations), number of points and protocols supported. iRTU and iGW units are supplied by iGrid T&D with the proper licenses installed according to the user’s requirements. However, the users may need to expand the iRTU/iGW communication capabilities, and then they will need to update the existing license. In this case, the user should contact the distributor in order to verify the capabilities (communication protocols, number of devices, number of points, functionalities, etc.) of the contractual iRTU/iGW package and, if required, ask for extending the iRTU/iGW license capabilities. Once the license is expanded by iGrid T&D, user should update the new license provided. In order to update the license, follow the steps described in section 14.6 of the present manual.
16.1. iRTU & iGW license errors When the configuration applied to the iRTU/iGW unit exceeds the maximum number of IEDs/master stations or number of points, or it uses a functionality not enabled in the license (redundancy, PLC), the console shows a license error with the following description: License limit error. Module “x” missing. Below images show different iRTU/iGW license errors:
Figure 162 shows a license error due to IEC61850 protocol is not included in the iRTU/iGW license. Figure 163 shows a license error due to PLC functionality is not enabled in the iRTU/iGW license. Figure 164 displays a license error due to redundancy functionality is not enabled in the iRTU/iGW license.
Figure 162 – License error example (I)
Figure 163 – License error example (II)
Figure 164 – License error example (III)
─ Index ─ 16. Licensing System
137
iRTU, iGW & iRTUe Series User Manual
17. Hot-Standby redundancy iRTU and iGW units can be deployed on a hot-standby redundant configuration. This means that the iGW/iRTU in standby becomes active automatically as soon as it detects that its peer it's down. Redundant iGW/iRTU units use a special communication link used to know each other’s state. Each iRTU/iGW sends it state to its peer and receives the state from its peer cyclically through this live link. The iRTU/iGW determines its own state (role) based on the state received from its peer. For example: An active iRTU/iGW unit that has been receiving a “Standby OK” state from its peer and that stops receiving its peer state, will change its state to “Active Alone”. An “Active Alone” iRTU/iGW that receives a “Standby Alone” or “Standby OK” from its peer, will change its state to “Active Ok”. N.B.: Redundancy states (i.e. roles) will be further explained in next section 17.3. Therefore, the live link between redundant iRTU/iGW devices is a critical point in the redundancy system. We recommend the use of a direct serial link, using RS422, as shown in Figure 165. Refer to section 17.6 for information about the serial cable layout.
Figure 165 – Redundant iRTU/iGW devices connected via direct serial link (RS422).
If a serial connection is not possible (because of distance between them, or any other reason) use network communication (UDP/IP).
─ Index ─ 17. Hot-Standby Redundancy
138
iRTU, iGW & iRTUe Series User Manual
Figure 166 – Redundant iRTU/iGW devices connected via UDP.
Important concepts when operating with two iRTU/iGW devices in redundant mode:
Active iRTU/iGW: o
Runs in normal operation.
o
Only the active unit communicates with field IEDs and master stations.
Standby iRTU/iGW: o
It does not communicate with IEDs/master stations (only the active unit does it).
o
The standby iGW/iRTU connects against its peer to be updated in real-time with the data received by the active unit.
o
It will take over the active role when its peer fails.
The above Active & Standby roles can be exchanged at any time with no loss of information using the Switchover command. The switchover command can be operated from: o
The maintenance console using the switchover command in the rdcy section (see section 17.3)
o
A master station, adding the #rdcy.SwitchOver command in the data base configuration (see section 17.5).
─ Index ─ 17. Hot-Standby Redundancy
139
iRTU, iGW & iRTUe Series User Manual
Primary iRTU/iGW: o
The Primary unit has preference at boot time when both iRTU/iGW devices are started up simultaneously. In this case, its peer (the Secondary unit) waits 3 seconds before starting listening to the Primary unit. This means that, when both units are started at the same time (and they both run successfully), the Primary unit will take the role of active, and the Secondary will take the standby role.
o
Do not confuse Primary with Active. The iRTU/iGW unit set as Primary can run on either Active or Standby modes.
Secondary iRTU/iGW: o
At boot time, the Secondary unit waits for 3 seconds, and then starts listening to its peer (the Primary unit).
o
Do not confuse Secondary with Standby. The iRTU/iGW unit set as Secondary can run on either Active or Standby modes.
Redundant iRTU/iGW units must be configured Primary or Secondary (i.e., one unit must be configured to be Primary and the other to be Secondary) through the iDevSetup menu: o
In order to access the iDevSetup menu, follow the instructions given in section 15.4.1.
o
Refer to section 15.4.2.6 for details on how to set the redundancy role through the iDevSetup menu.
Redundant iRTU/iGW units should have:
Same configuration: user must apply same configuration to both iRTU/iGW devices.
Same firmware, iKernel and iDevSetup version: o Firmware and iKernel version can be checked by entering the info command in the maintenance console (15.3.2.15). o iDevSetup version can be retrieved by accessing the iDevSetup menu (15.4.1.) and selecting the Show system info option (15.4.2.3)
Data synchronization between redundant iRTU/iGW is always done through the IP network. User must configure a different IP address for each iRTU/iGW device: Primary IP and Secondary IP (see Figure 165 & Figure 166). These IP addresses are persistent (Primary device will always have Primary IP address, and vice versa) and are used for data synchronization between active and standby units.
Primary IP and Secondary IP addresses should also be used by the user to connect to the iRTU/iGW devices for management. That is, to connect, configure and monitor each unit via iConf. o
Both IP addresses must be configured in the iConf’s properties panel, in the Redundancy section (17.2).
Besides the above Primary IP and Secondary IP addresses, both devices will have the same operative IPs (one or more) as defined in the iConf’s IP interfaces section. o
This/these is/are the IP address/es of the active unit used in the communication with the field IEDs and master stations (Control Centers). That is, the IP address/es used by other devices to connect to the active unit.
─ Index ─ 17. Hot-Standby Redundancy
140
iRTU, iGW & iRTUe Series User Manual
o
In case of failure of the current active iRTU/iGW, the standby unit will become active and it will enable all interfaces defined inside the IP interfaces section, becoming a new device in the network to take over the role of the previous one.
When redundant iRTU/iGW devices are interconnected via UDP, each iRTU/iGW performs continuous pings to a user defined IP address in order to verify the Ethernet connection. This IP address corresponds to the Network Check IP parameter in the iConf’s Redundancy settings (17.1). o
The selection of the Network Check IP address is an important point, because in case of failure to connect to this IP address, the iRTU/iGW will automatically switch to Standby role if it does not receive the state of its peer.
o
Choose a Network Check IP address that is always available.
Field events with time stamp information can be displayed in both Active and Standby unit’s maintenance consoles.
When a switchover is performed, the redundant iRTU/iGW devices change its role. Switchover can be of two types: o
Automatic, after the Active unit fails.
o
Manual:
through the iRTU/iGW maintenance console (17.3). through the #rdcy.SwitchOver command from a master station (section 17.5).
After a switchover is performed: o
the Active unit will reset and change its role to Standby,
o
the Standby unit will take over the role of Active.
Most maintenance console’s commands (15.3) are also available in the Standby unit (e.g. soe ram, date, info, ver, list dv, list mv, list cm, list sp, etc.). There are others like mod, sim section’s commands, etc. which are not available in the Standby unit.
17.1. Redundancy configuration in iConf Redundancy settings must be configured in the iConf tool: 1) Select the main node (i.e. the iRTU/iGW) from the System panel. 2) Select the Redundancy section from the Properties panel (Figure 167). 3) Configure parameters of Redundancy section. Redundancy parameter description can be found below.
─ Index ─ 17. Hot-Standby Redundancy
141
iRTU, iGW & iRTUe Series User Manual
Figure 167 – Redundancy section of the iConf’s Properties panel
Enabled redundancy: if set to true, it enables the iRTU/iGW redundancy. o o
Valid values: Boolean. Default value: false.
Primary IP: IP address of the Primary iRTU/iGW unit (refer to description in previous section). Mandatory.
Secondary IP: IP address of the Secondary iRTU/iGW unit (refer to description in previous section). Mandatory.
Common network mask: is the network mask used to define the Primary IP and Secondary IP addresses. When set to 0.0.0.0 a minimal mask is calculated to include both IPs, this may cause the network mask to be so narrow that no other device can reach them. o
Port Type: port type used for redundancy management between Primary and Secondary iRTU/iGW units. That is, allows user to set the type of the link between redundant devices: serial or UDP. o o
Default value: COM2. Valid values: one of the iRTU/iGW serial ports.
UDP Port: UDP port used for redundancy management when redundant units are interconnected via UDP. o o
Valid values: serial, UDP. Default value: serial.
Serial Port: serial port used for redundancy management when redundant units use direct serial link. o o
Default value: 255.255.255.0
Default value: 14002. Valid values: integer from 1 to 65535.
Network Check IP: when redundant iRTU/iGW units are interconnected via UDP, the Network Check IP address is used to verify the Ethernet connection. o o
This parameter is mandatory when redundant iRTU/iGW are interconnected via UDP. Not used when redundant units use direct serial link.
─ Index ─ 17. Hot-Standby Redundancy
142
iRTU, iGW & iRTUe Series User Manual
Network Failure Time Tolerance: maximum time of network failure detection before considering that the network is down. o o o
Primary Failure Time Tolerance: if Secondary iRTU/iGW unit can't hear the heartbeat signal of the Primary unit during this amount of time, the state of the peer iRTU/iGW unit (i.e. Primary) in the Secondary iRTU/iGW unit will change to unknown. o o o
Units: milliseconds. Default value: 2500 (milliseconds). Valid values: integer from 0 to 65534.
Units: milliseconds. Default value: 1000 (milliseconds). Valid values: integer from 0 to 65534.
Secondary Failure Time Tolerance: if Primary iRTU/iGW unit can't hear the heartbeat signal of the Secondary unit during this amount of time, the state of the peer iRTU/iGW unit (i.e. Secondary) in the Primary iRTU/iGW will change to unknown. o o o
Units: milliseconds. Default value: 1000 (milliseconds). Valid values: integer from 0 to 65534.
17.2. First time redundancy configuration The first time you configure redundancy in iRTU/iGW units we recommend user to follow below instructions: 1) First, configure and test only one iRTU/iGW device as if it were to be no redundant (i.e., as a standalone unit). 2) Once configuration is tested successfully, configure one iRTU/iGW to be the Primary unit and the other the Secondary unit through the iDevSetup menu: a) In order to access the iDevSetup menu, follow the instructions given in section 15.4.1. b) Refer to section 15.4.2.6 for details on how to set the redundancy role through the iDevSetup menu. 3) Use iConf tool to enable redundancy and to set the appropriate redundancy settings (see section 17.1). 4) Apply same configuration to both devices and restart them. 5) Check redundancy status through the iRTU/iGW maintenance console (see section 17.4).
17.2.1. Configuration and redundancy operation test example In this example, we will configure two iRTU/iGW devices in redundant mode as follow:
Redundancy management link: serial type. iRTU/iGW devices will be interconnected via direct serial link using RS422, and COM3 serial ports (Figure 168).
Persistent IP addresses for management and data synchronization (Figure 168): o o
Primary IP: 172.25.1.23 Secondary IP: 172.25.1.91
Operative IP address: 172.25.1.25. Refer to configuration in Figure 169.
─ Index ─ 17. Hot-Standby Redundancy
143
iRTU, iGW & iRTUe Series User Manual
Figure 168 – Example of Redundancy settings configuration in iConf
Figure 169 – Example of Redundancy settings configuration in iConf: operative IP address. This is the IP address of the active unit used in the communication with IEDs and master stations (Control Centers)
Figure 170 – Redundant iRTU/iGW example based on configuration shown in Figure 168 and Figure 169
Follow below steps for first time configuration:
─ Index ─ 17. Hot-Standby Redundancy
144
iRTU, iGW & iRTUe Series User Manual
1) Before enabling the redundancy in the iConf’s Redundancy section, configure and test the database and communication to IEDs/master stations, in one iRTU/iGW unit as it was a standalone unit. Configure IP address of the device as in Figure 169. 2) Connect to the iRTU/iGW units and set one as Primary and the other as Secondary: a) By default, all iRTU/iGW units have Primary role. If the unit to be defined as Primary, has already a Primary role, do not change it. b) If the unit to be configured as Secondary, has a Primary role, change it to Secondary. See example of Figure 171:
Figure 171 – Example of role change through the iDevSetup menu. The role is changed from Primary to Secondary.
3) Configure redundancy in iConf as in Figure 168. 4) Apply same configuration to both units and restart them (first Primary and later Secondary unit). 5) During initialization, Primary unit will take the Primary IP address, and the Secondary unit the Secondary IP address. From now on, use these IP addresses for management in iConf (i.e. to update configuration, open the respective maintenance consoles, etc.). Figure 172 and Figure 173 show the Primary and Secondary maintenance console respectively. In order to access the maintenance console, use the Primary IP and Secondary IP addresses, respectively. As shown in figures below, after the Primary unit has initialized and loaded the configuration files, it starts listening to its peer. It receives a hearing state from the Secondary unit, and therefore, changes its state to active alone (actAlone). Few seconds later, the Secondary unit sends a standby alone state (bckAlone). Then the Primary unit updates its state to Active (actOK) and the Secondary unit to Standby (bckOk).
─ Index ─ 17. Hot-Standby Redundancy
145
iRTU, iGW & iRTUe Series User Manual
Figure 172 – Example of maintenance console of the Primary iRTU/iGW.
─ Index ─ 17. Hot-Standby Redundancy
146
iRTU, iGW & iRTUe Series User Manual
Figure 173 – Example of maintenance console of the Secondary iRTU/iGW.
The Active unit (which is now the Primary unit) enables the interface as defined in the iConf IP interfaces section:
Figure 174 – Active unit IP settings. The active unit enables the interfaces as defined in the IP interfaces section of the iConf tool. In our example it is the 172.25.1.25 interface. It also displays the Primary IP address
Figure 175 – Standby unit IP settings. Only the Secondary IP address is displayed in the standby unit IP configuration.
In order to check redundancy state, enter in the rdcy section of the iRTU/iGW maintenance console (section 17.3):
─ Index ─ 17. Hot-Standby Redundancy
147
iRTU, iGW & iRTUe Series User Manual
Figure 176 – Example: redundancy state of the Primary unit
Figure 177 – Example: redundancy state of the Secondary unit
Test the manual switchover by entering the switchover command from the rdcy section of any of the iRTU/iGW unit’s maintenance console. After the switchover, the Secondary unit will switch to Active role, and will enable the 172.25.1.25 interface (operative IP; i.e. the IP set in the iConf’s IP Interfaces section):
Figure 178 – After switchover, Secondary unit switches to Active role
The Primary unit will change its role to Standby:
─ Index ─ 17. Hot-Standby Redundancy
148
iRTU, iGW & iRTUe Series User Manual
Figure 179 - After switchover, Primary unit switches to Standby role
iRTU/iGW redundant units are synchronized through the IP network. Active unit receives the field events, and the Standby unit connects against the Active unit to get this data. Events are displayed in both maintenance consoles:
Figure 180 – Events are displayed in both Active and Standby unit maintenance console
17.3. Redundancy section (rdcy) in iRTU/iGW maintenance console rdcy section in iRTU/iGW maintenance console allows the user to check the state of the current unit and its peer, and to perform a manual switchover in order to change the role of the iRTU/iGW units. In order to change to the rdcy section, enter the following command: cd rdcy
Figure 181 – rdcy section commands
─ Index ─ 17. Hot-Standby Redundancy
149
iRTU, iGW & iRTUe Series User Manual
The rdcy menu includes the commands below (Figure 181):
show: displays the following information (Figure 182): o
Status of the current iRTU/iGW unit: Primary or Secondary. Active or Standby.
o
Informs the user if redundant units are ready for a switchover.
o
In Active unit, it informs whether it is connected to Standby unit
o
In Standby unit, it informs the user whether the iRTU/iGW has completed the data synchronization.
o
Current iRTU/iGW and its peer exact redundant state. Refer to section 17.4 for further details.
o
Port used for live link.
Figure 182 – show command in rdcy section
switchover: performs a manual switchover in order to change the roles of the iRTU/iGW units. After a switchover is performed: o
the Active unit will reset and change its role to Standby (Figure 183),
o
the Standby unit will take over the role of Active.
Figure 183 – switchover command in rdcy section
17.4. Redundancy states As can be seen on previous Figure 172, Figure 173 and Figure 183, the redundancy state of Primary and Secondary units is shown in the maintenance console as follows:
Rdcy: my state: reports the current iRTU/iGW redundancy state. It is related to the internal point #rdcy.MyState (17.5). For example: o
Rdcy: my state = actAlone (Figure 184): the iRTU/iGW state is Active alone (actAlone). I.e. iRTU/iGW unit has Active role and there is no iRTU/iGW connected.
─ Index ─ 17. Hot-Standby Redundancy
150
iRTU, iGW & iRTUe Series User Manual
Rdcy: peer state: reports the current peer iRTU/iGW state. It is related to the internal point #rdcy.PeerState (17.5). For example: o
Rdcy: peer state = bckOK (Figure 185): the peer unit is Standby OK (bckOK). I.e. peer status is Standby and is connected to iRTU/iGW, which has the Active role.
Figure 184 – Redundancy states examples (I)
Figure 185 – Redundancy states examples (II)
Below is a description of the main redundancy statuses for iRTU/iGW:
booting: iRTU/iGW unit is initializing.
hearing: iRTU/iGW is hearing the peer state.
actAlone (Active alone): iRTU/iGW has the Active role and there is no peer connected (Figure 186). After a switchover, the standby unit also takes the role of Active alone and keeps this role until the peer connects.
Figure 186 - Redundancy states examples (III)
bckAlone (Standby alone): this value reports one of the following conditions: o
When the iRTU/iGW unit connects to the peer unit and the peer unit is active, it will enter in standby mode and change its role to Standby alone (Figure 187). After being synchronized with the active unit, it will change its role to bckOK (see description below).
o
When redundant units are connected via UDP and connection to the configured IP address in Network Check IP (17.1) fails, iRTU/iGW will change to Standby alone mode if it does not receive the heartbeat signal from its peer. ─ Index ─
17. Hot-Standby Redundancy
151
iRTU, iGW & iRTUe Series User Manual
Figure 187 - Redundancy states examples (IV)
actOK (Active OK): iRTU/iGW has Active role and communicates with its peer, which has a Standby role (bckOK).
Figure 188 - Redundancy states examples (V)
bckOK (Standby OK): iRTU/iGW has Standby role and communicates with its peer, which has the Active role (actOK).
Figure 189 – Redundancy states examples (VI)
actSwitchReq (Active switchover required): iRTU/iGW unit which has Active role and has executed a switchover, will change its role to actSwitchReq. See Figure 190. If both units are ready for a switchover, the active unit will reset and the peer unit will take over the active role.
actReboot (Active reboot): this value reports one of the following conditions: o
When the user uses the shutdown or reload command in the iRTU/iGW console to shutdown the device.
o
iRTU/iGW unit which has received a bckSwitchReady state (Standby switchover ready) from its peer, will change its role to actReboot. See Figure 190.
shutdown.
bckSwitchReq (Standby switchover required): iRTU/iGW unit which has Standby role and has executed a switchover, will change its role to bckSwitchReq. See Figure 191.
bckSwitchReady (Standby switchover ready): this indicates that the iRTU/iGW (which is Standby) is ready for a switchover.
bckSwitching (Standby switching): iRTU/iGW is switching to the Active role.
─ Index ─ 17. Hot-Standby Redundancy
152
iRTU, iGW & iRTUe Series User Manual
Figure 190 - Redundancy states examples (VII): upper image shows the status in the active unit when it performs a switchover. Lower image shows the status in the peer unit, that changes its status from standby to active after the switchover.
─ Index ─ 17. Hot-Standby Redundancy
153
iRTU, iGW & iRTUe Series User Manual
Figure 191 - Redundancy states examples (VIII): status in a standby unit which has performed a switchover.
Below is a description of some of the main redundancy statuses for the peer unit:
Unknown state: the state of the peer unit is unknown.
hearing: peer state is hearing the iRTU/iGW
actAlone (Active alone): peer unit is Active alone. It happens when the iRTU/iGW resets after a switchover and the peer unit has taken the role of Active alone.
bckAlone (Standby alone): peer unit is Standby alone.
actOK (Active OK): peer unit has the Active role, and current unit has the Standby role.
bckOK (Standby OK): peer unit has a Standby role and communicates with current unit, which has the Active role.
actSwitchReq (Active switchover required): peer unit with Active role which executes a switchover, will change its role to actSwitchReq. See Figure 192.
Figure 192 - Redundancy states examples (IX)
actReboot (Active reboot): peer unit will reboot in order to change its role from active to standby.
bckSwitchReq (Standby switchover required): peer unit with Standby role that executes a switchover, will change its role to bckSwitchReq.
─ Index ─ 17. Hot-Standby Redundancy
154
iRTU, iGW & iRTUe Series User Manual
bckSwitchReady (Standby switchover ready): this indicates that the peer unit (which is Standby) is ready for a switchover.
bckSwitching (Standby switching): peer unit is switching to the Active role.
The above states corresponds to the following numerical values: o o o o o o o o o o o o o
unknown state: state 0 Booting: state 1 Hearing: state 2 actAlone: state 10 actOK: state 11 actSwitchReq: state 12 actReboot: state 17 Shutdown: state 30 bckAlone: state 40 bckOK: state 41 bckSwitchReq: state 42 bckSwitchReady: state 43 bckSwitching: state 44
17.5. Redundancy internal points iRTU & iGW units use internal signals that provide information on redundancy statuses. These signals are the following:
#rdcy.IamActive: this signal reports whether the current iRTU/iGW role is Active.
#rdcy.IamPrimary: reports whether the current iRTU/iGW is Primary or Secondary. That is, it lets know whether the current Active unit is Primary or Secondary.
#rdcy.SwitchOverReady: reports switchover availability. In other words, based on iRTU/iGW states it reports whether it is possible to switch roles.
#rdcy.MyState: reports current iRTU/iGW state. It uses the same states as shown in previous section 17.4.
#rdcy.PeerState: reports current peer state. It uses the same states as shown in previous section 17.4.
The current value of these internal points can be shown in the iRTU/iGW console by using the list dv all command (15.3.2.16). User can also be interested in adding these points in the iRTU/iGW configuration, so that text, state, display options, and other settings can be customized. For example, it can be useful to send the current #rdcy.IamPrimary point state to Control Center, so that operator can monitor which is the active unit (the Primary or the Secondary) at any moment. Following are the steps to include the redundancy signals in the project database:
Run the iConf configuration tool and open the relevant configuration
Select the main node (iRTU or iGW) in the System panel.
Select the Digital Inputs tab in the signal list.
Add 5 signals.
─ Index ─ 17. Hot-Standby Redundancy
155
iRTU, iGW & iRTUe Series User Manual
Configure column Tag using the following identifiers: #rdcy.IamActive, #rdcy.IamPrimary, #rdcy.SwitchOverReady, #rdcy.MyState and #rdcy.PeerState (refer to Figure 193).
Figure 193 - Definition of internal signals #rdcy.IamActive, #rdcy.IamPrimary, #rdcy.SwitchOverReady, #rdcy.MyState and #rdcy.PeerState in the iRTU/iGW database using the iConf configuration tool
The states/values for these internal points are as follows:
#rdcy.IamActive: o
off: iRTU/iGW is not active
o
on: iRTU/iGW is active
#rdcy.IamPrimary: o
off: iRTU/iGW is Secondary
o
on: iRTU/iGW is Primary
#rdcy.SwitchOverReady: o
off: switchover is not ready
o
on: switchover is ready
#rdcy.MyState and #rdcy.PeerState: o
0: Unknown state
o
1: Booting
o
2: Hearing
o
10: actAlone (Active alone)
o
11: actOK (Active OK)
o
12: actSwitchReq (Active switchover required)
o
17: actReboot (Active reboot)
o
30: Shutdown
o
40: bckAlone (Standby alone)
o
41: bckOK (Standby OK)
o
42: bckSwitchReq (Standby switchover required)
o
43: bckSwitchReady (Standby switchover ready)
o
44: bckSwitching (Standby switching)
─ Index ─ 17. Hot-Standby Redundancy
156
iRTU, iGW & iRTUe Series User Manual
o
45: bckSwitchCloseingClient (Standby switchover closing client)
o
49: bckWaitReset (Standby wait reset)
o
50: bckReboot (Standby reboot)
Figure 194 shows an example of State type definition for #rdcy.IamActive, #rdcy.IamPrimary, and #rdcy.SwitchOverReady tags in iConf:
Figure 194 – Example of definition of State type for #rdcy.IamActive, #rdcy.IamPrimary, and #rdcy.SwitchOverReady tags using iConf tool
Figure 195 shows an example of State type definition for #rdcy.MyState and #rdcy.PeerState tags in iConf:
─ Index ─ 17. Hot-Standby Redundancy
157
iRTU, iGW & iRTUe Series User Manual
Figure 195 - Example of definition of State type for #rdcy.MyState and #rdcy.PeerState tags using iConf tool
17.6. Direct serial link between redundant iRTU/iGW: serial cable layout When using direct serial link, interconnect redundant iRTU/iGW units via RS422 using the following cable layout: Primary iRTU/iGW COM serial port Rx+ Rx– Tx– Tx+ GND
Secondary iRTU/iGW COM serial port Rx+ Rx– Tx– Tx+ GND
Table 23 – RS422 cable pin layout between redundant iRTU/iGW units
─ Index ─ 17. Hot-Standby Redundancy
158
iRTU, iGW & iRTUe Series User Manual
18. iKernel version and update process In this section we will see how to check the iRTU & iGW devices’ iKernel version and, if required, how to update it.
18.1. Checking the iKernel version Generally, all iRTU & iGW devices delivered in 2017 and later, include iKernel versions 2.9.0 and later. The exact iRTU & iGW iKernel version information can be found in the factory test sheet shipped with the iRTU/iGW device:
Figure 196 – Example of iGW-B0 unit factory test sheet. The iKernel version is shown in the general test section
User can also get the iKernel version information through the iRTU/iGW maintenance console, in two different ways:
─ Index ─ 18. iKernel version and update process
159
iRTU, iGW & iRTUe Series User Manual
Accessing the iRTU/iGW iDevSetup menu (15.4.1) and selecting the “Show system info” option. This option retrieves not only the iKernel version, but also the iDevSetup version, the RTC chip model and the Ethernet switch model and status. Refer to section 15.4.2.3 for further details. Enter command info in the maintenance console. This command displays not only the iKernel version, but also the firmware version, license code, serial number of the device, among others. See section 15.3.2.15 for more information.
Figure 197 – Info command
18.2. iKernel update process In order to update the iRTU/iGW’s iKernel version, user should use a USB drive and follow below steps: 1) Connect the USB flash drive to a PC. 2) Create a directory named UPLOAD_IKERNEL in the root directory of the USB drive. If the directory is already present, its contents should be deleted. 3) Copy the iKernel.bin file provided by iGrid T&D to the UPLOAD_IKERNEL directory in the USB drive. 4) Connect the USB drive to the USB port in the iRTU/iGW unit. 5) Open the maintenance console (section 15) and reboot the iRTU/iGW unit with the shutdown command. 6) Access the iRTU/iGW iDevSetup menu (15.4.1) and select the “Update iKernel” option:
─ Index ─ 18. iKernel version and update process
160
iRTU, iGW & iRTUe Series User Manual
Figure 198 – iDevSetup menu: Update iKernel option (key “k”)
7) Press “y” to start the update process. Do not disconnect the USB drive during the update process. Do not remove the power supply during the update process. 8) During this process, the console shows some messages about the update status:
Figure 199 – iKernel update process
9) The update process is successfully done when the console shows the following message: “iKernel image updated successfully. Resetting device..... Please wait.....” 10) iRTU/iGW unit will restart. 11) When the iRTU/iGW unit initializes, check the iKernel version by entering the command info in the maintenance console.
─ Index ─ 18. iKernel version and update process
161
iRTU, iGW & iRTUe Series User Manual
19. Field User Test The Field user test is a guided test intended to be used by users at field. In order to perform the field user test, user should access the iRTU/iGW iDevSetup menu (section 15.4), select option “4” (Execute factory test, section 15.4.2.4), and then press key “m” (15.4.2.4.1). The Field User test dialog will then be displayed. The first step consists of selecting the device (model) to test from the dialog shown in Figure 200.
Figure 200 – Field User test: user is asked to select the iRTU/iGW model to test
After selecting the type of device, the iRTU/iGW console will show a list of available tests for that model. Figure 201 shows an example of the different tests included in the field user test of an iRTU-S3D1 unit:
Figure 201 – Example of field user test of an iRTU-S3D1 device
─ Index ─ 19. Field User Test
162
iRTU, iGW & iRTUe Series User Manual
iRTU & iGW devices’ user tests include:
General tests (section 19.1) Communication tests: serial and Ethernet ports of the iRTU/iGW are being checked (section 19.1.2). I/O ports tests (section 19.1.3).
The type and quantity of available tests will depend on the device model. For iRTUe units, refer to section 19.2.
19.1. iRTU & iGW user test Includes the following tests:
19.1.1.
General tests
General tests are described in sections below: Get Version (key “a”) Retrieves the iKernel version.
Figure 202 – Get Version option example: returns the iKernel version of the device
Activation Code (key “b”) Retrieves the license code.
Figure 203 – Activation Code option example: returns the device license code
Eeprom Test (key "c") Checks the device’s EEPROM state.
Figure 204 – Eeprom Test example
RTC Test (key "d") Reports the RTC (Real-Time Clock) state.
Figure 205 – RTC Test example
─ Index ─ 19. Field User Test
163
iRTU, iGW & iRTUe Series User Manual
LEDs Test (key "e") This option allows testing the front panel LEDs: “A”, “B”, “C”, “D” and “STATE”. Enter one of the following keys in order to toggle the above LEDs:
Key “a”: LED “A” turns ON (green) when it is OFF, and turns OFF when it is ON. Key “b”: LED “B” turns ON (red) when it is OFF, and turns OFF when it is ON. Key “c”: LED “C” turns ON (red) when it is OFF, and turns OFF when it is ON. Key “d”: LED “D” turns ON (green) when it is OFF, and turns OFF when it is ON. While pressing the “r” key, LED “STATE” turns red. While pressing the “v” key, LED “STATE” turns green.
Figure 206 – LEDs Test example
USwitch Test (key "f") This options allows testing the configuration DIP switch (4 pins) located on the iRTU & iGW devices’ front panel (5.1.3).
Figure 207 – Uswitch Test example: in this example all 4 pins of the front panel switch are switched OFF (“1”)
Figure 208 – Uswitch Test example: in this example pins “1”, “2” and “3” of the front panel switch are switched OFF (“1”) and pin “4” is switched ON (“0”)
USB port Test (key "g") This test allows user to check the iRTU/iGW USB port. Plug an USB drive (with LED) into iRTU/iGW USB port, wait until the LED stops and then press any key. The test application will report the result of the test: “OK” or “FAILED”.
Figure 209 – USB port Test example
─ Index ─ 19. Field User Test
164
iRTU, iGW & iRTUe Series User Manual
I/O board firmware version Retrieves the firmware version of the internal I/O board of the iRTU devices.
Figure 210 – iRTU internal I/O board firmware version test example
19.1.2.
Communication ports tests
The tests within the Comms Tests section are intended to check the state of the iRTU & iGW serial ports. Some special cables and wiring (which will be described in the following sections) are required for passing each of the tests: COM1 mode RS-232 data test Use a connector for COM1 port (5.1.1, 5.1.1.1): Phoenix Contact MC 1,5/ 9-ST-3,5 (code no.: 1840434) terminal block. Interconnect the following pins (Figure 211):
1 (Rx) – 3 (Tx) 2 (CTS) – 4 (RTS) – 7(DCD) 5 (GND): not connected 6 (DSR) – 8 (DTR) – 9 (RI)
Figure 211 – COM1 port test pin connections
Plug the connector to the COM1 port, start the test by pressing the appropriate key, and follow the instructions given during the test (Figure 212).
Figure 212 – COM1 port, mode RS232 test
You should see COM1 Tx LED and COM1 Rx LED blinking during the test. If so, press “y” key to finish the test.
─ Index ─ 19. Field User Test
165
iRTU, iGW & iRTUe Series User Manual
COM1 mode RS-232 control lines test Follow same steps as described in previous section 19.1.2.1, and press the appropriate key to start the test. The test application will then report the result of the COM1 control lines test (“OK” or “FAILED”).
Figure 213 – COM1 port, mode RS232, control lines test
COM1 - COM2 mode RS-422 data test Create a RS422 crossed cable with the pin-out shown in Table 24. Use two Phoenix Contact MC 1,5/ 5ST-3,5 (code no.: 1840395) terminal blocks which are the connectors used for COM2 & COM3 serial ports (sections 5.1.1 and 5.1.1.2). Phoenix Contact (1)
Phoenix Contact (2)
Pin 1 (Rx+)
Pin 1 (Rx+)
Pin 2 (Rx-)
Pin 2 (Rx-)
Pin 3 (Tx-)
Pin 3 (Tx-)
Pin 4 (Tx+)
Pin 4 (Tx+)
Table 24 – RS422 cable pin out used for iRTU/iGW serial ports, mode RS422 data tests
Plug the connectors to the COM1 and COM2 ports, start the test by pressing the appropriate key, and follow the instructions given during the test (Figure 214).
Figure 214 – COM1 – COM2 ports, mode RS422 test
You should see COM1 Tx LED and COM2 Rx LED blinking during the test. If so, press “y” key to finish the test. COM2 - COM1 mode RS-422 data test Follow same steps as described in previous section 19.1.2.3, and press the appropriate key to start the test (Figure 215).
─ Index ─ 19. Field User Test
166
iRTU, iGW & iRTUe Series User Manual
Figure 215 – COM2 – COM1 ports, mode RS422 test
You should see COM2 Tx LED and COM1 Rx LED blinking during the test. If so, press “y” key to finish the test. COM1 - COM3 mode RS-422 data test Use the same RS422 crossed cable of section 19.1.2.3, plug the connectors to the COM1 and COM3 ports, and start the test by pressing the appropriate key (Figure 216).
Figure 216 –COM1 – COM3 ports, mode RS422 test
You should see COM1 Tx LED and COM3 Rx LED blinking during the test. If so, press “y” key to finish the test. COM3 - COM1 mode RS-422 data test Follow same steps as described in previous section 19.1.2.5, and press the appropriate key to start the test (Figure 217).
Figure 217 – COM3 – COM1 ports, mode RS422 test
You should see COM3 Tx LED and COM1 Rx LED blinking during the test. If so, press “y” key to finish the test. EXP422 data test Use a connector for EXP422 port (5.1.1, 5.1.1.3): MC 1,5/ 6-ST-3,5 (code no.: 1840405) or MC 1,5/ 5-ST3,5 (code no.: 1840395) terminal block.
─ Index ─ 19. Field User Test
167
iRTU, iGW & iRTUe Series User Manual
Interconnect the following pins:
1 (Rx+) – 4 (Tx+) 2 (Rx-) – 3 (Tx-) 5 (GND) and 6: not connected
Plug the connector to the EXP422 port, start the test by pressing the appropriate key, and follow the instructions given during the test (Figure 218).
Figure 218 – EXP422 data test
You should see EXP422 Tx LED and EXP422 Rx LED blinking during the test. If so, press “y” key to finish the test. Ethernet ports tests Connect the iRTU/iGW device by one of its Ethernet ports, start the test by pressing the appropriate key, and enter the IP address of a host (Figure 219). The iRTU/iGW device performs a ping test to this IP address. You should see Ethernet port Link LED on and Activity LED blinking during the test. If so, press “y” key to finish the test.
─ Index ─ 19. Field User Test
168
iRTU, iGW & iRTUe Series User Manual
Figure 219 – Ethernet ports test
19.1.3. I/O ports tests Figure 220 shows the menu of a C1 board I/O port test. The iRTU C1 I/O board is equipped with 8 digital inputs, 4 digital outputs, and 2 analog inputs. As shown in Figure 220 there is a different test for each I/O type:
Figure 220 – I/O ports test of iRTU C1 I/O board
Figure 221 shows the menu of a D1 board I/O port test. This test is used to check the 24 digital inputs of the D1 module.
Figure 221 – I/O ports test of iRTU D1 I/O board
─ Index ─ 19. Field User Test
169
iRTU, iGW & iRTUe Series User Manual
Digital input test This test allows the user to check that the digital inputs get On when applying the activation voltage. The test shows a “0” value at the deactivated digital inputs, and shows a “1” at the activated inputs. Refer to examples displayed in Figure 222 and Figure 223.
Figure 222 – Digital input ports test example (I): no digital input is activated
Figure 223 – Digital input ports test example (II): second and fourth digital inputs are activated
Digital output test The digital output test allows the user to continuously toggle the output relays and check their state after toggling. When the relay is activated, the test shows a “1” at the corresponding output (otherwise, it shows a “0”). User can also see that the LED besides the relay output in the frontal of the device is On when the relay is activated.
Figure 224 – Digital output ports test example (I)
Figure 225 – Digital output ports test example (II)
Analog input test Allows reading the current value at the analog input ports.
19.2. iRTUe user test The first step in the iRTUe device’s user test consist of entering the device serial number. After the serial number is typed, the iRTUe test menu is displayed including the following tests (Figure 226):
─ Index ─ 19. Field User Test
170
iRTU, iGW & iRTUe Series User Manual
Figure 226 – Example of field user test of an iRTUe-D1R1 device
iRTUe device address switch test (Figure 227). In order to set the switch, follow the instructions in section 12.4. Read firmware version of the I/O boards. Test the digital inputs, digital outputs and analog inputs as described in previous sections 19.1.3.1, 19.1.3.2 and 19.1.3.3, respectively.
Figure 227 – Example of field user test of an iRTUe-D1R1 device
─ Index ─ 19. Field User Test
171
iRTU, iGW & iRTUe Series User Manual
20. Dimensional outline drawings iRTU/iGW Series dimensions and weights are as follows:
External dimensions: 173 x 137 x 78.4 (mm) Weight (depending on model): from 600 gr to 1200 gr
Figure 228 – iRTU/iGW/iRTUe outline (dimensions in mm)
─ Index ─ 20. Dimensional outline drawings
172
iRTU, iGW & iRTUe Series User Manual
173
Figure 229 – iRTU/iGW/iRTUe outline (dimensions in mm)
─ Index ─ 20. Dimensional outline drawings
173
iRTU, iGW & iRTUe Series User Manual
78.4
173 Figure 230 – iRTU/iGW/iRTUe outline (dimensions in mm)
─ Index ─ 20. Dimensional outline drawings
174
iRTU, iGW & iRTUe Series User Manual
21. iRTU & iGW series type tests Title
Test Standard
Certifications APPLUS & LEITAT & UPC & PTEC & EEIFID & in-house test
Electrical Safety Insulation Resistance Test
UNE EN 60255-5 (Clause 6.2.2)
Voltage Impulse Test
UNE EN 60255-5 (Clause 6.1.3)
Dielectric Strength Test
UNE EN 60255-5 (Clause 6.1.4)
Creepage Distances Test
UNE EN 60255-5 (Clause 6.2.1)
Applied voltage: 500 Vdc Duration: 15 sec On power supply, telecom and I/O ports. Front time: 1,2 µs ± 30 % Time to half-value: 50 µs ± 20 % Output impedance: 500 Ω ± 10 % Output energy: 0,5 J ± 10 % Applied voltage: ± 4,8 kV Number of impulses: 5 in positive polarity and 5 in negative polarity Interval between impulses: at least 1 s On power supply, telecom and I/O ports. Applied voltage: 2,0 kV Frequency: 50 Hz Duration: 1 minute On power supply, telecom and I/O ports. Rated insulation voltage: 320 Vdc Pollution degree: 2 On power supply, telecom and I/O ports.
Electromagnetic compatibility Electrostatic Discharge Immunity
IEC 61000-4-2:2008
Radiated, radiofrequency, electromagnetic field Immunity
IEC 61000-4-3:2006 + A1:2007 + A2:2010
Electrical fast transient/burst Immunity
IEC 61000-4-4:2012
Surge Transients Immunity
IEC 61000-4-5:2014 Ed.3.0
Immunity to conducted disturbances, induced by radio-frequency fields
IEC 61000-4-6:2013
Criteria A/B Level Air: 8 kV Level Contact: 6 kV Criteria A Frequency range: 80 MHz - 1 GHz Severity: 10V/m Modulation: 80% AM 1 kHz Criteria A Severity level: 4 kV in power supply 2kV in telecom ports and I/O ports. Criteria A 1,2/50 µs Common mode severity: Power supply (line to ground): 4kV Telecom and I/O ports: 2kV Differential mode severity: Power supply (line to line), telecom ports and I/O ports: 2kV Criteria A Level of Severity: 10 V RMS Frequency range: 150 kHz - 80 MHz Modulation: 80% AM 1 kHz
─ Index ─ 21. iRTU & iGW series type tests
175
iRTU, iGW & iRTUe Series User Manual
Voltage Variations Immunity (interruptions and dips)
IEC 61000-4-29:2000 / UNE EN 61000-411:2005
Ring wave Immunity
IEC 61000-4-12:2006
Power Frequency Magnetic Field Immunity Pulse Magnetic Field Immunity Damped Oscillatory Magnetic Field Immunity 1 MHz burst Immunity High Voltage Impulse Conducted emissions Ripple on d.c. input power port Immunity Immunity to conducted, common mode disturbances, range 0 Hz to 150 kHz Electromagnetic emission tests for measuring relays and protection equipment, Radiated Emission
IEC 61000-4-8 IEC 61000-4-9
Criteria A Nominal voltage (Un): 230V/50Hz Short interruptions: 60% Un for 100 ms Voltage dips: 100% Un for 50 ms Criteria A 100 kHz & 1MHz: Common mode: 2,5 kV Differential mode: 1 kV Level 4 30 A/m – 50Hz Level 5 - 1000 A/m 5 pulses interval time 10s
IEC 61000-4-10
Level 4 - 30A/m
IEC 60255-22-1:2005
Class 3 -2.5 kV CM Class 3 -1.0 kV DM
IEC 60060-1/ UNE-EN 60255-5 UNE EN 55022:2011, UNE EN 55016-21:2009
5 kV - 0.5 j – 5 positive & 5 negative pulses Class A
IEC 61000-4-17
Criteria A Severity 3 10% Un
IEC 61000-4-16
Criteria A Severity 4 30V cont/ 300v 1seg / 0..150kHz
UNE-EN 6025525:2001
Pending (IEC 60255-26:2013 ED 3 currently)
Temperature
Cold
UNE-EN 60068-21:1996
Dry heat
UNE-EN 60068-22:1997
Damp heat, cyclic
UNE-EN 60068-230:2006
Change of temperature Damp heat (long term exposure)
UNE-EN 60068-2-14 UNE-EN 60068-2-3
Test A: Cold Cycle description: 2 h to reach -25°C ± 3°C 16 h at -25°C ± 3°C 2 h to reach a 25°C ± 3°C Test B: Dry heat Cycle description: 2 h to reach 70ºC ± 2ºC 16 h at 70ºC ± 2ºC 2 h to reach 25ºC Test Db: Damp heat, cyclic Cycle description: 3h to reach 55°C and (95-100)% r.h. 9h at 55°C and (95-100)% r.h. 3h to reach (22-28)°C and (95-100)% r.h. 9h at (22-28)°C and (95-100)% r.h. 2 days test with cycles between -10° C to +70° C continuous test at a steady temperature of 40°C and a relative humidity of 90-95%
─ Index ─ 21. iRTU & iGW series type tests
176
iRTU, iGW & iRTUe Series User Manual
Composite temperature/humidity cyclic test
UNE-EN 60068-2-38
10 days test with cycles from 24ºC to 65ºC with 93%RH
IEC 60068-2-6 IEC 60068-2-27
2g acceleration 9 to 350 Hz 15 g 11 ms
Storage Vibration (sinusoidal) Shock (inside packaging)
Table 25 – iRTU & iGW Type Tests
─ Index ─ 21. iRTU & iGW series type tests
177
iRTU, iGW & iRTUe Series User Manual
22. Ordering information This section describes ordering information for all iRTU & iGW Series products:
22.1. iRTU-B0 Series
Communication ports: o (4) serial ports (2.5 kVrms isolation) with TX/RX LED indicators: (1) Full RS232/RS422/RS485 serial port, software configurable (COM1 port). (2) Basic RS232/RS422/RS485 serial ports, software configurable (COM2 & COM3 ports). (1) RS422/RS485 serial port, software configurable (EXP422 port), for connection to iRTUe I/O expansion units. o (1) 10/100BaseTx Ethernet port (RJ45 connector). o (1) USB port to connect peripheral devices (e.g. USB drives). o (1) MGMT port (MiniUSB connector) to connect to a PC for local maintenance. o (1) MicroSD internal slot for data storage. Power supply options: o Wide range power supply: 32 - 250Vdc / 80 - 250Vac. o 24 Vdc power supply: 19.5-60Vdc. Internal I/O card options: o D1: 24 digital inputs. o C1: 8 digital inputs, 4 relay outputs and 2 DC current analog inputs. Digital inputs nominal voltage options: 24 Vdc, 48 Vdc, 110Vdc, 125 Vdc or 220Vdc.
Ordering information:
iRTU-B0Y-Z.V.U-S
Y: Internal I/O board options: - D1: (24) digital inputs. - C1: (8) digital inputs, 4 relay outputs (8A@250Vac) and 2 analog inputs @ 20mA. Z: Power supply options: - 24: 19.5 - 60 Vdc - W: 32 - 250 Vdc / 80 - 250 Vac V: Digital inputs nominal voltage options: 24, 48, 110, 125 or 220 Vdc. U: Analog inputs options: 20mA. S: Pre-installed internal industrial microSD card for data storage (optional): - 8: 8GB (SDCIT/8GBSP by Kingston or equivalent)
22.2. iGW-B0 Series
Communication ports: o (4) serial ports (2.5 kVrms isolation) with TX/RX LED indicators: (1) Full RS232/RS422/RS485 serial port, software configurable (COM1 port). (2) Basic RS232/RS422/RS485 serial ports, software configurable (COM2 & COM3 ports). (1) RS422/RS485 serial port, software configurable (EXP422 port), for connection to iRTUe I/O expansion units. o (1) 10/100BaseTx Ethernet port (RJ45 connector). o (1) USB port to connect peripheral devices (e.g. USB drives). o (1) MGMT port (MiniUSB connector) to connect to a PC for local maintenance. o (1) MicroSD internal slot for data storage. ─ Index ─
22. Ordering Information
178
iRTU, iGW & iRTUe Series User Manual
Power supply options: o Wide range power supply: 32 - 250Vdc / 80 - 250Vac. o 24 Vdc power supply: 19.5-60Vdc.
Ordering information:
iGW-B0-Z-S
Z: Power supply options: - 24: 19.5 - 60 Vdc - W: 32 - 250 Vdc / 80 - 250 Vac S: Pre-installed internal industrial microSD card for data storage (optional): - 8: 8GB (SDCIT/8GBSP by Kingston or equivalent)
22.3. iGW-B1 Series
Communication ports: o (2) serial ports (2.5 kVrms isolation) with TX/RX LED indicators: (1) Full RS232/RS422/RS485 serial port, software configurable (COM1 port). (1) Basic RS232/RS422/RS485 serial port, software configurable (COM2 port). o (1) 10/100BaseTx Ethernet port (RJ45 connector). o (1) USB port to connect peripheral devices (e.g. USB drives). o (1) MGMT port (MiniUSB connector) to connect to a PC for local maintenance. o (1) MicroSD internal slot for data storage. Power supply options: o Wide range power supply: 32 - 250Vdc / 80 - 250Vac. o 24 Vdc power supply: 19.5-60Vdc.
Ordering information:
iGW-B1-Z-S
Z: Power supply options: - 24: 19.5 - 60 Vdc - W: 32 - 250 Vdc / 80 - 250 Vac S: Pre-installed internal industrial microSD card for data storage (optional): - 8: 8GB (SDCIT/8GBSP by Kingston or equivalent)
22.4. iRTU-S3 Series
Communication ports: o Equipped with embedded Ethernet switch. o (4) serial ports (2.5 kVrms isolation) with TX/RX LED indicators: (1) Full RS232/RS422/RS485 serial port, software configurable (COM1 port). (2) Basic RS232/RS422/RS485 serial ports, software configurable (COM2 & COM3 ports). (1) RS422/RS485 serial port, software configurable (EXP422 port), for connection to iRTUe I/O expansion units. o (2) Ethernet 10/100BaseTX ports (RJ45 connector). o (2) Redundant 100BaseFX Ethernet ports. Available interfaces: Optical interface with SC or ST connectors, multimode fiber (62.5/125 µm and 50/125 µm) and 1300 nm wavelength. SFP (Small Form-factor Pluggable) interface. o (1) USB port to connect peripheral devices (e.g. USB drives). o (1) MGMT port (MiniUSB connector) to connect to a PC for local maintenance.
─ Index ─ 22. Ordering Information
179
iRTU, iGW & iRTUe Series User Manual
o (1) MicroSD internal slot for data storage. Power supply options: o Wide range power supply: 32 - 250Vdc / 80 - 250Vac. o 24 Vdc power supply: 19.5-60Vdc. Internal I/O card options: o D1: 24 digital inputs. o C1: 8 digital inputs, 4 relay outputs and 2 DC current analog inputs. Digital inputs nominal voltage options: 24 Vdc, 48 Vdc, 110Vdc, 125 Vdc or 220Vdc.
Ordering information: Y: Internal I/O board options: - D1: (24) digital inputs. - C1: (8) digital inputs, 4 relay outputs (8A@250Vac) and 2 analog inputs @ 20mA. Z: Power supply options: - 24: 19.5 - 60 Vdc - W: 32 - 250 Vdc / 80 - 250 Vac iRTU-S3 Y-Z.V.U-C-S V: Digital inputs nominal voltage options: 24, 48, 110, 125 or 220 Vdc. U: Analog inputs options: 20mA. C: FX100 connector options: ST, SC, or SFP. S: Pre-installed internal industrial microSD card for data storage (optional): - 8: 8GB (SDCIT/8GBSP by Kingston or equivalent)
22.5. iGW-S3 Series
Communication ports: o Equipped with embedded Ethernet switch. o (4) serial ports (2.5 kVrms isolation) with TX/RX LED indicators: (1) Full RS232/RS422/RS485 serial port, software configurable (COM1 port). (2) Basic RS232/RS422/RS485 serial ports, software configurable (COM2 & COM3 ports). (1) RS422/RS485 serial port, software configurable (EXP422 port), for connection to iRTUe I/O expansion units. o (2) Ethernet 10/100BaseTX ports (RJ45 connector). o (2) Redundant 100BaseFX Ethernet ports. Available interfaces: Optical interface with SC or ST connectors, multimode fiber (62.5/125 µm and 50/125 µm) and 1300 nm wavelength. SFP (Small Form-factor Pluggable) interface. o (1) USB port to connect peripheral devices (e.g. USB drives). o (1) MGMT port (MiniUSB connector) to connect to a PC for local maintenance. o (1) MicroSD internal slot for data storage. Power supply options: o Wide range power supply: 32 - 250Vdc / 80 - 250Vac. o 24 Vdc power supply: 19.5-60Vdc.
Ordering information:
iGW-S3-Z-C-S
Z: Power supply options: - 24: 19.5 - 60 Vdc - W: 32 - 250 Vdc / 80 - 250 Vac C: FX100 connector options: ST, SC, or SFP. S: Pre-installed internal industrial microSD card for data storage (optional): - 8: 8GB (SDCIT/8GBSP by Kingston or equivalent)
─ Index ─ 22. Ordering Information
180
iRTU, iGW & iRTUe Series User Manual
22.6. iRTU-M Series
Communication ports: o Equipped with 4G(LTE)/3G/GSM/GPRS built-in modem, with dual SIM card support: iRTU-M0: GPRS modem iRTU-M1: 3G modem iRTU-M2: 4G (LTE) modem o (3) serial ports (2.5 kVrms isolation) with TX/RX LED indicators: (2) Basic RS232/RS422/RS485 serial ports, software configurable (COM2 & COM3 ports). (1) RS422/RS485 serial port, software configurable (EXP422 port), for connection to iRTUe I/O expansion units. o (1) 10/100BaseTx Ethernet port (RJ45 connector). o (1) USB port to connect peripheral devices (e.g. USB drives). o (1) MGMT port (MiniUSB connector) to connect to a PC for local maintenance. o (1) MicroSD internal slot for data storage. Power supply options: o Wide range power supply: 32 - 250Vdc / 80 - 250Vac. o 24 Vdc power supply: 19.5-60Vdc. Internal I/O card options: o D1: 24 digital inputs. o C1: 8 digital inputs, 4 relay outputs and 2 DC current analog inputs. Digital inputs nominal voltage options: 24 Vdc, 48 Vdc, 110Vdc, 125 Vdc or 220Vdc.
Ordering information: X: M0: (1) ETH 10/100BaseTX, (1) GPRS modem, (2) Basic RS232/RS422/RS485, (1) RS422/RS485. M1: (1) ETH 10/100BaseTX, (1) 3G modem, (2) Basic RS232/RS422/RS485, (1) RS422/RS485. M2: (1) ETH 10/100BaseTX, (1) 4G modem, (2) Basic RS232/RS422/RS485, (1) RS422/RS485. Y: Internal I/O board options: - D1: (24) digital inputs. - C1: (8) digital inputs, 4 relay outputs (8A@250Vac) and 2 analog inputs @ 20mA. iRTU-XY-Z.V.U-S Z: Power supply options: - 24: 19.5 - 60 Vdc - W: 32 - 250 Vdc / 80 - 250 Vac V: Digital inputs nominal voltage options: 24, 48, 110, 125 or 220 Vdc. U: Analog inputs options: 20mA. S: Pre-installed internal industrial microSD card for data storage (optional): - 8: 8GB (SDCIT/8GBSP by Kingston or equivalent) N.B. Antenna and cable not included
22.7. iGW-M Series
Communication ports: o Equipped with 4G(LTE)/3G/GSM/GPRS built-in modem, with dual SIM card support: iGW-M0: GPRS modem iGW-M1: 3G modem iGW-M2: 4G (LTE) modem o (3) serial ports (2.5 kVrms isolation) with TX/RX LED indicators:
─ Index ─ 22. Ordering Information
181
iRTU, iGW & iRTUe Series User Manual
(2) Basic RS232/RS422/RS485 serial ports, software configurable (COM2 & COM3 ports). (1) RS422/RS485 serial port, software configurable (EXP422 port), for connection to iRTUe I/O expansion units. o (1) 10/100BaseTx Ethernet port (RJ45 connector). o (1) USB port to connect peripheral devices (e.g. USB drives). o (1) MGMT port (MiniUSB connector) to connect to a PC for local maintenance. o (1) MicroSD internal slot for data storage. Power supply options: o Wide range power supply: 32 - 250Vdc / 80 - 250Vac. o 24 Vdc power supply: 19.5-60Vdc.
Ordering information:
iGW-X-Z-S
X: M0: (1) ETH 10/100BaseTX, (1) GPRS modem, (2) Basic RS232/RS422/RS485, (1) RS422/RS485. M1: (1) ETH 10/100BaseTX, (1) 3G modem, (2) Basic RS232/RS422/RS485, (1) RS422/RS485. M2: (1) ETH 10/100BaseTX, (1) 4G modem, (2) Basic RS232/RS422/RS485, (1) RS422/RS485. Z: Power supply options: - 24: 19.5 - 60 Vdc - W: 32 - 250 Vdc / 80 - 250 Vac S: Pre-installed internal industrial microSD card for data storage (optional): - 8: 8GB (SDCIT/8GBSP by Kingston or equivalent) N.B. Antenna and cable not included
22.8. iRTUe Series
Communication with iRTU and iGW devices: o Serial RS422 port to connect to iRTU & iGW devices (EXP422 port) using Modbus RTU protocol. o Up to 7 iRTUe devices can be connected per RS422 bus I/O card options: o C1: 8 digital inputs, 4 relay outputs and 2 DC current analog inputs. o D1: 24 digital inputs. o R1: 8 relay outputs o A1: 8 analog inputs Power supply options: o Wide range power supply: 32 - 250Vdc / 80 - 250Vac. o 24 Vdc power supply: 19.5-60Vdc. Digital inputs nominal voltage options: 24 Vdc, 48 Vdc, 110Vdc, 125 Vdc or 220Vdc.
─ Index ─ 22. Ordering Information
182
iRTU, iGW & iRTUe Series User Manual
Ordering information:
iRTUe-X-Z.V-U
X: I/O module combination: - D1D1: (48) digital inputs - D1R1: (24) digital inputs + (8) relay outputs - D1A1: (24) digital inputs + (8) analog inputs - A1A1: (16) analog inputs - A1R1: (8) analog inputs + (8) relay outputs - R1: (8) relay outputs. Z: Power supply options: - 24: 19.5 - 60 Vdc - W: 32 - 250 Vdc / 80 - 250 Vac V: Digital inputs nominal voltage options: 24, 48, 110, 125 or 220 Vdc. U: Analog inputs options: 20mA.
22.9. iRTU & iGW communication capabilities and advanced functionalities All iRTU & iGW devices are supplied with a basic license that defines the communication capabilities of the device (i.e. number of IEDs/master stations, protocols and number of points). Depending on the customer requirements, the following options are available to be ordered:
Expansion of the basic license maximum number of IEDs and master stations. IEC61850 protocol (MMS client & server, GOOSE subscriber & publisher). Redundancy. IEC61131-3 automation.
22.10.
Connectoring kits
Following sections detail the connectoring kit (terminal blocks for serial ports, power supply and I/O) per iRTU/iGW/iRTUe model. Below references correspond to Phoenix Contact terminal blocks. Customer can use terminal blocks from Phoenix Contact or from other manufacturers with equivalent characteristics and quality.
22.10.1. iRTU-B0 Series connectoring kits iRTU/iGW Model
Description Includes the following terminal blocks:
iRTU-B0C1 connectoring kit
(1) MSTB 2,5/ 3-ST-5,08 (code no.: 1757022) for Power Supply. (1) MC 1,5/ 9-ST-3,5 (code no.: 1840434) for COM1 serial port. (2) MC 1,5/ 5-ST-3,5 (code no.: 1840395) for COM2 and COM3 serial ports. (1) MC 1,5/ 6-ST-3,5 (code no.: 1840405) for EXP422 serial port (3) MVSTBR 2,5/ 4-ST-5,08 (code no.: 1792265): 2 for relay outputs and 1 for analog input. (1) MVSTBR 2,5/ 9-ST-5,08 (code no.: 1792317) for digital inputs.
─ Index ─ 22. Ordering Information
183
iRTU, iGW & iRTUe Series User Manual
iRTU/iGW Model
Description Includes the following terminal blocks:
iRTU-B0D1 connectoring kit
(1) MSTB 2,5/ 3-ST-5,08 (code no.: 1757022) for Power Supply. (1) MC 1,5/ 9-ST-3,5 (code no.: 1840434) for COM1 serial port. (2) MC 1,5/ 5-ST-3,5 (code no.: 1840395) for COM2 and COM3 serial ports. (1) MC 1,5/ 6-ST-3,5 (code no.: 1840405) for EXP422 serial port (3) MVSTBR 2,5/ 9-ST-5,08 (code no.: 1792317) for digital inputs.
22.10.2. iGW-B0 Series connectoring kits iRTU/iGW Model
Description Includes the following terminal blocks:
iGW-B0 connectoring kit
(1) MSTB 2,5/ 3-ST-5,08 (code no.: 1757022) for Power Supply. (1) MC 1,5/ 9-ST-3,5 (code no.: 1840434) for COM1 serial port. (2) MC 1,5/ 5-ST-3,5 (code no.: 1840395) for COM2 and COM3 serial ports. (1) MC 1,5/ 6-ST-3,5 (code no.: 1840405) for EXP422 serial port
22.10.3. iGW-B1 Series connectoring kits iRTU/iGW Model
Description Includes the following terminal blocks:
iGW-B1 connectoring kit
(1) MSTB 2,5/ 3-ST-5,08 (code no.: 1757022) for Power Supply. (1) MC 1,5/ 9-ST-3,5 (code no.: 1840434) for COM1 serial port. (1) MC 1,5/ 5-ST-3,5 (code no.: 1840395) for COM2 serial port.
22.10.4. iRTU-S3 Series connectoring kits iRTU/iGW Model
Description Includes the following terminal blocks:
iRTU-S3C1 connectoring kit
(1) MSTB 2,5/ 3-ST-5,08 (code no.: 1757022) for Power Supply. (1) MC 1,5/ 9-ST-3,5 (code no.: 1840434) for COM1 serial port. (2) MC 1,5/ 5-ST-3,5 (code no.: 1840395) for COM2 and COM3 serial ports. (1) MC 1,5/ 6-ST-3,5 (code no.: 1840405) for EXP422 serial port (3) MVSTBR 2,5/ 4-ST-5,08 (code no.: 1792265): 2 for relay outputs and 1 for analog input. (1) MVSTBR 2,5/ 9-ST-5,08 (code no.: 1792317) for digital inputs.
─ Index ─ 22. Ordering Information
184
iRTU, iGW & iRTUe Series User Manual
iRTU/iGW Model
Description Includes the following terminal blocks:
iRTU-S3D1 connectoring kit
(1) MSTB 2,5/ 3-ST-5,08 (code no.: 1757022) for Power Supply. (1) MC 1,5/ 9-ST-3,5 (code no.: 1840434) for COM1 serial port. (2) MC 1,5/ 5-ST-3,5 (code no.: 1840395) for COM2 and COM3 serial ports. (1) MC 1,5/ 6-ST-3,5 (code no.: 1840405) for EXP422 serial port (3) MVSTBR 2,5/ 9-ST-5,08 (code no.: 1792317) for digital inputs.
22.10.5. iGW-S3 Series connectoring kits iRTU/iGW Model
Description Includes the following terminal blocks:
iGW-S3 connectoring kit
(1) MSTB 2,5/ 3-ST-5,08 (code no.: 1757022) for Power Supply. (1) MC 1,5/ 9-ST-3,5 (code no.: 1840434) for COM1 serial port. (2) MC 1,5/ 5-ST-3,5 (code no.: 1840395) for COM2 and COM3 serial ports. (1) MC 1,5/ 6-ST-3,5 (code no.: 1840405) for EXP422 serial port
22.10.6. iRTU-M Series connectoring kits iRTU/iGW Model
Description Includes the following terminal blocks:
iRTU-M0C1, iRTU-M1C1 & iRTU-M2C1 connectoring kit
(1) MSTB 2,5/ 3-ST-5,08 (code no.: 1757022) for Power Supply. (2) MC 1,5/ 5-ST-3,5 (code no.: 1840395) for COM2 and COM3 serial ports. (1) MC 1,5/ 6-ST-3,5 (code no.: 1840405) for EXP422 serial port (3) MVSTBR 2,5/ 4-ST-5,08 (code no.: 1792265): 2 for relay outputs and 1 for analog input. (1) MVSTBR 2,5/ 9-ST-5,08 (code no.: 1792317) for digital inputs. Includes the following terminal blocks:
iRTU-M0D1, iRTU-M1D1 & iRTU-M2D1 connectoring kit
(1) MSTB 2,5/ 3-ST-5,08 (code no.: 1757022) for Power Supply. (2) MC 1,5/ 5-ST-3,5 (code no.: 1840395) for COM2 and COM3 serial ports. (1) MC 1,5/ 6-ST-3,5 (code no.: 1840405) for EXP422 serial port. (3) MVSTBR 2,5/ 9-ST-5,08 (code no.: 1792317) for digital inputs.
─ Index ─ 22. Ordering Information
185
iRTU, iGW & iRTUe Series User Manual
22.10.7. iGW-M Series connectoring kits iRTU/iGW Model
Description Includes the following terminal blocks:
iGW-M series connectoring kit
(1) MSTB 2,5/ 3-ST-5,08 (code no.: 1757022) for Power Supply. (2) MC 1,5/ 5-ST-3,5 (code no.: 1840395) for COM2 and COM3 serial ports. (1) MC 1,5/ 6-ST-3,5 (code no.: 1840405) for EXP422 serial port
22.10.8. iRTUe Series connectoring kits iRTUe Model
Description Includes the following terminal blocks:
iRTUe-D1D1 connectoring kit
(1) MSTB 2,5/ 3-ST-5,08 (code no.: 1757022) for Power Supply. (1) MC 1,5/ 6-ST-3,5 (code no.: 1840405) for EXP422 serial port. (6) MVSTBR 2,5/ 9-ST-5,08 (code no.: 1792317) for digital inputs. Includes the following terminal blocks:
iRTUe-D1R1 connectoring kit
(1) MSTB 2,5/ 3-ST-5,08 (code no.: 1757022) for Power Supply. (1) MC 1,5/ 6-ST-3,5 (code no.: 1840405) for EXP422 serial port. (3) MVSTBR 2,5/ 9-ST-5,08 (code no.: 1792317) for digital inputs. (4) MVSTBR 2,5/ 4-ST-5,08 (code no.: 1792265) for relay outputs. Includes the following terminal blocks:
iRTUe-D1A1 connectoring kit
(1) MSTB 2,5/ 3-ST-5,08 (code no.: 1757022) for Power Supply. (1) MC 1,5/ 6-ST-3,5 (code no.: 1840405) for EXP422 serial port. (3) MVSTBR 2,5/ 9-ST-5,08 (code no.: 1792317) for digital inputs. (4) MVSTBR 2,5/ 4-ST-5,08 (code no.: 1792265) for analog inputs. Includes the following terminal blocks:
iRTUe-A1A1 connectoring kit
(1) MSTB 2,5/ 3-ST-5,08 (code no.: 1757022) for Power Supply. (1) MC 1,5/ 6-ST-3,5 (code no.: 1840405) for EXP422 serial port. (8) MVSTBR 2,5/ 4-ST-5,08 (code no.: 1792265) for analog inputs. Includes the following terminal blocks:
iRTUe-A1R1 connectoring kit
(1) MSTB 2,5/ 3-ST-5,08 (code no.: 1757022) for Power Supply. (1) MC 1,5/ 6-ST-3,5 (code no.: 1840405) for EXP422 serial port. (8) MVSTBR 2,5/ 4-ST-5,08 (code no.: 1792265): (4) for for analog inputs and (4) for relay outputs.
─ Index ─ 22. Ordering Information
186
iRTU, iGW & iRTUe Series User Manual
iRTUe Model
Description Includes the following terminal blocks:
iRTUe-R1 connectoring kit
(1) MSTB 2,5/ 3-ST-5,08 (code no.: 1757022) for Power Supply. (1) MC 1,5/ 6-ST-3,5 (code no.: 1840405) for EXP422 serial port. (4) MVSTBR 2,5/ 4-ST-5,08 (code no.: 1792265) for relay outputs.
─ Index ─ 22. Ordering Information
187
iRTU, iGW & iRTUe Series User Manual
ANNEX I: iAppManager version In order to verify if iAppManager application version is ≥ 3.0.0, a USB flash drive is required. These are the steps to follow to check the iAppManager version using a USB flash drive: N.B: Before starting, please, ensure that there is not any UPLOAD_CONF or UPLOAD_BIN folder in the USB drive. 1) Connect the USB drive to the USB port in the iRTU/iGW unit. 2) After 10-15 seconds, remove the USB drive from the iRTU/iGW unit and connect it to a USB port in the PC. 3) If iAppManager version is 3.0.0 or later, there will be an iRTU_info.txt file in the USB flash drive. The iRTU_info.txt file contains the version of the iAppManager and the network configuration of the device. Example of iRTU_info.txt file contents: Software versions ----------------- iAppManager version: 3.0.0 Network configuration --------------------- Adapter name: RNDISFN1 IP address: 10.10.10.100 Mask: 255.255.255.0 Gateway: MAC address: 82:00:60:0f:e8:00 - Adapter name: FEC1 IP address: 172.25.1.25 Mask: 255.255.255.0 Gateway: 172.25.1.1 MAC address: 00:0c:c6:7b:b9:7f
─ Index ─ ANNEX I. iAppManager version
188
iGrid T&D Marie Curie, 8-14 Parc Tecnològic 08042 – Barcelona (Spain) Telephone: +34 93 502 79 84 E-mail: [email protected] [email protected]