Troubleshooting ET 200S AI Module 'Not Available' Fault on S7-400

1. Problem Overview

An S7-400 station controlled by a CPU 416-3DP communicates with its field I/O through one or more ET 200S PROFIBUS-DP slaves. When an engineer extends an existing ET 200S station by adding a new Analog Input (AI) electronic module, every module on that station reports the diagnostic text "Module configured but not available". The new AI module is the same order number as the modules already in service, the hardware configuration was downloaded successfully, and the configuration in HW Config compiles without errors. Yet the moment the new module is plugged into the terminal block, the SF (group fault) LEDs on the IM 151 interface module light and every previously healthy module on the same ET 200S rack goes into a fault state.

The same physical expansion performed with a Digital Input (DI) module completes without error and leaves the station in RUN. This asymmetry is the diagnostic signature of the problem: it points to a slot/addressing conflict specific to analog modules rather than a generic PROFIBUS DP failure.

2. Affected System Architecture

The configuration described in the field report consists of three layers:

• Controller: S7-400 CPU 416-3DP with two DP interfaces (DP master and DP master/slave) and one MPI/DP combined interface.
• Field I/O network: PROFIBUS DP with one or more ET 200S stations. Each ET 200S uses an IM 151-1 (RS485) or IM 151-3 (PN/PN coupler) interface module as the PROFIBUS DP slave.
• Module rack: Terminal modules (TM-P / TM-E) carrying PM-E power modules and electronic modules (DI, DO, AI, AO).

The ET 200S family is documented in the Siemens ET 200S Distributed I/O System manual. The S7-400 CPU family and its diagnostic behavior are documented in the SIMATIC S7-400 Automation System reference. The CPU 416-3DP order-number family covers variants such as 6ES7416-3XP07-0AB0 and earlier releases; all share the same DP master diagnostic behavior described here.

3. Decoding the LED and Diagnostic Buffer

Before touching the hardware, read the LEDs on the IM 151 interface module and on the CPU 416-3DP. The LED pattern is the fastest way to discriminate the root cause.

Open the CPU diagnostic buffer in STEP 7 (Online → Accessible Nodes → CPU 416-3DP → Diagnostic Buffer). Typical entries when the AI module is plugged into an unconfigured slot are:

• Event ID 0x0E – "Module not available / Module slot empty"
• Event ID 0x0F – "Module mismatch / wrong module plugged"
• Event ID 0x39 – "Station failure" of the DP slave
• Event ID 0x38 – "Station return" of the DP slave

The exact wording is field-configurable; the diagnostic event codes follow the PROFIBUS DP standard EN 50170 / IEC 61158. Decode each entry with the event ID table in the S7-400 reference manual.

4. Root Cause Analysis

Six root causes account for nearly every instance of this fault in the field. They are listed in order of statistical likelihood based on the symptom asymmetry (AI fails, DI succeeds).

4.1 Missing Termination Module (TM-E) at the End of the ET 200S Rack

Every ET 200S station must terminate the backplane with the dedicated termination module (for example, 6ES7193-4CA00-0AA0). The termination module carries the bus terminator that closes the ET 200S internal backplane. When a new electronic module is inserted without the terminator in place, the new module physically closes the backplane but the previously open end of the rack was never terminated. The IM 151 detects a configuration drift and forces the entire station to "module not available" until the slot table is re-initialised. DI modules often mask this fault because they draw less backplane current during the slot enumeration pulse; AI modules draw the full address-decoding current and trigger the backplane error first.

4.2 OB 121 / OB 122 Not Loaded in the CPU

When the user program reads from an I/O address that is not currently available, the CPU operating system calls OB 122 (I/O access error). If OB 122 is not loaded, the CPU transitions to STOP. Likewise, OB 121 handles programming errors. On a CPU 416-3DP that has just experienced a station failure event, the operating system may generate access errors against the freshly inserted module's address before the module is fully parametrised. With OB 122 absent the CPU goes to STOP and the CPU's diagnostic buffer stops updating, masking the true root cause.

4.3 Slot Address Re-numbering When a New Module Is Inserted

When you insert a new module in slot N, every module that previously occupied slot N+1, N+2, ... shifts to slot N+1, N+2, ... on the backplane. The IM 151 reports this as a slot mismatch because HW Config still expects the old slot occupancy. The CPU pushes a "module configured but not available" event for every slot that just shifted, even though the modules are physically present. DI modules often survive this because the user program is rarely reading their inputs during the seconds after physical insertion; AI modules are typically read every scan, so the user program triggers OB 122 calls during the shift window.

4.4 Wrong Terminal Module Type

Every electronic module in the ET 200S requires a specific terminal module type. AI modules in particular require the TM-P (parameterisable) terminal module or, for some 2/4-wire variants, a TM-P with the correct power-feed strap. If the new AI module is seated on a TM-E terminal module borrowed from a DI block, the module powers up but cannot complete parameterisation, and the IM 151 reports the slot as "not available".

4.5 Wrong Address Range in HW Config

The IM 151-1 supports two address modes: standard addressing and compact addressing. If the new AI module is configured with addresses that fall outside the configured input range of the station, the CPU cannot reach it and reports "module not available". Right-click the DP slave in HW Config and verify that the I/O address range starts at the byte expected by your STEP 7 program.

4.6 GSD File or DP Slave Version Mismatch

If HW Config was opened against a newer STEP 7 version than the one originally used to configure the station, the IM 151-1 GSD file may have been re-imported with a different default parameter set. The CPU then expects a parameter block the IM 151 does not have, and every module on the station is reported as not available.

5. ET 200S Slot Mechanics and Termination

The ET 200S backplane is a passive bus terminated only at the last slot. The slot table in the IM 151 starts at slot 1 immediately after the IM 151 head module and ends at the slot that holds the termination module. The maximum number of slots is IM-dependent:

Every electronic module occupies one slot. A PM-E power module also occupies one slot but is transparent to the I/O address map. The TM-P terminal module that hosts an AI module must be of the correct revision: a 2-wire AI module needs the TM-P with terminal A4/A8 shorted to 24 V sensor supply, while a 4-wire AI module needs the TM-P with a separate power-feed strap.

6. PROFIBUS DP Configuration in HW Config

Open the STEP 7 project and navigate to HW Config. Verify the following before downloading:

1. The DP slave address on the ET 200S IM 151 matches the rotary switch on the physical module (range 1-125; addresses 0 and 126/127 are reserved).
2. The slot table in HW Config lists the new AI module in the same physical slot in which it is plugged.
3. The I/O address range starts at a byte boundary that does not collide with another DP slave (use PLC → Check Address Consistency).
4. The diagnostic interrupt enable for the AI module matches the OB 82 loading in the CPU.
5. The GSD file for the IM 151 (for example, SIEM811F.GSD or SI01811F.GSE depending on STEP 7 release) is loaded from the Tools → Install GSD File menu. Do not mix GSD revisions across the project.

After saving and compiling, perform a full download to the CPU, not just a partial delta download. The CPU 416-3DP must be in STOP during the hardware configuration download; if it is in RUN-P it will refuse the new slot table.

7. Step-by-Step Resolution Procedure

Apply the following procedure in the order shown. Stop at the first step that resolves the fault.

Step 1 – Load OB 121 and OB 122 into the CPU

This protects the CPU from going to STOP during I/O faults and lets the diagnostic buffer continue to update.

1. Open the S7 Program / Blocks container.
2. Insert OB 121 (Programming Error) and OB 122 (I/O Access Error). Leave the bodies empty – the default system handling is sufficient.
3. Download both OBs to the CPU in RUN-P.

Step 2 – Verify the Termination Module Position

1. Power down the ET 200S station (24 V OFF to the IM 151 and PM-E).
2. Confirm that the right-most terminal module is the ET 200S termination module (TM-E, dark grey back shell).
3. If you need to add a new AI module between the existing modules and the terminator, plug it in, then confirm the terminator is still the last module.

Step 3 – Verify the Terminal Module Type Under the New AI Module

1. Check the catalogue number stamped on the side of the terminal module under the new AI module.
2. Cross-reference it against the table in the ET 200S manual for the AI module order number.
3. Replace the terminal module if the wrong type is fitted (this is a hot-swappable repair if the station is in a redundant power architecture; otherwise power down).

Step 4 – Re-Compile and Re-Download HW Config

1. In HW Config, right-click the DP slave → Object Properties → verify the slot numbering matches the physical rack.
2. Press Ctrl+S to save, then Station → Save and Compile.
3. Put the CPU in STOP and download the entire station (PLC → Download → All).
4. Place the CPU back in RUN.

Step 5 – Read the Online DP Slave Diagnosis

1. In HW Config, right-click the DP slave → DP Slave Diagnostics.
2. Expand the tree: Station → Slot → Module. Confirm the new AI module reports Module OK and that its order number matches the configured order number.
3. If the slot still reports not available, right-click → Operating Mode → compare against the configured mode.

Step 6 – Clear and Re-Parametrise

If the slave still reports the fault, perform a station clear and re-parametrise sequence:

1. Set the CPU to STOP.
2. From PG/PC online, use PLC → Clear/Reset and then re-download the entire project including the system data blocks (SDB).
3. Bring the CPU back to RUN and observe the diagnostic buffer.

8. Verification and Acceptance Test

After applying the fix, perform the following acceptance checks before handing the station back to operations:

• LED check: All SF, BF, EXTF, BUSF LEDs OFF. Only the green ON LED remains lit on the IM 151 and the CPU.
• Online HW Config: All slots in the DP slave tree show "Module OK".
• Diagnostic buffer: No new "Module configured but not available" or "Station failure" events within 10 minutes of operation.
• Process I/O test: Force the input channels of the new AI module from the field (4-20 mA loop or voltage source) and read back the value with a VAT table in STEP 7. The value must match within the configured resolution.
• Cyclic scan test: Leave the station in RUN for at least 30 minutes and confirm that no transient faults are logged.

9. Preventive Configuration Best Practices

To prevent recurrence on future expansions, apply the following standards during project engineering:

1. Always load OB 121 and OB 122 in every S7-400 project. Without them, every I/O access error is a STOP event.
2. Reserve spare slots. When designing a new ET 200S station, leave at least one empty TM-P between the active modules and the termination module. This avoids the need to disturb the termination module during future expansions.
3. Document the slot map. Print the HW Config rack view and pin it to the cabinet door. Future maintainers will know exactly which TM type fits each slot.
4. Pin the GSD file version in the project documentation. If you upgrade STEP 7, re-import the GSD and verify that no implicit parameter changes occur.
5. Standardise on one AI module family across the plant. Mixing 6ES7134-4FB0x and 6ES7134-4GB0x modules in the same project complicates HW Config and increases the chance of a parameter mismatch.
6. Use a label printer to mark each terminal module with its module type. Avoid hand-written labels; they fade in the cabinet heat.

10. Extended Diagnostics Matrix

Use the matrix below to triage the fault based on the diagnostic buffer pattern and the LED state at the IM 151 and the CPU.

11. Frequently Asked Questions