11
11-5
FM 351 Positioning Function Module
EWA 4NEB 720 6001-02
When the FM 351 initiates a diagnostic interrupt:
The system makes four bytes of interrupt information available in the in-
terrupt OB (OB 82) (see Table 6-3).
Further diagnostic bytes are accessible via the FC DIAG_INF which are
entered in the FC in the relevant channel DB.
The Bit 0.0 on the faulty module is set (OB82_MDL_DEFECT) and
The LED “SF” lights and “CH1”/“CH2” depending on the error.
With the aid of the diagnostic chart shown in Figure 11-2 you can see the
relationship between the separate bits.
0.0
0.1 0.2
0.3 2.3 0.3 0.4
9.0 9.1 11.0 11.1 8.0 8.1 8.2 8.7 10.0 10.1 10.2 10.7
7.0 7.17.0 7.1
Module faulty
Internal error External error
Channel error Channel error
Channel 1 Channel 2Channel 1 Channel 2
Figure 11-2 Diagnostic Chart: Bits in the Channel DBs from Byte 72 Onwards (DIAGNOSTIC_INT_INFO)
If you have allowed diagnostic interrupts in the basic FM 351 parameteriza-
tion, then please take note of the following relationship:
In the CPU STOP state the diagnostic interrupts from the FM 351 are in-
hibited.
If with the CPU in the STOP state, none of or not all of the existing errors
are rectified, the FM 351 signals the errors which have been already de-
tected and not yet rectified again as “incoming” after the transition into
the RUN state.
If all existing errors have been rectified in the CPU STOP state, then the
error-free FM 351 state is not signaled with a diagnostic interrupt after
the transition to the RUN state.
How Can the Diag-
nostic Interrupt Be
Localized?
Diagnostic
Interrupts in
Dependence of the
CPU Status
Error Handling