www.balluff.com
27
8
Diagnostics
8.2.
Diagnostics
telegram
The diagnostics telegram is comprised of various blocks. The first 6 bytes are defined by the
Profibus standard EN 50170. The following 4 bytes are Device-specific and ID-specific
diagnostics information (2 bytes each). For each channel-specific diagnostic 3 bytes of
diagnostics information are added (min. 6 and max. 244 bytes).
8.3.
Norm diagnostics
Byte
Bit
7
6
5
4
3
2
1
0
0
Status 1
1
Status 2
2
Status 3
3
Master address
4
Indent_Number_High_Byte: 0Bhex
5
Indent_Number_Low_Byte: 1Ahex
Note, Tip!
When coding the norm-specific diagnostics: 1 = activated, 0 = deactivated
Norm diagnostics
coding
In the following the coding of bytes 0 to 3 of the norm diagnostics is described.
Byte 4 and Byte 5 (Identnumber) are fixed.
Status 1
Byte 0, Status 1
Bit
Meaning
0
Station_non_existent
The DP-Device always sets the bit to 0. The DP-Master sets it to 1 if the DP-Device
cannot be reached.
1
Station_not_ready
The DP Device sets the bit to 1 if it is not yet ready for data exchange.
2
Cfg_Fault
The DP Device sets the bit to 1 if the configuration data last received from the
Master do not agree with those which the DP Device determined.
3
Ext_diag
If the bit is set to 1, there is a diagnostics entry in the Device specific diagnostics
area (Ext_Diag_Data). A further diagnostic follows in the telegram.
4
Not supported
The DP Device sets the bit to 1 if a function was requested which is not supported
5
Invalid_Device-Response
The DP-Device always sets the bit to 0. The DP-Master sets it to 1 if it receives an
implausible response from the DP Device.
6
Prm_fault
The Device sets the bit to 1 if the last parameter telegram was defective (e.g. wrong
length, wrong ID number, invalid parameters).
7
Master_lock
The DP Device always sets the bit to 0. The DP Master sets it to 1 if the DP Device
was parameterized by a different Master (Lock from another Master, here: Address
in byte 3 not equal to FFhex and not equal to its own address).
