Siemens SIDOOR ATD4 W Series System Manual page 150

Controllers
5.5 Relay and fieldbus interfaces
The configuration described gives the following code for the standard module: 0xC1 0x15
0x15 0x00
Diagnostics
Extensive diagnostic possibilities are supported in the PROFIBUS DP. A DP master can query the
current diagnostics from the DP slave at any time. Diagnostic telegrams can write additional
device-specific diagnostics in the GSD file next to the standard diagnostics.
The DP slave can report in the data telegram at any time that current diagnostics are queued. To
do this it labels its data telegram (High Priority) in the cyclic data communication.
In normal cyclic data communication, the DP slave always answers with a (Low Priority) data
telegram. If an event requires a diagnostic query, the DP slave answers in the next cycle with high
priority. The DP master queries the diagnostics, and continues with the cyclic data
communication.
The diagnostic telegram is divided into several parts. The first 6 bytes and their meanings are
bindingly specified in the standard. The obligatory 6 bytes are followed by optionally one or
several diagnostic blocks.
Three additional device-related diagnostic bytes are defined for the PROFIBUS module. The first
device-related diagnostic byte defines the header, and the next two define the number of
diagnostic bytes.
These diagnostic blocks have the format for the device-related diagnostics, and are not
specified any further in DP-V0. The meanings of the individual bits are specified in the GSD file.
The following table shows the exact meanings of the bits for the SIDOOR ATD420W controller.
The diagnostic data relate exclusively to the internal communication bus between the SIDOOR
controller and the communication module.
Table 5-14
1.2 1.1 1.0 0.7 0.6 0.5 0.4 0.3 0.2 0.1 0.0 Device-related diagnostic bits
x
The 11 diagnostic bits are correspondingly divided between the two device-related diagnostic
bytes, i.e. bits 1.3 to 1.7 are not used or are reserved.
148
Device-related diagnostic bits
x
x
x
x
x
x Telegram length (LGE) false
x Remaining runtime exceeded
x Block check character (BCC) false
x Telegram start (STX) false
x Telegram type unknown (ADR)
Slave address false
Memory overflow
Parity error
Internal error
Answer delay time exceeded
Telegram type not identical
ATD4xxW for industrial applications
System Manual, 06/2022, A5E51901827B AA