Lenze EMF2133IB - Manual (Page 87)

Parameter data transfer
DRIVECOM parameter data channel
Addressing of the parameter data
8
l
87 EDSMF2133IB EN 5.0
8.2 DRIVECOM parameter data channel
The DRIVECOM parameter data channel ...
ƒ enables parameter setting and diagnostics of the controller.
ƒ allows access to all Lenze parameters (codes).
ƒ additionally occupies 4 words of the input and output data words in the master.
ƒ has an identical structure for both directions of transmission.
8.2.1 Addressing of the parameter data
The parameter data is accessed via codes listed in the code table included in this
documentation of the function module and the corresponding documentation of your
controller.
8.2.2 Addressing of the Lenze parameters
In the case of the DRIVECOM parameter data channel the parameters of a device are not
directly addressed via Lenze code numbers, but via indexes (byte 3, byte 4) and subindexes
(byte 2).
The Lenze code numbers are converted into indexes via an offset (24575
dec
/ 5FFF
hex
):
Addressing of Lenze codes Example for C0001 (operating mode)
l PROFIBUS index =
24575 − Lenze code l PROFIBUS index =
24575 − 1 = 24574
l PROFIBUS−DP−Index
hex
=
5FFF
hex
− Lenze code
hex
l PROFIBUS−DP−Index
hex
=
5FFF
hex
− 1
hex
= 5FFE
hex
Lenze parameters are mainly represented in the fixed point format (data type integer32
with four decimal digits). For this reason, the value of the parameter/code must be
multiplied by 10000 in order to obtain integer values.
The parameter value is entered in the user data (bytes 5 ... 8) of the telegram.
Example:
Set C0039 (JOG) = 150.4 Hz.
ƒ 150.4 x 10000 = 1504000 (0016F300
hex
)
ƒ The resulting parameter value is entered in the user data.
8.2.3 Telegram structure
The telegram of the DRIVECOM parameter data channel consists of a total of 8 bytes. The
individual bytes are described in detail on the following pages.
Byte 1 Byte 2 Byte 3 Byte 4 Byte 5 Byte 6 Byte 7 Byte 8
Service Subindex Index
High byte
Index
Low byte
Data 4 /
Error 4
Data 3 /
Error 3
Data 2 /
Error 2
Data 1 /
Error 1