Troubleshooting IM151-7 CPU Standalone Online Connection via MPI

David Krause15 min read
S7-300SiemensTroubleshooting
Licensed PE Working through this on a live machine? A Maine-licensed engineer can take it from here — included with IMD hardware, by the hour for everything else. Book an engineer

Problem Details and Affected Hardware

The SIMATIC ET 200S IM 151-7 CPU integrates an S7-300-compatible CPU with a PROFIBUS DP master/slave interface into a single head module designed for the ET 200S distributed I/O family. In standalone operation the IM 151-7 CPU exposes a single RS-485 port that supports both MPI (default) and PROFIBUS DP protocols. Field engineers frequently encounter a state in which STEP 7 V5.x (SIMATIC Manager) or TIA Portal cannot establish an online session to the IM 151-7 CPU even though the Field PG, the cable, and the PG/PC interface assignment are demonstrably functional with other S7-300 CPUs (for example the 6ES7315-2AH14-0AB0).

The catalog numbers most often encountered in service work are listed below.

Module / Cable Catalog Number Role Notes
IM 151-7 CPU (standard) 6ES7151-7AA20-0AB0 ET 200S head module with CPU S7-300 compatible, RS-485 MPI/DP
IM 151-7 CPU FO 6ES7151-7AA21-0AB0 Variant with fiber-optic PROFIBUS Phase-out model; modified system behavior
IM 151-1 COMPACT 6ES7151-1CA00-3BL0 ET 200S head module (no CPU) Interface module only, not programmable as CPU
MPI programming cable 6ES7901-08F00-0AA0 RS-485 MPI cable for Field PG Supplied with Field PG M3 / M4; 187.5 kbps
PROFIBUS 12 Mbps cable 6ES7901-4BD00-0XA0 PROFIBUS DP cable Up to 12 Mbps, RS-485, suitable for MPI
SIMATIC MMC (512 KB) 6ES7953-8LF20-0AA0 Micro Memory Card Stores project, hardware config, connection list
Note: The IM 151-1 COMPACT (6ES7151-1CA00-3BL0) is an interface module, not a CPU. It has no user program and cannot be the target of a STEP 7 online session. The troubleshooting procedure below applies only to the IM 151-7 CPU variants.

Symptom Matrix

Symptom Most Likely Cause First Check
"Port setting or cable faulty" dialog PG/PC interface points to S7ONLINE → None Set PG/PC Interface; select physical adapter
"Accessible Nodes" returns empty Address mismatch, BF, or MMC config Pull MMC, power-cycle, retry
Diagnostics shows only "Port 0, OK" No physical adapter assigned Set PG/PC Interface to PC Adapter / CP
BF LED permanently on PROFIBUS wiring or segment fault Check terminators, isolate downstream nodes
SF LED flashing, BF on, RUN off Hardware / configuration fault Read diagnostic buffer; consider MRES
Same Field PG connects to S7-300 but not IM 151-7 IM 151-7-side configuration issue Remove MMC and retry at MPI address 2
Field PG cannot see the IM 151-7 in Auto Wrong baud rate or address range Set Highest Station Address = 31; force 187.5 kbps

Root Cause Analysis

When the same Field PG, the same MPI/DP cable, and the same PG/PC interface assignment successfully connect to an S7-300 CPU but fail on the IM 151-7 CPU, the fault is generally on the IM 151-7 side. The four root causes most commonly observed in field service are summarized below.

Cause 1 — Address Conflict or Out-of-Range Address

Both MPI and PROFIBUS use node addresses in the segment. MPI defaults to 0–31, PROFIBUS to 0–126. If the IM 151-7 CPU has been configured with a non-default address that does not match the Field PG address range, or if two stations share an address, "Accessible Nodes" cannot enumerate the target. The BF LED may or may not be lit depending on whether the IM 151-7 CPU sees other active stations on the segment.

Cause 2 — Configuration Persisted on the MMC

The IM 151-7 CPU boots its project, hardware configuration, and connection parameters from a Micro Memory Card (MMC) inserted in the slot on the front of the module. If the MMC contains a project that was downloaded with a non-default PG/PC interface setting, a fixed PROFIBUS address, or a configuration that disables MPI on the integrated port, the Field PG must match those settings exactly. A factory reset of the CPU alone does not clear the MMC; the MMC must be removed, erased, or replaced to recover.

Cause 3 — Permanent Bus Fault (BF LED)

A permanently lit BF LED on the IM 151-7 CPU indicates the integrated DP master or DP slave interface cannot enter the operational state. Common causes include a missing terminating resistor at one or both ends of the PROFIBUS segment, a break in the segment, an unconfigured downstream slave, or a hardware fault in the IM 151-7 CPU itself. When BF is on, the CPU is typically still reachable on MPI while the DP side is dead.

Cause 4 — PG/PC Interface Misconfiguration

STEP 7 reports "Port 0" because the active PG/PC interface assignment is pointing to a virtual port (for example "S7ONLINE → None") rather than a physical adapter such as PC Adapter MPI, PC Adapter PROFIBUS, CP5512, CP5611, or CP5613. This is a configuration defect on the Field PG, not on the IM 151-7. The same Field PG can still communicate with other CPUs only because the operator previously selected the correct interface for those sessions.

Pre-Diagnostic Checklist

Before opening the IM 151-7 CPU, validate the following items in the order listed. Each item rules out a class of failure in under 30 seconds.

  1. Confirm the IM 151-7 CPU has 24 V DC supply on the ET 200S power module; the ON, SF, BF, RUN, and STOP LEDs must be observable.
  2. Verify the mode selector is in the RUN or RUN-P position, not MRES.
  3. Confirm the MMC is fully seated in the slot. The MMC must be present for the CPU to retain a project across power cycles.
  4. Open "Set PG/PC Interface" in SIMATIC Manager (or "Online & Diagnostics" in TIA Portal) and confirm the active interface is the physical adapter, not "S7ONLINE → None".
  5. Run the interface diagnostics (Test → Start) and verify it reports the physical port with baud rate, not just "Port 0".
  6. Swap the MPI cable for a known-good PROFIBUS 12 Mbps cable (for example 6ES7901-4BD00-0XA0). MPI and PROFIBUS share RS-485, so the same cable type is valid for both protocols.
  7. Terminate the bus segment at both physical ends with PROFIBUS connectors that have the terminating resistor enabled.
  8. Connect the Field PG to a known-good S7-300 CPU (for example 6ES7315-2AH14-0AB0) on the same cable to confirm the toolchain.

Diagnostic Procedure

Execute the following steps in sequence. Stop at the first step that changes the symptom and proceed to the corresponding solution path.

  1. Read the LED cluster on the IM 151-7 front panel. Note the state of SF, BF, ON, RUN, and STOP. A permanently lit BF LED combined with a flashing SF LED is the canonical signature of a configuration or bus fault.
  2. Open STEP 7 → Options → Set PG/PC Interface. Select the physical adapter (PC Adapter MPI, PC Adapter PROFIBUS, CP5512, CP5611, CP5613, or USB/MPI). Click "Diagnostics" → "Test" and verify the COM port and baud rate.
  3. Run "Accessible Nodes" (PLC → Accessible Nodes). If the IM 151-7 CPU appears with its MPI/DP address, the connection is functional; the issue is on the project side. If the list is empty, proceed.
  4. Open "Online → Online Partners" (or PLC → Diagnostics/Set). Observe whether the IM 151-7 reports a target address. A blank result confirms a layer-1 or layer-2 issue.
  5. Power-cycle the IM 151-7 CPU and re-test. This clears transient PROFIBUS state machines on the integrated DP master.
  6. Remove the MMC, power-cycle, and re-test. Without an MMC the IM 151-7 CPU boots with factory defaults (MPI address 2, baud 187.5 kbps). If "Accessible Nodes" now lists the IM 151-7, the fault was on the MMC.
  7. Test the IM 151-7 CPU in isolation on the bench. Disconnect all downstream ET 200S modules and the DP segment. Connect the Field PG directly with an MPI cable. If the IM 151-7 is reachable, the original segment had a wiring or termination defect.
Field PG PC Adapter MPI/DP RS-485 MPI 187.5 kbps IM 151-7 CPU 6ES7151-7AA20 ET 200S Power + I/O 24 V DC Point-to-point MPI link; PROFIBUS termination not required

Solution: MRES Factory Reset

The MRES (Memory Reset) operation restores the IM 151-7 CPU to factory defaults and clears the work memory, system data, and the backup copy of the project. It does not erase the MMC; for an MMC reset, see the next section.

  1. Set the mode selector to STOP. The RUN/STOP LED changes from green to steady yellow.
  2. Hold the selector in the MRES position until the STOP LED begins to flash slowly (approximately 3 seconds).
  3. Release the selector back to STOP, wait for the STOP LED to stop flashing, then move the selector to MRES again within 3 seconds.
  4. Hold MRES until the STOP LED begins to flash rapidly (the CPU is performing the reset).
  5. Release the selector. The STOP LED returns to a steady yellow state, indicating the reset is complete.

If the procedure is performed correctly, the IM 151-7 CPU is reachable at MPI address 2 with the default baud rate of 187.5 kbps. If the procedure does not complete, repeat the steps; the timing is sensitive and field engineers commonly report needing two or three attempts before the CPU accepts the reset.

RUN / RUN-P STOP Steady yellow LED MRES Hold 3 s Slow flash MRES Reset Fast flash, then steady STEP 1 STEP 2 STEP 3 Default state after MRES: MPI address 2, 187.5 kbps, no project loaded.

Solution: MMC Reset Procedure

When the IM 151-7 CPU loads a project from the MMC, parameters stored on the card (MPI address, DP address, baud rate, connection list) override the factory defaults. To recover from a corrupted or unwanted MMC configuration, use one of the procedures below.

  1. Pull the MMC, power-cycle, and operate without it. With no MMC, the IM 151-7 CPU boots in factory-default state (MPI address 2, 187.5 kbps). This is the quickest way to recover a reachable target without erasing the existing project on the card.
  2. Format the MMC from STEP 7. Insert the MMC into the Field PG's MMC reader, then in SIMATIC Manager select the drive, right-click → "Memory Card → Format". This clears all blocks, system data, and project files on the card. Reinsert the card into the IM 151-7 CPU and perform an MRES to ensure internal work memory matches the empty card.
  3. Replace the MMC with a known-empty card. If a spare blank MMC is available (for example 6ES7953-8LF20-0AA0, 512 KB, or larger), insert it and power-cycle. The IM 151-7 CPU will start without a project. Re-download the project from STEP 7 (PLC → Download to Device).
Warning: Performing an MMC format or using a blank MMC will erase the project stored on the original card. Always back up the original MMC contents with SIMATIC Manager (File → Memory Card → Upload to PG) before erasing, or use a spare card for the reset attempt.

Solution: Standalone Configuration

Once the IM 151-7 CPU is reachable, configure it explicitly for standalone operation. The configuration steps differ between STEP 7 V5.x (SIMATIC Manager) and TIA Portal.

STEP 7 V5.x (SIMATIC Manager)

  1. Open or create the STEP 7 project. Insert the IM 151-7 CPU from the hardware catalog (SIMATIC 300 → ET 200S → IM 151-7 CPU).
  2. Open HW Config and double-click the PROFIBUS interface (X1) on the IM 151-7 CPU module.
  3. In the Properties dialog, set the Address tab to "MPI" and confirm the address is 2 (or another unused address in the segment). The default Highest MPI Address is 15.
  4. For PROFIBUS operation, switch the interface type to "PROFIBUS" and set the address. Confirm the transmission rate matches the bus (default 1.5 Mbps).
  5. Save and compile (Station → Save and Compile). Download the hardware configuration to the IM 151-7 CPU (PLC → Download to Device).

TIA Portal

  1. Open the TIA Portal project. In the project tree, add the IM 151-7 CPU as a new device (Add new device → SIMATIC ET 200S CPU → IM 151-7 CPU).
  2. Open "Device Configuration" and select the PROFIBUS interface of the IM 151-7 CPU.
  3. In the Properties pane, switch the interface to "MPI" or "PROFIBUS" as required and set the address.
  4. Compile the project and download to the device (Online → Download to device).

For I-slave configuration where the IM 151-7 CPU exchanges data with a higher-level DP master, refer to the official TIA Portal example at Example: Configuring an ET 200 CPU as an I-Slave.

Cable and Connector Specifications

Both MPI and PROFIBUS DP operate on RS-485 over a shielded twisted-pair cable. The standard PROFIBUS cable (violet jacket, for example 6XV1830-0EH10) is suitable for both protocols. The two cable types referenced in the field case (6ES7901-08F00-0AA0 and 6ES7901-4BD00-0XA0) are functionally interchangeable for point-to-point connections between a Field PG and an IM 151-7 CPU; the difference is the maximum supported baud rate and the connector termination type.

Cable Catalog Connector Max Baud Notes
MPI programming cable 6ES7901-08F00-0AA0 Sub-D, 9-pin 187.5 kbps Supplied with Field PG M3 / M4
PROFIBUS cable 6ES7901-4BD00-0XA0 Sub-D, 9-pin 12 Mbps Suitable for MPI and DP
PROFIBUS FC cable (bulk) 6XV1830-0EH10 None (bulk) 12 Mbps Standard violet PROFIBUS cable

Termination rules: Each PROFIBUS segment must be terminated at both physical ends. The PROFIBUS connector at the IM 151-7 CPU should have the terminating resistor switched ON only if the IM 151-7 is the physical end of the segment; otherwise the switch must be OFF. In a point-to-point bench setup with a single Field PG and a single IM 151-7 CPU, exactly one terminator (typically at the IM 151-7 end) is sufficient.

LED Status and PG/PC Diagnostics

LED State Meaning
ON (green) Steady 24 V DC supply present
SF (red) Flashing System fault; read diagnostic buffer
SF (red) Steady Hardware fault
BF (red) Steady PROFIBUS / DP bus fault (no connection)
BF (red) Flashing DP slave not configured or failed
RUN (green) Steady CPU in RUN
RUN (green) Flashing CPU starting / self-test
STOP (yellow) Steady CPU in STOP
STOP (yellow) Slow flash MRES requested, hold position
STOP (yellow) Fast flash MRES in progress

The PG/PC interface diagnostics should report the physical COM or USB port, the active protocol (MPI or PROFIBUS), the local address (typically 0 for the PG), and the transmission rate. A return of "Port 0, OK" without a baud rate or peer address indicates the active interface is "S7ONLINE → None"; this is the cause of the "Port 0" symptom reported in the field case.

Verification Procedure

  1. Open SIMATIC Manager. From the menu, choose PLC → "Accessible Nodes".
  2. Confirm the IM 151-7 CPU appears in the list with the correct MPI or PROFIBUS address.
  3. Right-click the IM 151-7 entry and choose "Go Online". The online view should open without an error dialog.
  4. Open "PLC → Download to Device" and verify the system data, blocks, and hardware configuration match the offline project.
  5. Open the diagnostic buffer (PLC → Diagnostics/Set → Module Information) and confirm no SF or BF entries remain.
  6. Toggle the mode selector to RUN-P. The RUN LED should be steady green and the BF LED should be off if the PROFIBUS segment is healthy.

For TIA Portal, the equivalent verification is Online → "Online & Diagnostics" → "Accessible nodes" and the "Diagnostics" tab of the online view. The MRES procedure and MMC handling apply to both toolchains.

Edge Cases and Related Issues

Phase-Out Variant IM151-7 CPU FO (6ES7151-7AA21-0AB0)

The FO (fiber-optic) variant of the IM 151-7 CPU exhibits slightly modified system behavior compared to the standard variant, including differences in the diagnostic buffer format and the way BF LED states are reported. See the official phase-out announcement at Phase-out announcement for ET 200S IM151-7 CPU FO for details on the affected firmware revisions and migration paths.

Standalone vs. I-Slave Operation

The IM 151-7 CPU can be used as a standalone PROFIBUS DP master, as a DP slave (I-slave) behind another DP master, or as an MPI node. The configuration of the integrated PROFIBUS interface must match the role. Refer to the official manual at SIMATIC ET 200S IM 151-7 CPU Interface Module Manual for the full role matrix and configuration pages.

BF LED Caused by Downstream ET 200S Station Failure

If the BF LED remains on after the IM 151-7 CPU is reachable on MPI, the integrated DP master is detecting a failure on the PROFIBUS segment. Disconnect downstream ET 200S stations one at a time to isolate the offending node. Enable the terminating resistor only at the two physical ends of the segment.

Highest Station Address Affects "Accessible Nodes"

STEP 7's "Accessible Nodes" function scans up to the configured Highest Station Address. If the IM 151-7 CPU is at MPI address 2 and the Field PG is set to a Highest Station Address of 0, the scan will not find it. Set the Highest Station Address to 31 for MPI or 126 for PROFIBUS to ensure full enumeration.

What is the default MPI address and baud rate of a factory-fresh IM 151-7 CPU?

The factory-default MPI address is 2 with a baud rate of 187.5 kbps. The Highest MPI Address is 15. These defaults apply only when the MMC is empty or removed.

Does MRES erase the Micro Memory Card (MMC)?

No. MRES clears the work memory and the internal backup copy of the project, but the MMC is not modified. To clear the MMC, format it from SIMATIC Manager (Memory Card → Format) or replace it with a blank card.

Can I use a PROFIBUS cable to connect to the IM 151-7 CPU on MPI?

Yes. MPI and PROFIBUS DP both use RS-485 over a shielded twisted-pair cable. Any PROFIBUS cable (for example 6ES7901-4BD00-0XA0 or 6XV1830-0EH10) is suitable for MPI connections up to its rated baud rate. The 6ES7901-08F00-0AA0 MPI cable supplied with Field PG M3 / M4 is also valid for MPI but limited to 187.5 kbps.

Why is the BF LED on permanently even though the CPU runs?

A steady BF LED indicates the integrated PROFIBUS interface is unable to enter the operational state. The CPU itself is fine; the issue is on the bus segment (missing terminator, wiring break, unconfigured or failed slave). Disconnect downstream stations to isolate.

What is the difference between the IM 151-7 CPU and the IM 151-1 COMPACT?

The IM 151-7 CPU (6ES7151-7AA20-0AB0 / 6ES7151-7AA21-0AB0) is a true CPU that runs a STEP 7 user program. The IM 151-1 COMPACT (6ES7151-1CA00-3BL0) is an interface module that only forwards I/O data to a DP master; it has no user program and cannot be programmed online as a CPU.

Back to blog