Parameter data transfer – Lenze E82ZAFPC010 User Manual
Page 58
Parameter data transfer
DRIVECOM parameter data channel
Telegram structure
l
58
EDS82ZAFPC010 EN 4.0
Byte 1: Service, request and response control for the parameter data channel
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
Request
Request to the controller. The bits are set only by the master.
l
000 = No request
l
001 = Read request (read data from controller)
l
010 = Write request (write data to controller)
Data length
Length of data in bytes 5 ... 8 (data/error 1 ... 4)
l
00 = 1 byte
l
01 = 2 bytes
l
10 = 3 bytes
l
11 = 4 bytes
Handshake
Indicates a new request.
l
The master changes this (toggle) bit for every new request.
l
The controller copies the bit into its response telegram.
Status
Status information from the controller to the master when sending the request
confirmation. This bit informs the master whether the request has been carried
out without any faults.
l
0 = Request completed without fault.
l
1 = Request not completed. An error has occurred. The data of bytes 5 ... 8
(data/error) must be interpreted as an error message.
0
7 6 5 4 3 2 1
Arrangement of bits 0 ... 7 in byte 1
0
2 1
3
Reserved
5 4
6
7
Examples of byte 1:
ƒ
Read request
Bit 7
...
Bit 0
0
X
1
1
0
0
0
1
"1" (read)
Reserved
"3" (data length 4 bytes)
Handshake
Status (only relevant for response telegram)
ƒ
Write request
Bit 7
...
Bit 0
0
X
0
1
0
0
1
0
"2" (write)
Reserved
"1" (data length 2 bytes)
Handshake
Status (only relevant for response telegram)