Configuration & Startup of Saitel DP_EN_Rev3.1

Saitel DP Configuration & Startup 09/2016

www.schneider-electric.com

Rev. 3.1 (01-09-2016)

Change Control Rev

Date

3.1

01-09-2016

3.0

09-12-2014

Description 

Included information information about use use of the module SM_CPU866e.



Included information information about LED LED meanings and compact-flash compact-flash use. use.



Easergy Builder is used as configuration tool. tool.

Initial edition of the manual.

General Information The Saitel platform and all its components have been developed in accordance to the requirements for a quality management system, complying with the ISO 9001 Norm. The Saitel platform and all its components have been developed in accordance to the requirements for a quality management system, complying with the ISO 9001 Norm. Document nº:

TE-HG-0000-CYP-F700

Revision/Date:

Rev 3.1 / 01-09-2016

File:

Configuration & Startup of Saitel DP_EN_Rev3.1.pdf

Retention period:

Permanent throughout its validation period + 3 years after its cancellation.

NOTICE In case of any further queries , please, send an e-mail about the problem or suggestion to the following address: [email protected]

Configuration & Startup Saitel DP

1

Rev. 3.1 (01-09-2016)

Table of Contents Table of Contents ................................................................ ................................................................ .................................. 2 Index of Figures.............................................................................. ............................................................... ........................ 4 Index of Tables..................................... ............................................................... ................................................................ .. 6 Contents............... ................................................................ ............................................................... .................................. 7 Chapter Chapter 1.

Safety & Health.......... Health................. .............. ............. ............. .............. ............. ............. ............. ............. .............. ............. ............. .............. ............. ............. ............. ............. .............. ............. ......... ... 1-1

1.1

Introductio Introduction....... n............. ............. .............. ............. ............. ............. ............. .............. ............. ............. .............. ............. ............. ............. ............. .............. ............. ............. .............. ............. ............. ............. ........ 1-1

1.2

Restricted Restricted Liability ............. .................... .............. ............. ............. .............. ............. ............. ............. ............. .............. ............. ............. .............. ............. ............. ............. ............. .............. ............. ......... ... 1-1

1.3

Handling Handling Electronic Electronic Componen Components ts ............. ................... ............. .............. ............. ............. ............. ............. .............. ............. ............. .............. ............. ............. ............. ............. ..............1-2 .......1-2

1.4

Installation Installation and Operation.. Operation......... .............. ............. ............. .............. ............. ............. ............. ............. .............. ............. ............. .............. ............. ............. ............. ............. .............. ............. ......... ... 1-2

1.5

Protectiv Protective e Grounding..... Grounding............ ............. ............. .............. ............. ............. ............. ............. .............. ............. ............. .............. ............. ............. ............. ............. .............. ............. ............. ..............1-3 .......1-3

1.5.1

Electric Electric Safety....... Safety.............. ............. ............. ............. ............. .............. ............. ............. .............. ............. ............. ............. ............. .............. ............. ............. .............. ............. ............. ............. ........ .. 1-4

1.5.2

EMC ............ ................... ............. ............. .............. ............. ............. ............. ............. .............. ............. ............. .............. ............. ............. ............. ............. .............. ............. ............. .............. ............. .......... .... 1-4

1.6

Replacing Replacing the Battery Battery and Recicling Recicling the Product Product ........ .............. ............. ............. ............. .............. ............. ............. .............. ............. ............. ............. ............. .............. ......... 1-5

Chapter Chapter 2.

Baseline Baseline Software Software Platform Platform .............. .................... ............. .............. ............. ............. ............. ............. .............. ............. ............. .............. ............. ............. ............. ............. ..............2-1 .......2-1

2.1


2.2

Main Elements..... Elements............ ............. ............. .............. ............. ............. ............. ............. .............. ............. ............. .............. ............. ............. ............. ............. .............. ............. ............. .............. ............. .......... .... 2-3

2.3

Software Software Tools ................. ........................ .............. ............. ............. ............. ............. .............. ............. ............. .............. ............. ............. ............. ............. .............. ............. ............. .............. ............. .......... .... 2-4

Chapter Chapter 3.

Physical Physical Mounting Mounting ............. .................... ............. ............. .............. ............. ............. .............. ............. ............. ............. ............. .............. ............. ............. .............. ............. ............. ............. ........ .. 3-1

3.1


3.2

Handling Handling ............. .................... ............. ............. ............. ............. .............. ............. ............. .............. ............. ............. ............. ............. .............. ............. ............. .............. ............. ............. ............. ............. ............ ..... 3-1

3.3

Module Module Location Location within within the Chassis Chassis ............. .................... ............. ............. .............. ............. ............. ............. ............. .............. ............. ............. .............. ............. ............. ............. ......... ... 3-1

3.4

Power Power Requirement Requirements s ............. ................... ............. .............. ............. ............. .............. ............. ............. ............. ............. .............. ............. ............. .............. ............. ............. ............. ............. ............. ...... 3-2

3.5

Polarizatio Polarization n and Commons Commons .............. ..................... ............. ............. ............. ............. .............. ............. ............. .............. ............. ............. ............. ............. .............. ............. ............. .............. ......... 3-2

3.6

Configurati Configuration on Switches...... Switches............. .............. ............. ............. .............. ............. ............. ............. ............. .............. ............. ............. .............. ............. ............. ............. ............. .............. ............. ......... ... 3-2

3.6.1

I/O Modules Modules - Identificati Identification on and Profibu Profibus s Speed..... Speed............ ............. ............. ............. ............. .............. ............. ............. .............. ............. ............. ............. ........... ..... 3-2

3.6.2

Communic Communication ation Modules Modules - Identific Identification...... ation............ ............. .............. ............. ............. .............. ............. ............. ............. ............. .............. ............. ............. .............. ......... .. 3-3

3.6.3

CPU Modules Modules – Configur Configuration............ ation................... ............. ............. ............. ............. .............. ............. ............. .............. ............. ............. ............. ............. .............. ............. ........... ..... 3-3

3.7

LED Indicators...... Indicators............. ............. ............. .............. ............. ............. .............. ............. ............. ............. ............. .............. ............. ............. .............. ............. ............. ............. ............. .............. ............. ......... ... 3-4

3.7.1

SM_CPU866 SM_CPU866 .......... ................. ............. ............. .............. ............. ............. .............. ............. ............. ............. ............. .............. ............. ............. .............. ............. ............. ............. ............. ............. ...... 3-4

3.7.2

SM_CPU866 SM_CPU866e..... e........... ............. .............. ............. ............. .............. ............. ............. ............. ............. .............. ............. ............. .............. ............. ............. ............. ............. .............. ............. .......... .... 3-4

3.7.3

SM_SER...... SM_SER............. ............. ............. .............. ............. ............. ............. ............. .............. ............. ............. .............. ............. ............. ............. ............. .............. ............. ............. .............. ............. .......... .... 3-5

3.7.4

SM_DI32 SM_DI32 .............. ..................... ............. ............. ............. ............. .............. ............. ............. .............. ............. ............. ............. ............. .............. ............. ............. .............. ............. ............. ............. ........ .. 3-5

3.7.5

SM_DO32T SM_DO32T ........... .................. ............. ............. .............. ............. ............. ............. ............. .............. ............. ............. .............. ............. ............. ............. ............. .............. ............. ............. ..............3-6 .......3-6

3.7.6

SM_DO16R............ SM_DO16R................... ............. ............. .............. ............. ............. .............. ............. ............. ............. ............. .............. ............. ............. .............. ............. ............. ............. ............. ............. ...... 3-6

3.7.7

SM_AI16...... SM_AI16............. ............. ............. .............. ............. ............. ............. ............. .............. ............. ............. .............. ............. ............. ............. ............. .............. ............. ............. .............. ............. .......... .... 3-7

3.7.8

SM_AI8AO4 SM_AI8AO4 .......... ................. ............. ............. .............. ............. ............. ............. ............. .............. ............. ............. .............. ............. ............. ............. ............. .............. ............. ............. ..............3-7 .......3-7

3.7.9

SM_PS SM_PS .............. .................... ............. ............. ............. .............. ............. ............. .............. ............. ............. ............. ............. .............. ............. ............. .............. ............. ............. ............. ............. ............ ..... 3-8

3.7.10

SM_PS40 SM_PS40 ............. .................... ............. ............. ............. ............. .............. ............. ............. .............. ............. ............. ............. ............. .............. ............. ............. .............. ............. ............. ............. ........ .. 3-8

3.7.11

SM_BPX SM_BPX and SM_CHX SM_CHX ............. .................... ............. ............. .............. ............. ............. .............. ............. ............. ............. ............. .............. ............. ............. .............. ............. ............ ...... 3-8

Chapter Chapter 4. 4.1

Preparing Preparing the Work Area Area ............. .................... .............. ............. ............. ............. ............. .............. ............. ............. .............. ............. ............. ............. ............. .............. ............. ........... ..... 4-1

Introductio Introduction....... n............. ............. .............. ............. ............. ............. ............. .............. ............. ............. .............. ............. ............. ............. ............. .............. ............. ............. .............. ............. ............. ............. ........ 4-1 2


Rev. 3.1 (01-09-2016)

4.2

Connection with the Console..............................................................................................................................4-1

4.3

Working with SM_CPU866 ................................................................................................................................. 4-2

4.3.1

Initial IP Configuration (Console)................................................................................................................4-2

4.3.2

Configuring Definitive IP Addresses and Users (Easergy Builder) ............................................................. 4-4

4.3.3

Loading VxWorks ....................................................................................................................................... 4-5

4.4

Working with SM_CPU866e ............................................................................................................................... 4-7

4.4.1

Initial IP Configuration (Console)................................................................................................................4-8

4.4.2

Updating Linux............................................................................................................................................4-8

4.4.3

Configuring Definitive IP Addresses and Users (Easergy Builder) ........................................................... 4-10

4.5

File System Description.................................................................................................................................... 4-10

4.5.1

SM_CPU866 (VxWorks)........................................................................................................................... 4-10

4.5.2

SM_CPU866e (Linux)............................................................................................................................... 4-10

4.5.3

Environment Variables ............................................................................................................................. 4-11

4.6

Loading/Updating Baseline............................................................................................................................... 4-11

4.7

Updating Software for I/O and Communication Modules.................................................................................. 4-13

Chapter 5.

Configuration of the Backplane .................................................................................................................. 5-1

5.1

Introduction......................................................................................................................................................... 5-1

5.2

Configuration of the Backplane with Easergy Builder......................................................................................... 5-1

5.2.1

Initial Configuration..................................................................................................................................... 5-1

5.2.2

Adding a Configuration............................................................................................................................... 5-3

5.2.3

Channel Configuration................................................................................................................................5-4

5.3

Configuring the Database for Redundant CPUs................................................................................................. 5-6

5.4

Transferring the Configuration to the RTU.......................................................................................................... 5-8

5.5

Monitoring Communications............................................................................................................................... 5-8

Chapter 6. 6.1

Introduction......................................................................................................................................................... 6-1

6.1.1 6.2

Local Acquisition......................................................................................................................................... 6-1

coreDb in Easergy Builder.......................................................................................................................... 6-1

Centralized Local Acquisition ............................................................................................................................. 6-1

6.2.1

Information Processing............................................................................................................................... 6-2

6.2.2

Configuring the Local Acquisition ............................................................................................................... 6-4

6.2.3

Signal Identification - Coordinates............................................................................................................ 6-12

6.2.4

Diagnostic Signals ....................................................................................................................................6-13

6.2.5

Signal Calibration ..................................................................................................................................... 6-13

6.3

Transferring Databases to the RTU.................................................................................................................. 6-13

Chapter 7. 7.1

Console Commands................................................................................................................................... 7-1

Introduction......................................................................................................................................................... 7-1

7.1.1

SM_CPU866 Console ................................................................................................................................ 7-1

7.1.2

SM_CPU866e Console .............................................................................................................................. 7-1

7.2

VxWorks Commands (only SM_CPU866).......................................................................................................... 7-1

7.3

Saitel Commands ............................................................................................................................................... 7-5

7.4

BLMon Commands (only SM_CPU866e)........................................................................................................... 7-2

Glossary......................................................... ................................................................ ....................................................... B


3

Rev. 3.1 (01-09-2016)

Index of Figures Figure 2-1. Saitel RTU software architecture. ............................................................................................. ....................... 2-1 Figure 2-2. Relation between coreDb and other applications................ ............................................................... .............. 2-2 Figure 3-1. Backplane`s positions. .......................................................... ............................................................... ............ 3-1 Figure 3-2. Profibus switches for module configuration......................... ................................................................ ............. 3-2 Figure 4-1. Configuration of the serial port in the PC to connect the console..................................................................... 4-1 Figure 4-2. Example of console connection to a SM_CPU866 module.......... ............................................................... ..... 4-2 Figure 4-3. Available commands in VxWorks Boot..................................................... ........................................................ 4-3 Figure 4-4. Boot parameters. ........................................................ ............................................................... ...................... 4-3 Figure 4-5. Changing IP address for SM_CPU866 (ETH1). ............................................................ ................................... 4-3 Figure 4-6. Easergy Builder - Configuration of the connection with the CPU. ............................................................... ..... 4-4 Figure 4-7. Restoring boot configuration parameters. ........................................................... ............................................. 4-5 Figure 4-8. Boot parameters for VxWorks update ....................................................... ....................................................... 4-5 Figure 4-9. CISCO TFTP Server. ............................................................ ............................................................... ............ 4-6 Figure 4-10. Location of the vxWorks file. ........................................................ ................................................................ .. 4-6 Figure 4-11. Transfer of the vxWorks file from the PC to the RTU. .......................................................... .......................... 4-6 Figure 4-12. Restoring boot parameters............................................................ ............................................................... .. 4-7 Figure 4-13. Version of vxWorks. ............................................................ ............................................................... ............ 4-7 Figure 4-14. Example of console connection to a SM_CPU866e module..... ................................................................ ..... 4-7 Figure 4-15. u-Boot console. ........................................................ ................................................................ ...................... 4-8 Figure 4-16. Setting the environment variables................ ................................................................ .................................. 4-9 Figure 4-17. Message on the console while the file Is uploaded from TFTP server. .......................................................... 4-9 Figure 4-18. TFTP Server. ............................................................ ............................................................... ...................... 4-9 Figure 4-19. Linux has been updated...................... ............................................................... .......................................... 4-10 Figure 4-20. Baseline file ready to be installed................................................................................. ................................ 4-11 Figure 4-21. Installing the baseline in SM_CPU866e............................ ............................................................... ............ 4-12 Figure 4-22. BLMon – Console tool for SM_CPU866e.......................................................... ........................................... 4-12 Figure 4-23. Updating the software of the module SM_AI16........................................................... ................................. 4-13 Figure 5-1. Configuring backplane .......................................................... ............................................................... ............ 5-1 Figure 5-2. Acquisition strategy window. ........................................................... ............................................................... .. 5-2 Figure 5-3. Initial configuration of the RTU........................ ................................................................ ................................. 5-2 Figure 5-4– New configuration ...................................................... ............................................................... ...................... 5-3 Figure 5-5 – New configuration in the RTU tree .......................................................... ....................................................... 5-3 Figure 5-6– Configuration mode......................................... ............................................................... ................................. 5-3 Figure 5-7 – Contextual menu for Configuration ......................................................... ....................................................... 5-4 Figure 5-8. Module management window. ........................................................ ............................................................... .. 5-4 Figure 5-9. Redundancy configuration .............................................................. ................................................................ . 5-6 Figure 5-10. Using several IPs to a port. ........................................................... ............................................................... .. 5-7 Figure 5-11. main_cfg.xml file. ...................................................... ............................................................... ...................... 5-8 Figure 5-12. CPU correctly configured. ............................................................. ................................................................ . 5-8 Figure 6-1. Configuring local acquisition for Saitel DP .......................................................... ............................................. 6-2 4


Rev. 3.1 (01-09-2016)

Figure 6-2. coreDb Menu .............................................................. ............................................................... ...................... 6-2 Figure 6-3. Status signals defined in coreDb............................................................................................... ....................... 6-2 Figure 6-4. Available Saitel DP modules in Easergy Builder. .......................................................... ................................... 6-4 Figure 6-5. Configuring local acquisition. .......................................................... ............................................................... .. 6-4 Figure 6-6. Configuring the acquisition strategy. ........................................................ ........................................................ 6-5 Figure 6-7. Adding new I/O modules....................................................... ............................................................... ............ 6-6 Figure 6-8. Configuring acquisition signals for a I/O module ........................................................... ................................... 6-6 Figure 6-9. PLC module configuration............................... ................................................................ ................................. 6-7 Figure 6-10. Example of a PLC Configuration.................................................. ................................................................ .. 6-7 Figure 6-11. SM_AI16 Module Configuration .............................................................. ....................................................... 6-9 Figure 6-12. Configuration of analog outputs in a SM_AI8AO4 module .............................................................. ............. 6-10 Figure 6-13. Configuration of digital inputs in SM_DI32 module ...................................................................................... 6-10 Figure 6-14. SM_DO16R module configuration........................................................... ..................................................... 6-11 Figure 6-15. Analog signals included in coreDb. ........................................................ ...................................................... 6-12


5

Rev. 3.1 (01-09-2016)

Index of Tables Table 1. Reference manuals. ........................................................ ............................................................... ......................... 8 Table 2. Versions applicable for this manual............................................................... .......................................................... 8 Table 3. Software modules compatible with Saitel DP. ......................................................... ................................................ 8 Table 3-1. Profibus speed. ............................................................ ............................................................... ...................... 3-3 Table 4-1. Files required for software update and commands ........................................................ ................................. 4-13 Table 5-1. SM_CPU866 and SM_CPU866e - Channels to be defined..................................................... .......................... 5-5 Table 5-2. Channels to be defined depending on the number of installed SM_SER modules. .......................................... 5-6 Table 6-1. Diagnostic signals of the Saitel DP local acquisition. ............................................................... ....................... 6-13

6


Rev. 3.1 (01-09-2016)

Contents I. Manual’s Objective This manual provides information about how to perform the initial configuration of a Saitel DP RTU. It explains the installation and configuration processes using Easergy Builder.

II. Guide’s Arrangement This manual is divided in different chapters. They are listed below with their respective titles and a description of their contents.

Chapter 1 - Safety & Health Saitel DP is designed according to IEC61010 standard (Safety requirements for electrical equipment for measurement, control and laboratory use). Please read all information into this chapter before installation and/or operation.

Chapter 2 – Baseline Software Platform Description of Baseline Software Platform, the characteristic elements, typical architectures of Saitel DP, and software tools available.

Chapter 3 – Physical Mounting This chapter describes some steps of the installation procedure that are common for all modules. For example handling modules, installation on the backplane and power requirements.

Chapter 4 – Preparing the Work Area This chapter explains how to perform the initial configuration of the CPU and how you can update the software of the CPU and I/O modules.

Chapter 5 – Configuration of the Backplane Setting an initial configuration (redundancy, communication channels, communication protocols, etc…) using Easergy Builder.

Chapter 6 – Local Acquisition This chapter details the local acquisition configuration for each module in Saitel DP and how acquisition signals are managed in coreDb.

Chapter 7 – Console Commands Available console commands using SM_CPU866 and description of the BLMon tool using SM_CPU866e.

III. Reference Manuals Supplementary information to this document can be found in the following documents: Manual's name Software Tools

TE-HG-0000-USR-S855

Easergy Builder User Manual

TE-HG-0000-MSS-S856

Bin Controllers

TE-HG-0000-BIN-S855

Easergy Builder - Configuring IEC101

TE-HG-0000-I1D-S854


TE-HG-0000-I4D-S854


TE-HG-0000-I3D-S854


Document

7

Rev. 3.1 (01-09-2016)

Manual's name

Document

Easergy Builder - Configuring Modbus

TE-HG-0000-MBD-S854

Easergy Builder - Configuring ISaGRAF

TE-HG-0000-ISD-S854

Easergy Builder - Configuring DNP

TE-HG-0000-DNP-S854

Easergy Builder - Configuring SOE

TE-HG-0000-SOE-S854

Saitel DP Modules

TE-HG-0000-MOD-F700 Table 1. Reference manuals.

IV. Versions The information contained in this document is valid for the versions of the software modules listed below and later: Module

Version

Plugin install file

coreDb - 10.00.14

-

01.00.20

Easergy Builder.msi

Synchronization (thm)

thm - 05.03.11

-

Channel management (chan)

chan - 03.00.10

-

Supervision Bin Controller

supBinC - 10.01.03

-

SOE Bin Controller

soeBinC - 10.01.05

SOE_SPlugin.msi

Saitel DP Local acquisition

laqBinC - 10.00.02

LAQ - 7.1.6.0

Saitel DP Profibus

laqPfbM - 04.04.03

LAQ_SPlugin.msi

coreDb Easergy Builder

Web server

webServer – 03.02.03 Table 2. Versions applicable for this manual.

V. Hardware/Software Compatibility The controllers supported by each Saitel DP CPU module are:

Software Module

SM_CPU866e (Linux)

SM_CPU866 (VxWorks)

BLMon

√

×

Channels

√ √ √ √ √ √ √

√ √ √ √ √ √ √

Saitel DP Local acquisition Saitel DP Profibus (local acquisition) SOE Supervision Synchronization webServer

Table 3. Software modules compatible with Saitel DP.

8


Rev. 3.1 (01-09-2016)

Chapter 1. Safety & Health 1.1 Introduction As a result of the multiple uses of the product, the staff in charge of the application and the use of this control device must ensure these usages comply with all security and performance requirements applicable in each application. The requirements include the applicable industry-related laws, norms, regulations and standards. Saitel DP has been designed according to the international standard IEC61010-1 with normal environmental conditions: 

Indoor use.



Altitude up to 2000 m.



Temperature between 5 ºC and 40 ºC.



Maximum relative humidity 80% for temperatures up to 31 °C, decreasing linearly to 50% relative humidity at 40 °C.



Transitional overvoltage up to category III.



Level of contamination II.

The illustrations shown in this manual are intended for exemplary purposes. As there are variables and requirements which depend on each particular installation, Schneider Electric will not be held responsible for the misuse of the equipment based on the examples herein published. Read these instructions carefully and look at the equipment to become familiar with the device before trying to install, operate, service or maintain it. The following special messages may appear throughout this bulletin or on the equipment to warn of potential hazards or to call attention to information that clarifies or simplifies a procedure.

Risk of electric chock The addition of either symbol to a Danger or Warning safety label indicates that an electrical hazard exists, which will result in personal injury or death if the instructions are not followed. IEC

ANSI

Safety alert This is the safety alert symbol. It is used to alert you to potential personal injury hazards. Obey all safety messages that follow this symbol to avoid possible injury.

In this manual you can find the following message types:

DANGER DANGER indicates an imminently hazardous situation which, if not avoided, will result in death or serious injury.

WARNING WARNING indicates a potentially hazardous situation which, if not avoided, can result in serious injury to the persons or equipment.

NOTICE NOTICE is used to address practices not related to physical injury.

1.2 Restricted Liability Electrical equipment should be serviced and maintained only by qualified personnel. All person who can contact with the equipment must be informed and must read the chapter “Safety & Health” of this manual.


1-1

Rev. 3.1 (01-09-2016)

WARNING If this equipment is used in a different form from the recommended one by Schneider Electric, the protection assured for the equipment could be compromised. No responsibility is assumed by Schneider Electric for any consequences arising out of the use of this manual. This document is not intended as an instruction manual for untrained persons.

1.3 Handling Electronic Components The normal movements of a person easily can generate electrostatic potentials of several thousands of volts. A discharge of these voltages on the electronics during the manipulation can damage it. Is possible that this damage doesn't be detected immediately but they can have reduced the reliability of the equipment. While all electronic components are installed into their enclosure, they are protected for relevant levels of electrostatic discharge.

WARNING The enclosure shouldn’t be retired when isn’t necessary, because this action has a risk for the equipment. If the enclosure must be removed, the following precautions must be strictly followed: 

Before removing the enclosure, the operator must be equipotential with the equipment that he is handling.



Avoid touching the electronic. The board must be always manipulated for the edges.



If the equipment has to be passed between two persons, both must be equipotential.



Put the module always on an antistatic surface or on a surface equipotential with you.



During the storage and transport, the module will remain in its conductive or antistatic bag.

1.4 Installation and Operation The user is responsible for checking that the rated characteristics of the device are suitable for its application. The user is responsible for reading and following the device’s operating and installation instructions before attempting to commission or maintain it. Failure to follow these instructions can affect device operation and constitute a hazard for people and property. Some Saitel modules can have elements with dangerous voltages (> 50 V). It is recommended to install the equipments inside a cabinet with a key. This cabinet only should be opened by a qualified person. If this type of cabinet isn't available, a barrier must be installed in order to avoid an accidental contact with these dangerous elements. This barrier only should can be removed using an special tool. An electrical risk symbol with enough size must be included on the cabinet’s door or on the barrier.

WARNING If the barrier has to be removed in order to access to equipment, personnel responsible for the task must be sure that the barrier is installed again when the task is finished. Following image shows an example:

1-2


Rev. 3.1 (01-09-2016)

Figure 1-1. Protection barrier for elements handling dangerous voltage.

WARNING The terminals mustn't be accessible to the user directly when the installation of the equipment has been finished. The cabinet should remain blocked with key or the protection barrier installed. Modules that handle dangerous voltages are marked with a sticker of electrical hazards on the front (size 12.5 mm). This is the case of SM_PS, SM_PS40 and SM_DI32 for voltage higher than 50 V.

DANGER As for SM_DO32T module, since alone does not handle high voltages, NO will be marked at the factory. This module must be marked to inform about the risk when some equipments that manage voltage higher than 50 V are connected to digital outputs. The cabinet or installation must have a general switch placed just in the cable entry of the installation in order to assure the absence of dangerous voltages. This switch must be placed in such a way that it doesn't allow be manipulated by a third person whereas anybody operates inside the cabinet. In addition, the installation must have a switch in order to protect the internal installation of the cabinet of short-circuits in the supply from this one. Both switches have to be marked with the symbol O for OFF and the symbol I for ON.

WARNING The switch for connection / disconnection must be installed on a fix element (i.e. the wall of the cabinet) and it mustn’t interrupt any ground cable. Only a dry cloth should be used for the cleanliness of the surface of the equipment when excessive presence of powder is detected or when there is a foreign body deposited on the surface.

WARNING You mustn't use a liquid product of cleanliness due to the presence of active parts.

1.5 Protective Grounding WARNING 



Before energizing the equipment, this must be correctly grounded as it is indicated in paragraphs 1.5.1 and 1.5.2 In the installation of the equipment, ground is the first thing that should be connected and the last one that should be disconnected.

Saitel must be grounded for two different reasons: 



Electric safety (Protective Earth or PE). To Improve the behavior in EMC and to derive the perturbances to earth.


1-3

Rev. 3.1 (01-09-2016)

1.5.1 Electric Safety Only qualified personnel, with knowledge about hazards associate with electrical equipment is allowed to install Saitel DP. In general, the installation will be following IEC 61010-1 recommendations in order to be compliant with this norm. The backplane must be installed on a metallic surface. This metallic surface must have available an M4 screw marked with this symbol. The ground of the cabinet or installation must be connected to this screw, according to the norm IEC 61010-1.

Saitel DP modules have a plastic enclosure, that is it is not necessary an special consideration about grounding. Only the backplane (when panel mounting) has a metallic enclosure allowing protection when an electric derivation exists. Grounding must be done using a screw with a washer. This screw and washer must be used to fix the backplane to the panel.

WARNING Hazardous voltages can cause shock, burns or death. Disconnect and lockout all power sources before servicing and removing modules. Saitel DP is intended for indoor use in a cabinet with protection according environmental conditions. Electric power sources to the cabinet must be protected by a external switch or other device according local regulation. Make sure that metallic backplane as SM_BPX or SM_CHX is grounded. A dedicated connection with green/yellow wire should be used to assure electric continuity to the installation protective earth. Section of these wires must be enough in order to support 25 A. A test bounding following IEC61010-1 is recommended in order to check the electrical connection is good.

Figure 1-2. Yellow and green cable for ground. The installation manager is responsible for compliance with all the existing international and national electrical codes concerning protective grounding of any device.

WARNING According to the norms about Electric Safety, the screw for ground must be exclusive for this use.

1.5.2 EMC The criteria for grounding in EMC are lightly different. In this case the main rule is to use cables with the minor possible length to the shield or the most nearby ground connection. The section of the cable isn't relevant and it is recommended to use flat cables or conductive flexible bands for a good behavior in EMC. There are some terminal blocks having a dedicated earth ground terminal for EMC purposes. In this case a short wire to a metallic part grounded give the best result. In this case is not necessary the bounding test.

1-4


Rev. 3.1 (01-09-2016)

1.6 Replacing the Battery and Recicling the Product Saitel DP CPUs include a Lithium battery NOT rechargeable.

WARNING When necessary, the battery must be replaced with another of the same model. Only a qualified person should change the battery when is necessary. The appropriate tools should be used for disassembly of enclosure and to accede to the plinth where the battery lodges. It must be replaced by the same indicated model.

When the product is marked with this symbol, it means that, at the end of its life cycle, you mustn't eliminate the product together with habitual residues. To avoid the possible damage to the environment or to the human health that represents the uncontrolled elimination of residues, please, separate the battery (if there is one) of the other elements, and each one must be recycled according to the local regulation.

WARNING If the batteries aren't recycled correctly, the substances contained could produce personal injuries or damage to the environment.


1-5

Rev. 3.1 (01-09-2016)

Chapter 2. Baseline Software Platform 2.1 Introduction The BaseLine Software Platform of Schneider Electric consists of : 

Real-time operating system (RTOS): VxWorks, Linux,…



Real-time applications and configuration files.



Configuration, management, supervision and monitorization tools.

The following figure shows the different applications included in the software platform, as well as additional applications that implement new devices or protocols to upgrade Easergy Builder:

Figure 2-1. Saitel RTU software architecture. The operating system abstracts the hardware from the software applications and manages the applications in real time. It integrates the basic protocols to access the remote unit (SFTP, SSH, etc.) and manage multiple users. The real-time database, named coreDb, is probably the most important element. All the other elements are developed around coreDb:


2-1

Rev. 3.1 (01-09-2016)

Figure 2-2. Relation between coreDb and other applications. coreDb performs the real-time management of RTU points. This real-time database is associated with data producing and consuming by device controllers. The following concepts are related to coreDb: 









Device Controller (also referred to as Controller): Real-time application that accesses coreDb. Each Controller acts as a producer and/or consumer of information managed by coreDb. Point: Each register of coreDb is a point. A point can be included in the table Status, Analog, Command or Setpoint Device: A set of I/O points that share a common source/destination. A typical example of a Device is an IED that communicates with the RTU, or the representation of a SCADA exchanging information acquired or generated by the RTU. A Device is always associated to a type of Controller. Source: Origin of the value of a coreDb data point. Any coreDb data point can have several different sources (in one or several Devices). This means that a value of a database point can be configured to be updated by several different entities. Destination: Target of the value of a coreDb data point. coreDb data points can be configured to have several different destinations (in one or several Devices).

NOTICE It should be noted that any coreDb signal can be associated to more than one source; this is only applicable to Command and SetPoint tables. Allocating more than source to one point is not recommended in Status and Analog tables. 



Coordinate: Point identification within a Device. It is unique for each point and has a different structure for each Controller. It is described in detail in the appropriate manual of each Controller (see ¡Error! No se encuentra el origen de la referencia.). Configuration Plugin: Specific Configuration plugins extend the Easergy Builder application to configure Device Controllers. Additional details about these plugins are provided further in this manual.

Each Device communicates with the associated Controller through its specific protocol. The Controller receives the information, processes it following the specified set of rules and, finally, sends it to coreDb. Similarly, a Controller can read information from coreDb and send it to the appropriate Device. The user can modify the configuration of each Controller and Device using the appropriate Plugin. Once the database is completely configured, the files with the new information can be generated and transferred to the RTU, where they will be processed by the software on startup.

NOTICE The information exchange, that is, the exchange of configuration data between the RTU and Easergy Builder is not continuous, but performed through XML files under user’s request, sooner the configuration is modified in Easergy Builder and the XML files are sent to the RTU, it is necessary to reboot the RTU . 2-2


Rev. 3.1 (01-09-2016)

2.2 Main Elements For the user, the Baseline Software Platform main elements are: 





User Interfaces. coreDb. Device Controllers.

coreDb – Real Time DataBase (RTDB) coreDb is the real-time database backend on which BaseLine Software Platform is built. All the information controlled and managed by the system is stored in this database. Thanks to this architecture, the system’s functionalities can be easily expanded to manage new protocols, customized controllers, etc. To accomplish this, trained developers only need to implement the required Device Controller and the associated Configuration plugin for Easergy Builder, allowing end users to configure the extended functionality. coreDb registers also are called data points or, simply points (this term will be used onwards to avoid confusing these with Device points). coreDb points are organized in four tables: Status, Analog, SetPoint and Command to group the different types of point. These internal tables present the following differences: 



Depending on the point type: Status, Command, and SetPoint points support integer values, whereas Analog signals manage floating values. Depending on the treatment of the point: Status and SetPoint points can be locked, reset to initial values, whereas the other two signal types cannot. All types can retain the value in a non-volatile memory.

Devices Each type of device keeps a list of its associated points, identified by unique labels. These labels allow the identification of each device point unequivocally as source or destination of a coreDb data point. Each point is a piece of information produced (or consumed) by a Device. Within a single Device, point identifiers (coordinates) are unique and cannot be used by two different points. Easergy Builder supports the following device configuration plugins: 

ISAGRAF (version 3) and ISAGRAF5 (version 5).



MODBUS master and slave (with several profiles).



IEC101 master and slave.



IEC104 master and slave.



IEC103 master



DNP master and slave.



SOE (Sequence of Events management).



Saitel DP and Saitel DR local acquisition.





Formula Cilo and Lioc (T300 control & configuration)

Each Device will be available or not depending on the type of CPU to configure. More information about available Devices for each CPU in Table 3.

User Interfaces Easergy Builder has two types of user screens to consult and modify the information stored in coreDb: 

Graphical Interface (Plugin): The picture below shows the interface to configure Saitel DP acquisition hardware. Using this graphical interface the user can configure each local acquisition points with its corresponding point in coreDb. There is a graphical interface for each Device Controller.


2-3

Rev. 3.1 (01-09-2016)

Figure 2-1 – Saitel DP local acquisition plugin interface. 

coreDb tables: This interface enables access directly each point stored in coreDb. Every table is shown separately Status, Analog, SetPoint and Command.

Figure 2-2 – coreDb interface. Once the configuration process is completed, Easergy Builder generates the necessary XML configuration files. These files have to be transferred to the RTU to apply the new configuration. When the file transfer operation is completed without errors, the configuration changes can be activated in the RTU by rebooting it.

2.3 Software Tools The software tool used by the user will depend on the tasks to perform on the system. The following tools are available: 

Easergy Builder : General configuration and log revision (sysLog).



ISaGRAF (version 3 and 5): Configuration, debugging and optimization of the embedded logic programs.



SFTP: Manual exchange of configuration files (for expert users only).



Saitel Webtool: coreDb monitoring and maintenance (remote connection).



HU250 WebApp: Monitoring, diagnostic, settings and maintenance.



Console or SSH: Advanced diagnostic (for expert users only, local or remote connection).

Each tool is available for every CPU type. For more information, please, consult the RTU manual.

2-4


Rev. 3.1 (01-09-2016)

Chapter 3. Physical Mounting 3.1 Introduction Some steps of the installation procedure of a module in the backplane are common for all modules, and other steps will depend on the type of module to be mounted. The following steps are common for the installation of any module: 

Handling the module with extremely care (paragraph 3.2).



Selecting the right location within the backplane (paragraph 3.3).



Considering the backplane power requirements (paragraph 3.4).

3.2 Handling WARNING The electrostatic discharges may damage semi-conducive devices within the module, if the connector pins are in contact with the backplane. Please note the following precautions to avoid electrostatic damages: 

You should handle the module from the front side, as far as possible from the backplane connectors.



You should never touch the pins of the backplane connector.



You should keep the module in its antistatic bag or packaging box, when unused.

3.3 Module Location within the Chassis All modules must be installed always in vertical position.

Figure 3-1. Backplane`s positions. To mount the module in the backplane, please follow the following instructions: 





Switch off the backplane’s power supply. Mount the module at the desired position within the backplane and verify that the rear rails are properly mounted using the pre-drilled holes on the backplane. Firmly press the module to assure the connector fits in the backplane connector properly. Check whether the module is correctly mounted to the backplane base.



Fix the module to the backplane using the screw located at the top.



Insert the terminal or flat ribbon connectors.

WARNING When installing a SM_CPU866e module with fiber optic, we have to make sure that there is enough space between the front of the module and the cabinet door when it is closed, because the fiber optics can be pinching with the risk of breakage. Depending on the type of the module, there are several considerations:


3-1

Rev. 3.1 (01-09-2016)

Power Supply When using a power supply such as the SM_PS or SM_PS40 module, it must be located in the position 1 (slot1 left-hand side). In redundant-power supply configurations, there must be two reserved positions for the two power supply modules. These positions must be 1 and 2.

CPU The CPU must be placed as far as possible from the modules which operate at alternating currents or high currents. Slot 9 is recommended for the CPU module. If the system has redundant CPUs, both control modules must be put together using slots 8 and 9.

Communication Modules The communication bus cannot be expanded between backplanes, so that all communication modules (maximum 8) must be installed in the same backplane that CPU.

I/O Modules I/O modules can be located in any position (slot) within the chassis. These modules should be grouped to minimize the adverse effects caused by noise and heat.

3.4 Power Requirements WARNING The voltage input for the backplane is 5.4 ± 0.1 VDC. The external voltage input isn't protected against overvoltage nor polarity inversion, so an incorrect wiring or an incorrect adjustment of the supply voltage could damage electronic. The SM_PS and SM_PS40 modules (power-supplies) are scalable to supply power to the modules connected to the backplane, as required. When using auxiliary power supplies it is necessary to scale them depending on the installed modules. The power consumption is indicated for each module in the manual “Saitel DP Modules”. The consumption of all modules will be added plus a safety margin (between 20% and 50% of the full power). The power supply efficiency (typically, 70 90%) shall also be considered, in order to prevent the chassis and power supply from overloading.

3.5 Polarization and Commons The information related to the polarization and commons of each module is provided in the respective chapter of the manual “Saitel DP Modules”.

3.6 Configuration Switches 3.6.1 I/O Modules - Identification and Profibus Speed The module’s identification and Profibus communication speed can be set using the microswitches on the module's rear panel. Each microswitch has the following functions:

Figure 3-2. Profibus switches for module configuration. The module’s identification must be unique, selecting between 0 (only for CPU) and 96 using microswitches 1 to 7. The address definition will be as follows: 0

1

2

3

4

5

6

P1*2 + P2*2 + P3*2 + P4*2 + P5*2 + P6*2 + P7*2 3-2


Rev. 3.1 (01-09-2016)

Assuming Px is the value assigned to the position of microswitch x (0 is OFF and 1 is ON). For example, if switches 2, 4 and 5 are in the ON position, the Profibus address of the module is 26.

NOTICE It is possible to connect up to 96 Saitel DP modules. The Profibus communication speed must be the same for all Saitel DP modules, which is determined by the speed of the master, configured by software, in the control module. The speed is set using microswitches 9, 10 and 11 as shown in the following table: Position 9

Position 10

Position 11

Profibus Rate

OFF

OFF

OFF

19.2 kbaud

ON

OFF

OFF

93.75 kbaud

OFF

ON

OFF

187.5 kbaud

ON

ON

OFF

500 kbaud

OFF

OFF

ON

1.5 Mbaud

ON

OFF

ON

Not available

OFF

ON

ON

Not available

ON

ON

ON

Not available

Table 3-1. Profibus speed.

NOTICE For optimal system performance is recommended to set the Profibus rate to 1.5 Mbaud. Microswitches 8 and 12 are reserved and must be set to OFF, except for the SM_DI32 module. For additional information, please, see the manual “Saitel DP Modules”.

3.6.2 Communication Modules - Identification For communication modules, the microswitches 1 to 4 are used to identify the position of the module in the bus. This position indentifies the physical name of each serial port. For example, serial ports of SM_SER in position 1 are MUX1 to MUX8. MUX9 to MUX16 are the serial ports in the SM_SER in position 2.

3.6.3 CPU Modules – Configuration For the CPU modules, switches 1 to 7 must be OFF. Other configuration switches for SM_CPU866 are: 





Switch 9 configures the console communications rate: ON  19.200 bps and OFF  38.400 bps. When the CPU is booting, a message with the selected configuration will be shown: “Dip-Switch 9 OFF: CONSOLE_TTY Set to 38400”. For revision B9 of the SM_CPU866 and later, switch 5 is used for connection / disconnection of the battery (ON  The battery is connected / OFF  The battery is disconnected). For releases prior to B9 of the SM_CPU866 module, if after to be power-on the CPU this one is going to be disconnected during a long period of time it recommends to extract the battery. Other switches haven't got any associated functionality and should be in OFF state.

Configuration switches for the CPU SM_CPU866e: 





Switch 9 configures the console communications rate: ON  19.200 bps and OFF  38.400 bps. When the CPU is booting, a message with the selected configuration will be shown: “Dip-Switch 9 OFF: CONSOLE_TTY Set to 38400”. Switch 5 is used for connection / disconnection of the battery, like as SM_CPU866. For revision Lnx_15:11:26:07:49:11 of Linux and later, if switch 10 is ON, when the CPU is rebooted, the existing netConfig.xml file is renamed old_netConfig.xml and the existing userLogin.xml file is renamed old_userLogin.xml. The CPU starts with a configuration by default: ETH 1: 192.168.1.1 (mask: 255.255.255.0) ETH 2: 10.1.1.1 (mask: 255.0.0.0) ETH 3: 192.168.3.1 (mask: 255.255.255.0) ETH 4: 192.168.2.1 (mask: 255.255.255.0) Default user is “admin” and password “12345678”.


3-3

Rev. 3.1 (01-09-2016)

3.7 LED Indicators The Saitel DP modules include some visible LEDs (light emitting diodes) on the front side. All acquisition modules have common LEDs, and the rest are specific for each module. The front panel of each acquisition module has a red indicator DIA and a green indicator RUN. The module performs a self-check during the start-up process. If no error is detected, the red indicator is switched off and the green indicator displays the module’s configuration status. If any problem is detected, the red indicator DIA is switched off. Following tables provide a complete description of the possible module’s status.

3.7.1 SM_CPU866 PWR

RUN

FAIL

DIO

BAT

ONL

SYN

Description

Normal state of the CPU. In a system with redundant CPU the led ONL is On for the CPU ONLINE. In a system with external synchronization, the led SYN is On if the CPU is synchronized and is off in other case. No power supply. No running application or DOING_WELL has not been configured for supervision. RTU in fail. This led is associated to the supervision signal FAIL_RTU. DOING_WELL signal must be defined in STATUS table as destination for supervision. Important: The field INIT VALUE for this signal must be 1. Diagnostic error in at least one I/O module. The led DIA of the I/O module in fail should be On too (except for previous revision to DA of the module SM_DO32T). Is possible that the module isn’t inserted on the bus. If the module remains out of the bus, the led DIO is off. If the module is inserted on the bus, the led DIO blinks. An I/O module is m issing on t he bus. W hen you re-install the module, the led DIO blinks for about 40 seconds and if all is fine, will remain on. Low battery or not installed. See the instructions in this manual for replacement and battery recycling.  Blinking





On

Off

3.7.2 SM_CPU866e PWR

RUN

FAIL

DIO

BAT

ONL

SYN Description

Normal state of the CPU. In a system with redundant CPU the led ONL is On for the CPU ONLINE. In a system with external synchronization, the led SYN is On if the CPU is synchronized and is off in other case. No power supply. No running application or DOING_WELL has not been configured for supervision. RTU in fail. This led is associated to the supervision signal FAIL_RTU. DOING_WELL signal must be defined in STATUS table as destination for supervision. Important: The field INIT VALUE for this signal must be 1. Diagnostic error in at least one I/O module. The led DIA of the I/O module in fail should be On too (except for previous revision to DA of the module SM_DO32T). Is possible that the module isn’t inserted on the bus. If the module remains out of the bus, the led DIO is off. If the module is inserted on the bus, the led DIO blinks. An I/O module is m issing on t he bus. W hen you re-install the module, the led DIO blinks for about 40 seconds and if all is fine, will remain on. Low battery or not installed. See the instructions in this manual for replacement and battery recycling.  Blinking



On



Off

3-4


Rev. 3.1 (01-09-2016)

3.7.3 SM_SER DIA

RUN

STx

RXx

TXx

RTSx

CTSx Description

The module is configured and communication with the CPU. Configuration error. Is probably the module has assigned the address 0. (2)

Configuration error. Is probably the module has assigned an address greater than 8.

(1)

On when Request To Send (RTS) or Clear To Send (CTS) signals are activated. The channel has to been set with ENABLE for “RTS Control”. If the channel has been set as TOGGLE (or AUTO for revision DA and later), these leds are only on if there is transmission/reception. These leds are off for any other situation. Firmware error. It is necessary to load the software again.

(2)

Hardware failure. (3)

Hardware failure on the block x.

(2)

Receiving data. Transmitting data.  Blinking





On

Off

3.7.4 SM_DI32 DIA

RUN

STx

DIx

Description Polarization and configuration OK. The module is in service. Digital input x is deactivated. The Profibus slave number assigned to the module is 0 or greater than 96. The CPU may have detect a problem into the configuration, for example, the type of the module is different.

(1)

Module not configured or disconnected. If the module is connected, the address is between 1 and 96 but this address haven’t been configured.

(2)

Digital input x is active. It lights briefly during startup. If it remains on, an error has been detected in the firmware or during the startup process.

(3)

Polarization failure in block x.

(4)

(4)

Fail detected in the verification mechanism for the digital input x. (5)

(5)  Blink




On



3-5

Off

Rev. 3.1 (01-09-2016)

3.7.5 SM_DO32T DIA

RUN

STx

DOx

Description Normal status. The module is ready to run commands to field. NOTE: If in this situation commands aren’t executed, please consult action number 6. Incorrect address assigned to the module (0 or greater than 96). If the address is correct, the type of the module is different to the configured for this address (and a module with correct type and this address isn’t inserted on the bus).

(1)


(2)

Digital output x activated. It lights briefly during startup. If it remains on, an error has been detected in the firmware or during the startup process.

(3)

Polarization failure without active digital output.

(4)

Polarization error and at least one active digital output.

(4)

(4)

(5)

In this case, 8 digital outputs are blinking because a short-circuit has been detected between two blinking signals or one blinking signal and the mass line. All commands in the module are blocked.

(5)  Blinking



On

DOx



Off

3.7.6 SM_DO16R DIA

RUN

STx

Description Normal status. The module is ready to run commands to field. Incorrect address assigned to the module (0 or greater than 96). If the address is correct, the type of the module is different to the configured for this address (and a module with correct type and this address isn’t inserted on the bus).

(1)


(2)

Digital output x activated. It lights briefly during startup. If it remains on, an error has been detected in the firmware or during the startup process.

(3)

Polarization failure without active digital output.

(4)

Polarization error and at least one active digital output.

(4)

(4)

(5)

In this case, 8 digital outputs are blinking because a short-circuit has been detected between two blinking signals or one blinking signal and the mass line. All commands in the module are blocked.

(5)  Blinking



On



3-6

Off


Rev. 3.1 (01-09-2016)

3.7.7 SM_AI16 DIA

RUN

STx Description

Normal status. The module is communicating with the master. Incorrect address assigned to the module (0 or greater than 96). If the address is correct, the type of the module is different to the configured for this address (and a module with correct type and this address isn’t inserted on the bus).

(1)


(2)

It lights briefly during startup. If it remains on, an error has been detected in the firmware or during the startup process.

(3)

Hardware failure in the block x. (3)

(3)  Blinking





On

Off

3.7.8 SM_AI8AO4 DIA

RUN

ST1

ST2

PFail(x)

Break(x)

AIx

AOx Description

Normal status. The module is communicating with the master. Firmware failure. (3) Incorrect address assigned to the module (0 or greater than 96). If the address is correct, the type of the module is different to the configured for this address (and a module with correct type and this address isn’t inserted on the bus)

(1)


(2)

Ax out of range. AOx out of range.

(3)

(3)

Internal failure in the analog input block.

(3)

Internal failure in the analog output block.

(3)

Hardware failure in AOx.

(3)

(3)

Opened current loop for AOn.

(4)  Blinking




On

3-7



Off

Rev. 3.1 (01-09-2016)

3.7.9 SM_PS WDOG

AUX Description

PWR

(2)

If auxiliary output is not mounted in the module, the indicator AUX must be off. If this auxiliary output is mounted, revise fuse F2. If it is correct, consult the support service.

Main power supply failure. The module is not powered. (1)

Without function for new systems 

3.7.10 WDOG



On

Off

SM_PS40 AUX Description

PWR

If auxiliary output is not mounted in the module, the indicator AUX must be off. If this auxiliary output is mounted, revise fuse F2. If it is correct, consult the support service. Main power supply failure. The module is not powered. Without function for new systems 

3.7.11



On

Off

SM_BPX and SM_CHX

Each led is identified as follow:

3.7.11.1 MST

Supervision of the Profibus SLV

Status

Idle Correct

No answer

Description

No questions or answers have been detected from master nor slave module. Questions have been detected from a master in both channels (with redundancy) and answers from an slave in both channels. Questions have been detected from a master in both channels, but any slave module is responding.

Degraded, answer.

Questions have been detected from a master in both channels (with redundancy) and answers have been detected from an slave in only one channel.

Degraded, question

Questions have been detected from a master in only one channel (with redundancy) and answers have been detected from an slave in both channels.

Fail in question

The transmission lines of the master modules in both channels are blocked. Impossible to communicate with the slaves modules. A fail in the supervisor of Profibus is possible too.

Fail in answer

The transmission lines of the slaves modules in both channels are blocked. Impossible to communicate with the slaves modules. A fail in the supervisor of Profibus is possible too.

On

Fast blinking 3-8

Slow blinking

Off


Rev. 3.1 (01-09-2016)

3.7.11.2 OVx

Supervision of the Power Uvx

Status

Power-off for overvoltage High-high voltage (dangerous voltage) High voltage (warning voltage) Optimum Low voltage (warning voltage) Low-low voltage (dangerous voltage) Power-off for undervoltage Blocked No operative On


Description

Power voltage above the maximum. Power voltage much higher than the nominal value. The system can startup but cannot work fine. Power voltage slightly above the nominal value. Correct state for startup and working. Power voltage into the nominal value range. Optimum state for startup and working. Both leds are lighted each 3 s. Power voltage slightly under the nominal value. Correct state for working but not for the startup. Depending on voltage level the system could be restarted. Power voltage much higher than the nominal value. The system can startup but cannot work fine. Unsafe state for working and startup. If the voltage level is decreased, the backplane could be power off. The voltage level is much lower than the minimum. The maximum number of retries to boot has been exceeded. The supervisor will not attempt more reconnections until the power supply is completely removed. Without power supply or the voltage supervisor is broken. Fast blinking

3-9

Slow blinking

Off

Rev. 3.1 (01-09-2016)

Chapter 4. Preparing the Work Area 4.1 Introduction SM_CPU866 uses VxWorks as RTOS, whereas SM_CPU866e uses Linux. The following steps are necessary in order to prepare the work area: 





Installing Easergy Builder in our PC. The Easergy User Manual describes the installation process and the use of this tool. If needed, the user should know the software update procedure for any type of CPU and I/O module. This procedure for each CPU and I/O modules are detailed in this chapter. Configuring the RTU with Easergy Builder. Other chapters in this manual describe the configuration of the local acquisition, whereas the general configuration of the RTU as well as other devices are detailed in others manuals (consult Table 1).

4.2 Connection with the Console The RTOS provides a high-priority command interface to perform advanced monitoring and diagnostic operations.

NOTICE The use of the console interface must be restricted to personnel with a deep knowledge of the system. The console must be connected to the port labeled as CON in the CPU. Using a serial 3-wire crossover cable, we will connect this port to the serial port (COMx) in the PC. (For further details about this cable, please refer to the manual “Saitel DP modules”). In the PC, we will use the HyperTerminal software (or similar) to configure the serial port as follows:

Figure 4-1. Configuration of the serial port in the PC to connect the console. Once communication is established, the user will be prompted with the operating system messages. It is possible to disable the console tool using the CON port. To do so, edit the main_cfg.xml file and change the environment variable to “OFF”. If this variable doesn’t exist you can create it. The console shell cannot be executed using the CON port but could be executed using Telnet. For example:


4-1

Rev. 3.1 (01-09-2016)

4.3 Working with SM_CPU866 NOTICE The prompt displayed in the console will depend on the software version that is installed (“” or “SM_CPU866>”).

Figure 4-2. Example of console connection to a SM_CPU866 module.

NOTICE If the console is connected to an already initialized CPU, the screen will only display the prompt. The previous messages will appear after the CPU is reset. Once the console prompt is displayed, any available command can be executed. The more used commands for SM_CPU866 are detailed later in this manual.

4.3.1 Initial IP Configuration (Console) There are cases in which you need to assign the IP address to the control module manually, not only in the first connection but also in later connections.

NOTICE For SM_CPU866, the boot Ethernet port is ETH1. To perform this task, reboot de CPU (command: reboot) and stop the booting process using any key when the message “Press any key to stop auto-boot...” is shown. Now, the prompt of the VxWorks Boot is available. Use command “help” for more information about available commands.

4-2


Rev. 3.1 (01-09-2016)

Figure 4-3. Available commands in VxWorks Boot. Use “p” to consult the actual configuration:

Figure 4-4. Boot parameters. Use “c” command to change this boot parameters.

NOTICE To change any parameter, type the new value when the parameter is shown and press “Enter”. To maintain the current value, only press “Enter”. To remove the current value type a dot and press “Enter”. In order to assign an IP address, change the following parameters: 

inet on ethernet (e): IP address that will be assigned to the CPU in the next initialization.



other (o): motfec0

If only the IP address is indicated, the default subnet mask is 255.255.0.0. However, if a different subnet mask must be used (for example 255.255.248.0), you have to indicate the IP address followed by the mask in hexadecimal format and separated with a colon, (for example 169.254.13.155:fffff800). Following example fix the IP address to 172.19.131.10 with netmask 255.255.0.0:

Figure 4-5. Changing IP address for SM_CPU866 (ETH1). Reboot the CPU using the Reset button on the module or using command “@” in the VxWorks Boot. After reboot, you can verify the new IP address of the CPU executing a command “ping 172.19.131.10” from a PC in the same net.


4-3

Rev. 3.1 (01-09-2016)

NOTICE Once the IP address is changed with the console, you should take into account that this is a provisional change. This change must be definitive by transmitting this IP address through Easergy Builder, as explained in the section below.

4.3.2 Configuring Definitive IP Addresses and Users (Easergy Builder) In the previous section, a provisional IP address was assigned to the CPU. Now, using Easergy Builder, the definitive IP address has to be set. Open Easergy Builder and create a new RTU. Select SaitelDP-SM_CPU866 as type of CPU and configure Network and Users tabs.

Figure 4-6. Easergy Builder - Configuration of the connection with the CPU. The fields to be specified are: IP: Provisional IP set in previous section.





Users: At least one user has to be defined.



Netwotk: Definitive IP address for each available Ethernet. The main port is ETH1 and its definition is mandatory.

Please, note that each ETHx is in a different subnet (mask 255.255.255.0). If you define more than one ETH port in the same subnet, only the first port defined for this subnet is active. Refer Easergy Builder manual for more information about this configuration.

NOTICE Have in account that SM_CPU866 doesn’t allow the option “Secure Encrypt” for user’s password. The field “Target encrypt” must be set as “None” or “Encrypt”. The initial configuration is complete and it has to be sent to the CPU using button . At the first time or if the file userLogin.xml was removed from the CPU, you have to use “target”, with password “password” as default user. If there is an userLogin.xml in the CPU, a valid user must be indicated. If you have problems with the user, you can use switch 10 as is explained in paragraph 3.6.3.

NOTICE 



So that Easergy Builder may transfer successfully, VxWorks must be completely initialized and the prompt “” must be available. If the VxWorks Boot prompt is displayed, it means there has been a problem during the initialization, which must be solved. Once the transfer operation is finished, you will be prompted to confirm the RTU resetting. Select “No” this time, since a last change has to be made using the console.

Finally, both parameters “other (o)” and “inet on ethernet (e) should be restored. Reboot the CPU and stop the initialization process by pressing any key. On the Boot prompt, execute “c” and remove the values assigned to the parameters “ and “ (using a dot) when the parameter is shown (see red marks on the picture):

4-4


Rev. 3.1 (01-09-2016)

Figure 4-7. Restoring boot configuration parameters. Reset the CPU using “@”, since the RTU is already configured with the new IP address and the initial configuration files.

4.3.3 Loading VxWorks If there is a problem loading VxWorks, the FTP server isn’t available for copy a new VxWorks from the PC. The user has to know the process to install a specify version of VxWorks in the CPU when the OS doesn’t start properly. This section describes each step of this process assuming that following elements are available: 

File vxWoks to be sent to the CPU.



A TFTP server installed in our PC.

Reboot the CPU and stop the initialization process. On the Boot prompt, execute “c” command and set the boot parameters as follow (new values are identified in red):

Figure 4-8. Boot parameters for VxWorks update Where: 











boot device: motfec0. In the next reboot, the boot device will be ETH1. file name: vxWorks (Please, be careful because it is case-sensitive. The name must be the same as the file indicated in the TFTP server). inet on ethernet (e): IP address of the CPU. Subnet mask by default is 255.255.0.0. If you need to specify other mask, it must be included with the IP in hexadecimal format and behind colons(for example 172.19.131.10:fffff800). host inet (h): IP address of the PC executing the TFTP server. Subnet mask by default is 255.255.0.0, but like previous param, you can change it. flags: The new value has to be 0x1080. These flags define the kernel loading method and the meaning is explained in the tool’s help. other : Enter the motfec0 value (corresponding to ETH1), so that the IP address is obtained from the “inet on ethernet” field and not from the netconfig.xml file. This provisional IP address is used instead of the definitive IP address included in the configuration file.

Now and before rebooting the CPU, please , complete the following procedure:


4-5

Rev. 3.1 (01-09-2016)

1.

In the PC configured with the IP address above, start the TFTP server (for example CISCO TFTP Server v1.1 or SolarWinds TFTP Server v1.1 or SolarWinds TFTP Server). Both tools can be downloaded freeware in the official web on internet. For example, the CISCO TFTP Server has been used for the following examples.

Figure 4-9. CISCO TFTP Server. 2.

On the TFTP server interface, select “View Options”. In the configuration screen which is displayed, the path to the "vxWorks" file in the PC must be specified in the “TFTP server root directory” field.

Figure 4-10. Location of the vxWorks file. 3.

When the TFTP application initialized, to start downloading the file we simply need to reset the CPU and the following messages will be displayed.

NOTICE If the TFTP Server is running in a PC with Windows 7, you must assure that the OS service “1E PXE Lite Server ” is stopped; in other case the CPU could have problems to connect with the TFTP server. During the download process, the TFTP server window will display text messages to show the progress of the file transfer.

Figure 4-11. Transfer of the vxWorks file from the PC to the RTU. 4.

When the download is completed, a message similar to “Thu Jun 30 11:17:06 2016: Successful” will appear in the TFTP server screen and the CPU is automatically initialized.

5.

Finally, boot parameters have to be restored as follow:

4-6


Rev. 3.1 (01-09-2016)

Figure 4-12. Restoring boot parameters. Now, the CPU should be reset again, and vxWorks is already updated. Use “version” on the console to consult the information about the vxWorks installed on the RTU:

Figure 4-13. Version of vxWorks.

4.4 Working with SM_CPU866e If the console in connected when the CPU is rebooting, following message are shown:

Figure 4-14. Example of console connection to a SM_CPU866e module. A valid user must be used u sed in order to access to the console tool named BLMon. This tool is explained later in this manual.


4-7

Rev. 3.1 (01-09-2016)

4.4.1 Initial IP Configuration (Console) If a "baseline" has not been installed yet on the CPU or "/mnt/flash/netConfig.xml" file is not present, the device ETH2 is assigned a default IP address (10.1.1.1) and netmask (255.0.0.0). The default user is “admin” and password “12345678”. If a previous configuration was loaded but you don’t know a valid user, for Linux version Lnx_15.12.15.13.53.26 or later you can use the switch 10. If switch 10 is ON and the CPU is rebooted, the existing netConfig.xml file is renamed old_netConfig.xml and the existing userLogin.xml file is renamed old_userLogin.xml, the renamed files are then not used instead the following IP addresses are assigned; 

ETH 1: 192.168.1.1 (mask: 255.255.255.0)



ETH 2: 10.1.1.1 (mask: 255.0.0.0)



ETH 3: 192.168.3.1 (mask: 255.255.255.0)



ETH 4: 192.168.2.1 (mask: 255.255.255.0)

The default user is “admin” and password “12345678”.

4.4.2 Updating Linux NOTICE Only advanced users should be execute this procedure and only if needed. In order to update the Linux OS, following elements are necessary: 

File uImage-sm_cpu_dct.b uImage-sm_cpu_dct.bin in (OS kernel).



File uImage-sm_cpu_dct.dt uImage-sm_cpu_dct.dtb b (hardware profile)



File u-boot.bin (Boot console for Linux)



TFTP server (for example CISCO CISCO TFTP server v1.1 is used in this manual. manual.

All these steps must be executed from the u-Boot console. In order to access this tool, reboot th e CPU and press any key when the message “Hit “Hit any key to stop autoboot: autoboot: “ “ is shown:

Figure 4-15. u-Boot console. Now, the u-Boot console is available with the prompt “=> “=>”. ”. It’s recommendable to remove the content of /flash and /flash and /bf /bf folder folder in order to "clean" the CPU. Please, execute following commands in the u-Boot prompt: 

=> erase f0000000 +4000000



=> erase ec000000 +2000000

This operation could take some time depending on the amount of data to be removed.

4.4.2. 4.4.2.1 1 Step Step 1

Updating Kernel

First, from the u-Boot console, set up the environment variables netmask, ipaddr and serverip. See the next example: 

=> setenv netmask 255.255.0.0



=> setenv ipaddr 172.19.131.10 (Temporary IP for ETH2)



=> setenv serverip 172.19.131.2 172.19.131.2 (PC where the TFTP is running) 4-8


Rev. 3.1 (01-09-2016)

If you want to save these values run the “saveenv “saveenv”” command.

Figure 4-16. Setting the environment variables. Start the TFTP server on your PC (this is supposed to have the IP address specified on the serverip environment variable),. Copy the file “uImage-sm_cpu_dct.bin” file into the TFTP folder. For example, using CISCO server, select directory y is set on the field “TFTP server root directory”. View Options and Options and this director directory”. From the u-Boot console run the command “=> run update_kernel”.

Figure 4-17. Message on the console while the file Is uploaded from TFTP server.

Figure 4-18. TFTP Server. At the end, the Linux BSP should have been flashed successfully on the SM_CPU866e board. In addition, the hardware has to be updated using the file “uImage-sm_cpu_dct.dtb”. Copy this file on the TFTP server root directory and execute the command “=> run update_dtb” in the uBoot console. Now, Now, the hardware is updated and finally, the uBoot has to be updated updated too. Copy the file “u-boot.bin” on the TFTP server root directory and execute the command “=> run update_uboot”. Configuration & Startup Saitel DP

4-9

Rev. 3.1 (01-09-2016)

When the process is finished, reboot the CPU using the command “=>boot”.

Figure 4-19. Linux has been updated. Now, Linux OS is updated. Only the user “admin” with password “12345678” is available and the IP for ETH2 is 10.1.1.1 with netmask 255.0.0.0. Please, consult following paragraph in order to configure all definitive IP addresses and users.

4.4.3 Configuring Definitive IP Addresses and Users (Easergy Builder) To configure a definitive IP address, please, use Easergy Builder as is explained in paragraph 4.3.2. Have in account that the type of CPU must be Saitel DP-SM_CPU866e.

4.5 File System Description 4.5.1 SM_CPU866 (VxWorks) SM_CPU866e can be accessed by the user through a FTP session. The BaseLine software, applications and user settings are stored in non-volatile memory accessible to the user. These elements are arranged in the file system as follows: 







/bf – Flash memory. It is a general purpose drive where files ISaGRAF, web server and other applications are stored. c: – Compact-Flash memory (optional). This drive will be available or not depending on the ordering options of the module. This is a removable memory and is similar to a hard disk with a size upper than other zones. /flash – Main memory supporting user applications. Device controllers and its configuration files are stored in this drive. /nvRam – Non-volatil SRAM. This memory is used for data storage and its content is supported by a lithium battery.

4.5.2 SM_CPU866e (Linux) SM_CPU866e can be accessed by the user through a secure connection type SFTP (SSH - File Transfer Protocol). The BaseLine software, applications and user settings are stored in non-volatile memory accessible to the user. These elements are arranged in the file system as follows: 











/mnt/bf – Flash memory (32 MB). It is a general purpose drive where files ISaGRAF, web server and other applications are stored. /mnt/flash – Main memory (64 MB). User applications in BaseLine. Device controllers and its configuration files are stored in this drive. /mnt/nflash – Auxiliary memory (128 MB). It’s mounted on a NAND flash device. /nvRam – Non-volatil SRAM (4 MB Max). This memory is used for data storage and its content is supported by a lithium battery. /mnt/sd1 – SD memory (Secure Digital). Removable memory that can be used as an external hard disk using an SD board inserted into the front SD port. /mnt/usb1 – This memory is supported by a "pen drive” device inserted into the front USB port.

4-10


Rev. 3.1 (01-09-2016)

4.5.3 Environment Variables There are several environment variables that the user can define in order to change default folders. These variable are define in the main_cfg.xml file. For example:

Where: 

CONFIG_DIR: (Default value: /flash/cfgFiles/) Folder where configuration files are stored. Several configuration folders could be available corresponding to several projects, then the system could boot the application with one or other depending on the project that you need. The available space in the compact-flash folder could be used for this purpose.



WEB_DIR (Default value: /bf/webFiles/): HTML files defining the web interface.



BIN_DIR (Default value: /bf/binFiles/): Additional folder for storing binary files corresponding to Device controllers.

4.6 Loading/Updating Baseline The load and/or update process of the firmware in Saitel DP consists of copying the supplied file (for example BaseLine_11.05.11.tar.gz) using a FTP client from our PC to the RTU. This folder depending on the type of CPU: 



SM_CPU866: The baseline file must be in “/bf” or “/flash”. SM_CPU866e: The baseline file could be in “/mnt/flash”, “/mnt/bf” or “/mnt/nflash”. This file could be located in “/mnt/usb1” (see following paragraph).

The use of the last version of “Filezilla FTP Client” is recommended. This software can be downloaded for free at http://filezilla-project.org/download.php for all operating systems.

NOTICE With SM_CPU866e, the server type to configure for the FTP client has to be “SFTP using SSH2”. Please, be sure that the type of the transfer is binary.

Figure 4-20. Baseline file ready to be installed. When the copy of the file is finished, reboot the CPU and the new baseline will be automatically installed. Configuration & Startup Saitel DP

4-11

Rev. 3.1 (01-09-2016)

Figure 4-21. Installing the baseline in SM_CPU866e. When the installation is finished, you can access to the console using a valid user. For SM_CPU866e, if the Linux prompt is shown, you need to generate the configuration files for users and net interfaces (please consult paragraph 4.3.2). In another case, the BLMon is shown.

Figure 4-22. BLMon – Console tool for SM_CPU866e Previous to reboot, the baseline file is removed from the folder in order to avoid a new deployment. Only for SM_CPU866e, the baseline file can be stored in the root of a pen drive device inserted into USB port (/mnt/usb1). On Linux startup, when /mnt/usb1 device is available, if a baseline file is detected on the USB, the baseline included in this file is deployed. There are some differences regarding the procedure described above: 



The Baseline file is not removed from the pen drive. You can use this pen drive in order to update the same baseline revision in several CPUs. As a result of the baseline file is not removed, the RTU in not rebooted when the deployment is finished.

The priority order associated to devices in order to load a baseline file is the following: 1. /mnt/usb1 2. /mnt/bf 3. /mnt/flash 4. /mnt/nflash

4-12


Rev. 3.1 (01-09-2016)

4.7 Updating Software for I/O and Communication Modules NOTICE 



Only revisions C0 and later of the SM_AI16, SM_AI8AO4 modules and E0 of the SM_DO32T and SM_SER modules can be updated using this procedure. Others modules and previous versions of these modules only can be updated by authorized personal. For SM_CPU866e, only revision 01.00.13 and later of BLMon allow this functionality.

Once the RTU is configured, the CPU already knows the type of acquisition blocks installed and their respective IP address. According to the table below, copy the files associated to each type of module into the “flash” directory of RTU and execute the indicated command: Module SM_AI16

Binary files

Command SM_CPU866

Command SM_CPU866e

ST_AI16_C0.bin

SM_AI8AO4 ST_AI8AO4_C0.bin

dpUpgrade , “”

dpUpgrade

SM_DO32T ST_DO32T_C0.bin SM_SER

ST_SER_C0.bin

MUX_upgrade

Table 4-1. Files required for software update and commands

NOTICE (*) The name of these files can be different depending on the version of the modules. could be a specific number or 0. If you use 0 as number of slave, all installed modules of this type (depending on the software file) will be updated. could be a specific number between 1 and 8. It corresponds with the address of the SM_SER module to be updated. If the path isn’t indicated in the the file must be stored in /flash/cfgFiles if you are using SM_CPU866 or /mnt/flash/cfgFiles if SM_CPU866e. For example: -> value = 0 = 0x0 -> The task tFdldrv has been suspended Loading file /flash/cfgFiles/ST_AI16_C0.bin:OK /flash/cfgFiles/ST_AI16_C0.bin firmware version: v01.00.02:Apr Slave 3 firmware version ST_AI16_C0: v01.00.02 Apr

3 2014 16:42:04

3 2014 16:42:04

Connecting with slave 3:OK Bootloader version: 1.0 Requesting identification:OK Erasing slave 3:OK Programming slave 3 flash:OK Verifying slave 3 flash:OK Finishing program:OK Rebooted The task tFdldrv has been restarted 0x18b3ba8 (tFdldrv): DDLM_Data_Exchange_con: slave 3 leaves DATA by bus 1

Figure 4-23. Updating the software of the module SM_AI16. The command dpUpgrade 0, “ST_AI16_C0.bin” updates the software of the SM_AI16 modules using the file ST_AI16_C0.bin into the path “/flash/cfgFiles”.


4-13

Rev. 3.1 (01-09-2016)

NOTICE Double quotation marks must be included when typing the command parameter. Moreover, the files' name must be exactly the same as the one specified in this manual, since the command is case sensitive. After executing the command, the console will display messages to report the process progress. Finally, if no problem occurs, the acquisition blocks will be updated to the adequate firmware. There are two very useful console commands: 



dpSniffUpgradeOn and dpSniffUpgradeOff : Show or not in the console window all messages interchanges between the CPU and the I/O modules to be updated. dpVersion “”: Show the version of the specified software file.

NOTICE It’s necessary to have correctly configured the backplane in the CPU before to execute these commands. The CPU has to know previously the types of slaves and its addresses. Please, see following chapters in this manual.

4-14


Rev. 3.1 (01-09-2016)

Chapter 5. Configuration of the Backplane 5.1 Introduction At this moment: 

The operating system is updated and running properly



The software files are stored in the CPU and the application initializes properly

Now you can configure the complete backplane, that is, the communication between the CPU and the I/O modules. Each I/O module is allocated to a unique and identifying number in the bus (Profibus address). This number is assigned using the switches available in the rear panel of the module (see paragraph 3.6). The CPU needs to know the address and the types of I/O modules installed in the bus in order to initialize and switch to data acquisition mode properly. All examples in this chapter are made using SM_CPU866e but all operation are similar for SM_CPU866.

5.2 Configuration of the Backplane with Easergy Builder NOTICE From here onward, the user is supposed to be familiar with the general use of Easergy Builder. For additional information about this tool, please refer to the Easergy Builder manual.

5.2.1 Initial Configuration Once the CPU is powered and correctly initialized, run Easergy Builder in the PC and create a Saitel DP RTU. When the RTU is created, a window is shown allowing set all I/O modules installed in the backplane:

Figure 5-1. Configuring backplane This window allows: 



Add or remove module in the backplane. Use button

to add new modules and

The address for each module is displayed under its picture and it can be changed using module must be the same that is indicated with its rear switches.

NOTICE A maximum of 96 Saitel DP modules can be added to a backplane. 

to remove a module.

Use button

to configure the time parameters of the polling and digital filtering:


5-1

. The address for each

Rev. 3.1 (01-09-2016)

Figure 5-2. Acquisition strategy window.



o

Profibus Rate: This value is depending on position of switches 9, 10 and 11 in the modules installed on the backplane. More information in paragraph 3.6.1.

o

Analog and Digital period: Interval of time for the acquisition of analog and digital input signals when they are configured to be updated periodically (ChgEvt of the signal is set to “N”). Default value for digital signals is 1000 ms (10 ds) and for analog signals is 300 ms (3 ds). Both values have to be changed in intervals of 100 ms.

o

Integrity period: When a digital signal is set to be updated by event (ChgEvt of the signal is set to “Y”), this value indicates that if during this time no event occurred, the signal is updated anyway. This assures the integrity of the signal. Default value is 300 s (3000 ds) and it has to be changed in intervals of 100 ms.

o

Filter DI: This mark allows you to configure the filtering parameters for digital inputs. 

Rebound changes: Number of changes necessaries in order to activate the anti-rebound filter (default value = 5).



Detection period: Time window when the number of rebound will be counted in order to activate the anti-rebound filter blocking the signal. This time is expressed in seconds (default value = 1 s).



Unlock period: Time without changes in a blocked signal in order that this signal is unblocked. This time is expressed in seconds (default value = 1 s).

Use button and stored in XLB files.

to save and load templates with standards configuration of backplanes. This template are

Figure 5-3. Initial configuration of the RTU.

5-2


Rev. 3.1 (01-09-2016)

5.2.2 Adding a Configuration This section shows how you can create a new configuration using Easergy Builder. Select the RTU and press button

:

Figure 5-4– New configuration Write the name of the new configuration. If the RTU was created with an acquisition configuration by default, for a new configuration you can select the field “Create defined RTU acquisition points” in order to include all points of the pre-defined I/O modules in coreDb. For example, for the RTU created in the previous paragraph, this configuration will include a module SM_DI32, one module SM_DO16R and three modules SM_AI16. If “Create defined RTU acquisition point” is checked, following registers will be included in coreDb: 

32 digital inputs in status table.



16 digital outputs in status table.



48 analog inputs in analog table.

Other points associated to each AB will be included too. The new configuration is available for the RTU.

Figure 5-5 – New configuration in the RTU tree Double clicking on it will switch to Configuration mode where the new configuration can be edited.

Figure 5-6– Configuration mode Right-clicking on the configuration name, a contextual menu is displayed:


5-3

Rev. 3.1 (01-09-2016)

Figure 5-7 – Contextual menu for Configuration This menu allows: 

Add, remove or modify a configuration.



Create a template with the information associated to this configuration.



Change the name or description of the Device (description field allows 128 characters maximum. The description is shown when you locate the mouse over the Device name as follow:

5.2.3 Channel Configuration In the Easergy Builder Manual you can find the general operations that we should know to create and edit the communication channels available in the CPU and communications modules. In Configuration mode, select tab Channels in order to access channel management window.

Figure 5-8. Module management window. The following section details the channels to be defined and the parameters that must be assigned depending on the module.

NOTICE The CON port cannot be used for communications, and that is the reason why we do not have to include it in the channel list. The channels that must be defined for a SM_CPU866 and SM_CPU866e are:

5-4


Rev. 3.1 (01-09-2016)

Name

Description

Type

Channel

Protocol

COM1

GPS or RS-232 communications.

ASYNC

COM1

RS-232

COM2

RS-232 communications.

ASYNC

COM2

RS-232

COM3


ASYNC

COM3

RS-232

COM4


ASYNC

COM4

RS-232

Table 5-1. SM_CPU866 and SM_CPU866e - Channels to be defined. The name for each channel is chosen by the user.

NOTICE If it is configured “RTS Control” as AUTO (see section “Channels” in the Easergy Builder manual): 



For COM1 and COM2, the hardware will do the control of the signals RTS and CTS. WARNING!!  If CTS signal is not received, nothing will be transmitted. For RS-485, the management of the signal RTS and switching between RX mode and TX mode, are controlled by the hardware. This is much recommended!

If in the backplane there are installed one or more modules SM_SER, you must define other channels, as is explained in the following table: Name

Description

Type

Channel

Protocol

COM11

Port 1 in the module SM_SER with address 1

ASYNC

SM_SER1-COM1

RS-232/RS-485/RS-422

COM21


ASYNC

SM_SER1-COM2

RS-232/RS-485/RS-422

COM31


ASYNC

SM_SER1-COM3

RS-232/RS-485/RS-422

COM41


ASYNC

SM_SER1-COM4

RS-232 (all versions) RS-485/RS-422 (B4 and later)

COM51


ASYNC

SM_SER1-COM5

RS-232/RS-485/RS-422

COM61


ASYNC

SM_SER1-COM6

RS-232/RS-485/RS-422

COM71


ASYNC

SM_SER1-COM7

RS-232/RS-485/RS-422

COM81


ASYNC

SM_SER1-COM8


COM12


ASYNC

SM_SER2-COM1

RS-232/RS-485/RS-422

COM22


ASYNC

SM_SER2-COM2

RS-232/RS-485/RS-422

COM32


ASYNC

SM_SER2-COM3

RS-232/RS-485/RS-422

COM42


ASYNC

SM_SER2-COM4


COM52


ASYNC

SM_SER2-COM5

RS-232/RS-485/RS-422

COM62


ASYNC

SM_SER2-COM6

RS-232/RS-485/RS-422

COM72


ASYNC

SM_SER2-COM7

RS-232/RS-485/RS-422

COM82


ASYNC

SM_SER2-COM8


... COM18


ASYNC

SM_SER8-COM1

RS-232/RS-485/RS-422

COM28


ASYNC

SM_SER8-COM2

RS-232/RS-485/RS-422

COM38


ASYNC

SM_SER8-COM3

RS-232/RS-485/RS-422

COM48


ASYNC

SM_SER8-COM4


COM58



ASYNC

5-5

SM_SER8-COM5

RS-232/RS-485/RS-422

Rev. 3.1 (01-09-2016) Name

Description

Type

Channel

Protocol

COM68


ASYNC

SM_SER8-COM6

RS-232/RS-485/RS-422

COM78

Port 7 in the module SM_SER with address 8.

ASYNC

SM_SER8-COM7

RS-232/RS-485/RS-422

COM88


ASYNC

SM_SER8-COM8


Table 5-2. Channels to be defined depending on the number of installed SM_SER modules.

The name for each channel is chosen by the user.

5.3 Configuring the Database for Redundant CPUs Saitel DP allows defining redundant configurations with great flexibility, meeting the requirements of any system. From a functional point of view, the CPUs provide several configuration options depending on the redundancy level: 

Control of the switching mechanism.



Redundant operation mode.

It is also possible to define floating IP addresses, which are assigned dynamically to the CPU that is ONLINE. When a RTU is created in Easergy Builder, you can check the field “RTU Redundancy” in order to all configurations for this RTU are redundant (see Figure 5-3). By default, all configurations for this RTU will be redundant. When a new configuration is created for a RTU, you can select if this configuration is redundant or not (see Figure 5-5). In Configuration mode of Easergy Builder, select “coreDb only for redundant Configurations.

dbRED" to configure the redundancy. This tab is available

Figure 5-9. Redundancy configuration In the configuration screen there are four zones; Control, Mode, Bus and Additional IPs.

Control The fields to configure are: 





None: Default value. Without redundancy. MSAC: Switching is performed by the MSAC module. This module manages the switching between two RTUs by hardware, and other functions as well. Protocol: Switching by RCP (Redundancy Control Asynchronous Protocol). In this case, there is a redundant switching channel between both CPUs, which is used to manage the switching operation using a Schneider Electricproprietary protocol. “Via #1” and “Via #2” will be available when “Protocol” is selected: o Backplane. Only available when both CPUs are installed on the same backplane. o

Net (by Ethernet). IP addresses must be set for CPU A and B.

o Serial. A port must be set.

5-6


Rev. 3.1 (01-09-2016)

Mode Set the communication mode between both CPUs (online and backup): 



Cold: There is no communication between both CPUs, and when the switching is performed, the new ONLINE CPU starts with a database with default values. Hot: There is a high speed communication channel (Ethernet o backplane) between both CPUs, which is used to update the BACKUP CPU’s database with the ONLINE CPU’s database. When a switching is performed, the new ONLINE CPU starts with updated values.

WARNING In this operation mode, database IDs must be identical, i.e., it is very important to use the SAME configuration project to configure both CPUs. In this case “Via” allows selecting the replication mechanism: o Backplane o

Net (by Ethernet): the IP addresses must be set for CPU A and B.

The update is done by exception (only the variables that have changed), except the first time that the complete database is updated. The supervision signal DB_UPDATE monitors the process.

Bus It indicates if the CPUs share the same Profibus or not (SHARED or DIFFERENT, respectively), regardless of whether they are in the same backplane or use RS-485 expansion. This is useful to detect failures in dual redundant systems. 





SHARED: In this case, the bus of the STANDBY CPU is disabled. DIFFERENT: If checked, the bus is enabled even if the CPU is in STANDBY mode, so it can receive diagnostics from the modules. NO_ACCESS

Additional IPs It allows configuring a number of IP addresses associated to the CPU that is in ONLINE. These directions are associated in a dynamic way, so that in a redundant system they allow to communicate always with the CPU that is active. Regarding virtual addresses, it is even possible to assign multiple IP addresses to each port:

Figure 5-10. Using several IPs to a port.

NOTICE If a static IP address and a virtual address are defined for the same device in the same subnet, a warning console message will be displayed to notify this abnormal situation (sup_redAddIPs: dev xxx ip x.x.x.x subnetMask xxxxxxxx). This message is a warning from the operating system; nevertheless, it will not cause a system malfunction, since the configuration will operate properly.


5-7

Rev. 3.1 (01-09-2016)

The allocation of A or B to a determined CPU is performed by accessing via sftp to the existing “flash” folder, in a file named “main_cfg.xml”, as below:

Figure 5-11. main_cfg.xml file. If using a redundant configuration, the two CPUs must be distinguished by the value of the field SLOT. By default, the CPU will have the value A, so the change to B must be done directly in this CPU’s xml file; this change is done by opening a text editor and typing the value in uppercase characters.

5.4 Transferring the Configuration to the RTU By now, you have completed the following tasks: 

Configuring the IP address of the CPU.



Loading/Updating the software



Configuring the backplane with Easergy Builder

The next step is transferring the configuration from Easergy Builder (in the PC) to the CPU. . If Configuration mode is active, select button . If WorkSpace mode is active select button Then, you are prompted to confirm the project save operation. Press “ Yes” and the log window will display the information about the operation progress.

Finally, reset the RTU and, if no problem occurs, the console will display the information about the initialization progress of operating system and then the application). If all is correct, the message “CONF OK” should be shown. (Example2_7/24/2014 10:16:02 AM_2)CONF OK NO REDUNDANCY 2014-07-24

10:37:13.950 INFO

sysAutoLoadModule: Function coreDbShowState called

0x1fffe00 (tRootTask): usrAppInit exit

Figure 5-12. CPU correctly configured.

5.5 Monitoring Communications SM_SER allows monitoring its channels using the COM8 port. In order to use this monitoring tool, the following procedure should be follow: 1. The switch 12 of the SM_SER module must be ON 2. Connect the PC with the module using the COM8 port by default. This port can be changed to channel x using command SMx (more information later in this paragraph). 3. Open a terminal window similar to the console tool. A prompt for the SM_SER module should be shown, for example “SM_SER>”. Execute the command “help” and you can see a help with available commands:

5-8


Rev. 3.1 (01-09-2016) 

HE: Show this menu.



SNx: Start monitoring (sniff) for channel x, where x is from 1 to 8.



CSx: Show configuration of channel x. For example:





SMx: Change the monitor channel to channel x. This operation must be confirmed before channel x is the new channel monitoring. SV: Show the software version installed in the module (SM_SER).


5-9

Rev. 3.1 (01-09-2016)

Chapter 6. Local Acquisition 6.1 Introduction This chapter provides detailed information about the local acquisition management in the real-time database, named coreDb, of Baseline Software Platform. The aspects to be explained include: 

Description of coreDb main menu.



Signal identification.



Common operations in coreDb.



Signal configuration.

More information about coreDb in the Easergy Builder manual.

6.1.1 coreDb in Easergy Builder coreDb is the real-time database of Baseline Software Platform. This database stores all the information associated to the signals and the relationships with the I/O information managed by the Devices. These relationships are implemented through the associations of information sources and destinations. The information is arranged in tables which can retain data and values of different types of signals: 

Status: Digital inputs.



Analog: Analog inputs.



Setpoint: Analog outputs.



Command: Digital outputs or commands.

The user should be familiarized with the following concepts in order to understand the operation of coreDb: 







The database has an information producer-consumer arrangement. All points in coreDb are identified by a name and a description. A coreDb points can be assigned to different producers (sources) and/or consumers (destinations) of the information. A Device is a logical grouping of signals with common characteristics and a shared software (a controller). For example, a Device might be a set of signals that are acquired from a sensor, and the controller is the software module that implements the communication protocol. Some example of available Devices are (the controller's name is included in parenthesis): o

Saitel DP local acquisition. (LAQ).

o

Master and slave IEC101 (i1m and i1e).

o

Supervision (sup).

o

Master IEC103 (i3m)

Coordinate: Name or label associated to any signal managed by a Device. The label's format is defined for each Device and it identifies the signal uniquely.



Source: Information producer. Each point can be associated to more than one source.



Destination: Information consumer. Each point can be associated to more than one destination.



The source and destination allocations are made using the coordinates in coreDb, so the user needs to know their format in each Device.

For more information about the configuration of each point and the operation of Easergy Builder environment, you can consult the Easergy Builder manual and the user manual for each Device.

6.2 Centralized Local Acquisition The local acquisition Device for Saitel DP is named “laq” and it is create by default for each Saitel DP configuration.


6-1

Rev. 3.1 (01-09-2016)

Figure 6-1. Configuring local acquisition for Saitel DP The laq Device supports communication between inputs and the outputs managed by the acquisition blocks and coreDb points. The first step to configure the acquisition settings is including all I/O modules in the backplane. Section 5.2.1 in this manual provides a detailed description of the steps to be performed to configure the backplane. The configuration of each module according to the acquisition signals is explained in the following section. In Configuration mode, select coreDb tab in order to access to coreDb information:

Figure 6-2. coreDb Menu The information stored into each table is available selecting the corresponding tab: Status, Command, Analog and Setpoint. For example:

Figure 6-3. Status signals defined in coreDb This screen displays all status signals existing in coreDb. It specifies the name, the signal description, the producer (source) from which information will be sent and the consumer (destination) which will receive the information.

6.2.1 Information Processing How the information is treated by each I/O module or by the CPU depends on the type of signal. The processing of each type of data is shown below. For further details about this processing, please, consult the section “Signal Preprocessing and Acquisition Adjustment" in the manual “Saitel DP Modules”. 6-2


Rev. 3.1 (01-09-2016)

6.2.1.1 Digital Inputs The processing of digital inputs in Saitel DP includes: 







Filtering: The changes that take less than the user-specified time are rejected (Filtering time-TF). The aim of this filtering is to prevent changes caused by transients. Change memory: It applies to the signals set to "event". After an event, the signal's value is retained for a brief period of time (Change in memory- TM) before another event occurs. It must assure the correct detection by the logic. Settling Time - TS: Only for signals configured as double. They are controlled by the CPU, not by the I/O module. In digital signals defined as double signals, the stand-by time intends to create a time frame in which the deactivation of the active input is not detected until the other input is activated. Chronological record: This feature is applicable to the inputs configured as indications or numeric values. The inputs configured with chronological record generate an input with time marking when a status change is made to the inputs.

6.2.1.2 Digital Outputs Saitel DP can manage standard digital signal controlled by a direct execution command. They can operate as latched signals or pulsing variable pulse time. These signals can be associated to simple or double points in coreDb: 

Simple pulsing and retained output (DO_OSIM).



Double pulsing and retained output (DO_ODOB).

WARNING 



Please note that when a point is defined as double in the coreDb, the two associated field signals must have a contiguous wiring in the same acquisition block. When the RTU is operating under a “Local” mode, all the commands received on the digital outputs are rejected. This is not applicable for analog outputs

The following items are important for the processing of the commands: 

Pulse Time: It applies only when the output is set to pulsing (Latch”N”). It allows the output timing to be defined (Execution time - ExeTime).

6.2.1.3 Analog Inputs The processing of analog inputs in Saitel DP includes: 









Input range: We can define the input range (EMin and EMax in field units and Rng in engineering units) for each analog signal. Range limit detection: If after converting to engineering units, the system detects that the value exceed the lower or upper limit range, the quality bit associated to the corresponding signal is flagged. Analog points allow up to four alarms to be set which are triggered when they cross a defined threshold value (ALARM LOWEST LIMIT, ALARM LOW LIMIT, ALARM HIGH LIMIT, and ALARM HIGHEST LIMIT). Digital filtering: It applies a digital filtering to minimize the noise effects. Scaling at Engineering Units: Conversion of analog measuring value expressed in field units into engineering units (UI) according to the values specified in input ranges. Based on these values, the system defines the scaling formula which will be used to convert the field values to its matching engineering units within a valid range. Cancellation of values close to zero: Filter that eliminates the undesired changes to the signal. The user defines a lower limit range for field values, and any input value within this range is interpreted as zero. The lower limit range is defined as a percentage of the total input range.

6.2.1.4 Analog Outputs The processing of analog outputs in Saitel DP includes: 





Output range: We can define the output range (EMin and EMax in field units and Rng in engineering units) for each analog signal. Scaling at Engineering Units: Conversion of engineering units (UI) into analog measuring value expressed in field units according to the values specified in output ranges. Based on these values, the system defines the scaling formula which will be used to convert the engineering unit to its measuring value within a valid range. Keeping signal: This feature allows keeping the output when the link with the module is broken.


6-3

Rev. 3.1 (01-09-2016)

6.2.2 Configuring the Local Acquisition The local acquisition software is intended to exchange the information with the I/O modules installed in Saitel DP. In relation to the acquisition strategy of the local acquisition, the communication is established using Profibus. It is a master/slave protocol based on polling operations, that is, all modules are polled sequentially one after the other. Any information related to the Profibus DP protocol is configured through the profibusdp.xml file, being generated by Easergy Builder. A profiXXX.xml file is generated for each configured module, which allows setting the attributes of each managed signal. The XXX string represents the module’s Profibus address.

NOTICE The valid range for Profibus address in Saitel DP is between 0 and 96. The following types of modules can be configured:

Figure 6-4. Available Saitel DP modules in Easergy Builder. Each acquisition signal is associated to a coreDb point as source. This point can be used as a source or destination for others coreDb points. To access to the local acquisition configuration interface, double-click on the laq Device:

Figure 6-5. Configuring local acquisition. Acquisition strategy Set the refresh and integration periods for the different types of signals. Add a new module Add a new module. Remove a module Remove a module.

6-4


Rev. 3.1 (01-09-2016)

Change address of the selected module Change the address for a module. Create module points on coreDb Create in coreDb acquisition and diagnostics points for all included modules. Save LAQ configuration Save the current Device’s settings in a XLB file. Load LAQ Configuration Load the Device’s settings previously saved in a XLB file.

6.2.2.1 Configuring the Acquisition Strategy

Figure 6-6. Configuring the acquisition strategy.









Profibus Rate: CPU communication rate with I/O modules. All I/O modules must be set with the same value. Analog and Digital Period: Interval of time for the acquisition of analog and digital inputs signals when they are configured to be updated periodically (ChgEvt of the signal is set to “N”). Default value for digital signals is 1000 ms and for analog signals is 300 ms. Both values have to be changed in intervals of 100 ms. Integrity Period: When a digital signal is set to be updated by event (ChgEvt of the signal is set to “Y”), this value indicates that if during this time no event occurred, the signal is updated anyway. This assures the integrity of the signal. Default value is 300 s and it has to be changed in intervals of 100 ms. Filter DI: Mark this field to configure the filtering parameters for digital inputs. o

Rebound changes: Number of changes necessaries for activating the anti-rebound filter (default value = 5).

o

Detection period: Time window when the number of rebound will be counted in order to activate the antirebound filter blocking the signal. This time is expressed in seconds (default value = 1 s).

o

Unlock period: Time without changes in a blocked signal in order that this signal is unblocked. This time is expressed in seconds (default value = 1 s).

6.2.2.2 Adding New Modules Press “Add New Module” to add new modules. The following window will appear:


6-5

Rev. 3.1 (01-09-2016)

Figure 6-7. Adding new I/O modules Select the module to be included on the list. Enter the number of modules of the selected type to be added in the field “Number ”. Select OK button and new modules will be included in the RTU. A Profibus address is automatically assigned to each module. This address can be changed using button

.

The new address can be selected. Only unassigned addresses will be available. Once the modules are added, it is necessary to configure the associated signals. To do so, click the corresponding module on the picture and its signals will be shown.

Figure 6-8. Configuring acquisition signals for a I/O module The configuration for each type of module which can be added is explained in further sections.

6.2.2.3 Deleting a Module To delete a module, select it on the picture and use button the operation.

. The module will be removed from the tree after confirming

6.2.2.4 PLC Configuration By selecting a PLC module on the picture, the following configuration window will be displayed:

6-6


Rev. 3.1 (01-09-2016)

Figure 6-9. PLC module configuration There are three tabs; Configuration of the PLC, Inputs configuration and Outputs configuration.

PLC Configuration The information entered in “Device ID”, “Param Data” and “Config Data” fields must be consistent with the information contained in the GSD file provided by the PLC’s manufacturer which is being configured. 







Name: Device or PLC's name PFB ID: PLC Identifier; a 4-digit hexadecimal number provided by the manufacturer. Enter the string labeled as Ident_Number in the “General Parameters” tab included in GSD file. For example, if “Ident_Number = 0x05FC”, the user should indicate “05FC” as PFB ID. Param Data: These are the data to be sent by the master Profibus when “Send Parameter Data” is enabled. In the GSD file, there is a section named “UserPrmData: Length and Preset:” which includes a string labeled as User_Prm_Data. This string will be entered in this field. For example, “User_Prm_Data=0x00,0x00,0x00”. Config Data: Sequence of bytes in hexadecimal that describes the map size for inputs and outputs for the Profibus slave. The documentation of the slave (device master file) must specify the map size of inputs and outputs. The format of these bytes is described in the standard EN 50170-8-2: 1996 page 832. A partial length is detailed simultaneously in each byte for inputs, outputs or inputs and outputs. The length of the complete map is the addition of the length indicated in all bytes. Below is an excerpt from the standard explaining the bytes format in hexadecimal::

Figure 6-10. Example of a PLC Configuration A GSD file is the configuration file supplied for the provider for the PLC. Following table shows a part of this file for a PLC by ABB:


6-7

Rev. 3.1 (01-09-2016) … ;=========================================================== ;General parameters ;=========================================================== GSD_Revision

=3

Vendor_Name

="ABB"

Model_Name

="PDP22-FBP ABB"

Revision

="V 1.0"

Ident_Number

=0x082D

Protocol_Ident =0 Station_Type

=0

… ;============================================= ; Module Definition List ;============================================= ; Module="UMC22-FBP (V3.0)" 0x11, 0x21, 0x50

; 16DI, 16DO, 1AI

1 Ext_Module_Prm_Data_Len=42 Ext_User_Prm_Data_Const(0) =

; number of used data byte \ ; initialising of param data 0x00,0x00,0x00,0x32,0x00,0x01,0x00,0x00,0x00,0x32,0x01, \ 0x01,0x01,0x00,0x0A,0x1E,0x04,0xB0,0x00,0x01,0x02,0x04, \ 0xB0,0x00,0x00,0xC8,0x00,0x14,0x00,0x00,0x00,0x00,0x00, \ 0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x0A,0x00

The content of the identifier “Ident_Number” must be included into the field “PFB ID”. The hexadecimal numbers following the module’s name must be included into the field “CFG_DATA”. Finally, the hexadecimal string following the identifier “Ext_User_Prm_Data_Const(0)” must be included into the field “PARAM_DATA”.

Inputs and Outputs Signals in the PLC When the content of the messages to be exchanged with the PLC is completely defined, the user can configure the input and output signals which will store the information contained in these messages. Use “Add” and “Remove” buttons to add and remove inputs from the list, respectively. After pressing “Add”, an input will be added with default settings, which can be modified, (except NUMBER) by clicking the selected item. Select an input and press the “Remove” button to delete it from the list. Press “Add” on the tab “Inputs” and a new Input will be created. The information associated for each signal is: 

Point number.



Point’s name



Type of point (size in bits within the message). The size can be 1, 2, 8, 16, 32 bits or 1 bit event.



Address of the information related to the signal within the message.

6.2.2.5 SM_AI16 Configuration By selecting a SM_AI16 module you can see the following window:

6-8


Rev. 3.1 (01-09-2016)

Figure 6-11. SM_AI16 Module Configuration This module includes 16 analog signals to be configured. Each signal has associated the following fields: 





PROFI_AIx: Signal description. This value can be changed although it does not affect the signal’s identification, as its identification label, which is automatically attached, is internal and cannot be changed. This is applicable to all signal descriptions in all modules. Rng: Signal’s voltage range. EGU: Flag indicating whether engineering units are considered. El value “N” indicates “engineering units” (the Bin output will be between EMIN and EMAX) and the value “Y” indicates “counts”. These signals when configured in counts can take a value between: o EMin: Minimum value expressed in engineering units. The range is: -32768 to 32767. o EMax: Maximum value expressed in engineering units. The range is: -32768 to 32767.



The “AC FILTER” field is associated to a band rejection filter at 50/60 Hz to avoid the damaging effects of network noise. If no filter needs to be used, set NONE.

6.2.2.6 SM_AI8AO4 Configuration Select a SM_AI8AO4 module on the tree to open the configuration screen, which includes a module with analog inputs and outputs. The configuration window has two panels: 

Analog Inputs



Analog Outputs

The analog inputs panel is identical to the panel described for SM_AI16 module, but this time it has 8 signals only instead of 16 (see Figure 6-11). The second panel, labeled as “Analog Outputs” is used to configure the analog outputs:


6-9

Rev. 3.1 (01-09-2016)

Figure 6-12. Configuration of analog outputs in a SM_AI8AO4 module





Rst: Value taken by the output after a CPU reset (% of output range). Keep: If the value is set to “Y” the output is retained. if the communication with the CPU is lost.

Other parameters on this screen are detailed in paragraph “SM_AI16 configuration”.

6.2.2.7 SM_DI32 Configuration Select a SM_DI32 module on the tree to open the configuration screen:

Figure 6-13. Configuration of digital inputs in SM_DI32 module For each signal, the following items can be defined: 



PROFI_STSx: Signal description Input type. The following options are available: o DI_ISIM: Simple Digital o DI_IDOB: Double Digital o DI_ICNT32: Slow Counter.

NOTICE Due to Profibus streaming size, there are limitations in the configuration of SM_DI32 modules; for example, they support a maximum of 25 accumulator inputs, or 2 double inputs 24 accumulator inputs. 6-10


Rev. 3.1 (01-09-2016) 











ChgEvt: It indicates whether changes may generate events. The “Y” value will generate events, whereas “N” value will not generate them. Invert: It indicates whether the signal is inverted. TF: Filtering time expressed in milliseconds; a change in the value which last less than the TF will not be registered. Thus, glitches will not be detected. TM: Time in memory, expressed in units of 10 milliseconds. It is the time that a pulse will be stored in memory in order to ensure the correct detection by the logic executed. DBLCNT: Flange counter. This field is available for DI_ICNT32 signals; the value “Y” indicates that the two flanges of each pulse are counted, whereas the value “N” indicates that only one flange is counted. TS: Settling time, expressed in units of 100 milliseconds. This field is only definable for double signals. It is the maximum allowed time in an invalid state (11, 00).

If any signal is set a double digital signal, the next signal available will be disabled, since a double signal takes two signals:

A detailed explanation of TF, TM, and TS is included in the corresponding section of the Saitel DP module manual. If a signal is set as DI_ICNT32, the parameters to be defined include the filed DBLCNT. The value “Y” indicates that both flanges of each pulse are counted, whereas the value “N” indicates that only one flange is counted.

Finally, the button labeled with an horizontal arrow is used to access the rest of digital inputs of the module, that is, from 17 to 32.

6.2.2.8 SM_DO16R Configuration The following configuration panel is displayed when selecting a SM_DO16R module:

Figure 6-14. SM_DO16R module configuration For each signal, the following items can be changed: 



PROFI_DOx: Signal description Signal type. The following items can be selected: o DO_OSIM: Simple digital output. o DO_ODOB: Double digital output.


6-11

Rev. 3.1 (01-09-2016) 



Latch: The value “Y” indicates the signal is retained, whereas the value “N” indicates it is not. ExeTime: Time in which the signal’s value is retained. It is applied when the value of field Latch is “N”. The value is expressed in milliseconds, but its accuracy is 100 ms.

Like digital inputs, if you set a signal as DO_ODOB, the following signal is not available:

6.2.2.9 SM_DO32T Configuration The configuration panel for SM_DO32T module is identical to the panel of SM_DO16R explained above (see Figure 6-14).

6.2.2.10

Generating Point in coreDb

When all modules have been configured in the acquisition local panel, all acquisition and supervision signals associated to these modules have to be included in coreDB by pressing button

.

For example, for the module SM_AI16, the following signals are include into the analog table:

Figure 6-15. Analog signals included in coreDb.

6.2.3 Signal Identification - Coordinates The coordinate is an unique identifier of a signal within a Bin. Its definition is different for each Device and the local acquisition is defined with ten digits with the following format: 2 BBB CC DDDD 





2: The first number of its coordinate for all Saitel DP local acquisition signals will be 2. BBB: Three digits to indicate the point address according to the previous communication protocol. In the case of Profibus-DP, the address range is from 000 to 125. CC: Type of signal, which includes: o

00: Diagnostic signals of the acquisition modules.

o

01: Analog input (16-bit).

o

02: Simple digital input (1 bit).

o

03: Counter (32 bits).

o

04: Analog output (16 bits).

o

05: Simple digital output (1 bit).

o

07: Double digital input (2 bits).

o

08: Frequency meter (32 bits).

o

09: Quick counter (32 bits).

o

10: Digital input (1 bit) (Inputs table of Profibus).

o

11: Digital input (2 bits) (Inputs table of Profibus).

o

12: Analog input (8 bits) (Inputs table of Profibus).

o

13: Analog input (16 bits) (Inputs table of Profibus). 6-12


Rev. 3.1 (01-09-2016)



o

14: Analog input (32 bits) (Inputs table of Profibus).

o

15: Double digital output (2 bits).

o

16: Digital output (1 bit) (Inputs table of Profibus).

o

17: Digital output (2 bits) (Inputs table of Profibus).

o

18: Analog output (8 bits) (Inputs table of Profibus).

o


o


DDDD: Number of the signal within each type, that is, it does not need to match the physical position. The first signal of a type will be 0000, the second will be 0001 ..., with all the types of the previous point.

For example, if a coreDb point has associated the signal 2003020002 as source, then it means that this point of coreDb takes it’s the same value that the signal (0002) of the DI_ISIM (02) type, in the module with address 003, according to Profibus-DP (2) protocol.

6.2.4 Diagnostic Signals The following tables describe the coordinates of the diagnostic signals provided by the local acquisition controller. They are valid for all modules except for the STS_PPS indication, which is only available in those modules with a digital input. It will adopt the correct value for the rest of modules. Its name and complete coordinate (for this signals CC=00) is equivalent: Coordinate Name

DDDD

STS_COMM STS_DIAG

Description

0000 0001

Module offline. Value 1 indicates that there is not communication with the module. Module with diagnostics. Value 1 indicates a diagnostics. Usually correspond to a polarization failure in the module.

STS_PPS

0002

PPS Indication. Value 1 indicates that there is a digital input configured as event in the module and PPS signal is not received.

STS_FAILBUS1

0003

Value 1 indicates a communication failure in Profibus1.

STS_FAILBUS2

0004

Value 1 indicates a communication failure in Profibus2. Table 6-1. Diagnostic signals of the Saitel DP local acquisition.

If a coreDb point has assigned the signal 2003000000 as source, the value of this point indicates the communication status of the module 003 (address). The value of the signal 2007000004 changes to 1 when the communication with the module 007 is lost.

6.2.5 Signal Calibration Saitel WebTool allows calibrating the Saitel DP signals. All information about this process is explained in the Saitel WebTool manual.

6.3 Transferring Databases to the RTU By now, you have completed the following tasks: 

Configuring the backplane with Easergy Builder



In the PC, you have configured the local adquisition

The next step is transferring the databases from the PC to the CPU. In Configuration mode of Easergy Builder, press button

. In Workspace mode, select the configuration to

be transfer and press button . Save the project and the configuration will be transferred to the CPU. Consult the operation progress on the log window. Finally, reboot the RTU and, if no problem occurs, the console will display the information about the initialization progress of operating system and then the application).


6-13

Rev. 3.1 (01-09-2016)

Chapter 7. Console Commands 7.1 Introduction The operating system provides a high-priority command interface to perform monitoring and advanced diagnostic operations.

NOTICE The use of this console interface must be restricted to expert operators of the system. The console connection to the CPU module is established through the front connector CON. More information about this connection in paragrah 4.2 in this manual.

7.1.1 SM_CPU866 Console It is an open tool that allows executing all available commands in both, operating system and application software. Following paragraphs include information about OS commands (paragraph 7.2) and application commands (paragraph 7.4).

7.1.2 SM_CPU866e Console SM_CPU866e console is more limited than SM_CPU866 console. It doesn’t allow executing commands in a prompt. When the user access to the console, only the BLMon menu is available. The available commands could change depending on the version of the Baseline. Following paragraphs include information about BLMon for the Baseline 11.05.11 (paragraph 0) and application commands (paragraph 7.4).

7.2 VxWorks Commands (only SM_CPU866) This paragraph shows some examples of VxWorks commands. For more information about all available commands, please, refer the VxWorks documentation. Command Help

Parammeter / Description (without parameters) Show help about some general VxWorks commands.

i

(without parameters) Show the status and information about all the tasks.

devs

(without parameters) Show the devices within the system.

version

(without parameters) Show information about the version of VxWorks kernel and BootRom configuration. This information doesn’t include information about the Saitel Software.

pwd

(without parameters) Show the actual working directory.

cd “” Change the working directory to < directory >, i.e, cd "/flash" allows changing the working directory to the device /flash). ls

(without parameters) Show the name of the files in the working directory.


7-1

Rev. 3.1 (01-09-2016) Command ll

Parammeter / Description (without parameters) Show detailed information about the files in the working directory.

rm “” Delete the file named . chkdsk “” Show information about the status of the device < device>. lkup “” Search in the table of system symbols the symbols which contains the text < string >. It is very useful for example to found a command that you don’t know its correct syntax. For example:

The command lkup “Sniff” returns all available commands with the text “Sniff”. reboot

(without parameters) Reboot the CPU. Be careful with this command because it doesn’t ask to the user for confirmation.

bootChange

(without parameters) It allows changing the boot settings of BootRom.

ping

Ask to the device with the indicated IP address for a response.

ioHelp

(without parameters) Show help about VxWorks I/O commands.

netHelp

(without parameters) Show help about VxWorks net commands.

ifShow

(without parameters) Show information about network interfaces.

7.3 BLMon Commands (only SM_CPU866e) When an user login on the console de SM_CPU866e, the menu of BLMon is shown. This menu includes the following commands:

Command m

Parammeter / Description Print this menu. Selecting “m”, the BLMon main menu is shown.

s

Show coreDb state. Show the general state of the coreDb. This command is similar to “coreDbState”.

7-2


Rev. 3.1 (01-09-2016) Command t

Parammeter / Description Show thm information. Show the sinchronization state. This command is similar to “thmShow”.

e

Start events monitoring. If command “e” is executed, the monitorization event is started. This command is similar to “coreDbShowEvents”.

u

Stop events monitoring. If command “u” is executed, the monitorization event is stoped. This command is similar to “coreDbUnShowEvents”.

c

Start channel monitoring.

Start the monitorization for a communication channel. This command shows all configured channels and asks user to select one of them. You coud press “enter” in order to cancel this command. This command is similar to “chanSniffOn” o

Stop channel monitoring. If command “o” is executed, the monitorization of all channels is stoped. This command is similar to “chanSniffOff”.

l

Start link monitoring.

Start the monitorization for a communication link. This command shows all configured links and asks user to select one of them. You coud press “enter” in order to cancel this command. This command is similar to “chlnSniffOn”. f

Stop link monitoring. If command “f” is executed, the monitorization of all links is stoped. This command is similar to “chlnSniffOff”.

i

View network settings. This command shows all information about network interfaces. ¡¡WARNING!! Have in account that the phisical name shown in the output of this command (ethx) is not the same that the name of each port on the silk-screen.


Silk-screen (Module’s faceplate)

Command output

ETH1

eth1

ETH2

eth0

ETH3

eth3

ETH4

eth2

7-3

Rev. 3.1 (01-09-2016)

This command is similar to the system commands “ifconfig” and “route”. p

Show processes. Information about all process that are running in the CPU. This command shows the output of the system command “ps –eTcl”.

v

Show OS version. Pressing “v” the Linux version is shown. It is similar to the system command “version”.

7-4


Rev. 3.1 (01-09-2016) Command b

Parammeter / Description Show baseline version. Pressing “b” the Baseline version is shown. It is similar to the command “baselineShowVer”.

h Help. Pressing “h” you can see a detailed help about any available command in the system. In addition to commands included in the menu, the user has additional commands that can be executed using the prompt BLMon. Press "h", write the desired command in FUNCTION_HELP and a detailed help will be shown with the correct sintax. If you write "a" when FUNCTION_HELP is required, a list with all available commands is shown. More information about these commands in paragraph 7.4.

7.4 Saitel Commands This paragraph shows the more used commands available for both CPU, SM_CPU866 and SM_CPU866e: Command baselineShowVer

Parammeter / Description (without parameters) Show versions of all loaded modules. For example:

chanShowVer

(without parameters) Show information about the channels management module.

chanSniffOn

“” Enable the transparent mode for the specific channel. The channel’s name matches with the name defined in the channel module. It is can be disabled with chanSniffOff .

chanSniffOff

“” Disable the transparent mode for the specific channel. It was enabled with chanSniffOn.

chlnSniffOn

“” Enable the transparent mode for the specific link. It is can be disabled with chlnSniffOff .

chlnSniffOff

“” Disable the transparent mode for the specific link. It was enabled with chlnSniffOn.

dnpeShowVer

(without parameters) Show information about the slave dnp module.


7-5

Rev. 3.1 (01-09-2016) Command dnpmShowVer

Parammeter / Description (without parameters) Show information about the master dnp module.

laqShowVer

(without parameters) Show information about the version of the local acquisition Bin Controller.

laqPfbMShowVer

(without parameters) Show information about the version of the Profibus module.

laqShowEvents

(without parameters) Start local acquisition events monitoring.

laqShowMod
Show information about the module with the number
. For example, for module SM_AI8AO4 configured with address 6, the following information is shown:

laqUnShowEvents

(without parameters) Stop local acquisition events monitoring.

logbaselineShowVer

(without parameters) Write in sysLog the versions of all loaded modules.

pfbSniffOff

(without parameters) Stop Profibus monitoring.

pfbSniffOn

(without parameters) Start Profibus monitoring.

supCpuUsage

(without parameters) Show CPU usage.

supShowVer

(without parameters) Show information about the supervision module.

sup_wdShowTaskList

(without parameters) Show tasks that have been suscribed to watchdog.

thmConsoleSetTime

“:< MM>:
::< MM>:< S S >” Allow changing the synchronization time of the RTU using the console. For example:

7-6


Rev. 3.1 (01-09-2016) Command thmShow

Parammeter / Description (without parameters) Show information about the synchronization status of the RTU.

thmShowVer

(without parameters) Show information about the synchronization module.

x_blockPoint

“”, “< Poi nt name>”, If is 1, block the point . If is 0, unlock the point NOTE: The must be wrote without quotation marks.

x_krunchData

“”, “< Poi nt name>”, “” Write a point. For example: x_krunchData “setPoint”, “M006_AO_000”, “20”. You can view the new value of this point with Saitel Webtool or using the command x_readData. NOTE: All parameters must be wrote within quotation marks.

x_overridePoint

“”, “< Poi nt name>”, If is 1, set override value for the . If is 0, clear override value for the NOTE: The must be wrote without quotation marks.

x_readData

“”, “< Poi nt name>” Read information from coreDb and print it on the console window. For example:


7-7

Rev. 3.1 (01-09-2016)

Glossary A

Ampere.

SM_AI16

I/O module with 16 analog inputs

SM_AI8AO4

I/O module with 8 analog inputs and 4 analog outputs.

SM_CPU866

Standard control module.

SM_CPU866e

High-performance control module.

SM_DI32

I/O module with 32 digital inputs.

SM_DO16R

I/O module with 16 digital outputs to relay.

SM_DO32T

I/O module with 32 digital outputs to transistor.

SM_PS

Standard power supply.

SM_PS40

High-performance power supply.

SM_SER

Serial communications module.

AD

Analog Destination.

AI

Analog input.

ANSI

American National Standards Institute

AO

Analog output.

BaseLine

Telvent’s Software Platform.

Bps

Bit per second.

laq

Saitel DP Local acquisition Bin Controller .

CATconfig

Saitel configuration tool.

Saitel Webtool

Saitel monitoring and maintenance tool.

COM

Communication port.

CON

Console port.

coreDb

Real-time database of Saitel.

CPU

Central Processing Unit.

DB

Database.

DI

Digital input.

DIN

Deutsches Institut für Normung. German institute for standardization.

DO

Digital Output.

Ds

Decisecond

EGU

EnGineering Unit

EN

English language.

ETH

Ethernet port.

B


Rev. 3.1 (01-09-2016)

Ethernet

Technology used to implement networks through different physical media, including twisted pair and coaxial cables.

FTP

File Transfer Protocol

GMT

Greenwich Mean Time

GPS

Global Positioning System

Hz

Hertz, frequency express in cycles per second.

IEC

International Electrotechnical commission

IED

Intelligent Electronic Device

I/O

Input / Output

IP

Internet Protocol

ISO 9001

International Standard which regulates the requirements of a control management system.

kbaud

Kilobaud.

LAN

Local Area Network.

LAQ

Local AcQuisition.

LED

Light Emitting Diode.

Mbaud

Megabaud.

mm

Millimeter.

ms

Millisecond.

MSAC

Supervision, Arbitration and Switching Module.

NVRAM

Non Volatile Random Access Memory.

PC

Personal Computer.

PLC

Programmable Logic Controller.

RAM

Random Access Memory.

RCP

Redundancy Control asynchronous Protocol.

Rev

Revision.

RTC

Real Time Clock.

RTDB

Real-Time Database.

RTOS or OS

Real Time Operating System.

RTU

Remote Terminal Unit

SCADA

Supervisory Control and Data Acquisition

SNTP

Simple Network Time Protocol.

SOE

Sequence Of Events.

TCP

Transport Control Protocol.

TFTP

Trivial File Transfer Protocol.

UDP

User Datagram Protocol.

UTC

Universal Time Coordinated.


C

Rev. 3.1 (01-09-2016)

VDC

Volt (Direct Current).

VxWorks

Real-Time operating system used with some Saitel CPUs.

XLS

Excel binary file format.

XML

eXtensible Markup Language.

D


Configuration & Startup of Saitel DP_EN_Rev3.1

Recommend Documents