The device related diagnostic data provide detailed information on the slave and the
peripheral modules. The length of the device related diagnostic data is fixed at 10byte
Byte
Bit 7 ... Bit 0
6
n
Bit 0 ... 5: Length device specific diagnostic data
–
001010: Length 10byte (fix)
n
Bit 6 ... 7: Code for device specific diagnostic
–
00: Code 00 (fix)
7
n
Device specific diagnostic message
–
12h: Error: Data length parameters
–
13h: Error: Data length configuration data
–
14h: Error: Configuration entry
–
15h: Error: VPC3 buffer calculation
–
16h: Missing configuration data
–
17h: Error: Comparison DP parametrization and configuration
–
40h: User specific diagnostic data is valid
8 ...10
reserved
11 ...15
User specific diagnostic data that are stored behind the diagnostic
status byte in the process picture of the CPU.
This data may be overwritten and forwarded to the master.
n
In case of a diagnostic the contents of Byte 11 ... 15 of the device specific diagnostic
data will be transferred to the process image of the CPU and this preceded by a
status byte.
n
Where this diagnostic block with a length of 6byte is located in the process image can
be defined via the CPU parameters.
n
You start diagnostics by means of a status change from 0
à
1 in the diagnostic status
byte.
n
This transmits the respective diagnostic message to the master.
n
A status of 0000 0011 is ignored!
The diagnostic block of the CPU has the following structure:
Byte
Bit 7 ... Bit 0
0
Diagnostic status byte
n
Bit 0: User specific diagnostic data
–
0: Invalid diagnostic data
–
1: Valid diagnostic data
(starting a diagnostic)
n
Bit 1: Delete diagnostic
–
0: Diagnostic deletion not valid
–
1: Diagnostic deletion valid
n
Bit 2 ... Bit 7: reserved
1 ... 5
User specific diagnostic data equal to
Byte 11 ... 15 of device specific diagnostic
Device specific diagnostic
data
Release diagnostic
VIPA System SLIO
Option: Deployment PROFIBUS communication
Deployment as PROFIBUS DP slave > Diagnostic functions
HB300 | CPU | 013-CCF0R00 | en | 19-30
262