Introduction
No matter how stable a system is, unexpected issues can still arise. An excellent program not only runs correctly but also can “respond calmly” when a fault occurs, clearly informing maintenance personnel “where the problem lies.” This is the diagnostic and error handling function of a PLC, akin to an airplane’s “black box.”
1. Organization Blocks: The Scheduling Center of the PLC Operating System
Organization blocks serve as the interface between the operating system and user programs. Different events (such as startup, cyclic execution, timed interrupts, and errors) trigger the execution of different OBs.
-
OB1: The main program cyclic block, the one we are most familiar with.
-
OB100: The startup organization block, executed once when the PLC transitions from STOP to RUN, used for initialization.
-
OB82: Diagnostic error interrupt, triggered when a hardware fault is detected by the module.
-
OB121/122: Programming error/access error organization blocks.
Figure 1: List of Organization Blocks in TIA Portal2. Hardware Diagnostics: Starting with the LED Indicators
When a PLC fails, the first step is to observe the status LED indicators on the CPU and modules.
-
RUN/STOP: RUN green steady = running; STOP yellow steady = stopped.
-
ERROR/FAULT: Red flashing or steady indicates an error.
-
MAINT: Yellow steady indicates maintenance is required.
Figure 2: Detailed Diagram of S7-1200 CPU Status Indicators3. Software Diagnostics: Insight into Everything in TIA Portal
-
Online and Diagnostics: After bringing the PLC online, in the “Online and Diagnostics” view, you can check the detailed status of the CPU, log information, and even directly identify missing modules.
-
Module Information: You can view diagnostic information for each IO module, such as channel short circuit/break alarm.
Figure 3: Diagnostic Buffer in TIA Portal’s “Online and Diagnostics” View4. Programming Error Handling: Preventing Issues Before They Occur
-
Using RET_VAL (Return Value): Many instructions (such as communication instructions) have a RET_VAL output parameter. By checking whether this value is 0, you can determine if the instruction executed successfully.
-
Writing Error Handling OB: For example, writing a program in OB121 that, when a programming error occurs, does not cause the PLC to halt, but instead logs the error address and continues running.
Figure 4: Monitoring the RET_VAL Parameter of a Communication Instruction
Figure 5: Writing a Simple Error Logging Program in OB121Conclusion
Mastering diagnostic and error handling techniques means transforming your program from “fragile” to “robust.” It not only reduces unexpected downtime but also allows for quick fault localization, greatly enhancing equipment maintenance efficiency, which is an essential quality for senior engineers.