Table of Contents
Advertisement
Diagnostics and error behavior
Diagnostics by diagnostics interrupt
7.4 Diagnostics by diagnostics interrupt
Overview
Diagnostics interrupt
OB 82
Diagnostics information
104
The CP 341-1CH01 can trigger a diagnostics alarm on the assign CPU, thus indicating a
malfunction of the CP. You can specify at parameterization whether the CP is to trigger a
diagnostics interrupt or not in the event of an error. As default Diagnostics interrupt is
deactivated.
At an activated interrupt the following events may release a diagnostics interrupt:
n
Wire break at RxD line
n
Error in parameterization
In the event of an error the CP provides diagnostics data on the backplane bus. These
were read by the CPU and entered to its diagnostics buffer. At any time the CPU diagnos-
tics buffer may be read with the PC by means of the PLC functions. When a diagnostics
interrupt occurs, the SF LED lights up and the OB 82 is called.
n
As soon as an error occurs the OB 82 is called with the diagnostics data as start-up
information. Here you have the possibility to react on the diagnostics by means of a
corresponding programming.
n
If you have no OB 82 programmed, the CPU automatically changes to STOP mode.
The CP provides 4byte of diagnostics information. Depending on the event the 4byte are
used as follows:
Event
Wire break at RxD
Parameterization error
Byte 0
Byte 1
25h
0Ch
83h
0Ch
HB130 | CP | 341-1CH01 | en | 18-40
VIPA System 300S
Byte 2
Byte 3
02h
00h
00h
00h
Advertisement
Table of Contents
