Lenze PROFINET Controller-based Automation User Manual
Automation Systems
Controller-based
Automation
PROFINET®
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Communication Manual EN
Ä.O5^ä
13462061
L
Contents
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
1 About this documentation _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 3
1.1 Document history _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 5
1.2 Conventions used _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 5
1.3 Terminology used _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 6
1.4 Definition of the notes used _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 7
2Safety instructions _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 8
3 Controller-based Automation: Central motion control _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 9
4 The Lenze automation system with PROFINET _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 12
4.1 Structure of the PROFINET system _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 13
4.2 Network topology _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 14
4.3 Field devices _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 15
4.4 PROFINET hardware for Lenze Controllers _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 16
4.5 Lenze Engineering tools _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 17
5 Technical data _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 18
5.1 Technical data of the MC-PND communication card _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 18
5.2 PROFINET connection _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 19
6 Commissioning of the PROFINET _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 20
6.1 Overview of the commissioning steps _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 20
6.2 The commissioning steps in detail _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 21
6.2.1 Planning the bus topology _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 21
6.2.2 Installing field devices _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 21
6.2.3 Create a project folder _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 22
6.2.4 Commissioning the field devices _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 22
6.2.5 Importing missing devices / device description files _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 23
6.2.6 Creating a PLC program with a target system (Logic) _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 24
6.2.7 Configuring the communication parameters _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 26
6.2.8 Creating a control configuration (adding field devices) _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 28
6.2.9 Configuring the I/O device _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 31
6.2.10 Logging in on the controller with the »PLC Designer« _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 31
7 Mixed operation PROFINET with EtherCAT _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 32
8 Defining the cycle time of the PLC project _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 33
8.1 Determining the task utilisation of the application _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 33
8.2 Optimising the system _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 35
9Diagnostics _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 36
9.1 LED status displays of the MC-PND communication card _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 37
9.2 Diagnostics in the »PLC Designer« _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 38
10 Parameter reference _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 39
Index _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 41
Your opinion is important to us _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 43
2 Lenze · Controller-based Automation · PROFINET® Communication Manual · DMS 1.2 EN · 04/2014 · TD17
1 About this documentation
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
1 About this documentation
This documentation ...
• contains detailed information about the commissioning, configuration, and diagnostics of the
PROFINET® bus system as part of the Lenze automation system Controller-based Automation.
• 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
Online helps
Reference manuals
Online helps
Software manuals
Online helps
Bus systems
• Controller-based Automation EtherCAT®
• Controller-based Automation CANopen®
• Controller-based Automation PROFIBUS®
• Controller-based Automation PROFINET®
Lenze Controller:
• Controller 3200 C
• Controller c300
• Controller p300
• Controller p500
Lenze Engineering Tools:
• »PLC Designer«: Programming
• »Engineer«: Inverter configuration
• »VisiWinNET® Smart«: Visualisation
• »Backup & Restore«: Back up/restore data
Lenze · Controller-based Automation · PROFINET® Communication Manual · DMS 1.2 EN · 04/2014 · TD17 3
1 About this documentation
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
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
• Controller
• Communication cards (MC-xxx)
• I/O system 1000 (EPM-Sxxx)
• 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
•L-force 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)
Printed documentation
Online help in the Lenze Engineering
Tool (also available as PDF file at
www.lenze.com
.)
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 plan, install, commission and maintain the
networking of devices as part of the Lenze automation system "Controller-based Automation".
Information on validity
The information provided in this documentation is valid for the Lenze automation system
"Controller-based Automation" from version 3.
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.
4 Lenze · Controller-based Automation · PROFINET® Communication Manual · DMS 1.2 EN · 04/2014 · TD17
1 About this documentation
1.1 Document history
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
1.1 Document history
Version Description
1.0 03/2013 TD17 First edition
1.1 11/2013 TD17 Revision on the Lenze automation system"Controller-based Automation",
1.2 04/2014 TD17 Revision on the Lenze automation system"Controller-based Automation",
release 3.6
release 3.8
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 Normal spelling Example: 1234
Decimal separators Point The decimal point is generally used.
For example: 1234.56
Hexadecimal 0x[0 ... 9, A ... F] Example: 0x60F4
Binary
• Nibble
Text
Program name » « PC software
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
Sequence of menu
commands
Shortcut <bold> Use <F1> to open the online help.
Program code Courier IF var1 < var2 THEN
Keyword Courier bold
Hyperlink underlined
Symbols
Page reference ( 5) Optically highlighted reference to another page. Can be
Step-by-step instructions
0b[0, 1] Example: ’0b0110’
Example: ’0b0110.0100’
Example: Lenze »Engineer«
tab ... / The Name input field ...
If several successive commands are required for
executing a function, the individual commands are
separated from each other by an arrow: Select the
command File
If a key combination is required for a command, a "+" is
placed between the key identifiers: With
<Shift>+<ESC>...
a = a + 1
END IF
Optically highlighted reference to another topic. Can be
activated with a mouse-click in this documentation.
activated with a mouse-click in this documentation.
Step-by-step instructions are marked by a pictograph.
Open to...
Lenze · Controller-based Automation · PROFINET® Communication Manual · DMS 1.2 EN · 04/2014 · TD17 5
1 About this documentation
1.3 Terminology used
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
1.3 Terminology used
Term Meaning
CL-RPC Connectionless Remote Procedure Call
Code Parameter for parameterising or monitoring the field device. The term is also
Controller The controller is the central component of the automation system which
Engineering PC The Engineering PC and the Engineering tools installed serve to configure and
Engineering tools Lenze software solutions for simply engineering in all phases:
Fieldbus stations Controller (PLC) and inverter integrated into the bus system (PROFINET)
Field device
GSDML file A GSDML file described the properties of a field device.
I/O device PROFINET slave
I/O master PROFINET master
Inverter Generic term for Lenze frequency inverters, Servo Inverters
PDO Process Data Object
PLC Programmable Logic Controller
RT over UDP Real Time over User Datagram Protocol
Subcode If a code contains several parameters, they are stored in so-called "subcodes".
referred to as "index" in common usage.
controls the Logic and Motion functionalities (by means of the runtime
software).
The controller communicates with the field devices via the fieldbus.
parameterise the system.
The Engineering PC communicates with the controller via Ethernet.
• »EASY Starter«
• »Engineer«
•»PLC Designer«
•»WebConfig«
•»VisiWinNET®«
•»IPC Backup & Restore«
Lenze Engineering tools
Siemens software for programming and configuring Siemens SIMATIC S7 PLC:
•»STEP7«
EtherCAT® (Ethernet for Controller and Automation Technology) is an Ethernetbased fieldbus system which fulfils the application profile for industrial realtime systems.
EtherCAT® is a registered trademark and patented technology, licensed by
Beckhoff Automation GmbH, Germany.
It is described with the XML-based language GSDML (General Station
Description Markup Language).
The I/O master takes over the master function for data communication of the
decentralised field devices. The I/O master is usually the communication
interface of a PLC.
(German designation: SPS - Speicherprogrammierbare Steuerung)
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.
This manual uses a slash "/" as a separator between code and subcode
(e.g. "C00118/3").
In normal usage, the term is also referred to as "Subindex".
( 17)
6
Lenze · Controller-based Automation · PROFINET® Communication Manual · DMS 1.2 EN · 04/2014 · TD17
1 About this documentation
1.4 Definition of the notes used
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
1.4 Definition of the notes used
The following signal words and symbols are used in this documentation 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
Danger! Danger of personal injury through a general source of danger
Stop! Danger of material damage
Application notes
Reference to an imminent danger that may result in death or serious personal
injury unless the corresponding measures are taken.
Reference to an imminent danger that may result in death or serious personal
injury unless the corresponding measures are taken.
Indicates a potential danger that may lead to material damage unless the
corresponding measures are taken.
Pictograph Signal word Meaning
Note! Important note to ensure troublefree operation
Tip! Useful tip for easy handling
Reference to another document
Lenze · Controller-based Automation · PROFINET® Communication Manual · DMS 1.2 EN · 04/2014 · TD17 7
2 Safety instructions
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
2 Safety instructions
Observe the following safety instructions if you want to commission an inverter or a system with
the Lenze controller.
Read the documentation supplied with the system components carefully before you
start commissioning the devices and the Lenze controller!
The system manual contains safety instructions which must be observed!
Danger!
Risk of injury
There is risk of injury by ...
• unpredictable motor movements (e.g. an unintended direction of rotation, too high
speeds, or jerky movement);
• impermissible operating states during the parameterisation while there is an active
online connection to the device.
Possible consequences
Death or severe injuries
Protective measures
• If required, provide systems with installed inverters with additional monitoring and
protective devices according to the safety regulations valid in each case (e.g. law on
technical equipment, regulations for the prevention of accidents).
• During commissioning, maintain an adequate safety distance to the motor or the
machine parts driven by the motor.
Stop!
Damage or destruction of machine parts
Damage or destruction of machine parts can be caused by ...
• unpredictable motor movements (e.g. an unintended direction of rotation, too high
speeds, or jerky movement);
• impermissible operating states during the parameterisation while there is an active
online connection to the device.
Possible consequences
Damage or destruction of machine parts
Protective measures
If required, provide systems with installed inverters with additional monitoring and
protective devices according to the safety regulations valid in each case (e.g. law on
technical equipment, regulations for the prevention of accidents).
8 Lenze · Controller-based Automation · PROFINET® Communication Manual · DMS 1.2 EN · 04/2014 · TD17
3 Controller-based Automation: Central motion control
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
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.
Note!
In the Lenze automation system, no PROFINET master functionality is supported. In a
PROFINET network, a Lenze Controller can only be driven as I/O device (slave), e.g. by a
Siemens SIMATIC S7 PLC.
System structure of the Controller-based Automation: "All from one single source"
[3-1] Example: PROFINET with a Siemens SIMATIC S7 PLC (Lenze Controller 3221 C with I/O system 1000 and Servo Drive 9400 as
I/O devices)
Lenze · Controller-based Automation · PROFINET® Communication Manual · DMS 1.2 EN · 04/2014 · TD17 9
3 Controller-based Automation: Central motion control
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Lenze provides especially coordinated system components:
• Engineering software
The Lenze Engineering tools
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 provides the control and/or visualisation of
motion sequences. The following 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)
( 17) on your Engineering PC (Windows operating system ) serve
"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 for instance the case if the field devices, for example, are to move in a synchronised way
or if position setpoints are to be transmitted.
10 Lenze · Controller-based Automation · PROFINET® Communication Manual · DMS 1.2 EN · 04/2014 · TD17
3 Controller-based Automation: Central motion control
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
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)
Ethernet1212
EtherCAT 1
CANopen 1
Optional interfaces (communication cards)
CANopen
MC-CAN2
PROFIBUS master
MC-PBM
PROFIBUS slave
MC-PBS
PROFINET device
MC-PND
1)
2)
- -
- -
- -
- -
11
-1
1)
2)
1
-
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®
• Controller-based Automation CANopen®
• Controller-based Automation PROFIBUS®
• Controller-based Automation PROFINET®
Lenze · Controller-based Automation · PROFINET® Communication Manual · DMS 1.2 EN · 04/2014 · TD17 11
4 The Lenze automation system with PROFINET
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
4 The Lenze automation system with PROFINET
Note!
• In the Lenze automation system, no PROFINET master functionality is supported. In a
PROFINET network, a Lenze Controller can only be driven as I/O device (slave), e.g. by
a Siemens SIMATIC S7 PLC.
• In the Lenze automation system, Logic field devices can be exclusively operated via
PROFINET. Thus, as an I/O device, the Lenze Controller is a Logic field device.
• The motion functionality is not supported when PROFINET is used. Always use
EtherCAT to connect inverters to be controlled via the central Motion functionality.
Mixed operation PROFINET with EtherCAT
This chapter provides basic information about ...
• the structure of the Lenze automation system using the PROFINET bus system;
• the Lenze Engineering tools required for commissioning;
• the interaction of the components.
( 32)
We recommend using PROFINET for the following applications:
• Equipment and extension of system parts that have already been automated with PROFINET
before.
• Use of field devices that are not available for e.g. EtherCAT, CANopen or PROFIBUS.
• The combination of PROFINET with EtherCAT is possible.
Tip!
Detailed information about PROFINET can be found on the website of the PROFIBUS &
PROFINET user organisation:
www.profibus.com
12 Lenze · Controller-based Automation · PROFINET® Communication Manual · DMS 1.2 EN · 04/2014 · TD17
4 The Lenze automation system with PROFINET
4.1 Structure of the PROFINET system
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
4.1 Structure of the PROFINET system
[4-1] Example: PROFINET configuration with a Siemens SIMATIC S7-PLC (Lenze Controller 3221 C with I/O system 1000 and Servo
Drives 9400 as I/O devices)
Usually, field devices with PROFINET interface with an existing GSDML file can be used in a
PROFINET network.
In the example (fig [4-1]
Servo Drives 9400 are driven as I/O devices by a Siemens SIMATIC S7 PLC.
The Lenze Controller is configured in the »PLC Designer« (see Commissioning of the PROFINET
( 20)). When you log in with the »PLC Designer«, the configuration data is loaded into the Lenze
Controller via Ethernet.
In order to integrate a Lenze Controller or other Lenze field devices into a »STEP7« project use the
GSDML file of the device to be integrated.
), the Lenze Controller 3221 C together with the I/O system 1000 and two
Tip!
GSDML files of the Lenze Controllers and of other Lenze devices are provided in the
download area at:
www.lenze.com
Lenze · Controller-based Automation · PROFINET® Communication Manual · DMS 1.2 EN · 04/2014 · TD17 13
4 The Lenze automation system with PROFINET
M
D
D
D
D
M
D
D
D
sw
D
D
D
sw
D
D
D
sw
D
D
D
M
4.2 Network topology
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
4.2 Network topology
It is typical of PROFINET to have a rather free topology, the limiting factor of which is large message
latencies due to e.g. switches connected in series.
PROFINET supports the following topologies:
Line topology
[4-2] Line topology (M = I/O master, D = I/O device)
Star topology
[4-3] Star topology (M = I/O master, D = I/O device)
Tree topology
[4-4] Tree topology via switches (M = IO master, SW = switch, D = I/O device)
14
Lenze · Controller-based Automation · PROFINET® Communication Manual · DMS 1.2 EN · 04/2014 · TD17
Loading...