Troubleshooting PROFIBUS I-O Access Errors (OB122) and OB Execution Time Limits in S7-400H Systems

In SIMATIC PCS 7 S7-400H systems, the diagnostic buffer errors 'Data could not be read' and 'Data could not be written' for a specific slave slot (e.g. Slot 4 of Slave 9) indicate a peripheral access error (Event ID 16#38B2/38B3) where the CPU cannot communicate with the I/O module. Each failed read/write triggers Organization Block OB122 (I/O Access Error OB). When repeated across cyclic OBs, these high-frequency interrupts consume excessive CPU processing bandwidth, triggering the warning 'Net time consumption of all OBs exceeds max limit'. To resolve this, inspect the physical module in Slot 4 for power or hardware failure, reseat the active bus module, and ensure OB122 is loaded in the CPU to prevent controller STOP.

Executive Summary

In fault-tolerant SIMATIC S7-400H automation systems, the controller operating system is designed to maintain high process availability during component faults. However, when an individual distributed I/O module in an ET 200M station (e.g. Slot 4 of PROFIBUS DP Slave 9) fails, loses power, or experiences backplane communication disruption, the master CPU generates recurrent diagnostic buffer entries: 'Data could not be read' and 'Data could not be written'. Concurrently, the CPU diagnostic buffer frequently logs the critical timing alarm: 'Net time consumption of all OBs exceeds max limit'. Automation engineers often treat these as unrelated faults. In reality, the high-frequency invocation of error-handling interrupt routines (OB122) starves cyclic execution cycles, threatening CPU watchdog overruns. This technical guide explains the causal chain and provides structured diagnostic steps.

Peripheral Access Error Mechanics in S7-400 Controllers

The S7-400 CPU interacts with distributed field modules through two mechanisms:

Process Image Partition (PIP) Updates: Handled cyclically at the start and end of execution OBs.
Direct Peripheral Access (PIW / PQW): Executed directly by channel driver blocks (Pcs7AnIn, Pcs7DiIn).

When the CPU addresses an I/O module over the ET 200M backplane and receives no hardware acknowledge signal (due to a pulled module, wire-break, blown channel fuse, or backplane bus fault), the CPU hardware generates a Peripheral Access Error (Event ID 16#38B2 for read, 16#38B3 for write).

Organization Block OB122 and Interrupt Execution Latency

When a peripheral access error occurs:

The CPU immediately suspends active program execution in the current cyclic OB (e.g. OB32 or OB35).
The CPU operating system calls OB122 (I/O Access Error Organization Block).
If OB122 is not present in the CPU's block folder, the CPU immediately enters STOP mode to prevent unpredictable behavior.
If OB122 is present, it logs the fault and returns execution to the interrupted program block.

Why I/O Failures Trigger 'Net Time Consumption Exceeded' Warnings

In a large PCS 7 project with hundreds of channel driver blocks:

If a 16-channel analog input module fails, every driver block attempting to read peripheral addresses (PIWxxx) triggers OB122.
In high-speed cyclic OBs (e.g. OB35 executing at 100 ms or OB36 at 50 ms), calling OB122 hundreds of times per second imposes severe interrupt overhead.
The CPU execution scheduler monitors execution duration: If total time spent servicing cyclic OBs and interrupts exceeds the configured threshold (typically 80% to 100% of cycle time), the CPU flags the alarm: 'Net time consumption of all OBs exceeds max limit'.

Peripheral Access Error Diagnostic Matrix

The following table categorizes peripheral access error symptoms, causes, and impacts on S7-400H controllers:

Diagnostic Buffer EventMeaningSystem ImpactRoot CauseEngineering Remediation16#38B2 / 16#38B3Peripheral access errorCalls OB122 cyclicallyModule pulled, failed, or power lossRestore 24V DC power; reseat module.16#4301 / 16#4302OB execution time exceededThreatens cycle watchdog tripOB122 interrupt stormFix underlying hardware failure.CPU STOP on I/O errorStop due to missing error OBTotal plant shutdownOB122 missing from block folderDownload OB122, OB82, OB83 to CPU.SF LED red on ET 200MSystem Fault on stationI/O channels invalidHardware failure on designated slotInspect slot module diagnostics in HW Config.BF LED red on ET 200MBus Fault on IM153Loss of entire rackPROFIBUS cable damage / loose connectorCheck termination resistors and cable shielding.

Step-by-Step Troubleshooting and Resolution Procedure

Method 1: Isolating the Faulty Hardware Module via HW Config Online

Open SIMATIC Manager on the Engineering Station.
Open the station HW Config.
Select Target System > Diagnostics > Hardware Diagnostics (go online in HW Config).
Locate DP Slave 9 on the PROFIBUS DP line. Note the red warning symbol.
Double-click Slave 9 to view the physical rack layout.
Click on Slot 4. The Module Information dialog details the exact channel fault (e.g. 'No external auxiliary voltage', 'Internal module fault', or 'Module removed').

Method 2: Physical Inspection and Active Bus Module Maintenance

Locate the physical ET 200M rack corresponding to Slave 9 in the control cabinet.
Inspect the module seated in Slot 4 (counting from the power supply and interface module IM153-2).
Check the module's front LEDs: If the SF LED is lit red or LEDs are completely off, verify the 24V DC supply wiring to the front connector.
If auxiliary power is healthy, unlatch and extract the front connector.
In an active bus module setup (hot-swapping supported), carefully remove the module and inspect the active bus module connector (6ES7195-7HB00-0XA0) on the DIN rail.
Reseat or replace the module with an identical spare part.
Reinsert the front connector. Confirm that the module's SF LED turns OFF.
Check the CPU diagnostic buffer; confirm that 'Data could not be read/written' events cease.

Verification

To verify that peripheral communication and CPU cycle stability are restored:

Diagnostic Buffer Audit: Clear the CPU diagnostic buffer. Monitor for 5 minutes. Confirm that zero Event ID 16#38B2 or 16#38B3 errors are logged.
Cycle Time Inspection: In HW Config online diagnostics, check CPU Cycle Time. Confirm that current cycle time drops back to normal operational levels (typically 20-50 ms).
Channel Quality Codes: Open the CFC charts linked to Slot 4. Confirm that channel driver blocks output quality code 16#80 (Good) and live process values update smoothly.

Limitations and Operational Precautions

Always Download Error OBs: Ensure error OBs (OB82, OB83, OB85, OB86, OB121, OB122) are downloaded to all CPUs; missing error OBs cause the CPU to trip to STOP on minor field faults.
Hot-Swapping Prerequisites: Only pull modules under power if the ET 200M station is installed on active bus modules; pulling modules on standard compact backplanes interrupts communication to all downstream modules.
Do Not Suppress OB122 Indiscriminately: While OB122 can be programmed to ignore specific address ranges, masking errors blinds operators to field instrumentation failures.

Engineer FAQ

Why did the CPU not enter STOP when the module failed?

Because OB122 was loaded in the CPU block folder, intercepting the error and allowing the CPU to continue running.

Can a defective active bus module affect adjacent slots?

Yes, a bent pin or cracked connector on an active bus module can propagate electrical noise and communication faults to neighboring slots.

What parameter in CPU properties configures the 'Net time consumption' threshold?

Under CPU Properties > Cycle/Clock Memory, the parameter 'Scan cycle monitoring time' and maximum cyclic interrupt execution limits govern this alarm.

Technical References

Related Tags

https://industrialautomation.net/search?query=simatic-pcs7
https://industrialautomation.net/search?query=s7-400h
https://industrialautomation.net/search?query=profibus-dp
https://industrialautomation.net/search?query=diagnostics

6 respuestas

Troubleshooting PROFIBUS I-O Access Errors (OB122) and OB Execution Time Limits in S7-400H Systems