Parameter value
Byte 13 Byte 14 Byte 15 Byte 16
Value
(Integer8 / Unsigned8 / byte)
Value
(Integer16 / Unsigned16 / word)
Value
(Integer32 / Unsigned32 / double word)
Byte 13 Byte 14 Byte 15 Byte ...
String
(Visible string / octet string with an oponal length)
Field Data type Values
Value U8/U16/U32 Value range/length depends on the parameter format (see table above).
String U8 Visible string / octet string with an oponal length (n characters = n
bytes)
Response to a correctly executed write request
With an error-free mul-parameter request, only the response header is transmied, and the
complete data area is omied.
Response header
Byte 1 Byte 2 Byte 3 Byte 4
Request reference
(mirrored)
Response idencaon Axis
(mirrored)
Number of indices
Field Data type Values
Request reference U8 Mirrored value of the parameter request.
Response idencaon U8 0x02: Parameter has been wrien.
Axis U8 0x00 or 0x01
Number of indices U8 0x"n" (n = number of parameters addressed)
Response to a write error
In the case of a mul-parameter request, correct and possible faulty messages are summar-
ised in one telegram. They have the following data contents:
Correct message
•
Format: 0x40
•
Number of values: 0x00
Faulty message
•
Format: 0x44
•
Number of values: 0x01 or 0x02
•
Error code without addional informaon (for number of values = 0x01) or error code with
addional informaon (for number of values = 0x02)
A faulty access to a parameter "n" is indicated at the nth posion in the response telegram of
a mul-parameter request.
Response header
Byte 1 Byte 2 Byte 3 Byte 4
Request reference
(mirrored)
Response idencaon Axis
(mirrored)
Number of indices
Field Data type Values
Request reference U8 Mirrored value of the parameter request.
Response idencaon U8 0x82: Parameter has not been wrien.
The data in bytes 7 + 8 must be interpreted as an error code.
Axis U8 0x00 or 0x01
Number of indices U8 0x"n" (n = number of parameters addressed)
Conguring the network
PROFIBUS
Write parameter data
309
To Next Page
Loading...
Need help?
General