Probus DP V1 Agile 06/201026
Handling of the Objects
16.1.1 Request Identification
Structure of the request identification AK (output data set, Master
Request
Identification AK
Data type Function
0 - no request
1 int/uint , long read parameter value
2 int/uint write parameter value int/uint
3 long write parameter value long
6 int/uint , long Array read parameter value Array
7 int/uint Array write parameter value int/uint Array
8 long Array write parameter value long Array
Array: Applies to data set change-
over capable parameters; the required data must be specified in
data set/INDEX. Otherwise, data set/INDEX = 0.
16.1.2 Response Identification
Structure of the reply identification AK (input data set, Slave
Reply
Identification AK
Data type Function
0 - no request
1 int/uint transmit parameter value int/uint
2 long transmit parameter value long
4 int/uint Array transmit parameter value int/uint Array
5 long Array transmit parameter value long Array
7 - request cannot be implemented
8 - no control sovereignty for PKW interface
If the reply identification = 7 (request cannot be implemented), an error code is inserted in PWE low
(Byte 6/7).
If the reply identification = 8 (no control sovereignty), the master has no writing right to the slave.
16.1.3 Fault Messages
Coding of the fault messages in the reply data set PWE-Low/Low-Byte in Byte 7 (Slave Master):
Fault No. (dec.)
acc. to
PROFIDRIVE
Meaning
0 Inadmissible parameter number PNU
1 Parameter value cannot be altered
2 Lower or upper parameter value limit exceeded
3 Faulty data set
4 No data set change-over capable parameter
5 Wrong data type
18 Other fault
20 Systembus not responding
Extension Meaning
101
103
Fault occurred in reading the EEPROM
104
Fault occurred in writing the EPROM
105
Check sum fault in EEPROM occurred
106
Parameter may not be written in operation
107 Values of the data sets differ
108 Unknown request