Controller: Automation Systems

Automation Systems
Controller
Parameter setting and programming _ _ _ _ _ _ _ _ _ Reference Manual EN

Ä.O+Kä
13461042
L
Contents
________________________________________________________________
1 About this documentation _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 6

1.1 Document history _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 9
1.2 Conventions used _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 10
1.3 Terminology used _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 11
1.4 Definition of the notes used _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 13
2 Safety instructions _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 14
3 Controller-based Automation: Central motion control _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 15
4 System structure _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 18
4.1 Engineering tools _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 20
4.2 Controller: The control centre of the Controller-based Automation _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 22
4.3 Runtime software of the Lenze Controllers _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 24
4.3.1 "Logic" runtime software _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 25
4.3.2 "Motion" runtime software _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 25
4.3.3 "Visu" runtime software _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 26
4.3.3.1 Sample topology 1: External monitor panel/display for
cabinet controllers _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 27
4.3.3.2 Sample topology 2: Separate control and visualisation _ _ _ _ _ _ _ _ _ _ _ _ _ 28
4.3.3.3 Sample topology 3: Independent control and visualisation
(CANopen) _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 29
5 Commissioning the controller _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 30

5.1 Identification _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 31
5.2 Control elements of the controllers _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 31
5.3 Starting the controller _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 32
5.4 Configuring the controller _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 33
5.4.1 Establishing an automatic dial-up connection _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 33
5.4.2 Entering the IP address of the controller _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 33
5.4.2.1 Cabinet controllers with external monitor panels (3231 C/3241 C) _ _ _ _ _ _ 34
5.4.2.2 Cabinet Controller without external monitor panel (c300/3221 C) _ _ _ _ _ _ 35
5.4.3 Specifying the IP address of the controller via file (optional) _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 36
5.4.4 Establishing Windows® CE access rights _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 37
5.4.4.1 Setting up Windows® CE users in »WebConfig« _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 37
5.4.5 Using your own wallpaper on the controller (Windows® CE) _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 38
5.5 I/O system 1000 at the backplane bus of a cabinet controller _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 39
5.5.1 Configuring I/O modules at the backplane bus _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 39
5.5.2 Determining the topology of the I/O modules automatically _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 41
5.6 Tabs of the I/O modules at the backplane bus _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 42
5.7 Error messages (backplane bus) _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 43
2 Lenze · Controller | Parameter setting & programming · Reference Manual · DMS 1.5 EN · 04/2014 · TD17
Contents
________________________________________________________________
6 Parameter setting using »WebConfig« _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 45

6.1 System structure _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 45
6.2 Parameterising the controller _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 45
6.3 Online connection from the Engineering PC to the controller _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 46
6.3.1 Setting IP addresses on the Engineering PC (example: Windows® XP) _ _ _ _ _ _ _ _ _ _ _ 46
6.4 Start »WebConfig« _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 47
6.5 User interface of »WebConfig« _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 48
6.5.1 Device parameters of the controller _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 50
6.5.2 Diagnostic/device commands _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 51
6.5.3 Logbook _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 52
6.5.3.1 Structure of a logbook entry: example _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 52
6.5.3.2 Filter options _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 53
6.5.3.3 Time filter for the display of logbook entries _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 53
6.5.3.4 Saving log files with mains failure protection _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 54
6.5.3.5 Export logbook entries _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 54
6.5.4 Device commands _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 55
6.5.5 User management _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 55
6.5.6 General parameters _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 55
6.5.7 Parameters of the communication cards _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 56
6.5.7.1 CAN communication card (MC-CAN2) _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 56
6.5.7.2 Optional PROFIBUS/PROFINET communication cards _ _ _ _ _ _ _ _ _ _ _ _ _ _ 57
6.5.8 Automatic update _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 57
6.5.9 Language selection _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 57
6.5.10 Parameter list buttons _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 57
7 Programming with the »PLC Designer« _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 58

7.2 Function blocks _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 60
7.3 Configuring and parameterising the controller using the control application _ _ _ _ _ _ _ _ _ _ _ _ 61
7.4 Controller c300/p300: Access to odd Controller addresses _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 62
7.5 Creating remanent variables (retain/persistent) _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 64
7.5.1 Storage of retain data on the SD card (only Controllers 3221 C/3231 C) _ _ _ _ _ _ _ _ _ _ 65
8 »Backup & Restore« (data backup/restore) _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 67
9 Data integrity in the event of a voltage failure _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 68

9.1 UPS functionality of the controllers _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 68
9.1.1 Internal UPS (for Controllers without UPS connection) _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 68
9.1.2 External UPS (for Controllers 3241 C with UPS connection) _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 69
9.2 Storage of »VisiWinNET® Smart« visualisation data _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 70
9.3 Storage of retain/persistent variables of the PLC _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 71
10 Device replacement - replacing the controller (in the event of service) _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 72

10.1 Removing the connected (defective) controller _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 72
10.2 Connecting the new controller/replacement device _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 73
10.3 After the device replacement: Automatic data update _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 75
10.4 Subsequent use of retain data on the new controller _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 77
10.5 Error messages after a device replacement _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 78
Lenze · Controller | Parameter setting & programming · Reference Manual · DMS 1.5 EN · 04/2014 · TD17 3
Contents
________________________________________________________________
11 Remote maintenance and diagnostics _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 79

11.1 Status LEDs of the Controllers _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 80
11.2 Diagnostics via Telnet _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 82
11.2.1 »WebConfig« settings _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 83
11.3 Data transfer via FTP _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 85
11.3.1 FTP settings with the »WebConfig« _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 86
11.3.2 FTP and web settings in the Internet Explorer _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 87
11.4 Diagnostics with the logbook _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 89
11.4.1 Logbook query via »WebConfig« _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 90
11.4.2 Logbook parameters _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 91
11.5 Activate Windows® CE interface _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 92
11.5.1 Remote Display: Remote control of Controller via Internet or LAN _ _ _ _ _ _ _ _ _ _ _ _ _ 94
11.5.2 Virtual Network Computing (VNC) _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 95
12 Visualisation with »VisiWinNET®« _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 96

12.1 Visualisation on the controller: local and remote _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 97
12.3 Using the visualisation to access data of the control/parameters _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 99
12.4 Use the Direct driver "LogicAndMotionV3" (local visualisation) _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 101
12.4.1 Selecting the target device using the Windows® CE operating system
(example 3200 C/p500) _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 102
12.4.2 Project Explorer _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 104
12.4.3 Using the variables browser to access variables (browse variables) _ _ _ _ _ _ _ _ _ _ _ _ 105
12.4.4 Accept variable definitions to project _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 107
12.4.5 Creating control elements/linking them to variables _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 108
12.4.6 Transferring an application to the target device _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 109
12.4.7 Start the »VisiWinNET®« _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 110
12.5 Using the LogicAndMotionV3 direct driver (remote access) _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 111
12.6 OPC tunnel for local visualisation (integrated control system) _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 112
12.6.1 Integrating the OPC tunnel in »VisiWinNET®« _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 113
12.6.2 Browsing variable definitions / configuring the device _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 114
12.6.3 Manual integration of variables (experts only - background knowledge required!) _ _ _ _ 116
12.6.4 Configure OPC tunnel _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 119
12.7 OPC tunnel for external visualisation (remote access) _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 120
12.7.1 Windows® CE operating system _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 120
12.7.1.1 Configure OPC tunnel for remote access (Windows® CE) _ _ _ _ _ _ _ _ _ _ _ _ 121
12.7.2 Windows® XP/XP Embedded operating system _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 122
12.7.2.1 Configure OPC tunnel for remote access (Windows® XP/XP Embedded) _ _ _ 123
12.7.3 Browsing variables _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 124
12.8 Lenze specifications _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 126
12.8.1 Install additional fonts _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 126
12.8.2 Timeout (waiting position) of the CAN OPC server influences the time response of the
visualisation _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 126
Contents
________________________________________________________________
13 Parameter reference _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 127

13.1 Structure of the parameter description _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 128
13.1.1 Data types _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 128
13.1.2 Parameters with read access _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 129
13.1.3 Parameters with write access _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 129
13.1.3.1 Parameters with a setting range _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 129
13.1.3.2 Parameters with a selection list _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 129
13.1.3.3 Parameters with a bit-coded setting _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 130
13.1.4 Parameter attributes _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 130
13.2 Basic parameters of the Controllers 3200 C/c300 and p300/p500 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 131
13.3 Voltage buffering by external UPS (optional, for Controller 3241 C) _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 158
13.4 Ethernet (on board) _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 161
13.5 EtherCAT _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 163
13.6 Monitor panel (integrated/external) _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 168
13.7 PLC (Logic/Motion) _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 172
13.8 Backup&Restore _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 174
13.9 Communication cards: optional interface _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 178
13.9.1 CAN (MC-CAN2) communication card / CAN interface for Controller c300/p300 _ _ _ _ _ 179
13.9.2 PROFIBUS and PROFINET communication cards _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 185
Index _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 187
Your opinion is important to us _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 194
1 About this documentation
________________________________________________________________

This documentation contains general information on how to parameterise, configure and diagnose
the Lenze Controllers.
This manual is part of the "Controller-based Automation" manual collection. It consists of the
following sets of documentation:
Documentation type Subject

System manuals System overview/sample topologies
• Controller-based Automation
• Visualization
Communication manuals Bus systems
Online helps • Controller-based Automation EtherCAT®
• Controller-based Automation CANopen®
• Controller-based Automation PROFIBUS®
• Controller-based Automation PROFINET®
Reference manuals Lenze Controller:
Online helps • Controller 3200 C
• Controller c300
• Controller p300
• Controller p500
Software manuals Lenze Engineering Tools:
Online helps • »PLC Designer«: Programming
• »Engineer«: Inverter configuration
• »VisiWinNET® Smart«: Visualisation
• »Backup & Restore«: Back up/restore data
 Information on how to use the controllers outside the control technology can be found
in the system manuals created for the prevailing application case.
________________________________________________________________
More technical documentation for Lenze components

Further information on Lenze products which can be used in conjunction with Controller-based
Automation can be found in the following sets of documentation:
Mounting & wiring Symbols:

 Mounting instructions  Printed documentation
• Controller  Online help in the Lenze Engineering
• Communication cards (MC-xxx) Tool (also available as PDF file at
• I/O system 1000 (EPM-Sxxx) www.lenze.com.)
• Inverter, Servo Drives
• Communication modules
 Operating instructions
• Controller
• Servo system ECS (ECSxE, ECSxM)
Sample applications/Using application templates
 Online help/software manuals
• Application Sample i700
• Application Samples
• ApplicationTemplate
Parameterisation, configuration, commissioning
 Online help/reference manuals
• Controller
• Inverter, Servo Drives
• I/O system 1000 (EPM-Sxxx)
 Online help/communication manuals
• Bus systems
• Communication modules
 Operating instructions
• Servo system ECS (ECSxE, ECSxM)
 Tip!
Current documentation and software updates with regard to Lenze products can be found
in the download area at:
www.lenze.com
Target group
This documentation is intended for persons who commission and maintain a Controller-based
automation system by means of a Lenze Controller and the »PLC Designer« engineering tool.
Screenshots/application examples
All screenshots in this documentation are application examples. Depending on the firmware
version of the field devices and the software version of the Engineering tools installed (e.g. »PLC
Designer« ), screenshots in this documentation may differ from the representation on the screen.
________________________________________________________________
Information regarding the validity

The information provided in this documentation is valid for the following Lenze Controllers:
Controller Versions
Cabinet Controller
• Controller 3221 C
Example: Controller 3241 C with connected I/O system 1000
• Controller c300
Example: Controller c300 with connected I/O system 1000
Panel Controller
• Controller p300
• Controller p500
Example: Controller p500
 Operating instructions/mounting instructions of the Controllers

Here you will find technical data and information on how to install the devices.
1.1 Document history
________________________________________________________________
1.1 Document history
Version Description
1.0 10/2010 TD11 First edition for the Lenze automation system "Controller-based Automation" 3.x
1.1 04/2011 TD11 Update for the Lenze automation system "Controller-based Automation" 3.1
• Amended by Controllers p500 (panel controllers)
• Controller c300/p300 added (in preparation)
• Controller c300/p300
1.2 Conventions used
________________________________________________________________
1.2 Conventions used
This documentation uses the following conventions to distinguish between different types of
information:
Type of information Highlighting Examples/notes

Spelling of numbers
Decimal separators Point The decimal point is generally 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 of the inverter are highlighted
correspondingly in this documentation.
Example: This function extension is available from software
version V3.0!
Program name »« »PLC Designer«...
Window italics The message window... / The Options dialog box ...
Variable names 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 carry out a
commands function, the individual commands are separated by an
arrow: Select FileOpen to...
Shortcut <bold> Use <F1> to open the online help.
If a key combination is required for a command, a "+" is
placed between the key identifiers: With <Shift>+<ESC>...
Hyperlink underlined Reference to further information: Hyperlink to further
information.
Symbols
Page reference ( 10) Reference to further information: Page number in PDF file.
Step-by-step instructions Step-by-step instructions are marked by a pictograph.

1.3 Terminology used
________________________________________________________________
Term Meaning
Controller The controller is the central component of the automation system which controls the
Logic and Motion functionalities by means of the runtime software.
The controller communicates with the field devices via the fieldbus.
Engineering PC The Engineering PC and the Engineering tools installed serve to configure and
parameterise the system "Controller-based Automation".
The Engineering PC communicates with the controller via Ethernet.
Fieldbus stations Devices integrated in the bus system as, for instance, Controller and inverter
Field device
Inverter Generic term for Lenze frequency inverter, servo inverter
PLC Programmable Logic Controller
PLC Programmable Logic Controller (PLC)
UPS Uninterruptible power system (UPS)
Engineering tools
Software solutions for easy engineering in all phases which serve to commission, configure, parameterise and
diagnose the Lenze automation system.
Engineering tools ( 20)
»EASY Navigator« – provides for orientation
• All convenient Lenze Engineering tools at a glance
• Tools can be selected quickly
• Simplifies the access to the engineering process by its clarity.
»EASY Starter« – easy-to-use tool for service technicians
• For the maintenance of Lenze devices
• For the commissioning of Lenze devices
• Online diagnostics, parameterisation and commissioning
• Loading of ready-to-use applications to the device
»Engineer« – multi-device engineering
• Suitable for all products of the Lenze portfolio
• Easy handling by means of graphical user interfaces
•
Can be used in all engineering phases (project planning, commissioning,
production)
• Parameterisation and configuration of Lenze devices
»PLC Designer« – programming processes
• Creating individual programs
• Programming Logic & Motion according to IEC 61131-3 (AWL, KOP, FUP,
ST, AS and CFC-Editor), based on CoDeSys V3
• Certified function blocks according to PLCopen part 1 + 2
• Graphic DIN 66025 Editor (G code) with DXF import
• Integrated visualisation for the simple representation of processes
»VisiWinNET« – visualisation tool
• Visualise the applications of the automation system
• Create the visualisation/user interface
»Backup & Restore« – back up/restore/update data

• Create data backups
• Restore data after device replacement
• Carry out software update of the Controller
Bus systems
CAN CAN (Controller Area Network) is an asynchronous, serial fieldbus system.
CANopen® is a communication protocol based on CAN. The Lenze system bus (CAN on
board) operates with a subset of this communication protocol.
CANopen® is a registered community trademark of the CAN user organisation CiA® (CAN
in Automation e. V.).
________________________________________________________________
Term Meaning
EtherCAT® (Ethernet for Controller and Automation Technology) is an Ethernet-based
fieldbus system which fulfils the application profile for industrial real-time systems.
EtherCAT® is a registered trademark and patented technology, licensed by Beckhoff
Automation GmbH, Germany.
PROFIBUS® (Process Field Bus) is a widely used fieldbus system for the automation of
machines and production lines.
PROFIBUS® is a registered trademark and patented technology licensed by the PROFIBUS
& PROFINET International (PI) user organisation.
PROFINET® (Process Field Network) is a real-time capable fieldbus system based on
Ethernet.
PROFINET® is a registered trademark and patented technology licensed by the PROFIBUS
& PROFINET International (PI) user organisation.
1.4 Definition of the notes used
________________________________________________________________
1.4 Definition of the notes used
This documentation uses the following signal words and symbols to indicate dangers and
important information:
Safety instructions
Structure of the safety instructions:
 Pictograph and signal word!

(characterises the type and severity of danger)
Note
(describes the danger and informs how to prevent dangerous situations)
Pictograph Signal word Meaning

Danger! Danger of personal injuries through dangerous electrical voltage
 Reference to an imminent danger that may result in death or serious personal
injury unless the corresponding measures are 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 unless the corresponding measures are taken.
Stop! Danger of material damage
 Indicates a potential danger that may lead to material damage unless the
corresponding measures are taken.
Application notes
Pictograph Signal word Meaning

Note! Important note to ensure troublefree operation

Tip! Useful tip for easy handling

Reference to another document

2 Safety instructions
________________________________________________________________
2 Safety instructions
Please observe the following safety instructions when you want to commission an automation
system or a plant using a controller.
 Read the documentation supplied with the corresponding field device thoroughly before
starting to commission the devices with the controller!
The device documentation contains safety instructions which must be observed!
 Danger!
According to today's scientific knowledge it is not possible to ensure absolute freedom
from defects of a software.
If necessary, systems with built-in inverters must be provided with additional
monitoring and protective equipment complying with the relevant safety regulations
(e.g. law on technical equipment, regulations for the prevention of accidents) in each
case, 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 an unintended direction of rotation, too high speed, or jerky operation, the driven
machine parts may be damaged.
3 Controller-based Automation: Central motion control
________________________________________________________________

The Lenze automation system "Controller-based Automation" serves to create complex automation
solutions with central motion control. Here, the Controller is the control centre of the system.
System structure of the Controller-based Automation: "All from one single source"
[3-1] Example configuration (EtherCAT bus system): Controller 3200 C with I/O system 1000 and Servo Inverter i700.
________________________________________________________________
Lenze supply specially matched system components:

• Engineering software
The Lenze Engineering tools ( 20) on your Engineering PC (Windows® operating system) serve
to parameterise, configure and diagnose the system. The Engineering PC communicates with
the Controller via Ethernet.
• Controller
The Lenze Controller is available as Panel Controller with integrated touch display and as
Cabinet Controller in control cabinet design.
Cabinet Controllers provide a direct coupling of the I/O system 100 via the integrated backplane
bus.
The Runtime software of the Lenze Controllers ( 24) provides the control and/or visualisation
of motion sequences. These software versions are available:
• "Logic": Sequence control in the Controller, motion control in the inverter
• "Motion": Sequence control and motion control in the Controller, inverter as actuating drive
• "Visu": Optional visualisation of the automation system, can be used separately or in addition
to "Logic" or "Motion"
An external monitor panel/display can be connected to the Cabinet Controller 3231 C/
3241 C.
• Without software: Controller as single component with operating system only
• Bus systems
EtherCAT is a standard "on board" bus system of the Controller-based Automation. EtherCAT
enables the control of all nodes (Motion/Logic) on one common fieldbus.
Optionally, CANopen, PROFIBUS and PROFINET can be used as extended topologies.
The Controllers c300/p300 have a CANopen interface "on board" as well (in addition to
EtherCAT).
• Inverter (e.g. Servo Inverter i700)
"Logic & Motion" runtime software

The "Controller-based Automation" system allows for the central control of devices for Logic and
Motion applications. The runtime software runs on the Controller.
In case of Logic applications, the sequence control is carried out in the Controller and the motion
control is carried out in the inverter.
In case of Motion applications , the sequence control and motion control are carried out in the
Controller. The inverter is used as actuating drive.
• Motion applications make special demands on the cycle time and real-time capability of the bus
system between the Controller and the subordinate fieldbus nodes.
• This is e.g. the case if the nodes must traverse synchronously or if position setpoints must be
transmitted.
________________________________________________________________
Fieldbus communication
The Lenze Controllers have different interfaces for fieldbus communication:
Area Cabinet Controller Panel Controller

c300 3221 C 3231 C 3241 C p300 p500
Interfaces (on board)
Ethernet 1 2 1 2
EtherCAT 1 1) 1 1 1) 1
CANopen 1 2) - 1 2) -
Optional interfaces (communication cards)
CANopen -  - 
MC-CAN2
PROFIBUS master -  - 
MC-PBM
PROFIBUS slave -  - 
MC-PBS
PROFINET device -  - 
MC-PND
1) In preparation
2) Only the CAN master functionality is supported.
The Ethernet interface serves to connect the Engineering PC or to create line topologies (no
integrated switch for Controller c300/p300).
 More information on the bus systems and configuration can be found in the
communication manuals:
• Controller-based Automation EtherCAT®
4 System structure
________________________________________________________________
4 System structure
This chapter provides you with an overview of the basic system structure of the Lenze "Controller-
based Automation" system. The system consists of an Engineering PC, a Controller and the devices
communicating with the Controller via the fieldbus.
[4-1] * The PROFIBUS fieldbus driver can only be accessed via PLC (Logic/Motion). Access via EASY Starter and VisiWinNET®
Runtime is not provided.
Controllers and field devices form the automation system to be commissioned via the Engineering
PC. The Engineering PC is a PC/Laptop with Windows® operating system and network connection.
The Engineering PC comes installed with the Lenze Engineering tools ( 20) for parameter setting,
configuration, programming and diagnostics.
The Controller with the PLC (Logic/Motion) is the central control section, consisting of the PLC
runtime program (Runtime software of the Lenze Controllers ( 24)) with the running PLC
application.
Device-internally, the Controller comes with a data manager for configuring and managing the data
of the automation system. The data manager and the fieldbus driver enable the PLC (Logic/Motion)
to access the system components and the field devices.
The fieldbus (Logic/Motion) enables the Controller to read and write the parameters of the
connected field devices.
4 System structure
________________________________________________________________
 Note!
There is no OPC server available for PROFIBUS and PROFINET.
Controller c300/p300:
• The »EASY Starter« cannot be used for these devices (in preparation).
• The OPC communication for »VisiWinNET« is exclusively available for Controller p300
without PLC.
• Otherwise, only the Lenze "Logic&Motion" direct driver can be used for the data
exchange between »VisiWinNET« and PLC.
4 System structure
4.1 Engineering tools
________________________________________________________________
The Engineering PC is a PC/Laptop with Windows® operating system and network connection.
The Engineering PC comes installed with the Lenze Engineering tools which enable the desired
automation solution to be ...
• parameterised/configured;
• programmed;
• diagnosed.
4 System structure
________________________________________________________________
»EASY Navigator«: Starting the suitable Engineering tool
The Lenze Engineering software consists of the Engineering tools optimised for the respective
Engineering phase.
The »EASY Navigator« shows the Lenze Engineering tools installed on the Engineering PC. Start the
desired Engineering tool via the corresponding button:
The »EASY Navigator« ...

• simplifies the selection of the Engineering tool, depending on the Engineering phase.
• simplifies starting the desired Engineering tool (depending on the application case).
• makes it possible to select the Engineering tool suitable for the Engineering phase.
The overview displays the respective function of the Engineering tools:
What would you like to do? Button Engineering tool

Programming »PLC Designer«
• Program the controller
• Parameterise/commission the Servo-Inverter i700
• Parameterise the I/O system 1000
Parameterising/configuring the inverter »EASY Starter«
• Parameterise and configure the automation/drive
system
• Parameterise Inverter Drives 8400/Servo Drives 9400
Visualization »VisiWinNET«
• Visualise the applications of the automation system
• Create the visualisation/user interface
Online diagnostics »EASY Starter« 1)

• Easy online diagnostics of the Controllers (from»EASY (Reading parameters)
Starter« V1.2) and other Lenze devices
Online parameterisation »EASY Starter« 1)

• Online parameterisation/commissioning of Lenze (Reading/writing
devices parameters)
• Direct online parameterisation with an active online
connection to the Lenze devices
Engineering tools that are not included in the »EASY Navigator«:
Controller parameterisation/diagnostics »WebConfig«
• »WebConfig« can be used on the controller without
commissioning (integrated web server).
• By the use of »WebConfig«, the parameters of the
controller can be accessed via web browser.
• »WebConfig« can also be started in the »PLC Designer«.
Backup of controller data »Backup & Restore«
• Create data backups
• Restore data after device replacement
• Carry out software update of the Controller
1) For Controllers c300/p300 in preparation
4 System structure
4.2 Controller: The control centre of the Controller-based Automation
________________________________________________________________
Cabinet controllers: Compact control cabinet design

Cabinet controllers are designed for the demanding continuous use in industrial applications.
Compared to panel controllers, they are not equipped with an integrated display. The Controllers
3231 C and 3241 C are provided with a DVI interface for the connection of an external monitor
panel.
Mounting is carried out in a control cabinet or a corresponding built-in housing on a standard DIN
rail (35 mm). The device-internal backplane bus provides for a direct connection of the I/O system
1000.
Panel controllers: controlling and visualising

Panel controllers are designed for the installation into control cabinets, machine panels, or other
mounting cutouts. They are equipped with rear bolts and clamping screws which provide for easy
mounting and reliable sealing (front panel enclosure IP65/rear panel IP20) in rough industrial
environments. They can be operated easily by directly touching the screen.
General features
• Controller programming, configuration and diagnostics using the »PLC Designer« (on the basis
of CoDeSys 3.x)
• USB 2.0 interfaces and SD card slot, e.g. for data backup/restore
»Backup & Restore« (data backup/restore) ( 67)
• 4 LEDs for diagnostic purposes:
• Current supply
• Status of the PLC
• Status of the backplane bus
• Freely programmable LED
 Operating instructions for the Controller

Here, further information on the device-specific properties can be found.
4 System structure
________________________________________________________________
Fieldbus communication
The Lenze Controllers have different interfaces for fieldbus communication:
Area Cabinet Controller Panel Controller

c300 3221 C 3231 C 3241 C p300 p500
Interfaces (on board)
Ethernet 1 2 1 2
EtherCAT 1 1) 1 1 1) 1
CANopen 1 2) - 1 2) -
Optional interfaces (communication cards)
CANopen -  - 
MC-CAN2
PROFIBUS master -  - 
MC-PBM
PROFIBUS slave -  - 
MC-PBS
PROFINET device -  - 
MC-PND
1) In preparation
2) Only the CAN master functionality is supported.
The Ethernet interface serves to connect the Engineering PC or to create line topologies (no
integrated switch for Controller c300/p300).
 More information on the bus systems and configuration can be found in the
communication manuals:
4 System structure
4.3 Runtime software of the Lenze Controllers
________________________________________________________________
By default, the runtime software is installed in the Lenze Controller as "Logic" mode for the central
control of PLC applications.
Optionally, the "Motion" mode is available, additionally enabling extensive motion control of
Motion functions. The inverter then only acts as an actuating drive.
In addition, the "Visu" mode is available, enabling a central visualisation with the Controller.
The runtime software consists of:
• Operating system (Windows® CE)
• Software components (Logic/Motion), which for instance execute the control program.
• Optional visualisation software (»VisiWinNET« Compact CE).
Differences between "Logic" and "Motion"
Logic Motion
The controller controls... The controller controls extensive motion sequences.

• simple motion sequences; The runtime software "Motion" ...
• by logically combined control signals. • contains the PLCopen library;
• contains the "Logic" mode;
• supports "SoftMotion".
Logic applications are suitable for the control of inverters Motion applications are suitable...
without a Motion functionality which ... • for the control of inverters executing complex motion
• execute simple motion sequences; sequences of multi-axes in several dimensions;
• can only be controlled via PLC functionality. • ...for the control of devices that are to traverse
synchronously;
• for the transfer of setpoints.
 Note!
Depending on the runtime software (Logic/Motion) used, a bus system for a Lenze
device series can only be used in a limited way.
Details can be found in the communication manuals:
4 System structure
________________________________________________________________
4.3.1 "Logic" runtime software
"Logic" refers to the use of logically combined control signals without Motion functions. When the
"Logic" mode is used, the controller solely controls the motion sequences via logically combined
control signals.
Functionality
• Programming PLC functionality according to IEC 61131-3.
• SoftPLC functionality for executing PLC programs.
• The multi-tasking Windows® CE operating system processes the PLC
programs cyclically.
Performance
The "Logic" mode defines the program function. The performance of the entire
automation system results from the interaction of the runtime software and
the target system in each case. The system performance thus depends on the
processor of the respective controller, and on other factors.
Engineering tool required: »PLC Designer«
4.3.2 "Motion" runtime software
The "Motion" mode makes it possible to execute more complex motion sequences than with the
Logic mode.
In the case of a Motion system, the whole motion control (Motion) of the axes to be controlled takes
place in the controller. The higher-level controller generates the motion profiles for all Motion axes
and transfers the data to the axes via EtherCAT.
A Motion-application...
• ...makes special demands on the cycle time and real-time capability of the bus system between
the controller and the connected field devices.
• for instance is to be used if the axes to be controlled are to be traversed in a synchronised
manner or position setpoints are to be transmitted.
Functionality
• Motion functions according to PLCopen "Function blocks for Motion
Control" version 2.0
• Contains the "Logic" runtime software for the use of logically combined
control signals.
Additional functions
• Motion function blocks/libraries
• Supports programs for the control of complex motion sequences with
several axes.
Engineering tool required: »PLC Designer«
4 System structure
________________________________________________________________
4.3.3 "Visu" runtime software
The "Controller-based Automation" system enables the central visualisation of the automation
system.
The visualisation can either run on a separate Controller or monitor panel or on the Controller on
which the "Logic" or "Motion" runtime software is running.
Various options described in the following sections are available for the communication link.
Functionality
The "Visu" mode ...
• extends the Controller to a visualisation device;
• can be used separately or in addition to "Logic" or "Motion".
Engineering tool required: »VisiWinNET«
 Note!
without PLC.
4 System structure
________________________________________________________________
4.3.3.1 Sample topology 1: External monitor panel/display for cabinet controllers
[4-2] Sample topology: Controller 3231 C with an external monitor panel (connected to the DVI interface)
This topology with regard to its performance corresponds to the implemented solution (control/
visualisation on the same controller). The external monitor panel/display shows the visualisation.
Advantages
• Small amount of cabling
• Protected operating conditions
• Extensible topology
• No impact on the real-time capability of the fieldbus by the visualisation
4 System structure
________________________________________________________________
4.3.3.2 Sample topology 2: Separate control and visualisation
[4-3] Sample topology: Controller 3200 C as gateway for the Visualisation Controller (IPC)
The Visualisation Controller (IPC) accesses the field devices via the Controller 3200 C as gateway.
In order to separate the control and visualisation, the integrated gateway function of the controller
can be used.
The use of this topology is advisable...
• to achieve a higher performance;
• for the use of different operating systems within one automation system.
Engineering tools required: »EASY Starter«, »Engineer«
Advantages
• No impact on the real-time capability of the fieldbus by the visualisation.
• Several visualisations can access the controller.
• Most suitable for extensive visualisation processes.
 Note!
In case of Controller c300/p300, the gateway function is not supported (in preparation).
4 System structure
________________________________________________________________
4.3.3.3 Sample topology 3: Independent control and visualisation (CANopen)
[4-4] Sample configuration: Parallel access of Controller 3200 C and Visualisation Controller (IPC)
If this topology is used, the Controller 3200 C and the Visualisation Controller (IPC) access the
fieldbus independently of each other.
 Note!
The configuration with a control and configuration independent of each other is only
available for the CANopen bus system!
• CANopen enables (several) fieldbus master independent of each other.
• In connection with EtherCAT, no configuration with two fieldbus masters is possible.
Advantages
• Spatially separate control and visualisation.
• The visualisation has access to the parameters of the field devices.
Disadvantage
• The visualisation may disrupt the real-time capability of the fieldbus. This topology therefore is
only suitable for Motion systems to a limited extent (depending on the bus system used).
5 Commissioning the controller
________________________________________________________________

This chapter provides some general information on the commissioning of a controller. Depending
on the actual hardware installed, different settings are required for integrating the controller into a
network.
 Note!
Please observe the predefined IP address of the controller for the initial commissioning:
192.168.5.99 (Lenze setting).
Further information on how to set the IP address of the Controller can be found here:
Entering the IP address of the controller ( 33)
 Read the mounting instructions supplied before you start working!

The mounting instructions contains safety instructions which must be observed!

Here, further information on the device-specific properties can be found.
5.1 Identification
________________________________________________________________
5.1 Identification
 Note!
Here the documentation provides some general information about the commissioning
of a controller. Depending on the design and version of the controller, the
commissioning process can be different.
Every controller is provided with a nameplate containing the device data. The device data are
helpful for identifying the technical equipment of the controller. Detailed information relating to
the nameplate data can be found in the operating instructions for the Controller.
Web-based diagnostics/parameter setting

Via »WebConfig« the configuration of the controller can be identified. The parameter values of the
controller can be represented using the web browser.
Online connection from the Engineering PC to the controller ( 46)
Assigning a unique name to the controller

In order to be able to clearly identify a Controller, the desired name has to be assigned for parameter
13 System identification: Name C0013. The name assigned can then be used in the corresponding
Engineering tool (e.g. »PLC Designer«), in order to be able to identify the controller.
5.2 Control elements of the controllers
Depending on the equipment and type, the different device series are provided with various control
elements (e.g. function keys for external monitor panels) and status LEDs for diagnostic purposes.
Status LEDs of the Controllers ( 80)
The controllers can be operated via external input devices (keyboard/mouse). This makes it possible
to carry out comprehensive diagnostics and configuration tasks directly on the controller.

Here, further information on the device-specific properties of the Controller can be
found.
5.3 Starting the controller
________________________________________________________________
5.3 Starting the controller
 Note!
During the starting process of the controller
If a non-bootable USB flash drive is connected during the starting sequence, it will be
stopped!
• Remove the USB stick and restart the Controller.
• Alternatively, the USB stick can be prepared using the »Backup & Restore« software.
Further information can be found in the online help of the »Backup & Restore«
software.
When the controller is running
Removal of the SD card will lead to a system failure!
• The SD card must not be removed while the controller is running (no "Hot Plugging"
of the SD card possible).
• The SD card is required for the system start since it contains the system files for the
starting process.
The SD card and the internal flash memory are the storage media of the controller. Depending on
the device, the SD card can be used optionally. Detailed information can be found in the device-
specific operating instructions.
The 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 standard-IP address of the controller is 192.168.5.99 (Lenze setting)
The preset IP configuration can be changed in the »WebConfig«.
Setting IP addresses on the Engineering PC (example: Windows® XP) ( 46)
After 15 seconds, the network configuration dialog box will close automatically; the
controller continues with the starting process.
Error case: Controller c300/p300 does not start

In case the Controller c300 or p300 does not start, the Lenze standard settings can be activated
using the reset pushbutton.
 How to activate the Lenze standard settings:

1. Switch off voltage supply.
2. Press reset pushbutton.
3. While pressing the reset pushbutton, switch on the voltage supply and keep the reset
pushbutton pressed for at least 10 s.
• If the error LED is blinking (green/red) after this action, a manual mains switching is
required.
• The Controller has to be disconnected from the mains until all LEDs go off.
5.4 Configuring the controller
________________________________________________________________
This chapter provides information on how to configure the Controller during initial commissioning.
The IP address setting is preserved after a restart of the system.
5.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 ( 79)
In order to carry out a remote maintenance on the controller different mechanisms are provided:
Diagnostics via Telnet ( 82)
Data transfer via FTP ( 85)
Activate Windows® CE interface ( 92)
Diagnostics with the logbook ( 89)
 Note!
• These devices come with a deactivated Telnet and FTP in the Lenze standard setting.
• The functions can be activated via the »WebConfig«. The activation of the functions
can influence the real-time behaviour.
• After a restart of the Controller, the functions are deactivated again.
5.4.2 Entering the IP address of the controller
The controller has the following network settings by default:
Address Lenze setting

IP address 192.168.5.99
Subnetwork 255.255.255.0
Default gateway 192.168.5.1
During initial commissioning of the Controller, the desired IP address has to be entered.
Optionally, the network settings can be selected via a file:
Specifying the IP address of the controller via file (optional) ( 36)
________________________________________________________________
5.4.2.1 Cabinet controllers with external monitor panels (3231 C/3241 C)
 Note!
If an external display (monitor panel) is used, the switch-on sequence of display/
controller must be observed so that it can be correctly controlled by the controller:
• Connect the external display to the DVI output of the controller and switch it on
before switching on the controller.
After connection of a monitor panel/an external display to a running controller, the
display resolution is VGA .
• Calibrate the monitor panel/ display connected, so that the screen content can be
displayed correctly.
 Tip!
Connect a keyboard to the Controller to be able to enter the IP address.
Then you can make the entries:
[5-1] IP settings of the 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.
________________________________________________________________
5.4.2.2 Cabinet Controller without external monitor panel (c300/3221 C)

To configure a Cabinet Controller without a connected monitor panel (e.g. Controller 3221 C), a PC/
laptop with the suitable addresses (IP address, subnet mask, default gateway) is required.
• Connect the PC/laptop to the controller by means of a "crossed" network cable.
• Change the settings on an HTML compliant browser:
Setting IP addresses on the Engineering PC (example: Windows® XP) ( 46)
• Connection establishment: enter the IP address of the controller in the browser: 192.168.5.99
(Lenze default setting).
• In »WebConfig«, click the Ethernet button.
• Enter the desired IP address, subnet mask and default gangway of the 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.
________________________________________________________________
5.4.3 Specifying the IP address of the controller via file (optional)
 How to proceed:
1. Create file "ip.txt" on the Engineering PC.
2. Save file "ip.txt" to the SD card of the controller by connecting the SD card to the
Engineering PC using a memory card reader.
File "ip.txt"
172.31.207.88 {IP address}

255.255.255.0 {subnet mask}
172.31.201.1 {gateway}
[5-2] Example of an "ip.txt" file for selecting the IP address
In ASCII file "ip.txt" an IP address is defined which can be selected for the controller.
• Copy file "ip.txt" to the root directory of the SD card.
• Insert the SD card into the controller. Then start the controller.
Starting the controller ( 32)
• When the system is started ...
• the controller reads in the IP address file "ip.txt" from the SD card;
• the controller writes the result (Result) to the ip.txt file:
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.

[5-3] Example of an "ip.txt" file for IP address selection with result entry
• Then, the Controller 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.
________________________________________________________________
5.4.4 Establishing Windows® CE access rights
In order to be able to establish a connection to the 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 »WebConfig« and the »EASY Starter«:
Setting up Windows® CE users in »WebConfig« ( 37)
The representation for user 1 is displayed. The users 2 to 10 are displayed analogously.
5.4.4.1 Setting up Windows® CE users in »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 »WebConfig« the User management 10 area.
• Use parameters 101 to 169 to set up the user name, password, and various authorisations for a
maximum of ten users.
The representation for user 1 is displayed. The users 2 to 10 are displayed analogously.
Detailed information on the parameters can be found here:
Basic parameters of the Controllers 3200 C/c300 and p300/p500 ( 131)
________________________________________________________________
5.4.5 Using your own wallpaper on the controller (Windows® CE)
The standard wallpaper of the controller can be replaced by your own wallpaper.
The wallpaper must meet the following conditions:
• File format: bitmap (*.bmp)
• The resolution of the image must correspond to the resolution of the monitor panel to achieve
a correct representation:
Screen sizes Panel Controller

p300 p500
Diagonal 10.9 cm 17.8 cm 26.4 cm 17.8 cm 26.4 cm 38.1 cm
measurement (4.3") (7.0") (10.4") (7.0") (10.4") (15.0")
Resolution [pixel] 480 x 272 800 x 480 800 x 600 800 x 480 800 x 600 1024 x 768
(PSP) (WVGA) (SVGA) (WVGA) (SVGA) (XGA)
 How to proceed:
Copy the desired bitmap file to the SD card of the controller, directory: \CustomBitmap.
Directory name on the controller if the SD card has been inserted into the controller:
\USBStorage\CustomBitmap)
5.5 I/O system 1000 at the backplane bus of a cabinet controller
________________________________________________________________
The Cabinet Controllers 3200 C and c300 allow for a direct connection of the I/O system 1000 to the
integrated backplane bus.
The modules of the I/O system 100 connected to the backplane bus of the Controller can be
parameterised in the »PLC Designer«.
 System manual for I/O system 1000 (EPM-Sxxx)

Here, further information on the parameter setting/configuration can be found.
5.5.1 Configuring I/O modules at the backplane bus
The following illustration is a schematic representation of the controller hardware structure

including I/O modules.
The I/O system 1000 includes the following components:

• I/O module coupler for voltage supply of the I/O compound modules
• I/O compound modules:
Up to 64 modules are possible which are connected to the Controller 3200 C via the Lenze
backplane bus.
In order to be able to access the modules by means of a PLC program (read input signals/write
output signals), the modules have to be configured in the »PLC Designer«. For this, map the physical
arrangement of the I/O modules in the »PLC Designer«.
[5-4] Example: mapping the physical arrangement of modules 1...7 in the »PLC Designer«
________________________________________________________________
 How to configure the I/O modules in the »PLC Designer«:

1. Append the I/O modules used as Devices to the I/O module coupler:
Note: The sequence of the I/O modules in the device tree must comply with the physical
arrangement.
2. View in the device tree/Device view:
• 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.
________________________________________________________________
Use the I/O module coupler tab for diagnostics purposes using the PLC application.
Example: Insert the b_myError variable in this tab. The variable is globally declared and the PLC
application is able to evaluate it.
5.5.2 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).
For this purpose, execute the Start Search command in the context menu of the I/O module coupler:
5.6 Tabs of the I/O modules at the backplane bus
________________________________________________________________
5.6 Tabs of the I/O modules at the backplane bus
The Workspace ...

• uses various tabs to display the properties and settings of the module selected from the Device
view.
• serves to edit the parameters of the individual I/O compound modules.
Depending on the module selected from the Device view, different tabs are available in the
Workspace.
I/O module coupler (backplane bus)
Tab Contents
Diagnostics Error status of the modules.
Error messages (backplane bus) ( 43)
I/O module coupler List of all available objects for the parameter setting of the I/O compound
modules - digital I/O.
Status Status information of the module coupler.
Information Project information and catalogue information of the module coupler.
Every I/O module at the backplane bus is represented by means of the following tab:
I/O compound modules
Tab Contents
Parameter • Offline configuration of the I/O module
• All parameters of the I/O compound module
• Parameterising digital modules:
Polarity of the control signals, status in the event of an error for digital
output modules.
• Parameterising analog modules:
Signal functions, status in the event of an error.
Depending on the type of I/O module, specific settings are possible.
Further information is provided in the online help of the I/O system 1000.
I/O module image Process image of the I/O module
Status Status information of the I/O compound module.
Information Designation and connection diagram of the I/O compound module.
5.7 Error messages (backplane bus)
________________________________________________________________
Error messages are represented on the Diagnostics tab of the I/O module coupler.
[5-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
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
107 Write semaphore timeout for group 1
110 Internal error of the backplane bus hardware
• Contact Lenze
________________________________________________________________
Error number Error text/remedy

136 Configuration error in the I/O module topology.
137 Too many tasks for the processing of I/O modules. Three tasks at the maximum.
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
6 Parameter setting using »WebConfig«
6.1 System structure
________________________________________________________________

This chapter contains some information about the web-based parameterisation of the controller via
»WebConfig«.
6.2 Parameterising the controller
All settings that can be used for parameterising the controller are included in a numbered
parameter list.
»WebConfig« can be remotely called via http by an external Engineering PC which can be reached
via network. The Engineering PC is a desktop computer with a Windows® (XP/7) operating system.
6.3 Online connection from the Engineering PC to the controller
________________________________________________________________
6.3 Online connection from the Engineering PC to the controller
Connect the Engineering PC to the Controller using a network cable or connect the Controller to the
network which is accessed to the Engineering PC.
 Note!
In the case of a direct connection between the Engineering PC and the 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 controller.
6.3.1 Setting IP addresses on the Engineering PC (example: Windows® XP)
 Note!
Recommended setting for the Engineering PC:
IP address: <192.168.5.100>
Default settings of the controller:
IP address: <192.168.5.99>, subnetwork <255.255.255.0>.
Setting for the direct connection between Engineering PC and controller:
 How to set the static IP address of the Engineering PC:

1. Open the Network connections dialog box.
StartSettingsNetwork connections
2. Select the network interface which is connected to the Controller.
Right-click Properties.
3. Select Internet protocol (TCP/IP).
4. Click the Properties button.
5. Select the Alternate configuration tab.
6. Select the User configured option.
• Enter the IP address. The subnet range of this IP address and the one of the IP address of
the controller must be the same, example: <192.168.5.100> (Lenze setting of the
controller: <192.168.5.99>).
• Enter the subnet mask of the Engineering PC (standard setting: <255.255.255.0>)
7. Close the individual dialog boxes with OK/Close.
6.4 Start »WebConfig«
________________________________________________________________
The Properties of internet protocol (TCP/IP) dialog window
 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 controller: <;192.168.5*> (Lenze setting)
5. Close the individual dialog windows with OK.
6.4 Start »WebConfig«
Start a browser at the Engineering PC and enter the IP address of the controller.
1. Enter <User name:password>. As default

setting, admin:admin is preselected. Any
user set up on the controller can log in.
User management ( 55)
2. Confirm with OK .
3. Afterwards, »WebConfig« is visible.
User interface of »WebConfig« ( 48)
6.5 User interface of »WebConfig«
________________________________________________________________
The user interface of »WebConfig« is divided into the following areas  - :
 Note!
The representation of the user interface in area  depends on the respective system
configuration!
________________________________________________________________
Area Information
Menu buttons  Device parameters of the controller ( 50)
• Parameter list 1: All parameters of the standard device
• Parameter list 2: All parameters of the installed communication cards
• PLC parameters
• Ethernet (on board) parameters
• EtherCAT parameters
 Diagnostic/device commands ( 51)
• Logbook parameters
• Logbook of the controller
• Device commands
 User management ( 55)
... for settings of the users 1 - 10
 General parameters ( 55)
• Time
• UPS settings
• Monitoring functions
• Memory
• Diagnostics
 »Backup & Restore«
... for carrying out a backup, restore or software updates
Detailed information on the parameters of the »Backup & Restore« can be found here:
Backup&Restore ( 174)
Further information on how to carry out a backup, restore or software updates can be
found in the »Backup & Restore« software manual.
 Parameters of the communication cards ( 56)
Note:
• The represented parameters of slots 1 and 2 depend on the corresponding
communication cards that are installed!
• The additional buttons for the actually installed communication cards are
automatically added to the menu buttons.
• The top-down order of the buttons corresponds to the order in which the
communication cards have been installed (slot 1, slot 2).
Detailed information on the parameters of the communication cards can be found

here:Communication cards: optional interface ( 178)
 Automatic update ( 57)
 Language selection ( 57)
Buttons  Parameter list buttons ( 57)
Display area  Parameter display
Depending on the selected menu button, the parameters can be viewed in this area.
• Parameter numbers
• Name of the parameter
• Representation of the display, entry, selection, control and list fields.
Depending on the equipment of the controller, deviating components are shown by use of the
menu control fields.
Detailed information on the parameters of the Controller can be found here:
________________________________________________________________
Representation of parameter values

In the display area of »WebConfig«, 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.5.1 Device parameters of the controller
Button Function
Displays all parameters of the standard device of the 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.
The other menu buttons of the areas , and  are a filtered view of
parameter list 1.
Displays all parameters of the installed communication cards in numerically
Parameter list 2 ascending order.
The top-down order of the parameters corresponds to the order in which the
communication cards have been installed (slot 1, slot 2).
Detailed information on the parameters of the communication cards can be
found here:
Parameters of the communication cards ( 56)
Communication cards: optional interface ( 178)
The other menu buttons of area are a filtered view of parameter list 2.
Displays the PLC parameters in numerically ascending order.
PLC From this user interface can e.g. be seen:
• The PLC status,
• Information on a PLC project.
Detailed information on the parameters of the PLC can be found here:
PLC (Logic/Motion) ( 172)
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.
Detailed information on the EtherCAT parameters can be found here:
Ethernet (on board) ( 161)
Displays the EtherCAT parameters (information on EtherCAT master and
EtherCAT EtherCAT slaves).
Detailed information on the EtherCAT parameters can be found here:
EtherCAT ( 163)
________________________________________________________________
6.5.2 Diagnostic/device commands
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 Controller can

be found here:
Remote maintenance and diagnostics ( 79)
Displays logbook contents.
Logbook • Different filter settings display, for instance, only the oldest or only the
most recent logbook entries.
Logbook ( 52)
Displays the commands of the Controller to be executed.
Device commands The available commands can be found in the following section under
18 (C0018)
________________________________________________________________
6.5.3 Logbook
This user interface displays the logbook information of the Controller.

The logbook offers various filter options to systematically display specific logbook contents.
 Note!
If the ClearLog button is clicked, the entire logbook contents of the controller are deleted
without further query!
6.5.3.1 Structure of a logbook entry: example
Logbook entry, example Meaning

00001 Consecutive number of the entry
2009-03-24 14:45:26 Date (year/month/day) and time (hour/minute/second) on the
Controller when the logbook entry was made
Log service Application that has triggered the entry (application)
Logbook deleted Description of the event
Continuous processing Event origin within the application (area)
Warning Severity of the event
________________________________________________________________
6.5.3.2 Filter options
Section Information
Logbook Display logbook entries
Structure of a logbook entry: example ( 52)
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 severity
selected.
• The "Information" severity is deactivated by default. In order to show all
logbook entries, the "Information" option is to be activated
Area Set filter for the origin of the event
• The logbook will only display entries that correspond to the selected area.
6.5.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 specification for filtering the
• Date (year/month/day) entries to be displayed
• Time (hour/minute/second) • 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 specification for filtering the
• Date (year/month/day) entries to be displayed
• Time (hour/minute/second) • 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!
________________________________________________________________
6.5.3.4 Saving log files with mains failure protection

The log files are persisted automatically at certain events.
You can also persist the log files manually by means of the »EASY Starter« and »WebConfig«.
 How to proceed:
1. Click the Device commands button.
2. Select the entry "1282: Persist logbook" from the Commands list field.
3. Click the Accept button.
OK appears in the "Status" field.
6.5.3.5 Export logbook entries
 How to export the logbook entries to a text file (without using the »EASY Starter«):
1. Establish online connection to the controller.
2. Available logbook entries can be seen on the Logbook tab.
3. Click the ExportLog button in the header of the logbook to export the logbook entries to a
file.
The content of the logbook is exported to a German (*_de) and an English file (*_en) to the
memory card in the \USBStorage\export\log directory (The directory is already
preinstalled on the SD card by default).
• Note: The contents of the logbook can also be exported to a USB stick (connected to the
Controller). To be able to export the contents of the logbook to the USB stick, the
\export\log directory must be created manually on the USB stick prior to export.
• When the ExportLog button is clicked, the Controller writes the contents of the logbook
to the SD card and to the USB stick (directory: \USBStorage2\export\log).
• The execution of an ExportLog is entered into the logbook as Information. (Entries of the
Information type can only be seen in the logbook if the corresponding filter option is set
in the Logbook.)
Export logbook entries via device command

The logbook export can also be started by writing to command parameter 18 (C0018) via PLC or
»VisiWinNET®«.
In the section Device commands (parameter 18), execute the 304: Export complete logbook
command to export the logbook entries.
________________________________________________________________
6.5.4 Device commands
In this area, the available device commands of parameter 18 (C0018) can be executed.
Parameter 19 (C0019) shows status information relating to the executed command.
Saving parameters of the controller

The parameters of the controller can be saved with the Persist all data device command.
 How to proceed:
1. Click the Device commands button.
2. Select the entry "279: Persist all data" from Commands list field.
3. Click the Accept button.
OK appears in the "Status" field.
6.5.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.5.6 General parameters
Button Function
Displays the parameters for setting the time, date, system time, and time
Clock zone.
Shows the UPS settings for the parameterisation of the UPS (provided
UPS settings depending on the device/with UPS option).
Displays hardware/temperature data.
Monitoring functions
Displays information on program/Flash memories.
Memory
Displays information on system diagnostics.
Diagnostics
________________________________________________________________
6.5.7 Parameters of the communication cards
This area of »WebConfig« displays the parameters of the installed communication cards. The
following communication cards can be used:
• MC-CAN2
• MC-PBM (PROFIBUS master)
• MC-PBS (PROFIBUS slave)
• MC-PND (PROFINET)
A distinction is drawn between:
• Interface parameters,
• Communication card parameters.
A communication card can be equipped with several interfaces, such as the MC-CAN2
communication card.
CAN (MC-CAN2) communication card / CAN interface for Controller c300/p300 ( 179)
PROFIBUS and PROFINET communication cards ( 185)
6.5.7.1 CAN communication card (MC-CAN2)

The MC-CAN2 communication card ...
• has two CAN connections/interfaces;
• is not supported by the Controllers c300/p300.
The Controllers c300/p300 only support the CAN master functionality.
 Note!
The parameters are only visible if the MC-CAN2 communication card is installed. For
each Controller, a maximum of one communication card can be used.
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 communication card
MC-CAN2 interface x 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.
found here:
CAN (MC-CAN2) communication card / CAN interface for Controller c300/
p300 ( 179)
________________________________________________________________
6.5.7.2 Optional PROFIBUS/PROFINET communication cards
Button Function
MC-PBM: Parameter of the PROFIBUS master card communication card.
MC-xxx MC-PBS: Parameter of the PROFIBUS slave card communication card.
MC-PND: Parameter of the PROFINET communication card.
In this user interface, the parameters of an optional communication card are
visible if it is installed in the controller.
found here:
6.5.8 Automatic update
In this menu, the automatic, interval-controlled update of the screen content can be activated:
Interval:
Specify period in seconds, defining the intervals in which the screen content is
automatically updated; example value: 5, update every five seconds.
Active:
Tick the checkmark () to activate the automatic update.
6.5.9 Language selection
The desired language settings can be selected in the Language section.

The language settings take immediate effect.
6.5.10 Parameter list buttons
Button Function
Accept Accept data.
After a system restart changed data is lost, as it is 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 content.
7 Programming with the »PLC Designer«
________________________________________________________________
This chapter provides you with general information on the programming of

the control function of the controller.
The »PLC Designer« is a Lenze Engineering tool for the creation of PLC
programs according to IEC 61131.
The following programming languages can be used:
• Instruction list (IL),
• Ladder diagram (LD),
• Function block diagram (FBD),
• Structured text (ST),
• Sequential function chart (SFC),
• Function block diagram (CFC).
The completely created and compiled PLC program can be transferred to the
controller by means of the »PLC Designer«.
The PLC program can then be executed on the controller by the runtime
software (Logic/Motion).
 Note!
In the »PLC Designer«, the configuration/parameter setting of field devices below the
Controllers c300/p300 is only possible "offline".
________________________________________________________________
Install the »PLC Designer« on the Engineering PC. Via Ethernet, the »PLC Designer« accesses the
Controller:
7.2 Function blocks
________________________________________________________________
7.2 Function blocks
The »PLC Designer« contains function blocks which enable the PLC program to directly access the
parameters of the Controller and the connected field devices.
Parameters which can be accessed are ...
• device parameters or logbook entries of the Controller;
• device parameters of the field devices (example: Servo Inverter i700).
Memory sizes of the controllers
Memory area/data Value

Total RAM memory 3221 C: 1 GB DDR2-RAM
(Program memory/data memory) 3231 C:
3241 C:
c300: 512 MB DDR3-RAM
p300: 512 MB DDR3-RAM
p500: 1 GB DDR2-RAM
Retain and persistent data 3221 C: 60 kB
3231 C:
3241 C: 1 MB (with external battery pack/capacitor pack)
c300: 128 kB
p300: 128 kB
p500: 1 MB
Fixed memory (flash) 2 GB
Flag 4 kB
Maximum number of tasks 32
Shortest task time 3221 C: 1 ms
3231 C:
3241 C:
c300: 2 ms
p300: 2 ms
p500: 1 ms
Maximum input / output area 8 kB
Operating systems of the Controllers
Operating systems
Cabinet Controller c300 3221 C 3231 C 3231 C
Windows® Windows® CE 6.0 Windows®
Embedded Compact Embedded Standard
7 2009
Panel Controller p300 p500
Windows® Embedded Compact 7 Windows® CE 6.0
The operating systems and the PLC applications use the available RAM memory area of the
Controller together (see above).
7.3 Configuring and parameterising the controller using the control application
________________________________________________________________
7.3 Configuring and parameterising the controller using the control application
For the creation of a control application, Lenze provides function blocks in standardised libraries
(e.g.: motion functions according to PLCopen). Further function blocks can for instance be used to
access controller parameters.
By means of the »PLC Designer«, the compiled PLC program has to be loaded to the controller via
Ethernet, where it processes the operating system.
7.4 Controller c300/p300: Access to odd Controller addresses
________________________________________________________________
 Note!
Due to the processor type (Cortex™-A8), write/read access of variables is only possible to
memory addresses that are divisible by the variable size.
Examples:
• When variables of the DWORD/DINT data type are accessed (read/write), the memory address
must be divisible by 4.
• When variables of the WORD-/INT data type are accessed (read/write), the memory address
must be divisible by 2.
Access to other memory addresses causes exception handling of the runtime (exception).
Different response of the PLC program (3200 C/p500 and c300/p300)

1. In the case of the Controllers 3200 C/p500 with x86 processors, unlimited access to the memory
addresses is possible. Due to the different processor (Cortex™-A8), PLC programs cause
exception handling of the runtime on the Controllers A8c300/p300, although they run without
fault on the Controllers 3200 C/p500.
PROGRAM PLC_PRG
VAR
aByteArray : ARRAY [0..20] OF BYTE;
dwDword : DWORD;
wWord : WORD;
pDwordPtr : POINTER TO DWORD;
pWordPtr : POINTER TO WORD;
END_VAR
// Prerequisite: pDwordPtr is divisible by 4

// DWORD-access to an address which is not divisible by 4 => crash on ARM
// processor
pDwordPtr := ADR(aByteArray[2]);
dwDword := pDwordPtr^;
// WORD-access to an address which is not divisible by 2 => crash on ARM

// processor
pWordPtr := ADR(aByteArray[1]);
pWordPtr^ := wWord;
________________________________________________________________
2. In the case of many functions/function blocks, a pointer is transferred to a byte array and then
the content of the byte array is for instance interpreted as DWORD. This requires manual
conversion before the data are used:
PROGRAM PLC_PRG
PROGRAM PRG_Logic
VAR
mySDO_READ : CIA405.SDO_READ4;
aReadData : ARRAY [1..4] OF BYTE;
dwDword : DWORD;
END_VAR
mySDO_READ(NETWORK:= 1,
ENABLE:= TRUE,
TIMEOUT:= 10000,
CONFIRM=>,
ERROR=> ,
DEVICE:= 1001,
CHANNEL:= 1,
INDEX:= 16#5FE7,
SUBINDEX:= 0,
DATA=> aReadData,
DATALENGTH=>,
ERRORINFO=>);
// Manually create a DWORD from a Byte array

dwDword := aReadData[1]
+ 256 * aReadData[2]
+ 65536 * aReadData[3]
+ 16777216 * aReadData[4];
General information about the use of pointers can be found in the "Pointer" section.
7.5 Creating remanent variables (retain/persistent)
________________________________________________________________
Retain variables ...

• are variables of the PLC which are automatically saved by the controller in the case of a voltage
failure.
• are variables which are necessary to restart the production process.
The values of a drive system which cannot be read out from the machine due to the lack of a sensor
system should be persistent. These values should also be persistent if the corresponding value only
changes through the influence of the PLC.
Examples
Temperature: Changes, requires a sensor system
Position: Selection preferably via absolute value encoder
Number of parts within buffer inventory: Reasonable for RETAIN.
VAR RETAIN
remvar1: INT; (* 1st remanent variable*)
END_VAR
Persistent variables ...

can be created in the device tree in the »PLC Designer«:
Right-click ApplicationNew object Persistent variables.

VAR_GLOBAL PERSISTENT RETAIN
uiPerRetain : ARRAY[0..1000] OF UNIT; (* declaration of the persistent variable*)
END_VAR
 »PLC Designer« Online help

Further information on remanent variables can be found in the "remanent variables"
section.
Further information on the export of symbol files can be found in the "Symbol
configuration editor" section.
________________________________________________________________
7.5.1 Storage of retain data on the SD card (only Controllers 3221 C/3231 C)
For Controllers 3221 C/3231 C, the values of the RETAIN variables are by default saved to the device
only.
• Use the L_Util_Retain function (from the L_Util.lib library) to save the RETAIN values to the SD
card of the controllers. Like this, the retain data can then be re-used, for instance after a device
replacement.
• RETAIN values saved to the SD card offer the benefit of subsequent use of these values after a
device replacement (subsequent use of the SD card).
 Note!
The SD card is only suitable for storing retain data if the RETAIN values do not change
very often.
• It is not possible to save the RETAIN values to the SD card during every PLC cycle.
• SD cards only have a limited number of write/read cycles. Thus, the retain variables
should not be saved at very short time intervals.
• Please avoid calling the L_Util_Retain() function in a motion task. The creation of the
RETAIN file prolongs the current PLC cycle of the calling task by several 100 ms.
• The functions SysSaveRetains() and SysRestoreRetains() provided in the
SysPlcCtrl23.Library are not supported and must not be used.
L_Util_Retain
Function Library Function

L_Util_Retain() L_Util.library Save retain data to the SD card of the
controller.
PROGRAM PLC_PRG
VAR
FB_LUtilRetain: L_Util_Retain;
xRetainsIntoFile_LUtilRetain: BOOL;
instSetRetainValues: SetRetainValues;
xSetRetain: BOOL;
xStoreRetains_LUtilRetain: BOOL;
END_VAR
[7-1] Program example: Use of the L_Util_Retain function
When being called, the L_Util_Retain function saves the retain/persistent variables to the SD card
to file: retains.ret (directory: IPC\PLC).
 Note!
Device replacement: Avoiding the loss of retain data
The L_Util_Retain function is only required for the Controllers 3221 C/3231 C.
• Use the L_Util_Retain function in the desired application in order to be able to re-use
the retain data, if required.
• In the event of a device replacement, the L_Util_Retain function must already have
been used in the application before, since otherwise the retain data are deleted.
________________________________________________________________
Re-using remanent variables after a device replacement

• A device replacement involves the insertion of the SD card of the replaced controller into the
new device.
• The boot application starts with the RETAIN values saved last by L_Util_Retain.
• When the PLC is started, the RETAIN file is created once. Set xStoreRetains to create the RETAIN
file once again.
8 »Backup & Restore« (data backup/restore)
________________________________________________________________
8 »Backup & Restore« (data backup/restore)

The Lenze »Backup & Restore« software makes it possible to ...
• create backups (data backup);
• restore backups (data recovery);
• install updates (update of the software/firmware of the Controller, only available for control
technology).
 Online help for »Backup & Restore«

Here, further information can be found.
9 Data integrity in the event of a voltage failure
9.1 UPS functionality of the controllers
________________________________________________________________
Controller UPS functionality Saves backup files to ...

3221 C Internal capacitor for the short-time buffering of MRAM (Magnetoresistive Random Access
data Memory)
3231 C
3241 C External battery pack (ACCU-PACK) or capacitor Memory card
pack (CAPS-PACK)
c300 Internal capacitor
p300
p500
9.1.1 Internal UPS (for Controllers without UPS connection)
In case of a voltage failure, retain/persistent variables, logbook data and visualisation data (e.g.
trends alarms) are saved.
The Controllers 3221 C/3231 C have an internal buffer capacitor for the short-time buffering of the
data.
The Controllers c300/p300/p500 are equipped with a high-capacity, internal UPS for the storage of
data in the event of a voltage failure. This makes external energy storage dispensable. Voltage
fluctuations cannot be compensated for.
The UPS behaviour of the internal UPS is preset. Parameter setting is not possible/required.
________________________________________________________________
9.1.2 External UPS (for Controllers 3241 C with UPS connection)
The Controllers 3241 C provide for the connection of an external battery pack (ACCU-PACK) or
capacitor pack (CAPS-PACK) to the X9 socket. Thus, voltage fluctuations of up to five seconds can be
compensated for.
In the case of a voltage failure, the external UPS saves the following content to the memory card of
the Controller 3241 C:
• Retain/persistent variables of the PLC
• Logbook data
• Visualisation data (e.g. trends, alarms)
When the data have been saved, the PLC stops. The log service does not accept any further log
messages and deactivates itself.
The UPS behaviour of the external UPS can be parameterised via »WebConfig«:
Parameter setting using »WebConfig« ( 45)
Detailed information on the parameters of the UPS can be found here:
Voltage buffering by external UPS (optional, for Controller 3241 C) ( 158)
9.2 Storage of »VisiWinNET® Smart« visualisation data
________________________________________________________________
9.2 Storage of »VisiWinNET® Smart« visualisation data
The Controllers 3231 C cyclically store »VisiWinNET® Smart« visualisation data (user-specific trends,
alarms, recipes) every 60 seconds.
 Note!
Controller 3231 C:
Depending on the time of occurrence of the voltage failure, the data saved last may be
out-of-date by up to one minute.
There is a time period of one minute between two storage processes. Hence, the saved
visualisation data is not exactly up-to-date after a voltage failure.
In the event of a voltage failure, the Controllers 3241 C store the »VisiWinNET® Smart« visualisation
data (user-specific trends, alarms, recipes) exactly isochronously to the SD card.
In the event of a voltage failure, the Controllers c300/p300/p500 store the »VisiWinNET® Smart«
visualisation data (user-specific trends, alarms, recipes) exactly isochronously to the memory card.
This is made possible by the high-capacity, integrated UPS.
9.3 Storage of retain/persistent variables of the PLC
________________________________________________________________
9.3 Storage of retain/persistent variables of the PLC
For the storage of retain/persistent variables, a defined storage capacity is available:
Controller Storage capacity

3221 C 60 kB
3231 C
3241 C 1 MB (with external battery pack/capacitor pack)
c300 128 kB
p300 128 kB
p500 1 MB
 Tip!
You can create retain variables in the »PLC Designer« by marking the variables with the
keyword RETAIN.
Further information on how to create retain variables in the »PLC Designer« can be found here:
Creating remanent variables (retain/persistent) ( 64)
10 Device replacement - replacing the controller (in the event of
service)
________________________________________________________________
10 Device replacement - replacing the controller (in the event of service)
Condition
Principally, a defective Controller can only be replaced by a device of the same product type.
Which replacement device is suitable for the Controller? ( 73)
10.1 Removing the connected (defective) controller
 Danger!
High electrical voltage
De-energise the controller before removing a connected controller.
 Mounting instructions for the Controller or I/O system 1000 (EPM-Sxxx)

Here, further information on mounting can be found.
Observe the safety instructions contained therein!
 How to remove the connected controller:

1. Disconnect the system from the supply and check for correct disconnection.
2. Disconnect the current supply of the controller.
3. If I/O modules (I/O system 1000) are connected to the Controller:
Remove electronic module of the first I/O system 1000 (if available)
4. Remove bus connections and other connections.
5. Remove SD card from the card slot.
 System manual for I/O system 1000 (EPM-Sxxx)

Here, further information on the single modules of the I/O system can be found.
service)
________________________________________________________________
10.2 Connecting the new controller/replacement device
 Note!
When a replacement device is connected, all communication cards which have been
previously implemented and all terminals have to be selected identically.
The user data are stored on the memory card of the controller.
If a controller of the same product type has been used, the newly connected 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
controller can be accessed again.
Which replacement device is suitable for the Controller?

Controllers can be replaced against each other as follows:
Defective Controller Replacement device

3221 C 3231 C 3241 C c300 p300 p500
3221 C   - - - -
3231 C -  - - - -
3241 C - -  - - -
c300 - - -  - -
p300 - - - -  -
p500 - - - - - 
: compatible
-: incompatible
Principally, Panel Controllers can be exchanged against each other (despite different screen
diagonals). If the mounting dimension is to be identical, use a Panel Controller with identical screen
diagonal.
The control application of a controller is serviceable after the device replacement: Insert the suitable
controller in the »PLC Designer« and compile project.
service)
________________________________________________________________
 How to install and connect a new controller:

1. Insert the SD card of the removed controller into the new one.
2. Connect bus connections and other connections.
3. Connect the current supply of the controller.
4. If I/O modules (I/O system 1000) have to be connected to the controller:
Plug in electronic module of the first system 1000 (if available).
5. Switch on voltage supply.
The Controller will start when the data is automatically updated.
 Note!
Prevent voltage failure
In the event of a voltage failure during the update, the process will be stopped.
During the next system start the update process will automatically restart.
Free memory location is required on the memory card
The controllers require an SD card for operation.
• For a successful data update, the memory card of the Controllers must be provided
with a sufficient amount of free memory space.
• Guide value for the size of a backup file:
size of the data to be updated + 1 MB
 Tip!
The progress of the update process can be ...
• ... seen in the logbook of the controller. Click the Logbook button to display the
logbook of the controller in the »WebConfig«.
• identified by means of the Status LEDs of the Controllers ( 80) on the Controller.
service)
________________________________________________________________
10.3 After the device replacement: Automatic data update
When is an automatic data update possible?

An automatic data update takes place after a defective Controller has been replaced by a
replacement device.
Which replacement device is suitable for the Controller? ( 73)
After a device replacement, the data of the bootable SD card of the defective controller must be
usable in the replacement device.
The SD card contains e.g. an executable boot project and a visualisation. Quick commissioning is
possible due to the data reuse in the replacement device.
Device replacement against an incompatible replacement device (exceptional case)
If a device replacement involves an

incompatible replacement device, an
error message will be entered into the
logbook of the controller
(available from Control Technology
version 3.3).
[10-1] Example: Incompatible replacement device
Scenario (version of replacement device/SD card) Description

The firmware version of the replacement device (controller) is ...
• ... higher than the software version on the SD card of the replaced This is the standard case.
controller. • The controller's version is more up-to-
Example: date than the software version on the SD
card of the replaced/defective controller.
• Automatic data update is started.
• ... identical to the software version on the SD card of the replaced The data remains unchanged since a data
controller. update is not required.
Example:
• ... lower than the software version on the SD card of the replaced This is no case of application for an
controller. automatic data update.
Example: • Automatic data update is only possible if
the software version is identical or more
up-to-date.
• Remedy: Update the Controller firmware.
Use a USB stick to update the firmware.
Further information on the update is
provided in the online help for »Backup &
Restore«.
service)
________________________________________________________________
Undo update of the data (exceptional case)

In the event of an accidental update, the initial state (version before the update) can be restored
manually if a suitable backup is available.
An "accidental" update takes place if an SD card has been plugged into a Controller which is not
scheduled for replacement.
Copy the contents of the backup

directory to the root directory of the SD
card (\USBSTORAGE).
[10-2] Example: Undo update manually (exceptional case).
service)
________________________________________________________________
10.4 Subsequent use of retain data on the new controller
 Note!
Depending on the used controller, the retain data of the PLC may no longer be available
after a voltage failure/device replacement.
• Controllers 3221 C/3231 C save the retain data internally (in the device, not on the SD
card). Hence, the retain data of the replacement device correspond to the output
values (default values).
• The Controllers 3241 C, c300, p300 and p500 save the retain data on the SD card.
 How to proceed in case of 3221 C/3231 C:

In order to be able to further use the retain data of the Controllers 3221 C/3231 C after a
device replacement, ...
• save the desired data to the SD card from the application;
• restore the desired data from the application.
Further information on the use of retain variables.

Creating remanent variables (retain/persistent) ( 64)
Storage of retain data on the SD card (only Controllers 3221 C/3231 C) ( 65)
service)
________________________________________________________________
10.5 Error messages after a device replacement
Message Information / remedy

Backup/restore cannot be copied. Not The SD card used has not enough free memory space to
enough free memory on the data medium. execute a safety backup. Delete non-required data from
the SD card and try it again.
The replacement device is not compatible In order to replace a device, the devices have to be
with the original device. Device compatible.
migration was not successful. Which replacement device is suitable for the
Controller? ( 73)
Inserted SD card has higher version than Update the Controller firmware. Afterwards, you can
the system. Please update the controller replace the device.
first. After the device replacement: Automatic data update
( 75)
Error while creating the backup for device An error has occurred while creating a backup. Please try
replacement. Please try again. again.
Migration failed. Please check your The migration of the databases failed. Please contact
configuration. your manufacturer.
11 Remote maintenance and diagnostics
________________________________________________________________

This chapter contains information on the Status LEDs of the Controllers ( 80) and the various
diagnostics options for remote maintenance:
Diagnostics via Telnet ( 82)
Data transfer via FTP ( 85)
Activate Windows® CE interface ( 92)
 Note!
Error case: Controller c300/p300 does not start
Information on error correction can be found here:
Error case: Controller c300/p300 does not start ( 32)
 Tip!
Lenze controllers can be diagnosed with »WebConfig« via web browser and by means of
the »EASY Starter«.
11.1 Status LEDs of the Controllers
________________________________________________________________
The Controllers are provided with LEDs which indicate the current operating status. Depending on
the Controller used, the colours of the LEDs vary.
• Power: green/blue*, yellow

• Error: green, red
• Status 1: green, yellow
• Status 2: no function
* Device-dependent LED colour: Either green or blue
[11-1] Example: Cabinet Controller 3200 C
LED Interval Meaning

Colour 1 / colour 2
Power
green/blue* Constant Startup completed successfully.
• No error pending
• Controller is switched on
• Supply voltage OK
Yellow Constant The supply voltage has fallen below the minimum value. Voltage
buffering by external UPS (optional, for Controller 3241 C) ( 158)
UPS functionality of the controllers ( 68)
blinking Status after switch-on/restart
(2.0 Hz) (For Controller c300/p300 in preparation.)
green/ Yellow blinking "System clock is not synchronised" (time information missing).
blue* (0.5 Hz) Note:
If the Controller is switched off for more than two weeks, the time
information set will be lost.
• The next starting process creates a logbook entry (power LED is
blinking green/blue).
• The current time can be set manually via »WebConfig«
(parameter 91).
Only for Controller 3241 C: Battery pack (ACCU-PACK) is not fully charged.
green blinking The length of the dark phase indicates the charge status:
(5.0 Hz) • Battery pack almost empty: Long dark phase
• Battery pack almost full: Short dark phase
Only for Controller 3241 C: Error status of the battery pack (ACCU-PACK)
green Yellow blinking UPS function is not available, possible cause:
(5.0 Hz) • Connection to the battery pack interrupted
• Battery pack not connected, cable break/short circuit
Error
red blinking Error
(5.0 Hz) • Fatal error (abort)
• SD card not available/not inserted correctly
• No operating system licence available
green red blinking Mains switching required
(5.0 Hz)
Status 1 ("busy")
________________________________________________________________
LED Interval Meaning

Colour 1 / colour 2
green constantly on Controller is running (operating status):
• PLC project is running (device is running, operating status)
blinking Starting process of the Controller active
(0.5 Hz)
green Yellow blinking User action required:
(0.5 Hz) • "Load PLC project": PLC started, project is not running
• Remove USB flash drive
Status 2
- - No function
* Device-dependent LED colour: Either green or blue
Depending on the running software application, different control modes of the LEDs are possible.
 Online help for »Backup & Restore«

Here, further information on the »Backup & Restore« specific LED signals can be found.
11.2 Diagnostics via Telnet
________________________________________________________________
Telnet is a standard mechanism for experts to change system settings.

Telnet ...
• enables the access to the Controller data (example: Contents of the SD card);
• requires an existing local connection or remote connection.
 Note!
• These devices come with a deactivated Telnet in the Lenze standard setting.
• The function can be activated via the »WebConfig«. The activation of the function can
influence the real-time behaviour.
• After a restart of the Controller, the function is deactivated again.
________________________________________________________________
11.2.1 »WebConfig« settings
The telnet settings can be configured via telnet parameters 180 to 181 by clicking the Remote
maintenance button of the web-based parameterisation.
• Parameter 180 activates authentication of the telnet user.
• Parameter 181 activates the telnet access to the controller.
 Note!
The corresponding Windows® CE user must have a telnet authorisation.
Setting up Windows® CE users in »WebConfig« ( 37)
Access via telnet must only be used for diagnostic purposes. Changing system data may
result in controller faults.
Standard access data:

• login: admin
• Password: admin
________________________________________________________________
 How to establish a telnet connection to the 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 controller: Start telnet <IP address> of the controller.
4. The user name and password for the authentication must correspond to the data stored in
the user management, parameters 101 to 170.
11.3 Data transfer via FTP
________________________________________________________________
The File Transfer Protocol (FTP) is a network protocol for the transfer of data within networks.
• FTP makes it possible to exchange files between the controller and other PCs.
• The controller data can be accessed via FTP connection.
• FTP requires an existing connection or a remote connection.
• In order to be able to transfer files with Windows® via FTP, the Windows® Explorer can be used
which comes with an integrated FTP support.
 Note!
FTP must be used for system-diagnostic purposes only. Deleting or changing system files
causes malfunctions of the controller!
• These devices come with a deactivated FTP in the Lenze standard setting.
• The function can be activated via the »WebConfig«. The activation of the function can
influence the real-time behaviour.
• After a restart of the Controller, the function is deactivated again.
________________________________________________________________
11.3.1 FTP settings with the »WebConfig«
The settings of the FTP connection can be managed via the web-based parameterisation. From
parameters 171 to 174 the FTP access for the controller can be activated and user rights can be
specified. Click the Remote control button to call the FTP settings:
• Parameter 171 activates authentication of the FTP user,

• Parameter 172 enables log-on of the anonymous FTP user "Anonymous",
• Parameter 173 activates the upload of files by anonymous FTP users,
• Parameter 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 controller via FTP.
 Note!
Restart the FTP server to accept the changed settings: 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.
________________________________________________________________
11.3.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 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 ExtrasInternet
optionsConnectionsSettings ,
• Switch off the proxy server or remove the controller from the proxy settings.
________________________________________________________________
 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 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.
3. When the entry is correct, click the Log in button.
• The Controller can now be accessed by the Engineering PC.
11.4 Diagnostics with the logbook
________________________________________________________________
Lenze controllers are equipped with a logbook function which records system events and error
messages. The entries in the logbook of the controller make it easier to diagnose the automation
system if malfunctions occur.
The logbook of the controller...
• displays error messages and events of the 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 controller can be called via »WebConfig« and the »EASY Starter«:
Logbook query via »WebConfig« ( 90)
________________________________________________________________
11.4.1 Logbook query via »WebConfig«
The logbook entries can be called via »WebConfig«.

• The browser of the Engineering PC accesses the web server of the controller via Ethernet
connection (http://).
• The data manager of the controller provides for access to logbook contents.
 How to call the logbook in »WebConfig«:

1. Start your browser on the Engineering PC,
2. Enter the IP address of the controller: http://<IP address>,
3. Enter your user name and password,
4. Click the logbook button.
The logbook of the controller can be displayed via the Logbook button in »WebConfig«.
 Note!
The ClearLog command deletes all logbook entries on your controller without further
query!
 Tip!
The display of the logbook entries can be filtered according to the period, application,
severity, and area.
More information on how to use the logbook function in the »WebConfig« can be found here:
________________________________________________________________
Logbook ( 52)
11.4.2 Logbook parameters
The logbook settings can be called in »WebConfig« via the Diagnostics button.
Further information on the parameters of the logbook (from parameter C0048) can be found here:
11.5 Activate Windows® CE interface
________________________________________________________________
During normal operation the Windows® CE functions are hidden on the controller. All controller
functions can be controlled via the Engineering PC.
• For diagnostic purposes and maintenance activities you can use the standard functions of the
controller operating system Windows® CE.
• You can access the Windows® CE functions
• via the service mode if the controller is operated directly,
• via a telnet connection with the corresponding administrator rights.
 How to activate the user interface of Windows® CE on the 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 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 controller which requires a diagnostics via Diagnostics via Telnet.
• The standard settings of the Windows® CE User 1 are: User name: admin, password
• explorer activates the Windows® CE interface on the controller
________________________________________________________________
11.5.1 Remote Display: Remote control of Controller via Internet or LAN
Remote Display Control for Windows® CE (cerhost/cerdisp)

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 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 controller with the (previously identified) IP address of the
Engineering PC : cerdisp <IP address>
[11-2] Remote access to a controller via Remote Display Control
________________________________________________________________
11.5.2 Virtual Network Computing (VNC)
For the Engineering PC, you need the "Virtual Network Computing" (VNC) software.
• VNC is preinstalled on the controller. (directory: \USBStorage\windows\VNC.exe)
• VNC allows you to operate the 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 controller.
Conditions
• The controller is switched on and connected to the network/Internet.
• The VNC server is started on the 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 controller:

1. Start the VNC server on the controller
• In the »WebConfig«, set the "Activate VNC server"  (CS 95) or
• Execute the \windows\VNC.exe file
2. Start VNC client on the Engineering PC.
3. Enter the IP address of the controller.
Tip: To display the IP address of the controller, go to the Control Panel
(StartSettingsControl Panel) of the controller and select "Network Connections".
[11-3] Remote access to a controller via VNC (example: VNCviewer)
12 Visualisation with »VisiWinNET®«
________________________________________________________________

This chapter provides information about the Lenze Engineering tool »VisiWinNET®«.
In addition to some basic information, you are provided with information with regard to the use of
»VisiWinNET®« in connection with the "Controller-based Automation" system by Lenze.
»VisiWinNET®« is a visualisation software for mechanical and systems engineering.
»VisiWinNET®« can be used to create complex visualisation applications, the possibilities range
from classical operate and monitor functions through to sophisticated SCADA systems.
 Note!
The Controllers 3221 C and c300 can only be accessed by a remote connection via
»VisiWinNET®« as these devices do not have a display interface (DVI).
 Online help for »VisiWinNET®«

Here, further information on the use can be found.
Licensing
The Controllers can be ordered with a factory-set licence which enables the use of »VisiWinNET®«.
The licence level installed can be found in »WebConfig« under: DiagnosticsLicence
12.1 Visualisation on the controller: local and remote
________________________________________________________________
12.1 Visualisation on the controller: local and remote
A visualisation can either run locally on a controller, or via remote connection on an additional
controller.
The following cases are distinguished:
• Local visualisation - integrated control system
Control and visualisation on the same controller. The following runs on the controller:
»VisiWinNET®« runtime, PLC (Logic/Motion), the data manager, and the fieldbus driver.
Local visualisation can be carried out...
• on a panel controller.
• on a cabinet controller with a connection facility for a monitor panel.
• Remote access - external visualisation
Control and visualisation on separate controllers.
The »VisiWinNET®« runtime runs on a separate "Visu" controller. This controller solely
undertakes visualisation tasks. The external "Visu" controller accesses the process data of an
additional controller which controls the system.
The control program runs on the first controller. The »VisiWinNET®« runtime runs on the second
controller.
• External "Visu" on the controller
• External "Visu" on a Windows® XP or Windows® Embedded XP PC.
________________________________________________________________
»VisiWinNET®« consists of...
• the »VisiWinNET®« Engineering tool on the Engineering PC: and
• the »VisiWinNET®« runtime on the Controller: .

By means of »VisiWinNET®« you create the visualisations on the Engineering PC.
• The »VisiWinNET®« Engineering tool executes the associated »VisiWinNET®« runtime of the
controller.
• By means of the »VisiWinNET®« Remote Access Manager, you transfer the visualisations to the
controller.
• Activate parameter 97 "Activate VisiWinNET Remote Access " in »WebConfig« to start the
Remote Access Manager.
• TCP/IP serves as a standard for data transmission.
• The »VisiWinNET®« Runtime is able to access the following variables:
• PLC variables (Logic/Motion),
• Parameters of the controller (data manager)
• Parameters of the devices (via the fieldbus driver).
12.3 Using the visualisation to access data of the control/parameters
________________________________________________________________
Variables of the PLC (Logic/Motion) can be accessed with the "LogicAndMotionV3" direct driver.
Here, the »VisiWinNET®« Runtime may be on a local controller or on an external controller.
 Note!
We recommend the use of the "LogicAndMotionV3" direct driver for easy
commissioning.
Use the Direct driver "LogicAndMotionV3" (local visualisation) ( 101)
without PLC.
Use the "LogicAndMotionV3" direct driver to

access the following parameters:
• PLC (Logic/Motion) data
• Lenze recommend to use the
"LogicAndMotionV3" direct driver.
• Alternatively, you can access the following
data via the OPC tunnel:
• DataManager OPC server
 Controller parameters.
• CAN/EtherCAT OPC server
 Field device parameters (CAN/
EtherCAT).
• SoftPLC OPC server
 Variables of PLC (Logic/Motion):
Communication type / description Access to ...

Direct driver "LogicAndMotionV3" PLC (Logic/Motion) data
(Recommended connection type!)
Use the Direct driver "LogicAndMotionV3" (local
visualisation) ( 101)
• DataManager OPC tunnel Parameters of the Controller
• DataManager Remote OPC tunnel (remote access)
________________________________________________________________
Communication type / description Access to ...

• CAN OPC tunnel Field device parameters at the CAN bus
• CAN Remote OPC tunnel (remote access) Field device parameters at the EtherCAT bus
• EtherCAT OPC tunnel
• EtherCAT Remote OPC tunnel (remote access)
Note: The (Remote) SoftPLC OPC Tunnel communication PLC (Logic/Motion) data
type requires a separate configuration of the controller
(experts only - please contact Lenze if required!).
• SoftPLC OPC tunnel
• SoftPLC Remote OPC tunnel (remote access)
12.4 Use the Direct driver "LogicAndMotionV3" (local visualisation)
________________________________________________________________
We recommend the use of the "LogicAndMotionV3" direct driver for easy commissioning.
Start »VisiWinNET®«
Start the EASY »Navigator«
Start »VisiWinNET® Smart« by clicking the

Visualisation button.
 Note!
without PLC.
________________________________________________________________
12.4.1 Selecting the target device using the Windows® CE operating system (example 3200 C/
p500)
Using the "LogicAndMotionV3" direct driver.
 How to use the direct driver:

1. Create a new project in »VisiWinNET®«: File File New Project
2. Select the desired target device.
• Example: Controller 3231 C

• For cabinet controllers: select connected monitor panel.
3. Add the "LogicAndMotionV3" direct driver as communication channel:
________________________________________________________________
4. Configure the added communication channel:
• A Line must be activated and the PLC address (node address) of the Controller must be
specified.
• The PLC address and the IP address of the target device (Controller) must be specified.
(Preset IP address of the Controller: 192.168.5.99)
Note: The PLC address can be found in the »PLC Designer« in the context menu of the
device: DeviceCommunication SettingsIPC:Node Address
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.
5. In a next step, you can browse variable definitions:
Using the variables browser to access variables (browse variables) ( 105)
6. After completion of the project configuration, the Project Explorer is provided with a new
channel: "LogicAndMotionV3".
________________________________________________________________
12.4.2 Project Explorer
The project Explorer enables central access to controller data in »VisiWinNET®«.
 Select ViewProject Explorer in the menu bar to open the Project Explorer.
________________________________________________________________
12.4.3 Using the variables browser to access variables (browse variables)
The variables browser can be used to browse for variables on the devices connected to the controller
and to transfer them to a project subsequently. For this purpose, a connection between the
integrated »VisiWinNET®« development environment and the controller is not required. The data is
read from the locally available symbol description files, which have been exported from the »EASY
Starter« in advance.
 »PLC Designer« Online help

More information about this topic can be found in the following section:
"Symbol configuration editor"
 How to call up the Variables Browser:

1. Open the VariablesChannels folder in the Project Explorer.
Alternatively, you can browse variables when creating a new project.
2. Execute the Browse variables command in the context menu of the intended
communication channel.

In the VisiWinNET Lenze Variables Browser dialog box, all available devices for reading
variable definitions can be seen in the Devices selection list.
________________________________________________________________
3. Click the Add button to select the desired communication type.
Required information: Set line number (Line number), Devicealias (freely selectable), and
the Parameterfile (XML symbol configuration file) exported from the »PLC Designer« V3.x.
Browsing variable definitions / configuring the device ( 114)
________________________________________________________________
12.4.4 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 variables browser.
2. Click the OK button.
A tree view of the read variable definitions appears.
3. Select the variable definitions required.

The variable definitions are transferred to the project database.
________________________________________________________________
12.4.5 Creating control elements/linking them to variables
A user and visualisation interface created with »VisiWinNET®« consists of different control
elements (e.g. buttons. checkboxes and selection fields).
To be able to use control elements, the desired control elements must be linked to the available
variables of the target device.
Creating control elements
 How to create control elements:

1. In the Project Explorer double-click an existing form in the Design folder.
The FCentral form is created for a new project.
2. Call the Toolbox.
Double-click the View Toolbox menu command or tab on the right-hand side of the
screen.
3. Move the desired control elements using the Toolbox via the drag&drop functionality
to the desired position in the workspace.
 How to link control elements with variables:

1. Highlight the desired control element (example: VarIn1).
• Click the arrow icon .
• Click the VWItem() variable to open the ItemDialog.

2. Select the desired variable from the tree structure.
3. Click the OK button to assign the variable to the control element.

4. Repeat the process for all control elements correspondingly.
________________________________________________________________
12.4.6 Transferring an application to the target device
In order to be able to transfer an application to the target device, you have to start the
»VisiWinNET®« Remote Access Manager.
For this purpose, activate parameter 97, "Activate VisiWinNET Remote Access " in »WebConfig«.
 Alternatively, the »VisiWinNET®« Remote Access Manager can be started via the user
interface of an optional monitor panel:
1. Change to the service mode.
Start the control panel: F1 key on the monitor panel or key combination: <Shift>+<F4>
2. Double-click the »VisiWinNET®« Remote Access icon to start the Remote Access Manager.
 How to transfer an application to the target device:

1. Go to the »VisiWinNET®« menu bar
and select ProjectTransmit to target device.
The Connect device window appears.
2. Enter the IP address or network name.

You can view and alter the IP address of the controller in the "Network Connections"
program.
Configuring the controller ( 33)
3. Click the Connect button.
The application is transferred to the target device.
 Note!
If the firewall of Windows®XP/7 is active, you have to enable a port for »VisiWinNET®«. In
the standard setting this is port 10116.
________________________________________________________________
12.4.7 Start the »VisiWinNET®«
The »VisiWinNET®« Project Manager manages the »VisiWinNET®« project data of the target device
(visualisation controller).
 Click the »VisiWinNET®« Project Manager icon to start the Project Manager.
[12-1] »VisiWinNET®« Project Manager on the controller (Windows® CE)
• Click the Run button to start the selected project. (Corresponds to the Start project
command in »VisiWinNET®«)
• The Set AutoStart button sets the project as start project in »VisiWinNET®«.
This will cause the controller to load this project automatically when the system is started.
12.5 Using the LogicAndMotionV3 direct driver (remote access)
________________________________________________________________
12.5 Using the LogicAndMotionV3 direct driver (remote access)
Select the target device (Windows® XP operating system)

Using the direct driver for LogicAndMotionV3.x under »VisiWinNET® Smart«.
 How to use the direct driver:

1. Select new project with the desired target device, example: Controller 3241C.
For cabinet controllers: select connected monitor panel.

2. For the configuration of the LogicAndMotionV3 channel, the address of the target device
(Controller - control PC) must be specified.
3. The further procedure is identical to steps 2 to 5 of the LogicAndMotionV3 direct driver
under Windows® CE:
Selecting the target device using the Windows® CE operating system (example 3200 C/
p500) ( 102)
12.6 OPC tunnel for local visualisation (integrated control system)
________________________________________________________________
 Note!
without PLC.
• The local »VisiWinNET®« Runtime on the

controller uses the local OPC tunnel to
access the respective OPC server
(DataManager, CAN/EtherCAT, SoftPLC).
• For a local visualisation, the OPCServer.ini
configuration file must be adapted. The
configuration file is on the memory card of
the controller, directory: \USBStorage.
Configure OPC tunnel ( 119)
[12-2] Local visualisation on a controller
________________________________________________________________
12.6.1 Integrating the OPC tunnel in »VisiWinNET®«
The OPC tunnel is the communication channel between »VisiWinNET®« and the OPC servers of the
controller. The desired OPC tunnel must be integrated into the project.
 Note!
The OPC tunnel cannot be integrated by means of the menu navigation (during the
creation of a new project).
Integrate the OPC tunnel by means of the Project Explorer. Then the OPC tunnel can be
configured.
 How to integrate the OPC server into the project:

1. Open the Project Explorer.
2. Select the entry New in the context menu of the node VariablesChannels.
• Select "OPC server" as Channel type.

• Select the OPC server/driver by clicking the button.
• Select the Lenze OPC tunnel (Lenze.Digitec.OPCTunnel.DA).
3. Confirm your selection by clicking the OK button.
The OPC tunnel can be selected in the Project Explorer.
________________________________________________________________
12.6.2 Browsing variable definitions / configuring the device
When you have started the Lenze Variables Browser, you can configure one or more devices and
then import the variable definitions.
 How to browse for variable definitions:

1. Click the Add button in the Lenze Variables Browser:
2. Select the communication type from the Configure device dialog box depending on the
variables you want to access.
Communication types ( 115)
• Select the desired Communicationtype.

• Select the desired Parameterfile (variable definition file).
• Click the ... button to search for a parameter file on a data carrier.
3. Enter the name into the Devicealias text field (freely selectable).
The device alias is a »VisiWinNET®«-internal name for the device.
________________________________________________________________
Communication types
Communication type Description

DataManager OPC tunnel Required information:
• Devicealias
• Parameterfile
Supported file formats:
• Device description files (*.dcf, *.eds)
Suitable device description files (*.eds) for the Controller 32xx can be found
in the Lenze Application Knowledge Base (AKB) under:
http://www.Lenze.com
CAN OPC tunnel Required information:

• CAN interface (CAN Interface)
• CAN node address (CAN Node Address)
• Devicealias
• Parameterfile
• Parameter description (*.pdb)
• »Global Drive Control« file(*.gdc)
EtherCAT OPC tunnel Required information:

• EtherCAT interface (EtherCAT Interface)
• EtherCAT address (EtherCAT Node Address)
• Devicealias
• Parameterfile
Supported file format:
• Parameter file (*.pdb)
• »Global Drive Control« file (*.gdc)
Note: EtherCAT device description files (*.xml) are not supported!
SoftPLC OPC tunnel Required information:

• The configuration name (Configuration Name) must be entered
manually. Default value of the Controller: PLC1.
Note: The configuration name must be identical to the specification in
the OPCServer.ini file!
• The OPCServer.ini file is on the memory card of the Controller (directory:
\USBStorage).
• Symbol file (*.sym)
Note: XML symbol configuration files exported from the »PLC
Designer« V3.x are not supported!
Configure OPC tunnel ( 119)
Manual integration of variables (experts only - background knowledge
required!) ( 116)
________________________________________________________________
12.6.3 Manual integration of variables (experts only - background knowledge required!)
If no suitable parameter file is available, the Item ID can also be entered manually (as an alternative
to the variables browser).
Depending on the server and the type of connection (local or remote), a defined syntax must be
observed. The following sections provide a description of the syntax.
 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 entry from the context menu.
4. Enter the ItemID in the ItemID/address input field. Alternatively, enter the variable name
in the variable editor.
The given syntax of the ItemID must be observed!
Syntax of the ItemID

The ItemID must be used according to the table, depending on the desired OPC tunnel.
Data types used: Data types ( 118)
Access to ... Syntax of the ItemID

DataManager OPC tunnel 1. Put the prefix, <DM>, in front. DM = "DataManager".
2. The index results from 0x5FFF minus <Code> of the DataManager.
Example: (code = 5): 0x5FFF - 5 = 0x5FFA = 24570
3. Specify the variable as follows:
DM.pari<0x5FFF "minus" Code>d<Data type>.
4. If an additional reference to a subindex is provided, supplement the
following entry:
• Example with subindex "1": DM.pari24572s1d8
DataManager Remote OPC tunnel 1. In the ItemID, put the prefix, <RemoteIPC>, in front.
2. Specify the variable as follows: .pari<0x5FFF "minus" <Code>d<Data
type>.
• Example: RemoteIPC.DM.pari24572d8
3. If an additional reference to a subindex is provided, supplement the
following entry:
• Example with subindex "1": RemoteIPC.DM.pari24572s1d8
CAN OPC tunnel • Put the prefix, CAN, in front of the variable:
CAN.can<Number of the CAN interface>.dev<Device CAN
address>.pari<0x5FFF "minus" Code>d<Data type>
• Example (CAN interface 2, CAN address 18, code 1, subcode 2, data type
unsigned INT):
CAN.can2.dev18.pari24576s2d17
________________________________________________________________
Access to ... Syntax of the ItemID

CAN Remote OPC tunnel 1. In the ItemID, put the prefix, <RemoteIPC>, in front.
2. Specify the variable as follows: CAN.can<Number of the CAN
interface>.dev<Device CAN address>.pari<0x5FFF "minus"
Code>d<Data type>.
• Example (CAN interface 2, CAN address 18, code 1, subcode 2, data type
unsigned INT):
RemoteIPC.CAN.can2.dev18.pari24576s2d17
EtherCAT OPC tunnel 1. Put the prefix, ECAT, in front of the variable.
ECAT.ecat1.dev<Device address>.pari<0x5FFF "minus"
Code>d<Data type>
• Example (EtherCAT address 1001, code 1, subcode 2, data type unsigned
INT):RemoteIPC.ECAT.ecat1.dev1001.pari24576s2d17
EtherCAT Remote OPC tunnel 1. In the ItemID, put the prefix, <RemoteIPC>, in front.
.ecat1.dev<Device address>.pari<0x5FFF "minus" Code>d<Data
type>.
• Example (EtherCAT address 1001, code 1, subcode 2, data type unsigned
INT):RemoteIPC.ECAT.ecat1.dev1001.pari24576s2d17
SoftPLC OPC tunnel 1. Put the prefix, <PLC.PLC1.>, in front of the variable.
Note: The prefix, PLC1, must be identical to the specification in the
OPCServer.ini file!
\USBStorage).
<Application>.<POU>.<Symbol name>.
• Example: PLC.PLC1.Application.PLC_Prg.My_Variable
SoftPLC Remote OPC tunnel 1. In the ItemID, put the prefix, <RemoteIPC>, in front.
2. Specify the variable as follows: <RemoteIPC> <PLC.PLC1.> +
<Application>.<POU>.<Symbol name>.
• Example:
RemoteIPC.PLC.PLC1.Application.GVL.byGlobalByte
________________________________________________________________
Data types
The following data types are available for query:
Data type Description

»VisiWinNET®« OPC tunnel
VT_BOOL d11 Truth value (TRUE/FALSE)
VT_BSTR d8 String STRING
VT_DATE d7 Date / time format
VT_EMPTY d0 The data type is not specified.
• This data type is e.g. returned if no process variable has been specified.
VT_I1 d16 Integer 1-byte value; signed (-128 ... 127)
VT_INT d22 Integer value; signed; machine type-dependent
VT_R4 d4 Floating-point number simple accuracy (4 bytes)
VT_R8 d5 Floating-point number double accuracy (8 bytes)
VT_UI1 d17 Integer 1-byte value; unsigned (0 ... 255)
VT_UINT d23 Integer value; unsigned; machine type-dependent
________________________________________________________________
12.6.4 Configure OPC tunnel
The OPC tunnel ...

• permits »VisiWinNET®« access to the OPC servers of the Controller
• "tunnels" all accesses via a special Ethernet port and hence offers the possibility of remote
access by security systems.
 Note!
If the Windows® XP firewall is activated, the port (standard setting: port 56765) needs
to be activated for the OPC tunnel!
The OPCServer.ini configuration file
 Note!
• The OPCServer.ini configuration file contains parameters which must be observed/
edited if the SoftPLC OPC server is to be used for communication.
• After edition of the configuration file, the Controller must be restarted for the
changes to take effect.
To be able to access the SoftPLC OPC server, the ...

• ... configuration name (standard value: PLC1) specified in the OPCServer.ini file must be used.
• ... respective node address of the device must be entered into the OPCServer.ini file
(value0=<Node address>).
PLC0=PLC1 <-- Configuration name (standard value: PLC1)
...
[PLC:PLC1]
...
value0=0731 <-- Node address (example: 731)
The OPCServer.ini file is on the memory card of the Controller (directory: \USBStorage).
12.7 OPC tunnel for external visualisation (remote access)
________________________________________________________________
12.7.1 Windows® CE operating system
The »VisiWinNET®« Runtime of the external

controller, Controller(Visu), accesses the OPC
servers of the control system Controller via the
OPC tunnels (1, 2).
[12-3] Remote access with one visualisation controller ("Visu") and one controller
 Note!
without PLC.
________________________________________________________________
12.7.1.1 Configure OPC tunnel for remote access (Windows® CE)

For the configuration of the OPC tunnel, the oct.xml configuration file must be edited.
In our example, the IP address of the 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 controller in the
configuration file (as described in the following section).
• For configuring OPC tunnel 2, standard settings need not be changed (configuration file:
oct.xml).
Preparation
Read in the SD card of the visualisation Controller on your PC using a card reader.
or
Establish an FTP connection between your PC and the visualisation Controller.
FTP settings with the »WebConfig« ( 86)
 How to set up an external visualisation on the controller:

1. Go to the \USBStorage\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. Use the Software Microsoft Editor, for instance, for edition.
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 the IP address of the controller (with the control function).

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 the controller (with the visualisation function).
The OPC servers of the control 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 \USBStorage\OCT
directory and restart the controller.
________________________________________________________________
12.7.2 Windows® XP/XP Embedded operating system
The »VisiWinNET®« runtime of the external

Windows® XP/XP Embedded controller
accesses (via OPC tunnel 1) the OPC servers of
the Controller.
 Note!
without PLC.
________________________________________________________________
12.7.2.1 Configure OPC tunnel for remote access (Windows® XP/XP Embedded)
In our example, the IP address of the Controller is: 192.168.5.99
• For the configuration of OPC tunnel 1 (external Controller), the oct.xml configuration file is
used which can be found in the \Programs\Lenze\Lenze Digitec OPC Tunnel
directory.
• The suitable IP address of the control system Controller must be entered into the configuration
file as described in the following section.
Preparation
 Install the OPC tunnel on the Windows® XP PC.

1. The required installation files are provided on the Lenze installation CD in the following
directory:
2. Execute the installation file: Lenze_L-force_OPC_Tunnel_x.x.x.x_setup.exe.
 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:

Remove the "<!-" and "-->" comment characters at the beginning and at the end of the
section.
5. Enter the IP address of the Lenze controller (with the control function).
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 controller can now be accessed.
________________________________________________________________
12.7.3 Browsing variables
This chapter describes how to browse variables using the Remote OPC tunnel.
 How to browse for variable definitions:

1. Click the Add button to import the variable definition file which has been previously
exported from the »PLC Designer«.
Select the communication type (Remote OPC server) from the Configure device dialog box
depending on the variables you want to access.
Possible communication types

Remote DataManager OPC tunnel Required information:
• Remote name of the target device (standard value: RemoteIPC)
Note: The Remote name must be identical to the value specified in the
oct.xml file.
• The oct.xml file can be found on the SD memory card of the Controller
(directory: \USBStorage\OCT).
• Devicealias
• Parameterfile
EDS device description files can be found in the Lenze Application
Knowledge Base (AKB):
http://www.Lenze.com
CAN Remote OPC tunnel Required information:

• Remote name of the target device (example: "RemoteIPC")
• CAN interface (CAN Interface)
• CAN node address (CAN Node Address)
• Devicealias
• Parameterfile
________________________________________________________________

EtherCAT Remote OPC tunnel Required information:
• EtherCAT interface (EtherCAT Interface)
• EtherCAT address (EtherCAT Node Address)
• Devicealias
• Parameterfile
Note: EtherCAT device description files (*.xml) are not supported!
SoftPLC Remote OPC tunnel Required information:

• The configuration name (Configuration Name) must be entered
manually. Default value of the Controller: PLC1.
Note: The configuration name must be identical to the specification in
the OPCServer.ini file!
\USBStorage).
• Symbol file (*.sym)
Note: XML symbol configuration files exported from the »PLC Designer«
V3.x are not supported!
Manual integration of variables (experts only - background knowledge
required!) ( 116)
12.8 Lenze specifications
________________________________________________________________
12.8 Lenze specifications
12.8.1 Install additional fonts
 How to install additional fonts for visualisation:

1. Copy the additional font file to the \USBStorage\Fonts directory on the SD card.
2. In the PostStart.txt file, add the AddFont.exe entry.
The PostStart.txt file is in the \USBStorage directory (basic directory of the SD card).
12.8.2 Timeout (waiting position) of the CAN OPC server influences the time response of the
visualisation
When the visualisation directly accesses the parameters of an inverter 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.
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.

Examples:
• The first CAN interface is called: CAN2Bus1
• The second CAN interface is called: CAN2Bus2
13 Parameter reference
________________________________________________________________
This chapter provides a list of all controller parameters in numerically ascending order.
 Note!
Depending on the configuration and assembly of your controller, the parameter lists
may vary.
This chapter describes the following parameters:
Voltage buffering by external UPS (optional, for Controller 3241 C) ( 158)
Ethernet (on board) ( 161)
EtherCAT ( 163)
Monitor panel (integrated/external) ( 168)
PLC (Logic/Motion) ( 172)
Backup&Restore ( 174)
Communication cards: optional interface ( 178)

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 ( 129)
• Parameters with write access ( 129)
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
UNSIGNED_8 8-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
DATE Date
________________________________________________________________
13.1.2 Parameters with read access
Parameters without the "Write access" attribute are read only/not editable.
Description structure
Parameter | Name: Data type: _______

Cxxxxx | _____________ Index: _______
Descriptive text
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 are editable. The preset
Lenze setting for these parameters is printed in bold.
• The settings can either be changed ...
• ... via a selection list or
• ... by entering a value directly.
13.1.3.1 Parameters with a setting range

Cxxxxx | _____________ Index: _______
Descriptive text
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

Cxxxxx | _____________ Index: _______
Descriptive text
Selection list (Lenze setting printed in bold)
1
2
3
________________________________________________________________
13.1.3.3 Parameters with a bit-coded setting

Cxxxxx | _____________ Index: _______
Descriptive text
Value is bit-coded:
Bit 0
...
Bit 31
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 required for the parameter setting of the controllers!
 PLC STOP This attribute is not required for the parameter setting of the controllers!
 No transfer This attribute is not required for the parameter setting of the controllers!
13.2 Basic parameters of the Controllers 3200 C/c300 and p300/p500
________________________________________________________________
In this chapter all parameters of the controller standard devices (Cabinet Controller/Panel
Controller) are listed in numerically ascending order.
C0003
Parameter | Name: Data type: VISIBLE_STRING

C0003 | Device: Name Index: 24572d = 5FFCh
Device name of the controller

C0004

C0004 | Device: Software Index: 24571d = 5FFBh
Software version of the controller

C0005

C0005 | Device: Hardware Index: 24570d = 5FFAh
Hardware version of the controller

C0006

C0006 | Device: Serial number Index: 24569d = 5FF9h
Serial number of the controller

C0007

C0007 | Device: Manufacturer Index: 24568d = 5FF8h
Manufacturer of the controller

C0008

C0008 | Device: Manufacturing date Index: 24567d = 5FF7h
Manufacturing date of the controller

C0013

C0013 | System identification: Name Index: 24562d = 5FF2h
Assign device names to the controller, in order to be able to identify it in the Engineering tool more easily.
________________________________________________________________
C0015

C0015 | System identification: User name Index: 24560d = 5FF0h
User name for the identification on the system

C0016

C0016 | System identification: Description Index: 24559d = 5FEFh
Description for the identification on the system

C0018
Parameter | Name: Data type: UNSIGNED_16

C0018 | Command Index: 24557d = 5FEDh
Load PLC program command. Here the PLC boot project is reloaded.
Selection list (Lenze setting printed in bold) Info
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 including 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

C0019 | Command status Index: 24556d = 5FECh
Parameter with the status of the running command

________________________________________________________________
C0020

C0020 | CPU: Name Index: 24555d = 5FEBh
CPU type designation

C0025

C0025 | CPU: Firmware version Index: 24550d = 5FE6h
CPU firmware version

C0030

C0030 | CPU: Temperature Index: 24545d = 5FE1h
Processor temperature [°C]

0 °C 255
C0036

C0036 | Bootloader: Type version Index: 24539d = 5FDBh
C0040

C0040 | Activate front USB Index: 24535d = 5FD7h
The optional USB socket mounted on the monitor panel mounted on the front is ...
• ... activated by entering "1" and
• ... deactivated by entering "0".
• Applies to the Controllers 3200 C with external monitor panels (optionally available)
0 1 0
C0041

C0041 | Operating time Index: 24534d = 5FD6h
Total operating time since the device has been switched on [s]
0 h 16777215
________________________________________________________________
C0042

C0042 | Number of reboots Index: 24533d = 5FD5h
Number of boot processes of the device

0 65535
C0043

C0043 | Activate Explorer Index: 24532d = 5FD4h
Deactivate option to hide the WindowsCE user interface/task bar on the controller
• The VisiWin-Remote Access Manager remains visible.
0 1 1
C0048

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.
min 2 min
C0049

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.
0 150 150
C0050

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
SD memory card.
100 10000 3000
________________________________________________________________
C0051

C0051 | Logbook: Size on CF Index: 24524d = 5FCCh
Size of the memory space occupied on the SD memory card

C0052

C0052 | Logbook: Number of entries in RAM Index: 24523d = 5FCBh
Actual number of entries in the RAM

C0053
Parameter | Name: Data type: DATE

C0053 | Logbook: Time of oldest entry Index: 24522d = 5FCAh
Date of the oldest entry in the logbook

(Local time
C0054

C0054 | Logbook: Index of oldest entry Index: 24521d = 5FC9h
Number of the oldest entry in the logbook

C0055

C0055 | Logbook: Time of last entry on CF Index: 24520d = 5FC8h
Time of the last entry on the SD card

(Local time
________________________________________________________________
C0056

C0056 | Logbook: Index of last entry on CF Index: 24519d = 5FC7h
Number of the last entry on the SD memory card

C0057

C0057 | Logbook: Index of last entry Index: 24518d = 5FC6h
Number of the last entry in the logbook

C0058

C0058 | Logbook: Time of last entry Index: 24517d = 5FC5h
Time of the last entry in the logbook

(Local time
C0064

C0064 | Logbook: Time of last error entry Index: 24511d = 5FBFh
Entry of the last time error in the logbook

(Local time
C0070

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.
0 % 27 27 %
________________________________________________________________
C0071

C0071 | Allocated program memory Index: 24504d = 5FB8h
Size of the reserved program memory

0 Bytes 4294967295
C0072

C0072 | Used program memory Index: 24503d = 5FB7h
Size of the occupied program memory

0 Bytes 4294967295
C0075

C0075 | Allocated virtual file memory Index: 24500d = 5FB4h
Object store reserved for saving of virtual files

0 Bytes 4294967295
C0076

C0076 | Used virtual file memory Index: 24499d = 5FB3h
Object store occupied by virtual files

0 Bytes 4294967295
C0078

C0078 | Allocated flash memory Index: 24497d = 5FB1h
Flash memory reserved

0 Bytes 4294967295
________________________________________________________________
C0079

C0079 | Used flash memory Index: 24496d = 5FB0h
Flash memory occupied

0 Bytes 4294967295
C0085

C0085 | NTP: Activate network time protocol AutoUpdate Index: 24490d = 5FAAh
Activate global time levelling with an NTP server. Internet connection of the controller required.
0 1 0
C0086

C0086 | NTP: NTP server Index: 24489d = 5FA9h
Address of the NTP server to be used by the controller for global system time levelling.
C0090

C0090 | System: Date and time Index: 24485d = 5FA5h
Date and time

NaN
C0091

C0091 | Local date and time Index: 24484d = 5FA4h
Local date and time.

NaN
________________________________________________________________
C0092
________________________________________________________________
________________________________________________________________

C0092 | Time zone Index: 24483d = 5FA3h
Time zone of the device.

Possible values: "Central European Standard Time", "North Pacific Standard Time", "GMT Standard Time", ...
Afghanistan Standard Afghanistan Standard Time
Time
Alaskan Standard Time Alaska Standard Time
Arab Standard Time Arab Standard Time
Arabian Standard Time Arabian Standard Time
Arabic Standard Time Arabic Standard Time
Atlantic Standard Time Atlantic Standard Time
AUS Central Standard AUS Central Standard Time
Time
AUS Eastern Standard AUS Eastern Standard Time
Time
Azerbaijan Standard Azores Standard Time
Time
Azores Standard Time China Standard Time
Canada Central Standard Dateline Standard Time
Time
Cape Verde Standard E. Africa Standard Time
Time
Caucasus Standard Time E. Australia Standard Time
Cen. Australia Standard E. Europe Standard Time
Time
Central America E. South America Standard
Standard Time Time
Central Asia Standard Eastern Standard Time
Time
Central Brazilian Egypt Standard Time
Standard Time
Central Europe Standard Ekaterinburg Standard Time
Time
Central European Fiji Standard Time
Standard Time
Central Pacific Standard Malay Peninsula Standard
Time Time
Central Standard Time Mexico Standard Time
Central Standard Time Mexico Standard Time 2
(Mexico)
China Standard Time Mid-Atlantic Standard Time
Dateline Standard Time Mountain Standard Time
E. Africa Standard Time Myanmar Standard Time
E. Australia Standard N. Central Asia Standard
Time Time
E. Europe Standard Time Nepal Standard Time
E. South America New Zealand Standard Time
Standard Time
Eastern Standard Time Newfoundland Standard
Time
________________________________________________________________

Egypt Standard Time SE Asia Standard Time

Ekaterinburg Standard South Africa Standard Time
Time
Fiji Standard Time Sri Lanka Standard Time
FLE Standard Time Taipei Standard Time
Georgian Standard Time Tasmania Standard Time
GMT Standard Time Tokyo Standard Time
Greenland Standard Tonga Standard Time
Time
Greenwich Standard US Eastern Standard Time
Time
GTB Standard Time US Mountain Standard Time
Hawaiian Standard Time Vladivostok Standard Time
India Standard Time India Standard Time
Iran Standard Time Iran Standard Time
Israel Standard Time Jerusalem Standard Time
Jordan Standard Time Jordan Standard Time
Korea Standard Time Korea Standard Time
Mid-Atlantic Standard Mid-Atlantic Standard Time
Time
Middle East Standard Middle East Standard Time
Time
Mountain Standard Time Mountain Standard Time
Mountain Standard Time Mountain Standard Time
(Mexico) (Mexico)
________________________________________________________________

Myanmar Standard Time Myanmar Standard Time

N. Central Asia Standard N. Central Asia Standard
Time Time
Namibia Standard Time Namibia Standard Time
Nepal Standard Time Nepal Standard Time
New Zealand Standard New Zealand Standard Time
Time
Newfoundland Standard Newfoundland Standard
Time Time
North Asia East Standard North Asia East Standard
Time Time
North Asia Standard North Asia Standard Time
Time
Pacific SA Standard Time Pacific SA Standard Time
Pacific Standard Time Pacific Standard Time
Pacific Standard Time Pacific Standard Time
(Mexico) (Mexico)
Romance Standard Time Romance Standard Time
Russian Standard Time Russian Standard Time
SA Eastern Standard SA Eastern Standard Time
Time
Singapore Standard Time Malay Peninsula Standard
Time
SA Pacific Standard Time SA Pacific Standard Time
SA Western Standard SA Western Standard Time
Time
Samoa Standard Time Samoa Standard Time
SE Asia Standard Time SE Asia Standard Time
South Africa Standard South Africa Standard Time
Time
Sri Lanka Standard Time Sri Lanka Standard Time
Taipei Standard Time Taipei Standard Time
Tasmania Standard Time Tasmania Standard Time
Tokyo Standard Time Tokyo Standard Time
Tonga Standard Time Tonga Standard Time
US Eastern Standard US Eastern Standard Time
Time
US Mountain Standard US Mountain Standard Time
Time
Vladivostok Standard Vladivostok Standard Time
Time
W. Australia Standard W. Australia Standard Time
Time
W. Central Africa W. Central Africa Standard
Standard Time Time
W. Europe Standard Time W. Europe Standard Time
West Asia Standard Time West Asia Standard Time
West Pacific Standard West Pacific Standard Time
Time
________________________________________________________________

Yakutsk Standard Time Yakutsk Standard Time

C0093

C0093 | Locale Index: 24482d = 5FA2h
Selection of regional and language options

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

C0095 | Activate VNC server Index: 24480d = 5FA0h
Activate parameter to start the VNC server on the controller.

0 1 0
C0097

C0097 | Activate VisiWinNET Remote Access Index: 24478d = 5F9Eh
Activate parameter to start the VisiWinNET-Remote Access Manager on the controller.

0 1 1
________________________________________________________________
C0100

C0100 | WinCe users: Number Index: 24475d = 5F9Bh
Number of users registered

0 10
C0101

C0101 | WinCe users: User name 1 Index: 24474d = 5F9Ah
Name of the user

Default setting: admin
C0102

C0102 | WinCe users: Password 1 Index: 24473d = 5F99h
Password of the user

Default setting: admin
C0103

C0103 | WinCE-User: User with 1 FTP permissions Index: 24472d = 5F98h
User may use FTP

0 1 1
C0104

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
C0105

C0105 | FTP: Home user 1 Index: 24470d = 5F96h
Home directory of the user

________________________________________________________________
C0106

C0106 | WinCE-User: User 1 with telnet permissions Index: 24469d = 5F95h
User may use telnet

0 1 1
C0108

C0108 | WinCe-User: User name 2 Index: 24467d = 5F93h
Name of the user

C0109

C0109 | WinCe-User: Password 2 Index: 24466d = 5F92h

C0110

C0110 | WinCE-User: User 2 with FTP permissions Index: 24465d = 5F91h
User may use FTP

0 1 0
C0111


Value is bit-coded:
Bit 0 Allow Read
Bit 1 Allow Write
Bit 2 Virtual Roots
C0112

C0112 | FTP: Home user 2 Index: 24463d = 5F8Fh

________________________________________________________________
C0113

C0113 | WinCE user: User 2 with telnet permissions Index: 24462d = 5F8Eh
User may use telnet

0 1 0
C0115

C0115 | WinCe users: User name 3 Index: 24460d = 5F8Ch
Name of the user

C0116

C0116 | WinCe users: Password 3 Index: 24459d = 5F8Bh

C0117

C0117 | WinCE user: User 3 with FTP permissions Index: 24458d = 5F8Ah
User may use FTP

0 1 0
C0118


Value is bit-coded:
Bit 0 Allow Read
Bit 1 Allow Write
Bit 2 Virtual Roots
C0119


________________________________________________________________
C0120

C0120 | WinCE user: User 3 with telnet permissions Index: 24455d = 5F87h
User may use telnet

0 1 0
C0122

C0122 | WinCe users: User name 4 Index: 24453d = 5F85h
Name of the user

C0123


C0124

C0124 | WinCE users: User 4 with FTP permissions Index: 24451d = 5F83h
User may use FTP

0 1 0
C0125


Value is bit-coded:
Bit 0 Allow Read
Bit 1 Allow Write
Bit 2 Virtual Roots
C0126


________________________________________________________________
C0127

C0127 | WinCE users: User 4 with telnet permissions Index: 24448d = 5F80h
User may use telnet

0 1 0
C0129

C0129 | WinCe users: User name 5 Index: 24446d = 5F7Eh
Name of the user

C0130

C0130 | WinCe users: Password 5 Index: 24445d = 5F7Dh

C0131

C0131 | WinCE users: User 5 with FTP permissions Index: 24444d = 5F7Ch
User may use FTP

0 1 0
C0132

C0132 | FTP: Permissions user 5 Index: 24443d = 5F7Bh

Value is bit-coded:
Bit 0 Allow Read
Bit 1 Allow Write
Bit 2 Virtual Roots
C0133

C0133 | FTP: Home user 5 Index: 24442d = 5F7Ah

________________________________________________________________
C0134

User may use telnet

0 1 0
C0136

Name of the user

C0137


C0138

User may use FTP

0 1 0
C0139


Value is bit-coded:
Bit 0 Allow Read
Bit 1 Allow Write
Bit 2 Virtual Roots
C0140


________________________________________________________________
C0141

User may use telnet

0 1 0
C0143

Name of the user

C0144

C0144 | WinCe users: Password 7 Index: 24431d = 5F6Fh

C0145

C0145 | WinCE users: User 7 with FTP permissions Index: 24430d = 5F6Eh
User may use FTP

0 1 0
C0146

C0146 | FTP: Permissions user 7 Index: 24429d = 5F6Dh

Value is bit-coded:
Bit 0 Allow Read
Bit 1 Allow Write
Bit 2 Virtual Roots
C0147

C0147 | FTP: Home user 7 Index: 24428d = 5F6Ch

________________________________________________________________
C0148

C0148 | WinCE users: User 7 with telnet permissions Index: 24427d = 5F6Bh
User may use telnet

0 1 0
C0150

Name of the user

C0151


C0152

C0152 | WinCE users: User with 8 FTP permissions Index: 24423d = 5F67h
User may use FTP

0 1 0
C0153


Value is bit-coded:
Bit 0 Allow Read
Bit 1 Allow Write
Bit 2 Virtual Roots
C0154


________________________________________________________________
C0155

User may use telnet

0 1 0
C0157

C0157 WinCe users: User name 9 Index: 24418d = 5F62h
Name of the user

C0158


C0159

User may use FTP

0 1 0
C0160

C0160 | FTP: Permissions user 9 Index: 24415d = 5F5Fh

Value is bit-coded:
Bit 0 Allow Read
Bit 1 Allow Write
Bit 2 Virtual Roots
C0161

C0161 | FTP: Home user 9 Index: 24414d = 5F5Eh

________________________________________________________________
C0162

C0162 | WinCE users: User 9 with telnet permissions Index: 24413d = 5F5Dh
User may use telnet

0 1 0
C0164

C0164 | WinCe users: User name 10 Index: 24411d = 5F5Bh
Name of the user

C0165

C0165 | WinCe users: Password 10 Index: 24410d = 5F5Ah

C0166

User may use FTP

0 1 0
C0167


Value is bit-coded:
Bit 0 Allow Read
Bit 1 Allow Write
Bit 2 Virtual Roots
C0168


________________________________________________________________
C0169

User may use telnet

0 1 0
C0172

C0172 | FTP: Allow anonymous Index: 24403d = 5F53h
An unregistered user is allowed to log in. The user name is "anonymous"

• Entering "1" activates the log-in procedure
• Entering "0" deactivates the log-in procedure
0 1 0
C0173

C0173 | FTP: Allow anonymous upload Index: 24402d = 5F52h
An anonymous user is allowed to upload data to the controller if parameter ...

• ... FtpAllowAnonymousUpload = true and
• ... FtpAllowAnonymous = true.
0 1 1
C0174

C0174 | FTP: Enabled Index: 24401d = 5F51h
Activation of the FTP service

• Entering "1" activates the FTP service
• Entering "0" deactivates the FTP service
0 1 1
C0180

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
0 1 1
________________________________________________________________
C0181

C0181 | Telnet: Enabled Index: 24394d = 5F4Ah
Activation of the telnet service

• Entering "1" activates the telnet service
• Entering "0" deactivates the telnet service
0 1 1
C0182

C0182 | 0x100a: Software version Index: 24393d = 5F49h
Software version of the backplane bus Controller

• Applies to Controllers 3200 C
C0183

C0183 | 0x1009: Hardware version/FPGA firmware version Index: 24392d = 5F48h
Hardware version of the backplane bus Controller

Version of the FPGA (Field Programmable Gate Array)
• Applies to Controllers p500
C0184

C0184 | 0x100a: Software version Index: 24391d = 5F47h
Software version of the backplane bus master

C0185

C0185 | 0x1009: Hardware version Index: 24390d = 5F46h
Hardware version of the backplane bus master

C0186

C0186 | PLC: Licence Index: 24389d = 5F45h
Licence level of the PLC. Possible licence levels are:

• No licence
• Logic (LPC1000)
• Motion (MPC1200)
________________________________________________________________
C0187

C0187 | Visualisation licence Index: 24388d = 5F44h
Visualisation licence (relevant for the visualisation in VisiWinNET). Possible licence levels are:
• Compact CE
• Compact XP
C0188

C0188 | Visualisation: Number of power tags Index: 24387d = 5F43h
Max. number of variables that can be represented in VisiWinNET

13.3 Voltage buffering by external UPS (optional, for Controller 3241 C)
________________________________________________________________
This chapter lists all UPS parameters in numerically ascending order.

UPS functionality of the controllers ( 68)
C0203

C0203 | UPS: UPS monitoring Index: 24372d = 5F34h
Enable monitoring via an external UPS (optional)

0 Off
1 On
C0204

C0204 | UPS: Status Index: 24371d = 5F33h
Status of the external UPS

Selection list (read only) Info
0 ACU Controller is missing
85 Battery / capacitor is loaded
86 Battery / capacitor is being loaded
87 -
88 -
89 UPS is buffering the system
90 Battery / capacitor short circuit
91 Battery / capacitor is missing
92 Battery / capacitor is defective
93 ACU Controller is defective
94 -
95 Undefined status of battery /
capacitor
C0205
Parameter | Name: Data type: FLOAT_32

C0205 | UPS: Supply voltage Index: 24370d = 5F32h
Supply voltage of the external UPS in [V]

0 V 34
________________________________________________________________
C0207
Parameter | Name: Data type: FLOAT_32

C0207 | UPS: Battery / capacitor voltage Index: 24368d = 5F30h
Voltage of the battery/capacitor in [V]

V
C0208

C0208 | UPS: Display lighting after voltage failure Index: 24367d = 5F2Fh
Behaviour of the display lighting after a voltage failure.

0 Off Activate display lighting
1 On Deactivate display lighting
C0209

C0209 | UPS: Number of voltage dips Index: 24366d = 5F2Eh
Indicates the number of voltage failures.

0 255
C0210

C0210 | UPS: Supply voltage OK Index: 24365d = 5F2Dh
Status of the supply voltage

Selection list (read only) Info
0 No
1 Yes
C0211

C0211 | UPS: Voltage failure Index: 24364d = 5F2Ch
Status of voltage failure (present/not present)

Selection list (read only)
0 No
1 Yes
________________________________________________________________
C0212

C0212 | UPS: Firmware version Index: 24363d = 5F2Bh
Version of the UPS firmware

C0213

C0213 | UPS: Buffer time without action Index: 24362d = 5F2Ah
The UPS buffers the system without any further action. If the voltage dip lasts longer than the time set here:
• The PLC is stopped.
• The PLC saves the retain variables, logbook entries and visualisation data (trends and alarms).
• The timer C00214 is started.
0 0
250 250
500 500
750 750
1000 1000
1250 1250
1500 1500
1750 1750
2000 2000
2250 2250
2500 2500
2750 2750
3000 3000
3250 3250
3500 3500
3750 3750
4000 4000
4250 4250
4500 4500
4750 4750
5000 5000
C0214

C0214 | UPS: Buffer time until shutdown Index: 24361d = 5F29h
After expiration of the time set here, the system is shut down. If the voltage is applied once again, the system is
restarted automatically.
0 s 255 10 s
13.4 Ethernet (on board)
________________________________________________________________
This chapter provides a list of all parameters of the Ethernet interface (on board) of the controllers
in numerically ascending order.
C0238

C0238 | Apply IP configuration Index: 24337d = 5F11h
Parameter for the activation of the set IP configuration.

1 Activate device
0 No command
C0240

C0240 | Enable Dhcp Index: 24335d = 5F0Fh
Activation of the configuration. DHCP states:

• "0" = Inactive
• "1" = Active
If DHCP is active, parameters 241-245 do not have any function
0 1 0
C0241

C0241 | IP address Index: 24334d = 5F0Eh
IP address of the interface

C0242

C0242 | Subnet mask Index: 24333d = 5F0Dh
Subnet mask of the interface

C0243

C0243 | Default gateway Index: 24332d = 5F0Ch
Default gateway of the interface

________________________________________________________________
C0244

C0244 | Domain Index: 24331d = 5F0Bh
Domain name of the interface

C0246

C0246 | MAC address Index: 24329d = 5F09h
MAC address (6 8-bit hexadecimal numbers) (e.g. 00:af:13:42:01:a8)

13.5 EtherCAT
________________________________________________________________
13.5 EtherCAT
This chapter provides a list of all EtherCAT parameters of the EtherCAT interface (on board) of the
Controllers and the EtherCAT communication card MC-ETC in numerically ascending order.
C280/4

C280/4 | ECAT bus scan result Index: 24295.4d =
0x5EE7.0x04h
Brief information on whether the master configuration corresponds to the physical bus structure. The master
configuration of the stack is compared to the actual bus structure.
0 No match The master configuration does not correspond to the bus
structure.
1 OK The master configuration corresponds to the bus
structure.
C281/2

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
13.5 EtherCAT
________________________________________________________________
C281/5

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.
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 Match
Bit 11 Reserved 4
Bit 12 DC: Activated
Bit 13 DC: Synchronised
Bit 14 DC: Busy
Bit 15 Reserved 5
Bit 16 Link Up
Bit 17 Reserved 6
... ...
Bit 31 Reserved 20
C281/6

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

The fieldbus scan updates all EtherCAT codes.
0 No Operation
1 The bus is scanned
C282/2

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.
0 ns 4294967295
13.5 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.

-2147483647 ns 2147483647
C286/3

C286/3 | ECAT bus: No. of slaves Index: 24289.3d =
0x5EE1.0x03h
Number of slaves connected to the fieldbus

0 4294967295
C286/4

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

0 4294967295
C286/5

C286/5 | ECAT config.: No. of slaves Index: 24289.5d =
0x5EE1.0x05h
Number of slaves configured in the master configuration file

0 4294967295
C286/6

C286/6 | ECAT config.: No. of mailbox slaves Index: 24289.6d =
0x5EE1.0x06h
Number of mailbox slaves configured in the master configuration file

0 4294967295
13.5 EtherCAT
________________________________________________________________
C286/7

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

0 4294967295
C286/8

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

0 4294967295
C286/9

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

0 4294967295
C286/10

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

0 4294967295
C286/11

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

0 4294967295
13.5 EtherCAT
________________________________________________________________
C286/12

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

0 4294967295
C286/13

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

0 4294967295
C286/14

C286/14 | ECAT: Reset individual counters Index: 24289.14d =
0x5EE1.0x0Eh
Reset frame and datagram counters (C1086/7 ... 13)

0 No Operation
1 Reset - All counters
2 Reset - Tx frame counters
4 Reset - Rx frame counters
8 Reset - Lost frame counters
16 Clear Cyclical Frame Counter
32 Clear Cyclical Datagram Counter
64 Reset - Acyclic frame counters
128 Reset - Acyclic datagram counters
13.6 Monitor panel (integrated/external)
________________________________________________________________
This chapter lists all parameters of the monitor panel (panel controller) and the parameters of an
external, optional panel in numerically ascending order.
The parameters are available depending on the panel variant.
C0420

C0420 | Panel: Width Index: 24155d = 5E5Bh
Horizontal resolution of the panel

160 2400
C0421

C0421 | Panel: Height Index: 24154d = 5E5Ah
Vertical resolution of the panel

100 2000
C0422

C0422 | Dimout: Actual value Index: 24153d = 5E59h
Enter the actual brightness value of the display. The numerical value ranges from the
• Maximum = 0 and the
• Minimum = 63
0 63 0
C0423

C0423 | Brightness: Upper limit Index: 24152d = 5E58h
Enter the maximum brightness value of the display. The numerical value ranges from the
• Maximum = 0 and the
• Minimum = 63
0 63 0
________________________________________________________________
C0424

C0424 | Automatic dimout: Switch-on after Index: 24151d = 5E57h
Enter the time until automatic dimout of the display. The values range between ...
• ... 0 (maximum value = no dimout of the display) and
• ... 255 (minimum value)
Note:
To deactivate an active dimout of the display, an entry must be made (by activation of the touch display/mouse-
click/shortcut). Then the controller is ready to accept input.
• This is why the first entry only result in a deactivation of the dimout if this function is active. Afterwards further
entries are possible.
0 min 255 0 min
C0425

C0425 | Automatic dimout: Brightness value Index: 24150d = 5E56h
Brightness value of the monitor panel in its dimmed state after automatic dimout in [%].
• Applies to the integrated monitor panel (panel controller).
10 % 80 10 %
C0426

C0426 | Brightness: Actual value Index: 24149d = 5E55h
Actual brightness value of the monitor panel in [%]

• Applies to the integrated monitor panel (panel controller).
10 % 100 100 %
C0432

C0432 | F1 key: Function Index: 24143d = 5E4Fh
Function assignment of the F1 key. The individual functions are assigned from a selection list.
• Applies to external monitor panels with function keys.
0 None
1 Start program
2 Touch keyboard
3 Right-hand mouse button
4 Execute AP script
5 Start control panel
________________________________________________________________
C0433

C0433 | F1 key: Parameter Index: 24142d = 5E4Eh
Name of the program or script to be executed

C0434

C0434 | F2 key: Function Index: 24141d = 5E4Dh
0 None
1 Start program
2 Touch keyboard
4 Execute AP script
C0435

C0435 | F2 key: Parameter Index: 24140d = 5E4Ch

C0436

C0436 | F3 key: Function Index: 24139d = 5E4Bh
0 None
1 Start program
2 Touch keyboard
4 Execute AP script
________________________________________________________________
C0437

C0437 | F3 key: Parameter Index: 24138d = 5E4Ah

C0438

C0438 | F4 key: Function Index: 24137d = 5E49h
0 None
1 Start program
2 Touch keyboard
4 Execute AP script
C0439

C0439 | F4 key: Parameter Index: 24136d = 5E48h

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

C0620 | PLC: Status Index: 23955d = 5D93h
Status of the PLC application

C0630

C0630 | Display Soft PLC window Index: 23945d = 5D89h
Display/hide Soft PLC window on the controller

0 1
C0640

C0640 | Activate field device firmware update Index: 23935d = 5D7Fh
Activate firmware update of the field devices: The controller writes the parameters to the connected field devices.
• This function is available depending on the device!
0 1 1
C0650

C0650 | Start Field Device parameter storage Index: 23925d = 5D75h
Save the parameters of the connected field devices to the controller.

0 No Operation
1 Start parameter storage
C0651

C0651 | Status Field Device parameter storage Index: 23924d = 5D74h
Actual status of the storage of the field device parameters on the controller.
________________________________________________________________
C0660

C0660 | Available application credits Index: 23915d = 5D6Bh
Display of the available application credits

C0661

C0661 | Application credits used Index: 23914d = 5D6Ah
Display of the application credits used

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

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

0 Backup
C0810

C0810 | Select a main action for the Lenze software Index: 23765d = 5CD5h
Carry out a backup or restore by means of the WebConfig.

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

C0811 | Assign a name for the backup Index: 23764d = 5CD4h
C0813

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

1 Display 1 to 10
2 Display 11 to 20
3 Display 21 to 30
13.8 Backup&Restore
________________________________________________________________
C0814

C0814 | Backup or update file 1 Index: 23761d = 5CD1h
C0815

C0815 | Backup or update file 2 Index: 23760d = 5CD0h
C0816

C0816 | Backup or update file 3 Index: 23759d = 5CCFh
C0817

C0817 | Backup or update file 4 Index: 23758d = 5CCEh
C0818

C0818 | Backup or update file 5 Index: 23757d = 5CCDh
C0819

C0819 | Backup or update file 6 Index: 23756d = 5CCCh
C0820

C0820 | Backup or update file 7 Index: 23755d = 5CCBh
C0821

C0821 | Backup or update file 8 Index: 23754d = 5CCAh
C0822

C0822 | Backup or update file 9 Index: 23753d = 5CC9h
13.8 Backup&Restore
________________________________________________________________
C0823

C0823 | Backup or update file 10 Index: 23752d = 5CC8h
C0824

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

0 Nothing selected
1 Backup or update file 1
C0830

C0830 | Start backup Index: 23745d = 5CC1h

0 Do not carry out any action
1 Start backup
C0831

C0831 | Start restore update Index: 23744d = 5CC0h

0 Do not carry out any action
2 Start restore update
C0832

C0832 | Backup status Index: 23743d = 5CBFh
13.8 Backup&Restore
________________________________________________________________
C0833

C0833 | Restore update status Index: 23742d = 5CBEh
13.9 Communication cards: optional interface
________________________________________________________________
This chapter provides you with some information about the parameters of the optional controller
communication cards. The communication cards allow for a use of the controller with further bus
systems.
EtherCAT is the "on board" standard bus system of the Controllers.
 Note!
Controllers c300/p300 ...
• are equipped with an integrated CAN communication interface (on board);
• only support the CAN master functionality.
The optional MC-CAN2 communication card is not supported by the Controllers c300/
p300.
The following communication cards can be used with the controllers:

________________________________________________________________
13.9.1 CAN (MC-CAN2) communication card / CAN interface for Controller c300/p300
This chapter provides a list of all parameters of the communication card and the CAN interface of
the Controllers c300/p300 in numerically ascending order.
The MC-CAN2 communication card ...
• has two CAN connections/interfaces;
• is not supported by the Controllers c300/p300.
The Controllers c300/p300 only support the CAN master functionality.
 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!
C1031

C1031 | Device: Type key Index: 23544d = 5BF8h
Identification of the card

C1032

C1032 | Device: Type version Index: 23543d = 5BF7h
Version number of the card

C1033

C1033 | Device: Name Index: 23542d = 5BF6h
Device name of the card

C1034

C1034 | Device: Software Index: 23541d = 5BF5h
Software version of the card

C1035

C1035 | Device: Hardware Index: 23540d = 5BF4h
Hardware version of the card

________________________________________________________________
C1036

C1036 | Device: Serial number Index: 23539d = 5BF3h
Serial number of the card

C1037

C1037 | Device: Manufacturer Index: 23538d = 5BF2h
Manufacturer of the card

C1038

C1038 | Device: Manufacturing date Index: 23537d = 5BF1h
Manufacturing date of the card

Parameters of the first CAN interface
C1073

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

C1081 | Sync master: Interface index Index: 23494d = 5BC6h
Note: Restart the L-force Controller after changing this parameter!

4294967295
________________________________________________________________
C1082

C1082 | Baud rate Index: 23493d = 5BC5h
Baud rate of the CAN interface. The value is assigned from a selection list.
7 5
6 10
5 20
3 50
8 100
2 125
1 250
0 500
4 1000
C1090

C1090 | Tx PDO counter Index: 23485d = 5BBDh
PDO counter for sent CAN messages

C1091

C1091 | Rx PDO counter Index: 23484d = 5BBCh
PDO counter for received CAN messages

C1092

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
________________________________________________________________
C1093

C1093 | Error counter Index: 23482d = 5BBAh
Error counter since last initialisation of the CAN interface

C1094

C1094 | Last error code Index: 23481d = 5BB9h
Code of the last error that occurred

C1096

C1096 | CAN node ID Index: 23479d = 5BB7h

0 128 63
C1098

C1098 | Channel Index: 23477d = 5BB5h

0
Parameters of the second CAN interface
C1113

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

C1121 | Sync master: Interface index Index: 23454d = 5B9Eh
Note: Restart the L-force Controller after changing this parameter!

4294967295
C1122

C1122 | Baud rate Index: 23453d = 5B9Dh
Baud rate of the CAN interface. The value is assigned from a selection list.
7 5
6 10
5 20
3 50
8 100
2 125
1 250
0 500
4 1000
C1130

C1130 | Tx PDO counter Index: 23445d = 5B95h
PDO counter for sent CAN messages

C1131

C1131 | Rx PDO counter Index: 23444d = 5B94h
PDO counter for received CAN messages

________________________________________________________________
C1132

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
C1133

C1133 | Error counter Index: 23442d = 5B92h
Error counter since last initialisation of the CAN interface

C1134

C1134 | Last error code Index: 23441d = 5B91h
Code of the last error that occurred

C1136

C1136 | CAN node ID Index: 23439d = 5B8Fh

0 128 63
C1138

C1138 | Channel Index: 23437d = 5B8Dh

0
________________________________________________________________
13.9.2 PROFIBUS and PROFINET communication cards
This chapter provides a list of all parameters of the PROFINET IO/ device (MC-PND) and PROFIBUS
master/slave (MC-PBM/MC-PBS) communication cards in numerically ascending order.
C1031

C1031 | Device: Type key Index: 23544d = 5BF8h
Identification of the card

C1032

C1032 | Device: Type version Index: 23543d = 5BF7h
Version number of the card

C1033

C1033 | Device: Name Index: 23542d = 5BF6h
Device name of the card

C1034

C1034 | Device: Software Index: 23541d = 5BF5h
Software version of the card

C1035

C1035 | Device: Hardware Index: 23540d = 5BF4h
Hardware version of the card

C1036

C1036 | Device: Serial number Index: 23539d = 5BF3h
Serial number of the card

C1037

C1037 | Device: Manufacturer Index: 23538d = 5BF2h
Manufacturer of the card

________________________________________________________________
C1038

C1038 | Device: Manufacturing date Index: 23537d = 5BF1h
Manufacturing date of the card

Index
________________________________________________________________
0 ... 9 C
0x1009 C100 145
Hardware version (C183) 156 C101 145
Hardware version (C185) 156 C102 145
0x100a C103 145
Software version (C182) 156 C1031 179, 185
Software version (C184) 156 C1032 179, 185
C1033 179, 185
A
C1034 179, 185
Activate Explorer 134
C1035 179, 185
Activate field devices firmware update (C640) 172
C1036 180, 185
Activate front USB (C40) 133
C1037 180, 185
Activate Lenze standard settings (reset pushbutton) 32
C1038 180, 186
Activate standard settings (reset pushbutton) 32
C104 145
Activate VisiWinNET Remote Access (C97) 144
C105 145
Activate VNC server (C95) 144
C106 146
Activate Windows® CE interface 92
C1073 180
Allocated flash memory (C78) 137
C108 146
Allocated program memory (C71) 137
C1081 180
Allocated virtual file memory (C75) 137
C1082 181
Application notes 13
C109 146
Apply IP configuration (C238) 161
C1090 181
Assign a name for the backup (C811) 174
C1091 181
Automatic data update (after device replacement) 75
C1092 181
Automatic dimout
C1093 182
brightness value (C425) 169
C1094 182
switch-on after (C424) 169
C1096 182
B C1098 182
C110 146
Backup & Restore (parameters) 174
C111 146
Backup or update file 1 (C814) 175
C1113 182
C112 146
C1121 183
C1122 183
C113 147
C1130 183
C1131 183
C1132 184
C1133 184
C1134 184
Backup status (C832) 176
C1136 184
Backup&Restore 67
C1138 184
Basic parameters of the Lenze Controllers 131
C115 147
Baud rate (C1082) 181
C116 147
Baud rate (C1122) 183
C117 147
Bootloader: Version (C36) 133
C118 147
Brightness
actual value (C426) 169 C119 147
Upper limit (C423) 168 C120 148
Bus coupler module, tab 42 C122 148
Bus load (C1092) 181 C123 148
Bus load (C1132) 184 C124 148
Index
________________________________________________________________
C125 148 C187 157

C126 148 C188 157
C127 149 C19 132
C129 149 C20 133
C13 131 C203 158
C130 149 C204 158
C131 149 C205 158
C132 149 C207 159
C133 149 C208 159
C134 150 C209 159
C136 150 C210 159
C137 150 C211 159
C138 150 C212 160
C139 150 C213 160
C140 150 C214 160
C141 151 C238 161
C143 151 C240 161
C144 151 C241 161
C145 151 C242 161
C146 151 C243 161
C147 151 C244 162
C148 152 C246 162
C15 132 C25 133
C150 152 C280/4 | ECAT bus scan result 163
C151 152 C281/2 | ECAT Master: State 163
C152 152 C281/5 | ECAT master: State information 164
C153 152 C281/6 | ECAT bus scan 164
C154 152 C282/2 | ECAT DC: Perm. dev. slave sync 164
C155 153 C282/3 | ECAT DC: Current deviation 165
C157 153 C286/10 | ECAT counter - Cyclical frames 166
C158 153 C286/11 | ECAT counter - Cyclical datagrams 166
C159 153 C286/12 | ECAT counter - Acyclical frames 167
C16 132 C286/13 | ECAT counter - Acyclical datagrams 167
C160 153 C286/14 | ECAT Clear specific counters 167
C161 153 C286/3 | ECAT bus - No. of slaves 165
C162 154 C286/4 | ECATBus - No. of slaves with DC 165
C164 154 C286/5 | ECAT config.: No. of slaves 165
C165 154 C286/6 | ECAT config.: No. of mailbox slaves 165
C166 154 C286/7 | ECAT counter: Tx frames 166
C167 154 C286/8 | ECAT counter: Rx frames 166
C168 154 C286/9 | ECAT counter: Lost frames 166
C169 155 C3 131, 174
C172 155 C30 133
C173 155 C36 133
C174 155 C4 131
C18 132 C40 133
C180 155 C41 133
C181 156 C42 134
C182 156 C420 168
C183 156 C421 168
C184 156 C422 168
C185 156 C423 168
C186 156 C424 169
Index
________________________________________________________________
C425 169 C814 175

C426 169 C815 175
C43 134 C816 175
C432 169 C817 175
C433 170 C818 175
C434 170 C819 175
C435 170 C820 175
C436 170 C821 175
C437 171 C822 175
C438 171 C823 176
C439 171 C824 176
C48 134 C830 176
C49 134 C831 176
C5 131 C832 176
C50 134 C833 177
C51 135 C85 138
C52 135 C86 138
C53 135 C90 138
C54 135 C91 138
C55 135 C92 141
C56 136 C93 144
C57 136 C95 144
C58 136 C97 144
C6 131 Cabinet Controller 22
C620 172 CAN node ID (C1096) 182
C630 172 CAN node ID (C1136) 184
C64 136 CAN parameters 179
C640 172 Channel (C1098) 182
C650 172 Channel (C1138) 184
C651 172 Command (C18) 132
C660 173 Command status (C19) 132
C661 173 Communication cards: optional interface (parameters) 178
C7 131 Configure OPC tunnel 119
C70 136 Connect Controller/replacement device 73
C71 137 Control elements of the controllers 31
C72 137 Controller 22
C75 137 Establishing an automatic dial-up connection 33
C76 137 Controller basic parameters 131
C78 137 Controller c300/p300 does not start (error case) 32
C79 138 Conventions used 10
C8 131 CPU
C809 174 Firmware version (C25) 133
C810 174 Name (C20) 133
C811 174 Temperature (C30) 133
C813 174 Creating retain variables 64
Index
________________________________________________________________
D Engineering tools 20
Data transfer via FTP 85 Entering the IP address 33
Data types 128 Error case: Controller c300/p300 does not start 32
Default gateway (C243) 161 Error counter (C1093) 182
Device Error counter (C1133) 184
Driver index (C1073) 180 Error messages - backplane bus 43
Driver index (C1113) 182 Error messages after a device replacement 78
Hardware version (C1035) 179, 185 EtherCAT parameters 163
Hardware version (C5) 131 Ethernet parameters 161
Identification (C1031) 179, 185 External voltage buffering (UPS parameter) 158
Manufacturer (C1037) 180, 185
Manufacturer (C7) 131 F
Manufacturing date (C1038) 180, 186
F1 key
Manufacturing date (C8) 131
Function (C432) 169
Name (C1033) 179, 185
Parameter (C433) 170
Name (C3) 131
F2 key
Serial number (C1036) 180, 185
Function (C434) 170
Serial number (C6) 131
Software version (C1034) 179, 185
F3 key
Software version (C4) 131
Function (C436) 170
Version (C1032) 179, 185
Device replacement (error messages) 78
F4 key
Diagnostics 79
Function (C438) 171
Diagnostics via Telnet 82
Diagnostics with the logbook 89
Feedback to Lenze 194
Dimout: actual value (C422) 168
Fieldbus communication (interfaces) 17, 23
Direct driver "LogicAndMotionV3" 101
FPGA firmware version (C183) 156
Display of the backup or update files (C813) 174
FTP
Display Soft PLC window (C630) 172 Allow "Anonymous" (C172) 155
Domain (C244) 162 Allow "Anonymous" upload (C173) 155
Enabled (C174) 155
E Home user 1 (C105) 145
EASY Navigator 21 Home user 10 (C168) 154
ECAT bus - No. of slaves (C286/3) 165 Home user 2 (C112) 146
ECAT bus scan - compliance (C280/4) 163 Home user 3 (C119) 147
ECAT bus scan (C281/6) 164 Home user 4 (C126) 148
ECAT Clear specific counters (C286/14) 167 Home user 5 (C133) 149
Home user 6 (C140) 150
ECAT config.
No. of mailbox slaves (C286/6) 165
No. of slaves (C286/5) 165
ECAT counter
Permissions user 1 (C104) 145
Lost frames (C286/9) 166
Rx frames (C286/8) 166
Tx frames (C286/7) 166
ECAT counter - Acyclical datagrams (C286/13) 167
ECAT counter - Acyclical frames (C286/12) 167 Permissions user 5 (C132) 149
ECAT counter - Cyclical datagrams (C286/11) 166 Permissions user 6 (C139) 150
ECAT counter - Cyclical frames (C286/10) 166 Permissions user 7 (C146) 151
ECAT DC - Current deviation (C282/3) 165 Permissions user 8 (C153) 152
ECAT DC - Perm. dev. slave sync (C282/2) 164 Permissions user 9 (C160) 153
ECAT Master: State (C281/2) 163 FTP and web settings in the Internet Explorer 87
ECAT Master: State information (C281/5) 164 FTP settings with the »WebConfig« 86
ECATBus - No. of slaves with DC (C286/4) 165 Function blocks 60
E-mail to Lenze 194
Enable Dhcp (C240) 161
Index
________________________________________________________________
I O
I/O compound module, tab 42 Online connection between the Engineering PC and Industrial
I/O modules at the backplane bus 39 PC 46
Identification of the Controller 31 OPC tunnel for external visualisation 120
Identification of the controller 31 Operating systems of the Controllers 60
Interfaces for fieldbus communication 17, 23 Operating time (C41) 133
IP address (C241) 161
P
L Panel
L_Util_Retain 65 Height (C421) 168
L_Util_Retain - saving retain data of the controller 65 Width (C420) 168
Last error code (C1094) 182 Panel Controller 22
Last error code (C1134) 184 Parameter (external voltage buffering UPS) 158
Layout of the safety instructions 13 Parameter attributes 130
LEDs of the Controllers 80 Parameter description (structure) 128
Local date and time (C91) 138 Parameter reference 127
Locale (C93) 144 Parameterising the controller 45
Logbook Parameters (Backup & Restore) 174
Entry count to auto persist (C49) 134 Parameters (CAN interface/MC-CAN2) 179
Index of last entry (C57) 136 Parameters (communication cards: optional interface) 178
Index of last entry on CF (C56) 136 Parameters (EtherCAT) 163
Index of oldest entry (C54) 135 Parameters (Ethernet) 161
Max. entries (C50) 134 Parameters (Monitor Panel) 168
Number of entries in RAM (C52) 135 Parameters (PLC Logic/Motion) 172
Size on CF (C51) 135 Parameters (PROFIBUS, MC-PBM/MC-PBS) 185
Time of last entry (C58) 136 Parameters (PROFINET, MC-PND) 185
Time of last entry on CF (C55) 135
Parameters of the Lenze Controllers (basic parameters) 131
Time of last error entry (C64) 136
PLC
Time of oldest entry (C53) 135
Licence (C186) 156
Time to auto persist (C48) 134
Status (C620) 172
Logbook parameters 91
PLC (Logic/Motion) parameters 172
Logbook query via the »WebConfig« 90
Pointer - c300/p300 62
Logic (runtime software) 25
PROFIBUS parameters 185
LogicAndMotionV3 (direct driver) 101
PROFIBUS/PROFINET communication cards 57
PROFINET parameters 185
M
MAC address (C246) 162
R
MC-CAN2 communication card (parameters) 179
Ratio: Data/program memory (C70) 136
MC-PBM/MC-PBS communication card (parameters) 185
Remote Display: Remote control of Controller via Internet or
MC-PND communication card (parameters) 185 LAN 94
Memory sizes of the controllers 60, 61 Remote maintenance and diagnostics 79
Monitor Panel (parameters) 168 Remove Controller 72
Motion (runtime software) 25 Replacement devices for the Controller 73
Replacing the controller (in the event of service) 72
N
Reset pushbutton 32
Navigator 21
Restore update status (C833) 177
NTP
Runtime software of the Lenze Controllers 24
Activate network time protocol AutoUpdate (C85) 138
Rx PDO counter (C1091) 181
NTP server (C86) 138
Rx PDO counter (C1131) 183
Number of reboots (C42) 134
Index
________________________________________________________________
S U
Safety 14 UPS
Safety instructions 13 Battery / capacitor voltage (C207) 159
Screenshots 7 Buffer time until shutdown (C214) 160
Select a backup or update (C824) 176 Buffer time without action (C213) 160
Select a main action for the Lenze software (C809) 174 Display lighting after voltage failure (C208) 159
External UPS (for Controllers 3241 C with UPS connection) 69
Select a main action for the Lenze software (C810) 174
Firmware version (C212) 160
Selecting the IP address of the controller: With file 36
Internal UPS (for Controllers without UPS connection) 68
Setting IP addresses 46
Number of voltage dips (C209) 159
Settings in the »WebConfig« 83 Status (C204) 158
Software (Engineering tools) 20 Supply voltage (C205) 158
Start backup (C830) 176 Supply voltage OK (C210) 159
Start Field Device parameter storage (C650) 172 UPS monitoring (C203) 158
Start Field Device parameter storage (C660) 173 Voltage failure (C211) 159
Start Field Device parameter storage (C661) 173 UPS (Uninterrupted power supply) 68
Start restore update (C831) 176 UPS parameter 158
Status Field Device parameter storage (C651) 172 Used flash memory (C79) 138
Status LEDs of the Controllers 80 Used program memory (C72) 137
Structure of the parameter description 128 Used virtual file memory (C76) 137
Structure of the safety instructions 13 Using the direct driver for visualisations under Windows CE
Subnet mask (C242) 161 102
Subsequent use of retain data after device replacement 77 Using the direct driver for visualisations under Windows XP
111
Sync master
Interface index (C1081) 180 Using your own wallpaper on the controller (Windows CE) 38
Interface index (C1121) 183
System: Date and time (C90) 138
V
System architecture: PLC Designer - controller access 59 Virtual Network Computing (VNC) 95
System identification Visu (runtime software) 26
Description (C16) 132 Visualisation: Number of power tags (C188) 157
Name (C13) 131 Visualisation licence (C187) 157
User name (C15) 132
System structure of the Controller-based Automation 15
T
Tabs of the I/O modules at the backplane bus 42
Target group 7
telnet
Enabled (C181) 156
Use authentication (C180) 155
Terms 11
Time zone (C92) 141
Tx PDO counter (C1090) 181
Tx PDO counter (C1130) 183
Index
________________________________________________________________
W
Web settings in the Internet Explorer 87
WebConfig - user interface 48
WinCe users
Number (C100) 145
Password 1 (C102) 145
User 1 with FTP permissions (C103) 145
User 1 with telnet permissions (C106) 146
User name 1 (C101) 145
User name 10 (C164) 154
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.
Perhaps we have not succeeded in achieving this objective in every
respect. If you have suggestions for improvement, please e-mail us
to:
feedback-docu@lenze.com
Thank you very much for your support.

Your Lenze documentation team
194
Controller | Parameter setting & programming · Reference Manual · SHGPCBAUTO-001 · 13461042 · DMS 1.5 EN · 04/2014 · TD17
Lenze Automation GmbH

Postfach 10 13 52, D-31763 Hameln
Hans-Lenze-Straße 1, D-31855 Aerzen
Germany
+49 5154 82-0
+49 5154 82-2800
lenze@lenze.com
www.lenze.com
Service
Lenze Service GmbH
Breslauer Straße 3, D-32699 Extertal
Germany
008000 24 46877 (24 h helpline)
+49 5154 82-1112
service@lenze.com

Controller: Automation Systems

Uploaded by

Copyright:

Available Formats

Controller: Automation Systems

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Controller: Automation Systems

Uploaded by

Copyright:

Available Formats

Automation Systems

Parameter setting and programming _ _ _ _ _ _ _ _ _ Reference Manual EN

1 About this documentation _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 6

3 Controller-based Automation: Central motion control _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 15

5 Commissioning the controller _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 30

6 Parameter setting using »WebConfig« _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 45

7 Programming with the »PLC Designer« _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 58

8 »Backup & Restore« (data backup/restore) _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 67

9 Data integrity in the event of a voltage failure _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 68

10 Device replacement - replacing the controller (in the event of service) _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 72

11 Remote maintenance and diagnostics _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 79

12 Visualisation with »VisiWinNET®« _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 96

13 Parameter reference _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 127

Your opinion is important to us _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 194

1 About this documentation

Documentation type Subject

More technical documentation for Lenze components

Mounting & wiring Symbols:

Information regarding the validity

Example: Controller 3241 C with connected I/O system 1000

Example: Controller c300 with connected I/O system 1000

Example: Controller p500

 Operating instructions/mounting instructions of the Controllers

1.1 Document history

1.2 Conventions used

Type of information Highlighting Examples/notes

1.3 Terminology used

»Backup & Restore« – back up/restore/update data

1.4 Definition of the notes used

 Pictograph and signal word!

Pictograph Signal word Meaning

Pictograph Signal word Meaning

3 Controller-based Automation: Central motion control

Lenze supply specially matched system components:

"Logic & Motion" runtime software

Area Cabinet Controller Panel Controller

4.1 Engineering tools

»EASY Navigator«: Starting the suitable Engineering tool

The »EASY Navigator« ...

What would you like to do? Button Engineering tool

Online diagnostics »EASY Starter« 1)

Online parameterisation »EASY Starter« 1)

1) For Controllers c300/p300 in preparation

4.2 Controller: The control centre of the Controller-based Automation

Cabinet controllers: Compact control cabinet design

Panel controllers: controlling and visualising

 Operating instructions for the Controller

Area Cabinet Controller Panel Controller

4.3 Runtime software of the Lenze Controllers

Differences between "Logic" and "Motion"

The controller controls... The controller controls extensive motion sequences.

4.3.1 "Logic" runtime software

4.3.2 "Motion" runtime software

4.3.3 "Visu" runtime software

4.3.3.1 Sample topology 1: External monitor panel/display for cabinet controllers

4.3.3.2 Sample topology 2: Separate control and visualisation

4.3.3.3 Sample topology 3: Independent control and visualisation (CANopen)

5 Commissioning the controller

 Read the mounting instructions supplied before you start working!