Table of Contents

Advertisement

PACiS GTW
Gateway
GTW/EN T/C40
Version :
4-5
Technical Guide

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the GTW/EN T/C40 and is the answer not in the manual?

Questions and answers

Summary of Contents for PACiS GTW GTW/EN T/C40

  • Page 1 PACiS GTW Gateway GTW/EN T/C40 Version : Technical Guide...
  • Page 3 Technical Guide GTW/EN T/C40 PACiS GTW gateway Page 1/2 PACiS GTW GATEWAY CONTENT Safety & Handling GTW/EN SA/C40 Technical Data GTW/EN TD/C40 Introduction GTW/EN IT/C40 Hardware Description GTW/EN HW/C40 Connection GTW/EN CO/C40 Installation GTW/EN IN/C40 Human Machine Interface GTW/EN HI/C40...
  • Page 4 GTW/EN T/C40 Technical Guide Page 2/2 PACiS GTW gateway BLANK PAGE...
  • Page 5 Safety & Handling GTW/EN SA/C40 PACiS GTW gateway SAFETY & HANDLING...
  • Page 7: Table Of Contents

    Safety & Handling GTW/EN SA/C40 PACiS GTW gateway Page 1/8 CONTENT INTRODUCTION SAFETY Health and Safety Explanation of symbols and labels Installing, Commissioning and Servicing Decommissioning and Disposal GUARANTIES COPYRIGHTS & TRADEMARKS Copyrights Trademarks WARNINGS REGARDING USE OF SCHNEIDER ELECTRIC...
  • Page 8 GTW/EN SA/C40 Safety & Handling Page 2/8 PACiS GTW gateway BLANK PAGE...
  • Page 9: Introduction

    Safety & Handling GTW/EN SA/C40 PACiS GTW gateway Page 3/8 INTRODUCTION The present document is a PACiS GTW gateway chapter of the documentation binders. It describes the safety, handling, packing and unpacking procedures applicable to PACiS GTW gateway software tools.
  • Page 10: Safety

    Optical power meters should be used to determine the operation or signal level of the device. Decommissioning and Disposal Disposal: It is recommended to avoid incineration and disposal of the PC and the communication network supporting PACiS GTW gatewayS. The products should be disposed of in a safe manner.
  • Page 11: Guaranties

    Safety & Handling GTW/EN SA/C40 PACiS GTW gateway Page 5/8 GUARANTIES The media on which you received Schneider Electric software are guaranted not to fail executing programing instructions, due to defects in materials and workmanship, for a period of 90 days from date of shipment, as evidenced by receipts or other documentation.
  • Page 12: Copyrights & Trademarks

    Schneider Electric. Trademarks PACiS, PACiS SCE, PACiS ES, PACiS SMT, PACiS PS, PACiS GTW, PACiS OI are trademarks of Schneider Electric. Product and company names mentioned herein are trademarks or trade names of their respective companies.
  • Page 13: Warnings Regarding Use Of Schneider Electric Products

    Safety & Handling GTW/EN SA/C40 PACiS GTW gateway Page 7/8 WARNINGS REGARDING USE OF SCHNEIDER ELECTRIC PRODUCTS Schneider Electric products are not designed with components and testing for a level of reliability suitable for use in or in connection with surgical implants or as critical components in any life support systems whose failure to perform can reasonably be expected to cause significant injuries to a human.
  • Page 14 GTW/EN SA/C40 Safety & Handling Page 8/8 PACiS GTW gateway BLANK PAGE...
  • Page 15: Technical Data

    Technical Data GTW/EN TD/C40 PACiS GTW gateway TECHNICAL DATA...
  • Page 17 Technical Data GTW/EN TD/C40 PACiS GTW gateway Page 1/14 CONTENT INTRODUCTION General features INDUSTRIAL PC CHARACTERISTICS Operating System Configuration Communication ports with SCADA Ethernet Communication port Rated Values DC auxiliary supply AC auxiliary supply Insulation Environmental 2.10 Mechanical 2.11 Safety 2.12...
  • Page 18 GTW/EN TD/C40 Technical Data Page 2/14 PACiS GTW gateway LIMITS AND PERFORMANCES Exchanging message with SCADA SBUS acquisition Time Performance SYSTEM DEPENDABILITY MTBF Availability...
  • Page 19: Introduction

    This document is a chapter of PACiS GTW gateway documentation binder. It is the chapter Technical Data (TD) of this Product. PACiS GTW gateway is a software package installed on an industrial PC or on a Non- rotating part Embedded PC to increase environmental capabilities. Technical characteristics of these PCs are described thereafter.
  • Page 20: Industrial Pc Characteristics

    GTW/EN TD/C40 Technical Data Page 4/14 PACiS GTW gateway INDUSTRIAL PC CHARACTERISTICS Operating System Gateway software is intended to run under an industrial PC running under Windows 2000Pro, Windows 2000 Server or Windows XP operating system with at least 256 Mo of RAM.
  • Page 21: Dc Auxiliary Supply

    Technical Data GTW/EN TD/C40 PACiS GTW gateway Page 5/14 DC auxiliary supply INTERNATIONAL TEST Harmonised STANDARD Supply variations IEC 60255-6 Vn +/- 20% Vn + 30% & Vn - 25% for information Ramp down to zero From Vn down to 0 within 1mn...
  • Page 22: Environmental

    GTW/EN TD/C40 Technical Data Page 6/14 PACiS GTW gateway Environmental INTERNATIONAL TEST Harmonised STANDARD Cold Operating IEC 60068-2-1 Test Ad: -10°C, 96h Cold Storage IEC 60068-2-1 Test Ad: -40°C, 96h Dry Heat Operating IEC 60068-2-2 Test Bd: +40°C, 96h, accurate +55°C, 2h, errors...
  • Page 23: Emc Tests

    Technical Data GTW/EN TD/C40 PACiS GTW gateway Page 7/14 2.12 EMC TESTS INTERNATIONAL TEST Harmonised STANDARD Electrostatic Discharge IEC 61000-4-2 Cover on: Class III: 8KV air discharge 6KV contact discharge RFI Immunity-radiated IEC 61000-4-3 Class III: 10V/m, 80 to 1000MHz Modulation: 1KHz, 80% Polarisation H &...
  • Page 24: Wiring

    PACiS GTW gateway 2.13 Wiring The connection with the PACiS GTW gateway is full compatible with standard RS232C. A SCADA communication can be establish on one serial port. One more serial port is needed for redundancy. A Null-Modem cable can be connected to a SCADA simulator or a Network Analyser.
  • Page 25: Operating System

    Technical Data GTW/EN TD/C40 PACiS GTW gateway Page 9/14 NON-ROTATING PART EMBEDDED PC CHARACTERISTICS Operating System Gateway software is intended to run under a dedicated non-rotating part Embedded PC with the following characteristics: • Model: ADVANTECH ARK-3382 fanless Embedded Box Computer •...
  • Page 26: Wiring

    For more information about the connection see the chapter CO. 3.7.2 Ethernet connection The connection with the PACiS GTW gateway is full compatible with standard 10/100 Mbps RJ45. A SCADA communication can be establish on one ethernet port. One more ethernet port is needed for redundancy.
  • Page 27: Software Gateway Characteristics

    Technical Data GTW/EN TD/C40 PACiS GTW gateway Page 11/14 SOFTWARE GATEWAY CHARACTERISTICS Number of Data Points Refer to § 1.1. Response time Time to receive a response after sending a request: 100ms SBUS Avalanche The linked list that manage events can memorise 15 000 events by protocol processes.
  • Page 28: Gi74 Characteritics

    GTW/EN TD/C40 Technical Data Page 12/14 PACiS GTW gateway GI74 CHARACTERITICS Operating System The GI74 software is intended to run under the bellow described industrial PC only running under VxWorks with a specific communication board (BCOM8+). Configuration The industrial PC where the GI74 is running has the following configuration...
  • Page 29 Technical Data GTW/EN TD/C40 PACiS GTW gateway Page 13/14 LIMITS AND PERFORMANCES Exchanging message with SCADA The responds time to a SCADA request whatever the protocol must be less than 30 milliseconds after the parameter settings phase for the parameters, synchronisation pre and post transmission times.
  • Page 30 GTW/EN TD/C40 Technical Data Page 14/14 PACiS GTW gateway SYSTEM DEPENDABILITY MTBF Device MTBF Industrial PC Gateway 50 000h Non rotating part embedded PC Gateway 72 000h TABLEAU 4: MTBF Availability Device MTTR (in minutes) Industrial PC Gateway 30 to 60...
  • Page 31 Introduction GTW/EN IT/C40 PACiS GTW Gateway INTRODUCTION...
  • Page 33 Introduction GTW/EN IT/C40 PACiS GTW Gateway Page 1/8 CONTENT INTRODUCTION INTRODUCTION TO PACiS GTW GATEWAYS' GUIDES Chapters description 2.1.1 Safety Chapter (SA) 2.1.2 Introduction Chapter (IT) 2.1.3 Functional Description Chapter (FT) 2.1.4 Technical Data Chapter (TD) 2.1.5 Communications Chapter (CT) 2.1.6...
  • Page 34 GTW/EN IT/C40 Introduction Page 2/8 PACiS GTW Gateway BLANK PAGE...
  • Page 35: Introduction

    Page 3/8 INTRODUCTION The present document is a chapter of the PACiS GTW Gateway documentation binder. It describes the documentation’s chapters you can find in the different guides, the types of applications and how to use the product. It is the Introduction (IT) chapter of this Product's...
  • Page 36: Introduction To Pacis Gtw Gateways' Guides

    Copyrights and Trademarks. 2.1.2 Introduction Chapter (IT) This is the present document, it contains the description of each chapter of the PACiS GTW Gateway guides. It presents a brief introduction to PACiS GTW Gateways capabilities. 2.1.3 Functional Description Chapter (FT) This chapter contains a description of the product.
  • Page 37: Record Sheet Chapter (Rs)

    PACiS GTW Gateway Page 5/8 2.1.11 Record Sheet Chapter (RS) This chapter contains record sheet to follow the maintenance of the PACiS GTW Gateway product. 2.1.12 Applications Chapter (AP) This chapter gives a comprehensive and detailed description of the features of the PACiS GTW Gateways product.
  • Page 38: Introduction To Pacis

    GTW/EN IT/C40 Introduction Page 6/8 PACiS GTW Gateway INTRODUCTION TO PACiS Schneider Electric philosophy is to provide a full range of products, computers, gateways and IEDs products. Each of these products can be used independently, or can be integrated to form a PACiS system: a Digital Control System (DCS) SCADA system.
  • Page 39: Gateway Environment

    PACiS GTW Gateway Page 7/8 Gateway environment The PACiS GTW Gateway is a dedicated device (PC TYPE): do not confuse it with the remote control interface function which may be included in the MiCOM C264 computers. DLL Protocol 1 DLL Protocol 1...
  • Page 40 GTW/EN IT/C40 Introduction Page 8/8 PACiS GTW Gateway BLANK PAGE...
  • Page 41 Hardware Description GTW/EN HW/C40 PACiS GTW gateway HARDWARE DESCRIPTION...
  • Page 43 Hardware Description GTW/EN HW/C40 PACiS GTW gateway Page 1/8 CONTENT INTRODUCTION INDUSTRIAL PC DESCRIPTION Concept Hardware overview PACiS GTW gateway Erreur ! Signet non défini. 2.3.1 Front panel overview 2.3.2 Rear panel description 2.3.3 Dimensions 2.3.4 Power supply FANLESS EMBEDDED PC DESCRIPTION...
  • Page 44 GTW/EN HW/C40 Hardware Description Page 2/8 PACiS GTW gateway BLANK PAGE...
  • Page 45: Introduction

    PACiS GTW gateway Page 3/8 INTRODUCTION This document is a chapter of PACiS GTW gateway documentation binder. It is the chapter Hardware Description (HW) of this Product. The gateway may be either an industrial PC or a Non-rotating part Embedded PC.
  • Page 46: Industrial Pc Description

    PACiS GTW gateway INDUSTRIAL PC DESCRIPTION Concept To increase environmental capabilities of the PACiS GTW gateway, it runs on an industrial PC. It is a steel rugged chassis specially designed to work under harsh environment for high reliability application. The hardware description of this PC configuration is done hereafter.
  • Page 47: Hardware Overview

    Hardware Description GTW/EN HW/C40 PACiS GTW gateway Page 5/8 Hardware overview Mother board 14 slots ISA/PCI 3 Com Ethernet board Station Bus (IEC61850 devices) Serial port board (2 ports) Remote connection to SCADA CPU board 2 serial ports Remote connection to SCADA...
  • Page 48: Rear Panel Description

    GTW/EN HW/C40 Hardware Description Page 6/8 PACiS GTW gateway 2.3.2 Rear panel description You will needed to take care of keeping some place for wiring connections. Video card Ethernet board CPU extension USB Mouse Serial DB 9 connector 14 ISA/PCI slots...
  • Page 49: Main Features

    Hardware Description GTW/EN HW/C40 PACiS GTW gateway Page 7/8 NON-ROTATING PART EMBEDDED PC DESCRIPTION Main features • Supplier: Advantech • Reference model: ARK-3382) • Processor: low voltage Intel Pentium 1.4 GHz • RAM: 992 MB • Compact Flash: 4 GB •...
  • Page 50: Rear Panel External I/O

    GTW/EN HW/C40 Hardware Description Page 8/8 PACiS GTW gateway Rear Panel External I/O LAN 4 LAN 2 LAN 3 kb/mouse COM 2 COM1 LAN 1 reset CF/card DC input S0159ENa...
  • Page 51 Connection GTW/EN CO/C40 PACiS Gateway CONNECTION...
  • Page 53 Connection GTW/EN CO/C40 PACiS Gateway Page 1/8 CONTENT INTRODUCTION CONNECTOR BLOCKS RJ 45 Station Bus connection DB9 Serial connection Null modem connection DB26 Serial connection Power supply connectors...
  • Page 54 GTW/EN CO/C40 Connection Page 2/8 PACiS Gateway BLANK PAGE...
  • Page 55: Introduction

    PACiS Gateway Page 3/8 INTRODUCTION The present document is a PACiS GTW Gateway chapter of the documentation binder. It describes the connections you will need to make with the gateway. It is the chapter Connection (CO) of this Product. To get further details about connections you can see the User’s Manual furnish with the...
  • Page 56: Connector Blocks

    PCs you must refer to the HW chapter. RJ 45 Station Bus connection To connect the PACiS GTW Gateway to the Station Bus (or to the SCADA through IEC 60870-5-104 protocol) you will need a RJ 45 male cable. You can see the details of the...
  • Page 57: Db9 Serial Connection

    PACiS Gateway Page 5/8 DB9 Serial connection To connect the PACiS GTW gateway to the modem dialling with the remote SCADA you will need a DB9 female cable. You can see the details of the connection below: Connector DB 9...
  • Page 58 GTW/EN CO/C40 Connection Page 6/8 PACiS Gateway FIGURE 4: SERIAL FEMALE DB26 CONNECTION This serial port connector assignment is given in the following table: Pin nb Signal Mnemonic Direction Protective Ground Transmit Data Output (A) Receive Data Input (A) Request To Send Output (A) Clear To Send Input (A)
  • Page 59: Power Supply Connectors

    Connection GTW/EN CO/C40 PACiS Gateway Page 7/8 Power supply connectors The industrial PC can be supply with tree types of power supply, 230 VAC, 110 VDC or 48 VDC. Case type of 230 VAC connector is standard connector. For case types of 48 VDC and 110 VDC power supply the connector is the following: FIGURE 5: POWER CONNECTOR In case of 110 VCD the –48V is replaced by –110VDC.
  • Page 60 GTW/EN CO/C40 Connection Page 8/8 PACiS Gateway BLANK PAGE...
  • Page 61 Installation GTW/EN IN/C40 PACiS Gateway INSTALLATION...
  • Page 63 Preparing the PC and installing XP Embedded 7.1.1 Connecting hardware 7.1.2 Starting the PC 7.1.3 Booting on CD 7.1.4 First start of the PC Installing the PACiS GTW software 7.2.1 File location 7.2.2 OSILLC driver 7.2.3 Parameterize T101 and/or T104 file transfer 7.2.4 Adding shortcuts 7.2.5...
  • Page 64 GTW/EN IN/C40 Installation Page 2/30 PACiS Gateway BLANK PAGE...
  • Page 65: Scope Of The Document

    PACiS GTW. The objective of this document is to install all needed to run the PACiS GTW. You will need to install the IEC 61850 agency, the protocol layers 1 and 2 (OSI model) and the software...
  • Page 66: Automatic Loging Configuration

    Page 4/30 PACiS Gateway AUTOMATIC LOGING CONFIGURATION At power on, the operating system starts. In order to start directly PACiS GTW application, it needs to be configured to log automatically. Automatic Loging Configuration in Windows 2000 operating system Launch the Control Panel Double-click in the “Users and Passwords”...
  • Page 67: Automatic Loging Configuration In Windows Xp Operating System

    Click to clear the “Require users to press Ctrl-Alt-Delete before logging on” check-box Automatic Loging Configuration in Windows XP operating system Right click on the icon of the PACiS GTW application: a sub-menu appears as described in the following figure. Left click on the item "Copy"...
  • Page 68 GTW/EN IN/C40 Installation Page 6/30 PACiS Gateway With Windows Explorer select the folder: C:\Documents and Settings\Gateway User\Start Menu\Programs\Startup (assumption is made that the folder of the user is named "Gateway User")
  • Page 69 Installation GTW/EN IN/C40 PACiS Gateway Page 7/30 Right click on this folder: a sub-menu appears as described in the following figure.
  • Page 70 GTW/EN IN/C40 Installation Page 8/30 PACiS Gateway Left click on the item "Paste". A shortcut to the PACiS GTW application is added to this folder. Restart the PC.
  • Page 71: Pacis Gateway Software Installation

    Page 9/30 PACiS GATEWAY SOFTWARE INSTALLATION Before installing a new release of the PACiS GTW, make a backup of registry, remove the previous release using the Windows “Add/Suppress programs” menu. Don't install the PACiS GTW firmware on the same PC as PACiS SMT applications (Client or Server).
  • Page 72 GTW/EN IN/C40 Installation Page 10/30 PACiS Gateway C:\Program Files\PACiS\Gateway In the "Select Destination Location" dialog box define the installation folder then click on the "Next" button ( the default installation folder is C:\Program Files\ PACIS\Gateway). By default a full installation is proposed (IEC 61850 SBUS Protocol and all SCADA protocols except GI74).
  • Page 73 Installation GTW/EN IN/C40 PACiS Gateway Page 11/30 Schneider Electric\PACiS\ In the "Select Start Menu Folder" dialog box choose where you want the program's shortcuts to placed then click on the "Next" button. In the "Select Additional Tasks" dialog box select if you want (or not) to create a desktop icon then click on the "Next"...
  • Page 74 GTW/EN IN/C40 Installation Page 12/30 PACiS Gateway C:\Program Files\Schneider Electric\PACiS\Gateway Check that the proposed settings are the correct ones and click on the "Install" button. If you selected SCADA Protocol OPC, the setup install and register OPC libraries and the server OPC. Click on the "OK" button. Do the same for these files: opchda_ps.dll, OPCProxy.dll and opc.dll...
  • Page 75 Finish button. If you want an automatic start of the PACiS GTW application at the PC launching, we have to add a PACiS GTW application shortcut in the Startup menu.
  • Page 76: Communication Software Installation

    Installation Page 14/30 PACiS Gateway COMMUNICATION SOFTWARE INSTALLATION The communication between the PACiS GTW and the Station Bus is based on the IEC 61850 agency. IEC 61850 Agency installation PACiS GTW setup wizard doesn't install the Agency software see SBUS/EN-IN.
  • Page 77: Scada Protocol Opc

    OPC libraries use DCOM technology and need to be registered in order to be found by a local or a remote system. The PACiS GTW setup installs and registers these libraries (only for Data Access) but it is possible you want install and register another version of these libraries.
  • Page 78 GTW/EN IN/C40 Installation Page 16/30 PACiS Gateway Select the "Default Properties" tab and match the configuration as below: Select the "Default Security" tab and do the following: In the "Default Access Permissions" frame add “Everyone” and “INTERACTIVE” entries and allow access...
  • Page 79 Installation GTW/EN IN/C40 PACiS Gateway Page 17/30 In the "Default Launch Permissions" frame add “Everyone” and “INTERACTIVE” entries and deny launch for every items...
  • Page 80 GTW/EN IN/C40 Installation Page 18/30 PACiS Gateway In the "Default Configuration Permissions" frame add “Everyone” and “INTERACTIVE” and give full control...
  • Page 81 In Applications sheet, select "OPC DATA IMPLEMENTATION” and click on "Properties". Then set the different sheets as the following snapshots: In the "General" tab check that the PACiS GTW application is in your working directory In the "Location" tab choose “Run application on this computer”...
  • Page 82 GTW/EN IN/C40 Installation Page 20/30 PACiS Gateway Don’t forget to click on the "Apply" button...
  • Page 83 Installation GTW/EN IN/C40 PACiS Gateway Page 21/30 In the "Identity" tab select “The interactive user” In the "Endpoints" tab add default system protocols...
  • Page 84: Dcom Configuration For Windows Xp

    GTW/EN IN/C40 Installation Page 22/30 PACiS Gateway DCOM Configuration for Windows XP Run DCOMcnfg.exe application from the Run window "Components°Services" dialog select ConsoleRoot\Components Services\Computers In the control panel right click on "My Computer" and select the "Properties" sub- menu item...
  • Page 85 Installation GTW/EN IN/C40 PACiS Gateway Page 23/30 In the "My Computer Properties" dialog box select the "COM Security" tab In the "Access Permissions" frame left click on the "Edit Limits" button...
  • Page 86 GTW/EN IN/C40 Installation Page 24/30 PACiS Gateway For "ANONYMOUS LOGON" allow "Local Access" and "Remote Access" then left click on "OK"...
  • Page 87 Installation GTW/EN IN/C40 PACiS Gateway Page 25/30 In the "Launch and Permissions" frame left click on the "Edit Limits" button For "Everyone" deny "Local Launch", "Remote Launch" then left click on "OK"...
  • Page 88: Time Synchonisation With Hopf

    GTW/EN IN/C40 Installation Page 26/30 PACiS Gateway TIME SYNCHONISATION WITH HOPF Integration of the Hopf 6039 board in the PC GTW. The date/time messages receive from SCADA allows to update the Hopf clock. This facility is available for CDC II, DNP3 and T101 protocols using a register key: only one key can be activated (i.e.
  • Page 89: Xp Embedded Installation

    PACiS Gateway Page 27/30 XP EMBEDDED INSTALLATION This section describes how to install XP Embedded and PACiS GTW software on a Fanless Embedded Box Computer ARK-3382. Main features of this computer are given in chapter GTW/ EN HW. Preparing the PC and installing XP Embedded 7.1.1...
  • Page 90: First Start Of The Pc

    C: is reserved for XP Embedded operating system. This partition will be protected by Enhanced Write Filter (EWF) to avoid writing on flash disk. D: is reserved for PACiS GTW software. 7.1.3.2 Copying XP Embedded files To copy XP Embedded files on flash media click on "Start/Schneider Electric/Copy XPEmbedded files"...
  • Page 91: Installing The Pacis Gtw Software

    File location When you select the installation folder choose "D:\Program Files\PACiS\Gateway" instead of "C:\Program Files\PACiS\Gateway" folder. Note that the PACiS GTW setup wizard will install agency too. For the agency choose "D:\Program Files\PACiS\" instead of "C:\Program Files\PACiS" folder. 7.2.2 OSILLC driver The OSILLC Driver is not used any more, to see the installation of SBUS 7.2.3...
  • Page 92 GTW/EN IN/C40 Installation Page 30/30 PACiS Gateway 7.2.6.1 Procedure to setup EWF On the D: we provide ewfntldr and ewf.reg files. Installation automatically: Rename the c:ntldr file to ntldr.bak. Move the d:\ewfntldr file to c:\ntldr. Merge the file d:\ewf.reg by double-clicking on it. Reboot the system.
  • Page 93 Human Interface GTW/EN HI/C40 PACiS GTW gateway HUMAN INTERFACE...
  • Page 95 Human Interface GTW/EN HI/C40 PACiS GTW gateway Page 1/12 CONTENT SCOPE OF THE DOCUMENT RUNNING THE GATEWAY GATEWAY INTERFACE “Equipment status” button “Digital status” button “Analog status” button “Bay status” button “Control history” button “Components Versions” button “Erase All” button “Protocols”...
  • Page 96 GTW/EN HI/C40 Human Interface Page 2/12 PACiS GTW gateway BLANK PAGE...
  • Page 97: Scope Of The Document

    Human Interface GTW/EN HI/C40 PACiS GTW gateway Page 3/12 SCOPE OF THE DOCUMENT This document is a chapter PACiS GTW gateway documentation binder. It describes the Human Interface (HI) of PACiS GTW gateway.
  • Page 98: Running The Gateway

    As all other executables programs, you just need to double click on the shortcut ”PACiS GTW gateway” in the desktop, to run it. Gateway‘s appearance looks like this: FIGURE 1: PACIS GTW GATEWAY DEFAULT WINDOW Check at beginning that there is no starting problem [initialisation problem, configuration problem, running the processes, ...] by checking information on the main application list box.
  • Page 99: Equipment Status" Button

    Human Interface GTW/EN HI/C40 PACiS GTW gateway Page 5/12 PACiS GTW GATEWAY INTERFACE “Equipment status” button This button allows you to access some information about equipment for example information coming from the configuration (like equipment type: computers, …) and some other information on the equipment states.
  • Page 100: Digital Status" Button

    GTW/EN HI/C40 Human Interface Page 6/12 PACiS GTW gateway “Digital status” button This button allows having some information about Digital Inputs. You just have to choose the desired server and the desired equipment with selecting them with the drop list boxes, and informations about these digital inputs are displayed.
  • Page 101: Analog Status" Button

    Human Interface GTW/EN HI/C40 PACiS GTW gateway Page 7/12 “Analog status” button This button allows having some information about Analog Inputs. You just have to choose the desired server and the desired equipment with selecting them with the droplist box, and informations about these analog inputs are displayed.
  • Page 102: Control History" Button

    GTW/EN HI/C40 Human Interface Page 8/12 PACiS GTW gateway “Control history” button This window is used to follow step by step what happen during the commands. This window is not refreshed automatically, but you can also refresh them immediately by clicking the ”Refresh”...
  • Page 103: Components Versions" Button

    Human Interface GTW/EN HI/C40 PACiS GTW gateway Page 9/12 Equipment reference X [network: N equipment: E] is not accessible because the associated bay is in SBMC mode. The equipment with reference X is not accessible with the Organes, because the associated bay is passed in SBMC Mode.
  • Page 104: Protocols" Information

    GTW/EN HI/C40 Human Interface Page 10/12 PACiS GTW gateway “Protocols” information This field is used to indicate which protocols are currently running: FIGURE 7: PROTOCOLS INFORMATION “About” information You can access the “About” information by clicking the “About” button. Information...
  • Page 105: Leaving The Program

    Human Interface GTW/EN HI/C40 PACiS GTW gateway Page 11/12 LEAVING THE PROGRAM You can normally leave the program by clicking the cross on the right upper corner of the window. Leaving may take some time. FIGURE 9: GATEWAY QUIT POP-UP...
  • Page 106 GTW/EN HI/C40 Human Interface Page 12/12 PACiS GTW gateway BLANK PAGE...
  • Page 107 Communication GTW/EN CT/C40 PACiS Gateway COMMUNICATION...
  • Page 109 Communication GTW/EN CT/C40 PACiS Gateway Page 1/64 CONTENT SCOPE OF THE DOCUMENT 870-5-101 IEC:1995-> 2001 EDITION 2 – INTEROPERABILITY System or device Network configuration (Network-specific parameter) Physical layer (Network-specific parameter) Link layer (Network-specific parameter) Protocol Requirements 2.5.1 Class 1 data 2.5.2 Class 2 data Application Functions...
  • Page 110 GTW/EN CT/C40 Communication Page 2/64 PACiS Gateway MODBUS Functions 4.4.1 Supported functions 4.4.2 General format of MODBUS functions 4.4.3 MODBUS Data Addresses Function 01 / 02: Read Coil Status – Read Input Status Function 03 / 04: Read Holding Registers / Input Registers 4.6.1 Signed normalised coding 4.6.2...
  • Page 111: Scope Of The Document

    Communication GTW/EN CT/C40 PACiS Gateway Page 3/64 SCOPE OF THE DOCUMENT This document is a chapter of PACiS Gateway (GTW) documentation binders. It describes the various standard communications protocols implemented of this PACiS Gateway. It is the chapter Communication (CT) of this Product. PACiS Gateway supports two different types of communications: •...
  • Page 112: System Or Device

    GTW/EN CT/C40 Communication Page 4/64 PACiS Gateway 870-5-101 IEC:1995-> 2001 EDITION 2 – INTEROPERABILITY This companion standard presents sets of parameters and alternatives from which subsets have to be selected to implement particular telecontrol systems. Certain parameter values, such as the number of bytes in the COMMON ADDRESS of ASDUs represent mutually exclusive alternatives.
  • Page 113: Link Layer (Network-Specific Parameter)

    Communication GTW/EN CT/C40 PACiS Gateway Page 5/64 Transmission speed (monitor direction): Unbalanced interchange Balanced interchange Unbalanced interchange circuit V.24/V.28 circuit V.24/V.28 circuit X.24/X.27, V35 Standard Recommended if >1 200 bit/s 100 bit/s 2 400 bit/s 2 400 bit/s 200 bit/s 4 800 bit/s 4 800 bit/s 300 bit/s...
  • Page 114: Protocol Requirements

    GTW/EN CT/C40 Communication Page 6/64 PACiS Gateway Protocol Requirements 2.5.1 Class 1 data The following types of information are to be configured at the controlled station to be Class 1: Single point information with or without time tag (on change) Double point information with or without time tag (on change) Step position information with or without time tag (on change) Measured value, normalised with or without time tag (on change)
  • Page 115 Communication GTW/EN CT/C40 PACiS Gateway Page 7/64 Controlled station failure If its register key is set to 1 the controlled station shall indicate to the Send_init_asdu_70 controlling station that it has initialised by sending a frame indicating End of Initialisation (ASDU 70) with a Cause of Initialisation (COI) field, which will identify the reason for the initialisation.
  • Page 116: Application Layer

    GTW/EN CT/C40 Communication Page 8/64 PACiS Gateway Command transmission All control/set point commands shall be Select before Execute, or Direct Execute. For only the set point commands: Activation termination (C_SE_ACTTERM) shall be returned to the controlling station to signal the end of a control sequence. This is configurable in Registry.
  • Page 117 Communication GTW/EN CT/C40 PACiS Gateway Page 9/64 Selection of standard ASDUs Process information in monitor direction (Station-specific parameter) <1>: = Single-point information M-SP-NA-1 <2>: = Single-point information with time tag M-SP-TA-1 <3>: = Double-point information M-DP-NA-1 <4>: = Double-point information with time tag M-DP-TA-1 <5>: = Step position information...
  • Page 118 GTW/EN CT/C40 Communication Page 10/64 PACiS Gateway Process information in control direction (station-specific parameter) <45>: = Single command C-SC-NA-1 <46>: = Double command C-DC-NA-1 <47>: = Regulating step command C-RC-NA-1 <48>: = Set point command normalised value C-SE-NA-1 <49>: = Set point command scaled value C-SE-NB-1 <50>: =...
  • Page 119 Communication GTW/EN CT/C40 PACiS Gateway Page 11/64 File transfer (station-specific parameter) <120>: = File ready F-FR-NA-1 <121>: = Section ready F-SR-NA-1 <122>: = Call directory, select file, call file, call section F-SC-NA-1 <123>: = Last section, last segment F-LS-NA-1 <124>: = Ack file, ack section F-AF-NA-1 <125>: =...
  • Page 120 GTW/EN CT/C40 Communication Page 12/64 PACiS Gateway Type ID Cause of transmission 10 11 12 13 20 44 45 46 47 <17> M_EP_TA_1 <18> M_EP_TB_1 <19> M_EP_TC_1 <20> M_PS_NA_1 <21> M_ME_ND_1 <30> M_SP_TB_1 <31> M_DP_TB_1 <32> M_ST_TB_1 <33> M_BO_TB_1 <34> M_ME_TD_1 <35>...
  • Page 121: Basic Application Functions

    Communication GTW/EN CT/C40 PACiS Gateway Page 13/64 Type ID Cause of transmission 10 11 12 13 20 44 45 46 47 <125> F_SG_NA_1 <126> F_DR_TA_1 * COT <45>:= Unknown Cause of Transmission Basic application functions Station initialisation (Station-specific parameter) Remote initialisation (Between Reset User ASDU’s).
  • Page 122 GTW/EN CT/C40 Communication Page 14/64 PACiS Gateway Counter General interrogation (System or station-specific parameter) global group 1 group 3 group 2 group 4 Clock synchronisation (Station-specific parameter) Clock synchronisation Notes: The controlling station cannot synchronize the system (includes controlled station) When the controlling station sends to controlled station a clock synchronisation,the clock synchronisation response is positive ( if register key equals 1) or...
  • Page 123 Communication GTW/EN CT/C40 PACiS Gateway Page 15/64 Parameter loading (Object-specific parameter) Threshold value Smoothing factor Low limit for transmission of measured value High limit for transmission of measured value Parameter activation (Object-specific parameter) Act/Desactivation of persistent cyclic or periodic transmission of the addressed object Test procedure (Station-specific parameter) Test procedure...
  • Page 124: System Or Device

    GTW/EN CT/C40 Communication Page 16/64 PACiS Gateway IEC 60870-5-104 PROFILE - INTEROPERABILITY This companion standard presents sets of parameters and alternatives from which subsets have to be selected to implement particular telecontrol systems. Certain parameter values, such as the choice of “structured” or “unstructured” fields of the INFORMATION OBJECT ADDRESS of ASDU represent mutually exclusive alternatives.
  • Page 125: Link Layer (Network-Specific Parameter)

    Communication GTW/EN CT/C40 PACiS Gateway Page 17/64 Transmission speed (monitor direction): Unbalanced interchange Balanced interchange Unbalanced interchange circuit V.24/V.28 circuit V.24/V.28 circuit X.24/X.27, V35 Standard Recommended if >1 200 bit/s 100 bit/s 2 400 bit/s 2 400 bit/s 200 bit/s 4 800 bit/s 4 800 bit/s 300 bit/s...
  • Page 126: Protocol Requirements

    GTW/EN CT/C40 Communication Page 18/64 PACiS Gateway Protocol Requirements 3.4.1 Event The following types of information are to be configured at the controlled station to be Event: Single point information with or without time tag (on change) Double point information with or without time tag (on change) Step position information with or without time tag (on change) Measured value, normalised with or without time tag (on change) Measured value, scaled with or without time tag (on change)
  • Page 127 Communication GTW/EN CT/C40 PACiS Gateway Page 19/64 Length of APDU (System-specific parameter) The maximum length of APDU is 253 (fixed) Selection of standard ASDUs Process information in monitor direction (Station-specific parameter) <1>: = Single-point information M-SP-NA-1 <2>: = Single-point information with time tag M-SP-TA-1 <3>: = Double-point information...
  • Page 128 GTW/EN CT/C40 Communication Page 20/64 PACiS Gateway Process information in control direction (station-specific parameter) <45>: = Single command C-SC-NA-1 <46>: = Double command C-DC-NA-1 <47>: = Regulating step command C-RC-NA-1 <48>: = Set point command normalised value C-SE-NA-1 <49>: = Set point command scaled value C-SE-NB-1 <50>: = Set point command, short floating point value C-SE-NC-1...
  • Page 129 Communication GTW/EN CT/C40 PACiS Gateway Page 21/64 Parameter in control direction (station-specific parameter) <110>: = Parameter of measured value, normalised value P-ME-NA-1 <111>: = Parameter of measured value, scaled value P-ME-NB-1 <112>: = Parameter of measured value, short floating point value P-ME-NC-1 <113>: = Parameter activation...
  • Page 130 GTW/EN CT/C40 Communication Page 22/64 PACiS Gateway Type ID Cause of transmission 10 11 12 13 20 44 45 46 47 <1> M_SP_NA_1 <2> M_SP_TA_1 <3> M_DP_NA_1 <4> M_DP_TA_1 <5> M_ST_NA_1 <6> M_ST_TA_1 <7> M_BO_NA_1 <8> M_BO_TA_1 <9> M_ME_NA_1 X <10>...
  • Page 131 Communication GTW/EN CT/C40 PACiS Gateway Page 23/64 Type ID Cause of transmission 10 11 12 13 20 44 45 46 47 <50> C_SE_NC_1 <51> C_BO_NA_1 <58> C_SC_TA_1 <59> C_DC_TA_1 <60> C_RC_TA_1 <61> C_SE_TA_1 <62> C_SE_TB_1 <63> C_SE_TC_1 <64> C_BO_TA_1 <70> M_EI_NA_1 <100>...
  • Page 132: Basic Application Functions

    GTW/EN CT/C40 Communication Page 24/64 PACiS Gateway Basic application functions Station initialisation (Station-specific parameter) Remote initialisation (Between Reset User ASDU’s). Cyclic data transmission (Station-specific parameter) Cyclic data transmission (It’s the same cyclic for all data). Read procedure (Station-specific parameter) Read procedure Spontaneous transmission (Station-specific parameter) Spontaneous transmission...
  • Page 133 Communication GTW/EN CT/C40 PACiS Gateway Page 25/64 General interrogation (System or station-specific parameter) Global Group 1 Group 7 Group 13 Group 2 Group 8 Group 14 Group 3 Group 9 Group 15 Group 4 Group 10 Group 16 Group 5 Group 11 Group 6 Group 12...
  • Page 134 GTW/EN CT/C40 Communication Page 26/64 PACiS Gateway Transmission of integrated totals (Station or object-specific parameter) Mode A: local freeze with spontaneous. Mode B: local freeze with counter. Mode C: freeze and transmit by counter interrogation. Mode D: freeze by counter interrogation command, frozen values reported. Counter read General request counter Counter freeze without reset...
  • Page 135 Communication GTW/EN CT/C40 PACiS Gateway Page 27/64 Acquisition of transmission delay (Station-specific parameter) Acquisition of transmission delay Management events priorities (Station-specific parameter) Digital Inputs, Step-position, Analogues Inputs and Integrated Totals, management events priorities. Definition of time outs Parameter Default value Remarks Selected value Time out of connection establishment...
  • Page 136: Soe File Management

    GTW/EN CT/C40 Communication Page 28/64 PACiS Gateway SOE file management The number of SOE files, SOE104 files, in the directory defined by keys Drive+Path is limited. When the limit is reached, the oldest file is replaced by a new one. A SOE file creation is divided into 3 steps: until the maximum number of events in a SOE number is reached, events are stored in a xxxx.tmp file, where xxxx is the IEC name (number in [1…65535],...
  • Page 137: Disturbance File Management

    Communication GTW/EN CT/C40 PACiS Gateway Page 29/64 CAUTION: IF THE DIRECTORY IS FULL, WHILE THE OLDEST FILE IS LOCKED BY SCADA (FILE SELECTED AND NOT ACKNOWLEDGED) IT IS NOT POSSIBLE TO RENAME THE NEW .TMP_READY IN .SOE104 IN THIS CASE, IF THIS SITUATION LAST A VERY LONG TIME, THE NUMBER OF .TMP_READY FILE CAN INCREASE, WITHOUT LIMIT.
  • Page 138: Modbus Profile

    GTW/EN CT/C40 Communication Page 30/64 PACiS Gateway MODBUS PROFILE The purpose of this chapter is to describe the support of the MODBUS RTU protocol in the PACiS system for Gateway PC. The MODBUS RTU protocol defines a message structure that controllers will recognise and use.
  • Page 139: Error Check Field

    Communication GTW/EN CT/C40 PACiS Gateway Page 31/64 4.1.4 Error check field The error-checking field contains a 16-bit value implemented as two 8-bit bytes [low significant byte first]. The error check value is the result of a Cyclical Redundancy Check [CRC] calculation performed on the message contents. The gateway does not reply to corrupted data messages, i.e when the CRC is not correct or when parity is not correct.
  • Page 140: Exception Responses Codes

    GTW/EN CT/C40 Communication Page 32/64 PACiS Gateway 4.2.2 Exception Responses Codes The exception code is sent as an 8-bit data, the range of valid codes is 1-8 in the protocol. Supported exception responses codes are: Code Name Meaning ILLEGAL The function code received in the query is not an allowable action for FUNCTION the slave.
  • Page 141: Serial Transmission Mode

    Communication GTW/EN CT/C40 PACiS Gateway Page 33/64 Serial transmission mode When messages are transmitted on standard MODBUS serial networks, each byte is sent LSB first. The format for each byte in MODBUS RTU mode is: Coding system: 8-bit binary, hexadecimal 0-9, A-F Two hexadecimal characters contained in each 8-bit field of the message Bits per Byte: 1 start bit,8 data bits, LSB sent first,2 stop bits if no parity, or 1 parity bit and 1 stop bit)
  • Page 142: General Format Of Modbus Functions

    GTW/EN CT/C40 Communication Page 34/64 PACiS Gateway 4.4.2 General format of MODBUS functions A query message typically contains some of the following 8-bit fields: − Starting Address Hi − Starting Address Lo − No. of Registers / Points Hi − No.
  • Page 143: Function 01 / 02: Read Coil Status - Read Input Status

    Communication GTW/EN CT/C40 PACiS Gateway Page 35/64 Function 01 / 02: Read Coil Status – Read Input Status The request function 01 or 02 reads the ON / OFF status of digital inputs in the slave. These status may be any digital points ( physical, automations, system information, grouping, … ). These two functions are the only way to read digital points with the MODBUS protocol.
  • Page 144: Signed Normalised Coding

    GTW/EN CT/C40 Communication Page 36/64 PACiS Gateway Query: Slave Function Starting Starting No. of No. of Address Code Address Address Points Points = 03 The query message specifies the starting register and the quantity of registers to be read. Response: Slave Functio Byte Count...
  • Page 145: Natural Coding

    Communication GTW/EN CT/C40 PACiS Gateway Page 37/64 4.6.3 Natural coding The natural coding is used to encode data without any calculation. That’s means that integer value will be send. Example: if the gateway receives the value 10.xxxx, the value 0Ah will be set in the appropriate register.
  • Page 146: Function 08: Diagnostic [Sub-Function 0 Only]

    GTW/EN CT/C40 Communication Page 38/64 PACiS Gateway Function 08: Diagnostic [Sub-function 0 only] This request function 08 sub-function 0 is used to test the transmission. Query: Slave Function Data Data Address Code Function Function code code = 08 The query message specifies the data that will be echoed. Response: Slave Function...
  • Page 147: Dnp3 Profile

    Communication GTW/EN CT/C40 PACiS Gateway Page 39/64 DNP3 PROFILE In this section is described the support of the DNP3 protocol in the PACiS system for Gateway PC. Device Name: PACIS Telecontrol Gateway Highest DNP Level Supported: Device Function: For Requests Level 3 Master Slave...
  • Page 148 GTW/EN CT/C40 Communication Page 40/64 PACiS Gateway Requires Data Link Layer Confirmation: Never Always Sometimes - If ’Sometimes’, when? ……………………………………………………………………………………………………….. ……………………………………………………………………………………………………….. Configurable If ’Configurable’, how? User option to set Data Link Confirmation to: • Always – device will always request Data Link Confirmations. •...
  • Page 149 Communication GTW/EN CT/C40 PACiS Gateway Page 41/64 Requires Data Link Layer Confirmation: Never Always Sometimes - If ’Sometimes’, when? ……………………………………………………………………………………………………….. ……………………………………………………………………………………………………….. Configurable If ’Configurable’, how? User option to set Data Link Confirmation to: • Always – device will always request Data Link Confirmations. •...
  • Page 150 GTW/EN CT/C40 Communication Page 42/64 PACiS Gateway Default Counter Object/Variation: Counters Roll Over at: No Counters Reported No Counters Reported Configurable (explanation below) Configurable (explanation below) Default Object _____20_______ 16 Bits Default Variation _____02_______ 32 Bits Point-by-point list attached Other Value _____________ Point-by-point list attached User option to return all static counters in one of the following variations:...
  • Page 151: Implementation Table

    Communication GTW/EN CT/C40 PACiS Gateway Page 43/64 Implementation table Not available informations are shaded. REQUEST RESPONSE OBJECT (slave must parse) (master must parse) Description Func Codes Qual Func Codes Qual Codes Codes (dec) (hex) (hex) Binary Input – All Variations 00,01,06 Binary Input 00,01,06...
  • Page 152 GTW/EN CT/C40 Communication Page 44/64 PACiS Gateway REQUEST RESPONSE OBJECT (slave must parse) (master must parse) Description Func Codes Qual Func Codes Qual Codes Codes (dec) (hex) (hex) 32-Bit Frozen Counter with Time of Freeze 16-Bit Frozen Counter with Time of Freeze 32-Bit Frozen Delta Counter with Time of Freeze...
  • Page 153 Communication GTW/EN CT/C40 PACiS Gateway Page 45/64 REQUEST RESPONSE OBJECT (slave must parse) (master must parse) Description Func Codes Qual Func Codes Qual Codes Codes (dec) (hex) (hex) 16-Bit Frozen Counter Event with Time 32-Bit Frozen Delta Counter Event with Time 16-Bit Frozen Delta Counter Event with Time...
  • Page 154 GTW/EN CT/C40 Communication Page 46/64 PACiS Gateway REQUEST RESPONSE OBJECT (slave must parse) (master must parse) Description Func Codes Qual Func Codes Qual Codes Codes (dec) (hex) (hex) 32-Bit Analog Output Status (2) 00,01,06 129,130 00,01 16-Bit Analog Output Status (2) 00,01,06 129,130 00,01...
  • Page 155 Communication GTW/EN CT/C40 PACiS Gateway Page 47/64 REQUEST RESPONSE OBJECT (slave must parse) (master must parse) Description Func Codes Qual Func Codes Qual Codes Codes (dec) (hex) (hex) Application Identifier Short Floating Point Long Floating Point Extended Floating Point Small Packed Binary-Coded Decimal Medium Packed Binary-Coded Decimal Large Packed Binary-Coded Decimal...
  • Page 156: Cdc Type 2: Telecontrol Messages

    GTW/EN CT/C40 Communication Page 48/64 PACiS Gateway CDC TYPE 2: TELECONTROL MESSAGES Telecontrol messages are the application data units that are exchanged on the CDC Type 2 WAN between the PACiS gateway and the SCADA in order to realise functions that are defined by the protocol.
  • Page 157: Opc Protocol

    Communication GTW/EN CT/C40 PACiS Gateway Page 49/64 OPC PROTOCOL Implementation All required OPC Interfaces are supported for both OPC 1.0 and OPC 2.0 Data Access Standards as well as the Browse Interface (OPC DA 2.05). The OPC Protocol basically operates as a data librarian. The controlling application creates Process Tags by passing a name and value to the DLL.
  • Page 158 GTW/EN CT/C40 Communication Page 50/64 PACiS Gateway Updating Process Tags A process tag is updated with: HANDLE TagHandle defines the datapoint (Process Tag), VARIANT Value defines the new datapoint value, WORD Quality defines the new Quality, FILETIME timestamp defines the UTC source timestamp of the datapoint (This structure is a 64-bit value representing the number of 100-nanosecond intervals since January 1, 1601).
  • Page 159 Communication GTW/EN CT/C40 PACiS Gateway Page 51/64 Substatus for UNCERTAIN Quality SSSS BIT VALUE DEFINE 010000LL Non-specific 010001LL Last Usable Value 010100LL Sensor Not Accurate 010101LL Engineering Units Exceeded 010110LL Sub-Normal 7-15 Substatus for GOOD Quality SSSS BIT VALUE DEFINE 110000LL Non-specific 110110LL...
  • Page 160: Opc Standard Layer

    GTW/EN CT/C40 Communication Page 52/64 PACiS Gateway OPC Standard layer This layer provides a way to access (read/write) to a set of data sources. The OPC Client connects to the OPC Server and communicates to it through the OPC interfaces. The OPC Server object provides functionality to the OPC client to create and manipulate group objects.
  • Page 161 Communication GTW/EN CT/C40 PACiS Gateway Page 53/64 IConnectionPointContainer This interface allows the client to retrieve connection points so it can setup callback mechanism for asynchronous communication from the server. As defined by the OPC specification the only callback mechanism available from the OPCServer is the IOPCSutdown interface.
  • Page 162: Opcgroup Object

    GTW/EN CT/C40 Communication Page 54/64 PACiS Gateway 7.2.2 OPCGroup object The OPC Group object is delivered by the server to manage a collection of items. The set of interfaces provided by this object includes: IOPCItemMgt IOPCGroupStateMgt IOPCSyncIO IOPCAsyncIO2 IConnectionPointContainer IOPCItemMgt This interface allows the client to add, remove and control the behaviour of items in the group.
  • Page 163 Communication GTW/EN CT/C40 PACiS Gateway Page 55/64 <<default>> <<coclass>> COMOPCGroup IHiddenOPCGroup IConnectionPointImpl SetDara() (from Connection Point) SetServerHandle() SetServer() SendData() Advise() ProcessAsyncIO() EnumConnections() <<Implements>> CheckName() GetConnectionInterface() GetConnectionPointContainer() SetMarkedForDeletion() Unadvise() EnumNextItems() EnumCanSkip() <<atlobject>> IConnectionPointContainerImpl CCOMOPCGroup (from ConnectionPoints) m_csItems : CComAutoCriticalSection m_ItemMap : ItemMap <<stdmethod>>...
  • Page 164: Opc Server Schneider Electric Specificities

    GTW/EN CT/C40 Communication Page 56/64 PACiS Gateway OPC server Schneider Electric specificities 7.3.1 Historization mechanism An historization mechanism is available in the OPC server. For each Digital Input a buffer of maximum ten changes of state allows to differ the transmission of the update to the OPC server.
  • Page 165: Iec 61850 Protocol

    Communication GTW/EN CT/C40 PACiS Gateway Page 57/64 IEC 61850 PROTOCOL General The following ACSI conformance statements shall be used to provide an overview and details about a device claiming conformance with ACSI: • ASCI basic conformance statement, • ACSI models conformance statement, •...
  • Page 166 GTW/EN CT/C40 Communication Page 58/64 PACiS Gateway ASCI basic conformance statement The basic conformance statement is defined in the following table. Table A.1 – Basic conformance statement Client/ Server/ Value/ Subscriber Publisher Comments Client-Server roles Server side (of TWO-PARTY-APPLICATION- ASSOCIATION) Client side of (TWO-PARTY-APPLICATION- ASSOCIATION) SCSMs supported...
  • Page 167 Communication GTW/EN CT/C40 PACiS Gateway Page 59/64 ACSI models conformance statement The ACSI models conformance statement are defined in the following table. Table A.2 – ACSI models conformance statement Client/ Server/ Value/ Subscriber Publisher Comments If Server side (B1) supported Logical device Logical node Data...
  • Page 168: Acsi Service Conformance Statement

    GTW/EN CT/C40 Communication Page 60/64 PACiS Gateway Client/ Server/ Value/ Subscriber Publisher Comments If SVC (41/42) is supported Multicast SVC Unicast SVC Time Time source with required accuracy shall be available File Transfer c1 – Shall be ‘M’ if support for LOGICAL-DEVICE model has been declared. c2 –...
  • Page 169 Communication GTW/EN CT/C40 PACiS Gateway Page 61/64 Services Client Server Comments TP/MC Data set (clause 11) GetDataSetValues SetDataSetValues CreateDataSet DeleteDataSet GetDataSetDirectory Substitution (clause 12) SetDataValues Setting group control (clause 13) SelectActiveSG SelectEditSG SetSGValues ConfirmEditSGValues GetSGValues GetSGCBValues Reporting (clause 14) Buffered report control block (BRCB) Report S24- data-change...
  • Page 170 GTW/EN CT/C40 Communication Page 62/64 PACiS Gateway Services Client Server Comments TP/MC Logging (clause 14) Log control block GetLCBValues SetLCBValues QueryLogByTime QueryLogByEntry GetLogStatusValues c7 – Shall declare support for at least one (QueryLogByTime or QueryLogByEntry). Generic substation event model (GSE) (clause 14.3.5.3.4) GOOSE-CONTROL-BLOCK SendGOOSEMessage GetReference...
  • Page 171 Communication GTW/EN CT/C40 PACiS Gateway Page 63/64 Services Client Server Comments TP/MC Control (clause 16.4.8) Select SelectWithValue Cancel Operate Command- Termination TimeActivated-Operate File transfer (clause 20) GetFile SetFile DeleteFile GetFileAttributeValues Time (clause 5.5) Time resolution of nearest negative power of 2 in internal clock seconds Time accuracy of...
  • Page 172 GTW/EN CT/C40 Communication Page 64/64 PACiS Gateway BLANK PAGE...
  • Page 173 Commissioning GTW/EN CM/C40 PACiS GTW gateway COMMISSIONING...
  • Page 175 Commissioning GTW/EN CM/C40 PACiS GTW gateway Page 1/4 CONTENT SCOPE OF THE DOCUMENT Introduction Requirements CHECKING SOFTWARE INSTALLATION...
  • Page 176 GTW/EN CM/C40 Commissioning Page 2/4 PACiS GTW gateway BLANK PAGE...
  • Page 177 PACiS GTW gateway Page 3/4 SCOPE OF THE DOCUMENT This document is a chapter of PACiS GTW Gateway documentation binders. It describes the commissioning of the product. This chapter follows the GTW/EN IN (Installation) chapter. Introduction The PACiS Gateway application will run on an industrial PC or on a Fanless Embedded Box PC.
  • Page 178 GTW/EN CM/C40 Commissioning Page 4/4 PACiS GTW gateway CHECKING SOFTWARE INSTALLATION As this product is a software application running on an industrial PC or on a Non-rotating part Embedded PC commissioning will consist of looking for the following files to be installed. For more details about the behaviour of this application see the chapter GTW/EN MF (Maintenance) of this product.
  • Page 179 Record Sheet GTW/EN RS/C40 PACiS GTW gateway RECORD SHEET...
  • Page 181 Record Sheet GTW/EN RS/C40 PACiS GTW gateway Page 1/6 CONTENT SCOPE OF THE DOCUMENT WORKSTATION CHARACTERISTICS PC Characteristics OS Characteristics INSTALLATION Software Delivery GTW Installation Installation checking 3.3.1 General Checking...
  • Page 182 GTW/EN RS/C40 Record Sheet Page 2/6 PACiS GTW gateway BLANK PAGE...
  • Page 183: Scope Of The Document

    Record Sheet GTW/EN RS/C40 PACiS GTW gateway Page 3/6 SCOPE OF THE DOCUMENT This document is a chapter of PACiS GTW gateway (GTW) documentation binder. It describes the Commissioning record sheet and the Setting Record (GTW/EN RS) of this PACiS equipment.
  • Page 184: Workstation Characteristics

    GTW/EN RS/C40 Record Sheet Page 4/6 PACiS GTW gateway WORKSTATION CHARACTERISTICS PC Characteristics PC Name Clock Frequency (GHz) RAM Size (Ko) OS Characteristics WINDOWS OS VERSION WINDOWS OS SERVICE PACK WINDOWS OS LANGUAGE...
  • Page 185: Installation

    PACiS GTW Release Note Checked: PACiS SBUS AGENCY VERSION IEC 61850 PACiS SBUS Agency IEC 61850 Release Note Checked: PACiS GTW Installation PACiS GTW Installed using GTW/EN IN Manual: PACiS GTW Installation directory: Standard (C:\Program Files\PACiS\Gateway) Other (precise): ____________________________ PACiS GTW Installation Choice:...
  • Page 186: Installation Checking

    3.3.1 General Checking Check that the following files or directories are in the correct path (cf. GTW/EN IN Manual): PACiS GTW version directory PACiS SBUS Agency IEC 61850 Check that the following items are in the Start Menu: PACiS GTW gateway PACiS SBUS Agency IEC 61850 3.3.1.1...
  • Page 187 Maintenance GTW/EN MF/C40 PACiS GTW gateway MAINTENANCE...
  • Page 189 Additional board Hopf for time synchronization FILES INSTALLED BY SETUP PROCEDURE Directory Ecdd1 and 2 Other executables and DLLs Data model file Debugging tools EXPLOITATION TRACES Translation of PACiS GTW’s ID tool Find the translation manually Run-time traces DIFFERENT COMPONENTS TO DEBUG. Traces LogBook Translatefile...
  • Page 190 8.1.1 Message dump 8.1.2 Tele-status Trace Format 8.1.3 Tele-measurement Trace Format Redundant Trace Format PACiS GTW kernel trace Format PACiS GATEWAY HMI Components versions Server Equipment Status Trace Format Digital Trace Format Analog Trace Format Command Trace Format Communication Trace Format...
  • Page 191 Maintenance GTW/EN MF/C40 Page 3/68 PACiS GTW gateway INSTALLATION TRANSLATEFILE 10.1 Translate File WATCHDOG.LOG CONFIGURATION FILES 12.1 Uca2_OMM.xml 12.2 Gateway.txt 12.3 Gateway_comp.txt 12.4 GTWIdToUca2 PORTMON 13.1 Installation PortMon 13.2 How to use 14.1 T101: How to convert T10x decimal address to structured address? 14.2...
  • Page 192 GTW/EN MF/C40 Maintenance Page 4/68 PACiS GTW gateway BLANK PAGE...
  • Page 193 (MF) procedures and tools of PACiS GTW debugging and traces. This chapter explains how to use the PACiS GTW registry allowing you to control the PACiS GTW behaviour and to recover from minor fails. It describes the files installed by the...
  • Page 194 Comment "st_SO_Lire" dword 2500 ms 5000 ms 30000 ms Time (in milliseconds) of reading an acquisition This key is created by the PACiS GTW’s kernel. "st_SO_Remon" dword 30 ms 15 ms 100 ms Time (in milliseconds) of polling an acquisition.
  • Page 195 NbDetectWDDefault "NbDetectWDDefault" dword Number of maximum consecutive detection of watchdog failure authorized before automatic reboot of the PC. The PACiS GTW 's setup wizard creates this key with the default value 3. "PeriodHeartBeat" dword 120 s Period in seconds of the IEC 61850 Agency’s HeartBeat = 0: no HeartBeat >...
  • Page 196 Comment "bd1" string "0.0" Version of the BD N°1 x.y: version.revision This value is entirely controlled by the PACiS GTW’s kernel. "bd2" string "0.0" Version of the BD N°2 x.y: bd version.revision This value is entirely controlled by the PACiS GTW’s kernel.
  • Page 197 "timer_log" dword 60 mn 1 mn 120 mn Time (in minutes) to display DI or AI in PACiS GTW logbook. In "DI log" or "analogue log" is checked, PACiS GTW display AI and or DI during this time. cot3_at_reconnexion dword Boolean that defines PACiS GTW behaviour in case of C264 connection /disconnection.
  • Page 198 GTW/EN MF/C40 Maintenance Page 10/68 PACiS GTW gateway GENECDD [HKEY_CURRENT_USER\Software\Gateway\GENECDD] Format Default Modifiable Comment "STRUCT_MAIN" dword Updated by genECDD.dll. Version of configuration structure. "STRUCT_REVISION" dword Updated by genECDD.dll Revision of configuration structure. Redundancy [HKEY_LOCAL_MACHINE\SOFTWARE\GATEWAY\PROTOCOL\REDUND] Format Default Modifiable Comment "redundantDll_datetime_Prot0" dword This information is used during checking on events data.
  • Page 199 1: Balanced mode 0: Unbalanced mode "balanced_mode_LinkTimeout" dword 2000 10000 This key defines, in balanced mode, a timeout between a PACiS GTW information frame and SCADA acknowledgement. "balanced_mode_nb_retry" dword This key defines, in balanced mode, maximum of repetition on non acknowledged frame...
  • Page 200 GTW/EN MF/C40 Maintenance Page 12/68 PACiS GTW gateway "Class_Event_tm" dword This key indicates the class used to send event measurements. When this value is set to 1, the Analogue Outputs are sent on a class 1 request. And when the value is set to 2, AO are sent on a class 2 request.
  • Page 201 Defines a timeout ( in seconds) of communication with SCADA. After this delay if the SCADA don't send any request. It's considered as disconnected. The PACiS GTW stop memorising AI without time-stamp in its database. In case of lost of communication this permit to avoid saturation of event stack.
  • Page 202 This key indicates, when a class is uploaded (1 or 2), that Pas_Data_Dispo_Sur_Class_En_C the PACiS GTW can switches to the other class is the case ours" that there are no data available on the first class. 1 if switching is authorised...
  • Page 203 Maintenance GTW/EN MF/C40 PACiS GTW gateway Page 15/68 "Flag_SQ_PA" dword This key indicates how the SQ bit is used when a PA is upload. 0: the SQ bit is forced to 0 1: the SQ bit is forced to 1 2: no forcing See key Max_Gaps_DP.
  • Page 204 "Invert_DI_Interlock" dword This parameter can take values 0 or 1. 0: indicates that the PACiS GTW does not reverse the state of the DI of interlock. It is the normal case. 1: the DI of interlock is reversed. This treatment allows or not the authorisation of the sending of command.
  • Page 205 REMOTE_RESET 2 The DLL IEC101 controls this value. "Reset_Process_Hard" dword When the PACiS GTW receives an ASDU ‘Reset Process’ two cases must be considered depending on the value of this key: 1: the operating system reboot 0: only the PACiS GTW reboot "Send_init_asdu_70"...
  • Page 206 Defines the maximum time (in milliseconds) that library T101 will wait for receiving all the datapoints from kernel. At the end of this time PACiS GTW starts communicating with SCADA. If key is 0 library waits till all datapoint are receieved.
  • Page 207 1: only bit NT(not topical) is set balanced_mode_Ack dword Boolean indicating the T101 acknowledgment mode in balanced mode. 1: PACiS GTW always acknowledge at link level , even if it waiting a scada acknowledgment. 0: PACiS GTW not reply to scada, if it waiting acknowledgmen "ClearEventsOnResetLink"...
  • Page 208 0: events are recorded in file with Cp24Time2a, 1: events are recorded in file with Cp56Time2a. "Delete_File_after_read dword Defines if a file is deleted or not by the PACiS GTW after reception of a positive file transfert acknowledgement from the SCADA 0: file not deleted 1: file deleted "Drive"...
  • Page 209 Maintenance GTW/EN MF/C40 PACiS GTW gateway Page 21/68 "Path" string "\\T101\\" Corresponds to the directory where the files are recorded. This value is used for the file transfer under IEC101. "PercentOfEventForFileSend" dword Gives the percentage of event number compared with NbMaxEvent.
  • Page 210 In this case, old events are lost. When communication is available the PACiS GTW indicates the lost of old event by a special DI. This key define the T101 address of the DI to send to SCADA.
  • Page 211 Maintenance GTW/EN MF/C40 PACiS GTW gateway Page 23/68 "Flag_Pa_Gestion_Event" dword 0: event generation is made according to each counter own configuration of “evt” “value in SCE. ( for memory value of “evt” can be “no event”, “event with time tag”, “event without time tag”).
  • Page 212 GTW/EN MF/C40 Maintenance Page 24/68 PACiS GTW gateway "Flag_SQ_TM" dword This key indicates how the SQ bit is used when a AI is upload. 0: the SQ bit is forced to 0 1: the SQ bit is forced to 1 2: no forcing See key Max_Gaps_DP.
  • Page 213 0: for counters Managed ment in mode A or B (in these modes the SCADA only reads counters values). In this case values received by PACiS GTW are considered as frozen values, and will be transmitted as received following a counter interrogation (no need of freeze command).
  • Page 214 Maintenance Page 26/68 PACiS GTW gateway "Reset_Process_Hard" dword When the PACiS GTW receives an ASDU ‘Reset Process’ two cases must be considered depending on the value of this key: 1: the operating system reboot 0: only the PACiS GTW reboot "TimeOut_Initialisation"...
  • Page 215 For the path access of registry keys, please consult the Schneider Electric technical support if needed. Format Default Modifiable Comment "synchro" dword Indicates if the PACiS GTW is synchronised with the system or not = 0: PACiS GTW is not synchronised = 1: PACiS GTW is synchronised Default value at creation process: 0...
  • Page 216 "UseDllsInterlockProt" dword Used to know if the check of the interlock operation is done in the kernel of the PACiS GTW or at the level of the DLL IEC101. = 0: Check is done in the protocol library = 1: Check is done in the kernel...
  • Page 217 Maintenance GTW/EN MF/C40 PACiS GTW gateway Page 29/68 IEC61850 [HKEY_CURRENT_USER\Software\Gateway\Protocol\IEC61850\Protx] Format Default Modifiable Comment "VALID_NON_COMP_00" dword Complementary state 00 validity for DI. 0 - Complementary state 00 is invalid. Flag quality 0x4000). 1 - Complementary state 00 is valid. Flag quality 0x0000).
  • Page 218 GTW/EN MF/C40 Maintenance Page 30/68 PACiS GTW gateway "DefaultVariationAnalogChgt" dword Define variation of AI as event: 0 - Analogue Input All Variations 1 - 32 Bits Analogue Change Event without Time 2 - 16 Bits Analogue Change Event without Time...
  • Page 219 Defines the maximum time (in milliseconds) that library T101 will wait for receiving all the data points from kernel. At the end of this time PACiS GTW start communicating with SCADA. If key is 0 library wait till all data point are received.
  • Page 220 PACiS GTW gateway 2.10 [HKEY_LOCAL_MACHINE\SOFTWARE\protocol\OPC\svritfc] Format Default Modifiable Comment "Exe_Name" String "tg_rcc.exe" NA Gives the name of the PACiS GTW executable for the OPC Server "Historic Timer" Dword "PIF_name" string "PERTE INFO" "Server Rate" dword The specified ServerRate defines how fast the OPC Client...
  • Page 221 Bit 1 = 1 => decode frame "cdcii_typeSCADA" dword 0 - Standard SCADA 1 - TPC / CHEM SCADA For TPC SCADA PACiS GTW wait SOE positive acknowledge during 5 seconds, after this delay, SOE are negative acknowledge "cdcii_Hopf_Present " dword if =1 indicates that a HOPF board 6039 is present and PACiS GTW have to write time.
  • Page 222 GTW/EN MF/C40 Maintenance Page 34/68 PACiS GTW gateway 2.12 Additional board Hopf for time synchronization T101 protocol: NOTE: For the path access of registry keys, please consult the Schneider Electric technical support if needed. DNP3 protocol: [HKEY_CURRENT_USER\Software\Te\Dnp3\Protx_COMy\Configuration] Key: "Hopf_present" - This indicates if a HOPF 6039 is present or not: 0 not present ;...
  • Page 223 Take a good care that this name must not be longer then 8 characters otherwise when you will launch the PACiS GTW executable it will reboot the PC. If it is not the case, just cut this name to 8 characters.
  • Page 224 For more details see the file readme.txt delivered with this tool. Just take care that this tool will run under the same PC where the PACiS GTW is installed so first be sure the PC’s has enough resources to run the tool.
  • Page 225 It is capable to translate protocol frame format data into user readable format. LogBook When a screen and a keyboard are connected to PACiS GTW-PC an HMI is displayed with a logbook. Logbook will help you to know product, components, configuration, protocols versions, status of equipments and transmitted Analog/Digital information, State of communication and Execute command status etc…...
  • Page 226 The Debugview software is automatically installed with the application PACiS GTW. It is recommended to create a shortcut on the desk of the PC PACiS GTW if setup does not create shortcut. To Create a shortcut use the following procedure.
  • Page 227 Maintenance GTW/EN MF/C40 Page 39/68 PACiS GTW gateway Parameter setting Menus, hot-keys, or toolbar buttons can be used to set parameters, clear the window, save the monitored data to a file, search output, change the window font, and etc. 6.3.1 Depth of History DebugView output is to limit the number of lines that are retained in the display.
  • Page 228 ‘*’ as a wildcard. Possibilities of various filters: UCA2 to filter traces the acquisition part of PACiS GTW bytes to filter that traces in hexadecimal of frames sent on the communication link...
  • Page 229 Maintenance GTW/EN MF/C40 Page 41/68 PACiS GTW gateway TG_RCC to filter that traces kernel PACiS GTW Etc, … To remove a filter, click “reset” then “OK”. Stop traces Use the Capture|Capture Events menu item, Toolbar button, or the Ctrl+E hot-key sequence to stop the traces for user to analyse the recording data.
  • Page 230 GTW/EN MF/C40 Maintenance Page 42/68 PACiS GTW gateway 6.5.2 Saving Output You can save the contents of the DebugView output window as a text file (.log extension) using the File|Save or File|Save As menu items, or the Ctrl+S hot-key sequence.
  • Page 231 Installation View Trace The Viewtrace software is automatically installed with the application PACiS GTW. It is recommended to create a shortcut on the desk of the PC PACiS GTW if setup not created shortcut. To Create a shortcut use the following procedure.
  • Page 232 GTW/EN MF/C40 Maintenance Page 44/68 PACiS GTW gateway Parameter setting and Use Menus , Buttons can be used to set parameters, clear the window, save the monitored data to a file, use the Filter, find the string (only if traces acquisition is stopped), and etc.
  • Page 233 Maintenance GTW/EN MF/C40 Page 45/68 PACiS GTW gateway Depth of History View Trace output is to limit the number of lines that are retained in the display. You use the NB events list box to select the history-depth. Select the number of output lines you want View trace to retain and it will keep only that number of the most recent debug output lines, discarding older ones.
  • Page 234 GTW/EN MF/C40 Maintenance Page 46/68 PACiS GTW gateway Select Protocol View Trace allows you to interpret protocol frames. You must at first select Protocols and set required properties. Use the File|Protocol|IEC101 or IEC104 or DNP3 menu item to activate properties dialog box.
  • Page 235 In viewtraces filter is case sensistive. Possibilities of various filters: UCA2 to filter traces the acquisition part of PACiS GTW bytes to filter that traces in hexadecimal of frames sent on the communication link MODBUS to filter that traces Modbus protocol...
  • Page 236 GTW/EN MF/C40 Maintenance Page 48/68 PACiS GTW gateway Start/Stop traces Use the Start Traces / Stop Traces button to start/stop the traces for user to analyse the recording data.
  • Page 237 Maintenance GTW/EN MF/C40 Page 49/68 PACiS GTW gateway Saving of traces To have View Trace log output to a file as it displays it, use the Save x button. Log file will record as traceX.txt where X is 0 to 65535.
  • Page 238 GTW/EN MF/C40 Maintenance Page 50/68 PACiS GTW gateway Comment File You can save the contents of the View Trace output window (only RX and TX) as a Comment File (.txt extension) using the File|Generate Comment File menu item.
  • Page 239 Maintenance GTW/EN MF/C40 Page 51/68 PACiS GTW gateway 7.10 Import File You can import an existing file to ViewTrace output window using the File|Import Fichier menu item. The content of this file will be appended to the existing content of the output windows (you...
  • Page 240 GTW/EN MF/C40 Maintenance Page 52/68 PACiS GTW gateway 7.11 Frame Analysis You can Analyze the protocol frame in details by clicking on frame. You will have details of frame on the lower windows. 7.12 Backup mode To memorise traces for a long period you can: launch ViewTrace click on "stop traces"...
  • Page 241 : Time stamp of the traces (format is different on viewtrace and dbgview) NNNNN : Name of Protocol ( : Protocol instance number : Received Bytes from SCADA : Transmitted Bytes from PACiS GTW : Number of Bytes XX XX XX XX : Data Frame Example:...
  • Page 242 GTW/EN MF/C40 Maintenance Page 54/68 PACiS GTW gateway 8.1.3 Tele-measurement Trace Format [HH:MM:SS:MS ] NNNNN[Z] [MajTm no_conf = nnn etat = SSS value = VVV init = YES/NO] HH:MM:SS:MS : Time stamp NNNNN : Name of Protocol : Protocol instance number...
  • Page 243 PACiS GTW gateway PACiS GTW kernel trace Format [HH:MM:SS:MS ] [NNNNN] xxxxx HH:MM:SS:MS : Time stamp of traces NNNNN : Name of PACiS GTW part (TG_RCC, UCA2_OMM …) Xxxxx : Message of the trace Example: [11:29:32:853] [SO_UCA2][callback]ODCOnReportReceived Time stamp of traces 11:29:32:853...
  • Page 244 Timestamp on the left part indicates the time when the traces in generated. Logbook Components versions While starting PACiS GTW records components information in Logbook. You can display this information using Components Versions button. If you write a fault or assistance report indicates, at least, the product version.
  • Page 245 If a server is connected or disconnected it is logged in the logbook part. HH:MM:SS:MS Server XXXXXX, Equipment Y is connected/ disconnected HH:MM:SS:MS : Time stamp indicating when the PACiS GTW was advertised of the connection change XXXXXX : Name of Server : Equipment number 1 for a C264 2and more fore an IED connected to C264.
  • Page 246 Maintenance Page 58/68 PACiS GTW gateway Analog Trace Format HH:MM:SS:MS Sending AI ident:X V INI PHYS ZZZ DD/MM/YYYY HH:MM:SS:MS HH:MM:SS:MS : Time stamp indicating when the PACiS GTW received the AI. : Point Number : Value DD/MM/YYYY : Date Example: 10:34:28:383 Sending AI ident:1307 UNKNOWN Value:0.000000...
  • Page 247 Maintenance GTW/EN MF/C40 Page 59/68 PACiS GTW gateway INSTALLATION TRANSLATEFILE The TranslateFile software is automatically installed with the application PACiS GTW. 10.1 Translate File TranslateFile allows you to select Microsol or standard file and set required protocol parameters. Click the “Traduire” button to translate file into User readable format. TranslateFile application Will read SOE file from specified location and translate into .gen file...
  • Page 248 2007:06:12 10:01:53 Detection Watchdog Thread [T_OMM_BD] code exception:0xc000008d This indicates that, on the 12 of June 2007, at 10 a clock, PACiS GTW kernel raised an exception to restart PACiS GTW software because it didn't received the heartbeat from agency.
  • Page 249 Since GTW version 5.2.6, code exception have been modified. Till this version, code is different depending of origin of the issue. There are two cases: internal exceptions: when the PACiS GTW detects an major error, this error will be logged in watchdog.log with the internal code...
  • Page 250 1 (resp. 2) indicates that current datatbase is the one in folder ECDD1 (resp. ECDD2) Example: BD1 =0.0. indicates that there is no database in ECDD1 folder. PACiS GTW is running with database version 18.2, installed in folder ECDD2. 12.2 Gateway.txt...
  • Page 251 How to use Stop PACiS GTW software if launched and work permit available. Launch Portmon before running PACiS GTW software. (double click on portmon.exe) Do CTRL+H to display the dialog box that permit to define the maximum number of events to memorize. Set it to 50000.
  • Page 252 14.3 Command & traces Question: How can I understand the reason of interpret the acknowledgment of a DO ? Reply: Traces of PACiS GTW gives you two indications: ack_uca Description Negative acknowledgement received Positive acknowledgement received on select Negative acknowledgement received on select...
  • Page 253 Maintenance GTW/EN MF/C40 Page 65/68 PACiS GTW gateway Signification of ack_uca in case of IEC61850 agency. Ack_uca Description UNKNOWN NOT SUPPORTED BLOCKED BY SWITCHING HIERARCHY: Topological interlocking ????, not supported by PACiS system at the moment SELECT FAILED INVALID POSITION...
  • Page 254 GTW/EN MF/C40 Maintenance Page 66/68 PACiS GTW gateway Ack_uca Description "Exec" command received on a "select Exec" device not selected before. Cancel operator received Time-out feedback DI NO execution of the order, Used in UCA used by the transformer: Time-out waiting DI TCIP present...
  • Page 255 Maintenance GTW/EN MF/C40 Page 67/68 PACiS GTW gateway Example3: At logbook level: 11:12:04:509 PROT# 1:Command structure information read: configuration ident:1017, Execute command, Open 11:12:04:509 Possible to control Organe 1017 by PROT#1. 11:12:04:509 It's a TC 1017 configured S/E side System, and D/E side Scada on PROT#1.
  • Page 256 GTW/EN MF/C40 Maintenance Page 68/68 PACiS GTW gateway BLANK PAGE...
  • Page 257 Problem Analysis GTW/EN PR/C40 PACiS GTW gateway PROBLEM ANALYSIS...
  • Page 259 Problem Analysis GTW/EN PR/C40 PACiS GTW gateway Page 1/4 CONTENT SCOPE OF THE DOCUMENT PROBLEM IDENTIFICATION...
  • Page 260 GTW/EN PR/C40 Problem Analysis Page 2/4 PACiS GTW gateway BLANK PAGE...
  • Page 261 PACiS GTW gateway Page 3/4 SCOPE OF THE DOCUMENT This document is a chapter of the PACiS GTW gateway documentation binder, describing the Problem Analysis (GTW/EN PR) of this product. This chapter is complement to Commissioning and Maintenance chapters. For any problem concerning this equipment contacts the Schneider Electric team at the following address: http://www.schneider-electric.com/CCC...
  • Page 262 IEC 61850 client or the right IP address. The IEC 61850 client is Database version in PACiS GTW and the IEC 61850 connected but all information are client “unknown” (case of the GTW...
  • Page 263 Functional Description GTW/EN FT/C40 PACiS Gateway FUNCTIONAL DESCRIPTION...
  • Page 265 Substation Remote/Local mode checking 3.4.2 SBMC mode checking 3.4.3 Taking Control Redundancy management COMMUNICATION LAYER Telecontrol bus Station bus Loss of communication SBUS ACQUISITION IEC 61850 acquisition IEC 61850 supported Common Class IEC 61850 Controls IEC61850/61850 PACiS GTW Redundant IEC61850/IEC61850 PACiS GTW...
  • Page 266 GTW/EN FT/C40 Functional Description Page 2/12 PACiS GTW gateway BLANK PAGE...
  • Page 267: Introduction

    SCADA. The implemented SCADA protocols are: • IEC 60870-5-101 • IEC 60870-5-104 • Serial link GI74 ( this protocol is not available if PACiS GTW OS is Windows XP Embedded) • Modbus • DNP3 • CDC type II (this protocol is not available if PACiS GTW OS is Windows XP Embedded) •...
  • Page 268: Process Interface

    To know the data to catch on SBUS and their respective mapping on SCADA Protocol, the PACiS GTW uses a current database loaded from its hard disk at start-up. A second or stand-by database is used for new database download while current is running.
  • Page 269: Pacis Gateway Management

    The database is a zip file that contains all data needed to operate the PACiS GTW. It is to be noticed that there is no on line settings or parameterisation of the PACiS GTW.
  • Page 270: Time Management

    When a bay is set in SBMC (it means that some tests are running on it), the supervisory data from the bay can be configured to be filtered by PACiS GTW to the SCADA. Since and while the bay is in SBMC, its data are transmitted to a “suppress SBMC” state to its SCADA link avoiding to transmit non-significant events.
  • Page 271: Communication Layer

    PACiS Gateway Station Bus (IEC-61850) IEC-61850 devices S0132ENb FIGURE 2: COMMUNICATIONS Telecontrol bus PACiS GTW behaves as a slave into master/slave protocol. The chapter CT gives the associate companion standard or supported function. Protocols: • GI-74 • IEC 60870-5-101 (T101) •...
  • Page 272: Station Bus

    Ethernet network). Loss of communication PACiS GTW stores SBUS data changes in its kernel. It is then able to answer quickly to any kind of query from a remote master. It is a key advantage when communication with SCADA is subject to disconnection and reconnection (PSTN network).
  • Page 273: Sbus Acquisition

    Interested readers can refer to SII document for REPORT mechanism. IEC 61850 supported Common Class PACiS GTW can pick up the following kind of data or common class on IEC 61850. Their conversion to SCADA protocol is function of the protocol used (MODBUS MODICON has no mechanism for time tag transmission, unknown state on IEC 61850 is converted by IV bit set on T101…).
  • Page 274: Iec 61850 Controls

    PACiS System defines Bypass controls on common control class by specific attribute. Bypass control has usually no equivalence on common SCADA protocol, also each bypass control that may need to be defined is treated as a specific protocol control. The PACiS GTW can manage only the synchrocheck bypass.
  • Page 275: Redundant Iec61850/Iec61850 Pacis Gtw

    • one PACiS GTW is master at one time: an IEC object ( RedSt : Redundancy status) is set for a master PACiS GTW and reset for a slave PACiS GTW. The PACiS GTWs are servers of this object.
  • Page 276 GTW/EN FT/C40 Functional Description Page 12/12 PACiS GTW gateway BLANK PAGE...
  • Page 277 Logical Diagram GTW/EN LG/C40 PACiS GTW gateway LOGICAL DIAGRAM...
  • Page 279 Logical Diagram GTW/EN LG/C40 PACiS GTW gateway Page 1/6 CONTENT INTRODUCTION LOGICAL DIAGRAM Internal Automation Order treatments...
  • Page 280 GTW/EN LG/C40 Logical Diagram Page 2/6 PACiS GTW gateway BLANK PAGE...
  • Page 281: Introduction

    Logical Diagram GTW/EN LG/C40 PACiS GTW gateway Page 3/6 INTRODUCTION The present document is a PACiS GTW Gateway chapter of the documentation binder. It is the chapter Logic Diagrams (LG) of this Product.
  • Page 282: Logical Diagram

    GTW/EN LG/C40 Logical Diagram Page 4/6 PACiS GTW gateway LOGICAL DIAGRAM Internal Automation PACiS GTW Gateway operates as an IEC 61850 application. The operating modes can be described as follows: Power on or Reset INITIALISATION [Init OK] [Init OK] [Current DB not valid]...
  • Page 283: Order Treatments

    Logical Diagram GTW/EN LG/C40 PACiS GTW gateway Page 5/6 Operator orders (received from the System Management Tool in point to point exchange): • Stop. • Run. • Switch DB: Stand-By DB becomes Current, and vice-versa. For more details about IEC 61850 applications please refer to the PACiS SII reference document.
  • Page 284 GTW/EN LG/C40 Logical Diagram Page 6/6 PACiS GTW gateway BLANK PAGE...
  • Page 285 Glossary GTW/EN LX/C40 PACiS GTW gateway GLOSSARY...
  • Page 287 Glossary GTW/EN LX/C40 PACiS GTW gateway Page 1/10 CONTENT INTRODUCTION LEXICAL...
  • Page 288 GTW/EN LX/C40 Glossary Page 2/10 PACiS GTW gateway BLANK PAGE...
  • Page 289 Glossary GTW/EN LX/C40 PACiS GTW gateway Page 3/10 INTRODUCTION The present document is a PACiS Gateway (GTW°)chapter of the documentation binder. It is the lexical chapter (LX) of this Product.
  • Page 290 GTW/EN LX/C40 Glossary Page 4/10 PACiS GTW gateway LEXICAL Alternative Current Analogue to Digital Converter Analogue Input (Measurement Value including state attribute) Commonly Voltage or current DC signals delivered by transducers, and representing an external value (refer to CT/VT for AC).
  • Page 291 Glossary GTW/EN LX/C40 PACiS GTW gateway Page 5/10 DataBase Tool or set of data that define all configuration of a system or specific device like computer. Opposed to setting or parameter DB has a structure that can not be modified on line. DB are always versioned.
  • Page 292 GTW/EN LX/C40 Glossary Page 6/10 PACiS GTW gateway Factory Acceptance Test Validation procedures execution with the customer at factory.(SAT) Functional Block Diagram One of the IEC61131-3 programming languages (language used to define configurable automation). Gateway Level 6 session of OSI, the gateway is any device transfering data between different networks and/or protocol.
  • Page 293 Glossary GTW/EN LX/C40 PACiS GTW gateway Page 7/10 Ladder Diagram One of the IEC1131-3 programming languages (language used to define configurable automation). Light Emitting Diode Low Frequency Local Operator Console dedicated to maintenance operation When set to local for a given control point it means that the...
  • Page 294 GTW/EN LX/C40 Glossary Page 8/10 PACiS GTW gateway Object Linking and Embedding OLE is a Microsoft specification and defines standards for interfacing objects. OLE for Process Control OPC is a registered trademark of Microsoft, and is designed to be a method to allow business management access to plant floor data in a consistent manner.
  • Page 295 Glossary GTW/EN LX/C40 PACiS GTW gateway Page 9/10 SBMC Site Based Maintenance Control mode A bay in SBMC mode does not take into account the commands issued from RCP; moreover, some of its digital points and measurements (defined during the configuration phase) are not sent anymore to the RCP (they are “...
  • Page 296 GTW/EN LX/C40 Glossary Page 10/10 PACiS GTW gateway Suppression (Automatic) A binary information belonging to a bay in SBMC mode will be automatically suppressed for the remote control. However changes of state will be signalled locally, at SCP. A binary information can be suppressed by an order issued from Suppression (Manual) an operator.
  • Page 298 Customer Care Centre http://www.schneider-electric.com/CCC Schneider Electric 35 rue Joseph Monier 92506 Rueil-Malmaison FRANCE Phone: +33 (0) 1 41 29 70 00 Fax: +33 (0) 1 41 29 71 00 www.schneider-electric.com Publishing: Schneider Electric Publication: GTW/EN T/C40 03/2011...

Table of Contents