Chapter 4 Deployment CP 343-2P ASI
Manual VIPA System 300V
4-14
HB130E - CP - RE_343-2AH10 - Rev. 08/41
Diagnostic functions
There is the possibility to enable a diagnostic interrupt for the CP by means
of the CP properties with the register "Operating parameters".
A diagnostic interrupt may only be released in the
protected mode
; this is
not possible in
configuration mode
.
With a diagnostic requirement the CPU branches to the OB 82. To this
diagnostic it may be reacted by an appropriate program.
The following error events may release a diagnostic interrupt:
•
Changes to the AS-i slave configuration
•
AS-i power fail
•
Flash-ROM error of the CP
On error if diagnostic is enabled the CP releases a diagnostic request to
the CPU both with incoming and going event.
After that the CPU interrupts the cyclic user program and jumps to the OB
82. Here you can react accordingly to an error event.
More information about the error events may be accessed by the local
bytes of the OB 82.
If OB 82 is not programmed, the CPU changes to STOP.
The CP produces diagnostic interrupts exclusive in the
protected mode
.
If the CPU changes to STOP respectively the CP changes to the
configuration mode
, the interrupt history is reset; in other words, every error
bit of DS 0 is reset.
If the CP changes from the
configuration mode
to the
protected mode
and
if there is a configuration error at this point in time, this is signaled with a
diagnostic interrupt.
Via OB 82 you have access to detailed error information by means of the
SFC 59 RD_REC (read record set). The diagnostic data are consistent until
leaving the OB 82. The diagnostic interrupt is acknowledged by leaving the
OB 82.
The diagnostic data are in record set 0 (DS 0) and record set 1 (DS 1). DS
0 consists of 4byte, which describe the current state of the CP.
Overview
Error events
Sequence of
diagnostic
interrupt
processing
Interrupt behavior
and operating
modes
read diagnostic
data with SFC 59