Lenze PROFIBUS Controller-based Automation User Manual
Automation Systems
Controller-based
Automation
PROFIBUS®
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Communication Manual EN
Ä.O5~ä
13462093
L
Contents
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
1 About this documentation _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 4
1.1 Document history _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 6
1.2 Conventions used _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 7
1.3 Terminology used _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 8
1.4 Definition of the notes used _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 9
2Safety instructions _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 10
3 Controller-based Automation: Central motion control _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 11
4 The Lenze automation system with PROFIBUS _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 14
4.1 Brief description of PROFIBUS _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 14
4.1.1 Structure of the PROFIBUS system _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 15
4.1.2 Basic wiring of PROFIBUS _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 17
4.1.3 Field devices _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 19
4.2 PROFIBUS hardware for Lenze Controllers _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 20
4.3 Lenze Engineering tools _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 21
5 Technical data _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 22
5.1 Technical data of the MC-PBM / MC-PBS communication card _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 22
5.2 Bus cable specification _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 24
6 Commissioning of PROFIBUS _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 25
6.1 Overview of the commissioning steps _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 25
6.2 Detailed commissioning steps _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 26
6.2.1 Planning the bus topology _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 26
6.2.2 Installing field devices _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 26
6.2.3 Create a project folder _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 27
6.2.4 Commissioning the field devices _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 27
6.2.5 Creating a PLC program with a target system (Logic/Motion) _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 28
6.2.6 Configuring the communication parameters _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 30
6.2.7 Importing missing devices / device description files _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 32
6.2.8 Creating a control configuration (adding field devices) _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 33
6.2.9 Configuration of the PROFIBUS master _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 37
6.2.10 Configuring the PROFIBUS slave _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 40
6.2.11 Compiling the PLC program code _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 41
6.2.12 Logging in on the controller with the »PLC Designer« _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 41
6.2.13 Starting the PLC program _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 41
2 Lenze · Controller-based Automation · PROFIBUS® Communication Manual · DMS 4.3 EN · 04/2014 · TD17
Contents
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
7 Mixed operation PROFIBUS with EtherCAT _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 42
8 Function libraries _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 43
8.1 CAA_Device_Diagnosis.lib function library _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 43
8.2 IIoDrvDPV1C1.lib function library _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 43
9 Defining the minimum cycle time of the PLC project _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 44
9.1 Determining the task utilisation of the application _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 44
9.2 Optimising the system _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 46
10 Diagnostics _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 47
10.1 LED status displays of the MC-PBM communication card _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 47
10.2 LED status displays of the MC-PBS communication card _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 48
10.3 Diagnostics in the »PLC Designer« _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 49
11 Parameter reference _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 50
Index _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 52
Your opinion is important to us _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 54
Lenze · Controller-based Automation · PROFIBUS® Communication Manual · DMS 4.3 EN · 04/2014 · TD17 3
1 About this documentation
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
1 About this documentation
This documentation ...
• contains detailed information about the commissioning, configuration, and diagnostics of the
PROFIBUS® 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
• Visualising
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
4 Lenze · Controller-based Automation · PROFIBUS® Communication Manual · DMS 4.3 EN · 04/2014 · TD17
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
Parameter setting, 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.
Lenze · Controller-based Automation · PROFIBUS® Communication Manual · DMS 4.3 EN · 04/2014 · TD17 5
1 About this documentation
1.1 Document history
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
1.1 Document history
Version Description
1.0 05/2009 TD17 First edition
2.0 10/2009 TD17 General revision
3.0 10/2010 TD17 Commissioning and configuration with the Lenze »PLC Designer« V3.x
3.1 03/2011 TD17 Revision on the Lenze automation system"Controller-based Automation",
3.2 12/2011 TD17 Revision on the Lenze automation system"Controller-based Automation",
3.3 07/2012 TD17 Revision on the Lenze automation system"Controller-based Automation",
4.0 11/2012 TD17 General corrections
4.1 03/2013 TD17 Revision on the Lenze automation system"Controller-based Automation",
4.2 11/2013 TD17 Revision on the Lenze automation system"Controller-based Automation",
4.3 04/2014 TD17 Revision on the Lenze automation system"Controller-based Automation",
Release 3.1
release 3.2
release 3.3
New layout
Release 3.5
release 3.6
release 3.8
6
Lenze · Controller-based Automation · PROFIBUS® Communication Manual · DMS 4.3 EN · 04/2014 · TD17
1 About this documentation
1.2 Conventions used
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
1.2 Conventions used
This documentation uses the following conventions to distinguish different types of information:
Type of information Identification Examples/notes
Numbers
Decimal Normal spelling Example: 1234
Decimal separator Point In general, the decimal point is used.
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 name 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
Icons
Page reference ( 7) 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 · PROFIBUS® Communication Manual · DMS 4.3 EN · 04/2014 · TD17 7
1 About this documentation
1.3 Terminology used
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
1.3 Terminology used
Term Meaning
Code Parameter for parameterising or monitoring the field device. The term is also referred to as
Controller The controller is the central component of the automation system which controls the Logic
Engineering PC The Engineering PC and the Engineering tools installed serve to configure and parameterise
Engineering tools Lenze software solutions for simply engineering in all phases:
Fieldbus stations Controller (PLC) and inverter integrated in the bus system (PROFIBUS)
Field device
GSD / GSE Device data base file (device description for PROFIBUS stations)
Inverter Generic term for Lenze frequency inverters, Servo Inverters
PLC Programmable Logic Controller
Subcode If a code contains several parameters, they are stored in so-called "subcodes".
"index" in common usage.
and Motion functionalities (by means of the runtime software).
The controller communicates with the field devices via the fieldbus.
the system.
The Engineering PC communicates with the controller via Ethernet.
•»EASY Starter«
• »Engineer«
•»PLC Designer«
•»WebConfig«
•»VisiWinNET®«
•»IPC Backup & Restore«
Lenze Engineering tools
EtherCAT® (Ethernet for Controller and Automation Technology) is an Ethernet-based
fieldbus system which meets the application profile for industrial real-time systems.
EtherCAT® is a registered trademark and patented technology, licensed by Beckhoff
Automation GmbH, Germany.
(German designation: SPS - Speicherprogrammierbare Steuerung)
PROFIBUS® (Process Fieldbus) is a common fieldbus system for the automation of machines
and production lines.
PROFIBUS® is a registered trademark and patented technology licensed by the PROFIBUS &
PROFINET International user organisation (PI).
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".
( 21)
8
Lenze · Controller-based Automation · PROFIBUS® Communication Manual · DMS 4.3 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
Layout of the safety instructions:
Pictograph and signal word!
(characterises the type and severity of danger)
Note
(describes the danger and suggests how to prevent dangerous situations)
Pictograph Signal word Meaning
Danger! Danger of personal injury through dangerous electrical voltage
Danger! Danger of personal injury through a general source of danger
Stop! Danger of damage to material assets
Application notes
Refere nce to an i mmin ent d ange r tha t may resu lt in deat h or serio us pe rsonal in jury
if the corresponding measures are not taken.
Refere nce to an i mmin ent d ange r tha t may resu lt in deat h or serio us pe rsonal in jury
if the corresponding measures are not taken.
Reference to a possible danger that may result in damage to material assets if the
corresponding measures are not taken.
Pictograph Signal word Meaning
Note! Important note to ensure trouble-free operation
Tip! Useful tip for easy handling
Reference to other documentation
Lenze · Controller-based Automation · PROFIBUS® Communication Manual · DMS 4.3 EN · 04/2014 · TD17 9
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).
10 Lenze · Controller-based Automation · PROFIBUS® Communication Manual · DMS 4.3 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.
System structure of the Controller-based Automation: "All from one single source"
[3-1] Example: PROFIBUS with the 3231 C Lenze Controller (I/O system 1000 and Servo Drive 9400 as slaves)
Lenze · Controller-based Automation · PROFIBUS® Communication Manual · DMS 4.3 EN · 04/2014 · TD17 11
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)
( 21) 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.
12 Lenze · Controller-based Automation · PROFIBUS® Communication Manual · DMS 4.3 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 · PROFIBUS® Communication Manual · DMS 4.3 EN · 04/2014 · TD17 13
4 The Lenze automation system with PROFIBUS
4.1 Brief description of PROFIBUS
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
4 The Lenze automation system with PROFIBUS
Note!
In the Lenze automation system PROFIBUS is exclusively used as Logic bus.
The Motion functionality is not supported when PROFIBUS is used. Always use EtherCAT
to connect inverters to be controlled via the central motion functionality.
Mixed operation PROFIBUS with EtherCAT
This chapter provides basic information about ...
• the structure of the Lenze automation system using the PROFIBUS bus system;
• the Lenze Engineering tools required for commissioning;
• the interaction of the components.
4.1 Brief description of PROFIBUS
Today, PROFIBUS is the most commonly used fieldbus system. As it comes with the widest range of
various field devices, PROFIBUS is occasionally prioritised over more modern bus systems. Due to the
low bandwidth and synchronisation mechanisms, PROFIBUS is only provided as a logic bus as part
of the Lenze automation system.
We recommend using PROFIBUS for the following applications:
• Equipment and extension of system parts that have already been automated with PROFIBUS
before.
• Use of field devices that are not available for e.g. EtherCAT or CANopen.
• Combination of PROFIBUS as logic bus and EtherCAT as logic/motion bus
Tip!
Detailed information about PROFIBUS can be found on the website of the PROFIBUS &
PROFINET user organisation:
( 42)
14
www.profibus.com
Lenze · Controller-based Automation · PROFIBUS® Communication Manual · DMS 4.3 EN · 04/2014 · TD17
4 The Lenze automation system with PROFIBUS
4.1 Brief description of PROFIBUS
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
4.1.1 Structure of the PROFIBUS system
[4-1] Example: PROFIBUS with the 3231 C Lenze Controller (I/O system 1000 and Servo Drive 9400 as slaves)
In the example (Fig. [4-1]), the 3231 C Lenze Controller is the PROFIBUS master. It can communicate
with one or several stations (slaves).
PROFIBUS has an internal line topology (without repeater) or a tree topology (with repeater).
Basic wiring of PROFIBUS
The PROFIBUS network must be terminated at the first and last station. The bus terminating resistor
is integrated into the bus connector and is activated by a switch.
Using the Lenze Controller as a PROFIBUS slave
Using the MC-PBS communication card, the Lenze Controllers can also be applied as PROFIBUS
slaves.
( 17)
Tip!
A sample project for operation of a 3200 C controller as PROFIBUS slave can be found in the
"Download" area at www.Lenze.com
Application Knowledge Base: All articles Application Ideas Pool Controller 3200 C
:
Lenze · Controller-based Automation · PROFIBUS® Communication Manual · DMS 4.3 EN · 04/2014 · TD17 15
4 The Lenze automation system with PROFIBUS
4.1 Brief description of PROFIBUS
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Parameter setting
The PROFIBUS stations can be parameterised in different ways.
If field devices are used the parameters of which are completely written to an GSD/GSE file,
PROFIBUS can only be configured with the »PLC Designer«:
• Import of the PROFIBUS slaves' GSD/GSE files into the »PLC Designer« project.
• Set-up of the control configuration and creation of the PLC program
If PROFIBUS configuration is only possible via a PROFIdrive parameter channel, the
parameterisation can also be done using the »Engineer«/»EASY Starter« – depending on the device
type via the following interfaces:
•Ethernet
•CAN
• Diagnostic interface
Note!
The "L-force Controller as gateway" function is not available in combination with
PROFIBUS. Therefore logging in with the »Engineer« via the controller as gateway is not
possible.
16
Lenze · Controller-based Automation · PROFIBUS® Communication Manual · DMS 4.3 EN · 04/2014 · TD17
4 The Lenze automation system with PROFIBUS
M
Z
Z
S SS
1
M
Z
Z
S SS
Z
Z
Z
Z
1 23
R
S S
R
4.1 Brief description of PROFIBUS
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
4.1.2 Basic wiring of PROFIBUS
Two simple RS485 networks are described in the following examples.
Each segment of the network must be terminated at both ends. The bus terminators of the
PROFIBUS are marked with a "Z" in each one of the following examples.
In the case of an RS485 network consisting of only one segment, the network starts at the PROFIBUS
master (M) with the integrated bus terminating resistor and ends at the last PROFIBUS station (S);
its bus terminating resistor in the bus connector must be activated.
[4-2] PROFIBUS network with one segment
A PROFIBUS network consisting of several segments contains repeaters (R) for connecting the
segments. The repeaters are provided with integrated bus terminating resistors.
[4-3] PROFIBUS network with repeaters
If you do not use a repeater at the end of the segment, the bus terminating resistor in the bus
connector of the last device must be activated.
Activating the bus terminating resistor
( 26)
E94YCPM012a
E94YCPM012b
Lenze · Controller-based Automation · PROFIBUS® Communication Manual · DMS 4.3 EN · 04/2014 · TD17 17
Loading...