6BMESSAGES AND DIAGNOSTICS
The following message paths are possible:
• Output of DR31/32 to the program SIWATOOL U
• Output via the SIWA_U function block to its message outlets
• Diagnostic alarms in SIMATIC CPU with OB82 evaluation
• Process alarms (for limit value monitoring only) in the SIMATIC CPU with
the evaluation in the process alarm OBs.
7.3 Detecting messages with the aid of SIWATOOL U
The messages are not buffered on the module. After the switching over of
SIWATOOL U to "online" operation, all status and message bits are polled and
displayed in the online error log with the corresponding message texts.
7.4 Detecting messages using SIWA_U FB
Using FB SIWA_U, all messages of the SIWAREX U module can be detected via
the message bits and processed in the controller. By means of an output variable
FB_ERR, additional errors in the working of the SIWA_U FB are reported
(see Chapter 8 Communication in SIMATIC S7).
7.5 Detecting messages with the aid of the diagnostic alarms in the
SIMATIC CPU
7.5.1 Evaluating the diagnostic alarm with OB82
With the aid of the evaluation of the diagnostic alarms, the operating messages
(hardware faults) can be detected in the SIMATIC CPU.
In the case of enabled diagnostic alarm (in the HW config.) operating faults are
reported to the S7 CPU per diagnostic alarm. The diagnostic messages can be
evaluated via the OB82 local data.
Procedure:
1. If a diagnostic alarm is triggered, the diagnostic alarm OB (OB82) is called. If
this OB is not loaded in the S7 CPU, the CPU goes into the "STOP" operating
state.
2. If the diagnostic alarm is to be evaluated, a program for the evaluation of the
OB82 local data or of the diagnostic data sets DS0 and DS1 is to be
implemented in OB82.
You can find further information on the evaluation of DS0 and DS1 in the SIMATIC
S7–300/400 reference manual.
7-44
SIWAREX U
To Next Page
Loading...
