Troubleshooting Siemens ET 200S IM151-7 CPU MPI Connection Failure

The Siemens ET 200S with an IM 151-7 CPU (typical order number 6ES7 151-7AA21-0AB0, firmware V2.x and V3.x) is functionally a compact S7-300 class controller (instruction set compatible with CPU 314) integrated into the ET 200S backplane. It is widely used as a low-cost distributed controller in PROFIBUS DP networks. Engineers frequently encounter a specific failure mode where the IM 151-7 becomes inaccessible from STEP 7 V5.x over the MPI interface of a PC adapter (e.g., 6ES7 972-0CA23-0XA0), even though the node briefly appears in Accessible Nodes as a passive MPI node. This article documents the root cause, the diagnostic indicators, and the complete resolution matrix drawn from the official Siemens manuals and field-proven practice.

1. Problem Definition and Observable Symptoms

Engineers commissioning a small ET 200S station typically observe one or more of the following:

• STEP 7 V5.2 (or later) shows the IM 151-7 as a passive node in Accessible Nodes with the designation MPI = 3 (passive). The node does not respond to PLC > Display Accessible Nodes requests and Download / Online actions time out.
• RS-232 / USB PC Adapter (MPI) cannot reach the IM 151-7 even though the adapter is correctly installed, the COM/USB driver is loaded (SIMATIC PC Adapter USB driver package), and the bus termination is correct.
• MRES (memory reset) button briefly restores the MPI node in the node scan, but after a power cycle the same passive state returns because the load memory (MMC) re-injects the PROFIBUS DP slave configuration.
• Module information > Communication reports:
  • Transmission rate on interface X1: 187.5 kbps
  • Connection resources: 12 total, 11 free, 1 in use
  • PG communication: 1 assigned (the live connection)
  • OP / S7 / other: 0 assigned
• CPU LED pattern: SF (red) steady or flashing, BF (bus fault, red) on, RUN (green) off, STOP (yellow) on. This is the classic diagnostic signature of an IM 151-7 that is configured as a DP slave but has no PROFIBUS master on segment X1.

2. Hardware Reference: IM 151-7 CPU and Interface X1

The IM 151-7 CPU is documented in the Siemens manual SIMATIC ET 200S IM 151-7 CPU Interface Module. The relevant technical parameters are:

Because the IM 151-7 is part of the ET 200S distributed I/O family, the ET 200 Distributed I/O System manual provides the system-level context for how interface X1 participates in the bus. The manual states explicitly that the IM 151-7 can be integrated either as an MPI node or as a PROFIBUS DP slave, but not both simultaneously on X1.

3. Root Cause: MMC-Injected PROFIBUS DP Slave Configuration

The root cause of the passive MPI node and the loss of online access is almost always the same: the MMC currently inserted in the IM 151-7 contains a STEP 7 project whose hardware configuration sets interface X1 to "PROFIBUS DP slave" with a non-zero PROFIBUS address (typical addresses observed in the field: 2, 3, 4). When the IM 151-7 boots from that MMC, it activates the DP slave protocol stack on X1 and disables MPI token passing. The 9-pin X1 connector still carries the same electrical signals and the same 187.5 kbps default baud rate, so a node scan can still detect a termination and report a node at the configured MPI slot — but the IM 151-7 will not respond as a master peer.

This is the standard behaviour described in the IM 151-7 manual: if a PROFIBUS DP slave is configured but no PROFIBUS DP master is present on segment X1, the IM 151-7 enters STOP with BF on and SF on, and cannot be reached as an MPI device.

The two contributing factors that make this state "sticky" are:

1. Load memory on MMC. The hardware configuration and the assigned PROFIBUS address are persisted on the flash-based MMC. A memory reset (MRES) clears the work memory but does not erase the configuration stored on the MMC. A subsequent restart reloads the DP slave configuration.
2. PC Adapter (RS-232 / USB) cannot act as a PROFIBUS master. The 6ES7 972-0CA23-0XA0 PC Adapter is a passive programming device. It implements MPI master only and a very limited PROFIBUS master (typically 187.5 kbps with V5.x drivers and selected firmware). It cannot drive a 1.5 Mbps or higher DP segment and cannot be set up to talk to a slave using a real DP master parameter set.

The combination of the two factors above produces the field symptoms exactly as reported: a brief MRES-induced window where the node appears, then a permanent return to the inaccessible state.

4. Diagnostic Decision Tree

Use the following decision tree to confirm the root cause before applying the resolution matrix in Section 5.

Inline SVG flowchart (text-rendered for portability):

[CPU LED: BF red, SF red, STOP yellow]
            |
            v
[Cycle MRES; rescan accessible nodes]
            |
    +-------+-------+
    |               |
[Node shows]    [Node does not show]
M=3 passive        |
    |               v
    v         [Check PC adapter driver,
[Is MMC present? ]  bus termination,
    |               X1 pinout (3-8, 8-3, 5-5)]
    v
[Insert MMC configured for MPI in another known-good IM 151-7
 and read its HW Config; if PROFIBUS DP slave is set, root cause confirmed]
    |
    v
[Apply Resolution Matrix in Section 5]

4.1 Reading Module Information During the MRES Window

When MRES is cycled and the IM 151-7 has not yet pulled the configuration from MMC (or the MMC is missing), the diagnostic buffer and Module Information > Communication screen are the most reliable way to confirm the loaded state. The key fields and the values that point to the DP-slave / MMC-injected root cause are:

5. Resolution Matrix

The resolution depends on what you have available and whether you need to preserve the existing program. The matrix below summarises the three realistic recovery paths.

5.1 Path A — MRES Memory Reset

1. Power the ET 200S station down.
2. Hold the MRES switch in the reset position for at least 3 seconds.
3. Release, then within 3 seconds turn the mode selector to MRES again. The STOP LED flashes rapidly to confirm the request.
4. Wait for the CPU to return to STOP with the STOP LED on steady. The work memory is cleared. The MMC is not erased; it is only detached logically for the current session.
5. With the MMC removed or in a freshly-inserted state where the IM 151-7 cannot find a valid configuration, the default behaviour is to come up with interface X1 set to MPI, address 2, 187.5 kbps.
6. Re-scan Accessible Nodes from STEP 7. The IM 151-7 should now respond as an active MPI node.

5.2 Path B — Replace the MMC

1. Order a Siemens-branded MMC sized for the project (typical 512 KB to 2 MB is enough for the IM 151-7 program; 8 MB for the full V3.x firmware + project).
2. Power off, swap the MMC. The IM 151-7 will boot with no configuration; default MPI = 187.5 kbps, MPI address = 2.
3. Connect with the PC adapter on MPI and download the corrected project. In the corrected project's HW Config confirm that Interface X1 Properties > Interface Type is set to MPI and that the Address is the value your STEP 7 project expects.
4. Perform a PLC > Download to Target with the new configuration. Power-cycle to verify the new state persists.

Siemens does not publish a stand-alone MMC "image reset" tool for the S7-300 / ET 200S family, but a third-party MMC backup / restore tool is widely used to pre-stage a known-good image. Always verify the resulting image by writing to a fresh card and confirming the IM 151-7 boots in MPI mode at 187.5 kbps.

5.3 Path C — Use a Siemens PROFIBUS CP Card on the PC

Use a real PROFIBUS CP card on the PC so that STEP 7 can speak PROFIBUS at 1.5 Mbps and higher. Recommended CPs:

After installing the CP and the SIMATIC NET PC software, configure PG/PC interface in STEP 7 to point to the CP and the configured PROFIBUS address of your PC. You can then connect directly to the IM 151-7 on its PROFIBUS segment and download the project, even with the IM 151-7 left configured as a DP slave.

6. PC Adapter (6ES7 972-0CA23-0XA0) Limitations

The PC Adapter USB (6ES7 972-0CA23-0XA0) is the most common field PC-to-MPI / PROFIBUS interface for STEP 7 V5.x. Its electrical and protocol limits matter for this case:

The 187.5 kbps ceiling on the PC Adapter is the practical reason why a 1.5 Mbps or 12 Mbps DP segment will never come up with this adapter, even if the adapter driver nominally shows "PROFIBUS" in the PG/PC interface selection.

7. Step-by-Step Recovery Procedure (Recommended Order)

The following sequence is the safest and is what Siemens support would typically recommend. It is designed to preserve the program and to confirm at every step whether the IM 151-7 has actually returned to MPI master mode.

1. Disconnect the PROFIBUS cable from X1 if the IM 151-7 was on a real DP segment. This isolates the node and prevents bus noise from corrupting the diagnostic scan.
2. Connect the PC Adapter (USB or RS-232 variant) directly to X1 with a PROFIBUS cable. Confirm the bus termination: termination on at both ends of the segment, the IM 151-7 must be one of the physical ends (or use a PROFIBUS connector with the built-in switchable termination, e.g., 6ES7 972-0BA12-0XA0).
3. Set the PG/PC interface in STEP 7 to PC Adapter (MPI) with the local MPI address 0 and a transmission rate of 187.5 kbps (PG/PC interface > Properties > MPI). The transmission rate must match what the IM 151-7 is currently using on MPI.
4. Open Accessible Nodes. With the MMC configured for DP slave, the IM 151-7 will either not appear or will appear as passive.
5. Cycle the MRES switch as described in Section 5.1. Within the brief window before the MMC configuration reloads (or with the MMC removed), the IM 151-7 should reappear as an active MPI node at the default address 2.
6. If the node reappears: go online and read the diagnostic buffer (PLC > Diagnostic/Setting > Diagnostic Buffer). Look for entries such as DP slave not in master parameter set or Parameter assignment error on X1 — these confirm the DP-slave / MMC root cause.
7. Decide on the resolution path. If you have a CP 5611 / 5621 / 5711 available, path C is the cleanest because it preserves the program and the configuration. Otherwise proceed to path B and replace the MMC.
8. Re-download the corrected HW Config to the IM 151-7 with interface X1 set to MPI, address = your project value, baud = 187.5 kbps.
9. Power cycle the station and confirm with Accessible Nodes that the IM 151-7 still appears and that the BF LED is off.

8. Verification Checklist

After applying the recovery, the following must all be true before closing the case:

• BF LED off, SF LED off after a full power cycle with the corrected MMC and the corrected HW Config.
• STOP / RUN LED reflects the mode selector position (STOP = yellow, RUN = green).
• Accessible Nodes from STEP 7 lists the IM 151-7 as active at the configured MPI address and baud rate.
• Module Information > Communication shows: interface X1 = MPI, transmission rate = 187.5 kbps, at least 1 PG connection resource assigned.
• Diagnostic buffer shows a clean restart with no parameter-assignment or bus-fault entries.
• Program download and online monitor work without timeouts.

9. Edge Cases and Field-Proven Caveats

• Empty MMC still reports a PROFIBUS DP slave configuration. An MMC that has never held a STEP 7 project still contains enough low-level structure (firmware-aware boot block) that the IM 151-7 will boot. If the last user project configured the interface as DP slave, the IM 151-7 will continue to do so. Path B (blank MMC) is the only reliable way to force the default MPI behaviour.
• Different firmware, different default address. V2.x firmware defaults to MPI address 2; V3.x firmware in some sub-variants defaults to MPI address 3. Always read the actual address from the accessible node window — do not assume.
• MPI passive node at the same address as a real device. If a DP slave address is set to 2 and there is a real MPI device on the segment at address 2, the node scan will see the real device, not the IM 151-7. Use Target System > MPI Address > Diagnostics from the PC adapter properties to read the live bus participants.
• STEP 7 version compatibility. The IM 151-7 V3.x requires STEP 7 V5.4 SP5 or later, or TIA Portal V13 SP1 or later. With STEP 7 V5.2 the V3.x firmware is not editable in HW Config and the V2.x firmware image can produce cryptic errors. Either upgrade the tool or downgrade the firmware to V2.x on the IM 151-7.
• CP 5611 on modern PCs. CP 5611 is a 5 V PCI card. Most desktop PCs since 2015 use PCIe slots with no 5 V signalling. CP 5621 (PCIe) or CP 5711 (USB) is the modern equivalent. The Siemens Siemens SiePortal ET 200S communication forum has multiple threads documenting this compatibility issue.
• Bus topology. The PC adapter should be on its own short stub or at the end of the segment. Connecting it in the middle of a terminated segment without isolating the stub can lead to reflection and the "node appears intermittently" symptom.

10. When the IM 200S Migrates to S7-1200 / TIA Portal

For new installations, the ET 200S line is being replaced by the ET 200SP and the IM 151-8 PN/DP CPU. The TIA Portal configuration of a modern ET 200S (now an ET 200SP variant) as a PROFIBUS slave of an S7-1200 is documented in the TIA Portal help: Configuring an ET 200S (S7-1200). The principles of interface mode = MPI vs PROFIBUS DP slave still apply and the same root cause and resolution matrix applies — only the part numbers and the engineering tool change.

11. Quick Reference: LED-to-Cause Mapping

12. Frequently Asked Questions