Debugging functions, diagnostics and troubleshooting
10.6 Diagnostics using status and error LEDs
S7-300, CPU 31xC and CPU 31x: Installation
10-12 Operating Instructions, Edition 08/2004, A5E00105492-05
Possible errors Response of the CPU Remedies
I/O access errors
An error has occurred when
module data was accessed
Calls OB122. CPU does
not STOP if OB122 is
loaded.
Check module addressing in HW
Config or whether a module/DP slave
has failed.
Global data communication
error, e.g. insufficient length of
the DB for global data
communication.
Calls OB87. CPU does
not STOP if OB87 is
loaded.
Check global data communication in
STEP 7. If required, correct the DB
size.
Tip:
• You can use SFC 39 to disable all interrupts and asynchronous error events.
• You can set the times in the cyclic interrupt OB32 and OB35, starting from 1 ms.
Note
The shorter the selected cyclic interrupt period, the more likely it is that cyclic interrupt
errors will occur. You must take into account the operating system times of the CPU in
question, the user program runtime and extension of the cycle time by active PG
functions, for example.
Reference
Details on the OBs and on SFCs required for their evaluation can be found in the
STEP 7
Online Help
and in the Manual
System Software for S7-300/400 - System and Standard
Functions
.
To Next Page
Loading...
