Software Manual

L-force Engineer

HighLevel

L
 This Manual applies to the Lenze »Engineer« as of version 1.2.5.2

Copyright
© 2006 Lenze Drive Systems GmbH. All rights reserved.

Imprint
Lenze Drive Systems GmbH
Postfach 10 13 52, 31763 Hameln, Germany
Phone: ++49 (0)5154 / 82-0
Fax: ++49 (0)5154 / 82-2111
E-mail: [email protected]

Copyright information
All texts, photos and graphics contained in this documentation are subject to
copyright protection. No part of this documentation may be copied or made
available to third parties without the explicit written approval of Lenze Drive
Systems GmbH.

Liability
All information given in this documentation has been selected carefully and
tested for compliance with the described hardware and software. Neverthe-
less, discrepancies cannot be ruled out. We do not accept any responsibility or
liability for any damage that may occur. Required corrections will be included
in updates of this documentation.

Trademarks
Microsoft, Windows and Windows NT are either registered trademarks or
trademarks of Microsoft Corporation in the U.S.A. and/or other countries.
Adobe and Reader are either registered trademarks or trademarks of Adobe
Systems Incorporated in the U.S.A. and/or other countries.
All other products mentioned in this documentation are trademarks of the cor-
responding owners.

2 1.6 EN - 08/2006 - TD16 L

 L-force | Engineer
Contents

Contents
1 About this Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1.1 Conventions used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
1.2 Definition of notes used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

2 Safety instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

3 User interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
3.1 Control & function elements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
3.1.1 Title bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
3.1.2 Menu bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
3.1.3 Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
3.1.4 Project view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
3.1.4.1 Project structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
3.1.4.2 History of the preselected elements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
3.1.4.3 General processing functions in the project view . . . . . . . . . . . . . . . . 20
3.1.4.4 Shortcuts in the project view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
3.1.5 Operating range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
3.1.5.1 Representation of parameter values . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
3.1.6 Message window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
3.1.7 Monitor window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
3.1.7.1 Configuring the monitor window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
3.1.8 Assistants . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
3.2 Exiting the program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

4 Working with projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

4.1 Creating a new project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
4.2 Creating a new project (downloading data from the system) . . . . . . . . . . . . . . . . . . . . . . 32
4.3 Opening an existing project. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
4.4 Editing project properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
4.5 Saving the project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
4.6 Closing the project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

L 1.6 EN - 08/2006 3
L-force | Engineer
Contents

5 Device functions in the online mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

5.1 Establishing an online connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
5.1.1 Going online . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
5.1.1.1 System bus (CAN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
5.1.1.2 Diagnostic adapter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
5.1.1.3 Ethernet. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
5.1.1.4 Gateway diagnostic adapter -> system bus (CAN). . . . . . . . . . . . . . . . 46
5.1.1.5 After establishing the online connection.... . . . . . . . . . . . . . . . . . . . . . . 47
5.1.1.6 Going offline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
5.2 Control functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
5.2.1 Enabling the controller. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
5.2.2 Inhibiting the controller. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
5.2.3 Starting the application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
5.2.4 Stopping the application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
5.3 Application and parameter set transfer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
5.3.1 Reading the parameter set from the device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
5.3.2 Transferring the parameter set to the device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
5.3.3 Compare parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
5.3.4 Save parameter set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
5.3.5 Transferring the application to the device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
5.4 System bus configurator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
5.5 Diagnostic interface of the communication configurator . . . . . . . . . . . . . . . . . . . . . . . . . . 58

6 Project structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
6.1 Inserting system modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
6.2 Inserting axes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
6.3 Adding components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
6.3.1 Adding controllers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
6.3.2 Assigning an application to a device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
6.3.3 Assigning (a) device module(s) to a device. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
6.3.4 Adding a motor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
6.3.5 Adding an I/O system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
6.3.5.1 Adding a modular I/O system. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
6.3.6 Adding gearboxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
6.4 Adding documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

4 1.6 EN - 08/2006 L
 L-force | Engineer
Contents

7 Communication between the controllers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

7.1 Separation of the application and the network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
7.1.1 Application level. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
7.1.1.1 Process data object (PDO) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
7.1.1.2 Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
7.1.1.3 Variable types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
7.1.2 Network level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
7.1.3 Connection between application and network . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
7.1.3.1 User definitions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
7.1.4 Establishing the connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
7.1.4.1 Automatic connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
7.1.4.2 Manual connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
7.1.4.3 Predefined connection set connection . . . . . . . . . . . . . . . . . . . . . . . . . . 88
7.1.4.4 Mixed connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
7.2 System bus CAN - network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
7.2.1 CAN objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
7.2.2 Synchronisation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
7.2.3 Process data objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
7.2.3.1 Packing ports into process data objects . . . . . . . . . . . . . . . . . . . . . . . . . 90
7.2.4 CAN settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

8 Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
8.1 Connection between application and network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
8.2 Inserting a network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
8.3 System bus (CAN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
8.3.1 Nodes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
8.3.1.1 Inserting nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
8.3.1.2 Node settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
8.3.1.3 Removing nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
8.3.2 Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
8.3.3 Synchronisation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
8.3.4 CAN objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
8.3.5 Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

9 Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
9.1 Terminology used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
9.2 General notes with regard to the procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
9.3 Parameterising & configuring the devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
9.3.1 Displaying the properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
9.3.2 Assigning an application to the device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

L 1.6 EN - 08/2006 5
L-force | Engineer
Contents

9.3.3 Setting the parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

9.3.3.1 Terminology used. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
9.3.3.2 Working in the parameter list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
9.3.3.3 Altering a parameter offline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
9.3.3.4 Altering parameters online . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
9.3.3.5 Resetting parameters to the default setting . . . . . . . . . . . . . . . . . . . . . 118
9.3.3.6 Accepting the parameter settings of the device. . . . . . . . . . . . . . . . . . 118
9.3.3.7 Accepting parameter settings in the device. . . . . . . . . . . . . . . . . . . . . . 118
9.3.4 Configuring the terminal assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
9.3.4.1 Changing the terminal assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
9.3.4.2 Setting the gain & offset of the analog terminals . . . . . . . . . . . . . . . . 119
9.3.4.3 Setting the active level of the digital terminals . . . . . . . . . . . . . . . . . . 119
9.3.4.4 Displaying the actual state of the terminals . . . . . . . . . . . . . . . . . . . . . 120
9.3.5 Parameterising the application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
9.3.5.1 Working in the "Application parameters" tab . . . . . . . . . . . . . . . . . . . . 121
9.3.5.2 Going directly to a parameter dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
9.4 Port editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
9.4.1 Adding a port. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
9.4.1.1 "Simple" variable type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
9.4.1.2 "Record" variable type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
9.4.1.3 "Array" of byte variable type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
9.4.1.4 Port with the "Simple" variable type . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
9.4.1.5 Port with the "Record" variable type . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
9.4.1.6 Port with the "Array" variable type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
9.4.1.7 Defining the element variable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
9.4.1.8 Renaming a port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
9.4.1.9 Deleting a port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
9.4.2 Adding documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
9.5 Generating machine applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
9.5.1 Inserting a machine application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
9.5.2 Displaying the properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
9.5.3 Assigning applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
9.5.3.1 Carrying out assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
9.5.3.2 Removing assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
9.5.4 Connecting ports within the machine application . . . . . . . . . . . . . . . . . . . . . . . . . 142
9.5.5 Adding ports as an external interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
9.5.6 Adding documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

6 1.6 EN - 08/2006 L
 L-force | Engineer
Contents

9.5.7 Establishing the connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

9.5.7.1 Automatic connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
9.5.7.2 Manual connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
9.5.7.3 Predefined connection set connection . . . . . . . . . . . . . . . . . . . . . . . . . . 146
9.5.7.4 Mixed connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
9.6 Establishing a function block interconnection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
9.6.1 Terminology used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
9.6.2 Adjusting the representation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
9.6.3 Inserting objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
9.6.3.1 Inserting a function block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
9.6.3.2 Inserting a port block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
9.6.3.3 Inserting a variable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
9.6.3.4 Inserting a user code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
9.6.4 Arranging objects in the drawing area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
9.6.5 Establishing/removing connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
9.6.6 Converting connections into markings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
9.6.7 Changing the processing order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
9.6.8 Compiling the completed interconnection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167

10 Commissioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
10.1 Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
10.2 Oscilloscope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170

11 Application examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

11.1 Interconnection of ready-made technology applications. . . . . . . . . . . . . . . . . . . . . . . . . . . 171
11.2 External device without device description (catalog) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
11.3 Interconnection of an I/O terminal with a 9400 HighLine. . . . . . . . . . . . . . . . . . . . . . . . . 177
11.4 Profibus node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179

12 Error messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181

12.1 ApplicationConnection Generator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
12.2 PortLogic generator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
12.3 System bus (CAN) generator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
12.3.1 Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
12.3.2 Baud rate and MMT master . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
12.3.3 Synchronisation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
12.3.4 COB-ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
12.3.5 Ports and PDO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191

L 1.6 EN - 08/2006 7
L-force | Engineer

12.4 Generator communication entities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192

12.4.1 Standard (9300 servo + 9300 ServoPLC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
12.4.2 Compact (8200) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
12.4.3 9400 OnBoard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
12.4.4 EPM (compact and modular) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
12.4.5 9400 Profibus module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198

13 Short menu reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200

13.1 "File" menu" . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
13.2 "Edit" menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
13.3 "Insert" menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
13.4 "View" menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
13.5 "Online" menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
13.6 "Tools" menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
13.7 "Configuration" menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
13.8 "Extras" menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
13.9 "?" menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203

14 Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204

15 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208

Your opinion is important to us. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210

8 1.6 EN - 08/2006 L
 L-force | Engineer
About this Manual

1 About this Manual

This Manual contains information on the Lenze »Engineer«.
The »Engineer« is a tool which supports you throughout the whole machine life cycle -
from planning to maintenance.

Structure of this Manual

 The "Safety instructions" chapter contains safety instructions which must be observed
if you want to commission a controller or plant using the »Engineer«. ( 12)
 The "User interface" chapter introduces you to the user interface of the
»Engineer«. ( 13)
 The "Working with projects" chapter informs you on how to create a first project in the
»Engineer«. ( 28)
 The "Device functions in the online mode" chapter informs you on how to establish an
online connection to a device, execute control functions in the device and transfer pa-
rameter sets and programs between device and »Engineer«. ( 39)

Project Devices Network Functions

( 92) ( 107)

L 1.6 EN - 08/2006 9
L-force | Engineer
About this Manual
Conventions used

1.1 Conventions used

This Manual uses the following conventions to distinguish between different types of in-
formation:
Type of information Writing Examples/notes
Variable identifier Italics By setting bEnable to TRUE...
Window area The Message window... / The dialog box Options...
Control element Bold The OK button... / The Copy command... / The Properties index card... /
The Name input field...
Sequence of If several commands must be used in sequence to carry out a function,
menu commands then the individual commands are separated by an arrow. Select the
command FileOpen to...
Keyboard command <Bold> Use <F1> to open the online help.
If a key combination is required for a command, a "+" is inserted be-
tween the key identifiers: Use <Shift>+<ESC>...
Program code Courier IF var1 < var2 THEN
Keyword Courier a = a + 1
bold END IF

Hyperlink Underline Hyperlinks are highlighted references which are activated by means of a
mouse click.
Step-by-step instruc-
tion  Step-by-step instructions are marked by a pictograph.

10 1.6 EN - 08/2006 L
 L-force | Engineer
About this Manual
Definition of notes used

1.2 Definition of notes used

This documentation uses the following signal words and symbols to indicate dangers and
important information:

Safety information
Structure of the safety instructions:

 Pictograph and signal word!

(characterise the type and severity of danger)
Note
(describes the danger and suggests how to avoid the danger)

Pictograph Signal word Meaning

 Danger! Danger of personal injury through dangerous electrical voltage

Indicates an impending danger that may lead to death or severe personal injury if
the corresponding measures are not taken.

 Danger! Danger of personal injury through a general source of danger

Indicates an impending danger that may lead to death or severe personal injury if
the corresponding measures are not taken.

 Stop! Danger of material damage

Indicates a potential danger that may lead to material damage if the corresponding
measures are not taken.

Application notes

Pictograph Signal word Meaning

 Note! Important note to ensure trouble-free operation

 Tip! Useful tip for simple handling

L 1.6 EN - 08/2006 11
L-force | Engineer
Safety instructions

2 Safety instructions
Please observe the following safety instructions when you want to commission a controller
or system using the »Engineer«.

 Please read the provided documentation of the controller and single components
carefully before you start commissioning the devices with the »Engineer«!
The device documentation contains safety instructions which must be observed!

 Danger!
According to our present level of knowledge it is not possible to ensure an abso-
lute freedom from error of a software.
The systems with built-in controllers must be provided with additional monitor-
ing and protective equipment according to relevant safety instructions (e.g. law
on technical equipment, regulations for the prevention of accidents), so that an
impermissible operating status does not endanger persons or facilities.
During commissioning persons must keep a safe distance from the motor or the
machine parts driven by the motor. Otherwise there is be a risk of injury by the
moving machine parts.

 Stop!
If you change parameters in the »Engineer« while the controller is connected on-
line, the changes will be directly accepted by the controller!
A wrong parameter setting can cause unpredictable motor movements. By unin-
tentional direction of rotation, too high speed or jerky operation, the driven ma-
chine parts may be damaged!

12 NKS=bk=J=MULOMMS L
 L-force | Engineer
User interface
Control & function elements

3 User interface
This chapter presents the different control and function elements of the user interface and
explains how to exit the program again.
Control & function elements
Exiting the program ( 27)

3.1 Control & function elements

The user interface contains the following control and function elements:

 Title bar  Toolbar Project structure  Message window / Monitor window

 Menu bar Project view  Operating range without fig.: Assistants

L NKS=bk=J=MULOMMS 13
L-force | Engineer
User interface
Control & function elements

3.1.1 Title bar

In the Title bar in the upper position of the application window the Program icon and Pro-
gram name are displayed in the left-most position and the Window icons are displayed in
the right-most position:

 The view of the application window can be changed via the Window icons
Here, the following is distinguished:
– Icon in the Task bar ( )
– Complete picture ( )
– Window size ( )
 When clicking the Program icon you open the System menu which also contains com-
mands for positioning and changing the size of the application window.
 By clicking the Window icon or by double-clicking the Program icon you exit the »En-
gineer«.

3.1.2 Menu bar

The Menu bar enables you to access all menu commands.

 By clicking a main menu item you open the corresponding menu and the menu items
contained therein are displayed.
 By clicking a menu item you execute the function associated.
– Menu items displayed in light grey are deactivated in the current program status.

14 NKS=bk=J=MULOMMS L
 L-force | Engineer
User interface
Control & function elements

3.1.3 Toolbar

Via the icons in the Toolbar you can carry out one of the functions which is required the
most often in a simple manner without going the indirect way via the Menu bar. If you are
in the project view, the entire toolbar is displayed.
 Click an icon to execute the corresponding function:

Icon Menu command Function

- Go back or forth one step in the course of the segments se-
lected before.
History of the preselected elements ( 19)
-

FileNew project... Creating a new project ( 29)

FileOpen... Opening an existing project ( 36)

FileSave Saving the project ( 37)

- Configuring the monitor window ( 25)

- Maximise or minimise operating range

Operating range ( 21)

HelpIndex Display online help

InsertSystem module Inserting system modules ( 62)

InsertAxis Inserting axes ( 64)

InsertComponent Adding components ( 68)

InsertGearbox Adding gearboxes ( 80)

InsertDevice module Assigning (a) device module(s) to a device ( 73)

InsertApplication Assigning an application to a device ( 72)

InsertNetwork Inserting a network ( 96)

InsertApplication Inserting a machine application ( 139)

OnlineGo online Establish a connection to a drive

Going online ( 40)

OnlineGo offline Interrupt the connection to a drive

Going offline ( 47)

OnlineEnable controller Enable the controller (Deactivate controller inhibit)

 Safety instructions ( 12)

Enabling the controller ( 49)

OnlineInhibit controller Inhibit the controller (set controller inhibit)

Inhibiting the controller ( 49)

L NKS=bk=J=MULOMMS 15
L-force | Engineer
User interface
Control & function elements

Icon Menu command Function

OnlineStart application Start application in the device

 Safety instructions ( 12)

Starting the application ( 50)

OnlineStop application Stop application in the device

Stopping the application ( 50)

OnlineSave parameter set Saves parameters with mains failure protection in the de-
vice.
Save parameter set ( 56)
OnlineUpload parameter set Read parameter set from the device (upload)
Reading the parameter set from the device ( 52)
OnlineDownload parameter set Write parameter set in the device (download)
Transferring the parameter set to the device ( 53)

OnlineDownload application Write application in the device (download)

Transferring the application to the device ( 57)

ExtrasUpdate devices Update devices

 Note!
The icons which are available in detail in the Toolbar depend on the project view
selected and on the program context in which you are located at the moment.

16 NKS=bk=J=MULOMMS L
 L-force | Engineer
User interface
Control & function elements

3.1.4 Project view

Project Devices Network Applications

 Note!
Depending on the project view selected, the symbols available change in the
Toolbar, the elements displayed in the Project view and the Operating range.

3.1.4.1 Project structure

Similar to the folder view in the Windows Explorer, the elements of the current project are
displayed in the Project view of the »Engineer« in a hierarchical tree topology.

 Note!
If you press Project, the complete project tree will be displayed. If you press De-
vices, Network or Applications, the display will be filtered.

 If a plus sign is located in front of an element, this element contains further subele-
ments.
– A click on the plus sign shows the subelements.
– Another click on the minus sign displayed now hides the subelements.
 The features and settings of the currently selected element are displayed in the oper-
ating range and can be changed here as well.

L NKS=bk=J=MULOMMS 17
L-force | Engineer
User interface
Control & function elements

 Tip!
You can change the width and height of the Project view by shifting the screen di-
vider between Project view and Operating range or between Project view and Mes-
sage window accordingly using the mouse pointer.
The right mouse button provides a Context menu with element-related functions.

Via the icons and in the Toolbar, you can quickly jump back to the elements
selected in the Project view. History of the preselected elements ( 19)

18 NKS=bk=J=MULOMMS L
 L-force | Engineer
User interface
Control & function elements

3.1.4.2 History of the preselected elements

All elements selected during processing a project in the Project view are stored in a proto-
col, what is known as "history".

 Note!
When the project is closed, the history is cleared automatically, i.e. when you
open a project, the history is empty at first.

Via the icons and in the Toolbar you can move within this history which serves to
quickly and easily jump back to the elements selected before in the machine view.

 Tip!
If you are in the project tree with several controllers, you can return to the last one
processed.

 By clicking the symbol you can jump back to the element selected before.

 By clicking the symbol you jump one element forward in the history.

 When you click the arrow next to the symbols or , a list is shown which pro-
vides a quick access to the elements selected last.
– Simply click one entry in the list to jump to the corresponding element.
– Each entry has the form "project: element name".

L NKS=bk=J=MULOMMS 19
L-force | Engineer
User interface
Control & function elements

3.1.4.3 General processing functions in the project view

The following processing functions apply to all elements in the Project view.

Renaming an element
1. Select the element to be renamed.
2. Select the command EditRename or press function key <F2>.
3. Enter new name.
4. Press <Input key> to accept the new name.

Shifting an element
1. Select the element to be shifted including all subelements.
2. Shift element to the required position by keeping the left mouse button pressed. Here
the current position of the object is displayed.

or
1. Select the element to be shifted including all subelements.
2. Select command EditCut.
3. Select the element into which the element cut before is to be pasted.
4. Select command EditPaste.

Copying an element
1. Select the element which is to be copied including all subelements.
2. Select command EditCopy.
3. Select the element into which the element copied before is to be pasted.
4. Select command EditPaste.

Deleting an element
1. Select the element to be deleted including all subelements.
2. Select command EditDelete or press <DEL> key to delete the selected element.

20 NKS=bk=J=MULOMMS L
 L-force | Engineer
User interface
Control & function elements

3.1.4.4 Shortcuts in the project view

Especially if you execute the »Engineer« on a laptop, you can also use the keyboard as an
alternative to the mouse pointer for selecting elements to quickly move within the Project
view and select elements for processing.
The following shortcuts can be used for navigation within the Project view if an element is
focussed in the Project view:

Keyboard command Function

<PG DN> Scrolling down in the tree.
<PG UP> Scrolling up in the tree.
<DOWN ARROW> Selection of the next element down.
<UP ARROW> Selection of the next element up.
<RIGHT ARROW Depending on the icon that is indicated before the element:
Showing the subelements.
Selection of the first subelement.
<LEFT ARROW> Depending on the icon that is indicated before the element:
Selection of the superior element in the hierarchy.
Hiding the subelements.
<BACKSPACE> Selection of the respective superior element in the hierarchy.
<END> Selection of the last (shown) element.
<POS1> Selection of the first element (the project element).

 Tip!
To focus on an element in the Project view, simply click an element with the mouse
pointer or press the <Tab> key until the focus switches to an element.

3.1.5 Operating range

In the Operating range the properties and settings of the elements currently being selected
in the Project view are displayed in different tabs and can also be changed here.

 When the tab in the upper position is clicked, the corresponding tab comes to the fore-
ground.

 Tip!
The individual which tabs are displayed in the Operating range depend on the type
of the element selected.
You can change the width and height of the Operating range by shifting the screen
divider between Project view and Operating range or between Operating range and
Message window accordingly using the mouse pointer.

L NKS=bk=J=MULOMMS 21
L-force | Engineer
User interface
Control & function elements

3.1.5.1 Representation of parameter values

Settings of device parameters displayed in the operating range of the »Engineer« (e.g. on
the Parameters tab for a device) are represented in different background colours which
have the following meaning:

Colour Example Meaning

White Offline parameter
• The device is not connected "online" with the »Engineer«. The parameter value
set in the project is displayed.
Light grey Offline display parameter
• "Display parameters" are parameters which only serve as display of status infor-
mation and only permit reading access.
Yellow Online parameter
• The device is connected "online" with the »Engineer«. The current parameter val-
ue of the device is displayed.
• The symbol in front of a parameter value indicates that the value in the device
differs from the parameter value set in the project.
Pale yellow Online display parameter
• The device is connected "online" with the »Engineer«. The current parameter val-
ue of a display parameter is displayed.
Red Communication error (time-out)
• The communication to a device is interrupted, the online parameter could not be
read out of the device within a certain time.

When you edit a parameter value in an input field, the text colour indicates whether the
changed value has already been taken over into the project or device or is within the range
of validity:

Colour Example Meaning

Black Parameter value which is within the range of validity and has already been taken
over into the project or device.

Blue Changed parameter value which has not yet been taken over into the project or the
device.
• By pressing the <Input key> you accept the changed value.
• By pressing the <ESC> key you can undo the change made.
Red Changed parameter value which is outside the valid range.
• By pressing the <ESC> key you can undo the change made.

22 NKS=bk=J=MULOMMS L
 L-force | Engineer
User interface
Control & function elements

3.1.6 Message window

In the Message window status and error messages with regard to an executed program
operation or current program status are displayed.
Each message has the following structure:

Icon Time stamp Text

[hh.mm.ss] Information text

Note

Error text

Program error text

Context menu
The Message window provides a context menu (right mouse button) with the following
commands:

Command Function
Delete Delete all messages in the message window.
Display Submenu to select the elements to be displayed.
Copy list Copy all messages to the clipboard.
Copy message Copy the selected message to the clipboard.

 Tip!
You can change the Message window by moving the screen divider between Oper-
ating range and Message window up or down using the mouse pointer.

L NKS=bk=J=MULOMMS 23
L-force | Engineer
User interface
Control & function elements

3.1.7 Monitor window

Instead of the message window, a monitor window can be shown below the Project view
and the Operating range.

 In the monitor window the current values of up to 16 parameters of the devices availa-
ble in the project can be shown when an online connection has been established.
 Via the Selection list field you can determine whether the Monitor window is displayed
for the entire machine or a Monitor window is displayed for a particular device available
in the project.
– If the Monitor window for the machine has not been configured yet, the display area
for this Monitor window is empty first.
– The Monitor window for a device is already preconfigured with practical display pa-
rameters which can be changed if required.
 The size of configured display fields is automatically adapted to the size of the Monitor
window.
 For an optimum representation, completely empty columns in the right-most position
and empty lines at the bottom are automatically hidden.
 When the window symbol of a display field is clicked, the corresponding display can
be maximised in the Monitor window.
– By clicking the window symbol displayed then, you go back to the representation
of all configured display fields.

 How to show the monitor window:

1. Select the Monitor tab at the bottom of the application window to show the
Monitor window instead of the Message window.
2. Select the Monitor window to be displayed in the View list field.

24 NKS=bk=J=MULOMMS L
 L-force | Engineer
User interface
Control & function elements

3.1.7.1 Configuring the monitor window

The Monitor window for the machine and the device can be freely configured.

 How to configure the monitor window:

1. In the View list field select the Monitor window to be configured.
2. Press Adapt to open the Adapt view dialog box.
3. In the upper range click the display field you want to configure.
• The display field selected is highlighted by a blue frame.
4. Press Select parameter... to open the Parameter selection dialog box.
5. Select the target system from the tree structure on the left side which contains the
parameter to be displayed.
6. Select the desired parameter from the list field on the right.
• When you deactivate the control field Display only read parameters, all param-
eters available in the target system are indicated in the list field.
7. Press OK.
• The Parameter selection is closed and the selection is accepted.
8. Configuring the display of the parameter value:
• In the Display as input field, the name of the display field possibly must be
changed to indicate the reference to the respective device in the monitor win-
dow for the machine.
• In order to visualise the parameter value, select one of the following options:
phaser diagram, bar diagram, history, text, switched off.
• When you select an instrument of phaser diagram, bar diagram or history type,
you can additionally define a minimum and maximum value for the display ar-
ea.
• In the Display list field you can select whether the current value, the maximum
value, or the minimum value of the parameter is to be displayed.
• The position of the display field in the monitor window can be changed after-
wards by means of the arrow buttons.
9. Press OK.
• The Configure monitor window dialog box is closed and the display fields config-
ured are displayed in the Monitor window.

 Tip!
The right mouse button provides a context menu with element-related functions.

L NKS=bk=J=MULOMMS 25
L-force | Engineer
User interface
Control & function elements

3.1.8 Assistants

The »Engineer« has various "assistants", which will support you when creating a new pro-
ject or establishing and configuring a network.
All assistants have the same basic appearance of the dialog window via which the required
information is queried step by step.

 The left side displays the assistant step you are in at the moment.
 The actual dialog area is located in the middle.
 Supplementary information about the corresponding step is displayed on the right.

Standard buttons

Button Function
Next Go to the next step.
Previous Go back to the previous step.
Complete Exit assistant and accept the settings done.
Cancel Abort assistant and cancel the settings done.

26 NKS=bk=J=MULOMMS L
 L-force | Engineer
User interface
Exiting the program

3.2 Exiting the program

 Select the command FileExit or click Window symbol in the Title bar to exit the
»Engineer«.

 Note!
If another project with non-saved changes is open, the Save project dialog box
will be displayed before exit.
Working with projects: Closing the project ( 38)

L NKS=bk=J=MULOMMS 27
L-force | Engineer
Working with projects

4 Working with projects

This chapter describes the general handling with projects in the »Engineer«.
When you start the »Engineer«, first no project is loaded and the Start-up wizard appears:

The Start-up wizard enables you to create a new project or open a project already available:
Creating a new project ( 29)
Opening an existing project ( 36)

 Tip!
For a new project to be created you can let the »Engineer« search for devices that
can be reached Online. All devices identified are then listed in the Project view in a
flat structure. During the further project management, the flat structure can be
transferred to a hierarchical structure.
Creating a new project (downloading data from the system) ( 32)

28 1.6 EN - 08/2006 L
 L-force | Engineer
Working with projects
Creating a new project

4.1 Creating a new project

A new project is created by means of the Start-up wizard and consists of the definition of
the project properties and the indication of the project directory to store all project data in-
volved.

Project properties
The project properties entered in the Start-up wizard can always be changed afterwards.

Project directory
In addition to the project file with the ending ".afs" further directories and files belong to a
project which are stored in a project directory created by the Start-up wizard.
 Name and path for the project directory can be freely selected in the Start-up wizard.

 How to create a new (empty) project:

1. If the Start-up wizard is not displayed yet, click the symbol or select the com-
mand FileNew project... to call the Start-up wizard.
Step 1 - What do you want to do?

2. Select New project (empty).

3. Press Next.

L 1.6 EN - 08/2006 29
L-force | Engineer
Working with projects
Creating a new project

Step 2 - properties

4. Enter the corresponding properties of the project (name, order number etc.) in to
the input fields.
• The properties can always be changed afterwards.
• The name can later be found in the Project view as the name of the project ele-
ment.
5. Press Next.
Step 3 - memory location

30 1.6 EN - 08/2006 L
 L-force | Engineer
Working with projects
Creating a new project

6. The project designation entered before is suggested as the project name. If re-
quired correct the suggestion accordingly.
• The project name at the same time is the name for the project directory to be
created.
7. Specify the storage location for the project directory in the Directory input field.
• If the stated directory does not exist, a new one is created.
• As an alternative you can select an existing directory in your workplace environ-
ment via the Browse... button.
8. Press Complete to create the project with the defined settings.

 Tip!
The elements in the Project view can always be renamed, if required.

Next steps
The next step is to create a system structure.

L 1.6 EN - 08/2006 31
L-force | Engineer
Working with projects
Creating a new project (downloading data from the system)

4.2 Creating a new project (downloading data from the system)

Instead of beginning with an empty project, you can also let the »Engineer« search for de-
vices that can be reached Online.
 After the search you can select which of the identified devices are to be transferred to
the project in the Start-up wizard.

 Note!
To download the data a communication connection to the system must be es-
tablished either via the system bus (CAN) or, in the case of the Servo Drives 9400,
via the diagnostic interface X6.

 Stop!
In the fourth step "Read online data", the Start-up wizard automatically estab-
lishes an online connection via the selected interface after the Start search but-
ton is pressed to download data from the devices connected.

 How to create a new project with data downloaded from the system:
1. If the Start-up wizard is not displayed yet, click the symbol or select the com-
mand FileNew project... to call the Start-up wizard.
Step 1 - What do you want to do?

2. Select the option New project (download data from system).

3. Press Next.

32 1.6 EN - 08/2006 L
 L-force | Engineer
Working with projects
Creating a new project (downloading data from the system)

Step 2 - properties

4. Enter the corresponding properties of the project (name, order number etc.) in to
the input fields.
• The properties can always be changed afterwards.
• The name can later be found in the Project view as the name of the project ele-
ment.
5. Press Next.
Step 3 - memory location

L 1.6 EN - 08/2006 33
L-force | Engineer
Working with projects
Creating a new project (downloading data from the system)

6. The project designation entered before is suggested as the project name. If re-
quired, correct the suggestion accordingly.
• The project name at the same time is the name for the project directory to be
created.
7. Specify the storage location for the project directory in the Directory input field.
• If the stated directory does not exist, a new one is created.
• As an alternative you can select an existing directory in your workplace environ-
ment via the Browse... button.
8. Press Next.
Step 4 - Read online data

9. Select the interface to be used in the Online connection list field.

10. Press the Start search button to start the search for the devices connected to the
selected interface.
• The Search for online devices dialog box with status messages is displayed.
• The Start-up wizard automatically establishes an online connection via the se-
lected interface to download data from the connected devices.
11. After the search, press the Close button to close the Search for online devices dialog
box again.
12. Select the devices from the Identified devices list field which are to be transferred
to the new project to be created.
• Via the Device modules button you can assign the device currently selected
from the list field to possibly available device modules which could not have
been identified automatically.
13. Press Complete.
• The project is created with the defined settings.
• Now an online connection to the devices selected already is available!

34 1.6 EN - 08/2006 L
 L-force | Engineer
Working with projects
Creating a new project (downloading data from the system)

The Project view displays the Project element with the name stored for the project and be-
low the project element all devices selected before are listed in a flat system structure.

 Stop!
An online connection to the devices now already is available, which can be seen
by the yellow highlighted device symbol in the Project view!
If you change parameters in the »Engineer« while the controller is connected on-
line, the changes will be directly accepted by the controller!

[4.1] Example: project with Servo Drives 9400 HighLine with an existing online connection.

Next steps
In a next step you can continue to complete the system structure and for instance transfer
the existing flat structure into a hierarchical structure by adding further system modules
to the project.
Parameterising & configuring the devices

L 1.6 EN - 08/2006 35
L-force | Engineer
Working with projects
Opening an existing project

4.3 Opening an existing project

 How to open an existing project:

1. If the Start-up wizard is not displayed yet, click the symbol or select the com-
mand FileOpen project... to call the Start-up wizard.
Step 1 - What do you want to do?

2. Select the option Open existing project.

• If the Start-up wizard was started via the symbol or the command FileOpen
project... this option is already selected and all other options are deactivated.
3. Select one of the project files edited last from the Project file list field or press the
Search... button to select an existing project file in the workplace environment.
4. Press the Complete button to open the selected project file.

36 1.6 EN - 08/2006 L
 L-force | Engineer
Working with projects
Editing project properties

4.4 Editing project properties

When you select Project element in the Project view, the Properties tab for the project is dis-
played in the Operating range:

 In this tab you can enter global information on the project, e.g. the version and editor
of the project.

4.5 Saving the project

 Click the symbol or select the command FileSave to save the project.

 Tip!
Save the project from time to time to protect your work from power failure or sys-
tem problems.

L 1.6 EN - 08/2006 37
L-force | Engineer
Working with projects
Closing the project

4.6 Closing the project

 Select the command FileClose to close the currently open project.

 Note!
If some changes are not saved so far, the Save Project dialog box is displayed:

• Press the Yes button to save/close or the Cancel button to abort the action.
• When you press No, the project will be closed without the changes made be-
ing saved.

38 1.6 EN - 08/2006 L
 L-force | Engineer
Device functions in the online mode
Establishing an online connection

5 Device functions in the online mode

This chapter informs you on
 how you can establish an online connection to a device, e. g. via system bus (CAN), di-
agnostic adapter, or gateway diagnostic adapter -> system bus (CAN).
 how you can carry out control functions like "Start application" or "Set controller inhib-
it" in the device from the »Engineer«. ( 48)
 how you can transfer parameter settings of the »Engineer« project (as well as option-
ally the drive application) into the device. ( 51)
 how you can transfer the parameter settings currently stored in the device into the »En-
gineer« project. ( 51)

 Tip!
In the »Engineer« an existing online connection can be recognised from the ani-
mated picture in the lower area of the Project view:

5.1 Establishing an online connection

If a device available in the Project view is connected to the PC via corresponding communi-
cation accessories (e. g. diagnostic adapter or system bus adapter), you can establish an on-
line connection to this device, for instance in order to carry out parameter settings in the
device, or to carry out a diagnostics of the device.

 Note!
Detailed information on the communication with a device can be found in the
Communication Manual for the respective interface, e. g. for the system bus
(CAN) in the "CAN Communication Manual".

 The functions for establishing/cancelling an online connection can always be executed

via the Toolbar or the Online menu:

Icon Menu command Keyboard com-

mand
Going online ( 40) <F4>

Going offline ( 47) <Shift>

L NKS=bk=J=MULOMMS 39
L-force | Engineer
Device functions in the online mode
Establishing an online connection

5.1.1 Going online

 How to establish an online connection to a device:

1. Select the device which the online connection is to be established to in the Project
view.
• The following illustration exemplarily shows the Servo Drives 9400 HighLine:

2. Click the icon or select the command OnlineGo online.

• If no online connection has been configured for the selected controller so far,
the Assignment of offline controllers dialog box will be displayed:

• The dialog box also appears if the online connection is built up via the command
OnlineGo online instead of using the Toolbar icon.
3. If several devices are itemised in the upper list field, select the respective device.
• If you for instance have selected a system module instead of a device in the
Project view, all devices available in this system module are specified in the up-
per list field.
4. Select the bus connection to be used from the Bus connection list field.
5. Carry out the further instructions as described in the subchapter for the corre-
sponding bus connection:
System bus (CAN) ( 42)
Diagnostic adapter ( 44)
Ethernet ( 45)
Gateway diagnostic adapter -> system bus (CAN) ( 46)

40 NKS=bk=J=MULOMMS L
 L-force | Engineer
Device functions in the online mode
Establishing an online connection

Establishing an online connection to several devices

If you click the symbol or select the command OnlineGo online, and if a project, sy-
stem module, or axis containing several devices is selected in the Project view instead of a
device, the Device assignment of offline devices dialog box always is displayed.
 In the upper list field all devices available in this system module are specified with the
corresponding communication settings; in the following example two
"Servo Drives 9400 HighLine":

 If you select a device from the upper list field, you can set or alter the communication
settings for this device in the lower dialog area.
 If you press Connect, the online connection is established to all devices with the check-
mark in the Selection column.
– By clicking the checkmark you can deactivate the selection.

Further information:
After establishing the online connection... ( 47)

L NKS=bk=J=MULOMMS 41
L-force | Engineer
Device functions in the online mode
Establishing an online connection

5.1.1.1 System bus (CAN)

Certain Lenze products are provided with an integrated system bus interface.
 Via the system bus interface among other things process data and parameter values
can be exchanged between the nodes via the system bus interface, furthermore the in-
terface enables the connection of further modules, like for example decentralised ter-
minals, operator and input devices, as well as external controls and master systems.
 The system bus interface transfers CAN objects following the CANopen (CiA DS301,
version 4.02) communication profile, which was generated under the umbrella associ-
ation of the CiA (CAN in Automation) in consistency with CAL (CAN Application Layer).

 Tip!
Detailed information about the subject "System bus (CAN)" can be found in the
"System bus (CAN)" Communication Manual of the same name.
System bus configurator ( 58)

42 NKS=bk=J=MULOMMS L
 L-force | Engineer
Device functions in the online mode
Establishing an online connection

 How to establish an online connection via the system bus (CAN):

1. Carry out the steps 1 ... 3 as described in the instructions in the chapter
"Going online". ( 40)
2. Select the entry "CAN system bus" from the Bus connection list field.
3. Press Search field devices.
• The Address assignment dialog box appears:

4. Select the corresponding controller from the Identified field devices list field.
5. Press OK.
• The Address assignment dialog box is closed and the selected Controller access
path is indicated in the Assignment of offline devices dialog box.
6. Click Connect.
• The dialog box is closed and the online connection with the device is built up.

Further information:
After establishing the online connection... ( 47)

L NKS=bk=J=MULOMMS 43
L-force | Engineer
Device functions in the online mode
Establishing an online connection

5.1.1.2 Diagnostic adapter

For the initial commissioning of a controller of the Servo Drives 9400 you can for instance
use the diagnostic adapter offered by Lenze, which at the controller is connected to the dia-
gnostic interface X6 and at the PC is connected to a free USB port:
The online connection with the diagnostic adapter is a 1:1 connection, except for the gate-
way diagnostic adapter -> system bus (CAN).

 How to establish an online connection via the diagnostic adapter:

1. Carry out the steps 1 ... 3 as described in the instructions in the chapter
"Going online". ( 40)
2. Select the entry "Diagnostic adapter" from the Bus connection list field.
3. Press Search field devices.
• The Address assignment dialog box appears:

4. Select the corresponding controller from the Identified field devices list field.
5. Press OK.
• The Address assignment dialog box is closed and the selected Device access path
(e.g. "DDCMP:/") is indicated in the Assignment of offline devices dialog box.

44 NKS=bk=J=MULOMMS L
 L-force | Engineer
Device functions in the online mode
Establishing an online connection

6. Click Connect.
• The dialog box is closed and the online connection with the device is built up.

Further information:
After establishing the online connection... ( 47)

5.1.1.3 Ethernet
By the use of controllers of the Servo Drives 9400 you can also establish an online connec-
tion via a TCP/IP network if the controller is equipped with an Ethernet communication
module and the PC also is provided with an access to this TCP/IP network (e. g. via a net-
work interface card).

 Note!
For the communication settings in the »Engineer« you require the IP address of
the controller.
• Via code C13000 the IP address currently set in the controller can be read out
and can also be changed (e. g. when an online connection has been estab-
lished via the diagnostic interface), for detailed information on this subject,
please see the documentation for the Servo Drives 9400.

 Tip!
Note down the set IP address using an adhesive label on the memory module.
Detailed information on the "Ethernet" can be found in the "Ethernet" Communi-
cation Manual of the same name.

L NKS=bk=J=MULOMMS 45
L-force | Engineer
Device functions in the online mode
Establishing an online connection

 How to establish an online connection via Ethernet:

1. Carry out the steps 1 ... 3 as described in the instructions in the chapter
"Going online". ( 40)
2. Select the entry "Ethernet" from the Bus connection list field.
3. Press Search field devices.
• The Enter IP address dialog box is displayed:

4. Enter the IP address of the controller.

• By pressing Ping you can carry out a simple test on whether a device can actually
be reached via the IP address set.
Please note: However, this has not necessarily got to mean that the intended
device can be reached via this IP address!
5. Press OK.
• The Enter IP address dialog box is closed and the Device access path selected is
shown in the Assignment of offline devices dialog box (e. g. "EPL:/
172_31_201_52/").
6. Click Connect.
• The dialog box is closed and the online connection with the controller is built up.

Further information:
After establishing the online connection... ( 47)

5.1.1.4 Gateway diagnostic adapter -> system bus (CAN)

For this version it is not possible yet to go online via Gateway diagnostic adapter -> system
bus (CAN).

Further information:
After establishing the online connection... ( 47)

46 NKS=bk=J=MULOMMS L
 L-force | Engineer
Device functions in the online mode
Establishing an online connection

5.1.1.5 After establishing the online connection...

...the available online connection to the device is displayed by a yellow highlighted icon in
the Project view:

 Stop!
If you change parameters in the »Engineer« while the controller is connected on-
line, the changes will be directly accepted by the controller!

Now you can use the icons and to easily build up and close a connection with the
device. The communication settings are only required when communication with a device
is built up for the first time.
 If you want to change the existing configuration, select the command OnlineGo on-
line to open the Assignment of offline devices dialog box and change the settings.
 When an online connection has been established, the »Engineer« displays the current
parameter settings of the controller with a yellow background col-
our. Representation of parameter values ( 22)

5.1.1.6 Going offline

 How to close an online connection to a device again:

1. Select the device the online connection of which is to be closed in the Project view.
• Alternatively you can select a system module in the Project view to close the on-
line connection to all devices contained in the system module.

2. Click the icon or select the command OnlineGo offline.

L NKS=bk=J=MULOMMS 47
L-force | Engineer
Device functions in the online mode
Control functions

5.2 Control functions

The functions described in the following subchapters can be carried out for a device if you
are connected online to the device.

 Stop!
If instead of a device a system module containing several devices is selected in
the Project view, the corresponding control function is carried out in all devices
of the system module to which an online connection is established!

 Note!
Before a control function is carried out within the device, there first is a safety
query on whether the function is to be carried out.
If you confirm the safety query with No, the corresponding control function is
not carried out.

 The control functions can be executed via the Toolbar or the Online menu:

Icon Menu command Be sure to observe: Keyboard com-

mand
Enabling the controller ( 49)
 Safety instructions ( 12)
<F8>

Inhibiting the controller ( 49) <F9>

Starting the application ( 50)

 Safety instructions ( 12)

Stopping the application ( 50)

48 NKS=bk=J=MULOMMS L
 L-force | Engineer
Device functions in the online mode
Control functions

5.2.1 Enabling the controller

 Danger!
During commissioning persons must keep a safe distance from the motor or the
machine parts driven by the motor. Otherwise there is a risk of injury by the mov-
ing machine parts.

 How to deactivate controller inhibit:

1. Select the controller for which the controller inhibit is to be deactivated in the
Project view.

2. Click the icon or select the command OnlineEnable controller.

3. Confirm the safety query on whether the controller is to be enabled with Yes.
• Then the controller inhibit in the controller is deactivated if there is no further
precondition for a controller inhibit (e. g. via digital terminal).
• By clicking or via the command OnlineInhibit controller you can reset the
controller inhibit within the controller.

5.2.2 Inhibiting the controller

 How to set the controller inhibit:

1. Select the controller for which the controller inhibit is to be set in the Project view.

2. Click the icon or select the command OnlineInhibit controller.

3. Confirm the safety query on whether the controller is to be inhibited with Yes.
• The controller then is inhibited.

• By clicking or via the command OnlineEnable controller you can deactivate

the controller inhibit within the controller again.

L NKS=bk=J=MULOMMS 49
L-force | Engineer
Device functions in the online mode
Control functions

5.2.3 Starting the application

 Danger!
During commissioning persons must keep a safe distance from the motor or the
machine parts driven by the motor. Otherwise there would be a risk of injury by
the moving machine parts.

 How to start the application in the controller:

1. Select the controller for which the application is to be started in the Project view.

2. Click the icon or select the command OnlineStart application.

3. Confirm the safety query on whether the application in the controller is to be start-
ed with Yes.
• Then the application in the controller is started.
• By clicking or via the command OnlineStop application you can stop the
application in the controller again.

5.2.4 Stopping the application

 How to stop the application in the controller:

1. Select the controller for which the application is to be stopped in the Project view.

2. Click the icon or select the command OnlineStop application.

3. Confirm the safety query on whether the application in the controller is to be
stopped with Yes.
• Then the application in the controller is stopped and controller inhibit is set.
• By clicking or via the command OnlineStart application you can start the
application in the controller again.

50 NKS=bk=J=MULOMMS L
 L-force | Engineer
Device functions in the online mode
Application and parameter set transfer

5.3 Application and parameter set transfer

If an online connection to the device has been established you can transfer the parameter
set of the device to the »Engineer« project, and vice versa, furthermore you can transfer a
(modified) application from the »Engineer« into the device.

 Stop!
If instead of a device a system module containing several devices is selected in
the Project view, the transfer function selected is carried out with all devices of
the system module to which an online connection is established!

 The transfer functions can be executed via the Toolbar or the Online menu:

Icon Menu command Keyboard com-

mand
Reading the parameter set from the device ( 52) <F7>

Transferring the parameter set to the device ( 53) <F5>

Save parameter set ( 56)

Compare parameters ( 55)

Transferring the application to the device ( 57)

L NKS=bk=J=MULOMMS 51
L-force | Engineer
Device functions in the online mode
Application and parameter set transfer

5.3.1 Reading the parameter set from the device

By means of this transfer function, the parameter set that is currently available in the de-
vice is transferred to the »Engineer« project.

 How to transfer the parameter set from the device to the »Engineer«:
1. If no online connection has been established yet, click on the icon in the Toolbar
to establish an online connection to the device.
Establishing an online connection ( 39)

2. Click on the icon or select the command OnlineRead parameter set from the
device.
• The Transfer dialog box appears:

3. Click Start to start data transmission.

• The progress of the data transmission is shown in the form of a bar display.
• After the data transmission has been completed successfully, the status "OK" is
displayed behind the corresponding device.
4. Press Close to close the Transfer dialog box again.

52 NKS=bk=J=MULOMMS L
 L-force | Engineer
Device functions in the online mode
Application and parameter set transfer

5.3.2 Transferring the parameter set to the device

By means of this transfer function, the (offline) parameter set of the »Engineer« project is
transferred to the device.

 How to transfer the parameter set from the »Engineer« to the device:
1. If no online connection has been established yet, click on the icon in the Toolbar
to establish an online connection to the device.
Establishing an online connection ( 39)

2. Click on the icon in the Toolbar or select the command OnlineTransfer param-
eter set to the device.
• The Transfer parameter set to the device dialog box is displayed:

• In the group field Details you can select the parameters which are not to be
transferred to the device.

L NKS=bk=J=MULOMMS 53
L-force | Engineer
Device functions in the online mode
Application and parameter set transfer

• If you press Details... in the group field Details, all parameters which are not
transferred to the device are itemised in the Parameter set details dialog box:

• Press Close to close the Parameter set details dialog box again.
3. Click Start to start data transmission.
• The progress of the data transmission is shown in the form of a bar display.
4. Confirm Save parameter set dialog box with Yes to save the parameter set with
mains failure protection in the device.
• If you confirm the dialog box with No instead, the altered parameter settings
only are maintained until the next mains switching of the device.
• After the data transmission has been completed successfully, the status "OK" is
displayed behind the corresponding device in the Transfer parameter set to the
device dialog box.
5. Press Close to close the Transfer parameter set to the device dialog box again.

54 NKS=bk=J=MULOMMS L
 L-force | Engineer
Device functions in the online mode
Application and parameter set transfer

5.3.3 Compare parameters

Use this function to read out the current parameter settings of the device and to compare
them to the (offline) parameter settings of the »Engineer« project.

 How to carry out a parameter comparison:

1. If no online connection has been established yet, click on the icon in the Toolbar
to establish an online connection to the device.
Establishing an online connection ( 39)
2. Select the command OnlineCompare parameters.
• The parameter settings of the device are read out and the process of the data
transmission is displayed in the Transfer dialog box.
• After the data transmission has been completed, the result of the comparison is
displayed in the form of a parameter list in the Compare parameters dialog box.
Structure of the parameter list
• In the default setting, the parameter list only specifies the parameters, the val-
ue of which in the device differs from the parameter value saved in the project.

Structure of the parameter list

After executing the command OnlineCompare parameters and after the data transmis-
sion has been carried out, the result of the comparison is displayed in the Compare param-
eters dialog box in the form of a parameter list:

 The parameters are classified in different categories and subcategories which you se-
lect via the buttons on the left.
– If you click on a category button, the available subcategories are shown and can be
selected via mouse-click.
– If you change to another category, the subcategories of the previously selected cate-
gory are masked out again.

L NKS=bk=J=MULOMMS 55
L-force | Engineer
Device functions in the online mode
Application and parameter set transfer

 In the parameter list on the right all parameters of the category/subcategory are
shown.
– By clicking on the head of the respective column you can alter the sorting of the pa-
rameter list and switch between ascending and descending sorting.
– If you select the first category "Code list", all parameters of the corresponding device
are displayed in the parameter list.
– The icon behind a parameter value indicates that the value in the device differs
from the parameter value saved in the project.
 Below the parameter list, in a so-called "information area", further information on the
parameter selected are displayed on the left side.
– Using the command Information area in the Context menu of the parameter list you
can show or hide the information area.

Comparison operation
The Compare parameters dialog box in the upper position is provided with an individual
toolbar.
 Click a symbol to execute the associated function:

Icon Function
Accept the parameter setting(s) selected of the project in the device.
• Via <Shift> and <Ctrl you can select several parameters at the same time, the settings of which
are to be accepted in the device.
Accept the parameter setting(s) selected of the device in the project.
• Via <Shift> and <Ctrl you can select several parameters at the same time, the settings of which
are to be accepted in the project.
Only show the parameters which are different in the project and the device.

Mask out all parameters featuring an only-read access.

5.3.4 Save parameter set

In order to prevent parameter settings carried out in the device from being lost by mains
switching, you have to explicitly save the parameter set with mains failure protection in
the device.

 Click on the icon in the Toolbar or select the command OnlineSave parameter
set to save the current parameter settings of the device selected in the Project view
with mains failure protection.

56 NKS=bk=J=MULOMMS L
 L-force | Engineer
Device functions in the online mode
Application and parameter set transfer

5.3.5 Transferring the application to the device

By means of this transfer function, the application is transferred from the »Engineer« pro-
ject to the device.

 Note!
Together with the application, also the complete (offline) parameter set is trans-
ferred to the 9400 controller.

 How to carry out an application & parameter set download:

1. If no online connection has been established yet, click on the icon in the Toolbar
to establish an online connection to the device.
Establishing an online connection ( 39)

2. Click on the icon in the Toolbar or select the command OnlineTransfer appli-
cation to the device.
• The Transfer application to the device dialog box is displayed:

3. Press Start.

L NKS=bk=J=MULOMMS 57
L-force | Engineer
Device functions in the online mode
System bus configurator

4. Confirm Note dialog box with Yes to continue with the data transmission.
• If you confirm the dialog box with No instead, the data transmission is not ef-
fected.
Then the application and afterwards the parameter set are transferred to the de-
vice.
• If an application has already been started in the device, accordingly a query on
whether the application is to be stopped before is effected; in both cases con-
firm this dialog box with Yes.
• The progress of the data transmission is shown in the form of a bar display.
5. Confirm Application stopped dialog box with Yes to start the downloaded applica-
tion in the device.
6. Confirm the query on whether the application in the device is to be started with
Yes.
• After the data transmission has been completed successfully, the status "OK" is
displayed behind the corresponding device in the Transfer application to the de-
vice dialog box.
7. Press Close to close the Transfer application to the device dialog box again.

5.4 System bus configurator

Via the menu command OnlineSystem bus configurator you open the system bus confi-
gurator.
By the use of the system bus configurator you can comfortably configure the communica-
tion parameters of the Lenze PC system bus adapters connected to the PC

5.5 Diagnostic interface of the communication configurator

Via the menu command OnlineDiagnostic interface configurator you open the commu-
nication configurator of the diagnostic interface.

58 NKS=bk=J=MULOMMS L
 L-force | Engineer
Project structure

6 Project structure
In the Project view you create the hierarchical project structure, which usually results from
 the functional segmentation of the entire system into system parts
(e. g. conveyor and press) and
 the devices which are available or intended (e. g. drive controllers, controls, motors).

 Tip!
On the basis of your system you decide for yourself on the structuring of your
project and therefore on the structure displayed in the Project view!
You can describe a hierarchical system structure with several levels, but you can
also select a "flat" modular design.

Modularisation by means of system modules and axes

In the project view a system part is represented by a so-called system module.
 The task of a system module is the realisation of a specific system function (e. g. wind-
ing, positioning, pressing).
 A system module can contain devices, communication networks, applications, and doc-
umentation.
 For representing hierarchical system structures a system module can also contain fur-
ther system modules and so-called axes, which also have structuring purposes.
 An axis is a special variant of a system module and basically contains one controller and
one motor, but depending on the application it may contain further devices such as
gearboxes.

L NKS=bk=J=MULOMMS 59
L-force | Engineer
Project structure

Structure of the system structure

If you create a new (empty) project, first only the Project element with the name of the
prject is shown in the project view:

Extending the system structure according to the top-down method

On the basis of this state, you can now complete the system structure step by step in ac-
cordance with the Top-down method by inserting further system modules and/or axes:

Inserting system modules ( 62)

Inserting axes ( 64)

Adding components
After you have described the system structure by means of system modules and axes, you
add the corresponding components (controllers, control systems, motors, I/O systems, ge-
arboxes, etc.) to this elements, if this hasn't already been done when the axis/axes were
inserted:

Adding components ( 68)

60 NKS=bk=J=MULOMMS L
 L-force | Engineer
Project structure

 Tip!
For purposes of documentation, you can add notes like documents available in
electronic form (pictures, circuit diagrams, CAD data, etc.) to every element in the
Project view. Documentations concerning the entire system can for instance be
added to the Project element. Adding documentation ( 82)
If you select an element in the Project view and press the function key <F2>, you can
change the designation of the element:

• Press the <Input key> to accept the change, or the <ESC> key to discard the
change.

Next steps

If you have added all devices to your project, the structure of the project has
been created.
 Then you can extend the system structure by a logical view to networks
available in the system. Network ( 92)
Network

L NKS=bk=J=MULOMMS 61
L-force | Engineer
Project structure
Inserting system modules

6.1 Inserting system modules

You can insert system modules in the Project element, but also in system modules that are
already available, e. g. to describe a hierarchical system structure with several levels like
this:

 How to insert a system module:

1. Either select
• the project element in the Project view, or
• select a system module that is already available , which a further system
module is to be inserted in.

2. Click the icon.

• The Insert system module dialog box appears:

3. Enter a name for the system module in the Designation text field.
• Optionally you can enter a comment on the system module in the Comment
text field.
4. Press OK.
• The dialog box is closed and the system module is inserted in the highlighted el-
ement.

62 NKS=bk=J=MULOMMS L
 L-force | Engineer
Project structure
Inserting system modules

Properties, components & documentation

If you select a system module in the Project view, the Properties, Components and Docu-
mentation tabs are provided in the Operating range.
 General information on the system module, e. g. the version and the editor, can be en-
tered in the Properties tab.
 In the Components tab all components of the system module are listed.
 In the Documentation tab you can add notes and documents in electronic form to the
system module. Adding documentation ( 82)

L NKS=bk=J=MULOMMS 63
L-force | Engineer
Project structure
Inserting axes

6.2 Inserting axes

For representing hierarchical system structures, you can insert one or more axes in the pro-
ject element or in a subordinate system module, which also have the purpose of structu-
ring.
 An axis is a special variant of a system module and basically contains one controller and
one motor, but depending on the application it may contain further devices, such as
gearboxes and encoders.

 Tip!
If you have inserted an axis, you can also select the further components of the axis
(controller, motor, gearbox, etc.). By this, you do not have to repeatedly call the
function Adding components.

ProjectDesigner
By additionally installing the »ProjectDesigner« you can insert more than 15 controllers or
I/O modules in the current »Engineer« version.

 How to insert an axis:

1. Select the system module which the axis is to be inserted in from the Project
view.
• An axis can also be directly inserted in the project element; for modularising the
system, however, we recommend the use of system modules.

2. Click the icon to open the assistant for adding an axis.

64 NKS=bk=J=MULOMMS L
 L-force | Engineer
Project structure
Inserting axes

Step 1 - properties

3. Enter a name for the axis in the Designation text field.

• Optionally you can enter a comment on the axis in the Comment text field.
• If the control field Select individual components of the axis is activated, you can
select the components (controller, motor, etc.) which the axis is to contain, after
pressing Continue.
4. Press Continue or complete.
• If the control field Select individual components of the axis has been deactivat-
ed, the dialog box is closed and the axis is inserted in the highlighted element
without further components. Of course you can add further components to the
axis or remove them again anytime later on.

L NKS=bk=J=MULOMMS 65
L-force | Engineer
Project structure
Inserting axes

Step 2 - components

5. Select the components the axis is to contain.

6. Press Next.
• In the following dialog steps you can now select the components for the axis
from the respective catalogs.
• If you press Complete in the last step, the dialog box is closed and the axis is in-
serted in the highlighted element with the components selected.

66 NKS=bk=J=MULOMMS L
 L-force | Engineer
Project structure
Inserting axes

Properties, components & documentation

If you select an axis in the Project view, the Properties, Components and Documentation
tabs are provided in the Operating range.
 General information on the axis, e. g. the version and the editor, can be entered in the
Properties tab.
 In the Components tab all components of the axis are listed.
 In the Documentation tab you can add notes and documents in electronic form to the
axis. Adding documentation ( 82)

L NKS=bk=J=MULOMMS 67
L-force | Engineer
Project structure
Adding components

6.3 Adding components

If you have divided the entire system into functional system parts by means of system mo-
dules and axes, you can afterwards add the corresponding components to these structu-
ring elements:

Adding controllers ( 69)

Adding a motor ( 75)

Adding an I/O system ( 77)

Adding gearboxes ( 80)

Applications & device modules

When you add a controller, you can simultaneously assign an application to this device;
furthermore, where applicable, you can assign device modules to the device, if the device
is provided with appropriate extension possibilities.

Assigning an application to a device ( 72)

Assigning (a) device module(s) to a device ( 73)

 Tip!
You can also select the components of an axis when you insert the axis if you acti-
vate the Select individual components of the axis control field for this in the first
step and select the corresponding components in the second step.
Inserting axes ( 64)

Tabs of the different components

If you select a component in the Project view, different tabs are provided in the Operating
range.
 In the Properties tab the designation and identification of the component is displayed.
 In the All parameters tab all parameters of the component are listed.
 In the Documentation tab you can add notes and documents in electronic form to the
component. Adding documentation ( 82)

68 NKS=bk=J=MULOMMS L
 L-force | Engineer
Project structure
Adding components

6.3.1 Adding controllers

 Tip!
You can also select the controller and further components when you insert the axis,
if you activate the Select individual components of the axis control field for this in
the first step and select the corresponding components in the second
step. Inserting axes ( 64)
Even if you add a controller to an already existing axis or system module later on,
you can select the further components (application, motor, gearbox) which are to
be inserted at the same time.

 How to add a controller:

1. Select the system module or the axis which the controller is to be inserted in
from the Project view.

2. Click the icon to open the assistant for adding a component.

Step 1 - component

3. Unless it is already displayed, select the Controller tab.

• All controllers available are displayed in the Search results list field.
4. If required, define Search options to accordingly narrow down the controllers avail-
able:
• Designation:
String which has to be contained in the designation of the controller.
• Type/manufacturer:
Limitation of the selection to a specific type or manufacturer.

L NKS=bk=J=MULOMMS 69
L-force | Engineer
Project structure
Adding components

5. After a change with regard to the search options, press Search to update the selec-
tion.
• Then only the controllers complying with the features set in the Search options
are itemised in the Search results list field.
• If no Search options are set, all controllers available are shown.
6. Select the controller to be inserted in the Search results list field.
• On the right further details and technical data on the controller selected are dis-
played.
7. Press Next.
Step 2 - device modules
If the controller selected supports device modules, you can select the device mod-
ules available in this step.
• If the controller does not support device modules, this step is not displayed.

8. Press Select... to carry out the selection of the corresponding device module.
• The selection is carried out in the same way as the selection of the controller.
• Accept the respective selection by OK.
• Via the Remove button, you can remove a device module which has already
been selected again.
9. Press Next.

70 NKS=bk=J=MULOMMS L
 L-force | Engineer
Project structure
Adding components

Step 3 - further components

10. Select the further components which are to be added to the controller.
• If you do not select a device application in this step, a so-called "empty" device
application is assigned to the controller, which you can replace by another de-
vice application anytime. Assigning an application to a device ( 72)
11. Press Continue or Complete.
• If no further components have been selected, the dialog box is closed and the
controller is inserted in the axis or system module highlighted without further
components.
• In the following steps you can carry out the required selection for the highlight-
ed components in the corresponding catalogs.
• If you press Complete in the last step, the dialog box is closed and the controller
is inserted in the highlighted element with the further components selected.

L NKS=bk=J=MULOMMS 71
L-force | Engineer
Project structure
Adding components

6.3.2 Assigning an application to a device

If you add a controller and in doing this activate the Application control field in the step
"further components", you can select an application for the controller in the following step:

 Note!
If you do not select an application, a so-called "empty" device application is as-
signed to the controller, which you can replace by another device application an-
ytime.

72 NKS=bk=J=MULOMMS L
 L-force | Engineer
Project structure
Adding components

6.3.3 Assigning (a) device module(s) to a device

If the controller is equipped with device modules (e. g. memory module, safety module,
function and/or communication module), you can assign them to the controller now when
selecting the controller or anytime later on.

 Tip!
The steps described in the following can also be carried out to replace a device
module already assigned to a device by another device module.

 How to assign device modules to a device:

1. Select the device which device modules are to be assigned to in the Project view.

2. Click the icon.

• The Insert device module dialog box appears:

• On the right the device modules which are already assigned to the device are
displayed.
3. Press the corresponding Select... button to carry out the selection of the corre-
sponding device module or to change an assignment which is already available.
• The selection is carried out in the same way as the selection of a device.
• Accept the respective selection by OK.
4. Press Complete.
• The dialog box is closed and the device module(s) selected is/are assigned to the
device selected in the Project view.

L NKS=bk=J=MULOMMS 73
L-force | Engineer
Project structure
Adding components

The device modules assigned to a device are shown below the device in the Project view:

Properties, memory module manager & documentation

If you select a device module in the Project view, the Properties, Memory module manager
and Documentation tabs are provided in the Operating range.
 In the Properties tab the designation and identification of the device module is dis-
played.
 In the Memory module manager tab all parameters of the device module are listed.
 In the Documentation tab you can add notes and documents in electronic form to the
device module. Adding documentation ( 82)

74 NKS=bk=J=MULOMMS L
 L-force | Engineer
Project structure
Adding components

6.3.4 Adding a motor

 Tip!
You can also select the motor and further components when you insert the axis if
you activate the Select individual components of the axis control field for this in
the first step and select the corresponding components in the second
step. Inserting axes ( 64)

 How to add a motor:

1. Select the system module or the axis which the motor is to be inserted in
from the Project view.

2. Click the icon to open the assistant for adding a component.

Step 1 - component
3. Select the Motors tab.
• All motors available are displayed in the Search results list field.

L NKS=bk=J=MULOMMS 75
L-force | Engineer
Project structure
Adding components

4. If required, define Search options to accordingly narrow down the motors availa-
ble:
• Designation:
String which has to be contained in the designation of the motor.
• Type/manufacturer:
Limitation of the selection to a specific type or manufacturer.
• C86 value
If you use a Lenze motor, you can enter the C86 value specified on the name-
plate of the motor, in order to carry out a specific selection.
• Rated power
Limitation of the selection to a specific rated power range.
5. After a change with regard to the search options, press Search to update the selec-
tion.
• Then only the motors complying with the features set in the Search options are
itemised in the Search results list field.
• If no Search options are set, all motors available are shown.
6. Select the motor to be inserted in the Search results list field.
• On the right further details and technical data on the motor selected are dis-
played.
7. Press Complete.
• The dialog box is closed and the selected motor is inserted in the highlighted el-
ement.

Properties, motor parameters & documentation

If you select a motor in the Project view, the Properties, Motor parameters and Documen-
tation tabs are provided in the Operating range.
 In the Properties tab the designation and identification of the motor is displayed.
 In the Motor parameters tab all parameters of the motor, and also the associated con-
troller are specified.
 In the Documentation tab you can add notes and documents in electronic form to the
device module. Adding documentation ( 82)

76 NKS=bk=J=MULOMMS L
 L-force | Engineer
Project structure
Adding components

6.3.5 Adding an I/O system

 How to add an I/O system:

1. Click the icon to open the assistant for adding a component.
Step 1 - component
2. Select the I/O system tab.
• All I/O systems available are displayed in the Search results list field.

3. If required, define Search options to accordingly narrow down the I/O systems
available:
• Designation:
String which has to be contained in the designation of the I/O system.
• Manufacturer:
Limitation of the selection to a specific type or manufacturer.
4. After a change with regard to the search options, press Search to update the selec-
tion.
• Then only the I/O systems complying with the features set in the Search options
are itemised in the Search results list field.
• If no Search options are set, all I/O systems available are shown.
5. Select the I/O system to be inserted in the Search results list field.
• On the right further details and technical data on the I/O system selected are
displayed.

L NKS=bk=J=MULOMMS 77
L-force | Engineer
Project structure
Adding components

6. Press Complete.
• The dialog box is closed and the selected I/O system is inserted in the highlight-
ed element.

6.3.5.1 Adding a modular I/O system

 Note!
Inserting a modular I/O systems is effected in the same way as inserting a com-
pact I/O system. One module at a minimum has to be inserted at the CAN gate-
way base station.

 How to add a modular I/O system:

1. Select a CAN gateway in the Insert component dialog box on the I/O system tab and
press Next.
• The Insert component dialog box with the represented CAN gateway base sta-
tion opens.

2. Insert the corresponding modules by Attach module or Insert module.

• By Attach module the module selected is placed at the end. By Insert module the
module selected is inserted in front of the module highlighted.
• The other buttons can be used for editing the system.

 Note!
Depending on the I/O module inserted, different tabs are displayed.

78 NKS=bk=J=MULOMMS L
 L-force | Engineer
Project structure
Adding components

Tabs of the I/O systems

If you select an I/O module in the Project view, different tabs are provided in the Operating
range. Thereby it depends on the module which tabs are shown.

CAN gateway
 In the Properties tab project information and catalog information of the I/O module is
displayed.
 In the Configuration tab the compiled modular system is presented.
 In the Ports tab the input and output ports of the CAN gateway are presented.
 In the All parameters tab the codes for parameterising the CAN gateway are shown.
 In the Documentation tab you can add notes and documents in electronic form to the
device module. Adding documentation ( 82)

CAN gateway module

 In the Properties tab project information and catalog information of the I/O module is
displayed.
 In the Status tab the status of the input and outputs is displayed.
 In the Parameters tab all parameters of the module are listed. Via the parameter data
of the digital modules you define whether the control signals are to be transmitted in
the original polarity or in inverted polarity.
 In the Documentation tab you can add notes and documents in electronic form to the
device module. Adding documentation ( 82)

Compact modules
 In the Properties tab the designation and identification of the I/O module is displayed.
 In the Configuration tab the compact system is presented.
 In the Status tab the status of the input and outputs is displayed.
 In the Parameters tab all parameters of the module are listed. Via the parameter data
of the digital modules you define whether the control signals are to be transmitted in
the original polarity or in inverted polarity.
 In the Ports tab the input and output ports of the module are presented.
 In the All parameters tab the codes for parameterising the compact module are shown.
 In the Documentation tab you can add notes and documents in electronic form to the
device module. Adding documentation ( 82)

L NKS=bk=J=MULOMMS 79
L-force | Engineer
Project structure
Adding components

6.3.6 Adding gearboxes

In addition to components like controllers, motor, and I/O systems you can also insert ge-
arboxes in system modules and axes.

 Tip!
You can also select the gearbox and further components when you insert the axis,
if you activate the Select individual components of the axis control field for this in
the first step and select the corresponding components in the second
step. Inserting axes ( 64)

 How to add a gearbox:

1. Select the system module or the axis which the gearbox is to be inserted in
from the Project view.

2. Click the icon.

• The Insert gearbox dialog box appears:

3. Enter a name for the gearbox in the Designation text field.

• Optionally you can enter a comment on the gearbox in the Comment text field.
4. Enter the corresponding number of teeth of the gearbox in the Number of teeth
(numerator) and Number of teeth (denominator) text fields.
• Below the Number of teeth (denominator) text field the gearbox factor result-
ing from this is displayed.
5. Press OK.
• The dialog box is closed and the gearbox is inserted in the highlighted element.

80 NKS=bk=J=MULOMMS L
 L-force | Engineer
Project structure
Adding components

Properties, gearbox parameters & documentation

If you select an inserted gearbox in the Project view, the Properties, Gearbox parameters
and Documentation tabs are provided in the Operating range.
 In the Properties tab the designation and identification of the gearbox is displayed.
 In the Gearbox parameters tab you can set the transmission ratio and the moment of
inertia for the gearbox.
 In the Documentation tab you can add notes and documents in electronic form to the
gearbox. Adding documentation ( 82)

L NKS=bk=J=MULOMMS 81
L-force | Engineer
Project structure
Adding documentation

6.4 Adding documentation

Via the Documentation tab you can add notes and documents that are available in electro-
nic form to each element in the Project view.
 Like this you can document the corresponding element or the entire system and pro-
vide important information on the project to the persons editing the project, e. g.:
– Sketches & photographs of the system
– Processing tasks,
– Work instructions,
– Circuit diagrams,
– CAD data,
– Lists of parts, etc.

On the left in the Documentation

list all documents available for
the element are listed.

On the right the properties of the

element selected from the Docu-
mentation list are shown.

If you select the Preview from the

View list field, on the right a pre-
view of the element selected
from the Documentation list is
shown instead.

82 NKS=bk=J=MULOMMS L
 L-force | Engineer
Project structure
Adding documentation

 Tip!
In the preview all document types which can also be displayed by the Microsoft®
Internet Explorer, e. g. HTML and ASCII files, graphics in JPEG or GIF format, or also
PDF documents (if the Adobe® Reader® is installed) can be shown.
Which document types can be shown in detail depends on the display plug-ins in-
stalled for the Microsoft® Internet Explorer.

Editing the documentation list

The Documentation list is edited via the icons in the toolbar above.
 Click a symbol to execute the corresponding function:

Icon Function
Insert note

Copy file into the project

• After you have selected the corresponding file within your workplace environment, a copy of this
file is stored in the project folder.
Add a linkage to a file
• After you have selected the corresponding file within your workspace environment, a linkage to
this file is stored in the project folder.
Open document
• By means of this function you can open a selected document from the documentation list.

Save document selected

• By means of this function you can save a copy of the selected document from the project folder
to a selectable folder within your workplace environment.
Delete element selected from the documentation list

Display area
Above the display area, the View list field shows the selection preview and the file charac-
teristics:

Command Function
Preview Display properties of the element selected from the documentation list
File properties Display preview of the document selected, or text of the note selected

L NKS=bk=J=MULOMMS 83
L-force | Engineer
Communication between the controllers
Separation of the application and the network

7 Communication between the controllers

In the »Engineer« communication between the controllers can be effected via the applica-
tion level or the network level.

7.1 Separation of the application and the network

 By separating the two levels you can generate an application and decide later on via
which communication medium the information is to be exchanged during the runtime.
 The »Engineer« provides the opportunity to you to just concentrate on the application.
 The creation of process data objects and the assignment of interfaces (ports) are carried
out by the »Engineer«.
 If you have generated an application, you possibly have to carry out a few settings. This
is referred to in another part of the documentation.
Application level ( 84)
In the application level the interfaces (ports) of devices for an application are defined and
connected (interconnected).
Network level ( 85)
In the network level the transfer-specific parameters are defined. These are
 the creation of networks
 adding nodes to the networks
 the parameterisation of process data objects

7.1.1 Application level

In the application level you define the interfaces of an application. This can be a program
or a fixed application. The definition of the interface is effected by the port editor. The port
editor can be called for an application on a device itself and for a higher-level application,
the machine application.
The machine application serves as a structuring means for the generation of system mod-
ules which already contain a predesigned interconnection. Generating machine applica-
tions ( 138)

7.1.1.1 Process data object (PDO)

A process data object can serve as a container for several ports. Several ports can be trans-
mitted by one process data object. The assignment of the ports to the process data objects
can be effected automatically or manually. CAN objects ( 106)

7.1.1.2 Ports
A port is an interface which enables an application to transmit process data to the outside
or receive it from the outside respectively.
Port editor ( 125)

84 1.6 EN - 08/2006 L
 L-force | Engineer
Communication between the controllers
Separation of the application and the network

7.1.1.3 Variable types

Variable type Information

"Simple" variable type This type only contains one variable of a basic data type like INT, WORD, etc.
( 129) • To be used if it is not known how the devices are comprehensively interconnect-
ed. A data consistency between the variables is not required.
"Record" variable type This type contains one or several variables of a basic data type like INT, WORD, etc.
( 130) • To be used in a network, e. g. a controller with a predesigned application, where-
by the data structure is always identical.
"Array" of byte variable type This type contains one or several variables of the same basic data type like INT,
( 130) WORD, etc.
• To be used for simple binary systems (terminals).

7.1.2 Network level

In the network level, the node created can be assigned to a network and parameterised. If
a network object, e.g. system bus (CAN) has been selected in the project tree, comprehen-
sive settings are possible via the tabs displayed. Nodes ( 98)

7.1.3 Connection between application and network

In order to transfer the data from the port via a communication medium, e.g. system bus
(CAN), they have to be assigned to a process data object.

PDO_RX1 PDO_TX1

PDO_RX2 PDO_TX2

One or more ports can be assigned to a process data object.

Defining the connection

The type of connection is defined in the port editor when creating a new port. If a port was
created already, the type of connection can be changed with the Change bus system....
The Interface selection only those communication interfaces are offered which are availa-
ble on the device.

L 1.6 EN - 08/2006 85
L-force | Engineer
Communication between the controllers
Separation of the application and the network

7.1.3.1 User definitions

The kind of port date transfer can be influenced differently.

1. In case of an interconnection, interface and process data object are selected automati-
cally by the system.
2. The interface is defined by the user, the process data object is defined by the system.
The system selects the process data object in case of an interconnection. Thus this se-
lection indirectly defines the bus system.
3. The process data object is defined. Thus, the interface and the bus system are indirectly
defined.

 Note!
During the assignment of ports to process data objects, no checks are made with
regard to data width and existing mapping entries. Only if you compile the
project using the menu command ExtrasUpdata project, these checks are
made and fault messages are output in case of violation and the compiling proc-
ess is cancelled.
If you adapt a port up to the process data object level, the flexibility with regard
to automatic combination of interconnections will be reduced.

7.1.4 Establishing the connection

Basically there are three types of data communication between two ports via a network.
Automatic connection ( 87)
Manual connection ( 87)
Predefined connection set connection ( 88)

86 1.6 EN - 08/2006 L
 L-force | Engineer
Communication between the controllers
Separation of the application and the network

7.1.4.1 Automatic connection

For this purpose a network object in the »Engineer« and a machine application are re-
quired.
 The nodes which are to communicate with each other have to be assigned to the net-
work.
 The applications have to be assigned to the machine application.

 It is not necessary to assign an interface or a process data object to the ports. If it is re-
quired, your specifications are considered.
 For each interconnection featuring a starting point and maximally one end point as
port of an application the ports are combined to process data objects.
 It is checked whether the end points match with regard to the data size and storage
partitioning.
By means of the specification for realising the individual ports and of the information from
the interconnection within the machine applications and from the formation of networks
via the menu command ExtrasUpdate project it is tried to transform the information into
communication objects during the compilation process.

7.1.4.2 Manual connection

The manual connection can be effected without a network object in the »Engineer« and
without a machine application.
 Directly assign the ports to the process data objects and set the communication param-
eters yourself like COB-ID for CAN.
This procedure is reasonable for external devices without »Engineer« catalogs and for bus
systems if no network is provided in the »Engineer«.

 Tip!
Observe that send and receive process data objects, data structure, and communi-
cation parameters comply with each other.

L 1.6 EN - 08/2006 87
L-force | Engineer
Communication between the controllers
System bus CAN - network

7.1.4.3 Predefined connection set connection

 The Use predefined connection set control field in the Settings tab of the CAN on board
only is active if you have not assigned a network to the CAN node.
If the Use pre-defined connection set control field is activated, the COB-IDs of the CAN
process data objects are derived from the node address.

Process data object COB-ID

PDO_RX1 0x200 + node address
PDO_RX2 03200 + node address
PDO_RX3 0x400 + node address
PDO_RX4 0x500 + node address
PDO_TX1 0x180 + node address
PDO_TX2 0x280 + node address
PDO_TX3 0x380 + node address
PDO_TX4 0x480 + node address

 Tip!
Observe that send and receive process data objects, data structure, and communi-
cation parameters comply with each other.

7.1.4.4 Mixed connection

A mixed form of the connections Automatic connection ( 87) and
Manual connection ( 87) is possible.
A mixed form of the connection Predefined connection set connection ( 88) and another
one is not possible.

7.2 System bus CAN - network

7.2.1 CAN objects

 Note!
The CAN objects tab cannot be edited. The information displayed are only valid
if the project is completely compiled.

88 1.6 EN - 08/2006 L
 L-force | Engineer
Communication between the controllers
System bus CAN - network

The CAN objects tab provides an overview of the process data objects which are transmit-
ted via a network.
The following is displayed:
 Objects which have been created by a device-independent interconnection
 Objects the transfer of which can be enforced by deselecting the Automatic allocation
in the Process data objects tab.
Press the Linking send and receive objects… to open a dialog which displays the linkage of
transmitted and received process data objects in tree topology. For a better orientation, the
send process data objects are arranged according to nodes.

7.2.2 Synchronisation

The Synchronisation serves to

 determine the node which is to send a sync object,
 determine the nodes which are to adapt their internal control cycle to this sync object,
 determine the parameters for further device-specific sync receivers.

 In the Sync source group field the sync source with COB-ID and time interval is deter-
mined.
 In the Sync receiver group field all nodes of the network are displayed in tabular form.
– The Appl. (*1) column indicates if, on the corresponding device, the process is to be
synchronised to the SYNC object. If no process can be synchronised tot he SYNC ob-
ject on the device, the respective cell will be inhibited.
– The "PDO (*2)" column indicates if a process data object of this node possesses the
"Synchronised" transfer mode.
 In the Parameter group field, further parameters of the selected SYNC receivers are dis-
played. These parameters are device-specific and are not set automatically.

L 1.6 EN - 08/2006 89
L-force | Engineer
Communication between the controllers
System bus CAN - network

7.2.3 Process data objects

The Process data objects tab indicates the currently available process data objects for a
node.
 In the Process data object group field a send or receive data object can be selected. De-
pending on the selection, the interface of the tyb changes.
 The Create Send PDO, Create Receive PDO and Delete PDO buttons serve to create or
delete process data objects.
 In the Transfer parameter group field the respective transfer parameters of the process
data object are displayed. The option depends on the process data object selected and
the functionality of the node. The No. of Sync signals can only be edited when "Synchro-
nous" has been selected in the Transfer mode selection field.
 Usually, the COB-ID are assigned through a generation (Update project). If a process
data object is required for an interconnection, a valid COB-ID will be entered for the
sender and all receivers. If a process data object is not used, it will be inhibited - normal-
ly by setting bit[31].
 If you want to enforce the sending or receiving of a process data object, this is not pos-
sible by selecting the Automatic allocation control field and setting the required COB-
ID.

 Note!
You are responsible for the correct setting and effects on the system!

7.2.3.1 Packing ports into process data objects

The mechanism for packing ports into process data objects works identically for all net-
works offering a network configurator in the »Engineer«. The realisation of the mapping
information into device-specific information is taken over by the device-specific genera-
tors.
The objective is to send as few process data objects via the bus systems as possible.

90 1.6 EN - 08/2006 L
 L-force | Engineer
Communication between the controllers
System bus CAN - network

7.2.4 CAN settings

The CAN settings can be made when inserting a CAN network or after the insertion into the
Settings tab of the system bus (CAN).

In the dialog box the area information is used to allocate the addresses of the nodes, as-
cending from minimum.
If you have changed something, you will receive a message to prevent that the project will
be compiled again and loaded into the devices. No automatic adaptations, neither node
address nor COB-ID will be carried out.

L 1.6 EN - 08/2006 91
L-force | Engineer
Network

8 Network
In this part of the project creation you add networks to the project, define the nodes of
communication and configure the networks inserted and the nodes assigned, so that an
exchange of information between the devices of the system is enabled.
 The basis of all worksteps is a Logical view to networks.
 Physical connections, topologies, bus connections, and also contents and the structure
of the variables communicated within a network are not important here.
 The Project view only presents the assignment between the system structure consisting
of system modules and axes, and the networks integrated.
 If you select a network in the Project view, several tabs are provided to you in the Oper-
ating range, via which you can configure the corresponding network. The possible set-
tings depend on the type of network and are described in detail in the subchapter to the
corresponding network!

 Note!
• Configurations carried out are not immediately accepted in device-specific
parameter assignments (for Lenze devices the known codes)!
– This acceptance only is effected later on in the course of a compilation
process for the entire project after you have defined interconnections.
– During the compilation process, network- and device-specific generators
are activated, automatically generating the relevant parameter assign-
ments and applications.
• A project can contain several networks of the same or of a different type,
therefore not all devices of a project have to communicate with each other in
the same network!
• In the version at hand, the »Engineer« supports the structure and the config-
uration of the system bus (CAN) by Lenze.
– Due to this limitation it normally is sufficient to insert a network in the top
system module (see the following example).

Network level
 In the network level, networks are assigned to the nodes.
 The following overall settings are available via the network object nodes:
– Node overview
– Synchronisation
– Process data objects transmitted

92 1.6 EN - 08/2006 L
 L-force | Engineer
Network

Structure of the communication structure

If you create a new project, in the first step you describe the system structure by means of
system modules and axes and then add the corresponding devices to these structuring el-
ements:

If you change to the project view "Network" afterwards, only the structuring elements (sys-
tem modules and axes) and the network-relevant components contained therein are dis-
played in the Project view:

L 1.6 EN - 08/2006 93
L-force | Engineer
Network
Connection between application and network

Starting from here, you can now extend the project by a communication structure by ac-
cordingly adding the networks which are available in the system:

8.1 Connection between application and network

In order to transfer the data from the port via a communication medium, they have to be
assigned to a process data object, e. g. PDO_TX2.
 Via the Process data objects tab of the object CAN on board you can generate and pa-
rameterise process data objects (PDO).
 You can assign one or more ports to a process data object.
 You can decide for yourself via which interface or which process data object the data is
transmitted or received.

PDO_RX1 PDO_TX1

PDO_RX2 PDO_TX2

Inserting a network ( 96)

More information about the network

System bus (CAN) ( 98)

94 1.6 EN - 08/2006 L
 L-force | Engineer
Network
Connection between application and network

Next steps
If you have added all networks to your project and have defined and parameterised the as-
sociated nodes, the project is completely established from the view of the networks.
 Now you can define the function of your entire system.
 You can change to other areas of the »Engineer« anytime to view certain settings or to
alter settings.

L 1.6 EN - 08/2006 95
L-force | Engineer
Network
Inserting a network

8.2 Inserting a network

 How to insert a network:

1. Select the system module or the axis which a network is to be inserted in
from the Project view.

2. Click the icon.

• The Insert network dialog box appears:

• All networks available are displayed in the Search results list field.
• In the version at hand, the »Engineer« only supports the system bus (CAN) by
Lenze.
3. Select the network to be inserted in the Search results list field.
4. Select the option Insert node and configure nodes and machine application if all
devices available are to be automatically added to the network as nodes.CAN
settings ( 91)
• If you select this option, also an application which is displayed in the project tree
is added to the project.
• The indicated default value for Lenze devices do not need to be changed in the
settings area.
• All compatible network nodes which are below the network system module are
added to the network. If a device has several node interfaces of the same type,
a selection dialog appears.
• All allocated network nodes are assigned with ascending addresses. In case of
CAN the minimum address is taken from the settings.
• If no machine application is available yet, this will be added to the project. All
applications are allocated to the machine application.

96 1.6 EN - 08/2006 L
 L-force | Engineer
Network
Inserting a network

5. Press OK.
• The network selected is inserted in the element highlighted.
• If the option Establish network has been highlighted, an assistant for establish-
ing the corresponding network is displayed.

L 1.6 EN - 08/2006 97
L-force | Engineer
Network
System bus (CAN)

8.3 System bus (CAN)

If you select a network of the "System bus (CAN)" type in the Project view, different tabs are
provided to you in the Operating range via which you can configure the network.
 Via the Properties tab you can change the name of the network and add a comment to
the network.
 Via the Nodes tab you can add nodes to the network or remove nodes that are already
available from the network. Nodes ( 98)
 Via the Settings tab you can carry out settings concerning the entire net-
work. Settings ( 103)
 Via the Synchronisation tab you can carry out settings with regard to the synchronisa-
tion of the nodes among each other. Synchronisation ( 104)
 Via the CAN objects tab you can have a list displayed of the CAN process data objects to
be transferred on this network, which have been generated during the course of the
compilation process. CAN objects ( 106)

 Tip!
It is recommended to first define and configure all nodes of a network via the
Nodes tab and only afterwards carry out the global settings of the network via the
Settings tab.

8.3.1 Nodes

In the Nodes tab you establish nodes which are to communicate with each other via the
network.
 In the Nodes tab the nodes are represented in the form of a network.
 You can only establish a network from nodes which you have also inserted as devices
in your project.

 Tip!
If the option Insert node and configure nodes and machine application was select-
ed in the Insert network dialog box when you inserted the network, all the devices
available were already inserted as nodes in the network automatically.

98 1.6 EN - 08/2006 L
 L-force | Engineer
Network
System bus (CAN)

Working in the network view

In the upper position, the network view is provided with an individual toolbar.
 Click a symbol to execute the corresponding function.

Icon Menu command Function

NetworkInsert nodes Inserting nodes ( 100)

NetworkRemove nodes Removing nodes ( 102)

NetworkNode settings Node settings ( 102)

Arrange the nodes according to address

NetworkZoom in view Zoom in view on the Nodes tab

NetworkZoom out view Zoom out view on the Nodes tab

NetworkOverview Show overview window

NetworkWhole worksheet Adapt view to the whole worksheet

NetworkPage width Adapt view to the width of the worksheet

NetworkPrint Print worksheet

Context menu in the network view

The Network view furthermore provides you with a Context menu for each node, featuring
the following commands:

Command Function
Go to... Display of a submenu via which you can directly change to specific device settings:

Remove node Remove a node from the network again.

Reset node Changes of the nodes are accepted
Set as master Define node as master.
• By the master the initialisation of the system bus (CAN) and the associated state
change from Pre-operational to Operational is effected.
• The node taking over the role of the master in the network view is identified by a
black triangle in the left corner at the bottom:

L 1.6 EN - 08/2006 99
L-force | Engineer
Network
System bus (CAN)

8.3.1.1 Inserting nodes

 Tip!
If you insert the network, you can also highlight the option Insert and configure
nodes in the Insert network dialog box instead of inserting nodes in the network
manually, in order to insert all devices available automatically as nodes in the net-
work .

Inserting a network ( 96)

The (manual) selection of a node is effected via the Node selection dialog box, where all
components of the system structure containing communication-capable devices (e. g. con-
trollers with a system bus interface) are specified again in a tree structure:

 You can only establish a network from nodes which also are available as communica-
tion-capable devices in your project.

 The element below a communication-capable device in this connection represents

an individual, independently configurable node interface (not to confuse with the
physical bus connection).
 If a device is provided with several node interfaces which can be configured independ-
ently from each other, it can appear in several networks or in the same network as a
multiple node.

 Note!
In the tree structure in the Node selection dialog box only the devices are listed
that actually can be inserted in the network as nodes.

100 1.6 EN - 08/2006 L

 L-force | Engineer
Network
System bus (CAN)

 How to insert a node in the network:

1. Click the icon in the Network toolbar.
• The Node selection dialog box is displayed.

2. Select the node interface in the tree structure, the higher-level device of which
is to be inserted in the network as node.
• Devices containing only one node interface can be selected without opening
them further to the node interface in the tree structure.
3. Press Accept.
4. The dialog box is closed and the selection is accepted.

 The node inserted then is displayed in the Network view as follows:

 In the project view additionally all nodes of the network are listed as a "linkage" below
the network element:

 Repeat the command Add nodes if you want to insert further nodes in the network.

L 1.6 EN - 08/2006 101

L-force | Engineer
Network
System bus (CAN)

8.3.1.2 Node settings

Configuration options in the network view

Directly in the Network view you can change the node address of a node, its designation,
and the designation of the device.

 How to change a setting in the network view:

1. Click into the respective text field to alter the corresponding setting:

2. Press <Input key> to accept the change.

Further configuration options

Further settings with regard to a node can be carried out via the Properties, Settings and
Monitoring tabs.

 Tip!
Detailed information on the system bus (CAN) for controllers of the 9400 device se-
ries can be found in the "CAN on board 9400" Communication Manual.

 How to define the further settings of a node:

1. Select the node to be configured in the Network view.
• In the network view a selected node is highlighted by a green frame.

2. Click the icon in the Network toolbar.

3. Carry out the corresponding node settings in the Properties, Settings and Monitor-
ing tabs.
• Via the icon in the Toolbar you can go back to the settings of the network.

8.3.1.3 Removing nodes

 Click the icon in the Network toolbar to remove the selected node from the net-
work again.

102 1.6 EN - 08/2006 L

 L-force | Engineer
Network
System bus (CAN)

8.3.2 Settings

In the Settings tab you define the global settings applying for the entire network.

General
In order to enable communication via the system bus (CAN), all nodes have to use the same
data transfer rate.
 Via the Baud rate list field you can centrally define the data transfer rate for the entire
network:

Possible settings Information

20 kbit/s • If you change the setting of the baud rate for one node, you have to carry out a
Reset node afterwards to make the change effective.
50 kbit/s
• Lenze devices are preset by the factory with a data transfer rate of 500 kbit/s.
125 kbit/s
250 kbit/s
500 kbit/s
1000 kbit/s

Allocating identifiers automatically

Process data objects have a definite identifier.
 Via the input fields from / to you can preselect a range for the automatic allocation of
the identifiers for all process data objects parameterised within the »Engineer«.

 Tip!
Such a range specification can be reasonable if also process data objects are com-
municated within the actual network in your system, the identifiers of which can-
not be defined by means of the »Engineer«. This situation for instance occurs if
external devices are available in you system, which cannot be configured within
the »Engineer«, which, however, take active part in communication all the same.
• In such a case you can separately define these external devices and the identifi-
ers of the process data objects transmitted by these devices.
• By setting the permissible range in the »Engineer« you then ensure that identi-
fiers which have already been allocated externally are not used or allocated
again.

L 1.6 EN - 08/2006 103

L-force | Engineer
Network
System bus (CAN)

Address range
A so-called node address, also called "Node ID", is to be assigned to each node within the
system bus network as a definite identification.
 For the nodes, node addresses in the range of 1 ... 63 can be allocated.
 Via the input fields Minimum node address and Maximum node address you can nar-
row this range further.
 Via the input field Maximum number of nodes you can narrow the maximum number
of the possible nodes.

Restoring the standard settings

By pressing Standard you restore the standard settings for the identifier range or the ad-
dress range.

8.3.3 Synchronisation

Via the Synchronisation tab you can configure the required parameters, in order to syn-
chronise the internal time base of selectable network nodes with the arrival of a so-called
sync telegram. Furthermore you can define the node which is to transmit a sync object. The
nodes which are to adapt their internal control cycle to the sync object.
By this, the internal calculation processes (e. g. control-oriented processes) of a node can
be synchronised with the calculation processes of other nodes which can also process the
sync telegram.

SYNC source

Setting Information
Nodes Selection of the node that cyclically sends the sync telegram.
Sync telegram identifier Send identifier of the sync telegram.
• Setting range: 1 ... 256
• Default setting: 128
Sync cycle time Transfer cycle for the sync telegram
• Setting range: 0 ... 65000 ms
• Default setting: 0 ms (= Off)

SYNC receiver
In this list field select the nodes which are to synchronise to the sync telegram in the first
column by clicking the corresponding control fields.

104 1.6 EN - 08/2006 L

 L-force | Engineer
Network
System bus (CAN)

Parameter
Here you can set further parameters of the CAN object.

L 1.6 EN - 08/2006 105

L-force | Engineer
Network
System bus (CAN)

8.3.4 CAN objects

This tab provides you with the display of a list of the CAN process data objects (PDOs) to be
transferred on the network, which have been generated in the course of the compilation
process.
Objects which have been created by a comprehensive interconnection of the devices, and
objects which are forced automatically are displayed.
The list contains the following information:

Column Information
Nodes Objects of the interconnection
Process data object Application for which the CAN process data object has been created.
Identifier COB-ID allocated for the CAN process data object.
• This setting can also be altered in the list.
Transfer mode Transfer mode by means of which the CAN process data object is transmitted via the
system bus.
Time [ms]

 Note!
For detailed information about the CAN process data object, please see the "CAN
on-board 9400" Communication Manual.

8.3.5 Properties

You can enter a designation for the system module in the Designation text field.
Optionally you can enter a comment on the system module in the Comment text field.
The fields "Version" and "Protocol" are not editable.

106 1.6 EN - 08/2006 L

 L-force | Engineer
Functions

9 Functions
In this area, you define the functionality of your entire system. For this purpose, describe
the kind of information that is communicated between the devices of your system for an
interaction as desired. Moreover, define for the single devices their concrete function in the
system. the Project view only presents the assignment between the system structure con-
sisting of system modules and axes, and the logic integrated.

 The symbols below the devices represent the application selected for the respective
device.

 A higher-level machine application is always required if several devices have to ex-

change information with each other, as applications can only be interconnected within
a machine application.
 In contrast to networks, with regard to function not the network-specific settings, but
the contents and the structure of the communicated variables are of interest.

 Note!
Configurations carried out in the functions are not immediately accepted in de-
vice-specific parameter assignments (for Lenze devices the known codes)!
• This acceptance only is effected later on in the course of a compilation proc-
ess for the entire project.
• During the compilation process, network- and device-specific generators are
activated, automatically generating the relevant parameter assignments and
applications.

L 1.6 EN - 08/2006 107

L-force | Engineer
Functions
Terminology used

9.1 Terminology used

Applications & ports

The function of a device in the »Engineer« is symbolised by its Application. An application
can be viewed as a block that mostly is configurable via parameters and is provided with
external connection points, so-called Ports:

 A device always brings along an application which may also be empty or unconfigured.
 Via input ports, for instance setpoints and control commands can be transferred to the
application, via output ports an application can provide actual values and status mes-
sages.
 Examples of applications are "speed control" and "torque control".

Machine application
A function of the system which is realised by the interaction of several devices in the »En-
gineer« is symbolised by a Machine application.
 A machine application is generated by defining the applications which form this ma-
chine application by allocation in a first step:

 The second step is to interconnect the ports of the applications assigned with each oth-
er and like this describe the applications between which information is exchanged:

108 1.6 EN - 08/2006 L

 L-force | Engineer
Functions
Terminology used

Ports for machine applications

You can also define Ports for a machine application to realise an exchange of information
between different machine applications:

 Basically not only applications, but also machine applications which have already been
pre-configured can be assigned to a machine application. Like this, hierarchical applica-
tion structures can be established.
 An "electrical shaft" is an example of a machine application.

Application variables
The information to be exchanged between applications is called Application variables.
 A "control word" is an example of an application variable.

Element variables
An application variable in turn consists of so-called Element variables.
 The configuration of an application variable of element variables is defined by the ap-
plication which generates the respective variable and provides it to its environment via
an output port.
 Examples of element variables:
– Variable of the BOOL type for exchanging the "set controller inhibit" control signal.
– Variable of the DINT type for exchanging the speed setpoint.

 Note!
The configurations which you generate within the functions can be network-in-
dependent!
• For instance, if you define that an application variable is communicated be-
tween two applications with a specific cycle time, you do not yet have to spec-
ify within the functions the process data object which the variable is imaged
to and the network via which the process data object will actually be commu-
nicated.

L 1.6 EN - 08/2006 109

L-force | Engineer
Functions
General notes with regard to the procedure

9.2 General notes with regard to the procedure

For describing the functions of the system, the following procedure is recommended:

 Note!
The procedure described in the following is based on one application for the
project, however, a project can also contain several applications for representing
hierarchical structures!

1. Parameterise& configure the devices

Carry out the parameter settings required for the individual devices and the applications
assigned.
Parameterising & configuring the devices ( 111)

2. Generate machine application

Generate a machine application within a system module or an axis to realise device-inde-
pendent functions.
Generating machine applications ( 138)

3. Compile the entire project

Have the entire project compiled to automatically generate all relevant parameter assign-
ments for the networks and devices contained in the project.

110 1.6 EN - 08/2006 L

 L-force | Engineer
Functions
Parameterising & configuring the devices

9.3 Parameterising & configuring the devices

If you select a device in the Project view, different tabs are provided to you in the Operating
range via which you can parameterise and configure the device.

 Note!
The tabs provided for a device and the settings which can be carried out via these
tabs depend on the respective device and therefore can only be explained exem-
plarily here!
Also read the documentation supplied with the corresponding device before
you start working!

Tab Information
Application parameter Via the Application parameter tab you can parameterise the application assigned to
the device.
Parameterising the application ( 120)
FB editor The configuration of the application of certain devices can be altered via the FB edi-
tor tab by means of a corresponding interconnection.
Establishing a function block interconnection ( 147)
Terminal assignment Via the Terminal assignment tab you can configure the digital and analog input and
output terminals of the device.
Configuring the terminal assignment ( 119)
Ports Via the Ports tab you can add ports to the application for a data exchange with other
applications.
Port editor ( 125)
Diagnostics Via the Diagnostics tab you can for instance carry out a diagnostics of the device con-
nected when an online connection has been established.
Diagnostics ( 169)
Oscilloscope Via the Oscilloscope tab you can use an integrated oscilloscope function for support-
ing commissioning, maintenance, and troubleshooting.
Oscilloscope ( 170)
All parameters Via the All parameters tab you can have all parameter settings of the device dis-
played and can also alter them.
Setting the parameters ( 113)
Properties In the Properties tab general information about the device is displayed, e. g. manu-
facturer, order number, and device series.
Displaying the properties ( 111)
Documentation Via the Documentation tab you can add notes and documents available in electronic
form to the device.
Adding documentation ( 137)

9.3.1 Displaying the properties

In the Properties tab of a device the designation and identification of the device is dis-
played.
 The designation of the device in the project can also be altered via the input field Des-
ignation.

L 1.6 EN - 08/2006 111

L-force | Engineer
Functions
Parameterising & configuring the devices

9.3.2 Assigning an application to the device

If you insert a device, after selecting the device to be inserted you can also optionally select
an application available for the respective device, which then is displayed below the de-
vice:

 If no application has been selected for the device when it was inserted, a so-called
"empty application" is assigned to the device instead:

 The application assigned to the device at any time can be replaced by another applica-
tion which is available for the device.

 Note!
If an application is replaced, the present parameterisation, configuration, and
the program for the device are lost!

 How to replace an application:

1. Select the controller under which the application to be replaced is located in the
Project view.
2. Select the command InsertApplication.
• The Replace device application dialog box is displayed.
3. Select the new application.
4. Press OK.
5. Confirm safety query with Yes to replace the existing application by the application
selected.
• The dialog box is closed and the present application is replaced by the newly se-
lected application.

112 1.6 EN - 08/2006 L

 L-force | Engineer
Functions
Parameterising & configuring the devices

9.3.3 Setting the parameters

Via the All parameters tab of a device or an application you can have the parameter set-
tings of the corresponding device displayed and also modify them, e. g. in order to define
further functional settings for the device:

 The parameters are classified in different categories and subcategories which you se-
lect via the buttons on the left.
– If you click on a category button, the available subcategories are shown and can be
selected via mouse-click.
 If you change to another category, the subcategories of the previously selected catego-
ry are masked out again.In the parameter list on the right all parameters of the catego-
ry/subcategory are shown.
– By clicking on the head of the corresponding column you can alter the sorting of the
parameter list and switch between ascending and descending sorting.
– If you select the first category "Code list", all parameters of the corresponding device
are displayed in the parameter list.
 Below the parameter list, in a so-called "information area", further information on the
parameter selected are displayed on the left.
– Using the command Information area in the Context menu of the parameter list you
can show or hide the information area.

 Tip!
By means of the command OnlineCompare parameters you can read the current
parameter settings of the device when an online connection has been established
and compare them to the (offline) parameter settings of the »Engineer« project.
Compare parameters ( 55)

L 1.6 EN - 08/2006 113

L-force | Engineer
Functions
Parameterising & configuring the devices

9.3.3.1 Terminology used

Offline/online
With regard to the representation of the parameter setting, the modes "Offline" and "On-
line" are differentiated.
 If no online connection to the device is available, the parameter list is in the "Offline
mode". In this mode the parameter list displays so-called "Offline parameters" present-
ing the parameter settings of the device saved within the project. Altering a param-
eter offline ( 116)
 However, if an online connection to the device is available, the parameter list is in the
"Online mode". In this mode the parameter list displays so-called "Online parameters",
presenting the parameter settings which are currently existing within the device.
Altering parameters online ( 117)
 In the »Engineer« offline and online parameters are identified by a different back-
ground colour:

Colour Example Meaning

White Offline parameter
• The device is not connected "online" with the »Engineer«. The parameter value
set in the project is displayed.
Yellow Online parameter
• The device is connected "online" with the »Engineer«. The current parameter val-
ue of the device is displayed.
• The symbol after a parameter value indicates that the value in the device dif-
fers from the parameter value set in the project.
Red Communication error (time-out) for an online parameter
• The communication connection to the device is interrupted.

 Tip!
In the information area below the parameter list the current mode (offline/online)
is displayed on the right side.

Display parameters
"Display parameters" are parameters which only serve as display of status information and
actual values and which only permit reading access.
 In the »Engineer« display parameters also are identified by a different background col-
our:

Colour Example Meaning

Light grey Offline display parameter

Pale yellow Online display parameter

• The device is connected "online" with the »Engineer«. The current parameter val-
ue of a display parameter is displayed.
Red Communication error (time-out) for an online display parameter
• The communication connection to the device is interrupted.

114 1.6 EN - 08/2006 L

 L-force | Engineer
Functions
Parameterising & configuring the devices

9.3.3.2 Working in the parameter list

In the upper position the parameter list is provided with an individual toolbar which in the
following text is called "parameter toolbar".
 Click a symbol to execute the corresponding function.

Icon Function
Accepting parameter settings in the device ( 118) *

Accepting the parameter settings of the device ( 118) *

Resetting parameters to the default setting ( 118)

* Function only possible only when an online connection has been established.

 Tip!
Via the command Go to in the Context menu of the parameter list you can quickly
reach the corresponding parameter in the list by entering the parameter number
or the parameter designation:

L 1.6 EN - 08/2006 115

L-force | Engineer
Functions
Parameterising & configuring the devices

9.3.3.3 Altering a parameter offline

If you are "offline" and therefore are not connected with the device, the parameter settings
for the respective device saved within the project are displayed in the direct mode in the
"Value" column:

Offline parameter
Offline display parameter

 In the offline mode you can carry out all required parameter settings for a device,
whereby the corresponding device at this time does not have to be physically available
or connected to the PC.
 Like this you can for instance "pre-configure" the project unhurriedly and carry out the
transfer of the complete parameter set in the device later.
 All settings in the parameter list are saved together with the project and thus are again
provided in the next »Engineer« session.

 How to alter a parameter setting "offline" in the project:

1. Select the parameter to be altered from the list.
2. Enter the new value in the Value column, or select it from the options defined.
• Invalid or impermissible values are presented "red" in the input field.
• Values that have not been accepted yet are presented "blue" in the input field.
3. Press the <Input key> to accept the changed value.
• By pressing the <ESC> key you can undo the entry.

116 1.6 EN - 08/2006 L

 L-force | Engineer
Functions
Parameterising & configuring the devices

9.3.3.4 Altering parameters online

If you are connected to the device "online", instead of the parameter settings saved within
the project the current parameter settings of the device are displayed in the direct mode in
the "Value" column:

Online parameter
Online display parameter

 The values are continuously updated in a cyclic manner.

 The symbol after a parameter value indicates that the value in the device differs from
the parameter value set in the project.
 In the information area below the parameter list further information on the parameter
selected is displayed, such as for instance the value set in the project.

 Note!
If you alter a parameter value when an online connection has been established,
this setting is also accepted for the corresponding device!

 How to alter a parameter setting "online" in the project and the device:
1. If no online connection has been established yet, click on the icon in the Toolbar
to establish an online connection to the device.
Establishing an online connection ( 39)
2. Select the parameter to be altered from the list.
3. Enter the new value in the Value column, or select it from the options defined.
• Invalid or impermissible values are presented "red" in the input field.
• Values that have not been accepted yet are presented "blue" in the input field.
4. Press the <Input key> to accept the changed value.
• By pressing the <ESC> key you can undo the entry.
• If you exit the input field without having accepted the altered value before-
hand, a query as to whether the altered value is to be accepted or not is effected.

L 1.6 EN - 08/2006 117

L-force | Engineer
Functions
Parameterising & configuring the devices

9.3.3.5 Resetting parameters to the default setting

 How to reset a parameter to the default setting:

1. Select the parameter to be altered from the list.

2. Click the icon in the Parameter toolbar to reset the selected parameter to the
default setting.

9.3.3.6 Accepting the parameter settings of the device

If you are connected to the device "online", you can accept parameter settings of the device
easily in the project.
Establishing an online connection ( 39)

 How to accept parameter settings of the device in the project:

1. Select the parameter from the parameter list.
• The symbol after a parameter value indicates that the value in the device dif-
fers from the parameter value saved in the project.

2. Click the icon in the Parameter toolbar to accept the selected parameter setting
of the device in the project.

9.3.3.7 Accepting parameter settings in the device

If you are connected to the device "online", you can accept parameter settings saved within
the project easily in the device.
Establishing an online connection ( 39)

 How to accept parameter settings of the project in the device:

1. Select the parameter from the parameter list.
• The symbol after a parameter value indicates that the value in the device dif-
fers from the parameter value saved in the project.

2. Click the icon in the Parameter toolbar to accept the selected parameter setting
of the project in the device.

118 1.6 EN - 08/2006 L

 L-force | Engineer
Functions
Parameterising & configuring the devices

9.3.4 Configuring the terminal assignment

Via the Terminal assignment tab for a device you can configure the digital and analog input
and output terminals of the device.

 Note!
The display of the Terminal assignment tab and the possible settings specified
are device-dependent!
Also read the documentation supplied with the corresponding device before
you start working!

9.3.4.1 Changing the terminal assignment

Depending on the device application assigned to the device and on the default setting of
the device, terminals can already be linked to internal signals. This assignment, however,
can be changed if required.

 Click the corresponding buttons in the Application group field to alter the I/O con-
figuration for the associated terminal.

9.3.4.2 Setting the gain & offset of the analog terminals

Click the button to parameterise the gain and offset for the associated an-
alog terminal.

9.3.4.3 Setting the active level of the digital terminals

For each digital terminal the set active level is displayed:

Icon Meaning
Digital terminal is "High active"

Digital terminal is "Low active"

L 1.6 EN - 08/2006 119

L-force | Engineer
Functions
Parameterising & configuring the devices

 Click the buttons or to change the active level for the associated digital
terminal from "High active" to "Low active", or from "Low active" to "High active".

9.3.4.4 Displaying the actual state of the terminals

If an online connection to the device is available, the Terminal assignment tab displays
the actual state of the terminals.

Analog inputs/outputs
For the analog inputs/outputs the corresponding actual value is displayed as voltage val-
ue:

 The display of the actual values for the analog inputs is effected in consideration of the
accordingly set signal adjustment (offset & gain).

Digital inputs/outputs
For the digital inputs the current status is visualised by an "LED":

Icon Meaning
Off

On

 The status display for the digital inputs is effected in consideration of the terminal po-
larity set.

9.3.5 Parameterising the application

Via the Application parameters tab you carry out the parameter setting of the application
assigned for the device, the ambient conditions, as well as further components connected
to the device (e. g. motor, brake, gearbox).

120 1.6 EN - 08/2006 L

 L-force | Engineer
Functions
Parameterising & configuring the devices

9.3.5.1 Working in the "Application parameters" tab

 Note!
The display of the Application parameters tab and the possible settings specified
are device-dependent!
Also read the documentation supplied with the corresponding device before
you start working!

The Application parameters tab contains several levels of parameter dialogs.

 The top "Overview" level presents all parameterisable device functions and the param-
eterisable device components in the form of pictographs which can be clicked:

L 1.6 EN - 08/2006 121

L-force | Engineer
Functions
Parameterising & configuring the devices

 If you click on one of the pictographs marked with the symbol , you reach one level
deeper in the corresponding parameter dialog.
– In this example the pictograph highlighted red was selected.

 This parameter dialog can also have further subordinate parameter dialogs, depending
on the complexity.
 Some pictographs are marked with the so-called flag symbol , indicating that set-
tings still have to be carried out in the associated parameter dialog.
– If you click on such a pictograph to change to the associated parameter dialog, the
flag is automatically reset (removed).

122 1.6 EN - 08/2006 L

 L-force | Engineer
Functions
Parameterising & configuring the devices

Toolbar
The Application parameters tab is provided with an individual toolbar in the upper posi-
tion, which in the following text is called "Application parameters toolbar".
 Click a symbol to execute the corresponding function.

Icon Function
Back to the previously displayed parameter dialog.

Set flag for the current parameter dialog.

• The flag symbol on a pictograph is to point out that settings still have to be carried out or have
to be checked in the associated parameter dialog.
Going directly to a parameter dialog ( 124)

Display online values of the inputs.

• The actual state of the inputs is directly displayed on the buttons.

Add note
• You can add a note to each parameter dialog.

Change to the FB editor.

 Tip!
In the blue header the current parameter dialog level always is displayed:

L 1.6 EN - 08/2006 123

L-force | Engineer
Functions
Parameterising & configuring the devices

9.3.5.2 Going directly to a parameter dialog

If you want to change to a parameter dialog which is not directly one level higher or low-
er, you can use the function "Go directly to the dialog...".
 You can also use this function to have all parameter dialogs for the application dis-
played in a hierarchical tree topology.

 How to go directly to a parameter dialog:

1. Click the icon in the Application parameters toolbar.
• The Go to the function detail dialog box is displayed:

Tip!
Simultaneously to the display of this dialog box you can carry out further settings
on the Application parameters tab and change to other parameter dialog levels.
The accentuation of the current parameter dialog level in the tree topology also is
updated when the change-over is effected.
2. Select the parameter dialog to be displayed from the hierarchical structure or nav-
igate through the structure via the Back or Next buttons.
• The respectively selected parameter dialog is displayed immediately on the Ap-
plication parameters tab.
• The Go to the function detail dialog box remains open until the Cancel button is
pressed.

124 1.6 EN - 08/2006 L

 L-force | Engineer
Functions
Port editor

9.4 Port editor

Establishing and visualising ports is effected by the port editor.

The port editor can
 be called for an application on a device.
 be called for a device-independent application (machine application).

Range Information
Port Display of all input and output ports of an application/
machine application.
Communication Display and change the assignment of a port to an interface or process data object.
Variable Display of the variable definition for a port selected.

Communication

Display Information
User specification Display of the interface and process data object via which a port is to be transmitted:
• automatically
• <interface>
• <interface>/<process data object>
Realisation Display of the interface and process data object via which a port is transmitted:
• automatically
• <interface>
• <interface>/<process data object>
Offset Display of the offset in the process data object if a port is transmitted or received via
a process data object.

L 1.6 EN - 08/2006 125

L-force | Engineer
Functions
Port editor

Adding input/output ports

A port is an interface via which an application sends and receives data within the runtime.
A port is a group of information which cannot be separated anymore and which has to be
transmitted in one piece.
A process data object can serve as a container for several ports. This means that several
ports can be transmitted by one process data object. The assignment of the ports to the
process data objects can be effected automatically or manually.
Establishing the connection ( 144) Most applications have ports which are already fixed-
ly predefined.
 Via the Ports tab of the current device or the application assigned you are provided with
an overview of the ports which are defined for this device application.
 Simply click an icon to activate the corresponding command.

Icon Function
Adding a port ( 127)

Renaming a port ( 137)

Deleting a port ( 137)

 After you have added a port, you have to define a structure of element variables for this
port which are to be communicated via this port. Defining the element variable (
136)

126 1.6 EN - 08/2006 L

 L-force | Engineer
Functions
Port editor

9.4.1 Adding a port

 How to add a port:

1. Click the icon in the Ports toolbar
• above the field Input ports to add an input port,
or
• above the field Output ports to add an output port.
Then the assistant for adding a port will open.
Step 1 - port designation

2. Enter a designation for the port in the Name input field.

3. Press Next.
Then the next dialog for adding a port will open.

L 1.6 EN - 08/2006 127

L-force | Engineer
Functions
Port editor

Step 2 - variable type

4. Select a variable type for the port in the Variable type selection field.
• For this purpose, the variable types simple, record and array are provided.

 Note!
The identifiers of ports and the associated variables have to be definite.
The identifiers of the »Engineer« must not be identical with the IEC 61131-5
identifiers.

A port of an application consists of variables. In the »Engineer« these variables again are
summarised to simple, record or array types.

Variable type Information

"Simple" variable type This type only contains one variable of a basic data type like INT, WORD, etc.
( 129) • To be used if it is not known how the devices are comprehensively interconnect-
ed. A data consistency between the variables is not required.
"Record" variable type This type contains one or several variables of a basic data type like INT, WORD, etc.
( 130) • To be used in a network, e. g. a controller with a predesigned application, where-
by the data structure is always identical.
"Array" of byte variable type This type contains one or several variables of the same basic data type like INT,
( 130) WORD, etc.
• To be used for simple binary systems (terminals).

According to the variable type selected, the surface of the dialog box changes.
Port with the "Simple" variable type ( 131)
Port with the "Record" variable type ( 132)
Port with the "Array" variable type ( 134)

128 1.6 EN - 08/2006 L

 L-force | Engineer
Functions
Port editor

9.4.1.1 "Simple" variable type

Highest flexibility

Devices Device A Device B Device C Device D

Variable 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16
Device A Variable01
Variable02
Variable03
Variable04
Device B Variable05
Variable06
Variable07
Variable08
Device C Variable09
Variable10
Variable11
Variable12
Device D Variable13
Variable14
Variable15
Variable16

L 1.6 EN - 08/2006 129

L-force | Engineer
Functions
Port editor

9.4.1.2 "Record" variable type

Variable network

9.4.1.3 "Array" of byte variable type

Simple systems

130 1.6 EN - 08/2006 L

 L-force | Engineer
Functions
Port editor

9.4.1.4 Port with the "Simple" variable type

 How to define a port with the "Simple" variable type:

1. Carry out the steps as described in the instructions in chapter "Adding a port
( 127)".

2. Select the Variable type Simple from the selection field.

• The Port definition dialog box then is presented as follows.

3. Select a type from the Type selection field.

4. Press Next.
• The Interface and Process data object selection fields are displayed.
5. Press the Complete button if the port is to be designed like this.
6. Select the entry "CAN on board" from the Interface selection field.
• The Port definition dialog box then is presented as follows.

L 1.6 EN - 08/2006 131

L-force | Engineer
Functions
Port editor

7. Enter the desired settings.

8. Press the Complete button to complete the port definition.

9.4.1.5 Port with the "Record" variable type

 How to define a port with the "Record" variable type:

1. Carry out the steps as described in the instructions in chapter "Adding a port
( 127)".

2. Select the Variable type Record from the selection field.

• The Port definition dialog box then is presented as follows.

3. Press New to open the Element variable dialog box.

4. Define the name and type of the new element variable and confirm by pressing OK.
Defining the element variable ( 136)
5. Press Next.
• The Interface and Process data object selection fields are displayed.
6. Press the Complete button if the port is to be designed like this.

132 1.6 EN - 08/2006 L

 L-force | Engineer
Functions
Port editor

7. Select the entry "CAN on board" from the Interface selection field.
• The Port definition dialog box then is presented as follows.

8. Enter the desired settings.

9. Press the Complete button to complete the port definition.

L 1.6 EN - 08/2006 133

L-force | Engineer
Functions
Port editor

9.4.1.6 Port with the "Array" variable type

 Note!
Designing a port with the "Array" variable type is not supported in this Engineer
version.

 How to define a port with the "Array" variable type:

1. Carry out the steps as described in the instructions in chapter "Adding a port
( 127)".

2. Select the Variable type Array from the selection field.

• The Port definition dialog box then is presented as follows.

3. Select a type from the Type selection field and enter the desired number in the
Number of the elements input field.

134 1.6 EN - 08/2006 L

 L-force | Engineer
Functions
Port editor

4. Press Next.
• The Port definition dialog box then is presented as follows.

5. Enter the desired settings.

6. Press the Complete button to complete the port definition.

Transfer parameters for the system bus (CAN)

Parameter Information
Process data object Selection of a fixed or free CAN process data object (PDO).
Transfer mode Transfer mode by means of which the CAN process data object is transmitted via the
system bus.
COB-ID COB-ID allocated for the CAN process data object.
• If the option automatic allocation is activated, the COB-ID is automatically allo-
cated by the »Engineer« during the compilation process.
• If the option automatic allocation is deactivated, the COB-ID can be defined by
the user and is not changed by the »Engineer« anymore.
Transfer time Transfer time
• Only adjustable for an output port.
Blocking time Blocking time between the transfer of two output objects.
• Only adjustable for an output port.
Number of sync signals Number of sync signals
• Input or output data only are accepted or transmitted at arrival of every nth sync
telegram.
• Only adjustable for "synchronous" transfer mode.
• Is not supported by all devices.

L 1.6 EN - 08/2006 135

L-force | Engineer
Functions
Port editor

9.4.1.7 Defining the element variable

Button Information
New Generate new element variable
Change Change element variable selected
Delete Delete element variable selected
Place selected element variable one position higher in the list
Place selected element variable one position lower in the list
Optimise Without function in the current version of the engineering software.
Task Selection of the task context for the port selected.

 How to generate a new element variable:

1. Select the port for the associated structure of which a new element variable is to
be generated in the Ports tab.
2. Press the New button in the Element variables group field .
• The Element variable dialog box appears:

3. Enter a name for the element variable to be generated.

4. Select the data type for the element variable from the Type list field.
• In accordance with IEC 61131-3 integer data types can be selected.
5. Press OK.
• The dialog box is closed and the element variable is generated.

Changing/deleting existing element variables

Of course you can change the settings of element variables which are already existing at
any time and remove element variables from the list and therefore from the structure
again.

 How to change an element variable:

1. Select the element variable to be changed from the list field Element variables.
2. Press the Change button.
• The Element variable dialog box appears.
3. Carry out the desired changes in the Element variable dialog box.
4. Press OK.
• The dialog box is closed and the changes are accepted.

136 1.6 EN - 08/2006 L

 L-force | Engineer
Functions
Port editor

 How to delete an element variable:

1. Select the element variable to be deleted from the list field Element variables.
2. Press the Delete button to delete the element variable selected.

9.4.1.8 Renaming a port

Existing ports can be renamed at any time, in order to facilitate the identification of the
ports within an application.

 How to rename a port:

1. Select the port to be renamed in the Ports tab.

2. Click the icon above the respective Input or Output ports list field in the Ports
toolbar.
• Then you can change the name of the port:

3. Press <Input key> to accept the new name.

9.4.1.9 Deleting a port

 How to delete a port:

1. Select the port to be deleted in the Ports tab.

2. Click the icon above the respective Input or Output ports list field in the Ports
toolbar to delete the port selected.

9.4.2 Adding documentation

Via the Documentation tab you can add notes and documents in electronic form to the de-
vice. Adding documentation ( 82)

L 1.6 EN - 08/2006 137

L-force | Engineer
Functions
Generating machine applications

9.5 Generating machine applications

The machine application serves as a structuring means for the generation of system mod-
ules which already contain a predesigned interconnection.
In the Project view the existing system modules, axes and devices, as well as the applica-
tions subordinate to the devices, and possibly available machine applications are dis-
played:

 The symbols below the devices represent the respective application.

 A machine application always is required if several devices have to exchange infor-

mation among each other, as the applications assigned to the devices can only be in-
terconnected within a machine application. In the illustration this is represented by
9400 HighLine 1 and 9400 HighLine 2.
 Basically not only applications, but also machine applications which have already been
pre-configured can be assigned to a machine application. Like this, hierarchical applica-
tion structures can be established.
 A project can also contain several machine applications.
If you select a machine application in the Project view, different tabs are provided to you in
the Operating range via which you can configure the machine application.

Tab Information
Device applications Via the Device applications tab you assign the respective applications to the ma-
chine application.
Assigning applications ( 140)
Connections Via the Connections tab you define the applications exchanging information and the
ports via which this information is exchanged within the machine application.
Connecting ports within the machine application ( 142)
Ports Via the Ports tab you can add ports to the machine application to exchange informa-
tion with other machine applications via these ports.
Adding ports as an external interface ( 144)
Properties Via the Properties tab you can change the name of the application and add a com-
ment to the application.
Documentation Via the Documentation tab you can add notes and documents in electronic form to
the application.
Adding documentation

138 1.6 EN - 08/2006 L

 L-force | Engineer
Functions
Generating machine applications

9.5.1 Inserting a machine application

 How to insert a machine application:

1. Select the system module or the axis in which the machine application is to
be inserted from the Project view.

2. Click the icon.

• The Insert machine application dialog box appears:

3. Enter a name for the application in the Designation text field.

• Optionally you can enter a comment on the application in the Comment text
field.
4. Press OK.
• The dialog box is closed and the machine application is inserted into the high-
lighted element.

Next worksteps
 Assign the applications to the added machine application which are to exchange infor-
mation within the machine application. Assigning applications ( 140)
 If required, add ports to the machine application which serve as an external interface
and enable an exchange of information with other machine applications. Adding
ports as an external interface ( 144)
 Interconnect the ports of the applications assigned and those of the machine applica-
tion to each other, in order to thus describe between which applications information is
to be exchanged within the machine application, and what information is to be com-
municated to the outside. Connecting ports within the machine application ( 142)

9.5.2 Displaying the properties

The Properties tab of an application displays the name of the application in the project and
an optional comment.
 The name and comment can also be changed via the input fields.

L 1.6 EN - 08/2006 139

L-force | Engineer
Functions
Generating machine applications

9.5.3 Assigning applications

Via the Connections tab of a machine application you define by means of assignment
which applications are to exchange information within the machine application.

 Click in the Connections to display the following dialog.

 Each device already brings along an application which can be assigned to the machine
application, even if the respective application has not been fully defined.
 Not all applications of a project necessarily have to be assigned to the same machine
application.
 Apart from applications, also preconfigured machine applications can be assigned to a
machine application, in order to set up hierarchical application structures like this.

9.5.3.1 Carrying out assignments

 How to assign logic blocks to an application:

1. Select the application (or the already existing machine application) which is to be
assigned to the machine application in the field Available applications & machine
applications on the left:

140 1.6 EN - 08/2006 L

 L-force | Engineer
Functions
Generating machine applications

2. Press the button to accept the application selected to the field Applications &
machine applications selected on the right:

• By pressing the button you can remove a selected application from the field
Applications & machine applications selected on the right again and therefore
remove the assignment to the machine application.
• Logic blocks which have already been assigned are presented in grey in the field
Available applications & machine applications on the left and cannot be newly
assigned.
3. Repeat the first two steps to assign further applications to the machine applica-
tion.

Next worksteps
 If required add ports to the machine application which serve as an external interface
and enable an exchange of information with other machine applications. Adding
ports as an external interface ( 144)
 Interconnect the ports of the applications assigned and those of the machine applica-
tion to each other, in order to thus describe between which applications information is
to be exchanged within the machine application, and what information is to be com-
municated to the outside. Connecting ports within the machine application ( 142)

9.5.3.2 Removing assignments

 How to remove an assignment:

1. Select the corresponding application (or machine application) from the field Appli-
cations & machine applications selected on the right.
2. Press button.
• The application selected is removed from the field Applications & machine ap-
plications selected and therefore is not assigned to the machine application an-
ymore.

L 1.6 EN - 08/2006 141

L-force | Engineer
Functions
Generating machine applications

9.5.4 Connecting ports within the machine application

Interconnection of ports
In the function block editor ports of different devices are interconnected to each other.
Whether an interconnection of two or more ports is possible is checked by updating devic-
es ExtraUpdate devices.
 The following checks are carried out:
– Does the data width of the source port comply with those of the target port? If this
is not the case, an error is output and the compilation is cancelled.
– Does the data width of each element variable of the source port comply with that of
the target port? If this is not the case, a warning is output and the compilation is con-
tinued.
Via the Connections tab of a machine application you define which applications are to ex-
change information via which ports within the machine application.
The number of ports that can be interconnected with each other is checked during the
function "Update devices".

 If you connect an output port of an application to an input port of another application,

you express that the element variables of the output port of the first application are to
be communicated to the input port of the second application.
 A connection always has a direction and therefore always has a source and a target.
 Several connections may lead from one port, but only one connection can end in a port.
 Hierarchical application structures can be generated.

142 1.6 EN - 08/2006 L

 L-force | Engineer
Functions
Generating machine applications

 Tip!
You can also add Ports to a machine application to realise an exchange of informa-
tion between different machine applications like this: Adding ports as an exter-
nal interface ( 144)
Afterwards you can also interconnect these ports, in order to define what informa-
tion is to be communicated externally.

Examples of possible connection combinations

 An output port of an application is connected to an input port of another application:
(For this both applications have to be assigned to the same machine application.)

 An input port of a machine application is connected to an input port of an assigned ap-

plication:

 An output port of a machine application is connected to an output port of an assigned

application:

L 1.6 EN - 08/2006 143

L-force | Engineer
Functions
Generating machine applications

9.5.5 Adding ports as an external interface

You can also add ports to an application to realise an exchange of information between dif-
ferent applications like this.
Via the Ports tab of an application you receive an overview of the ports which are defined
for this application:

Adding input/output ports

Adding ports to an application is carried out in the same way as adding ports to an appli-
cation. Port editor ( 125)

9.5.6 Adding documentation

Via the Documentation tab you can add notes and documents in electronic form to the ap-
plication. Adding documentation ( 82)

9.5.7 Establishing the connection

Basically there are three types of data communication between two ports via a network.
Automatic connection ( 145)
Manual connection ( 146)
Predefined connection set connection ( 146)

144 1.6 EN - 08/2006 L

 L-force | Engineer
Functions
Generating machine applications

9.5.7.1 Automatic connection

For this purpose a network object in the »Engineer« and a machine application are re-
quired.
 The nodes which are to communicate with each other have to be assigned to the net-
work.
 The applications have to be assigned to the machine application.

 It is not necessary to assign an interface or a process data object to the ports. If it is re-
quired, your specifications are considered.
 For each interconnection featuring a starting point and maximally one end point as
port of an application the ports are combined to process data objects.
 It is checked whether the end points match with regard to the data size and storage
partitioning.
By means of the specification for realising the individual ports and of the information from
the interconnection within the machine applications and from the formation of networks
via the menu command ExtrasUpdate project it is tried to transform the information into
communication objects during the compilation process.
 It is tried to provide for a bus load as low as possible.
 Several ports are assigned to one process data object.
 Automatic disintegration is supported for "System bus (CAN)" and "ETHERNET Power-
link" networks.
 If a connection can be disintegrated via both "System bus (CAN)" and "ETHERNET Pow-
erlink", "ETHERNET Powerlink" is preferred due to the greater band width.
 If one of the interconnection end points (ports) has already been defined to an inter-
face, this connection is represented via the network assigned. If interfaces are not con-
nected via an identical network, an error message is output.
 If a port is assigned to a process data object, this port only is provided for this process
data object. No further ports are automatically assigned to this process data object.

L 1.6 EN - 08/2006 145

L-force | Engineer
Functions
Generating machine applications

9.5.7.2 Manual connection

The manual connection can be effected without a network object in the »Engineer« and
without a machine application.
 Directly assign the ports to the process data objects and set the communication param-
eters yourself like COB-ID for CAN.
This procedure is reasonable for external devices without »Engineer« catalogs and for bus
systems if no network is provided in the »Engineer«.

 Tip!
Observe that send and receive process data objects, data structure, and communi-
cation parameters comply with each other.

9.5.7.3 Predefined connection set connection

 The Use predefined connection set control field in the Settings tab of the CAN on board
only is active if you have not assigned a network to the CAN node.
If the Use pre-defined connection set control field is activated, the COB-IDs of the CAN
process data objects are derived from the node address.

Process data object COB-ID

PDO_RX1 0x200 + node address
PDO_RX2 03200 + node address
PDO_RX3 0x400 + node address
PDO_RX4 0x500 + node address
PDO_TX1 0x180 + node address
PDO_TX2 0x280 + node address
PDO_TX3 0x380 + node address
PDO_TX4 0x480 + node address

 Tip!
Observe that send and receive process data objects, data structure, and communi-
cation parameters comply with each other.

9.5.7.4 Mixed connection

A mixed form of the connections Automatic connection ( 145) and
Manual connection ( 146) is possible.
A mixed form of the connection Predefined connection set connection ( 146) and another
one is not possible.

146 1.6 EN - 08/2006 L

 L-force | Engineer
Functions
Establishing a function block interconnection

9.6 Establishing a function block interconnection

The applications of specific Lenze devices cannot only be parameterised, but can also be
reconfigured by means of a corresponding function block interconnection.
For these devices the FB editor tab is provided in the Operating range:
After you have selected the FB editor tab in the Operating range, you can activate the FB
editor via the button Enable editor.

L 1.6 EN - 08/2006 147

L-force | Engineer
Functions
Establishing a function block interconnection

9.6.1 Terminology used

Function block (FB)

A function block (FB) can be compared with an integrated circuit that contains a certain
control logic and delivers one or several values when being executed.
 Function blocks are classified in function libraries according to their functions.
 An entity (reproduction, copy) of the function block is always inserted in the circuit.
 It is also possible to insert several entities of a function block in a circuit.
 Each entity has an unequivocal identifier (the entity name) and a processing number
which defines the position the function block is calculated during runtime.

n Instance name (freely selectable)

o Function block name (cannot be changed)
p Processing number
q Other instance of the function block

[9.2] Information on a function block in the function block editor

Parameterisable function blocks

Some function blocks have parameters by means of which, if required, particular settings
can be changed during operation or which display actual values & status information.

 By clicking the symbol the parameter list of a function block can be opened.

System block (SB)

System blocks can be considered as a specific variant of a function block.
 In contrast to function blocks, system blocks are fixedly integrated in the runtime sys-
tem of the controller or of the control and therefore are not instanceable.
 System blocks partly activate real hardware, e. g. the digital and analog inputs/outputs
and the motor control.

148 1.6 EN - 08/2006 L

 L-force | Engineer
Functions
Establishing a function block interconnection

 The system blocks which are provided for a device within the FB editor depend on the
respective device.

[9.3] Example: LS_DigitalInput and LS_DigitalOutput of the 9400 HighLine for representing the digital inputs/outputs

Port block
If input or output ports have been defined for an application, you can insert these ports
into the interconnection in the form of port blocks and like this read or write the associated
element variables.

[9.4] Example: input port Input_AppSpeedMode and output port Output_AppSpeedMode

Variable
You can define variables for the interconnection and for instance apply these variables to
codes, in order to be able to parameterise setpoints and functions of the interconnection
via the keypad.
 For the data type of the variable integer data types in accordance with IEC 61131-3 are
provided.

[9.5] Example: variable bReset of the BOOL data type (on the left: assignment to the variable, on the right: assignment by the var-
iable)

User code
You can define user codes for the interconnection and thus assign the inputs of function
blocks.

L 1.6 EN - 08/2006 149

L-force | Engineer
Functions
Establishing a function block interconnection

Task
A task describes the runtime characteristics, such as the cycle time and the priority of one
or several programs running within the device, and together with the program makes a
runtime system.
 If the device supports several tasks, you can select the task for the interconnection to
be generated in the Task list field.

150 1.6 EN - 08/2006 L

 L-force | Engineer
Functions
Establishing a function block interconnection

9.6.2 Adjusting the representation

In the FB editor a Context menu with commands for adjusting the representation of the in-
terconnection, etc., is provided to you in the drawing area via the right mouse button.
 All functions listed in the following only change the representation of the interconnec-
tion, but not its function.

Command Function
Overview Show or hide overview window in the top left corner
Delete selection Delete selected objects in the drawing area
Zoom in Zoom in representation
Zoom out Zoom out representation
Complete overview Adjust representation so that all objects of the interconnection can be viewed in the draw-
ing area.
Draw grid Show or hide grid
Draw new Draw representation new

Functions in the overview window

By means of the overview window that can be shown in the top left corner of the drawing
area you can easily define and shift the cutout of the interconnection which is to be pre-
sented, and thus move within the interconnection.

 Select the command Overview window in the Context menu of the drawing area to
show the overview window.

 In the overview window the drawing area is presented in a minimised manner, where-
by the green frame identifies the cutout of the interconnection that is currently pre-
sented in the drawing area.

L 1.6 EN - 08/2006 151

L-force | Engineer
Functions
Establishing a function block interconnection

 How to shift the cutout presented in the drawing area:

1. Position the mouse pointer to the green frame in the overview window.
2. Click left mouse button and shift the green frame to its new position by keeping
the mouse button pressed, so that the desired cutout of the interconnection is dis-
played in the drawing area.

 How to redefine the cutout to be presented:

In the overview window draw a frame around the area of the interconnection
which is to be presented in the drawing window by keeping the left mouse button
pressed:

• According to the size of the frame that is drawn, also the presentation size of
the objects in the drawing area changes.

 Tip!
Select the command Complete overview in the Context menu of the drawing area
to adjust the presentation size so that all objects available in the interconnection
can be viewed in the drawing area.

Automatic scrolling ("AutoScroll function")

If you reach a window limitation in the drawing area when shifting an object or in the over-
view window when shifting the green frame, and if you then shortly hold the mouse point-
er in this position, an automatic scrolling into the corresponding direction is carried out:

[9.6] Example: automatic scrolling to the right in the overview window

152 1.6 EN - 08/2006 L

 L-force | Engineer
Functions
Establishing a function block interconnection

9.6.3 Inserting objects

In order to configure the functions of a device via an FB interconnection, first insert the ob-
jects required in the drawing area and thus in the interconnection.
Inserting a function block
Inserting a port block ( 155)
Inserting a variable ( 156)
Inserting a user code ( 159)

9.6.3.1 Inserting a function block

Function blocks are inserted in the interconnection from a function library.
 In the function library all the function blocks provided for the corresponding device are
classified in different function libraries according to their function.

 How to insert a function block or a system block:

1. Click the icon in the FB editor toolbar.
• The Insert function blocks dialog box appears:

2. Select the Function blocks or System blocks tab.

L 1.6 EN - 08/2006 153

L-force | Engineer
Functions
Establishing a function block interconnection

3. Select the corresponding block from the Search results list field and press the Insert
button.
• Via the Block name and Library input fields the search results can be filtered.
• The Define function block properties dialog box will open.

4. When selecting a function block, enter a name for the entity in the Function block
instance name input field.
• The instance name may not already be allocated within the interconnection.

5. Enter the instance name of the function block and possibly the code range.
6. Press OK.
• The function or system block selected is inserted in the interconnection.

Reducing the block view

For instance, if you use an extensive system block in your interconnection, but only use few
inputs and outputs, you can mask out inputs and outputs which you do not use. Thus, the
size of the system block accordingly is reduced.

 How to reduce visible inputs and outputs:

1. Click into the header of the inserted function or system block using the right mouse
button and select Connection views from the menu of the right mouse button.
• The Define visible inputs and outputs for function blocks dialog box will open.
• In the case of a function block that is inserted for the first time, all inputs and
outputs are highlighted and therefore can be viewed.

154 1.6 EN - 08/2006 L

 L-force | Engineer
Functions
Establishing a function block interconnection

2. Remove the markings of the respective control fields and press OK.
• If a block already is integrated in an interconnection, only the connected inputs
and outputs are displayed via the button Not connected hidden. Via the All but-
ton, all inputs and outputs are displayed again.

 Tip!
For an extensive function block interconnection it is reasonable to hide the inputs
and outputs that are not used.

Next worksteps
 Insert further objects in the interconnection. Inserting objects ( 153)
 Arrange the objects inserted in a reasonable manner in the drawing area. Arranging
objects in the drawing area ( 162)

9.6.3.2 Inserting a port block

All input/output ports of the application can be inserted in the interconnection in the form
of port blocks, in order to receive access to the associated element variables.

 Tip!
In between, you can change to the Ports and FB editor tabs at any time to define
new ports and afterwards insert them in the interconnection.

 How to insert a port block:

1. Click the icon in the Function block editor toolbar.
• The Insert port block dialog box appears:

2. Select the desired port in the Available port blocks list field.
• Ports which have already been inserted in the interconnection no longer are
provided for selection in the Available port blocks list field.
3. Press Insert button.
• The dialog box is closed and the port selected is inserted in the interconnection.

L 1.6 EN - 08/2006 155

L-force | Engineer
Functions
Establishing a function block interconnection

Next worksteps
 Insert further objects in the interconnection. Inserting objects ( 153)
 Arrange the objects inserted in a reasonable manner in the drawing area. Arranging
objects in the drawing area ( 162)

9.6.3.3 Inserting a variable

By the use of variables you can write inputs of ports or function or system blocks via the
keypad or read outputs by assigning a code to the respective variable; furthermore the in-
terconnection can be kept more clearly arranged and can be better maintained by means
of significantly named variables.

 Note!
Only variables that have been declared before can be inserted in the intercon-
nection!

 How to declare a variable:

1. Click the icon in the FB editor toolbar.
• The Insert variables dialog box appears:

• In the list field all variables that have already been declared are specified.
2. Press New button.
• The Establish new variable dialog box for the declaration of a new variable is dis-
played:

156 1.6 EN - 08/2006 L

 L-force | Engineer
Functions
Establishing a function block interconnection

3. Enter a name for the variable that is to be established in the Variable name input
field.
• The variable name may not already be allocated within the interconnection.
4. Select the data type for the variable from the Data type list field.
• In accordance with IEC 61131-3 integer data types can be selected.
• The data types are prenamed according to their designation.
5. For instance, a starting value can be entered for a counter variable in the Initialisa-
tion value input field.
6. Activate the Use variable task-independently control field if the variable is to be
used in several tasks.
• Then further possible settings are shown in the dialog box, via which among
other things you can define the code, the associated display text, the access, and
the value representation.
7. Activate the Use variable with mains failure protection control field if the corre-
sponding variable is to maintain its value after a mains failure.
8. Press OK.
• The Establish new variable dialog box is closed and the newly established varia-
ble is listed in the Insert variables dialog box.
9. Click Close to close the dialog box again.
• Instead of closing the dialog box you can also repeat steps 2 .... 7 to declare fur-
ther variables.

The variables declared then are presented as follows.

After you have declared a variable you can insert it in the interconnection with an input or
with an output, according to whether the variable is to be written or read.

L 1.6 EN - 08/2006 157

L-force | Engineer
Functions
Establishing a function block interconnection

 In order to interconnect the variable with an output and therefore to be able to write it
by this output, insert an assignment to the variable.

 In order to interconnect the variable with an input and therefore to be able to transfer
the variable value to this input, insert an assignment by the variable instead.

 How to insert a variable with an input or output:

1. Select the corresponding variable in the Insert variable dialog box.

2. Click insert (with input) or insert (with output) to accordingly insert the var-
iable in the FB editor.
3. Connect the variable as output to a function block.

Next worksteps
 Insert further objects in the interconnection. Inserting objects ( 153)
 Arrange the objects inserted in a reasonable manner in the drawing area. Arranging
objects in the drawing area ( 162)

158 1.6 EN - 08/2006 L

 L-force | Engineer
Functions
Establishing a function block interconnection

9.6.3.4 Inserting a user code

For parameterising an application you can establish user codes and use them in the func-
tion block interconnection.

 How to insert a user code:

1. Click the icon in the FB editor toolbar.
• The Assign user code dialog box is displayed.

• In the list field all codes that have already been declared are specified.
2. Press New button.
• The Configure user codes dialog box for establishing a new code is displayed.

L 1.6 EN - 08/2006 159

L-force | Engineer
Functions
Establishing a function block interconnection

3. Configure the Configure user code dialog box for the project.
Configuring user codes ( 160)
• The code name may not already be allocated within the interconnection.
• If the Code input field is not changed, the system numerically allocates another
code:

4. Press the buttons Insert write code or Insert read code to insert a code with an in-
put or output.
• The code selected is inserted in the FB editor with an input or output.

Configuring user codes

Parameter Information
Code Number of the user code.
• The number cannot be assigned anymore
• The numbering must be between 3000 and 9999.
Number of subcodes Number of subcodes for the user code.
(not active)
Display text DisplayCodeIndex XXXX
This text is proposed by Engineer. Assign a definite name to the user code. The name
appears in the FB editor on the user code.
Data type Selection of a data type
Display as Selection of the form in which the user code is to be displayed.
• Linear value
• Selection list
According to the selection, the dialog box changes.
Access authorisations • Read only
• Read & write
– Depending on the controller inhibit
– Depending on PLC stop
– Keypad operation: Confirmation required

160 1.6 EN - 08/2006 L

 L-force | Engineer
Functions
Establishing a function block interconnection

Displayed as linear value

Parameter Information
Linear value The user code is directly assigned with values
Unit Entry of a physical or virtual unit for the code.
Code initialisation value Entry of the code value by which the variable is to be initialised.
Change scaling of the code If the control field is active, the supplementary settings for the user code can be al-
tered.
Code decimal positions Entry of the decimal positions.
Data type Is accepted from the previously made selection.
Maximum code value +100 %
Minimum code value -100 %
Maximum variable value +16384
Minimum variable value -16384

Some user codes also have parameters by means of which, if required, particular settings
can be changed during operation or which display actual values & status information.

 By clicking the symbol the parameter list of a user code can be opened:

L 1.6 EN - 08/2006 161

L-force | Engineer
Functions
Establishing a function block interconnection

9.6.4 Arranging objects in the drawing area

After you have inserted the required objects you can arrange them in a reasonable manner
in the drawing area, so that afterwards the required connections between the inputs and
outputs can easily be established:

 How to shift an object within the drawing area:

Press the left mouse button and click the object, then drag the object to the desired
position within the drawing area by keeping the mouse button pressed.
• In doing this, please be sure that the mouse pointer is not immediately near a
connection point of an input or output, as otherwise a new connection is estab-
lished from this connection point instead.
• Via <Esc> you can cancel this action.

Shifting several objects at the same time

You can also shift several objects at the same time by selecting the objects to be shifted
and then click one of the selected objects with the left mouse button and dragging the ob-
jects selected to the desired position within the drawing area by keeping the mouse button
pressed.
 You can easily select objects that are placed together by drawing a frame around these
objects while keeping the mouse button pressed.

 If you click objects while pressing <Ctrl> they are added to an already existing selection
(multi-selection).

162 1.6 EN - 08/2006 L

 L-force | Engineer
Functions
Establishing a function block interconnection

Shifting objects that have already been interconnected

If you shift one or more objects which already contain connections, these connection are
automatically re-routed after shifting.

Next worksteps
 Insert further objects in the interconnection. Inserting objects ( 153)
 Establish the connections required for the desired function. Establishing/removing
connections

9.6.5 Establishing/removing connections

After adding objects and arranging them in a reasonable manner within the drawing area,
you can establish the connections between the available objects which are required for the
desired function.
A connection always has a direction and therefore
always has a source and a target.
• An output represents a possible source in the in-
terconnection.
• An input represents a possible target in the in-
terconnection.

Several connections can lead from one output.

• Therefore it is always possible to start a new
connection from an output.

However, maximally one connection may end in an

input.
• Therefore it is only possible to start a new con-
nection from an input if there is no connection
already ending in this input.

 How to establish a connection by drawing a line:

1. Click the connection point from which the new connection is to be started.
• It is only possible to start a new connection from an input if there is no connec-
tion already ending in this input.
• If you then move the mouse pointer away from the connection point, a new con-
nection is "drawn" from this connection point.
• Via <Esc> you can cancel this action.
2. Click the connection point where the connection is to end.
• Then a corresponding connection is automatically routed.

L 1.6 EN - 08/2006 163

L-force | Engineer
Functions
Establishing a function block interconnection

 Tip!
If you move the mouse pointer across the connection point while drawing a new
connection, you can see whether the connection is permissible or not from the col-
our of the drawn line and from the mouse pointer symbol.
In order to delete a connection, you can directly click the connection line using the
left mouse button. The connected is highlighted red. Afterwards delete the connec-
tion by pressing <Esc>.

Non-permissible connection (from output to output):

Permissible connection (from output to input):

 How to establish a connection by drawing the variable:

1. Click directly on the variable name.
• The variable is framed green.
2. Drag the blue segment to the variable name of the other block by keeping the left
mouse button pressed.

164 1.6 EN - 08/2006 L

 L-force | Engineer
Functions
Establishing a function block interconnection

3. Release the left mouse button if the variable is placed in the desired position.
• The variable is directly connected to the block. In the connected segment, the in-
stance name and the variable name are displayed.

Next worksteps
 Insert further objects in the interconnection. Inserting objects ( 153)
 If required change the processing order of the function blocks. Changing the process-
ing order
 Compile the completed interconnection. Compiling the completed interconnection
( 167)

9.6.6 Converting connections into markings

If you have established and connected several system blocks, function blocks, variables,
etc., the connections may be too complex when you use a line. There is the possibility of
representing connections belonging together by pairs of numbers.

 How to convert connections into markings:

In order to change all connections or markings, click into the FB editor using the
right mouse button, and select the command Use markings for all connections or
Use lines for all connections from the context menu.

If you only want to change an individual connection, directly click on the connec-
tion line or on one of the connectors using the right mouse button. Select the com-
mand Use connectors for connection or Use lines for connection from the context
menu.

 Tip!
You can switch between connections by line or by pairs of numbers at any time.

L 1.6 EN - 08/2006 165

L-force | Engineer
Functions
Establishing a function block interconnection

9.6.7 Changing the processing order

If you insert a function block in the connection, a processing number is automatically as-
signed to this function block. By means of this processing number it is defined in which or-
der the individual function blocks are calculated with regard to the runtime.
 The first function block inserted contains the processing number "1", the next function
block inserted contains the processing number "2", etc.
 The respective function number is displayed in the top right corner of the function
block:

 When a function block is shifted, its processing number is maintained.

 The order has an impact on the result and has to be altered in specific cases.

 How to change the processing order:

1. Select "Overview" from the list field in the top right corner of the FB editor.
• In the list field all function and system blocks of the interconnection are speci-
fied:

• In the "Order" column the processing number of each function block is listed.
2. Select the function block which is to receive a different position within the process-
ing order.

3. Shift the function block to the desired position via the or buttons.

Next worksteps
 Compile the completed interconnection. Compiling the completed interconnection

166 1.6 EN - 08/2006 L

 L-force | Engineer
Functions
Establishing a function block interconnection

9.6.8 Compiling the completed interconnection

 Click on the symbol in the FB editor toolbar to compile the interconnection.

L 1.6 EN - 08/2006 167

L-force | Engineer
Commissioning

10 Commissioning
During commissioning several (device-dependent) functions with regard to a device are
provided to you, supporting you during commissioning and the diagnostics of the device.

 Tip!
Detailed information on the respective function can be found in the documenta-
tion to the corresponding device.

168 NKS=bk=J=MULOMMS L
 L-force | Engineer
Commissioning
Diagnostics

10.1 Diagnostics

When an online connection has been established, you can for instance carry out a diagno-
stics of the device connected during commissioning.

 Note!
The diagnostics options which are available for a device depend on the corre-
sponding device and therefore can only be explained exemplarily here!
Also read the documentation supplied with the corresponding device before
you start working!

 How to carry out a diagnostics:

1. Select the corresponding device in the Project view.

2. Click the icon or select the command OnlineGo online to build up an online
connection with the controller. Going online ( 40)
3. Select the Diagnostics tab.
• When an online connection has been established, the Diagnostics tab displays
current status information about the controller.

Example: diagnostics for 9400 HighLine

L NKS=bk=J=MULOMMS 169
L-force | Engineer
Commissioning
Oscilloscope

10.2 Oscilloscope

Some Lenze devices are provided with an integrated oscilloscope function which you can
use as a means of support for commissioning, maintenance and troubleshooting.
 If a device is provided with this oscilloscope function, the Oscilloscope tab via which
you can parameterise the oscilloscope function additionally is available for the device
in the operating range.

 Tip!
Detailed information on the oscilloscope function can be found in the documenta-
tion to the corresponding device.

Example: oscilloscope function for 9400 HighLine

170 NKS=bk=J=MULOMMS L
 L-force | Engineer
Application examples
Interconnection of ready-made technology applications

11 Application examples
This chapters informs by using examples how the applications and the network co-operate
in the »Engineer«. The examples focus on the connection of process data objects and ports.
The examples can be reproduced in offline operation.

11.1 Interconnection of ready-made technology applications

 Two 9400 HighLine with TA "Actuating drive - speed" are to be interconnected.

 Each millisecond the master is to transmit a synchronisation object with the COB-ID
0x80 and the slave application is to synchronise to this object.
 The slave data is to be transmitted with the sync object to the process image.

 How to interconnect ready-made technology applications:

1. Create the following project tree in the project view.
• Rename the two inserted 9400 HighLine as master and slave.

2. Select the Machine application object in the project tree and change to the Connec-
tions tab.

L 1.6 EN - 08/2006 171

L-force | Engineer
Application examples
Interconnection of ready-made technology applications

3. Connect the ports of master and slave as follows.

4. Select the System bus (CAN) object in the project tree and change to the Synchro-
nisation tab.
5. Make the following settings in the Synchronisation tab.

172 1.6 EN - 08/2006 L

 L-force | Engineer
Application examples
Interconnection of ready-made technology applications

6. Select the menu command ExtrasUpdate project to compile the project.

• Process data objects are created.

7. Select the Master object in the project tree and change to the Ports tab. Select the
corresponding port.
• Process data object button gets active.

L 1.6 EN - 08/2006 173

L-force | Engineer
Application examples
Interconnection of ready-made technology applications

8. Press Process data object to change to the Process data objects dialog, check and
set send and receive parameters.

9. Set the process data objects of the receiver (Slave) as follows.

10. Select the menu command ExtrasUpdate project to compile the project.
• Process data objects are accepted.

Result
The communication parameters are accepted.

174 1.6 EN - 08/2006 L

 L-force | Engineer
Application examples
External device without device description (catalog)

11.2 External device without device description (catalog)

Two data words are to be sent from a 9400 HighLine to a PLC via system bus (CAN).
The following data is given.
 PW 0: Actual value
 PW 2: Status
 COB-ID: 0x300
 Transfer parameters: 10 ms (time-controlled)

 How to interconnect an external device without device description:

1. Create the following project tree in the project view.

2. Select the CAN on board object in the project tree and change to the Process data
objects tab.
3. Press Create send PDO.
• Accept the following settings in the Process data objects.

L 1.6 EN - 08/2006 175

L-force | Engineer
Application examples
External device without device description (catalog)

4. Select the 9400 HighLine object in the project tree, change to the Ports tab and cre-
ate an output port "Pre_definedCanPort" with the element variables displayed.

5. Select the CAN on board interface for the port definition and the process data ob-
ject PDO_TX1.
6. Change to the FB-Editor tab of the 9400 HighLine and connect the regenerated
port (FesterCanPort) with further function blocks.
7. Select the 9400 HighLine in the project tree and execute the menu command Ex-
trasUpdate project.

Result
Every 10 milliseconds a CAN process data object is transmitted with the 4 bytes. The data
package contains the actual value and the status.

176 1.6 EN - 08/2006 L

 L-force | Engineer
Application examples
Interconnection of an I/O terminal with a 9400 HighLine

11.3 Interconnection of an I/O terminal with a 9400 HighLine

A terminal 16×dig. I/O compact (single-wire conductor) is interconnected with a

9400 HighLine. The inputs and outputs of the I/O module are to be available in the FB edi-
tor of the 9400 HighLine.

 How to interconnect an I/O terminal with the 9400 HighLine:

1. Create the following project tree in the project view.

2. Select the T831: 16xDig. I/O compact (single-wire conductor) object in the project
tree and change to the Ports tab.
3. Copy the output port of the terminal with the context menu of the right mouse
button.
4. Insert the copied output port as input port into the port editor of the
9400 HighLine.
5. In the same way, insert the input port of the terminal as output port into the port
editor of the 9400 HighLine.
6. Select the Machine application object in the project tree and change to the Connec-
tions tab.
7. Interconnect the two ports as follows.

8. Select the 9400 HighLine object in the project tree and change to the Ports tab.

L 1.6 EN - 08/2006 177

L-force | Engineer
Application examples
Interconnection of an I/O terminal with a 9400 HighLine

9. Click to insert the two ports into the FB editor and connect them with other
function blocks.

10. Select the topmost object in the project tree and execute the menu command
ExtrasUpdate project.

Result
Two CAN Tx process data objects are created.

178 1.6 EN - 08/2006 L

 L-force | Engineer
Application examples
Profibus node

11.4 Profibus node

Four data words are to be received from the PLC and processed in the FB editor.
 Data structure:
– PW 0: Setpoint
– PW 2: Status
– PW 4: Max. value
– PW 6: Min. value
– Station address: 3

 How to process the received data words in the FB editor:

1. Create the following project tree in the project view.

2. Select the 9400 HighLine object in the project tree, change to the Ports tab and cre-
ate an input port "Profibusport" of "record" type.
• Press New to create the following element variables in the port definition.

3. Select the following interface and process data object for the port definition.

4. Select the PROFIBUS [Slot 1] object in the project tree and change to the Settings
tab.
5. Select Station address 3 from the selection field.

L 1.6 EN - 08/2006 179

L-force | Engineer
Application examples
Profibus node

6. Select the 9400 HighLine in the project tree and execute the menu command Ex-
trasUpdate project.

Result
The Profibus data transmitted for station 3 are copied into the process image and are avail-
able as port "ProfibusPort" in the FB editor.

180 1.6 EN - 08/2006 L

 L-force | Engineer
Error messages

12 Error messages
Generators and their error messages which are called during the build process.
ApplicationConnection Generator ( 182)
PortLogic generator ( 184)
System bus (CAN) generator ( 186)
Generator communication entities ( 192)

L NKS=bk=J=MULOMMS 181
L-force | Engineer
Error messages
ApplicationConnection Generator

12.1 ApplicationConnection Generator

Checking the connection between the port and the process data object

Dynamically creating a PDO [AC0001]

Response (Lenze setting printed in bold)

Error : Warning Information

Cause Remedy

A port is not further specified by the user, but it has been Check transfer parameters with the settings in the appli-
interconnected to another device. It is tried to create a cation.
dynamic PDO for this port. Connection between application and network ( 94)

Dynamic PDO for a port cannot be created [AC0002]

Response (Lenze setting printed in bold)

: Error Warning Information

Cause Remedy

Communication entity not found Apply the port to a specific interface in the port editor.
A port is not further specified, but has been interconnect- Port editor ( 125)
ed to another device. It is tried to create a dynamic PDO
for this port, which, however, fails, as the device has no
or several communication interfaces.

Dynamic ProcessDataObject for port cannot be created [AC0003]

Response (Lenze setting printed in bold)

: Error Warning Information

Cause Remedy

Communication entity not found Device is not provided with an interface enabling the dy-
A port is not further specified, but has been interconnect- namic creation of PDOs, or the supply is used up.
ed to another device. It is tried to create a dynamic PDO • Apply port to a fixed PDO (8200 and 9300), or
for this port, which, however, fails, as the device has no • convert unused, unconnected ports to automatic
or several communication interfaces. ports.

Assignment of port to ProcessDataObject is missing [AC0004]

Response (Lenze setting printed in bold)

: Error Warning Information

Cause Remedy

Internal error
There is no connection between a port and a PDO.

Definition of the network by means of port has failed [AC0005]

Response (Lenze setting printed in bold)

: Error Warning Information

Cause Remedy

Internal error
It is tried to find a network for an interconnected port, by
means of which the connection can be realised.

182 NKS=bk=J=MULOMMS L
 L-force | Engineer
Error messages
ApplicationConnection Generator

Connection beyond network limits cannot be closed [AC0006]

Response (Lenze setting printed in bold)

Error Warning : Information

Cause Remedy

It is tried to carry out a device-independent interconnec- Add the nodes to be interconnected to a network.
tion of ports which are not located within one network.
For this purpose a gateway function is required, which is
not supported at present.

Connection cannot be closed [AC0007]

Response (Lenze setting printed in bold)

Error Warning : Information

Cause Remedy

Node is not connected to the network. Add the nodes to be interconnected to a network.
It is tried to carry out a device-independent interconnec-
tion of ports which are not part of one network. For this
purpose a gateway function is required which at present
is not supported.

Data width of the target port differs from the source port [AC0008]

Response (Lenze setting printed in bold)

Error Warning : Information

Cause Remedy

Ports of a different data width are tried to be connected. Adapt the sum of the element variable data widths of
the source and target ports in the port editor.
Only the definite source port is specified. The target ports
have to be gathered from the application interconnec-
tion editor. Port editor

Storage arrangement of the target port differs from the source port [AC0009]

Response (Lenze setting printed in bold)

: Error Warning Information

Cause Remedy

Ports with a different storage layout are tried to be con- Only the definite source port is specified. The target ports
nected. have to be gathered from the application connection ed-
Example itor.
Source: WORD, DWORD (6 bytes Port editor
Target: BYTE, DWORD (6 bytes)

Only a differentiation with regard to the data width of

the element variable is made, but not with regard to the
type itself (sign/no sign or ANY_BIT types).

L NKS=bk=J=MULOMMS 183
L-force | Engineer
Error messages
PortLogic generator

12.2 PortLogic generator

Checking the ports created

Transmission direction is not supported {0} [PL0001]

Response (Lenze setting printed in bold)

: Error Warning Information

Cause Remedy

Transmission direction is invalid for the port specified. Port editor

Data length exceeds CAN-PDO length of 64 bits [PL0002]

Response (Lenze setting printed in bold)

: Error Warning Information

Cause Remedy

The data width of the port specified exceeds the permis- Reduce the data width of the element variables of the
sible data width for a CAN PDO. port to maximally 8 bytes. Defining the element variable

Port name not definite [PL0003]

Response (Lenze setting printed in bold)

: Error Warning Information

Cause Remedy

The ports of an application have to differ with regard to Allocate definite port names in the PortEditor.
their display names. Among other things, port names are used in IEC 61131
programs for enabling the access to ports via IEC 61131
variables.
Adding a port ( 127)

Invalid task context: task {0} on runtime system not available [PL0004]

Response (Lenze setting printed in bold)

: Error Warning Information

Cause Remedy

It is tried to assign the port to a task which is not availa- • Open the port editor for the device application speci-
ble in real terms on the device or in the PLC designer fied.
project. • Select the task button down on the right in the appli-
cation variable field for the port specified.
– A list with available tasks is displayed.
• Select a task from the selection list
• Close the dialog with OK.
If no task is defined in the task configuration of a 9400
PLC Designer program, the operating system automati-
cally generates a task with the designation "Default-
Task".

184 NKS=bk=J=MULOMMS L
 L-force | Engineer
Error messages
PortLogic generator

Invalid task context: port is associated with task {0} [PL0005]

Response (Lenze setting printed in bold)

Error : Warning Information

Cause Remedy

It is tried to assign a port to a task which is not available

in real terms on the device or in the PLC Designer project.
As the associated application of the editor FB is active/
enabled, the ports are automatically assigned to the user
task ("UserTask") and this warning is output.

L NKS=bk=J=MULOMMS 185
L-force | Engineer
Error messages
System bus (CAN) generator

12.3 System bus (CAN) generator

Addresses ( 186)
Baud rate and MMT master ( 187)
Synchronisation ( 188)
COB-ID ( 189)
Ports and PDO ( 191)

12.3.1 Addresses

Invalid value range for addresses (min and max exchanged?) [NWCAN0001]

Response (Lenze setting printed in bold)

: Error Warning Information

Cause Remedy

In the CAN network, Settings tab, the minimum and Accordingly change the range, so that the minimum ad-
maximum addresses of the possible address range have dress is smaller than the maximum address.
been exchanged.

Number of nodes for the network exceeded [NWCAN0002]

Response (Lenze setting printed in bold)

: Error Warning Information

Cause Remedy

More nodes than permitted in the "Settings" tab of the • Remove nodes that are not required from the net-
CAN network are assigned to the CAN network. work
or
• Increase the maximum permissible number of nodes
in the "Network/settings" tab.

Node address for nodes beyond the value range [NWCAN0003]

Response (Lenze setting printed in bold)

: Error Warning Information

Cause Remedy

An invalid node address has been entered for the node

specified.

Node address for node already exists [NWCAN0004]

Response (Lenze setting printed in bold)

: Error Warning Information

Cause Remedy

An already existing node address has been entered for

the node specified.

186 NKS=bk=J=MULOMMS L
 L-force | Engineer
Error messages
System bus (CAN) generator

Error with regard to reading the address of nodes [NWCAN0005]

Response (Lenze setting printed in bold)

: Error Warning Information

Cause Remedy

12.3.2 Baud rate and MMT master

Error with regard to reading the address of nodes [NWCAN0006

Response (Lenze setting printed in bold)

: Error Warning Information

Cause Remedy

A baud rate which is not supported has been set for the Set a different baud rate in the "Settings" tab of the asso-
node defined. ciated network.

Error with regard to processing the baud rate of an object {0} [NWCAN0007]

Response (Lenze setting printed in bold)

: Error Warning Information

Cause Remedy

The access to the baud rate parameter has failed.

No NMT master defined in the network! [NWCAN0008]

Response (Lenze setting printed in bold)

Error : Warning Information

Cause Remedy

In the entire network no NMT master which transfers the Ignore warning if an external device takes over this func-
nodes to the operational mode has been defined. tion.

More than one NMT master has been defined in the network! [NWCAN0009]

Response (Lenze setting printed in bold)

Error : Warning Information

Cause Remedy

Several nodes have been defined as NMT master in the Ignore warning if this function is desired.
specified network. They transfer the nodes to the opera-
tional mode.

Error with regard to reading the NMT master setting [NWCAN0010]

Response (Lenze setting printed in bold)

: Error Warning Information

Cause Remedy

The access to the NMT master settings has failed.

L NKS=bk=J=MULOMMS 187
L-force | Engineer
Error messages
System bus (CAN) generator

12.3.3 Synchronisation

SYNC master not defined [NWCAN0011]

Response (Lenze setting printed in bold)

: Error Warning Information

Cause Remedy

In the specified network either process data objects or • Change to the Synchronisation tab of the network
processes (tasks) are connected to the synchronisation specified.
object. However, no synchronisation object generator is • Select the node which is to transmit the synchronisa-
defined. tion object cyclically under SYNC source.

SYNC transmission identifier {0} is not supported by the nodes [NWCAN0012]

Response (Lenze setting printed in bold)

: Error Warning Information

Cause Remedy

The SYNC source specified does not support the defined Select a COB-ID under SYNC source in the Synchronisa-
COB-ID. tion tab of the network specified which supports all
nodes. (E. g: 128).

SYNC transmission cycle time {0} ms is not supported by the nodes [NWCAN0013]

Response (Lenze setting printed in bold)

: Error Warning Information

Cause Remedy

The sync source specified does not support the defined Select a cycle time under SYNC source in the Synchroni-
cycle time for transmitting the synchronisation object. sation tab of the network specified which supports all
nodes.

SYNC reception identifier {0} is not supported by the nodes [NWCAN0014]

Response (Lenze setting printed in bold)

: Error Warning Information

Cause Remedy

The SYNC receiver specified does not support the defined Select a COB-ID under SYNC source in the Synchronisa-
COB-ID. tion tab of the network specified which supports all
nodes. (E. g: 128).

Node does not support a SYNC slave function [NWCAN0015]

Response (Lenze setting printed in bold)

: Error Warning Information

Cause Remedy

Node does not support a sync slave function.

188 NKS=bk=J=MULOMMS L
 L-force | Engineer
Error messages
System bus (CAN) generator

Node does not support a SYNC master function [NWCAN0016]

Response (Lenze setting printed in bold)

: Error Warning Information

Cause Remedy

Node does not support a sync master function.

Node is SYNC transmitter and receiver at the same time [NWCAN0017]

Response (Lenze setting printed in bold)

Error Warning : Information

Cause Remedy

Reserved

Object cannot be transmitted. Node is no SYNC slave [NWCAN0026]

Response (Lenze setting printed in bold)

: Error Warning Information

Cause Remedy

The node specified either operates with synchronised Change to the Synchronisation tab of the network speci-
process data objects or processes (tasks). However, the fied and under SYNC select the following for the node re-
node has not been declared as synchronisation object re- ceiver:
ceiver. • Transmit /receive process data objects in synchro-
nised manner
• Synchronise processes (tasks)

12.3.4 COB-ID

Store of the CanId depleted [NWCAN0018]

Response (Lenze setting printed in bold)

: Error Warning Information

Cause Remedy

Too many communication objects are transmitted in the • Reduce number of port connections
network specified • Extend the COB-ID identifier range in the Settings tab
No available COB-IDs are provided anymore. of the network specified.
Please note:
The default range is designed in a manner that also ena-
bles old Lenze devices like 9300 and 8200 to operate with
it.

L NKS=bk=J=MULOMMS 189
L-force | Engineer
Error messages
System bus (CAN) generator

Invalid value range for COB-ID (min and max exchanged?) [NWCAN0019]

Response (Lenze setting printed in bold)

: Error Warning Information

Cause Remedy

The data for the automatically allocated COB-ID range • Change to the Settings tab of the network specified.
are incorrect. • Set a range in the Automatically allocate identifier
group field supporting all devices connected to the
network.
• Set from < to.

COB-ID beyond the limits. Generate new COB-ID for PDO [NWCAN0020]

Response (Lenze setting printed in bold)

Error : Warning Information

Cause Remedy

During checking the COB-IDs it was observed that the Ignore warning. In the case of time-critical processes,
COB-ID of the process data object specified (associated however, the COB-IDs allocated in the CAN objects tab of
port) is beyond the COB-ID range defined under the net- the network should be checked and possibly adjusted.
work settings. A new COB-ID is generated for the process
data object specified.

COB-ID is used more than once [NWCAN0021]

Response (Lenze setting printed in bold)

Error : Warning Information

Cause Remedy

Generate new COB-ID for PDO Ignore warning. In the case of time-critical processes,
During checking the COB-IDs it was observed that the however, the COB-IDs allocated in the CAN objects tab of
COB-ID of the process data object specified (associated the network should be checked and possibly adjusted.
port) has already been allocated. A new COB-ID is gener-
ated for the process data object specified.

COB-ID {0} beyond the value range [NWCAN0028]

Response (Lenze setting printed in bold)

: Error Warning Information

Cause Remedy

It is tried to transfer the COB-ID of the transmitter to the Check value range of the COB-ID.
receiving process data objects. In doing this, an error has
occurred. Possibly the COB-ID is beyond the valid value
range.

190 NKS=bk=J=MULOMMS L
 L-force | Engineer
Error messages
System bus (CAN) generator

12.3.5 Ports and PDO

Error with regard to the analysis of the port interconnection [NWCAN0022]

Response (Lenze setting printed in bold)

: Error Warning Information

Cause Remedy

Port-PDO assignment missing

There is no connection between a port and a process data
object.

Data width for port exceeded [NWCAN0023]

Response (Lenze setting printed in bold)

: Error Warning Information

Cause Remedy

Maximally 64 bits possible Reduce the data width of the element variables of the
The data width of the port specified exceeds the permis- port to maximally 8 bytes.
sible data width for a CAN PDO.

Template catalog for CAN communication object not found [NWCAN0024]

Response (Lenze setting printed in bold)

: Error Warning Information

Cause Remedy

Catalog not registered?

Error with regard to the generation of CAN communication object [NWCAN0025]

Response (Lenze setting printed in bold)

: Error Warning Information

Cause Remedy

Assignment of port to PDO is missing [NWCAN0027]

Response (Lenze setting printed in bold)

: Error Warning Information

Cause Remedy

No connection between a port and a process data object.

L NKS=bk=J=MULOMMS 191
L-force | Engineer
Error messages
Generator communication entities

12.4 Generator communication entities

Standard (9300 servo + 9300 ServoPLC) ( 192)

Compact (8200) ( 195)
9400 OnBoard ( 196)
EPM (compact and modular) ( 198)
9400 Profibus module ( 198)

12.4.1 Standard (9300 servo + 9300 ServoPLC)

Unexpected error [CESTD0001]

Response (Lenze setting printed in bold)

: Error Warning Information

Cause Remedy

Baud rate of {0}k is not supported by the nodes [CESTD0002]

Response (Lenze setting printed in bold)

: Error Warning Information

Cause Remedy

The baud rate cannot be transferred to the associated

code.

COB-ID {0} is assigned to several nodes [CESTD0003]

Response (Lenze setting printed in bold)

: Error Warning Information

Cause Remedy

It is not permissible for a 9300 to assign the same COB-ID Ensure that no ports of a 9300 device are connected to
several times to fixed process data objects. each other in the function block editor. By this, the ports
would receive the same COB-IDs.

Error with regard to writing to object [CESTD0004]

Response (Lenze setting printed in bold)

: Error Warning Information

Cause Remedy

Object could not be written.

192 NKS=bk=J=MULOMMS L
 L-force | Engineer
Error messages
Generator communication entities

Error with regard to writing parameter value {0} [CESTD0005]

Response (Lenze setting printed in bold)

: Error Warning Information

Cause Remedy

Parameter value could not be written to the code.

Transmission mode {0} is not supported [CESTD0006]

Response (Lenze setting printed in bold)

: Error Warning Information

Cause Remedy

The transmission mode specified is not supported.

Error with regard to writing the SYNC master settings [CESTD0007]

Response (Lenze setting printed in bold)

: Error Warning Information

Cause Remedy

The sync master settings could not be transferred to the

associated codes.

Error with regard to writing the SYNC slave settings [CESTD0008]

Response (Lenze setting printed in bold)

: Error Warning Information

Cause Remedy

The sync slave settings could not be transferred to the as-

sociated codes.

PlugIn could not be found {0} [CEPLC0001]

Response (Lenze setting printed in bold)

: Error Warning Information

Cause Remedy

For the generation of the program code a PlugIn is re- Install PlugIn.
quired (PlugIn_DrivePlcDeveloperStudio). This PlugIn
probably is not registered or there are version conflicts
with regard to the catalogs and the PlugIn.

L NKS=bk=J=MULOMMS 193
L-force | Engineer
Error messages
Generator communication entities

PlugIn method could not be found {0} [CEPLC0002]

Response (Lenze setting printed in bold)

: Error Warning Information

Cause Remedy

For the generation of the program code a PlugIn is re- Install PlugIn.
quired (PlugIn_Drive PLC Developer Studio). This PlugIn
obviously does not dispose of the method required.
There are obviously version conflicts with regard to cata-
logs and PlugIn.

PlugIn method not executable {0} [CEPLC0003]

Response (Lenze setting printed in bold)

: Error Warning Information

Cause Remedy

For the generation of program code a PlugIn is required Close all DDS or PLC Designer processes on the PC.
(PlugIn_Drive PLC Developer Studio). The method re-
quired cannot be carried out at present.

PlugIn method, error with regard to execution {0} [CEPLC0004]

Response (Lenze setting printed in bold)

: Error Warning Information

Cause Remedy

For the generation of program code a PlugIn is required

(PlugIn_DrivePlcDeveloperStudio). During execution of
the method specified, an error has occurred.

194 NKS=bk=J=MULOMMS L
 L-force | Engineer
Error messages
Generator communication entities

12.4.2 Compact (8200)

Unexpected error [CECOMP0001]

Response (Lenze setting printed in bold)

: Error Warning Information

Cause Remedy

Different transmission modes for CAN1 IN/OUT [CECOMP0002]

Response (Lenze setting printed in bold)

: Error Warning Information

Cause Remedy

The transmission modes for the CAN1 objects of the con- CAN1-IN and CAN1-OUT have to be transferred in a syn-
troller are connected. chronised manner or asynchronously.
The following combinations are permissible:
CAN1-IN CAN1-OUT
Synchronous Synchronous
Asynchronous Time or event

COB-ID {0} is assigned to nodes more than once [CECOMP0003]

Response (Lenze setting printed in bold)

: Error Warning Information

Cause Remedy

Ii is not permissible for a 9300 to assign the same COB-ID Ensure that no ports of a 9300 device are connected to
several times to fixed process data objects. each other in the function block editor.
By this, the ports would receive the same COB-IDs.

Baud rate of {0}k is not supported by nodes [CECOMP0004]

Response (Lenze setting printed in bold)

: Error Warning Information

Cause Remedy

The baud rate cannot be transferred to the associated

code.

Error with regard to writing to object [CECOMP0005]

Response (Lenze setting printed in bold)

: Error Warning Information

Cause Remedy

Object could not be written.

L NKS=bk=J=MULOMMS 195
L-force | Engineer
Error messages
Generator communication entities

Error with regard to writing parameter value {0} [CECOMP0006]

Response (Lenze setting printed in bold)

: Error Warning Information

Cause Remedy

Parameter value could not be written to the code.

Transmission mode {0} is not supported [CECOMP0007]

Response (Lenze setting printed in bold)

: Error Warning Information

Cause Remedy

The transmission mode specified is not supported.

Transmission direction is not supported [CECOMP0008]

Response (Lenze setting printed in bold)

: Error Warning Information

Cause Remedy

The transmission direction specified (input, output) is

not supported.

12.4.3 9400 OnBoard

Node cannot be SYNC source and receiver at the same time [CE94CAN0001]

Response (Lenze setting printed in bold)

: Error Warning Information

Cause Remedy

Reserved

Deviating target version - This can bring about problems with regard to the compilation and the download (expected: {0}
[CE94CAN0002]

Response (Lenze setting printed in bold)

: Error Warning Information

Cause Remedy

The target version stored in the PLC Designer project of Change to the PLC programming tab and open the PLC
the device specified does not comply with the version ex- Designer project. Select the target system in the PLC De-
pected by the generator. This can bring about problems signer and clean and compile the project again. Before
in particular if older PLC Designer projects are imported. exiting the PLC Designer, the project has to be saved.

This error message only is output in developer mode.

196 NKS=bk=J=MULOMMS L
 L-force | Engineer
Error messages
Generator communication entities

Error with regard to writing the parameter value {0} [CE94CAN0003]

Response (Lenze setting printed in bold)

: Error Warning Information

Cause Remedy

Parameter value could not be written to the code.

Node with SYNC source characteristic has to be NMT master [CE94CAN0004]

Response (Lenze setting printed in bold)

: Error Warning Information

Cause Remedy

The special feature of the 9400 is that when it is to trans- • Go to the network which is assigned to the device.
mit a synchronisation object it has to be NMT master at • Highlight the corresponding node in the Nodes tab.
the same time. – The node is framed green.
• Select
Set NMT master from the context menu of the right
mouse button.
– The master node has a black triangle in the right cor-
ner at the bottom.
Nodes ( 98)

Predefined connectionset active [CE94CAN0005]

Response (Lenze setting printed in bold)

Error Warning : Information

Cause Remedy

Node is not connected to a CAN network. Under the Set-

tings tab of the node, the Use predefined connection set
control field is selected. In the transmission process, the
settings for COB-IDs, sync, etc. according to CANopen
have been allocated.
This message is an information for the user.

L NKS=bk=J=MULOMMS 197
L-force | Engineer
Error messages
Generator communication entities

12.4.4 EPM (compact and modular)

Unexpected error [CEEPMT0001]

Response (Lenze setting printed in bold)

: Error Warning Information

Cause Remedy

Error with regard to writing the parameter value {0} [CEEPMT0002]

Response (Lenze setting printed in bold)

: Error Warning Information

Cause Remedy

Parameter value could not be written to the code.

Transmission mode {0} is not supported [CEEPMT0003]

Response (Lenze setting printed in bold)

: Error Warning Information

Cause Remedy

The transmission mode specified is not supported.

12.4.5 9400 Profibus module

EXTENSION_BOARD_SLOT could not be entered into the control configuration [CE94PRF0001]

Response (Lenze setting printed in bold)

: Error Warning Information

Cause Remedy

For the Profibus module specified no control configura-

tion module can be entered into the control configura-
tion.

Error with regard to the generation of the EXTENSION_BOARD_SLOT mappings/code [CE94PRF0002]

Response (Lenze setting printed in bold)

: Error Warning Information

Cause Remedy

No mapping code can be generated for the Profibus

module between the control configuration module and
the port variables.

198 NKS=bk=J=MULOMMS L
 L-force | Engineer
Error messages
Generator communication entities

Error with regard to the generation of the EXTENSION_BOARD_SLOT mappings/task context [CE94PRF0003]

Response (Lenze setting printed in bold)

: Error Warning Information

Cause Remedy

The mapping code between the control configuration

module and the port variables cannot be entered into the
task configuration for the Profibus module specified.

Error with regard to the generation of the EXTENSION_BOARD_SLOT mappings. Task {0} not available on runtime system
[CE94PRF0004]

Response (Lenze setting printed in bold)

: Error Warning Information

Cause Remedy

Internal error. The mapping code between the control

configuration module and the port variables cannot be
entered in the task configuration for the Profibus mod-
ule specified, as the task defined for the port is not avail-
able on the runtime system.

Invalid data width [CE94PRF0005]

Response (Lenze setting printed in bold)

: Error Warning Information

Cause Remedy

Internal error. The data type of an element variable is not

supported for the port specified.

L NKS=bk=J=MULOMMS 199
L-force | Engineer
Short menu reference
"File" menu"

13 Short menu reference

This chapter contains a list of all menu commands with references to further information
to the prevailing menu command.

13.1 "File" menu"

Icon Command Keyboard com- Information

mand
New Creating a new project ( 29)

Open Opening an existing project ( 36)

Save as

Save Saving the project ( 37)

Close Closing the project ( 38)

"Import" submenu
Import of parameter values Import of parameter set for the selected device from
a GDC parameter set file.
"Export" submenu
Export of parameter values Export of parameter set of the selected device into a
GDC parameter set file.

Exit <Alt>+<F4> Exiting the program ( 27)

13.2 "Edit" menu

Icon Command Keyboard com- Information

mand
Undo Undo the last action

Repeat Repeat undone action

Cut General processing functions in the project view

( 20)
Copy

Insert

Delete <DEL>

Rename <F2>

200 NKS=bk=J=MULOMMS L
 L-force | Engineer
Short menu reference
"Insert" menu

13.3 "Insert" menu

Icon Command Keyboard com- Information

mand
System module Inserting system modules ( 62)

Axis Inserting axes ( 64)

Component Adding components ( 68)

Gearbox Adding gearboxes ( 80)

Device module Assigning (a) device module(s) to a device ( 73)

Insert device identified on- Insert a device identified online into the project.
line
Network Inserting a network ( 96)

Machine application Inserting a machine application ( 139)

Application Generating machine applications ( 138)

13.4 "View" menu

Icon Command Keyboard com- Information

mand
Clear message window Message window ( 23)

13.5 "Online" menu

Icon Command Keyboard com- Information

mand
Go online Going online ( 40)

Go offline Going offline ( 47)

Enable controller <F8> Enabling the controller ( 49)

 Safety instructions ( 12)

Inhibit controller <F9> Inhibiting the controller ( 49)

L NKS=bk=J=MULOMMS 201
L-force | Engineer
Short menu reference
"Tools" menu

Icon Command Keyboard com- Information

mand
Start program Starting the application ( 50)

 Safety instructions ( 12)

Stop program Stopping the application ( 50)

Save parameter set Save parameter set

( 56)

Upload the parameter set <F7> Reading the parameter set from the device ( 52)

Download the parameter set <F5> Transferring the parameter set to the device (
53)

Compare parameters Compare parameters ( 55)

Download program Transferring the application to the device ( 57)

System bus configurator Start system bus configurator

13.6 "Tools" menu

Icon Command Keyboard com- Information

mand
Page setup

Print preview

Print

13.7 "Configuration" menu

Icon Command Keyboard com- Information

mand
Options

13.8 "Extras" menu

Icon Command Keyboard com- Information

mand
Update devices F11

202 NKS=bk=J=MULOMMS L
 L-force | Engineer
Short menu reference
"?" menu

13.9 "?" menu

Icon Command Keyboard com- Information

mand
Index Display online help

Direct help Display direct help for an element

Information Display information on »Engineer«

L NKS=bk=J=MULOMMS 203
L-force | Engineer
Glossary

14 Glossary

A
AIF Abbreviation for "Automation Interface". Lenze-specific interface at the con-
troller which a communication module can be attached to.
Communication module
Application Realisation of a precise function (e. g. speed control) on an individual device.
Application variable Structure consisting of element variables, communicated with a specific
transmission mode via network(s). The definition of an application variable is
completely independent of a concrete network type.
Element variable
Axis Is a special variant of a system module and contains basically one controller
and one motor, but depending on the application it may contain further devic-
es, such as a gearbox and encoder.

B
Bus server Fieldbus-specific OPC server according to DRIVECOM specification.
OPC
DRIVECOM

C
CAL Abbr. for "CAN Application Layer". Communication standard (CiA DS 201-207)
which provides the objects, protocols and services for the event or polling-con-
trolled transmission of CAN messages and the transmission of greater data ar-
eas between CAN nodes. Furthermore, CAL offers powerful processes for an
automatic assignment of message identifiers, the initialisation of network
nodes and the assignment of an individual identification to network nodes.
CAN Abbr. for "Controller Area Network". Serial, message-oriented (not node-ori-
ented) bus system for max. 63 nodes.
CANopen Communication profile (CiADS301, version 4.01), which has been created un-
der the umbrella association of the CiA ("CAN in Automation") in conformance
with the CAL ("CAN Application layer").
CiA Abbr. for "CAN in Automation (e. V.)": International manufacturer and user or-
ganisation with the target to distribute worldwide the knowledge about the
internationally standardised CAN bus system (ISO 11898) and promote its
technical further development.
Internet: http://www.can-cia.org/
Code Parameters for Lenze devices for setting the device functions.
COM Abbr. for "Component Object Model": Architecture developed by Microsoft®
for the co-operation of individual executable software components (objects)
which communicate with each other in a similar manner and are not connect-
ed until the program runs.
Communication module Generic term for Lenze function modules and communication modules.
Function module
Communication module
Communication module Device extension which can neither fulfil a function nor is able to communi-
cate without a device.
Controller Generic term for Lenze frequency inverters, servo inverters and PLCs.

204 NKS=bk=J=MULOMMS L
 L-force | Engineer
Glossary

D
DCOM Abbr. for "Distributed Component Object Model": COM, where the executable
objects are distributed to different computers within one local area network.
COM
Drive Mechatronic unit which serves a certain purpose and can be provided with
mechanical, electrical and logical interfaces with regard to its environment. A
device is called a "communication-capable device" if it is able to communicate
as a node in a network.
Unlike the mechatronic unit "system module", a device already is created by
the manufacturer and not only when a system of a concrete project is created.
Examples of devices: drive controllers, PLCs, motors, gearboxes, sensors, en-
coders
DRIVECOM "DRIVECOM User Group e.V.": International organisation of manufacturers of
drive technology, universities and institutes with the target to develop an easy
integration of drives into open automation structures.
Internet: http://www.drivecom.org/
DriveServer Lenze software which provides an easy integration of drives into open auto-
mation structures based on OPC ("OLE for Process Control").
OPC

E
Element variable Variable which is used in an application to implement a specific function of
the respective device.
Application

F
FIF Abbr. for "Function Interface". Lenze-specific interface at the controller on
which a function module can be plugged.
Function module
Function module Device extension for the FIF interface which can neither fulfil a function nor is
able to communicate without a device.
FIF

H
Hyperlink Optically highlighted reference which is activated by means of a mouse click.

L NKS=bk=J=MULOMMS 205
L-force | Engineer
Glossary

M
Machine application Implementation of a function which is generated by the interaction of several
communication-capable devices. A machine application is defined by the (de-
vice) applications involved and the exchange of application variables between
them.
Menu bar Bar in the upper position of the application window below the title bar which
shows the names of menus that open with a mouse click.

N
NMT Abbr. for "Network Management": Services and protocols for initialisation,
configuration, management and network monitoring within one CAN net-
work according to the master/slave principle.
CAN

O
OLE Abbr. for "Object Linking and Embedding": Insertion of functional objects in
other applications, e.g. a Microsoft® Excel table into a Microsoft® Word docu-
ment.
OPC Abbr. for "OLE for Process Control": Defines an interface based on the Micro-
soft® Windows® technologies OLE, COM and DCOM which is enabled via a
data exchange between different automation devices and PC programs with-
out considering driver and interface problems.
COM
DCOM

P
PDF Abbr. for "Portable Document Format", one of the universal file format devel-
oped by Adobe for the exchange of electronic documents. With this free soft-
ware Adobe® Reader® PDF files can be displayed and printed, independent of
the application and platform used for the creation.
Internet: http://www.adobe.com/
PLC Abbr. for "Programmable Logic Controller".
PLC Designer Integrated development environment for the creation of IEC 61131 programs
for Lenze PLCs.
Port Connection point or interface of an application or machine application. Input
ports serve to transmit e.g. setpoints and control commands to an application,
output ports serve to provide e.g. actual values and status messages.
Application
Machine application
Project element The topmost element (root element) in the project view with the global prop-
erties of the project.

R
Reset node Function for Lenze devices with a system bus (CAN) interface, by which the de-
vice can be reinitialised if a change with regard to the data transfer rate, node
address, or identifiers is effected. NMT- CAN
NMT

206 NKS=bk=J=MULOMMS L
 L-force | Engineer
Glossary

S
ST Abbr. for "Structured Text": Standardised programming language (IEC 61131-
3) for programmable logic controllers (PLC).
System bus (CAN) Lenze bus system based on the communication profile CANopen (CiADS301,
version 4.01).
CAN
System module Generic term for a mechatronic unit which can generally include several devic-
es, one or several networks, information on parameter values, program logic
and documentation.
A system module provides a specific technological function. It interacts with
its environment and can be generally reused in another environment or sys-
tem. The interfaces of a system module are provided by the interfaces of its
components.

T
Title bar Bar in the upper position of the application window which contains the pro-
gram symbol in the left-most position and the window symbols in the right-
most position.
Window symbol
Top-down method Design and implementation method which provides a step-by-step transition
from the general comprehensive structure to more and more special details
until the entire project structure has been created.

V
Variable Name of a data memory which can adopt values which are defined by the data
type and information on the variable declaration.

W
Window symbol Button in the right-most position of the title bar to change the window pres-
entation or close the window.

X
XML Abbr. for "EXtensible Markup Language", a meta language which describes the
structure of documents.

L NKS=bk=J=MULOMMS 207
L-force | Engineer
Index

15 Index
A CEPLC0004 194
AC0001 182 CESTD0001 192
AC0002 182 CESTD0002 192
AC0003 182 CESTD0003 192
AC0004 182 CESTD0004 192
AC0005 182 CESTD0005 193
AC0006 183 CESTD0006 193
AC0007 183 CESTD0007 193
AC0008 183 CESTD0008 193
AC0009 183 Closing the project 38
Adding a modular I/O system 78 Communication 84
Adding a port 127 Configuring the monitor window 25
Adding an I/O system 77 Connection 85
Application examples 171 Connections into markings 165
Application level 84 Control elements 13
Application notes 11 Conventions used 10
ApplicationConnection Generator 182 Copying an element 20
Assistants 26 Copyright 2
Automatic connection 87, 145 Copyright information 2
Available technology applications 171 Creating a new project 29

B D
Baud rate 103 Deleting an element 20
Diagnostic interface of the communication configurator
C 58
CAN objects 88 Downloading data from the system 32
CAN settings 91
CE94CAN0001 196
E
Editing project properties
CE94CAN0002 196
37
CE94CAN0003 197
Editing projects 28
CE94CAN0004 197
E-mail to Lenze 210
CE94CAN0005 197
Error messages 181
CE94PRF000 199
Establishing the connection 86, 144
CE94PRF0001 198
Exiting the program 27
CE94PRF0002 198
External device without device description (catalog) 175
CE94PRF0003 199
CE94PRF0004 199
F
CECOMP0001 195
FBE_insert_user_code 159
CECOMP0002 195
Feedback to Lenze 210
CECOMP0003 195
Function elements 13
CECOMP0004 195
Function library 148
CECOMP0005 195
CECOMP0006 196 G
CECOMP0007 196
Gateway diagnostic adapter -> system bus (CAN) 46
CECOMP0008 196
Generator communication entities 192
CEEPMT0001 198
CEEPMT0002 198 H
CEEPMT0003 198 History of the preselected elements 19
CEPLC0001 193
CEPLC0002 194 I
CEPLC0003 194 I/O terminal with 9400 Highline 177

208 1.6 EN - 08/2006 L

 L-force | Engineer
Index

Imprint 2 PL0003 184

PL0004 184
L PL0005 185
Layout of the safety information 11 Port editor 125
Liability 2 PortLogic generator 184
Ports 84
M Predefined connection set connection 88, 146
Manual connection 87, 146 Process data object 84
Menu bar 14 Process data objects 90
Message window 23 Processing functions in the project view 20
Mixed connection 88, 146 Profibus node 179
Monitor window 24 Project directory 29
Project phase 16
N Project properties 29
Network level 85 Project structure 17
Networks 92 Project view 17
NWCAN0001 186 Copying an element 20
NWCAN0002 186 Deleting an element 20
NWCAN0003 186 Renaming an element 20
NWCAN0004 186 Shifting an element 20
NWCAN0005 187
NWCAN0006 187 R
NWCAN0007 187 Renaming an element 20
NWCAN0009 187 Representation of parameter values 22
NWCAN0010 187
NWCAN0011 188 S
NWCAN0012 188 Safety 12
NWCAN0013 188 Safety information 11
NWCAN0014 188 Saving the project 37
NWCAN0015 188 Shifting an element 20
NWCAN0016 189 Shortcuts in the project view 21
NWCAN0017 189 Structure of the safety instructions 11
NWCAN0018 189 Synchronisation 89
NWCAN0019 190 System bus (CAN) generator 186
NWCAN0020 190 System bus CAN - network 88
NWCAN0021 190 System bus configurator 58
NWCAN0022 191
NWCAN0023 191
T
NWCAN0024 191 Title bar 14
NWCAN0025 191 Toolbar 15
NWCAN0026 189 Trademarks 2
NWCAN0027 191
U
NWCAN0028 190
User interface 13
O
V
Opening an existing project 36
Variable types 85
Operating range 21
Oscilloscope 170
W
P Working in the network view 99

Parameters
Representation in the Engineer 22
PL0001 184
PL0002 184

L 1.6 EN - 08/2006 209

 Your opinion is important to us

)(('%$&.
These instructions were created to the best of our knowledge
and belief to give you the best support for handling our pro-
duct.
If you have suggestions for improvement, please e-mail us to:
[email protected]

Thank you for your support.

Your Lenze documentation team

210 L