EIO0000000547 11/2009

RTU Configuration
Software
a SoCollaborative software
User Manual
11/2009
EIO0000000547.00

www.schneider-electric.com
 The information provided in this documentation contains general descriptions and/or
technical characteristics of the performance of the products contained herein. This
documentation is not intended as a substitute for and is not to be used for
determining suitability or reliability of these products for specific user applications. It
is the duty of any such user or integrator to perform the appropriate and complete
risk analysis, evaluation and testing of the products with respect to the relevant
specific application or use thereof. Neither Schneider Electric nor any of its affiliates
or subsidiaries shall be responsible or liable for misuse of the information contained
herein. If you have any suggestions for improvements or amendments or have found
errors in this publication, please notify us.
No part of this document may be reproduced in any form or by any means, electronic
or mechanical, including photocopying, without express written permission of
Schneider Electric.
All pertinent state, regional, and local safety regulations must be observed when
installing and using this product. For reasons of safety and to help ensure
compliance with documented system data, only the manufacturer should perform
repairs to components.
When devices are used for applications with technical safety requirements, the
relevant instructions must be followed.
Failure to use Schneider Electric software or approved software with our hardware
products may result in injury, harm, or improper operating results.
Failure to observe this information can result in injury or equipment damage.
2009 Schneider Electric. All rights reserved.

2 EIO0000000547 11/2009
 Table of Contents

Safety Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
About the Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Chapter 1 Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
General Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Software Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Chapter 2 RTU Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
RTU Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Chapter 3 RTU Configuration Software . . . . . . . . . . . . . . . . . . . . . . 17
Variable Name Creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Information Object Address. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Station Configuration Browser. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Common Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Device Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Single Points Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Double Points Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Measured Values Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Integrated Totals Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Single Commands Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Double Commands Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Set Points Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Import of Data to Unity Pro . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Edit Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Appendices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Appendix A RTU Application Example . . . . . . . . . . . . . . . . . . . . . . . . 37
Configuration with the Embedded Web Server . . . . . . . . . . . . . . . . . . . . . 38
RTU Configuration Software Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Resulting Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

EIO0000000547 11/2009 3
4 EIO0000000547 11/2009
 Safety Information

Important Information

NOTICE
Read these instructions carefully, and look at the equipment to become familiar with
the device before trying to install, operate, or maintain it. The following special
messages may appear throughout this documentation or on the equipment to warn
of potential hazards or to call attention to information that clarifies or simplifies a
procedure.

EIO0000000547 11/2009 5
PLEASE NOTE
Electrical equipment should be installed, operated, serviced, and maintained only by
qualified personnel. No responsibility is assumed by Schneider Electric for any
consequences arising out of the use of this material.
A qualified person is one who has skills and knowledge related to the construction
and operation of electrical equipment and the installation, and has received safety
training to recognize and avoid the hazards involved.

6 EIO0000000547 11/2009
 About the Book

At a Glance

Document Scope
This manual describes the RTU Configuration Software, which helps you to
parameterize variables that are used in a telecontrol module.

Validity Note
This documentation is valid for RTU Configuration Software V1.0.

Related Documents

Title of Documentation Reference Number

W315, W320E Remote Interface Units User Manual NT00135-EN-04
Unity Pro Reference Manual 35006144 (Eng),
35006146 (Ger)
Unity Pro Operating Modes Manual 33003101 (Eng),
33003103 (Ger)

You can download these technical publications and other technical information from
our website at www.schneider-electric.com.

User Comments
We welcome your comments about this document. You can reach us by e-mail at
techcomm@schneider-electric.com.

EIO0000000547 11/2009 7
8 EIO0000000547 11/2009
 Introduction
EIO0000000547 11/2009

Introduction

1
Overview
This chapter provides general information on the RTU Configuration Software.

What's in this Chapter?

This chapter contains the following topics:
Topic Page
General Information 10
Hardware Requirements 13
Software Requirements 14
Installation 14

EIO0000000547 11/2009 9
Introduction

General Information

Overview
The RTU Configuration Software helps you to parameterize variables that are used
in telecontrol modules.
The tool simplifies the configuration of variables significantly, because you configure
the variables per variable type instead of parameterizing every single variable.
NOTE: This tool is not an alternative to the embedded web server of telecontrol
modules, because it only covers the variable part and not the complete configuration
of telecontrol modules.

W@DE Modules
The W@DE TSXETW3xx product range is a PLC-based remote control solution
incorporating:
z operation in local or remote mode
z data archiving
z direct user alarm notification.

Each remote control interface communicates with a control station using Modbus,
IEC or DNP3 open protocols over a communication medium (Radio, PSTN, GSM,
RS232, Ethernet, USB).

10 EIO0000000547 11/2009
 Introduction

Data Flow
The following graphic shows the data flow between a telecontrol module, a PLC, the
RTU Configuration Software and Unity Pro.

EIO0000000547 11/2009 11
Introduction

Backup of Module Configuration

NOTE: It is recommended to save the telecontrol module configuration (created with
the embedded web server of the module) before importing the variable type
configuration (created with the RTU Configuration Software).

Build/Import
During installation of the RTU Configuration Software an additional library (RTU
library), providing the DFBs and DDT needed by the tool, is installed in Unity Pro.
Stages for build/import

Stage Description
1 Build of the configuration data out of the common settings and the different
variable types in the RTU Configuration Software.
2 Export of the generated data out of the RTU Configuration Software for:
z Unity Pro (Variable list and Sections)
z telecontrol module (variable configuration)

3 Import of the generated data to Unity Pro and to the telecontrol module.

For detailed information on how to build and import a configuration please refer to
User Interface (see page 20).

Save, Edit
For detailed information on how to save and edit a configuration please refer to User
Interface (see page 20).

12 EIO0000000547 11/2009
 Introduction

Hardware Requirements

PC

Component Description
System with Microsoft Windows Vista
System Pentium Processor 2.4 GHz or higher
recommended: 3.0 GHz
RAM Memory 1 GB minimum
recommended: 2 GB
Hard Disk minimum available free space: 100 MB
System with Microsoft Windows XP
System Pentium Processor 1.2 GHz or higher
recommended: 3.0 GHz
RAM Memory 512 MB minimum
recommended: 1 GB
Hard Disk minimum available free space: 100 MB

Component Description
Drive CD-ROM drive, to install the software
recommended: CD-ROM writer

Component Description
Display VGA (800-600) minimum
recommended: SVGA (1024-768 or more) with high color
24 bits

Telecontrol Modules
The following W@DE modules can be used with the tool:
z TSXETW315xx
z TSXETW320xxxx
z TSXETW325xxxx

PLCs
The following PLC platforms can be used with the tool:
z Premium
z Quantum
z Modicon M340

EIO0000000547 11/2009 13
Introduction

Software Requirements

General Software
The following software has to be installed on your PC:
z Microsoft Windows XP Professional or Microsoft Windows Vista
z Microsoft .NET Framework V3.5
z Microsoft Internet Explorer 5.5 or later
z Unity Pro 4.0 or later

After installing the software mentioned above you can start to install the RTU
Configuration Software 1.0.

Installation

Overview
To install, repair or remove the tool you have to start the setup.exe.
After starting the setup.exe follow the installation routine.
NOTE: Please refer to the Software Requirements (see page 14) before starting the
installation.

Result
The result of the installation process is the following:
z The RTU Configuration Software is available.
z A icon to start the tool is available in the Unity Pro toolbar.
z The additional RTU library, providing the DFBs and DDTs needed by the tool, is
available in Unity Pro.

14 EIO0000000547 11/2009
 RTU Library
EIO0000000547 11/2009

RTU Library

2
RTU Library

Overview
During installation of the RTU Configuration Software an additional library (RTU
library), providing the DFBs and DDT needed by the tool, is installed in Unity Pro.
These DFBs/DDT must be available before you can import the variable list and
sections generated by the RTU Configuration Software.

DFBs
The RTU Configuration Software needs the following DFBs:

DFB Name Description

IEC_DTI calculation of the number cycles per seconds
IEC_RTU_COMMAND Word to Bit
IEC_RTU_TimeSync time synchronization after PLC restart (second, minute, hour,
day, month, year, weekday)
IEC_SCAL_ME scaling of data values

EIO0000000547 11/2009 15
RTU Library

DDT
The RTU Configuration Software needs the DateAndTime DDT.
The DateAndTime DDT has the following structure:

Element Data Type

hour INT
minute INT
second INT
day INT
month INT
year INT
monday BOOL
tuesday BOOL
wednesday BOOL
thursday BOOL
friday BOOL
saturday BOOL
sunday BOOL
weekday BOOL
weekend BOOL
summertime BOOL
IV BOOL

16 EIO0000000547 11/2009
 RTU Configuration Software
EIO0000000547 11/2009

RTU Configuration Software

3
Overview
This chapter provides information on the RTU Configuration Software.

What's in this Chapter?

This chapter contains the following topics:
Topic Page
Variable Name Creation 18
Information Object Address 19
User Interface 20
Station Configuration Browser 22
Common Settings 23
Device Configuration 24
Single Points Properties 25
Double Points Properties 26
Measured Values Properties 27
Integrated Totals Properties 28
Single Commands Properties 29
Double Commands Properties 30
Set Points Properties 31
Import of Data to Unity Pro 32
Edit Variables 33

EIO0000000547 11/2009 17
RTU Configuration Software

Variable Name Creation

Overview
The variable names are automatically generated from different data entered in the
interface of the RTU Configuration Software.
For detailed information on the different data please refer to the Device
configuration section and the respective variable types (e.g Single points)
sections.

Name Creation
The following data is used to generate the variable names:

Data Defined in Description/Comment

Station prefix Device configuration optional
properties window This prefix is only used to generate the
variable names, if the Prefix is used
check box is activated.
Example: Station01
Prefix properties window of the IEC variable type specific prefix
respective variable type This prefix is merged with a 4-digits
(e.g. Single points incremental number.
properties window) Example: SP0001
Objects address properties window of the starting object address of the related IEC
respective variable type variable type
(e.g. Single points Example: 102
properties window)
Objects start Device configuration station address
address properties window The specific %MW Object address of a
variable is calculated from the inserted
Objects start address. Example: 100

The concatenated data are separated from each other with an underline.
Example: Station01_SP0001_102_100

WARNING
UNINTENDED EQUIPMENT OPERATION
Test and verify the complete configuration and the final application.
Ensure that no mistakes were made during configuration.
Failure to follow these instructions can result in death, serious injury, or
equipment damage.

18 EIO0000000547 11/2009
 RTU Configuration Software

Information Object Address

Overview
According to the IEC-60870/101 and 104, the information object address (IOA) is
used to identify the configured data points in the telecontrol module.
Together with the hardware address (the link address for a Modbus Serial Line
connection or the IP address for a Modbus TCP/IP connection) and the sector
address (common address) the data points can be accessed from outside of the
device.

EIO0000000547 11/2009 19
RTU Configuration Software

User Interface

Overview
The user interface consists of several windows, a menu bar and a toolbar.

Legend

Number Description
1 Menu bar
z (File New, Open, Save, Save As, Exit)
z (Build Configuration, Prepare Unity Pro Part...)
z (Extras Cleanup Log-Window)

2 Toolbar (New, Open, Save)

3 Station Configuration Browser (see page 22)
4 Properties window
The displayed properties depend on the variable type selected in the
Station Configuration Browser at the left.
For the different variable type properties please refer to the subsequent
sections.
5 Information window (provides information on the status of operations)
You can clear the information window using Extras Cleanup Log-
Window.

20 EIO0000000547 11/2009
 RTU Configuration Software

Saving the Configuration

To open, save or exit the configuration, use the menu bar or the toolbar.
You can save the configuration to any folder you like to.
The configuration is saved as a *.config file.

Building the Configuration

To build the configuration use Build Configuration.
When building the configuration, a sub-folder is created in the folder you saved your
configuration to, named as your configuration file.
Example: MyConfiguration.config will result in a sub-folder MyConfiguration.
This sub-folder (e.g. MyConfiguration) contains:
z a file Variables.TXT (telecontrol module variable list)
z another sub-folder for each station you defined in your configuration (named as
the respective station) with
z a variable list, the structures and the sections for Unity Pro

Editing the Configuration/Variables

To edit the configuration or the variables, use the Configuration or the Variables
tab.
Now you can modify your configuration or variables and add comments in a list
format.

Importing the Data

The generated data for the telecontrol modules you have to import manually.
For Unity Pro the import is done automatically using Build Prepare Unity Pro
part.... Please refer to Import of Data to Unity Pro (see page 32).

EIO0000000547 11/2009 21
RTU Configuration Software

Station Configuration Browser

Overview
The Station Configuration Browser provides to
z add, delete or rename a station
z select the group of properties you want to edit (for example Common settings,
Monitoring Single points, Controlling Single commands)

Adding, Deleting or Renaming the Station

Right-click a station and select the respective item from the context menu (Add,
Delete, Rename).

22 EIO0000000547 11/2009
 RTU Configuration Software

Selecting a Group of Properties

To select a group of properties you want to edit, click on of the following items/sub-
items:
z Device configuration (see page 24)
z Monitoring (data, read from the station)
z Single points (see page 25)
z Double points (see page 26)
z Measured values (see page 27)
z Integrated totals (see page 28)

z Controlling (data, written to the station)

z Single commands (see page 29)
z Double commands (see page 30)
z Set points (see page 31)

Common Settings

Overview
Select Common settings in the Station Configuration Browser to open the
Common settings properties window.
In this window you can define up to 5 Cycles (range: 0..100000 ms).
The defined Cycles are available in the Query cycle drop down list of the different
variable types (e.g. in the Single points properties window).

EIO0000000547 11/2009 23
RTU Configuration Software

Device Configuration

Overview
Select Device configuration in the Station Configuration Browser to open the
Device configuration properties window.
In this window you can define the general settings for each station configuration.
For information on how variable names are generated please refer to Variable Name
Creation (see page 18).

Data/Properties
You can define the following data/properties in the Device configuration properties
window:

Data Property Description

Description This station description of the station
manages ... for
example
Version 0.0.001 ... for version of the station configuration
example
PLC drop-down list PLC, the module communicates with
z M340
z Premium
z Quantum

Station prefix Station01 for prefix for the station

example This prefix will be used to generate the variable
names, if the Prefix is used check box is
activated.
Prefix is used check box If this check box is activated the Station prefix
generate the variable names.
Modbus slave 32 for example Modbus Serial Line slave address
address
Network address 192.168.19.2 Modbus TCP/IP address of the station
[x.y.z.n] for example
Objects start 1000 for example start address of the ASDU data (%MW)
address
Quality bits start 100 for example start address of the quality data (%MW)
address
Structure name RTU for example name of the variable structure in Unity Pro

24 EIO0000000547 11/2009
 RTU Configuration Software

Single Points Properties

Overview
Select Single Points in the Station Configuration Browser to open the properties
window of the Single Point variable type.
For information on how variable names are generated please refer to Variable Name
Creation (see page 18).

Data/Properties
You can define the following data/properties for the Single Point variable type:

Data Property Description

Prefix SP for example IEC variable type specific prefix
For variable name generation this prefix is
merged with a 4-digits incremental number.
Example: SP0001
Structure name SinglePoints name of the subelement of the variable structure
for example in Unity Pro
Number objects 10 for example number of variables of this type
NOTE: If this variable type is not used set the
number to 0.
Objects address 100 for example address of the first variable of this type
The Object address is used to access the
variables from a control station via a RTU
connection (according to IEC-60870/101 and
/104; DNP3).
Datatype BOOL for example Unity Pro datatype
Query cycle 1000ms for choice of cycle defined in the Common settings
example

NOTE: For all used variable types the Number of objects and the Objects address
have to be defined.

EIO0000000547 11/2009 25
RTU Configuration Software

Double Points Properties

Overview
Select Double points in the Station Configuration Browser to open the properties
window of the Double point variable type.
For information on how variable names are generated please refer to Variable Name
Creation (see page 18).

Data/Properties
You can define the following data/properties for the Double point variable type:

Data Property Description

Prefix DP for example IEC variable type specific prefix
For variable name generation this prefix is
merged with a 4-digits incremental number.
Example: DP0001
Structure name DoublePoints name of the subelement of the variable structure
for example in Unity Pro
Number objects 10 for example number of variables of this type
NOTE: If this variable type is not used set the
number to 0.
Objects address 200 for example address of the first variable of this type
The Object address is used to access the
variables from a control station via a RTU
connection (according to IEC-60870/101 and
/104; DNP3).
Datatype DBOOL for example Unity Pro datatype
Query cycle 1000ms for choice of cycle defined in the Common settings
example

NOTE: For all used variable types the Number of objects and the Objects address
have to be defined.

26 EIO0000000547 11/2009
 RTU Configuration Software

Measured Values Properties

Overview
Select Measured Values in the Station Configuration Browser to open the
properties window of the Measured Value variable type.
For information on how variable names are generated please refer to Variable Name
Creation (see page 18).

Data/Properties
You can define the following data/properties for the Measured Value variable type:

Data Property Description

Prefix ME for example IEC variable type specific prefix
For variable name generation this prefix is
merged with a 4-digits incremental number.
Example: ME0001
Structure name MeasuredValues name of the subelement of the variable structure
for example in Unity Pro
Number objects 10 for example number of variables of this type
NOTE: If this variable type is not used set the
number to 0.
Objects address 300 for example address of the first variable of this type
The Object address is used to access the
variables from a control station via a RTU
connection (according to IEC-60870/101 and
/104; DNP3).
Datatype INT for example Unity Pro datatype
Query cycle 1000ms for example choice of cycle defined in the Common settings
Variation method z TIMEINTEGRAL variation of a variable to avoid multiple events
z PERCENT with lowest values / value changes
z FIXED

Variation value 100 for example value for the configured Variation method
(Example for the variation method
TIMEINTEGRAL: integrated value until the data
point variable gets transmitted.
Variation 32767 for example reference value to which the measured value will
reference be normalized

NOTE: For all used variable types the Number of objects and the Objects address
have to be defined.

EIO0000000547 11/2009 27
RTU Configuration Software

Integrated Totals Properties

Overview
Select Integrated totals in the Station Configuration Browser to open the
properties window of the Integrated total variable type.
For information on how variable names are generated please refer to Variable Name
Creation (see page 18).

Data/Properties
You can define the following data/properties for the Integrated total variable type:

Data Property Description

Prefix IT for example IEC variable type specific prefix
For variable name generation this prefix is
merged with a 4-digits incremental number.
Example: IT0001
Structure name IntegratedTota name of the subelement of the variable structure
ls for example in Unity Pro
Number objects 10 for example number of variables of this type
NOTE: If this variable type is not used set the
number to 0.
Objects address 400 for example address of the first variable of this type
The Object address is used to access the
variables from a control station via a RTU
connection (according to IEC-60870/101 and
/104; DNP3).
Datatype INT for example Unity Pro datatype
Query cycle 1000ms for choice of cycle defined in the Common settings
example
Periodic event is check box If this check box is activated the integrated total
used values are saved periodically. See Periodic
event.
Periodic event 15 min for time span between 2 savings of the integrated
example total values
You can select the Periodic event data from a
list (10 sec up to 1 day).
This property is used only, if the Periodic event
is used check box is activated.
Reset value 1000000 for Overflow value that must be exceeded, for the
example integrated total value to be reset.

NOTE: For all used variable types the Number of objects and the Objects address
have to be defined.

28 EIO0000000547 11/2009
 RTU Configuration Software

Single Commands Properties

Overview
Select Single commands in the Station Configuration Browser to open the
properties window of the Single command variable type.
For information on how variable names are generated please refer to Variable Name
Creation (see page 18).

Data/Properties
You can define the following data/properties for the Single command variable type:

Data Property Description

Prefix SC for example IEC variable type specific prefix
For variable name generation this prefix is
merged with a 4-digits incremental number.
Example: SC0001
Structure name SingleCommands name of the subelement of the variable structure
for example in Unity Pro
Number objects 10 for example number of variables of this type
NOTE: If this variable type is not used set the
number to 0.
Objects address 500 for example address of the first variable of this type
The Object address is used to access the
variables from a control station via a RTU
connection (according to IEC-60870/101 and
/104; DNP3).
Datatype BOOL for example Unity Pro datatype

NOTE: For all used variable types the Number of objects and the Objects address
have to be defined.

EIO0000000547 11/2009 29
RTU Configuration Software

Double Commands Properties

Overview
Select Double commands in the Station Configuration Browser to open the
properties window of the Double command variable type.
For information on how variable names are generated please refer to Variable Name
Creation (see page 18).

Data/Properties
You can define the following data/properties for the Double command variable
type:

Data Property Description

Prefix DC for example IEC variable type specific prefix
For variable name generation this prefix is
merged with a 4-digits incremental number.
Example: DC0001
Structure name DoubleCommands name of the subelement of the variable structure
for example in Unity Pro
Number objects 10 for example number of variables of this type
NOTE: If this variable type is not used set the
number to 0.
Objects address 600 for example address of the first variable of this type
The Object address is used to access the
variables from a control station via a RTU
connection (according to IEC-60870/101 and
/104; DNP3).
Datatype DBOOL for example Unity Pro datatype

NOTE: For all used variable types the Number of objects and the Objects address
have to be defined.

30 EIO0000000547 11/2009
 RTU Configuration Software

Set Points Properties

Overview
Select Set points in the Station Configuration Browser to open the properties
window of the Set point variable type.
For information on how variable names are generated please refer to Variable Name
Creation (see page 18).

Data/Properties
You can define the following data/properties for the Set points variable type:

Data Property Description

Prefix SE for example IEC variable type specific prefix
For variable name generation this prefix is
merged with a 4-digits incremental number.
Example: SP0001
Structure name SetPoints for name of the subelement of the variable structure
example in Unity Pro
Number objects 10 for example number of variables of this type
NOTE: If this variable type is not used set the
number to 0.
Objects address 700 for example address of the first variable of this type
The Object address is used to access the
variables from a control station via a RTU
connection (according to IEC-60870/101 and
/104; DNP3).
Datatype INT for example Unity Pro datatype

NOTE: For all used variable types the Number of objects and the Objects address
have to be defined.

EIO0000000547 11/2009 31
RTU Configuration Software

Import of Data to Unity Pro

Overview
After building the configuration (Build Configuration), you can import the
application specific part automatically to Unity Pro by selecting Build Prepare
Unity Pro part....

Procedure

Step Action
1 Select the Station you want to import.
2 z Either open an existing Unity Pro application using Open: Unity
application...
z or create a new one using Create: Unity application...
z or import an existing XEF file using Import: Unity application...

3 Import the generated sections and variables of the selected station by clicking
the Generate button.

NOTE: Using Open: Unity application... or Import: Unity application... you have
to verify that the %MW addresses generated with the RTU Configuration Software
are not used for other variables in the Unity application you are opening or importing.

Batch Processing
NOTE: Using the so called Batch processing you can create 1 new Unity Pro
application for every station in 1 step.

32 EIO0000000547 11/2009
 RTU Configuration Software

Edit Variables

Overview
For each variable you can insert an additional comment in the variable list using the
Variables tab.

Also a measurement unit can be defined for the Measured values.

An optional text can be defined for all BOOL and DBOOL variables to indicate the
value of the variable.
This text can be displayed in an HMI for the values 1 or rather 0 of the variable.

XML File
After the generation, an Excel XML file is available for each station in the
corresponding folder, which documents the whole variable configuration.
The name of this file is build accordingly to the following scheme:
<Station Prefix>_VariablesExcel.xml

EIO0000000547 11/2009 33
RTU Configuration Software

34 EIO0000000547 11/2009
 EIO0000000547 11/2009

Appendices

EIO0000000547 11/2009 35
36 EIO0000000547 11/2009
 RTU Application Example
EIO0000000547 11/2009

RTU Application Example

A
Overview
This chapter provides information on the configuration of a W@DE module using the
RTU Configuration Software.

What's in this Chapter?

This chapter contains the following topics:
Topic Page
Configuration with the Embedded Web Server 38
RTU Configuration Software Settings 40
Resulting Variables 45

EIO0000000547 11/2009 37
RTU Application Example

Configuration with the Embedded Web Server

Overview
The configuration of the RTU transmission protocol has to be done once using the
embedded web server of the W@DE modules.
This can be done before or after using the RTU Configuration Software.

Communication Configuration
In the Modbus master Communication Configuration dialog you have to
configure the general parameters for the Modbus communication (e.g. reply timeout,
transmission speed, parity, etc.).
The topics are automatically configured and linked to the variables by the import of
the configuration file from the RTU Configuration Software.

38 EIO0000000547 11/2009
 RTU Application Example

Protocol Parameters
In the Protocol Parameters IEC 60870-5-101 dialog you have to
z configure the settings for transmission with time-tag (with/without and 3-Byte/7-
Byte time-tag)
z adjust the transmission priority of the classes

In the example the measurement values are transmitted as normalized values.

Therefore you have to configure the parameter of the measured value as shown
below.

EIO0000000547 11/2009 39
RTU Application Example

RTU Configuration Software Settings

Overview
For the RTU application example please define the data/properties listed below.
For information on how variable names are generated please refer to Variable Name
Creation (see page 18).

Device Configuration

Data Property Description/Comment

Description This is an example station. -
Version 0.0.001 version of the station configuration
PLC Select M340 from the drop- PLC, the module communicates
down list. with
Station prefix Tele1 This prefix will be used to generate
the variable names.
Prefix is used activate the check box -
Modbus slave 32 Modbus Serial Line slave address
address
Network address - Modbus TCP/IP address of the
[x.y.z.n] station (not used for this example)
Objects start 1000 start address of the ASDU data
address (%MW)
Quality bits start 100 start address of the quality data
address (%MW)
Structure name RTU name of the variable structure in
Unity Pro

40 EIO0000000547 11/2009
 RTU Application Example

Single Points

Data Property Description

Prefix SP For variable name generation this
prefix is merged with a 4-digits
incremental number.
Structure name SinglePoints name of the subelement of the
variable structure in Unity Pro
Number objects 25 number of variables of this type
Objects address 100 address of the first variable of this
type
Datatype BOOL Unity Pro datatype
Query cycle 1000ms choice of cycle defined in the
Common settings

The above properties correspond to 25 single points starting from the object address
100.
The variable names start with Tele1_SP0000_100_1000.
2 WORDs are required to transmit these 25 single points.

Single Commands

Data Property Description

Prefix SC For variable name generation this
prefix is merged with a 4-digits
incremental number.
Structure name SingleCommands name of the subelement of the
variable structure in Unity Pro
Number objects 15 number of variables of this type
Objects address 500 address of the first variable of this
type
Datatype BOOL Unity Pro datatype

The above properties correspond to 15 single commands starting from the object
address 500.
The variable names start with Tele1_SC0000_500_1002.
Only 1 WORD (%MW1002) is required to transmit these 15 single commands.

EIO0000000547 11/2009 41
RTU Application Example

Double Points

Data Property Description

Prefix DP For variable name generation this
prefix is merged with a 4-digits
incremental number.
Structure name DoublePoints name of the subelement of the
variable structure in Unity Pro
Number objects 10 number of variables of this type
Objects address 200 address of the first variable of this
type
Datatype DBOOL Unity Pro datatype
Query cycle 5000ms choice of cycle defined in the
Common settings

The above properties correspond to 10 double points starting from the object
address 200.
The variable names start with Tele1_DP0000_200_1003.
2 WORDs are required to transmit these 10 double points.

Double Commands

Data Property Description

Prefix DC For variable name generation this prefix is
merged with a 4-digits incremental number.
Structure name DoubleCommands name of the subelement of the variable structure
in Unity Pro
Number objects 5 number of variables of this type
Objects address 600 address of the first variable of this type
Datatype DBOOL Unity Pro datatype

The above properties correspond to 5 double commands starting from the object
address 600.
The variable names start with Tele1_DC0000_600_1005.
Only 1 WORD is required to transmit these 5 double commands.

42 EIO0000000547 11/2009
 RTU Application Example

Measured Values

Data Property Description

Prefix ME For variable name generation this prefix is
merged with a 4-digits incremental number.
Structure name MeasuredValues name of the subelement of the variable structure
in Unity Pro
Number objects 20 number of variables of this type
Objects address 300 address of the first variable of this type
Datatype INT Unity Pro datatype
Query cycle 1000ms choice of cycle defined in the Common settings
Variation method select variation of a variable to avoid multiple events
TIMEINTEGRAL with lowest values / value changes
from the drop-
down list
Variation value 100 value for the configured Variation method
(TIMEINTEGRAL: integrated value until the data
point variable gets transmitted.
Variation reference 32767 reference value to which the measured value will
be normalized

The above properties correspond to 20 measured values starting from the object
address 300.
Variation value was set to 100 and Variation reference was set to 32767.
The variable names start with Tele1_ME0000_300_1006.
20 WORDs are required to transmit these 20 measured values.

Set Points
Set Number objects to 0. So all other settings for Set points will be ignored.

EIO0000000547 11/2009 43
RTU Application Example

Integrated Totals

Data Property Description

Prefix IT For variable name generation this prefix is
merged with a 4-digits incremental number.
Structure name IntegratedTota name of the subelement of the variable structure
ls in Unity Pro
Number objects 3 number of variables of this type
Objects address 400 address of the first variable of this type
Datatype INT Unity Pro datatype
Query cycle 1000ms choice of cycle defined in the Common settings
Periodic event is activate this check If this check box is activated the integrated total
used box values are saved periodically. See Periodic
event.
Periodic event 5 min time span between 2 savings of the integrated
total values
This property is used only, if the Periodic event
is used check box is activated.
Reset value 1000000 Overflow value that must be exceeded, for the
integrated total value to be reset.

The above properties correspond to 3 integrated totals starting from the object
address 400.
Reset value was set to 1000000 and Periodic event was set to 5 min.
The variable names start with Tele1_IT0000_400_1026.
6 WORDs are required to transmit these 3 integrated totals.

44 EIO0000000547 11/2009
 RTU Application Example

Resulting Variables

The complete configuration includes 32 WORDs in the area of %MW1000 to

%MW1031.

Variable Type Name Object Address %MW Address

Single point1 Tele1_SP0000_100_1000 100 1000.0
Single point2 Tele1_SP0001_101_1000 101 1000.1
Single point3 Tele1_SP0002_102_1000 102 1000.2
Single point4 Tele1_SP0003_103_1000 103 1000.3
Single point5 Tele1_SP0004_104_1000 104 1000.4
Single point6 Tele1_SP0005_105_1000 105 1000.5
Single point7 Tele1_SP0006_106_1000 106 1000.6
Single point8 Tele1_SP0007_107_1000 107 1000.7
Single point9 Tele1_SP0008_108_1000 108 1000.8
Single point10 Tele1_SP0009_109_1000 109 1000.9
Single point11 Tele1_SP0010_110_1000 110 1000.10
Single point12 Tele1_SP0011_111_1000 111 1000.11
Single point13 Tele1_SP0012_112_1000 112 1000.12
Single point14 Tele1_SP0013_113_1000 113 1000.13
Single point15 Tele1_SP0014_114_1000 114 1000.14
Single point16 Tele1_SP0015_115_1000 115 1000.15
Single point17 Tele1_SP0016_116_1001 116 1001.0
Single point18 Tele1_SP0017_117_1001 117 1001.1
Single point19 Tele1_SP0018_118_1001 118 1001.2
Single point20 Tele1_SP0019_119_1001 119 1001.3
Single point21 Tele1_SP0020_120_1001 120 1001.4
Single point22 Tele1_SP0021_121_1001 121 1001.5
Single point23 Tele1_SP0022_122_1001 122 1001.6
Single point24 Tele1_SP0023_123_1001 123 1001.7
Single point25 Tele1_SP0024_124_1001 124 1001.8
Single command1 Tele1_SC0000_500_1002 500 1002.0
Single command2 Tele1_SC0001_501_1002 501 1002.1
Single command3 Tele1_SC0002_502_1002 502 1002.2
Single command4 Tele1_SC0003_503_1002 503 1002.3

EIO0000000547 11/2009 45
RTU Application Example

Variable Type Name Object Address %MW Address

Single command5 Tele1_SC0004_504_1002 504 1002.4
Single command6 Tele1_SC0005_505_1002 505 1002.5
Single command7 Tele1_SC0006_506_1002 506 1002.6
Single command8 Tele1_SC0007_507_1002 507 1002.7
Single command9 Tele1_SC0008_508_1002 508 1002.8
Single command10 Tele1_SC0009_509_1002 509 1002.9
Single command11 Tele1_SC0010_510_1002 510 1002.10
Single command12 Tele1_SC0011_511_1002 511 1002.11
Single command13 Tele1_SC0012_512_1002 512 1002.12
Single command14 Tele1_SC0013_513_1002 513 1002.13
Single command15 Tele1_SC0014_514_1002 514 1002.14
Double point1 Tele1_DP0000_200_1003 200 1003.0
Double point2 Tele1_DP0001_201_1003 201 1003.2
Double point3 Tele1_DP0002_202_1003 202 1003.4
Double point4 Tele1_DP0003_203_1003 203 1003.6
Double point5 Tele1_DP0004_204_1003 204 1003.8
Double point6 Tele1_DP0005_205_1003 205 1003.10
Double point7 Tele1_DP0006_206_1003 206 1003.12
Double point8 Tele1_DP0007_207_1003 207 1003.14
Double point9 Tele1_DP0008_208_1004 208 1004.0
Double point10 Tele1_DP0009_209_1004 209 1004.2
Double command1 Tele1_DC0000_600_1005 600 1005.0
Double command2 Tele1_DC0001_601_1005 601 1005.2
Double command3 Tele1_DC0002_602_1005 602 1005.4
Double command4 Tele1_DC0003_603_1005 603 1005.6
Double command5 Tele1_DC0004_604_1005 604 1005.8
Measured value1 Tele1_ME0000_300_1006 300 1006
Measured value2 Tele1_ME0001_301_1007 301 1007
Measured value3 Tele1_ME0002_302_1008 302 1008
Measured value4 Tele1_ME0003_303_1009 303 1009
Measured value5 Tele1_ME0004_304_1010 304 1010
Measured value6 Tele1_ME0005_305_1011 305 1011
Measured value7 Tele1_ME0006_306_1012 306 1012
Measured value8 Tele1_ME0007_307_1013 307 1013

46 EIO0000000547 11/2009
 RTU Application Example

Variable Type Name Object Address %MW Address

Measured value9 Tele1_ME0008_308_1014 308 1014
Measured value10 Tele1_ME0009_309_1015 309 1015
Measured value11 Tele1_ME0010_310_1016 310 1016
Measured value12 Tele1_ME0011_311_1017 311 1017
Measured value13 Tele1_ME0012_312_1018 312 1018
Measured value14 Tele1_ME0013_313_1019 313 1019
Measured value15 Tele1_ME0014_314_1020 314 1020
Measured value16 Tele1_ME0015_315_1021 315 1021
Measured value17 Tele1_ME0016_316_1022 316 1022
Measured value18 Tele1_ME0017_317_1023 317 1023
Measured value19 Tele1_ME0018_318_1024 318 1024
Measured value20 Tele1_ME0019_319_1025 319 1025
Integrated total1 Tele1_IT0000_400_1026 400 1026
Integrated total2 Tele1_IT0002_401_1028 401 1028
Integrated total3 Tele1_IT0003_402_1030 402 1030

EIO0000000547 11/2009 47
RTU Application Example

48 EIO0000000547 11/2009
 Index
EIO0000000547 11/2009

Index
B
AC
B G
browser general information, 10
station configuration, 22

H
C hardware requirements, 13
common settings, 23
configuration
device, 24 I
configuration with the embedded web server, import of data to Unity Pro, 32
38 information object address, 19
installation, 14
integrated totals
D properties, 28
device configuration, 24
DFBs, DDT, 15
double commands L
properties, 30 library
double points RTU, 15
properties, 26

M
E measured values
edit variables, 33 properties, 27
embedded web server
configuration, 38
example N
configuration tool settings, 40 name creation
resulting variables, 45 variables, 18

EIO0000000547 11/2009 49
Index

O V
object address, 19 variable name creation, 18
variables
edit, 33
P
properties
double commands, 30
double points, 26
integrated totals, 28
measured values, 27
set points, 31
single commands, 29
single points, 25

R
requirements
hardware, 13
software, 14
resulting variables (example), 45
RTU library, 15

S
set points
properties, 31
settings
common, 23
settings (example)
configuration tool, 40
single commands
properties, 29
single points
properties, 25
software requirements, 14
station configuration browser, 22

U
Unity Pro
import of data, 32
user interface, 20

50 EIO0000000547 11/2009