Contents
ILX69-PBS ♦ CompactLogix or MicroLogix Platform
User Manual
PROFIBUS Slave Communication Module
Page 62 of 102
ProSoft Technology, Inc.
April 27, 2016
The content of abExtDiagData[ ] follows the PROFIBUS decoding of extended diagnostic
data. The abExtDiagData[ ] can contain one or more diagnostic blocks. If the content does
not follow these rules, the confirmation will be returned with an error. Following table
describes the PROFIBUS-specified extended diagnostic blocks.
Extended Diag
Block
Byte 0 Byte 1
Byte 2
Byte 3
Byte 4 to n
Note
Alarm Block
Header
Alarm Type Slot Number Alarm Specifier DiagUserData[59
]
2*
Status Block
Header
Status
Type
Slot Number Status
Specifier
DiagUserData[59
]
1*
Device-related Block
Header
User data
User data
User data
User data
2*
Module-related Block
Header
Module0...7 Module8...15 Module16...23 Module24...255
1*
Channel-related Block Header
Channel
Error
-
-
1*
Note: The FSPMS_SetSlaveDiag service only sends the Status, Module and Channel-related Blocks.
The Alarm and the Device-related diagnostic blocks are listed here only to give an overview of PROFIBUS-
defined Extended Diagnostic Blocks. These blocks cannot be sent with the service “FSPMS_SetSlaveDiag”. The
Alarm Block will be transferred separately with the service “FSPMS_C1_Alarm_Notification”. The Device-related
Block is reserved for DPV0 Slaves only.
Example:
The following example shows how to transmit an extended diagnostic with two blocks; one
channel-
related and one status block. The channel diagnostic reports an “Overload”. The
status block reports a user-
specific status with the string “HELP” in Slot1.
