Unity Pro

33003101 12/2015

Unity Pro
Operating Modes
12/2015
33003101.17

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.
© 2015 Schneider Electric. All rights reserved.

2 33003101 12/2015
 Table of Contents

Safety Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
About the Book. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Part I General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Chapter 1 General Presentation of Unity Pro . . . . . . . . . . . . . . . . 35
Capabilities of Unity Pro . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Chapter 2 Programming Language Editors. . . . . . . . . . . . . . . . . . 43
Function Block Diagram FBD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Ladder Diagram (LD) Language . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
General Information about SFC Sequence Language . . . . . . . . . . . . 48
Instruction List IL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Structured Text ST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Chapter 3 Connecting a terminal to a PLC . . . . . . . . . . . . . . . . . . 55
Methodology for connecting from a PC to a PLC . . . . . . . . . . . . . . . . 55
Chapter 4 Global project management . . . . . . . . . . . . . . . . . . . . . 57
4.1 Access security management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Unity Pro access security management . . . . . . . . . . . . . . . . . . . . . . . 59
Security editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
User Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
User Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
User Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Recovery procedure with an error . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Access rights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
4.2 Project management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Access to Unity Pro Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Services in Offline Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Services in Online Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Allowed Online Modifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Connection / disconnection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Accessing a PLC via a Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Overview of Types of Connection Possible With Schneider PLCs . . . 107
Accessing communication parameters . . . . . . . . . . . . . . . . . . . . . . . . 111
Project comparison . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Conversion of Legacy Applications/Projects . . . . . . . . . . . . . . . . . . . . 115
33003101 12/2015 3
 Importing an LL984 Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Transferring the project between the terminal and the PLC. . . . . . . . . 125
Update of Upload Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Sending a command to the PLC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Project Backup Management for Modicon M340 . . . . . . . . . . . . . . . . . 132
Project backup for Premium. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Save/Restore Data Between a File and the PLC . . . . . . . . . . . . . . . . . 136
Compatibility Rules for Restore Using a *.DTX File . . . . . . . . . . . . . . . 140
Transferring current values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
Memory usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
Function Pack for Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
Memory Card Access for Modicon M340 . . . . . . . . . . . . . . . . . . . . . . . 155
FTP and Memory Card for Modicon M340. . . . . . . . . . . . . . . . . . . . . . 156
Project Management with DTMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
Chapter 5 Project browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
5.1 Introduction to the project browser. . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
Introduction to the project browser. . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
Structural view and functional view of the project . . . . . . . . . . . . . . . . 165
The Zoom In and Zoom Out commands . . . . . . . . . . . . . . . . . . . . . . . 167
The commands Contract all and Expand all . . . . . . . . . . . . . . . . . . . . 170
The Goto command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
User Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
Project Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
Application Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
Firmware Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
Section and Subroutine Protection. . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
Data Storage Protection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
Loss of Password. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
5.2 Introduction to the various directories of the project browser. . . . . . . . 193
Station Directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
Configuration Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
Derived data types (DDT) directory . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
Derived FB (DFB) types directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
Variables Directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
Motion Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
Communication Directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
Program Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206

4 33003101 12/2015
 Animation Tables Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
Operator Screens Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
Documentation Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
Conversion Report Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
5.3 Summaries of the utilities associated with the structure view and
function view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
Summary of the services associated with the structural view . . . . . . . 215
Chapter 6 Functional modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
6.1 Introduction to the functional view . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
Functional modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223
Station directory of the functional view . . . . . . . . . . . . . . . . . . . . . . . . 225
Functional Module Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
Functional Module Program Directory . . . . . . . . . . . . . . . . . . . . . . . . . 228
Functional Module Animation Tables Directory . . . . . . . . . . . . . . . . . . 229
Functional Module Operator Screens Directory . . . . . . . . . . . . . . . . . 230
Summary of the services associated with the functional view . . . . . . . 231
6.2 The functional modules and their associated utilities . . . . . . . . . . . . . 234
Properties of a functional module . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
Creating a functional module. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
Programming a functional module . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237
Protecting program elements of the functional module . . . . . . . . . . . . 239
Debugging a functional module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240
Detaching/Deleting a functional module . . . . . . . . . . . . . . . . . . . . . . . 241
Functional module export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
Functional module import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
Creating, Deleting, Locating, Dragging-and-Dropping an Animation
Table in a Functional Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247
Creating, Deleting, Locating and Dragging-and-Dropping an Operator
Screen in a Functional Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
Chapter 7 FDT Container. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
7.1 FDT Container . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254
Introduction to the Unity Pro FDT Container . . . . . . . . . . . . . . . . . . . . 255
FDT Container User Rights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256
7.2 DTM Hardware Catalog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257
Description of DTM Hardware Catalog . . . . . . . . . . . . . . . . . . . . . . . . 257
7.3 DTM Browser. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262
DTM Browser. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263
Ethernet Ready Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268
Ready, Built, Connected and Installed DTMs . . . . . . . . . . . . . . . . . . . 270

33003101 12/2015 5
 DTM Browser Contextual Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273
Field Bus Discovery Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281
Store Device Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284
Renaming DTMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285
Profibus DTMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287
7.4 DTM Properties Tabs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288
DTM Properties Dialog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288
Chapter 8 Type Library Manager . . . . . . . . . . . . . . . . . . . . . . . . . . 293
Libset (Set of Libraries) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294
Overview of the Type Library Manager . . . . . . . . . . . . . . . . . . . . . . . . 297
Type Library Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298
Description of the Type Library Manager . . . . . . . . . . . . . . . . . . . . . . . 301
Loading an object from the library into the project . . . . . . . . . . . . . . . 307
Transferring an object from the project into the library. . . . . . . . . . . . . 310
Creating a new library and family. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312
Creating an installable family . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314
Updating a family of a library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315
Consistency Check Assistant. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317
Library Version Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320
Using the type library of an older Unity Pro Version . . . . . . . . . . . . . . 324
Part II Data Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325
Chapter 9 Description of the Data Editor . . . . . . . . . . . . . . . . . . . 327
Data Editor Access. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328
Description of Data Editor tabs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330
Chapter 10 Creating derived data types (DDT) . . . . . . . . . . . . . . . . 333
Access to derived data types (DDT) . . . . . . . . . . . . . . . . . . . . . . . . . . 334
Creation of a derived data type (DDT) . . . . . . . . . . . . . . . . . . . . . . . . . 335
Administration of derived data types and their elements . . . . . . . . . . . 346
Creating Nested Derived Data Types . . . . . . . . . . . . . . . . . . . . . . . . . 348
Save Derived Data Types (DDT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355
Chapter 11 Creating data types of user function blocks (DFB) . . 357
Creation and Management of Data Types and Function Blocks (DFB) 357
Chapter 12 Managing of instances of data belonging to the family
of function blocks (EF) . . . . . . . . . . . . . . . . . . . . . . . . . 359
Creating / Deleting a variable instance of function blocks (EFB/DFB) . 360
Displaying function block variable instances in the editor . . . . . . . . . . 363
Changing the attribute for variable instances in a function block . . . . . 366

6 33003101 12/2015
 Chapter 13 Managing variable instances belonging to the
EDT/DDT/IODDT/Device DDT families . . . . . . . . . . . . . 369
Creation of EDT type variable instances . . . . . . . . . . . . . . . . . . . . . . . 370
Creation of variable DDT type instances . . . . . . . . . . . . . . . . . . . . . . . 375
Creating a type IODDT variable instance . . . . . . . . . . . . . . . . . . . . . . 382
Creating a Type Device DDT Variable instance . . . . . . . . . . . . . . . . . 385
Managing an IODDT, DDT or an Array type instance . . . . . . . . . . . . . 387
Creation of multiple variable instances . . . . . . . . . . . . . . . . . . . . . . . . 393
Displaying the variable instances in the editor . . . . . . . . . . . . . . . . . . 395
Changing attributes of variable instances . . . . . . . . . . . . . . . . . . . . . . 399
Creation of a Reference Type Instance . . . . . . . . . . . . . . . . . . . . . . . . 402
Chapter 14 General Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403
Configuring the Data Editor columns. . . . . . . . . . . . . . . . . . . . . . . . . . 404
Description of the Data Editor: Variable type selection . . . . . . . . . . . . 408
Filtering of Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 412
Exporting a subset of variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 416
Analyze DDT and DFB Data Types . . . . . . . . . . . . . . . . . . . . . . . . . . . 417
Purge of Unused Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 418
Local printing of data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 420
Save the context of the Data Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . 421
Part III Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . 423
Chapter 15 Presentation of the communication editors . . . . . . . . 425
Presentation of the communication editors of the project browser . . . 425
Chapter 16 Network Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . 427
Network Configuration Principle Using Unity Pro . . . . . . . . . . . . . . . . 428
Creating a Logic Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429
Configuring a Logic Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 431
Associating a Logic Network with Network Hardware . . . . . . . . . . . . . 432
Chapter 17 Configuration of X-Way Routing Premium Stations . . 435
Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 436
Configuration of Multi-Network Services . . . . . . . . . . . . . . . . . . . . . . . 437
Configuring an X-Way Router Module. . . . . . . . . . . . . . . . . . . . . . . . . 439
Examples of X-Way Routing Stations . . . . . . . . . . . . . . . . . . . . . . . . . 443
Examples of Partial Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 447

33003101 12/2015 7
 Part IV Programming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 451
Chapter 18 Accessing Tasks and Sections. . . . . . . . . . . . . . . . . . . 453
18.1 Access to Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 454
Create and Configuration of a Task . . . . . . . . . . . . . . . . . . . . . . . . . . . 455
Displaying and Modifying Task Properties . . . . . . . . . . . . . . . . . . . . . . 456
18.2 Accessing Sections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 457
Creating an FBD, LD, IL, or ST Section . . . . . . . . . . . . . . . . . . . . . . . . 458
Properties Dialog Box for FBD, LD, IL, or ST Sections . . . . . . . . . . . . 461
Creating SFC sections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 467
Properties Dialog Box for SFC Sections . . . . . . . . . . . . . . . . . . . . . . . 470
Creating action, transition and macro sections . . . . . . . . . . . . . . . . . . 477
Action, transition and macro sections properties dialog box . . . . . . . . 478
Create a Sub-Program Section (SR) . . . . . . . . . . . . . . . . . . . . . . . . . . 481
Property Dialog of the Sub-Program Sections . . . . . . . . . . . . . . . . . . . 483
Creating a Timer Event Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 486
Properties dialog box for Timer Event Sections . . . . . . . . . . . . . . . . . . 489
Create an I/O Event Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 493
Property Dialog of I/O Event Sections . . . . . . . . . . . . . . . . . . . . . . . . . 496
Opening a Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 500
Deleting sections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 501
Execution order of sections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 502
Creating LL984 Segments and Networks . . . . . . . . . . . . . . . . . . . . . . 503
Modifying LL984 Segment Properties . . . . . . . . . . . . . . . . . . . . . . . . . 508
Modifying LL984 Network Properties . . . . . . . . . . . . . . . . . . . . . . . . . . 510
Scheduling LL984 Segments and Network . . . . . . . . . . . . . . . . . . . . . 512
Deleting, Cutting, Copying and Pasting LL984 Segments and Network 513
Chapter 19 Unity Pro Software Options . . . . . . . . . . . . . . . . . . . . . 515
19.1 Project Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 516
General Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 517
General Project Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 519
Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 531
Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 534
Maintain Output Links on Disabled EF (EN=0) . . . . . . . . . . . . . . . . . . 542
Configuration Settings for Operator Screens . . . . . . . . . . . . . . . . . . . . 550

8 33003101 12/2015
 19.2 Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 554
General Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 555
General Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 557
Data and Languages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 559
Connection Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 561
The Operator Screens Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 563
Converters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 565
19.3 Customize Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 571
Customize Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 571
Chapter 20 Common Function for graphical language . . . . . . . . . 575
Using Bookmarks in Graphical Languages Sections. . . . . . . . . . . . . . 576
Display grid in a FBD/LD/SFC section. . . . . . . . . . . . . . . . . . . . . . . . . 581
Zoom in a FBD/LD/SFC section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 582
Tracking links in a FBD/LD/SFC section . . . . . . . . . . . . . . . . . . . . . . . 585
Print Current Section in a FBD/LD/SFC section . . . . . . . . . . . . . . . . . 586
Undo and redo changes in a FBD/LD section . . . . . . . . . . . . . . . . . . . 587
Using connectors in a FBD/LD section . . . . . . . . . . . . . . . . . . . . . . . . 588
Inspect windows in a FBD/LD section . . . . . . . . . . . . . . . . . . . . . . . . . 593
Tooltips for Variables in a FBD/LD/SFC Section . . . . . . . . . . . . . . . . . 597
Replace Variables in a FBD/LD Section . . . . . . . . . . . . . . . . . . . . . . . 599
Initialize search in a FBD/LD section . . . . . . . . . . . . . . . . . . . . . . . . . . 603
Initialize Animation Table in a FBD/LD section . . . . . . . . . . . . . . . . . . 604
Go to in a FBD/LD section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 605
Go to dialog box in a FBD/LD section . . . . . . . . . . . . . . . . . . . . . . . . . 607
Chapter 21 FBD Editor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 611
21.1 Creating a program with FBD programming language . . . . . . . . . . . . 612
Structure of an FBD program (function block language) . . . . . . . . . . . 613
Creating an FBD Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 615
Syntax and Semantics Check during programming . . . . . . . . . . . . . . 616
Navigating with the keyboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 617
Selecting objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 618
Deleting, cutting, copying, pasting and moving objects . . . . . . . . . . . . 621
Inserting Rows and Columns. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 625
Deleting Rows and Columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 626
Displaying the properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 627
Refining DFBs and subroutines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 628

33003101 12/2015 9
 21.2 Editing FFBs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 630
General information about calling an FFB . . . . . . . . . . . . . . . . . . . . . . 631
Calling an FFB via the FFB Input Assistant. . . . . . . . . . . . . . . . . . . . . 633
Calling an FFB via the data selection. . . . . . . . . . . . . . . . . . . . . . . . . . 637
Assign actual parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 642
Using Public Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 654
Expanding Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 656
Negating FFB Pins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 657
EN and ENO Show and Hide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 658
Modifying the execution order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 659
Replacing an FFB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 663
Properties dialog box for elementary functions, procedures and sub-
routine blocks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 665
Properties dialog box for elementary and derived function blocks (FBs) 667
21.3 Returning from a Subroutine or DFB . . . . . . . . . . . . . . . . . . . . . . . . . . 670
Returning from a Subroutine or DFB . . . . . . . . . . . . . . . . . . . . . . . . . . 671
Return object properties dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . 673
21.4 Calling a Subroutine. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 674
Calling a subroutine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 674
21.5 Jumps within the Current Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . 678
Jump within the current section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 679
Jump object properties dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . 683
21.6 Definition of the Jump Target (Jump Labels) . . . . . . . . . . . . . . . . . . . . 685
Definitions of Jump Labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 686
Jump label objects properties dialog box . . . . . . . . . . . . . . . . . . . . . . . 688
21.7 Editing Links. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 690
Links. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 691
Placing a Link. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 693
Editing Links. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 696
21.8 Entering Comments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 702
Entering comments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 702
21.9 Online functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 704
Online functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 704
21.10 FBD Reference Data Type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 705
Reference Data Type in FBD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 705
21.11 Export/Import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 706
Export/Import FBD Sections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 706

10 33003101 12/2015
 21.12 Customize FBD Editor Colors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 707
Customize FBD Editor Colors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 707
Chapter 22 LD Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 709
22.1 Creating a program with LD programming language. . . . . . . . . . . . . . 710
Structure of an LD program (ladder diagram) . . . . . . . . . . . . . . . . . . . 711
Creating an LD program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 713
Syntax and Semantics Check during programming . . . . . . . . . . . . . . 717
View for variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 719
Navigating with the Keyboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 724
Selecting objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 727
Deleting, cutting, copying, pasting and moving objects . . . . . . . . . . . . 730
Displaying the properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 734
Refining DFBs and subroutines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 735
Inserting and Deleting Rows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 737
22.2 Editing Contacts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 738
Select contacts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 739
Placing contacts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 741
Property dialog box for contacts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 745
22.3 Editing Coils. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 748
Selection of coils . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 749
Placing coils. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 752
Property dialog box for coils . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 758
22.4 Editing compare blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 761
Placing compare blocks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 762
Compare block properties dialog box . . . . . . . . . . . . . . . . . . . . . . . . . 766
22.5 Editing operation blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 768
Placing Operate Blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 769
Operate block properties dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . 774
22.6 Editing FFBs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 776
General information on calling an FFB . . . . . . . . . . . . . . . . . . . . . . . . 777
Calling an FFB via the FFB input assistant . . . . . . . . . . . . . . . . . . . . . 779
Calling an FFB via the data selection . . . . . . . . . . . . . . . . . . . . . . . . . 783
Connection of FFBs to the Left Power Rail . . . . . . . . . . . . . . . . . . . . . 788
Assigning Actual Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 789
Using Public Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 801
Expanding Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 803

33003101 12/2015 11
 Negating FFB Pins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 805
EN and ENO Show and Hide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 806
Properties dialog box for elementary functions, procedures and sub-
routine blocks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 807
Properties dialog box for elementary and derived function blocks (FBs) 809
22.7 Returning from a Subroutine or DFB . . . . . . . . . . . . . . . . . . . . . . . . . . 811
Returning from a subroutine or DFB . . . . . . . . . . . . . . . . . . . . . . . . . . 812
Return object properties dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . 814
22.8 Jumps within the Current Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . 815
Jumps within the current section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 816
Jump object properties dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . 819
22.9 Definition of the Jump Target (Jump Labels) . . . . . . . . . . . . . . . . . . . . 821
Definitions of jump targets (jump labels) . . . . . . . . . . . . . . . . . . . . . . . 822
Jump label properties dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 825
22.10 Editing Links. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 827
Select links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 828
Combining Links. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 830
Placing links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 832
Editing links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 847
22.11 Entering Comments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 853
Entering comments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 853
22.12 Online functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 855
Online Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 855
22.13 LD Reference Data Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 856
Reference Data Type in LD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 856
22.14 Export/Import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 857
Export/Import LD Sections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 857
22.15 Customize LD Editor Colors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 858
Customize LD Editor Colors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 858
Chapter 23 SFC Editor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 861
23.1 Creating a program with the SFC programming language. . . . . . . . . . 862
Structure of an SFC Program (Sequential Function Chart) . . . . . . . . . 863
Creating an SFC Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 866
Syntax and Semantics Check during Programming. . . . . . . . . . . . . . . 867
Navigating with the keyboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 869
Selecting Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 870
Undo and Redo Changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 873
Deleting, cutting, copying, pasting and moving objects . . . . . . . . . . . . 874

12 33003101 12/2015
 Inserting Rows and Columns. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 880
Deleting Rows and Columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 882
Displaying the object properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 884
Initialize Search . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 885
Initialize Animation Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 886
Refining steps, macro steps and transitions . . . . . . . . . . . . . . . . . . . . 887
Go to . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 889
Go to dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 891
List and display jumps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 895
Go to Step . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 896
23.2 General Information about Steps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 897
Selecting steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 898
Placing steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 900
23.3 Editing "normal" steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 901
Defining the properties of steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 902
Steps properties dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 909
23.4 Editing macro steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 915
Defining the properties of macro steps . . . . . . . . . . . . . . . . . . . . . . . . 916
Macro Steps Properties Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . 923
23.5 Editing input steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 926
Defining the properties of InSteps . . . . . . . . . . . . . . . . . . . . . . . . . . . . 927
InSteps properties dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 929
23.6 Editing Output Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 933
Defining the properties of OutSteps . . . . . . . . . . . . . . . . . . . . . . . . . . 934
OutStep properties dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 936
23.7 Editing actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 939
Assigning actions to a step . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 940
Display modes for actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 949
23.8 Editing Transitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 951
Placing transitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 952
Defining transition properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 954
Properties dialog box for transitions . . . . . . . . . . . . . . . . . . . . . . . . . . 960
23.9 Editing Jumps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 963
Placing jumps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 964
Defining jump properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 966
Jump properties dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 968

33003101 12/2015 13
 23.10 Editing Branches and Joints. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 970
Selecting Branches and Joints. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 971
Placing branches and joints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 973
Modifying the Properties of Branches and Joints. . . . . . . . . . . . . . . . . 974
Branches properties dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 977
Joints properties dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 978
23.11 Inserting Alternative Strings and Simultaneous Strings . . . . . . . . . . . . 979
Selecting Alternative Sequences and Parallel Sequences . . . . . . . . . 980
Placing alternative sequences and parallel sequences . . . . . . . . . . . . 981
23.12 Inserting Step-Transitions and Transition-Step-Sequences. . . . . . . . . 984
Selecting Step-Transition and Transition-Step Sequences . . . . . . . . . 985
Placing step-transition and transition-step sequences. . . . . . . . . . . . . 986
23.13 Editing Links. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 989
Links. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 990
Placing a Link. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 991
Editing links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 995
23.14 Entering Comments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1000
Entering comments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1000
23.15 Online functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1002
Online functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1002
23.16 Export/Import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1003
Export/Import SFC Sections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1003
23.17 Customize SFC Editor Colors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1004
Customize SFC Editor Colors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1004
Chapter 24 Common Function for Textual Language . . . . . . . . . . 1007
Selecting Text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1008
Deleting, cutting, copying, pasting and moving text . . . . . . . . . . . . . . . 1010
Undoing and redoing changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1012
Match case. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1013
Zoom (font size) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1014
Using Bookmarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1015
Go to . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1017
Go to dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1019
Searching text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1022
Searching and replacing text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1024
Call a subroutine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1026
Refine DFBs and subroutines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1028
Inspect windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1030

14 33003101 12/2015
 Enter comments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1034
Printing the Current Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1036
Initialize search . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1037
Initialize Animation table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1038
Displaying the section properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1039
Fullscreen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1040
Chapter 25 IL Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1041
Structure of an IL program. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1042
Creating an IL Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1044
Syntax and Semantics Check during Programming . . . . . . . . . . . . . . 1045
Navigating with the keyboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1049
Data input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1050
Calling an FFB. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1057
Using Public Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1068
Online functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1070
Reference Data Type in IL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1071
Export/Import IL Sections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1072
Chapter 26 ST Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1073
Structure of an ST program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1074
Creating an ST Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1076
Syntax and Semantics Check during Programming . . . . . . . . . . . . . . 1077
Navigating with the keyboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1081
Data input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1082
Calling an FFB. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1088
Using public variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1099
Calling a statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1101
Online functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1107
Reference Data Type in ST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1108
Export/Import IL Sections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1109
Chapter 27 LL984 Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1111
27.1 Creating a Program with LL984 Programming Language . . . . . . . . . . 1112
Project Settings for LL984 Programs. . . . . . . . . . . . . . . . . . . . . . . . . . 1113
Structure of an LL984 Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1114
Creating an LL984 Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1117
Syntax and Semantics Check During Programming . . . . . . . . . . . . . . 1120
Network Display. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1123
Navigating with the Keyboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1124

33003101 12/2015 15
 Selecting Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1126
Deleting, Cutting, Copying, Pasting and Moving Objects. . . . . . . . . . . 1128
Displaying the Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1131
Inserting and Deleting Rows/Columns . . . . . . . . . . . . . . . . . . . . . . . . . 1132
27.2 Editing Contacts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1134
Selecting Contacts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1135
Placing Contacts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1137
Properties Dialog for Contacts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1141
27.3 Editing Coils . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1144
Selecting Coils . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1145
Placing Coils . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1147
Property Dialog for Coils . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1150
27.4 Editing Function Blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1152
Editing Function Blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1153
Using Mnemonics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1156
27.5 Editing Links. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1157
Selecting Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1158
Combining Links. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1159
Placing Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1160
Editing Links. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1162
27.6 Editing Equation Network Blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1163
Editing Equation Network Blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1164
Editing the ST Assignment Expression . . . . . . . . . . . . . . . . . . . . . . . . 1167
27.7 Assigning Variables to LL984 Objects . . . . . . . . . . . . . . . . . . . . . . . . . 1171
Assigning Variables to LL984 Objects . . . . . . . . . . . . . . . . . . . . . . . . . 1171
27.8 Calling Subroutines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1175
Calling Subroutines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1175
27.9 Entering Comments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1177
Entering Comments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1177
27.10 Customize LL984 Editor Colors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1179
Customize LL984 Editor Colors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1179
Chapter 28 Programming Languages Data Selection Dialog Box 1181
Variable selection dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1182
FFB Selection Dialog box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1184
FFB Type Selection Dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1187

16 33003101 12/2015
 Data selection dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1189
Function Input Assistant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1194
Data Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1197
Generate variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1199
Chapter 29 I/O Objects tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1201
Introduction to the I/O Object Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1202
I/O Objects Tab for a Processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1204
I/O Objects Tab for a Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1207
Details of Areas in the I/O Objects Tab . . . . . . . . . . . . . . . . . . . . . . . . 1209
I/O Objects Tab for a Bus Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1214
How to Use the I/O Objects Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1215
Chapter 30 Memory Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1219
Memory Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1219
Chapter 31 Type Library Browser. . . . . . . . . . . . . . . . . . . . . . . . . . . 1225
Access to the Type Library Browser . . . . . . . . . . . . . . . . . . . . . . . . . . 1226
Description of the Type Library Browser . . . . . . . . . . . . . . . . . . . . . . . 1228
Configuration of Columns of the Type Library Browser . . . . . . . . . . . . 1231
Drag & Drop of FFBs in a program section . . . . . . . . . . . . . . . . . . . . . 1233
Chapter 32 Search/Replace Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . 1235
Overview of the Search / Replace tool . . . . . . . . . . . . . . . . . . . . . . . . 1236
General Features for Search/Replace. . . . . . . . . . . . . . . . . . . . . . . . . 1238
Searching for Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1239
Replacing Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1240
Search Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1241
Data Search Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1242
Cross-References (Search Results) . . . . . . . . . . . . . . . . . . . . . . . . . . 1244
Cross-References (Replace) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1247
Tracing Variables / Addresses. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1249
Chapter 33 User's Function Blocks . . . . . . . . . . . . . . . . . . . . . . . . . 1251
33.1 DFB Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1252
DFB Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1253
Creating a DFB Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1255
Configuration of a DFB Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1256
Programming a DFB type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1259
Deleting a DFB type element. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1262
Archiving a DFB Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1263

33003101 12/2015 17
 How to protect a DFB type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1264
Deleting a DFB Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1266
How to access the attributes of a DFB type . . . . . . . . . . . . . . . . . . . . . 1267
Authorized DFB Type Modifications. . . . . . . . . . . . . . . . . . . . . . . . . . . 1269
33.2 DFB Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1272
DFB Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1273
Creating a DFB Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1274
Creating several DFB Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1276
Deleting a DFB instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1277
Operations on DFB Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1278
Modifying the Attributes of a DFB Instance . . . . . . . . . . . . . . . . . . . . . 1280
Authorized DFB Instance Modifications . . . . . . . . . . . . . . . . . . . . . . . . 1283
33.3 How to Create Nested DFBs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1284
How to Create Nested DFBs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1284
Part V Project Configuration . . . . . . . . . . . . . . . . . . . . . . 1285
Chapter 34 Introduction to the configuration . . . . . . . . . . . . . . . . . 1287
Proposed Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1288
Services offered in offline mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1292
Services Offered In Online Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1293
Access to project configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1295
Chapter 35 Bus Editors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1299
35.1 Rack configuration on local bus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1300
Organization of the Racks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1301
How to configure the racks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1306
35.2 Configuration of the power supply modules . . . . . . . . . . . . . . . . . . . . . 1308
How to configure the power supply modules . . . . . . . . . . . . . . . . . . . . 1308
35.3 Configuration of the processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1311
Choice and replacement of the processor . . . . . . . . . . . . . . . . . . . . . . 1311
35.4 Configuration of the modules in the PLC station . . . . . . . . . . . . . . . . . 1314
How to configure the modules in the PLC station . . . . . . . . . . . . . . . . 1314
35.5 Configuration of devices on the field bus . . . . . . . . . . . . . . . . . . . . . . . 1319
Configuration of the CANopen Slaves for Modicon M340 . . . . . . . . . . 1320
How to access and create a Fipio field bus . . . . . . . . . . . . . . . . . . . . . 1324
Creating and Accessing RIO\DIO Field Buses. . . . . . . . . . . . . . . . . . . 1328
How to configure devices on the RIO/DIO bus . . . . . . . . . . . . . . . . . . 1334
35.6 Consumption management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1340
Power consumption budget . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1341
Budget on the number of application-specific channels. . . . . . . . . . . . 1344

18 33003101 12/2015
 35.7 Bus editors in online mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1347
Online Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1347
Chapter 36 Modules editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1351
36.1 Configuration of Modicon M340 processors . . . . . . . . . . . . . . . . . . . . 1352
Configuration of Modicon M340 Processors . . . . . . . . . . . . . . . . . . . . 1352
36.2 Configuration of Premium processors . . . . . . . . . . . . . . . . . . . . . . . . . 1363
Configuration of Premium\Atrium processors . . . . . . . . . . . . . . . . . . . 1364
Access to PCMCIA memory cards of Premium processors . . . . . . . . 1370
Access to control loop configuration for Premium processors. . . . . . . 1372
36.3 Configuration of the Quantum processors . . . . . . . . . . . . . . . . . . . . . . 1373
Configuration of Quantum processors . . . . . . . . . . . . . . . . . . . . . . . . . 1374
Configuration of Modbus ports on Quantum . . . . . . . . . . . . . . . . . . . . 1380
36.4 Configuration of the input\output modules for a Premium\Atrium,
Quantum or Modicon M340 station . . . . . . . . . . . . . . . . . . . . . . . . . . . 1383
Access to the Modicon, Premium or Atrium I/O module configuration
editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1384
Access the Quantum input/output module configuration editor . . . . . . 1386
Chapter 37 General functionalities of the editor . . . . . . . . . . . . . . . 1389
Analysis of the configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1390
Export\Import of the configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1391
Printing the configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1392
Part VI Debugging and adjustment . . . . . . . . . . . . . . . . . . 1393
Chapter 38 Debugging the program. . . . . . . . . . . . . . . . . . . . . . . . . 1395
38.1 Safety precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1396
Modification in RUN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1397
Switch to STOP of a PLC in Debug mode. . . . . . . . . . . . . . . . . . . . . . 1398
Setting a task to STOP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1399
Task deactivation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1400
Deactivation of Inputs/Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1401
Use of the Step by Step mode and Breakpoint . . . . . . . . . . . . . . . . . . 1402
Unwanted disconnection in Debug mode for Premium . . . . . . . . . . . . 1403
Debug Screen Via a Fipway, Fipio or Uni-Telway Network with a
PCMCIA Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1404
Behavior of Forced Variables between Modsoft/NxT/Concept and
Unity Pro . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1405
38.2 Program Animation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1406
Introduction to animation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1407
Section in textual languages (Structured Text or Instruction List) . . . . 1410
Section in a Ladder Diagram language . . . . . . . . . . . . . . . . . . . . . . . . 1411

33003101 12/2015 19
 Section in Function Block Diagram (FBD) language . . . . . . . . . . . . . . 1414
Section in Sequential Function Chart language (SFC) . . . . . . . . . . . . 1416
Display of Prepositioned steps, after an on-line modification. . . . . . . . 1418
DFB instances (user function blocks). . . . . . . . . . . . . . . . . . . . . . . . . . 1419
Representation of forced variables . . . . . . . . . . . . . . . . . . . . . . . . . . . 1421
38.3 Debugging in Ladder Language. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1422
Inserting a breakpoint in Ladder Diagram language (LD) . . . . . . . . . . 1423
Step by step execution mode in Ladder Diagram language (LD) . . . . 1425
Inserting a Watchpoint in Ladder Diagram Language . . . . . . . . . . . . . 1428
38.4 Debugging in Textual Languages (Structured Text, Instruction List) . . 1431
Insertion of a breakpoint in textual languages (Structured Text or
Instruction List). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1432
Step by step execution mode in textual languages (Structured Text or
Instruction List). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1434
Insertion of a Watchpoint in Textual Languages (Structured Text or
Instruction List). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1437
38.5 Debugging in Function Block Diagram (FBD) Language . . . . . . . . . . . 1440
Inserting a breakpoint in Function Block Diagram language . . . . . . . . 1441
Step by step execution mode in Function Block Diagram language
(FBD) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1444
Inserting a watchpoint in Function Block Diagram language (FBD). . . 1447
38.6 Debugging User Function Block (DFB) Instances . . . . . . . . . . . . . . . . 1450
Inserting a breakpoint in a DFB instance (user function block) . . . . . . 1451
Step by step execution mode in a DFB instance (user function block) 1453
Inserting a watchpoint in a user function block (DFB) . . . . . . . . . . . . . 1454
38.7 Debugging in Sequential Function Chart Language (SFC) . . . . . . . . . 1455
Inserting a breakpoint in Sequential Function Chart language (SFC) . 1456
Step by step execution mode in Sequential Function Chart language
(SFC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1459
Inserting a watchpoint in Sequential Function Chart language . . . . . . 1463
38.8 Information on Debugging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1464
Tracing task execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1465
Task states during debugging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1467
Disconnection during the debug phase . . . . . . . . . . . . . . . . . . . . . . . . 1468
Operation of the alarm relay in Debug mode . . . . . . . . . . . . . . . . . . . . 1469

20 33003101 12/2015
 38.9 PLC debug screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1470
Overview of the CPU debugging screen . . . . . . . . . . . . . . . . . . . . . . . 1471
Description of the Task tab: Task checking field . . . . . . . . . . . . . . . . . 1473
Description of the Task tab: Operating mode field . . . . . . . . . . . . . . . 1475
Description of tab: Realtime Clock . . . . . . . . . . . . . . . . . . . . . . . . . . . 1477
Description of the Tab: Information . . . . . . . . . . . . . . . . . . . . . . . . . . . 1478
Chapter 39 Viewing and adjusting variables . . . . . . . . . . . . . . . . . . 1483
39.1 Introduction to variable animation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1484
Displaying variables in debug mode . . . . . . . . . . . . . . . . . . . . . . . . . . 1484
39.2 Variable Display Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1485
Introduction to the Variable Output Window . . . . . . . . . . . . . . . . . . . . 1485
39.3 Variable Display Boxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1488
Introduction to variable display boxes . . . . . . . . . . . . . . . . . . . . . . . . . 1488
39.4 Animation Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1491
Permanent and Temporary Animation Tables . . . . . . . . . . . . . . . . . . . 1492
Introduction to Animation Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1494
Managing Animation Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1496
Multiple Modifications of Animation Table Variables . . . . . . . . . . . . . . 1500
Animation Table Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1501
Basic functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1502
Animation of Strings in the Animation Table . . . . . . . . . . . . . . . . . . . . 1506
Modification Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1507
Force Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1512
Multiple modification and forcing of Boolean variables . . . . . . . . . . . . 1518
Animation Table of Forced Bits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1521
39.5 Instruction Editor (LL984) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1522
Instruction Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1522
39.6 Modifying values: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1525
Modifying values: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1525
Chapter 40 Machine-Process Simulator . . . . . . . . . . . . . . . . . . . . . 1529
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1529
Part VII Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1531
Chapter 41 Introduction to diagnostics tools . . . . . . . . . . . . . . . . . 1533
Diagnostics with Unity Pro . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1533
Chapter 42 Diagnostics screens. . . . . . . . . . . . . . . . . . . . . . . . . . . . 1535
42.1 Module and processor diagnostics screens . . . . . . . . . . . . . . . . . . . . 1536
Viewing fault diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1537
Lists of fault diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1539

33003101 12/2015 21
 Chapter 43 Diagnostics Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1541
Reminder of the Diagnostics Associated with the Viewer . . . . . . . . . . 1542
Operation of the diagnostics in Unity Pro . . . . . . . . . . . . . . . . . . . . . . 1544
Description of the Diagnostics Viewer . . . . . . . . . . . . . . . . . . . . . . . . . 1545
How to find causes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1548
Configuring the display. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1550
Managing error messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1552
Diagnostics Viewer Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1554
DiagViewer Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1556
Archiving error messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1558
Chapter 44 System diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1561
System diagnostic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1561
Chapter 45 Project diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1565
How to Create a User Diagnostic DFB. . . . . . . . . . . . . . . . . . . . . . . . . 1566
Project diagnostic. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1568
Part VIII Operator screen . . . . . . . . . . . . . . . . . . . . . . . . . . . 1571
Chapter 46 General information . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1573
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1574
Creation of Runtime Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1575
Chapter 47 First steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1577
47.1 Working principles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1578
How to access the operator screens . . . . . . . . . . . . . . . . . . . . . . . . . . 1578
47.2 Menus and tools in the runtime screen editor . . . . . . . . . . . . . . . . . . . 1580
Menus in the operator screen editor . . . . . . . . . . . . . . . . . . . . . . . . . . 1581
Edit toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1584
47.3 Configuring options from the runtime screen editor . . . . . . . . . . . . . . . 1587
General configuration of operator screens. . . . . . . . . . . . . . . . . . . . . . 1587
Chapter 48 Editing runtime screens . . . . . . . . . . . . . . . . . . . . . . . . 1589
48.1 Editing screens from the browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1590
Editing operator screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1591
Operator screen editor functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1593
Screen Family Editor Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1596
Operator screen properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1598
Properties of Operator Screen Families. . . . . . . . . . . . . . . . . . . . . . . . 1601

22 33003101 12/2015
 48.2 Creating an object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1602
Introduction of a graphic screen object . . . . . . . . . . . . . . . . . . . . . . . . 1603
How to create standard objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1604
How to insert an image in a screen . . . . . . . . . . . . . . . . . . . . . . . . . . . 1606
How to create driving objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1608
Operation of the driving objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1610
48.3 Default Properties screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1614
Default Properties screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1614
48.4 Modification of an object’s attributes . . . . . . . . . . . . . . . . . . . . . . . . . . 1616
How to access an object’s attributes . . . . . . . . . . . . . . . . . . . . . . . . . . 1617
Design tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1618
Extended colors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1620
Text tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1621
Animation Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1623
Animation type tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1625
Trend diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1628
Bar chart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1630
Screen browse tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1632
Control tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1634
Image Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1636
Explicit Exchanges Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1638
Information on the objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1640
The data selection tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1642
48.5 Manipulation of objects in runtime screens . . . . . . . . . . . . . . . . . . . . . 1645
How to select graphic objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1646
How to move and resize objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1648
How to delete and copy objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1650
How to position objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1652
How to create compound objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1654
48.6 Managing the runtime screens messages editor . . . . . . . . . . . . . . . . . 1655
Operator screens messages editor . . . . . . . . . . . . . . . . . . . . . . . . . . . 1656
How to manage messages linked to operator screens . . . . . . . . . . . . 1658
Find dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1660
Replace dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1662
Message Renumbering Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . 1663
Message editing and import/export function . . . . . . . . . . . . . . . . . . . . 1664

33003101 12/2015 23
 Chapter 49 Runtime screens in online mode . . . . . . . . . . . . . . . . . 1667
Basic functions in online mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1668
How to select an animated object . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1669
How to use command objects to modify the variables associated with
objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1670
How to view the variables associated with graphic objects . . . . . . . . . 1671
How to modify the variables associated with objects from an animation
table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1672
How to search for cross-references . . . . . . . . . . . . . . . . . . . . . . . . . . . 1673
How to manage the display of operator screens . . . . . . . . . . . . . . . . . 1674
How to modify screen control. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1676
How to obtain information on objects when in connected mode . . . . . 1677
Chapter 50 Runtime screens objects library. . . . . . . . . . . . . . . . . . 1679
50.1 Managing library objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1680
The Objects Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1681
How to manage the list of graphic items in the library . . . . . . . . . . . . . 1682
Properties of the object library and its elements . . . . . . . . . . . . . . . . . 1685
Handling the Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1689
Dereferencing in Operator Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . 1691
Part IX Documentation, Import/export . . . . . . . . . . . . . . . 1693
Chapter 51 Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1695
Creating Project Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1696
Documentation Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1697
Topics in Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1700
Creating Project Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1707
Print Preview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1709
Page Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1711
Print . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1713
Printout Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1715
Chapter 52 Import / Export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1719
52.1 General information on the Import/Export function . . . . . . . . . . . . . . . 1720
General information on import/export. . . . . . . . . . . . . . . . . . . . . . . . . . 1721
Import / Export Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1722
Type of dialog box for the export function . . . . . . . . . . . . . . . . . . . . . . 1723
Type of dialog boxes for the import function . . . . . . . . . . . . . . . . . . . . 1726
Managing Conflicts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1728

24 33003101 12/2015
 52.2 Importing/Exporting the various elements of Unity Pro . . . . . . . . . . . 1730
Export of the input/output configuration . . . . . . . . . . . . . . . . . . . . . . . . 1731
Import of the input/output configuration . . . . . . . . . . . . . . . . . . . . . . . . 1732
Exporting the program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1733
Program Import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1735
Exporting DFB types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1737
Importing DFB types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1738
Exporting DDTs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1739
Importing DDTs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1740
Exporting Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1741
Importing Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1744
Exporting the communication network configuration . . . . . . . . . . . . . . 1745
Importing the configuration of a communication network . . . . . . . . . . 1746
Exporting operator screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1747
Importing operator screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1749
Exporting animation tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1750
Importing animation tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1751
Exporting a functional module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1752
Importing a functional module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1754
Exporting a global project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1755
Importing a global project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1757
Exporting/Importing LL984 Segments/Networks . . . . . . . . . . . . . . . . . 1759
52.3 Wizard for importing the various elements of Unity Pro . . . . . . . . . . . 1761
Using the assistant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1762
Variables tab of the wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1766
DFB and DDT Tabs of the Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1768
SR, Sections, Events and Macro steps tabs of the wizard . . . . . . . . . 1770
Wizard animation tables tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1771
Wizard functional module tabs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1772
Correspondence file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1774
Part X Conversion Wizard . . . . . . . . . . . . . . . . . . . . . . . . . 1775
Chapter 53 Conversion Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1777
53.1 General Description of the Conversion Wizard . . . . . . . . . . . . . . . . . . 1778
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1779
Access to Conversion Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1781
General Representation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1784
Conversion and Result . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1786

33003101 12/2015 25
 53.2 Structure Tab of the Conversion Wizard . . . . . . . . . . . . . . . . . . . . . . . 1787
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1788
Selecting Application Parts to be Converted . . . . . . . . . . . . . . . . . . . . 1790
53.3 I/O Remapping Tab of the Conversion Wizard . . . . . . . . . . . . . . . . . . 1792
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1793
Remapping Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1796
Remapping Channels, Groups of Channels or Specific I/O Types . . . 1799
Clustering and Remapping of Memory Variables. . . . . . . . . . . . . . . . . 1801
Memory Area Tabs of the Conversion Wizard . . . . . . . . . . . . . . . . . . . 1803
Concurrent Editing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1805
Exclude, Communication -1, Type Restriction . . . . . . . . . . . . . . . . . . . 1808
53.4 CPU Configuration Tab of the Conversion Wizard. . . . . . . . . . . . . . . . 1813
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1813
Appendices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1815
Appendix A Hyperlinks in Unity Pro . . . . . . . . . . . . . . . . . . . . . . . . . 1817
A.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1818
Introduction to Hyperlinks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1819
Representation and opening of a hyperlink . . . . . . . . . . . . . . . . . . . . . 1822
A.2 Principles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1823
Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1824
Overview of operate-modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1825
1-step mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1826
2-step mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1827
Description of the Hyperlink Comment Window. . . . . . . . . . . . . . . . . . 1829
Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1832
List of barred characters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1833
A.3 Hyperlinks in the project browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1834
Creating a hyperlink in the project browser . . . . . . . . . . . . . . . . . . . . . 1835
Editing the properties of a hyperlink in the project browser . . . . . . . . . 1837
Opening a hyperlink from the project browser . . . . . . . . . . . . . . . . . . . 1839
Deleting a hyperlink in the project browser . . . . . . . . . . . . . . . . . . . . . 1840
A.4 Hyperlink in the data editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1841
Creating a hyperlink in the data editor . . . . . . . . . . . . . . . . . . . . . . . . . 1842
Editing a hyperlink in the data editor . . . . . . . . . . . . . . . . . . . . . . . . . . 1844
Selecting a hyperlink in the data editor . . . . . . . . . . . . . . . . . . . . . . . . 1846
Deleting a hyperlink in the data editor . . . . . . . . . . . . . . . . . . . . . . . . . 1847

26 33003101 12/2015
 A.5 Hyperlinks in the DFB type attributes . . . . . . . . . . . . . . . . . . . . . . . . . 1849
Creating a Hyperlink from DFB Type Attributes . . . . . . . . . . . . . . . . . 1850
Modifying a Hyperlink from DFB Type Attributes. . . . . . . . . . . . . . . . . 1853
Selecting a Hyperlink from DFB Type Attributes . . . . . . . . . . . . . . . . . 1855
Deleting a Hyperlink from DFB Type Attributes . . . . . . . . . . . . . . . . . . 1857
A.6 Hyperlinks in animation tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1860
Creating a hyperlink in an animation table . . . . . . . . . . . . . . . . . . . . . 1861
Editing a hyperlink from an animation table. . . . . . . . . . . . . . . . . . . . . 1863
Selecting a hyperlink from an animation table . . . . . . . . . . . . . . . . . . . 1865
Deleting a hyperlink from an animation table . . . . . . . . . . . . . . . . . . . 1866
A.7 Hyperlinks in runtime screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1867
Creating a hyperlink from operator screens . . . . . . . . . . . . . . . . . . . . 1868
Editing a hyperlink in the operator screens . . . . . . . . . . . . . . . . . . . . . 1870
Selecting a hyperlink in an operator screen . . . . . . . . . . . . . . . . . . . . 1872
Deleting a hyperlink in an operator screen . . . . . . . . . . . . . . . . . . . . . 1873
A.8 Hyperlinks in the documentation folder . . . . . . . . . . . . . . . . . . . . . . . . 1874
Creating a hyperlink in the general information of the project folder . 1875
Editing a hyperlink in the documentation folder . . . . . . . . . . . . . . . . . . 1877
Deleting a hyperlink in the documentation folder. . . . . . . . . . . . . . . . . 1879
A.9 Hyperlinks and drag-and-drop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1881
Drag/drop. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1881
Appendix B User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1885
Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1886
Anchored window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1889
Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1892
Menu commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1895
Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1898
Output windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1903
Status bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1905
Directory Structures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1907
Using the Mouse . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1909
Using the Keyboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1910
Data selection boxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1911
Dialog boxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1913
Appendix C Keyboard Shortcuts . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1917
C.1 General Keyboard Shortcuts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1918
Bus Editor Keyboard Shortcuts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1919
Unity Pro Main Screen and Project Browser Keyboard Shortcuts. . . . 1920

33003101 12/2015 27
 C.2 Configuring the Project. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1922
PLC Configuration Screen Keyboard Shortcuts. . . . . . . . . . . . . . . . . . 1922
C.3 Creating the Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1923
ST/IL Editors Keyboard Shortcuts . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1924
FBD Editor Keyboard Shortcuts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1926
SFC Editor Keyboard Shortcuts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1928
LD Editor Keyboard Shortcuts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1930
Data Editor Keyboard Shortcuts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1932
Type Library Browser Keyboard Shortcuts . . . . . . . . . . . . . . . . . . . . . 1933
Type Library Manager Keyboard Shortcuts . . . . . . . . . . . . . . . . . . . . . 1934
C.4 Operating the Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1935
Search Replace Tool Screen Keyboard Shortcuts. . . . . . . . . . . . . . . . 1936
Diagnostic Viewer Screen Keyboard Shortcuts . . . . . . . . . . . . . . . . . . 1937
PLC Screen Keyboard Shortcuts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1938
Animation Screen Keyboard Shortcuts . . . . . . . . . . . . . . . . . . . . . . . . 1939
Operator Screen Keyboard Shortcuts . . . . . . . . . . . . . . . . . . . . . . . . . 1940
C.5 Documenting the Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1941
Documentation Screen Keyboard Shortcuts . . . . . . . . . . . . . . . . . . . . 1941
Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1943
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1965

28 33003101 12/2015
 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, service, 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.

33003101 12/2015 29
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 its installation, and has received safety training to recognize and avoid
the hazards involved.

30 33003101 12/2015
 About the Book

At a Glance

Document Scope
This document describes programming a Modicon M340, Modicon M580, Premium, Atrium, or
Quantum PLC using the IEC 61131-3 conforming programming languages Function Block
Diagram (FBD), Ladder Diagram (LD), Sequential Function Chart (SFC), Instruction List (IL) and
Structured Text (ST).

Validity Note
This document is valid for Unity Pro 11.0 or later.

Related Documents

Title of Documentation Reference Number

Unity Pro Program Languages and structure, Reference Manual 35006144 (English),
35006145 (French),
35006146 (German),
35013361 (Italian),
35006147 (Spanish),
35013362 (Chinese)
Unity Pro System Bits and Words, Reference Manual EIO0000002135 (English),
EIO0000002136 (French),
EIO0000002137 (German),
EIO0000002138 (Italian),
EIO0000002139 (Spanish),
EIO0000002140 (Chinese)

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

33003101 12/2015 31
32 33003101 12/2015
 Unity Pro
General
33003101 12/2015

Part I
General

General

Subject of this Part

This part presents Unity Pro services and describes the different tools used to manage a project:
access rights, save/restore, online/offline mode services, etc.

What Is in This Part?

This part contains the following chapters:
Chapter Chapter Name Page
1 General Presentation of Unity Pro 35
2 Programming Language Editors 43
3 Connecting a terminal to a PLC 55
4 Global project management 57
5 Project browser 161
6 Functional modules 221
7 FDT Container 253
8 Type Library Manager 293

33003101 12/2015 33
General

34 33003101 12/2015
 Unity Pro
General Presentation
33003101 12/2015

Chapter 1
General Presentation of Unity Pro

General Presentation of Unity Pro

Overview
This chapter describes the general features of a project created using Unity Pro.

What Is in This Chapter?

This chapter contains the following topics:
Topic Page
Capabilities of Unity Pro 36
User Interface 40

33003101 12/2015 35
General Presentation

Capabilities of Unity Pro

Hardware Platforms
Unity Pro supports the following hardware platforms:
 Modicon M340
 Modicon M580
 Quantum
 Momentum
 Premium
 Atrium

Programming Languages
Unity Pro provides the following programming languages for creating the user program:
 Function Block Diagram FBD
 Ladder Diagram (LD) language
 Instruction List IL
 Structured Text ST
 Sequential Control SFC
 Ladder Logic 984 (LL984)

All of these programming languages can be used together in the same project.
All these languages (except LL984) conform to IEC 61131-3.

Block Libraries
The blocks that are included in the delivery of Unity Pro extensive block libraries extend from
blocks for simple boolean operations, through blocks for strings and array operations to blocks for
controlling complex control loops.
For a better overview, the different blocks are arranged in libraries, which are then broken down
into families.
The blocks can be used in the programming languages FBD, LD, IL, and ST.

Elements of a Program
A program can be constructed from:
 a master task (MAST)
 a FAST task (not available for Momentum)
 one to 4 AUX tasks (not available for Modicon M340 and Momentum)
 sections, which are assigned one of the defined tasks
 sections for processing time controlled events (Timerx, not available for Momentum)
 sections for processing hardware controlled events (EVTx, not available for Momentum)
 subroutine sections (SR)

36 33003101 12/2015
 General Presentation

Software Packages
The following software packages are available:
 Unity Pro S
 Unity Pro L
 Unity Pro XL
 Unity Pro XLS

Performance Scope
This table shows the main characteristics of the individual software packages:

Unity Pro S Unity Pro L Unity Pro XL Unity Pro XLS

Programming languages
Function Block Diagram FBD + + + +
Ladder Diagram (LD) + + + +
language
Instruction List IL + + + +(2)
Structured Text ST + + + +(2)
Sequential Language SFC + + + +(2)
Ladder Logic 984 (LL984) + + + +
Libraries (1)
Standard library + + + +(2)
Control library + + + +(2)
Communication library + + + +(2)
Diagnostics library + + + +(2)
I/O management library + + + +(2)
System library + + + +(2)
Motion control drive library - + + +(2)
TCP Open library - optional optional optional (2)
Obsolete library + + + +(2)
MFB library + + + +(2)
Safety library - - - +
Memory card file + + + +(2)
management library
General information
Create and use data + + + +(2)
structures (DDTs)
Create and use Derived + + + +
Function Blocks (DFBs)

33003101 12/2015 37
General Presentation

Unity Pro S Unity Pro L Unity Pro XL Unity Pro XLS

Project browser with + + + +
structural and/or functional
view
Managing access rights + + + +
Operator screen + + + +
Diagnostic viewer + + + +
System diagnostics + + + +
Project diagnostics + + + +(2)
Trending Tool + + + +
Application converter PL7 converter PL7 converter PL7 converter PL7 converter
Concept Converter Concept Converter Concept Concept
Partial conversion Converter Converter
Managing multi-stations - - - -
Supported platforms
Modicon M340 BMX P34 1000 BMX P34 1000 BMX P34 1000 BMX P34 1000
BMX P34 20•• BMX P34 20•• BMX P34 20•• BMX P34 20••
Modicon M580 - BME P58 10•• BME P58 10•• -
BME P58 20•• BME P58 20••
BME P58 30•• BME P58 30••
BME H58 20•• BME H58 20••
BME P58 40••
BME H58 40••
BME P58 50••
BME P58 60••
BME H58 60••
Momentum 171CBU78090 171CBU78090 171CBU78090 171CBU78090
171CBU98090 171CBU98090 171CBU98090 171CBU98090
171CBU98091 171CBU98091 171CBU98091 171CBU98091
Premium - All CPUs except: All CPUs All CPUs
P57 554M
P57 5634M
P57 6634M

38 33003101 12/2015
 General Presentation

Unity Pro S Unity Pro L Unity Pro XL Unity Pro XLS

Quantum - 140 CPU 311 10 CPU 311 10 CPU 311 10
140 CPU 434 12 U/A* CPU 434 12 U/A CPU 434 12 U/A
140 CPU 534 14 U/A* CPU 534 14 U/A CPU 534 14 U/A
* Upgrade using Unity OS CPU 651 50 CPU 651 50
CPU 651 60 CPU 651 60
CPU 652 60 CPU 652 60
CPU 658 60 CPU 658 60
CPU 670 60 CPU 670 60
CPU 671 60 CPU 671 60
CPU 672 60 CPU 672 60
CPU 672 61 CPU 672 61
CPU 678 61 CPU 678 61
CPU 651 60S
CPU 671 60S
Atrium - All CPUs All CPUs All CPUs
Simulator + + + +
Openness
Hyperlinks + + + +
Unity Pro Server (for OFS, + + + +
UAG)
Software components contained in the software package
Documentation as context + + + +
help and PDF
OS Loader tool + HW + + + +
firmware
Unity Loader + + + +

Legend:
+ = available
+ (1) = Availability of the blocks depends on the hardware platforms (see Unity Pro, Standard,
Block Library).
+ (2) = Available on all PLC except platforms CPU 651 60S, CPU 671 60S.
- = not available

Naming Convention
In the rest of this document, "Unity Pro" is used as general term for "Unity Pro S", "Unity Pro L",
"Unity Pro XL" and "Unity Pro XLS".

33003101 12/2015 39
General Presentation

User Interface

Overview
The user interface consists of several, configurable windows and toolbars.
User interface:

40 33003101 12/2015
 General Presentation

Legend:

Number Description
1 Menu bar (see page 1892)
2 Toolbar (see page 1898)
3 Project Browser (see page 161)
4 Editor window (programming language editors, data editor, etc.)
5 Register tabs for direct access to the editor window
6 Information window (see page 1903) (provides information about errors which
have occurred, signal tracking, import functions, etc.)
7 Status bar (see page 1905)

33003101 12/2015 41
General Presentation

42 33003101 12/2015
 Unity Pro
Programming Language Editors
33003101 12/2015

Chapter 2
Programming Language Editors

Programming Language Editors

Overview
This chapter describes the different programming languages provided by Unity Pro.

What Is in This Chapter?

This chapter contains the following topics:
Topic Page
Function Block Diagram FBD 44
Ladder Diagram (LD) Language 46
General Information about SFC Sequence Language 48
Instruction List IL 52
Structured Text ST 53

33003101 12/2015 43
Programming Language Editors

Function Block Diagram FBD

Introduction
The FBD editor is used for graphical function block programming according to IEC 61131-3.

Representation
Representation of an FBD section:

Objects
The objects of the FBD (Function Block Diagram) programming language help to divide a section
into a number of:
 Elementary Functions (EFs),
 Elementary Function Blocks (EFBs)
 Derived Function Blocks (DFBs)
 Procedures
 Subroutine calls
 Jumps
 Links
 Actual Parameters
 Text objects to comment on the logic

44 33003101 12/2015
 Programming Language Editors

Properties
FBD sections have a grid behind them. A grid unit consists of 10 coordinates. A grid unit is the
smallest possible space between 2 objects in an FBD section.
The FBD programming language is not cell oriented but the objects are still aligned with the grid
coordinates.
An FBD section can be configured in number of cells (horizontal grid coordinates and vertical grid
coordinates).
The program can be entered using the mouse or the keyboard.

Input Aids
The FBD editor offers the following input aids:
 Toolbars for quick and easy access to the desired objects
 Syntax and semantics are checked as the program is being written.
 Incorrect functions and function blocks are displayed in blue
 Unknown words (e.g. undeclared variables) or unsuitable data types are marked with a red
wavy line
 Brief description of errors in the Quickinfo (Tooltip)

 Information for variables and pins can be displayed in a Quickinfo (Tooltip)

 type, name, address and comment of a variable/expression
 type, name and comment of an FFB pin

 Tabular display of FFBs

 Actual parameters can be entered and displayed as symbols or topological addresses
 Different zoom factors
 Tracking of links
 Optimization of link routes
 Display of inspection windows

33003101 12/2015 45
Programming Language Editors

Ladder Diagram (LD) Language

Introduction
The LD editor is used for graphical ladder diagram programming according to IEC 61131-3.

Representation
Representation of an LD section:

Objects
The objects of the LD programming language help to divide a section into a number of:
 Contacts,
 Coils,
 Elementary Functions (EFs)
 Elementary Function Blocks (EFBs),
 Derived Function Blocks (DFBs)
 Procedures
 Control elements
 Operation and compare blocks which represent an extension to IEC 61131-3
 Subroutine calls
 Jumps
 Links
 Actual Parameters
 Text objects to comment on the logic

46 33003101 12/2015
 Programming Language Editors

Properties
LD sections have a background grid that divides the section into lines and columns.
The LD programming language is cell oriented, i.e. only one object can be placed in each cell.
LD sections can be 11-64 columns and 17-2000 lines in size.
The program can be entered using the mouse or the keyboard.

Input Aids
The LD editor offers the following input aids:
 Objects can be selected from the toolbar, the menu or directly using shortcut keys
 Syntax and semantics are checked as the program is being written.
 Incorrect objects are displayed in blue
 Unknown words (e.g. undeclared variables) or unsuitable data types are marked with a red
wavy line
 Brief description of errors in the Quickinfo (Tooltip)

 Information for variables and for elements of an LD section, that can be connected to a variable
(pins, contacts, coils, operation and compare blocks), can be displayed in a Quickinfo (Tooltip)
 type, name, address and comment of a variable/expression
 type, name and comment of FFB pins, contacts etc.

 Tabular display of FFBs

 Actual parameters can be entered and displayed as symbols or topological addresses
 Different zoom factors
 Tracking of FFB links
 Optimizing the link routes of FFB links
 Display of inspection windows

33003101 12/2015 47
Programming Language Editors

General Information about SFC Sequence Language

Introduction
The sequence language SFC (Sequential Function Chart), which conforms to IEC 61131-3, is
described in this section.
IEC conformity restrictions can be lifted through explicit enable procedures. Features such as multi
token, multiple initial steps, jumps to and from parallel strings etc. are then possible.

48 33003101 12/2015
 Programming Language Editors

Representation
Representation of an SFC section:

33003101 12/2015 49
Programming Language Editors

Objects
An SFC section provides the following objects for creating a program:
 Steps
 Macro steps (embedded sub-step sequences)
 Transitions (transition conditions)
 Transition sections
 Action sections
 Jumps
 Links
 Alternative sequences
 Parallel sequences
 Text objects to comment on the logic

Properties
The SFC editor has a background grid that divides the section into 200 rows and 32 columns.
The program can be entered using the mouse or the keyboard.

Input Aids
The SFC editor offers the following input aids:
 Toolbars for quick and easy access to the desired objects
 Automatic step numbering
 Direct access to actions and transition conditions
 Syntax and semantics are checked as the program is being written.
 Incorrect objects are displayed in blue
 Unknown words (e.g. undeclared variables) or unsuitable data types are marked with a red
wavy line
 Brief description of errors in the Quickinfo (Tooltip)

 Information for variables and for transitions can be displayed in a Quickinfo (Tooltip)
 type, name, address and comment of a variable/expression
 type, name and comment of transitions

 Different zoom factors

 Show/hide the allocated actions
 Tracking of links
 Optimization of link routes

50 33003101 12/2015
 Programming Language Editors

Step Properties
Step properties:

The step properties are defined using a dialog box that offers the following features:
 Definition of initial steps
 Definition of diagnostics times
 Step comments
 Allocation of actions and their qualifiers

33003101 12/2015 51
Programming Language Editors

Instruction List IL

Introduction
The IL editor is used for instruction list programming according to IEC 61131-3.

Representation
Representation of an IL section:

Objects
An instruction list is composed of a series of instructions.
Each instruction begins on a new line and consists of:
 An operator
 A modifier if required
 One or more operands if required
 A label as a jump target if required
 A comment about the logic if required.

Input Aids
The IL editor offers the following input aids:
 Syntax and semantics are checked as the program is being written.
 Keywords and comments are displayed in color
 Unknown words (e.g. undeclared variables) or unsuitable data types are marked with a red
wavy line
 Brief description of errors in the Quickinfo (Tooltip)

 Tabular display of the functions and function blocks

 Input assistance for functions and function blocks
 Operands can be entered and displayed as symbols or topological addresses
 Display of inspection windows

52 33003101 12/2015
 Programming Language Editors

Structured Text ST

Introduction
The ST editor is used for programming in structured text according to IEC 61131-3.

Representation
Representation of an ST section:

Objects
The ST programming language works with "Expressions".
Expressions are constructions consisting of operators and operands that return a value when
executed.
Operators are symbols representing the operations to be executed.
Operators are used for operands. Operands are variables, literals, function and function block
inputs/outputs etc.
Instructions are used to structure and control the expressions.

33003101 12/2015 53
Programming Language Editors

Input Aids
The ST editor offers the following input aids:
 Syntax and semantics are checked as the program is being written.
 Keywords and comments are displayed in color
 Unknown words (e.g. undeclared variables) or unsuitable data types are marked with a red
wavy line
 Brief description of errors in the Quickinfo (Tooltip)

 Tabular display of the functions and function blocks

 Input assistance for functions and function blocks
 Operands can be entered and displayed as symbols or topological addresses
 Display of inspection windows

54 33003101 12/2015
 Unity Pro
PC<->PLC connection
33003101 12/2015

Chapter 3
Connecting a terminal to a PLC

Connecting a terminal to a PLC

Methodology for connecting from a PC to a PLC

At a Glance
To program a Modicon M340, Modicon M580, Premium, or Quantum PLC using Unity Pro
software, observe the rules described below.

Cables References
Select a cable that conforms to your PLC type to physically connect your PLC to your computer:

Platform Produce Product Reference

Quantum Modbus cable 990 NAA 263 20
Modbus Plus cable UNY XCA 42 020
crossed Ethernet cable 490 NTC 000 05(1)
USB cable UNY XCA USB 033(2)
Premium terminal port cable TSX PCX 1031 (RS 232/RS 485)
terminal port cable TSX PCX 3030 (USB/RS 485)
crossed Ethernet cable 490 NTC 000 05(1)
USB cable UNY XCA USB 033(2)
Modicon M340 Modbus cable TCS MCN 3M4F3C2
crossed Ethernet cable 490 NTC 000 05(1)
USB cable BMX XCA USBH •••(2)
(1) Use a crossed cable for a PC-PLC link; whereas, use a straight-through cable for PC-Hub or PLC-Hub
link.
(2) When connecting a PC to a PLC, the use of a USB 2.0 shielded cable following the USB international
standard is strongly recommended. The cables mentioned earlier avoid unexpected behavior of the PLC
as they are shielded and tested against electrical noises.
(3) This cable is usable but not recommended as all ports of a M580 system are Auto-MDIX capable and
crossed cables could be incompatible with future gigabit systems.

33003101 12/2015 55
PC<->PLC connection

Platform Produce Product Reference

Modicon M580 mini-USB to USB-A programming cable BMX XCA USBH •••(2)
(industrial use rated)
Ethernet straight-through Cat5E cable, CE 490 NTW 000 ••(U)
or UL standard (industrial use rated)
Ethernet straight-through Cat5E cable, CE TCSEC(E/U)3M3M••S4
or UL standard (industrial use/high demand
rating)
Ethernet straight-through Cat5E cable, 1 TCSECN3M3M1S4
meter
Ethernet crossed Cat5E cable (industrial 490 NTC 000 ••(U)
use rated), CE or UL standard. (3)
(1) Use a crossed cable for a PC-PLC link; whereas, use a straight-through cable for PC-Hub or PLC-Hub
link.
(2) When connecting a PC to a PLC, the use of a USB 2.0 shielded cable following the USB international
standard is strongly recommended. The cables mentioned earlier avoid unexpected behavior of the PLC
as they are shielded and tested against electrical noises.
(3) This cable is usable but not recommended as all ports of a M580 system are Auto-MDIX capable and
crossed cables could be incompatible with future gigabit systems.

Procedure
The table below describes how to connect from a PC to a PLC.

Step Action
1 Physically connect your PLC to your computer using the appropriate cables (see page 55).
2 Check that for the chosen communication protocol, the Driver corresponding to your operating
system is correctly installed.
Note: The documentation on drivers (see Communication Drivers, Installation Manual)
describes the various drivers available according to the operating system. For example, for the
PC to be able to use an X-Way address on an Ethernet network, you must install the XIP driver.
3 Verify in the toolbar that the simulator icon is unchecked.
4 Choose the address of the PLC (see page 101) to which you want to connect and the type of link
(see page 107) using the PLC → Set Address... command.
5 Connect by selecting the command: PLC → Connection
Result: You can now perform all the operations available on line, set the PLC to RUN or to
STOP, download projects, or make program modifications, etc.

56 33003101 12/2015
 Unity Pro
Project management
33003101 12/2015

Chapter 4
Global project management

Global project management

Subject of this Chapter

This chapter introduces the various tools used for project management: security and user access
rights management, project creation, project backup, transfer of the project to the PLC,
management of the user memory, etc.

What Is in This Chapter?

This chapter contains the following sections:
Section Topic Page
4.1 Access security management 58
4.2 Project management 80

33003101 12/2015 57
Project management

Section 4.1
Access security management

Access security management

Subject of this Section

This section introduces the tools used to manage security for a project.

What Is in This Section?

This section contains the following topics:
Topic Page
Unity Pro access security management 59
Security editor 61
User Information 62
User Functions 64
User Profiles 67
Policies 72
Recovery procedure with an error 74
Access rights 75

58 33003101 12/2015
 Project management

Unity Pro access security management

At a Glance
A security configuration tool lets you limit and control access to the software different
functionalities.
NOTE: Protected access to the software is optional.
Unity Pro access security concerns the terminal on which the software is installed and not the
project, which has its own protection system.
A log file can be used to keep a chronological record of the various operations carried out by users
with access to the software.

Super User (Supervisor)

The super user is the only person with rights to manage access security for the software. The super
user defines the list including the names of users who can access the software and their access
rights.
During installation of the software on the drop, only the super user can access the security
configuration without any limitation of rights (without a password).
NOTE: The user name reserved for the super user is Supervisor.
The super user has the following rights:
 create or modify the user list,
 create or modify user profiles,
 disable one or more users,
 modify the rules for software access security,
 modify his password,
 reset user passwords.

Users
Software users are defined in the list of users by the super user, if Unity Pro access security is
active. If your name is in the user list, you can access a software instance by entering your name
(exactly as it appears on the list) and your password.
A user has the following rights:
 access the rights defined by his user profile in read mode,
 modify his password.

User Profile
The profile for a user comprises all of his access rights. It is defined by a name (2 to16 characters),
an optional comment (maximum of 256 characters) and a list of access rights. Unity Pro provides
5 preconfigured user profiles that cannot be modified. To complete this list, the super user can
create all the personalized profiles that he requires.

33003101 12/2015 59
Project management

Preconfigured User Profiles

Unity Pro provides the following 5 user profiles:

Profile Description
ReadOnly The user can only access the project in read mode, except for
the PLC address, which can be modified. He can also copy or
download the project.
Operate The user has the same rights as with a ReadOnly profile, with
the added possibility of modifying execution parameters
(constants, initial values, task cycle times, etc.).
Adjust The user has the same rights as with an Operate profile, with
the added possibility of uploading a project (transfer to the
PLC) and modifying the PLC operating mode (Run, Stop, ...).
Debug The user has the same rights as with an Adjust profile, with the
added possibility of using the debugging tools.
Program The user has the same rights as with a Debug profile, with the
added possibility of modifying the program.
Disabled User cannot access the project.

Default User Profile

When the software access security is active, the super user can authorize a given user to open the
software instance without having to enter his name and password. In this case, this user has a
default profile.

Log Information Generated by the Security Editor

Security editor log information is managed by the Microsoft Windows Event Viewer. If you want to
display the log information, launch the event viewer. Here you can filter according to all the server
sequential events.
You can use all the Event viewer functions, like sort, filter etc.

Confirm
If this option is chosen by the super user, enter your name and password each time secure access
is defined for a user action.

Multiple Instancing
When Unity Pro executes multiple instances concurrently on the same terminal, each of these
instances grants access to the functions that were defined by the rights of the user who created
this instance. However, the Unity Pro access method used (inactive security or type of active
security) is identical for all the instances.

60 33003101 12/2015
 Project management

Security editor

At a Glance
The security editor is used to define software users and their access rights. It also allows you to
define actions which are protected (user name and password) and which are stored in the log file.

Launching the security editor.

Execute the following commands to start security editor:

Step Action
1 Open with Start → Programs → Schneider Electric → SoCollaborative →
Unity Pro → Security Editor.The following dialog appears:

2 Enter your name and password.

3 Confirm with OK .
4 If you are a user (see page 59), you can access the User information screen
(see page 62) which allows you to consult your user profile or to modify your
password.
5 If you are the Super User (Supervisor) (see page 59) the Security Editor
(see page 62) will launch enabling administration of Unity Pro access security.

NOTE: The user name reserved for the super user is Supervisor.

33003101 12/2015 61
Project management

User Information

At a Glance
This tab in the security editor can be accessed by all users. It enables the execution of the following
functions:
 modify a password. Users, including the super user, can only modify their own passwords,
 consult a profile and the associated user rights.

User information tab

The User Information looks as follows. It indicates the name of the user and contains the two
sections Password and Profile:

62 33003101 12/2015
 Project management

Description of the parameters

Password field,

Parameter Description
New password Data entry field for the new password: 2 to 16 characters. This
field can be empty (no characters entered).
Confirm the new Confirmation field for the new password. The contents of this
password field has to be identical to that of the New password field.
Apply Command used to apply the new password.
Note: The new password is entirely acknowledged only if it is
validated with the OK command. Clicking Cancel cancels
acknowledgment of the new password.

Profile(s) field

Parameter Description
Product Enables the selection of the product for which you want to
display your user profile: In our case, Unity Pro.
Profile Shows the name of your user profile for the product.
View profile Use this command to display all of the access rights included in
your user profile.

33003101 12/2015 63
Project management

User Functions

At a Glance
Only the Super User (see page 59) can access this tab. It enables the execution of the
following functions:
 Modify the user list.
 Assign a profile to each user.
 Import/export information for one or more users.
 Disable/enable one or more users.
 Delete passwords for one or more users.
NOTE: The user name reserved for the super user is Supervisor.

Users tab
The User tab looks like this. It contains the two areas User and Profile:

64 33003101 12/2015
 Project management

Description of the parameters

Users field

Parameter Description
Users List of users with access to Unity Pro. The name of the super
user is Supervisor.
The Preconfigured User (see page 60) field is also available for
selection:
 user_Adjust,
 user_Debug,
 user_Operate,
 user_Program,
 user_ReadOnly.

Add Command used to add a new user to the list.

Delete Command used to delete the selected user(s) from the list.
Export Command used to export the information (name and profiles) of
the selected user(s) to a file. Passwords are not exported.
Import Command used to import the information (name and profiles) of
the selected user(s) from a file. If a user is already on the list, a
warning message is displayed.
Disable/Enable Command used to disable selected users. A disabled user is
blocked during login. One or more users can be selected. You
are asked whether the user or users should really be disabled
prior to disabling them. Disable is not possible for the user
Supervisor.
If a user has been disabled, the user name is grayed out and -
-disabled-- is displayed in the profile.
If a disabled user attempts to start Unity Pro, the User disabled
message appears.
Clear Password Command used to delete passwords for selected users such as
when a user forgot his password. Clear Password is not
possible for predefined users.

Profiles field

Parameter Description
Product Used to choose the product whose user profile you would like
to define.
Profile Used to choose the profile that is assigned to the selected user.
Apply Command used to apply the profile assignment. The profile is
entirely acknowledged only if it is validated with the OK
command. Clicking Cancel cancels assignment of the profile.

33003101 12/2015 65
Project management

Adding a user
Clicking Add displays the following dialog window:

2 data entry fields are provided:

Parameter Description
User name This field is used to enter the name of the new user (2 to 16
characters). If the name entered is not correct, or if it exists
already, a warning message is displayed.
Password Data entry field for the password: 2 to 16 characters. This field
can be empty (no characters entered).
Confirm password Confirmation field for the password. The contents of this field
has to be identical to that of the Password field.
With the following Field used to select the user whose attributes you would like to
attributes retrieve.

66 33003101 12/2015
 Project management

User Profiles

At a Glance
Only the Super User (see page 59) can access this tab. It is used to perform the following
functions:
 Add or delete a profile in the list.
 Read and modify the access rights associated with a profile.
 Import/export information for one or more user profiles.

“Profiles” Tab
The Profiles tab looks as follows. It features the Product and Profiles areas:

33003101 12/2015 67
Project management

Description of the parameters

Product area:

Parameter Description
Product Used to specify the product whose user profile you would like to
access.

Profiles area:

Parameter Description
Profiles When the product chosen is Unity Pro,list of user profiles
associated with Unity Pro.
Add Command used to add a new user profile to the list.
Delete Command used to delete one or more selected user profiles
from the list. If you delete a profile from the list, users with this
profile will now have the default profile.
Preconfigured user profiles cannot be deleted from the list.
Edit Command used to modify access rights associated with the
selected user profile.
Export Command used for exporting to a file the information (name and
profiles) of the selected user profile(s).
Import Command used for importing from a file the information (name
and profiles) of the selected user profile(s). If a user profile is
already on the list, a warning message is displayed.

68 33003101 12/2015
 Project management

Adding a user profile

Use the Add command to display the following dialog box:

2 data entry fields are provided:

Parameter Description
Add the profile This field is used to enter the name of the new user profile (2
to16 characters). If the name entered is not correct, or if it exists
already, a warning message is displayed.
With the following Field used to choose the user profile whose attributes you
would like to retrieve.

33003101 12/2015 69
Project management

Modifying a user profile

Use the Edit command to display the following dialog box:

70 33003101 12/2015
 Project management

4 areas are provided for display or data entry:

Parameter Description
Tool Shows the name of the product that you selected in the
previous screen.
Profile Shows the user profile name that you selected in the previous
screen.
Description This data entry field is used to associate a comment with the
user profile modification.
Access rights list This list displays the access rights associated with the selected
user profile.
 Access right: List of access rights associated with the user
profile.
 State On/Off: This option is used to enable/disable a
designated right for the current profile.
To enable/disable the right:
 Select Access right in the list.
 Click State On/Off: the selection mark
appears/disappears.
 Audit Yes/No: When this option is enabled, it enables an
operation to be stored in the log file.
To enable/disable the option for the corresponding access
right:
 Select Access right in the list.
 Click Audit Yes/No.

 Confirm Yes/No: Enable this option to require a

confirmation for an operation.
To enable/disable the option for the corresponding access
right:
 Select Access right in the list.
 Click Confirm Yes/No.

NOTE: You can view the access rights associated with a preconfigured profile, but you cannot
modify them.

33003101 12/2015 71
Project management

Policies

At a Glance
This tab in the security editor can be accessed only by the super user. It enables the execution of
the following functions:
 Determine the guidelines associated with a product,
 define the default profile,
 Enable/disable the Check option.
 Enable/disable the Confirm option.

Policies
The Policies tab of the security editor looks as follows:

72 33003101 12/2015
 Project management

Description of the parameters

The following table describes the screen parameters:

Parameter Description
Product Used to choose the product for which you would like to define
guidelines. In our case, Unity Pro.
Login Used to define Unity Pro access rules:
 Security off: Security is disabled. You have direct access to
Unity Pro. This is the default setting.
 Security on, mandatory login: Security is enabled. To
access Unity Pro, it is mandatory that you enter your name
and password, which will determine your profile.
 Security on, avoidable login: Security is enabled. To
access Unity Pro, enter your name and password. In this
case, you will have your user profile. You can also access
Unity Pro without entering the password. In this case, you
will have the default user profile.
 Security on, no login Security is enabled, but you have
direct access to Unity Pro. The profile then is the default
profile.
When the security is disabled, the Audit and Confirm options
will also be disabled.
Specified profile Used to define the default user profile.
Audit Used to enable or disable the Audit option (this option is only
available if security is enabled).
If this checkbox is enabled, a log file will be created to store
Unity Pro user events.
The log file is located at Start → Settings → Control Panel →
Administrative Tools → Event Viewer on your desktop.
Confirm Used to enable or disable the Confirm option.
If this box is checked, enter your name and password each time
secure access is defined for a user action (see page 67).
Note:
If you are using the Confirm option in the Policies tab of the
security editor, carefully select access rights when creating a
new profile. Otherwise, changes will require multiple
confirmations in the program sections.

NOTE: The Audit and Confirm options are not assigned to one user but apply globally to all Unity
Pro products.

33003101 12/2015 73
Project management

Recovery procedure with an error

At a Glance
The security editor is used to control access to Unity Pro. If a problem occurs, (access attempted
by an illegal user, loss of password, etc.), follow the recovery procedure corresponding to the
problem.

Access by an unknown user

If a user is not known to the security editor, and security is enabled, there are two options:
 Access is configured with an avoidable login (Security On, Password Optional): in this case,
the unknown user can access Unity Pro with the default profile,
 Access is configured with mandatory login (Security On, Password Required): in this case,
the unknown user cannot access Unity Pro.
If the database of the security editor is damaged or it was deleted, access to Unity Pro is not
possible, even if security is not active (Security Off).

Loss of password
If you have forgotten your password, the procedure to follow differs depending upon whether you
are a user or a super user:
 if you are a user, contact the super user. He can reset your password. You can then enter a new
password.
 If you are the super user, reinstall Unity Pro, choosing a customized installation: Install only the
security editor.

Database protection
To protect the database against possible damage, a backup file is created during installation. This
hidden file can only be accessed in read mode. It enables the database to be restored when a fault
occurs.
NOTE: The backup file is maintained and used if the database is damaged. If the automatic
procedure fails, then repeat the installation procedure.

74 33003101 12/2015
 Project management

Access rights

At a Glance
Unity Pro access rights are classified in the following categories:
 project services
 adjustment/debugging
 libraries
 global modification
 elementary modification of a variable
 elementary modification of DDT compound data
 elementary modification of a DFB type
 elementary modification of a DFB instance
 bus configuration editor
 input/output configuration editor
 runtime screens

Project services
The access rights for this category are as follows:

Access right Description

Create a new project You can create a new project.
Open an existing project You can open an existing project.
Save a project You can save the project.
SaveAs a project You can copy the project.
Import a project You can import a project. Partial import is considered to
be a program modification.
Build off-line You can launch generation of the executable in offline
mode.
Build on-line STOP You can launch generation of the executable in online
mode, with the PLCs powered down.
Build on-line RUN You can launch generation of the executable in online
mode, with the PLCs powered up.
Start, stop or initialize the PLC You can command the PLC (power up, power down,
initialization).
Update init values with current You can copy the current values to update the initial
values values.
Transfer project from PLC You can transfer the executable program from the PLC
to the terminal.
Transfer data init values from PLC You can transfer the initial values from the PLC.
Transfer project to PLC You can transfer the executable program from the
terminal to the PLC.

33003101 12/2015 75
Project management

Access right Description

Transfer data values from file to PLC You can transfer data from a file to the PLC.
Transfer data values from file to PLC You can transfer data from the PLC to a file.
Restore project backup in PLC You can restore the contents of backup memory
(Premium) or the memory card (Modicon M340 and
Modicon M580) in the PLC executable area.
NOTE: On Modicon M580, you can save to flash
memory if no memory card is inserted.
Save to project backup in PLC You can save the project program in the backup
memory (Premium) or the memory card (Modicon
M340 and Modicon M580).
NOTE: On Modicon M580, you can restore from flash
memory if no memory card is inserted.
Set address You can access a PLC via the network.
Modify options You can modify project attributes.

Adjustment/Debugging
The access rights for this category are as follows:

Access right Description

Modify variable values You can modify the value of the variables.
Force internal bits You can force internal bits.
Force outputs You can force outputs.
Force inputs You can force inputs.
Task management You can command execution of project program tasks
(power up, power down; initialization).
Task cycle time modification You can modify cycle time for cyclical tasks.
Suppress message in viewer You can delete the message displayed in the viewer.
Debug the executable You can debug the executable program.
Replace a project variable You can replace all occurrences of one variable in the
program by another.

76 33003101 12/2015
 Project management

Libraries
The access rights for this category are as follows:

Access right Description

Create libraries or families You can create libraries or families of user functions.
Delete libraries or families You can delete libraries or families of user functions.
Put an object into library You can insert an object in a library.
Delete an object from library You can delete an object from a library.
Get an object from a library You can import an object from a library to the project.

Global modification
The access rights for this category are as follows:

Access right Description

Modify the documentation You can modify the documentation.
Modify the functional view You can create, delete, or modify a functional module.
Modify the animation tables You can modify the structure of the animation tables
(not the values).
Modify constants value You can modify the value of the project constants.
Modify the program structure You can modify the executable code structure
(add/delete a section; modify the activation conditions
for a section, modify section order.)
Modify program sections You can modify the executable code for a section.
Modify project settings You can modify the generation options.

Elementary modification of a variable

The access rights for this category are as follows:

Access right Description

Variable add/remove You can add or delete a variable.
Variable main attributes You can modify a variable's name, type, and address.
modifications
Variable minor attributes You can modify the comment and the initial value for a
modifications variable.

33003101 12/2015 77
Project management

Elementary modification of DDT compound data

The access rights for this category are as follows:

Access right Description

DDT add/remove You can add or delete a compound data item.
DDT modifications You can modify the structure, comment and initial value
for a compound data item.

Elementary modification of a DFB type

The access rights for this category are as follows:

Access right Description

DFB type add/remove You can add or delete a DFB type.
DFB type structure modification You can modify the structure of a DFB type.
DFB type sections modification You can modify the code section of a DFB type.

Elementary modification of a DFB instance

The access rights for this category are as follows:

Access right Description

DFB instance modification You can add, delete, or modify (name and type) a DFB
instance.
DFB instance minor attributes You can modify the comment and the initial value for a
modification DFB instance.

Bus configuration editor

The access rights for this category are as follows:

Access right Description

Modify the configuration You can modify the configuration.
I/O sniffing You can carry out bus configuration sniffing.

78 33003101 12/2015
 Project management

Input/output configuration editor

The access rights for this category are as follows:

Access right Description

Modify the I/O configuration You can modify the input/output configuration.
Adjust the I/O You can adjust inputs/outputs.
Save_param You can save the module input/output parameters
explicitly (initial parameter values are replaced by their
current values).
Restore_param You can restore the module input/output parameters
explicitly (initial parameter values replace their current
values).

Runtime screens
The access rights for this category are as follows:

Access right Description

Modify screens You can modify the runtime screens.
Modify messages You can modify the runtime messages.
Add/remove screens or families You can add or delete a runtime screen.

33003101 12/2015 79
Project management

Section 4.2
Project management

Project management

Subject of this Section

This section introduces the tools used for project management.

What Is in This Section?

This section contains the following topics:
Topic Page
Access to Unity Pro Software 81
Services in Offline Mode 83
Services in Online Mode 92
Allowed Online Modifications 94
Connection / disconnection 99
Accessing a PLC via a Network 101
Overview of Types of Connection Possible With Schneider PLCs 107
Accessing communication parameters 111
Project comparison 114
Conversion of Legacy Applications/Projects 115
Importing an LL984 Application 117
Transferring the project between the terminal and the PLC 125
Update of Upload Information 129
Sending a command to the PLC 131
Project Backup Management for Modicon M340 132
Project backup for Premium 134
Save/Restore Data Between a File and the PLC 136
Compatibility Rules for Restore Using a *.DTX File 140
Transferring current values 146
Memory usage 147
Function Pack for Memory 152
Memory Card Access for Modicon M340 155
FTP and Memory Card for Modicon M340 156
Project Management with DTMs 158

80 33003101 12/2015
 Project management

Access to Unity Pro Software

At a Glance
It is possible to launch several instances of Unity Pro simultaneously on the same workstation.
However, the access method is identical for all instances and depends on whether the security
option has been enabled:
 If security is active, clicking the Unity Pro icon calls up a login dialog box which is used to access
Unity Pro.
 If security is inactive, you have direct access to Unity Pro.

Security Inactive or Active in No Login Mode

If security is inactive, execute the following commands to launch an instance of Unity Pro:

Step Action
1 Click Start → Programs.
2 Select the group Schneider Electric → SoCollaborative.
3 Select the group Unity Pro.
Result: A list appears
 Language selection
 OS Loader
 PLC Simulator
 Readme
 Registration Tool
 Types library update
 Unity Pro S, L, or XL

4 From the list, select Unity Pro S, L, or XL.

Result: Unity Pro is launched in the selected language.
Special case:
If you have not yet registered the software, a message warns you of the
number of days of use left, and asks you whether you want to register (see
Unity Pro installation manual).

33003101 12/2015 81
Project management

Other Cases
When security is active (see page 58), execute the following commands to launch an instance of
Unity Pro:

Step Action
1 Activate the Unity Pro icon: see procedure below.
Result: The dialog box Enter your user name and password is displayed.

2 Enter your name and password (if necessary).

3 Confirm with OK.

82 33003101 12/2015
 Project management

Services in Offline Mode

At a Glance
The following operations can be carried out when accessing Unity Pro software in off-line mode:
 Creating,
 Opening,
 Converting,
 Analyzing,
 Generating,
 Saving,
 Closing.

Creating a Project
To create a new project, carry out the following actions:

Step Action
1 Activate the New command in the File menu.
Result: The New Project screen appears.

2 To see all PLC versions, check Show all versions box.

33003101 12/2015 83
Project management

Step Action
3 Select the processor you wish to use from those proposed.
4 To create a project with specific values of project settings, check Settings File box and use the browser
button to localize the .XSO file (Project Settings file). It is also possible to create a new one.
If the Settings File box is not checked, default values of project settings are used.
5 Confirm with OK.

84 33003101 12/2015
 Project management

Open Dialog
Open project dialog

33003101 12/2015 85
Project management

Element Description
Look in The upper part of this dialog displays a standard
File name Windows File Open dialog.
Files of type
Opening a legacy LL984 project Please refer to Importing an LL984 Application
(see page 117).
Open Options
Open the project in read-only mode Opens the project in read-only mode.
Open import File with Wizard Select this check box to use the import
(see page 1719) wizard.
Libset version
Libset (set of libraries) contains all libraries, families, functions and variables (I/O data
structures) that can be used to develop an automation project.
In general, to open an existing project (.STU file) or an archived project (.STA file) the Libset
version can be selected.
To import a .ZEF or .XEF file, the latest Libset version must be selected.
More information on the default Libset version used to open a project according to the file
type is provided in the libset (see page 294) section.
Keep project version Select this option to keep the Libset version used at
file creation time.
If the respective Libset is not installed, the latest
Libset version will be used.
Update with latest version available Select this option to update the project with the
latest Libset version.
Select a specific target version Select this option to choose a specific Libset
version. The Version box can be used to select a
version.
Project information
Type Target PLC.
Name / Version Project name and software package version.
Last modification Date and time of last modification of the project.
Comment Comment associated to the project.

86 33003101 12/2015
 Project management

Opening a Project
To open an existing project, carry out the following actions:

Step Action
1 Choose the Open command from the File menu.
2 Select the file related to the project (file *.STU).
3 Select one of the Libset version options.
4 Confirm with Open.

Opening a project also restores the Unity Pro context, which was saved when the project was
closed. This involves:
 The list of open tools,
 For each tool: its window size, position, contents and animation status,
 taskbar and tool configuration.

The context file is a companion file to the <Project_name>.STU file. It is saved in the same
directory with the name <Project_name>.ZTX. The .ZTX file is not required to open an application.
If no .ZTX is provided the application is open with default context.
NOTE: When a project file is selected, the software provides a certain amount of information: the
project name, associated comment, version and date the project was generated, target PLC, and
date of last modification to the source code.
NOTE: The .STU file is a work file and it can not be used to switch from one version to another of
Unity Pro software. In this case, you should use the archive format (.STA file) or use the export
function in the project and create a .ZEF or .XEF file.
NOTE: The .STU file contains the configuration of the TSX CPP 110 in the Project Browser.
A The file not found message appears each time the configuration screen of the TSX CPP 110
PCMCIA card is opened. Select the required .CO file to update the CANopen configuration.

33003101 12/2015 87
Project management

Opening an Archived Project

To open a project archived in STA format, carry out the following actions:

Step Action
1 Choose the Open command from the File menu.
2 Select the file related to the project (file *.STA).
3 Select one of the Libset version options.
4 Confirm with Open.

An STA file is a project archive file that can be accessed using the Archive command in the File
menu.
The properties of the .STA file are the following:
 The .STA file is very compressed (approximately 50 times more so than the STU). It is used to
transfer projects to networks (local or Internet, for example).
 The .STA file can be used to transfer projects between versions of Unity Pro software (for
example, between version 2.0 and version 4.1).
 The .STA file contains the entire project:
 The PLC binary,
 The Upload information: comments and animation tables,
 The operator screens.

NOTE:
When a .STA file is selected, the software provides a certain amount of information:
 The project name,
 Associated comment,
 Version and date the project was generated,
 Target PLC,
 Date of last modification to the source code,
 The version of Unity Pro used to create this archive.

NOTE: As the file is compressed, loading takes much longer than for an .STU file. We recommend
using the .STA file to archive the project and the .STU file as the actual work file.
NOTE: To Fully retrieve an application with Quantum Ethernet I/O system and/or 140 NOC 78• 00
topologies, The Upload information or Open an archive files must be used.

88 33003101 12/2015
 Project management

Converting an Existing PL7 or Concept Project

To convert an existing PL7 or Concept project, carry out the following actions:

Step Action
1 Choose the Open command from the File menu.
2 Select the file related to the project:
 *.FEF or *.DFB, to launch the conversion procedure for a PL7 application
(see Unity Pro, PL7 Application Converter, User Manual),
 *.ASC, to launch the conversion procedure for a Concept application
(see Unity Pro, Concept Application Converter, User Manual).
3 Confirm with Open.

Conversion Wizard
To convert a legacy project partially or as a whole the Conversion Wizard can be used.
The Conversion Wizard provides options to remap I/O objects (channels, variables etc.) during
conversion and to adapt the hardware configuration of the new project concurrently in Unity Pro.

Shortcuts to Recent Projects

To simplify access to the current project(s), the software provides a shortcut for accessing the last
8 projects used. In the File menu, activate the shortcut to the project you would like to open.

Archiving a Project
To archive a project in STA format, carry out the following actions:

Step Action
1 Select the Save Archive command from the File menu.
2 If necessary, select the directory where the project will be stored (disk and path).
3 Enter the file name.
4 Confirm with Save.

NOTE: Archiving is only possible after a Rebuild all project with the Upload information
(see page 519) section of the Project Settings window set as follows:

 the Upload information and Comments check boxes are checked, with the Animation tables
check box unchecked
 the Upload information, Comments and Animation tables check boxes are checked
 the Upload information, Comments and Animation tables check boxes are unchecked
NOTE: The .STA file partially contains the TSX CPP 110 configuration. Do not forget to backup the
.CO file (Sycon) for CANopen after archiving of the project.

33003101 12/2015 89
Project management

Analyzing a Project
To analyze the syntax of your project, carry out the following actions:

Step Action
1 Activate the Analyze project command in the Build menu.
Result: the software analyzes the project.
2 Any errors detected are displayed in the information window at the bottom of
your screen.

Analyzing and Generating a Project

To analyze and generate your project at the same time (generation of links between input/output
modules and declared objects in the project, etc.), carry out the following actions:

Step Action
1 Activate the Rebuild all Project command in the Build menu.
Result: the software analyzes and generates the project.
2 Any errors detected are displayed in the information window at the bottom of
your screen.

Analyzing and Generating Modified Project Parts

To analyze and generate only the modified parts of your project, carry out the following actions:

Step Action
1 Activate the Build Changes command in the Build menu.
Result: the software analyzes and generates the modified parts of your project.
2 Any errors detected are displayed in the information window at the bottom of
your screen.

NOTE: The Build Changes analyses and displays only modified sections or sections impacted by
modifications. To display all warnings, a Rebuild all Project command is needed.
NOTE: The Build Changes command can be executed only if the Rebuild all Project command
has been executed at least once previously.

90 33003101 12/2015
 Project management

Backing up a New Project

To back up a new project, carry out the following actions:

Step Action
1 Activate the Save or Save As command in the File menu.
2 If necessary, select the directory where the project will be stored (disk and path).
3 Enter the file name.
4 Confirm with Save.

Backing up an Existing Project

To back up your modifications, select the Save command from the File menu.

Closing a Project
To close your project, carry out the following actions:

Step Action
1 Activate the Close command in the File menu.
2 If you have modified your project, a dialog box is displayed with the message
that you must save your project.
3 Save your project or close it without saving changes.

NOTE: Closing a project triggers saving the current context in the file <Project_name>.ZTX
(see page 87).

Exiting Unity Pro

To exit Unity Pro, carry out the following actions:

Step Action
1 Activate the Exit command in the File menu.
2 If you have modified your project, a dialog box is displayed with the message
that you must save your project.
3 Save your project or exit it without saving changes.

33003101 12/2015 91
Project management

Services in Online Mode

Programming and monitoring modes

You can access the project in the PLC in Online Mode in the following two ways:
 Programming, the PLC is reserved by the terminal; it is possible to access all the functions of
the software. It is not possible to connect in programming mode to a PLC that is already
reserved.
 Monitoring, The PLC is not reserved by the terminal; it is not possible to modify functions of the
PLC, (the program), however it is possible to modify values of the variable with the animation
table.It is also possible to connect in monitoring mode to a PLC that is already reserved. Links
between EFs are not animated.
Note: The command Tools → Options...Connection tab lets you choose the default operating
mode (see page 561).

Equal or Different Modes

On connection, the data in the PLC and the terminal is compared (see page 519):
 if the data is identical, this determines an equal online mode (see page 99),
 if the data is different, this determines a different online mode (see page 99).

Information in the PLC

Two types of information are compared between the PLC and the terminal:
 Executable information is used to identify and execute the project in the PLC:
 identification of the project,
 configuration,
 code sections,
 DDT types,
 DFB types,
 EF and EFB codes,
 project options.

 Upload information:
 project upload information: graphic code for languages with LD contacts and chart of FBD
function blocks, symbols of static and dynamic variables,
 comments: variables, code sections, project, DFBs, etc.,
 animation tables.

92 33003101 12/2015
 Project management

User functions
The user functions provided in online mode that can be accessed from the PLC menu are the
following:

Function Description
Connection/Disconnection Connection (change to online mode) or disconnection
(change to offline mode).
Set Address Access to a PLC via the network.
Standard mode Choice of connection with a PLC.
Simulator mode Choice of connection with a PLC.
Compare Comparison of terminal/PLC projects.
Transfer Project to PLC Transfer of the program between the terminal and the PLC.
and Transfer Project from PLC
Save Data from PLC to File Transfer of data between a file and the PLC.
and Restore Data from File to PLC
Run/Stop Sending a command to the PLC.
and Init
Update Upload Information Update the Upload information in the PLC.
Update Init Values with Current The PLC forces the update of the initial values using current
Values values (this applies to the variables with the save attribute).
Project Backup Backs up the project in memory.
Memory Consumption Access to PLC memory usage statistics.
Diagnostics Access to the debug function.

Cancel/Repeat
The Cancel/Repeat commands in the Edit menu are not available in the following cases:
 Deletion of a step or macro-step in online mode.
 Switch from normal view to extended view in SFC debug mode and vice-versa.

33003101 12/2015 93
Project management

Allowed Online Modifications

Overview
The following pages describe modifications that are allowed when Unity mode is online.

General Rules Concerning Online Modifications

Online modification is a feature that concerns only the ‘online equal’ state.
If the application present in the PLC is different from the one opened in Unity Pro, the state is
‘online different’. One of both applications should be chosen and loaded to be in the ‘online equal’
state.
NOTE: To download the application from Unity Pro into the PLC, it is mandatory to stop the PLC.
However, the PLC may stay in RUN mode while uploading the application to the PC via Unity Pro.
The ‘online equal’ state may only be reached if the connection mode is ‘programming’. To configure
the connection mode, use the command Tool → Options → Connection.
Two different connection modes are available:
 monitoring (see page 92): state is ‘monitoring’ and no online modification is allowed,
 programming (see page 92).

The distinction between executable code and upload information means that there are 2 kinds of
modifications:
 those which truly modify the executable information (e.g., which add a new EFB call or a new
ST instruction)
 modifications that have an impact only on the Upload information (e.g. concerning comments,
graphical information of languages).
Consequently, these kinds of modifications may not need to be built depending on whether upload
information is loaded into PLC, comments and animation tables included in upload information.
As a general rule, Unity Pro prevents the user from doing actions by mistake that would force them
to stop the PLC and/or to perform a complete download:
 either by simply disabling the forbidden functions in online mode
 or by a warning message, as follows:

To know what parts have been modified, the application browser displays a specific mark for the
modified parts and in the title bar of the editors by character ‘*’.

94 33003101 12/2015
 Project management

Modify the Program

It is always possible to modify a section of the program in online mode. As soon as a section has
been modified, it is no longer animated until the next build and transfer to PLC.
Nevertheless, depending on the kind of modifications, a SFC graph may be reset after the build
and PLC update.
Some modifications performed in SFC might need a rebuild all command. In such cases, a
warning message appears in the editor. For example, deleting an action or a transition section
requires a ‘rebuild all’ command. However, removing an action or a transition section from a step
or a transition and keeping the section unused only requires an online build.
NOTE: Adding an SFC section must be done offline, if the two following conditions are fulfilled
simultaneously:
 If the project contains at least one SFC section already.
 If the project has been designed with an earlier version than Unity Pro 3.0.

This modification requires a rebuild all of the project and a PLC stop to download the entire
application.

Modify Data
In the data editor, there is no specific operating mode.
Generally, it is allowed to modify the type of a variable or a Function Block (FB) in online mode.
Modifying a data, which is used in the program, may have consequences wherever it is used, on
the contrary to an unused variable. Therefore online actions are more restricted on used data.
NOTE: Adding a variable without rebuilding increases the memory usage until next rebuild.
For used EDT variable or used DDT/FB instance, only comments and the initial values can be
modified. Unused variable/instance may be deleted. It is allowed to create new variable/instance
online.
Concerning DDT type, it is only allowed to change comments if the type is used. It is possible to
create new DDT or to delete an unused one.
For DFB type, it is possible to:
 create, modify and delete sections
 change comments
 change initial values
 add a new public or private variable

If there is no instance of the DFB, there is no limitation. The DFB type may even be deleted. Finally
creating new DFB type(s) and instantiating it in online mode is straightforward.

33003101 12/2015 95
Project management

Modify the Configuration

For Premium and Atrium PLCs, it is not possible to add or remove any module in online mode.
Parameters of an existing module on the contrary may be configured online. Once modified, the
animated mode is no longer available until the next build and PLC update.
For Quantum system PLCs, it is possible to add or delete a selection of modules and change the
parameters of an existing module (see Modicon Quantum, Change Configuration On The Fly, User
Guide) in STOP and RUN mode.

Comment Concerning Offline Modifications

Modifications that are only possible offline and new application downloads require an offline build
and a rebuild all. In these cases, the modification is not possible online and a message notifies the
user.
The rebuild is needed:
 After application creation or import
 Once the application is already built:
 Changing some project settings
 CPU change
 Memory card change
 Memory card layout change
 Switching from real target to simulator and vice versa

Furthermore, if a flash PCMCIA card without additional SRAM (TSX MFPP •••M or
TSX MFPP •••K) is configured, no modification is allowed online. User is informed by a specific
message ‘This action is forbidden because: Flash Cartridge’.

Synthesis of Authorized and Unauthorized Modifications

The following table presents the main authorized and unauthorized online modifications. The
second column indicates which modifications have impact only to the upload information and do
not have any impact to the executable code:

Type of Modification Impacts Only Upload Allowed in Online Requires to Build the
Information Mode (RUN/STOP) Application in Offline
Mode
General
Name of Station, Programs, Sections Yes Yes No
Comment of Station, Configuration, Yes Yes No
Programs, Sections
Documentation Summary Yes Yes No
Animation Table Yes Yes No
(1) Modifying only the graphical layout or the free form comments does not impact code generation, but only
generation of the upload information.
(2) This is only available in the RUN mode for the Quantum modules.

96 33003101 12/2015
 Project management

Type of Modification Impacts Only Upload Allowed in Online Requires to Build the
Information Mode (RUN/STOP) Application in Offline
Mode
Integrated Operator Screens Yes Yes No
Functional View Yes Yes No
Security Information: Passwords, No Yes No
Protection Attributes,...
Switch Simulator <-> Real Target No No Yes
Import/Export Project No Yes No
Program
Sections of Programs: Add, Change No Yes No
Execution Order
Modify the Code of a Section (Task Yes(1) Yes No
Section, SR, Transition, Action, DFB
Sections)
Modify the Code of EVT Sections No Yes(2) Yes

Modify the Code of SFC Chart No Yes No(1)

Configuration/Communication
Premium Configuration: Add/Delete a No No Yes
Module
Premium Configuration: Change No Yes No
Module Parameters
Quantum Configuration: Add/Delete a No Yes No
Module
Quantum Configuration: Change No Yes No
Module Parameters
Changing Memory Sizes in No No Yes
Configuration Screen
Global Variables (Used Even in
Animation Table or Operator
Screen)
Remove an Used Variable No No Yes
Symbol an Used Variable No Yes No
Type an Used Variable No No Yes
Topological Address of an Used No Yes No
Variable
(1) Modifying only the graphical layout or the free form comments does not impact code generation, but only
generation of the upload information.
(2) This is only available in the RUN mode for the Quantum modules.

33003101 12/2015 97
Project management

Type of Modification Impacts Only Upload Allowed in Online Requires to Build the
Information Mode (RUN/STOP) Application in Offline
Mode
Initial Value of an Used Variable No Yes No
Comment of an Used Variable Yes Yes No
Create, Remove or Modify Unused No Yes No
Variables (EDT, DDT)
Create, Remove or Modify Unused No Yes No
Variables (FB)
Used DFB
Type Name of Used DFB No No Yes
All Comments Yes Yes No
Add a Parameter No No Yes
Add a Public or Private Variable No Yes No
Delete or Change Unused Private No Yes No
Variable
Initial Value of Parameters and No Yes No
Variables
Other Attributes of Parameters and No No Yes
Variables (Public and Private)
Modify the Code of a section No Yes No
Create a New DFB Type No Yes No
Delete an Unused DFB Type No Yes No
Used DDT
Create a New DDT Type No Yes No
Delete an Unused DDT Type No Yes No
(1) Modifying only the graphical layout or the free form comments does not impact code generation, but only
generation of the upload information.
(2) This is only available in the RUN mode for the Quantum modules.

98 33003101 12/2015
 Project management

Connection / disconnection

At a Glance
Connection enables you to change from offline to online mode. On connection, data in the PLC and
the terminal is compared:
 if the information is identical, the online mode is Equal,
 if the information is different, the online mode is Different,
By disconnecting, you can return to offline mode from an online mode.

Equal online mode

On connection to the PLC, Unity Pro runs in Equal online mode when executable files and the
Upload information are identical in the PLC and in the terminal.
You can modify the project in the same way as for offline mode. Generating the executable also
automatically triggers loading of modifications to the PLC.
If the project program has been modified in the terminal without regenerating the executable, only
the non-modified parts of the project will be animated.
To animate the entire project once again, you must generate the executable and update the PLC.

Different online mode

On connection to the PLC, Unity Pro runs in Different online mode when executable files and the
Upload information are different in the PLC and in the terminal.
To run in Equal online mode, you must transfer the project between the terminal and the PLC.
In Different online mode, the animation level is limited to access to located variables via their
topological address. Modification of the program is not authorized.

Connection procedure
You must execute the following actions to connect up:

Step Action
1 On first connection: Click (see page 101) PLC → Set Address.
2 Choose the connection mode:
 PLC → Standard mode: to connect to a PLC
 PLC → Simulator mode: to connect to a simulator

3 Click PLC → Connection.

33003101 12/2015 99
Project management

Disconnection procedure
You must execute the following actions to disconnect:

Step Action
1 Click PLC → Disconnection.

Automatic disconnection
In order to avoid online mode switching automatically to offline mode, without your explicit request
(which is possible if the process executed by the processor is too large), you are recommended to
increase the Timeout communication parameter (see page 111).

100 33003101 12/2015

 Project management

Accessing a PLC via a Network

Procedure
You must carry out the following actions to access a new PLC via the network:

Step Action
1 Activate the menu PLC → Set address command, which displays the
Set address dialogue.
2 In the PLC Address field, enter the address of the new PLC.
3 In the PLC Media field, select the type of communication you wish to use
(see page 107). For Ethway drivers, refer to the following note.
4 If you wish, modify:
 the communication parameters (see page 111) using the Communication
Parameters buttons in the PLC and Simulator group boxes
 the connection bandwidths (see page 112) using the Bandwidth button

5 To carry out a connection test click on the Test Connection button.

6 When you are finished, confirm with the OK button.

NOTE: In the Set Address dialogue, Ethway drivers are not available. To use this type of
communication, you must enter manually ETHWAY01 or ETHWAY02 in the Media drop-down
menu.
NOTE: By default the simulator is started on port number 502. To change the port number
(portnum), add in the Simulator Address box an unused port number (e.g., 127.0.0.1:511 to use
port number 511).

33003101 12/2015 101

Project management

Description of Set Address Parameters

The following table describes the Set Address dialogue:

Group box Parameter Description

PLC Address PLC address (by default, the address of the PCL physically wired to the
terminal).
The drop-down menu lists any previous addresses entered. Clicking on the
trashcan clears the drop-down list
Media This drop-down selects the type of communication with the network for the
PCL.
Communication By clicking this button you access the PLC communication parameters
Parameters (see page 111).
Simulator Address Simulator address
The drop-down menu lists any previous addresses entered. Clicking on the
trashcan clears the drop-down list
Media This drop-down selects the type of communication with the network for the
simulator.
Communication By clicking this button you access the simulator communication parameters
Parameters (see page 112).
Bandwidth Click this button to display the Online Mode Services Bandwidth dialogue
(see page 112).
Test Connection Click this button to execute a connection test without closing the Set
Address dialogue.
Speed rate auto- Choose this mode for applications which do not require a specific speed
adaptation at the end rate (e.g., Modems).
of download

102 33003101 12/2015

 Project management

Network Address Syntax

The network address syntax is documented in the Architecture and Communication Services
(see Communication Services and Architectures, Reference Manual) manual.
The following table describes the various authorized addresses according to the platforms and
media supports.

Platform Support Address syntax

Premium Uni-Telway SCP01 X-Way
Uni-Telway UNTLW01 X-Way Example: UNTLW01 0.2.1.4 access to the
Uni-Telway slave at address 4 which is connected
to rack 0, module 2, channel 1 of the local PLC.
Fipway FIP01, FIP02, X-Way
FPP2001 (driver for
the TSX FPP20
card)
Fipio FIP01, FIP02, X-Way Example: FIP02 \2.55\SYS to access to
FPP2001 FIPIO connection point 55 through the privileged
terminal Fipio (address 63 for Premium)
Example: FIP01 SYS to access to Fipio Master
through the privileged terminal Fipio (address 63 for
Premium).
PCIway PCIWAY01, X-Way
PCIWAY02
Ethway ETHWAY01, X-Way
ETHWAY02
XIP XIP01 to XIP05 X-Way Example: XIP01 {3.5}\2.55\SYS to access a
FIPIO connection point 55, through the network 3
and station 5 PLC.
Example: XIP02 {3.5}0.2.0.4 access to a Uni-
Telway slave connection at address 4 which is
connected on the rack 0 module 2 channel 0 of the
network 3 and station 5 PLC.
Ethernet IP TCP/IP IP address
Ethernet IP TCP/IP** IP address;Index or
"DNS machine name;Index"
USB USB implicit; no address is necessary as the connection
is point to point. However, it is possible to enter an
X-Way address when the PLC is acting as an X-
Way router
Modbus Plus MBPLUS01 to Modbus Plus Address Example: MBPLUS01 2.1
MBPLUS04 access to Modbus Plus node address 1 which is
connected after the Modus Bridge address 2.

33003101 12/2015 103

Project management

Platform Support Address syntax

Quantum Serial Modbus MODBUS01 to Modbus Slave Number
MODBUS04
Modbus Plus MBPLUS01 to Modbus Plus Address
MBPLUS04
Ethernet TCP/IP IP Address Example: TCPIP 84.0.127.6 access to
an Ethernet TCP/IP station.
Ethernet IP TCP/IP*** IP address;Index or
"DNS machine name;Index"
USB USB implicit; no address is necessary as the connection
is point to point
Modicon M340 Serial Modbus MODBUS01 to Direct Address: Modbus slave number
MODBUS04 Remote address: Link_address.Modbus Slave
number
Link_address = r.m.c. of Modbus link
Direct address example: 66
Bridging example:
 66\\0.0.3{118.159.35.45} for Modbus slave 66 to
PLC on Ethernet CPU.
 66\\0.3.0{118.159.35.45} for Modbus slave 66 to
PLC on Ethernet NOE on slot 3.
Ethernet TCP/IP Direct address: IP Address
Remote address: Netlink {IP address}
Netlink address = r.m.c. of Ethernet link
Direct address example: 84.0.127.6
Bridging example:
 139.160.235.20\\0.3.0{118.159.35.45} for
Ethernet CPU to PLC on Ethernet NOE on slot 3.
 139.159.35.20\\0.0.0.66 for Ethernet to Modbus
slave 66.
Ethernet IP TCP/IP** IP address;Index or
"DNS machine name;Index"
USB USB SYS or empty
Bridging example: SYS\\0.0.0.66 for USB to
Modbus slave 66.

104 33003101 12/2015

 Project management

Platform Support Address syntax

Modicon M580 Ethernet TCP/IP Direct address: IP Address
Remote address: Netlink {IP address}
Netlink address = r.m.c. of Ethernet link
Direct address example: 84.0.127.6
Bridging example:
 139.160.235.20\\0.3.0{118.159.35.45} for
Ethernet CPU to PLC on Ethernet BMX NOR on
slot 3.
 139.159.35.20\\0.4.0.66 for Ethernet to Modbus
slave 66 of channel 0 of a BMX NOM 0200 on
slot 4.
Ethernet IP TCP/IP** IP address;Index or
"DNS machine name;Index"
USB USB SYS or empty
Bridging example: SYS\\0.4.0.66 for USB to
Modbus slave 66 of channel 0 of a BMX NOM 0200
on slot 4.
Simulator Ethernet TCP/IP IP address;Index **
"localhost"
"DNS machine name;Index" **
Legend **: "Index" is the Modbus Plus or Modbus index stipulated in the bridge you want to cross.
This access only works in display mode: it cannot be used to modify the program or force
values.
***: "Index" is the Modbus Plus or Modbus index stipulated in the bridge you want to cross.
Note: You must use quotation marks when the address includes characters other than
figures, full stops or semi colons. These are used to avoid this address being analyzed
syntactically.

33003101 12/2015 105

Project management

Accessing PLCs Behind a Router

When you need to communicate to several PLCs behind routers, configure a network address
translation table in Unity Pro to handle different ports. You supply the router address and different
ports to reach PLCs behind the routers.
Example:
Suppose the router address is 139.160.39.12. The PLC addresses below are local:

PLC Number PLC Address

1 192.168.0.1:502
2 192.168.0.2:502
3 192.168.0.3:502
This example shows PLCs with different addresses, but the same port.

Network Address Translation Table

The network address translation table would look something like this:

Port Destination
TCP/IP 3501 192.168.0.1:502
TCP/IP 3502 192.168.0.2:502
TCP/IP 3503 192.168.0.3:502
This example shows the same router address with different ports, each port corresponding to
a PLC address.

Notes:
 Unity Pro can communicate with PLC 2 using the router address followed by port 3502.
 In the Set Address dialog, type 139.160.39.12:3502.
 The router sends the message to the address 192.168.0.2:502 (configured in the router in the
network address translation table).
 To communicate with other PLCs, use the same router address, but change the port number.

106 33003101 12/2015

 Project management

Overview of Types of Connection Possible With Schneider PLCs

At a Glance
Unity Pro connects to Modicon M340, Modicon M580, Premium, Atrium, and Quantum PLCs in
different ways.
Each type of connection has its own characteristics. The following table provides an overview of
the different possibilities.

Connection Solutions

CAUTION
UNEXPECTED APPLICATION BEHAVIOR
Do not connect more than one PLC over USB on the same computer.
Failure to follow these instructions can result in injury or equipment damage.

33003101 12/2015 107

Project management

The following table shows the different solutions that can be used to connect a PLC with Unity Pro
software.

Type of Connection M340 M580 Premium and Atrium Quantum

USB All processors All processors On processors: On processors:
 TSX P57 4634  140 CPU 651 50
 TSX P57 554  140 CPU 651 60
 TSX P57 5634  140 CPU 651 60S
 TSX P57 6634  140 CPU 652 60
 140 CPU 658 60
 140 CPU 670 60
 140 CPU 671 60
 140 CPU 672 60
 140 CPU 672 61
 140 CPU 671 60S
 140 CPU 678 61

Uni-Telway - - All processors, via -

terminal port and
PCMCIA cards

Modbus (1) On processors: - - All processors have a

 BMX P34 1000 Modbus connection
 BMX P34 2000 which can be used by
 BMX P34 2010 Unity Pro.
 BMX P34 20102
 BMX P34 2020

(1) Bluetooth connection is limited to Diagnostics and Animation.

(2) Requires a valid application to be installed on the PLC and requires the communication cards or modules used to
be configured correctly.
NOTE:
For Modicon M580 and M340 PLCs, the TCP/IP connection does not require a valid application inside the PLC to
work.
 For details on Modicon M580 default address configuration, refer to Unity Pro Configuration Tabs
(see Modicon M580, Hardware, Reference Manual).
 For details on Modicon M340 default address configuration, refer to Methods for IP Addressing (see Modicon M340
for Ethernet, Communications Modules and Processors, User Manual).
(3) Cannot be used to view application-specific screens in online mode.
(4) Programming mode (see page 92) cannot be accessed via a Modbus Plus network.

108 33003101 12/2015

 Project management

Type of Connection M340 M580 Premium and Atrium Quantum

XIP (2) - - Via the following -

modules:
 TSX ETY 110
 TSX ETY 4103
 TSX ETY 5103
 TSX ETY PORT
 Ethernet channel of
TSX P57 4634
 Ethernet channel of
TSX P57 5634
 Ethernet channel of
TSX P57 6634
Modbus Plus - - Via PCMCIA cards All processors
TSX MBP 100 (2)(3)(4)

Ethernet TCP/IP (2) Processors Ethernet All processors Processors Ethernet Processors Ethernet
channels: channels: channels:
 BMX P34 2020  TSX P57 4634  140 CPU 651 50
 BMX P34 2030  TSX P57 5634  140 CPU 651 60
 BMX P34 20302  TSX P57 6634  140 CPU 651 60S
 140 CPU 652 60
Via the following Via the following
 140 CPU 658 60
modules: modules:
 BMX NOE 0100  TSX ETY 4103 (3) Via the following
 BMX NOE 0110 (3) modules:
 TSX ETY 5103
 140 NOE 211 x0
 TSX ETY PORT (3)
 140 NOE 251 x0
 140 NOE 771 00
 140 NOE 771 01
 140 NOE 771 10
 140 NOE 771 11
 140 NOE 771 20

(1) Bluetooth connection is limited to Diagnostics and Animation.

(2) Requires a valid application to be installed on the PLC and requires the communication cards or modules used to
be configured correctly.
NOTE:
For Modicon M580 and M340 PLCs, the TCP/IP connection does not require a valid application inside the PLC to
work.
 For details on Modicon M580 default address configuration, refer to Unity Pro Configuration Tabs
(see Modicon M580, Hardware, Reference Manual).
 For details on Modicon M340 default address configuration, refer to Methods for IP Addressing (see Modicon M340
for Ethernet, Communications Modules and Processors, User Manual).
(3) Cannot be used to view application-specific screens in online mode.
(4) Programming mode (see page 92) cannot be accessed via a Modbus Plus network.

33003101 12/2015 109

Project management

Type of Connection M340 M580 Premium and Atrium Quantum

PCI - - On Atrium processors -
only:
 TSX PCI 57 204
 TSX PCI 57 354

Fipio (2) - - All PLCs connected to -

the Fipio bus to which the
PC running Unity Pro is
connected, as well as all
those accessible via X-
Way routers

Fipway (2) - - All PLCs connected to -

the Fipway network to
which the PC running
Unity Pro is connected,
as well as all those
accessible via X-Way
routers
(1) Bluetooth connection is limited to Diagnostics and Animation.
(2) Requires a valid application to be installed on the PLC and requires the communication cards or modules used to
be configured correctly.
NOTE:
For Modicon M580 and M340 PLCs, the TCP/IP connection does not require a valid application inside the PLC to
work.
 For details on Modicon M580 default address configuration, refer to Unity Pro Configuration Tabs
(see Modicon M580, Hardware, Reference Manual).
 For details on Modicon M340 default address configuration, refer to Methods for IP Addressing (see Modicon M340
for Ethernet, Communications Modules and Processors, User Manual).
(3) Cannot be used to view application-specific screens in online mode.
(4) Programming mode (see page 92) cannot be accessed via a Modbus Plus network.

110 33003101 12/2015

 Project management

Accessing communication parameters

Procedure for accessing PLC parameters

You must perform the following actions to access the communication parameters of the PLC:

Step Action
1 Access the Set Address screen (see page 101).
2 Click on the Communication Parameters button in the PLC field to display the
following screen:

3 Modify the parameters you wish to change:

 Enter the number of attempts you wish to be made for failure recovery in the
Number of tries field.
 Enter the timeout delay to be used for failure recovery in the Timeout (ms)
field:
 For Uni-Telway, the recommended value is: 4000 ms.
 For Modbus ASCII, the recommended value is: 6000 ms.

 Check the Speed at 115 KBds box to increase the project loading speed:
from the configured speed to 115 KBds. This option is only available in Uni-
Telway mode for TSX 57 3•• and TSX 57 4•• processors. For all other types
of processor the Speed at 115 KBds option has no effect.
Note: Click on Driver Settings to display the driver management screen
(see Communication Drivers, Installation Manual).
4 Confirm with OK.
Note: Any modification to the communication parameters of the PLC will only
actually be taken into account if it is confirmed by clicking OK in the Set Address
screen. Clicking Cancel cancels acknowledgment of any modifications.

33003101 12/2015 111

Project management

Procedure for accessing simulator parameters

You must perform the following actions to access the communication parameters of the simulator:
(see Unity Pro, Program Languages and Structure, Reference Manual )

Step Action
1 Access the Set Address screen (see page 101).
2 Click on the Communication Parameters button in the Simulator field to
display the following screen:

3 Modify the parameters you wish to change:

 enter the number of attempts you wish to be made for failure recovery in the
Number of tries field,
 enter the timeout delay to be used for failure recovery in the Timeout (ms)
field.
4 Confirm with OK.
Note: Any modification to the simulator communication parameters will only
actually be taken into account if it is confirmed by clicking OK in the Set Address
screen. Clicking Cancel cancels acknowledgment of any modifications.

Procedure for accessing bandwidths

You may divide up the bandwidth quota allocated to Unity Pro for the selected communication
medium between the different functions available in online mode.
This screen is used to define the percentage of bandwidth allocated to each of the 4 categories of
functionality in online mode:
 Animation Support: animation tables, operator screens, animation of language editors,
application-specific screens. The higher the percentage allocated, the higher the frequency with
which the data in the PLC will be scanned.
 PLC Monitoring: monitoring of the overall operating mode of the PLC (Run or Stop), or of its
tasks for the "Program debugging" function. The higher the percentage allocated, the higher the
frequency with which the state of the PLC and its tasks will be scanned.

112 33003101 12/2015

 Project management

 PLC Screen (PLC debug screen): the higher the percentage allocated, the higher the frequency
with which the PLC and application information will be scanned.
 Diagnostics (Diagnostic Viewer). The higher the percentage allocated, the higher the
frequency with which the alarms in the PLC will be acquired.
This screen is used to optimize performance in online mode, by adjusting the parameters to suit:
 the characteristics of the project loaded onto the PLC: numerous and frequent diagnostics
alarms, many animation screens open at once
 and the use made of online mode: the most frequently used functions.
Procedure:

Step Action
1 Access the Set Address screen (see page 101).
2 Click on the Bandwidth button to display the following screen:

3 Using the sliders, adjust the parameter values to suit the characteristics of your
project and the functions you use most frequently in online mode.
4 Click on the Default button if you want to revert to the default values.
5 The Freeze option is used for fine adjustment (in increments) of the parameters
to suit the characteristics of the project loaded in the PLC.
It is used to retain the value of a parameter once the response time of the
corresponding function has been determined, and then adjust only the
parameters corresponding to the other functions.
6 Confirm with OK.
Note: Any modification will only actually be taken into account if it is confirmed
by clicking OK in the Set Address screen. Clicking Cancel cancels
acknowledgment of any modifications.

33003101 12/2015 113

Project management

Project comparison

At a Glance
Project comparison provides you with a concise overview of the possible differences between a
project embedded in the PLC and a project in the terminal. For each project, the following
information is displayed:
 Name,
 Version,
 Last build: date and time the executable was last generated.

Procedure
You must perform the following actions to launch project comparison:

Step Action
1 Activate the PLC → Compare command, which displays the screen below.

2 Confirm with OK.

Different projects
If the projects are different, 2 commands let you carry out a transfer between the terminal and the
PLC or vice versa, thus changing to Equal online mode:
 Transfer Project to PLC, transfer the project from the terminal to the PLC,
 Transfer Project from PLC, transfer the project from the PLC to the terminal.
NOTE: When the transfer is not possible, the corresponding button is grayed out (for example, the
Transfer Project from PLC command is grayed out when the project embedded in the PLC is
invalid or when information required for uploading is missing or invalid).

114 33003101 12/2015

 Project management

Conversion of Legacy Applications/Projects

Introduction
There are 2 possibilities to convert legacy applications to Unity Pro.
 Global conversion provides to convert a legacy application (PL7, Concept) to Unity Pro as a
whole.
 Partial conversion with the conversion wizard provides to select parts of a legacy application to
be converted and to control the conversion result.
To convert a legacy application to Unity Pro, you must at first export the application out of the
legacy software (PL7, Concept).
NOTE: In case of global conversion with a default hardware configuration (see below) as well as
in case of partial conversion, the hardware configuration must be edited and completed by the
user.

Global Conversion
To convert a legacy application as a whole you select the file exported out of the legacy software
in Unity Pro via File → Open.
The respective converter (PL7 Converter, Concept Converter) automatically generates a Unity Pro
application.
For detailed information on the converters, please refer to Unity Pro Software -> PL7 Converter or
Unity Pro Software -> Concept Converter.
 Global conversion for Premium and Quantum contains also a hardware configuration.
 Applications with PLCs which do not have a direct equivalent in Unity Pro (Compact,
Momentum, TSX Micro) should be converted using the partial conversion with the conversion
wizard.
However, if global conversion is chosen, a default hardware configuration is generated.
 For global conversion of Compact applications you can select either Quantum or Modicon M340
as target PLC. Please refer to Importing an LL984 Application (see page 117).
 Global conversion of Momentum applications contains only a default Quantum hardware
configuration with a CPU (140 CPU 534 14A/U) and a power supply (140 CPS 424 00). If
needed the default CPU can be replaced.
 Global conversion of TSX Micro applications contains only a default Modicon M340 hardware
configuration with a CPU (BMX P34 2020) and a power supply (BMX CPS 2000). If needed the
default CPU can be replaced.

33003101 12/2015 115

Project management

Partial Conversion
To convert a legacy application partially to Unity Pro, use the conversion wizard.
You can launch the conversion wizard in Unity Pro via Tools → Convert Partially.
With the conversion wizard you can:
 select the parts of the application to be converted
 remap I/O objects before conversion
 adapt concurrently the hardware configuration of the new application in Unity Pro
 modify the amount of used memory in the CPU

The partial conversion is possible for TSX Micro, Premium, Quantum, Momentum and Compact
applications.
With partial conversion for Compact and Momentum applications it is recommended to prepare a
Modicon M340 hardware configuration.
For detailed information, please refer to Unity Pro Software -> Operating Modes -> Conversion
Wizard, page 1777.

116 33003101 12/2015

 Project management

Importing an LL984 Application

Introduction
When you import an application to Unity Pro from other programming software, some functions
may behave differently.
For example:
 Cold start behavior of Unity Pro LL984 applications is different from legacy LL984 applications.
 Imported Concept IEC coils behave differently than imported LL984 coils.
 Unit Pro MATH functions might not behave the same as legacy LL984 (overflow, underflow,
etc.).

WARNING
UNINTENDED EQUIPMENT OPERATION
 After you imported an application program, edit the result carefully to check that all the logic
elements have been ported completely and are located correctly in the program.
 Test the application before running it to check that it performs as expected.
 If necessary, edit the program to add logic elements that are missing, remove code that is not
necessary, and replace logic elements that behave differently from their intended purpose.
Failure to follow these instructions can result in death, serious injury, or equipment
damage.

General Message after Import

After the import check the log file (see page 124) for error and warning messages.
You have to Analyze and Build the project.

Import
To import an LL984 application use the File → Open menu command.
Please refer to Open dialog (see page 85).
You can import the following legacy LL984 applications:
 Concept Projects (*.ASC)
 Modsoft Projects (*.CFG)
 ProWORX32 Databases (*.PWX)
 ProWORX Nxt (*.DCF)

NOTE: Imported MSTR functions are not designed to work with the Modicon M340 CPUs. After an
application is converted to Unity Pro, it must be manually updated. The MSTR function must be
replaced by the READ_VAR and WRITE_VAR functions.
For further information please refer to Import / Export of LL984 Applications (see LL984 Editor,
Reference Manual, LL984 Specifics).

33003101 12/2015 117

Project management

LL984 Options Dialog (-> Target PLC Quantum)

After selecting a legacy LL984 application file, the following LL984 Options dialog is displayed.
The following graphic shows an example with a legacy Quantum LL984 source application and a
Quantum selected as target PLC family.

Element Description
Application Displays the name of the legacy application to be imported.
Source PLC Family Displays the PLC family of the legacy application to be
imported.
OK Starts the import.
Cancel Displays a message ...“Convert” step failed, no
application is imported, and the following message is generated
in the import log file: “Conversion terminated by User”.

118 33003101 12/2015

 Project management

Element Description
Full Topological This check box is only used to convert applications to Modicon
M340 PLCs.
Symbols
Original Select this option to use the original variable names of the
legacy application in your new Unity Pro application.
_XYYYYY Select this option to automatically convert the legacy variable
names.
The new variable names will be composed according to the
following list:
 _: an underscore will be the leading sign of the converted
variables.
 X: represents the data type in the memory area.
 0: %M (memory bit)
 1: %I (discrete input)
 3: %IM (input word)
 4: %MW (memory word)

 YYYYY: represents the address number.

For example _400001 stands for%MW1.

Target PLC Family
Quantum Select this option to use the Quantum as target PLC.
M340 Select this option to use the Modicon M340 as target PLC.
The Modicon M340-specific parameters for full topological
addressing are listed in a separate table below.
Momentum Select this option to use the the Modicon Momentum under
Unity Pro as target PLC.
Label causes SR Select this option to import a segment containing labels as an
SR segment, even if its scheduling does not express this.
Labels are allowed only in SR segments.
For details please refer to Calling Subroutines (see page 1175).

33003101 12/2015 119

Project management

LL984 Options Dialog (-> Target PLC Modicon M340)

Converting a legacy LL984 application to a Modicon M340 application you can determine the kind
of addressing. By default Mixed topological / State RAM addressing is used (option Full
Topological not selected).
Mixed Topological / State RAM Addressing (-> Modicon M340)
The following graphic shows an example for converting a legacy Compact application to a Modicon
M340 application with Mixed topological / State RAM addressing (option Full Topological not
selected).

NOTE: If you want to import a legacy LL984 Compact application which uses Modbus request to
communicate with an HMI, you have to use State RAM addressing to preserve the Modbus
exchange between PLC and HMI.

120 33003101 12/2015

 Project management

Full Topological Addressing (-> Modicon M340)

To convert a legacy LL984 application to a Modicon M340 application with full topological
addressing, the option Full Topological has to be selected.
 All word variables get a declaration with a symbol and the topological address in the data editor,
if not already present.
 Input Words are copied to a mirror area of memory words, allowing SCADA access.
 Discrete words are directly addressed with topological addresses in the programs, if no symbols
are defined for them, showing in this way directly their hardware connection to the controller.
 If SCADA access is required to discrete inputs, the input bits can be copied as well to a mirror
area of memory bits by checking Copy Input Bits.
 SCADA access for inputs with Full Topological checked needs modified addresses in the
SCADA system – the offsets in the dialog must be added to the original offsets and the memory
areas must be used instead of the input areas.

33003101 12/2015 121

Project management

The following graphic shows an example for converting a legacy Compact application to a Modicon
M340 application with full topological addressing.

122 33003101 12/2015

 Project management

For converting a legacy LL984 application to a Modicon M340 application with full topological
addressing, the following additional parameters are used:

Element Description
Full Topological Activate this option to convert input word addresses (3x) of the
legacy LL984 application to a separate, mirrored area of the
%MW areas of the target Modicon M340 application.
If this option is not activated, the legacy LL984 application is
converted into a State RAM Modicon M340 application.
Input Word Offset Enter the offset for the input word addresses (3x) in the mirrored
area of the %MW area of the target Modicon M340 application.
Copy Input Bits Activate this option to additionally convert input bit addresses
(1x) to the mirrored area of the %M area of the target Modicon
M340 application.
Input Bit Offset Enter the offset for the input bit addresses (1x) in the mirrored
area of the %M area of the target Modicon M340 application.

NOTE: With this Full Topological option activated you must manually change the access to the
%I and %IW addresses in the SCADA components.

Converting a Legacy Compact Application to Modicon M340 with Full Topological Addressing
During conversion of a legacy Compact application to a Modicon M340 application with full
topological addressing, the import automatically creates separate ST code sections for input and
output operations with copying commands to transfer I/O data to the mirrored memory areas.
Please refer to Module Emulation (see LL984 Editor, Reference Manual, LL984 Specifics).

Import Behavior
During import of a legacy LL984 application, problems may be detected:
 controller family not supported
 I/O family not supported
 I/O module not supported
 rack count exceeded
 instruction/function block not supported
 non-coil in column 11

Generally such an issue does not stop the import.

Instead a message is displayed for each of these detected problems in the Import/Export tab of
the Output Window at the bottom of the Unity Pro user interface.
Double-click such a message in the Output Window to access the respective dialog in your
application.

33003101 12/2015 123

Project management

If detected problems occur the following is done during import:

 Not supported controllers or I/O families are replaced by a default Quantum/Modicon M340
configuration.
 Not supported I/O modules are ignored in case of Quantum as target PLC family.
 Exceeding racks and their modules are ignored.
 Not supported instructions are represented by empty DFBs that look identical to the LL984
instruction. In such a case proceed as described under Not Supported Legacy LL984
Instructions and User Loadables (see LL984 Editor, Reference Manual, LL984 Specifics).
 Equation networks with questionable conversions (for example implicit type cast) will contain the
imported equation statement and an additional message.
Equation networks which are not compliant with Modicon M340 variable alignment rules, will
cause a build error during Analyze.
For details please refer to Equation Networks (see LL984 Editor, Reference Manual, LL984
Specifics).
 The import of a legacy application that contains duplicated identifiers is aborted. For details
please refer to Duplicated Identifiers (see LL984 Editor, Reference Manual, LL984 Specifics).
If parts of a legacy application are not imported, after Analyze and Build of the project an
appropriate message is displayed. In this case you have to adapt the application manually. (For
example in case of Modicon M340 by selecting Mixed topological and State RAM in the Memory
Tab (see page 1219) of the modules and subsequently fixing the related variables).

Import Log File

After import a message informs you that the conversion and import is finished and reminds you to
have a look at the import log file.
The import log file is stored in the root directory of your application.
You have to Analyze and Build the project.

124 33003101 12/2015

 Project management

Transferring the project between the terminal and the PLC

At a Glance
Transferring a project enables you to:
 copy the current project from the terminal to the memory of the current PLC (PLC whose
address is selected)
 copy the embedded project from the current PLC to the terminal. It then becomes the current
Unity Pro project

Transfer from the terminal to the PLC

Perform these actions to transfer the current project to a PLC:

Step Action
1 Use the PLC → Set address command to define the current PLC to which you would like to
transfer your project (see page 101).
2 Change to online mode (see page 99).
3 Activate the PLC → Transfer Project to PLC command, which displays the corresponding
screen (see page 126).
4 Check the PLC Run after Transfer box if you want the PLC to switch automatically to Run after
the transfer.
5 Activate the Transfer command.
6 If the project has not been generated in advance, the screen below allows you to generate it
before the transfer (Rebuild All then Transfer) or interrupt the transfer (Cancel Transfer).

7 The transfer progress is displayed on screen. At any moment, you can interrupt the transfer by
using the Esc key, which invalidates the PLC project.
Note: In the event that the project is transferred to a Flash Eprom memory card, the transfer can
take several minutes.

33003101 12/2015 125

Project management

Transfer from the PLC to the terminal

Perform these actions to transfer the contents of the PLC to the terminal:

Step Action
1 Use the PLC → Set address command to define the current PLC to which you would like to
transfer your project (see page 101).
2 Change to online mode (see page 99).
3 Activate the PLC → Transfer Project from PLC command to display the corresponding screen
(see page 127).
4 The transfer progress is displayed on screen. At any moment, you can interrupt the transfer by
using the Esc key.

Terminal to PLC transfer screen

The screen used to transfer the project from the terminal to the PLC is shown below:

126 33003101 12/2015

 Project management

Description of the parameters

The following table describes the parameters of the Terminal to PLC transfer screen.

Parameter Description
PC Project Identification field for the project in the terminal: name, version, date and time the
executable was last generated.
Overwritten PLC Identification field for the project embedded in the PLC: name, version, date and
Project time the executable was last generated. This project will be overwritten or
updated by the transfer.
Compatibility Restriction of compatibility (only for ascending compatibility). The configuration
declared in the current project is slightly different from the real PLC configuration,
but remains compatible.
PLC Run after Transfer If this box is checked, the PLC changes to Run after the transfer.
Transfer Transfer command.
Cancel Command used to cancel the transfer.

PLC to Terminal transfer screen

The screen used to transfer the project from the PLC to the terminal is shown below:

33003101 12/2015 127

Project management

Description of the parameters

The following table describes the parameters of the PLC to terminal transfer screen.

Parameter Description
Overwritten PC Project Identification field for the project in the terminal: name, version, date and time
the executable was last generated. This project will be overwritten or updated
by the transfer.
PLC Project Identification field for the project embedded in the PLC: name, version, date and
time the executable was last generated.
Transfer Project from PLC Transfer command: the project is transferred.
Cancel Command used to cancel the transfer.

Incompatibility during a transfer

During transfer from the terminal to the PLC, incompatibility between the current project and the
PLC configuration triggers display of a message.
During transfer from the PLC to the terminal, incompatibility between the project embedded in the
PLC and the version of Unity Pro also triggers display of a message.

128 33003101 12/2015

 Project management

Update of Upload Information

Upload Information
Upload information consists of:
 Project upload information: graphic code for languages with LD contacts and chart of FBD
function blocks, symbols of located and unlocated variables,
 Comments: variables, code sections, project, DFBs, etc.,
 Animation tables.
These are always saved when a project backup is performed on the terminal (STU or STA file), but
may or may not be included with the executable code (see page 519) when building the project
which is then transferred to the PLC.

Use of Upload Information

Upload information should only be loaded in the PLC where this is strictly necessary, in order to
optimize the available memory size and save this for the executable code, and also to improve the
performance of modifications in online mode.
In the coding and debug phase, this information is generally present on the workstation and
therefore does not need to be transferred to the PLC, thus achieving a real gain in performance.
In the maintenance and operation phase, this information should be included in the PLC where
the application needs to be restored on empty terminals (i.e. that do not have the project STU or
STA file). However, in addition to the gain in memory space, the absence of the Upload information
also forms a protection against reading and writing.

Choice of Upload Information

By default, the upload information necessary to rebuild the project program is not embedded in the
PLC.
You can choose the information to have embedded:
 The information necessary for uploading the project,
 Comments (variables and types),
 The animation tables.
To access the Upload information (see page 519) select: Tools → Project Settings → PLC
Embedded data

33003101 12/2015 129

Project management

Update
When making modifications in online mode, it is possible to choose between 2 modes of updating
the Upload information:
 Automatic update; in which case the update of Upload information is implicit on each build,
 Update on user request; in which case the update is performed explicitly, by the clicking PLC
→ Update Upload Information.
The way in which upload information is updated is chosen in the Project Settings screen
(see page 557) and is accessible by: Tools → Project Settings → PLC Embedded data
NOTE: The upload information is updated implicitly whenever a terminal project is transferred to
the PLC (where this is included with the executable code).
On connection, a message asks you to confirm the update of the Upload information, if this has
not already been performed.

130 33003101 12/2015

 Project management

Sending a command to the PLC

At a Glance
The Run/Stop and Init commands enable the project to be controlled from the terminal when it is
stored on a target PLC:
 Run/Stop launches or stops execution of the project, (see Unity Pro, Program Languages and
Structure, Reference Manual )
 Init initializes the project.

Procedure
You must perform the following actions to control the PLC:

Step Action
1 Use the PLC → Set address command to define the target PLC that you wish
to control (see page 101).
2 Change to online mode.
3 Activate the PLC → Run/Stop command to launch or stop execution of the
project or the PLC → Init command to initialize the project.
4 Confirm the command.

33003101 12/2015 131

Project management

Project Backup Management for Modicon M340

At a Glance
Automatic and manual accesses are carried out between the Schneider BMX RMS ••••• memory
card and Unity Pro or the PLC to:
 restore a project in the PLC
 save the PLC project on the memory card
 compare the PLC project and the memory card project

NOTICE
INOPERABLE MEMORY CARD
Do not format the memory card with a non-Schneider tool. The memory card needs a structure
to contain program and data. Formatting with another tool destroys this structure.
Failure to follow these instructions can result in equipment damage.

Restore Function
The restore function is carried out as follows:
 Automatically:
 after a power cycle
 on a warm start
 on a cold start

 Manually, using the Unity Pro command PLC → Project Backup... → Backup Restore.
NOTE: When you insert the memory card in run or stop mode, power cycle to restore the project
on the PLC.

WARNING
UNEXPECTED BEHAVIOUR OF APPLICATION
Ensure that the right user application is contained in the memory card before inserting it into the
PLC.
If the application contained in the memory card includes the RUN AUTO option, then the PLC will
automatically restart in RUN mode with this application as soon as the inserted memory card
content is restored to the PLC.
Failure to follow these instructions can result in death, serious injury, or equipment
damage.

132 33003101 12/2015

 Project management

Save Function
The save function is carried out as follows:
 Automatically, after:
 a download, if the memory card is present and not write-protected
 online modification, if the memory card is present and not write-protected
 detection of a system bit %S66 rising edge

 Manually, using the command PLC → Project Backup... → Backup Save.

NOTE: If you remove the memory card when the backup is in progress, the program on the
memory card is lost. With system bit %S65 you can disable processor access to the memory card.
If the memory card is not present or write-protected, the download in Processor memory is allowed
but the online modification is not allowed.

Compare Function
You can compare your project with the one contained on the memory card. To do so, use the
command PLC → Project Backup... → Compare.

Memory Card State and Diagnostic

Unity Pro and the PLC front panel display the status of the memory card:

Display on Icon/LED Description

State
Status bar at bottom Project on memory card is different from PLC project.
of Unity Pro

Memory card is not present on the PLC or is inoperable.

no icon Project in memory card is equivalent to PLC project.

LED on bottom of On Access to the memory card is enabled.
memory card slot
Flashing Activity between the memory card and the PLC.
Off Access to the memory card is disabled. You can remove the memory card.
CARDERR LED on On Memory card is missing or memory card is not detected, or project on
PLC front panel memory card is different from PLC project.
Off Memory card is detected, and project in memory card is equivalent to PLC
project.

33003101 12/2015 133

Project management

Project backup for Premium

At a Glance
Certain PLCs Premium allow you to save the project program contained in the executable zone
(see Unity Pro, Program Languages and Structure, Reference Manual ) (RAM) of the PLC in the
backup memory zone.
The available backup memory card is the TSX MFP B 096K.
Unity pro enables the use of these functions:
 Comparison
 Automatic restore (shaded field) when the PLC powers up, if the project program is different
 Save PLC program on the memory card
 Clearing of card data
NOTE: The backup function is not available when the project is already being executed on a RAM
or EPROM memory card.

Comparison
You can compare your project with the one contained in the backup memory. To do this, perform
the following actions:

Step Action
1 Activate the command PLC → Project backup → Compare....
Result: A dialog box appears informing you of the result of the comparison.

Backup Memory Card → RAM Transfer

You Must Perform the Following Actions to Restore the Contents of the Backup Memory to the
Executable Zone of the PLC:

Step Action
1 Set the WP switch on the backup memory card to ON (lock).
2 Insert the backup memory card into the PLC.
3 Result: The memory card automatically transfers the contents of the backup
memory to the executable zone of the PLC.

NOTE: Inserting the memory card in its slot triggers a cold start of the PLC.

134 33003101 12/2015

 Project management

RAM → backup memory card transfer

You must perform the following actions to transfer the project program to the backup memory:

Step Action
1 Set the WP switch on the backup memory card to OFF (unlock).
2 Insert the backup memory card into the PLC.
3 Activate the command PLC → Project backup → Save....
Result: A command confirmation screen is displayed.
4 Confirm with OK.
5 Remove the backup memory card from the PLC.
6 Set the WP switch on the backup memory card to ON (lock).

Clearing procedure
You must perform the following actions to clear the backup memory:

Step Action
1 Set the WP switch on the backup memory card to OFF (unlock).
2 Insert the backup memory card into the PLC.
3 Activate the command PLC → Project backup → Clear....
Result: A command confirmation screen is displayed.
4 Confirm with OK.

33003101 12/2015 135

Project management

Save/Restore Data Between a File and the PLC

At a Glance
The data transfer function allows you to store the value of the following data (see Unity Pro,
Program Languages and Structure, Reference Manual ) in a file:
 boolean-type located data: %Mi
 word-type located data: %MWi
 unlocated variables
 function block instances

There are 2 types of data files:

 DAT:
 Saving PLC data to a *.DAT file is allowed for all previous data types. *.DAT contains only
data blocks.
 Restoring all data blocks from a *.DAT file to the PLC is allowed if the project has not been
built since the Save was done.If a build was done, only BOOL and WORD located data (%Mi
and %MWi) are restored.
 DTX (requires Unity Pro 6.0 of higher):
 Saving PLC data to a *.DTX file is allowed for all previous data types. In addition, application
references (at the time of the Save) are saved.
NOTE: I/O and device DTT objects cannot be saved in DTX data files.
 Restoring data from a *.DTX file is allowed even if the application has been built and/or data
has been modified since the Save was done. Compatibility Rules for Restore Using a *.DTX
File (see page 140) explains the restoration process and the types of data that cannot be
restored.
NOTE: It is recommended to convert any *.DAT files to *.DTX file by restoring the.DAT file and
then saving using the *.DTX format.

CAUTION
LOSS OF DATA
Before transferring unlocated variables and function block instances data to the PLC, ensure that
your application is in a compatible state with the saved data.
Failure to follow these instructions can result in injury or equipment damage.

136 33003101 12/2015

 Project management

Procedure for Saving PLC Data

If the PLC is in RUN mode, the saving of data from the PLC to a file may need several application
cycles and the data, in the file, may be de-synchronized, which may affect application execution
during restoration.

CAUTION
UNEXPECTED BEHAVIOUR OF APPLICATION
Before saving the data, verify the impact of the save on the application execution.
Failure to follow these instructions can result in injury or equipment damage.

You must perform the following actions to save the data from the PLC to a file:

Step Action
1 To enable the menu item Save Data from PLC to File, the following must be true:
 The PLC is loaded with an application.
 The PLC is in RUN or STOP mode.
 Unity Pro is running and is connected to the PLC.
 The Application built in Unity Pro is equal to those in the PLC.
 The Application in Unity Pro is in the built state.

2 Activate the PLC → Save Data from PLC to File command.

Result: The Save Data from PLC to File dialog (CPU in STOP mode) opens.

For more information, refer to the corresponding screen (see page 138).
3 Using the checkboxes, select the data type(s) to be transferred. For located data you
must also define the range of data to be transferred by entering the start and end
address of the range.
4 Define the path and the name of the file to which the data is to be saved.
5 Confirm with OK.

33003101 12/2015 137

Project management

Data Transfer Dialog for Transfers to a File

The Save Data from PLC to File dialog (CPU in RUN mode) is shown below:

The following table shows the parameters of the Save Data from PLC to File dialog.

Parameter Description
Content This field is used to define the type and range of the data to be
transferred.
The checkboxes are used to define the type of located data. From:
and To: fields are used to define the range for located data.
Default values:
 %M and %MW checkboxes are checked
 %M and %MW range is set to the PLC values
 Unlocated variables instances and Function block
instances (DFB and EFB) are not checked
To file This field is used to define the path and name of the file.
Browse This button can be used to browse the disk to define the file name
and path.

138 33003101 12/2015

 Project management

Procedure for Restoring Data to PLC

If the PLC is in RUN mode, the restoring of data to the PLC from a file may need several application
cycles and the data may be de-synchronized, which may affect application execution.

CAUTION
UNEXPECTED BEHAVIOUR OF APPLICATION
Before restoring the data, verify the impact of the store on the application execution.
Failure to follow these instructions can result in injury or equipment damage.

You must perform the following actions to restore the data from a file to the PLC:

Step Action
1 To enable the menu item Restore Data from File to PLC, the following must be
true:
 The PLC is loaded with an application.
 The PLC is in RUN or STOP status.
 Unity Pro is running and is connected to the PLC.
 The Application built in Unity Pro may be different than those in the PLC.
 The Application in Unity Pro is built state.

2 Activate the PLC → Restore Data from File to PLC command.

Result: The Restore Data from File to PLC dialog opens.

3 Select the file to be restored to the PLC.

4 Confirm with OK.

33003101 12/2015 139

Project management

Compatibility Rules for Restore Using a *.DTX File

At a Glance
The DTX file allows a restore even if there have been changes in the application since the save
was done.
When a restore is performed, if the build number of the application is greater than the version of
the DTX file, Unity Pro analyses the content of the file to verify the compatibility with variables of
the PLC application.
The following tables presents the rules followed for restoring variables when there is a difference
between the *.DTX file and the PLC application. This condition results from building the application
after the data was saved in the *.DTX file.

CAUTION
UNEXPECTED BEHAVIOUR OF APPLICATION
Before restoring the data, verify the impact of the store on the application execution.
Failure to follow these instructions can result in injury or equipment damage.

PLC versions compatibility (Premium, Quantum , M340, M580)

As memory block allocation is different on PLCs version <= 2.0 or > 2.0:
 If the DTX file has been created from a PLC version 2.0 or < 2.0, data can’t be restored on PLC
version 2.1 or later.
 If the DTX file has been created from a PLC version 2.1 or later , data can’t be restored on PLC
version 2.0 or < 2.0.

140 33003101 12/2015

 Project management

Simple Variable Compatibilities

The following table presents the rules followed for restoring simple variables:

Case Data File Contents PLC Application Restore Behavior Unity Pro Message
Contents
1 Var1 Deleted Var1 is not restored Var1: this variable no longer
exists.
2 - New Var2 Var2 is kept in memory -
3 Var3 Var3 was renamed The restore CANNOT BE Var3: this variable no longer
into Var3-3 (name PERFORMED due to technical exists.
changed) limitations.
Var3 is deleted and Var3-3 is a
new variable.
4 Var4 is a simple Var4 was changed to The Var4 is converted into the Var4: type of the variable is
compatible type. a different simple new type, which has the same changed (from TYPE1 to
type. Source value is value as source. TYPE2). Types are
compatible with compatible.
target type.
5 Var5 is a simple Var5 was changed to The restore CANNOT BE Var5: type of the variable is
compatible type. a different simple PERFORMED. changed (from TYPE1 to
type. Source value is Var5 is converted into a different TYPE2) but value may not
not compatible with type (the target) and its value is be compatible.
target type. either: +
 longer than target type Var5: value not compatible
 not compatible with target for conversion between
type TYPE1 and TYPE2.
6 Var6 is a simple Var6 was changed Restore of original value Var6: type of the variable is
incompatible type. into another type. CANNOT BE PERFORMED. changed (from TYPE1 to
Var6 retains its application value. TYPE2). But types are not
compatible.

33003101 12/2015 141

Project management

Structured Variable Compatibilities

The following table presents the rules followed for restoring structured variables:

Case Data File PLC Application Restore Behavior Unity Pro Message
Contents Contents
DDT Types
7 Var7 is a DDT Var7 was changed to The restore CANNOT BE Var7: type of the variable is
type. a simple type. PERFORMED because type is changed (from TYPE1 to
not compatible. TYPE2). But types are not
compatible.
8 Var8 is a simple Var8 was changed to The restore CANNOT BE Var8: type of the variable is
type. a DDT type. PERFORMED because type is changed (from TYPE1 to
not compatible. TYPE2). But types are not
compatible.
9 Var9 is a DDT Var9 is changed to The restore CANNOT BE Var9: type of the variable is
type. another DDT type. PERFORMED because type is changed (from TYPE1 to
not compatible. TYPE2). But types are not
compatible.
10 Var10 is a DDT The DDT type has Make the mapping of the field Var10.SubField1: … (see
type. changed. (see the cases from 1 to 9 and cases 1 to 9 and 11 to 16).
cases from 11 to 16 for array
type sub-fields).
ARRAY Types
11 Var11 is an array. Var11 is an array of Transfer the data file values. The -
the same type, same rest of the longer application
starting index but array is kept.
longer.
12 Var12 is an array. Var12 is an array of Transfer the data file values until Var12: length of ARRAY…
the same type, same target array is full. The rest of the array (range # 2) is shorter.
starting index but source array is lost. Last indexes will be lost.
shorter.
13 Var13 is an array. Var13 is an array of The restore CANNOT BE Var13: low bound of ARRAY…
the same type, but PERFORMED because starting array (range #2) has changed.
starting index is lower indexes must be identical. Cannot restore.
or a different type.
Ending index is the
same
14 Var14 is an array. Var14 is an array of The restore CANNOT BE Var14: high bound of ARRAY…
the same type, but PERFORMED because starting array (range #2) has changed.
starting index is indexes must be identical. Cannot restore.
higher or a different
type. Ending index is
the same

142 33003101 12/2015

 Project management

Case Data File PLC Application Restore Behavior Unity Pro Message
Contents Contents
15 Var15 is an array. Var15 is an array of The restore CANNOT BE Var15: bounds of ARRAY…
the same type, but PERFORMED because starting array (range #2) have changed.
the lower and upper indexes must be identical. Cannot restore.
indexes are shifted.
The length is the
same.
16 Var16 is an array. The type of the array See cases 1 to 10 and 7 to 10. See cases 4 to 10 and 11 to 16.
has changed

Elementary Type Compatibilities

BOOL, BYTE, INT, UINT, DINT, UDINT, WORD and DWORD are compatible types if no lost of
value are detected.
Examples are:
 a DINT variable can be changed into an INT variable if only the 2 first bytes of the DINT are used
 an INT variable can be changed into an INT variable if the value is compatible.

A BOOL to EBOOL change is OK because the types are compatible, but for an EBOOL to BOOL
change the types are not compatible: the historic and forcing state are lost.
REAL, STRING, TOD, TIME, DATE and DT are not compatible types.
The table below presents the compatibility between the elementary types:

BOOL EBOOL BYTE INT UINT WORD DINT UDINT DWORD REAL STRING TOD TIME DATE DT
BOOL YES YES YES YES YES YES YES YES NO NO NO NO NO NO
EBOOL PDL YES YES YES YES YES YES YES NO NO NO NO NO NO
BYTE PDL PDL YES YES YES YES YES YES NO NO NO NO NO NO
INT PDL PDL PDL PDL YES YES YES YES NO NO NO NO NO NO
UINT PDL PDL PDL PDL YES YES YES YES NO NO NO NO NO NO
WORD PDL PDL PDL PDL YES YES YES YES NO NO NO NO NO NO
DINT PDL PDL PDL PDL PDL YES PDL YES NO NO NO NO NO NO
UDINT PDL PDL PDL PDL PDL PDL PDL YES NO NO NO NO NO NO
DWORD PDL PDL PDL PDL PDL PDL YES YES NO NO NO NO NO NO
REAL NO NO NO NO NO NO NO NO NO NO NO NO NO NO
STRING NO NO NO NO NO NO NO NO NO NO NO NO NO NO
TOD NO NO NO NO NO NO NO NO NO NO NO NO NO NO
TIME NO NO NO NO NO NO NO NO NO NO NO NO NO NO
DATE NO NO NO NO NO NO NO NO NO NO NO NO NO NO
DT NO NO NO NO NO NO NO NO NO NO NO NO NO NO

NOTE: PDL means Possible Data Loss.

33003101 12/2015 143

Project management

Compatibility of Aliases
The table below presents the rules followed for restoring aliases:

Case Data File Contents PLC Application Restore Behavior Unity Pro Message
Contents
1 Map1 is unlocated. Map1 is located on Value of the data file for Map1 is Map1: restored at
%MW100 is used. %MW100. set to %MW100. %MW100
2 Map2 is located on Map2 is no longer Value of data file for Map2 is set Map2: restored into
%MW100. located on %MW100, at the new address of Map2 unlocated data area.
%MW100 is used. (unlocated data area). %MW100: keeps current
%MW100 of the application value.
keeps its current value.
3 Map3 is located on Map3 is located on Restores the value of %MW100 Map2: restored from
%MW100. %MW200. at address %MW 200. %MW100 to %MW200.
%MW200 is used %MW100 is used. %MW100 of the application %MW100: keeps current
keeps its value. value.
4 Map4 is located on Map4 is no longer Restore CANNOT BE Map4: value at address
%MW100, but %MW located on %MW100, PERFORMED because the %MW100 is not available.
area not exported. %MW100 is used. source value is not in data file.
5 Map5 is not located Map5 is located on Restore CANNOT BE Map5: value at address
but in a unlocated %MW100. PERFORMED because the %MW100 is not available.
area not exported. source value is not in data file.
6 Map6 is located at Map6 is now located Restore CANNOT BE Map6: value at address
%MW100 and on %MW200 and PERFORMED because the %MW100 is not available.
%MW200 is used, but %MW100 is used. source value is not in data file.
%MW area is not
exported.
7 Map7 does not exist Map7 is located at Restore CANNOT BE Map7: mapped variable
or is an alias. %MW100. PERFORMED to avoid the lost of that didn't exist at the file
the current variable. generation or was an alias.
%MW100 value not
restored.
8 Topological - - MapVar: variable mapped
addresses, %CH, on an unauthorized
%SW, etc. address (%CH0.2.0).

144 33003101 12/2015

 Project management

Restoration of FB Instances and Other Variables

The table below presents the rules followed for restoring certain special variables:

Type of Entity Unity Pro Message

FB Instances: for all fields (input, output, I/O, private, -
public) that is not a pointer, the fields are restored or
not by using the rules above. If any field cannot be
restored, the FB Instance is not restored
SFC variables cannot be restored. Step1: SFC types (SFCSTEP_STATE) are not
allowed for restore
Step1: SFC types (SFCCHART_STATE) are not
allowed for restore
Hidden variables cannot be restored. -
IODDT variables cannot be restored. IOVar: IODDT types (T_ANA...) are unknown so not
allowed for restore.
Device DDTs cannot be restored. DevDDT: Device DDT types (T_...) are not allowed for
restore.

33003101 12/2015 145

Project management

Transferring current values

At a Glance
The functions below apply to the following variables:
 located and unlocated variables
 for EFBs and DFBs:
 public variables,
 private variables
 input parameters entered in the form of a value
 output parameters entered in the form of a value

Update Init Value with Current Value

The Update Init value with Current Value function is used to replace the initial values in the PLC
of these variables with their current values if their Save attribute is checked.
When the initial values are updated in the PLC, a "*" is displayed in the status bar to indicate that
the initial values in the PLC are different from the initial values displayed in the variable editor.
Use PLC → Update Init Values with Current Values to activate this function.

Update Local Init Values with PLC Init Values

When the Initial values have been modified by the function Update Init value with Current Value
or by using %S94 in the application, the Update Local Init Values with PLC Init Values function
updates the initial values on the PC in the variable editor.
After using this function "*" is no longer displayed in the status bar.
Use PLC → Update Local Init Values with PLC Init Values to activate this function.

146 33003101 12/2015

 Project management

Memory usage

At a Glance
The memory usage function is used to view:
 the physical distribution of the PLC memory (see Unity Pro, Program Languages and Structure,
Reference Manual ) (internal memory and memory card)
 the space taken up in the memory by a project (data, program, configuration, system)

It can also be used to reorganize the memory where possible.

NOTE: The memory usage screen is not available in simulation mode. This screen is only available
in standard mode when you have built the application.
If the application has been built and if it is in NOT BUILT state due to a program modification, the
screen is accessible, but it corresponds to the application built previously. Modifications will be
taken into account at the next build.

Procedure
Perform these actions to access the memory usage details of the PLC:

Step Action
1 Activate the PLC → Memory Consumption... command, which displays the corresponding
screen. The memory usage statistics of a project can only be accessed if you have generated
its executable in advance.
2 If you want to reorganize the memory to optimize it, activate the Pack command.

33003101 12/2015 147

Project management

Memory usage screen Modicon M580

The memory usage screen is shown below:

148 33003101 12/2015

 Project management

Memory usage screen Modicon M340

The memory usage screen is shown below:

33003101 12/2015 149

Project management

Memory usage screen Premium/Quantum

The memory usage screen of a PLC with a memory card and data storage is shown below. If the
PLC does not have a memory card, only the information relating to the internal memory is
displayed.

150 33003101 12/2015

 Project management

Description of the parameters

The following information fields are available:

Parameter Description
User Data This field indicates the memory space (in words) taken up by user data (objects relating
to configuration):
 Data: located data associated with the processor (%M, %MW, %S, %SW, etc.) or
the input/output modules,
 Declared Data: unlocated data (declared in the data editor) saved after power cut.
 Unsaved Declared Data: unlocated data (declared in the data editor) not saved
after power cut.
User Program This field indicates the memory space (in words) taken up by the project program:
 Constants: static constants associated with the processor (%KW) and the
input/output modules; initial data values,
 Executable code: executable code of the project program, EFs, EFBs and DFB
types,
 Upload information: information for uploading a project (graphic code of
languages, symbols, etc.).
Other This field indicates the memory space (in words) taken up by other data relating to the
configuration and the project structure:
 Configuration: other data relating to configuration (Page0 for a Quantum PLC,
hardware configuration, software configuration),
 System: data used by the operating system (task stack, catalogs, etc.),
 Diagnostic: information relating to process or system diagnostics, diagnostics
buffer,
 Data Dictionary: Dictionary of symbolized variables with their characteristic
(address, type....)
 Data Storage: file and data storage (only for Premium and Quantum).

Internal Memory This field shows the organization of the PLC's internal memory. It also indicates the
memory space available (Total), the largest possible contiguous memory space
(Greatest) and the level of fragmentation (due to online modifications).
Cartridge A / Only for Premium and Quantum, this field shows the organization of the memory cards.
Cartridge B It also indicates the memory space available (Total), the largest possible contiguous
memory space (Greatest) and the level of fragmentation (due to online modifications).
Pack This command is used to reorganize the memory structure.

Memory re-organization
Memory re-organization is activated using the Pack command (see page 152).
Memory re-organization can be performed in online or offline mode (Even if the PLC is in Run or
in Stop).
NOTE: Certain blocks cannot be moved in online mode. You will attain a lower level of
fragmentation by re-organizing the memory in offline mode.

33003101 12/2015 151

Project management

Function Pack for Memory

At a Glance
With the Pack command it is possible to reorganize the memory so as to optimize it.
To avoid certain detected errors (Internal Memory full or Cartridge Memory full) when you do a
build after online modifications, the Pack command must be carried out before the online
modifications.
NOTE: When the MEM status of the Status bar becomes Red, it is recommended to make a Pack
command by clicking on the Pack button in the Memory usage screen (see page 150) of the PLC.
The necessity of Packing the internal (or cartridge) memory is evaluated by the PLC operating
system and recommended when:
 the degree of fragmentation (due to many online modifications for instance) of the memory is
becoming high,
 and/or the size of the largest contiguous block of available memory is becoming low compared
to the total size of available memory.
NOTE: for Quantum PLCs, the Pack command can be used for OS version 2.3 or later.

Elements that Require Large Amounts of Memory

Certain project elements and actions consume a large amount of memory:
 configuration with a Cartridge memory:
 with a large section,
 with several actions in the same SFC section.

 configuration with an internal memory:

 with a large DFB instances,

 configuration with an internal memory in a Hot StandBy project:

 several DFB instances,
 adding or deleting DFB instances,
 modifying an SFC section.

152 33003101 12/2015

 Project management

Procedure
Perform the following actions to use the Pack command:

Step Action
1 Activate the PLC → Memory Consumption: command, which displays the
corresponding screen.
2 In the Internal Memory or Cartridge area check the percentage values of:
 Memory available,
 Fragmentation,
 Greatest / total of Memory available.

3 Check if these values are in the ranges listed in the tables below.
4 If Yes, click on the Pack button.
5 Above the Pack button, if the warning Memory optimization is not terminated,
please continue to pack appears, the Pack button must be clicked again.
6 The Pack function is finished when:
 the Pack button is grayed,
 the Fragmentation field is equal to 0,
 the Greatest value is near the Total Memory available value.

How the PLC detects it’s recommended to make a Pack command for Internal Memory
The following table shows how the PLC detects it’s recommended to make a Pack command,
regarding the field values in the Internal memory area:

If the Percentage of then if the Percentage of OR if

Memory available Fragmentation Greatest (1) / Total Available
is, is, Memory
is:
>25% >15% <50%
[15% ... 25%] >10% <80%
<15% >5% <90%
(1) Greatest is the Largest free contiguous block of memory available, this information is
given in the Memory usage screen.

33003101 12/2015 153

Project management

How the PLC detects it’s recommended to make a Pack command for Cartridge Memory
The following table shows how the PLC detects it’s recommended to make a Pack command,
regarding the field values in the Cartridge memory area:

If the Percentage of then if the Percentage of OR if

Memory available Fragmentation Greatest (1) / Total Available
is, is, Memory
is:
>25% >10% <70%
[15% ... 25%] >5% <90%
<15% >3% <95%
(1) Greatest is the Largest free contiguous block of memory available, this information is
given in the Memory usage screen.

154 33003101 12/2015

 Project management

Memory Card Access for Modicon M340

Overview
BMX RMS ••••• memory cards are used to save projects, Web pages, and data in general.
They are mainly used when inserted into a PLC. They may also be read with an SDcard drive or
reader.

Memory Card in the PLC

When the memory card is in the Modicon M340, it may be accessed as follows:
 with the PLC, automatically
 with the Unity Pro commands (see page 132) PLC → Project Backup... → ....
 by programming with the Memory Card File Management EFBs (See Memory Card File
Management in the System library)
 with an FTP (see page 156) client (for processors with an Ethernet connection) to manage files
on the memory card

Memory Card in an SDcard Drive or Reader

When the memory card is inserted into an SDcard drive or reader, it may be accessed as a data
storage medium (for example, a USB key or hard drive). The files on the memory card may thus
be viewed.
NOTE: In order to read the memory card in an SDcard drive or reader, install the Reliance driver
first. This driver is available on Unity Loader CD-ROM.

Tree Structure of Files on the Memory Card

When the memory card is used in an SDcard drive or reader, or via FTP, its contents are accessible
with a file explorer. The tree structure shown includes three directories:
 DataStorage, which includes all data files from Memory Card File Management EFBs (see Unity
Pro, System, Block Library)
 Firmware, which includes all files used by Unity Loader
 Web, which includes all Web pages (see Modicon M340 for Ethernet, Communications
Modules and Processors, User Manual)
It is also possible to create directories for personal files.
NOTE: The memory zone for project files is not accessible by users.

33003101 12/2015 155

Project management

FTP and Memory Card for Modicon M340

Overview
With an FTP client, it is possible to transfer files between the memory card in the Modicon M340
PLC (with an embedded Ethernet port connection), a destination, and/or a source such as a hard
drive or server.
Any FTP client installed on your computer may be used. We recommend using Filezilla or Microsoft
Explorer.
You can transfer:
 data files used by the memory card file management EFBs
 web pages used by the HTTP server
 personal files that are useful for your project

NOTE: Downloading write-protected files to the memory card can prevent the Unity loader from
properly upgrading the module. Some FTP clients (for example, the Windows Explorer client)
cannot remove write-protected files from the card. You can delete write-protected files from the
card with some FTP clients (for instance, FileZilla) that are available for free download over the
Internet.

Using FTP
The following table describes how to use FTP with Internet Explorer.

Step Action
1 Open Internet Explorer.
2 Input the FTP address in the Address field.
Example: ftp://login:password@FTP_Server_IP_Address
 Login: datastorage

 Password: datadownload

Result: The contents of the memory card are displayed.

3 Copy and/or paste the files between the memory card and your desired location.

156 33003101 12/2015

 Project management

The following modules have a time out value of 15 minutes and a maximum number of eight
sessions:
 BMX P34 20•0
 BMX NOE 01•0
 BMX NOC 0401
 BMX NOR 0200
 BME P58 ••••
 BME NOC 03•1
 TSX P57 •634
 TSX ETY •10••
 TSX ETY PORT
 140 CPU 651 •0
 140 NOE 771 ••
 140 NOC 78• 00

33003101 12/2015 157

Project management

Project Management with DTMs

At a Glance
The Unity Pro Project and Archive files can be saved and opened even if DTMs are not installed
in the DTM Hardware Catalog (see page 257).
Building a complete Unity Pro project requires that all DTMs in the project be installed.

Opening STU and STA Files

Opening the *.stu Project file and *.sta Archive files restores the DTM topology tree and device
configurations.
If there are DTMs in the restored project that are not installed on the host PC, there is no warning
message. Services such as Rebuild all or Check devices (see page 274) must be used to check
for un-installed DTMs.

Saving STU and STA Files

The DTM topology tree and device configurations are saved in these files.

ZEF Files
The DTM topology tree and device configurations is saved and restored in the *.zef import/export
files.

XEF Files
The DTM topology tree and device configurations cannot be saved nor restored in the *.xef
import/export files.

Complete Build Management

Rebuild all project (see page 90) (DTM modifications or not) requires that all DTMs in the project
be installed on the PC because the Check devices service is part a complete build.
If any DTMs are not found, a detected error is displayed in 2 places:
 The Build tab in the Output WIndow
 DTM topology tree

158 33003101 12/2015

 Project management

Partial Build Management

The user can choose not to include the DTM configuration in a PCL binary:

A partial project build that does not take into account the DTM configurations does not call the
Check devices service, therefore, this build does not need to have all the DTMs installed on the
PC.

Upload Project
The Unity Pro Transfer Project from PLC (see page 93) (Upload project) function uploads the
current DTM topology tree and the device configurations stored in the PLC (but not the information
in the Profibus Remote Bus Master and the devices). This function is not the same as the Load
data from device DTM (see page 277) service.
Some DTMs have a Compare function that allows comparing the configuration in the device to the
configuration in the PLC.

Download Project
To use the Unity Pro Transfer Project to PLC (Download project) function with DTMs:

Step Action
1 Construct a DTM topology tree.
2 Use the Store to device (see page 277) service on each DTM that has a
physical device on the network.
3 Call the Transfer Project to PLC function to download the Unity Pro project
that includes a DTM topology tree and device configurations.

33003101 12/2015 159

Project management

160 33003101 12/2015

 Unity Pro
Project browser
33003101 12/2015

Chapter 5
Project browser

Project browser

Subject of this chapter

This chapter introduces the Unity Pro browser that allows you to move around your project, via the
structure view or function view of its directory tree.

What Is in This Chapter?

This chapter contains the following sections:
Section Topic Page
5.1 Introduction to the project browser 162
5.2 Introduction to the various directories of the project browser 193
5.3 Summaries of the utilities associated with the structure view and function view 215

33003101 12/2015 161

Project browser

Section 5.1
Introduction to the project browser

Introduction to the project browser

About this sub-chapter

This sub-chapter provides general information on the project browser.

What Is in This Section?

This section contains the following topics:
Topic Page
Introduction to the project browser 163
Structural view and functional view of the project 165
The Zoom In and Zoom Out commands 167
The commands Contract all and Expand all 170
The Goto command 174
User Directory 177
Project Properties 179
Application Protection 180
Firmware Protection 184
Section and Subroutine Protection 186
Data Storage Protection 188
Loss of Password 190

162 33003101 12/2015

 Project browser

Introduction to the project browser

General points
The project browser allows you to display the contents of a Unity Pro project and to move around
its various elements: configuration, data, program, etc. To do this you can display your project in 2
different ways:
 Structural View,
 Functional View.

Structural view
The structural view displays the directory tree of the Unity Pro project and allows you to navigate
within this with direct access:
 to the configuration,
 to the DDT and DFB types,
 to the variables (EDT, DDT, DFB and EFB instances),
 to motion functions,
 to communication functions,
 to the program,
 to the animation tables,
 to the operator screens,
 to the project documentation (title page, general information).
The following illustration shows the structural view of a project:

By default, the browser displays the second level of the directory tree. To access the other levels,
you need to expand the directories.
NOTE: The default project directory name is Station. You can change this name by accessing the
project properties dialog box using the Properties command from the contextual menu.

33003101 12/2015 163

Project browser

Functional view
The functional view displays the directory tree of the project, broken down into functional modules
(see page 221). This breakdown does not take into account the order of execution of the program
by the PLC.
The following illustration shows the functional view of a project:

By default, the browser displays the first level of the directory tree. To access the other levels, you
need to expand the directories.

Navigating between the functional view and structural view.

In the toolbar of the project browser you will find the following icons that allow you to display the
various project views:

Allows you to display the structural view of the project.

Allows you to display the functional view of the project.

Allows you to display the structural view and the functional view in series
(see page 165).

Allows you to display the structural view and the functional view in parallel
(see page 166).

164 33003101 12/2015

 Project browser

Structural view and functional view of the project

At a Glance
The project browser allows you to simultaneously display the structural view and functional view of
the project. You can choose to display these views:
 in series. Both views are displayed, one next to the other,
 in parallel. Both views are displayed, one above the other.

Display of both views in series

The following illustration shows a series display of the structural view and functional view:

33003101 12/2015 165

Project browser

Display of both views in parallel

The following illustration shows a parallel display of the structure and functional views:

166 33003101 12/2015

 Project browser

The Zoom In and Zoom Out commands

At a Glance
In the functional view and structural view of the project browser, you can display a specific directory
tree level by using the Zoom In command. You can apply this command in a level below the one
you are in. This command is no longer available once you cannot expand the tree structure any
further.
The Zoom Out command allows you to go back to the previous display of the project browser.

NOTE: The following steps show how to use the Zoom In and Zoom Out commands with a
structural view. These steps can also be used with a functional view.

Displaying a specific level of the directory tree

The following table shows you how to use the Zoom in command in the structural view:

Step Action
1 In the project browser select the directory you wish to display (for example
Program).
Result: The element selected appears in reverse video.
2 Activate the Zoom In command from the Display menu or from the contextual
menu.
Result: Only the directory selected appears in the structural view (for example
Program):

33003101 12/2015 167

Project browser

Step Action
3 From the directory (for example Program) select the directory (for example
Sections) that you wish to display.
Result: The element selected appears in reverse video.
4 Activate the Zoom In command from the Display menu or from the contextual
menu.
Result: Only the directory selected appears in the structural view (for example
Sections):

Returning to the structural view of the project

The following table shows you how to use the Zoom Out command in the structural view:

Step Action
1 In the project browser select the directory from the structural view.
Result: The element selected appears in reverse video.
2 Activate the Zoom Out command from the Display menu or from the

contextual menu or by clicking on the icon.

Result: The structural view appears along with the directory tree of the project.

168 33003101 12/2015

 Project browser

Returning to directory tree level

The following table shows you how to use Zoom Out command in a lower level of the directory
tree of the structural view:

Step Action
1 In the project browser select the directory from the structural view (for example
Sections).
Result: The element selected appears in reverse video.
2 Expand the menu using the arrow to the right of the icon.

Result: The menu with the choice of different views appears.

3 In the menu (for example Program) select the structural view to be displayed.
Result: The directory (for example Program) appears in the structural view:

Selecting None displays the entire structural view of the project.

33003101 12/2015 169

Project browser

The commands Contract all and Expand all

At a Glance
In the functional view and structural view of the project browser, you can display a specific directory
tree level and its sub-directories by using the Expand all command.
The command Contract all allows you to contract an entire directory.

NOTE: The following steps show how to use the Contract all and Expand all commands with a
structural view. These steps can also be used with a functional view.

How to expand a directory

The following table shows you how to use the Expand all command in the structural view:

Step Action
1 In the project browser select the directory you wish to expand (for example
Program).
Result: the element selected appears in reverse video:

170 33003101 12/2015

 Project browser

Step Action
2 Activate the Expand all command from the Display menu or from the
contextual menu.
Result: the selected directory is expanded completely:

33003101 12/2015 171

Project browser

How to contract a directory

The following table shows you how to use the Contract all command in the structural view:

Step Action
1 In the project browser select the directory you wish to contract (for example
Program).
Result: the element selected appears in reverse video:

172 33003101 12/2015

 Project browser

Step Action
2 Activate the Contract all command from the Display menu or from the
contextual menu.
Result: the selected directory is contracted:

33003101 12/2015 173

Project browser

The Goto command

At a Glance
The Goto command allows you to access a desired location in the project browser.
In the functional view or structural view, the levels are not always expanded. The Goto command
allows you to go directly to what you are looking for.

Finding an element
The following table shows you how to use the Goto command in the structural view of the browser:

Step Action
1 Click the right mouse button on the background of the structural view.
Result: The contextual menu appears.

174 33003101 12/2015

 Project browser

Step Action
2 Select the Goto command from the menu.
Result: The Go to window appears.

3 In the window, double-click the element you want to go to.

Result: The element appears shaded in the structural view (Configuration in
the example).

4 In the Goto window confirm your choice with OK.

Elements with the same name

Where one or more elements have the same name (examples: sections). In the Go to window the
element appears with a marker. . The Next command in the Go to window is unshaded. This
allows you to pinpoint one by one the different elements with the same name when the Go to
window is active.

33003101 12/2015 175

Project browser

Fast access to an element

In order to access an element in the window more quickly in the Go to window, you can use the
Location function. Typing in the first letter of the element gives you access to the elements
beginning with these letters. The following table shows you how to use the Location function in
the structural view of the browser:

Step Action
1 Click the right mouse button on the background of the structural view.
2 Select the Goto command from the menu.
Result: The Go to window appears.

3 In the Location field type the first letter of the element you want to go to.
Result: The element appears in reverse color in the Go to window.

4 In the Go to window confirm your choice with OK.

176 33003101 12/2015

 Project browser

User Directory

At a Glance
In the Station directory and in all the directories of the project browser, you can create hyperlinks
(see page 1817) and user directories for grouping of hyperlinks.
NOTE: You cannot nest a user directory in a user directory and a hyperlink in a hyperlink.
The following illustration shows a hyperlink and a user directory in the directory Program :

33003101 12/2015 177

Project browser

Creating a User Directory

The following table shows you how to create a user directory in the structural view of the browser:

Step Action
1 In the project browser select the directory in which you wish to create a user
directory.
Result: The element selected appears in reverse video.
2 Select the Add User Directory.. command from the popup menu..
Result: the User Directory Properties window appears:

3 Give the user directory a name in the General tab.

4 In the Comment tab enter the comment associated with the user directory.
5 Click OK to confirm your choice.
Result: The user directory appears in the project browser.
6 You can now create hyperlinks (see page 1817) in the directory provided for
this purpose.

178 33003101 12/2015

 Project browser

Project Properties

At a Glance
Whichever view is displayed, you can access the project properties by using the Properties
command from the contextual menu (which can be reached by right-clicking the mouse on the
Project folder). This gives you access to a dialog box which allows you to:
 access information on the current project,
 define certain parameters of the project.

Description of the Tabs

The dialog box has 4 tabs allowing the actions given below:

Tab Description
General Name: allows you to define the name of the project.
Type: indicates the type of Unity Pro software used.
FFB Library version: indicates the Libset version used for your current project.
Protection Password setting applies to the following:
 Application:(1) application password settings (see page 180)
 Sections: sections password settings (see page 186)
 Firmware(2): firmware password settings (see page 184)
 Data Storage(3): data storage password settings (see page 188)

Identification Allows you to identify the project:

 current version with the option of automatic increment
 creation date
 generation date
 Last rebuild all
 Last partial build
Comment Allows a comment to be associated with the project.
1 Except for Modicon Momentum.
2 Only for Modicon M580 CPUs with OS version ≥ 2.00, BME NOC 03••, and BME CXM 0100 modules.
3 Only for Modicon M580 CPUs.

NOTE: By default, the dialog box is called Properties of Project. If you give the project another
name (myproject for example), this dialog box is called Properties of myproject.

33003101 12/2015 179

Project browser

Application Protection

Overview
CPU application protection by a password prevents unwanted application modification, download,
or opening (.STU and .STA files). The password is stored encrypted in the application.

Password
An application is not password protected by default.
It is possible to create or change a password at any time.
The password is case-sensitive and it must have a size from 8 to 16 alphanumeric characters. The
password robustness is increased when it contains a mix of upper and lower case, alphabetical,
numerical, and special characters.

Creating a Password
Procedure for creating the application protection password:

Step Action
1 In the project browser right-click Project.
2 Select Properties command from the popup menu.
Result: The Properties of Project window appears.
3 Select Protection tab.
4 In the Application field, click Change password ....
Result: The Modify Password window appears.
5 Enter the new password in the Entry field.
6 Enter the confirmation of the new password in the Confirmation field.
7 Click OK to confirm.
8 Click OK or Apply in the Properties of Project window to confirm all changes.
If you click Cancel in the Properties of Project window, all changes are canceled.

180 33003101 12/2015

 Project browser

Changing the Password

Procedure for changing the application protection password:

Step Action
1 In the project browser right-click Project.
2 Select Properties command from the popup menu.
Result: The Properties of Project window appears.
3 Select Protection tab.
4 In the Application field, click Change password ....
Result: The Modify Password window appears.
5 Enter previous password in the Old password field.
6 Enter the new password in the Entry field.
7 Enter the confirmation of the new password in the Confirmation field.
8 Click OK to confirm.
9 Click OK or Apply in the Properties of Project window to confirm all changes.
If you click Cancel in the Properties of Project window, all changes are canceled.

Deleting the Password

Procedure for clearing the application protection password:

Step Action
1 In the project browser right-click Project.
2 Select Properties command from the popup menu.
Result: The Properties of Project window appears.
3 Select Protection tab.
4 In the Application field, click Clear password....
Result: The Password window appears.
5 Enter the password in the Password field.
6 Click OK to confirm.
7 Click OK or Apply in the Properties of Project window to confirm all changes.
If you click Cancel in the Properties of Project window, all changes are canceled.

33003101 12/2015 181

Project browser

Auto-Lock Feature
There is an optional feature to limit access to the Unity Pro software programming tool after a
configured time of inactivity. After that time of inactivity a dialog box is displayed and prompts to
enter the application password.
Behind the modal dialog box, the current opened editors remain opened in the same position. That
means that anybody can read the current content of the Unity Pro windows but cannot continue to
work with Unity Pro.
You can activate the auto-lock feature with the check box Auto-lock and select the time-out for the
time of inactivity via Minutes before lock.
The default values are:
 Auto-lock is not activated
 Minutes before lock is set to 10 minutes (possible values: 1...999 minutes)

Password Request Condition

Open an application (project):

Password Management
When an application file is opened, an Application Password dialog box opens.
Enter the password.
Click OK. If the password is correct, the application opens.
If the password is wrong, a dialog box pops up to indicate it and a new Application
Password dialog box opens.
If you click Cancel, the application is not opened

Unity Pro software auto-lock:

Password Management
When auto-lock time is elapsed, an Application Password dialog box opens:
Enter the password.
Click OK. If the password is correct, Unity Pro becomes active again.
If the password is wrong, a dialog box pops up to indicate it and a new Application
Password dialog box opens.
If you click Close, the application is closed without being saved.

182 33003101 12/2015

 Project browser

CPU application auto-lock:

Password Management
When auto-lock time is elapsed, an Application Password dialog box opens:
Enter the password.
Click OK. If the password is correct, the connection between Unity Pro and the CPU becomes active
again.
If the password is wrong, a dialog box pops up to indicate it and a new Application
Password dialog box opens.
NOTE: The password must be entered to have the connection and the request cannot be
canceled.

CPU connection to Unity Pro:

Password Management
On connection, if Unity Pro software application and the CPU application are not equal, an Application
Password dialog box opens:
Enter the password.
Click OK. If the password is correct, the connection is established.
If the password is wrong, a dialog box pops up to indicate it and a new
Application Password dialog box opens.
If you click Cancel, the connection is not established.
NOTE: On connection, if Unity Pro software application and the CPU applications are equal, there is no
password request. If no password has been initially entered (left empty on project creation), click OK to
establish the connection on password prompt.

NOTE: For each new password request, the elapsed time increases between the wrong password
notification and a new Application Password dialog box prompt (up to 1 hour).
NOTE: In case of password loss, contact Schneider Electric support (see page 190).

33003101 12/2015 183

Project browser

Firmware Protection

Overview
Firmware protection by a password helps prevent unwanted access to the module firmware via
FTP.
NOTE: Firmware password is implemented from Unity Pro V10.0. An application created with
Unity Pro V10.0 cannot be opened with an earlier version of Unity Pro.

Password
The firmware is password protected by default with the following password: fwdownload.
It is possible to change a password at any time.
The password is case-sensitive and contains 8 to 16 alphanumeric characters. The password
robustness is increased when it contains a mix of upper and lower case, alphabetical, numerical,
and special characters.
NOTE: When importing a ZEF file, the firmware password of the module is set to its default value.

Changing the Password

NOTE: Firmware default password: fwdownload
Procedure for changing the firmware protection password:

Step Action
1 In the project browser right-click Project.
2 Select Properties command from the popup menu.
Result: The Properties of Project window appears.
3 Select Protection tab.
4 In the Firmware field, click Change password ....
Result: The Modify Password window appears.
5 Enter previous password in the Old password field.
6 Enter the new password in the Entry field.
7 Enter the confirmation of the new password in the Confirmation field.
8 Click OK to confirm.
9 Click OK or Apply in the Properties of Project window to confirm all changes.
If you click Cancel in the Properties of Project window, all changes are canceled.

184 33003101 12/2015

 Project browser

Resetting the Password

Resetting the password assigns its default value to the firmware password (fwdownload) once
the current password is confirmed. Proceed as follows:

Step Action
1 In the project browser right-click Project.
2 Select Properties command from the popup menu.
Result: The Properties of Project window appears.
3 Select Protection tab.
4 In the Firmware field, click Reset password....
Result: The Password window appears.
5 Enter current password in the Password field.
6 Click OK to confirm.
7 Click OK or Apply in the Properties of Project window to confirm all changes. The new
password is the default password: fwdownload.
If you click Cancel in the Properties of Project window, all changes are canceled.

33003101 12/2015 185

Project browser

Section and Subroutine Protection

At a Glance
The section protection function is accessible from the Properties screen of the project in offline
mode.
This function is used to protect the program sections.
NOTE: The section protection is not active as long as the protection has not been activated in the
project.
NOTE:
The project protection is effective to the marked sections only. This does not prevent from:
 Connecting to the CPU
 Uploading application from the CPU
 Changing the configuration
 Adding new sections
 Changing the logic in a new (not protected) section

Activating Protection and Creating Password

Procedure for activating the protection of sections and creating the password:

Step Action
1 In the project browser right-click Project.
2 Select Properties command from the popup menu.
Result: The Properties of Project window appears.
3 Select Protection tab.
4 In the Sections field, activate the protection by checking the Protection active box.
Result: The Modify Password dialog box appears:
5 Enter a password in the Entry field.
6 Enter the confirmation of the password in the Confirmation field.
7 Select Crypted check box if an enhanced password protection is required.
NOTE: A project with a crypted password cannot be edited with a Unity Pro version lower than 4.1.
8 Click OK to confirm.
9 Click OK or Apply in the Properties of Project window to confirm all changes.
If you click Cancel in the Properties of Project window, all changes are canceled.

Notes
If a section (see page 467) is configured with a protection (read or read/write), when protection has
been activated this will be indicated by a locked padlock at the section level.
If the section is configured with a protection but the protection is disabled, an open padlock is
displayed at the section level.

186 33003101 12/2015

 Project browser

Changing the Password

Procedure for changing the project sections protection password:

Step Action
1 In the project browser right-click Project.
2 Select Properties command from the popup menu.
Result: The Properties of Project window appears.
3 Select Protection tab.
4 In the Sections field, click Change password ....
Result: The Modify Password dialog box appears:
5 Enter previous password in the Old password field.
6 Enter the new password in the Entry field.
7 Enter the confirmation of the new password in the Confirmation field.
8 Select Crypted check box if an enhanced password protection is required.
NOTE: A project with a crypted password cannot be edited with a Unity Pro version lower than 4.1.
9 Click OK to confirm.
10 Click OK or Apply in the Properties of Project window to confirm all changes.
If you click Cancel in the Properties of Project window, all changes are canceled.

Deleting the Password

Procedure for deleting the project sections protection password:

Step Action
1 In the project browser right-click Project.
2 Select Properties command from the popup menu.
Result: The Properties of Project window appears.
3 Select Protection tab.
4 In the Sections field, click Clear password....
Result: The Access control dialog box appears:
5 Enter the previous password in the Password field.
6 Click OK to confirm.
7 Click OK or Apply in the Properties of Project window to confirm all changes.
If you click Cancel in the Properties of Project window, all changes are canceled.

33003101 12/2015 187

Project browser

Data Storage Protection

Overview
Data storage protection by a password helps prevent unwanted access to the data storage zone
of the SD memory card (if a valid card is inserted in the CPU).

Password
The data storage area is password protected by default with the following password:
datadownload.
It is possible to change a password at any time.
The password is case-sensitive and it must have a size from 8 to 16 alphanumeric characters. The
password robustness is increased when it contains a mix of upper and lower case, alphabetical,
numerical, and special characters.
NOTE: When importing a ZEF file, the data storage password of the application is set to its default
value.

Changing the Password

NOTE: Data storage default password: datadownload
Procedure for changing the data storage protection password:

Step Action
1 In the project browser right-click Project.
2 Select Properties command from the popup menu.
Result: The Properties of Project window appears.
3 Select Protection tab.
4 In the Data Storage field, click Change password ....
Result: The Modify Password window appears.
5 Enter previous password in the Old password field.
6 Enter the new password in the Entry field.
7 Enter the confirmation of the new password in the Confirmation field.
8 Click OK to confirm.
9 Click OK or Apply in the Properties of Project window to confirm all changes.
If you click Cancel in the Properties of Project window, all changes are canceled.

188 33003101 12/2015

 Project browser

Resetting the Password

Resetting the password assigns its default value to the data storage password (datadownload)
once the current password is confirmed. Proceed as follows:

Step Action
1 In the project browser right-click Project.
2 Select Properties command from the popup menu.
Result: The Properties of Project window appears.
3 Select Protection tab.
4 In the Data Storage field, click Reset password....
Result: The Password window appears.
5 Enter current password in the Password field.
6 Click OK to confirm.
7 Click OK or Apply in the Properties of Project window to confirm all changes. The new
password is the default password: datadownload.
If you click Cancel in the Properties of Project window, all changes are canceled.

33003101 12/2015 189

Project browser

Loss of Password

Overview
If you forget your password, proceed as indicated in the following procedures and contact
Schneider Electric support.

Unity Pro Application Password

Schneider Electric support needs a number displayed from the Password dialog box reached in
following conditions:
 At open time, select the application and the Password dialog box is displayed.
 At auto-lock time, the Password dialog box is displayed. If you do not remember the password,
select Close. Open the application again and the Password dialog box is displayed.
NOTE: When the application is closed without entering a password after an auto-lock, all
modifications are lost.
Procedure for resetting the application password:

Step Action
1 Condition: The Password dialog box is displayed.
2 Press SHIFT+F2.
Result: A grayed number is displayed in the right side of the Password dialog box.
3 Give this number to Schneider Electric support.
4 Receive the generated password from Schneider Electric support.
NOTE: The password is a temporary password, available as long as you do not modify the
application.
5 Enter this password.
6 Modify the password (old password = password provided by Schneider Electric support).
7 Click Build → Build Changes.
8 Save the application.

190 33003101 12/2015

 Project browser

CPU Application Password

Procedure for resetting the CPU application password if the respective *.STU file is available:

Step Action
1 Open the respective *.STU file.
2 When the password dialog box is displayed press SHIFT+F2.
Result: A grayed number is displayed in the right side of the Password dialog box.
3 Give this number to Schneider Electric support.
4 Receive the generated password from Schneider Electric support.
Note: The password is a temporary password, available as long as you do not modify the
application.
5 Enter this password.
6 Modify the password (old password = password provided by Schneider Electric support).
7 Connect to the PLC.
8 Click Build → Build Changes.
9 Save the application.

Procedure for resetting the CPU application password if the respective *.STU file is not available:

Step Action
1 Condition: At connection time, the Password dialog box is displayed.
2 Press SHIFT+F2.
Result: A grayed number is displayed in the right side of the Password dialog box.
3 Give this number to Schneider Electric support.
4 Receive the generated password from Schneider Electric support.
Note: The password provided by Schneider Electric support is a temporary password, available as
long as you do not modify the application.
5 Enter this password.
6 Upload the application from CPU.
7 Save the application.
8 Modify the password (old password = the one provided by Schneider Electric support).
9 Click Build → Build Changes.
10 Save the application.

33003101 12/2015 191

Project browser

Firmware Password
Schneider Electric support needs a number displayed from the Password dialog box reached in
following condition:
 In Properties of Project → Protection → Firmware field, click Reset password... and the
Password dialog box is displayed.
Procedure for resetting the firmware password:

Step Action
1 Condition: The Password dialog box is displayed.
2 Press SHIFT+F2.
Result: A grayed number is displayed in the right side of the Password dialog box.
3 Give this number to Schneider Electric support.
4 Receive the generated password from Schneider Electric support.
Note: The password is a temporary password, available as long as you do not modify the
application.
5 Enter this password.
6 Modify the password (old password = password provided by Schneider Electric support).
7 Click OK or Apply in the Properties of Project window to confirm all changes.
If you click Cancel in the Properties of Project window, all changes are canceled.

Data Storage Password

Schneider Electric support needs a number displayed from the Password dialog box reached in
following condition:
 In Properties of Project → Protection → Data Storage field, click Reset password... and the
Password dialog box is displayed.
Procedure for resetting the data storage password:

Step Action
1 Condition: The Password dialog box is displayed.
2 Press SHIFT+F2.
Result: A grayed number is displayed in the right side of the Password dialog box.
3 Give this number to Schneider Electric support.
4 Receive the generated password from Schneider Electric support.
Note: The password is a temporary password, available as long as you do not modify the
application.
5 Enter this password.
6 Modify the password (old password = password provided by Schneider Electric support).
7 Click OK or Apply in the Properties of Project window to confirm all changes.
If you click Cancel in the Properties of Project window, all changes are canceled.

192 33003101 12/2015

 Project browser

Section 5.2
Introduction to the various directories of the project browser

Introduction to the various directories of the project

browser

About this sub-chapter

This sub-chapter describes the various directories of the project browser.

What Is in This Section?

This section contains the following topics:
Topic Page
Station Directory 194
Configuration Directory 196
Derived data types (DDT) directory 198
Derived FB (DFB) types directory 199
Variables Directory 200
Motion Directory 202
Communication Directory 204
Program Directory 206
Animation Tables Directory 209
Operator Screens Directory 211
Documentation Directory 213
Conversion Report Directory 214

33003101 12/2015 193

Project browser

Station Directory

At a Glance
The Station directory of the structural view allows you to access the structure of the project and
the associated services.
The following illustration shows the Station directory:

194 33003101 12/2015

 Project browser

Associated services
The Station directory allows you to access the following services, which can be reached via the
contextual menu:

Directory Services
Station Export Project: allows you to access export of the global project (see page 1755).
Properties: allows you to access the properties of the global project.
Configuration allows you to access the hardware configuration (see page 196) and the parameter
settings of the modules.
Derived Data Types allows you to access the DDTs (see page 198).
Derived FB types allows you to access the DFB (see page 199) types.
Variables & FB allows you to access the variables (see page 200) and function block instances.
instances
Motion allows you to access the declaration (see page 202) and configuration of the
servodrives.
Communication allows you to access the configuration of the networks (see page 204).
Program allows you to access the project program (see page 206).
Animation tables allows you to access the animation tables (see page 209).
Operator Screens allows you to access the operator screens (see page 211).
Documentation allows you to access the documentation (see page 213).

33003101 12/2015 195

Project browser

Configuration Directory

At a Glance
The Configuration directory of the structural view of the project allows you to access the hardware
configuration and the parameter settings of the following modules: bus, rack, module.
The following illustration shows an example of a directory tree of the Configuration directory:

Accessible Services
The Configuration directory allows you to access the following services, which can be reached
via the contextual menu:

Directory Services
Configuration Import: used to import the configuration (see page 1732) of the project
inputs/outputs (offline mode only).
Import SIS: used to import the configuration (see page 1391) of a project
created using the SIS Automation tool.
Export: used to export the configuration (see page 1731) of the project
inputs/outputs (offline mode only),
Bus Open: used to access the bus editor, X Bus in the above example.
Go to Bus Master: displays the processor in reverse video in the project
navigator, TSX 57304M in the above example.
Rack Open: used to access the bus editor, TSX RKY 6EX in the above
example.
Module Open: used to access the input/output editor (module settings).

196 33003101 12/2015

 Project browser

Access
From the Configuration directory, you can:
 Configure the PLC rack (see page 1300) with:
 a power supply (see page 1308),
 a processor (see page 1311),
 one or more modules (see page 1314).

 Configure field bus devices (see page 1319),

 Access the configuration of the rack elements:
 Premium (see page 1363) and Quantum (see page 1373) processors,
 modules (see page 1383).

33003101 12/2015 197

Project browser

Derived data types (DDT) directory

At a Glance
The Derived data types (see Unity Pro, Program Languages and Structure, Reference Manual )
directory of the structural view of the project allows you to access the DDT types.
The following illustration shows an example of a directory tree of the Derived data types directory:

Associated services
The Derived Data Types directory allows you to access the following services, which can be
reached via the contextual menu:

Directory Services
Derived Data Types Open: allows you to access the DDT types tab of the data editor (see page 327),
from which you can:
 create (see page 335) a DDT,
 manage (see page 346) a DDT,

Get from Library: allows you read access to one or more DDT types from a library
(see page 293).
Put in Library: used to archive (see page 355) all the DDTs in a library
(see page 293).
Export: allows you to access export of all DDT types (see page 1739).
Import: allows you to access import of one or more DDT types (see page 1740).
DDT Open: allows you to access the DDT in the DDT types tab of the data editor.
(Input, Output, .etc.) Delete: allows you to delete the DDT.
Put in Library: allows you write access to the DDT in a library.
Analyze: allows you to analyze (see page 417) the DDT.
Properties: allows you to access the DDT properties.
Export: allows you to access export of all DDT types (see page 1739).

198 33003101 12/2015

 Project browser

Derived FB (DFB) types directory

At a Glance
The Derived FB types (see Unity Pro, Program Languages and Structure, Reference Manual )
directory of the structural view of the project allows you to access the DFB types.
The following illustration shows an example of a directory tree of the Derived FB types directory:

Associated services
The Derived FB types directory allows you to access the following services, which can be reached
via the contextual menu:

Directory Services
FB Type Open: allows you to access the DFB tab of the data editor (see page 1255).
Get from Library: allows you read access to one or more DFB types from a
library (see page 293).
Put in Library: allows you write access to all DFB types in a library.
Export: allows you to access export of all DFB types (see page 1737) of the
project.
Import: allows you to access import of one or more DFB types (see page 1738).
DFB Type (Counter, etc.) Open: allows you to access the DFB type in the DFB tab of the Data Editor
(see page 1255).
Delete: allows you to delete the DFB type.
Put in Library: allows you write access to the DFB type in a Library
(see page 293).
Analyze: allows you to analyze (see page 417) the DFB type.
Properties: allows you to access the properties (see page 1267) of the DFB
type.
Export: allows you to access export of the DFB type (see page 1737).
Sections New Section: allows you to create a new section (see page 457) in the DFB type.
Section XX Open: allows you to access the section (see page 457) program language editor.
Delete: allows you to delete the section.
Properties: allows you to access the properties (see page 461) of the section.

33003101 12/2015 199

Project browser

Variables Directory

At a Glance
The Variables & FB instances directory of the structural view of the project is used to access the
variables (EDT, (see Unity Pro, Program Languages and Structure, Reference Manual )DDT,
IODDT) (see Unity Pro, Program Languages and Structure, Reference Manual )and the function
block instances(EFB, DFB). (see Unity Pro, Program Languages and Structure, Reference Manual
)
The following illustration shows an example of the Variables & FB instances directory:

Accessible Services
The Variables & FB instances directory allows you access to the following services, which can
be reached via the contextual menu:

Directory Services
Variables & FB instances Open: used to access the variables editor,
Export: used to access the export of all variables
(see page 1741) of the project,
Import: used to access the import of all variables
(see page 1744) of the project.
Elementary variables Open: used to access the tab corresponding to the variables
Derived variables editor,
Decice DDT variables Export: used to access the export of all variables
I/O derived variables (see page 1741) of the family selected (EDT, DFB, etc.) .
Elementary FB instances
Derived FB instances

200 33003101 12/2015

 Project browser

Access
From the Variables & FB instances directory, you can access the different tabs of the data editor:
 Variables tab,
 Create (see page 370) a data instance,
 Create (see page 382) an IODDT type data instance,
 Create (see page 385) a Device DDT type data instance,
 Modify (see page 399) attributes of data instances.

 DDT Types tab,

 Create (see page 335) a data instance,
 Archive (see page 355) DDTs in a library (see page 293),

 Function blocks tab,

 Create (see page 360) a data instance,
 Modify (see page 366) attributes of data instances.

 DFB Types tab,

 Create (see page 1255) a DFB type,
 Configure settings (see page 1256) of a DFB type.

33003101 12/2015 201

Project browser

Motion Directory

At a Glance
The Motion directory of the structural view of the project allows you to access the declaration and
configuration of the servodrives.
When declaring a servodrive, various information is required, such as:
 the name given to the servodrive
 the type of servodrive
 the CANopen address of the servodrive
 the reference of the servodrive
 the version of the servodrive
 the input of variable names associated to the axis.
The following diagram shows an example of a tree structure for the Motion directory:

In this diagram, the name given to the servodrive is ‘Axis_Z’.

A recipe is linked, by default, each time an axis is created. It is possible to create several recipes
(see MFB using Unity Pro, Start-up Guide).

202 33003101 12/2015

 Project browser

Accessible Services
The Motion directory gives you access to the following services, which can be reached via the
contextual menu:

Directory Service
Motion New axis: allows you to create a new axis.
Axis New recipe: allows you to create a new recipe.
Delete: allows you to delete an axis.
Properties: allows you to access the axis properties.
Recipe Delete: allows you to delete a recipe.
Properties: allows you to access the recipe properties.

33003101 12/2015 203

Project browser

Communication Directory

At a Glance
The Communication directory of the structural view of the project allows you to access the
configuration of the networks.
The following illustration shows an example of a directory tree of the Communication directory:

204 33003101 12/2015

 Project browser

Associated services
The Communication directory allows you to access the following services, which can be reached
via the contextual menu:

Directory Services
Communication Export: allows you to access export of all networks
(see page 1745).
Import: allows you to access import of one or more networks
(see page 1746).
Network New Network: allows you to add a network (see page 427) to
your project.
Network Open: allows you to access the corresponding network editor:
(Network_1, Modbus Ethernet, Modbus Plus, Fipway.
Plus_A, etc.) Export: allows you to access export of one network
(see page 1745).
Delete: allows you to delete a network.
Properties: allows you to access the network properties.
Routing Table Open: allows you to access the configuration (see page 435) of
a bridge between 2 networks (routing tables).

33003101 12/2015 205

Project browser

Program Directory

At a Glance
The Program directory of the structural view of the project allows you to define the structure of the
program (see Unity Pro, Program Languages and Structure, Reference Manual ) and to access the
language editors of the program (see Unity Pro, Program Languages and Structure, Reference
Manual ) elements: sections, program modules and event processing.
The following illustration shows an example of a directory tree of the Program directory:

206 33003101 12/2015

 Project browser

Services associated with the sequential tasks directories.

The sequential tasks (see Unity Pro, Program Languages and Structure, Reference Manual )
directories (Tasks, MAST, FAST, etc.) allow you to access the following services, which can be
reached via the contextual menu:

Directory Services
Tasks New Task: allows you to create a new sequential task (see page 454) (FAST, AUX,
AUX0, AUX1). The MAST task is created by default.
Import: allows you to access import of sections (see page 1735) and/or program
modules of a sequential task.
MAST, FAST, etc. Delete: allows you to delete the task. The MAST task cannot be deleted.
Clear: allows you to clear the contents of the task. This clears all the sections of the
task.
Export: allows you to access export of the sequential tasks (see page 1733).
Properties: allows you to access the properties of the sequential task.

Services associated with the sections directories

The sections (see Unity Pro, Program Languages and Structure, Reference Manual ) directories
allow you to access the following services, which can be reached via the contextual menu:

Directory Services
Sections New Section: allows you to create a new "empty" section (see page 457).
Import: allows you to access import of sections (see page 1735).
Create section activation conditions table: allows you to initialize an animation
table, with the activation condition variables associated with the sections.
For each section Open: allows you to access the section (see page 457) language editor.
Delete: allows you to delete the section.
Detach: allows you to detach the section of the functional module.
Export: allows you to access export of sections (see page 1733).
Forcing to 0, allows you to choose Force to 0 as the activation condition of the section
(in online mode).
Forcing to 1, allows you to choose Force to 1 as the activation condition of the section
(in online mode).
Unforce: allows you to choose cancel forcing as the activation condition of the
section.
Properties: allows you to access the properties of the section (in online mode).
For each Section Open: allows you to access the section language editor.
Macro-step, action,
or transition

NOTE: Only the MAST task can contain one or more sections in SFC language.

33003101 12/2015 207

Project browser

Services associated with the program modules directories

The program modules directories (SR Sections) (see Unity Pro, Program Languages and
Structure, Reference Manual )allow you to access the following services, which can be reached
via the contextual menu:

Directory Services
SR Sections New SR Section: allows you to create a new "empty" program module
(see page 481).
Import: allows you to access import of program module (see page 1735).
For each program Open: allows you to access the program module language editor.
module Delete: allows you to delete the program module.
Export: allows you to access export program module (see page 1733).
Properties: allows you to access the properties of the program module.

Services associated with the event processing directories

The event processing (see Unity Pro, Program Languages and Structure, Reference Manual
)directories allow you to access the following services, which can be reached via the contextual
menu:

Directory Services
Timer Events, I/O New Event Section: allows you to create a new "empty" event processing
Events (see page 486).
Import: allows you to access import of event processing (see page 1735).
For each event Open: allows you to access the event processing language editor.
processing Delete: allows you to delete the event processing.
Detach: allows you to detach the event processing of the functional module.
Export: allows you to access export of event processing (see page 1733).
Properties: allows you to access the event processing properties.

208 33003101 12/2015

 Project browser

Animation Tables Directory

At a Glance
The Animation Tables Directory of the structural view of the project allows you to access the
animation tables.
The following illustration shows an example of a directory tree of the Animation Tables directory:

33003101 12/2015 209

Project browser

Associated services
The Animation Tables directory allows you to access the following services, which can be
reached via the contextual menu:

Directory Services
Animation tables New Animation Table: allows you to create a new animation table
(see page 1494).
Paste: used to paste an animation table into the clipboard or the
animation tables directory.
Delete all: allows you to delete all the animation tables.
Detach all: allows you to detach all the animation tables from the
functional modules.
Export: allows you to access export of all animation tables
(see page 1750).
Import: allows you to access import of one or more animation tables
(see page 1751).
Make All Tables Permanent: allows you to change all temporary
animation tables to permanent animation tables (see also Permanent
and Temporary Animation Tables, page 1492).
Purge Temporary Tables: allows you to delete all temporary
animation tables (see also Permanent and Temporary Animation
Tables, page 1492).
Open Forced Bits Table: allows you to create the animation table
that includes all forced bits of a project (see also Animation Table of
Forced Bits, page 1521).
For each animation Open: allows you to access the animation table.
table Copy: allows you to duplicate an animation table.
Paste: allows you to add a copy of an animation table to the clipboard
or the animation tables directory.
Delete: allows you to delete the animation table.
Detach: allows you to Detach the animation table from the functional
module.
Export: allows you to access export of the animation table
(see page 1750).
Properties: allows you to access the animation table properties.

Access
The Animation Tables Directory is used to create an animation table. From this table, you can:
 add (see page 1502) data,
 switch to modification (see page 1507) mode,
 switch to forcing (see page 1512) mode,
 modify or force (see page 1518) several variables.

210 33003101 12/2015

 Project browser

Operator Screens Directory

At a Glance
The Operator Screens Directory of the structural view of the project are used to access the
operator screens.
The following diagram shows an example of a directory tree of the Operator Screens directory:

33003101 12/2015 211

Project browser

Associated services
The Operator Screens directory allows you to access the following services, which can be
reached via the contextual menu:

Directory Services
Operator Screens New screen: allows you to create a new operator screen.
New family: allows you to create a new family of screens.
Paste: allows you to paste an operator screen into the clipboard or the operator
screen directory.
Delete all: allows you to delete all the operator screens.
Detach all: allows you to detach all the operator screens from the functional
modules.
Clean unuse image: allows you delete all the created images that are not used.
Import: allows you to access import of one or several screens (see page 1749)
and/or family of screens.
Export: allows you to access export of all screens (see page 1747).
Messages list: allows you to access the message list for the operator screens.
For each family of New screen: allows you to create a new operator screen.
screens Copy: allows you to duplicate the family of screens and its associated operator
screens.
Paste: allows you to add a copy of a screen family and its operator screens to the
clipboard or the operator screens directory.
Delete: allows you to delete the family of screens.
Detach: allows you to detach the functional module family.
Export: allows you to access export of the family of screens (see page 1747).
Family Properties: allows you to access the properties of the family of screens.
For each operator Open: allows you to access the operator screens editor.
screen Copy: allows you to duplicate the operator screen.
Paste: allows you to add a copy of an operator screen to the clipboard or the
operator screen directory.
Delete: allows you to delete the operator screen.
Detach: allows you to detach the operator screen from the functional module.
Export: allows you to access export of the operator screen (see page 1747).
Screen properties: allows you to access the properties of the operator screen.

Access
The Operator Screens directory is used to create screens. From these screens, you can:
 create (see page 1602) objects,
 insert objects from a library (see page 1680),
 modify the attributes (see page 1616) of the objects,
 manipulate (see page 1645) the objects that make up the screen,
 use the screens in online mode (see page 1667).

212 33003101 12/2015

 Project browser

Documentation Directory

At a Glance
The Documentation directory of the structural view of the project allows you to access the
documentation.
The following illustration shows an example of a Documentation directory:

Associated services
The Documentation directory allows you to access the following services, which can be reached
via the contextual menu:

Directory Services
Documentation Open: allows you to access the documentation (see page 1695) tool.
Title Page Print Configuration: also gives access to the print configuration
settings.
General information Open: this heading allows you to specify various information about
the project. A dialog box allows you to enter the information and to
create hyperlinks (see page 1874).

33003101 12/2015 213

Project browser

Conversion Report Directory

At a Glance
The Conversion Report directory is displayed in the structural view of the project when opening
a PL7 (see Unity Pro, PL7 Application Converter, User Manual) project with a .FEF extension or a
Concept (see Unity Pro, Concept Application Converter, User Manual) project with an .ASC
extension. This directory enables you to access a conversion report for a project.
The following illustration shows an example of a directory tree of the Conversion Report directory:

Services
The Conversion Report directory provides you with:
 general information (application name, source file, PLC type, etc.),
 warnings,
 errors.

214 33003101 12/2015

 Project browser

Section 5.3
Summaries of the utilities associated with the structure view and function view

Summaries of the utilities associated with the structure

view and function view

Summary of the services associated with the structural view

At a Glance
The following tables summarize the services associated with the structural view of the project and
indicate the operating modes in which you can use them.

Station Directory
The Station directory (see page 194) allows you to access the following services.

Directory Services Mode

Off-line On-line On-line
Stop Run
Station Export Project Yes No No
Properties Yes Yes Yes

Configuration Directory
The Configuration directory (see page 196) allows you to access the following services.

Directory Services Mode

Off-line On-line On-line
Stop Run
Configuration Export Yes No No
Import Yes No No
Import SIS Yes No No
Bus Open Yes Yes Yes
Go to Bus Master Yes Yes Yes
Rack Open Yes Yes Yes
Module Open Yes Yes Yes

33003101 12/2015 215

Project browser

Derived FB Types Directory

The Derived FB Types directory (see page 199) allows you to access the following services.

Directory Services Mode

Off-line On-line On-line
Stop Run
FB Type Open Yes Yes Yes
Export Yes No No
Import Yes No No
Put in Library Yes No No
Get from Library Yes No No
For each type of Open Yes Yes Yes
DFB Export Yes No No
Put in Library Yes No No
Delete Yes (1) Yes (1) Yes (1)
Analyze Yes Yes Yes
Properties Yes Yes Yes
Section Open Yes Yes Yes
Delete Yes No No
Properties Yes Yes Yes

(1) Only if the DFB type is not instantiated in the project.

Derived Data Types Directory

The Derived Data Types directory (see page 198) allows you to access the following services.

Directory Services Mode

Off-line On-line On-line
Stop Run
Derived Data Open Yes Yes Yes
Types Export Yes No No
Import Yes No No
Put in Library Yes No No
Get from Library Yes No No
For each DDT Open Yes Yes Yes
Export Yes Yes No
Put in Library Yes No No
Delete Yes (1) Yes (1) Yes (1)
Analyze Yes Yes Yes
Properties Yes Yes Yes

(1) Only if the DDT type is not instantiated in the project.

216 33003101 12/2015

 Project browser

Variables & FB instances Directory

The Variables & FB instances directory (see page 200) allows you to access the following
services.

Directory Services Mode

Off-line On-line On-line
Stop Run
Variables Open Yes Yes Yes
Export Yes No No
Import Yes No No
EDT, DDT, EFB, DFB Open Yes Yes Yes
Export Yes No No

Motion Directory
The Motion directory (see page 200) allows you to access the following services.

Directory Services Mode

Off-line On-line On-line
Stop Run
Motion New axis Yes No No
Axis New recipe Yes No No
Delete Yes No No
Properties Yes Yes Yes
Recipe Delete Yes No No
Properties Yes Yes Yes

Communication Directory
The Communication directory (see page 204) allows you to access the following services.

Directory Services Mode

Off-line On-line On-line
Stop Run
Communication Export Yes No No
Import Yes No No
Network New Network Yes No No
For each network Open Yes Yes Yes
Export Yes Yes Yes
Delete Yes Yes Yes
Properties Yes Yes Yes
Routing Table Open Yes Yes Yes

33003101 12/2015 217

Project browser

Program Directory
The Program directory (see page 206) allows you to access the following services.

Directory Services Mode

Off-line On-line On-line
Stop Run
Tasks New Task Yes No No
Import Yes No No
MAST Clear Yes Yes No
FAST Delete Yes (1) No No
Export Yes No No
Properties Yes Yes Yes
Sections New Section Yes Yes Yes
Create section activation conditions Yes Yes Yes
table Yes No No
Import
For each section Open Yes Yes Yes
Delete Yes Yes Yes
Detach Yes Yes Yes
Export Yes No No
Force to 0 No Yes Yes
Force to 1 No Yes Yes
Unforce No Yes Yes
Properties Yes Yes Yes
SR Sections New SR Section Yes Yes Yes
Import Yes No No
For each Open Yes Yes Yes
program module Delete Yes (2) Yes (2) Yes (2)
Export Yes No No
Properties Yes Yes Yes
Timer Events, I/O New Event Section Yes Yes Yes
Events Import Yes No No
For each event Open Yes Yes Yes
processing Delete Yes (2) No No
Detach Yes Yes Yes
Export Yes No No
Properties Yes Yes Yes

(1) Except for MAST task.

(2) Only if the program module or the event processing is not called.

218 33003101 12/2015

 Project browser

Animation tables Directory

The Animation tables directory (see page 209) allows you to access the following services.

Directory Services Mode

Off-line On-line On-line
Stop Run
Animation tables New Animation Table Yes Yes Yes
Paste Yes Yes Yes
Detach All Yes Yes Yes
Delete All Yes Yes Yes
Import Yes No No
Export Yes No No
Make All Tables Permanent Yes Yes Yes
Purge Temporary Tables Yes Yes Yes
Open Forced Bits Table No Yes Yes
For each Open Yes Yes Yes
animation table Copy Yes Yes Yes
Paste Yes Yes Yes
Export Yes No No
Delete Yes Yes Yes
Detach Yes Yes Yes
Properties Yes Yes Yes

Operator Screens Directory

The Operator Screens directory (see page 211) allows you to access the following services.

Directory Services Mode

Off-line On-line On-line
Stop Run
Operator New screen Yes Yes Yes
Screens New family Yes Yes Yes
Detach All Yes Yes Yes
Delete All Yes Yes Yes
Export Yes No No
Import Yes No No
Messages list Yes Yes Yes
For each family of New screen Yes Yes Yes
screens Copy Yes Yes Yes
Paste Yes Yes Yes
Delete Yes Yes Yes
Detach Yes Yes Yes
Export Yes No No
Family Properties Yes Yes Yes

33003101 12/2015 219

Project browser

Directory Services Mode

Off-line On-line On-line
Stop Run
For each screen Open Yes Yes Yes
Copy Yes Yes Yes
Paste Yes Yes Yes
Delete Yes Yes Yes
Detach Yes Yes Yes
Export Yes No No
Screen properties Yes Yes Yes

Documentation Directory
The Documentation directory (see page 213) allows you to access the following services.

Directory Services Mode

Off-line On-line On-line
Stop Run
Documentation Open Yes Yes Yes
Title Page Print Setup Yes Yes Yes
General Open Yes Yes Yes
Information

220 33003101 12/2015

 Unity Pro
Functional modules
33003101 12/2015

Chapter 6
Functional modules

Functional modules

Aim of this Chapter

This chapter introduces the functional modules incorporated in a Unity Pro project.

What Is in This Chapter?

This chapter contains the following sections:
Section Topic Page
6.1 Introduction to the functional view 222
6.2 The functional modules and their associated utilities 234

33003101 12/2015 221

Functional modules

Section 6.1
Introduction to the functional view

Introduction to the functional view

About this sub-chapter

This sub-chapter provides general information on the functional modules and their associated
utilities.

What Is in This Section?

This section contains the following topics:
Topic Page
Functional modules 223
Station directory of the functional view 225
Functional Module Directory 226
Functional Module Program Directory 228
Functional Module Animation Tables Directory 229
Functional Module Operator Screens Directory 230
Summary of the services associated with the functional view 231

222 33003101 12/2015

 Functional modules

Functional modules

Definition
A functional module is a group of program elements intended to perform a PLC function.
A functional module is comprised:
 program or event processing sections,
 animation tables associated with the functional module,
 runtime screens associated with the functional module,
 a comment (max. 1024 characters),
 interleaved functional modules, with these modules, in relation to the main function, performing
one or more PLC sub-functions.
NOTE: a functional module does not necessarily have a program section, an animation table or
runtime screens.
The other elements that make up a project are not incorporated into the functional modules:
 the configuration,
 the global variables of a project,
 the DFB and DDT types, which are global to a project,
 the SRi program modules, which are global to a task,
 the documentation.

33003101 12/2015 223

Functional modules

At a glance
All the functional modules of the project can be found in the Functional Station directory of the
function view.
The following illustration shows the Functional Station directory:

As the default the browser displays the first level of the directory tree. To access the other levels,
you need to expand the directories.
NOTE: This breakdown does not take into account the order of execution of the program by the
PLC.

224 33003101 12/2015

 Functional modules

Station directory of the functional view

At a Glance
The Functional Station directory of the functional view allows you to access all the functional
modules of the project and the associated services.
The following illustration shows the Functional Station directory:

Associated services
The Functional Station directory allows you to access the following services, which can be
reached via the contextual menu:

Directory Services
Functional station New Functional Module: allows you to create a new functional
module.
Detach all: allows you to detach all elements included in the
functional modules (sections and animation tables) without deleting
them.
Export: allows you to access export of the global project
(see page 1755).
Import: allows you to access import of a functional module
(see page 1754).
Properties: allows you to access the properties of the global
project.
For each functional allows you to access all the elements of the functional module:
module program, animation tables, operator screens, nested functional
modules.

33003101 12/2015 225

Functional modules

Functional Module Directory

At a Glance
The Functional Module directory of the functional view allows you to access all the elements of a
functional module (program, animation tables and operator screens) and the nested modules.
The following illustration shows an example of a Functional Module directory:

226 33003101 12/2015

 Functional modules

Associated services
The functional module directory allows you to access the following services, which can be
reached via the contextual menu:

Directory Services
Functional module: New Functional Module: allows you to create a new nested
Factory1 functional module.
Create: allows you to create a new program element in the functional
module: section, program module or event processing.
Delete: allows you to delete the functional module.
Detach all: allows you to detach all elements included in the
functional module (sections and animation tables) without deleting
them.
Export: allows you to access export of the functional module
(see page 1752).
Import: allows you to access import of a functional module
(see page 1754).
Create section activation conditions table/CTRL+T: allows you to
initialize an animation table, with the activation conditions associated
with the program elements of the functional module (sections,
program modules and event processings).
Protection of Included Sections: allows you to define the protection
of the program elements (sections, program modules and event
processings) of the function module (no protection, write-protection,
read/write-protection).
Properties: allows you to access the functional module properties.
Program allows you to access the functional module programs (see page 228).
Table allows you to access the animation tables of the functional module
(see page 229).
Screen allows you to access the operator screens of the functional module
(see page 230).

33003101 12/2015 227

Functional modules

Functional Module Program Directory

At a Glance
The Program Directory of a functional module allows you to access the program elements of this
module: sections, (see Unity Pro, Program Languages and Structure, Reference Manual )program
modules and event processing. (see Unity Pro, Program Languages and Structure, Reference
Manual )

Associated services
The Program directory of a functional module allows you to access the following services, which
can be reached via the contextual menu:

Directory Services
Program Create: allows you to create a new program element in the functional
module: section, program module or event processing.
Detach all: allows you to detach all elements included in the functional
module (sections and animation tables) without deleting them.
Import: allows you to access import program elements of the
functional module: sections, program modules, event processing (see
also topic on program import (see page 1735)).
Create section activation conditions table/CTRL+T: allows you to
initialize an animation table, with the activation conditions associated
with the program elements of the functional module: sections.
Protection of Included Sections: allows you to define the protection
of the program elements of the functional module: sections, program
modules and event processing.
Section, SR section, See Program Directory, page 206 for a description of the associated
event processing services.

228 33003101 12/2015

 Functional modules

Functional Module Animation Tables Directory

At a Glance
The Table directory of a functional module allows you to access the animation tables of this
module.

Associated services
The Table directory of a functional module allows you to access the following services, which can
be reached via the contextual menu:

Directory Services
Table New Animation Table: allows you to create a new animation table.
Detach all: allows you to detach all the animation tables from the
functional module, without deleting them.
Import: allows you to access import of the animation tables
(see page 1751) in the functional module.
For each animation Open: allows you to access the animation table.
table Copy: allows you to duplicate the animation table.
Paste: allows you to add a copy of an animation table into the
animation tables directory in the functional module and the project
browser.
Export: allows you to access export of the animation table
(see page 1750).
Delete: allows you to delete the animation table.
Detach: allows you to detach the animation table from the functional
module, without deleting it.
Properties: allows you to access the animation table properties.

33003101 12/2015 229

Functional modules

Functional Module Operator Screens Directory

At a Glance
The Screen directory of a functional module allows you to access the operator screens of this
module.

Associated services
The Screen directory of a functional module allows you to access the following services, which can
be reached via the contextual menu:

Directory Services
Screen Import: allows you to access import of one or more screens
(see page 1749) and/or families of screens.
New family: allows you to create a new family of screens.
New screen: allows you to create a new operator screen.
Detach all: allows you to detach all the screen elements from the
functional module, without deleting them.
For each family of See Operator Screens Directory, page 211 for a description of the
screens screen families services.
For each operator See Operator Screens Directory, page 211 for a description of the
screen services available from the screen.

230 33003101 12/2015

 Functional modules

Summary of the services associated with the functional view

At a Glance
The following tables summarize the services associated with the functional view of the project and
indicate the operating modes in which you can use them.

Functional Station Directory

The Functional Station directory (see page 225) allows you to access the following services.

Directory Services Mode

Off-line On-line On-line
Stop Run
Functional New Functional Module Yes Yes Yes
Station Detach All Yes Yes Yes
Export Yes No No
Import Yes No No
Properties Yes Yes Yes

Functional Module Directory

The Functional Module directory (see page 226) allows you to access the following services.

Directory Services Mode

Off-line On-line On-line
Stop Run
For each New Functional Module Yes Yes Yes
functional Detach All Yes Yes Yes
module Create Yes Yes Yes
Delete Yes Yes Yes
Export Yes No No
Import Yes No No
Protection of Included Sections Yes Yes Yes
Create section activation conditions Yes Yes Yes
table Yes Yes Yes
Properties

33003101 12/2015 231

Functional modules

Functional Module Program Directory

The Program directory (see page 228) of a functional module allows you to access the following
services.

Directory Services Mode

Off-line On-line On-line
Stop Run
Program Create Yes Yes Yes
Import Yes No No
Detach All Yes Yes Yes
Protection of Included Sections Yes Yes Yes
Create section activation conditions Yes Yes Yes
table
For each section, Open Yes Yes Yes
SR sections, Detach Yes Yes Yes
event processing Delete Yes Yes Yes
Export Yes No No
Force to 0 No Yes Yes
Force to 1 No Yes Yes
Unforce No Yes Yes
Properties Yes Yes Yes

Functional Module Animation Tables Directory

The Table directory (see page 229) of a functional module allows you to access the following
services.

Directory Services Mode

Off-line On-line On-line
Stop Run
Table New Animation Table Yes Yes Yes
Import Yes No No
Detach All Yes Yes Yes
For each Open Yes Yes Yes
animation table Export Yes No No
Delete Yes Yes Yes
Copy Yes Yes Yes
Paste Yes Yes Yes
Properties Yes Yes Yes
Detach Yes Yes Yes

232 33003101 12/2015

 Functional modules

Functional Module Operator Screens Directory

The Screen directory (see page 230) of a functional module allows you to access the following
services.

Directory Services Mode

Off-line On-line On-line
Stop Run
Screen New family Yes Yes Yes
New screen Yes No No
Import Yes No No
Detach All Yes Yes Yes
For each family of New screen Yes Yes Yes
screens Copy Yes Yes Yes
Paste Yes Yes Yes
Delete Yes Yes Yes
Export Yes No No
Detach Yes Yes Yes
Family Properties Yes Yes Yes
For each Open Yes Yes Yes
operator screen Copy Yes Yes Yes
Paste Yes Yes Yes
Export Yes No No
Detach Yes Yes Yes
Delete Yes Yes Yes
Screen properties Yes Yes Yes

33003101 12/2015 233

Functional modules

Section 6.2
The functional modules and their associated utilities

The functional modules and their associated utilities

About this sub-chapter

This sub-chapter is a guide on how to use the utilities associated with the functional modules.

What Is in This Section?

This section contains the following topics:
Topic Page
Properties of a functional module 235
Creating a functional module 236
Programming a functional module 237
Protecting program elements of the functional module 239
Debugging a functional module 240
Detaching/Deleting a functional module 241
Functional module export 245
Functional module import 246
Creating, Deleting, Locating, Dragging-and-Dropping an Animation Table in a Functional 247
Module
Creating, Deleting, Locating and Dragging-and-Dropping an Operator Screen in a Functional 250
Module

234 33003101 12/2015

 Functional modules

Properties of a functional module

Properties to define
List of different properties to define:
 the name comprising 32 characters. This name must be unique for modules positioned on the
same level.
 the definition of the activation conditions of the program elements (sections, program modules
and event processings) of the functional module (Force to 0, Force to 1, cancel forcing),
 the protection of the program elements (sections, program modules and event processings) of
the functional module (no protection, write-protection, read/write-protection),
 the comment comprising 256 characters.

Displaying or editing properties

Carry out the following steps:

Step Action
1 In the functional view, right-click the functional module, in the Functional
Station directory.
2 Click Properties.
3 Perform the editing.
4 Confirm with OK.

NOTE: The Apply button confirms the editing without closing the window.

33003101 12/2015 235

Functional modules

Creating a functional module

At a Glance
A functional module can be created off-line, with the PLC at Stop or in Run.
It can be created at the Station level or at the level of each existing functional module.

Creating a new functional module

Carry out the following actions:

Step Action
1 In the functional view, right-click the Functional Station directory.
2 Select New Functional Module.
3 Enter the name and comment and confirm with OK.

Creating a lower level functional module

Carry out the following actions:

Step Action
1 In the functional view, right-click the module "above", in the Functional Station
directory.
2 Select New Functional Module.
3 Enter the name and comment and confirm with OK.

Moving a functional module

A functional module can be moved off-line, with the PLC at Stop or in Run (this has no effect on
the execution of the project). The movement corresponds only to a modification of the functional
architecture of the project (a module is directly attached to the Functional Station directory level
or to another functional module).
Moving a functional module:

Step Action
1 Left-click on the module to be moved (holding down the mouse button),
2 Move the module to the desired position.

236 33003101 12/2015

 Functional modules

Programming a functional module

Introduction to programming a functional module

A functional module has a program directory that may contain:
 LD, ST, IL sections (see Unity Pro, Program Languages and Structure, Reference Manual )
 event processing (see Unity Pro, Program Languages and Structure, Reference Manual )
 SFC sections (see Unity Pro, Program Languages and Structure, Reference Manual )

Various cases may arise when programming a functional module:

 Case 1: the section, event processing or SFC section already exists in the structural view
 Case 2: creating the section or event processing using the functional view
 Case 3: importing a section using the functional view

Case 1: the section, event processing or chart already exists in the structural view
The section has already been created in the structural view:

Step Action
1 Select the section.
2 Move the section to the functional module.

Case 2: creating the section or event processing using the functional view
The following table shows how to create a section:

Step Action
1 In the Functional view, right-click the Program directory in the Functional
Station directory.
2 Select the Create command from the contextual menu.
3 Select either New Section or New Event.
4 Enter the various headings in exactly the same way as for creating a section
from the structural view. The name of the functional module is shown again at
the structural view level.

33003101 12/2015 237

Functional modules

Case 3: importing a section using the functional view

The following table shows how to import a section:

Step Action
1 In the Functional view, right-click the Program directory in the Functional
Station directory.
2 Select the Import command from the contextual menu.
3 In the Import dialog select the file to be imported.
4 Click on the Import button to finish the import.

When using the functional view to import a section that does not have its task in the importing
application, the section is attached to the MAST task.

WARNING
UNEXPECTED APPLICATION BEHAVIOR
Verify that an imported section operates correctly while attached to the MAST task if it was
originally running in a non-MAST task.
Failure to follow these instructions can result in death, serious injury, or equipment
damage.

Rules
Take into account the following notes:

1 An SFC section can only be created off-line and then only in the Mast task.
2 A macro-step or an event can only be created off-line.
3 The other actions are authorized in off-line mode, with the PLC at Stop or in Run.
4 The protection of a module applies to all the sections attached to the functional
module and to the lower level modules.

238 33003101 12/2015

 Functional modules

Protecting program elements of the functional module

At a Glance
In a functional module you are able to define the protection (see page 186) of the program
elements (sections, program modules and event processings) contained in the module.

Protection
Procedure:

Select from Then...

the functional module  with the mouse right-click the Program directory in a functional
module of the functional view,
 select Protection of Included Sections,
 select Write or Read/Write.

Result: All the program elements of the module and of the lower
module(s) are protected.
from the Program  with the mouse right-click on the Program directory in a
directory functional module of the functional view,
 select Protection of Included Sections,

 select Write or Read/Write.

Result: All the program elements of the module are protected.

33003101 12/2015 239

Functional modules

Debugging a functional module

At a Glance
The organization of a functional module, and the distribution of the sections, event processing and
SFC sections in the various modules has no impact on the execution of the program. The program
is executed in the order shown in the structural view. To help you debug a functional view, the
following are available:
 basic debugging functions,
 the animation table initialization function.

Initializing an animation table

This action allows you to initialize an animation table, with the activation conditions associated with
the program elements of the functional module (sections, program modules and event processing).

Select from Then...

the functional module  right-click with the mouse on the directory of a functional module
in the functional view.
 select Create section activation conditions table.

from the Program  with the mouse right-click on the Program directory in a
directory functional module of the functional view.
 select Create section activation conditions table.

NOTE: All the activation conditions that are displayed in the animation table are theconditions used
during the last build (partial or total).

240 33003101 12/2015

 Functional modules

Detaching/Deleting a functional module

At a Glance
Detaching elements from a functional module consists of cutting the links between a functional
module and the associated elements (program elements, animation table and screen).
 the sections contained in the module are not deleted, they are merely detached,
 the animation tables associated with the modules are not deleted, they are merely detached
from the module,
 the screens associated with the modules are not deleted, they are merely detached from the
module.
NOTE: These actions are authorized off-line and on-line, with PLC at Stop or in Run.

Detaching Functional Modules

To detach functional modules carry out the following actions:

Step Action
1 Select the Functional Station directory.
2 Select Detach All from the contextual menu.
3 Confirm with Yes.

Detaching a functional module

To detach a functional module carry out the following actions:

Step Action
1 Select the functional module from the Functional Station directory.
2 Select Detach All from the contextual menu.
3 Confirm with Yes.

Detaching all the elements in a directory from a functional module

To detach all the elements in a directory (Program, Table, Screen) from a functional module, you
must do the following:

Step Action
1 Select the Program or Table or Screen directory from the functional module.
2 Select the Detach All command from the contextual menu.
Result: All the elements in the chosen directory are detached from the
functional module.

33003101 12/2015 241

Functional modules

Detaching one element in a directory from a functional module

To detach one element in a directory (Program, Table, Screen) from a functional module, you must
do the following:

Step Action
1 Select the element to be detached in the Program or Table or Screen
directory.
2 SelectDetach from the contextual menu.
Result: The element in the chosen directory is detached from the functional
module.

Introduction to deleting a functional module

Deletion can be carried out in a number of ways:
 deleting one or more functional modules without deleting the program elements, animation
tables and screens,
 deleting one functional module with deletion of the program elements, animation tables and
screens,
 deleting all the functional modules with deletion of the program elements, animation tables and
screens,
 deleting one section, a macro-step or an event processing in a functional module.

Deleting one or more functional modules without deleting the program elements, animation tables
and screens
To delete a functional module without deleting the program elements and animation tables, you
must proceed as follows:

Step Action
1 From the functional module, detach the module with the Detach all command
in the contextual menu.
Result: All the elements of the module and the lower level modules are
detached.
2 Delete the module(s) by right-clicking (contextual menu) and selecting the
Delete command.
Note: You must be in off-line mode.

242 33003101 12/2015

 Functional modules

Deleting one functional module with deletion of the modules, animation tables and screens

CAUTION
UNEXPECTED APPLICATION BEHAVIOR - MODULE DELETION
Before deleting a module, ensure that the deletion of the subsequent elements:
 the sub-modules contained in the module,
 the sections contained in the module,
 the associated animation tables,
 the associated screens,

has no adverse consequence on the application behavior.

Failure to follow these instructions can result in injury or equipment damage.

Carry out the following actions:

Step Action
1 Select the module.
2 Select Delete.
3 Confirm with Yes.

NOTE: This action is authorized for the SFC sections and the events in off-line mode, with the PLC
at Stop. The other elements may be deleted in Run.

Deleting a section or an event in a functional module

CAUTION
UNEXPECTED APPLICATION BEHAVIOR - SECTION DELETION
A section or an event may be deleted in a functional module. They are then deleted in the module
and in the associated task.
Failure to follow these instructions can result in injury or equipment damage.

Carry out the following actions:

Step Action
1 Select the desired section or event.
2 Select Delete.
3 Confirm with Yes.

33003101 12/2015 243

Functional modules

Rules
Take into account the following rules:

1 In order not to delete the contents of a module, you must detach its elements
before deleting.
2 An SFC section or an event can only be deleted in off-line mode.

244 33003101 12/2015

 Functional modules

Functional module export

Exporting a functional module

You can export (see page 1752) a functional module.

33003101 12/2015 245

Functional modules

Functional module import

Importing a functional module

You can import (see page 1754) a functional module.

246 33003101 12/2015

 Functional modules

Creating, Deleting, Locating, Dragging-and-Dropping an Animation Table in a

Functional Module

At a Glance
In a functional module you are able to create, delete, locate and drag-and-drop an animation table.

Creating an Animation Table

Procedure:

If the table Then...

already exists  select the animation table in the Functional Station directory of
the functional view or the Animation tables directory of the
structural view,
 drop the animation table to a functional module in the Table
directory level.
must be created from  with the mouse right-click the Table directory of the module,
the functional view
 select New Animation Table.

Accessing the Properties of an Animation Table

Carry out the following actions:

Step Action
1 Select the table.
2 Select Properties from the contextual menu.
3 You can edit the name or the comment of a table and its assignment to a module.

Copying an Animation Table.

Procedure:

If the table Then...

must be copied from the  with the mouse right-click the source table in the Functional
functional view. Station directory of the functional view,
 select Copy,

 select the source table in the Functional Station directory of

the functional view,
 select Paste.

Result: The copy of the table is created in the source table

directory.

33003101 12/2015 247

Functional modules

Opening an Animation Table

Carry out the following actions:

Step Action
1 Select the table.
2 Select Open from the contextual menu.

Deleting an Animation Table

Carry out the following actions:

Step Action
1 Select the table.
2 Select Delete from the contextual menu.

Moving an Animation Table

Procedure:

If using Then...
the drag-and-drop  left-click on the table to be moved (holding down the mouse
function button),
 drop the table at the desired position.

Note: The insertion point of the table is represented by a line.

Properties from the  select the table,
contextual menu
 select Properties from the contextual menu,

 select the name of the module in the Functional Module zone.

Detach all Animation Tables

Procedure:

If using the Then...

contextual menu
Detach all  select the Table directory of the functional module,

 select Detach All from the contextual menu,

 confirm with Yes.

248 33003101 12/2015

 Functional modules

Detaching an Animation Table

Procedure:

If using the Then...

contextual menu
Detach  select the animation table,

 select Detach from the contextual menu,

 confirm with Yes.

Properties  select the table,

 select Properties from the contextual menu,

 select "none" in the Functional Module zone.

33003101 12/2015 249

Functional modules

Creating, Deleting, Locating and Dragging-and-Dropping an Operator Screen in

a Functional Module

At a Glance
In a functional module you are able to create, delete, locate and drag-and-drop an operator screen.

Creating an Operator Screen

Procedure:

If the screen Then...

already exists  select the operator screen in the Functional Station directory
of the functional view or the Operator Screens directory of the
structural view,
 in any language editor window, select Open Operator Screen.
in the function block contextual menu.
 drop the operator screen in a functional module at the Screen
directory level.
NOTE: With the Open Operator Screen menu if multiple operator
screens exist with the same name, the editor opens the first one
found.
must be created from  with the mouse right-click the Screen directory of the functional
the functional view module,
 select New screen.

Accessing the Operator Screen Properties

Procedure:

If selected at the level Then...

of the
a family of screens  select the family of screens in the Screen directory of the
structural view,
 Select Family Properties from the contextual menu.

a specific screen  select a screen in the Screen directory of the structural view,
 Select Screen Properties from the contextual menu.

250 33003101 12/2015

 Functional modules

Creating a Family of Operator Screens

Procedure:

If the family Then...

already exists  select the family of operator screens in the Functional Station
directory of the functional view or the Operator Screen
directory of the structural view,
 drop the family of operator screens in a functional module at the
Screen directory level.
must be created from  with the mouse right-click the Screen directory of the functional
the functional view module,
 select New family.

Opening an Operator Screen

Carry out the following actions:

Step Action
1 Select the operator screen in the Functional Station directory of the functional
view or the Operator Screens directory of the structural view.
2 Select Open from the contextual menu.

Deleting an Operator Screen

Procedure:

If the screen Then...

does not belong to a  with the mouse right click the operator screen in the Operator
family of screens Screen directory,
 select Delete.

belongs to a family of  from the Screen directory, right-click the operator screen
screens belonging to the family,
 select Delete.

33003101 12/2015 251

Functional modules

Moving an Operator Screen

Procedure:

If using Then...
the drag-and-drop  left-click on the operator screen to be moved (holding down the
function mouse button),
 move the operator screen to the desired location.

NOTE: The insertion point of the operator screen is represented by

a line.
Screen Properties  select the operator screen,
from the contextual  select Screen Properties from the contextual menu,
menu  select the name of the module in the Location zone.

Detaching All Screens and Families of Screens

Procedure:

If you have chosen to Then...

detach
the operator screens  select the Screen directory of the functional module,
and the families of  select Detach All from the contextual menu,
screens  confirm with Yes.

the family of screens  in the Screen directory of the functional module, select the family
of screens,
 select Detach from the contextual menu,

a specific screen  select the operator screen in the Screen directory of the
functional module,
 select Detach from the contextual menu,

Accessing the Messages List

The following table shows the procedure for accessing the operator screens messages list.

Step Action
1 Select the Operator Screens directory from the structural view.
2 Select Messages list from the contextual menu.

252 33003101 12/2015

 Unity Pro
FDT Container
33003101 12/2015

Chapter 7
FDT Container

FDT Container

Object of the Chapter

This chapter introduces the FDT Container and explains how it is used.

What Is in This Chapter?

This chapter contains the following sections:
Section Topic Page
7.1 FDT Container 254
7.2 DTM Hardware Catalog 257
7.3 DTM Browser 262
7.4 DTM Properties Tabs 288

33003101 12/2015 253

FDT Container

Section 7.1
FDT Container

FDT Container

Object of this Section

This section is an introduction to using DTMs in Unity Pro.

What Is in This Section?

This section contains the following topics:
Topic Page
Introduction to the Unity Pro FDT Container 255
FDT Container User Rights 256

254 33003101 12/2015

 FDT Container

Introduction to the Unity Pro FDT Container

At a Glance
The FDT/DTM (Field Device Tool/Device Type Manager), an open-standard, in Unity Pro
integrates the configuration tools needed to build projects, with a mix of Schneider and Third Party
intelligent devices, on heterogeneous networks.
Unity Pro is now a FDT Container (Field Device Tool Container) for DTMs and, therefore, is a
Generic Fieldbus Intergrater.
NOTE: Schneider-Electric is not responsible for the correct functioning of non-Schneider-Electric
DTMs under Unity Pro.

FDT Concept
The FDT defines the interfaces between device-specific software components (DTMs) and Unity
Pro. The focus of the current version of FDT is on engineering, commissioning, diagnostics and
documentation of fieldbus based control systems.
The device-specific software component is called a DTM (Device Type Manager), which are
supplied by the device manufacturer together with the device. Because the FDT technology used
in Unity Pro is based on an open standard, Unity Pro accepts compliant DTM products from any
DTM/device vendor.
NOTE: The DTMs are installed/uninstalled on the PC (like most other Windows® programs) that
runs Unity Pro and information about the DTMs is kept in the Windows Registry.
NOTE: The DTM Browser displays the DTM connectivity configuration, but does not create any
topological variables (%I or %Q) in the application.

Components
To create a Fieldbus network with Unity Pro, its FDT Container uses:
 The DTM Hardware Catalog (see page 257)
 The DTM Browser (see page 262)
 The DTM Editor, which uses vendor supplied GUIs to configure the DTMs
NOTE: The DTM vendor is responsible for the DTM Configuration on-line Help, it is not available
through the Unity Pro on-line Help.

33003101 12/2015 255

FDT Container

FDT Container User Rights

At a Glance
With 2 exceptions, a FDT Container user has unlimited access to the installed DTMs.

User Rights
The FDT Container user has all rights of access for the DTM connectivity tree (add, delete,
configure, save DTMs) unless:
1. The Unity Pro profile is set to Read Only for the user
2. The user has opened Unity Pro in the Read Only mode

Unity Pro Online/Offline and Device Connections

For the user to load and store DTM device parameters from/to its physical device, the device must
be connected to its DTM through the Host PC.
This connection:
 Requires that the DTM be installed on the Host PC.
 Is independent of the Unity Pro - PLC connection status. A DTM can connect to its device and
transfer configuration information over the network in either direction under both conditions:
Unity Pro off-line or Unity Pro on-line.

Limitation
If the user opens a project in Read Only mode, the DTM user right remains in Read-Only as long
as the project is still opened (even if the user removes the Read-Only opened mode by performing
the service Save As).

256 33003101 12/2015

 FDT Container

Section 7.2
DTM Hardware Catalog

DTM Hardware Catalog

Description of DTM Hardware Catalog

At a Glance
The DTM Hardware Catalog displays all the DTMs installed on the PC.
The DTM tab of the Hardware Catalog is divided into 3 parts:
 The Filter area
 The Device List Area
 The Update button

The DTM Catalog Tab

The following illustration is an example of the DTM Hardware Catalog:

33003101 12/2015 257

FDT Container

Add DTMs to Connectivity Tree

There are 2 ways to add DTMs to a DTM connectivity tree:
 By using the Add device (see page 277) procedure in the DTM Browser
 By using the mouse to drag a DTM from the Hardware Catalog and dropping it on an appropriate
DTM in the connectivity tree

The Filter Area

The browser in the Filter Area has 4 types of filters with sub-filters. The actual sub-filters available
depend on the type of DTMs installed on the PC:
 Devices
There are 3 device type sub-filters:
 Communication
 Gateway or Modular
 (Other) Devices

 Vendors
Selecting a vendor name displays only the installed DTMs from that vendor.
 Groups
Selecting a group type displays only the installed DTMs corresponding to that type of DTM.
 Protocols
Selecting a protocol displays only the installed DTMs corresponding to that type of protocol.
When a protocol is selected as the filter, a DTM is only shown if this protocol is required and/or
supported by the DTM.
When a filter is selected, only the DTMs corresponding to that filter are displayed in the Device
List Area.

The Device List Area

The Device List Area columns give information about each DTM. They are:
 Device (name)
 Type
 Vendor (name)
 Version
 Date

Clicking on a column heading sorts the DTMs alphabetically according the contents of the column.

258 33003101 12/2015

 FDT Container

DTM Properties
To display the properties of a DTM from the Device List Area:

Step Action
1 Click anywhere on the line of the DTM.
Result: The DTM is selected.
2 Right-click on the DTM.
Result: The Properties menu opens.
3 Use the tabs (see page 288) to see additional information about the DTM:

4 When finished with the window, click on OK or Cancel.

NOTE: When installing or modifying a DTM, update the Hardware Catalog (see page 260) to
update its properties information.

33003101 12/2015 259

FDT Container

Update Hardware Catalog

The DTM catalog is fully embeded in the Unity Pro software and requires to be up to date whenever
a DTM is installed or unistalled. It can be done:
 automatically when the Unity Pro software is launched in closed project mode
 or manually, from the Hardware Catalog window, anytime the customer requests an update.

When the Unity Pro software is launched, in closed project mode, and DTMs are installed or
uninstalled on/from the PC, the DTM catalog must be updated using the following procedure:

Step Action
1 When DTMs are installed or uninstalled and the Unity Pro software is launched.
Results: The dialog box update opens:

2 Click on the Yes button.

Results: When the update is completed, a message box appears:

NOTE: Only a V1.2.1 FDT/DTM version or higher provides the detection service.
The DTM catalog can be updated manually update can be done using the following procedure:

Step Action
1 From the hardware Catalog (see page 260), click on the Update button.
Results: The dialog box update opens:
2 Click on the Yes button.
Results: The standard Unity Pro progress control dialog is displayed:

Updating the Hardware Catalog does not modify the build status of the DTM. It creates an internal
catalog file based on the installed DTMs existing in the Windows® registry.
The time necessary for an update depends on the number for DTMs installed and their sizes.

260 33003101 12/2015

 FDT Container

DTM Version Compatibility

The compatibility of DTM versions is managed by the vendor. They cannot be managed in Unity
Pro.
During an update no check is made if a DTM missing from the Hardware Catalog is used in an
application.
There are 2 methods to check and display any inconsistencies:
 Build the whole Unity Pro application
 Run the Check devices (see page 273) service from the HostPS contextual menu

33003101 12/2015 261

FDT Container

Section 7.3
DTM Browser

DTM Browser

About this Section

This section describes the DTM Browser, which enables the user to select the different DTMs that
make up the DTM connectivity tree on the host PC.

What Is in This Section?

This section contains the following topics:
Topic Page
DTM Browser 263
Ethernet Ready Equipment 268
Ready, Built, Connected and Installed DTMs 270
DTM Browser Contextual Menus 273
Field Bus Discovery Service 281
Store Device Configurations 284
Renaming DTMs 285
Profibus DTMs 287

262 33003101 12/2015

 FDT Container

DTM Browser

At a Glance
The DTM Browser is the main component of the Unity Pro FDT Container. The DTM devices are
managed from the browser.

DTM Browser
To open the DTM Browser use the Tools menu -> DTM Browser:

The root of the DTM Browser is HostPC, which is the PC platform for the Unity Pro project.

33003101 12/2015 263

FDT Container

DTM Browser DTM Types

The DTM Browser displays the configured DTMs added to the connectivity tree HostPC with
hierarchical levels (nodes).
There are 3 types of DTMs:
 Communication DTMs (drivers)
 Any COM DTM can be plugged directly under the root node (HostPC) and must be at the 1st
level
 A COM DTM can support Gateway DTMs or Device DTMs as children if their protocols are
compatible
 Gateway DTMs
A Gateway DTM can support other Gateway DTMs or Device DTMs as children if their protocols
are compatible.
 Device DTMs
A Device DTM does not support any child DTMs
The following illustration is a connectivity tree:

264 33003101 12/2015

 FDT Container

The following table describes the different hierarchical nodes of the connected DTMs in the above
example connectivity tree:

Number Description of Level

1 The First Level is the root node, HostPC, which is where the PC is connected
to the physical network.
2 The Second Level devices are communication DTMs (drivers) that connect to
their physical communication devices on the network.
3 The Third Level devices are connected to a communication device.

Copy Paste feature

Each device DTM configured can be copied and pasted to easily create configuration.
NOTE: Only Device DTMs can be copy and pasted.
Operating mode to make a Copy/Paste:
 Make a right click on the Device DTM you want to Copy/Paste
 Select Copy
 Make a right click on the Communication DTM or Gateway DTM in which you want to paste the
Device DTM
 Select Paste.

NOTE: If protocols are matching only device DTM can be paste under Communication DTM, only
if protocols are matching. Communication DTM has to be in off-line mode.
NOTE: If protocols are matching, only device DTM can be paste under Gateway DTM, only if
protocols are matching. Gateway DTM has to be in off-line mode.
NOTE: When a DTM is pasted in the connectivity Tree, the General tab (see page 289) is
displayed. By default, the copied DTM alias is based on a valid DTM alias name.
NOTE: A default address is automatically created after the paste of a device DTM. The address
can be modified when entering in the father DTM configuration screen. Copy/Paste feature has
limitation, it can only be done inside an application and can not be done between two applications.

33003101 12/2015 265

FDT Container

Tree View Naming

Each DTM has a default name when inserted into the browser. The syntax is the following:
<Channel: Bus Address> User Name:
 Channel
This is the name of the channel communication media where the DTM is plugged in. This
name is read from the DTM and is set by the device vendor.
 Bus Address of the device. It can be either:
 The connection point on its parent gateway network
 The slot number in the modular device parent internal bus

This information is supplied by the parent DTM and can be modified in Unity Pro if the DTM
supports this modification.

 User Defined Name

This name is set by default to the vendors name for the DTM name (which is the default vendor
name), but can be reset (see page 285).
Examples:
 For a communication DTM
<1> My =S= PRM COMM, where 1 is the references number.
 For a Device or a Gateway
<Profibus:1> Tank1Sond1 means that the DTM is connected to the Profibus channel of its
“parent” at connection point 1.

266 33003101 12/2015

 FDT Container

Example Connectivity Tree

The following illustration is a connectivity tree:

Number Node Level Description

1 This Second Level PRM Comm Master communication DTM connects to the
HostPC for communication with a PRM device via the Ethernet for DPV0 and
DPV1 exchanges.
2 This Second Level PRM Comm communication DTM connects to the HostPC
for communication with a PRM device via the Ethernet for DPV1 exchanges.
3 This Third Level Profibus Gateway DTM connects simple or Gateway devices
to the higher communication DTM.
4 The Simple or Compact DTMs are connected to communication DTMs that
allow them to communicate with their physical devices on the network. These
tree leaves do not allow any sub-connectively.

33003101 12/2015 267

FDT Container

Ethernet Ready Equipment

Definition
An Ethernet Ready equipment is an Ethernet equipment that provides additional services
compared to standard EIP or Modbus equipment.

Applicability
This concept of Ready equipment applies to:
 Standalone devices connected to the Ethernet I/O
 Modules plugged on the Ethernet backplane

NOTE: The only Ready module that exists is the BME CXM 0100.

Representation

In Unity Pro, such devices are identified with a specific green label in the DTM browser:

268 33003101 12/2015

 FDT Container

Services
Ready services are related to the software integration of the products into Unity Pro. It is based on
DTM technology.
This table presents the services available for Ethernet Ready equipment:

Service Description
Single parameter entry Any device parameter that you enter is shared into the entire configuration
environment.
Bus editor declaration Declaration is done from the Ethernet I/O bus editor or PLC bus editor in the
Unity Pro browser. It uses products that belong natively to the Unity Pro
Hardware Catalog.
System transfer You can transfer all the system in a single operation: the Ready device
configuration is transferred to the PLC with the PLC application.
NOTE: The PLC acts as a configuration server for all the Ready devices.
Scanning capacity Scanned in a deterministic way (from the CPU RIO scanner(1)): you can attach
the Ready equipment to any PLC task. It is refreshed within the task scan.
NOTE: This Ready equipment is called remote equipment to differentiate it
from distributed equipment, which is scanned from the DIO scanner (RPI can be
changed and is not linked to the task period).
Alert message Inform you when a modification done from the device DTM impacts the PLC
application and can lead to stop the PLC.
Online help integration –
Shared user rights User rights are automatically shared between Unity Pro and the device DTM.

(1) Scanners that accept Ready devices (M580 CPU) are also identified with this green label .

33003101 12/2015 269

FDT Container

Ready, Built, Connected and Installed DTMs

At a Glance
The status of a DTM is indicated in the DTM Browser: Ready, Not-Built, Connected and Installed.

Ready
Ready devices or modules are devices or modules that are used by DTMs and fully integrated in
the Unity Pro software, they mainly bring two particularities:
 They use new Unity Pro mechanisms to be integrated into the Unity Pro hardware catalog.
 They are managed by Unity Pro Ethernet I/O bus editors as for any X80 I/O modules.

A red “R” icon indicates that the device or module is a Ready one.

Built or Not-Built DTMs

Build status:
 Not-Built: A blue check marks indicated that a node or one of its sub-nodes have changed, the
information stored in the physical device is no longer consistent with the local project.
 Built: After building the Unity Pro project, the blue check mark is no longer in front of browser
nodes that were changed before the build.

Connected or Non-Connected DTMs

Connecting a DTM to its physical device automatically connects all higher level parent nodes up
to the root node (all DTMs that the DTM being connected depends on.
Disconnecting a DTM from its physical device automatically disconnects all its lower level child
nodes (all DTMs that depend on the DTM being disconnected).
Connection status:
 Connected: Connected nodes are represented by bold text in the browser. A node can be
connected without all its sub-nodes being connected.
 Non-Connected: Non-connected nodes are represented by normal text.
NOTE: Connecting a fieldbus or device is not linked the Unity Pro connection to a PLC (Off-line
or On-line). DTMs can be connected/disconnected while Unity Pro is either Off-line or On-line.

270 33003101 12/2015

 FDT Container

Installed DTMs
Installation status:
A red X on the icon of a DTM indicates that the DTM software is not installed on the PC.
 This status is updated (red X added) when devices are detected but no DTM software is
installed on the Host PC when the user:
 Updates the Hardware Catalog
 Tries to build the application
 Tries to use a service in one of the 2 right-click contextual menus in the DTM Browser
 Tries to use the Open service by left-clicking twice on a DTM in the DTM Browser

 This status is updated (red X removed) when the user updates the Hardware Catalog with the
missing DTM.
A right-click on an invalid or non-installed DTM opens a 2-item contextual menu:

Function Description
Delete This removes the selected DTM (and its sub-nodes) from the DTM
project.
Properties To help identify the non-installed DTMs, this function displays one tab
(Device information) in the Properties of dialog box:

33003101 12/2015 271

FDT Container

DTM Browser
The following illustration gives examples of built/non-built, connected/non-connected and non-
installed statuses:

The following table explains how a DTM Browser indicates if the DTMs are built, connected and
non-installed:

Number Status Number Status

1 Not-Built 4 Not-Built
2 Non-installed 5 Connected
3 Built

272 33003101 12/2015

 FDT Container

DTM Browser Contextual Menus

At a Glance
The (right-click) contextual menu of the DTM Browser offers functions that depend on item clicked
on.
NOTE: The contextual menu items are also available via the Edit and View menus.
The DTM Browser Contextual Menu accesses:
 Adding and deleting DTMs
 Connecting and disconnecting DTMs to their physical devices
 Displaying and printing the properties of a DTM
 Transferring DTM configuration information to and from the physical device
 DTM-specific functions (via the Device menu function)
 Field Bus Discovery used to scan the physical devices in a fieldbus network

HostPC
The HostPC contextual menu:

The HostPC contextual menu has the following items:

Name Description

Add device1 The Add, a version of the Hardware Catalog,

opens allowing the selection of a Communication
DTM.

Check DTM devices1 This function checks the current project for invalid or
non-PC-installed DTMs. Refer to Check DTM
devices (see page 274) below.

DTM Services1 This function allows the users to select/unselect all

the DTMs added in the project and performed
actions on the selected DTMs. Refer to DTM
Services (see page 275) below.

33003101 12/2015 273

FDT Container

Name Description

DTM Hardware Catalog1 This function open the DTM catalog tab in the
Hardware Catalog (see page 257).

Expand all2 All DTMs in the project are shown.

Collapse all2 Only the Commutation DTMs in the project are

shown.

Legend:
1 This function is available via the Edit menu.
2 This function is similar to Project Browser Expand/Collapse all (see page 170).

Check DTM Devices

If the results of the check include invalid or non-installed DTMs, they are displayed in the User
errors tab in the bottom information window and a Red X is placed over their icons in the DTM
Browser:

NOTE: Check DTM devices only detects installed DTMs, for GSDs verify the GSD library.

274 33003101 12/2015

 FDT Container

DTM Services
The users can select/unselect DTMs added in the project and performed actions on the selected
DTMs:

The DTMs services dialog box menu contains the following group boxes:

Name Description
Communication Dtms The user can select or unselect all communication DTMs and
selection attached DTMs currently added in the project.
Topology The Topology area lists all DTMs added in the project. The set of
selected DTMs can be modified by selecting or unselecting the
DTMs in the Structure tree control.
Actions The user can perform actions for each DTMs contained in the set
of DTMs previously selected in the Structure tree control.
On errors The user can select to Continue or Stop the process if an error
is detected. A dialog box is displayed whatever options is
selected.
Selection The user to select either all DTMs added in the project or none.

33003101 12/2015 275

FDT Container

The dialog box below is an example when the user selects either Continue or Stop in the On
errors group box:

NOTE: The entire process can be cancelled any time by using control button Cancel.

276 33003101 12/2015

 FDT Container

Communication and Other DTMs

The available DTM Browser contextual menu items differ according to the DTM selected:

33003101 12/2015 277

FDT Container

The DTM contextual menu has the following items:

Name Description

Open 1 This opens the “<device name> - DTM Configuration” window

with the Configuration and Device Description information
supplied by the device vendor.
A double-click on the DTM in the DTM Browser also opens this
window.

Add...1 This opens the Add dialog, a version of the Hardware Catalog,
allowing the instantiation of a DTM.
The DTMs are filtered, that is, the Add window only displays
DTMs compatible with the DTM selected in the DTM Browser.
To add a device refer to Add device (see page 280) below

Delete1 If the selected DTM allows this function, this deletes the selected
DTM and its sub-node DTMs from the DTM connectivity tree.
Deletion from the DTM connectivity tree does not effect the
DTMs link to the I/O Scanning table.
Field Bus Discovery This scans the connected physical devices to create the
corresponding field bus connection topology. This item is only
available in the contextual menu if a device connected.
Refer to Field Bus Discovery (see page 281) service.
NOTE: The DTM to scan has to be installed in the PC and the
Hardware Catalog must be up to date.
Sort by address This displays the DTMs sorted under their parent DTMs
according to the bus address of its physical device in ascending
order.

Connect1 This connects the DTM to its physical device on the network.
This connection does not depend on the PLC online/offline status
of the Unity Pro project application.
Connecting a Gateway- or Device-DTM implicitly connects its
parent DTM.
While the device is connected, Connect is not available.

Disconnect1 This disconnects the DTM from its physical device. This
disconnection does not depend on the PLC online/offline status
of the Unity Pro project application.
Disconnecting a DTM implicitly disconnects all its child DTMs.
While the device is disconnected, Disconnect is not available.

Load data from device1 This uploads the configuration parameters from the physical
device to the local DTM, but not from the application (binary) in
the PLC.
While the device is disconnected, Load data from device is not
available.

278 33003101 12/2015

 FDT Container

Name Description

Store data to device1 This downloads the local DTM parameters to the physical device.
Each DTM must be stored manually (one by one).
While the device is disconnected, Store data to device is not
available.
To make an application in the PLC consistent with the stored
DTM, the user must build the Unity Pro application and download
the new version of the application to the PLC
Device Menu The functions in this menu are vendor dependant, such as:
 Compare (the online and offline parameters)
 Diagnostic (displays a diagnostic screen)
 Print (HTML)
 Observe
 Additionnal functions available when selecting the
communication DTM:
 EDS (add or remove from librairy)
 Online Action
 Explicit Message (Ethernet or Modbus)
 About
 Advanced Mode4

When configuring a DTM, the changes are validated in Unity Pro

in 2 ways, depending on the changes:
 Automatically as the changes are made.
 You must click on a OK, Apply or Validate button after
making the changes.
Properties Refer to the DTM Properties Tabs (see page 288) section.
Print device If this optional function is supported by a DTM, it opens the
vendor device documentation in Internet Explorer, which can
then be printed.
Only one DTM information can be printed out at time. A print of
the whole network is not available.

Zoom in1,2 This displays only the selected DTM node and its child DTMs.
While zoomed-in, Zoom in is not available.

Zoom out1,2 This returns to the full display of the DTM connectivity tree.
While there is a full display, Zoom out is not available.

Expand all3 This displays all DTMs below the selected DTM.

Collapse all3 This displays only the selected DTM.

Legend:
1 This function is available via the Edit menu.
2 This function is similar to Project Browser Zoom in/out (see page 167).
3 This function is similar to Project Browser Expand/Collapse all (see page 170).
4 Advanced option are available DTM configuration screen

33003101 12/2015 279

FDT Container

Add a DTM Device

To add a new DTM to the connectivity tree in the DTM Browser:

Step Action
1 Make sure that the DTM appears in the Hardware Catalog.
If it is not in the catalog, perform an update (see page 260) of the Hardware
Catalog using the Update button.
If it still does not appear in the Hardware Catalog, the DTM must be installed
on the PC (see page 258).
2 In the DTM Browser select the node where the DTM is to be added.
3 Right-click and select Add...
4 In the Add window select the DTM to be added to the DTM connectivity tree.
5 Either:
 Click on the Add DTM button
 Double-click on the selected DTM

Results: The 4-tab DTM Properties of dialog opens.

6 Using the 4 tabs, verify that the correct DTM has been added to the DTM
connectivity tree and verify its configuration.
7 If the DTM Alias name does not meet the Unity Pro (or the user application)
naming rules, it must be changed before closing the dialog.
8 Click on the OK button to finish adding the DTM to the network tree or click on
the Cancel button to close the dialog without adding anything.

280 33003101 12/2015

 FDT Container

Field Bus Discovery Service

At a Glance
The Field Bus Discovery service is available for Communication and Gateway DTMs that:
 Support device scanning
 Are connected to their physical devices

Only the first level devices below the Communication and Gateway DTMs are detected (there is
no recursive scanning).

Field Bus Discovery Use

The results of the scanning process is compared to the registered DTMs in the DTM catalog of the
computer. If a match is found in the DTM catalog for a scanned device, the results are
accompanied with a matching type that gives the accuracy of the match.
The three available matching types are:
 Exact Match:
All identification attributes are matching. The correct device type was found.
 Generic Match:
At least the Manufacturer ID and Device Type ID attributes match. The support level of DTM is
“Generic Support”.
 Uncertain Match:
At least the Manufacturer ID and Device Type ID attributes match. The support level of DTM is
not “Generic Support”.
The following procedure explains how to use the Field Bus Discovery service:

Step Action
1 In the DTM Browser select an appropriate DTM.
2 Right click to open the Contextual menu Field Bus Discovery.
3 If necessary, select the channel and protocol:
 If the DTM has more than one channel
 If the channel supports more than one protocol

4 Click on OK in the message box to have this service detect all devices on the
selected channel.
5 If at least one matched device has been found, the Field Bus Discovery dialog
(see page 282) is displayed listing the scanned and matched devices. Select the
matched devices to be created in the Unity Pro project.

NOTE: a device that is connected on the bus can be detected if:

 Its DTM is installed on the PC.

 Its GSD is added into the GSD library (if not a DTM device).
 The DTM hardware catalog is up-to-date (with the DTM installed and the GSD in the library).

33003101 12/2015 281

FDT Container

Field Bus Discovery Dialog

If at least one matched device has been found, the Field Bus Discovery dialog box is displayed
listing the scanned and matched devices. Select the matched devices to be created in the Unity
Pro project (which then shows up in the Selected Devices list:

282 33003101 12/2015

 FDT Container

This dialog has three lists:

List Description
Scanned Devices This list displays all the devices (matched and unmatched) found during the
scan.
Matched Devices This list displays the matched DTM found in the workstation DTM catalogue
for the selected device in the Scanned Devices list.
Each time a scanned device is selected in the Scanned Devices list, the
contents of the Matched Devices list is updated to display the matched
device DTM found for the selected scanned device.
The matching process can yield one or more matched devices for a given
scanned device. In this case, select one among the matched DTMs found.
Selected Devices This list displays the device DTMs selected to be added to the Unity Pro
project.

The lists use colored icons:

Color Description
Green Indicates that the device has been selected
Yellow Indicates that the device has been matched
Red Indicates that the device has not been matched
Black Indicates information about the address of the scanned device:
 In the Scanned Devices list, the device has an address identical to one of the
DTMs in the Unity Pro project
 In the Matched Devices list, the device will be assigned an address identical to
one of the DTMs in the Unity Pro project

This dialog has five buttons:

Button Use this button to...

1 automatically add the best matched (according to the matching types listed above)
device DTM for each found device in the Matched Devices list to the Selected
Devices list.
2 add the matched device DTM selected in the Matched Devices list.
3 remove one or more devices from the Selected Devices list.
OK insert the device DTMs in the Selected Devices list into the Unity Pro project.
If there are one or more devices in the Selected Devices list that have the same
address in the Unity Pro project, a message box opens asking if you want to
continue.
If you click OK, all devices in the Unity Pro project that have identical addresses as
the selected devices is deleted and replaced by the DTMs selected in the Selected
Devices list.
Cancel cancel the Field Bus Discovery scan and do nothing. All information in the three lists
is lost

33003101 12/2015 283

FDT Container

Store Device Configurations

Introduction
After configuring or modifying a configuration of a DTM, the changes must be downloaded to its
physical device using Store data to device (see page 273).

Connectivity Tree
For a connectivity tree it is necessary to:
 Store the configuration for each DTM into the corresponding device so that the device works
correctly
 Build or Rebuild all the Unity Pro application and download it to the PLC be able to upload the
complete application including all DTM configurations from the PLC binary
The total number of operations equals the number of DTMs stored + 1 download of rebuilt
application.

Recovering Connectivity from the PLC Application

If the complete application has been stored in the PLC (ETS option checked), it includes the
connectivity of the DTMs.
Uploading the application from the PLC provides the connectivity stored in the PLC. For this, the
PC used for uploading must have the corresponding DTMs (see page 266) installed.
Verify that the corresponding configuration is stored in the devices to avoid de-synchronization of
the project..

De-synchronization of Project
If a DTM configuration is changed and stored to its device, the application running in the PLC is
not updated.
To synchronize the PLC application with the device configuration, rebuild the Unity Pro application
to take into account the changes and download it to the PLC.
Uploading a binary from a PLC overwrites the configurations of all DTMs in Unity Pro applications
retrieved from the PLC. Any modifications of the DTM configurations that are not stored in the PLC
binary are overwritten by the configuration in the PLC binary and lost.

CAUTION
UNEXPECTED EQUIPMENT OPERATION
Do not upload a project from the PLC if any changes have been made in any devices connected
to the PLC since the last build and download of the project.
Failure to follow these instructions can result in injury or equipment damage.

284 33003101 12/2015

 FDT Container

Renaming DTMs

At a Glance
According to the FDT standard, the official name of a DTM is its Tag name assigned by the DTM
vendor.
Unfortunately, some DTMs have Tag names that do not:
 Allow the Tag name to be changed
 Meet the Unity Pro naming rules

The solution is to choose the DTM Alias name that meets these rules (and any special user defined
application naming rules).

Alias Name
The Alias name is the DTM reference name in Unity Pro and must be unique in an application.
If possible, the default, the Alias name is the same as the DTM Tag name. But if necessary, the
Alias name can be changed in 3 places:
 Directly in the General tab (see page 289)
 In the DTM Browser by clicking on the selected DTM or using the F2 shortcut with the selected
DTM.

I/O Vision in Communication DTMs

For device DTMs attached to certain Schneider Electric Communication DTMs (such as the
SE_Master_PRM_DTM), the default names of the DTM Input/Output Types (a structure) and the
Variable instances of the Type are based on the default DTM Alias/Tag name:

33003101 12/2015 285

FDT Container

Changing the Alias name automatically changes the names of the Input/Output Types and
Variables:

286 33003101 12/2015

 FDT Container

Profibus DTMs

Configuration of Profibus Field Devices

Using vendor-supplied Profibus DTMs, users are able to remotely:
 Configure Profibus devices associated with the DTM
 Adjust the parameters of these devices while they are off-line
 Adjust the parameters of these devices while they are on-line

PRM Master Bus Module and its DTMs

Unity Pro uses a Profibus Remote Master (PRM) Gateway module (the bus master physical
device) and its PRM configuration tools (software):
 The PRM Master DTM that allows the PRM Gateway to carry out:
 Explicit DPV0 functions (control and diagnostics of the Profibus slaves on the network).
 Communication functions (implicit DPV1 exchanges with the Profibus slaves). It also
provides access to the Profibus slaves from the Control network to HMI, SCADA or ASSET
management tools.
 The PRM Comm DTM that only allows the PRM Gateway module to carry out communication
of implicit DPV1 exchanges and access to management tools.
The Modbus TCP I/O scanning link between the PLC and the (PRM) Gateway module connected
to the Profibus network is provided by a Quantum, Premium, M340, or M580 module with an
Ethernet port.

33003101 12/2015 287

FDT Container

Section 7.4
DTM Properties Tabs

DTM Properties Tabs

DTM Properties Dialog

At a Glance
The number of tabs in a Properties dialog varies according where the dialog is called from.

Properties Tabs
The Properties dialog is called when a DTM is selected:
 To be added to connectivity tree in the DTM Browser from the Hardware Catalog:
 For the Contextual Menu Properties service in the Hardware Catalog:
 It opens with 4 tabs:
 General
 Device Information
 DTM Information
 Protocol Information

288 33003101 12/2015

 FDT Container

General
The General tab:

NOTE: The Alias name (and the DTM Tag name if the vendor allows it) can be changed
(see page 285) here or in the DTM Browser.

33003101 12/2015 289

FDT Container

Device Information
The Device Information tab:

290 33003101 12/2015

 FDT Container

DTM Information
The DTM Information tab:

33003101 12/2015 291

FDT Container

Protocol information
The Protocol Information tab:

Item Description
Supported protocols These are the protocols available for the child nodes of this DTM.
Required protocols These are the protocols that must be supported by the parent
DTM of this DTM.

292 33003101 12/2015

 Unity Pro
Type Library Manager
33003101 12/2015

Chapter 8
Type Library Manager

Type Library Manager

Object of this section

This chapter describes the main functions of the Type Library Manager.

What Is in This Chapter?

This chapter contains the following topics:
Topic Page
Libset (Set of Libraries) 294
Overview of the Type Library Manager 297
Type Library Manager 298
Description of the Type Library Manager 301
Loading an object from the library into the project 307
Transferring an object from the project into the library 310
Creating a new library and family 312
Creating an installable family 314
Updating a family of a library 315
Consistency Check Assistant 317
Library Version Management 320
Using the type library of an older Unity Pro Version 324

33003101 12/2015 293

Type Library Manager

Libset (Set of Libraries)

At a Glance
Libset (set of libraries) comprises all libraries, families, functions and variables (I/O data
structures) that can be used to develop an automation project.
You can only modify the Libset version in the Open project dialog.

Creating a New Project

Creating a new project, the latest Libset version is automatically selected for this project.
To modify the Libset version of your project, you have to save your project and open it again with
the version of Libset you want to use.

Opening a Project
In general, opening an existing project (STU file) or an archived project (STA file), you can select
the Libset version.
Importing a ZEF or XEF file, the latest Libset version is always selected.
The following table describes the default Libset version used to open a project according to the
file type.

File Type Project before Unity Pro 4.0 Project from Project from
Unity Pro 4.0 to Unity Pro 6.0
Unity Pro 5.1
STU file Not applicable The Libset version used to build the project is
automatically selected. If the respective Libset
version is not installed, the latest version will be
used.
STA file The Libset version used to The Libset version used to generate the STA file
generate the STA file is is automatically selected. If the respective
automatically selected. If the Libset version is not installed, the latest version
respective Libset version is will be used.
not installed, the latest version
will be used.
XEF file The latest Libset version is The latest Libset version is selected.
selected.
ZEF file Not applicable Not applicable The latest Libset
version is selected.

294 33003101 12/2015

 Type Library Manager

Modifying the Libset Version

Opening an existing project (see page 87) (STU file) or an archived project (STA file) you can
select the Libset version.
The Open dialog provides the following options.

Element Description
Keep project version Select this option to keep the Libset version used to
build the project.
If the respective Libset is not installed, the latest
Libset version will be used.
Update with latest version available Select this option to update the project with the
latest Libset version.
Select a specific target version Select this option to choose a specific Libset
version. You can select the version by means of the
Version box below.

If the Libset version is modified, the project is in modified state.

Upgrade/Downgrade

 Upgrading the Libset does not update the project with the newly chosen libset automatically.
EF/EFB differences will be displayed during opening the project in the LIBRARY Version
Management dialog, where you can update the project.
You can update the project later as well, using the contextual menu command in the Type
Library Manager dialog (see page 320).
If you have updated the project, you have to start a Rebuild All. A Rebuild All needs to stop
the PLC and to perform a global download.
 You can also downgrade the Libset version.
There is no consistency check when downgrading the Libset while opening a project.
So you may not be able to rebuild the project (using a block created in an earlier Libset version,
not available in the latest Libset version).
If the rebuild is unsuccessful, you have to save your project and to open it again with an
appropriate Libset.
 If you want to add an FFB which is not yet contained in the current version of the Libset, you
have to upgrade the whole Libset.
 A change of Libset version in the Open dialog is memorized in the project.

33003101 12/2015 295

Type Library Manager

Libset Information
If no project is opened, information is displayed on the latest Libset.
If a project is opened, information is displayed on the Libset used for the project.
Information on the Libset version used for your current project you can get from the General tab
of the Properties of Station dialog.
In the Project Browser of Unity Pro right-click on Station and select Properties from the context
menu. In the General tab you will find the FFB Library version.
Further on the following dialogs provide information on the Libset version (e.g. LibsetV3.0):
 Types Library Manager
 Types Library Browser
 Data Selection
 Data Editor: Variable Type Selection
 Function Input Assistant: FFB Type Selection
 Data Properties
 PLCScreen → Information tab → APPLICATION → IDENTIFICATION

Types Library Manager

In the Types Library Manager click the Information button to get the following information:
 Current library
 Library status
 Diagnostic

 Library contents
 Families
 Libraries
 FFBs

For the Libset Information window please refer to information (see page 299).

296 33003101 12/2015

 Type Library Manager

Overview of the Type Library Manager

Principle
The Unity Pro Library contains all available objects to develop an automation project. These
objects may be the following functions or variables:
 EF (Functions),
 EFB (Function blocks),
 DFB (user function blocks),
 DDT (Variables)
 ...
The Type Library Manager provides functions to edit the contents of the library and execute
transfers between the library and the project you are working on.
Simple operations are automatically executed or you will be asked to confirm. An Assistant
(see page 317) will support complex operations. This Assistant becomes available during loading,
transfers, or deletions.

List of available functions

The Unity Pro context menus provide access to the library management functions below:
 Creating a family or library
 Deleting a family or library
 Cutting a family or object
 Inserting a family or object
 Showing and hiding a tree structure for an object, family, or library
 Renaming the current entry in the tree structure
 Displaying the Assistant to load an object
 Fit columns
 Deleting types not used in the project
 Version check: Consistency between different versions of the objects of the library and project
Library Version Management, page 320.

33003101 12/2015 297

Type Library Manager

Type Library Manager

At a Glance
Unity Pro software provides a manager to edit objects in the library providing access to all
managing functions of the library.
 Loading an object into the project from the library (see page 307).
 Transferring an object of the project into the library (see page 310).
 Deleting a library object
 Updating and managing library versions
 ...

Accessing the Manager

Step Action
1 In the Tools menu, select the Type Library Manager option.
Result: The following window appears.

298 33003101 12/2015

 Type Library Manager

Areas of the Type Library Manager

Area Description
Tabs The tabs enable you to display the following according to your
selection:
 All Types
 Variable types
 FFB Types (Functions)

The left sub-window His sub-window shows the tree structures of the objects of the
project, library of functions (division of functions by family), and the
IODDT.
The right sub-window This sub-window displays the list of objects included in the selection
made in the left sub-window.
The check boxes above it are used to define this list.
Buttons  Information
Click this button to get information on the current library.
See paragraph below.
 Close
Click this button to close the dialog box without accepting
changes.
 Access Assistant
Click this button to open a window to copy objects into a project
(Loading an object from the library into the project, page 307).
 Help
Click this button to call up the dialog help.

Information
Click the Information button to open the Libset Information window.

33003101 12/2015 299

Type Library Manager

The table below describes the various functions offered.

Fields Description
Current library Library status: information on the status of the custom library
 available
 not available

Diagnostics: information on the validity of the library

 OK (valid)
 not valid.

Library contents Families: indicates the number of families available

Libraries: indicates the number of libraries available
FFBs: indicates the number of function blocks available
Custom Library: indicates whether or not user libraries exist

300 33003101 12/2015

 Type Library Manager

Description of the Type Library Manager

Dialog structure
The dialog box to select objects has three tabs:
 All Types
Under this tab, you can select variables and FFBs.
 Variable types
Under this tab, you can select the variables.
 FFB Types
Under this tab, you can select FFBs.

Tab All Types tab

33003101 12/2015 301

Type Library Manager

Elements of the All Types tab:

Element Description
Button Click this button to update the display corresponding to the filter term
defined in the Name field.

Button Click this button to open a dialog box (see page 412) for defining the
filters.

Button Click this button to invert the filter. The button changes from = to <>
and vice versa.

Name (Text Box) The name of the object to search for can be entered in this text box.
You can also use the joker * and ?.
EF When you enable this check box, Elementary Function types (EFs)
are displayed.
EFB When you enable this checkbox, Elementary Function Block types
(EFBs) are displayed.
DFB When you enable this checkbox, Derived Function Blocks (DFBs) are
displayed.
DDT When you enable this checkbox, multi-element variables (derived
variables) are displayed.
Device DDT When you enable this checkbox, multi-element variables (derived
variables) are displayed.
Name (Column) This column displays the names of the function types and function
block types and their formal parameters (inputs, outputs).
Type This column displays the types of the function types and function block
types and the data types of their formal parameters (inputs, outputs).
Comment This column displays comments about the function types and function
block types and their formal parameters (inputs, outputs).
For information on the buttons at the bottom of the dialog please refer to Areas of the Type
Library Manager, page 299.

NOTE: Help on Type:

Hold down the SHIFT+F1 keys and then click on the function block type for which you wish to
access Help.

302 33003101 12/2015

 Type Library Manager

Variable Types tab

Elements of the Variable Types tab:

Element Description
Button Click this button to update the display corresponding to the filter term
defined in the Name field.

Button Click this button to open a dialog box (see page 412) for defining the
filters.

Button Click this button to invert the filter. The button changes from = to <>
and vice versa.

Name (Text Box)) The name of the object to search for can be entered in this text box.
You can also use the joker * and ?.
DDT When you enable this checkbox, multi-element variables (derived
variables) are displayed.
Device DDT When you enable this checkbox, multi-element variables (derived
variables) are displayed.

33003101 12/2015 303

Type Library Manager

Element Description
Name (Column) This column displays the names of the function types and function
block types and their formal parameters (inputs, outputs).
Type This column displays the types of the function types and function block
types and the data types of their formal parameters (inputs, outputs).
Comment This column displays comments about the function types and function
block types and their formal parameters (inputs, outputs).
For information on the buttons at the bottom of the dialog please refer to Areas of the Type
Library Manager, page 299.

Tab FFB Types

Elements of the FFB Types tab:

Element Description
Button Click this button to update the display corresponding to the filter term
defined in the Name field.

Button Click this button to open a dialog box (see page 412) for defining the
filters.

304 33003101 12/2015

 Type Library Manager

Element Description
Button Click this button to invert the filter. The button changes from = to <>
and vice versa.

Name (Text Box) The name of the object to search for can be entered in this text box.
You can also use the joker * and ?.
EF When you enable this check box, Elementary Function types (EFs)
are displayed.
EFB When you enable this checkbox, Elementary Function Block types
(EFBs) are displayed.
DFB When you enable this checkbox, Derived Function Blocks (DFBs) are
displayed.
Name (Column) This column displays the names of the function types and function
block types and their formal parameters (inputs, outputs).
Type This column displays the types of the function types and function block
types and the data types of their formal parameters (inputs, outputs).
Comment This column displays comments about the function types and function
block types and their formal parameters (inputs, outputs).
For information on the buttons at the bottom of the dialog please refer to Areas of the Type
Library Manager, page 299.

NOTE: Help on Type:

Hold down the SHIFT+F1 keys and then click on the function block type for which you wish to
access Help.

Shortcut menu structure

Additional commands can be executed via the shortcut menu of the Type Library Manager.
Shortcut menu commands:

Menu command Description

Delete Use this menu command to delete a selected user-defined
library.
Expand All Use this menu command to show the directory structure of a
selected library. The same function is also available via the +
symbol.
Collapse Use this menu command to hide the directory structure of a
selected library. The same function is also available via the -
symbol.
Create New Library Use this menu command to create a new user-defined library.
Compare also Creating a new library and family, page 312.

33003101 12/2015 305

Type Library Manager

Menu command Description

Rename Use this menu command to rename a user-defined library.
Local Print Use this menu command to print a list of the FFBs of a selected
library.
Display Get Assistant Use this menu command to open a window to copy objects into
a project. (Loading an object from the library into the project,
page 307).
Customize Columns... Using this menu command you can:
 define the columns (see page 1231) to be displayed and
 define the sequence (see page 1231) for the columns shown.

Purge unused Types Use the menu command to delete all unused FFBs from the
project.
NOTE: When a FFB is not available for a kind of PLC (after a
section import for instance) but still in the application (removed
from the section but still in the list of the Application FFBs), the
purge feature should be used before building the application.
Compare Project with This menu command enables you to compare all FFB types of a
Library project with the FFB types of the libraries and update them, if
necessary. Compare to Library Version Management, page 320

306 33003101 12/2015

 Type Library Manager

Loading an object from the library into the project

At a Glance
Loading objects from the library into the projects makes the objects used in a project available
quicker without having to run the list of all other objects in the library.
Loading is automatically executed during the first use of a Logic section. You can also load the
objects manually from the Type Library Manager.

Loading an object into the project

Step Action
1 In the Tools menu, select the Type Library Manager option.
Result: The following window appears.

33003101 12/2015 307

Type Library Manager

Step Action
2 Click on Access Assistant to open the Help window for loading.
Result: The following area is added on the right of the previously displayed window:

3 Use this area to create a list of objects to be loaded by selecting them in sequence beginning in the two
sub-windows of Step 1 and then transfer the objects by clicking on the button (double arrows).
4 Click on Copy to project to execute the loading process.
Result: The objects are now loaded into the project and will be displayed in the tree structure for the
project.

308 33003101 12/2015

 Type Library Manager

Loading requirements

If the name of the object in the then...

project ...
does not exist, the object will be transferred automatically.
exists, but the types are different. the transfer will be stopped and not performed,
and a message listing the causes will be
displayed.
Note: To load this object you must rename it and
restart the loading process.
exists and the types are identical. loading will be executed after you confirm.
Note: The Consistency Check Assistant
(see page 317) will ask you to confirm before
loading.

33003101 12/2015 309

Type Library Manager

Transferring an object from the project into the library

At a Glance
The transfer of an object from the project into the library enables the use of the objects of a project
with another project without having to import or export between applications.
Objects transferred to the library can be accessed from all projects.

Transferring an object to the library

Step Action
1 In the Tools menu, select the Type Library Manager option.
Result: The following window appears.

2 Select the object of the project to be transferred.

3 Click the right mouse button to open the context menu and select the Copy to Library option.
4 Select the library and target family and click on OK to confirm your selection.
Result: The transfer will be performed automatically.
Note: If the transfer is not performed automatically, a help window will be displayed to help you correct
the problem.

310 33003101 12/2015

 Type Library Manager

Transfer requirements from

If the name of the object in the library ... then...

does not exist, the object will be transferred if you have specified
the family and the library to which the object is to be
transferred.
exists, but the types are different. the transfer will be stopped and not performed,
and a message listing the causes will be
displayed.
Note: To load this object you must rename it and
restart the loading process.
exists and the objects are identical. no action is required because the objects are
identical.
exists and only the codes of the objects the transfer will only be executed if the version of
are different. the object to be transferred matches or is higher
than the version of the object that currently exists in
the library.
Note: The Consistency Check Assistant
(see page 317) will ask for a confirmation before
executing the transfer.
exists and only the prototypes of the the transfer will be stopped and not performed,
objects are different. and a message listing the causes will be
displayed.
Note: To load this object you must rename it and
restart the loading process.

33003101 12/2015 311

Type Library Manager

Creating a new library and family

At a Glance
You can create a user-defined library. It contains objects that are available for the development of
automation projects, such as:
 Derived Data Types (DDT),
 Function Block Types (EFB/DFB),
 Elementary Functions (EF).
The library is linked to a programming device. This library can access all projects created with this
programming device. You can save the Family of the Library (see page 314) to reuse
(see page 315) it on another programming device.
The following steps are required:
 Creating a library,
 Creating one or more families in the new library,
 Linking objects (EF, EFB, DFB, DDT) to each family.
Unity Pro provides a User-defined Library. This library contains the family custom FAMILY;
however, it does not contain objects at this time.

Create a new library

Step Action
1 In the Tools menu, select the Type Library Manager option.
Result: The following window will be displayed.

312 33003101 12/2015

 Type Library Manager

Step Action
2 Under Name select the Libset directory.
3 Select the Create New Library command in the context menu.
4 Enter the name and confirm with Enter.

Create a new family

Step Action
1 In the Tools menu, select the Type Library Manager option.
2 Under Name select User-defined Library or a self-created library.
3 Select the Create New Family command in the context menu.
4 Enter the name and confirm with Enter.

Link the object to the family

Step Action
1 In the Tools menu, select the Type Library Manager option.
Result: The following window will be displayed.

2 Under Name select User-defined Library or a self-created library.

3 In the user-defined library, select Custom FAMILY or a self-created family.
4 Select the object on the right side in the Name area.
5 Drag the object onto Custom FAMILY or a self-created family.
Result: The selected object is located in Custom FAMILY or the new family.

33003101 12/2015 313

Type Library Manager

Creating an installable family

Introduction
The user-defined library can be saved in a file. It can then be imported into another programming
device.

Procedure

Step Action
1 In the Tools menu, select the Type Library Manager option.
2 In the Name area, display the contents of the Libset directory.
3 Select a family in the User-defined Library or a self-created library.
4 Select the Create Install-Ready Familycommand from the shortcut menu.
Result: The following window will be displayed.

Note: Enable the Include Sub-Types checkbox when the family contains sub-
types that are not defined in the new project.
5 Select the directory where the family is to be stored (installed).
Use Search to select the directory.
6 Click OK.

Notes for EF/EFBs

NOTE: When you try to create an installable family from a family that contains EF/EFBs, a warning
will be displayed that the EF/EFBs will not be exported. For more information about using families
with EF/EFBs in other Unity Pro installations, refer to Updating a family of a library, page 315.

314 33003101 12/2015

 Type Library Manager

Updating a family of a library

Introduction
You can update the type library on a programming device. You can add new EF, EFB, DFB, DDT
to use in your program.
NOTE: Close Unity Pro before updating.

Procedure

Step Action
1 Select Start → Programs → Schneider Electric → Unity Pro → Type Library
Update.
The Type Library Update window will be displayed.

2 Select the directory where the family is stored using the ... button.
3 Select the Libset version (e.g. V4.0) you want to update.
(To change the Library path please refer to Library configuration options
(see page 557).)
4 Click on Install Family.
5 Answer Yes to the displayed question.
6 Answer OK to the displayed warning and click on Exit.

NOTE: If you want to use a family in several Libset versions of Unity Pro, you must proceed as
described above for each Libset version.

33003101 12/2015 315

Type Library Manager

Family with EF/EFBs

You have created a user defined family (e.g. toolkit family) with the EFB tool kit and installed it in
Unity Pro.
You have also copied DFBs and/or DDTs into the family in Unity Pro.
If you now want to create an installable family, the EF/EFBs from this family will not be exported.

Using families with EF/EFBs in other Unity Pro installations

If you want to use user-defined families with EF/EFBs in other Unity Pro installations, proceed as
follows:

Step Action
1 Use your user-defined family (e.g. ToolKit family) to create an installable family
(Creating an installable family, page 314).
Result: The DFB/DDTs of the family will be exported, the EF/EFBs will not be
exported. A warning will advise you.
2 Install the user-defined family with the EF/EFBs you originally created with the
EFB toolkit in the new Unity Pro installation.
3 Install the family you exported in Step 1via Start → Programs → Schneider
Electric → Unity Pro → Type Library Update.
Result: Since the original family from the EFB toolkit and the installable family
from Unity Pro have the same name, a message will appear that this family
already exists and you will be asked if you want to replace it.
4 Answer No to the displayed question.
Result: Another question is displayed whether you want to add the additional
types to the existing family instead.
5 Answer Yes to the displayed question.
Result: All other types (DFB/DDTs) will be added to the family. No existing types
will be replaced.

NOTE: If you want to use a family in several Libset versions of Unity Pro, you must proceed as
described above for each Libset version.

316 33003101 12/2015

 Type Library Manager

Consistency Check Assistant

At a Glance
An Assistant will automatically be displayed for complex or multiple operations to check the library
or any objects of the projects for consistency to enable easy executing of required processes.
When nested objects are loaded or transferred the Assistant will help you select the objects to be
transferred. It will show you the available operations, and which operations do or do not require
preparation (renaming, updating, etc.).
NOTE: Depending on the complexity of your action, the Assistant will present the objects in a flat
or hierarchical format. In some cases a partial list of objects may be selected for processing, and
other cases require confirming or canceling the entire operation. The following sections list some
examples and meanings.
NOTE: The illustrations below show the windows with different columns. This results from the
option to configure the columns differently, just like in the Data Editor (see page 406).

Unchecked elements
When using the Type Library Manager, some elements are not considered during the compatibility
check of DFB and EFB types.
These elements are:
 Initial value elements that contain the initial value of data.
 The Save option showing whether a data element accepts or doesn’t accept the backup /
restore mechanism.
 The RW program option showing whether a public variable can or cannot be written from the
DFB and EFB program.
 The RW program instance option showing whether a public variable can or cannot be written
from the program launcher.
 The Pin Number of the parameter. (Note: This check is only not considered with DFBs)

Libset Version 2.2

NOTE: Upgrading the Libset version of the project may lead to have a list of differences during the
comparison of EFs, EFBs, DFBs used in the application with the library. In case of a project build
with a Libset version 2.2, the version number (V1.0) may be identical with the selected Libset,
even if differences are existing. Upgrading the project with the new Libset requires a rebuild of the
project and a download in the PLC.

33003101 12/2015 317

Type Library Manager

Example of a hierarchal illustration with global confirmation.

The following illustration shows an example of the assistant for a hierarchal view with required
global confirmation. The window shows that certain object types already exist in the library and you
are asked to confirm whether the types should remain in the library.

Example of a flat illustration with global confirmation.

The following illustration shows an example of the assistant for a flat (non-hierarchal) view with
required global confirmation. The window shows that certain object types already exist in the
library and you are asked to confirm whether the types should remain in the library.

318 33003101 12/2015

 Type Library Manager

Example of a hierarchal illustration with selective confirmation.

The following illustration shows an example of the assistant for a hierarchal view with a selective
confirmation option. The window shows that certain object types already exist in the library and you
are asked to confirm whether certain types should remain in the library.

Example of a flat illustration with selective confirmation.

The following illustration shows an example of the assistant for a flat (non-hierarchal) view with a
selective confirmation option. The window shows that certain object types already exist in the
library and you are asked to confirm whether certain types should remain in the library.

33003101 12/2015 319

Type Library Manager

Library Version Management

At a Glance
The Type Library Manager enables you to compare all FFB types of a project with the FFB types
of the libraries.
If there are differences between the FFB types in the project and FFB types in the library, the
LIBRARY Version Management dialog will be displayed showing the relevant information.
This dialog box has two buttons to updated the FFB types of the project with the FFB types of the
libraries.

Compare project to library

The Compare Project to Library command... Begin via the context menu of the Type Library
Manager (right-click).

LIBRARY Version Management tab.

The LIBRARY Version Management consists of three tabs:
 Check new versions
 Other types that can be updated
 Types cannot be updated
The first two tabs have buttons to update the FFB types of the project with the FFB types of the
libraries.

Register: Check new versions

This tab displays FFB types of the project that are older than the types of the libraries.

320 33003101 12/2015

 Type Library Manager

Elements of the Check New Versions tab:

Element Description
Name Name of the FFB type
V. Library Version of the FFB type in the library
V. Project Version of the FFB type in the project
Difference Determined difference between the two versions
Comment Comment about the version difference
Button Updates the selected FFB type with the FFB type from the
Update library.
Button Updates all FFB types shown in this tab with the FFB
Update All types from the library.
Button Closes the window.
OK
Button Opens Unity Pro Help
Help

NOTE: Updating FFB types leads to Rebuild All Project. The PLC must be stopped and a global
download of the project must be performed.

Register: Other types that can be updated

This tab shows FFB types of the project that are different from those in the libraries, but can be
updated.

33003101 12/2015 321

Type Library Manager

Elements of the Other types that can be updated tab:

Element Description
Name Name of the FFB type
V. Library Version of the FFB type in the library
V. Project Version of the FFB type in the project
Difference Determined difference between the two versions
Comment Comment about the version difference
Button Updates the selected FFB type with the FFB type from the
Update library.
Button Updates all FFB types shown in this tab with the FFB
Update All types from the library.
Button Closes the window.
OK
Button Opens Unity Pro Help
Help

NOTE: Updating FFB types leads to Rebuild All Project. The PLC must be stopped and a global
download of the project must be performed.

Register: Types cannot be updated

This tab shows FFB types of the project with differences from those in the libraries that are so great
that they cannot be updated. In this case you could updated FFB types only after you did an
export/import of your project.

322 33003101 12/2015

 Type Library Manager

Elements of the Types that cannot be updated tab:

Element Description
Name Name of the FFB type
V. Library Version of the FFB type in the library
V. Project Version of the FFB type in the project
Difference Determined difference between the two versions
Comment Comment about the version difference
Button Closes the window.
OK
Button Opens Unity Pro Help
Help

33003101 12/2015 323

Type Library Manager

Using the type library of an older Unity Pro Version

At a Glance
If you have already used an older version of Unity Pro, and if you have created your own type
library and families to store DFBs or DDTs, you have to provide this own type library and family for
the new version of Unity Pro.

Providing the type library and families

Follow the steps below to install a new version of Unity Pro:

Step Action
1 Start the Unity Pro software.
2 Use Tools to open the Type Library Manager.
3 Create a ready-to-install family for each family containing your own DFBs or
DDTs (via the context menu for the applicable family). Save these families on
your hard drive (but not in the Schneider Electric directories).
4 Install the new version of Unity Pro.
5 Go to Programs → Schneider Electric → Unity Pro and start the Tool Type
Library Update and install all of your families.
Note: If you want to use your families in several Libset versions, you must
repeat this step for every Libset version.
6 Start the Unity Pro software.
7 Make sure that all of your families have been installed.
8 Create an application.
9 Copy each DFB that belongs to your own type library from the library into your
application.
10 Then copy each DFB from the application into the library family that it came from.
11 All of your libraries and families are now ready for the new Unity Pro Version.

324 33003101 12/2015

 Unity Pro
Data Editor
33003101 12/2015

Part II
Data Editor

Data Editor

Object of this part

It guides the user through the general features available in the data editor in order to:
 Create data types,
 Create data type instances,
 search for data types or instances.

What Is in This Part?

This part contains the following chapters:
Chapter Chapter Name Page
9 Description of the Data Editor 327
10 Creating derived data types (DDT) 333
11 Creating data types of user function blocks (DFB) 357
12 Managing of instances of data belonging to the family of function blocks (EF) 359
13 Managing variable instances belonging to the EDT/DDT/IODDT/Device DDT 369
families
14 General Functions 403

33003101 12/2015 325

Data Editor

326 33003101 12/2015

 Unity Pro
Description of the Data Editor
33003101 12/2015

Chapter 9
Description of the Data Editor

Description of the Data Editor

Object of this chapter

This chapter gives an overview of the data editor.

What Is in This Chapter?

This chapter contains the following topics:
Topic Page
Data Editor Access 328
Description of Data Editor tabs 330

33003101 12/2015 327

Description of the Data Editor

Data Editor Access

Introduction
The project can be accessed from the structural view in the data editor. It has features which
support the following:
 Creating data types,
 Archiving or using function block data types in a library,
 Creating data type instances,
 Displaying data structures in hierarchical manner,
 Searching/sorting/filtering data.

Accessing the Data Editor

Structural view of a project:

328 33003101 12/2015

 Description of the Data Editor

Carry out the following steps:

Step Action
1 With the right mouse-button click on the Variables and FB instances directory.
2 Select the Opencommand in the shortcut menu.
Result: The data editor opens. The Variables tab is shown by default.

Data Editor:

NOTE: You can open the editor directly via data instances which belong to a family defined by you.
If you want to do this open the editor from one of the subdirectories in the Variables and FB
instances directory. The variables to be displayed will be listed in the selected subdirectory.

33003101 12/2015 329

Description of the Data Editor

Description of Data Editor tabs

Data Editor Elements

Appearance:

Description:

Element Description
Filter
Button Clicking on this button updates the display corresponding to the filter term
defined in the name field.

Button Clicking on this button opens a dialog box (see page 412) for defining the
filters.

Button Clicking on this button inverts the filter. The button changes from = to <> and
vice versa.

Name Column where you enter the name (symbol) of the instance or the data type
you want to display. You can use the place holders (* or ? for this.).
EDT Displaying elementary data types
DDT Displaying derived data types
IODDT Display the derived data types (DDT) that reference inputs/outputs
Device DDT Display the device derived data types

330 33003101 12/2015

 Description of the Data Editor

Element Description
Properties
Name Column where you enter the name (symbol) of the instance or data type
Type Column where you select the variable type.
Address Column where you reference the variable instance with an address in the
controller (located instance).
Value Column where you initialize the variable.
Comment Column where you enter the comment for the variables.

NOTE: The different fields can be assigned parameters (see page 404).

Tab: Variables
The Variables tab enables the administration of variable instances that belong to the families EDT/
DDT/ IODDT/ Device DDT

Tab: DDT Types

The DDT Types tab is used to manage derived data types (structures or arrays):

33003101 12/2015 331

Description of the Data Editor

Tab: Function blocks

The Function Blocks tab enables the management of the variable instances of type EFB or DFB
that belong to the function block family.

Tab: DFB Types

The DFB Types tab enables the administration of data types of derived function blocks (DFB).

332 33003101 12/2015

 Unity Pro
Creating derived data types (DDT)
33003101 12/2015

Chapter 10
Creating derived data types (DDT)

Creating derived data types (DDT)

Object of this chapter

This chapter guides the user through the creation and management of derived data types (DDT).

What Is in This Chapter?

This chapter contains the following topics:
Topic Page
Access to derived data types (DDT) 334
Creation of a derived data type (DDT) 335
Administration of derived data types and their elements 346
Creating Nested Derived Data Types 348
Save Derived Data Types (DDT) 355

33003101 12/2015 333

Creating derived data types (DDT)

Access to derived data types (DDT)

Procedure
You have the following two options to access the Data Editor to create derived data types:
 from the project structure view via the Variables and FB Instances directory,
 from the project structure view via the Derived Data Types directory,

Access via the "Variables and FB Instances" directory.

Step Action
1 In the project structure view, switch to the Variables and FB Instances
directory.
2 Select the Open command in the shortcut menu and the Data Editor will open.
3 Select the DDT Types tab in the Data Editor.

Example:

Access via the "Derived Data Types" directory.

Step Action
1 Switch to the Derived Data Types directory in the project structure view.
2 Select the Open command in the shortcut menu, which will open the Data
Editor that is automatically shown in the DDT Types tab.

334 33003101 12/2015

 Creating derived data types (DDT)

Creation of a derived data type (DDT)

Introduction
A derived data type corresponds with:
A derived data type is one of the following
 a structure type:
 Structure for input/output data, the type is not created by the user in this case, but by the
manufacturer (IODDT),
 Structure for other data; in this case the type is created by user.

 an array type.
 a reference type.

Memory Structure
The different PLC families vary in memory structure.

Creating a Structure Type

Step Action
1 Double click in the Data Editor in the DDT Types tab on the empty field (marked
by an arrow Name, and enter the name of the structure type (e.g. IDENTITY); the
default type is <Struct>. Enter a comment (optional).
2 Call up the newly created structure by clicking on +.
Example:

33003101 12/2015 335

Creating derived data types (DDT)

Step Action
3 Double-click on the corresponding Name field and enter the name of the first
element of the structure (e.g. Name, Age) and its type and comment (optional).
Example:

4 Double-click on the next cell (marked with an arrow) to enter the name of the next
element etc.
5 Go to the name of the structure type (IDENTITY) and select Analyze Type in the
shortcut menu.

Result: The structure was successfully analyzed (the symbol in front of the structure type has
changed):

336 33003101 12/2015

 Creating derived data types (DDT)

Result: The IDENTITY structure is created in the structure view of the project:

NOTE: Using the shortcut menu and the Open command you can access the IDENTITY structure.

Creating a Structure Type with an Extracted Bit

The user can create structure type using extracted bit.
The Bit Rank dialog box is accessible by right clicking on the instance or data type which type must
be:
 WORD
 UINT
 INT
 BYTE
 an extracted bit with a compatible parent

Step Action
1 Double click in the Data Editor in the DDT Types tab on the empty field (marked
by an arrow Name, and enter the name of the structure type (for example,
MyDDT); the default type is <Struct>. Enter a comment (optional).

33003101 12/2015 337

Creating derived data types (DDT)

Step Action
2 Call up the newly created structure by clicking on +:

3 Double-click on the corresponding Name field and enter the name of the first
element of the structure (e.g. Extract, Extract1) and its type and comment
(optional):

4 Double-click on the next cell (marked with an arrow) to enter the name of the next
element etc.

338 33003101 12/2015

 Creating derived data types (DDT)

Step Action
5 Select the variable to create the extracted bit and right-click on the variable.
The Edit Bit Rank is available in the contextual menu list:

Here below is the Bit Rank dialog box:

33003101 12/2015 339

Creating derived data types (DDT)

Step Action
6 Within the Bit Rank menu, the user can select to named each variable manually
or automatically using the Generate button.
NOTE: The Bit name can be edited manually directly in the Data Editor.
7 Go to the name of the structure type (MyDDT) and select Analyze Type in the
shortcut menu.

Result: The structure was successfully analyzed (the symbol in front of the array type has
changed):

340 33003101 12/2015

 Creating derived data types (DDT)

Result: The MyDDT structure is created in the structure view of the project:

NOTE: Using the shortcut menu and the Open command you can access the IDENTITY structure.

Creating an Array Type

Use this procedure to create an array type:

Step Action
1 Double click in the Data Editor in the DDT Types tab on the empty field (marked
by an arrow Name, and enter the name of the array type (e.g. SERIAL_NUMBER);
the default type is <Struct>. Enter a comment (optional).
2 Double click on the Type field, select <Array>, and confirm by pressing Enter.
Result: The Variable Type Selection dialog appears.
3 The ARRAY checkbox is automatically checked:
 Enter the size of the array in the corresponding field (for example, 1..6)
 In the libraries/families area select the types that should be displayed:
 the <EDT> directory for an elementary type
 the <Application> directory for a derived type already in the application
 the <Libset> directory for a derived type archived in a library

4 Confirm with OK.

33003101 12/2015 341

Creating derived data types (DDT)

Step Action
5 Change to the name of the array type and go to the shortcut menu and select
Analyze Type.
Result: The array was successfully analyzed (the symbol in front of the array type
has changed):

NOTE: Comments cannot be entered for the sub elements of the array type.
The array type SERIAL_NUMBERS is created in the project structure view:

NOTE: You can access the array of the SERIAL_NUMBER type in the context menu using the Open
command.

342 33003101 12/2015

 Creating derived data types (DDT)

Creating a Reference Type

Step Action
1 Double click in the Data Editor in the DDT Types tab on the empty field (marked
by an arrow Name, and enter the name of the reference type (e.g. MyRefInt); the
default type is <Struct>. Enter a comment (optional).
2 Double click on the Type field, select <Reference>, and confirm by pressing
Enter.
Result: The Variable Type Selection dialog appears.
3 The REF_TO checkbox is automatically checked. Select the reference data type,
in this example: INT.
4 Confirm with OK.
5 In the Data Editor, right-click the name MyRefInt and select Analyze Type.
Result: The reference was successfully analyzed (the symbol in front of the
reference type has changed).

The reference type MyRefInt is created in the Project Browser Structure view.
NOTE: You can access the reference of the MyRefInt type using the contextual menu using the
Open command.

33003101 12/2015 343

Creating derived data types (DDT)

Array of References
You cannot make directly, for example, an Array of REF_TO INT. You must first make a reference
DDT with type REF_TO INT as in the figure above. Then you make a new DDT type, an array of
the references.
In <Application>, select MyRefInt:

After confirming with OK and performing an Analyze Type, you obtain an array of references:

344 33003101 12/2015

 Creating derived data types (DDT)

Structure with References

This example shows the creation of an array of reference type variables:

Step Action
1 Double click DDT Types tab in the Data Editor on the empty field (marked by
an arrow Name, enter the name of the structured type and press ENTER. The
default type is <Struct>.
2 Double click Types and select <Array> in the drop-down menu.
3 Press ENTER to open the Variable Type Selection dialog.
4 Set the size of the array.
5 Select <Application>.
6 Select MyDDTRefINT.

The array of reference types example:

33003101 12/2015 345

Creating derived data types (DDT)

Administration of derived data types and their elements

Inserting an element into a derived data type

Execute the following steps:

Steps Action
1 Display the desired data type in the data editor in the DDT Types tab.
2 Place the cursor on the element in front of which you want to insert another element and select the
Insert new command in the shortcut menu.
Inserting an element into an address element

3 Enter the attributes of the element into the newly created row.

Deleting an element belonging to a derived data type

Carry out the following steps:

Step Action
1 Display the desired data type in the data editor in the DDT Types tab from which you wish to delete
the element.
2 Select the desired element.
3 Use the shortcut menu to select the Delete command.

NOTE: Elements belonging to protected data types cannot be deleted.

346 33003101 12/2015

 Creating derived data types (DDT)

Deleting a derived data type:

Carry out the following steps:

Step Action
1 Select the desired data type in the data editor in the DDT Types tab.
2 Using the context menu select the Delete command.

NOTE: Data types that exist as an instance in the application cannot be deleted.

33003101 12/2015 347

Creating derived data types (DDT)

Creating Nested Derived Data Types

Introduction
Data types that are part of the DDT family can be nested. The nesting can be organized as follows:
 in structures that contain arrays or structures
 in arrays that contain arrays or structures
 in a combination of these different nestings

348 33003101 12/2015

 Creating derived data types (DDT)

Array, that contains structures

Carry out the following steps:

Step Action
1 Double click in the Data Editor in the DDT Types tab on the empty field (marked by an arrow Name,
and enter the name of the array type (e.g. PERSONNEL); the default type is <Struct>. Enter a
comment (optional).
2 Double click on the Typefield, select <Array>, and confirm by pressing Enter.
Result: The Variable Type Selection appears.
3 The ARRAY checkbox is automatically checked:
 enter the size of the array in the corresponding field
 In the libraries/families area select the following:
 the <EDT> directory for an elementary type
 the <Applications> directory for a type already in the application
 the <Library> directory for an already archived type

See the following window:

4 Enable the DDT checkbox, which will display the derived data types.
5 Select the desired structure in the Name column and confirm with OK.
6 Change to the name of the array type and go to the context menu and select Analyze Type.

NOTE: Comments cannot be entered for the sub elements of the array type.
NOTE: Changing the boundaries of an anonymous array lead to the lost of the initial values of that
array. Those values must be re-entered after the modification.

33003101 12/2015 349

Creating derived data types (DDT)

Array of the type PERSONNEL that contains structures of the type IDENTITY:

350 33003101 12/2015

 Creating derived data types (DDT)

Structure containing a structure

Execute the following actions (provided a structure exists):

Step Action
1 Click on + to display the type of the structure in the DDT Types tab in the data editor, to which you
want to add an element.
2 Double click on the empty Namefield and enter the name of the new structure type element. Enter a
comment (optional).
3 Double-click on the corresponding Type field and click on .

The following window appears.

33003101 12/2015 351

Creating derived data types (DDT)

Step Action
4 In the libraries/families area select:
 the <EDT> index for an elementary type
 the <Applications> directory for a type that already exists in the application
 the <Library> for an already archived type

See the following example:

5 Enable the DDT checkbox, which will display the derived data types.
6 Select the desired structure in the Name column and confirm with OK.
7 Switch to the name of the structure type and select the Analyze Typeentry in the context menu.

352 33003101 12/2015

 Creating derived data types (DDT)

Example: IDENTITY structure that contains an INFORMATION structure of the STATUS type.

33003101 12/2015 353

Creating derived data types (DDT)

Combination of the different nestings.

The following example shows:
 a PERSONNEL array consisting of IDENTITY type structures
 IDENTITY structures containing STATUS type structures
 STATUS structures containing arrays of the NAME_CHILD type

Example:

354 33003101 12/2015

 Creating derived data types (DDT)

Save Derived Data Types (DDT)

Description of how to save

You can copy the data types you created into your library to reuse them in another project.

Filing a data type in the library

Carry out the following steps:

Step Action
1 Select the DDT Types tab in the Data Editor.
2 Select the data type that you want to save in the library.
3 Using the shortcut menu select the Copy into Library command.
The following dialog box opens:

4 Show the desired family to select the directory where you want to archive the
data type.
5 Confirm with OK.

NOTE: This procedure can also be started from the project browser in the Derived Data Types
directory.

33003101 12/2015 355

Creating derived data types (DDT)

Restoring a data type in the library

See loading an object from the library. (see page 307)

356 33003101 12/2015

 Unity Pro
Creating user function blocks (DFB)
33003101 12/2015

Chapter 11
Creating data types of user function blocks (DFB)

Creating data types of user function blocks (DFB)

Creation and Management of Data Types and Function Blocks (DFB)

At a Glance
See Derived Function Blocks (DFB) (see page 1251).
This chapter explains the DFB Types tab modes of the Data Editor with the following descriptions:
 accessing the DFB Types
 creating a DFB Type
 programming a DFB Type
 managing the elements of a DFB Type
 nestling of the DFB Types
 saving DFB Types

33003101 12/2015 357

Creating user function blocks (DFB)

358 33003101 12/2015

 Unity Pro
Managing instances of data belonging to the family of function blocks (EF)
33003101 12/2015

Chapter 12
Managing of instances of data belonging to the family of function blocks (EF)

Managing of instances of data belonging to the family of

function blocks (EF)

Object of this chapter

This chapter guides the user through the creation and management of data instances belonging to
block function types such as:
 Elementary function blocks (EFB),
 Derived function blocks (DFB).

What Is in This Chapter?

This chapter contains the following topics:
Topic Page
Creating / Deleting a variable instance of function blocks (EFB/DFB) 360
Displaying function block variable instances in the editor 363
Changing the attribute for variable instances in a function block 366

33003101 12/2015 359

Managing instances of data belonging to the family of function blocks (EF)

Creating / Deleting a variable instance of function blocks (EFB/DFB)

Creating a function block instance

Carry out the following steps:

Steps Actions
1 In the Data Editor select the function blocks tab.
2 Double-click the empty cell for Name (marked with an arrow), enter the name of the instance and
confirm by pressing the Enterbutton.
3 Double-click on the corresponding Type field and click on .

The following window appears:

360 33003101 12/2015

 Managing instances of data belonging to the family of function

Steps Actions
4 In the libraries/families area select the following:
 the <Applications> directory for a type already in the application,
 the <Library> directory for an already archived type.

Example: Select an EFB type archived in the Diagnostics library:

5 In the Name column select the EFB or DFB type and confirm with OK.

33003101 12/2015 361

Managing instances of data belonging to the family of function blocks (EF)

Example:

Deleting a function block instance

Instances that are accessed at least once cannot be deleted in the data editor.
Example from an ST section:
FBI_1(IN:=TRUE, OUT=>VarA);
The application explained above will block the deletion because FBI_1 is accessed.
VarA:=FBI_1.OUT
The application explained above will not block the deletion because FBI_1 is not accessed.

362 33003101 12/2015

 Managing instances of data belonging to the family of function

Displaying function block variable instances in the editor

Display sequence in a column

The variable instances can be displayed in ascending or descending alphabetical order. This
sequence will be used in a column chosen by you.
To do this, click on the area that contains the name of the column in question and the arrow will
turn blue.
Sorting in descending alphabetical order in the column Name

Sorting in ascending alphabetical order in the column Type

33003101 12/2015 363

Managing instances of data belonging to the family of function blocks (EF)

Displaying elements from one function block instance

To show the elements that belong to an instance of the function block type, carry out the following
actions:

Step Action
1 In the Data Editor select the function blocks tab.
2 Click on the + beside the instance of the desired function block type and the
elements will then be shown on screen.
3 Carry out the procedure again if you want to display the interface data or the
internal data for the function block on the screen.

Example: Display the instance Control_Process of the type EFB

364 33003101 12/2015

 Managing instances of data belonging to the family of function

Displaying the attributes

For an unopened window Data Properties:

Step Action
1 In the Data Editor select the function blocks tab.
2 Select the variable instance.
3 From the context menu select the command Data Properties and the attributes
will be displayed in a window.

Example:

For a window that is already open Data Properties:

After the instance has been chosen, the window Data properties is updated automatically with the
display for the attribute in question.

Sorting the variable instances

See Filtering of Data, page 412.

33003101 12/2015 365

Managing instances of data belonging to the family of function blocks (EF)

Changing the attribute for variable instances in a function block

Detailed information
The internal organization of a variable instance of function blocks (input / output parameters, public
/ private variables, code) cannot be changed from the instances, but must be performed from the
type of the instance DFB Types) tab.
The changes listed below do not effect the internal organization of the function block, but rather its
instantiation.

Changing the name of an instance

Carry out the following steps:

Step Action
1 In the Data Editor select the function blocks tab.
2 Double-click on the instance name, enter the new name, and confirm with Enter.

NOTE: the instance name can only be used once.

Changing the type of an instance

There are three options.
In the Data Editor Function blocks tab:

Double-click on the variable type and ... then...

enter the desired type, -

depending on the input, an automatic search is

carried out.
use the type field select the desired type.

select the type in the "FB type selection"

click the button
(see page 408) window.

366 33003101 12/2015

 Managing instances of data belonging to the family of function

Reactions to type changes of an instance.

If the type of an FB instance is changed in the Data Editor, the access will be adjusted to the
instance.
The access is adjusted as follows:
 The connections are mapped with pin positions.
Note: Compatibility of data types will not be checked, which means that errors may occur during
the analysis following the adjustment.
 Excess pins of the new type remain unused.
 The connections of pins that no longer exist in the new type are lost.

IL and ST sections:
If necessary, formal parameters in IL and ST sections will be renamed according to the new block
during formal access. The number of actual parameters will be adjusted during informal access.
NOTE: Instance access in IL or ST sections will only be adjusted if required by the type change.
However, if an adjustment is made, the old access will be removed and replaced with a generated
access. This means that all comments and formatting contained in the old access will be lost.
FBD and LD sections
The new type will be displayed in the FBD and LD sections following the adjustment.

33003101 12/2015 367

Managing instances of data belonging to the family of function blocks (EF)

368 33003101 12/2015

 Unity Pro
Managing variable instances belonging to the EDT/DDT/IODDT/Device DDT families
33003101 12/2015

Chapter 13
Managing variable instances belonging to the EDT/DDT/IODDT/Device DDT families

Managing variable instances belonging to the

EDT/DDT/IODDT/Device DDT families

Object of this chapter

This chapter guides the user through the creation and management of variable instances
belonging to the following families:
 Elementary data types (EDT)
 Derived Data Types (DDT)
 Derived Data Types that reference IODDT inputs/outputs (input / output data types)
 Device Derived Data Types (Device DDT)

What Is in This Chapter?

This chapter contains the following topics:
Topic Page
Creation of EDT type variable instances 370
Creation of variable DDT type instances 375
Creating a type IODDT variable instance 382
Creating a Type Device DDT Variable instance 385
Managing an IODDT, DDT or an Array type instance 387
Creation of multiple variable instances 393
Displaying the variable instances in the editor 395
Changing attributes of variable instances 399
Creation of a Reference Type Instance 402

33003101 12/2015 369

Managing variable instances belonging to the EDT/DDT/IODDT/Device DDT families

Creation of EDT type variable instances

Instance of an Unlocated Variable

Creating the instance of an unlocated variable:

Step Action
1 Select the Variables tab in the data editor.
2 Double-click the empty cell Name (marked with an arrow) and enter the name
of the instance.
3 Double-click the Type cell and enter the type of the instance.
4 Enter a comment if necessary.

Example:

370 33003101 12/2015

 Managing variable instances belonging to the EDT/DDT/IODDT/De-

Instance of a Referenced Variable

Creating an instance of a Referenced variable:

Step Action
1 Select the Variables tab in the data editor.
2 Double-click the empty cell Name (marked with an arrow) and enter the name
of the instance.
3 Double-click the Type cell and enter REF_TO and the type referenced for this
instance.
4 Enter the initial value (see page 372) of the variable instance.

Example:

33003101 12/2015 371

Managing variable instances belonging to the EDT/DDT/IODDT/Device DDT families

Initial Value of a Reference Type Variable

To set an initial value to a variable of reference type

Step Action
1 In the Variables tab of the Data Editor, select the reference type variable to
be initialized.
2 Double-click Value.
3 Enter REF(VarName), where VarName is the variable referenced by the
Instance of the Referenced Variable.

Example:

372 33003101 12/2015

 Managing variable instances belonging to the EDT/DDT/IODDT/De-

Instance of a Located Variable

Creating an instance of a located variable:

Step Action
1 Select the Variables tab in the data editor.
2 Double-click on the empty cell Name (marked with an arrow) and enter the
name of the instance.
3 Double-click on the Type cell and enter the type of the instance.
4 Double-click on the Address cell and enter the storage address for the
controller.
5 Enter a comment if necessary.

NOTE: Several different instances can be assigned to one address (multiple assignment).
Example:

33003101 12/2015 373

Managing variable instances belonging to the EDT/DDT/IODDT/Device DDT families

Instance with Direct Addressing

Creating an instance with direct addressing

Step Action
1 Double-click on the empty Address cell and enter the storage address for the
controller.
2 Enter a comment if necessary.

Example:

374 33003101 12/2015

 Managing variable instances belonging to the EDT/DDT/IODDT/De-

Creation of variable DDT type instances

Structure type instance

Creating a Structure type instance:

Step Action
1 Select the Variables tab in the data editor.
2 Double-click on the empty cell Name (marked with an arrow) and enter the name of the instance. Enter
a comment (optional).
3 Double-click on the corresponding Type field and click on.

The following window appears.

4 In the libraries/families area select the following:

 the <Application> directory for an existing type in the application.
 the <Libset> directory for an already archived type.

5 Enable the DDT checkbox, which will display the derived data types.
6 Select the desired structure type in the Name column and confirm with OK.
7 Fill out the Value column to initialize the elements of the structure. To carry out this task, click on + to
show the structure.

33003101 12/2015 375

Managing variable instances belonging to the EDT/DDT/IODDT/Device DDT families

Example:

NOTE: The comments will be transferred to the selected structure type, but they may be changed
for the applicable instance.

376 33003101 12/2015

 Managing variable instances belonging to the EDT/DDT/IODDT/De-

Instance of a non-typical array.

What is a non-typical array?

NOTE: My_Tab1 and My_Tab2 are two identical instances. The difference is that the type of the
My_Tab1 instance was previously defined (the name of the Type is Tab) while the type of the
My_Tab2 instance was defined during instancing.
Creating an instance for a non-typical array:

Step Action
1 Select the Variables tab in the data editor.
2 Double-click on the empty cell Name (marked with an arrow) and enter the name of the instance.
Enter a comment (optional).
3 Double-click on the corresponding Type field and click on.

The following window appears.

33003101 12/2015 377

Managing variable instances belonging to the EDT/DDT/IODDT/Device DDT families

Step Action
4 Enable the Array check box and
 fill in the field with the size of the array (example 1..6),
 In the libraries/families area select the types that should be displayed:
 the <EDT> directory for an elementary type,
 the <Application> directory for an existing derived type in the application,
 the <Libset> directory for a derived type archived in a library.

 Select the type for the elements of the array in the Name column (Example: STRING for an EDT).

Example:

Confirm with OK.

5 Fill out the Value column to initialize the elements of the array as needed. To carry out this task, click
on + to show the elements.

378 33003101 12/2015

 Managing variable instances belonging to the EDT/DDT/IODDT/De-

Example:

NOTE: Enter comments for the sub-elements of this instance of a non-typical array.

33003101 12/2015 379

Managing variable instances belonging to the EDT/DDT/IODDT/Device DDT families

Type Array instance

Creating an Array type instance:

Step Action
1 Select the Variables tab in the data editor.
2 Double-click on the empty cell Name (marked with an arrow) and enter the name of the instance.
Enter a comment (optional).
3 Double-click on the corresponding Type field and click on.

The following window appears.

4 In the libraries/families area select the following:

 the <Applications> directory for a type already in the application,
 the <Libset> directory for a derived type archived in a library.

5 Enable the DDT checkbox, which will display the derived data types.
6 Select the desired array type in the Name column and confirm with OK.
7 Fill out the Value column to initialize the elements of the array as needed. To carry out this task, click
on + to show the elements.

380 33003101 12/2015

 Managing variable instances belonging to the EDT/DDT/IODDT/De-

Example:

NOTE: Comments cannot be entered for the sub elements of this instance of an array.
NOTE: If you resize an array variable type, you will lose the comments and the initial values of the
elements of the array.

33003101 12/2015 381

Managing variable instances belonging to the EDT/DDT/IODDT/Device DDT families

Creating a type IODDT variable instance

Type IODDT instance

The data types (structures) have been predefined by the manufacturer and contain I/O language
objects belonging to the channel of an application specific module (or the module itself).
Perform the following steps to create a type IODDT instance:

Step Action
1 Select the Variables tab in the data editor.
2 Double-click on the empty cell Name (marked with an arrow) and enter the name of the instance.
3 Double-click on the corresponding Type field and click on it .

The following window appears.

382 33003101 12/2015

 Managing variable instances belonging to the EDT/DDT/IODDT/De-

Step Action
4 In the Library/Family area, display the <Catalog> index.
The following window appears.

5 Select the Type of Controller, Function and the corresponding IODDT Type.
Confirm with OK.

Example: Instance ENTRY_PRESSURE of Type T_ANA_IN_BMX:

33003101 12/2015 383

Managing variable instances belonging to the EDT/DDT/IODDT/Device DDT families

Linking to the application specific module

Step Action
1 Select the Variables tab in the data editor.
2 Enable the IODDT checkbox, which will display instances of Type IODDT.
3 Select the IODDT instance based on which the link will be created.
4 Enter the address of the module or its future storage location in the Address column (it is not
necessary to configure the module during this phase).
Example:

Rules
Follow the rules below:
 An IODDT data type cannot be nestled in a DDT data type.
 An IODDT data type cannot be nestled in another IODDT data type.
 A public or private variable of a DFB cannot be an IODDT type.
 An input / output parameter of a DFB may be of Type IODDT. However, you can only use those
IODDT types that are listed in the Variable Type Selection menu.
 An IODDT instance cannot be accessed from a DFB section.

384 33003101 12/2015

 Managing variable instances belonging to the EDT/DDT/IODDT/De-

Creating a Type Device DDT Variable instance

Type Device DDT Instance

When adding an I/O module to the remote rack the Unity Pro software will automatically
instantiated the associated Device DDT structure.
Each I/O modules are associated with one implicit device DDT instances.
Implicit Device DDT instances are created by default on device insertion and refreshed
automatically by the PLC. They contain the modules status, modules and channels health bits,
values of the modules inputs, values of the modules outputs, etc.
NOTE: Optional explicit DDT types are proposed in the data editor to support status or command
data used by explicit exchanges on a channel of an IO Modules in a remote I/O drop. Explicit DDT
instances are created manually by the user in the data editor and used as input or output parameter
with the function block managing the explicit exchange (see Unity Pro, I/O Management, Block
Library).
Perform the following steps to create a type Device DDT instance:

Step Action
1 Select the Variables tab in the data editor.
2 Double-click on the empty cell Name (marked with an arrow) and enter the
name of the instance.
3 Double-click on the corresponding Type field and click on it.

Results: The Variable Type Selection dialog appears.

4 In the Library/Family area, display the <Libset vx.0> index.
Where x indicated the Unity Pro software version.
5 Select the I/O Management and the corresponding Device DDT Type.
6 Confirm with OK.

33003101 12/2015 385

Managing variable instances belonging to the EDT/DDT/IODDT/Device DDT families

Example: Instance COM_DeviceDDT of Type T_M_COM_NOM:

Linking to the Application Specific Module

Use this procedure:

Step Action
1 Select the Variables tab in the data editor.
2 Enable the Device DDT checkbox, which will display instances of Type Device DDT.
3 Select the Device DDT instance based on which the link will be created.
4 Enter the address of the module or its future storage location in the Address column (it is not
necessary to configure the module during this phase).
Example:

386 33003101 12/2015

 Managing variable instances belonging to the EDT/DDT/IODDT/De-

Managing an IODDT, DDT or an Array type instance

Adding an alias
An alias name can be given to all elements of an IODDT, DDT or an Array type instance of
application.
The aliases can be created with the following rules:
 The alias descriptions are only allowed for elements of type IODDT, DDT or an Array.
 The type and address for an alias cannot be changed as these attributes are defined by the
IODDT, DDT or an Array
 Name and Comment can be changed.
 The alias displays the initial value of a DDT or Array element.

This procedure below is used for customizing elements used to make up a DDT instance, however
the procedure is the same for an IODDT or Array instance.

Step Action
1 Create one or more variable instances you want to customize that are identical with the elements of
the IODDT / DDT / Array.
For example AliasValue and AliasValid:
DED Data Editor

Variables DDT Types Function blocks DFB Types

Filter
Name = * EDT DDT IODDT
Name Type Address Value Comment
AliasValue INT
AliasValid BOOL
DDT_Inst1 My_DDT %MW10
Value INT %MW10
Valid BOOL %MW11
History ARRAY[0..4] OF INT %MW12
History[0] INT %MW12
History[1] INT %MW13
History[2] INT %MW14
History[3] INT %MW15
History[4] INT %MW16
Complement Infos %MW17
TestNr INT %MW17
Errors INT %MW18

2 Select an element of the DDT_Inst1 instance (for example Value) that you want to assign to the
previously created AliasValue instance.
Alternatively, the user can also assign a new symbol as alias. In this case the alias variable is
automatically be created with the type of the current element.

33003101 12/2015 387

Managing variable instances belonging to the EDT/DDT/IODDT/Device DDT families

Step Action
3 Using the shortcut menu select the Properties command.
The Data properties field opens:
Data Properties : DDT_Inst1.Value
General attributes

Name Value
Path name DDT_Inst1.Value
Name Value
Comment
RW program
Type INT
Category <EDT>
Size 2
Value
Address
Alias

4 In the Alias area enter the element AliasValue and then do the same for all elements that you want
to assign.
Along with the alias names and the elements of the DDT a symbol is shown.
DED Data Editor

Variables DDT Types Function blocks DFB Types

Filter
Name = * EDT DDT IODDT
Name Type Address Value Alias
AliasValid BOOL %MW10
DDT_Inst1 My_DDT %MW10
Value INT %MW10 AliasValue
Valid BOOL %MW11

NOTE: The user can directly enter the AliasValue in the Alias column.

388 33003101 12/2015

 Managing variable instances belonging to the EDT/DDT/IODDT/De-

The "Data Properties" window

The Data properties window can be opened from the IODDT structure, DDT structure or an
Array element. In such a case Alias is the structure attribute; it contains the names of the
variables.
Example:
Data Properties : DDT_Inst1.Value
General attributes

Name Value
Path name DDT_Inst1.Value
Name Value
Comment
RW program
Type INT
Category <EDT>
Size 2
Value
Address
Alias AliasValue

The Data properties window can also be opened from the Alias instance. In such a case Alias
of is an instance attribute; it contains the names of the elements of the IODDT structure, DDT
structure or an Array element.
Example:
Data Properties : AliasValue
General attributes

Name Value
Name AliasValue
Comment
Address
RW program
Alias of DDT_Inst1.Value
Constant
Save
Global data NO
Owner
Type INT
Category <EDT>
Size 2
Used 0
Custom

33003101 12/2015 389

Managing variable instances belonging to the EDT/DDT/IODDT/Device DDT families

Disconnecting an alias

Step Action
1 Select the element from the appropriate IODDT structure, DDT structure or Array element.
2 From the shortcut menu select the command Properties, and the following dialog box will appear.
Dialog box:
Data Properties : DDT_Inst1.Value
General attributes

Name Value
Path name DDT_Inst1.Value
Name Value
Comment
RW program
Type INT
Category <EDT>
Size 2
Value
Address
Alias AliasValue

3 Double-click on the target alias, delete the element in edit mode (AliasValue) and confirm.
The symbols shown on the element disappear:
DED Data Editor

Variables DDT Types Function blocks DFB Types

Filter
Name = * EDT DDT IODDT
Name Type Address Value Alias
AliasValid BOOL %MW10
DDT_Inst1 My_DDT %MW10
Value INT %MW10
Valid BOOL %MW11

NOTE: Alternatively, the user can directly delete the name in the column Alias or AliasOf.
NOTE: The alias instance returns to being a normal EDT instance and the attributes for the
element to which the instance is assigned are retained. The element for the IODDT structure, DDT
structure or an Array element contains the original manufacturer-defined name again.

Alias on sub fields of existing Alias

The user can set the alias on a sub field of an IODDT structure, DDT structure or an Array element
that is already an alias.
Example: AliasComplement is alias of DDT_Inst1.Complement and AliasTestNr is alias of
AliasComplement.TestNr.

390 33003101 12/2015

 Managing variable instances belonging to the EDT/DDT/IODDT/De-

Management of initial value for an alias

The initial value of an alias is the initial value on the sub field of DDT or Array. This sub field path
is given by attribute Alias OF. So when you get or set the initial value on an Alias in fact you get it
or set it on the sub field path given by attribute Alias OF.
Example: Initial value of alias "AliasValue" is the initial value given on path "DDT_Inst1.Value". (12
in the following example screen)

DED Data Editor

Variables DDT Types Function blocks DFB Types

Filter
Name = * EDT DDT IODDT
Name Type Address Value Comment Alias OF Global data
AliasComplement Infos NO
AliasTestNr INT AliasComplement NO
AliasValid BOOL NO
AliasValue INT 12 DDT_Inst1.V NO
DDT_Inst1 My_DDT NO
AliasValue INT 12 DDT_Inst1.V
Valid BOOL
History ARRAY[0..4] OF INT
History[0] INT
History[1] INT
History[2] INT
History[3] INT
History[4] INT
Complement Infos
TestNr INT
Errors INT

33003101 12/2015 391

Managing variable instances belonging to the EDT/DDT/IODDT/Device DDT families

Additionaly if we get or set initial value of “ DDT_Inst1.Complement.Errors” you will get or set initial
value on “ AliasComplement.Errors”, because “ AliasComplement” is an alias on “
DDT_Inst1.Complement” (see following figure).

DED Data Editor

Variables DDT Types Function blocks DFB Types

Filter
Name = * EDT DDT IODDT
Name Type Address Value Comment Alias OF Global data +
AliasComplement Infos NO
TestNr INT AliasComplement
Errors INT 37
AliasTestNr INT AliasComplement NO
AliasValid BOOL NO
AliasValue INT 12 DDT_Inst1.V NO
DDT_Inst1 My_DDT NO
AliasValue INT 12 DDT_Inst1.V
Valid BOOL
History ARRAY[0..4] OF INT
Complement Infos
TestNr INT
Errors INT 37

392 33003101 12/2015

 Managing variable instances belonging to the EDT/DDT/IODDT/De-

Creation of multiple variable instances

Procedure
There are two possibilities for this:
 using the Copy/Paste function,
 using the Import function.

Copying / pasting of instances.

The following procedure shows the method to create and rename an instance, following defined
rules, using the Copy/Paste function:

Step Action
1 Select the Variablestab in the data editor.
2 Select the desired instances (rows).

3 Using the context menu select the Copy command.

4 Select an open position (row) from which the instances will be copied.

33003101 12/2015 393

Managing variable instances belonging to the EDT/DDT/IODDT/Device DDT families

Step Action
5 From the context menu select the command Insert and the new instances will be created and renamed.
Example:

NOTE: Renaming Rules:

 From a name of the instance <Name>_<Number> or <Name> results after renaming

<Name>_<Number+1> or <Name_0>.

Importing instances
See "Importing Variables" (see page 1744).

394 33003101 12/2015

 Managing variable instances belonging to the EDT/DDT/IODDT/De-

Displaying the variable instances in the editor

Display sequence in a column

The variable instances can be displayed in ascending or descending alphabetical order. This
sequence will be used in a column chosen by you.
For this, click on the area that contains the name of the column in question which determines the
sorting order. After that the corresponding arrow will turn blue.
Sorting in descending alphabetical order in the column Name

33003101 12/2015 395

Managing variable instances belonging to the EDT/DDT/IODDT/Device DDT families

Sorting in ascending alphabetical order in the column Type

Display the elements of an instance of the "derived" type

To show the elements that belong to an instance of the "derived" type (structure or array), carry
out the following steps:

Step Action
1 Select the Variables tab in the data editor.
2 Enable the DDT check box.
2 Click on the + beside the instance of the desired structure or array type and this
will then be shown on screen.
3 Run the operation again if you want to display an interlaced element.

396 33003101 12/2015

 Managing variable instances belonging to the EDT/DDT/IODDT/De-

Example: Display the instance Person_1 of the structure type IDENTITY.

Displaying the instance attributes

For anunopened field Data Properties:

Step Action
1 Select the Variables tab in the data editor.
2 Select the desired instance.
3 Select the Properties command from the shortcut menu and the attributes will
be displayed in a window.

33003101 12/2015 397

Managing variable instances belonging to the EDT/DDT/IODDT/Device DDT families

Example:

For a window that is already open Data Properties:

After the instance has been chosen, the window Data properties is updated automatically with the
display for the attribute in question.

Sorting the variable instances

See Filtering of Data, page 412

398 33003101 12/2015

 Managing variable instances belonging to the EDT/DDT/IODDT/De-

Changing attributes of variable instances

Changing the name of an instance

Carry out the following steps:

Step Action
1 Select the Variables tab in the data editor.
2 Double-click on the instance name and enter the new name.

NOTE: The instance name can only be used once.

Changing the type of an instance

There are three options.
In the Data Editor select the Variables tab:

Double-click on the variable type and ... then...

enter the desired type

select the desired
type

use a Type from the list

select the appropriate
click the button type in the "Variables
type selection"
(see page 408)
window

Changing the address of an instance

Carry out the following steps:

Step Action
1 Select the Variables tab in the data editor.
2 Double-click on the instance address and enter the new address.

NOTE: Several different instances can be assigned to one address (multiple assignment).

33003101 12/2015 399

Managing variable instances belonging to the EDT/DDT/IODDT/Device DDT families

Changing an attribute in the "Data Properties" field

Carry out the following steps:

Step Action
1 Select the Variables tab in the data editor.
2 Select the desired instance.
3 Use the shortcut menu to select the Properties command.
4 In the Data properties field select the desired attribute.
5 Change the attribute.

Assigning an address for the CD_MOTOR1 instance (the variable is located):

Changing the attribute in several instances

Carry out the following steps:

Step Action
1 Select the Variables tab in the data editor.
2 Select the desired instances.
3 Use the shortcut menu to select the Properties command.
4 Select the desired attribute in the Data Properties window.
5 Change the attribute.

NOTE: For this functionality the following restrictions apply:

 names and addresses cannot be changed,
 the contents of the attribute to be changed must be the same for all selected instances,
 the change must be tolerated by all the instances selected,
 for sub-element instances with different superior elements, multiple selections are not possible.

400 33003101 12/2015

 Managing variable instances belonging to the EDT/DDT/IODDT/De-

Example: As can be seen in the following graphic, the three instances have the same type and can
be changed from Bool to Ebool.

Rule for instances of the type Structure

The internal organization of an instance of type structure (type, that belongs to the DDT family)
cannot be changed via the instance, but rather via the type of the instance (DDT type tab).
In contrast, the changes listed above (instance name, type, address) are applied directly to the
instances and do not affect the internal organization, only the instantiation of the type.

33003101 12/2015 401

Managing variable instances belonging to the EDT/DDT/IODDT/Device DDT families

Creation of a Reference Type Instance

Reference Type Instance

The reference type is used to create references to EDT, DDT and Device DDT variables.

Creating a Reference to a Variable

Creating a reference type instance:

Step Action
1 Select the Variables tab in the Data Editor.
2 Double-click on an empty cell Name (marked with an arrow) and enter the name of
the instance. Enter a comment (optional).
3 Double-click on the corresponding Type field and click.

The Data Editor: Variable Type Selection dialog opens.

4 Click the REF_TO checkbox.
5 Enable the EDT, DDT or Device DDT checkbox.
6 Select the desired type in the Name column and confirm with OK.
7 Fill out the Value column to initialize the variable by typing the name of the variable
to be referenced.

Example of the Data Editor with a reference to a variable:

402 33003101 12/2015

 Unity Pro
General Functions
33003101 12/2015

Chapter 14
General Functions

General Functions

Object of this chapter

This chapter guides the user through the use of the general features available in the data editor.

What Is in This Chapter?

This chapter contains the following topics:
Topic Page
Configuring the Data Editor columns 404
Description of the Data Editor: Variable type selection 408
Filtering of Data 412
Exporting a subset of variables 416
Analyze DDT and DFB Data Types 417
Purge of Unused Instances 418
Local printing of data 420
Save the context of the Data Editor 421

33003101 12/2015 403

General Functions

Configuring the Data Editor columns

Introduction
In every Data Editor tab you can configure the column display (a default configuration is
suggested). This lets you:
 define the columns you want to display,
 define the sequence for the columns shown.

Columns Available
The following table showns the different columns available in the Data Editor under various tabs.

Column Name Description

Name name of the instance or data type
Type data type
Address address in the controller for referencing the variables
984 Address LL984 address of the variable (%Mx = 00000x, %Ix = 10000x,
%IWx = 30000x, %MWx = 40000x)
This column is only available for Quantum PLCs (but not for
Quantum Safety PLCs).
Value initial value for the variables
Comment comment for the variables
Custom free text for use of an external tool or for special user
requirements
Global data Shows if the variable is a variable that was swapped between
different stations via the network.
Global data number of the group (the variables) in which the variable is
- Group transported
Global data number for the unique display of a variable in the group (the
- ID variables)
Alias name selected by the user which makes it possible to change
an IODDT, DDT or an Array element to a name defined by the
manufacturer or the user
Alias of complete path of the variable sub-field on which user sets
Alias attribute
Save define if the variable accepts the mechanism for updating
initial values with current values.
Used number of times the variables are used in the program and in
other parts of the project (animation tables, user windows)
RW program access rights of the variable, read only or read and write by the
program.
Constant kind of variable, the variable is a constant or not.

404 33003101 12/2015

 General Functions

Column Name Description

Owner only for Device DDT, it displays the address of the modules
which owns this variable.
Scanned Variables attribute that you can use to tag a variable to be a scanned
variable by the PLC, through Ethernet for instance.
Exchange On STBY Only for M580 Hotstandby systems (see Modicon M580 Hot
Standby, System Planning Guide for, Frequently Used
Architectures), if checked, the variable or the function block
instance is automatically exchanged between Primary PLC
and Standby PLC. By default this attribute is checked.
Task Give the task in which a Variable, EFB instance or DFB
instance is used.
Retain If checked, the variable, EFB instance or DFB instance values
are automatically stored in the backup memory, if not checked
the values are lost on power cut. By default this attribute is
checked.
Descriptor descriptors (1 to 9) of variables
Descriptor 1 is displayed after selecting this column in the
Column Configuration dialog. Descriptors 2 to 9 can be
displayed using the + sign in the Descriptor column header.
No. order number of a function block
Version type version
Bit rank gives the bit rank of the variable in its structure type.
HMI when General Project Settings → Data Dictionnary → Only
HMI variables is checked, this reduces memory usage.
Time stamping select if a variable is time stamped or not and the kind of time
stamping, see the System time stamping variables
(see System Time Stamping, User Guide) or Applicative time
stamping variables (see Applicative Time Stamping with Unity
Pro, User Guide).
Time stamping gives the source of the time stamping
- Source
Time stamping gives the ID of the time stamped variable
- TS ID
R/W Rights of Referenced access rights of a Reference type instance, used when the
value reference dereference a read only variable, see the Reference
Access rights (see Unity Pro, Program Languages and
Structure, Reference Manual ).

33003101 12/2015 405

General Functions

Defining Columns

Step Action
1 Select the desired tab in the Data Editor.
2 Via the context menu open the Column Configuration dialog using Customize Columns.
The following dialog appears.

3 Check the check boxes that correspond to the columns you wish to display.
4 Confirm the changes using the command OK.

NOTE: The Name and Type columns are required.

Description of the buttons

Button Description
OK confirms the configuration and exits the dialog
Cancel discards the changes and exits the dialog
Default restores the default configuration
Help opens the Help of the Column Configuration dialog

406 33003101 12/2015

 General Functions

Changing the Columns Sequence

Step Action
1 Select the desired tab in the Data Editor.
2 Via the context menu open the Column Configuration dialog using Customize
Columns.
3 Place the cursor on the chosen attribute and move it to the desired location by
clicking on the two buttons to the right of the window.
4 Confirm by clicking OK.

NOTE: The first column must always correspond with the attribute Name.

33003101 12/2015 407

General Functions

Description of the Data Editor: Variable type selection

Introduction
The Data Editor: Variable Type Selection provides the following options:
 Selection:
 of derived data types (typical structures/arrays),
 the function block data types (EFB\DFB),

 Creating non-typical arrays.

At a Glance
Data Editor: You can access the variables type selection by double-clicking on the Type

column and clicking on in the Data Editor.

Depending on the tab used to start the editor for the selection of the data type, one of the following
windows is displayed:
Variables:

408 33003101 12/2015

 General Functions

DDT Types:

Function blocks:

NOTE: Access to the editor for the selection of the data types is not possible via the DFB types tab.

33003101 12/2015 409

General Functions

Description of the area Libraries/Families

This area contains directories and subdirectories where various selectable data types are
classified.
If you choose one of the directories or subdirectories, the types for the right-hand side of the
columns Name/Type/Comment are shown.
 The directory <Application> shows the data types used in the project:
 the Derived Data Types (DDT); the checkbox DDT must be enabled.
 the Derived Function Block (DFB); the DFB checkbox must be enabled.
 the Derived Data Types that refer to the inputs/outputs (IODDT); the IODDT checkbox must
be enabled.
 the data types for the elementary function blocks (EFB); the EFB checkbox must be enabled,
 the Device Derived Data Types (DDDT); the Device DDT checkbox must be enabled.

 the <EDT> directory shows the types for the elementary data,
 the <Libset> directory that is organized into special libraries contains the families made
available by the manufacturer or the functions archived by the user:
 the Derived Data Types (DDT); the DDT checkbox must be enabled.
 the data types for the sequence controls (SFC); the DDT checkbox must be enabled,
 the data types for the derived function blocks (DFB); the DFB checkbox must be enabled,
 the elementary function blocks (EFB); the EFB checkbox must be enabled,
 the Device Derived Data Types (DDDT); the Device DDT checkbox must be enabled.

 the <Catalog> directory that shows the derived data types that reference inputs/outputs
(IODDT) from the manufacturer; the IODDT checkbox must be enabled.

410 33003101 12/2015

 General Functions

ARRAY checkbox
If this checkbox is enabled, you can use the editor to select the array types to have a single size
or several sizes (maximum six dimensions).
Example: Array with two dimensions 10x4 Dint

Filtering
You can create filters in the data editor to display the data types according to your requirements.
The Name field is used to enter the name of the data type that you want to display in the
Name/Type/Comment area. You can use place holder symbols (* or ?) to carry out multiple search
operations.

Clicking on the button updates the display corresponding to the filter term defined in the
field Name.

Clicking on this button opens the Filtering data (see page 413) dialog box where you can
define various filter attributes.

Clicking on this button inverts the filter. The button changes from = to <> and vice versa.

33003101 12/2015 411

General Functions

Filtering of Data

Introduction
You can create filters in the data editor to display the data according to your requirements.
A filter is the sum of the conditions applied to various attributes.
In every tab, it is standard for all variable instances or data types to be shown.
The various filters you have defined are saved when the data editor is closed and restored when
it is opened again.

At a Glance
The filter parameterization in the data editor is determined depending on the tab chosen.
Description of the Data editor different fields depending on the tab:

Area In which table is it Purpose

available ?
Button All tabs Clicking on this button updates the display corresponding to the filter
term defined in the name field.

Button All tabs Clicking on this button opens the Filtering data dialog box where
you can define the conditions for the individual attributes.

Button All tabs Clicking on this button inverts the filter. The button changes from =
to <> and vice versa.

Name All tabs Field where the name (symbol) of the instance or the data type you
want to display can be entered. You can use the place holder (* or ?)
for this.
EDT Variables tab The enabled check box authorizes the display of the Elementary
Data Types (EDT).
EFB Function Blocks tab The enabled check box authorizes the display of the Elementary
Function Blocks (EFB).
DDT Variables tab The enabled check box authorizes the display of the Derived Data
Types (DDT).
DFB Function Blocks tab The enabled check box authorizes the display of the Derived
Function Blocks (DFB).

412 33003101 12/2015

 General Functions

Area In which table is it Purpose

available ?
IODDT Variables tab The enabled check box authorizes the display of the Derived Data
Types (DDT) that reference inputs/outputs (IODDT).
Device DDT Variables tab The enabled check box authorizes the display of the Derived Data
Types (DDT).

The dialog box Filtering data

The dialog box Filtering data makes it possible to:
 view the current filter conditions,
 change the current filter conditions,
 define new filter conditions.

NOTE: The contents of the Filtering data dialog box depends on the tab from which it was called.

Description of the dialog box columns Filtering data

Description:

Column Description
Name This column contains the attributes for the (Variables, DDT types,
Function blocks or DFB types) tab used to open the dialog box.
Check the box for the attributes that you want to filter.
Condition The column allows you to define the filter condition for every attribute.
Inverted Using this checkbox you can invert the filter condition for the attribute in
question.

Options for defining a filter for Variables:

Name Condition inverted disabled inverted enabled

Comment Free text All variables whose comment All variables whose comment
e.g. *motor* attribute contains the word attribute does not contain the
Motor are filtered. word Motor are filtered.
Type Free text All variables of data type Int are All variables not of data type
e.g. Int filtered. Int are filtered.
Address Free text All variables with the address All variables that do not have
e.g. %MW1 %MW1 are filtered. the address %MW1 are filtered.
Global data Yes All variables defined as global All variables not defined as
data are filtered. global data are filtered.
Alias Of Yes All variables defined as an alias All variables not defined as an
are filtered. alias are filtered.
Value User defined All variables defined with an All variables not defined with
initial value are filtered. an initial value are filtered.

33003101 12/2015 413

General Functions

Name Condition inverted disabled inverted enabled

Save Accept All variables that accept saving All variables that do not accept
and restore operations are saving and restore operations
filtered. are filtered.
Constants Yes All variables defined as All variables not defined as
constants are filtered. constants are filtered.
Custom Free text All variables are filtered if their All variables whose user-
e.g. *HMI* user-defined text (free text for defined text does not contain
use in an external tool or for the word HMI are filtered.
special user requirements)
contains the word HMI.
Used >0 All variables used in the project All variables not used in the
are filtered. project are filtered.
Owner Free text All variables which owner begins All variables which owner
e.g. \2.1\* with \2.1\ are filtered. doesn’t begin with \2.1\ are
filtered.
HMI Variable Yes All variables defined as HMI All variables not defined as
variable are filtered. HMI variable are filtered.
Scanned Variables Yes All variables defined as Scanend All variables not defined as
Variables are filtered. Scanned Variables are filtered.
Exchange On STBY Yes All variables defined as All variables not defined as
Exchange On STBY Variables Exchange On STBY are
are filtered. filtered.
Task Free text All variables which Task attribute All variables which Task
e.g. MAST is MAST are filtered. attribute is not MAST are
filtered.
Retain Yes All variables defined as Retain All variables not defined as
Variables are filtered. Retain are filtered.

Options for defining a filter for DDT types:

Name Condition inverted disabled inverted enabled

Comment Free text All DDT types whose comment All DDT types whose comment
e.g. *Motor* attribute contains the word attribute does not contain the
Motor are filtered. word Motor are filtered.

414 33003101 12/2015

 General Functions

Options for defining a filter for Function Blocks:

Name Condition inverted disabled inverted enabled

Comment Free text All function blocks whose All function blocks whose
e.g. *Motor* comment attribute contains the comment attribute does not
word Motor are filtered. contains the word Motor are
filtered.
Diag. Accept All function blocks that accept All function blocks that do not
the attribute Diag. are filtered. accept the attribute Diag. are
filtered.
Type Free text All function blocks of type TON All function blocks not of type
e.g. TON are filtered. TON are filtered.
Custom Free text All function blocks are filtered if All function blocks whose user-
e.g. *HMI* their user-defined text (free text defined text does not contain
for use in an external tool or for the word HMI are filtered.
special user requirements)
contains the word HMI.
Used >0 All function blocks used in the All function blocks not used in
project are filtered. the project are filtered.
Owner Free text All function blocks which owner All function blocks which owner
e.g. \2.1\* begins with \2.1\ are filtered. doesn’t begin with \2.1\ are
filtered.
HMI Variable Yes All function blocks defined as All function blocks not defined
HMI variable are filtered. as HMI variable are filtered.
Exchange On STBY Yes All function blocks defined as All function blocks not defined
Exchange On STBY Variables as Exchange On STBY are
are filtered. filtered.
Task Free text All function blocks which Task All function blocks which Task
e.g. MAST attribute is MAST are filtered. attribute is not MAST are
filtered.
Retain Yes All function blocks defined as All function blocks not defined
Retain Variables are filtered. as Retain are filtered.

Options for defining a filter for DFB types:

Name Condition inverted disabled inverted enabled

Comment Free text All DFB types whose comment All DFB types whose comment
e.g. *Motor* attribute contains the word attribute does not contain the
Motor are filtered. word Motor are filtered.
Diag. Accept All DFB types that accept the All DFB types that do not
attribute Diag. are filtered. accept the attribute Diag. are
filtered.
Protection Protected All protected DFB types are All non-protected DFB types
filtered. are filtered.

33003101 12/2015 415

General Functions

Exporting a subset of variables

Introduction
The chapter Import / Export, page 1719 explains how to export variables.
However, all variables and FB instances, and subsets, were always exported (EDT, DDT, IODDT,
EFB, DFB).
In addition, a subset of variables may be filtered out and/or selected via the Data Editor and only
this subset will then be exported.

Filter
Filter the variables as described in the chapter Filtering of Data, page 412.

Selecting
Click on a variable to select it in the Data Editor. You can select multiple variables by holding down
the Alt or Ctrl keys.

Export
Export the filtered or selected variables via the context menu (right-click).

416 33003101 12/2015

 General Functions

Analyze DDT and DFB Data Types

At a Glance
DDT (Derived Data Types) and DFB (Derived Function Block) will have one of the following status
after setup:
 Status "in Process",
 Status "after the analysis".
This means that the data are instantiated with a type that is in process. The created instance has
characteristics of the prior type that was analyzed prior to processing.
After the analysis, to the extent that the type has no errors, the applicable instances within the
application will be updated..

Local analysis of data

Running the local analysis checks the selected data type for compatibility with the corresponding
instances throughout the entire project.
For DFB types, each section of the type is analyzed separately..
Perform the following steps to start a local analysis:

Step Action
1 Select the desired data type in the DDT Types or DFB Types tab.
2 Select the Analyze Typecommand from the shortcut menu.
3 Check the result of the analysis in the Display Window on the lower part of
the window.

NOTE: Double-click on an error row in the display window to go to the source of the error.

Global analysis of data

Running the global analysis checks all selected data types for compatibility with the corresponding
instances throughout the entire project.
Perform the following steps to start a global analysis:

Step Action
1 Select the Generate> Analyze Project command in the menu.
2 Check the result of the analysis in the display window on the lower part of the
window.

NOTE: Double-click on an error row in the display window to go to the source of the error.

33003101 12/2015 417

General Functions

Purge of Unused Instances

Overview
To purge unused instances of EDTs, EFBs and DFBs the Data Editor tabs provide the respective
context menus.

Purge Unused Variable

The purge depends on the check boxes (EDT, DDT, IODDT and Device DDT), i.e. only the visible
data (of checked types) will be purged.

Step Action
1 Select the Variables tab of the Data Editor.
2 Right-click any column of the tab.
3 Select the menu command Purge Unused Variables from the context menu.
4 Confirm with Yes.
Result: The unused data will be purged.

Purge DDT Types

NOTE: The purge feature is not available for DDT types.

Purge Unused FB Instances

The purge depends on the check boxes (EFB, DFB), i.e. only the visible data (of checked types)
will be purged.

Step Action
1 Select the Function Blocks tab of the Data Editor.
2 Right-click any column of the tab.
3 Select the menu command Purge Unused FB Instances from the context
menu.
4 Confirm with Yes.
Result: The unused data will be purged.

NOTE: When a FFB is not available for a kind of PLC (after a section import for instance) but still
in the application (removed from the section but still in the list of the Application FFBs), the purge
feature should be used before building the application.

418 33003101 12/2015

 General Functions

Purge Unused Private Variables/DFB Types

From the context menu of the DFB Types tab two purge operations are accessible.

Step Action
1 Select the DFB Types tab of the Data Editor.
2 Right-click any column of the tab.
3 Select one of the two menu commands Purge Unused Private Data Instances
or Purge unused Types from the context menu.
4 Confirm with Yes.
Result: The unused data will be purged.

33003101 12/2015 419

General Functions

Local printing of data

Introduction
Printing is a user-defined process and is executed using the following items:
 selected tab,
 Filtering variables,
 Sorting variables,
 Using certain variables

How to print
Carry out the following steps:

Step Action
1 Select the user-defined adjustment of the printing process in the Data Editor:
 Select the tab,
 Select the filter (see page 412):
 Select the sorting order (alphabetically ascending or descending),
 Using structured variables

2 Select the File → Print menu command

or
use the key combination Ctrl+P
or

use the toolbar icon .

NOTE: Local printing takes the access security into consideration. Only information appearing in
the window is printed.
NOTE: If an IODDT, a DDT or an Array element of an instance has an alias, the instance is
displayed with the alias of the element as in the Data Editor.

420 33003101 12/2015

 General Functions

Save the context of the Data Editor

Principles
When you leave the Data Editor, the configuration of the editor (visual aspect) will be saved. This
includes:
 the size and position of the Editor window,
 the selected tab,
 the filter of the variables display,
 The configuration of the columns in each tab.
The following information will not be saved:
 An instance or variable type will be hidden when the Editor is reopened.
 The selection of single or multiple variables.

33003101 12/2015 421

General Functions

422 33003101 12/2015

 Unity Pro
Communication
33003101 12/2015

Part III
Communication

Communication

Subject of this Part

This part describes the communication editors.

What Is in This Part?

This part contains the following chapters:
Chapter Chapter Name Page
15 Presentation of the communication editors 425
16 Network Configuration 427
17 Configuration of X-Way Routing Premium Stations 435

33003101 12/2015 423

Communication

424 33003101 12/2015

 Unity Pro
Presentation of the communication tab
33003101 12/2015

Chapter 15
Presentation of the communication editors

Presentation of the communication editors

Presentation of the communication editors of the project browser

At a Glance
The communication editors allow you to configure and manage the different communication
entities at project level.
They are accessible through the project browser by clicking the Communication tab.

Illustration
The figure below shows an example of the project browser

33003101 12/2015 425

Presentation of the communication tab

426 33003101 12/2015

 Unity Pro
Network Configuration
33003101 12/2015

Chapter 16
Network Configuration

Network Configuration

Subject of this Chapter

This chapter presents the tools for configuring a network at the global level and at the station level.

What Is in This Chapter?

This chapter contains the following topics:
Topic Page
Network Configuration Principle Using Unity Pro 428
Creating a Logic Network 429
Configuring a Logic Network 431
Associating a Logic Network with Network Hardware 432

33003101 12/2015 427

Network Configuration

Network Configuration Principle Using Unity Pro

At a Glance
With Unity Pro, the installation of a network takes place from the application browser and from the
hardware configuration editor.
The method involves the following four steps:
 creation of a logic network,
 configuration of the logic network,
 declaration of the module or of the PCMCIA card (for Premium),
 association of the card or of the module with the logic network.
These four methods are presented further on in this documentation.
NOTE: The advantage of this method is that from the second step onwards, you can design your
communication application (you do not need the hardware to start working) and use the simulator
for functional testing of it.
NOTE: The first two steps are carried out in the project browser and the following two in the
hardware configuration editor.
This manual introduces the method. For details of the various network configurations, please refer
to the following documentation:
 Ethernet configuration for Premium (see Premium and Atrium Using Unity Pro, Ethernet
Network Modules, User Manual), Ethernet configuration for M340 (see Modicon M340 for
Ethernet, Communications Modules and Processors, User Manual), and Ethernet configuration
for Modicon M580,
 Modbus Plus configuration (see Premium and Atrium Using Unity Pro, Modbus Plus Network,
User Manual),
 Fipway configuration (see Premium and Atrium using Unity Pro, Fipway Network, User Manual).

428 33003101 12/2015

 Network Configuration

Creating a Logic Network

At a Glance
The first step in implementing a communication network is to create a logic network.

Creating a Logic Network

The following table describes how to create a network using the project browser.

Step Action
1 Expand the Communication directory in the project browser.
Result::

2 Right-click in the Networks sub-directory and select the New network option.
Result::

33003101 12/2015 429

Network Configuration

Step Action
3 Select the network that you want to create from the list of available networks and give
it a meaningful name.
Result: Example of an Ethernet network:

Note: You can also add a comment, if you so desire, by clicking on the Comment tab.
4 Click OK and a new logic network is created.
Result: We have just created the Ethernet network that appears in the project browser

Note: As you can see, a small icon indicates that the logic network is not associated
with any PLC hardware. Furthermore, the small blue "v" sign indicates that the project
needs to be rebuilt before it can be used in the PLC.

430 33003101 12/2015

 Network Configuration

Configuring a Logic Network

At a Glance
The second step in implementing a communication network is to configure a logic network.
This manual introduces the access to network configuration. For information on how to configure
the various networks, please refer to the following documentation:
 Ethernet configuration for Premium (see Premium and Atrium Using Unity Pro, Ethernet
Network Modules, User Manual), Ethernet configuration for M340 (see Modicon M340 for
Ethernet, Communications Modules and Processors, User Manual), and Ethernet configuration
for Modicon M580,
 Modbus Plus configuration (see Premium and Atrium Using Unity Pro, Modbus Plus Network,
User Manual),
 Fipway configuration (see Premium and Atrium using Unity Pro, Fipway Network, User Manual).

Configuring a Logic Network

The table below describes how to access the configuration of a network from the project browser.

Step Action
1 In the project browser, expand the directory tree under the Networks sub-tab
located in the Communication tab of the tree directory to display all the project
networks.
Example::

2 Double-click the network you want to configure to obtain the network configuration
window.
Note: The windows differ according to the network family selected. However, for all
networks, from this window it is possible to configure the Global Data, IPO
scanning, Peer Cop utilities, common words, etc.
Note: For Ethernet networks, an intermediate step is necessary, which involves
selecting the family of the module that will be used in the hardware configuration.

33003101 12/2015 431

Network Configuration

Associating a Logic Network with Network Hardware

At a Glance
The final step in implementing a communication network is to associate a logic network with a
network module, Modbus Plus card or Fipway card. Although the screens differ, the procedure is
the same for each network device.

How to Associate a Logic Network

The following table describes how to associate a logic network to a network device declared in the
hardware configuration editor.

Step Action
1 Open the hardware configuration editor.
2 Right-click the device (Ethernet module, Fipway PCMCIA card or Modbus Plus
PCMCIA card) that you wish to associate with a logical network.
3 Select the channel and function.
Result: For a TSX ETY 4103 module:

432 33003101 12/2015

 Network Configuration

Step Action
4 In the Network link field, select the network to be associated with the card.
Result:

5 Confirm your choice and close the window.

Result: The logic network is associated with the device. The icon associated with
this logic network changes and indicates the existence of a link with a PLC.
Furthermore, the rack, module and channel numbers are updated in the logic
network configuration screen. In our example we obtain the following project
browser:

33003101 12/2015 433

Network Configuration

434 33003101 12/2015

 Unity Pro
Configuration of X-Way Routing
33003101 12/2015

Chapter 17
Configuration of X-Way Routing Premium Stations

Configuration of X-Way Routing Premium Stations

Subject of this Chapter

This chapter presents the operating modes required for configuring X-Way routing Premium
stations.

What Is in This Chapter?

This chapter contains the following topics:
Topic Page
Configuration 436
Configuration of Multi-Network Services 437
Configuring an X-Way Router Module 439
Examples of X-Way Routing Stations 443
Examples of Partial Routing 447

33003101 12/2015 435

Configuration of X-Way Routing

Configuration

At a Glance
In an intermediate station, the management of several network couplers requires a configuration
phase in order to distribute the functional characteristics to the various network entities.

NOTE: Multi-network routing information is constructed at the station level at the time of
configuration of each bridge. No consistency check is done on routing data for the same network
architecture.

436 33003101 12/2015

 Configuration of X-Way Routing

Configuration of Multi-Network Services

At a Glance
In a station that supports various network modules, each network connection point is considered
as an address for the station. When configuring each module, it is necessary to define the list of
network numbers that are accessible for each connection point.
Depending on the processor selected during hardware configuration, a bridge station can only
manage 3 or 4 network modules. The table will therefore have a maximum of 4 elements.

Illustration
A specific screen allows entry of routing data for all the network modules of a station.

33003101 12/2015 437

Configuration of X-Way Routing

Elements and Functions

The following table describes the various zones in the configuration screen:

Label Field Function

1 Logical Used to display the logical network name.
network
2 Network type Used to display the network type.
3 Accessible Used:
networks  for the unshaded Logical Network zone, to enter the list of
networks accessible by this module,
 for the shaded Logical Network zones, to display the list of
networks accessible by these modules.
4 Available Used to select the networks accessible by a module configured
networks as a bridge.
A list of numbers from 1 to 127 shows the networks available
for a connection point. Each network number selected as being
accessible is removed from the list of available networks in
order to avoid configuration errors.

438 33003101 12/2015

 Configuration of X-Way Routing

Configuring an X-Way Router Module

At a Glance
Before configuring the module as an X-Way router, the station’s logical networks must be created.

Procedure
The following procedure is used to access, and then configure the station’s module as an X-Way
router.

Step Action
1 Open the Communication tab in your project browser and in the Routing
table tab, click the X-Way table tab.
Result: The following window appears.

If the list of accessible module networks is empty, the window appears

automatically (without double-clicking).

33003101 12/2015 439

Configuration of X-Way Routing

Step Action
2 Double-click the highlighted field in order to configure the first network.
Result: The Selection of accessible networks window appears.

3 Double-click the number of the required network from the Available networks
scroll list.
Result: The network number is assigned in the Access networks scroll list.
4 Perform operation 3 as many times as necessary to define all the networks
accessible by the module.
Once finished, proceed to step 5.
5 Confirm the selection by clicking OK.
6 Confirm the configuration of the X-Way router by closing the window or clicking
the Enable button in the toolbar.

440 33003101 12/2015

 Configuration of X-Way Routing

Removing the Bridge Function

It is possible to remove the bridge function from the module.

Step Action
1 Access the following X-Way window.

2 Click Delete network list.

3 Confirm the configuration

33003101 12/2015 441

Configuration of X-Way Routing

Removing Access to a Network

It is possible to remove access to a single network.

Step Action
1 Access the following X-Way window of the accessible networks.

2 Double-click the numbers of the accessible networks to be removed (left column).

Result: The network number is reassigned in the Available networks scroll list.
3 Confirm the selection by clicking OK.
4 Confirm the router configuration.

442 33003101 12/2015

 Configuration of X-Way Routing

Examples of X-Way Routing Stations

At a Glance
Each station must be configured in order to define the list of accessible networks.

33003101 12/2015 443

Configuration of X-Way Routing

Configuration of Station R1
The module at slot 2 can only access network 12.
The module at slot 4 can only access network 1 and 11.
The module at slot 5 can access networks 13 and 21.
The bridge configuration of the station is therefore as follows:

Configuration of Station R2
The module at slot 0 can only access network 11.
The module at slot 5 can access networks 1, 12, 13 and 21.
The bridge configuration of the station is therefore as follows:

444 33003101 12/2015

 Configuration of X-Way Routing

Configuration of Station R3
The module at slot 0 can access networks 13, 12, 1 and 11.
The module at slot 5 can only access network 21.
The bridge configuration of the station is therefore as follows:

Messaging
To use the communication function (see Unity Pro, Communication, Block Library) such as
Read_VAR for ethernet exchange between stations, configure the TCP/IP Messaging in the
Ethernet network configuration (see Premium and Atrium Using Unity Pro, Ethernet Network
Modules, User Manual) screen. In the Messaging tab, for each exchange set the IP address and
target XWay address.
For example if station R3 needs to communicate with station B, in R1Messaging tab:
 set the R2 IP address (139.255.255.4) in the field IP address, and
 set the B XWay address (11.4) in the field XWay address.
The following illustration shows the R1 Messaging tab:

For another example if station B needs to communicate with station A, in R2, Messaging tab:
 set the R1 IP address (139.255.255.5) in the field IP address, and
 set the A XWay address (21.7) in the field XWay address.

33003101 12/2015 445

Configuration of X-Way Routing

The following illustration shows the R2 Messaging tab:

446 33003101 12/2015

 Configuration of X-Way Routing

Examples of Partial Routing

At a Glance
When configuring a module as a bridge, it is possible to assign to it only a part of the available
networks, instead of all of them. This selection is used to define a partial routing.

Illustration
Each station must be configured in order to define the list of accessible networks.

33003101 12/2015 447

Configuration of X-Way Routing

Configuration of Station R1
The module at slot 2 is not involved in the routing of data.
The module at slot 4 can access networks #1 and #11.
The module at slot 5 can access networks #13 and #21.
The bridge configuration of the station is therefore as follows:

Configuration of Station R2
The module at slot 0 can only access network #11.
The module at slot 5 can access networks #1, #13 and #21. Network #12 is inaccessible.
The bridge configuration of the station is therefore as follows:

448 33003101 12/2015

 Configuration of X-Way Routing

Configuration of Station R3
The module at slot 0 can access networks #13, #1 and #11. Network #12 is no longer accessible.
The module at slot 5 can only access network #21.
The bridge configuration of the station is therefore as follows:

33003101 12/2015 449

Configuration of X-Way Routing

450 33003101 12/2015

 Unity Pro
Programming
33003101 12/2015

Part IV
Programming

Programming

Subject of this part

This part describes the programming editors.

What Is in This Part?

This part contains the following chapters:
Chapter Chapter Name Page
18 Accessing Tasks and Sections 453
19 Unity Pro Software Options 515
20 Common Function for graphical language 575
21 FBD Editor 611
22 LD Editor 709
23 SFC Editor 861
24 Common Function for Textual Language 1007
25 IL Editor 1041
26 ST Editor 1073
27 LL984 Editor 1111
28 Programming Languages Data Selection Dialog Box 1181
29 I/O Objects tab 1201
30 Memory Tab 1219
31 Type Library Browser 1225
32 Search/Replace Tool 1235
33 User's Function Blocks 1251

33003101 12/2015 451

Programming

452 33003101 12/2015

 Unity Pro
Accessing Tasks and Sections
33003101 12/2015

Chapter 18
Accessing Tasks and Sections

Accessing Tasks and Sections

Overview
This section describes how to access tasks and sections.

What Is in This Chapter?

This chapter contains the following sections:
Section Topic Page
18.1 Access to Tasks 454
18.2 Accessing Sections 457

33003101 12/2015 453

Accessing Tasks and Sections

Section 18.1
Access to Tasks

Access to Tasks

Subject of this Section

This section covers the creation and modification of program tasks.

What Is in This Section?

This section contains the following topics:
Topic Page
Create and Configuration of a Task 455
Displaying and Modifying Task Properties 456

454 33003101 12/2015

 Accessing Tasks and Sections

Create and Configuration of a Task

General
The first operation you need to perform to create an application program is to define the tasks.
By default, only the master task is proposed. It is possible to create the following tasks:
the FAST task and the auxiliary tasks AUX0 to 3.
NOTE: For a fipio (see Premium and Atrium Using Unity Pro, Fipio Bus, Setup Manual)
configuration, the window displayed is different.

Creating a Task
Carry out the following actions:

Step Action
1 In the project browser, double-click on the program directory.
The MAST directory appears in the Tasks directory.
2 Right-click on the Tasks directory, and then execute the New task... command from
the contextual menu.
3 Click on New task..., and the following dialog box appears:

4 Select the task:

 FAST: Fast task
 AUX 0 , AUX1, AUX2 or AUX3: Auxiliary tasks (for processors with auxiliary tasks)

5 Select the type of scanning:

 Periodic
 or cyclic (for master task only)

6 Set the task period.

7 Set the Watchdog value which must be greater than the period value.
8 The Comment tab can be used to add a comment to describe the role of the task for
example.

33003101 12/2015 455

Accessing Tasks and Sections

Displaying and Modifying Task Properties

General
This procedure should be followed to display and/or modify the properties of an existing task.
NOTE: For a fipio (see Premium and Atrium Using Unity Pro, Fipio Bus, Setup Manual)
configuration, the window displayed is different.

Task Properties
Carry out the following actions:

Step Action
1 In the project browser, double-click on the program directory.
The MAST directory (as well as the FAST and AUX directories if they have been
created) appears in the Tasks directory.
2 Right-click on the MAST, FAST, or AUX directory, and then execute the Properties
command from the contextual menu.
3 Click on Properties, and the following dialog box appears:

4 Select the type of task:

 Periodic
 or cyclic

5 If you have selected a periodic task, set the task period.

6 Set the Watchdog value which must be greater than the period value.
7 The Comment tab can be used to add a comment to describe the role of the task for
example.

456 33003101 12/2015

 Accessing Tasks and Sections

Section 18.2
Accessing Sections

Accessing Sections

Overview
This section describes accessing sections.

What Is in This Section?

This section contains the following topics:
Topic Page
Creating an FBD, LD, IL, or ST Section 458
Properties Dialog Box for FBD, LD, IL, or ST Sections 461
Creating SFC sections 467
Properties Dialog Box for SFC Sections 470
Creating action, transition and macro sections 477
Action, transition and macro sections properties dialog box 478
Create a Sub-Program Section (SR) 481
Property Dialog of the Sub-Program Sections 483
Creating a Timer Event Section 486
Properties dialog box for Timer Event Sections 489
Create an I/O Event Section 493
Property Dialog of I/O Event Sections 496
Opening a Section 500
Deleting sections 501
Execution order of sections 502
Creating LL984 Segments and Networks 503
Modifying LL984 Segment Properties 508
Modifying LL984 Network Properties 510
Scheduling LL984 Segments and Network 512
Deleting, Cutting, Copying and Pasting LL984 Segments and Network 513

33003101 12/2015 457

Accessing Tasks and Sections

Creating an FBD, LD, IL, or ST Section

Introduction
Create FBD, LD, IL, or ST sections for Modicon M340:
 in the MAST and FAST tasks
 in offline and online mode

Create FBD, LD, IL, or ST sections for Modicon M580:

 in the MAST, FAST, AUX0, and AUX1 tasks
 in offline and online mode

Create FBD, LD, IL, or ST sections for Quantum, Premium and Atrium:
 in MAST, FAST, and AUX tasks
 in offline and online mode

Information for creating LD sections

An LD section contains 11-64 columns and 17-2000 rows.
The number of columns is set in the Tools → Project Settings dialog in the Editors tab in the
Ladder Daigram (LD) area at Number of columns.
This setting only applies to sections to be created, not existing sections. Verify that you define the
number of columns before you create a new LD section.
(The number of rows and columns can be changed during the creation of section contents.)

Information for creating FBD sections

An FBD section contains 86,400 grids (number of rows x number of columns).
The number of rows and columns is set in the Tools → Project Settings dialog in the Editors tab
in the Function Block Diagram (FBD) area.
This setting only applies to sections to be created, not existing sections. Always define the number
of rows and columns before you create a new FBD section.
(The number of rows and columns can be changed during the creation of section contents.)

458 33003101 12/2015

 Accessing Tasks and Sections

Creating a section
Creating a section:

Step Action
1 Left-click the Sections directory of the desired task, or place the cursor using the arrow keys on
this directory.
2 Click the right mouse button or use Shift+F10 to select New Section in the context menu.
Result: The properties dialog box (see page 461) for the section is opened.
3 Enter the section name.
The section name must be unique in the entire project and conform to the general naming
conventions.
4 Select the programming language of the section.
5 Select the type of access protection if necessary from the Protection list box:
 None
No protection
 Read-Only
Write protection
 No read & write
Read and write protection
See also section Project Protection (see page 186).
6 Select the functional module to which the section is allocated from the Localization tab if
necessary.
See also section Functional module (see page 221).
7 Define a Boolean variable in the Condition tab with which the section can be
activated/deactivated (section active when variable=1) if required.
You have the following options to select variables:
 You can enter the name of the variable/address directly or copy it from the clipboard.
 Use the command button ...to open a variable selection dialog box (see page 330).

Activate the Can be forced check box when you want to force the variable.
8 Only applies to Quantum projects:
Assign a read RIO drop and a write RIO drop to the section in the Remote IO tab if required.
See also section Executing Quantum sections with distributed inputs/outputs (see Unity Pro,
Program Languages and Structure, Reference Manual ) in the Reference manual.
9 Enter a comment in the Comment tab if desired.
10 If you wish to create additional sections, confirm the entries with Apply. In this case, the Property
dialog box will remain open and you can generate additional sections.
If you do not wish to create additional sections, confirm the entries with OK. In this case, the
Property dialog box will close and the generated section will open automatically.

33003101 12/2015 459

Accessing Tasks and Sections

Displaying or modifying section properties

Displaying or modifying section properties:

Step Action
1 Left-click on the desired section, or place the cursor on this section with the arrow keys.
2 Select (right-click or Shift+F10 key combination) the Properties... menu command from the
shortcut menu..
Result: The properties dialog box (see page 461) for the section is opened.
3 Implement the desired changes.
4 Confirm all entries with OK.

Importing/exporting sections
See:
 Importing programs (see page 1735)
 Exporting programs (see page 1733)

460 33003101 12/2015

 Accessing Tasks and Sections

Properties Dialog Box for FBD, LD, IL, or ST Sections

Structure of the properties dialog box

The properties dialog box consists of four or five tabs depending on the platform of the project:
 General
Enter the name, the programming language and the type of access protection of the section in
this tab.
 Localization
You can enter the functional module of the section in this tab.
 Condition
You can enter a Boolean variable which can enable/disable the section in this tab.
 Remote IO
This tab is only available for Quantum projects.
Assign a read RIO drop and a write RIO drop to the section in this tab.
Assigning drops will remove them from the TASK I/O update routine and will be managed from
the section.
When disabling a section by a condition, the read and write of the assigned drops are still active.
 Comment
You can enter a comment in this tab.

General tab
Representation of the General tab:

33003101 12/2015 461

Accessing Tasks and Sections

Elements of the General tab:

Element Description
Name Enter the name of the section in this text box.
The section name must be unique in the entire project and conform to
the general naming conventions.
Language Select the programming language of the section from this list box.
Note: The programming language can only be defined for new
sections. The programming language cannot be changed for existing
sections.
Protection Select the type of access protection from this list box.
 None
No protection
 Read-Only
Write protection
 No read & write
Read and write protection
See also Section and Subroutine Protection (see page 186).
OK Generating a new section:
If you do not want to create any additional sections, click on this
command button to confirm the entries. In this case, the properties
dialog box will close and the generated section will open
automatically.
Displaying properties of an existing section:
Use this command button to accept the entries and close the
properties dialog box.
Apply Generating a new section:
If you want to create any additional sections, click on this command
button to confirm the entries. In this case, the properties dialog box will
remain open and you can generate additional sections. The generated
section will not open automatically.
Displaying properties of an existing section:
Use this command button to accept the entries without closing the
properties dialog box.

462 33003101 12/2015

 Accessing Tasks and Sections

Localization tab
Representation of the Localization tab:

Elements of the Localization tab:

Element Description
Task The task of the section is displayed in this field.
Functional module Select the functional module to which the section is to be allocated to
in this list box.
For detail, refer to chapter Functional Modules (see page 221).
OK Generating a new section:
If you do not want to create any additional sections, click on this
command button to confirm the entries. In this case, the properties
dialog box will close and the generated section will open
automatically.
Displaying properties of an existing section:
Use this command button to accept the entries and close the
properties dialog box.
Apply Generating a new section:
If you want to create any additional sections, click on this command
button to confirm the entries. In this case, the properties dialog box will
remain open and you can generate additional sections. The generated
section will not open automatically.
Displaying properties of an existing section:
Use this command button to accept the entries without closing the
properties dialog box.

33003101 12/2015 463

Accessing Tasks and Sections

Condition tab
Display of the Condition tab:

Elements of the Condition tab:

Element Description
Variable You can enter Boolean variables which can conditionally enable/disable the
section in this tab.
In this area, you can enter the following:
 Name
 You can directly enter the name of the variable/address or paste it
from the clipboard.
 Use the command button ... to open a variable selection dialog box
(see page 330).
 Comment
The comments about the selected variables are displayed in this text box.
Can be forced This check box indicates whether the selected variable can be forced or not.
OK Generating a new section:
If you do not want to create any additional sections, click on this command
button to confirm the entries. In this case, the properties dialog box will close
and the generated section will open automatically.
Displaying properties of an existing section:
Use this command button to accept the entries and close the properties
dialog box.
Apply Generating a new section:
If you want to create any additional sections, click on this command button
to confirm the entries. In this case, the properties dialog box will remain open
and you can generate additional sections. The generated section will not
open automatically.
Displaying properties of an existing section:
Use this command button to accept the entries without closing the properties
dialog box.

464 33003101 12/2015

 Accessing Tasks and Sections

Remote IO tab
Representation of the Remote IO tab (only for Quantum projects):

Elements of the Remote IO tab:

Element Description
Remote drop Select the remote drop to read/write from this list box.
Already configured drops are displayed in black; non-configured in red.
See also section Executing Quantum sections with distributed
inputs/outputs (see Unity Pro, Program Languages and Structure,
Reference Manual ) in the Reference manual.
Read > Use this button to accept the selected drop as the drop to read. I.e. when
processing starts on the current section, the inputs for this drop are read.
Write > Use this button to accept the selected drop as the drop to write. I.e. when
processing ends on the current section, the outputs for this drop are written.
Delete Use this command button to reset the selected read/write drops.
OK Generating a new section:
If you do not want to create any additional sections, click on this command
button to confirm the entries. In this case, the properties dialog box will close
and the generated section will open automatically.
Displaying properties of an existing section:
Use this command button to accept the entries and close the properties
dialog box.
Apply Generating a new section:
If you want to create any additional sections, click on this command button
to confirm the entries. In this case, the properties dialog box will remain
open and you can generate additional sections. The generated section will
not open automatically.
Displaying properties of an existing section:
Use this command button to accept the entries without closing the
properties dialog box.

33003101 12/2015 465

Accessing Tasks and Sections

Comment tab
Representation of the Comment tab:

Elements of the Comment tab:

Element Description
Text box A comment about the section can be entered in this text box.
OK Generating a new section:
If you do not want to create any additional sections, click on this
command button to confirm the entries. In this case, the properties
dialog box will close and the generated section will open
automatically.
Displaying properties of an existing section:
Use this command button to accept the entries and close the
properties dialog box.
Apply Generating a new section:
If you want to create any additional sections, click on this command
button to confirm the entries. In this case, the properties dialog box will
remain open and you can generate additional sections. The generated
section will not open automatically.
Displaying properties of an existing section:
Use this command button to accept the entries without closing the
properties dialog box.

466 33003101 12/2015

 Accessing Tasks and Sections

Creating SFC sections

Introduction
SFC sections can be created:
 only in the MAST task
 in offline and online mode

When creating an SFC section, the following three directories are created in addition to the actual
SFC section:
 Unused macros
In this directory, all macro sections are stored which were created but are no longer being used
(see page 874).
 Actions
This directory contains all Action sections (see page 944) for the current SFC section.
 Transitions
This directory contains all transition sections (see page 957) for the current SFC section.

Creating SFC sections

Creating SFC sections:

Step Action
1 Left-click the Sections directory for the MAST task or place the cursor on this
directory using the arrow keys.
2 Select (right-click or Shift+F10 key combination) the New Section menu
command from the shortcut menu.
Result: The properties dialog box (see page 470) for the section is opened.
3 Enter the section name.
The section name must be unique in the entire project and conform to the
general naming conventions.
4 Select the programming language SFC.
5 If necessary, assign an automation area from 0-15 to the section in the Area
number list box.
This automation area (area number) can be used as sorting criteria in the
diagnostic viewer (see page 1545).
It makes sense to assign the area number corresponding to the functional unit.
Example:
Cutting: No. 1
Milling: No. 2
Thread cutting: No. 3
In the example, the Area number must have the value 1, 2 or 3.
6 If you want an explicit acknowledgment of all diagnostic results for the SFC
section (e.g. exceeding the step monitoring times) to be required in the
diagnostic viewer (see page 1545), activate the Operator control check box.

33003101 12/2015 467

Accessing Tasks and Sections

Step Action
7 Select the type of access protection if necessary from the Protection list box:
 None
No protection
 Read-Only
Write protection
 No read & write
Read and write protection
See also Project Protection (see page 186).
8 Select the functional module to which the section is allocated from the
Localization tab if necessary.
See Functional module (see page 221).
9 Define a Boolean variable in the Condition tab with which the section can be
activated/deactivated (section active when variable=1) if required.
You have the following options to select variables:
 You can enter the name of the variable/address directly or copy it from the
clipboard.
 Use the command button ...to open a variable selection dialog box
(see page 330).
Activate the Can be forced check box when you want to force the variable.
10 Only applies to Quantum projects:
Assign a read RIO drop and a write RIO drop to the section in the Remote IO tab
if required.
See also Executing Quantum sections with distributed inputs/outputs (see Unity
Pro, Program Languages and Structure, Reference Manual ) in the Reference
manual.
11 Enter a comment in the Comment tab if desired.
12 If you wish to create additional sections, confirm the entries with Apply. In this
case, the Property dialog box will remain open and you can generate additional
sections.
If you do not wish to create additional sections, confirm the entries with OK. In
this case, the Property dialog box will close and the generated section will open
automatically.

468 33003101 12/2015

 Accessing Tasks and Sections

Displaying or modifying section properties

Displaying or modifying section properties:

Step Action
1 Left-click on the desired section, or place the cursor on this section with the
arrow keys.
2 Select (right-click or Shift+F10 key combination) the Properties... menu
command from the shortcut menu.
Result: The properties dialog box (see page 470) for the section is opened.
3 Implement the desired changes.
4 Confirm all entries with OK.

Importing/exporting sections
See sections:
 Importing programs (see page 1735)
 Exporting programs (see page 1733)

33003101 12/2015 469

Accessing Tasks and Sections

Properties Dialog Box for SFC Sections

Structure of the properties dialog box

The properties dialog box consists of five tabs for Quantum projects and four tabs for Modicon
M340, Premium, and Atrium projects:
 General
You can enter the name, the programming language, the type of access protection and
diagnostic settings for the section in this tab.
 Localization
You can enter the functional module of the section in this tab.
 Condition
You can enter a Boolean variable which can enable/disable the section in this tab.
 Remote IO
This tab is only available for Quantum projects.
Assign a read RIO drop and a write RIO drop to the section in this tab.
Assigning drops will remove them from the TASK I/O update routine and will be managed from
the section.
When disabling a section by a condition, the read and write of the assigned drops are still active.
 Comment
You can enter a comment in this tab.

General tab
Representation of the General tab:

470 33003101 12/2015

 Accessing Tasks and Sections

Elements of the General tab:

Element Description
Name Enter the name of the section in this text box.
The section name must be unique in the entire project and conform to
the general naming conventions.
Language Select the programming language of the section from this list box.
Note: The programming language can only be defined for new
sections. The programming language cannot be changed for existing
sections.
Area number This list box is used to assign an automation range to the section; see
also how to create an SFC section (see page 467).
This automation area (area number) can be used as sorting criteria in
the diagnostic viewer (see page 1545).
The valid range for Area number 0...15.
Operator control When you enable this check box, any diagnostics events occurring in
the SFC section (e.g. violation of the step supervision times) must be
acknowledged in the diagnostics viewer (see page 1545).
Protection Select the type of access protection from this list box.
 None
No protection
 Read-Only
Write protection
 No read & write
Read and write protection
See also Project Protection (see page 186) .
OK Generating a new section:
If you do not want to create any additional sections, click on this
command button to confirm the entries. In this case, the properties
dialog box will close and the generated section will open
automatically.
Displaying properties of an existing section:
Use this command button to accept the entries and close the
properties dialog box.
Apply Generating a new section:
If you want to create any additional sections, click on this command
button to confirm the entries. In this case, the properties dialog box will
remain open and you can generate additional sections.
Displaying properties of an existing section:
Use this command button to accept the entries without closing the
properties dialog box.

33003101 12/2015 471

Accessing Tasks and Sections

Localization tab
Representation of the Localization tab:

Elements of the Localization tab:

Element Description
Task The task of the section is displayed in this field.
Functional module Select the functional module to which the section is to be allocated to
in this list box.
See also Functional module (see page 221).
OK Generating a new section:
If you do not want to create any additional sections, click on this
command button to confirm the entries. In this case, the properties
dialog box will close and the generated section will open
automatically.
Displaying properties of an existing section:
Use this command button to accept the entries and close the
properties dialog box.
Apply Generating a new section:
If you want to create any additional sections, click on this command
button to confirm the entries. In this case, the properties dialog box will
remain open and you can generate additional sections.
Displaying properties of an existing section:
Use this command button to accept the entries without closing the
properties dialog box.

472 33003101 12/2015

 Accessing Tasks and Sections

Condition tab
Display of the Condition tab:

Elements of the Condition tab:

Element Description
Variable You can enter a Boolean variable which can conditionally
enable/disable the section in this tab.
In this area, you can enter the following:
 Name
 You can directly enter the name of the variable/address or
paste it from the clipboard.
 Use the command button ... to open a variable selection dialog
box (see page 330).
 Comment
The comments about the selected variables are displayed in this
text box.
Can be forced This check box indicates whether the selected variable can be forced
or not.
OK Generating a new section:
If you do not want to create any additional sections, click on this
command button to confirm the entries. In this case, the properties
dialog box will close and the generated section will open
automatically.
Displaying properties of an existing section:
Use this command button to accept the entries and close the
properties dialog box.

33003101 12/2015 473

Accessing Tasks and Sections

Element Description
Apply Generating a new section:
If you want to create any additional sections, click on this command
button to confirm the entries. In this case, the properties dialog box will
remain open and you can generate additional sections.
Displaying properties of an existing section:
Use this command button to accept the entries without closing the
properties dialog box.

Remote IO tab
Representation of the Remote IO tab (only for Quantum projects):

Elements of the Remote IO tab:

Element Description
Remote drop Select the remote drop to read/write from this list box.
Already configured drops are displayed in black; non-configured in
red.
See also section Executing Quantum sections with distributed
inputs/outputs (see Unity Pro, Program Languages and Structure,
Reference Manual ) in the Reference manual.
Read > Use this button to accept the selected drop as the drop to read. I.e.
when processing starts on the current section, the inputs for this drop
are read.
Write > Use this button to accept the selected drop as the drop to write. I.e.
when processing ends on the current section, the outputs for this drop
are written.
Delete Use this command button to reset the selected read/write drops.

474 33003101 12/2015

 Accessing Tasks and Sections

Element Description
OK Generating a new section:
If you do not want to create any additional sections, click on this
command button to confirm the entries. In this case, the properties
dialog box will close and the generated section will open
automatically.
Displaying properties of an existing section:
Use this command button to accept the entries and close the
properties dialog box.
Apply Generating a new section:
If you want to create any additional sections, click on this command
button to confirm the entries. In this case, the properties dialog box will
remain open and you can generate additional sections.
Displaying properties of an existing section:
Use this command button to accept the entries without closing the
properties dialog box.

Comment tab
Representation of the Comment tab:

33003101 12/2015 475

Accessing Tasks and Sections

Elements of the Comment tab:

Element Description
Text box A comment about the section can be entered in this text box.
OK Generating a new section:
If you do not want to create any additional sections, click on this
command button to confirm the entries. In this case, the properties
dialog box will close and the generated section will open
automatically.
Displaying properties of an existing section:
Use this command button to accept the entries and close the
properties dialog box.
Apply Generating a new section:
If you want to create any additional sections, click on this command
button to confirm the entries. In this case, the properties dialog box will
remain open and you can generate additional sections.
Displaying properties of an existing section:
Use this command button to accept the entries without closing the
properties dialog box.

476 33003101 12/2015

 Accessing Tasks and Sections

Creating action, transition and macro sections

Creating action, transition and macro sections

The descriptions are found in the following sections:
 Creating action sections (see page 944)
 Creating transition sections (see page 957)
 Creating macro sections (see page 916)

Displaying or modifying section properties

Displaying or modifying section properties:

Step Action
1 Left-click the target section, or place the cursor on this section with the arrow
keys.
2 Select (right-click or Shift+F10 key combination) the menu command
Properties from the shortcut menu.
Result: The properties dialog box (see page 478) for the section is opened.
3 Modify the section name as required.
Note that when you modify the name, the name of a link between the section
and the element calling (action, transition or macro section) is deleted.
4 Select the type of access protection if necessary from the Protection list box:
 None
No protection
 Read-Only
Write protection
 No read & write
Read and write protection
See also section Section and Subroutine Protection, page 186.
5 Enter a comment in the Comment tab if desired.
6 Confirm all entries with OK.

33003101 12/2015 477

Accessing Tasks and Sections

Action, transition and macro sections properties dialog box

Structure of the properties dialog box

The properties dialog box consists of three tabs:
 General
The name and the programming language are displayed in this tab. You can also define the type
of protection for the section.
 Localization
You can enter the functional module of the section in this tab.
 Comment
You can enter a comment in this tab.

General tab
Representation of the General tab:

Elements of the General tab:

Element Description
Name The name of the section is displayed in this field.
Note that when you modify the name, the name of a link between the
section and the element calling (action, transition or macro section) is
deleted.
Language The programming language of the section is displayed in this list box.
Note: The programming language can only be defined when creating
the section. The programming language cannot be changed for
existing sections.

478 33003101 12/2015

 Accessing Tasks and Sections

Element Description
Protection Select the type of access protection from this list box.
 None
No protection
 Read-Only
Write protection
 No read & write
Read and write protection
See also section Section and Subroutine Protection, page 186.
OK Use this command button to accept all entries and close the properties
dialog box.
Apply Use this command button to accept all entries without closing the
properties dialog box.

Localization tab
Representation of the Localization tab:

Elements of the Localization tab:

Element Description
Task The task of the section is displayed in this field.
Functional module Select the functional module to which the section is to be allocated to
in this list box.
See also section Functional modules, page 221.
OK Use this command button to accept all entries and close the properties
dialog box.
Apply Use this command button to accept all entries without closing the
properties dialog box.
Note: This command button is only available in the properties dialog
box for existing sections.

33003101 12/2015 479

Accessing Tasks and Sections

Comment tab
Representation of the Comment tab:

Elements of the Comment tab:

Element Description
Text box A comment about the section can be entered in this text box.
OK Use this command button to accept all entries and close the properties
dialog box.
Apply Use this command button to accept all entries without closing the
properties dialog box.
Note: This command button is only available in the properties dialog
box for existing sections.

480 33003101 12/2015

 Accessing Tasks and Sections

Create a Sub-Program Section (SR)

Introduction
Subroutine sections can be created:
 in offline and online mode
Subroutines are expansions to IEC 61131-3 and must be explicitly enabled via the Tools →
Project Settings dialog box, in the Language extensions tab by activating the Allow
subroutines check box.

Information for creating LD sections

An LD section contains 11-64 columns and 17-2000 lines.
The number of columns is set in the Tools → Project Settings dialog in the Editors tab in the
Number of Columns text box.
This setting only applies to sections to be created, not existing sections. Always define the number
of columns before you create a new LD section.
(The number of lines can be increased or reduced during the creation of section contents.)

Creating subroutine sections

Creating subroutines:

Step Action
1 Left-click the SR Sections directory for the target task, or place the cursor on this
directory using the arrow keys.
2 Select (right-click or Shift+F10 key combination) the New SR Section menu
command from the shortcut menu.
Result: The properties dialog box (see page 483) for the section is opened.
3 Enter the section name.
The section name must be unique in the entire project and conform to the
general naming conventions.
4 Select the programming language of the section.
5 Enter a comment in the Comment tab if desired.
6 If you wish to create additional sections, confirm the entries with Apply. In this
case, the Property dialog box will remain open and you can generate additional
sections.
If you do not wish to create additional sections, confirm the entries with OK. In
this case, the Property dialog box will close and the generated section will open
automatically.

33003101 12/2015 481

Accessing Tasks and Sections

View or edit section properties

Displaying or modifying section properties:

Step Action
1 Left-click on the desired section, or place the cursor on this section with the
arrow keys.
2 Click the right mouse button or press Shift+F10 to select the Properties menu
command in the context menu....
Result: The properties dialog box (see page 483) for the section is opened.
3 Implement the desired changes.
4 Confirm all entries with OK.

Importing/exporting sections
See sections:
 Program Import, page 1735
 Exporting the program, page 1733

482 33003101 12/2015

 Accessing Tasks and Sections

Property Dialog of the Sub-Program Sections

Structure of the properties dialog box

The properties dialog box consists of two tabs:
 General
Enter the name and the programming language of the section in this tab. The display indicates
whether the subroutine is used in the project.
 Comment
You can enter a comment in this tab.

General tab
Representation of the General tab:

Elements of the General tab:

Element Description
Name Enter the name of the subroutine section in this text box.
The section name must be unique in the entire project and conform to
the general naming conventions.
Language The programming language of the section is displayed in this list box.
Note: The programming language can only be defined when creating
the section. The programming language cannot be changed for
existing sections.

33003101 12/2015 483

Accessing Tasks and Sections

Element Description
Protection Select the type of access protection from this list box.
 None
No protection
 Read-Only
Write protection
 No read & write
Read and write protection
See also section Section and Subroutine Protection, page 186.
Is called This check box indicates whether the subroutine is used in the project.
OK Generating a new section:
If you do not want to create any additional sections, click on this
command button to confirm the entries. In this case, the Property
dialog box will close and the generated section will open
automatically.
Displaying properties of an existing section:
Use this command button to accept the entries and close the
properties dialog box.
Apply Generating a new section:
If you want to create any additional sections, click on this command
button to confirm the entries. In this case, the Property dialog box will
remain open and you can generate additional sections.
Displaying properties of an existing section:
Use this command button to accept the entries without closing the
properties dialog box.

Comment tab
Representation of the Commenttab:

484 33003101 12/2015

 Accessing Tasks and Sections

Elements of the Comment tab:

Element Description
Text box A comment about the section can be entered in this text box.
OK Generating a new section:
If you do not want to create any additional sections, click on this
command button to confirm the entries. In this case, the Property
dialog box will close and the generated section will open
automatically.
Displaying properties of an existing section:
Use this command button to accept the entries and close the
properties dialog box.
Apply Generating a new section:
If you want to create any additional sections, click on this command
button to confirm the entries. In this case, the Property dialog box will
remain open and you can generate additional sections.
Displaying properties of an existing section:
Use this command button to accept the entries without closing the
properties dialog box.

33003101 12/2015 485

Accessing Tasks and Sections

Creating a Timer Event Section

Introduction
Timer event sections can only be created in offline mode.
The following can be modified in offline mode:
 the number of the timer event,
 the time base,
 the unit of the preset value,
 the unit for the phase,
 the type of access protection,
 the functional module,
 the comment.

In online mode in stop mode, the following can be changed:

 the unit of the preset value,
 the unit for the phase,
 the type of access protection,
 the functional module,
 the comment.

Information for creating LD sections

An LD section contains 11-64 columns and 17-2000 rows.
The number of columns is set in the Tools → Project Settings dialog in the Editors tab in the
Ladder Daigram (LD) area at Number of columns.
This setting only applies to sections to be created, not existing sections. Always define the number
of columns before you create a new LD section.
(The number of rows and columns can be changed during the creation of section contents.)

Information for creating FBD sections

An FBD section contains 86,400 grids (number of rows x number of columns).
The number of rows and columns is set in the Tools → Project Settings dialog in the Editors tab
in the Function Block Diagram (FBD) area.
This setting only applies to sections to be created, not existing sections. Always define the number
of rows and columns before you create a new FBD section.
(The number of rows and columns can be changed during the creation of section contents.)

486 33003101 12/2015

 Accessing Tasks and Sections

Creating timer event sections

Creating timer event sections:

Step Action
1 Left-click the Timer Events directory of the Events task, or place the cursor on
this directory with the arrow keys.
2 Select (right-click or Shift+F10 key combination) the New Event Section menu
command from the shortcut menu.
Result: The properties dialog box (see page 489) for the section is opened.
3 Enter the number of the timer event in the Timer number list box.
The maximum number of timer events depends on the selected CPU, see also
section Timer section (see Unity Pro, Program Languages and Structure,
Reference Manual ) in the Reference manual.
4 Enter the time base for the preset value and phase in the Time base list box.
Note: Select the largest time base to reduce system load.
5 Enter the units for the preset value in the Preset text box.
The valid range is 0...1023.
Preset value = Preset x Timer base
6 Enter the unit for the phase in the Phase text box.
The valid range is 0...1023.
Phase value = Phase x Timer base
7 Select the programming language of the section.
8 Select the type of access protection if necessary from the Protection list box:
 None
No protection
 Read-Only
Write protection
 No read & write
Read and write protection
See also section Section and Subroutine Protection, page 186.
9 Select the functional module to which the section is allocated from the
Localization tab if necessary.
See also section Functional modules, page 221.
10 Enter a comment in the Comment tab if desired.
11 If you wish to create additional sections, confirm the entries with Apply. In this
case, the Property dialog box will remain open and you can generate additional
sections.
If you do not wish to create additional sections, confirm the entries with OK. In
this case, the Property dialog box will close and the generated section will open
automatically.

33003101 12/2015 487

Accessing Tasks and Sections

Displaying or modifying the section properties

Displaying or modifying section properties:

Step Action
1 Left-click on the desired section, or place the cursor on this section with the
arrow keys.
2 Click the right mouse button or press Shift+F10 to select the Properties menu
command in the context menu....
Result: The properties dialog box (see page 489) for the section is opened.
3 Implement the desired changes (see page 486).
4 Confirm all entries with OK.

Importing/exporting sections
See sections:
 Program Import, page 1735
 Exporting the program, page 1733

488 33003101 12/2015

 Accessing Tasks and Sections

Properties dialog box for Timer Event Sections

Structure of the properties dialog box

The properties dialog box consists of three tabs:
 General
In this tab, you can enter the timer event number, the timer time value, the programming
language and the type of access protection for the timer event section, see also section Event
processing (see Unity Pro, Program Languages and Structure, Reference Manual ) in the
Reference manual.
 Localization
You can enter the functional module of the section in this tab.
 Comment
You can enter a comment in this tab.

General tab
Representation of the General tab:

33003101 12/2015 489

Accessing Tasks and Sections

Elements of the General tab:

Element Description
Timer number Enter the number of the timer event in this list box. Note that the
ITCNTRL function block (see Unity Pro, System, Block Library) is
required to activate a timer event.
The maximum number of timer events depends on the selected CPU,
see also section Event processing (see Unity Pro, Program
Languages and Structure, Reference Manual ) in the Reference
manual.
Time base Enter the time base for the preset value and phase in this list box.
The following values are available:
 1 ms
 10 ms
 100 ms
 1 sec

The default value is 10 ms.

Note: Select the largest time base to reduce system load.
Preset Enter the unit for the preset value in this text box.
The valid range is 1...255.
Preset value = Preset x Timer base
Phase Enter the units for the phase in this text box.
The valid range is 0...255.
Phase value = Phase x Timer base
Language The programming language of the section is displayed in this list box.
Note: The programming language can only be defined when creating
the section. The programming language cannot be changed for
existing sections.
Protection Select the type of access protection from this list box.
 None
No protection
 Read-Only
Write protection
 No read & write
Read and write protection
See also Project Protection (see page 186).
OK Generating a new section:
If you do not want to create any additional sections, click on this
command button to confirm the entries. In this case, the properties
dialog box will close and the generated section will open
automatically.
Displaying properties of an existing section:
Use this command button to accept the entries and close the
properties dialog box.

490 33003101 12/2015

 Accessing Tasks and Sections

Element Description
Apply Generating a new section:
If you want to create any additional sections, click on this command
button to confirm the entries. In this case, the properties dialog box will
remain open and you can generate additional sections.
Displaying properties of an existing section:
Use this command button to accept the entries without closing the
properties dialog box.

Localization tab
Representation of the Localization tab:

Elements of the Localization tab:

Element Description
Functional module Select the functional module to which the section is to be allocated to
in this list box.
See also Functional module (see page 221).
OK Generating a new section:
If you do not want to create any additional sections, click on this
command button to confirm the entries. In this case, the properties
dialog box will close and the generated section will open
automatically.
Displaying properties of an existing section:
Use this command button to accept the entries and close the
properties dialog box.
Apply Generating a new section:
If you want to create any additional sections, click on this command
button to confirm the entries. In this case, the properties dialog box will
remain open and you can generate additional sections.
Displaying properties of an existing section:
Use this command button to accept the entries without closing the
properties dialog box.

33003101 12/2015 491

Accessing Tasks and Sections

Comment tab
Representation of the Comment tab:

Elements of the Comment tab:

Element Description
Text box A comment about the section can be entered in this text box.
OK Generating a new section:
If you do not want to create any additional sections, click on this
command button to confirm the entries. In this case, the properties
dialog box will close and the generated section will open
automatically.
Displaying properties of an existing section:
Use this command button to accept the entries and close the
properties dialog box.
Apply Generating a new section:
If you want to create any additional sections, click on this command
button to confirm the entries. In this case, the properties dialog box will
remain open and you can generate additional sections.
Displaying properties of an existing section:
Use this command button to accept the entries without closing the
properties dialog box.

492 33003101 12/2015

 Accessing Tasks and Sections

Create an I/O Event Section

Introduction
I/O event sections can be created in offline and online mode.

Information for creating LD sections

An LD section contains 11-64 columns and 17-2000 rows.
The number of columns is set in the Tools → Project Settings dialog in the Editors tab in the
Ladder Daigram (LD) area at Number of columns.
This setting only applies to sections to be created, not existing sections. Always define the number
of columns before you create a new LD section.
(The number of rows and columns can be changed during the creation of section contents.)

Information for creating FBD sections

An FBD section contains 86,400 grids (number of rows x number of columns).
The number of rows and columns is set in the Tools → Project Settings dialog in the Editors tab
in the Function Block Diagram (FBD) area.
This setting only applies to sections to be created, not existing sections. Always define the number
of rows and columns before you create a new FBD section.
(The number of rows and columns can be changed during the creation of section contents.)

33003101 12/2015 493

Accessing Tasks and Sections

Creating I/O event sections

Creating I/O event sections:

Step Action
1 Left-click on the I/O Events directory of the Events task, or place the cursor
arrow on this directory.
2 Use the right mouse button or the Shift+F10 key combination to select the New
Event Section menu command in the context menu.
Result: The properties dialog box (see page 496) for the section is opened.
3 Enter the number of the I/O event in the I/O Event number list box.
The maximum number of I/O events depends on the selected CPU, see also
section Event section (see page 493) in the Reference manual.
4 Select the programming language of the section.
5 Select the type of access protection if necessary from the Protection list box:
 None
No protection
 Read-Only
Write protection
 No read & write
Read and write protection
See also section Section and Subroutine Protection, page 186.
6 Select the functional module to which the section is allocated from the
Localization tab if necessary.
See also section Functional modules, page 221
7 Enter a comment in the Comment tab if desired.
8 If you wish to create additional sections, confirm the entries with Apply. In this
case, the Property dialog box will remain open and you can generate additional
sections.
If you do not wish to create additional sections, confirm the entries with OK. In
this case, the Property dialog box will close and the generated section will open
automatically.

Displaying or modifying section properties

Displaying or modifying section properties:

Step Action
1 Left-click on the desired section, or place the cursor on this section with the
arrow keys.
2 Use the right mouse button or press Shift+F10 to select the Properties menu
command.
Result: The properties dialog box (see page 496) for the section is opened.
3 Implement the desired changes.
4 Confirm all entries with OK.

494 33003101 12/2015

 Accessing Tasks and Sections

Importing/exporting sections
See sections:
 Program Import, page 1735
 Exporting the program, page 1733

33003101 12/2015 495

Accessing Tasks and Sections

Property Dialog of I/O Event Sections

Structure of the properties dialog box

The properties dialog box consists of three tabs:
 General
Enter the I/O event number, the programming language and the type of access protection for
the I/O event section in this tab, see also section Event processing (see Unity Pro, Program
Languages and Structure, Reference Manual ) in the Reference manual.
 Localization
You can enter the functional module of the section in this tab.
 Comment
You can enter a comment in this tab.

General tab
Representation of the General tab:

Elements of the General tab:

Element Description
I/O Event number You can enter the number of the I/O event in this list box.
The maximum number of I/O events depends on the selected CPU,
see also section Event section (see page 493) in the Reference
manual.
Language The programming language of the section is displayed in this list box.
Note: The programming language can only be defined when creating
the section. The programming language cannot be changed for
existing sections.

496 33003101 12/2015

 Accessing Tasks and Sections

Element Description
Protection Select the type of access protection from this list box.
 None
No protection
 Read-Only
Write protection
 No read & write
Read and write protection
See also section Section and Subroutine Protection, page 186.
OK Generating a new section:
If you do not want to create any additional sections, click on this
command button to confirm the entries. In this case, the Property
dialog box will close and the generated section will open
automatically.
Displaying properties of an existing section:
Use this command button to accept the entries and close the
properties dialog box.
Apply Generating a new section:
If you want to create any additional sections, click on this command
button to confirm the entries. In this case, the Property dialog box will
remain open and you can generate additional sections.
Displaying properties of an existing section:
Use this command button to accept the entries without closing the
properties dialog box.

Localization tab
Representation of the Localization tab:

33003101 12/2015 497

Accessing Tasks and Sections

Elements of the Localization tab:

Element Description
Functional module Select the functional module to which the section is to be allocated to
in this list box.
See also section Functional modules, page 221.
OK Generating a new section:
If you do not want to create any additional sections, click on this
command button to confirm the entries. In this case, the Property
dialog box will close and the generated section will open
automatically.
Displaying properties of an existing section:
Use this command button to accept the entries and close the
properties dialog box.
Apply Generating a new section:
If you want to create any additional sections, click on this command
button to confirm the entries. In this case, the Property dialog box will
remain open and you can generate additional sections.
Displaying properties of an existing section:
Use this command button to accept the entries without closing the
properties dialog box.

Comment tab
Representation of the Commenttab:

498 33003101 12/2015

 Accessing Tasks and Sections

Elements of the Comment tab:

Element Description
Text box A comment about the section can be entered in this text box.
OK Generating a new section:
If you do not want to create any additional sections, click on this
command button to confirm the entries. In this case, the Property
dialog box will close and the generated section will open
automatically.
Displaying properties of an existing section:
Use this command button to accept the entries and close the
properties dialog box.
Apply Generating a new section:
If you want to create any additional sections, click on this command
button to confirm the entries. In this case, the Property dialog box will
remain open and you can generate additional sections.
Displaying properties of an existing section:
Use this command button to accept the entries without closing the
properties dialog box.

33003101 12/2015 499

Accessing Tasks and Sections

Opening a Section

Opening a section
Opening a section:

Step Action
1 Click the left mouse button on the section desired (section, subroutine, event), or
place the cursor on this section with the arrow keys.
2 Select (right-click or Shift+F10 key combination) the menu command Open from
the shortcut menu.
or
Double click on the section.
Result: The section is opened.

500 33003101 12/2015

 Accessing Tasks and Sections

Deleting sections

Deleting sections
Deleting sections:

Step Action
1 Left-click the target section (section, subroutine, event), or place the cursor on
this section with the arrow keys.
2 Select (right-click or Shift+F10 key combination) the Delete menu command
from the shortcut menu.
Result: The section is deleted.

33003101 12/2015 501

Accessing Tasks and Sections

Execution order of sections

Introduction
The execution of sections is carried out according to the order displayed in the structural view.
The arrangement of the actions, transition, macro steps, subroutines, and event sections has no
influence on the execution order as their execution is program or event controlled.
The execution order of sections can be changed exclusively in the structural view.
The changes can be made:
 in offline mode
 in online mode in stop mode

Modifying the execution order

Modifying the execution order:

Step Action
1 Click on the desired section with the left mouse button and hold the mouse button
down.
2 Move the section to the required position within the current task or into another
task.

502 33003101 12/2015

 Accessing Tasks and Sections

Creating LL984 Segments and Networks

Introduction
The logic of LL984 is programmed in networks.
Several networks are grouped in segments.
Each network contains a matrix of 7 rows and 11 columns, where you can place contacts, coils,
function blocks etc.
At the beginning of each segment's code execution the inputs of a RIO drop can be read and at
the end the outputs of the same or another RIO drop can be written.

Recommendations
It is recommended not to use more than 64 segments and 5,000 networks in an application.

Restrictions
For creating LL984 segments and networks the following rules apply:
 LL984 segments can only be created when the Ladder Logic 984 (LL984) project setting is
activated via Tools → Project Settings → Program → Languages.
 LL984 segments can only be created in the MAST task of the application, they are not allowed
in the FAST and AUX tasks.
 Only one LL984 segment can be created inside the subroutine (SR Sections) node of the
MAST task.
 LL984 segments can not be created under Timer Events or I/O Events nodes.
 LL984 segments can not be created in DFBs.
 For action and transition sections in SFC, LL984 is not allowed as language.
Only ST, IL, FBD and LD are allowed as language.
 LL984 segments and sections with Unity Pro IEC languages can be mixed inside the Sections
node of the MAST task. The same is valid inside the subroutine (SR Sections) node of the
MAST task.
 LL984 networks can only be created as children of LL984 segments.
 Only LL984 networks are allowed as children of LL984 segments, no sections with IEC
languages can be created there.

33003101 12/2015 503

Accessing Tasks and Sections

Creating a Segment

Step Action
1 Left-click the Sections directory of the MAST task, or place the cursor using the
arrow keys on this directory.
2 Click the right mouse button or use Shift+F10 to select New Section in the context
menu.
Result: The properties dialog for the segment is opened.
3 Enter the section (segment) name.
The section (segment) name must be unique in the entire project and conform to
the general naming conventions of Unity Pro.
4 Select LL984 Segment as programming Language of the segment.
5 Select the functional module to which the segment is attached from the
Localization tab if necessary.
Also refer to Functional modules (see page 221).
6 Define a boolean variable in the Condition tab with which the segment can be
activated/deactivated (segment active when variable=1) if required.
You have the following options to select variables:
 Enter the name of the variable/address directly or copy it from the clipboard.
 Use the ... button to open a Data Selection dialog.

7 Only applies to Quantum projects:

Assign a read RIO drop and a write RIO drop to the segment in the Remote IO tab
if required.
8 Enter a comment in the Comment tab if desired (max. 1024 characters).
9 If you wish to create additional segments, confirm the entries with Apply. In this
case, the dialog will remain open and you can generate additional segments.
If you do not wish to create additional segments, confirm the entries with OK. In
this case, the dialog will close and the generated segment is displayed as the last
element in the Sections directory.
NOTE: The position of sections and segments inside the Structural view
matches exactly the execution sequence and can be changed via drag-and-drop.

504 33003101 12/2015

 Accessing Tasks and Sections

Creating a Network

Step Action
1 Left-click an LL984 Segment in the Sections directory of the MAST task, or
place the cursor using the arrow keys on this directory.
2 Click the right mouse button or use Shift+F10 to select New 984 Network in the
context menu.
Result: The properties dialog for the network is opened.
3 Enter the network name.
The network name must be unique in the entire project and conform to the
general naming conventions of Unity Pro.
4 LL984 Network is preselected for the Language of the network and can not be
changed.
5 Define a boolean variable in the Condition tab with which the segment can be
activated/deactivated (segment active when variable=1) if required.
You have the following options to select variables:
 Enter the name of the variable/address directly or copy it from the clipboard.
 Use the command button ...to open a Data Selection dialog.

6 Enter a comment in the Comment tab if desired.

7 Confirm the entries with OK. The dialog will close and the generated network is
displayed as the last element in the LL984 Segment directory.
NOTE: The position of networks inside the Structural view matches exactly the
execution sequence and can be changed via drag-and-drop.

A new network is normally inserted as the last element in the LL984 Segment directory.
To insert a new network directly before a selected network use Insert Network … from the context
menu.

33003101 12/2015 505

Accessing Tasks and Sections

Creating a Network for Subroutines

Step Action
1 Left-click the SR Sections directory of the MAST task, or place the cursor using
the arrow keys on this directory.
2 Click the right mouse button or use Shift+F10 to select New SR Section in the
context menu.
Result: The properties dialog for the SR section (LL984 Segment) is opened.
3 Enter the SR section (LL984 segment) name.
The SR section (LL984 Segment) name must be unique in the entire project and
conform to the general naming conventions of Unity Pro.
4 Select LL984 Segment as programming Language of the segment.
NOTE: There can be only 1 LL984 SR segment in a project. So when there is
already 1 existing you can no longer select LL984 Segment as programming
Language for a new SR section.
5 Enter a comment in the Comment tab if desired (max. 1024 characters).
6 Confirm the entries with OK. The dialog will close and the generated LL984
segment is displayed in the SR Section directory.
7 Left-click the LL984 Segment in the SR Sections directory of the MAST task,
or place the cursor using the arrow keys on this directory.
8 Click the right mouse button or use Shift+F10 to select New 984 Network in the
context menu.
Result: The properties dialog for the network is opened.
9 Enter the network name.
The network name must be unique in the entire project and conform to the
general naming conventions of Unity Pro.
10 LL984 Network is preselected for the Language of the network and can not be
changed.
11 Enter a comment in the Comment tab if desired.
12 Confirm the entries with OK. Tthe dialog will close and the generated network is
displayed as the last element in the LL984 Segment directory.
NOTE: The position of networks inside the Structural view matches exactly the
execution sequence and can be changed via drag-and-drop.

506 33003101 12/2015

 Accessing Tasks and Sections

Displaying or Modifying Segment/Network Properties

Step Action
1 Left-click on the desired segment/network, or place the cursor on this
section/network with the arrow keys.
2 Click the right mouse button or use Shift+F10 to select Properties in the
context menu.
Result: The Properties dialog for is opened.
3 Implement the desired changes.
4 Confirm all entries with OK.

Exporting/Importing Segments/Networks
Please refer to Exporting/Importing LL984 Segments/Networks (see page 1759).

33003101 12/2015 507

Accessing Tasks and Sections

Modifying LL984 Segment Properties

Introduction
This section describes the specifics of the LL984 Editor referring to modifying LL984 segment
properties.
For standard features please refer to Accessing Sections (see page 457).

Protection
The Protection property is not available at the moment.

Localization
You can only attach LL984 segments to a functional module and not LL984 networks. The
networks of a segment are implicitly attached to the functional module of their segment.
You can attach an LL984 segment to a functional module either in the Localization tab of its
properties dialog or in the Project Browser via drag-and-drop from the Structural View to the
Functional View.
You can detach an LL984 segment from a functional module either in the Localization tab of its
properties dialog or by selecting Detach from the segment´s context menu.

Condition
You can modify the Condition of an LL984 segment in the Condition tab of its properties dialog.
When you configure a boolean variable in this tab, the state of this variable is checked at the
beginning of the LL984 segment's code execution.
When the variable´s state is 0, the segment and all its networks are not executed.
When the variable´s state is 1 or when no condition variable is defined for the segment, it depends
on the condition variables of the networks whether the networks are executed or not.

Remote I/O
You can synchronize the Remote I/Os of an LL984 segment in the Remote I/O tab of its properties
dialog.
Here you can configure which Remote Quantum drop is read before and which one is written after
execution of the LL984 segment.
Drops which are not yet configured are displayed in red inside the list box.
Not configured drops can be selected here, but when they are not configured before next Build,
the build will not be successful and a diagnostic message will be displayed.
NOTE: This property is only available for Quantum projects.

508 33003101 12/2015

 Accessing Tasks and Sections

Comment
You can enter a comment to an LL984 segment in the Comment tab of its properties dialog.
The maximum size of a comment is 1024 characters.

The LL984 Subroutine Segment

You can only have 1 LL984 segment under the SR sections node of the MAST task.
The properties dialog of this LL984 subroutine segment only provides the General and the
Comments tabs.
The Is called check book in the General tab is greyed and not checked.
This is done because in LL984, subroutines can be called via a memory word and so you only know
at run time whether a subroutine is called or not.
You can not define a condition variable for the LL984 subroutine segment.

33003101 12/2015 509

Accessing Tasks and Sections

Modifying LL984 Network Properties

Introduction
This section describes the specifics of the LL984 Editor referring to modifying LL984 network
properties.
For standard features please refer to Accessing Sections (see page 457).

Protection
The Protection property is not available at the moment.

Localization
You can only attach an LL984 segment to a functional modules. The networks of a segment are
implicitly attached to the functional module of their segment.

Condition
You can modify the Condition of an LL984 network in the Condition tab of its properties dialog.
When you configure a boolean variable in this tab, the state of this variable is checked at the
beginning of the LL984 network's code execution.
When the variable´s state is 0, the variable and its networks are not executed.
When the variable´s state is 1 or when no condition variable is defined for the network, it depends
on the condition variables of the networks whether the networks are executed or not.
You can define a condition variable for each network.
NOTE: Condition variables do not have influence on the execution of an L9_SKP block, that means
when you have a skip over 4 networks, you skip the remainder of the current network and the next
3 networks independent of their condition variables.

Remote I/O
You can synchronize the Remote I/Os only for LL984 segments and not for LL984 networks.

Comment
You can enter a comment to an LL984 network in the Comment tab of its properties dialog.
The maximum size of a comment is 1024 characters.

510 33003101 12/2015

 Accessing Tasks and Sections

User Directory/Hyperlink
For LL984 networks you can add hyperlinks by selecting Add Hyperlink from the network´s
context menu.
For details please refer to chapter Hyperlinks (see page 1817).
You can not add user directories to LL984 networks.

LL984 Networks in Subroutine Segments

The properties dialog of an LL984 network in a subroutine (SR) segment only provides the General
and the Comments tabs.
The Is called check box in the General tab is greyed and not checked, because in LL984
subroutines can be called via a memory word and so you only know at run time whether a
subroutine is called or not.
You can not define a condition variable for an LL984 network in a subroutine (SR) segment.

33003101 12/2015 511

Accessing Tasks and Sections

Scheduling LL984 Segments and Network

Introduction
Sections and LL984 segments (and also LL984 networks inside segments) are executed in the
sequence in which they are displayed in the Structural View of the Project Browser.
To change this sequence, you can drag-and-drop sections, LL984 segments or LL984 networks
inside the Structural View.

Restrictions
For dragging-and-dropping LL984 segments and networks the following rules apply:
 Sections (ST, LD, …) can not be dropped into LL984 segments.
 LL984 segments can not be dropped into other LL984 segments.
 LL984 networks can only be dropped into LL984 segments.
LL984 networks can be dropped into the LL984 subroutine segment under the SR Sections)
node of the MAST task.
After dropping the networks, they are re-analyzed latest during next Build, because e.g.
L9_LAB function blocks are only allowed in networks of the LL984 segment in the SR Sections
node.
 When an LL984 network has an activation condition and is dragged-and-dropped into the LL984
subroutine segment, the LL984 network loses its activation condition because subroutine
networks do not have activation conditions.

Drag-and Drop Between Applications

You can not drag-and drop LL984 segments and networks from one Unity Pro application to
another.
To copy sections between applications you have to use the import/export feature of Unity Pro.

512 33003101 12/2015

 Accessing Tasks and Sections

Deleting, Cutting, Copying and Pasting LL984 Segments and Network

Deleting LL984 Segments and Networks

You can delete LL984 segments and networks in the Structural View of the Project Browser.
To delete an LL984 segment or network either select Delete from its context menu or press the
DEL key.
If you want to delete an LL984 segment, a message is displayed that all its networks will be deleted,
too.
You have to confirm this message to delete the LL984 segment.

Cutting, Copying and Pasting

You can not cut, copy and paste LL984 segments and networks in a Unity Pro application.
Alternatively you can use the import/export feature on segment or network level.

33003101 12/2015 513

Accessing Tasks and Sections

514 33003101 12/2015

 Unity Pro
Unity Pro Software Options
33003101 12/2015

Chapter 19
Unity Pro Software Options

Unity Pro Software Options

Subject of this Chapter

This chapter describes the options in Unity Pro software. The software provides 3 types of option:
 Project Settings: they are specific to the generated project and to how it is executed on the
PLC (for example: acknowledgment of diagnostic functions, execution of SFC language, etc.).
 Options..: they are specific to the workstation and may therefore differ from one station to
another for the same project (for example: the way in which errors are displayed, direction of
movement of selection after data entry, etc.)
 Custom..: they are used to customize the ergonomics of the workstation (contents of toolbar
etc.).

What Is in This Chapter?

This chapter contains the following sections:
Section Topic Page
19.1 Project Settings 516
19.2 Options 554
19.3 Customize Dialog Box 571

33003101 12/2015 515

Unity Pro Software Options

Section 19.1
Project Settings

Project Settings

Overview
This section describes the Tools → Project settings dialog box tab.

What Is in This Section?

This section contains the following topics:
Topic Page
General Description 517
General Project Settings 519
Variables 531
Program 534
Maintain Output Links on Disabled EF (EN=0) 542
Configuration Settings for Operator Screens 550

516 33003101 12/2015

 Unity Pro Software Options

General Description

Introduction

CAUTION
UNEXPECTED APPLICATION BEHAVIOR
When importing a project settings file, ensure that the required file is used. Importing an
inappropriate project setting file can result in unexpected application behavior.
Failure to follow these instructions can result in injury or equipment damage.

The table below describes the general functions used with all Project Settings tabs:

Fields Description
Import This button allows the selection of a Project Setting .XSO file. All values in the file will be
taken into account for the current opened project. After Import, click on OK or Apply to
validate the settings.
Export This button allows the current values of the project settings to be saved in an .XSO file.
Reset All This button is used to reset all the settings to their default values.
OK This button is used to save the modifications and close the current tab.
Apply This button is used to save the modifications.
Cancel This button is used to cancel without saving the modifications on the current tab.
Help This button is used to call the online help.

General Navigation
The table below describes the general key shortcut navigation used with all Project Settings tabs:

Fields Description
TAB This key is used to move from one control to another.
ENTER This key is used to confirm the current action.
ESC This key is used to cancel without saving the modifications in the
current tab.
Up, Down, Left and These keys are used to navigate within the tree control and the right
Right Arrows list box.

33003101 12/2015 517

Unity Pro Software Options

Specific Navigation
The table below describes the Specific key shortcut navigation used with all Project Settings tabs:

Fields Description
Space This key is used to check/uncheck an element.
F2 This key is used to activate the current line.
ESC This key is used to deactivate the current line.
Up and Down These keys are used to navigate in the list box in the active line.
Arrows
+ and - These keys are used to increase or decrease a value in the number
field in the active line.

518 33003101 12/2015

 Unity Pro Software Options

General Project Settings

At a Glance

The following tables describe the available functions in the Project Settings dialog for project
generation:
 Management of build messages
 Build settings
 Project autosaving on download
 PLC embedded data
 PLC diagnostics
 PLC behaviour
 Path
 Time
 Configuration

Management of build messages

The table below shows all available Management of build messages fields, their description and
required action to take modification into account:

Fields Description
Variable not used nothing or a detected warning is displayed in the view window if variables defined
generates in the project are not used in the program.
Variables defined in the project but are not used in the program.
Modification: Online possible
Action required: No build necessary
Multiple writing of Variables assigned several times to different places in the program.
variables generates
Modification: Online possible
Action required: No build necessary
Parameters not EFB or DFB parameters not assigned.
assigned generates
Modification: Online possible
Action required: Build Changes (Offline)
Multiple use of FB EFB or DFB instances used several times at different places in the program.
instance generates
Modification: Online possible
Action required: No build necessary

33003101 12/2015 519

Unity Pro Software Options

Fields Description
DDT mapping An alignment test on DDTs is done for each type of data structure (BOOL, BYTE,
compatibility INT, DINT...) with specific rules for each platform. Unity Pro displays a notification
generates statomg which DDTs have to be modified when either an Analyze Project, Build
Changes, or Rebuild all Project command runs.
If the data structures have the same alignment in each platform, communication
between them is possible. Otherwise, a notification appears to inform which DDTs
have to be modified for allowing communication.
Premium and Quantum have the same mapping rule so these two platforms are
aligned for communication.
M340, M580 and Momentum has a different mapping rule than Premium and
Quantum. So, it is necessary to check if the alignment of the exchanged DDTs is
the same for each platform (M340 and Premium for example) and in this case
modify the DDTs.
Refer to DDT: Mapping rules (see Unity Pro, Program Languages and Structure,
Reference Manual ) for alignment rules.
Modification: Online possible
Action required: No build necessary
Overlapping of If nothing is selected, no message is displayed in the view window even if there is
address generates overlapping of address of some variables.
If a detected warning is selected, some address messages are displayed in the
view window if there is overlapping of addresses of some variables.The project is
generated.
If a detected error is selected, some detected error messages are displayed in the
view window if there is overlapping of addresses of some variables. Due to the
detected errors, the project is not generated.
NOTE: Overlapping of topological addresses is not detected. Only flat addresses
are detected by Unity Pro.
NOTE: The overlapping can generate a high number of detected errors for clients
using many located variables or LL984 converted code and so increase the build
generation time.
Modification: Online possible
Action required: Rebuild All Project (Offline)
Missing gateway IP @ A detected error is generated on Quantum RIO architecture when a
generates 140 NOC 780 00, 140 NOC 781 00 or 140 CRP 312 00 module is configured
without gateway IP address defined (equal to 0.0.0.0).
Modification: Online possible
Action required: No build necessary

520 33003101 12/2015

 Unity Pro Software Options

Fields Description
Control numbers of The Control numbers of warnings has to be selected and a value defined in the
warnings Maximum of warnings allowed field (the valid range is 100...2000). Then, when
the number configured is reached, the next detected warnings are not displayed in
the view window.
Modification: Online possible
Action required: No build necessary
Control numbers of The Control numbers of errors has to be selected and a value defined in the
errors detected Maximum of errors allowed field (the valid range is 100- 2000). Then,
when the number configured is reached, the next detected errors are not displayed
in the view window.
Modification: Online possible
Action required: No build necessary

Build settings
The table below shows all available Build settings fields and their description:

Fields Description
Create New data block Exclusive setting that allows you to select the management of data memory during
on line on line modification.
This setting allows you to add/modify variables without limitation of the memory
block. By default, this check box is checked:
 When checked, the dynamic allocation of unlocated variables in a new data
block can be done online and you are not prompted Unity Pro does not prompt
you to Rebuild all Project.
 When unchecked, Unity Pro acts as per the free data memory setting, which
appears below.
NOTES:
 For applications (STA, XEF, ZEF files, or an upload) that contain this project
setting when opened the setting is not changed.
 For applications that do not contain this project setting, when opened or
uploaded it is set to the default value: checked.
Modification: Online possible
Action Rebuild All Project (Offline) to deselect
required: Build Changes (Online) to select

33003101 12/2015 521

Unity Pro Software Options

Fields Description
Free data memory (in Exclusive setting that allows you to select the management of data memory during
kbytes) on line modification.
This setting was the only way to manage data memory during on line changes
before Unity Pro V6.0. It is kept for compatibility with previous versions or when
only a few modifications of variables on line are planned.
When this setting is valid, only one memory block 1...64 K is reserved.
Each time unlocated variables are created or modified, they are added to this
memory block in the PLC.
When the memory allocated is full, it is not possible to perform additional on-line
modifications (a detected error message is displayed during the on-line change
session). A Rebuild All Project is mandatory to restart with this memory block
empty and available for new on line modifications.
Modification: Online possible
Action Rebuild All Project (Offline)
required:
Virtual connected Used to modify a project on a non-connected terminal, as if this terminal was
mode connected to the PLC.
It is then simply a case of connecting the terminal to the PLC and activating the
command Build → Build Changes in order to have these modifications taken into
consideration in the PLC. This transfer does not stop the PLC and only the
changes made are taken into account. The purpose of this mode is to inform when
an online modification is not possible. However, if the change is made, the virtual
connected mode is aborted.
Analysis is permitted in this mode, but generation is not possible. The project can
be regenerated at any time, but this exits virtual mode.
Modification: Online possible
Action Rebuild All Project (Offline)
required:
Generate with LD link Allows choosing to include or not information on ladder diagram link animation in
animation the generated code.
Modification: Online possible
Action Rebuild All Project (Offline)
required:
Optimized code Used to reduce the size of the code generated. Note the following:
 On Premium PLCs and on Quantum 140 CPU 6•• PLCs, the bit %S18 is no
longer managed for arithmetic operations on EDT (Elementary Data Types)
and tables.
 On Quantum 140 CPU 3••/4••/5•• PLCs, the bit %S18 is no longer managed for
arithmetic operations on EDT. The bit %S20 is no longer managed for table
indexing (the threshold values are still checked).
Modification: Online possible
Action Build Changes (Offline)
required:

522 33003101 12/2015

 Unity Pro Software Options

Fields Description
Apply online Allows choosing whether the application is to be downloaded automatically or on
modification a user request after the Build Changes command.
On each modification, this dialog box allows you to validate or not the modification:

Modification: Online possible

Action No build necessary
required:

Project autosaving on download

The table below shows all available Project autosaving on download fields and their description:

Fields Description
save STA If selected, the archive file is automatically saved each time it is transferred
to the PLC (generation in online mode or transfer of complete program).
Modification: Online possible
Action required: No build necessary
save STU If selected, the project is automatically backed up (STU and auto.STA files
saved if the application has changed since the last download) each time it is
transferred to the PLC (generation in online mode or transfer of complete
program).
NOTE: Each time the project is saved (STU file), if the project is in BUILT
state, a file with AUTO.STA suffix is saved, even if the STU box is not
checked.
Modification: Online possible
Action required: No build necessary
save XVM If selected, the project variables are automatically backed up (XVM file) each
time the project is transferred to the PLC (generation in online mode or
transfer of complete program).
Modification: Online possible
Action required: No build necessary

33003101 12/2015 523

Unity Pro Software Options

PLC embedded data

The table below shows all available PLC embedded data fields and their description:

Fields Description
Data dictionary Dictionary of symbolized variables with their characteristics (address, type,...) in the PLC
memory.
If this setting is enabled, all symbolized variables of the application are embedded in the
PLC memory. Any client (SCADA using OFS, HMI, embedded Web server...) can then
animate or modify those variables. By default, the settings are disabled.
The Data dictionary is generated at build time. This block is updated only if it is needed
during an online modification.
NOTE: Comments of the variables are not stored.
The 3 following properties improve the performances of the Data dictionary online build:
 When checking Preload on build changes, download of data dictionary reflecting
the change of variable definition is performed before applying the real change of the
application in the PLC. The PLC client tools are then able to learn new changes of
data.
 The Effective Build changes time-out (sec) is the time (1...240 s) that Unity Pro is
waiting between the download of the new data dictionary and the real online
application change. The down counting of the time-out is displayed in the progress
bar during the Build Changes operation.
 Checking the Only HMI variables and identifying the HMI variables necessary in the
Data Property table improves online build performances and memory usage of the
PLC. This setting means that the data dictionary embeds only variables or DFB/EFB
instances that have the HMI attribute set.
NOTE: A detected Memory full error message could happen during a Build Changes
if there is not enough free memory. A project with the Data dictionary enabled needs a
large amount of free memory to be built.
Modification: Online possible
Action required: Build Changes (Online)
Upload If selected, this non-executable code designed to restore the source of the project on a
information terminal is simultaneously loaded with the executable code when transferring the project
to the PLC.
If selected, program transfer from the PLC to the PC cannot be done. In this non-
executable code, the check boxes Comments and Animation tables are used to
include comments associated with the variables and types and animation tables
respectively.
Modification: Online possible
Action required: Rebuild All Project (Offline)

524 33003101 12/2015

 Unity Pro Software Options

Fields Description
Upload If Automatic is selected, all online modifications are made on both the executable code
information and the non-executable code designed to restore the project on the terminal.
management If On user request is selected, the online modifications are only made on the executable
code in the PLC processor. The non-executable code has to be updated implicitly using
the PLC → Update Upload Information command.
An indicator at the foot of the screen is displayed if the non-executable code has not been
updated.
Modification: Online possible
Action required: No build necessary
Optimize data If this box is checked, it reduces the time of the Upload information generation relating
on-line change to variables and function blocks of the application in online mode.
NOTE: Uncheck this option to keep compatibility with Unity Pro versions before 4.1.
Modification: Online possible
Action required: Build Changes (Offline)

PLC diagnostics
The table below shows all available PLC diagnostics fields and their description:

Fields Description
Application diagnostics If the box is checked, you can choose an Application diagnostic level.
Modification: Online possible
Action required: Rebuild All Project (Offline)
Application diagnostic Diagnostic level choice:
level  If No cause of fault is selected, the analysis of the diagnostic detected error
origin is not performed.
 If Local diagnostic is selected, the analysis of the diagnostic detected error
origin is performed within the section using the diagnostic DFB.
 If Global diagnostic is selected, the analysis of the diagnostic detected
error origin is performed within the whole application.
Modification: Online possible
Action required: Rebuild All Project (Offline)
System diagnostics If the box is checked, you can choose a System diagnostic language.
Modification: Online possible
Action required: Build Changes (Offline)

33003101 12/2015 525

Unity Pro Software Options

Fields Description
System diagnostic Language choice:
language  English (by default)
 German
 Italian
 Spanish
 French

Modification: Online possible

Action required: Build Changes (Offline)
Rack Viewer diagnostics If selected, it provides a view of the rack.
information
Modification: Online possible
Action required: Build Changes (Online)
Rack Viewer variable If selected, it provides a view of the rack names.
names
Modification: Online possible
Action required: Build Changes (Online)
Program Viewer The Program Viewer runs on a PC that is connected to an Ethernet module.
information If selected, it provides a view of the program structure (functional and structural)
and displays the contents of sections and animation.
Use of this function requires Unity Pro 6.0 of higher.
NOTES:
 Useful only when having a FactoryCast 140 NOE 771 1•, TSY ETY 5103 in
the PLC local rack.
 The Data dictionary has to be selected and preferably without the Only HMI
variables option.The program viewer relies on the data dictionary being fully
present in the PLC to animate the variables in the code. If the data dictionary
is not present, or incomplete, the code is visible but not animated or only
partially animated. Using the HMI variables only would limit the scope of the
animated variables in the code.
Modification: Offline only
Action required: Build Changes (Offline)
Event Logging Select this field to enables event logging for each possible originator of event
logging in the architecture. The syslog settings entered below are transferred to
each event logging originator in the architecture.
NOTE: Event logging is enabled if this field is selected and a valid syslog
server IP address is entered in SYSLOG server address field below.
NOTE: Unity Pro event logging is configured in Security Editor → Profiles.
Modification: Offline only
Action required: Build Changes (Offline)

526 33003101 12/2015

 Unity Pro Software Options

Fields Description
SYSLOG server address Sets the IP address of the syslog server that stores the system events logging.
NOTE: The default value (0.0.0.0) does not allow events to be logged, a valid
server address is needed with the Event Logging field selected.
NOTE: The syslog server address entered here is embedded in the
application.
Modification: Offline only
Action required: Build Changes (Offline)
SYSLOG server port Sets the syslog port number.
number Port number value:
Default: 601
Range: 0...65535
Modification: Offline only
Action required: Build Changes (Offline)
SYSLOG server protocol Sets the syslog server protocol.
TCP V1 is the default syslog protocol.
NOTE:
Modification: The syslog protocol cannot be modified in Unity Pro 10.0.
Action required: –

PLC behaviour

CAUTION
UNINTENDED EQUIPMENT OPERATION
Ensure that the use of the function Reset %M on Stop->Run transition is appropriate to the
application and carefully tested before any implementation.
Failure to follow these instructions can result in injury or equipment damage.

The table below shows the PLC behaviour field and its description:

Field Description
Reset %M on Stop- This function resets %M that is not used in LL984 sections during a STOP to RUN
>Run transition transition of the CPU.
NOTE: This function is only available for the Quantum CPUs with version 2.82 or
higher of the operating system.
Modification: Online possible
Action required: Build Changes (Offline)

33003101 12/2015 527

Unity Pro Software Options

The action of the Reset %M on Stop->Run transition function depends on the following (Tools
menu) → Project Settings check boxes:
 General → PLC behaviour → Reset%M on Stop->Run transition
This setting only impacts % M not used in LL984 language sections.
 Program → Languages → Ladder Logic 984 (LL984)
This setting only impacts %M used with normal coils in LL984 language sections.
This table shows that results of a transition depend on which check boxes are validated:

Reset%M LL984 Resulting Action on Stop → Run transition

Unchecked Unchecked No %M are reset.
Checked Reset of %M used with normal LL984 coils.
Checked Unchecked Reset of %M.
Checked Reset of all %M not used with latched LL984 coils.

If there are %M conflicts:

 For a %M used on an LL984 latched coil and on a non-LL984 coil, the LL984 latched coil has
the higher priority
 For a %M used on an LL984 normal coil and on a non-LL984 coil, the LL984 normal coil has
the higher priority
If a %M has its value forced, its forced value does not change after a Reset %M on Stop->Run
transition.

Path
The table below shows the Path field and its description:

Fields Description
Hyperlink Root Path Allows choosing a path which is used for LL984 application (see page 118) when
the option to convert long comments to text files is chosen. In this case, the long
comments are available as hyperlinks in the variable comments column of the data
editor.
Additionally you can define a path for the created hyperlink text files by either of 2
ways:
 Define a relative path in the root directory of your application.
 Use the ... button to select any other path.

The subfolder of the hyperlink files is displayed below the edit field.