Testing functions, Diagnostics and Fault Elimination
S7-300 Programmable Controller Hardware and Installation
10-4 A5E00105492-01
10.3 Overview: Diagnostics
Introduction
System errors can occur especially in the Commissioning phase. Tracking these
errors might be a time-consuming effort, since they can occur likewise on hardware
and on software side. Here, the multitude of testing functions ensures
commissioning without problems.
Errors duringoperation are almost always a result of faults or damage to the
hardware.
Types of Error
Errors the S7 CPUs can recognize and to which you can react with the help of
organization blocks (OBs) can be split into the following two categories:
• Synchronous errors: Errors you can relate to a specific point in the user
program (e.g. error when accessing a peripheral module).
• Asynchronous errors: Errors you can not relate to a specific point in the user
program (e.g. cycle time exceeded, module error).
Error Handling
Programming with foresight and, above all, knowledge and proper handling of
diagnostic tools puts you into an advantageous position in error situations:
• You can reduce the effects of errors.
• It makes it easier for you to locate errors (e.g. by programming error OBs).
• You can limit downtimes.
Diagnostics with LED display
SIMATIC S7 hardware offers diagnostics with LEDs.
These LEDs are implemented in three colors:
• Green LEDs report regular operation (e.g. supply voltage is applied).
• Yellow LEDs indicate special operating states (e.g. "Force" is active).
• Red LEDs report errors (e.g. bus error)
A flashing LED also indicates a special event (e.g. memory reset).
Cross-reference
Notes on diagnostics with LEDs are found in the Chapter below.
Notes on diagnostics of I/O modules capable of diagnostics are found in the
respective Manual.
To Next Page
Loading...
Need help?
General
