Resolving CPU 315-2PN/DP Fault with IE/PB Link and IM151-7 CPU

David Krause13 min read
PLC HardwareSiemensTroubleshooting
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 Overview

When an IE/PB Link PN IO gateway is inserted between a Siemens S7-300 CPU 315-2PN/DP (6ES7 315-2EH14-0AB0 family) and an ET 200S IM151-7 CPU (6ES7 151-7AA20-0AB0), the controllers drop into SF (System Fault) / STOP while the IE/PB Link itself remains in RUN, displays no diagnostic alarms, and is fully accessible from the engineering station. The visible symptom in STEP 7 / SIMATIC Manager is that the CPU 315-2PN/DP goes into fault mode and the IM151-7 CPU also goes into fault mode, yet the IE/PB Link module is in Run mode and shows OK and is accessible.

This is a configuration symptom, not a hardware failure. The IE/PB Link has no PROFINET slot mismatch and no bus fault, so it stays online; the CPUs detect a mismatch in slot 0 / slot 2 configuration data, in PROFINET device name assignment, or in PROFIBUS DP slave I/O mapping and raise an OB 85 / OB 86 / OB 122 error that escalates to STOP without an explicit OB handler.

Affected Hardware and Firmware

Component MLFB / Part Number Valid Firmware Notes
CPU 315-2 PN/DP 6ES7 315-2EH14-0AB0 V3.3 / V3.4 2 PROFINET ports, 1 PROFIBUS DP master/slave
ET 200S IM151-7 CPU 6ES7 151-7AA20-0AB0 V2.7 / V3.0 PROFINET IO Device, S7-300 compatible instruction set
IE/PB Link PN IO 6GK1 411-5AB00 V4.2 or higher PROFINET IO Device, PROFIBUS DP Master
STEP 7 V5.5 + SP4 / HF7 — HW Config catalog version 2017.10 or newer required for IM151-7 FW 3.0
Always confirm the IM151-7 firmware version on the front of the module (the last two digits of the MLFB are insufficient). Modules labeled V2.x cannot operate in some topologies that V3.x supports, and mismatches between STEP 7 catalog revision and module firmware can also produce SF on the CPU.

Network Topology and Data Flow

The intended topology in the source configuration is a two-level PROFINET/PROFIBUS bridge:

  1. CPU 315-2PN/DP acts as PROFINET IO Controller on its PN port (X1 or X2, both are PROFINET interfaces on a 315-2 PN/DP; the second port is X2 with switch functionality).
  2. The IE/PB Link PN IO is a PROFINET IO Device on the same PROFINET subnet and a PROFIBUS DP Master on its downstream DP port.
  3. The IM151-7 CPU is connected as a PROFIBUS DP Slave on the downstream PROFIBUS network of the IE/PB Link, OR — in the configuration shown — as a PROFINET IO Device on the same PROFINET subnet with the IE/PB Link used only for additional DP slaves.

The user's HW Config screenshot shows an explicit I/O mapping of 1 byte: IB157 (1 Byte output, QB0 of the IM151-7 CPU) -> 1 Byte Input, IB0 of the main PLC. This is a typical slot 0 / slot 1 mapping for the IM151-7 in a DP-Slave role. The mapping itself is technically allowed; the fault originates from the way the slot is configured inside the IE/PB Link head module.

Diagnostic Buffer Analysis

Open the CPU online with STEP 7 and read the diagnostic buffer (PLC → Module Information → Diagnostic Buffer). The first incoming event with a stop cause must be identified before changing any hardware. The expected entries — in time order — for this fault class are:

Event ID Meaning Likely Cause in This Topology
0x1391 / W#16#1391 PROFINET IO: station failure Device name of IE/PB Link not assigned, or wrong name written
0x1394 / W#16#1394 PROFINET IO: module slot mismatch Slot 0 submodule of the IM151-7 differs from configured submodule
0x39E1 / W#16#39E1 PROFIBUS DP: slave diagnostic, station failure PROFIBUS address conflict or termination missing
0x2942 / W#16#2942 I/O access error (OB 85) Process image mismatch on IM151-7
0x3582 / W#16#3582 STOP due to STOP command or configuration error Configuration error in OB 100 / startup

Document the diagnostic buffer of both controllers before downloading. The IM151-7 buffer is read through its own PROFINET/DP interface using its configured IP or PROFIBUS address.

Root Cause Analysis

Three independent root causes are commonly observed in this configuration, all of which lead to the observed symptom ("IE/PB Link RUN, both CPUs in fault mode"):

  1. PROFINET device name not written to the IE/PB Link PN IO. The IE/PB Link is delivered with a blank name. Without a name it cannot be addressed by the IO Controller, the slot 0 head module reports not found, and any DP slaves behind the link generate station-failure events that the controller's OB 86 cannot acknowledge. Reference: PROFINET commissioning (entry ID 19290277).
  2. HW Config slot mismatch for the IM151-7 CPU. The IM151-7 has a default slot 0 with submodule "IM151-7 CPU interface". If the project uses a generic IM151 head instead of the IM151-7 CPU variant, the slot 0 record length differs and the CPU raises an OB 85 on every cycle. The correct entry is IM151-7 CPU > Interface module > Submodule: PROFINET IO in the catalog.
  3. PROFIBUS DP address and master address of the IE/PB Link. The IE/PB Link must be configured as a DP Master with a unique PROFIBUS address (default 0 is reserved for masters with class 2). The IM151-7 must be assigned a slave address that does not collide with other DP nodes on that segment.
A common mistake is to drag a generic IE/PB Link V3.0 into HW Config while the physical module is V4.x. The slot 0 GSD revision is then incompatible and the IE/PB Link reports OK on its own web page, but the IO Controller cannot synchronize the AR (Application Relationship). Always match the catalog entry to the printed firmware version on the label.

Hardware Configuration Procedure in STEP 7

  1. Open the STEP 7 project, expand SIMATIC 300 Station, double-click Hardware to open HW Config.
  2. Insert the CPU 315-2PN/DP in slot 2 of the rail from SIMATIC 300 > CPU 300 > CPU 315-2 PN/DP > 6ES7 315-2EH14-0AB0 > V3.3 (or matching firmware).
  3. Right-click the CPU PROFINET interface and select Properties > Ethernet > IP address. Assign a free IPv4 address from the same subnet as the IE/PB Link (default factory IP of the IE/PB Link is 192.168.0.1; change it before assigning a name).
  4. Drag the IE/PB Link PN IO from the catalog (PROFINET IO > Network Components > IE/PB Link PN IO > 6GK1 411-5AB00) onto the PROFINET subnet. STEP 7 will create a PROFINET IO System on the IE/PB Link's DP port automatically.
  5. Drag the IM151-7 CPU from PROFINET IO > ET 200S > IM151-7 CPU > 6ES7 151-7AA20-0AB0 either onto the PROFINET IO System of the CPU 315-2PN/DP (PROFINET topology) or onto the PROFIBUS network hosted by the IE/PB Link (PROFIBUS topology). Verify the catalog revision matches the firmware.
  6. Open the IE/PB Link Properties > PROFINET device name. Enter a unique device name, e.g. iepb-link-01. The name is case-sensitive.
  7. Configure the IM151-7 slot 0 module. The module should be IM151-7 CPU with submodule PROFINET IO. The slot 0 length must be 0 bytes for the IM151-7 CPU; the I/O area is mapped via the integrated digital I/O or DP/PN submodule and not via slot 0.
  8. Open the I/O mapping. The example shows QB0 of IM151-7 → IB157 of CPU 315-2PN/DP as 1 byte. This is created on the Module properties of the IM151-7, tab Addresses. Do not set the address of the IE/PB Link head module itself to a non-zero slot 0; it must remain at address 0 with 0 bytes.
  9. Save and compile, then download HW Config to both stations.

PROFINET Device Name Assignment

The IE/PB Link does not adopt a name by itself. The name must be written over PROFINET using one of these methods:

  1. From STEP 7 (recommended): In HW Config, right-click the IE/PB Link → PROFINET device name → Assign. STEP 7 will resolve the device using LLDP and write the name to the persistent storage of the IE/PB Link.
  2. From the IE/PB Link web server: Browse to the IP, log in with the admin / siemens default credentials, navigate to Module Information → PROFINET, enter the name, click Set Name. The web server is the only method that does not require a TIA / STEP 7 connection; it is used when the controller CPU is offline.
  3. From the Primary Setup Tool (PST) or PRONETA: These utilities can scan the network and push a name without an online connection to the controller.
The device name and the IP address are independent. A controller with a configured device name that does not match the link will start the AR (Application Relationship) and then immediately drop it. The CPU buffer will then show Station failure / 0x1391 and the IE/PB Link will appear healthy because it never received a valid AR. This is the single most common root cause of the observed symptom.

PROFIBUS DP Slave Configuration of the IM151-7

When the IM151-7 is used as a DP slave behind the IE/PB Link, additional steps are required:

  1. On the IE/PB Link, open PROFIBUS DP Master System → Properties > PROFIBUS and set a master PROFIBUS address (e.g. 2). Address 1 is normally the IE/PB Link's own address; address 0 is reserved for class-2 masters.
  2. Drag the IM151-7 from PROFIBUS DP > ET 200S > IM151-7 CPU > 6ES7 151-7AA20-0AB0 onto the DP Master System of the IE/PB Link.
  3. Set the IM151-7 slave address to a unique value (e.g. 3). The address must match the DIP switch on the physical module — STEP 7 will warn if a mismatch exists, but the CPU will still go to fault on the first cycle.
  4. Configure slot 1 with the digital I/O submodule. The mapping shown in the source (QB0 → IB0 main PLC) corresponds to a 1-byte output submodule of the IM151-7 in slot 1.
  5. Save, compile, and download to the IE/PB Link. The IE/PB Link holds the DP configuration for its slaves in its own project, not in the main CPU project.

Firmware Compatibility Matrix

IE/PB Link Firmware STEP 7 Catalog Entry IM151-7 FW Supported Status
V3.0 IE/PB Link V3.0 V2.x only Obsolete, no V3.x support
V4.0 IE/PB Link V4.0 V2.x, V3.0 Recommended minimum
V4.2 IE/PB Link V4.2 V2.x, V3.0 Current production
V5.0 IE/PB Link V5.0 (HW Rev ≥ 8) V3.0+ For TIA Portal V18 projects

If the catalog and firmware do not match, the CPU diagnostic buffer will report 0xEA02 / W#16#EA02 ("Configuration of the PROFINET device does not match") on the first PROFINET AR attempt.

Step-by-Step Resolution Procedure

  1. Power down all three stations. Inspect the IE/PB Link and IM151-7 labels and record firmware versions.
  2. Open STEP 7 HW Config and verify each catalog entry matches the recorded firmware version. Replace any generic entries with the exact MLFB and firmware combination.
  3. Assign a unique PROFINET device name to the IE/PB Link and write it using PLC → Ethernet → Assign PROFINET device name.
  4. Verify PROFIBUS address DIP switches on every DP slave against the HW Config.
  5. Add error-handling OBs: OB 82 (diagnostic interrupt), OB 83 (insert/remove), OB 85 (I/O access error), OB 86 (rack failure), OB 121 (programming error), OB 122 (I/O access). Without these OBs, the CPU will STOP on the first error. Reference: S7-300 CPU 31x-2 PN/DP Operating Instructions (entry ID 12996906).
  6. Compile and download HW Config to all three stations. Perform a complete restart (MRES) on each CPU so the new PROFINET AR is negotiated from cold-start state.
  7. Go online and read the diagnostic buffer of all three stations. The "incoming" event list must be empty after the restart.
  8. Force-test the I/O mapping: set QB0 of the IM151-7 and observe the value at IB157 of the CPU 315-2PN/DP via a VAT or watch table.
  9. Repeat the mapping in the opposite direction (output from the main CPU to input of the IM151-7) to verify the symmetric path is also alive.

Verification

The configuration is considered correct when all of the following are true:

  • SF / BF LEDs on the CPU 315-2PN/DP, the IM151-7 CPU, and the IE/PB Link are all off.
  • All three stations remain in RUN indefinitely (verified for ≥ 1 hour of process execution).
  • The diagnostic buffer has no incoming events for PROFINET station failure, DP station failure, or I/O access error.
  • The user I/O mapping exchanges process values in both directions with the configured length (in the source case, 1 byte output from IM151-7 → 1 byte input at the main PLC).
  • The IE/PB Link web server displays the assigned PROFINET name and shows the connected DP slaves in green.
If the IM151-7 is used as a PROFINET IO Device and not as a DP slave, ensure that the PROFINET name is also written to the IM151-7. The IM151-7 has its own PROFINET name independent of the IE/PB Link. Reference: ET 200S IM151-7 CPU Manual (entry ID 49857446).

Troubleshooting Matrix

Symptom Check Corrective Action
IE/PB Link RUN, CPU 315-2PN/DP in STOP with SF Diagnostic buffer event 0x1391 Write PROFINET device name to IE/PB Link
IM151-7 in STOP, IE/PB Link RUN Slot 0 / slot 1 configuration mismatch Reassign correct catalog entry and submodule
Both CPUs STOP, BF blinks on IE/PB Link PROFIBUS address conflict Re-number DP slaves, check termination (ON at both ends, OFF in the middle)
IM151-7 reachable but SF on main CPU Missing OBs (82, 83, 85, 86, 121, 122) Download empty OBs or OBs with user code
IE/PB Link shows OK but no I/O exchanged Slot 0 length not 0 Set slot 0 to 0 bytes, I/O on slot 1+
All stations go to STOP after power cycle but RUN in cold start PROFINET name not saved permanently Re-assign name from STEP 7, verify save in IE/PB Link

Safety and Diagnostic OB Recommendations

Distributed I/O is inherently fault-prone. The following OBs should be present in both CPU programs before commissioning is declared complete:

  • OB 82 — handles PROFINET diagnostic interrupts (submodule state change). Without OB 82, a channel fault will STOP the CPU.
  • OB 83 — handles submodule insert/remove events from the IE/PB Link DP port.
  • OB 85 — handles I/O access errors when the process image is updated against a missing or faulty slot.
  • OB 86 — handles rack / station failure, including IE/PB Link station failure.
  • OB 122 — handles direct I/O access errors (load / transfer to a faulty periphery word).

A minimal OB 100 (warm restart) and OB 102 (cold restart) are also required. Reference: IE/PB Link PN IO Operating Instructions (entry ID 23644920).

Why does the IE/PB Link show RUN while the CPUs are in fault mode?

The IE/PB Link has no PROFINET slot mismatch and no bus fault on its own; it stays online even when the controller cannot establish the Application Relationship (AR). The CPUs detect a missing or misconfigured AR and enter STOP through OB 85 or OB 86. Check the diagnostic buffer for events 0x1391 (station failure) and 0x1394 (module slot mismatch).

Do I have to assign a PROFINET device name to the IE/PB Link PN IO?

Yes. The IE/PB Link is delivered with a blank name. Without a name, the CPU 315-2PN/DP cannot address it and the AR will fail. Assign the name from STEP 7 (PLC → Ethernet → Assign PROFINET device name) or from the IE/PB Link's web interface at the IP address 192.168.0.1.

Can the IM151-7 CPU (6ES7 151-7AA20-0AB0) be used as a DP slave behind an IE/PB Link?

Yes. The IM151-7 supports both PROFINET IO Device mode and PROFIBUS DP Slave mode. In DP slave mode it is configured in HW Config on the PROFIBUS Master System hosted by the IE/PB Link. The slave address (set by DIP switch on the module) must match the configured address and must be unique on the segment.

Which OBs must be present in the CPU to avoid immediate STOP on PROFINET errors?

At minimum OB 82, OB 85, OB 86, and OB 122 should exist in the S7 program. Their absence causes the CPU to STOP on the first station failure, diagnostic interrupt, or I/O access error. Empty OBs are acceptable as a defensive baseline.

What does the mapping IB157 ← QB0 of the IM151-7 mean in the original configuration?

It defines a 1-byte output area in the IM151-7 (starting at QB0) that is read by the main CPU 315-2PN/DP as input bytes starting at IB157. The mapping is created on the IM151-7 module properties, tab Addresses. The address range must not collide with any other I/O in the main CPU process image.

Back to blog