Structure \ of the Diagnosis Block via FBP with S500 DC505-FBP

If a DC505-FBP module is connected via a FieldBusPlug, then the fieldbus master receives diagnosis information by an extended diagnosis block. The following table shows the structure of this diagnosis block:

Byte number	Description	Possible values
0	Data length (header included)	18
1	FBP diagnosis byte	0 = Communication with DC505-FBP OK 1 = Communication with DC505-FBP failed other values according to FBP documentation
2	DC505-FBP diagnosis byte, slot number	31 = DC505-FBP (e. g. error at integrated 8DI/8DC) 1 = 1st connected S500 I/O Module … 7 = 7th connected S500 I/O Module
3	DC505-FBP diagnosis byte, module number	According to the I/O Bus specification passed on by modules to the fieldbus master
4	DC505-FBP diagnosis byte, channel	According to the I/O Bus specification passed on by modules to the fieldbus master
5	DC505-FBP diagnosis byte, error code	According to the I/O Bus specification Bit 7 and bit 6, coded error class 0 = E1 1 = E2 2 = E3 3 = E4 Bit 0 to Bit 5, coded error description passed on by modules to the fieldbus master
6	DC505-FBP diagnosis byte, flags	According to the I/O-Bus specification Bit 7: 1 = coming error Bit 6: 1 = leaving error Bit 2 to Bit 5: reserved Bit 1: 1 = explicit acknowledgement Bit 0: 1 = static error passed on by modules to the fieldbus master Value = 0: static message for other systems, which do not have a coming/leaving evaluation
7	Error code explicit / readable	Calculated from byte No. 8, bits 0 to 5
8	Error class explicit / readable	Calculated from byte No. 8, bits 6 to 7 Values: 1 = EC1 2 = EC2 3 = EC3 4 = EC4
9	Module type	From module type list, created at initialization 0 = DI 1 = AI 2 = DO 3 = AO 4 = DC 5 = AC 6 = mixed module
10..15	reserved