SHGCBAUTO-001

13375708 L-force Controls

.FZ)
Software Manual

Controller-based automation

L-force Controller
Parameterisation & Configuration

L
 L-force Controller | Parameter setting & configuration
Contents

Contents
1 About this documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.1 Document history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1.2 Conventions used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
1.3 Terminology used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.4 Notes used. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

2 Safety instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

3 The system "Controller-based automation" . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

4 Commissioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
4.1 Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
4.1.1 Module labelling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
4.2 Control elements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
4.2.1 Status LEDs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
4.3 Configuring the L-force Controller. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
4.3.1 Establishing an automatic dial-up connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
4.3.2 Entering the IP address of the L-force Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
4.3.2.1 L-force Controller with external monitor . . . . . . . . . . . . . . . . . . . . . . . . 19
4.3.2.2 L-force Controller without external monitor . . . . . . . . . . . . . . . . . . . . . 20
4.3.3 Establishing Windows® CE access rights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
4.3.3.1 Setting up Windows® CE users in the »WebConfig« . . . . . . . . . . . . . 21
4.4 Configuring the I/O modules at the backplane bus of the L-force Controller . . . . . . . . 23
4.4.1 Determining the topology of the I/O modules automatically . . . . . . . . . . . . . . . 25
4.4.2 Setting the cycle time for access to the I/O modules . . . . . . . . . . . . . . . . . . . . . . . 26
4.5 Backplane bus - error messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

5 System structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
5.1 Engineering PC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
5.2 L-force Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
5.2.1 Centralised control system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
5.2.2 Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

6 Web-based parameterisation using »WebConfig« . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

6.1 Parameterisation of the L-force Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
6.2 Requirements for working with the web-based parameterisation . . . . . . . . . . . . . . . . . . 31
6.2.1 Online connection between Engineering PC and L-force Controller . . . . . . . . . 32
6.2.2 Setting IP addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

1.1 EN - 04/2011 L 3
L-force Controller | Parameter setting & configuration
Contents

6.3 Start of the web-based parameterisation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

6.3.1 Start at the Engineering PC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
6.3.2 Start of L-force Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
6.4 User interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
6.4.1 Standard device parameters of the L-force Controller . . . . . . . . . . . . . . . . . . . . . . 38
6.4.2 Diagnostics/Command execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
6.4.3 Logbook. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
6.4.3.1 Explanations on the logbook entries, example. . . . . . . . . . . . . . . . . . . 40
6.4.3.2 Filter options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
6.4.3.3 Time filter for the display of logbook entries. . . . . . . . . . . . . . . . . . . . . 41
6.4.4 Device commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
6.4.5 User management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
6.4.6 General parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
6.4.7 Extension card parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
6.4.7.1 CAN communication card (MC-CAN2) . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
6.4.7.2 PROFIBUS master communication card (MC-PBM) . . . . . . . . . . . . . . . 44
6.4.8 Polling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
6.4.9 Language selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
6.4.10 Parameter list buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

7 Programming with the »PLC Designer« . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

7.1 Basics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
7.2 Configuration and parameterisation via the control application . . . . . . . . . . . . . . . . . . . 47
7.3 Accessing L-force Controller parameters from the PLC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
7.3.1 The LDM_ParameterAccess_FB function block. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
7.3.2 The LLS_AddLog function block - Generate logbook entry . . . . . . . . . . . . . . . . . . 50

8 Backup&Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

9 Data integrity in the case of a voltage failure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

9.1 Retain variables of the PLC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
9.2 Backup with UPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
9.2.1 Persisting the PLC's retain variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
9.2.2 Persisting changed parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
9.2.3 Persisting log files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

10 Replacing the L-force Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

10.1 Removing the L-force Controller. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
10.2 Connecting a new L-force Controller. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
10.3 Subsequent use of retain data on the new controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

4 L 1.1 EN - 04/2011
 L-force Controller | Parameter setting & configuration
Contents

11 Remote maintenance and diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

11.1 telnet connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
11.1.1 Settings of the web-based parameterisation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
11.2 FTP connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
11.2.1 FTP settings with the »WebConfig« . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
11.2.2 FTP and web settings in the Internet Explorer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
11.3 Windows® CE functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
11.3.1 Remote Display - remote control of L-force Controller via Internet or LAN . . . 67
11.4 Logbook function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
11.4.1 Logbook query via »WebConfig«. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
11.4.1.1 Logbook codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

12 Visualisation with »VisiWinNET®« . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

12.1 Introduction to »VisiWinNET®« . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
12.1.1 »VisiWinNET®« Compact. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
12.2 Basic functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
12.2.1 Start the »VisiWinNET®« development system . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
12.2.1.1 »VisiWinNET®« Smart. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
12.2.1.2 »VisiWinNET®« Professional . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
12.2.2 Creating a new project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
12.2.2.1 Creating a new project in »VisiWinNET®« Smart . . . . . . . . . . . . . . . . . 73
12.2.2.2 Creating a new project in »VisiWinNET®« Professional . . . . . . . . . . . 74
12.2.3 Open the Project Explorer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
12.3 Constellation and connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
12.3.1 Using the LogicandMotionV3 direct driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
12.3.1.1 Using direct drivers for visualisations under Windows CE . . . . . . . . 77
12.3.1.2 Using direct drivers for visualisations under Windows XP . . . . . . . . 79
12.3.2 Inserting the OPC tunnel in »VisiWinNET®« . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
12.3.3 The Lenze Variables Browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
12.3.3.1 Browsing for variable definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
12.3.3.2 Accept variable definitions to project . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
12.3.4 Entering variables manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
12.3.4.1 Access to PLC variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
12.3.5 Linking control elements and variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
12.3.6 Transferring an application to the target device . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
12.4 Configuration of the OPC tunnel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
12.4.1 Local visualisation (integrated control system) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
12.4.2 External visualisation (remote access) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
12.4.3 External Visu on a Windows XP/XP Embedded L-force Controller (remote access)
91
12.5 Installing additional fonts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

1.1 EN - 04/2011 L 5
L-force Controller | Parameter setting & configuration
Contents

12.6 Lenze specifications - exception handling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

12.6.1 Timeout (waiting position) of the CAN OPC server influences the time response of
the visualisation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

13 Parameter reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
13.1 Structure of the parameter description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
13.1.1 Data types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
13.1.2 Parameters with read access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
13.1.3 Parameters with write access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
13.1.3.1 Parameters with a setting range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
13.1.3.2 Parameters with a selection list. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
13.1.3.3 Parameters with a bit-coded setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
13.1.3.4 Parameters with subcodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
13.1.4 Parameter attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
13.2 Parameters of standard devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
13.3 Ethernet (on board) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
13.4 EtherCAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
13.5 PLC (Logic/Motion) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
13.6 Backup&Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
13.7 Extension cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
13.7.1 CAN communication card (MC-CAN2). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
13.7.2 PROFIBUS master communication card (MC-PBM) . . . . . . . . . . . . . . . . . . . . . . . . . 136

14 Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

15 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

Your opinion is important to us. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146

6 L 1.1 EN - 04/2011
 L-force Controller | Parameter setting & configuration
About this documentation

1 About this documentation

This documentation contains general information on the parameterisation and
configuration of an L-force Controller.
This manual belongs to the "Controller-based Automation" manual collection which
consists of the following documentation:

Documentation Subject
System manuals • Control technology - System structure & configuration
"Controller-based automation" • Visualisation - System structure & configuration
(Software) manual • L-force Controller - Parameter setting & configuration
Communication manuals • Control technology CANopen - Commissioning & configuration
"Controller-based automation" • Control technology EtherCAT - Commissioning & configuration
• Control technology PROFIBUS - Commissioning & configuration
Further software manuals • »Backup & Restore«
• »Global Drive Control« (»GDC«)
– L-force Controller as gateway - Parameter setting & configuration
• »Engineer«
• »PLC Designer«
• »VisiWinNET® Smart«

 Information on the use of the L-force Controllers beyond control technology can
be found in the system manuals which are designed to meet the respective case
of application.

1.1 EN - 04/2011 L 7
L-force Controller | Parameter setting & configuration
About this documentation

Further technical documentation for Lenze components

Further information on Lenze components which can be used in connection with L-force
Controllers can be found in the following documentation:
Mounting & wiring Legend:
 MA EPM-Sxxx (I/O system 1000)  Printed documentation
 MA Controller 3200 C  Online help/PDF
 MAs for Servo Drives 9400 Abbreviations used:
 MAs for Inverter Drives 8400 SHB System Manual
 MAs for the ECS servo system BA Operating Instructions
 MA MC-CAN2 communication card MA Mounting Instructions
 MA MC-ETC communication card SW Software manual
 MA MC-PBM communication card KHB Communication manual
 MAs for communication modules

Parameterisation, configuration, commissioning

 SHB I/O system 1000 (EPM-Sxxx)
 SHB Controller 3200 C
 SW Servo Drive 9400 HighLine / PLC
 9400 HighLine commissioning guideline
 SW Inverter Drive 8400
BaseLine / StateLine / HighLine / TopLine
 BAs for the ECS servo system
 KHBs for the communication modules

Programming
 SW 9400 function library

Establishing a network
 KHBs for the communication modules

Target group
This documentation is intended for persons who want to parameterise, configure, and
diagnose a control system using an L-force Controller in conjunction with the L-force »PLC
Designer« engineering software.

8 L 1.1 EN - 04/2011
 L-force Controller | Parameter setting & configuration
About this documentation
Document history

1.1 Document history

Version Description
1.0 10/2010 TD11 First edition (control technology 3.0)
.1.1 04/2011 TD11 Updated for control technology 3.1

 Tip!
Information and tools regarding Lenze products can be found in the download area
on: http://www.Lenze.com

1.1 EN - 04/2011 L 9
L-force Controller | Parameter setting & configuration
About this documentation
Conventions used

1.2 Conventions used

This documentation uses the following conventions to distinguish between different types
of information:

Type of information Writing Examples/notes

Spelling of numbers
Decimal separator Point Generally the decimal point is used.
For example: 1234.56
Text
Version information Text colour blue All pieces of information that only apply to or from a
specific software version are indicated accordingly in
this documentation.
Example: This function extension is available from
software version V3.0!
Program name »« The Lenze PC software »Engineer«...
Window Italics The Message window... / The Options dialog box...
Variable identifier By setting bEnable to TRUE...
Control element Bold The OK button... / The Copy command... / The
Properties tab... / The Name input field...
Sequence of menu If several commands must be used in sequence to
commands carry out a function, then the individual commands
are separated by an arrow. Select FileOpen to...
Keyboard command <Bold> Press <F1> to open the online help.
If a command requires a combination of keys, a "+" is
placed between the key symbols:
With <Shift>+<ESC> you can...
Program listings Courier IF var1 < var2 THEN
Keyword Courier bold a = a + 1
END IF

Hyperlink underlined Optically highlighted reference to another topic. Is

activated via mouse-click in this documentation.
Icons
Page reference ( 10) Optically highlighted reference to another page. Is
activated via mouse-click in this documentation.
Step-by-step instructions Step-by-step instructions are indicated by a
 pictograph.

10 L 1.1 EN - 04/2011
 L-force Controller | Parameter setting & configuration
About this documentation
Terminology used

1.3 Terminology used

Term Meaning
»PLC Designer« Lenze engineering tools which support you throughout the whole life cycle of a
machine with an Industrial PC - from planning to maintenance.
»VisiWinNET®«
L-force Controller The L-force Controller 3200 C is the central control component of
Controller-based Automation.
PLC Programmable Logic Controller
SD card The SD card serves to save the user-specific data of the L-force Controller.
• In the file system (e.g. Windows Explorer), the SD card is shown as
\USBStorage directory. (The system-internal connection is carried out via
the USB adapter).

1.1 EN - 04/2011 L 11
L-force Controller | Parameter setting & configuration
About this documentation
Notes used

1.4 Notes used

The following signal words and icons are used in this documentation to indicate dangers
and important information:

Safety instructions
Structure of safety instructions:

 Pictograph and signal word!

(characterise the type and severity of danger)
Note
(describes the danger and gives information about how to prevent dangerous
situations)

Pictograph Signal word Meaning

Danger! Danger of personal injury through dangerous electrical voltage
 Reference to an imminent danger that may result in death or serious
personal injury if the corresponding measures are not taken.
Danger! Danger of personal injury through a general source of danger
 Reference to an imminent danger that may result in death or serious
personal injury if the corresponding measures are not taken.
Stop! Danger of property damage
 Reference to a possible danger that may result in property 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

Reference to another documentation


12 L 1.1 EN - 04/2011
 L-force Controller | Parameter setting & configuration
Safety instructions

2 Safety instructions
Please observe the following safety instructions when you want to commission a controller
or system using the L-force Controller.

 Read the documentation supplied with the corresponding field device

thoroughly before starting to commission the devices with the L-force
Controller!
The device documentation contains safety instructions which must be
observed!

 Danger!
According to our present level of knowledge it is not possible to ensure the
absolute freedom from errors of a software.
If necessary, systems with built-in controllers must be provided with additional
monitoring and protective equipment according to relevant safety regulations
(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 would be a risk of injury by
the moving machine parts.

 Stop!
If you change parameters in the engineering software while a device is
connected online, the changes will be directly accepted by the device!
A wrong parameter setting can cause unpredictable motor movements. By
unintentional direction of rotation, too high speed or jerky operation, the driven
machine parts may be damaged!

1.1 EN - 04/2011 L 13
L-force Controller | Parameter setting & configuration
The system "Controller-based automation"

3 The system "Controller-based automation"

Central control technology keeps finding its way into automation technology. Due to their
scaling options and various possibilities of combining visualisation and control in one
device, Industrial PCs offer great advantages for many applications.
The L-force Controllers are available in the following software equipments:
 L-force Controller as control system
 L-force Controller as visualisation system (depending on the mode, an additional panel
may be available)
 L-force Controllers as component, on request with operating system, without further
software
The system "Controller-based automation" enables central control of Logic and Motion
systems.

 More information on how to parameterise and configure the single bus systems
can be found in the following communication manuals:
• Control technology CANopen - Commissioning & configuration
• Control technology EtherCAT - Commissioning & configuration
• Control technology PROFIBUS - Commissioning & configuration

14 L 1.1 EN - 04/2011
 L-force Controller | Parameter setting & configuration
The system "Controller-based automation"

Lenze provides well-matched system components:

 L-force Controller as control and visualisation system
– The L-force Controller is the central component of PC-based automation, which
controls the Logic and Motion functionalities by means of the runtime software.
– The L-force Controller uses the fieldbus to communicate with the field devices.
 Engineering tools for the Engineering PC
– The Engineering PC uses Ethernet to communicate with the L-force Controller.
– Use the various Engineering tools to configure and parameterise the system.
 Fieldbuses
 Field devices

1.1 EN - 04/2011 L 15
L-force Controller | Parameter setting & Configuration
Commissioning
Identification

4 Commissioning
This chapter provides general information on the first commissioning of an L-force
Controller. Depending on the actual hardware installed, different settings are required to
integrate the L-force Controller (for machine control purposes) into a network.

 Note!
• Please observe the predefined IP addresses when commissioning your L-force
Controller for the first time:
– Engineering PC: 192.168.5.100
– L-force Controller: 192.168.5.99

Further information on the L-force Controller IP address setting can be found in the
following section: Entering the IP address of the L-force Controller ( 19)

 Read the Mounting Instructions accompanying the controller first before you
start working!
The Mounting Instructions contain safety instructions which must be observed!

 Further information on the device-specific properties can be found in the

Hardware Manual of the corresponding L-force Controller.

4.1 Identification

 Note!
Here the documentation provides some general information on the
commissioning of an L-force Controller. Depending on the design and version of
the L-force Controller, the commissioning can vary.

Every L-force Controller is provided with a nameplate containing the device data. The
device data are helpful for being able to detect the technical equipment of the L-force
Controller.
 Via the »WebConfig«, you can detect the L-force Controller equipment on the basis of
the parameter values. Online connection between Engineering PC and L-force
Controller ( 32)

16 L 1.1 EN - 04/2011
 L-force Controller | Parameter setting & Configuration
Commissioning
Control elements

4.1.1 Module labelling

The labelling on the extension modules indicates the possible connections to the fieldbus.

[4-1] Module labelling, example: the CAN communication card (MC-CAN2)

4.2 Control elements

Depending on their equipment and model range, the different series provide different
control elements.
 If extensive diagnostics and configurations are required, the L-force Controller can also
be operated via external input devices such as a keyboard or mouse.

4.2.1 Status LEDs

The L-force Controller 3200 C is provided with LEDs, which show the current operating
status
 Power
 Error
 Status 1
 Status 2

Signalling of the status LEDs Status/meaning

Power Error Status1 (busy)
- Blinking red - Fatal error (abort)
(5 Hz) • SD card not available/not inserted in the
module slot correctly
• No operating system licence available
- - Green on Controller is running (operating status):
• PLC project is running (device is running,
operating status)
- - Blinking green/yel- User action required: "Load PLC project"
low • PLC started, project is not running
(0.5 Hz)
- - Blinking green Starting process of the Controller active
(0.5 Hz)

1.1 EN - 04/2011 L 17
L-force Controller | Parameter setting & Configuration
Commissioning
Control elements

Signalling of the status LEDs Status/meaning

Power Error Status1 (busy)
- Blinking red/green - Mains switching required
(5 Hz)
Green on - - • Controller is switched on
• "Time not synchronised" (missing time
information)
– When the controller is switched off, the
time information is not buffered. This is
not documented in the logbook.

Depending on the running software application, different control modes of the LEDs are
possible.

 Further information on the software-specific LED control can be found in the

hardware manual of the respective L-force Controller.

4.3 System boot-up

 Note!
Removal of the SD card will lead to a malfunction of the system!
• The SD card is required for the system start because the operating system and
all system files needed for the boot process are stored on the SD card.

 The SD card and the internal flash memory are the storage media of the L-force
Controller
 The L-force Controller saves the user data (like projects and individual data) on the SD
card. The operating system and the Lenze software are saved in the internal flash
memory.

 Note!
• The L-force Controller is preconfiured, i.e. during initial commissioning the
touch display is already precalibrated and a default IP address (192.168.5.99)
is defined.
• After the starting process, the default IP address can be edited. For this,
connect an external display to the Controller. After 15 seconds the dialog
window for the network configuration closes automatically; the L-force
Controller continues the starting process. Entering the IP address of the L-
force Controller ( 19)

 Tip!
The preset IP configuration can be configured using the »WebConfig«.

18 L 1.1 EN - 04/2011
 L-force Controller | Parameter setting & Configuration
Commissioning
Configuring the L-force Controller

4.4 Configuring the L-force Controller

This chapter will inform you on how to configure the L-force Controller during initial
commissioning. The configuration of the IP address is maintained after system restart.

4.4.1 Establishing an automatic dial-up connection

Further information on how to establish an automatic dial-up connection, remote

maintenance and diagnostics options can be found under: Remote maintenance and
diagnostics ( 58)
In order to carry out a remote maintenance on the L-force Controller different mechanisms
are provided:
telnet connection ( 59)

FTP connection ( 61)

4.4.2 Entering the IP address of the L-force Controller

The L-force Controller has the following network settings by default:

Setting Value
IP address 192.168.5.99
Subnetwork 255.255.255.0
Default gateway 192.168.5.1

 When the L-force Controller is commissioned for the first time, the desired
IP address must be entered.

4.4.2.1 L-force Controller with external monitor

 Note!
Observe the switch-on sequence when using an external display (monitor/pan-
el) to ensure that the external display can be correctly controlled by the L-force
Controller:
• Connect the external display to the DVI output of the L-force Controller and
switch it on before switching on the L-force Controller.

 Tip!
Connect a keyboard to the L-force Controller in order to be able to enter the IP
address. Then you can make the entries:

1.1 EN - 04/2011 L 19
L-force Controller | Parameter setting & Configuration
Commissioning
Configuring the L-force Controller

[4-1] IP settings of the L-force Controller by default

 Start the control panel with <Shift+F4>.

 Start the network connections by double-click and enter the IP address, subnet mask,
and the default gateway.

 After clicking the button the IP address is saved and need not be entered again
when the system is restarted.

4.4.2.2 L-force Controller without external monitor

If there is no external monitor available, you need a laptop with an appropriate IP address
as well as a subnet mask and a default gateway to select the settings.
 Connect the laptop to the L-force Controller by means of a "crossed" network cable.
 Change the settings on an HTML compliant browser:
Setting IP addresses ( 32)
 Establish the connection from the laptop to the L-force Controller. For this purpose
enter the IP address of the L-force Controller on the browser: 192.168.5.99 (default
setting).
 Select the Ethernet menu button and enter the desired IP address, subnet mask, and
the default gateway of the L-force Controller.
 Click Accept & Save all
 Set Use IP configuration to the value "Activate device"
 Click again Accept & Save all in order to save the network settings permanently.

IP address selection via file

172.31.207.88 {IP address}

255.255.255.0 {subnet mask}
172.31.201.1 {gateway}
[4-2] Example of an "ip.txt" file for selecting the IP address

The L-force Controller allows initial IP address selection by means of an

ASCII file "ip.txt".
 Copy the "ip.txt" file to the root directory of the SD card (directory \USBstorage).
 When the system is started ...
– the L-force Controller reads in the IP address file "ip.txt" from the SD card
– the L-force Controller writes the result (Result) to the ip.txt file:

20 L 1.1 EN - 04/2011
 L-force Controller | Parameter setting & Configuration
Commissioning
Configuring the L-force Controller

172.31.207.88
255.255.255.0
172.31.201.1

Result: 2010-9-24 14:42:23 :Success: IP Settings taken from file.

[4-3] Example of an "ip.txt" file for IP address selection with result entry

 Then, the L-force Contoller renames the file: "ip_old.txt".

 To select the IP address once again using the file, the file must be renamed to "ip.txt".

 Tip!
The "ip.txt" file can be used to select the use of the DHCP. For this, write "DHCP"
into the first line of the file. Then, the following lines will no longer be considered.

4.4.3 Establishing Windows® CE access rights

In order to be able to establish a connection to the L-force Controller, each user has to be
assigned access rights. For this the respective user has to be set up as a Windows® CE user
with a user name and a password. Windows® CE users can be set up via the »WebConfig«
and the »Engineer«:
Setting up Windows® CE users in the »WebConfig« ( 21)

The representation for user 1 is displayed. Users 2 to 10 are represented analogously.

4.4.3.1 Setting up Windows® CE users in the »WebConfig«

 Note!
You have to be set up as Windows® CE user to have authorisations for further
services like FTP, telnet, or web server access.

 Up to ten Windows® CE users can be set up in the »WebConfig« in the User

management area.
 In codes 101 to 169 the user name, password, and various authorisations are set up for
a maximum of ten users.

1.1 EN - 04/2011 L 21
L-force Controller | Parameter setting & Configuration
Commissioning
Configuring the L-force Controller

The representation for user 1 is displayed. Users 2 to 10 are represented analogously.

Detailed information on the parameters can be found in the following section:
Parameters of standard devices ( 99)

22 L 1.1 EN - 04/2011
 L-force Controller | Parameter setting & Configuration
Commissioning
Configuring the I/O modules at the backplane bus of the L-force Controller

4.5 Configuring the I/O modules at the backplane bus of the L-force Controller

In the »PLC Designer« you can configure the I/O modules of the L-force system 1000.
 The following illustration is a schematic representation of the L-force Controller
hardware structure.

The L-force Controller consists of the two components:

 Head end: Controller with a PLC control in the form of a Soft-PLC by the company 3S.
 I/O modules: Up to 64 modules which are connected to the controller via the Lenze
backplane bus.
In order to be able to access the modules by means of a PLC program (i.e. read input signals
/ write output signals), the creation of a terminal configuration in the »PLC Designer« is
required.
For this, simulate the physical arrangement of the I/O modules in the control configuration
of the PLC.

[4-4] Example: Mapping of the physical topology (module 1 to module 7) in the control configuration in the »PLC Designer«

1.1 EN - 04/2011 L 23
L-force Controller | Parameter setting & Configuration
Commissioning
Configuring the I/O modules at the backplane bus of the L-force Controller

 How to configure the I/O modules in the »PLC Designer«:

1. Append the desired I/O modules as Devices below the I/O module coupler.
Note: The sequence of the I/O modules in the device tree must comply with the
physical arrangement.

2. Representation in the device tree:

• If everything is configured correctly, all modules are marked with the symbol
in the device tree after going online and starting the PLC.

• In the event of an error, i.e. if the configuration deviates from the physical
arrangement, the modules are marked with the symbol.

24 L 1.1 EN - 04/2011
 L-force Controller | Parameter setting & Configuration
Commissioning
Configuring the I/O modules at the backplane bus of the L-force Controller

4.5.1 Determining the topology of the I/O modules automatically

In addition to appending devices manually, the »PLC Designer« allows for the automatic
recognition of I/O modules connected (fieldbus scan).
 Execute the command Start Search in the context menu of the I/O module coupler:

1.1 EN - 04/2011 L 25
L-force Controller | Parameter setting & Configuration
Commissioning
Configuring the I/O modules at the backplane bus of the L-force Controller

4.5.2 Setting the cycle time for access to the I/O modules

In the L-force Controller a central bus cycle task is selected, which is valid for the processing
of all fieldbuses and for the I/O modules
connected via the backplane bus.
 This selection is a default setting and can be overwritten in the bus master nodes
(EtherCAT master, CANopen_Manager, I/O module coupler, ....).
 If you require a shorter cycle time for the backplane bus than the one selected in the L-
force Controller, you can select a faster task in the I/O module coupler: Select the bus
cycle task for the EtherCAT master under the EtherCAT I/O Mapping tab (unless this has
been carried out in the task configuration already).

 At first, the »PLC Designer« defines a processing task for the PLC for generating the
I/O image. An individual Bus cycle task can be defined for each individual module,
within which the process image for the module is then created.
 Altogether three different tasks for the I/O modules can be defined. The limitation to
three tasks is determined by the system on the basis of the backplane bus specification.
 The backplane bus controller uses two internal bus cycle groups for each task; one for
input signals and one for the outputs. A total of six groups is provided.

26 L 1.1 EN - 04/2011
 L-force Controller | Parameter setting & Configuration
Commissioning
Backplane bus - error messages

4.6 Backplane bus - error messages

 Error messages are displayed on the 'Diagnostics' tab of the I/O module coupler.

[4-5] Example: Topology error, the EPM-S501 module cannot be reached at the backplane bus.

Error messages
The following error messages can be displayed:

Error number Error text/remedy

11 Too many I/O modules for the task cycle time selected.
• Increase cycle time.
12 FIFO response full.
• Contact Lenze
32 Timeout reset
• Contact Lenze
33 Timeout reset error
• Contact Lenze
96 Too many I/O modules for the task cycle time selected.
• Increase cycle time.
97 Too many I/O modules for the task cycle time selected.
• Increase cycle time.
98 Too many I/O modules for the task cycle time selected.
• Increase cycle time.
99 Too many I/O modules for the task cycle time selected.
• Increase cycle time.
100 Too many I/O modules for the task cycle time selected.
• Increase cycle time.
101 Timeout for master queue operation
• Contact Lenze
102 Bus initialisation error with one I/O module
• Contact Lenze
103 Master queue operation error
• Not all I/O modules can be reached.
104 Read semaphore timeout for group 1
105 Read semaphore timeout for group 2
106 Read semaphore timeout for group 3
107 Write semaphore timeout for group 1
108 Write semaphore timeout for group 2
109 Write semaphore timeout for group 3
110 Internal backplane bus error (hardware error)
• Contact Lenze
116 Read semaphore timeout for group 1

1.1 EN - 04/2011 L 27
L-force Controller | Parameter setting & Configuration
Commissioning
Backplane bus - error messages

Error number Error text/remedy

117 Read semaphore timeout for group 2
118 Read semaphore timeout for group 3
119 Write semaphore timeout for group 1
120 Write semaphore timeout for group 2
121 Write semaphore timeout for group 3
136 Configuration error in the I/O module topology.
137 Too many tasks for the processing of I/O modules. Three tasks at the maxi-
mum.
138 Device description does not contain a device type
• Contact Lenze
139 Error while writing the initialisation parameters
• Contact Lenze
140 No definition for number of channels in device description
• Contact Lenze
181 Synchronisation of the I/O system incorrect
• Contact Lenze
200 SDO timeout
• Contact Lenze
220 SDO communication error
• Contact Lenze
221 Physical I/O module topology could not be read.
• Contact Lenze
222 I/O system driver could not be opened.
• Contact Lenze

28 L 1.1 EN - 04/2011
 L-force Controller | Parameter setting & configuration
System structure
Engineering PC

5 System structure
This chapter gives you an overview of the general system structure in control technology.

 Further information can be found in the respective documentation of the

corresponding Engineering software.

5.1 Engineering PC

 The Engineering PC serves to

– parameterise, configure and maintain the L-force Controller (»WebConfig« ),
– parameterise, configure, and maintain the field devices connected
(»Engineer«, »Global Drive Control«),
– program the L-force Controller (»PLC Designer«),
– create a visualisation project (»VisiWinNET®«)
– prepare Backup/Restore (»Backup & Restore«).

5.2 L-force Controller

 The following runs on the L-force Controller:

– the control software (L-force Logic, L-force Motion),
– the fieldbus drivers,
– the optional visualisation software, and
– additional services (Data manager, web server, logbook).

1.1 EN - 04/2011 L 29
L-force Controller | Parameter setting & configuration
System structure
L-force Controller

5.2.1 Centralised control system

 The PLC of the L-force Controller (Logic/Motion) is the central control component,
consisting of the PLC runtime program with the running PLC application.
– Via the Data manager and the fieldbus driver the PLC (Logic/Motion) has access to
the system components and field devices.

[5-1] * The PROFIBUS fieldbus driver can only be accessed via PLC (Logic/Motion). Access via Engineer, GDC or VisiWinNET®
Runtime is not provided.

 Field devices and the L-force Controller form the machine to be commissioned by the
Engineering PC.
 The L-force Controller can read parameters from and write parameters to the
connected field devices via the fieldbus (Logic/Motion).

5.2.2 Data

With the Data manager, L-force Controllers contain a central tool for the configuration and
data management of a system.
 A system in this connection is the combination of an L-force Controller and the field
devices connected to it and registered via the fieldbus.

30 L 1.1 EN - 04/2011
 L-force Controller | Parameter setting & configuration
Web-based parameterisation using »WebConfig«
Parameterisation of the L-force Controller

6 Web-based parameterisation using »WebConfig«

This chapter provides information on the parameterisation of the L-force Controller using
web-based parameterisation.

6.1 Parameterisation of the L-force Controller

All settings by means of which you can parameterise the L-force Controller are summarised
in a numbered parameter list.
The »WebConfig« can be carried out LOCALLY on the L-force Controller or REMOTELY via
http by each Engineering PC transmitted which can be reached via the network. The
Engineering PC is a desktop computer including the Windows® XP operating system.

 Tip!
The web server and the »WebConfig« for the web-based parameterisation are
preinstalled on the L-force Controller.

 The parameter lists can be found in the chapter: Parameter reference ( 95)

6.2 Requirements for working with the web-based parameterisation

This chapter provides you with information on how to prepare a remote connection for the
web-based parameterisation.

1.1 EN - 04/2011 L 31
L-force Controller | Parameter setting & configuration
Web-based parameterisation using »WebConfig«
Requirements for working with the web-based parameterisation

6.2.1 Online connection between Engineering PC and L-force Controller

 Connect the Engineering PC directly to the L-force Controller using a

network cable.
or
 Connect the L-force Controller to the network to which the Engineering PC has access.

 Note!
In the case of a direct connection between the Engineering PC and the L-force
Controller, a crossed network cable is required.
The settings of the static IP address of the Engineering PC are only to be carried
out for the direct connection between the Engineering PC and L-force Controller.

6.2.2 Setting IP addresses

 Note!
Recommended setting for the Engineering PC:
IP address: <192.168.5.100>
Standard settings of the L-force Controller:
IP address: <192.168.5.99>, subnetwork <255.255.255.0>.

Setting for the direct connection between Engineering PC and L-force Controller:

 How to set the static IP address of the Engineering PC:

1. Open the Network connections dialog box Network connections.
(StartSettingsNetwork connections)
2. Select the network interface the L-force Controller is connected to.
Right-click Properties.
3. Select Internet protocol (TCP/IP).
4. Click the Properties button.
5. Select the Alternative configuration tab.
6. Select the User configured option.
• Enter the IP address of the L-force Controller (default address: <192.168.5.99>).
• Enter the subnet mask of the Engineering PC
(standard setting: <255.255.255.0>)
7. Close the individual dialog windows with OK or Close

The Properties of internet protocol (TCP/IP) dialog window

32 L 1.1 EN - 04/2011
 L-force Controller | Parameter setting & configuration
Web-based parameterisation using »WebConfig«
Requirements for working with the web-based parameterisation

 How to set the browser:

1. Open the browser at the Engineering PC
(This setting refers to the Microsoft Internet Explorer).
2. Select the Proxy settings dialog window
(ToolsInternet options ConnectionsSettingsAdvanced)
3. Position the cursor in the Exceptions field at the end of the entries available.
4. Enter the IP address of the L-force Controller:
<;172.31.217*> (example of the IP address of an L-force Controller, default address:
<192.168.5.99>)
5. Close the individual dialog windows with OK.

1.1 EN - 04/2011 L 33
L-force Controller | Parameter setting & configuration
Web-based parameterisation using »WebConfig«
Start of the web-based parameterisation

6.3 Start of the web-based parameterisation

6.3.1 Start at the Engineering PC

 Start a browser at the Engineering PC and enter the IP address of the L-force Controller.
– The dialog box for entering the connection data appears:
.

1. Enter <User name:password>. As default setting, admin:admin is preselected. Any user

set up on the L-force Controller can log in. User management ( 42)
2. Confirm with OK .
3. Afterwards the user interface of the web-based parameterisation appears.
User interface ( 36)

6.3.2 Start of L-force Controller

After connection to the current supply, the L-force Controller starts automatically. If no
external keyboard has been connected, the on-screen keyboard can be shown via the
function key
<F1>.
 Change to <Shift+F4> in the Control Panel.
Note: Changing predefined settings may lead to a malfunction of the system!
• Do not change the Internet Options settings to avoid an unexpected behaviour
of the system!

34 L 1.1 EN - 04/2011
 L-force Controller | Parameter setting & configuration
Web-based parameterisation using »WebConfig«
Start of the web-based parameterisation

 Double-click the WebConfig icon:

.

1. Enter <User name:password> in the Enter Network Password dialog box . As standard
setting admin:admin is preselected. Every registered user can log in.
2. Confirm with OK .
3. Afterwards the user interface of the web-based parameterisation appears.
User interface ( 36)

1.1 EN - 04/2011 L 35
L-force Controller | Parameter setting & configuration
Web-based parameterisation using »WebConfig«
User interface

6.4 User interface

The user interface of the »WebConfig« is divided into the following areas  - :

 Note!
The representation of the user interface in the area  depends on the respective
system configuration! In the L-force Controller, one extension card can be used.

36 L 1.1 EN - 04/2011
 L-force Controller | Parameter setting & configuration
Web-based parameterisation using »WebConfig«
User interface

Area Information
Menu buttons  Standard device parameters of the L-force Controller ( 38)
• Parameter list 1: All parameters of the standard device
• Parameter list 2: All parameters of the installed extension cards
• PLC parameters
• Ethernet (on board) parameters
• EtherCAT parameters
 Diagnostics/Command execution ( 39)
• Logbook parameters
• Logbook of the L-force Controller
• Device commands
 User management ( 42)
• Setting users 1-10
 General parameters ( 42)
• Time
• UPS settings
• Monitoring functions
• Memory
• Identification
 Backup&Restore
• Parameters for carrying out »Backup & Restore«
• More information on the parameters can be found in the following section:
Backup&Restore ( 127)
• More information on how to carry out a backup, restore, or software updates can be
found in the »Backup & Restore« software manual
 Extension card parameters ( 43)

Note:
• The represented parameters of slots 1 and 2 depend on the corresponding extension
modules that are installed!
• The additional buttons for the actually installed extension cards are automatically
added to the menu buttons.
• The top-down order of the buttons corresponds to the order in which the extension
cards have been installed (slot 1, slot 2).
• The parameters of the communication cards are listed in numerically ascending
order in the following section: Extension cards ( 130)

 Polling ( 44)
 Language selection ( 44)
Buttons  Parameter list buttons ( 45)
Display area  Parameter display
Depending on the selected menu button, the parameters can be viewed in this area.
• Code numbers
• Name of the code
• Representation of the display, entry, selection, control and list fields.

According to the equipment of the L-force Controller, deviating components are shown by
use of the menu control fields.
Detailed information on the parameters can be found in the section Parameter reference
( 95)

1.1 EN - 04/2011 L 37
L-force Controller | Parameter setting & configuration
Web-based parameterisation using »WebConfig«
User interface

Representation of parameter values

In the display area of the web-based parameterisation, settings of device parameters are
represented with different background colours which have the following meaning:

Colour Example Meaning

Pale yellow Parameter (read only)
• Display of status information and actual values.

Yellow Parameter (read and write)

• The current parameter value of the device is displayed. Changes with regard to a
parameter have to be transmitted to the device with Accept or Accept & Save All.
Red Entry of a value beyond the valid range.
• Via Refresh the original value is shown again.
• A correct value can be entered in the red input field and transmitted to the device
with Accept or Accept & Save All .

In the following the individual menus of the web-based parameterisation »WebConfig«

are described.

6.4.1 Standard device parameters of the L-force Controller

Button Function
Displays all parameters of the standard device of the L-force Controller in
Parameter list 1 numerically ascending order.
• This user interface helps you to e.g.
– Find system properties and version numbers (read-only parameters),
– Set the system time,
– Activate the USB connection at the front of the monitor panel.
Parameters of standard devices ( 99)
The other menu buttons of areas , and  are a filtered view of parameter
list 1.
Displays all parameters of the installed extension cards in numerically
Parameter list 2 ascending order.
• The parameters of the extension cards are listed according to the order in
which they have been installed.
Extension card parameters ( 43)
The other menu buttons of area are a filtered view of parameter list 2.
Displays the PLC parameters in numerically ascending order.
PLC • This user interface shows you e.g.
– The PLC status,
– Information on a PLC project.
PLC (Logic/Motion) ( 38)
Displays the Ethernet (on board) parameters in numerically ascending order.
Ethernet • On this user interface the network settings of the on board
network connection are displayed/set.
Ethernet (on board) ( 120)
Shows the EtherCAT parameters.
EtherCAT • Information on EtherCAT master and EtherCAT slaves.
• The EtherCAT parameters are listed in the following section in
numerically ascending order:
EtherCAT ( 122)

38 L 1.1 EN - 04/2011
 L-force Controller | Parameter setting & configuration
Web-based parameterisation using »WebConfig«
User interface

6.4.2 Diagnostics/Command execution

Button Function
Displays parameters of the following areas:
Diagnostics • Diagnostics
• Logbook

In the Logbook area you can configure settings regarding the Logbook.

Further information on remote maintenance options

of the L-force Controller:
Remote maintenance and diagnostics ( 58)
Displays logbook contents.
Logbook • Different filter settings display, for instance, only the oldest or only the
most recent logbook entries.
Logbook ( 40)
Shows the executable commands of the L-force Controller. The available
Device commands commands can be found in the following section in code 18 (C0018)
Parameters of standard devices ( 99)

1.1 EN - 04/2011 L 39
L-force Controller | Parameter setting & configuration
Web-based parameterisation using »WebConfig«
User interface

6.4.3 Logbook

This user interface displays the logbook of the L-force Controller. The logbook provides
various filter options to show specific logbook contents.

 Note!
If the ClearLog button is clicked, the entire logbook contents of the L-force
Controller are deleted without further query!

6.4.3.1 Explanations on the logbook entries, example

Logbook entry, example Meaning

00001 Consecutive number of the entry
2009-03-24 14:45:26 Date(Format: Year-Month-Day)/Time on the L-force Controller
when the logbook entry was made
Log service Application that has triggered the entry (application)
Logbook cleared Description of the event
Continuous processing Event origin within the application (area)
Warning Severity of the event

40 L 1.1 EN - 04/2011
 L-force Controller | Parameter setting & configuration
Web-based parameterisation using »WebConfig«
User interface

6.4.3.2 Filter options

Section Information
Logbook Display logbook entries
Explanations on the logbook entries, example ( 40)
Time period Select filter for the time period of the logbook entries shown
• The logbook will only display entries which are in the selected time
period.
Application Set filter for the application
• The logbook will only display entries for the selected applications.
Severity Set filter for the severity of the error messages displayed
• The logbook will only display entries that correspond to the selected
degree of severity.
Area Set filter for the origin of the event
• The logbook will only display entries that correspond to the selected area.

6.4.3.3 Time filter for the display of logbook entries

Area Filter option Function

Time period 1: All Display all entries
2: From - to Filter entries according to date
specified
3: Last Display last entries only. Possible
filter options:
• 1: Days
• 2: Weeks
• 3: Months
• 4: Years
-from Time zone: Date (Format: Year/ Date specification for filtering the
Month/Day), Time (Format: Hours/ entries to be displayed
Minutes/Seconds) • Starting date from which the
entries are to be displayed
Example:
10th March 2009, 15.05 hours, 11
seconds: UTC 2009 03 10 15 05 11
-to Time zone: Date (Format: Year/ Date specification for filtering the
Month/Day), Time (Format: ) entries to be displayed
• Target date up to which the
entries are to be displayed
-last 1: Days Display entries according to filter
2: Weeks options.
3: Months • To activate this filter option, in the
4: Years Time period area of the selection
list the last item must be selected!

1.1 EN - 04/2011 L 41
L-force Controller | Parameter setting & configuration
Web-based parameterisation using »WebConfig«
User interface

6.4.4 Device commands

In this area, the available device commands of code 18 ( C0018) can be executed.
 Code 19 (C0019) displays status information regarding the executed
command.
More information on the supported device commands can be found in the following
section: Parameters of standard devices ( 99)

6.4.5 User management

This section sets up the Windows® CE users (users 1-10) and defines their access
authorisations.

Button Function
Set up Windows® CE user, enter user-specific data
User management • Enter user name and password, and the home directory.
• Enter access authorisation of the user.
Standard value for user 1: admin:admin

6.4.6 General parameters

Button Function
Displays the parameters for setting the time, date, system time, and time
Clock zone.
Displays the UPS settings for the parameterisation of optional
UPS settings UPS accessories.
Displays hardware/temperature data.
Monitoring functions
Displays information on program/Flash memories.
Memory
Displays information on system identification.
Identification

42 L 1.1 EN - 04/2011
 L-force Controller | Parameter setting & configuration
Web-based parameterisation using »WebConfig«
User interface

6.4.7 Extension card parameters

This area of the »WebConfig« displays the parameters of the expansion cards installed. The
following communication cards can be used:
 MC-CAN2,
 MC-PBM,
A distinction is drawn between:
– Interface parameters,
– Communication card parameters.
A communication card can be equipped with several physical bus interfaces, such as the
MC-CAN2 communication card.
CAN communication card (MC-CAN2) ( 131)
PROFIBUS master communication card (MC-PBM) ( 136)

1.1 EN - 04/2011 L 43
L-force Controller | Parameter setting & configuration
Web-based parameterisation using »WebConfig«
User interface

6.4.7.1 CAN communication card (MC-CAN2)

 Note!
The parameters can only be viewed if the corresponding communication card
MC-CAN2 is inserted. Two communication cards per Controller can be plugged
maximally!

Button Function
The MC-CAN2 button displays the parameter list of the MC-CAN2
MC-CAN2 communication card.
Parameters of the x interface of the
MC-CAN2 interface x MC-CAN2 communication card
• The MC-CAN2 Interface x button displays the parameters of the
respective interface (1 or 2) of a MC-CAN2 communication card.
• In addition, the button displays which card the respective interface
belongs to.
• The parameters of the communication card are listed in the following
section in numerically ascending
order:
CAN communication card (MC-CAN2) ( 131)

6.4.7.2 PROFIBUS master communication card (MC-PBM)

Button Function
Display the parameters of the PROFIBUS master card.
MC-PBM • This user interface displays the parameters of the MC-PBM
communication card.
• The parameters of the communication card are listed in the following
section in numerically ascending
order:
PROFIBUS master communication card (MC-PBM) ( 136)

6.4.8 Polling

In this menu the polling of the screen is activated.

Interval:
Setting the interval for the polling in seconds.
• Example value: 5.
Active:
Click the control field to activate the polling.

6.4.9 Language selection

 In the Language section you can define the desired language settings from the
selection list.
 The language settings take immediate effect, the »WebConfig« does not need to be
restarted.

44 L 1.1 EN - 04/2011
 L-force Controller | Parameter setting & configuration
Web-based parameterisation using »WebConfig«
User interface

6.4.10 Parameter list buttons

Button Function
Accept Accept data.
• After a system restart changed data are lost, as they are not persisted
automatically.
Accept & Save all Accept and save all changed data.
• The data will remain on your PC after a system restart.
Update Reload data and update screen display

1.1 EN - 04/2011 L 45
L-force Controller | Parameter setting & Configuration
Programming with the »PLC Designer«
Basics

7 Programming with the »PLC Designer«

This chapter provides you with information on the programming of the control function of
the L-force Controller.

 Further information on working with the »PLC Designer« can be found in the
documentation for the »PLC Designer«.

7.1 Basics

The »PLC Designer« is the PLC programming system to be installed on the Engineering PC.
The »PLC Designer« is one of the Lenze Engineering tools. The »PLC Designer« accesses the
L-force Controller via Ethernet:

The »PLC Designer« serves to create PLC programs in the programming languages of IEC
61131. The IEC 61131 programming languages are:
 Instruction list (IL),
 Ladder diagram (LD),
 Function plan (FP),
 Structured text (ST),
 Sequential function chart (SFC),
 Function block diagram

46 L 1.1 EN - 04/2011
 L-force Controller | Parameter setting & Configuration
Programming with the »PLC Designer«
Configuration and parameterisation via the control application

The completely created and compiled program is transferred to the L-force Controller with
the »PLC Designer«. On the L-force Controller, the program can be executed by the L-force
Logic & Motion runtime software.

Technical data of the L-force Controller

Intended use Value

Memory for retain and persistent 60 kB
data
Program memory/data memory 512 MB
Flag 4 kB
Maximum number of tasks 32
Shortest task time 1 ms

7.2 Configuration and parameterisation via the control application

For creating the control application diverse function blocks, like for example standardised
libraries with motion functions according to PLCopen, are provided.
Furthermore there are function blocks that are suitable for the access to parameters of the
L-force Controller.
The translated PLC program is loaded into the L-force Controller via the network by means
of the »PLC Designer«. There it can be processed by the operating software of the L-force
Controller.

 Further information on working with the »PLC Designer« can be found in the
documentation for the »PLC Designer«.

1.1 EN - 04/2011 L 47
L-force Controller | Parameter setting & Configuration
Programming with the »PLC Designer«
Accessing L-force Controller parameters from the PLC

7.3 Accessing L-force Controller parameters from the PLC

For the parameter access to parameters of the L-force Controller from the PLC an interface
to the PLC is provided by means of the PLCDataManagerAccess library.

7.3.1 The LDM_ParameterAccess_FB function block

Function library: PLCDataManagerAccess

With the LDM_ParameterAcces_FB function block the device parameters of the L-force
Controller can be read and written by the PLC.

Inputs

Identifier/data type Information/possible settings

bExecute Rising edge starts the access
BOOL
eDirection Access direction
LDM_tDIR • LDM_READ - read
• LDM_WRITE - write
sTopoAddr Topology address
STRING(255) '/' - access to parameters of the L-force Controller
wCode Code of the parameter (Lenze)
WORD Then wIndex has to be set to 0
wIndex Index of the parameter (CANopen)
WORD Then wCode has to be set to 0
bySubIndex Subindex/subcode of the parameter
Byte
eDataType Specification of the type of the parameter to be written
LDM_tVT Example: LDM_VT_I2 : 2 bytes integer
Example: LDM_VT_I4 : 4 bytes integer
sDataW Value to be written (string) - table [7-1]
STRING(255)

byDataW Value to be written (1*byte) - table [7-1]

Byte

48 L 1.1 EN - 04/2011
 L-force Controller | Parameter setting & Configuration
Programming with the »PLC Designer«
Accessing L-force Controller parameters from the PLC

Identifier/data type Information/possible settings

wDataW Value to be written (2*byte) - table [7-1]
WORD

dwDataW Value to be written (4*byte) - table [7-1]

WORD

Outputs

Identifier/data type Value/meaning

bDone TRUE if operation has been completed successfully
BOOL
bBusy TRUE as long as the operation is running without errors
BOOL
bError TRUE if an error has occurred
BOOL
dwErrorID Greater 0 if an error has occurred
DWORD
eDataRType Returned type of the parameter read
LDM_tVT {LDM_VT_EMPTY, LDM_VT_I4, ...}
sDataR Value read (string) - table [7-1]
STRING(255)
byDataR Value read (1*byte) - table [7-1]
Byte
wDataR Value read (2*byte) - table [7-1]
WORD
dwDataR Value read (4*byte) - table [7-1]
DWORD

Input, output Data type

sDataR, sDataW LDM_VT_BSTR
byDataR, byDataW LDM_VT_I1, LDM_VT_UI1
wDataR, wDataW LDM_VT_I2, LDM_VT_UI2
dwDataR, dwDataW LDM_VT_I4, LDM_VT_UI4, LDM_VT_DATE

[7-1] Connection between the inputs and outputs and the data type

1.1 EN - 04/2011 L 49
L-force Controller | Parameter setting & Configuration
Programming with the »PLC Designer«
Accessing L-force Controller parameters from the PLC

7.3.2 The LLS_AddLog function block - Generate logbook entry

Function library: PLCLoggingAccess

This function renders it possible to make an entry in the logbook of the L-force Controller.
 The function supplies a return value TRUE if the entry was carried out.

LLS_AddLog:BOOL
eSeverity
eFacility
sLogPayLoad

Inputs

Identifier/data type Information/possible settings

eSeverity Logging Severity - risk of the error
T_LLS_Severity • LLS_FatalError
• LLS_Error, LLS_Warning
• LLS_Information
The Enum parameter eSeverity (IEC_INT) transferred to Add2Log as severity (BYTE).
eFacility Logging Facility: - area from which the error is reported
T_LLS_Facility • LLS_PLC_USER_LOG_SCOPE1
• LLS_PLC_USER_LOG_SCOPE2
• LLS_PLC_USER_LOG_SCOPE3
The Enum parameter eFacility (IEC_INT) is transferred to Add2Log as Facility
(WORD).
sLogPayLoad Logbook entry
STRING(80) The Ansi string from "sLogPayLoad" is transferred to Add2Log as 1-byte string
parameter. ("hs", SLOGPAYLOAD)

50 L 1.1 EN - 04/2011
 L-force Controller | Parameter setting & configuration
Backup&Restore

8 Backup&Restore
»Backup & Restore« allows you to ...
 create backups: back up databases.
 restore backups: restore databases
 install updates (only available for control technology): update the software version of
the L-force Controller

 Further information on the use of »Backup & Restore« can be found in the
following documentation:
• Software manual - »Backup & Restore«

1.1 EN - 04/2011 L 51
L-force Controller | Parameter setting & Configuration
Data integrity in the case of a voltage failure
Retain variables of the PLC

9 Data integrity in the case of a voltage failure

If a voltage failure occurs, important volatile data must not be lost. Therefore the
possibility of saving these data on the SD card is provided. You can also save the data via a
PLC function. Persisting the PLC's retain variables ( 53)
Here you will learn
 what Retain variables of the PLC are,
 how the Backup with UPS functions and

9.1 Retain variables of the PLC

Retain variables are variables of the PLC which will be saved if a voltage failure occurs.

 Tip!
You can create retain variables in the »PLC Designer« by marking the variables with
the keyword RETAIN.

Variables that are important for the resumption of the production process, and the actual
value of which cannot be read out of the machine because no sensors are available, should
be persistent. This makes only sense if the values only changes when being influenced by
the PLC.

Examples
Temperature: alters, requires sensors
Position: preferably via absolute encoders
Number of parts within buffer inventory: reasonable for RETAIN.
VAR RETAIN
remvar1:INT; (* 1st remanent variable*)
END_VAR

 Note!
For saving variables of the RETAIN and PERSISTENT types, a memory area of 60
kB is provided.

52 L 1.1 EN - 04/2011
 L-force Controller | Parameter setting & Configuration
Data integrity in the case of a voltage failure
Backup with UPS

9.2 Backup with UPS

The L-force Controller 3200 allows short-time data buffering by means of a UPS. In the case
of a voltage failure, the most important data will be backed up. During the backup, the
following data will be stored in an internal memory:
 Retain variables and persistent variables of the PLC
 Logbook entries (log files)
When the data is saved, the PLC is stopped. The log service does not accept any further log
messages and deactivates itself.

9.2.1 Persisting the PLC's retain variables

The PLC offers the SysSaveRetains function by means of which all retain variables can be
saved from the PLC program. Furthermore you can define cycles for saving the retain
variables.

 Tip!
Detailed information on this function can be found in the »PLC Designer« manual.

 Note!
SD cards only have a limited number of write/read cycles. It is therefore not
useful to save the retain variables at very short time intervals.

9.2.2 Persisting changed parameters

You can persist the parameterisation of the L-force Controller manually using the web-
based parameterisation.

Web-based parameterisation
 In the web-based parameterisation, click the Device commands. button.
 Select the entry "279: Persist all data" from Commands list field.

1.1 EN - 04/2011 L 53
L-force Controller | Parameter setting & Configuration
Data integrity in the case of a voltage failure
Backup with UPS

 Click the Accept button.

– OK appears in the "Status" field.

9.2.3 Persisting log files

The log files are persisted automatically at certain events. Logbook function ( 69)

However, you can also persist the log files manually using the »Engineer« and the web-
based parameterisation.

Web-based parameterisation
 In the web-based parameterisation, click the Device commands. button.
 Select the entry "1282: Persist logbook" from the Commands list field.
 Click the Accept button.
– OK appears in the "Status" field.

54 L 1.1 EN - 04/2011
 L-force Controller | Parameter setting & Configuration
Replacing the L-force Controller
Removing the L-force Controller

10 Replacing the L-force Controller

Precondition
Only L-force Controllers of the same product type can be exchanged against each other.

[10-1] L-force Controller of the 3221 C series with communication card MC-CAN2

10.1 Removing the L-force Controller

 Danger!
Electrical voltage! Deenergise the L-force Controller before removing a
connected L-force Controller.

 How to remove the connected L-force Controller:

1. Disconnect the system from the supply and check for correct disconnection.
2. Disconnect current supply from the L-force Controller.
3. Remove first I/O module next to the L-force Controller to disconnect the I/O
modules.
4. If I/O modules (I/O system 1000) are connected to the L-force Controller:
• Remove electronic module of the first I/O system 1000 (if available) so that the
L-force Controller can be separately removed.
5. Remove bus connections and other connections.
6. Remove SD card from the card slot.

1.1 EN - 04/2011 L 55
L-force Controller | Parameter setting & Configuration
Replacing the L-force Controller
Connecting a new L-force Controller

10.2 Connecting a new L-force Controller

 Note!
The SD card contains the user data.
If an L-force Controller of the same product type has been used, the L-force
Controller is ready for operation after boot-up.
• The previous network settings are accepted. Alternatively they can be edited.
– After 15 seconds, the previous IP address is transferred automatically and
the L-force Controller can be accessed again.

 Note!
When connecting a new L-force Controller...
• all cards are to be kept in the same slot,
• all connections are to be selected identically.

 How to install and connect a new L-force Controller:

1. Use a new L-force Controller of the same product type.
2. Insert the SD card of the removed L-force Controller into the new one.
3. Connect bus connections and other connections.
4. Connect current supply of the L-force Controller.
• Plug in electronic module of the system 1000 (if available)
5. Switch on the voltage supply.
• New L-force Controller starts.

10.3 Subsequent use of retain data on the new controller

 Note!
• If the L-force Controller is replaced, the retain data are not available on the
new device without implementing additional measures.
– In the case of a voltage failure, the retain data of the PLC are stored in the
internal RAM of the L-force Controller (not on the SD card).

56 L 1.1 EN - 04/2011
 L-force Controller | Parameter setting & Configuration
Replacing the L-force Controller
Subsequent use of retain data on the new controller

 How to proceed:
1. In order to be able to further use the retain data after a device replacement, ...
• ... the desired data are to be saved to the SD card from the application.
• ... the desired data are to be restored from the application.

Functions for saving/restoring retain data

 Note!
The functions SysSaveRetains() and SysRestoreRetains() provided in the
SysPlcCtrl23.Library are not supported and must not be used!

Function Library Function

AppStoreRetainsInFile() CmpApp.Library Save retain data to the SD card
AppRestoreRetainsFromFile() CmpApp.Library Restore retain data from the SD card

PROGRAM ManualRetains
VAR
xStoreManualRetains: BOOL;
stMyRetainFile : STRING := 'myRetains';
xRestoreManualRetains: BOOL;
pMyApp: POINTER TO application;
pResult: POINTER TO rts_IEC_result;
END_VAR

IF pMyApp = 0 THEN
pMyApp := AppGetFirstApp(ADR(pResult));
END_IF

IF xStoreManualRetains THEN
pResult := AppStoreRetainsInFile(pMyApp, stMyRetainFile);
xStoreManualRetains := FALSE;
END_IF

IF xRestoreManualRetains THEN
pResult := AppRestoreRetainsFromFile(pMyApp, stMyRetainFile);
xRestoreManualRetains := FALSE;
END_IF
[10-2] Program example regarding the use of the functions AppStoreRetainsInFile() and AppRestoreRetainsFromFile()

1.1 EN - 04/2011 L 57
L-force Controller | Parameter setting & configuration
Remote maintenance and diagnostics

11 Remote maintenance and diagnostics

This chapter contains information on remote maintenance and diagnostics of the L-force
Controller. The L-force Controller provides different diagnostics options:
telnet connection ( 59)

FTP connection ( 61)

Windows® CE functions ( 65)

Logbook function ( 69)

 Tip!
The configuration of the individual diagnostics options can be carried out via the
web-based parameterisation and the »Engineer«. The chapters will provide you
with details on how the settings can be carried out.

58 L 1.1 EN - 04/2011
 L-force Controller | Parameter setting & configuration
Remote maintenance and diagnostics
telnet connection

11.1 telnet connection

The term "telnet" refers to a method used for the connection with a host. In this way it is
possible to operate a connected remote computer via the command line interface.

11.1.1 Settings of the web-based parameterisation

The telnet settings can be configured via codes 180 to 181 via the Remote maintenance
button of the web-based parameterisation.
 Code 180 activates authentication of the telnet user,
 Code 181 activates the telnet access to the L-force Controller,

 Note!
The corresponding Windows® CE user must have a telnet authorisation.
Setting up Windows® CE users in the »WebConfig« ( 21)

1.1 EN - 04/2011 L 59
L-force Controller | Parameter setting & configuration
Remote maintenance and diagnostics
telnet connection

 How to establish a telnet connection to the L-force controller:

1. Start the command line on the PC by means of which you want to log in,
2. Start buttonExecute,
3. Establish the telnet connection to the L-force Controller: Start telnet <IP address>
of the L-force Controller.
4. The user name and password for the authentication must correspond to the data
stored in the user management, codes 101 to 170.

 Note!
Access via telnet must only be used for diagnostic purposes. Changing system
data may result in L-force Controller faults.

 Standard access data:

– login: admin
– Password: admin

60 L 1.1 EN - 04/2011
 L-force Controller | Parameter setting & configuration
Remote maintenance and diagnostics
FTP connection

11.2 FTP connection

The File Transfer Protocol (FTP) is a network protocol for the transfer of data in networks.
FTP enables the exchange of files between the L-force Controller and other PCs. Via the FTP
connection the user can access the files of the Compact Flash card of the L-force Controller.

 Note!
FTP must be used for system-diagnostic purposes only. Deleting or changing
system files causes malfunctions of the L-force Controller!

11.2.1 FTP settings with the »WebConfig«

The settings of the FTP connection can be managed via the web-based parameterisation.
From codes 171 to 174 the FTP access for the L-force Controller can be activated and user
rights can be specified. Click the Remote control button to call the FTP settings:

 Code 171 activates authentication of the FTP user,

 Code 172 enables log-on of the anonymous FTP user "Anonymous",
 Code 173 activates the upload of files by anonymous FTP users,
 Code 174 activates the FTP service.
The user management, the User management button, specifies the following:
– The Windows® CE users who are allowed to use the FTP access.
– Which authorisations the Windows® CE users have.

The authorisations are required to be able to connect to the L-force Controller via FTP.

 Note!
For accepting the FTP settings, the FTP server has to be restarted:
Click the Device commands button.
• Send the "Stop FTP server" command. The FTP server is stopped.
• Send the "Start FTP server" command. The FTP server is started with the
changed settings.
• Send the "Update FTP server" command to update information to the FTP
server.

1.1 EN - 04/2011 L 61
L-force Controller | Parameter setting & configuration
Remote maintenance and diagnostics
FTP connection

11.2.2 FTP and web settings in the Internet Explorer

 Note!
• You must change your browser settings to be able to establish an FTP / web
connection to the L-force Controller.
• Your firewall settings may be blocking your access via FTP and HTTP. Change
your firewall settings or deactivate your firewall.
• You need administrator rights to be able to change your firewall settings.

 Open browser settings via ToolsInternet OptionsAdvanced,

 Activate folder view for FTP and passive FTP,

 Open the settings for the local area network via ToolsInternet
optionsConnectionsSettings,
 Switch off the proxy server or remove the L-force Controller from the proxy settings.

62 L 1.1 EN - 04/2011
 L-force Controller | Parameter setting & configuration
Remote maintenance and diagnostics
FTP connection

 Note!
The settings for the local area network and the proxy settings depend on your
own network settings on site.

 How to start an FTP connection to the L-force Controller:

1. Select the file transfer protocol in the input line of the web browser or in the
command line via StartExecute...:
2. Enter:
• FTP://<Username>:<password>@<IP address>.
The standard setting is FTP://admin:admin@<IP address>. Alternatively the IP
address can be entered directly: FTP://<IP address>
• In the following input window, the user name and password have to be entered.

1.1 EN - 04/2011 L 63
L-force Controller | Parameter setting & configuration
Remote maintenance and diagnostics
FTP connection

3. When the entry is correct, click the Log in button.

• The L-force Controller can now be accessed by the Engineering PC.

64 L 1.1 EN - 04/2011
 L-force Controller | Parameter setting & configuration
Remote maintenance and diagnostics
Windows® CE functions

11.3 Windows® CE functions

 During normal operation the Windows® CE functions are hidden on the L-force
Controller. All L-force Controller functions can be controlled via the Engineering PC.
 For diagnostic purposes and maintenance activities you can use the standard functions
of the L-force Controller operating system Windows® CE.
 You can access the Windows® CE functions
– via the service mode if the L-force Controller is operated directly,
– Via a telnet connection with the corresponding administrator rights,

 How to activate the user interface of Windows® CE on the L-force Controller:

1. Activate the service mode by keeping the <Shift> key pressed. There are two
possibilities of activating the service mode:
• <Shift>+<F4> starts the Control panel. The entry can be made via the on-screen
keyboard or via an optionally connected keyboard.
• When the green LED is blinking, you can start the Control panel with the
function key F1 on the monitor panel.
2. Start the Service command by double-click.
3. Activate the task bar by entering explorer in the command line box.

• The task bar facilitates the navigation by providing the basic functions of
Windows® CE:

 Note!
In order to be able to use a telnet connection, you have to provide a telnet
authorisation to the corresponding Windows® CE user.

 How to activate the user interface of Windows® CE via telnet:

1. Log in on the L-force Controller which requires a diagnostics via telnet connection.
• The standard settings of the Windows CE User 1 are: User name: admin,
password

1.1 EN - 04/2011 L 65
L-force Controller | Parameter setting & configuration
Remote maintenance and diagnostics
Windows® CE functions

• explorer activates the Windows® CE interface on the

66 L 1.1 EN - 04/2011
 L-force Controller | Parameter setting & configuration
Remote maintenance and diagnostics
Windows® CE functions

11.3.1 Remote Display - remote control of L-force Controller via Internet or LAN

Remote Display C
 The Engineering PC requires the Remote Display Control software (cerhost.exe) which
can be downloaded from the AKB on the Lenze homepage. It is also provided on the CD
that is delivered along with the devices.

 How to establish a Remote Display connection to the L-force controller:

1. Find out the IP address of the Engineering PC (e.g. by executing the IPConfig
command),
2. Start Remote Display Control (cerhost.exe) on the Engineering PC,
3. Start cerdisp.exe on the L-force Controller with the (previously identified) IP
address of the Engineering PC : cerdisp <IP address>

[11-1] Remote access to an L-force Controller via Remote Display Control

Virtual Network Computing (VNC)

For the Engineering PC, you need the "Virtual Network Computing" (VNC) software.
 VNC is preinstalled on the L-force Controller. (\USBStorage\windows\VNC.exe)
 VNC allows you to operate the L-force Controller by remote control from the
Engineering PC. In this way, you will work on a remote PC as if you were sitting directly
in front of the L-force Controller.
Precondition
 The L-force Controller is switched on and connected to the network/Internet.

1.1 EN - 04/2011 L 67
L-force Controller | Parameter setting & configuration
Remote maintenance and diagnostics
Windows® CE functions

 The VNC client is started on the L-force Controller.

 A VNC client (e.g. VNCviewer) is installed on the Engineering PC.

 Note!
The VNC server is not protected by a password. To protect data from
unauthorised access, the server should be deactivated whenever the connection
is not needed.

 How to establish a Remote Display connection to the L-force controller:

1. Start VNC server on the L-force Controller
• In the »WebConfig«, set the "Activate VNC server" parameter ; (CS 95), or
• Execute the \USBStorage\windows\VNC.exe file
2. Start VNC client on the Engineering PC.
3. Enter the IP address of the L-force Controller
Tip: To display the IP address of the L-force Controller, go to the Control Panel
(StartSettingsControl Panel) of the L-force Controller and select "Network
Connections".

[11-2] Remote access to an L-force Controller via VNC (example: VNCviewer)

68 L 1.1 EN - 04/2011
 L-force Controller | Parameter setting & configuration
Remote maintenance and diagnostics
Logbook function

11.4 Logbook function

The L-force Controller has a logbook function which records system events and error
messages. The logbook entries are meant to facilitate the system diagnostics in the event
of faults.
The logbook function
 displays the recorded error messages and events of the L-force Controller applications,
 automatically stores the information on the SD card.

Structure of a logbook entry

Each logbook entry contains the following information:
 Ascending numbering,
 Date / time,
 Application causing the logbook entry,
 Severity of the event in four categories
– Information,
– Warning,
– Error,
– Fatal error.
 Area as the event origin of the triggered error message.

The logbook of the L-force Controller can be called via »WebConfig« and »Engineer«:
Logbook query via »WebConfig« ( 70)

1.1 EN - 04/2011 L 69
L-force Controller | Parameter setting & configuration
Remote maintenance and diagnostics
Logbook function

11.4.1 Logbook query via »WebConfig«

The logbook entries can be queried via »WebConfig«.

 The browser of the Engineering PC accesses the web server of the L-force Controller via
Ethernet connection (http://).
 The data manager of the L-force Controller provides for access to logbook contents.

 How to call the logbook in the »WebConfig«:

1. Start your browser on the Engineering PC,
2. Enter the IP address of the L-force Controller: http://<IP address>,
3. Enter your user name and password,
4. Click the logbook button.

 The logbook of the L-force Controller can be displayed via the Logbook button in the
»WebConfig«.

 Note!
The ClearLog command deletes all logbook entries on your L-force Controller
without further query!

70 L 1.1 EN - 04/2011
 L-force Controller | Parameter setting & configuration
Remote maintenance and diagnostics
Logbook function

 Tip!
The display of the logbook entries can be filtered according to the period,
application, severity, and area.

Further information on the use of the logbook function in the »WebConfig« can be found
in the following section: Logbook ( 40)

11.4.1.1 Logbook codes

The logbook settings can be called in the »WebConfig« via the Diagnostics tab.
Further information on the parameters of the logbook C0048) can be found in the
following section: Parameters of standard devices ( 99)

1.1 EN - 04/2011 L 71
L-force Controller | Parameter setting & configuration
Visualisation with »VisiWinNET®«
Introduction to »VisiWinNET®«

12 Visualisation with »VisiWinNET®«

This chapter provides information on the »VisiWinNET®« software. In addition to basic
information, you will get an overview of the use of »VisiWinNET®« in connection with the
Lenze control technology.

 Further information on the operation of »VisiWinNET®« can be found in the

software documentation for »VisiWinNET®«.

12.1 Introduction to »VisiWinNET®«

»VisiWinNET®« is a visualisation platform for mechanical and systems engineering.

 It can be used to create complex visualisation applications, the possibilities range from
classical operate and monitor functions through to sophisticated SCADA systems.
»VisiWinNET®« consists of a development component and a runtime component.
 The developer software is used to create visualisation applications on the Engineering
PC which are run using the runtime component on the L-force Controller.
 In order to transfer the visualisation applications created by means of the Engineering
PC to the L-force Controller, the »VisiWinNET®« Remote Access Manager software is
used. TCP/IP is used as a transmission standard.
• Activate the "Activate VisiWinNET remote access ;" parameter (CS 97) in the
»WebConfig« to start the Remote Access Manager.

Licensing
If required, the L-force Controller is provided with a corresponding licence for the use with
»VisiWinNET®« by the factory. The licence that is available for the respective controller can
be identified by means of the »WebConfig«: IdentificationLicence

12.1.1 »VisiWinNET®« Compact

»VisiWinNET®« Compact is a runtime version of »VisiWinNET®« especially designed for use

on computer systems. »VisiWinNET®« Compact requires very little memory capacity and
processor power. A version for the Windows® CE operating system and a version for
Windows® XP Embedded is available. Detailed information on the installation and use of
»VisiWinNET®« COMPACT can be found in the manufacturer's original documentation.

12.2 Basic functions

 Further information on the use of »VisiWinNET®« can be found in the online

documentation of »VisiWinNET®«.

72 L 1.1 EN - 04/2011
 L-force Controller | Parameter setting & configuration
Visualisation with »VisiWinNET®«
Basic functions

12.2.1 Start the »VisiWinNET®« development system

12.2.1.1 »VisiWinNET®« Smart

 Select the following entry in the Microsoft Windows® start menu to start the
integrated development environment »VisiWinNET®« Smart:
ProgramsLenzeVisiWinNet 2005VisiWinNET Smart

12.2.1.2 »VisiWinNET®« Professional

 Select the following entry in the Microsoft Windows® start menu to start the
integrated development environment »VisiWinNET®« Professional:
ProgramsLenzeVisiWinNet 2005VisiWinNET Professional

12.2.2 Creating a new project

12.2.2.1 Creating a new project in »VisiWinNET®« Smart

 How to create a new project:

1. Select the entry FileNew project... in the menu bar.
2. Select the Configure target device from catalog option.
3. Click the Next button.
• A tree view with all relevant Lenze target devices appears. With a click on a
target device a picture and a description of the device appear.

4. Search for the target device used.

5. Select the operating system used on the target device.
6. Click the Next button.
7. Enter a project name in the Project name text field.

1.1 EN - 04/2011 L 73
L-force Controller | Parameter setting & configuration
Visualisation with »VisiWinNET®«
Basic functions

8. Click the OK button.

12.2.2.2 Creating a new project in »VisiWinNET®« Professional

In »VisiWinNET®« Professional there is no device catalogue. The creation of a new project
is described in the documentation for »VisiWinNET®« Professional.

74 L 1.1 EN - 04/2011
 L-force Controller | Parameter setting & configuration
Visualisation with »VisiWinNET®«
Basic functions

12.2.3 Open the Project Explorer

An important tool for working with »VisiWinNET®« is the Project Explorer. It is a

component of the integrated development environment and enables central access to
important data.

 Select View Project Explorer in the menu bar to open the Project Explorer.

1.1 EN - 04/2011 L 75
L-force Controller | Parameter setting & configuration
Visualisation with »VisiWinNET®«
Constellation and connection

12.3 Constellation and connection

»VisiWinNET®« accesses the fieldbus driver (CAN and EtherCAT) of the L-force Controller
via an OPC tunnel.
Depending on the constellation, the servers are either connected to »VisiWinNET®« locally
or via another computer (remote). A remote connection for instance is reasonable if an L-
force Controller is only responsible for the visualisation and accesses the process data of
another L-force Controller.

 Note!
• There are no OPC tunnels available for PROFIBUS.

The following data can be accessed:

 Access to the data of the Data manager (e. g. logbook data),
 Access to the data of the nodes on the fieldbus (e.g. CAN),
 Access to PLC variables.
During all accesses the OPC server is connected to the
»VisiWinNET®« project via the OPC tunnel.
The following sections provide information on how...
...Using the LogicandMotionV3 direct driver ( 77)
... Inserting the OPC tunnel in »VisiWinNET®« ( 80),
... to access variables: The Lenze Variables Browser ( 81)

76 L 1.1 EN - 04/2011
 L-force Controller | Parameter setting & configuration
Visualisation with »VisiWinNET®«
Constellation and connection

... Linking control elements and variables ( 85)

... Open the Project Explorer
( 75)

12.3.1 Using the LogicandMotionV3 direct driver

12.3.1.1 Using direct drivers for visualisations under Windows CE

Use of the LogicAndMotionV3 direct driver under »VisiWinNET® Smart«.

 How to use the direct driver:

1. Create a new project with the L-force Controller 3231C target device and a
connected display:

2. Add the LogicAndMotionV3 direct driver as communication channel:

1.1 EN - 04/2011 L 77
L-force Controller | Parameter setting & configuration
Visualisation with »VisiWinNET®«
Constellation and connection

3. Configure the communication channel added:

Further information on the configuration of the communication channel can be

found in the »VisiWinNET®« online help. Click the Help button to call the online
help.
Note: The PLC address can be found in the »PLC Designer« in the device context
menu: DeviceCommunication settingsIPC: Node address
4. After the project configuration has been completed, a new LogicAndMotionV3
channel is available in the Project Explorer:

78 L 1.1 EN - 04/2011
 L-force Controller | Parameter setting & configuration
Visualisation with »VisiWinNET®«
Constellation and connection

5. In the context menu of the LogicAndMotionV3 channel, select the Browse

variables command to add variables of the PLC:

12.3.1.2 Using direct drivers for visualisations under Windows XP

Use of the direct driver for LogicAndMotionV3.x under »VisiWinNET® Smart«.

 How to use the direct driver:

1. Create a new project with the L-force Controller 3241C target device and a
connected display:

2. The further procedure is identical with steps 2 to 5 of the LogicAndMotionV3 direct

driver under Windows CE: Using direct drivers for visualisations under Windows
CE ( 77)

1.1 EN - 04/2011 L 79
L-force Controller | Parameter setting & configuration
Visualisation with »VisiWinNET®«
Constellation and connection

12.3.2 Inserting the OPC tunnel in »VisiWinNET®«

The OPC tunnel is the communication channel between »VisiWinNET®« and the
OPC servers of the L-force Controller. You have to integrate the OPC tunnel into your
project once.

 How to integrate the OPC server into your project:

1. Open the Project Explorer.
2. Select the entry New in the context menu of the node VariablesChannels.
• The Add channel dialog box appears.
3. Enter Lenze.Digitec.OPCTunnel.DA in the OPC Server/Driver text field.

4. Enter a name in the Name text field.

5. Click the Browser button.
6. Select the VisiWinNET.LenzeVariables.Brw.dll entry from the selection list.

7. Click the OK button.

• The OPC tunnel can be selected in the Project Explorer.

80 L 1.1 EN - 04/2011
 L-force Controller | Parameter setting & configuration
Visualisation with »VisiWinNET®«
Constellation and connection

12.3.3 The Lenze Variables Browser

The variables browser can be used to browse for variables on the devices connected to the
L-force Controller and to transfer them to a »VisiWinNET®« project. For this purpose, a
connection between the integrated »VisiWinNET®« development environment and the L-
force Controller is not required. The data is read from the locally available parameter files,
which have been exported from the »Engineer« in advance.

 How to call up the Variables Browser:

1. Open the Project Explorer (Open the Project Explorer).
2. Open the Variables ->Channels branch in the Project Explorer.
3. Select Browse variables in the context menu of the intended communication
channel.

• The Lenze Variables Browser window appears. In the Devices selection list all
devices available for reading variable definitions appear.

12.3.3.1 Browsing for variable definitions

When you have started the Lenze Variables Browser, you can select one or more devices
and then read their variable definitions.

1.1 EN - 04/2011 L 81
L-force Controller | Parameter setting & configuration
Visualisation with »VisiWinNET®«
Constellation and connection

 How to browse for variable definitions:

1. Click the Add button.
• The Configure device dialog appears.

2. Select the required communication type from the Communication type drop-down
menu:
»VisiWinNET®« and the control system are on the same Engineering PC:
• Data manager OPC Tunnel: Access to data of the Data manager
(e. g. logbook data),
• CAN OPC Tunnel: Access to data of a node on the CAN bus,
• SoftPLC OPC Tunnel: Access to variables of the PLC.

»VisiWinNET®« and the control system are on different Engineering PCs:

• Remote Data manager OPC Tunnel: Access to data of the Data manager
(e. g. logbook data),
• Remote CAN OPC Tunnel: Access to data of a node on the CAN bus,
• Remote SoftPLC OPC Tunnel: Access to variables of the PLC.
The non-tunnel servers are not relevant for the configuration.
3. Enter the name of the parameter file in the Parameter file text field. The file
extension depends on the device selected:
• OPC server of the PLC: .sym
• OPC-CAN bus server and OPC-DM server: .eds and .dSD
• Click the ... button to search for a parameter file on a data medium.
• If the CAN OPC tunnel is used, the CAN address and the CAN interface must be
specified.
4. Enter a name in the Device alias text field. This device alias is a designation for the
device used internally in »VisiWinNET®«.
5. Click the OK button.

82 L 1.1 EN - 04/2011
 L-force Controller | Parameter setting & configuration
Visualisation with »VisiWinNET®«
Constellation and connection

12.3.3.2 Accept variable definitions to project

You can transfer one or more "browsed" variable definitions to your »VisiWinNET®«
project.

 How to transfer the variable definitions to the project:

1. Highlight the desired device in the Devices selection list of the Lenze variables
browser.
2. Click the OK button.
• A tree view of the read variable definitions appears.

3. Select the variable definitions required.

4. Click the OK button.
• The variable definitions are transferred to the project database.

1.1 EN - 04/2011 L 83
L-force Controller | Parameter setting & configuration
Visualisation with »VisiWinNET®«
Constellation and connection

12.3.4 Entering variables manually

Variables can also be entered manually, as an alternative to using the Lenze Variables
Browser. Depending on the server and the connection type (local or remote), you have to
observe a special syntax. This syntax is described on the following pages.

 How to enter a variable manually:

1. Open the Project Explorer.
2. Activate the variable editor by double-clicking on the desired channel in the node
VariablesChannels.
3. Select the New item from the context menu.
4. Enter the variable name in the ItemID/address input field.
• In doing this, observe the corresponding syntax!

12.3.4.1 Access to PLC variables

Access to... How to proceed...

OPC tunnel (SoftPLC) 1. Prefix the variable with <PLC.PLC1:> .
2. Specify the variable in the form
<Application>.<CoDeSys block>.<Symbol name>.
• Example: PLC.PLC1.Application.PLC_Prg.My_variable

Data 1. Prefix the variable with DM.

2. Specify the variable in the form
.pari<24575 minus code>d<data type>.
3. Example: DM.pari24572d8
4. If an additional reference to a subindex is provided, supplement the
following entry:
• Example with subindex "S1": pari24572s1d3

CAN (OPC tunnel) - local access • Prefix the variable with CAN. Specify the variable in the following form:
.can<Can port>.dev<CAN device address>.pari<24575 minus
code>d<data type>
– Example: CAN.can1.dev40.pari24572d8

OPC tunnel - remote access 1. Precede the variables with the Remote Controller ID (RemoteIPC) and
the prefix PLC.PLC:,
2. Specify the variable in the form <CoDeSys block>.<CoDeSys
variable>.
• Example: RemoteIPC.PLC.PLC:.EPMAP

Data manager - remote access 1. Precede the variables with the Remote L-force Controller RemoteIPC ID
and the prefix DM .
2. Specify the variable in the form .pari<24575 minus code>d<data
type>.
• Example: RemoteIPC.DM.pari24572d8

84 L 1.1 EN - 04/2011
 L-force Controller | Parameter setting & configuration
Visualisation with »VisiWinNET®«
Constellation and connection

Access to... How to proceed...

CAN (OPC tunnel) - remote access 1. Precede the variables with the Remote L-force Controller RemoteIPC ID
and the prefix CAN.
2. Specify the variable in the form.can<Can port>.dev<CAN address
device>.pari<24575 minus code>d<data type>.
• Example: RemoteIPC.CAN.can1.dev40.pari24572d8

12.3.5 Linking control elements and variables

A user interface created with »VisiWinNET®« consists of different control elements such as
buttons, check boxes and option fields. An important function of »VisiWinNET®« is to link
these control elements with the variables available on the target device.

 How to link control elements with variables:

1. Select the control element.
2. Click the ... button of the VWItem property.

3. Select the intended variable from the tree view.

4. Click the OK button.
• The selected variable is assigned to the control element.

12.3.6 Transferring an application to the target device

 Note!
In order to be able to transfer an application to the target device, you have to
start the
»VisiWinNET®« Remote Access Manager.
• For this, activate the ""Activate VisiWinNET Remote Access ;" parameter (CS
97) in the »WebConfig«.

 Alternatively you can start the »VisiWinNET®« Remote Access Manager via the
user interface of the L-force Controller:
1. Change to the service mode.
2. Press F1 on the monitor panel.
• The control panel is started.
• Here the »VisiWinNET®« Remote Access. icon can be found

1.1 EN - 04/2011 L 85
L-force Controller | Parameter setting & configuration
Visualisation with »VisiWinNET®«
Constellation and connection

3. A double-click on this icon starts the Remote Access Manager.

 How to transfer an application to the target device:

1. In the »VisiWinNET®« menu bar,
select ProjectTransfer to target device.
• The Connect device window appears.

2. Enter the IP address of the L-force Controller in the IP address or network name text
field.
You can view and alter the IP address of the L-force Controller in the "Network
Connections" program. Configuring the L-force Controller ( 19)
3. Click the Connect button.
Note!
If the firewall of Windows® XP is active, you have to enable a port for
»VisiWinNET®«. In the standard setting this is port 10116.
• The application is transferred to the target device.

86 L 1.1 EN - 04/2011
 L-force Controller | Parameter setting & configuration
Visualisation with »VisiWinNET®«
Configuration of the OPC tunnel

12.4 Configuration of the OPC tunnel

The OPC tunnel...

...enables »VisiWinNET®« to access the OPC servers of the L-force Controller.
...makes sure that all accesses are tunneled via a specific Ethernet port and thus presents
the precondition for remote access by security systems.
 Depending on the system on which the visualisation takes place, you have to configure
the OCT tunnel accordingly.

 Note!
If the Windows® XP firewall is activated, one of the ports (standard setting: port
56765) needs to be activated for the OPC tunnel!

The configuration is carried out in the oct.xml file.

 The file can be edited using Microsoft WordPad and Microsoft Editor .
The following cases are distinguished:
1. local Visu on the Lenze L-force Controller control system: Local visualisation
(integrated control system) ( 88)
2. external Visu on a Lenze L-force Controller: External visualisation (remote access)
( 89)

3. external Visu on a WinXP or WinEmbeddedXP computer: External Visu on a

Windows XP/XP Embedded L-force Controller (remote access) ( 91)

1.1 EN - 04/2011 L 87
L-force Controller | Parameter setting & configuration
Visualisation with »VisiWinNET®«
Configuration of the OPC tunnel

12.4.1 Local visualisation (integrated control system)

[12-1] Local visualisation on a Lenze L-force Controller control system

 The local »VisiWinNET®« application on the Lenze L-force Controller) accesses the
corresponding OPC server via the local OPC tunnel.
 The oct.xml configuration file in the \USBstorage\OCT directory is used to
configure the OPC tunnel.

 Note!
For a local visualisation on the L-force Controller, the configuration file need not
be adapted! Do not change the standard settings of the configuration file.

88 L 1.1 EN - 04/2011
 L-force Controller | Parameter setting & configuration
Visualisation with »VisiWinNET®«
Configuration of the OPC tunnel

12.4.2 External visualisation (remote access)

[12-2] External visualisation using a visualisation L-force Controller (visualisation) and an L-force Controller (control)

The »VisiWinNET®« application of the external Lenze L-force Controller (Visu) accesses the
OPC server of the control L-force Controller via the OPC tunnel. In the example, the IP
address of the L-force Controller (controller) is: 192.168.5.99
 For configuring OPC tunnel 1, use the oct.xml configuration file in the
\USBStorage\OCT storage\OCT directory. Enter the corresponding IP address of the
control L-force Controller in the configuration file (as described in the following
section).
 For configuring OPC tunnel 2, use the oct.xml configuration file. The standard
settings need not be changed.

 Note!
For using an external visualisation, the oct.xml adapt the configuration file on
the visualisation L-force Controller (Visu) accordingly.

1.1 EN - 04/2011 L 89
L-force Controller | Parameter setting & configuration
Visualisation with »VisiWinNET®«
Configuration of the OPC tunnel

Preparation

 Read in the SD card of the visualisation L-force Controller on your PC using a card
reader

or

 Establish an FTP connection between your PC and the visualisation L-force

Controller FTP connection ( 61)

 How to set up an external visualisation on a Lenze L-force Controller:

1. Go to the \Storage\OCT directory
2. Rename the oct.xml file to oct_save.xml
3. Rename the octvisu.xml file to oct.xml
4. Open the oct.xml file using an editor. This is a text file. For file editing you can for
instance use the Microsoft Editor software.
5. Go to the following section:
<Server ID="RemoteIPC" URL="tpda://172.31.207.56:56765" ProvideItems="dynamic"
ItemPre-fix="RemoteIPC" EstablishConnection="on demand"/>

6. Enter IP address of the Lenze control L-force Controller.

7. Line contents (example):
<Server ID="RemoteIPC" URL="tpda://192.168.5.99:56765" ProvideItems="dynamic" ItemPre-
fix="RemoteIPC" EstablishConnection="on demand"/>

8. Save changed file on the SD card.

9. Restart visualisation L-force Controller.
• The OPC servers of the control L-force Controller can now be accessed.

 Tip!
To undo faulty changes in the configuration files, the original state of the
configuration files can be restored. For this, delete all configuration files from the
\Storage\OCT directory and restart the L-force Controller.

90 L 1.1 EN - 04/2011
 L-force Controller | Parameter setting & configuration
Visualisation with »VisiWinNET®«
Configuration of the OPC tunnel

12.4.3 External Visu on a Windows XP/XP Embedded L-force Controller (remote access)

 The »VisiWinNET®« application of the external Windows XP/XP Embedded L-force

Controller accesses the OPC server of the control IPC (controller) (via OPC tunnel 1). In
the example, the IP address of the control L-force controller (controller) is:
192.168.5.99
 For configuring OPC tunnel 1, use the oct.xml configuration file in the
\Programs\Lenze\Lenze Digitec OPC Tunnel directory. Enter the
corresponding IP address of the control L-force controller in the configuration file (as
described in the following section).
 For configuring OPC tunnel 2, use the oct.xml configuration file. The standard
settings need not be changed.

 Note!
For using an external Visu on a Windows XP/XP Embedded L-force Controller,
the oct.xml configuration file on the Windows XP L-force Controller must be
adapted.

1.1 EN - 04/2011 L 91
L-force Controller | Parameter setting & configuration
Visualisation with »VisiWinNET®«
Configuration of the OPC tunnel

Preparation

 Install the OPC tunnel on the Windows XP IPC.

1. The required installation files are provided on the Lenze installation CD in the
following directory:

2. Execute the Setup_OPC_Tunnel_Vxxx.exe installation file.

 How to set up the external visualisation:

1. Open the Windows Explorer on the visualisation IPC
2. Go to the following directory: ... \Programs\Lenze\Lenze Digitec OPC
Tunnel
3. Open the oct.xml file using an editor.
• The file can for instance be edited using the Microsoft Editor
4. Go to the following file section:
<!-- <Server ID="RemoteIPC" URL="tpda://172.31.207.16:56765" ProvideItems="dynamic"
ItemPre-fix="RemoteIPC" EstablishConnection="on demand"> <FilterFile Path=""/>
</Server>-->

• Remove the "<!-" and "-->" comment characters at the beginning and at the
end of the section.
5. Enter IP address of the Lenze control L-force Controller
• In the example, the line contents is now as follows:
<Server ID="RemoteIPC" URL="tpda://192.168.5.99:56765" ProvideItems="dynamic" ItemPre-
fix="RemoteIPC" EstablishConnection="on demand"> <FilterFile Path=""/>
</Server>

6. Save the changed file.

7. Restart visualisation IPC.
• The OPC servers of the control L-force Controller can now be accessed

92 L 1.1 EN - 04/2011
 L-force Controller | Parameter setting & configuration
Visualisation with »VisiWinNET®«
Installing additional fonts

12.5 Installing additional fonts

 How to install additional fonts for the visualisation:

1. Copy the additional font file into the \usbstorage\Fonts directory on the SD
card.
2. In the PostStart.txt file, add the entry AddFont.exe.
The file PostStart.txt is stored in the \usbstorage directory (basic directory
of the SD card).

12.6 Lenze specifications - exception handling

12.6.1 Timeout (waiting position) of the CAN OPC server influences the time response of the
visualisation

When the visualisation directly accesses the codes of a controller and does not get any
response afterwards, this will cause a timeout (waiting position) of the
CAN OPC server.

 Note!
The timeout occurs if...
• ... VWGET / VWSET is used to read / write a variable via the CAN OPC server and
the node does not respond to it (SDO).
• ...Alarms or trends are connected to a variable which is retrieved via the CAN
OPC server and the node does not respond to it (SDO).
• ...no node is connected and no feedback takes place, a timeout is caused.

 Note!
The timeout of the CAN OPC server affects the display speed of the visualisation.
This may, for instance, cause a time delay for the page changeover in the
visualisation.

Remedy
When the timeout is changed in the registry, the visualisation can be operated again. For
this purpose you must enter the following data in the PostStart.txt file. This sets the
timeout to 200 ms.
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\CANXBusY]
"SDOTimeout"=dword:0xc8
"Timeout"=dword:0xc8

The designation CANXBusY designates the respective CAN interface.

1.1 EN - 04/2011 L 93
L-force Controller | Parameter setting & configuration
Visualisation with »VisiWinNET®«
Lenze specifications - exception handling

 Examples:
– The first CAN interface is called: CAN2Bus1
– The second CAN interface is called: CAN2Bus2

94 L 1.1 EN - 04/2011
 L-force Controller | Parameter setting & configuration
Parameter reference
Structure of the parameter description

13 Parameter reference
This chapter lists all parameters of the L-force Controller and the extension modules in
numerically ascending order.
The parameters of a Lenze device are called codes. Each code can be divided further into
subcodes.

 Note!
Depending on the configuration and assembly of your L-force Controller, the
parameter lists may vary.

This chapter contains the following parameters:

Standard device parameters of the L-force Controller: Parameters of standard devices ( 99)
Ethernet (on board) ( 120)
EtherCAT ( 122)
PLC (Logic/Motion) ( 126)
Backup&Restore ( 127)

Extension modules of the L-force Controller: Extension cards ( 130)

CAN communication card (MC-CAN2) ( 131)
PROFIBUS master communication card (MC-PBM) ( 136)

13.1 Structure of the parameter description

Each parameter is described in the parameter list in the form of a table which consists of
the following three areas:

Table header
The table header contains the following general information:
 Parameter number (Cxxxxx)
 Name of the parameter
 Data types
 Decimal and hexadecimal parameter index for access via bus systems

Table contents
The table contains further general explanations and notes on the parameter and the
possible settings. The representation depends on the parameter type:
 Parameters with read access ( 96)

1.1 EN - 04/2011 L 95
L-force Controller | Parameter setting & configuration
Parameter reference
Structure of the parameter description

 Parameters with write access ( 96)

Table footer
The table footer contains the Parameter attributes.

13.1.1 Data types

The following data types are available for parameters:

Data type Meaning

INTEGER_8 8-bit value with sign
INTEGER_16 16-bit value with sign
INTEGER_32 32-bit value with sign
INTEGER_64 64-bit value with sign
UNSIGNED_8 8-bit value without sign
UNSIGNED_16 16-bit value without sign
UNSIGNED_32 32-bit value without sign
UNSIGNED_64 64-bit value without sign
FLOAT_32 32-bit floating point number
FLOAT_64 64-bit floating point number
VISIBLE_STRING String of characters from printable characters
OCTET_STRING String of characters from any characters
BITFIELD_8 8-bit value bit coded
BITFIELD_16 16-bit value bit coded
BITFIELD_32 32-bit value bit coded
DATE Date

13.1.2 Parameters with read access

Parameters not having the "write access" attribute can only be read. The user cannot
change these parameters.

Description structure

Parameter | Name: Data type: _______

Cxxxxx | _____________ Index: _______

Description
Display range (min. value | unit | max. value)

; Read access Write access CINH PLC STOP No transfer

13.1.3 Parameters with write access

Parameters with a checkmark (;) in front of the "write access" attribute can be changed
by the user. The Lenze setting for these parameters is printed in bold.

96 L 1.1 EN - 04/2011
 L-force Controller | Parameter setting & configuration
Parameter reference
Structure of the parameter description

 The user can change these settings

– via a selection list or
– by directly entering a value.

13.1.3.1 Parameters with a setting range

Description structure

Parameter | Name: Data type: _______

Cxxxxx | _____________ Index: _______

Description
Setting range (min. value | unit | max. value) Lenze setting

; Read access ; Write access CINH PLC STOP No transfer

13.1.3.2 Parameters with a selection list

Description structure

Parameter | Name: Data type: _______

Cxxxxx | _____________ Index: _______

Description
Selection list (Lenze setting printed in bold)
1
2
3
; Read access ; Write access CINH PLC STOP No transfer

13.1.3.3 Parameters with a bit-coded setting

Description structure

Parameter | Name: Data type: _______

Cxxxxx | _____________ Index: _______

Description
Value is bit-coded:
Bit 0
...
Bit 31
; Read access ; Write access CINH PLC STOP No transfer

1.1 EN - 04/2011 L 97
L-force Controller | Parameter setting & configuration
Parameter reference
Structure of the parameter description

13.1.3.4 Parameters with subcodes

Description structure

Parameter | Name: Data type: _______

Cxxxxx | _____________ Index: _______

Description
Setting range (min. value | unit | max. value)

Subcodes Lenze setting

Cxxxxx/1
Cxxxxx/2
Cxxxxx/3
Cxxxxx/4
; Read access ; Write access CINH PLC STOP No transfer

13.1.4 Parameter attributes

Attribute Meaning
; Read access Read access to parameter possible.
; Write access Write access to parameter possible.
; CINH This attribute is not used for parameterising the L-force Controller!
; PLC STOP This attribute is not used for parameterising the L-force Controller!
; No transfer This attribute is not used for parameterising the L-force Controller!

98 L 1.1 EN - 04/2011
 L-force Controller | Parameter setting & configuration
Parameter reference
Parameters of standard devices

13.2 Parameters of standard devices

In this chapter all parameters of the L-force Controller standard devices are listed in
numerically ascending order.

C0003
Parameter | Name: Data type: VISIBLE_STRING
C0003 | Device: Name Index: 24572d = 5FFCh

Device name of the L-force Controller

; Read access Write access CINH PLC STOP No transfer

C0004
Parameter | Name: Data type: VISIBLE_STRING
C0004 | Device: Software version Index: 24571d = 5FFBh

Software version of the L-force Controller

; Read access Write access CINH PLC STOP No transfer

C0005
Parameter | Name: Data type: VISIBLE_STRING
C0005 | Device: Hardware version Index: 24570d = 5FFAh

Hardware version of the L-force Controller

; Read access Write access CINH PLC STOP No transfer

C0006
Parameter | Name: Data type: VISIBLE_STRING
C0006 | Device: Serial number Index: 24569d = 5FF9h

Serial number of the L-force Controller

; Read access Write access CINH PLC STOP No transfer

C0007
Parameter | Name: Data type: VISIBLE_STRING
C0007 | Device: Manufacturer Index: 24568d = 5FF8h

Manufacturer of the L-force Controller

; Read access Write access CINH PLC STOP No transfer

C0008
Parameter | Name: Data type: VISIBLE_STRING
C0008 | Device: Manufacturing date Index: 24567d = 5FF7h

Date of manufacture of the L-force Controller

; Read access Write access CINH PLC STOP No transfer

C0016
Parameter | Name: Data type: VISIBLE_STRING
C0016 | System identification: Description Index: 24559d = 5FEFh

Description for the identification on the system

; Read access ; Write access CINH PLC STOP No transfer

1.1 EN - 04/2011 L 99
L-force Controller | Parameter setting & configuration
Parameter reference
Parameters of standard devices

C0018
Parameter | Name: Data type
C0018 | Command Index: 24557d = 5FEDh

Load PLC program command. Here the PLC boot project is reloaded.
Selection list (Lenze setting printed in bold) Information
0 No command
279 Persist all Save the data from the following tables to the
management data base:
• Data of the object table
• Data of all address tables
• Data of the file table
302 Delete logbook
304 Export complete logbook
512 Start PLC
513 Stop PLC
515 PLC: Reload boot project
1282 Persist logbook Save the logbook with all entries to a logbook file
1538 Start FTP server
1539 Stop FTP server
1560 Update FTP server
1540 Start telnet server
1541 Stop telnet server
1561 Update telnet server
1542 Start web server
1543 Stop web server
1562 Update web server
; Read access ; Write access CINH PLC STOP ; No transfer

C0019
Parameter | Name: Data type
C0019 | Command status Index: 24556d = 5FECh

Code with the status of the running command

Display range (min. value | unit | max. value)

; Read access Write access CINH PLC STOP No transfer

C0020
Parameter | Name: Data type: VISIBLE_STRING
C0020 | CPU: Name Index: 24555d = 5FEBh

CPU type designation

; Read access Write access CINH PLC STOP No transfer

C0030
Parameter | Name: Data type
C0030 | CPU: Temperature Index: 24545d = 5FE1h

Processor temperature [°C]

Display range (min. value | unit | max. value)
0 °C 255
; Read access Write access CINH PLC STOP No transfer

100 L 1.1 EN - 04/2011

 L-force Controller | Parameter setting & configuration
Parameter reference
Parameters of standard devices

C0040
Parameter | Name: Data type
C0040 | Activate front USB Index: 24535d = 5FD7h

The optional USB socket located on the front monitor panel is

• activated by entering "1" and
• deactivated by entering "0".
Setting range (min. value | unit | max. value) Lenze setting
0 1 0
; Read access ; Write access CINH PLC STOP No transfer

C0041
Parameter | Name: Data type: UNSIGNED_32
C0041 | Operating time Index: 24534d = 5FD6h

Total operating time since the device has been switched on [s]
Display range (min. value | unit | max. value)
0 h 16777215
; Read access Write access CINH PLC STOP No transfer

C0042
Parameter | Name: Data type: UNSIGNED_32
C0042 | Number of reboots Index: 24533d = 5FD5h

Number of boot processes of the device

Display range (min. value | unit | max. value)
0 65535
; Read access Write access CINH PLC STOP No transfer

C0043
Parameter | Name: Data type
C0043 | Activate Explorer Index: 24532d = 5FD4h

Setting range (min. value | unit | max. value) Lenze setting

0 1 1
; Read access ; Write access CINH PLC STOP No transfer

C0048
Parameter | Name: Data type: UNSIGNED_32
C0048 | Logbook: Time to auto persist Index: 24527d = 5FCFh

The time for the timer is entered in minutes. The timer is restarted when the log service has saved data. If the time
has expired and no logbook entries have been saved in the meantime, the saving process will be activated.
Setting range (min. value | unit | max. value) Lenze setting
min 2 min
; Read access ; Write access CINH PLC STOP No transfer

C0049
Parameter | Name: Data type: UNSIGNED_32
C0049 | Entry count to auto persist Index: 24526d = 5FCEh

Enter the number of logbook entries after which the saving process is to be activated. Counting starts with the last
saving.
Setting range (min. value | unit | max. value) Lenze setting
0 150 150
; Read access ; Write access CINH PLC STOP No transfer

1.1 EN - 04/2011 L 101

L-force Controller | Parameter setting & configuration
Parameter reference
Parameters of standard devices

C0050
Parameter | Name: Data type: UNSIGNED_32
C0050 | Logbook: Max. entries Index: 24525d = 5FCDh

Enter the maximum number of logbook entries. The logbook entries are taken from the main memory and from the
CF memory card.
Setting range (min. value | unit | max. value) Lenze setting
100 10000 1000
; Read access ; Write access CINH PLC STOP No transfer

C0051
Parameter | Name: Data type: UNSIGNED_32
C0051 | Logbook: Size on CF Index: 24524d = 5FCCh

Size of the memory space occupied on the CF memory card

Display range (min. value | unit | max. value)

; Read access Write access CINH PLC STOP No transfer

C0052
Parameter | Name: Data type: UNSIGNED_32
C0052 | Logbook: Number of entries in RAM Index: 24523d = 5FCBh

Actual number of entries in the RAM

Display range (min. value | unit | max. value)

; Read access Write access CINH PLC STOP No transfer

C0053
Parameter | Name: Data type: DATE
C0053 | Logbook: Time of oldest entry Index: 24522d = 5FCAh

Date of the oldest entry in the logbook

Display range (min. value | unit | max. value)
(Local time
; Read access Write access CINH PLC STOP No transfer

C0054
Parameter | Name: Data type: UNSIGNED_32
C0054 | Logbook: Index of oldest entry Index: 24521d = 5FC9h

Number of the oldest entry in the logbook

Display range (min. value | unit | max. value)

; Read access Write access CINH PLC STOP No transfer

C0055
Parameter | Name: Data type: DATE
C0055 | Logbook: Time of last entry on CF Index: 24520d = 5FC8h

Time of the last entry on the CF card

Display range (min. value | unit | max. value)
(Local time
; Read access Write access CINH PLC STOP No transfer

102 L 1.1 EN - 04/2011

 L-force Controller | Parameter setting & configuration
Parameter reference
Parameters of standard devices

C0056
Parameter | Name: Data type: UNSIGNED_32
C0056 | Logbook: Index of last entry on CF Index: 24519d = 5FC7h

Number of the last entry on the CF memory card

Display range (min. value | unit | max. value)

; Read access Write access CINH PLC STOP No transfer

C0057
Parameter | Name: Data type: UNSIGNED_32
C0057 | Logbook: Index of last entry Index: 24518d = 5FC6h

Number of the last entry in the logbook

Display range (min. value | unit | max. value)

; Read access Write access CINH PLC STOP No transfer

C0058
Parameter | Name: Data type: DATE
C0058 | Logbook: Time of last entry Index: 24517d = 5FC5h

Time of the last entry in the logbook

Display range (min. value | unit | max. value)
(Local time
; Read access Write access CINH PLC STOP No transfer

C0064
Parameter | Name: Data type: DATE
C0064 | Logbook: Time of last error entry Index: 24511d = 5FBFh

Entry of the last time error in the logbook

Display range (min. value | unit | max. value)
(Local time
; Read access Write access CINH PLC STOP No transfer

C0070
Parameter | Name: Data type: UNSIGNED_32
C0070 | Ratio: Data/program memory Index: 24505d = 5FB9h

• A part of the available memory is provided to the current programs as main memory.
• The other part is available as object store for saving files in the RAM.
• The percentage value indicated shows the ratio between object store (MemoryVirtualFilesAll) and total memory.
Setting range (min. value | unit | max. value) Lenze setting
0 % 100 50 %
; Read access ; Write access CINH PLC STOP No transfer

C0071
Parameter | Name: Data type: UNSIGNED_32
C0071 | Allocated program memory Index: 24504d = 5FB8h

Size of the reserved program memory

Display range (min. value | unit | max. value)
0 Bytes 4294967295
; Read access Write access CINH PLC STOP No transfer

1.1 EN - 04/2011 L 103

L-force Controller | Parameter setting & configuration
Parameter reference
Parameters of standard devices

C0072
Parameter | Name: Data type: UNSIGNED_32
C0072 | Used program memory Index: 24503d = 5FB7h

Size of the occupied program memory

Display range (min. value | unit | max. value)
0 Bytes 4294967295
; Read access Write access CINH PLC STOP No transfer

C0075
Parameter | Name: Data type: UNSIGNED_32
C0075 | Allocated virtual file memory Index: 24500d = 5FB4h

Object store reserved for saving of virtual files

Display range (min. value | unit | max. value)
0 Bytes 4294967295
; Read access Write access CINH PLC STOP No transfer

C0076
Parameter | Name: Data type: UNSIGNED_32
C0076 | Used virtual file memory Index: 24499d = 5FB3h

Object store occupied by virtual files

Display range (min. value | unit | max. value)
0 Bytes 4294967295
; Read access Write access CINH PLC STOP No transfer

C0078
Parameter | Name: Data type: UNSIGNED_32
C0078 | Allocated flash memory Index: 24497d = 5FB1h

Flash memory reserved

Display range (min. value | unit | max. value)
0 Bytes 4294967295
; Read access Write access CINH PLC STOP No transfer

C0079
Parameter | Name: Data type: UNSIGNED_32
C0079 | Used flash memory Index: 24496d = 5FB0h

Flash memory occupied

Display range (min. value | unit | max. value)
0 Bytes 4294967295
; Read access Write access CINH PLC STOP No transfer

C0090
Parameter | Name: Data type: DATE
C0090 | System: Date and time Index: 24485d = 5FA5h

Date and time

Setting range (min. value | unit | max. value) Lenze setting
NaN
; Read access ; Write access CINH PLC STOP ; No transfer

104 L 1.1 EN - 04/2011

 L-force Controller | Parameter setting & configuration
Parameter reference
Parameters of standard devices

C0091
Parameter | Name: Data type: DATE
C0091 | Local date and time Index: 24484d = 5FA4h

Local date and time.

Setting range (min. value | unit | max. value) Lenze setting
NaN
; Read access ; Write access CINH PLC STOP ; No transfer

C0092
Parameter | Name: Data type: VISIBLE_STRING
C0092 | Time zone Index: 24483d = 5FA3h

Time zone of the device.

Possible values: "Central European Standard Time", "North Pacific Standard Time", "GMT Standard Time", ...
Selection list (Lenze setting printed in bold) Information
Afghanistan Afghanistan Standard Time
Standard Time
Alaskan Standard Alaska Standard Time
Time
Arab Standard Arab Standard Time
Time
Arabian Standard Arabian Standard Time
Time
Arabic Standard Arabic Standard Time
Time
Atlantic Standard Atlantic Standard Time
Time
AUS Central AUS Central Standard Time
Standard Time
AUS Eastern AUS Eastern Standard Time
Standard Time
Azerbaijan Azores Standard Time
Standard Time
Azores Standard China Standard Time
Time
Canada Central Dateline Standard Time
Standard Time
Cape Verde E. Africa Standard Time
Standard Time
Caucasus E. Australia Standard Time
Standard Time
Cen. Australia E. Europe Standard Time
Standard Time
Central America E. South America Standard Time
Standard Time
Central Asia Eastern Standard Time
Standard Time
Central Brazilian Egypt Standard Time
Standard Time
Central Europe Ekaterinburg Standard Time
Standard Time
Central European Fiji Standard Time
Standard Time
Central Pacific Malay Peninsula Standard Time
Standard Time

1.1 EN - 04/2011 L 105

L-force Controller | Parameter setting & configuration
Parameter reference
Parameters of standard devices

Parameter | Name: Data type: VISIBLE_STRING

C0092 | Time zone Index: 24483d = 5FA3h

Central Standard Mexico Standard Time

Time
Central Standard Mexico Standard Time 2
Time (Mexico)
China Standard Mid-Atlantic Standard Time
Time
Dateline Mountain Standard Time
Standard Time
E. Africa Standard Myanmar Standard Time
Time
E. Australia N. Central Asia Standard Time
Standard Time
E. Europe Nepal Standard Time
Standard Time
E. South America New Zealand Standard Time
Standard Time
Eastern Standard Newfoundland Standard Time
Time
Egypt Standard SE Asia Standard Time
Time
Ekaterinburg South Africa Standard Time
Standard Time
Fiji Standard Sri Lanka Standard Time
Time
FLE Standard Taipei Standard Time
Time
Georgian Tasmania Standard Time
Standard Time
GMT Standard Tokyo Standard Time
Time
Greenland Tonga Standard Time
Standard Time
Greenwich US Eastern Standard Time
Standard Time
GTB Standard US Mountain Standard Time
Time
Hawaiian Vladivostok Standard Time
Standard Time
India Standard India Standard Time
Time
Iran Standard Iran Standard Time
Time
Israel Standard Jerusalem Standard Time
Time
Jordan Standard Jordan Standard Time
Time
Korea Standard Korea Standard Time
Time
Mid-Atlantic Mid-Atlantic Standard Time
Standard Time
Middle East Middle East Standard Time
Standard Time

106 L 1.1 EN - 04/2011

 L-force Controller | Parameter setting & configuration
Parameter reference
Parameters of standard devices

Parameter | Name: Data type: VISIBLE_STRING

C0092 | Time zone Index: 24483d = 5FA3h

Mountain Mountain Standard Time

Standard Time
Mountain Mountain Standard Time (Mexico)
Standard Time
(Mexico)
Myanmar Myanmar Standard Time
Standard Time
N. Central Asia N. Central Asia Standard Time
Standard Time
Namibia Namibia Standard Time
Standard Time
Nepal Standard Nepal Standard Time
Time
New Zealand New Zealand Standard Time
Standard Time
Newfoundland Newfoundland Standard Time
Standard Time
North Asia East North Asia East Standard Time
Standard Time
North Asia North Asia Standard Time
Standard Time
Pacific SA Pacific SA Standard Time
Standard Time
Pacific Standard Pacific Standard Time
Time
Pacific Standard Pacific Standard Time (Mexico)
Time (Mexico)
Romance Romance Standard Time
Standard Time
Russian Standard Russian Standard Time
Time
SA Eastern SA Eastern Standard Time
Standard Time
Singapore Malay Peninsula Standard Time
Standard Time
SA Pacific SA Pacific Standard Time
Standard Time
SA Western SA Western Standard Time
Standard Time
Samoa Standard Samoa Standard Time
Time
SE Asia Standard SE Asia Standard Time
Time
South Africa South Africa Standard Time
Standard Time
Sri Lanka Sri Lanka Standard Time
Standard Time
Taipei Standard Taipei Standard Time
Time
Tasmania Tasmania Standard Time
Standard Time
Tokyo Standard Tokyo Standard Time
Time

1.1 EN - 04/2011 L 107

L-force Controller | Parameter setting & configuration
Parameter reference
Parameters of standard devices

Parameter | Name: Data type: VISIBLE_STRING

C0092 | Time zone Index: 24483d = 5FA3h

Tonga Standard Tonga Standard Time

Time
US Eastern US Eastern Standard Time
Standard Time
US Mountain US Mountain Standard Time
Standard Time
Vladivostok Vladivostok Standard Time
Standard Time
W. Australia W. Australia Standard Time
Standard Time
W. Central Africa W. Central Africa Standard Time
Standard Time
W. Europe W. Europe Standard Time
Standard Time
West Asia West Asia Standard Time
Standard Time
West Pacific West Pacific Standard Time
Standard Time
Yakutsk Standard Yakutsk Standard Time
Time
; Read access ; Write access CINH PLC STOP No transfer

C0093
Parameter | Name: Data type: UNSIGNED_32
C0093 | Locale Index: 24482d = 5FA2h

Selection of regional and language options

Selection list (Lenze setting printed in bold) Information
1030 Danish (Denmark)
1043 Dutch (Netherlands)
1033 English (United States)
2057 English (United Kingdom)
1036 French (France)
1031 German (Germany)
1037 Hebrew (Israel)
1040 Italian (Italy)
1044 Norwegian (Norway, Bokmål)
2070 Portuguese (Portugal)
3082 Spanish (Spain, International Sort)
1053 Swedish (Sweden)
; Read access ; Write access CINH PLC STOP No transfer

C0095
Parameter | Name: Data type
C0095 | Activate VNC server Index: 24480d = 5FA0h

Activate parameter to start VNC server on the L-force Controller.

Setting range (min. value | unit | max. value) Lenze setting
0 1 0
; Read access ; Write access CINH PLC STOP No transfer

108 L 1.1 EN - 04/2011

 L-force Controller | Parameter setting & configuration
Parameter reference
Parameters of standard devices

C0097
Parameter | Name: Data type
C0097 | Activate VisiWinNET remote access Index: 24478d = 5F9Eh

Activate parameter to start the VisiWinNET remote access manager on the L-force Controller.
Setting range (min. value | unit | max. value) Lenze setting
0 1 1
; Read access ; Write access CINH PLC STOP No transfer

C0100
Parameter | Name: Data type
C0100 | WinCe user: Number Index: 24475d = 5F9Bh

Number of users registered

Display range (min. value | unit | max. value)
0 10
; Read access Write access CINH PLC STOP No transfer

C0101
Parameter | Name: Data type: VISIBLE_STRING
C0101 | WinCe user: User name 1 Index: 24474d = 5F9Ah

Name of the user

Default setting: admin
; Read access ; Write access CINH PLC STOP No transfer

C0102
Parameter | Name: Data type: VISIBLE_STRING
C0102 | WinCe user: Password 1 Index: 24473d = 5F99h

Password of the user

Default setting: admin
; Read access ; Write access CINH PLC STOP No transfer

C0103
Parameter | Name: Data type
C0103 | WinCE user: User 1 with FTP permissions Index: 24472d = 5F98h

User may use FTP

Setting range (min. value | unit | max. value) Lenze setting
0 1 1
; Read access ; Write access CINH PLC STOP No transfer

C0104
Parameter | Name: Data type: UNSIGNED_32
C0104 | FTP: Permissions user 1 Index: 24471d = 5F97h

FTP rights of the user.

Value is bit-coded:
Bit 0 Allow Read
Bit 1 Allow Write
Bit 2 Virtual Roots
Bit 3 Allow Hidden Files
; Read access ; Write access CINH PLC STOP No transfer

C0105
Parameter | Name: Data type: VISIBLE_STRING
C0105 | FTP: Home user 1 Index: 24470d = 5F96h

Home directory of the user

; Read access ; Write access CINH PLC STOP No transfer

1.1 EN - 04/2011 L 109

L-force Controller | Parameter setting & configuration
Parameter reference
Parameters of standard devices

C0106
Parameter | Name: Data type
C0106 | WinCE user: User 1 with telnet permissions Index: 24469d = 5F95h

User may use telnet

Setting range (min. value | unit | max. value) Lenze setting
0 1 1
; Read access ; Write access CINH PLC STOP No transfer

C0108
Parameter | Name: Data type: VISIBLE_STRING
C0108 | WinCe user: User name 2 Index: 24467d = 5F93h

Name of the user

; Read access ; Write access CINH PLC STOP No transfer

C0109
Parameter | Name: Data type: VISIBLE_STRING
C0109 | WinCe user: Password 2 Index: 24466d = 5F92h

Password of the user

; Read access ; Write access CINH PLC STOP No transfer

C0110
Parameter | Name: Data type
C0110 | WinCE user: User 2 with FTP permissions Index: 24465d = 5F91h

User may use FTP

Setting range (min. value | unit | max. value) Lenze setting
0 1 0
; Read access ; Write access CINH PLC STOP No transfer

C0111
Parameter | Name: Data type: UNSIGNED_32
C0111 | FTP: Permissions user 2 Index: 24464d = 5F90h

FTP rights of the user.

Value is bit-coded:
Bit 0 Allow Read
Bit 1 Allow Write
Bit 2 Virtual Roots
Bit 3 Allow Hidden Files
; Read access ; Write access CINH PLC STOP No transfer

C0112
Parameter | Name: Data type: VISIBLE_STRING
C0112 | FTP: Home user 2 Index: 24463d = 5F8Fh

Home directory of the user

; Read access ; Write access CINH PLC STOP No transfer

C0113
Parameter | Name: Data type
C0113 | WinCE user: User 2 with telnet permissions Index: 24462d = 5F8Eh

User may use telnet

Setting range (min. value | unit | max. value) Lenze setting
0 1 0
; Read access ; Write access CINH PLC STOP No transfer

110 L 1.1 EN - 04/2011

 L-force Controller | Parameter setting & configuration
Parameter reference
Parameters of standard devices

C0115
Parameter | Name: Data type: VISIBLE_STRING
C0115 | WinCe user: User name 3 Index: 24460d = 5F8Ch

Name of the user

; Read access ; Write access CINH PLC STOP No transfer

C0116
Parameter | Name: Data type: VISIBLE_STRING
C0116 | WinCe user: Password 3 Index: 24459d = 5F8Bh

Password of the user

; Read access ; Write access CINH PLC STOP No transfer

C0117
Parameter | Name: Data type
C0117 | WinCE user: User 3 with FTP permissions Index: 24458d = 5F8Ah

User may use FTP

Setting range (min. value | unit | max. value) Lenze setting
0 1 0
; Read access ; Write access CINH PLC STOP No transfer

C0118
Parameter | Name: Data type: UNSIGNED_32
C0118 | FTP: Permissions user 3 Index: 24457d = 5F89h

FTP rights of the user.

Value is bit-coded:
Bit 0 Allow Read
Bit 1 Allow Write
Bit 2 Virtual Roots
Bit 3 Allow Hidden Files
; Read access ; Write access CINH PLC STOP No transfer

C0119
Parameter | Name: Data type: VISIBLE_STRING
C0119 | FTP: Home user 3 Index: 24456d = 5F88h

Home directory of the user

; Read access ; Write access CINH PLC STOP No transfer

C0120
Parameter | Name: Data type
C0120 | WinCE user: User 3 with telnet permissions Index: 24455d = 5F87h

User may use telnet

Setting range (min. value | unit | max. value) Lenze setting
0 1 0
; Read access ; Write access CINH PLC STOP No transfer

C0122
Parameter | Name: Data type: VISIBLE_STRING
C0122 | WinCe user: User name 4 Index: 24453d = 5F85h

Name of the user

; Read access ; Write access CINH PLC STOP No transfer

C0123
Parameter | Name: Data type: VISIBLE_STRING
C0123 | WinCe user: Password 4 Index: 24452d = 5F84h

Password of the user

; Read access ; Write access CINH PLC STOP No transfer

1.1 EN - 04/2011 L 111

L-force Controller | Parameter setting & configuration
Parameter reference
Parameters of standard devices

C0124
Parameter | Name: Data type
C0124 | WinCE user: User 4 with FTP permissions Index: 24451d = 5F83h

User may use FTP

Setting range (min. value | unit | max. value) Lenze setting
0 1 0
; Read access ; Write access CINH PLC STOP No transfer

C0125
Parameter | Name: Data type: UNSIGNED_32
C0125 | FTP: Permissions user 4 Index: 24450d = 5F82h

FTP rights of the user.

Value is bit-coded:
Bit 0 Allow Read
Bit 1 Allow Write
Bit 2 Virtual Roots
Bit 3 Allow Hidden Files
; Read access ; Write access CINH PLC STOP No transfer

C0126
Parameter | Name: Data type: VISIBLE_STRING
C0126 | FTP: Home user 4 Index: 24449d = 5F81h

Home directory of the user

; Read access ; Write access CINH PLC STOP No transfer

C0127
Parameter | Name: Data type
C0127 | WinCE users: User 4 with telnet permissions Index: 24448d = 5F80h

User may use telnet

Setting range (min. value | unit | max. value) Lenze setting
0 1 0
; Read access ; Write access CINH PLC STOP No transfer

C0129
Parameter | Name: Data type: VISIBLE_STRING
C0129 | WinCe user: User name 5 Index: 24446d = 5F7Eh

Name of the user

; Read access ; Write access CINH PLC STOP No transfer

C0130
Parameter | Name: Data type: VISIBLE_STRING
C0130 | WinCe user: Password 5 Index: 24445d = 5F7Dh

Password of the user

; Read access ; Write access CINH PLC STOP No transfer

C0131
Parameter | Name: Data type
C0131 | WinCE user: User 5 with FTP permissions Index: 24444d = 5F7Ch

User may use FTP

Setting range (min. value | unit | max. value) Lenze setting
0 1 0
; Read access ; Write access CINH PLC STOP No transfer

112 L 1.1 EN - 04/2011

 L-force Controller | Parameter setting & configuration
Parameter reference
Parameters of standard devices

C0132
Parameter | Name: Data type: UNSIGNED_32
C0132 | FTP: Permissions user 5 Index: 24443d = 5F7Bh

FTP rights of the user.

Value is bit-coded:
Bit 0 Allow Read
Bit 1 Allow Write
Bit 2 Virtual Roots
Bit 3 Allow Hidden Files
; Read access ; Write access CINH PLC STOP No transfer

C0133
Parameter | Name: Data type: VISIBLE_STRING
C0133 | FTP: Home user 5 Index: 24442d = 5F7Ah

Home directory of the user

; Read access ; Write access CINH PLC STOP No transfer

C0134
Parameter | Name: Data type
C0134 | WinCE user: User 5 with telnet permissions Index: 24441d = 5F79h

User may use telnet

Setting range (min. value | unit | max. value) Lenze setting
0 1 0
; Read access ; Write access CINH PLC STOP No transfer

C0136
Parameter | Name: Data type: VISIBLE_STRING
C0136 | WinCe user: User name 6 Index: 24439d = 5F77h

Name of the user

; Read access ; Write access CINH PLC STOP No transfer

C0137
Parameter | Name: Data type: VISIBLE_STRING
C0137 | WinCe user: Password 6 Index: 24438d = 5F76h

Password of the user

; Read access ; Write access CINH PLC STOP No transfer

C0138
Parameter | Name: Data type
C0138 | WinCE user: User 6 with FTP permissions Index: 24437d = 5F75h

User may use FTP

Setting range (min. value | unit | max. value) Lenze setting
0 1 0
; Read access ; Write access CINH PLC STOP No transfer

C0139
Parameter | Name: Data type: UNSIGNED_32
C0139 | FTP: Permissions user 6 Index: 24436d = 5F74h

FTP rights of the user.

1.1 EN - 04/2011 L 113

L-force Controller | Parameter setting & configuration
Parameter reference
Parameters of standard devices

Parameter | Name: Data type: UNSIGNED_32

C0139 | FTP: Permissions user 6 Index: 24436d = 5F74h

Value is bit-coded:
Bit 0 Allow Read
Bit 1 Allow Write
Bit 2 Virtual Roots
Bit 3 Allow Hidden Files
; Read access ; Write access CINH PLC STOP No transfer

C0140
Parameter | Name: Data type: VISIBLE_STRING
C0140 | FTP: Home user 6 Index: 24435d = 5F73h

Home directory of the user

; Read access ; Write access CINH PLC STOP No transfer

C0141
Parameter | Name: Data type
C0141 | WinCE user: User 6 with telnet permissions Index: 24434d = 5F72h

User may use telnet

Setting range (min. value | unit | max. value) Lenze setting
0 1 0
; Read access ; Write access CINH PLC STOP No transfer

C0143
Parameter | Name: Data type: VISIBLE_STRING
C0143 | WinCe user: User name 7 Index: 24432d = 5F70h

Name of the user

; Read access ; Write access CINH PLC STOP No transfer

C0144
Parameter | Name: Data type: VISIBLE_STRING
C0144 | WinCe user: Password 7 Index: 24431d = 5F6Fh

Password of the user

; Read access ; Write access CINH PLC STOP No transfer

C0145
Parameter | Name: Data type
C0145 | WinCE user: User 7 with FTP permissions Index: 24430d = 5F6Eh

User may use FTP

Setting range (min. value | unit | max. value) Lenze setting
0 1 0
; Read access ; Write access CINH PLC STOP No transfer

C0146
Parameter | Name: Data type: UNSIGNED_32
C0146 | FTP: Permissions user 7 Index: 24429d = 5F6Dh

FTP rights of the user.

Value is bit-coded:
Bit 0 Allow Read
Bit 1 Allow Write
Bit 2 Virtual Roots
Bit 3 Allow Hidden Files
; Read access ; Write access CINH PLC STOP No transfer

114 L 1.1 EN - 04/2011

 L-force Controller | Parameter setting & configuration
Parameter reference
Parameters of standard devices

C0147
Parameter | Name: Data type: VISIBLE_STRING
C0147 | FTP: Home user 7 Index: 24428d = 5F6Ch

Home directory of the user

; Read access ; Write access CINH PLC STOP No transfer

C0148
Parameter | Name: Data type
C0148 | WinCE user: User 7 with telnet permissions Index: 24427d = 5F6Bh

User may use telnet

Setting range (min. value | unit | max. value) Lenze setting
0 1 0
; Read access ; Write access CINH PLC STOP No transfer

C0150
Parameter | Name: Data type: VISIBLE_STRING
C0150 | WinCe user: User name 8 Index: 24425d = 5F69h

Name of the user

; Read access ; Write access CINH PLC STOP No transfer

C0151
Parameter | Name: Data type: VISIBLE_STRING
C0151 | WinCe user: Password 8 Index: 24424d = 5F68h

Password of the user

; Read access ; Write access CINH PLC STOP No transfer

C0152
Parameter | Name: Data type
C0152 | WinCE user: User with 8 FTP permissions Index: 24423d = 5F67h

User may use FTP

Setting range (min. value | unit | max. value) Lenze setting
0 1 0
; Read access ; Write access CINH PLC STOP No transfer

C0153
Parameter | Name: Data type: UNSIGNED_32
C0153 | FTP: Permissions user 8 Index: 24422d = 5F66h

FTP rights of the user.

Value is bit-coded:
Bit 0 Allow Read
Bit 1 Allow Write
Bit 2 Virtual Roots
Bit 3 Allow Hidden Files
; Read access ; Write access CINH PLC STOP No transfer

C0154
Parameter | Name: Data type: VISIBLE_STRING
C0154 | FTP: Home user 8 Index: 24421d = 5F65h

Home directory of the user

; Read access ; Write access CINH PLC STOP No transfer

1.1 EN - 04/2011 L 115

L-force Controller | Parameter setting & configuration
Parameter reference
Parameters of standard devices

C0155
Parameter | Name: Data type
C0155 | WinCE user: User 8 with telnet permissions Index: 24420d = 5F64h

User may use telnet

Setting range (min. value | unit | max. value) Lenze setting
0 1 0
; Read access ; Write access CINH PLC STOP No transfer

C0157
Parameter | Name: Data type: VISIBLE_STRING
C0157 | WinCe user: User name 9 Index: 24418d = 5F62h

Name of the user

; Read access ; Write access CINH PLC STOP No transfer

C0158
Parameter | Name: Data type: VISIBLE_STRING
C0158 | WinCe user: Password 9 Index: 24417d = 5F61h

Password of the user

; Read access ; Write access CINH PLC STOP No transfer

C0159
Parameter | Name: Data type
C0159 | WinCE user: User 9 with FTP permissions Index: 24416d = 5F60h

User may use FTP

Setting range (min. value | unit | max. value) Lenze setting
0 1 0
; Read access ; Write access CINH PLC STOP No transfer

C0160
Parameter | Name: Data type: UNSIGNED_32
C0160 | FTP: Permissions user 9 Index: 24415d = 5F5Fh

FTP rights of the user.

Value is bit-coded:
Bit 0 Allow Read
Bit 1 Allow Write
Bit 2 Virtual Roots
Bit 3 Allow Hidden Files
; Read access ; Write access CINH PLC STOP No transfer

C0161
Parameter | Name: Data type: VISIBLE_STRING
C0161 | FTP: Home user 9 Index: 24414d = 5F5Eh

Home directory of the user

; Read access ; Write access CINH PLC STOP No transfer

C0162
Parameter | Name: Data type
C0162 | WinCE user: User 9 with telnet permissions Index: 24413d = 5F5Dh

User may use telnet

Setting range (min. value | unit | max. value) Lenze setting
0 1 0
; Read access ; Write access CINH PLC STOP No transfer

116 L 1.1 EN - 04/2011

 L-force Controller | Parameter setting & configuration
Parameter reference
Parameters of standard devices

C0164
Parameter | Name: Data type: VISIBLE_STRING
C0164 | WinCe user: User name 10 Index: 24411d = 5F5Bh

Name of the user

; Read access ; Write access CINH PLC STOP No transfer

C0165
Parameter | Name: Data type: VISIBLE_STRING
C0165 | WinCe user: Password 10 Index: 24410d = 5F5Ah

Password of the user

; Read access ; Write access CINH PLC STOP No transfer

C0166
Parameter | Name: Data type
C0166 | WinCE user: User 10 with FTP permissions Index: 24409d = 5F59h

User may use FTP

Setting range (min. value | unit | max. value) Lenze setting
0 1 0
; Read access ; Write access CINH PLC STOP No transfer

C0167
Parameter | Name: Data type: UNSIGNED_32
C0167 | FTP: Permissions user 10 Index: 24408d = 5F58h

FTP rights of the user.

Value is bit-coded:
Bit 0 Allow Read
Bit 1 Allow Write
Bit 2 Virtual Roots
Bit 3 Allow Hidden Files
; Read access ; Write access CINH PLC STOP No transfer

C0168
Parameter | Name: Data type: VISIBLE_STRING
C0168 | FTP: Home user 10 Index: 24407d = 5F57h

Home directory of the user

; Read access ; Write access CINH PLC STOP No transfer

C0169
Parameter | Name: Data type
C0169 | WinCE user: User 10 with telnet permissions Index: 24406d = 5F56h

User may use telnet

Setting range (min. value | unit | max. value) Lenze setting
0 1 0
; Read access ; Write access CINH PLC STOP No transfer

C0172
Parameter | Name: Data type: UNSIGNED_32
C0172 | FTP: Allow anonymous Index: 24403d = 5F53h

An unregistered users is allowed to log in. The user name is "anonymous"

• Entering "1" activates the log-in procedure
• Entering "0" deactivates the log-in procedure
Setting range (min. value | unit | max. value) Lenze setting
0 1 0
; Read access ; Write access CINH PLC STOP No transfer

1.1 EN - 04/2011 L 117

L-force Controller | Parameter setting & configuration
Parameter reference
Parameters of standard devices

C0173
Parameter | Name: Data type: UNSIGNED_32
C0173 | FTP: Allow anonymous upload Index: 24402d = 5F52h

An anonymous user is allowed to upload data to the L-force Controller with the following code setting:
• FtpAllowAnonymousUpload = true and
• FtpAllowAnonymous = true.
Setting range (min. value | unit | max. value) Lenze setting
0 1 1
; Read access ; Write access CINH PLC STOP No transfer

C0174
Parameter | Name: Data type: UNSIGNED_32
C0174 | FTP: Enabled Index: 24401d = 5F51h

Activation of the FTP service

• Entering "1" activates the FTP service
• Entering "0" deactivates the FTP service
Setting range (min. value | unit | max. value) Lenze setting
0 1 1
; Read access ; Write access CINH PLC STOP No transfer

C0180
Parameter | Name: Data type: UNSIGNED_32
C0180 | Telnet: Use authentication Index: 24395d = 5F4Bh

The telnet user has to identify himself/herself with name and password when connecting.
• Entering "1" activates the log-in procedure
• Entering "0" deactivates the log-in procedure
Setting range (min. value | unit | max. value) Lenze setting
0 1 1
; Read access ; Write access CINH PLC STOP No transfer

C0181
Parameter | Name: Data type: UNSIGNED_32
C0181 | Telnet: Enabled Index: 24394d = 5F4Ah

Activation of the telnet service

• Entering "1" activates the telnet service
• Entering "0" deactivates the telnet service
Setting range (min. value | unit | max. value) Lenze setting
0 1 1
; Read access ; Write access CINH PLC STOP No transfer

Display parameters of backplane bus

C0182
Parameter | Name: Data type: VISIBLE_STRING
C0182 | 0x100a: Software version Index: 24393d = 5F49h

Software version of the backplane bus controller

; Read access Write access CINH PLC STOP No transfer

C0183
Parameter | Name: Data type: VISIBLE_STRING
C0183 | 0x1009: Hardware version Index: 24392d = 5F48h

Hardware version of the backplane bus controller

; Read access Write access CINH PLC STOP No transfer

118 L 1.1 EN - 04/2011

 L-force Controller | Parameter setting & configuration
Parameter reference
Parameters of standard devices

C0184
Parameter | Name: Data type: VISIBLE_STRING
C0184 | 0x100a: Software version Index: 24391d = 5F47h

Software version of the backplane bus master

; Read access Write access CINH PLC STOP No transfer

C0185
Parameter | Name: Data type: VISIBLE_STRING
C0185 | 0x1009: Hardware version Index: 24390d = 5F46h

Hardware version of the backplane bus master

; Read access Write access CINH PLC STOP No transfer

C0186
Parameter | Name: Data type: VISIBLE_STRING
C0186 | PLC licence Index: 24389d = 5F45h

Licence level of the PLC. Possible licence levels:

• No licence
• Logic (LPC1000)
• Motion (MPC1200)
; Read access Write access CINH PLC STOP No transfer

C0187
Parameter | Name: Data type: VISIBLE_STRING
C0187 | Visualisation licence Index: 24388d = 5F44h

Visualisation licence (relevant for the visualisation in VisiWinNET) available on the L-force Controller. Possible
licence levels are for instance:
• Compact CE
• Compact XP
; Read access Write access CINH PLC STOP No transfer

C0188
Parameter | Name: Data type: UNSIGNED_32
C0188 | Visualisation: Number of powertags Index: 24387d = 5F43h

Number of maximum representable variables in VisiWinNET

Display range (min. value | unit | max. value)

; Read access Write access CINH PLC STOP No transfer

1.1 EN - 04/2011 L 119

L-force Controller | Parameter setting & configuration
Parameter reference
Ethernet (on board)

13.3 Ethernet (on board)

This chapter lists all parameters of the Ethernet interface (on board) of the
L-force Controller in numerically ascending order.

C0221
Parameter | Name: Data type: VISIBLE_STRING
C0221 | Device: Type key Index: 24354d = 5F22h

Type key of the interface

; Read access Write access CINH PLC STOP No transfer

C0222
Parameter | Name: Data type: VISIBLE_STRING
C0222 | Device: Type version Index: 24353d = 5F21h

Version number of the interface

; Read access Write access CINH PLC STOP No transfer

C0223
Parameter | Name: Data type: VISIBLE_STRING
C0223 | Device: Name Index: 24352d = 5F20h

Device name of the interface

; Read access Write access CINH PLC STOP No transfer

C0238
Parameter | Name: Data type
C0238 | Apply IP configuration Index: 24337d = 5F11h

Code for activating the set configuration. The interface is activated by writing a "1".
Selection list (Lenze setting printed in bold) Information
1 Activate device
0 No command
; Read access ; Write access CINH PLC STOP ; No transfer

C0240
Parameter | Name: Data type: UNSIGNED_32
C0240 | Enable Dhcp Index: 24335d = 5F0Fh

Activation of the configuration. DHCP states:

• "0" = Inactive
• "1" = Active
If DHCP is active, the codes 21-25 do not have any function
Setting range (min. value | unit | max. value) Lenze setting
0 1 0
; Read access ; Write access CINH PLC STOP No transfer

C0241
Parameter | Name: Data type: VISIBLE_STRING
C0241 | IP address Index: 24334d = 5F0Eh

IP address of the interface

; Read access ; Write access CINH PLC STOP No transfer

C0242
Parameter | Name: Data type: VISIBLE_STRING
C0242 | Subnet mask Index: 24333d = 5F0Dh

Subnet mask of the interface

; Read access ; Write access CINH PLC STOP No transfer

120 L 1.1 EN - 04/2011

 L-force Controller | Parameter setting & configuration
Parameter reference
Ethernet (on board)

C0243
Parameter | Name: Data type: VISIBLE_STRING
C0243 | Default gateway Index: 24332d = 5F0Ch

Default gateway of the interface

; Read access ; Write access CINH PLC STOP No transfer

C0244
Parameter | Name: Data type: VISIBLE_STRING
C0244 | Domain Index: 24331d = 5F0Bh

Domain name of the interface

; Read access ; Write access CINH PLC STOP No transfer

C0245
Parameter | Name: Data type: VISIBLE_STRING
C0245 | Host name Index: 24330d = 5F0Ah

Host name of the interface

; Read access ; Write access CINH PLC STOP No transfer

C0246
Parameter | Name: Data type: VISIBLE_STRING
C0246 | MAC address Index: 24329d = 5F09h

MAC address (6 8-bit hexadecimal numbers) (e.g. 00:af:13:42:01:a8)

; Read access Write access CINH PLC STOP No transfer

1.1 EN - 04/2011 L 121

L-force Controller | Parameter setting & configuration
Parameter reference
EtherCAT

13.4 EtherCAT

This chapter lists all EtherCAT parameters in numerically ascending order.

EtherCAT card

C280/4

Parameter | Name: Data type

C280/4 | ECAT bus scan result Index: 24295.4d =
0x5EE7.0x04h

Brief information on whether the master configuration complies with the physical bus structure or not. The stack
compares the master configuration with the actual bus structure.
Selection list (Lenze setting printed in bold) Information
0 No compliance Master configuration does not comply with bus
structure
1 OK Master configuration complies with bus structure
; Read access Write access CINH PLC STOP No transfer

C281/2

Parameter | Name: Data type

C281/2 | ECAT master: State Index: 24294.2d =
0x5EE6.0x02h

Display of the current state of the master

Selection list(read only)
0 Unknown
1 Init
2 Pre-Operational
3 Bootstrap mode Bootstrap mode is not supported.
4 Safe Operational
8 Operational
; Read access Write access CINH PLC STOP No transfer

C281/5

Parameter | Name: Data type: UNSIGNED_32

C281/5 | ECAT master: State information Index: 24294.5d =
0x5EE6.0x05h

Display of additional information on the current state of the master

The bits are set to value 1 if the respective states are reached.

122 L 1.1 EN - 04/2011

 L-force Controller | Parameter setting & configuration
Parameter reference
EtherCAT

Parameter | Name: Data type: UNSIGNED_32

C281/5 | ECAT master: State information Index: 24294.5d =
0x5EE6.0x05h

Value is bit-coded:
Bit 0 Master ok
Bit 1 Reserved 1
Bit 2 Reserved 2
Bit 3 Reserved 3
Bit 4 Init
Bit 5 Pre-Operational
Bit 6 Safe Operational
Bit 7 Operational
Bit 8 Slaves in requested state
Bit 9 Master in requested state
Bit 10 Bus scan result
Bit 11 Reserved 4
Bit 12 DC: Activated
Bit 13 DC: Sychronised
Bit 14 DC: Busy
Bit 15 Reserved 5
Bit 16 Link up
Bit 17 Reserved 6
... ...
Bit 31 Reserved 20
; Read access Write access CINH PLC STOP No transfer

C281/6

Parameter | Name: Data type

C281/6 | ECAT bus scan Index: 24294.6d =
0x5EE6.0x06h

Activation of the fieldbus scan

The fieldbus scan updates all EtherCAT codes.
Selection list (Lenze setting printed in bold)
0 No action
1 The bus is scanned
; Read access ; Write access CINH PLC STOP ; No transfer

C282/2

Parameter | Name: Data type: UNSIGNED_32

C282/2 | ECAT DC: Perm. dev. slave sync Index: 24293.2d =
0x5EE5.0x02h

Permissible deviation of the distributed clocks of all devices in nanoseconds. If the permissible deviation is
exceeded, the master will initiate a resynchronisation of the distributed clocks.
Display range (min. value | unit | max. value)
0 ns 4294967295
; Read access Write access CINH PLC STOP No transfer

1.1 EN - 04/2011 L 123

L-force Controller | Parameter setting & configuration
Parameter reference
EtherCAT

C282/3

Parameter | Name: Data type: INTEGER_32

C282/3 | ECAT DC: Current deviation Index: 24293.3d =
0x5EE5.0x03h

Current maximum deviation of the distributed clocks of all devices in nanoseconds.

Display range (min. value | unit | max. value)
-2147483647 ns 2147483647
; Read access Write access CINH PLC STOP No transfer

C286/3

Parameter | Name: Data type: UNSIGNED_32

C286/3 | ECAT bus: No. of slaves Index: 24289.3d =
0x5EE1.0x03h

Number of slaves connected to the fieldbus

Display range (min. value | unit | max. value)
0 4294967295
; Read access Write access CINH PLC STOP No transfer

C286/4

Parameter | Name: Data type: UNSIGNED_32

C286/4 | ECATBus: No. of slaves with DC Index: 24289.4d =
0x5EE1.0x04h

Number of slaves connected to the fieldbus and supported by distributed clocks

Display range (min. value | unit | max. value)
0 4294967295
; Read access Write access CINH PLC STOP No transfer

C286/5

Parameter | Name: Data type: UNSIGNED_32

C286/5 | ECAT config.: No. of slaves Index: 24289.5d =
0x5EE1.0x05h

Number of slaves configured in the master configuration file

Display range (min. value | unit | max. value)
0 4294967295
; Read access Write access CINH PLC STOP No transfer

C286/6

Parameter | Name: Data type: UNSIGNED_32

C286/6 | ECAT config.: No. of mailbox slaves Index: 24289.6d =
0x5EE1.0x06h

Number of mailbox slaves configured in the master configuration file

Display range (min. value | unit | max. value)
0 4294967295
; Read access Write access CINH PLC STOP No transfer

124 L 1.1 EN - 04/2011

 L-force Controller | Parameter setting & configuration
Parameter reference
EtherCAT

C286/7

Parameter | Name: Data type: UNSIGNED_32

C286/7 | ECAT counter: Tx frames Index: 24289.7d =
0x5EE1.0x07h

Number of sent frames

Display range (min. value | unit | max. value)
0 4294967295
; Read access Write access CINH PLC STOP No transfer

C286/8

Parameter | Name: Data type: UNSIGNED_32

C286/8 | ECAT counter: Rx frames Index: 24289.8d =
0x5EE1.0x08h

Number of received frames

Display range (min. value | unit | max. value)
0 4294967295
; Read access Write access CINH PLC STOP No transfer

C286/9

Parameter | Name: Data type: UNSIGNED_32

C286/9 | ECAT counter: Lost frames Index: 24289.9d =
0x5EE1.0x09h

Number of lost frames

Display range (min. value | unit | max. value)
0 4294967295
; Read access Write access CINH PLC STOP No transfer

C286/10

Parameter | Name: Data type: UNSIGNED_32

C286/10 | ECAT counter: Cyclic frames Index: 24289.10d =
0x5EE1.0x0Ah

Number of cyclic frames

Display range (min. value | unit | max. value)
0 4294967295
; Read access Write access CINH PLC STOP No transfer

C286/11

Parameter | Name: Data type: UNSIGNED_32

C286/11 | ECAT counter: Cyclic datagrams Index: 24289.11d =
0x5EE1.0x0Bh

Number of cyclic datagrams

Display range (min. value | unit | max. value)
0 4294967295
; Read access Write access CINH PLC STOP No transfer

1.1 EN - 04/2011 L 125

L-force Controller | Parameter setting & configuration
Parameter reference
PLC (Logic/Motion)

C286/12

Parameter | Name: Data type: UNSIGNED_32

C286/12 | ECAT counter: Acyclic frames Index: 24289.12d =
0x5EE1.0x0Ch

Number of acyclic frames

Display range (min. value | unit | max. value)
0 4294967295
; Read access Write access CINH PLC STOP No transfer

C286/13

Parameter | Name: Data type: UNSIGNED_32

C286/13 | ECAT counter: Acyclic datagrams Index: 24289.13d =
0x5EE1.0x0Dh

Number of acyclic datagrams

Display range (min. value | unit | max. value)
0 4294967295
; Read access Write access CINH PLC STOP No transfer

C286/14

Parameter | Name: Data type: UNSIGNED_32

C286/14 | ECAT: Reset individual counters Index: 24289.14d =
0x5EE1.0x0Eh

Reset frame and datagram counters (C1086/7 ... 13)

Selection list (Lenze setting printed in bold)
0 No action
1 Reset - All counters
2 Reset - Tx frame counters
4 Reset - Rx frame counters
8 Reset - Lost frame counters
16 Reset - Cyclic frame counters
32 Reset - Cyclic datagram counters
64 Reset - Acyclic frame counters
128 Reset - Acyclic datagram counters
; Read access ; Write access CINH PLC STOP ; No transfer

13.5 PLC (Logic/Motion)

In this chapter the parameters of the PLC (Logic/Motion) are listed in numerically
ascending order.

C0620
Parameter | Name: Data type: VISIBLE_STRING
C0620 | PLC: Status Index: 23955d = 5D93h

Status of the PLC application

; Read access Write access CINH PLC STOP No transfer

126 L 1.1 EN - 04/2011

 L-force Controller | Parameter setting & configuration
Parameter reference
Backup&Restore

13.6 Backup&Restore

In this chapter, all parameters for carrying out a »Backup & Restore« (using the
»WebConfig«) are listed in numerically ascending order.

C0809
Parameter | Name: Data type
C0809 | Select a main action for the Lenze software Index: 23766d = 5CD6h

Selection list (Lenze setting printed in bold) Information

0 Backup
; Read access ; Write access CINH PLC STOP No transfer

C0810
Parameter | Name: Data type
C0810 | Select a main action for the Lenze software Index: 23765d = 5CD5h

Carry out a backup or restore by means of the WebConfig.

•
Selection list (Lenze setting printed in bold) Information
2 Restore Carry out restore:
• Select the process to restore the data base of a backup
at an individual L-force Controller.
3 Auto restore Carry out auto restore:
• Restore (restore of a backup) at any number of L-force
Controllers.
• If you connect the USB stick to another L-force
Controller, the same process is carried out
automatically (standard set-up).
4 Update Carry out update:
• The software of the L-force Controller is updated (the
data is transferred from the USB stick to the internal
flash memory of the L-force Controller).
5 Auto update Carry out auto update:
• Multiple restore of an update at any number of L-
force Controllers.
• If you connect the USB stick to another L-force
Controller, the same process is carried out
automatically (standard set-up).
; Read access ; Write access CINH PLC STOP No transfer

C0811
Parameter | Name: Data type: VISIBLE_STRING
C0811 | Assign a name for the backup Index: 23764d = 5CD4h

; Read access ; Write access CINH PLC STOP No transfer

C0813
Parameter | Name: Data type
C0813 | Display of the backup or update files Index: 23762d = 5CD2h

Selection list (Lenze setting printed in bold) Information

1 Display 1 to 10
2 Display 11 to 20
3 Display 21 to 30
; Read access ; Write access CINH PLC STOP No transfer

C0814
Parameter | Name: Data type: VISIBLE_STRING
C0814 | Backup or update file 1 Index: 23761d = 5CD1h

; Read access Write access CINH PLC STOP No transfer

1.1 EN - 04/2011 L 127

L-force Controller | Parameter setting & configuration
Parameter reference
Backup&Restore

C0815
Parameter | Name: Data type: VISIBLE_STRING
C0815 | Backup or update file 2 Index: 23760d = 5CD0h

; Read access Write access CINH PLC STOP No transfer

C0816
Parameter | Name: Data type: VISIBLE_STRING
C0816 | Backup or update file 3 Index: 23759d = 5CCFh

; Read access Write access CINH PLC STOP No transfer

C0817
Parameter | Name: Data type: VISIBLE_STRING
C0817 | Backup or update file 4 Index: 23758d = 5CCEh

; Read access Write access CINH PLC STOP No transfer

C0818
Parameter | Name: Data type: VISIBLE_STRING
C0818 | Backup or update file 5 Index: 23757d = 5CCDh

; Read access Write access CINH PLC STOP No transfer

C0819
Parameter | Name: Data type: VISIBLE_STRING
C0819 | Backup or update file 6 Index: 23756d = 5CCCh

; Read access Write access CINH PLC STOP No transfer

C0820
Parameter | Name: Data type: VISIBLE_STRING
C0820 | Backup or update file 7 Index: 23755d = 5CCBh

; Read access Write access CINH PLC STOP No transfer

C0821
Parameter | Name: Data type: VISIBLE_STRING
C0821 | Backup or update file 8 Index: 23754d = 5CCAh

; Read access Write access CINH PLC STOP No transfer

C0822
Parameter | Name: Data type: VISIBLE_STRING
C0822 | Backup or update file 9 Index: 23753d = 5CC9h

; Read access Write access CINH PLC STOP No transfer

C0823
Parameter | Name: Data type: VISIBLE_STRING
C0823 | Backup or update file 10 Index: 23752d = 5CC8h

; Read access Write access CINH PLC STOP No transfer

C0824
Parameter | Name: Data type
C0824 | Select a backup or update Index: 23751d = 5CC7h

Selection list (Lenze setting printed in bold) Information

0 Nothing selected
1 Backup or update file 1
2 Backup or update file 2
3 Backup or update file 3
4 Backup or update file 4
5 Backup or update file 5
6 Backup or update file 6

128 L 1.1 EN - 04/2011

 L-force Controller | Parameter setting & configuration
Parameter reference
Backup&Restore

Parameter | Name: Data type

C0824 | Select a backup or update Index: 23751d = 5CC7h

7 Backup or update file 7

8 Backup or update file 8
9 Backup or update file 9
10 Backup or update file 10
; Read access ; Write access CINH PLC STOP No transfer

C0830
Parameter | Name: Data type
C0830 | Start backup Index: 23745d = 5CC1h

Selection list (Lenze setting printed in bold) Information

0 Do not carry out any action
1 Start backup with restart
; Read access ; Write access CINH PLC STOP No transfer

C0831
Parameter | Name: Data type
C0831 | Start restore update Index: 23744d = 5CC0h

Selection list (Lenze setting printed in bold) Information

0 Do not carry out any action
2 Start restore update with restart
; Read access ; Write access CINH PLC STOP No transfer

C0832
Parameter | Name: Data type: VISIBLE_STRING
C0832 | Backup status Index: 23743d = 5CBFh

; Read access Write access CINH PLC STOP No transfer

C0833
Parameter | Name: Data type: VISIBLE_STRING
C0833 | Restore update status Index: 23742d = 5CBEh

; Read access Write access CINH PLC STOP No transfer

1.1 EN - 04/2011 L 129

L-force Controller | Parameter setting & configuration
Parameter reference
Extension cards

13.7 Extension cards

This section represents the parameters of the different L-force Controller extension
modules. The following communication cards can be used:
CAN communication card (MC-CAN2) ( 131)
PROFIBUS master communication card (MC-PBM) ( 136)

130 L 1.1 EN - 04/2011

 L-force Controller | Parameter setting & configuration
Parameter reference
Extension cards

13.7.1 CAN communication card (MC-CAN2)

In this chapter all parameters of the MC-CAN2 communication card are listed in
numerically ascending order.

 Note!
If a CAN card is replaced, the parameters of the card previously used must be
checked and deviant settings will have to be adjusted!

Parameters of the card

C1031
Parameter | Name: Data type: VISIBLE_STRING
C1031 | Device: Type key Index: 23544d = 5BF8h

Card identification
; Read access Write access CINH PLC STOP No transfer

C1032
Parameter | Name: Data type: VISIBLE_STRING
C1032 | Device: Type version Index: 23543d = 5BF7h

Version number of the card

; Read access Write access CINH PLC STOP No transfer

C1033
Parameter | Name: Data type: VISIBLE_STRING
C1033 | Device: Name Index: 23542d = 5BF6h

Device name of the card

; Read access Write access CINH PLC STOP No transfer

C1034
Parameter | Name: Data type: VISIBLE_STRING
C1034 | Device: Software Index: 23541d = 5BF5h

Software version of the card

; Read access Write access CINH PLC STOP No transfer

C1035
Parameter | Name: Data type: VISIBLE_STRING
C1035 | Device: Hardware Index: 23540d = 5BF4h

Hardware version of the card

; Read access Write access CINH PLC STOP No transfer

C1036
Parameter | Name: Data type: VISIBLE_STRING
C1036 | Device: Serial number Index: 23539d = 5BF3h

Serial number of the card

; Read access Write access CINH PLC STOP No transfer

C1037
Parameter | Name: Data type: VISIBLE_STRING
C1037 | Device: Manufacturer Index: 23538d = 5BF2h

Manufacturer of the card

; Read access Write access CINH PLC STOP No transfer

1.1 EN - 04/2011 L 131

L-force Controller | Parameter setting & configuration
Parameter reference
Extension cards

C1038
Parameter | Name: Data type: VISIBLE_STRING
C1038 | Device: Manufacturing date Index: 23537d = 5BF1h

Manufacturing date of the card

; Read access Write access CINH PLC STOP No transfer

Parameters of the first CAN interface

C1073
Parameter | Name: Data type: UNSIGNED_32
C1073 | Device: Driver index Index: 23502d = 5BCEh

Index of the device driver. Since there can be more than one CAN interface, several instances can be run via the
driver.
Display range (min. value | unit | max. value)

; Read access Write access CINH PLC STOP No transfer

C1081
Parameter | Name: Data type: UNSIGNED_32
C1081 | Sync master: Interface index Index: 23494d = 5BC6h

Note: Restart the L-force Controller after changing this parameter!

Setting range (min. value | unit | max. value) Lenze setting
4294967295
; Read access ; Write access CINH PLC STOP No transfer

C1082
Parameter | Name: Data type: UNSIGNED_32
C1082 | Baud rate Index: 23493d = 5BC5h

Baud rate of the CAN interface. The value is assigned from a selection list.
Selection list (Lenze setting printed in bold)
7 5
6 10
5 20
3 50
8 100
2 125
1 250
0 500
4 1000
; Read access ; Write access CINH PLC STOP No transfer

C1090
Parameter | Name: Data type: UNSIGNED_32
C1090 | Tx PDO counter Index: 23485d = 5BBDh

PDO counter for sent CAN messages

Display range (min. value | unit | max. value)

; Read access Write access CINH PLC STOP No transfer

132 L 1.1 EN - 04/2011

 L-force Controller | Parameter setting & configuration
Parameter reference
Extension cards

C1091
Parameter | Name: Data type: UNSIGNED_32
C1091 | Rx PDO counter Index: 23484d = 5BBCh

PDO counter for received CAN messages

Display range (min. value | unit | max. value)

; Read access Write access CINH PLC STOP No transfer

C1092
Parameter | Name: Data type: UNSIGNED_32
C1092 | Bus load Index: 23483d = 5BBBh

Specification of the average bus load. The bus load is calculated as follows: Bus load = Value in percent x 1000
Display range (min. value | unit | max. value)

; Read access Write access CINH PLC STOP No transfer

C1093
Parameter | Name: Data type: UNSIGNED_32
C1093 | Error counter Index: 23482d = 5BBAh

Error counter since last initialisation of the CAN interface

Display range (min. value | unit | max. value)

; Read access Write access CINH PLC STOP No transfer

C1094
Parameter | Name: Data type: UNSIGNED_32
C1094 | Last error code Index: 23481d = 5BB9h

Code of the last error that occurred

Display range (min. value | unit | max. value)

; Read access Write access CINH PLC STOP No transfer

C1096
Parameter | Name: Data type
C1096 | CAN node ID Index: 23479d = 5BB7h

Setting range (min. value | unit | max. value) Lenze setting

0 128 63
; Read access ; Write access CINH PLC STOP No transfer

C1098
Parameter | Name: Data type: UNSIGNED_32
C1098 | Channel Index: 23477d = 5BB5h

Setting range (min. value | unit | max. value) Lenze setting

0
; Read access ; Write access CINH PLC STOP No transfer

1.1 EN - 04/2011 L 133

L-force Controller | Parameter setting & configuration
Parameter reference
Extension cards

Parameters of the second CAN interface

C1113
Parameter | Name: Data type: UNSIGNED_32
C1113 | Device: Driver index Index: 23462d = 5BA6h

Index of the device driver. Since there can be more than one CAN interface, several instances can be run via the
driver.
Display range (min. value | unit | max. value)

; Read access Write access CINH PLC STOP No transfer

C1121
Parameter | Name: Data type: UNSIGNED_32
C1121 | Sync master: Interface index Index: 23454d = 5B9Eh

Note: Restart the L-force Controller after changing this parameter!

Setting range (min. value | unit | max. value) Lenze setting
4294967295
; Read access ; Write access CINH PLC STOP No transfer

C1122
Parameter | Name: Data type: UNSIGNED_32
C1122 | Baud rate Index: 23453d = 5B9Dh

Baud rate of the CAN interface. The value is assigned from a selection list.
Selection list (Lenze setting printed in bold)
7 5
6 10
5 20
3 50
8 100
2 125
1 250
0 500
4 1000
; Read access ; Write access CINH PLC STOP No transfer

C1130
Parameter | Name: Data type: UNSIGNED_32
C1130 | Tx PDO counter Index: 23445d = 5B95h

PDO counter for sent CAN messages

Display range (min. value | unit | max. value)

; Read access Write access CINH PLC STOP No transfer

C1131
Parameter | Name: Data type: UNSIGNED_32
C1131 | Rx PDO counter Index: 23444d = 5B94h

PDO counter for received CAN messages

Display range (min. value | unit | max. value)

; Read access Write access CINH PLC STOP No transfer

134 L 1.1 EN - 04/2011

 L-force Controller | Parameter setting & configuration
Parameter reference
Extension cards

C1132
Parameter | Name: Data type: UNSIGNED_32
C1132 | Bus load Index: 23443d = 5B93h

Specification of the average bus load. The bus load is calculated as follows: Bus load = Value in percent x 1000
Display range (min. value | unit | max. value)

; Read access Write access CINH PLC STOP No transfer

C1133
Parameter | Name: Data type: UNSIGNED_32
C1133 | Error counter Index: 23442d = 5B92h

Error counter since last initialisation of the CAN interface

Display range (min. value | unit | max. value)

; Read access Write access CINH PLC STOP No transfer

C1134
Parameter | Name: Data type: UNSIGNED_32
C1134 | Last error code Index: 23441d = 5B91h

Code of the last error that occurred

Display range (min. value | unit | max. value)

; Read access Write access CINH PLC STOP No transfer

C1136
Parameter | Name: Data type
C1136 | CAN node ID Index: 23439d = 5B8Fh

Setting range (min. value | unit | max. value) Lenze setting

0 128 63
; Read access ; Write access CINH PLC STOP No transfer

C1138
Parameter | Name: Data type: UNSIGNED_32
C1138 | Channel Index: 23437d = 5B8Dh

Setting range (min. value | unit | max. value) Lenze setting

0
; Read access ; Write access CINH PLC STOP No transfer

1.1 EN - 04/2011 L 135

L-force Controller | Parameter setting & configuration
Parameter reference
Extension cards

13.7.2 PROFIBUS master communication card (MC-PBM)

This chapter lists all parameters of the MC-PBM communication card in numerically
ascending order.

C1031
Parameter | Name: Data type: VISIBLE_STRING
C1031 | Device: Type key Index: 23544d = 5BF8h

Card identification
; Read access Write access CINH PLC STOP No transfer

C1032
Parameter | Name: Data type: VISIBLE_STRING
C1032 | Device: Type version Index: 23543d = 5BF7h

Version number of the card

; Read access Write access CINH PLC STOP No transfer

C1033
Parameter | Name: Data type: VISIBLE_STRING
C1033 | Device: Name Index: 23542d = 5BF6h

Device name of the card

; Read access Write access CINH PLC STOP No transfer

C1034
Parameter | Name: Data type: VISIBLE_STRING
C1034 | Device: Software Index: 23541d = 5BF5h

Software version of the card

; Read access Write access CINH PLC STOP No transfer

C1035
Parameter | Name: Data type: VISIBLE_STRING
C1035 | Device: Hardware Index: 23540d = 5BF4h

Hardware version of the card

; Read access Write access CINH PLC STOP No transfer

C1036
Parameter | Name: Data type: VISIBLE_STRING
C1036 | Device: Serial number Index: 23539d = 5BF3h

Serial number of the card

; Read access Write access CINH PLC STOP No transfer

C1037
Parameter | Name: Data type: VISIBLE_STRING
C1037 | Device: Manufacturer Index: 23538d = 5BF2h

Manufacturer of the card

; Read access Write access CINH PLC STOP No transfer

C1038
Parameter | Name: Data type: VISIBLE_STRING
C1038 | Device: Manufacturing date Index: 23537d = 5BF1h

Manufacturing date of the card

; Read access Write access CINH PLC STOP No transfer

136 L 1.1 EN - 04/2011

 L-force Controller | Parameter setting & configuration
Glossary

14 Glossary

A
AIF Abbreviation for "Automation Interface". Lenze-specific interface at the con-
troller on which a communication module can be plugged.
Communication module
Application Implementation of a precise function (e.g. speed control) on an individual de-
vice.
Application variable Structure of element variables which is communicated via network(s) using a
specific transfer mode. The definition of an application variable is completely
independent of a specific type of network.
Element variable
Axis An axis is a special variant of a system module and basically contains at least
one controller and one motor, but depending on the application it may con-
tain further devices, such as gearboxes and encoders.

B
Bus server Fieldbus-specific OPC server according to DRIVECOM specification.
OPC
DRIVECOM

C
CAL Abbreviation for "CAN Application Layer". Communication standard (CiA DS
201-207) which provides the objects, protocols and services for the event or
polling-controlled transfer of CAN messages and the transfer of greater data
areas 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 Abbreviation for "Controller Area Network". Serial, message-oriented (not
node-oriented) 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").
Catalogue A catalogue contains descriptive information on all element types that form
an »Engineer« project. The »Engineer« uses various catalogue types, e.g. for
devices, device modules, technology applications, function blocks, and mo-
tors. Each catalogue is labelled by versioning.
Catalogue package A catalogue package consists of several related catalogues and is named and
versioned. Multiple versions of a catalogue package can be added to an »Engi-
neer« installation. Every »Engineer« project can use an optional number of
catalogue packages. Each catalogue package can be used in exactly one ver-
sion.
CiA Abbreviation for "CAN in Automation (e. V.)": International manufacturer and
user organisation with the target to worldwide distribute the knowledge of
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 Abbreviation for "Component Object Model": Architecture developed by Mi-
crosoft® for the co-operation of individual executable software components
(objects) which communicate with each other in a similar manner and are not
connected until the program is running.
Communication module Generic term for Lenze function modules and communication modules.
Function module
Communication module

1.1 EN - 04/2011 L 137

L-force Controller | Parameter setting & configuration
Glossary

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.

D
DCOM Abbreviation for "Distributed Component Object Model": COM where the ex-
ecutable objects are distributed to different computers within one local area
network.
COM
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/
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
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 Abbreviation for "Function Interface". Lenze-specific interface at the controller
which can be plugged onto a function module.
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
L-force Controller The L-force Controller is used as a centralised system for the control and/or
visualisation of machines.

138 L 1.1 EN - 04/2011

 L-force Controller | Parameter setting & configuration
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 Abbreviation for "Network Management": Services and protocols for initialisa-
tion, configuration, management and network monitoring within one CAN
network according to the master/slave principle.
CAN

O
OLE Abbreviation for "Object Linking and Embedding": Insertion of functional ob-
jects into other applications, e.g. a Microsoft® Excel table into a Microsoft®
Word document.
OPC Abbreviation for "OLE for Process Control": Defines an interface based on the
Microsoft® Windows® technologies OLE, COM and DCOM which is enabled via
a data exchange between different automation devices and PC programs
without considering driver and interface problems.
COM
DCOM
OPC tunnel OPC server and OPC client can be on different PCs networked via Ethernet.
Communication between the PCs requires a special DCOM configuration. For
OPC communication from several computers, Lenze uses an OPC tunnel that
does not require any configuration.

P
PDF Abbr. for "Portable Document Format", a universal file format developed by
Adobe for the exchange of electronic documents. With this free software Ado-
be® Reader® PDF files can be displayed and printed, independent of the appli-
cation and platform used for the creation.
Internet: http://www.adobe.com/
PLC Abbreviation 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 transferit e.g. setpoints and control commands to an applica-
tion, output ports serve to, for instance, provide actual values and status mes-
sages.
Application
Machine application
Project element The topmost element (root element) in the project view with the global prop-
erties of the project.

R
RAS server With the Remote Access Service (RAS), Windows allows you to connect clients
via a modem, ISDN, or X.25-connection with the local network. Different
clients are supported and the selection and possible combinations of the
network protocols used are very flexible.
The clients connected with the Windows network via RAS can use all network
functions as if they were directly locally connected with the network.

1.1 EN - 04/2011 L 139

L-force Controller | Parameter setting & configuration
Glossary

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. Ein Reset-Node kann bei Lenze-Geräten du-
rch erneutes Netzschalten, einem Reset-Node-Befehl perNMT-Kommando
oder über die entsprechende Codestelle erfolgen.
CAN
NMT

S
ST Abbreviation 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 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 Abbreviation for "EXtensible Markup Language", a meta language which de-
scribes the structure of documents.

140 L 1.1 EN - 04/2011

 L-force Controller | Parameter setting & configuration
Index

15 Index
Zahlen C104 109
0x1009 C105 109
Hardware version (C183) 118 C106 110
Hardware version (C185) 119 C1073 132
0x100a C108 110
Software version (C182) 118 C1081 132
Software version (C184) 119 C1082 132
C109 110
A C1090 132
Activate Explorer 101 C1091 133
Activate front USB (C40) 101 C1092 133
Activate VisiWinNET remote access (C97) 109 C1093 133
Activate VNC server (C95) 108 C1094 133
Allocated flash memory (C78) 104 C1096 133
Allocated program memory (C71) 103 C1098 133
Allocated virtual file memory (C75) 104 C110 110
Application notes (representation) 12 C111 110
Apply IP configuration (C238) 120 C1113 134
Assign a name for the backup (C811) 127 C112 110
C1121 134
B C1122 134
Backup or update file 1 (C814) 127 C113 110
Backup or update file 10 (C823) 128 C1130 134
Backup or update file 2 (C815) 128 C1131 134
Backup or update file 3 (C816) 128 C1132 135
Backup or update file 4 (C817) 128 C1133 135
Backup or update file 5 (C818) 128 C1134 135
Backup or update file 6 (C819) 128 C1136 135
Backup or update file 7 (C820) 128 C1138 135
Backup or update file 8 (C821) 128 C115 111
Backup or update file 9 (C822) 128 C116 111
Backup status (C832) 129 C117 111
Baud rate (C1082) 132 C118 111
Baud rate (C1122) 134 C119 111
Bus load (C1092) 133 C120 111
Bus load (C1132) 135 C122 111
C123 111
C C124 112
C10 120
C125 112
C100 109
C126 112
C101 109
C127 112
C102 109
C129 112
C103 109
C130 112
C1031 131, 136
C131 112
C1032 131, 136
C132 113
C1033 131, 136
C133 113
C1034 131, 136
C134 113
C1035 131, 136
C136 113
C1036 131, 136
C137 113
C1037 131, 136
C138 113
C1038 132, 136
C139 113

1.1 EN - 04/2011 L 141

L-force Controller | Parameter setting & configuration
Index

C140 114 C245 121

C141 114 C246 121
C143 114 C26 100
C144 114 C280/4 | ECAT bus scan result 122
C145 114 C281/2 | ECAT master
C146 114 State 122
C147 115 C281/5 | ECAT master
C148 115 State information 122
C150 115 C281/6 | ECAT bus scan 123
C151 115 C282/2 | ECAT DC
C152 115 Perm. dev. slave sync 123
C153 115 C282/3 | ECAT DC
C154 115 Current deviation 124
C155 116 C286/10 | ECAT counter
Cyclic frames 125
C157 116
C286/11 | ECAT counter
C158 116
Cyclic datagrams 125
C159 116
C286/12 | ECAT counter
C16 99
Acyclic frames 126
C160 116
C286/13 | ECAT counter
C161 116
Acyclic datagrams 126
C162 116
C286/14 | ECAT
C164 117 Reset individual counters 126
C165 117 C286/3 | ECAT bus - No. of slaves 124
C166 117 C286/4 | ECATBus - No. of slaves with DC 124
C167 117 C286/5 | ECAT config.
C168 117 No. of slaves 124
C169 117 C286/6 | ECAT config.
C171 117 No. of mailbox slaves 124
C172 117 C286/7 | ECAT counter
C173 118 Tx frames 125
C174 118 C286/8 | ECAT counter
C18 100 Rx frames 125
C180 118 C286/9 | ECAT counter
C181 118 Lost frames 125
C182 118 C3 99
C183 118 C30 100
C184 119 C31 101
C185 119 C4 99
C186 119 C40 101
C187 119 C41 101
C188 119 C42 101
C19 100 C43 101
C20 100 C46 101
C218 120 C48 101
C221 120 C49 101
C222 120 C5 99
C223 120 C50 102
C238 120 C51 102
C240 120 C52 102
C241 120 C53 102
C242 120 C54 102
C243 121 C55 102
C244 121 C56 103

142 L 1.1 EN - 04/2011

 L-force Controller | Parameter setting & configuration
Index

C57 103 D
C58 103 Data types 96
C6 99 Default gateway (C243) 121
C620 126 Device
C64 103 Driver index (C1073) 132
C65 103 Driver index (C1113) 134
C7 99 Hardware version (C1035) 131, 136
C70 103 Hardware version (C5) 99
C71 103 Manufacturer (C1037) 131, 136
C72 104 Manufacturer (C7) 99
Manufacturing date (C1038) 132, 136
C75 104
Manufacturing date (C8) 99
C76 104
Name (C1033) 131, 136
C78 104
Name (C223) 120
C79 104 Name (C3) 99
C8 99 Serial number (C1036) 131, 136
C809 127 Serial number (C6) 99
C810 127 Software version (C1034) 131, 136
C811 127 Software version (C4) 99
C813 127 Type key (C1031) 131, 136
C814 127 Type key (C221) 120
C815 128 Type version (C1032) 131, 136
C816 128 Type version (C222) 120
C817 128 Display of the backup or update files (C813) 127
C818 128 Domain (C244) 121
C819 128
E
C820 128
ECAT
C821 128
Reset individual counters (C286/14) 126
C822 128
ECAT bus - No. of slaves (C286/3) 124
C823 128
ECAT bus scan (C281/6) 123
C824 128
ECAT bus scan result (C280/4) 122
C830 129
ECAT config.
C831 129
No. of mailbox slaves (C286/6) 124
C832 129
No. of slaves (C286/5) 124
C833 129
ECAT counter
C90 104 Acyclic datagrams (C286/13) 126
C91 105 Acyclic frames (C286/12) 126
C92 105 Cyclic datagrams (C286/11) 125
C93 108 Cyclic frames (C286/10) 125
C95 108 Lost frames (C286/9) 125
C97 109 Rx frames (C286/8) 125
CAN node ID (C1096) 133 Tx frames (C286/7) 125
CAN node ID (C1136) 135 ECAT DC - Current deviation (C282/3) 124
Channel (C1098) 133 ECAT DC - Perm. dev. slave sync (C282/2) 123
Channel (C1138) 135 ECAT master
Command (C18) 100 State (C281/2) 122
State information (C281/5) 122
Command status (C19) 100
ECATBus - No. of slaves with DC (C286/4) 124
Configure OPC tunnel 87
E-mail to Lenze 146
Connecting an Industrial PC 56
Enable Dhcp (C240) 120
Conventions used 10
Entering the IP address 19
CPU
Name (C20) 100 Error counter (C1093) 133
Temperature (C30) 100 Error counter (C1133) 135
EtherCAT I/O image 26

1.1 EN - 04/2011 L 143

L-force Controller | Parameter setting & configuration
Index

F Time to auto persist (C48) 101

Feedback to Lenze 146
FTP
M
Allow "Anonymous" (C172) 117 MAC address (C246) 121
Allow "Anonymous" upload (C173) 118 Module labelling 17
Enabled (C174) 118
Home user 1 (C105) 109 N
Home user 10 (C168) 117 Notes used 12
Home user 2 (C112) 110 Number of reboots (C42) 101
Home user 3 (C119) 111
Home user 4 (C126) 112 O
Home user 5 (C133) 113 Online connection between the Engineering PC and
Home user 6 (C140) 114 Industrial PC 32
Home user 7 (C147) 115 Operating time (C41) 101
Home user 8 (C154) 115
Home user 9 (C161) 116 P
Permissions user 1 (C104) 109
PLC
Permissions user 10 (C167) 117
Status (C620) 126
Permissions user 2 (C111) 110
PLC licence (C186) 119
Permissions user 3 (C118) 111
Permissions user 4 (C125) 112
Permissions user 5 (C132) 113
R
Permissions user 6 (C139) 113 Ratio
Permissions user 7 (C146) 114 Data/program memory (C70) 103
Permissions user 8 (C153) 115 Removing the Industrial PC 55
Permissions user 9 (C160) 116 Replacing the Industrial PC 55
Restore update status (C833) 129
G Rx PDO counter (C1091) 133
Generating a logbook entry (LLS_AddLog) 50 Rx PDO counter (C1131) 134

H S
Host name (C245) 121 Safety 13
Safety instructions (representation) 12
I SD card 11
Identifying the Industrial PC 16 Select a backup or update (C824) 128
IP address (C241) 120 Select a main action for the Lenze software (C809) 127
Select a main action for the Lenze software (C810) 127
L Setting IP addresses 32
Last error code (C1094) 133 Start backup (C830) 129
Last error code (C1134) 135 Start restore update (C831) 129
LDM_ParameterAccess_FB 48 Start screen 36
LLS_AddLog_FUN 50 Subnet mask (C242) 120
Local date and time (C91) 105 Sync master
Locale (C93) 108 Interface index (C1081) 132
Logbook Interface index (C1121) 134
Entry count to auto persist (C49) 101 System
Index of last entry (C57) 103 Date and time (C90) 104
Index of last entry on CF (C56) 103 System boot-up 18
Index of oldest entry (C54) 102 System identification
Max. entries (C50) 102 Description (C16) 99
Number of entries in RAM (C52) 102
Size on CF (C51) 102
Time of last entry (C58) 103
Time of last entry on CF (C55) 102
Time of last error entry (C64) 103
Time of oldest entry (C53) 102

144 L 1.1 EN - 04/2011

 L-force Controller | Parameter setting & configuration
Index

T User 9 with FTP permissions (C159) 116

Target group 8 User 9 with telnet permissions (C162) 116
User name 1 (C101) 109
Technical data of the L-force Controller 47
User name 10 (C164) 117
telnet
User name 2 (C108) 110
Enabled (C181) 118
User name 3 (C115) 111
Use authentication (C180) 118
User name 4 (C122) 111
Terms 11
User name 5 (C129) 112
Time zone (C92) 105 User name 6 (C136) 113
Tx PDO counter (C1090) 132 User name 7 (C143) 114
Tx PDO counter (C1130) 134 User name 8 (C150) 115
User name 9 (C157) 116
U
Used flash memory (C79) 104
Used program memory (C72) 104
Used virtual file memory (C76) 104
Using direct drivers for visualisations under Windows
CE 77
Using direct drivers for visualisations under Windows
XP 79

V
Visualisation
Number of powertags (C188) 119
Visualisation licence (C187) 119

W
WinCe users
Number (C100) 109
Password 1 (C102) 109
Password 10 (C165) 117
Password 2 (C109) 110
Password 3 (C116) 111
Password 4 (C123) 111
Password 5 (C130) 112
Password 6 (C137) 113
Password 7 (C144) 114
Password 8 (C151) 115
Password 9 (C158) 116
User 1 with FTP permissions (C103) 109
User 1 with telnet permissions (C106) 110
User 10 with FTP permissions (C166) 117
User 10 with telnet permissions (C169) 117
User 2 with FTP permissions (C110) 110
User 2 with telnet permissions (C113) 110
User 3 with FTP permissions (C117) 111
User 3 with telnet permissions (C120) 111
User 4 with FTP permissions (C124) 112
User 4 with telnet permissions (C127) 112
User 5 with FTP permissions (C131) 112
User 5 with telnet permissions (C134) 113
User 6 with FTP permissions (C138) 113
User 6 with telnet permissions (C141) 114
User 7 with FTP permissions (C145) 114
User 7 with telnet permissions (C148) 115
User 8 with FTP permissions (C152) 115
User 8 with telnet permissions (C155) 116

1.1 EN - 04/2011 L 145

 Your opinion is important to us

)(('%$&.
These instructions were created to the best of our knowledge
and belief to give you the best possible support for handling
our product.
If you have suggestions for improvement, please e-mail us to:
[email protected]

Thank you for your support.

Your Lenze documentation team

146 L
L 147
 
© 04/2011
) Lenze Automation GmbH Service Lenze Service GmbH
Hans-Lenze-Str. 1 Breslauer Straße 3
D-31855 Aerzen D-32699 Extertal
Germany Germany
+49 (0)5154 – 82 -0 00 80 00 / 24 4 68 77 (24 h helpline)

¬ +49 (0)5154 – 82 - 2800 ¬ +49 (0)51 54 / 82-11 12

| [email protected] | [email protected]

Þ www.Lenze.com

SHGCBAUTO-001 ƒ 13375708 ƒ EN 1.1 ƒ TD11

10 9 8 7 6 5 4 3 2 1