3 response to a read error, Communication manual 8400 motec profibus – Lenze E84DGFCP User Manual

Page 57

Advertising
background image

EDS84DMOTPBUS EN 3.0 - 11/2011

L

57

Communication manual 8400 motec PROFIBUS

Parameter data transfer

PROFIdrive parameter data channel (DP-V1)

Parameter value

9.3.3.3

Response to a read error

Response header

Byte 7

Byte 8

Byte 9

Byte 10

Value

Field

Data type

Values

Value

String

Any (length > 4 bytes possible)

U8

0x00 .... 0xFF

U16

0x0000 .... 0xFFFF

U32

0x0000 0000 .... 0xFFFF FFFF

Note!

In the case of a multi-parameter request, correct and possible faulty messages

are summarised in one telegram. They have the following data contents:
• Correct message:

– Format: data type of the value requested
– Number of values: as described in chapter "

Reading parameter data from

the controller

"

( 55)

.

– Parameter value: value requested

• Faulty message

– Format: 0x44
– Number of values: 0x01 or 0x02
– Error code without additional information (for number of values = 0x01) or
– Error code with additional information (for number of values = 0x02)

A faulty access to a parameter "n" is indicated at the nth position in the response

telegram of a multi-parameter request.

Byte 1

Byte 2

Byte 3

Byte 4

Request reference

(mirrored)

Response identification

Axis

(mirrored)

Number of indices

Field

Data type

Values

Request reference

U8

Mirrored value of the parameter request

Response identification

U8

0x81: Parameter has not been read

• The data in the 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 requested)

Advertising