Professional Documents
Culture Documents
931E-931K - PROFIBUS-DP Communication - v2-1 - EN
931E-931K - PROFIBUS-DP Communication - v2-1 - EN
0004−EN
.Bò*
Ä.Bò*ä
Communication Manual
931EPx, 931KPx
PROFIBUS−DP
l
0Fig. 0Tab. 0
2 Product description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.1 Product features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
3 Technical data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
3.1 Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
4 Electrical installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
4.1 Wiring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
4.2 Assignment of the interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
4.2.1 931E servo inverter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
4.2.2 931K servo inverter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
5 PROFIBUS communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
5.1 The data telegram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
5.1.1 Structure of the receive message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
5.1.2 Structure of the response message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
5.1.3 Structure of the receive and response message with PKW mechanism . 16
5.2 Consistent parameter data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
6 Commissioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
6.1 Important notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
6.2 Initial switch−on . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
6.3 Settings on the controller (slave) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
6.3.1 Node address setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
6.3.2 Definition of parameter numbers (PNU) in the telegram editor . . . . . . . 24
6.4 Control system configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
6.5 "Speed control" mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
6.5.1 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
6.5.2 Commissioning with PROFIdrive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
6.5.3 PNUs for parameter setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
6.6 "Positioning" mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
6.6.1 Setting of homing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
6.6.2 Positioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
6.6.3 Static position data sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
6.6.4 Dynamic position data set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
6.6.5 Commissioning with PROFIdrive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
6.6.6 PNUs for parameter setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
7 Parameter setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
7.1 Physical units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
7.2 Global parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
7.2.1 Saving of parameter set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
7.2.2 Setting of manual jog (inching mode) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
7.2.3 Motor data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
7.3 "Speed control" mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
7.3.1 Speed setpoint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
7.3.2 Acceleration value . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
7.4 "Positioning" mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
7.4.1 Selection of position data set for parameter setting . . . . . . . . . . . . . . . . 49
7.4.2 Setting of positioning profile parameters . . . . . . . . . . . . . . . . . . . . . . . . . 49
7.4.3 Position data set at starting of positioning . . . . . . . . . . . . . . . . . . . . . . . . 50
7.4.4 Jerk limitation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
7.4.5 Homing modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
7.4.6 Homing offset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
7.5 Error management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
7.5.1 Setting of responses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
8 Device control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
8.1 Important notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
8.2 "Speed control" mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
8.2.1 Control word 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
8.2.2 Status word 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
8.3 "Positioning" mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
8.3.1 Control word 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
8.3.2 Status word 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
8.4 State diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
10 Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
10.1 Table of parameter numbers (PNU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
11 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Contents
This documentation contains descriptions for PROFIBUS with servo inverters of the 931
series.
) Note!
This documentation completes the mounting instructions coming with the
931 servo inverter and the corresponding hardware manual.
The mounting instructions and the hardware manual contain safety
instructions which must be observed!
ƒ The features of the PROFIBUS−DP for servo inverters of the 931 series are described
in detail.
ƒ Typical applications are illustrated by use of examples.
ƒ Furthermore, this documentation contains:
– the most important technical data for PROFIBUS communication;
– information on the installation and commissioning of the PROFIBUS network;
– information on the PROFIBUS data transfer, PROFIBUS monitoring functions,
communication−relevant parameters, and different operating modes.
The theoretical connections are only explained as far as required for understanding the
PROFIBUS communication for servo inverters of the 931 series.
All trade names listed in this manual are trademarks of their respective owners.
Validity information
The information given in this documentation is valid for servo inverters of the 931 series.
Target group
This documentation addresses to all persons designing, installing, commissioning, and
setting the servo inverters of the 931 series.
I Tip!
Documentation and software updates for further Lenze products can be found
on the Internet in the "Services & Downloads" area under
http://www.Lenze.com
The following pictographs and signal words are used in this documentation to indicate
dangers and important information:
Safety instructions
Structure of safety instructions:
} Danger!
(characterises the type and severity of danger)
Note
(describes the danger and gives information about how to prevent dangerous
situations)
{ Danger!
Reference to an imminent danger that may result in death or
serious personal injury if the corresponding measures are not
taken.
Danger of personal injury through a general source of danger.
} Danger!
Reference to an imminent danger that may result in death or
serious personal injury if the corresponding measures are not
taken.
(
Danger of property damage.
Stop! Reference to a possible danger that may result in property
damage if the corresponding measures are not taken.
Application notes
Pictograph and signal word Meaning
2 Product description
3 Technical data
3.1 Communication
Field Values
Communication profile Profibus DP
(DIN 19245 part 1 and part 3)
Communication medium RS485
Drive profile PROFIdrive
Network topology Without repeater: line / with repeaters: line or tree
PROFIBUS−DP device Slave
Baud rate [kbps] 9.6 ... 12000
Maximum cable length per bus 1200 m (depending on baud rate and cable type)
segment
Bus connection X4.1, X4.2 9−pin Sub−D socket (931E), 5−pin M12 connector (931K)
4 Electrical installation
4.1 Wiring
1 1 1
£ 1200 m
931e_037
Element Note
0 Control system E.g. PC or PLC with PROFIBUS−DP master interface module
1 Bus cable Adapt baud rate to bus cable length
931X PROFIBUS slave Appropriate standard device
) Note!
When using a repeater, up to 125 stations can communicate via PROFIBUS.
EMC−compliant wiring
For wiring according to EMC requirements, please observe the following points:
) Note!
ƒ Separate control cables from motor cables.
ƒ Connect control/data cable shields correctly:
– On both sides for cables with digital signals.
ƒ Observe the information on wiring according to EMC guidelines given in the
documentation for the standard device.
Wiring procedure
1. Do not change the bus topology, i.e. do not use stubs.
2. Observe wiring notes given in the documentation for the control system.
3. Only use cables that comply with the listed specifications.
4. Activate bus terminating resistors at the first and last physical station.
When using sub plugs Lenze recommends to use sub−D plugs with internal series
inductance (110 nH).
M
R R
S S S S S
1 2 3
2133PFB004
I Tip!
Repeaters do not have a station address but in the calculation of the
maximum number of stations they reduce the number of stations by 1 on
each side of the segment.
Repeaters can be used to build up line and tree topologies. In this case, the
maximum total bus system expansion depends on
ƒ the baud rate used
ƒ the number of repeaters used
Baud rates
Baud rate [kbps] Length of the transmission cable [m]
9.6 ... 93.75 1200
187.5 1000
500 400
1500 200
3000 100
6000 100
12000 100
) Note!
ƒ The baud rate depends on the data volume, cycle time and number of bus
stations.
ƒ The baud rate selected should be as low as possible. The lower the baud
rate, the more insensitive the PROFIBUS is to parasitic coupling.
I Tip!
For high baud rates, we recommend to consider the application of optical
fibres.
Advantages of optical fibres:
ƒ External electromagnetic interferences have no effects on the transmission
path.
ƒ Bus lengths of several kilometres are also possible with higher baud rates.
The bus length is
– independent of the baud rate.
– depend on the optical fibre used.
The controller is connected to the PROFIBUS via the 9−pin Sub−D socket X4.1/X4.2.
View Pin Designation Explanation
1 − −
2 − −
The controller is connected to the PROFIBUS via the M12 connector X4.1/X4.2.
X4.1 / X4.2 PROFIBUS
Input contact pattern Pin Signal Specification
no.
1 n. c. Not assigned
2 RxD/TxD− Receive / Transmit data −N (A line)
N
3 DGND Data Ground (reference potential to VP)
4 RxD/TxD− Receive / Transmit data −plus (B line)
P
5 Shield Shield
Output contact Pin Signal Specification
pattern no.
1 VP Power supply plus (5V)
2 RxD/TxD− Receive / Transmit data −N (A line)
N
3 DGND Data Ground (reference potential to VP)
4 RxD/TxD− Receive / Transmit data −plus (B line)
P
5 Shield Shield
5 PROFIBUS communication
The controller supports the communication protocol DP in the power section DP−V0. The
controller and the PLC communicate via receive telegram and response telegram. Enter
parameter numbers (PNU) in these telegrams to address objects of the drive (e.g. process
data and parameter data). Telegrams are transmitted cyclically. The telegram length
depends on the settings of the telegram editor in the SDC.
ƒ Receive telegrams contain output data which is transmitted from the PLC (master)
to the controller (slave).
ƒ Response telegrams contain input data which is transmitted from the
controller (slave) to the PLC (master).
) Note!
ƒ To enable the PLC to receive the process data from the controller, you have
to assign the corresponding response message to the receive message in
"SDC". (¶ 24)
ƒ In the PLC you have to enter the identifier in byte 0 of the receive message.
The identifier sets the operating mode of the controller.
– E1h: speed control mode
– E0h: positioning mode
5.1.3 Structure of the receive and response message with PKW mechanism
The PKW mechanism (PKW = parameter identifier value) enables a variable read/write
access to the parameters of the controller with a defined telegram structure.
ƒ Use the PNU 2000 for the PKW mechanism.
Receive message
The PNU 2000 can be entered in the telegram editor, for instance under address 4.
ADR = 1 ADR = 2 ADR = 4 ADR = 12 ADR = 16
1st DWORD 2nd DWORD
Parameter value
Subindex of PNU
PNU to be accessed by the master
Identifier:
l Read access: 41h
l Write access: 42h
l No access: 00h
Response message
The PNU 2000 must be entered under the same address as in the receive message.
ADR = 1 ADR = 2 ADR = 4 ADR = 12 ADR = 16
1st DWORD 2nd DWORD
Parameter value
Subindex of PNU
PNU requested by the master
Identifier:
l Write access: 42h
) Note!
ƒ The PNU 2000 must be entered under the same address in the receive
message and in the corresponding response message!
ƒ For reasons relating to the address register of the master’s CPU (see
documentation for the master), we recommend to use variables of the type
"double word" for the telegram.
If the telegram is generated byte by byte, a shift in the data telegram may
result which causes transmission errors.
ƒ The transmission of a parameter is not acknowledged by the controller.
In the PROFIBUS communication system, a permanent data exchange takes place between
the master computer (CPU + PROFIBUS master) and the slave.
The PROFIBUS master and the CPU (central processing unit) of the master computer access
a common storage medium for this purpose − the dual port memory (DPM).
The DPM enables a data exchange into both directions (read/write):
Without any further data organisation, a slower write action of the PROFIBUS master
might be overtaken by a faster read action of the CPU within a cycle.
To prevent this from happening, the parameter data to be transferred must be marked as
"consistent".
0 1
Central Processing ó Dual Port Memory ó PROFIBUS Master
Unit (CPU) (DPM)
6 Commissioning
Before you switch on the controller for the first time in the PROFIBUS−DP network, check
ƒ the entire wiring for completeness, short circuit, and earth fault,
ƒ and whether the bus system is terminated by terminating resistors at the first and
last bus station.
) Note!
Keep to the switch−on sequence!
) Note!
The controller parameters are set using the »Small Drives Control (SDC)« PC
software.
ƒ Establish an RS232 connection for communication between the PC and the
controller. For a detailed description please refer to the controller’s software
manual.
ƒ Save all settings in the parameter set of the controller using the command
File W Parameter set W Save parameter set (flash) to prevent the settings
from getting lost in the case of a reset or mains switching.
931E_020, 931E_21
2. Enter the desired node address for the controller in the Slave node number input
box.
3. Tick the Profibus active check box.
– If the check box is enabled, the Slave node number input box is disabled.
4. Click on the Save & Reset button to save the settings.
– After saving, the assigned node address is displayed in the Effective slave node
number box.
5. Click on the OK button.
) Note!
The dialog box displays that the communication between master and slave
has been established successfully:
ƒ The Data Exchange box is lit green.
ƒ The baud rate set on the master is displayed in the Baud rate box.
Selecting the node address via the digital inputs DIN0 ... DIN5
You assign the node address to the controller by adding to the preset slave node number
an offset via DIN0 ... DIN5.
1. Open the Parameters W Fieldbus W Profibus... W Operating parameters... menu.
931E_020, 931E_22
2. Enter the desired value in the Slave node number input box.
3. Click on the + Offset (DIN) (inactive) button (see arrow in the screenshot of the
"Profibus" dialog box).
– The Digital inputs dialog box opens.
4. Tick the Offset node number (field bus) check box.
– Tick the AIN’s used as DIN’s check box (if necessary) to use DIN0 ... DIN3 as well for
the offset.
– Adjustable offset: 0 ... 63 with DIN0 ... DIN5 or 16, 32, 48 with DIN4, DIN5
– Click on the OK button.
5. Set the digital inputs DINx for the desired offset.
Calculation of the offset:
Offset = DIN0 × 20 + DIN1 × 21 + DIN2 × 22 + DIN3 × 23 + DIN4 × 24 + DIN5 × 25
Example:
The node address of the controller is to be "35". In the Slave node number input box "3"
is entered. So the offset must be "32":
Offset = DIN0 × 20 + DIN1 × 21 + DIN2 × 22 + DIN3 × 23 + DIN4 × 24 + DIN5 × 25
32 = 0 × 20 + 0 × 21 + 0 × 22 + 0 × 23 + 0 × 24 + 1 × 25
931E_23
) Note!
The dialog box displays that the communication between master and slave
has been established successfully:
ƒ The Data Exchange box is lit green.
ƒ The baud rate set on the master is displayed in the Baud rate box.
ƒ Parameter numbers (PNU) can be used to address drive objects (e.g. process and
parameter data).
– Parameter numbers can comprise several subindexes under which objects are
represented. When defining the PNU, the respective subindex must be defined as
well.
ƒ With the telegram editor you can define all PNUs required for the application. The
PNUs are stored in the controller.
– Define the PNUs before activating communication to the master.
1. Open the Parameters W Fieldbus W Profibus... W Profibus telegram editor... menu.
931E_024
) Note!
ƒ If the response message does not correspond to the receive message, the
master receives incorrect data from the controller.
ƒ In the PLC you have to enter the identifier in byte 0 of the receive message.
The identifier sets the operating mode of the controller.
– E1h: speed control mode
– E0h: positioning mode
4. Click on the Append entry button to enter a PNU.
– If you want to enter the PNU in hexadecimal notation, activate the hexadecimal
format in the Append entry box.
– If you want to change a PNU, select the PNU and click on the Change entry button.
– If you want to delete the PNU entered last, click on the Delete last entry button.
) Note!
ƒ If necessary, enter PNU 2010 as a wildcard to make the telegram length
match the parameterised telegram length of the master.
ƒ Check that the parameterised telegram length corresponds to the memory
allocation (see arrows in the screenshot of the "Profibus telegram editor"
dialog box).
931E_025
) Note!
ƒ If necessary, enter PNU 2010 as a wildcard to make the telegram length
match the parameterised telegram length of the master.
ƒ Check that the parameterised telegram length corresponds to the memory
allocation (see arrows in the screenshot of the "Profibus telegram editor"
dialog box).
The control system must be configured before communication with the controller is
possible.
Creating a project
ƒ Please refer to the documentation for the configuration tool if you want to create a
project.
) Note!
Use of data consistency
ƒ We recommend to use exclusively configurations with consistency to avoid
data conflicts between the PROFIBUS−DP master and the CPU of the control
system.
– If the telegram has, for instance, a length of 8 bytes of data, the PLC must
be able to process the 8 bytes of data continuously (consistently).
ƒ Detailed description of consistency: (¶ 18)
ƒ Please note that the processing of consistent data varies between different
control systems. This must be considered in the configuration tool.
– It may be necessary to use system functions of the PLC to ensure the data
consistency.
– Please refer to the documentation for the PLC to find out which data
length can be processed consistently by the CPU.
6.5.1 Description
Limit Function
[inc]
acceleration velocity control [acceleration units] velocity demand value (2)
(PNU 1011.0) Profile Acceleration
status word 1
velocity window time (2) (PNU 968.0, Bit 8,
velocity = 0)
velocity actual value Timer
(PNU 1101.0) status word 1
Window (PNU 968.0, Bit 10,
Comparator velocity reached)
velocity window
931e_030
) Note!
ƒ The bit assignment of the control word 1 and the status word 1 is described
in the chapter "Device control". (¶ 54)
ƒ To enable the PLC to control the controller via PROFIBUS, bit 10 of the
control word 1 must be set statically. When the communication self−test has
been completed successfully, bit 9 of the status word 1 is set.
931e_028
Adjustment
ƒ Homing speed
– First the drive searches for the limit switch using the search speed. For
determining the position of the switching edge exactly, the drive changes to the
creep speed. Both speeds are set in SDC.
ƒ Acceleration
– The acceleration is set in SDC.
ƒ Homing mode
– A description of the different homing methods is given in the software manual of
the controller.
ƒ Shifting of the zero position
– Via PNU 1051.0 the zero position of the drive can be shifted. The value under
PNU 1051.0 is added to the value of the homing point (e.g. limit switch position).
) Note!
Traversing to the zero position is not part of the homing run. If the controller
knows all parameters required (e.g. the position of the zero pulse), no physical
movement is executed.
6.6.2 Positioning
2
position set number (PNU 1000)
931e_032
ƒ The target position is transferred to the trajectory generator via PNU 1001.0. The
trajectory generator generates the position setpoint for the position controller.
Trajectory generator and position controller can be set independently of each other.
Adjustment
ƒ Simple travel task
– Select position data set (0 63) under PNU 1002. (¶ 35)
– Activation: Control word 1, set bit 6 from 0 ® 1.
– The controller stops when the target position has been reached. Bit 10 of status
word 1 is used to signal the reaching of the target position to the master.
v2
v1
t0 t1 t2 t3 t
931e_407
v2
v1
t0 t2 t1 t3 t
931e_408
) Note!
It is possible to interrupt the running travel task and immediately start the
next travel task:
ƒ Select PROFIBUS position data set (68) under PNU 1002. (¶ 36)
ƒ Activation: Control word 1, set bit 13 = 1.
– Interruption of the positioning process. Start of next travel task.
1
Bit 10
(1) (2) t
Control word 1
1
Bit 4
(3) t
1
Bit 5
(4) t
1
Bit 6
(5) t
1
Bit 9
t
Status word 1
1
Bit 10
(6) t
1
Bit 11
(0) t
931e_031
The settings (positioning, start delay, start during positioning) and the driving profile
(travelling speed, acceleration, time constant without jerk) of the position data sets 0 ... 63,
which can be parameterised with »Small Drives Control (SDC)«, are divided into four
groups (see software manual for the controller).
ƒ You can, for instance, select a travelling speed for the "Positioning 0 15" group
(position data sets 0 15). This also applies to the position data sets 16 31,
32 47 and 48 63.
ƒ The target positions 0 63 are parameterised in SDC. Only approaching/activating
of the target positions (PNU 1002.0 = 0 63) is controlled via PROFIBUS.
) Note!
Please observe that you have to jump between the groups if e.g. the travelling
speeds differ.
931E_33
If the application requires positioning with different settings and driving profiles, use
dynamic positioning via position data set 68:
ƒ Selection of the driving profile via PROFIBUS.
ƒ Changing between absolute and relative positioning via control word 1.
ƒ Interruption of a running positioning task and approaching of a new target via a
start command.
931e_34
) Note!
ƒ The bit assignment of the control word 1 and the status word 1 is described
in the chapter "Device control". (¶ 54)
ƒ To enable the PLC to control the controller via PROFIBUS, bit 10 of the
control word 1 must be set statically. When the communication self−test has
been completed successfully, bit 9 of the status word 1 is set.
ƒ Via PNU 1290.1 (iit Ratio Motor) you can read out the actual utilisation of the I2t
limitation in [].
PNU Name Possible settings Characteristics
7 Parameter setting
) Note!
Application−specific parameters depend on the physical units. For this reason
set the physical units before starting to parameterise the application.
With the »Small Drives Control (SDC)« program you can parameterise the controller in such
a way that the physical quantities can be entered/read out on the drive directly in the
desired units (e.g. position values of a linear axis in millimetres and speeds in millimetres
per second).
ƒ Open the Parameters W Fieldbus W Profibus... W Display units... menu.
931E_026
UE
x1
UA x2
931e_415
Notes on settings
ƒ From the set physical units conversion factors are automatically generated
internally. The conversion factors consist of a numerator and a denominator and
may not be longer than 32 bits.
ƒ The value of the feed constant is ignored for the respective physical unit if the feed
constant has a translatory unit and a rotatory unit is selected for the physical
quantity.
ƒ If the entries for the factors or physical units are incorrect, an overflow occurs and
the value is rejected.
ƒ Examples for incorrect settings:
Incorrect setting Effect
Position in [revolutions] and The feed constant is ignored.
feed constant in [mm/revolution]
Position in [mm] and The feed constant is considered as a gearbox factor.
feed constant without a unit
Position in [mm] and The feed constant is evaluated using the factor 1000.
feed constant in [mm/revolution]
Inching speed
l The physical unit is the
PROFIBUS speed
1 Symmetrical Jog 10000 0 {1 rpm/s} 20000 UINT32 RW
Accelerations Inching acceleration
l The physical unit is the
PROFIBUS acceleration
l The value read is the
acceleration
ƒ Via PNU 1290.0 (iit Time Motor) you can set the duration of the maximum motor
current.
When the time has elapsed, the motor current is automatically limited to the
parameterised rated motor current.
ƒ Via PNU 1290.1 (iit Ratio Motor) you can read out the actual utilisation of the I2t
limitation in [].
PNU Name Possible settings Characteristics
ƒ Selecting the position data set of the controller to be parameterised via PNU 1001.
The position data set for PROFIBUS can be parameterised via the "SDC" program and saved
in the controller. In this way the parameters of an application which do not have to be
changed during operation can be specified permanently. You just have to enter, for
instance, the values for accelerations once. These values then do not have to be transferred.
PNU Name Possible settings Characteristics
ƒ Changing the parameters of the position data set selected via PNU 1000.
The data is interpreted according to the selected physical units. (¶ 43)
PNU Name Possible settings Characteristics
ƒ Selection of the position data set to be started via the control word 1 when a
command to start a positioning process is issued.
The controller is provided with 64 storable standard position data sets which can be
selected via 8 bits.
PNU Name Possible settings Characteristics
ƒ Defining the distance between the home position (zero position) and the reference
point of a homing run.
Positive values shift the zero point to the positive direction with respect to the reference
point.
0 1
Home Offset
x
2
931_029
8 Device control
} Danger!
Uncontrolled motor movements can occur
If the power stage of the controller is inhibited, the motor coasts to stop
without braking.
Possible consequences:
ƒ Injury to persons through uncontrolled machine movements.
Protective measures:
ƒ Install a mechanical motor brake which is activated automatically when the
power stage is inhibited.
The controller is controlled via PROFIdrive by means of a data word (LOW byte and HIGH
byte):
ƒ The master uses the control word 1 to control the essential function of the
controller.
– The assignment of the control word 1 corresponds to the PROFIdrive profile. Some
functions have manufacturer−specific definitions.
– The controller first accepts the parameter data and then evaluates the control
word 1. This ensures that the sequence of the positioning steps is correct.
– State changes triggered via the control word 1 first have to be confirmed via the
status word 1 before another command can be sent via the control word 1.
ƒ The controller (slave) uses the status word 1 to signal its state to the master.
– The assignment of the status word 1 corresponds to the PROFIdrive profile. Some
functions have manufacturer−specific definitions.
– The status word 1 displays the different states of the controller.
Power on
S1: SWITCHING_ON_INHIBITED
S2: READY_FOR_SWITCH_ON
(2) (5)
(8) (10)
S3: SWITCHED_ON
S4:OPERATION
931e_027
Controller states
Status word 1
State Bit 6 Bit 2 Bit 1 Bit 0 Description
0040h 0004h 0002h 0001h
Power on Switch−on and initialisation of the controller.
Communication via PROFIBUS is not yet possible.
SWITCHING_ON_INHIBITED 1 0 0 0 The initialisation is completed.
The power stage is deactivated, the motor
produces zero torque.
Communication via PROFIBUS is possible.
The controller changes to this state when an error
message occurs.
READY_FOR_SWITCH_ON 0 0 0 1 Waiting for the controller to be enabled.
The controller can be enabled via DIN9 = HIGH or
via the controller enable logic "DIN9 and
PROFIBUS".
SWITCHED_ON 0 0 1 1 The controller is enabled (DIN9 = HIGH).
OPERATION 0 1 1 1 The controller is operating. The drive is controlled
according to the selected operating mode.
Fault Remedy
The controller operates faultlessly but the Correct the message assignment in SDC:
PLC does not receive any process data. l Assign the response message 0 to the receive message 0 and
the response message 1 to the receive message 1.
The controller is in the wrong operating Check the telegram identifier in byte 0:
mode / does not receive any control l "Positioning" mode: Byte 0 = E0h (receive message 0/response
commands. message 0).
l "Speed control" mode: Byte 0 = E1h (receive
message 1/response message 1).
The master signals an error during data Check the memory area used by the PLC in the hardware
transmission (e.g. access error). configuration.
The power stage is active but the motor Enter the torque setpoint limitation in the receive message:
does not rotate. l For limitation via analog input (PNU 1022.0 = 1, 2), apply a
voltage at input (AIN).
l For limitation via PROFIBUS (PNU 1022.0 = 7), enter the setpoint
directly via PNU 1022.1.
No processing of the PROFIdrive profile, but Check that the controller enable logic is entered in the receive
the motor is rotating. message and that the value is set appropriately.
The error messages of the controller are coded in the error numbers 1 ... 64. These error
numbers can be read via PNU 1601:
ƒ PNU 1601.0 transfers the error numbers 1 ... 32
ƒ PNU 1601.1 transfers the error numbers 33 ... 64
PNU Name Possible settings Characteristics
¨ Setting is possible
− Setting is not possible
l
KHB 13.0004−EN 2.1
KHB 13.0004−EN
l Are there any other sources of heat near the motor that
may additionally increase the ambient temperature and
thus lead to a reduced heat loss dissipation?
l Check the controller settings, poor settings will lead to an
unnecessary heat generation.
l Reduce the load torque of the motor.
l Check the setting of the temperature sensor.
l Check the resolver and encoder cable for an open circuit.
l Check the resolver position adjustment.
04 Overtemperature/ < 100 ms þ þ − − Overtemperature/undertemperature of l Check if the controller has been correctly mounted into the
undertemperature of the controller control cabinet:
power electronics – Heatsink must have large−surface contact with the
housing of the control cabinet.
9
9
64
deceleration ramps).
l Increase following error margin/response delay.
31 Limit switch error < 1 ms þ þ þ ¨ Incorrect configuration of limit switch. Check limit switch configuration.
Incorrect wiring of limit switch. Ensure correct wiring of limit switch.
Limit switch defective. Replace limit switch.
35 Time−out at quick stop < 5 ms þ ¨ ¨ ¨ Angle encoder error occurred. Check encoder.
Motor identification failed. Repeat motor identification.
Acceleration too high. Check settings.
36 Homing error < 5 ms þ þ þ ¨ Homing run completed with errors. Check homing configuration.
Incorrect parameter setting for controller Check settings of controller and angle encoder.
9
10 Appendix
Table of parameter numbers (PNU)
10 Appendix
ƒ The PNUs are numerically sorted in ascending order to form a "reference book".
ƒ How to read the table:
Column Abbreviation Meaning
PNU XXXX Parameter number XXXX
1 Subindex 1 of PNU XXXX (PNU XXXX.1)
2 Subindex 2 of PNU XXXX (PNU XXXX.2)
Name Name of the PNU
Possible settings
Lenze Lenze setting (value at delivery or after restoring the delivery state)
Selection 1 {%} 99 Minimum value {unit} maximum value
Characteristics
Object type REC Record
ARR Array, composed type (field)
VAR Variable
Data type UINT8 Unsigned integer, 1 byte without sign
UINT16 Unsigned integer, 2 bytes without sign
UINT32 Unsigned integer, 4 bytes without sign
INT8 Integer, 1 byte with sign
INT16 Integer, 2 bytes with sign
INT32 Integer, 4 bytes with sign
Access RO Read only
RW Read/write
WO Write only
Description Short, important explanations
Parameterisation of the
position data set selected via
PNU 1000.
0 Target Position 0 −32768 {1 inc} 32768 Target position
1 Profile Velocity 1000 0 {1 rpm} 3000 Travelling speed
3 Acceleration 10000 0 {1 rpm/s} 20000 Acceleration
Positioning
4 Deceleration 10000 0 {1 rpm/s} 20000 Deceleration
Positioning
5 All Accelerations 10000 0 {1 rpm/s} 20000 Acceleration and
Positioning deceleration
l Writes the set value to
PNU 1001.3 and
PNU 1001.4.
l Reads out PNU 1001.3
only.
1002 0 Start Set Number 68 UINT8 RW
Inching speed
l The physical unit is the
PROFIBUS speed
1 Symmetrical Jog 10000 0 {1 rpm/s} 20000 UINT32 RW
Accelerations Inching acceleration
l The physical unit is the
PROFIBUS acceleration
l The value read is the
acceleration
1050 0 Homing Method 1 INT8 RW
1 16 Bit 0 UINT16 RW
2 32 Bit 0 UINT32 RW
11 Index
A I
Actual position, 40 Inching mode (manual jog), setting, 45
Actual speed value, 40 Initial switch−on, 19
Actual value of effective current, 40 Inputs, digital, 41
Installation, electrical, 11
B
Basic wiring of the PROFIBUS, 11 J
Baud rate, 10 Jerk limitation, 50
C M
Cable length, per bus segment, 10 Manual jog (inching mode), setting, 45
Cable specification, 13 Modes for homing, 51
Command, control word 1, 55 , 57 Motor data, 42 , 46
Commissioning, 19
− Defining the positioning profile, setting of positioning N
profile parameters, 49 Network topology, 10
− Initial switch−on, 19
Notes, definition, 8
− Setting of homing, 31
homing modes, 51 Number of bus stations, 12
Communication, PROFIBUS, 15
Communication profile, 10 O
Consistent parameter data, 18 Offset, for homing, 52
R Speed setpoint, 47