![Pepperl+Fuchs AS-I 3.0 PROFIBUS Скачать руководство пользователя страница 81](http://html1.mh-extra.com/html/pepperl-fuchs/as-i-3-0-profibus/as-i-3-0-profibus_manual_1527734081.webp)
AS-i 3.0 PROFIBUS Gateway in Stainless Steel
Appendix: Example for startup on a Siemens S7
26
.9.20
1
3
81
12.2.7
System behavior on AS-i Config Error
If while running in protected mode a configured AS-i slave fails, an AS-i configura-
tion error is generated.
1.
The missing slave is shown on the display of the AS-i 3.0 PROFIBUS Gate-
way in Stainless Steel.
2.
The input flag AS-i Config Error bit 4 in byte 2 is set.
3.
If the standard parameters for the PROFIBUS hardware configuration were
applied unchanged for the VBG-PB-K30-D-S, the Gateway sets the ExtDiag
flag in the PROFIBUS data reply. This results in the controller signaling a
PROFIBUS slave error and invoking OB82. At the same time the event is
written to the diagnostic buffer of the CPU.
If the message for the ExDiagFlag is turned off in the PROFIBUS parameters, no
PROFIBUS message is generated and OB82 is not activated. This is always rec-
ommended for applications which do not have to respond immediately to an error
using OB82. In such cases the status can be processed using the message bit of
the AS-i Flags or the Flags + Fault Detector bits for the normal PLC cycle. Error
management can be structured on the basis of these messages.
In the diagnostic buffer of the CPU the configuration error which occurred is en-
tered with "Module error".
The affected VBG-PB-K30-D-S can be ascertained from the diagnostic address of
the slave which reports the error. This diagnostic address is evident as a parame-
ter of the OB82 when it is invoked. The event is declared as an incoming event.