beautypg.com

3 response to a read error, Response to a read error, 9parameter data transfer – Lenze E94AYCPM User Manual

Page 64

background image

9

Parameter data transfer

9.3

PROFIdrive parameter data channel (DP-V1)

64

Lenze · E94AYCPM communication module (PROFIBUS®) · Communication Manual · DMS 12.0 EN · 11/2012 · TD17

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

9.3.3.3

Response to a read error

Response header

Parameter format

Note!

In case of a multi-parameter request, correct and possibly faulty messages are

summarised in one telegram.
Correct message

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

Reading parameter data from the

controller

"

( 61)

.

• 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)

Byte 5

Byte 6

Format

Number of values

Field

Data type

Values

Format

U8

0x44: Error

Number of values

U8

0x01: Error code without additional information

0x02: Error code with additional information