Lenze i55AE155F

9.9.7 Parameter data transfer
Data communicaon with PROFINET is characterised by the simultaneous operaon of cyclic
and acyclic services in the network. As an oponal extension, the parameter data transfer
belongs to the acyclic services.
Details
•
Only one parameter request is processed at a me (no pipelining).
•
No spontaneous messages are transferred.
•
There are only acyclic parameter requests.
•
Prole-specic parameters can be independently of the states of the IO-Device.
An IO-Controller can always request parameters from the IO-Device if the IO-Device is in the
DATA_EXCHANGE state.
Transmission direcons for acyclic data transfer
Write.res
Write.req
with data (parameter request)
with data (parameter response)
without data
without data
without data
without data
Read.req
Read.res (-)
Read.req
Read.res (+)Parameter response
Parameter request Parameter request
Parameter
processing
Parameter response
IO controller
IO device
1.
A "Write.req" is used to transmit the data set (DB47) to the IO-Device in the form of a
parameter request.
2.
With "Write.res", the IO-Controller receives the conrmaon for the receipt of the mes-
sage.
3.
The IO-Controller requests the response of the IO-Device with "Read-req".
4.
The IO-Device responds with a "Read.res (-)" if processing has not been completed yet.
5.
Aer parameter processing, the parameter request is completed by transming the
parameter response to the IO-Controller with "Read.res (+).
Telegram structure
Destr ScrAddr VLAN
Type
0x0800
RPC NDR Read/Write Block Data FCS
6 bytes 6 bytes 4 bytes 4 bytes 80 bytes 64 bytes 64 bytes 0 .... 240 bytes 4 bytes
In the Read / Write Block eld, the iniator species the access to the "DB47" data set. The
data that is wrien on this index or read by it, contain a header and the parameter request or
the parameter response. The read data or the data to be wrien are contained in the Data
eld.
Conguring the network
PROFINET
Parameter data transfer
375