5.9.3 Diagnostic interrupt
An interrupt for the corresponding channel operating mode can only be
triggered if you have additionally parameterized ‘DiagProcess’ at
‘Select interrupt’ of the ‘Basic parameters’ .
Via the parameterization (record set 7Fh) you may activate a global diagnostic interrupt
for the module. A diagnostic interrupt occurs when during a process interrupt execution in
OB 40 another process interrupt is thrown for the same event. The initialization of a diag-
nostic interrupt interrupts the recent process interrupt execution in OB 40 and branches in
OB 82 to diagnostic interrupt processing
incoming
. If during the diagnostic interrupt pro-
cessing other events are occurring at other channels that may also cause a process res.
diagnostic interrupt, these are interim stored. After the end of the diagnostic interrupt pro-
cessing at first all interim stored diagnostic interrupts are processed in the sequence of
their occurrence and then all process interrupts. If a channel where currently a diagnostic
interrupt
incoming
is processed res. interim stored initializes further process interrupts, these
get lost. When a process interrupt for which a diagnostic interrupt
incoming
has been
released is ready, the diagnostic interrupt processing is called again as diagnostic inter-
rupt
outgoing
. All events of a channel between diagnostic interrupt
incoming
and diagnostic inter-
rupt
outgoing
are not stored and get lost. Within this time window (1. diagnostic inter-
rupt
incoming
until last diagnostic interrupt
outgoing
) the SF-LED of the CPU is on. Additionally
for every diagnostic interrupt
incoming
/
outgoing
an entry in the diagnostic buffer of the CPU
occurs.
Every OB 82 call causes an entry in the diagnostic buffer of the CPU containing error
cause and module address. By using the SFC 59 you may read the diagnostic bytes. At
de-activated diagnostic interrupt you have access to the last recent diagnostic event. If
you've activated the diagnostic function in your hardware configuration, the contents of
record set 0 are already in the local double word 8 when calling the OB 82. The SFC 59
allows you to also read the record set 1 that contains additional information. After leaving
the OB 82 a clear assignment of the data to the last diagnostic interrupt is not longer pos-
sible. The record sets of the diagnostic range have the following structure:
Function
Example:
Diagnostic interrupt pro-
cessing
VIPA System MICRO
Deployment I/O periphery
Diagnostic and interrupt > Diagnostic interrupt
HB400 | CPU | M13-CCF0000 | en | 16-47
131
Содержание VIPA System MICRO M13-CCF0000
Страница 35: ...3 2 2 Interfaces VIPA System MICRO Hardware description Structure Interfaces HB400 CPU M13 CCF0000 en 16 47 35 ...
Страница 211: ...Appendix VIPA System MICRO Appendix HB400 CPU M13 CCF0000 en 16 47 211 ...
Страница 212: ...Content A System specific event IDs B Integrated blocks VIPA System MICRO Appendix HB400 CPU M13 CCF0000 en 16 47 212 ...