EcoStruxure™ Control Expert

Operating Modes
Original instructions

33003101.26
06/2022

www.se.com
Legal Information
The Schneider Electric brand and any trademarks of Schneider Electric SE and its
subsidiaries referred to in this guide are the property of Schneider Electric SE or its
subsidiaries. All other brands may be trademarks of their respective owners.
This guide and its content are protected under applicable copyright laws and furnished for
informational use only. No part of this guide may be reproduced or transmitted in any form or
by any means (electronic, mechanical, photocopying, recording, or otherwise), for any
purpose, without the prior written permission of Schneider Electric.
Schneider Electric does not grant any right or license for commercial use of the guide or its
content, except for a non-exclusive and personal license to consult it on an "as is" basis.
Schneider Electric products and equipment should be installed, operated, serviced, and
maintained only by qualified personnel.
As standards, specifications, and designs change from time to time, information contained in
this guide may be subject to change without notice.
To the extent permitted by applicable law, no responsibility or liability is assumed by
Schneider Electric and its subsidiaries for any errors or omissions in the informational
content of this material or consequences arising out of or resulting from the use of the
information contained herein.

As part of a group of responsible, inclusive companies, we are updating our communications

that contain non-inclusive terminology. Until we complete this process, however, our content
may still contain standardized industry terms that may be deemed inappropriate by our
customers.
Table of Contents
Safety Information ..................................................................................................31
Before You Begin..............................................................................................32
Start-up and Test ..............................................................................................33
Operation and Adjustments ...............................................................................34
About the Book ......................................................................................................35
General ....................................................................................................................39
General Presentation of Control Expert ....................................................................40
Capabilities of Control Expert ............................................................................40
User Interface ..................................................................................................45
Programming Language Editors ..............................................................................49
Function Block Diagram FBD.............................................................................49
Ladder Diagram (LD) Language ........................................................................52
General Information about SFC Sequence Language..........................................54
Instruction List IL ..............................................................................................58
Structured Text ST............................................................................................59
Connecting a terminal to a PLC ...............................................................................62
Methodology for connecting from a PC to a PLC .................................................62
Global project management ....................................................................................65
Access security management ............................................................................65
Access security management ......................................................................65
Project management.........................................................................................66
Access to Control Expert Software ...............................................................66
Services in Offline Mode..............................................................................68
Services in Online Mode..............................................................................77
Allowed Online Modifications .......................................................................79
Connection / disconnection..........................................................................85
Accessing a PLC via a Network....................................................................87
Overview of Types of Connection Possible With Schneider PLCs ...................92
Accessing communication parameters .........................................................95
Project comparison .....................................................................................99
Conversion of Legacy Applications/Projects................................................ 101
Importing an LL984 Application .................................................................. 102

33003101.26 3
 Transferring the project between the terminal and the PLC........................... 112
Update of Upload Information .................................................................... 116
Sending a command to the PLC................................................................. 117
Project Backup Management for Modicon M340.......................................... 118
Project backup for Premium....................................................................... 120
Save/Restore Data Between a File and the PLC.......................................... 122
Compatibility Rules for Restore Using a *.DTX File ...................................... 127
Transferring Current Values ....................................................................... 134
Memory usage.......................................................................................... 134
Data Memory Protection............................................................................ 140
Function Pack for Memory ......................................................................... 145
Memory Card Access for Modicon M340..................................................... 147
FTP and Memory Card for Modicon M340................................................... 148
Project Management with DTMs ................................................................ 150
Project browser .................................................................................................... 155
Introduction to the project browser ................................................................... 155
Introduction to the project browser.............................................................. 155
Structural view and functional view of the project ......................................... 158
The Zoom In and Zoom Out commands...................................................... 160
The commands Contract all and Expand all ................................................ 163
The Goto command .................................................................................. 168
User Directory .......................................................................................... 171
Project Properties ..................................................................................... 172
Application Protection ............................................................................... 174
Safe Area Password Protection.................................................................. 181
Firmware Protection .................................................................................. 185
Program Unit, Section and Subroutine Protection ........................................ 187
Data Storage/Web Protection .................................................................... 189
Loss of Password ..................................................................................... 191
Introduction to the various directories of the project browser .............................. 198
Project Directory ...................................................................................... 198
Configuration Directory.............................................................................. 199
Derived data types (DDT) directory ............................................................ 201
Derived FB (DFB) types directory ............................................................... 202
Variables Directory.................................................................................... 203

4 33003101.26
 Motion Directory ....................................................................................... 205
Communication Directory .......................................................................... 207
Ethernet Network Directory ...................................................................... 208
Programs Directory .................................................................................. 208
Animation Tables Directory ........................................................................ 212
Operator Screens Directory ....................................................................... 215
Documentation Directory ........................................................................... 217
Conversion Report Directory...................................................................... 218
Summaries of the utilities associated with the structure view and function
view............................................................................................................... 220
Summary of the services associated with the structural view ........................ 220
Functional modules .............................................................................................. 232
Introduction to the functional view .................................................................... 232
Functional modules................................................................................... 232
Project directory of the functional view ........................................................ 234
Functional Module Directory .................................................................... 235
Functional Module Program Directory......................................................... 236
Functional Module Animation Tables Directory ............................................ 237
Functional Module Operator Screens Directory ........................................... 238
Summary of the services associated with the functional view........................ 239
The functional modules and their associated utilities ......................................... 246
Properties of a functional module ............................................................... 246
Creating a functional module ..................................................................... 247
Programming a functional module .............................................................. 248
Protecting program elements of the functional module ................................. 250
Debugging a functional module .................................................................. 250
Detaching/Deleting a functional module ...................................................... 251
Functional module export .......................................................................... 255
Functional module import .......................................................................... 255
Creating, Deleting, Locating, Dragging-and-Dropping an Animation Table
in a Functional Module .............................................................................. 255
Creating, Deleting, Locating and Dragging-and-Dropping an Operator
Screen in a Functional Module ................................................................... 258
FDT Container ..................................................................................................... 263
FDT Container ............................................................................................... 263

33003101.26 5
 Introduction to the Control Expert FDT Container ........................................ 263
FDT Container User Rights........................................................................ 264
DTM Hardware Catalog .................................................................................. 266
Introduction to the Hardware Catalog ......................................................... 266
Description of DTM Hardware Catalog........................................................ 267
Adding a DTM to the Control Expert Hardware Catalog................................ 271
Adding an EDS File to the Hardware Catalog .............................................. 272
Removing an EDS File from the Hardware Catalog...................................... 274
Export / Import EDS Library ....................................................................... 276
DTM Browser ................................................................................................. 279
DTM Browser ........................................................................................... 279
Ethernet Ready Equipment........................................................................ 284
Ready, Built, Connected and Installed DTMs............................................... 285
DTM Browser Contextual Menus................................................................ 289
Field Bus Discovery Service ...................................................................... 297
Store Device Configurations ...................................................................... 301
Renaming DTMs....................................................................................... 302
Profibus DTMs.......................................................................................... 304
DTM Properties Tabs ...................................................................................... 305
DTM Properties Dialog .............................................................................. 305
Type Library Manager........................................................................................... 310
Libset (Set of Libraries) ................................................................................... 310
Overview of the Type Library Manager ............................................................. 313
Type Library Manager ..................................................................................... 314
Description of the Type Library Manager .......................................................... 317
Loading an object from the library into the project ............................................. 323
Transferring an object from the project into the library........................................ 326
Creating a new library and family ..................................................................... 328
Creating an installable family ........................................................................... 330
Updating a family of a library ........................................................................... 332
Consistency Check Assistant .......................................................................... 334
Library Version Management........................................................................... 337
Using the type library of an older Unity Pro/Control Expert Version ..................... 341
Data Editor ............................................................................................................. 344
Description of the Data Editor................................................................................ 345

6 33003101.26
 Data Editor Access ......................................................................................... 345
Description of Data Editor tabs ........................................................................ 347
Creating derived data types (DDT)......................................................................... 352
Access to derived data types (DDT) ................................................................. 352
Creation of a derived data type (DDT) .............................................................. 353
Administration of derived data types and their elements..................................... 364
Creating Nested Derived Data Types ............................................................... 366
Save Derived Data Types (DDT)...................................................................... 371
Creating data types of user function blocks (DFB)................................................... 374
Creation and Management of Data Types and Function Blocks (DFB) ................ 374
Managing of instances of data belonging to the family of function blocks (EF) ........... 376
Creating / Deleting a variable instance of function blocks (EFB/DFB) .................. 376
Displaying function block variable instances in the editor ................................... 379
Changing the attribute for variable instances in a function block ......................... 382
Managing variable instances belonging to the EDT/DDT/IODDT/Device DDT
families................................................................................................................ 386
Creation of EDT instances............................................................................... 386
Creation of DDT instances............................................................................... 390
Creating an IODDT instance............................................................................ 396
Managing a Device DDT instance .................................................................... 399
Managing an IODDT, DDT or an Array type instance ......................................... 403
Creation of multiple variable instances ............................................................. 409
Displaying the variable instances in the editor ................................................... 411
Changing attributes of variable instances ......................................................... 414
Creation of a Reference Type Instance............................................................. 418
General Functions ............................................................................................... 421
Configuring the Data Editor columns ................................................................ 421
Description of the Data Editor: Variable type selection ....................................... 425
Filtering of Data .............................................................................................. 430
Exporting a subset of variables ........................................................................ 434
Analyze DDT and DFB Data Types................................................................... 435
Purge of Unused Instances ............................................................................. 436
Local printing of data....................................................................................... 437
Save the context of the Data Editor .................................................................. 438
Communication ..................................................................................................... 441

33003101.26 7
 Presentation of the communication editors ............................................................. 442
Presentation of the communication editors of the project browser....................... 442
Network Configuration .......................................................................................... 445
Network Configuration Principle Using Control Expert ....................................... 445
Creating a Logic Network ................................................................................ 446
Configuring a Logic Network............................................................................ 448
Associating a Logic Network with Network Hardware......................................... 449
Configuration of X-Way Routing Premium Stations ................................................. 453
Configuration ................................................................................................. 454
Configuration of Multi-Network Services ........................................................... 455
Configuring an X-Way Router Module .............................................................. 456
Examples of X-Way Routing Stations ............................................................... 460
Examples of Partial Routing ............................................................................ 463
Programming ......................................................................................................... 468
Accessing Tasks, Program Units and Sections ....................................................... 469
Access to Tasks.............................................................................................. 469
Create and Configuration of a Task ............................................................ 469
Displaying and Modifying Task Properties ................................................... 471
Accessing Program Units ................................................................................ 472
Creating Program Units ............................................................................. 472
Properties Dialog Box for Program Units..................................................... 474
Program Unit Data Scope .......................................................................... 479
Program Unit Data Editor Access ............................................................... 482
Description of Program Unit Data Editor Tabs.............................................. 483
Program Unit Variables.............................................................................. 488
Program Unit Management........................................................................ 496
Accessing Sections ........................................................................................ 499
Creating an FBD, LD, IL, or ST Section....................................................... 499
Properties Dialog Box for FBD, LD, IL, or ST Sections ................................. 502
Creating SFC sections .............................................................................. 507
Properties Dialog Box for SFC Sections...................................................... 510
Creating action, transition and macro sections ............................................ 515
Action, transition and macro sections properties dialog box .......................... 516
Create a Sub-Program Section (SR)........................................................... 519
Property Dialog of the Sub-Program Sections ............................................. 521

8 33003101.26
 Creating a Timer Event Section.................................................................. 523
Properties dialog box for Timer Event Sections ........................................... 526
Create an I/O Event Section ...................................................................... 529
Property Dialog of I/O Event Sections......................................................... 531
Opening a Section .................................................................................... 534
Deleting sections ...................................................................................... 535
Execution order of sections........................................................................ 535
Creating LL984 Segments and Networks .................................................... 536
Modifying LL984 Segment Properties ......................................................... 540
Modifying LL984 Network Properties .......................................................... 541
Scheduling LL984 Segments and Network.................................................. 543
Deleting, Cutting, Copying and Pasting LL984 Segments and
Network ................................................................................................... 544
Control Expert Software Options ........................................................................... 546
Project Settings .............................................................................................. 546
General Description ................................................................................. 547
General Project Settings............................................................................ 548
Variables .................................................................................................. 562
Program................................................................................................... 566
Maintain Output Links on Disabled EF (EN=0)............................................. 574
Configuration Settings for Operator Screens ............................................... 583
Options.......................................................................................................... 587
General Description ................................................................................. 587
General Options ....................................................................................... 588
Data and Languages................................................................................. 590
Connection Options .................................................................................. 592
The Operator Screens Option .................................................................... 594
Converters ............................................................................................... 596
Customize Dialog Box..................................................................................... 602
Customize Dialog Box ............................................................................... 602
Common Function for graphical language .............................................................. 607
Using Bookmarks in Graphical Languages Sections.......................................... 607
Display grid in a FBD/LD/SFC section .............................................................. 613
Zoom in a FBD/LD/SFC section ....................................................................... 613
Tracking links in a FBD/LD/SFC section ........................................................... 616

33003101.26 9
 Print Current Section in a FBD/LD/SFC section................................................. 617
Undo and redo changes in a FBD/LD section.................................................... 618
Using connectors in a FBD/LD section ............................................................. 619
Inspect windows in a FBD/LD section............................................................... 624
Tooltips for Variables in a FBD/LD/SFC Section ................................................ 628
Replace Variables in a FBD/LD Section............................................................ 630
Initialize search in a FBD/LD section ................................................................ 635
Initialize Animation Table in a FBD/LD section................................................... 636
Go to in a FBD/LD section ............................................................................... 637
Go to dialog box in a FBD/LD section ............................................................... 639
FBD Editor........................................................................................................... 643
Creating a program with FBD programming language ....................................... 643
Structure of an FBD program (function block language) ............................... 643
Creating an FBD Program ......................................................................... 645
Syntax and Semantics Check during programming...................................... 646
Navigating with the keyboard ..................................................................... 647
Selecting objects ...................................................................................... 648
Deleting, cutting, copying, pasting, duplicating, and moving objects .............. 650
Copying, pasting and adjusting pin variables............................................... 655
Inserting Rows and Columns ..................................................................... 656
Deleting Rows and Columns...................................................................... 657
Displaying the properties ........................................................................... 658
Refining DFBs and subroutines.................................................................. 659
Editing FFBs .................................................................................................. 661
General information about calling an FFB ................................................... 661
Calling an FFB via the FFB Input Assistant. ................................................ 663
Calling an FFB via the data selection .......................................................... 666
Assign actual parameters .......................................................................... 671
Using Public Variables............................................................................... 683
Expanding Functions................................................................................. 684
Negating FFB Pins.................................................................................... 685
EN and ENO Show and Hide ....................................................................... 686
Modifying the execution order .................................................................... 687
Replacing an FFB ..................................................................................... 691

10 33003101.26
 Properties dialog box for elementary functions, procedures and sub-routine
blocks. ..................................................................................................... 693
Properties dialog box for elementary and derived function blocks
(FBs) ....................................................................................................... 695
Returning from a Subroutine or DFB ................................................................ 698
Returning from a Subroutine or DFB........................................................... 698
Return object properties dialog box ............................................................ 700
Calling a Subroutine ....................................................................................... 700
Calling a subroutine .................................................................................. 701
Jumps within the Current Section..................................................................... 705
Jump within the current section .................................................................. 705
Jump object properties dialog box .............................................................. 708
Definition of the Jump Target (Jump Labels) ..................................................... 710
Definitions of Jump Labels......................................................................... 710
Jump label objects properties dialog box..................................................... 713
Editing Links .................................................................................................. 715
Links........................................................................................................ 715
Placing a Link ........................................................................................... 716
Editing Links............................................................................................. 721
Entering Comments ........................................................................................ 729
Entering comments ................................................................................... 729
Online functions ............................................................................................. 731
Online functions........................................................................................ 731
FBD Reference Data Type .............................................................................. 731
Reference Data Type in FBD ..................................................................... 731
Export/Import ................................................................................................. 732
Export/Import FBD Sections ...................................................................... 733
Customize FBD Editor .................................................................................... 733
Customize FBD Editor Colors .................................................................... 733
FBD Favorite Bar..................................................................................... 735
LD Editor ............................................................................................................. 737
Creating a program with LD programming language .......................................... 737
Structure of an LD program (ladder diagram) .............................................. 738
Creating an LD program ............................................................................ 740
Syntax and Semantics Check during programming...................................... 744

33003101.26 11
 View for variables ..................................................................................... 745
Navigating with the Keyboard .................................................................... 750
Selecting objects ...................................................................................... 752
Deleting, cutting, copying, pasting, duplicating, and moving objects .............. 755
Copying, and pasting variables .................................................................. 759
Insert Mode .............................................................................................. 760
Using Mnemonics ..................................................................................... 761
Displaying the properties ........................................................................... 762
Refining DFBs and subroutines.................................................................. 763
Inserting, Deleting, and Copying Rows ....................................................... 765
Columns Management .............................................................................. 766
Editing Contacts ............................................................................................. 767
Select contacts ......................................................................................... 768
Placing contacts ....................................................................................... 769
Property dialog box for contacts ................................................................. 773
Editing Coils................................................................................................... 775
Selection of coils....................................................................................... 776
Placing coils ............................................................................................. 778
Property dialog box for coils....................................................................... 783
Editing compare blocks ................................................................................... 786
Placing compare blocks............................................................................. 787
Compare block properties dialog box.......................................................... 790
Editing operation blocks .................................................................................. 792
Placing Operate Blocks ............................................................................. 792
Operate block properties dialog box ........................................................... 796
Editing FFBs .................................................................................................. 798
General information on calling an FFB ........................................................ 799
Calling an FFB via the FFB input assistant .................................................. 800
Calling an FFB via the data selection .......................................................... 804
Connection of FFBs to the Left Power Rail .................................................. 808
Assigning Actual Parameters ..................................................................... 809
Using Public Variables............................................................................... 822
Expanding Functions................................................................................. 824
Negating FFB Pins.................................................................................... 826
EN and ENO Show and Hide ....................................................................... 827

12 33003101.26
 Properties dialog box for elementary functions, procedures and sub-routine
blocks. ..................................................................................................... 827
Properties dialog box for elementary and derived function blocks
(FBs) ....................................................................................................... 830
Returning from a Subroutine or DFB ................................................................ 832
Returning from a subroutine or DFB ........................................................... 832
Return object properties dialog box ............................................................ 834
Jumps within the Current Section..................................................................... 835
Jumps within the current section ................................................................ 835
Jump object properties dialog box .............................................................. 838
Definition of the Jump Target (Jump Labels) ..................................................... 840
Definitions of jump targets (jump labels) ..................................................... 840
Jump label properties dialog box ................................................................ 843
Editing Links .................................................................................................. 845
Select links............................................................................................... 845
Combining Links ....................................................................................... 847
Placing links ............................................................................................. 849
Editing links .............................................................................................. 864
Entering Comments ........................................................................................ 872
Entering comments ................................................................................... 872
Online functions ............................................................................................. 874
Online Functions....................................................................................... 874
LD Reference Data Type................................................................................. 874
Reference Data Type in LD........................................................................ 874
Export/Import ................................................................................................. 875
Export/Import LD Sections ......................................................................... 876
Customize LD Editor ....................................................................................... 876
Customize LD Editor Colors....................................................................... 876
LD Instruction Bar................................................................................... 878
LD Favorite Bar ....................................................................................... 879
SFC Editor........................................................................................................... 882
Creating a program with the SFC programming language .................................. 882
Structure of an SFC Program (Sequential Function Chart) ........................... 883
Creating an SFC Program ......................................................................... 885
Syntax and Semantics Check during Programming ..................................... 886

33003101.26 13
 Navigating with the keyboard ..................................................................... 887
Selecting Objects...................................................................................... 889
Undo and Redo Changes .......................................................................... 891
Deleting, cutting, copying, pasting and moving objects................................. 892
Inserting Rows and Columns ..................................................................... 897
Deleting Rows and Columns...................................................................... 899
Displaying the object properties ................................................................. 900
Initialize Search ........................................................................................ 901
Initialize Animation Table ........................................................................... 902
Refining steps, macro steps and transitions ................................................ 904
Go to ....................................................................................................... 905
Go to dialog.............................................................................................. 907
List and display jumps ............................................................................... 911
Go to Step................................................................................................ 912
General Information about Steps ..................................................................... 913
Selecting steps ......................................................................................... 913
Placing steps............................................................................................ 915
Editing "normal" steps ..................................................................................... 916
Defining the properties of steps.................................................................. 917
Steps properties dialog box ....................................................................... 924
Editing macro steps ........................................................................................ 929
Defining the properties of macro steps........................................................ 930
Macro Steps Properties Dialog Box ............................................................ 937
Editing input steps .......................................................................................... 940
Defining the properties of InSteps .............................................................. 940
InSteps properties dialog box..................................................................... 942
Editing Output Steps ....................................................................................... 946
Defining the properties of OutSteps ............................................................ 947
OutStep properties dialog box.................................................................... 948
Editing actions................................................................................................ 950
Assigning actions to a step ........................................................................ 951
Display modes for actions.......................................................................... 960
Editing Transitions .......................................................................................... 961
Placing transitions..................................................................................... 961
Defining transition properties ..................................................................... 963

14 33003101.26
 Properties dialog box for transitions............................................................ 968
Editing Jumps ................................................................................................ 970
Placing jumps ........................................................................................... 971
Defining jump properties............................................................................ 972
Jump properties dialog box........................................................................ 974
Editing Branches and Joints ............................................................................ 976
Selecting Branches and Joints ................................................................... 977
Placing branches and joints ....................................................................... 978
Modifying the Properties of Branches and Joints ......................................... 979
Branches properties dialog box .................................................................. 982
Joints properties dialog box ....................................................................... 983
Inserting Alternative Strings and Simultaneous Strings ...................................... 984
Selecting Alternative Sequences and Parallel Sequences ............................ 984
Placing alternative sequences and parallel sequences................................. 985
Inserting Step-Transitions and Transition-Step-Sequences ................................ 988
Selecting Step-Transition and Transition-Step Sequences ........................... 988
Placing step-transition and transition-step sequences.................................. 989
Editing Links .................................................................................................. 992
Links........................................................................................................ 993
Placing a Link ........................................................................................... 994
Editing links .............................................................................................. 998
Entering Comments ...................................................................................... 1003
Entering comments ................................................................................. 1003
Online functions ........................................................................................... 1005
Online functions...................................................................................... 1005
Export/Import ............................................................................................... 1005
Export/Import SFC Sections .................................................................... 1005
Customize SFC Editor Colors ........................................................................ 1005
Customize SFC Editor Colors .................................................................. 1006
Common Function for Textual Language .............................................................. 1009
Selecting Text............................................................................................... 1009
Deleting, cutting, copying, pasting and moving text.......................................... 1012
Undoing and redoing changes ....................................................................... 1014
Match case .................................................................................................. 1015
Zoom (font size) ........................................................................................... 1016

33003101.26 15
 Using Bookmarks ......................................................................................... 1017
Go to ........................................................................................................... 1019
Go to dialog box ........................................................................................... 1021
Searching text .............................................................................................. 1023
Searching and replacing text ......................................................................... 1025
Call a subroutine .......................................................................................... 1027
Refine DFBs and subroutines ........................................................................ 1028
Inspect windows ........................................................................................... 1030
Enter comments .......................................................................................... 1034
Printing the Current Section........................................................................... 1035
Initialize search ............................................................................................ 1036
Initialize Animation table ............................................................................... 1037
Displaying the section properties ................................................................... 1039
Fullscreen .................................................................................................... 1039
Customize IL and ST Editor Colors ................................................................ 1040
IL Editor............................................................................................................. 1044
Structure of an IL program............................................................................. 1044
Creating an IL Program ................................................................................. 1046
Syntax and Semantics Check during Programming ......................................... 1047
Navigating with the keyboard......................................................................... 1052
Data input .................................................................................................... 1053
Calling an FFB ............................................................................................. 1059
Using Public Variables .................................................................................. 1070
Online functions ........................................................................................... 1072
Reference Data Type in IL ............................................................................. 1072
Export/Import IL Sections .............................................................................. 1073
ST Editor ........................................................................................................... 1075
Structure of an ST program ........................................................................... 1075
Creating an ST Program ............................................................................... 1077
Syntax and Semantics Check during Programming ......................................... 1078
Navigating with the keyboard......................................................................... 1082
Data input .................................................................................................... 1083
Calling an FFB ............................................................................................. 1090
Using public variables ................................................................................... 1101
Calling a statement ....................................................................................... 1103

16 33003101.26
 Online functions ............................................................................................1110
Reference Data Type in ST ............................................................................1111
Export/Import IL Sections ...............................................................................1111
LL984 Editor .......................................................................................................1113
Creating a Program with LL984 Programming Language ..................................1113
Project Settings for LL984 Programs .........................................................1113
Structure of an LL984 Program .................................................................1114
Creating an LL984 Program......................................................................1117
Syntax and Semantics Check During Programming....................................1119
Network Display...................................................................................... 1122
Navigating with the Keyboard .................................................................. 1123
Selecting Objects.................................................................................... 1125
Deleting, Cutting, Copying, Pasting and Moving Objects ............................ 1127
Displaying the Properties......................................................................... 1130
Inserting and Deleting Rows/Columns ...................................................... 1130
Editing Contacts ........................................................................................... 1132
Selecting Contacts .................................................................................. 1132
Placing Contacts..................................................................................... 1134
Properties Dialog for Contacts ................................................................. 1137
Editing Coils................................................................................................. 1139
Selecting Coils........................................................................................ 1140
Placing Coils .......................................................................................... 1142
Property Dialog for Coils.......................................................................... 1145
Editing Function Blocks................................................................................. 1147
Editing Function Blocks ........................................................................... 1147
Using Mnemonics ................................................................................... 1150
Editing Links ................................................................................................ 1151
Selecting Links ....................................................................................... 1151
Combining Links ..................................................................................... 1152
Placing Links .......................................................................................... 1153
Editing Links........................................................................................... 1155
Editing Equation Network Blocks ................................................................... 1156
Editing Equation Network Blocks.............................................................. 1156
Editing the ST Assignment Expression ..................................................... 1158
Assigning Variables to LL984 Objects ............................................................ 1163

33003101.26 17
 Assigning Variables to LL984 Objects....................................................... 1163
Calling Subroutines ...................................................................................... 1166
Calling Subroutines................................................................................. 1166
Entering Comments ...................................................................................... 1168
Entering Comments ................................................................................ 1168
Customize LL984 Editor Colors ..................................................................... 1170
Customize LL984 Editor Colors................................................................ 1170
Programming Languages Data Selection Dialog Box ............................................ 1174
Instance selection dialog box......................................................................... 1174
FFB Selection Dialog box .............................................................................. 1179
FFB Type Selection Dialog box ...................................................................... 1183
Data selection dialog box............................................................................. 1185
Function Input Assistant ................................................................................ 1192
Data Properties ............................................................................................ 1195
Generate variables ....................................................................................... 1197
I/O Objects tab ................................................................................................... 1200
Introduction to the I/O Object Tab................................................................... 1200
I/O Objects Tab for a Processor ..................................................................... 1202
I/O Objects Tab for a Module ......................................................................... 1204
Details of Areas in the I/O Objects Tab ........................................................... 1206
I/O Objects Tab for a Bus Device ................................................................... 1212
How to Use the I/O Objects Tab ..................................................................... 1212
Memory Tab....................................................................................................... 1218
Memory Tab ................................................................................................. 1218
Type Library Browser.......................................................................................... 1224
Access to the Type Library Browser ............................................................... 1224
Description of the Type Library Browser ......................................................... 1226
Configuration of Columns of the Type Library Browser..................................... 1228
Drag & Drop of FFBs in a program section...................................................... 1230
Search/Replace Tool .......................................................................................... 1232
Overview of the Search / Replace tool ............................................................ 1232
General Features for Search/Replace ............................................................ 1234
Searching for Data........................................................................................ 1235
Replacing Data............................................................................................. 1236
Search Toolbar ............................................................................................. 1237

18 33003101.26
 Data Search Dialog....................................................................................... 1239
Cross-References (Search Results) ............................................................... 1240
Cross-References (Replace) ......................................................................... 1243
Tracing Variables / Addresses ....................................................................... 1245
User's Function Blocks ....................................................................................... 1247
DFB Type..................................................................................................... 1247
DFB Type............................................................................................... 1247
Creating a DFB Type............................................................................... 1249
Configuration of a DFB Type .................................................................... 1250
Programming a DFB type ........................................................................ 1254
Deleting a DFB type element ................................................................... 1256
Archiving a DFB Type.............................................................................. 1257
How to Reinforce Protection of a DFB Type .............................................. 1258
Deleting a DFB Type ............................................................................... 1260
How to access the attributes of a DFB type ............................................... 1261
Authorized DFB Type Modifications.......................................................... 1262
DFB Instance ............................................................................................... 1266
DFB Instance ......................................................................................... 1266
Creating a DFB Instance ......................................................................... 1267
Creating several DFB Instances............................................................... 1269
Deleting a DFB instance .......................................................................... 1269
Operations on DFB Instances .................................................................. 1269
Modifying the Attributes of a DFB Instance................................................ 1272
Authorized DFB Instance Modifications .................................................... 1276
Searching / Animating DFB Instances....................................................... 1277
How to Create Nested DFBs.......................................................................... 1279
How to Create Nested DFBs .................................................................... 1279
Project Configuration ......................................................................................... 1280
Introduction to the configuration........................................................................... 1281
Proposed Services ....................................................................................... 1281
Services offered in offline mode ..................................................................... 1286
Services Offered In Online Mode ................................................................... 1287
Access to project configuration ...................................................................... 1288
Bus Editors ........................................................................................................ 1294
Rack configuration on local bus ..................................................................... 1294

33003101.26 19
 Organization of the Racks ....................................................................... 1294
How to configure the racks ...................................................................... 1299
Configuration of the power supply modules..................................................... 1300
How to configure the power supply modules ............................................. 1301
Configuration of the processor ....................................................................... 1303
Choice and replacement of the processor ................................................. 1303
Configuration of the modules in the PLC station .............................................. 1307
How to configure the modules in the PLC station ....................................... 1307
Configuration of devices on the field bus......................................................... 1311
Configuration of the CANopen Slaves for Modicon M340 ........................... 1311
How to access and create a Fipio field bus................................................ 1314
Creating and Accessing RIO\DIO Field Buses........................................... 1318
How to configure devices on the RIO/DIO bus........................................... 1324
Consumption management ........................................................................... 1329
Power consumption budget ..................................................................... 1329
Budget on the number of application-specific channels .............................. 1332
Bus editors in online mode ............................................................................ 1335
Online Information .................................................................................. 1336
Modules editor ................................................................................................... 1340
Configuration of Modicon M340 processors .................................................... 1340
Configuration of Modicon M340 Processors .............................................. 1340
Configuration of Premium processors............................................................. 1353
Configuration of Premium\Atrium processors ............................................ 1353
Access to PCMCIA memory cards of Premium processors......................... 1360
Access to control loop configuration for Premium processors ..................... 1361
Configuration of the Quantum processors....................................................... 1363
Configuration of Quantum processors ...................................................... 1363
Configuration of Modbus ports on Quantum .............................................. 1369
Configuration of the input\output modules for a Premium\Atrium, Quantum or
Modicon M340 station................................................................................... 1372
Access to the Modicon, Premium or Atrium I/O module configuration
editor ..................................................................................................... 1372
Access the Quantum input/output module configuration editor.................... 1374
General functionalities of the editor...................................................................... 1377
Analysis of the configuration .......................................................................... 1377

20 33003101.26
 Export\Import of the configuration .................................................................. 1378
Printing the configuration............................................................................... 1378
Debugging and adjustment ............................................................................... 1381
Debugging the program ...................................................................................... 1382
Safety precautions........................................................................................ 1382
Modification in RUN ................................................................................ 1383
Switch to STOP of a PLC in Debug mode ................................................. 1383
Setting a task to STOP ............................................................................ 1384
Task deactivation .................................................................................... 1385
Deactivation of Inputs/Outputs ................................................................. 1386
Use of the Step by Step mode and Breakpoint .......................................... 1387
Unwanted disconnection in Debug mode for Premium ............................... 1387
Debug Screen Via a Fipway, Fipio or Uni-Telway Network with a PCMCIA
Card ...................................................................................................... 1388
Behavior of Forced Variables between Modsoft/NxT/Concept and Control
Expert .................................................................................................... 1388
Program Animation....................................................................................... 1389
Introduction to animation ......................................................................... 1389
Section in textual languages (Structured Text or Instruction List)................. 1393
Section in a Ladder Diagram language ..................................................... 1394
Section in Function Block Diagram (FBD) language................................... 1397
Section in Sequential Function Chart language (SFC)................................ 1399
Display of Prepositioned steps, after an on-line modification....................... 1400
DFB instances (user function blocks)........................................................ 1401
Representation of forced variables ........................................................... 1404
Debugging in Ladder Language..................................................................... 1405
Inserting a breakpoint in Ladder Diagram language (LD)............................ 1405
Step by step execution mode in Ladder Diagram language (LD) ................. 1408
Inserting a Watchpoint in Ladder Diagram Language ................................. 1411
Debugging in Textual Languages (Structured Text, Instruction List) .................. 1413
Insertion of a breakpoint in textual languages (Structured Text or
Instruction List) ....................................................................................... 1414
Step by step execution mode in textual languages (Structured Text or
Instruction List) ....................................................................................... 1416

33003101.26 21
 Insertion of a Watchpoint in Textual Languages (Structured Text or
Instruction List) ....................................................................................... 1419
Debugging in Function Block Diagram (FBD) Language .................................. 1422
Inserting a breakpoint in Function Block Diagram language........................ 1422
Step by step execution mode in Function Block Diagram language
(FBD)..................................................................................................... 1425
Inserting a watchpoint in Function Block Diagram language (FBD).............. 1428
Debugging User Function Block (DFB) Instances............................................ 1431
Inserting a breakpoint in a DFB instance (user function block) .................... 1432
Step by step execution mode in a DFB instance (user function
block)..................................................................................................... 1433
Inserting a watchpoint in a user function block (DFB) ................................. 1434
Debugging in Sequential Function Chart Language (SFC) ............................... 1435
Inserting a breakpoint in Sequential Function Chart language
(SFC)..................................................................................................... 1435
Step by step execution mode in Sequential Function Chart language
(SFC)..................................................................................................... 1439
Inserting a watchpoint in Sequential Function Chart language .................... 1443
Information on Debugging ............................................................................. 1443
Tracing task execution ............................................................................ 1444
Task states during debugging .................................................................. 1446
Disconnection during the debug phase ..................................................... 1446
Operation of the alarm relay in Debug mode ............................................. 1447
PLC debug screen ........................................................................................ 1448
Overview of the CPU debugging screen ................................................... 1448
Description of the Task tab: Task checking field ......................................... 1450
Description of the Task tab: Operating mode field ...................................... 1451
Description of tab: Realtime Clock............................................................ 1454
Description of the Tab: Information ........................................................... 1455
Viewing and adjusting variables........................................................................... 1460
Introduction to variable animation .................................................................. 1460
Displaying variables in debug mode ......................................................... 1460
Variable Display Window............................................................................... 1461
Introduction to the Variable Output Window............................................... 1462
Variable Display Boxes ................................................................................. 1464

22 33003101.26
 Introduction to variable display boxes ....................................................... 1465
Animation Tables .......................................................................................... 1467
Permanent and Temporary Animation Tables ............................................ 1467
Introduction to Animation Tables .............................................................. 1469
Managing Animation Tables..................................................................... 1470
Multiple Modifications of Animation Table Variables ................................... 1473
Animation Table Properties ...................................................................... 1474
Basic functions ....................................................................................... 1475
Animation of Strings in the Animation Table............................................... 1479
Modification Mode................................................................................... 1481
Force Mode ............................................................................................ 1486
Multiple modification and forcing of Boolean variables ............................... 1491
Animation Table of Forced Bits................................................................. 1494
Instruction Editor (LL984) .............................................................................. 1495
Instruction Editor..................................................................................... 1495
Modifying values:.......................................................................................... 1498
Modifying values: .................................................................................... 1498
Machine-Process Simulator ................................................................................ 1502
Introduction .................................................................................................. 1502
Diagnostics .......................................................................................................... 1504
Introduction to diagnostics tools........................................................................... 1505
Diagnostics with Control Expert ..................................................................... 1505
Diagnostics screens ........................................................................................... 1508
Module and processor diagnostics screens .................................................... 1508
Viewing fault diagnostics ......................................................................... 1508
Lists of fault diagnostics .......................................................................... 1510
Diagnostics Viewer............................................................................................. 1514
Reminder of the Diagnostics Associated with the Viewer ................................. 1514
Operation of the diagnostics in Control Expert ................................................ 1516
Description of the Diagnostics Viewer ............................................................ 1517
How to find causes ....................................................................................... 1520
Configuring the display.................................................................................. 1522
Managing error messages............................................................................. 1524
Diagnostics Viewer Commands ..................................................................... 1526
DiagViewer Properties .................................................................................. 1528

33003101.26 23
 Archiving error messages.............................................................................. 1530
System diagnostics ............................................................................................ 1535
System diagnostic ........................................................................................ 1535
Project diagnostics ............................................................................................. 1539
How to Create a User Diagnostic DFB............................................................ 1539
Project diagnostic ......................................................................................... 1541
Operator screen .................................................................................................. 1545
General information............................................................................................ 1546
Introduction .................................................................................................. 1546
Creation of Runtime Screens......................................................................... 1547
First steps.......................................................................................................... 1549
Working principles ........................................................................................ 1549
How to access the operator screens ......................................................... 1549
Menus and tools in the runtime screen editor .................................................. 1550
Menus in the operator screen editor ......................................................... 1551
Edit toolbar............................................................................................. 1554
Configuring options from the runtime screen editor.......................................... 1557
General configuration of operator screens ................................................ 1558
Editing runtime screens ...................................................................................... 1559
Editing screens from the browser .................................................................. 1559
Editing operator screens.......................................................................... 1559
Operator screen editor functions .............................................................. 1561
Screen Family Editor Functions................................................................ 1565
Operator screen properties ...................................................................... 1567
Properties of Operator Screen Families .................................................... 1569
Creating an object ........................................................................................ 1571
Introduction of a graphic screen object...................................................... 1571
How to create standard objects ................................................................ 1571
How to insert an image in a screen ........................................................... 1573
How to create driving objects ................................................................... 1575
Operation of the driving objects................................................................ 1576
Default Properties screen.............................................................................. 1580
Default Properties screen ........................................................................ 1580
Modification of an object’s attributes............................................................... 1582
How to access an object’s attributes ......................................................... 1582

24 33003101.26
 Design tab.............................................................................................. 1583
Extended colors...................................................................................... 1584
Text tab .................................................................................................. 1585
Animation Tab......................................................................................... 1587
Animation type tab .................................................................................. 1589
Trend diagrams ...................................................................................... 1592
Bar chart ................................................................................................ 1593
Screen browse tab .................................................................................. 1595
Control tab ............................................................................................. 1597
Image Tab .............................................................................................. 1599
Explicit Exchanges Tab ........................................................................... 1601
Information on the objects ....................................................................... 1602
The data selection tool ............................................................................ 1604
Manipulation of objects in runtime screens ..................................................... 1607
How to select graphic objects................................................................... 1607
How to move and resize objects............................................................... 1608
How to delete and copy objects................................................................ 1610
How to position objects............................................................................ 1611
How to create compound objects ............................................................. 1613
Managing the runtime screens messages editor ............................................. 1615
Operator screens messages editor........................................................... 1615
How to manage messages linked to operator screens ............................... 1617
Find dialog box ....................................................................................... 1619
Replace dialog box ................................................................................. 1620
Message Renumbering Dialog Box .......................................................... 1621
Message editing and import/export function .............................................. 1622
Runtime screens in online mode.......................................................................... 1626
Basic functions in online mode....................................................................... 1626
How to select an animated object................................................................... 1627
How to use command objects to modify the variables associated with
objects......................................................................................................... 1628
How to view the variables associated with graphic objects ............................... 1629
How to modify the variables associated with objects from an animation
table ............................................................................................................ 1630
How to search for cross-references................................................................ 1631

33003101.26 25
 How to manage the display of operator screens .............................................. 1632
How to modify screen control......................................................................... 1634
How to obtain information on objects when in connected mode ........................ 1635
Runtime screens objects library........................................................................... 1637
Managing library objects ............................................................................... 1637
The Objects Library................................................................................. 1637
How to manage the list of graphic items in the library ................................. 1638
Properties of the object library and its elements......................................... 1641
Handling the Objects............................................................................... 1644
Dereferencing in Operator Screens .......................................................... 1647
Documentation, Import/export .......................................................................... 1650
Documentation................................................................................................... 1651
Creating Project Documentation .................................................................... 1651
Documentation Structure .............................................................................. 1652
Topics in Documentation ............................................................................... 1654
Creating Project Documentation .................................................................... 1663
Print Preview................................................................................................ 1666
Page Setup .................................................................................................. 1668
Print ............................................................................................................ 1669
Printout Setup .............................................................................................. 1672
Import / Export ................................................................................................... 1677
General information on the Import/Export function........................................... 1677
General Information on Import/Export....................................................... 1677
Import / Export Files ................................................................................ 1679
Type of dialog box for the export function .................................................. 1680
Type of dialog boxes for the import function .............................................. 1683
Managing Conflicts ................................................................................. 1685
Importing/Exporting the various elements of Control Expert ............................ 1687
Export of the input/output configuration..................................................... 1687
Import of the input/output configuration ..................................................... 1689
Exporting the program............................................................................. 1690
Importing the Program............................................................................. 1692
Exporting DFB types ............................................................................... 1694
Importing DFB types ............................................................................... 1695
Exporting DDTs ...................................................................................... 1696

26 33003101.26
 Importing DDTs....................................................................................... 1697
Exporting Variables ................................................................................. 1698
Importing Variables ................................................................................. 1701
Exporting the communication network configuration .................................. 1702
Importing the configuration of a communication network ............................ 1703
Exporting operator screens...................................................................... 1704
Importing operator screens ...................................................................... 1705
Exporting animation tables ...................................................................... 1707
Importing animation tables....................................................................... 1708
Exporting a functional module .................................................................. 1709
Importing a functional module .................................................................. 1710
Exporting a global project ........................................................................ 1711
Importing a global project ........................................................................ 1713
Exporting/Importing LL984 Segments/Networks ........................................ 1715
Wizard for importing the various elements of Control Expert ............................ 1717
Using the assistant.................................................................................. 1717
Variables tab of the wizard ....................................................................... 1722
DFB and DDT Tabs of the Wizard............................................................. 1724
SR, Sections, Events and Macro steps tabs of the wizard .......................... 1725
Wizard animation tables tab..................................................................... 1727
Wizard functional module tabs ................................................................. 1727
Correspondence file................................................................................ 1729
Conversion Wizard ............................................................................................. 1732
Conversion Wizard ............................................................................................. 1733
General Description of the Conversion Wizard ................................................ 1733
Introduction ............................................................................................ 1733
Access to Conversion Wizard .................................................................. 1735
General Representation .......................................................................... 1737
Conversion and Result ............................................................................ 1738
Structure Tab of the Conversion Wizard.......................................................... 1739
Introduction ............................................................................................ 1739
Selecting Application Parts to be Converted.............................................. 1741
I/O Remapping Tab of the Conversion Wizard................................................. 1743
Introduction ............................................................................................ 1743
Remapping Table.................................................................................... 1746

33003101.26 27
 Remapping Channels, Groups of Channels or Specific I/O Types ............... 1749
Clustering and Remapping of Memory Variables ....................................... 1752
Memory Area Tabs of the Conversion Wizard............................................ 1753
Concurrent Editing .................................................................................. 1755
Exclude, Communication -1, Type Restriction ........................................... 1757
CPU Configuration Tab of the Conversion Wizard ........................................... 1761
Introduction ............................................................................................ 1762
Appendices .......................................................................................................... 1764
Hyperlinks in Control Expert ............................................................................... 1765
General ....................................................................................................... 1765
Introduction to Hyperlinks ........................................................................ 1765
Representation and opening of a hyperlink ............................................... 1767
Principles..................................................................................................... 1768
Definitions .............................................................................................. 1768
Overview of operate-modes..................................................................... 1769
1-step mode ........................................................................................... 1769
2-step mode ........................................................................................... 1771
Description of the Hyperlink Comment Window ......................................... 1772
Properties .............................................................................................. 1775
List of barred characters .......................................................................... 1776
Hyperlinks in the project browser ................................................................... 1777
Creating a hyperlink in the project browser................................................ 1777
Editing the properties of a hyperlink in the project browser ......................... 1778
Opening a hyperlink from the project browser............................................ 1780
Deleting a hyperlink in the project browser ................................................ 1780
Hyperlink in the data editor ............................................................................ 1781
Creating a hyperlink in the data editor....................................................... 1781
Editing a hyperlink in the data editor ......................................................... 1783
Selecting a hyperlink in the data editor...................................................... 1785
Deleting a hyperlink in the data editor ....................................................... 1786
Hyperlinks in the DFB type attributes.............................................................. 1787
Creating a Hyperlink from DFB Type Attributes ......................................... 1787
Modifying a Hyperlink from DFB Type Attributes ........................................ 1789
Selecting a Hyperlink from DFB Type Attributes ........................................ 1791
Deleting a Hyperlink from DFB Type Attributes .......................................... 1793

28 33003101.26
 Hyperlinks in animation tables ....................................................................... 1795
Creating a hyperlink in an animation table................................................. 1795
Editing a hyperlink from an animation table ............................................... 1797
Selecting a hyperlink from an animation table............................................ 1798
Deleting a hyperlink from an animation table ............................................. 1799
Hyperlinks in runtime screens........................................................................ 1799
Creating a hyperlink from operator screens ............................................... 1800
Editing a hyperlink in the operator screens ................................................ 1801
Selecting a hyperlink in an operator screen ............................................... 1803
Deleting a hyperlink in an operator screen ................................................ 1803
Hyperlinks in the documentation folder ........................................................... 1805
Creating a hyperlink in the general information of the project folder ............ 1805
Editing a hyperlink in the documentation folder.......................................... 1807
Deleting a hyperlink in the documentation folder........................................ 1809
Hyperlinks and drag-and-drop ....................................................................... 1810
Drag/drop............................................................................................... 1811
User Interface .................................................................................................... 1816
Window ....................................................................................................... 1816
Anchored window ......................................................................................... 1818
Menus ......................................................................................................... 1821
Menu commands.......................................................................................... 1823
Toolbar ........................................................................................................ 1826
Output windows............................................................................................ 1832
Status bar .................................................................................................... 1834
Directory Structures ...................................................................................... 1837
Using the Mouse .......................................................................................... 1838
Using the Keyboard ...................................................................................... 1839
Data selection boxes .................................................................................... 1841
Dialog boxes ................................................................................................ 1842
Keyboard Shortcuts............................................................................................ 1848
General Keyboard Shortcuts ......................................................................... 1848
Bus Editor Keyboard Shortcuts ................................................................ 1848
Control Expert Main Screen and Project Browser Keyboard
Shortcuts ............................................................................................... 1849
Configuring the Project.................................................................................. 1851

33003101.26 29
 PLC Configuration Screen Keyboard Shortcuts ......................................... 1851
Creating the Project ...................................................................................... 1852
ST/IL Editors Keyboard Shortcuts ............................................................ 1852
FBD Editor Keyboard Shortcuts ............................................................... 1854
SFC Editor Keyboard Shortcuts ............................................................... 1855
LD Editor Keyboard Shortcuts.................................................................. 1857
Data Editor Keyboard Shortcuts ............................................................... 1859
Type Library Browser Keyboard Shortcuts ................................................ 1860
Type Library Manager Keyboard Shortcuts ............................................... 1861
Operating the Project .................................................................................... 1861
Search Replace Tool Screen Keyboard Shortcuts...................................... 1862
Diagnostic Viewer Screen Keyboard Shortcuts.......................................... 1862
PLC Screen Keyboard Shortcuts.............................................................. 1862
Animation Screen Keyboard Shortcuts ..................................................... 1863
Operator Screen Keyboard Shortcuts ....................................................... 1864
Documenting the Project ............................................................................... 1865
Documentation Screen Keyboard Shortcuts.............................................. 1865
Glossary ............................................................................................................... 1867
Index ..................................................................................................................... 1875

30 33003101.26
Safety Information

Safety Information
Important Information
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.

The addition of this symbol to a “Danger” or “Warning” safety label indicates that an
electrical hazard exists which will result in personal injury if the instructions are not
followed.

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

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

! WARNING
WARNING indicates a hazardous situation which, if not avoided, could result in death or
serious injury.

! CAUTION
CAUTION indicates a hazardous situation which, if not avoided, could result in minor or
moderate injury.

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

33003101.26 31
 Safety Information

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.

Before You Begin

Do not use this product on machinery lacking effective point-of-operation guarding. Lack of
effective point-of-operation guarding on a machine can result in serious injury to the
operator of that machine.

WARNING
UNGUARDED EQUIPMENT
• Do not use this software and related automation equipment on equipment which does
not have point-of-operation protection.
• Do not reach into machinery during operation.
Failure to follow these instructions can result in death, serious injury, or equipment
damage.

This automation equipment and related software is used to control a variety of industrial
processes. The type or model of automation equipment suitable for each application will
vary depending on factors such as the control function required, degree of protection
required, production methods, unusual conditions, government regulations, etc. In some
applications, more than one processor may be required, as when backup redundancy is
needed.
Only you, the user, machine builder or system integrator can be aware of all the conditions
and factors present during setup, operation, and maintenance of the machine and,
therefore, can determine the automation equipment and the related safeties and interlocks
which can be properly used. When selecting automation and control equipment and related
software for a particular application, you should refer to the applicable local and national
standards and regulations. The National Safety Council's Accident Prevention Manual
(nationally recognized in the United States of America) also provides much useful
information.
In some applications, such as packaging machinery, additional operator protection such as
point-of-operation guarding must be provided. This is necessary if the operator's hands and

32 33003101.26
Safety Information

other parts of the body are free to enter the pinch points or other hazardous areas and
serious injury can occur. Software products alone cannot protect an operator from injury. For
this reason the software cannot be substituted for or take the place of point-of-operation
protection.
Ensure that appropriate safeties and mechanical/electrical interlocks related to point-of-
operation protection have been installed and are operational before placing the equipment
into service. All interlocks and safeties related to point-of-operation protection must be
coordinated with the related automation equipment and software programming.
NOTE: Coordination of safeties and mechanical/electrical interlocks for point-of-
operation protection is outside the scope of the Function Block Library, System User
Guide, or other implementation referenced in this documentation.

Start-up and Test

Before using electrical control and automation equipment for regular operation after
installation, the system should be given a start-up test by qualified personnel to verify
correct operation of the equipment. It is important that arrangements for such a check are
made and that enough time is allowed to perform complete and satisfactory testing.

WARNING
EQUIPMENT OPERATION HAZARD
• Verify that all installation and set up procedures have been completed.
• Before operational tests are performed, remove all blocks or other temporary holding
means used for shipment from all component devices.
• Remove tools, meters, and debris from equipment.
Failure to follow these instructions can result in death, serious injury, or equipment
damage.

Follow all start-up tests recommended in the equipment documentation. Store all equipment
documentation for future references.
Software testing must be done in both simulated and real environments.
Verify that the completed system is free from all short circuits and temporary grounds that
are not installed according to local regulations (according to the National Electrical Code in
the U.S.A, for instance). If high-potential voltage testing is necessary, follow
recommendations in equipment documentation to prevent accidental equipment damage.
Before energizing equipment:
• Remove tools, meters, and debris from equipment.

33003101.26 33
 Safety Information

• Close the equipment enclosure door.

• Remove all temporary grounds from incoming power lines.
• Perform all start-up tests recommended by the manufacturer.

Operation and Adjustments

The following precautions are from the NEMA Standards Publication ICS 7.1-1995 (English
version prevails):
• Regardless of the care exercised in the design and manufacture of equipment or in the
selection and ratings of components, there are hazards that can be encountered if such
equipment is improperly operated.
• It is sometimes possible to misadjust the equipment and thus produce unsatisfactory or
unsafe operation. Always use the manufacturer’s instructions as a guide for functional
adjustments. Personnel who have access to these adjustments should be familiar with
the equipment manufacturer’s instructions and the machinery used with the electrical
equipment.
• Only those operational adjustments actually required by the operator should be
accessible to the operator. Access to other controls should be restricted to prevent
unauthorized changes in operating characteristics.

34 33003101.26
About the Book

About the Book

Document Scope
This document describes programming a Modicon M340, Modicon M580, Momentum,
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 EcoStruxure™ Control Expert 15.1 or later.

Related Documents
Title of documentation Reference number
EcoStruxure™ Control Expert, Program Languages 35006144 (English), 35006145 (French), 35006146
and Structure, Reference Manual (German), 35013361 (Italian), 35006147 (Spanish),
35013362 (Chinese)

EcoStruxure™ Control Expert, System Bits and Words, EIO0000002135 (English), EIO0000002136 (French),
Reference Manual EIO0000002137 (German), EIO0000002138 (Italian),
EIO0000002139 (Spanish), EIO0000002140
(Chinese)

EcoStruxure™ Control Expert, Installation Manual 35014792 (English), 35014793 (French), 35014794
(German), 35014795 (Spanish), 35014796 (Italian),
35012191 (Chinese)

EcoStruxure™ Control Expert, LL984 Editor, Reference EIO0000000549 (English), EIO0000000802 (French),
Manual EIO0000000803 (German), EIO0000000804 (Italian),
EIO0000000805 (Spanish), EIO0000000806
(Chinese)

EcoStruxure™ Control Expert, Concept Application 33002515 (English), 33002516 (French), 33002517
Converter, User Manual (German), 33003676 (Italian), 33002518 (Spanish),
33003677 (Chinese)

EcoStruxure™ Control Expert, PL7 Application 35006148 (English), 35006149 (French), 35006150
Converter, User Manual (German), 35013967 (Italian), 35006151 (Spanish),
35012199 (Chinese)

Modicon M580, Hardware, Reference Manual EIO0000001578 (English), EIO0000001579 (French),

EIO0000001580 (German), EIO0000001582 (Italian),
EIO0000001581 (Spanish), EIO0000001583
(Chinese)

Modicon M580, Change Configuration on the Fly, User EIO0000001590 (English), EIO0000001591 (French),
Guide EIO0000001592 (German), EIO0000001594 (Italian),

33003101.26 35
 About the Book

Title of documentation Reference number

EIO0000001593 (Spanish), EIO0000001595
(Chinese)

Modicon M580 Hot Standby, System Planning Guide NHA58880 (English), NHA58881 (French),
for Frequently Used Architectures NHA58882 (German), NHA58883 (Italian), NHA58884
(Spanish), NHA58885 (Chinese)

Modicon M580, System Planning Guide for Complex NHA58892 (English), NHA58893 (French),
Topologies NHA58894 (German), NHA58895 (Italian), NHA58896
(Spanish), NHA58897 (Chjnese)

Modicon M580, Safety Manual QGH46982 (English), QGH46983 (French),

QGH46984 (German), QGH46985 (Italian),
QGH46986 (Spanish), QGH46987 (Chinese)

Modicon M340 for Ethernet, Communications Modules 31007131 (English), 31007132 (French), 31007133
and Processors, User Manual (German), 31007494 (Italian), 31007134 (Spanish),
31007493 (Chinese)

Premium and Atrium using EcoStruxure™ Control 35006216 (English), 35006217 (French), 35006218
Expert, Counter Modules, User Manual (German), 35013968 (Italian), 35006219 (Spanish),
35012200 (Chinese)

Premium and Atrium using EcoStruxure™ Control 35006242 (English), 35006243 (French), 35006244
Expert, Process Control, User Manual (German), 35014013 (Italian), 35006245 (Spanish),
35012198 (Chinese)

Communication Services and Architectures, Reference 35010500 (English), 35010501 (French), 35006176
Manual (German), 35013966 (Italian), 35006177 (Spanish),
35012196 (Chinese)

Premium and Atrium using EcoStruxure™ Control 35008155 (English), 35008156 (French), 35008157
Expert, Fipio Bus, Setup Manual (German), 35013953 (Italian), 35008158 (Spanish),
35013954 (Chinese)

Premium and Atrium using EcoStruxure™ Control 35006183 (English), 35006185 (French), 35006186
Expert, Fipway Network, User Manual (German), 35013955 (Italian), 35006187 (Spanish),
35013956 (Chinese)

Premium and Atrium using EcoStruxure™ Control 35006192 (English), 35006193 (French), 35006194
Expert, Ethernet Network Modules, User Manual (German), 31007214 (Italian), 35006195 (Spanish),
31007102 (Chinese)

Premium and Atrium using EcoStruxure™ Control 35006188 (English), 35006189 (French), 35006190
Expert, Modbus Plus Network, User Manual (German), 35013962 (Italian), 35006191 (Spanish),
35013963 (Chinese)

Communication Drivers, Installation Manual 35006152 (English), 35006153 (French), 35006154

(German), 35013950 (Italian), 35006155 (Spanish),
35012192 (Chinese)

Premium using EcoStruxure™ Control Expert, Motion 35010601 (English), 35010602 (French), 35010603
Function Blocks, Start-up Guide (German), 35010600 (Italian), 35010604 (Spanish),
35012309 (Chinese)

Modicon M340, Processors, Setup Manual 35012676 (English), 35012677 (French), 35013351
(German), 35013352 (Italian), 35013353 (Spanish),
35013354 (Chinese)

36 33003101.26
About the Book

Title of documentation Reference number

Modicon X80, Analog Input/Output Modules, User 35011978 (English), 35011979 (German), 35011980
Manual (French), 35011981 (Spanish), 35011982 (Italian),
35011983 (Chinese)

Modicon M340, CANopen, Setup Manual 35013944 (English), 35013945 (French), 35013946
(German), 35013948 (Italian), 35013947 (Spanish),
35013949 (Chinese)

Quantum using EcoStruxure™ Control Expert, 35010529 (English), 35010530 (French), 35010531
Hardware Reference Manual (German), 35013975 (Italian), 35010532 (Spanish),
35012184 (Chinese)

Quantum using EcoStruxure™ Control Expert, Change S1A48967 (English), S1A48968 (French), S1A48969
Configuration On The Fly, User Guide (German), S1A48970 (Italian), S1A48972 (Spanish),
S1A48976 (Chinese)

Momentum for EcoStruxure™ Control Expert, 171 CBU HRB44124 (English)

78090, 171 CBU 98090, 171 CBU 98091 Processors,
User Guide
EcoStruxure™ Control Expert, Standard, Block Library 33002519 (English), 33002520 (French), 33002521
(German), 33003678 (Italian), 33002522 (Spanish),
33003679 (Chinese)

EcoStruxure™ Control Expert, Diagnostics, Block 33002523 (English), 33002524 (French), 33002525
Library (German), 33003680 (Italian), 33002526 (Spanish),
33003681 (Chinese)

EcoStruxure™ Control Expert, Communication, Block 33002527 (English), 33002528 (French), 33002529
Library (German), 33003682 (Italian), 33002530 (Spanish),
33003683 (Chinese)

EcoStruxure™ Control Expert, I/O Management, Block 33002531 (English), 33002532 (French), 33002533
Library (German), 33003684 (Italian), 33002534 (Spanish),
33003685 (Chinese)

EcoStruxure™ Control Expert, System, Block Library 33002539 (English), 33002540 (French), 33002541
(German), 33003688 (Italian), 33002542 (Spanish),
33003689 (Chinese)

EcoStruxure™ Control Expert, UnityLL984, Block EIO0000000550 (English), EIO0000000807 (French),

Library EIO0000000808 (German), EIO0000000809 (Italian),
EIO0000000810 (Spanish), EIO0000000811
(Chinese)

System Time Stamping, User Guide EIO0000001217 (English), EIO0000001707 (French),

EIO0000001708 (German), EIO0000001710 (Italian),
EIO0000001709 (Spanish), EIO0000001711
(Chinese)

EcoStruxure™ Control Expert, Applicative Time EIO0000001268 (English), EIO0000001702 (French),

Stamping, User Guide EIO0000001703 (German), EIO0000001705 (Italian),
EIO0000001704 (Spanish), EIO0000001706
(Chinese)

You can download these technical publications, the present document and other technical
information from our website www.se.com/en/download/.

33003101.26 37
General
What’s in This Part
General Presentation of Control Expert......................................40
Programming Language Editors................................................49
Connecting a terminal to a PLC.................................................62
Global project management......................................................65
Project browser...................................................................... 155
Functional modules................................................................ 232
FDT Container....................................................................... 263
Type Library Manager ............................................................ 310

Subject of this Part

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

33003101.26 39
 General Presentation of Control Expert

General Presentation of Control Expert

What’s in This Chapter
Capabilities of Control Expert....................................................40
User Interface..........................................................................45

Overview
This chapter describes the general features of a project created using Control Expert.

Capabilities of Control Expert

Hardware Platforms
Control Expert supports the following hardware platforms:
• Modicon M340
• Modicon M580
• Quantum
• Momentum
• Premium
• Atrium

Programming Languages
Control Expert 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.

40 33003101.26
General Presentation of Control Expert

All these languages (except LL984) conform to IEC 61131-3.

Block Libraries
The blocks that are included in the delivery of Control Expert 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)
• Program Units which are assigned one of the defined tasks (available for Modicon
M580 and Modicon M340)
• 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)

Software Licenses
There is one Control Expert installation setup (.iso file) and the license determines the
version that can be launched.
The following software versions are available:
• Control Expert S
• Control Expert L
• Control Expert XL
• Control Expert XL with M580 Safety

33003101.26 41
 General Presentation of Control Expert

The M580 Safety CPUs are included in a Safety add-on available for Control Expert L and
XL.
Two types of licenses are available to activate Control Expert:
• Node-locked license for single use on a local PC.
• Floating license for multiple uses of an authorized number of PCs in a network
connected to the Enterprise License Server.
For detailed information on license activation and/or registration, refer to EcoStruxure™
Control Expert, Installation Manual.

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

Control Expert Control Expert Control Expert Control Expert Control Expert
S L L + Safety add- XL XL + Safety
on add-on
Programming languages

Function Block + + + + +
Diagram FBD

Ladder Diagram (LD) + + + + +

language

Instruction List IL + + +(2) + +(2)

Structured Text ST + + +(2) + +(2)

Sequential Language + + +(2) + +(2)

SFC
Ladder Logic 984 + + + + +
(LL984)

Libraries(1)

Standard library + + +(2) + +(2)

Control library + + +(2) + +(2)

Communication + + +(2) + +(2)

library

Diagnostics library + + +(2) + +(2)

I/O management + + +(2) + +(2)

library

System library + + +(2) + +(2)

42 33003101.26
General Presentation of Control Expert

Control Expert Control Expert Control Expert Control Expert Control Expert
S L L + Safety add- XL XL + Safety
on add-on
Motion control drive - + +(2) + +(2)
library

TCP Open library - optional optional(2) optional optional(2)

Obsolete library + + +(2) + +(2)

MFB library + + +(2) + +(2)

Safety library - - + - +

Memory card file + + +(2) + +(2)

management library

General information
Create and use data + + +(2) + +(2)
structures (DDTs)

Create and use + + + + +

Derived Function
Blocks (DFBs)

Project browser with + + + + +

structural and/or
functional view
Managing access + + + + +
rights

Operator screen + + + + +

Diagnostic viewer + + + + +

System diagnostics + + + + +

Project diagnostics + + +(2) + +(2)

Trending Tool + + + + +

Application converter PL7 converter PL7 converter PL7 converter PL7 converter PL7 converter

Concept Concept Concept Concept Concept

Converter Converter Converter Converter Converter

Partial
conversion
Managing multi- - - - - -
stations
Supported platforms

Modicon M340 All CPUs All CPUs All CPUs All CPUs All CPUs
Modicon M580 - BMEP5810•• BMEP5810•• BMEP5810•• BMEP5810••

33003101.26 43
 General Presentation of Control Expert

Control Expert Control Expert Control Expert Control Expert Control Expert
S L L + Safety add- XL XL + Safety
on add-on

BMEP5820•• BMEP5820•• BMEP5820•• BMEP5820••

BMEP5830•• BMEP5830•• BMEP5830•• BMEP5830••

BMEH582040 BMEH582040 BMEP5840•• BMEP5840••

BMEP582040S BMEP585040 BMEP585040

BMEH582040S BMEP586040 BMEP586040

BMEH582040 BMEH582040

BMEH584040 BMEH584040

BMEH586040 BMEH586040

BMEP582040S

BMEP584040S

BMEH582040S

BMEH584040S

BMEH586040S
Momentum 171CBU78090 171CBU78090 171CBU78090 171CBU78090 171CBU78090

171CBU98090 171CBU98090 171CBU98090 171CBU98090 171CBU98090

171CBU98091 171CBU98091 171CBU98091 171CBU98091 171CBU98091

Premium - All CPUs All CPUs All CPUs All CPUs
except: except:

P57 554M P57 554M

P57 5634M P57 5634M

P57 6634M P57 6634M

Quantum - 140CPU31110 140CPU31110 140CPU31110 140CPU31110

140CPU43412 140CPU43412 140CPU43412 140CPU43412

U/A* U/A* U/A U/A

140CPU53414 140CPU53414 140CPU53414 140CPU53414

U/A* U/A* U/A U/A

* Upgrade using * Upgrade using 140CPU65150 140CPU65150

OS Loader OS Loader
140CPU65160 140CPU65160

140CPU65260 140CPU65260

140CPU65860 140CPU65860

140CPU67060 140CPU67060

44 33003101.26
General Presentation of Control Expert

Control Expert Control Expert Control Expert Control Expert Control Expert
S L L + Safety add- XL XL + Safety
on add-on

140CPU67160 140CPU67160

140CPU67260 140CPU67260

140CPU67261 140CPU67261

140CPU67861 140CPU67861
Atrium - All CPUs All CPUs All CPUs All CPUs
Simulator + + + + +

Openness

Hyperlinks + + + + +

Control Expert Server + + + + +

(for OFS, UAG)

Software components contained in the software package

Documentation as + + + + +
context help and PDF

OS Loader tool + HW + + + + +
firmware
+ Available

- Not available

(1) Availability of the blocks depends on the hardware platforms.

(2) Available on all PLC except platforms M580 Safety.

Naming Convention
In the rest of this document, "Control Expert" is used as general term for "Control Expert S",
"Control Expert L", and "Control Expert XL", with or without Safety add-on.

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

33003101.26 45
 General Presentation of Control Expert

User interface:

Legend:

Number Description

1 Menu bar, page 1821

2 Toolbar, page 1826

3 Project Browser, page 155

4 Editor window (programming language editors, data editor, etc.)

46 33003101.26
General Presentation of Control Expert

Number Description

5 Register tabs for direct access to the editor window

6 Information window, page 1832 (provides information about errors which have occurred, signal
tracking, import functions, etc.)

7 Status bar, page 1834

33003101.26 47
48 33003101.26
Programming Language Editors

Programming Language Editors

What’s in This Chapter
Function Block Diagram FBD ....................................................49
Ladder Diagram (LD) Language................................................52
General Information about SFC Sequence Language .................54
Instruction List IL......................................................................58
Structured Text ST ...................................................................59

Overview
This chapter describes the different programming languages provided by Control Expert.

Function Block Diagram FBD

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

33003101.26 49
 Programming Language Editors

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

50 33003101.26
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.26 51
 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)

52 33003101.26
Programming Language Editors

• 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

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-63 columns and 17-3998 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

33003101.26 53
 Programming Language Editors

• Different zoom factors

• Tracking of FFB links
• Optimizing the link routes of FFB links
• Display of inspection windows

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.

54 33003101.26
Programming Language Editors

Representation
Representation of an SFC section:

Objects
An SFC section provides the following objects for creating a program:

33003101.26 55
 Programming Language Editors

• 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 64
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

56 33003101.26
Programming Language Editors

• Tracking of links
• Optimization of link routes

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.26 57
 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:

58 33003101.26
Programming Language Editors

• 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

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:

33003101.26 59
 Programming Language Editors

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.

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

60 33003101.26
33003101.26 61
 Connecting a terminal to a PLC

Connecting a terminal to a PLC

What’s in This Chapter
Methodology for connecting from a PC to a PLC.........................62

Subject of this Chapter

This chapter describes how to connect a PC 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 Control
Expert 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)

62 33003101.26
Connecting a terminal to a PLC

Platform Produce Product Reference

USB cable BMX XCA USBH •••(2)

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, page 62.

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, page 87 to which you want to connect and the type of link, page 92
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.

33003101.26 63
 Connecting a terminal to a PLC

64 33003101.26
Global project management

Global project management

What’s in This Chapter
Access security management ...................................................65
Project management ................................................................66

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.

Access security management

Subject of this Section
This section introduces the tools used to manage security for a project.

Access security management

Security Editor Tool
Refer to EcoStruxure™ Control Expert, Security Editor, Operation Guide to manage security
for a project.

33003101.26 65
 Global project management

Project management
Subject of this Section
This section introduces the tools used for project management.

Access to Control Expert Software

At a Glance
It is possible to launch several instances of Control Expert 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 Control Expert icon calls up a login dialog box which is
used to access Control Expert.
• If security is inactive, you have direct access to Control Expert.

Security Inactive or Active in No Login Mode

If security is inactive, execute the following commands to launch an instance of Control
Expert:

66 33003101.26
Global project management

Step Action

1 Click Start > Programs.

2 Select the group EcoStruxure Control Expert.

Result: A list appears

• Language selection
• OS Loader
• PLC Simulator
• Readme
• Registration Tool
• Types library update
• Control Expert

3 From the list, select Control Expert.

Result: Control Expert is launched in the selected language.

Special case:

If you have not yet activated the software, a message warns you of the number of days of use left,
and asks you whether you want to activate. For more information, refer to EcoStruxure™ Control
Expert, Installation Manual.

Other Cases
When security is active, page 65, execute the following commands to launch an instance of
Control Expert:

33003101.26 67
 Global project management

Step Action

1 Activate the Control Expert 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.

NOTE: If you click Ignore Control Expert starts with access setting of user default defined in
Security Editor Policies.

Services in Offline Mode

At a Glance
The following operations can be carried out when accessing Control Expert 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:

68 33003101.26
Global project management

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.

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.

33003101.26 69
 Global project management

Open Dialog
Open project dialog

70 33003101.26
Global project management

Element Description

Look in The upper part of this dialog displays a standard Windows File Open
dialog.
File name

Files of type

Opening a legacy LL984 project Please refer to Importing an LL984 Application, page 102.

Open Options

Open the project in read-only Opens the project in read-only mode.

mode
Open import File with Wizard Select this check box to use the import, page 1677 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, page 311 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 Select this option to update the project with the latest Libset version.
available
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.

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

33003101.26 71
 Global project management

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 Control Expert 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 Control Expert 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.

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.

72 33003101.26
Global project management

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 Control Expert
software.
• 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 Control Expert 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.

Converting an Existing PL7 or Concept Project

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

33003101.26 73
 Global project management

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 EcoStruxure™
Control Expert, PL7 Application Converter, User Manual),
• *.ASC, to launch the conversion procedure for a Concept application (see EcoStruxure™
Control Expert, 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
Control Expert.

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.

74 33003101.26
Global project management

NOTE: Archiving is only possible after a Rebuild all project with the Upload
information, page 548 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.

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:

33003101.26 75
 Global project management

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.

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.

76 33003101.26
Global project management

NOTE: Closing a project triggers saving the current context in the file <Project_name>.
ZTX, page 71.

Exiting Control Expert

To exit Control Expert, 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.

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, page 592.

Equal or Different Modes

On connection, the data in the PLC and the terminal is compared, page 548:
• if the data is identical, this determines an equal online mode, page 86,
• if the data is different, this determines a different online mode, page 86.

33003101.26 77
 Global project management

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.

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

78 33003101.26
Global project management

Function Description

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 (this
Values 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.

Allowed Online Modifications

Overview
The following pages describe modifications that are allowed when Control Expert 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 Control Expert, 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 Control Expert 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 Control Expert.
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, page 77: state is ‘monitoring’ and no online modification is allowed,

33003101.26 79
 Global project management

• programming, page 77.

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, Control Expert 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 ‘*’.

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.

80 33003101.26
Global project management

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
Unity Pro is the former name of Control Expert for version 13.1 or earlier.
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.

Modify the Configuration

For Modicon M340, 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.

33003101.26 81
 Global project management

For Modicon Quantum system PLCs, it is possible to add or delete a selection of modules
and change the parameters of an existing module in STOP and RUN mode. For more
information refer to Modicon Quantum, Change Configuration on the Fly, User Guide.
For Modicon M580 PLCs when the option CCTOF is selected, it is possible to add or delete
a selection of modules and change the parameters of an existing module in STOP and RUN
mode. For more information refer to Modicon M580, Change Configuration on the Fly, User
Guide.

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, Yes Yes No
Sections

82 33003101.26
Global project management

Type of Modification Impacts Only Upload Allowed in Online Requires to Build the
Information Mode (RUN/STOP) Application in Offline
Mode
Comment of Station, Yes Yes No
Configuration, Programs,
Sections
Documentation Summary Yes Yes No

Animation Table Yes Yes No

Integrated Operator Screens Yes Yes No

Functional View Yes Yes No

Security Information: No Yes No
Passwords, Protection
Attributes,...

Switch Simulator <-> Real No No Yes

Target

Import/Export Project No Yes No

Program

Program elements (Sections, No Yes No

Program Units): Add,
Change Execution Order

Modify the Code of a Section Yes(1) Yes No

(Task Section, SR,
Transition, Action, DFB
Sections)

Modify the Code of EVT No Yes(2) Yes

Sections
Modify the Code of SFC No Yes No(1)
Chart
Configuration/
Communication
Premium Configuration: Add/ No No Yes
Delete a Module
Premium Configuration: No Yes No
Change Module Parameters

Quantum Configuration: Add/ No Yes No

Delete a Module
Quantum Configuration: No Yes No
Change Module Parameters

Changing Memory Sizes in No No Yes

Configuration Screen

33003101.26 83
 Global project management

Type of Modification Impacts Only Upload Allowed in Online Requires to Build the
Information Mode (RUN/STOP) Application in Offline
Mode
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 No Yes No

Used Variable
Initial Value of an Used No Yes No
Variable
Comment of an Used Yes Yes No
Variable
Create, Remove or Modify No Yes No
Unused Variables (EDT,
DDT)

Create, Remove or Modify No Yes No

Unused Variables (FB)

Program Unit Variables

(Used Even in Animation
Table)

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 No Yes No

Used Variable
Initial Value of an Used No Yes No
Variable
Comment of an Used Yes Yes No
Variable
Effective Parameter of an Yes Yes No
Used Variable
Create, Remove or Modify No Yes No
Unused Variables (EDT,
DDT)

Create, Remove or Modify No Yes No

Unused Variables (FB)

Used DFB
Type Name of Used DFB No No Yes

84 33003101.26
Global project management

Type of Modification Impacts Only Upload Allowed in Online Requires to Build the
Information Mode (RUN/STOP) Application in Offline
Mode
All Comments Yes Yes No
Add a Parameter No No Yes
Add a Public or Private No Yes No
Variable
Delete or Change Unused No Yes No
Private Variable
Initial Value of Parameters No Yes No
and Variables
Other Attributes of No No Yes
Parameters and 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.

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.

33003101.26 85
 Global project management

Equal online mode

On connection to the PLC, Control Expert 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, Control Expert 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 , page 87 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.

Disconnection procedure
You must execute the following actions to disconnect:

86 33003101.26
Global project management

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, page 95.

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, page 92. For Ethway
drivers, refer to the following note.

4 If you wish, modify:

• the communication parameters, page 95 using the Communication Parameters buttons
in the PLC and Simulator group boxes
• the connection bandwidths, page 97 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.26 87
 Global 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 page 95.

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 page 96.

Bandwidth Click this button to display the Online Mode Services Bandwidth dialogue,
page 97.

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 rate
adaptation at the end (e.g., Modems).
of download

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

88 33003101.26
Global project management

Platform Support Address syntax

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.

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"

33003101.26 89
 Global project management

Platform Support Address syntax

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.
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.

90 33003101.26
Global project management

Platform Support Address syntax

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.

Accessing PLCs Behind a Router

When you need to communicate to several PLCs behind routers, configure a network
address translation table in Control Expert 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:

33003101.26 91
 Global project management

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:
• Control Expert 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.

Overview of Types of Connection Possible With

Schneider PLCs
At a Glance
Control Expert 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.

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

92 33003101.26
Global project management

Type of Connection M340 M580 Premium and Quantum

Atrium
USB All processors All processors On processors: On processors:
• TSX P57 4634 • 140 CPU 651
50
• TSX P57 554
• 140 CPU 651
• TSX P57 5634
60
• TSX P57 6634
• 140 CPU 651
60S
• 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
Modbus connection
• BMX P34 1000
which can be used
• BMX P34 2000 by Control Expert.
• BMX P34 2010
• BMX P34
20102
• BMX P34 2020
XIP (2) - - Via the following -
modules:
• TSX ETY 110
• TSX ETY 4103
• TSX ETY 5103
• TSX ETY
PORT
• Ethernet
channel of TSX
P57 4634

33003101.26 93
 Global project management

Type of Connection M340 M580 Premium and Quantum

Atrium
• 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
• BMX P34 2030 • TSX P57 5634 50

• BMX P34 • TSX P57 6634 • 140 CPU 651

60
20302 Via the following
• 140 CPU 651
Via the following modules:
modules: 60S
• TSX ETY 4103
• BMX NOE
(3) • 140 CPU 652
0100 60
• TSX ETY 5103
(3)
• BMX NOE 0110 • 140 CPU 658
• TSX ETY 60
PORT (3) Via the following
modules:
• 140 NOE 211
x0
• 140 NOE 251
x0
• 140 NOE 771
00
• 140 NOE 771
01
• 140 NOE 771
10
• 140 NOE 771
11
• 140 NOE 771
20
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
Control Expert is

94 33003101.26
Global project management

Type of Connection M340 M580 Premium and Quantum

Atrium
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 Control
Expert 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 Control Expert 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, page 77 cannot be accessed via a Modbus Plus network.

Accessing communication parameters

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

33003101.26 95
 Global project management

Step Action

1 Access the Set Address screen, page 87.

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.

Procedure for accessing simulator parameters

You must perform the following actions to access the communication parameters of the
simulator: (see EcoStruxure™ Control Expert, Program Languages and Structure, Reference
Manual)

96 33003101.26
Global project management

Step Action

1 Access the Set Address screen, page 87.

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 Control Expert 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.
• PLC Screen (PLC debug screen): the higher the percentage allocated, the higher the
frequency with which the PLC and application information will be scanned.

33003101.26 97
 Global project management

• 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, page 87.

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.

98 33003101.26
Global 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.
• SourceSafeSignature: an SHA256 algorithmic fingerprint of the safe application.

Procedure
Perform the following actions to launch project comparison:

33003101.26 99
 Global project management

Step Action

1
Activate the PLC > Compare command, which displays the screen below.

NOTE: Both the project and the safe application SourceSafeSignature values are compared. The
combination of the two comparisons is displayed in an icon placed between the two
SourceSafeSignature values:
• The icon in the graphic, above, indicates both the Projects and the SourceSafeSignatures are
DIFFERENT.

• indicates both the Projects and the SourceSafeSignatures are EQUAL.

• indicates the Projects are DIFFERENT, but the SourceSafeSignatures are EQUAL.

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).

100 33003101.26
Global project management

Conversion of Legacy Applications/Projects

Introduction
There are 2 possibilities to convert legacy applications to Control Expert.
• Global conversion provides to convert a legacy application (PL7, Concept) to Control
Expert 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 Control Expert, 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 Control Expert via File > Open.
The respective converter (PL7 Converter, Concept Converter) automatically generates a
Control Expert application.
For detailed information on the converters, please refer to EcoStruxure™ Control Expert,
PL7 Application Converter, User Manual or EcoStruxure™ Control Expert, Concept
Application Converter, User Manual.
• Global conversion for Premium and Quantum contains also a hardware configuration.
• Applications with PLCs which do not have a direct equivalent in Control Expert
(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, page
102.
• 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.26 101
 Global project management

Partial Conversion
To convert a legacy application partially to Control Expert, use the conversion wizard.
You can launch the conversion wizard in Control Expert 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 Control Expert
• 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 chapter Conversion Wizard, page 1733.

Importing an LL984 Application

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

102 33003101.26
Global project management

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, page 111 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, page 70.
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 Control Expert, 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
EcoStruxure™ Control Expert, LL984 Editor, Reference Manual).

33003101.26 103
 Global 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”.

Full Topological This check box is only used to convert applications to Modicon M340 PLCs.

104 33003101.26
Global project management

Element Description

Symbols

Original Select this option to use the original variable names of the legacy application in
your new Control Expert 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 Modicon Momentum under Control Expert 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, page 1166.

33003101.26 105
 Global project management

Element Description

Shift 984 Remote This additional option appears if the legacy application CPU family is a 984 family.

If selected, a Quantum local rack is added to the application and all drop numbers
are increased by one until an unused drop number is reached, keeping the old
984 rack as the first remote rack (drop number 2) without the old CPU.

If the option is not selected, conversion attempts to translate the local rack and its
modules to Quantum, as far as possible. A common situation encountered is that
984 local drops often contain more racks than allowed with Quantum.

Long Comments are in This additional dialog box displays the path where the long comments are stored if
project and in directory the legacy application contains long comments.

This path is identical to the path where the legacy application is stored plus one
additional directory for the long comments.

Long comments appear twice in the conversion:

• Inside the internal project database of the data editor.
• As text files in the additional application path directory for long comments.
To back up all information of the application, only the files in the additional
application path directory are to be saved.

To achieve consistency between data editor and text files, comment in both places
must be edited together.

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)

106 33003101.26
Global project management

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.
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.

33003101.26 107
 Global project management

• 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.

108 33003101.26
Global project management

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

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

33003101.26 109
 Global project management

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 EcoStruxure™ Control Expert, LL984 Editor,
Reference Manual).

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.

110 33003101.26
Global project management

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 Control Expert user interface.
Double-click such a message in the Output Window to access the respective dialog in your
application.
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 EcoStruxure™ Control Expert, LL984
Editor, Reference Manual).
• 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 EcoStruxure™ Control Expert, LL984
Editor, Reference Manual).
• The import of a legacy application that contains duplicated identifiers is aborted. For
details please refer to Duplicated Identifiers (see EcoStruxure™ Control Expert, LL984
Editor, Reference Manual).
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, page 1218 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.

33003101.26 111
 Global 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 Control Expert project
NOTE:
When you manage a PLC (controller) as part of a system project (Topology Manager),
you cannot transfer the project from the PLC to the terminal by using Control Expert
editor; the corresponding commands are disabled.
• For controllers of the M340, MC80, and Momentum platforms, transfer (upload) the
project from the controller to the system project by using the Topology Manager.
• For controllers of the M580, Quantum, and Premium platforms, transfer the project
from the PLC to the terminal by using Control Expert Classic.

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, page 87.

2 Change to online mode, page 85.

3 Activate the PLC > Transfer Project to PLC command, which displays the corresponding screen,
page 114.

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.

112 33003101.26
Global project management

Step Action

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.

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, page 87.

2 Change to online mode, page 85.

3 Activate the PLC > Transfer Project from PLC command to display the corresponding screen,
page 115.

4 The transfer progress is displayed on screen. At any moment, you can interrupt the transfer by
using the Esc key.

33003101.26 113
 Global project management

Terminal to PLC transfer screen

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

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
• Last Build (date and time the executable was last generated)
• SourceSafeSignature: an SHA256 algorithmic fingerprint of the safe
application (for safety PLCs).
NOTE: An icon located between the SourceSafeSignature entries in the PC
Project field and the Overwritten PLC Project field indicates a comparison
between the two values:

• indicates the values are DIFFERENT.

• indicates the values are EQUAL.

• No icon indicates there is no application in the PLC.

Overwritten PLC Identification field for the project in the embedded in the PL. This project will be
Project overwritten or updated by the transfer:
• Name
• Version
• Last Build (date and time the executable was last generated)

114 33003101.26
Global project management

Parameter Description

• SourceSafeSignature: an SHA256 algorithmic fingerprint of the safe

application (for safety PLCs).

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:

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 Transfer command: the project is transferred.

PLC
Cancel Command used to cancel the transfer.

33003101.26 115
 Global project management

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 Control Expert also triggers display of a message.

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, page 548 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.

116 33003101.26
Global project management

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, page 548 select: Tools > Project Settings > PLC
Embedded data

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,
page 588 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.

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 EcoStruxure™ Control
Expert, Program Languages and Structure, Reference Manual)
• Init initializes the project.

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

33003101.26 117
 Global project management

Step Action

1 Use the PLC > Set address command to define the target PLC that you wish to control, page
87.
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.

Project Backup Management for Modicon M340

At a Glance
Automatic and manual accesses are carried out between the Schneider BMX RMS •••••
memory card and Control Expert 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 Control Expert command PLC > Project Backup... > Backup
Restore.

118 33003101.26
Global project management

NOTE:
• When you insert the memory card in run or stop mode, power cycle to restore the
project on 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.

WARNING
UNEXPECTED BEHAVIOUR OF APPLICATION
Ensure that the right user application is contained in the memory card before inserting it
into the PLC.
Failure to follow these instructions can result in death, serious injury, or equipment
damage.

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.

33003101.26 119
 Global project management

Memory Card State and Diagnostic

Control Expert and the PLC front panel display the status of the memory card:

Display on Icon/LED Description

State
Status bar at Project on memory card is different from PLC project.
bottom of Control
Expert
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.

Project backup for Premium

At a Glance
Certain PLCs Premium allow you to save the project program contained in the executable
zone (see EcoStruxure™ Control Expert, 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.
Control Expert 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.

120 33003101.26
Global project management

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.

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).

33003101.26 121
 Global project management

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.

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
EcoStruxure™ Control Expert, 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.

122 33003101.26
Global project management

• DTX:
◦ 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 DDT 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, page 127 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.
NOTE: The data transfer function can be used for migrating from different PLC range.
You can save M340 or Premium data to a *.DTX file and restore to M580 PLC the *.DTX
file.

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.

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.
NOTE: On forced bits, value is saved but the forcing status (F) is not saved.

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:

33003101.26 123
 Global project management

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.
• Control Expert is running and is connected to the PLC.
• The Application built in Control Expert is equal to those in the PLC.
• The Application in Control Expert 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, page 125.

3 Using the check boxes, 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.

124 33003101.26
Global 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.

Procedure for Restoring Data to PLC

If forced bits are detected in the PLC, forcing status (F) and value will not be updated in the
PLC.

33003101.26 125
 Global project management

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.
NOTE: It is strongly recommended to do the transfer with the PLC in STOP mode.
• Control Expert is running and is connected to the PLC.
• The Application built in Control Expert may be different than those in the PLC.
• The Application in Control Expert is built state.

2 Activate the PLC > Restore Data from File to PLC command.
If the PLC is in RUN status, a message is displayed allowing to perform the transfer while the PLC
is still operating (Ok) or to cancel the transfer.

If forced bits are detected in the PLC, a message is displayed allowing to perform the transfer (Ok)
or to cancel the transfer.

126 33003101.26
Global project management

Step Action

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

3 Select the file to be restored to the PLC.

4 Confirm with Open.

5 A confirmation message is asking you if you want to proceed with the transfer.

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, Control Expert analyses the content of the file to verify the
compatibility with variables of the PLC application.
The following tables present 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.

33003101.26 127
 Global project management

CAUTION
UNEXPECTED BEHAVIOR 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 cannot 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 cannot be
restored on PLC version 2.0 or < 2.0.

Simple Variable Compatibilities

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

Cas- Data File Contents PLC Application Restore Behavior Control Expert Message
e 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
into Var3-3 (name PERFORMED due to technical longer 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.

128 33003101.26
Global project management

Cas- Data File Contents PLC Application Restore Behavior Control Expert Message
e Contents
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 TYPE2) but value may not
not compatible with Var5 is converted into a different be compatible.
target type. type (the target) and its value is
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.

Structured Variable Compatibilities

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

Cas- Data File Contents PLC Application Restore Behavior Control Expert Message
e Contents
DDT Types

7 Var7 is a DDT type. Var7 was changed to The restore CANNOT BE Var7: type of the variable is
a simple type. PERFORMED because type is changed (from TYPE1 to
not compatible. TYPE2). But types are not
compatible.

8 Var8 is a simple type. Var8 was changed to The restore CANNOT BE Var8: type of the variable is
a DDT type. PERFORMED because type is changed (from TYPE1 to
not compatible. TYPE2). But types are not
compatible.

9 Var9 is a DDT type. Var9 is changed to The restore CANNOT BE Var9: type of the variable is
another DDT type. PERFORMED because type is changed (from TYPE1 to
not compatible. TYPE2). But types are not
compatible.

10 Var10 is a DDT type. The DDT type has Make the mapping of the field Var10.SubField1: … (see
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.

33003101.26 129
 Global project management

Cas- Data File Contents PLC Application Restore Behavior Control Expert Message
e Contents
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
the same type, but PERFORMED because starting ARRAY… array (range #2)
starting index is indexes must be identical. has changed. Cannot
lower or a different restore.
type. Ending index is
the same
14 Var14 is an array. Var14 is an array of The restore CANNOT BE Var14: high bound of
the same type, but PERFORMED because starting ARRAY… array (range #2)
starting index is indexes must be identical. has changed. Cannot
higher or a different restore.
type. Ending index is
the same
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
the lower and upper indexes must be identical. changed. 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
has changed 16.

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 UINT or UDINT variable can be changed into an INT variable if the value is
compatible.
REAL, STRING, TOD, TIME, DATE, and DT are not compatible types.
The following table presents the compatibility between the elementary types:

130 33003101.26
Global project management

TOD

TIME

DATE
INT

UDINT

DWORD

REAL

DT
BOOL

EBOOL

BYTE

UINT

WORD

DINT

STRING
BOOL YES NO NO NO NO NO NO NO NO NO NO NO NO NO
EBOOL YES NO PDL PDL NO PDL PDL NO NO NO NO NO NO NO
BYTE NO NO YES YES YES YES YES YES NO NO NO NO NO NO
INT NO NO PDL PDL YES YES YES YES NO NO NO NO NO NO
UINT NO NO PDL PDL YES YES YES YES NO NO NO NO NO NO

WORD NO NO PDL YES YES YES YES YES NO NO NO NO NO NO

DINT NO NO PDL PDL PDL PDL PDL YES NO NO NO NO NO NO
UDINT NO NO PDL PDL PDL PDL PDL YES NO NO NO NO NO NO
DWORD NO NO 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.

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

Cas- Data File Contents PLC Application Restore Behavior Control Expert Message
e Contents
1 Map1 is unlocated. Map1 is located on % Value of the data file for Map1 is Map1: restored at %
MW100. set to %MW100. MW100
%MW100 is used.
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.

33003101.26 131
 Global project management

Cas- Data File Contents PLC Application Restore Behavior Control Expert Message
e Contents

%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 unlocated Map5 is located on % Restore CANNOT BE Map5: value at address %

but in an area not MW100. PERFORMED because the MW100 is not available.
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).

Restoration of FB Instances and Other Variables

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

Type of Entity Control Expert 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.

132 33003101.26
Global project management

Restoration of Forced Variables

NOTE: If forced bits are detected in the PLC before performing the restore data, forcing
status (F) and value are not updated in the PLC after the restore data is performed.
The following table presents the rules followed for restoring forced variables:

Variable Value when the save data Value before performing the Value in the application after
from PLC to file is restore data from file to PLC the restore data is
performed performed

Located 0 1 0
Located 0 forced to 1 forced to 1
Unlocated 0 1 0
Unlocated 0 forced to 1 forced to 1

Located 1 0 1
Located forced to 1 0 1(1)

Unlocated 1 0 1
Unlocated forced to 1 0 1(1)

Located 1 forced to 0 forced to 0

Located forced to 1 0 1(1)

Unlocated 1 forced to 0 forced to 0

Unlocated forced to 1 0 1(1)

Located forced to 0 1 0(1)

Located forced to 1 forced to 0 forced to 0

Unlocated forced to 0 1 0(1)

Unlocated forced to 1 forced to 0 forced to 0

(1) The restored value is not forced.

33003101.26 133
 Global project management

Transferring Current Values

At a Glance
The functions below apply to the following variables:
• Located and unlocated variables
• Public and Privates variables of DFBs

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.
NOTE: to be taken in account in the code a build change is needed.
NOTE: when disconnecting the PLC from Control Expert, to update the STU file with the
same values as the PLC, you have to answer Yes, confirm modification, backup the PLC
project, connect the PLC again, make a build changes and save the STU file.

Memory usage
At a Glance
The memory usage function is used to view:

134 33003101.26
Global project management

• the physical distribution of the PLC memory (see EcoStruxure™ Control Expert,
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.26 135
 Global project management

Memory usage screen Modicon M580

The memory usage screen is shown below:

136 33003101.26
Global project management

Memory usage screen Modicon M340

The memory usage screen is shown below:

33003101.26 137
 Global 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.

Description of the parameters

The following information fields are available:

138 33003101.26
Global project management

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 (available for the Hot Standby CPU BMEP586040).

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
Cartridge B cards. 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, page 145.
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.26 139
 Global project management

Data Memory Protection

Introduction
The data memory protection contributes to the protection of data from a modification request
in monitoring mode.
The data memory protection is effective:
• off-line, or
• in monitoring mode, or
• in programming mode when project status is DIFFERENT.
NOTE: Modification of a variable with the reinforced protection is only possible when
Control Expert is connected in programming mode and project status is EQUAL.
A variable with the reinforced protection can only be modified by the program. Any
modification of a variable with the reinforced protection in monitoring mode via Control
Expert language editor, animation table and so on is not possible. This is the same behavior
for external tools (HMI, SCADA, …).
NOTE: The data memory protection settings can only be modified off-line. Online
modification is not effective.
The data protection applies to the following data:
• Located data
◦ A range of %M and %MW
◦ System data %S and %SW
◦ Input / output data
• Unlocated data
◦ Elementary unlocated data
◦ Structured unlocated data
◦ Safety unlocated data

NOTICE
COMMUNICATION LIMITATION
Do not activate the data protection function on a variable or range if it needs to be written
by means other than the program.
Failure to follow these instructions can result in equipment damage.

140 33003101.26
Global project management

CPU Firmware Limitation

The data memory protection feature is supported by:
• M580 CPU with OS version V3.20 or later
• M340 CPU with OS version V3.30 or later
NOTE: Replacing a CPU to an earlier version than respectively V3.20 for M580 and
V3.30 for M340 is only possible if the current project setting Data memory protect is not
activated.

Protection Activation
Before any action on the data memory protection, you must activate this feature in your
project settings.
In the Control Expert main window, click Tools > Project Setting > PLC embedded data.
Then select the Data memory protect box and click Apply.

Protection of Located Data

The data protection function applies to the following located data:
• A range of %M and %MW(1)
• System data %S and %SW
• Input / output data:
◦ Local I/O objects (LIO)
◦ Remote I/O objects (EIO)
◦ Distributed I/O objects (DIO): with a topological vision or with a DDT/DDDT vision
(1) Array variables which are mapped on a %MW range must be entirely inside or entirely
outside of the %MW range with the reinforced protection.
The data memory protection function is enabled in the CPU configuration window: Project >
Configuration > PLC Bus > CPU.
NOTE: The current project setting Data memory protect must be activated.
For the procedure of the located data protection enforcement, please refer to Protecting
Located Data, page 1351.

33003101.26 141
 Global project management

Mapping Address Protection

The properties of a located variable have priority on the properties of an unlocated variable.
Thus, the unlocated variable that is mapped on a located address, automatically takes the
protection of this address. The protection of this unlocated variable is reinforced the same
way as that of the located variable to which it is mapped.
Depending on the type of the located variable to which the unlocated variable is mapped,
the following protection enforcement of the mapping address is applied:
• On %MW/%M flat: the mapping address is not modifiable.
The attribute with the reinforced protection depends on the %MWi/%M protect
configuration
• On %SW/%S: the mapping address is not modifiable.
The attribute with the reinforced protection depends on the %SWi/%Si protect
configuration
• On a topological object: the mapping address is not modifiable.
The attribute with the reinforced protection depends on the I/O protect configuration
This is an automatic reinforced protection which cannot be modified in the Data Editor
window.

Data Protect Attribute

The Data Protect attribute is used to reinforce protection of an unlocated data in the Data
Editor window.
This attribute is enabled if:
• The variable is not mapped to any located address; and
• The variable is not managed; and
• The variable is not a subfield of a structure (DDT, array EFB instance, DFB instance);
and
• The variable is not a Device DDT; and
• The variable is not a constant
In all other cases the Data Protect attribute is disabled.

Protection of Unlocated Data

General Description
The data protection function applies to the following unlocated data:

142 33003101.26
Global project management

• Elementary
• Structured
• Safety
The unlocated data memory protection function is enabled in the Data Editor window. By
default, unlocated data are not protected.
NOTE: The current project setting Data memory protect must be activated.
The following particular cases must be considered when reinforcing protection of unlocated
data:
• An alias variable takes the same protection as the aliased variable
• A reference variable has always the reinforced protection; it is not affected by the
protection of the referenced variable
• The data protection can also be applied to DDT, Device DDT and IODDT data; and it is
enabled in the I/O protection check box in the CPU configuration window
The data memory protection function is also available for the Program Unit data:
• Input data:
◦ The data memory protection is applied to the input data if there is no effective
parameter on it
◦ Input data becomes “Read” when an effective parameter is set
• Output data:
◦ The data memory protection is not applied to the output data
◦ Output data becomes “Read” when an effective parameter is set
• Input/output data takes the protection of its effective parameter
Protecting Elementary Unlocated Data
The protection of unlocated elementary data can be reinforced individually. The required
modifications are done respectively for each element, one by one.
Protecting Structured Unlocated Data
The protection of structures of unlocated data can be reinforced globally. The required
modification is done once for the entire structure and applies to all its elements (all subfields
except subfields which are read-only by intrinsic access right).
The data protection function applies to the following structures of unlocated data:
• DDT
• Device DDT
• IODDT
• Array
• EFB instance

33003101.26 143
 Global project management

• DFB instance
NOTE: The protection enforcement of DDT, Device DDT and IODDT unlocated data can
be enabled in the I/O protection check box of the CPU configuration window.
Protecting Safety Unlocated Data
In safety applications, the data protection function applies to the following unlocated data:
• Global variables
• Process resource data:
◦ Input variables (with or without an effective parameter)
◦ Output variables (with or without an effective parameter)
◦ Private variables)
◦ FB Instances
◦ DDT and device DDT
• Safe resource data:
◦ Input variables (with or without an effective parameter)
◦ Output variables (with or without an effective parameter)
◦ Private variables)
◦ Safe FB Instances
◦ Safe DDT and device DDT

Procedure of Reinforcing Protection of Unlocated Data

Follow the procedure below to define unlocated data for which you need to reinforce the
protection:

Step Action

1 In the Control Expert main window, activate the data memory protection feature: click Tools > Project
Setting > PLC embedded data.

Then select the Data memory protect box and click Apply.

2 In the Control Expert Project Browser, double-click Variables & FB Instances to open the Data
Editor window, or click Tools > Data Editor in the Control Expert toolbar.

3 In the Data Protect column, select the boxes corresponding to data for which you need to reinforce
the protection.
NOTE: When you select the Data Editor attribute of a structured unlocated variable, this action
applies to all the subfields of the selected structure.

144 33003101.26
Global project management

NOTE: The unlocated variable that is mapped on a located address automatically takes
the protection of this address. Thus, the protection of this unlocated variable becomes
reinforced the same way as that of the located variable to which it is mapped.

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,
page 138 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.

33003101.26 145
 Global 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 Memory
is, is,
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.

146 33003101.26
Global 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 Memory
is, is,
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.

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 SD-card
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 Control Expert commands, page 118 PLC > Project Backup... > ....
• by programming with the Memory Card File Management EFBs (See Memory Card File
Management in the System library)
• with an FTP, page 148 client (for processors with an Ethernet connection) to manage
files on the memory card

33003101.26 147
 Global project management

Memory Card in an SD-card Drive or Reader

When the memory card is inserted into an SD-card 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 SD-card drive or reader, install the
Reliance driver first. This driver is available on the Automation Device Maintenance CD-
ROM.

Tree Structure of Files on the Memory Card

When the memory card is used in an SD-card 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 EcoStruxure™ Control Expert, System, Block Library)
• Firmware, which includes all files used by the Automation Device Maintenance software
• 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.

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

148 33003101.26
Global project management

NOTE: Downloading write-protected files to the memory card can prevent the
Automation Device Maintenance software 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.

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.26 149
 Global project management

Project Management with DTMs

At a Glance
The Control Expert Project and Archive files can be saved and opened even if DTMs are not
installed in the DTM Hardware Catalog, page 266.
Building a complete Control Expert project requires that all DTMs in the project are installed.
A DTM audit tool provides a comparison between the version of the project DTMs and the
PC DTMs.

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, page 290 must be used
to check for uninstalled 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.

150 33003101.26
Global project management

DTM Audit Tool

A tool is provided to have a clear vision of the DTM versions embedded in a project and the
versions installed on the PC. Depending on the DTM versions compatibility, the tool informs
if the project can be opened and built.
File format compatible with the DTM audit tool:
• *.stu project file
• *.sta archive file
• *.zef import/export file
Launching the DTM audit tool:
• Start > Programs > EcoStruxure Control Expert > DTMAuditTool. The tool can be
launch even if Control Expert is not running.
• In Control Expert, select Tools > DTMAuditTool.
Opening a project (*.stu or *.sta) or an inport/export file (*.zef) in Control Expert: the DTM
audit tool analyzes the DTM versions compatibility.
• If they are compatible, the tool does not display any message.
• If one or more DTM versions are not compatible, the tool displays a table with the DTM
versions and compatibilities.
Then you can choose to cancel the project opening or continue, being informed that
DTM versions are not compatible and that the project cannot be built.
When DTMs are available on Schneider Electric DTM Catalog Server, a link is available to
download and install the required DTM versions. It is then possible to download and install
the DTM from this link.
After download and installation of the DTM, the Control Expert DTM catalog must be
updated following one of these procedures:
• close and open again Control Expert (the DTM catalog is then automatically updated).
• select Tools > Hardware Catalog, select the DTM catalog tab and click on the Update
button.
NOTE: Although DTM from EDS file is already installed on the PC, the DTM Audit tool
informs you to add the missing EDS file to the library and the project cannot be built.
This behavior results from a difference between the Device Name created during the
EDS file import to the DTM Hardware Catalog (with or without the setting New Naming
Convention) and the Device Name used in the DTM browser of your project.
To fix this mismatch:
• Remove the inconsistent EDS file from the DTM Hardware Catalog.
• close and open again Control Expert
• Re-import the EDS file to match the Device Name in the application (with or without the
setting New Naming Convention.

33003101.26 151
 Global project management

• Update the DTM catalog

For more detailed information about removing or importing EDS file, refer to chapter DTM
Hardware Catalog, page 266.

Complete Build Management

Rebuild all project, page 75 (DTM modifications or not) requires that all DTMs in the project
are 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

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 Control Expert Transfer Project from PLC, page 78 (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, page 293 service.
Some DTMs have a Compare function that allows comparing the configuration in the device
to the configuration in the PLC.

152 33003101.26
Global project management

Download Project
To use the Control Expert Transfer Project to PLC (Download project) function with DTMs:

Step Action

1 Construct a DTM topology tree.

2 Use the Store to device, page 293 service on each DTM that has a physical device on the
network.
3 Call the Transfer Project to PLC function to download the Control Expert project that includes a
DTM topology tree and device configurations.

33003101.26 153
154 33003101.26
Project browser

Project browser
What’s in This Chapter
Introduction to the project browser........................................... 155
Introduction to the various directories of the project
browser................................................................................. 198
Summaries of the utilities associated with the structure view
and function view ................................................................... 220

Subject of this chapter

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

Introduction to the project browser

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

Introduction to the project browser

General points
The project browser allows you to display the contents of a Control Expert 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 Control Expert project and allows you to
navigate within this with direct access:

33003101.26 155
 Project browser

• 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 Project. You can change this name by
accessing the project properties dialog box using the Properties command from the
contextual menu.

Functional view
The functional view displays the directory tree of the project, broken down into functional
modules , page 232. This breakdown does not take into account the order of execution of
the program by the PLC.

156 33003101.26
Project browser

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, page 158.

Allows you to display the structural view and the functional view in parallel, page 159.

33003101.26 157
 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:

158 33003101.26
Project browser

Display of both views in parallel

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

33003101.26 159
 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.

160 33003101.26
Project browser

Step Action

Result: Only the directory selected appears in the structural view (for example Program):

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:

33003101.26 161
 Project browser

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.

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:

162 33003101.26
Project browser

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.

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.

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.

33003101.26 163
 Project browser

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:

164 33003101.26
Project browser

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:

2 Activate the Expand all command from the Display menu or from the contextual menu.

Result: the selected directory is expanded completely:

33003101.26 165
 Project browser

How to contract a directory

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

166 33003101.26
Project browser

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:

2 Activate the Contract all command from the Display menu or from the contextual menu.

Result: the selected directory is contracted:

33003101.26 167
 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.

2 Select the Goto command from the menu.

168 33003101.26
Project browser

Step Action

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.26 169
 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.

170 33003101.26
Project browser

User Directory
At a Glance
In the Project directory and in all the directories of the project browser, you can create
hyperlinks, page 1765 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.26 171
 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, page 1765 in the directory provided for this purpose.

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.

172 33003101.26
Project browser

Description of the Tabs

The dialog box includes the following tabs and actions:

Tab Description

General Name: allows you to define the name of the project.

Type: indicates the type of Control Expert software used.

Libset version: indicates the FB library version used for your current project.

Program & Safety Password setting applies to the following:

Protection • Sections & Program Units: sections password settings, page 187
• Safety(1): safety password settings, page 181

Project & Controller Password setting applies to the following:

Protection
• Application(2): application password settings, page 174
• Firmware(3): firmware password settings, page 185
• Data Storage(4) or Web Diagnostics / Data Storage(5): data storage
password settings, page 189

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
• SourceSafeSignature (safety PACs)
When Automatically incremented is set:
• Major and Minor counters are not active
• Build counter is incremented at build
• Last rebuild All date is updated at Rebuild All
• Last partial build date is updated at Rebuild All and Build Change
When Automatically incremented is not set:
• Major, Minor and Build counters can be incremented manually by the user
• Last rebuild All date is updated at Rebuild All
• Last partial build date is updated at Rebuild All and Build Change
NOTE: Automatically incremented is set by default at project creation. It can
be deactivated by default when the option Auto incrementation of project
version is deselected (menu: Tools > Options > General).

33003101.26 173
 Project browser

Tab Description

Comment Allows a comment to be associated with the project.

1 Only for Modicon M580 Safety CPUs.

2 Except for Modicon Momentum.

3 Only for Modicon M580 CPUs with OS version ≥ 2.00, BME NOC 03••, and BME CXM 0100 modules.

4 Only for Modicon M580 CPUs.

5 Only for Modicon M580 CPUs with firmware version ≥ 4.01.

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.

Application Protection
Overview
Control Expert provides a password mechanism to help guard against unauthorized access
to the application.
Control Expert uses the password when you:
• Open the application in Control Expert.
• Connect to the PAC in Control Expert.
Setting an application password helps prevent unwanted application modification,
download, or opening of application files. The password is stored encrypted in the
application.
In addition to setting the password, you can encrypt the .STU, .STA and .ZEF files. The file
encryption feature in Control Expert helps prevent modifications by any malicious person
and reinforces protection against theft of intellectual property. The file encryption option is
protected by a password mechanism.
NOTE: When a controller is managed as part of a system project, the application
password and file encryption are disabled in Control Expert editor and need to be
managed by using the Topology Manager.

Password Construction
The password construction is based on IEEE Standard 1686–2013 recommendations.

174 33003101.26
Project browser

A password should contain at least 8 characters and should combine as a minimum one
upper-case (A, B, C, …), one lower-case (a, b, c, …), one number, and one non–
alphanumeric character (!, $, %, &, …).
NOTE: when exporting a project not encrypted to a .XEF or a .ZEF file, the application
password is cleared.

New Project Creation

By default a project is not password-protected and application files are not encrypted.
At project creation, the Security enforcement window allows you to:
• Set an application password, or
• Set an application password and apply encryption to your application files. Applying file
encryption also requires setting a password and we recommend setting two different
passwords.
If no password is entered the encryption of application files is not possible. In this case, the
next time you open your Control Expert project, the Password dialog opens. To access your
project, enter no password text, thereby accepting the empty string, and click OK.
Thereafter, you can follow the steps set forth below to set an application password and
enable file encryption.
NOTE: It is possible to create or change an application password at any time.
Setting an application password is mandatory for enabling file encryption.
When file encryption is enabled:
• Changing the application password is allowed.
• Clearing the application password is not allowed.

Setting an Application Password

Procedure for setting the application 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 Project & Controller Protection tab.

4 In the Application field, click Change password ....

Result: The Modify Password window appears.

33003101.26 175
 Project browser

Step Action

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.

Changing the Application 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 Project & Controller 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 Application Password

Clearing the application password is not allowed while file encryption is enabled.
Procedure for clearing the application protection password:

176 33003101.26
Project browser

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 Project & Controller 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.

Auto-Lock Feature
There is an optional auto-lock feature that limits access to the Control Expert software
programming tool after a configured time of inactivity. 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)
If the auto-lock feature is enabled and the configured inactivity time elapses, a modal dialog
box is displayed requiring the entry of the application password. Behind the modal dialog
box, all opened editors remain open in the same position. As a result, anybody can read the
current content of the Control Expert windows but cannot continue to work with Control
Expert.
NOTE: If you have not assigned a password to the project, the modal dialog box is not
displayed.

Password Request Condition

Open an existing application (project) in Control Expert:

33003101.26 177
 Project browser

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 message box indicates an incorrect password was entered, and a
new Application Password dialog box opens.

If you click Cancel, the application is not opened

Accessing the application in Control Expert after an auto-lock, when Control Expert is not
connected to the PAC or when the project in Control Expert is EQUAL to the project in the
PAC:

Password Management

When auto-lock time is elapsed, an Application Password dialog box opens:

Enter the password.

Click OK. If the password is correct, Control Expert becomes active again.

If the password is wrong, a message box indicates an incorrect password was entered, and a
new Application Password dialog box opens.

If you click Close, the application is closed without being saved.

Accessing the application in the PAC after an auto-lock, when Control Expert is connected to
the PAC and the application in Control Expert is DIFFERENT from the application in the
PAC:

Password Management

On connection, if Control Expert 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 message box indicates an incorrect password was

entered, and a new Application Password dialog box opens.

If you click Cancel, the connection is not established.

NOTE: On connection, if Control Expert 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.

178 33003101.26
Project browser

NOTE: After three attempts with a wrong password, you will have to wait an increasing
amount of time between each subsequent password attempt. The wait period increases
from 15 seconds to 1 hour, with the wait increment increasing by a factor of 2 after each
successive attempt with a wrong password.
NOTE: In case of password loss, refer to the procedure described in chapter Loss of
Password, page 191.

Enabling File Encryption Option

NOTE: You need to set an application password before enabling file encryption.
Procedure for enabling the file encryption option:

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 Project & Controller Protection tab.

4 Select File encryption active check-box.

Result: The Create Password window appears.

5 Enter the password in the Entry field.

6 Enter the confirmation of the 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.

Disabling File Encryption Option

Procedure for disabling the file encryption option:

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 Project & Controller Protection tab.

33003101.26 179
 Project browser

Step Action

4 De-select File encryption active check-box.

Result: The File Encryption Password window appears.

5 Enter the password and click OK to confirm.

NOTE: The application is no longer encrypted.

6 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.

Changing the File Encryption Password

Procedure for changing the file encryption 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 Project & Controller Protection tab.

4 In the File encryption 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.

Clearing the File Encryption Password

Procedure for clearing the file encryption password:

180 33003101.26
Project browser

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 Project & Controller Protection tab.

4 In the File encryption 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.

NOTE: In case of file encryption password loss, refer to the procedure described in
chapter Loss of Password, page 191.

Compatibility Rules
Encrypted application files (.STA, and .ZEF) can not be opened in Control Expert 15.0
Classic or earlier versions and encrypted files (.ZEF) cannot be imported in Control Expert
with Topology Manager.
The compatibility rules between application version and Control Expert/Unity Pro version
apply to .ZEF files exported without encryption option.
NOTE: When file encryption option in your project is enabled, archived application files
(.STA) cannot be saved without encryption.

Safe Area Password Protection

At a Glance
Safety CPUs include a safe area password protection function, which is accessible from the
Properties screen of the project. This function is used to help protect project elements
located within the safe area of the safety project.
NOTE: When the safe area password protection function is active, the safe parts of the
application cannot be modified

33003101.26 181
 Project browser

Modifications to the following safe area parts are not permitted when safe area password
protection is enabled:

Safe Part Forbidden action (offline AND online)

Configuration Modify CPU characteristics

Add, Delete, Modify a Safety module in the rack

Modify Safety Power supply

Types Create, Delete, Modify a Safe DDT

Change a DDT attribute: from not safe->safe

Change a DDT attribute: from safe->not safe

Create, Delete, Modify a Safe DFB

Change a DFB attribute: from not safe->safe

Change a DFB attribute: from safe->not safe

Program-SAFE Any Change under the Variables an FB instances node

Create Task
Import Task

Modify Task

Create Section
Delete Section
Import Section

Modify Section

Project Settings Modify SAFE project settings

Modify COMMON project settings

Encryption
The safe area password uses the standard encryption SHA-256 with a salt.

Safe Area Password Function versus Safety Project User Rights

The activation of the safe area password and the implementation of user rights created in
the Security Editor are mutually exclusive security functions, as follows:

182 33003101.26
Project browser

• If the user launching Control Expert has been assigned a user profile, that user can
access the safe areas of the safety application if the user knows the safe area
password and has been granted access rights in the Security Editor.
• If user profiles have not been assigned, a user can access the safe areas of the safety
application by knowing the safe area password.

Visual Indicators in Control Expert

The state of the safe area protection function can be visibly detected by viewing the
Program-SAFE node in the Project Browser:
• A locked padlock indicates a safe area password has been created and activated.
• An unlocked padlock indicates a safe area password has been created but not
activated.
• No padlock indicates a safe area password has not been created.
NOTE: If a safe area password has been created but not activated, and the safety
application is closed then re-opened, the safe area password is automatically activated
on re-opening. This behavior serves as a precaution if the safe are password was
unintentionally not re-activated.

Compatibility
The safe area password function exists for Control Expert V14.0 or later, for M580 safety
CPUs with firmware 2.80 or later.
NOTE:
• Application program .STU, .STA, and .ZEF files, which are created in Control
Expert V14.0 or later, cannot be opened in Unity Pro V13.1 and earlier.
• Replacing an M580 safety CPU in a Control Expert v14.0 application has the
following effect:
◦ Upgrading from firmware 2.70 to 2.80 (or later) adds the safe area password
functionality to the Program & Safety Protection tab of the Project >
Properties window.
◦ Downgrading from firmware 2.80 (or later) to 2.70 removes the safe area
password functionality.

Activating Protection and Creating Password

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

33003101.26 183
 Project browser

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 the Program & Safety Protection tab.

4 In the Safety area, 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 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.

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 the Program & Safety Protection tab.

4 In the Safety area, 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 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.26
Project browser

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 the Program & Safety Protection tab.

4 In the Safety area, 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.

Firmware Protection
Overview
Firmware protection by a password helps prevent unwanted access to the module firmware.

Password
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 is stored inside the module
only if the File encryption option is selected.

Changing the Password

It is possible to change a password at any time.

33003101.26 185
 Project browser

NOTE: Firmware password default value in the Control Expert application is:
fwdownload.
• For firmware V4.01 and later, you need to change the firmware password default
value, otherwise it will not be possible to build the Control Expert application.
• For firmware versions earlier than V4.01 it is not mandatory but strongly advised to
change firmware password default value.
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 Project & Controller 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.

Resetting the Password

Resetting the password assigns its default value to the firmware password in the Control
Expert application if the current password is confirmed.
To reset 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 Project & Controller Protection tab.

4 In the Firmware field, click Reset password....

186 33003101.26
Project browser

Step Action

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.

Program Unit, Section and Subroutine Protection

At a Glance
The protection function is accessible from the Properties screen of the project in offline
mode.
This function is used to protect the program elements (sections, Program Units).
NOTE: The 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 program elements only. This
does not prevent from:
• Connecting to the CPU
• Uploading application from the CPU
• Changing the configuration
• Adding new Program Units and/or sections
• Changing the logic in a new (not protected) section

Activating Protection and Creating Password

Procedure for activating the protection and creating the password for sections and Program
Units:

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.

33003101.26 187
 Project browser

Step Action

3 Select Program & Safety Protection tab.

4 In the Sections & Program Units 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 Unity Pro V4.0 and earlier.

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 program element is configured with a protection (read or read/write), when protection
has been activated this will be indicated by a locked padlock at the program element level.
If the program element is configured with a protection but the protection is disabled, an open
padlock is displayed at the program element level.

Changing the Password

Procedure for changing the project protection password for sections and Program Units:

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 Program & Safety Protection tab.

4 In the Sections & Program Units 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.

188 33003101.26
Project browser

Step Action

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 Unity Pro V4.0 and earlier.

Unity Pro is the former name of Control Expert for version 13.1 or earlier.

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 protection password for sections and Program Units:

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 Program & Safety Protection tab.

4 In the Sections & Program Units 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.

Data Storage/Web Protection

Overview
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).
For Modicon M580 CPUs in a project created by Control Expert with version:

33003101.26 189
 Project browser

• Earlier than version 15.1, you can provide password protection for data storage access.
• Version 15.1 or later, you can provide password protection for both web diagnostics and
data storage access.

Password
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 Data Storage/Web password is stored inside the
module only if the File encryption option is selected.

Changing the Password

It is possible to change a password at any time.
NOTE: Data Storage/Web password has a default value in Control Expert application.
This default value depends on the version of Control Expert, and is:
• datadownload for Control Expert versions earlier than V15.1.
• webuser for Control Expert versions V15.1 and later.
Changing the default password is mandatory, or not, depending on the module firmware
version:
• For firmware V4.01 and later, you need to change the Data Storage/Web password
default value, otherwise it will not be possible to build the Control Expert application.
• For firmware versions earlier than V4.01 it is not mandatory but strongly advised to
change Data Storage/Web password default value.
Procedure for changing the Data Storage/Web 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 Project & Controller Protection tab.

4 In the Data Storage (or Web Diagnostics / 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.

190 33003101.26
Project browser

Step Action

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.

Resetting the Password

Resetting the password assigns its default value to the Data Storage/Web password in the
Control Expert application if the current password is confirmed.
To reset 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 Project & Controller Protection tab.

4 In the Data Storage (or Web Diagnostics / 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.

Loss of Password
Overview
If you forget your password, proceed as indicated in the following procedures and contact
Schneider Electric support.
NOTE: The application password recovery procedure differ depending on whether the
file encryption option is enabled or disabled.

33003101.26 191
 Project browser

Control Expert Application Password without File Encryption

Option
The following procedure for resetting the application password is valid when file encryption
option is disabled or for application file managed with Control Expert 15.0 Classic or earlier
versions.
Schneider Electric support needs a string of alphanumeric characters displayed in the
Password forgotten pop-up window as soon as you press SHIFT+F2 in the Password
dialog box.
The following conditions must be met in order to reach the Password dialog box:
• 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: The Password forgotten pop-up window is open and a string of alphanumeric characters is
displayed.

3 Copy this string and give it 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.

192 33003101.26
Project browser

Control Expert Application Password with File Encryption Option

If you forget your application password when file encryption is enabled, you need to send
the application file to Schneider Electric support. Then you receive back the encrypted
application file with a new file application password from Schneider Electric support.
NOTE: We highly recommend to change the application password.

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: The Password forgotten pop-up window is open and a string of alphanumeric characters is
displayed.

3 Copy this string and give it 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: The Password forgotten pop-up window is open and a string of alphanumeric characters is
displayed.

3 Copy this string and give it to Schneider Electric support.

4 Receive the generated password from Schneider Electric support.

33003101.26 193
 Project browser

Step Action

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.

File Encryption Password

Schneider Electric support needs a string of alphanumeric characters displayed in the
Password forgotten pop-up window as soon as you press SHIFT+F2 in the Password
dialog box.
To reach the Password dialog box:
• Go to Project > Properties of Project > Project & Controller Protection
• In the File encryption field, click Clear password.... The Password dialog box is
displayed.
Procedure for resetting the file encryption password:

Step Action

1 Condition: The Password dialog box is displayed.

2 Press SHIFT+F2.

Result: The Password forgotten pop-up window is open and a string of alphanumeric characters is
displayed.

3 Copy this string and give it 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 and click OK to close the Password dialog.

194 33003101.26
Project browser

Step Action

6 Click Change Password and change the password (the old password = password provided by
Schneider Electric support).

7 Click OK to close the Modify Password dialog, then 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.

Safe Area Password

Schneider Electric support needs a string of alphanumeric characters displayed in the
Password forgotten pop-up window as soon as you press SHIFT+F2 in the Password
dialog box.
To reach the Password dialog box:
• Go to Project > Properties of Project > Program & Safety Protection
• In the Safety field, click Change password.... The Password dialog box is displayed.
Procedure for resetting the safe area password:

Step Action

1 Condition: The Password dialog box is displayed.

2 Press SHIFT+F2.

Result: The Password forgotten pop-up window is open and a string of alphanumeric characters is
displayed.

3 Copy this string and give it 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 and click OK to close the Password dialog.

6 Click Change Password and change the password (the old password = password provided by
Schneider Electric support).

7 Click OK to close the Modify Password dialog, then 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.26 195
 Project browser

Firmware Password
Schneider Electric support needs a string of alphanumeric characters displayed in the
Password forgotten pop-up window as soon as you press SHIFT+F2 in the Password
dialog box.
To reach the Password dialog box:
• Go to Project > Properties of Project > Project & Controller Protection
• In the Firmware field, click Reset password.... 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: The Password forgotten pop-up window is open and a string of alphanumeric characters is
displayed.

3 Copy this string and give it 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 and click OK to close the Password dialog.

6 Click Change Password and change the password (the old password = password provided by
Schneider Electric support).

7 Click OK to close the Modify Password dialog, then 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/Web Password

Schneider Electric support needs a string of alphanumeric characters displayed in the
Password forgotten pop-up window as soon as you press SHIFT+F2 in the Password
dialog box.
To reach the Password dialog box:
• Go to Project > Properties of Project > Project & Controller Protection
• In the Data Storage field, click Reset password.... The Password dialog box is
displayed.
Procedure for resetting the data storage password:

196 33003101.26
Project browser

Step Action

1 Condition: The Password dialog box is displayed.

2 Press SHIFT+F2.

Result: The Password forgotten pop-up window is open and a string of alphanumeric characters is
displayed.

3 Copy this string and give it 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 and click OK to close the Password dialog.

6 Click Change Password and change the password (the old password = password provided by
Schneider Electric support).

7 Click OK to close the Modify Password dialog, then 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.26 197
 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.

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

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

198 33003101.26
Project browser

Directory Services

Project Export Project: allows you to access export of the global project, page 1711.

Project Settings: allows you to access the project specific settings, page 548.

Properties: allows you to access the properties of the global project.

Configuration allows you to access the hardware configuration, page 199 and the parameter
settings of the modules.

Derived Data Types allows you to access the DDTs, page 201.

Derived FB Types allows you to access the DFB, page 202 types.

Variables & FB allows you to access the variables, page 203 and function block instances.
instances
Motion allows you to access the declaration, page 205 and configuration of the
servodrives.
Communication allows you to access the configuration of the networks, page 207.

Ethernet Network allows you to access the Ethernet Network configuration, page 208.

Programs allows you to access the project programs, page 208.

Animation Tables allows you to access the animation tables, page 212.

Operator Screens allows you to access the operator screens, page 215.

Documentation allows you to access the documentation, page 217.

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.

33003101.26 199
 Project browser

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 Open: used to access the bus editor, X Bus in the above example.

Import: used to import the configuration, page 1689 of the project inputs/outputs (offline
mode only).

Import SIS: used to import the configuration, page 1378 of a project created using the SIS
Automation tool.

Export: used to export the configuration, page 1687 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).

Export: used to export the configuration, page 1687 of the module(offline mode only and
depending on the module).

Empty slot Import: used to import the configuration of a BMENOC03•1 module with all devices
configured behind the NOC master DTM.

import the configuration, page 1689 of a module (offline mode only).

200 33003101.26
Project browser

Access
From the Configuration directory, you can:
• Configure the PLC rack, page 1294 with:
◦ a power supply, page 1300,
◦ a processor, page 1303,
◦ one or more modules, page 1307.
• Configure field bus devices, page 1311,
• Access the configuration of the rack elements:
◦ Premium, page 1353 and Quantum, page 1363 processors,
◦ modules, page 1372.

Derived data types (DDT) directory

At a Glance
The Derived data types (see EcoStruxure™ Control Expert, 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:

33003101.26 201
 Project browser

Directory Services

Derived Data Types Open: allows you to access the DDT types tab of the data editor, page 345, from
which you can:
• create, page 353 a DDT,
• manage, page 364 a DDT,
Get from Library: allows you read access to one or more DDT types from a library,
page 310.

Put in Library: used to archive, page 371 all the DDTs in a library, page 310.

Export: allows you to access export of all DDT types, page 1696.

Import: allows you to access import of one or more DDT types, page 1697.

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, page 435 the DDT.

Properties: allows you to access the DDT properties.

Export: allows you to access export of all DDT types, page 1696.

Derived FB (DFB) types directory

At a Glance
The Derived FB types (see EcoStruxure™ Control Expert, 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:

202 33003101.26
Project browser

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, page 1249.

Get from Library: allows you read access to one or more DFB types from a library,
page 310.

Put in Library: allows you write access to all DFB types in a library.

Export: allows you to access export of all DFB types, page 1694 of the project.

Import: allows you to access import of one or more DFB types, page 1695.

DFB Type (Counter, etc.) Open: allows you to access the DFB type in the DFB tab of the Data Editor, page
1249.

Delete: allows you to delete the DFB type.

Put in Library: allows you write access to the DFB type in a Library, page 310.

Analyze: allows you to analyze, page 435 the DFB type.

Properties: allows you to access the properties, page 1261 of the DFB type.

Export: allows you to access export of the DFB type, page 1694.

Sections New Section: allows you to create a new section, page 499 in the DFB type.

Section XX Open: allows you to access the section, page 499 program language editor.

Delete: allows you to delete the section.

Properties: allows you to access the properties, page 502 of the section.

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 EcoStruxure™ Control Expert, Program Languages and
Structure, Reference Manual)DDT, IODDT) (see EcoStruxure™ Control Expert, Program
Languages and Structure, Reference Manual)and the function block instances(EFB, DFB).
(see EcoStruxure™ Control Expert, Program Languages and Structure, Reference Manual)

33003101.26 203
 Project browser

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, page 1698 of the
project,

Import: used to access the import of all variables, page 1701 of the
project.

Elementary variables Open: used to access the tab corresponding to the variables editor,

Derived variables Export: used to access the export of all variables, page 1698 of the
family selected (EDT, DFB, etc.) .
Decice DDT variables

I/O derived variables

Elementary FB instances

Derived FB instances

Access
From the Variables & FB instances directory, you can access the different tabs of the data
editor:

204 33003101.26
Project browser

• Variables tab,
◦ Create, page 386 a data instance,
◦ Create, page 396 an IODDT type data instance,
◦ Create, page 399 a Device DDT type data instance,
◦ Modify, page 414 attributes of data instances.
• DDT Types tab,
◦ Create, page 353 a data instance,
◦ Archive, page 371 DDTs in a library, page 310,
• Function blocks tab,
◦ Create, page 376 a data instance,
◦ Modify, page 382 attributes of data instances.
• DFB Types tab,
◦ Create, page 1249 a DFB type,
◦ Configure settings, page 1250 of a DFB type.

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.

33003101.26 205
 Project browser

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 Premium using EcoStruxure™ Control Expert, Motion Function Blocks, Start-up
Guide).

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.

206 33003101.26
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:

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, page 1702.

Import: allows you to access import of one or more networks, page 1703.

Network New Network: allows you to add a network, page 445 to your project.

33003101.26 207
 Project browser

Directory Services

Network Open: allows you to access the corresponding network editor: Ethernet,
Modbus Plus, Fipway.
(Network_1, Modbus Plus_A,
etc.) Export: allows you to access export of one network, page 1702.

Delete: allows you to delete a network.

Properties: allows you to access the network properties.

Routing Table Open: allows you to access the configuration, page 453 of a bridge between 2
networks (routing tables).

Ethernet Network Directory

At a Glance
Double-click the Ethernet Network directory of the project structural view provides access
to the Ethernet Network Manager tool.
This directory is available in a Modicon M580 configuration.

Ethernet Network Window

The Ethernet Network window displays configuration information on the PAC networks and
allows you to edit some parameters for specific communication adapter modules.
More information on the Ethernet Network Manager tool is provided in Modicon M580
topology guides (see Modicon M580, System Planning Guide for, Complex Topologies).

Programs Directory
At a Glance
The Programs directory of the structural view of the project allows you to define the
structure of the program and to access the language editors of the program elements:
Program Units, sections, program modules and event processing.

208 33003101.26
Project browser

The following illustration shows an example of a directory tree of the Programs directory:

NOTE: When Program Units in the application are not allowed, the Logic folder is
replaced by the Sections folder in the directory tree. For more detailed information refer
to the chapter Description of the Available Functions for Each Type of PLC (see
EcoStruxure™ Control Expert, Program Languages and Structure, Reference Manual).

Services associated with the sequential Tasks directories.

The sequential Tasks directories (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, page 469 (FAST, AUX, AUX0,
AUX1). The MAST task is created by default.

Import ...: allows you to import a task, page 1692.

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.

33003101.26 209
 Project browser

Directory Services

Export: allows you to export the sequential task, page 1690.

Properties: allows you to access the properties of the sequential task.

Logic New Program Unit...: allows you to create a new “empty” Program Unit.

New Section ...: allows you to create a new “empty” section, page 499.

Import ...: allows you to import a program unit or a section, page 1692.

Create builded Activation Conditions Table: allows you to initialize an animation

table, with the activation condition variables associated with the sections.

Or
Sections New Section ...: allows you to create a new "empty" section, page 499.

Import ...: allows you to import a section, page 1692.

Create section activation conditions table: allows you to initialize an animation table,
with the activation condition variables associated with the sections.

Services associated with the Program Unit

The structure of a Program Unit allow you to access the following services, which can be
reached via the contextual menu:

Program Element Services

For each Program Analyze: allows you to analyze the Program Unit.
Unit
Delete: allows you to delete the Program Unit.

Copy: allows you to copy the Program Unit.

Paste After: allows you to paste after a duplication of the copied Program Unit, page
497.

Paste Special after...: allows you to paste after a duplication of the copied Program
Unit with effective parameters, page 498.

Import after: allows you to import a Program Unit or a section, page 1692.

Export ...: allows you to export the Program Unit, page 1690.

Properties: allows you to access the properties of the Program Unit.

For the Interface & Open: allows you to access the Program Unit data editor.
Variables
Sections directory New Section ...: allows you to create a new “empty” section, page 499.
(under Program Unit)
Import ...: allows you to import a section, page 1692

210 33003101.26
Project browser

Program Element Services

For each section, Refer to services associated, page 211 with the section.
section Macro-step,
action, or transition

Animation Tables Refer to services associated, page 213 with the Animation Tables Directory.
directory (under
Program Unit)

For each animation

table

Services associated with the section

The section allow you to access the following services, which can be reached via the
contextual menu:

Program Element Services

For each section Open: allows you to access the section, page 499 language editor.

Delete: allows you to delete the section.

Detach: allows you to detach the section of the functional module.

Export: allows you to export the section, page 1690.

Import after ...: allows you to import a section, page 1692

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
(in online mode).

Properties: allows you to access the properties of the section.

For each Section Open: allows you to access the section language editor.
Macro-step, action,
or transition Delete: allows you to delete the section.

Properties: allows you to access the properties of the section.

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

33003101.26 211
 Project browser

Services associated with the program modules directories

The program modules directories (SR Sections) 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, page 519.

Import ...: allows you to access import of program module, page 1692.

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, page 1690.

Properties: allows you to access the properties of the program module.

Services associated with the event processing directories

The event processing (see EcoStruxure™ Control Expert, 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, page 523.
Events
Import: allows you to access import of event processing, page 1692.

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, page 1690.

Properties: allows you to access the event processing properties.

Animation Tables Directory

At a Glance
The Animation Tables Directory of the structural view of the project allows you to access
the animation tables.

212 33003101.26
Project browser

The following illustration shows an example of a directory tree of the Animation Tables
directory:

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

33003101.26 213
 Project browser

Directory Services

Animation tables New Animation Table: allows you to create a new animation table, page 1469.

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, page 1707.

Import: allows you to access import of one or more animation tables, page 1708.

Make All Tables Permanent: allows you to change all temporary animation tables
to permanent animation tables (see also Permanent and Temporary Animation
Tables, page 1467).

Purge Temporary Tables: allows you to delete all temporary animation tables (see
also Permanent and Temporary Animation Tables, page 1467).

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 1494).

For each animation table Open: allows you to access the animation 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, page 1707.

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, page 1475 data,
• switch to modification, page 1481 mode,
• switch to forcing, page 1486 mode,
• modify or force, page 1491 several variables.

214 33003101.26
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:

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

33003101.26 215
 Project browser

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, page 1705 and/or
family of screens.

Export: allows you to access export of all screens, page 1704.

Messages list: allows you to access the message list for the operator screens.

For each family of screens New screen: allows you to create a new operator screen.

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, page 1704.

Family Properties: allows you to access the properties of the family of screens.

For each operator screen Open: allows you to access the operator screens editor.

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, page 1704.

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:

216 33003101.26
Project browser

• create, page 1571 objects,

• insert objects from a library, page 1637,
• modify the attributes, page 1582 of the objects,
• manipulate, page 1607 the objects that make up the screen,
• use the screens in online mode, page 1626.

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:

33003101.26 217
 Project browser

Directory Services

Documentation Open: allows you to access the documentation, page 1651 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, page 1805.

Conversion Report Directory

At a Glance
The Conversion Report directory is displayed in the structural view of the project when
opening a PL7 (see EcoStruxure™ Control Expert, PL7 Application Converter, User Manual)
project with a .FEF extension or a Concept (see EcoStruxure™ Control Expert, 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.),

218 33003101.26
Project browser

• warnings,
• errors.

33003101.26 219
 Project browser

Summaries of the utilities associated with the

structure view and function view
About this sub-chapter
This sub-chapter provides summaries of the utilities associated with the function view and
structure 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.

Project Directory
The Project directory, page 198 allows you to access the following services.

Directory Services Mode

Off-line On-line On-line

Stop Run

Project Export Project Yes No No

Properties Yes Yes Yes

Configuration Directory
The Configuration directory, page 199 allows you to access the following services.

220 33003101.26
Project browser

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

Derived FB Types Directory

The Derived FB Types directory, page 202 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 DFB Open Yes Yes Yes

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

33003101.26 221
 Project browser

Directory Services Mode

Off-line On-line On-line

Stop Run

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, page 201 allows you to access the following services.

Directory Services Mode

Off-line On-line On-line

Stop Run

Derived Data Types 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 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.

Variables & FB instances Directory

The Variables & FB instances directory, page 203 allows you to access the following
services.

222 33003101.26
Project browser

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, page 203 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, page 207 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

33003101.26 223
 Project browser

Directory Services Mode

Off-line On-line On-line

Stop Run

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

Programs Directory
The Programs directory, page 208 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

For each task, (MAST, Clear Yes Yes No

FAST, AUX•)
Delete Yes(1) No No

Export Yes No No

Properties Yes Yes Yes

Sections(3) Refer to the tables below for services availability according to the operating mode.

or

Logic(3)

SR Sections New SR Section Yes Yes Yes

Import Yes No No

For each program Open Yes Yes Yes

module
Delete Yes(2) Yes(2) Yes(2)

Export Yes No No

Import after Yes No No

Properties Yes Yes Yes

224 33003101.26
Project browser

Directory Services Mode

Off-line On-line On-line

Stop Run

Timer Events, I/O Events New Event Section Yes Yes Yes

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.

(3) Depends on the CPU.

The Sections directory under each task allows you to access the following services.

Directory Services Mode

Off-line On-line On-line

Stop Run

Sections New Section Yes Yes Yes

Create section activation conditions table Yes Yes Yes

Import Yes No No

For each section Open Yes Yes Yes

Delete Yes Yes Yes

Detach Yes Yes Yes

Export Yes No No

Import after Yes No No

Force to 0 No Yes Yes

Force to 1 No Yes Yes

Unforce No Yes Yes

Properties Yes Yes Yes

The Logic directory under each task allows you to access the following services.

33003101.26 225
 Project browser

Directory Services Mode

Off-line On-line On-line

Stop Run

Logic New Program Unit Yes Yes Yes

New Section Yes Yes Yes

Create builded activation conditions table Yes Yes Yes

Import Yes No No

For each Program Unit Analyze Yes Yes Yes

Delete Yes Yes Yes

Detach Yes Yes Yes

Copy Yes Yes Yes

Paste After Yes Yes Yes

Paste Special after Yes Yes Yes

Import after Yes No No

Export Yes No No

Properties Yes Yes Yes

Sections (under Program New Section Yes Yes Yes

Unit)
Import Yes No No

For each section of the Open Yes Yes Yes

Program Unit
Delete Yes Yes Yes

Export Yes No No

Import after Yes No No

Force to 0 No Yes Yes

Force to 1 No Yes Yes

Unforce No Yes Yes

Properties Yes Yes Yes

Animation tables (under New Animation Table Yes Yes Yes

Program Unit)
Paste Yes Yes Yes

Detach All Yes Yes Yes

Delete All Yes Yes Yes

Import Yes No No

226 33003101.26
Project browser

Directory Services Mode

Off-line On-line On-line

Stop Run

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 animation table Open Yes Yes Yes

of the Program Unit
Copy Yes Yes Yes

Paste Yes Yes Yes

Export Yes No No

Delete Yes Yes Yes

Detach Yes Yes Yes

Properties Yes Yes Yes

For each section (under Open Yes Yes Yes

Logic)
Delete Yes Yes Yes

Detach Yes Yes Yes

Export Yes No No

Import after Yes No No

Force to 0 No Yes Yes

Force to 1 No Yes Yes

Unforce No Yes Yes

Properties Yes Yes Yes

Animation tables Directory

The Animation tables directory, page 212 allows you to access the following services.

33003101.26 227
 Project browser

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 animation table Open Yes Yes Yes

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, page 215 allows you to access the following services.

228 33003101.26
Project browser

Directory Services Mode

Off-line On-line On-line

Stop Run

Operator Screens New screen Yes Yes Yes

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

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, page 217 allows you to access the following services.

33003101.26 229
 Project browser

Directory Services Mode

Off-line On-line On-line

Stop Run

Documentation Open Yes Yes Yes

Title Page Print Setup Yes Yes Yes

General Information Open Yes Yes Yes

230 33003101.26
33003101.26 231
 Functional modules

Functional modules
What’s in This Chapter
Introduction to the functional view ........................................... 232
The functional modules and their associated utilities................. 246

Aim of this Chapter

This chapter introduces the functional modules incorporated in a Control Expert project.

Introduction to the functional view

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

Functional modules
Definition
A functional module is a group of program elements intended to perform a PLC function.
A functional module is comprised:
• Program Units (only for Modicon M580 and M340)
• 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:

232 33003101.26
Functional modules

• the configuration,
• the global variables of a project,
• the DFB and DDT types, which are global to a project,
• the SR program modules, which are global to a task,
• the documentation.

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

NOTE: When Program Units are allowed in the application (Modicon M580 and M340),
the Program folder is replaced by the Logic folder in each functional module 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.

33003101.26 233
 Functional modules

Project directory of the functional view

At a Glance
The Functional Project 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 Project directory:

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

Directory Services

Functional Project 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, page 1711.

Import: allows you to access import of a functional module, page 1710.

Project Settings: allows you to access the project specific settings, page 548.

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: program,
module animation tables, operator screens, nested functional modules.

234 33003101.26
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:

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

33003101.26 235
 Functional modules

Directory Services

Functional module: New Functional Module...: allows you to create a new nested functional module.
Processing
Create...: allows you to create a new program element in the functional module.

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, page 1709.

Import: allows you to access import of a functional module, page 1710.

Create builded 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 Section(s)...: 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, page 236.

or

Logic

Table allows you to access the animation tables of the functional module, page 237.

Screen allows you to access the operator screens of the functional module, page 238.

Functional Module Program Directory

At a Glance
The program directory of a functional module (Program or Logic) allows you to access the
program elements of this module: Program Units (when available), sections, program
modules, and event processing.

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

236 33003101.26
Functional modules

Directory Services

Program Create...: allows you to create a new program element in the functional module:
Program Unit, section, program module or event processing.
or
Detach all: allows you to detach all elements included in the functional module
Logic (Program Units, sections, and animation tables) without deleting them.

Import...: allows you to import a program element to the functional module: Program
unit, section, program module, event processing (see also topic on program import,
page 1692).

Create builded 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 Section(s)...: allows you to define the protection of the

program elements of the functional module: Program Units, sections, program modules
and event processing.

Program Unit, See Programs Directory, page 208 for a description of the associated services.
Section, SR
section, event
processing

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:

33003101.26 237
 Functional modules

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, page 1708 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, page 1707.

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.

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:

238 33003101.26
Functional modules

Directory Services

Screen Import: allows you to access import of one or more screens, page 1705 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 215 for a description of the screen families
screens services.
For each operator See Operator Screens Directory, page 215 for a description of the services
screen available from the screen.

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 Project Directory

The Functional Project directory, page 234 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

Project
Detach All Yes Yes Yes

Export Yes No No

Import Yes No No

Project Settings Yes Yes Yes

Properties Yes Yes Yes

33003101.26 239
 Functional modules

Functional Module Directory

The Functional Module directory, page 235 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
module Detach All Yes Yes Yes

Create Yes Yes Yes

Delete Yes Yes Yes

Export Yes No No

Import Yes No No

Protection of Included Sections Yes Yes Yes

Create builded Activation Conditions Table Yes Yes Yes

Properties Yes Yes Yes

Functional Module Program Directory

The program directory, page 236 of a functional module allows you to access the following
services.

Directory Services Mode

Off-line On-line On-line

Stop Run

Program(1) Create Yes Yes Yes

or Import Yes No No

Logic(1) Detach All Yes Yes Yes

Protection of Included Sections Yes Yes Yes

Create builded Activation Conditions Table Yes Yes Yes

For each Refer to the table below for services availability according to the operating mode.
Program Unit

240 33003101.26
Functional modules

Directory Services Mode

Off-line On-line On-line

Stop Run

For each section, Open Yes Yes Yes

event processing
Delete Yes Yes Yes

Detach Yes Yes Yes

Export Yes No No

Import After Yes No No

Force to 0 No Yes Yes

Force to 1 No Yes Yes

Unforce No Yes Yes

Properties Yes Yes Yes

(1) Depends on the CPU

The Program Unit directory, page 236 of a functional module allows you to access the
following services.

33003101.26 241
 Functional modules

Directory Services Mode

Off-line On-line On-line

Stop Run

For each Analyze Yes Yes Yes

Program Unit
Delete Yes Yes Yes

Detach Yes Yes Yes

Copy Yes Yes Yes

Paste After Yes Yes Yes

Paste Special after Yes Yes Yes

Import After Yes No No

Export Yes No No

Force to 0 No Yes Yes

Force to 1 No Yes Yes

Unforce No Yes Yes

Properties Yes Yes Yes

Sections (under New Section Yes Yes Yes

a Program unit
Import Yes No No

For each section Open Yes Yes Yes

of the Program
Unit Delete Yes Yes Yes

Detach Yes Yes Yes

Import After Yes No No

Export Yes No No

Force to 0 No Yes Yes

Force to 1 No Yes Yes

Unforce No Yes Yes

Properties Yes Yes Yes

242 33003101.26
Functional modules

Directory Services Mode

Off-line On-line On-line

Stop Run

Animation tables New Animation Table Yes Yes Yes

(under Program
Unit) 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
of the Program Copy Yes Yes Yes
Unit
Paste Yes Yes Yes

Export Yes No No

Delete Yes Yes Yes

Detach Yes Yes Yes

Properties Yes Yes Yes

Functional Module Animation Tables Directory

The Table directory, page 237 of a functional module allows you to access the following
services.

33003101.26 243
 Functional modules

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

Functional Module Operator Screens Directory

The Screen directory, page 238 of a functional module allows you to access the following
services.

244 33003101.26
Functional modules

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 New screen Yes Yes Yes
of 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.26 245
 Functional modules

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.

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 comment comprising 256 characters.
NOTE: The activation condition and the protection of the program elements (Program
Units, sections, program modules and event processing) are defined under program
element properties.

Displaying or editing properties

Carry out the following steps:

Step Action

1 In the functional view, right-click the functional module, in the Functional Project directory.

2 Click Properties.

3 Perform the editing.

4 Confirm with OK.

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

246 33003101.26
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 Project 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 Project 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 Project 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
Project directory level or to another functional module).
Moving a functional module:

33003101.26 247
 Functional modules

Step Action

1 Left-click on the module to be moved (holding down the mouse button),

2 Move the module to the desired position.

Programming a functional module

Introduction to programming a functional module
A functional module has a program directory (Program or Logic) that may contain program
elements:
• Program Unit (only for Modicon M580 an M340)
• LD, ST, FBD, IL sections
• event processing
• SFC sections
For more detailed information, refer to chapter Application Program structure (see
EcoStruxure™ Control Expert, Program Languages and Structure, Reference Manual).
Various cases may arise when programming a functional module:
• Case 1: the program element already exists in the structural view
• Case 2: creating the program element using the functional view
• Case 3: importing a program element using the functional view

Case 1: the program element already exists in the structural view

The program element has already been created in the structural view:

Step Action

1 Select the program element.

2 Move the program element to the functional module.

Case 2: creating the program element using the functional view

The following table shows how to create a program element:

248 33003101.26
Functional modules

Step Action

1 In the Functional view, right-click the Program or Logic directory in the functional module
directory.

2 Select the Create ... command from the contextual menu.

3 Select either New Program Unit ..., New Section ..., New Timer Event ... or New IO Event ....

4 Enter the various headings in exactly the same way as for creating a program element from the
structural view. The name of the functional module is shown again at the structural view level.

Case 3: importing a program element using the functional view

The following table shows how to import a program element:

Step Action

1 In the Functional view, right-click the Program or Logic directory in the functional module
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 program element that does not have its task in
the importing application, the program element is attached to the MAST task.

CAUTION
UNEXPECTED APPLICATION BEHAVIOR
Verify that an imported program element 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 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.

33003101.26 249
 Functional modules

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 program elements attached to the functional module
and to the lower level modules.

Protecting program elements of the functional module

At a Glance
In a functional module you are able to define the protection, page 187 of the program
elements contained in the module.

Protection
Procedure:

Select from Then...

the functional module • with the mouse right-click the functional module in the Functional Project
directory of the functional view,
• select Protection of Included Section(s) ...,
• select Read only or No read & write.
Result: All the program elements of the module are protected.

from the Program or Logic • with the mouse right-click on the Program or Logic directory in a functional
directory module of the functional view,
• select Protection of Included Section(s) ...,
• select Read only or No read & write.
Result: All the program elements of the module are protected.

Debugging a functional module

At a Glance
The organization of a functional module, and the distribution of the Program Units, 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.

250 33003101.26
Functional modules

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.

Select from Then...

the functional module • right-click with the mouse on the directory of a functional module in the
functional view.
• select Create builded Activation Conditions Table.
from the Program or • with the mouse right-click on the Program or Logic directory in a functional
Logic directory module of the functional view.
• select Create builded Activation Conditions Table.

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

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 Program Units and/or 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:

33003101.26 251
 Functional modules

Step Action

1 Select the Functional Project 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 Project 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, Logic, Table, Screen) from a functional
module, you must do the following:

Step Action

1 Select the Program or Logic 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.

Detaching one element in a directory from a functional module

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

Step Action

1 Select the element to be detached in the Program or Logic or Table or Screen directory.

2 Select Detach from the contextual menu.

Result: The element in the chosen directory is detached from the functional module.

252 33003101.26
Functional modules

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.

33003101.26 253
 Functional modules

Deleting one functional module with deletion of the modules,

animation tables and screens

CAUTION
UNEXPECTED APPLICATION BEHAVIOR
Before deleting a module, ensure that the deletion of the subsequent elements:
• the Program Units contained in the module,
• 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 Program Unit, or a section, or an event in a functional

module

CAUTION
UNEXPECTED APPLICATION BEHAVIOR
A Program Unit, or 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:

254 33003101.26
Functional modules

Step Action

1 Select the desired Program Unit, or section, or event.

2 Select Delete.
3 Confirm with Yes.

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.

Functional module export

Exporting a functional module
You can export, page 1709 a functional module.

Functional module import

Importing a functional module
You can import, page 1710 a functional module.

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.

33003101.26 255
 Functional modules

Creating an Animation Table

Procedure:

If the table Then...

already exists • select the animation table in the Functional Project 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.

needs to 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...

needs to be copied from the • with the mouse right-click the source table in the Functional Project
functional view. directory of the functional view,
• select Copy,
• select the source table in the Functional Project directory of the functional
view,
• select Paste.
Result: The copy of the table is created in the source table directory.

Opening an Animation Table

Carry out the following actions:

256 33003101.26
Functional modules

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 function • left-click on the table to be moved (holding down the mouse 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 contextual Then...

menu
Detach all • select the Table directory of the functional module,
• select Detach All from the contextual menu,
• confirm with Yes.

33003101.26 257
 Functional modules

Detaching an Animation Table

Procedure:

If using the contextual Then...

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.

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 Project 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.

needs to be created from • with the mouse right-click the Screen directory of the functional module,
the functional view
• select New screen.

258 33003101.26
Functional modules

Accessing the Operator Screen Properties

Procedure:

If selected at the level of Then...

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.

Creating a Family of Operator Screens

Procedure:

If the family Then...

already exists • select the family of operator screens in the Functional Project 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.

needs to be created from • with the mouse right-click the Screen directory of the functional module,
the functional view • select New family.

Opening an Operator Screen

Carry out the following actions:

Step Action

1 Select the operator screen in the Functional Project 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:

33003101.26 259
 Functional modules

If the screen Then...

does not belong to a family • with the mouse right click the operator screen in the Operator Screen
of screens directory,
• select Delete.
belongs to a family of • from the Screen directory, right-click the operator screen belonging to the
screens family,
• select Delete.

Moving an Operator Screen

Procedure:

If using Then...

the drag-and-drop function • left-click on the operator screen to be moved (holding down the 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 from • select the operator screen,

the contextual menu • select Screen Properties from the contextual 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 and • select the Screen directory of the functional module,
the families of screens
• select Detach All from the contextual menu,
• 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,

260 33003101.26
Functional modules

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.

33003101.26 261
262 33003101.26
FDT Container

FDT Container
What’s in This Chapter
FDT Container....................................................................... 263
DTM Hardware Catalog.......................................................... 266
DTM Browser ........................................................................ 279
DTM Properties Tabs ............................................................. 305

Object of the Chapter

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

FDT Container
Object of this Section
This section is an introduction to using DTMs in Control Expert.

Introduction to the Control Expert FDT Container

At a Glance
The FDT/DTM (Field Device Tool/Device Type Manager), an open-standard, in Control
Expert integrates the configuration tools needed to build projects, with a mix of Schneider
and Third Party intelligent devices, on heterogeneous networks.
Control Expert 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 Control Expert.

33003101.26 263
 FDT Container

FDT Concept
The FDT defines the interfaces between device-specific software components (DTMs) and
Control Expert. 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 Control Expert is based on an open standard, Control Expert 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 Control Expert 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 Control Expert, its FDT Container uses:
• The DTM Hardware Catalog, page 267
• The DTM Browser, page 279
• 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 Control Expert on-line Help.

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 Control Expert profile is set to Read Only for the user
2. The user has opened Control Expert in the Read Only mode

264 33003101.26
FDT Container

Control Expert 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 Control Expert - PLC connection status. A DTM can connect to
its device and transfer configuration information over the network in either direction
under both conditions: Control Expert off-line or Control Expert 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).

33003101.26 265
 FDT Container

DTM Hardware Catalog

Object of the Section
This section explains the DTM Hardware Catalog.

Introduction to the Hardware Catalog

Introduction
The Control Expert Hardware Catalog contains a list of modules and devices that you can
add to a Control Expert project. EtherNet/IP and Modbus TCP devices are located in the
DTM Catalog tab at the bottom of the Hardware Catalog. Each module or device in the
catalog is represented by a DTM that defines its parameters.

EDS Files
Not all devices in today’s market offer device-specific DTMs. Some devices are defined by
device-specific EDS files. Control Expert displays EDS files in the form of a DTM. In this
way, you can use Control Expert to configure devices that are defined by an EDS file in the
same way you would configure a device defined by its DTM.
Other devices lack both a DTM and an EDS file. Configure those devices by using the
generic DTM on the DTM Catalog page.

View the Hardware Catalog

Open the Control Expert Hardware Catalog:

Step Action

1 Open Control Expert.

2 Find the PLC bus in the Project Browser.

3 Use one method to open the catalog:

• Use the pull-down menu (Tools > Hardware Catalog).
• Double-click an empty slot in the PLC bus.

266 33003101.26
FDT Container

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.26 267
 FDT Container

Add DTMs to Connectivity Tree

There are 2 ways to add DTMs to a DTM connectivity tree:
• By using the Add device, page 293 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

268 33003101.26
FDT Container

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

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, page 305 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, page 270 to
update its properties information.

33003101.26 269
 FDT Container

Update Hardware Catalog

The DTM catalog is fully embedded in the Control Expert software and requires to be up to
date whenever a DTM is installed or unistalled. It can be done:
• automatically when the Control Expert software is launched in closed project mode
• or manually, from the Hardware Catalog window, anytime the customer requests an
update.
When the Control Expert 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 Control Expert 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:

270 33003101.26
FDT Container

Step Action

1 From the hardware Catalog, page 270, click on the Update button.

Results: The dialog box update opens:

2 Click on the Yes button.

Results: The standard Control Expert 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.

DTM Version Compatibility

The compatibility of DTM versions is managed by the vendor. They cannot be managed in
Control Expert.
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 Control Expert application
• Run the Check devices, page 289 service from the HostPS contextual menu

Adding a DTM to the Control Expert Hardware Catalog

A Manufacturer-Defined Process
Before a DTM can be used by the Control Expert Hardware Catalog, install the DTM on the
host PC (the PC that is running Control Expert).

33003101.26 271
 FDT Container

The installation process for the DTM is defined by the device manufacturer. Consult the
documentation from the device manufacturer to install a device DTM on your PC.
NOTE: After a device DTM is successfully installed on your PC, update the Control
Expert Hardware Catalog to see the new DTM in the catalog. The DTM can then be
added to a Control Expert project.

Adding an EDS File to the Hardware Catalog

Introduction
You may want to use an EtherNet/IP device for which no DTM is in the catalog. In that case,
use these instructions to import the EDS files into the catalog to create a corresponding
DTM.
Control Expert includes a wizard you can use to add one or more EDS files to the Control
Expert Hardware Catalog. The wizard presents instruction screens to execute these
commands:
• Simplify the addition of EDS files to the Hardware Catalog.
• Provide a redundancy check when you add duplicate EDS files to the Hardware
Catalog.
NOTE: The Control Expert Hardware Catalog displays a partial collection of DTMs and
EDS files that are registered with the ODVA. This library includes DTMs and EDS files
for products that are not manufactured or sold by Schneider Electric. The non-Schneider
Electric EDS files are identified by vendor in the catalog. Please contact the identified
device’s manufacturer for inquiries regarding the corresponding non-Schneider Electric
EDS files.

Adding EDS Files

Open the EDS Addition dialog box:

Step Action

1 Open a Control Expert project that includes an Ethernet communication module.

2 Open the DTM Browser (Tools > DTM Browser).

3 In the DTM Browser, select a communication module.

4 Right-click on the communication module and scroll to Device menu > Additional functions > Add
EDS to library.

5 In the EDS Addition window, click Next.

272 33003101.26
FDT Container

You can now see this page:

Add one or more EDS files to the library:

Step Action

1 Use these commands in the Select the Location of the EDS File(s) area of the EDS Addition dialog
box to identify the location of the EDS files:
• Add File(s): Add one or more EDS files that are individually selected.
• Add all the EDS from the Directory: Add all files from a selected folder. (Check Look in
Subfolders to add EDS files from the folders within the selected folder.)

2 Click Browse to open a navigation dialog box.

3 Select the location of the EDS file(s):

• Navigate to at least one EDS file.
• Navigate to a folder that contains EDS files.
NOTE: Keep the location selected (highlighted).

4 Click Select to close the navigation window.

NOTE: Your selection appears in the Directory or File Name field.

33003101.26 273
 FDT Container

Step Action

5 Choose the naming convention rule for the EDS DTM name creation.

The new naming convention is based on Model Name / Product Name and Revision. A random
character is automatically suffixed when Model Name / Product Name and Revision of an EDS file in
the library is identical. The new naming convention is irrespective of the order in which EDS files are
added to device library.

By default, the New Naming Convention check box is selected and the new naming rule applies.
NOTE: To keep backward compatibility with Unity Pro/Control Expert versions, unchecked the
New Naming Convention check box and the naming rule is based on Model Name / Product
Name.
6 Click Next to compare the selected EDS files to the files in the library.
NOTE: If one or more selected EDS files is a duplicate, a File Already Exists message appears.
Click Close to hide the message.

7 The next page of the EDS Addition wizard opens. It indicates the status of each device you
attempted to add:

• check mark (green): The EDS file can be added.

• informational icon (blue): There is a redundant file.

• exclamation point (red): There is an invalid EDS file.

NOTE: You can click View Selected File to open and view the selected file.

8 Click Next to add the non-duplicate files.

Result: The next page of the EDS Addition wizard opens to indicate that the action is complete.

9 Click Finish to close the wizard.

Result: The hardware catalog automatically updates.

Removing an EDS File from the Hardware Catalog

Introduction
You can remove a module or device from the list of available devices in the Control Expert
Hardware Catalog by removing its EDS file from the library.
When you remove an EDS file from the library, the device or module disappears from the
DTM Catalog. However, removing the file from the library does not delete the file from its
stored location, so you can import the file again later.

274 33003101.26
FDT Container

Removing an EDS File from the Catalog

Use these steps to remove an EDS file from the catalog:

Step Action

1 Open the Control Expert DTM Browser (Tools > DTM Browser).
2 In the DTM Browser, select an Ethernet communication module.

3
Right-click the module and scroll to Device menu > Additional functions > Remove EDS from
library to open the EDS Deletion from Device Library window:

4 Use the selection lists in the heading of this window to specify how EDS files are displayed:

Display Choose criteria to filter the list of EDS files:

• All EDS (no filtering)
• Only Devices
• Only Chassis
• Only Modules

Sort by Choose criteria to sort the list of displayed EDS files:

• File Name
• Manufacturer
• Category
• Device Name
Displayed Name Choose the identifier for each device:
• Catalog Name
• Product Name

33003101.26 275
 FDT Container

Step Action

5 Expand (+) the Device Library navigation tree and select the EDS file you want to remove.
NOTE: Click View Selected File to see the read-only contents of the selected EDS file.

6 Click the Delete Selected File(s) button to open the DeleteEDS dialog box.

7 Click Yes to remove the selected EDS file from the list.
8 Repeat these steps for each EDS file you want to delete.

9 Click Finish to close the wizard.

Result: The hardware catalog automatically updates.

Export / Import EDS Library

Introduction
To use the same project on two Control Expert installations (for example a source, and a
target Host PCs), you may have to update the DTM Hardware Catalog of the target Host
PC.
Instead of adding one by one the missing EDS files in the target Host PC, you can update
the DTM Hardware Catalog in two steps:
• Exporting the EDS library from the source Host PC.
• Importing the EDS library in the target Host PC.
NOTE: When you export the EDS library, the software generates an .DLB file which
contains all the DTM created form EDS files.

Exporting EDS Library

Open the Export EDS Library dialog box:

Step Action

1 Open a Control Expert project that includes an Ethernet communication module.

2 Open the DTM Browser (Tools > DTM Browser).

3 In the DTM Browser, select a communication module.

276 33003101.26
FDT Container

Step Action

4
Right-click on the communication module and scroll to Device menu > Additional functions >
Export EDS library to open the Export EDS library window:

5 For the archived EDS library you want to create:

• Enter the full folder path along with the file name in the Enter / Select EDS Library File Name
field, or
• Click Browse to open a navigation dialog box:
◦ Select the location, and
◦ Enter the file name, and
◦ Click Save to close the navigation window and your selection appears in the Enter / Select
EDS Library File Name field.

6 Click Export to create the archived EDS library.

Result: A new wizard opens to indicate that the export is complete. Click Ok to close the wizard.

7 In the Export EDS library window, click Close.

Importing EDS Library

Use these steps to import an archived EDS library:

Step Action

1 Open the Control Expert DTM Browser (Tools > DTM Browser).
2 In the DTM Browser, select an Ethernet communication module.

33003101.26 277
 FDT Container

Step Action

3
Right-click the module and scroll to Device menu > Additional functions > Import EDS library to
open the Import EDS library window:

4 For the archived EDS library you want to import:

• Enter the full folder path along with the file name in the Enter / Select EDS Library File Name
field, or
• Click Browse to open a navigation dialog box:
◦ Select the location, and
◦ Enter the file name, and
◦ Click Save to close the navigation window and your selection appears in the Enter / Select
EDS Library File Name field.

5 Click Import.

Result: A new wizard opens to indicate that the export is complete. Click Ok to close the wizard.

6 In the Import EDS library window, click Close.

278 33003101.26
FDT Container

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.

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

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

33003101.26 279
 FDT Container

The root of the DTM Browser is HostPC, which is the PC platform for the Control Expert
project.

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

280 33003101.26
FDT Container

The following illustration is a connectivity tree:

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.

33003101.26 281
 FDT Container

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, page 306 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.

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 Control Expert 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, page 302.
Examples:
• For a communication DTM
<1> My =S= PRM COMM, where 1 is the references number.

282 33003101.26
FDT Container

• 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.

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.26 283
 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 Control Expert, such devices are identified with a specific green label in the DTM
browser:

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

284 33003101.26
FDT Container

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
Control Expert browser. It uses products that belong natively to the Control Expert
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 Control Expert and the device DTM.

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

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 Control Expert software, they mainly bring two particularities:
• They use new Control Expert mechanisms to be integrated into the Control Expert
hardware catalog.
• They are managed by Control Expert Ethernet I/O bus editors as for any X80 I/O
modules.
A green “R” icon indicates that the device or module is a Ready one.

33003101.26 285
 FDT Container

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 Control Expert 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 Control Expert connection
to a PLC (Off-line or On-line). DTMs can be connected/disconnected while Control
Expert is either Off-line or On-line.

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:

286 33003101.26
FDT Container

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.26 287
 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

288 33003101.26
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

Host PC
The Host PC contextual menu:

The HostPC contextual menu has the following items:

Name Description

Add...(1) The Add dialog box opens, a version of the Hardware Catalog, allowing the
selection of a Communication DTM.
Check DTM devices(1) This function checks the current project for invalid or non-PC-installed DTMs. Refer
to Check DTM devices, page 290 below.

DTM Services(1) 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, page 291
below.

33003101.26 289
 FDT Container

Name Description

DTM Hardware Catalog This function open the DTM catalog tab in the Hardware Catalog.
(1)

Expand all(2) All DTMs in the project are shown.

Collapse all(2) Only the Commutation DTMs in the project are shown.

(1) This function is available via the Edit menu.

(2) This function is similar to Project Browser Expand/Collapse all, page 163.

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.

290 33003101.26
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 attached DTMs
selection 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 To select either all DTMs added in the project or none.

33003101.26 291
 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.

292 33003101.26
FDT Container

Communication and Other DTMs

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

The DTM contextual menu has the following items:

33003101.26 293
 FDT Container

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 box, 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, page 296 below

Delete(1) 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.
NOTE: If the DTM you want to delete is a Gateway, and is not installed on the
Host PC:
• It is possible to delete the DTM only if no devices are configured under
the Gateway.
• If devices are configured under the Gateway, it is not possible to delete
these devices nor the DTM Gateway.

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, page 297 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.

Connect(1) This connects the DTM to its physical device on the network. This connection does
not depend on the PLC online/offline status of the Control Expert project
application.

Connecting a Gateway- or Device-DTM implicitly connects its parent DTM.

While the device is connected, Connect is not available.

Disconnect(1) This disconnects the DTM from its physical device. This disconnection does not
depend on the PLC online/offline status of the Control Expert project application.

Disconnecting a DTM implicitly disconnects all its child DTMs.

While the device is disconnected, Disconnect is not available.

Load data from device(1) 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.

294 33003101.26
FDT Container

Name Description

Store data to device(1) 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 Control Expert application and download the new version of the
application to the PLC

Device Menu The functions in this menu are vendor dependent, such as:
• Compare (the online and offline parameters)
• Diagnostic (displays a diagnostic screen)
• Print (HTML)
• Observe
• Additional functions available when selecting the communication DTM:
◦ EDS file (add, or remove)
◦ EDS library (export, or import)
◦ Online Action
◦ Explicit Message (Ethernet or Modbus)
◦ Store configuration of devices to the FDR server
◦ About
◦ Advanced Mode(4)
When configuring a DTM, the changes are validated in Control Expert 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, page 305 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 in(1),(2) This displays only the selected DTM node and its child DTMs.

While zoomed-in, Zoom in is not available.

Zoom out(1),(2) This returns to the full display of the DTM connectivity tree.

While there is a full display, Zoom out is not available.

Expand all(3) This displays all DTMs below the selected DTM.

33003101.26 295
 FDT Container

Name Description

Collapse all(3) This displays only the selected DTM.

(1) This function is available via the Edit menu.

(2) This function is similar to Project Browser Zoom in/out, page 160.

(3) This function is similar to Project Browser Expand/Collapse all, page 163.

(4) Advanced option are available DTM configuration screen

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, page 270 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, page 268.

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 Control Expert (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.

296 33003101.26
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, page 299 is
displayed listing the scanned and matched devices. Select the matched devices to be created in the
Control Expert project.

33003101.26 297
 FDT Container

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).

298 33003101.26
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 Control Expert project (which then shows up in the Selected Devices list:

33003101.26 299
 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 Control Expert
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
Control Expert project
• In the Matched Devices list, the device will be assigned an address identical to one of the
DTMs in the Control Expert 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 Control Expert project.

If there are one or more devices in the Selected Devices list that have the same address in the
Control Expert project, a message box opens asking if you want to continue.

If you click OK, all devices in the Control Expert 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

300 33003101.26
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, page 289.

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 Control Expert 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, page 282 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 Control Expert
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 Control Expert
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.

33003101.26 301
 FDT Container

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.

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 Control Expert 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 Control Expert 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, page 306
• In the DTM Browser by clicking on the selected DTM or using the F2 shortcut with the
selected DTM.

302 33003101.26
FDT Container

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:

Changing the Alias name automatically changes the names of the Input/Output Types and
Variables:

33003101.26 303
 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

Control Expert 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.

304 33003101.26
FDT Container

DTM Properties Tabs

About this Section
This section explains the different versions of the Properties of dialogs.

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

33003101.26 305
 FDT Container

General
The General tab:

NOTE: The Alias name (and the DTM Tag name if the vendor allows it) can be changed,
page 302 here or in the DTM Browser.

306 33003101.26
FDT Container

Device Information
The Device Information tab:

33003101.26 307
 FDT Container

DTM Information
The DTM Information tab:

308 33003101.26
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.

33003101.26 309
 Type Library Manager

Type Library Manager

What’s in This Chapter
Libset (Set of Libraries) .......................................................... 310
Overview of the Type Library Manager..................................... 313
Type Library Manager ............................................................ 314
Description of the Type Library Manager.................................. 317
Loading an object from the library into the project .................... 323
Transferring an object from the project into the library ............... 326
Creating a new library and family............................................. 328
Creating an installable family .................................................. 330
Updating a family of a library................................................... 332
Consistency Check Assistant.................................................. 334
Library Version Management .................................................. 337
Using the type library of an older Unity Pro/Control Expert
Version ................................................................................. 341

Object of this section

This chapter describes the main functions of the 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.

Libset Versions
The Libset V10.0 and later are automatically installed with Control Expert.
To install previous Libset versions, start Programs > EcoStruxure Control Expert >
Install libset tool.

310 33003101.26
Type Library Manager

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.
NOTE: At opening time, if the Libset version is missing, a pop-up message appears.
You can use the Installer libset tool to setup one or several Libsets.
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 Unity Pro 4.0 Project from Unity Pro 6.0
to 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 is
generate the STA file is automatically selected. If the respective Libset version is not
automatically selected. If the installed, the latest version will be used.
respective Libset version is 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.

Modifying the Libset Version

Opening an existing project, page 71 (STU file) or an archived project (STA file) you can
select the Libset version.
The Open dialog provides the following options.

33003101.26 311
 Type Library Manager

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, page 337.
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.

Libset Information
If no project is opened, information is displayed on the latest Libset.

312 33003101.26
Type Library Manager

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 is provided in the General
tab of the Properties of Project dialog.
In the Project Browser of Control Expert right-click Project and select Properties from the
context menu. In the General tab you 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, page 316.

Overview of the Type Library Manager

Principle
The Control Expert Library contains all available objects to develop an automation project.
These objects may be the following functions or variables:

33003101.26 313
 Type Library Manager

• 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,
page 334 will support complex operations. This Assistant becomes available during loading,
transfers, or deletions.

List of available functions

The Control Expert 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 337.

Type Library Manager

At a Glance
Control Expert 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, page 323.

314 33003101.26
Type Library Manager

• Transferring an object of the project into the library, page 326.

• 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.

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.

33003101.26 315
 Type Library Manager

Area Description

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 323).
• Help
Click this button to call up the dialog help.

Information
Click the Information button to open the Libset Information window.

The table below describes the various functions offered.

316 33003101.26
Type Library Manager

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

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.

33003101.26 317
 Type Library Manager

Tab All Types tab

Elements of the All Types tab:

Element Description

Click this button to update the display corresponding to the filter term defined in the
Button Name field.

Click this button to open a dialog box, page 430 for defining the filters.
Button

318 33003101.26
Type Library Manager

Element Description

Click this button to invert the filter. The button changes from = to <> and vice versa.
Button

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 315.

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.

33003101.26 319
 Type Library Manager

Variable Types tab

Elements of the Variable Types tab:

Element Description

Click this button to update the display corresponding to the filter term defined in the
Button Name field.

Click this button to open a dialog box, page 430 for defining the filters.
Button

Click this button to invert the filter. The button changes from = to <> and vice versa.
Button

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.

Name (Column) This column displays the names of the function types and function block types and
their formal parameters (inputs, outputs).

320 33003101.26
Type Library Manager

Element Description

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 315.

Tab FFB Types

Elements of the FFB Types tab:

Element Description

Click this button to update the display corresponding to the filter term defined in the
Button Name field.

Click this button to open a dialog box, page 430 for defining the filters.
Button

33003101.26 321
 Type Library Manager

Element Description

Click this button to invert the filter. The button changes from = to <> and vice versa.
Button

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 315.

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 328.

322 33003101.26
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 323).

Customize Columns... Using this menu command you can:

• define the columns, page 1228 to be displayed and
• define the sequence, page 1228 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 Library This menu command enables you to compare all FFB types of a project
with the FFB types of the libraries and update them, if necessary.
Compare to Library Version Management, page 337

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.

33003101.26 323
 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.

2 Click on Access Assistant to open the Help window for loading.

324 33003101.26
Type Library Manager

Step Action

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.

33003101.26 325
 Type Library Manager

Loading requirements
If the name of the object in the project ... then...

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, page 334 will ask

you to confirm before loading.

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.

326 33003101.26
Type Library Manager

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.

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.

33003101.26 327
 Type Library Manager

If the name of the object in the library ... then...

exists and the objects are identical. no action is required because the objects are identical.

exists and only the codes of the objects are the transfer will only be executed if the version of the object to
different. be transferred matches or is higher than the version of the
object that currently exists in the library.

Note: The Consistency Check Assistant, page 334 will ask for
a confirmation before executing the transfer.

exists and only the prototypes of the objects are the transfer will be stopped and not performed, and a
different. message listing the causes will be displayed.

Note: To load this object you must rename it and restart the
loading process.

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, page 330 to reuse,
page 332 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.
Control Expert provides a User-defined Library. This library contains the family custom
FAMILY; however, it does not contain objects at this time.

328 33003101.26
Type Library Manager

Create a new library

Step Action

1 In the Tools menu, select the Type Library Manager option.

Result: The following window will be displayed.

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.

33003101.26 329
 Type Library Manager

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.

Creating an installable family

Introduction
The user-defined library can be saved in a file. It can then be imported into another
programming device.

330 33003101.26
Type Library Manager

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 Control Expert installations, refer to Updating
a family of a library, page 332.

33003101.26 331
 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 Control Expert before updating.

Procedure
Step Action

1 Select Start > Programs > EcoStruxure Control Expert > Types Library Update.
The Types 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. V14.0) you want to update.

(To change the Library path please refer to Library configuration options, page 589.)

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 Control Expert, you must
proceed as described above for each Libset version.

332 33003101.26
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 Control Expert.
You have also copied DFBs and/or DDTs into the family in Control Expert.
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 Control Expert

installations
If you want to use user-defined families with EF/EFBs in other Control Expert installations,
proceed as follows:

Step Action

1 Use your user-defined family (e.g. ToolKit family) to create an installable family, page 330.

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 Control Expert installation.

3 Install the family you exported in Step 1via Start > Programs > EcoStruxure Contro lExpert >
Types Library Update.

Result: Since the original family from the EFB toolkit and the installable family from Control
Expert 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 Control Expert, you must
proceed as described above for each Libset version.

33003101.26 333
 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, page
423.

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)

334 33003101.26
Type Library Manager

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.

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.

33003101.26 335
 Type Library Manager

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.

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.

336 33003101.26
Type Library Manager

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.

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).

33003101.26 337
 Type Library Manager

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.

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 library.

Update

Button Updates all FFB types shown in this tab with the FFB types from the
library.
Update All

338 33003101.26
Type Library Manager

Element Description

Button Closes the window.

OK
Button Opens Control Expert 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.

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 library.

Update

Button Updates all FFB types shown in this tab with the FFB types from the
library.
Update All

33003101.26 339
 Type Library Manager

Element Description

Button Closes the window.

OK
Button Opens Control Expert 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.

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

340 33003101.26
Type Library Manager

Element Description

Button Closes the window.

OK
Button Opens Control Expert Help

Help

Using the type library of an older Unity Pro/Control

Expert Version
At a Glance
NOTE:
Unity Pro is the former name of Control Expert for version 13.1 or earlier.
If you have already used an older version of Unity Pro/Control Expert, 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 Control Expert.

Providing the type library and families

Follow the steps below to install a new version of Control Expert:

Step Action

1 Start the Unity Pro/Control Expert 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 Control Expert.

5 Go to Programs > Schneider Electric > EcoStruxureControlExpert > Control Expert 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 Control Expert software.

33003101.26 341
 Type Library Manager

Step Action

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 Control Expert Version.

342 33003101.26
33003101.26 343
Data Editor
What’s in This Part
Description of the Data Editor ................................................. 345
Creating derived data types (DDT) .......................................... 352
Creating data types of user function blocks (DFB) .................... 374
Managing of instances of data belonging to the family of
function blocks (EF) ............................................................... 376
Managing variable instances belonging to the EDT/DDT/
IODDT/Device DDT families ................................................... 386
General Functions ................................................................. 421

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.

344 33003101.26
Description of the Data Editor

Description of the Data Editor

What’s in This Chapter
Data Editor Access ................................................................ 345
Description of Data Editor tabs................................................ 347

Object of this chapter

This chapter gives an overview 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.

33003101.26 345
 Description of the Data Editor

Accessing the Data Editor

Structural view of a project:

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.

346 33003101.26
Description of the Data Editor

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.

Description of Data Editor tabs

Data Editor Elements
Appearance:

Description:

Element Description

Filter
Clicking on this button updates the display corresponding to the filter term defined in the
Button name field.

33003101.26 347
 Description of the Data Editor

Element Description

Clicking on this button opens a dialog box, page 430 for defining the filters.
Button

Clicking on this button inverts the filter. The button changes from = to <> and vice versa.
Button

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

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, page 421.

348 33003101.26
Description of the Data Editor

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.26 349
 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).

350 33003101.26
33003101.26 351
 Creating derived data types (DDT)

Creating derived data types (DDT)

What’s in This Chapter
Access to derived data types (DDT) ........................................ 352
Creation of a derived data type (DDT)...................................... 353
Administration of derived data types and their elements ............ 364
Creating Nested Derived Data Types....................................... 366
Save Derived Data Types (DDT) ............................................. 371

Object of this chapter

This chapter guides the user through the creation and management of 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.

352 33003101.26
Creating derived data types (DDT)

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.

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.

33003101.26 353
 Creating derived data types (DDT)

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:

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:

354 33003101.26
Creating derived data types (DDT)

Step Action

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):

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.

33003101.26 355
 Creating derived data types (DDT)

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).

2
Call up the newly created structure by clicking on +:

356 33003101.26
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. 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.

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:

33003101.26 357
 Creating derived data types (DDT)

Step Action

Here below is the Bit Rank dialog box:

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.

358 33003101.26
Creating derived data types (DDT)

Result: The structure was successfully analyzed (the symbol in front of the array type has
changed):

33003101.26 359
 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 <Application> directory for a derived type already in the application
◦ the <EDT> directory for an elementary type
◦ the <GDT> directory (displayed but not applicable here)
◦ the <Libset> directory for a derived type archived in a library

360 33003101.26
Creating derived data types (DDT)

Step Action

4 Confirm with OK.

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.

33003101.26 361
 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.

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.

362 33003101.26
Creating derived data types (DDT)

In <Application>, select MyRefInt:

After confirming with OK and performing an Analyze Type, you obtain an array of
references:

Structure with References

This example shows the creation of an array of reference type variables:

33003101.26 363
 Creating derived data types (DDT)

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:

Administration of derived data types and their

elements
Inserting an element into a derived data type
Execute the following steps:

364 33003101.26
Creating derived data types (DDT)

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.

33003101.26 365
 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.

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

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

366 33003101.26
Creating derived data types (DDT)

Step Action

• 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.26 367
 Creating derived data types (DDT)

Array of the type PERSONNEL that contains structures of the type IDENTITY:

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

368 33003101.26
Creating derived data types (DDT)

Step Action

The following window appears.

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:

33003101.26 369
 Creating derived data types (DDT)

Step Action

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.

Example: IDENTITY structure that contains an INFORMATION structure of the STATUS

type.

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

370 33003101.26
Creating derived data types (DDT)

Example:

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:

33003101.26 371
 Creating derived data types (DDT)

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.

Restoring a data type in the library

See loading an object from the library., page 323

372 33003101.26
33003101.26 373
 Creating data types of user function blocks (DFB)

Creating data types of user function blocks

(DFB)
What’s in This Chapter
Creation and Management of Data Types and Function
Blocks (DFB) ......................................................................... 374

Object of this chapter

This chapter guides the user through the creation and management of user function block
data types.

Creation and Management of Data Types and

Function Blocks (DFB)
At a Glance
See Derived Function Blocks (DFB), page 1247.
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

374 33003101.26
33003101.26 375
 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)
What’s in This Chapter
Creating / Deleting a variable instance of function blocks
(EFB/DFB) ............................................................................ 376
Displaying function block variable instances in the
editor .................................................................................... 379
Changing the attribute for variable instances in a function
block..................................................................................... 382

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).

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

376 33003101.26
Managing of instances of data belonging to the family
of function blocks (EF)

Steps Actions

The following window appears:

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.

33003101.26 377
 Managing of instances of data belonging to the family
of function blocks (EF)

Steps Actions

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.

378 33003101.26
Managing of 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.

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.

33003101.26 379
 Managing of instances of data belonging to the family
of function blocks (EF)

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

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:

380 33003101.26
Managing of instances of data belonging to the family
of function blocks (EF)

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

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.

33003101.26 381
 Managing of instances of data belonging to the family
of function blocks (EF)

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 430.

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.

382 33003101.26
Managing of instances of data belonging to the family
of function blocks (EF)

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", page 425

click the button window.

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.

33003101.26 383
 Managing of instances of data belonging to the family
of function blocks (EF)

• 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.

384 33003101.26
33003101.26 385
 Managing variable instances belonging to the EDT/
DDT/IODDT/Device DDT families

Managing variable instances belonging to the

EDT/DDT/IODDT/Device DDT families
What’s in This Chapter
Creation of EDT instances ...................................................... 386
Creation of DDT instances ...................................................... 390
Creating an IODDT instance ................................................... 396
Managing a Device DDT instance ........................................... 399
Managing an IODDT, DDT or an Array type instance................. 403
Creation of multiple variable instances..................................... 409
Displaying the variable instances in the editor .......................... 411
Changing attributes of variable instances................................. 414
Creation of a Reference Type Instance .................................... 418

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)

Creation of EDT 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.

386 33003101.26
Managing variable instances belonging to the EDT/
DDT/IODDT/Device DDT families

Example:

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, page 388 of the variable instance.

Example:

33003101.26 387
 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:

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.

388 33003101.26
Managing variable instances belonging to the EDT/
DDT/IODDT/Device DDT families

NOTE: Several different instances can be assigned to one address (multiple

assignment).
Example:

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:

33003101.26 389
 Managing variable instances belonging to the EDT/
DDT/IODDT/Device DDT families

Creation of DDT 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.

390 33003101.26
Managing variable instances belonging to the EDT/
DDT/IODDT/Device DDT families

Step Action

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.

Example:

NOTE: The comments will be transferred to the selected structure type, but they may be
changed for the applicable instance.

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:

33003101.26 391
 Managing variable instances belonging to the EDT/
DDT/IODDT/Device DDT families

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.

392 33003101.26
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.

33003101.26 393
 Managing variable instances belonging to the EDT/
DDT/IODDT/Device DDT families

Example:

NOTE: Enter comments for the sub-elements of this instance of a non-typical array.

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

394 33003101.26
Managing variable instances belonging to the EDT/
DDT/IODDT/Device DDT families

Step Action

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.

33003101.26 395
 Managing variable instances belonging to the EDT/
DDT/IODDT/Device DDT families

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.

Creating an IODDT 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 an 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

396 33003101.26
Managing variable instances belonging to the EDT/
DDT/IODDT/Device DDT families

Step Action

The following window appears.

4 In the Library/Family area, display the <Catalog> index.

The following window appears.

33003101.26 397
 Managing variable instances belonging to the EDT/
DDT/IODDT/Device DDT families

Step Action

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:

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.

398 33003101.26
Managing variable instances belonging to the EDT/
DDT/IODDT/Device DDT families

Step Action

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.

Managing a Device DDT instance

Device DDT Instance
When adding a module to a rack, Control Expert software instantiates the associated device
DDT structure. The main family of modules concerned by device DDT is the I/O modules
family, some specific modules are also concerned. The device DDT name syntax is
explained in the section on Device DDT Naming Rule (see EcoStruxure™ Control Expert,
Program Languages and Structure, Reference Manual).
Each module is associated with one implicit device DDT instance.

33003101.26 399
 Managing variable instances belonging to the EDT/
DDT/IODDT/Device DDT families

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 I/O 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 EcoStruxure™ Control Expert, I/O Management, Block Library).

Renaming a Device DDT

The following table describes a way to rename a module device DDT:

Step Action

1 In the Project Browser, double-click the module that contains the device DDT to rename.

2 In the module window, select the Device DDT tab.

3 Select the module (not the channel).

4 Modify the device DDT name.

NOTE: The total name length is limited to 32 characters.
NOTE: A name needs to be unique in an application.

5 Validate the name changes in the advice window. This advice window appears when selecting
another tab or view.

WARNING
UNEXPECTED EQUIPMENT BEHAVIOR
• Always verify that the Control Expert configuration is consistent with the hardware
installation.
• If you attempt to change the default names of your devices, manage the naming to
prevent from addressing the wrong device.
Failure to follow these instructions can result in death, serious injury, or equipment
damage.

Copying and Pasting a Module

During a module copy/paste action, the pasted module respects the default naming rule
linked to its topological location.

400 33003101.26
Managing variable instances belonging to the EDT/
DDT/IODDT/Device DDT families

Moving a Module
Moving a module does not modify its name.
If the same module type is inserted in the slot freed by the module shifting, the new inserted
module should get the same topological name. In order to keep the naming uniqueness,
_rrrrrr is added at the end of the string (rrrrrr being a random character series).

Replacing a Hot Standby CPU

Replacing a Hot Standby CPU does not modify the device DDT name of the CPU.

Checking the Device DDT Owner

When a module is moved or a Device DDT is renamed, it may be difficult to locate the
module in the architecture. This information is provided in the Owner column of the Data
Editor. Displayed columns are configured, page 421 as needed.

Creating a Device DDT Instance

Perform the following steps to create a Device DDT instance:

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 corresponding Type field and click the following button:

Results: The Variable Type Selection dialog appears.

4 In the Libraries/Families area, display the <Libset vx.y> index.

Where x.y indicates the Control Expert software version.

5 Select the family (I/O Management for example) and the corresponding Device DDT type.

6 Confirm with OK.

33003101.26 401
 Managing variable instances belonging to the EDT/
DDT/IODDT/Device DDT families

Example: Instance ANA_OUT of type T_U_ANA_STD_OUT_8:

Linking a Device DDT Instance to a Module

Use the following procedure:

Step Action

1 Create a Device DDT as explained previously.

2 In the Project Browser, double-click the module to be associated to the created device DDT.
NOTE: The created device DDT can only be linked to a module of the same type. For
example, an 8 analog input module can only be linked to an 8 analog input device DDT.

3 In the module window, select the Device DDT tab.

4 Select the module (not the channel).

5 In the Implicit device DDT > Name : list, select the name of the device DDT created (instead
of the current name).

402 33003101.26
Managing variable instances belonging to the EDT/
DDT/IODDT/Device DDT families

Step Action

6 Validate the name changes in the advice window. This advice window appears when selecting
another tab or view.
NOTE: Once a module is linked to a new device DDT, the variables that were linked to
former device DDT name do not address the module anymore.

7
The previously created Device DDT instance is now linked to the module. It is displayed as
follows in the data editor:

NOTE: A variable linked to a module shows a lock in front of its name in the data
editor.

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.

33003101.26 403
 Managing variable instances belonging to the EDT/
DDT/IODDT/Device DDT families

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:

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.

404 33003101.26
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:

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.

NOTE: The user can directly enter the AliasValue in the Alias column.

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.

33003101.26 405
 Managing variable instances belonging to the EDT/
DDT/IODDT/Device DDT families

Example:

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:

406 33003101.26
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:

3 Double-click on the target alias, delete the element in edit mode (AliasValue) and confirm.

The symbols shown on the element disappear:

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.

33003101.26 407
 Managing variable instances belonging to the EDT/
DDT/IODDT/Device DDT families

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.

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)

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).

408 33003101.26
Managing variable instances belonging to the EDT/
DDT/IODDT/Device DDT families

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:

33003101.26 409
 Managing variable instances belonging to the EDT/
DDT/IODDT/Device DDT families

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.

5 From the context menu select the command Insert and the new instances will be created and renamed.

Example:

410 33003101.26
Managing variable instances belonging to the EDT/
DDT/IODDT/Device DDT families

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", page 1701.

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.26 411
 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.

412 33003101.26
Managing variable instances belonging to the EDT/
DDT/IODDT/Device DDT families

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.26 413
 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 430

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.

414 33003101.26
Managing variable instances belonging to the EDT/
DDT/IODDT/Device DDT families

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

type in the "Variables type
click the button selection", page 425
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).

Changing an attribute in the "Data Properties" field

Carry out the following steps:

33003101.26 415
 Managing variable instances belonging to the EDT/
DDT/IODDT/Device DDT families

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.

416 33003101.26
Managing variable instances belonging to the EDT/
DDT/IODDT/Device DDT families

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.
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).

33003101.26 417
 Managing variable instances belonging to the EDT/
DDT/IODDT/Device DDT families

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.

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.

418 33003101.26
Managing variable instances belonging to the EDT/
DDT/IODDT/Device DDT families

Example of the Data Editor with a reference to a variable:

33003101.26 419
420 33003101.26
General Functions

General Functions
What’s in This Chapter
Configuring the Data Editor columns ....................................... 421
Description of the Data Editor: Variable type selection............... 425
Filtering of Data ..................................................................... 430
Exporting a subset of variables ............................................... 434
Analyze DDT and DFB Data Types .......................................... 435
Purge of Unused Instances..................................................... 436
Local printing of data .............................................................. 437
Save the context of the Data Editor ......................................... 438

Object of this chapter

This chapter guides the user through the use of the general features available in the data
editor.

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 shows the different columns available in the Data Editor:

Column Name Description

Name Name of the instance or data type.

Type Data type. By default this attribute is checked.

Value Initial value for the variables. By default this attribute is checked.

33003101.26 421
 General Functions

Column Name Description

Comment Comment for the variables. By default this attribute is checked.

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. By default this attribute is
checked.
NOTE: An Alias value cannot be set for a variable if the Bit rank attribute has been set,
page 356 for that variable.

Alias of Complete path of the variable subfield on which user sets Alias attribute. By default this
attribute is checked.
Constant Kind of variable, the variable is a constant or not.

Custom Free text for use of an external tool or for special user requirements.

Used Number of times the variables are used in the program and in other parts of the project
(animation tables, user windows).

Owner Only for Device DDT, it displays the address of the modules which owns this variable.

Address Address in the controller for referencing the variables. By default this attribute is checked.

Global data Shows if the variable is a variable that was swapped between different stations via the
network.
+ Group Number of the group (the variables) in which the variable is transported.

ID Number for the unique display of a variable in the group (the variables).

Save Define if the variable accepts the mechanism for updating initial values with current values.

HMI variable When General Project Settings > Data Dictionary > Only HMI variables is checked, this
reduces memory usage. By default this attribute is checked.

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 EcoStruxure™ Control Expert, Applicative Time Stamping, User
Guide).

+ Source Gives the source of the time stamping.

TS ID Gives the ID of the time stamped variable.

Scanned Variables Attribute that you can use to tag a variable to be a scanned variable by the PLC, through
Ethernet for instance.
R/W Rights of Access rights of a reference type instance, used when the reference dereferences a read
Referenced Variable only variable, see the Reference Access rights (see EcoStruxure™ Control Expert, Program
Languages and Structure, Reference Manual). By default this attribute is checked.

Data Protect Use this attribute to protect your data from modification request in monitoring mode.

When Data Protect is checked, it is not possible to modify the protected variable. By default
this attribute is unchecked.
NOTE: The project setting Data memory protect must be enabled: Tools > Project
Settings > PLC embedded data.

422 33003101.26
General Functions

Column Name Description

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 BME•586040 CPUs present this variable attribute, which determines whether the variable
value will persist after a warm start of the CPU. If the attribute is:
• Selected: Variable data persists and is applied to the variable after a warm start.
• De-selected: Variable data is lost after a warm start; the variable value is reset.
For other Modicon M580 CPUs, this attribute is read-only. It is selected by default and
cannot be de-selected.
no. Order number of a function block.
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).

RW program Access rights of the variable, read only or read and write by the program.

Descriptor x 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.

Version Type version.

Bit rank Gives the bit rank of the variable in its structure type.

Nature Only for the Program Unit data editor. Define if the Program Unit variable is an input, output
or Input/output parameter, a public or private variable. By default this attribute is checked.

Effective Parameter Only for the Program Unit data editor. Variable assignment to the program unit parameters
(input, output and input/output parameters).

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.

33003101.26 423
 General Functions

Step Action

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.

424 33003101.26
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 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.

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:

33003101.26 425
 General Functions

Variables:

DDT Types:

426 33003101.26
General Functions

Function blocks:

NOTE: Access to the editor for the selection of the data types is not possible via the
DFB types tab.

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 <GDT> directory shows the types for the generic data,

33003101.26 427
 General Functions

• 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.

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

428 33003101.26
General Functions

REF_TO checkbox
If this checkbox is enabled, you can use the editor to create a reference type instance.
Example: REF_TO BOOL

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, page 431 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.26 429
 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 ?
All tabs Clicking on this button updates the display corresponding to the filter term
Button defined in the name field.

All tabs Clicking on this button opens the Filtering data dialog box where you can
Button define the conditions for the individual attributes.

All tabs Clicking on this button inverts the filter. The button changes from = to <>
Button 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).

430 33003101.26
General Functions

Area In which table is it Purpose

available ?
DFB Function Blocks tab The enabled check box authorizes the display of the Derived Function
Blocks (DFB).

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
attribute contains the word attribute does not contain the
e.g. *motor* Motor are filtered. word Motor are filtered.

Type Free text All variables of data type Int All variables not of data type
are filtered. Int are filtered.

33003101.26 431
 General Functions

Name Condition inverted disabled inverted enabled

e.g. Int

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.
Constant 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-
user-defined text (free text for defined text does not contain
e.g. *HMI* 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
with \2.1\ are filtered. doesn’t begin with \2.1\ are
e.g. \2.1\* filtered.

Address Free text All variables with the address % All variables that do not have
MW1 are filtered. the address %MW1 are filtered.
e.g. %MW1

Global data Yes All variables defined as global All variables not defined as
data are filtered. global data are filtered.

Save Accept All variables that accept saving All variables that do not accept
and restore operations are saving and restore operations
filtered. are filtered.
HMI variable Yes All variables defined as HMI All variables not defined as
variable are filtered. HMI variable are filtered.
Time stamping Free text All variables which Time All variables which Time
stamping attribute is Both stamping attribute is not Both
e.g. Both edges edges are filtered. edges are filtered.

Scanned Variables Yes All variables defined as Scanned 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 are filtered. Exchange On STBY 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:

432 33003101.26
General Functions

Name Condition inverted disabled inverted enabled

Comment Free text All DDT types whose comment All DDT types whose comment
attribute contains the word attribute does not contain the
e.g. *Motor* Motor are filtered. word Motor are filtered.

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
comment attribute contains the comment attribute does not
e.g. *Motor* 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
are filtered. TON are filtered.
e.g. TON

Custom Free text All function blocks are filtered if All function blocks whose user-
their user-defined text (free text defined text does not contain
e.g. *HMI* 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
begins with \2.1\ are filtered. doesn’t begin with \2.1\ are
e.g. \2.1\* 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.
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:

33003101.26 433
 General Functions

Name Condition inverted disabled inverted enabled

Comment Free text All DFB types whose comment All DFB types whose comment
attribute contains the word attribute does not contain the
e.g. *Motor* 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.

Exporting a subset of variables

Introduction
The chapter Import / Export, page 1677 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 430.

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).

434 33003101.26
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:

33003101.26 435
 General Functions

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.

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.

436 33003101.26
General Functions

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.

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.

Local printing of data

Introduction
Printing is a user-defined process and is executed using the following items:
• selected tab,

33003101.26 437
 General Functions

• 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, page 430:
• 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.

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,

438 33003101.26
General Functions

• 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.26 439
440 33003101.26
Communication
What’s in This Part
Presentation of the communication editors............................... 442
Network Configuration............................................................ 445
Configuration of X-Way Routing Premium Stations ................... 453

Subject of this Part

This part describes the communication editors.

33003101.26 441
 Presentation of the communication editors

Presentation of the communication editors

What’s in This Chapter
Presentation of the communication editors of the project
browser................................................................................. 442

Subject of this Chapter

This chapter describes 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.

442 33003101.26
Presentation of the communication editors

Illustration
The figure below shows an example of the project browser

33003101.26 443
444 33003101.26
Network Configuration

Network Configuration
What’s in This Chapter
Network Configuration Principle Using Control Expert .............. 445
Creating a Logic Network ....................................................... 446
Configuring a Logic Network ................................................... 448
Associating a Logic Network with Network Hardware ................ 449

Subject of this Chapter

This chapter presents the tools for configuring a network at the global level and at the station
level.

Network Configuration Principle Using Control

Expert
At a Glance
With Control Expert, 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:

33003101.26 445
 Network Configuration

• Ethernet configuration for Premium (see Premium and Atrium Using EcoStruxure™
Control Expert, 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 (see Modicon M580,
Hardware, Reference Manual),
• Modbus Plus configuration (see Premium and Atrium Using EcoStruxure™ Control
Expert, Modbus Plus Network, User Manual),
• Fipway configuration (see Premium and Atrium using EcoStruxure™ Control Expert,
Fipway Network, User Manual).

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::

446 33003101.26
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.

33003101.26 447
 Network Configuration

Step Action

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.

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 EcoStruxure™
Control Expert, 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 EcoStruxure™ Control
Expert, Modbus Plus Network, User Manual),
• Fipway configuration (see Premium and Atrium using EcoStruxure™ Control Expert,
Fipway Network, User Manual).

Configuring a Logic Network

The table below describes how to access the configuration of a network from the project
browser.

448 33003101.26
Network Configuration

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.

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.

33003101.26 449
 Network Configuration

Step Action

3 Select the channel and function.

Result: For a TSX ETY 4103 module:

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:

450 33003101.26
Network Configuration

Step Action

33003101.26 451
452 33003101.26
Configuration of X-Way Routing Premium Stations

Configuration of X-Way Routing Premium

Stations
What’s in This Chapter
Configuration......................................................................... 454
Configuration of Multi-Network Services .................................. 455
Configuring an X-Way Router Module...................................... 456
Examples of X-Way Routing Stations ...................................... 460
Examples of Partial Routing.................................................... 463

Subject of this Chapter

This chapter presents the operating modes required for configuring X-Way routing Premium
stations.

33003101.26 453
 Configuration of X-Way Routing Premium Stations

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.

454 33003101.26
Configuration of X-Way Routing Premium Stations

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.26 455
 Configuration of X-Way Routing Premium Stations

Elements and Functions

The following table describes the various zones in the configuration screen:

Label Field Function

1 Logical network Used to display the logical network name.

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 as a bridge.

networks
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.

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.

456 33003101.26
Configuration of X-Way Routing Premium Stations

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).

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.

33003101.26 457
 Configuration of X-Way Routing Premium Stations

Step Action

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.

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

458 33003101.26
Configuration of X-Way Routing Premium Stations

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.

33003101.26 459
 Configuration of X-Way Routing Premium Stations

Examples of X-Way Routing Stations

At a Glance
Each station must be configured in order to define the list of accessible networks.

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.

460 33003101.26
Configuration of X-Way Routing Premium Stations

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:

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.

33003101.26 461
 Configuration of X-Way Routing Premium Stations

The bridge configuration of the station is therefore as follows:

Messaging
To use the communication function (see EcoStruxure™ Control Expert, 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
EcoStruxure™ Control Expert, 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.

462 33003101.26
Configuration of X-Way Routing Premium Stations

The following illustration shows the R2 Messaging tab:

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.

33003101.26 463
 Configuration of X-Way Routing Premium Stations

Illustration
Each station must be configured in order to define the list of accessible networks.

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.

464 33003101.26
Configuration of X-Way Routing Premium Stations

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:

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.

33003101.26 465
 Configuration of X-Way Routing Premium Stations

The bridge configuration of the station is therefore as follows:

466 33003101.26
33003101.26 467
Programming
What’s in This Part
Accessing Tasks, Program Units and Sections ......................... 469
Control Expert Software Options ............................................. 546
Common Function for graphical language................................ 607
FBD Editor ............................................................................ 643
LD Editor............................................................................... 737
SFC Editor ............................................................................ 882
Common Function for Textual Language................................ 1009
IL Editor .............................................................................. 1044
ST Editor............................................................................. 1075
LL984 Editor.........................................................................1113
Programming Languages Data Selection Dialog Box .............. 1174
I/O Objects tab..................................................................... 1200
Memory Tab ........................................................................ 1218
Type Library Browser ........................................................... 1224
Search/Replace Tool ............................................................ 1232
User's Function Blocks ......................................................... 1247

Subject of this part

This part describes the programming editors.

468 33003101.26
Accessing Tasks, Program Units and Sections

Accessing Tasks, Program Units and

Sections
What’s in This Chapter
Access to Tasks ..................................................................... 469
Accessing Program Units ....................................................... 472
Accessing Sections................................................................ 499

Overview
This section describes how to access tasks, Program Units and sections.
NOTE: Program Units are not available for Momentum, Quantum, Premium and Atrium.

Access to Tasks
Subject of this Section
This section covers the creation and modification of program tasks.

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 EcoStruxure™ Control Expert, Fipio
Bus, Setup Manual) configuration, the window displayed is different.

33003101.26 469
 Accessing Tasks, Program Units and Sections

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. We recommend to set it at twice
the logic execution time.

8 The Comment tab can be used to add a comment to describe the role of the task for example.

470 33003101.26
Accessing Tasks, Program Units 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 EcoStruxure™ Control Expert, 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.

33003101.26 471
 Accessing Tasks, Program Units and Sections

Step Action

6 Set the Watchdog value which must be greater than the period value. We recommend to set it at twice
the logic execution time.

7 The Comment tab can be used to add a comment to describe the role of the task for example.

Accessing Program Units

Overview
This section describes accessing Program Units for Modicon M580 and M340.

Creating Program Units

Introduction
Create Program Units for Modicon M340:
• in the MAST and FAST tasks
• in offline and online mode
Create Program Units for Modicon M580:
• in the MAST, FAST, AUX0, and AUX1 tasks
• in offline and online mode

Creating a Program Unit

Creating a Program Unit:

Step Action

1 Left-click the Logic 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 Program Unit... in the context menu.

Result: The New dialog box for the Program Unit opens.

3 Enter the name of the Program Unit. It must be unique in the entire project and conform to the
general naming conventions.

472 33003101.26
Accessing Tasks, Program Units and Sections

Step Action

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 Project Protection, page 187.

5 Select the functional module to which the section is allocated from the Localization tab if
necessary.

See also section Functional module, page 232.

6 Define a variable of BOOL or EBOOL type in the Condition tab with which the Program Unit 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 an instance selection dialog box, page 1174.
Only for EBOOL variable, activate the Can be forced check box when you want to force the
variable.
7 Enter a comment in the Comment tab if desired.
8 Confirm the entries with OK and the Program Unit is automatically created in the Logic directory
with the following structure:
• Interface & Variables
• Sections folder
• Animation Tables folder
You can refer to the chapter Animation Tables, page 1467, which refers to the global project,
for the implementation of animation tables in the Program Unit.
NOTE: For the animation tables the accessible variable scope is limited to the Program Unit
scope.

9 Declare the parameters and variables for the Program Unit.

10 Create sections in FBD, LD, IL, ST, page 499 or SFC, page 507.

Displaying or modifying Program Unit properties

Displaying or modifying Program Unit properties:

33003101.26 473
 Accessing Tasks, Program Units and Sections

Step Action

1 Left-click on the desired Program Unit, or place the cursor on this Program Unit with the arrow
keys.

2 Select (right-click or Shift+F10 key combination) the Properties menu command from the shortcut
menu.

Result: The Properties of dialog box for the Program Unit opens.

3 Implement the desired changes.

4 Confirm all entries with OK.

Importing/exporting Program Units

See:
• Importing programs, page 1692
• Exporting programs, page 1690

Properties Dialog Box for Program Units

Structure of the properties dialog box
The properties dialog box consists of four tabs:
• General
Enter the name and the type of access protection of the Program Unit in this tab.
• Localization
You can enter the functional module of the Program Unit in this tab.
• Condition
You can enter a BOOL or EBOOL variable which can enable/disable the Program Unit
in this tab.
• Comment
You can enter a comment in this tab.

474 33003101.26
Accessing Tasks, Program Units and Sections

General tab
Representation of the General tab:

Elements of the General tab:

Element Description

Name Enter the name of the Program Unit in this text box.

The name must be unique in the entire project and conform to the general naming
conventions.
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 Program Unit, Section and Subroutine Protection, page 187.

OK Use this command button to accept the entries and close the properties dialog box.

Apply Use this command button to accept the entries without closing the properties dialog box.

33003101.26 475
 Accessing Tasks, Program Units and Sections

Localization tab
Representation of the Localization tab:

Elements of the Localization tab:

Element Description

Task The task of the Program Unit is displayed in this field.

Functional module Select the functional module to which the Program Unit is to be allocated to in this list
box.

For detail, refer to chapter Functional Modules, page 232.

OK Use this command button to accept the entries and close the properties dialog box.

Apply Use this command button to accept the entries without closing the properties dialog box.

476 33003101.26
Accessing Tasks, Program Units and Sections

Condition tab
Display of the Condition tab:

Elements of the Condition tab:

Element Description

Variable You can enter variable of BOOL or EBOOL type which can conditionally enable/disable
the Program Unit in this tab. The scope to select the variable is a either a global variable,
or a public variable or an output parameter of another Program Unit.

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 an instance selection dialog box, page
1174.
• 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 Use this command button to accept the entries and close the properties dialog box.

Apply Use this command button to accept the entries without closing the properties dialog box.

The animation of the activation condition behavior is provided in the project browser. The
Program Unit and its sections have activation conditions, page 505.
In the project browser, the flag (green for activate, red for inactivate) of the Program Unit and
the sections reflect the variable value of the variable used for their activation.

33003101.26 477
 Accessing Tasks, Program Units and Sections

A section under a Program Unit is executed only if the section is activated and the Program
Unit is activated.

Case: Description

The section Start_process is executed and the

section Weighing_Material is not executed.

The Program1 is not activated, Start_process

and Weighing_Material sections are not
executed.

Comment tab
Representation of the Comment tab:

Elements of the Comment tab:

478 33003101.26
Accessing Tasks, Program Units and Sections

Element Description

Text box A comment about the Program Unit can be entered in this text box.

OK Use this command button to accept the entries and close the properties dialog box.

Apply Use this command button to accept the entries without closing the properties dialog box.

Program Unit Data Scope

Introduction
When Program Units are allowed in programming your application (Modicon M580 and
M340), variables are determined by the scope to which they belong to:

Global variables: They refer to the application wide - or global - scope of data in a project which are:
• Unlocated variable
• Located variable (mapped at %M flat address)

Program Unit variables: They refer to the Program Unit data scope and have one of the following attributes:
• Private: can only be R/W in the scope of this Program Unit.
• Public: can be R/W out of the scope of this Program Unit.
• Parameter (Inputs, Outputs, and Inputs/Outputs): linked to Public variables
(from other Program Units) or Global variables.
• External: Global variables used in this Program Unit.

NOTE: The management of topological variable is only supported in the data editor,
refer to parameter assignment, page 489 to map a variable of a Program Unit to a
topological variable.

33003101.26 479
 Accessing Tasks, Program Units and Sections

Data Scope in Project Browser

1 Global variables, managed via the Data Editor

2 Variables under Program0 scope, managed via the Program Unit Data Editor of the
Program0.
3 Variables under Program1 scope, managed via the Program Unit Data Editor of the
Program1.

480 33003101.26
Accessing Tasks, Program Units and Sections

Variables Accessibility
The variable accessibility is dependent to the scope (Global, Program Unit):

NOTE: System behavior of the PLC is accessible using the system bits and system
words into the Program Unit.

33003101.26 481
 Accessing Tasks, Program Units and Sections

Program Unit Data Editor Access

Introduction
The variables under the scope of a Program Unit can be accessed from the structural view
in the Program Unit data editor. It has features which support the following:
• Creating and declaring variables of different natures,
◦ Parameters (Inputs, Outputs, and Inputs/Outputs)
◦ Public, which can be accessible also from an other Program Unit
◦ External, for global variables used in the Program Unit
◦ Private, only accessible in scope of the Program Unit
• Assigning variables to Program Unit parameters (via effective parameter attribute),
• Searching/sorting/filtering variables.
• Managing of instances of data belonging to the family of function blocks (EFB/DFB).

Accessing the Program Unit Data Editor

Structural view of a project:

Carry out the following steps:

482 33003101.26
Accessing Tasks, Program Units and Sections

Step Action

1 Click the left mouse button on the selected Interface & Variables directory, or place the cursor on
this directory with the arrow keys.

2 Select (right-click or Shift+F10 combination) the Open command from the shortcut menu.

or

Double click on the Interface & Variables.

or

Select Edit > Open.

Result: The Program Unit data editor opens. The Variables tab is shown by default.

Program Unit Data Editor:

Description of Program Unit Data Editor Tabs

Introduction
NOTE: The different fields can be assigned parameters, page 421.

33003101.26 483
 Accessing Tasks, Program Units and Sections

Tab: Variables
The Variables tab enables the management of all the variables that belong to the Program
Unit:

Description:

Element Description

Filter
Clicking on this button updates the display corresponding to the filter term defined in the name
Button field.

Clicking on this button opens a dialog box, page 430 for defining the filters.
Button

Clicking on this button inverts the filter. The button changes from = to <> and vice versa.
Button

Name Column where you enter the name (symbol) of the variable you want to display. You can use the
place holders (* or ? for this.).

EDT Displaying variables with elementary data types

DDT Displaying variables with derived data types

IODDT Display the variables with derived data types (DDT) that reference inputs/outputs

Device DDT Display the variables with device derived data types

Properties

Name Column where you enter the name (symbol) of the variable.

484 33003101.26
Accessing Tasks, Program Units and Sections

Element Description

Type Column where you select the variable type.

Value Column where you initialize the variable.

Comment Column where you enter the comment for the variable.

Alias Column where you can change the name of a variable. Only for <private> variables.

Alias of Column where you enter the complete path of the variable subfield on which you set Alias
attribute.
HMI variable Column where you check if the variable is embedded in the data dictionary.

R/W Rights Column where you set the access rights of a reference type variable.
of
Referenced
variable
Effective Column where you can assign a variable to the Program Unit parameter.
Parameter
Nature Column where you set the nature of the Program Unit variable.

The above properties are displayed by default, for customized properties, refer to Configuring the Data Editor
columns, page 421.

NOTE: For more detailed information, refer to chapter Managing of variables belonging
to the Program Unit, page 488.

Tab: Function Blocks

The Function Blocks tab enables the management of the instance of elementary and
derived function blocks used in the sections of the Program Unit:

Description:

33003101.26 485
 Accessing Tasks, Program Units and Sections

Element Description

Filter
Clicking on this button updates the display corresponding to the filter term defined in the name
Button field.

Clicking on this button opens a dialog box, page 430 for defining the filters.
Button

Clicking on this button inverts the filter. The button changes from = to <> and vice versa.
Button

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.).

EFB Displaying elementary data types

DFB Displaying derived data types

Properties

Name Column where you enter the name (symbol) of the function block instance.

no. Order number of the inputs and outputs of the function block.

Type Column where you select the function block type.

Value Column where you enter the initial value for the variable.

Comment Column where you enter the comment for the variable.

HMI variable Column where you check if the variable is embedded in the data dictionary.

R/W Rights Column where you set the access rights of a reference type variable.
of
Referenced
variable
The above properties are displayed by default, for customized properties, refer to Configuring the Data Editor
columns, page 421.

NOTE: For more detailed information, refer to chapter Managing of instances of date
belonging to the family of function blocks (EF), page 376.

486 33003101.26
Accessing Tasks, Program Units and Sections

Tab: Interface
The Interface tab enables the management of the Program Unit variables sorted by Nature:

NOTE: The <inputs>, <outputs>, <inputs/outputs>, <public> and <external>

variables that belong to the Program Unit are displayed in this tab. These variables can
be declared in this tab and they automatically added in the Variables tab and vice versa.
Description:

Element Description

Properties

Name This column contains the Column where you set the nature of the Program Unit variable.

Column where you enter the name (symbol) of the variable.

Type Column where you select the variable type.

Value Column where you initialize the variable.

Comment Column where you enter the comment for the variable.

Effective Column where you can assign a variable to the Program Unit parameter.
Parameter
HMI variable Column where you check if the variable is embedded in the data dictionary.

The above properties are displayed by default, for customized properties, refer to Configuring the Data Editor
columns, page 421.

33003101.26 487
 Accessing Tasks, Program Units and Sections

Program Unit Variables

Naming Rule
The duplication of a variable name is possible when the variables belong to different scopes:
• Two Program Unit scopes, or
• The global scope and a Program Unit scope.
NOTE: In the same Program Unit scope, the variable name duplication is not allowed.

Variables Definition and Attributes

The following table

Program Definition and access Nature Type allowed

Unit
Variables
Input These parameters are read-only access in <inputs> EDT, DDT, ARRAY, References
parameters the Program Unit. They are used to (REF_TO), Device DDT
transfer values to the Program Unit.

Output These parameters are read/write access in <outputs> EDT, DDT, ARRAY, References
parameters the Program Unit. They are used to (REF_TO), Device DDT
transfer values from the Program Unit.

Input/Output These parameters are read/write access in <inputs/ EDT, DDT, ARRAY, Device
parameters the Program Unit. They are used to outputs> DDT, IODDT
transfer values to and from the Program
Unit.
Public These local variables are accessible from <public> EDT, DDT, ARRAY
variables another Program Unit using the effective
parameter assignment.

Private These local variables are only accessible <private> EDT, DDT, ARRAY, References
variables inside the scope of the Program Unit to (REF_TO), DFB, EFB
which they belong.
NOTE: A REF_TO can be
initialized with a variable of
the Program Unit which
Nature is <private> or
<public>.

External The global variables are accessible in the <external> EDT, DDT, ARRAY, References
variables sections of the Program Unit. (REF_TO)

These variables must be declared with the

same name and data type as the ones
defined in the global project.

488 33003101.26
Accessing Tasks, Program Units and Sections

Parameter Assignment
The following table gives the rule for assigning to parameters of a Program Unit:

Program Unit Parameters Assignment

Input parameters Optional except for ARRAY, DDT, Device DDT, STRING, and REF_TO

Output parameters

Input/Output parameters Compulsory

The way to assign variable for Program Unit parameter (formal parameter) is done via the
attribute Effective Parameter. The assigned variable is a global variable or a public variable
of another Program Unit.
The Program Unit parameters and the variables which are assigned to must be of the same
data type. For example, if the data type INT is defined for the input parameter, then you
cannot assign to this parameter a variable of the data type DINT nor REAL.
The only exceptions are for BOOL and EBOOL data types which can be mixed. For
example, a %Mi internal bit of data type EBOOL can be assigned to an input parameter
defined as BOOL.
You have the following options to enter the variable in the Effective parameter field:
• You can enter the variable name.
or
• Using the button ... you can open a Data selection dialog box and confirm the selected
variables there with OK.
Example of a Data selection dialog box according to the scope:

33003101.26 489
 Accessing Tasks, Program Units and Sections

NOTE: As the management of topological variable is only supported in the data editor of
the application (Address attribute of the variable), to map an interface variable of a
Program Unit to a topological variable, you have to:
• define a global located variable in the Data editor, then
• assign the global variable as an effective parameter of the Program Unit.

Program Unit Execution

The copy of the data from effective parameter to input formal parameter is performed before
the Program Unit execution.
The copy of the data from output formal parameter to the effective parameter is performed
after the Program Unit execution.
The following figure shows how a Program Unit is executed:

(1) Under the global scope.

(2) Under the scope of another Program Unit.

490 33003101.26
Accessing Tasks, Program Units and Sections

Example of Program Unit Variable Usage

The following example defines two Program Units and a section under a task:

This is a variable belonging to the global scope (declared in the Data Editor):

Name Type

Glob1 BOOL

This is the definition of the variables belonging to the Prog1 scope (declared in the
Program Unit Data Editor):

Name Type Nature

Glob1 BOOL <external>

Input1 BOOL <inputs>

Output1 BOOL <outputs>

InOut1 BOOL <inputs/outputs>

Pub1 BOOL <public>

Priv1 BOOL <private>

The following table shows the syntax, the usage, and the access rights of the variables
according to their nature and scope:

33003101.26 491
 Accessing Tasks, Program Units and Sections

Variable Usage in Prog1 Usage in the code Usage in Prog2 Usage in Sect1
of Prog2 as Effective
Parameter
Glob1 Glob1 (R/W) No Glob1 (R/W) Glob1 (R/W)

PROG1.Input1 Input1 (R) No No PROG1.Input1 (R)

PROG1.Output1 Output1 (R/W) No No PROG1.Output1

(R/W)

PROG1.InOut1 InOut1 (R/W) No No PROG1.InOut1 (R/

W)

PROG1.Glob1 No No No PROG1.Glob1 (R/

W)

PROG1.Pub1 Pub1 (R/W(1)) No PROG1.Pub1 (R/W PROG1.Pub1 (R/W

(2)) (1))

PROG1.Priv1 Priv1 (R/W) No No No

%S6 %S6 (R/W(3)) %S6 (R/W(3)) No %S6 (R/W(3))

%M23 %M23 %M23 No %M23

%MW17 %MW17 %MW17 No %MW17

No: The variable could not be used

R: Read only

R/W: Read and write

(1) The write access can be restricted if Pub1 has the attribute RW program set to read only.

(2) The write access can be restricted in external usage if Pub1 has the attribute RW program external use set
to read only.

(3) The write access depends on the write access of the system bit or system word.

Purge of Unused Variables

To purge unused variables, the Program Unit data editor tabs provide the context menu
Purge Unused Variables.
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 Program Unit data editor.

2 Right-click any column of the tab.

492 33003101.26
Accessing Tasks, Program Units and Sections

Step Action

3 Select the menu command Purge Unused Variables from the context menu.

4 Confirm with Yes.

Result: The unused variables will be purged.

NOTE: This action can also be done from the Interface tab and Function Blocks tab.

Export a Subset of Variables and FB Instances

A subset of variables or FB instances may be filtered out and/or selected via the Program
Unit Data Editor.
Program Unit variables and FB instances are saved in source format .XPU.
Whatever the variables or FB instances you export, you can choose two options:
• export with or without the content of all the DDTs used,
• export with or without the content of all the DFB types used.
By default, the two "export with" options are selected.
To export filtered variables:

Step Action

1 Select the Variables tab in the Program Unit data editor.

2 Filter the variables as described in the chapter Filtering of Data, page 430.

3 Select the menu command Export Filtered from the context menu.

Result: A dialog box appears on the screen.

4 Select the target folder for the export (directory tree) then enter the file name.

5 Select the export mode (with or without DDT, DFB type).

Result: When a "with" option is selected, the corresponding box is checked.

6 Activate the Export command.

Result: A progress indicator shows how the export is progressing.

7 A message is displayed in the display window to indicate that the export is finished.

To export selected variables:

33003101.26 493
 Accessing Tasks, Program Units and Sections

Step Action

1 Select the Variables tab in the Program Unit data editor.

2 Click on a variable to select it in the Program Unit data editor. You can select multiple variables by
holding down the Alt or Ctrl keys.

3 Select the menu command Export Selected from the context menu.

Result: A dialog box appears on the screen.

4 Select the target folder for the export (directory tree) then enter the file name.

5 Select the export mode (with or without DDT, DFB type).

Result: When a "with" option is selected, the corresponding box is checked.

6 Activate the Export command.

Result: A progress indicator shows how the export is progressing.

7 A message is displayed in the display window to indicate that the export is finished.

NOTE: The above export procedures can be also performed for the FB instances
defined under the Program Unit by selecting the Function Blocks tab of the Program
Unit data editor instead of the Variables tab.

Import a Subset of Variables and FB Instances

A subset of variables or FB instances may be imported via the Program Unit Data Editor.
NOTE: If the DDTs or associated DFB types have been exported (options selected on
export), they are imported with the list of variables.
If the list of variables already exists in the current Program Unit, the software asks you to
choose between the following options:
• keep the component of the current Program Unit,
• replace the Program Unit component by the one from the import file,
• rename the imported component, allowing you to keep both components.
To import variables:

Step Action

1 Select the Variables tab in the Program Unit data editor.

2 Activate the Import command from the contextual menu (by clicking the right mouse button).

Result: a dialog box appears on the screen.

3 Choose the source folder for the import (directory tree) then select the file to be imported (XPU or
XSY).

494 33003101.26
Accessing Tasks, Program Units and Sections

Step Action

Result: the name of the file then appears in the File name field.

4 Activate the Import command.

Result: a progress indicator shows how the import is progressing.

5 A message tells you when the import is complete.

If errors occur during the import, they are indicated by a message in the display window.

NOTE: The above import procedure can be also performed for the FB instances defined
under the Program Unit by selecting the Function Blocks tab of the Program Unit data
editor instead of the Variables tab.

Access Right for Animation Tables in a Program Unit

The access right for object of an Animation table in a Program Unit depends on the nature of
the variable:

Nature Type Access Right

With Effective Without

Parameter Effective
Parameter
<inputs> BOOL, EBOOL, and INT R R/W

ARRAY, DDT, STRING, and REF_TO R N/A

<outputs> BOOL, EBOOL, and INT R R

ARRAY, DDT, STRING, and REF_TO R N/A

<inputs/outputs> BOOL, R R

EBOOL, EDT, ARRAY, DDT, STRING, and REF_ R N/A

TO
R: Read only

R/W: Read and write

N/A: Not applicable

Nature Type Access Right

<public> EDT, DDT, and ARRAY R/W

Constant R
<private> EDT, DDT, ARRAY, DFB, and EFB R/W

33003101.26 495
 Accessing Tasks, Program Units and Sections

Nature Type Access Right

REF_TO, and constant R

R: Read only

R/W: Read and write

NOTE: In the animation table dedicated to a Program Unit (sub folder Animation
Tables under Program Unit directory), only variables that belong to this Program Unit
can be added.
The implementation of animation tables dedicated to a Program Unit and its management is
similar to the ones in the Animation Tables folder in the Project directory. For detailed
information refer to chapter Animation Tables, page 1467.

HMI Access
The following Program Unit variables are accessible from HMI/SCADA:

Parameters: They have read only access by default.

NOTE: <inputs> parameter without assigned Effective parameter have read
and write access by default.

Public: They are read and write access by default.

Using the attribute RW program external used, you can restrict the default access as:
• Read only for public variables.
• No access for public variables and parameters.
In the Program Unit data editor, select the attribute HMI variable to embed the variable in
the data dictionary. These variables will be visible for HMI/SCADA.
To access the Program Unit variable from HMI/SCADA, use the variable syntax: <Program
Unit name>.<variable name>. For example: Program1.MyVar

Program Unit Management

Introduction
There are two ways to duplicate a Program Unit:
• Copy of the Program Unit without copy of the effective parameters.
• Copy of the Program Unit with copy of the effective parameters.

496 33003101.26
Accessing Tasks, Program Units and Sections

You can use the menu command, shortcut menu or drag-and-drop to duplicate a Program
Unit.

Moving a Program Unit

The execution order of programs elements can be changed exclusively in the structural
view.
Process the following steps to move a Program Unit:

Step Action

1 Click on the desired Program Unit with the left mouse button and hold the mouse button down.

2 Move the Program Unit to the required position within the current task or into another task.

NOTE: A Program Unit containing an SFC section can not be moved form the MAST
task to another task.

Duplication Without Effective Parameters

Process the following steps to duplicate a Program Unit without copying the effective
parameters:

Step Action

1 Select the desired Program Unit.

2 Copy the Program Unit by:

• Click Copy from the shortcut menu
or
• The Ctrl+C key combination

3 Select the location for the new Program Unit. It can be a Program Unit.

4 Paste the new Program Unit by:

• Click Paste After from the shortcut menu
or
• The Ctrl+V key combination
Result: The new Program Unit is created just after the selected lProgram Unit.

If using the drag-and-drop function to duplicate a Program Unit without copy of the effective
parameters:
• Press the key combination Ctrl + left-click on the Program Unit to be duplicated
(holding down the mouse button),

33003101.26 497
 Accessing Tasks, Program Units and Sections

• drop the Program Unit at the desired location.

NOTE: A Program Unit containing an SFC section can be only duplicated in the MAST
task.

Duplication With Effective Parameters

Process the following steps to duplicate a Program Unit with copying the effective
parameter:

Step Action

1 Select the desired Program Unit.

2 Copy the Program Unit by:

• Click Copy from the shortcut menu
or
• The Ctrl+C key combination

3 Select the location for the new Program Unit. It can be a Program Unit.

4 Paste the new Program Unit by clicking Paste Special After... from the shortcut menu.

Result: A message box opens asking if you want to copy the effective parameters.

5 Click Yes to confirm the duplication with effective parameters.

NOTE: If you click No, the duplication is done without effective parameters, page 497.

6 Result: The new Program Unit is created just after the selected Program Unit.

If using the drag-and-drop function to duplicate a Program Unit with copy of the effective
parameters:
• Press the key combination Ctrl + Shift + left-click on the Program Unit to be duplicated
(holding down the mouse button),
• drop the Program Unit at the desired location.
NOTE: A Program Unit containing an SFC section can be only duplicated in the MAST
task.

Analyze
Process the following steps to analyze a Program Unit:

498 33003101.26
Accessing Tasks, Program Units and Sections

Step Action

1 Select the desired Program Unit.

2 Analyze the Program Unit by clicking Analyze 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.

Accessing Sections
Overview
This section describes accessing 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 (Logic directory of the task)
• in a Program Unit that belongs to a task (Sections directory of the Program Unit)
• in offline and online mode
Create FBD, LD, IL, or ST sections for Modicon M580:
• in the MAST, FAST, AUX0, and AUX1 tasks (Logic directory of the task)
• in a Program Unit that belongs to a task (Sections directory of the Program Unit)
• in offline and online mode
Create FBD, LD, IL, or ST sections for Quantum, Premium and Atrium:
• in MAST, FAST, and AUX tasks (Sections directory of the task)
• in offline and online mode

Information for creating LD sections

An LD section contains 11-63 columns and 17-3998 rows.

33003101.26 499
 Accessing Tasks, Program Units and Sections

The number of columns is set in the Tools > Project Settings dialog box, in the Program >
Languages > LD tab, in the Number of Columns text box.
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 box, in the
Program > FBD tab.
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.)

Creating a section
Creating a section:

Step Action

1 To create a section in a task, select the desired directory (Sections or Logic) 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.

Or

Select Edit > New Section

Result: The New dialog box for the section opens.

3 Enter the section name.

The section name must be unique in the entire project and conform to the general naming
conventions.
NOTE: Two sections of different program units can have the same name.

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

500 33003101.26
Accessing Tasks, Program Units and Sections

Step Action

• Read-Only
Write protection
• No read & write
Read and write protection
See also section Project Protection, page 187.

6 Select the functional module to which the section is allocated from the Localization tab if
necessary.

See also section Functional module, page 232.

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 an instance selection dialog box, page 1174.
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 EcoStruxure™
Control Expert, Program Languages and Structure, 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 New
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 New
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 Select (right-click or Shift+F10 key combination) the Properties... menu command from the
shortcut menu.

Result: The Properties of dialog box for the section opens.

3 Implement the desired changes.

4 Confirm all entries with OK.

33003101.26 501
 Accessing Tasks, Program Units and Sections

Importing/exporting sections
See:
• Importing programs, page 1692
• Exporting programs, page 1690

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.

502 33003101.26
Accessing Tasks, Program Units and Sections

General tab
Representation of the General tab:

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 Program Unit, Section and Subroutine Protection, page 187.

OK Use this command button to accept the entries and close the properties dialog box.

Apply Use this command button to accept the entries without closing the properties dialog box.

33003101.26 503
 Accessing Tasks, Program Units 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, page 232.

OK Use this command button to accept the entries and close the properties dialog box.

Apply Use this command button to accept the entries without closing the properties dialog box.

504 33003101.26
Accessing Tasks, Program Units 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 an instance selection dialog box, pa